diff --git a/doc/admin-guide-cloud/locale/admin-guide-cloud.pot b/doc/admin-guide-cloud/locale/admin-guide-cloud.pot new file mode 100644 index 0000000000..e6a075a636 --- /dev/null +++ b/doc/admin-guide-cloud/locale/admin-guide-cloud.pot @@ -0,0 +1,7734 @@ +msgid "" +msgstr "" +"Project-Id-Version: PACKAGE VERSION\n" +"POT-Creation-Date: 2014-01-30 06:24+0000\n" +"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n" +"Last-Translator: FULL NAME \n" +"Language-Team: LANGUAGE \n" +"MIME-Version: 1.0\n" +"Content-Type: text/plain; charset=UTF-8\n" +"Content-Transfer-Encoding: 8bit\n" + +#: ./doc/admin-guide-cloud/section_networking_introduction.xml:5(title) +msgid "Introduction to Networking" +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking_introduction.xml:6(para) +msgid "The Networking service, code-named Neutron, provides an API that lets you define network connectivity and addressing in the cloud. The Networking service enables operators to leverage different networking technologies to power their cloud networking. The Networking service also provides an API to configure and manage a variety of network services ranging from L3 forwarding and NAT to load balancing, edge firewalls, and IPSEC VPN." +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking_introduction.xml:14(para) +msgid "For a detailed description of the Networking API abstractions and their attributes, see the OpenStack Networking API v2.0 Reference." +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking_introduction.xml:20(title) +msgid "Networking API" +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking_introduction.xml:21(para) +msgid "Networking is a virtual network service that provides a powerful API to define the network connectivity and IP addressing used by devices from other services, such as Compute." +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking_introduction.xml:25(para) +msgid "The Compute API has a virtual server abstraction to describe computing resources. Similarly, the Networking API has virtual network, subnet, and port abstractions to describe networking resources." +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking_introduction.xml:30(caption) +msgid "Networking resources" +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking_introduction.xml:35(th) +msgid "Resource" +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking_introduction.xml:36(th) ./doc/admin-guide-cloud/section_networking_arch.xml:36(th) ./doc/admin-guide-cloud/section_networking_arch.xml:148(th) ./doc/admin-guide-cloud/section_networking_adv_features.xml:45(th) ./doc/admin-guide-cloud/section_networking_adv_features.xml:171(th) ./doc/admin-guide-cloud/section_networking_adv_features.xml:374(th) ./doc/admin-guide-cloud/section_networking_adv_features.xml:436(th) ./doc/admin-guide-cloud/section_networking_adv_features.xml:759(th) ./doc/admin-guide-cloud/section_networking_adv_features.xml:806(th) ./doc/admin-guide-cloud/section_networking_adv_features.xml:1074(th) ./doc/admin-guide-cloud/section_networking_adv_features.xml:1209(th) ./doc/admin-guide-cloud/section_networking_adv_features.xml:1287(th) ./doc/admin-guide-cloud/section_networking_adv_features.xml:1524(th) ./doc/admin-guide-cloud/section_networking_adv_features.xml:1902(th) ./doc/admin-guide-cloud/section_networking_adv_features.xml:2011(th) ./doc/admin-guide-cloud/section_networking_adv_features.xml:2054(th) ./doc/admin-guide-cloud/section_networking-use.xml:63(th) ./doc/admin-guide-cloud/section_networking-use.xml:127(th) ./doc/admin-guide-cloud/section_networking-use.xml:200(th) ./doc/admin-guide-cloud/section_networking-use.xml:304(th) +msgid "Description" +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking_introduction.xml:42(emphasis) ./doc/admin-guide-cloud/section_networking_arch.xml:147(th) ./doc/admin-guide-cloud/section_networking-use.xml:69(emphasis) +msgid "Network" +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking_introduction.xml:43(td) +msgid "An isolated L2 segment, analogous to VLAN in the physical networking world." +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking_introduction.xml:48(emphasis) ./doc/admin-guide-cloud/section_networking-use.xml:78(emphasis) +msgid "Subnet" +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking_introduction.xml:49(td) +msgid "A block of v4 or v6 IP addresses and associated configuration state." +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking_introduction.xml:53(emphasis) ./doc/admin-guide-cloud/section_networking-use.xml:90(emphasis) +msgid "Port" +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking_introduction.xml:54(td) +msgid "A connection point for attaching a single device, such as the NIC of a virtual server, to a virtual network. Also describes the associated network configuration, such as the MAC and IP addresses to be used on that port." +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking_introduction.xml:63(para) +msgid "You can configure rich network topologies by creating and configuring networks and subnets, and then instructing other OpenStack services like Compute to attach virtual devices to ports on these networks." +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking_introduction.xml:68(para) +msgid "In particular, Networking supports each tenant having multiple private networks, and allows tenants to choose their own IP addressing scheme (even if those IP addresses overlap with those used by other tenants). The Networking service:" +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking_introduction.xml:75(para) +msgid "Enables advanced cloud networking use cases, such as building multi-tiered web applications and allowing applications to be migrated to the cloud without changing IP addresses." +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking_introduction.xml:82(para) +msgid "Offers flexibility for the cloud administrator to customize network offerings." +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking_introduction.xml:87(para) +msgid "Enables developers to extend the Networking API. Over time, the extended functionality becomes part of the core Networking API." +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking_introduction.xml:95(title) +msgid "Plug-in architecture" +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking_introduction.xml:96(para) +msgid "The original Compute network implementation assumed a basic model of isolation through Linux VLANs and IP tables. Networking introduces the concept of a plug-in, which is a back-end implementation of the Networking API. A plug-in can use a variety of technologies to implement the logical API requests. Some Networking plug-ins might use basic Linux VLANs and IP tables, while others might use more advanced technologies, such as L2-in-L3 tunneling or OpenFlow, to provide similar benefits." +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking_introduction.xml:108(caption) +msgid "Available networking plug-ins" +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking_introduction.xml:113(th) ./doc/admin-guide-cloud/section_networking_introduction.xml:248(th) ./doc/admin-guide-cloud/section_networking_pagination_and_sorting_support.xml:12(th) +msgid "Plug-in" +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking_introduction.xml:114(th) +msgid "Documentation" +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking_introduction.xml:119(emphasis) +msgid "Big Switch Plug-in (Floodlight REST Proxy)" +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking_introduction.xml:125(link) +msgid "http://www.openflowhub.org/display/floodlightcontroller/Neutron+REST+Proxy+Plugin" +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking_introduction.xml:122(td) +msgid "Documentation included in this guide and " +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking_introduction.xml:129(emphasis) +msgid "Brocade Plug-in" +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking_introduction.xml:131(td) +msgid "Documentation included in this guide" +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking_introduction.xml:135(emphasis) ./doc/admin-guide-cloud/section_networking_introduction.xml:274(td) +msgid "Cisco" +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking_introduction.xml:138(link) +msgid "http://wiki.openstack.org/cisco-neutron" +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking_introduction.xml:141(emphasis) +msgid "Cloudbase Hyper-V Plug-in" +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking_introduction.xml:145(link) +msgid "http://www.cloudbase.it/quantum-hyper-v-plugin/" +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking_introduction.xml:148(emphasis) +msgid "Linux Bridge Plug-in" +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking_introduction.xml:152(link) +msgid "http://wiki.openstack.org/Neutron-Linux-Bridge-Plugin" +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking_introduction.xml:155(emphasis) +msgid "Mellanox Plug-in" +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking_introduction.xml:159(link) +msgid "https://wiki.openstack.org/wiki/Mellanox-Neutron/" +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking_introduction.xml:162(emphasis) +msgid "Midonet Plug-in" +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking_introduction.xml:166(link) +msgid "http://www.midokura.com/" +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking_introduction.xml:169(emphasis) +msgid "ML2 (Modular Layer 2) Plug-in" +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking_introduction.xml:173(link) +msgid "https://wiki.openstack.org/wiki/Neutron/ML2" +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking_introduction.xml:176(emphasis) +msgid "NEC OpenFlow Plug-in" +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking_introduction.xml:180(link) +msgid "http://wiki.openstack.org/Quantum-NEC-OpenFlow-Plugin" +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking_introduction.xml:183(emphasis) +msgid "Nicira NVP Plug-in" +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking_introduction.xml:188(link) +msgid "NVP Product Overview" +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking_introduction.xml:190(link) +msgid "NVP Product Support" +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking_introduction.xml:185(td) +msgid "Documentation included in this guide as well as in , " +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking_introduction.xml:193(emphasis) +msgid "Open vSwitch Plug-in" +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking_introduction.xml:195(td) +msgid "Documentation included in this guide." +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking_introduction.xml:199(emphasis) +msgid "PLUMgrid" +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking_introduction.xml:203(link) +msgid "https://https://wiki.openstack.org/wiki/PLUMgrid-Neutron" +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking_introduction.xml:200(td) ./doc/admin-guide-cloud/section_networking_introduction.xml:208(td) +msgid "Documentation included in this guide as well as in " +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking_introduction.xml:206(emphasis) +msgid "Ryu Plug-in" +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking_introduction.xml:211(link) +msgid "https://github.com/osrg/ryu/wiki/OpenStack" +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking_introduction.xml:215(para) +msgid "Plug-ins can have different properties for hardware requirements, features, performance, scale, or operator tools. Because Networking supports a large number of plug-ins, the cloud administrator can weigh options to decide on the right networking technology for the deployment." +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking_introduction.xml:221(para) +msgid "In the Havana release, OpenStack Networking provides the Modular Layer 2 (ML2) plug-in that can concurrently use multiple layer 2 networking technologies that are found in real-world data centers. It currently works with the existing Open vSwitch, Linux Bridge, and Hyper-v L2 agents. The ML2 framework simplifies the addition of support for new L2 technologies and reduces the effort that is required to add and maintain them compared to monolithic plug-ins." +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking_introduction.xml:232(title) +msgid "Plug-in deprecation notice:" +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking_introduction.xml:233(para) +msgid "The Open vSwitch and Linux Bridge plug-ins are deprecated in the Havana release and will be removed in the Icehouse release. All features have been ported to the ML2 plug-in in the form of mechanism drivers. ML2 currently provides Linux Bridge, Open vSwitch and Hyper-v mechanism drivers." +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking_introduction.xml:241(para) +msgid "Not all Networking plug-ins are compatible with all possible Compute drivers:" +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking_introduction.xml:244(caption) +msgid "Plug-in compatibility with Compute drivers" +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking_introduction.xml:249(th) +msgid "Libvirt (KVM/QEMU)" +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking_introduction.xml:250(th) +msgid "XenServer" +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking_introduction.xml:251(th) +msgid "VMware" +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking_introduction.xml:252(th) ./doc/admin-guide-cloud/ch_compute.xml:47(link) +msgid "Hyper-V" +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking_introduction.xml:253(th) +msgid "Bare-metal" +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking_introduction.xml:258(td) +msgid "Big Switch / Floodlight" +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking_introduction.xml:259(td) ./doc/admin-guide-cloud/section_networking_introduction.xml:267(td) ./doc/admin-guide-cloud/section_networking_introduction.xml:275(td) ./doc/admin-guide-cloud/section_networking_introduction.xml:286(td) ./doc/admin-guide-cloud/section_networking_introduction.xml:291(td) ./doc/admin-guide-cloud/section_networking_introduction.xml:299(td) ./doc/admin-guide-cloud/section_networking_introduction.xml:307(td) ./doc/admin-guide-cloud/section_networking_introduction.xml:315(td) ./doc/admin-guide-cloud/section_networking_introduction.xml:318(td) ./doc/admin-guide-cloud/section_networking_introduction.xml:323(td) ./doc/admin-guide-cloud/section_networking_introduction.xml:331(td) ./doc/admin-guide-cloud/section_networking_introduction.xml:332(td) ./doc/admin-guide-cloud/section_networking_introduction.xml:333(td) ./doc/admin-guide-cloud/section_networking_introduction.xml:339(td) ./doc/admin-guide-cloud/section_networking_introduction.xml:347(td) ./doc/admin-guide-cloud/section_networking_introduction.xml:349(td) ./doc/admin-guide-cloud/section_networking_introduction.xml:355(td) ./doc/admin-guide-cloud/section_networking_adv_features.xml:1908(td) ./doc/admin-guide-cloud/section_networking_adv_features.xml:1917(td) ./doc/admin-guide-cloud/section_networking_adv_features.xml:1926(td) +msgid "Yes" +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking_introduction.xml:266(td) +msgid "Brocade" +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking_introduction.xml:282(td) +msgid "Cloudbase Hyper-V" +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking_introduction.xml:290(td) ./doc/admin-guide-cloud/section_networking-adv-config.xml:102(emphasis) ./doc/admin-guide-cloud/section_networking_pagination_and_sorting_support.xml:29(td) ./doc/admin-guide-cloud/section_networking-scenarios.xml:378(title) +msgid "Linux Bridge" +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking_introduction.xml:298(td) +msgid "Mellanox" +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking_introduction.xml:306(td) +msgid "Midonet" +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking_introduction.xml:314(td) ./doc/admin-guide-cloud/section_networking_pagination_and_sorting_support.xml:19(td) ./doc/admin-guide-cloud/section_networking-scenarios.xml:581(title) +msgid "ML2" +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking_introduction.xml:322(td) +msgid "NEC OpenFlow" +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking_introduction.xml:330(td) +msgid "Nicira NVP" +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking_introduction.xml:338(td) ./doc/admin-guide-cloud/section_networking-adv-config.xml:79(emphasis) ./doc/admin-guide-cloud/section_networking_pagination_and_sorting_support.xml:24(td) ./doc/admin-guide-cloud/section_networking-scenarios.xml:11(title) +msgid "Open vSwitch" +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking_introduction.xml:346(td) +msgid "Plumgrid" +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking_introduction.xml:354(td) +msgid "Ryu" +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking_introduction.xml:364(title) +msgid "Plug-in configurations" +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking_introduction.xml:365(para) +msgid "For configurations options, see Networking configuration options in Configuration Reference. These sections explain how to configure specific plug-ins." +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking_introduction.xml:372(title) +msgid "Configure Big Switch, Floodlight REST Proxy plug-in" +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking_introduction.xml:375(title) +msgid "To use the REST Proxy plug-in with OpenStack Networking" +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking_introduction.xml:378(para) ./doc/admin-guide-cloud/section_networking_introduction.xml:531(para) ./doc/admin-guide-cloud/section_networking_introduction.xml:695(para) ./doc/admin-guide-cloud/section_networking_introduction.xml:738(para) +msgid "Edit /etc/neutron/neutron.conf and set:" +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking_introduction.xml:384(para) +msgid "Edit the plug-in configuration file, /etc/neutron/plugins/bigswitch/restproxy.ini, and specify a comma-separated list of controller_ip:port pairs: For database configuration, see Install Networking Services in any of the Installation Guides in the OpenStack Documentation index. (The link defaults to the Ubuntu version.)" +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking_introduction.xml:401(para) ./doc/admin-guide-cloud/section_networking_introduction.xml:601(para) ./doc/admin-guide-cloud/section_networking_introduction.xml:799(para) +msgid "To apply the new settings, restart neutron-server:" +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking_introduction.xml:410(title) +msgid "Configure Brocade plug-in" +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking_introduction.xml:412(title) +msgid "To use the Brocade plug-in with OpenStack Networking" +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking_introduction.xml:415(para) +msgid "Install the Brocade modified Python netconf client (ncclient) library which is available at https://github.com/brocade/ncclient: " +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking_introduction.xml:424(para) +msgid "Edit the /etc/neutron/neutron.conf file and set the following option:" +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking_introduction.xml:430(para) +msgid "Edit the /etc/neutron/plugins/brocade/brocade.ini configuration file for the Brocade plug-in and specify the admin user name, password, and IP address of the Brocade switch:" +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking_introduction.xml:437(replaceable) ./doc/admin-guide-cloud/section_networking_introduction.xml:658(replaceable) ./doc/admin-guide-cloud/section_networking_introduction.xml:659(replaceable) ./doc/admin-guide-cloud/section_networking_introduction.xml:670(replaceable) +msgid "admin" +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking_introduction.xml:438(replaceable) +msgid "password" +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking_introduction.xml:439(replaceable) +msgid "switch mgmt ip address" +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking_introduction.xml:441(para) +msgid "For database configuration, see Install Networking Services in any of the Installation Guides in the OpenStack Documentation index. (The link defaults to the Ubuntu version.)" +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking_introduction.xml:453(para) +msgid "To apply the new settings, restart the neutron-server service:" +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking_introduction.xml:463(title) +msgid "Configure OVS plug-in" +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking_introduction.xml:464(para) +msgid "If you use the Open vSwitch (OVS) plug-in in a deployment with multiple hosts, you will need to use either tunneling or vlans to isolate traffic from multiple networks. Tunneling is easier to deploy because it does not require configuring VLANs on network switches." +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking_introduction.xml:471(para) +msgid "This procedure uses tunneling:" +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking_introduction.xml:473(title) +msgid "To configure OpenStack Networking to use the OVS plug-in" +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking_introduction.xml:476(para) +msgid "Edit /etc/neutron/plugins/openvswitch/ovs_neutron_plugin.ini to specify these values (for database configuration, see Install Networking Services in Installation Guide):" +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking_introduction.xml:491(para) +msgid "If you use the neutron DHCP agent, add these lines to the /etc/neutron/dhcp_agent.ini file:" +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking_introduction.xml:498(para) +msgid "Create /etc/neutron/dnsmasq-neutron.conf, and add these values to lower the MTU size on instances and prevent packet fragmentation over the GRE tunnel:" +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking_introduction.xml:507(para) +msgid "After performing that change on the node running neutron-server, restart neutron-server to apply the new settings:" +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking_introduction.xml:519(title) +msgid "Configure Nicira NVP plug-in" +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking_introduction.xml:521(title) +msgid "To configure OpenStack Networking to use the NVP plug-in" +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking_introduction.xml:523(para) +msgid "While the instructions in this section refer to the Nicira NVP platform, they also apply to VMware NSX." +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking_introduction.xml:526(para) +msgid "Install the NVP plug-in, as follows:" +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking_introduction.xml:535(para) +msgid "Example neutron.conf file for NVP:" +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking_introduction.xml:552(para) +msgid "A set of parameters need to establish and configure the connection with the controller cluster. Such parameters include NVP API endpoints, access credentials, and settings for HTTP redirects and retries in case of connection failures" +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking_introduction.xml:564(para) +msgid "In order to ensure correct operations nvp_user shoud be a user with administrator credentials on the NVP platform." +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking_introduction.xml:567(para) +msgid "A controller API endpoint consists of the controller's IP address and port; if the port is omitted, port 443 will be used. If multiple API endpoints are specified, it is up to the user to ensure that all these endpoints belong to the same controller cluster; The Openstack Networking Nicira NVP plugin does not perform this check, and results might be unpredictable." +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking_introduction.xml:575(para) +msgid "When multiple API endpoints are specified, the plugin will load balance requests on the various API endpoints." +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking_introduction.xml:580(para) +msgid "The UUID of the NVP Transport Zone that should be used by default when a tenant creates a network. This value can be retrieved from the NVP Manager's Transport Zones page:" +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking_introduction.xml:589(para) +msgid "Ubuntu packaging currently does not update the neutron init script to point to the NVP configuration file. Instead, you must manually update /etc/default/neutron-server with the following:" +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking_introduction.xml:543(para) +msgid "To configure the NVP controller cluster for the Openstack Networking Service, locate the [default] section in the /etc/neutron/plugins/nicira/nvp.ini file, and add the following entries (for database configuration, see Install Networking Services in Installation Guide): " +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking_introduction.xml:607(para) +msgid "Example nvp.ini file:" +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking_introduction.xml:616(para) +msgid "To debug nvp.ini configuration issues, run this command from the host that runs neutron-server:" +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking_introduction.xml:622(para) +msgid "This command tests whether neutron-server can log into all of the NVP Controllers and the SQL server, and whether all UUID values are correct." +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking_introduction.xml:630(title) +msgid "Loadbalancer-as-a-Service and Firewall-as-a-Service" +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking_introduction.xml:631(para) +msgid "The NVP LBaaS and FWaaS services use the standard OpenStack API with the exception of requiring routed-insertion extension support." +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking_introduction.xml:632(para) +msgid "Below are the main differences between the NVP implementation and the community reference implementation of these services:" +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking_introduction.xml:635(para) +msgid "The NVP LBaaS and FWaaS plugins require the routed-insertion extension, which adds the router_id attribute to the VIP (Virtual IP address) and firewall resources and binds these services to a logical router." +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking_introduction.xml:638(para) +msgid "The community reference implementation of LBaaS only supports a one-arm model, which restricts the VIP to be on the same subnet as the backend servers. The NVP LBaaS plugin only supports a two-arm model between north-south traffic, meaning that the VIP can only be created on the external (physical) network." +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking_introduction.xml:641(para) +msgid "The community reference implementation of FWaaS applies firewall rules to all logical routers in a tenant, while the NVP FWaaS plugin applies firewall rules only to one logical router according to the router_id of the firewall entity." +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking_introduction.xml:645(title) +msgid "To configure Loadbalancer-as-a-Service and Firewall-as-a-Service with NVP:" +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking_introduction.xml:647(para) +msgid "Edit /etc/neutron/neutron.conf file:" +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking_introduction.xml:653(para) +msgid "Edit /etc/neutron/plugins/nicira/nvp.ini file:" +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking_introduction.xml:654(para) +msgid "In addition to the original NVP configuration, the default_l3_gw_service_uuid is required for the NVP Advanced Plugin and a vcns section must be added as shown below." +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking_introduction.xml:660(replaceable) +msgid "10.37.1.137:443" +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking_introduction.xml:661(replaceable) +msgid "aae63e9b-2e4e-4efe-81a1-92cf32e308bf" +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking_introduction.xml:662(replaceable) +msgid "2702f27a-869a-49d1-8781-09331a0f6b9e" +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking_introduction.xml:667(replaceable) +msgid "https://10.24.106.219" +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking_introduction.xml:673(replaceable) ./doc/admin-guide-cloud/section_networking_adv_features.xml:1535(td) +msgid "default" +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking_introduction.xml:676(replaceable) +msgid "f2c023cf-76e2-4625-869b-d0dabcfcc638" +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking_introduction.xml:690(title) +msgid "Configure PLUMgrid plug-in" +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking_introduction.xml:692(title) +msgid "To use the PLUMgrid plug-in with OpenStack Networking" +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking_introduction.xml:701(para) +msgid "Edit /etc/neutron/plugins/plumgrid/plumgrid.ini under the [PLUMgridDirector] section, and specify the IP address, port, admin user name, and password of the PLUMgrid Director: For database configuration, see Install Networking Services in Installation Guide." +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking_introduction.xml:720(para) +msgid "To apply the settings, restart neutron-server:" +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking_introduction.xml:728(title) +msgid "Configure Ryu plug-in" +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking_introduction.xml:730(title) +msgid "To use the Ryu plug-in with OpenStack Networking" +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking_introduction.xml:733(para) +msgid "Install the Ryu plug-in, as follows:" +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking_introduction.xml:756(para) +msgid "The openflow_rest_api is used to tell where Ryu is listening for REST API. Substitute ip-address and port-no based on your Ryu setup." +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking_introduction.xml:766(para) +msgid "The ovsdb_interface is used for Ryu to access the ovsdb-server. Substitute eth0 based on your set up. The IP address is derived from the interface name. If you want to change this value irrespective of the interface name, ovsdb_ip can be specified. If you use a non-default port for ovsdb-server, it can be specified by ovsdb_port." +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking_introduction.xml:783(para) +msgid "tunnel_interface needs to be set to tell what IP address is used for tunneling (if tunneling isn't used, this value is ignored). The IP address is derived from the network interface name." +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking_introduction.xml:744(para) +msgid "Edit /etc/neutron/plugins/ryu/ryu.ini (for database configuration, see Install Networking Services in Installation Guide), and update the following in the [ovs] section for the ryu-neutron-agent: " +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking_introduction.xml:792(para) +msgid "You can use the same configuration file for many Compute nodes by using a network interface name with a different IP address:" +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking_introduction.xml:809(title) +msgid "Configure neutron agents" +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking_introduction.xml:810(para) +msgid "Plug-ins typically have requirements for particular software that must be run on each node that handles data packets. This includes any node that runs nova-compute and nodes that run dedicated OpenStack Networking service agents such as, neutron-dhcp-agent, neutron-l3-agent, or neutron-lbaas-agent (see below for more information about individual service agents)." +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking_introduction.xml:821(para) +msgid "A data-forwarding node typically has a network interface with an IP address on the “management network” and another interface on the “data network”." +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking_introduction.xml:825(para) +msgid "This section shows you how to install and configure a subset of the available plug-ins, which may include the installation of switching software (for example, Open vSwitch) as well as agents used to communicate with the neutron-server process running elsewhere in the data center." +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking_introduction.xml:833(title) +msgid "Configure data-forwarding nodes" +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking_introduction.xml:835(title) +msgid "Node set up: OVS plug-in" +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking_introduction.xml:838(para) +msgid "This section also applies to the ML2 plugin when Open vSwitch is used as a mechanism driver." +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking_introduction.xml:836(para) +msgid "If you use the Open vSwitch plug-in, you must install Open vSwitch and the neutron-plugin-openvswitch-agent agent on each data-forwarding node:" +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking_introduction.xml:844(para) +msgid "Do not install the openvswitch-brcompat package as it breaks the security groups functionality." +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking_introduction.xml:849(title) +msgid "To set up each node for the OVS plug-in" +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking_introduction.xml:852(para) +msgid "Install the OVS agent package (this pulls in the Open vSwitch software as a dependency):" +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking_introduction.xml:858(para) +msgid "On each node that runs the neutron-plugin-openvswitch-agent:" +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking_introduction.xml:862(para) +msgid "Replicate the ovs_neutron_plugin.ini file created in the first step onto the node." +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking_introduction.xml:868(para) +msgid "If using tunneling, the node's ovs_neutron_plugin.ini file must also be updated with the node's IP address configured on the data network using the local_ip value." +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking_introduction.xml:880(para) ./doc/admin-guide-cloud/section_networking_introduction.xml:984(para) +msgid "Restart Open vSwitch to properly load the kernel module:" +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking_introduction.xml:885(para) ./doc/admin-guide-cloud/section_networking_introduction.xml:989(para) +msgid "Restart the agent:" +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking_introduction.xml:889(para) +msgid "All nodes that run neutron-plugin-openvswitch-agent must have an OVS br-int bridge. . To create the bridge, run:" +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking_introduction.xml:899(title) +msgid "Node set up: Nicira NVP plug-in" +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking_introduction.xml:900(para) +msgid "If you use the Nicira NVP plug-in, you must also install Open vSwitch on each data-forwarding node. However, you do not need to install an additional agent on each node." +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking_introduction.xml:906(para) +msgid "It is critical that you are running an Open vSwitch version that is compatible with the current version of the NVP Controller software. Do not use the Open vSwitch version that is installed by default on Ubuntu. Instead, use the Open Vswitch version that is provided on the Nicira support portal for your NVP Controller version." +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking_introduction.xml:917(title) +msgid "To set up each node for the Nicira NVP plug-in" +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking_introduction.xml:920(para) +msgid "Ensure each data-forwarding node has an IP address on the \"management network,\" and an IP address on the \"data network\" that is used for tunneling data traffic. For full details on configuring your forwarding node, see the NVP Administrator Guide." +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking_introduction.xml:931(para) +msgid "Use the NVP Administrator Guide to add the node as a \"Hypervisor\" using the NVP Manager GUI. Even if your forwarding node has no VMs and is only used for services agents like neutron-dhcp-agent or neutron-lbaas-agent, it should still be added to NVP as a Hypervisor." +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking_introduction.xml:944(para) +msgid "After following the NVP Administrator Guide, use the page for this Hypervisor in the NVP Manager GUI to confirm that the node is properly connected to the NVP Controller Cluster and that the NVP Controller Cluster can see the br-int integration bridge." +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking_introduction.xml:957(title) +msgid "Node set up: Ryu plug-in" +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking_introduction.xml:958(para) +msgid "If you use the Ryu plug-in, you must install both Open vSwitch and Ryu, in addition to the Ryu agent package:" +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking_introduction.xml:962(title) +msgid "To set up each node for the Ryu plug-in" +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking_introduction.xml:965(para) +msgid "Install Ryu (there isn't currently an Ryu package for ubuntu):" +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking_introduction.xml:970(para) +msgid "Install the Ryu agent and Open vSwitch packages:" +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking_introduction.xml:975(para) +msgid "Replicate the ovs_ryu_plugin.ini and neutron.conf files created in the above step on all nodes running neutron-plugin-ryu-agent." +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking_introduction.xml:993(para) +msgid "All nodes running neutron-plugin-ryu-agent also require that an OVS bridge named \"br-int\" exists on each node. To create the bridge, run:" +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking_introduction.xml:1004(title) +msgid "Configure DHCP agent" +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking_introduction.xml:1005(para) +msgid "The DHCP service agent is compatible with all existing plug-ins and is required for all deployments where VMs should automatically receive IP addresses through DHCP." +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking_introduction.xml:1010(title) +msgid "To install and configure the DHCP agent" +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking_introduction.xml:1013(para) +msgid "You must configure the host running the neutron-dhcp-agent as a \"data forwarding node\" according to the requirements for your plug-in (see )." +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking_introduction.xml:1021(para) +msgid "Install the DHCP agent:" +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking_introduction.xml:1025(para) +msgid "Finally, update any options in the /etc/neutron/dhcp_agent.ini file that depend on the plug-in in use (see the sub-sections)." +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking_introduction.xml:1032(para) +msgid "If you reboot a node that runs the DHCP agent, you must run the command before the neutron-dhcp-agent service starts." +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking_introduction.xml:1036(para) +msgid "On Red Hat-based systems, the neutron-ovs-cleanup service runs the command automatically. However, on Debian-based systems such as Ubuntu, you must manually run this command or write your own system script that runs on boot before the neutron-dhcp-agent service starts." +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking_introduction.xml:1046(title) +msgid "DHCP agent setup: OVS plug-in" +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking_introduction.xml:1047(para) +msgid "These DHCP agent options are required in the /etc/neutron/dhcp_agent.ini file for the OVS plug-in:" +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking_introduction.xml:1057(title) +msgid "DHCP agent setup: NVP plug-in" +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking_introduction.xml:1058(para) +msgid "These DHCP agent options are required in the /etc/neutron/dhcp_agent.ini file for the NVP plug-in:" +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking_introduction.xml:1069(title) +msgid "DHCP agent setup: Ryu plug-in" +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking_introduction.xml:1070(para) +msgid "These DHCP agent options are required in the /etc/neutron/dhcp_agent.ini file for the Ryu plug-in:" +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking_introduction.xml:1080(title) +msgid "Configure L3 agent" +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking_introduction.xml:1081(para) +msgid "The OpenStack Networking Service has a widely used API extension to allow administrators and tenants to create routers to interconnect L2 networks, and floating IPs to make ports on private networks publicly accessible." +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking_introduction.xml:1086(para) +msgid "Many plug-ins rely on the L3 service agent to implement the L3 functionality. However, the following plug-ins already have built-in L3 capabilities:" +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking_introduction.xml:1093(para) +msgid "Nicira NVP plug-in" +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking_introduction.xml:1096(para) +msgid "Big Switch/Floodlight plug-in, which supports both the open source Floodlight controller and the proprietary Big Switch controller." +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking_introduction.xml:1103(para) +msgid "Only the proprietary BigSwitch controller implements L3 functionality. When using Floodlight as your OpenFlow controller, L3 functionality is not available." +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking_introduction.xml:1112(para) +msgid "PLUMgrid plug-in" +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking_introduction.xml:1116(para) +msgid "Do not configure or use neutron-l3-agent if you use one of these plug-ins." +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking_introduction.xml:1121(title) +msgid "To install the L3 agent for all other plug-ins" +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking_introduction.xml:1124(para) +msgid "Install the neutron-l3-agent binary on the network node:" +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking_introduction.xml:1130(para) +msgid "To uplink the node that runs neutron-l3-agent to the external network, create a bridge named \"br-ex\" and attach the NIC for the external network to this bridge." +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking_introduction.xml:1136(para) +msgid "For example, with Open vSwitch and NIC eth1 connected to the external network, run:" +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking_introduction.xml:1141(para) +msgid "Do not manually configure an IP address on the NIC connected to the external network for the node running neutron-l3-agent. Rather, you must have a range of IP addresses from the external network that can be used by OpenStack Networking for routers that uplink to the external network. This range must be large enough to have an IP address for each router in the deployment, as well as each floating IP." +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking_introduction.xml:1155(para) +msgid "The neutron-l3-agent uses the Linux IP stack and iptables to perform L3 forwarding and NAT. In order to support multiple routers with potentially overlapping IP addresses, neutron-l3-agent defaults to using Linux network namespaces to provide isolated forwarding contexts. As a result, the IP addresses of routers will not be visible simply by running or on the node. Similarly, you will not be able to directly fixed IPs." +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking_introduction.xml:1172(para) +msgid "To do either of these things, you must run the command within a particular router's network namespace. The namespace will have the name \"qrouter-<UUID of the router>. These example commands run in the router namespace with UUID 47af3868-0fa8-4447-85f6-1304de32153b:" +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking_introduction.xml:1186(para) +msgid "If you reboot a node that runs the L3 agent, you must run the command before the neutron-l3-agent service starts." +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking_introduction.xml:1189(para) +msgid "On Red Hat-based systems, the neutron-ovs-cleanup service runs the command automatically. However, on Debian-based systems such as Ubuntu, you must manually run this command or write your own system script that runs on boot before the neutron-l3-agent service starts." +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking_introduction.xml:1199(title) +msgid "Configure LBaaS agent" +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking_introduction.xml:1200(para) +msgid "Starting with the Havana release, the Neutron Load-Balancer-as-a-Service (LBaaS) supports an agent scheduling mechanism, so several neutron-lbaas-agents can be run on several nodes (one per one)." +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking_introduction.xml:1206(title) +msgid "To install the LBaas agent and configure the node" +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking_introduction.xml:1209(para) +msgid "Install the agent by running:" +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking_introduction.xml:1215(para) +msgid "An OVS-based plug-in (OVS, NVP, Ryu, NEC, BigSwitch/Floodlight), you must set:" +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking_introduction.xml:1222(para) +msgid "A plug-in that uses LinuxBridge, you must set:" +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking_introduction.xml:1213(para) +msgid "If you are using: " +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking_introduction.xml:1229(para) +msgid "To use the reference implementation, you must also set:" +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking_introduction.xml:1234(para) ./doc/admin-guide-cloud/section_networking_introduction.xml:1255(para) +msgid "Set this parameter in the neutron.conf file on the host that runs neutron-server:" +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking_introduction.xml:1244(title) +msgid "Configure FWaaS agent" +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking_introduction.xml:1245(para) +msgid "The Firewall-as-a-Service (FWaaS) agent is co-located with the Neutron L3 agent and does not require any additional packages apart from those required for the Neutron L3 agent. You can enable the FWaaS functionality by setting the configuration, as follows." +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking_introduction.xml:1252(title) +msgid "To configure FWaaS service and agent" +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking_introduction.xml:1263(para) +msgid "To use the reference implementation, you must also add a FWaaS driver configuration to the neutron.conf file on every node where the Neutron L3 agent is deployed:" +msgstr "" + +#: ./doc/admin-guide-cloud/ch_identity_mgmt.xml:7(title) +msgid "Identity management" +msgstr "" + +#: ./doc/admin-guide-cloud/ch_identity_mgmt.xml:8(para) +msgid "The OpenStack Identity Service, code-named Keystone, is the default identity management system for OpenStack. After you install the Identity Service, you configure it through the etc/keystone.conf configuration file and, possibly, a separate logging configuration file. You initialize data into the Identity Service by using the command-line client." +msgstr "" + +#: ./doc/admin-guide-cloud/ch_identity_mgmt.xml:16(title) +msgid "Identity Service concepts" +msgstr "" + +#: ./doc/admin-guide-cloud/ch_identity_mgmt.xml:32(title) +msgid "User CRUD" +msgstr "" + +#: ./doc/admin-guide-cloud/ch_identity_mgmt.xml:33(para) +msgid "The Identity Service provides a user CRUD filter that can be added to the public_api pipeline. This user CRUD filter enables users to use a HTTP PATCH to change their own password. To enable this extension you should define a user_crud_extension filter, insert it after the *_body middleware and before the public_service application in the public_api WSGI pipeline in keystone.conf. For example:" +msgstr "" + +#: ./doc/admin-guide-cloud/ch_identity_mgmt.xml:47(para) +msgid "Each user can then change their own password with a HTTP PATCH:" +msgstr "" + +#: ./doc/admin-guide-cloud/ch_identity_mgmt.xml:50(para) +msgid "In addition to changing their password, all of the user's current tokens are deleted (if the back-end is KVS or sql)." +msgstr "" + +#: ./doc/admin-guide-cloud/ch_identity_mgmt.xml:52(para) +msgid "Only use a KVS backend for tokens when testing." +msgstr "" + +#: ./doc/admin-guide-cloud/ch_identity_mgmt.xml:55(title) +msgid "Logging" +msgstr "" + +#: ./doc/admin-guide-cloud/ch_identity_mgmt.xml:56(para) +msgid "You configure logging externally to the rest of the Identity Service. The file specifying the logging configuration is in the [DEFAULT] section of the keystone.conf file under log_config. To route logging through syslog, set use_syslog=true option in the [DEFAULT] section." +msgstr "" + +#: ./doc/admin-guide-cloud/ch_identity_mgmt.xml:63(para) +msgid "A sample logging file is available with the project in the etc/logging.conf.sample directory. Like other OpenStack projects, the Identity Service uses the Python logging module, which includes extensive configuration options that let you define the output levels and formats." +msgstr "" + +#: ./doc/admin-guide-cloud/ch_identity_mgmt.xml:68(para) +msgid "Review the etc/keystone.conf sample configuration files that are distributed with the Identity Service. For example, each server application has its own configuration file." +msgstr "" + +#: ./doc/admin-guide-cloud/ch_identity_mgmt.xml:72(para) +msgid "For services that have separate paste-deploy .ini files, you can configure auth_token middleware in the [keystone_authtoken] section in the main configuration file, such as nova.conf. For example in Compute, you can remove the middleware parameters from api-paste.ini, as follows:" +msgstr "" + +#: ./doc/admin-guide-cloud/ch_identity_mgmt.xml:82(para) +msgid "Set these values in the nova.conf file:" +msgstr "" + +#: ./doc/admin-guide-cloud/ch_identity_mgmt.xml:97(para) +msgid "Middleware parameters in paste config take priority. You must remove them to use values in the [keystone_authtoken] section." +msgstr "" + +#: ./doc/admin-guide-cloud/ch_identity_mgmt.xml:103(title) +msgid "Monitoring" +msgstr "" + +#: ./doc/admin-guide-cloud/ch_identity_mgmt.xml:104(para) +msgid "The Identity Service provides some basic request/response monitoring statistics out of the box." +msgstr "" + +#: ./doc/admin-guide-cloud/ch_identity_mgmt.xml:106(para) +msgid "Enable data collection by defining a stats_monitoring filter and including it at the beginning of any desired WSGI pipelines:" +msgstr "" + +#: ./doc/admin-guide-cloud/ch_identity_mgmt.xml:114(para) +msgid "Enable the reporting of collected data by defining a stats_reporting filter and including it near the end of your admin_api WSGI pipeline (After *_body middleware and before *_extension filters is recommended):" +msgstr "" + +#: ./doc/admin-guide-cloud/ch_identity_mgmt.xml:124(para) +msgid "Query the admin API for statistics using:" +msgstr "" + +#: ./doc/admin-guide-cloud/ch_identity_mgmt.xml:126(para) +msgid "Reset collected data using:" +msgstr "" + +#: ./doc/admin-guide-cloud/ch_identity_mgmt.xml:131(title) +msgid "Start the Identity Service" +msgstr "" + +#: ./doc/admin-guide-cloud/ch_identity_mgmt.xml:132(para) +msgid "To start the services for the Identity Service, run the following command:" +msgstr "" + +#: ./doc/admin-guide-cloud/ch_identity_mgmt.xml:135(para) +msgid "This command starts two wsgi.Server instances configured by the keystone.conf file as described previously. One of these wsgi servers is admin (the administration API) and the other is main (the primary/public API interface). Both run in a single process." +msgstr "" + +#: ./doc/admin-guide-cloud/ch_identity_mgmt.xml:143(title) +msgid "Example usage" +msgstr "" + +#: ./doc/admin-guide-cloud/ch_identity_mgmt.xml:144(para) +msgid "The keystone client is set up to expect commands in the general form of keystonecommandargument, followed by flag-like keyword arguments to provide additional (often optional) information. For example, the command user-list and tenant-create can be invoked as follows:" +msgstr "" + +#: ./doc/admin-guide-cloud/ch_identity_mgmt.xml:174(title) +msgid "Authentication middleware with user name and password" +msgstr "" + +#: ./doc/admin-guide-cloud/ch_identity_mgmt.xml:176(para) +msgid "You can also configure the Identity Service authentication middleware using the and options. When using the and options the parameter is optional. If is specified, it is used only if the specified token is still valid." +msgstr "" + +#: ./doc/admin-guide-cloud/ch_identity_mgmt.xml:184(para) +msgid "For services that have a separate paste-deploy .ini file, you can configure the authentication middleware in the [keystone_authtoken] section of the main configuration file, such as nova.conf. In Compute, for example, you can remove the middleware parameters from api-paste.ini, as follows:" +msgstr "" + +#: ./doc/admin-guide-cloud/ch_identity_mgmt.xml:193(para) +msgid "And set the following values in nova.conf as follows:" +msgstr "" + +#: ./doc/admin-guide-cloud/ch_identity_mgmt.xml:208(para) +msgid "The middleware parameters in the paste config take priority. You must remove them to use the values in the [keystone_authtoken] section." +msgstr "" + +#: ./doc/admin-guide-cloud/ch_identity_mgmt.xml:212(para) +msgid "This sample paste config filter makes use of the and options:" +msgstr "" + +#: ./doc/admin-guide-cloud/ch_identity_mgmt.xml:225(para) +msgid "Using this option requires an admin tenant/role relationship. The admin user is granted access to the admin role on the admin tenant." +msgstr "" + +#: ./doc/admin-guide-cloud/section_ts_failed_sched_create_vol.xml:4(title) +msgid "Failed to schedule and create volume" +msgstr "" + +#: ./doc/admin-guide-cloud/section_ts_failed_sched_create_vol.xml:6(title) ./doc/admin-guide-cloud/section_ts_failed_connect_vol_FC_SAN.xml:6(title) ./doc/admin-guide-cloud/section_ts_vol_attach_miss_sg_scan.xml:10(title) ./doc/admin-guide-cloud/section_ts_failed_attach_vol_after_detach.xml:8(title) ./doc/admin-guide-cloud/section_ts_non_existent_host.xml:6(title) ./doc/admin-guide-cloud/section_ts_no_emulator_x86_64.xml:6(title) ./doc/admin-guide-cloud/section_ts_HTTP_bad_req_in_cinder_vol_log.xml:8(title) ./doc/admin-guide-cloud/section_ts_non_existent_vlun.xml:6(title) ./doc/admin-guide-cloud/section_ts_failed_attach_vol_no_sysfsutils.xml:6(title) ./doc/admin-guide-cloud/section_ts_multipath_warn.xml:8(title) ./doc/admin-guide-cloud/section_ts_attach_vol_fail_not_JSON.xml:7(title) ./doc/admin-guide-cloud/section_ts_duplicate_3par_host.xml:6(title) +msgid "Problem" +msgstr "" + +#: ./doc/admin-guide-cloud/section_ts_failed_sched_create_vol.xml:7(para) +msgid "The following warning is seen in the cinder-scheduler.log when volume type and extra specs are defined and the volume is in an error state." +msgstr "" + +#: ./doc/admin-guide-cloud/section_ts_failed_sched_create_vol.xml:14(title) ./doc/admin-guide-cloud/section_ts_failed_connect_vol_FC_SAN.xml:15(title) ./doc/admin-guide-cloud/section_ts_vol_attach_miss_sg_scan.xml:24(title) ./doc/admin-guide-cloud/section_ts_failed_attach_vol_after_detach.xml:14(title) ./doc/admin-guide-cloud/section_ts_non_existent_host.xml:14(title) ./doc/admin-guide-cloud/section_ts_no_emulator_x86_64.xml:11(title) ./doc/admin-guide-cloud/section_ts_HTTP_bad_req_in_cinder_vol_log.xml:43(title) ./doc/admin-guide-cloud/section_ts_non_existent_vlun.xml:12(title) ./doc/admin-guide-cloud/section_ts_failed_attach_vol_no_sysfsutils.xml:15(title) ./doc/admin-guide-cloud/section_ts_multipath_warn.xml:20(title) ./doc/admin-guide-cloud/section_ts_attach_vol_fail_not_JSON.xml:15(title) ./doc/admin-guide-cloud/section_ts_duplicate_3par_host.xml:12(title) +msgid "Solution" +msgstr "" + +#: ./doc/admin-guide-cloud/section_ts_failed_sched_create_vol.xml:15(para) +msgid "Enable the option scheduler_driver=cinder.scheduler.simple.SimpleScheduler in the /etc/cinder/cinder.conf file and restart the cinder-scheduler service. The scheduler_driver defaults to cinder.scheduler.filter_scheduler.FilterScheduler." +msgstr "" + +#. When image changes, this message will be marked fuzzy or untranslated for you. +#. It doesn't matter what you translate it to: it's not used at all. +#: ./doc/admin-guide-cloud/section_networking-multi-dhcp-agents.xml:32(None) +msgid "@@image: '../common/figures/demo_multiple_dhcp_agents.png'; md5=7e9abc4226d6b6cb9a6a3b3ec7435805" +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking-multi-dhcp-agents.xml:6(title) +msgid "Scalable and highly available DHCP agents" +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking-multi-dhcp-agents.xml:7(para) +msgid "This section describes how to use the agent management (alias agent) and scheduler (alias agent_scheduler) extensions for DHCP agents scalability and HA." +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking-multi-dhcp-agents.xml:11(para) +msgid "Use the client command to check if these extensions are enabled: " +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking-multi-dhcp-agents.xml:47(para) +msgid "Runs the Neutron, Keystone, and Nova services that are required to deploy VMs. The node must have at least one network interface that is connected to the Management Network." +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking-multi-dhcp-agents.xml:52(para) +msgid "Note that nova-network should not be running because it is replaced by Neutron." +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking-multi-dhcp-agents.xml:35(para) +msgid "There will be three hosts in the setup.
Hosts for demo
HostDescription
OpenStack Controller host - controlnode
HostARuns Nova compute, the Neutron L2 agent and DHCP agent
HostBSame as HostA
" +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking-multi-dhcp-agents.xml:71(title) ./doc/admin-guide-cloud/section_networking-scenarios.xml:15(title) ./doc/admin-guide-cloud/section_networking-scenarios.xml:383(title) ./doc/admin-guide-cloud/section_networking-config-identity.xml:146(th) ./doc/admin-guide-cloud/section_networking-config-identity.xml:221(td) ./doc/admin-guide-cloud/section_networking-config-identity.xml:256(td) +msgid "Configuration" +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking-multi-dhcp-agents.xml:73(title) +msgid "controlnode—Neutron Server" +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking-multi-dhcp-agents.xml:75(para) ./doc/admin-guide-cloud/section_networking-multi-dhcp-agents.xml:100(para) +msgid "Neutron configuration file /etc/neutron/neutron.conf:" +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking-multi-dhcp-agents.xml:85(para) ./doc/admin-guide-cloud/section_networking-multi-dhcp-agents.xml:109(para) +msgid "Update the plug-in configuration file /etc/neutron/plugins/linuxbridge/linuxbridge_conf.ini:" +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking-multi-dhcp-agents.xml:98(title) +msgid "HostA and HostB—L2 Agent" +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking-multi-dhcp-agents.xml:121(para) +msgid "Update the nova configuration file /etc/nova/nova.conf:" +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking-multi-dhcp-agents.xml:136(title) +msgid "HostA and HostB—DHCP Agent" +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking-multi-dhcp-agents.xml:138(para) +msgid "Update the DHCP configuration file /etc/neutron/dhcp_agent.ini:" +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking-multi-dhcp-agents.xml:146(title) +msgid "Commands in agent management and scheduler extensions" +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking-multi-dhcp-agents.xml:148(para) +msgid "The following commands require the tenant running the command to have an admin role." +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking-multi-dhcp-agents.xml:151(para) +msgid "Ensure that the following environment variables are set. These are used by the various clients to access Keystone." +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking-multi-dhcp-agents.xml:160(title) ./doc/admin-guide-cloud/section_networking-adv-config.xml:68(caption) +msgid "Settings" +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking-multi-dhcp-agents.xml:161(para) +msgid "To experiment, you need VMs and a neutron network:" +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking-multi-dhcp-agents.xml:181(title) +msgid "Manage agents in neutron deployment" +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking-multi-dhcp-agents.xml:182(para) +msgid "Every agent which supports these extensions will register itself with the neutron server when it starts up." +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking-multi-dhcp-agents.xml:186(para) +msgid "List all agents:" +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking-multi-dhcp-agents.xml:197(para) +msgid "The output shows information for four agents. The alive field shows :-) if the agent reported its state within the period defined by the option in the neutron.conf file. Otherwise the is xxx." +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking-multi-dhcp-agents.xml:209(para) +msgid "List the DHCP agents that host a specified network" +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking-multi-dhcp-agents.xml:211(para) +msgid "In some deployments, one DHCP agent is not enough to hold all network data. In addition, you must have a backup for it even when the deployment is small. The same network can be assigned to more than one DHCP agent and one DHCP agent can host more than one network." +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking-multi-dhcp-agents.xml:218(para) +msgid "List DHCP agents that a a specified network:" +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking-multi-dhcp-agents.xml:229(para) +msgid "List the networks hosted by a given DHCP agent." +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking-multi-dhcp-agents.xml:231(para) +msgid "This command is to show which networks a given dhcp agent is managing." +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking-multi-dhcp-agents.xml:242(para) +msgid "Show agent details." +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking-multi-dhcp-agents.xml:243(para) +msgid "The command shows details for a specified agent:" +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking-multi-dhcp-agents.xml:271(para) +msgid "In this output, heartbeat_timestamp is the time on the neutron server. You do not need to synchronize all agents to this time for this extension to run correctly. configurations describes the static configuration for the agent or run time data. This agent is a DHCP agent and it hosts one network, one subnet, and three ports." +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking-multi-dhcp-agents.xml:281(para) +msgid "Different types of agents show different details. The following output shows information for a Linux bridge agent:" +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking-multi-dhcp-agents.xml:306(para) +msgid "The output shows bridge-mapping and the number of virtual network devices on this L2 agent." +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking-multi-dhcp-agents.xml:313(title) +msgid "Manage assignment of networks to DHCP agent" +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking-multi-dhcp-agents.xml:314(para) +msgid "Now that you have run the and commands, you can add a network to a DHCP agent and remove one from it." +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking-multi-dhcp-agents.xml:320(para) +msgid "Default scheduling." +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking-multi-dhcp-agents.xml:321(para) +msgid "When you create a network with one port, you can schedule it to an active DHCP agent. If many active DHCP agents are running, select one randomly. You can design more sophisticated scheduling algorithms in the same way as nova-schedule later on." +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking-multi-dhcp-agents.xml:339(para) +msgid "It is allocated to DHCP agent on HostA. If you want to validate the behavior through the command, you must create a subnet for the network because the DHCP agent starts the dnsmasq service only if there is a DHCP." +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking-multi-dhcp-agents.xml:349(para) +msgid "Assign a network to a given DHCP agent." +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking-multi-dhcp-agents.xml:351(para) +msgid "To add another DHCP agent to host the network, run this command:" +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking-multi-dhcp-agents.xml:362(para) +msgid "Both DHCP agents host the net2 network." +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking-multi-dhcp-agents.xml:367(para) +msgid "Remove a network from a specified DHCP agent." +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking-multi-dhcp-agents.xml:369(para) +msgid "This command is the sibling command for the previous one. Remove net2 from the DHCP agent for HostA:" +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking-multi-dhcp-agents.xml:381(para) +msgid "You can see that only the DHCP agent for HostB is hosting the net2 network." +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking-multi-dhcp-agents.xml:388(title) +msgid "HA of DHCP agents" +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking-multi-dhcp-agents.xml:389(para) +msgid "Boot a VM on net2. Let both DHCP agents host net2. Fail the agents in turn to see if the VM can still get the desired IP." +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking-multi-dhcp-agents.xml:394(para) +msgid "Boot a VM on net2." +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking-multi-dhcp-agents.xml:415(para) +msgid "Make sure both DHCP agents hosting 'net2'." +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking-multi-dhcp-agents.xml:417(para) +msgid "Use the previous commands to assign the network to agents." +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking-multi-dhcp-agents.xml:429(title) +msgid "Test the HA" +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking-multi-dhcp-agents.xml:431(para) +msgid "Log in to the myserver4 VM, and run udhcpc, dhclient or other DHCP client." +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking-multi-dhcp-agents.xml:438(para) +msgid "Stop the DHCP agent on HostA. Besides stopping the neutron-dhcp-agent binary, you must stop the processes." +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking-multi-dhcp-agents.xml:446(para) +msgid "Run a DHCP client in VM to see if it can get the wanted IP." +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking-multi-dhcp-agents.xml:451(para) +msgid "Stop the DHCP agent on HostB too." +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking-multi-dhcp-agents.xml:455(para) +msgid "Run in the VM; it cannot get the wanted IP." +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking-multi-dhcp-agents.xml:460(para) +msgid "Start DHCP agent on HostB. The VM gets the wanted IP again." +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking-multi-dhcp-agents.xml:465(title) +msgid "Disable and remove an agent" +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking-multi-dhcp-agents.xml:466(para) +msgid "An administrator might want to disable an agent if a system hardware or software upgrade is planned. Some agents that support scheduling also support disabling and enabling agents, such as L3 and DHCP agents. After the agent is disabled, the scheduler does not schedule new resources to the agent. After the agent is disabled, you can safely remove the agent. Remove the resources on the agent before you delete the agent." +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking-multi-dhcp-agents.xml:475(para) +msgid "To run the following commands, you must stop the DHCP agent on HostA." +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking-multi-dhcp-agents.xml:497(para) +msgid "After deletion, if you restart the DHCP agent, it appears on the agent list again." +msgstr "" + +#: ./doc/admin-guide-cloud/section_rootwrap.xml:6(title) +msgid "Secure with root wrappers" +msgstr "" + +#: ./doc/admin-guide-cloud/section_rootwrap.xml:7(para) +msgid "The root wrapper enables the Compute unprivileged user to run a number of actions as the root user in the safest manner possible. Historically, Compute used a specific sudoers file that listed every command that the Compute user was allowed to run, and used to run that command as root. However this was difficult to maintain (the sudoers file was in packaging), and did not enable complex filtering of parameters (advanced filters). The rootwrap was designed to solve those issues." +msgstr "" + +#: ./doc/admin-guide-cloud/section_rootwrap.xml:19(title) +msgid "How rootwrap works" +msgstr "" + +#: ./doc/admin-guide-cloud/section_rootwrap.xml:20(para) +msgid "Instead of calling , Compute services start with nova- call . A generic sudoers entry lets the Compute user run nova-rootwrap as root. The nova-rootwrap code looks for filter definition directories in its configuration file, and loads command filters from them. Then it checks if the command requested by Compute matches one of those filters, in which case it executes the command (as root). If no filter matches, it denies the request." +msgstr "" + +#: ./doc/admin-guide-cloud/section_rootwrap.xml:33(title) +msgid "Security model" +msgstr "" + +#: ./doc/admin-guide-cloud/section_rootwrap.xml:34(para) +msgid "The escalation path is fully controlled by the root user. A sudoers entry (owned by root) allows Compute to run (as root) a specific rootwrap executable, and only with a specific configuration file (which should be owned by root). nova-rootwrap imports the Python modules it needs from a cleaned (and system-default) PYTHONPATH. The configuration file (also root-owned) points to root-owned filter definition directories, which contain root-owned filters definition files. This chain ensures that the Compute user itself is not in control of the configuration or modules used by the nova-rootwrap executable." +msgstr "" + +#: ./doc/admin-guide-cloud/section_rootwrap.xml:47(title) +msgid "Details of rootwrap.conf" +msgstr "" + +#: ./doc/admin-guide-cloud/section_rootwrap.xml:48(para) +msgid "You configure nova-rootwrap in the rootwrap.conf file. Because it's in the trusted security path, it must be owned and writable by only the root user. Its location is specified both in the sudoers entry and in the nova.conf configuration file with the rootwrap_config=entry." +msgstr "" + +#: ./doc/admin-guide-cloud/section_rootwrap.xml:55(para) +msgid "It uses an INI file format with these sections and parameters:" +msgstr "" + +#: ./doc/admin-guide-cloud/section_rootwrap.xml:59(caption) ./doc/admin-guide-cloud/section_rootwrap.xml:98(caption) +msgid "rootwrap.conf configuration options" +msgstr "" + +#: ./doc/admin-guide-cloud/section_rootwrap.xml:64(para) ./doc/admin-guide-cloud/section_rootwrap.xml:103(para) +msgid "Configuration option=Default value" +msgstr "" + +#: ./doc/admin-guide-cloud/section_rootwrap.xml:66(para) ./doc/admin-guide-cloud/section_rootwrap.xml:105(para) +msgid "(Type) Description" +msgstr "" + +#: ./doc/admin-guide-cloud/section_rootwrap.xml:71(para) +msgid "[DEFAULT]" +msgstr "" + +#: ./doc/admin-guide-cloud/section_rootwrap.xml:72(para) +msgid "filters_path=/etc/nova/rootwrap.d,/usr/share/nova/rootwrap" +msgstr "" + +#: ./doc/admin-guide-cloud/section_rootwrap.xml:74(para) +msgid "(ListOpt) Comma-separated list of directories containing filter definition files. Defines where filters for root wrap are stored. Directories defined on this line should all exist, be owned and writable only by the root user." +msgstr "" + +#: ./doc/admin-guide-cloud/section_rootwrap.xml:86(title) +msgid "Details of .filters files" +msgstr "" + +#: ./doc/admin-guide-cloud/section_rootwrap.xml:87(para) +msgid "Filters definition files contain lists of filters that nova-rootwrap will use to allow or deny a specific command. They are generally suffixed by .filters. Since they are in the trusted security path, they need to be owned and writable only by the root user. Their location is specified in the rootwrap.conf file." +msgstr "" + +#: ./doc/admin-guide-cloud/section_rootwrap.xml:93(para) +msgid "It uses an INI file format with a [Filters] section and several lines, each with a unique parameter name (different for each filter that you define):" +msgstr "" + +#: ./doc/admin-guide-cloud/section_rootwrap.xml:110(para) +msgid "[Filters]" +msgstr "" + +#: ./doc/admin-guide-cloud/section_rootwrap.xml:111(para) +msgid "filter_name=kpartx: CommandFilter, /sbin/kpartx, root" +msgstr "" + +#: ./doc/admin-guide-cloud/section_rootwrap.xml:113(para) +msgid "(ListOpt) Comma-separated list containing first the Filter class to use, followed by that Filter arguments (which vary depending on the Filter class selected)." +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking_auth.xml:6(title) +msgid "Authentication and authorization" +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking_auth.xml:7(para) +msgid "Networking uses the Identity Service as the default authentication service. When the Identity Service is enabled, users who submit requests to the Networking service must provide an authentication token in X-Auth-Token request header. Users obtain this token by authenticating with the Identity Service endpoint. For more information about authentication with the Identity Service, see OpenStack Identity Service API v2.0 Reference. When the Identity Service is enabled, it is not mandatory to specify the tenant ID for resources in create requests because the tenant ID is derived from the authentication token." +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking_auth.xml:22(para) +msgid "The default authorization settings only allow administrative users to create resources on behalf of a different tenant. Networking uses information received from Identity to authorize user requests. Networking handles two kind of authorization policies:" +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking_auth.xml:31(para) +msgid "Operation-based policies specify access criteria for specific operations, possibly with fine-grained control over specific attributes;" +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking_auth.xml:37(para) +msgid "Resource-based policies specify whether access to specific resource is granted or not according to the permissions configured for the resource (currently available only for the network resource). The actual authorization policies enforced in Networking might vary from deployment to deployment." +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking_auth.xml:47(para) +msgid "The policy engine reads entries from the policy.json file. The actual location of this file might vary from distribution to distribution. Entries can be updated while the system is running, and no service restart is required. Every time the policy file is updated, the policies are automatically reloaded. Currently the only way of updating such policies is to edit the policy file. In this section, the terms policy and rule refer to objects that are specified in the same way in the policy file. There are no syntax differences between a rule and a policy. A policy is something that is matched directly from the Networking policy engine. A rule is an element in a policy, which is evaluated. For instance in create_subnet: [[\"admin_or_network_owner\"]], create_subnet is a policy, and admin_or_network_owner is a rule." +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking_auth.xml:67(para) +msgid "Policies are triggered by the Networking policy engine whenever one of them matches an Networking API operation or a specific attribute being used in a given operation. For instance the create_subnet policy is triggered every time a POST /v2.0/subnets request is sent to the Networking server; on the other hand create_network:shared is triggered every time the shared attribute is explicitly specified (and set to a value different from its default) in a POST /v2.0/networks request. It is also worth mentioning that policies can be also related to specific API extensions; for instance extension:provider_network:set is be triggered if the attributes defined by the Provider Network extensions are specified in an API request." +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking_auth.xml:83(para) +msgid "An authorization policy can be composed by one or more rules. If more rules are specified, evaluation policy succeeds if any of the rules evaluates successfully; if an API operation matches multiple policies, then all the policies must evaluate successfully. Also, authorization rules are recursive. Once a rule is matched, the rule(s) can be resolved to another rule, until a terminal rule is reached." +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking_auth.xml:91(para) +msgid "The Networking policy engine currently defines the following kinds of terminal rules:" +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking_auth.xml:95(para) +msgid "Role-based rules evaluate successfully if the user who submits the request has the specified role. For instance \"role:admin\" is successful if the user who submits the request is an administrator." +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking_auth.xml:103(para) +msgid "Field-based rules evaluate successfully if a field of the resource specified in the current request matches a specific value. For instance \"field:networks:shared=True\" is successful if the shared attribute of the network resource is set to true." +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking_auth.xml:113(para) +msgid "Generic rules compare an attribute in the resource with an attribute extracted from the user's security credentials and evaluates successfully if the comparison is successful. For instance \"tenant_id:%(tenant_id)s\" is successful if the tenant identifier in the resource is equal to the tenant identifier of the user submitting the request." +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking_auth.xml:124(para) +msgid "This extract is from the default policy.json file:" +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking_auth.xml:148(para) +msgid "[1] is a rule which evaluates successfully if the current user is an administrator or the owner of the resource specified in the request (tenant identifier is equal)." +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking_auth.xml:152(para) +msgid "[2] is the default policy which is always evaluated if an API operation does not match any of the policies in policy.json." +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking_auth.xml:155(para) +msgid "[3] This policy evaluates successfully if either admin_or_owner, or shared evaluates successfully." +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking_auth.xml:159(para) +msgid "[4] This policy restricts the ability to manipulate the shared attribute for a network to administrators only." +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking_auth.xml:162(para) +msgid "[5] This policy restricts the ability to manipulate the mac_address attribute for a port only to administrators and the owner of the network where the port is attached." +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking_auth.xml:166(para) +msgid "In some cases, some operations are restricted to administrators only. This example shows you how to modify a policy file to permit tenants to define networks and see their resources and permit administrative users to perform all other operations:" +msgstr "" + +#: ./doc/admin-guide-cloud/section_ts_cinder_config.xml:7(title) +msgid "Troubleshoot the Block Storage configuration" +msgstr "" + +#: ./doc/admin-guide-cloud/section_ts_cinder_config.xml:9(para) +msgid "This section helps you solve some basic and common errors that you might encounter during setup and configuration of the Block Storage Service. The focus here is on failed creation of volumes. The most important thing to know is where to look in case of a failure." +msgstr "" + +#: ./doc/admin-guide-cloud/section_ts_cinder_config.xml:14(para) +msgid "Two log files are especially helpful for solving volume creation failures, the cinder-api log and the cinder-volume log. The cinder-api log is useful for determining if you have endpoint or connectivity issues. If you send a request to create a volume and it fails, review the cinder-api log to determine whether the request made it to the Block Storage service. If the request is logged and you see no errors or trace-backs, check the cinder-volume log for errors or trace-backs." +msgstr "" + +#: ./doc/admin-guide-cloud/section_ts_cinder_config.xml:28(para) +msgid "Create commands are listed in the cinder-api log." +msgstr "" + +#: ./doc/admin-guide-cloud/section_ts_cinder_config.xml:31(para) +msgid "These entries in the cinder.openstack.common.log file can be used to assist in troubleshooting your block storage configuration." +msgstr "" + +#: ./doc/admin-guide-cloud/section_ts_cinder_config.xml:103(para) +msgid "These common issues might occur during configuration. To correct, use these suggested solutions." +msgstr "" + +#: ./doc/admin-guide-cloud/section_ts_cinder_config.xml:107(para) +msgid "Issues with state_path and volumes_dir settings." +msgstr "" + +#: ./doc/admin-guide-cloud/section_ts_cinder_config.xml:109(para) +msgid "The OpenStack Block Storage uses as the default iscsi helper and implements persistent targets. This means that in the case of a tgt restart or even a node reboot your existing volumes on that node will be restored automatically with their original IQN." +msgstr "" + +#: ./doc/admin-guide-cloud/section_ts_cinder_config.xml:114(para) +msgid "In order to make this possible the iSCSI target information needs to be stored in a file on creation that can be queried in case of restart of the tgt daemon. By default, Block Storage uses a state_path variable, which if installing with Yum or APT should be set to /var/lib/cinder/. The next part is the volumes_dir variable, by default this just simply appends a \"volumes\" directory to the state_path. The result is a file-tree /var/lib/cinder/volumes/." +msgstr "" + +#: ./doc/admin-guide-cloud/section_ts_cinder_config.xml:127(para) +msgid "While this should all be handled by the installer, it can go wrong. If you have trouble creating volumes and this directory does not exist you should see an error message in the cinder-volume log indicating that the volumes_dir does not exist, and it should provide information about which path it was looking for." +msgstr "" + +#: ./doc/admin-guide-cloud/section_ts_cinder_config.xml:137(para) +msgid "The persistent tgt include file." +msgstr "" + +#: ./doc/admin-guide-cloud/section_ts_cinder_config.xml:138(para) +msgid "Along with the option, the iSCSI target driver also needs to be configured to look in the correct place for the persist files. This is a simple entry in the /etc/tgt/conf.d file that you should have set when you installed OpenStack. If issues occur, verify that you have a /etc/tgt/conf.d/cinder.conf file." +msgstr "" + +#: ./doc/admin-guide-cloud/section_ts_cinder_config.xml:147(para) +msgid "If the file is not present, create it with this command:" +msgstr "" + +#: ./doc/admin-guide-cloud/section_ts_cinder_config.xml:152(para) +msgid "No sign of attach call in the cinder-api log." +msgstr "" + +#: ./doc/admin-guide-cloud/section_ts_cinder_config.xml:155(para) +msgid "This is most likely going to be a minor adjustment to your nova.conf file. Make sure that your nova.conf has this entry:" +msgstr "" + +#: ./doc/admin-guide-cloud/section_ts_cinder_config.xml:162(para) +msgid "Failed to create iscsi target error in the cinder-volume.log file." +msgstr "" + +#: ./doc/admin-guide-cloud/section_ts_cinder_config.xml:166(para) +msgid "You might see this error in cinder-volume.log after trying to create a volume that is 1 GB. To fix this issue:" +msgstr "" + +#: ./doc/admin-guide-cloud/section_ts_cinder_config.xml:170(para) +msgid "Change content of the /etc/tgt/targets.conf from include /etc/tgt/conf.d/*.conf to include /etc/tgt/conf.d/cinder_tgt.conf, as follows:" +msgstr "" + +#: ./doc/admin-guide-cloud/section_ts_cinder_config.xml:179(para) +msgid "Restart tgt and cinder-* services so they pick up the new configuration." +msgstr "" + +#: ./doc/admin-guide-cloud/ch_blockstorage.xml:7(title) +msgid "Block Storage" +msgstr "" + +#: ./doc/admin-guide-cloud/ch_blockstorage.xml:8(para) +msgid "The OpenStack Block Storage service works though the interaction of a series of daemon processes named cinder-* that reside persistently on the host machine or machines. The binaries can all be run from a single node, or spread across multiple nodes. They can also be run on the same node as other OpenStack services." +msgstr "" + +#: ./doc/admin-guide-cloud/ch_blockstorage.xml:16(title) +msgid "Introduction to Block Storage" +msgstr "" + +#: ./doc/admin-guide-cloud/ch_blockstorage.xml:17(para) +msgid "To administer the OpenStack Block Storage service, it is helpful to understand a number of concepts. You must make certain choices when you configure the Block Storage service in OpenStack. The bulk of the options come down to two choices, single node or multi-node install. You can read a longer discussion about storage decisions in Storage Decisions in the OpenStack Operations Guide." +msgstr "" + +#: ./doc/admin-guide-cloud/ch_blockstorage.xml:26(para) +msgid "The OpenStack Block Storage Service enables you to add extra block-level storage to your OpenStack Compute instances. This service is similar to the Amazon EC2 Elastic Block Storage (EBS) offering." +msgstr "" + +#: ./doc/admin-guide-cloud/ch_blockstorage.xml:33(title) +msgid "Manage volumes" +msgstr "" + +#: ./doc/admin-guide-cloud/ch_blockstorage.xml:34(para) +msgid "The default OpenStack Block Storage service implementation is an iSCSI solution that uses Logical Volume Manager (LVM) for Linux." +msgstr "" + +#: ./doc/admin-guide-cloud/ch_blockstorage.xml:38(para) +msgid "The OpenStack Block Storage service is not a shared storage solution like a Storage Area Network (SAN) of NFS volumes, where you can attach a volume to multiple servers. With the OpenStack Block Storage service, you can attach a volume to only one instance at a time." +msgstr "" + +#: ./doc/admin-guide-cloud/ch_blockstorage.xml:44(para) +msgid "The OpenStack Block Storage service also provides drivers that enable you to use several vendors' back-end storage devices, in addition to or instead of the base LVM implementation." +msgstr "" + +#: ./doc/admin-guide-cloud/ch_blockstorage.xml:49(para) +msgid "This high-level procedure shows you how to create and attach a volume to a server instance." +msgstr "" + +#: ./doc/admin-guide-cloud/ch_blockstorage.xml:53(para) +msgid "You must configure both OpenStack Compute and the OpenStack Block Storage service through the cinder.conf file." +msgstr "" + +#: ./doc/admin-guide-cloud/ch_blockstorage.xml:58(para) +msgid "Create a volume through the command. This command creates an LV into the volume group (VG) \"cinder-volumes.\"" +msgstr "" + +#: ./doc/admin-guide-cloud/ch_blockstorage.xml:64(para) +msgid "Attach the volume to an instance through the command. This command creates a unique iSCSI IQN that is exposed to the compute node." +msgstr "" + +#: ./doc/admin-guide-cloud/ch_blockstorage.xml:70(para) +msgid "The compute node, which runs the instance, now has an active ISCSI session and new local storage (usually a /dev/sdX disk)." +msgstr "" + +#: ./doc/admin-guide-cloud/ch_blockstorage.xml:77(para) +msgid "libvirt uses that local storage as storage for the instance. The instance get a new disk, usually a /dev/vdX disk." +msgstr "" + +#: ./doc/admin-guide-cloud/ch_blockstorage.xml:86(para) +msgid "For this particular walk through, one cloud controller runs nova-api, nova-scheduler, nova-objectstore, nova-network and cinder-* services. Two additional compute nodes run nova-compute. The walk through uses a custom partitioning scheme that carves out 60 GB of space and labels it as LVM. The network uses the FlatManager and NetworkManager settings for OpenStack Compute (Nova)." +msgstr "" + +#: ./doc/admin-guide-cloud/ch_blockstorage.xml:100(para) +msgid "The network mode does not interfere with the way cinder works, but you must set up networking for cinder to work. For details, see ." +msgstr "" + +#: ./doc/admin-guide-cloud/ch_blockstorage.xml:103(para) +msgid "To set up Compute to use volumes, ensure that Block Storage is installed along with lvm2. This guide describes how to troubleshoot your installation and back up your Compute volumes." +msgstr "" + +#: ./doc/admin-guide-cloud/ch_blockstorage.xml:108(title) +msgid "Boot from volume" +msgstr "" + +#: ./doc/admin-guide-cloud/ch_blockstorage.xml:109(para) +msgid "In some cases, instances can be stored and run from inside volumes. For information, see the Launch an instance from a volume section in the OpenStack End User Guide." +msgstr "" + +#: ./doc/admin-guide-cloud/ch_blockstorage.xml:124(title) +msgid "Troubleshoot your installation" +msgstr "" + +#: ./doc/admin-guide-cloud/ch_blockstorage.xml:125(para) +msgid "This section provides useful tips to help troubleshoot your Block Storage Service installation." +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking-adv-config.xml:6(title) +msgid "Advanced configuration options" +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking-adv-config.xml:7(para) +msgid "This section describes advanced configuration options for various system components. For example, configuration options where the default works but that the user wants to customize options. After installing from packages, $NEUTRON_CONF_DIR is /etc/neutron." +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking-adv-config.xml:13(title) +msgid "OpenStack Networking server with plug-in" +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking-adv-config.xml:14(para) +msgid "This is the web server that runs the OpenStack Networking API Web Server. It is responsible for loading a plug-in and passing the API calls to the plug-in for processing. The neutron-server should receive one of more configuration files as it its input, for example:" +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking-adv-config.xml:20(para) +msgid "The neutron config contains the common neutron configuration parameters. The plug-in config contains the plug-in specific flags. The plug-in that is run on the service is loaded through the core_plugin configuration parameter. In some cases a plug-in might have an agent that performs the actual networking." +msgstr "" + +#. Specific +#. configuration details can be seen in the Appendix - +#. Configuration File Options. +#: ./doc/admin-guide-cloud/section_networking-adv-config.xml:31(para) +msgid "Most plug-ins require a SQL database. After you install and start the database server, set a password for the root account and delete the anonymous accounts:" +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking-adv-config.xml:37(para) +msgid "Create a database and user account specifically for plug-in:" +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking-adv-config.xml:43(para) +msgid "Once the above is done you can update the settings in the relevant plug-in configuration files. The plug-in specific configuration files can be found at $NEUTRON_CONF_DIR/plugins." +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking-adv-config.xml:47(para) +msgid "Some plug-ins have a L2 agent that performs the actual networking. That is, the agent will attach the virtual machine NIC to the OpenStack Networking network. Each node should have an L2 agent running on it. Note that the agent receives the following input parameters:" +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking-adv-config.xml:53(para) +msgid "Two things need to be done prior to working with the plug-in:" +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking-adv-config.xml:57(para) +msgid "Ensure that the core plug-in is updated." +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking-adv-config.xml:60(para) +msgid "Ensure that the database connection is correctly set." +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking-adv-config.xml:64(para) +msgid "The following table contains examples for these settings. Some Linux packages might provide installation utilities that configure these." +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking-adv-config.xml:73(th) +msgid "Parameter" +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking-adv-config.xml:74(th) +msgid "Value" +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking-adv-config.xml:84(td) ./doc/admin-guide-cloud/section_networking-adv-config.xml:107(td) +msgid "core_plugin ($NEUTRON_CONF_DIR/neutron.conf)" +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking-adv-config.xml:86(td) +msgid "neutron.plugins.openvswitch.ovs_neutron_plugin.OVSNeutronPluginV2" +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking-adv-config.xml:90(code) ./doc/admin-guide-cloud/section_networking-adv-config.xml:113(code) +msgid "[database]" +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking-adv-config.xml:89(td) +msgid "connection (in the plugin configuration file, section )" +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking-adv-config.xml:91(td) +msgid "mysql://<username>:<password>@localhost/ovs_neutron?charset=utf8" +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking-adv-config.xml:94(td) ./doc/admin-guide-cloud/section_networking-adv-config.xml:117(td) +msgid "Plug-in Configuration File" +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking-adv-config.xml:95(td) +msgid "$NEUTRON_CONF_DIR/plugins/openvswitch/ovs_neutron_plugin.ini" +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking-adv-config.xml:98(td) ./doc/admin-guide-cloud/section_networking-adv-config.xml:121(td) ./doc/admin-guide-cloud/section_networking_arch.xml:35(th) +msgid "Agent" +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking-adv-config.xml:99(td) +msgid "neutron-openvswitch-agent" +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking-adv-config.xml:109(td) +msgid "neutron.plugins.linuxbridge.lb_neutron_plugin.LinuxBridgePluginV2" +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking-adv-config.xml:112(td) +msgid "connection (in the plug-in configuration file, section )" +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking-adv-config.xml:114(td) +msgid "mysql://<username>:<password>@localhost/neutron_linux_bridge?charset=utf8" +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking-adv-config.xml:118(td) +msgid "$NEUTRON_CONF_DIR/plugins/linuxbridge/linuxbridge_conf.ini" +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking-adv-config.xml:122(td) +msgid "neutron-linuxbridge-agent" +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking-adv-config.xml:126(para) +msgid "All plug-in configuration files options can be found in the Appendix - Configuration File Options." +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking-adv-config.xml:130(title) ./doc/admin-guide-cloud/section_networking-scenarios.xml:200(title) +msgid "DHCP agent" +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking-adv-config.xml:131(para) +msgid "There is an option to run a DHCP server that will allocate IP addresses to virtual machines running on the network. When a subnet is created, by default, the subnet has DHCP enabled." +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking-adv-config.xml:135(para) +msgid "The node that runs the DHCP agent should run:" +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking-adv-config.xml:138(para) +msgid "Currently the DHCP agent uses dnsmasq to perform that static address assignment." +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking-adv-config.xml:140(para) +msgid "A driver needs to be configured that matches the plug-in running on the service.
Basic settings
ParameterValue
Open vSwitch
interface_driver ($NEUTRON_CONF_DIR/dhcp_agent.ini)neutron.agent.linux.interface.OVSInterfaceDriver
Linux Bridge
interface_driver ($NEUTRON_CONF_DIR/dhcp_agent.ini)neutron.agent.linux.interface.BridgeInterfaceDriver
" +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking-adv-config.xml:175(title) ./doc/admin-guide-cloud/section_networking-adv-config.xml:264(title) ./doc/admin-guide-cloud/section_networking-adv-config.xml:386(title) +msgid "Namespace" +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking-adv-config.xml:176(para) +msgid "By default the DHCP agent makes use of Linux network namespaces in order to support overlapping IP addresses. Requirements for network namespaces support are described in the Limitations section." +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking-adv-config.xml:182(para) +msgid "If the Linux installation does not support network namespace, you must disable using network namespace in the DHCP agent config file (The default value of use_namespaces is True)." +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking-adv-config.xml:192(title) +msgid "L3 Agent" +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking-adv-config.xml:193(para) +msgid "There is an option to run a L3 agent that will give enable layer 3 forwarding and floating IP support. The node that runs the L3 agent should run:" +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking-adv-config.xml:198(para) +msgid "A driver needs to be configured that matches the plug-in running on the service. The driver is used to create the routing interface.
Basic settings
ParameterValue
Open vSwitch
interface_driver ($NEUTRON_CONF_DIR/l3_agent.ini)neutron.agent.linux.interface.OVSInterfaceDriver
external_network_bridge ($NEUTRON_CONF_DIR/l3_agent.ini)br-ex
Linux Bridge
interface_driver ($NEUTRON_CONF_DIR/l3_agent.ini)neutron.agent.linux.interface.BridgeInterfaceDriver
external_network_bridge ($NEUTRON_CONF_DIR/l3_agent.ini)This field must be empty (or the bridge name for the external network).
" +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking-adv-config.xml:250(para) +msgid "OpenStack Identity authentication:" +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking-adv-config.xml:252(para) +msgid "For example," +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking-adv-config.xml:256(para) +msgid "Admin user details:" +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking-adv-config.xml:246(para) +msgid "The L3 agent communicates with the OpenStack Networking server via the OpenStack Networking API, so the following configuration is required: " +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking-adv-config.xml:265(para) +msgid "By default the L3 agent makes use of Linux network namespaces in order to support overlapping IP addresses. Requirements for network namespaces support are described in the Limitation section." +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking-adv-config.xml:271(para) +msgid "If the Linux installation does not support network namespace, you must disable using network namespace in the L3 agent config file (The default value of use_namespaces is True)." +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking-adv-config.xml:278(para) +msgid "When use_namespaces is set to False, only one router ID can be supported per node. This must be configured via the configuration variable router_id." +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking-adv-config.xml:285(para) +msgid "To configure it, you need to run the OpenStack Networking service and create a router, and then set an ID of the router created to router_id in the L3 agent configuration file." +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking-adv-config.xml:305(title) +msgid "Multiple floating IP pools" +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking-adv-config.xml:306(para) +msgid "The L3 API in OpenStack Networking supports multiple floating IP pools. In OpenStack Networking, a floating IP pool is represented as an external network and a floating IP is allocated from a subnet associated with the external network. Since each L3 agent can be associated with at most one external network, we need to invoke multiple L3 agent to define multiple floating IP pools. 'gateway_external_network_id' in L3 agent configuration file indicates the external network that the L3 agent handles. You can run multiple L3 agent instances on one host." +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking-adv-config.xml:318(para) +msgid "In addition, when you run multiple L3 agents, make sure that handle_internal_only_routers is set to True only for one L3 agent in an OpenStack Networking deployment and set to False for all other L3 agents. Since the default value of this parameter is True, you need to configure it carefully." +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking-adv-config.xml:327(para) +msgid "Before starting L3 agents, you need to create routers and external networks, then update the configuration files with UUID of external networks and start L3 agents." +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking-adv-config.xml:331(para) +msgid "For the first agent, invoke it with the following l3_agent.ini where handle_internal_only_routers is True." +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking-adv-config.xml:340(para) +msgid "For the second (or later) agent, invoke it with the following l3_agent.ini where handle_internal_only_routers is False." +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking-adv-config.xml:349(title) +msgid "L3 Metering Agent" +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking-adv-config.xml:350(para) +msgid "There is an option to run a L3 metering agent that will enable layer 3 traffic metering. In general case the metering agent should be launched on all nodes that run the L3 agent:" +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking-adv-config.xml:355(para) +msgid "A driver needs to be configured that matches the plug-in running on the service. The driver is used to add metering to the routing interface.
Basic settings
ParameterValue
Open vSwitch
interface_driver ($NEUTRON_CONF_DIR/metering_agent.ini)neutron.agent.linux.interface.OVSInterfaceDriver
Linux Bridge
interface_driver ($NEUTRON_CONF_DIR/metering_agent.ini)neutron.agent.linux.interface.BridgeInterfaceDriver
" +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking-adv-config.xml:387(para) +msgid "The metering agent and the L3 agent have to have the same configuration regarding to the network namespaces setting." +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking-adv-config.xml:389(para) +msgid "If the Linux installation does not support network namespace, you must disable using network namespace in the L3 metering config file (The default value of is True)." +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking-adv-config.xml:396(title) +msgid "L3 metering driver" +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking-adv-config.xml:397(para) +msgid "A driver which implements the metering abstraction needs to be configured. Currently there is only one implementation which is based on iptables." +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking-adv-config.xml:402(title) +msgid "L3 metering service driver" +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking-adv-config.xml:403(para) +msgid "To enable L3 metering you have to be sure to set the following parameter in neutron.conf on the host that runs neutron-server:" +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking-adv-config.xml:410(title) +msgid "Limitations" +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking-adv-config.xml:413(para) +msgid "No equivalent for nova-network --multi_host flag: Nova-network has a model where the L3, NAT, and DHCP processing happen on the compute node itself, rather than a dedicated networking node. OpenStack Networking now support running multiple l3-agent and dhcp-agents with load being split across those agents, but the tight coupling of that scheduling with the location of the VM is not supported in Grizzly. The Havana release is expected to include an exact replacement for the --multi_host flag in nova-network." +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking-adv-config.xml:427(para) +msgid "Linux network namespace required on nodes running neutron-l3-agent or neutron-dhcp-agent if overlapping IPs are in use: . In order to support overlapping IP addresses, the OpenStack Networking DHCP and L3 agents use Linux network namespaces by default. The hosts running these processes must support network namespaces. To support network namespaces, the following are required:" +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking-adv-config.xml:445(para) +msgid "Linux kernel 2.6.24 or newer (with CONFIG_NET_NS=y in kernel configuration) and" +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking-adv-config.xml:450(para) +msgid "iproute2 utilities ('ip' command) version 3.1.0 (aka 20111117) or newer" +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking-adv-config.xml:455(para) +msgid "To check whether your host supports namespaces try running the following as root:" +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking-adv-config.xml:459(para) +msgid "If the preceding commands do not produce errors, your platform is likely sufficient to use the dhcp-agent or l3-agent with namespace. In our experience, Ubuntu 12.04 or later support namespaces as does Fedora 17 and new, but some older RHEL platforms do not by default. It may be possible to upgrade the iproute2 package on a platform that does not support namespaces by default." +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking-adv-config.xml:468(para) +msgid "If you need to disable namespaces, make sure the neutron.conf used by neutron-server has the following setting:" +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking-adv-config.xml:472(para) +msgid "and that the dhcp_agent.ini and l3_agent.ini have the following setting:" +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking-adv-config.xml:476(para) +msgid "If the host does not support namespaces then the neutron-l3-agent and neutron-dhcp-agent should be run on different hosts. This is due to the fact that there is no isolation between the IP addresses created by the L3 agent and by the DHCP agent. By manipulating the routing the user can ensure that these networks have access to one another." +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking-adv-config.xml:488(para) +msgid "If you run both L3 and DHCP services on the same node, you should enable namespaces to avoid conflicts with routes:" +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking-adv-config.xml:496(para) +msgid "No IPv6 support for L3 agent: The neutron-l3-agent, used by many plug-ins to implement L3 forwarding, supports only IPv4 forwarding. Currently, there are no errors provided if you configure IPv6 addresses via the API." +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking-adv-config.xml:507(para) +msgid "ZeroMQ support is experimental: Some agents, including neutron-dhcp-agent, neutron-openvswitch-agent, and neutron-linuxbridge-agent use RPC to communicate. ZeroMQ is an available option in the configuration file, but has not been tested and should be considered experimental. In particular, issues might occur with ZeroMQ and the dhcp agent." +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking-adv-config.xml:522(para) +msgid "MetaPlugin is experimental: This release includes a MetaPlugin that is intended to support multiple plug-ins at the same time for different API requests, based on the content of those API requests. The core team has not thoroughly reviewed or tested this functionality. Consider this functionality to be experimental until further validation is performed." +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking_pagination_and_sorting_support.xml:6(title) +msgid "Plug-in pagination and sorting support" +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking_pagination_and_sorting_support.xml:8(caption) +msgid "Plug-ins that support native pagination and sorting" +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking_pagination_and_sorting_support.xml:13(th) +msgid "Support Native Pagination" +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking_pagination_and_sorting_support.xml:14(th) +msgid "Support Native Sorting" +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking_pagination_and_sorting_support.xml:20(td) ./doc/admin-guide-cloud/section_networking_pagination_and_sorting_support.xml:21(td) ./doc/admin-guide-cloud/section_networking_pagination_and_sorting_support.xml:25(td) ./doc/admin-guide-cloud/section_networking_pagination_and_sorting_support.xml:26(td) ./doc/admin-guide-cloud/section_networking_pagination_and_sorting_support.xml:30(td) ./doc/admin-guide-cloud/section_networking_pagination_and_sorting_support.xml:31(td) ./doc/admin-guide-cloud/section_networking_adv_features.xml:394(td) ./doc/admin-guide-cloud/section_networking_adv_features.xml:1189(td) ./doc/admin-guide-cloud/section_networking_adv_features.xml:1322(td) ./doc/admin-guide-cloud/section_networking-use.xml:134(td) ./doc/admin-guide-cloud/section_networking-use.xml:235(td) +msgid "True" +msgstr "" + +#: ./doc/admin-guide-cloud/section_backup-block-storage-disks.xml:6(title) +msgid "Back up Block Storage Service disks" +msgstr "" + +#: ./doc/admin-guide-cloud/section_backup-block-storage-disks.xml:7(para) +msgid "While you can use the LVM snapshot to create snapshots, you can also use it to back up your volumes. By using LVM snapshot, you reduce the size of the backup; only existing data is backed up instead of the entire volume." +msgstr "" + +#: ./doc/admin-guide-cloud/section_backup-block-storage-disks.xml:11(para) +msgid "To back up a volume, you must create a snapshot of it. An LVM snapshot is the exact copy of a logical volume, which contains data in a frozen state. This prevents data corruption, because data cannot be manipulated during the volume creation process. Remember that the volumes created through a command exist in an LVM logical volume." +msgstr "" + +#: ./doc/admin-guide-cloud/section_backup-block-storage-disks.xml:18(para) +msgid "Before you create the snapshot, you must have enough space to save it. As a precaution, you should have at least twice as much space as the potential snapshot size. If insufficient space is available, the snapshot might become corrupted." +msgstr "" + +#: ./doc/admin-guide-cloud/section_backup-block-storage-disks.xml:23(para) +msgid "For this example, assume that a 100 GB volume named volume-00000001 was created for an instance while only 4 GB are used. This example uses these commands to back up only those 4 GB:" +msgstr "" + +#: ./doc/admin-guide-cloud/section_backup-block-storage-disks.xml:29(para) +msgid " command. Directly manipulates the volumes." +msgstr "" + +#: ./doc/admin-guide-cloud/section_backup-block-storage-disks.xml:33(para) +msgid " command. Discovers the partition table created inside the instance." +msgstr "" + +#: ./doc/admin-guide-cloud/section_backup-block-storage-disks.xml:37(para) +msgid " command. Creates a minimum-sized backup." +msgstr "" + +#: ./doc/admin-guide-cloud/section_backup-block-storage-disks.xml:41(para) +msgid " command. Calculates the backup checksum to check its consistency." +msgstr "" + +#: ./doc/admin-guide-cloud/section_backup-block-storage-disks.xml:45(para) +msgid "You can apply this process to volumes of any size." +msgstr "" + +#: ./doc/admin-guide-cloud/section_backup-block-storage-disks.xml:47(title) +msgid "To back up Block Storage Service disks" +msgstr "" + +#: ./doc/admin-guide-cloud/section_backup-block-storage-disks.xml:49(title) +msgid "Create a snapshot of a used volume" +msgstr "" + +#: ./doc/admin-guide-cloud/section_backup-block-storage-disks.xml:52(para) +msgid "Use this command to list all volumes:" +msgstr "" + +#: ./doc/admin-guide-cloud/section_backup-block-storage-disks.xml:56(para) +msgid "Create the snapshot; you can do this while the volume is attached to an instance:" +msgstr "" + +#: ./doc/admin-guide-cloud/section_backup-block-storage-disks.xml:59(para) +msgid "Use the configuration option to tell LVM that you want a snapshot of an already existing volume. The command includes the size of the space reserved for the snapshot volume, the name of the snapshot, and the path of an already existing volume. Generally, this path is /dev/nova-volumes/$volume_name." +msgstr "" + +#: ./doc/admin-guide-cloud/section_backup-block-storage-disks.xml:67(para) +msgid "The size does not have to be the same as the volume of the snapshot. The size parameter defines the space that LVM reserves for the snapshot volume. As a precaution, the size should be the same as that of the original volume, even if the whole space is not currently used by the snapshot." +msgstr "" + +#: ./doc/admin-guide-cloud/section_backup-block-storage-disks.xml:78(para) +msgid "Run the command again to verify the snapshot:" +msgstr "" + +#: ./doc/admin-guide-cloud/section_backup-block-storage-disks.xml:120(title) +msgid "Partition table discovery" +msgstr "" + +#: ./doc/admin-guide-cloud/section_backup-block-storage-disks.xml:123(para) +msgid "To exploit the snapshot with the command, mount your partition on the Block Storage Service server." +msgstr "" + +#: ./doc/admin-guide-cloud/section_backup-block-storage-disks.xml:127(para) +msgid "The utility discovers and maps table partitions. You can use it to view partitions that are created inside the instance. Without using the partitions created inside instances, you cannot see its content and create efficient backups." +msgstr "" + +#: ./doc/admin-guide-cloud/section_backup-block-storage-disks.xml:136(para) +msgid "On a Debian-based distribution, you can also use the command." +msgstr "" + +#: ./doc/admin-guide-cloud/section_backup-block-storage-disks.xml:140(para) +msgid "If the tools successfully find and map the partition table, no errors are returned." +msgstr "" + +#: ./doc/admin-guide-cloud/section_backup-block-storage-disks.xml:145(para) +msgid "To check the partition table map, run this command:" +msgstr "" + +#: ./doc/admin-guide-cloud/section_backup-block-storage-disks.xml:148(para) +msgid "You can see the nova--volumes-volume--00000001--snapshot1 partition." +msgstr "" + +#: ./doc/admin-guide-cloud/section_backup-block-storage-disks.xml:151(para) +msgid "If you created more than one partition on that volume, you see several partitions; for example: nova--volumes-volume--00000001--snapshot2, nova--volumes-volume--00000001--snapshot3, and so on." +msgstr "" + +#: ./doc/admin-guide-cloud/section_backup-block-storage-disks.xml:159(para) +msgid "Mount your partition:" +msgstr "" + +#: ./doc/admin-guide-cloud/section_backup-block-storage-disks.xml:161(para) +msgid "If the partition mounts successfully, no errors are returned." +msgstr "" + +#: ./doc/admin-guide-cloud/section_backup-block-storage-disks.xml:163(para) +msgid "You can directly access the data inside the instance. If a message prompts you for a partition or you cannot mount it, determine whether enough space was allocated for the snapshot or the command failed to discover the partition table." +msgstr "" + +#: ./doc/admin-guide-cloud/section_backup-block-storage-disks.xml:170(para) +msgid "Allocate more space to the snapshot and try the process again." +msgstr "" + +#: ./doc/admin-guide-cloud/section_backup-block-storage-disks.xml:176(title) +msgid "Use the command to create archives" +msgstr "" + +#: ./doc/admin-guide-cloud/section_backup-block-storage-disks.xml:178(para) +msgid "Create a backup of the volume:" +msgstr "" + +#: ./doc/admin-guide-cloud/section_backup-block-storage-disks.xml:180(para) +msgid "This command creates a tar.gz file that contains the data, and data only. This ensures that you do not waste space by backing up empty sectors." +msgstr "" + +#: ./doc/admin-guide-cloud/section_backup-block-storage-disks.xml:186(title) +msgid "Checksum calculation I" +msgstr "" + +#: ./doc/admin-guide-cloud/section_backup-block-storage-disks.xml:187(para) +msgid "You should always have the checksum for your backup files. When you transfer the same file over the network, you can run a checksum calculation to ensure that your file was not corrupted during its transfer. The checksum is a unique ID for a file. If the checksums are different, the file is corrupted." +msgstr "" + +#: ./doc/admin-guide-cloud/section_backup-block-storage-disks.xml:193(para) +msgid "Run this command to run a checksum for your file and save the result to a file:" +msgstr "" + +#: ./doc/admin-guide-cloud/section_backup-block-storage-disks.xml:197(para) +msgid "Use the command carefully because the time it takes to complete the calculation is directly proportional to the size of the file." +msgstr "" + +#: ./doc/admin-guide-cloud/section_backup-block-storage-disks.xml:201(para) +msgid "For files larger than around 4 to 6 GB, and depending on your CPU, the process might take a long time." +msgstr "" + +#: ./doc/admin-guide-cloud/section_backup-block-storage-disks.xml:207(title) +msgid "After work cleaning" +msgstr "" + +#: ./doc/admin-guide-cloud/section_backup-block-storage-disks.xml:208(para) +msgid "Now that you have an efficient and consistent backup, use this command to clean up the file system:" +msgstr "" + +#: ./doc/admin-guide-cloud/section_backup-block-storage-disks.xml:213(para) +msgid "Unmount the volume:" +msgstr "" + +#: ./doc/admin-guide-cloud/section_backup-block-storage-disks.xml:217(para) +msgid "Delete the partition table:" +msgstr "" + +#: ./doc/admin-guide-cloud/section_backup-block-storage-disks.xml:221(para) +msgid "Remove the snapshot:" +msgstr "" + +#: ./doc/admin-guide-cloud/section_backup-block-storage-disks.xml:225(para) +msgid "Repeat these steps for all your volumes." +msgstr "" + +#: ./doc/admin-guide-cloud/section_backup-block-storage-disks.xml:228(title) +msgid "Automate your backups" +msgstr "" + +#: ./doc/admin-guide-cloud/section_backup-block-storage-disks.xml:229(para) +msgid "Because more and more volumes might be allocated to your Block Storage service, you might want to automate your backups. The SCR_5005_V01_NUAC-OPENSTACK-EBS-volumes-backup.sh script assists you with this task. The script performs the operations from the previous example, but also provides a mail report and runs the backup based on the setting." +msgstr "" + +#: ./doc/admin-guide-cloud/section_backup-block-storage-disks.xml:239(para) +msgid "Launch this script from the server that runs the Block Storage Service." +msgstr "" + +#: ./doc/admin-guide-cloud/section_backup-block-storage-disks.xml:241(para) +msgid "This example shows a mail report:" +msgstr "" + +#: ./doc/admin-guide-cloud/section_backup-block-storage-disks.xml:255(para) +msgid "The script also enables you to SSH to your instances and run a command into them. To make this work, enable the connection to the Compute project keys. If you do not want to run the command, you can add enable_mysql_dump=0 to the script to turn off this functionality." +msgstr "" + +#: ./doc/admin-guide-cloud/section_ts_failed_connect_vol_FC_SAN.xml:4(title) +msgid "Failed to connect volume in FC SAN" +msgstr "" + +#: ./doc/admin-guide-cloud/section_ts_failed_connect_vol_FC_SAN.xml:7(para) +msgid "Compute node failed to connect to a volume in a Fibre Channel (FC) SAN configuration. The WWN may not be zoned correctly in your FC SAN that links the Compute host to the storage array." +msgstr "" + +#: ./doc/admin-guide-cloud/section_ts_failed_connect_vol_FC_SAN.xml:16(para) +msgid "The network administrator must configure the FC SAN fabric by correctly zoning the WWN (port names) from your Compute node HBAs." +msgstr "" + +#: ./doc/admin-guide-cloud/section_object-storage-admin.xml:6(title) +msgid "System administration for Object Storage" +msgstr "" + +#: ./doc/admin-guide-cloud/section_object-storage-admin.xml:7(para) +msgid "By understanding Object Storage concepts, you can better monitor and administer your storage solution. The majority of the administration information is maintained in developer documentation at docs.openstack.org/developer/swift/." +msgstr "" + +#: ./doc/admin-guide-cloud/section_object-storage-admin.xml:13(para) +msgid "See the OpenStack Configuration Reference for a list of configuration options for Object Storage." +msgstr "" + +#: ./doc/admin-guide-cloud/ch_objectstorage.xml:7(title) +msgid "Object Storage" +msgstr "" + +#: ./doc/admin-guide-cloud/section_ts_vol_attach_miss_sg_scan.xml:8(title) +msgid "Failed to Attach Volume, Missing sg_scan" +msgstr "" + +#: ./doc/admin-guide-cloud/section_ts_vol_attach_miss_sg_scan.xml:11(para) +msgid "Failed to attach volume to an instance, sg_scan file not found. This warning and error occur when the sg3-utils package is not installed on the Compute node. The IDs in your message are unique to your system:" +msgstr "" + +#: ./doc/admin-guide-cloud/section_ts_vol_attach_miss_sg_scan.xml:25(para) +msgid "Run this command on the Compute node to install the sg3-utils package:" +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking_high_avail.xml:6(title) +msgid "High availability" +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking_high_avail.xml:7(para) +msgid "The use of high-availability in a Networking deployment helps prevent individual node failures. In general, you can run neutron-server and neutron-dhcp-agent in an active-active fashion. You can run the neutron-l3-agent service as active/passive, which avoids IP conflicts with respect to gateway IP addresses." +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking_high_avail.xml:17(title) +msgid "Networking high availability with Pacemaker" +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking_high_avail.xml:18(para) +msgid "You can run some Networking services into a cluster (Active / Passive or Active / Active for Networking Server only) with Pacemaker." +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking_high_avail.xml:21(para) +msgid "Download the latest resources agents:" +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking_high_avail.xml:24(para) +msgid "neutron-server: https://github.com/madkiss/openstack-resource-agents" +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking_high_avail.xml:29(para) +msgid "neutron-dhcp-agent : https://github.com/madkiss/openstack-resource-agents" +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking_high_avail.xml:34(para) +msgid "neutron-l3-agent : https://github.com/madkiss/openstack-resource-agents" +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking_high_avail.xml:40(para) +msgid "For information about how to build a cluster, see Pacemaker documentation." +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking_adv_operational_features.xml:6(title) +msgid "Advanced operational features" +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking_adv_operational_features.xml:8(title) +msgid "Logging settings" +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking_adv_operational_features.xml:9(para) +msgid "Networking components use Python logging module to do logging. Logging configuration can be provided in neutron.conf or as command line options. Command options override ones in neutron.conf." +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking_adv_operational_features.xml:14(para) +msgid "To configure logging for Networking components, use one of these methods:" +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking_adv_operational_features.xml:18(para) +msgid "Provide logging settings in a logging configuration file." +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking_adv_operational_features.xml:20(para) +msgid "See Python logging how-to to learn more about logging." +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking_adv_operational_features.xml:24(para) +msgid "Provide logging setting in neutron.conf" +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking_adv_operational_features.xml:49(title) +msgid "Notifications" +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking_adv_operational_features.xml:50(para) +msgid "Notifications can be sent when Networking resources such as network, subnet and port are created, updated or deleted." +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking_adv_operational_features.xml:54(title) +msgid "Notification options" +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking_adv_operational_features.xml:55(para) +msgid "To support DHCP agent, rpc_notifier driver must be set. To set up the notification, edit notification options in neutron.conf:" +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking_adv_operational_features.xml:85(title) +msgid "Setting cases" +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking_adv_operational_features.xml:87(title) +msgid "Logging and RPC" +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking_adv_operational_features.xml:88(para) +msgid "These options configure the Networking server to send notifications through logging and RPC. The logging options are described in OpenStack Configuration Reference . RPC notifications go to 'notifications.info' queue bound to a topic exchange defined by 'control_exchange' in neutron.conf." +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking_adv_operational_features.xml:127(title) +msgid "Multiple RPC topics" +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking_adv_operational_features.xml:128(para) +msgid "These options configure the Networking server to send notifications to multiple RPC topics. RPC notifications go to 'notifications_one.info' and 'notifications_two.info' queues bound to a topic exchange defined by 'control_exchange' in neutron.conf." +msgstr "" + +#. ... Based on a blog, should be replaced with original material... +#: ./doc/admin-guide-cloud/section_object-storage-monitoring.xml:7(title) +msgid "Object Storage monitoring" +msgstr "" + +#: ./doc/admin-guide-cloud/section_object-storage-monitoring.xml:9(para) +msgid "Excerpted from a blog post by Darrell Bishop" +msgstr "" + +#: ./doc/admin-guide-cloud/section_object-storage-monitoring.xml:12(para) +msgid "An OpenStack Object Storage cluster is a collection of many daemons that work together across many nodes. With so many different components, you must be able to tell what is going on inside the cluster. Tracking server-level metrics like CPU utilization, load, memory consumption, disk usage and utilization, and so on is necessary, but not sufficient." +msgstr "" + +#: ./doc/admin-guide-cloud/section_object-storage-monitoring.xml:19(para) +msgid "What are different daemons are doing on each server? What is the volume of object replication on node8? How long is it taking? Are there errors? If so, when did they happen?" +msgstr "" + +#: ./doc/admin-guide-cloud/section_object-storage-monitoring.xml:22(para) +msgid "In such a complex ecosystem, you can use multiple approaches to get the answers to these questions. This section describes several approaches." +msgstr "" + +#: ./doc/admin-guide-cloud/section_object-storage-monitoring.xml:26(title) +msgid "Swift Recon" +msgstr "" + +#: ./doc/admin-guide-cloud/section_object-storage-monitoring.xml:27(para) +msgid "The Swift Recon middleware (see http://swift.openstack.org/admin_guide.html#cluster-telemetry-and-monitoring) provides general machine statistics, such as load average, socket statistics, /proc/meminfo contents, and so on, as well as Swift-specific metrics:" +msgstr "" + +#: ./doc/admin-guide-cloud/section_object-storage-monitoring.xml:35(para) +msgid "The MD5 sum of each ring file." +msgstr "" + +#: ./doc/admin-guide-cloud/section_object-storage-monitoring.xml:38(para) +msgid "The most recent object replication time." +msgstr "" + +#: ./doc/admin-guide-cloud/section_object-storage-monitoring.xml:41(para) +msgid "Count of each type of quarantined file: Account, container, or object." +msgstr "" + +#: ./doc/admin-guide-cloud/section_object-storage-monitoring.xml:45(para) +msgid "Count of “async_pendings” (deferred container updates) on disk." +msgstr "" + +#: ./doc/admin-guide-cloud/section_object-storage-monitoring.xml:49(para) +msgid "Swift Recon is middleware that is installed in the object servers pipeline and takes one required option: A local cache directory. To track async_pendings, you must set up an additional cron job for each object server. You access data by either sending HTTP requests directly to the object server or using the command-line client." +msgstr "" + +#: ./doc/admin-guide-cloud/section_object-storage-monitoring.xml:57(para) +msgid "There are some good Object Storage cluster statistics but the general server metrics overlap with existing server monitoring systems. To get the Swift-specific metrics into a monitoring system, they must be polled. Swift Recon essentially acts as a middleware metrics collector. The process that feeds metrics to your statistics system, such as collectd and gmond, probably already runs on the storage node. So, you can choose to either talk to Swift Recon or collect the metrics directly." +msgstr "" + +#: ./doc/admin-guide-cloud/section_object-storage-monitoring.xml:69(title) +msgid "Swift-Informant" +msgstr "" + +#: ./doc/admin-guide-cloud/section_object-storage-monitoring.xml:70(para) +msgid "Florian Hines developed the Swift-Informant middleware (see http://pandemicsyn.posterous.com/swift-informant-statsd-getting-realtime-telem) to get real-time visibility into Object Storage client requests. It sits in the pipeline for the proxy server, and after each request to the proxy server, sends three metrics to a StatsD server (see http://codeascraft.etsy.com/2011/02/15/measure-anything-measure-everything/):" +msgstr "" + +#: ./doc/admin-guide-cloud/section_object-storage-monitoring.xml:82(para) +msgid "A counter increment for a metric like obj.GET.200 or cont.PUT.404." +msgstr "" + +#: ./doc/admin-guide-cloud/section_object-storage-monitoring.xml:87(para) +msgid "Timing data for a metric like acct.GET.200 or obj.GET.200. [The README says the metrics look like duration.acct.GET.200, but I do not see the duration in the code. I am not sure what the Etsy server does but our StatsD server turns timing metrics into five derivative metrics with new segments appended, so it probably works as coded. The first metric turns into acct.GET.200.lower, acct.GET.200.upper, acct.GET.200.mean, acct.GET.200.upper_90, and acct.GET.200.count]." +msgstr "" + +#: ./doc/admin-guide-cloud/section_object-storage-monitoring.xml:104(para) +msgid "A counter increase by the bytes transferred for a metric like tfer.obj.PUT.201." +msgstr "" + +#: ./doc/admin-guide-cloud/section_object-storage-monitoring.xml:109(para) +msgid "This is good for getting a feel for the quality of service clients are experiencing with the timing metrics, as well as getting a feel for the volume of the various permutations of request server type, command, and response code. Swift-Informant also requires no change to core Object Storage code because it is implemented as middleware. However, it gives you no insight into the workings of the cluster past the proxy server. If the responsiveness of one storage node degrades, you can only see that some of your requests are bad, either as high latency or error status codes. You do not know exactly why or where that request tried to go. Maybe the container server in question was on a good node but the object server was on a different, poorly-performing node." +msgstr "" + +#: ./doc/admin-guide-cloud/section_object-storage-monitoring.xml:125(title) +msgid "Statsdlog" +msgstr "" + +#: ./doc/admin-guide-cloud/section_object-storage-monitoring.xml:126(para) +msgid "Florian’s Statsdlog project increments StatsD counters based on logged events. Like Swift-Informant, it is also non-intrusive, but statsdlog can track events from all Object Storage daemons, not just proxy-server. The daemon listens to a UDP stream of syslog messages and StatsD counters are incremented when a log line matches a regular expression. Metric names are mapped to regex match patterns in a JSON file, allowing flexible configuration of what metrics are extracted from the log stream." +msgstr "" + +#: ./doc/admin-guide-cloud/section_object-storage-monitoring.xml:137(para) +msgid "Currently, only the first matching regex triggers a StatsD counter increment, and the counter is always incremented by one. There is no way to increment a counter by more than one or send timing data to StatsD based on the log line content. The tool could be extended to handle more metrics for each line and data extraction, including timing data. But a coupling would still exist between the log textual format and the log parsing regexes, which would themselves be more complex to support multiple matches for each line and data extraction. Also, log processing introduces a delay between the triggering event and sending the data to StatsD. It would be preferable to increment error counters where they occur and send timing data as soon as it is known to avoid coupling between a log string and a parsing regex and prevent a time delay between events and sending data to StatsD." +msgstr "" + +#: ./doc/admin-guide-cloud/section_object-storage-monitoring.xml:153(para) +msgid "The next section describes another method for gathering Object Storage operational metrics." +msgstr "" + +#: ./doc/admin-guide-cloud/section_object-storage-monitoring.xml:157(title) +msgid "Swift StatsD logging" +msgstr "" + +#: ./doc/admin-guide-cloud/section_object-storage-monitoring.xml:158(para) +msgid "StatsD (see http://codeascraft.etsy.com/2011/02/15/measure-anything-measure-everything/) was designed for application code to be deeply instrumented; metrics are sent in real-time by the code that just noticed or did something. The overhead of sending a metric is extremely low: a sendto of one UDP packet. If that overhead is still too high, the StatsD client library can send only a random portion of samples and StatsD approximates the actual number when flushing metrics upstream." +msgstr "" + +#: ./doc/admin-guide-cloud/section_object-storage-monitoring.xml:169(para) +msgid "To avoid the problems inherent with middleware-based monitoring and after-the-fact log processing, the sending of StatsD metrics is integrated into Object Storage itself. The submitted change set (see https://review.openstack.org/#change,6058) currently reports 124 metrics across 15 Object Storage daemons and the tempauth middleware. Details of the metrics tracked are in the Administrator's Guide." +msgstr "" + +#: ./doc/admin-guide-cloud/section_object-storage-monitoring.xml:180(para) +msgid "The sending of metrics is integrated with the logging framework. To enable, configure log_statsd_host in the relevant config file. You can also specify the port and a default sample rate. The specified default sample rate is used unless a specific call to a statsd logging method (see the list below) overrides it. Currently, no logging calls override the sample rate, but it is conceivable that some metrics may require accuracy (sample_rate == 1) while others may not." +msgstr "" + +#: ./doc/admin-guide-cloud/section_object-storage-monitoring.xml:195(para) +msgid "Then the LogAdapter object returned by get_logger(), usually stored in self.logger, has these new methods:" +msgstr "" + +#: ./doc/admin-guide-cloud/section_object-storage-monitoring.xml:201(para) +msgid "set_statsd_prefix(self, prefix) Sets the client library stat prefix value which gets prefixed to every metric. The default prefix is the “name” of the logger (such as, . “object-server”, “container-auditor”, etc.). This is currently used to turn “proxy-server” into one of “proxy-server.Account”, “proxy-server.Container”, or “proxy-server.Object” as soon as the Controller object is determined and instantiated for the request." +msgstr "" + +#: ./doc/admin-guide-cloud/section_object-storage-monitoring.xml:213(para) +msgid "update_stats(self, metric, amount, sample_rate=1) Increments the supplied metric by the given amount. This is used when you need to add or subtract more that one from a counter, like incrementing “suffix.hashes” by the number of computed hashes in the object replicator." +msgstr "" + +#: ./doc/admin-guide-cloud/section_object-storage-monitoring.xml:222(para) +msgid "increment(self, metric, sample_rate=1) Increments the given counter metric by one." +msgstr "" + +#: ./doc/admin-guide-cloud/section_object-storage-monitoring.xml:227(para) +msgid "decrement(self, metric, sample_rate=1) Lowers the given counter metric by one." +msgstr "" + +#: ./doc/admin-guide-cloud/section_object-storage-monitoring.xml:232(para) +msgid "timing(self, metric, timing_ms, sample_rate=1) Record that the given metric took the supplied number of milliseconds." +msgstr "" + +#: ./doc/admin-guide-cloud/section_object-storage-monitoring.xml:238(para) +msgid "timing_since(self, metric, orig_time, sample_rate=1) Convenience method to record a timing metric whose value is “now” minus an existing timestamp." +msgstr "" + +#: ./doc/admin-guide-cloud/section_object-storage-monitoring.xml:244(para) +msgid "Note that these logging methods may safely be called anywhere you have a logger object. If StatsD logging has not been configured, the methods are no-ops. This avoids messy conditional logic each place a metric is recorded. These example usages show the new logging methods:" +msgstr "" + +#: ./doc/admin-guide-cloud/section_object-storage-monitoring.xml:287(para) +msgid "The development team of StatsD wanted to use the pystatsd client library (not to be confused with a similar-looking project also hosted on GitHub), but the released version on PyPi was missing two desired features the latest version in GitHub had: the ability to configure a metrics prefix in the client object and a convenience method for sending timing data between “now” and a “start” timestamp you already have. So they just implemented a simple StatsD client library from scratch with the same interface. This has the nice fringe benefit of not introducing another external library dependency into Object Storage." +msgstr "" + +#: ./doc/admin-guide-cloud/section_ts_failed_attach_vol_after_detach.xml:5(title) ./doc/admin-guide-cloud/section_ts_HTTP_bad_req_in_cinder_vol_log.xml:5(title) +msgid "Failed to attach volume after detaching" +msgstr "" + +#: ./doc/admin-guide-cloud/section_ts_failed_attach_vol_after_detach.xml:9(para) +msgid "Failed to attach a volume after detaching the same volume." +msgstr "" + +#: ./doc/admin-guide-cloud/section_ts_failed_attach_vol_after_detach.xml:15(para) +msgid "You must change the device name on the command. The VM might not clean up after a command runs. This example shows how the command fails when you use the vdb, vdc, or vdd device names:" +msgstr "" + +#: ./doc/admin-guide-cloud/section_ts_failed_attach_vol_after_detach.xml:34(para) +msgid "You might also have this problem after attaching and detaching the same volume from the same VM with the same mount point multiple times. In this case, restart the KVM host." +msgstr "" + +#: ./doc/admin-guide-cloud/section_ts_non_existent_host.xml:4(title) +msgid "Non-existent host" +msgstr "" + +#: ./doc/admin-guide-cloud/section_ts_non_existent_host.xml:7(para) +msgid "This error could be caused by a volume being exported outside of OpenStack using a host name different from the system name that OpenStack expects. This error could be displayed with the IQN if the host was exported using iSCSI." +msgstr "" + +#: ./doc/admin-guide-cloud/section_ts_non_existent_host.xml:15(para) +msgid "Host names constructed by the driver use just the local hostname, not the fully qualified domain name (FQDN) of the Compute host. For example, if the FQDN was myhost.example.com, just myhost would be used as the 3PAR hostname. IP addresses are not allowed as host names on the 3PAR storage server." +msgstr "" + +#. When image changes, this message will be marked fuzzy or untranslated for you. +#. It doesn't matter what you translate it to: it's not used at all. +#: ./doc/admin-guide-cloud/section_networking-scenarios.xml:38(None) ./doc/admin-guide-cloud/section_networking-scenarios.xml:406(None) +msgid "@@image: '../common/figures/under-the-hood-scenario-1.png'; md5=6c8c80ff7e23cc2c7c7e1aa66e1fd8c0" +msgstr "" + +#. When image changes, this message will be marked fuzzy or untranslated for you. +#. It doesn't matter what you translate it to: it's not used at all. +#: ./doc/admin-guide-cloud/section_networking-scenarios.xml:79(None) +msgid "@@image: '../common/figures/under-the-hood-scenario-1-ovs-compute.png'; md5=46509fcb546df0f43adb5350f2dd9fab" +msgstr "" + +#. When image changes, this message will be marked fuzzy or untranslated for you. +#. It doesn't matter what you translate it to: it's not used at all. +#: ./doc/admin-guide-cloud/section_networking-scenarios.xml:172(None) +msgid "@@image: '../common/figures/under-the-hood-scenario-1-ovs-network.png'; md5=8eea1c1dbde433c46666c985751c3276" +msgstr "" + +#. When image changes, this message will be marked fuzzy or untranslated for you. +#. It doesn't matter what you translate it to: it's not used at all. +#: ./doc/admin-guide-cloud/section_networking-scenarios.xml:252(None) +msgid "@@image: '../common/figures/under-the-hood-scenario-1-ovs-netns.png'; md5=de52650e491e4dc2946e827cd93e0a85" +msgstr "" + +#. When image changes, this message will be marked fuzzy or untranslated for you. +#. It doesn't matter what you translate it to: it's not used at all. +#: ./doc/admin-guide-cloud/section_networking-scenarios.xml:298(None) ./doc/admin-guide-cloud/section_networking-scenarios.xml:503(None) +msgid "@@image: '../common/figures/under-the-hood-scenario-2.png'; md5=148feb87744e7b04da21ec4f17503c75" +msgstr "" + +#. When image changes, this message will be marked fuzzy or untranslated for you. +#. It doesn't matter what you translate it to: it's not used at all. +#: ./doc/admin-guide-cloud/section_networking-scenarios.xml:340(None) +msgid "@@image: '../common/figures/under-the-hood-scenario-2-ovs-compute.png'; md5=94603b4ec7904ac04bc1ed81a2d38f79" +msgstr "" + +#. When image changes, this message will be marked fuzzy or untranslated for you. +#. It doesn't matter what you translate it to: it's not used at all. +#: ./doc/admin-guide-cloud/section_networking-scenarios.xml:355(None) +msgid "@@image: '../common/figures/under-the-hood-scenario-2-ovs-network.png'; md5=80aa67268b5ce7deddc41845e6313634" +msgstr "" + +#. When image changes, this message will be marked fuzzy or untranslated for you. +#. It doesn't matter what you translate it to: it's not used at all. +#: ./doc/admin-guide-cloud/section_networking-scenarios.xml:364(None) +msgid "@@image: '../common/figures/under-the-hood-scenario-2-ovs-netns.png'; md5=d8878beff47037240d6f8c48f8d4d4c3" +msgstr "" + +#. When image changes, this message will be marked fuzzy or untranslated for you. +#. It doesn't matter what you translate it to: it's not used at all. +#: ./doc/admin-guide-cloud/section_networking-scenarios.xml:446(None) +msgid "@@image: '../common/figures/under-the-hood-scenario-1-linuxbridge-compute.png'; md5=8270a65d291a628c7091997414046167" +msgstr "" + +#. When image changes, this message will be marked fuzzy or untranslated for you. +#. It doesn't matter what you translate it to: it's not used at all. +#: ./doc/admin-guide-cloud/section_networking-scenarios.xml:484(None) +msgid "@@image: '../common/figures/under-the-hood-scenario-1-linuxbridge-network.png'; md5=bd78453eb11ffebddf55484ca2cd125e" +msgstr "" + +#. When image changes, this message will be marked fuzzy or untranslated for you. +#. It doesn't matter what you translate it to: it's not used at all. +#: ./doc/admin-guide-cloud/section_networking-scenarios.xml:491(None) +msgid "@@image: '../common/figures/under-the-hood-scenario-1-linuxbridge-netns.png'; md5=915d10e90cbb18e887b4d5eb5ea15e58" +msgstr "" + +#. When image changes, this message will be marked fuzzy or untranslated for you. +#. It doesn't matter what you translate it to: it's not used at all. +#: ./doc/admin-guide-cloud/section_networking-scenarios.xml:546(None) +msgid "@@image: '../common/figures/under-the-hood-scenario-2-linuxbridge-compute.png'; md5=f68f0baeba932b219574e55853bd2300" +msgstr "" + +#. When image changes, this message will be marked fuzzy or untranslated for you. +#. It doesn't matter what you translate it to: it's not used at all. +#: ./doc/admin-guide-cloud/section_networking-scenarios.xml:559(None) +msgid "@@image: '../common/figures/under-the-hood-scenario-2-linuxbridge-network.png'; md5=25f818f7f9148152e5a8dbf6d530dcf6" +msgstr "" + +#. When image changes, this message will be marked fuzzy or untranslated for you. +#. It doesn't matter what you translate it to: it's not used at all. +#: ./doc/admin-guide-cloud/section_networking-scenarios.xml:567(None) +msgid "@@image: '../common/figures/under-the-hood-scenario-2-linuxbridge-netns.png'; md5=cdc0bd4b3e7988f7fedffefae4dae9d0" +msgstr "" + +#. When image changes, this message will be marked fuzzy or untranslated for you. +#. It doesn't matter what you translate it to: it's not used at all. +#: ./doc/admin-guide-cloud/section_networking-scenarios.xml:599(None) +msgid "@@image: '../common/figures/ml2_without_l2pop_full_mesh.png'; md5=881485c0686f20b82967d5b817932952" +msgstr "" + +#. When image changes, this message will be marked fuzzy or untranslated for you. +#. It doesn't matter what you translate it to: it's not used at all. +#: ./doc/admin-guide-cloud/section_networking-scenarios.xml:609(None) +msgid "@@image: '../common/figures/ml2_without_l2pop_partial_mesh.png'; md5=66fe83560a3e1880ffe3a85d80538f83" +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking-scenarios.xml:6(title) +msgid "Networking scenarios" +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking-scenarios.xml:7(para) +msgid "This chapter describes two networking scenarios and how the Open vSwitch plug-in and the Linux bridging plug-in implement these scenarios." +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking-scenarios.xml:12(para) +msgid "This section describes how the Open vSwitch plug-in implements the Networking abstractions." +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking-scenarios.xml:16(para) +msgid "This example uses VLAN isolation on the switches to isolate tenant networks. This configuration labels the physical network associated with the public network as physnet1, and the physical network associated with the data network as physnet2, which leads to the following configuration options in ovs_neutron_plugin.ini:" +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking-scenarios.xml:29(title) ./doc/admin-guide-cloud/section_networking-scenarios.xml:397(title) +msgid "Scenario 1: one tenant, two networks, one router" +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking-scenarios.xml:30(para) +msgid "The first scenario has two private networks (net01, and net02), each with one subnet (net01_subnet01: 192.168.101.0/24, net02_subnet01, 192.168.102.0/24). Both private networks are attached to a router that connects them to the public network (10.64.201.0/24)." +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking-scenarios.xml:41(para) ./doc/admin-guide-cloud/section_networking-scenarios.xml:409(para) +msgid "Under the service tenant, create the shared router, define the public network, and set it as the default gateway of the router" +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking-scenarios.xml:52(para) ./doc/admin-guide-cloud/section_networking-scenarios.xml:420(para) +msgid "Under the demo user tenant, create the private network net01 and corresponding subnet, and connect it to the router01 router. Configure it to use VLAN ID 101 on the physical switch." +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking-scenarios.xml:63(para) ./doc/admin-guide-cloud/section_networking-scenarios.xml:431(para) +msgid "Similarly, for net02, using VLAN ID 102 on the physical switch:" +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking-scenarios.xml:73(title) ./doc/admin-guide-cloud/section_networking-scenarios.xml:440(title) +msgid "Scenario 1: Compute host config" +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking-scenarios.xml:74(para) +msgid "The following figure shows how to configure various Linux networking devices on the compute host:" +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking-scenarios.xml:84(title) ./doc/admin-guide-cloud/section_networking-scenarios.xml:451(title) +msgid "Types of network devices" +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking-scenarios.xml:85(para) +msgid "There are four distinct type of virtual networking devices: TAP devices, veth pairs, Linux bridges, and Open vSwitch bridges. For an ethernet frame to travel from eth0 of virtual machine vm01 to the physical network, it must pass through nine devices inside of the host: TAP vnet0, Linux bridge qbrnnn, veth pair (qvbnnn, qvonnn), Open vSwitch bridge br-int, veth pair (int-br-eth1, phy-br-eth1), and, finally, the physical network interface card eth1." +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking-scenarios.xml:96(para) ./doc/admin-guide-cloud/section_networking-scenarios.xml:460(para) +msgid "A TAP device, such as vnet0 is how hypervisors such as KVM and Xen implement a virtual network interface card (typically called a VIF or vNIC). An ethernet frame sent to a TAP device is received by the guest operating system." +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking-scenarios.xml:100(para) +msgid "A veth pair is a pair of directly connected virtual network interfaces. An ethernet frame sent to one end of a veth pair is received by the other end of a veth pair. Networking uses veth pairs as virtual patch cables to make connections between virtual bridges." +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking-scenarios.xml:104(para) ./doc/admin-guide-cloud/section_networking-scenarios.xml:473(para) +msgid "A Linux bridge behaves like a hub: you can connect multiple (physical or virtual) network interfaces devices to a Linux bridge. Any ethernet frames that come in from one interface attached to the bridge is transmitted to all of the other devices." +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking-scenarios.xml:108(para) +msgid "An Open vSwitch bridge behaves like a virtual switch: network interface devices connect to Open vSwitch bridge's ports, and the ports can be configured much like a physical switch's ports, including VLAN configurations." +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking-scenarios.xml:114(title) +msgid "Integration bridge" +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking-scenarios.xml:115(para) +msgid "The br-int OpenvSwitch bridge is the integration bridge: all guests running on the compute host connect to this bridge. Networking implements isolation across these guests by configuring the br-int ports." +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking-scenarios.xml:121(title) +msgid "Physical connectivity bridge" +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking-scenarios.xml:122(para) +msgid "The br-eth1 bridge provides connectivity to the physical network interface card, eth1. It connects to the integration bridge by a veth pair: (int-br-eth1, phy-br-eth1)." +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking-scenarios.xml:127(title) +msgid "VLAN translation" +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking-scenarios.xml:128(para) +msgid "In this example, net01 and net02 have VLAN ids of 1 and 2, respectively. However, the physical network in our example only supports VLAN IDs in the range 101 through 110. The Open vSwitch agent is responsible for configuring flow rules on br-int and br-eth1 to do VLAN translation. When br-eth1 receives a frame marked with VLAN ID 1 on the port associated with phy-br-eth1, it modifies the VLAN ID in the frame to 101. Similarly, when br-int receives a frame marked with VLAN ID 101 on the port associated with int-br-eth1, it modifies the VLAN ID in the frame to 1." +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking-scenarios.xml:139(title) +msgid "Security groups: iptables and Linux bridges" +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking-scenarios.xml:140(para) +msgid "Ideally, the TAP device vnet0 would be connected directly to the integration bridge, br-int. Unfortunately, this isn't possible because of how OpenStack security groups are currently implemented. OpenStack uses iptables rules on the TAP devices such as vnet0 to implement security groups, and Open vSwitch is not compatible with iptables rules that are applied directly on TAP devices that are connected to an Open vSwitch port." +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking-scenarios.xml:147(para) +msgid "Networking uses an extra Linux bridge and a veth pair as a workaround for this issue. Instead of connecting vnet0 to an Open vSwitch bridge, it is connected to a Linux bridge, qbrXXX. This bridge is connected to the integration bridge, br-int, through the (qvbXXX, qvoXXX) veth pair." +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking-scenarios.xml:157(title) ./doc/admin-guide-cloud/section_networking-scenarios.xml:480(title) +msgid "Scenario 1: Network host config" +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking-scenarios.xml:158(para) +msgid "The network host runs the neutron-openvswitch-plugin-agent, the neutron-dhcp-agent, neutron-l3-agent, and neutron-metadata-agent services." +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking-scenarios.xml:160(para) +msgid "On the network host, assume that eth0 is connected to the external network, and eth1 is connected to the data network, which leads to the following configuration in the ovs_neutron_plugin.ini file: The following figure shows the network devices on the network host:" +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking-scenarios.xml:175(para) +msgid "As on the compute host, there is an Open vSwitch integration bridge (br-int) and an Open vSwitch bridge connected to the data network (br-eth1), and the two are connected by a veth pair, and the neutron-openvswitch-plugin-agent configures the ports on both switches to do VLAN translation." +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking-scenarios.xml:180(para) +msgid "An additional Open vSwitch bridge, br-ex, connects to the physical interface that is connected to the external network. In this example, that physical interface is eth0." +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking-scenarios.xml:183(para) +msgid "While the integration bridge and the external bridge are connected by a veth pair (int-br-ex, phy-br-ex), this example uses layer 3 connectivity to route packets from the internal networks to the public network: no packets traverse that veth pair in this example." +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking-scenarios.xml:187(title) +msgid "Open vSwitch internal ports" +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking-scenarios.xml:188(para) +msgid "The network host uses Open vSwitch internal ports. Internal ports enable you to assign one or more IP addresses to an Open vSwitch bridge. In previous example, the br-int bridge has four internal ports: tapXXX, qr-YYY, qr-ZZZ, and tapWWW. Each internal port has a separate IP address associated with it. An internal port, qg-VVV, is on the br-ex bridge." +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking-scenarios.xml:201(para) +msgid "By default, The Networking DHCP agent uses a process called dnsmasq to provide DHCP services to guests. Networking must create an internal port for each network that requires DHCP services and attach a dnsmasq process to that port. In the previous example, the tapXXX interface is on net01_subnet01, and the tapWWW interface is on net02_subnet01." +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking-scenarios.xml:211(title) +msgid "L3 agent (routing)" +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking-scenarios.xml:212(para) +msgid "The Networking L3 agent uses Open vSwitch internal ports to implement routing and relies on the network host to route the packets across the interfaces. In this example, the qr-YYY interface is on net01_subnet01 and has the IP address 192.168.101.1/24. The qr-ZZZ, interface is on net02_subnet01 and has the IP address 192.168.102.1/24. The qg-VVV interface has the IP address 10.64.201.254/24. Because each of these interfaces is visible to the network host operating system, the network host routes the packets across the interfaces, as long as an administrator has enabled IP forwarding." +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking-scenarios.xml:224(para) +msgid "The L3 agent uses iptables to implement floating IPs to do the network address translation (NAT)." +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking-scenarios.xml:228(title) +msgid "Overlapping subnets and network namespaces" +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking-scenarios.xml:229(para) +msgid "One problem with using the host to implement routing is that one of the Networking subnets might overlap with one of the physical networks that the host uses. For example, if the management network is implemented on eth2 and also happens to be on the 192.168.101.0/24 subnet, routing problems will occur because the host can't determine whether to send a packet on this subnet to qr-YYY or eth2. If end users are permitted to create their own logical networks and subnets, you must design the system so that such collisions do not occur." +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking-scenarios.xml:238(para) +msgid "Networking uses Linux network namespaces to prevent collisions between the physical networks on the network host, and the logical networks used by the virtual machines. It also prevents collisions across different logical networks that are not routed to each other, as the following scenario shows." +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking-scenarios.xml:243(para) +msgid "A network namespace is an isolated environment with its own networking stack. A network namespace has its own network interfaces, routes, and iptables rules. Consider it a chroot jail, except for networking instead of for a file system. LXC (Linux containers) use network namespaces to implement networking virtualization." +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking-scenarios.xml:248(para) +msgid "Networking creates network namespaces on the network host to avoid subnet collisions." +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking-scenarios.xml:257(para) +msgid "qdhcp-aaa: contains the tapXXX interface and the dnsmasq process that listens on that interface to provide DHCP services for net01_subnet01. This allows overlapping IPs between net01_subnet01 and any other subnets on the network host." +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking-scenarios.xml:267(para) +msgid "qrouter-bbbb: contains the qr-YYY, qr-ZZZ, and qg-VVV interfaces, and the corresponding routes. This namespace implements router01 in our example." +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking-scenarios.xml:276(para) +msgid "qdhcp-ccc: contains the tapWWW interface and the dnsmasq process that listens on that interface, to provide DHCP services for net02_subnet01. This allows overlapping IPs between net02_subnet01 and any other subnets on the network host." +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking-scenarios.xml:255(para) +msgid "In this example, there are three network namespaces, as shown in the figure above:" +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking-scenarios.xml:290(title) ./doc/admin-guide-cloud/section_networking-scenarios.xml:497(title) +msgid "Scenario 2: two tenants, two networks, two routers" +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking-scenarios.xml:292(para) +msgid "In this scenario, tenant A and tenant B each have a network with one subnet and one router that connects the tenants to the public Internet." +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking-scenarios.xml:301(para) ./doc/admin-guide-cloud/section_networking-scenarios.xml:506(para) +msgid "Under the service tenant, define the public network:" +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking-scenarios.xml:309(para) ./doc/admin-guide-cloud/section_networking-scenarios.xml:514(para) +msgid "Under the tenantA user tenant, create the tenant router and set its gateway for the public network. Then, define private network net01 using VLAN ID 102 on the physical switch, along with its subnet, and connect it to the router. " +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking-scenarios.xml:322(para) ./doc/admin-guide-cloud/section_networking-scenarios.xml:527(para) +msgid "Similarly, for tenantB, create a router and another network, using VLAN ID 102 on the physical switch:" +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking-scenarios.xml:335(title) ./doc/admin-guide-cloud/section_networking-scenarios.xml:540(title) +msgid "Scenario 2: Compute host config" +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking-scenarios.xml:336(para) +msgid "The following figure shows how to configure Linux networking devices on the Compute host:" +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking-scenarios.xml:343(para) +msgid "The Compute host configuration resembles the configuration in scenario 1. However, in scenario 1, a guest connects to two subnets while in this scenario, the subnets belong to different tenants." +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking-scenarios.xml:350(title) ./doc/admin-guide-cloud/section_networking-scenarios.xml:554(title) +msgid "Scenario 2: Network host config" +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking-scenarios.xml:351(para) ./doc/admin-guide-cloud/section_networking-scenarios.xml:555(para) +msgid "The following figure shows the network devices on the network host for the second scenario." +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking-scenarios.xml:358(para) +msgid "In this configuration, the network namespaces are organized to isolate the two subnets from each other as shown in the following figure." +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking-scenarios.xml:367(para) ./doc/admin-guide-cloud/section_networking-scenarios.xml:570(para) +msgid "In this scenario, there are four network namespaces (qhdcp-aaa, qrouter-bbbb, qrouter-cccc, and qhdcp-dddd), instead of three. Since there is no connectivity between the two networks, and so each router is implemented by a separate namespace." +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking-scenarios.xml:379(para) +msgid "This section describes how the Linux Bridge plug-in implements the Networking abstractions. For information about DHCP and L3 agents, see ." +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking-scenarios.xml:384(para) +msgid "This example uses VLAN isolation on the switches to isolate tenant networks. This configuration labels the physical network associated with the public network as physnet1, and the physical network associated with the data network as physnet2, which leads to the following configuration options in linuxbridge_conf.ini:" +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking-scenarios.xml:398(para) +msgid "The first scenario has two private networks (net01, and net02), each with one subnet (net01_subnet01: 192.168.101.0/24, net02_subnet01, 192.168.102.0/24). Both private networks are attached to a router that contains them to the public network (10.64.201.0/24)." +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking-scenarios.xml:441(para) +msgid "The following figure shows how to configure the various Linux networking devices on the compute host." +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking-scenarios.xml:452(para) +msgid "There are three distinct type of virtual networking devices: TAP devices, VLAN devices, and Linux bridges. For an ethernet frame to travel from eth0 of virtual machine vm01, to the physical network, it must pass through four devices inside of the host: TAP vnet0, Linux bridge brqXXX, VLAN eth1.101), and, finally, the physical network interface card eth1." +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking-scenarios.xml:464(para) +msgid "A VLAN device is associated with a VLAN tag attaches to an existing interface device and adds or removes VLAN tags. In the preceding example, VLAN device eth1.101 is associated with VLAN ID 101 and is attached to interface eth1. Packets received from the outside by eth1 with VLAN tag 101 will be passed to device eth1.101, which will then strip the tag. In the other direction, any ethernet frame sent directly to eth1.101 will have VLAN tag 101 added and will be forward to eth1 for sending out to the network." +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking-scenarios.xml:481(para) +msgid "The following figure shows the network devices on the network host." +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking-scenarios.xml:487(para) +msgid "The following figure shows how the Linux Bridge plug-in uses network namespaces to provide isolation." +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking-scenarios.xml:488(para) +msgid "veth pairs form connections between the Linux bridges and the network namespaces." +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking-scenarios.xml:498(para) +msgid "The second scenario has two tenants (A, B). Each tenant has a network with one subnet, and each one has a router that connects them to the public Internet." +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking-scenarios.xml:541(para) +msgid "The following figure shows how the various Linux networking devices would be configured on the compute host under this scenario." +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking-scenarios.xml:549(para) +msgid "The configuration on the compute host is very similar to the configuration in scenario 1. The only real difference is that scenario 1 had a guest that was connected to two subnets, and in this scenario, the subnets belong to different tenants." +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking-scenarios.xml:562(para) +msgid "The main difference between the configuration in this scenario and the previous one is the organization of the network namespaces, in order to provide isolation across the two subnets, as shown in the following figure." +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking-scenarios.xml:582(para) +msgid "The Modular Layer 2 plugin allows OpenStack Networking to simultaneously utilize the variety of layer 2 networking technologies found in complex real-world data centers. It currently includes drivers for the local, flat, vlan, gre and vxlan network types and works with the existing Open vSwitch, Linux Bridge, and HyperV L2 agents. The ML2 plug-in can be extended through mechanism drivers, multiple mechanisms can be used simultaneously. This section describes different ML2 plug-in / agents configurations with different type drivers and mechanism drivers." +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking-scenarios.xml:592(title) +msgid "ML2 with L2 population mechanism driver" +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking-scenarios.xml:593(para) +msgid "Current Open vSwitch and Linux Bridge tunneling implementations broadcast to every agent, even if they don’t host the corresponding network as illustrated below." +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking-scenarios.xml:602(para) +msgid "As broadcast emulation on overlay is costly, it may be better to avoid its use for mac learning and ARP resolution. This supposes the use of proxy ARP on the agent to answer VM requests, and to populate forwarding table. Currently only the Linux Bridge Agent implements an ARP proxy. The prepopulation limits L2 broadcasts in overlay, however it may anyway be necessary to provide broadcast emulation. This is achieved by sending broadcasts packets over unicasts only to the relevant agents as illustrated below.The partial-mesh is available with the Open vSwitch and the Linux Bridge agent. The following scenarios will use the L2 population mechanism driver with an Open vSwitch agent and a Linux Bridge agent. To enable the l2 population driver we have to add it in the list of mechanism drivers. We also need to have at least one tunneling type driver enabled, either GRE, VXLAN or both. Below configuration options that we have to set in ml2_conf.ini:" +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking-scenarios.xml:621(title) +msgid "Scenario 1: L2 population with Open vSwitch agent" +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking-scenarios.xml:625(replaceable) ./doc/admin-guide-cloud/section_networking-scenarios.xml:637(replaceable) +msgid "192.168.1.10" +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking-scenarios.xml:628(replaceable) ./doc/admin-guide-cloud/section_networking_adv_features.xml:184(literal) ./doc/admin-guide-cloud/section_networking_adv_features.xml:191(literal) ./doc/admin-guide-cloud/section_networking_adv_features.xml:208(literal) +msgid "gre" +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking-scenarios.xml:628(replaceable) +msgid "vxlan" +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking-scenarios.xml:622(para) +msgid "We have to enable the l2 population extension on the Open vSwitch agent side and we also have to set the parameter and the ml2_conf.ini." +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking-scenarios.xml:632(title) +msgid "Scenario 2: L2 population with Linux Bridge agent" +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking-scenarios.xml:633(para) +msgid "We have to enable the l2 population extension on the agent side and we also have to set the local_ip parameter and enable VXLAN in ml2_conf.ini." +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking-scenarios.xml:641(title) +msgid "Enable security group API" +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking-scenarios.xml:642(para) +msgid "Since the ML2 plugin can concurrently support different L2 agents (or other mechanisms) with different configuration files, the actual value in the ml2_conf.ini file does not matter in the server, but must be set to a non-default value in the ml2 configuration to enable the securitygroup extension. To enable securitygroup API, edit the ml2_conf.ini file: Each L2 agent configuration file (such as ovs_neutron_plugin.ini or linuxbridge_conf.ini) should contain the appropriate value for that agent. To disable securitygroup API, edit the ml2_conf.ini file: Also, each L2 agent configuration file (such as ovs_neutron_plugin.ini or linuxbridge_conf.ini) should contain this value in parameter for that agent." +msgstr "" + +#: ./doc/admin-guide-cloud/ch_networking.xml:7(title) +msgid "Networking" +msgstr "" + +#: ./doc/admin-guide-cloud/ch_networking.xml:8(para) +msgid "Learn Networking concepts, architecture, and basic and advanced neutron and nova command-line interface (CLI) cloud." +msgstr "" + +#: ./doc/admin-guide-cloud/bk-admin-guide-cloud.xml:8(title) +msgid "OpenStack Cloud Administrator Guide" +msgstr "" + +#: ./doc/admin-guide-cloud/bk-admin-guide-cloud.xml:10(titleabbrev) +msgid "Cloud Administrator Guide" +msgstr "" + +#: ./doc/admin-guide-cloud/bk-admin-guide-cloud.xml:18(orgname) ./doc/admin-guide-cloud/bk-admin-guide-cloud.xml:23(holder) +msgid "OpenStack Foundation" +msgstr "" + +#: ./doc/admin-guide-cloud/bk-admin-guide-cloud.xml:22(year) +msgid "2013" +msgstr "" + +#: ./doc/admin-guide-cloud/bk-admin-guide-cloud.xml:25(releaseinfo) +msgid "havana" +msgstr "" + +#: ./doc/admin-guide-cloud/bk-admin-guide-cloud.xml:26(productname) +msgid "OpenStack" +msgstr "" + +#: ./doc/admin-guide-cloud/bk-admin-guide-cloud.xml:30(remark) +msgid "Copyright details are filled in by the template." +msgstr "" + +#: ./doc/admin-guide-cloud/bk-admin-guide-cloud.xml:36(remark) +msgid "Remaining licensing details are filled in by the template." +msgstr "" + +#: ./doc/admin-guide-cloud/bk-admin-guide-cloud.xml:41(para) +msgid "OpenStack offers open source software for cloud administrators to manage and troubleshoot an OpenStack cloud." +msgstr "" + +#: ./doc/admin-guide-cloud/bk-admin-guide-cloud.xml:48(date) +msgid "2013-11-12" +msgstr "" + +#: ./doc/admin-guide-cloud/bk-admin-guide-cloud.xml:52(para) +msgid "Adds options for tuning operational status synchronization in the NVP plug-in." +msgstr "" + +#: ./doc/admin-guide-cloud/bk-admin-guide-cloud.xml:60(date) +msgid "2013-10-17" +msgstr "" + +#: ./doc/admin-guide-cloud/bk-admin-guide-cloud.xml:64(para) +msgid "Havana release." +msgstr "" + +#: ./doc/admin-guide-cloud/bk-admin-guide-cloud.xml:70(date) +msgid "2013-09-05" +msgstr "" + +#: ./doc/admin-guide-cloud/bk-admin-guide-cloud.xml:74(para) +msgid "Moves object storage monitoring section to this guide." +msgstr "" + +#: ./doc/admin-guide-cloud/bk-admin-guide-cloud.xml:78(para) +msgid "Removes redundant object storage information." +msgstr "" + +#: ./doc/admin-guide-cloud/bk-admin-guide-cloud.xml:85(date) +msgid "2013-09-03" +msgstr "" + +#: ./doc/admin-guide-cloud/bk-admin-guide-cloud.xml:89(para) +msgid "Moved all but configuration and installation information from these component guides to create the new guide:" +msgstr "" + +#: ./doc/admin-guide-cloud/bk-admin-guide-cloud.xml:95(para) +msgid "OpenStack Compute Administration Guide" +msgstr "" + +#: ./doc/admin-guide-cloud/bk-admin-guide-cloud.xml:99(para) +msgid "OpenStack Networking Administration Guide" +msgstr "" + +#: ./doc/admin-guide-cloud/bk-admin-guide-cloud.xml:103(para) +msgid "OpenStack Object Storage Administration Guide" +msgstr "" + +#: ./doc/admin-guide-cloud/bk-admin-guide-cloud.xml:107(para) +msgid "OpenStack Block Storage Service Administration Guide" +msgstr "" + +#: ./doc/admin-guide-cloud/section_ts_no_emulator_x86_64.xml:4(title) +msgid "Cannot find suitable emulator for x86_64" +msgstr "" + +#: ./doc/admin-guide-cloud/section_ts_no_emulator_x86_64.xml:7(para) +msgid "When you attempt to create a VM, the error shows the VM is in the BUILD then ERROR state." +msgstr "" + +#: ./doc/admin-guide-cloud/section_ts_no_emulator_x86_64.xml:12(para) +msgid "On the KVM host run, cat /proc/cpuinfo. Make sure the vme and svm flags are set." +msgstr "" + +#: ./doc/admin-guide-cloud/section_ts_no_emulator_x86_64.xml:14(para) +msgid "Follow the instructions in the enabling KVM section of the Configuration Reference to enable hardware virtualization support in your BIOS." +msgstr "" + +#. When image changes, this message will be marked fuzzy or untranslated for you. +#. It doesn't matter what you translate it to: it's not used at all. +#: ./doc/admin-guide-cloud/section_networking_arch.xml:132(None) +msgid "@@image: '../common/figures/Neutron-PhysNet-Diagram.png'; md5=ac17dba8837f9d7ba714a692c60e68ab" +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking_arch.xml:4(title) +msgid "Networking architecture" +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking_arch.xml:5(para) +msgid "Before you deploy Networking, it helps to understand the Networking components and how these components interact with each other and other OpenStack services." +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking_arch.xml:9(title) +msgid "Overview" +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking_arch.xml:10(para) +msgid "Networking is a standalone service, just like other OpenStack services such as Compute, Image service, Identity service, or the Dashboard. Like those services, a deployment of Networking often involves deploying several processes on a variety of hosts." +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking_arch.xml:16(para) +msgid "The Networking server uses the neutron-server daemon to expose the Networking API and to pass user requests to the configured Networking plug-in for additional processing. Typically, the plug-in requires access to a database for persistent storage (also similar to other OpenStack services)." +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking_arch.xml:23(para) +msgid "If your deployment uses a controller host to run centralized Compute components, you can deploy the Networking server on that same host. However, Networking is entirely standalone and can be deployed on its own host as well. Depending on your deployment, Networking can also include the following agents." +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking_arch.xml:30(caption) +msgid "Networking agents" +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking_arch.xml:41(emphasis) +msgid "plug-in agent" +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking_arch.xml:43(literal) +msgid "neutron-*-agent" +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking_arch.xml:41(td) ./doc/admin-guide-cloud/section_networking_arch.xml:51(td) ./doc/admin-guide-cloud/section_networking_arch.xml:59(td) ./doc/admin-guide-cloud/section_networking_arch.xml:68(td) +msgid " ()" +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking_arch.xml:44(td) +msgid "Runs on each hypervisor to perform local vswitch configuration. The agent that runs depends on the plug-in that you use, and some plug-ins do not require an agent." +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking_arch.xml:51(emphasis) +msgid "dhcp agent" +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking_arch.xml:53(literal) +msgid "neutron-dhcp-agent" +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking_arch.xml:54(td) +msgid "Provides DHCP services to tenant networks. Some plug-ins use this agent." +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking_arch.xml:59(emphasis) +msgid "l3 agent" +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking_arch.xml:61(literal) +msgid "neutron-l3-agent" +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking_arch.xml:62(td) +msgid "Provides L3/NAT forwarding to provide external network access for VMs on tenant networks. Some plug-ins use this agent." +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking_arch.xml:68(emphasis) +msgid "l3 metering agent" +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking_arch.xml:69(literal) +msgid "neutron-metering-agent" +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking_arch.xml:70(td) +msgid "Provides L3 traffic measurements for tenant networks." +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking_arch.xml:75(para) +msgid "These agents interact with the main neutron process through RPC (for example, rabbitmq or qpid) or through the standard Networking API. Further:" +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking_arch.xml:80(para) +msgid "Networking relies on the Identity service (Keystone) for the authentication and authorization of all API requests." +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking_arch.xml:85(para) +msgid "Compute (Nova) interacts with Networking through calls to its standard API.  As part of creating a VM, the nova-compute service communicates with the Networking API to plug each virtual NIC on the VM into a particular network. " +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking_arch.xml:94(para) +msgid "The Dashboard (Horizon) integrates with the Networking API, enabling administrators and tenant users to create and manage network services through a web-based GUI." +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking_arch.xml:102(title) +msgid "Place services on physical hosts" +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking_arch.xml:103(para) +msgid "Like other OpenStack services, Networking enables cloud administrators to run one or more services on one or more physical devices. At one extreme, the cloud administrator can run all service daemons on a single physical host for evaluation purposes. Alternatively the cloud administrator can run each service on its own physical host and, in some cases, can replicate services across multiple hosts for redundancy. For more information, see the OpenStack Configuration Reference." +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking_arch.xml:116(para) +msgid "A standard architecture includes a cloud controller host, a network gateway host, and a set of hypervisors that run virtual machines. The cloud controller and network gateway can be on the same host. However, if you expect VMs to send significant traffic to or from the Internet, a dedicated network gateway host helps avoid CPU contention between the neutron-l3-agent and other OpenStack services that forward packets." +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking_arch.xml:127(title) +msgid "Network connectivity for physical hosts" +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking_arch.xml:135(para) +msgid "A standard Networking set up has one or more of the following distinct physical data center networks." +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking_arch.xml:141(caption) +msgid "General distinct physical data center networks" +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking_arch.xml:153(emphasis) +msgid "Management network" +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking_arch.xml:155(td) +msgid "Provides internal communication between OpenStack Components. IP addresses on this network should be reachable only within the data center." +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking_arch.xml:162(emphasis) +msgid "Data network" +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking_arch.xml:164(td) +msgid "Provides VM data communication within the cloud deployment. The IP addressing requirements of this network depend on the Networking plug-in that is used." +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking_arch.xml:171(emphasis) +msgid "External network" +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking_arch.xml:173(td) +msgid "Provides VMs with Internet access in some deployment scenarios. Anyone on the Internet can reach IP addresses on this network." +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking_arch.xml:179(emphasis) +msgid "API network" +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking_arch.xml:181(td) +msgid "Exposes all OpenStack APIs, including the Networking API, to tenants. IP addresses on this network should be reachable by anyone on the Internet. The API network might be the same as the external network, because it is possible to create an external-network subnet that is allocated IP ranges that use less than the full range of IP addresses in an IP block." +msgstr "" + +#: ./doc/admin-guide-cloud/section_ts_HTTP_bad_req_in_cinder_vol_log.xml:9(para) +msgid "These errors appear in the cinder-volume.log file." +msgstr "" + +#: ./doc/admin-guide-cloud/section_ts_HTTP_bad_req_in_cinder_vol_log.xml:44(para) +msgid "You need to update your copy of the hp_3par_fc.py driver which contains the synchronization code." +msgstr "" + +#: ./doc/admin-guide-cloud/section_ts_non_existent_vlun.xml:4(title) +msgid "Non-existent VLUN" +msgstr "" + +#: ./doc/admin-guide-cloud/section_ts_non_existent_vlun.xml:7(para) +msgid "This error occurs if the 3PAR host exists with the correct host name that the OpenStack Block Storage drivers expect but the volume was created in a different Domain." +msgstr "" + +#: ./doc/admin-guide-cloud/section_ts_non_existent_vlun.xml:13(para) +msgid "The hp3par_domain configuration items either need to be updated to use the domain the 3PAR host currently resides in, or the 3PAR host needs to be moved to the domain that the volume was created in." +msgstr "" + +#: ./doc/admin-guide-cloud/section_ts_failed_attach_vol_no_sysfsutils.xml:4(title) +msgid "Failed to attach volume, systool is not installed" +msgstr "" + +#: ./doc/admin-guide-cloud/section_ts_failed_attach_vol_no_sysfsutils.xml:7(para) +msgid "This warning and error occurs if you do not have the required sysfsutils package installed on the Compute node." +msgstr "" + +#: ./doc/admin-guide-cloud/section_ts_failed_attach_vol_no_sysfsutils.xml:16(para) +msgid "Run the following command on the Compute node to install the sysfsutils packages." +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking_adv_features.xml:6(title) +msgid "Advanced features through API extensions" +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking_adv_features.xml:7(para) +msgid "Several plug-ins implement API extensions that provide capabilities similar to what was available in nova-network: These plug-ins are likely to be of interest to the OpenStack community." +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking_adv_features.xml:12(title) +msgid "Provider networks" +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking_adv_features.xml:13(para) +msgid "Provider networks enable cloud administrators to create Networking networks that map directly to the physical networks in the data center. This is commonly used to give tenants direct access to a public network that can be used to reach the Internet. It might also be used to integrate with VLANs in the network that already have a defined meaning (for example, enable a VM from the \"marketing\" department to be placed on the same VLAN as bare-metal marketing hosts in the same data center)." +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking_adv_features.xml:22(para) +msgid "The provider extension allows administrators to explicitly manage the relationship between Networking virtual networks and underlying physical mechanisms such as VLANs and tunnels. When this extension is supported, Networking client users with administrative privileges see additional provider attributes on all virtual networks, and are able to specify these attributes in order to create provider networks." +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking_adv_features.xml:30(para) +msgid "The provider extension is supported by the Open vSwitch and Linux Bridge plug-ins. Configuration of these plug-ins requires familiarity with this extension." +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking_adv_features.xml:34(title) +msgid "Terminology" +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking_adv_features.xml:35(para) +msgid "A number of terms are used in the provider extension and in the configuration of plug-ins supporting the provider extension:" +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking_adv_features.xml:39(caption) +msgid "Provider extension terminology" +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking_adv_features.xml:44(th) +msgid "Term" +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking_adv_features.xml:50(emphasis) +msgid "virtual network" +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking_adv_features.xml:52(td) +msgid "An Networking L2 network (identified by a UUID and optional name) whose ports can be attached as vNICs to Compute instances and to various Networking agents. The Open vSwitch and Linux Bridge plug-ins each support several different mechanisms to realize virtual networks." +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking_adv_features.xml:61(emphasis) +msgid "physical network" +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking_adv_features.xml:63(td) +msgid "A network connecting virtualization hosts (such as, Compute nodes) with each other and with other network resources. Each physical network might support multiple virtual networks. The provider extension and the plug-in configurations identify physical networks using simple string names." +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking_adv_features.xml:73(emphasis) +msgid "tenant network" +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking_adv_features.xml:75(td) +msgid "A virtual network that a tenant or an administrator creates. The physical details of the network are not exposed to the tenant." +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking_adv_features.xml:81(emphasis) +msgid "provider network" +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking_adv_features.xml:83(td) +msgid "A virtual network administratively created to map to a specific network in the data center, typically to enable direct access to non-OpenStack resources on that network. Tenants can be given access to provider networks." +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking_adv_features.xml:91(emphasis) +msgid "VLAN network" +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking_adv_features.xml:93(td) +msgid "A virtual network implemented as packets on a specific physical network containing IEEE 802.1Q headers with a specific VID field value. VLAN networks sharing the same physical network are isolated from each other at L2, and can even have overlapping IP address spaces. Each distinct physical network supporting VLAN networks is treated as a separate VLAN trunk, with a distinct space of VID values. Valid VID values are 1 through 4094." +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking_adv_features.xml:107(emphasis) +msgid "flat network" +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking_adv_features.xml:109(td) +msgid "A virtual network implemented as packets on a specific physical network containing no IEEE 802.1Q header. Each physical network can realize at most one flat network." +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking_adv_features.xml:116(emphasis) +msgid "local network" +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking_adv_features.xml:118(td) +msgid "A virtual network that allows communication within each host, but not across a network. Local networks are intended mainly for single-node test scenarios, but can have other uses." +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking_adv_features.xml:125(emphasis) +msgid "GRE network" +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking_adv_features.xml:130(emphasis) +msgid "tunnels" +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking_adv_features.xml:127(td) +msgid "A virtual network implemented as network packets encapsulated using GRE. GRE networks are also referred to as . GRE tunnel packets are routed by the IP routing table for the host, so GRE networks are not associated by Networking with specific physical networks." +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking_adv_features.xml:137(emphasis) +msgid "Virtual Extensible LAN (VXLAN) network" +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking_adv_features.xml:139(td) +msgid "VXLAN is a proposed encapsulation protocol for running an overlay network on existing Layer 3 infrastructure. An overlay network is a virtual network that is built on top of existing network Layer 2 and Layer 3 technologies to support elastic compute architectures." +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking_adv_features.xml:149(para) +msgid "The ML2, Open vSwitch, and Linux Bridge plug-ins support VLAN networks, flat networks, and local networks. Only the ML2 and Open vSwitch plug-ins currently support GRE and VXLAN networks, provided that the required features exist in the hosts Linux kernel, Open vSwitch, and iproute2 packages." +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking_adv_features.xml:157(title) +msgid "Provider attributes" +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking_adv_features.xml:158(para) +msgid "The provider extension extends the Networking network resource with these attributes:" +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking_adv_features.xml:161(caption) +msgid "Provider network attributes" +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking_adv_features.xml:168(th) ./doc/admin-guide-cloud/section_networking_adv_features.xml:371(th) ./doc/admin-guide-cloud/section_networking_adv_features.xml:433(th) ./doc/admin-guide-cloud/section_networking_adv_features.xml:756(th) ./doc/admin-guide-cloud/section_networking_adv_features.xml:803(th) ./doc/admin-guide-cloud/section_networking_adv_features.xml:1071(th) ./doc/admin-guide-cloud/section_networking_adv_features.xml:1206(th) ./doc/admin-guide-cloud/section_networking_adv_features.xml:1284(th) ./doc/admin-guide-cloud/section_networking_adv_features.xml:1521(th) ./doc/admin-guide-cloud/section_networking_adv_features.xml:1899(th) ./doc/admin-guide-cloud/section_networking_adv_features.xml:2008(th) ./doc/admin-guide-cloud/section_networking_adv_features.xml:2051(th) +msgid "Attribute name" +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking_adv_features.xml:169(th) ./doc/admin-guide-cloud/section_networking_adv_features.xml:372(th) ./doc/admin-guide-cloud/section_networking_adv_features.xml:434(th) ./doc/admin-guide-cloud/section_networking_adv_features.xml:757(th) ./doc/admin-guide-cloud/section_networking_adv_features.xml:804(th) ./doc/admin-guide-cloud/section_networking_adv_features.xml:1072(th) ./doc/admin-guide-cloud/section_networking_adv_features.xml:1207(th) ./doc/admin-guide-cloud/section_networking_adv_features.xml:1285(th) ./doc/admin-guide-cloud/section_networking_adv_features.xml:1522(th) ./doc/admin-guide-cloud/section_networking_adv_features.xml:2009(th) ./doc/admin-guide-cloud/section_networking_adv_features.xml:2052(th) ./doc/admin-guide-cloud/section_networking-use.xml:125(th) ./doc/admin-guide-cloud/section_networking-use.xml:198(th) ./doc/admin-guide-cloud/section_networking-use.xml:302(th) +msgid "Type" +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking_adv_features.xml:170(th) ./doc/admin-guide-cloud/section_networking_adv_features.xml:373(th) ./doc/admin-guide-cloud/section_networking_adv_features.xml:435(th) ./doc/admin-guide-cloud/section_networking_adv_features.xml:758(th) ./doc/admin-guide-cloud/section_networking_adv_features.xml:805(th) ./doc/admin-guide-cloud/section_networking_adv_features.xml:1073(th) ./doc/admin-guide-cloud/section_networking_adv_features.xml:1208(th) ./doc/admin-guide-cloud/section_networking_adv_features.xml:1286(th) ./doc/admin-guide-cloud/section_networking_adv_features.xml:1523(th) ./doc/admin-guide-cloud/section_networking_adv_features.xml:2010(th) ./doc/admin-guide-cloud/section_networking_adv_features.xml:2053(th) ./doc/admin-guide-cloud/section_networking-use.xml:199(th) ./doc/admin-guide-cloud/section_networking-use.xml:303(th) +msgid "Default Value" +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking_adv_features.xml:176(td) +msgid "provider:network_type" +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking_adv_features.xml:177(td) ./doc/admin-guide-cloud/section_networking_adv_features.xml:197(td) ./doc/admin-guide-cloud/section_networking_adv_features.xml:386(td) ./doc/admin-guide-cloud/section_networking_adv_features.xml:401(td) ./doc/admin-guide-cloud/section_networking_adv_features.xml:771(td) ./doc/admin-guide-cloud/section_networking_adv_features.xml:780(td) ./doc/admin-guide-cloud/section_networking_adv_features.xml:825(td) ./doc/admin-guide-cloud/section_networking_adv_features.xml:832(td) ./doc/admin-guide-cloud/section_networking_adv_features.xml:851(td) ./doc/admin-guide-cloud/section_networking_adv_features.xml:1094(td) ./doc/admin-guide-cloud/section_networking_adv_features.xml:1101(td) ./doc/admin-guide-cloud/section_networking_adv_features.xml:1131(td) ./doc/admin-guide-cloud/section_networking_adv_features.xml:1181(td) ./doc/admin-guide-cloud/section_networking_adv_features.xml:1229(td) ./doc/admin-guide-cloud/section_networking_adv_features.xml:1236(td) ./doc/admin-guide-cloud/section_networking_adv_features.xml:1307(td) ./doc/admin-guide-cloud/section_networking_adv_features.xml:1314(td) ./doc/admin-guide-cloud/section_networking_adv_features.xml:1329(td) ./doc/admin-guide-cloud/section_networking_adv_features.xml:1545(td) ./doc/admin-guide-cloud/section_networking_adv_features.xml:1565(td) ./doc/admin-guide-cloud/section_networking_adv_features.xml:2023(td) ./doc/admin-guide-cloud/section_networking_adv_features.xml:2030(td) +msgid "String" +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking_adv_features.xml:178(td) ./doc/admin-guide-cloud/section_networking_adv_features.xml:214(td) ./doc/admin-guide-cloud/section_networking_adv_features.xml:402(td) ./doc/admin-guide-cloud/section_networking_adv_features.xml:409(td) ./doc/admin-guide-cloud/section_networking_adv_features.xml:457(td) ./doc/admin-guide-cloud/section_networking_adv_features.xml:465(td) ./doc/admin-guide-cloud/section_networking_adv_features.xml:491(td) ./doc/admin-guide-cloud/section_networking_adv_features.xml:788(td) ./doc/admin-guide-cloud/section_networking_adv_features.xml:826(td) ./doc/admin-guide-cloud/section_networking_adv_features.xml:872(td) ./doc/admin-guide-cloud/section_networking_adv_features.xml:1087(td) ./doc/admin-guide-cloud/section_networking_adv_features.xml:1222(td) ./doc/admin-guide-cloud/section_networking_adv_features.xml:1300(td) ./doc/admin-guide-cloud/section_networking_adv_features.xml:1330(td) ./doc/admin-guide-cloud/section_networking_adv_features.xml:1559(td) ./doc/admin-guide-cloud/section_networking_adv_features.xml:1579(td) ./doc/admin-guide-cloud/section_networking_adv_features.xml:2038(td) ./doc/admin-guide-cloud/section_networking_adv_features.xml:2074(td) ./doc/admin-guide-cloud/section_networking_adv_features.xml:2093(td) ./doc/admin-guide-cloud/section_networking-use.xml:166(td) ./doc/admin-guide-cloud/section_networking-use.xml:180(td) ./doc/admin-guide-cloud/section_networking-use.xml:221(td) ./doc/admin-guide-cloud/section_networking-use.xml:277(td) ./doc/admin-guide-cloud/section_networking-use.xml:284(td) ./doc/admin-guide-cloud/section_networking-use.xml:362(td) ./doc/admin-guide-cloud/section_networking-use.xml:369(td) ./doc/admin-guide-cloud/section_networking-use.xml:376(td) +msgid "N/A" +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking_adv_features.xml:181(literal) ./doc/admin-guide-cloud/section_networking_adv_features.xml:201(literal) ./doc/admin-guide-cloud/section_networking_adv_features.xml:221(literal) +msgid "flat" +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking_adv_features.xml:182(literal) ./doc/admin-guide-cloud/section_networking_adv_features.xml:190(literal) ./doc/admin-guide-cloud/section_networking_adv_features.xml:202(literal) +msgid "vlan" +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking_adv_features.xml:183(literal) ./doc/admin-guide-cloud/section_networking_adv_features.xml:192(literal) ./doc/admin-guide-cloud/section_networking_adv_features.xml:207(literal) ./doc/admin-guide-cloud/section_networking_adv_features.xml:222(literal) +msgid "local" +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking_adv_features.xml:179(td) +msgid "The physical mechanism by which the virtual network is implemented. Possible values are , , , and , corresponding to flat networks, VLAN networks, local networks, and GRE networks as defined above. All types of provider networks can be created by administrators, while tenant networks can be implemented as , , or network types depending on plug-in configuration." +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking_adv_features.xml:196(td) +msgid "provider:physical_network" +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking_adv_features.xml:198(td) +msgid "If a physical network named \"default\" has been configured, and if provider:network_type is or , then \"default\" is used." +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking_adv_features.xml:204(td) +msgid "The name of the physical network over which the virtual network is implemented for flat and VLAN networks. Not applicable to the or network types." +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking_adv_features.xml:212(td) +msgid "provider:segmentation_id" +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking_adv_features.xml:213(td) ./doc/admin-guide-cloud/section_networking_adv_features.xml:839(td) ./doc/admin-guide-cloud/section_networking_adv_features.xml:845(td) ./doc/admin-guide-cloud/section_networking_adv_features.xml:1171(td) ./doc/admin-guide-cloud/section_networking_adv_features.xml:1551(td) ./doc/admin-guide-cloud/section_networking_adv_features.xml:1558(td) ./doc/admin-guide-cloud/section_networking_adv_features.xml:1572(td) +msgid "Integer" +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking_adv_features.xml:215(td) +msgid "For VLAN networks, the VLAN VID on the physical network that realizes the virtual network. Valid VLAN VIDs are 1 through 4094. For GRE networks, the tunnel ID. Valid tunnel IDs are any 32 bit unsigned integer. Not applicable to the or network types." +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking_adv_features.xml:227(para) +msgid "To view or set provider extended attributes, a client must be authorized for the extension:provider_network:view and extension:provider_network:set actions in the Networking policy configuration. The default Networking configuration authorizes both actions for users with the admin role. An authorized client or an administrative user can view and set the provider extended attributes through Networking API calls. See for details on policy configuration." +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking_adv_features.xml:240(title) +msgid "Provider extension API operations" +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking_adv_features.xml:241(para) +msgid "To use the provider extension with the default policy settings, you must have the administrative role." +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking_adv_features.xml:244(para) +msgid "This table shows example neutron commands that enable you to complete basic provider extension API operations:" +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking_adv_features.xml:248(caption) +msgid "Basic provider extension API operations" +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking_adv_features.xml:254(th) ./doc/admin-guide-cloud/section_networking_adv_features.xml:514(th) ./doc/admin-guide-cloud/section_networking_adv_features.xml:891(th) ./doc/admin-guide-cloud/section_networking_adv_features.xml:969(th) ./doc/admin-guide-cloud/section_networking_adv_features.xml:1597(th) ./doc/admin-guide-cloud/section_networking_adv_features.xml:2114(th) ./doc/admin-guide-cloud/section_networking-use.xml:403(th) ./doc/admin-guide-cloud/section_networking-use.xml:484(th) ./doc/admin-guide-cloud/section_networking-use.xml:617(th) +msgid "Operation" +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking_adv_features.xml:255(th) ./doc/admin-guide-cloud/section_networking_adv_features.xml:515(th) ./doc/admin-guide-cloud/section_networking_adv_features.xml:892(th) ./doc/admin-guide-cloud/section_networking_adv_features.xml:970(th) ./doc/admin-guide-cloud/section_networking_adv_features.xml:1598(th) ./doc/admin-guide-cloud/section_networking_adv_features.xml:2115(th) ./doc/admin-guide-cloud/section_networking-use.xml:404(th) ./doc/admin-guide-cloud/section_networking-use.xml:485(th) ./doc/admin-guide-cloud/section_networking-use.xml:544(th) ./doc/admin-guide-cloud/section_networking-use.xml:618(th) +msgid "Command" +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking_adv_features.xml:261(para) +msgid "Shows all attributes of a network, including provider attributes." +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking_adv_features.xml:270(para) +msgid "Creates a local provider network." +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking_adv_features.xml:278(para) +msgid "Creates a flat provider network. When you create flat networks, <phys-net-name> must be known to the plug-in. See the OpenStack Configuration Reference for details." +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking_adv_features.xml:293(para) +msgid "Creates a VLAN provider network. When you create VLAN networks, <phys-net-name> must be known to the plug-in. See the OpenStack Configuration Reference for details on configuring network_vlan_ranges to identify all physical networks. When you create VLAN networks, <VID> can fall either within or outside any configured ranges of VLAN IDs from which tenant networks are allocated." +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking_adv_features.xml:314(para) +msgid "Creates a GRE provider network. When you create GRE networks, <tunnel-id> can be either inside or outside any tunnel ID ranges from which tenant networks are allocated." +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking_adv_features.xml:320(para) +msgid "After you create provider networks, you can allocate subnets, which you can use in the same way as other virtual networks, subject to authorization policy based on the specified <tenant_id>." +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking_adv_features.xml:336(title) +msgid "L3 routing and NAT" +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking_adv_features.xml:337(para) +msgid "The Networking API provides abstract L2 network segments that are decoupled from the technology used to implement the L2 network. Networking includes an API extension that provides abstract L3 routers that API users can dynamically provision and configure. These Networking routers can connect multiple L2 Networking networks, and can also provide a gateway that connects one or more private L2 networks to a shared external network. For example, a public network for access to the Internet. See the OpenStack Configuration Reference for details on common models of deploying Networking L3 routers." +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking_adv_features.xml:350(para) +msgid "The L3 router provides basic NAT capabilities on gateway ports that uplink the router to external networks. This router SNATs all traffic by default, and supports floating IPs, which creates a static one-to-one mapping from a public IP on the external network to a private IP on one of the other subnets attached to the router. This allows a tenant to selectively expose VMs on private networks to other hosts on the external network (and often to all hosts on the Internet). You can allocate and map floating IPs from one port to another, as needed." +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking_adv_features.xml:362(title) +msgid "L3 API abstractions" +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking_adv_features.xml:364(caption) +msgid "Router" +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking_adv_features.xml:379(td) ./doc/admin-guide-cloud/section_networking_adv_features.xml:441(td) ./doc/admin-guide-cloud/section_networking_adv_features.xml:764(td) ./doc/admin-guide-cloud/section_networking_adv_features.xml:811(td) ./doc/admin-guide-cloud/section_networking_adv_features.xml:1079(td) ./doc/admin-guide-cloud/section_networking_adv_features.xml:1214(td) ./doc/admin-guide-cloud/section_networking_adv_features.xml:1292(td) ./doc/admin-guide-cloud/section_networking_adv_features.xml:1529(td) ./doc/admin-guide-cloud/section_networking_adv_features.xml:2016(td) ./doc/admin-guide-cloud/section_networking_adv_features.xml:2059(td) ./doc/admin-guide-cloud/section_networking-use.xml:141(option) ./doc/admin-guide-cloud/section_networking-use.xml:256(option) ./doc/admin-guide-cloud/section_networking-use.xml:341(option) ./doc/admin-guide-cloud/section_networking-use.xml:424(option) +msgid "id" +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking_adv_features.xml:380(td) ./doc/admin-guide-cloud/section_networking_adv_features.xml:408(td) ./doc/admin-guide-cloud/section_networking_adv_features.xml:442(td) ./doc/admin-guide-cloud/section_networking_adv_features.xml:456(td) ./doc/admin-guide-cloud/section_networking_adv_features.xml:464(td) ./doc/admin-guide-cloud/section_networking_adv_features.xml:473(td) ./doc/admin-guide-cloud/section_networking_adv_features.xml:490(td) ./doc/admin-guide-cloud/section_networking_adv_features.xml:765(td) ./doc/admin-guide-cloud/section_networking_adv_features.xml:787(td) ./doc/admin-guide-cloud/section_networking_adv_features.xml:812(td) ./doc/admin-guide-cloud/section_networking_adv_features.xml:871(td) ./doc/admin-guide-cloud/section_networking_adv_features.xml:1080(td) ./doc/admin-guide-cloud/section_networking_adv_features.xml:1086(td) ./doc/admin-guide-cloud/section_networking_adv_features.xml:1215(td) ./doc/admin-guide-cloud/section_networking_adv_features.xml:1221(td) ./doc/admin-guide-cloud/section_networking_adv_features.xml:1293(td) ./doc/admin-guide-cloud/section_networking_adv_features.xml:1299(td) ./doc/admin-guide-cloud/section_networking_adv_features.xml:1530(td) ./doc/admin-guide-cloud/section_networking_adv_features.xml:1578(td) ./doc/admin-guide-cloud/section_networking_adv_features.xml:2017(td) ./doc/admin-guide-cloud/section_networking_adv_features.xml:2037(td) ./doc/admin-guide-cloud/section_networking_adv_features.xml:2060(td) ./doc/admin-guide-cloud/section_networking_adv_features.xml:2073(td) ./doc/admin-guide-cloud/section_networking-use.xml:142(td) ./doc/admin-guide-cloud/section_networking-use.xml:179(td) +msgid "uuid-str" +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking_adv_features.xml:381(td) ./doc/admin-guide-cloud/section_networking_adv_features.xml:443(td) ./doc/admin-guide-cloud/section_networking_adv_features.xml:766(td) ./doc/admin-guide-cloud/section_networking_adv_features.xml:813(td) ./doc/admin-guide-cloud/section_networking_adv_features.xml:1081(td) ./doc/admin-guide-cloud/section_networking_adv_features.xml:1216(td) ./doc/admin-guide-cloud/section_networking_adv_features.xml:1294(td) ./doc/admin-guide-cloud/section_networking_adv_features.xml:1531(td) ./doc/admin-guide-cloud/section_networking_adv_features.xml:2018(td) ./doc/admin-guide-cloud/section_networking_adv_features.xml:2061(td) +msgid "generated" +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking_adv_features.xml:382(td) +msgid "UUID for the router." +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking_adv_features.xml:385(td) ./doc/admin-guide-cloud/section_networking_adv_features.xml:770(td) ./doc/admin-guide-cloud/section_networking_adv_features.xml:1093(td) ./doc/admin-guide-cloud/section_networking_adv_features.xml:1228(td) ./doc/admin-guide-cloud/section_networking_adv_features.xml:1306(td) ./doc/admin-guide-cloud/section_networking_adv_features.xml:1544(td) ./doc/admin-guide-cloud/section_networking_adv_features.xml:2022(td) ./doc/admin-guide-cloud/section_networking-use.xml:147(option) ./doc/admin-guide-cloud/section_networking-use.xml:268(option) ./doc/admin-guide-cloud/section_networking-use.xml:353(option) +msgid "name" +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking_adv_features.xml:387(td) ./doc/admin-guide-cloud/section_networking_adv_features.xml:772(td) ./doc/admin-guide-cloud/section_networking_adv_features.xml:781(td) ./doc/admin-guide-cloud/section_networking_adv_features.xml:833(td) ./doc/admin-guide-cloud/section_networking_adv_features.xml:840(td) ./doc/admin-guide-cloud/section_networking_adv_features.xml:846(td) ./doc/admin-guide-cloud/section_networking_adv_features.xml:852(td) ./doc/admin-guide-cloud/section_networking_adv_features.xml:859(td) ./doc/admin-guide-cloud/section_networking_adv_features.xml:1095(td) ./doc/admin-guide-cloud/section_networking_adv_features.xml:1102(td) ./doc/admin-guide-cloud/section_networking_adv_features.xml:1132(td) ./doc/admin-guide-cloud/section_networking_adv_features.xml:1144(td) ./doc/admin-guide-cloud/section_networking_adv_features.xml:1150(td) ./doc/admin-guide-cloud/section_networking_adv_features.xml:1158(td) ./doc/admin-guide-cloud/section_networking_adv_features.xml:1166(td) ./doc/admin-guide-cloud/section_networking_adv_features.xml:1172(td) ./doc/admin-guide-cloud/section_networking_adv_features.xml:1230(td) ./doc/admin-guide-cloud/section_networking_adv_features.xml:1237(td) ./doc/admin-guide-cloud/section_networking_adv_features.xml:1254(td) ./doc/admin-guide-cloud/section_networking_adv_features.xml:1308(td) ./doc/admin-guide-cloud/section_networking_adv_features.xml:1315(td) ./doc/admin-guide-cloud/section_networking_adv_features.xml:1359(td) ./doc/admin-guide-cloud/section_networking_adv_features.xml:1546(td) ./doc/admin-guide-cloud/section_networking_adv_features.xml:2024(td) ./doc/admin-guide-cloud/section_networking_adv_features.xml:2031(td) ./doc/admin-guide-cloud/section_networking-use.xml:149(td) ./doc/admin-guide-cloud/section_networking-use.xml:270(td) ./doc/admin-guide-cloud/section_networking-use.xml:319(td) ./doc/admin-guide-cloud/section_networking-use.xml:327(td) ./doc/admin-guide-cloud/section_networking-use.xml:355(td) +msgid "None" +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking_adv_features.xml:388(td) +msgid "Human-readable name for the router. Might not be unique." +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking_adv_features.xml:392(td) ./doc/admin-guide-cloud/section_networking_adv_features.xml:1320(td) ./doc/admin-guide-cloud/section_networking-use.xml:132(option) ./doc/admin-guide-cloud/section_networking-use.xml:309(option) +msgid "admin_state_up" +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking_adv_features.xml:393(td) +msgid "Bool" +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking_adv_features.xml:395(td) +msgid "The administrative state of router. If false (down), the router does not forward packets." +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking_adv_features.xml:400(td) ./doc/admin-guide-cloud/section_networking_adv_features.xml:1328(td) ./doc/admin-guide-cloud/section_networking-use.xml:164(option) ./doc/admin-guide-cloud/section_networking-use.xml:367(option) +msgid "status" +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking_adv_features.xml:403(para) +msgid "Indicates whether router is currently operational." +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking_adv_features.xml:407(td) ./doc/admin-guide-cloud/section_networking_adv_features.xml:489(td) ./doc/admin-guide-cloud/section_networking_adv_features.xml:786(td) ./doc/admin-guide-cloud/section_networking_adv_features.xml:870(td) ./doc/admin-guide-cloud/section_networking_adv_features.xml:1085(td) ./doc/admin-guide-cloud/section_networking_adv_features.xml:1220(td) ./doc/admin-guide-cloud/section_networking_adv_features.xml:1298(td) ./doc/admin-guide-cloud/section_networking_adv_features.xml:1577(td) ./doc/admin-guide-cloud/section_networking_adv_features.xml:2036(td) ./doc/admin-guide-cloud/section_networking-use.xml:178(option) ./doc/admin-guide-cloud/section_networking-use.xml:282(option) ./doc/admin-guide-cloud/section_networking-use.xml:374(option) +msgid "tenant_id" +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking_adv_features.xml:410(td) +msgid "Owner of the router. Only admin users can specify a tenant_id other than its own." +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking_adv_features.xml:415(td) +msgid "external_gateway_info" +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking_adv_features.xml:416(td) +msgid "dict contain 'network_id' key-value pair" +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking_adv_features.xml:418(td) ./doc/admin-guide-cloud/section_networking_adv_features.xml:474(td) ./doc/admin-guide-cloud/section_networking_adv_features.xml:482(td) +msgid "Null" +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking_adv_features.xml:419(td) +msgid "External network that this router connects to for gateway services (for example, NAT)" +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking_adv_features.xml:426(caption) +msgid "Floating IP" +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking_adv_features.xml:444(td) +msgid "UUID for the floating IP." +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking_adv_features.xml:447(td) +msgid "floating_ip_address" +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking_adv_features.xml:448(td) ./doc/admin-guide-cloud/section_networking_adv_features.xml:481(td) +msgid "string (IP address)" +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking_adv_features.xml:449(td) ./doc/admin-guide-cloud/section_networking_adv_features.xml:819(td) ./doc/admin-guide-cloud/section_networking_adv_features.xml:1110(td) +msgid "allocated by Networking" +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking_adv_features.xml:450(td) +msgid "The external network IP address available to be mapped to an internal IP address." +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking_adv_features.xml:455(td) +msgid "floating_network_id" +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking_adv_features.xml:458(para) +msgid "The network indicating the set of subnets from which the floating IP should be allocated" +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking_adv_features.xml:463(td) +msgid "router_id" +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking_adv_features.xml:466(td) +msgid "Read-only value indicating the router that connects the external network to the associated internal port, if a port is associated." +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking_adv_features.xml:472(td) +msgid "port_id" +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking_adv_features.xml:475(td) +msgid "Indicates the internal Networking port associated with the external floating IP." +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking_adv_features.xml:480(td) +msgid "fixed_ip_address" +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking_adv_features.xml:483(td) +msgid "Indicates the IP address on the internal port that is mapped to by the floating IP (since an Networking port might have more than one IP address)." +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking_adv_features.xml:492(td) +msgid "Owner of the Floating IP. Only admin users can specify a tenant_id other than its own." +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking_adv_features.xml:501(title) ./doc/admin-guide-cloud/section_networking_adv_features.xml:509(caption) ./doc/admin-guide-cloud/section_networking_adv_features.xml:2109(caption) +msgid "Basic L3 operations" +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking_adv_features.xml:502(para) +msgid "External networks are visible to all users. However, the default policy settings enable only administrative users to create, update, and delete external networks." +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking_adv_features.xml:506(para) +msgid "This table shows example neutron commands that enable you to complete basic L3 operations:" +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking_adv_features.xml:521(para) +msgid "Creates external networks." +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking_adv_features.xml:530(para) +msgid "Lists external networks." +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking_adv_features.xml:536(para) +msgid "Creates an internal-only router that connects to multiple L2 networks privately." +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking_adv_features.xml:551(para) +msgid "Connects a router to an external network, which enables that router to act as a NAT gateway for external connectivity." +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking_adv_features.xml:557(para) +msgid "The router obtains an interface with the gateway_ip address of the subnet, and this interface is attached to a port on the L2 Networking network associated with the subnet. The router also gets a gateway interface to the specified external network. This provides SNAT connectivity to the external network as well as support for floating IPs allocated on that external networks. Commonly an external network maps to a network in the provider" +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking_adv_features.xml:574(para) +msgid "Lists routers." +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking_adv_features.xml:581(para) +msgid "Shows information for a specified router." +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking_adv_features.xml:589(para) +msgid "Shows all internal interfaces for a router." +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking_adv_features.xml:595(para) +msgid "Identifies the port-id that represents the VM NIC to which the floating IP should map." +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking_adv_features.xml:601(para) +msgid "This port must be on an Networking subnet that is attached to a router uplinked to the external network used to create the floating IP.  Conceptually, this is because the router must be able to perform the Destination NAT (DNAT) rewriting of packets from the Floating IP address (chosen from a subnet on the external network) to the internal Fixed IP (chosen from a private subnet that is behind the router)." +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking_adv_features.xml:617(para) +msgid "Creates a floating IP address and associates it with a port." +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking_adv_features.xml:626(para) +msgid "Creates a floating IP address and associates it with a port, in a single step." +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking_adv_features.xml:635(para) +msgid "Lists floating IPs." +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking_adv_features.xml:642(para) +msgid "Finds floating IP for a specified VM port." +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking_adv_features.xml:650(para) +msgid "Disassociates a floating IP address." +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking_adv_features.xml:658(para) +msgid "Deletes the floating IP address." +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking_adv_features.xml:666(para) +msgid "Clears the gateway." +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking_adv_features.xml:673(para) +msgid "Removes the interfaces from the router." +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking_adv_features.xml:681(para) +msgid "Deletes the router." +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking_adv_features.xml:692(title) +msgid "Security groups" +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking_adv_features.xml:693(para) +msgid "Security groups and security group rules allows administrators and tenants the ability to specify the type of traffic and direction (ingress/egress) that is allowed to pass through a port. A security group is a container for security group rules." +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking_adv_features.xml:698(para) +msgid "When a port is created in Networking it is associated with a security group. If a security group is not specified the port is associated with a 'default' security group. By default, this group drops all ingress traffic and allows all egress. Rules can be added to this group in order to change the behaviour." +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking_adv_features.xml:704(para) +msgid "To use the Compute security group APIs or use Compute to orchestrate the creation of ports for instances on specific security groups, you must complete additional configuration. You must configure the /etc/nova/nova.conf file and set the security_group_api=neutron option on every node that runs nova-compute and nova-api. After you make this change, restart nova-api and nova-compute to pick up this change. Then, you can use both the Compute and OpenStack Network security group APIs at the same time." +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking_adv_features.xml:721(para) +msgid "To use the Compute security group API with Networking, the Networking plug-in must implement the security group API. The following plug-ins currently implement this: ML2, Nicira NVP, Open vSwitch, Linux Bridge, NEC, and Ryu." +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking_adv_features.xml:729(para) +msgid "You must configure the correct firewall driver in the securitygroup section of the plug-in/agent configuration file. Some plug-ins and agents, such as Linux Bridge Agent and Open vSwitch Agent, use the no-operation driver as the default, which results in non-working security groups." +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking_adv_features.xml:738(para) +msgid "When using the security group API through Compute, security groups are applied to all ports on an instance. The reason for this is that Compute security group APIs are instances based and not port based as Networking." +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking_adv_features.xml:747(title) +msgid "Security group API abstractions" +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking_adv_features.xml:749(caption) +msgid "Security group attributes" +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking_adv_features.xml:767(td) +msgid "UUID for the security group." +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking_adv_features.xml:773(td) +msgid "Human-readable name for the security group. Might not be unique. Cannot be named default as that is automatically created for a tenant." +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking_adv_features.xml:779(td) ./doc/admin-guide-cloud/section_networking_adv_features.xml:1100(td) ./doc/admin-guide-cloud/section_networking_adv_features.xml:1235(td) ./doc/admin-guide-cloud/section_networking_adv_features.xml:1313(td) ./doc/admin-guide-cloud/section_networking_adv_features.xml:2029(td) +msgid "description" +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking_adv_features.xml:782(td) +msgid "Human-readable description of a security group." +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking_adv_features.xml:789(td) +msgid "Owner of the security group. Only admin users can specify a tenant_id other than their own." +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking_adv_features.xml:796(caption) +msgid "Security group rules" +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking_adv_features.xml:814(td) +msgid "UUID for the security group rule." +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking_adv_features.xml:817(td) +msgid "security_group_id" +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking_adv_features.xml:818(td) ./doc/admin-guide-cloud/section_networking_adv_features.xml:864(td) +msgid "uuid-str or Integer" +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking_adv_features.xml:820(td) +msgid "The security group to associate rule with." +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking_adv_features.xml:824(td) ./doc/admin-guide-cloud/section_networking_adv_features.xml:2065(td) ./doc/admin-guide-cloud/section_networking_adv_features.xml:2159(replaceable) +msgid "direction" +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking_adv_features.xml:827(td) +msgid "The direction the traffic is allow (ingress/egress) from a VM." +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking_adv_features.xml:831(td) ./doc/admin-guide-cloud/section_networking_adv_features.xml:1130(td) +msgid "protocol" +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking_adv_features.xml:834(td) +msgid "IP Protocol (icmp, tcp, udp, and so on)." +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking_adv_features.xml:838(td) +msgid "port_range_min" +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking_adv_features.xml:841(td) +msgid "Port at start of range" +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking_adv_features.xml:844(td) +msgid "port_range_max" +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking_adv_features.xml:847(td) +msgid "Port at end of range" +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking_adv_features.xml:850(td) +msgid "ethertype" +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking_adv_features.xml:853(td) +msgid "ethertype in L2 packet (IPv4, IPv6, and so on)" +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking_adv_features.xml:857(td) ./doc/admin-guide-cloud/section_networking_adv_features.xml:2091(td) +msgid "remote_ip_prefix" +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking_adv_features.xml:858(td) +msgid "string (IP cidr)" +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking_adv_features.xml:860(td) +msgid "CIDR for address range" +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking_adv_features.xml:863(td) +msgid "remote_group_id" +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking_adv_features.xml:865(td) +msgid "allocated by Networking or Compute" +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking_adv_features.xml:866(td) +msgid "Source security group to apply to rule." +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking_adv_features.xml:873(td) +msgid "Owner of the security group rule. Only admin users can specify a tenant_id other than its own." +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking_adv_features.xml:881(title) ./doc/admin-guide-cloud/section_networking_adv_features.xml:886(caption) +msgid "Basic security group operations" +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking_adv_features.xml:882(para) +msgid "This table shows example neutron commands that enable you to complete basic security group operations:" +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking_adv_features.xml:898(para) +msgid "Creates a security group for our web servers." +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking_adv_features.xml:904(para) +msgid "Lists security groups." +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking_adv_features.xml:910(para) +msgid "Creates a security group rule to allow port 80 ingress." +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking_adv_features.xml:917(para) +msgid "Lists security group rules." +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking_adv_features.xml:923(para) +msgid "Deletes a security group rule." +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking_adv_features.xml:930(para) +msgid "Deletes a security group." +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking_adv_features.xml:936(para) +msgid "Creates a port and associates two security groups." +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking_adv_features.xml:943(para) +msgid "Removes security groups from a port." +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking_adv_features.xml:954(title) +msgid "Basic Load-Balancer-as-a-Service operations" +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking_adv_features.xml:956(para) +msgid "The Load-Balancer-as-a-Service (LBaaS) API provisions and configures load balancers. The Havana release offers a reference implementation that is based on the HAProxy software load balancer." +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking_adv_features.xml:961(para) +msgid "This table shows example neutron commands that enable you to complete basic LBaaS operations:" +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking_adv_features.xml:964(caption) +msgid "Basic LBaaS operations" +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking_adv_features.xml:976(para) +msgid "Creates a load balancer pool by using specific provider." +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking_adv_features.xml:978(para) +msgid "--provider is an optional argument. If not used, the pool is created with default provider for LBaaS service. You should configure the default provider in the [service_providers] section of neutron.conf file. If no default provider is specified for LBaaS, the --provider option is required for pool creation." +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking_adv_features.xml:992(parameter) +msgid "--provider <provider_name>" +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking_adv_features.xml:996(para) +msgid "Associates two web servers with pool." +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking_adv_features.xml:1004(para) +msgid "Creates a health monitor which checks to make sure our instances are still running on the specified protocol-port." +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking_adv_features.xml:1012(para) +msgid "Associates a health monitor with pool." +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking_adv_features.xml:1019(para) +msgid "Creates a virtual IP (VIP) address that, when accessed through the load balancer, directs the requests to one of the pool members." +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking_adv_features.xml:1032(title) +msgid "Firewall-as-a-Service" +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking_adv_features.xml:1033(para) +msgid "The Firewall-as-a-Service (FWaaS) API is an experimental API that enables early adopters and vendors to test their networking implementations." +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking_adv_features.xml:1036(para) +msgid "The FWaaS is backed by a reference implementation that works with the Networking OVS plug-in and provides perimeter firewall functionality. It leverages the footprint of the Networking OVS L3 agent and an IPTables driver to apply the firewall rules contained in a particular firewall policy. This reference implementation supports one firewall policy and consequently one logical firewall instance for each tenant. This is not a constraint of the resource model, but of the current reference implementation. The firewall is present on a Networking virtual router. If a tenant has multiple routers, the firewall is present on all the routers. If a tenant does not have any router, the firewall is in PENDING_CREATE state until a router is created and the first interface is added to the router. At that point the firewall policy is immediately applied to the router and the firewall changes to ACTIVE state." +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking_adv_features.xml:1056(para) +msgid "Because this is the first iteration of this implementation, it should probably not be run in production environments without adequate testing." +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking_adv_features.xml:1062(title) +msgid "Firewall-as-a-Service API abstractions" +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking_adv_features.xml:1064(caption) +msgid "Firewall rules" +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking_adv_features.xml:1082(td) +msgid "UUID for the firewall rule." +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking_adv_features.xml:1088(td) +msgid "Owner of the firewall rule. Only admin users can specify a tenant_id other than its own." +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking_adv_features.xml:1096(td) +msgid "Human readable name for the firewall rule (255 characters limit)." +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking_adv_features.xml:1103(td) +msgid "Human readable description for the firewall rule (1024 characters limit)." +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking_adv_features.xml:1108(td) ./doc/admin-guide-cloud/section_networking_adv_features.xml:1357(td) +msgid "firewall_policy_id" +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking_adv_features.xml:1109(td) ./doc/admin-guide-cloud/section_networking_adv_features.xml:1358(td) +msgid "uuid-str or None" +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking_adv_features.xml:1111(td) +msgid "This is a read-only attribute that gets populated with the uuid of the firewall policy when this firewall rule is associated with a firewall policy. A firewall rule can be associated with only one firewall policy at a time. However, the association can be changed to a different firewall policy." +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking_adv_features.xml:1121(td) ./doc/admin-guide-cloud/section_networking_adv_features.xml:1243(td) ./doc/admin-guide-cloud/section_networking-use.xml:154(option) +msgid "shared" +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking_adv_features.xml:1122(td) ./doc/admin-guide-cloud/section_networking_adv_features.xml:1188(td) ./doc/admin-guide-cloud/section_networking_adv_features.xml:1244(td) ./doc/admin-guide-cloud/section_networking_adv_features.xml:1262(td) ./doc/admin-guide-cloud/section_networking_adv_features.xml:1321(td) ./doc/admin-guide-cloud/section_networking_adv_features.xml:1536(td) ./doc/admin-guide-cloud/section_networking_adv_features.xml:2082(td) +msgid "Boolean" +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking_adv_features.xml:1123(td) ./doc/admin-guide-cloud/section_networking_adv_features.xml:1245(td) ./doc/admin-guide-cloud/section_networking_adv_features.xml:1263(td) ./doc/admin-guide-cloud/section_networking_adv_features.xml:1840(td) ./doc/admin-guide-cloud/section_networking_adv_features.xml:2083(td) ./doc/admin-guide-cloud/section_networking-use.xml:156(td) +msgid "False" +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking_adv_features.xml:1124(td) +msgid "When set to True makes this firewall rule visible to tenants other than its owner, and it can be used in firewall policies not owned by its tenant." +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking_adv_features.xml:1133(td) +msgid "IP Protocol (icmp, tcp, udp, None)." +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking_adv_features.xml:1136(td) ./doc/admin-guide-cloud/section_networking-use.xml:262(option) +msgid "ip_version" +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking_adv_features.xml:1137(td) +msgid "Integer or String" +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking_adv_features.xml:1138(td) ./doc/admin-guide-cloud/section_networking-use.xml:264(td) +msgid "4" +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking_adv_features.xml:1139(td) +msgid "IP Version (4, 6)." +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking_adv_features.xml:1142(td) +msgid "source_ip_address" +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking_adv_features.xml:1143(td) ./doc/admin-guide-cloud/section_networking_adv_features.xml:1149(td) +msgid "String (IP address or CIDR)" +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking_adv_features.xml:1145(td) +msgid "Source IP address or CIDR." +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking_adv_features.xml:1148(td) +msgid "destination_ip_address" +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking_adv_features.xml:1151(td) +msgid "Destination IP address or CIDR." +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking_adv_features.xml:1154(td) +msgid "source_port" +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking_adv_features.xml:1155(td) ./doc/admin-guide-cloud/section_networking_adv_features.xml:1163(td) +msgid "Integer or String (either as a single port number or in the format of a ':' separated range)" +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking_adv_features.xml:1159(td) +msgid "Source port number or a range." +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking_adv_features.xml:1162(td) +msgid "destination_port" +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking_adv_features.xml:1167(td) +msgid "Destination port number or a range." +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking_adv_features.xml:1170(td) +msgid "position" +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking_adv_features.xml:1173(td) +msgid "This is a read-only attribute that gets assigned to this rule when the rule is associated with a firewall policy. It indicates the position of this rule in that firewall policy." +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking_adv_features.xml:1180(td) ./doc/admin-guide-cloud/section_networking_adv_features.xml:1925(td) +msgid "action" +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking_adv_features.xml:1182(td) +msgid "deny" +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking_adv_features.xml:1183(td) +msgid "Action to be performed on the traffic matching the rule (allow, deny)." +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking_adv_features.xml:1187(td) +msgid "enabled" +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking_adv_features.xml:1190(td) +msgid "When set to False, disables this rule in the firewall policy. Facilitates selectively turning off rules without having to disassociate the rule from the firewall policy." +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking_adv_features.xml:1199(caption) +msgid "Firewall policies" +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking_adv_features.xml:1217(td) +msgid "UUID for the firewall policy." +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking_adv_features.xml:1223(td) +msgid "Owner of the firewall policy. Only admin users can specify a tenant_id other their own." +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking_adv_features.xml:1231(td) +msgid "Human readable name for the firewall policy (255 characters limit)." +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking_adv_features.xml:1238(td) +msgid "Human readable description for the firewall policy (1024 characters limit)." +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking_adv_features.xml:1246(td) +msgid "When set to True makes this firewall policy visible to tenants other than its owner, and can be used to associate with firewalls not owned by its tenant." +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking_adv_features.xml:1252(td) +msgid "firewall_rules" +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking_adv_features.xml:1253(td) +msgid "List of uuid-str or None" +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking_adv_features.xml:1255(td) +msgid "This is an ordered list of firewall rule uuids. The firewall applies the rules in the order in which they appear in this list." +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking_adv_features.xml:1261(td) +msgid "audited" +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking_adv_features.xml:1264(td) +msgid "When set to True by the policy owner indicates that the firewall policy has been audited. This attribute is meant to aid in the firewall policy audit workflows. Each time the firewall policy or the associated firewall rules are changed, this attribute is set to False and must be explicitly set to True through an update operation." +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking_adv_features.xml:1277(caption) +msgid "Firewalls" +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking_adv_features.xml:1295(td) +msgid "UUID for the firewall." +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking_adv_features.xml:1301(td) +msgid "Owner of the firewall. Only admin users can specify a tenant_id other than its own." +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking_adv_features.xml:1309(td) +msgid "Human readable name for the firewall (255 characters limit)." +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking_adv_features.xml:1316(td) +msgid "Human readable description for the firewall (1024 characters limit)." +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking_adv_features.xml:1323(td) +msgid "The administrative state of the firewall. If False (down), the firewall does not forward any packets." +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking_adv_features.xml:1331(para) +msgid "Indicates whether the firewall is currently operational. Possible values include:" +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking_adv_features.xml:1336(para) +msgid "ACTIVE" +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking_adv_features.xml:1339(para) +msgid "DOWN" +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking_adv_features.xml:1342(para) +msgid "PENDING_CREATE" +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking_adv_features.xml:1345(para) +msgid "PENDING_UPDATE" +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking_adv_features.xml:1348(para) +msgid "PENDING_DELETE" +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking_adv_features.xml:1351(para) +msgid "ERROR" +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking_adv_features.xml:1360(td) +msgid "The firewall policy uuid that this firewall is associated with. This firewall implements the rules contained in the firewall policy represented by this uuid." +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking_adv_features.xml:1370(title) +msgid "Basic Firewall-as-a-Service operations" +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking_adv_features.xml:1373(para) +msgid "Create a firewall rule:" +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking_adv_features.xml:1375(para) +msgid "The CLI requires that a protocol value be provided. If the rule is protocol agnostic, the 'any' value can be used." +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking_adv_features.xml:1378(para) +msgid "In addition to the protocol attribute, other attributes can be specified in the firewall rule. See the previous section for the supported attributes." +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking_adv_features.xml:1384(para) +msgid "Create a firewall policy:" +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking_adv_features.xml:1386(para) +msgid "The order of the rules specified above is important. A firewall policy can be created without any rules and rules can be added later either via the update operation (if adding multiple rules) or via the insert-rule operation (if adding a single rule). Please check the CLI help for more details on these operations." +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking_adv_features.xml:1395(para) +msgid "The reference implementation always adds a default deny all rule at the end of each policy. This implies that if a firewall policy is created without any rules and is associated with a firewall, that firewall blocks all traffic." +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking_adv_features.xml:1404(para) +msgid "Create a firewall:" +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking_adv_features.xml:1409(para) +msgid "The FWaaS features and the above workflow can also be accessed from the Horizon user interface. This support is disabled by default, but can be enabled by configuring #HORIZON_DIR/openstack_dashboard/local/local_settings.py and setting:" +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking_adv_features.xml:1421(title) +msgid "Allowed-address-pairs" +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking_adv_features.xml:1422(para) +msgid "Allowed-address-pairs is an API extension that extends the port attribute. This extension allows one to specify arbitrary mac_address/ip_address(cidr) pairs that are allowed to pass through a port regardless of subnet. The main use case for this is to enable the ability to use protocols such as VRRP which floats an ip address between two instances to enable fast data plane failover." +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking_adv_features.xml:1430(para) +msgid "The allowed-address-pairs extension is currently only supported by these plug-ins: ML2, Nicira NVP, and Open vSwitch." +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking_adv_features.xml:1435(title) +msgid "Basic allowed address pairs operations" +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking_adv_features.xml:1438(para) +msgid "Create a port with a specific allowed-address-pairs:" +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking_adv_features.xml:1443(para) +msgid "Update a port adding allowed-address-pairs:" +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking_adv_features.xml:1449(para) +msgid "Setting an allowed-address-pair that matches the mac_address and ip_address of a port is prevented. This is because that would have no effect since traffic matching the mac_address and ip_address is already allowed to pass through the port." +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking_adv_features.xml:1456(para) +msgid "If your plug-in implements the port-security extension port-security-enabled must be set to True on the port in order to have allowed-address-pairs on a port. The reason for this is because if port-security-enabled is set to False this allows all traffic to be passed through the port thus having allowed-address-pairs would have no effect." +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking_adv_features.xml:1469(title) +msgid "Plug-in specific extensions" +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking_adv_features.xml:1471(para) +msgid "Each vendor can choose to implement additional API extensions to the core API. This section describes the extensions for each plug-in." +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking_adv_features.xml:1475(title) +msgid "Nicira NVP extensions" +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking_adv_features.xml:1476(para) +msgid "These sections explain Nicira NVP plug-in extensions." +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking_adv_features.xml:1479(title) +msgid "Nicira NVP QoS extension" +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking_adv_features.xml:1480(para) +msgid "The Nicira NVP QoS extension rate-limits network ports to guarantee a specific amount of bandwidth for each port. This extension, by default, is only accessible by a tenant with an admin role but is configurable through the policy.json file. To use this extension, create a queue and specify the min/max bandwidth rates (kbps) and optionally set the QoS Marking and DSCP value (if your network fabric uses these values to make forwarding decisions). Once created, you can associate a queue with a network. Then, when ports are created on that network they are automatically created and associated with the specific queue size that was associated with the network. Because one size queue for a every port on a network might not be optimal, a scaling factor from the Nova flavor 'rxtx_factor' is passed in from Compute when creating the port to scale the queue." +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking_adv_features.xml:1499(para) +msgid "Lastly, if you want to set a specific baseline QoS policy for the amount of bandwidth a single port can use (unless a network queue is specified with the network a port is created on) a default queue can be created in Networking which then causes ports created to be associated with a queue of that size times the rxtx scaling factor. Note that after a network or default queue is specified, queues are added to ports that are subsequently created but are not added to existing ports." +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking_adv_features.xml:1512(title) +msgid "Nicira NVP QoS API abstractions" +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking_adv_features.xml:1514(caption) +msgid "Nicira NVP QoS attributes" +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking_adv_features.xml:1532(td) +msgid "UUID for the QoS queue." +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking_adv_features.xml:1537(td) +msgid "False by default" +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking_adv_features.xml:1538(td) +msgid "If True, ports are created with this queue size unless the network port is created or associated with a queue at port creation time." +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking_adv_features.xml:1547(td) +msgid "Name for QoS queue." +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking_adv_features.xml:1550(td) +msgid "min" +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking_adv_features.xml:1552(td) ./doc/admin-guide-cloud/section_networking_adv_features.xml:1573(td) +msgid "0" +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking_adv_features.xml:1553(td) +msgid "Minimum Bandwidth Rate (kbps)." +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking_adv_features.xml:1557(td) +msgid "max" +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking_adv_features.xml:1560(td) +msgid "Maximum Bandwidth Rate (kbps)." +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking_adv_features.xml:1564(td) +msgid "qos_marking" +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking_adv_features.xml:1566(td) +msgid "untrusted by default" +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking_adv_features.xml:1567(td) +msgid "Whether QoS marking should be trusted or untrusted." +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking_adv_features.xml:1571(td) +msgid "dscp" +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking_adv_features.xml:1574(td) +msgid "DSCP Marking value." +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking_adv_features.xml:1580(td) +msgid "The owner of the QoS queue." +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking_adv_features.xml:1586(title) ./doc/admin-guide-cloud/section_networking_adv_features.xml:1591(caption) +msgid "Basic Nicira NVP QoS operations" +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking_adv_features.xml:1587(para) +msgid "This table shows example neutron commands that enable you to complete basic queue operations:" +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking_adv_features.xml:1604(para) +msgid "Creates QoS Queue (admin-only)." +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking_adv_features.xml:1612(para) +msgid "Associates a queue with a network." +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking_adv_features.xml:1620(para) +msgid "Creates a default system queue." +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking_adv_features.xml:1626(para) +msgid "Lists QoS queues." +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking_adv_features.xml:1633(para) +msgid "Deletes a QoS queue." +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking_adv_features.xml:1644(title) +msgid "Nicira NVP provider networks extension" +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking_adv_features.xml:1645(para) +msgid "Provider networks can be implemented in different ways by the underlying NVP platform." +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking_adv_features.xml:1648(para) +msgid "The FLAT and VLAN network types use bridged transport connectors. These network types enable the attachment of large number of ports. To handle the increased scale, the NVP plug-in can back a single Openstack Network with a chain of NVP logical switches. You can specify the maximum number of ports on each logical switch in this chain on the max_lp_per_bridged_ls parameter, which has a default value of 5,000." +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking_adv_features.xml:1660(para) +msgid "The recommended value for this parameter varies with the NVP version running in the back-end, as shown in the following table." +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking_adv_features.xml:1664(caption) +msgid "Recommended values for max_lp_per_bridged_ls" +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking_adv_features.xml:1670(td) +msgid "NVP version" +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking_adv_features.xml:1671(td) +msgid "Recommended Value" +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking_adv_features.xml:1676(td) +msgid "2.x" +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking_adv_features.xml:1677(td) +msgid "64" +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking_adv_features.xml:1680(td) +msgid "3.0.x" +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking_adv_features.xml:1681(td) ./doc/admin-guide-cloud/section_networking_adv_features.xml:1685(td) +msgid "5,000" +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking_adv_features.xml:1684(td) +msgid "3.1.x" +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking_adv_features.xml:1688(td) +msgid "3.2.x" +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking_adv_features.xml:1689(td) +msgid "10,000" +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking_adv_features.xml:1693(para) +msgid "In addition to these network types, the NVP plug-in also supports a special l3_ext network type, which maps external networks to specific NVP gateway services as discussed in the next section." +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking_adv_features.xml:1701(title) +msgid "Nicira NVP L3 extension" +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking_adv_features.xml:1702(para) +msgid "NVP exposes its L3 capabilities through gateway services which are usually configured out of band from OpenStack. To use NVP with L3 capabilities, first create a L3 gateway service in the NVP Manager. Next, in /etc/neutron/plugins/nicira/nvp.ini set default_l3_gw_service_uuid to this value. By default, routers are mapped to this gateway service." +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking_adv_features.xml:1712(title) +msgid "Nicira NVP L3 extension operations" +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking_adv_features.xml:1713(para) +msgid "Create external network and map it to a specific NVP gateway service:" +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking_adv_features.xml:1717(para) +msgid "Terminate traffic on a specific VLAN from a NVP gateway service:" +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking_adv_features.xml:1724(title) +msgid "Operational status synchronization in the Nicira NVP plug-in" +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking_adv_features.xml:1726(para) +msgid "Starting with the Havana release, the Nicira NVP plug-in provides an asynchronous mechanism for retrieving the operational status for neutron resources from the NVP back-end; this applies to network, port, and router resources." +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking_adv_features.xml:1733(para) +msgid "The back-end is polled periodically, and the status for every resource is retrieved; then the status in the Networking database is updated only for the resources for which a status change occurred. As operational status is now retrieved asynchronously, performance for GET operations is consistently improved." +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking_adv_features.xml:1741(para) +msgid "Data to retrieve from the back-end are divided in chunks in order to avoid expensive API requests; this is achieved leveraging NVP APIs response paging capabilities. The minimum chunk size can be specified using a configuration option; the actual chunk size is then determined dynamically according to: total number of resources to retrieve, interval between two synchronization task runs, minimum delay between two subsequent requests to the NVP back-end." +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking_adv_features.xml:1752(para) +msgid "The operational status synchronization can be tuned or disabled using the configuration options reported in this table; it is however worth noting that the default values work fine in most cases." +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking_adv_features.xml:1758(caption) +msgid "Configuration options for tuning operational status synchronization in the NVP plug-in" +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking_adv_features.xml:1768(th) +msgid "Option name" +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking_adv_features.xml:1769(th) +msgid "Group" +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking_adv_features.xml:1770(th) ./doc/admin-guide-cloud/section_networking-use.xml:126(th) +msgid "Default value" +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking_adv_features.xml:1771(th) +msgid "Type and constraints" +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking_adv_features.xml:1772(th) +msgid "Notes" +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking_adv_features.xml:1777(literal) ./doc/admin-guide-cloud/section_networking_adv_features.xml:1784(literal) ./doc/admin-guide-cloud/section_networking_adv_features.xml:1808(literal) ./doc/admin-guide-cloud/section_networking_adv_features.xml:1826(literal) +msgid "state_sync_interval" +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking_adv_features.xml:1778(literal) ./doc/admin-guide-cloud/section_networking_adv_features.xml:1793(literal) ./doc/admin-guide-cloud/section_networking_adv_features.xml:1805(literal) ./doc/admin-guide-cloud/section_networking_adv_features.xml:1818(literal) ./doc/admin-guide-cloud/section_networking_adv_features.xml:1839(literal) +msgid "nvp_sync" +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking_adv_features.xml:1779(td) +msgid "120 seconds" +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking_adv_features.xml:1780(td) ./doc/admin-guide-cloud/section_networking_adv_features.xml:1820(td) +msgid "Integer; no constraint." +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking_adv_features.xml:1781(td) +msgid "Interval in seconds between two run of the synchronization task. If the synchronization task takes more than seconds to execute, a new instance of the task is started as soon as the other is completed. Setting the value for this option to 0 will disable the synchronization task." +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking_adv_features.xml:1792(literal) ./doc/admin-guide-cloud/section_networking_adv_features.xml:1799(literal) +msgid "max_random_sync_delay" +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking_adv_features.xml:1794(td) +msgid "0 seconds" +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking_adv_features.xml:1796(literal) ./doc/admin-guide-cloud/section_networking_adv_features.xml:1804(literal) ./doc/admin-guide-cloud/section_networking_adv_features.xml:1828(literal) +msgid "min_sync_req_delay" +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking_adv_features.xml:1795(td) +msgid "Integer. Must not exceed " +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking_adv_features.xml:1797(td) +msgid "When different from zero, a random delay between 0 and will be added before processing the next chunk." +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking_adv_features.xml:1806(td) +msgid "10 seconds" +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking_adv_features.xml:1807(td) +msgid "Integer. Must not exceed ." +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking_adv_features.xml:1809(td) +msgid "The value of this option can be tuned according to the observed load on the NVP controllers. Lower values will result in faster synchronization, but might increase the load on the controller cluster." +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking_adv_features.xml:1817(literal) ./doc/admin-guide-cloud/section_networking_adv_features.xml:1832(literal) +msgid "min_chunk_size" +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking_adv_features.xml:1819(td) +msgid "500 resources" +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking_adv_features.xml:1821(td) +msgid "Minimum number of resources to retrieve from the back-end for each synchronization chunk. The expected number of synchronization chunks is given by the ratio between and . This size of a chunk might increase if the total number of resources is such that more than resources must be fetched in one chunk with the current number of chunks." +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking_adv_features.xml:1838(literal) +msgid "always_read_status" +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking_adv_features.xml:1841(td) +msgid "Boolean; no constraint." +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking_adv_features.xml:1845(literal) +msgid "GET" +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking_adv_features.xml:1842(td) +msgid "When this option is enabled, the operational status will always be retrieved from the NVP back-end ad every request. In this case it is advisable to disable the synchronization task." +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking_adv_features.xml:1851(para) +msgid "When running multiple OpenStack Networking server instances, the status synchronization task should not run on every node; doing so sends unnecessary traffic to the NVP back-end and performs unnecessary DB operations. Set the configuration option to a non-zero value exclusively on a node designated for back-end status synchronization." +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking_adv_features.xml:1860(para) +msgid "The fields=status parameter in Networking API requests always triggers an explicit query to the NVP back end, even when you enable asynchronous state synchronization. For example, GET /v2.0/networks/<net-id>?fields=status&fields=name." +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking_adv_features.xml:1869(title) +msgid "Big Switch plug-in extensions" +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking_adv_features.xml:1870(para) +msgid "This section explains the Big Switch Neutron plug-in-specific extension." +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking_adv_features.xml:1873(title) +msgid "Big Switch router rules" +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking_adv_features.xml:1874(para) +msgid "Big Switch allows router rules to be added to each tenant router. These rules can be used to enforce routing policies such as denying traffic between subnets or traffic to external networks. By enforcing these at the router level, network segmentation policies can be enforced across many VMs that have differing security groups." +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking_adv_features.xml:1882(title) +msgid "Router rule attributes" +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking_adv_features.xml:1883(para) +msgid "Each tenant router has a set of router rules associated with it. Each router rule has the attributes in this table. Router rules and their attributes can be set using the command, through the Horizon interface or the Neutron API." +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking_adv_features.xml:1891(caption) +msgid "Big Switch Router rule attributes" +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking_adv_features.xml:1900(th) +msgid "Required" +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking_adv_features.xml:1901(th) +msgid "Input Type" +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking_adv_features.xml:1907(td) +msgid "source" +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking_adv_features.xml:1909(td) ./doc/admin-guide-cloud/section_networking_adv_features.xml:1918(td) +msgid "A valid CIDR or one of the keywords 'any' or 'external'" +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking_adv_features.xml:1911(td) +msgid "The network that a packet's source IP must match for the rule to be applied" +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking_adv_features.xml:1916(td) +msgid "destination" +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking_adv_features.xml:1920(td) +msgid "The network that a packet's destination IP must match for the rule to be applied" +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking_adv_features.xml:1927(td) +msgid "'permit' or 'deny'" +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking_adv_features.xml:1928(td) +msgid "Determines whether or not the matched packets will allowed to cross the router" +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking_adv_features.xml:1933(td) +msgid "nexthop" +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking_adv_features.xml:1934(td) +msgid "No" +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking_adv_features.xml:1937(literal) +msgid "1.1.1.1+1.1.1.2" +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking_adv_features.xml:1935(td) +msgid "A plus-separated (+) list of next-hop IP addresses. For example, ." +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking_adv_features.xml:1938(td) +msgid "Overrides the default virtual router used to handle traffic for packets that match the rule" +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking_adv_features.xml:1947(title) +msgid "Order of rule processing" +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking_adv_features.xml:1948(para) +msgid "The order of router rules has no effect. Overlapping rules are evaluated using longest prefix matching on the source and destination fields. The source field is matched first so it always takes higher precedence over the destination field. In other words, longest prefix matching is used on the destination field only if there are multiple matching rules with the same source." +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking_adv_features.xml:1960(title) +msgid "Big Switch router rules operations" +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking_adv_features.xml:1961(para) +msgid "Router rules are configured with a router update operation in OpenStack Networking. The update overrides any previous rules so all rules must be provided at the same time." +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking_adv_features.xml:1966(para) +msgid "Update a router with rules to permit traffic by default but block traffic from external networks to the 10.10.10.0/24 subnet:" +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking_adv_features.xml:1969(replaceable) ./doc/admin-guide-cloud/section_networking_adv_features.xml:1974(replaceable) ./doc/admin-guide-cloud/section_networking_adv_features.xml:1979(replaceable) +msgid "Router-UUID" +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking_adv_features.xml:1972(para) +msgid "Specify alternate next-hop addresses for a specific subnet:" +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking_adv_features.xml:1977(para) +msgid "Block traffic between two subnets while allowing everything else:" +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking_adv_features.xml:1987(title) +msgid "L3 metering" +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking_adv_features.xml:1988(para) +msgid "The L3 metering API extension enables administrators to configure IP ranges and assign a specified label to them to be able to measure traffic that goes through a virtual router." +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking_adv_features.xml:1992(para) +msgid "The L3 metering extension is decoupled from the technology that implements the measurement. Two abstractions have been added: One is the metering label that can contain metering rules. Because a metering label is associated with a tenant, all virtual routers in this tenant are associated with this label." +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking_adv_features.xml:1999(title) +msgid "L3 metering API abstractions" +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking_adv_features.xml:2001(caption) +msgid "Label" +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking_adv_features.xml:2019(td) +msgid "UUID for the metering label." +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking_adv_features.xml:2025(td) +msgid "Human-readable name for the metering label. Might not be unique." +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking_adv_features.xml:2032(td) +msgid "The optional description for the metering label." +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking_adv_features.xml:2039(td) +msgid "Owner of the metering label." +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking_adv_features.xml:2044(caption) +msgid "Rules" +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking_adv_features.xml:2062(td) +msgid "UUID for the metering rule." +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking_adv_features.xml:2066(td) +msgid "String (Either ingress or egress)" +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking_adv_features.xml:2067(td) ./doc/admin-guide-cloud/section_networking_adv_features.xml:2160(replaceable) +msgid "ingress" +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking_adv_features.xml:2068(td) +msgid "The direction in which metering rule is applied, either ingress or egress." +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking_adv_features.xml:2072(td) +msgid "metering_label_id" +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking_adv_features.xml:2076(para) +msgid "The metering label ID to associate with this metering rule." +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking_adv_features.xml:2081(td) +msgid "excluded" +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking_adv_features.xml:2084(td) +msgid "Specify whether the remote_ip_prefix will be excluded or not from traffic counters of the metering label (for example, to not count the traffic of a specific IP address of a range)." +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking_adv_features.xml:2092(td) +msgid "String (CIDR)" +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking_adv_features.xml:2094(td) +msgid "Indicates remote IP prefix to be associated with this metering rule." +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking_adv_features.xml:2102(title) +msgid "Basic L3 metering operations" +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking_adv_features.xml:2103(para) +msgid "Only administrators can manage the L3 metering labels and rules." +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking_adv_features.xml:2105(para) +msgid "This table shows example commands that enable you to complete basic L3 metering operations:" +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking_adv_features.xml:2121(para) +msgid "Creates a metering label." +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking_adv_features.xml:2124(replaceable) ./doc/admin-guide-cloud/section_networking_adv_features.xml:2142(replaceable) ./doc/admin-guide-cloud/section_networking_adv_features.xml:2151(replaceable) ./doc/admin-guide-cloud/section_networking_adv_features.xml:2160(replaceable) ./doc/admin-guide-cloud/section_networking_adv_features.xml:2161(replaceable) +msgid "label1" +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking_adv_features.xml:2124(replaceable) +msgid "\"description of label1\"" +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking_adv_features.xml:2129(para) +msgid "Lists metering labels." +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking_adv_features.xml:2137(para) +msgid "Shows information for a specified label." +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking_adv_features.xml:2141(replaceable) ./doc/admin-guide-cloud/section_networking_adv_features.xml:2150(replaceable) ./doc/admin-guide-cloud/section_networking_adv_features.xml:2159(replaceable) +msgid "label-uuid" +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking_adv_features.xml:2147(para) +msgid "Deletes a metering label." +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking_adv_features.xml:2156(para) +msgid "Creates a metering rule." +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking_adv_features.xml:2159(replaceable) ./doc/admin-guide-cloud/section_networking-use.xml:208(option) ./doc/admin-guide-cloud/section_networking-use.xml:219(option) ./doc/admin-guide-cloud/section_networking-use.xml:242(option) +msgid "cidr" +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking_adv_features.xml:2160(replaceable) +msgid "10.0.0.0/24" +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking_adv_features.xml:2161(replaceable) +msgid "20.0.0.0/24" +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking_adv_features.xml:2166(para) +msgid "Lists metering all label rules." +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking_adv_features.xml:2175(para) +msgid "Shows information for a specified label rule." +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking_adv_features.xml:2179(replaceable) ./doc/admin-guide-cloud/section_networking_adv_features.xml:2185(replaceable) +msgid "rule-uuid" +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking_adv_features.xml:2183(td) +msgid "Deletes a metering label rule." +msgstr "" + +#: ./doc/admin-guide-cloud/section_multi_backend.xml:5(title) +msgid "Configure a multiple-storage back-end" +msgstr "" + +#: ./doc/admin-guide-cloud/section_multi_backend.xml:6(para) +msgid "This section presents the multi back-end storage feature introduced with the Grizzly release. Multi back-end allows the creation of several back-end storage solutions serving the same OpenStack Compute configuration. Basically, multi back-end launches one cinder-volume for each back-end." +msgstr "" + +#: ./doc/admin-guide-cloud/section_multi_backend.xml:12(para) +msgid "In a multi back-end configuration, each back-end has a name (volume_backend_name). Several back-ends can have the same name. In that case, the scheduler properly decides which back-end the volume has to be created in." +msgstr "" + +#: ./doc/admin-guide-cloud/section_multi_backend.xml:17(para) +msgid "The name of the back-end is declared as an extra-specification of a volume type (such as, volume_backend_name=LVM_iSCSI). When a volume is created, the scheduler chooses an appropriate back-end to handle the request, according to the volume type specified by the user." +msgstr "" + +#: ./doc/admin-guide-cloud/section_multi_backend.xml:24(title) +msgid "Enable multi back-end" +msgstr "" + +#: ./doc/admin-guide-cloud/section_multi_backend.xml:25(para) +msgid "To enable a multi back-end configuration, you must set the flag in the cinder.conf file. This flag defines the names (separated by a comma) of the configuration groups for the different back-ends: one name is associated to one configuration group for a back-end (such as, [lvmdriver-1])." +msgstr "" + +#: ./doc/admin-guide-cloud/section_multi_backend.xml:33(para) +msgid "The configuration group name is not related to the volume_backend_name." +msgstr "" + +#: ./doc/admin-guide-cloud/section_multi_backend.xml:36(para) +msgid "The options for a configuration group must be defined in the group (or default options are used). All the standard Block Storage configuration options (volume_group, volume_driver, and so on) might be used in a configuration group. Configuration values in the [DEFAULT] configuration group are not used." +msgstr "" + +#: ./doc/admin-guide-cloud/section_multi_backend.xml:44(para) +msgid "These examples show three back-ends:" +msgstr "" + +#: ./doc/admin-guide-cloud/section_multi_backend.xml:59(para) +msgid "In this configuration, lvmdriver-1 and lvmdriver-2 have the same volume_backend_name. If a volume creation requests the LVM_iSCSI back-end name, the scheduler uses the capacity filter scheduler to choose the most suitable driver, which is either lvmdriver-1 or lvmdriver-2. The capacity filter scheduler is enabled by default. The next section provides more information. In addition, this example presents a lvmdriver-3 back-end." +msgstr "" + +#: ./doc/admin-guide-cloud/section_multi_backend.xml:72(title) +msgid "Configure Block Storage scheduler multi back-end" +msgstr "" + +#: ./doc/admin-guide-cloud/section_multi_backend.xml:73(para) +msgid "You must enable the option to use multi back-end. Filter scheduler acts in two steps:" +msgstr "" + +#: ./doc/admin-guide-cloud/section_multi_backend.xml:78(para) +msgid "The filter scheduler filters the available back-ends. By default, AvailabilityZoneFilter, CapacityFilter and CapabilitiesFilter are enabled." +msgstr "" + +#: ./doc/admin-guide-cloud/section_multi_backend.xml:86(para) +msgid "The filter scheduler weighs the previously filtered back-ends. By default, CapacityWeigher is enabled. The CapacityWeigher attributes higher scores to back-ends with the most available." +msgstr "" + +#: ./doc/admin-guide-cloud/section_multi_backend.xml:94(para) +msgid "The scheduler uses the filtering and weighing process to pick the best back-end to handle the request, and explicitly creates volumes on specific back-ends through the use of volume types." +msgstr "" + +#: ./doc/admin-guide-cloud/section_multi_backend.xml:99(para) +msgid "To enable the filter scheduler, add this line to the cinder.conf configuration file:" +msgstr "" + +#: ./doc/admin-guide-cloud/section_multi_backend.xml:103(para) +msgid "While the Block Storage Scheduler defaults to in Grizzly, this setting is not required." +msgstr "" + +#: ./doc/admin-guide-cloud/section_multi_backend.xml:110(title) +msgid "Volume type" +msgstr "" + +#: ./doc/admin-guide-cloud/section_multi_backend.xml:111(para) +msgid "Before using it, a volume type has to be declared to Block Storage. This can be done by the following command:" +msgstr "" + +#: ./doc/admin-guide-cloud/section_multi_backend.xml:114(para) +msgid "Then, an extra-specification have to be created to link the volume type to a back-end name. Run this command:" +msgstr "" + +#: ./doc/admin-guide-cloud/section_multi_backend.xml:118(para) +msgid "This example creates a lvm volume type with volume_backend_name=LVM_iSCSI as extra-specifications." +msgstr "" + +#: ./doc/admin-guide-cloud/section_multi_backend.xml:121(para) +msgid "Create another volume type:" +msgstr "" + +#: ./doc/admin-guide-cloud/section_multi_backend.xml:124(para) +msgid "This second volume type is named lvm_gold and has LVM_iSCSI_b as back-end name." +msgstr "" + +#: ./doc/admin-guide-cloud/section_multi_backend.xml:129(para) +msgid "To list the extra-specifications, use this command:" +msgstr "" + +#: ./doc/admin-guide-cloud/section_multi_backend.xml:134(para) +msgid "If a volume type points to a volume_backend_name that does not exist in the Block Storage configuration, the filter_scheduler returns an error that it cannot find a valid host with the suitable back-end." +msgstr "" + +#: ./doc/admin-guide-cloud/section_multi_backend.xml:143(title) +msgid "Usage" +msgstr "" + +#: ./doc/admin-guide-cloud/section_multi_backend.xml:144(para) +msgid "When you create a volume, you must specify the volume type. The extra-specifications of the volume type are used to determine which back-end has to be used. Considering the cinder.conf described previously, the scheduler creates this volume on lvmdriver-1 or lvmdriver-2." +msgstr "" + +#: ./doc/admin-guide-cloud/section_multi_backend.xml:153(para) +msgid "This second volume is created on lvmdriver-3." +msgstr "" + +#: ./doc/admin-guide-cloud/section_ts_multipath_warn.xml:6(title) +msgid "Multipath Call Failed Exit" +msgstr "" + +#: ./doc/admin-guide-cloud/section_ts_multipath_warn.xml:9(para) +msgid "Multipath call failed exit. This warning occurs in the Compute log if you do not have the optional multipath-tools package installed on the Compute node. This is an optional package and the volume attachment does work without the multipath tools installed. If the multipath-tools package is installed on the Compute node, it is used to perform the volume attachment. The IDs in your message are unique to your system." +msgstr "" + +#: ./doc/admin-guide-cloud/section_ts_multipath_warn.xml:21(para) +msgid "Run the following command on the Compute node to install the multipath-tools packages." +msgstr "" + +#: ./doc/admin-guide-cloud/section_volume-migration.xml:6(title) +msgid "Migrate volumes" +msgstr "" + +#: ./doc/admin-guide-cloud/section_volume-migration.xml:7(para) +msgid "The Havana release of OpenStack introduces the ability to migrate volumes between back-ends. Migrating a volume transparently moves its data from the current back-end for the volume to a new one. This is an administrator function, and can be used for functions including storage evacuation (for maintenance or decommissioning), or manual optimizations (for example, performance, reliability, or cost)." +msgstr "" + +#: ./doc/admin-guide-cloud/section_volume-migration.xml:14(para) +msgid "These workflows are possible for a migration:" +msgstr "" + +#: ./doc/admin-guide-cloud/section_volume-migration.xml:17(para) +msgid "If the storage can migrate the volume on its own, it is given the opportunity to do so. This allows the Block Storage driver to enable optimizations that the storage might be able to perform. If the back-end is not able to perform the migration, the Block Storage Service uses one of two generic flows, as follows." +msgstr "" + +#: ./doc/admin-guide-cloud/section_volume-migration.xml:26(para) +msgid "If the volume is not attached, the Block Storage Service creates a volume and copies the data from the original to the new volume. Note: While most back-ends support this function, not all do. See driver documentation in the OpenStack Configuration Reference for more details." +msgstr "" + +#: ./doc/admin-guide-cloud/section_volume-migration.xml:37(para) +msgid "If the volume is attached to a VM instance, the Block Storage Service creates a volume, and calls Compute to copy the data from the original to the new volume. Currently this is supported only by the Compute libvirt driver." +msgstr "" + +#: ./doc/admin-guide-cloud/section_volume-migration.xml:44(para) +msgid "As an example, this scenario shows two LVM back-ends and migrates an attached volume from one to the other. This scenario uses the third migration flow." +msgstr "" + +#: ./doc/admin-guide-cloud/section_volume-migration.xml:47(para) +msgid "First, list the available back-ends:" +msgstr "" + +#: ./doc/admin-guide-cloud/section_volume-migration.xml:51(para) +msgid "Next, as the admin user, you can see the current status of the volume (replace the example ID with your own):" +msgstr "" + +#: ./doc/admin-guide-cloud/section_volume-migration.xml:75(para) +msgid "Note these attributes:" +msgstr "" + +#: ./doc/admin-guide-cloud/section_volume-migration.xml:78(para) +msgid "os-vol-host-attr:host - the volume's current back-end." +msgstr "" + +#: ./doc/admin-guide-cloud/section_volume-migration.xml:82(para) +msgid "os-vol-mig-status-attr:migstat - the status of this volume's migration ('None' means that a migration is not currently in progress)." +msgstr "" + +#: ./doc/admin-guide-cloud/section_volume-migration.xml:87(para) +msgid "os-vol-mig-status-attr:name_id - the volume ID that this volume's name on the back-end is based on. Before a volume is ever migrated, its name on the back-end storage may be based on the volume's ID (see the volume_name_template configuration parameter). For example, if volume_name_template is kept as the default value (volume-%s), your first LVM back-end has a logical volume named volume-6088f80a-f116-4331-ad48-9afb0dfb196c. During the course of a migration, if you create a volume and copy over the data, the volume get the new name but keeps its original ID. This is exposed by the name_id attribute." +msgstr "" + +#: ./doc/admin-guide-cloud/section_volume-migration.xml:104(para) +msgid "Migrate this volume to the second LVM back-end:" +msgstr "" + +#: ./doc/admin-guide-cloud/section_volume-migration.xml:106(para) +msgid "You can use the command to see the status of the migration. While migrating, the migstat attribute shows states such as migrating or completing. On error, migstat is set to None and the host attribute shows the original host. On success, in this example, the output looks like:" +msgstr "" + +#: ./doc/admin-guide-cloud/section_volume-migration.xml:137(para) +msgid "Note that migstat is None, host is the new host, and name_id holds the ID of the volume created by the migration. If you look at the second LVM back-end, you find the logical volume volume-133d1f56-9ffc-4f57-8798-d5217d851862." +msgstr "" + +#: ./doc/admin-guide-cloud/section_volume-migration.xml:144(para) +msgid "The migration is not visible to non-admin users (for example, through the volume status). However, some operations are not allowed while a migration is taking place, such as attaching/detaching a volume and deleting a volume. If a user performs such an action during a migration, an error is returned." +msgstr "" + +#: ./doc/admin-guide-cloud/section_volume-migration.xml:152(para) +msgid "Migrating volumes that have snapshots are currently not allowed." +msgstr "" + +#: ./doc/admin-guide-cloud/ch_dashboard.xml:7(title) ./doc/admin-guide-cloud/ch_compute.xml:766(title) +msgid "Dashboard" +msgstr "" + +#: ./doc/admin-guide-cloud/ch_dashboard.xml:8(para) +msgid "The OpenStack dashboard is a web-based interface that allows you to manage OpenStack resources and services. The dashboard allows you to interact with the OpenStack Compute cloud controller using the OpenStack APIs. For more information about installing and configuring the dashboard, see the OpenStack Installation Guide for your operating system." +msgstr "" + +#: ./doc/admin-guide-cloud/ch_dashboard.xml:20(para) +msgid ", for customizing the dashboard." +msgstr "" + +#: ./doc/admin-guide-cloud/ch_dashboard.xml:24(para) +msgid ", for setting up session storage for the dashboard." +msgstr "" + +#: ./doc/admin-guide-cloud/ch_dashboard.xml:28(para) +msgid "The Horizon documentation, for deploying the dashboard." +msgstr "" + +#: ./doc/admin-guide-cloud/ch_dashboard.xml:32(para) +msgid "The OpenStack End User Guide, for launching instances with the dashboard.." +msgstr "" + +#: ./doc/admin-guide-cloud/ch_dashboard.xml:16(para) +msgid "For more information about using the dashboard, see: " +msgstr "" + +#: ./doc/admin-guide-cloud/section_ts_attach_vol_fail_not_JSON.xml:5(title) +msgid "Nova volume attach error, not JSON serializable" +msgstr "" + +#: ./doc/admin-guide-cloud/section_ts_attach_vol_fail_not_JSON.xml:8(para) +msgid "When you attach a nova volume to a VM, you will see the error with stack trace in /var/log/nova/nova-volume.log. The JSON serializable issue is caused by an RPC response timeout." +msgstr "" + +#: ./doc/admin-guide-cloud/section_ts_attach_vol_fail_not_JSON.xml:16(para) +msgid "Make sure your iptables allow port 3260 communication on the ISC controller. Run this command:" +msgstr "" + +#: ./doc/admin-guide-cloud/section_ts_attach_vol_fail_not_JSON.xml:19(para) +msgid "If the port communication is properly configured, you can try running this command." +msgstr "" + +#: ./doc/admin-guide-cloud/section_ts_attach_vol_fail_not_JSON.xml:23(para) +msgid "This service does not exist on Debian or Ubuntu." +msgstr "" + +#: ./doc/admin-guide-cloud/section_ts_attach_vol_fail_not_JSON.xml:26(para) +msgid "If you continue to get the RPC response time out, your ISC controller and KVM host might be incompatible." +msgstr "" + +#: ./doc/admin-guide-cloud/section_ts_duplicate_3par_host.xml:4(title) +msgid "Duplicate 3PAR host" +msgstr "" + +#: ./doc/admin-guide-cloud/section_ts_duplicate_3par_host.xml:7(para) +msgid "This error may be caused by a volume being exported outside of OpenStack using a host name different from the system name that OpenStack expects. This error could be displayed with the IQN if the host was exported using iSCSI." +msgstr "" + +#: ./doc/admin-guide-cloud/section_ts_duplicate_3par_host.xml:13(para) +msgid "Change the 3PAR host name to match the one that OpenStack expects. The 3PAR host constructed by the driver uses just the local hostname, not the fully qualified domain name (FQDN) of the compute host. For example, if the FQDN was myhost.example.com, just myhost would be used as the 3PAR hostname. IP addresses are not allowed as host names on the 3PAR storage server." +msgstr "" + +#. When image changes, this message will be marked fuzzy or untranslated for you. +#. It doesn't matter what you translate it to: it's not used at all. +#: ./doc/admin-guide-cloud/ch_compute.xml:214(None) +msgid "@@image: '../common/figures/instance-life-1.png'; md5=c7e56263f9ffb5a5cffb59fbc5ffba35" +msgstr "" + +#. When image changes, this message will be marked fuzzy or untranslated for you. +#. It doesn't matter what you translate it to: it's not used at all. +#: ./doc/admin-guide-cloud/ch_compute.xml:233(None) +msgid "@@image: '../common/figures/instance-life-2.png'; md5=84aed8a4c2575548c2f8bacf496465ac" +msgstr "" + +#. When image changes, this message will be marked fuzzy or untranslated for you. +#. It doesn't matter what you translate it to: it's not used at all. +#: ./doc/admin-guide-cloud/ch_compute.xml:275(None) +msgid "@@image: '../common/figures/instance-life-3.png'; md5=e25d1bd617373f95e1b8a12605a65ac6" +msgstr "" + +#. When image changes, this message will be marked fuzzy or untranslated for you. +#. It doesn't matter what you translate it to: it's not used at all. +#: ./doc/admin-guide-cloud/ch_compute.xml:1543(None) +msgid "@@image: '../common/figures/SCH_5007_V00_NUAC-multi_nic_OpenStack-Flat-manager.jpg'; md5=31f7e15a45d042bd9d6499631e2f3ccc" +msgstr "" + +#. When image changes, this message will be marked fuzzy or untranslated for you. +#. It doesn't matter what you translate it to: it's not used at all. +#: ./doc/admin-guide-cloud/ch_compute.xml:1553(None) +msgid "@@image: '../common/figures/SCH_5007_V00_NUAC-multi_nic_OpenStack-Flat-DHCP-manager.jpg'; md5=0f33a228f1dec4a4e4424dd5ee81bde8" +msgstr "" + +#. When image changes, this message will be marked fuzzy or untranslated for you. +#. It doesn't matter what you translate it to: it's not used at all. +#: ./doc/admin-guide-cloud/ch_compute.xml:1563(None) +msgid "@@image: '../common/figures/SCH_5007_V00_NUAC-multi_nic_OpenStack-VLAN-manager.jpg'; md5=0acaf3e2041f941d8fee2d111f37e7ac" +msgstr "" + +#: ./doc/admin-guide-cloud/ch_compute.xml:9(title) ./doc/admin-guide-cloud/section_networking-config-identity.xml:102(title) +msgid "Compute" +msgstr "" + +#: ./doc/admin-guide-cloud/ch_compute.xml:10(para) +msgid "The OpenStack Compute service allows you to control an Infrastructure-as-a-Service (IaaS) cloud computing platform. It gives you control over instances and networks, and allows you to manage access to the cloud through users and projects." +msgstr "" + +#: ./doc/admin-guide-cloud/ch_compute.xml:15(para) +msgid "Compute does not include any virtualization software. Instead, it defines drivers that interact with underlying virtualization mechanisms that run on your host operating system, and exposes functionality over a web-based API." +msgstr "" + +#: ./doc/admin-guide-cloud/ch_compute.xml:20(title) +msgid "Hypervisors" +msgstr "" + +#: ./doc/admin-guide-cloud/ch_compute.xml:21(para) +msgid "Compute controls hypervisors through an API server. Selecting the best hypervisor to use can be difficult, and you must take budget, resource constraints, supported features, and required technical specifications into account. However, the majority of OpenStack development is done on systems using KVM and Xen-based hypervisors. For a detailed list of features and support across different hypervisors, see http://wiki.openstack.org/HypervisorSupportMatrix." +msgstr "" + +#: ./doc/admin-guide-cloud/ch_compute.xml:31(para) +msgid "You can also orchestrate clouds using multiple hypervisors in different availability zones. The types of virtualization standards that can be used with Compute include:" +msgstr "" + +#: ./doc/admin-guide-cloud/ch_compute.xml:40(link) +msgid "Baremetal" +msgstr "" + +#: ./doc/admin-guide-cloud/ch_compute.xml:54(link) +msgid "Kernel-based Virtual Machine (KVM)" +msgstr "" + +#: ./doc/admin-guide-cloud/ch_compute.xml:60(link) +msgid "Linux Containers (LXC)" +msgstr "" + +#: ./doc/admin-guide-cloud/ch_compute.xml:66(link) +msgid "Quick Emulator (QEMU)" +msgstr "" + +#: ./doc/admin-guide-cloud/ch_compute.xml:73(link) +msgid "User Mode Linux (UML)" +msgstr "" + +#: ./doc/admin-guide-cloud/ch_compute.xml:80(link) +msgid "VMWare vSphere" +msgstr "" + +#: ./doc/admin-guide-cloud/ch_compute.xml:87(link) +msgid "Xen" +msgstr "" + +#: ./doc/admin-guide-cloud/ch_compute.xml:91(para) +msgid "For more information about hypervisors, see the Hypervisors section in the OpenStack Configuration Reference." +msgstr "" + +#: ./doc/admin-guide-cloud/ch_compute.xml:98(title) +msgid "Tenants, users, and roles" +msgstr "" + +#: ./doc/admin-guide-cloud/ch_compute.xml:99(para) +msgid "The Compute system is designed to be used by different consumers in the form of tenants on a shared system, and role-based access assignments. Roles control the actions that a user is allowed to perform." +msgstr "" + +#: ./doc/admin-guide-cloud/ch_compute.xml:103(para) +msgid "Tenants are isolated resource containers that form the principal organizational structure within the Compute service. They consist of an individual VLAN, and volumes, instances, images, keys, and users. A user can specify the tenant by appending :project_id to their access key. If no tenant is specified in the API request, Compute attempts to use a tenant with the same ID as the user." +msgstr "" + +#: ./doc/admin-guide-cloud/ch_compute.xml:111(para) +msgid "For tenants, quota controls are available to limit the:" +msgstr "" + +#: ./doc/admin-guide-cloud/ch_compute.xml:115(para) +msgid "number of volumes that may be launched." +msgstr "" + +#: ./doc/admin-guide-cloud/ch_compute.xml:118(para) +msgid "number of processor cores and the amount of RAM that can be allocated." +msgstr "" + +#: ./doc/admin-guide-cloud/ch_compute.xml:122(para) +msgid "floating IP addresses assigned to any instance when it launches. This allows instances to have the same publicly accessible IP addresses." +msgstr "" + +#: ./doc/admin-guide-cloud/ch_compute.xml:127(para) +msgid "fixed IP addresses assigned to the same instance when it launches. This allows instances to have the same publicly or privately accessible IP addresses." +msgstr "" + +#: ./doc/admin-guide-cloud/ch_compute.xml:133(para) +msgid "Roles control the actions a user is allowed to perform. By default, most actions do not require a particular role, but you can configure them by editing the policy.json file for user roles. For example, a rule can be defined so that a user must have the admin role in order to be able to allocate a public IP address." +msgstr "" + +#: ./doc/admin-guide-cloud/ch_compute.xml:140(para) +msgid "A tenant limits users' access to particular images. Each user is assigned a username and password. Keypairs granting access to an instance are enabled for each user, but quotas are set, so that each tenant can control resource consumption across available hardware resources." +msgstr "" + +#: ./doc/admin-guide-cloud/ch_compute.xml:147(para) +msgid "Earlier versions of OpenStack used the term project instead of tenant. Because of this legacy terminology, some command-line tools use --project_id where you would normally expect to enter a tenant ID." +msgstr "" + +#: ./doc/admin-guide-cloud/ch_compute.xml:157(title) +msgid "Images and instances" +msgstr "" + +#: ./doc/admin-guide-cloud/ch_compute.xml:158(para) +msgid "Disk images provide templates for virtual machine file systems. The Glance service manages storage and management of images." +msgstr "" + +#: ./doc/admin-guide-cloud/ch_compute.xml:161(para) +msgid "Instances are the individual virtual machines that run on physical compute nodes. Users can launch any number of instances from the same image. Each launched instance runs from a copy of the base image so that any changes made to the instance do not affect the base image. You can take snapshots of running instances to create an image based on the current disk state of a particular instance. The Compute services manages instances." +msgstr "" + +#: ./doc/admin-guide-cloud/ch_compute.xml:169(para) +msgid "For more information about creating and troubleshooting images, see the Manage Images section of the OpenStack Admin User Guide." +msgstr "" + +#: ./doc/admin-guide-cloud/ch_compute.xml:175(para) +msgid "For more information about image configuration options, see the Image Services section of the OpenStack Configuration Reference." +msgstr "" + +#: ./doc/admin-guide-cloud/ch_compute.xml:181(para) +msgid "When you launch an instance, you must choose a flavor, which represents a set of virtual resources. Flavors define how many virtual CPUs an instance has and the amount of RAM and size of its ephemeral disks. OpenStack provides a number of predefined flavors that you can edit or add to. Users must select from the set of available flavors defined on their cloud." +msgstr "" + +#: ./doc/admin-guide-cloud/ch_compute.xml:189(para) +msgid "For more information about flavors, see the Flavors section in the OpenStack Operations Guide." +msgstr "" + +#: ./doc/admin-guide-cloud/ch_compute.xml:193(para) +msgid "You can add and remove additional resources from running instances, such as persistent volume storage, or public IP addresses. The example used in this chapter is of a typical virtual system within an OpenStack cloud. It uses the cinder-volume service, which provides persistent block storage, instead of the ephemeral storage provided by the selected instance flavor." +msgstr "" + +#: ./doc/admin-guide-cloud/ch_compute.xml:201(para) +msgid "This diagram shows the system state prior to launching an instance. The image store, fronted by the image service, Glance, has a number of predefined images. Inside the cloud, a compute node contains the available vCPU, memory, and local disk resources. Additionally, the cinder-volume service provides a number of predefined volumes." +msgstr "" + +#: ./doc/admin-guide-cloud/ch_compute.xml:209(title) +msgid "Base image state with no running instances" +msgstr "" + +#: ./doc/admin-guide-cloud/ch_compute.xml:218(para) +msgid "To launch an instance, select an image, a flavor, and other optional attributes. The selected flavor provides a root volume, labeled vda in this diagram, and additional ephemeral storage, labeled vdb. In this example, the cinder-volume store is mapped to the third virtual disk on this instance, vdc." +msgstr "" + +#: ./doc/admin-guide-cloud/ch_compute.xml:227(title) +msgid "Instance creation from image and runtime state" +msgstr "" + +#: ./doc/admin-guide-cloud/ch_compute.xml:237(para) +msgid "The base image is copied from the image store to the local disk. The local disk is the first disk that the instance accesses, and is labeled vda. By using smaller images, your instances start up faster as less data needs to be copied across the network." +msgstr "" + +#: ./doc/admin-guide-cloud/ch_compute.xml:242(para) +msgid "A new empty disk, labeled vdb is also created. This is an empty ephemeral disk, which is destroyed when you delete the instance." +msgstr "" + +#: ./doc/admin-guide-cloud/ch_compute.xml:245(para) +msgid "The compute node is attached to the cinder-volume using iSCSI, and maps to the third disk, vdc. The vCPU and memory resources are provisioned and the instance is booted from vda. The instance runs and changes data on the disks as indicated in red in the diagram." +msgstr "" + +#: ./doc/admin-guide-cloud/ch_compute.xml:255(para) +msgid "Some of the details in this example scenario might be different in your environment. Specifically, you might use a different type of back-end storage or different network protocols. One common variant is that the ephemeral storage used for volumes vda and vdb could be backed by network storage rather than a local disk." +msgstr "" + +#: ./doc/admin-guide-cloud/ch_compute.xml:264(para) +msgid "When the instance is deleted, the state is reclaimed with the exception of the persistent volume. The ephemeral storage is purged, memory and vCPU resources are released. The image remains unchanged throughout." +msgstr "" + +#: ./doc/admin-guide-cloud/ch_compute.xml:269(title) +msgid "End state of image and volume after instance exits" +msgstr "" + +#: ./doc/admin-guide-cloud/ch_compute.xml:281(title) +msgid "System architecture" +msgstr "" + +#: ./doc/admin-guide-cloud/ch_compute.xml:282(para) +msgid "OpenStack Compute contains several main components. The cloud controller represents the global state and interacts with the other components. The API server acts as the web services front end for the cloud controller. The compute controller provides compute server resources and usually also contains the Compute service." +msgstr "" + +#: ./doc/admin-guide-cloud/ch_compute.xml:289(para) +msgid "The object store is an optional component that provides storage services. An auth manager provides authentication and authorization services when used with the Compute system, or you can use the identity service as a separate authentication service instead. A volume controller provides fast and permanent block-level storage for the compute servers. The network controller provides virtual networks to enable compute servers to interact with each other and with the public network. The scheduler is used to select the most suitable compute controller to host an instance." +msgstr "" + +#: ./doc/admin-guide-cloud/ch_compute.xml:303(para) +msgid "Compute uses a messaging-based, shared nothing architecture. All major components exist on multiple servers, including the compute, volume, and network controllers, and the object store or image service. The state of the entire system is stored in a database. The cloud controller communicates with the internal object store using HTTP, but it communicates with the scheduler, network controller, and volume controller using AMQP (advanced message queueing protocol). To avoid blocking a component while waiting for a response, Compute uses asynchronous calls, with a callback that is triggered when a response is received." +msgstr "" + +#: ./doc/admin-guide-cloud/ch_compute.xml:317(title) +msgid "Block storage" +msgstr "" + +#: ./doc/admin-guide-cloud/ch_compute.xml:318(para) +msgid "OpenStack provides two classes of block storage: ephemeral storage and persistent volumes. Volumes are persistent virtualized block devices independent of any particular instance." +msgstr "" + +#: ./doc/admin-guide-cloud/ch_compute.xml:322(para) +msgid "Ephemeral storage is associated with a single unique instance, and it exists only for the life of that instance. The amount of ephemeral storage is defined by the flavor of the instance. Generally, the root file system for an instance will be stored on ephemeral storage. It persists across reboots of the guest operating system, but when the instance is deleted, the ephemeral storage is also removed." +msgstr "" + +#: ./doc/admin-guide-cloud/ch_compute.xml:330(para) +msgid "In addition to the ephemeral root volume, all flavors except the smallest, m1.tiny, also provide an additional ephemeral block device of between 20 and 160GB. These sizes can be configured to suit your environment. This is presented as a raw block device with no partition table or file system. Cloud-aware operating system images can discover, format, and mount these storage devices. For example, the cloud-init package included in Ubuntu's stock cloud images format this space as an ext3 file system and mount it on /mnt. This is a feature of the guest operating system you are using, and is not an OpenStack mechanism. OpenStack only provisions the raw storage." +msgstr "" + +#: ./doc/admin-guide-cloud/ch_compute.xml:345(para) +msgid "Persistent volumes are created by users and their size is limited only by the user's quota and availability limits. Upon initial creation, volumes are raw block devices without a partition table or a file system. To partition or format volumes, you must attach them to an instance. Once they are attached to an instance, you can use persistent volumes in much the same way as you would use external hard disk drive. You can attach volumes to only one instance at a time, although you can detach and reattach volumes to as many different instances as you like." +msgstr "" + +#: ./doc/admin-guide-cloud/ch_compute.xml:356(para) +msgid "Persistent volumes can be configured as bootable and used to provide a persistent virtual instance similar to traditional non-cloud-based virtualization systems. Typically, the resulting instance can also still have ephemeral storage depending on the flavor selected, but the root file system can be on the persistent volume and its state maintained even if the instance is shut down. For more information about this type of configuration, see the OpenStack Configuration Reference." +msgstr "" + +#: ./doc/admin-guide-cloud/ch_compute.xml:367(para) +msgid "Persistent volumes do not provide concurrent access from multiple instances. That type of configuration requires a traditional network file system like NFS or CIFS, or a cluster file system such as GlusterFS. These systems can be built within an OpenStack cluster or provisioned outside of it, but OpenStack software does not provide these features." +msgstr "" + +#: ./doc/admin-guide-cloud/ch_compute.xml:377(title) +msgid "Image management" +msgstr "" + +#: ./doc/admin-guide-cloud/ch_compute.xml:378(para) +msgid "The OpenStack Image service discovers, registers, and retrieves virtual machine images. The service also includes a RESTful API that allows you to query VM image metadata and retrieve the actual image with HTTP requests. For more information about the API, see the OpenStack API or the Python API." +msgstr "" + +#: ./doc/admin-guide-cloud/ch_compute.xml:387(para) +msgid "The OpenStack Image service can be controlled using a command line tool. For more information about the OpenStack Image command line tool, see the Image Management section in the OpenStack User Guide." +msgstr "" + +#: ./doc/admin-guide-cloud/ch_compute.xml:393(para) +msgid "Virtual images that have been made available through the Image service can be stored in a variety of ways. In order to use these services, you must have a working installation of the Image service, with a working endpoint, and users that have been created in the Identity service. Additionally, you must meet the environment variables required by the Compute and Image clients." +msgstr "" + +#: ./doc/admin-guide-cloud/ch_compute.xml:401(para) +msgid "The Image service supports these back end stores:" +msgstr "" + +#: ./doc/admin-guide-cloud/ch_compute.xml:404(term) +msgid "File system" +msgstr "" + +#: ./doc/admin-guide-cloud/ch_compute.xml:406(para) +msgid "The OpenStack Image service stores virtual machine images in the file system back-end by default. This simple back end writes image files to the local file system." +msgstr "" + +#: ./doc/admin-guide-cloud/ch_compute.xml:413(term) +msgid "Object Storage service" +msgstr "" + +#: ./doc/admin-guide-cloud/ch_compute.xml:415(para) +msgid "The OpenStack highly-available object storage service." +msgstr "" + +#: ./doc/admin-guide-cloud/ch_compute.xml:420(term) +msgid "S3" +msgstr "" + +#: ./doc/admin-guide-cloud/ch_compute.xml:422(para) +msgid "The Amazon S3 service." +msgstr "" + +#: ./doc/admin-guide-cloud/ch_compute.xml:426(term) +msgid "HTTP" +msgstr "" + +#: ./doc/admin-guide-cloud/ch_compute.xml:428(para) +msgid "OpenStack Image Service can read virtual machine images that are available on the internet using HTTP. This store is read only." +msgstr "" + +#: ./doc/admin-guide-cloud/ch_compute.xml:435(term) +msgid "Rados block device (RBD)" +msgstr "" + +#: ./doc/admin-guide-cloud/ch_compute.xml:437(para) +msgid "Stores images inside of a Ceph storage cluster using Ceph's RBD interface." +msgstr "" + +#: ./doc/admin-guide-cloud/ch_compute.xml:442(term) +msgid "GridFS" +msgstr "" + +#: ./doc/admin-guide-cloud/ch_compute.xml:444(para) +msgid "Stores images using MongoDB." +msgstr "" + +#: ./doc/admin-guide-cloud/ch_compute.xml:450(title) +msgid "Instance management tools" +msgstr "" + +#: ./doc/admin-guide-cloud/ch_compute.xml:451(para) +msgid "OpenStack provides command line, web-based, and API-based instance management tools. Additionally, a number of third party management tools are available, using either the native API or the provided EC2-compatible API." +msgstr "" + +#: ./doc/admin-guide-cloud/ch_compute.xml:456(para) +msgid "The OpenStack python-novaclient package provides a basic command line utility, which uses the command. This is available as a native package for most Linux distributions, or you can install the latest version using the pip python package installer: " +msgstr "" + +#: ./doc/admin-guide-cloud/ch_compute.xml:466(para) +msgid "For more information about python-novaclient and other available command line tools, see the OpenStack End User Guide." +msgstr "" + +#: ./doc/admin-guide-cloud/ch_compute.xml:574(title) +msgid "EC2 compatibility API" +msgstr "" + +#: ./doc/admin-guide-cloud/ch_compute.xml:575(para) +msgid "In addition to the native compute API, OpenStack provides an EC2-compatible API. This API allows EC2 legacy workflows built for EC2 to work with OpenStack." +msgstr "" + +#: ./doc/admin-guide-cloud/ch_compute.xml:578(para) +msgid "The OpenStack Configuration Reference lists configuration options for customizing this compatibility API on your OpenStack cloud." +msgstr "" + +#: ./doc/admin-guide-cloud/ch_compute.xml:582(para) +msgid "Numerous third party tools and language-specific SDKs can be used to interact with OpenStack clouds, using both native and compatibility APIs. Some of the more popular third-party tools are:" +msgstr "" + +#: ./doc/admin-guide-cloud/ch_compute.xml:588(term) +msgid "Euca2ools" +msgstr "" + +#: ./doc/admin-guide-cloud/ch_compute.xml:590(para) +msgid "A popular open source command line tool for interacting with the EC2 API. This is convenient for multi-cloud environments where EC2 is the common API, or for transitioning from EC2-based clouds to OpenStack. For more information, see the euca2ools site." +msgstr "" + +#: ./doc/admin-guide-cloud/ch_compute.xml:601(term) +msgid "Hybridfox" +msgstr "" + +#: ./doc/admin-guide-cloud/ch_compute.xml:603(para) +msgid "A Firefox browser add-on that provides a graphical interface to many popular public and private cloud technologies, including OpenStack. For more information, see the hybridfox site." +msgstr "" + +#: ./doc/admin-guide-cloud/ch_compute.xml:612(term) +msgid "boto" +msgstr "" + +#: ./doc/admin-guide-cloud/ch_compute.xml:614(para) +msgid "A Python library for interacting with Amazon Web Services. It can be used to access OpenStack through the EC2 compatibility API. For more information, see the boto project page on GitHub." +msgstr "" + +#: ./doc/admin-guide-cloud/ch_compute.xml:623(term) +msgid "fog" +msgstr "" + +#: ./doc/admin-guide-cloud/ch_compute.xml:625(para) +msgid "A Ruby cloud services library. It provides methods for interacting with a large number of cloud and virtualization platforms, including OpenStack. For more information, see the fog site." +msgstr "" + +#: ./doc/admin-guide-cloud/ch_compute.xml:634(term) +msgid "php-opencloud" +msgstr "" + +#: ./doc/admin-guide-cloud/ch_compute.xml:636(para) +msgid "A PHP SDK designed to work with most OpenStack- based cloud deployments, as well as Rackspace public cloud. For more information, see the php-opencloud site." +msgstr "" + +#: ./doc/admin-guide-cloud/ch_compute.xml:647(title) +msgid "Building blocks" +msgstr "" + +#. There are two fundamental requirements for a +#. computing system, software and hardware. +#. Virtualization and cloud frameworks tend to blur these +#. lines and some of your "hardware" might actually be +#. "software" but conceptually you still need an +#. operating system and something to run it on. +#: ./doc/admin-guide-cloud/ch_compute.xml:654(para) +msgid "In OpenStack the base operating system is usually copied from an image stored in the OpenStack Image service. This is the most common case and results in an ephemeral instance that starts from a known template state and loses all accumulated states on shutdown. It is also possible to put an operating system on a persistent volume in the Nova-Volume or Cinder volume system. This gives a more traditional persistent system that accumulates states, which are preserved across restarts. To get a list of available images on your system run: " +msgstr "" + +#: ./doc/admin-guide-cloud/ch_compute.xml:673(para) +msgid "The displayed image attributes are:" +msgstr "" + +#: ./doc/admin-guide-cloud/ch_compute.xml:676(literal) +msgid "ID" +msgstr "" + +#: ./doc/admin-guide-cloud/ch_compute.xml:678(para) +msgid "Automatically generated UUID of the image" +msgstr "" + +#: ./doc/admin-guide-cloud/ch_compute.xml:683(literal) +msgid "Name" +msgstr "" + +#: ./doc/admin-guide-cloud/ch_compute.xml:685(para) +msgid "Free form, human-readable name for image" +msgstr "" + +#: ./doc/admin-guide-cloud/ch_compute.xml:690(literal) +msgid "Status" +msgstr "" + +#: ./doc/admin-guide-cloud/ch_compute.xml:692(para) +msgid "The status of the image. Images marked ACTIVE are available for use." +msgstr "" + +#: ./doc/admin-guide-cloud/ch_compute.xml:698(literal) +msgid "Server" +msgstr "" + +#: ./doc/admin-guide-cloud/ch_compute.xml:700(para) +msgid "For images that are created as snapshots of running instances, this is the UUID of the instance the snapshot derives from. For uploaded images, this field is blank." +msgstr "" + +#: ./doc/admin-guide-cloud/ch_compute.xml:708(para) +msgid "Virtual hardware templates are called flavors. The default installation provides five flavors. By default, these are configurable by admin users, however that behavior can be changed by redefining the access controls for compute_extension:flavormanage in /etc/nova/policy.json on the compute-api server." +msgstr "" + +#: ./doc/admin-guide-cloud/ch_compute.xml:716(para) +msgid "For a list of flavors that are available on your system:" +msgstr "" + +#: ./doc/admin-guide-cloud/ch_compute.xml:742(title) +msgid "Control where instances run" +msgstr "" + +#: ./doc/admin-guide-cloud/ch_compute.xml:743(para) +msgid "The OpenStack Configuration Reference provides detailed information on controlling where your instances run, including ensuring a set of instances run on different compute nodes for service resiliency or on the same node for high performance inter-instance communications." +msgstr "" + +#: ./doc/admin-guide-cloud/ch_compute.xml:752(replaceable) +msgid "availability-zone" +msgstr "" + +#: ./doc/admin-guide-cloud/ch_compute.xml:752(replaceable) +msgid "compute-host" +msgstr "" + +#: ./doc/admin-guide-cloud/ch_compute.xml:750(para) +msgid "Admin users can specify an exact compute node to run on using the command " +msgstr "" + +#: ./doc/admin-guide-cloud/ch_compute.xml:757(title) +msgid "Admin password injection" +msgstr "" + +#: ./doc/admin-guide-cloud/ch_compute.xml:758(para) +msgid "You can configure Compute to generate a random administrator (root) password and inject that password into the instance. If this feature is enabled, a user can ssh to an instance without an ssh keypair. The random password appears in the output of the command. You can also view and set the admin password from the dashboard." +msgstr "" + +#: ./doc/admin-guide-cloud/ch_compute.xml:767(para) +msgid "The dashboard is configured by default to display the admin password and allow the user to modify it." +msgstr "" + +#: ./doc/admin-guide-cloud/ch_compute.xml:770(para) +msgid "If you do not want to support password injection, we recommend disabling the password fields by editing your Dashboard local_settings file (file location will vary by Linux distribution, on Fedora/RHEL/CentOS: /etc/openstack-dashboard/local_settings, on Ubuntu and Debian: /etc/openstack-dashboard/local_settings.py and on openSUSE and SUSE Linux Enterprise Server: /usr/share/openstack-dashboard/openstack_dashboard/local/local_settings.py) " +msgstr "" + +#: ./doc/admin-guide-cloud/ch_compute.xml:786(title) +msgid "Libvirt-based hypervisors (KVM, QEMU, LXC)" +msgstr "" + +#: ./doc/admin-guide-cloud/ch_compute.xml:787(para) +msgid "For hypervisors such as KVM that use the libvirt backend, admin password injection is disabled by default. To enable it, set the following option in /etc/nova/nova.conf:" +msgstr "" + +#: ./doc/admin-guide-cloud/ch_compute.xml:795(para) +msgid "When enabled, Compute will modify the password of the root account by editing the /etc/shadow file inside of the virtual machine instance." +msgstr "" + +#: ./doc/admin-guide-cloud/ch_compute.xml:803(para) +msgid "The virtual machine image is a Linux distribution" +msgstr "" + +#: ./doc/admin-guide-cloud/ch_compute.xml:807(para) +msgid "The virtual machine has been configured to allow users to ssh as the root user. This is not the case for Ubuntu cloud images, which disallow ssh to the root account by default." +msgstr "" + +#: ./doc/admin-guide-cloud/ch_compute.xml:800(para) +msgid "Users will only be able to ssh to the instance using the admin password if:" +msgstr "" + +#: ./doc/admin-guide-cloud/ch_compute.xml:820(title) +msgid "XenAPI (XenServer/XCP)" +msgstr "" + +#: ./doc/admin-guide-cloud/ch_compute.xml:821(para) +msgid "Compute uses the XenAPI agent to inject passwords into guests when using the XenAPI hypervisor backend. The virtual machine image must be configured with the agent for password injection to work." +msgstr "" + +#: ./doc/admin-guide-cloud/ch_compute.xml:827(title) +msgid "Windows images (all hypervisors)" +msgstr "" + +#: ./doc/admin-guide-cloud/ch_compute.xml:828(para) +msgid "To support the admin password for Windows virtual machines, you must configure the Windows image to retrieve the admin password on boot by installing an agent such as cloudbase-init." +msgstr "" + +#: ./doc/admin-guide-cloud/ch_compute.xml:856(title) +msgid "Networking with nova-network" +msgstr "" + +#: ./doc/admin-guide-cloud/ch_compute.xml:857(para) +msgid "Understanding the networking configuration options helps you design the best configuration for your Compute instances." +msgstr "" + +#: ./doc/admin-guide-cloud/ch_compute.xml:861(title) +msgid "Networking options" +msgstr "" + +#: ./doc/admin-guide-cloud/ch_compute.xml:862(para) +msgid "This section offers a brief overview of each concept in networking for Compute. With the Grizzly release, you can choose to either install and configure nova-network for networking between VMs or use the Networking service (neutron) for networking. To configure Compute networking options with Neutron, see the ." +msgstr "" + +#: ./doc/admin-guide-cloud/ch_compute.xml:871(para) +msgid "For each VM instance, Compute assigns to it a private IP address. (Currently, Compute with nova-network only supports Linux bridge networking that enables the virtual interfaces to connect to the outside network through the physical interface.)" +msgstr "" + +#: ./doc/admin-guide-cloud/ch_compute.xml:878(para) +msgid "The network controller with nova-network provides virtual networks to enable compute servers to interact with each other and with the public network." +msgstr "" + +#: ./doc/admin-guide-cloud/ch_compute.xml:887(para) +msgid "Flat Network Manager" +msgstr "" + +#: ./doc/admin-guide-cloud/ch_compute.xml:890(para) +msgid "Flat DHCP Network Manager" +msgstr "" + +#: ./doc/admin-guide-cloud/ch_compute.xml:893(para) +msgid "VLAN Network Manager" +msgstr "" + +#: ./doc/admin-guide-cloud/ch_compute.xml:882(para) +msgid "Currently, Compute with nova-network supports these kinds of networks, implemented in different “Network Manager” types: " +msgstr "" + +#: ./doc/admin-guide-cloud/ch_compute.xml:896(para) +msgid "These networks can co-exist in a cloud system. However, because you can't yet select the type of network for a given project, you cannot configure more than one type of network in a given Compute installation." +msgstr "" + +#: ./doc/admin-guide-cloud/ch_compute.xml:902(para) +msgid "All networking options require network connectivity to be already set up between OpenStack physical nodes. OpenStack does not configure any physical network interfaces. OpenStack automatically creates all network bridges (for example, br100) and VM virtual interfaces." +msgstr "" + +#: ./doc/admin-guide-cloud/ch_compute.xml:909(para) +msgid "All machines must have a public and internal network interface (controlled by the options: public_interface for the public interface, and flat_interface and vlan_interface for the internal interface with flat / VLAN managers)." +msgstr "" + +#: ./doc/admin-guide-cloud/ch_compute.xml:919(para) +msgid "The internal network interface is used for communication with VMs, it shouldn't have an IP address attached to it before OpenStack installation (it serves merely as a fabric where the actual endpoints are VMs and dnsmasq). Also, the internal network interface must be put in promiscuous mode, because it must receive packets whose target MAC address is of the guest VM, not of the host." +msgstr "" + +#: ./doc/admin-guide-cloud/ch_compute.xml:930(para) +msgid "All the network managers configure the network using network drivers. For example, the Linux L3 driver (l3.py and linux_net.py), which makes use of iptables, route and other network management facilities, and libvirt's network filtering facilities. The driver isn't tied to any particular network manager; all network managers use the same driver. The driver usually initializes (creates bridges and so on) only when the first VM lands on this host node." +msgstr "" + +#: ./doc/admin-guide-cloud/ch_compute.xml:944(para) +msgid "All network managers operate in either single-host or multi-host mode. This choice greatly influences the network configuration. In single-host mode, a single nova-network service provides a default gateway for VMs and hosts a single DHCP server (dnsmasq). In multi-host mode, each compute node runs its own nova-network service. In both cases, all traffic between VMs and the outer world flows through nova-network. Each mode has its pros and cons. Read more in the OpenStack Configuration Reference." +msgstr "" + +#: ./doc/admin-guide-cloud/ch_compute.xml:961(para) +msgid "Compute makes a distinction between fixed IPs and floating IPs for VM instances. Fixed IPs are IP addresses that are assigned to an instance on creation and stay the same until the instance is explicitly terminated. By contrast, floating IPs are addresses that can be dynamically associated with an instance. A floating IP address can be disassociated and associated with another instance at any time. A user can reserve a floating IP for their project." +msgstr "" + +#: ./doc/admin-guide-cloud/ch_compute.xml:972(para) +msgid "In Flat Mode, a network administrator specifies a subnet. The IP addresses for VM instances are grabbed from the subnet, and then injected into the image on launch. Each instance receives a fixed IP address from the pool of available addresses. A system administrator may create the Linux networking bridge (typically named br100, although this configurable) on the systems running the nova-network service. All instances of the system are attached to the same bridge, configured manually by the network administrator." +msgstr "" + +#: ./doc/admin-guide-cloud/ch_compute.xml:986(para) +msgid "The configuration injection currently only works on Linux-style systems that keep networking configuration in /etc/network/interfaces." +msgstr "" + +#: ./doc/admin-guide-cloud/ch_compute.xml:991(para) +msgid "In Flat DHCP Mode, OpenStack starts a DHCP server (dnsmasq) to pass out IP addresses to VM instances from the specified subnet in addition to manually configuring the networking bridge. IP addresses for VM instances are grabbed from a subnet specified by the network administrator." +msgstr "" + +#: ./doc/admin-guide-cloud/ch_compute.xml:997(para) +msgid "Like Flat Mode, all instances are attached to a single bridge on the compute node. In addition a DHCP server is running to configure instances (depending on single-/multi-host mode, alongside each nova-network). In this mode, Compute does a bit more configuration in that it attempts to bridge into an ethernet device (flat_interface, eth0 by default). For every instance, nova allocates a fixed IP address and configure dnsmasq with the MAC/IP pair for the VM. Dnsmasq doesn't take part in the IP address allocation process, it only hands out IPs according to the mapping done by nova. Instances receive their fixed IPs by doing a dhcpdiscover. These IPs are not assigned to any of the host's network interfaces, only to the VM's guest-side interface." +msgstr "" + +#: ./doc/admin-guide-cloud/ch_compute.xml:1014(para) +msgid "In any setup with flat networking, the hosts providing the nova-network service are responsible for forwarding traffic from the private network. They also run and configure dnsmasq as a DHCP server listening on this bridge, usually on IP address 10.0.0.1 (see DHCP server: dnsmasq ). Compute can determine the NAT entries for each network, though sometimes NAT is not used, such as when configured with all public IPs or a hardware router is used (one of the HA options). Such hosts need to have br100 configured and physically connected to any other nodes that are hosting VMs. You must set the flat_network_bridge option or create networks with the bridge parameter in order to avoid raising an error. Compute nodes have iptables/ebtables entries created for each project and instance to protect against IP/MAC address spoofing and ARP poisoning." +msgstr "" + +#: ./doc/admin-guide-cloud/ch_compute.xml:1034(para) +msgid "In single-host Flat DHCP mode you will be able to ping VMs through their fixed IP from the nova-network node, but you cannot ping them from the compute nodes. This is expected behavior." +msgstr "" + +#: ./doc/admin-guide-cloud/ch_compute.xml:1041(para) +msgid "VLAN Network Mode is the default mode for OpenStack Compute. In this mode, Compute creates a VLAN and bridge for each project. For multiple machine installation, the VLAN Network Mode requires a switch that supports VLAN tagging (IEEE 802.1Q). The project gets a range of private IPs that are only accessible from inside the VLAN. In order for a user to access the instances in their project, a special VPN instance (code named cloudpipe) needs to be created. Compute generates a certificate and key for the user to access the VPN and starts the VPN automatically. It provides a private network segment for each project's instances that can be accessed through a dedicated VPN connection from the Internet. In this mode, each project gets its own VLAN, Linux networking bridge, and subnet." +msgstr "" + +#: ./doc/admin-guide-cloud/ch_compute.xml:1058(para) +msgid "The subnets are specified by the network administrator, and are assigned dynamically to a project when required. A DHCP Server is started for each VLAN to pass out IP addresses to VM instances from the subnet assigned to the project. All instances belonging to one project are bridged into the same VLAN for that project. OpenStack Compute creates the Linux networking bridges and VLANs when required." +msgstr "" + +#: ./doc/admin-guide-cloud/ch_compute.xml:1069(title) +msgid "DHCP server: dnsmasq" +msgstr "" + +#: ./doc/admin-guide-cloud/ch_compute.xml:1070(para) +msgid "The Compute service uses dnsmasq as the DHCP server when running with either that Flat DHCP Network Manager or the VLAN Network Manager. The nova-network service is responsible for starting up dnsmasq processes." +msgstr "" + +#: ./doc/admin-guide-cloud/ch_compute.xml:1077(para) +msgid "The behavior of dnsmasq can be customized by creating a dnsmasq configuration file. Specify the config file using the dnsmasq_config_file configuration option. For example: See the OpenStack Configuration Reference for an example of how to change the behavior of dnsmasq using a dnsmasq configuration file. The dnsmasq documentation has a more comprehensive dnsmasq configuration file example." +msgstr "" + +#: ./doc/admin-guide-cloud/ch_compute.xml:1092(para) +msgid "Dnsmasq also acts as a caching DNS server for instances. You can explicitly specify the DNS server that dnsmasq should use by setting the dns_server configuration option in /etc/nova/nova.conf. The following example would configure dnsmasq to use Google's public DNS server: " +msgstr "" + +#: ./doc/admin-guide-cloud/ch_compute.xml:1100(para) +msgid "Dnsmasq logging output goes to the syslog (typically /var/log/syslog or /var/log/messages, depending on Linux distribution). The dnsmasq logging output can be useful for troubleshooting if VM instances boot successfully but are not reachable over the network." +msgstr "" + +#: ./doc/admin-guide-cloud/ch_compute.xml:1107(para) +msgid "A network administrator can run nova-manage fixed reserve --address=x.x.x.x to specify the starting point IP address (x.x.x.x) to reserve with the DHCP server. This reservation only affects which IP address the VMs start at, not the fixed IP addresses that the nova-network service places on the bridges." +msgstr "" + +#: ./doc/admin-guide-cloud/ch_compute.xml:1118(title) +msgid "Metadata service" +msgstr "" + +#: ./doc/admin-guide-cloud/ch_compute.xml:1120(title) +msgid "Introduction" +msgstr "" + +#: ./doc/admin-guide-cloud/ch_compute.xml:1121(para) +msgid "The Compute service uses a special metadata service to enable virtual machine instances to retrieve instance-specific data. Instances access the metadata service at http://169.254.169.254. The metadata service supports two sets of APIs: an OpenStack metadata API and an EC2-compatible API. Each of the APIs is versioned by date." +msgstr "" + +#: ./doc/admin-guide-cloud/ch_compute.xml:1129(para) +msgid "To retrieve a list of supported versions for the OpenStack metadata API, make a GET request to For example:" +msgstr "" + +#: ./doc/admin-guide-cloud/ch_compute.xml:1133(para) +msgid " To retrieve a list of supported versions for the EC2-compatible metadata API, make a GET request to " +msgstr "" + +#: ./doc/admin-guide-cloud/ch_compute.xml:1139(para) ./doc/admin-guide-cloud/ch_compute.xml:1163(para) ./doc/admin-guide-cloud/ch_compute.xml:1207(para) ./doc/admin-guide-cloud/ch_compute.xml:1235(para) ./doc/admin-guide-cloud/ch_compute.xml:1241(para) ./doc/admin-guide-cloud/ch_compute.xml:1450(para) ./doc/admin-guide-cloud/section_networking-config-identity.xml:47(para) ./doc/admin-guide-cloud/section_networking-config-identity.xml:61(para) ./doc/admin-guide-cloud/section_networking-use.xml:463(para) +msgid "For example:" +msgstr "" + +#: ./doc/admin-guide-cloud/ch_compute.xml:1151(para) +msgid "If you write a consumer for one of these APIs, always attempt to access the most recent API version supported by your consumer first, then fall back to an earlier version if the most recent one is not available." +msgstr "" + +#: ./doc/admin-guide-cloud/ch_compute.xml:1158(title) +msgid "OpenStack metadata API" +msgstr "" + +#: ./doc/admin-guide-cloud/ch_compute.xml:1159(para) +msgid "Metadata from the OpenStack API is distributed in JSON format. To retrieve the metadata, make a GET request to:" +msgstr "" + +#: ./doc/admin-guide-cloud/ch_compute.xml:1166(para) +msgid "Here is the same content after having run through a JSON pretty-printer:" +msgstr "" + +#: ./doc/admin-guide-cloud/ch_compute.xml:1182(para) +msgid "Instances also retrieve user data (passed as the user_data parameter in the API call or by the --user_data flag in the command) through the metadata service, by making a GET request to: For example:" +msgstr "" + +#: ./doc/admin-guide-cloud/ch_compute.xml:1196(title) +msgid "EC2 metadata API" +msgstr "" + +#: ./doc/admin-guide-cloud/ch_compute.xml:1197(para) +msgid "The metadata service has an API that is compatible with version 2009-04-04 of the Amazon EC2 metadata service; virtual machine images that are designed for EC2 work properly with OpenStack." +msgstr "" + +#: ./doc/admin-guide-cloud/ch_compute.xml:1203(para) +msgid "The EC2 API exposes a separate URL for each metadata. You can retrieve a listing of these elements by making a GET query to:" +msgstr "" + +#: ./doc/admin-guide-cloud/ch_compute.xml:1231(para) +msgid "Instances can retrieve the public SSH key (identified by keypair name when a user requests a new instance) by making a GET request to:" +msgstr "" + +#: ./doc/admin-guide-cloud/ch_compute.xml:1238(para) +msgid "Instances can retrieve user data by making a GET request to:" +msgstr "" + +#: ./doc/admin-guide-cloud/ch_compute.xml:1247(title) +msgid "Run the metadata service" +msgstr "" + +#: ./doc/admin-guide-cloud/ch_compute.xml:1248(para) +msgid "The metadata service is implemented by either the nova-api service or the nova-api-metadata service. (The nova-api-metadata service is generally only used when running in multi-host mode, see the OpenStack Configuration Reference for details). If you are running the nova-api service, you must have metadata as one of the elements of the list of the enabled_apis configuration option in /etc/nova/nova.conf. The default enabled_apis configuration setting includes the metadata service, so you should not need to modify it." +msgstr "" + +#: ./doc/admin-guide-cloud/ch_compute.xml:1271(para) +msgid "To enable instances to reach the metadata service, the nova-network service configures iptables to NAT port 80 of the 169.254.169.254 address to the IP address specified in (default $my_ip, which is the IP address of the nova-network service) and port specified in (default 8775) in /etc/nova/nova.conf." +msgstr "" + +#: ./doc/admin-guide-cloud/ch_compute.xml:1285(para) +msgid "The metadata_host configuration option must be an IP address, not a host name." +msgstr "" + +#: ./doc/admin-guide-cloud/ch_compute.xml:1290(para) +msgid "The default Compute service settings assume that the nova-network service and the nova-api service are running on the same host. If this is not the case, you must make this change in the /etc/nova/nova.conf file on the host running the nova-network service:" +msgstr "" + +#: ./doc/admin-guide-cloud/ch_compute.xml:1301(para) +msgid "Set the metadata_host configuration option to the IP address of the host where the nova-api service runs." +msgstr "" + +#: ./doc/admin-guide-cloud/ch_compute.xml:1312(title) +msgid "Enable ping and SSH on VMs" +msgstr "" + +#: ./doc/admin-guide-cloud/ch_compute.xml:1313(para) +msgid "Be sure you enable access to your VMs by using the or command. These commands enable you to and to your VMs:" +msgstr "" + +#: ./doc/admin-guide-cloud/ch_compute.xml:1319(para) +msgid "You must run these commands as root only if the credentials used to interact with nova-api are in /root/.bashrc. If the EC2 credentials are the .bashrc file for another user, you must run these commands as the user." +msgstr "" + +#: ./doc/admin-guide-cloud/ch_compute.xml:1327(para) +msgid "Run commands:" +msgstr "" + +#: ./doc/admin-guide-cloud/ch_compute.xml:1330(para) +msgid "Using euca2ools:" +msgstr "" + +#: ./doc/admin-guide-cloud/ch_compute.xml:1333(para) +msgid "If you still cannot ping or SSH your instances after issuing the commands, look at the number of dnsmasq processes that are running. If you have a running instance, check to see that TWO dnsmasq processes are running. If not, perform this as root:" +msgstr "" + +#: ./doc/admin-guide-cloud/ch_compute.xml:1344(title) +msgid "Configure public (floating) IP addresses" +msgstr "" + +#: ./doc/admin-guide-cloud/ch_compute.xml:1347(para) +msgid "This section describes how to configure floating IP addresses if you opt to use nova-network instead of neutron for OpenStack Networking. For instructions on how to configure neutron to provide access to instances through floating IP addresses, see ." +msgstr "" + +#: ./doc/admin-guide-cloud/ch_compute.xml:1357(title) +msgid "Private and public IP addresses" +msgstr "" + +#: ./doc/admin-guide-cloud/ch_compute.xml:1358(para) +msgid "Every virtual instance is automatically assigned a private IP address. You can optionally assign public IP addresses to instances. The term floating IP refers to an IP address, typically public, that you can dynamically add to a running virtual instance. OpenStack Compute uses Network Address Translation (NAT) to assign floating IPs to virtual instances." +msgstr "" + +#: ./doc/admin-guide-cloud/ch_compute.xml:1368(para) +msgid "If you plan to use this feature, you must add edit the /etc/nova/nova.conf file to specify to which interface the nova-network service binds public IP addresses, as follows:" +msgstr "" + +#: ./doc/admin-guide-cloud/ch_compute.xml:1374(replaceable) +msgid "vlan100" +msgstr "" + +#: ./doc/admin-guide-cloud/ch_compute.xml:1375(para) +msgid "If you make changes to the /etc/nova/nova.conf file while the nova-network service is running, you must restart the service." +msgstr "" + +#: ./doc/admin-guide-cloud/ch_compute.xml:1381(title) +msgid "Traffic between VMs using floating IPs" +msgstr "" + +#: ./doc/admin-guide-cloud/ch_compute.xml:1383(para) +msgid "Because floating IPs are implemented by using a source NAT (SNAT rule in iptables), security groups can show inconsistent behavior if VMs use their floating IP to communicate with other VMs, particularly on the same physical host. Traffic from VM to VM across the fixed network does not have this issue, and so this is the recommended path. To ensure that traffic does not get SNATed to the floating range, explicitly set . The x.x.x.x/y value specifies the range of floating IPs for each pool of floating IPs that you define. If the VMs in the source group have floating IPs, this configuration is also required." +msgstr "" + +#: ./doc/admin-guide-cloud/ch_compute.xml:1402(title) +msgid "Enable IP forwarding" +msgstr "" + +#: ./doc/admin-guide-cloud/ch_compute.xml:1403(para) +msgid "By default, IP forwarding is disabled on most Linux distributions. To use the floating IP feature, you must enable IP forwarding." +msgstr "" + +#: ./doc/admin-guide-cloud/ch_compute.xml:1407(para) +msgid "You must enable IP forwarding on only the nodes that run the nova-network service. If you use multi_host mode, make sure to enable it on all compute nodes. Otherwise, enable it on only the node that runs the nova-network service." +msgstr "" + +#: ./doc/admin-guide-cloud/ch_compute.xml:1416(para) +msgid "To check if the forwarding is enabled, run this command:" +msgstr "" + +#: ./doc/admin-guide-cloud/ch_compute.xml:1420(para) +msgid "Alternatively, you can run this command:" +msgstr "" + +#: ./doc/admin-guide-cloud/ch_compute.xml:1423(para) +msgid "In this example, IP forwarding is disabled. To enable it dynamically, run this command:" +msgstr "" + +#: ./doc/admin-guide-cloud/ch_compute.xml:1427(para) +msgid "Or:" +msgstr "" + +#: ./doc/admin-guide-cloud/ch_compute.xml:1429(para) +msgid "To make the changes permanent, edit the /etc/sysctl.conf file and update the IP forwarding setting:" +msgstr "" + +#: ./doc/admin-guide-cloud/ch_compute.xml:1433(para) +msgid "Save the file and run this command to apply the changes:" +msgstr "" + +#: ./doc/admin-guide-cloud/ch_compute.xml:1436(para) +msgid "You can also update the setting by restarting the network service." +msgstr "" + +#: ./doc/admin-guide-cloud/ch_compute.xml:1438(para) +msgid "For example, on Ubuntu, run this command:" +msgstr "" + +#: ./doc/admin-guide-cloud/ch_compute.xml:1440(para) +msgid "On RHEL/Fedora/CentOS, run this command:" +msgstr "" + +#: ./doc/admin-guide-cloud/ch_compute.xml:1444(title) +msgid "Create a list of available floating IP addresses" +msgstr "" + +#: ./doc/admin-guide-cloud/ch_compute.xml:1446(para) +msgid "Nova maintains a list of floating IP addresses that you can assign to instances. Use the command to add entries to this list." +msgstr "" + +#: ./doc/admin-guide-cloud/ch_compute.xml:1452(para) +msgid "You can use the following commands to perform floating IP operations:" +msgstr "" + +#: ./doc/admin-guide-cloud/ch_compute.xml:1458(para) +msgid "Lists the floating IP addresses in the pool." +msgstr "" + +#: ./doc/admin-guide-cloud/ch_compute.xml:1463(replaceable) +msgid "[pool name]" +msgstr "" + +#: ./doc/admin-guide-cloud/ch_compute.xml:1465(replaceable) ./doc/admin-guide-cloud/ch_compute.xml:1472(replaceable) +msgid "[CIDR]" +msgstr "" + +#: ./doc/admin-guide-cloud/ch_compute.xml:1467(para) +msgid "Creates specific floating IPs for either a single address or a subnet." +msgstr "" + +#: ./doc/admin-guide-cloud/ch_compute.xml:1473(para) +msgid "Removes floating IP addresses using the same parameters as the create command." +msgstr "" + +#: ./doc/admin-guide-cloud/ch_compute.xml:1478(para) +msgid "For information about how administrators can associate floating IPs with instances, see Manage IP addresses in the OpenStack Admin User Guide." +msgstr "" + +#: ./doc/admin-guide-cloud/ch_compute.xml:1486(title) +msgid "Automatically add floating IPs" +msgstr "" + +#: ./doc/admin-guide-cloud/ch_compute.xml:1487(para) +msgid "You can configure the nova-network service to automatically allocate and assign a floating IP address to virtual instances when they are launched. Add the following line to the /etc/nova/nova.conf file and restart the nova-network service:" +msgstr "" + +#: ./doc/admin-guide-cloud/ch_compute.xml:1497(para) +msgid "If you enable this option and all floating IP addresses have already been allocated, the command fails." +msgstr "" + +#: ./doc/admin-guide-cloud/ch_compute.xml:1505(title) +msgid "Remove a network from a project" +msgstr "" + +#: ./doc/admin-guide-cloud/ch_compute.xml:1506(para) +msgid "You cannot remove a network that has already been associated to a project by simply deleting it." +msgstr "" + +#: ./doc/admin-guide-cloud/ch_compute.xml:1508(para) +msgid "To determine the project ID you must have admin rights. You can disassociate the project from the network with a scrub command and the project ID as the final parameter:" +msgstr "" + +#: ./doc/admin-guide-cloud/ch_compute.xml:1512(replaceable) +msgid "<id>" +msgstr "" + +#: ./doc/admin-guide-cloud/ch_compute.xml:1515(title) +msgid "Multiple interfaces for your instances (multinic)" +msgstr "" + +#: ./doc/admin-guide-cloud/ch_compute.xml:1522(para) +msgid "SSL Configurations (VIPs)" +msgstr "" + +#: ./doc/admin-guide-cloud/ch_compute.xml:1525(para) +msgid "Services failover/ HA" +msgstr "" + +#: ./doc/admin-guide-cloud/ch_compute.xml:1528(para) +msgid "Bandwidth Allocation" +msgstr "" + +#: ./doc/admin-guide-cloud/ch_compute.xml:1531(para) +msgid "Administrative/ Public access to your instances" +msgstr "" + +#: ./doc/admin-guide-cloud/ch_compute.xml:1538(title) +msgid "multinic flat manager" +msgstr "" + +#: ./doc/admin-guide-cloud/ch_compute.xml:1548(title) +msgid "multinic flatdhcp manager" +msgstr "" + +#: ./doc/admin-guide-cloud/ch_compute.xml:1558(title) +msgid "multinic VLAN manager" +msgstr "" + +#: ./doc/admin-guide-cloud/ch_compute.xml:1518(para) +msgid "The multi-nic feature allows you to plug more than one interface to your instances, making it possible to make several use cases available: Each VIF is representative of a separate network with its own IP block. Every network mode introduces it's own set of changes regarding the mulitnic usage: " +msgstr "" + +#: ./doc/admin-guide-cloud/ch_compute.xml:1569(title) +msgid "Use the multinic feature" +msgstr "" + +#: ./doc/admin-guide-cloud/ch_compute.xml:1570(para) +msgid "In order to use the multinic feature, first create two networks, and attach them to your project: Now every time you spawn a new instance, it gets two IP addresses from the respective DHCP servers:" +msgstr "" + +#: ./doc/admin-guide-cloud/ch_compute.xml:1585(para) +msgid "Make sure to power up the second interface on the instance, otherwise that last won't be reachable through its second IP. Here is an example of how to setup the interfaces within the instance (this is the configuration that needs to be applied inside the image):" +msgstr "" + +#: ./doc/admin-guide-cloud/ch_compute.xml:1591(filename) +msgid "/etc/network/interfaces" +msgstr "" + +#: ./doc/admin-guide-cloud/ch_compute.xml:1603(para) +msgid "If the Virtual Network Service Neutron is installed, it is possible to specify the networks to attach to the respective interfaces by using the --nic flag when invoking the nova command: " +msgstr "" + +#: ./doc/admin-guide-cloud/ch_compute.xml:1615(title) +msgid "Troubleshoot Networking" +msgstr "" + +#: ./doc/admin-guide-cloud/ch_compute.xml:1617(title) +msgid "Cannot reach floating IPs" +msgstr "" + +#: ./doc/admin-guide-cloud/ch_compute.xml:1618(para) +msgid "If you cannot reach your instances through the floating IP address, make sure the default security group allows ICMP (ping) and SSH (port 22), so that you can reach the instances:" +msgstr "" + +#: ./doc/admin-guide-cloud/ch_compute.xml:1629(para) +msgid "Ensure the NAT rules have been added to iptables on the node that nova-network is running on, as root:" +msgstr "" + +#: ./doc/admin-guide-cloud/ch_compute.xml:1637(para) +msgid "Check that the public address, in this example \"68.99.26.170\", has been added to your public interface: You should see the address in the listing when you enter \"ip addr\" at the command prompt." +msgstr "" + +#: ./doc/admin-guide-cloud/ch_compute.xml:1649(para) +msgid "Note that you cannot SSH to an instance with a public IP from within the same server as the routing configuration won't allow it." +msgstr "" + +#: ./doc/admin-guide-cloud/ch_compute.xml:1652(para) +msgid "You can use to identify if packets are being routed to the inbound interface on the compute host. If the packets are reaching the compute hosts but the connection is failing, the issue may be that the packet is being dropped by reverse path filtering. Try disabling reverse path filtering on the inbound interface. For example, if the inbound interface is eth2, as root:" +msgstr "" + +#: ./doc/admin-guide-cloud/ch_compute.xml:1662(replaceable) +msgid "eth2" +msgstr "" + +#: ./doc/admin-guide-cloud/ch_compute.xml:1663(para) +msgid "If this solves your issue, add this line to /etc/sysctl.conf so that the reverse path filter is disabled the next time the compute host reboots: " +msgstr "" + +#: ./doc/admin-guide-cloud/ch_compute.xml:1670(title) +msgid "Disable firewall" +msgstr "" + +#: ./doc/admin-guide-cloud/ch_compute.xml:1671(para) +msgid "To help debug networking issues with reaching VMs, you can disable the firewall by setting the following option in /etc/nova/nova.conf:" +msgstr "" + +#: ./doc/admin-guide-cloud/ch_compute.xml:1676(para) +msgid "We strongly recommend you remove this line to re-enable the firewall once your networking issues have been resolved." +msgstr "" + +#: ./doc/admin-guide-cloud/ch_compute.xml:1681(title) +msgid "Packet loss from instances to nova-network server (VLANManager mode)" +msgstr "" + +#: ./doc/admin-guide-cloud/ch_compute.xml:1683(para) +msgid "If you can SSH to your instances but you find that the network interactions to your instance is slow, or if you find that running certain operations are slower than they should be (for example, ), then there may be packet loss occurring on the connection to the instance." +msgstr "" + +#: ./doc/admin-guide-cloud/ch_compute.xml:1690(para) +msgid "Packet loss can be caused by Linux networking configuration settings related to bridges. Certain settings can cause packets to be dropped between the VLAN interface (for example, vlan100) and the associated bridge interface (for example, br100) on the host running the nova-network service." +msgstr "" + +#: ./doc/admin-guide-cloud/ch_compute.xml:1699(para) +msgid "One way to check if this is the issue in your setup is to open up three terminals and run the following commands:" +msgstr "" + +#: ./doc/admin-guide-cloud/ch_compute.xml:1702(para) +msgid "In the first terminal, on the host running nova-network, use to monitor DNS-related traffic (UDP, port 53) on the VLAN interface. As root:" +msgstr "" + +#: ./doc/admin-guide-cloud/ch_compute.xml:1707(para) +msgid "In the second terminal, also on the host running nova-network, use to monitor DNS-related traffic on the bridge interface. As root:" +msgstr "" + +#: ./doc/admin-guide-cloud/ch_compute.xml:1712(para) +msgid "In the third terminal, SSH inside of the instance and generate DNS requests by using the command:" +msgstr "" + +#: ./doc/admin-guide-cloud/ch_compute.xml:1716(para) +msgid "The symptoms may be intermittent, so try running multiple times. If the network configuration is correct, the command should return immediately each time. If it is not functioning properly, the command hangs for several seconds." +msgstr "" + +#: ./doc/admin-guide-cloud/ch_compute.xml:1722(para) +msgid "If the command sometimes hangs, and there are packets that appear in the first terminal but not the second, then the problem may be due to filtering done on the bridges. Try to disable filtering, as root:" +msgstr "" + +#: ./doc/admin-guide-cloud/ch_compute.xml:1730(para) +msgid "If this solves your issue, add this line to /etc/sysctl.conf so that these changes take effect the next time the host reboots:" +msgstr "" + +#: ./doc/admin-guide-cloud/ch_compute.xml:1739(title) +msgid "KVM: Network connectivity works initially, then fails" +msgstr "" + +#: ./doc/admin-guide-cloud/ch_compute.xml:1741(para) +msgid "Some administrators have observed an issue with the KVM hypervisor where instances running Ubuntu 12.04 sometimes loses network connectivity after functioning properly for a period of time. Some users have reported success with loading the vhost_net kernel module as a workaround for this issue (see bug #997978) . This kernel module may also improve network performance on KVM. To load the kernel module, as root:" +msgstr "" + +#: ./doc/admin-guide-cloud/ch_compute.xml:1756(para) +msgid "Loading the module has no effect on running instances." +msgstr "" + +#: ./doc/admin-guide-cloud/ch_compute.xml:1763(title) +msgid "Volumes" +msgstr "" + +#: ./doc/admin-guide-cloud/ch_compute.xml:1764(para) +msgid "The Block Storage Service provides persistent block storage resources that OpenStack Compute instances can consume." +msgstr "" + +#: ./doc/admin-guide-cloud/ch_compute.xml:1767(para) +msgid "See the OpenStack Configuration Reference for information about configuring volume drivers and creating and attaching volumes to server instances." +msgstr "" + +#: ./doc/admin-guide-cloud/ch_compute.xml:1773(title) +msgid "System administration" +msgstr "" + +#: ./doc/admin-guide-cloud/ch_compute.xml:1774(para) +msgid "By understanding how the different installed nodes interact with each other you can administer the Compute installation. Compute offers many ways to install using multiple servers but the general idea is that you can have multiple compute nodes that control the virtual servers and a cloud controller node that contains the remaining Compute services." +msgstr "" + +#: ./doc/admin-guide-cloud/ch_compute.xml:1781(para) +msgid "The Compute cloud works through the interaction of a series of daemon processes named nova-* that reside persistently on the host machine or machines. These binaries can all run on the same machine or be spread out on multiple boxes in a large deployment. The responsibilities of Services, Managers, and Drivers, can be a bit confusing at first. Here is an outline the division of responsibilities to make understanding the system a little bit easier." +msgstr "" + +#: ./doc/admin-guide-cloud/ch_compute.xml:1790(para) +msgid "Currently, Services are nova-api, nova-objectstore (which can be replaced with Glance, the OpenStack Image Service), nova-compute, and nova-network. Managers and Drivers are specified by configuration options and loaded using utils.load_object(). Managers are responsible for a certain aspect of the system. It is a logical grouping of code relating to a portion of the system. In general other components should be using the manager to make changes to the components that it is responsible for." +msgstr "" + +#: ./doc/admin-guide-cloud/ch_compute.xml:1805(para) +msgid "nova-api. Receives xml requests and sends them to the rest of the system. It is a wsgi app that routes and authenticate requests. It supports the EC2 and OpenStack APIs. There is a nova-api.conf file created when you install Compute." +msgstr "" + +#: ./doc/admin-guide-cloud/ch_compute.xml:1814(para) +msgid "nova-objectstore: The nova-objectstore service is an ultra simple file-based storage system for images that replicates most of the S3 API. It can be replaced with OpenStack Image Service and a simple image manager or use OpenStack Object Storage as the virtual machine image storage facility. It must reside on the same node as nova-compute." +msgstr "" + +#: ./doc/admin-guide-cloud/ch_compute.xml:1828(para) +msgid "nova-compute. Responsible for managing virtual machines. It loads a Service object which exposes the public methods on ComputeManager through Remote Procedure Call (RPC)." +msgstr "" + +#: ./doc/admin-guide-cloud/ch_compute.xml:1836(para) +msgid "nova-network. Responsible for managing floating and fixed IPs, DHCP, bridging and VLANs. It loads a Service object which exposes the public methods on one of the subclasses of NetworkManager. Different networking strategies are available to the service by changing the network_manager configuration option to FlatManager, FlatDHCPManager, or VlanManager (default is VLAN if no other is specified)." +msgstr "" + +#: ./doc/admin-guide-cloud/ch_compute.xml:1849(title) +msgid "Compute service architecture" +msgstr "" + +#: ./doc/admin-guide-cloud/ch_compute.xml:1850(para) +msgid "These basic categories describe the service architecture and what's going on within the cloud controller." +msgstr "" + +#: ./doc/admin-guide-cloud/ch_compute.xml:1854(title) +msgid "API server" +msgstr "" + +#: ./doc/admin-guide-cloud/ch_compute.xml:1855(para) +msgid "At the heart of the cloud framework is an API server. This API server makes command and control of the hypervisor, storage, and networking programmatically available to users in realization of the definition of cloud computing." +msgstr "" + +#: ./doc/admin-guide-cloud/ch_compute.xml:1860(para) +msgid "The API endpoints are basic HTTP web services which handle authentication, authorization, and basic command and control functions using various API interfaces under the Amazon, Rackspace, and related models. This enables API compatibility with multiple existing tool sets created for interaction with offerings from other vendors. This broad compatibility prevents vendor lock-in." +msgstr "" + +#: ./doc/admin-guide-cloud/ch_compute.xml:1871(title) +msgid "Message queue" +msgstr "" + +#: ./doc/admin-guide-cloud/ch_compute.xml:1872(para) +msgid "A messaging queue brokers the interaction between compute nodes (processing), the networking controllers (software which controls network infrastructure), API endpoints, the scheduler (determines which physical hardware to allocate to a virtual resource), and similar components. Communication to and from the cloud controller is by HTTP requests through multiple API endpoints." +msgstr "" + +#: ./doc/admin-guide-cloud/ch_compute.xml:1881(para) +msgid "A typical message passing event begins with the API server receiving a request from a user. The API server authenticates the user and ensures that the user is permitted to issue the subject command. Availability of objects implicated in the request is evaluated and, if available, the request is routed to the queuing engine for the relevant workers. Workers continually listen to the queue based on their role, and occasionally their type host name. When such listening produces a work request, the worker takes assignment of the task and begins its execution. Upon completion, a response is dispatched to the queue which is received by the API server and relayed to the originating user. Database entries are queried, added, or removed as necessary throughout the process." +msgstr "" + +#: ./doc/admin-guide-cloud/ch_compute.xml:1900(title) +msgid "Compute worker" +msgstr "" + +#: ./doc/admin-guide-cloud/ch_compute.xml:1901(para) +msgid "Compute workers manage computing instances on host machines. The API dispatches commands to compute workers to complete these tasks:" +msgstr "" + +#: ./doc/admin-guide-cloud/ch_compute.xml:1906(para) +msgid "Run instances" +msgstr "" + +#: ./doc/admin-guide-cloud/ch_compute.xml:1909(para) +msgid "Terminate instances" +msgstr "" + +#: ./doc/admin-guide-cloud/ch_compute.xml:1912(para) +msgid "Reboot instances" +msgstr "" + +#: ./doc/admin-guide-cloud/ch_compute.xml:1915(para) +msgid "Attach volumes" +msgstr "" + +#: ./doc/admin-guide-cloud/ch_compute.xml:1918(para) +msgid "Detach volumes" +msgstr "" + +#: ./doc/admin-guide-cloud/ch_compute.xml:1921(para) +msgid "Get console output" +msgstr "" + +#: ./doc/admin-guide-cloud/ch_compute.xml:1926(title) +msgid "Network Controller" +msgstr "" + +#: ./doc/admin-guide-cloud/ch_compute.xml:1927(para) +msgid "The Network Controller manages the networking resources on host machines. The API server dispatches commands through the message queue, which are subsequently processed by Network Controllers. Specific operations include:" +msgstr "" + +#: ./doc/admin-guide-cloud/ch_compute.xml:1934(para) +msgid "Allocate fixed IP addresses" +msgstr "" + +#: ./doc/admin-guide-cloud/ch_compute.xml:1937(para) +msgid "Configuring VLANs for projects" +msgstr "" + +#: ./doc/admin-guide-cloud/ch_compute.xml:1940(para) +msgid "Configuring networks for compute nodes" +msgstr "" + +#: ./doc/admin-guide-cloud/ch_compute.xml:1947(title) +msgid "Manage Compute users" +msgstr "" + +#: ./doc/admin-guide-cloud/ch_compute.xml:1948(para) +msgid "Access to the Euca2ools (ec2) API is controlled by an access and secret key. The user’s access key needs to be included in the request, and the request must be signed with the secret key. Upon receipt of API requests, Compute verifies the signature and runs commands on behalf of the user." +msgstr "" + +#: ./doc/admin-guide-cloud/ch_compute.xml:1954(para) +msgid "To begin using Compute, you must create a user with the Identity Service." +msgstr "" + +#: ./doc/admin-guide-cloud/ch_compute.xml:1958(title) +msgid "Manage the cloud" +msgstr "" + +#: ./doc/admin-guide-cloud/ch_compute.xml:1959(para) +msgid "A system administrator can use these tools to manage a cloud; the nova client, the command, and the commands." +msgstr "" + +#: ./doc/admin-guide-cloud/ch_compute.xml:1963(para) +msgid "The command can only be run by cloud administrators. Both nova client and euca2ools can be used by all users, though specific commands might be restricted by Role Based Access Control in the Identity Service." +msgstr "" + +#: ./doc/admin-guide-cloud/ch_compute.xml:1969(title) +msgid "To use the nova command-line tool" +msgstr "" + +#: ./doc/admin-guide-cloud/ch_compute.xml:1971(para) +msgid "Installing the python-novaclient gives you a nova shell command that enables Compute API interactions from the command line. You install the client, and then provide your user name and password, set as environment variables for convenience, and then you can have the ability to send commands to your cloud on the command-line." +msgstr "" + +#: ./doc/admin-guide-cloud/ch_compute.xml:1979(para) +msgid "To install python-novaclient, download the tarball from http://pypi.python.org/pypi/python-novaclient/2.6.3#downloads and then install it in your favorite python environment." +msgstr "" + +#: ./doc/admin-guide-cloud/ch_compute.xml:1991(para) +msgid "Now that you have installed the python-novaclient, confirm the installation by entering:" +msgstr "" + +#: ./doc/admin-guide-cloud/ch_compute.xml:2002(para) +msgid "This command returns a list of nova commands and parameters. Set the required parameters as environment variables to make running commands easier. You can add --os-username, for example, on the nova command, or set it as environment variables:" +msgstr "" + +#: ./doc/admin-guide-cloud/ch_compute.xml:2014(para) +msgid "Using the Identity Service, you are supplied with an authentication endpoint, which nova recognizes as the OS_AUTH_URL." +msgstr "" + +#: ./doc/admin-guide-cloud/ch_compute.xml:2025(title) +msgid "To use the nova-manage command" +msgstr "" + +#: ./doc/admin-guide-cloud/ch_compute.xml:2026(para) +msgid "The nova-manage command may be used to perform many essential functions for administration and ongoing maintenance of nova, such as network creation or user manipulation." +msgstr "" + +#: ./doc/admin-guide-cloud/ch_compute.xml:2031(para) +msgid "The man page for nova-manage has a good explanation for each of its functions, and is recommended reading for those starting out. Access it by running:" +msgstr "" + +#: ./doc/admin-guide-cloud/ch_compute.xml:2038(para) +msgid "For administrators, the standard pattern for executing a nova-manage command is:" +msgstr "" + +#: ./doc/admin-guide-cloud/ch_compute.xml:2040(replaceable) +msgid "[args]" +msgstr "" + +#: ./doc/admin-guide-cloud/ch_compute.xml:2043(para) +msgid "For example, to obtain a list of all projects:" +msgstr "" + +#: ./doc/admin-guide-cloud/ch_compute.xml:2048(para) +msgid "Run without arguments to see a list of available command categories:" +msgstr "" + +#: ./doc/admin-guide-cloud/ch_compute.xml:2053(para) +msgid "You can also run with a category argument such as user to see a list of all commands in that category:" +msgstr "" + +#: ./doc/admin-guide-cloud/ch_compute.xml:2060(title) +msgid "Use the euca2ools commands" +msgstr "" + +#: ./doc/admin-guide-cloud/ch_compute.xml:2061(para) +msgid "For a command-line interface to EC2 API calls, use the euca2ools command line tool. See http://open.eucalyptus.com/wiki/Euca2oolsGuide_v1.3" +msgstr "" + +#: ./doc/admin-guide-cloud/ch_compute.xml:2070(title) +msgid "Manage logs" +msgstr "" + +#: ./doc/admin-guide-cloud/ch_compute.xml:2072(title) +msgid "Logging module" +msgstr "" + +#: ./doc/admin-guide-cloud/ch_compute.xml:2073(para) +msgid "Add this line to the /etc/nova/nova.conf file to specify a configuration file to change the logging behavior. To change the logging level, such as DEBUG, INFO, WARNING, ERROR): " +msgstr "" + +#: ./doc/admin-guide-cloud/ch_compute.xml:2082(para) +msgid "The log config file is an ini-style config file which must contain a section called logger_nova, which controls the behavior of the logging facility in the nova-* services. The file must contain a section called logger_nova, for example:" +msgstr "" + +#: ./doc/admin-guide-cloud/ch_compute.xml:2093(para) +msgid "This example sets the debugging level to INFO (which less verbose than the default DEBUG setting). See the Python documentation on logging configuration file format for more details on this file, including the meaning of the handlers and quaname variables. See etc/nova/logging_sample.conf in the openstack/nova repository on GitHub for an example logging.conf file with various handlers defined." +msgstr "" + +#: ./doc/admin-guide-cloud/ch_compute.xml:2111(title) +msgid "Syslog" +msgstr "" + +#: ./doc/admin-guide-cloud/ch_compute.xml:2112(para) +msgid "You can configure OpenStack Compute services to send logging information to syslog. This is useful if you want to use rsyslog, which forwards the logs to a remote machine. You need to separately configure the Compute service (Nova), the Identity Service (Keystone), the Image Service (Glance), and, if you are using it, the Block Storage Service (Cinder) to send log messages to syslog. To do so, add these lines to:" +msgstr "" + +#: ./doc/admin-guide-cloud/ch_compute.xml:2123(filename) +msgid "/etc/nova/nova.conf" +msgstr "" + +#: ./doc/admin-guide-cloud/ch_compute.xml:2126(filename) +msgid "/etc/keystone/keystone.conf" +msgstr "" + +#: ./doc/admin-guide-cloud/ch_compute.xml:2129(filename) +msgid "/etc/glance/glance-api.conf" +msgstr "" + +#: ./doc/admin-guide-cloud/ch_compute.xml:2132(filename) +msgid "/etc/glance/glance-registry.conf" +msgstr "" + +#: ./doc/admin-guide-cloud/ch_compute.xml:2135(filename) +msgid "/etc/cinder/cinder.conf" +msgstr "" + +#: ./doc/admin-guide-cloud/ch_compute.xml:2145(para) +msgid "While the example above uses the same local facility for each service (LOG_LOCAL0, which corresponds to syslog facility LOCAL0), we recommend that you configure a separate local facility for each service, as this provides better isolation and more flexibility. For example, you may want to capture logging info at different severity levels for different services. Syslog allows you to define up to seven local facilities, LOCAL0, LOCAL1, ..., LOCAL7. See the syslog documentation for more details." +msgstr "" + +#: ./doc/admin-guide-cloud/ch_compute.xml:2142(para) +msgid "In addition to enabling syslog, these settings also turn off more verbose output and debugging output from the log." +msgstr "" + +#: ./doc/admin-guide-cloud/ch_compute.xml:2163(title) +msgid "Rsyslog" +msgstr "" + +#: ./doc/admin-guide-cloud/ch_compute.xml:2164(para) +msgid "Rsyslog is a useful tool for setting up a centralized log server across multiple machines. We briefly describe the configuration to set up an rsyslog server; a full treatment of rsyslog is beyond the scope of this document. We assume rsyslog has already been installed on your hosts, which is the default on most Linux distributions." +msgstr "" + +#: ./doc/admin-guide-cloud/ch_compute.xml:2172(para) +msgid "This example shows a minimal configuration for /etc/rsyslog.conf on the log server host, which receives the log files:" +msgstr "" + +#: ./doc/admin-guide-cloud/ch_compute.xml:2184(replaceable) +msgid "compute-01" +msgstr "" + +#: ./doc/admin-guide-cloud/ch_compute.xml:2179(para) +msgid "Add to /etc/rsyslog.conf a filter rule on which looks for a host name. The example below use compute-01 as an example of a compute host name:" +msgstr "" + +#: ./doc/admin-guide-cloud/ch_compute.xml:2185(para) +msgid "On the compute hosts, create a file named /etc/rsyslog.d/60-nova.conf, with this content." +msgstr "" + +#: ./doc/admin-guide-cloud/ch_compute.xml:2192(para) +msgid "Once you have created this file, restart your rsyslog daemon. Error-level log messages on the compute hosts should now be sent to your log server." +msgstr "" + +#: ./doc/admin-guide-cloud/ch_compute.xml:2200(title) +msgid "Migration" +msgstr "" + +#: ./doc/admin-guide-cloud/ch_compute.xml:2201(para) +msgid "Before starting migrations, review the Configure migrations section in OpenStack Configuration Reference." +msgstr "" + +#: ./doc/admin-guide-cloud/ch_compute.xml:2206(para) +msgid "Migration provides a scheme to migrate running instances from one OpenStack Compute server to another OpenStack Compute server." +msgstr "" + +#: ./doc/admin-guide-cloud/ch_compute.xml:2210(title) +msgid "To migrate instances" +msgstr "" + +#: ./doc/admin-guide-cloud/ch_compute.xml:2212(para) +msgid "Look at the running instances, to get the ID of the instance you wish to migrate." +msgstr "" + +#: ./doc/admin-guide-cloud/ch_compute.xml:2223(para) +msgid "Look at information associated with that instance - our example is vm1 from above." +msgstr "" + +#: ./doc/admin-guide-cloud/ch_compute.xml:2240(para) +msgid "In this example, vm1 is running on HostB." +msgstr "" + +#: ./doc/admin-guide-cloud/ch_compute.xml:2244(para) +msgid "Select the server to migrate instances to." +msgstr "" + +#: ./doc/admin-guide-cloud/ch_compute.xml:2251(para) +msgid "In this example, HostC can be picked up because nova-compute is running on it." +msgstr "" + +#: ./doc/admin-guide-cloud/ch_compute.xml:2257(para) +msgid "Ensure that HostC has enough resource for migration." +msgstr "" + +#: ./doc/admin-guide-cloud/ch_compute.xml:2269(para) +msgid "cpu:the number of cpu" +msgstr "" + +#: ./doc/admin-guide-cloud/ch_compute.xml:2274(para) +msgid "mem(mb):total amount of memory (MB)" +msgstr "" + +#: ./doc/admin-guide-cloud/ch_compute.xml:2279(para) +msgid "hdd:total amount of space for NOVA-INST-DIR/instances (GB)" +msgstr "" + +#: ./doc/admin-guide-cloud/ch_compute.xml:2285(para) +msgid "1st line shows total amount of resource physical server has." +msgstr "" + +#: ./doc/admin-guide-cloud/ch_compute.xml:2290(para) +msgid "2nd line shows current used resource." +msgstr "" + +#: ./doc/admin-guide-cloud/ch_compute.xml:2295(para) +msgid "3rd line shows maximum used resource." +msgstr "" + +#: ./doc/admin-guide-cloud/ch_compute.xml:2300(para) +msgid "4th line and under shows the resource for each project." +msgstr "" + +#: ./doc/admin-guide-cloud/ch_compute.xml:2307(para) +msgid "Use the command to migrate the instances." +msgstr "" + +#: ./doc/admin-guide-cloud/ch_compute.xml:2320(para) +msgid "While the nova command is called , under the default Compute configuration options the instances are suspended before migration." +msgstr "" + +#: ./doc/admin-guide-cloud/ch_compute.xml:2325(para) +msgid "See Configure migrations in OpenStack Configuration Reference for more details." +msgstr "" + +#: ./doc/admin-guide-cloud/ch_compute.xml:2311(para) +msgid "Make sure instances are migrated successfully with . If instances are still running on HostB, check log files (src/dest nova-compute and nova-scheduler) to determine why. " +msgstr "" + +#: ./doc/admin-guide-cloud/ch_compute.xml:2337(title) +msgid "Recover from a failed compute node" +msgstr "" + +#: ./doc/admin-guide-cloud/ch_compute.xml:2338(para) +msgid "If you have deployed Compute with a shared file system, you can quickly recover from a failed compute node. Of the two methods covered in these sections, the evacuate API is the preferred method even in the absence of shared storage. The evacuate API provides many benefits over manual recovery, such as re-attachment of volumes and floating IPs." +msgstr "" + +#: ./doc/admin-guide-cloud/ch_compute.xml:2347(title) +msgid "Manual recovery" +msgstr "" + +#: ./doc/admin-guide-cloud/ch_compute.xml:2348(para) +msgid "For KVM/libvirt compute node recovery, see the previous section. Use this procedure for other hypervisors." +msgstr "" + +#: ./doc/admin-guide-cloud/ch_compute.xml:2352(title) +msgid "To work with host information" +msgstr "" + +#: ./doc/admin-guide-cloud/ch_compute.xml:2354(para) +msgid "Identify the vms on the affected hosts, using tools such as a combination of nova list and nova show or euca-describe-instances. Here's an example using the EC2 API - instance i-000015b9 that is running on node np-rcc54:" +msgstr "" + +#: ./doc/admin-guide-cloud/ch_compute.xml:2365(para) +msgid "You can review the status of the host by using the nova database. Some of the important information is highlighted below. This example converts an EC2 API instance ID into an OpenStack ID - if you used the nova commands, you can substitute the ID directly. You can find the credentials for your database in /etc/nova.conf." +msgstr "" + +#: ./doc/admin-guide-cloud/ch_compute.xml:2396(title) +msgid "To recover the VM" +msgstr "" + +#: ./doc/admin-guide-cloud/ch_compute.xml:2398(para) +msgid "Armed with the information of VMs on the failed host, determine to which compute host the affected VMs should move. Run the following database command to move the VM to np-rcc46:" +msgstr "" + +#: ./doc/admin-guide-cloud/ch_compute.xml:2406(para) +msgid "Next, if using a hypervisor that relies on libvirt (such as KVM) it is a good idea to update the libvirt.xml file (found in /var/lib/nova/instances/[instance ID]). The important changes to make are to change the DHCPSERVER value to the host ip address of the Compute host that is the VMs new home, and update the VNC IP if it isn't already 0.0.0.0." +msgstr "" + +#: ./doc/admin-guide-cloud/ch_compute.xml:2421(para) +msgid "Next, reboot the VM:" +msgstr "" + +#: ./doc/admin-guide-cloud/ch_compute.xml:2425(para) +msgid "In theory, the above database update and nova reboot command are all that is required to recover the VMs from a failed host. However, if further problems occur, consider looking at recreating the network filter configuration using virsh, restarting the Compute services or updating the vm_state and power_state in the Compute database." +msgstr "" + +#: ./doc/admin-guide-cloud/ch_compute.xml:2442(title) +msgid "Recover from a UID/GID mismatch" +msgstr "" + +#: ./doc/admin-guide-cloud/ch_compute.xml:2443(para) +msgid "When running OpenStack compute, using a shared file system or an automated configuration tool, you could encounter a situation where some files on your compute node are using the wrong UID or GID. This causes a raft of errors, such as being unable to live migrate, or start virtual machines." +msgstr "" + +#: ./doc/admin-guide-cloud/ch_compute.xml:2449(para) +msgid "This basic procedure runs on nova-compute hosts, based on the KVM hypervisor, that could help to restore the situation:" +msgstr "" + +#: ./doc/admin-guide-cloud/ch_compute.xml:2454(title) +msgid "To recover from a UID/GID mismatch" +msgstr "" + +#: ./doc/admin-guide-cloud/ch_compute.xml:2456(para) +msgid "Make sure you don't use numbers that are already used for some other user/group." +msgstr "" + +#: ./doc/admin-guide-cloud/ch_compute.xml:2460(para) +msgid "Set the nova uid in /etc/passwd to the same number in all hosts (for example, 112)." +msgstr "" + +#: ./doc/admin-guide-cloud/ch_compute.xml:2466(para) +msgid "Set the libvirt-qemu uid in /etc/passwd to the same number in all hosts (for example, 119)." +msgstr "" + +#: ./doc/admin-guide-cloud/ch_compute.xml:2472(para) +msgid "Set the nova group in /etc/group file to the same number in all hosts (for example, 120)." +msgstr "" + +#: ./doc/admin-guide-cloud/ch_compute.xml:2478(para) +msgid "Set the libvirtd group in /etc/group file to the same number in all hosts (for example, 119)." +msgstr "" + +#: ./doc/admin-guide-cloud/ch_compute.xml:2484(para) +msgid "Stop the services on the compute node." +msgstr "" + +#: ./doc/admin-guide-cloud/ch_compute.xml:2488(para) +msgid "Change all the files owned by user nova or by group nova. For example:" +msgstr "" + +#: ./doc/admin-guide-cloud/ch_compute.xml:2494(para) +msgid "Repeat the steps for the libvirt-qemu owned files if those were needed to change." +msgstr "" + +#: ./doc/admin-guide-cloud/ch_compute.xml:2498(para) +msgid "Restart the services." +msgstr "" + +#: ./doc/admin-guide-cloud/ch_compute.xml:2501(para) +msgid "Now you can run the command to verify that all files using the correct identifiers." +msgstr "" + +#: ./doc/admin-guide-cloud/ch_compute.xml:2508(title) +msgid "Compute disaster recovery process" +msgstr "" + +#: ./doc/admin-guide-cloud/ch_compute.xml:2509(para) +msgid "In this section describes how to manage your cloud after a disaster, and how to easily back up the persistent storage volumes. Backups are mandatory, even outside of disaster scenarios." +msgstr "" + +#: ./doc/admin-guide-cloud/ch_compute.xml:2514(para) +msgid "For reference, you can find a DRP definition at http://en.wikipedia.org/wiki/Disaster_Recovery_Plan." +msgstr "" + +#: ./doc/admin-guide-cloud/ch_compute.xml:2519(title) +msgid "A- The disaster recovery process presentation" +msgstr "" + +#: ./doc/admin-guide-cloud/ch_compute.xml:2521(para) +msgid "A disaster could happen to several components of your architecture: a disk crash, a network loss, a power cut, and so on. In this example, assume the following set up:" +msgstr "" + +#: ./doc/admin-guide-cloud/ch_compute.xml:2527(para) +msgid "A cloud controller (nova-api, nova-objecstore, nova-network)" +msgstr "" + +#: ./doc/admin-guide-cloud/ch_compute.xml:2531(para) +msgid "A compute node (nova-compute)" +msgstr "" + +#: ./doc/admin-guide-cloud/ch_compute.xml:2536(para) +msgid "A Storage Area Network used by cinder-volumes (aka SAN)" +msgstr "" + +#: ./doc/admin-guide-cloud/ch_compute.xml:2542(para) +msgid "The disaster example is the worst one: a power loss. That power loss applies to the three components. Let's see what runs and how it runs before the crash:" +msgstr "" + +#: ./doc/admin-guide-cloud/ch_compute.xml:2549(para) +msgid "From the SAN to the cloud controller, we have an active iscsi session (used for the \"cinder-volumes\" LVM's VG)." +msgstr "" + +#: ./doc/admin-guide-cloud/ch_compute.xml:2554(para) +msgid "From the cloud controller to the compute node we also have active iscsi sessions (managed by cinder-volume)." +msgstr "" + +#: ./doc/admin-guide-cloud/ch_compute.xml:2560(para) +msgid "For every volume an iscsi session is made (so 14 ebs volumes equals 14 sessions)." +msgstr "" + +#: ./doc/admin-guide-cloud/ch_compute.xml:2565(para) +msgid "From the cloud controller to the compute node, we also have iptables/ ebtables rules which allows the access from the cloud controller to the running instance." +msgstr "" + +#: ./doc/admin-guide-cloud/ch_compute.xml:2572(para) +msgid "And at least, from the cloud controller to the compute node ; saved into database, the current state of the instances (in that case \"running\" ), and their volumes attachment (mount point, volume id, volume status, and so on.)" +msgstr "" + +#: ./doc/admin-guide-cloud/ch_compute.xml:2580(para) +msgid "Now, after the power loss occurs and all hardware components restart, the situation is as follows:" +msgstr "" + +#: ./doc/admin-guide-cloud/ch_compute.xml:2585(para) +msgid "From the SAN to the cloud, the ISCSI session no longer exists." +msgstr "" + +#: ./doc/admin-guide-cloud/ch_compute.xml:2589(para) +msgid "From the cloud controller to the compute node, the ISCSI sessions no longer exist." +msgstr "" + +#: ./doc/admin-guide-cloud/ch_compute.xml:2594(para) +msgid "From the cloud controller to the compute node, the iptables and ebtables are recreated, since, at boot, nova-network reapply the configurations." +msgstr "" + +#: ./doc/admin-guide-cloud/ch_compute.xml:2600(para) +msgid "From the cloud controller, instances turn into a shutdown state (because they are no longer running)" +msgstr "" + +#: ./doc/admin-guide-cloud/ch_compute.xml:2605(para) +msgid "Into the database, data was not updated at all, since Compute could not have guessed the crash." +msgstr "" + +#: ./doc/admin-guide-cloud/ch_compute.xml:2610(para) +msgid "Before going further, and to prevent the admin to make fatal mistakes, the instances won't be lost, because no \"\" or \"\" command was invoked, so the files for the instances remain on the compute node." +msgstr "" + +#: ./doc/admin-guide-cloud/ch_compute.xml:2617(para) +msgid "Perform these tasks in that exact order." +msgstr "" + +#: ./doc/admin-guide-cloud/ch_compute.xml:2618(para) +msgid "Any extra step would be dangerous at this stage :" +msgstr "" + +#: ./doc/admin-guide-cloud/ch_compute.xml:2623(para) +msgid "Get the current relation from a volume to its instance, so that you can recreate the attachment." +msgstr "" + +#: ./doc/admin-guide-cloud/ch_compute.xml:2628(para) +msgid "Update the database to clean the stalled state. (After that, you cannot perform the first step)." +msgstr "" + +#: ./doc/admin-guide-cloud/ch_compute.xml:2633(para) +msgid "Restart the instances. In other words, go from a shutdown to running state." +msgstr "" + +#: ./doc/admin-guide-cloud/ch_compute.xml:2638(para) +msgid "After the restart, you can reattach the volumes to their respective instances." +msgstr "" + +#: ./doc/admin-guide-cloud/ch_compute.xml:2643(para) +msgid "That step, which is not a mandatory one, exists in an SSH into the instances to reboot them." +msgstr "" + +#: ./doc/admin-guide-cloud/ch_compute.xml:2651(title) +msgid "B - Disaster recovery" +msgstr "" + +#: ./doc/admin-guide-cloud/ch_compute.xml:2653(title) +msgid "To perform disaster recovery" +msgstr "" + +#: ./doc/admin-guide-cloud/ch_compute.xml:2655(title) +msgid "Get the instance-to-volume relationship" +msgstr "" + +#: ./doc/admin-guide-cloud/ch_compute.xml:2657(para) +msgid "You must get the current relationship from a volume to its instance, because we re-create the attachment." +msgstr "" + +#: ./doc/admin-guide-cloud/ch_compute.xml:2660(para) +msgid "You can find this relationship by running . Note that nova client includes the ability to get volume information from cinder." +msgstr "" + +#: ./doc/admin-guide-cloud/ch_compute.xml:2667(title) +msgid "Update the database" +msgstr "" + +#: ./doc/admin-guide-cloud/ch_compute.xml:2668(para) +msgid "Update the database to clean the stalled state. You must restore for every volume, uses these queries to clean up the database:" +msgstr "" + +#: ./doc/admin-guide-cloud/ch_compute.xml:2677(para) +msgid "Then, when you run commands, all volumes appear." +msgstr "" + +#: ./doc/admin-guide-cloud/ch_compute.xml:2682(title) +msgid "Restart instances" +msgstr "" + +#: ./doc/admin-guide-cloud/ch_compute.xml:2685(replaceable) +msgid "$instance" +msgstr "" + +#: ./doc/admin-guide-cloud/ch_compute.xml:2683(para) +msgid "You can restart the instances through the ." +msgstr "" + +#: ./doc/admin-guide-cloud/ch_compute.xml:2686(para) +msgid "At that stage, depending on your image, some instances completely reboot and become reachable, while others stop on the \"plymouth\" stage." +msgstr "" + +#: ./doc/admin-guide-cloud/ch_compute.xml:2692(title) +msgid "DO NOT reboot a second time" +msgstr "" + +#: ./doc/admin-guide-cloud/ch_compute.xml:2693(para) +msgid "Do not reboot the ones that are stopped at that stage (see the fourth step). In fact it depends on whether you added an /etc/fstab entry for that volume. Images built with the cloud-init package remain in a pending state, while others skip the missing volume and start. (More information is available on help.ubuntu.com.) The idea of that stage is only to ask nova to reboot every instance, so the stored state is preserved." +msgstr "" + +#: ./doc/admin-guide-cloud/ch_compute.xml:2710(title) +msgid "Reattach volumes" +msgstr "" + +#: ./doc/admin-guide-cloud/ch_compute.xml:2711(para) +msgid "After the restart, you can reattach the volumes to their respective instances. Now that nova has restored the right status, it is time to perform the attachments through a " +msgstr "" + +#: ./doc/admin-guide-cloud/ch_compute.xml:2717(para) +msgid "This simple snippet uses the created file:" +msgstr "" + +#: ./doc/admin-guide-cloud/ch_compute.xml:2729(para) +msgid "At that stage, instances that were pending on the boot sequence (plymouth) automatically continue their boot, and restart normally, while the ones that booted see the volume." +msgstr "" + +#: ./doc/admin-guide-cloud/ch_compute.xml:2737(title) +msgid "SSH into instances" +msgstr "" + +#: ./doc/admin-guide-cloud/ch_compute.xml:2738(para) +msgid "If some services depend on the volume, or if a volume has an entry into fstab, it could be good to simply restart the instance. This restart needs to be made from the instance itself, not through nova. So, we SSH into the instance and perform a reboot:" +msgstr "" + +#: ./doc/admin-guide-cloud/ch_compute.xml:2748(para) +msgid "By completing this procedure, you can successfully recover your cloud." +msgstr "" + +#: ./doc/admin-guide-cloud/ch_compute.xml:2750(para) +msgid "Follow these guidelines:" +msgstr "" + +#: ./doc/admin-guide-cloud/ch_compute.xml:2753(para) +msgid "Use the errors=remount parameter in the fstab file, which prevents data corruption." +msgstr "" + +#: ./doc/admin-guide-cloud/ch_compute.xml:2757(para) +msgid "The system would lock any write to the disk if it detects an I/O error. This configuration option should be added into the cinder-volume server (the one which performs the ISCSI connection to the SAN), but also into the instances' fstab file." +msgstr "" + +#: ./doc/admin-guide-cloud/ch_compute.xml:2768(para) +msgid "Do not add the entry for the SAN's disks to the cinder-volume's fstab file." +msgstr "" + +#: ./doc/admin-guide-cloud/ch_compute.xml:2773(para) +msgid "Some systems hang on that step, which means you could lose access to your cloud-controller. To re-run the session manually, you would run the following command before performing the mount: " +msgstr "" + +#: ./doc/admin-guide-cloud/ch_compute.xml:2781(para) +msgid "For your instances, if you have the whole /home/ directory on the disk, instead of emptying the /home directory and map the disk on it, leave a user's directory with the user's bash files and the authorized_keys file." +msgstr "" + +#: ./doc/admin-guide-cloud/ch_compute.xml:2789(para) +msgid "This enables you to connect to the instance, even without the volume attached, if you allow only connections through public keys." +msgstr "" + +#: ./doc/admin-guide-cloud/ch_compute.xml:2797(title) +msgid "C - Scripted DRP" +msgstr "" + +#: ./doc/admin-guide-cloud/ch_compute.xml:2799(title) +msgid "To use scripted DRP" +msgstr "" + +#: ./doc/admin-guide-cloud/ch_compute.xml:2800(para) +msgid "You can download from here a bash script which performs these steps:" +msgstr "" + +#: ./doc/admin-guide-cloud/ch_compute.xml:2805(para) +msgid "The \"test mode\" allows you to perform that whole sequence for only one instance." +msgstr "" + +#: ./doc/admin-guide-cloud/ch_compute.xml:2810(para) +msgid "To reproduce the power loss, connect to the compute node which runs that same instance and close the iscsi session. Do not detach the volume through , but instead manually close the iscsi session." +msgstr "" + +#: ./doc/admin-guide-cloud/ch_compute.xml:2821(para) +msgid "In this example, the iscsi session is number 15 for that instance:" +msgstr "" + +#: ./doc/admin-guide-cloud/ch_compute.xml:2826(para) +msgid "Do not forget the -r flag. Otherwise, you close ALL sessions." +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking-config-identity.xml:6(title) +msgid "Configure Identity Service for Networking" +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking-config-identity.xml:8(title) +msgid "To configure the Identity Service for use with Networking" +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking-config-identity.xml:11(title) +msgid "Create the get_id() function" +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking-config-identity.xml:12(para) +msgid "The get_id() function stores the ID of created objects, and removes the need to copy and paste object IDs in later steps:" +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking-config-identity.xml:16(para) +msgid "Add the following function to your .bashrc file:" +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking-config-identity.xml:23(para) +msgid "Source the .bashrc file:" +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking-config-identity.xml:29(title) +msgid "Create the Networking service entry" +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking-config-identity.xml:30(para) +msgid "Networking must be available in the Compute service catalog. Create the service:" +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking-config-identity.xml:34(title) +msgid "Create the Networking service endpoint entry" +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking-config-identity.xml:36(para) +msgid "The way that you create a Networking endpoint entry depends on whether you are using the SQL or the template catalog driver:" +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking-config-identity.xml:40(para) +msgid "If you use the SQL driver, run the following command with the specified region ($REGION), IP address of the Networking server ($IP), and service ID ($NEUTRON_SERVICE_ID, obtained in the previous step)." +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking-config-identity.xml:52(para) +msgid "If you are using the template driver, specify the following parameters in your Compute catalog template file (default_catalog.templates), along with the region ($REGION) and IP address of the Networking server ($IP)." +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking-config-identity.xml:70(title) +msgid "Create the Networking service user" +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking-config-identity.xml:71(para) +msgid "You must provide admin user credentials that Compute and some internal Networking components can use to access the Networking API. Create a special service tenant and a neutron user within this tenant, and assign an admin role to this role." +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking-config-identity.xml:77(para) +msgid "Create the admin role:" +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking-config-identity.xml:82(para) +msgid "Create the neutron user:" +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking-config-identity.xml:87(para) +msgid "Create the service tenant:" +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking-config-identity.xml:91(para) +msgid "Establish the relationship among the tenant, user, and role:" +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking-config-identity.xml:98(para) +msgid "For information about how to create service entries and users, see the OpenStack Installation Guide for your distribution (docs.openstack.org)." +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking-config-identity.xml:103(para) +msgid "If you use Networking, do not run the Compute nova-network service (like you do in traditional Compute deployments). Instead, Compute delegates most network-related decisions to Networking. Compute proxies tenant-facing API calls to manage security groups and floating IPs to Networking APIs. However, operator-facing tools such as nova-manage, are not proxied and should not be used." +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking-config-identity.xml:110(para) +msgid "When you configure networking, you must use this guide. Do not rely on Compute networking documentation or past experience with Compute. If a command or configuration option related to networking is not mentioned in this guide, the command is probably not supported for use with Networking. In particular, you cannot use CLI tools like and to manage networks or IP addressing, including both fixed and floating IPs, with Networking." +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking-config-identity.xml:118(para) +msgid "Uninstall nova-network and reboot any physical nodes that have been running nova-network before using them to run Networking. Inadvertently running the nova-network process while using Networking can cause problems, as can stale iptables rules pushed down by previously running nova-network." +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking-config-identity.xml:126(para) +msgid "To ensure that Compute works properly with Networking (rather than the legacy nova-network mechanism), you must adjust settings in the nova.conf configuration file." +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking-config-identity.xml:133(title) +msgid "Networking API and credential configuration" +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking-config-identity.xml:134(para) +msgid "Each time you provision or de-provision a VM in Compute, nova-* services communicate with Networking using the standard API. For this to happen, you must configure the following items in the nova.conf file (used by each nova-compute and nova-api instance)." +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking-config-identity.xml:140(caption) +msgid "nova.conf API and credential settings" +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking-config-identity.xml:145(th) ./doc/admin-guide-cloud/section_networking-config-identity.xml:220(td) ./doc/admin-guide-cloud/section_networking-config-identity.xml:255(td) +msgid "Item" +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking-config-identity.xml:151(literal) +msgid "network_api_class" +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking-config-identity.xml:153(para) +msgid "Modify from the default to nova.network.neutronv2.api.API, to indicate that Networking should be used rather than the traditional nova-network networking model." +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking-config-identity.xml:161(literal) +msgid "neutron_url" +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking-config-identity.xml:162(para) +msgid "Update to the hostname/IP and port of the neutron-server instance for this deployment." +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking-config-identity.xml:168(literal) +msgid "neutron_auth_strategy" +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking-config-identity.xml:169(para) +msgid "Keep the default keystone value for all production deployments." +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking-config-identity.xml:173(literal) +msgid "neutron_admin_tenant_name" +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking-config-identity.xml:175(para) +msgid "Update to the name of the service tenant created in the above section on Identity configuration." +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking-config-identity.xml:180(literal) +msgid "neutron_admin_username" +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking-config-identity.xml:182(para) +msgid "Update to the name of the user created in the above section on Identity configuration." +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking-config-identity.xml:187(literal) +msgid "neutron_admin_password" +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking-config-identity.xml:189(para) +msgid "Update to the password of the user created in the above section on Identity configuration." +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking-config-identity.xml:194(literal) +msgid "neutron_admin_auth_url" +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking-config-identity.xml:196(para) +msgid "Update to the Identity server IP and port. This is the Identity (keystone) admin API server IP and port value, and not the Identity service API IP and port." +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking-config-identity.xml:206(title) +msgid "Configure security groups" +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking-config-identity.xml:207(para) +msgid "The Networking Service provides security group functionality using a mechanism that is more flexible and powerful than the security group capabilities built into Compute. Therefore, if you use Networking, you should always disable built-in security groups and proxy all security group calls to the Networking API . If you do not, security policies will conflict by being simultaneously applied by both services." +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking-config-identity.xml:212(para) +msgid "To proxy security groups to Networking, use the following configuration values in nova.conf:" +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking-config-identity.xml:215(caption) +msgid "nova.conf security group settings" +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking-config-identity.xml:226(literal) +msgid "firewall_driver" +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking-config-identity.xml:227(para) +msgid "Update to nova.virt.firewall.NoopFirewallDriver, so that nova-compute does not perform iptables-based filtering itself." +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking-config-identity.xml:234(literal) +msgid "security_group_api" +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking-config-identity.xml:235(para) +msgid "Update to neutron, so that all security group requests are proxied to the Network Service." +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking-config-identity.xml:242(title) +msgid "Configure metadata" +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking-config-identity.xml:243(para) +msgid "The Compute service allows VMs to query metadata associated with a VM by making a web request to a special 169.254.169.254 address. Networking supports proxying those requests to nova-api, even when the requests are made from isolated networks, or from multiple networks that use overlapping IP addresses." +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking-config-identity.xml:247(para) +msgid "To enable proxying the requests, you must update the following fields in nova.conf." +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking-config-identity.xml:250(caption) +msgid "nova.conf metadata settings" +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking-config-identity.xml:261(literal) +msgid "service_neutron_metadata_proxy" +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking-config-identity.xml:263(para) +msgid "Update to true, otherwise nova-api will not properly respond to requests from the neutron-metadata-agent." +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking-config-identity.xml:270(literal) +msgid "neutron_metadata_proxy_shared_secret" +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking-config-identity.xml:272(para) +msgid "Update to a string \"password\" value. You must also configure the same value in the metadata_agent.ini file, to authenticate requests made for metadata." +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking-config-identity.xml:276(para) +msgid "The default value of an empty string in both files will allow metadata to function, but will not be secure if any non-trusted entities have access to the metadata APIs exposed by nova-api." +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking-config-identity.xml:285(para) +msgid "As a precaution, even when using neutron_metadata_proxy_shared_secret, it is recommended that you do not expose metadata using the same nova-api instances that are used for tenants. Instead, you should run a dedicated set of nova-api instances for metadata that are available only on your management network. Whether a given nova-api instance exposes metadata APIs is determined by the value of enabled_apis in its nova.conf." +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking-config-identity.xml:300(title) +msgid "Example nova.conf (for nova-compute and nova-api)" +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking-config-identity.xml:303(para) +msgid "Example values for the above settings, assuming a cloud controller node running Compute and Networking with an IP address of 192.168.1.2:" +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking-use.xml:5(title) +msgid "Use Networking" +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking-use.xml:6(para) +msgid "You can start and stop OpenStack Networking services using the service command. For example:" +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking-use.xml:13(para) +msgid "Log files are in the /var/log/neutron directory." +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking-use.xml:16(para) +msgid "Configuration files are in the /etc/neutron directory." +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking-use.xml:19(para) +msgid "You can use Networking in the following ways:" +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking-use.xml:22(para) +msgid "Expose the Networking API to cloud tenants, which enables them to build rich network topologies." +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking-use.xml:27(para) +msgid "Have the cloud administrator, or an automated administrative tool, create network connectivity on behalf of tenants." +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking-use.xml:32(para) +msgid "A tenant or cloud administrator can both perform the following procedures." +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking-use.xml:35(title) +msgid "Core Networking API features" +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking-use.xml:36(para) +msgid "After you install and run Networking, tenants and administrators can perform create-read-update-delete (CRUD) API networking operations by using the Networking API directly or the neutron command-line interface (CLI). The neutron CLI is a wrapper around the Networking API. Every Networking API call has a corresponding neutron command." +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking-use.xml:43(para) +msgid "The CLI includes a number of options. For details, refer to the OpenStack End User Guide." +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking-use.xml:49(title) ./doc/admin-guide-cloud/section_networking-use.xml:57(caption) +msgid "API abstractions" +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking-use.xml:50(para) +msgid "The Networking v2.0 API provides control over both L2 network topologies and the IP addresses used on those networks (IP Address Management or IPAM). There is also an extension to cover basic L3 forwarding and NAT, which provides capabilities similar to ." +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking-use.xml:62(th) +msgid "Abstraction" +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking-use.xml:70(td) +msgid "An isolated L2 network segment (similar to a VLAN) that forms the basis for describing the L2 network topology available in an Networking deployment." +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking-use.xml:79(td) +msgid "Associates a block of IP addresses and other network configuration, such as, default gateways or dns-servers, with an Networking network. Each subnet represents an IPv4 or IPv6 address block and, if needed, each Networking network can have multiple subnets." +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking-use.xml:91(td) +msgid "Represents an attachment port to a L2 Networking network. When a port is created on the network, by default it is allocated an available fixed IP address out of one of the designated subnets for each IP version (if one exists). When the port is destroyed, its allocated addresses return to the pool of available IPs on the subnet. Users of the Networking API can either choose a specific IP address from the block, or let Networking choose the first available IP address." +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking-use.xml:110(para) +msgid "This table summarizes the attributes available for each networking abstraction. For information about API abstraction and operations, see the Networking API v2.0 Reference." +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking-use.xml:117(caption) +msgid "Network attributes" +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking-use.xml:124(th) ./doc/admin-guide-cloud/section_networking-use.xml:197(th) ./doc/admin-guide-cloud/section_networking-use.xml:301(th) +msgid "Attribute" +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking-use.xml:133(td) ./doc/admin-guide-cloud/section_networking-use.xml:155(td) ./doc/admin-guide-cloud/section_networking-use.xml:234(td) ./doc/admin-guide-cloud/section_networking-use.xml:310(td) +msgid "bool" +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking-use.xml:135(td) +msgid "Administrative state of the network. If specified as False (down), this network does not forward packets." +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking-use.xml:143(td) ./doc/admin-guide-cloud/section_networking-use.xml:258(td) ./doc/admin-guide-cloud/section_networking-use.xml:343(td) ./doc/admin-guide-cloud/section_networking-use.xml:349(td) +msgid "Generated" +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking-use.xml:144(td) +msgid "UUID for this network." +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking-use.xml:148(td) ./doc/admin-guide-cloud/section_networking-use.xml:165(td) ./doc/admin-guide-cloud/section_networking-use.xml:220(td) ./doc/admin-guide-cloud/section_networking-use.xml:241(td) ./doc/admin-guide-cloud/section_networking-use.xml:269(td) ./doc/admin-guide-cloud/section_networking-use.xml:318(td) ./doc/admin-guide-cloud/section_networking-use.xml:326(td) ./doc/admin-guide-cloud/section_networking-use.xml:348(td) ./doc/admin-guide-cloud/section_networking-use.xml:354(td) ./doc/admin-guide-cloud/section_networking-use.xml:368(td) +msgid "string" +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking-use.xml:150(td) +msgid "Human-readable name for this network; is not required to be unique." +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking-use.xml:157(td) +msgid "Specifies whether this network resource can be accessed by any tenant. The default policy setting restricts usage of this attribute to administrative users only." +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking-use.xml:167(td) +msgid "Indicates whether this network is currently operational." +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking-use.xml:171(option) +msgid "subnets" +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking-use.xml:172(td) +msgid "list(uuid-str)" +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking-use.xml:173(td) ./doc/admin-guide-cloud/section_networking-use.xml:228(td) ./doc/admin-guide-cloud/section_networking-use.xml:250(td) +msgid "Empty list" +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking-use.xml:174(td) +msgid "List of subnets associated with this network." +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking-use.xml:181(td) +msgid "Tenant owner of the network. Only administrative users can set the tenant identifier; this cannot be changed using authorization policies." +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking-use.xml:190(caption) +msgid "Subnet attributes" +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking-use.xml:205(option) +msgid "allocation_pools" +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking-use.xml:206(td) ./doc/admin-guide-cloud/section_networking-use.xml:249(td) ./doc/admin-guide-cloud/section_networking-use.xml:333(td) +msgid "list(dict)" +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking-use.xml:209(option) ./doc/admin-guide-cloud/section_networking-use.xml:240(option) +msgid "gateway_ip" +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking-use.xml:207(td) +msgid "Every address in , excluding (if configured)." +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking-use.xml:211(para) +msgid "List of cidr sub-ranges that are available for dynamic allocation to ports. Syntax:" +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking-use.xml:222(td) +msgid "IP range for this subnet, based on the IP version." +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking-use.xml:226(option) +msgid "dns_nameservers" +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking-use.xml:227(td) +msgid "list(string)" +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking-use.xml:229(td) +msgid "List of DNS name servers used by hosts in this subnet." +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking-use.xml:233(option) +msgid "enable_dhcp" +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking-use.xml:236(td) +msgid "Specifies whether DHCP is enabled for this subnet." +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking-use.xml:242(td) +msgid "First address in " +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking-use.xml:244(td) +msgid "Default gateway used by devices in this subnet." +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking-use.xml:248(option) +msgid "host_routes" +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking-use.xml:251(td) +msgid "Routes that should be used by devices with IPs from this subnet (not including local subnet route)." +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking-use.xml:257(td) ./doc/admin-guide-cloud/section_networking-use.xml:276(td) ./doc/admin-guide-cloud/section_networking-use.xml:283(td) ./doc/admin-guide-cloud/section_networking-use.xml:342(td) ./doc/admin-guide-cloud/section_networking-use.xml:361(td) ./doc/admin-guide-cloud/section_networking-use.xml:375(td) +msgid "uuid-string" +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking-use.xml:259(td) +msgid "UUID representing this subnet." +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking-use.xml:263(td) +msgid "int" +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking-use.xml:265(td) +msgid "IP version." +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking-use.xml:271(td) +msgid "Human-readable name for this subnet (might not be unique)." +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking-use.xml:275(option) ./doc/admin-guide-cloud/section_networking-use.xml:360(option) +msgid "network_id" +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking-use.xml:278(td) +msgid "Network with which this subnet is associated." +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking-use.xml:285(td) +msgid "Owner of network. Only administrative users can set the tenant identifier; this cannot be changed using authorization policies." +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking-use.xml:294(caption) +msgid "Port attributes" +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking-use.xml:311(td) +msgid "true" +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking-use.xml:312(td) +msgid "Administrative state of this port. If specified as False (down), this port does not forward packets." +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking-use.xml:317(option) +msgid "device_id" +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking-use.xml:320(td) +msgid "Identifies the device using this port (for example, a virtual server's ID)." +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking-use.xml:325(option) ./doc/admin-guide-cloud/section_networking-use.xml:426(option) +msgid "device_owner" +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking-use.xml:328(td) +msgid "Identifies the entity using this port (for example, a dhcp agent)." +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking-use.xml:332(option) ./doc/admin-guide-cloud/section_networking-use.xml:425(option) +msgid "fixed_ips" +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking-use.xml:334(td) +msgid "Automatically allocated from pool" +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking-use.xml:335(td) +msgid "Specifies IP addresses for this port; associates the port with the subnets containing the listed IP addresses." +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking-use.xml:344(td) +msgid "UUID for this port." +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking-use.xml:347(option) ./doc/admin-guide-cloud/section_networking-use.xml:570(option) +msgid "mac_address" +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking-use.xml:350(td) +msgid "Mac address to use on this port." +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking-use.xml:356(td) +msgid "Human-readable name for this port (might not be unique)." +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking-use.xml:363(td) +msgid "Network with which this port is associated." +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking-use.xml:370(td) +msgid "Indicates whether the network is currently operational." +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking-use.xml:377(td) +msgid "Owner of the network. Only administrative users can set the tenant identifier; this cannot be changed using authorization policies." +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking-use.xml:387(title) ./doc/admin-guide-cloud/section_networking-use.xml:398(caption) +msgid "Basic Networking operations" +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking-use.xml:388(para) +msgid "To learn about advanced capabilities that are available through the neutron command-line interface (CLI), read the networking section in the OpenStack End User Guide." +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking-use.xml:394(para) +msgid "This table shows example neutron commands that enable you to complete basic Networking operations:" +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking-use.xml:409(td) +msgid "Creates a network." +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking-use.xml:413(td) +msgid "Creates a subnet that is associated with net1." +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking-use.xml:418(td) +msgid "Lists ports for a specified tenant." +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking-use.xml:423(td) +msgid "Lists ports for a specified tenant and displays the , , and columns." +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking-use.xml:432(td) +msgid "Shows information for a specified port." +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking-use.xml:434(replaceable) ./doc/admin-guide-cloud/section_networking-use.xml:577(replaceable) ./doc/admin-guide-cloud/section_networking-use.xml:630(option) ./doc/admin-guide-cloud/section_networking-use.xml:634(replaceable) +msgid "port-id" +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking-use.xml:439(para) +msgid "The field describes who owns the port. A port whose begins with:" +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking-use.xml:445(para) +msgid "network is created by Networking." +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking-use.xml:449(para) +msgid "compute is created by Compute." +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking-use.xml:456(title) +msgid "Administrative operations" +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking-use.xml:457(para) +msgid "The cloud administrator can run any command on behalf of tenants by specifying an Identity in the command, as follows:" +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking-use.xml:462(replaceable) +msgid "tenant-id" +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking-use.xml:462(replaceable) +msgid "network-name" +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking-use.xml:466(para) +msgid "To view all tenant IDs in Identity, run the following command as an Identity Service admin user:" +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking-use.xml:474(title) ./doc/admin-guide-cloud/section_networking-use.xml:479(caption) +msgid "Advanced Networking operations" +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking-use.xml:475(para) +msgid "This table shows example neutron commands that enable you to complete advanced Networking operations:" +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking-use.xml:490(td) +msgid "Creates a network that all tenants can use." +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking-use.xml:495(td) +msgid "Creates a subnet with a specified gateway IP address." +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking-use.xml:500(td) +msgid "Creates a subnet that has no gateway IP address." +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking-use.xml:505(td) +msgid "Creates a subnet with DHCP disabled." +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking-use.xml:510(td) +msgid "Creates a subnet with a specified set of host routes." +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking-use.xml:515(td) +msgid "Creates a subnet with a specified set of dns name servers." +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking-use.xml:520(td) +msgid "Displays all ports and IPs allocated on a network." +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking-use.xml:522(replaceable) ./doc/admin-guide-cloud/section_networking-use.xml:555(replaceable) ./doc/admin-guide-cloud/section_networking-use.xml:632(option) ./doc/admin-guide-cloud/section_networking-use.xml:633(replaceable) +msgid "net-id" +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking-use.xml:530(title) +msgid "Use Compute with Networking" +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking-use.xml:532(title) ./doc/admin-guide-cloud/section_networking-use.xml:537(caption) +msgid "Basic Compute and Networking operations" +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking-use.xml:533(para) +msgid "This table shows example neutron and nova commands that enable you to complete basic Compute and Networking operations:" +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking-use.xml:543(th) +msgid "Action" +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking-use.xml:549(td) +msgid "Checks available networks." +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking-use.xml:553(td) +msgid "Boots a VM with a single NIC on a selected Networking network." +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking-use.xml:555(replaceable) ./doc/admin-guide-cloud/section_networking-use.xml:624(replaceable) ./doc/admin-guide-cloud/section_networking-use.xml:634(replaceable) ./doc/admin-guide-cloud/section_networking-use.xml:643(replaceable) +msgid "img" +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking-use.xml:555(replaceable) ./doc/admin-guide-cloud/section_networking-use.xml:624(replaceable) ./doc/admin-guide-cloud/section_networking-use.xml:634(replaceable) ./doc/admin-guide-cloud/section_networking-use.xml:643(replaceable) +msgid "flavor" +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking-use.xml:555(replaceable) ./doc/admin-guide-cloud/section_networking-use.xml:624(replaceable) ./doc/admin-guide-cloud/section_networking-use.xml:634(replaceable) ./doc/admin-guide-cloud/section_networking-use.xml:643(replaceable) +msgid "vm-name" +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking-use.xml:559(para) +msgid "Searches for ports with a that matches the Compute instance UUID. See ." +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking-use.xml:566(replaceable) ./doc/admin-guide-cloud/section_networking-use.xml:572(replaceable) +msgid "vm-id" +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking-use.xml:569(td) +msgid "Searches for ports, but shows only the for the port." +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking-use.xml:575(td) +msgid "Temporarily disables a port from sending traffic." +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking-use.xml:582(para) +msgid "The can also be a logical router ID." +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking-use.xml:586(title) +msgid "Create and delete VMs" +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking-use.xml:589(para) +msgid "When you boot a Compute VM, a port on the network that corresponds to the VM NIC is automatically created and associated with the default security group. You can configure security group rules to enable users to access the VM." +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking-use.xml:599(para) +msgid "When you delete a Compute VM, the underlying Networking port is automatically deleted." +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking-use.xml:607(title) ./doc/admin-guide-cloud/section_networking-use.xml:612(caption) +msgid "Advanced VM creation operations" +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking-use.xml:608(para) +msgid "This table shows example nova and neutron commands that enable you to complete advanced VM creation operations:" +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking-use.xml:623(td) +msgid "Boots a VM with multiple NICs." +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking-use.xml:624(replaceable) +msgid "net1-id" +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking-use.xml:624(replaceable) +msgid "net2-id" +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking-use.xml:627(td) +msgid "Boots a VM with a specific IP address. First, create an Networking port with a specific IP address. Then, boot a VM specifying a rather than a ." +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking-use.xml:633(replaceable) +msgid "subnet-id" +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking-use.xml:633(replaceable) +msgid "IP" +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking-use.xml:641(parameter) +msgid "--nic" +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking-use.xml:638(td) +msgid "Boots a VM that connects to all networks that are accessible to the tenant who submits the request (without the option)." +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking-use.xml:649(para) +msgid "Networking does not currently support the v4-fixed-ip parameter of the --nic option for the command." +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking-use.xml:656(title) +msgid "Enable ping and SSH on VMs (security groups)" +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking-use.xml:658(para) +msgid "You must configure security group rules depending on the type of plug-in you are using. If you are using a plug-in that:" +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking-use.xml:663(para) +msgid "Implements Networking security groups, you can configure security group rules directly by using . This example enables and access to your VMs." +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking-use.xml:677(para) +msgid "Does not implement Networking security groups, you can configure security group rules by using the or command. These commands enable and access to your VMs." +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking-use.xml:691(para) +msgid "If your plug-in implements Networking security groups, you can also leverage Compute security groups by setting security_group_api = neutron in the nova.conf file. After you set this option, all Compute security group commands are proxied to Networking." +msgstr "" + +#: ./doc/admin-guide-cloud/identity/section_keystone-token-binding.xml:6(title) +msgid "Configure the Identity Service for token binding" +msgstr "" + +#: ./doc/admin-guide-cloud/identity/section_keystone-token-binding.xml:7(para) +msgid "Token binding refers to the practice of embedding information from external authentication providers (like a company's Kerberos server) inside the token such that a client may enforce that the token only be used in conjunction with that specified authentication. This is an additional security mechanism as it means that if a token is stolen it will not be usable without also providing the external authentication." +msgstr "" + +#: ./doc/admin-guide-cloud/identity/section_keystone-token-binding.xml:14(para) +msgid "To activate token binding you must specify the types of authentication that token binding should be used for in keystone.conf: Currently only kerberos is supported." +msgstr "" + +#: ./doc/admin-guide-cloud/identity/section_keystone-token-binding.xml:25(para) +msgid "disabled disable token bind checking" +msgstr "" + +#: ./doc/admin-guide-cloud/identity/section_keystone-token-binding.xml:29(para) +msgid "permissive enable bind checking, if a token is bound to a mechanism that is unknown to the server then ignore it. This is the default." +msgstr "" + +#: ./doc/admin-guide-cloud/identity/section_keystone-token-binding.xml:34(para) +msgid "strict enable bind checking, if a token is bound to a mechanism that is unknown to the server then this token should be rejected." +msgstr "" + +#: ./doc/admin-guide-cloud/identity/section_keystone-token-binding.xml:39(para) +msgid "required enable bind checking and require that at least 1 bind mechanism is used for tokens." +msgstr "" + +#: ./doc/admin-guide-cloud/identity/section_keystone-token-binding.xml:44(para) +msgid "named enable bind checking and require that the specified authentication mechanism is used: " +msgstr "" + +#: ./doc/admin-guide-cloud/identity/section_keystone-token-binding.xml:51(para) +msgid "Do not set enforce_token_bind = named as there is not an authentication mechanism called named." +msgstr "" + +#: ./doc/admin-guide-cloud/identity/section_keystone-token-binding.xml:20(para) +msgid "To enforce checking of token binding the enforce_token_bind parameter should be set to one of the following modes: " +msgstr "" + +#. Put one translator per line, in the form of NAME , YEAR1, YEAR2 +#: ./doc/admin-guide-cloud/identity/section_keystone-token-binding.xml:0(None) +msgid "translator-credits" +msgstr "" + diff --git a/doc/admin-guide-cloud/locale/he_IL.po b/doc/admin-guide-cloud/locale/he_IL.po new file mode 100644 index 0000000000..5b324d0b00 --- /dev/null +++ b/doc/admin-guide-cloud/locale/he_IL.po @@ -0,0 +1,11874 @@ +# +# Translators: +msgid "" +msgstr "" +"Project-Id-Version: OpenStack Manuals\n" +"POT-Creation-Date: 2014-01-30 06:24+0000\n" +"PO-Revision-Date: 2014-01-29 22:14+0000\n" +"Last-Translator: openstackjenkins \n" +"Language-Team: Hebrew (Israel) (http://www.transifex.com/projects/p/openstack/language/he_IL/)\n" +"MIME-Version: 1.0\n" +"Content-Type: text/plain; charset=UTF-8\n" +"Content-Transfer-Encoding: 8bit\n" +"Language: he_IL\n" +"Plural-Forms: nplurals=2; plural=(n != 1);\n" + +#: ./doc/admin-guide-cloud/section_networking_introduction.xml5(title) +msgid "Introduction to Networking" +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking_introduction.xml6(para) +msgid "" +"The Networking service, code-named Neutron, provides an API that lets you " +"define network connectivity and addressing in the cloud. The Networking " +"service enables operators to leverage different networking technologies to " +"power their cloud networking. The Networking service also provides an API to" +" configure and manage a variety of network services ranging from L3 " +"forwarding and NAT to load balancing, edge firewalls, and IPSEC VPN." +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking_introduction.xml14(para) +msgid "" +"For a detailed description of the Networking API abstractions and their " +"attributes, see the OpenStack Networking API v2.0 " +"Reference." +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking_introduction.xml20(title) +msgid "Networking API" +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking_introduction.xml21(para) +msgid "" +"Networking is a virtual network service that provides a powerful API to " +"define the network connectivity and IP addressing used by devices from other" +" services, such as Compute." +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking_introduction.xml25(para) +msgid "" +"The Compute API has a virtual server abstraction to describe computing " +"resources. Similarly, the Networking API has virtual network, subnet, and " +"port abstractions to describe networking resources." +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking_introduction.xml30(caption) +msgid "Networking resources" +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking_introduction.xml35(th) +msgid "Resource" +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking_introduction.xml36(th) +#: ./doc/admin-guide-cloud/section_networking_arch.xml36(th) +#: ./doc/admin-guide-cloud/section_networking_arch.xml148(th) +#: ./doc/admin-guide-cloud/section_networking_adv_features.xml45(th) +#: ./doc/admin-guide-cloud/section_networking_adv_features.xml171(th) +#: ./doc/admin-guide-cloud/section_networking_adv_features.xml374(th) +#: ./doc/admin-guide-cloud/section_networking_adv_features.xml436(th) +#: ./doc/admin-guide-cloud/section_networking_adv_features.xml759(th) +#: ./doc/admin-guide-cloud/section_networking_adv_features.xml806(th) +#: ./doc/admin-guide-cloud/section_networking_adv_features.xml1074(th) +#: ./doc/admin-guide-cloud/section_networking_adv_features.xml1209(th) +#: ./doc/admin-guide-cloud/section_networking_adv_features.xml1287(th) +#: ./doc/admin-guide-cloud/section_networking_adv_features.xml1524(th) +#: ./doc/admin-guide-cloud/section_networking_adv_features.xml1902(th) +#: ./doc/admin-guide-cloud/section_networking_adv_features.xml2011(th) +#: ./doc/admin-guide-cloud/section_networking_adv_features.xml2054(th) +#: ./doc/admin-guide-cloud/section_networking-use.xml63(th) +#: ./doc/admin-guide-cloud/section_networking-use.xml127(th) +#: ./doc/admin-guide-cloud/section_networking-use.xml200(th) +#: ./doc/admin-guide-cloud/section_networking-use.xml304(th) +msgid "Description" +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking_introduction.xml42(emphasis) +#: ./doc/admin-guide-cloud/section_networking_arch.xml147(th) +#: ./doc/admin-guide-cloud/section_networking-use.xml69(emphasis) +msgid "Network" +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking_introduction.xml43(td) +msgid "" +"An isolated L2 segment, analogous to VLAN in the physical networking world." +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking_introduction.xml48(emphasis) +#: ./doc/admin-guide-cloud/section_networking-use.xml78(emphasis) +msgid "Subnet" +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking_introduction.xml49(td) +msgid "A block of v4 or v6 IP addresses and associated configuration state." +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking_introduction.xml53(emphasis) +#: ./doc/admin-guide-cloud/section_networking-use.xml90(emphasis) +msgid "Port" +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking_introduction.xml54(td) +msgid "" +"A connection point for attaching a single device, such as the NIC of a " +"virtual server, to a virtual network. Also describes the associated network " +"configuration, such as the MAC and IP addresses to be used on that port." +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking_introduction.xml63(para) +msgid "" +"You can configure rich network topologies by creating and configuring " +"networks and subnets, and then instructing other OpenStack services like " +"Compute to attach virtual devices to ports on these networks." +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking_introduction.xml68(para) +msgid "" +"In particular, Networking supports each tenant having multiple private " +"networks, and allows tenants to choose their own IP addressing scheme (even " +"if those IP addresses overlap with those used by other tenants). The " +"Networking service:" +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking_introduction.xml75(para) +msgid "" +"Enables advanced cloud networking use cases, such as building multi-tiered " +"web applications and allowing applications to be migrated to the cloud " +"without changing IP addresses." +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking_introduction.xml82(para) +msgid "" +"Offers flexibility for the cloud administrator to customize network " +"offerings." +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking_introduction.xml87(para) +msgid "" +"Enables developers to extend the Networking API. Over time, the extended " +"functionality becomes part of the core Networking API." +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking_introduction.xml95(title) +msgid "Plug-in architecture" +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking_introduction.xml96(para) +msgid "" +"The original Compute network implementation assumed a basic model of " +"isolation through Linux VLANs and IP tables. Networking introduces the " +"concept of a plug-in, which is a back-" +"end implementation of the Networking API. A plug-in can use a variety of " +"technologies to implement the logical API requests. Some Networking plug-ins" +" might use basic Linux VLANs and IP tables, while others might use more " +"advanced technologies, such as L2-in-L3 tunneling or OpenFlow, to provide " +"similar benefits." +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking_introduction.xml108(caption) +msgid "Available networking plug-ins" +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking_introduction.xml113(th) +#: ./doc/admin-guide-cloud/section_networking_introduction.xml248(th) +#: ./doc/admin-guide-cloud/section_networking_pagination_and_sorting_support.xml12(th) +msgid "Plug-in" +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking_introduction.xml114(th) +msgid "Documentation" +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking_introduction.xml119(emphasis) +msgid "Big Switch Plug-in (Floodlight REST Proxy)" +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking_introduction.xml125(link) +msgid "" +"http://www.openflowhub.org/display/floodlightcontroller/Neutron+REST+Proxy+Plugin" +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking_introduction.xml122(td) +msgid "Documentation included in this guide and " +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking_introduction.xml129(emphasis) +msgid "Brocade Plug-in" +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking_introduction.xml131(td) +msgid "Documentation included in this guide" +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking_introduction.xml135(emphasis) +#: ./doc/admin-guide-cloud/section_networking_introduction.xml274(td) +msgid "Cisco" +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking_introduction.xml138(link) +msgid "http://wiki.openstack.org/cisco-neutron" +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking_introduction.xml141(emphasis) +msgid "Cloudbase Hyper-V Plug-in" +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking_introduction.xml145(link) +msgid "http://www.cloudbase.it/quantum-hyper-v-plugin/" +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking_introduction.xml148(emphasis) +msgid "Linux Bridge Plug-in" +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking_introduction.xml152(link) +msgid "http://wiki.openstack.org/Neutron-Linux-Bridge-Plugin" +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking_introduction.xml155(emphasis) +msgid "Mellanox Plug-in" +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking_introduction.xml159(link) +msgid "https://wiki.openstack.org/wiki/Mellanox-Neutron/" +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking_introduction.xml162(emphasis) +msgid "Midonet Plug-in" +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking_introduction.xml166(link) +msgid "http://www.midokura.com/" +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking_introduction.xml169(emphasis) +msgid "ML2 (Modular Layer 2) Plug-in" +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking_introduction.xml173(link) +msgid "https://wiki.openstack.org/wiki/Neutron/ML2" +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking_introduction.xml176(emphasis) +msgid "NEC OpenFlow Plug-in" +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking_introduction.xml180(link) +msgid "http://wiki.openstack.org/Quantum-NEC-OpenFlow-Plugin" +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking_introduction.xml183(emphasis) +msgid "Nicira NVP Plug-in" +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking_introduction.xml188(link) +msgid "NVP Product Overview" +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking_introduction.xml190(link) +msgid "NVP Product Support" +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking_introduction.xml185(td) +msgid "" +"Documentation included in this guide as well as in , " +"" +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking_introduction.xml193(emphasis) +msgid "Open vSwitch Plug-in" +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking_introduction.xml195(td) +msgid "Documentation included in this guide." +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking_introduction.xml199(emphasis) +msgid "PLUMgrid" +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking_introduction.xml203(link) +msgid "https://https://wiki.openstack.org/wiki/PLUMgrid-Neutron" +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking_introduction.xml200(td) +#: ./doc/admin-guide-cloud/section_networking_introduction.xml208(td) +msgid "Documentation included in this guide as well as in " +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking_introduction.xml206(emphasis) +msgid "Ryu Plug-in" +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking_introduction.xml211(link) +msgid "https://github.com/osrg/ryu/wiki/OpenStack" +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking_introduction.xml215(para) +msgid "" +"Plug-ins can have different properties for hardware requirements, features, " +"performance, scale, or operator tools. Because Networking supports a large " +"number of plug-ins, the cloud administrator can weigh options to decide on " +"the right networking technology for the deployment." +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking_introduction.xml221(para) +msgid "" +"In the Havana release, OpenStack Networking provides the Modular Layer 2 (ML2) " +"plug-in that can concurrently use multiple layer 2 networking " +"technologies that are found in real-world data centers. It currently works " +"with the existing Open vSwitch, Linux Bridge, and Hyper-v L2 agents. The ML2" +" framework simplifies the addition of support for new L2 technologies and " +"reduces the effort that is required to add and maintain them compared to " +"monolithic plug-ins." +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking_introduction.xml232(title) +msgid "Plug-in deprecation notice:" +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking_introduction.xml233(para) +msgid "" +"The Open vSwitch and Linux Bridge plug-ins are deprecated in the Havana " +"release and will be removed in the Icehouse release. All features have been " +"ported to the ML2 plug-in in the form of mechanism drivers. ML2 currently " +"provides Linux Bridge, Open vSwitch and Hyper-v mechanism drivers." +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking_introduction.xml241(para) +msgid "" +"Not all Networking plug-ins are compatible with all possible Compute " +"drivers:" +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking_introduction.xml244(caption) +msgid "Plug-in compatibility with Compute drivers" +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking_introduction.xml249(th) +msgid "Libvirt (KVM/QEMU)" +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking_introduction.xml250(th) +msgid "XenServer" +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking_introduction.xml251(th) +msgid "VMware" +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking_introduction.xml252(th) +#: ./doc/admin-guide-cloud/ch_compute.xml47(link) +msgid "Hyper-V" +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking_introduction.xml253(th) +msgid "Bare-metal" +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking_introduction.xml258(td) +msgid "Big Switch / Floodlight" +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking_introduction.xml259(td) +#: ./doc/admin-guide-cloud/section_networking_introduction.xml267(td) +#: ./doc/admin-guide-cloud/section_networking_introduction.xml275(td) +#: ./doc/admin-guide-cloud/section_networking_introduction.xml286(td) +#: ./doc/admin-guide-cloud/section_networking_introduction.xml291(td) +#: ./doc/admin-guide-cloud/section_networking_introduction.xml299(td) +#: ./doc/admin-guide-cloud/section_networking_introduction.xml307(td) +#: ./doc/admin-guide-cloud/section_networking_introduction.xml315(td) +#: ./doc/admin-guide-cloud/section_networking_introduction.xml318(td) +#: ./doc/admin-guide-cloud/section_networking_introduction.xml323(td) +#: ./doc/admin-guide-cloud/section_networking_introduction.xml331(td) +#: ./doc/admin-guide-cloud/section_networking_introduction.xml332(td) +#: ./doc/admin-guide-cloud/section_networking_introduction.xml333(td) +#: ./doc/admin-guide-cloud/section_networking_introduction.xml339(td) +#: ./doc/admin-guide-cloud/section_networking_introduction.xml347(td) +#: ./doc/admin-guide-cloud/section_networking_introduction.xml349(td) +#: ./doc/admin-guide-cloud/section_networking_introduction.xml355(td) +#: ./doc/admin-guide-cloud/section_networking_adv_features.xml1908(td) +#: ./doc/admin-guide-cloud/section_networking_adv_features.xml1917(td) +#: ./doc/admin-guide-cloud/section_networking_adv_features.xml1926(td) +msgid "Yes" +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking_introduction.xml266(td) +msgid "Brocade" +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking_introduction.xml282(td) +msgid "Cloudbase Hyper-V" +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking_introduction.xml290(td) +#: ./doc/admin-guide-cloud/section_networking-adv-config.xml102(emphasis) +#: ./doc/admin-guide-cloud/section_networking_pagination_and_sorting_support.xml29(td) +#: ./doc/admin-guide-cloud/section_networking-scenarios.xml378(title) +msgid "Linux Bridge" +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking_introduction.xml298(td) +msgid "Mellanox" +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking_introduction.xml306(td) +msgid "Midonet" +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking_introduction.xml314(td) +#: ./doc/admin-guide-cloud/section_networking_pagination_and_sorting_support.xml19(td) +#: ./doc/admin-guide-cloud/section_networking-scenarios.xml581(title) +msgid "ML2" +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking_introduction.xml322(td) +msgid "NEC OpenFlow" +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking_introduction.xml330(td) +msgid "Nicira NVP" +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking_introduction.xml338(td) +#: ./doc/admin-guide-cloud/section_networking-adv-config.xml79(emphasis) +#: ./doc/admin-guide-cloud/section_networking_pagination_and_sorting_support.xml24(td) +#: ./doc/admin-guide-cloud/section_networking-scenarios.xml11(title) +msgid "Open vSwitch" +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking_introduction.xml346(td) +msgid "Plumgrid" +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking_introduction.xml354(td) +msgid "Ryu" +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking_introduction.xml364(title) +msgid "Plug-in configurations" +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking_introduction.xml365(para) +msgid "" +"For configurations options, see Networking configuration " +"options in Configuration Reference. These " +"sections explain how to configure specific plug-ins." +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking_introduction.xml372(title) +msgid "Configure Big Switch, Floodlight REST Proxy plug-in" +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking_introduction.xml375(title) +msgid "To use the REST Proxy plug-in with OpenStack Networking" +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking_introduction.xml378(para) +#: ./doc/admin-guide-cloud/section_networking_introduction.xml531(para) +#: ./doc/admin-guide-cloud/section_networking_introduction.xml695(para) +#: ./doc/admin-guide-cloud/section_networking_introduction.xml738(para) +msgid "Edit /etc/neutron/neutron.conf and set:" +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking_introduction.xml384(para) +msgid "" +"Edit the plug-in configuration file, " +"/etc/neutron/plugins/bigswitch/restproxy.ini, and " +"specify a comma-separated list of " +"controller_ip:port pairs: For " +"database configuration, see Install Networking Services in any of the " +"Installation Guides in the OpenStack Documentation index. " +"(The link defaults to the Ubuntu version.)" +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking_introduction.xml401(para) +#: ./doc/admin-guide-cloud/section_networking_introduction.xml601(para) +#: ./doc/admin-guide-cloud/section_networking_introduction.xml799(para) +msgid "" +"To apply the new settings, restart neutron-" +"server:" +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking_introduction.xml410(title) +msgid "Configure Brocade plug-in" +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking_introduction.xml412(title) +msgid "To use the Brocade plug-in with OpenStack Networking" +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking_introduction.xml415(para) +msgid "" +"Install the Brocade modified Python netconf client (ncclient) library which " +"is available at https://github.com/brocade/ncclient:" +" " +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking_introduction.xml424(para) +msgid "" +"Edit the /etc/neutron/neutron.conf file and set the " +"following option:" +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking_introduction.xml430(para) +msgid "" +"Edit the /etc/neutron/plugins/brocade/brocade.ini " +"configuration file for the Brocade plug-in and specify the admin user name, " +"password, and IP address of the Brocade switch:" +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking_introduction.xml437(replaceable) +#: ./doc/admin-guide-cloud/section_networking_introduction.xml658(replaceable) +#: ./doc/admin-guide-cloud/section_networking_introduction.xml659(replaceable) +#: ./doc/admin-guide-cloud/section_networking_introduction.xml670(replaceable) +msgid "admin" +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking_introduction.xml438(replaceable) +msgid "password" +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking_introduction.xml439(replaceable) +msgid "switch mgmt ip address" +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking_introduction.xml441(para) +msgid "" +"For database configuration, see Install Networking Services in " +"any of the Installation Guides in the OpenStack Documentation index. " +"(The link defaults to the Ubuntu version.)" +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking_introduction.xml453(para) +msgid "" +"To apply the new settings, restart the neutron-server service:" +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking_introduction.xml463(title) +msgid "Configure OVS plug-in" +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking_introduction.xml464(para) +msgid "" +"If you use the Open vSwitch (OVS) plug-in in a deployment with multiple " +"hosts, you will need to use either tunneling or vlans to isolate traffic " +"from multiple networks. Tunneling is easier to deploy because it does not " +"require configuring VLANs on network switches." +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking_introduction.xml471(para) +msgid "This procedure uses tunneling:" +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking_introduction.xml473(title) +msgid "To configure OpenStack Networking to use the OVS plug-in" +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking_introduction.xml476(para) +msgid "" +"Edit /etc/neutron/plugins/openvswitch/ovs_neutron_plugin.ini " +" to specify these values (for database configuration, see Install Networking Services in " +"Installation Guide):" +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking_introduction.xml491(para) +msgid "" +"If you use the neutron DHCP agent, add these lines to the " +"/etc/neutron/dhcp_agent.ini file:" +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking_introduction.xml498(para) +msgid "" +"Create /etc/neutron/dnsmasq-neutron.conf, and add these" +" values to lower the MTU size on instances and prevent packet fragmentation " +"over the GRE tunnel:" +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking_introduction.xml507(para) +msgid "" +"After performing that change on the node running neutron-server, restart neutron-server to apply the new settings:" +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking_introduction.xml519(title) +msgid "Configure Nicira NVP plug-in" +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking_introduction.xml521(title) +msgid "To configure OpenStack Networking to use the NVP plug-in" +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking_introduction.xml523(para) +msgid "" +"While the instructions in this section refer to the Nicira NVP platform, " +"they also apply to VMware NSX." +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking_introduction.xml526(para) +msgid "Install the NVP plug-in, as follows:" +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking_introduction.xml535(para) +msgid "Example neutron.conf file for NVP:" +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking_introduction.xml552(para) +msgid "" +"A set of parameters need to establish and configure the connection with the " +"controller cluster. Such parameters include NVP API endpoints, access " +"credentials, and settings for HTTP redirects and retries in case of " +"connection failures" +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking_introduction.xml564(para) +msgid "" +"In order to ensure correct operations nvp_user shoud be a" +" user with administrator credentials on the NVP platform." +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking_introduction.xml567(para) +msgid "" +"A controller API endpoint consists of the controller's IP address and port; " +"if the port is omitted, port 443 will be used. If multiple API endpoints are" +" specified, it is up to the user to ensure that all these endpoints belong " +"to the same controller cluster; The Openstack Networking Nicira NVP plugin " +"does not perform this check, and results might be unpredictable." +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking_introduction.xml575(para) +msgid "" +"When multiple API endpoints are specified, the plugin will load balance " +"requests on the various API endpoints." +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking_introduction.xml580(para) +msgid "" +"The UUID of the NVP Transport Zone that should be used by default when a " +"tenant creates a network. This value can be retrieved from the NVP Manager's" +" Transport Zones page:" +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking_introduction.xml589(para) +msgid "" +"Ubuntu packaging currently does not update the neutron init script to point " +"to the NVP configuration file. Instead, you must manually update " +"/etc/default/neutron-server with the following:" +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking_introduction.xml543(para) +msgid "" +"To configure the NVP controller cluster for the Openstack Networking " +"Service, locate the [default] section in the " +"/etc/neutron/plugins/nicira/nvp.ini file, and add the " +"following entries (for database configuration, see Install Networking Services in " +"Installation Guide): " +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking_introduction.xml607(para) +msgid "Example nvp.ini file:" +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking_introduction.xml616(para) +msgid "" +"To debug nvp.ini configuration issues, run this command" +" from the host that runs neutron-" +"server:" +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking_introduction.xml622(para) +msgid "" +"This command tests whether neutron-" +"server can log into all of the NVP Controllers and the SQL " +"server, and whether all UUID values are correct." +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking_introduction.xml630(title) +msgid "Loadbalancer-as-a-Service and Firewall-as-a-Service" +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking_introduction.xml631(para) +msgid "" +"The NVP LBaaS and FWaaS services use the standard OpenStack API with the " +"exception of requiring routed-insertion extension support." +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking_introduction.xml632(para) +msgid "" +"Below are the main differences between the NVP implementation and the " +"community reference implementation of these services:" +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking_introduction.xml635(para) +msgid "" +"The NVP LBaaS and FWaaS plugins require the routed-insertion extension, " +"which adds the router_id attribute to the VIP (Virtual IP " +"address) and firewall resources and binds these services to a logical " +"router." +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking_introduction.xml638(para) +msgid "" +"The community reference implementation of LBaaS only supports a one-arm " +"model, which restricts the VIP to be on the same subnet as the backend " +"servers. The NVP LBaaS plugin only supports a two-arm model between north-" +"south traffic, meaning that the VIP can only be created on the external " +"(physical) network." +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking_introduction.xml641(para) +msgid "" +"The community reference implementation of FWaaS applies firewall rules to " +"all logical routers in a tenant, while the NVP FWaaS plugin applies firewall" +" rules only to one logical router according to the router_id of" +" the firewall entity." +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking_introduction.xml645(title) +msgid "" +"To configure Loadbalancer-as-a-Service and Firewall-as-a-Service with NVP:" +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking_introduction.xml647(para) +msgid "Edit /etc/neutron/neutron.conf file:" +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking_introduction.xml653(para) +msgid "Edit /etc/neutron/plugins/nicira/nvp.ini file:" +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking_introduction.xml654(para) +msgid "" +"In addition to the original NVP configuration, the " +"default_l3_gw_service_uuid is required for the NVP Advanced " +"Plugin and a vcns section must be added as shown below." +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking_introduction.xml660(replaceable) +msgid "10.37.1.137:443" +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking_introduction.xml661(replaceable) +msgid "aae63e9b-2e4e-4efe-81a1-92cf32e308bf" +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking_introduction.xml662(replaceable) +msgid "2702f27a-869a-49d1-8781-09331a0f6b9e" +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking_introduction.xml667(replaceable) +msgid "https://10.24.106.219" +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking_introduction.xml673(replaceable) +#: ./doc/admin-guide-cloud/section_networking_adv_features.xml1535(td) +msgid "default" +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking_introduction.xml676(replaceable) +msgid "f2c023cf-76e2-4625-869b-d0dabcfcc638" +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking_introduction.xml690(title) +msgid "Configure PLUMgrid plug-in" +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking_introduction.xml692(title) +msgid "To use the PLUMgrid plug-in with OpenStack Networking" +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking_introduction.xml701(para) +msgid "" +"Edit /etc/neutron/plugins/plumgrid/plumgrid.ini under " +"the [PLUMgridDirector] section, and specify the IP " +"address, port, admin user name, and password of the PLUMgrid Director: " +" For database configuration, see Install Networking Services in " +"Installation Guide." +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking_introduction.xml720(para) +msgid "" +"To apply the settings, restart neutron-" +"server:" +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking_introduction.xml728(title) +msgid "Configure Ryu plug-in" +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking_introduction.xml730(title) +msgid "To use the Ryu plug-in with OpenStack Networking" +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking_introduction.xml733(para) +msgid "Install the Ryu plug-in, as follows:" +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking_introduction.xml756(para) +msgid "" +"The openflow_rest_api is used to tell where Ryu is " +"listening for REST API. Substitute ip-address and " +"port-no based on your Ryu setup." +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking_introduction.xml766(para) +msgid "" +"The ovsdb_interface is used for Ryu to access the " +"ovsdb-server. Substitute eth0 based on your set up." +" The IP address is derived from the interface name. If you want to change " +"this value irrespective of the interface name, " +"ovsdb_ip can be specified. If you use a non-default" +" port for ovsdb-server, it can be specified by " +"ovsdb_port." +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking_introduction.xml783(para) +msgid "" +"tunnel_interface needs to be set to tell what IP " +"address is used for tunneling (if tunneling isn't used, this value is " +"ignored). The IP address is derived from the network interface name." +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking_introduction.xml744(para) +msgid "" +"Edit /etc/neutron/plugins/ryu/ryu.ini (for database " +"configuration, see Install " +"Networking Services in Installation Guide), " +"and update the following in the [ovs] section for " +"the ryu-neutron-agent: " +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking_introduction.xml792(para) +msgid "" +"You can use the same configuration file for many Compute nodes by using a " +"network interface name with a different IP address:" +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking_introduction.xml809(title) +msgid "Configure neutron agents" +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking_introduction.xml810(para) +msgid "" +"Plug-ins typically have requirements for particular software that must be " +"run on each node that handles data packets. This includes any node that runs" +" nova-compute and nodes that run " +"dedicated OpenStack Networking service agents such as, neutron-" +"dhcp-agent, neutron-l3-agent, or " +"neutron-lbaas-agent (see below for more information" +" about individual service agents)." +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking_introduction.xml821(para) +msgid "" +"A data-forwarding node typically has a network interface with an IP address " +"on the “management network” and another interface on the “data network”." +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking_introduction.xml825(para) +msgid "" +"This section shows you how to install and configure a subset of the " +"available plug-ins, which may include the installation of switching software" +" (for example, Open vSwitch) as well as agents used to communicate with the " +"neutron-server process running " +"elsewhere in the data center." +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking_introduction.xml833(title) +msgid "Configure data-forwarding nodes" +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking_introduction.xml835(title) +msgid "Node set up: OVS plug-in" +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking_introduction.xml838(para) +msgid "" +"This section also applies to the ML2 plugin when Open vSwitch is used as a " +"mechanism driver." +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking_introduction.xml836(para) +msgid "" +"If you use the Open vSwitch plug-in, you must install Open " +"vSwitch and the neutron-plugin-openvswitch-agent " +"agent on each data-forwarding node:" +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking_introduction.xml844(para) +msgid "" +"Do not install the openvswitch-brcompat package as it breaks the security " +"groups functionality." +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking_introduction.xml849(title) +msgid "To set up each node for the OVS plug-in" +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking_introduction.xml852(para) +msgid "" +"Install the OVS agent package (this pulls in the Open vSwitch software as a " +"dependency):" +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking_introduction.xml858(para) +msgid "" +"On each node that runs the neutron-plugin-openvswitch-" +"agent:" +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking_introduction.xml862(para) +msgid "" +"Replicate the ovs_neutron_plugin.ini file created in " +"the first step onto the node." +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking_introduction.xml868(para) +msgid "" +"If using tunneling, the node's ovs_neutron_plugin.ini " +"file must also be updated with the node's IP address configured on the data " +"network using the local_ip value." +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking_introduction.xml880(para) +#: ./doc/admin-guide-cloud/section_networking_introduction.xml984(para) +msgid "Restart Open vSwitch to properly load the kernel module:" +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking_introduction.xml885(para) +#: ./doc/admin-guide-cloud/section_networking_introduction.xml989(para) +msgid "Restart the agent:" +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking_introduction.xml889(para) +msgid "" +"All nodes that run neutron-plugin-openvswitch-agent" +" must have an OVS br-int bridge. . To create the bridge, " +"run:" +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking_introduction.xml899(title) +msgid "Node set up: Nicira NVP plug-in" +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking_introduction.xml900(para) +msgid "" +"If you use the Nicira NVP plug-in, you must also install Open vSwitch on " +"each data-forwarding node. However, you do not need to install an additional" +" agent on each node." +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking_introduction.xml906(para) +msgid "" +"It is critical that you are running an Open vSwitch version that is " +"compatible with the current version of the NVP Controller software. Do not " +"use the Open vSwitch version that is installed by default on Ubuntu. " +"Instead, use the Open Vswitch version that is provided on the Nicira support" +" portal for your NVP Controller version." +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking_introduction.xml917(title) +msgid "To set up each node for the Nicira NVP plug-in" +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking_introduction.xml920(para) +msgid "" +"Ensure each data-forwarding node has an IP address on the \"management " +"network,\" and an IP address on the \"data network\" that is used for " +"tunneling data traffic. For full details on configuring your forwarding " +"node, see the NVP Administrator Guide." +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking_introduction.xml931(para) +msgid "" +"Use the NVP Administrator Guide to add the node as a " +"\"Hypervisor\" using the NVP Manager GUI. Even if your forwarding node has " +"no VMs and is only used for services agents like neutron-dhcp-" +"agent or neutron-lbaas-agent, it " +"should still be added to NVP as a Hypervisor." +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking_introduction.xml944(para) +msgid "" +"After following the NVP Administrator Guide, use the " +"page for this Hypervisor in the NVP Manager GUI to confirm that the node is " +"properly connected to the NVP Controller Cluster and that the NVP Controller" +" Cluster can see the br-int integration bridge." +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking_introduction.xml957(title) +msgid "Node set up: Ryu plug-in" +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking_introduction.xml958(para) +msgid "" +"If you use the Ryu plug-in, you must install both Open vSwitch and Ryu, in " +"addition to the Ryu agent package:" +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking_introduction.xml962(title) +msgid "To set up each node for the Ryu plug-in" +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking_introduction.xml965(para) +msgid "Install Ryu (there isn't currently an Ryu package for ubuntu):" +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking_introduction.xml970(para) +msgid "Install the Ryu agent and Open vSwitch packages:" +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking_introduction.xml975(para) +msgid "" +"Replicate the ovs_ryu_plugin.ini and " +"neutron.conf files created in the above step on all " +"nodes running neutron-plugin-ryu-agent." +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking_introduction.xml993(para) +msgid "" +"All nodes running neutron-plugin-ryu-agent also " +"require that an OVS bridge named \"br-int\" exists on each node. To create " +"the bridge, run:" +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking_introduction.xml1004(title) +msgid "Configure DHCP agent" +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking_introduction.xml1005(para) +msgid "" +"The DHCP service agent is compatible with all existing plug-ins and is " +"required for all deployments where VMs should automatically receive IP " +"addresses through DHCP." +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking_introduction.xml1010(title) +msgid "To install and configure the DHCP agent" +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking_introduction.xml1013(para) +msgid "" +"You must configure the host running the neutron-dhcp-" +"agent as a \"data forwarding node\" according to the " +"requirements for your plug-in (see )." +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking_introduction.xml1021(para) +msgid "Install the DHCP agent:" +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking_introduction.xml1025(para) +msgid "" +"Finally, update any options in the " +"/etc/neutron/dhcp_agent.ini file that depend on the " +"plug-in in use (see the sub-sections)." +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking_introduction.xml1032(para) +msgid "" +"If you reboot a node that runs the DHCP agent, you must run the " +" command before the neutron-" +"dhcp-agent service starts." +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking_introduction.xml1036(para) +msgid "" +"On Red Hat-based systems, the neutron-ovs-" +"cleanup service runs the command automatically." +" However, on Debian-based systems such as Ubuntu, you must manually run this" +" command or write your own system script that runs on boot before the " +" neutron-dhcp-agent service " +"starts." +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking_introduction.xml1046(title) +msgid "DHCP agent setup: OVS plug-in" +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking_introduction.xml1047(para) +msgid "" +"These DHCP agent options are required in the " +"/etc/neutron/dhcp_agent.ini file for the OVS plug-in:" +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking_introduction.xml1057(title) +msgid "DHCP agent setup: NVP plug-in" +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking_introduction.xml1058(para) +msgid "" +"These DHCP agent options are required in the " +"/etc/neutron/dhcp_agent.ini file for the NVP plug-in:" +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking_introduction.xml1069(title) +msgid "DHCP agent setup: Ryu plug-in" +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking_introduction.xml1070(para) +msgid "" +"These DHCP agent options are required in the " +"/etc/neutron/dhcp_agent.ini file for the Ryu plug-in:" +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking_introduction.xml1080(title) +msgid "Configure L3 agent" +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking_introduction.xml1081(para) +msgid "" +"The OpenStack Networking Service has a widely used API extension to allow " +"administrators and tenants to create routers to interconnect L2 networks, " +"and floating IPs to make ports on private networks publicly accessible." +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking_introduction.xml1086(para) +msgid "" +"Many plug-ins rely on the L3 service agent to implement the L3 " +"functionality. However, the following plug-ins already have built-in L3 " +"capabilities:" +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking_introduction.xml1093(para) +msgid "Nicira NVP plug-in" +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking_introduction.xml1096(para) +msgid "" +"Big Switch/Floodlight plug-in, which supports both the open source Floodlight " +"controller and the proprietary Big Switch controller." +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking_introduction.xml1103(para) +msgid "" +"Only the proprietary BigSwitch controller implements L3 functionality. When " +"using Floodlight as your OpenFlow controller, L3 functionality is not " +"available." +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking_introduction.xml1112(para) +msgid "PLUMgrid plug-in" +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking_introduction.xml1116(para) +msgid "" +"Do not configure or use neutron-l3-agent if you use one" +" of these plug-ins." +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking_introduction.xml1121(title) +msgid "To install the L3 agent for all other plug-ins" +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking_introduction.xml1124(para) +msgid "" +"Install the neutron-l3-agent binary on the network " +"node:" +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking_introduction.xml1130(para) +msgid "" +"To uplink the node that runs neutron-l3-agent to " +"the external network, create a bridge named \"br-ex\" and attach the NIC for" +" the external network to this bridge." +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking_introduction.xml1136(para) +msgid "" +"For example, with Open vSwitch and NIC eth1 connected to the external " +"network, run:" +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking_introduction.xml1141(para) +msgid "" +"Do not manually configure an IP address on the NIC connected to the external" +" network for the node running neutron-l3-agent. " +"Rather, you must have a range of IP addresses from the external network that" +" can be used by OpenStack Networking for routers that uplink to the external" +" network. This range must be large enough to have an IP address for each " +"router in the deployment, as well as each floating IP." +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking_introduction.xml1155(para) +msgid "" +"The neutron-l3-agent uses the Linux IP stack and " +"iptables to perform L3 forwarding and NAT. In order to support multiple " +"routers with potentially overlapping IP addresses, " +"neutron-l3-agent defaults to using Linux network " +"namespaces to provide isolated forwarding contexts. As a result, the IP " +"addresses of routers will not be visible simply by running " +"or on the node. Similarly, you will not be able to directly" +" fixed IPs." +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking_introduction.xml1172(para) +msgid "" +"To do either of these things, you must run the command within a particular " +"router's network namespace. The namespace will have the name " +"\"qrouter-<UUID of the router>. These example commands run in the " +"router namespace with UUID 47af3868-0fa8-4447-85f6-1304de32153b:" +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking_introduction.xml1186(para) +msgid "" +"If you reboot a node that runs the L3 agent, you must run the " +" command before the neutron-l3-agent service starts." +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking_introduction.xml1189(para) +msgid "" +"On Red Hat-based systems, the neutron-ovs-" +"cleanup service runs the command " +"automatically. However, on Debian-based systems such as Ubuntu, you must " +"manually run this command or write your own system script that runs on boot " +"before the neutron-l3-agent " +"service starts." +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking_introduction.xml1199(title) +msgid "Configure LBaaS agent" +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking_introduction.xml1200(para) +msgid "" +"Starting with the Havana release, the Neutron Load-Balancer-as-a-Service " +"(LBaaS) supports an agent scheduling mechanism, so several neutron-lbaas-agents can be run on several nodes (one per " +"one)." +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking_introduction.xml1206(title) +msgid "To install the LBaas agent and configure the node" +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking_introduction.xml1209(para) +msgid "Install the agent by running:" +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking_introduction.xml1215(para) +msgid "" +"An OVS-based plug-in (OVS, NVP, Ryu, NEC, BigSwitch/Floodlight), you must " +"set:" +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking_introduction.xml1222(para) +msgid "A plug-in that uses LinuxBridge, you must set:" +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking_introduction.xml1213(para) +msgid "If you are using: " +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking_introduction.xml1229(para) +msgid "To use the reference implementation, you must also set:" +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking_introduction.xml1234(para) +#: ./doc/admin-guide-cloud/section_networking_introduction.xml1255(para) +msgid "" +"Set this parameter in the neutron.conf file on the host" +" that runs neutron-server:" +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking_introduction.xml1244(title) +msgid "Configure FWaaS agent" +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking_introduction.xml1245(para) +msgid "" +"The Firewall-as-a-Service (FWaaS) agent is co-located with the Neutron L3 " +"agent and does not require any additional packages apart from those required" +" for the Neutron L3 agent. You can enable the FWaaS functionality by setting" +" the configuration, as follows." +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking_introduction.xml1252(title) +msgid "To configure FWaaS service and agent" +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking_introduction.xml1263(para) +msgid "" +"To use the reference implementation, you must also add a FWaaS driver " +"configuration to the neutron.conf file on every node " +"where the Neutron L3 agent is deployed:" +msgstr "" + +#: ./doc/admin-guide-cloud/ch_identity_mgmt.xml7(title) +msgid "Identity management" +msgstr "" + +#: ./doc/admin-guide-cloud/ch_identity_mgmt.xml8(para) +msgid "" +"The OpenStack Identity Service, code-named Keystone, is the default identity" +" management system for OpenStack. After you install the Identity Service, " +"you configure it through the etc/keystone.conf " +"configuration file and, possibly, a separate logging configuration file. You" +" initialize data into the Identity Service by using the " +"command-line client." +msgstr "" + +#: ./doc/admin-guide-cloud/ch_identity_mgmt.xml16(title) +msgid "Identity Service concepts" +msgstr "" + +#: ./doc/admin-guide-cloud/ch_identity_mgmt.xml32(title) +msgid "User CRUD" +msgstr "" + +#: ./doc/admin-guide-cloud/ch_identity_mgmt.xml33(para) +msgid "" +"The Identity Service provides a user CRUD filter that can be added to the " +"public_api pipeline. This user CRUD filter enables users to use a HTTP PATCH" +" to change their own password. To enable this extension you should define a " +"user_crud_extension filter, insert it after the " +"*_body middleware and before the " +"public_service application in the public_api WSGI " +"pipeline in keystone.conf. For example:" +msgstr "" + +#: ./doc/admin-guide-cloud/ch_identity_mgmt.xml47(para) +msgid "Each user can then change their own password with a HTTP PATCH:" +msgstr "" + +#: ./doc/admin-guide-cloud/ch_identity_mgmt.xml50(para) +msgid "" +"In addition to changing their password, all of the user's current tokens are" +" deleted (if the back-end is KVS or sql)." +msgstr "" + +#: ./doc/admin-guide-cloud/ch_identity_mgmt.xml52(para) +msgid "Only use a KVS backend for tokens when testing." +msgstr "" + +#: ./doc/admin-guide-cloud/ch_identity_mgmt.xml55(title) +msgid "Logging" +msgstr "" + +#: ./doc/admin-guide-cloud/ch_identity_mgmt.xml56(para) +msgid "" +"You configure logging externally to the rest of the Identity Service. The " +"file specifying the logging configuration is in the " +"[DEFAULT] section of the " +"keystone.conf file under log_config." +" To route logging through syslog, set use_syslog=true " +"option in the [DEFAULT] section." +msgstr "" + +#: ./doc/admin-guide-cloud/ch_identity_mgmt.xml63(para) +msgid "" +"A sample logging file is available with the project in the " +"etc/logging.conf.sample directory. Like other OpenStack" +" projects, the Identity Service uses the Python logging module, which " +"includes extensive configuration options that let you define the output " +"levels and formats." +msgstr "" + +#: ./doc/admin-guide-cloud/ch_identity_mgmt.xml68(para) +msgid "" +"Review the etc/keystone.conf sample configuration files" +" that are distributed with the Identity Service. For example, each server " +"application has its own configuration file." +msgstr "" + +#: ./doc/admin-guide-cloud/ch_identity_mgmt.xml72(para) +msgid "" +"For services that have separate paste-deploy .ini " +"files, you can configure auth_token middleware in the " +"[keystone_authtoken] section in the main configuration " +"file, such as nova.conf. For example in Compute, you " +"can remove the middleware parameters from api-" +"paste.ini, as follows:" +msgstr "" + +#: ./doc/admin-guide-cloud/ch_identity_mgmt.xml82(para) +msgid "Set these values in the nova.conf file:" +msgstr "" + +#: ./doc/admin-guide-cloud/ch_identity_mgmt.xml97(para) +msgid "" +"Middleware parameters in paste config take priority. You must remove them to" +" use values in the [keystone_authtoken] section." +msgstr "" + +#: ./doc/admin-guide-cloud/ch_identity_mgmt.xml103(title) +msgid "Monitoring" +msgstr "" + +#: ./doc/admin-guide-cloud/ch_identity_mgmt.xml104(para) +msgid "" +"The Identity Service provides some basic request/response monitoring " +"statistics out of the box." +msgstr "" + +#: ./doc/admin-guide-cloud/ch_identity_mgmt.xml106(para) +msgid "" +"Enable data collection by defining a stats_monitoring " +"filter and including it at the beginning of any desired WSGI pipelines:" +msgstr "" + +#: ./doc/admin-guide-cloud/ch_identity_mgmt.xml114(para) +msgid "" +"Enable the reporting of collected data by defining a " +"stats_reporting filter and including it near the end of " +"your admin_api WSGI pipeline (After " +"*_body middleware and before " +"*_extension filters is recommended):" +msgstr "" + +#: ./doc/admin-guide-cloud/ch_identity_mgmt.xml124(para) +msgid "Query the admin API for statistics using:" +msgstr "" + +#: ./doc/admin-guide-cloud/ch_identity_mgmt.xml126(para) +msgid "Reset collected data using:" +msgstr "" + +#: ./doc/admin-guide-cloud/ch_identity_mgmt.xml131(title) +msgid "Start the Identity Service" +msgstr "" + +#: ./doc/admin-guide-cloud/ch_identity_mgmt.xml132(para) +msgid "" +"To start the services for the Identity Service, run the following command:" +msgstr "" + +#: ./doc/admin-guide-cloud/ch_identity_mgmt.xml135(para) +msgid "" +"This command starts two wsgi.Server instances configured by the " +"keystone.conf file as described previously. One of " +"these wsgi servers is admin (the administration API) and " +"the other is main (the primary/public API interface). " +"Both run in a single process." +msgstr "" + +#: ./doc/admin-guide-cloud/ch_identity_mgmt.xml143(title) +msgid "Example usage" +msgstr "" + +#: ./doc/admin-guide-cloud/ch_identity_mgmt.xml144(para) +msgid "" +"The keystone client is set up to expect commands in the " +"general form of " +"keystonecommandargument," +" followed by flag-like keyword arguments to provide additional (often " +"optional) information. For example, the command user-list" +" and tenant-create can be invoked as follows:" +msgstr "" + +#: ./doc/admin-guide-cloud/ch_identity_mgmt.xml174(title) +msgid "Authentication middleware with user name and password" +msgstr "" + +#: ./doc/admin-guide-cloud/ch_identity_mgmt.xml176(para) +msgid "" +"You can also configure the Identity Service authentication middleware using " +"the and options." +" When using the and " +" options the " +"parameter is optional. If is specified, it is " +"used only if the specified token is still valid." +msgstr "" + +#: ./doc/admin-guide-cloud/ch_identity_mgmt.xml184(para) +msgid "" +"For services that have a separate paste-deploy .ini file, you can configure " +"the authentication middleware in the [keystone_authtoken]" +" section of the main configuration file, such as " +"nova.conf. In Compute, for example, you can remove the " +"middleware parameters from api-paste.ini, as follows:" +msgstr "" + +#: ./doc/admin-guide-cloud/ch_identity_mgmt.xml193(para) +msgid "" +"And set the following values in nova.conf as follows:" +msgstr "" + +#: ./doc/admin-guide-cloud/ch_identity_mgmt.xml208(para) +msgid "" +"The middleware parameters in the paste config take priority. You must remove" +" them to use the values in the [keystone_authtoken] section." +msgstr "" + +#: ./doc/admin-guide-cloud/ch_identity_mgmt.xml212(para) +msgid "" +"This sample paste config filter makes use of the " +" and options:" +msgstr "" + +#: ./doc/admin-guide-cloud/ch_identity_mgmt.xml225(para) +msgid "" +"Using this option requires an admin tenant/role relationship. The admin user" +" is granted access to the admin role on the admin tenant." +msgstr "" + +#: ./doc/admin-guide-cloud/section_ts_failed_sched_create_vol.xml4(title) +msgid "Failed to schedule and create volume" +msgstr "" + +#: ./doc/admin-guide-cloud/section_ts_failed_sched_create_vol.xml6(title) +#: ./doc/admin-guide-cloud/section_ts_failed_connect_vol_FC_SAN.xml6(title) +#: ./doc/admin-guide-cloud/section_ts_vol_attach_miss_sg_scan.xml10(title) +#: ./doc/admin-guide-cloud/section_ts_failed_attach_vol_after_detach.xml8(title) +#: ./doc/admin-guide-cloud/section_ts_non_existent_host.xml6(title) +#: ./doc/admin-guide-cloud/section_ts_no_emulator_x86_64.xml6(title) +#: ./doc/admin-guide-cloud/section_ts_HTTP_bad_req_in_cinder_vol_log.xml8(title) +#: ./doc/admin-guide-cloud/section_ts_non_existent_vlun.xml6(title) +#: ./doc/admin-guide-cloud/section_ts_failed_attach_vol_no_sysfsutils.xml6(title) +#: ./doc/admin-guide-cloud/section_ts_multipath_warn.xml8(title) +#: ./doc/admin-guide-cloud/section_ts_attach_vol_fail_not_JSON.xml7(title) +#: ./doc/admin-guide-cloud/section_ts_duplicate_3par_host.xml6(title) +msgid "Problem" +msgstr "" + +#: ./doc/admin-guide-cloud/section_ts_failed_sched_create_vol.xml7(para) +msgid "" +"The following warning is seen in the cinder-" +"scheduler.log when volume type and extra specs are defined and " +"the volume is in an error state." +msgstr "" + +#: ./doc/admin-guide-cloud/section_ts_failed_sched_create_vol.xml14(title) +#: ./doc/admin-guide-cloud/section_ts_failed_connect_vol_FC_SAN.xml15(title) +#: ./doc/admin-guide-cloud/section_ts_vol_attach_miss_sg_scan.xml24(title) +#: ./doc/admin-guide-cloud/section_ts_failed_attach_vol_after_detach.xml14(title) +#: ./doc/admin-guide-cloud/section_ts_non_existent_host.xml14(title) +#: ./doc/admin-guide-cloud/section_ts_no_emulator_x86_64.xml11(title) +#: ./doc/admin-guide-cloud/section_ts_HTTP_bad_req_in_cinder_vol_log.xml43(title) +#: ./doc/admin-guide-cloud/section_ts_non_existent_vlun.xml12(title) +#: ./doc/admin-guide-cloud/section_ts_failed_attach_vol_no_sysfsutils.xml15(title) +#: ./doc/admin-guide-cloud/section_ts_multipath_warn.xml20(title) +#: ./doc/admin-guide-cloud/section_ts_attach_vol_fail_not_JSON.xml15(title) +#: ./doc/admin-guide-cloud/section_ts_duplicate_3par_host.xml12(title) +msgid "Solution" +msgstr "" + +#: ./doc/admin-guide-cloud/section_ts_failed_sched_create_vol.xml15(para) +msgid "" +"Enable the option " +"scheduler_driver=cinder.scheduler.simple.SimpleScheduler" +" in the /etc/cinder/cinder.conf file and restart the " +"cinder-scheduler service. The " +"scheduler_driver defaults to " +"cinder.scheduler.filter_scheduler.FilterScheduler." +msgstr "" + +#. When image changes, this message will be marked fuzzy or untranslated for +#. you. +#. It doesn't matter what you translate it to: it's not used at all. +#: ./doc/admin-guide-cloud/section_networking-multi-dhcp-agents.xml32(None) +msgid "" +"@@image: '../common/figures/demo_multiple_dhcp_agents.png'; " +"md5=7e9abc4226d6b6cb9a6a3b3ec7435805" +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking-multi-dhcp-agents.xml6(title) +msgid "Scalable and highly available DHCP agents" +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking-multi-dhcp-agents.xml7(para) +msgid "" +"This section describes how to use the agent management (alias agent) and " +"scheduler (alias agent_scheduler) extensions for DHCP agents scalability and" +" HA." +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking-multi-dhcp-agents.xml11(para) +msgid "" +"Use the client command to check if these extensions are " +"enabled: " +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking-multi-dhcp-agents.xml47(para) +msgid "" +"Runs the Neutron, Keystone, and Nova services that are required to deploy " +"VMs. The node must have at least one network interface that is connected to " +"the Management Network." +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking-multi-dhcp-agents.xml52(para) +msgid "" +"Note that nova-network should not" +" be running because it is replaced by Neutron." +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking-multi-dhcp-agents.xml35(para) +msgid "" +"There will be three hosts in the setup.
Hosts " +"for " +"demo
HostDescription
OpenStack" +" Controller host - " +"controlnode
HostARuns Nova " +"compute, the Neutron L2 agent and DHCP " +"agent
HostBSame as HostA
" +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking-multi-dhcp-agents.xml71(title) +#: ./doc/admin-guide-cloud/section_networking-scenarios.xml15(title) +#: ./doc/admin-guide-cloud/section_networking-scenarios.xml383(title) +#: ./doc/admin-guide-cloud/section_networking-config-identity.xml146(th) +#: ./doc/admin-guide-cloud/section_networking-config-identity.xml221(td) +#: ./doc/admin-guide-cloud/section_networking-config-identity.xml256(td) +msgid "Configuration" +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking-multi-dhcp-agents.xml73(title) +msgid "controlnode—Neutron Server" +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking-multi-dhcp-agents.xml75(para) +#: ./doc/admin-guide-cloud/section_networking-multi-dhcp-agents.xml100(para) +msgid "" +"Neutron configuration file /etc/neutron/neutron.conf:" +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking-multi-dhcp-agents.xml85(para) +#: ./doc/admin-guide-cloud/section_networking-multi-dhcp-agents.xml109(para) +msgid "" +"Update the plug-in configuration file " +"/etc/neutron/plugins/linuxbridge/linuxbridge_conf.ini:" +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking-multi-dhcp-agents.xml98(title) +msgid "HostA and HostB—L2 Agent" +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking-multi-dhcp-agents.xml121(para) +msgid "" +"Update the nova configuration file /etc/nova/nova.conf:" +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking-multi-dhcp-agents.xml136(title) +msgid "HostA and HostB—DHCP Agent" +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking-multi-dhcp-agents.xml138(para) +msgid "" +"Update the DHCP configuration file " +"/etc/neutron/dhcp_agent.ini:" +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking-multi-dhcp-agents.xml146(title) +msgid "Commands in agent management and scheduler extensions" +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking-multi-dhcp-agents.xml148(para) +msgid "" +"The following commands require the tenant running the command to have an " +"admin role." +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking-multi-dhcp-agents.xml151(para) +msgid "" +"Ensure that the following environment variables are set. These are used by " +"the various clients to access Keystone." +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking-multi-dhcp-agents.xml160(title) +#: ./doc/admin-guide-cloud/section_networking-adv-config.xml68(caption) +msgid "Settings" +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking-multi-dhcp-agents.xml161(para) +msgid "To experiment, you need VMs and a neutron network:" +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking-multi-dhcp-agents.xml181(title) +msgid "Manage agents in neutron deployment" +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking-multi-dhcp-agents.xml182(para) +msgid "" +"Every agent which supports these extensions will register itself with the " +"neutron server when it starts up." +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking-multi-dhcp-agents.xml186(para) +msgid "List all agents:" +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking-multi-dhcp-agents.xml197(para) +msgid "" +"The output shows information for four agents. The alive " +"field shows :-) if the agent reported its state within " +"the period defined by the option in the " +"neutron.conf file. Otherwise the " +" is xxx." +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking-multi-dhcp-agents.xml209(para) +msgid "List the DHCP agents that host a specified network" +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking-multi-dhcp-agents.xml211(para) +msgid "" +"In some deployments, one DHCP agent is not enough to hold all network data. " +"In addition, you must have a backup for it even when the deployment is " +"small. The same network can be assigned to more than one DHCP agent and one " +"DHCP agent can host more than one network." +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking-multi-dhcp-agents.xml218(para) +msgid "List DHCP agents that a a specified network:" +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking-multi-dhcp-agents.xml229(para) +msgid "List the networks hosted by a given DHCP agent." +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking-multi-dhcp-agents.xml231(para) +msgid "This command is to show which networks a given dhcp agent is managing." +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking-multi-dhcp-agents.xml242(para) +msgid "Show agent details." +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking-multi-dhcp-agents.xml243(para) +msgid "The command shows details for a specified agent:" +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking-multi-dhcp-agents.xml271(para) +msgid "" +"In this output, heartbeat_timestamp is the time on the " +"neutron server. You do not need to synchronize all agents to this time for " +"this extension to run correctly. configurations describes" +" the static configuration for the agent or run time data. This agent is a " +"DHCP agent and it hosts one network, one subnet, and three ports." +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking-multi-dhcp-agents.xml281(para) +msgid "" +"Different types of agents show different details. The following output shows" +" information for a Linux bridge agent:" +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking-multi-dhcp-agents.xml306(para) +msgid "" +"The output shows bridge-mapping and the number of virtual" +" network devices on this L2 agent." +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking-multi-dhcp-agents.xml313(title) +msgid "Manage assignment of networks to DHCP agent" +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking-multi-dhcp-agents.xml314(para) +msgid "" +"Now that you have run the and commands, " +"you can add a network to a DHCP agent and remove one from it." +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking-multi-dhcp-agents.xml320(para) +msgid "Default scheduling." +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking-multi-dhcp-agents.xml321(para) +msgid "" +"When you create a network with one port, you can schedule it to an active " +"DHCP agent. If many active DHCP agents are running, select one randomly. You" +" can design more sophisticated scheduling algorithms in the same way as " +"nova-schedule later on." +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking-multi-dhcp-agents.xml339(para) +msgid "" +"It is allocated to DHCP agent on HostA. If you want to validate the behavior" +" through the command, you must create a subnet for the " +"network because the DHCP agent starts the dnsmasq service only if there is a DHCP." +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking-multi-dhcp-agents.xml349(para) +msgid "Assign a network to a given DHCP agent." +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking-multi-dhcp-agents.xml351(para) +msgid "To add another DHCP agent to host the network, run this command:" +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking-multi-dhcp-agents.xml362(para) +msgid "Both DHCP agents host the net2 network." +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking-multi-dhcp-agents.xml367(para) +msgid "Remove a network from a specified DHCP agent." +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking-multi-dhcp-agents.xml369(para) +msgid "" +"This command is the sibling command for the previous one. Remove " +"net2 from the DHCP agent for HostA:" +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking-multi-dhcp-agents.xml381(para) +msgid "" +"You can see that only the DHCP agent for HostB is hosting the " +"net2 network." +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking-multi-dhcp-agents.xml388(title) +msgid "HA of DHCP agents" +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking-multi-dhcp-agents.xml389(para) +msgid "" +"Boot a VM on net2. Let both DHCP agents host net2. Fail " +"the agents in turn to see if the VM can still get the desired IP." +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking-multi-dhcp-agents.xml394(para) +msgid "Boot a VM on net2." +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking-multi-dhcp-agents.xml415(para) +msgid "Make sure both DHCP agents hosting 'net2'." +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking-multi-dhcp-agents.xml417(para) +msgid "Use the previous commands to assign the network to agents." +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking-multi-dhcp-agents.xml429(title) +msgid "Test the HA" +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking-multi-dhcp-agents.xml431(para) +msgid "" +"Log in to the myserver4 VM, and run " +"udhcpc, dhclient or other DHCP client." +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking-multi-dhcp-agents.xml438(para) +msgid "" +"Stop the DHCP agent on HostA. Besides stopping the neutron-dhcp-" +"agent binary, you must stop the processes." +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking-multi-dhcp-agents.xml446(para) +msgid "Run a DHCP client in VM to see if it can get the wanted IP." +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking-multi-dhcp-agents.xml451(para) +msgid "Stop the DHCP agent on HostB too." +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking-multi-dhcp-agents.xml455(para) +msgid "Run in the VM; it cannot get the wanted IP." +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking-multi-dhcp-agents.xml460(para) +msgid "Start DHCP agent on HostB. The VM gets the wanted IP again." +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking-multi-dhcp-agents.xml465(title) +msgid "Disable and remove an agent" +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking-multi-dhcp-agents.xml466(para) +msgid "" +"An administrator might want to disable an agent if a system hardware or " +"software upgrade is planned. Some agents that support scheduling also " +"support disabling and enabling agents, such as L3 and DHCP agents. After the" +" agent is disabled, the scheduler does not schedule new resources to the " +"agent. After the agent is disabled, you can safely remove the agent. Remove " +"the resources on the agent before you delete the agent." +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking-multi-dhcp-agents.xml475(para) +msgid "To run the following commands, you must stop the DHCP agent on HostA." +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking-multi-dhcp-agents.xml497(para) +msgid "" +"After deletion, if you restart the DHCP agent, it appears on the agent list " +"again." +msgstr "" + +#: ./doc/admin-guide-cloud/section_rootwrap.xml6(title) +msgid "Secure with root wrappers" +msgstr "" + +#: ./doc/admin-guide-cloud/section_rootwrap.xml7(para) +msgid "" +"The root wrapper enables the Compute unprivileged user to run a number of " +"actions as the root user in the safest manner possible. Historically, " +"Compute used a specific sudoers file that listed every " +"command that the Compute user was allowed to run, and used " +"to run that command as root. However this was difficult " +"to maintain (the sudoers file was in packaging), and " +"did not enable complex filtering of parameters (advanced filters). The " +"rootwrap was designed to solve those issues." +msgstr "" + +#: ./doc/admin-guide-cloud/section_rootwrap.xml19(title) +msgid "How rootwrap works" +msgstr "" + +#: ./doc/admin-guide-cloud/section_rootwrap.xml20(para) +msgid "" +"Instead of calling , Compute services start with nova- call " +". A generic sudoers entry lets the Compute user run nova-" +"rootwrap as root. The nova-rootwrap code looks for filter definition " +"directories in its configuration file, and loads command filters from them. " +"Then it checks if the command requested by Compute matches one of those " +"filters, in which case it executes the command (as root). If no filter " +"matches, it denies the request." +msgstr "" + +#: ./doc/admin-guide-cloud/section_rootwrap.xml33(title) +msgid "Security model" +msgstr "" + +#: ./doc/admin-guide-cloud/section_rootwrap.xml34(para) +msgid "" +"The escalation path is fully controlled by the root user. A sudoers entry " +"(owned by root) allows Compute to run (as root) a specific rootwrap " +"executable, and only with a specific configuration file (which should be " +"owned by root). nova-rootwrap imports the Python modules it needs from a " +"cleaned (and system-default) PYTHONPATH. The configuration file (also root-" +"owned) points to root-owned filter definition directories, which contain " +"root-owned filters definition files. This chain ensures that the Compute " +"user itself is not in control of the configuration or modules used by the " +"nova-rootwrap executable." +msgstr "" + +#: ./doc/admin-guide-cloud/section_rootwrap.xml47(title) +msgid "Details of rootwrap.conf" +msgstr "" + +#: ./doc/admin-guide-cloud/section_rootwrap.xml48(para) +msgid "" +"You configure nova-rootwrap in the rootwrap.conf file. " +"Because it's in the trusted security path, it must be owned and writable by " +"only the root user. Its location is specified both in the sudoers entry and " +"in the nova.conf configuration file with the " +"rootwrap_config=entry." +msgstr "" + +#: ./doc/admin-guide-cloud/section_rootwrap.xml55(para) +msgid "It uses an INI file format with these sections and parameters:" +msgstr "" + +#: ./doc/admin-guide-cloud/section_rootwrap.xml59(caption) +#: ./doc/admin-guide-cloud/section_rootwrap.xml98(caption) +msgid "rootwrap.conf configuration options" +msgstr "" + +#: ./doc/admin-guide-cloud/section_rootwrap.xml64(para) +#: ./doc/admin-guide-cloud/section_rootwrap.xml103(para) +msgid "Configuration option=Default value" +msgstr "" + +#: ./doc/admin-guide-cloud/section_rootwrap.xml66(para) +#: ./doc/admin-guide-cloud/section_rootwrap.xml105(para) +msgid "(Type) Description" +msgstr "" + +#: ./doc/admin-guide-cloud/section_rootwrap.xml71(para) +msgid "[DEFAULT]" +msgstr "" + +#: ./doc/admin-guide-cloud/section_rootwrap.xml72(para) +msgid "filters_path=/etc/nova/rootwrap.d,/usr/share/nova/rootwrap" +msgstr "" + +#: ./doc/admin-guide-cloud/section_rootwrap.xml74(para) +msgid "" +"(ListOpt) Comma-separated list of directories containing filter definition " +"files. Defines where filters for root wrap are stored. Directories defined " +"on this line should all exist, be owned and writable only by the root user." +msgstr "" + +#: ./doc/admin-guide-cloud/section_rootwrap.xml86(title) +msgid "Details of .filters files" +msgstr "" + +#: ./doc/admin-guide-cloud/section_rootwrap.xml87(para) +msgid "" +"Filters definition files contain lists of filters that nova-rootwrap will " +"use to allow or deny a specific command. They are generally suffixed by " +".filters. Since they are in the trusted security path, they need to be owned" +" and writable only by the root user. Their location is specified in the " +"rootwrap.conf file." +msgstr "" + +#: ./doc/admin-guide-cloud/section_rootwrap.xml93(para) +msgid "" +"It uses an INI file format with a [Filters] section and several lines, each " +"with a unique parameter name (different for each filter that you define):" +msgstr "" + +#: ./doc/admin-guide-cloud/section_rootwrap.xml110(para) +msgid "[Filters]" +msgstr "" + +#: ./doc/admin-guide-cloud/section_rootwrap.xml111(para) +msgid "filter_name=kpartx: CommandFilter, /sbin/kpartx, root" +msgstr "" + +#: ./doc/admin-guide-cloud/section_rootwrap.xml113(para) +msgid "" +"(ListOpt) Comma-separated list containing first the Filter class to use, " +"followed by that Filter arguments (which vary depending on the Filter class " +"selected)." +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking_auth.xml6(title) +msgid "Authentication and authorization" +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking_auth.xml7(para) +msgid "" +"Networking uses the Identity Service as the default authentication service. " +"When the Identity Service is enabled, users who submit requests to the " +"Networking service must provide an authentication token in X-Auth-" +"Token request header. Users obtain this token by authenticating " +"with the Identity Service endpoint. For more information about " +"authentication with the Identity Service, see OpenStack Identity Service API v2.0 " +"Reference. When the Identity Service is enabled, it is " +"not mandatory to specify the tenant ID for resources in create requests " +"because the tenant ID is derived from the authentication token." +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking_auth.xml22(para) +msgid "" +"The default authorization settings only allow administrative users to create" +" resources on behalf of a different tenant. Networking uses information " +"received from Identity to authorize user requests. Networking handles two " +"kind of authorization policies:" +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking_auth.xml31(para) +msgid "" +"Operation-based policies specify access " +"criteria for specific operations, possibly with fine-grained control over " +"specific attributes;" +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking_auth.xml37(para) +msgid "" +"Resource-based policies specify whether " +"access to specific resource is granted or not according to the permissions " +"configured for the resource (currently available only for the network " +"resource). The actual authorization policies enforced in Networking might " +"vary from deployment to deployment." +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking_auth.xml47(para) +msgid "" +"The policy engine reads entries from the policy.json " +"file. The actual location of this file might vary from distribution to " +"distribution. Entries can be updated while the system is running, and no " +"service restart is required. Every time the policy file is updated, the " +"policies are automatically reloaded. Currently the only way of updating such" +" policies is to edit the policy file. In this section, the terms policy and rule refer to objects that are specified in the " +"same way in the policy file. There are no syntax differences between a rule " +"and a policy. A policy is something that is matched directly from the " +"Networking policy engine. A rule is an element in a policy, which is " +"evaluated. For instance in create_subnet: " +"[[\"admin_or_network_owner\"]], create_subnet is a policy, and admin_or_network_owner is a rule." +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking_auth.xml67(para) +msgid "" +"Policies are triggered by the Networking policy engine whenever one of them " +"matches an Networking API operation or a specific attribute being used in a " +"given operation. For instance the create_subnet policy is " +"triggered every time a POST /v2.0/subnets request is sent to " +"the Networking server; on the other hand create_network:shared " +"is triggered every time the shared " +"attribute is explicitly specified (and set to a value different from its " +"default) in a POST /v2.0/networks request. It is also worth " +"mentioning that policies can be also related to specific API extensions; for" +" instance extension:provider_network:set is be triggered if the" +" attributes defined by the Provider Network extensions are specified in an " +"API request." +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking_auth.xml83(para) +msgid "" +"An authorization policy can be composed by one or more rules. If more rules " +"are specified, evaluation policy succeeds if any of the rules evaluates " +"successfully; if an API operation matches multiple policies, then all the " +"policies must evaluate successfully. Also, authorization rules are " +"recursive. Once a rule is matched, the rule(s) can be resolved to another " +"rule, until a terminal rule is reached." +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking_auth.xml91(para) +msgid "" +"The Networking policy engine currently defines the following kinds of " +"terminal rules:" +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking_auth.xml95(para) +msgid "" +"Role-based rules evaluate successfully if" +" the user who submits the request has the specified role. For instance " +"\"role:admin\" is successful if the user who submits the " +"request is an administrator." +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking_auth.xml103(para) +msgid "" +"Field-based rules evaluate successfully " +"if a field of the resource specified in the current request matches a " +"specific value. For instance \"field:networks:shared=True\" is " +"successful if the shared attribute of the " +"network resource is set to true." +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking_auth.xml113(para) +msgid "" +"Generic rules compare an attribute in the" +" resource with an attribute extracted from the user's security credentials " +"and evaluates successfully if the comparison is successful. For instance " +"\"tenant_id:%(tenant_id)s\" is successful if the tenant " +"identifier in the resource is equal to the tenant identifier of the user " +"submitting the request." +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking_auth.xml124(para) +msgid "" +"This extract is from the default policy.json file:" +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking_auth.xml148(para) +msgid "" +"[1] is a rule which evaluates successfully if the current user is an " +"administrator or the owner of the resource specified in the request (tenant " +"identifier is equal)." +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking_auth.xml152(para) +msgid "" +"[2] is the default policy which is always evaluated if an API operation does" +" not match any of the policies in policy.json." +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking_auth.xml155(para) +msgid "" +"[3] This policy evaluates successfully if either admin_or_owner, or shared evaluates successfully." +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking_auth.xml159(para) +msgid "" +"[4] This policy restricts the ability to manipulate the shared attribute for a network to administrators " +"only." +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking_auth.xml162(para) +msgid "" +"[5] This policy restricts the ability to manipulate the mac_address attribute for a port only to " +"administrators and the owner of the network where the port is attached." +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking_auth.xml166(para) +msgid "" +"In some cases, some operations are restricted to administrators only. This " +"example shows you how to modify a policy file to permit tenants to define " +"networks and see their resources and permit administrative users to perform " +"all other operations:" +msgstr "" + +#: ./doc/admin-guide-cloud/section_ts_cinder_config.xml7(title) +msgid "Troubleshoot the Block Storage configuration" +msgstr "" + +#: ./doc/admin-guide-cloud/section_ts_cinder_config.xml9(para) +msgid "" +"This section helps you solve some basic and common errors that you might " +"encounter during setup and configuration of the Block Storage Service. The " +"focus here is on failed creation of volumes. The most important thing to " +"know is where to look in case of a failure." +msgstr "" + +#: ./doc/admin-guide-cloud/section_ts_cinder_config.xml14(para) +msgid "" +"Two log files are especially helpful for solving volume creation failures, " +"the cinder-api log and the " +"cinder-volume log. The " +"cinder-api log is useful for " +"determining if you have endpoint or connectivity issues. If you send a " +"request to create a volume and it fails, review the cinder-api log to determine whether the " +"request made it to the Block Storage service. If the request is logged and " +"you see no errors or trace-backs, check the cinder-volume log for errors or trace-backs." +msgstr "" + +#: ./doc/admin-guide-cloud/section_ts_cinder_config.xml28(para) +msgid "" +"Create commands are listed in the cinder-" +"api log." +msgstr "" + +#: ./doc/admin-guide-cloud/section_ts_cinder_config.xml31(para) +msgid "" +"These entries in the cinder.openstack.common.log file " +"can be used to assist in troubleshooting your block storage configuration." +msgstr "" + +#: ./doc/admin-guide-cloud/section_ts_cinder_config.xml103(para) +msgid "" +"These common issues might occur during configuration. To correct, use these " +"suggested solutions." +msgstr "" + +#: ./doc/admin-guide-cloud/section_ts_cinder_config.xml107(para) +msgid "" +"Issues with state_path and volumes_dir" +" settings." +msgstr "" + +#: ./doc/admin-guide-cloud/section_ts_cinder_config.xml109(para) +msgid "" +"The OpenStack Block Storage uses as the default iscsi " +"helper and implements persistent targets. This means that in the case of a " +"tgt restart or even a node reboot your existing volumes on that node will be" +" restored automatically with their original IQN." +msgstr "" + +#: ./doc/admin-guide-cloud/section_ts_cinder_config.xml114(para) +msgid "" +"In order to make this possible the iSCSI target information needs to be " +"stored in a file on creation that can be queried in case of restart of the " +"tgt daemon. By default, Block Storage uses a state_path " +"variable, which if installing with Yum or APT should be set to " +"/var/lib/cinder/. The next part is the " +"volumes_dir variable, by default this just simply appends" +" a \"volumes\" directory to the " +"state_path. The result is a file-tree " +"/var/lib/cinder/volumes/." +msgstr "" + +#: ./doc/admin-guide-cloud/section_ts_cinder_config.xml127(para) +msgid "" +"While this should all be handled by the installer, it can go wrong. If you " +"have trouble creating volumes and this directory does not exist you should " +"see an error message in the cinder-" +"volume log indicating that the volumes_dir " +"does not exist, and it should provide information about which path it was " +"looking for." +msgstr "" + +#: ./doc/admin-guide-cloud/section_ts_cinder_config.xml137(para) +msgid "The persistent tgt include file." +msgstr "" + +#: ./doc/admin-guide-cloud/section_ts_cinder_config.xml138(para) +msgid "" +"Along with the option, the iSCSI target driver " +"also needs to be configured to look in the correct place for the persist " +"files. This is a simple entry in the /etc/tgt/conf.d " +"file that you should have set when you installed OpenStack. If issues occur," +" verify that you have a /etc/tgt/conf.d/cinder.conf " +"file." +msgstr "" + +#: ./doc/admin-guide-cloud/section_ts_cinder_config.xml147(para) +msgid "If the file is not present, create it with this command:" +msgstr "" + +#: ./doc/admin-guide-cloud/section_ts_cinder_config.xml152(para) +msgid "" +"No sign of attach call in the cinder-" +"api log." +msgstr "" + +#: ./doc/admin-guide-cloud/section_ts_cinder_config.xml155(para) +msgid "" +"This is most likely going to be a minor adjustment to your " +"nova.conf file. Make sure that your " +"nova.conf has this entry:" +msgstr "" + +#: ./doc/admin-guide-cloud/section_ts_cinder_config.xml162(para) +msgid "" +"Failed to create iscsi target error in the cinder-" +"volume.log file." +msgstr "" + +#: ./doc/admin-guide-cloud/section_ts_cinder_config.xml166(para) +msgid "" +"You might see this error in cinder-volume.log after " +"trying to create a volume that is 1 GB. To fix this issue:" +msgstr "" + +#: ./doc/admin-guide-cloud/section_ts_cinder_config.xml170(para) +msgid "" +"Change content of the /etc/tgt/targets.conf from " +"include /etc/tgt/conf.d/*.conf to include " +"/etc/tgt/conf.d/cinder_tgt.conf, as follows:" +msgstr "" + +#: ./doc/admin-guide-cloud/section_ts_cinder_config.xml179(para) +msgid "" +"Restart tgt and cinder-* services so they pick up the new " +"configuration." +msgstr "" + +#: ./doc/admin-guide-cloud/ch_blockstorage.xml7(title) +msgid "Block Storage" +msgstr "" + +#: ./doc/admin-guide-cloud/ch_blockstorage.xml8(para) +msgid "" +"The OpenStack Block Storage service works though the interaction of a series" +" of daemon processes named cinder-* that reside persistently on the host " +"machine or machines. The binaries can all be run from a single node, or " +"spread across multiple nodes. They can also be run on the same node as other" +" OpenStack services." +msgstr "" + +#: ./doc/admin-guide-cloud/ch_blockstorage.xml16(title) +msgid "Introduction to Block Storage" +msgstr "" + +#: ./doc/admin-guide-cloud/ch_blockstorage.xml17(para) +msgid "" +"To administer the OpenStack Block Storage service, it is helpful to " +"understand a number of concepts. You must make certain choices when you " +"configure the Block Storage service in OpenStack. The bulk of the options " +"come down to two choices, single node or multi-node install. You can read a " +"longer discussion about storage decisions in Storage Decisions in the " +"OpenStack Operations Guide." +msgstr "" + +#: ./doc/admin-guide-cloud/ch_blockstorage.xml26(para) +msgid "" +"The OpenStack Block Storage Service enables you to add extra block-level " +"storage to your OpenStack Compute instances. This service is similar to the " +"Amazon EC2 Elastic Block Storage (EBS) offering." +msgstr "" + +#: ./doc/admin-guide-cloud/ch_blockstorage.xml33(title) +msgid "Manage volumes" +msgstr "" + +#: ./doc/admin-guide-cloud/ch_blockstorage.xml34(para) +msgid "" +"The default OpenStack Block Storage service implementation is an iSCSI " +"solution that uses Logical Volume Manager (LVM) for Linux." +msgstr "" + +#: ./doc/admin-guide-cloud/ch_blockstorage.xml38(para) +msgid "" +"The OpenStack Block Storage service is not a shared storage solution like a " +"Storage Area Network (SAN) of NFS volumes, where you can attach a volume to " +"multiple servers. With the OpenStack Block Storage service, you can attach a" +" volume to only one instance at a time." +msgstr "" + +#: ./doc/admin-guide-cloud/ch_blockstorage.xml44(para) +msgid "" +"The OpenStack Block Storage service also provides drivers that enable you to" +" use several vendors' back-end storage devices, in addition to or instead of" +" the base LVM implementation." +msgstr "" + +#: ./doc/admin-guide-cloud/ch_blockstorage.xml49(para) +msgid "" +"This high-level procedure shows you how to create and attach a volume to a " +"server instance." +msgstr "" + +#: ./doc/admin-guide-cloud/ch_blockstorage.xml53(para) +msgid "" +"You must configure both OpenStack Compute and the OpenStack Block Storage " +"service through the cinder.conf file." +msgstr "" + +#: ./doc/admin-guide-cloud/ch_blockstorage.xml58(para) +msgid "" +"Create a volume through the command. This command creates " +"an LV into the volume group (VG) \"cinder-volumes.\"" +msgstr "" + +#: ./doc/admin-guide-cloud/ch_blockstorage.xml64(para) +msgid "" +"Attach the volume to an instance through the command. This " +"command creates a unique iSCSI IQN that is exposed to the compute node." +msgstr "" + +#: ./doc/admin-guide-cloud/ch_blockstorage.xml70(para) +msgid "" +"The compute node, which runs the instance, now has an active ISCSI session " +"and new local storage (usually a /dev/sdX disk)." +msgstr "" + +#: ./doc/admin-guide-cloud/ch_blockstorage.xml77(para) +msgid "" +"libvirt uses that local storage as storage for the instance. The instance " +"get a new disk, usually a /dev/vdX disk." +msgstr "" + +#: ./doc/admin-guide-cloud/ch_blockstorage.xml86(para) +msgid "" +"For this particular walk through, one cloud controller runs nova-api, nova-" +"scheduler, nova-" +"objectstore, nova-network and " +"cinder-* services. Two additional compute nodes run " +"nova-compute. The walk through " +"uses a custom partitioning scheme that carves out 60 GB of space and labels " +"it as LVM. The network uses the FlatManager and " +"NetworkManager settings for OpenStack Compute (Nova)." +msgstr "" + +#: ./doc/admin-guide-cloud/ch_blockstorage.xml100(para) +msgid "" +"The network mode does not interfere with the way cinder works, but you must " +"set up networking for cinder to work. For details, see ." +msgstr "" + +#: ./doc/admin-guide-cloud/ch_blockstorage.xml103(para) +msgid "" +"To set up Compute to use volumes, ensure that Block Storage is installed " +"along with lvm2. This guide describes how to troubleshoot your installation " +"and back up your Compute volumes." +msgstr "" + +#: ./doc/admin-guide-cloud/ch_blockstorage.xml108(title) +msgid "Boot from volume" +msgstr "" + +#: ./doc/admin-guide-cloud/ch_blockstorage.xml109(para) +msgid "" +"In some cases, instances can be stored and run from inside volumes. For " +"information, see the Launch an instance from a " +"volume section in the OpenStack End User Guide." +msgstr "" + +#: ./doc/admin-guide-cloud/ch_blockstorage.xml124(title) +msgid "Troubleshoot your installation" +msgstr "" + +#: ./doc/admin-guide-cloud/ch_blockstorage.xml125(para) +msgid "" +"This section provides useful tips to help troubleshoot your Block Storage " +"Service installation." +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking-adv-config.xml6(title) +msgid "Advanced configuration options" +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking-adv-config.xml7(para) +msgid "" +"This section describes advanced configuration options for various system " +"components. For example, configuration options where the default works but " +"that the user wants to customize options. After installing from packages, " +"$NEUTRON_CONF_DIR is /etc/neutron." +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking-adv-config.xml13(title) +msgid "OpenStack Networking server with plug-in" +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking-adv-config.xml14(para) +msgid "" +"This is the web server that runs the OpenStack Networking API Web Server. It" +" is responsible for loading a plug-in and passing the API calls to the plug-" +"in for processing. The neutron-server should receive one of more " +"configuration files as it its input, for example:" +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking-adv-config.xml20(para) +msgid "" +"The neutron config contains the common neutron configuration parameters. The" +" plug-in config contains the plug-in specific flags. The plug-in that is run" +" on the service is loaded through the core_plugin " +"configuration parameter. In some cases a plug-in might have an agent that " +"performs the actual networking." +msgstr "" + +#. Specific +#. configuration details can be seen in the Appendix - +#. Configuration File Options. +#: ./doc/admin-guide-cloud/section_networking-adv-config.xml31(para) +msgid "" +"Most plug-ins require a SQL database. After you install and start the " +"database server, set a password for the root account and delete the " +"anonymous accounts:" +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking-adv-config.xml37(para) +msgid "Create a database and user account specifically for plug-in:" +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking-adv-config.xml43(para) +msgid "" +"Once the above is done you can update the settings in the relevant plug-in " +"configuration files. The plug-in specific configuration files can be found " +"at $NEUTRON_CONF_DIR/plugins." +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking-adv-config.xml47(para) +msgid "" +"Some plug-ins have a L2 agent that performs the actual networking. That is, " +"the agent will attach the virtual machine NIC to the OpenStack Networking " +"network. Each node should have an L2 agent running on it. Note that the " +"agent receives the following input parameters:" +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking-adv-config.xml53(para) +msgid "Two things need to be done prior to working with the plug-in:" +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking-adv-config.xml57(para) +msgid "Ensure that the core plug-in is updated." +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking-adv-config.xml60(para) +msgid "Ensure that the database connection is correctly set." +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking-adv-config.xml64(para) +msgid "" +"The following table contains examples for these settings. Some Linux " +"packages might provide installation utilities that configure these." +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking-adv-config.xml73(th) +msgid "Parameter" +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking-adv-config.xml74(th) +msgid "Value" +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking-adv-config.xml84(td) +#: ./doc/admin-guide-cloud/section_networking-adv-config.xml107(td) +msgid "core_plugin ($NEUTRON_CONF_DIR/neutron.conf)" +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking-adv-config.xml86(td) +msgid "neutron.plugins.openvswitch.ovs_neutron_plugin.OVSNeutronPluginV2" +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking-adv-config.xml90(code) +#: ./doc/admin-guide-cloud/section_networking-adv-config.xml113(code) +msgid "[database]" +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking-adv-config.xml89(td) +msgid "" +"connection (in the plugin configuration file, section )" +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking-adv-config.xml91(td) +msgid "" +"mysql://<username>:<password>@localhost/ovs_neutron?charset=utf8" +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking-adv-config.xml94(td) +#: ./doc/admin-guide-cloud/section_networking-adv-config.xml117(td) +msgid "Plug-in Configuration File" +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking-adv-config.xml95(td) +msgid "$NEUTRON_CONF_DIR/plugins/openvswitch/ovs_neutron_plugin.ini" +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking-adv-config.xml98(td) +#: ./doc/admin-guide-cloud/section_networking-adv-config.xml121(td) +#: ./doc/admin-guide-cloud/section_networking_arch.xml35(th) +msgid "Agent" +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking-adv-config.xml99(td) +msgid "neutron-openvswitch-agent" +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking-adv-config.xml109(td) +msgid "neutron.plugins.linuxbridge.lb_neutron_plugin.LinuxBridgePluginV2" +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking-adv-config.xml112(td) +msgid "" +"connection (in the plug-in configuration file, section )" +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking-adv-config.xml114(td) +msgid "" +"mysql://<username>:<password>@localhost/neutron_linux_bridge?charset=utf8" +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking-adv-config.xml118(td) +msgid "$NEUTRON_CONF_DIR/plugins/linuxbridge/linuxbridge_conf.ini" +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking-adv-config.xml122(td) +msgid "neutron-linuxbridge-agent" +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking-adv-config.xml126(para) +msgid "" +"All plug-in configuration files options can be found in the Appendix - " +"Configuration File Options." +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking-adv-config.xml130(title) +#: ./doc/admin-guide-cloud/section_networking-scenarios.xml200(title) +msgid "DHCP agent" +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking-adv-config.xml131(para) +msgid "" +"There is an option to run a DHCP server that will allocate IP addresses to " +"virtual machines running on the network. When a subnet is created, by " +"default, the subnet has DHCP enabled." +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking-adv-config.xml135(para) +msgid "The node that runs the DHCP agent should run:" +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking-adv-config.xml138(para) +msgid "" +"Currently the DHCP agent uses dnsmasq to perform that static address " +"assignment." +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking-adv-config.xml140(para) +msgid "" +"A driver needs to be configured that matches the plug-in running on the " +"service.
Basic settings
ParameterValue
Open " +"vSwitch
interface_driver " +"($NEUTRON_CONF_DIR/dhcp_agent.ini)neutron.agent.linux.interface.OVSInterfaceDriver
Linux " +"Bridge
interface_driver " +"($NEUTRON_CONF_DIR/dhcp_agent.ini)neutron.agent.linux.interface.BridgeInterfaceDriver
" +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking-adv-config.xml175(title) +#: ./doc/admin-guide-cloud/section_networking-adv-config.xml264(title) +#: ./doc/admin-guide-cloud/section_networking-adv-config.xml386(title) +msgid "Namespace" +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking-adv-config.xml176(para) +msgid "" +"By default the DHCP agent makes use of Linux network namespaces in order to " +"support overlapping IP addresses. Requirements for network namespaces " +"support are described in the Limitations section." +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking-adv-config.xml182(para) +msgid "" +"If the Linux installation does not support network " +"namespace, you must disable using network namespace in the DHCP agent config" +" file (The default value of use_namespaces is True)." +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking-adv-config.xml192(title) +msgid "L3 Agent" +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking-adv-config.xml193(para) +msgid "" +"There is an option to run a L3 agent that will give enable layer 3 " +"forwarding and floating IP support. The node that runs the L3 agent should " +"run:" +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking-adv-config.xml198(para) +msgid "" +"A driver needs to be configured that matches the plug-in running on the " +"service. The driver is used to create the routing interface.
Basic settings
ParameterValue
Open " +"vSwitch
interface_driver " +"($NEUTRON_CONF_DIR/l3_agent.ini)neutron.agent.linux.interface.OVSInterfaceDriver
external_network_bridge" +" ($NEUTRON_CONF_DIR/l3_agent.ini)br-ex
Linux Bridge
interface_driver" +" " +"($NEUTRON_CONF_DIR/l3_agent.ini)neutron.agent.linux.interface.BridgeInterfaceDriver
external_network_bridge" +" ($NEUTRON_CONF_DIR/l3_agent.ini)This field must be empty (or the " +"bridge name for the external network).
" +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking-adv-config.xml250(para) +msgid "OpenStack Identity authentication:" +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking-adv-config.xml252(para) +msgid "For example," +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking-adv-config.xml256(para) +msgid "Admin user details:" +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking-adv-config.xml246(para) +msgid "" +"The L3 agent communicates with the OpenStack Networking server via the " +"OpenStack Networking API, so the following configuration is required: " +"" +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking-adv-config.xml265(para) +msgid "" +"By default the L3 agent makes use of Linux network namespaces in order to " +"support overlapping IP addresses. Requirements for network namespaces " +"support are described in the Limitation section." +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking-adv-config.xml271(para) +msgid "" +"If the Linux installation does not support network " +"namespace, you must disable using network namespace in the L3 agent config " +"file (The default value of use_namespaces is True)." +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking-adv-config.xml278(para) +msgid "" +"When use_namespaces is set to False, only one router ID can be supported per" +" node. This must be configured via the configuration variable " +"router_id." +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking-adv-config.xml285(para) +msgid "" +"To configure it, you need to run the OpenStack Networking service and create" +" a router, and then set an ID of the router created to " +"router_id in the L3 agent configuration file." +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking-adv-config.xml305(title) +msgid "Multiple floating IP pools" +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking-adv-config.xml306(para) +msgid "" +"The L3 API in OpenStack Networking supports multiple floating IP pools. In " +"OpenStack Networking, a floating IP pool is represented as an external " +"network and a floating IP is allocated from a subnet associated with the " +"external network. Since each L3 agent can be associated with at most one " +"external network, we need to invoke multiple L3 agent to define multiple " +"floating IP pools. 'gateway_external_network_id' in L3 agent " +"configuration file indicates the external network that the L3 agent handles." +" You can run multiple L3 agent instances on one host." +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking-adv-config.xml318(para) +msgid "" +"In addition, when you run multiple L3 agents, make sure that handle_internal_only_routers is set to True only for one L3 agent in an OpenStack " +"Networking deployment and set to False " +"for all other L3 agents. Since the default value of this parameter is True, " +"you need to configure it carefully." +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking-adv-config.xml327(para) +msgid "" +"Before starting L3 agents, you need to create routers and external networks," +" then update the configuration files with UUID of external networks and " +"start L3 agents." +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking-adv-config.xml331(para) +msgid "" +"For the first agent, invoke it with the following l3_agent.ini where " +"handle_internal_only_routers is True." +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking-adv-config.xml340(para) +msgid "" +"For the second (or later) agent, invoke it with the following l3_agent.ini " +"where handle_internal_only_routers is False." +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking-adv-config.xml349(title) +msgid "L3 Metering Agent" +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking-adv-config.xml350(para) +msgid "" +"There is an option to run a L3 metering agent that will enable layer 3 " +"traffic metering. In general case the metering agent should be launched on " +"all nodes that run the L3 agent:" +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking-adv-config.xml355(para) +msgid "" +"A driver needs to be configured that matches the plug-in running on the " +"service. The driver is used to add metering to the routing interface.
Basic settings
ParameterValue
Open " +"vSwitch
interface_driver " +"($NEUTRON_CONF_DIR/metering_agent.ini)neutron.agent.linux.interface.OVSInterfaceDriver
Linux " +"Bridge
interface_driver " +"($NEUTRON_CONF_DIR/metering_agent.ini)neutron.agent.linux.interface.BridgeInterfaceDriver
" +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking-adv-config.xml387(para) +msgid "" +"The metering agent and the L3 agent have to have the same configuration " +"regarding to the network namespaces setting." +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking-adv-config.xml389(para) +msgid "" +"If the Linux installation does not support network namespace, you must " +"disable using network namespace in the L3 metering config file (The default " +"value of is True)." +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking-adv-config.xml396(title) +msgid "L3 metering driver" +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking-adv-config.xml397(para) +msgid "" +"A driver which implements the metering abstraction needs to be configured. " +"Currently there is only one implementation which is based on iptables." +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking-adv-config.xml402(title) +msgid "L3 metering service driver" +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking-adv-config.xml403(para) +msgid "" +"To enable L3 metering you have to be sure to set the following parameter in " +"neutron.conf on the host that runs neutron-server:" +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking-adv-config.xml410(title) +msgid "Limitations" +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking-adv-config.xml413(para) +msgid "" +"No equivalent for nova-network --multi_host flag: Nova-" +"network has a model where the L3, NAT, and DHCP processing happen on the " +"compute node itself, rather than a dedicated networking node. OpenStack " +"Networking now support running multiple l3-agent and dhcp-agents with load " +"being split across those agents, but the tight coupling of that scheduling " +"with the location of the VM is not supported in Grizzly. The Havana release " +"is expected to include an exact replacement for the --multi_host flag in " +"nova-network." +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking-adv-config.xml427(para) +msgid "" +"Linux network namespace required on nodes running neutron-l3-agent or " +"neutron-dhcp-" +"agent if overlapping IPs are in use: . In order to " +"support overlapping IP addresses, the OpenStack Networking DHCP and L3 " +"agents use Linux network namespaces by default. The hosts running these " +"processes must support network namespaces. To support network namespaces, " +"the following are required:" +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking-adv-config.xml445(para) +msgid "" +"Linux kernel 2.6.24 or newer (with CONFIG_NET_NS=y in kernel configuration) " +"and" +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking-adv-config.xml450(para) +msgid "" +"iproute2 utilities ('ip' command) version 3.1.0 (aka 20111117) or newer" +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking-adv-config.xml455(para) +msgid "" +"To check whether your host supports namespaces try running the following as " +"root:" +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking-adv-config.xml459(para) +msgid "" +"If the preceding commands do not produce errors, your platform is likely " +"sufficient to use the dhcp-agent or l3-agent with namespace. In our " +"experience, Ubuntu 12.04 or later support namespaces as does Fedora 17 and " +"new, but some older RHEL platforms do not by default. It may be possible to " +"upgrade the iproute2 package on a platform that does not support namespaces " +"by default." +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking-adv-config.xml468(para) +msgid "" +"If you need to disable namespaces, make sure the " +"neutron.conf used by neutron-server has the following " +"setting:" +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking-adv-config.xml472(para) +msgid "" +"and that the dhcp_agent.ini and l3_agent.ini have the following setting:" +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking-adv-config.xml476(para) +msgid "" +"If the host does not support namespaces then the neutron-l3-agent and neutron-dhcp-agent should be run on different" +" hosts. This is due to the fact that there is no isolation between the IP " +"addresses created by the L3 agent and by the DHCP agent. By manipulating the" +" routing the user can ensure that these networks have access to one another." +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking-adv-config.xml488(para) +msgid "" +"If you run both L3 and DHCP services on the same node, you should enable " +"namespaces to avoid conflicts with routes:" +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking-adv-config.xml496(para) +msgid "" +"No IPv6 support for L3 agent: The neutron-l3-agent, used by many " +"plug-ins to implement L3 forwarding, supports only IPv4 forwarding. " +"Currently, there are no errors provided if you configure IPv6 addresses via " +"the API." +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking-adv-config.xml507(para) +msgid "" +"ZeroMQ support is experimental: Some agents, including " +"neutron-dhcp-agent, neutron-openvswitch-agent, and neutron-linuxbridge-agent use RPC to " +"communicate. ZeroMQ is an available option in the configuration file, but " +"has not been tested and should be considered experimental. In particular, " +"issues might occur with ZeroMQ and the dhcp agent." +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking-adv-config.xml522(para) +msgid "" +"MetaPlugin is experimental: This release includes a " +"MetaPlugin that is intended to support multiple plug-ins at the same time " +"for different API requests, based on the content of those API requests. The " +"core team has not thoroughly reviewed or tested this functionality. Consider" +" this functionality to be experimental until further validation is " +"performed." +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking_pagination_and_sorting_support.xml6(title) +msgid "Plug-in pagination and sorting support" +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking_pagination_and_sorting_support.xml8(caption) +msgid "Plug-ins that support native pagination and sorting" +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking_pagination_and_sorting_support.xml13(th) +msgid "Support Native Pagination" +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking_pagination_and_sorting_support.xml14(th) +msgid "Support Native Sorting" +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking_pagination_and_sorting_support.xml20(td) +#: ./doc/admin-guide-cloud/section_networking_pagination_and_sorting_support.xml21(td) +#: ./doc/admin-guide-cloud/section_networking_pagination_and_sorting_support.xml25(td) +#: ./doc/admin-guide-cloud/section_networking_pagination_and_sorting_support.xml26(td) +#: ./doc/admin-guide-cloud/section_networking_pagination_and_sorting_support.xml30(td) +#: ./doc/admin-guide-cloud/section_networking_pagination_and_sorting_support.xml31(td) +#: ./doc/admin-guide-cloud/section_networking_adv_features.xml394(td) +#: ./doc/admin-guide-cloud/section_networking_adv_features.xml1189(td) +#: ./doc/admin-guide-cloud/section_networking_adv_features.xml1322(td) +#: ./doc/admin-guide-cloud/section_networking-use.xml134(td) +#: ./doc/admin-guide-cloud/section_networking-use.xml235(td) +msgid "True" +msgstr "" + +#: ./doc/admin-guide-cloud/section_backup-block-storage-disks.xml6(title) +msgid "Back up Block Storage Service disks" +msgstr "" + +#: ./doc/admin-guide-cloud/section_backup-block-storage-disks.xml7(para) +msgid "" +"While you can use the LVM snapshot to create snapshots, you can also use it " +"to back up your volumes. By using LVM snapshot, you reduce the size of the " +"backup; only existing data is backed up instead of the entire volume." +msgstr "" + +#: ./doc/admin-guide-cloud/section_backup-block-storage-disks.xml11(para) +msgid "" +"To back up a volume, you must create a snapshot of it. An LVM snapshot is " +"the exact copy of a logical volume, which contains data in a frozen state. " +"This prevents data corruption, because data cannot be manipulated during the" +" volume creation process. Remember that the volumes created through a " +" command exist in an LVM logical volume." +msgstr "" + +#: ./doc/admin-guide-cloud/section_backup-block-storage-disks.xml18(para) +msgid "" +"Before you create the snapshot, you must have enough space to save it. As a " +"precaution, you should have at least twice as much space as the potential " +"snapshot size. If insufficient space is available, the snapshot might become" +" corrupted." +msgstr "" + +#: ./doc/admin-guide-cloud/section_backup-block-storage-disks.xml23(para) +msgid "" +"For this example, assume that a 100 GB volume named " +"volume-00000001 was created for an instance while only 4 " +"GB are used. This example uses these commands to back up only those 4 GB:" +msgstr "" + +#: ./doc/admin-guide-cloud/section_backup-block-storage-disks.xml29(para) +msgid " command. Directly manipulates the volumes." +msgstr "" + +#: ./doc/admin-guide-cloud/section_backup-block-storage-disks.xml33(para) +msgid "" +" command. Discovers the partition table created inside the " +"instance." +msgstr "" + +#: ./doc/admin-guide-cloud/section_backup-block-storage-disks.xml37(para) +msgid " command. Creates a minimum-sized backup." +msgstr "" + +#: ./doc/admin-guide-cloud/section_backup-block-storage-disks.xml41(para) +msgid "" +" command. Calculates the backup checksum to check its " +"consistency." +msgstr "" + +#: ./doc/admin-guide-cloud/section_backup-block-storage-disks.xml45(para) +msgid "You can apply this process to volumes of any size." +msgstr "" + +#: ./doc/admin-guide-cloud/section_backup-block-storage-disks.xml47(title) +msgid "To back up Block Storage Service disks" +msgstr "" + +#: ./doc/admin-guide-cloud/section_backup-block-storage-disks.xml49(title) +msgid "Create a snapshot of a used volume" +msgstr "" + +#: ./doc/admin-guide-cloud/section_backup-block-storage-disks.xml52(para) +msgid "Use this command to list all volumes:" +msgstr "" + +#: ./doc/admin-guide-cloud/section_backup-block-storage-disks.xml56(para) +msgid "" +"Create the snapshot; you can do this while the volume is attached to an " +"instance:" +msgstr "" + +#: ./doc/admin-guide-cloud/section_backup-block-storage-disks.xml59(para) +msgid "" +"Use the configuration option to tell LVM that " +"you want a snapshot of an already existing volume. The command includes the " +"size of the space reserved for the snapshot volume, the name of the " +"snapshot, and the path of an already existing volume. Generally, this path " +"is /dev/nova-" +"volumes/$volume_name." +msgstr "" + +#: ./doc/admin-guide-cloud/section_backup-block-storage-disks.xml67(para) +msgid "" +"The size does not have to be the same as the volume of the snapshot. The " +"size parameter defines the space that LVM reserves " +"for the snapshot volume. As a precaution, the size should be the same as " +"that of the original volume, even if the whole space is not currently used " +"by the snapshot." +msgstr "" + +#: ./doc/admin-guide-cloud/section_backup-block-storage-disks.xml78(para) +msgid "Run the command again to verify the snapshot:" +msgstr "" + +#: ./doc/admin-guide-cloud/section_backup-block-storage-disks.xml120(title) +msgid "Partition table discovery" +msgstr "" + +#: ./doc/admin-guide-cloud/section_backup-block-storage-disks.xml123(para) +msgid "" +"To exploit the snapshot with the command, mount your " +"partition on the Block Storage Service server." +msgstr "" + +#: ./doc/admin-guide-cloud/section_backup-block-storage-disks.xml127(para) +msgid "" +"The utility discovers and maps table partitions. You can " +"use it to view partitions that are created inside the instance. Without " +"using the partitions created inside instances, you cannot see its content " +"and create efficient backups." +msgstr "" + +#: ./doc/admin-guide-cloud/section_backup-block-storage-disks.xml136(para) +msgid "" +"On a Debian-based distribution, you can also use the " +"command." +msgstr "" + +#: ./doc/admin-guide-cloud/section_backup-block-storage-disks.xml140(para) +msgid "" +"If the tools successfully find and map the partition table, no errors are " +"returned." +msgstr "" + +#: ./doc/admin-guide-cloud/section_backup-block-storage-disks.xml145(para) +msgid "To check the partition table map, run this command:" +msgstr "" + +#: ./doc/admin-guide-cloud/section_backup-block-storage-disks.xml148(para) +msgid "" +"You can see the nova--volumes-volume--00000001--snapshot1" +" partition." +msgstr "" + +#: ./doc/admin-guide-cloud/section_backup-block-storage-disks.xml151(para) +msgid "" +"If you created more than one partition on that volume, you see several " +"partitions; for example: nova--volumes-volume--00000001--" +"snapshot2, nova--volumes-volume--00000001--" +"snapshot3, and so on." +msgstr "" + +#: ./doc/admin-guide-cloud/section_backup-block-storage-disks.xml159(para) +msgid "Mount your partition:" +msgstr "" + +#: ./doc/admin-guide-cloud/section_backup-block-storage-disks.xml161(para) +msgid "If the partition mounts successfully, no errors are returned." +msgstr "" + +#: ./doc/admin-guide-cloud/section_backup-block-storage-disks.xml163(para) +msgid "" +"You can directly access the data inside the instance. If a message prompts " +"you for a partition or you cannot mount it, determine whether enough space " +"was allocated for the snapshot or the command failed to " +"discover the partition table." +msgstr "" + +#: ./doc/admin-guide-cloud/section_backup-block-storage-disks.xml170(para) +msgid "Allocate more space to the snapshot and try the process again." +msgstr "" + +#: ./doc/admin-guide-cloud/section_backup-block-storage-disks.xml176(title) +msgid "Use the command to create archives" +msgstr "" + +#: ./doc/admin-guide-cloud/section_backup-block-storage-disks.xml178(para) +msgid "Create a backup of the volume:" +msgstr "" + +#: ./doc/admin-guide-cloud/section_backup-block-storage-disks.xml180(para) +msgid "" +"This command creates a tar.gz file that contains the " +"data, and data only. This ensures that " +"you do not waste space by backing up empty sectors." +msgstr "" + +#: ./doc/admin-guide-cloud/section_backup-block-storage-disks.xml186(title) +msgid "Checksum calculation I" +msgstr "" + +#: ./doc/admin-guide-cloud/section_backup-block-storage-disks.xml187(para) +msgid "" +"You should always have the checksum for your backup files. When you transfer" +" the same file over the network, you can run a checksum calculation to " +"ensure that your file was not corrupted during its transfer. The checksum is" +" a unique ID for a file. If the checksums are different, the file is " +"corrupted." +msgstr "" + +#: ./doc/admin-guide-cloud/section_backup-block-storage-disks.xml193(para) +msgid "" +"Run this command to run a checksum for your file and save the result to a " +"file:" +msgstr "" + +#: ./doc/admin-guide-cloud/section_backup-block-storage-disks.xml197(para) +msgid "" +"Use the command carefully because the time it takes to " +"complete the calculation is directly proportional to the size of the file." +msgstr "" + +#: ./doc/admin-guide-cloud/section_backup-block-storage-disks.xml201(para) +msgid "" +"For files larger than around 4 to 6 GB, and depending on your CPU, the " +"process might take a long time." +msgstr "" + +#: ./doc/admin-guide-cloud/section_backup-block-storage-disks.xml207(title) +msgid "After work cleaning" +msgstr "" + +#: ./doc/admin-guide-cloud/section_backup-block-storage-disks.xml208(para) +msgid "" +"Now that you have an efficient and consistent backup, use this command to " +"clean up the file system:" +msgstr "" + +#: ./doc/admin-guide-cloud/section_backup-block-storage-disks.xml213(para) +msgid "Unmount the volume:" +msgstr "" + +#: ./doc/admin-guide-cloud/section_backup-block-storage-disks.xml217(para) +msgid "Delete the partition table:" +msgstr "" + +#: ./doc/admin-guide-cloud/section_backup-block-storage-disks.xml221(para) +msgid "Remove the snapshot:" +msgstr "" + +#: ./doc/admin-guide-cloud/section_backup-block-storage-disks.xml225(para) +msgid "Repeat these steps for all your volumes." +msgstr "" + +#: ./doc/admin-guide-cloud/section_backup-block-storage-disks.xml228(title) +msgid "Automate your backups" +msgstr "" + +#: ./doc/admin-guide-cloud/section_backup-block-storage-disks.xml229(para) +msgid "" +"Because more and more volumes might be allocated to your Block Storage " +"service, you might want to automate your backups. The SCR_5005_V01_NUAC-" +"OPENSTACK-EBS-volumes-backup.sh script assists you with this task. " +"The script performs the operations from the previous example, but also " +"provides a mail report and runs the backup based on the " +" setting." +msgstr "" + +#: ./doc/admin-guide-cloud/section_backup-block-storage-disks.xml239(para) +msgid "" +"Launch this script from the server that runs the Block Storage Service." +msgstr "" + +#: ./doc/admin-guide-cloud/section_backup-block-storage-disks.xml241(para) +msgid "This example shows a mail report:" +msgstr "" + +#: ./doc/admin-guide-cloud/section_backup-block-storage-disks.xml255(para) +msgid "" +"The script also enables you to SSH to your instances and run a " +" command into them. To make this work, enable the connection" +" to the Compute project keys. If you do not want to run the " +" command, you can add enable_mysql_dump=0 to the script " +"to turn off this functionality." +msgstr "" + +#: ./doc/admin-guide-cloud/section_ts_failed_connect_vol_FC_SAN.xml4(title) +msgid "Failed to connect volume in FC SAN" +msgstr "" + +#: ./doc/admin-guide-cloud/section_ts_failed_connect_vol_FC_SAN.xml7(para) +msgid "" +"Compute node failed to connect to a volume in a Fibre Channel (FC) SAN " +"configuration. The WWN may not be zoned correctly in your FC SAN that links " +"the Compute host to the storage array." +msgstr "" + +#: ./doc/admin-guide-cloud/section_ts_failed_connect_vol_FC_SAN.xml16(para) +msgid "" +"The network administrator must configure the FC SAN fabric by correctly " +"zoning the WWN (port names) from your Compute node HBAs." +msgstr "" + +#: ./doc/admin-guide-cloud/section_object-storage-admin.xml6(title) +msgid "System administration for Object Storage" +msgstr "" + +#: ./doc/admin-guide-cloud/section_object-storage-admin.xml7(para) +msgid "" +"By understanding Object Storage concepts, you can better monitor and " +"administer your storage solution. The majority of the administration " +"information is maintained in developer documentation at docs.openstack.org/developer/swift/." +msgstr "" + +#: ./doc/admin-guide-cloud/section_object-storage-admin.xml13(para) +msgid "" +"See the OpenStack Configuration " +"Reference for a list of configuration options for Object " +"Storage." +msgstr "" + +#: ./doc/admin-guide-cloud/ch_objectstorage.xml7(title) +msgid "Object Storage" +msgstr "" + +#: ./doc/admin-guide-cloud/section_ts_vol_attach_miss_sg_scan.xml8(title) +msgid "Failed to Attach Volume, Missing sg_scan" +msgstr "" + +#: ./doc/admin-guide-cloud/section_ts_vol_attach_miss_sg_scan.xml11(para) +msgid "" +"Failed to attach volume to an instance, sg_scan file " +"not found. This warning and error occur when the " +"sg3-utils package is not installed on the Compute node. " +"The IDs in your message are unique to your system:" +msgstr "" + +#: ./doc/admin-guide-cloud/section_ts_vol_attach_miss_sg_scan.xml25(para) +msgid "" +"Run this command on the Compute node to install the " +"sg3-utils package:" +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking_high_avail.xml6(title) +msgid "High availability" +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking_high_avail.xml7(para) +msgid "" +"The use of high-availability in a Networking deployment helps prevent " +"individual node failures. In general, you can run neutron-server and neutron-dhcp-agent in an active-active " +"fashion. You can run the neutron-l3-agent service as active/passive, " +"which avoids IP conflicts with respect to gateway IP addresses." +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking_high_avail.xml17(title) +msgid "Networking high availability with Pacemaker" +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking_high_avail.xml18(para) +msgid "" +"You can run some Networking services into a cluster (Active / Passive or " +"Active / Active for Networking Server only) with Pacemaker." +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking_high_avail.xml21(para) +msgid "Download the latest resources agents:" +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking_high_avail.xml24(para) +msgid "" +"neutron-server: https://github.com/madkiss" +"/openstack-resource-agents" +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking_high_avail.xml29(para) +msgid "" +"neutron-dhcp-agent : https://github.com/madkiss/openstack-resource-agents" +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking_high_avail.xml34(para) +msgid "" +"neutron-l3-agent : https://github.com/madkiss/openstack-resource-agents" +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking_high_avail.xml40(para) +msgid "" +"For information about how to build a cluster, see Pacemaker " +"documentation." +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking_adv_operational_features.xml6(title) +msgid "Advanced operational features" +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking_adv_operational_features.xml8(title) +msgid "Logging settings" +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking_adv_operational_features.xml9(para) +msgid "" +"Networking components use Python logging module to do logging. Logging " +"configuration can be provided in neutron.conf or as " +"command line options. Command options override ones in " +"neutron.conf." +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking_adv_operational_features.xml14(para) +msgid "" +"To configure logging for Networking components, use one of these methods:" +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking_adv_operational_features.xml18(para) +msgid "Provide logging settings in a logging configuration file." +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking_adv_operational_features.xml20(para) +msgid "" +"See Python logging " +"how-to to learn more about logging." +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking_adv_operational_features.xml24(para) +msgid "Provide logging setting in neutron.conf" +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking_adv_operational_features.xml49(title) +msgid "Notifications" +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking_adv_operational_features.xml50(para) +msgid "" +"Notifications can be sent when Networking resources such as network, subnet " +"and port are created, updated or deleted." +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking_adv_operational_features.xml54(title) +msgid "Notification options" +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking_adv_operational_features.xml55(para) +msgid "" +"To support DHCP agent, rpc_notifier driver must be set. To set up the " +"notification, edit notification options in " +"neutron.conf:" +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking_adv_operational_features.xml85(title) +msgid "Setting cases" +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking_adv_operational_features.xml87(title) +msgid "Logging and RPC" +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking_adv_operational_features.xml88(para) +msgid "" +"These options configure the Networking server to send notifications through " +"logging and RPC. The logging options are described in OpenStack " +"Configuration Reference . RPC notifications go to " +"'notifications.info' queue bound to a topic exchange defined by " +"'control_exchange' in neutron.conf." +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking_adv_operational_features.xml127(title) +msgid "Multiple RPC topics" +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking_adv_operational_features.xml128(para) +msgid "" +"These options configure the Networking server to send notifications to " +"multiple RPC topics. RPC notifications go to 'notifications_one.info' and " +"'notifications_two.info' queues bound to a topic exchange defined by " +"'control_exchange' in neutron.conf." +msgstr "" + +#. ... Based on a blog, should be replaced with original material... +#: ./doc/admin-guide-cloud/section_object-storage-monitoring.xml7(title) +msgid "Object Storage monitoring" +msgstr "" + +#: ./doc/admin-guide-cloud/section_object-storage-monitoring.xml9(para) +msgid "" +"Excerpted from a blog post by Darrell Bishop" +msgstr "" + +#: ./doc/admin-guide-cloud/section_object-storage-monitoring.xml12(para) +msgid "" +"An OpenStack Object Storage cluster is a collection of many daemons that " +"work together across many nodes. With so many different components, you must" +" be able to tell what is going on inside the cluster. Tracking server-level " +"metrics like CPU utilization, load, memory consumption, disk usage and " +"utilization, and so on is necessary, but not sufficient." +msgstr "" + +#: ./doc/admin-guide-cloud/section_object-storage-monitoring.xml19(para) +msgid "" +"What are different daemons are doing on each server? What is the volume of " +"object replication on node8? How long is it taking? Are there errors? If so," +" when did they happen?" +msgstr "" + +#: ./doc/admin-guide-cloud/section_object-storage-monitoring.xml22(para) +msgid "" +"In such a complex ecosystem, you can use multiple approaches to get the " +"answers to these questions. This section describes several approaches." +msgstr "" + +#: ./doc/admin-guide-cloud/section_object-storage-monitoring.xml26(title) +msgid "Swift Recon" +msgstr "" + +#: ./doc/admin-guide-cloud/section_object-storage-monitoring.xml27(para) +msgid "" +"The Swift Recon middleware (see http://swift.openstack.org/admin_guide.html#cluster-telemetry-" +"and-monitoring) provides general machine statistics, such as load " +"average, socket statistics, /proc/meminfo contents, and so on, " +"as well as Swift-specific metrics:" +msgstr "" + +#: ./doc/admin-guide-cloud/section_object-storage-monitoring.xml35(para) +msgid "The MD5 sum of each ring file." +msgstr "" + +#: ./doc/admin-guide-cloud/section_object-storage-monitoring.xml38(para) +msgid "The most recent object replication time." +msgstr "" + +#: ./doc/admin-guide-cloud/section_object-storage-monitoring.xml41(para) +msgid "Count of each type of quarantined file: Account, container, or object." +msgstr "" + +#: ./doc/admin-guide-cloud/section_object-storage-monitoring.xml45(para) +msgid "Count of “async_pendings” (deferred container updates) on disk." +msgstr "" + +#: ./doc/admin-guide-cloud/section_object-storage-monitoring.xml49(para) +msgid "" +"Swift Recon is middleware that is installed in the object servers pipeline " +"and takes one required option: A local cache directory. To track " +"async_pendings, you must set up an additional cron job " +"for each object server. You access data by either sending HTTP requests " +"directly to the object server or using the command-line " +"client." +msgstr "" + +#: ./doc/admin-guide-cloud/section_object-storage-monitoring.xml57(para) +msgid "" +"There are some good Object Storage cluster statistics but the general server" +" metrics overlap with existing server monitoring systems. To get the Swift-" +"specific metrics into a monitoring system, they must be polled. Swift Recon " +"essentially acts as a middleware metrics collector. The process that feeds " +"metrics to your statistics system, such as collectd and " +"gmond, probably already runs on the storage node. So, you" +" can choose to either talk to Swift Recon or collect the metrics directly." +msgstr "" + +#: ./doc/admin-guide-cloud/section_object-storage-monitoring.xml69(title) +msgid "Swift-Informant" +msgstr "" + +#: ./doc/admin-guide-cloud/section_object-storage-monitoring.xml70(para) +msgid "" +"Florian Hines developed the Swift-Informant middleware (see http://pandemicsyn.posterous.com/swift-informant-statsd-" +"getting-realtime-telem) to get real-time visibility into Object " +"Storage client requests. It sits in the pipeline for the proxy server, and " +"after each request to the proxy server, sends three metrics to a StatsD " +"server (see http://codeascraft.etsy.com/2011/02/15" +"/measure-anything-measure-everything/):" +msgstr "" + +#: ./doc/admin-guide-cloud/section_object-storage-monitoring.xml82(para) +msgid "" +"A counter increment for a metric like obj.GET.200 or " +"cont.PUT.404." +msgstr "" + +#: ./doc/admin-guide-cloud/section_object-storage-monitoring.xml87(para) +msgid "" +"Timing data for a metric like acct.GET.200 or " +"obj.GET.200. [The README says the metrics look like " +"duration.acct.GET.200, but I do not see the " +"duration in the code. I am not sure what the Etsy server " +"does but our StatsD server turns timing metrics into five derivative metrics" +" with new segments appended, so it probably works as coded. The first metric" +" turns into acct.GET.200.lower, " +"acct.GET.200.upper, acct.GET.200.mean, " +"acct.GET.200.upper_90, and acct.GET.200.count]." +msgstr "" + +#: ./doc/admin-guide-cloud/section_object-storage-monitoring.xml104(para) +msgid "" +"A counter increase by the bytes transferred for a metric like " +"tfer.obj.PUT.201." +msgstr "" + +#: ./doc/admin-guide-cloud/section_object-storage-monitoring.xml109(para) +msgid "" +"This is good for getting a feel for the quality of service clients are " +"experiencing with the timing metrics, as well as getting a feel for the " +"volume of the various permutations of request server type, command, and " +"response code. Swift-Informant also requires no change to core Object " +"Storage code because it is implemented as middleware. However, it gives you " +"no insight into the workings of the cluster past the proxy server. If the " +"responsiveness of one storage node degrades, you can only see that some of " +"your requests are bad, either as high latency or error status codes. You do " +"not know exactly why or where that request tried to go. Maybe the container " +"server in question was on a good node but the object server was on a " +"different, poorly-performing node." +msgstr "" + +#: ./doc/admin-guide-cloud/section_object-storage-monitoring.xml125(title) +msgid "Statsdlog" +msgstr "" + +#: ./doc/admin-guide-cloud/section_object-storage-monitoring.xml126(para) +msgid "" +"Florian’s Statsdlog project " +"increments StatsD counters based on logged events. Like Swift-Informant, it " +"is also non-intrusive, but statsdlog can track events from all Object " +"Storage daemons, not just proxy-server. The daemon listens to a UDP stream " +"of syslog messages and StatsD counters are incremented when a log line " +"matches a regular expression. Metric names are mapped to regex match " +"patterns in a JSON file, allowing flexible configuration of what metrics are" +" extracted from the log stream." +msgstr "" + +#: ./doc/admin-guide-cloud/section_object-storage-monitoring.xml137(para) +msgid "" +"Currently, only the first matching regex triggers a StatsD counter " +"increment, and the counter is always incremented by one. There is no way to " +"increment a counter by more than one or send timing data to StatsD based on " +"the log line content. The tool could be extended to handle more metrics for " +"each line and data extraction, including timing data. But a coupling would " +"still exist between the log textual format and the log parsing regexes, " +"which would themselves be more complex to support multiple matches for each " +"line and data extraction. Also, log processing introduces a delay between " +"the triggering event and sending the data to StatsD. It would be preferable " +"to increment error counters where they occur and send timing data as soon as" +" it is known to avoid coupling between a log string and a parsing regex and " +"prevent a time delay between events and sending data to StatsD." +msgstr "" + +#: ./doc/admin-guide-cloud/section_object-storage-monitoring.xml153(para) +msgid "" +"The next section describes another method for gathering Object Storage " +"operational metrics." +msgstr "" + +#: ./doc/admin-guide-cloud/section_object-storage-monitoring.xml157(title) +msgid "Swift StatsD logging" +msgstr "" + +#: ./doc/admin-guide-cloud/section_object-storage-monitoring.xml158(para) +msgid "" +"StatsD (see http://codeascraft.etsy.com/2011/02/15" +"/measure-anything-measure-everything/) was designed for application " +"code to be deeply instrumented; metrics are sent in real-time by the code " +"that just noticed or did something. The overhead of sending a metric is " +"extremely low: a sendto of one UDP packet. If that overhead is " +"still too high, the StatsD client library can send only a random portion of " +"samples and StatsD approximates the actual number when flushing metrics " +"upstream." +msgstr "" + +#: ./doc/admin-guide-cloud/section_object-storage-monitoring.xml169(para) +msgid "" +"To avoid the problems inherent with middleware-based monitoring and after-" +"the-fact log processing, the sending of StatsD metrics is integrated into " +"Object Storage itself. The submitted change set (see https://review.openstack.org/#change,6058)" +" currently reports 124 metrics across 15 Object Storage daemons and the " +"tempauth middleware. Details of the metrics tracked are in the Administrator's" +" Guide." +msgstr "" + +#: ./doc/admin-guide-cloud/section_object-storage-monitoring.xml180(para) +msgid "" +"The sending of metrics is integrated with the logging framework. To enable, " +"configure log_statsd_host in the relevant config file. You can " +"also specify the port and a default sample rate. The specified default " +"sample rate is used unless a specific call to a statsd logging method (see " +"the list below) overrides it. Currently, no logging calls override the " +"sample rate, but it is conceivable that some metrics may require accuracy " +"(sample_rate == 1) while others may not." +msgstr "" + +#: ./doc/admin-guide-cloud/section_object-storage-monitoring.xml195(para) +msgid "" +"Then the LogAdapter object returned by get_logger(), usually " +"stored in self.logger, has these new methods:" +msgstr "" + +#: ./doc/admin-guide-cloud/section_object-storage-monitoring.xml201(para) +msgid "" +"set_statsd_prefix(self, prefix) Sets the client library stat " +"prefix value which gets prefixed to every metric. The default prefix is the " +"“name” of the logger (such as, . “object-server”, “container-auditor”, " +"etc.). This is currently used to turn “proxy-server” into one of “proxy-" +"server.Account”, “proxy-server.Container”, or “proxy-server.Object” as soon " +"as the Controller object is determined and instantiated for the request." +msgstr "" + +#: ./doc/admin-guide-cloud/section_object-storage-monitoring.xml213(para) +msgid "" +"update_stats(self, metric, amount, sample_rate=1) Increments " +"the supplied metric by the given amount. This is used when you need to add " +"or subtract more that one from a counter, like incrementing “suffix.hashes” " +"by the number of computed hashes in the object replicator." +msgstr "" + +#: ./doc/admin-guide-cloud/section_object-storage-monitoring.xml222(para) +msgid "" +"increment(self, metric, sample_rate=1) Increments the given " +"counter metric by one." +msgstr "" + +#: ./doc/admin-guide-cloud/section_object-storage-monitoring.xml227(para) +msgid "" +"decrement(self, metric, sample_rate=1) Lowers the given counter" +" metric by one." +msgstr "" + +#: ./doc/admin-guide-cloud/section_object-storage-monitoring.xml232(para) +msgid "" +"timing(self, metric, timing_ms, sample_rate=1) Record that the " +"given metric took the supplied number of milliseconds." +msgstr "" + +#: ./doc/admin-guide-cloud/section_object-storage-monitoring.xml238(para) +msgid "" +"timing_since(self, metric, orig_time, sample_rate=1) " +"Convenience method to record a timing metric whose value is “now” minus an " +"existing timestamp." +msgstr "" + +#: ./doc/admin-guide-cloud/section_object-storage-monitoring.xml244(para) +msgid "" +"Note that these logging methods may safely be called anywhere you have a " +"logger object. If StatsD logging has not been configured, the methods are " +"no-ops. This avoids messy conditional logic each place a metric is recorded." +" These example usages show the new logging methods:" +msgstr "" + +#: ./doc/admin-guide-cloud/section_object-storage-monitoring.xml287(para) +msgid "" +"The development team of StatsD wanted to use the pystatsd client library " +"(not to be confused with a similar-looking project also hosted on GitHub), but the released " +"version on PyPi was missing two desired features the latest version in " +"GitHub had: the ability to configure a metrics prefix in the client object " +"and a convenience method for sending timing data between “now” and a “start”" +" timestamp you already have. So they just implemented a simple StatsD client" +" library from scratch with the same interface. This has the nice fringe " +"benefit of not introducing another external library dependency into Object " +"Storage." +msgstr "" + +#: ./doc/admin-guide-cloud/section_ts_failed_attach_vol_after_detach.xml5(title) +#: ./doc/admin-guide-cloud/section_ts_HTTP_bad_req_in_cinder_vol_log.xml5(title) +msgid "Failed to attach volume after detaching" +msgstr "" + +#: ./doc/admin-guide-cloud/section_ts_failed_attach_vol_after_detach.xml9(para) +msgid "Failed to attach a volume after detaching the same volume." +msgstr "" + +#: ./doc/admin-guide-cloud/section_ts_failed_attach_vol_after_detach.xml15(para) +msgid "" +"You must change the device name on the command. The VM " +"might not clean up after a command runs. This example shows" +" how the command fails when you use the vdb, " +"vdc, or vdd device names:" +msgstr "" + +#: ./doc/admin-guide-cloud/section_ts_failed_attach_vol_after_detach.xml34(para) +msgid "" +"You might also have this problem after attaching and detaching the same " +"volume from the same VM with the same mount point multiple times. In this " +"case, restart the KVM host." +msgstr "" + +#: ./doc/admin-guide-cloud/section_ts_non_existent_host.xml4(title) +msgid "Non-existent host" +msgstr "" + +#: ./doc/admin-guide-cloud/section_ts_non_existent_host.xml7(para) +msgid "" +"This error could be caused by a volume being exported outside of OpenStack " +"using a host name different from the system name that OpenStack expects. " +"This error could be displayed with the IQN if the host was exported using " +"iSCSI." +msgstr "" + +#: ./doc/admin-guide-cloud/section_ts_non_existent_host.xml15(para) +msgid "" +"Host names constructed by the driver use just the local hostname, not the " +"fully qualified domain name (FQDN) of the Compute host. For example, if the " +"FQDN was myhost.example.com, just " +"myhost would be used as the 3PAR hostname. IP addresses" +" are not allowed as host names on the 3PAR storage server." +msgstr "" + +#. When image changes, this message will be marked fuzzy or untranslated for +#. you. +#. It doesn't matter what you translate it to: it's not used at all. +#: ./doc/admin-guide-cloud/section_networking-scenarios.xml38(None) +#: ./doc/admin-guide-cloud/section_networking-scenarios.xml406(None) +msgid "" +"@@image: '../common/figures/under-the-hood-scenario-1.png'; " +"md5=6c8c80ff7e23cc2c7c7e1aa66e1fd8c0" +msgstr "" + +#. When image changes, this message will be marked fuzzy or untranslated for +#. you. +#. It doesn't matter what you translate it to: it's not used at all. +#: ./doc/admin-guide-cloud/section_networking-scenarios.xml79(None) +msgid "" +"@@image: '../common/figures/under-the-hood-scenario-1-ovs-compute.png'; " +"md5=46509fcb546df0f43adb5350f2dd9fab" +msgstr "" + +#. When image changes, this message will be marked fuzzy or untranslated for +#. you. +#. It doesn't matter what you translate it to: it's not used at all. +#: ./doc/admin-guide-cloud/section_networking-scenarios.xml172(None) +msgid "" +"@@image: '../common/figures/under-the-hood-scenario-1-ovs-network.png'; " +"md5=8eea1c1dbde433c46666c985751c3276" +msgstr "" + +#. When image changes, this message will be marked fuzzy or untranslated for +#. you. +#. It doesn't matter what you translate it to: it's not used at all. +#: ./doc/admin-guide-cloud/section_networking-scenarios.xml252(None) +msgid "" +"@@image: '../common/figures/under-the-hood-scenario-1-ovs-netns.png'; " +"md5=de52650e491e4dc2946e827cd93e0a85" +msgstr "" + +#. When image changes, this message will be marked fuzzy or untranslated for +#. you. +#. It doesn't matter what you translate it to: it's not used at all. +#: ./doc/admin-guide-cloud/section_networking-scenarios.xml298(None) +#: ./doc/admin-guide-cloud/section_networking-scenarios.xml503(None) +msgid "" +"@@image: '../common/figures/under-the-hood-scenario-2.png'; " +"md5=148feb87744e7b04da21ec4f17503c75" +msgstr "" + +#. When image changes, this message will be marked fuzzy or untranslated for +#. you. +#. It doesn't matter what you translate it to: it's not used at all. +#: ./doc/admin-guide-cloud/section_networking-scenarios.xml340(None) +msgid "" +"@@image: '../common/figures/under-the-hood-scenario-2-ovs-compute.png'; " +"md5=94603b4ec7904ac04bc1ed81a2d38f79" +msgstr "" + +#. When image changes, this message will be marked fuzzy or untranslated for +#. you. +#. It doesn't matter what you translate it to: it's not used at all. +#: ./doc/admin-guide-cloud/section_networking-scenarios.xml355(None) +msgid "" +"@@image: '../common/figures/under-the-hood-scenario-2-ovs-network.png'; " +"md5=80aa67268b5ce7deddc41845e6313634" +msgstr "" + +#. When image changes, this message will be marked fuzzy or untranslated for +#. you. +#. It doesn't matter what you translate it to: it's not used at all. +#: ./doc/admin-guide-cloud/section_networking-scenarios.xml364(None) +msgid "" +"@@image: '../common/figures/under-the-hood-scenario-2-ovs-netns.png'; " +"md5=d8878beff47037240d6f8c48f8d4d4c3" +msgstr "" + +#. When image changes, this message will be marked fuzzy or untranslated for +#. you. +#. It doesn't matter what you translate it to: it's not used at all. +#: ./doc/admin-guide-cloud/section_networking-scenarios.xml446(None) +msgid "" +"@@image: '../common/figures/under-the-hood-scenario-1-linuxbridge-" +"compute.png'; md5=8270a65d291a628c7091997414046167" +msgstr "" + +#. When image changes, this message will be marked fuzzy or untranslated for +#. you. +#. It doesn't matter what you translate it to: it's not used at all. +#: ./doc/admin-guide-cloud/section_networking-scenarios.xml484(None) +msgid "" +"@@image: '../common/figures/under-the-hood-scenario-1-linuxbridge-" +"network.png'; md5=bd78453eb11ffebddf55484ca2cd125e" +msgstr "" + +#. When image changes, this message will be marked fuzzy or untranslated for +#. you. +#. It doesn't matter what you translate it to: it's not used at all. +#: ./doc/admin-guide-cloud/section_networking-scenarios.xml491(None) +msgid "" +"@@image: '../common/figures/under-the-hood-scenario-1-linuxbridge-" +"netns.png'; md5=915d10e90cbb18e887b4d5eb5ea15e58" +msgstr "" + +#. When image changes, this message will be marked fuzzy or untranslated for +#. you. +#. It doesn't matter what you translate it to: it's not used at all. +#: ./doc/admin-guide-cloud/section_networking-scenarios.xml546(None) +msgid "" +"@@image: '../common/figures/under-the-hood-scenario-2-linuxbridge-" +"compute.png'; md5=f68f0baeba932b219574e55853bd2300" +msgstr "" + +#. When image changes, this message will be marked fuzzy or untranslated for +#. you. +#. It doesn't matter what you translate it to: it's not used at all. +#: ./doc/admin-guide-cloud/section_networking-scenarios.xml559(None) +msgid "" +"@@image: '../common/figures/under-the-hood-scenario-2-linuxbridge-" +"network.png'; md5=25f818f7f9148152e5a8dbf6d530dcf6" +msgstr "" + +#. When image changes, this message will be marked fuzzy or untranslated for +#. you. +#. It doesn't matter what you translate it to: it's not used at all. +#: ./doc/admin-guide-cloud/section_networking-scenarios.xml567(None) +msgid "" +"@@image: '../common/figures/under-the-hood-scenario-2-linuxbridge-" +"netns.png'; md5=cdc0bd4b3e7988f7fedffefae4dae9d0" +msgstr "" + +#. When image changes, this message will be marked fuzzy or untranslated for +#. you. +#. It doesn't matter what you translate it to: it's not used at all. +#: ./doc/admin-guide-cloud/section_networking-scenarios.xml599(None) +msgid "" +"@@image: '../common/figures/ml2_without_l2pop_full_mesh.png'; " +"md5=881485c0686f20b82967d5b817932952" +msgstr "" + +#. When image changes, this message will be marked fuzzy or untranslated for +#. you. +#. It doesn't matter what you translate it to: it's not used at all. +#: ./doc/admin-guide-cloud/section_networking-scenarios.xml609(None) +msgid "" +"@@image: '../common/figures/ml2_without_l2pop_partial_mesh.png'; " +"md5=66fe83560a3e1880ffe3a85d80538f83" +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking-scenarios.xml6(title) +msgid "Networking scenarios" +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking-scenarios.xml7(para) +msgid "" +"This chapter describes two networking scenarios and how the Open vSwitch " +"plug-in and the Linux bridging plug-in implement these scenarios." +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking-scenarios.xml12(para) +msgid "" +"This section describes how the Open vSwitch plug-in implements the " +"Networking abstractions." +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking-scenarios.xml16(para) +msgid "" +"This example uses VLAN isolation on the switches to isolate tenant networks." +" This configuration labels the physical network associated with the public " +"network as physnet1, and the physical network associated " +"with the data network as physnet2, which leads to the " +"following configuration options in " +"ovs_neutron_plugin.ini:" +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking-scenarios.xml29(title) +#: ./doc/admin-guide-cloud/section_networking-scenarios.xml397(title) +msgid "Scenario 1: one tenant, two networks, one router" +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking-scenarios.xml30(para) +msgid "" +"The first scenario has two private networks (net01, and " +"net02), each with one subnet " +"(net01_subnet01: 192.168.101.0/24, " +"net02_subnet01, 192.168.102.0/24). Both private networks " +"are attached to a router that connects them to the public network " +"(10.64.201.0/24)." +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking-scenarios.xml41(para) +#: ./doc/admin-guide-cloud/section_networking-scenarios.xml409(para) +msgid "" +"Under the service tenant, create the shared router, " +"define the public network, and set it as the default gateway of the " +"router" +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking-scenarios.xml52(para) +#: ./doc/admin-guide-cloud/section_networking-scenarios.xml420(para) +msgid "" +"Under the demo user tenant, create the private network " +"net01 and corresponding subnet, and connect it to the " +"router01 router. Configure it to use VLAN ID 101 on the " +"physical switch." +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking-scenarios.xml63(para) +#: ./doc/admin-guide-cloud/section_networking-scenarios.xml431(para) +msgid "" +"Similarly, for net02, using VLAN ID 102 on the physical " +"switch:" +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking-scenarios.xml73(title) +#: ./doc/admin-guide-cloud/section_networking-scenarios.xml440(title) +msgid "Scenario 1: Compute host config" +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking-scenarios.xml74(para) +msgid "" +"The following figure shows how to configure various Linux networking devices" +" on the compute host:" +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking-scenarios.xml84(title) +#: ./doc/admin-guide-cloud/section_networking-scenarios.xml451(title) +msgid "Types of network devices" +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking-scenarios.xml85(para) +msgid "" +"There are four distinct type of virtual networking devices: TAP devices, " +"veth pairs, Linux bridges, and Open vSwitch bridges. For an ethernet frame " +"to travel from eth0 of virtual machine " +"vm01 to the physical network, it must pass through nine " +"devices inside of the host: TAP vnet0, Linux bridge " +"qbrnnn, veth pair " +"(qvbnnn, " +"qvonnn), Open vSwitch bridge br-int, veth pair (int-br-eth1, phy-br-eth1), " +"and, finally, the physical network interface card eth1." +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking-scenarios.xml96(para) +#: ./doc/admin-guide-cloud/section_networking-scenarios.xml460(para) +msgid "" +"A TAP device, such as " +"vnet0 is how hypervisors such as KVM and Xen implement a " +"virtual network interface card (typically called a VIF or vNIC). An ethernet" +" frame sent to a TAP device is received by the guest operating system." +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking-scenarios.xml100(para) +msgid "" +"A veth pair is a pair of directly " +"connected virtual network interfaces. An ethernet frame sent to one end of a" +" veth pair is received by the other end of a veth pair. Networking uses veth" +" pairs as virtual patch cables to make connections between virtual bridges." +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking-scenarios.xml104(para) +#: ./doc/admin-guide-cloud/section_networking-scenarios.xml473(para) +msgid "" +"A Linux bridge behaves like a hub: you " +"can connect multiple (physical or virtual) network interfaces devices to a " +"Linux bridge. Any ethernet frames that come in from one interface attached " +"to the bridge is transmitted to all of the other devices." +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking-scenarios.xml108(para) +msgid "" +"An Open vSwitch bridge behaves like a " +"virtual switch: network interface devices connect to Open vSwitch bridge's " +"ports, and the ports can be configured much like a physical switch's ports, " +"including VLAN configurations." +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking-scenarios.xml114(title) +msgid "Integration bridge" +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking-scenarios.xml115(para) +msgid "" +"The br-int OpenvSwitch bridge is the integration bridge: " +"all guests running on the compute host connect to this bridge. Networking " +"implements isolation across these guests by configuring the br-" +"int ports." +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking-scenarios.xml121(title) +msgid "Physical connectivity bridge" +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking-scenarios.xml122(para) +msgid "" +"The br-eth1 bridge provides connectivity to the physical " +"network interface card, eth1. It connects to the " +"integration bridge by a veth pair: (int-br-eth1, phy-br-" +"eth1)." +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking-scenarios.xml127(title) +msgid "VLAN translation" +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking-scenarios.xml128(para) +msgid "" +"In this example, net01 and net02 have VLAN ids of 1 and 2, respectively. " +"However, the physical network in our example only supports VLAN IDs in the " +"range 101 through 110. The Open vSwitch agent is responsible for configuring" +" flow rules on br-int and br-eth1 to " +"do VLAN translation. When br-eth1 receives a frame marked" +" with VLAN ID 1 on the port associated with phy-br-eth1, " +"it modifies the VLAN ID in the frame to 101. Similarly, when br-" +"int receives a frame marked with VLAN ID 101 on the port " +"associated with int-br-eth1, it modifies the VLAN ID in " +"the frame to 1." +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking-scenarios.xml139(title) +msgid "Security groups: iptables and Linux bridges" +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking-scenarios.xml140(para) +msgid "" +"Ideally, the TAP device vnet0 would be connected directly" +" to the integration bridge, br-int. Unfortunately, this " +"isn't possible because of how OpenStack security groups are currently " +"implemented. OpenStack uses iptables rules on the TAP devices such as " +"vnet0 to implement security groups, and Open vSwitch is " +"not compatible with iptables rules that are applied directly on TAP devices " +"that are connected to an Open vSwitch port." +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking-scenarios.xml147(para) +msgid "" +"Networking uses an extra Linux bridge and a veth pair as a workaround for " +"this issue. Instead of connecting vnet0 to an Open " +"vSwitch bridge, it is connected to a Linux bridge, " +"qbrXXX. This bridge is " +"connected to the integration bridge, br-int, through the " +"(qvbXXX, " +"qvoXXX) veth pair." +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking-scenarios.xml157(title) +#: ./doc/admin-guide-cloud/section_networking-scenarios.xml480(title) +msgid "Scenario 1: Network host config" +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking-scenarios.xml158(para) +msgid "" +"The network host runs the neutron-openvswitch-plugin-agent, the neutron-" +"dhcp-agent, neutron-l3-agent, and neutron-metadata-agent services." +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking-scenarios.xml160(para) +msgid "" +"On the network host, assume that eth0 is connected to the external network, " +"and eth1 is connected to the data network, which leads to the following " +"configuration in the ovs_neutron_plugin.ini file: " +" The following figure shows the network devices on the " +"network host:" +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking-scenarios.xml175(para) +msgid "" +"As on the compute host, there is an Open vSwitch integration bridge " +"(br-int) and an Open vSwitch bridge connected to the data" +" network (br-eth1), and the two are connected by a veth " +"pair, and the neutron-openvswitch-plugin-agent configures the ports on both " +"switches to do VLAN translation." +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking-scenarios.xml180(para) +msgid "" +"An additional Open vSwitch bridge, br-ex, connects to the" +" physical interface that is connected to the external network. In this " +"example, that physical interface is eth0." +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking-scenarios.xml183(para) +msgid "" +"While the integration bridge and the external bridge are connected by a veth" +" pair (int-br-ex, phy-br-ex), this example uses layer 3 " +"connectivity to route packets from the internal networks to the public " +"network: no packets traverse that veth pair in this example." +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking-scenarios.xml187(title) +msgid "Open vSwitch internal ports" +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking-scenarios.xml188(para) +msgid "" +"The network host uses Open vSwitch internal " +"ports. Internal ports enable you to assign one or more IP " +"addresses to an Open vSwitch bridge. In previous example, the br-" +"int bridge has four internal ports: " +"tapXXX, " +"qr-YYY, " +"qr-ZZZ, and " +"tapWWW. Each internal port has" +" a separate IP address associated with it. An internal port, qg-" +"VVV, is on the br-ex bridge." +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking-scenarios.xml201(para) +msgid "" +"By default, The Networking DHCP agent uses a process called dnsmasq to " +"provide DHCP services to guests. Networking must create an internal port for" +" each network that requires DHCP services and attach a dnsmasq process to " +"that port. In the previous example, the " +"tapXXX interface is on " +"net01_subnet01, and the " +"tapWWW interface is on " +"net02_subnet01." +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking-scenarios.xml211(title) +msgid "L3 agent (routing)" +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking-scenarios.xml212(para) +msgid "" +"The Networking L3 agent uses Open vSwitch internal ports to implement " +"routing and relies on the network host to route the packets across the " +"interfaces. In this example, the qr-YYY interface is on " +"net01_subnet01 and has the IP address 192.168.101.1/24. " +"The qr-ZZZ, interface is on " +"net02_subnet01 and has the IP address " +"192.168.102.1/24. The " +"qg-VVV interface has the IP " +"address 10.64.201.254/24. Because each of these " +"interfaces is visible to the network host operating system, the network host" +" routes the packets across the interfaces, as long as an administrator has " +"enabled IP forwarding." +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking-scenarios.xml224(para) +msgid "" +"The L3 agent uses iptables to implement floating IPs to do the network " +"address translation (NAT)." +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking-scenarios.xml228(title) +msgid "Overlapping subnets and network namespaces" +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking-scenarios.xml229(para) +msgid "" +"One problem with using the host to implement routing is that one of the " +"Networking subnets might overlap with one of the physical networks that the " +"host uses. For example, if the management network is implemented on " +"eth2 and also happens to be on the " +"192.168.101.0/24 subnet, routing problems will occur " +"because the host can't determine whether to send a packet on this subnet to " +"qr-YYY or eth2. If end users are " +"permitted to create their own logical networks and subnets, you must design " +"the system so that such collisions do not occur." +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking-scenarios.xml238(para) +msgid "" +"Networking uses Linux network namespaces " +"to prevent collisions between the physical networks on the " +"network host, and the logical networks used by the virtual machines. It also" +" prevents collisions across different logical networks that are not routed " +"to each other, as the following scenario shows." +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking-scenarios.xml243(para) +msgid "" +"A network namespace is an isolated environment with its own networking " +"stack. A network namespace has its own network interfaces, routes, and " +"iptables rules. Consider it a chroot jail, except for networking instead of " +"for a file system. LXC (Linux containers) use network namespaces to " +"implement networking virtualization." +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking-scenarios.xml248(para) +msgid "" +"Networking creates network namespaces on the network host to avoid subnet " +"collisions." +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking-scenarios.xml257(para) +msgid "" +"qdhcp-aaa: contains the " +"tapXXX interface and the " +"dnsmasq process that listens on that interface to provide DHCP services for " +"net01_subnet01. This allows overlapping IPs between " +"net01_subnet01 and any other subnets on the network host." +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking-scenarios.xml267(para) +msgid "" +"qrouter-bbbb: contains the " +"qr-YYY, " +"qr-ZZZ, and " +"qg-VVV interfaces, and the " +"corresponding routes. This namespace implements router01 " +"in our example." +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking-scenarios.xml276(para) +msgid "" +"qdhcp-ccc: contains the " +"tapWWW interface and the " +"dnsmasq process that listens on that interface, to provide DHCP services for" +" net02_subnet01. This allows overlapping IPs between " +"net02_subnet01 and any other subnets on the network host." +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking-scenarios.xml255(para) +msgid "" +"In this example, there are three network namespaces, as shown in the figure " +"above:" +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking-scenarios.xml290(title) +#: ./doc/admin-guide-cloud/section_networking-scenarios.xml497(title) +msgid "Scenario 2: two tenants, two networks, two routers" +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking-scenarios.xml292(para) +msgid "" +"In this scenario, tenant A and tenant B each have a network with one subnet " +"and one router that connects the tenants to the public Internet." +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking-scenarios.xml301(para) +#: ./doc/admin-guide-cloud/section_networking-scenarios.xml506(para) +msgid "" +"Under the service tenant, define the public " +"network:" +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking-scenarios.xml309(para) +#: ./doc/admin-guide-cloud/section_networking-scenarios.xml514(para) +msgid "" +"Under the tenantA user tenant, create the tenant router " +"and set its gateway for the public network. Then, define " +"private network net01 using VLAN ID 102 on the physical " +"switch, along with its subnet, and connect it to the router. " +"" +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking-scenarios.xml322(para) +#: ./doc/admin-guide-cloud/section_networking-scenarios.xml527(para) +msgid "" +"Similarly, for tenantB, create a router and another " +"network, using VLAN ID 102 on the physical switch:" +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking-scenarios.xml335(title) +#: ./doc/admin-guide-cloud/section_networking-scenarios.xml540(title) +msgid "Scenario 2: Compute host config" +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking-scenarios.xml336(para) +msgid "" +"The following figure shows how to configure Linux networking devices on the " +"Compute host:" +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking-scenarios.xml343(para) +msgid "" +"The Compute host configuration resembles the configuration in scenario 1. " +"However, in scenario 1, a guest connects to two subnets while in this " +"scenario, the subnets belong to different tenants." +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking-scenarios.xml350(title) +#: ./doc/admin-guide-cloud/section_networking-scenarios.xml554(title) +msgid "Scenario 2: Network host config" +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking-scenarios.xml351(para) +#: ./doc/admin-guide-cloud/section_networking-scenarios.xml555(para) +msgid "" +"The following figure shows the network devices on the network host for the " +"second scenario." +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking-scenarios.xml358(para) +msgid "" +"In this configuration, the network namespaces are organized to isolate the " +"two subnets from each other as shown in the following figure." +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking-scenarios.xml367(para) +#: ./doc/admin-guide-cloud/section_networking-scenarios.xml570(para) +msgid "" +"In this scenario, there are four network namespaces " +"(qhdcp-aaa, " +"qrouter-bbbb, " +"qrouter-cccc, and " +"qhdcp-dddd), instead of three." +" Since there is no connectivity between the two networks, and so each router" +" is implemented by a separate namespace." +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking-scenarios.xml379(para) +msgid "" +"This section describes how the Linux Bridge plug-in implements the " +"Networking abstractions. For information about DHCP and L3 agents, see ." +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking-scenarios.xml384(para) +msgid "" +"This example uses VLAN isolation on the switches to isolate tenant networks." +" This configuration labels the physical network associated with the public " +"network as physnet1, and the physical network associated " +"with the data network as physnet2, which leads to the " +"following configuration options in " +"linuxbridge_conf.ini:" +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking-scenarios.xml398(para) +msgid "" +"The first scenario has two private networks (net01, and " +"net02), each with one subnet " +"(net01_subnet01: 192.168.101.0/24, " +"net02_subnet01, 192.168.102.0/24). Both private networks " +"are attached to a router that contains them to the public network " +"(10.64.201.0/24)." +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking-scenarios.xml441(para) +msgid "" +"The following figure shows how to configure the various Linux networking " +"devices on the compute host." +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking-scenarios.xml452(para) +msgid "" +"There are three distinct type of virtual networking devices: TAP devices, " +"VLAN devices, and Linux bridges. For an ethernet frame to travel from " +"eth0 of virtual machine vm01, to the " +"physical network, it must pass through four devices inside of the host: TAP " +"vnet0, Linux bridge " +"brqXXX, VLAN " +"eth1.101), and, finally, the physical network interface " +"card eth1." +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking-scenarios.xml464(para) +msgid "" +"A VLAN device is associated with a VLAN" +" tag attaches to an existing interface device and adds or removes VLAN tags." +" In the preceding example, VLAN device eth1.101 is " +"associated with VLAN ID 101 and is attached to interface " +"eth1. Packets received from the outside by " +"eth1 with VLAN tag 101 will be passed to device " +"eth1.101, which will then strip the tag. In the other " +"direction, any ethernet frame sent directly to eth1.101 will have VLAN tag " +"101 added and will be forward to eth1 for sending out to " +"the network." +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking-scenarios.xml481(para) +msgid "The following figure shows the network devices on the network host." +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking-scenarios.xml487(para) +msgid "" +"The following figure shows how the Linux Bridge plug-in uses network " +"namespaces to provide isolation." +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking-scenarios.xml488(para) +msgid "" +"veth pairs form connections between the Linux bridges and the network " +"namespaces." +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking-scenarios.xml498(para) +msgid "" +"The second scenario has two tenants (A, B). Each tenant has a network with " +"one subnet, and each one has a router that connects them to the public " +"Internet." +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking-scenarios.xml541(para) +msgid "" +"The following figure shows how the various Linux networking devices would be" +" configured on the compute host under this scenario." +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking-scenarios.xml549(para) +msgid "" +"The configuration on the compute host is very similar to the configuration " +"in scenario 1. The only real difference is that scenario 1 had a guest that " +"was connected to two subnets, and in this scenario, the subnets belong to " +"different tenants." +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking-scenarios.xml562(para) +msgid "" +"The main difference between the configuration in this scenario and the " +"previous one is the organization of the network namespaces, in order to " +"provide isolation across the two subnets, as shown in the following figure." +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking-scenarios.xml582(para) +msgid "" +"The Modular Layer 2 plugin allows OpenStack Networking to simultaneously " +"utilize the variety of layer 2 networking technologies found in complex " +"real-world data centers. It currently includes drivers for the local, flat, " +"vlan, gre and vxlan network types and works with the existing Open" +" vSwitch, Linux Bridge, and " +"HyperV L2 agents. The ML2 plug-in " +"can be extended through mechanism drivers, multiple mechanisms can be used " +"simultaneously. This section describes different ML2 " +"plug-in / agents configurations with different type drivers and mechanism " +"drivers." +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking-scenarios.xml592(title) +msgid "ML2 with L2 population mechanism driver" +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking-scenarios.xml593(para) +msgid "" +"Current Open vSwitch and Linux " +"Bridge tunneling implementations broadcast to every agent, even " +"if they don’t host the corresponding network as illustrated below." +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking-scenarios.xml602(para) +msgid "" +"As broadcast emulation on overlay is costly, it may be better to avoid its " +"use for mac learning and ARP resolution. This supposes the use of proxy ARP " +"on the agent to answer VM requests, and to populate forwarding table. " +"Currently only the Linux Bridge Agent implements an ARP" +" proxy. The prepopulation limits L2 broadcasts in overlay, however it may " +"anyway be necessary to provide broadcast emulation. This is achieved by " +"sending broadcasts packets over unicasts only to the relevant agents as " +"illustrated below.The partial-mesh is available with the " +"Open vSwitch and the Linux Bridge " +"agent. The following scenarios will use the L2 population mechanism driver " +"with an Open vSwitch agent and a Linux " +"Bridge agent. To enable the l2 population driver we have to add " +"it in the list of mechanism drivers. We also need to have at least one " +"tunneling type driver enabled, either GRE, VXLAN or both. Below " +"configuration options that we have to set in " +"ml2_conf.ini:" +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking-scenarios.xml621(title) +msgid "Scenario 1: L2 population with Open vSwitch agent" +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking-scenarios.xml625(replaceable) +#: ./doc/admin-guide-cloud/section_networking-scenarios.xml637(replaceable) +msgid "192.168.1.10" +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking-scenarios.xml628(replaceable) +#: ./doc/admin-guide-cloud/section_networking_adv_features.xml184(literal) +#: ./doc/admin-guide-cloud/section_networking_adv_features.xml191(literal) +#: ./doc/admin-guide-cloud/section_networking_adv_features.xml208(literal) +msgid "gre" +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking-scenarios.xml628(replaceable) +msgid "vxlan" +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking-scenarios.xml622(para) +msgid "" +"We have to enable the l2 population extension on the Open " +"vSwitch agent side and we also have to set the " +" parameter and the " +"ml2_conf.ini." +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking-scenarios.xml632(title) +msgid "Scenario 2: L2 population with Linux Bridge agent" +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking-scenarios.xml633(para) +msgid "" +"We have to enable the l2 population extension on the agent side and we also " +"have to set the local_ip parameter and enable VXLAN in " +"ml2_conf.ini." +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking-scenarios.xml641(title) +msgid "Enable security group API" +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking-scenarios.xml642(para) +msgid "" +"Since the ML2 plugin can concurrently support different L2 agents (or other " +"mechanisms) with different configuration files, the actual " +" value in the " +"ml2_conf.ini file does not matter in the server, but " +" must be set to a non-default value in the " +"ml2 configuration to enable the securitygroup extension. To enable " +"securitygroup API, edit the ml2_conf.ini " +"file: Each L2 agent configuration file (such as " +"ovs_neutron_plugin.ini or " +"linuxbridge_conf.ini) should contain the appropriate " +" value for that agent. To disable " +"securitygroup API, edit the ml2_conf.ini " +"file: Also, each L2 agent configuration file (such as " +"ovs_neutron_plugin.ini or " +"linuxbridge_conf.ini) should contain this value in " +" parameter for that agent." +msgstr "" + +#: ./doc/admin-guide-cloud/ch_networking.xml7(title) +msgid "Networking" +msgstr "" + +#: ./doc/admin-guide-cloud/ch_networking.xml8(para) +msgid "" +"Learn Networking concepts, architecture, and basic and advanced neutron and " +"nova command-line interface (CLI) cloud." +msgstr "" + +#: ./doc/admin-guide-cloud/bk-admin-guide-cloud.xml8(title) +msgid "OpenStack Cloud Administrator Guide" +msgstr "" + +#: ./doc/admin-guide-cloud/bk-admin-guide-cloud.xml10(titleabbrev) +msgid "Cloud Administrator Guide" +msgstr "" + +#: ./doc/admin-guide-cloud/bk-admin-guide-cloud.xml18(orgname) +#: ./doc/admin-guide-cloud/bk-admin-guide-cloud.xml23(holder) +msgid "OpenStack Foundation" +msgstr "" + +#: ./doc/admin-guide-cloud/bk-admin-guide-cloud.xml22(year) +msgid "2013" +msgstr "" + +#: ./doc/admin-guide-cloud/bk-admin-guide-cloud.xml25(releaseinfo) +msgid "havana" +msgstr "" + +#: ./doc/admin-guide-cloud/bk-admin-guide-cloud.xml26(productname) +msgid "OpenStack" +msgstr "" + +#: ./doc/admin-guide-cloud/bk-admin-guide-cloud.xml30(remark) +msgid "Copyright details are filled in by the template." +msgstr "" + +#: ./doc/admin-guide-cloud/bk-admin-guide-cloud.xml36(remark) +msgid "Remaining licensing details are filled in by the template." +msgstr "" + +#: ./doc/admin-guide-cloud/bk-admin-guide-cloud.xml41(para) +msgid "" +"OpenStack offers open source software for cloud administrators to manage and" +" troubleshoot an OpenStack cloud." +msgstr "" + +#: ./doc/admin-guide-cloud/bk-admin-guide-cloud.xml48(date) +msgid "2013-11-12" +msgstr "" + +#: ./doc/admin-guide-cloud/bk-admin-guide-cloud.xml52(para) +msgid "" +"Adds options for tuning operational status synchronization in the NVP plug-" +"in." +msgstr "" + +#: ./doc/admin-guide-cloud/bk-admin-guide-cloud.xml60(date) +msgid "2013-10-17" +msgstr "" + +#: ./doc/admin-guide-cloud/bk-admin-guide-cloud.xml64(para) +msgid "Havana release." +msgstr "" + +#: ./doc/admin-guide-cloud/bk-admin-guide-cloud.xml70(date) +msgid "2013-09-05" +msgstr "" + +#: ./doc/admin-guide-cloud/bk-admin-guide-cloud.xml74(para) +msgid "Moves object storage monitoring section to this guide." +msgstr "" + +#: ./doc/admin-guide-cloud/bk-admin-guide-cloud.xml78(para) +msgid "Removes redundant object storage information." +msgstr "" + +#: ./doc/admin-guide-cloud/bk-admin-guide-cloud.xml85(date) +msgid "2013-09-03" +msgstr "" + +#: ./doc/admin-guide-cloud/bk-admin-guide-cloud.xml89(para) +msgid "" +"Moved all but configuration and installation information from these " +"component guides to create the new guide:" +msgstr "" + +#: ./doc/admin-guide-cloud/bk-admin-guide-cloud.xml95(para) +msgid "OpenStack Compute Administration Guide" +msgstr "" + +#: ./doc/admin-guide-cloud/bk-admin-guide-cloud.xml99(para) +msgid "OpenStack Networking Administration Guide" +msgstr "" + +#: ./doc/admin-guide-cloud/bk-admin-guide-cloud.xml103(para) +msgid "OpenStack Object Storage Administration Guide" +msgstr "" + +#: ./doc/admin-guide-cloud/bk-admin-guide-cloud.xml107(para) +msgid "OpenStack Block Storage Service Administration Guide" +msgstr "" + +#: ./doc/admin-guide-cloud/section_ts_no_emulator_x86_64.xml4(title) +msgid "Cannot find suitable emulator for x86_64" +msgstr "" + +#: ./doc/admin-guide-cloud/section_ts_no_emulator_x86_64.xml7(para) +msgid "" +"When you attempt to create a VM, the error shows the VM is in the " +"BUILD then ERROR state." +msgstr "" + +#: ./doc/admin-guide-cloud/section_ts_no_emulator_x86_64.xml12(para) +msgid "" +"On the KVM host run, cat /proc/cpuinfo. Make sure the " +"vme and svm flags are set." +msgstr "" + +#: ./doc/admin-guide-cloud/section_ts_no_emulator_x86_64.xml14(para) +msgid "" +"Follow the instructions in the enabling KVM " +"section of the Configuration Reference to " +"enable hardware virtualization support in your BIOS." +msgstr "" + +#. When image changes, this message will be marked fuzzy or untranslated for +#. you. +#. It doesn't matter what you translate it to: it's not used at all. +#: ./doc/admin-guide-cloud/section_networking_arch.xml132(None) +msgid "" +"@@image: '../common/figures/Neutron-PhysNet-Diagram.png'; " +"md5=ac17dba8837f9d7ba714a692c60e68ab" +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking_arch.xml4(title) +msgid "Networking architecture" +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking_arch.xml5(para) +msgid "" +"Before you deploy Networking, it helps to understand the Networking " +"components and how these components interact with each other and other " +"OpenStack services." +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking_arch.xml9(title) +msgid "Overview" +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking_arch.xml10(para) +msgid "" +"Networking is a standalone service, just like other OpenStack services such " +"as Compute, Image service, Identity service, or the Dashboard. Like those " +"services, a deployment of Networking often involves deploying several " +"processes on a variety of hosts." +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking_arch.xml16(para) +msgid "" +"The Networking server uses the neutron-" +"server daemon to expose the Networking API and to pass user " +"requests to the configured Networking plug-in for additional processing. " +"Typically, the plug-in requires access to a database for persistent storage " +"(also similar to other OpenStack services)." +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking_arch.xml23(para) +msgid "" +"If your deployment uses a controller host to run centralized Compute " +"components, you can deploy the Networking server on that same host. However," +" Networking is entirely standalone and can be deployed on its own host as " +"well. Depending on your deployment, Networking can also include the " +"following agents." +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking_arch.xml30(caption) +msgid "Networking agents" +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking_arch.xml41(emphasis) +msgid "plug-in agent" +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking_arch.xml43(literal) +msgid "neutron-*-agent" +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking_arch.xml41(td) +#: ./doc/admin-guide-cloud/section_networking_arch.xml51(td) +#: ./doc/admin-guide-cloud/section_networking_arch.xml59(td) +#: ./doc/admin-guide-cloud/section_networking_arch.xml68(td) +msgid " ()" +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking_arch.xml44(td) +msgid "" +"Runs on each hypervisor to perform local vswitch configuration. The agent " +"that runs depends on the plug-in that you use, and some plug-ins do not " +"require an agent." +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking_arch.xml51(emphasis) +msgid "dhcp agent" +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking_arch.xml53(literal) +msgid "neutron-dhcp-agent" +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking_arch.xml54(td) +msgid "" +"Provides DHCP services to tenant networks. Some plug-ins use this agent." +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking_arch.xml59(emphasis) +msgid "l3 agent" +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking_arch.xml61(literal) +msgid "neutron-l3-agent" +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking_arch.xml62(td) +msgid "" +"Provides L3/NAT forwarding to provide external network access for VMs on " +"tenant networks. Some plug-ins use this agent." +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking_arch.xml68(emphasis) +msgid "l3 metering agent" +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking_arch.xml69(literal) +msgid "neutron-metering-agent" +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking_arch.xml70(td) +msgid "Provides L3 traffic measurements for tenant networks." +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking_arch.xml75(para) +msgid "" +"These agents interact with the main neutron process through RPC (for " +"example, rabbitmq or qpid) or through the standard Networking API. Further:" +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking_arch.xml80(para) +msgid "" +"Networking relies on the Identity service (Keystone) for the authentication " +"and authorization of all API requests." +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking_arch.xml85(para) +msgid "" +"Compute (Nova) interacts with Networking through calls to its standard API." +"  As part of creating a VM, the nova-" +"compute service communicates with the Networking API to plug " +"each virtual NIC on the VM into a particular network. " +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking_arch.xml94(para) +msgid "" +"The Dashboard (Horizon) integrates with the Networking API, enabling " +"administrators and tenant users to create and manage network services " +"through a web-based GUI." +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking_arch.xml102(title) +msgid "Place services on physical hosts" +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking_arch.xml103(para) +msgid "" +"Like other OpenStack services, Networking enables cloud administrators to " +"run one or more services on one or more physical devices. At one extreme, " +"the cloud administrator can run all service daemons on a single physical " +"host for evaluation purposes. Alternatively the cloud administrator can run " +"each service on its own physical host and, in some cases, can replicate " +"services across multiple hosts for redundancy. For more information, see the" +" OpenStack Configuration Reference." +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking_arch.xml116(para) +msgid "" +"A standard architecture includes a cloud controller host, a network gateway " +"host, and a set of hypervisors that run virtual machines. The cloud " +"controller and network gateway can be on the same host. However, if you " +"expect VMs to send significant traffic to or from the Internet, a dedicated " +"network gateway host helps avoid CPU contention between the neutron-l3-agent and other OpenStack services" +" that forward packets." +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking_arch.xml127(title) +msgid "Network connectivity for physical hosts" +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking_arch.xml135(para) +msgid "" +"A standard Networking set up has one or more of the following distinct " +"physical data center networks." +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking_arch.xml141(caption) +msgid "General distinct physical data center networks" +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking_arch.xml153(emphasis) +msgid "Management network" +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking_arch.xml155(td) +msgid "" +"Provides internal communication between OpenStack Components. IP addresses " +"on this network should be reachable only within the data center." +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking_arch.xml162(emphasis) +msgid "Data network" +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking_arch.xml164(td) +msgid "" +"Provides VM data communication within the cloud deployment. The IP " +"addressing requirements of this network depend on the Networking plug-in " +"that is used." +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking_arch.xml171(emphasis) +msgid "External network" +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking_arch.xml173(td) +msgid "" +"Provides VMs with Internet access in some deployment scenarios. Anyone on " +"the Internet can reach IP addresses on this network." +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking_arch.xml179(emphasis) +msgid "API network" +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking_arch.xml181(td) +msgid "" +"Exposes all OpenStack APIs, including the Networking API, to tenants. IP " +"addresses on this network should be reachable by anyone on the Internet. The" +" API network might be the same as the external network, because it is " +"possible to create an external-network subnet that is allocated IP ranges " +"that use less than the full range of IP addresses in an IP block." +msgstr "" + +#: ./doc/admin-guide-cloud/section_ts_HTTP_bad_req_in_cinder_vol_log.xml9(para) +msgid "" +"These errors appear in the cinder-volume.log file." +msgstr "" + +#: ./doc/admin-guide-cloud/section_ts_HTTP_bad_req_in_cinder_vol_log.xml44(para) +msgid "" +"You need to update your copy of the hp_3par_fc.py " +"driver which contains the synchronization code." +msgstr "" + +#: ./doc/admin-guide-cloud/section_ts_non_existent_vlun.xml4(title) +msgid "Non-existent VLUN" +msgstr "" + +#: ./doc/admin-guide-cloud/section_ts_non_existent_vlun.xml7(para) +msgid "" +"This error occurs if the 3PAR host exists with the correct host name that " +"the OpenStack Block Storage drivers expect but the volume was created in a " +"different Domain." +msgstr "" + +#: ./doc/admin-guide-cloud/section_ts_non_existent_vlun.xml13(para) +msgid "" +"The hp3par_domain configuration items either need to be updated" +" to use the domain the 3PAR host currently resides in, or the 3PAR host " +"needs to be moved to the domain that the volume was created in." +msgstr "" + +#: ./doc/admin-guide-cloud/section_ts_failed_attach_vol_no_sysfsutils.xml4(title) +msgid "Failed to attach volume, systool is not installed" +msgstr "" + +#: ./doc/admin-guide-cloud/section_ts_failed_attach_vol_no_sysfsutils.xml7(para) +msgid "" +"This warning and error occurs if you do not have the required " +"sysfsutils package installed on the Compute node." +msgstr "" + +#: ./doc/admin-guide-cloud/section_ts_failed_attach_vol_no_sysfsutils.xml16(para) +msgid "" +"Run the following command on the Compute node to install the " +"sysfsutils packages." +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking_adv_features.xml6(title) +msgid "Advanced features through API extensions" +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking_adv_features.xml7(para) +msgid "" +"Several plug-ins implement API extensions that provide capabilities similar " +"to what was available in nova-network: These plug-ins are likely to be of " +"interest to the OpenStack community." +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking_adv_features.xml12(title) +msgid "Provider networks" +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking_adv_features.xml13(para) +msgid "" +"Provider networks enable cloud administrators to create Networking networks " +"that map directly to the physical networks in the data center. This is " +"commonly used to give tenants direct access to a public network that can be " +"used to reach the Internet. It might also be used to integrate with VLANs in" +" the network that already have a defined meaning (for example, enable a VM " +"from the \"marketing\" department to be placed on the same VLAN as bare-" +"metal marketing hosts in the same data center)." +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking_adv_features.xml22(para) +msgid "" +"The provider extension allows administrators to explicitly manage the " +"relationship between Networking virtual networks and underlying physical " +"mechanisms such as VLANs and tunnels. When this extension is supported, " +"Networking client users with administrative privileges see additional " +"provider attributes on all virtual networks, and are able to specify these " +"attributes in order to create provider networks." +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking_adv_features.xml30(para) +msgid "" +"The provider extension is supported by the Open vSwitch and Linux Bridge " +"plug-ins. Configuration of these plug-ins requires familiarity with this " +"extension." +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking_adv_features.xml34(title) +msgid "Terminology" +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking_adv_features.xml35(para) +msgid "" +"A number of terms are used in the provider extension and in the " +"configuration of plug-ins supporting the provider extension:" +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking_adv_features.xml39(caption) +msgid "Provider extension terminology" +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking_adv_features.xml44(th) +msgid "Term" +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking_adv_features.xml50(emphasis) +msgid "virtual network" +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking_adv_features.xml52(td) +msgid "" +"An Networking L2 network (identified by a UUID and optional name) whose " +"ports can be attached as vNICs to Compute instances and to various " +"Networking agents. The Open vSwitch and Linux Bridge plug-ins each support " +"several different mechanisms to realize virtual networks." +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking_adv_features.xml61(emphasis) +msgid "physical network" +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking_adv_features.xml63(td) +msgid "" +"A network connecting virtualization hosts (such as, Compute nodes) with each" +" other and with other network resources. Each physical network might support" +" multiple virtual networks. The provider extension and the plug-in " +"configurations identify physical networks using simple string names." +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking_adv_features.xml73(emphasis) +msgid "tenant network" +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking_adv_features.xml75(td) +msgid "" +"A virtual network that a tenant or an administrator creates. The physical " +"details of the network are not exposed to the tenant." +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking_adv_features.xml81(emphasis) +msgid "provider network" +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking_adv_features.xml83(td) +msgid "" +"A virtual network administratively created to map to a specific network in " +"the data center, typically to enable direct access to non-OpenStack " +"resources on that network. Tenants can be given access to provider networks." +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking_adv_features.xml91(emphasis) +msgid "VLAN network" +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking_adv_features.xml93(td) +msgid "" +"A virtual network implemented as packets on a specific physical network " +"containing IEEE 802.1Q headers with a specific VID field value. VLAN " +"networks sharing the same physical network are isolated from each other at " +"L2, and can even have overlapping IP address spaces. Each distinct physical " +"network supporting VLAN networks is treated as a separate VLAN trunk, with a" +" distinct space of VID values. Valid VID values are 1 through 4094." +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking_adv_features.xml107(emphasis) +msgid "flat network" +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking_adv_features.xml109(td) +msgid "" +"A virtual network implemented as packets on a specific physical network " +"containing no IEEE 802.1Q header. Each physical network can realize at most " +"one flat network." +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking_adv_features.xml116(emphasis) +msgid "local network" +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking_adv_features.xml118(td) +msgid "" +"A virtual network that allows communication within each host, but not across" +" a network. Local networks are intended mainly for single-node test " +"scenarios, but can have other uses." +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking_adv_features.xml125(emphasis) +msgid "GRE network" +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking_adv_features.xml130(emphasis) +msgid "tunnels" +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking_adv_features.xml127(td) +msgid "" +"A virtual network implemented as network packets encapsulated using GRE. GRE" +" networks are also referred to as . GRE tunnel packets are " +"routed by the IP routing table for the host, so GRE networks are not " +"associated by Networking with specific physical networks." +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking_adv_features.xml137(emphasis) +msgid "Virtual Extensible LAN (VXLAN) network" +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking_adv_features.xml139(td) +msgid "" +"VXLAN is a proposed encapsulation protocol for running an overlay network on" +" existing Layer 3 infrastructure. An overlay network is a virtual network " +"that is built on top of existing network Layer 2 and Layer 3 technologies to" +" support elastic compute architectures." +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking_adv_features.xml149(para) +msgid "" +"The ML2, Open vSwitch, and Linux Bridge plug-ins support VLAN networks, flat" +" networks, and local networks. Only the ML2 and Open vSwitch plug-ins " +"currently support GRE and VXLAN networks, provided that the required " +"features exist in the hosts Linux kernel, Open vSwitch, and iproute2 " +"packages." +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking_adv_features.xml157(title) +msgid "Provider attributes" +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking_adv_features.xml158(para) +msgid "" +"The provider extension extends the Networking network resource with these " +"attributes:" +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking_adv_features.xml161(caption) +msgid "Provider network attributes" +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking_adv_features.xml168(th) +#: ./doc/admin-guide-cloud/section_networking_adv_features.xml371(th) +#: ./doc/admin-guide-cloud/section_networking_adv_features.xml433(th) +#: ./doc/admin-guide-cloud/section_networking_adv_features.xml756(th) +#: ./doc/admin-guide-cloud/section_networking_adv_features.xml803(th) +#: ./doc/admin-guide-cloud/section_networking_adv_features.xml1071(th) +#: ./doc/admin-guide-cloud/section_networking_adv_features.xml1206(th) +#: ./doc/admin-guide-cloud/section_networking_adv_features.xml1284(th) +#: ./doc/admin-guide-cloud/section_networking_adv_features.xml1521(th) +#: ./doc/admin-guide-cloud/section_networking_adv_features.xml1899(th) +#: ./doc/admin-guide-cloud/section_networking_adv_features.xml2008(th) +#: ./doc/admin-guide-cloud/section_networking_adv_features.xml2051(th) +msgid "Attribute name" +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking_adv_features.xml169(th) +#: ./doc/admin-guide-cloud/section_networking_adv_features.xml372(th) +#: ./doc/admin-guide-cloud/section_networking_adv_features.xml434(th) +#: ./doc/admin-guide-cloud/section_networking_adv_features.xml757(th) +#: ./doc/admin-guide-cloud/section_networking_adv_features.xml804(th) +#: ./doc/admin-guide-cloud/section_networking_adv_features.xml1072(th) +#: ./doc/admin-guide-cloud/section_networking_adv_features.xml1207(th) +#: ./doc/admin-guide-cloud/section_networking_adv_features.xml1285(th) +#: ./doc/admin-guide-cloud/section_networking_adv_features.xml1522(th) +#: ./doc/admin-guide-cloud/section_networking_adv_features.xml2009(th) +#: ./doc/admin-guide-cloud/section_networking_adv_features.xml2052(th) +#: ./doc/admin-guide-cloud/section_networking-use.xml125(th) +#: ./doc/admin-guide-cloud/section_networking-use.xml198(th) +#: ./doc/admin-guide-cloud/section_networking-use.xml302(th) +msgid "Type" +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking_adv_features.xml170(th) +#: ./doc/admin-guide-cloud/section_networking_adv_features.xml373(th) +#: ./doc/admin-guide-cloud/section_networking_adv_features.xml435(th) +#: ./doc/admin-guide-cloud/section_networking_adv_features.xml758(th) +#: ./doc/admin-guide-cloud/section_networking_adv_features.xml805(th) +#: ./doc/admin-guide-cloud/section_networking_adv_features.xml1073(th) +#: ./doc/admin-guide-cloud/section_networking_adv_features.xml1208(th) +#: ./doc/admin-guide-cloud/section_networking_adv_features.xml1286(th) +#: ./doc/admin-guide-cloud/section_networking_adv_features.xml1523(th) +#: ./doc/admin-guide-cloud/section_networking_adv_features.xml2010(th) +#: ./doc/admin-guide-cloud/section_networking_adv_features.xml2053(th) +#: ./doc/admin-guide-cloud/section_networking-use.xml199(th) +#: ./doc/admin-guide-cloud/section_networking-use.xml303(th) +msgid "Default Value" +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking_adv_features.xml176(td) +msgid "provider:network_type" +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking_adv_features.xml177(td) +#: ./doc/admin-guide-cloud/section_networking_adv_features.xml197(td) +#: ./doc/admin-guide-cloud/section_networking_adv_features.xml386(td) +#: ./doc/admin-guide-cloud/section_networking_adv_features.xml401(td) +#: ./doc/admin-guide-cloud/section_networking_adv_features.xml771(td) +#: ./doc/admin-guide-cloud/section_networking_adv_features.xml780(td) +#: ./doc/admin-guide-cloud/section_networking_adv_features.xml825(td) +#: ./doc/admin-guide-cloud/section_networking_adv_features.xml832(td) +#: ./doc/admin-guide-cloud/section_networking_adv_features.xml851(td) +#: ./doc/admin-guide-cloud/section_networking_adv_features.xml1094(td) +#: ./doc/admin-guide-cloud/section_networking_adv_features.xml1101(td) +#: ./doc/admin-guide-cloud/section_networking_adv_features.xml1131(td) +#: ./doc/admin-guide-cloud/section_networking_adv_features.xml1181(td) +#: ./doc/admin-guide-cloud/section_networking_adv_features.xml1229(td) +#: ./doc/admin-guide-cloud/section_networking_adv_features.xml1236(td) +#: ./doc/admin-guide-cloud/section_networking_adv_features.xml1307(td) +#: ./doc/admin-guide-cloud/section_networking_adv_features.xml1314(td) +#: ./doc/admin-guide-cloud/section_networking_adv_features.xml1329(td) +#: ./doc/admin-guide-cloud/section_networking_adv_features.xml1545(td) +#: ./doc/admin-guide-cloud/section_networking_adv_features.xml1565(td) +#: ./doc/admin-guide-cloud/section_networking_adv_features.xml2023(td) +#: ./doc/admin-guide-cloud/section_networking_adv_features.xml2030(td) +msgid "String" +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking_adv_features.xml178(td) +#: ./doc/admin-guide-cloud/section_networking_adv_features.xml214(td) +#: ./doc/admin-guide-cloud/section_networking_adv_features.xml402(td) +#: ./doc/admin-guide-cloud/section_networking_adv_features.xml409(td) +#: ./doc/admin-guide-cloud/section_networking_adv_features.xml457(td) +#: ./doc/admin-guide-cloud/section_networking_adv_features.xml465(td) +#: ./doc/admin-guide-cloud/section_networking_adv_features.xml491(td) +#: ./doc/admin-guide-cloud/section_networking_adv_features.xml788(td) +#: ./doc/admin-guide-cloud/section_networking_adv_features.xml826(td) +#: ./doc/admin-guide-cloud/section_networking_adv_features.xml872(td) +#: ./doc/admin-guide-cloud/section_networking_adv_features.xml1087(td) +#: ./doc/admin-guide-cloud/section_networking_adv_features.xml1222(td) +#: ./doc/admin-guide-cloud/section_networking_adv_features.xml1300(td) +#: ./doc/admin-guide-cloud/section_networking_adv_features.xml1330(td) +#: ./doc/admin-guide-cloud/section_networking_adv_features.xml1559(td) +#: ./doc/admin-guide-cloud/section_networking_adv_features.xml1579(td) +#: ./doc/admin-guide-cloud/section_networking_adv_features.xml2038(td) +#: ./doc/admin-guide-cloud/section_networking_adv_features.xml2074(td) +#: ./doc/admin-guide-cloud/section_networking_adv_features.xml2093(td) +#: ./doc/admin-guide-cloud/section_networking-use.xml166(td) +#: ./doc/admin-guide-cloud/section_networking-use.xml180(td) +#: ./doc/admin-guide-cloud/section_networking-use.xml221(td) +#: ./doc/admin-guide-cloud/section_networking-use.xml277(td) +#: ./doc/admin-guide-cloud/section_networking-use.xml284(td) +#: ./doc/admin-guide-cloud/section_networking-use.xml362(td) +#: ./doc/admin-guide-cloud/section_networking-use.xml369(td) +#: ./doc/admin-guide-cloud/section_networking-use.xml376(td) +msgid "N/A" +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking_adv_features.xml181(literal) +#: ./doc/admin-guide-cloud/section_networking_adv_features.xml201(literal) +#: ./doc/admin-guide-cloud/section_networking_adv_features.xml221(literal) +msgid "flat" +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking_adv_features.xml182(literal) +#: ./doc/admin-guide-cloud/section_networking_adv_features.xml190(literal) +#: ./doc/admin-guide-cloud/section_networking_adv_features.xml202(literal) +msgid "vlan" +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking_adv_features.xml183(literal) +#: ./doc/admin-guide-cloud/section_networking_adv_features.xml192(literal) +#: ./doc/admin-guide-cloud/section_networking_adv_features.xml207(literal) +#: ./doc/admin-guide-cloud/section_networking_adv_features.xml222(literal) +msgid "local" +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking_adv_features.xml179(td) +msgid "" +"The physical mechanism by which the virtual network is implemented. Possible" +" values are , , , and " +", corresponding to flat networks, VLAN networks, local " +"networks, and GRE networks as defined above. All types of provider networks " +"can be created by administrators, while tenant networks can be implemented " +"as , , or network types " +"depending on plug-in configuration." +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking_adv_features.xml196(td) +msgid "provider:physical_network" +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking_adv_features.xml198(td) +msgid "" +"If a physical network named \"default\" has been configured, and if " +"provider:network_type is or , then " +"\"default\" is used." +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking_adv_features.xml204(td) +msgid "" +"The name of the physical network over which the virtual network is " +"implemented for flat and VLAN networks. Not applicable to the " +" or network types." +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking_adv_features.xml212(td) +msgid "provider:segmentation_id" +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking_adv_features.xml213(td) +#: ./doc/admin-guide-cloud/section_networking_adv_features.xml839(td) +#: ./doc/admin-guide-cloud/section_networking_adv_features.xml845(td) +#: ./doc/admin-guide-cloud/section_networking_adv_features.xml1171(td) +#: ./doc/admin-guide-cloud/section_networking_adv_features.xml1551(td) +#: ./doc/admin-guide-cloud/section_networking_adv_features.xml1558(td) +#: ./doc/admin-guide-cloud/section_networking_adv_features.xml1572(td) +msgid "Integer" +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking_adv_features.xml215(td) +msgid "" +"For VLAN networks, the VLAN VID on the physical network that realizes the " +"virtual network. Valid VLAN VIDs are 1 through 4094. For GRE networks, the " +"tunnel ID. Valid tunnel IDs are any 32 bit unsigned integer. Not applicable " +"to the or network types." +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking_adv_features.xml227(para) +msgid "" +"To view or set provider extended attributes, a client must be authorized for" +" the extension:provider_network:view and " +"extension:provider_network:set actions in the Networking policy" +" configuration. The default Networking configuration authorizes both actions" +" for users with the admin role. An authorized client or an administrative " +"user can view and set the provider extended attributes through Networking " +"API calls. See for details on " +"policy configuration." +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking_adv_features.xml240(title) +msgid "Provider extension API operations" +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking_adv_features.xml241(para) +msgid "" +"To use the provider extension with the default policy settings, you must " +"have the administrative role." +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking_adv_features.xml244(para) +msgid "" +"This table shows example neutron commands that enable you to complete basic " +"provider extension API operations:" +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking_adv_features.xml248(caption) +msgid "Basic provider extension API operations" +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking_adv_features.xml254(th) +#: ./doc/admin-guide-cloud/section_networking_adv_features.xml514(th) +#: ./doc/admin-guide-cloud/section_networking_adv_features.xml891(th) +#: ./doc/admin-guide-cloud/section_networking_adv_features.xml969(th) +#: ./doc/admin-guide-cloud/section_networking_adv_features.xml1597(th) +#: ./doc/admin-guide-cloud/section_networking_adv_features.xml2114(th) +#: ./doc/admin-guide-cloud/section_networking-use.xml403(th) +#: ./doc/admin-guide-cloud/section_networking-use.xml484(th) +#: ./doc/admin-guide-cloud/section_networking-use.xml617(th) +msgid "Operation" +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking_adv_features.xml255(th) +#: ./doc/admin-guide-cloud/section_networking_adv_features.xml515(th) +#: ./doc/admin-guide-cloud/section_networking_adv_features.xml892(th) +#: ./doc/admin-guide-cloud/section_networking_adv_features.xml970(th) +#: ./doc/admin-guide-cloud/section_networking_adv_features.xml1598(th) +#: ./doc/admin-guide-cloud/section_networking_adv_features.xml2115(th) +#: ./doc/admin-guide-cloud/section_networking-use.xml404(th) +#: ./doc/admin-guide-cloud/section_networking-use.xml485(th) +#: ./doc/admin-guide-cloud/section_networking-use.xml544(th) +#: ./doc/admin-guide-cloud/section_networking-use.xml618(th) +msgid "Command" +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking_adv_features.xml261(para) +msgid "Shows all attributes of a network, including provider attributes." +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking_adv_features.xml270(para) +msgid "Creates a local provider network." +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking_adv_features.xml278(para) +msgid "" +"Creates a flat provider network. When you create flat networks, <phys-" +"net-name> must be known to the plug-in. See the OpenStack " +"Configuration Reference for details." +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking_adv_features.xml293(para) +msgid "" +"Creates a VLAN provider network. When you create VLAN networks, <phys-" +"net-name> must be known to the plug-in. See the OpenStack " +"Configuration Reference for details on configuring " +"network_vlan_ranges to identify all physical networks. When you create VLAN " +"networks, <VID> can fall either within or outside any configured " +"ranges of VLAN IDs from which tenant networks are allocated." +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking_adv_features.xml314(para) +msgid "" +"Creates a GRE provider network. When you create GRE networks, <tunnel-" +"id> can be either inside or outside any tunnel ID ranges from which " +"tenant networks are allocated." +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking_adv_features.xml320(para) +msgid "" +"After you create provider networks, you can allocate subnets, which you can " +"use in the same way as other virtual networks, subject to authorization " +"policy based on the specified <tenant_id>." +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking_adv_features.xml336(title) +msgid "L3 routing and NAT" +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking_adv_features.xml337(para) +msgid "" +"The Networking API provides abstract L2 network segments that are decoupled " +"from the technology used to implement the L2 network. Networking includes an" +" API extension that provides abstract L3 routers that API users can " +"dynamically provision and configure. These Networking routers can connect " +"multiple L2 Networking networks, and can also provide a gateway that " +"connects one or more private L2 networks to a shared external network. For " +"example, a public network for access to the Internet. See the " +"OpenStack Configuration Reference for details on " +"common models of deploying Networking L3 routers." +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking_adv_features.xml350(para) +msgid "" +"The L3 router provides basic NAT capabilities on gateway ports that uplink " +"the router to external networks. This router SNATs all traffic by default, " +"and supports floating IPs, which creates a static one-to-one mapping from a " +"public IP on the external network to a private IP on one of the other " +"subnets attached to the router. This allows a tenant to selectively expose " +"VMs on private networks to other hosts on the external network (and often to" +" all hosts on the Internet). You can allocate and map floating IPs from one " +"port to another, as needed." +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking_adv_features.xml362(title) +msgid "L3 API abstractions" +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking_adv_features.xml364(caption) +msgid "Router" +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking_adv_features.xml379(td) +#: ./doc/admin-guide-cloud/section_networking_adv_features.xml441(td) +#: ./doc/admin-guide-cloud/section_networking_adv_features.xml764(td) +#: ./doc/admin-guide-cloud/section_networking_adv_features.xml811(td) +#: ./doc/admin-guide-cloud/section_networking_adv_features.xml1079(td) +#: ./doc/admin-guide-cloud/section_networking_adv_features.xml1214(td) +#: ./doc/admin-guide-cloud/section_networking_adv_features.xml1292(td) +#: ./doc/admin-guide-cloud/section_networking_adv_features.xml1529(td) +#: ./doc/admin-guide-cloud/section_networking_adv_features.xml2016(td) +#: ./doc/admin-guide-cloud/section_networking_adv_features.xml2059(td) +#: ./doc/admin-guide-cloud/section_networking-use.xml141(option) +#: ./doc/admin-guide-cloud/section_networking-use.xml256(option) +#: ./doc/admin-guide-cloud/section_networking-use.xml341(option) +#: ./doc/admin-guide-cloud/section_networking-use.xml424(option) +msgid "id" +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking_adv_features.xml380(td) +#: ./doc/admin-guide-cloud/section_networking_adv_features.xml408(td) +#: ./doc/admin-guide-cloud/section_networking_adv_features.xml442(td) +#: ./doc/admin-guide-cloud/section_networking_adv_features.xml456(td) +#: ./doc/admin-guide-cloud/section_networking_adv_features.xml464(td) +#: ./doc/admin-guide-cloud/section_networking_adv_features.xml473(td) +#: ./doc/admin-guide-cloud/section_networking_adv_features.xml490(td) +#: ./doc/admin-guide-cloud/section_networking_adv_features.xml765(td) +#: ./doc/admin-guide-cloud/section_networking_adv_features.xml787(td) +#: ./doc/admin-guide-cloud/section_networking_adv_features.xml812(td) +#: ./doc/admin-guide-cloud/section_networking_adv_features.xml871(td) +#: ./doc/admin-guide-cloud/section_networking_adv_features.xml1080(td) +#: ./doc/admin-guide-cloud/section_networking_adv_features.xml1086(td) +#: ./doc/admin-guide-cloud/section_networking_adv_features.xml1215(td) +#: ./doc/admin-guide-cloud/section_networking_adv_features.xml1221(td) +#: ./doc/admin-guide-cloud/section_networking_adv_features.xml1293(td) +#: ./doc/admin-guide-cloud/section_networking_adv_features.xml1299(td) +#: ./doc/admin-guide-cloud/section_networking_adv_features.xml1530(td) +#: ./doc/admin-guide-cloud/section_networking_adv_features.xml1578(td) +#: ./doc/admin-guide-cloud/section_networking_adv_features.xml2017(td) +#: ./doc/admin-guide-cloud/section_networking_adv_features.xml2037(td) +#: ./doc/admin-guide-cloud/section_networking_adv_features.xml2060(td) +#: ./doc/admin-guide-cloud/section_networking_adv_features.xml2073(td) +#: ./doc/admin-guide-cloud/section_networking-use.xml142(td) +#: ./doc/admin-guide-cloud/section_networking-use.xml179(td) +msgid "uuid-str" +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking_adv_features.xml381(td) +#: ./doc/admin-guide-cloud/section_networking_adv_features.xml443(td) +#: ./doc/admin-guide-cloud/section_networking_adv_features.xml766(td) +#: ./doc/admin-guide-cloud/section_networking_adv_features.xml813(td) +#: ./doc/admin-guide-cloud/section_networking_adv_features.xml1081(td) +#: ./doc/admin-guide-cloud/section_networking_adv_features.xml1216(td) +#: ./doc/admin-guide-cloud/section_networking_adv_features.xml1294(td) +#: ./doc/admin-guide-cloud/section_networking_adv_features.xml1531(td) +#: ./doc/admin-guide-cloud/section_networking_adv_features.xml2018(td) +#: ./doc/admin-guide-cloud/section_networking_adv_features.xml2061(td) +msgid "generated" +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking_adv_features.xml382(td) +msgid "UUID for the router." +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking_adv_features.xml385(td) +#: ./doc/admin-guide-cloud/section_networking_adv_features.xml770(td) +#: ./doc/admin-guide-cloud/section_networking_adv_features.xml1093(td) +#: ./doc/admin-guide-cloud/section_networking_adv_features.xml1228(td) +#: ./doc/admin-guide-cloud/section_networking_adv_features.xml1306(td) +#: ./doc/admin-guide-cloud/section_networking_adv_features.xml1544(td) +#: ./doc/admin-guide-cloud/section_networking_adv_features.xml2022(td) +#: ./doc/admin-guide-cloud/section_networking-use.xml147(option) +#: ./doc/admin-guide-cloud/section_networking-use.xml268(option) +#: ./doc/admin-guide-cloud/section_networking-use.xml353(option) +msgid "name" +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking_adv_features.xml387(td) +#: ./doc/admin-guide-cloud/section_networking_adv_features.xml772(td) +#: ./doc/admin-guide-cloud/section_networking_adv_features.xml781(td) +#: ./doc/admin-guide-cloud/section_networking_adv_features.xml833(td) +#: ./doc/admin-guide-cloud/section_networking_adv_features.xml840(td) +#: ./doc/admin-guide-cloud/section_networking_adv_features.xml846(td) +#: ./doc/admin-guide-cloud/section_networking_adv_features.xml852(td) +#: ./doc/admin-guide-cloud/section_networking_adv_features.xml859(td) +#: ./doc/admin-guide-cloud/section_networking_adv_features.xml1095(td) +#: ./doc/admin-guide-cloud/section_networking_adv_features.xml1102(td) +#: ./doc/admin-guide-cloud/section_networking_adv_features.xml1132(td) +#: ./doc/admin-guide-cloud/section_networking_adv_features.xml1144(td) +#: ./doc/admin-guide-cloud/section_networking_adv_features.xml1150(td) +#: ./doc/admin-guide-cloud/section_networking_adv_features.xml1158(td) +#: ./doc/admin-guide-cloud/section_networking_adv_features.xml1166(td) +#: ./doc/admin-guide-cloud/section_networking_adv_features.xml1172(td) +#: ./doc/admin-guide-cloud/section_networking_adv_features.xml1230(td) +#: ./doc/admin-guide-cloud/section_networking_adv_features.xml1237(td) +#: ./doc/admin-guide-cloud/section_networking_adv_features.xml1254(td) +#: ./doc/admin-guide-cloud/section_networking_adv_features.xml1308(td) +#: ./doc/admin-guide-cloud/section_networking_adv_features.xml1315(td) +#: ./doc/admin-guide-cloud/section_networking_adv_features.xml1359(td) +#: ./doc/admin-guide-cloud/section_networking_adv_features.xml1546(td) +#: ./doc/admin-guide-cloud/section_networking_adv_features.xml2024(td) +#: ./doc/admin-guide-cloud/section_networking_adv_features.xml2031(td) +#: ./doc/admin-guide-cloud/section_networking-use.xml149(td) +#: ./doc/admin-guide-cloud/section_networking-use.xml270(td) +#: ./doc/admin-guide-cloud/section_networking-use.xml319(td) +#: ./doc/admin-guide-cloud/section_networking-use.xml327(td) +#: ./doc/admin-guide-cloud/section_networking-use.xml355(td) +msgid "None" +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking_adv_features.xml388(td) +msgid "Human-readable name for the router. Might not be unique." +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking_adv_features.xml392(td) +#: ./doc/admin-guide-cloud/section_networking_adv_features.xml1320(td) +#: ./doc/admin-guide-cloud/section_networking-use.xml132(option) +#: ./doc/admin-guide-cloud/section_networking-use.xml309(option) +msgid "admin_state_up" +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking_adv_features.xml393(td) +msgid "Bool" +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking_adv_features.xml395(td) +msgid "" +"The administrative state of router. If false (down), the router does not " +"forward packets." +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking_adv_features.xml400(td) +#: ./doc/admin-guide-cloud/section_networking_adv_features.xml1328(td) +#: ./doc/admin-guide-cloud/section_networking-use.xml164(option) +#: ./doc/admin-guide-cloud/section_networking-use.xml367(option) +msgid "status" +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking_adv_features.xml403(para) +msgid "Indicates whether router is currently operational." +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking_adv_features.xml407(td) +#: ./doc/admin-guide-cloud/section_networking_adv_features.xml489(td) +#: ./doc/admin-guide-cloud/section_networking_adv_features.xml786(td) +#: ./doc/admin-guide-cloud/section_networking_adv_features.xml870(td) +#: ./doc/admin-guide-cloud/section_networking_adv_features.xml1085(td) +#: ./doc/admin-guide-cloud/section_networking_adv_features.xml1220(td) +#: ./doc/admin-guide-cloud/section_networking_adv_features.xml1298(td) +#: ./doc/admin-guide-cloud/section_networking_adv_features.xml1577(td) +#: ./doc/admin-guide-cloud/section_networking_adv_features.xml2036(td) +#: ./doc/admin-guide-cloud/section_networking-use.xml178(option) +#: ./doc/admin-guide-cloud/section_networking-use.xml282(option) +#: ./doc/admin-guide-cloud/section_networking-use.xml374(option) +msgid "tenant_id" +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking_adv_features.xml410(td) +msgid "" +"Owner of the router. Only admin users can specify a tenant_id other than its" +" own." +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking_adv_features.xml415(td) +msgid "external_gateway_info" +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking_adv_features.xml416(td) +msgid "dict contain 'network_id' key-value pair" +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking_adv_features.xml418(td) +#: ./doc/admin-guide-cloud/section_networking_adv_features.xml474(td) +#: ./doc/admin-guide-cloud/section_networking_adv_features.xml482(td) +msgid "Null" +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking_adv_features.xml419(td) +msgid "" +"External network that this router connects to for gateway services (for " +"example, NAT)" +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking_adv_features.xml426(caption) +msgid "Floating IP" +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking_adv_features.xml444(td) +msgid "UUID for the floating IP." +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking_adv_features.xml447(td) +msgid "floating_ip_address" +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking_adv_features.xml448(td) +#: ./doc/admin-guide-cloud/section_networking_adv_features.xml481(td) +msgid "string (IP address)" +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking_adv_features.xml449(td) +#: ./doc/admin-guide-cloud/section_networking_adv_features.xml819(td) +#: ./doc/admin-guide-cloud/section_networking_adv_features.xml1110(td) +msgid "allocated by Networking" +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking_adv_features.xml450(td) +msgid "" +"The external network IP address available to be mapped to an internal IP " +"address." +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking_adv_features.xml455(td) +msgid "floating_network_id" +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking_adv_features.xml458(para) +msgid "" +"The network indicating the set of subnets from which the floating IP should " +"be allocated" +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking_adv_features.xml463(td) +msgid "router_id" +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking_adv_features.xml466(td) +msgid "" +"Read-only value indicating the router that connects the external network to " +"the associated internal port, if a port is associated." +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking_adv_features.xml472(td) +msgid "port_id" +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking_adv_features.xml475(td) +msgid "" +"Indicates the internal Networking port associated with the external floating" +" IP." +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking_adv_features.xml480(td) +msgid "fixed_ip_address" +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking_adv_features.xml483(td) +msgid "" +"Indicates the IP address on the internal port that is mapped to by the " +"floating IP (since an Networking port might have more than one IP address)." +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking_adv_features.xml492(td) +msgid "" +"Owner of the Floating IP. Only admin users can specify a tenant_id other " +"than its own." +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking_adv_features.xml501(title) +#: ./doc/admin-guide-cloud/section_networking_adv_features.xml509(caption) +#: ./doc/admin-guide-cloud/section_networking_adv_features.xml2109(caption) +msgid "Basic L3 operations" +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking_adv_features.xml502(para) +msgid "" +"External networks are visible to all users. However, the default policy " +"settings enable only administrative users to create, update, and delete " +"external networks." +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking_adv_features.xml506(para) +msgid "" +"This table shows example neutron commands that enable you to complete basic " +"L3 operations:" +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking_adv_features.xml521(para) +msgid "Creates external networks." +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking_adv_features.xml530(para) +msgid "Lists external networks." +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking_adv_features.xml536(para) +msgid "" +"Creates an internal-only router that connects to multiple L2 networks " +"privately." +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking_adv_features.xml551(para) +msgid "" +"Connects a router to an external network, which enables that router to act " +"as a NAT gateway for external connectivity." +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking_adv_features.xml557(para) +msgid "" +"The router obtains an interface with the gateway_ip address of the subnet, " +"and this interface is attached to a port on the L2 Networking network " +"associated with the subnet. The router also gets a gateway interface to the " +"specified external network. This provides SNAT connectivity to the external " +"network as well as support for floating IPs allocated on that external " +"networks. Commonly an external network maps to a network in the provider" +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking_adv_features.xml574(para) +msgid "Lists routers." +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking_adv_features.xml581(para) +msgid "Shows information for a specified router." +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking_adv_features.xml589(para) +msgid "Shows all internal interfaces for a router." +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking_adv_features.xml595(para) +msgid "" +"Identifies the port-id that represents the VM NIC to " +"which the floating IP should map." +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking_adv_features.xml601(para) +msgid "" +"This port must be on an Networking subnet that is attached to a router " +"uplinked to the external network used to create the floating IP.  " +"Conceptually, this is because the router must be able to perform the " +"Destination NAT (DNAT) rewriting of packets from the Floating IP address " +"(chosen from a subnet on the external network) to the internal Fixed IP " +"(chosen from a private subnet that is behind the router)." +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking_adv_features.xml617(para) +msgid "Creates a floating IP address and associates it with a port." +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking_adv_features.xml626(para) +msgid "" +"Creates a floating IP address and associates it with a port, in a single " +"step." +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking_adv_features.xml635(para) +msgid "Lists floating IPs." +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking_adv_features.xml642(para) +msgid "Finds floating IP for a specified VM port." +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking_adv_features.xml650(para) +msgid "Disassociates a floating IP address." +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking_adv_features.xml658(para) +msgid "Deletes the floating IP address." +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking_adv_features.xml666(para) +msgid "Clears the gateway." +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking_adv_features.xml673(para) +msgid "Removes the interfaces from the router." +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking_adv_features.xml681(para) +msgid "Deletes the router." +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking_adv_features.xml692(title) +msgid "Security groups" +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking_adv_features.xml693(para) +msgid "" +"Security groups and security group rules allows administrators and tenants " +"the ability to specify the type of traffic and direction (ingress/egress) " +"that is allowed to pass through a port. A security group is a container for " +"security group rules." +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking_adv_features.xml698(para) +msgid "" +"When a port is created in Networking it is associated with a security group." +" If a security group is not specified the port is associated with a " +"'default' security group. By default, this group drops all ingress traffic " +"and allows all egress. Rules can be added to this group in order to change " +"the behaviour." +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking_adv_features.xml704(para) +msgid "" +"To use the Compute security group APIs or use Compute to orchestrate the " +"creation of ports for instances on specific security groups, you must " +"complete additional configuration. You must configure the " +"/etc/nova/nova.conf file and set the " +"security_group_api=neutron option on every node that runs " +"nova-compute and nova-api. After you make this change, restart" +" nova-api and nova-compute to pick up this change. Then, " +"you can use both the Compute and OpenStack Network security group APIs at " +"the same time." +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking_adv_features.xml721(para) +msgid "" +"To use the Compute security group API with Networking, the Networking plug-" +"in must implement the security group API. The following plug-ins currently " +"implement this: ML2, Nicira NVP, Open vSwitch, Linux Bridge, NEC, and Ryu." +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking_adv_features.xml729(para) +msgid "" +"You must configure the correct firewall driver in the " +"securitygroup section of the plug-in/agent configuration " +"file. Some plug-ins and agents, such as Linux Bridge Agent and Open vSwitch " +"Agent, use the no-operation driver as the default, which results in non-" +"working security groups." +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking_adv_features.xml738(para) +msgid "" +"When using the security group API through Compute, security groups are " +"applied to all ports on an instance. The reason for this is that Compute " +"security group APIs are instances based and not port based as Networking." +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking_adv_features.xml747(title) +msgid "Security group API abstractions" +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking_adv_features.xml749(caption) +msgid "Security group attributes" +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking_adv_features.xml767(td) +msgid "UUID for the security group." +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking_adv_features.xml773(td) +msgid "" +"Human-readable name for the security group. Might not be unique. Cannot be " +"named default as that is automatically created for a tenant." +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking_adv_features.xml779(td) +#: ./doc/admin-guide-cloud/section_networking_adv_features.xml1100(td) +#: ./doc/admin-guide-cloud/section_networking_adv_features.xml1235(td) +#: ./doc/admin-guide-cloud/section_networking_adv_features.xml1313(td) +#: ./doc/admin-guide-cloud/section_networking_adv_features.xml2029(td) +msgid "description" +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking_adv_features.xml782(td) +msgid "Human-readable description of a security group." +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking_adv_features.xml789(td) +msgid "" +"Owner of the security group. Only admin users can specify a tenant_id other " +"than their own." +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking_adv_features.xml796(caption) +msgid "Security group rules" +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking_adv_features.xml814(td) +msgid "UUID for the security group rule." +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking_adv_features.xml817(td) +msgid "security_group_id" +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking_adv_features.xml818(td) +#: ./doc/admin-guide-cloud/section_networking_adv_features.xml864(td) +msgid "uuid-str or Integer" +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking_adv_features.xml820(td) +msgid "The security group to associate rule with." +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking_adv_features.xml824(td) +#: ./doc/admin-guide-cloud/section_networking_adv_features.xml2065(td) +#: ./doc/admin-guide-cloud/section_networking_adv_features.xml2159(replaceable) +msgid "direction" +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking_adv_features.xml827(td) +msgid "The direction the traffic is allow (ingress/egress) from a VM." +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking_adv_features.xml831(td) +#: ./doc/admin-guide-cloud/section_networking_adv_features.xml1130(td) +msgid "protocol" +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking_adv_features.xml834(td) +msgid "IP Protocol (icmp, tcp, udp, and so on)." +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking_adv_features.xml838(td) +msgid "port_range_min" +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking_adv_features.xml841(td) +msgid "Port at start of range" +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking_adv_features.xml844(td) +msgid "port_range_max" +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking_adv_features.xml847(td) +msgid "Port at end of range" +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking_adv_features.xml850(td) +msgid "ethertype" +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking_adv_features.xml853(td) +msgid "ethertype in L2 packet (IPv4, IPv6, and so on)" +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking_adv_features.xml857(td) +#: ./doc/admin-guide-cloud/section_networking_adv_features.xml2091(td) +msgid "remote_ip_prefix" +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking_adv_features.xml858(td) +msgid "string (IP cidr)" +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking_adv_features.xml860(td) +msgid "CIDR for address range" +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking_adv_features.xml863(td) +msgid "remote_group_id" +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking_adv_features.xml865(td) +msgid "allocated by Networking or Compute" +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking_adv_features.xml866(td) +msgid "Source security group to apply to rule." +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking_adv_features.xml873(td) +msgid "" +"Owner of the security group rule. Only admin users can specify a tenant_id " +"other than its own." +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking_adv_features.xml881(title) +#: ./doc/admin-guide-cloud/section_networking_adv_features.xml886(caption) +msgid "Basic security group operations" +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking_adv_features.xml882(para) +msgid "" +"This table shows example neutron commands that enable you to complete basic " +"security group operations:" +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking_adv_features.xml898(para) +msgid "Creates a security group for our web servers." +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking_adv_features.xml904(para) +msgid "Lists security groups." +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking_adv_features.xml910(para) +msgid "Creates a security group rule to allow port 80 ingress." +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking_adv_features.xml917(para) +msgid "Lists security group rules." +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking_adv_features.xml923(para) +msgid "Deletes a security group rule." +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking_adv_features.xml930(para) +msgid "Deletes a security group." +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking_adv_features.xml936(para) +msgid "Creates a port and associates two security groups." +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking_adv_features.xml943(para) +msgid "Removes security groups from a port." +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking_adv_features.xml954(title) +msgid "Basic Load-Balancer-as-a-Service operations" +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking_adv_features.xml956(para) +msgid "" +"The Load-Balancer-as-a-Service (LBaaS) API provisions and configures load " +"balancers. The Havana release offers a reference implementation that is " +"based on the HAProxy software load balancer." +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking_adv_features.xml961(para) +msgid "" +"This table shows example neutron commands that enable you to complete basic " +"LBaaS operations:" +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking_adv_features.xml964(caption) +msgid "Basic LBaaS operations" +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking_adv_features.xml976(para) +msgid "Creates a load balancer pool by using specific provider." +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking_adv_features.xml978(para) +msgid "" +"--provider is an optional argument. If not used, the " +"pool is created with default provider for LBaaS service. You should " +"configure the default provider in the [service_providers]" +" section of neutron.conf file. If no default provider " +"is specified for LBaaS, the --provider option is " +"required for pool creation." +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking_adv_features.xml992(parameter) +msgid "--provider <provider_name>" +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking_adv_features.xml996(para) +msgid "Associates two web servers with pool." +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking_adv_features.xml1004(para) +msgid "" +"Creates a health monitor which checks to make sure our instances are still " +"running on the specified protocol-port." +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking_adv_features.xml1012(para) +msgid "Associates a health monitor with pool." +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking_adv_features.xml1019(para) +msgid "" +"Creates a virtual IP (VIP) address that, when accessed through the load " +"balancer, directs the requests to one of the pool members." +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking_adv_features.xml1032(title) +msgid "Firewall-as-a-Service" +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking_adv_features.xml1033(para) +msgid "" +"The Firewall-as-a-Service (FWaaS) API is an experimental API that enables " +"early adopters and vendors to test their networking implementations." +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking_adv_features.xml1036(para) +msgid "" +"The FWaaS is backed by a reference " +"implementation that works with the Networking OVS plug-in and " +"provides perimeter firewall functionality. It leverages the footprint of the" +" Networking OVS L3 agent and an IPTables driver to apply the firewall rules " +"contained in a particular firewall policy. This reference implementation " +"supports one firewall policy and consequently one logical firewall instance " +"for each tenant. This is not a constraint of the resource model, but of the " +"current reference implementation. The firewall is present on a Networking " +"virtual router. If a tenant has multiple routers, the firewall is present on" +" all the routers. If a tenant does not have any router, the firewall is in " +"PENDING_CREATE state until a router is created and the first " +"interface is added to the router. At that point the firewall policy is " +"immediately applied to the router and the firewall changes to " +"ACTIVE state." +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking_adv_features.xml1056(para) +msgid "" +"Because this is the first iteration of this implementation, it should " +"probably not be run in production environments without adequate testing." +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking_adv_features.xml1062(title) +msgid "Firewall-as-a-Service API abstractions" +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking_adv_features.xml1064(caption) +msgid "Firewall rules" +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking_adv_features.xml1082(td) +msgid "UUID for the firewall rule." +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking_adv_features.xml1088(td) +msgid "" +"Owner of the firewall rule. Only admin users can specify a tenant_id other " +"than its own." +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking_adv_features.xml1096(td) +msgid "Human readable name for the firewall rule (255 characters limit)." +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking_adv_features.xml1103(td) +msgid "" +"Human readable description for the firewall rule (1024 characters limit)." +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking_adv_features.xml1108(td) +#: ./doc/admin-guide-cloud/section_networking_adv_features.xml1357(td) +msgid "firewall_policy_id" +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking_adv_features.xml1109(td) +#: ./doc/admin-guide-cloud/section_networking_adv_features.xml1358(td) +msgid "uuid-str or None" +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking_adv_features.xml1111(td) +msgid "" +"This is a read-only attribute that gets populated with the uuid of the " +"firewall policy when this firewall rule is associated with a firewall " +"policy. A firewall rule can be associated with only one firewall policy at a" +" time. However, the association can be changed to a different firewall " +"policy." +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking_adv_features.xml1121(td) +#: ./doc/admin-guide-cloud/section_networking_adv_features.xml1243(td) +#: ./doc/admin-guide-cloud/section_networking-use.xml154(option) +msgid "shared" +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking_adv_features.xml1122(td) +#: ./doc/admin-guide-cloud/section_networking_adv_features.xml1188(td) +#: ./doc/admin-guide-cloud/section_networking_adv_features.xml1244(td) +#: ./doc/admin-guide-cloud/section_networking_adv_features.xml1262(td) +#: ./doc/admin-guide-cloud/section_networking_adv_features.xml1321(td) +#: ./doc/admin-guide-cloud/section_networking_adv_features.xml1536(td) +#: ./doc/admin-guide-cloud/section_networking_adv_features.xml2082(td) +msgid "Boolean" +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking_adv_features.xml1123(td) +#: ./doc/admin-guide-cloud/section_networking_adv_features.xml1245(td) +#: ./doc/admin-guide-cloud/section_networking_adv_features.xml1263(td) +#: ./doc/admin-guide-cloud/section_networking_adv_features.xml1840(td) +#: ./doc/admin-guide-cloud/section_networking_adv_features.xml2083(td) +#: ./doc/admin-guide-cloud/section_networking-use.xml156(td) +msgid "False" +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking_adv_features.xml1124(td) +msgid "" +"When set to True makes this firewall rule visible to tenants other than its " +"owner, and it can be used in firewall policies not owned by its tenant." +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking_adv_features.xml1133(td) +msgid "IP Protocol (icmp, tcp, udp, None)." +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking_adv_features.xml1136(td) +#: ./doc/admin-guide-cloud/section_networking-use.xml262(option) +msgid "ip_version" +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking_adv_features.xml1137(td) +msgid "Integer or String" +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking_adv_features.xml1138(td) +#: ./doc/admin-guide-cloud/section_networking-use.xml264(td) +msgid "4" +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking_adv_features.xml1139(td) +msgid "IP Version (4, 6)." +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking_adv_features.xml1142(td) +msgid "source_ip_address" +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking_adv_features.xml1143(td) +#: ./doc/admin-guide-cloud/section_networking_adv_features.xml1149(td) +msgid "String (IP address or CIDR)" +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking_adv_features.xml1145(td) +msgid "Source IP address or CIDR." +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking_adv_features.xml1148(td) +msgid "destination_ip_address" +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking_adv_features.xml1151(td) +msgid "Destination IP address or CIDR." +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking_adv_features.xml1154(td) +msgid "source_port" +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking_adv_features.xml1155(td) +#: ./doc/admin-guide-cloud/section_networking_adv_features.xml1163(td) +msgid "" +"Integer or String (either as a single port number or in the format of a ':' " +"separated range)" +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking_adv_features.xml1159(td) +msgid "Source port number or a range." +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking_adv_features.xml1162(td) +msgid "destination_port" +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking_adv_features.xml1167(td) +msgid "Destination port number or a range." +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking_adv_features.xml1170(td) +msgid "position" +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking_adv_features.xml1173(td) +msgid "" +"This is a read-only attribute that gets assigned to this rule when the rule " +"is associated with a firewall policy. It indicates the position of this rule" +" in that firewall policy." +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking_adv_features.xml1180(td) +#: ./doc/admin-guide-cloud/section_networking_adv_features.xml1925(td) +msgid "action" +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking_adv_features.xml1182(td) +msgid "deny" +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking_adv_features.xml1183(td) +msgid "Action to be performed on the traffic matching the rule (allow, deny)." +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking_adv_features.xml1187(td) +msgid "enabled" +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking_adv_features.xml1190(td) +msgid "" +"When set to False, disables this rule in the firewall policy. Facilitates " +"selectively turning off rules without having to disassociate the rule from " +"the firewall policy." +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking_adv_features.xml1199(caption) +msgid "Firewall policies" +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking_adv_features.xml1217(td) +msgid "UUID for the firewall policy." +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking_adv_features.xml1223(td) +msgid "" +"Owner of the firewall policy. Only admin users can specify a tenant_id other" +" their own." +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking_adv_features.xml1231(td) +msgid "Human readable name for the firewall policy (255 characters limit)." +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking_adv_features.xml1238(td) +msgid "" +"Human readable description for the firewall policy (1024 characters limit)." +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking_adv_features.xml1246(td) +msgid "" +"When set to True makes this firewall policy visible to tenants other than " +"its owner, and can be used to associate with firewalls not owned by its " +"tenant." +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking_adv_features.xml1252(td) +msgid "firewall_rules" +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking_adv_features.xml1253(td) +msgid "List of uuid-str or None" +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking_adv_features.xml1255(td) +msgid "" +"This is an ordered list of firewall rule uuids. The firewall applies the " +"rules in the order in which they appear in this list." +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking_adv_features.xml1261(td) +msgid "audited" +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking_adv_features.xml1264(td) +msgid "" +"When set to True by the policy owner indicates that the firewall policy has " +"been audited. This attribute is meant to aid in the firewall policy audit " +"workflows. Each time the firewall policy or the associated firewall rules " +"are changed, this attribute is set to False and must be explicitly set to " +"True through an update operation." +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking_adv_features.xml1277(caption) +msgid "Firewalls" +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking_adv_features.xml1295(td) +msgid "UUID for the firewall." +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking_adv_features.xml1301(td) +msgid "" +"Owner of the firewall. Only admin users can specify a tenant_id other than " +"its own." +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking_adv_features.xml1309(td) +msgid "Human readable name for the firewall (255 characters limit)." +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking_adv_features.xml1316(td) +msgid "Human readable description for the firewall (1024 characters limit)." +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking_adv_features.xml1323(td) +msgid "" +"The administrative state of the firewall. If False (down), the firewall does" +" not forward any packets." +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking_adv_features.xml1331(para) +msgid "" +"Indicates whether the firewall is currently operational. Possible values " +"include:" +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking_adv_features.xml1336(para) +msgid "ACTIVE" +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking_adv_features.xml1339(para) +msgid "DOWN" +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking_adv_features.xml1342(para) +msgid "PENDING_CREATE" +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking_adv_features.xml1345(para) +msgid "PENDING_UPDATE" +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking_adv_features.xml1348(para) +msgid "PENDING_DELETE" +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking_adv_features.xml1351(para) +msgid "ERROR" +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking_adv_features.xml1360(td) +msgid "" +"The firewall policy uuid that this firewall is associated with. This " +"firewall implements the rules contained in the firewall policy represented " +"by this uuid." +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking_adv_features.xml1370(title) +msgid "Basic Firewall-as-a-Service operations" +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking_adv_features.xml1373(para) +msgid "Create a firewall rule:" +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking_adv_features.xml1375(para) +msgid "" +"The CLI requires that a protocol value be provided. If the rule is protocol " +"agnostic, the 'any' value can be used." +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking_adv_features.xml1378(para) +msgid "" +"In addition to the protocol attribute, other attributes can be specified in " +"the firewall rule. See the previous section for the supported attributes." +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking_adv_features.xml1384(para) +msgid "Create a firewall policy:" +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking_adv_features.xml1386(para) +msgid "" +"The order of the rules specified above is important. A firewall policy can " +"be created without any rules and rules can be added later either via the " +"update operation (if adding multiple rules) or via the insert-rule operation" +" (if adding a single rule). Please check the CLI help for more details on " +"these operations." +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking_adv_features.xml1395(para) +msgid "" +"The reference implementation always adds a default deny all rule at the end " +"of each policy. This implies that if a firewall policy is created without " +"any rules and is associated with a firewall, that firewall blocks all " +"traffic." +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking_adv_features.xml1404(para) +msgid "Create a firewall:" +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking_adv_features.xml1409(para) +msgid "" +"The FWaaS features and the above workflow can also be accessed from the " +"Horizon user interface. This support is disabled by default, but can be " +"enabled by configuring " +"#HORIZON_DIR/openstack_dashboard/local/local_settings.py " +" and setting:" +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking_adv_features.xml1421(title) +msgid "Allowed-address-pairs" +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking_adv_features.xml1422(para) +msgid "" +"Allowed-address-pairs is an API extension that extends the port attribute. " +"This extension allows one to specify arbitrary mac_address/ip_address(cidr) " +"pairs that are allowed to pass through a port regardless of subnet. The main" +" use case for this is to enable the ability to use protocols such as VRRP " +"which floats an ip address between two instances to enable fast data plane " +"failover." +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking_adv_features.xml1430(para) +msgid "" +"The allowed-address-pairs extension is currently only supported by these " +"plug-ins: ML2, Nicira NVP, and Open vSwitch." +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking_adv_features.xml1435(title) +msgid "Basic allowed address pairs operations" +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking_adv_features.xml1438(para) +msgid "Create a port with a specific allowed-address-pairs:" +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking_adv_features.xml1443(para) +msgid "Update a port adding allowed-address-pairs:" +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking_adv_features.xml1449(para) +msgid "" +"Setting an allowed-address-pair that matches the mac_address and ip_address " +"of a port is prevented. This is because that would have no effect since " +"traffic matching the mac_address and ip_address is already allowed to pass " +"through the port." +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking_adv_features.xml1456(para) +msgid "" +"If your plug-in implements the port-security extension port-security-enabled" +" must be set to True on the port in order to have allowed-address-pairs on a" +" port. The reason for this is because if port-security-enabled is set to " +"False this allows all traffic to be passed through the port thus having " +"allowed-address-pairs would have no effect." +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking_adv_features.xml1469(title) +msgid "Plug-in specific extensions" +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking_adv_features.xml1471(para) +msgid "" +"Each vendor can choose to implement additional API extensions to the core " +"API. This section describes the extensions for each plug-in." +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking_adv_features.xml1475(title) +msgid "Nicira NVP extensions" +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking_adv_features.xml1476(para) +msgid "These sections explain Nicira NVP plug-in extensions." +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking_adv_features.xml1479(title) +msgid "Nicira NVP QoS extension" +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking_adv_features.xml1480(para) +msgid "" +"The Nicira NVP QoS extension rate-limits network ports to guarantee a " +"specific amount of bandwidth for each port. This extension, by default, is " +"only accessible by a tenant with an admin role but is configurable through " +"the policy.json file. To use this extension, create a " +"queue and specify the min/max bandwidth rates (kbps) and optionally set the " +"QoS Marking and DSCP value (if your network fabric uses these values to make" +" forwarding decisions). Once created, you can associate a queue with a " +"network. Then, when ports are created on that network they are automatically" +" created and associated with the specific queue size that was associated " +"with the network. Because one size queue for a every port on a network might" +" not be optimal, a scaling factor from the Nova flavor 'rxtx_factor' is " +"passed in from Compute when creating the port to scale the queue." +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking_adv_features.xml1499(para) +msgid "" +"Lastly, if you want to set a specific baseline QoS policy for the amount of " +"bandwidth a single port can use (unless a network queue is specified with " +"the network a port is created on) a default queue can be created in " +"Networking which then causes ports created to be associated with a queue of " +"that size times the rxtx scaling factor. Note that after a network or " +"default queue is specified, queues are added to ports that are subsequently " +"created but are not added to existing ports." +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking_adv_features.xml1512(title) +msgid "Nicira NVP QoS API abstractions" +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking_adv_features.xml1514(caption) +msgid "Nicira NVP QoS attributes" +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking_adv_features.xml1532(td) +msgid "UUID for the QoS queue." +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking_adv_features.xml1537(td) +msgid "False by default" +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking_adv_features.xml1538(td) +msgid "" +"If True, ports are created with this queue size unless the network port is " +"created or associated with a queue at port creation time." +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking_adv_features.xml1547(td) +msgid "Name for QoS queue." +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking_adv_features.xml1550(td) +msgid "min" +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking_adv_features.xml1552(td) +#: ./doc/admin-guide-cloud/section_networking_adv_features.xml1573(td) +msgid "0" +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking_adv_features.xml1553(td) +msgid "Minimum Bandwidth Rate (kbps)." +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking_adv_features.xml1557(td) +msgid "max" +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking_adv_features.xml1560(td) +msgid "Maximum Bandwidth Rate (kbps)." +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking_adv_features.xml1564(td) +msgid "qos_marking" +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking_adv_features.xml1566(td) +msgid "untrusted by default" +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking_adv_features.xml1567(td) +msgid "Whether QoS marking should be trusted or untrusted." +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking_adv_features.xml1571(td) +msgid "dscp" +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking_adv_features.xml1574(td) +msgid "DSCP Marking value." +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking_adv_features.xml1580(td) +msgid "The owner of the QoS queue." +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking_adv_features.xml1586(title) +#: ./doc/admin-guide-cloud/section_networking_adv_features.xml1591(caption) +msgid "Basic Nicira NVP QoS operations" +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking_adv_features.xml1587(para) +msgid "" +"This table shows example neutron commands that enable you to complete basic " +"queue operations:" +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking_adv_features.xml1604(para) +msgid "Creates QoS Queue (admin-only)." +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking_adv_features.xml1612(para) +msgid "Associates a queue with a network." +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking_adv_features.xml1620(para) +msgid "Creates a default system queue." +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking_adv_features.xml1626(para) +msgid "Lists QoS queues." +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking_adv_features.xml1633(para) +msgid "Deletes a QoS queue." +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking_adv_features.xml1644(title) +msgid "Nicira NVP provider networks extension" +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking_adv_features.xml1645(para) +msgid "" +"Provider networks can be implemented in different ways by the underlying NVP" +" platform." +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking_adv_features.xml1648(para) +msgid "" +"The FLAT and VLAN network types " +"use bridged transport connectors. These network types enable the attachment " +"of large number of ports. To handle the increased scale, the NVP plug-in can" +" back a single Openstack Network with a chain of NVP logical switches. You " +"can specify the maximum number of ports on each logical switch in this chain" +" on the max_lp_per_bridged_ls parameter, which has a " +"default value of 5,000." +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking_adv_features.xml1660(para) +msgid "" +"The recommended value for this parameter varies with the NVP version running" +" in the back-end, as shown in the following table." +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking_adv_features.xml1664(caption) +msgid "Recommended values for max_lp_per_bridged_ls" +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking_adv_features.xml1670(td) +msgid "NVP version" +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking_adv_features.xml1671(td) +msgid "Recommended Value" +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking_adv_features.xml1676(td) +msgid "2.x" +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking_adv_features.xml1677(td) +msgid "64" +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking_adv_features.xml1680(td) +msgid "3.0.x" +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking_adv_features.xml1681(td) +#: ./doc/admin-guide-cloud/section_networking_adv_features.xml1685(td) +msgid "5,000" +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking_adv_features.xml1684(td) +msgid "3.1.x" +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking_adv_features.xml1688(td) +msgid "3.2.x" +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking_adv_features.xml1689(td) +msgid "10,000" +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking_adv_features.xml1693(para) +msgid "" +"In addition to these network types, the NVP plug-in also supports a special " +"l3_ext network type, which maps external networks to " +"specific NVP gateway services as discussed in the next section." +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking_adv_features.xml1701(title) +msgid "Nicira NVP L3 extension" +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking_adv_features.xml1702(para) +msgid "" +"NVP exposes its L3 capabilities through gateway services which are usually " +"configured out of band from OpenStack. To use NVP with L3 capabilities, " +"first create a L3 gateway service in the NVP Manager. Next, in " +"/etc/neutron/plugins/nicira/nvp.ini set " +"default_l3_gw_service_uuid to this value. By default, " +"routers are mapped to this gateway service." +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking_adv_features.xml1712(title) +msgid "Nicira NVP L3 extension operations" +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking_adv_features.xml1713(para) +msgid "Create external network and map it to a specific NVP gateway service:" +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking_adv_features.xml1717(para) +msgid "Terminate traffic on a specific VLAN from a NVP gateway service:" +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking_adv_features.xml1724(title) +msgid "Operational status synchronization in the Nicira NVP plug-in" +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking_adv_features.xml1726(para) +msgid "" +"Starting with the Havana release, the Nicira NVP plug-in provides an " +"asynchronous mechanism for retrieving the operational status for neutron " +"resources from the NVP back-end; this applies to " +"network, port, and " +"router resources." +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking_adv_features.xml1733(para) +msgid "" +"The back-end is polled periodically, and the status for every resource is " +"retrieved; then the status in the Networking database is updated only for " +"the resources for which a status change occurred. As operational status is " +"now retrieved asynchronously, performance for GET " +"operations is consistently improved." +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking_adv_features.xml1741(para) +msgid "" +"Data to retrieve from the back-end are divided in chunks in order to avoid " +"expensive API requests; this is achieved leveraging NVP APIs response paging" +" capabilities. The minimum chunk size can be specified using a configuration" +" option; the actual chunk size is then determined dynamically according to: " +"total number of resources to retrieve, interval between two synchronization " +"task runs, minimum delay between two subsequent requests to the NVP back-" +"end." +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking_adv_features.xml1752(para) +msgid "" +"The operational status synchronization can be tuned or disabled using the " +"configuration options reported in this table; it is however worth noting " +"that the default values work fine in most cases." +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking_adv_features.xml1758(caption) +msgid "" +"Configuration options for tuning operational status synchronization in the " +"NVP plug-in" +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking_adv_features.xml1768(th) +msgid "Option name" +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking_adv_features.xml1769(th) +msgid "Group" +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking_adv_features.xml1770(th) +#: ./doc/admin-guide-cloud/section_networking-use.xml126(th) +msgid "Default value" +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking_adv_features.xml1771(th) +msgid "Type and constraints" +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking_adv_features.xml1772(th) +msgid "Notes" +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking_adv_features.xml1777(literal) +#: ./doc/admin-guide-cloud/section_networking_adv_features.xml1784(literal) +#: ./doc/admin-guide-cloud/section_networking_adv_features.xml1808(literal) +#: ./doc/admin-guide-cloud/section_networking_adv_features.xml1826(literal) +msgid "state_sync_interval" +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking_adv_features.xml1778(literal) +#: ./doc/admin-guide-cloud/section_networking_adv_features.xml1793(literal) +#: ./doc/admin-guide-cloud/section_networking_adv_features.xml1805(literal) +#: ./doc/admin-guide-cloud/section_networking_adv_features.xml1818(literal) +#: ./doc/admin-guide-cloud/section_networking_adv_features.xml1839(literal) +msgid "nvp_sync" +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking_adv_features.xml1779(td) +msgid "120 seconds" +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking_adv_features.xml1780(td) +#: ./doc/admin-guide-cloud/section_networking_adv_features.xml1820(td) +msgid "Integer; no constraint." +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking_adv_features.xml1781(td) +msgid "" +"Interval in seconds between two run of the synchronization task. If the " +"synchronization task takes more than seconds to execute, a " +"new instance of the task is started as soon as the other is completed. " +"Setting the value for this option to 0 will disable the synchronization " +"task." +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking_adv_features.xml1792(literal) +#: ./doc/admin-guide-cloud/section_networking_adv_features.xml1799(literal) +msgid "max_random_sync_delay" +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking_adv_features.xml1794(td) +msgid "0 seconds" +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking_adv_features.xml1796(literal) +#: ./doc/admin-guide-cloud/section_networking_adv_features.xml1804(literal) +#: ./doc/admin-guide-cloud/section_networking_adv_features.xml1828(literal) +msgid "min_sync_req_delay" +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking_adv_features.xml1795(td) +msgid "Integer. Must not exceed " +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking_adv_features.xml1797(td) +msgid "" +"When different from zero, a random delay between 0 and will" +" be added before processing the next chunk." +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking_adv_features.xml1806(td) +msgid "10 seconds" +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking_adv_features.xml1807(td) +msgid "Integer. Must not exceed ." +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking_adv_features.xml1809(td) +msgid "" +"The value of this option can be tuned according to the observed load on the " +"NVP controllers. Lower values will result in faster synchronization, but " +"might increase the load on the controller cluster." +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking_adv_features.xml1817(literal) +#: ./doc/admin-guide-cloud/section_networking_adv_features.xml1832(literal) +msgid "min_chunk_size" +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking_adv_features.xml1819(td) +msgid "500 resources" +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking_adv_features.xml1821(td) +msgid "" +"Minimum number of resources to retrieve from the back-end for each " +"synchronization chunk. The expected number of synchronization chunks is " +"given by the ratio between and . This size " +"of a chunk might increase if the total number of resources is such that more" +" than resources must be fetched in one chunk with the " +"current number of chunks." +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking_adv_features.xml1838(literal) +msgid "always_read_status" +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking_adv_features.xml1841(td) +msgid "Boolean; no constraint." +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking_adv_features.xml1845(literal) +msgid "GET" +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking_adv_features.xml1842(td) +msgid "" +"When this option is enabled, the operational status will always be retrieved" +" from the NVP back-end ad every request. In this case it is" +" advisable to disable the synchronization task." +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking_adv_features.xml1851(para) +msgid "" +"When running multiple OpenStack Networking server instances, the status " +"synchronization task should not run on every node; doing so sends " +"unnecessary traffic to the NVP back-end and performs unnecessary DB " +"operations. Set the configuration " +"option to a non-zero value exclusively on a node designated for back-end " +"status synchronization." +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking_adv_features.xml1860(para) +msgid "" +"The fields=status parameter in Networking API " +"requests always triggers an explicit query to the NVP back end, even when " +"you enable asynchronous state synchronization. For example, GET " +"/v2.0/networks/<net-id>?fields=status&fields=name." +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking_adv_features.xml1869(title) +msgid "Big Switch plug-in extensions" +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking_adv_features.xml1870(para) +msgid "" +"This section explains the Big Switch Neutron plug-in-specific extension." +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking_adv_features.xml1873(title) +msgid "Big Switch router rules" +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking_adv_features.xml1874(para) +msgid "" +"Big Switch allows router rules to be added to each tenant router. These " +"rules can be used to enforce routing policies such as denying traffic " +"between subnets or traffic to external networks. By enforcing these at the " +"router level, network segmentation policies can be enforced across many VMs " +"that have differing security groups." +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking_adv_features.xml1882(title) +msgid "Router rule attributes" +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking_adv_features.xml1883(para) +msgid "" +"Each tenant router has a set of router rules associated with it. Each router" +" rule has the attributes in this table. Router rules and their attributes " +"can be set using the command, through the Horizon interface" +" or the Neutron API." +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking_adv_features.xml1891(caption) +msgid "Big Switch Router rule attributes" +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking_adv_features.xml1900(th) +msgid "Required" +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking_adv_features.xml1901(th) +msgid "Input Type" +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking_adv_features.xml1907(td) +msgid "source" +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking_adv_features.xml1909(td) +#: ./doc/admin-guide-cloud/section_networking_adv_features.xml1918(td) +msgid "A valid CIDR or one of the keywords 'any' or 'external'" +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking_adv_features.xml1911(td) +msgid "" +"The network that a packet's source IP must match for the rule to be applied" +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking_adv_features.xml1916(td) +msgid "destination" +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking_adv_features.xml1920(td) +msgid "" +"The network that a packet's destination IP must match for the rule to be " +"applied" +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking_adv_features.xml1927(td) +msgid "'permit' or 'deny'" +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking_adv_features.xml1928(td) +msgid "" +"Determines whether or not the matched packets will allowed to cross the " +"router" +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking_adv_features.xml1933(td) +msgid "nexthop" +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking_adv_features.xml1934(td) +msgid "No" +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking_adv_features.xml1937(literal) +msgid "1.1.1.1+1.1.1.2" +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking_adv_features.xml1935(td) +msgid "" +"A plus-separated (+) list of next-hop IP addresses. For example, " +"." +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking_adv_features.xml1938(td) +msgid "" +"Overrides the default virtual router used to handle traffic for packets that" +" match the rule" +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking_adv_features.xml1947(title) +msgid "Order of rule processing" +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking_adv_features.xml1948(para) +msgid "" +"The order of router rules has no effect. Overlapping rules are evaluated " +"using longest prefix matching on the source and destination fields. The " +"source field is matched first so it always takes higher precedence over the " +"destination field. In other words, longest prefix matching is used on the " +"destination field only if there are multiple matching rules with the same " +"source." +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking_adv_features.xml1960(title) +msgid "Big Switch router rules operations" +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking_adv_features.xml1961(para) +msgid "" +"Router rules are configured with a router update operation in OpenStack " +"Networking. The update overrides any previous rules so all rules must be " +"provided at the same time." +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking_adv_features.xml1966(para) +msgid "" +"Update a router with rules to permit traffic by default but block traffic " +"from external networks to the 10.10.10.0/24 subnet:" +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking_adv_features.xml1969(replaceable) +#: ./doc/admin-guide-cloud/section_networking_adv_features.xml1974(replaceable) +#: ./doc/admin-guide-cloud/section_networking_adv_features.xml1979(replaceable) +msgid "Router-UUID" +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking_adv_features.xml1972(para) +msgid "Specify alternate next-hop addresses for a specific subnet:" +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking_adv_features.xml1977(para) +msgid "Block traffic between two subnets while allowing everything else:" +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking_adv_features.xml1987(title) +msgid "L3 metering" +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking_adv_features.xml1988(para) +msgid "" +"The L3 metering API extension enables administrators to configure IP ranges " +"and assign a specified label to them to be able to measure traffic that goes" +" through a virtual router." +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking_adv_features.xml1992(para) +msgid "" +"The L3 metering extension is decoupled from the technology that implements " +"the measurement. Two abstractions have been added: One is the metering label" +" that can contain metering rules. Because a metering label is associated " +"with a tenant, all virtual routers in this tenant are associated with this " +"label." +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking_adv_features.xml1999(title) +msgid "L3 metering API abstractions" +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking_adv_features.xml2001(caption) +msgid "Label" +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking_adv_features.xml2019(td) +msgid "UUID for the metering label." +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking_adv_features.xml2025(td) +msgid "Human-readable name for the metering label. Might not be unique." +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking_adv_features.xml2032(td) +msgid "The optional description for the metering label." +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking_adv_features.xml2039(td) +msgid "Owner of the metering label." +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking_adv_features.xml2044(caption) +msgid "Rules" +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking_adv_features.xml2062(td) +msgid "UUID for the metering rule." +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking_adv_features.xml2066(td) +msgid "String (Either ingress or egress)" +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking_adv_features.xml2067(td) +#: ./doc/admin-guide-cloud/section_networking_adv_features.xml2160(replaceable) +msgid "ingress" +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking_adv_features.xml2068(td) +msgid "" +"The direction in which metering rule is applied, either ingress or egress." +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking_adv_features.xml2072(td) +msgid "metering_label_id" +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking_adv_features.xml2076(para) +msgid "The metering label ID to associate with this metering rule." +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking_adv_features.xml2081(td) +msgid "excluded" +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking_adv_features.xml2084(td) +msgid "" +"Specify whether the remote_ip_prefix will be excluded or not from traffic " +"counters of the metering label (for example, to not count the traffic of a " +"specific IP address of a range)." +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking_adv_features.xml2092(td) +msgid "String (CIDR)" +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking_adv_features.xml2094(td) +msgid "Indicates remote IP prefix to be associated with this metering rule." +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking_adv_features.xml2102(title) +msgid "Basic L3 metering operations" +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking_adv_features.xml2103(para) +msgid "Only administrators can manage the L3 metering labels and rules." +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking_adv_features.xml2105(para) +msgid "" +"This table shows example commands that enable you to " +"complete basic L3 metering operations:" +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking_adv_features.xml2121(para) +msgid "Creates a metering label." +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking_adv_features.xml2124(replaceable) +#: ./doc/admin-guide-cloud/section_networking_adv_features.xml2142(replaceable) +#: ./doc/admin-guide-cloud/section_networking_adv_features.xml2151(replaceable) +#: ./doc/admin-guide-cloud/section_networking_adv_features.xml2160(replaceable) +#: ./doc/admin-guide-cloud/section_networking_adv_features.xml2161(replaceable) +msgid "label1" +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking_adv_features.xml2124(replaceable) +msgid "\"description of label1\"" +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking_adv_features.xml2129(para) +msgid "Lists metering labels." +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking_adv_features.xml2137(para) +msgid "Shows information for a specified label." +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking_adv_features.xml2141(replaceable) +#: ./doc/admin-guide-cloud/section_networking_adv_features.xml2150(replaceable) +#: ./doc/admin-guide-cloud/section_networking_adv_features.xml2159(replaceable) +msgid "label-uuid" +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking_adv_features.xml2147(para) +msgid "Deletes a metering label." +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking_adv_features.xml2156(para) +msgid "Creates a metering rule." +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking_adv_features.xml2159(replaceable) +#: ./doc/admin-guide-cloud/section_networking-use.xml208(option) +#: ./doc/admin-guide-cloud/section_networking-use.xml219(option) +#: ./doc/admin-guide-cloud/section_networking-use.xml242(option) +msgid "cidr" +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking_adv_features.xml2160(replaceable) +msgid "10.0.0.0/24" +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking_adv_features.xml2161(replaceable) +msgid "20.0.0.0/24" +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking_adv_features.xml2166(para) +msgid "Lists metering all label rules." +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking_adv_features.xml2175(para) +msgid "Shows information for a specified label rule." +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking_adv_features.xml2179(replaceable) +#: ./doc/admin-guide-cloud/section_networking_adv_features.xml2185(replaceable) +msgid "rule-uuid" +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking_adv_features.xml2183(td) +msgid "Deletes a metering label rule." +msgstr "" + +#: ./doc/admin-guide-cloud/section_multi_backend.xml5(title) +msgid "Configure a multiple-storage back-end" +msgstr "" + +#: ./doc/admin-guide-cloud/section_multi_backend.xml6(para) +msgid "" +"This section presents the multi back-end storage feature introduced with the" +" Grizzly release. Multi back-end allows the creation of several back-end " +"storage solutions serving the same OpenStack Compute configuration. " +"Basically, multi back-end launches one cinder-" +"volume for each back-end." +msgstr "" + +#: ./doc/admin-guide-cloud/section_multi_backend.xml12(para) +msgid "" +"In a multi back-end configuration, each back-end has a name " +"(volume_backend_name). Several back-ends can have the " +"same name. In that case, the scheduler properly decides which back-end the " +"volume has to be created in." +msgstr "" + +#: ./doc/admin-guide-cloud/section_multi_backend.xml17(para) +msgid "" +"The name of the back-end is declared as an extra-specification of a volume " +"type (such as, volume_backend_name=LVM_iSCSI). When a " +"volume is created, the scheduler chooses an appropriate back-end to handle " +"the request, according to the volume type specified by the user." +msgstr "" + +#: ./doc/admin-guide-cloud/section_multi_backend.xml24(title) +msgid "Enable multi back-end" +msgstr "" + +#: ./doc/admin-guide-cloud/section_multi_backend.xml25(para) +msgid "" +"To enable a multi back-end configuration, you must set the " +" flag in the " +"cinder.conf file. This flag defines the names " +"(separated by a comma) of the configuration groups for the different back-" +"ends: one name is associated to one configuration group for a back-end (such" +" as, [lvmdriver-1])." +msgstr "" + +#: ./doc/admin-guide-cloud/section_multi_backend.xml33(para) +msgid "" +"The configuration group name is not related to the " +"volume_backend_name." +msgstr "" + +#: ./doc/admin-guide-cloud/section_multi_backend.xml36(para) +msgid "" +"The options for a configuration group must be defined in the group (or " +"default options are used). All the standard Block Storage configuration " +"options (volume_group, volume_driver, " +"and so on) might be used in a configuration group. Configuration values in " +"the [DEFAULT] configuration group are not used." +msgstr "" + +#: ./doc/admin-guide-cloud/section_multi_backend.xml44(para) +msgid "These examples show three back-ends:" +msgstr "" + +#: ./doc/admin-guide-cloud/section_multi_backend.xml59(para) +msgid "" +"In this configuration, lvmdriver-1 and " +"lvmdriver-2 have the same " +"volume_backend_name. If a volume creation requests the " +"LVM_iSCSI back-end name, the scheduler uses the capacity " +"filter scheduler to choose the most suitable driver, which is either " +"lvmdriver-1 or lvmdriver-2. The " +"capacity filter scheduler is enabled by default. The next section provides " +"more information. In addition, this example presents a " +"lvmdriver-3 back-end." +msgstr "" + +#: ./doc/admin-guide-cloud/section_multi_backend.xml72(title) +msgid "Configure Block Storage scheduler multi back-end" +msgstr "" + +#: ./doc/admin-guide-cloud/section_multi_backend.xml73(para) +msgid "" +"You must enable the option to use multi " +"back-end. Filter scheduler acts in two steps:" +msgstr "" + +#: ./doc/admin-guide-cloud/section_multi_backend.xml78(para) +msgid "" +"The filter scheduler filters the available back-ends. By default, " +"AvailabilityZoneFilter, CapacityFilter" +" and CapabilitiesFilter are enabled." +msgstr "" + +#: ./doc/admin-guide-cloud/section_multi_backend.xml86(para) +msgid "" +"The filter scheduler weighs the previously filtered back-ends. By default, " +"CapacityWeigher is enabled. The " +"CapacityWeigher attributes higher scores to back-ends " +"with the most available." +msgstr "" + +#: ./doc/admin-guide-cloud/section_multi_backend.xml94(para) +msgid "" +"The scheduler uses the filtering and weighing process to pick the best back-" +"end to handle the request, and explicitly creates volumes on specific back-" +"ends through the use of volume types." +msgstr "" + +#: ./doc/admin-guide-cloud/section_multi_backend.xml99(para) +msgid "" +"To enable the filter scheduler, add this line to the " +"cinder.conf configuration file:" +msgstr "" + +#: ./doc/admin-guide-cloud/section_multi_backend.xml103(para) +msgid "" +"While the Block Storage Scheduler defaults to " +" in Grizzly, this setting is not required." +msgstr "" + +#: ./doc/admin-guide-cloud/section_multi_backend.xml110(title) +msgid "Volume type" +msgstr "" + +#: ./doc/admin-guide-cloud/section_multi_backend.xml111(para) +msgid "" +"Before using it, a volume type has to be declared to Block Storage. This can" +" be done by the following command:" +msgstr "" + +#: ./doc/admin-guide-cloud/section_multi_backend.xml114(para) +msgid "" +"Then, an extra-specification have to be created to link the volume type to a" +" back-end name. Run this command:" +msgstr "" + +#: ./doc/admin-guide-cloud/section_multi_backend.xml118(para) +msgid "" +"This example creates a lvm volume type with " +"volume_backend_name=LVM_iSCSI as extra-specifications." +msgstr "" + +#: ./doc/admin-guide-cloud/section_multi_backend.xml121(para) +msgid "Create another volume type:" +msgstr "" + +#: ./doc/admin-guide-cloud/section_multi_backend.xml124(para) +msgid "" +"This second volume type is named lvm_gold and has " +"LVM_iSCSI_b as back-end name." +msgstr "" + +#: ./doc/admin-guide-cloud/section_multi_backend.xml129(para) +msgid "To list the extra-specifications, use this command:" +msgstr "" + +#: ./doc/admin-guide-cloud/section_multi_backend.xml134(para) +msgid "" +"If a volume type points to a volume_backend_name that " +"does not exist in the Block Storage configuration, the " +"filter_scheduler returns an error that it cannot find a " +"valid host with the suitable back-end." +msgstr "" + +#: ./doc/admin-guide-cloud/section_multi_backend.xml143(title) +msgid "Usage" +msgstr "" + +#: ./doc/admin-guide-cloud/section_multi_backend.xml144(para) +msgid "" +"When you create a volume, you must specify the volume type. The extra-" +"specifications of the volume type are used to determine which back-end has " +"to be used. Considering the cinder.conf " +"described previously, the scheduler creates this volume on " +"lvmdriver-1 or lvmdriver-2." +msgstr "" + +#: ./doc/admin-guide-cloud/section_multi_backend.xml153(para) +msgid "This second volume is created on lvmdriver-3." +msgstr "" + +#: ./doc/admin-guide-cloud/section_ts_multipath_warn.xml6(title) +msgid "Multipath Call Failed Exit" +msgstr "" + +#: ./doc/admin-guide-cloud/section_ts_multipath_warn.xml9(para) +msgid "" +"Multipath call failed exit. This warning occurs in the Compute log if you do" +" not have the optional multipath-tools package " +"installed on the Compute node. This is an optional package and the volume " +"attachment does work without the multipath tools installed. If the multipath-tools package is installed on the Compute node, it is " +"used to perform the volume attachment. The IDs in your message are unique to" +" your system." +msgstr "" + +#: ./doc/admin-guide-cloud/section_ts_multipath_warn.xml21(para) +msgid "" +"Run the following command on the Compute node to install the multipath-tools packages." +msgstr "" + +#: ./doc/admin-guide-cloud/section_volume-migration.xml6(title) +msgid "Migrate volumes" +msgstr "" + +#: ./doc/admin-guide-cloud/section_volume-migration.xml7(para) +msgid "" +"The Havana release of OpenStack introduces the ability to migrate volumes " +"between back-ends. Migrating a volume transparently moves its data from the " +"current back-end for the volume to a new one. This is an administrator " +"function, and can be used for functions including storage evacuation (for " +"maintenance or decommissioning), or manual optimizations (for example, " +"performance, reliability, or cost)." +msgstr "" + +#: ./doc/admin-guide-cloud/section_volume-migration.xml14(para) +msgid "These workflows are possible for a migration:" +msgstr "" + +#: ./doc/admin-guide-cloud/section_volume-migration.xml17(para) +msgid "" +"If the storage can migrate the volume on its own, it is given the " +"opportunity to do so. This allows the Block Storage driver to enable " +"optimizations that the storage might be able to perform. If the back-end is " +"not able to perform the migration, the Block Storage Service uses one of two" +" generic flows, as follows." +msgstr "" + +#: ./doc/admin-guide-cloud/section_volume-migration.xml26(para) +msgid "" +"If the volume is not attached, the Block Storage Service creates a volume " +"and copies the data from the original to the new volume. Note: While most " +"back-ends support this function, not all do. See driver documentation in the" +" OpenStack Configuration " +"Reference for more details." +msgstr "" + +#: ./doc/admin-guide-cloud/section_volume-migration.xml37(para) +msgid "" +"If the volume is attached to a VM instance, the Block Storage Service " +"creates a volume, and calls Compute to copy the data from the original to " +"the new volume. Currently this is supported only by the Compute libvirt " +"driver." +msgstr "" + +#: ./doc/admin-guide-cloud/section_volume-migration.xml44(para) +msgid "" +"As an example, this scenario shows two LVM back-ends and migrates an " +"attached volume from one to the other. This scenario uses the third " +"migration flow." +msgstr "" + +#: ./doc/admin-guide-cloud/section_volume-migration.xml47(para) +msgid "First, list the available back-ends:" +msgstr "" + +#: ./doc/admin-guide-cloud/section_volume-migration.xml51(para) +msgid "" +"Next, as the admin user, you can see the current status of the volume " +"(replace the example ID with your own):" +msgstr "" + +#: ./doc/admin-guide-cloud/section_volume-migration.xml75(para) +msgid "Note these attributes:" +msgstr "" + +#: ./doc/admin-guide-cloud/section_volume-migration.xml78(para) +msgid "" +"os-vol-host-attr:host - the volume's current back-end." +msgstr "" + +#: ./doc/admin-guide-cloud/section_volume-migration.xml82(para) +msgid "" +"os-vol-mig-status-attr:migstat - the status of this " +"volume's migration ('None' means that a migration is not currently in " +"progress)." +msgstr "" + +#: ./doc/admin-guide-cloud/section_volume-migration.xml87(para) +msgid "" +"os-vol-mig-status-attr:name_id - the volume ID that this " +"volume's name on the back-end is based on. Before a volume is ever migrated," +" its name on the back-end storage may be based on the volume's ID (see the " +"volume_name_template configuration parameter). For example, if " +"volume_name_template is kept as the default value (volume-%s), your first " +"LVM back-end has a logical volume named volume-" +"6088f80a-f116-4331-ad48-9afb0dfb196c. During the course of a " +"migration, if you create a volume and copy over the data, the volume get the" +" new name but keeps its original ID. This is exposed by the " +"name_id attribute." +msgstr "" + +#: ./doc/admin-guide-cloud/section_volume-migration.xml104(para) +msgid "Migrate this volume to the second LVM back-end:" +msgstr "" + +#: ./doc/admin-guide-cloud/section_volume-migration.xml106(para) +msgid "" +"You can use the command to see the status of the migration." +" While migrating, the migstat attribute shows states such" +" as migrating or completing. On error," +" migstat is set to None and the " +"host attribute shows the original host. On success, in " +"this example, the output looks like:" +msgstr "" + +#: ./doc/admin-guide-cloud/section_volume-migration.xml137(para) +msgid "" +"Note that migstat is None, host is the" +" new host, and name_id holds the ID of the volume created" +" by the migration. If you look at the second LVM back-end, you find the " +"logical volume volume-133d1f56-9ffc-" +"4f57-8798-d5217d851862." +msgstr "" + +#: ./doc/admin-guide-cloud/section_volume-migration.xml144(para) +msgid "" +"The migration is not visible to non-admin users (for example, through the " +"volume status). However, some operations are not allowed " +"while a migration is taking place, such as attaching/detaching a volume and " +"deleting a volume. If a user performs such an action during a migration, an " +"error is returned." +msgstr "" + +#: ./doc/admin-guide-cloud/section_volume-migration.xml152(para) +msgid "Migrating volumes that have snapshots are currently not allowed." +msgstr "" + +#: ./doc/admin-guide-cloud/ch_dashboard.xml7(title) +#: ./doc/admin-guide-cloud/ch_compute.xml766(title) +msgid "Dashboard" +msgstr "" + +#: ./doc/admin-guide-cloud/ch_dashboard.xml8(para) +msgid "" +"The OpenStack dashboard is a web-based interface that allows you to manage " +"OpenStack resources and services. The dashboard allows you to interact with " +"the OpenStack Compute cloud controller using the OpenStack APIs. For more " +"information about installing and configuring the dashboard, see the " +"OpenStack Installation Guide for your operating " +"system." +msgstr "" + +#: ./doc/admin-guide-cloud/ch_dashboard.xml20(para) +msgid ", for customizing the dashboard." +msgstr "" + +#: ./doc/admin-guide-cloud/ch_dashboard.xml24(para) +msgid "" +", for setting up session storage for " +"the dashboard." +msgstr "" + +#: ./doc/admin-guide-cloud/ch_dashboard.xml28(para) +msgid "" +"The " +" Horizon documentation, for deploying the dashboard." +msgstr "" + +#: ./doc/admin-guide-cloud/ch_dashboard.xml32(para) +msgid "" +"The OpenStack End User Guide, for" +" launching instances with the dashboard.." +msgstr "" + +#: ./doc/admin-guide-cloud/ch_dashboard.xml16(para) +msgid "For more information about using the dashboard, see: " +msgstr "" + +#: ./doc/admin-guide-cloud/section_ts_attach_vol_fail_not_JSON.xml5(title) +msgid "Nova volume attach error, not JSON serializable" +msgstr "" + +#: ./doc/admin-guide-cloud/section_ts_attach_vol_fail_not_JSON.xml8(para) +msgid "" +"When you attach a nova volume to a VM, you will see the error with stack " +"trace in /var/log/nova/nova-volume.log. The JSON " +"serializable issue is caused by an RPC response timeout." +msgstr "" + +#: ./doc/admin-guide-cloud/section_ts_attach_vol_fail_not_JSON.xml16(para) +msgid "" +"Make sure your iptables allow port 3260 communication on the ISC controller." +" Run this command:" +msgstr "" + +#: ./doc/admin-guide-cloud/section_ts_attach_vol_fail_not_JSON.xml19(para) +msgid "" +"If the port communication is properly configured, you can try running this " +"command." +msgstr "" + +#: ./doc/admin-guide-cloud/section_ts_attach_vol_fail_not_JSON.xml23(para) +msgid "This service does not exist on Debian or Ubuntu." +msgstr "" + +#: ./doc/admin-guide-cloud/section_ts_attach_vol_fail_not_JSON.xml26(para) +msgid "" +"If you continue to get the RPC response time out, your ISC controller and " +"KVM host might be incompatible." +msgstr "" + +#: ./doc/admin-guide-cloud/section_ts_duplicate_3par_host.xml4(title) +msgid "Duplicate 3PAR host" +msgstr "" + +#: ./doc/admin-guide-cloud/section_ts_duplicate_3par_host.xml7(para) +msgid "" +"This error may be caused by a volume being exported outside of OpenStack " +"using a host name different from the system name that OpenStack expects. " +"This error could be displayed with the IQN if the host was exported using " +"iSCSI." +msgstr "" + +#: ./doc/admin-guide-cloud/section_ts_duplicate_3par_host.xml13(para) +msgid "" +"Change the 3PAR host name to match the one that OpenStack expects. The 3PAR " +"host constructed by the driver uses just the local hostname, not the fully " +"qualified domain name (FQDN) of the compute host. For example, if the FQDN " +"was myhost.example.com, just " +"myhost would be used as the 3PAR hostname. IP addresses" +" are not allowed as host names on the 3PAR storage server." +msgstr "" + +#. When image changes, this message will be marked fuzzy or untranslated for +#. you. +#. It doesn't matter what you translate it to: it's not used at all. +#: ./doc/admin-guide-cloud/ch_compute.xml214(None) +msgid "" +"@@image: '../common/figures/instance-life-1.png'; " +"md5=c7e56263f9ffb5a5cffb59fbc5ffba35" +msgstr "" + +#. When image changes, this message will be marked fuzzy or untranslated for +#. you. +#. It doesn't matter what you translate it to: it's not used at all. +#: ./doc/admin-guide-cloud/ch_compute.xml233(None) +msgid "" +"@@image: '../common/figures/instance-life-2.png'; " +"md5=84aed8a4c2575548c2f8bacf496465ac" +msgstr "" + +#. When image changes, this message will be marked fuzzy or untranslated for +#. you. +#. It doesn't matter what you translate it to: it's not used at all. +#: ./doc/admin-guide-cloud/ch_compute.xml275(None) +msgid "" +"@@image: '../common/figures/instance-life-3.png'; " +"md5=e25d1bd617373f95e1b8a12605a65ac6" +msgstr "" + +#. When image changes, this message will be marked fuzzy or untranslated for +#. you. +#. It doesn't matter what you translate it to: it's not used at all. +#: ./doc/admin-guide-cloud/ch_compute.xml1543(None) +msgid "" +"@@image: '../common/figures/SCH_5007_V00_NUAC-multi_nic_OpenStack-Flat-" +"manager.jpg'; md5=31f7e15a45d042bd9d6499631e2f3ccc" +msgstr "" + +#. When image changes, this message will be marked fuzzy or untranslated for +#. you. +#. It doesn't matter what you translate it to: it's not used at all. +#: ./doc/admin-guide-cloud/ch_compute.xml1553(None) +msgid "" +"@@image: '../common/figures/SCH_5007_V00_NUAC-multi_nic_OpenStack-Flat-DHCP-" +"manager.jpg'; md5=0f33a228f1dec4a4e4424dd5ee81bde8" +msgstr "" + +#. When image changes, this message will be marked fuzzy or untranslated for +#. you. +#. It doesn't matter what you translate it to: it's not used at all. +#: ./doc/admin-guide-cloud/ch_compute.xml1563(None) +msgid "" +"@@image: '../common/figures/SCH_5007_V00_NUAC-multi_nic_OpenStack-VLAN-" +"manager.jpg'; md5=0acaf3e2041f941d8fee2d111f37e7ac" +msgstr "" + +#: ./doc/admin-guide-cloud/ch_compute.xml9(title) +#: ./doc/admin-guide-cloud/section_networking-config-identity.xml102(title) +msgid "Compute" +msgstr "" + +#: ./doc/admin-guide-cloud/ch_compute.xml10(para) +msgid "" +"The OpenStack Compute service allows you to control an Infrastructure-" +"as-a-Service (IaaS) cloud computing platform. It gives you control over " +"instances and networks, and allows you to manage access to the cloud through" +" users and projects." +msgstr "" + +#: ./doc/admin-guide-cloud/ch_compute.xml15(para) +msgid "" +"Compute does not include any virtualization software. Instead, it defines " +"drivers that interact with underlying virtualization mechanisms that run on " +"your host operating system, and exposes functionality over a web-based API." +msgstr "" + +#: ./doc/admin-guide-cloud/ch_compute.xml20(title) +msgid "Hypervisors" +msgstr "" + +#: ./doc/admin-guide-cloud/ch_compute.xml21(para) +msgid "" +"Compute controls hypervisors through an API server. Selecting the best " +"hypervisor to use can be difficult, and you must take budget, resource " +"constraints, supported features, and required technical specifications into " +"account. However, the majority of OpenStack development is done on systems " +"using KVM and Xen-based hypervisors. For a detailed list of features and " +"support across different hypervisors, see http://wiki.openstack.org/HypervisorSupportMatrix." +msgstr "" + +#: ./doc/admin-guide-cloud/ch_compute.xml31(para) +msgid "" +"You can also orchestrate clouds using multiple hypervisors in different " +"availability zones. The types of virtualization standards that can be used " +"with Compute include:" +msgstr "" + +#: ./doc/admin-guide-cloud/ch_compute.xml40(link) +msgid "Baremetal" +msgstr "" + +#: ./doc/admin-guide-cloud/ch_compute.xml54(link) +msgid "Kernel-based Virtual Machine (KVM)" +msgstr "" + +#: ./doc/admin-guide-cloud/ch_compute.xml60(link) +msgid "Linux Containers (LXC)" +msgstr "" + +#: ./doc/admin-guide-cloud/ch_compute.xml66(link) +msgid "Quick Emulator (QEMU)" +msgstr "" + +#: ./doc/admin-guide-cloud/ch_compute.xml73(link) +msgid "User Mode Linux (UML)" +msgstr "" + +#: ./doc/admin-guide-cloud/ch_compute.xml80(link) +msgid "VMWare vSphere" +msgstr "" + +#: ./doc/admin-guide-cloud/ch_compute.xml87(link) +msgid "Xen" +msgstr "" + +#: ./doc/admin-guide-cloud/ch_compute.xml91(para) +msgid "" +"For more information about hypervisors, see the Hypervisors section in the " +"OpenStack Configuration Reference." +msgstr "" + +#: ./doc/admin-guide-cloud/ch_compute.xml98(title) +msgid "Tenants, users, and roles" +msgstr "" + +#: ./doc/admin-guide-cloud/ch_compute.xml99(para) +msgid "" +"The Compute system is designed to be used by different consumers in the form" +" of tenants on a shared system, and role-based access assignments. Roles " +"control the actions that a user is allowed to perform." +msgstr "" + +#: ./doc/admin-guide-cloud/ch_compute.xml103(para) +msgid "" +"Tenants are isolated resource containers that form the principal " +"organizational structure within the Compute service. They consist of an " +"individual VLAN, and volumes, instances, images, keys, and users. A user can" +" specify the tenant by appending :project_id to their " +"access key. If no tenant is specified in the API request, Compute attempts " +"to use a tenant with the same ID as the user." +msgstr "" + +#: ./doc/admin-guide-cloud/ch_compute.xml111(para) +msgid "For tenants, quota controls are available to limit the:" +msgstr "" + +#: ./doc/admin-guide-cloud/ch_compute.xml115(para) +msgid "number of volumes that may be launched." +msgstr "" + +#: ./doc/admin-guide-cloud/ch_compute.xml118(para) +msgid "number of processor cores and the amount of RAM that can be allocated." +msgstr "" + +#: ./doc/admin-guide-cloud/ch_compute.xml122(para) +msgid "" +"floating IP addresses assigned to any instance when it launches. This allows" +" instances to have the same publicly accessible IP addresses." +msgstr "" + +#: ./doc/admin-guide-cloud/ch_compute.xml127(para) +msgid "" +"fixed IP addresses assigned to the same instance when it launches. This " +"allows instances to have the same publicly or privately accessible IP " +"addresses." +msgstr "" + +#: ./doc/admin-guide-cloud/ch_compute.xml133(para) +msgid "" +"Roles control the actions a user is allowed to perform. By default, most " +"actions do not require a particular role, but you can configure them by " +"editing the policy.json file for user roles. For " +"example, a rule can be defined so that a user must have the " +"admin role in order to be able to allocate a public " +"IP address." +msgstr "" + +#: ./doc/admin-guide-cloud/ch_compute.xml140(para) +msgid "" +"A tenant limits users' access to particular images. Each user is assigned a " +"username and password. Keypairs granting access to an instance are enabled " +"for each user, but quotas are set, so that each tenant can control resource " +"consumption across available hardware resources." +msgstr "" + +#: ./doc/admin-guide-cloud/ch_compute.xml147(para) +msgid "" +"Earlier versions of OpenStack used the term project instead of tenant. Because of this legacy terminology, " +"some command-line tools use --project_id where you " +"would normally expect to enter a tenant ID." +msgstr "" + +#: ./doc/admin-guide-cloud/ch_compute.xml157(title) +msgid "Images and instances" +msgstr "" + +#: ./doc/admin-guide-cloud/ch_compute.xml158(para) +msgid "" +"Disk images provide templates for virtual machine file systems. The Glance " +"service manages storage and management of images." +msgstr "" + +#: ./doc/admin-guide-cloud/ch_compute.xml161(para) +msgid "" +"Instances are the individual virtual machines that run on physical compute " +"nodes. Users can launch any number of instances from the same image. Each " +"launched instance runs from a copy of the base image so that any changes " +"made to the instance do not affect the base image. You can take snapshots of" +" running instances to create an image based on the current disk state of a " +"particular instance. The Compute services manages instances." +msgstr "" + +#: ./doc/admin-guide-cloud/ch_compute.xml169(para) +msgid "" +"For more information about creating and troubleshooting images, see the " +"Manage Images section of the " +"OpenStack Admin User Guide." +msgstr "" + +#: ./doc/admin-guide-cloud/ch_compute.xml175(para) +msgid "" +"For more information about image configuration options, see the Image Services section" +" of the OpenStack Configuration Reference." +msgstr "" + +#: ./doc/admin-guide-cloud/ch_compute.xml181(para) +msgid "" +"When you launch an instance, you must choose a flavor, " +"which represents a set of virtual resources. Flavors define how many virtual" +" CPUs an instance has and the amount of RAM and size of its ephemeral disks." +" OpenStack provides a number of predefined flavors that you can edit or add " +"to. Users must select from the set of available flavors defined on their " +"cloud." +msgstr "" + +#: ./doc/admin-guide-cloud/ch_compute.xml189(para) +msgid "" +"For more information about flavors, see the Flavors section in the " +"OpenStack Operations Guide." +msgstr "" + +#: ./doc/admin-guide-cloud/ch_compute.xml193(para) +msgid "" +"You can add and remove additional resources from running instances, such as " +"persistent volume storage, or public IP addresses. The example used in this " +"chapter is of a typical virtual system within an OpenStack cloud. It uses " +"the cinder-volume service, which " +"provides persistent block storage, instead of the ephemeral storage provided" +" by the selected instance flavor." +msgstr "" + +#: ./doc/admin-guide-cloud/ch_compute.xml201(para) +msgid "" +"This diagram shows the system state prior to launching an instance. The " +"image store, fronted by the image service, Glance, has a number of " +"predefined images. Inside the cloud, a compute node contains the available " +"vCPU, memory, and local disk resources. Additionally, the cinder-volume service provides a number of " +"predefined volumes." +msgstr "" + +#: ./doc/admin-guide-cloud/ch_compute.xml209(title) +msgid "Base image state with no running instances" +msgstr "" + +#: ./doc/admin-guide-cloud/ch_compute.xml218(para) +msgid "" +"To launch an instance, select an image, a flavor, and other optional " +"attributes. The selected flavor provides a root volume, labeled " +"vda in this diagram, and additional ephemeral storage, " +"labeled vdb. In this example, the cinder-volume store is mapped to the third " +"virtual disk on this instance, vdc." +msgstr "" + +#: ./doc/admin-guide-cloud/ch_compute.xml227(title) +msgid "Instance creation from image and runtime state" +msgstr "" + +#: ./doc/admin-guide-cloud/ch_compute.xml237(para) +msgid "" +"The base image is copied from the image store to the local disk. The local " +"disk is the first disk that the instance accesses, and is labeled " +"vda. By using smaller images, your instances start up " +"faster as less data needs to be copied across the network." +msgstr "" + +#: ./doc/admin-guide-cloud/ch_compute.xml242(para) +msgid "" +"A new empty disk, labeled vdb is also created. This is an" +" empty ephemeral disk, which is destroyed when you delete the instance." +msgstr "" + +#: ./doc/admin-guide-cloud/ch_compute.xml245(para) +msgid "" +"The compute node is attached to the cinder-" +"volume using iSCSI, and maps to the third disk, " +"vdc. The vCPU and memory resources are provisioned and " +"the instance is booted from vda. The instance runs and " +"changes data on the disks as indicated in red in the diagram." +msgstr "" + +#: ./doc/admin-guide-cloud/ch_compute.xml255(para) +msgid "" +"Some of the details in this example scenario might be different in your " +"environment. Specifically, you might use a different type of back-end " +"storage or different network protocols. One common variant is that the " +"ephemeral storage used for volumes vda and " +"vdb could be backed by network storage rather than a " +"local disk." +msgstr "" + +#: ./doc/admin-guide-cloud/ch_compute.xml264(para) +msgid "" +"When the instance is deleted, the state is reclaimed with the exception of " +"the persistent volume. The ephemeral storage is purged, memory and vCPU " +"resources are released. The image remains unchanged throughout." +msgstr "" + +#: ./doc/admin-guide-cloud/ch_compute.xml269(title) +msgid "End state of image and volume after instance exits" +msgstr "" + +#: ./doc/admin-guide-cloud/ch_compute.xml281(title) +msgid "System architecture" +msgstr "" + +#: ./doc/admin-guide-cloud/ch_compute.xml282(para) +msgid "" +"OpenStack Compute contains several main components. The cloud " +"controller represents the global state and interacts with the " +"other components. The API server acts as the web services" +" front end for the cloud controller. The compute " +"controller provides compute server resources and usually also " +"contains the Compute service." +msgstr "" + +#: ./doc/admin-guide-cloud/ch_compute.xml289(para) +msgid "" +"The object store is an optional component that provides " +"storage services. An auth manager provides authentication" +" and authorization services when used with the Compute system, or you can " +"use the identity service as a separate authentication " +"service instead. A volume controller provides fast and " +"permanent block-level storage for the compute servers. The network " +"controller provides virtual networks to enable compute servers to " +"interact with each other and with the public network. The " +"scheduler is used to select the most suitable compute " +"controller to host an instance." +msgstr "" + +#: ./doc/admin-guide-cloud/ch_compute.xml303(para) +msgid "" +"Compute uses a messaging-based, shared nothing " +"architecture. All major components exist on multiple servers, including the " +"compute, volume, and network controllers, and the object store or image " +"service. The state of the entire system is stored in a database. The cloud " +"controller communicates with the internal object store using HTTP, but it " +"communicates with the scheduler, network controller, and volume controller " +"using AMQP (advanced message queueing protocol). To avoid blocking a " +"component while waiting for a response, Compute uses asynchronous calls, " +"with a callback that is triggered when a response is received." +msgstr "" + +#: ./doc/admin-guide-cloud/ch_compute.xml317(title) +msgid "Block storage" +msgstr "" + +#: ./doc/admin-guide-cloud/ch_compute.xml318(para) +msgid "" +"OpenStack provides two classes of block storage: ephemeral storage and " +"persistent volumes. Volumes are persistent virtualized block devices " +"independent of any particular instance." +msgstr "" + +#: ./doc/admin-guide-cloud/ch_compute.xml322(para) +msgid "" +"Ephemeral storage is associated with a single unique instance, and it exists" +" only for the life of that instance. The amount of ephemeral storage is " +"defined by the flavor of the instance. Generally, the root file system for " +"an instance will be stored on ephemeral storage. It persists across reboots " +"of the guest operating system, but when the instance is deleted, the " +"ephemeral storage is also removed." +msgstr "" + +#: ./doc/admin-guide-cloud/ch_compute.xml330(para) +msgid "" +"In addition to the ephemeral root volume, all flavors except the smallest, " +"m1.tiny, also provide an additional ephemeral block " +"device of between 20 and 160GB. These sizes can be configured to suit your " +"environment. This is presented as a raw block device with no partition table" +" or file system. Cloud-aware operating system images can discover, format, " +"and mount these storage devices. For example, the cloud-init package included in Ubuntu's stock" +" cloud images format this space as an ext3 file system " +"and mount it on /mnt. This is a feature of the guest " +"operating system you are using, and is not an OpenStack mechanism. OpenStack" +" only provisions the raw storage." +msgstr "" + +#: ./doc/admin-guide-cloud/ch_compute.xml345(para) +msgid "" +"Persistent volumes are created by users and their size is limited only by " +"the user's quota and availability limits. Upon initial creation, volumes are" +" raw block devices without a partition table or a file system. To partition " +"or format volumes, you must attach them to an instance. Once they are " +"attached to an instance, you can use persistent volumes in much the same way" +" as you would use external hard disk drive. You can attach volumes to only " +"one instance at a time, although you can detach and reattach volumes to as " +"many different instances as you like." +msgstr "" + +#: ./doc/admin-guide-cloud/ch_compute.xml356(para) +msgid "" +"Persistent volumes can be configured as bootable and used to provide a " +"persistent virtual instance similar to traditional non-cloud-based " +"virtualization systems. Typically, the resulting instance can also still " +"have ephemeral storage depending on the flavor selected, but the root file " +"system can be on the persistent volume and its state maintained even if the " +"instance is shut down. For more information about this type of " +"configuration, see the OpenStack Configuration " +"Reference." +msgstr "" + +#: ./doc/admin-guide-cloud/ch_compute.xml367(para) +msgid "" +"Persistent volumes do not provide concurrent access from multiple instances." +" That type of configuration requires a traditional network file system like " +"NFS or CIFS, or a cluster file system such as GlusterFS. These systems can " +"be built within an OpenStack cluster or provisioned outside of it, but " +"OpenStack software does not provide these features." +msgstr "" + +#: ./doc/admin-guide-cloud/ch_compute.xml377(title) +msgid "Image management" +msgstr "" + +#: ./doc/admin-guide-cloud/ch_compute.xml378(para) +msgid "" +"The OpenStack Image service discovers, registers, and retrieves virtual " +"machine images. The service also includes a RESTful API that allows you to " +"query VM image metadata and retrieve the actual image with HTTP requests. " +"For more information about the API, see the OpenStack " +"API or the Python API." +msgstr "" + +#: ./doc/admin-guide-cloud/ch_compute.xml387(para) +msgid "" +"The OpenStack Image service can be controlled using a command line tool. For" +" more information about the OpenStack Image command line tool, see the Image Management section in " +"the OpenStack User Guide." +msgstr "" + +#: ./doc/admin-guide-cloud/ch_compute.xml393(para) +msgid "" +"Virtual images that have been made available through the Image service can " +"be stored in a variety of ways. In order to use these services, you must " +"have a working installation of the Image service, with a working endpoint, " +"and users that have been created in the Identity service. Additionally, you " +"must meet the environment variables required by the Compute and Image " +"clients." +msgstr "" + +#: ./doc/admin-guide-cloud/ch_compute.xml401(para) +msgid "The Image service supports these back end stores:" +msgstr "" + +#: ./doc/admin-guide-cloud/ch_compute.xml404(term) +msgid "File system" +msgstr "" + +#: ./doc/admin-guide-cloud/ch_compute.xml406(para) +msgid "" +"The OpenStack Image service stores virtual machine images in the file system" +" back-end by default. This simple back end writes image files to the local " +"file system." +msgstr "" + +#: ./doc/admin-guide-cloud/ch_compute.xml413(term) +msgid "Object Storage service" +msgstr "" + +#: ./doc/admin-guide-cloud/ch_compute.xml415(para) +msgid "The OpenStack highly-available object storage service." +msgstr "" + +#: ./doc/admin-guide-cloud/ch_compute.xml420(term) +msgid "S3" +msgstr "" + +#: ./doc/admin-guide-cloud/ch_compute.xml422(para) +msgid "The Amazon S3 service." +msgstr "" + +#: ./doc/admin-guide-cloud/ch_compute.xml426(term) +msgid "HTTP" +msgstr "" + +#: ./doc/admin-guide-cloud/ch_compute.xml428(para) +msgid "" +"OpenStack Image Service can read virtual machine images that are available " +"on the internet using HTTP. This store is read only." +msgstr "" + +#: ./doc/admin-guide-cloud/ch_compute.xml435(term) +msgid "Rados block device (RBD)" +msgstr "" + +#: ./doc/admin-guide-cloud/ch_compute.xml437(para) +msgid "" +"Stores images inside of a Ceph storage cluster using Ceph's RBD interface." +msgstr "" + +#: ./doc/admin-guide-cloud/ch_compute.xml442(term) +msgid "GridFS" +msgstr "" + +#: ./doc/admin-guide-cloud/ch_compute.xml444(para) +msgid "Stores images using MongoDB." +msgstr "" + +#: ./doc/admin-guide-cloud/ch_compute.xml450(title) +msgid "Instance management tools" +msgstr "" + +#: ./doc/admin-guide-cloud/ch_compute.xml451(para) +msgid "" +"OpenStack provides command line, web-based, and API-based instance " +"management tools. Additionally, a number of third party management tools are" +" available, using either the native API or the provided EC2-compatible API." +msgstr "" + +#: ./doc/admin-guide-cloud/ch_compute.xml456(para) +msgid "" +"The OpenStack python-novaclient package provides " +"a basic command line utility, which uses the command. This " +"is available as a native package for most Linux distributions, or you can " +"install the latest version using the pip python " +"package installer: " +msgstr "" + +#: ./doc/admin-guide-cloud/ch_compute.xml466(para) +msgid "" +"For more information about python-novaclient and " +"other available command line tools, see the OpenStack End User " +"Guide." +msgstr "" + +#: ./doc/admin-guide-cloud/ch_compute.xml574(title) +msgid "EC2 compatibility API" +msgstr "" + +#: ./doc/admin-guide-cloud/ch_compute.xml575(para) +msgid "" +"In addition to the native compute API, OpenStack provides an EC2-compatible " +"API. This API allows EC2 legacy workflows built for EC2 to work with " +"OpenStack." +msgstr "" + +#: ./doc/admin-guide-cloud/ch_compute.xml578(para) +msgid "" +"The OpenStack Configuration Reference lists " +"configuration options for customizing this compatibility API on your " +"OpenStack cloud." +msgstr "" + +#: ./doc/admin-guide-cloud/ch_compute.xml582(para) +msgid "" +"Numerous third party tools and language-specific SDKs can be used to " +"interact with OpenStack clouds, using both native and compatibility APIs. " +"Some of the more popular third-party tools are:" +msgstr "" + +#: ./doc/admin-guide-cloud/ch_compute.xml588(term) +msgid "Euca2ools" +msgstr "" + +#: ./doc/admin-guide-cloud/ch_compute.xml590(para) +msgid "" +"A popular open source command line tool for interacting with the EC2 API. " +"This is convenient for multi-cloud environments where EC2 is the common API," +" or for transitioning from EC2-based clouds to OpenStack. For more " +"information, see the euca2ools " +"site." +msgstr "" + +#: ./doc/admin-guide-cloud/ch_compute.xml601(term) +msgid "Hybridfox" +msgstr "" + +#: ./doc/admin-guide-cloud/ch_compute.xml603(para) +msgid "" +"A Firefox browser add-on that provides a graphical interface to many popular" +" public and private cloud technologies, including OpenStack. For more " +"information, see the " +"hybridfox site." +msgstr "" + +#: ./doc/admin-guide-cloud/ch_compute.xml612(term) +msgid "boto" +msgstr "" + +#: ./doc/admin-guide-cloud/ch_compute.xml614(para) +msgid "" +"A Python library for interacting with Amazon Web Services. It can be used to" +" access OpenStack through the EC2 compatibility API. For more information, " +"see the boto project page on " +"GitHub." +msgstr "" + +#: ./doc/admin-guide-cloud/ch_compute.xml623(term) +msgid "fog" +msgstr "" + +#: ./doc/admin-guide-cloud/ch_compute.xml625(para) +msgid "" +"A Ruby cloud services library. It provides methods for interacting with a " +"large number of cloud and virtualization platforms, including OpenStack. For" +" more information, see the fog" +" site." +msgstr "" + +#: ./doc/admin-guide-cloud/ch_compute.xml634(term) +msgid "php-opencloud" +msgstr "" + +#: ./doc/admin-guide-cloud/ch_compute.xml636(para) +msgid "" +"A PHP SDK designed to work with most OpenStack- based cloud deployments, as " +"well as Rackspace public cloud. For more information, see the php-opencloud site." +msgstr "" + +#: ./doc/admin-guide-cloud/ch_compute.xml647(title) +msgid "Building blocks" +msgstr "" + +#. There are two fundamental requirements for a +#. computing system, software and hardware. +#. Virtualization and cloud frameworks tend to blur these +#. lines and some of your "hardware" might actually be +#. "software" but conceptually you still need an +#. operating system and something to run it on. +#: ./doc/admin-guide-cloud/ch_compute.xml654(para) +msgid "" +"In OpenStack the base operating system is usually copied from an image " +"stored in the OpenStack Image service. This is the most common case and " +"results in an ephemeral instance that starts from a known template state and" +" loses all accumulated states on shutdown. It is also possible to put an " +"operating system on a persistent volume in the Nova-Volume or Cinder volume " +"system. This gives a more traditional persistent system that accumulates " +"states, which are preserved across restarts. To get a list of available " +"images on your system run: " +msgstr "" + +#: ./doc/admin-guide-cloud/ch_compute.xml673(para) +msgid "The displayed image attributes are:" +msgstr "" + +#: ./doc/admin-guide-cloud/ch_compute.xml676(literal) +msgid "ID" +msgstr "" + +#: ./doc/admin-guide-cloud/ch_compute.xml678(para) +msgid "Automatically generated UUID of the image" +msgstr "" + +#: ./doc/admin-guide-cloud/ch_compute.xml683(literal) +msgid "Name" +msgstr "" + +#: ./doc/admin-guide-cloud/ch_compute.xml685(para) +msgid "Free form, human-readable name for image" +msgstr "" + +#: ./doc/admin-guide-cloud/ch_compute.xml690(literal) +msgid "Status" +msgstr "" + +#: ./doc/admin-guide-cloud/ch_compute.xml692(para) +msgid "" +"The status of the image. Images marked ACTIVE are " +"available for use." +msgstr "" + +#: ./doc/admin-guide-cloud/ch_compute.xml698(literal) +msgid "Server" +msgstr "" + +#: ./doc/admin-guide-cloud/ch_compute.xml700(para) +msgid "" +"For images that are created as snapshots of running instances, this is the " +"UUID of the instance the snapshot derives from. For uploaded images, this " +"field is blank." +msgstr "" + +#: ./doc/admin-guide-cloud/ch_compute.xml708(para) +msgid "" +"Virtual hardware templates are called flavors. The " +"default installation provides five flavors. By default, these are " +"configurable by admin users, however that behavior can be changed by " +"redefining the access controls for " +"compute_extension:flavormanage in " +"/etc/nova/policy.json on the compute-" +"api server." +msgstr "" + +#: ./doc/admin-guide-cloud/ch_compute.xml716(para) +msgid "For a list of flavors that are available on your system:" +msgstr "" + +#: ./doc/admin-guide-cloud/ch_compute.xml742(title) +msgid "Control where instances run" +msgstr "" + +#: ./doc/admin-guide-cloud/ch_compute.xml743(para) +msgid "" +"The OpenStack Configuration Reference provides " +"detailed information on controlling where your instances run, including " +"ensuring a set of instances run on different compute nodes for service " +"resiliency or on the same node for high performance inter-instance " +"communications." +msgstr "" + +#: ./doc/admin-guide-cloud/ch_compute.xml752(replaceable) +msgid "availability-zone" +msgstr "" + +#: ./doc/admin-guide-cloud/ch_compute.xml752(replaceable) +msgid "compute-host" +msgstr "" + +#: ./doc/admin-guide-cloud/ch_compute.xml750(para) +msgid "" +"Admin users can specify an exact compute node to run on using the command " +"" +msgstr "" + +#: ./doc/admin-guide-cloud/ch_compute.xml757(title) +msgid "Admin password injection" +msgstr "" + +#: ./doc/admin-guide-cloud/ch_compute.xml758(para) +msgid "" +"You can configure Compute to generate a random administrator (root) password" +" and inject that password into the instance. If this feature is enabled, a " +"user can ssh to an instance without an ssh keypair. The random password " +"appears in the output of the command. You can also view and" +" set the admin password from the dashboard." +msgstr "" + +#: ./doc/admin-guide-cloud/ch_compute.xml767(para) +msgid "" +"The dashboard is configured by default to display the admin password and " +"allow the user to modify it." +msgstr "" + +#: ./doc/admin-guide-cloud/ch_compute.xml770(para) +msgid "" +"If you do not want to support password injection, we recommend disabling the" +" password fields by editing your Dashboard " +"local_settings file (file location will vary by Linux " +"distribution, on Fedora/RHEL/CentOS: /etc/openstack-" +"dashboard/local_settings, on Ubuntu and Debian: /etc" +"/openstack-dashboard/local_settings.py and on openSUSE and SUSE " +"Linux Enterprise Server: /usr/share/openstack-" +"dashboard/openstack_dashboard/local/local_settings.py) " +"" +msgstr "" + +#: ./doc/admin-guide-cloud/ch_compute.xml786(title) +msgid "Libvirt-based hypervisors (KVM, QEMU, LXC)" +msgstr "" + +#: ./doc/admin-guide-cloud/ch_compute.xml787(para) +msgid "" +"For hypervisors such as KVM that use the libvirt backend, admin password " +"injection is disabled by default. To enable it, set the following option in " +"/etc/nova/nova.conf:" +msgstr "" + +#: ./doc/admin-guide-cloud/ch_compute.xml795(para) +msgid "" +"When enabled, Compute will modify the password of the root account by " +"editing the /etc/shadow file inside of the virtual " +"machine instance." +msgstr "" + +#: ./doc/admin-guide-cloud/ch_compute.xml803(para) +msgid "The virtual machine image is a Linux distribution" +msgstr "" + +#: ./doc/admin-guide-cloud/ch_compute.xml807(para) +msgid "" +"The virtual machine has been configured to allow users to ssh as the root " +"user. This is not the case for Ubuntu cloud images, which disallow ssh to the " +"root account by default." +msgstr "" + +#: ./doc/admin-guide-cloud/ch_compute.xml800(para) +msgid "" +"Users will only be able to ssh to the instance using the admin password " +"if:" +msgstr "" + +#: ./doc/admin-guide-cloud/ch_compute.xml820(title) +msgid "XenAPI (XenServer/XCP)" +msgstr "" + +#: ./doc/admin-guide-cloud/ch_compute.xml821(para) +msgid "" +"Compute uses the XenAPI agent to inject passwords into guests when using the" +" XenAPI hypervisor backend. The virtual machine image must be configured " +"with the agent for password injection to work." +msgstr "" + +#: ./doc/admin-guide-cloud/ch_compute.xml827(title) +msgid "Windows images (all hypervisors)" +msgstr "" + +#: ./doc/admin-guide-cloud/ch_compute.xml828(para) +msgid "" +"To support the admin password for Windows virtual machines, you must " +"configure the Windows image to retrieve the admin password on boot by " +"installing an agent such as cloudbase-init." +msgstr "" + +#: ./doc/admin-guide-cloud/ch_compute.xml856(title) +msgid "Networking with nova-network" +msgstr "" + +#: ./doc/admin-guide-cloud/ch_compute.xml857(para) +msgid "" +"Understanding the networking configuration options helps you design the best" +" configuration for your Compute instances." +msgstr "" + +#: ./doc/admin-guide-cloud/ch_compute.xml861(title) +msgid "Networking options" +msgstr "" + +#: ./doc/admin-guide-cloud/ch_compute.xml862(para) +msgid "" +"This section offers a brief overview of each concept in networking for " +"Compute. With the Grizzly release, you can choose to either install and " +"configure nova-network for " +"networking between VMs or use the Networking service (neutron) for " +"networking. To configure Compute networking options with Neutron, see the " +"." +msgstr "" + +#: ./doc/admin-guide-cloud/ch_compute.xml871(para) +msgid "" +"For each VM instance, Compute assigns to it a private IP address. " +"(Currently, Compute with nova-" +"network only supports Linux bridge networking that enables the " +"virtual interfaces to connect to the outside network through the physical " +"interface.)" +msgstr "" + +#: ./doc/admin-guide-cloud/ch_compute.xml878(para) +msgid "" +"The network controller with nova-" +"network provides virtual networks to enable compute servers to " +"interact with each other and with the public network." +msgstr "" + +#: ./doc/admin-guide-cloud/ch_compute.xml887(para) +msgid "Flat Network Manager" +msgstr "" + +#: ./doc/admin-guide-cloud/ch_compute.xml890(para) +msgid "Flat DHCP Network Manager" +msgstr "" + +#: ./doc/admin-guide-cloud/ch_compute.xml893(para) +msgid "VLAN Network Manager" +msgstr "" + +#: ./doc/admin-guide-cloud/ch_compute.xml882(para) +msgid "" +"Currently, Compute with nova-" +"network supports these kinds of networks, implemented in " +"different “Network Manager” types: " +msgstr "" + +#: ./doc/admin-guide-cloud/ch_compute.xml896(para) +msgid "" +"These networks can co-exist in a cloud system. However, because you can't " +"yet select the type of network for a given project, you cannot configure " +"more than one type of network in a given Compute installation." +msgstr "" + +#: ./doc/admin-guide-cloud/ch_compute.xml902(para) +msgid "" +"All networking options require network connectivity to be already set up " +"between OpenStack physical nodes. OpenStack does not configure any physical " +"network interfaces. OpenStack automatically creates all network bridges (for" +" example, br100) and VM virtual interfaces." +msgstr "" + +#: ./doc/admin-guide-cloud/ch_compute.xml909(para) +msgid "" +"All machines must have a public and " +"internal network interface (controlled " +"by the options: public_interface for the public " +"interface, and flat_interface and " +"vlan_interface for the internal interface with flat / " +"VLAN managers)." +msgstr "" + +#: ./doc/admin-guide-cloud/ch_compute.xml919(para) +msgid "" +"The internal network interface is used for communication with VMs, it " +"shouldn't have an IP address attached to it before OpenStack installation " +"(it serves merely as a fabric where the actual endpoints are VMs and " +"dnsmasq). Also, the internal network interface must be put in promiscuous mode, because it must receive packets" +" whose target MAC address is of the guest VM, not of the host." +msgstr "" + +#: ./doc/admin-guide-cloud/ch_compute.xml930(para) +msgid "" +"All the network managers configure the network using network drivers. For example, the Linux L3 driver" +" (l3.py and linux_net.py), which makes" +" use of iptables, route and other " +"network management facilities, and libvirt's network filtering " +"facilities. The driver isn't tied to any particular network manager; " +"all network managers use the same driver. The driver usually initializes " +"(creates bridges and so on) only when the first VM lands on this host node." +msgstr "" + +#: ./doc/admin-guide-cloud/ch_compute.xml944(para) +msgid "" +"All network managers operate in either single-" +"host or multi-host mode. " +"This choice greatly influences the network configuration. In single-host " +"mode, a single nova-network " +"service provides a default gateway for VMs and hosts a single DHCP server " +"(dnsmasq). In multi-host mode, each compute node runs its own nova-network service. In both cases, all " +"traffic between VMs and the outer world flows through nova-network. Each mode has its pros and " +"cons. Read more in the OpenStack Configuration " +"Reference." +msgstr "" + +#: ./doc/admin-guide-cloud/ch_compute.xml961(para) +msgid "" +"Compute makes a distinction between fixed " +"IPs and floating IPs for VM " +"instances. Fixed IPs are IP addresses that are assigned to an instance on " +"creation and stay the same until the instance is explicitly terminated. By " +"contrast, floating IPs are addresses that can be dynamically associated with" +" an instance. A floating IP address can be disassociated and associated with" +" another instance at any time. A user can reserve a floating IP for their " +"project." +msgstr "" + +#: ./doc/admin-guide-cloud/ch_compute.xml972(para) +msgid "" +"In Flat Mode, a network administrator " +"specifies a subnet. The IP addresses for VM instances are grabbed from the " +"subnet, and then injected into the image on launch. Each instance receives a" +" fixed IP address from the pool of available addresses. A system " +"administrator may create the Linux networking bridge (typically named " +"br100, although this configurable) on the systems running" +" the nova-network service. All " +"instances of the system are attached to the same bridge, configured manually" +" by the network administrator." +msgstr "" + +#: ./doc/admin-guide-cloud/ch_compute.xml986(para) +msgid "" +"The configuration injection currently only works on Linux-style systems that" +" keep networking configuration in " +"/etc/network/interfaces." +msgstr "" + +#: ./doc/admin-guide-cloud/ch_compute.xml991(para) +msgid "" +"In Flat DHCP Mode, OpenStack starts a " +"DHCP server (dnsmasq) to pass out IP addresses to VM instances from the " +"specified subnet in addition to manually configuring the networking bridge. " +"IP addresses for VM instances are grabbed from a subnet specified by the " +"network administrator." +msgstr "" + +#: ./doc/admin-guide-cloud/ch_compute.xml997(para) +msgid "" +"Like Flat Mode, all instances are attached to a single bridge on the compute" +" node. In addition a DHCP server is running to configure instances " +"(depending on single-/multi-host mode, alongside each nova-network). In this mode, Compute does a " +"bit more configuration in that it attempts to bridge into an ethernet device" +" (flat_interface, eth0 by default). For every instance, " +"nova allocates a fixed IP address and configure dnsmasq with the MAC/IP pair" +" for the VM. Dnsmasq doesn't take part in the IP address allocation process," +" it only hands out IPs according to the mapping done by nova. Instances " +"receive their fixed IPs by doing a dhcpdiscover. These IPs are not assigned to any of the host's network " +"interfaces, only to the VM's guest-side interface." +msgstr "" + +#: ./doc/admin-guide-cloud/ch_compute.xml1014(para) +msgid "" +"In any setup with flat networking, the hosts providing the nova-network service are responsible for " +"forwarding traffic from the private network. They also run and configure " +"dnsmasq as a DHCP server listening on this bridge, usually on IP address " +"10.0.0.1 (see DHCP server: dnsmasq " +"). Compute can determine the NAT entries for each network, though " +"sometimes NAT is not used, such as when configured with all public IPs or a " +"hardware router is used (one of the HA options). Such hosts need to have " +"br100 configured and physically connected to any other " +"nodes that are hosting VMs. You must set the " +"flat_network_bridge option or create networks with the " +"bridge parameter in order to avoid raising an error. Compute nodes have " +"iptables/ebtables entries created for each project and instance to protect " +"against IP/MAC address spoofing and ARP poisoning." +msgstr "" + +#: ./doc/admin-guide-cloud/ch_compute.xml1034(para) +msgid "" +"In single-host Flat DHCP mode you will " +"be able to ping VMs through their fixed IP from the nova-network node, but " +"you cannot ping them from the compute " +"nodes. This is expected behavior." +msgstr "" + +#: ./doc/admin-guide-cloud/ch_compute.xml1041(para) +msgid "" +"VLAN Network Mode is the default mode for" +" OpenStack Compute. In this mode, Compute creates a VLAN and bridge for each" +" project. For multiple machine installation, the VLAN Network Mode requires " +"a switch that supports VLAN tagging (IEEE 802.1Q). The project gets a range " +"of private IPs that are only accessible from inside the VLAN. In order for a" +" user to access the instances in their project, a special VPN instance (code" +" named cloudpipe) needs to be created. Compute generates a certificate and " +"key for the user to access the VPN and starts the VPN automatically. It " +"provides a private network segment for each project's instances that can be " +"accessed through a dedicated VPN connection from the Internet. In this mode," +" each project gets its own VLAN, Linux networking bridge, and subnet." +msgstr "" + +#: ./doc/admin-guide-cloud/ch_compute.xml1058(para) +msgid "" +"The subnets are specified by the network administrator, and are assigned " +"dynamically to a project when required. A DHCP Server is started for each " +"VLAN to pass out IP addresses to VM instances from the subnet assigned to " +"the project. All instances belonging to one project are bridged into the " +"same VLAN for that project. OpenStack Compute creates the Linux networking " +"bridges and VLANs when required." +msgstr "" + +#: ./doc/admin-guide-cloud/ch_compute.xml1069(title) +msgid "DHCP server: dnsmasq" +msgstr "" + +#: ./doc/admin-guide-cloud/ch_compute.xml1070(para) +msgid "" +"The Compute service uses dnsmasq as the" +" DHCP server when running with either that Flat DHCP Network Manager or the " +"VLAN Network Manager. The nova-" +"network service is responsible for starting up dnsmasq " +"processes." +msgstr "" + +#: ./doc/admin-guide-cloud/ch_compute.xml1077(para) +msgid "" +"The behavior of dnsmasq can be customized by creating a dnsmasq " +"configuration file. Specify the config file using the " +"dnsmasq_config_file configuration option. For example: " +" See the OpenStack Configuration " +"Reference for an example of how to change the behavior of" +" dnsmasq using a dnsmasq configuration file. The dnsmasq documentation has a" +" more comprehensive dnsmasq" +" configuration file example." +msgstr "" + +#: ./doc/admin-guide-cloud/ch_compute.xml1092(para) +msgid "" +"Dnsmasq also acts as a caching DNS server for instances. You can explicitly " +"specify the DNS server that dnsmasq should use by setting the " +"dns_server configuration option in " +"/etc/nova/nova.conf. The following example would " +"configure dnsmasq to use Google's public DNS server: " +msgstr "" + +#: ./doc/admin-guide-cloud/ch_compute.xml1100(para) +msgid "" +"Dnsmasq logging output goes to the syslog (typically " +"/var/log/syslog or " +"/var/log/messages, depending on Linux distribution). " +"The dnsmasq logging output can be useful for troubleshooting if VM instances" +" boot successfully but are not reachable over the network." +msgstr "" + +#: ./doc/admin-guide-cloud/ch_compute.xml1107(para) +msgid "" +"A network administrator can run nova-manage fixed reserve " +"--address=x.x.x.x to specify the starting " +"point IP address (x.x.x.x) to reserve with the DHCP server. This reservation" +" only affects which IP address the VMs start at, not the fixed IP addresses " +"that the nova-network service " +"places on the bridges." +msgstr "" + +#: ./doc/admin-guide-cloud/ch_compute.xml1118(title) +msgid "Metadata service" +msgstr "" + +#: ./doc/admin-guide-cloud/ch_compute.xml1120(title) +msgid "Introduction" +msgstr "" + +#: ./doc/admin-guide-cloud/ch_compute.xml1121(para) +msgid "" +"The Compute service uses a special metadata service to enable virtual " +"machine instances to retrieve instance-specific data. Instances access the " +"metadata service at http://169.254.169.254. The metadata " +"service supports two sets of APIs: an OpenStack metadata API and an " +"EC2-compatible API. Each of the APIs is versioned by date." +msgstr "" + +#: ./doc/admin-guide-cloud/ch_compute.xml1129(para) +msgid "" +"To retrieve a list of supported versions for the OpenStack metadata API, " +"make a GET request to For example:" +msgstr "" + +#: ./doc/admin-guide-cloud/ch_compute.xml1133(para) +msgid "" +" To retrieve a list of supported versions for the " +"EC2-compatible metadata API, make a GET request to " +msgstr "" + +#: ./doc/admin-guide-cloud/ch_compute.xml1139(para) +#: ./doc/admin-guide-cloud/ch_compute.xml1163(para) +#: ./doc/admin-guide-cloud/ch_compute.xml1207(para) +#: ./doc/admin-guide-cloud/ch_compute.xml1235(para) +#: ./doc/admin-guide-cloud/ch_compute.xml1241(para) +#: ./doc/admin-guide-cloud/ch_compute.xml1450(para) +#: ./doc/admin-guide-cloud/section_networking-config-identity.xml47(para) +#: ./doc/admin-guide-cloud/section_networking-config-identity.xml61(para) +#: ./doc/admin-guide-cloud/section_networking-use.xml463(para) +msgid "For example:" +msgstr "" + +#: ./doc/admin-guide-cloud/ch_compute.xml1151(para) +msgid "" +"If you write a consumer for one of these APIs, always attempt to access the " +"most recent API version supported by your consumer first, then fall back to " +"an earlier version if the most recent one is not available." +msgstr "" + +#: ./doc/admin-guide-cloud/ch_compute.xml1158(title) +msgid "OpenStack metadata API" +msgstr "" + +#: ./doc/admin-guide-cloud/ch_compute.xml1159(para) +msgid "" +"Metadata from the OpenStack API is distributed in JSON format. To retrieve " +"the metadata, make a GET request to:" +msgstr "" + +#: ./doc/admin-guide-cloud/ch_compute.xml1166(para) +msgid "" +"Here is the same content after having run through a JSON pretty-printer:" +msgstr "" + +#: ./doc/admin-guide-cloud/ch_compute.xml1182(para) +msgid "" +"Instances also retrieve user data (passed as the " +"user_data parameter in the API call or by the " +"--user_data flag in the command) through" +" the metadata service, by making a GET request to: For " +"example:" +msgstr "" + +#: ./doc/admin-guide-cloud/ch_compute.xml1196(title) +msgid "EC2 metadata API" +msgstr "" + +#: ./doc/admin-guide-cloud/ch_compute.xml1197(para) +msgid "" +"The metadata service has an API that is compatible with version 2009-04-04 " +"of the Amazon EC2 metadata service; virtual " +"machine images that are designed for EC2 work properly with OpenStack." +msgstr "" + +#: ./doc/admin-guide-cloud/ch_compute.xml1203(para) +msgid "" +"The EC2 API exposes a separate URL for each metadata. You can retrieve a " +"listing of these elements by making a GET query to:" +msgstr "" + +#: ./doc/admin-guide-cloud/ch_compute.xml1231(para) +msgid "" +"Instances can retrieve the public SSH key (identified by keypair name when a" +" user requests a new instance) by making a GET request to:" +msgstr "" + +#: ./doc/admin-guide-cloud/ch_compute.xml1238(para) +msgid "Instances can retrieve user data by making a GET request to:" +msgstr "" + +#: ./doc/admin-guide-cloud/ch_compute.xml1247(title) +msgid "Run the metadata service" +msgstr "" + +#: ./doc/admin-guide-cloud/ch_compute.xml1248(para) +msgid "" +"The metadata service is implemented by either the nova-api service or the nova-api-metadata service. (The nova-api-metadata service is generally only " +"used when running in multi-host mode, see the OpenStack Configuration " +"Reference for details). If you are running the " +"nova-api service, you must have " +"metadata as one of the elements of the list of the " +"enabled_apis configuration option in " +"/etc/nova/nova.conf. The default " +"enabled_apis configuration setting includes the metadata " +"service, so you should not need to modify it." +msgstr "" + +#: ./doc/admin-guide-cloud/ch_compute.xml1271(para) +msgid "" +"To enable instances to reach the metadata service, the nova-network service configures iptables to " +"NAT port 80 of the 169.254.169.254 " +"address to the IP address specified in " +"(default $my_ip, which is the IP address of the " +"nova-network service) and port " +"specified in (default " +"8775) in /etc/nova/nova.conf." +msgstr "" + +#: ./doc/admin-guide-cloud/ch_compute.xml1285(para) +msgid "" +"The metadata_host configuration option must be an IP " +"address, not a host name." +msgstr "" + +#: ./doc/admin-guide-cloud/ch_compute.xml1290(para) +msgid "" +"The default Compute service settings assume that the nova-network service and the nova-api service are running on the same " +"host. If this is not the case, you must make this change in the " +"/etc/nova/nova.conf file on the host running the " +"nova-network service:" +msgstr "" + +#: ./doc/admin-guide-cloud/ch_compute.xml1301(para) +msgid "" +"Set the metadata_host configuration option to the IP " +"address of the host where the nova-" +"api service runs." +msgstr "" + +#: ./doc/admin-guide-cloud/ch_compute.xml1312(title) +msgid "Enable ping and SSH on VMs" +msgstr "" + +#: ./doc/admin-guide-cloud/ch_compute.xml1313(para) +msgid "" +"Be sure you enable access to your VMs by using the or " +" command. These commands enable you to and " +" to your VMs:" +msgstr "" + +#: ./doc/admin-guide-cloud/ch_compute.xml1319(para) +msgid "" +"You must run these commands as root only if the credentials used to interact" +" with nova-api are in " +"/root/.bashrc. If the EC2 credentials are the " +".bashrc file for another user, you must run these " +"commands as the user." +msgstr "" + +#: ./doc/admin-guide-cloud/ch_compute.xml1327(para) +msgid "Run commands:" +msgstr "" + +#: ./doc/admin-guide-cloud/ch_compute.xml1330(para) +msgid "Using euca2ools:" +msgstr "" + +#: ./doc/admin-guide-cloud/ch_compute.xml1333(para) +msgid "" +"If you still cannot ping or SSH your instances after issuing the " +" commands, look at the number of dnsmasq " +"processes that are running. If you have a running instance, check to see " +"that TWO dnsmasq processes are running. If not, perform " +"this as root:" +msgstr "" + +#: ./doc/admin-guide-cloud/ch_compute.xml1344(title) +msgid "Configure public (floating) IP addresses" +msgstr "" + +#: ./doc/admin-guide-cloud/ch_compute.xml1347(para) +msgid "" +"This section describes how to configure floating IP addresses if you opt to " +"use nova-network instead of " +"neutron for OpenStack Networking. For instructions on how to configure " +"neutron to provide access to instances through floating IP addresses, see " +"." +msgstr "" + +#: ./doc/admin-guide-cloud/ch_compute.xml1357(title) +msgid "Private and public IP addresses" +msgstr "" + +#: ./doc/admin-guide-cloud/ch_compute.xml1358(para) +msgid "" +"Every virtual instance is automatically assigned a private IP address. You " +"can optionally assign public IP addresses to instances. The term floating IP refers to an IP " +"address, typically public, that you can dynamically add to a running virtual" +" instance. OpenStack Compute uses Network Address Translation (NAT) to " +"assign floating IPs to virtual instances." +msgstr "" + +#: ./doc/admin-guide-cloud/ch_compute.xml1368(para) +msgid "" +"If you plan to use this feature, you must add edit the " +"/etc/nova/nova.conf file to specify to which interface " +"the nova-network service binds " +"public IP addresses, as follows:" +msgstr "" + +#: ./doc/admin-guide-cloud/ch_compute.xml1374(replaceable) +msgid "vlan100" +msgstr "" + +#: ./doc/admin-guide-cloud/ch_compute.xml1375(para) +msgid "" +"If you make changes to the /etc/nova/nova.conf file " +"while the nova-network service is" +" running, you must restart the service." +msgstr "" + +#: ./doc/admin-guide-cloud/ch_compute.xml1381(title) +msgid "Traffic between VMs using floating IPs" +msgstr "" + +#: ./doc/admin-guide-cloud/ch_compute.xml1383(para) +msgid "" +"Because floating IPs are implemented by using a source NAT (SNAT rule in " +"iptables), security groups can show inconsistent behavior if VMs use their " +"floating IP to communicate with other VMs, particularly on the same physical" +" host. Traffic from VM to VM across the fixed network does not have this " +"issue, and so this is the recommended path. To ensure that traffic does not " +"get SNATed to the floating range, explicitly set . The " +"x.x.x.x/y value specifies the range of floating IPs for " +"each pool of floating IPs that you define. If the VMs in the source group " +"have floating IPs, this configuration is also required." +msgstr "" + +#: ./doc/admin-guide-cloud/ch_compute.xml1402(title) +msgid "Enable IP forwarding" +msgstr "" + +#: ./doc/admin-guide-cloud/ch_compute.xml1403(para) +msgid "" +"By default, IP forwarding is disabled on most Linux distributions. To use " +"the floating IP feature, you must enable IP forwarding." +msgstr "" + +#: ./doc/admin-guide-cloud/ch_compute.xml1407(para) +msgid "" +"You must enable IP forwarding on only the nodes that run the nova-network service. If you use " +"multi_host mode, make sure to enable it on all compute " +"nodes. Otherwise, enable it on only the node that runs the nova-network service." +msgstr "" + +#: ./doc/admin-guide-cloud/ch_compute.xml1416(para) +msgid "To check if the forwarding is enabled, run this command:" +msgstr "" + +#: ./doc/admin-guide-cloud/ch_compute.xml1420(para) +msgid "Alternatively, you can run this command:" +msgstr "" + +#: ./doc/admin-guide-cloud/ch_compute.xml1423(para) +msgid "" +"In this example, IP forwarding is disabled. To enable it dynamically, run this " +"command:" +msgstr "" + +#: ./doc/admin-guide-cloud/ch_compute.xml1427(para) +msgid "Or:" +msgstr "" + +#: ./doc/admin-guide-cloud/ch_compute.xml1429(para) +msgid "" +"To make the changes permanent, edit the " +"/etc/sysctl.conf file and update the IP forwarding " +"setting:" +msgstr "" + +#: ./doc/admin-guide-cloud/ch_compute.xml1433(para) +msgid "Save the file and run this command to apply the changes:" +msgstr "" + +#: ./doc/admin-guide-cloud/ch_compute.xml1436(para) +msgid "You can also update the setting by restarting the network service." +msgstr "" + +#: ./doc/admin-guide-cloud/ch_compute.xml1438(para) +msgid "For example, on Ubuntu, run this command:" +msgstr "" + +#: ./doc/admin-guide-cloud/ch_compute.xml1440(para) +msgid "On RHEL/Fedora/CentOS, run this command:" +msgstr "" + +#: ./doc/admin-guide-cloud/ch_compute.xml1444(title) +msgid "Create a list of available floating IP addresses" +msgstr "" + +#: ./doc/admin-guide-cloud/ch_compute.xml1446(para) +msgid "" +"Nova maintains a list of floating IP addresses that you can assign to " +"instances. Use the command to add entries to this list." +msgstr "" + +#: ./doc/admin-guide-cloud/ch_compute.xml1452(para) +msgid "" +"You can use the following commands to perform floating IP " +"operations:" +msgstr "" + +#: ./doc/admin-guide-cloud/ch_compute.xml1458(para) +msgid "Lists the floating IP addresses in the pool." +msgstr "" + +#: ./doc/admin-guide-cloud/ch_compute.xml1463(replaceable) +msgid "[pool name]" +msgstr "" + +#: ./doc/admin-guide-cloud/ch_compute.xml1465(replaceable) +#: ./doc/admin-guide-cloud/ch_compute.xml1472(replaceable) +msgid "[CIDR]" +msgstr "" + +#: ./doc/admin-guide-cloud/ch_compute.xml1467(para) +msgid "Creates specific floating IPs for either a single address or a subnet." +msgstr "" + +#: ./doc/admin-guide-cloud/ch_compute.xml1473(para) +msgid "" +"Removes floating IP addresses using the same parameters as the create " +"command." +msgstr "" + +#: ./doc/admin-guide-cloud/ch_compute.xml1478(para) +msgid "" +"For information about how administrators can associate floating IPs with " +"instances, see Manage IP addresses in the " +"OpenStack Admin User Guide." +msgstr "" + +#: ./doc/admin-guide-cloud/ch_compute.xml1486(title) +msgid "Automatically add floating IPs" +msgstr "" + +#: ./doc/admin-guide-cloud/ch_compute.xml1487(para) +msgid "" +"You can configure the nova-" +"network service to automatically allocate and assign a floating" +" IP address to virtual instances when they are launched. Add the following " +"line to the /etc/nova/nova.conf file and restart the " +"nova-network service:" +msgstr "" + +#: ./doc/admin-guide-cloud/ch_compute.xml1497(para) +msgid "" +"If you enable this option and all floating IP addresses have already been " +"allocated, the command fails." +msgstr "" + +#: ./doc/admin-guide-cloud/ch_compute.xml1505(title) +msgid "Remove a network from a project" +msgstr "" + +#: ./doc/admin-guide-cloud/ch_compute.xml1506(para) +msgid "" +"You cannot remove a network that has already been associated to a project by" +" simply deleting it." +msgstr "" + +#: ./doc/admin-guide-cloud/ch_compute.xml1508(para) +msgid "" +"To determine the project ID you must have admin rights. You can disassociate" +" the project from the network with a scrub command and the project ID as the" +" final parameter:" +msgstr "" + +#: ./doc/admin-guide-cloud/ch_compute.xml1512(replaceable) +msgid "<id>" +msgstr "" + +#: ./doc/admin-guide-cloud/ch_compute.xml1515(title) +msgid "Multiple interfaces for your instances (multinic)" +msgstr "" + +#: ./doc/admin-guide-cloud/ch_compute.xml1522(para) +msgid "SSL Configurations (VIPs)" +msgstr "" + +#: ./doc/admin-guide-cloud/ch_compute.xml1525(para) +msgid "Services failover/ HA" +msgstr "" + +#: ./doc/admin-guide-cloud/ch_compute.xml1528(para) +msgid "Bandwidth Allocation" +msgstr "" + +#: ./doc/admin-guide-cloud/ch_compute.xml1531(para) +msgid "Administrative/ Public access to your instances" +msgstr "" + +#: ./doc/admin-guide-cloud/ch_compute.xml1538(title) +msgid "multinic flat manager" +msgstr "" + +#: ./doc/admin-guide-cloud/ch_compute.xml1548(title) +msgid "multinic flatdhcp manager" +msgstr "" + +#: ./doc/admin-guide-cloud/ch_compute.xml1558(title) +msgid "multinic VLAN manager" +msgstr "" + +#: ./doc/admin-guide-cloud/ch_compute.xml1518(para) +msgid "" +"The multi-nic feature allows you to plug more than one interface to your " +"instances, making it possible to make several use cases available: " +" Each VIF is representative of a separate network with its " +"own IP block. Every network mode introduces it's own set of changes " +"regarding the mulitnic usage: " +"" +msgstr "" + +#: ./doc/admin-guide-cloud/ch_compute.xml1569(title) +msgid "Use the multinic feature" +msgstr "" + +#: ./doc/admin-guide-cloud/ch_compute.xml1570(para) +msgid "" +"In order to use the multinic feature, first create two networks, and attach " +"them to your project: Now every time you spawn a new " +"instance, it gets two IP addresses from the respective DHCP servers:" +msgstr "" + +#: ./doc/admin-guide-cloud/ch_compute.xml1585(para) +msgid "" +"Make sure to power up the second interface on the instance, otherwise that " +"last won't be reachable through its second IP. Here is an example of how to " +"setup the interfaces within the instance (this is the configuration that " +"needs to be applied inside the image):" +msgstr "" + +#: ./doc/admin-guide-cloud/ch_compute.xml1591(filename) +msgid "/etc/network/interfaces" +msgstr "" + +#: ./doc/admin-guide-cloud/ch_compute.xml1603(para) +msgid "" +"If the Virtual Network Service Neutron is installed, it is possible to " +"specify the networks to attach to the respective interfaces by using the " +"--nic flag when invoking the nova " +"command: " +msgstr "" + +#: ./doc/admin-guide-cloud/ch_compute.xml1615(title) +msgid "Troubleshoot Networking" +msgstr "" + +#: ./doc/admin-guide-cloud/ch_compute.xml1617(title) +msgid "Cannot reach floating IPs" +msgstr "" + +#: ./doc/admin-guide-cloud/ch_compute.xml1618(para) +msgid "" +"If you cannot reach your instances through the floating IP address, make " +"sure the default security group allows ICMP (ping) and SSH (port 22), so " +"that you can reach the instances:" +msgstr "" + +#: ./doc/admin-guide-cloud/ch_compute.xml1629(para) +msgid "" +"Ensure the NAT rules have been added to iptables on the node that nova-" +"network is running on, as root:" +msgstr "" + +#: ./doc/admin-guide-cloud/ch_compute.xml1637(para) +msgid "" +"Check that the public address, in this example \"68.99.26.170\", has been " +"added to your public interface: You should see the address in the listing " +"when you enter \"ip addr\" at the command prompt." +msgstr "" + +#: ./doc/admin-guide-cloud/ch_compute.xml1649(para) +msgid "" +"Note that you cannot SSH to an instance with a public IP from within the " +"same server as the routing configuration won't allow it." +msgstr "" + +#: ./doc/admin-guide-cloud/ch_compute.xml1652(para) +msgid "" +"You can use to identify if packets are being routed to the " +"inbound interface on the compute host. If the packets are reaching the " +"compute hosts but the connection is failing, the issue may be that the " +"packet is being dropped by reverse path filtering. Try disabling reverse " +"path filtering on the inbound interface. For example, if the inbound " +"interface is eth2, as root:" +msgstr "" + +#: ./doc/admin-guide-cloud/ch_compute.xml1662(replaceable) +msgid "eth2" +msgstr "" + +#: ./doc/admin-guide-cloud/ch_compute.xml1663(para) +msgid "" +"If this solves your issue, add this line to " +"/etc/sysctl.conf so that the reverse path filter is " +"disabled the next time the compute host reboots: " +msgstr "" + +#: ./doc/admin-guide-cloud/ch_compute.xml1670(title) +msgid "Disable firewall" +msgstr "" + +#: ./doc/admin-guide-cloud/ch_compute.xml1671(para) +msgid "" +"To help debug networking issues with reaching VMs, you can disable the " +"firewall by setting the following option in " +"/etc/nova/nova.conf:" +msgstr "" + +#: ./doc/admin-guide-cloud/ch_compute.xml1676(para) +msgid "" +"We strongly recommend you remove this line to re-enable the firewall once " +"your networking issues have been resolved." +msgstr "" + +#: ./doc/admin-guide-cloud/ch_compute.xml1681(title) +msgid "Packet loss from instances to nova-network server (VLANManager mode)" +msgstr "" + +#: ./doc/admin-guide-cloud/ch_compute.xml1683(para) +msgid "" +"If you can SSH to your instances but you find that the network interactions " +"to your instance is slow, or if you find that running certain operations are" +" slower than they should be (for example, ), then there may " +"be packet loss occurring on the connection to the instance." +msgstr "" + +#: ./doc/admin-guide-cloud/ch_compute.xml1690(para) +msgid "" +"Packet loss can be caused by Linux networking configuration settings related" +" to bridges. Certain settings can cause packets to be dropped between the " +"VLAN interface (for example, vlan100) and the associated " +"bridge interface (for example, br100) on the host running" +" the nova-network service." +msgstr "" + +#: ./doc/admin-guide-cloud/ch_compute.xml1699(para) +msgid "" +"One way to check if this is the issue in your setup is to open up three " +"terminals and run the following commands:" +msgstr "" + +#: ./doc/admin-guide-cloud/ch_compute.xml1702(para) +msgid "" +"In the first terminal, on the host running nova-network, use " +" to monitor DNS-related traffic (UDP, port 53) on the VLAN " +"interface. As root:" +msgstr "" + +#: ./doc/admin-guide-cloud/ch_compute.xml1707(para) +msgid "" +"In the second terminal, also on the host running nova-network, use " +" to monitor DNS-related traffic on the bridge interface. As " +"root:" +msgstr "" + +#: ./doc/admin-guide-cloud/ch_compute.xml1712(para) +msgid "" +"In the third terminal, SSH inside of the instance and generate DNS requests " +"by using the command:" +msgstr "" + +#: ./doc/admin-guide-cloud/ch_compute.xml1716(para) +msgid "" +"The symptoms may be intermittent, so try running multiple " +"times. If the network configuration is correct, the command should return " +"immediately each time. If it is not functioning properly, the command hangs " +"for several seconds." +msgstr "" + +#: ./doc/admin-guide-cloud/ch_compute.xml1722(para) +msgid "" +"If the command sometimes hangs, and there are packets that " +"appear in the first terminal but not the second, then the problem may be due" +" to filtering done on the bridges. Try to disable filtering, as root:" +msgstr "" + +#: ./doc/admin-guide-cloud/ch_compute.xml1730(para) +msgid "" +"If this solves your issue, add this line to " +"/etc/sysctl.conf so that these changes take effect the " +"next time the host reboots:" +msgstr "" + +#: ./doc/admin-guide-cloud/ch_compute.xml1739(title) +msgid "KVM: Network connectivity works initially, then fails" +msgstr "" + +#: ./doc/admin-guide-cloud/ch_compute.xml1741(para) +msgid "" +"Some administrators have observed an issue with the KVM hypervisor where " +"instances running Ubuntu 12.04 sometimes loses network connectivity after " +"functioning properly for a period of time. Some users have reported success " +"with loading the vhost_net kernel module as a workaround for this issue (see" +" bug " +"#997978) . This kernel module may also improve network performance on KVM. To load " +"the kernel module, as root:" +msgstr "" + +#: ./doc/admin-guide-cloud/ch_compute.xml1756(para) +msgid "Loading the module has no effect on running instances." +msgstr "" + +#: ./doc/admin-guide-cloud/ch_compute.xml1763(title) +msgid "Volumes" +msgstr "" + +#: ./doc/admin-guide-cloud/ch_compute.xml1764(para) +msgid "" +"The Block Storage Service provides persistent block storage resources that " +"OpenStack Compute instances can consume." +msgstr "" + +#: ./doc/admin-guide-cloud/ch_compute.xml1767(para) +msgid "" +"See the OpenStack Configuration Reference for " +"information about configuring volume drivers and creating and attaching " +"volumes to server instances." +msgstr "" + +#: ./doc/admin-guide-cloud/ch_compute.xml1773(title) +msgid "System administration" +msgstr "" + +#: ./doc/admin-guide-cloud/ch_compute.xml1774(para) +msgid "" +"By understanding how the different installed nodes interact with each other " +"you can administer the Compute installation. Compute offers many ways to " +"install using multiple servers but the general idea is that you can have " +"multiple compute nodes that control the virtual servers and a cloud " +"controller node that contains the remaining Compute services." +msgstr "" + +#: ./doc/admin-guide-cloud/ch_compute.xml1781(para) +msgid "" +"The Compute cloud works through the interaction of a series of daemon " +"processes named nova-* that reside persistently on the host machine or " +"machines. These binaries can all run on the same machine or be spread out on" +" multiple boxes in a large deployment. The responsibilities of Services, " +"Managers, and Drivers, can be a bit confusing at first. Here is an outline " +"the division of responsibilities to make understanding the system a little " +"bit easier." +msgstr "" + +#: ./doc/admin-guide-cloud/ch_compute.xml1790(para) +msgid "" +"Currently, Services are nova-api," +" nova-objectstore (which can be " +"replaced with Glance, the OpenStack Image Service), nova-compute, and nova-network. Managers and Drivers are specified by " +"configuration options and loaded using utils.load_object(). Managers are " +"responsible for a certain aspect of the system. It is a logical grouping of " +"code relating to a portion of the system. In general other components should" +" be using the manager to make changes to the components that it is " +"responsible for." +msgstr "" + +#: ./doc/admin-guide-cloud/ch_compute.xml1805(para) +msgid "" +"nova-api. Receives xml requests " +"and sends them to the rest of the system. It is a wsgi app that routes and " +"authenticate requests. It supports the EC2 and OpenStack APIs. There is a " +"nova-api.conf file created when you install Compute." +msgstr "" + +#: ./doc/admin-guide-cloud/ch_compute.xml1814(para) +msgid "" +"nova-objectstore: The nova-objectstore service is an ultra simple " +"file-based storage system for images that replicates most of the S3 API. It " +"can be replaced with OpenStack Image Service and a simple image manager or " +"use OpenStack Object Storage as the virtual machine image storage facility. " +"It must reside on the same node as nova-" +"compute." +msgstr "" + +#: ./doc/admin-guide-cloud/ch_compute.xml1828(para) +msgid "" +"nova-compute. Responsible for " +"managing virtual machines. It loads a Service object which exposes the " +"public methods on ComputeManager through Remote Procedure Call (RPC)." +msgstr "" + +#: ./doc/admin-guide-cloud/ch_compute.xml1836(para) +msgid "" +"nova-network. Responsible for " +"managing floating and fixed IPs, DHCP, bridging and VLANs. It loads a " +"Service object which exposes the public methods on one of the subclasses of " +"NetworkManager. Different networking strategies are available to the service" +" by changing the network_manager configuration option to FlatManager, " +"FlatDHCPManager, or VlanManager (default is VLAN if no other is specified)." +msgstr "" + +#: ./doc/admin-guide-cloud/ch_compute.xml1849(title) +msgid "Compute service architecture" +msgstr "" + +#: ./doc/admin-guide-cloud/ch_compute.xml1850(para) +msgid "" +"These basic categories describe the service architecture and what's going on" +" within the cloud controller." +msgstr "" + +#: ./doc/admin-guide-cloud/ch_compute.xml1854(title) +msgid "API server" +msgstr "" + +#: ./doc/admin-guide-cloud/ch_compute.xml1855(para) +msgid "" +"At the heart of the cloud framework is an API server. This API server makes " +"command and control of the hypervisor, storage, and networking " +"programmatically available to users in realization of the definition of " +"cloud computing." +msgstr "" + +#: ./doc/admin-guide-cloud/ch_compute.xml1860(para) +msgid "" +"The API endpoints are basic HTTP web services which handle authentication, " +"authorization, and basic command and control functions using various API " +"interfaces under the Amazon, Rackspace, and related models. This enables API" +" compatibility with multiple existing tool sets created for interaction with" +" offerings from other vendors. This broad compatibility prevents vendor " +"lock-in." +msgstr "" + +#: ./doc/admin-guide-cloud/ch_compute.xml1871(title) +msgid "Message queue" +msgstr "" + +#: ./doc/admin-guide-cloud/ch_compute.xml1872(para) +msgid "" +"A messaging queue brokers the interaction between compute nodes " +"(processing), the networking controllers (software which controls network " +"infrastructure), API endpoints, the scheduler (determines which physical " +"hardware to allocate to a virtual resource), and similar components. " +"Communication to and from the cloud controller is by HTTP requests through " +"multiple API endpoints." +msgstr "" + +#: ./doc/admin-guide-cloud/ch_compute.xml1881(para) +msgid "" +"A typical message passing event begins with the API server receiving a " +"request from a user. The API server authenticates the user and ensures that " +"the user is permitted to issue the subject command. Availability of objects " +"implicated in the request is evaluated and, if available, the request is " +"routed to the queuing engine for the relevant workers. Workers continually " +"listen to the queue based on their role, and occasionally their type host " +"name. When such listening produces a work request, the worker takes " +"assignment of the task and begins its execution. Upon completion, a response" +" is dispatched to the queue which is received by the API server and relayed " +"to the originating user. Database entries are queried, added, or removed as " +"necessary throughout the process." +msgstr "" + +#: ./doc/admin-guide-cloud/ch_compute.xml1900(title) +msgid "Compute worker" +msgstr "" + +#: ./doc/admin-guide-cloud/ch_compute.xml1901(para) +msgid "" +"Compute workers manage computing instances on host machines. The API " +"dispatches commands to compute workers to complete these tasks:" +msgstr "" + +#: ./doc/admin-guide-cloud/ch_compute.xml1906(para) +msgid "Run instances" +msgstr "" + +#: ./doc/admin-guide-cloud/ch_compute.xml1909(para) +msgid "Terminate instances" +msgstr "" + +#: ./doc/admin-guide-cloud/ch_compute.xml1912(para) +msgid "Reboot instances" +msgstr "" + +#: ./doc/admin-guide-cloud/ch_compute.xml1915(para) +msgid "Attach volumes" +msgstr "" + +#: ./doc/admin-guide-cloud/ch_compute.xml1918(para) +msgid "Detach volumes" +msgstr "" + +#: ./doc/admin-guide-cloud/ch_compute.xml1921(para) +msgid "Get console output" +msgstr "" + +#: ./doc/admin-guide-cloud/ch_compute.xml1926(title) +msgid "Network Controller" +msgstr "" + +#: ./doc/admin-guide-cloud/ch_compute.xml1927(para) +msgid "" +"The Network Controller manages the networking resources on host machines. " +"The API server dispatches commands through the message queue, which are " +"subsequently processed by Network Controllers. Specific operations include:" +msgstr "" + +#: ./doc/admin-guide-cloud/ch_compute.xml1934(para) +msgid "Allocate fixed IP addresses" +msgstr "" + +#: ./doc/admin-guide-cloud/ch_compute.xml1937(para) +msgid "Configuring VLANs for projects" +msgstr "" + +#: ./doc/admin-guide-cloud/ch_compute.xml1940(para) +msgid "Configuring networks for compute nodes" +msgstr "" + +#: ./doc/admin-guide-cloud/ch_compute.xml1947(title) +msgid "Manage Compute users" +msgstr "" + +#: ./doc/admin-guide-cloud/ch_compute.xml1948(para) +msgid "" +"Access to the Euca2ools (ec2) API is controlled by an access and secret key." +" The user’s access key needs to be included in the request, and the request " +"must be signed with the secret key. Upon receipt of API requests, Compute " +"verifies the signature and runs commands on behalf of the user." +msgstr "" + +#: ./doc/admin-guide-cloud/ch_compute.xml1954(para) +msgid "" +"To begin using Compute, you must create a user with the Identity Service." +msgstr "" + +#: ./doc/admin-guide-cloud/ch_compute.xml1958(title) +msgid "Manage the cloud" +msgstr "" + +#: ./doc/admin-guide-cloud/ch_compute.xml1959(para) +msgid "" +"A system administrator can use these tools to manage a cloud; the nova " +"client, the command, and the commands." +msgstr "" + +#: ./doc/admin-guide-cloud/ch_compute.xml1963(para) +msgid "" +"The command can only be run by cloud administrators. Both " +"nova client and euca2ools can be used by all users, though specific commands" +" might be restricted by Role Based Access Control in the Identity Service." +msgstr "" + +#: ./doc/admin-guide-cloud/ch_compute.xml1969(title) +msgid "To use the nova command-line tool" +msgstr "" + +#: ./doc/admin-guide-cloud/ch_compute.xml1971(para) +msgid "" +"Installing the python-novaclient gives you a nova shell command" +" that enables Compute API interactions from the command line. You install " +"the client, and then provide your user name and password, set as environment" +" variables for convenience, and then you can have the ability to send " +"commands to your cloud on the command-line." +msgstr "" + +#: ./doc/admin-guide-cloud/ch_compute.xml1979(para) +msgid "" +"To install python-novaclient, download the tarball from http://pypi.python.org/pypi/python-" +"novaclient/2.6.3#downloads and then install it in your favorite " +"python environment." +msgstr "" + +#: ./doc/admin-guide-cloud/ch_compute.xml1991(para) +msgid "" +"Now that you have installed the python-novaclient, confirm the installation " +"by entering:" +msgstr "" + +#: ./doc/admin-guide-cloud/ch_compute.xml2002(para) +msgid "" +"This command returns a list of nova commands and parameters. Set the " +"required parameters as environment variables to make running commands " +"easier. You can add --os-username, for example, on " +"the nova command, or set it as environment variables:" +msgstr "" + +#: ./doc/admin-guide-cloud/ch_compute.xml2014(para) +msgid "" +"Using the Identity Service, you are supplied with an authentication " +"endpoint, which nova recognizes as the OS_AUTH_URL." +msgstr "" + +#: ./doc/admin-guide-cloud/ch_compute.xml2025(title) +msgid "To use the nova-manage command" +msgstr "" + +#: ./doc/admin-guide-cloud/ch_compute.xml2026(para) +msgid "" +"The nova-manage command may be used to perform many essential functions for " +"administration and ongoing maintenance of nova, such as network creation or " +"user manipulation." +msgstr "" + +#: ./doc/admin-guide-cloud/ch_compute.xml2031(para) +msgid "" +"The man page for nova-manage has a good explanation for each of its " +"functions, and is recommended reading for those starting out. Access it by " +"running:" +msgstr "" + +#: ./doc/admin-guide-cloud/ch_compute.xml2038(para) +msgid "" +"For administrators, the standard pattern for executing a nova-manage command" +" is:" +msgstr "" + +#: ./doc/admin-guide-cloud/ch_compute.xml2040(replaceable) +msgid "[args]" +msgstr "" + +#: ./doc/admin-guide-cloud/ch_compute.xml2043(para) +msgid "For example, to obtain a list of all projects:" +msgstr "" + +#: ./doc/admin-guide-cloud/ch_compute.xml2048(para) +msgid "Run without arguments to see a list of available command categories:" +msgstr "" + +#: ./doc/admin-guide-cloud/ch_compute.xml2053(para) +msgid "" +"You can also run with a category argument such as user to see a list of all " +"commands in that category:" +msgstr "" + +#: ./doc/admin-guide-cloud/ch_compute.xml2060(title) +msgid "Use the euca2ools commands" +msgstr "" + +#: ./doc/admin-guide-cloud/ch_compute.xml2061(para) +msgid "" +"For a command-line interface to EC2 API calls, use the euca2ools command " +"line tool. See http://open.eucalyptus.com/wiki/Euca2oolsGuide_v1.3" +msgstr "" + +#: ./doc/admin-guide-cloud/ch_compute.xml2070(title) +msgid "Manage logs" +msgstr "" + +#: ./doc/admin-guide-cloud/ch_compute.xml2072(title) +msgid "Logging module" +msgstr "" + +#: ./doc/admin-guide-cloud/ch_compute.xml2073(para) +msgid "" +"Add this line to the /etc/nova/nova.conf file to " +"specify a configuration file to change the logging behavior. To change the " +"logging level, such as DEBUG, INFO, " +"WARNING, ERROR): " +msgstr "" + +#: ./doc/admin-guide-cloud/ch_compute.xml2082(para) +msgid "" +"The log config file is an ini-style config file which must contain a section" +" called logger_nova, which controls the behavior of the " +"logging facility in the nova-* services. The file must " +"contain a section called logger_nova, for " +"example:" +msgstr "" + +#: ./doc/admin-guide-cloud/ch_compute.xml2093(para) +msgid "" +"This example sets the debugging level to INFO (which less" +" verbose than the default DEBUG setting). See the Python documentation on logging configuration " +"file format for more details on this file, including the meaning of " +"the handlers and quaname variables. " +"See etc/nova/logging_sample.conf" +" in the openstack/nova repository on GitHub for an example " +"logging.conf file with various handlers defined." +msgstr "" + +#: ./doc/admin-guide-cloud/ch_compute.xml2111(title) +msgid "Syslog" +msgstr "" + +#: ./doc/admin-guide-cloud/ch_compute.xml2112(para) +msgid "" +"You can configure OpenStack Compute services to send logging information to " +"syslog. This is useful if you want to use rsyslog, which forwards the logs " +"to a remote machine. You need to separately configure the Compute service " +"(Nova), the Identity Service (Keystone), the Image Service (Glance), and, if" +" you are using it, the Block Storage Service (Cinder) to send log messages " +"to syslog. To do so, add these lines to:" +msgstr "" + +#: ./doc/admin-guide-cloud/ch_compute.xml2123(filename) +msgid "/etc/nova/nova.conf" +msgstr "" + +#: ./doc/admin-guide-cloud/ch_compute.xml2126(filename) +msgid "/etc/keystone/keystone.conf" +msgstr "" + +#: ./doc/admin-guide-cloud/ch_compute.xml2129(filename) +msgid "/etc/glance/glance-api.conf" +msgstr "" + +#: ./doc/admin-guide-cloud/ch_compute.xml2132(filename) +msgid "/etc/glance/glance-registry.conf" +msgstr "" + +#: ./doc/admin-guide-cloud/ch_compute.xml2135(filename) +msgid "/etc/cinder/cinder.conf" +msgstr "" + +#: ./doc/admin-guide-cloud/ch_compute.xml2145(para) +msgid "" +"While the example above uses the same local facility for each service " +"(LOG_LOCAL0, which corresponds to syslog facility " +"LOCAL0), we recommend that you configure a separate local" +" facility for each service, as this provides better isolation and more " +"flexibility. For example, you may want to capture logging info at different " +"severity levels for different services. Syslog allows you to define up to " +"seven local facilities, LOCAL0, LOCAL1, ..., LOCAL7. See " +"the syslog documentation for more details." +msgstr "" + +#: ./doc/admin-guide-cloud/ch_compute.xml2142(para) +msgid "" +"In addition to enabling syslog, these settings also turn off more verbose " +"output and debugging output from the log." +msgstr "" + +#: ./doc/admin-guide-cloud/ch_compute.xml2163(title) +msgid "Rsyslog" +msgstr "" + +#: ./doc/admin-guide-cloud/ch_compute.xml2164(para) +msgid "" +"Rsyslog is a useful tool for setting up a centralized log server across " +"multiple machines. We briefly describe the configuration to set up an " +"rsyslog server; a full treatment of rsyslog is beyond the scope of this " +"document. We assume rsyslog has already been installed on your hosts, which " +"is the default on most Linux distributions." +msgstr "" + +#: ./doc/admin-guide-cloud/ch_compute.xml2172(para) +msgid "" +"This example shows a minimal configuration for " +"/etc/rsyslog.conf on the log server host, which " +"receives the log files:" +msgstr "" + +#: ./doc/admin-guide-cloud/ch_compute.xml2184(replaceable) +msgid "compute-01" +msgstr "" + +#: ./doc/admin-guide-cloud/ch_compute.xml2179(para) +msgid "" +"Add to /etc/rsyslog.conf a filter rule on which looks " +"for a host name. The example below use compute-01" +" as an example of a compute host name:" +msgstr "" + +#: ./doc/admin-guide-cloud/ch_compute.xml2185(para) +msgid "" +"On the compute hosts, create a file named " +"/etc/rsyslog.d/60-nova.conf, with this " +"content." +msgstr "" + +#: ./doc/admin-guide-cloud/ch_compute.xml2192(para) +msgid "" +"Once you have created this file, restart your rsyslog daemon. Error-level " +"log messages on the compute hosts should now be sent to your log server." +msgstr "" + +#: ./doc/admin-guide-cloud/ch_compute.xml2200(title) +msgid "Migration" +msgstr "" + +#: ./doc/admin-guide-cloud/ch_compute.xml2201(para) +msgid "" +"Before starting migrations, review the Configure migrations section in OpenStack " +"Configuration Reference." +msgstr "" + +#: ./doc/admin-guide-cloud/ch_compute.xml2206(para) +msgid "" +"Migration provides a scheme to migrate running instances from one OpenStack " +"Compute server to another OpenStack Compute server." +msgstr "" + +#: ./doc/admin-guide-cloud/ch_compute.xml2210(title) +msgid "To migrate instances" +msgstr "" + +#: ./doc/admin-guide-cloud/ch_compute.xml2212(para) +msgid "" +"Look at the running instances, to get the ID of the instance you wish to " +"migrate." +msgstr "" + +#: ./doc/admin-guide-cloud/ch_compute.xml2223(para) +msgid "" +"Look at information associated with that instance - our example is vm1 from " +"above." +msgstr "" + +#: ./doc/admin-guide-cloud/ch_compute.xml2240(para) +msgid "In this example, vm1 is running on HostB." +msgstr "" + +#: ./doc/admin-guide-cloud/ch_compute.xml2244(para) +msgid "Select the server to migrate instances to." +msgstr "" + +#: ./doc/admin-guide-cloud/ch_compute.xml2251(para) +msgid "" +"In this example, HostC can be picked up because nova-compute is running on it." +msgstr "" + +#: ./doc/admin-guide-cloud/ch_compute.xml2257(para) +msgid "Ensure that HostC has enough resource for migration." +msgstr "" + +#: ./doc/admin-guide-cloud/ch_compute.xml2269(para) +msgid "cpu:the number of cpu" +msgstr "" + +#: ./doc/admin-guide-cloud/ch_compute.xml2274(para) +msgid "mem(mb):total amount of memory (MB)" +msgstr "" + +#: ./doc/admin-guide-cloud/ch_compute.xml2279(para) +msgid "" +"hdd:total amount of space for NOVA-INST-" +"DIR/instances (GB)" +msgstr "" + +#: ./doc/admin-guide-cloud/ch_compute.xml2285(para) +msgid "" +"1st line shows total amount of resource " +"physical server has." +msgstr "" + +#: ./doc/admin-guide-cloud/ch_compute.xml2290(para) +msgid "2nd line shows current used resource." +msgstr "" + +#: ./doc/admin-guide-cloud/ch_compute.xml2295(para) +msgid "3rd line shows maximum used resource." +msgstr "" + +#: ./doc/admin-guide-cloud/ch_compute.xml2300(para) +msgid "" +"4th line and under shows the resource for" +" each project." +msgstr "" + +#: ./doc/admin-guide-cloud/ch_compute.xml2307(para) +msgid "Use the command to migrate the instances." +msgstr "" + +#: ./doc/admin-guide-cloud/ch_compute.xml2320(para) +msgid "" +"While the nova command is called , under the default Compute" +" configuration options the instances are suspended before migration." +msgstr "" + +#: ./doc/admin-guide-cloud/ch_compute.xml2325(para) +msgid "" +"See Configure migrations in " +"OpenStack Configuration Reference for more details." +msgstr "" + +#: ./doc/admin-guide-cloud/ch_compute.xml2311(para) +msgid "" +"Make sure instances are migrated successfully with . If " +"instances are still running on HostB, check log files (src/dest nova-compute and nova-scheduler) to determine why. " +msgstr "" + +#: ./doc/admin-guide-cloud/ch_compute.xml2337(title) +msgid "Recover from a failed compute node" +msgstr "" + +#: ./doc/admin-guide-cloud/ch_compute.xml2338(para) +msgid "" +"If you have deployed Compute with a shared file system, you can quickly " +"recover from a failed compute node. Of the two methods covered in these " +"sections, the evacuate API is the preferred method even in the absence of " +"shared storage. The evacuate API provides many benefits over manual " +"recovery, such as re-attachment of volumes and floating IPs." +msgstr "" + +#: ./doc/admin-guide-cloud/ch_compute.xml2347(title) +msgid "Manual recovery" +msgstr "" + +#: ./doc/admin-guide-cloud/ch_compute.xml2348(para) +msgid "" +"For KVM/libvirt compute node recovery, see the previous section. Use this " +"procedure for other hypervisors." +msgstr "" + +#: ./doc/admin-guide-cloud/ch_compute.xml2352(title) +msgid "To work with host information" +msgstr "" + +#: ./doc/admin-guide-cloud/ch_compute.xml2354(para) +msgid "" +"Identify the vms on the affected hosts, using tools such as a combination of" +" nova list and nova show or euca-describe-instances. Here's an example using the EC2 API - " +"instance i-000015b9 that is running on node np-rcc54:" +msgstr "" + +#: ./doc/admin-guide-cloud/ch_compute.xml2365(para) +msgid "" +"You can review the status of the host by using the nova database. Some of " +"the important information is highlighted below. This example converts an EC2" +" API instance ID into an OpenStack ID - if you used the " +"nova commands, you can substitute the ID directly. You " +"can find the credentials for your database in " +"/etc/nova.conf." +msgstr "" + +#: ./doc/admin-guide-cloud/ch_compute.xml2396(title) +msgid "To recover the VM" +msgstr "" + +#: ./doc/admin-guide-cloud/ch_compute.xml2398(para) +msgid "" +"Armed with the information of VMs on the failed host, determine to which " +"compute host the affected VMs should move. Run the following database " +"command to move the VM to np-rcc46:" +msgstr "" + +#: ./doc/admin-guide-cloud/ch_compute.xml2406(para) +msgid "" +"Next, if using a hypervisor that relies on libvirt (such as KVM) it is a " +"good idea to update the libvirt.xml file (found in " +"/var/lib/nova/instances/[instance ID]). The important " +"changes to make are to change the DHCPSERVER value to the" +" host ip address of the Compute host that is the VMs new home, and update " +"the VNC IP if it isn't already 0.0.0.0." +msgstr "" + +#: ./doc/admin-guide-cloud/ch_compute.xml2421(para) +msgid "Next, reboot the VM:" +msgstr "" + +#: ./doc/admin-guide-cloud/ch_compute.xml2425(para) +msgid "" +"In theory, the above database update and nova reboot " +"command are all that is required to recover the VMs from a failed host. " +"However, if further problems occur, consider looking at recreating the " +"network filter configuration using virsh, restarting the " +"Compute services or updating the vm_state and " +"power_state in the Compute database." +msgstr "" + +#: ./doc/admin-guide-cloud/ch_compute.xml2442(title) +msgid "Recover from a UID/GID mismatch" +msgstr "" + +#: ./doc/admin-guide-cloud/ch_compute.xml2443(para) +msgid "" +"When running OpenStack compute, using a shared file system or an automated " +"configuration tool, you could encounter a situation where some files on your" +" compute node are using the wrong UID or GID. This causes a raft of errors, " +"such as being unable to live migrate, or start virtual machines." +msgstr "" + +#: ./doc/admin-guide-cloud/ch_compute.xml2449(para) +msgid "" +"This basic procedure runs on nova-" +"compute hosts, based on the KVM hypervisor, that could help to " +"restore the situation:" +msgstr "" + +#: ./doc/admin-guide-cloud/ch_compute.xml2454(title) +msgid "To recover from a UID/GID mismatch" +msgstr "" + +#: ./doc/admin-guide-cloud/ch_compute.xml2456(para) +msgid "" +"Make sure you don't use numbers that are already used for some other " +"user/group." +msgstr "" + +#: ./doc/admin-guide-cloud/ch_compute.xml2460(para) +msgid "" +"Set the nova uid in /etc/passwd to the same number in " +"all hosts (for example, 112)." +msgstr "" + +#: ./doc/admin-guide-cloud/ch_compute.xml2466(para) +msgid "" +"Set the libvirt-qemu uid in /etc/passwd to the same " +"number in all hosts (for example, 119)." +msgstr "" + +#: ./doc/admin-guide-cloud/ch_compute.xml2472(para) +msgid "" +"Set the nova group in /etc/group file to the same " +"number in all hosts (for example, 120)." +msgstr "" + +#: ./doc/admin-guide-cloud/ch_compute.xml2478(para) +msgid "" +"Set the libvirtd group in /etc/group file to the same " +"number in all hosts (for example, 119)." +msgstr "" + +#: ./doc/admin-guide-cloud/ch_compute.xml2484(para) +msgid "Stop the services on the compute node." +msgstr "" + +#: ./doc/admin-guide-cloud/ch_compute.xml2488(para) +msgid "Change all the files owned by user nova or by group nova. For example:" +msgstr "" + +#: ./doc/admin-guide-cloud/ch_compute.xml2494(para) +msgid "" +"Repeat the steps for the libvirt-qemu owned files if those were needed to " +"change." +msgstr "" + +#: ./doc/admin-guide-cloud/ch_compute.xml2498(para) +msgid "Restart the services." +msgstr "" + +#: ./doc/admin-guide-cloud/ch_compute.xml2501(para) +msgid "" +"Now you can run the command to verify that all files using " +"the correct identifiers." +msgstr "" + +#: ./doc/admin-guide-cloud/ch_compute.xml2508(title) +msgid "Compute disaster recovery process" +msgstr "" + +#: ./doc/admin-guide-cloud/ch_compute.xml2509(para) +msgid "" +"In this section describes how to manage your cloud after a disaster, and how" +" to easily back up the persistent storage volumes. Backups are mandatory, even outside of disaster scenarios." +msgstr "" + +#: ./doc/admin-guide-cloud/ch_compute.xml2514(para) +msgid "" +"For reference, you can find a DRP definition at http://en.wikipedia.org/wiki/Disaster_Recovery_Plan." +msgstr "" + +#: ./doc/admin-guide-cloud/ch_compute.xml2519(title) +msgid "A- The disaster recovery process presentation" +msgstr "" + +#: ./doc/admin-guide-cloud/ch_compute.xml2521(para) +msgid "" +"A disaster could happen to several components of your architecture: a disk " +"crash, a network loss, a power cut, and so on. In this example, assume the " +"following set up:" +msgstr "" + +#: ./doc/admin-guide-cloud/ch_compute.xml2527(para) +msgid "A cloud controller (nova-api, nova-objecstore, nova-network)" +msgstr "" + +#: ./doc/admin-guide-cloud/ch_compute.xml2531(para) +msgid "A compute node (nova-compute)" +msgstr "" + +#: ./doc/admin-guide-cloud/ch_compute.xml2536(para) +msgid "" +"A Storage Area Network used by cinder-" +"volumes (aka SAN)" +msgstr "" + +#: ./doc/admin-guide-cloud/ch_compute.xml2542(para) +msgid "" +"The disaster example is the worst one: a power loss. That power loss applies" +" to the three components. Let's see what runs and " +"how it runs before the crash:" +msgstr "" + +#: ./doc/admin-guide-cloud/ch_compute.xml2549(para) +msgid "" +"From the SAN to the cloud controller, we have an active iscsi session (used " +"for the \"cinder-volumes\" LVM's VG)." +msgstr "" + +#: ./doc/admin-guide-cloud/ch_compute.xml2554(para) +msgid "" +"From the cloud controller to the compute node we also have active iscsi " +"sessions (managed by cinder-" +"volume)." +msgstr "" + +#: ./doc/admin-guide-cloud/ch_compute.xml2560(para) +msgid "" +"For every volume an iscsi session is made (so 14 ebs volumes equals 14 " +"sessions)." +msgstr "" + +#: ./doc/admin-guide-cloud/ch_compute.xml2565(para) +msgid "" +"From the cloud controller to the compute node, we also have iptables/ " +"ebtables rules which allows the access from the cloud controller to the " +"running instance." +msgstr "" + +#: ./doc/admin-guide-cloud/ch_compute.xml2572(para) +msgid "" +"And at least, from the cloud controller to the compute node ; saved into " +"database, the current state of the instances (in that case \"running\" ), " +"and their volumes attachment (mount point, volume id, volume status, and so " +"on.)" +msgstr "" + +#: ./doc/admin-guide-cloud/ch_compute.xml2580(para) +msgid "" +"Now, after the power loss occurs and all hardware components restart, the " +"situation is as follows:" +msgstr "" + +#: ./doc/admin-guide-cloud/ch_compute.xml2585(para) +msgid "From the SAN to the cloud, the ISCSI session no longer exists." +msgstr "" + +#: ./doc/admin-guide-cloud/ch_compute.xml2589(para) +msgid "" +"From the cloud controller to the compute node, the ISCSI sessions no longer " +"exist." +msgstr "" + +#: ./doc/admin-guide-cloud/ch_compute.xml2594(para) +msgid "" +"From the cloud controller to the compute node, the iptables and ebtables are" +" recreated, since, at boot, nova-network reapply the configurations." +msgstr "" + +#: ./doc/admin-guide-cloud/ch_compute.xml2600(para) +msgid "" +"From the cloud controller, instances turn into a shutdown state (because " +"they are no longer running)" +msgstr "" + +#: ./doc/admin-guide-cloud/ch_compute.xml2605(para) +msgid "" +"Into the database, data was not updated at all, since Compute could not have" +" guessed the crash." +msgstr "" + +#: ./doc/admin-guide-cloud/ch_compute.xml2610(para) +msgid "" +"Before going further, and to prevent the admin to make fatal " +"mistakes, the instances won't be lost, " +"because no \"\" or \"\" command was invoked," +" so the files for the instances remain on the compute node." +msgstr "" + +#: ./doc/admin-guide-cloud/ch_compute.xml2617(para) +msgid "Perform these tasks in that exact order." +msgstr "" + +#: ./doc/admin-guide-cloud/ch_compute.xml2618(para) +msgid "" +"Any extra step would be dangerous at this " +"stage :" +msgstr "" + +#: ./doc/admin-guide-cloud/ch_compute.xml2623(para) +msgid "" +"Get the current relation from a volume to its instance, so that you can " +"recreate the attachment." +msgstr "" + +#: ./doc/admin-guide-cloud/ch_compute.xml2628(para) +msgid "" +"Update the database to clean the stalled state. (After that, you cannot " +"perform the first step)." +msgstr "" + +#: ./doc/admin-guide-cloud/ch_compute.xml2633(para) +msgid "" +"Restart the instances. In other words, go from a shutdown to running state." +msgstr "" + +#: ./doc/admin-guide-cloud/ch_compute.xml2638(para) +msgid "" +"After the restart, you can reattach the volumes to their respective " +"instances." +msgstr "" + +#: ./doc/admin-guide-cloud/ch_compute.xml2643(para) +msgid "" +"That step, which is not a mandatory one, exists in an SSH into the instances" +" to reboot them." +msgstr "" + +#: ./doc/admin-guide-cloud/ch_compute.xml2651(title) +msgid "B - Disaster recovery" +msgstr "" + +#: ./doc/admin-guide-cloud/ch_compute.xml2653(title) +msgid "To perform disaster recovery" +msgstr "" + +#: ./doc/admin-guide-cloud/ch_compute.xml2655(title) +msgid "Get the instance-to-volume relationship" +msgstr "" + +#: ./doc/admin-guide-cloud/ch_compute.xml2657(para) +msgid "" +"You must get the current relationship from a volume to its instance, because" +" we re-create the attachment." +msgstr "" + +#: ./doc/admin-guide-cloud/ch_compute.xml2660(para) +msgid "" +"You can find this relationship by running . Note that nova " +"client includes the ability to get volume information from cinder." +msgstr "" + +#: ./doc/admin-guide-cloud/ch_compute.xml2667(title) +msgid "Update the database" +msgstr "" + +#: ./doc/admin-guide-cloud/ch_compute.xml2668(para) +msgid "" +"Update the database to clean the stalled state. You must restore for every " +"volume, uses these queries to clean up the database:" +msgstr "" + +#: ./doc/admin-guide-cloud/ch_compute.xml2677(para) +msgid "Then, when you run commands, all volumes appear." +msgstr "" + +#: ./doc/admin-guide-cloud/ch_compute.xml2682(title) +msgid "Restart instances" +msgstr "" + +#: ./doc/admin-guide-cloud/ch_compute.xml2685(replaceable) +msgid "$instance" +msgstr "" + +#: ./doc/admin-guide-cloud/ch_compute.xml2683(para) +msgid "You can restart the instances through the ." +msgstr "" + +#: ./doc/admin-guide-cloud/ch_compute.xml2686(para) +msgid "" +"At that stage, depending on your image, some instances completely reboot and" +" become reachable, while others stop on the \"plymouth\" stage." +msgstr "" + +#: ./doc/admin-guide-cloud/ch_compute.xml2692(title) +msgid "DO NOT reboot a second time" +msgstr "" + +#: ./doc/admin-guide-cloud/ch_compute.xml2693(para) +msgid "" +"Do not reboot the ones that are stopped at that stage (see the fourth step). In fact it depends on " +"whether you added an /etc/fstab entry for that volume. " +"Images built with the cloud-init package remain in a " +"pending state, while others skip the missing volume and start. (More " +"information is available on help.ubuntu.com.)" +" The idea of that stage is only to ask nova to reboot every instance, so the" +" stored state is preserved." +msgstr "" + +#: ./doc/admin-guide-cloud/ch_compute.xml2710(title) +msgid "Reattach volumes" +msgstr "" + +#: ./doc/admin-guide-cloud/ch_compute.xml2711(para) +msgid "" +"After the restart, you can reattach the volumes to their respective " +"instances. Now that nova has restored the right status, it is time to " +"perform the attachments through a " +msgstr "" + +#: ./doc/admin-guide-cloud/ch_compute.xml2717(para) +msgid "This simple snippet uses the created file:" +msgstr "" + +#: ./doc/admin-guide-cloud/ch_compute.xml2729(para) +msgid "" +"At that stage, instances that were pending on the boot sequence (plymouth) automatically continue their boot, and " +"restart normally, while the ones that booted see the volume." +msgstr "" + +#: ./doc/admin-guide-cloud/ch_compute.xml2737(title) +msgid "SSH into instances" +msgstr "" + +#: ./doc/admin-guide-cloud/ch_compute.xml2738(para) +msgid "" +"If some services depend on the volume, or if a volume has an entry into " +"fstab, it could be good to simply restart the instance. This restart needs " +"to be made from the instance itself, not through nova. So, we SSH into the " +"instance and perform a reboot:" +msgstr "" + +#: ./doc/admin-guide-cloud/ch_compute.xml2748(para) +msgid "By completing this procedure, you can successfully recover your cloud." +msgstr "" + +#: ./doc/admin-guide-cloud/ch_compute.xml2750(para) +msgid "Follow these guidelines:" +msgstr "" + +#: ./doc/admin-guide-cloud/ch_compute.xml2753(para) +msgid "" +"Use the errors=remount parameter in the " +"fstab file, which prevents data corruption." +msgstr "" + +#: ./doc/admin-guide-cloud/ch_compute.xml2757(para) +msgid "" +"The system would lock any write to the disk if it detects an I/O error. This" +" configuration option should be added into the cinder-volume server (the one which performs the ISCSI " +"connection to the SAN), but also into the instances' " +"fstab file." +msgstr "" + +#: ./doc/admin-guide-cloud/ch_compute.xml2768(para) +msgid "" +"Do not add the entry for the SAN's disks to the cinder-volume's fstab file." +msgstr "" + +#: ./doc/admin-guide-cloud/ch_compute.xml2773(para) +msgid "" +"Some systems hang on that step, which means you could lose access to your " +"cloud-controller. To re-run the session manually, you would run the " +"following command before performing the mount: " +msgstr "" + +#: ./doc/admin-guide-cloud/ch_compute.xml2781(para) +msgid "" +"For your instances, if you have the whole /home/ " +"directory on the disk, instead of emptying the /home " +"directory and map the disk on it, leave a user's directory with the user's " +"bash files and the authorized_keys file." +msgstr "" + +#: ./doc/admin-guide-cloud/ch_compute.xml2789(para) +msgid "" +"This enables you to connect to the instance, even without the volume " +"attached, if you allow only connections through public keys." +msgstr "" + +#: ./doc/admin-guide-cloud/ch_compute.xml2797(title) +msgid "C - Scripted DRP" +msgstr "" + +#: ./doc/admin-guide-cloud/ch_compute.xml2799(title) +msgid "To use scripted DRP" +msgstr "" + +#: ./doc/admin-guide-cloud/ch_compute.xml2800(para) +msgid "" +"You can download from here a bash script " +"which performs these steps:" +msgstr "" + +#: ./doc/admin-guide-cloud/ch_compute.xml2805(para) +msgid "" +"The \"test mode\" allows you to perform that whole sequence for only one " +"instance." +msgstr "" + +#: ./doc/admin-guide-cloud/ch_compute.xml2810(para) +msgid "" +"To reproduce the power loss, connect to the compute node which runs that " +"same instance and close the iscsi session. Do " +"not detach the volume through , but instead " +"manually close the iscsi session." +msgstr "" + +#: ./doc/admin-guide-cloud/ch_compute.xml2821(para) +msgid "In this example, the iscsi session is number 15 for that instance:" +msgstr "" + +#: ./doc/admin-guide-cloud/ch_compute.xml2826(para) +msgid "" +"Do not forget the -r flag. Otherwise, you close ALL " +"sessions." +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking-config-identity.xml6(title) +msgid "Configure Identity Service for Networking" +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking-config-identity.xml8(title) +msgid "To configure the Identity Service for use with Networking" +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking-config-identity.xml11(title) +msgid "Create the get_id() function" +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking-config-identity.xml12(para) +msgid "" +"The get_id() function stores the ID of created objects," +" and removes the need to copy and paste object IDs in later steps:" +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking-config-identity.xml16(para) +msgid "Add the following function to your .bashrc file:" +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking-config-identity.xml23(para) +msgid "Source the .bashrc file:" +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking-config-identity.xml29(title) +msgid "Create the Networking service entry" +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking-config-identity.xml30(para) +msgid "" +"Networking must be available in the Compute service catalog. Create the " +"service:" +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking-config-identity.xml34(title) +msgid "Create the Networking service endpoint entry" +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking-config-identity.xml36(para) +msgid "" +"The way that you create a Networking endpoint entry depends on whether you " +"are using the SQL or the template catalog driver:" +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking-config-identity.xml40(para) +msgid "" +"If you use the SQL driver, run the following command " +"with the specified region ($REGION), IP address of the " +"Networking server ($IP), and service ID " +"($NEUTRON_SERVICE_ID, obtained in the previous step)." +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking-config-identity.xml52(para) +msgid "" +"If you are using the template driver, specify the " +"following parameters in your Compute catalog template file " +"(default_catalog.templates), along with the region " +"($REGION) and IP address of the Networking server " +"($IP)." +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking-config-identity.xml70(title) +msgid "Create the Networking service user" +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking-config-identity.xml71(para) +msgid "" +"You must provide admin user credentials that Compute and some internal " +"Networking components can use to access the Networking API. Create a special" +" service tenant and a neutron user " +"within this tenant, and assign an admin role to this " +"role." +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking-config-identity.xml77(para) +msgid "Create the admin role:" +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking-config-identity.xml82(para) +msgid "Create the neutron user:" +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking-config-identity.xml87(para) +msgid "Create the service tenant:" +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking-config-identity.xml91(para) +msgid "Establish the relationship among the tenant, user, and role:" +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking-config-identity.xml98(para) +msgid "" +"For information about how to create service entries and users, see the " +"OpenStack Installation Guide for your distribution " +"(docs.openstack.org)." +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking-config-identity.xml103(para) +msgid "" +"If you use Networking, do not run the Compute nova-network service (like you do in traditional Compute " +"deployments). Instead, Compute delegates most network-related decisions to " +"Networking. Compute proxies tenant-facing API calls to manage security " +"groups and floating IPs to Networking APIs. However, operator-facing tools " +"such as nova-manage, are not " +"proxied and should not be used." +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking-config-identity.xml110(para) +msgid "" +"When you configure networking, you must use this guide. Do not rely on " +"Compute networking documentation or past experience with Compute. If a " +" command or configuration option related to networking is " +"not mentioned in this guide, the command is probably not supported for use " +"with Networking. In particular, you cannot use CLI tools like " +" and to manage networks or IP addressing, " +"including both fixed and floating IPs, with Networking." +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking-config-identity.xml118(para) +msgid "" +"Uninstall nova-network and reboot" +" any physical nodes that have been running nova-network before using them to run Networking. " +"Inadvertently running the nova-" +"network process while using Networking can cause problems, as " +"can stale iptables rules pushed down by previously running nova-network." +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking-config-identity.xml126(para) +msgid "" +"To ensure that Compute works properly with Networking (rather than the " +"legacy nova-network mechanism), " +"you must adjust settings in the nova.conf configuration" +" file." +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking-config-identity.xml133(title) +msgid "Networking API and credential configuration" +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking-config-identity.xml134(para) +msgid "" +"Each time you provision or de-provision a VM in Compute, nova-* services communicate with Networking " +"using the standard API. For this to happen, you must configure the following" +" items in the nova.conf file (used by each nova-compute and nova-api instance)." +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking-config-identity.xml140(caption) +msgid "nova.conf API and credential settings" +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking-config-identity.xml145(th) +#: ./doc/admin-guide-cloud/section_networking-config-identity.xml220(td) +#: ./doc/admin-guide-cloud/section_networking-config-identity.xml255(td) +msgid "Item" +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking-config-identity.xml151(literal) +msgid "network_api_class" +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking-config-identity.xml153(para) +msgid "" +"Modify from the default to " +"nova.network.neutronv2.api.API, to indicate that " +"Networking should be used rather than the traditional nova-network networking model." +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking-config-identity.xml161(literal) +msgid "neutron_url" +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking-config-identity.xml162(para) +msgid "" +"Update to the hostname/IP and port of the neutron-server instance for this deployment." +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking-config-identity.xml168(literal) +msgid "neutron_auth_strategy" +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking-config-identity.xml169(para) +msgid "" +"Keep the default keystone value for all production " +"deployments." +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking-config-identity.xml173(literal) +msgid "neutron_admin_tenant_name" +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking-config-identity.xml175(para) +msgid "" +"Update to the name of the service tenant created in the above section on " +"Identity configuration." +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking-config-identity.xml180(literal) +msgid "neutron_admin_username" +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking-config-identity.xml182(para) +msgid "" +"Update to the name of the user created in the above section on Identity " +"configuration." +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking-config-identity.xml187(literal) +msgid "neutron_admin_password" +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking-config-identity.xml189(para) +msgid "" +"Update to the password of the user created in the above section on Identity " +"configuration." +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking-config-identity.xml194(literal) +msgid "neutron_admin_auth_url" +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking-config-identity.xml196(para) +msgid "" +"Update to the Identity server IP and port. This is the Identity (keystone) " +"admin API server IP and port value, and not the Identity service API IP and " +"port." +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking-config-identity.xml206(title) +msgid "Configure security groups" +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking-config-identity.xml207(para) +msgid "" +"The Networking Service provides security group functionality using a " +"mechanism that is more flexible and powerful than the security group " +"capabilities built into Compute. Therefore, if you use Networking, you " +"should always disable built-in security groups and proxy all security group " +"calls to the Networking API . If you do not, security policies will conflict" +" by being simultaneously applied by both services." +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking-config-identity.xml212(para) +msgid "" +"To proxy security groups to Networking, use the following configuration " +"values in nova.conf:" +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking-config-identity.xml215(caption) +msgid "nova.conf security group settings" +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking-config-identity.xml226(literal) +msgid "firewall_driver" +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking-config-identity.xml227(para) +msgid "" +"Update to nova.virt.firewall.NoopFirewallDriver, so that " +"nova-compute does not perform " +"iptables-based filtering itself." +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking-config-identity.xml234(literal) +msgid "security_group_api" +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking-config-identity.xml235(para) +msgid "" +"Update to neutron, so that all security group requests " +"are proxied to the Network Service." +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking-config-identity.xml242(title) +msgid "Configure metadata" +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking-config-identity.xml243(para) +msgid "" +"The Compute service allows VMs to query metadata associated with a VM by " +"making a web request to a special 169.254.169.254 address. Networking " +"supports proxying those requests to nova-" +"api, even when the requests are made from isolated networks, or" +" from multiple networks that use overlapping IP addresses." +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking-config-identity.xml247(para) +msgid "" +"To enable proxying the requests, you must update the following fields in " +"nova.conf." +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking-config-identity.xml250(caption) +msgid "nova.conf metadata settings" +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking-config-identity.xml261(literal) +msgid "service_neutron_metadata_proxy" +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking-config-identity.xml263(para) +msgid "" +"Update to true, otherwise nova-api will not properly respond to requests from the " +"neutron-metadata-agent." +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking-config-identity.xml270(literal) +msgid "neutron_metadata_proxy_shared_secret" +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking-config-identity.xml272(para) +msgid "" +"Update to a string \"password\" value. You must also configure the same " +"value in the metadata_agent.ini file, to authenticate " +"requests made for metadata." +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking-config-identity.xml276(para) +msgid "" +"The default value of an empty string in both files will allow metadata to " +"function, but will not be secure if any non-trusted entities have access to " +"the metadata APIs exposed by nova-" +"api." +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking-config-identity.xml285(para) +msgid "" +"As a precaution, even when using " +"neutron_metadata_proxy_shared_secret, it is recommended " +"that you do not expose metadata using the same nova-api instances that are used for tenants. Instead, you " +"should run a dedicated set of nova-" +"api instances for metadata that are available only on your " +"management network. Whether a given nova-" +"api instance exposes metadata APIs is determined by the value " +"of enabled_apis in its nova.conf." +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking-config-identity.xml300(title) +msgid "" +"Example nova.conf (for nova-" +"compute and nova-" +"api)" +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking-config-identity.xml303(para) +msgid "" +"Example values for the above settings, assuming a cloud controller node " +"running Compute and Networking with an IP address of 192.168.1.2:" +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking-use.xml5(title) +msgid "Use Networking" +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking-use.xml6(para) +msgid "" +"You can start and stop OpenStack Networking services using the " +"service command. For example:" +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking-use.xml13(para) +msgid "" +"Log files are in the /var/log/neutron directory." +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking-use.xml16(para) +msgid "" +"Configuration files are in the /etc/neutron " +"directory." +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking-use.xml19(para) +msgid "You can use Networking in the following ways:" +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking-use.xml22(para) +msgid "" +"Expose the Networking API to cloud tenants, which enables them to build rich" +" network topologies." +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking-use.xml27(para) +msgid "" +"Have the cloud administrator, or an automated administrative tool, create " +"network connectivity on behalf of tenants." +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking-use.xml32(para) +msgid "" +"A tenant or cloud administrator can both perform the following procedures." +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking-use.xml35(title) +msgid "Core Networking API features" +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking-use.xml36(para) +msgid "" +"After you install and run Networking, tenants and administrators can perform" +" create-read-update-delete (CRUD) API networking operations by using the " +"Networking API directly or the neutron command-line interface (CLI). The " +"neutron CLI is a wrapper around the Networking API. Every Networking API " +"call has a corresponding neutron command." +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking-use.xml43(para) +msgid "" +"The CLI includes a number of options. For details, refer to the OpenStack " +"End User Guide." +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking-use.xml49(title) +#: ./doc/admin-guide-cloud/section_networking-use.xml57(caption) +msgid "API abstractions" +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking-use.xml50(para) +msgid "" +"The Networking v2.0 API provides control over both L2 network topologies and" +" the IP addresses used on those networks (IP Address Management or IPAM). " +"There is also an extension to cover basic L3 forwarding and NAT, which " +"provides capabilities similar to ." +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking-use.xml62(th) +msgid "Abstraction" +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking-use.xml70(td) +msgid "" +"An isolated L2 network segment (similar to a VLAN) that forms the basis for " +"describing the L2 network topology available in an Networking deployment." +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking-use.xml79(td) +msgid "" +"Associates a block of IP addresses and other network configuration, such as," +" default gateways or dns-servers, with an Networking network. Each subnet " +"represents an IPv4 or IPv6 address block and, if needed, each Networking " +"network can have multiple subnets." +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking-use.xml91(td) +msgid "" +"Represents an attachment port to a L2 Networking network. When a port is " +"created on the network, by default it is allocated an available fixed IP " +"address out of one of the designated subnets for each IP version (if one " +"exists). When the port is destroyed, its allocated addresses return to the " +"pool of available IPs on the subnet. Users of the Networking API can either " +"choose a specific IP address from the block, or let Networking choose the " +"first available IP address." +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking-use.xml110(para) +msgid "" +"This table summarizes the attributes available for each networking " +"abstraction. For information about API abstraction and operations, see the " +"Networking API v2.0 Reference." +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking-use.xml117(caption) +msgid "Network attributes" +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking-use.xml124(th) +#: ./doc/admin-guide-cloud/section_networking-use.xml197(th) +#: ./doc/admin-guide-cloud/section_networking-use.xml301(th) +msgid "Attribute" +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking-use.xml133(td) +#: ./doc/admin-guide-cloud/section_networking-use.xml155(td) +#: ./doc/admin-guide-cloud/section_networking-use.xml234(td) +#: ./doc/admin-guide-cloud/section_networking-use.xml310(td) +msgid "bool" +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking-use.xml135(td) +msgid "" +"Administrative state of the network. If specified as False (down), this " +"network does not forward packets." +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking-use.xml143(td) +#: ./doc/admin-guide-cloud/section_networking-use.xml258(td) +#: ./doc/admin-guide-cloud/section_networking-use.xml343(td) +#: ./doc/admin-guide-cloud/section_networking-use.xml349(td) +msgid "Generated" +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking-use.xml144(td) +msgid "UUID for this network." +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking-use.xml148(td) +#: ./doc/admin-guide-cloud/section_networking-use.xml165(td) +#: ./doc/admin-guide-cloud/section_networking-use.xml220(td) +#: ./doc/admin-guide-cloud/section_networking-use.xml241(td) +#: ./doc/admin-guide-cloud/section_networking-use.xml269(td) +#: ./doc/admin-guide-cloud/section_networking-use.xml318(td) +#: ./doc/admin-guide-cloud/section_networking-use.xml326(td) +#: ./doc/admin-guide-cloud/section_networking-use.xml348(td) +#: ./doc/admin-guide-cloud/section_networking-use.xml354(td) +#: ./doc/admin-guide-cloud/section_networking-use.xml368(td) +msgid "string" +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking-use.xml150(td) +msgid "Human-readable name for this network; is not required to be unique." +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking-use.xml157(td) +msgid "" +"Specifies whether this network resource can be accessed by any tenant. The " +"default policy setting restricts usage of this attribute to administrative " +"users only." +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking-use.xml167(td) +msgid "Indicates whether this network is currently operational." +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking-use.xml171(option) +msgid "subnets" +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking-use.xml172(td) +msgid "list(uuid-str)" +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking-use.xml173(td) +#: ./doc/admin-guide-cloud/section_networking-use.xml228(td) +#: ./doc/admin-guide-cloud/section_networking-use.xml250(td) +msgid "Empty list" +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking-use.xml174(td) +msgid "List of subnets associated with this network." +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking-use.xml181(td) +msgid "" +"Tenant owner of the network. Only administrative users can set the tenant " +"identifier; this cannot be changed using authorization policies." +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking-use.xml190(caption) +msgid "Subnet attributes" +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking-use.xml205(option) +msgid "allocation_pools" +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking-use.xml206(td) +#: ./doc/admin-guide-cloud/section_networking-use.xml249(td) +#: ./doc/admin-guide-cloud/section_networking-use.xml333(td) +msgid "list(dict)" +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking-use.xml209(option) +#: ./doc/admin-guide-cloud/section_networking-use.xml240(option) +msgid "gateway_ip" +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking-use.xml207(td) +msgid "" +"Every address in , excluding (if " +"configured)." +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking-use.xml211(para) +msgid "" +"List of cidr sub-ranges that are available for dynamic allocation to ports. " +"Syntax:" +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking-use.xml222(td) +msgid "IP range for this subnet, based on the IP version." +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking-use.xml226(option) +msgid "dns_nameservers" +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking-use.xml227(td) +msgid "list(string)" +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking-use.xml229(td) +msgid "List of DNS name servers used by hosts in this subnet." +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking-use.xml233(option) +msgid "enable_dhcp" +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking-use.xml236(td) +msgid "Specifies whether DHCP is enabled for this subnet." +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking-use.xml242(td) +msgid "First address in " +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking-use.xml244(td) +msgid "Default gateway used by devices in this subnet." +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking-use.xml248(option) +msgid "host_routes" +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking-use.xml251(td) +msgid "" +"Routes that should be used by devices with IPs from this subnet (not " +"including local subnet route)." +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking-use.xml257(td) +#: ./doc/admin-guide-cloud/section_networking-use.xml276(td) +#: ./doc/admin-guide-cloud/section_networking-use.xml283(td) +#: ./doc/admin-guide-cloud/section_networking-use.xml342(td) +#: ./doc/admin-guide-cloud/section_networking-use.xml361(td) +#: ./doc/admin-guide-cloud/section_networking-use.xml375(td) +msgid "uuid-string" +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking-use.xml259(td) +msgid "UUID representing this subnet." +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking-use.xml263(td) +msgid "int" +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking-use.xml265(td) +msgid "IP version." +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking-use.xml271(td) +msgid "Human-readable name for this subnet (might not be unique)." +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking-use.xml275(option) +#: ./doc/admin-guide-cloud/section_networking-use.xml360(option) +msgid "network_id" +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking-use.xml278(td) +msgid "Network with which this subnet is associated." +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking-use.xml285(td) +msgid "" +"Owner of network. Only administrative users can set the tenant identifier; " +"this cannot be changed using authorization policies." +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking-use.xml294(caption) +msgid "Port attributes" +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking-use.xml311(td) +msgid "true" +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking-use.xml312(td) +msgid "" +"Administrative state of this port. If specified as False (down), this port " +"does not forward packets." +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking-use.xml317(option) +msgid "device_id" +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking-use.xml320(td) +msgid "" +"Identifies the device using this port (for example, a virtual server's ID)." +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking-use.xml325(option) +#: ./doc/admin-guide-cloud/section_networking-use.xml426(option) +msgid "device_owner" +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking-use.xml328(td) +msgid "Identifies the entity using this port (for example, a dhcp agent)." +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking-use.xml332(option) +#: ./doc/admin-guide-cloud/section_networking-use.xml425(option) +msgid "fixed_ips" +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking-use.xml334(td) +msgid "Automatically allocated from pool" +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking-use.xml335(td) +msgid "" +"Specifies IP addresses for this port; associates the port with the subnets " +"containing the listed IP addresses." +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking-use.xml344(td) +msgid "UUID for this port." +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking-use.xml347(option) +#: ./doc/admin-guide-cloud/section_networking-use.xml570(option) +msgid "mac_address" +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking-use.xml350(td) +msgid "Mac address to use on this port." +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking-use.xml356(td) +msgid "Human-readable name for this port (might not be unique)." +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking-use.xml363(td) +msgid "Network with which this port is associated." +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking-use.xml370(td) +msgid "Indicates whether the network is currently operational." +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking-use.xml377(td) +msgid "" +"Owner of the network. Only administrative users can set the tenant " +"identifier; this cannot be changed using authorization policies." +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking-use.xml387(title) +#: ./doc/admin-guide-cloud/section_networking-use.xml398(caption) +msgid "Basic Networking operations" +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking-use.xml388(para) +msgid "" +"To learn about advanced capabilities that are available through the neutron " +"command-line interface (CLI), read the networking section in the OpenStack " +"End User Guide." +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking-use.xml394(para) +msgid "" +"This table shows example neutron commands that enable you to complete basic " +"Networking operations:" +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking-use.xml409(td) +msgid "Creates a network." +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking-use.xml413(td) +msgid "Creates a subnet that is associated with net1." +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking-use.xml418(td) +msgid "Lists ports for a specified tenant." +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking-use.xml423(td) +msgid "" +"Lists ports for a specified tenant and displays the , " +", and columns." +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking-use.xml432(td) +msgid "Shows information for a specified port." +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking-use.xml434(replaceable) +#: ./doc/admin-guide-cloud/section_networking-use.xml577(replaceable) +#: ./doc/admin-guide-cloud/section_networking-use.xml630(option) +#: ./doc/admin-guide-cloud/section_networking-use.xml634(replaceable) +msgid "port-id" +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking-use.xml439(para) +msgid "" +"The field describes who owns the port. A port " +"whose begins with:" +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking-use.xml445(para) +msgid "network is created by Networking." +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking-use.xml449(para) +msgid "compute is created by Compute." +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking-use.xml456(title) +msgid "Administrative operations" +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking-use.xml457(para) +msgid "" +"The cloud administrator can run any command on behalf of " +"tenants by specifying an Identity in the command," +" as follows:" +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking-use.xml462(replaceable) +msgid "tenant-id" +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking-use.xml462(replaceable) +msgid "network-name" +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking-use.xml466(para) +msgid "" +"To view all tenant IDs in Identity, run the following command as an Identity" +" Service admin user:" +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking-use.xml474(title) +#: ./doc/admin-guide-cloud/section_networking-use.xml479(caption) +msgid "Advanced Networking operations" +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking-use.xml475(para) +msgid "" +"This table shows example neutron commands that enable you to complete " +"advanced Networking operations:" +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking-use.xml490(td) +msgid "Creates a network that all tenants can use." +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking-use.xml495(td) +msgid "Creates a subnet with a specified gateway IP address." +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking-use.xml500(td) +msgid "Creates a subnet that has no gateway IP address." +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking-use.xml505(td) +msgid "Creates a subnet with DHCP disabled." +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking-use.xml510(td) +msgid "Creates a subnet with a specified set of host routes." +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking-use.xml515(td) +msgid "Creates a subnet with a specified set of dns name servers." +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking-use.xml520(td) +msgid "Displays all ports and IPs allocated on a network." +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking-use.xml522(replaceable) +#: ./doc/admin-guide-cloud/section_networking-use.xml555(replaceable) +#: ./doc/admin-guide-cloud/section_networking-use.xml632(option) +#: ./doc/admin-guide-cloud/section_networking-use.xml633(replaceable) +msgid "net-id" +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking-use.xml530(title) +msgid "Use Compute with Networking" +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking-use.xml532(title) +#: ./doc/admin-guide-cloud/section_networking-use.xml537(caption) +msgid "Basic Compute and Networking operations" +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking-use.xml533(para) +msgid "" +"This table shows example neutron and nova commands that enable you to " +"complete basic Compute and Networking operations:" +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking-use.xml543(th) +msgid "Action" +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking-use.xml549(td) +msgid "Checks available networks." +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking-use.xml553(td) +msgid "Boots a VM with a single NIC on a selected Networking network." +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking-use.xml555(replaceable) +#: ./doc/admin-guide-cloud/section_networking-use.xml624(replaceable) +#: ./doc/admin-guide-cloud/section_networking-use.xml634(replaceable) +#: ./doc/admin-guide-cloud/section_networking-use.xml643(replaceable) +msgid "img" +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking-use.xml555(replaceable) +#: ./doc/admin-guide-cloud/section_networking-use.xml624(replaceable) +#: ./doc/admin-guide-cloud/section_networking-use.xml634(replaceable) +#: ./doc/admin-guide-cloud/section_networking-use.xml643(replaceable) +msgid "flavor" +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking-use.xml555(replaceable) +#: ./doc/admin-guide-cloud/section_networking-use.xml624(replaceable) +#: ./doc/admin-guide-cloud/section_networking-use.xml634(replaceable) +#: ./doc/admin-guide-cloud/section_networking-use.xml643(replaceable) +msgid "vm-name" +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking-use.xml559(para) +msgid "" +"Searches for ports with a that matches the " +"Compute instance UUID. See ." +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking-use.xml566(replaceable) +#: ./doc/admin-guide-cloud/section_networking-use.xml572(replaceable) +msgid "vm-id" +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking-use.xml569(td) +msgid "Searches for ports, but shows only the for the port." +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking-use.xml575(td) +msgid "Temporarily disables a port from sending traffic." +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking-use.xml582(para) +msgid "The can also be a logical router ID." +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking-use.xml586(title) +msgid "Create and delete VMs" +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking-use.xml589(para) +msgid "" +"When you boot a Compute VM, a port on the network that corresponds to the VM" +" NIC is automatically created and associated with the default security " +"group. You can configure security " +"group rules to enable users to access the VM." +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking-use.xml599(para) +msgid "" +"When you delete a Compute VM, the underlying Networking port is " +"automatically deleted." +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking-use.xml607(title) +#: ./doc/admin-guide-cloud/section_networking-use.xml612(caption) +msgid "Advanced VM creation operations" +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking-use.xml608(para) +msgid "" +"This table shows example nova and neutron commands that enable you to " +"complete advanced VM creation operations:" +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking-use.xml623(td) +msgid "Boots a VM with multiple NICs." +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking-use.xml624(replaceable) +msgid "net1-id" +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking-use.xml624(replaceable) +msgid "net2-id" +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking-use.xml627(td) +msgid "" +"Boots a VM with a specific IP address. First, create an Networking port with" +" a specific IP address. Then, boot a VM specifying a rather" +" than a ." +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking-use.xml633(replaceable) +msgid "subnet-id" +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking-use.xml633(replaceable) +msgid "IP" +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking-use.xml641(parameter) +msgid "--nic" +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking-use.xml638(td) +msgid "" +"Boots a VM that connects to all networks that are accessible to the tenant " +"who submits the request (without the option)." +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking-use.xml649(para) +msgid "" +"Networking does not currently support the v4-fixed-ip" +" parameter of the --nic option for the " +" command." +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking-use.xml656(title) +msgid "Enable ping and SSH on VMs (security groups)" +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking-use.xml658(para) +msgid "" +"You must configure security group rules depending on the type of plug-in you" +" are using. If you are using a plug-in that:" +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking-use.xml663(para) +msgid "" +"Implements Networking security groups, you can configure security group " +"rules directly by using . This example enables " +" and access to your VMs." +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking-use.xml677(para) +msgid "" +"Does not implement Networking security groups, you can configure security " +"group rules by using the or command. These" +" commands enable and " +"access to your VMs." +msgstr "" + +#: ./doc/admin-guide-cloud/section_networking-use.xml691(para) +msgid "" +"If your plug-in implements Networking security groups, you can also leverage" +" Compute security groups by setting security_group_api = " +"neutron in the nova.conf file. After you set " +"this option, all Compute security group commands are proxied to Networking." +msgstr "" + +#: ./doc/admin-guide-cloud/identity/section_keystone-token-binding.xml6(title) +msgid "Configure the Identity Service for token binding" +msgstr "" + +#: ./doc/admin-guide-cloud/identity/section_keystone-token-binding.xml7(para) +msgid "" +"Token binding refers to the practice of embedding information from external " +"authentication providers (like a company's Kerberos server) inside the token" +" such that a client may enforce that the token only be used in conjunction " +"with that specified authentication. This is an additional security mechanism" +" as it means that if a token is stolen it will not be usable without also " +"providing the external authentication." +msgstr "" + +#: ./doc/admin-guide-cloud/identity/section_keystone-token-binding.xml14(para) +msgid "" +"To activate token binding you must specify the types of authentication that " +"token binding should be used for in keystone.conf: " +" Currently only kerberos is supported." +msgstr "" + +#: ./doc/admin-guide-cloud/identity/section_keystone-token-binding.xml25(para) +msgid "disabled disable token bind checking" +msgstr "" + +#: ./doc/admin-guide-cloud/identity/section_keystone-token-binding.xml29(para) +msgid "" +"permissive enable bind checking, if a token is bound to a" +" mechanism that is unknown to the server then ignore it. This is the " +"default." +msgstr "" + +#: ./doc/admin-guide-cloud/identity/section_keystone-token-binding.xml34(para) +msgid "" +"strict enable bind checking, if a token is bound to a " +"mechanism that is unknown to the server then this token should be rejected." +msgstr "" + +#: ./doc/admin-guide-cloud/identity/section_keystone-token-binding.xml39(para) +msgid "" +"required enable bind checking and require that at least 1" +" bind mechanism is used for tokens." +msgstr "" + +#: ./doc/admin-guide-cloud/identity/section_keystone-token-binding.xml44(para) +msgid "" +"named enable bind checking and require that the specified" +" authentication mechanism is used: " +msgstr "" + +#: ./doc/admin-guide-cloud/identity/section_keystone-token-binding.xml51(para) +msgid "" +"Do not set enforce_token_bind = named as there is not an " +"authentication mechanism called named." +msgstr "" + +#: ./doc/admin-guide-cloud/identity/section_keystone-token-binding.xml20(para) +msgid "" +"To enforce checking of token binding the " +"enforce_token_bind parameter should be set to one of the " +"following modes: " +msgstr "" + +#. Put one translator per line, in the form of NAME , YEAR1, YEAR2 +#: ./doc/admin-guide-cloud/identity/section_keystone-token-binding.xml0(None) +msgid "translator-credits" +msgstr "" diff --git a/doc/common/locale/common.pot b/doc/common/locale/common.pot new file mode 100644 index 0000000000..cda3a2adda --- /dev/null +++ b/doc/common/locale/common.pot @@ -0,0 +1,23467 @@ +msgid "" +msgstr "" +"Project-Id-Version: PACKAGE VERSION\n" +"POT-Creation-Date: 2014-01-30 06:24+0000\n" +"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n" +"Last-Translator: FULL NAME \n" +"Language-Team: LANGUAGE \n" +"MIME-Version: 1.0\n" +"Content-Type: text/plain; charset=UTF-8\n" +"Content-Transfer-Encoding: 8bit\n" + +#: ./doc/common/app_support.xml:7(title) +msgid "Community support" +msgstr "" + +#: ./doc/common/app_support.xml:9(para) +msgid "Many resources are available to help you run and use OpenStack. Members of the OpenStack community can answer questions and help with bug suspicions. We are constantly improving and adding to the main features of OpenStack, but if you have any problems, do not hesitate to ask. Use the following resources to get OpenStack support and troubleshoot your existing installations." +msgstr "" + +#: ./doc/common/app_support.xml:18(title) +msgid "Documentation" +msgstr "" + +#: ./doc/common/app_support.xml:19(para) +msgid "For the available OpenStack documentation, see docs.openstack.org." +msgstr "" + +#: ./doc/common/app_support.xml:22(para) ./doc/common/app_support.xml:342(para) ./doc/common/ch_getstart.xml:174(para) +msgid "To provide feedback on documentation, join and use the openstack-docs@lists.openstack.org mailing list at OpenStack Documentation Mailing List, or report a bug." +msgstr "" + +#: ./doc/common/app_support.xml:30(para) +msgid "The following books explain how to install an OpenStack cloud and its associated components:" +msgstr "" + +#: ./doc/common/app_support.xml:37(citetitle) +msgid "Installation Guide for Debian 7.0" +msgstr "" + +#: ./doc/common/app_support.xml:44(citetitle) +msgid "Installation Guide for openSUSE and SUSE Linux Enterprise Server" +msgstr "" + +#: ./doc/common/app_support.xml:51(citetitle) +msgid "Installation Guide for Red Hat Enterprise Linux, CentOS, and Fedora" +msgstr "" + +#: ./doc/common/app_support.xml:59(citetitle) +msgid "Installation Guide for Ubuntu 12.04 (LTS)" +msgstr "" + +#: ./doc/common/app_support.xml:64(para) +msgid "The following books explain how to configure and run an OpenStack cloud:" +msgstr "" + +#: ./doc/common/app_support.xml:71(citetitle) +msgid "Cloud Administrator Guide" +msgstr "" + +#: ./doc/common/app_support.xml:77(citetitle) +msgid "Configuration Reference" +msgstr "" + +#: ./doc/common/app_support.xml:83(citetitle) +msgid "Operations Guide" +msgstr "" + +#: ./doc/common/app_support.xml:88(citetitle) +msgid "High Availability Guide" +msgstr "" + +#: ./doc/common/app_support.xml:94(citetitle) +msgid "Security Guide" +msgstr "" + +#: ./doc/common/app_support.xml:100(citetitle) +msgid "Virtual Machine Image Guide" +msgstr "" + +#: ./doc/common/app_support.xml:104(para) +msgid "The following books explain how to use the OpenStack dashboard and command-line clients:" +msgstr "" + +#: ./doc/common/app_support.xml:111(citetitle) +msgid "API Quick Start" +msgstr "" + +#: ./doc/common/app_support.xml:118(citetitle) +msgid "End User Guide" +msgstr "" + +#: ./doc/common/app_support.xml:125(citetitle) +msgid "Admin User Guide" +msgstr "" + +#: ./doc/common/app_support.xml:129(para) +msgid "The following documentation provides reference and guidance information for the OpenStack APIs:" +msgstr "" + +#: ./doc/common/app_support.xml:131(link) +msgid "OpenStack API Reference" +msgstr "" + +#: ./doc/common/app_support.xml:135(citetitle) +msgid "OpenStack Block Storage Service API v2 Reference" +msgstr "" + +#: ./doc/common/app_support.xml:142(citetitle) +msgid "OpenStack Compute API v2 and Extensions Reference" +msgstr "" + +#: ./doc/common/app_support.xml:147(citetitle) +msgid "OpenStack Identity Service API v2.0 Reference" +msgstr "" + +#: ./doc/common/app_support.xml:152(citetitle) +msgid "OpenStack Image Service API v2 Reference" +msgstr "" + +#: ./doc/common/app_support.xml:157(citetitle) +msgid "OpenStack Networking API v2.0 Reference" +msgstr "" + +#: ./doc/common/app_support.xml:162(citetitle) +msgid "OpenStack Object Storage API v1 Reference" +msgstr "" + +#: ./doc/common/app_support.xml:164(para) +msgid "The Training Guides offer software training for cloud administration and management." +msgstr "" + +#: ./doc/common/app_support.xml:170(title) +msgid "ask.openstack.org" +msgstr "" + +#: ./doc/common/app_support.xml:171(para) +msgid "During the set up or testing of OpenStack, you might have questions about how a specific task is completed or be in a situation where a feature does not work correctly. Use the ask.openstack.org site to ask questions and get answers. When you visit the http://ask.openstack.org site, scan the recently asked questions to see whether your question has already been answered. If not, ask a new question. Be sure to give a clear, concise summary in the title and provide as much detail as possible in the description. Paste in your command output or stack traces, links to screen shots, and so on." +msgstr "" + +#: ./doc/common/app_support.xml:186(title) +msgid "OpenStack mailing lists" +msgstr "" + +#: ./doc/common/app_support.xml:187(para) +msgid "A great way to get answers and insights is to post your question or problematic scenario to the OpenStack mailing list. You can learn from and help others who might have similar issues. To subscribe or view the archives, go to http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack. You might be interested in the other mailing lists for specific projects or development, which you can find on the wiki. A description of all mailing lists is available at http://wiki.openstack.org/MailingLists." +msgstr "" + +#: ./doc/common/app_support.xml:203(title) +msgid "The OpenStack wiki" +msgstr "" + +#: ./doc/common/app_support.xml:204(para) +msgid "The OpenStack wiki contains a broad range of topics but some of the information can be difficult to find or is a few pages deep. Fortunately, the wiki search feature enables you to search by title or content. If you search for specific information, such as about networking or nova, you can find lots of relevant material. More is being added all the time, so be sure to check back often. You can find the search box in the upper right corner of any OpenStack wiki page." +msgstr "" + +#: ./doc/common/app_support.xml:216(title) +msgid "The Launchpad Bugs area" +msgstr "" + +#: ./doc/common/app_support.xml:217(para) +msgid "The OpenStack community values your set up and testing efforts and wants your feedback. To log a bug, you must sign up for a Launchpad account at https://launchpad.net/+login. You can view existing bugs and report bugs in the Launchpad Bugs area. Use the search feature to determine whether the bug has already been reported or even better, already fixed. If it still seems like your bug is unreported, fill out a bug report." +msgstr "" + +#: ./doc/common/app_support.xml:227(para) +msgid "Some tips:" +msgstr "" + +#: ./doc/common/app_support.xml:230(para) +msgid "Give a clear, concise summary!" +msgstr "" + +#: ./doc/common/app_support.xml:233(para) +msgid "Provide as much detail as possible in the description. Paste in your command output or stack traces, links to screen shots, and so on." +msgstr "" + +#: ./doc/common/app_support.xml:238(para) +msgid "Be sure to include the software and package versions that you are using, especially if you are using a development branch, such as, \"Grizzly release\" vs git commit bc79c3ecc55929bac585d04a03475b72e06a3208." +msgstr "" + +#: ./doc/common/app_support.xml:244(para) +msgid "Any deployment specific information is helpful, such as Ubuntu 12.04 or multi-node install." +msgstr "" + +#: ./doc/common/app_support.xml:248(para) +msgid "The Launchpad Bugs areas are available here:" +msgstr "" + +#: ./doc/common/app_support.xml:251(link) +msgid "Bugs: OpenStack Compute (nova)" +msgstr "" + +#: ./doc/common/app_support.xml:255(link) +msgid "Bugs: OpenStack Object Storage (swift)" +msgstr "" + +#: ./doc/common/app_support.xml:259(link) +msgid "Bugs: OpenStack Image Service (glance)" +msgstr "" + +#: ./doc/common/app_support.xml:264(link) +msgid "Bugs: OpenStack Identity (keystone)" +msgstr "" + +#: ./doc/common/app_support.xml:267(link) +msgid "Bugs: OpenStack Dashboard (horizon)" +msgstr "" + +#: ./doc/common/app_support.xml:271(link) +msgid "Bugs: OpenStack Networking (neutron)" +msgstr "" + +#: ./doc/common/app_support.xml:275(link) +msgid "Bugs: OpenStack Orchestration (heat)" +msgstr "" + +#: ./doc/common/app_support.xml:280(link) +msgid "Bugs: OpenStack Telemetry (ceilometer)" +msgstr "" + +#: ./doc/common/app_support.xml:284(link) +msgid "Bugs: Database Service (trove)" +msgstr "" + +#: ./doc/common/app_support.xml:288(link) +msgid "Bugs: Bare Metal (ironic)" +msgstr "" + +#: ./doc/common/app_support.xml:292(link) +msgid "Bugs: OpenStack Queue Service (marconi)" +msgstr "" + +#: ./doc/common/app_support.xml:296(link) +msgid "Bugs: OpenStack Data Processing Service (savanna)" +msgstr "" + +#: ./doc/common/app_support.xml:301(link) +msgid "Bugs: OpenStack Documentation (docs.openstack.org)" +msgstr "" + +#: ./doc/common/app_support.xml:307(link) +msgid "Bugs: OpenStack API Documentation (api.openstack.org)" +msgstr "" + +#: ./doc/common/app_support.xml:313(title) +msgid "The OpenStack IRC channel" +msgstr "" + +#: ./doc/common/app_support.xml:314(para) +msgid "The OpenStack community lives and breathes in the #openstack IRC channel on the Freenode network. You can hang out, ask questions, or get immediate feedback for urgent and pressing issues. To install an IRC client or use a browser-based client, go to http://webchat.freenode.net/. You can also use Colloquy (Mac OS X, http://colloquy.info/), mIRC (Windows, http://www.mirc.com/), or XChat (Linux). When you are in the IRC channel and want to share code or command output, the generally accepted method is to use a Paste Bin. The OpenStack project has one at http://paste.openstack.org. Just paste your longer amounts of text or logs in the web form and you get a URL you can paste into the channel. The OpenStack IRC channel is: #openstack on irc.freenode.net. You can find a list of all OpenStack-related IRC channels at https://wiki.openstack.org/wiki/IRC." +msgstr "" + +#: ./doc/common/app_support.xml:340(title) +msgid "Documentation feedback" +msgstr "" + +#: ./doc/common/app_support.xml:354(title) +msgid "OpenStack distribution packages" +msgstr "" + +#: ./doc/common/app_support.xml:355(para) +msgid "The following Linux distributions provide community-supported packages for OpenStack:" +msgstr "" + +#: ./doc/common/app_support.xml:361(emphasis) +msgid "Debian:" +msgstr "" + +#: ./doc/common/app_support.xml:362(link) +msgid "http://wiki.debian.org/OpenStack" +msgstr "" + +#: ./doc/common/app_support.xml:365(emphasis) +msgid "CentOS, Fedora, and Red Hat Enterprise Linux:" +msgstr "" + +#: ./doc/common/app_support.xml:367(link) +msgid "http://openstack.redhat.com/" +msgstr "" + +#: ./doc/common/app_support.xml:371(emphasis) +msgid "openSUSE and SUSE Linux Enterprise Server:" +msgstr "" + +#: ./doc/common/app_support.xml:374(link) +msgid "http://en.opensuse.org/Portal:OpenStack" +msgstr "" + +#: ./doc/common/app_support.xml:378(emphasis) +msgid "Ubuntu:" +msgstr "" + +#: ./doc/common/app_support.xml:380(link) +msgid "https://wiki.ubuntu.com/ServerTeam/CloudArchive" +msgstr "" + +#: ./doc/common/section_cli_glance_manage_images.xml:7(title) +msgid "Manage images" +msgstr "" + +#: ./doc/common/section_cli_glance_manage_images.xml:8(para) +msgid "The cloud operator assigns roles to users. Roles determine who can upload and manage images. The operator might restrict image upload and management to only cloud administrators or operators." +msgstr "" + +#: ./doc/common/section_cli_glance_manage_images.xml:12(para) +msgid "You can upload images through the glance client or the Image Service API. You can also use the nova client to list images, set, and delete image metadata, delete images, and take a snapshot of a running instance to create an image. After you upload an image, you cannot change it." +msgstr "" + +#: ./doc/common/section_cli_glance_manage_images.xml:16(para) +msgid "For details about image creation, see the Virtual Machine Image Guide." +msgstr "" + +#: ./doc/common/section_cli_glance_manage_images.xml:21(title) +msgid "List or get details for images (glance)" +msgstr "" + +#: ./doc/common/section_cli_glance_manage_images.xml:24(para) +msgid "To list the available images:" +msgstr "" + +#: ./doc/common/section_cli_glance_manage_images.xml:34(para) +msgid "You can use grep to filter the list, as follows:" +msgstr "" + +#: ./doc/common/section_cli_glance_manage_images.xml:42(para) +msgid "To get image details, by name or ID:" +msgstr "" + +#: ./doc/common/section_cli_glance_manage_images.xml:82(para) +msgid "To store location metadata for images, which enables direct file access for a client, update the /etc/glance/glance.conf file with the following statements:" +msgstr "" + +#: ./doc/common/section_cli_glance_manage_images.xml:89(code) +msgid "show_multiple_locations = True" +msgstr "" + +#: ./doc/common/section_cli_glance_manage_images.xml:92(para) +msgid "filesystem_store_metadata_file = filePath, where filePath points to a JSON file that defines the mount point for OpenStack images on your system and a unique ID. For example: " +msgstr "" + +#: ./doc/common/section_cli_glance_manage_images.xml:108(para) +msgid "After you restart the Image Service, you can use the following syntax to view the image's location information:" +msgstr "" + +#: ./doc/common/section_cli_glance_manage_images.xml:109(replaceable) +msgid "imageID" +msgstr "" + +#: ./doc/common/section_cli_glance_manage_images.xml:110(para) ./doc/common/section_cli_nova_quotas.xml:190(para) ./doc/common/section_cli_nova_quotas.xml:214(para) ./doc/common/section_cli_nova_quotas.xml:228(para) ./doc/common/section_cli_nova_quotas.xml:256(para) ./doc/common/section_cli_nova_quotas.xml:299(para) ./doc/common/section_cli_nova_quotas.xml:331(para) ./doc/common/section_cli_keystone_services.xml:100(para) ./doc/common/section_keystone_certificates-for-pki.xml:180(para) ./doc/common/section_cli_cinder_manage_volumes.xml:352(para) ./doc/common/section_cli_cinder_manage_volumes.xml:366(para) ./doc/common/section_cli_cinder_manage_volumes.xml:410(para) ./doc/common/section_objectstorage-ringbuilder.xml:83(para) +msgid "For example:" +msgstr "" + +#: ./doc/common/section_cli_glance_manage_images.xml:116(title) +msgid "Create or update an image (glance)" +msgstr "" + +#: ./doc/common/section_cli_glance_manage_images.xml:119(para) +msgid "To upload a CentOS 6.3 image in qcow2 format and configure it for public access:" +msgstr "" + +#: ./doc/common/section_cli_glance_manage_images.xml:125(para) +msgid "To update an image by name or ID:" +msgstr "" + +#: ./doc/common/section_cli_glance_manage_images.xml:126(replaceable) ./doc/common/section_cli_nova_manage_images.xml:44(replaceable) ./doc/common/section_cli_nova_images.xml:45(replaceable) +msgid "IMAGE" +msgstr "" + +#: ./doc/common/section_cli_glance_manage_images.xml:127(para) +msgid "To modify image properties, use the following optional arguments:" +msgstr "" + +#: ./doc/common/section_cli_glance_manage_images.xml:134(replaceable) ./doc/common/section_cli_nova_boot_from_volume.xml:67(replaceable) ./doc/common/section_cli_nova_boot_from_volume.xml:140(replaceable) +msgid "NAME" +msgstr "" + +#: ./doc/common/section_cli_glance_manage_images.xml:133(parameter) +msgid "--name " +msgstr "" + +#: ./doc/common/section_cli_glance_manage_images.xml:135(para) +msgid "The name of the image." +msgstr "" + +#: ./doc/common/section_cli_glance_manage_images.xml:140(replaceable) +msgid "DISK_FORMAT" +msgstr "" + +#: ./doc/common/section_cli_glance_manage_images.xml:139(parameter) +msgid "--disk-format " +msgstr "" + +#: ./doc/common/section_cli_glance_manage_images.xml:141(para) +msgid "The disk format of the image. Acceptable formats are ami, ari, aki, vhd, vmdk, raw, qcow2, vdi, and iso." +msgstr "" + +#: ./doc/common/section_cli_glance_manage_images.xml:149(replaceable) +msgid "CONTAINER_FORMAT" +msgstr "" + +#: ./doc/common/section_cli_glance_manage_images.xml:148(parameter) +msgid "--container-format " +msgstr "" + +#: ./doc/common/section_cli_glance_manage_images.xml:150(para) +msgid "The container format of the image. Acceptable formats are ami, ari, aki, bare, and ovf." +msgstr "" + +#: ./doc/common/section_cli_glance_manage_images.xml:157(replaceable) +msgid "TENANT_ID" +msgstr "" + +#: ./doc/common/section_cli_glance_manage_images.xml:156(parameter) +msgid "--owner " +msgstr "" + +#: ./doc/common/section_cli_glance_manage_images.xml:158(para) +msgid "The tenant who should own the image." +msgstr "" + +#: ./doc/common/section_cli_glance_manage_images.xml:164(replaceable) ./doc/common/section_cli_nova_boot_from_volume.xml:67(replaceable) +msgid "SIZE" +msgstr "" + +#: ./doc/common/section_cli_glance_manage_images.xml:163(parameter) +msgid "--size " +msgstr "" + +#: ./doc/common/section_cli_glance_manage_images.xml:165(para) +msgid "The size of image data, in bytes." +msgstr "" + +#: ./doc/common/section_cli_glance_manage_images.xml:171(replaceable) +msgid "DISK_GB" +msgstr "" + +#: ./doc/common/section_cli_glance_manage_images.xml:170(parameter) +msgid "--min-disk " +msgstr "" + +#: ./doc/common/section_cli_glance_manage_images.xml:172(para) +msgid "The minimum size of disk needed to boot image, in gigabytes." +msgstr "" + +#: ./doc/common/section_cli_glance_manage_images.xml:178(replaceable) +msgid "DISK_RAM" +msgstr "" + +#: ./doc/common/section_cli_glance_manage_images.xml:177(parameter) +msgid "--min-ram " +msgstr "" + +#: ./doc/common/section_cli_glance_manage_images.xml:179(para) +msgid "The minimum amount of ram needed to boot image, in megabytes." +msgstr "" + +#: ./doc/common/section_cli_glance_manage_images.xml:185(replaceable) ./doc/common/section_cli_glance_manage_images.xml:211(replaceable) +msgid "IMAGE_URL" +msgstr "" + +#: ./doc/common/section_cli_glance_manage_images.xml:184(parameter) +msgid "--location " +msgstr "" + +#: ./doc/common/section_cli_glance_manage_images.xml:186(para) +msgid "The URL where the data for this image resides. For example, if the image data is stored in swift, you could specify swift://account:key@example.com/container/obj." +msgstr "" + +#: ./doc/common/section_cli_glance_manage_images.xml:195(replaceable) +msgid "FILE" +msgstr "" + +#: ./doc/common/section_cli_glance_manage_images.xml:194(parameter) +msgid "--file " +msgstr "" + +#: ./doc/common/section_cli_glance_manage_images.xml:196(para) +msgid "Local file that contains disk image to be uploaded during update. Alternatively, you can pass images to the client through stdin." +msgstr "" + +#: ./doc/common/section_cli_glance_manage_images.xml:204(replaceable) +msgid "CHECKSUM" +msgstr "" + +#: ./doc/common/section_cli_glance_manage_images.xml:203(parameter) +msgid "--checksum " +msgstr "" + +#: ./doc/common/section_cli_glance_manage_images.xml:205(para) +msgid "Hash of image data to use for verification." +msgstr "" + +#: ./doc/common/section_cli_glance_manage_images.xml:210(parameter) +msgid "--copy-from " +msgstr "" + +#: ./doc/common/section_cli_glance_manage_images.xml:212(para) +msgid "Similar to --location in usage, but indicates that the Image server should immediately copy the data and store it in its configured image store." +msgstr "" + +#: ./doc/common/section_cli_glance_manage_images.xml:221(parameter) +msgid "--is-public [True|False]" +msgstr "" + +#: ./doc/common/section_cli_glance_manage_images.xml:223(para) +msgid "Makes an image accessible to the public." +msgstr "" + +#: ./doc/common/section_cli_glance_manage_images.xml:228(parameter) +msgid "--is-protected [True|False]" +msgstr "" + +#: ./doc/common/section_cli_glance_manage_images.xml:230(para) +msgid "Prevents an image from being deleted." +msgstr "" + +#: ./doc/common/section_cli_glance_manage_images.xml:236(replaceable) +msgid "KEY" +msgstr "" + +#: ./doc/common/section_cli_glance_manage_images.xml:236(replaceable) +msgid "VALUE" +msgstr "" + +#: ./doc/common/section_cli_glance_manage_images.xml:235(parameter) +msgid "--property =" +msgstr "" + +#: ./doc/common/section_cli_glance_manage_images.xml:237(para) +msgid "Arbitrary property to associate with image. Can be used multiple times." +msgstr "" + +#: ./doc/common/section_cli_glance_manage_images.xml:243(parameter) +msgid "--purge-props" +msgstr "" + +#: ./doc/common/section_cli_glance_manage_images.xml:244(para) +msgid "Deletes all image properties that are not explicitly set in the update request. Otherwise, those properties not referenced are preserved." +msgstr "" + +#: ./doc/common/section_cli_glance_manage_images.xml:251(parameter) +msgid "--human-readable" +msgstr "" + +#: ./doc/common/section_cli_glance_manage_images.xml:252(para) +msgid "Prints image size in a human-friendly format." +msgstr "" + +#: ./doc/common/section_cli_glance_manage_images.xml:259(para) +msgid "To annotate an image with a property that describes the disk_bus, cdrom_bus, and vif_model:" +msgstr "" + +#: ./doc/common/section_cli_glance_manage_images.xml:266(para) +msgid "Currently libvirt will determine the disk/cdrom/vif device models based on the configured hypervisor type (libvirt_type in /etc/nova/nova.conf). For the sake of optimal performance, it will default to using virtio for both disk and VIF (NIC) models. The downside of this approach is that it is not possible to run operating systems that lack virtio drivers, for example, BSD, Solaris, old Linux, and old Windows." +msgstr "" + +#: ./doc/common/section_cli_glance_manage_images.xml:273(para) +msgid "If you specify a disk or CD-ROM bus model that is not supported, see . If you specify a VIF model that is not supported, the instance fails to launch. See ." +msgstr "" + +#: ./doc/common/section_cli_glance_manage_images.xml:279(para) +msgid "The valid model values depend on the libvirt_type setting, as shown in the following tables:" +msgstr "" + +#: ./doc/common/section_cli_glance_manage_images.xml:283(caption) +msgid "Disk and CD-ROM bus model values" +msgstr "" + +#: ./doc/common/section_cli_glance_manage_images.xml:288(th) ./doc/common/section_cli_glance_manage_images.xml:335(th) +msgid "libvirt_type setting" +msgstr "" + +#: ./doc/common/section_cli_glance_manage_images.xml:289(th) ./doc/common/section_cli_glance_manage_images.xml:336(th) +msgid "Supported model values" +msgstr "" + +#: ./doc/common/section_cli_glance_manage_images.xml:294(td) ./doc/common/section_cli_glance_manage_images.xml:341(td) +msgid "qemu or kvm" +msgstr "" + +#: ./doc/common/section_cli_glance_manage_images.xml:299(para) ./doc/common/section_cli_glance_manage_images.xml:308(para) ./doc/common/section_cli_glance_manage_images.xml:346(para) +msgid "virtio" +msgstr "" + +#: ./doc/common/section_cli_glance_manage_images.xml:302(para) +msgid "scsi" +msgstr "" + +#: ./doc/common/section_cli_glance_manage_images.xml:305(para) ./doc/common/section_cli_glance_manage_images.xml:322(para) +msgid "ide" +msgstr "" + +#: ./doc/common/section_cli_glance_manage_images.xml:315(td) ./doc/common/section_cli_glance_manage_images.xml:319(para) ./doc/common/section_cli_glance_manage_images.xml:365(td) +msgid "xen" +msgstr "" + +#: ./doc/common/section_cli_glance_manage_images.xml:330(caption) +msgid "VIF model values" +msgstr "" + +#: ./doc/common/section_cli_glance_manage_images.xml:349(para) ./doc/common/section_cli_glance_manage_images.xml:372(para) +msgid "ne2k_pci" +msgstr "" + +#: ./doc/common/section_cli_glance_manage_images.xml:352(para) ./doc/common/section_cli_glance_manage_images.xml:375(para) +msgid "pcnet" +msgstr "" + +#: ./doc/common/section_cli_glance_manage_images.xml:355(para) ./doc/common/section_cli_glance_manage_images.xml:378(para) +msgid "rtl8139" +msgstr "" + +#: ./doc/common/section_cli_glance_manage_images.xml:358(para) ./doc/common/section_cli_glance_manage_images.xml:381(para) +msgid "e1000" +msgstr "" + +#: ./doc/common/section_cli_glance_manage_images.xml:369(para) +msgid "netfront" +msgstr "" + +#: ./doc/common/section_cli_glance_manage_images.xml:387(td) +msgid "vmware" +msgstr "" + +#: ./doc/common/section_cli_glance_manage_images.xml:392(para) +msgid "VirtualE1000" +msgstr "" + +#: ./doc/common/section_cli_glance_manage_images.xml:395(para) +msgid "VirtualPCNet32" +msgstr "" + +#: ./doc/common/section_cli_glance_manage_images.xml:398(para) +msgid "VirtualVmxnet" +msgstr "" + +#: ./doc/common/section_cli_glance_manage_images.xml:409(title) ./doc/common/section_cli_nova_images.xml:125(title) +msgid "Troubleshoot image creation" +msgstr "" + +#: ./doc/common/section_cli_glance_manage_images.xml:412(para) ./doc/common/section_cli_nova_manage_images.xml:12(para) ./doc/common/section_cli_nova_images.xml:12(para) ./doc/common/section_cli_nova_images.xml:128(para) +msgid "You cannot create a snapshot from an instance that has an attached volume. Detach the volume, create the image, and re-mount the volume." +msgstr "" + +#: ./doc/common/section_cli_glance_manage_images.xml:417(para) ./doc/common/section_cli_nova_images.xml:133(para) +msgid "Make sure the version of qemu you are using is version 0.14 or greater. Older versions of qemu result in an \"unknown option -s\" error message in the nova-compute.log." +msgstr "" + +#: ./doc/common/section_cli_glance_manage_images.xml:424(para) ./doc/common/section_cli_nova_images.xml:140(para) +msgid "Examine the /var/log/nova-api.log and /var/log/nova-compute.log log files for error messages." +msgstr "" + +#: ./doc/common/section_cli_nova_manage_images.xml:6(title) +msgid "Create image (nova)" +msgstr "" + +#: ./doc/common/section_cli_nova_manage_images.xml:7(para) ./doc/common/section_cli_nova_images.xml:7(para) +msgid "You can use the nova client to list images, set and delete image metadata, delete images, and take a snapshot of a running instance to create an image." +msgstr "" + +#: ./doc/common/section_cli_nova_manage_images.xml:10(para) ./doc/common/section_cli_nova_images.xml:10(para) +msgid "The safest approach is to shut down the instance before you take a snapshot." +msgstr "" + +#: ./doc/common/section_cli_nova_manage_images.xml:17(para) ./doc/common/section_cli_nova_images.xml:18(para) +msgid "Write any buffered data to disk." +msgstr "" + +#: ./doc/common/section_cli_nova_manage_images.xml:18(para) +msgid "For more information, see Taking Snapshots in the OpenStack Operations Guide." +msgstr "" + +#: ./doc/common/section_cli_nova_manage_images.xml:25(para) ./doc/common/section_cli_nova_images.xml:26(para) +msgid "To create the image, list instances to get the server ID:" +msgstr "" + +#: ./doc/common/section_cli_nova_manage_images.xml:33(para) ./doc/common/section_cli_nova_images.xml:34(para) +msgid "In this example, the server is named myCirrosServer. Use this server to create a snapshot, as follows: The command creates a qemu snapshot and automatically uploads the image to your repository. Only the tenant that creates the image has access to it." +msgstr "" + +#: ./doc/common/section_cli_nova_manage_images.xml:42(para) ./doc/common/section_cli_nova_images.xml:43(para) +msgid "Get details for your image to check its status:" +msgstr "" + +#: ./doc/common/section_cli_nova_manage_images.xml:78(para) ./doc/common/section_cli_nova_images.xml:79(para) +msgid "The image status changes from SAVING to ACTIVE. Only the tenant who creates the image has access to it." +msgstr "" + +#: ./doc/common/section_cli_nova_manage_images.xml:84(para) ./doc/common/section_cli_nova_images.xml:89(para) +msgid "To launch an instance from your image, include the image ID and flavor ID, as follows:" +msgstr "" + +#. When image changes, this message will be marked fuzzy or untranslated for you. +#. It doesn't matter what you translate it to: it's not used at all. +#: ./doc/common/section_compute-configure-vnc.xml:63(None) +msgid "@@image: '../common/figures/novnc/SCH_5009_V00_NUAC-VNC_OpenStack.png'; md5=182dc38019a220c851e1c94aa50f4565" +msgstr "" + +#: ./doc/common/section_compute-configure-vnc.xml:6(title) +msgid "VNC console proxy" +msgstr "" + +#: ./doc/common/section_compute-configure-vnc.xml:7(para) +msgid "The VNC proxy is an OpenStack component that enables compute service users to access their instances through VNC clients." +msgstr "" + +#: ./doc/common/section_compute-configure-vnc.xml:10(para) +msgid "The VNC console connection works as follows:" +msgstr "" + +#: ./doc/common/section_compute-configure-vnc.xml:13(para) +msgid "A user connects to the API and gets an access_url such as, http://ip:port/?token=xyz." +msgstr "" + +#: ./doc/common/section_compute-configure-vnc.xml:19(para) +msgid "The user pastes the URL in a browser or uses it as a client parameter." +msgstr "" + +#: ./doc/common/section_compute-configure-vnc.xml:23(para) +msgid "The browser or client connects to the proxy." +msgstr "" + +#: ./doc/common/section_compute-configure-vnc.xml:26(para) +msgid "The proxy talks to nova-consoleauth to authorize the token for the user, and maps the token to the private host and port of the VNC server for an instance." +msgstr "" + +#: ./doc/common/section_compute-configure-vnc.xml:31(para) +msgid "The compute host specifies the address that the proxy should use to connect through the nova.conf file option, . In this way, the VNC proxy works as a bridge between the public network and private host network." +msgstr "" + +#: ./doc/common/section_compute-configure-vnc.xml:39(para) +msgid "The proxy initiates the connection to VNC server and continues to proxy until the session ends." +msgstr "" + +#: ./doc/common/section_compute-configure-vnc.xml:43(para) +msgid "The proxy also tunnels the VNC protocol over WebSockets so that the noVNC client can talk VNC." +msgstr "" + +#: ./doc/common/section_compute-configure-vnc.xml:45(para) +msgid "In general, the VNC proxy:" +msgstr "" + +#: ./doc/common/section_compute-configure-vnc.xml:48(para) +msgid "Bridges between the public network where the clients live and the private network where vncservers live." +msgstr "" + +#: ./doc/common/section_compute-configure-vnc.xml:52(para) +msgid "Mediates token authentication." +msgstr "" + +#: ./doc/common/section_compute-configure-vnc.xml:55(para) +msgid "Transparently deals with hypervisor-specific connection details to provide a uniform client experience." +msgstr "" + +#: ./doc/common/section_compute-configure-vnc.xml:58(title) +msgid "noVNC process" +msgstr "" + +#: ./doc/common/section_compute-configure-vnc.xml:71(title) +msgid "About nova-consoleauth" +msgstr "" + +#: ./doc/common/section_compute-configure-vnc.xml:73(para) +msgid "Both client proxies leverage a shared service to manage token authentication called nova-consoleauth. This service must be running for either proxy to work. Many proxies of either type can be run against a single nova-consoleauth service in a cluster configuration." +msgstr "" + +#: ./doc/common/section_compute-configure-vnc.xml:80(para) +msgid "Do not confuse the nova-consoleauth shared service with nova-console, which is a XenAPI-specific service that most recent VNC proxy architectures do not use." +msgstr "" + +#: ./doc/common/section_compute-configure-vnc.xml:87(title) +msgid "Typical deployment" +msgstr "" + +#: ./doc/common/section_compute-configure-vnc.xml:88(para) +msgid "A typical deployment has the following components:" +msgstr "" + +#: ./doc/common/section_compute-configure-vnc.xml:91(para) +msgid "A nova-consoleauth process. Typically runs on the controller host." +msgstr "" + +#: ./doc/common/section_compute-configure-vnc.xml:96(para) +msgid "One or more nova-novncproxy services. Supports browser-based noVNC clients. For simple deployments, this service typically runs on the same machine as nova-api because it operates as a proxy between the public network and the private compute host network." +msgstr "" + +#: ./doc/common/section_compute-configure-vnc.xml:105(para) +msgid "One or more nova-xvpvncproxy services. Supports the special Java client discussed here. For simple deployments, this service typically runs on the same machine as nova-api because it acts as a proxy between the public network and the private compute host network." +msgstr "" + +#: ./doc/common/section_compute-configure-vnc.xml:114(para) +msgid "One or more compute hosts. These compute hosts must have correctly configured options, as follows." +msgstr "" + +#: ./doc/common/section_compute-configure-vnc.xml:120(title) +msgid "VNC configuration options" +msgstr "" + +#: ./doc/common/section_compute-configure-vnc.xml:123(para) +msgid "To support live migration, you cannot specify a specific IP address for vncserver_listen, because that IP address does not exist on the destination host." +msgstr "" + +#: ./doc/common/section_compute-configure-vnc.xml:130(para) +msgid "The vncserver_proxyclient_address defaults to 127.0.0.1, which is the address of the compute host that nova instructs proxies to use when connecting to instance servers." +msgstr "" + +#: ./doc/common/section_compute-configure-vnc.xml:134(para) +msgid "For all-in-one XenServer domU deployments, set this to 169.254.0.1." +msgstr "" + +#: ./doc/common/section_compute-configure-vnc.xml:136(para) +msgid "For multi-host XenServer domU deployments, set to a dom0 management IP on the same network as the proxies." +msgstr "" + +#: ./doc/common/section_compute-configure-vnc.xml:138(para) +msgid "For multi-host libvirt deployments, set to a host management IP on the same network as the proxies." +msgstr "" + +#: ./doc/common/section_compute-configure-vnc.xml:144(title) +msgid "nova-novncproxy (noVNC)" +msgstr "" + +#: ./doc/common/section_compute-configure-vnc.xml:146(para) +msgid "You must install the noVNC package, which contains the nova-novncproxy service." +msgstr "" + +#: ./doc/common/section_compute-configure-vnc.xml:149(para) +msgid "As root, run the following command:" +msgstr "" + +#: ./doc/common/section_compute-configure-vnc.xml:151(para) +msgid "The service starts automatically on installation." +msgstr "" + +#: ./doc/common/section_compute-configure-vnc.xml:152(para) +msgid "To restart it, run the following command:" +msgstr "" + +#: ./doc/common/section_compute-configure-vnc.xml:154(para) +msgid "The configuration option parameter should point to your nova.conf file, which includes the message queue server address and credentials." +msgstr "" + +#: ./doc/common/section_compute-configure-vnc.xml:157(para) +msgid "By default, nova-novncproxy binds on 0.0.0.0:6080." +msgstr "" + +#: ./doc/common/section_compute-configure-vnc.xml:160(para) +msgid "To connect the service to your nova deployment, add the following configuration options to your nova.conf file:" +msgstr "" + +#: ./doc/common/section_compute-configure-vnc.xml:165(para) +msgid "vncserver_listen=0.0.0.0" +msgstr "" + +#: ./doc/common/section_compute-configure-vnc.xml:168(para) +msgid "Specifies the address on which the VNC service should bind. Make sure it is assigned one of the compute node interfaces. This address is the one used by your domain file." +msgstr "" + +#: ./doc/common/section_compute-configure-vnc.xml:174(para) +msgid "To use live migration, use the 0.0.0.0 address." +msgstr "" + +#: ./doc/common/section_compute-configure-vnc.xml:179(para) +msgid "vncserver_ proxyclient_ address =127.0.0.1" +msgstr "" + +#: ./doc/common/section_compute-configure-vnc.xml:183(para) +msgid "The address of the compute host that nova instructs proxies to use when connecting to instance vncservers." +msgstr "" + +#: ./doc/common/section_compute-configure-vnc.xml:191(title) +msgid "Frequently asked questions about VNC access to virtual machines" +msgstr "" + +#: ./doc/common/section_compute-configure-vnc.xml:197(literal) +msgid "nova-xvpvncproxy" +msgstr "" + +#: ./doc/common/section_compute-configure-vnc.xml:198(systemitem) +msgid "nova-novncproxy" +msgstr "" + +#: ./doc/common/section_compute-configure-vnc.xml:196(emphasis) +msgid "Q: What is the difference between and ?" +msgstr "" + +#: ./doc/common/section_compute-configure-vnc.xml:200(para) +msgid "A: nova-xvpvncproxy, which ships with nova, is a proxy that supports a simple Java client. nova-novncproxy uses noVNC to provide VNC support through a web browser." +msgstr "" + +#: ./doc/common/section_compute-configure-vnc.xml:207(emphasis) +msgid "Q: I want VNC support in the Dashboard. What services do I need?" +msgstr "" + +#: ./doc/common/section_compute-configure-vnc.xml:209(para) +msgid "A: You need nova-novncproxy, nova-consoleauth, and correctly configured compute hosts." +msgstr "" + +#: ./doc/common/section_compute-configure-vnc.xml:215(emphasis) +msgid "Q: When I use or click on the VNC tab of the Dashboard, it hangs. Why?" +msgstr "" + +#: ./doc/common/section_compute-configure-vnc.xml:218(para) +msgid "A: Make sure you are running nova-consoleauth (in addition to nova-novncproxy). The proxies rely on nova-consoleauth to validate tokens, and waits for a reply from them until a timeout is reached." +msgstr "" + +#: ./doc/common/section_compute-configure-vnc.xml:227(emphasis) +msgid "Q: My VNC proxy worked fine during my all-in-one test, but now it doesn't work on multi host. Why?" +msgstr "" + +#: ./doc/common/section_compute-configure-vnc.xml:230(para) +msgid "A: The default options work for an all-in-one install, but changes must be made on your compute hosts once you start to build a cluster. As an example, suppose you have two servers:" +msgstr "" + +#: ./doc/common/section_compute-configure-vnc.xml:236(para) +msgid "Your nova-compute configuration file must set the following values:" +msgstr "" + +#: ./doc/common/section_compute-configure-vnc.xml:248(para) +msgid "novncproxy_base_url and xvpvncproxy_base_url use a public IP; this is the URL that is ultimately returned to clients, which generally do not have access to your private network. Your PROXYSERVER must be able to reach vncserver_proxyclient_address, because that is the address over which the VNC connection is proxied." +msgstr "" + +#: ./doc/common/section_compute-configure-vnc.xml:260(emphasis) +msgid "Q: My noVNC does not work with recent versions of web browsers. Why?" +msgstr "" + +#: ./doc/common/section_compute-configure-vnc.xml:263(para) +msgid "A: Make sure you have installed python-numpy, which is required to support a newer version of the WebSocket protocol (HyBi-07+)." +msgstr "" + +#: ./doc/common/section_compute-configure-vnc.xml:270(emphasis) +msgid "Q: How do I adjust the dimensions of the VNC window image in the OpenStack dashboard?" +msgstr "" + +#: ./doc/common/section_compute-configure-vnc.xml:273(para) +msgid "A: These values are hard-coded in a Django HTML template. To alter them, edit the _detail_vnc.html template file. The location of this file varies based on Linux distribution. On Ubuntu 12.04, the file is at /usr/share/pyshared/horizon/dashboards/nova/instances/templates/instances/_detail_vnc.html." +msgstr "" + +#: ./doc/common/section_compute-configure-vnc.xml:279(para) +msgid "Modify the and options, as follows:" +msgstr "" + +#: ./doc/common/section_cli_cinder_commands.xml:11(title) +msgid "cinder commands" +msgstr "" + +#: ./doc/common/section_cli_cinder_commands.xml:12(para) +msgid "The cinder client is the command-line interface (CLI) for the OpenStack Block Storage API and its extensions." +msgstr "" + +#: ./doc/common/section_cli_cinder_commands.xml:14(para) ./doc/common/section_cli_keystone_commands.xml:14(para) ./doc/common/section_cli_ceilometer_commands.xml:14(para) ./doc/common/section_cli_swift_commands.xml:14(para) ./doc/common/section_cli_neutron_commands.xml:14(para) ./doc/common/section_cli_heat_commands.xml:14(para) ./doc/common/section_cli_nova_commands.xml:14(para) ./doc/common/section_cli_glance_commands.xml:14(para) +msgid "For help on a specific command, enter:" +msgstr "" + +#: ./doc/common/section_cli_cinder_commands.xml:17(option) ./doc/common/section_cli_keystone_commands.xml:17(option) ./doc/common/section_cli_ceilometer_commands.xml:17(option) ./doc/common/section_cli_swift_commands.xml:17(option) ./doc/common/section_cli_neutron_commands.xml:17(option) ./doc/common/section_cli_heat_commands.xml:17(option) ./doc/common/section_cli_nova_commands.xml:17(option) ./doc/common/section_cli_glance_commands.xml:17(option) +msgid "help" +msgstr "" + +#: ./doc/common/section_cli_cinder_commands.xml:17(replaceable) ./doc/common/section_cli_keystone_commands.xml:17(replaceable) ./doc/common/section_cli_ceilometer_commands.xml:17(replaceable) ./doc/common/section_cli_swift_commands.xml:17(replaceable) ./doc/common/section_cli_neutron_commands.xml:17(replaceable) ./doc/common/section_cli_keystone_example_usage.xml:12(replaceable) ./doc/common/section_cli_heat_commands.xml:17(replaceable) ./doc/common/section_cli_nova_commands.xml:17(replaceable) ./doc/common/section_cli_glance_commands.xml:17(replaceable) +msgid "COMMAND" +msgstr "" + +#: ./doc/common/section_cli_cinder_commands.xml:20(title) +msgid "cinder usage" +msgstr "" + +#: ./doc/common/section_cli_cinder_commands.xml:33(title) +msgid "cinder positional arguments" +msgstr "" + +#: ./doc/common/section_cli_cinder_commands.xml:124(title) +msgid "cinder optional arguments" +msgstr "" + +#: ./doc/common/section_cli_cinder_commands.xml:156(title) +msgid "cinder absolute-limits command" +msgstr "" + +#: ./doc/common/section_cli_cinder_commands.xml:164(title) +msgid "cinder availability-zone-list command" +msgstr "" + +#: ./doc/common/section_cli_cinder_commands.xml:172(title) +msgid "cinder backup-create command" +msgstr "" + +#: ./doc/common/section_cli_cinder_commands.xml:194(title) +msgid "cinder backup-delete command" +msgstr "" + +#: ./doc/common/section_cli_cinder_commands.xml:205(title) +msgid "cinder backup-list command" +msgstr "" + +#: ./doc/common/section_cli_cinder_commands.xml:213(title) +msgid "cinder backup-restore command" +msgstr "" + +#: ./doc/common/section_cli_cinder_commands.xml:227(title) +msgid "cinder backup-show command" +msgstr "" + +#: ./doc/common/section_cli_cinder_commands.xml:238(title) +msgid "cinder create command" +msgstr "" + +#: ./doc/common/section_cli_cinder_commands.xml:275(title) +msgid "cinder credentials command" +msgstr "" + +#: ./doc/common/section_cli_cinder_commands.xml:283(title) +msgid "cinder delete command" +msgstr "" + +#: ./doc/common/section_cli_cinder_commands.xml:294(title) +msgid "cinder encryption-type-create command" +msgstr "" + +#: ./doc/common/section_cli_cinder_commands.xml:321(title) +msgid "cinder encryption-type-list command" +msgstr "" + +#: ./doc/common/section_cli_cinder_commands.xml:329(title) +msgid "cinder encryption-type-show command" +msgstr "" + +#: ./doc/common/section_cli_cinder_commands.xml:340(title) +msgid "cinder endpoints command" +msgstr "" + +#: ./doc/common/section_cli_cinder_commands.xml:348(title) +msgid "cinder extend command" +msgstr "" + +#: ./doc/common/section_cli_cinder_commands.xml:360(title) +msgid "cinder extra-specs-list command" +msgstr "" + +#: ./doc/common/section_cli_cinder_commands.xml:368(title) +msgid "cinder force-delete command" +msgstr "" + +#: ./doc/common/section_cli_cinder_commands.xml:379(title) +msgid "cinder list command" +msgstr "" + +#: ./doc/common/section_cli_cinder_commands.xml:398(title) +msgid "cinder list-extensions command" +msgstr "" + +#: ./doc/common/section_cli_cinder_commands.xml:406(title) +msgid "cinder metadata command" +msgstr "" + +#: ./doc/common/section_cli_cinder_commands.xml:419(title) +msgid "cinder metadata-show command" +msgstr "" + +#: ./doc/common/section_cli_cinder_commands.xml:430(title) +msgid "cinder metadata-update-all command" +msgstr "" + +#: ./doc/common/section_cli_cinder_commands.xml:442(title) +msgid "cinder migrate command" +msgstr "" + +#: ./doc/common/section_cli_cinder_commands.xml:460(title) +msgid "cinder qos-associate command" +msgstr "" + +#: ./doc/common/section_cli_cinder_commands.xml:472(title) +msgid "cinder qos-create command" +msgstr "" + +#: ./doc/common/section_cli_cinder_commands.xml:484(title) +msgid "cinder qos-delete command" +msgstr "" + +#: ./doc/common/section_cli_cinder_commands.xml:499(title) +msgid "cinder qos-disassociate command" +msgstr "" + +#: ./doc/common/section_cli_cinder_commands.xml:511(title) +msgid "cinder qos-disassociate-all command" +msgstr "" + +#: ./doc/common/section_cli_cinder_commands.xml:522(title) +msgid "cinder qos-get-association command" +msgstr "" + +#: ./doc/common/section_cli_cinder_commands.xml:533(title) +msgid "cinder qos-key command" +msgstr "" + +#: ./doc/common/section_cli_cinder_commands.xml:546(title) +msgid "cinder qos-list command" +msgstr "" + +#: ./doc/common/section_cli_cinder_commands.xml:554(title) +msgid "cinder qos-show command" +msgstr "" + +#: ./doc/common/section_cli_cinder_commands.xml:565(title) +msgid "cinder quota-class-show command" +msgstr "" + +#: ./doc/common/section_cli_cinder_commands.xml:576(title) +msgid "cinder quota-class-update command" +msgstr "" + +#: ./doc/common/section_cli_cinder_commands.xml:600(title) +msgid "cinder quota-defaults command" +msgstr "" + +#: ./doc/common/section_cli_cinder_commands.xml:611(title) +msgid "cinder quota-show command" +msgstr "" + +#: ./doc/common/section_cli_cinder_commands.xml:622(title) +msgid "cinder quota-update command" +msgstr "" + +#: ./doc/common/section_cli_cinder_commands.xml:645(title) +msgid "cinder quota-usage command" +msgstr "" + +#: ./doc/common/section_cli_cinder_commands.xml:656(title) +msgid "cinder rate-limits command" +msgstr "" + +#: ./doc/common/section_cli_cinder_commands.xml:664(title) +msgid "cinder readonly-mode-update command" +msgstr "" + +#: ./doc/common/section_cli_cinder_commands.xml:678(title) +msgid "cinder rename command" +msgstr "" + +#: ./doc/common/section_cli_cinder_commands.xml:695(title) +msgid "cinder reset-state command" +msgstr "" + +#: ./doc/common/section_cli_cinder_commands.xml:711(title) +msgid "cinder service-disable command" +msgstr "" + +#: ./doc/common/section_cli_cinder_commands.xml:723(title) +msgid "cinder service-enable command" +msgstr "" + +#: ./doc/common/section_cli_cinder_commands.xml:735(title) +msgid "cinder service-list command" +msgstr "" + +#: ./doc/common/section_cli_cinder_commands.xml:747(title) +msgid "cinder show command" +msgstr "" + +#: ./doc/common/section_cli_cinder_commands.xml:758(title) +msgid "cinder snapshot-create command" +msgstr "" + +#: ./doc/common/section_cli_cinder_commands.xml:780(title) +msgid "cinder snapshot-delete command" +msgstr "" + +#: ./doc/common/section_cli_cinder_commands.xml:791(title) +msgid "cinder snapshot-list command" +msgstr "" + +#: ./doc/common/section_cli_cinder_commands.xml:810(title) +msgid "cinder snapshot-metadata command" +msgstr "" + +#: ./doc/common/section_cli_cinder_commands.xml:824(title) +msgid "cinder snapshot-metadata-show command" +msgstr "" + +#: ./doc/common/section_cli_cinder_commands.xml:835(title) +msgid "cinder snapshot-metadata-update-all command" +msgstr "" + +#: ./doc/common/section_cli_cinder_commands.xml:848(title) +msgid "cinder snapshot-rename command" +msgstr "" + +#: ./doc/common/section_cli_cinder_commands.xml:865(title) +msgid "cinder snapshot-reset-state command" +msgstr "" + +#: ./doc/common/section_cli_cinder_commands.xml:883(title) +msgid "cinder snapshot-show command" +msgstr "" + +#: ./doc/common/section_cli_cinder_commands.xml:894(title) +msgid "cinder transfer-accept command" +msgstr "" + +#: ./doc/common/section_cli_cinder_commands.xml:906(title) +msgid "cinder transfer-create command" +msgstr "" + +#: ./doc/common/section_cli_cinder_commands.xml:921(title) +msgid "cinder transfer-delete command" +msgstr "" + +#: ./doc/common/section_cli_cinder_commands.xml:932(title) +msgid "cinder transfer-list command" +msgstr "" + +#: ./doc/common/section_cli_cinder_commands.xml:940(title) +msgid "cinder transfer-show command" +msgstr "" + +#: ./doc/common/section_cli_cinder_commands.xml:951(title) +msgid "cinder type-create command" +msgstr "" + +#: ./doc/common/section_cli_cinder_commands.xml:962(title) +msgid "cinder type-delete command" +msgstr "" + +#: ./doc/common/section_cli_cinder_commands.xml:973(title) +msgid "cinder type-key command" +msgstr "" + +#: ./doc/common/section_cli_cinder_commands.xml:986(title) +msgid "cinder type-list command" +msgstr "" + +#: ./doc/common/section_cli_cinder_commands.xml:994(title) +msgid "cinder upload-to-image command" +msgstr "" + +#: ./doc/common/section_cli_nova_resizerebuild.xml:6(title) +msgid "Change the size of your server" +msgstr "" + +#: ./doc/common/section_cli_nova_resizerebuild.xml:7(para) +msgid "You change the size of a server by changing its flavor." +msgstr "" + +#: ./doc/common/section_cli_nova_resizerebuild.xml:10(para) ./doc/common/section_cli_nova_boot.xml:102(para) +msgid "List the available flavors:" +msgstr "" + +#: ./doc/common/section_cli_nova_resizerebuild.xml:23(para) +msgid "Show information about your server, including its size:" +msgstr "" + +#: ./doc/common/section_cli_nova_resizerebuild.xml:57(para) +msgid "The size of the server is m1.small (2)." +msgstr "" + +#: ./doc/common/section_cli_nova_resizerebuild.xml:61(para) +msgid "To resize the server, pass the server ID and the desired flavor to the nova command. Include the --poll parameter to report the resize progress." +msgstr "" + +#: ./doc/common/section_cli_nova_resizerebuild.xml:70(para) +msgid "Show the status for your server:" +msgstr "" + +#: ./doc/common/section_cli_nova_resizerebuild.xml:79(para) +msgid "When the resize completes, the status becomes VERIFY_RESIZE. To confirm the resize:" +msgstr "" + +#: ./doc/common/section_cli_nova_resizerebuild.xml:83(para) ./doc/common/section_cli_nova_resizerebuild.xml:89(para) +msgid "The server status becomes ACTIVE." +msgstr "" + +#: ./doc/common/section_cli_nova_resizerebuild.xml:86(para) +msgid "If the resize fails or does not work as expected, you can revert the resize:" +msgstr "" + +#. When image changes, this message will be marked fuzzy or untranslated for you. +#. It doesn't matter what you translate it to: it's not used at all. +#: ./doc/common/section_getstart_dashboard.xml:14(None) +msgid "@@image: 'figures/horizon-screenshot.jpg'; md5=9471047adf0d93713be7f54b9db2b53c" +msgstr "" + +#: ./doc/common/section_getstart_dashboard.xml:5(title) ./doc/common/ch_getstart.xml:36(link) +msgid "Dashboard" +msgstr "" + +#: ./doc/common/section_getstart_dashboard.xml:6(para) +msgid "The dashboard is a modular Django web application that provides a graphical interface to OpenStack services." +msgstr "" + +#: ./doc/common/section_getstart_dashboard.xml:18(para) +msgid "The dashboard is usually deployed through mod_wsgi in Apache. You can modify the dashboard code to make it suitable for different sites." +msgstr "" + +#: ./doc/common/section_getstart_dashboard.xml:22(para) +msgid "From a network architecture point of view, this service must be accessible to customers and the public API for each OpenStack service. To use the administrator functionality for other services, it must also connect to Admin API endpoints, which should not be accessible by customers." +msgstr "" + +#: ./doc/common/section_cli_nova_quotas.xml:13(title) +msgid "Manage Compute service quotas" +msgstr "" + +#: ./doc/common/section_cli_nova_quotas.xml:14(para) +msgid "As an administrative user, you can use the commands, which are provided by the python-novaclient package, to update the Compute Service quotas for a specific tenant or tenant user, as well as update the quota defaults for a new tenant." +msgstr "" + +#: ./doc/common/section_cli_nova_quotas.xml:19(caption) +msgid "Compute Quota Descriptions" +msgstr "" + +#: ./doc/common/section_cli_nova_quotas.xml:24(td) +msgid "Quota Name" +msgstr "" + +#: ./doc/common/section_cli_nova_quotas.xml:27(td) ./doc/common/section_cli_nova_boot_from_volume.xml:73(th) ./doc/common/ch_getstart.xml:29(th) ./doc/common/section_cli_nova_customize_flavors.xml:35(td) ./doc/common/section_identity-configure.xml:27(td) ./doc/common/section_cli_install.xml:32(th) ./doc/common/tables/nova-cells.xml:14(th) ./doc/common/tables/glance-policy.xml:14(th) ./doc/common/tables/neutron-mlnx.xml:14(th) ./doc/common/tables/nova-ipv6.xml:14(th) ./doc/common/tables/cinder-eqlx.xml:14(th) ./doc/common/tables/swift-object-expirer-filter-catch_errors.xml:13(th) ./doc/common/tables/swift-object-expirer-filter-cache.xml:13(th) ./doc/common/tables/cinder-netapp_cdot_extraspecs.xml:12(th) ./doc/common/tables/swift-proxy-server-filter-cache.xml:13(th) ./doc/common/tables/neutron-ml2_l2pop.xml:14(th) ./doc/common/tables/glance-qpid.xml:14(th) ./doc/common/tables/swift-container-server-DEFAULT.xml:13(th) ./doc/common/tables/nova-volumes.xml:14(th) ./doc/common/tables/glance-gridfs.xml:14(th) ./doc/common/tables/neutron-ml2_arista.xml:14(th) ./doc/common/tables/glance-filesystem.xml:14(th) ./doc/common/tables/swift-container-server-container-updater.xml:13(th) ./doc/common/tables/cinder-storage_gpfs.xml:14(th) ./doc/common/tables/nova-docker.xml:14(th) ./doc/common/tables/cinder-nexenta_iscsi.xml:14(th) ./doc/common/tables/nova-tilera.xml:14(th) ./doc/common/tables/nova-ca.xml:14(th) ./doc/common/tables/swift-account-server-filter-recon.xml:13(th) ./doc/common/tables/cinder-huawei.xml:14(th) ./doc/common/tables/swift-container-server-container-replicator.xml:13(th) ./doc/common/tables/nova-glance.xml:14(th) ./doc/common/tables/nova-neutron.xml:14(th) ./doc/common/tables/cinder-backups_ceph.xml:14(th) ./doc/common/tables/swift-proxy-server-filter-name_check.xml:13(th) ./doc/common/tables/nova-metadata.xml:14(th) ./doc/common/tables/glance-s3.xml:14(th) ./doc/common/tables/neutron-kombu.xml:14(th) ./doc/common/tables/swift-proxy-server-filter-ratelimit.xml:13(th) ./doc/common/tables/cinder-block-device.xml:14(th) ./doc/common/tables/cinder-zones.xml:14(th) ./doc/common/tables/cinder-netapp_7mode_iscsi.xml:14(th) ./doc/common/tables/swift-container-server-container-sync.xml:13(th) ./doc/common/tables/neutron-common.xml:14(th) ./doc/common/tables/swift-object-server-object-auditor.xml:13(th) ./doc/common/tables/neutron-openvswitch_agent.xml:14(th) ./doc/common/tables/cinder-compute.xml:14(th) ./doc/common/tables/cinder-lvm.xml:14(th) ./doc/common/tables/cinder-storage_nfs.xml:14(th) ./doc/common/tables/neutron-plumgrid.xml:14(th) ./doc/common/tables/nova-hypervisor.xml:14(th) ./doc/common/tables/swift-proxy-server-filter-tempurl.xml:13(th) ./doc/common/tables/cinder-quota.xml:14(th) ./doc/common/tables/swift-proxy-server-filter-healthcheck.xml:13(th) ./doc/common/tables/swift-object-expirer-DEFAULT.xml:13(th) ./doc/common/tables/nova-console.xml:14(th) ./doc/common/tables/swift-swift-bench-bench.xml:13(th) ./doc/common/tables/nova-common.xml:14(th) ./doc/common/tables/swift-object-server-object-updater.xml:13(th) ./doc/common/tables/glance-zmq.xml:14(th) ./doc/common/tables/swift-proxy-server-filter-account-quotas.xml:13(th) ./doc/common/tables/swift-proxy-server-app-proxy-server.xml:13(th) ./doc/common/tables/nova-keymgr.xml:14(th) ./doc/common/tables/neutron-api.xml:14(th) ./doc/common/tables/nova-testing.xml:14(th) ./doc/common/tables/cinder-backups.xml:14(th) ./doc/common/tables/swift-container-server-pipeline-main.xml:13(th) ./doc/common/tables/swift-rsyncd-object.xml:13(th) ./doc/common/tables/nova-s3.xml:14(th) ./doc/common/tables/neutron-openvswitch.xml:14(th) ./doc/common/tables/nova-zookeeper.xml:14(th) ./doc/common/tables/cinder-rpc.xml:14(th) ./doc/common/tables/cinder-api.xml:14(th) ./doc/common/tables/cinder-windows.xml:14(th) ./doc/common/tables/swift-object-server-pipeline-main.xml:13(th) ./doc/common/tables/cinder-san.xml:14(th) ./doc/common/tables/swift-account-server-app-account-server.xml:13(th) ./doc/common/tables/cinder-keymgr.xml:14(th) ./doc/common/tables/nova-db.xml:14(th) ./doc/common/tables/neutron-ml2_vxlan.xml:14(th) ./doc/common/tables/glance-logging.xml:14(th) ./doc/common/tables/glance-wsgi.xml:14(th) ./doc/common/tables/nova-periodic.xml:14(th) ./doc/common/tables/swift-account-server-filter-healthcheck.xml:13(th) ./doc/common/tables/cinder-images.xml:14(th) ./doc/common/tables/swift-container-server-app-container-server.xml:13(th) ./doc/common/tables/swift-proxy-server-filter-slo.xml:13(th) ./doc/common/tables/neutron-wsgi.xml:14(th) ./doc/common/tables/neutron-scheduler.xml:14(th) ./doc/common/tables/glance-rbd.xml:14(th) ./doc/common/tables/neutron-metadata.xml:14(th) ./doc/common/tables/cinder-hp3par.xml:14(th) ./doc/common/tables/cinder-storage_ceph.xml:14(th) ./doc/common/tables/nova-livemigration.xml:14(th) ./doc/common/tables/nova-ldap.xml:14(th) ./doc/common/tables/nova-fping.xml:14(th) ./doc/common/tables/neutron-securitygroups.xml:14(th) ./doc/common/tables/cinder-netapp_cdot_iscsi.xml:14(th) ./doc/common/tables/nova-ec2.xml:14(th) ./doc/common/tables/swift-account-server-account-auditor.xml:13(th) ./doc/common/tables/swift-object-server-DEFAULT.xml:13(th) ./doc/common/tables/cinder-nexenta_nfs.xml:14(th) ./doc/common/tables/swift-proxy-server-filter-bulk.xml:13(th) ./doc/common/tables/nova-policy.xml:14(th) ./doc/common/tables/neutron-logging.xml:14(th) ./doc/common/tables/glance-rpc.xml:14(th) ./doc/common/tables/nova-authentication.xml:14(th) ./doc/common/tables/cinder-vmware.xml:14(th) ./doc/common/tables/glance-sheepdog.xml:14(th) ./doc/common/tables/neutron-qpid.xml:14(th) ./doc/common/tables/neutron-hyperv_agent.xml:14(th) ./doc/common/tables/glance-swift.xml:14(th) ./doc/common/tables/swift-account-server-DEFAULT.xml:13(th) ./doc/common/tables/neutron-bigswitch.xml:14(th) ./doc/common/tables/nova-libvirt.xml:14(th) ./doc/common/tables/neutron-lbaas.xml:14(th) ./doc/common/tables/cinder-backups_swift.xml:14(th) ./doc/common/tables/neutron-ml2_cisco.xml:14(th) ./doc/common/tables/nova-pci.xml:14(th) ./doc/common/tables/swift-proxy-server-filter-proxy-logging.xml:13(th) ./doc/common/tables/neutron-varmour.xml:14(th) ./doc/common/tables/glance-imagecache.xml:14(th) ./doc/common/tables/swift-rsyncd-account.xml:13(th) ./doc/common/tables/cinder-storage.xml:14(th) ./doc/common/tables/nova-vpn.xml:14(th) ./doc/common/tables/nova-wsgi.xml:14(th) ./doc/common/tables/cinder-storage_glusterfs.xml:14(th) ./doc/common/tables/swift-container-server-filter-healthcheck.xml:13(th) ./doc/common/tables/nova-availabilityzones.xml:14(th) ./doc/common/tables/nova-vnc.xml:14(th) ./doc/common/tables/swift-swift-swift-constraints.xml:13(th) ./doc/common/tables/neutron-cisco.xml:14(th) ./doc/common/tables/nova-hyperv.xml:14(th) ./doc/common/tables/swift-object-server-filter-recon.xml:13(th) ./doc/common/tables/cinder-coraid.xml:14(th) ./doc/common/tables/swift-container-server-container-auditor.xml:13(th) ./doc/common/tables/swift-proxy-server-filter-catch_errors.xml:13(th) ./doc/common/tables/nova-vmware.xml:14(th) ./doc/common/tables/nova-logging.xml:14(th) ./doc/common/tables/nova-xen.xml:14(th) ./doc/common/tables/swift-proxy-server-filter-list-endpoints.xml:13(th) ./doc/common/tables/neutron-nicira.xml:14(th) ./doc/common/tables/swift-memcache-memcache.xml:13(th) ./doc/common/tables/swift-proxy-server-filter-keystoneauth.xml:13(th) ./doc/common/tables/neutron-ml2.xml:14(th) ./doc/common/tables/neutron-linuxbridge.xml:14(th) ./doc/common/tables/cinder-netapp_7mode_nfs.xml:14(th) ./doc/common/tables/glance-common.xml:14(th) ./doc/common/tables/nova-network.xml:14(th) ./doc/common/tables/cinder-scality.xml:14(th) ./doc/common/tables/neutron-notifier.xml:14(th) ./doc/common/tables/cinder-common.xml:14(th) ./doc/common/tables/nova-trustedcomputing.xml:14(th) ./doc/common/tables/neutron-ml2_flat.xml:14(th) ./doc/common/tables/nova-configdrive.xml:14(th) ./doc/common/tables/cinder-database.xml:14(th) ./doc/common/tables/neutron-rpc.xml:14(th) ./doc/common/tables/nova-zeromq.xml:14(th) ./doc/common/tables/glance-testing.xml:14(th) ./doc/common/tables/swift-proxy-server-filter-tempauth.xml:13(th) ./doc/common/tables/glance-registry.xml:14(th) ./doc/common/tables/swift-object-server-object-replicator.xml:13(th) ./doc/common/tables/swift-dispersion-dispersion.xml:13(th) ./doc/common/tables/swift-account-server-account-replicator.xml:13(th) ./doc/common/tables/neutron-fwaas.xml:14(th) ./doc/common/tables/glance-rabbitmq.xml:14(th) ./doc/common/tables/cinder-backups_tsm.xml:14(th) ./doc/common/tables/nova-qpid.xml:14(th) ./doc/common/tables/cinder-connection.xml:14(th) ./doc/common/tables/swift-proxy-server-filter-authtoken.xml:13(th) ./doc/common/tables/neutron-zeromq.xml:14(th) ./doc/common/tables/neutron-vpn.xml:14(th) ./doc/common/tables/cinder-log.xml:14(th) ./doc/common/tables/neutron-agent.xml:14(th) ./doc/common/tables/neutron-ryu.xml:14(th) ./doc/common/tables/swift-object-server-app-object-server.xml:13(th) ./doc/common/tables/neutron-policy.xml:14(th) ./doc/common/tables/swift-proxy-server-DEFAULT.xml:13(th) ./doc/common/tables/swift-proxy-server-filter-staticweb.xml:13(th) ./doc/common/tables/swift-object-expirer-app-proxy-server.xml:13(th) ./doc/common/tables/neutron-meta.xml:14(th) ./doc/common/tables/neutron-ssl.xml:14(th) ./doc/common/tables/nova-scheduling.xml:14(th) ./doc/common/tables/swift-drive-audit-drive-audit.xml:13(th) ./doc/common/tables/swift-container-server-filter-recon.xml:13(th) ./doc/common/tables/neutron-db.xml:14(th) ./doc/common/tables/neutron-brocade.xml:14(th) ./doc/common/tables/swift-object-expirer-pipeline-main.xml:13(th) ./doc/common/tables/neutron-linuxbridge_agent.xml:14(th) ./doc/common/tables/cinder-xiv.xml:14(th) ./doc/common/tables/neutron-rabbitmq.xml:14(th) ./doc/common/tables/swift-proxy-server-filter-container-quotas.xml:13(th) ./doc/common/tables/swift-swift-swift-hash.xml:13(th) ./doc/common/tables/cinder-auth.xml:14(th) ./doc/common/tables/nova-kombu.xml:14(th) ./doc/common/tables/swift-proxy-server-filter-formpost.xml:13(th) ./doc/common/tables/cinder-hds.xml:14(th) ./doc/common/tables/nova-spice.xml:14(th) ./doc/common/tables/neutron-midonet.xml:14(th) ./doc/common/tables/cinder-storwize.xml:14(th) ./doc/common/tables/cinder-solidfire.xml:14(th) ./doc/common/tables/glance-ssl.xml:14(th) ./doc/common/tables/nova-apiv3.xml:14(th) ./doc/common/tables/glance-db.xml:14(th) ./doc/common/tables/nova-api.xml:14(th) ./doc/common/tables/swift-rsyncd-container.xml:13(th) ./doc/common/tables/cinder-san-solaris.xml:14(th) ./doc/common/tables/cinder-netapp_cdot_nfs.xml:14(th) ./doc/common/tables/swift-object-server-filter-healthcheck.xml:13(th) ./doc/common/tables/glance-paste.xml:14(th) ./doc/common/tables/neutron-quotas.xml:14(th) ./doc/common/tables/nova-rpc.xml:14(th) ./doc/common/tables/nova-baremetal.xml:14(th) ./doc/common/tables/swift-account-server-pipeline-main.xml:13(th) ./doc/common/tables/glance-api.xml:14(th) ./doc/common/tables/cinder-scheduler.xml:14(th) ./doc/common/tables/neutron-ml2_ncs.xml:14(th) ./doc/common/tables/neutron-nec.xml:14(th) ./doc/common/tables/neutron-testing.xml:14(th) ./doc/common/tables/swift-object-expirer-object-expirer.xml:13(th) ./doc/common/tables/glance-cinder.xml:14(th) ./doc/common/tables/nova-redis.xml:14(th) ./doc/common/tables/neutron-embrane.xml:14(th) ./doc/common/tables/swift-proxy-server-pipeline-main.xml:13(th) ./doc/common/tables/nova-upgrade_levels.xml:14(th) ./doc/common/tables/swift-proxy-server-filter-cname_lookup.xml:13(th) ./doc/common/tables/nova-rabbitmq.xml:14(th) ./doc/common/tables/cinder-zadara.xml:14(th) ./doc/common/tables/swift-account-server-account-reaper.xml:13(th) ./doc/common/tables/nova-quota.xml:14(th) ./doc/common/tables/nova-conductor.xml:14(th) ./doc/common/tables/nova-compute.xml:14(th) ./doc/common/tables/swift-proxy-server-filter-domain_remap.xml:13(th) ./doc/common/tables/neutron-hyperv.xml:14(th) ./doc/common/tables/cinder-storage_xen.xml:14(th) ./doc/common/tables/nova-xvpnvncproxy.xml:14(th) +msgid "Description" +msgstr "" + +#: ./doc/common/section_cli_nova_quotas.xml:36(systemitem) +msgid "cores" +msgstr "" + +#: ./doc/common/section_cli_nova_quotas.xml:40(para) +msgid "Number of instance cores (VCPUs) allowed per tenant." +msgstr "" + +#: ./doc/common/section_cli_nova_quotas.xml:48(systemitem) +msgid "fixed-ips" +msgstr "" + +#: ./doc/common/section_cli_nova_quotas.xml:52(para) +msgid "Number of fixed IP addresses allowed per tenant. This number must be equal to or greater than the number of allowed instances." +msgstr "" + +#: ./doc/common/section_cli_nova_quotas.xml:62(systemitem) +msgid "floating-ips" +msgstr "" + +#: ./doc/common/section_cli_nova_quotas.xml:66(para) +msgid "Number of floating IP addresses allowed per tenant." +msgstr "" + +#: ./doc/common/section_cli_nova_quotas.xml:74(systemitem) +msgid "injected-file-content-bytes" +msgstr "" + +#: ./doc/common/section_cli_nova_quotas.xml:78(para) +msgid "Number of content bytes allowed per injected file." +msgstr "" + +#: ./doc/common/section_cli_nova_quotas.xml:86(systemitem) +msgid "injected-file-path-bytes" +msgstr "" + +#: ./doc/common/section_cli_nova_quotas.xml:90(para) +msgid "Number of bytes allowed per injected file path." +msgstr "" + +#: ./doc/common/section_cli_nova_quotas.xml:98(systemitem) +msgid "injected-files" +msgstr "" + +#: ./doc/common/section_cli_nova_quotas.xml:102(para) +msgid "Number of injected files allowed per tenant." +msgstr "" + +#: ./doc/common/section_cli_nova_quotas.xml:111(systemitem) +msgid "instances" +msgstr "" + +#: ./doc/common/section_cli_nova_quotas.xml:115(para) +msgid "Number of instances allowed per tenant." +msgstr "" + +#: ./doc/common/section_cli_nova_quotas.xml:123(systemitem) +msgid "key-pairs" +msgstr "" + +#: ./doc/common/section_cli_nova_quotas.xml:127(para) +msgid "Number of key pairs allowed per user." +msgstr "" + +#: ./doc/common/section_cli_nova_quotas.xml:135(systemitem) +msgid "metadata-items" +msgstr "" + +#: ./doc/common/section_cli_nova_quotas.xml:139(para) +msgid "Number of metadata items allowed per instance." +msgstr "" + +#: ./doc/common/section_cli_nova_quotas.xml:147(systemitem) +msgid "ram" +msgstr "" + +#: ./doc/common/section_cli_nova_quotas.xml:151(para) +msgid "Megabytes of instance ram allowed per tenant." +msgstr "" + +#: ./doc/common/section_cli_nova_quotas.xml:159(systemitem) +msgid "security-groups" +msgstr "" + +#: ./doc/common/section_cli_nova_quotas.xml:163(para) +msgid "Number of security groups per tenant." +msgstr "" + +#: ./doc/common/section_cli_nova_quotas.xml:171(systemitem) +msgid "security-group-rules" +msgstr "" + +#: ./doc/common/section_cli_nova_quotas.xml:175(para) +msgid "Number of rules per security group." +msgstr "" + +#: ./doc/common/section_cli_nova_quotas.xml:184(title) +msgid "View and update Compute quotas for a tenant (project)" +msgstr "" + +#: ./doc/common/section_cli_nova_quotas.xml:186(title) +msgid "To view and update default quota values" +msgstr "" + +#: ./doc/common/section_cli_nova_quotas.xml:188(para) +msgid "List all default quotas for all tenants, as follows:" +msgstr "" + +#: ./doc/common/section_cli_nova_quotas.xml:211(para) +msgid "Update a default value for a new tenant, as follows:" +msgstr "" + +#: ./doc/common/section_cli_nova_quotas.xml:213(replaceable) +msgid "key" +msgstr "" + +#: ./doc/common/section_cli_nova_quotas.xml:213(replaceable) +msgid "value" +msgstr "" + +#: ./doc/common/section_cli_nova_quotas.xml:220(title) +msgid "To view quota values for an existing tenant (project)" +msgstr "" + +#: ./doc/common/section_cli_nova_quotas.xml:221(para) +msgid "Place the tenant ID in a usable variable, as follows:" +msgstr "" + +#: ./doc/common/section_cli_nova_quotas.xml:222(replaceable) ./doc/common/section_cli_nova_quotas.xml:251(replaceable) ./doc/common/section_cli_nova_quotas.xml:293(replaceable) +msgid "tenantName" +msgstr "" + +#: ./doc/common/section_cli_nova_quotas.xml:225(para) +msgid "List the currently set quota values for a tenant, as follows:" +msgstr "" + +#: ./doc/common/section_cli_nova_quotas.xml:249(title) +msgid "To update quota values for an existing tenant (project)" +msgstr "" + +#: ./doc/common/section_cli_nova_quotas.xml:250(para) +msgid "Obtain the tenant ID, as follows:" +msgstr "" + +#: ./doc/common/section_cli_nova_quotas.xml:254(para) ./doc/common/section_cli_nova_quotas.xml:329(para) +msgid "Update a particular quota value, as follows:" +msgstr "" + +#: ./doc/common/section_cli_nova_quotas.xml:255(replaceable) ./doc/common/section_cli_nova_quotas.xml:330(replaceable) +msgid "quotaName" +msgstr "" + +#: ./doc/common/section_cli_nova_quotas.xml:255(replaceable) ./doc/common/section_cli_nova_quotas.xml:330(replaceable) +msgid "quotaValue" +msgstr "" + +#: ./doc/common/section_cli_nova_quotas.xml:255(replaceable) +msgid "tenantID" +msgstr "" + +#: ./doc/common/section_cli_nova_quotas.xml:277(para) ./doc/common/section_cli_nova_quotas.xml:352(para) +msgid "To view a list of options for the command, run:" +msgstr "" + +#: ./doc/common/section_cli_nova_quotas.xml:285(title) +msgid "View and update Compute quotas for a tenant user" +msgstr "" + +#: ./doc/common/section_cli_nova_quotas.xml:287(title) +msgid "To view quota values for a tenant user" +msgstr "" + +#: ./doc/common/section_cli_nova_quotas.xml:288(para) ./doc/common/section_cli_nova_quotas.xml:322(para) +msgid "Place the user ID in a usable variable, as follows:" +msgstr "" + +#: ./doc/common/section_cli_nova_quotas.xml:289(replaceable) ./doc/common/section_cli_nova_quotas.xml:323(replaceable) ./doc/common/section_cli_nova_quotas.xml:326(replaceable) +msgid "userName" +msgstr "" + +#: ./doc/common/section_cli_nova_quotas.xml:292(para) ./doc/common/section_cli_nova_quotas.xml:325(para) +msgid "Place the user's tenant ID in a usable variable, as follows:" +msgstr "" + +#: ./doc/common/section_cli_nova_quotas.xml:296(para) +msgid "List the currently set quota values for a tenant user, as follows:" +msgstr "" + +#: ./doc/common/section_cli_nova_quotas.xml:321(title) +msgid "To update quota values for a tenant user" +msgstr "" + +#. ... Old module003-ch001-intro-objstore edited, renamed, and stored in doc/common for use by both Cloud Admin and Operator Training Guides... +#: ./doc/common/section_objectstorage-intro.xml:8(title) ./doc/common/section_about-object-storage.xml:7(title) +msgid "Introduction to Object Storage" +msgstr "" + +#: ./doc/common/section_objectstorage-intro.xml:9(para) +msgid "OpenStack Object Storage (code-named Swift) is open source software for creating redundant, scalable data storage using clusters of standardized servers to store petabytes of accessible data. It is a long-term storage system for large amounts of static data that can be retrieved, leveraged, and updated. Object Storage uses a distributed architecture with no central point of control, providing greater scalability, redundancy, and permanence. Objects are written to multiple hardware devices, with the OpenStack software responsible for ensuring data replication and integrity across the cluster. Storage clusters scale horizontally by adding new nodes. Should a node fail, OpenStack works to replicate its content from other active nodes. Because OpenStack uses software logic to ensure data replication and distribution across different devices, inexpensive commodity hard drives and servers can be used in lieu of more expensive equipment." +msgstr "" + +#: ./doc/common/section_objectstorage-intro.xml:20(para) +msgid "Object Storage is ideal for cost effective, scale-out storage. It provides a fully distributed, API-accessible storage platform that can be integrated directly into applications or used for backup, archiving, and data retention." +msgstr "" + +#: ./doc/common/section_cli_keystone_commands.xml:11(title) +msgid "keystone commands" +msgstr "" + +#: ./doc/common/section_cli_keystone_commands.xml:12(para) +msgid "The keystone client is the command-line interface (CLI) for the OpenStack Identity API and its extensions." +msgstr "" + +#: ./doc/common/section_cli_keystone_commands.xml:20(title) +msgid "keystone usage" +msgstr "" + +#: ./doc/common/section_cli_keystone_commands.xml:35(title) +msgid "keystone positional arguments" +msgstr "" + +#: ./doc/common/section_cli_keystone_commands.xml:86(title) +msgid "keystone optional arguments" +msgstr "" + +#: ./doc/common/section_cli_keystone_commands.xml:139(title) +msgid "keystone bootstrap command" +msgstr "" + +#: ./doc/common/section_cli_keystone_commands.xml:160(title) +msgid "keystone catalog command" +msgstr "" + +#: ./doc/common/section_cli_keystone_commands.xml:172(title) +msgid "keystone discover command" +msgstr "" + +#: ./doc/common/section_cli_keystone_commands.xml:186(title) +msgid "keystone ec2-credentials-create command" +msgstr "" + +#: ./doc/common/section_cli_keystone_commands.xml:200(title) +msgid "keystone ec2-credentials-delete command" +msgstr "" + +#: ./doc/common/section_cli_keystone_commands.xml:214(title) +msgid "keystone ec2-credentials-get command" +msgstr "" + +#: ./doc/common/section_cli_keystone_commands.xml:228(title) +msgid "keystone ec2-credentials-list command" +msgstr "" + +#: ./doc/common/section_cli_keystone_commands.xml:239(title) +msgid "keystone endpoint-create command" +msgstr "" + +#: ./doc/common/section_cli_keystone_commands.xml:262(title) +msgid "keystone endpoint-delete command" +msgstr "" + +#: ./doc/common/section_cli_keystone_commands.xml:273(title) +msgid "keystone endpoint-get command" +msgstr "" + +#: ./doc/common/section_cli_keystone_commands.xml:292(title) +msgid "keystone endpoint-list command" +msgstr "" + +#: ./doc/common/section_cli_keystone_commands.xml:300(title) +msgid "keystone password-update command" +msgstr "" + +#: ./doc/common/section_cli_keystone_commands.xml:316(title) +msgid "keystone role-create command" +msgstr "" + +#: ./doc/common/section_cli_keystone_commands.xml:327(title) +msgid "keystone role-delete command" +msgstr "" + +#: ./doc/common/section_cli_keystone_commands.xml:338(title) +msgid "keystone role-get command" +msgstr "" + +#: ./doc/common/section_cli_keystone_commands.xml:349(title) +msgid "keystone role-list command" +msgstr "" + +#: ./doc/common/section_cli_keystone_commands.xml:357(title) +msgid "keystone service-create command" +msgstr "" + +#: ./doc/common/section_cli_keystone_commands.xml:374(title) +msgid "keystone service-delete command" +msgstr "" + +#: ./doc/common/section_cli_keystone_commands.xml:385(title) +msgid "keystone service-get command" +msgstr "" + +#: ./doc/common/section_cli_keystone_commands.xml:396(title) +msgid "keystone service-list command" +msgstr "" + +#: ./doc/common/section_cli_keystone_commands.xml:404(title) +msgid "keystone tenant-create command" +msgstr "" + +#: ./doc/common/section_cli_keystone_commands.xml:421(title) +msgid "keystone tenant-delete command" +msgstr "" + +#: ./doc/common/section_cli_keystone_commands.xml:432(title) +msgid "keystone tenant-get command" +msgstr "" + +#: ./doc/common/section_cli_keystone_commands.xml:443(title) +msgid "keystone tenant-list command" +msgstr "" + +#: ./doc/common/section_cli_keystone_commands.xml:451(title) +msgid "keystone tenant-update command" +msgstr "" + +#: ./doc/common/section_cli_keystone_commands.xml:470(title) +msgid "keystone token-get command" +msgstr "" + +#: ./doc/common/section_cli_keystone_commands.xml:481(title) +msgid "keystone user-create command" +msgstr "" + +#: ./doc/common/section_cli_keystone_commands.xml:500(title) +msgid "keystone user-delete command" +msgstr "" + +#: ./doc/common/section_cli_keystone_commands.xml:511(title) +msgid "keystone user-get command" +msgstr "" + +#: ./doc/common/section_cli_keystone_commands.xml:522(title) +msgid "keystone user-list command" +msgstr "" + +#: ./doc/common/section_cli_keystone_commands.xml:534(title) +msgid "keystone user-password-update command" +msgstr "" + +#: ./doc/common/section_cli_keystone_commands.xml:546(title) +msgid "keystone user-role-add command" +msgstr "" + +#: ./doc/common/section_cli_keystone_commands.xml:562(title) +msgid "keystone user-role-list command" +msgstr "" + +#: ./doc/common/section_cli_keystone_commands.xml:576(title) +msgid "keystone user-role-remove command" +msgstr "" + +#: ./doc/common/section_cli_keystone_commands.xml:593(title) +msgid "keystone user-update command" +msgstr "" + +#: ./doc/common/section_cli_keystone_credentials.xml:6(title) +msgid "Set up credentials for the keystone client" +msgstr "" + +#: ./doc/common/section_cli_keystone_credentials.xml:7(para) +msgid "You can configure the python-keystoneclient with admin credentials with either an authentication token or a user name and password." +msgstr "" + +#: ./doc/common/section_cli_keystone_credentials.xml:12(title) +msgid "To configure the keystone client with an authentication token" +msgstr "" + +#: ./doc/common/section_cli_keystone_credentials.xml:15(para) +msgid "Export your keystone endpoint to the OS_SERVICE_ENDPOINT environment variable:" +msgstr "" + +#: ./doc/common/section_cli_keystone_credentials.xml:21(para) +msgid "Export the administrator service token to the OS_SERVICE_TOKEN environment variable:" +msgstr "" + +#: ./doc/common/section_cli_keystone_credentials.xml:26(para) ./doc/common/section_cli_keystone_credentials.xml:80(para) +msgid "Alternatively, you can specify these parameters on any keystone client command:" +msgstr "" + +#: ./doc/common/section_cli_keystone_credentials.xml:30(para) +msgid "--os-endpoint SERVICE_ENDPOINT. An endpoint to use instead of the one in the service catalog. Defaults to env[OS_SERVICE_ENDPOINT]." +msgstr "" + +#: ./doc/common/section_cli_keystone_credentials.xml:39(para) +msgid "--os-token SERVICE_TOKEN. An existing token to use instead of the one generated by authentication. Defaults to env[OS_SERVICE_TOKEN]." +msgstr "" + +#: ./doc/common/section_cli_keystone_credentials.xml:52(title) +msgid "To configure the keystone client with a user name and password" +msgstr "" + +#: ./doc/common/section_cli_keystone_credentials.xml:55(para) +msgid "Export the administrator user name to the OS_USERNAME environment variable:" +msgstr "" + +#: ./doc/common/section_cli_keystone_credentials.xml:61(para) +msgid "Export the administrator password to the OS_PASSWORD environment variable:" +msgstr "" + +#: ./doc/common/section_cli_keystone_credentials.xml:67(para) +msgid "Export the tenant name to the OS_TENANT_NAME environment variable:" +msgstr "" + +#: ./doc/common/section_cli_keystone_credentials.xml:73(para) +msgid "Export the URL of the keystone auth server, for example http://localhost:5000/v2.0', to the OS_AUTH_URL environment variable:" +msgstr "" + +#: ./doc/common/section_cli_keystone_credentials.xml:84(para) +msgid "--os-username OS_USERNAME. Name used for authentication with the Identity Service. Defaults to env[OS_USERNAME]." +msgstr "" + +#: ./doc/common/section_cli_keystone_credentials.xml:92(para) +msgid "--os-password OS_PASSWORD. Password used for authentication with the Identity Service. Defaults to env[OS_PASSWORD]." +msgstr "" + +#: ./doc/common/section_cli_keystone_credentials.xml:100(para) +msgid "--os-tenant_name OS_TENANT_NAME. Tenant for which to request authentication. Defaults to env[OS_TENANT_NAME]." +msgstr "" + +#: ./doc/common/section_cli_keystone_credentials.xml:108(para) +msgid "--os-auth_url OS_AUTH_URL. The Identity Service endpoint to use for authentication. Defaults to env[OS_AUTH_URL]." +msgstr "" + +#: ./doc/common/section_using-vnc-console.xml:6(title) +msgid "Use the VNC console" +msgstr "" + +#: ./doc/common/section_using-vnc-console.xml:7(para) +msgid "To interact through the VNC console, you can use a VNC client directly, a special Java client, or a web browser. For information about how to configure the console, see ." +msgstr "" + +#: ./doc/common/section_using-vnc-console.xml:15(title) +msgid "Get an access URL" +msgstr "" + +#: ./doc/common/section_using-vnc-console.xml:16(para) +msgid "The Compute Service enables you to create access_urls through the os-consoles extension. Support for accessing this URL is provided by the nova client:" +msgstr "" + +#: ./doc/common/section_using-vnc-console.xml:19(replaceable) ./doc/common/section_using-vnc-console.xml:25(replaceable) ./doc/common/section_using-vnc-console.xml:52(replaceable) ./doc/common/section_using-vnc-console.xml:65(replaceable) +msgid "[server_id]" +msgstr "" + +#: ./doc/common/section_using-vnc-console.xml:19(replaceable) +msgid "[novnc|xvpvnc]" +msgstr "" + +#: ./doc/common/section_using-vnc-console.xml:20(para) +msgid "Specify 'novnc' to get a URL suitable for pasting into a web browser." +msgstr "" + +#: ./doc/common/section_using-vnc-console.xml:22(para) +msgid "Specify 'xvpvnc' for a URL suitable for pasting into the Java client." +msgstr "" + +#: ./doc/common/section_using-vnc-console.xml:24(para) +msgid "To request a web browser URL:" +msgstr "" + +#: ./doc/common/section_using-vnc-console.xml:28(title) +msgid "Access a VNC console with a Java client" +msgstr "" + +#: ./doc/common/section_using-vnc-console.xml:29(para) +msgid "To enable support for the OpenStack Java VNC client in compute, run the nova-xvpvncproxy service." +msgstr "" + +#: ./doc/common/section_using-vnc-console.xml:34(para) +msgid "xvpvncproxy_port=[port] - port to bind (defaults to 6081)" +msgstr "" + +#: ./doc/common/section_using-vnc-console.xml:38(para) +msgid "xvpvncproxy_host=[host] - host to bind (defaults to 0.0.0.0)" +msgstr "" + +#: ./doc/common/section_using-vnc-console.xml:42(para) +msgid "As a client, you need a special Java client, which is a slightly modified version of TightVNC that supports our token auth:" +msgstr "" + +#: ./doc/common/section_using-vnc-console.xml:48(para) +msgid "To create a session, request an access URL by using . Then, run the client as follows." +msgstr "" + +#: ./doc/common/section_using-vnc-console.xml:51(para) +msgid "To get an access URL:" +msgstr "" + +#: ./doc/common/section_using-vnc-console.xml:53(para) +msgid "To run the client:" +msgstr "" + +#: ./doc/common/section_using-vnc-console.xml:54(replaceable) +msgid "[access_url]" +msgstr "" + +#: ./doc/common/section_using-vnc-console.xml:59(title) +msgid "Access a VNC console with a web browser" +msgstr "" + +#: ./doc/common/section_using-vnc-console.xml:61(para) +msgid "Retrieving an access_url for a web browser is similar to the flow for the Java client." +msgstr "" + +#: ./doc/common/section_using-vnc-console.xml:63(para) +msgid "To get the access URL, run the following command:" +msgstr "" + +#: ./doc/common/section_using-vnc-console.xml:66(para) +msgid "Paste the URL into your web browser." +msgstr "" + +#: ./doc/common/section_using-vnc-console.xml:68(para) +msgid "Additionally, you can use the OpenStack dashboard, known as horizon, to access browser-based VNC consoles for instances." +msgstr "" + +#: ./doc/common/section_objectstorage_tenant-specific-image-storage.xml:6(title) +msgid "Configure tenant-specific image locations with Object Storage" +msgstr "" + +#: ./doc/common/section_objectstorage_tenant-specific-image-storage.xml:14(para) +msgid "The tenant who owns the image" +msgstr "" + +#: ./doc/common/section_objectstorage_tenant-specific-image-storage.xml:17(para) +msgid "Tenants that are defined in and that have admin-level accounts" +msgstr "" + +#: ./doc/common/section_objectstorage_tenant-specific-image-storage.xml:8(para) +msgid "For some deployers, it is not ideal to store all images in one place to enable all tenants and users to access them. You can configure the Image Service to store image data in tenant-specific image locations. Then, only the following tenants can use the Image Service to access the created image:" +msgstr "" + +#: ./doc/common/section_objectstorage_tenant-specific-image-storage.xml:23(title) +msgid "To configure tenant-specific image locations" +msgstr "" + +#: ./doc/common/section_objectstorage_tenant-specific-image-storage.xml:25(para) +msgid "Configure swift as your in the glance-api.conf file." +msgstr "" + +#: ./doc/common/section_objectstorage_tenant-specific-image-storage.xml:33(para) +msgid ". Set to True to enable tenant-specific storage locations. Default is False." +msgstr "" + +#: ./doc/common/section_objectstorage_tenant-specific-image-storage.xml:39(para) +msgid ". Specify a list of tenant IDs that can grant read and write access to all Object Storage containers that are created by the Image Service." +msgstr "" + +#: ./doc/common/section_objectstorage_tenant-specific-image-storage.xml:30(para) +msgid "Set these configuration options in the glance-api.conf file: " +msgstr "" + +#: ./doc/common/section_objectstorage_tenant-specific-image-storage.xml:48(para) +msgid "With this configuration, images are stored in an Object Storage service (swift) endpoint that is pulled from the service catalog for the authenticated user." +msgstr "" + +#: ./doc/common/section_cli_ceilometer_commands.xml:11(title) +msgid "ceilometer commands" +msgstr "" + +#: ./doc/common/section_cli_ceilometer_commands.xml:12(para) +msgid "The ceilometer client is the command-line interface (CLI) for the OpenStack Telemetry API and its extensions." +msgstr "" + +#: ./doc/common/section_cli_ceilometer_commands.xml:20(title) +msgid "ceilometer usage" +msgstr "" + +#: ./doc/common/section_cli_ceilometer_commands.xml:36(title) +msgid "ceilometer positional arguments" +msgstr "" + +#: ./doc/common/section_cli_ceilometer_commands.xml:74(title) +msgid "ceilometer optional arguments" +msgstr "" + +#: ./doc/common/section_cli_ceilometer_commands.xml:121(title) +msgid "ceilometer alarm-combination-create command" +msgstr "" + +#: ./doc/common/section_cli_ceilometer_commands.xml:171(title) +msgid "ceilometer alarm-combination-update command" +msgstr "" + +#: ./doc/common/section_cli_ceilometer_commands.xml:222(title) +msgid "ceilometer alarm-delete command" +msgstr "" + +#: ./doc/common/section_cli_ceilometer_commands.xml:234(title) +msgid "ceilometer alarm-history command" +msgstr "" + +#: ./doc/common/section_cli_ceilometer_commands.xml:250(title) +msgid "ceilometer alarm-list command" +msgstr "" + +#: ./doc/common/section_cli_ceilometer_commands.xml:264(title) +msgid "ceilometer alarm-show command" +msgstr "" + +#: ./doc/common/section_cli_ceilometer_commands.xml:276(title) +msgid "ceilometer alarm-state-get command" +msgstr "" + +#: ./doc/common/section_cli_ceilometer_commands.xml:288(title) +msgid "ceilometer alarm-state-set command" +msgstr "" + +#: ./doc/common/section_cli_ceilometer_commands.xml:302(title) +msgid "ceilometer alarm-threshold-create command" +msgstr "" + +#: ./doc/common/section_cli_ceilometer_commands.xml:369(title) +msgid "ceilometer alarm-threshold-update command" +msgstr "" + +#: ./doc/common/section_cli_ceilometer_commands.xml:438(title) +msgid "ceilometer alarm-update command" +msgstr "" + +#: ./doc/common/section_cli_ceilometer_commands.xml:506(title) +msgid "ceilometer event-list command" +msgstr "" + +#: ./doc/common/section_cli_ceilometer_commands.xml:520(title) +msgid "ceilometer event-show command" +msgstr "" + +#: ./doc/common/section_cli_ceilometer_commands.xml:532(title) +msgid "ceilometer event-type-list command" +msgstr "" + +#: ./doc/common/section_cli_ceilometer_commands.xml:540(title) +msgid "ceilometer meter-list command" +msgstr "" + +#: ./doc/common/section_cli_ceilometer_commands.xml:554(title) +msgid "ceilometer resource-list command" +msgstr "" + +#: ./doc/common/section_cli_ceilometer_commands.xml:568(title) +msgid "ceilometer resource-show command" +msgstr "" + +#: ./doc/common/section_cli_ceilometer_commands.xml:580(title) +msgid "ceilometer sample-create command" +msgstr "" + +#: ./doc/common/section_cli_ceilometer_commands.xml:615(title) +msgid "ceilometer sample-list command" +msgstr "" + +#: ./doc/common/section_cli_ceilometer_commands.xml:633(title) +msgid "ceilometer statistics command" +msgstr "" + +#: ./doc/common/section_cli_ceilometer_commands.xml:651(title) +msgid "ceilometer trait-description-list command" +msgstr "" + +#: ./doc/common/section_cli_ceilometer_commands.xml:664(title) +msgid "ceilometer trait-list command" +msgstr "" + +#: ./doc/common/app_command_reference.xml:17(title) +msgid "Command reference" +msgstr "" + +#: ./doc/common/section_cli_keystone_services.xml:7(title) +msgid "Create and manage services and service users" +msgstr "" + +#: ./doc/common/section_cli_keystone_services.xml:8(para) +msgid "The Identity Service enables you to define services, as follows:" +msgstr "" + +#: ./doc/common/section_cli_keystone_services.xml:12(para) +msgid "Service catalog template. The Identity Service acts as a service catalog of endpoints for other OpenStack services. The etc/default_catalog.templates template file defines the endpoints for services. When the Identity Service uses a template file back end, any changes that are made to the endpoints are cached. These changes do not persist when you restart the service or reboot the machine." +msgstr "" + +#: ./doc/common/section_cli_keystone_services.xml:23(para) +msgid "A SQL back end for the catalog service. When the Identity Service is online, you must add the services to the catalog. When you deploy a system for production, use the SQL back end." +msgstr "" + +#: ./doc/common/section_cli_keystone_services.xml:29(para) +msgid "The auth_token middleware supports the use of either a shared secret or users for each service." +msgstr "" + +#: ./doc/common/section_cli_keystone_services.xml:32(para) +msgid "To authenticate users against the Identity Service, you must create a service user for each OpenStack service. For example, create a service user for the Compute, Block Storage, and Networking services." +msgstr "" + +#: ./doc/common/section_cli_keystone_services.xml:36(para) +msgid "To configure the OpenStack services with service users, create a project for all services and create users for each service. Assign the admin role to each service user and project pair. This role enables users to validate tokens and authenticate and authorize other user requests." +msgstr "" + +#: ./doc/common/section_cli_keystone_services.xml:42(title) +msgid "Create a service" +msgstr "" + +#: ./doc/common/section_cli_keystone_services.xml:45(para) +msgid "List the available services:" +msgstr "" + +#: ./doc/common/section_cli_keystone_services.xml:59(para) +msgid "To create a service, run this command:" +msgstr "" + +#: ./doc/common/section_cli_keystone_services.xml:60(replaceable) +msgid "service_name" +msgstr "" + +#: ./doc/common/section_cli_keystone_services.xml:60(replaceable) +msgid "service_type" +msgstr "" + +#: ./doc/common/section_cli_keystone_services.xml:60(replaceable) +msgid "service_description" +msgstr "" + +#: ./doc/common/section_cli_keystone_services.xml:61(para) +msgid "The arguments are:" +msgstr "" + +#: ./doc/common/section_cli_keystone_services.xml:64(para) +msgid "service_name. The unique name of the new service." +msgstr "" + +#: ./doc/common/section_cli_keystone_services.xml:68(para) +msgid "service_type. The service type, such as identity, compute, network, image, object-store or any other service identifier string." +msgstr "" + +#: ./doc/common/section_cli_keystone_services.xml:78(para) +msgid "service_description. The description of the service." +msgstr "" + +#: ./doc/common/section_cli_keystone_services.xml:82(para) +msgid "For example, to create a swift service of type object-store, run this command:" +msgstr "" + +#: ./doc/common/section_cli_keystone_services.xml:97(para) +msgid "To get details for a service, run this command:" +msgstr "" + +#: ./doc/common/section_cli_keystone_services.xml:99(replaceable) +msgid "service_ID" +msgstr "" + +#: ./doc/common/section_cli_keystone_services.xml:114(title) +msgid "Create service users" +msgstr "" + +#: ./doc/common/section_cli_keystone_services.xml:117(para) +msgid "Create a project for the service users. Typically, this project is named service, but choose any name you like:" +msgstr "" + +#: ./doc/common/section_cli_keystone_services.xml:122(para) +msgid "The output shows the ID for the project." +msgstr "" + +#: ./doc/common/section_cli_keystone_services.xml:123(para) +msgid "Make a note of this ID. You need it to create service users and assign roles." +msgstr "" + +#: ./doc/common/section_cli_keystone_services.xml:135(para) +msgid "Create service users for the relevant services for your deployment." +msgstr "" + +#: ./doc/common/section_cli_keystone_services.xml:139(para) +msgid "To assign the admin role to the service user-project pairs, run this command to get the ID of the admin role:" +msgstr "" + +#: ./doc/common/section_cli_keystone_services.xml:155(para) +msgid "Assign the admin role to the user-project pair:" +msgstr "" + +#: ./doc/common/section_cli_keystone_services.xml:157(replaceable) +msgid "SERVICE_USER_ID" +msgstr "" + +#: ./doc/common/section_cli_keystone_services.xml:157(replaceable) +msgid "ADMIN_ROLE_ID" +msgstr "" + +#: ./doc/common/section_cli_keystone_services.xml:157(replaceable) +msgid "SERVICE_PROJECT_ID" +msgstr "" + +#: ./doc/common/section_cli_keystone_services.xml:162(title) +msgid "Delete a service" +msgstr "" + +#: ./doc/common/section_cli_keystone_services.xml:163(para) +msgid "To delete a specified service, specify its ID:" +msgstr "" + +#: ./doc/common/section_cli_keystone_services.xml:164(replaceable) +msgid "SERVICE_ID" +msgstr "" + +#: ./doc/common/section_cli_nova_boot_from_volume.xml:6(title) +msgid "Launch an instance from a volume" +msgstr "" + +#: ./doc/common/section_cli_nova_boot_from_volume.xml:7(para) +msgid "After you create a bootable volume, you can launch an instance from that volume." +msgstr "" + +#: ./doc/common/section_cli_nova_boot_from_volume.xml:9(para) +msgid "Optionally, to configure your volume, see the OpenStack Configuration Reference." +msgstr "" + +#: ./doc/common/section_cli_nova_boot_from_volume.xml:15(para) +msgid "For a list of images to choose from to create a bootable volume, run this command:" +msgstr "" + +#: ./doc/common/section_cli_nova_boot_from_volume.xml:27(para) +msgid "To create a bootable volume from an image, include the image ID in the command:" +msgstr "" + +#: ./doc/common/section_cli_nova_boot_from_volume.xml:48(para) +msgid "Before the volume builds, its bootable state is false." +msgstr "" + +#: ./doc/common/section_cli_nova_boot_from_volume.xml:52(para) +msgid "To list volumes, run the following command:" +msgstr "" + +#: ./doc/common/section_cli_nova_boot_from_volume.xml:59(para) +msgid "Note that the bootable state is now true. Copy the value in the ID field for your volume." +msgstr "" + +#: ./doc/common/section_cli_nova_boot_from_volume.xml:64(para) +msgid "To launch an instance, include the --block_device_mapping parameter:" +msgstr "" + +#: ./doc/common/section_cli_nova_boot_from_volume.xml:67(replaceable) ./doc/common/section_cli_nova_boot_from_volume.xml:80(replaceable) +msgid "FLAVOR" +msgstr "" + +#: ./doc/common/section_cli_nova_boot_from_volume.xml:67(replaceable) +msgid "DEVNAME" +msgstr "" + +#: ./doc/common/section_cli_nova_boot_from_volume.xml:67(replaceable) +msgid "ID" +msgstr "" + +#: ./doc/common/section_cli_nova_boot_from_volume.xml:67(replaceable) +msgid "TYPE" +msgstr "" + +#: ./doc/common/section_cli_nova_boot_from_volume.xml:67(replaceable) +msgid "DELETE_ON_TERMINATE" +msgstr "" + +#: ./doc/common/section_cli_nova_boot_from_volume.xml:68(para) +msgid "The command arguments are:" +msgstr "" + +#: ./doc/common/section_cli_nova_boot_from_volume.xml:72(th) +msgid "Parameter" +msgstr "" + +#: ./doc/common/section_cli_nova_boot_from_volume.xml:79(parameter) +msgid "--flavor" +msgstr "" + +#: ./doc/common/section_cli_nova_boot_from_volume.xml:83(para) +msgid "The flavor ID." +msgstr "" + +#: ./doc/common/section_cli_nova_boot_from_volume.xml:88(para) +msgid "--block_device_mappingDEVNAME=ID:type:size:delete-on-terminate" +msgstr "" + +#: ./doc/common/section_cli_nova_boot_from_volume.xml:94(para) +msgid "DEVNAME. A device name where the volume is attached in the system at /dev/dev_name. This value is typically vda." +msgstr "" + +#: ./doc/common/section_cli_nova_boot_from_volume.xml:101(para) +msgid "ID. The ID of the volume to boot from, as shown in the output of ." +msgstr "" + +#: ./doc/common/section_cli_nova_boot_from_volume.xml:106(para) +msgid "type. Either snap or any other value, including a blank string. snap means that the volume was created from a snapshot." +msgstr "" + +#: ./doc/common/section_cli_nova_boot_from_volume.xml:113(para) +msgid "size. The size of the volume, in GBs. It is safe to leave this blank and have the Compute service infer the size." +msgstr "" + +#: ./doc/common/section_cli_nova_boot_from_volume.xml:119(para) +msgid "delete-on-terminate. Boolean. Indicates whether the volume is deleted when the instance is deleted. You can specify:" +msgstr "" + +#: ./doc/common/section_cli_nova_boot_from_volume.xml:125(para) +msgid "True or 1" +msgstr "" + +#: ./doc/common/section_cli_nova_boot_from_volume.xml:130(para) +msgid "False or 0" +msgstr "" + +#: ./doc/common/section_cli_nova_boot_from_volume.xml:143(para) +msgid "The name for the server." +msgstr "" + +#: ./doc/common/section_cli_nova_boot_from_volume.xml:148(para) +msgid "You can also attach a swap disk on boot with the --swap flag, or you can attach an ephemeral disk on boot with the --ephemeral flag." +msgstr "" + +#: ./doc/common/section_cli_nova_boot_from_volume.xml:152(para) +msgid "For example, you might enter the following command to boot from a volume. The volume is not deleted when the instance is terminated:" +msgstr "" + +#: ./doc/common/section_cli_nova_boot_from_volume.xml:187(para) +msgid "Now when you list volumes, the volume is attached to a server:" +msgstr "" + +#: ./doc/common/section_cli_nova_images.xml:6(title) +msgid "Manage images with the nova client" +msgstr "" + +#: ./doc/common/section_cli_nova_images.xml:16(title) +msgid "To create an image" +msgstr "" + +#: ./doc/common/section_cli_nova_images.xml:19(para) +msgid "For more information, see the Taking Snapshots in the OpenStack Operations Guide." +msgstr "" + +#: ./doc/common/section_cli_nova_images.xml:86(title) +msgid "To launch an instance from your image" +msgstr "" + +#: ./doc/common/section_keystone-external-auth.xml:7(title) +msgid "External authentication with the Identity Service" +msgstr "" + +#: ./doc/common/section_keystone-external-auth.xml:9(para) +msgid "When the Identity Service runs in apache-httpd, you can use external authentication methods that differ from the authentication provided by the identity store back-end. For example, you can use an SQL identity back-end together with X.509 authentication, Kerberos, and so on instead of using the user name and password combination." +msgstr "" + +#: ./doc/common/section_keystone-external-auth.xml:16(title) +msgid "Use HTTPD authentication" +msgstr "" + +#: ./doc/common/section_keystone-external-auth.xml:17(para) +msgid "Web servers, like Apache HTTP, support many methods of authentication. The Identity Service can allow the web server to perform the authentication. The web server then passes the authenticated user to the Identity Service by using the REMOTE_USER environment variable. This user must already exist in the Identity Service back-end so as to get a token from the controller. To use this method, the Identity Service should run on apache-httpd." +msgstr "" + +#: ./doc/common/section_keystone-external-auth.xml:28(title) +msgid "Use X.509" +msgstr "" + +#: ./doc/common/section_keystone-external-auth.xml:29(para) +msgid "The following Apache configuration snippet authenticates the user based on a valid X.509 certificate from a known CA:" +msgstr "" + +#: ./doc/common/section_getstart_orchestration.xml:5(title) +msgid "Orchestration service overview" +msgstr "" + +#: ./doc/common/section_getstart_orchestration.xml:6(para) +msgid "The Orchestration service provides a template-based orchestration for describing a cloud application by running OpenStack API calls to generate running cloud applications. The software integrates other core components of OpenStack into a one-file template system. The templates enable you to create most OpenStack resource types, such as instances, floating IPs, volumes, security groups, users, and so on. Also, provides some more advanced functionality, such as instance high availability, instance auto-scaling, and nested stacks. By providing very tight integration with other OpenStack core projects, all OpenStack core projects could receive a larger user base." +msgstr "" + +#: ./doc/common/section_getstart_orchestration.xml:17(para) +msgid "The service enables deployers to integrate with the Orchestration service directly or through custom plug-ins." +msgstr "" + +#: ./doc/common/section_getstart_orchestration.xml:19(para) +msgid "The Orchestration service consists of the following components:" +msgstr "" + +#: ./doc/common/section_getstart_orchestration.xml:23(para) +msgid "heat command-line client. A CLI that communicates with the heat-api to run AWS CloudFormation APIs. End developers could also use the Orchestration REST API directly." +msgstr "" + +#: ./doc/common/section_getstart_orchestration.xml:28(para) +msgid "heat-api component. Provides an OpenStack-native REST API that processes API requests by sending them to the heat-engine over RPC." +msgstr "" + +#: ./doc/common/section_getstart_orchestration.xml:33(para) +msgid "heat-api-cfn component. Provides an AWS Query API that is compatible with AWS CloudFormation and processes API requests by sending them to the heat-engine over RPC." +msgstr "" + +#: ./doc/common/section_getstart_orchestration.xml:39(para) +msgid "heat-engine. Orchestrates the launching of templates and provides events back to the API consumer." +msgstr "" + +#: ./doc/common/section_getstart_networking.xml:5(title) +msgid "Networking service overview" +msgstr "" + +#: ./doc/common/section_getstart_networking.xml:6(para) +msgid "Provides network-connectivity-as-a-service between interface devices that are managed by other OpenStack services, usually Compute. Enables users to create and attach interfaces to networks. Like many OpenStack services, OpenStack Networking is highly configurable due to its plug-in architecture. These plug-ins accommodate different networking equipment and software. Consequently, the architecture and deployment vary dramatically." +msgstr "" + +#: ./doc/common/section_getstart_networking.xml:14(para) +msgid "Includes the following components:" +msgstr "" + +#: ./doc/common/section_getstart_networking.xml:17(para) +msgid "neutron-server. Accepts and routes API requests to the appropriate OpenStack Networking plug-in for action." +msgstr "" + +#: ./doc/common/section_getstart_networking.xml:22(para) +msgid "OpenStack Networking plug-ins and agents. Plugs and unplugs ports, creates networks or subnets, and provides IP addressing. These plug-ins and agents differ depending on the vendor and technologies used in the particular cloud. OpenStack Networking ships with plug-ins and agents for Cisco virtual and physical switches, Nicira NVP product, NEC OpenFlow products, Open vSwitch, Linux bridging, and the Ryu Network Operating System." +msgstr "" + +#: ./doc/common/section_getstart_networking.xml:30(para) +msgid "The common agents are L3 (layer 3), DHCP (dynamic host IP addressing), and a plug-in agent." +msgstr "" + +#: ./doc/common/section_getstart_networking.xml:34(para) +msgid "Messaging queue. Most OpenStack Networking installations make use of a messaging queue to route information between the neutron-server and various agents as well as a database to store networking state for particular plug-ins." +msgstr "" + +#: ./doc/common/section_getstart_networking.xml:40(para) +msgid "OpenStack Networking interacts mainly with OpenStack Compute, where it provides networks and connectivity for its instances." +msgstr "" + +#: ./doc/common/section_user-data.xml:6(title) +msgid "Configure instances at boot" +msgstr "" + +#: ./doc/common/section_user-data.xml:7(para) +msgid "When you boot instances in an OpenStack cloud, you can use user data or cloud-init to automatically configure instances at boot time. You might want to install some packages, start services, or manage your instance by using a Puppet or Chef server." +msgstr "" + +#: ./doc/common/section_user-data.xml:13(title) +msgid "User data" +msgstr "" + +#: ./doc/common/section_user-data.xml:14(para) +msgid "User data is the mechanism by which a user can pass information contained in a local file to an instance at launch time. The typical use case is to pass something like a shell script or a configuration file as user data." +msgstr "" + +#: ./doc/common/section_user-data.xml:19(para) +msgid "User data is sent using the --user-data /path/to/filename option when calling . This example creates a text file and sends its contents as user data to the instance:" +msgstr "" + +#: ./doc/common/section_user-data.xml:26(para) +msgid "The instance can get user data by querying the metadata service through either the OpenStack metadata API or the EC2 compatibility API:" +msgstr "" + +#: ./doc/common/section_user-data.xml:34(para) +msgid "The Compute service treats user data as a blob. While the previous example uses a text file, user data can be in any format." +msgstr "" + +#: ./doc/common/section_user-data.xml:38(para) +msgid "For more information, see ." +msgstr "" + +#: ./doc/common/section_user-data.xml:42(package) +msgid "cloud-init" +msgstr "" + +#: ./doc/common/section_user-data.xml:43(para) +msgid "To do something useful with the user data, you must configure the virtual machine image to run a service on boot that gets user data from the metadata service and takes some action based on the contents of the data. The cloud-init package does exactly this. This package is compatible with the Compute metadata service and the Compute configuration drive." +msgstr "" + +#: ./doc/common/section_user-data.xml:51(para) +msgid "The cloud-init package supports multiple cloud providers. You can use the same virtual machine image in different clouds without modification. The cloud-init package is an open source project and the source code is available on Launchpad. It is maintained by Canonical, the company that runs the Ubuntu project. All Ubuntu cloud images come pre-installed with cloud-init. However, cloud-init is not designed to be Ubuntu-specific and has been successfully ported to several other platforms including Fedora." +msgstr "" + +#: ./doc/common/section_user-data.xml:66(para) +msgid "Even if you do not use user data to configure instance behavior at boot time, install cloud-init on images that you create because this package provides useful functionality. For example, the cloud-init package enables you to copy the public key to an account (the ubuntu account by default on Ubuntu instances, the ec2-user by default in Fedora instances)." +msgstr "" + +#: ./doc/common/section_user-data.xml:75(para) +msgid "If you do not have cloud-init installed, you must manually configure your image to get the public key from the metadata service on boot and copy it to the appropriate account." +msgstr "" + +#: ./doc/common/section_user-data.xml:81(title) +msgid "cloud-init supported formats and documentation" +msgstr "" + +#: ./doc/common/section_user-data.xml:83(para) +msgid "Look at the cloud-initdoc/userdata.txt file the examples directory and the Ubuntu community documentation for details about how to use cloud-init. Some basic examples are provided here." +msgstr "" + +#: ./doc/common/section_user-data.xml:96(para) +msgid "Shell scripts (starts with #!)" +msgstr "" + +#: ./doc/common/section_user-data.xml:100(para) +msgid "Cloud config files (starts with #cloud-config)" +msgstr "" + +#: ./doc/common/section_user-data.xml:93(para) +msgid "cloud-init supports several different input formats for user data. Two commonly used formats are:" +msgstr "" + +#: ./doc/common/section_user-data.xml:106(title) +msgid "Run a shell script on boot" +msgstr "" + +#: ./doc/common/section_user-data.xml:107(para) +msgid "Assuming you have cloud-init installed, the simplest way to configure an instance on boot is to pass a shell script as user data. The shell file must begin with #! in order for cloud-init to recognize it as a shell script. This example shows a script that creates a clouduser account:" +msgstr "" + +#: ./doc/common/section_user-data.xml:116(para) +msgid "Sending a shell script as user data has a similar effect to writing an /etc/rc.local script: it executes very late in the boot sequence as root." +msgstr "" + +#: ./doc/common/section_user-data.xml:121(title) +msgid "Cloud-config format" +msgstr "" + +#: ./doc/common/section_user-data.xml:122(para) +msgid "cloud-init supports a YAML-based config format that allows the user to configure a large number of options on a system. User data that begins with #cloud-config will be interpreted by cloud-init as cloud-config format." +msgstr "" + +#: ./doc/common/section_user-data.xml:130(title) +msgid "Example: Set the host name" +msgstr "" + +#: ./doc/common/section_user-data.xml:131(para) +msgid "This cloud-init user data example sets the hostname and the FQDN, as well as updating /etc/hosts on the instance:" +msgstr "" + +#: ./doc/common/section_user-data.xml:143(title) +msgid "Example: Configure instances with Puppet" +msgstr "" + +#: ./doc/common/section_user-data.xml:144(para) +msgid "This cloud-init user data example, based on doc/examples/cloud-config-puppet.txt, would configure the instance to contact a Puppet server at puppetmaster.example.org and verify its identity using a certificate. " +msgstr "" + +#: ./doc/common/section_user-data.xml:172(title) +msgid "Example: Configure instances with Chef" +msgstr "" + +#: ./doc/common/section_user-data.xml:173(para) +msgid "This cloud-init user data example, based on doc/examples/cloud-config/chef.txt and intended for use in an Ubuntu image, adds the Chef apt repository, installs Chef, connects to a Chef server at https://chefserver.example.com:4000, and installs Apache:" +msgstr "" + +#: ./doc/common/section_cli_nova_secgroups.xml:8(title) +msgid "Add security group and rules" +msgstr "" + +#: ./doc/common/section_cli_nova_secgroups.xml:9(para) +msgid "The following procedure shows you how to add security groups and add rules to the default security group." +msgstr "" + +#: ./doc/common/section_cli_nova_secgroups.xml:12(title) +msgid "Add or delete a security group" +msgstr "" + +#: ./doc/common/section_cli_nova_secgroups.xml:13(para) +msgid "Security groups can be added with ." +msgstr "" + +#: ./doc/common/section_cli_nova_secgroups.xml:15(para) +msgid "The following example shows the creation of the security group secure1. After the group is created, it can be viewed in the security group list." +msgstr "" + +#: ./doc/common/section_cli_nova_secgroups.xml:39(para) +msgid "All the traffic originated by the instances (outbound traffic) is allowed" +msgstr "" + +#: ./doc/common/section_cli_nova_secgroups.xml:43(para) +msgid "All the traffic destined to instances (inbound traffic) is denied" +msgstr "" + +#: ./doc/common/section_cli_nova_secgroups.xml:47(para) +msgid "All the instances inside the group are allowed to talk to each other" +msgstr "" + +#: ./doc/common/section_cli_nova_secgroups.xml:52(para) +msgid "You can add extra rules into the default security group for handling the egress traffic. Rules are ingress only at this time." +msgstr "" + +#: ./doc/common/section_cli_nova_secgroups.xml:35(para) +msgid "Security groups can be deleted with . The default security group cannot be deleted. The default security group contains these initial settings:" +msgstr "" + +#: ./doc/common/section_cli_nova_secgroups.xml:56(para) +msgid "In the following example, the group secure1 is deleted. When you view the security group list, it no longer appears." +msgstr "" + +#: ./doc/common/section_cli_nova_secgroups.xml:71(title) +msgid "Modify security group rules" +msgstr "" + +#: ./doc/common/section_cli_nova_secgroups.xml:74(para) +msgid "It is not possible to change the default outbound behaviour." +msgstr "" + +#: ./doc/common/section_cli_nova_secgroups.xml:83(para) ./doc/common/section_cli_nova_secgroups.xml:101(para) ./doc/common/section_cli_nova_secgroups.xml:167(para) +msgid "<secgroup> ID of security group." +msgstr "" + +#: ./doc/common/section_cli_nova_secgroups.xml:86(para) ./doc/common/section_cli_nova_secgroups.xml:170(para) +msgid "<ip_proto> IP protocol (icmp, tcp, udp)." +msgstr "" + +#: ./doc/common/section_cli_nova_secgroups.xml:89(para) ./doc/common/section_cli_nova_secgroups.xml:173(para) +msgid "<from_port> Port at start of range." +msgstr "" + +#: ./doc/common/section_cli_nova_secgroups.xml:92(para) ./doc/common/section_cli_nova_secgroups.xml:176(para) +msgid "<to_port> Port at end of range." +msgstr "" + +#: ./doc/common/section_cli_nova_secgroups.xml:95(para) ./doc/common/section_cli_nova_secgroups.xml:179(para) +msgid "<cidr> CIDR for address range." +msgstr "" + +#: ./doc/common/section_cli_nova_secgroups.xml:72(para) +msgid "The security group rules control the incoming traffic that is allowed to the instances in the group, while all outbound traffic is automatically allowed. Every security group rule is a policy which allows you to specify inbound connections that are allowed to access the instance, by source address, destination port and IP protocol,(TCP, UDP or ICMP). Currently, ipv6 and other protocols cannot be managed with the security rules, making them permitted by default. To manage such, you can deploy a firewall in front of your OpenStack cloud to control other types of traffic. The command requires the following arguments for both TCP and UDP rules : " +msgstr "" + +#: ./doc/common/section_cli_nova_secgroups.xml:104(para) +msgid "<ip_proto> IP protocol (with icmp specified)." +msgstr "" + +#: ./doc/common/section_cli_nova_secgroups.xml:107(para) +msgid "<ICMP_code> The ICMP code." +msgstr "" + +#: ./doc/common/section_cli_nova_secgroups.xml:110(para) +msgid "<ICMP_type> The ICMP type." +msgstr "" + +#: ./doc/common/section_cli_nova_secgroups.xml:113(para) +msgid "<cidr> CIDR for the source address range." +msgstr "" + +#: ./doc/common/section_cli_nova_secgroups.xml:117(para) +msgid "Entering \"-1\" for both code and type indicates that all ICMP codes and types should be allowed." +msgstr "" + +#: ./doc/common/section_cli_nova_secgroups.xml:98(para) +msgid "For ICMP rules, instead of specifying a begin and end port, you specify the allowed ICMP code and ICMP type: " +msgstr "" + +#: ./doc/common/section_cli_nova_secgroups.xml:124(title) +msgid "The CIDR notation" +msgstr "" + +#: ./doc/common/section_cli_nova_secgroups.xml:125(para) +msgid "That notation allows you to specify a base IP address and a suffix that designates the number of significant bits in the IP address used to identify the network. For example, by specifying a 88.170.60.32/27, you specify 88.170.60.32 as the base IP and 27 as the suffix. Since you use an IPV4 format, there are only 5 bits available for the host part (32 minus 27). The 0.0.0.0/0 notation means you allow the entire IPV4 range, meaning allowing all addresses." +msgstr "" + +#: ./doc/common/section_cli_nova_secgroups.xml:135(para) +msgid "For example, in order to allow any IP address to access to a web server running on one of your instance inside the default security group:" +msgstr "" + +#: ./doc/common/section_cli_nova_secgroups.xml:145(para) +msgid "In order to allow any IP address to ping an instance inside the default security group (Code 0, Type 8 for the ECHO request.):" +msgstr "" + +#: ./doc/common/section_cli_nova_secgroups.xml:164(para) +msgid "In order to delete a rule, you need to specify the exact same arguments you used to create it:" +msgstr "" + +#: ./doc/common/section_keystone-concepts-domain-management.xml:6(title) ./doc/common/section_dashboard_access.xml:347(guilabel) +msgid "Domains" +msgstr "" + +#: ./doc/common/section_keystone-concepts-domain-management.xml:7(para) +msgid "A domain defines administrative boundaries for the management of Identity entities. A domain may represent an individual, company, or operator-owned space. It is used for exposing administrative activities directly to the system users." +msgstr "" + +#: ./doc/common/section_keystone-concepts-domain-management.xml:10(para) +msgid "A domain is a collection of tenants, users, and roles. Users may be given a domain's administrator role. A domain administrator may create tenants, users, and groups within a domain and assign roles to users and groups." +msgstr "" + +#: ./doc/common/section_cli_nova_get_console.xml:7(title) +msgid "Get a console to access an instance" +msgstr "" + +#: ./doc/common/section_cli_nova_get_console.xml:8(para) +msgid "To get a VNC console to access an instance, run the following command:" +msgstr "" + +#: ./doc/common/section_cli_nova_get_console.xml:10(para) +msgid "The command returns a URL from which you can access your instance:" +msgstr "" + +#: ./doc/common/section_cli_nova_get_console.xml:16(para) +msgid "To get a non-VNC console, specify the novnc parameter instead of the xvpvnc parameter." +msgstr "" + +#: ./doc/common/section_getstart_telemetry.xml:5(title) +msgid "The Telemetry Service" +msgstr "" + +#: ./doc/common/section_getstart_telemetry.xml:6(para) +msgid "The OpenStack Telemetry service:" +msgstr "" + +#: ./doc/common/section_getstart_telemetry.xml:10(para) +msgid "Efficiently collects the metering data about the CPU and network costs." +msgstr "" + +#: ./doc/common/section_getstart_telemetry.xml:14(para) +msgid "Collects data by monitoring notifications sent from services or by polling the infrastructure." +msgstr "" + +#: ./doc/common/section_getstart_telemetry.xml:18(para) +msgid "Configures the type of collected data to meet various operating requirements. Accessing and inserting the metering data through the REST API." +msgstr "" + +#: ./doc/common/section_getstart_telemetry.xml:23(para) +msgid "Expands the framework to collect custom usage data by additional plug-ins." +msgstr "" + +#: ./doc/common/section_getstart_telemetry.xml:27(para) +msgid "Produces signed metering messages that cannot be repudiated." +msgstr "" + +#: ./doc/common/section_getstart_telemetry.xml:32(para) +msgid "The system consists of the following basic components:" +msgstr "" + +#: ./doc/common/section_getstart_telemetry.xml:36(para) +msgid "A compute agent (ceilometer-agent-compute). Runs on each compute node and polls for resource utilization statistics. There may be other types of agents in the future, but for now we will focus on creating the compute agent." +msgstr "" + +#: ./doc/common/section_getstart_telemetry.xml:44(para) +msgid "A central agent (ceilometer-agent-central). Runs on a central management server to poll for resource utilization statistics for resources not tied to instances or compute nodes." +msgstr "" + +#: ./doc/common/section_getstart_telemetry.xml:51(para) +msgid "A collector (ceilometer-collector). Runs on one or more central management servers to monitor the message queues (for notifications and for metering data coming from the agent). Notification messages are processed and turned into metering messages and sent back out onto the message bus using the appropriate topic. Telemetry messages are written to the data store without modification." +msgstr "" + +#: ./doc/common/section_getstart_telemetry.xml:62(para) +msgid "An alarm notifier (ceilometer-alarm-notifier). Runs on one or more central management servers to allow settting alarms based on threshold evaluation for a collection of samples." +msgstr "" + +#: ./doc/common/section_getstart_telemetry.xml:69(para) +msgid "A data store. A database capable of handling concurrent writes (from one or more collector instances) and reads (from the API server)." +msgstr "" + +#: ./doc/common/section_getstart_telemetry.xml:74(para) +msgid "An API server (ceilometer-api). Runs on one or more central management servers to provide access to the data from the data store. These services communicate using the standard OpenStack messaging bus. Only the collector and API server have access to the data store." +msgstr "" + +#: ./doc/common/section_getstart_telemetry.xml:83(para) +msgid "These services communicate by using the standard OpenStack messaging bus. Only the collector and API server have access to the data store." +msgstr "" + +#: ./doc/common/section_compute-configure-quotas.xml:9(title) +msgid "Configure quotas" +msgstr "" + +#: ./doc/common/section_compute-configure-quotas.xml:10(para) +msgid "To prevent system capacities from being exhausted without notification, you can set up quotas. Quotas are operational limits. For example, the number of gigabytes allowed per tenant can be controlled so that cloud resources are optimized. Quotas are currently enforced at the tenant (or project) level, rather than by user." +msgstr "" + +#: ./doc/common/section_cli_swift_commands.xml:11(title) +msgid "swift commands" +msgstr "" + +#: ./doc/common/section_cli_swift_commands.xml:12(para) +msgid "The swift client is the command-line interface (CLI) for the OpenStack Object Storage API and its extensions." +msgstr "" + +#: ./doc/common/section_cli_swift_commands.xml:20(title) +msgid "swift usage" +msgstr "" + +#: ./doc/common/section_cli_swift_commands.xml:36(title) +msgid "swift positional arguments" +msgstr "" + +#: ./doc/common/section_cli_swift_commands.xml:50(title) +msgid "swift examples" +msgstr "" + +#: ./doc/common/section_cli_swift_commands.xml:61(title) +msgid "swift optional arguments" +msgstr "" + +#: ./doc/common/section_cli_swift_commands.xml:118(title) +msgid "swift delete command" +msgstr "" + +#: ./doc/common/section_cli_swift_commands.xml:200(title) +msgid "swift download command" +msgstr "" + +#: ./doc/common/section_cli_swift_commands.xml:309(title) +msgid "swift list command" +msgstr "" + +#: ./doc/common/section_cli_swift_commands.xml:391(title) +msgid "swift post command" +msgstr "" + +#: ./doc/common/section_cli_swift_commands.xml:491(title) +msgid "swift stat command" +msgstr "" + +#: ./doc/common/section_cli_swift_commands.xml:561(title) +msgid "swift upload command" +msgstr "" + +#: ./doc/common/section_xen-install.xml:6(title) +msgid "Install XenServer and XCP" +msgstr "" + +#: ./doc/common/section_xen-install.xml:8(para) +msgid "Before you can run OpenStack with XCP or XenServer, you must install the software on an appropriate server." +msgstr "" + +#: ./doc/common/section_xen-install.xml:13(para) +msgid "Xen is a type 1 hypervisor: When your server starts, Xen is the first software that runs. Consequently, you must install XenServer or XCP before you install the operating system where you want to run OpenStack code. The OpenStack services then run in a virtual machine that you install on top of XenServer." +msgstr "" + +#: ./doc/common/section_xen-install.xml:20(para) +msgid "Before you can install your system, decide whether to install a free or paid edition of Citrix XenServer or Xen Cloud Platform from Xen.org. Download the software from these locations:" +msgstr "" + +#: ./doc/common/section_xen-install.xml:28(link) +msgid "http://www.citrix.com/XenServer/download" +msgstr "" + +#: ./doc/common/section_xen-install.xml:33(link) +msgid "http://www.xen.org/download/xcp/index.html" +msgstr "" + +#: ./doc/common/section_xen-install.xml:36(para) +msgid "When you install many servers, you might find it easier to perform PXE boot installations of XenServer or XCP. You can also package any post-installation changes that you want to make to your XenServer by creating your own XenServer supplemental pack." +msgstr "" + +#: ./doc/common/section_xen-install.xml:46(para) +msgid "You can also install the xcp-xenapi package on Debian-based distributions to get XCP. However, this is not as mature or feature complete as above distributions. This modifies your boot loader to first boot Xen and boot your existing OS on top of Xen as Dom0. The xapi daemon runs in Dom0. Find more details at http://wiki.xen.org/wiki/Project_Kronos." +msgstr "" + +#: ./doc/common/section_xen-install.xml:55(para) +msgid "Make sure you use the EXT type of storage repository (SR). Features that require access to VHD files (such as copy on write, snapshot and migration) do not work when you use the LVM SR. Storage repository (SR) is a XenAPI-specific term relating to the physical storage where virtual disks are stored." +msgstr "" + +#: ./doc/common/section_xen-install.xml:61(para) +msgid "On the XenServer/XCP installation screen, choose the XenDesktop Optimized option. If you use an answer file, make sure you use srtype=\"ext\" in the tag of the answer file." +msgstr "" + +#: ./doc/common/section_xen-install.xml:69(title) +msgid "Post-installation steps" +msgstr "" + +#: ./doc/common/section_xen-install.xml:70(para) +msgid "Complete these steps to install OpenStack in your XenServer system:" +msgstr "" + +#: ./doc/common/section_xen-install.xml:74(para) +msgid "For resize and migrate functionality, complete the changes described in the Configure resize section in the OpenStack Configuration Reference." +msgstr "" + +#: ./doc/common/section_xen-install.xml:82(para) +msgid "Install the VIF isolation rules to help prevent mac and IP address spoofing." +msgstr "" + +#: ./doc/common/section_xen-install.xml:86(para) +msgid "Install the XenAPI plug-ins. See the following section." +msgstr "" + +#: ./doc/common/section_xen-install.xml:90(para) +msgid "To support AMI type images, you must set up /boot/guest symlink/directory in Dom0. For detailed instructions, see next section." +msgstr "" + +#: ./doc/common/section_xen-install.xml:96(para) +msgid "To support resize/migration, set up an ssh trust relation between your XenServer hosts, and ensure /images is properly set up. See next section for more details." +msgstr "" + +#: ./doc/common/section_xen-install.xml:102(para) +msgid "Create a Paravirtualized virtual machine that can run the OpenStack compute code." +msgstr "" + +#: ./doc/common/section_xen-install.xml:106(para) +msgid "Install and configure the nova-compute in the above virtual machine." +msgstr "" + +#: ./doc/common/section_xen-install.xml:111(para) +msgid "For more information, see how DevStack performs the last three steps for developer deployments. For more information about DevStack, see Getting Started With XenServer and Devstack (https://github.com/openstack-dev/devstack/blob/master/tools/xen/README.md). Find more information about the first step, see Multi Tenancy Networking Protections in XenServer (https://github.com/openstack/nova/blob/master/plugins/xenserver/doc/networking.rst). For information about how to install the XenAPI plug-ins, see XenAPI README (https://github.com/openstack/nova/blob/master/plugins/xenserver/xenapi/README)." +msgstr "" + +#: ./doc/common/section_xen-install.xml:131(title) +msgid "Xen boot from ISO" +msgstr "" + +#: ./doc/common/section_xen-install.xml:132(para) +msgid "XenServer, through the XenAPI integration with OpenStack, provides a feature to boot instances from an ISO file. To activate the Boot From ISO feature, you must configure the SR elements on XenServer host, as follows:" +msgstr "" + +#: ./doc/common/section_xen-install.xml:139(para) +msgid "Create an ISO-typed SR, such as an NFS ISO library, for instance. For this, using XenCenter is a simple method. You must export an NFS volume from a remote NFS server. Make sure it is exported in read-write mode." +msgstr "" + +#: ./doc/common/section_xen-install.xml:146(para) +msgid "On the compute host, find and record the uuid of this ISO SR:" +msgstr "" + +#: ./doc/common/section_xen-install.xml:151(para) +msgid "Locate the uuid of the NFS ISO library:" +msgstr "" + +#: ./doc/common/section_xen-install.xml:155(para) +msgid "Set the uuid and configuration. Even if an NFS mount point is not local, you must specify local-storage-iso." +msgstr "" + +#: ./doc/common/section_xen-install.xml:161(para) +msgid "Make sure the host-uuid from xe pbd-list equals the uuid of the host you found previously:" +msgstr "" + +#: ./doc/common/section_xen-install.xml:167(para) +msgid "You can now add images through the OpenStack Image Service with disk-format=iso, and boot them in OpenStack Compute:" +msgstr "" + +#. When image changes, this message will be marked fuzzy or untranslated for you. +#. It doesn't matter what you translate it to: it's not used at all. +#: ./doc/common/section_getstart_conceptual_arch.xml:16(None) +msgid "@@image: 'figures/openstack_havana_conceptual_arch.png'; md5=96e1d5492d4c865fc9145710bb294a91" +msgstr "" + +#: ./doc/common/section_getstart_conceptual_arch.xml:6(title) +msgid "Conceptual architecture" +msgstr "" + +#: ./doc/common/section_getstart_conceptual_arch.xml:7(para) +msgid "The following diagram shows the relationships among the OpenStack services:" +msgstr "" + +#: ./doc/common/section_getstart_conceptual_arch.xml:11(title) +msgid "OpenStack conceptual architecture" +msgstr "" + +#: ./doc/common/section_cli_nova_metadata.xml:9(title) +msgid "Insert metadata during launch" +msgstr "" + +#: ./doc/common/section_cli_nova_metadata.xml:10(para) +msgid "When booting a server, you can also add metadata, so that you can more easily identify it amongst your ever-growing elastic cloud. Use the --meta option with a key=value pair, where you can make up the string for both the key and the value. For example, you could add a description and also the creator of the server. " +msgstr "" + +#: ./doc/common/section_cli_nova_metadata.xml:18(para) +msgid "When viewing the server information, you can see the metadata included on the metadata line: " +msgstr "" + +#. When image changes, this message will be marked fuzzy or untranslated for you. +#. It doesn't matter what you translate it to: it's not used at all. +#: ./doc/common/section_objectstorage-arch.xml:20(None) +msgid "@@image: '../common/figures/objectstorage-arch.png'; md5=90f6c7cf3947d7987eeb55d657cdc927" +msgstr "" + +#. When image changes, this message will be marked fuzzy or untranslated for you. +#. It doesn't matter what you translate it to: it's not used at all. +#: ./doc/common/section_objectstorage-arch.xml:57(None) +msgid "@@image: '../common/figures/objectstorage-nodes.png'; md5=2aa7eb3bddcf6826f33469920dc2a9c3" +msgstr "" + +#. ... Old module003-ch007-swift-cluster-architecture edited, renamed, and stored in doc/common for use by both Cloud Admin and Operator Training Guides... +#: ./doc/common/section_objectstorage-arch.xml:8(title) +msgid "Cluster architecture" +msgstr "" + +#: ./doc/common/section_objectstorage-arch.xml:10(title) +msgid "Access tier" +msgstr "" + +#: ./doc/common/section_objectstorage-arch.xml:11(para) +msgid "Large-scale deployments segment off an access tier, which is considered the Object Storage system's central hub. The access tier fields the incoming API requests from clients and moves data in and out of the system. This tier consists of front-end load balancers, ssl-terminators, and authentication services. It runs the (distributed) brain of the Object Storage system—the proxy server processes." +msgstr "" + +#: ./doc/common/section_objectstorage-arch.xml:17(title) +msgid "Object Storage architecture" +msgstr "" + +#: ./doc/common/section_objectstorage-arch.xml:24(para) +msgid "Because access servers are collocated in their own tier, you can scale out read/write access regardless of the storage capacity. For example, if a cluster is on the public Internet, requires SSL termination, and has a high demand for data access, you can provision many access servers. However, if the cluster is on a private network and used primarily for archival purposes, you need fewer access servers." +msgstr "" + +#: ./doc/common/section_objectstorage-arch.xml:29(para) +msgid "Since this is an HTTP addressable storage service, you may incorporate a load balancer into the access tier." +msgstr "" + +#: ./doc/common/section_objectstorage-arch.xml:31(para) +msgid "Typically, the tier consists of a collection of 1U servers. These machines use a moderate amount of RAM and are network I/O intensive. Since these systems field each incoming API request, you should provision them with two high-throughput (10GbE) interfaces—one for the incoming \"front-end\" requests and the other for the \"back-end\" access to the object storage nodes to put and fetch data." +msgstr "" + +#: ./doc/common/section_objectstorage-arch.xml:37(title) ./doc/common/section_objectstorage-arch.xml:65(title) +msgid "Factors to consider" +msgstr "" + +#: ./doc/common/section_objectstorage-arch.xml:38(para) +msgid "For most publicly facing deployments as well as private deployments available across a wide-reaching corporate network, you use SSL to encrypt traffic to the client. SSL adds significant processing load to establish sessions between clients, which is why you have to provision more capacity in the access layer. SSL may not be required for private deployments on trusted networks." +msgstr "" + +#: ./doc/common/section_objectstorage-arch.xml:46(title) +msgid "Storage nodes" +msgstr "" + +#: ./doc/common/section_objectstorage-arch.xml:47(para) +msgid "In most configurations, each of the five zones should have an equal amount of storage capacity. Storage nodes use a reasonable amount of memory and CPU. Metadata needs to be readily available to return objects quickly. The object stores run services not only to field incoming requests from the access tier, but to also run replicators, auditors, and reapers. You can provision object stores provisioned with single gigabit or 10 gigabit network interface depending on the expected workload and desired performance." +msgstr "" + +#: ./doc/common/section_objectstorage-arch.xml:54(title) ./doc/common/section_storage-concepts.xml:17(td) ./doc/common/section_objectstorage-characteristics.xml:47(title) +msgid "Object Storage (Swift)" +msgstr "" + +#: ./doc/common/section_objectstorage-arch.xml:61(para) +msgid "Currently, 2TB or 3TB SATA disks deliver good price/performance value. You can use desktop-grade drives if you have responsive remote hands in the datacenter and enterprise-grade drives if you don't." +msgstr "" + +#: ./doc/common/section_objectstorage-arch.xml:66(para) +msgid "You should keep in mind the desired I/O performance for single-threaded requests . This system does not use RAID, so a single disk handles each request for an object. Disk performance impacts single-threaded response rates." +msgstr "" + +#: ./doc/common/section_objectstorage-arch.xml:69(para) +msgid "To achieve apparent higher throughput, the object storage system is designed to handle concurrent uploads/downloads. The network I/O capacity (1GbE, bonded 1GbE pair, or 10GbE) should match your desired concurrent throughput needs for reads and writes." +msgstr "" + +#: ./doc/common/section_dochistory.xml:6(title) +msgid "Document change history" +msgstr "" + +#: ./doc/common/section_dochistory.xml:8(para) +msgid "This version of the guide replaces and obsoletes all previous versions. The following table describes the most recent changes:" +msgstr "" + +#: ./doc/common/section_cli_nova_host_aggregates.xml:6(title) +msgid "Host aggregates" +msgstr "" + +#: ./doc/common/section_cli_nova_host_aggregates.xml:7(para) +msgid "Host aggregates are a mechanism to further partition an availability zone; while availability zones are visible to users, host aggregates are only visible to administrators. Host Aggregates provide a mechanism to allow administrators to assign key-value pairs to groups of machines. Each node can have multiple aggregates, each aggregate can have multiple key-value pairs, and the same key-value pair can be assigned to multiple aggregates. This information can be used in the scheduler to enable advanced scheduling, to set up hypervisor resource pools or to define logical groups for migration." +msgstr "" + +#: ./doc/common/section_cli_nova_host_aggregates.xml:19(title) +msgid "Command-line interface" +msgstr "" + +#: ./doc/common/section_cli_nova_host_aggregates.xml:26(para) +msgid "Print a list of all aggregates." +msgstr "" + +#: ./doc/common/section_cli_nova_host_aggregates.xml:31(replaceable) ./doc/common/section_cli_nova_host_aggregates.xml:107(replaceable) +msgid "<name>" +msgstr "" + +#: ./doc/common/section_cli_nova_host_aggregates.xml:32(replaceable) +msgid "<availability-zone>" +msgstr "" + +#: ./doc/common/section_cli_nova_host_aggregates.xml:34(para) +msgid "Create a new aggregate named <name> in availability zone <availability-zone>. Returns the ID of the newly created aggregate. Hosts can be made available to multiple availability zones, but administrators should be careful when adding the host to a different host aggregate within the same availability zone and pay attention when using the and commands to avoid user confusion when they boot instances in different availability zones. An error occurs if you cannot add a particular host to an aggregate zone for which it is not intended." +msgstr "" + +#: ./doc/common/section_cli_nova_host_aggregates.xml:56(replaceable) ./doc/common/section_cli_nova_host_aggregates.xml:64(replaceable) ./doc/common/section_cli_nova_host_aggregates.xml:72(replaceable) ./doc/common/section_cli_nova_host_aggregates.xml:83(replaceable) ./doc/common/section_cli_nova_host_aggregates.xml:94(replaceable) ./doc/common/section_cli_nova_host_aggregates.xml:106(replaceable) +msgid "<id>" +msgstr "" + +#: ./doc/common/section_cli_nova_host_aggregates.xml:58(para) +msgid "Delete an aggregate with id <id>." +msgstr "" + +#: ./doc/common/section_cli_nova_host_aggregates.xml:66(para) +msgid "Show details of the aggregate with id <id>." +msgstr "" + +#: ./doc/common/section_cli_nova_host_aggregates.xml:73(replaceable) ./doc/common/section_cli_nova_host_aggregates.xml:84(replaceable) +msgid "<host>" +msgstr "" + +#: ./doc/common/section_cli_nova_host_aggregates.xml:75(para) +msgid "Add host with name <host> to aggregate with id <id>." +msgstr "" + +#: ./doc/common/section_cli_nova_host_aggregates.xml:86(para) +msgid "Remove the host with name <host> from the aggregate with id <id>." +msgstr "" + +#: ./doc/common/section_cli_nova_host_aggregates.xml:95(replaceable) ./doc/common/section_cli_nova_host_aggregates.xml:96(replaceable) +msgid "<key=value>" +msgstr "" + +#: ./doc/common/section_cli_nova_host_aggregates.xml:99(para) +msgid "Add or update metadata (key-value pairs) associated with the aggregate with id <id>." +msgstr "" + +#: ./doc/common/section_cli_nova_host_aggregates.xml:108(replaceable) +msgid "<availability_zone>" +msgstr "" + +#: ./doc/common/section_cli_nova_host_aggregates.xml:110(para) +msgid "Update the name and availability zone (optional) for the aggregate." +msgstr "" + +#: ./doc/common/section_cli_nova_host_aggregates.xml:117(para) +msgid "List all hosts by service." +msgstr "" + +#: ./doc/common/section_cli_nova_host_aggregates.xml:124(para) +msgid "Put/resume host into/from maintenance." +msgstr "" + +#: ./doc/common/section_cli_nova_host_aggregates.xml:20(para) +msgid "The command-line tool supports the following aggregate-related commands. " +msgstr "" + +#: ./doc/common/section_cli_nova_host_aggregates.xml:130(para) +msgid "Only administrators can access these commands. If you try to use these commands and the user name and tenant that you use to access the Compute service do not have the admin role or the appropriate privileges, these errors occur:" +msgstr "" + +#: ./doc/common/section_cli_nova_host_aggregates.xml:142(title) +msgid "Configure scheduler to support host aggregates" +msgstr "" + +#: ./doc/common/section_cli_nova_host_aggregates.xml:143(para) +msgid "One common use case for host aggregates is when you want to support scheduling instances to a subset of compute hosts because they have a specific capability. For example, you may want to allow users to request compute hosts that have SSD drives if they need access to faster disk I/O, or access to compute hosts that have GPU cards to take advantage of GPU-accelerated code." +msgstr "" + +#: ./doc/common/section_cli_nova_host_aggregates.xml:150(para) +msgid "To configure the scheduler to support host aggregates, the scheduler_default_filters configuration option must contain the AggregateInstanceExtraSpecsFilter in addition to the other filters used by the scheduler. Add the following line to /etc/nova/nova.conf on the host that runs the nova-scheduler service to enable host aggregates filtering, as well as the other filters that are typically enabled:" +msgstr "" + +#: ./doc/common/section_cli_nova_host_aggregates.xml:164(title) +msgid "Example: Specify compute hosts with SSDs" +msgstr "" + +#: ./doc/common/section_cli_nova_host_aggregates.xml:165(para) +msgid "This example configures the Compute service to enable users to request nodes that have solid-state drives (SSDs). You create a fast-io host aggregate in the nova availability zone and you add the ssd=true key-value pair to the aggregate. Then, you add the node1, and node2 compute nodes to it." +msgstr "" + +#: ./doc/common/section_cli_nova_host_aggregates.xml:201(para) +msgid "Use the command to create the ssd.large flavor called with an ID of 6, 8GB of RAM, 80GB root disk, and 4 vCPUs." +msgstr "" + +#: ./doc/common/section_cli_nova_host_aggregates.xml:211(para) +msgid "Once the flavor is created, specify one or more key-value pairs that match the key-value pairs on the host aggregates. In this case, that is the ssd=true key-value pair. Setting a key-value pair on a flavor is done using the command." +msgstr "" + +#: ./doc/common/section_cli_nova_host_aggregates.xml:218(para) +msgid "Once it is set, you should see the extra_specs property of the ssd.large flavor populated with a key of ssd and a corresponding value of true." +msgstr "" + +#: ./doc/common/section_cli_nova_host_aggregates.xml:239(para) +msgid "Now, when a user requests an instance with the ssd.large flavor, the scheduler only considers hosts with the ssd=true key-value pair. In this example, these are node1 and node2." +msgstr "" + +#: ./doc/common/section_cli_nova_host_aggregates.xml:247(title) +msgid "XenServer hypervisor pools to support live migration" +msgstr "" + +#: ./doc/common/section_cli_nova_host_aggregates.xml:249(para) +msgid "When using the XenAPI-based hypervisor, the Compute service uses host aggregates to manage XenServer Resource pools, which are used in supporting live migration." +msgstr "" + +#: ./doc/common/section_keystone_db_sync.xml:6(title) +msgid "Migrate the Identity Service database" +msgstr "" + +#: ./doc/common/section_keystone_db_sync.xml:7(para) +msgid "Between revisions of the Identity Service project, you might need to complete SQL migrations. The Identity Service project uses SQLAlchemy-migrate (see http://code.google.com/p/sqlalchemy-migrate/) to migrate the SQL database between revisions. For core components, the source code stores migrations in a central repository under a keystone/common/sql/migrate_repo directory." +msgstr "" + +#: ./doc/common/section_keystone_db_sync.xml:17(para) +msgid "Extensions to the Identity Service might also require SQL migrations. The directory keystone/contrib/example in the keystone repository contains a sample extension migration." +msgstr "" + +#: ./doc/common/section_keystone_db_sync.xml:23(title) +msgid "To set up a migration for an extension" +msgstr "" + +#: ./doc/common/section_keystone_db_sync.xml:25(para) +msgid "Create a directory structure where my_extension is the name of the extension, as follows: keystone/contrib/my_extension/migrate_repo/versions/." +msgstr "" + +#: ./doc/common/section_keystone_db_sync.xml:31(para) +msgid "Create empty __init__.py files in the migrate_repo and versions subdirectories." +msgstr "" + +#: ./doc/common/section_keystone_db_sync.xml:37(para) +msgid "Create a migrate.cfg configuration file in the migrate_repo subdirectory, which conforms to a key/value .ini file format." +msgstr "" + +#: ./doc/common/section_keystone_db_sync.xml:41(para) +msgid "An example configuration file:" +msgstr "" + +#: ./doc/common/section_keystone_db_sync.xml:49(title) +msgid "To test a migration for a specific extension" +msgstr "" + +#: ./doc/common/section_keystone_db_sync.xml:50(para) +msgid "You can use the command with the --extension parameter for both the and commands. Ensure that the required configuration files exist before completing these steps." +msgstr "" + +#: ./doc/common/section_keystone_db_sync.xml:57(para) +msgid "Test your migrations with an example extension:" +msgstr "" + +#: ./doc/common/section_keystone_db_sync.xml:62(para) +msgid "Migrate to version 1:" +msgstr "" + +#: ./doc/common/section_keystone_db_sync.xml:66(para) +msgid "Migrate back to version 0:" +msgstr "" + +#: ./doc/common/section_keystone_db_sync.xml:70(para) +msgid "Check the version:" +msgstr "" + +#: ./doc/common/section_cli_neutron_commands.xml:11(title) +msgid "neutron commands" +msgstr "" + +#: ./doc/common/section_cli_neutron_commands.xml:12(para) +msgid "The neutron client is the command-line interface (CLI) for the OpenStack Networking API and its extensions." +msgstr "" + +#: ./doc/common/section_cli_neutron_commands.xml:20(title) +msgid "neutron usage" +msgstr "" + +#: ./doc/common/section_cli_neutron_commands.xml:218(title) +msgid "neutron agent-delete command" +msgstr "" + +#: ./doc/common/section_cli_neutron_commands.xml:234(title) +msgid "neutron agent-list command" +msgstr "" + +#: ./doc/common/section_cli_neutron_commands.xml:265(title) +msgid "neutron agent-show command" +msgstr "" + +#: ./doc/common/section_cli_neutron_commands.xml:302(title) +msgid "neutron agent-update command" +msgstr "" + +#: ./doc/common/section_cli_neutron_commands.xml:318(title) +msgid "neutron cisco-credential-create command" +msgstr "" + +#: ./doc/common/section_cli_neutron_commands.xml:359(title) +msgid "neutron cisco-credential-delete command" +msgstr "" + +#: ./doc/common/section_cli_neutron_commands.xml:376(title) +msgid "neutron cisco-credential-list command" +msgstr "" + +#: ./doc/common/section_cli_neutron_commands.xml:408(title) +msgid "neutron cisco-credential-show command" +msgstr "" + +#: ./doc/common/section_cli_neutron_commands.xml:446(title) +msgid "neutron cisco-network-profile-create command" +msgstr "" + +#: ./doc/common/section_cli_neutron_commands.xml:502(title) +msgid "neutron cisco-network-profile-delete command" +msgstr "" + +#: ./doc/common/section_cli_neutron_commands.xml:519(title) +msgid "neutron cisco-network-profile-list command" +msgstr "" + +#: ./doc/common/section_cli_neutron_commands.xml:551(title) +msgid "neutron cisco-network-profile-show command" +msgstr "" + +#: ./doc/common/section_cli_neutron_commands.xml:590(title) +msgid "neutron cisco-network-profile-update command" +msgstr "" + +#: ./doc/common/section_cli_neutron_commands.xml:607(title) +msgid "neutron cisco-policy-profile-list command" +msgstr "" + +#: ./doc/common/section_cli_neutron_commands.xml:639(title) +msgid "neutron cisco-policy-profile-show command" +msgstr "" + +#: ./doc/common/section_cli_neutron_commands.xml:678(title) +msgid "neutron cisco-policy-profile-update command" +msgstr "" + +#: ./doc/common/section_cli_neutron_commands.xml:695(title) +msgid "neutron dhcp-agent-list-hosting-net command" +msgstr "" + +#: ./doc/common/section_cli_neutron_commands.xml:731(title) +msgid "neutron dhcp-agent-network-add command" +msgstr "" + +#: ./doc/common/section_cli_neutron_commands.xml:749(title) +msgid "neutron dhcp-agent-network-remove command" +msgstr "" + +#: ./doc/common/section_cli_neutron_commands.xml:767(title) +msgid "neutron ext-list command" +msgstr "" + +#: ./doc/common/section_cli_neutron_commands.xml:798(title) +msgid "neutron ext-show command" +msgstr "" + +#: ./doc/common/section_cli_neutron_commands.xml:835(title) +msgid "neutron firewall-create command" +msgstr "" + +#: ./doc/common/section_cli_neutron_commands.xml:878(title) +msgid "neutron firewall-delete command" +msgstr "" + +#: ./doc/common/section_cli_neutron_commands.xml:894(title) +msgid "neutron firewall-list command" +msgstr "" + +#: ./doc/common/section_cli_neutron_commands.xml:938(title) +msgid "neutron firewall-policy-create command" +msgstr "" + +#: ./doc/common/section_cli_neutron_commands.xml:984(title) +msgid "neutron firewall-policy-delete command" +msgstr "" + +#: ./doc/common/section_cli_neutron_commands.xml:1001(title) +msgid "neutron firewall-policy-insert-rule command" +msgstr "" + +#: ./doc/common/section_cli_neutron_commands.xml:1025(title) +msgid "neutron firewall-policy-list command" +msgstr "" + +#: ./doc/common/section_cli_neutron_commands.xml:1069(title) +msgid "neutron firewall-policy-remove-rule command" +msgstr "" + +#: ./doc/common/section_cli_neutron_commands.xml:1087(title) +msgid "neutron firewall-policy-show command" +msgstr "" + +#: ./doc/common/section_cli_neutron_commands.xml:1125(title) +msgid "neutron firewall-policy-update command" +msgstr "" + +#: ./doc/common/section_cli_neutron_commands.xml:1142(title) +msgid "neutron firewall-rule-create command" +msgstr "" + +#: ./doc/common/section_cli_neutron_commands.xml:1199(title) +msgid "neutron firewall-rule-delete command" +msgstr "" + +#: ./doc/common/section_cli_neutron_commands.xml:1216(title) +msgid "neutron firewall-rule-list command" +msgstr "" + +#: ./doc/common/section_cli_neutron_commands.xml:1260(title) +msgid "neutron firewall-rule-show command" +msgstr "" + +#: ./doc/common/section_cli_neutron_commands.xml:1298(title) +msgid "neutron firewall-rule-update command" +msgstr "" + +#: ./doc/common/section_cli_neutron_commands.xml:1318(title) +msgid "neutron firewall-show command" +msgstr "" + +#: ./doc/common/section_cli_neutron_commands.xml:1355(title) +msgid "neutron firewall-update command" +msgstr "" + +#: ./doc/common/section_cli_neutron_commands.xml:1371(title) +msgid "neutron floatingip-associate command" +msgstr "" + +#: ./doc/common/section_cli_neutron_commands.xml:1394(title) +msgid "neutron floatingip-create command" +msgstr "" + +#: ./doc/common/section_cli_neutron_commands.xml:1435(title) +msgid "neutron floatingip-delete command" +msgstr "" + +#: ./doc/common/section_cli_neutron_commands.xml:1451(title) +msgid "neutron floatingip-disassociate command" +msgstr "" + +#: ./doc/common/section_cli_neutron_commands.xml:1468(title) +msgid "neutron floatingip-list command" +msgstr "" + +#: ./doc/common/section_cli_neutron_commands.xml:1512(title) +msgid "neutron floatingip-show command" +msgstr "" + +#: ./doc/common/section_cli_neutron_commands.xml:1549(title) +msgid "neutron ipsec-site-connection-create command" +msgstr "" + +#: ./doc/common/section_cli_neutron_commands.xml:1620(title) +msgid "neutron ipsec-site-connection-delete command" +msgstr "" + +#: ./doc/common/section_cli_neutron_commands.xml:1638(title) +msgid "neutron ipsec-site-connection-list command" +msgstr "" + +#: ./doc/common/section_cli_neutron_commands.xml:1683(title) +msgid "neutron ipsec-site-connection-show command" +msgstr "" + +#: ./doc/common/section_cli_neutron_commands.xml:1723(title) +msgid "neutron ipsec-site-connection-update command" +msgstr "" + +#: ./doc/common/section_cli_neutron_commands.xml:1749(title) +msgid "neutron l3-agent-list-hosting-router command" +msgstr "" + +#: ./doc/common/section_cli_neutron_commands.xml:1785(title) +msgid "neutron l3-agent-router-add command" +msgstr "" + +#: ./doc/common/section_cli_neutron_commands.xml:1803(title) +msgid "neutron l3-agent-router-remove command" +msgstr "" + +#: ./doc/common/section_cli_neutron_commands.xml:1821(title) +msgid "neutron lb-agent-hosting-pool command" +msgstr "" + +#: ./doc/common/section_cli_neutron_commands.xml:1859(title) +msgid "neutron lb-healthmonitor-associate command" +msgstr "" + +#: ./doc/common/section_cli_neutron_commands.xml:1878(title) +msgid "neutron lb-healthmonitor-create command" +msgstr "" + +#: ./doc/common/section_cli_neutron_commands.xml:1938(title) +msgid "neutron lb-healthmonitor-delete command" +msgstr "" + +#: ./doc/common/section_cli_neutron_commands.xml:1955(title) +msgid "neutron lb-healthmonitor-disassociate command" +msgstr "" + +#: ./doc/common/section_cli_neutron_commands.xml:1975(title) +msgid "neutron lb-healthmonitor-list command" +msgstr "" + +#: ./doc/common/section_cli_neutron_commands.xml:2019(title) +msgid "neutron lb-healthmonitor-show command" +msgstr "" + +#: ./doc/common/section_cli_neutron_commands.xml:2057(title) +msgid "neutron lb-healthmonitor-update command" +msgstr "" + +#: ./doc/common/section_cli_neutron_commands.xml:2074(title) +msgid "neutron lb-member-create command" +msgstr "" + +#: ./doc/common/section_cli_neutron_commands.xml:2119(title) +msgid "neutron lb-member-delete command" +msgstr "" + +#: ./doc/common/section_cli_neutron_commands.xml:2135(title) +msgid "neutron lb-member-list command" +msgstr "" + +#: ./doc/common/section_cli_neutron_commands.xml:2179(title) +msgid "neutron lb-member-show command" +msgstr "" + +#: ./doc/common/section_cli_neutron_commands.xml:2216(title) +msgid "neutron lb-member-update command" +msgstr "" + +#: ./doc/common/section_cli_neutron_commands.xml:2232(title) +msgid "neutron lb-pool-create command" +msgstr "" + +#: ./doc/common/section_cli_neutron_commands.xml:2280(title) +msgid "neutron lb-pool-delete command" +msgstr "" + +#: ./doc/common/section_cli_neutron_commands.xml:2296(title) +msgid "neutron lb-pool-list command" +msgstr "" + +#: ./doc/common/section_cli_neutron_commands.xml:2340(title) +msgid "neutron lb-pool-list-on-agent command" +msgstr "" + +#: ./doc/common/section_cli_neutron_commands.xml:2376(title) +msgid "neutron lb-pool-show command" +msgstr "" + +#: ./doc/common/section_cli_neutron_commands.xml:2413(title) +msgid "neutron lb-pool-stats command" +msgstr "" + +#: ./doc/common/section_cli_neutron_commands.xml:2450(title) +msgid "neutron lb-pool-update command" +msgstr "" + +#: ./doc/common/section_cli_neutron_commands.xml:2466(title) +msgid "neutron lb-vip-create command" +msgstr "" + +#: ./doc/common/section_cli_neutron_commands.xml:2522(title) +msgid "neutron lb-vip-delete command" +msgstr "" + +#: ./doc/common/section_cli_neutron_commands.xml:2538(title) +msgid "neutron lb-vip-list command" +msgstr "" + +#: ./doc/common/section_cli_neutron_commands.xml:2582(title) +msgid "neutron lb-vip-show command" +msgstr "" + +#: ./doc/common/section_cli_neutron_commands.xml:2619(title) +msgid "neutron lb-vip-update command" +msgstr "" + +#: ./doc/common/section_cli_neutron_commands.xml:2635(title) +msgid "neutron meter-label-create command" +msgstr "" + +#: ./doc/common/section_cli_neutron_commands.xml:2674(title) +msgid "neutron meter-label-delete command" +msgstr "" + +#: ./doc/common/section_cli_neutron_commands.xml:2691(title) +msgid "neutron meter-label-list command" +msgstr "" + +#: ./doc/common/section_cli_neutron_commands.xml:2735(title) +msgid "neutron meter-label-rule-create command" +msgstr "" + +#: ./doc/common/section_cli_neutron_commands.xml:2777(title) +msgid "neutron meter-label-rule-delete command" +msgstr "" + +#: ./doc/common/section_cli_neutron_commands.xml:2794(title) +msgid "neutron meter-label-rule-list command" +msgstr "" + +#: ./doc/common/section_cli_neutron_commands.xml:2838(title) +msgid "neutron meter-label-rule-show command" +msgstr "" + +#: ./doc/common/section_cli_neutron_commands.xml:2876(title) +msgid "neutron meter-label-show command" +msgstr "" + +#: ./doc/common/section_cli_neutron_commands.xml:2913(title) +msgid "neutron net-create command" +msgstr "" + +#: ./doc/common/section_cli_neutron_commands.xml:2952(title) +msgid "neutron net-delete command" +msgstr "" + +#: ./doc/common/section_cli_neutron_commands.xml:2968(title) +msgid "neutron net-external-list command" +msgstr "" + +#: ./doc/common/section_cli_neutron_commands.xml:3012(title) +msgid "neutron net-gateway-connect command" +msgstr "" + +#: ./doc/common/section_cli_neutron_commands.xml:3038(title) +msgid "neutron net-gateway-create command" +msgstr "" + +#: ./doc/common/section_cli_neutron_commands.xml:3077(title) +msgid "neutron net-gateway-delete command" +msgstr "" + +#: ./doc/common/section_cli_neutron_commands.xml:3094(title) +msgid "neutron net-gateway-disconnect command" +msgstr "" + +#: ./doc/common/section_cli_neutron_commands.xml:3120(title) +msgid "neutron net-gateway-list command" +msgstr "" + +#: ./doc/common/section_cli_neutron_commands.xml:3151(title) +msgid "neutron net-gateway-show command" +msgstr "" + +#: ./doc/common/section_cli_neutron_commands.xml:3188(title) +msgid "neutron net-gateway-update command" +msgstr "" + +#: ./doc/common/section_cli_neutron_commands.xml:3205(title) +msgid "neutron net-list command" +msgstr "" + +#: ./doc/common/section_cli_neutron_commands.xml:3248(title) +msgid "neutron net-list-on-dhcp-agent command" +msgstr "" + +#: ./doc/common/section_cli_neutron_commands.xml:3296(title) +msgid "neutron net-show command" +msgstr "" + +#: ./doc/common/section_cli_neutron_commands.xml:3333(title) +msgid "neutron net-update command" +msgstr "" + +#: ./doc/common/section_cli_neutron_commands.xml:3349(title) +msgid "neutron port-create command" +msgstr "" + +#: ./doc/common/section_cli_neutron_commands.xml:3408(title) +msgid "neutron port-delete command" +msgstr "" + +#: ./doc/common/section_cli_neutron_commands.xml:3424(title) +msgid "neutron port-list command" +msgstr "" + +#: ./doc/common/section_cli_neutron_commands.xml:3467(title) +msgid "neutron port-show command" +msgstr "" + +#: ./doc/common/section_cli_neutron_commands.xml:3504(title) +msgid "neutron port-update command" +msgstr "" + +#: ./doc/common/section_cli_neutron_commands.xml:3531(title) +msgid "neutron queue-create command" +msgstr "" + +#: ./doc/common/section_cli_neutron_commands.xml:3576(title) +msgid "neutron queue-delete command" +msgstr "" + +#: ./doc/common/section_cli_neutron_commands.xml:3592(title) +msgid "neutron queue-list command" +msgstr "" + +#: ./doc/common/section_cli_neutron_commands.xml:3623(title) +msgid "neutron queue-show command" +msgstr "" + +#: ./doc/common/section_cli_neutron_commands.xml:3660(title) +msgid "neutron quota-delete command" +msgstr "" + +#: ./doc/common/section_cli_neutron_commands.xml:3676(title) +msgid "neutron quota-list command" +msgstr "" + +#: ./doc/common/section_cli_neutron_commands.xml:3703(title) +msgid "neutron quota-show command" +msgstr "" + +#: ./doc/common/section_cli_neutron_commands.xml:3735(title) +msgid "neutron quota-update command" +msgstr "" + +#: ./doc/common/section_cli_neutron_commands.xml:3781(title) +msgid "neutron router-create command" +msgstr "" + +#: ./doc/common/section_cli_neutron_commands.xml:3819(title) +msgid "neutron router-delete command" +msgstr "" + +#: ./doc/common/section_cli_neutron_commands.xml:3835(title) +msgid "neutron router-gateway-clear command" +msgstr "" + +#: ./doc/common/section_cli_neutron_commands.xml:3852(title) +msgid "neutron router-gateway-set command" +msgstr "" + +#: ./doc/common/section_cli_neutron_commands.xml:3872(title) +msgid "neutron router-interface-add command" +msgstr "" + +#: ./doc/common/section_cli_neutron_commands.xml:3893(title) +msgid "neutron router-interface-delete command" +msgstr "" + +#: ./doc/common/section_cli_neutron_commands.xml:3914(title) +msgid "neutron router-list command" +msgstr "" + +#: ./doc/common/section_cli_neutron_commands.xml:3958(title) +msgid "neutron router-list-on-l3-agent command" +msgstr "" + +#: ./doc/common/section_cli_neutron_commands.xml:3994(title) +msgid "neutron router-port-list command" +msgstr "" + +#: ./doc/common/section_cli_neutron_commands.xml:4042(title) +msgid "neutron router-show command" +msgstr "" + +#: ./doc/common/section_cli_neutron_commands.xml:4079(title) +msgid "neutron router-update command" +msgstr "" + +#: ./doc/common/section_cli_neutron_commands.xml:4095(title) +msgid "neutron security-group-create command" +msgstr "" + +#: ./doc/common/section_cli_neutron_commands.xml:4134(title) +msgid "neutron security-group-delete command" +msgstr "" + +#: ./doc/common/section_cli_neutron_commands.xml:4151(title) +msgid "neutron security-group-list command" +msgstr "" + +#: ./doc/common/section_cli_neutron_commands.xml:4195(title) +msgid "neutron security-group-rule-create command" +msgstr "" + +#: ./doc/common/section_cli_neutron_commands.xml:4252(title) +msgid "neutron security-group-rule-delete command" +msgstr "" + +#: ./doc/common/section_cli_neutron_commands.xml:4269(title) +msgid "neutron security-group-rule-list command" +msgstr "" + +#: ./doc/common/section_cli_neutron_commands.xml:4316(title) +msgid "neutron security-group-rule-show command" +msgstr "" + +#: ./doc/common/section_cli_neutron_commands.xml:4355(title) +msgid "neutron security-group-show command" +msgstr "" + +#: ./doc/common/section_cli_neutron_commands.xml:4393(title) +msgid "neutron security-group-update command" +msgstr "" + +#: ./doc/common/section_cli_neutron_commands.xml:4414(title) +msgid "neutron service-provider-list command" +msgstr "" + +#: ./doc/common/section_cli_neutron_commands.xml:4458(title) +msgid "neutron subnet-create command" +msgstr "" + +#: ./doc/common/section_cli_neutron_commands.xml:4514(title) +msgid "neutron subnet-delete command" +msgstr "" + +#: ./doc/common/section_cli_neutron_commands.xml:4530(title) +msgid "neutron subnet-list command" +msgstr "" + +#: ./doc/common/section_cli_neutron_commands.xml:4574(title) +msgid "neutron subnet-show command" +msgstr "" + +#: ./doc/common/section_cli_neutron_commands.xml:4611(title) +msgid "neutron subnet-update command" +msgstr "" + +#: ./doc/common/section_cli_neutron_commands.xml:4627(title) +msgid "neutron vpn-ikepolicy-create command" +msgstr "" + +#: ./doc/common/section_cli_neutron_commands.xml:4686(title) +msgid "neutron vpn-ikepolicy-delete command" +msgstr "" + +#: ./doc/common/section_cli_neutron_commands.xml:4703(title) +msgid "neutron vpn-ikepolicy-list command" +msgstr "" + +#: ./doc/common/section_cli_neutron_commands.xml:4747(title) +msgid "neutron vpn-ikepolicy-show command" +msgstr "" + +#: ./doc/common/section_cli_neutron_commands.xml:4785(title) +msgid "neutron vpn-ikepolicy-update command" +msgstr "" + +#: ./doc/common/section_cli_neutron_commands.xml:4807(title) +msgid "neutron vpn-ipsecpolicy-create command" +msgstr "" + +#: ./doc/common/section_cli_neutron_commands.xml:4866(title) +msgid "neutron vpn-ipsecpolicy-delete command" +msgstr "" + +#: ./doc/common/section_cli_neutron_commands.xml:4883(title) +msgid "neutron vpn-ipsecpolicy-list command" +msgstr "" + +#: ./doc/common/section_cli_neutron_commands.xml:4927(title) +msgid "neutron vpn-ipsecpolicy-show command" +msgstr "" + +#: ./doc/common/section_cli_neutron_commands.xml:4965(title) +msgid "neutron vpn-ipsecpolicy-update command" +msgstr "" + +#: ./doc/common/section_cli_neutron_commands.xml:4987(title) +msgid "neutron vpn-service-create command" +msgstr "" + +#: ./doc/common/section_cli_neutron_commands.xml:5029(title) +msgid "neutron vpn-service-delete command" +msgstr "" + +#: ./doc/common/section_cli_neutron_commands.xml:5046(title) +msgid "neutron vpn-service-list command" +msgstr "" + +#: ./doc/common/section_cli_neutron_commands.xml:5090(title) +msgid "neutron vpn-service-show command" +msgstr "" + +#: ./doc/common/section_cli_neutron_commands.xml:5127(title) +msgid "neutron vpn-service-update command" +msgstr "" + +#: ./doc/common/section_cli_neutron-quotas.xml:6(title) +msgid "Manage Networking service quotas" +msgstr "" + +#: ./doc/common/section_cli_neutron-quotas.xml:7(para) +msgid "A quota limits the number of available resources. A default quota might be enforced for all tenants. When you try to create more resources than the quota allows, an error occurs:" +msgstr "" + +#: ./doc/common/section_cli_neutron-quotas.xml:12(para) +msgid "Per-tenant quota configuration is also supported by the quota extension API. See Per-tenant quota configuration for details." +msgstr "" + +#: ./doc/common/section_cli_neutron-quotas.xml:16(title) +msgid "Basic quota configuration" +msgstr "" + +#: ./doc/common/section_cli_neutron-quotas.xml:17(para) +msgid "In the Networking default quota mechanism, all tenants have the same quota values, such as the number of resources that a tenant can create." +msgstr "" + +#: ./doc/common/section_cli_neutron-quotas.xml:20(para) +msgid "The quota value is defined in the OpenStack Networking neutron.conf configuration file. To disable quotas for a specific resource, such as network, subnet, or port, remove a corresponding item from . This example shows the default quota values:" +msgstr "" + +#: ./doc/common/section_cli_neutron-quotas.xml:41(para) +msgid "OpenStack Networking also supports quotas for L3 resources: router and floating IP. Add these lines to the quotas section in the neutron.conf file." +msgstr "" + +#: ./doc/common/section_cli_neutron-quotas.xml:52(para) ./doc/common/section_cli_neutron-quotas.xml:67(para) +msgid "The option does not affect these quotas." +msgstr "" + +#: ./doc/common/section_cli_neutron-quotas.xml:55(para) +msgid "OpenStack Networking also supports quotas for security group resources: number of security groups and the number of rules for each security group. Add these lines to the quotas section in the neutron.conf file:" +msgstr "" + +#: ./doc/common/section_cli_neutron-quotas.xml:72(title) +msgid "Configure per-tenant quotas" +msgstr "" + +#: ./doc/common/section_cli_neutron-quotas.xml:73(para) +msgid "OpenStack Networking also supports per-tenant quota limit by quota extension API." +msgstr "" + +#: ./doc/common/section_cli_neutron-quotas.xml:77(para) +msgid ". Deletes defined quotas for a specified tenant." +msgstr "" + +#: ./doc/common/section_cli_neutron-quotas.xml:81(para) +msgid ". Lists defined quotas for all tenants." +msgstr "" + +#: ./doc/common/section_cli_neutron-quotas.xml:85(para) +msgid ". Shows quotas for a specified tenant." +msgstr "" + +#: ./doc/common/section_cli_neutron-quotas.xml:89(para) +msgid ". Updates quotas for a specified tenant." +msgstr "" + +#: ./doc/common/section_cli_neutron-quotas.xml:75(para) +msgid "Use these commands to manage per-tenant quotas:Only users with the admin role can change a quota value. By default, the default set of quotas are enforced for all tenants, so no command exists." +msgstr "" + +#: ./doc/common/section_cli_neutron-quotas.xml:98(title) +msgid "Configure Networking to show per-tenant quotas" +msgstr "" + +#: ./doc/common/section_cli_neutron-quotas.xml:99(para) +msgid "Set the quota_driver option in the neutron.conf file:" +msgstr "" + +#: ./doc/common/section_cli_neutron-quotas.xml:102(para) +msgid "When you set this option, the output for Networking commands shows quotas." +msgstr "" + +#: ./doc/common/section_cli_neutron-quotas.xml:106(title) +msgid "List Networking extensions" +msgstr "" + +#: ./doc/common/section_cli_neutron-quotas.xml:107(para) +msgid "To list the Networking extensions, run this command:" +msgstr "" + +#: ./doc/common/section_cli_neutron-quotas.xml:110(para) +msgid "The command shows the quotas extension, which provides per-tenant quota management support:" +msgstr "" + +#: ./doc/common/section_cli_neutron-quotas.xml:128(title) +msgid "Show information for the quotas extension" +msgstr "" + +#: ./doc/common/section_cli_neutron-quotas.xml:129(para) +msgid "To show information for the quotas extension, run this command:" +msgstr "" + +#: ./doc/common/section_cli_neutron-quotas.xml:143(para) +msgid "Only some plug-ins support per-tenant quotas. Specifically, Open vSwitch, Linux Bridge, and Nicira NVP support them, but new versions of other plug-ins might bring additional functionality. See the documentation for each plug-in." +msgstr "" + +#: ./doc/common/section_cli_neutron-quotas.xml:151(title) +msgid "List tenants who have per-tenant quota support" +msgstr "" + +#: ./doc/common/section_cli_neutron-quotas.xml:152(para) +msgid "The command lists tenants for which the per-tenant quota is enabled. The command does not list tenants with default quota support. You must be an administrative user to run this command:" +msgstr "" + +#: ./doc/common/section_cli_neutron-quotas.xml:165(title) +msgid "Show per-tenant quota values" +msgstr "" + +#: ./doc/common/section_cli_neutron-quotas.xml:166(para) +msgid "The reports the current set of quota limits for the specified tenant. Non-administrative users can run this command without the --tenant_id parameter. If per-tenant quota limits are not enabled for the tenant, the command shows the default set of quotas:" +msgstr "" + +#: ./doc/common/section_cli_neutron-quotas.xml:182(para) +msgid "The following command shows the command output for a non-administrative user:" +msgstr "" + +#: ./doc/common/section_cli_neutron-quotas.xml:196(title) +msgid "Update quota values for a specified tenant" +msgstr "" + +#: ./doc/common/section_cli_neutron-quotas.xml:197(para) +msgid "Use the command to update a quota for a specified tenant:" +msgstr "" + +#: ./doc/common/section_cli_neutron-quotas.xml:209(para) +msgid "You can update quotas for multiple resources through one command:" +msgstr "" + +#: ./doc/common/section_cli_neutron-quotas.xml:221(para) +msgid "To update the limits for an L3 resource such as, router or floating IP, you must define new values for the quotas after the -- directive." +msgstr "" + +#: ./doc/common/section_cli_neutron-quotas.xml:224(para) +msgid "This example updates the limit of the number of floating IPs for the specified tenant:" +msgstr "" + +#: ./doc/common/section_cli_neutron-quotas.xml:236(para) +msgid "You can update the limits of multiple resources by including L2 resources and L3 resource through one command." +msgstr "" + +#: ./doc/common/section_cli_neutron-quotas.xml:251(title) +msgid "Delete per-tenant quota values" +msgstr "" + +#: ./doc/common/section_cli_neutron-quotas.xml:252(para) +msgid "To clear per-tenant quota limits, use the command:" +msgstr "" + +#: ./doc/common/section_cli_neutron-quotas.xml:256(para) +msgid "After you run this command, you can see that quota values for the tenant are reset to the default values:" +msgstr "" + +#: ./doc/common/section_cli_nova_terminate.xml:8(title) +msgid "Delete an instance" +msgstr "" + +#: ./doc/common/section_cli_nova_terminate.xml:9(para) +msgid "When you no longer need an instance, you can delete it." +msgstr "" + +#: ./doc/common/section_cli_nova_terminate.xml:11(para) +msgid "List all instances:" +msgstr "" + +#: ./doc/common/section_cli_nova_terminate.xml:21(para) +msgid "Use the following command to delete the newServer instance, which is in ERROR state:" +msgstr "" + +#: ./doc/common/section_cli_nova_terminate.xml:25(para) +msgid "The command does not notify that your server was deleted." +msgstr "" + +#: ./doc/common/section_cli_nova_terminate.xml:26(para) +msgid "Instead, run the command:" +msgstr "" + +#: ./doc/common/section_cli_nova_terminate.xml:35(para) +msgid "The deleted instance does not appear in the list." +msgstr "" + +#: ./doc/common/section_cli_keystone_example_usage.xml:6(title) +msgid "keystone command-line client example usage" +msgstr "" + +#: ./doc/common/section_cli_keystone_example_usage.xml:7(para) +msgid "Before you can use keystone client commands, you must download and source an OpenStack RC file. For information, see the OpenStack Admin User Guide." +msgstr "" + +#: ./doc/common/section_cli_keystone_example_usage.xml:10(para) +msgid "The keystone command-line client uses the following syntax:" +msgstr "" + +#: ./doc/common/section_cli_keystone_example_usage.xml:12(replaceable) +msgid "PARAMETER" +msgstr "" + +#: ./doc/common/section_cli_keystone_example_usage.xml:12(replaceable) +msgid "ARGUMENT" +msgstr "" + +#: ./doc/common/section_cli_keystone_example_usage.xml:13(para) +msgid "For example, you can run the and commands, as follows:" +msgstr "" + +#: ./doc/common/section_cli_keystone_example_usage.xml:22(replaceable) ./doc/common/section_cli_keystone_example_usage.xml:23(replaceable) +msgid "token" +msgstr "" + +#: ./doc/common/section_cli_keystone_example_usage.xml:22(replaceable) ./doc/common/section_cli_keystone_example_usage.xml:23(replaceable) +msgid "endpoint" +msgstr "" + +#: ./doc/common/section_cli_keystone_example_usage.xml:31(replaceable) +msgid "id" +msgstr "" + +#: ./doc/common/section_cli_keystone_example_usage.xml:34(para) +msgid "For information about using the keystone client commands to create and manage users, roles, and projects, see the OpenStack Admin User Guide." +msgstr "" + +#: ./doc/common/section_cli_nova_volumes.xml:8(title) ./doc/common/section_dashboard_access.xml:108(guilabel) ./doc/common/section_dashboard_access.xml:274(guilabel) +msgid "Volumes" +msgstr "" + +#: ./doc/common/section_cli_nova_volumes.xml:9(para) +msgid "Depending on the setup of your cloud provider, they may give you an endpoint to use to manage volumes, or there may be an extension under the covers. In either case, you can use the nova CLI to manage volumes." +msgstr "" + +#: ./doc/common/section_getstart_object-storage.xml:5(title) +msgid "Object Storage service" +msgstr "" + +#: ./doc/common/section_getstart_object-storage.xml:6(para) +msgid "The Object Storage service is a highly scalable and durable multi-tenant object storage system for large amounts of unstructured data at low cost through a RESTful HTTP API." +msgstr "" + +#: ./doc/common/section_getstart_object-storage.xml:9(para) +msgid "It includes the following components:" +msgstr "" + +#: ./doc/common/section_getstart_object-storage.xml:12(para) +msgid "Proxy servers (swift-proxy-server). Accepts Object Storage API and raw HTTP requests to upload files, modify metadata, and create containers. It also serves file or container listings to web browsers. To improve performance, the proxy server can use an optional cache usually deployed with memcache." +msgstr "" + +#: ./doc/common/section_getstart_object-storage.xml:21(para) +msgid "Account servers (swift-account-server). Manage accounts defined with the Object Storage service." +msgstr "" + +#: ./doc/common/section_getstart_object-storage.xml:26(para) +msgid "Container servers (swift-container-server). Manage a mapping of containers, or folders, within the Object Storage service." +msgstr "" + +#: ./doc/common/section_getstart_object-storage.xml:32(para) +msgid "Object servers (swift-object-server). Manage actual objects, such as files, on the storage nodes." +msgstr "" + +#: ./doc/common/section_getstart_object-storage.xml:37(para) +msgid "A number of periodic processes. Performs housekeeping tasks on the large data store. The replication services ensure consistency and availability through the cluster. Other periodic processes include auditors, updaters, and reapers." +msgstr "" + +#: ./doc/common/section_getstart_object-storage.xml:44(para) +msgid "Configurable WSGI middleware that handles authentication. Usually the Identity Service." +msgstr "" + +#: ./doc/common/section_rpc-for-networking.xml:7(title) ./doc/common/section_rpc.xml:7(title) +msgid "Configure the Oslo RPC messaging system" +msgstr "" + +#: ./doc/common/section_rpc-for-networking.xml:9(para) +msgid "OpenStack projects use an open standard for messaging middleware known as AMQP. This messaging middleware enables the OpenStack services that run on multiple servers to talk to each other. OpenStack Oslo RPC supports three implementations of AMQP: RabbitMQ, Qpid, and ZeroMQ." +msgstr "" + +#: ./doc/common/section_rpc-for-networking.xml:18(title) ./doc/common/section_rpc.xml:15(title) +msgid "Configure RabbitMQ" +msgstr "" + +#: ./doc/common/section_rpc-for-networking.xml:20(para) +msgid "OpenStack Oslo RPC uses RabbitMQ by default. Use these options to configure the RabbitMQ message system. The option is optional as long as RabbitMQ is the default messaging system. However, if it is included the configuration, you must set it to neutron.openstack.common.rpc.impl_kombu." +msgstr "" + +#: ./doc/common/section_rpc-for-networking.xml:34(para) +msgid "Use these options to configure the RabbitMQ messaging system. You can configure messaging communication for different installation scenarios, tune retries for RabbitMQ, and define the size of the RPC thread pool. To monitor notifications through RabbitMQ, you must set the option to neutron.notifier.rabbit_notifier in the neutron.conf file:" +msgstr "" + +#: ./doc/common/section_rpc-for-networking.xml:46(title) ./doc/common/section_rpc.xml:39(title) +msgid "Configure Qpid" +msgstr "" + +#: ./doc/common/section_rpc-for-networking.xml:47(para) +msgid "Use these options to configure the Qpid messaging system for OpenStack Oslo RPC. Qpid is not the default messaging system, so you must enable it by setting the option in the neutron.conf file:" +msgstr "" + +#: ./doc/common/section_rpc-for-networking.xml:56(para) +msgid "This critical option points the compute nodes to the Qpid broker (server). Set the option to the host name where the broker runs in the neutron.conf file." +msgstr "" + +#: ./doc/common/section_rpc-for-networking.xml:62(para) ./doc/common/section_rpc.xml:52(para) +msgid "The option accepts a host name or IP address value." +msgstr "" + +#: ./doc/common/section_rpc-for-networking.xml:69(para) ./doc/common/section_rpc.xml:56(para) +msgid "If the Qpid broker listens on a port other than the AMQP default of 5672, you must set the option to that value:" +msgstr "" + +#: ./doc/common/section_rpc-for-networking.xml:78(para) ./doc/common/section_rpc.xml:61(para) +msgid "If you configure the Qpid broker to require authentication, you must add a user name and password to the configuration:" +msgstr "" + +#: ./doc/common/section_rpc-for-networking.xml:87(para) ./doc/common/section_rpc.xml:66(para) +msgid "By default, TCP is used as the transport. To enable SSL, set the option:" +msgstr "" + +#: ./doc/common/section_rpc-for-networking.xml:94(para) +msgid "Use these additional options to configure the Qpid messaging driver for OpenStack Oslo RPC. These options are used infrequently." +msgstr "" + +#: ./doc/common/section_rpc-for-networking.xml:102(title) ./doc/common/section_rpc.xml:75(title) +msgid "Configure ZeroMQ" +msgstr "" + +#: ./doc/common/section_rpc-for-networking.xml:103(para) +msgid "Use these options to configure the ZeroMQ messaging system for OpenStack Oslo RPC. ZeroMQ is not the default messaging system, so you must enable it by setting the option in the neutron.conf file:" +msgstr "" + +#: ./doc/common/section_rpc-for-networking.xml:112(title) ./doc/common/section_rpc.xml:85(title) +msgid "Configure messaging" +msgstr "" + +#: ./doc/common/section_rpc-for-networking.xml:114(para) +msgid "Use these common options to configure the RabbitMQ, Qpid, and ZeroMq messaging drivers:" +msgstr "" + +#: ./doc/common/section_fibrechannel.xml:5(title) +msgid "Fibre Channel support in Compute" +msgstr "" + +#: ./doc/common/section_fibrechannel.xml:6(para) +msgid "Fibre Channel support in OpenStack Compute is remote block storage attached to Compute nodes for VMs." +msgstr "" + +#: ./doc/common/section_fibrechannel.xml:8(para) +msgid "In the Grizzly release, Fibre Channel supported only the KVM hypervisor." +msgstr "" + +#: ./doc/common/section_fibrechannel.xml:10(para) +msgid "Compute and Block Storage for Fibre Channel do not support automatic zoning. Fibre Channel arrays must be pre-zoned or directly attached to the KVM hosts." +msgstr "" + +#: ./doc/common/section_fibrechannel.xml:14(title) +msgid "KVM host requirements" +msgstr "" + +#: ./doc/common/section_fibrechannel.xml:15(para) +msgid "You must install these packages on the KVM host:" +msgstr "" + +#: ./doc/common/section_fibrechannel.xml:18(para) +msgid "sysfstools - Nova uses the systool application in this package." +msgstr "" + +#: ./doc/common/section_fibrechannel.xml:24(para) +msgid "sg3-utils - Nova uses the sg_scan and sginfo applications." +msgstr "" + +#: ./doc/common/section_fibrechannel.xml:30(para) +msgid "Installing the multipath-tools package is optional." +msgstr "" + +#: ./doc/common/section_fibrechannel.xml:34(title) +msgid "Install required packages" +msgstr "" + +#: ./doc/common/section_fibrechannel.xml:35(para) +msgid "Use these commands to install the system packages:" +msgstr "" + +#: ./doc/common/section_fibrechannel.xml:39(para) +msgid "For systems running Ubuntu:" +msgstr "" + +#: ./doc/common/section_fibrechannel.xml:45(para) +msgid "For systems running Red Hat:" +msgstr "" + +#: ./doc/common/section_cli_help.xml:6(title) +msgid "Get help for client commands" +msgstr "" + +#: ./doc/common/section_cli_help.xml:7(para) +msgid "To get usage information, including a list of commands with descriptions, for a client, run the following command:" +msgstr "" + +#: ./doc/common/section_cli_help.xml:9(replaceable) ./doc/common/section_cli_help.xml:59(replaceable) +msgid "CLIENT_NAME" +msgstr "" + +#: ./doc/common/section_cli_help.xml:10(para) +msgid "For example, to get help information for the swift client, run the following command:" +msgstr "" + +#: ./doc/common/section_cli_help.xml:54(para) +msgid "Depending on your credentials, you might not have permission to use every command." +msgstr "" + +#: ./doc/common/section_cli_help.xml:57(para) +msgid "After the command, you can enter a command name to get help for that command, as follows:" +msgstr "" + +#: ./doc/common/section_cli_help.xml:59(replaceable) +msgid "COMMAND_NAME" +msgstr "" + +#: ./doc/common/section_cli_help.xml:60(para) +msgid "For example, to get help for the glance command, enter the following command:" +msgstr "" + +#: ./doc/common/section_cli_help.xml:64(para) +msgid "The command returns a description of the command and its positional and optional arguments:" +msgstr "" + +#: ./doc/common/ch_getstart.xml:6(title) +msgid "Get started with OpenStack" +msgstr "" + +#: ./doc/common/ch_getstart.xml:8(para) +msgid "The OpenStack project is an open source cloud computing platform for all types of clouds, which aims to be simple to implement, massively scalable, and feature rich. Developers and cloud computing technologists from around the world create the OpenStack project." +msgstr "" + +#: ./doc/common/ch_getstart.xml:13(para) +msgid "OpenStack provides an Infrastructure as a Service (IaaS) solution through a set of interrelated services. Each service offers an application programming interface (API) that facilitates this integration. Depending on your needs, you can install some or all services." +msgstr "" + +#: ./doc/common/ch_getstart.xml:18(para) +msgid "The following table describes the OpenStack services that make up the OpenStack architecture:" +msgstr "" + +#: ./doc/common/ch_getstart.xml:21(caption) ./doc/common/ch_getstart.xml:154(title) +msgid "OpenStack services" +msgstr "" + +#: ./doc/common/ch_getstart.xml:27(th) ./doc/common/section_keystone-concepts.xml:89(emphasis) +msgid "Service" +msgstr "" + +#: ./doc/common/ch_getstart.xml:28(th) +msgid "Project name" +msgstr "" + +#: ./doc/common/ch_getstart.xml:39(link) +msgid "Horizon" +msgstr "" + +#: ./doc/common/ch_getstart.xml:40(td) +msgid "Provides a web-based self-service portal to interact with underlying OpenStack services, such as launching an instance, assigning IP addresses and configuring access controls." +msgstr "" + +#: ./doc/common/ch_getstart.xml:48(link) +msgid "Compute" +msgstr "" + +#: ./doc/common/ch_getstart.xml:51(link) +msgid "Nova" +msgstr "" + +#: ./doc/common/ch_getstart.xml:52(td) +msgid "Manages the lifecycle of compute instances in an OpenStack environment. Responsibilities include spawning, scheduling and decomissioning of machines on demand." +msgstr "" + +#: ./doc/common/ch_getstart.xml:60(link) +msgid "Networking" +msgstr "" + +#: ./doc/common/ch_getstart.xml:63(link) +msgid "Neutron" +msgstr "" + +#: ./doc/common/ch_getstart.xml:64(td) +msgid "Enables network connectivity as a service for other OpenStack services, such as OpenStack Compute. Provides an API for users to define networks and the attachments into them. Has a pluggable architecture that supports many popular networking vendors and technologies." +msgstr "" + +#: ./doc/common/ch_getstart.xml:71(th) +msgid "Storage" +msgstr "" + +#: ./doc/common/ch_getstart.xml:75(link) +msgid "Object Storage" +msgstr "" + +#: ./doc/common/ch_getstart.xml:78(link) +msgid "Swift" +msgstr "" + +#: ./doc/common/ch_getstart.xml:80(glossterm) +msgid "RESTful" +msgstr "" + +#: ./doc/common/ch_getstart.xml:79(td) +msgid "Stores and retrieves arbitrary unstructured data objects via a , HTTP based API. It is highly fault tolerant with its data replication and scale out architecture. Its implementation is not like a file server with mountable directories." +msgstr "" + +#: ./doc/common/ch_getstart.xml:89(link) +msgid "Block Storage" +msgstr "" + +#: ./doc/common/ch_getstart.xml:92(link) +msgid "Cinder" +msgstr "" + +#: ./doc/common/ch_getstart.xml:93(td) +msgid "Provides persistent block storage to running instances. Its pluggable driver architecture facilitates the creation and management of block storage devices." +msgstr "" + +#: ./doc/common/ch_getstart.xml:98(th) +msgid "Shared services" +msgstr "" + +#: ./doc/common/ch_getstart.xml:102(link) +msgid "Identity Service" +msgstr "" + +#: ./doc/common/ch_getstart.xml:105(link) +msgid "Keystone" +msgstr "" + +#: ./doc/common/ch_getstart.xml:106(td) +msgid "Provides an authentication and authorization service for other OpenStack services. Provides a catalog of endpoints for all OpenStack services." +msgstr "" + +#: ./doc/common/ch_getstart.xml:113(link) +msgid "Image Service" +msgstr "" + +#: ./doc/common/ch_getstart.xml:116(link) +msgid "Glance" +msgstr "" + +#: ./doc/common/ch_getstart.xml:117(td) +msgid "Stores and retrieves virtual machine disk images. OpenStack Compute makes use of this during instance provisioning." +msgstr "" + +#: ./doc/common/ch_getstart.xml:126(link) +msgid "Telemetry Service" +msgstr "" + +#: ./doc/common/ch_getstart.xml:129(link) +msgid "Ceilometer" +msgstr "" + +#: ./doc/common/ch_getstart.xml:130(td) +msgid "Monitors and meters the OpenStack cloud for billing, benchmarking, scalability, and statistical purposes." +msgstr "" + +#: ./doc/common/ch_getstart.xml:134(th) +msgid "Higher-level services" +msgstr "" + +#: ./doc/common/ch_getstart.xml:138(link) +msgid "Orchestration Service" +msgstr "" + +#: ./doc/common/ch_getstart.xml:141(link) +msgid "Heat" +msgstr "" + +#: ./doc/common/ch_getstart.xml:142(td) +msgid "Orchestrates multiple composite cloud applications by using either the native HOT template format or the AWS CloudFormation template format, through both an OpenStack-native REST API and a CloudFormation-compatible Query API." +msgstr "" + +#: ./doc/common/ch_getstart.xml:155(para) +msgid "This section describes OpenStack services in detail." +msgstr "" + +#: ./doc/common/ch_getstart.xml:173(title) +msgid "Feedback" +msgstr "" + +#: ./doc/common/section_getstart_compute.xml:5(title) +msgid "Compute service" +msgstr "" + +#: ./doc/common/section_getstart_compute.xml:6(para) +msgid "The Compute service is a cloud computing fabric controller, which is the main part of an IaaS system. Use it to host and manage cloud computing systems. The main modules are implemented in Python." +msgstr "" + +#: ./doc/common/section_getstart_compute.xml:10(para) +msgid "Compute interacts with the Identity Service for authentication, Image Service for images, and the Dashboard for the user and administrative interface. Access to images is limited by project and by user; quotas are limited per project (for example, the number of instances). The Compute service scales horizontally on standard hardware, and downloads images to launch instances as required." +msgstr "" + +#: ./doc/common/section_getstart_compute.xml:17(para) +msgid "The Compute Service is made up of the following functional areas and their underlying components:" +msgstr "" + +#: ./doc/common/section_getstart_compute.xml:20(title) +msgid "API" +msgstr "" + +#: ./doc/common/section_getstart_compute.xml:22(para) +msgid "nova-api service. Accepts and responds to end user compute API calls. Supports the OpenStack Compute API, the Amazon EC2 API, and a special Admin API for privileged users to perform administrative actions. Also, initiates most orchestration activities, such as running an instance, and enforces some policies." +msgstr "" + +#: ./doc/common/section_getstart_compute.xml:30(para) +msgid "nova-api-metadata service. Accepts metadata requests from instances. The nova-api-metadata service is generally only used when you run in multi-host mode with nova-network installations. For details, see Metadata service in the Cloud Administrator Guide." +msgstr "" + +#: ./doc/common/section_getstart_compute.xml:39(para) +msgid "On Debian systems, it is included in the nova-api package, and can be selected through debconf." +msgstr "" + +#: ./doc/common/section_getstart_compute.xml:45(title) +msgid "Compute core" +msgstr "" + +#: ./doc/common/section_getstart_compute.xml:47(para) +msgid "nova-compute process. A worker daemon that creates and terminates virtual machine instances through hypervisor APIs. For example, XenAPI for XenServer/XCP, libvirt for KVM or QEMU, VMwareAPI for VMware, and so on. The process by which it does so is fairly complex but the basics are simple: Accept actions from the queue and perform a series of system commands, like launching a KVM instance, to carry them out while updating state in the database." +msgstr "" + +#: ./doc/common/section_getstart_compute.xml:58(para) +msgid "nova-scheduler process. Conceptually the simplest piece of code in Compute. Takes a virtual machine instance request from the queue and determines on which compute server host it should run." +msgstr "" + +#: ./doc/common/section_getstart_compute.xml:64(para) +msgid "nova-conductor module. Mediates interactions between nova-compute and the database. Aims to eliminate direct accesses to the cloud database made by nova-compute. The nova-conductor module scales horizontally. However, do not deploy it on any nodes where nova-compute runs. For more information, see A new Nova service: nova-conductor." +msgstr "" + +#: ./doc/common/section_getstart_compute.xml:79(title) +msgid "Networking for VMs" +msgstr "" + +#: ./doc/common/section_getstart_compute.xml:81(para) +msgid "nova-network worker daemon. Similar to nova-compute, it accepts networking tasks from the queue and performs tasks to manipulate the network, such as setting up bridging interfaces or changing iptables rules. This functionality is being migrated to OpenStack Networking, which is a separate OpenStack service." +msgstr "" + +#: ./doc/common/section_getstart_compute.xml:90(para) +msgid "nova-dhcpbridge script. Tracks IP address leases and records them in the database by using the dnsmasq dhcp-script facility. This functionality is being migrated to OpenStack Networking. OpenStack Networking provides a different script." +msgstr "" + +#: ./doc/common/section_getstart_compute.xml:100(title) +msgid "Console interface" +msgstr "" + +#: ./doc/common/section_getstart_compute.xml:102(para) +msgid "nova-consoleauth daemon. Authorizes tokens for users that console proxies provide. See nova-novncproxy and nova-xvpnvcproxy. This service must be running for console proxies to work. Many proxies of either type can be run against a single nova-consoleauth service in a cluster configuration. For information, see About nova-consoleauth." +msgstr "" + +#: ./doc/common/section_getstart_compute.xml:115(para) +msgid "nova-novncproxy daemon. Provides a proxy for accessing running instances through a VNC connection. Supports browser-based novnc clients." +msgstr "" + +#: ./doc/common/section_getstart_compute.xml:121(para) +msgid "nova-console daemon. Deprecated for use with Grizzly. Instead, the nova-xvpnvncproxy is used." +msgstr "" + +#: ./doc/common/section_getstart_compute.xml:127(para) +msgid "nova-xvpnvncproxy daemon. A proxy for accessing running instances through a VNC connection. Supports a Java client specifically designed for OpenStack." +msgstr "" + +#: ./doc/common/section_getstart_compute.xml:133(para) +msgid "nova-cert daemon. Manages x509 certificates." +msgstr "" + +#: ./doc/common/section_getstart_compute.xml:137(para) +msgid "In Debian, a unique nova-consoleproxy package provides the nova-novncproxy, nova-spicehtml5proxy, and nova-xvpvncproxy packages. To select packages, edit the /etc/default/nova-consoleproxy file or use the debconf interface. You can also manually edit the /etc/default/nova-consoleproxy file and stop and start the console daemons." +msgstr "" + +#: ./doc/common/section_getstart_compute.xml:148(title) +msgid "Image management (EC2 scenario)" +msgstr "" + +#: ./doc/common/section_getstart_compute.xml:150(para) +msgid "nova-objectstore daemon. Provides an S3 interface for registering images with the Image Service. Mainly used for installations that must support euca2ools. The euca2ools tools talk to nova-objectstore in S3 language, and nova-objectstore translates S3 requests into Image Service requests." +msgstr "" + +#: ./doc/common/section_getstart_compute.xml:160(para) +msgid "euca2ools client. A set of command-line interpreter commands for managing cloud resources. Though not an OpenStack module, you can configure nova-api to support this EC2 interface. For more information, see the Eucalyptus 2.0 Documentation." +msgstr "" + +#: ./doc/common/section_getstart_compute.xml:170(title) +msgid "Command-line clients and other interfaces" +msgstr "" + +#: ./doc/common/section_getstart_compute.xml:172(para) +msgid "nova client. Enables users to submit commands as a tenant administrator or end user." +msgstr "" + +#: ./doc/common/section_getstart_compute.xml:176(para) +msgid "nova-manage client. Enables cloud administrators to submit commands." +msgstr "" + +#: ./doc/common/section_getstart_compute.xml:181(title) +msgid "Other components" +msgstr "" + +#: ./doc/common/section_getstart_compute.xml:183(para) +msgid "The queue. A central hub for passing messages between daemons. Usually implemented with RabbitMQ, but could be any AMPQ message queue, such as Apache Qpid or Zero MQ." +msgstr "" + +#: ./doc/common/section_getstart_compute.xml:192(para) +msgid "SQL database. Stores most build-time and runtime states for a cloud infrastructure. Includes instance types that are available for use, instances in use, available networks, and projects. Theoretically, OpenStack Compute can support any database that SQL-Alchemy supports, but the only databases widely used are sqlite3 databases (only appropriate for test and development work), MySQL, and PostgreSQL." +msgstr "" + +#: ./doc/common/section_getstart_compute.xml:201(para) +msgid "The Compute Service interacts with other OpenStack services: Identity Service for authentication, Image Service for images, and the OpenStack dashboard for a web interface." +msgstr "" + +#: ./doc/common/section_compute-configure-console.xml:5(title) +msgid "Configure remote console access" +msgstr "" + +#. +#: ./doc/common/section_compute-configure-console.xml:7(para) +msgid "To provide a remote console or remote desktop access to guest virtual machines, use VNC or SPICE HTML5 through either the OpenStack dashboard or the command line. Best practice is to select one or the other to run." +msgstr "" + +#: ./doc/common/section_xapi-resize-setup.xml:7(title) +msgid "Modify Dom0 for resize/migration support" +msgstr "" + +#: ./doc/common/section_xapi-resize-setup.xml:8(para) +msgid "To resize servers with XenServer and XCP, you must:" +msgstr "" + +#: ./doc/common/section_xapi-resize-setup.xml:11(para) +msgid "Establish a root trust between all hypervisor nodes of your deployment:" +msgstr "" + +#: ./doc/common/section_xapi-resize-setup.xml:13(para) +msgid "To do so, generate an ssh key-pair with the command. Ensure that each of your dom0's authorized_keys file (located in /root/.ssh/authorized_keys) contains the public key fingerprint (located in /root/.ssh/id_rsa.pub)." +msgstr "" + +#: ./doc/common/section_xapi-resize-setup.xml:22(para) +msgid "Provide an /images mount point to the dom0 for your hypervisor:" +msgstr "" + +#: ./doc/common/section_xapi-resize-setup.xml:24(para) +msgid "Dom0 space is at a premium so creating a directory in dom0 is potentially dangerous and likely to fail especially when you resize large servers. The least you can do is to symlink /images to your local storage SR. The following instructions work for an English-based installation of XenServer (and XCP) and in the case of ext3-based SR (with which the resize functionality is known to work correctly)." +msgstr "" + +#: ./doc/common/section_cli_nova_sshkeys.xml:6(title) +msgid "Add keypair" +msgstr "" + +#: ./doc/common/section_cli_nova_sshkeys.xml:7(para) +msgid "Create at least one keypair for each project. If you have generated a keypair with an external tool, you can import it into OpenStack. The keypair can be used for multiple instances that belong to a project." +msgstr "" + +#: ./doc/common/section_cli_nova_sshkeys.xml:13(para) +msgid "Create a key." +msgstr "" + +#: ./doc/common/section_cli_nova_sshkeys.xml:14(para) +msgid "To create a mykey key that you can associate with instances, run the following command:" +msgstr "" + +#: ./doc/common/section_cli_nova_sshkeys.xml:17(para) +msgid "Save the mykey.pem file to a secure location. It enables root access to any instances with which the mykey key is associated." +msgstr "" + +#: ./doc/common/section_cli_nova_sshkeys.xml:22(para) +msgid "Alternatively, you can import a keypair." +msgstr "" + +#: ./doc/common/section_cli_nova_sshkeys.xml:23(para) +msgid "To import an existing public key, mykey.pub, and associate it with the mykey key, run the following command:" +msgstr "" + +#: ./doc/common/section_cli_nova_sshkeys.xml:28(para) +msgid "You must have the matching private key to access instances that are associated with this key." +msgstr "" + +#: ./doc/common/section_dashboard-configure-https.xml:4(title) +msgid "Configure the dashboard for HTTPS" +msgstr "" + +#: ./doc/common/section_dashboard-configure-https.xml:5(para) ./doc/common/section_dashboard-configure.xml:10(para) +msgid "You can configure the dashboard for a secured HTTPS deployment. While the standard installation uses a non-encrypted HTTP channel, you can enable SSL support for the dashboard." +msgstr "" + +#: ./doc/common/section_dashboard-configure-https.xml:9(para) +msgid "The following example uses the domain, \"http://openstack.example.com.\" Use a domain that fits your current setup." +msgstr "" + +#: ./doc/common/section_dashboard-configure-https.xml:13(para) +msgid "In/etc/openstack-dashboard/local_settings.py update the following directives:" +msgstr "" + +#: ./doc/common/section_dashboard-configure-https.xml:19(para) +msgid "The first option is required to enable HTTPS. The other recommended settings defend against cross-site scripting and require HTTPS." +msgstr "" + +#: ./doc/common/section_dashboard-configure-https.xml:24(para) +msgid "Edit /etc/apache2/ports.conf and add the following line:" +msgstr "" + +#: ./doc/common/section_dashboard-configure-https.xml:30(para) +msgid "Edit /etc/apache2/conf.d/openstack-dashboard.conf:" +msgstr "" + +#: ./doc/common/section_dashboard-configure-https.xml:33(para) +msgid "Before:" +msgstr "" + +#: ./doc/common/section_dashboard-configure-https.xml:46(para) +msgid "After:" +msgstr "" + +#: ./doc/common/section_dashboard-configure-https.xml:87(para) +msgid "In this configuration, Apache http server listens on the port 443 and redirects all the hits to the HTTPS protocol for all the non-secured requests. The secured section defines the private key, public key, and certificate to use." +msgstr "" + +#: ./doc/common/section_dashboard-configure-https.xml:94(para) +msgid "Restart Apache http server. For Debian/Ubuntu/SUSE:" +msgstr "" + +#: ./doc/common/section_dashboard-configure-https.xml:96(para) +msgid "Or for Fedora/RHEL/CentOS:" +msgstr "" + +#: ./doc/common/section_dashboard-configure-https.xml:98(para) ./doc/common/section_dashboard-configure-http.xml:32(para) +msgid "Next, restart memcached:" +msgstr "" + +#: ./doc/common/section_dashboard-configure-https.xml:100(para) +msgid "If you try to access the dashboard through HTTP, the browser redirects you to the HTTPS page." +msgstr "" + +#. When image changes, this message will be marked fuzzy or untranslated for you. +#. It doesn't matter what you translate it to: it's not used at all. +#: ./doc/common/section_getstart_logical_arch.xml:34(None) +msgid "@@image: 'figures/openstack-arch-havana-logical-v1.jpg'; md5=e7acaaee72722626b045eda3fae81841" +msgstr "" + +#: ./doc/common/section_getstart_logical_arch.xml:5(title) ./doc/common/section_getstart_logical_arch.xml:29(title) +msgid "Logical architecture" +msgstr "" + +#: ./doc/common/section_getstart_logical_arch.xml:6(para) +msgid "To design, install, and configure a cloud, cloud administrators must understand the logical architecture." +msgstr "" + +#: ./doc/common/section_getstart_logical_arch.xml:8(para) +msgid "OpenStack modules are one of the following types:" +msgstr "" + +#: ./doc/common/section_getstart_logical_arch.xml:11(para) +msgid "Daemon. Runs as a daemon. On Linux platforms, a daemon is usually installed as a service." +msgstr "" + +#: ./doc/common/section_getstart_logical_arch.xml:15(para) +msgid "Script. Installs and tests of a virtual environment. For example, the run_tests.sh script installs and optionally tests a virtual environment for a service." +msgstr "" + +#: ./doc/common/section_getstart_logical_arch.xml:20(para) +msgid "Command-line interface (CLI). Enables users to submit API calls to OpenStack services through easy-to-use commands." +msgstr "" + +#: ./doc/common/section_getstart_logical_arch.xml:25(para) +msgid "The following diagram shows the most common, but not the only, architecture for an OpenStack cloud:" +msgstr "" + +#: ./doc/common/section_getstart_logical_arch.xml:38(para) +msgid "As in , end users can interact through the dashboard, CLIs, and APIs. All services authenticate through a common Identity Service and individual services interact with each other through public APIs, except where privileged administrator commands are necessary." +msgstr "" + +#. When image changes, this message will be marked fuzzy or untranslated for you. +#. It doesn't matter what you translate it to: it's not used at all. +#: ./doc/common/section_keystone-concepts.xml:132(None) ./doc/common/section_keystone-concepts.xml:137(None) +msgid "@@image: 'figures/SCH_5002_V00_NUAC-Keystone.png'; md5=657851bcb185467ac322b4b4008fdf39" +msgstr "" + +#: ./doc/common/section_keystone-concepts.xml:7(title) +msgid "Identity Service concepts" +msgstr "" + +#: ./doc/common/section_keystone-concepts.xml:8(para) +msgid "The Identity Service performs the following functions:" +msgstr "" + +#: ./doc/common/section_keystone-concepts.xml:12(para) +msgid "User management. Tracks users and their permissions." +msgstr "" + +#: ./doc/common/section_keystone-concepts.xml:16(para) +msgid "Service catalog. Provides a catalog of available services with their API endpoints." +msgstr "" + +#: ./doc/common/section_keystone-concepts.xml:21(para) +msgid "To understand the Identity Service, you must understand the following concepts:" +msgstr "" + +#: ./doc/common/section_keystone-concepts.xml:25(emphasis) +msgid "User" +msgstr "" + +#: ./doc/common/section_keystone-concepts.xml:27(para) +msgid "Digital representation of a person, system, or service who uses OpenStack cloud services. The Identity Service validates that incoming requests are made by the user who claims to be making the call. Users have a login and may be assigned tokens to access resources. Users can be directly assigned to a particular tenant and behave as if they are contained in that tenant." +msgstr "" + +#: ./doc/common/section_keystone-concepts.xml:38(emphasis) +msgid "Credentials" +msgstr "" + +#: ./doc/common/section_keystone-concepts.xml:40(para) +msgid "Data that is known only by a user that proves who they are. In the Identity Service, examples are: User name and password, user name and API key, or an authentication token provided by the Identity Service." +msgstr "" + +#: ./doc/common/section_keystone-concepts.xml:49(emphasis) +msgid "Authentication" +msgstr "" + +#: ./doc/common/section_keystone-concepts.xml:51(para) +msgid "The act of confirming the identity of a user. The Identity Service confirms an incoming request by validating a set of credentials supplied by the user." +msgstr "" + +#: ./doc/common/section_keystone-concepts.xml:55(para) +msgid "These credentials are initially a user name and password or a user name and API key. In response to these credentials, the Identity Service issues an authentication token to the user, which the user provides in subsequent requests." +msgstr "" + +#: ./doc/common/section_keystone-concepts.xml:63(emphasis) +msgid "Token" +msgstr "" + +#: ./doc/common/section_keystone-concepts.xml:65(para) +msgid "An arbitrary bit of text that is used to access resources. Each token has a scope which describes which resources are accessible with it. A token may be revoked at any time and is valid for a finite duration." +msgstr "" + +#: ./doc/common/section_keystone-concepts.xml:70(para) +msgid "While the Identity Service supports token-based authentication in this release, the intention is for it to support additional protocols in the future. The intent is for it to be an integration service foremost, and not aspire to be a full-fledged identity store and management solution." +msgstr "" + +#: ./doc/common/section_keystone-concepts.xml:80(emphasis) +msgid "Tenant" +msgstr "" + +#: ./doc/common/section_keystone-concepts.xml:82(para) +msgid "A container used to group or isolate resources and/or identity objects. Depending on the service operator, a tenant may map to a customer, account, organization, or project." +msgstr "" + +#: ./doc/common/section_keystone-concepts.xml:91(para) +msgid "An OpenStack service, such as Compute (Nova), Object Storage (Swift), or Image Service (Glance). Provides one or more endpoints through which users can access resources and perform operations." +msgstr "" + +#: ./doc/common/section_keystone-concepts.xml:99(emphasis) +msgid "Endpoint" +msgstr "" + +#: ./doc/common/section_keystone-concepts.xml:101(para) +msgid "A network-accessible address, usually described by a URL, from where you access a service. If using an extension for templates, you can create an endpoint template, which represents the templates of all the consumable services that are available across the regions." +msgstr "" + +#: ./doc/common/section_keystone-concepts.xml:110(emphasis) +msgid "Role" +msgstr "" + +#: ./doc/common/section_keystone-concepts.xml:112(para) +msgid "A personality that a user assumes that enables them to perform a specific set of operations. A role includes a set of rights and privileges. A user assuming that role inherits those rights and privileges." +msgstr "" + +#: ./doc/common/section_keystone-concepts.xml:117(para) +msgid "In the Identity Service, a token that is issued to a user includes the list of roles that user has. Services that are being called by that user determine how they interpret the set of roles a user has and to which operations or resources each role grants access." +msgstr "" + +#: ./doc/common/section_keystone-concepts.xml:126(para) +msgid "The following diagram shows the Identity Service process flow:" +msgstr "" + +#: ./doc/common/section_kvm_enable.xml:6(title) +msgid "Enable KVM" +msgstr "" + +#: ./doc/common/section_kvm_enable.xml:7(para) +msgid "To perform these steps, you must be logged in as the root user." +msgstr "" + +#: ./doc/common/section_kvm_enable.xml:11(para) +msgid "To determine whether the svm or vmx CPU extensions are present, run this command:" +msgstr "" + +#: ./doc/common/section_kvm_enable.xml:15(para) +msgid "This command generates output if the CPU is hardware-virtualization capable. Even if output is shown, you might still need to enable virtualization in the system BIOS for full support." +msgstr "" + +#: ./doc/common/section_kvm_enable.xml:19(para) +msgid "If no output appears, consult your system documentation to ensure that your CPU and motherboard support hardware virtualization. Verify that any relevant hardware virtualization options are enabled in the system BIOS." +msgstr "" + +#: ./doc/common/section_kvm_enable.xml:24(para) +msgid "The BIOS for each manufacturer is different. If you must enable virtualization in the BIOS, look for an option containing the words virtualization, VT, VMX, or SVM." +msgstr "" + +#: ./doc/common/section_kvm_enable.xml:32(para) +msgid "To list the loaded kernel modules and verify that the kvm modules are loaded, run this command:" +msgstr "" + +#: ./doc/common/section_kvm_enable.xml:36(para) +msgid "If the output includes kvm_intel or kvm_amd, the kvm hardware virtualization modules are loaded and your kernel meets the module requirements for OpenStack Compute." +msgstr "" + +#: ./doc/common/section_kvm_enable.xml:43(para) +msgid "If the output does not show that the kvm module is loaded, run this command to load it:" +msgstr "" + +#: ./doc/common/section_kvm_enable.xml:47(para) +msgid "Run the command for your CPU. For Intel, run this command:" +msgstr "" + +#: ./doc/common/section_kvm_enable.xml:50(para) +msgid "For AMD, run this command:" +msgstr "" + +#: ./doc/common/section_kvm_enable.xml:52(para) +msgid "Because a KVM installation can change user group membership, you might need to log in again for changes to take effect." +msgstr "" + +#: ./doc/common/section_kvm_enable.xml:55(para) +msgid "If the kernel modules do not load automatically, use the procedures listed in these subsections." +msgstr "" + +#: ./doc/common/section_kvm_enable.xml:59(para) +msgid "If the checks indicate that required hardware virtualization support or kernel modules are disabled or unavailable, you must either enable this support on the system or find a system with this support." +msgstr "" + +#: ./doc/common/section_kvm_enable.xml:64(para) +msgid "Some systems require that you enable VT support in the system BIOS. If you believe your processor supports hardware acceleration but the previous command did not produce output, reboot your machine, enter the system BIOS, and enable the VT option." +msgstr "" + +#: ./doc/common/section_kvm_enable.xml:70(para) +msgid "If KVM acceleration is not supported, configure Compute to use a different hypervisor, such as QEMU or Xen." +msgstr "" + +#: ./doc/common/section_kvm_enable.xml:76(para) +msgid "These procedures help you load the kernel modules for Intel-based and AMD-based processors if they do not load automatically during KVM installation." +msgstr "" + +#: ./doc/common/section_kvm_enable.xml:80(title) +msgid "Intel-based processors" +msgstr "" + +#: ./doc/common/section_kvm_enable.xml:81(para) +msgid "If your compute host is Intel-based, run these commands as root to load the kernel modules:" +msgstr "" + +#: ./doc/common/section_kvm_enable.xml:85(para) +msgid "Add these lines to the /etc/modules file so that these modules load on reboot:" +msgstr "" + +#: ./doc/common/section_kvm_enable.xml:91(title) +msgid "AMD-based processors" +msgstr "" + +#: ./doc/common/section_kvm_enable.xml:92(para) +msgid "If your compute host is AMD-based, run these commands as root to load the kernel modules:" +msgstr "" + +#: ./doc/common/section_kvm_enable.xml:96(para) +msgid "Add these lines to /etc/modules file so that these modules load on reboot:" +msgstr "" + +#: ./doc/common/section_xapi-install-plugins.xml:7(title) +msgid "Install the XenAPI plug-ins" +msgstr "" + +#: ./doc/common/section_xapi-install-plugins.xml:8(para) +msgid "When you use Xen as the hypervisor for OpenStack Compute, you can install a Python script (or any executable) on the host side, and call that through the XenAPI. These scripts are called plug-ins. The XenAPI plug-ins live in the nova code repository. These plug-ins have to be copied to the Dom0 for the hypervisor, to the appropriate directory, where xapi can find them. There are several options for the installation. The important thing is to ensure that the version of the plug-ins are in line with the nova installation by only installing plug-ins from a matching nova repository." +msgstr "" + +#: ./doc/common/section_xapi-install-plugins.xml:19(title) +msgid "Manually install the plug-in" +msgstr "" + +#: ./doc/common/section_xapi-install-plugins.xml:22(para) +msgid "Create temporary files/directories:" +msgstr "" + +#: ./doc/common/section_xapi-install-plugins.xml:27(para) +msgid "Get the source from github. The example assumes the master branch is used. Amend the URL to match the version being used:" +msgstr "" + +#: ./doc/common/section_xapi-install-plugins.xml:32(para) +msgid "(Alternatively) To use the official Ubuntu packages, use the following commands to get the nova code base:" +msgstr "" + +#: ./doc/common/section_xapi-install-plugins.xml:39(para) +msgid "Copy the plug-ins to the hypervisor:" +msgstr "" + +#: ./doc/common/section_xapi-install-plugins.xml:44(para) +msgid "Remove the temporary files/directories:" +msgstr "" + +#: ./doc/common/section_xapi-install-plugins.xml:51(title) +msgid "Package a XenServer supplemental pack" +msgstr "" + +#: ./doc/common/section_xapi-install-plugins.xml:52(para) +msgid "Follow these steps to produce a supplemental pack from the nova sources, and package it as a XenServer supplemental pack." +msgstr "" + +#: ./doc/common/section_xapi-install-plugins.xml:57(para) +msgid "Create RPM packages. Given you have the nova sources. Use one of the methods in :" +msgstr "" + +#: ./doc/common/section_xapi-install-plugins.xml:62(para) +msgid "These commands leave an .rpm file in the rpmbuild/RPMS/noarch/ directory." +msgstr "" + +#: ./doc/common/section_xapi-install-plugins.xml:68(para) +msgid "Pack the RPM packages to a Supplemental Pack, using the XenServer DDK (the following command should be issued on the XenServer DDK virtual appliance, after the produced rpm file has been copied over):" +msgstr "" + +#: ./doc/common/section_xapi-install-plugins.xml:81(para) +msgid "This command produces an .iso file in the output directory specified. Copy that file to the hypervisor." +msgstr "" + +#: ./doc/common/section_xapi-install-plugins.xml:87(para) +msgid "Install the Supplemental Pack. Log in to the hypervisor, and issue:" +msgstr "" + +#: ./doc/common/section_dashboard-configure-vnc-window.xml:6(title) +msgid "Change the size of the dashboard VNC window" +msgstr "" + +#: ./doc/common/section_dashboard-configure-vnc-window.xml:7(para) +msgid "The _detail_vnc.html file defines the size of the VNC window. To change the window size, edit this file." +msgstr "" + +#: ./doc/common/section_dashboard-configure-vnc-window.xml:12(para) +msgid "Edit /usr/share/pyshared/horizon/dashboards/nova/instances/templates/instances/_detail_vnc.html." +msgstr "" + +#: ./doc/common/section_dashboard-configure-vnc-window.xml:16(para) +msgid "Modify the width and height parameters, as follows:" +msgstr "" + +#: ./doc/common/section_cli_nova_fileinjection.xml:10(title) +msgid "Inject files into instances" +msgstr "" + +#: ./doc/common/section_cli_nova_fileinjection.xml:11(para) +msgid "You can inject local files into the instance file system when you launch an instance." +msgstr "" + +#: ./doc/common/section_cli_nova_fileinjection.xml:13(para) +msgid "Use the --file dst-path=src-path parameter on the nova command." +msgstr "" + +#: ./doc/common/section_cli_nova_fileinjection.xml:15(para) +msgid "You can inject up to five files." +msgstr "" + +#: ./doc/common/section_cli_nova_fileinjection.xml:16(para) +msgid "For example, you might inject the special_authorized_keysfile file into the instance rather than using the regular ssh key injection." +msgstr "" + +#: ./doc/common/section_cli_nova_fileinjection.xml:19(para) +msgid "Run the following command:" +msgstr "" + +#: ./doc/common/section_keystone_certificates-for-pki.xml:7(title) +msgid "Certificates for PKI" +msgstr "" + +#: ./doc/common/section_keystone_certificates-for-pki.xml:8(para) +msgid "PKI stands for Public Key Infrastructure. Tokens are documents, cryptographically signed using the X509 standard. In order to work correctly token generation requires a public/private key pair. The public key must be signed in an X509 certificate, and the certificate used to sign it must be available as Certificate Authority (CA) certificate. These files can be generated either using the utility, or externally generated. The files need to be in the locations specified by the top level Identity Service configuration file keystone.conf as specified in the above section. Additionally, the private key should only be readable by the system user that will run the Identity Service." +msgstr "" + +#: ./doc/common/section_keystone_certificates-for-pki.xml:23(para) +msgid "The certificates can be world readable, but the private key cannot be. The private key should only be readable by the account that is going to sign tokens. When generating files with the command, your best option is to run as the pki user. If you run nova-manage as root, you can append --keystone-user and --keystone-group parameters to set the username and group keystone is going to run under." +msgstr "" + +#: ./doc/common/section_keystone_certificates-for-pki.xml:33(para) +msgid "The values that specify where to read the certificates are under the [signing] section of the configuration file. The configuration values are:" +msgstr "" + +#: ./doc/common/section_keystone_certificates-for-pki.xml:38(para) +msgid "token_format - Determines the algorithm used to generate tokens. Can be either UUID or PKI. Defaults to PKI." +msgstr "" + +#: ./doc/common/section_keystone_certificates-for-pki.xml:45(para) +msgid "certfile - Location of certificate used to verify tokens. Default is /etc/keystone/ssl/certs/signing_cert.pem." +msgstr "" + +#: ./doc/common/section_keystone_certificates-for-pki.xml:51(para) +msgid "keyfile - Location of private key used to sign tokens. Default is /etc/keystone/ssl/private/signing_key.pem." +msgstr "" + +#: ./doc/common/section_keystone_certificates-for-pki.xml:57(para) +msgid "ca_certs - Location of certificate for the authority that issued the above certificate. Default is /etc/keystone/ssl/certs/ca.pem." +msgstr "" + +#: ./doc/common/section_keystone_certificates-for-pki.xml:64(para) +msgid "key_size - Default is 1024." +msgstr "" + +#: ./doc/common/section_keystone_certificates-for-pki.xml:69(para) +msgid "valid_days - Default is 3650." +msgstr "" + +#: ./doc/common/section_keystone_certificates-for-pki.xml:74(para) +msgid "ca_password - Password required to read the ca_file. Default is None." +msgstr "" + +#: ./doc/common/section_keystone_certificates-for-pki.xml:80(para) +msgid "If token_format=UUID, a typical token looks like 53f7f6ef0cc344b5be706bcc8b1479e1. If token_format=PKI, a typical token is a much longer string, such as:" +msgstr "" + +#: ./doc/common/section_keystone_certificates-for-pki.xml:113(title) +msgid "Sign certificate issued by external CA" +msgstr "" + +#: ./doc/common/section_keystone_certificates-for-pki.xml:114(para) +msgid "You can use a signing certificate issued by an external CA instead of generated by . However, certificate issued by external CA must satisfy the following conditions:" +msgstr "" + +#: ./doc/common/section_keystone_certificates-for-pki.xml:121(para) +msgid "all certificate and key files must be in Privacy Enhanced Mail (PEM) format" +msgstr "" + +#: ./doc/common/section_keystone_certificates-for-pki.xml:125(para) +msgid "private key files must not be protected by a password" +msgstr "" + +#: ./doc/common/section_keystone_certificates-for-pki.xml:129(para) +msgid "When using signing certificate issued by an external CA, you do not need to specify key_size, valid_days, and ca_password as they will be ignored." +msgstr "" + +#: ./doc/common/section_keystone_certificates-for-pki.xml:134(para) +msgid "The basic workflow for using a signing certificate issued by an external CA involves:" +msgstr "" + +#: ./doc/common/section_keystone_certificates-for-pki.xml:138(para) +msgid "Request Signing Certificate from External CA" +msgstr "" + +#: ./doc/common/section_keystone_certificates-for-pki.xml:142(para) +msgid "Convert certificate and private key to PEM if needed" +msgstr "" + +#: ./doc/common/section_keystone_certificates-for-pki.xml:146(para) +msgid "Install External Signing Certificate" +msgstr "" + +#: ./doc/common/section_keystone_certificates-for-pki.xml:151(title) +msgid "Request a signing certificate from an external CA" +msgstr "" + +#: ./doc/common/section_keystone_certificates-for-pki.xml:153(para) +msgid "One way to request a signing certificate from an external CA is to first generate a PKCS #10 Certificate Request Syntax (CRS) using OpenSSL CLI." +msgstr "" + +#: ./doc/common/section_keystone_certificates-for-pki.xml:156(para) +msgid "Create a certificate request configuration file. For example, create the cert_req.conf file, as follows:" +msgstr "" + +#: ./doc/common/section_keystone_certificates-for-pki.xml:176(para) +msgid "Then generate a CRS with OpenSSL CLI. Do not encrypt the generated private key. Must use the -nodes option." +msgstr "" + +#: ./doc/common/section_keystone_certificates-for-pki.xml:183(para) +msgid "If everything is successfully, you should end up with signing_cert_req.pem and signing_key.pem. Send signing_cert_req.pem to your CA to request a token signing certificate and make sure to ask the certificate to be in PEM format. Also, make sure your trusted CA certificate chain is also in PEM format." +msgstr "" + +#: ./doc/common/section_keystone_certificates-for-pki.xml:193(title) +msgid "Install an external signing certificate" +msgstr "" + +#: ./doc/common/section_keystone_certificates-for-pki.xml:194(para) +msgid "Assuming you have the following already:" +msgstr "" + +#: ./doc/common/section_keystone_certificates-for-pki.xml:197(para) +msgid "signing_cert.pem - (Keystone token) signing certificate in PEM format" +msgstr "" + +#: ./doc/common/section_keystone_certificates-for-pki.xml:202(para) +msgid "signing_key.pem - corresponding (non-encrypted) private key in PEM format" +msgstr "" + +#: ./doc/common/section_keystone_certificates-for-pki.xml:208(para) +msgid "cacert.pem - trust CA certificate chain in PEM format" +msgstr "" + +#: ./doc/common/section_keystone_certificates-for-pki.xml:213(para) +msgid "Copy the above to your certificate directory. For example:" +msgstr "" + +#: ./doc/common/section_keystone_certificates-for-pki.xml:222(para) +msgid "Make sure the certificate directory is only accessible by root." +msgstr "" + +#: ./doc/common/section_keystone_certificates-for-pki.xml:225(para) +msgid "If your certificate directory path is different from the default /etc/keystone/ssl/certs, make sure it is reflected in the [signing] section of the configuration file." +msgstr "" + +#: ./doc/common/section_cli_nova_customize_flavors.xml:6(title) ./doc/common/section_dashboard_access.xml:281(guilabel) +msgid "Flavors" +msgstr "" + +#: ./doc/common/section_cli_nova_customize_flavors.xml:7(para) +msgid "Authorized users can use the command to create flavors. To see the available flavor-related commands, run:" +msgstr "" + +#: ./doc/common/section_cli_nova_customize_flavors.xml:22(para) +msgid "To modify an existing flavor in the dashboard, you must delete the flavor and create a modified one with the same name." +msgstr "" + +#: ./doc/common/section_cli_nova_customize_flavors.xml:26(para) +msgid "Flavors define these elements:" +msgstr "" + +#: ./doc/common/section_cli_nova_customize_flavors.xml:28(caption) +msgid "Identity Service configuration file sections" +msgstr "" + +#: ./doc/common/section_cli_nova_customize_flavors.xml:34(td) +msgid "Element" +msgstr "" + +#: ./doc/common/section_cli_nova_customize_flavors.xml:40(literal) +msgid "Name" +msgstr "" + +#: ./doc/common/section_cli_nova_customize_flavors.xml:42(replaceable) +msgid "xx" +msgstr "" + +#: ./doc/common/section_cli_nova_customize_flavors.xml:42(replaceable) +msgid "size_name" +msgstr "" + +#: ./doc/common/section_cli_nova_customize_flavors.xml:41(td) +msgid "A descriptive name. . is typically not required, though some third party tools may rely on it." +msgstr "" + +#: ./doc/common/section_cli_nova_customize_flavors.xml:47(literal) +msgid "Memory_MB" +msgstr "" + +#: ./doc/common/section_cli_nova_customize_flavors.xml:48(td) +msgid "Virtual machine memory in megabytes." +msgstr "" + +#: ./doc/common/section_cli_nova_customize_flavors.xml:51(literal) +msgid "Disk" +msgstr "" + +#: ./doc/common/section_cli_nova_customize_flavors.xml:52(td) +msgid "Virtual root disk size in gigabytes. This is an ephemeral disk that the base image is copied into. When booting from a persistent volume it is not used. The \"0\" size is a special case which uses the native base image size as the size of the ephemeral root volume." +msgstr "" + +#: ./doc/common/section_cli_nova_customize_flavors.xml:60(literal) +msgid "Ephemeral" +msgstr "" + +#: ./doc/common/section_cli_nova_customize_flavors.xml:61(td) +msgid "Specifies the size of a secondary ephemeral data disk. This is an empty, unformatted disk and exists only for the life of the instance." +msgstr "" + +#: ./doc/common/section_cli_nova_customize_flavors.xml:66(literal) +msgid "Swap" +msgstr "" + +#: ./doc/common/section_cli_nova_customize_flavors.xml:67(td) +msgid "Optional swap space allocation for the instance." +msgstr "" + +#: ./doc/common/section_cli_nova_customize_flavors.xml:71(literal) +msgid "VCPUs" +msgstr "" + +#: ./doc/common/section_cli_nova_customize_flavors.xml:72(td) +msgid "Number of virtual CPUs presented to the instance." +msgstr "" + +#: ./doc/common/section_cli_nova_customize_flavors.xml:76(literal) +msgid "RXTX_Factor" +msgstr "" + +#: ./doc/common/section_cli_nova_customize_flavors.xml:77(td) +msgid "Optional property allows created servers to have a different bandwidth cap than that defined in the network they are attached to. This factor is multiplied by the rxtx_base property of the network. Default value is 1.0. That is, the same as attached network." +msgstr "" + +#: ./doc/common/section_cli_nova_customize_flavors.xml:85(literal) +msgid "Is_Public" +msgstr "" + +#: ./doc/common/section_cli_nova_customize_flavors.xml:86(td) +msgid "Boolean value, whether flavor is available to all users or private to the tenant it was created in. Defaults to True." +msgstr "" + +#: ./doc/common/section_cli_nova_customize_flavors.xml:91(literal) +msgid "extra_specs" +msgstr "" + +#: ./doc/common/section_cli_nova_customize_flavors.xml:92(td) +msgid "Key and value pairs that define on which compute nodes a flavor can run. These pairs must match corresponding pairs on the compute nodes. Use to implement special resources, such as flavors that run on only compute nodes with GPU hardware." +msgstr "" + +#: ./doc/common/section_cli_nova_customize_flavors.xml:100(para) +msgid "Flavor customization can be limited by the hypervisor in use, for example the libvirt driver enables quotas on CPUs available to a VM, disk tuning, bandwidth I/O, and instance VIF traffic control." +msgstr "" + +#: ./doc/common/section_cli_nova_customize_flavors.xml:104(para) +msgid "You can configure the CPU limits with control parameters with the nova tool. For example, to configure the I/O limit:" +msgstr "" + +#: ./doc/common/section_cli_nova_customize_flavors.xml:109(para) +msgid "There are CPU control parameters for weight shares, enforcement intervals for runtime quotas, and a quota for maximum allowed bandwidth." +msgstr "" + +#: ./doc/common/section_cli_nova_customize_flavors.xml:112(para) +msgid "The optional cpu_shares element specifies the proportional weighted share for the domain. If this element is omitted, the service defaults to the OS provided defaults. There is no unit for the value. It is a relative measure based on the setting of other VMs. For example, a VM configured with value 2048 gets twice as much CPU time as a VM configured with value 1024." +msgstr "" + +#: ./doc/common/section_cli_nova_customize_flavors.xml:119(para) +msgid "The optional cpu_period element specifies the enforcement interval (unit: microseconds) for QEMU and LXC hypervisors. Within a period, each VCPU of the domain is not allowed to consume more than the quota worth of runtime. The value should be in range [1000, 1000000]. A period with value 0 means no value." +msgstr "" + +#: ./doc/common/section_cli_nova_customize_flavors.xml:125(para) +msgid "The optional cpu_quota element specifies the maximum allowed bandwidth (unit: microseconds). A domain with a quota with a negative value indicates that the domain has infinite bandwidth, which means that it is not bandwidth controlled. The value should be in range [1000, 18446744073709551] or less than 0. A quota with value 0 means no value. You can use this feature to ensure that all vcpus run at the same speed. For example:" +msgstr "" + +#: ./doc/common/section_cli_nova_customize_flavors.xml:135(para) +msgid "In this example, the instance of m1.low_cpu can only consume a maximum of 50% CPU of a physical CPU computing capability." +msgstr "" + +#: ./doc/common/section_cli_nova_customize_flavors.xml:138(para) +msgid "Through disk I/O quotas, you can set maximum disk write to 10 MB per second for a VM user. For example:" +msgstr "" + +#: ./doc/common/section_cli_nova_customize_flavors.xml:141(para) +msgid "The disk I/O options are:" +msgstr "" + +#: ./doc/common/section_cli_nova_customize_flavors.xml:144(para) +msgid "disk_read_bytes_sec" +msgstr "" + +#: ./doc/common/section_cli_nova_customize_flavors.xml:147(para) +msgid "disk_read_iops_sec" +msgstr "" + +#: ./doc/common/section_cli_nova_customize_flavors.xml:150(para) +msgid "disk_write_bytes_sec" +msgstr "" + +#: ./doc/common/section_cli_nova_customize_flavors.xml:153(para) +msgid "disk_write_iops_sec" +msgstr "" + +#: ./doc/common/section_cli_nova_customize_flavors.xml:156(para) +msgid "disk_total_bytes_sec" +msgstr "" + +#: ./doc/common/section_cli_nova_customize_flavors.xml:159(para) +msgid "disk_total_iops_sec" +msgstr "" + +#: ./doc/common/section_cli_nova_customize_flavors.xml:162(para) +msgid "The vif I/O options are:" +msgstr "" + +#: ./doc/common/section_cli_nova_customize_flavors.xml:165(para) +msgid "vif_inbound_ average" +msgstr "" + +#: ./doc/common/section_cli_nova_customize_flavors.xml:168(para) +msgid "vif_inbound_burst" +msgstr "" + +#: ./doc/common/section_cli_nova_customize_flavors.xml:171(para) +msgid "vif_inbound_peak" +msgstr "" + +#: ./doc/common/section_cli_nova_customize_flavors.xml:174(para) +msgid "vif_outbound_ average" +msgstr "" + +#: ./doc/common/section_cli_nova_customize_flavors.xml:177(para) +msgid "vif_outbound_burst" +msgstr "" + +#: ./doc/common/section_cli_nova_customize_flavors.xml:180(para) +msgid "vif_outbound_peak" +msgstr "" + +#: ./doc/common/section_cli_nova_customize_flavors.xml:183(para) +msgid "Incoming and outgoing traffic can be shaped independently. The bandwidth element can have at most one inbound and at most one outbound child element. Leaving any of these children element out result in no quality of service (QoS) applied on that traffic direction. So, when you want to shape only the network's incoming traffic, use inbound only, and vice versa. Each of these elements have one mandatory attribute average." +msgstr "" + +#: ./doc/common/section_cli_nova_customize_flavors.xml:191(para) +msgid "It specifies average bit rate on the interface being shaped. Then there are two optional attributes: peak, which specifies maximum rate at which bridge can send data, and burst, amount of bytes that can be burst at peak speed. Accepted values for attributes are integer numbers, The units for average and peak attributes are kilobytes per second, and for the burst just kilobytes. The rate is shared equally within domains connected to the network." +msgstr "" + +#: ./doc/common/section_cli_nova_customize_flavors.xml:199(para) +msgid "This example configures a bandwidth limit for instance network traffic:" +msgstr "" + +#: ./doc/common/section_cli_nova_customize_flavors.xml:203(para) +msgid "Flavors can also be assigned to particular projects. By default, a flavor is public and available to all projects. Private flavors are only accessible to those on the access list and are invisible to other projects. To create and assign a private flavor to a project, run these commands:" +msgstr "" + +#: ./doc/common/section_cli_nova_evacuate.xml:6(title) +msgid "Evacuate instances" +msgstr "" + +#: ./doc/common/section_cli_nova_evacuate.xml:7(para) +msgid "If a cloud compute node fails due to a hardware malfunction or another reason, you can evacuate instances to make them available again." +msgstr "" + +#: ./doc/common/section_cli_nova_evacuate.xml:10(para) +msgid "You can choose evacuation parameters for your use case." +msgstr "" + +#: ./doc/common/section_cli_nova_evacuate.xml:12(para) +msgid "To preserve user data on server disk, you must configure shared storage on the target host. Also, you must validate that the current VM host is down. Otherwise the evacuation fails with an error." +msgstr "" + +#: ./doc/common/section_cli_nova_evacuate.xml:18(para) +msgid "To find a different host for the evacuated instance, run this command to list hosts:" +msgstr "" + +#: ./doc/common/section_cli_nova_evacuate.xml:23(para) +msgid "You can pass the instance password to the command by using the --password <pwd> option. If you do not specify a password, one is generated and printed after the command finishes successfully. The following command evacuates a server without shared storage:" +msgstr "" + +#: ./doc/common/section_cli_nova_evacuate.xml:29(replaceable) ./doc/common/section_cli_nova_evacuate.xml:50(replaceable) +msgid "evacuated_server_name" +msgstr "" + +#: ./doc/common/section_cli_nova_evacuate.xml:29(replaceable) ./doc/common/section_cli_nova_evacuate.xml:50(replaceable) +msgid "host_b" +msgstr "" + +#: ./doc/common/section_cli_nova_evacuate.xml:30(para) +msgid "The command evacuates an instance from a down host to a specified host. The instance is booted from a new disk, but preserves its configuration including its ID, name, uid, IP address, and so on. The command returns a password:" +msgstr "" + +#: ./doc/common/section_cli_nova_evacuate.xml:42(para) +msgid "To preserve the user disk data on the evacuated server, deploy OpenStack Compute with shared file system. To configure your system, see Configure migrations in OpenStack Configuration Reference. In this example, the password remains unchanged." +msgstr "" + +#: ./doc/common/section_cli_neutron_manage_networks.xml:8(title) +msgid "Create and manage networks" +msgstr "" + +#: ./doc/common/section_cli_neutron_manage_networks.xml:9(para) +msgid "Before you run commands, set the following environment variables:" +msgstr "" + +#: ./doc/common/section_cli_neutron_manage_networks.xml:16(title) +msgid "Create networks" +msgstr "" + +#: ./doc/common/section_cli_neutron_manage_networks.xml:19(para) +msgid "List the extensions of the system:" +msgstr "" + +#: ./doc/common/section_cli_neutron_manage_networks.xml:35(para) +msgid "Create a network:" +msgstr "" + +#: ./doc/common/section_cli_neutron_manage_networks.xml:54(para) +msgid "Some fields of the created network are invisible to non-admin users." +msgstr "" + +#: ./doc/common/section_cli_neutron_manage_networks.xml:59(para) +msgid "Create a network with specified provider network type:" +msgstr "" + +#: ./doc/common/section_cli_neutron_manage_networks.xml:78(para) +msgid "Just as shown previous, the unknown option --provider:network-type is used to create a local provider network." +msgstr "" + +#: ./doc/common/section_cli_neutron_manage_networks.xml:86(title) +msgid "Create subnets" +msgstr "" + +#: ./doc/common/section_cli_neutron_manage_networks.xml:89(para) +msgid "Create a subnet:" +msgstr "" + +#: ./doc/common/section_cli_neutron_manage_networks.xml:107(para) +msgid "In the previous command, net1 is the network name, 192.168.2.0/24 is the subnet's CIDR. They are positional arguments. --name subnet1 is an unknown option, which specifies the subnet's name." +msgstr "" + +#: ./doc/common/section_cli_neutron_manage_networks.xml:118(title) +msgid "Create ports" +msgstr "" + +#: ./doc/common/section_cli_neutron_manage_networks.xml:121(para) +msgid "Create a port with specified IP address:" +msgstr "" + +#: ./doc/common/section_cli_neutron_manage_networks.xml:140(para) +msgid "In the previous command, net1 is the network name, which is a positional argument. --fixed-ip ip_address=192.168.2.40 is an option, which specifies the port's fixed IP address we wanted." +msgstr "" + +#: ./doc/common/section_cli_neutron_manage_networks.xml:148(para) +msgid "Create a port without specified IP address:" +msgstr "" + +#: ./doc/common/section_cli_neutron_manage_networks.xml:168(para) +msgid "We can see that the system will allocate one IP address if we don't specify the IP address in command line." +msgstr "" + +#: ./doc/common/section_cli_neutron_manage_networks.xml:173(para) +msgid "Query ports with specified fixed IP addresses:" +msgstr "" + +#: ./doc/common/section_cli_neutron_manage_networks.xml:182(para) +msgid "--fixed-ips ip_address=192.168.2.2 ip_address=192.168.2.40 is one unknown option." +msgstr "" + +#: ./doc/common/section_cli_neutron_manage_networks.xml:185(para) +msgid "How to find unknown options? The unknown options can be easily found by watching the output of create_xxx or show_xxx command. For example, in the port creation command, we see the fixed_ips fields, which can be used as an unknown option." +msgstr "" + +#: ./doc/common/section_cli_keystone_apiv3.xml:5(title) +msgid "Use Identity Service API v3 instead of API v2.0" +msgstr "" + +#: ./doc/common/section_cli_keystone_apiv3.xml:6(para) +msgid "Use the following parameters in combination on any keystone command to specify which version of the API to use:" +msgstr "" + +#: ./doc/common/section_cli_keystone_apiv3.xml:11(para) +msgid "--os-endpoint. The endpoint to use instead of the one in the service catalog. Defaults to env[OS_SERVICE_ENDPOINT]." +msgstr "" + +#: ./doc/common/section_cli_keystone_apiv3.xml:15(para) +msgid "The keystone client detects the version of the API from this parameter." +msgstr "" + +#: ./doc/common/section_cli_keystone_apiv3.xml:19(para) +msgid "--os-auth_url. The Identity Service endpoint to use for authentication. Defaults to env[OS_AUTH_URL]." +msgstr "" + +#: ./doc/common/section_cli_keystone_apiv3.xml:25(para) +msgid "--os-identity-api-version. The Identity Service API version. Defaults to env[OS_IDENTITY_API_VERSION] or 2.0." +msgstr "" + +#: ./doc/common/section_cli_keystone_apiv3.xml:31(para) +msgid "For example, use the following parameters to use API v3:" +msgstr "" + +#: ./doc/common/section_cli_keystone_apiv3.xml:33(parameter) ./doc/common/section_cli_keystone_apiv3.xml:35(parameter) +msgid "--os-auth_url" +msgstr "" + +#: ./doc/common/section_cli_keystone_apiv3.xml:33(parameter) ./doc/common/section_cli_keystone_apiv3.xml:35(parameter) +msgid "--os-identity-api-version" +msgstr "" + +#: ./doc/common/section_cli_keystone_apiv3.xml:34(para) +msgid "Use the following parameters to use API v2.0:" +msgstr "" + +#. When image changes, this message will be marked fuzzy or untranslated for you. +#. It doesn't matter what you translate it to: it's not used at all. +#: ./doc/common/section_trusted-compute-pools.xml:48(None) ./doc/common/section_trusted-compute-pools.xml:53(None) +msgid "@@image: 'figures/OpenStackTrustedComputePool1.png'; md5=858fbd6148b927723cea5ad2c88d54bd" +msgstr "" + +#. When image changes, this message will be marked fuzzy or untranslated for you. +#. It doesn't matter what you translate it to: it's not used at all. +#: ./doc/common/section_trusted-compute-pools.xml:161(None) ./doc/common/section_trusted-compute-pools.xml:166(None) +msgid "@@image: 'figures/OpenStackTrustedComputePool2.png'; md5=077261c595464638c4b3fcc92b6afb9a" +msgstr "" + +#: ./doc/common/section_trusted-compute-pools.xml:6(title) +msgid "Trusted compute pools" +msgstr "" + +#: ./doc/common/section_trusted-compute-pools.xml:7(para) +msgid "Trusted compute pools enable administrators to designate a group of compute hosts as trusted. These hosts use hardware-based security features, such as the Intel Trusted Execution Technology (TXT), to provide an additional level of security. Combined with an external stand-alone web-based remote attestation server, cloud providers can ensure that the compute node runs only software with verified measurements and can ensure a secure cloud stack." +msgstr "" + +#: ./doc/common/section_trusted-compute-pools.xml:15(para) +msgid "Through the trusted compute pools, cloud subscribers can request services to run on verified compute nodes." +msgstr "" + +#: ./doc/common/section_trusted-compute-pools.xml:17(para) +msgid "The remote attestation server performs node verification as follows:" +msgstr "" + +#: ./doc/common/section_trusted-compute-pools.xml:21(para) +msgid "Compute nodes boot with Intel TXT technology enabled." +msgstr "" + +#: ./doc/common/section_trusted-compute-pools.xml:25(para) +msgid "The compute node BIOS, hypervisor, and OS are measured." +msgstr "" + +#: ./doc/common/section_trusted-compute-pools.xml:29(para) +msgid "Measured data is sent to the attestation server when challenged by attestation server." +msgstr "" + +#: ./doc/common/section_trusted-compute-pools.xml:33(para) +msgid "The attestation server verifies those measurements against a good and known database to determine nodes' trustworthiness." +msgstr "" + +#: ./doc/common/section_trusted-compute-pools.xml:38(para) +msgid "A description of how to set up an attestation service is beyond the scope of this document. For an open source project that you can use to implement an attestation service, see the Open Attestation project." +msgstr "" + +#: ./doc/common/section_trusted-compute-pools.xml:57(title) +msgid "Configure Compute to use trusted compute pools" +msgstr "" + +#: ./doc/common/section_trusted-compute-pools.xml:60(para) +msgid "Configure the Compute service with the connection information for the attestation service." +msgstr "" + +#: ./doc/common/section_trusted-compute-pools.xml:63(para) +msgid "Specify these connection options in the trusted_computing section in the nova.conf configuration file:" +msgstr "" + +#: ./doc/common/section_trusted-compute-pools.xml:69(term) +msgid "server" +msgstr "" + +#: ./doc/common/section_trusted-compute-pools.xml:71(para) +msgid "Host name or IP address of the host that runs the attestation service" +msgstr "" + +#: ./doc/common/section_trusted-compute-pools.xml:77(term) +msgid "port" +msgstr "" + +#: ./doc/common/section_trusted-compute-pools.xml:79(para) +msgid "HTTPS port for the attestation service" +msgstr "" + +#: ./doc/common/section_trusted-compute-pools.xml:84(term) +msgid "server_ca_file" +msgstr "" + +#: ./doc/common/section_trusted-compute-pools.xml:86(para) +msgid "Certificate file used to verify the attestation server's identity." +msgstr "" + +#: ./doc/common/section_trusted-compute-pools.xml:91(term) +msgid "api_url" +msgstr "" + +#: ./doc/common/section_trusted-compute-pools.xml:93(para) +msgid "The attestation service URL path." +msgstr "" + +#: ./doc/common/section_trusted-compute-pools.xml:98(term) +msgid "auth_blob" +msgstr "" + +#: ./doc/common/section_trusted-compute-pools.xml:100(para) +msgid "An authentication blob, which is required by the attestation service." +msgstr "" + +#: ./doc/common/section_trusted-compute-pools.xml:108(para) +msgid "To enable scheduling support for trusted compute pools, add the following lines to the DEFAULT and trusted_computing sections in the /etc/nova/nova.conf file. Edit the details in the trusted_computing section based on the details of your attestation service:" +msgstr "" + +#: ./doc/common/section_trusted-compute-pools.xml:133(para) +msgid "Restart the nova-compute and nova-scheduler services." +msgstr "" + +#: ./doc/common/section_trusted-compute-pools.xml:140(title) ./doc/common/section_compute_config-api.xml:181(title) +msgid "Configuration reference" +msgstr "" + +#: ./doc/common/section_trusted-compute-pools.xml:145(title) +msgid "Specify trusted flavors" +msgstr "" + +#: ./doc/common/section_trusted-compute-pools.xml:146(para) +msgid "You must configure one or more flavors as trusted. Users can request trusted nodes by specifying a trusted flavor when they boot an instance." +msgstr "" + +#: ./doc/common/section_trusted-compute-pools.xml:150(para) +msgid "Use the command to set a flavor as trusted. For example, to set the m1.tiny flavor as trusted:" +msgstr "" + +#: ./doc/common/section_trusted-compute-pools.xml:154(para) +msgid "To request that their instances run on a trusted host, users can specify a trusted flavor on the command:" +msgstr "" + +#: ./doc/common/section_compute-configure-ec2.xml:9(title) +msgid "Configure the EC2 API" +msgstr "" + +#: ./doc/common/section_compute-configure-ec2.xml:10(para) +msgid "You can set options in the nova.conf configuration file to control which network address and port the EC2 API listens on, the formatting of some API responses, and authentication related options." +msgstr "" + +#: ./doc/common/section_compute-configure-ec2.xml:14(para) +msgid "To customize these options for OpenStack EC2 API, use these configuration option settings:" +msgstr "" + +#. ... Old module003-ch002-features-benefits edited, renamed, and stored in doc/common for use by both Cloud Admin and Operator Training Guides... +#: ./doc/common/section_objectstorage-features.xml:8(title) +msgid "Features and benefits" +msgstr "" + +#: ./doc/common/section_objectstorage-features.xml:13(th) +msgid "Features" +msgstr "" + +#: ./doc/common/section_objectstorage-features.xml:14(th) +msgid "Benefits" +msgstr "" + +#: ./doc/common/section_objectstorage-features.xml:18(emphasis) +msgid "Leverages commodity hardware" +msgstr "" + +#: ./doc/common/section_objectstorage-features.xml:21(td) +msgid "No lock-in, lower price/GB" +msgstr "" + +#: ./doc/common/section_objectstorage-features.xml:27(emphasis) +msgid "HDD/node failure agnostic" +msgstr "" + +#: ./doc/common/section_objectstorage-features.xml:28(td) +msgid "Self-healing, reliable, data redundancy protects from failures" +msgstr "" + +#: ./doc/common/section_objectstorage-features.xml:33(emphasis) +msgid "Unlimited storage" +msgstr "" + +#: ./doc/common/section_objectstorage-features.xml:34(td) +msgid "Large and flat namespace, highly scalable read/write access, able to serve content directly from storage system" +msgstr "" + +#: ./doc/common/section_objectstorage-features.xml:39(emphasis) +msgid "Multi-dimensional scalability" +msgstr "" + +#: ./doc/common/section_objectstorage-features.xml:41(td) +msgid "Scale-out architecture—Scale vertically and horizontally-distributed storage Backs up and archives large amounts of data with linear performance" +msgstr "" + +#: ./doc/common/section_objectstorage-features.xml:46(emphasis) +msgid "Account/container/object structure" +msgstr "" + +#: ./doc/common/section_objectstorage-features.xml:48(td) +msgid "No nesting, not a traditional file system—Optimized for scale, it scales to multiple petabytes and billions of objects" +msgstr "" + +#: ./doc/common/section_objectstorage-features.xml:53(emphasis) +msgid "Built-in replication 3✕ + data redundancy (compared with 2✕ on RAID)" +msgstr "" + +#: ./doc/common/section_objectstorage-features.xml:55(td) +msgid "A configurable number of accounts, containers and object copies for high availability" +msgstr "" + +#: ./doc/common/section_objectstorage-features.xml:60(emphasis) +msgid "Easily add capacity (unlike RAID resize)" +msgstr "" + +#: ./doc/common/section_objectstorage-features.xml:63(td) +msgid "Elastic data scaling with ease" +msgstr "" + +#: ./doc/common/section_objectstorage-features.xml:69(emphasis) +msgid "No central database" +msgstr "" + +#: ./doc/common/section_objectstorage-features.xml:71(td) +msgid "Higher performance, no bottlenecks" +msgstr "" + +#: ./doc/common/section_objectstorage-features.xml:77(emphasis) +msgid "RAID not required" +msgstr "" + +#: ./doc/common/section_objectstorage-features.xml:78(td) +msgid "Handle many small, random reads and writes efficiently" +msgstr "" + +#: ./doc/common/section_objectstorage-features.xml:83(emphasis) +msgid "Built-in management utilities" +msgstr "" + +#: ./doc/common/section_objectstorage-features.xml:85(td) +msgid "Account management—Create, add, verify, and delete users; Container management—Upload, download, and verify; Monitoring—Capacity, host, network, log trawling, and cluster health" +msgstr "" + +#: ./doc/common/section_objectstorage-features.xml:92(emphasis) +msgid "Drive auditing" +msgstr "" + +#: ./doc/common/section_objectstorage-features.xml:94(td) +msgid "Detect drive failures preempting data corruption" +msgstr "" + +#: ./doc/common/section_objectstorage-features.xml:100(emphasis) +msgid "Expiring objects" +msgstr "" + +#: ./doc/common/section_objectstorage-features.xml:102(td) +msgid "Users can set an expiration time or a TTL on an object to control access" +msgstr "" + +#: ./doc/common/section_objectstorage-features.xml:109(emphasis) +msgid "Direct object access" +msgstr "" + +#: ./doc/common/section_objectstorage-features.xml:111(td) +msgid "Enable direct browser access to content, such as for a control panel" +msgstr "" + +#: ./doc/common/section_objectstorage-features.xml:118(emphasis) +msgid "Realtime visibility into client requests" +msgstr "" + +#: ./doc/common/section_objectstorage-features.xml:121(td) +msgid "Know what users are requesting" +msgstr "" + +#: ./doc/common/section_objectstorage-features.xml:127(emphasis) +msgid "Supports S3 API" +msgstr "" + +#: ./doc/common/section_objectstorage-features.xml:129(td) +msgid "Utilize tools that were designed for the popular S3 API" +msgstr "" + +#: ./doc/common/section_objectstorage-features.xml:135(emphasis) +msgid "Restrict containers per account" +msgstr "" + +#: ./doc/common/section_objectstorage-features.xml:138(td) +msgid "Limit access to control usage by user" +msgstr "" + +#: ./doc/common/section_objectstorage-features.xml:144(emphasis) +msgid "Support for NetApp, Nexenta, SolidFire" +msgstr "" + +#: ./doc/common/section_objectstorage-features.xml:147(td) +msgid "Unified support for block volumes using a variety of storage systems" +msgstr "" + +#: ./doc/common/section_objectstorage-features.xml:154(emphasis) +msgid "Snapshot and backup API for block volumes" +msgstr "" + +#: ./doc/common/section_objectstorage-features.xml:157(td) +msgid "Data protection and recovery for VM data" +msgstr "" + +#: ./doc/common/section_objectstorage-features.xml:163(emphasis) +msgid "Standalone volume API available" +msgstr "" + +#: ./doc/common/section_objectstorage-features.xml:166(td) +msgid "Separate endpoint and API for integration with other compute systems" +msgstr "" + +#: ./doc/common/section_objectstorage-features.xml:173(emphasis) +msgid "Integration with Compute" +msgstr "" + +#: ./doc/common/section_objectstorage-features.xml:174(td) +msgid "Fully integrated with Compute for attaching block volumes and reporting on usage" +msgstr "" + +#: ./doc/common/section_cli_heat_commands.xml:11(title) +msgid "heat commands" +msgstr "" + +#: ./doc/common/section_cli_heat_commands.xml:12(para) +msgid "The heat client is the command-line interface (CLI) for the OpenStack Orchestration API and its extensions." +msgstr "" + +#: ./doc/common/section_cli_heat_commands.xml:20(title) +msgid "heat usage" +msgstr "" + +#: ./doc/common/section_cli_heat_commands.xml:32(title) +msgid "heat positional arguments" +msgstr "" + +#: ./doc/common/section_cli_heat_commands.xml:66(title) +msgid "heat optional arguments" +msgstr "" + +#: ./doc/common/section_cli_heat_commands.xml:112(title) +msgid "heat action-resume command" +msgstr "" + +#: ./doc/common/section_cli_heat_commands.xml:123(title) +msgid "heat action-suspend command" +msgstr "" + +#: ./doc/common/section_cli_heat_commands.xml:134(title) +msgid "heat event-list command" +msgstr "" + +#: ./doc/common/section_cli_heat_commands.xml:149(title) +msgid "heat event-show command" +msgstr "" + +#: ./doc/common/section_cli_heat_commands.xml:162(title) +msgid "heat resource-list command" +msgstr "" + +#: ./doc/common/section_cli_heat_commands.xml:173(title) +msgid "heat resource-metadata command" +msgstr "" + +#: ./doc/common/section_cli_heat_commands.xml:185(title) +msgid "heat resource-show command" +msgstr "" + +#: ./doc/common/section_cli_heat_commands.xml:197(title) +msgid "heat resource-template command" +msgstr "" + +#: ./doc/common/section_cli_heat_commands.xml:212(title) +msgid "heat resource-type-list command" +msgstr "" + +#: ./doc/common/section_cli_heat_commands.xml:220(title) +msgid "heat resource-type-show command" +msgstr "" + +#: ./doc/common/section_cli_heat_commands.xml:231(title) +msgid "heat stack-create command" +msgstr "" + +#: ./doc/common/section_cli_heat_commands.xml:262(title) +msgid "heat stack-delete command" +msgstr "" + +#: ./doc/common/section_cli_heat_commands.xml:273(title) +msgid "heat stack-list command" +msgstr "" + +#: ./doc/common/section_cli_heat_commands.xml:281(title) +msgid "heat stack-show command" +msgstr "" + +#: ./doc/common/section_cli_heat_commands.xml:292(title) +msgid "heat stack-update command" +msgstr "" + +#: ./doc/common/section_cli_heat_commands.xml:319(title) +msgid "heat template-show command" +msgstr "" + +#: ./doc/common/section_cli_heat_commands.xml:330(title) +msgid "heat template-validate command" +msgstr "" + +#: ./doc/common/section_keystone-concepts-user-management.xml:6(title) +msgid "User management" +msgstr "" + +#: ./doc/common/section_keystone-concepts-user-management.xml:7(para) +msgid "The main components of Identity user management are:" +msgstr "" + +#: ./doc/common/section_keystone-concepts-user-management.xml:10(para) +msgid "User. Represents a human user. Has associated information such as user name, password, and email. This example creates a user named alice:" +msgstr "" + +#: ./doc/common/section_keystone-concepts-user-management.xml:17(para) +msgid "Tenant. A project, group, or organization. When you make requests to OpenStack services, you must specify a tenant. For example, if you query the Compute service for a list of running instances, you get a list of all running instances in the tenant that you specified in your query. This example creates a tenant named acme:" +msgstr "" + +#: ./doc/common/section_keystone-concepts-user-management.xml:27(para) +msgid "Because the term project was used instead of tenant in earlier versions of OpenStack Compute, some command-line tools use --project_id instead of --tenant-id or --os-tenant-id to refer to a tenant ID." +msgstr "" + +#: ./doc/common/section_keystone-concepts-user-management.xml:38(para) +msgid "Role. Captures the operations that a user can perform in a given tenant." +msgstr "" + +#: ./doc/common/section_keystone-concepts-user-management.xml:40(para) +msgid "This example creates a role named compute-user:" +msgstr "" + +#: ./doc/common/section_keystone-concepts-user-management.xml:44(para) +msgid "Individual services, such as Compute and the Image Service, assign meaning to roles. In the Identity Service, a role is simply a name." +msgstr "" + +#: ./doc/common/section_keystone-concepts-user-management.xml:51(para) +msgid "The Identity Service assigns a tenant and a role to a user. You might assign the compute-user role to the alice user in the acme tenant:" +msgstr "" + +#: ./doc/common/section_keystone-concepts-user-management.xml:74(para) +msgid "A user can have different roles in different tenants. For example, Alice might also have the admin role in the Cyberdyne tenant. A user can also have multiple roles in the same tenant." +msgstr "" + +#: ./doc/common/section_keystone-concepts-user-management.xml:78(para) +msgid "The /etc/[SERVICE_CODENAME]/policy.json file controls the tasks that users can perform for a given service. For example, /etc/nova/policy.json specifies the access policy for the Compute service, /etc/glance/policy.json specifies the access policy for the Image service, and /etc/keystone/policy.json specifies the access policy for the Identity Service." +msgstr "" + +#: ./doc/common/section_keystone-concepts-user-management.xml:88(para) +msgid "The default policy.json files in the Compute, Identity, and Image service recognize only the admin role: all operations that do not require the admin role are accessible by any user that has any role in a tenant." +msgstr "" + +#: ./doc/common/section_keystone-concepts-user-management.xml:93(para) +msgid "If you wish to restrict users from performing operations in, say, the Compute service, you need to create a role in the Identity Service and then modify /etc/nova/policy.json so that this role is required for Compute operations." +msgstr "" + +#: ./doc/common/section_keystone-concepts-user-management.xml:99(para) +msgid "For example, this line in /etc/nova/policy.json specifies that there are no restrictions on which users can create volumes: if the user has any role in a tenant, they can create volumes in that tenant." +msgstr "" + +#: ./doc/common/section_keystone-concepts-user-management.xml:105(para) +msgid "To restrict creation of volumes to users who had the compute-user role in a particular tenant, you would add \"role:compute-user\", like so:" +msgstr "" + +#: ./doc/common/section_keystone-concepts-user-management.xml:110(para) +msgid "To restrict all Compute service requests to require this role, the resulting file would look like:" +msgstr "" + +#: ./doc/common/section_cli_nova_commands.xml:11(title) +msgid "nova commands" +msgstr "" + +#: ./doc/common/section_cli_nova_commands.xml:12(para) +msgid "The nova client is the command-line interface (CLI) for the OpenStack Compute API and its extensions." +msgstr "" + +#: ./doc/common/section_cli_nova_commands.xml:20(title) +msgid "nova usage" +msgstr "" + +#: ./doc/common/section_cli_nova_commands.xml:35(title) +msgid "nova positional arguments" +msgstr "" + +#: ./doc/common/section_cli_nova_commands.xml:270(title) +msgid "nova optional arguments" +msgstr "" + +#: ./doc/common/section_cli_nova_commands.xml:316(title) +msgid "nova absolute-limits command" +msgstr "" + +#: ./doc/common/section_cli_nova_commands.xml:328(title) +msgid "nova add-fixed-ip command" +msgstr "" + +#: ./doc/common/section_cli_nova_commands.xml:340(title) +msgid "nova add-secgroup command" +msgstr "" + +#: ./doc/common/section_cli_nova_commands.xml:352(title) +msgid "nova agent-create command" +msgstr "" + +#: ./doc/common/section_cli_nova_commands.xml:369(title) +msgid "nova agent-delete command" +msgstr "" + +#: ./doc/common/section_cli_nova_commands.xml:380(title) +msgid "nova agent-list command" +msgstr "" + +#: ./doc/common/section_cli_nova_commands.xml:392(title) +msgid "nova agent-modify command" +msgstr "" + +#: ./doc/common/section_cli_nova_commands.xml:406(title) +msgid "nova aggregate-add-host command" +msgstr "" + +#: ./doc/common/section_cli_nova_commands.xml:418(title) +msgid "nova aggregate-create command" +msgstr "" + +#: ./doc/common/section_cli_nova_commands.xml:430(title) +msgid "nova aggregate-delete command" +msgstr "" + +#: ./doc/common/section_cli_nova_commands.xml:441(title) +msgid "nova aggregate-details command" +msgstr "" + +#: ./doc/common/section_cli_nova_commands.xml:452(title) +msgid "nova aggregate-list command" +msgstr "" + +#: ./doc/common/section_cli_nova_commands.xml:460(title) +msgid "nova aggregate-remove-host command" +msgstr "" + +#: ./doc/common/section_cli_nova_commands.xml:472(title) +msgid "nova aggregate-set-metadata command" +msgstr "" + +#: ./doc/common/section_cli_nova_commands.xml:484(title) +msgid "nova aggregate-update command" +msgstr "" + +#: ./doc/common/section_cli_nova_commands.xml:497(title) +msgid "nova availability-zone-list command" +msgstr "" + +#: ./doc/common/section_cli_nova_commands.xml:505(title) +msgid "nova backup command" +msgstr "" + +#: ./doc/common/section_cli_nova_commands.xml:519(title) +msgid "nova baremetal-interface-add command" +msgstr "" + +#: ./doc/common/section_cli_nova_commands.xml:538(title) +msgid "nova baremetal-interface-list command" +msgstr "" + +#: ./doc/common/section_cli_nova_commands.xml:549(title) +msgid "nova baremetal-interface-remove command" +msgstr "" + +#: ./doc/common/section_cli_nova_commands.xml:561(title) +msgid "nova baremetal-node-create command" +msgstr "" + +#: ./doc/common/section_cli_nova_commands.xml:591(title) +msgid "nova baremetal-node-delete command" +msgstr "" + +#: ./doc/common/section_cli_nova_commands.xml:602(title) +msgid "nova baremetal-node-list command" +msgstr "" + +#: ./doc/common/section_cli_nova_commands.xml:610(title) +msgid "nova baremetal-node-show command" +msgstr "" + +#: ./doc/common/section_cli_nova_commands.xml:621(title) +msgid "nova boot command" +msgstr "" + +#: ./doc/common/section_cli_nova_commands.xml:706(title) +msgid "nova cell-capacities command" +msgstr "" + +#: ./doc/common/section_cli_nova_commands.xml:717(title) +msgid "nova cell-show command" +msgstr "" + +#: ./doc/common/section_cli_nova_commands.xml:728(title) +msgid "nova clear-password command" +msgstr "" + +#: ./doc/common/section_cli_nova_commands.xml:739(title) +msgid "nova cloudpipe-configure command" +msgstr "" + +#: ./doc/common/section_cli_nova_commands.xml:751(title) +msgid "nova cloudpipe-create command" +msgstr "" + +#: ./doc/common/section_cli_nova_commands.xml:762(title) +msgid "nova cloudpipe-list command" +msgstr "" + +#: ./doc/common/section_cli_nova_commands.xml:770(title) +msgid "nova console-log command" +msgstr "" + +#: ./doc/common/section_cli_nova_commands.xml:784(title) +msgid "nova credentials command" +msgstr "" + +#: ./doc/common/section_cli_nova_commands.xml:795(title) +msgid "nova delete command" +msgstr "" + +#: ./doc/common/section_cli_nova_commands.xml:806(title) +msgid "nova diagnostics command" +msgstr "" + +#: ./doc/common/section_cli_nova_commands.xml:817(title) +msgid "nova dns-create command" +msgstr "" + +#: ./doc/common/section_cli_nova_commands.xml:833(title) +msgid "nova dns-create-private-domain command" +msgstr "" + +#: ./doc/common/section_cli_nova_commands.xml:851(title) +msgid "nova dns-create-public-domain command" +msgstr "" + +#: ./doc/common/section_cli_nova_commands.xml:866(title) +msgid "nova dns-delete command" +msgstr "" + +#: ./doc/common/section_cli_nova_commands.xml:878(title) +msgid "nova dns-delete-domain command" +msgstr "" + +#: ./doc/common/section_cli_nova_commands.xml:889(title) +msgid "nova dns-domains command" +msgstr "" + +#: ./doc/common/section_cli_nova_commands.xml:897(title) +msgid "nova dns-list command" +msgstr "" + +#: ./doc/common/section_cli_nova_commands.xml:912(title) +msgid "nova endpoints command" +msgstr "" + +#: ./doc/common/section_cli_nova_commands.xml:920(title) +msgid "nova evacuate command" +msgstr "" + +#: ./doc/common/section_cli_nova_commands.xml:940(title) +msgid "nova fixed-ip-get command" +msgstr "" + +#: ./doc/common/section_cli_nova_commands.xml:951(title) +msgid "nova fixed-ip-reserve command" +msgstr "" + +#: ./doc/common/section_cli_nova_commands.xml:962(title) +msgid "nova fixed-ip-unreserve command" +msgstr "" + +#: ./doc/common/section_cli_nova_commands.xml:973(title) +msgid "nova flavor-access-add command" +msgstr "" + +#: ./doc/common/section_cli_nova_commands.xml:985(title) +msgid "nova flavor-access-list command" +msgstr "" + +#: ./doc/common/section_cli_nova_commands.xml:997(title) +msgid "nova flavor-access-remove command" +msgstr "" + +#: ./doc/common/section_cli_nova_commands.xml:1009(title) +msgid "nova flavor-create command" +msgstr "" + +#: ./doc/common/section_cli_nova_commands.xml:1036(title) +msgid "nova flavor-delete command" +msgstr "" + +#: ./doc/common/section_cli_nova_commands.xml:1047(title) +msgid "nova flavor-key command" +msgstr "" + +#: ./doc/common/section_cli_nova_commands.xml:1060(title) +msgid "nova flavor-list command" +msgstr "" + +#: ./doc/common/section_cli_nova_commands.xml:1072(title) +msgid "nova flavor-show command" +msgstr "" + +#: ./doc/common/section_cli_nova_commands.xml:1083(title) +msgid "nova floating-ip-associate command" +msgstr "" + +#: ./doc/common/section_cli_nova_commands.xml:1100(title) +msgid "nova floating-ip-bulk-create command" +msgstr "" + +#: ./doc/common/section_cli_nova_commands.xml:1117(title) +msgid "nova floating-ip-bulk-delete command" +msgstr "" + +#: ./doc/common/section_cli_nova_commands.xml:1128(title) +msgid "nova floating-ip-bulk-list command" +msgstr "" + +#: ./doc/common/section_cli_nova_commands.xml:1139(title) +msgid "nova floating-ip-create command" +msgstr "" + +#: ./doc/common/section_cli_nova_commands.xml:1150(title) +msgid "nova floating-ip-delete command" +msgstr "" + +#: ./doc/common/section_cli_nova_commands.xml:1161(title) +msgid "nova floating-ip-disassociate command" +msgstr "" + +#: ./doc/common/section_cli_nova_commands.xml:1173(title) +msgid "nova floating-ip-list command" +msgstr "" + +#: ./doc/common/section_cli_nova_commands.xml:1181(title) +msgid "nova floating-ip-pool-list command" +msgstr "" + +#: ./doc/common/section_cli_nova_commands.xml:1189(title) +msgid "nova force-delete command" +msgstr "" + +#: ./doc/common/section_cli_nova_commands.xml:1200(title) +msgid "nova get-password command" +msgstr "" + +#: ./doc/common/section_cli_nova_commands.xml:1215(title) +msgid "nova get-spice-console command" +msgstr "" + +#: ./doc/common/section_cli_nova_commands.xml:1227(title) +msgid "nova get-vnc-console command" +msgstr "" + +#: ./doc/common/section_cli_nova_commands.xml:1239(title) +msgid "nova host-action command" +msgstr "" + +#: ./doc/common/section_cli_nova_commands.xml:1253(title) +msgid "nova host-describe command" +msgstr "" + +#: ./doc/common/section_cli_nova_commands.xml:1264(title) +msgid "nova host-evacuate command" +msgstr "" + +#: ./doc/common/section_cli_nova_commands.xml:1282(title) +msgid "nova host-list command" +msgstr "" + +#: ./doc/common/section_cli_nova_commands.xml:1294(title) +msgid "nova host-meta command" +msgstr "" + +#: ./doc/common/section_cli_nova_commands.xml:1307(title) +msgid "nova host-servers-migrate command" +msgstr "" + +#: ./doc/common/section_cli_nova_commands.xml:1318(title) +msgid "nova host-update command" +msgstr "" + +#: ./doc/common/section_cli_nova_commands.xml:1337(title) +msgid "nova hypervisor-list command" +msgstr "" + +#: ./doc/common/section_cli_nova_commands.xml:1349(title) +msgid "nova hypervisor-servers command" +msgstr "" + +#: ./doc/common/section_cli_nova_commands.xml:1360(title) +msgid "nova hypervisor-show command" +msgstr "" + +#: ./doc/common/section_cli_nova_commands.xml:1371(title) +msgid "nova hypervisor-stats command" +msgstr "" + +#: ./doc/common/section_cli_nova_commands.xml:1379(title) +msgid "nova hypervisor-uptime command" +msgstr "" + +#: ./doc/common/section_cli_nova_commands.xml:1390(title) +msgid "nova image-create command" +msgstr "" + +#: ./doc/common/section_cli_nova_commands.xml:1406(title) +msgid "nova image-delete command" +msgstr "" + +#: ./doc/common/section_cli_nova_commands.xml:1417(title) +msgid "nova image-list command" +msgstr "" + +#: ./doc/common/section_cli_nova_commands.xml:1428(title) +msgid "nova image-meta command" +msgstr "" + +#: ./doc/common/section_cli_nova_commands.xml:1442(title) +msgid "nova image-show command" +msgstr "" + +#: ./doc/common/section_cli_nova_commands.xml:1453(title) +msgid "nova instance-action command" +msgstr "" + +#: ./doc/common/section_cli_nova_commands.xml:1465(title) +msgid "nova instance-action-list command" +msgstr "" + +#: ./doc/common/section_cli_nova_commands.xml:1476(title) +msgid "nova interface-attach command" +msgstr "" + +#: ./doc/common/section_cli_nova_commands.xml:1495(title) +msgid "nova interface-detach command" +msgstr "" + +#: ./doc/common/section_cli_nova_commands.xml:1507(title) +msgid "nova interface-list command" +msgstr "" + +#: ./doc/common/section_cli_nova_commands.xml:1518(title) +msgid "nova keypair-add command" +msgstr "" + +#: ./doc/common/section_cli_nova_commands.xml:1532(title) +msgid "nova keypair-delete command" +msgstr "" + +#: ./doc/common/section_cli_nova_commands.xml:1543(title) +msgid "nova keypair-list command" +msgstr "" + +#: ./doc/common/section_cli_nova_commands.xml:1551(title) +msgid "nova keypair-show command" +msgstr "" + +#: ./doc/common/section_cli_nova_commands.xml:1562(title) +msgid "nova list command" +msgstr "" + +#: ./doc/common/section_cli_nova_commands.xml:1599(title) +msgid "nova list-extensions command" +msgstr "" + +#: ./doc/common/section_cli_nova_commands.xml:1607(title) +msgid "nova list-secgroup command" +msgstr "" + +#: ./doc/common/section_cli_nova_commands.xml:1618(title) +msgid "nova live-migration command" +msgstr "" + +#: ./doc/common/section_cli_nova_commands.xml:1636(title) +msgid "nova lock command" +msgstr "" + +#: ./doc/common/section_cli_nova_commands.xml:1647(title) +msgid "nova meta command" +msgstr "" + +#: ./doc/common/section_cli_nova_commands.xml:1660(title) +msgid "nova migrate command" +msgstr "" + +#: ./doc/common/section_cli_nova_commands.xml:1674(title) +msgid "nova migration-list command" +msgstr "" + +#: ./doc/common/section_cli_nova_commands.xml:1689(title) +msgid "nova net command" +msgstr "" + +#: ./doc/common/section_cli_nova_commands.xml:1700(title) +msgid "nova net-create command" +msgstr "" + +#: ./doc/common/section_cli_nova_commands.xml:1713(title) +msgid "nova net-delete command" +msgstr "" + +#: ./doc/common/section_cli_nova_commands.xml:1724(title) +msgid "nova net-list command" +msgstr "" + +#: ./doc/common/section_cli_nova_commands.xml:1732(title) +msgid "nova network-associate-host command" +msgstr "" + +#: ./doc/common/section_cli_nova_commands.xml:1744(title) +msgid "nova network-associate-project command" +msgstr "" + +#: ./doc/common/section_cli_nova_commands.xml:1755(title) +msgid "nova network-create command" +msgstr "" + +#: ./doc/common/section_cli_nova_commands.xml:1800(title) +msgid "nova network-disassociate command" +msgstr "" + +#: ./doc/common/section_cli_nova_commands.xml:1817(title) +msgid "nova network-list command" +msgstr "" + +#: ./doc/common/section_cli_nova_commands.xml:1825(title) +msgid "nova network-show command" +msgstr "" + +#: ./doc/common/section_cli_nova_commands.xml:1836(title) +msgid "nova pause command" +msgstr "" + +#: ./doc/common/section_cli_nova_commands.xml:1847(title) +msgid "nova quota-class-show command" +msgstr "" + +#: ./doc/common/section_cli_nova_commands.xml:1858(title) +msgid "nova quota-class-update command" +msgstr "" + +#: ./doc/common/section_cli_nova_commands.xml:1905(title) +msgid "nova quota-defaults command" +msgstr "" + +#: ./doc/common/section_cli_nova_commands.xml:1916(title) +msgid "nova quota-delete command" +msgstr "" + +#: ./doc/common/section_cli_nova_commands.xml:1928(title) +msgid "nova quota-show command" +msgstr "" + +#: ./doc/common/section_cli_nova_commands.xml:1940(title) +msgid "nova quota-update command" +msgstr "" + +#: ./doc/common/section_cli_nova_commands.xml:1994(title) +msgid "nova rate-limits command" +msgstr "" + +#: ./doc/common/section_cli_nova_commands.xml:2002(title) +msgid "nova reboot command" +msgstr "" + +#: ./doc/common/section_cli_nova_commands.xml:2017(title) +msgid "nova rebuild command" +msgstr "" + +#: ./doc/common/section_cli_nova_commands.xml:2040(title) +msgid "nova remove-fixed-ip command" +msgstr "" + +#: ./doc/common/section_cli_nova_commands.xml:2052(title) +msgid "nova remove-secgroup command" +msgstr "" + +#: ./doc/common/section_cli_nova_commands.xml:2064(title) +msgid "nova rename command" +msgstr "" + +#: ./doc/common/section_cli_nova_commands.xml:2076(title) +msgid "nova rescue command" +msgstr "" + +#: ./doc/common/section_cli_nova_commands.xml:2087(title) +msgid "nova reset-network command" +msgstr "" + +#: ./doc/common/section_cli_nova_commands.xml:2098(title) +msgid "nova reset-state command" +msgstr "" + +#: ./doc/common/section_cli_nova_commands.xml:2113(title) +msgid "nova resize command" +msgstr "" + +#: ./doc/common/section_cli_nova_commands.xml:2128(title) +msgid "nova resize-confirm command" +msgstr "" + +#: ./doc/common/section_cli_nova_commands.xml:2139(title) +msgid "nova resize-revert command" +msgstr "" + +#: ./doc/common/section_cli_nova_commands.xml:2150(title) +msgid "nova restore command" +msgstr "" + +#: ./doc/common/section_cli_nova_commands.xml:2161(title) +msgid "nova resume command" +msgstr "" + +#: ./doc/common/section_cli_nova_commands.xml:2172(title) +msgid "nova root-password command" +msgstr "" + +#: ./doc/common/section_cli_nova_commands.xml:2183(title) +msgid "nova scrub command" +msgstr "" + +#: ./doc/common/section_cli_nova_commands.xml:2194(title) +msgid "nova secgroup-add-group-rule command" +msgstr "" + +#: ./doc/common/section_cli_nova_commands.xml:2210(title) +msgid "nova secgroup-add-rule command" +msgstr "" + +#: ./doc/common/section_cli_nova_commands.xml:2226(title) +msgid "nova secgroup-create command" +msgstr "" + +#: ./doc/common/section_cli_nova_commands.xml:2238(title) +msgid "nova secgroup-delete command" +msgstr "" + +#: ./doc/common/section_cli_nova_commands.xml:2249(title) +msgid "nova secgroup-delete-group-rule command" +msgstr "" + +#: ./doc/common/section_cli_nova_commands.xml:2265(title) +msgid "nova secgroup-delete-rule command" +msgstr "" + +#: ./doc/common/section_cli_nova_commands.xml:2281(title) +msgid "nova secgroup-list command" +msgstr "" + +#: ./doc/common/section_cli_nova_commands.xml:2293(title) +msgid "nova secgroup-list-rules command" +msgstr "" + +#: ./doc/common/section_cli_nova_commands.xml:2304(title) +msgid "nova secgroup-update command" +msgstr "" + +#: ./doc/common/section_cli_nova_commands.xml:2317(title) +msgid "nova service-disable command" +msgstr "" + +#: ./doc/common/section_cli_nova_commands.xml:2332(title) +msgid "nova service-enable command" +msgstr "" + +#: ./doc/common/section_cli_nova_commands.xml:2344(title) +msgid "nova service-list command" +msgstr "" + +#: ./doc/common/section_cli_nova_commands.xml:2356(title) +msgid "nova shelve command" +msgstr "" + +#: ./doc/common/section_cli_nova_commands.xml:2367(title) +msgid "nova shelve-offload command" +msgstr "" + +#: ./doc/common/section_cli_nova_commands.xml:2378(title) +msgid "nova show command" +msgstr "" + +#: ./doc/common/section_cli_nova_commands.xml:2392(title) +msgid "nova ssh command" +msgstr "" + +#: ./doc/common/section_cli_nova_commands.xml:2420(title) +msgid "nova start command" +msgstr "" + +#: ./doc/common/section_cli_nova_commands.xml:2431(title) +msgid "nova stop command" +msgstr "" + +#: ./doc/common/section_cli_nova_commands.xml:2442(title) +msgid "nova suspend command" +msgstr "" + +#: ./doc/common/section_cli_nova_commands.xml:2453(title) +msgid "nova unlock command" +msgstr "" + +#: ./doc/common/section_cli_nova_commands.xml:2464(title) +msgid "nova unpause command" +msgstr "" + +#: ./doc/common/section_cli_nova_commands.xml:2475(title) +msgid "nova unrescue command" +msgstr "" + +#: ./doc/common/section_cli_nova_commands.xml:2486(title) +msgid "nova unshelve command" +msgstr "" + +#: ./doc/common/section_cli_nova_commands.xml:2497(title) +msgid "nova usage command" +msgstr "" + +#: ./doc/common/section_cli_nova_commands.xml:2512(title) +msgid "nova usage-list command" +msgstr "" + +#: ./doc/common/section_cli_nova_commands.xml:2524(title) +msgid "nova volume-attach command" +msgstr "" + +#: ./doc/common/section_cli_nova_commands.xml:2538(title) +msgid "nova volume-create command" +msgstr "" + +#: ./doc/common/section_cli_nova_commands.xml:2571(title) +msgid "nova volume-delete command" +msgstr "" + +#: ./doc/common/section_cli_nova_commands.xml:2582(title) +msgid "nova volume-detach command" +msgstr "" + +#: ./doc/common/section_cli_nova_commands.xml:2594(title) +msgid "nova volume-list command" +msgstr "" + +#: ./doc/common/section_cli_nova_commands.xml:2606(title) +msgid "nova volume-show command" +msgstr "" + +#: ./doc/common/section_cli_nova_commands.xml:2617(title) +msgid "nova volume-snapshot-create command" +msgstr "" + +#: ./doc/common/section_cli_nova_commands.xml:2639(title) +msgid "nova volume-snapshot-delete command" +msgstr "" + +#: ./doc/common/section_cli_nova_commands.xml:2650(title) +msgid "nova volume-snapshot-list command" +msgstr "" + +#: ./doc/common/section_cli_nova_commands.xml:2658(title) +msgid "nova volume-snapshot-show command" +msgstr "" + +#: ./doc/common/section_cli_nova_commands.xml:2669(title) +msgid "nova volume-type-create command" +msgstr "" + +#: ./doc/common/section_cli_nova_commands.xml:2680(title) +msgid "nova volume-type-delete command" +msgstr "" + +#: ./doc/common/section_cli_nova_commands.xml:2691(title) +msgid "nova volume-type-list command" +msgstr "" + +#: ./doc/common/section_cli_nova_commands.xml:2699(title) +msgid "nova volume-update command" +msgstr "" + +#: ./doc/common/section_cli_nova_commands.xml:2712(title) +msgid "nova x509-create-cert command" +msgstr "" + +#: ./doc/common/section_cli_nova_commands.xml:2725(title) +msgid "nova x509-get-root-cert command" +msgstr "" + +#: ./doc/common/section_compute-configure-spice.xml:6(title) +msgid "SPICE console" +msgstr "" + +#: ./doc/common/section_compute-configure-spice.xml:7(para) +msgid "OpenStack Compute supports VNC consoles to guests. The VNC protocol is fairly limited, lacking support for multiple monitors, bi-directional audio, reliable cut-and-paste, video streaming and more. SPICE is a new protocol that aims to address the limitations in VNC and provide good remote desktop support." +msgstr "" + +#: ./doc/common/section_compute-configure-spice.xml:19(para) +msgid "If you do not configure SPICE correctly, Compute falls back on VNC." +msgstr "" + +#: ./doc/common/section_compute-configure-spice.xml:12(para) +msgid "SPICE support in OpenStack Compute shares a similar architecture to the VNC implementation. The OpenStack dashboard uses a SPICE-HTML5 widget in its console tab that communicates to the nova-spicehtml5proxy service by using SPICE-over-websockets. The nova-spicehtml5proxy service communicates directly with the hypervisor process by using SPICE." +msgstr "" + +#: ./doc/common/section_compute-configure-spice.xml:22(para) +msgid "The following table shows the options to configure SPICE as the console for OpenStack Compute:" +msgstr "" + +#: ./doc/common/section_dashboard-configure.xml:6(title) +msgid "Configure the dashboard" +msgstr "" + +#: ./doc/common/section_dashboard-configure.xml:8(para) +msgid "You can configure the dashboard for a simple HTTP deployment." +msgstr "" + +#: ./doc/common/section_dashboard-configure.xml:14(para) +msgid "Also, you can configure the size of the VNC window in the dashboard." +msgstr "" + +#: ./doc/common/section_dashboard-configure-http.xml:6(title) +msgid "Configure the dashboard for HTTP" +msgstr "" + +#: ./doc/common/section_dashboard-configure-http.xml:8(para) +msgid "You can configure the dashboard for a simple HTTP deployment. The standard installation uses a non-encrypted HTTP channel." +msgstr "" + +#: ./doc/common/section_dashboard-configure-http.xml:12(para) +msgid "Specify the host for your OpenStack Identity Service endpoint in the /etc/openstack-dashboard/local_settings.py file with the OPENSTACK_HOST setting." +msgstr "" + +#: ./doc/common/section_dashboard-configure-http.xml:17(para) +msgid "The following example shows this setting:" +msgstr "" + +#: ./doc/common/section_dashboard-configure-http.xml:19(para) +msgid "The service catalog configuration in the Identity Service determines whether a service appears in the dashboard. For the full listing, see Horizon Settings and Configuration." +msgstr "" + +#: ./doc/common/section_dashboard-configure-http.xml:28(para) +msgid "Restart Apache http server. For Ubuntu/Debian/SUSE:" +msgstr "" + +#: ./doc/common/section_dashboard-configure-http.xml:30(para) +msgid "or for Fedora/RHEL/CentOS:" +msgstr "" + +#. When image changes, this message will be marked fuzzy or untranslated for you. +#. It doesn't matter what you translate it to: it's not used at all. +#: ./doc/common/section_dashboard_access.xml:86(None) +msgid "@@image: 'figures/dashboard-project-tab.png'; md5=d3d853ce44ba4f82a5c957ea1302430c" +msgstr "" + +#. When image changes, this message will be marked fuzzy or untranslated for you. +#. It doesn't matter what you translate it to: it's not used at all. +#: ./doc/common/section_dashboard_access.xml:209(None) +msgid "@@image: 'figures/dashboard-admin-tab.png'; md5=badc7ae21a0956572dcabeacd7117971" +msgstr "" + +#: ./doc/common/section_dashboard_access.xml:14(title) +msgid "Log in to the dashboard" +msgstr "" + +#: ./doc/common/section_dashboard_access.xml:15(para) +msgid "The dashboard is available on the node with the nova-dashboard server role." +msgstr "" + +#: ./doc/common/section_dashboard_access.xml:19(para) +msgid "Ask the cloud operator for the host name or public IP address from which you can access the dashboard, and your user name and password." +msgstr "" + +#: ./doc/common/section_dashboard_access.xml:24(para) +msgid "Open a Web browser. Make sure that JavaScript and cookies are enabled." +msgstr "" + +#: ./doc/common/section_dashboard_access.xml:27(para) +msgid "To use the Virtual Network Computing (VNC) client for the dashboard, your browser must support HTML5 Canvas and HTML5 WebSockets. The VNC client is based on noVNC. For details, see noVNC: HTML5 VNC Client. For a list of supported browsers, see Browser support." +msgstr "" + +#: ./doc/common/section_dashboard_access.xml:40(para) +msgid "In the address bar, type the host name or IP address for the dashboard:" +msgstr "" + +#: ./doc/common/section_dashboard_access.xml:42(replaceable) +msgid "IP_ADDRESS_OR_HOSTNAME" +msgstr "" + +#: ./doc/common/section_dashboard_access.xml:44(title) +msgid "Certificate warning" +msgstr "" + +#: ./doc/common/section_dashboard_access.xml:45(para) +msgid "If a certificate warning appears when you try to access the URL for the first time, a self-signed certificate is in use, which is not considered trustworthy by default. Verify the certificate or add an exception in the browser to bypass the warning." +msgstr "" + +#: ./doc/common/section_dashboard_access.xml:54(para) +msgid "On the Log In page, enter your user name and password, and click Sign In." +msgstr "" + +#: ./doc/common/section_dashboard_access.xml:57(para) +msgid "The top-level row shows your user name. You can also access Settings or sign out of the dashboard." +msgstr "" + +#: ./doc/common/section_dashboard_access.xml:60(para) +msgid "The visible tabs and functions in the dashboard depend on the access permissions, or roles, of the user you are logged in as." +msgstr "" + +#: ./doc/common/section_dashboard_access.xml:64(para) +msgid "If you are logged in as an end user, the main screen shows the Project tab." +msgstr "" + +#: ./doc/common/section_dashboard_access.xml:67(para) +msgid "If you are logged in as an administrator, the main screen shows the Project tab and Admin tab." +msgstr "" + +#: ./doc/common/section_dashboard_access.xml:75(title) +msgid "OpenStack dashboard—Project tab" +msgstr "" + +#: ./doc/common/section_dashboard_access.xml:76(para) +msgid "Select a project from the CURRENT PROJECT drop-down list on the left side to view and manage resources in that project." +msgstr "" + +#: ./doc/common/section_dashboard_access.xml:79(para) +msgid "The Project tab displays the details of the selected project." +msgstr "" + +#: ./doc/common/section_dashboard_access.xml:82(title) +msgid "Dashboard projects" +msgstr "" + +#: ./doc/common/section_dashboard_access.xml:90(para) +msgid "Access the following tabs:" +msgstr "" + +#: ./doc/common/section_dashboard_access.xml:91(para) +msgid "Manage Compute tab" +msgstr "" + +#: ./doc/common/section_dashboard_access.xml:94(guilabel) ./doc/common/section_dashboard_access.xml:216(guilabel) ./doc/common/section_cli_overview.xml:14(title) +msgid "Overview" +msgstr "" + +#: ./doc/common/section_dashboard_access.xml:96(para) +msgid "View reports for the project." +msgstr "" + +#: ./doc/common/section_dashboard_access.xml:100(guilabel) ./doc/common/section_dashboard_access.xml:264(guilabel) +msgid "Instances" +msgstr "" + +#: ./doc/common/section_dashboard_access.xml:102(para) +msgid "View, launch, create a snapshot from, stop, pause, or reboot instances, or connect to them through VNC." +msgstr "" + +#: ./doc/common/section_dashboard_access.xml:110(para) +msgid "View, create, edit, and delete volumes." +msgstr "" + +#: ./doc/common/section_dashboard_access.xml:115(guilabel) +msgid "Images & Snapshots" +msgstr "" + +#: ./doc/common/section_dashboard_access.xml:118(para) +msgid "View images, instance snapshots, and volume snapshots created project users, plus any images that are publicly available. Create, edit, and delete images, and launch instances from images and snapshots." +msgstr "" + +#: ./doc/common/section_dashboard_access.xml:126(guilabel) +msgid "Access & Security" +msgstr "" + +#: ./doc/common/section_dashboard_access.xml:129(para) +msgid "Use the following tabs to complete these tasks:" +msgstr "" + +#: ./doc/common/section_dashboard_access.xml:132(title) +msgid "Security Groups tab" +msgstr "" + +#: ./doc/common/section_dashboard_access.xml:134(para) +msgid "View, create, edit, and delete security groups and security group rules." +msgstr "" + +#: ./doc/common/section_dashboard_access.xml:138(title) +msgid "Keypairs tab" +msgstr "" + +#: ./doc/common/section_dashboard_access.xml:140(para) +msgid "View, create, edit, and import keypairs, and delete keypairs." +msgstr "" + +#: ./doc/common/section_dashboard_access.xml:144(title) +msgid "Floating IPs tab" +msgstr "" + +#: ./doc/common/section_dashboard_access.xml:146(para) +msgid "Allocate an IP address to or release it from a project." +msgstr "" + +#: ./doc/common/section_dashboard_access.xml:150(title) +msgid "API Access tab" +msgstr "" + +#: ./doc/common/section_dashboard_access.xml:152(para) +msgid "View API endpoints." +msgstr "" + +#: ./doc/common/section_dashboard_access.xml:157(para) +msgid "Manage Network tab" +msgstr "" + +#: ./doc/common/section_dashboard_access.xml:160(guilabel) ./doc/common/section_dashboard_access.xml:296(guilabel) +msgid "Networks" +msgstr "" + +#: ./doc/common/section_dashboard_access.xml:162(para) +msgid "Create and manage public and private networks." +msgstr "" + +#: ./doc/common/section_dashboard_access.xml:166(guilabel) ./doc/common/section_dashboard_access.xml:303(guilabel) +msgid "Routers" +msgstr "" + +#: ./doc/common/section_dashboard_access.xml:168(para) +msgid "Create and manage subnets." +msgstr "" + +#: ./doc/common/section_dashboard_access.xml:172(guilabel) +msgid "Network Topology" +msgstr "" + +#: ./doc/common/section_dashboard_access.xml:174(para) +msgid "View the network topology." +msgstr "" + +#: ./doc/common/section_dashboard_access.xml:178(para) +msgid "Object Store tab" +msgstr "" + +#: ./doc/common/section_dashboard_access.xml:181(guilabel) +msgid "Containers" +msgstr "" + +#: ./doc/common/section_dashboard_access.xml:183(para) +msgid "Create and manage object storage." +msgstr "" + +#: ./doc/common/section_dashboard_access.xml:187(para) +msgid "Orchestration tab" +msgstr "" + +#: ./doc/common/section_dashboard_access.xml:190(guilabel) +msgid "Stacks" +msgstr "" + +#: ./doc/common/section_dashboard_access.xml:192(para) +msgid "Use REST API to orchestrate multiple composite cloud applications" +msgstr "" + +#: ./doc/common/section_dashboard_access.xml:199(title) +msgid "OpenStack dashboard—Admin tab" +msgstr "" + +#: ./doc/common/section_dashboard_access.xml:200(para) +msgid "Enables administrative users to view usage and manage instances, volumes, flavors, images, projects, users, services, and quotas." +msgstr "" + +#: ./doc/common/section_dashboard_access.xml:204(title) +msgid "Admin tab" +msgstr "" + +#: ./doc/common/section_dashboard_access.xml:213(para) +msgid "Access the following categories to complete these tasks:" +msgstr "" + +#: ./doc/common/section_dashboard_access.xml:218(para) +msgid "View basic reports." +msgstr "" + +#: ./doc/common/section_dashboard_access.xml:222(guilabel) +msgid "Resource Usage" +msgstr "" + +#: ./doc/common/section_dashboard_access.xml:224(para) +msgid "Use the following tabs to view the following usages:" +msgstr "" + +#: ./doc/common/section_dashboard_access.xml:226(title) +msgid "Global Disk Usage tab" +msgstr "" + +#: ./doc/common/section_dashboard_access.xml:228(para) +msgid "View the global disk usage for all tenants as an average over the last 30 days." +msgstr "" + +#: ./doc/common/section_dashboard_access.xml:232(title) +msgid "Global Network Traffic Usage tab" +msgstr "" + +#: ./doc/common/section_dashboard_access.xml:234(para) ./doc/common/section_dashboard_access.xml:247(para) +msgid "View the global network usage for all tenants as an average over the last 30 days." +msgstr "" + +#: ./doc/common/section_dashboard_access.xml:238(title) +msgid "Global Object Storage Usage tab" +msgstr "" + +#: ./doc/common/section_dashboard_access.xml:240(para) +msgid "View the global object storage usage for all tenants as an average over the last 30 days." +msgstr "" + +#: ./doc/common/section_dashboard_access.xml:245(title) +msgid "Global Network Usage tab" +msgstr "" + +#: ./doc/common/section_dashboard_access.xml:251(title) +msgid "Stats tab" +msgstr "" + +#: ./doc/common/section_dashboard_access.xml:253(para) +msgid "View the statistics of all resources." +msgstr "" + +#: ./doc/common/section_dashboard_access.xml:258(guilabel) +msgid "Hypervisors" +msgstr "" + +#: ./doc/common/section_dashboard_access.xml:260(para) +msgid "View the hypervisor summary." +msgstr "" + +#: ./doc/common/section_dashboard_access.xml:266(para) +msgid "View, pause, resume, suspend, migrate, soft or hard reboot, and delete running instances that belong to users of some, but not all, projects. Also, view the log for an instance or access an instance through VNC." +msgstr "" + +#: ./doc/common/section_dashboard_access.xml:276(para) +msgid "View, create, edit, and delete volumes and volume types." +msgstr "" + +#: ./doc/common/section_dashboard_access.xml:283(para) +msgid "View, create, edit, view extra specs for, and delete flavors. A flavor is size for an instance." +msgstr "" + +#: ./doc/common/section_dashboard_access.xml:289(guilabel) +msgid "Images" +msgstr "" + +#: ./doc/common/section_dashboard_access.xml:291(para) +msgid "View, create, edit properties for, and delete custom images." +msgstr "" + +#: ./doc/common/section_dashboard_access.xml:298(para) +msgid "View, create, edit properties for, and delete networks." +msgstr "" + +#: ./doc/common/section_dashboard_access.xml:305(para) +msgid "View, create, edit properties for, and delete routers." +msgstr "" + +#: ./doc/common/section_dashboard_access.xml:310(guilabel) +msgid "Defaults" +msgstr "" + +#: ./doc/common/section_dashboard_access.xml:312(para) +msgid "View default quota values. Quotas are hard-coded in OpenStack Compute and define the maximum allowable size and number of resources." +msgstr "" + +#: ./doc/common/section_dashboard_access.xml:319(guilabel) +msgid "System Info" +msgstr "" + +#: ./doc/common/section_dashboard_access.xml:321(para) +msgid "Use the following tabs to view the service info:" +msgstr "" + +#: ./doc/common/section_dashboard_access.xml:323(title) +msgid "Services tab" +msgstr "" + +#: ./doc/common/section_dashboard_access.xml:324(para) +msgid "View a list of the services." +msgstr "" + +#: ./doc/common/section_dashboard_access.xml:327(title) +msgid "Compute Services tab" +msgstr "" + +#: ./doc/common/section_dashboard_access.xml:328(para) +msgid "View a list of all Compute services." +msgstr "" + +#: ./doc/common/section_dashboard_access.xml:331(title) +msgid "Availability Zones tab" +msgstr "" + +#: ./doc/common/section_dashboard_access.xml:333(para) +msgid "View the availability zones." +msgstr "" + +#: ./doc/common/section_dashboard_access.xml:336(title) +msgid "Host Aggregates tab" +msgstr "" + +#: ./doc/common/section_dashboard_access.xml:337(para) +msgid "View host aggregates." +msgstr "" + +#: ./doc/common/section_dashboard_access.xml:340(title) +msgid "Network Agents tab" +msgstr "" + +#: ./doc/common/section_dashboard_access.xml:342(para) +msgid "View the network agents." +msgstr "" + +#: ./doc/common/section_dashboard_access.xml:349(para) +msgid "View domains." +msgstr "" + +#: ./doc/common/section_dashboard_access.xml:353(guilabel) +msgid "Projects" +msgstr "" + +#: ./doc/common/section_dashboard_access.xml:355(para) +msgid "View, create, assign users to, remove users from, and delete projects." +msgstr "" + +#: ./doc/common/section_dashboard_access.xml:360(guilabel) +msgid "Users" +msgstr "" + +#: ./doc/common/section_dashboard_access.xml:362(para) +msgid "View, create, enable, disable, and delete users." +msgstr "" + +#: ./doc/common/section_dashboard_access.xml:367(guilabel) ./doc/common/section_keystone-concepts-group-management.xml:6(title) +msgid "Groups" +msgstr "" + +#: ./doc/common/section_dashboard_access.xml:369(para) +msgid "View, create, enable, disable, and delete groups." +msgstr "" + +#: ./doc/common/section_dashboard_access.xml:374(guilabel) +msgid "Roles" +msgstr "" + +#: ./doc/common/section_dashboard_access.xml:376(para) +msgid "View, create, enable, disable, and delete roles." +msgstr "" + +#: ./doc/common/ch_using_openstack_overview.xml:10(title) +msgid "How can I useadminister an OpenStack cloud?" +msgstr "" + +#: ./doc/common/ch_using_openstack_overview.xml:14(para) +msgid "As an OpenStack cloud end user, you can provision your own resources within the limits set by administrators." +msgstr "" + +#: ./doc/common/ch_using_openstack_overview.xml:17(para) +msgid "As an OpenStack cloud administrative user, you can manage tenants, known as projects, users, services, images, flavors, and quotas." +msgstr "" + +#: ./doc/common/ch_using_openstack_overview.xml:21(para) +msgid "The examples in this guide show you how to complete these tasks with either:" +msgstr "" + +#: ./doc/common/ch_using_openstack_overview.xml:25(para) +msgid "The OpenStack dashboard. Use this Web-based graphical interface, code named horizon, to view, create, and manage resources and services." +msgstr "" + +#: ./doc/common/ch_using_openstack_overview.xml:33(para) +msgid "The OpenStack command-line clients. Each core OpenStack project has a command-line client that lets you run simple commands to view, create, and manage resources and services in a cloud and automate tasks by using scripts." +msgstr "" + +#: ./doc/common/ch_using_openstack_overview.xml:41(para) +msgid "You can modify these examples for your specific use cases." +msgstr "" + +#: ./doc/common/ch_using_openstack_overview.xml:43(para) +msgid "In addition to these ways of interacting with a cloud, you can access the OpenStack APIs directly or indirectly through cURL commands or open SDKs. You can automate access or build tools to manage resources and services by using the native OpenStack APIs or the EC2 compatibility API." +msgstr "" + +#: ./doc/common/ch_using_openstack_overview.xml:49(para) +msgid "To use the OpenStack APIs, it helps to be familiar with HTTP/1.1, RESTful web services, the OpenStack services, and JSON or XML data serialization formats." +msgstr "" + +#: ./doc/common/section_xapi-ami-setup.xml:7(title) +msgid "Prepare for AMI type images" +msgstr "" + +#: ./doc/common/section_xapi-ami-setup.xml:8(para) +msgid "To support AMI type images in your OpenStack installation, you must create a /boot/guest directory inside Dom0. The OpenStack VM extracts the kernel and ramdisk from the AKI and ARI images puts them in this location." +msgstr "" + +#: ./doc/common/section_xapi-ami-setup.xml:12(para) +msgid "OpenStack maintains the contents of this directory and its size should not increase during normal operation. However, in case of power failures or accidental shutdowns, some files might be left over. To prevent these files from filling the Dom0 disk, set up this directory as a symlink that points to a subdirectory of the local SR." +msgstr "" + +#: ./doc/common/section_xapi-ami-setup.xml:18(para) +msgid "Run these commands in Dom0 to achieve this setup:" +msgstr "" + +#: ./doc/common/section_about-object-storage.xml:8(para) +msgid "Object Storage is a robust, highly scalable and fault tolerant storage platform for unstructured data such as objects. Objects are stored bits, accessed through a RESTful, HTTP-based interface. You cannot access data at the block or file level. Object Storage is commonly used to archive and back up data, with use cases in virtual machine image, photo, video and music storage." +msgstr "" + +#: ./doc/common/section_about-object-storage.xml:15(para) +msgid "Object Storage provides a high degree of availability, throughput, and performance with its scale out architecture. Each object is replicated across multiple servers, residing within the same data center or across data centers, which mitigates the risk of network and hardware failure. In the event of hardware failure, Object Storage will automatically copy objects to a new location to ensure that there are always three copies available. Object Storage is an eventually consistent distributed storage platform; it sacrifices consistency for maximum availability and partition tolerance. Object Storage enables you to create a reliable platform by using commodity hardware and inexpensive storage." +msgstr "" + +#: ./doc/common/section_about-object-storage.xml:27(para) +msgid "For more information, review the key concepts in the developer documentation at docs.openstack.org/developer/swift/." +msgstr "" + +#: ./doc/common/section_cli_cinder_manage_volumes.xml:7(title) +msgid "Manage volumes" +msgstr "" + +#: ./doc/common/section_cli_cinder_manage_volumes.xml:8(para) +msgid "A volume is a detachable block storage device, similar to a USB hard drive. You can attach a volume to only one instance. To create and manage volumes, you use a combination of nova and cinder client commands." +msgstr "" + +#: ./doc/common/section_cli_cinder_manage_volumes.xml:12(para) +msgid "This example creates a my-new-volume volume based on an image." +msgstr "" + +#: ./doc/common/section_cli_cinder_manage_volumes.xml:16(title) +msgid "Migrate a volume" +msgstr "" + +#: ./doc/common/section_cli_cinder_manage_volumes.xml:17(para) +msgid "As an administrator, you can migrate a volume with its data from one location to another in a manner that is transparent to users and workloads. You can migrate only detached volumes with no snapshots." +msgstr "" + +#: ./doc/common/section_cli_cinder_manage_volumes.xml:21(para) +msgid "Possible use cases for data migration:" +msgstr "" + +#: ./doc/common/section_cli_cinder_manage_volumes.xml:24(para) +msgid "Bring down a physical storage device for maintenance without disrupting workloads." +msgstr "" + +#: ./doc/common/section_cli_cinder_manage_volumes.xml:28(para) +msgid "Modify the properties of a volume." +msgstr "" + +#: ./doc/common/section_cli_cinder_manage_volumes.xml:31(para) +msgid "Free up space in a thinly-provisioned back end." +msgstr "" + +#: ./doc/common/section_cli_cinder_manage_volumes.xml:35(para) +msgid "Migrate a volume, as follows:" +msgstr "" + +#: ./doc/common/section_cli_cinder_manage_volumes.xml:36(replaceable) ./doc/common/section_cli_cinder_manage_volumes.xml:288(replaceable) +msgid "volumeID" +msgstr "" + +#: ./doc/common/section_cli_cinder_manage_volumes.xml:36(replaceable) +msgid "destinationHost" +msgstr "" + +#: ./doc/common/section_cli_cinder_manage_volumes.xml:36(replaceable) +msgid "True|False" +msgstr "" + +#: ./doc/common/section_cli_cinder_manage_volumes.xml:37(para) +msgid "Where --force-host-copy=True forces the generic host-based migration mechanism and bypasses any driver optimizations." +msgstr "" + +#: ./doc/common/section_cli_cinder_manage_volumes.xml:41(para) +msgid "If the volume is in use or has snapshots, the specified host destination cannot accept the volume." +msgstr "" + +#: ./doc/common/section_cli_cinder_manage_volumes.xml:44(para) +msgid "If the user is not an administrator, the migration fails." +msgstr "" + +#: ./doc/common/section_cli_cinder_manage_volumes.xml:49(title) +msgid "Create a volume" +msgstr "" + +#: ./doc/common/section_cli_cinder_manage_volumes.xml:52(para) +msgid "List images, and note the ID of the image to use for your volume:" +msgstr "" + +#: ./doc/common/section_cli_cinder_manage_volumes.xml:66(para) +msgid "List the availability zones, and note the ID of the availability zone in which to create your volume:" +msgstr "" + +#: ./doc/common/section_cli_cinder_manage_volumes.xml:86(para) +msgid "Create a volume with 8 GBs of space. Specify the availability zone and image:" +msgstr "" + +#: ./doc/common/section_cli_cinder_manage_volumes.xml:109(para) +msgid "To verify that your volume was created successfully, list the available volumes:" +msgstr "" + +#: ./doc/common/section_cli_cinder_manage_volumes.xml:118(para) +msgid "If your volume was created successfully, its status is available. If its status is error, you might have exceeded your quota." +msgstr "" + +#: ./doc/common/section_cli_cinder_manage_volumes.xml:126(title) +msgid "Attach a volume to an instance" +msgstr "" + +#: ./doc/common/section_cli_cinder_manage_volumes.xml:129(para) +msgid "Attach your volume to a server:" +msgstr "" + +#: ./doc/common/section_cli_cinder_manage_volumes.xml:139(para) +msgid "Note the ID of your volume." +msgstr "" + +#: ./doc/common/section_cli_cinder_manage_volumes.xml:142(para) +msgid "Show information for your volume:" +msgstr "" + +#: ./doc/common/section_cli_cinder_manage_volumes.xml:164(para) +msgid "The output shows that the volume is attached to the server with ID 84c6e57d-a6b1-44b6-81eb-fcb36afd31b5, is in the nova availability zone, and is bootable." +msgstr "" + +#: ./doc/common/section_cli_cinder_manage_volumes.xml:173(title) +msgid "Resize a volume" +msgstr "" + +#: ./doc/common/section_cli_cinder_manage_volumes.xml:176(para) +msgid "To resize your volume, you must first detach it from the server." +msgstr "" + +#: ./doc/common/section_cli_cinder_manage_volumes.xml:178(para) +msgid "To detach the volume from your server, pass the server ID and volume ID to the command:" +msgstr "" + +#: ./doc/common/section_cli_cinder_manage_volumes.xml:181(para) ./doc/common/section_cli_cinder_manage_volumes.xml:200(para) +msgid "The command does not return any output." +msgstr "" + +#: ./doc/common/section_cli_cinder_manage_volumes.xml:185(para) +msgid "List volumes:" +msgstr "" + +#: ./doc/common/section_cli_cinder_manage_volumes.xml:193(para) +msgid "Note that the volume is now available." +msgstr "" + +#: ./doc/common/section_cli_cinder_manage_volumes.xml:196(para) +msgid "Resize the volume by passing the volume ID and the new size (a value greater than the old one) as parameters:" +msgstr "" + +#: ./doc/common/section_cli_cinder_manage_volumes.xml:199(replaceable) +msgid "573e024d-5235-49ce-8332-be1576d323f8" +msgstr "" + +#: ./doc/common/section_cli_cinder_manage_volumes.xml:199(replaceable) +msgid "10" +msgstr "" + +#: ./doc/common/section_cli_cinder_manage_volumes.xml:206(title) +msgid "Delete a volume" +msgstr "" + +#: ./doc/common/section_cli_cinder_manage_volumes.xml:209(para) +msgid "To delete your volume, you must first detach it from the server." +msgstr "" + +#: ./doc/common/section_cli_cinder_manage_volumes.xml:211(para) +msgid "To detach the volume from your server and check for the list of existing volumes, see steps 1 and 2 mentioned in ." +msgstr "" + +#: ./doc/common/section_cli_cinder_manage_volumes.xml:217(para) ./doc/common/section_cli_cinder_manage_volumes.xml:408(para) +msgid "Delete the volume:" +msgstr "" + +#: ./doc/common/section_cli_cinder_manage_volumes.xml:219(para) +msgid "The delete command does not return any output." +msgstr "" + +#: ./doc/common/section_cli_cinder_manage_volumes.xml:223(para) +msgid "List the volumes again, and note that the status of your volume is deleting:" +msgstr "" + +#: ./doc/common/section_cli_cinder_manage_volumes.xml:233(para) +msgid "When the volume is fully deleted, it disappears from the list of volumes:" +msgstr "" + +#: ./doc/common/section_cli_cinder_manage_volumes.xml:245(title) +msgid "Transfer a volume" +msgstr "" + +#: ./doc/common/section_cli_cinder_manage_volumes.xml:246(para) +msgid "You can transfer a volume from one owner to another by using the commands. The volume donor, or original owner, creates a transfer request and sends the created transfer ID and authorization key to the volume recipient. The volume recipient, or new owner, accepts the transfer by using the ID and key." +msgstr "" + +#: ./doc/common/section_cli_cinder_manage_volumes.xml:254(para) +msgid "The procedure for volume transfer is intended for tenants (both the volume donor and recipient) within the same cloud." +msgstr "" + +#: ./doc/common/section_cli_cinder_manage_volumes.xml:256(para) +msgid "Use cases include:" +msgstr "" + +#: ./doc/common/section_cli_cinder_manage_volumes.xml:259(para) +msgid "Create a custom bootable volume or a volume with a large data set and transfer it to the end customer." +msgstr "" + +#: ./doc/common/section_cli_cinder_manage_volumes.xml:264(para) +msgid "For bulk import of data to the cloud, the data ingress system creates a new Block Storage volume, copies data from the physical device, and transfers device ownership to the end user." +msgstr "" + +#: ./doc/common/section_cli_cinder_manage_volumes.xml:271(title) +msgid "Create a volume transfer request" +msgstr "" + +#: ./doc/common/section_cli_cinder_manage_volumes.xml:274(para) +msgid "While logged in as the volume donor, list available volumes:" +msgstr "" + +#: ./doc/common/section_cli_cinder_manage_volumes.xml:285(para) +msgid "As the volume donor, request a volume transfer authorization code for a specific volume:" +msgstr "" + +#: ./doc/common/section_cli_cinder_manage_volumes.xml:289(para) +msgid "The volume must be in an ‘available’ state or the request will be denied. If the transfer request is valid in the database (that is, it has not expired or been deleted), the volume is placed in an awaiting transfer state. For example:" +msgstr "" + +#: ./doc/common/section_cli_cinder_manage_volumes.xml:307(para) +msgid "Optionally, you can specify a name for the transfer by using the --display-name displayName parameter." +msgstr "" + +#: ./doc/common/section_cli_cinder_manage_volumes.xml:315(para) +msgid "Send the volume transfer ID and authorization key to the new owner (for example, by email)." +msgstr "" + +#: ./doc/common/section_cli_cinder_manage_volumes.xml:320(para) +msgid "View pending transfers:" +msgstr "" + +#: ./doc/common/section_cli_cinder_manage_volumes.xml:329(para) +msgid "After the volume recipient, or new owner, accepts the transfer, you can see that the transfer is no longer available:" +msgstr "" + +#: ./doc/common/section_cli_cinder_manage_volumes.xml:341(title) +msgid "Accept a volume transfer request" +msgstr "" + +#: ./doc/common/section_cli_cinder_manage_volumes.xml:344(para) +msgid "As the volume recipient, you must first obtain the transfer ID and authorization key from the original owner." +msgstr "" + +#: ./doc/common/section_cli_cinder_manage_volumes.xml:349(para) +msgid "Display the transfer request details using the ID:" +msgstr "" + +#: ./doc/common/section_cli_cinder_manage_volumes.xml:351(replaceable) ./doc/common/section_cli_cinder_manage_volumes.xml:365(replaceable) ./doc/common/section_cli_cinder_manage_volumes.xml:409(replaceable) +msgid "transferID" +msgstr "" + +#: ./doc/common/section_cli_cinder_manage_volumes.xml:364(para) +msgid "Accept the request:" +msgstr "" + +#: ./doc/common/section_cli_cinder_manage_volumes.xml:365(replaceable) +msgid "authKey" +msgstr "" + +#: ./doc/common/section_cli_cinder_manage_volumes.xml:376(para) +msgid "If you do not have a sufficient quota for the transfer, the transfer is refused." +msgstr "" + +#: ./doc/common/section_cli_cinder_manage_volumes.xml:384(title) +msgid "Delete a volume transfer" +msgstr "" + +#: ./doc/common/section_cli_cinder_manage_volumes.xml:388(para) +msgid "List available volumes and their statuses:" +msgstr "" + +#: ./doc/common/section_cli_cinder_manage_volumes.xml:399(para) +msgid "Find the matching transfer ID:" +msgstr "" + +#: ./doc/common/section_cli_cinder_manage_volumes.xml:414(para) +msgid "The transfer list is now empty and the volume is again available for transfer:" +msgstr "" + +#: ./doc/common/section_cli_glance_commands.xml:11(title) +msgid "glance commands" +msgstr "" + +#: ./doc/common/section_cli_glance_commands.xml:12(para) +msgid "The glance client is the command-line interface (CLI) for the OpenStack Image Service API and its extensions." +msgstr "" + +#: ./doc/common/section_cli_glance_commands.xml:20(title) +msgid "glance usage" +msgstr "" + +#: ./doc/common/section_cli_glance_commands.xml:37(title) +msgid "glance positional arguments" +msgstr "" + +#: ./doc/common/section_cli_glance_commands.xml:64(title) +msgid "glance optional arguments" +msgstr "" + +#: ./doc/common/section_cli_glance_commands.xml:135(title) +msgid "glance image-create command" +msgstr "" + +#: ./doc/common/section_cli_glance_commands.xml:195(title) +msgid "glance image-delete command" +msgstr "" + +#: ./doc/common/section_cli_glance_commands.xml:206(title) +msgid "glance image-list command" +msgstr "" + +#: ./doc/common/section_cli_glance_commands.xml:255(title) +msgid "glance image-show command" +msgstr "" + +#: ./doc/common/section_cli_glance_commands.xml:269(title) +msgid "glance image-update command" +msgstr "" + +#: ./doc/common/section_cli_glance_commands.xml:332(title) +msgid "glance member-create command" +msgstr "" + +#: ./doc/common/section_cli_glance_commands.xml:347(title) +msgid "glance member-delete command" +msgstr "" + +#: ./doc/common/section_cli_glance_commands.xml:359(title) +msgid "glance member-list command" +msgstr "" + +#: ./doc/common/section_cli_nova_usage_statistics.xml:4(title) +msgid "Show usage statistics for hosts and instances" +msgstr "" + +#: ./doc/common/section_cli_nova_usage_statistics.xml:4(para) +msgid "You can show basic statistics on resource usage for hosts and instances." +msgstr "" + +#: ./doc/common/section_cli_nova_usage_statistics.xml:6(para) +msgid "For more sophisticated monitoring, see the Ceilometer project, which is under development. You can also use tools, such as Ganglia or Graphite, to gather more detailed data." +msgstr "" + +#: ./doc/common/section_cli_nova_usage_statistics.xml:15(title) +msgid "To show host usage statistics" +msgstr "" + +#: ./doc/common/section_cli_nova_usage_statistics.xml:16(para) +msgid "List the hosts and the nova-related services that run on them:" +msgstr "" + +#: ./doc/common/section_cli_nova_usage_statistics.xml:29(para) +msgid "Get a summary of resource usage of all of the instances running on the host." +msgstr "" + +#: ./doc/common/section_cli_nova_usage_statistics.xml:31(replaceable) +msgid "devstack-grizzly" +msgstr "" + +#: ./doc/common/section_cli_nova_usage_statistics.xml:41(para) +msgid "The cpu column shows the sum of the virtual CPUs for instances running on the host." +msgstr "" + +#: ./doc/common/section_cli_nova_usage_statistics.xml:43(para) +msgid "The memory_mb column shows the sum of the memory (in MB) allocated to the instances that run on the hosts." +msgstr "" + +#: ./doc/common/section_cli_nova_usage_statistics.xml:46(para) +msgid "The disk_gb column shows the sum of the root and ephemeral disk sizes (in GB) of the instances that run on the hosts." +msgstr "" + +#: ./doc/common/section_cli_nova_usage_statistics.xml:49(para) +msgid "The used_now row shows the sum of the resources allocated to the instances that run on the host plus the resources allocated to the virtual machine of the host itself." +msgstr "" + +#: ./doc/common/section_cli_nova_usage_statistics.xml:53(para) +msgid "The used_max row shows the sum of the resources allocated to the instances that run on the host." +msgstr "" + +#: ./doc/common/section_cli_nova_usage_statistics.xml:56(para) +msgid "These values are computed by using only information about the flavors of the instances that run on the hosts. This command does not query the CPU usage, memory usage, or hard disk usage of the physical host." +msgstr "" + +#: ./doc/common/section_cli_nova_usage_statistics.xml:62(title) +msgid "To show instance usage statistics" +msgstr "" + +#: ./doc/common/section_cli_nova_usage_statistics.xml:64(para) +msgid "Get CPU, memory, I/O, and network statistics for an instance." +msgstr "" + +#: ./doc/common/section_cli_nova_usage_statistics.xml:66(para) +msgid "First, list instances:" +msgstr "" + +#: ./doc/common/section_cli_nova_usage_statistics.xml:74(para) +msgid "Then, get diagnostic statistics:" +msgstr "" + +#: ./doc/common/section_cli_nova_usage_statistics.xml:96(para) +msgid "Get summary statistics for each tenant:" +msgstr "" + +#: ./doc/common/section_cli_nova_userdata.xml:7(title) +msgid "Provide user data to instances" +msgstr "" + +#: ./doc/common/section_cli_nova_userdata.xml:8(para) +msgid "User data is a special key in the metadata service that holds a file that cloud-aware applications in the guest instance can access. For example the cloudinit system is a Ubuntu open source package that handles early initialization of a cloud instance and that makes use of user data." +msgstr "" + +#: ./doc/common/section_cli_nova_userdata.xml:17(para) +msgid "You can place user data in a local file and pass it through the --user-data <user-data-file> parameter at instance creation:" +msgstr "" + +#. ... Old module003-ch009-replication edited, renamed, and stored in doc/common for use by both Cloud Admin and Operator Training Guides... +#: ./doc/common/section_objectstorage-replication.xml:7(title) ./doc/common/section_objectstorage-components.xml:193(title) +msgid "Replication" +msgstr "" + +#: ./doc/common/section_objectstorage-replication.xml:8(para) +msgid "Because each replica in Object Storage functions independently and clients generally require only a simple majority of nodes to respond to consider an operation successful, transient failures like network partitions can quickly cause replicas to diverge. These differences are eventually reconciled by asynchronous, peer-to-peer replicator processes. The replicator processes traverse their local file systems and concurrently perform operations in a manner that balances load across physical disks." +msgstr "" + +#: ./doc/common/section_objectstorage-replication.xml:17(para) +msgid "Replication uses a push model, with records and files generally only being copied from local to remote replicas. This is important because data on the node might not belong there (as in the case of hand offs and ring changes), and a replicator cannot know which data it should pull in from elsewhere in the cluster. Any node that contains data must ensure that data gets to where it belongs. The ring handles replica placement." +msgstr "" + +#: ./doc/common/section_objectstorage-replication.xml:25(para) +msgid "To replicate deletions in addition to creations, every deleted record or file in the system is marked by a tombstone. The replication process cleans up tombstones after a time period known as the consistency window. This window defines the duration of the replication and how long transient failure can remove a node from the cluster. Tombstone cleanup must be tied to replication to reach replica convergence." +msgstr "" + +#: ./doc/common/section_objectstorage-replication.xml:33(para) +msgid "If a replicator detects that a remote drive has failed, the replicator uses the get_more_nodes interface for the ring to choose an alternate node with which to synchronize. The replicator can maintain desired levels of replication during disk failures, though some replicas might not be in an immediately usable location." +msgstr "" + +#: ./doc/common/section_objectstorage-replication.xml:40(para) +msgid "The replicator does not maintain desired levels of replication when failures such as entire node failures occur; most failures are transient." +msgstr "" + +#: ./doc/common/section_objectstorage-replication.xml:44(para) +msgid "The main replication types are:" +msgstr "" + +#: ./doc/common/section_objectstorage-replication.xml:47(para) +msgid "Database replication. Replicates containers and objects." +msgstr "" + +#: ./doc/common/section_objectstorage-replication.xml:52(para) +msgid "Object replication. Replicates object data." +msgstr "" + +#: ./doc/common/section_objectstorage-replication.xml:57(title) +msgid "Database replication" +msgstr "" + +#: ./doc/common/section_objectstorage-replication.xml:58(para) +msgid "Database replication completes a low-cost hash comparison to determine whether two replicas already match. Normally, this check can quickly verify that most databases in the system are already synchronized. If the hashes differ, the replicator synchronizes the databases by sharing records added since the last synchronization point." +msgstr "" + +#: ./doc/common/section_objectstorage-replication.xml:65(para) +msgid "This synchronization point is a high water mark that notes the last record at which two databases were known to be synchronized, and is stored in each database as a tuple of the remote database ID and record ID. Database IDs are unique across all replicas of the database, and record IDs are monotonically increasing integers. After all new records are pushed to the remote database, the entire synchronization table of the local database is pushed, so the remote database can guarantee that it is synchronized with everything with which the local database was previously synchronized." +msgstr "" + +#: ./doc/common/section_objectstorage-replication.xml:76(para) +msgid "If a replica is missing, the whole local database file is transmitted to the peer by using rsync(1) and is assigned a new unique ID." +msgstr "" + +#: ./doc/common/section_objectstorage-replication.xml:79(para) +msgid "In practice, database replication can process hundreds of databases per concurrency setting per second (up to the number of available CPUs or disks) and is bound by the number of database transactions that must be performed." +msgstr "" + +#: ./doc/common/section_objectstorage-replication.xml:86(title) +msgid "Object replication" +msgstr "" + +#: ./doc/common/section_objectstorage-replication.xml:87(para) +msgid "The initial implementation of object replication performed an rsync to push data from a local partition to all remote servers where it was expected to reside. While this worked at small scale, replication times skyrocketed once directory structures could no longer be held in RAM. This scheme was modified to save a hash of the contents for each suffix directory to a per-partition hashes file. The hash for a suffix directory is no longer valid when the contents of that suffix directory is modified." +msgstr "" + +#: ./doc/common/section_objectstorage-replication.xml:96(para) +msgid "The object replication process reads in hash files and calculates any invalidated hashes. Then, it transmits the hashes to each remote server that should hold the partition, and only suffix directories with differing hashes on the remote server are rsynced. After pushing files to the remote server, the replication process notifies it to recalculate hashes for the rsynced suffix directories." +msgstr "" + +#: ./doc/common/section_objectstorage-replication.xml:104(para) +msgid "The number of uncached directories that object replication must traverse, usually as a result of invalidated suffix directory hashes, impedes performance. To provide acceptable replication speeds, object replication is designed to invalidate around 2 percent of the hash space on a normal node each day." +msgstr "" + +#: ./doc/common/section_cli_nova_reboot.xml:5(title) +msgid "Reboot an instance" +msgstr "" + +#: ./doc/common/section_cli_nova_reboot.xml:6(para) +msgid "You can soft or hard reboot a running instance. A soft reboot attempts a graceful shut down and restart of the instance. A hard reboot power cycles the instance." +msgstr "" + +#: ./doc/common/section_cli_nova_reboot.xml:9(para) +msgid "By default, when you reboot a server, it is a soft reboot." +msgstr "" + +#: ./doc/common/section_cli_nova_reboot.xml:10(replaceable) ./doc/common/section_cli_nova_reboot.xml:12(replaceable) ./doc/common/section_cli_nova_startstop.xml:14(replaceable) ./doc/common/section_cli_nova_startstop.xml:19(replaceable) ./doc/common/section_cli_nova_startstop.xml:36(replaceable) ./doc/common/section_cli_nova_startstop.xml:40(replaceable) +msgid "SERVER" +msgstr "" + +#: ./doc/common/section_cli_nova_reboot.xml:11(para) +msgid "To perform a hard reboot, pass the --hard parameter, as follows:" +msgstr "" + +#. ... Old module003-ch005-the-ring edited, renamed, and stored in doc/common for use by both Cloud Admin and Operator Training Guides... +#: ./doc/common/section_objectstorage-ringbuilder.xml:7(title) +msgid "Ring-builder" +msgstr "" + +#: ./doc/common/section_objectstorage-ringbuilder.xml:8(para) +msgid "Use the swift-ring-builder utility to build and manage rings. This utility assigns partitions to devices and writes an optimized Python structure to a gzipped, serialized file on disk for transmission to the servers. The server processes occasionally check the modification time of the file and reload in-memory copies of the ring structure as needed. If you use a slightly older version of the ring, one of the three replicas for a partition subset will be incorrect because of the way the ring-builder manages changes to the ring. You can work around this issue." +msgstr "" + +#: ./doc/common/section_objectstorage-ringbuilder.xml:18(para) +msgid "The ring-builder also keeps its own builder file with the ring information and additional data required to build future rings. It is very important to keep multiple backup copies of these builder files. One option is to copy the builder files out to every server while copying the ring files themselves. Another is to upload the builder files into the cluster itself. If you lose the builder file, you have to create a new ring from scratch. Nearly all partitions would be assigned to different devices and, therefore, nearly all of the stored data would have to be replicated to new locations. So, recovery from a builder file loss is possible, but data would be unreachable for an extended time." +msgstr "" + +#: ./doc/common/section_objectstorage-ringbuilder.xml:31(title) +msgid "Ring data structure" +msgstr "" + +#: ./doc/common/section_objectstorage-ringbuilder.xml:32(para) +msgid "The ring data structure consists of three top level fields: a list of devices in the cluster, a list of lists of device ids indicating partition to device assignments, and an integer indicating the number of bits to shift an MD5 hash to calculate the partition for the hash." +msgstr "" + +#: ./doc/common/section_objectstorage-ringbuilder.xml:39(title) +msgid "Partition assignment list" +msgstr "" + +#: ./doc/common/section_objectstorage-ringbuilder.xml:40(para) +msgid "This is a list of array(‘H’) of devices ids. The outermost list contains an array(‘H’) for each replica. Each array(‘H’) has a length equal to the partition count for the ring. Each integer in the array(‘H’) is an index into the above list of devices. The partition list is known internally to the Ring class as _replica2part2dev_id." +msgstr "" + +#: ./doc/common/section_objectstorage-ringbuilder.xml:49(para) +msgid "So, to create a list of device dictionaries assigned to a partition, the Python code would look like: " +msgstr "" + +#: ./doc/common/section_objectstorage-ringbuilder.xml:53(para) +msgid "That code is a little simplistic because it does not account for the removal of duplicate devices. If a ring has more replicas than devices, a partition will have more than one replica on a device." +msgstr "" + +#: ./doc/common/section_objectstorage-ringbuilder.xml:57(para) +msgid "array(‘H’) is used for memory conservation as there may be millions of partitions." +msgstr "" + +#: ./doc/common/section_objectstorage-ringbuilder.xml:62(title) +msgid "Replica counts" +msgstr "" + +#: ./doc/common/section_objectstorage-ringbuilder.xml:63(para) +msgid "To support the gradual change in replica counts, a ring can have a real number of replicas and is not restricted to an integer number of replicas." +msgstr "" + +#: ./doc/common/section_objectstorage-ringbuilder.xml:66(para) +msgid "A fractional replica count is for the whole ring and not for individual partitions. It indicates the average number of replicas for each partition. For example, a replica count of 3.2 means that 20 percent of partitions have four replicas and 80 percent have three replicas." +msgstr "" + +#: ./doc/common/section_objectstorage-ringbuilder.xml:71(para) +msgid "The replica count is adjustable." +msgstr "" + +#: ./doc/common/section_objectstorage-ringbuilder.xml:72(para) +msgid "Example:" +msgstr "" + +#: ./doc/common/section_objectstorage-ringbuilder.xml:75(para) +msgid "You must rebalance the replica ring in globally distributed clusters. Operators of these clusters generally want an equal number of replicas and regions. Therefore, when an operator adds or removes a region, the operator adds or removes a replica. Removing unneeded replicas saves on the cost of disks." +msgstr "" + +#: ./doc/common/section_objectstorage-ringbuilder.xml:81(para) +msgid "You can gradually increase the replica count at a rate that does not adversely affect cluster performance." +msgstr "" + +#: ./doc/common/section_objectstorage-ringbuilder.xml:92(para) +msgid "Changes take effect after the ring is rebalanced. Therefore, if you intend to change from 3 replicas to 3.01 but you accidentally type 2.01, no data is lost." +msgstr "" + +#: ./doc/common/section_objectstorage-ringbuilder.xml:97(replaceable) +msgid "X.builder" +msgstr "" + +#: ./doc/common/section_objectstorage-ringbuilder.xml:96(para) +msgid "Additionally, can now take a decimal argument for the number of replicas." +msgstr "" + +#: ./doc/common/section_objectstorage-ringbuilder.xml:102(title) +msgid "Partition shift value" +msgstr "" + +#: ./doc/common/section_objectstorage-ringbuilder.xml:103(para) +msgid "The partition shift value is known internally to the Ring class as _part_shift. This value is used to shift an MD5 hash to calculate the partition where the data for that hash should reside. Only the top four bytes of the hash is used in this process. For example, to compute the partition for the /account/container/object path, the Python code might look like the following code: " +msgstr "" + +#: ./doc/common/section_objectstorage-ringbuilder.xml:114(para) +msgid "For a ring generated with part_power P, the partition shift value is 32 - P." +msgstr "" + +#: ./doc/common/section_objectstorage-ringbuilder.xml:118(title) +msgid "Build the ring" +msgstr "" + +#: ./doc/common/section_objectstorage-ringbuilder.xml:119(para) +msgid "The ring builder process includes these high-level steps:" +msgstr "" + +#: ./doc/common/section_objectstorage-ringbuilder.xml:123(para) +msgid "The utility calculates the number of partitions to assign to each device based on the weight of the device. For example, for a partition at the power of 20, the ring has 1,048,576 partitions. One thousand devices of equal weight will each want 1,048.576 partitions. The devices are sorted by the number of partitions they desire and kept in order throughout the initialization process." +msgstr "" + +#: ./doc/common/section_objectstorage-ringbuilder.xml:133(para) +msgid "Each device is also assigned a random tiebreaker value that is used when two devices desire the same number of partitions. This tiebreaker is not stored on disk anywhere, and so two different rings created with the same parameters will have different partition assignments. For repeatable partition assignments, RingBuilder.rebalance() takes an optional seed value that seeds the Python pseudo-random number generator." +msgstr "" + +#: ./doc/common/section_objectstorage-ringbuilder.xml:147(para) +msgid "The ring builder assigns each partition replica to the device that requires most partitions at that point while keeping it as far away as possible from other replicas. The ring builder prefers to assign a replica to a device in a region that does not already have a replica. If no such region is available, the ring builder searches for a device in a different zone, or on a different server. If it does not find one, it looks for a device with no replicas. Finally, if all options are exhausted, the ring builder assigns the replica to the device that has the fewest replicas already assigned." +msgstr "" + +#: ./doc/common/section_objectstorage-ringbuilder.xml:161(para) +msgid "The ring builder assigns multiple replicas to one device only if the ring has fewer devices than it has replicas." +msgstr "" + +#: ./doc/common/section_objectstorage-ringbuilder.xml:167(para) +msgid "When building a new ring from an old ring, the ring builder recalculates the desired number of partitions that each device wants." +msgstr "" + +#: ./doc/common/section_objectstorage-ringbuilder.xml:176(para) +msgid "The ring builder unassigns any assigned partitions from any removed devices and adds these partitions to the gathered list." +msgstr "" + +#: ./doc/common/section_objectstorage-ringbuilder.xml:182(para) +msgid "The ring builder unassigns any partition replicas that can be spread out for better durability and adds these partitions to the gathered list." +msgstr "" + +#: ./doc/common/section_objectstorage-ringbuilder.xml:189(para) +msgid "The ring builder unassigns random partitions from any devices that have more partitions than they need and adds these partitions to the gathered list." +msgstr "" + +#: ./doc/common/section_objectstorage-ringbuilder.xml:172(para) +msgid "The ring builder unassigns partitions and gathers these partitions for reassignment, as follows: " +msgstr "" + +#: ./doc/common/section_objectstorage-ringbuilder.xml:199(para) +msgid "The ring builder reassigns the gathered partitions to devices by using a similar method to the one described previously." +msgstr "" + +#: ./doc/common/section_objectstorage-ringbuilder.xml:204(para) +msgid "When the ring builder reassigns a replica to a partition, the ring builder records the time of the reassignment. The ring builder uses this value when it gathers partitions for reassignment so that no partition is moved twice in a configurable amount of time. The RingBuilder class knows this configurable amount of time as min_part_hours. The ring builder ignores this restriction for replicas of partitions on removed devices because removal of a device happens on device failure only, and reassignment is the only choice." +msgstr "" + +#: ./doc/common/section_objectstorage-ringbuilder.xml:218(para) +msgid "Theses steps do not always perfectly rebalance a ring due to the random nature of gathering partitions for reassignment. To help reach a more balanced ring, the rebalance process is repeated until near perfect (less than 1 percent off) or when the balance does not improve by at least 1 percent (indicating we probably cannot get perfect balance due to wildly imbalanced zones or too many partitions recently moved)." +msgstr "" + +#. ... Old module003-ch008-account-reaper edited, renamed, and stored in doc/common for use by both Cloud Admin and Operator Training Guides... +#: ./doc/common/section_objectstorage-account-reaper.xml:8(title) +msgid "Account reaper" +msgstr "" + +#: ./doc/common/section_objectstorage-account-reaper.xml:9(para) +msgid "In the background, the account reaper removes data from the deleted accounts." +msgstr "" + +#: ./doc/common/section_objectstorage-account-reaper.xml:10(para) +msgid "A reseller marks an account for deletion by issuing a DELETE request on the account’s storage URL. This action sets the status column of the account_stat table in the account database and replicas to DELETED, marking the account's data for deletion." +msgstr "" + +#: ./doc/common/section_objectstorage-account-reaper.xml:18(para) +msgid "It's on the developers' to-do list to write a utility that performs this task, preferably through a ReST call." +msgstr "" + +#: ./doc/common/section_objectstorage-account-reaper.xml:13(para) +msgid "Typically, a specific retention time or undelete are not provided. However, you can set a delay_reaping value in the [account-reaper] section of the account-server.conf to delay the actual deletion of data. At this time, to undelete you have to update the account database replicas directly, setting the status column to an empty string and updating the put_timestamp to be greater than the delete_timestamp. " +msgstr "" + +#: ./doc/common/section_objectstorage-account-reaper.xml:21(para) +msgid "The account reaper runs on each account server and scans the server occasionally for account databases marked for deletion. It only fires up on the accounts for which the server is the primary node, so that multiple account servers aren’t trying to do it simultaneously. Using multiple servers to delete one account might improve the deletion speed but requires coordination to avoid duplication. Speed really is not a big concern with data deletion, and large accounts aren’t deleted often." +msgstr "" + +#: ./doc/common/section_objectstorage-account-reaper.xml:27(para) +msgid "Deleting an account is simple. For each account container, all objects are deleted and then the container is deleted. Deletion requests that fail will not stop the overall process but will cause the overall process to fail eventually (for example, if an object delete times out, you will not be able to delete the container or the account). The account reaper keeps trying to delete an account until it is empty, at which point the database reclaim process within the db_replicator will remove the database files." +msgstr "" + +#: ./doc/common/section_objectstorage-account-reaper.xml:33(para) +msgid "A persistent error state may prevent the deletion of an object or container. If this happens, you will see a message such as “Account <name> has not been reaped since <date>” in the log. You can control when this is logged with the reap_warn_after value in the [account-reaper] section of the account-server.conf file. The default value is 30 days." +msgstr "" + +#: ./doc/common/section_support-compute.xml:6(title) +msgid "Troubleshoot Compute" +msgstr "" + +#: ./doc/common/section_support-compute.xml:7(para) +msgid "Common problems for Compute typically involve misconfigured networking or credentials that are not sourced properly in the environment. Also, most flat networking configurations do not enable or from a compute node to the instances that run on that node. Another common problem is trying to run 32-bit images on a 64-bit compute node. This section shows you how to troubleshoot Compute." +msgstr "" + +#: ./doc/common/section_support-compute.xml:16(title) +msgid "Compute log files" +msgstr "" + +#: ./doc/common/section_support-compute.xml:17(para) +msgid "Compute stores a log file for each service in /var/log/nova. For example, nova-compute.log is the log for the nova-compute service. You can set the following options to format log strings for the nova.log module in the nova.conf file:" +msgstr "" + +#: ./doc/common/section_support-compute.xml:26(literal) +msgid "logging_context_format_string" +msgstr "" + +#: ./doc/common/section_support-compute.xml:29(literal) +msgid "logging_default_format_string" +msgstr "" + +#: ./doc/common/section_support-compute.xml:32(para) +msgid "If the log level is set to debug, you can also specify logging_debug_format_suffix to append extra formatting. For information about what variables are available for the formatter see: http://docs.python.org/library/logging.html#formatter." +msgstr "" + +#: ./doc/common/section_support-compute.xml:39(para) +msgid "You have two options for logging for OpenStack Compute based on configuration settings. In nova.conf, include the logfile option to enable logging. Alternatively you can set use_syslog=1 so that the nova daemon logs to syslog." +msgstr "" + +#: ./doc/common/section_support-compute.xml:47(title) +msgid "Common errors and fixes for Compute" +msgstr "" + +#: ./doc/common/section_support-compute.xml:48(para) +msgid "The ask.openstack.org site offers a place to ask and answer questions, and you can also mark questions as frequently asked questions. This section describes some errors people have posted previously. Bugs are constantly being fixed, so online resources are a great way to get the most up-to-date errors and fixes." +msgstr "" + +#: ./doc/common/section_support-compute.xml:56(title) +msgid "Credential errors, 401, and 403 forbidden errors" +msgstr "" + +#: ./doc/common/section_support-compute.xml:63(para) +msgid "Manual method. Get get the novarc file from the project ZIP file, save existing credentials in case of override. and manually source the novarc file." +msgstr "" + +#: ./doc/common/section_support-compute.xml:73(para) +msgid "Script method. Generates novarc from the project ZIP file and sources it for you." +msgstr "" + +#: ./doc/common/section_support-compute.xml:58(para) +msgid "Missing credentials cause a 403forbidden error. To resolve this issue, use one of these methods:" +msgstr "" + +#: ./doc/common/section_support-compute.xml:80(para) +msgid "When you run nova-api the first time, it generates the certificate authority information, including openssl.cnf. If you start the CA services before this, you might not be able to create your ZIP file. Restart the services. When your CA information is available, create your ZIP file." +msgstr "" + +#: ./doc/common/section_support-compute.xml:88(para) +msgid "Also, check your HTTP proxy settings to see whether they cause problems with novarc creation." +msgstr "" + +#: ./doc/common/section_support-compute.xml:93(title) +msgid "Instance errors" +msgstr "" + +#: ./doc/common/section_support-compute.xml:94(para) +msgid "Sometimes a particular instance shows pending or you cannot SSH to it. Sometimes the image itself is the problem. For example, when you use flat manager networking, you do not have a DHCP server and certain images do not support interface injection; you cannot connect to them. The fix for this problem is to use an image that does support this method, such as Ubuntu, which obtains an IP address correctly with FlatManager network settings." +msgstr "" + +#: ./doc/common/section_support-compute.xml:104(para) +msgid "To troubleshoot other possible problems with an instance, such as an instance that stays in a spawning state, check the directory for the particular instance under /var/lib/nova/instances on the nova-compute host and make sure that these files are present:" +msgstr "" + +#: ./doc/common/section_support-compute.xml:113(filename) +msgid "libvirt.xml" +msgstr "" + +#: ./doc/common/section_support-compute.xml:116(filename) +msgid "disk" +msgstr "" + +#: ./doc/common/section_support-compute.xml:119(filename) +msgid "disk-raw" +msgstr "" + +#: ./doc/common/section_support-compute.xml:122(filename) +msgid "kernel" +msgstr "" + +#: ./doc/common/section_support-compute.xml:125(filename) +msgid "ramdisk" +msgstr "" + +#: ./doc/common/section_support-compute.xml:128(para) +msgid "After the instance starts, console.log" +msgstr "" + +#: ./doc/common/section_support-compute.xml:132(para) +msgid "If any files are missing, empty, or very small, the nova-compute service did not successfully download the images from the Image Service." +msgstr "" + +#: ./doc/common/section_support-compute.xml:137(para) +msgid "Also check nova-compute.log for exceptions. Sometimes they do not appear in the console output." +msgstr "" + +#: ./doc/common/section_support-compute.xml:140(para) +msgid "Next, check the log file for the instance in the /var/log/libvirt/qemu directory to see if it exists and has any useful error messages in it." +msgstr "" + +#: ./doc/common/section_support-compute.xml:144(para) +msgid "Finally, from the /var/lib/nova/instances directory for the instance, see if this command returns an error:" +msgstr "" + +#: ./doc/common/section_support-compute.xml:152(title) +msgid "Reset the state of an instance" +msgstr "" + +#: ./doc/common/section_support-compute.xml:153(para) +msgid "If an instance remains in an intermediate state, such as deleting, you can use the command to manually reset the state of an instance to an error state. You can then delete the instance. For example:" +msgstr "" + +#: ./doc/common/section_support-compute.xml:160(para) +msgid "You can also use the --active parameter to force the instance back to an active state instead of an error state. For example:" +msgstr "" + +#: ./doc/common/section_support-compute.xml:166(title) +msgid "Injection problems" +msgstr "" + +#: ./doc/common/section_support-compute.xml:167(para) +msgid "If instances do not boot or boot slowly, investigate file injection as a cause." +msgstr "" + +#: ./doc/common/section_support-compute.xml:169(para) +msgid "To disable injection in libvirt, set to -2." +msgstr "" + +#: ./doc/common/section_support-compute.xml:173(para) +msgid "If you have not enabled the configuration drive and you want to make user-specified files available from the metadata server for to improve performance and avoid boot failure if injection fails, you must disable injection." +msgstr "" + +#: ./doc/common/section_keystone-sample-conf-files.xml:6(title) +msgid "Identity Service sample configuration files" +msgstr "" + +#: ./doc/common/section_keystone-sample-conf-files.xml:10(filename) +msgid "etc/keystone.conf.sample" +msgstr "" + +#: ./doc/common/section_keystone-sample-conf-files.xml:17(filename) +msgid "etc/keystone-paste.ini" +msgstr "" + +#: ./doc/common/section_keystone-sample-conf-files.xml:24(literal) +msgid "etc/logging.conf.sample" +msgstr "" + +#: ./doc/common/section_identity-configure.xml:6(title) +msgid "Identity Service configuration files" +msgstr "" + +#: ./doc/common/section_identity-configure.xml:9(term) +msgid "keystone.conf" +msgstr "" + +#: ./doc/common/section_identity-configure.xml:11(para) +msgid "The Identity Service /etc/keystone/keystone.conf configuration file is an INI-format file with sections." +msgstr "" + +#: ./doc/common/section_identity-configure.xml:15(para) +msgid "The [DEFAULT] section configures general configuration values." +msgstr "" + +#: ./doc/common/section_identity-configure.xml:17(para) +msgid "Specific sections, such as the [sql] and [ec2] sections, configure individual services." +msgstr "" + +#: ./doc/common/section_identity-configure.xml:21(caption) +msgid "keystone.conf file sections" +msgstr "" + +#: ./doc/common/section_identity-configure.xml:26(td) +msgid "Section" +msgstr "" + +#: ./doc/common/section_identity-configure.xml:32(literal) ./doc/common/tables/glance-policy.xml:19(th) ./doc/common/tables/nova-ipv6.xml:19(th) ./doc/common/tables/cinder-eqlx.xml:19(th) ./doc/common/tables/glance-qpid.xml:19(th) ./doc/common/tables/swift-container-server-DEFAULT.xml:7(literal) ./doc/common/tables/nova-volumes.xml:19(th) ./doc/common/tables/glance-gridfs.xml:19(th) ./doc/common/tables/glance-filesystem.xml:19(th) ./doc/common/tables/cinder-storage_gpfs.xml:19(th) ./doc/common/tables/cinder-nexenta_iscsi.xml:19(th) ./doc/common/tables/nova-ca.xml:19(th) ./doc/common/tables/cinder-huawei.xml:19(th) ./doc/common/tables/nova-glance.xml:19(th) ./doc/common/tables/nova-neutron.xml:19(th) ./doc/common/tables/cinder-backups_ceph.xml:19(th) ./doc/common/tables/nova-metadata.xml:19(th) ./doc/common/tables/glance-s3.xml:19(th) ./doc/common/tables/cinder-block-device.xml:19(th) ./doc/common/tables/cinder-zones.xml:19(th) ./doc/common/tables/cinder-netapp_7mode_iscsi.xml:19(th) ./doc/common/tables/cinder-compute.xml:19(th) ./doc/common/tables/cinder-lvm.xml:19(th) ./doc/common/tables/cinder-storage_nfs.xml:19(th) ./doc/common/tables/nova-hypervisor.xml:19(th) ./doc/common/tables/cinder-quota.xml:19(th) ./doc/common/tables/swift-object-expirer-DEFAULT.xml:7(literal) ./doc/common/tables/nova-console.xml:19(th) ./doc/common/tables/nova-common.xml:19(th) ./doc/common/tables/glance-zmq.xml:19(th) ./doc/common/tables/nova-testing.xml:19(th) ./doc/common/tables/cinder-backups.xml:19(th) ./doc/common/tables/nova-s3.xml:19(th) ./doc/common/tables/cinder-rpc.xml:19(th) ./doc/common/tables/cinder-api.xml:19(th) ./doc/common/tables/cinder-windows.xml:19(th) ./doc/common/tables/cinder-san.xml:19(th) ./doc/common/tables/nova-db.xml:19(th) ./doc/common/tables/glance-logging.xml:19(th) ./doc/common/tables/glance-wsgi.xml:19(th) ./doc/common/tables/nova-periodic.xml:19(th) ./doc/common/tables/cinder-images.xml:19(th) ./doc/common/tables/glance-rbd.xml:19(th) ./doc/common/tables/cinder-hp3par.xml:19(th) ./doc/common/tables/cinder-storage_ceph.xml:19(th) ./doc/common/tables/nova-livemigration.xml:19(th) ./doc/common/tables/nova-ldap.xml:19(th) ./doc/common/tables/nova-fping.xml:19(th) ./doc/common/tables/cinder-netapp_cdot_iscsi.xml:19(th) ./doc/common/tables/nova-ec2.xml:19(th) ./doc/common/tables/swift-object-server-DEFAULT.xml:7(literal) ./doc/common/tables/cinder-nexenta_nfs.xml:19(th) ./doc/common/tables/nova-policy.xml:19(th) ./doc/common/tables/glance-rpc.xml:19(th) ./doc/common/tables/nova-authentication.xml:19(th) ./doc/common/tables/cinder-vmware.xml:19(th) ./doc/common/tables/glance-sheepdog.xml:19(th) ./doc/common/tables/glance-swift.xml:19(th) ./doc/common/tables/swift-account-server-DEFAULT.xml:7(literal) ./doc/common/tables/nova-libvirt.xml:19(th) ./doc/common/tables/cinder-backups_swift.xml:19(th) ./doc/common/tables/nova-pci.xml:19(th) ./doc/common/tables/glance-imagecache.xml:19(th) ./doc/common/tables/cinder-storage.xml:19(th) ./doc/common/tables/nova-vpn.xml:19(th) ./doc/common/tables/nova-wsgi.xml:19(th) ./doc/common/tables/cinder-storage_glusterfs.xml:19(th) ./doc/common/tables/nova-availabilityzones.xml:19(th) ./doc/common/tables/nova-vnc.xml:19(th) ./doc/common/tables/cinder-coraid.xml:19(th) ./doc/common/tables/nova-logging.xml:19(th) ./doc/common/tables/nova-xen.xml:19(th) ./doc/common/tables/cinder-netapp_7mode_nfs.xml:19(th) ./doc/common/tables/glance-common.xml:19(th) ./doc/common/tables/nova-network.xml:19(th) ./doc/common/tables/cinder-scality.xml:19(th) ./doc/common/tables/cinder-common.xml:19(th) ./doc/common/tables/nova-configdrive.xml:19(th) ./doc/common/tables/cinder-database.xml:19(th) ./doc/common/tables/nova-zeromq.xml:19(th) ./doc/common/tables/glance-testing.xml:19(th) ./doc/common/tables/glance-registry.xml:19(th) ./doc/common/tables/glance-rabbitmq.xml:19(th) ./doc/common/tables/cinder-backups_tsm.xml:19(th) ./doc/common/tables/nova-qpid.xml:19(th) ./doc/common/tables/cinder-log.xml:19(th) ./doc/common/tables/swift-proxy-server-DEFAULT.xml:7(literal) ./doc/common/tables/nova-scheduling.xml:19(th) ./doc/common/tables/cinder-xiv.xml:19(th) ./doc/common/tables/cinder-auth.xml:19(th) ./doc/common/tables/nova-kombu.xml:19(th) ./doc/common/tables/cinder-hds.xml:19(th) ./doc/common/tables/cinder-storwize.xml:19(th) ./doc/common/tables/cinder-solidfire.xml:19(th) ./doc/common/tables/glance-ssl.xml:19(th) ./doc/common/tables/glance-db.xml:19(th) ./doc/common/tables/nova-api.xml:19(th) ./doc/common/tables/cinder-san-solaris.xml:19(th) ./doc/common/tables/cinder-netapp_cdot_nfs.xml:19(th) ./doc/common/tables/nova-rpc.xml:19(th) ./doc/common/tables/glance-api.xml:19(th) ./doc/common/tables/cinder-scheduler.xml:19(th) ./doc/common/tables/glance-cinder.xml:19(th) ./doc/common/tables/nova-rabbitmq.xml:19(th) ./doc/common/tables/cinder-zadara.xml:19(th) ./doc/common/tables/nova-quota.xml:19(th) ./doc/common/tables/nova-conductor.xml:19(th) ./doc/common/tables/nova-compute.xml:19(th) ./doc/common/tables/cinder-storage_xen.xml:19(th) ./doc/common/tables/nova-xvpnvncproxy.xml:19(th) +msgid "[DEFAULT]" +msgstr "" + +#: ./doc/common/section_identity-configure.xml:33(td) +msgid "General configuration." +msgstr "" + +#: ./doc/common/section_identity-configure.xml:36(literal) +msgid "[sql]" +msgstr "" + +#: ./doc/common/section_identity-configure.xml:37(td) +msgid "Optional storage back-end configuration." +msgstr "" + +#: ./doc/common/section_identity-configure.xml:40(literal) +msgid "[ec2]" +msgstr "" + +#: ./doc/common/section_identity-configure.xml:41(td) +msgid "Amazon EC2 authentication driver configuration." +msgstr "" + +#: ./doc/common/section_identity-configure.xml:44(literal) +msgid "[s3]" +msgstr "" + +#: ./doc/common/section_identity-configure.xml:45(td) +msgid "Amazon S3 authentication driver configuration." +msgstr "" + +#: ./doc/common/section_identity-configure.xml:48(literal) +msgid "[identity]" +msgstr "" + +#: ./doc/common/section_identity-configure.xml:49(td) +msgid "Identity Service system driver configuration." +msgstr "" + +#: ./doc/common/section_identity-configure.xml:52(literal) +msgid "[catalog]" +msgstr "" + +#: ./doc/common/section_identity-configure.xml:53(td) +msgid "Service catalog driver configuration." +msgstr "" + +#: ./doc/common/section_identity-configure.xml:56(literal) +msgid "[token]" +msgstr "" + +#: ./doc/common/section_identity-configure.xml:57(td) +msgid "Token driver configuration." +msgstr "" + +#: ./doc/common/section_identity-configure.xml:60(literal) +msgid "[policy]" +msgstr "" + +#: ./doc/common/section_identity-configure.xml:61(td) +msgid "Policy system driver configuration for RBAC." +msgstr "" + +#: ./doc/common/section_identity-configure.xml:64(literal) +msgid "[signing]" +msgstr "" + +#: ./doc/common/section_identity-configure.xml:65(td) +msgid "Cryptographic signatures for PKI based tokens." +msgstr "" + +#: ./doc/common/section_identity-configure.xml:68(literal) ./doc/common/tables/nova-ca.xml:62(th) +msgid "[ssl]" +msgstr "" + +#: ./doc/common/section_identity-configure.xml:69(td) +msgid "SSL configuration." +msgstr "" + +#: ./doc/common/section_identity-configure.xml:73(para) +msgid "When you start the Identity Service, you can use the --config-file parameter to specify a configuration file." +msgstr "" + +#: ./doc/common/section_identity-configure.xml:76(para) +msgid "If you do not specify a configuration file, the Identity Service looks for the keystone.conf configuration file in these directories in this order:" +msgstr "" + +#: ./doc/common/section_identity-configure.xml:83(literal) +msgid "~/.keystone" +msgstr "" + +#: ./doc/common/section_identity-configure.xml:88(literal) +msgid "~/" +msgstr "" + +#: ./doc/common/section_identity-configure.xml:93(literal) +msgid "/etc/keystone" +msgstr "" + +#: ./doc/common/section_identity-configure.xml:98(literal) +msgid "/etc" +msgstr "" + +#: ./doc/common/section_identity-configure.xml:105(term) +msgid "keystone-paste.ini" +msgstr "" + +#: ./doc/common/section_identity-configure.xml:107(para) +msgid "The /etc/keystone/keystone-paste.ini file configures the Identity Service WSGI middleware pipeline." +msgstr "" + +#: ./doc/common/section_keystone-ssl-config.xml:7(title) +msgid "Configure the Identity Service with SSL" +msgstr "" + +#: ./doc/common/section_keystone-ssl-config.xml:8(para) +msgid "You can configure the Identity Service to support two-way SSL." +msgstr "" + +#: ./doc/common/section_keystone-ssl-config.xml:10(para) +msgid "You must obtain the x509 certificates externally and configure them." +msgstr "" + +#: ./doc/common/section_keystone-ssl-config.xml:12(para) +msgid "The Identity Service provides a set of sample certificates in the examples/pki/certs and examples/pki/private directories:" +msgstr "" + +#: ./doc/common/section_keystone-ssl-config.xml:18(title) +msgid "Certificate types" +msgstr "" + +#: ./doc/common/section_keystone-ssl-config.xml:20(term) +msgid "cacert.pem" +msgstr "" + +#: ./doc/common/section_keystone-ssl-config.xml:22(para) +msgid "Certificate Authority chain to validate against." +msgstr "" + +#: ./doc/common/section_keystone-ssl-config.xml:27(term) +msgid "ssl_cert.pem" +msgstr "" + +#: ./doc/common/section_keystone-ssl-config.xml:29(para) +msgid "Public certificate for Identity Service server." +msgstr "" + +#: ./doc/common/section_keystone-ssl-config.xml:34(term) +msgid "middleware.pem" +msgstr "" + +#: ./doc/common/section_keystone-ssl-config.xml:36(para) +msgid "Public and private certificate for Identity Service middleware/client." +msgstr "" + +#: ./doc/common/section_keystone-ssl-config.xml:41(term) +msgid "cakey.pem" +msgstr "" + +#: ./doc/common/section_keystone-ssl-config.xml:43(para) +msgid "Private key for the CA." +msgstr "" + +#: ./doc/common/section_keystone-ssl-config.xml:47(term) +msgid "ssl_key.pem" +msgstr "" + +#: ./doc/common/section_keystone-ssl-config.xml:49(para) +msgid "Private key for the Identity Service server." +msgstr "" + +#: ./doc/common/section_keystone-ssl-config.xml:55(para) +msgid "You can choose names for these certificates. You can also combine the public/private keys in the same file, if you wish. These certificates are provided as an example." +msgstr "" + +#: ./doc/common/section_keystone-ssl-config.xml:61(title) +msgid "SSL configuration" +msgstr "" + +#: ./doc/common/section_keystone-ssl-config.xml:62(para) +msgid "To enable SSL with client authentication, modify the [ssl] section in the etc/keystone.conf file. The following SSL configuration example uses the included sample certificates:" +msgstr "" + +#: ./doc/common/section_keystone-ssl-config.xml:74(title) +msgid "Options" +msgstr "" + +#: ./doc/common/section_keystone-ssl-config.xml:76(para) +msgid "enable. True enables SSL. Default is False." +msgstr "" + +#: ./doc/common/section_keystone-ssl-config.xml:80(para) +msgid "certfile. Path to the Identity Service public certificate file." +msgstr "" + +#: ./doc/common/section_keystone-ssl-config.xml:84(para) +msgid "keyfile. Path to the Identity Service private certificate file. If you include the private key in the certfile, you can omit the keyfile." +msgstr "" + +#: ./doc/common/section_keystone-ssl-config.xml:90(para) +msgid "ca_certs. Path to the CA trust chain." +msgstr "" + +#: ./doc/common/section_keystone-ssl-config.xml:94(para) +msgid "cert_required. Requires client certificate. Default is False." +msgstr "" + +#: ./doc/common/section_cli_nova_startstop.xml:6(title) +msgid "Stop and start an instance" +msgstr "" + +#: ./doc/common/section_cli_nova_startstop.xml:7(para) +msgid "Use one of the following methods to stop and start an instance." +msgstr "" + +#: ./doc/common/section_cli_nova_startstop.xml:10(title) +msgid "Pause and un-pause an instance" +msgstr "" + +#: ./doc/common/section_cli_nova_startstop.xml:13(para) +msgid "To pause a server, run the following command:" +msgstr "" + +#: ./doc/common/section_cli_nova_startstop.xml:15(para) +msgid "This command stores the state of the VM in RAM. A paused instance continues to run in a frozen state." +msgstr "" + +#: ./doc/common/section_cli_nova_startstop.xml:17(para) +msgid "To un-pause the server, run the following command:" +msgstr "" + +#: ./doc/common/section_cli_nova_startstop.xml:24(title) +msgid "Suspend and resume an instance" +msgstr "" + +#: ./doc/common/section_cli_nova_startstop.xml:26(para) +msgid "Administrative users might want to suspend an infrequently used instance or to perform system maintenance." +msgstr "" + +#: ./doc/common/section_cli_nova_startstop.xml:29(para) +msgid "When you suspend an instance, its VM state is stored on disk, all memory is written to disk, and the virtual machine is stopped. Suspending an instance is similar to placing a device in hibernation; memory and vCPUs become available." +msgstr "" + +#: ./doc/common/section_cli_nova_startstop.xml:34(para) +msgid "To initiate a hypervisor-level suspend operation, run the following command:" +msgstr "" + +#: ./doc/common/section_cli_nova_startstop.xml:39(para) +msgid "To resume a suspended server:" +msgstr "" + +#. When image changes, this message will be marked fuzzy or untranslated for you. +#. It doesn't matter what you translate it to: it's not used at all. +#: ./doc/common/section_objectstorage-components.xml:44(None) +msgid "@@image: '../common/figures/objectstorage-buildingblocks.png'; md5=ed79466c8464513dbeaf1e0954280e5e" +msgstr "" + +#. When image changes, this message will be marked fuzzy or untranslated for you. +#. It doesn't matter what you translate it to: it's not used at all. +#: ./doc/common/section_objectstorage-components.xml:87(None) +msgid "@@image: '../common/figures/objectstorage-ring.png'; md5=a94e26734cec6980c3684d9e824eac2d" +msgstr "" + +#. When image changes, this message will be marked fuzzy or untranslated for you. +#. It doesn't matter what you translate it to: it's not used at all. +#: ./doc/common/section_objectstorage-components.xml:127(None) +msgid "@@image: '../common/figures/objectstorage-zones.png'; md5=1b1dc0abe6ea0c516f22ce399deb75ed" +msgstr "" + +#. When image changes, this message will be marked fuzzy or untranslated for you. +#. It doesn't matter what you translate it to: it's not used at all. +#: ./doc/common/section_objectstorage-components.xml:145(None) +msgid "@@image: '../common/figures/objectstorage-accountscontainers.png'; md5=4b15e5a202db5bde53c9b369058aeab8" +msgstr "" + +#. When image changes, this message will be marked fuzzy or untranslated for you. +#. It doesn't matter what you translate it to: it's not used at all. +#: ./doc/common/section_objectstorage-components.xml:170(None) +msgid "@@image: '../common/figures/objectstorage-partitions.png'; md5=2c161c2e92d6fefc8140ec86e79e9492" +msgstr "" + +#. When image changes, this message will be marked fuzzy or untranslated for you. +#. It doesn't matter what you translate it to: it's not used at all. +#: ./doc/common/section_objectstorage-components.xml:196(None) +msgid "@@image: '../common/figures/objectstorage-replication.png'; md5=9d55594d7f445764569ab04d8d4373b2" +msgstr "" + +#. When image changes, this message will be marked fuzzy or untranslated for you. +#. It doesn't matter what you translate it to: it's not used at all. +#: ./doc/common/section_objectstorage-components.xml:223(None) +msgid "@@image: '../common/figures/objectstorage-usecase.png'; md5=07480e7175b383171173775fb96d70d7" +msgstr "" + +#. ... Old module003-ch004-swift-building-blocks edited, renamed, and stored in doc/common for use by both Cloud Admin and Operator Training Guides... +#: ./doc/common/section_objectstorage-components.xml:8(title) +msgid "Components" +msgstr "" + +#: ./doc/common/section_objectstorage-components.xml:9(para) +msgid "The components that enable Object Storage to deliver high availability, high durability, and high concurrency are:" +msgstr "" + +#: ./doc/common/section_objectstorage-components.xml:13(para) +msgid "Proxy servers—Handle all of the incoming API requests." +msgstr "" + +#: ./doc/common/section_objectstorage-components.xml:17(para) +msgid "Rings—Map logical names of data to locations on particular disks." +msgstr "" + +#: ./doc/common/section_objectstorage-components.xml:21(para) +msgid "Zones—Isolate data from other zones. A failure in one zone doesn’t impact the rest of the cluster because data is replicated across zones." +msgstr "" + +#: ./doc/common/section_objectstorage-components.xml:26(para) +msgid "Accounts and containers—Each account and container are individual databases that are distributed across the cluster. An account database contains the list of containers in that account. A container database contains the list of objects in that container." +msgstr "" + +#: ./doc/common/section_objectstorage-components.xml:32(para) +msgid "Objects—The data itself." +msgstr "" + +#: ./doc/common/section_objectstorage-components.xml:35(para) +msgid "Partitions—A partition stores objects, account databases, and container databases and helps manage locations where data lives in the cluster." +msgstr "" + +#: ./doc/common/section_objectstorage-components.xml:41(title) +msgid "Object Storage building blocks" +msgstr "" + +#: ./doc/common/section_objectstorage-components.xml:49(title) +msgid "Proxy servers" +msgstr "" + +#: ./doc/common/section_objectstorage-components.xml:50(para) +msgid "Proxy servers are the public face of Object Storage and handle all of the incoming API requests. Once a proxy server receives a request, it determines the storage node based on the object's URL, for example, https://swift.example.com/v1/account/container/object. Proxy servers also coordinate responses, handle failures, and coordinate timestamps." +msgstr "" + +#: ./doc/common/section_objectstorage-components.xml:55(para) +msgid "Proxy servers use a shared-nothing architecture and can be scaled as needed based on projected workloads. A minimum of two proxy servers should be deployed for redundancy. If one proxy server fails, the others take over." +msgstr "" + +#: ./doc/common/section_objectstorage-components.xml:60(title) +msgid "Rings" +msgstr "" + +#: ./doc/common/section_objectstorage-components.xml:61(para) +msgid "A ring represents a mapping between the names of entities stored on disk and their physical locations. There are separate rings for accounts, containers, and objects. When other components need to perform any operation on an object, container, or account, they need to interact with the appropriate ring to determine their location in the cluster." +msgstr "" + +#: ./doc/common/section_objectstorage-components.xml:66(para) +msgid "The ring maintains this mapping using zones, devices, partitions, and replicas. Each partition in the ring is replicated, by default, three times across the cluster, and partition locations are stored in the mapping maintained by the ring. The ring is also responsible for determining which devices are used for handoff in failure scenarios." +msgstr "" + +#: ./doc/common/section_objectstorage-components.xml:71(para) +msgid "Data can be isolated into zones in the ring. Each partition replica is guaranteed to reside in a different zone. A zone could represent a drive, a server, a cabinet, a switch, or even a data center." +msgstr "" + +#: ./doc/common/section_objectstorage-components.xml:74(para) +msgid "The partitions of the ring are equally divided among all of the devices in the Object Storage installation. When partitions need to be moved around (for example, if a device is added to the cluster), the ring ensures that a minimum number of partitions are moved at a time, and only one replica of a partition is moved at a time." +msgstr "" + +#: ./doc/common/section_objectstorage-components.xml:78(para) +msgid "Weights can be used to balance the distribution of partitions on drives across the cluster. This can be useful, for example, when differently sized drives are used in a cluster." +msgstr "" + +#: ./doc/common/section_objectstorage-components.xml:81(para) +msgid "The ring is used by the proxy server and several background processes (like replication)." +msgstr "" + +#: ./doc/common/section_objectstorage-components.xml:84(title) +msgid "The ring" +msgstr "" + +#: ./doc/common/section_objectstorage-components.xml:91(para) +msgid "These rings are externally managed, in that the server processes themselves do not modify the rings, they are instead given new rings modified by other tools." +msgstr "" + +#: ./doc/common/section_objectstorage-components.xml:93(para) +msgid "The ring uses a configurable number of bits from a path’s MD5 hash as a partition index that designates a device. The number of bits kept from the hash is known as the partition power, and 2 to the partition power indicates the partition count. Partitioning the full MD5 hash ring allows other parts of the cluster to work in batches of items at once which ends up either more efficient or at least less complex than working with each item separately or the entire cluster all at once." +msgstr "" + +#: ./doc/common/section_objectstorage-components.xml:102(para) +msgid "Another configurable value is the replica count, which indicates how many of the partition-device assignments make up a single ring. For a given partition number, each replica’s device will not be in the same zone as any other replica's device. Zones can be used to group devices based on physical locations, power separations, network separations, or any other attribute that would improve the availability of multiple replicas at the same time." +msgstr "" + +#: ./doc/common/section_objectstorage-components.xml:110(title) ./doc/common/section_objectstorage-components.xml:124(title) +msgid "Zones" +msgstr "" + +#: ./doc/common/section_objectstorage-components.xml:111(para) +msgid "Object Storage allows configuring zones in order to isolate failure boundaries. Each data replica resides in a separate zone, if possible. At the smallest level, a zone could be a single drive or a grouping of a few drives. If there were five object storage servers, then each server would represent its own zone. Larger deployments would have an entire rack (or multiple racks) of object servers, each representing a zone. The goal of zones is to allow the cluster to tolerate significant outages of storage servers without losing all replicas of the data." +msgstr "" + +#: ./doc/common/section_objectstorage-components.xml:118(para) +msgid "As mentioned earlier, everything in Object Storage is stored, by default, three times. Swift will place each replica \"as-uniquely-as-possible\" to ensure both high availability and high durability. This means that when chosing a replica location, Object Storage chooses a server in an unused zone before an unused server in a zone that already has a replica of the data." +msgstr "" + +#: ./doc/common/section_objectstorage-components.xml:131(para) +msgid "When a disk fails, replica data is automatically distributed to the other zones to ensure there are three copies of the data." +msgstr "" + +#: ./doc/common/section_objectstorage-components.xml:135(title) ./doc/common/section_objectstorage-components.xml:142(title) +msgid "Accounts and containers" +msgstr "" + +#: ./doc/common/section_objectstorage-components.xml:136(para) +msgid "Each account and container is an individual SQLite database that is distributed across the cluster. An account database contains the list of containers in that account. A container database contains the list of objects in that container." +msgstr "" + +#: ./doc/common/section_objectstorage-components.xml:149(para) +msgid "To keep track of object data locations, each account in the system has a database that references all of its containers, and each container database references each object." +msgstr "" + +#: ./doc/common/section_objectstorage-components.xml:154(title) ./doc/common/section_objectstorage-components.xml:167(title) +msgid "Partitions" +msgstr "" + +#: ./doc/common/section_objectstorage-components.xml:155(para) +msgid "A partition is a collection of stored data, including account databases, container databases, and objects. Partitions are core to the replication system." +msgstr "" + +#: ./doc/common/section_objectstorage-components.xml:157(para) +msgid "Think of a partition as a bin moving throughout a fulfillment center warehouse. Individual orders get thrown into the bin. The system treats that bin as a cohesive entity as it moves throughout the system. A bin is easier to deal with than many little things. It makes for fewer moving parts throughout the system." +msgstr "" + +#: ./doc/common/section_objectstorage-components.xml:161(para) +msgid "System replicators and object uploads/downloads operate on partitions. As the system scales up, its behavior continues to be predictable because the number of partitions is a fixed number." +msgstr "" + +#: ./doc/common/section_objectstorage-components.xml:164(para) +msgid "Implementing a partition is conceptually simple—a partition is just a directory sitting on a disk with a corresponding hash table of what it contains." +msgstr "" + +#: ./doc/common/section_objectstorage-components.xml:176(title) +msgid "Replicators" +msgstr "" + +#: ./doc/common/section_objectstorage-components.xml:177(para) +msgid "In order to ensure that there are three copies of the data everywhere, replicators continuously examine each partition. For each local partition, the replicator compares it against the replicated copies in the other zones to see if there are any differences." +msgstr "" + +#: ./doc/common/section_objectstorage-components.xml:181(para) +msgid "The replicator knowd if replication needs to take plac by examining hashes. A hash file is created for each partition, which contains hashes of each directory in the partition. Each of the three hash files is compared. For a given partition, the hash files for each of the partition's copies are compared. If the hashes are different, then it is time to replicate, and the directory that needs to be replicated is copied over." +msgstr "" + +#: ./doc/common/section_objectstorage-components.xml:187(para) +msgid "This is where partitions come in handy. With fewer things in the system, larger chunks of data are transferred around (rather than lots of little TCP connections, which is inefficient) and there is a consistent number of hashes to compare." +msgstr "" + +#: ./doc/common/section_objectstorage-components.xml:190(para) +msgid "The cluster eventually has a consistent behavior where the newest data has a priority." +msgstr "" + +#: ./doc/common/section_objectstorage-components.xml:200(para) +msgid "If a zone goes down, one of the nodes containing a replica notices and proactively copies data to a handoff location." +msgstr "" + +#: ./doc/common/section_objectstorage-components.xml:204(title) +msgid "Use cases" +msgstr "" + +#: ./doc/common/section_objectstorage-components.xml:205(para) +msgid "The following sections show use cases for object uploads and downloads and introduce the components." +msgstr "" + +#: ./doc/common/section_objectstorage-components.xml:207(title) +msgid "Upload" +msgstr "" + +#: ./doc/common/section_objectstorage-components.xml:208(para) +msgid "A client uses the REST API to make a HTTP request to PUT an object into an existing container. The cluster receives the request. First, the system must figure out where the data is going to go. To do this, the account name, container name, and object name are all used to determine the partition where this object should live." +msgstr "" + +#: ./doc/common/section_objectstorage-components.xml:212(para) +msgid "Then a lookup in the ring figures out which storage nodes contain the partitions in question." +msgstr "" + +#: ./doc/common/section_objectstorage-components.xml:214(para) +msgid "The data is then sent to each storage node where it is placed in the appropriate partition. At least two of the three writes must be successful before the client is notified that the upload was successful." +msgstr "" + +#: ./doc/common/section_objectstorage-components.xml:217(para) +msgid "Next, the container database is updated asynchronously to reflect that there is a new object in it." +msgstr "" + +#: ./doc/common/section_objectstorage-components.xml:220(title) +msgid "Object Storage in use" +msgstr "" + +#: ./doc/common/section_objectstorage-components.xml:229(title) +msgid "Download" +msgstr "" + +#: ./doc/common/section_objectstorage-components.xml:230(para) +msgid "A request comes in for an acount/container/object. Using the same consistent hashing, the partition name is generated. A lookup in the ring reveals which storage nodes contain that partition. A request is made to one of the storage nodes to fetch the object and, if that fails, requests are made to the other nodes." +msgstr "" + +#: ./doc/common/section_storage-concepts.xml:6(title) +msgid "Storage concepts" +msgstr "" + +#: ./doc/common/section_storage-concepts.xml:7(para) +msgid "The OpenStack stack uses the following storage types:" +msgstr "" + +#: ./doc/common/section_storage-concepts.xml:9(caption) +msgid "Storage types" +msgstr "" + +#: ./doc/common/section_storage-concepts.xml:15(td) +msgid "On-instance / ephemeral" +msgstr "" + +#: ./doc/common/section_storage-concepts.xml:16(td) +msgid "Block storage (Cinder)" +msgstr "" + +#: ./doc/common/section_storage-concepts.xml:22(td) +msgid "Runs operating systems and provides scratch space" +msgstr "" + +#: ./doc/common/section_storage-concepts.xml:23(td) +msgid "Used for adding additional persistent storage to a virtual machine (VM)" +msgstr "" + +#: ./doc/common/section_storage-concepts.xml:25(td) +msgid "Used for storing virtual machine images and data" +msgstr "" + +#: ./doc/common/section_storage-concepts.xml:28(td) +msgid "Persists until VM is terminated" +msgstr "" + +#: ./doc/common/section_storage-concepts.xml:29(td) ./doc/common/section_storage-concepts.xml:30(td) +msgid "Persists until deleted" +msgstr "" + +#: ./doc/common/section_storage-concepts.xml:33(td) ./doc/common/section_storage-concepts.xml:34(td) +msgid "Access associated with a VM" +msgstr "" + +#: ./doc/common/section_storage-concepts.xml:35(td) +msgid "Available from anywhere" +msgstr "" + +#: ./doc/common/section_storage-concepts.xml:38(td) +msgid "Implemented as a filesystem underlying OpenStack Compute" +msgstr "" + +#: ./doc/common/section_storage-concepts.xml:40(td) +msgid "Mounted via OpenStack Block-Storage controlled protocol (for example, iSCSI)" +msgstr "" + +#: ./doc/common/section_storage-concepts.xml:42(td) +msgid "REST API" +msgstr "" + +#: ./doc/common/section_storage-concepts.xml:45(td) +msgid "Administrator configures size setting, based on flavors" +msgstr "" + +#: ./doc/common/section_storage-concepts.xml:47(td) +msgid "Sizings based on need" +msgstr "" + +#: ./doc/common/section_storage-concepts.xml:48(td) +msgid "Easily scalable for future growth" +msgstr "" + +#: ./doc/common/section_storage-concepts.xml:51(td) +msgid "Example: 10GB first disk, 30GB/core second disk" +msgstr "" + +#: ./doc/common/section_storage-concepts.xml:52(td) +msgid "Example: 1TB \"extra hard drive\"" +msgstr "" + +#: ./doc/common/section_storage-concepts.xml:53(td) +msgid "Example: 10s of TBs of data set storage" +msgstr "" + +#: ./doc/common/section_storage-concepts.xml:60(para) +msgid "OpenStack Object Storage is not used like a traditional hard drive. Object storage is all about relaxing some of the constraints of a POSIX-style file system. The access to it is API-based (and the API uses http). This is a good idea as if you don't have to provide atomic operations (that is, you can rely on eventual consistency), you can much more easily scale a storage system and avoid a central point of failure." +msgstr "" + +#: ./doc/common/section_storage-concepts.xml:70(para) +msgid "The OpenStack Image Service is used to manage the virtual machine images in an OpenStack cluster, not store them. Instead, it provides an abstraction to different methods for storage - a bridge to the storage, not the storage itself." +msgstr "" + +#: ./doc/common/section_storage-concepts.xml:77(para) +msgid "OpenStack Object Storage can function on its own. The Object Storage (swift) product can be used independently of the Compute (nova) product." +msgstr "" + +#: ./doc/common/section_storage-concepts.xml:58(para) +msgid "Other points of note include: " +msgstr "" + +#: ./doc/common/section_cli_nova_boot.xml:6(title) +msgid "Launch instances" +msgstr "" + +#: ./doc/common/section_cli_nova_boot.xml:7(para) ./doc/common/section_dashboard_launch_instances_from_image.xml:8(para) +msgid "Instances are virtual machines that run inside the cloud." +msgstr "" + +#: ./doc/common/section_cli_nova_boot.xml:9(para) +msgid "Before you can launch an instance, gather the following parameters:" +msgstr "" + +#: ./doc/common/section_cli_nova_boot.xml:13(para) ./doc/common/section_dashboard_launch_instances_from_image.xml:22(para) +msgid "The instance source, which is an image or snapshot. Alternatively, you can boot from a volume, which is block storage, to which you've copied an image or snapshot." +msgstr "" + +#: ./doc/common/section_cli_nova_boot.xml:19(para) ./doc/common/section_dashboard_launch_instances_from_image.xml:28(para) +msgid "The image or snapshot, which represents the operating system." +msgstr "" + +#: ./doc/common/section_cli_nova_boot.xml:24(para) ./doc/common/section_dashboard_launch_instances_from_image.xml:33(para) +msgid "A name for your instance." +msgstr "" + +#: ./doc/common/section_cli_nova_boot.xml:28(para) +msgid "The flavor for your instance, which defines the compute, memory, and storage capacity of nova computing instances. A flavor is an available hardware configuration for a server. It defines the \"size\" of a virtual server that can be launched." +msgstr "" + +#: ./doc/common/section_cli_nova_boot.xml:36(para) +msgid "User Data is a special key in the metadata service that holds a file that cloud-aware applications in the guest instance can access. For example. the cloudinit system is an open-source package from Ubuntu that is available on various Linux distributions including Ubuntu, Fedora, and openSUSE and that handles early initialization of a cloud instance that uses user data." +msgstr "" + +#: ./doc/common/section_cli_nova_boot.xml:49(para) ./doc/common/section_dashboard_launch_instances_from_image.xml:45(para) +msgid "Access and security credentials, which include one or both of the following credentials:" +msgstr "" + +#: ./doc/common/section_cli_nova_boot.xml:53(para) ./doc/common/section_dashboard_launch_instances_from_image.xml:49(para) +msgid "A keypair for your instance, which are SSH credentials that are injected into images when they are launched. For this to work, the image must contain the cloud-init package. Create at least one keypair for each project. If you already have generated a keypair with an external tool, you can import it into OpenStack. You can use the keypair for multiple instances that belong to that project." +msgstr "" + +#: ./doc/common/section_cli_nova_boot.xml:66(para) ./doc/common/section_dashboard_launch_instances_from_image.xml:62(para) +msgid "A security group, which defines which incoming network traffic is forwarded to instances. Security groups hold a set of firewall policies, known as security group rules." +msgstr "" + +#: ./doc/common/section_cli_nova_boot.xml:77(para) ./doc/common/section_dashboard_launch_instances_from_image.xml:73(para) +msgid "If needed, you can assign a floating (public) IP address to a running instance and attach a block storage device, or volume, for persistent storage." +msgstr "" + +#: ./doc/common/section_cli_nova_boot.xml:83(para) +msgid "After you gather the parameters you need to launch an instance, you can launch it from an image or a volume." +msgstr "" + +#: ./doc/common/section_cli_nova_boot.xml:87(para) +msgid "You can launch an instance directly from one of the available OpenStack images or from an image that you have copied to a persistent volume. The OpenStack Image Service provides a pool of images that are accessible to members of different projects." +msgstr "" + +#: ./doc/common/section_cli_nova_boot.xml:94(title) +msgid "Gather parameters to launch an instance" +msgstr "" + +#: ./doc/common/section_cli_nova_boot.xml:98(para) +msgid "On a shell, source the OpenStack RC file. See ." +msgstr "" + +#: ./doc/common/section_cli_nova_boot.xml:113(para) +msgid "Note the ID of the flavor that you want to use for your instance." +msgstr "" + +#: ./doc/common/section_cli_nova_boot.xml:117(para) +msgid "List the available images:" +msgstr "" + +#: ./doc/common/section_cli_nova_boot.xml:126(para) +msgid "You can also filter the image list by using grep to find a specific image, like this:" +msgstr "" + +#: ./doc/common/section_cli_nova_boot.xml:130(para) +msgid "Note the ID of the image that you want to boot your instance from." +msgstr "" + +#: ./doc/common/section_cli_nova_boot.xml:134(para) +msgid "List the available security groups:" +msgstr "" + +#: ./doc/common/section_cli_nova_boot.xml:136(para) +msgid "If you are an admin user, specify the --all-tenants parameter to list groups for all tenants." +msgstr "" + +#: ./doc/common/section_cli_nova_boot.xml:147(para) +msgid "If you have not created any security groups, you can assign the instance to only the default security group." +msgstr "" + +#: ./doc/common/section_cli_nova_boot.xml:150(para) +msgid "You can also list rules for a specified security group:" +msgstr "" + +#: ./doc/common/section_cli_nova_boot.xml:153(para) +msgid "This example modifies the default security group to allow HTTP traffic on the instance by permitting TCP traffic on Port 80." +msgstr "" + +#: ./doc/common/section_cli_nova_boot.xml:158(para) +msgid "List the available keypairs." +msgstr "" + +#: ./doc/common/section_cli_nova_boot.xml:160(para) +msgid "Note the name of the keypair that you use for SSH access." +msgstr "" + +#: ./doc/common/section_cli_nova_boot.xml:167(title) ./doc/common/section_dashboard_launch_instances_from_image.xml:6(title) +msgid "Launch an instance from an image" +msgstr "" + +#: ./doc/common/section_cli_nova_boot.xml:170(para) +msgid "Now you have all parameters required to launch an instance, run the following command and specify the server name, flavor ID, and image ID. Optionally, you can provide a key name for access control and security group for security. You can also include metadata key and value pairs. For example you can add a description for your server by providing the --meta description=\"My Server\" parameter." +msgstr "" + +#: ./doc/common/section_cli_nova_boot.xml:179(para) +msgid "You can pass user data in a local file at instance launch by using the flag --user-data USER-DATA-FILE parameter." +msgstr "" + +#: ./doc/common/section_cli_nova_boot.xml:184(replaceable) +msgid "FLAVOR_ID" +msgstr "" + +#: ./doc/common/section_cli_nova_boot.xml:184(replaceable) +msgid "IMAGE_ID" +msgstr "" + +#: ./doc/common/section_cli_nova_boot.xml:184(replaceable) +msgid "KEY_NAME" +msgstr "" + +#: ./doc/common/section_cli_nova_boot.xml:185(replaceable) +msgid "SEC_GROUP NAME_FOR_INSTANCE" +msgstr "" + +#: ./doc/common/section_cli_nova_boot.xml:186(replaceable) ./doc/common/section_cli_nova_boot.xml:187(replaceable) +msgid "KEY=VALUE" +msgstr "" + +#: ./doc/common/section_cli_nova_boot.xml:188(replaceable) +msgid "SERVER_NAME" +msgstr "" + +#: ./doc/common/section_cli_nova_boot.xml:189(para) +msgid "Depending on the parameters that you provide, the command returns a list of server properties." +msgstr "" + +#: ./doc/common/section_cli_nova_boot.xml:192(para) +msgid "A status of BUILD indicates that the instance has started, but is not yet online." +msgstr "" + +#: ./doc/common/section_cli_nova_boot.xml:195(para) +msgid "A status of ACTIVE indicates that the instance is active." +msgstr "" + +#: ./doc/common/section_cli_nova_boot.xml:227(para) +msgid "Copy the server ID value from the id field in the output. You use this ID to get details for or delete your server." +msgstr "" + +#: ./doc/common/section_cli_nova_boot.xml:231(para) +msgid "Copy the administrative password value from the adminPass field. You use this value to log into your server." +msgstr "" + +#: ./doc/common/section_cli_nova_boot.xml:235(para) +msgid "Arbitrary local files can also be placed into the instance file system at creation time using the --file <dst-path=src-path> option. You may store up to 5 files. For example if you have a special authorized_keys file named special_authorized_keysfile that you want to put on the instance rather than using the regular ssh key injection, you can use the following command:" +msgstr "" + +#: ./doc/common/section_cli_nova_boot.xml:251(para) +msgid "Check if the instance is online:" +msgstr "" + +#: ./doc/common/section_cli_nova_boot.xml:253(para) +msgid "The list shows the ID, name, status, and private (and if assigned, public) IP addresses for all instances in the project that you belong to:" +msgstr "" + +#: ./doc/common/section_cli_nova_boot.xml:263(para) +msgid "If the status for the instance is ACTIVE, the instance is online." +msgstr "" + +#: ./doc/common/section_cli_nova_boot.xml:265(para) +msgid "To view the available options for the command, run the following command:" +msgstr "" + +#: ./doc/common/section_cli_nova_boot.xml:271(para) +msgid "If you did not provide a keypair, security groups, or rules, you can only access the instance from inside the cloud through VNC. Even pinging the instance is not possible." +msgstr "" + +#: ./doc/common/section_keystone_config_ldap.xml:6(title) +msgid "Configure the Identity Service with an LDAP back-end" +msgstr "" + +#: ./doc/common/section_keystone_config_ldap.xml:8(para) +msgid "As an alternative to the SQL database backing store, the Identity Service can use a directory server to provide the Identity Service, for example:" +msgstr "" + +#: ./doc/common/section_keystone_config_ldap.xml:31(para) +msgid "The corresponding entries in the keystone.conf configuration file are:" +msgstr "" + +#: ./doc/common/section_keystone_config_ldap.xml:50(para) +msgid "The default object classes and attributes are intentionally simple. They reflect the common standard objects according to the LDAP RFCs. However, in a live deployment, you can override the correct attributes to support a preexisting, complex schema. For example, in the user object, the objectClass posixAccount from RFC2307 is very common. If this is the underlying objectclass, then the uid field should probably be uidNumber and username field either uid or cn. To change these two fields, the corresponding entries in the Keystone configuration file are:" +msgstr "" + +#: ./doc/common/section_keystone_config_ldap.xml:65(para) +msgid "Depending on your deployment, you can modify a set of allowed actions for each object type. For example, you might set the following options:" +msgstr "" + +#: ./doc/common/section_keystone_config_ldap.xml:80(para) +msgid "If the back-end provides too much output, you can filter users, tenants, and roles. For example:" +msgstr "" + +#: ./doc/common/section_keystone_config_ldap.xml:86(para) +msgid "If the directory server has not enabled the boolean type for the user, you can use configuration options to extract the value from an integer attribute. For example, in an Active Directory, as follows:" +msgstr "" + +#: ./doc/common/section_keystone_config_ldap.xml:95(para) +msgid "The attribute is an integer. Bit 1 contains the enabled attribute. If the user_enabled_mask mask is not 0, it gets its value from the field and it performs an ADD operation by using the user_enabled_mask value. If the value matches the mask, the account is disabled." +msgstr "" + +#: ./doc/common/section_keystone_config_ldap.xml:102(para) +msgid "It also saves the value without mask to the identity user in the attribute. In case you must change it to enable or disable a user, you can use this value because it contains more information than the status such as, password expiration. The user_enabled_mask value is required to create a default value on the integer attribute (512 = NORMAL ACCOUNT on AD)." +msgstr "" + +#: ./doc/common/section_keystone_config_ldap.xml:111(para) +msgid "If Active Directory classes and attributes do not match the specified classes in the LDAP module, so you can modify them, as follows:" +msgstr "" + +#. When image changes, this message will be marked fuzzy or untranslated for you. +#. It doesn't matter what you translate it to: it's not used at all. +#: ./doc/common/section_dashboard_launch_instances_from_image.xml:106(None) +msgid "@@image: 'figures/launch_instances.png'; md5=8a7e6864bce97f6478db572daf3ef5de" +msgstr "" + +#. When image changes, this message will be marked fuzzy or untranslated for you. +#. It doesn't matter what you translate it to: it's not used at all. +#: ./doc/common/section_dashboard_launch_instances_from_image.xml:164(None) +msgid "@@image: 'figures/instances.png'; md5=6b0f5cb3009d447334ff8b5c5b2cd121" +msgstr "" + +#: ./doc/common/section_dashboard_launch_instances_from_image.xml:10(para) +msgid "You can launch an instance directly from one of the available OpenStack images. The OpenStack Image Service provides a pool of images that are accessible to members of different projects. When you launch an instance from an image, OpenStack creates a local copy of the image on the respective compute node where the instance is started." +msgstr "" + +#: ./doc/common/section_dashboard_launch_instances_from_image.xml:16(para) +msgid "Alternatively, you can launch an instance from an image that you have copied to a persistent volume." +msgstr "" + +#: ./doc/common/section_dashboard_launch_instances_from_image.xml:18(para) +msgid "To launch an instance, specify the following parameters:" +msgstr "" + +#: ./doc/common/section_dashboard_launch_instances_from_image.xml:37(para) +msgid "The flavor for your instance, which defines the compute, memory, and storage capacity of nova computing instances. A flavor is an available hardware configuration for a server. It defines the size of a virtual server that can be launched." +msgstr "" + +#: ./doc/common/section_dashboard_launch_instances_from_image.xml:80(title) +msgid "To launch an instance:" +msgstr "" + +#: ./doc/common/section_dashboard_launch_instances_from_image.xml:82(para) +msgid "Log in to the OpenStack dashboard." +msgstr "" + +#: ./doc/common/section_dashboard_launch_instances_from_image.xml:85(para) +msgid "If you are a member of multiple projects, select a project from the drop-down list at the top of the Project tab." +msgstr "" + +#: ./doc/common/section_dashboard_launch_instances_from_image.xml:90(para) +msgid "Click the Images & Snapshot category." +msgstr "" + +#: ./doc/common/section_dashboard_launch_instances_from_image.xml:92(para) +msgid "The dashboard shows the images that have been uploaded to OpenStack Image Service and are available for this project." +msgstr "" + +#: ./doc/common/section_dashboard_launch_instances_from_image.xml:100(title) +msgid "OpenStack dashboard - Launch Instances window" +msgstr "" + +#: ./doc/common/section_dashboard_launch_instances_from_image.xml:97(para) +msgid "Select an image and click Launch. The Launch Image window appears: " +msgstr "" + +#: ./doc/common/section_dashboard_launch_instances_from_image.xml:112(para) +msgid "Specify the following parameters:" +msgstr "" + +#: ./doc/common/section_dashboard_launch_instances_from_image.xml:116(para) +msgid "Enter an instance name to assign to the virtual machine." +msgstr "" + +#: ./doc/common/section_dashboard_launch_instances_from_image.xml:120(para) +msgid "From the Flavor drop-down list, select the size of the virtual machine to launch." +msgstr "" + +#: ./doc/common/section_dashboard_launch_instances_from_image.xml:125(para) +msgid "Optionally, select a keypair." +msgstr "" + +#: ./doc/common/section_dashboard_launch_instances_from_image.xml:126(para) +msgid "In case an image uses a static root password or a static key set (neither is recommended), you do not need to provide a keypair on starting the instance." +msgstr "" + +#: ./doc/common/section_dashboard_launch_instances_from_image.xml:132(para) +msgid "In Instance Count, enter the number of virtual machines to launch from this image." +msgstr "" + +#: ./doc/common/section_dashboard_launch_instances_from_image.xml:137(para) +msgid "Assign the instance to the default security group. If you added rules to this group, the instance implements these rules." +msgstr "" + +#: ./doc/common/section_dashboard_launch_instances_from_image.xml:150(para) +msgid "Click Launch Instance. The instance is launched on any of the compute nodes in the cloud." +msgstr "" + +#: ./doc/common/section_dashboard_launch_instances_from_image.xml:155(para) +msgid "After you have launched an instance, switch to the Instances & Volumes category to view the instance name, its (private or public) IP address, size, status, task, and power state." +msgstr "" + +#: ./doc/common/section_dashboard_launch_instances_from_image.xml:160(title) +msgid "OpenStack dashboard - Instances" +msgstr "" + +#: ./doc/common/section_dashboard_launch_instances_from_image.xml:168(para) +msgid "If you did not provide a keypair on starting and have not touched security groups or rules so far, by default the instance can only be accessed from inside the cloud through VNC at this point. Even pinging the instance is not possible." +msgstr "" + +#: ./doc/common/section_identity-troubleshooting.xml:6(title) +msgid "Troubleshoot the Identity Service" +msgstr "" + +#: ./doc/common/section_identity-troubleshooting.xml:7(para) +msgid "To troubleshoot the Identity Service, review the logs in the /var/log/keystone.log file." +msgstr "" + +#: ./doc/common/section_identity-troubleshooting.xml:10(para) +msgid "Use the /etc/keystone/logging.conf file to configure the location of log files." +msgstr "" + +#: ./doc/common/section_identity-troubleshooting.xml:13(para) +msgid "The logs show the components that have come in to the WSGI request, and ideally show an error that explains why an authorization request failed. If you do not see the request in the logs, run keystone with --debug parameter. Pass the --debug parameter before the command parameters." +msgstr "" + +#: ./doc/common/section_identity-troubleshooting.xml:20(title) +msgid "Debug PKI middleware" +msgstr "" + +#: ./doc/common/section_identity-troubleshooting.xml:21(para) +msgid "If you receive an Invalid OpenStack Identity Credentials message when you talk to an OpenStack service, it might be caused by the changeover from UUID tokens to PKI tokens in the Grizzly release. Learn how to troubleshoot this error." +msgstr "" + +#: ./doc/common/section_identity-troubleshooting.xml:26(para) +msgid "The PKI-based token validation scheme relies on certificates from the Identity Service that are fetched through HTTP and stored in a local directory. The location for this directory is specified by the signing_dir configuration option. In your services configuration file, look for a section like this:" +msgstr "" + +#: ./doc/common/section_identity-troubleshooting.xml:41(para) +msgid "If your service lacks this stanza, the keystoneclient/middleware/auth_token.py file specifies the defaults. If no value is specified for this directory, it defaults to a secure temporary directory. Initialization code for the service checks that the directory exists and is writable. If it does not exist, the code tries to create it. If this fails, the service fails to start. However, it often succeeds but problems occur later." +msgstr "" + +#: ./doc/common/section_identity-troubleshooting.xml:53(para) +msgid "The first thing to check is that the signing_dir does, in fact, exist. If it does, check for the presence of the certificate files inside there:" +msgstr "" + +#: ./doc/common/section_identity-troubleshooting.xml:64(para) +msgid "This directory contains two certificates and the token revocation list. If these files are not present, your service cannot fetch them from the Identity Service. To troubleshoot, try to talk to the Identity Service to make sure it is serving out the files, as follows:" +msgstr "" + +#: ./doc/common/section_identity-troubleshooting.xml:70(para) +msgid "This command fetches the signing certificate:" +msgstr "" + +#: ./doc/common/section_identity-troubleshooting.xml:81(para) +msgid "Note the expiration dates of the certificate:" +msgstr "" + +#: ./doc/common/section_identity-troubleshooting.xml:84(para) +msgid "The token revocation list is updated once a minute, but the certificates are not. One possible problem is that the certificates are the wrong files or garbage. You can remove these files and run another command against your server: They are fetched on demand." +msgstr "" + +#: ./doc/common/section_identity-troubleshooting.xml:89(para) +msgid "The Identity Service log should show the access of the certificate files. You might have to turn up your logging levels. Set debug = True and verbose = True in your Identity Service configuration file and restart the Identity Service server." +msgstr "" + +#: ./doc/common/section_identity-troubleshooting.xml:99(para) +msgid "If the files do not appear in your directory after this, it is likely one of the following issues:" +msgstr "" + +#: ./doc/common/section_identity-troubleshooting.xml:103(para) +msgid "Your service is configured incorrectly and cannot talk to the Identity Service. Check the auth_port and auth_host values and make sure that you can talk to that service through cURL, as shown previously." +msgstr "" + +#: ./doc/common/section_identity-troubleshooting.xml:111(para) +msgid "Your signing directory is not writable. Use the command to change its permissions so that the service (POSIX) user can write to it. Verify the change through and commands." +msgstr "" + +#: ./doc/common/section_identity-troubleshooting.xml:119(para) +msgid "The SELinux policy is denying access to the directory." +msgstr "" + +#: ./doc/common/section_identity-troubleshooting.xml:123(para) +msgid "SELinux troubles often when you use Fedora/RHEL-based packages and you choose configuration options that do not match the standard policy. Run the command. If that makes a different, you should relabel the directory. If you are using a sub-directory of the /var/cache/ directory, run the following command:" +msgstr "" + +#: ./doc/common/section_identity-troubleshooting.xml:132(para) +msgid "If you are not using a /var/cache sub-directory, you should. Modify the signing_dir configuration option for your service and restart." +msgstr "" + +#: ./doc/common/section_identity-troubleshooting.xml:136(para) +msgid "Set back to setenforce enforcing to confirm that your changes solve the problem." +msgstr "" + +#: ./doc/common/section_identity-troubleshooting.xml:138(para) +msgid "If your certificates are fetched on demand, the PKI validation is working properly. Most likely, the token from the Identity Service is not valid for the operation you are attempting to perform, and your user needs a different role for the operation." +msgstr "" + +#: ./doc/common/section_identity-troubleshooting.xml:145(title) +msgid "Debug signing key file errors" +msgstr "" + +#: ./doc/common/section_identity-troubleshooting.xml:146(para) +msgid "If an error occurs when the signing key file opens, it is possible that the person who ran the command to generate certificates and keys did not use the correct user. When you run the command, the Identity Service generates a set of certificates and keys in /etc/keystone/ssl*, which is owned by root:root." +msgstr "" + +#: ./doc/common/section_identity-troubleshooting.xml:155(para) +msgid "This can present a problem when you run the Identity Service daemon under the keystone user account (nologin) when you try to run PKI. Unless you run the command against the files keystone:keystone or run the command with the --keystone-user and --keystone-group parameters, you get an error, as follows:" +msgstr "" + +#: ./doc/common/section_dashboard_customizing.xml:6(title) +msgid "Customize the dashboard" +msgstr "" + +#: ./doc/common/section_dashboard_customizing.xml:7(para) +msgid "Adapted from How To Custom Brand The OpenStack “Horizon” Dashboard." +msgstr "" + +#: ./doc/common/section_dashboard_customizing.xml:11(para) +msgid "You install the OpenStack dashboard through the openstack-dashboard package. You can customize the dashboard with your own colors, logo, and site title through a CSS file." +msgstr "" + +#: ./doc/common/section_dashboard_customizing.xml:15(para) +msgid "Canonical also provides an openstack-dashboard-ubuntu-theme package that brands the Python-based Django interface." +msgstr "" + +#: ./doc/common/section_dashboard_customizing.xml:47(para) +msgid "Create a graphical logo with a transparent background. The text TGen Cloud in this example is rendered through .png files of multiple sizes created with a graphics program." +msgstr "" + +#: ./doc/common/section_dashboard_customizing.xml:52(para) +msgid "Use a 200×27 for the logged-in banner graphic, and 365×50 for the login screen graphic." +msgstr "" + +#: ./doc/common/section_dashboard_customizing.xml:56(para) +msgid "Set the HTML title, which appears at the top of the browser window, by adding the following line to /etc/openstack-dashboard/local_settings.py:" +msgstr "" + +#: ./doc/common/section_dashboard_customizing.xml:59(code) +msgid "SITE_BRANDING = \"Example, Inc. Cloud\"" +msgstr "" + +#: ./doc/common/section_dashboard_customizing.xml:63(para) +msgid "Upload your new graphic files to the following location: /usr/share/openstack-dashboard/openstack_dashboard/static/dashboard/img/" +msgstr "" + +#: ./doc/common/section_dashboard_customizing.xml:68(para) +msgid "Create a CSS style sheet in the following directory: /usr/share/openstack-dashboard/openstack_dashboard/static/dashboard/css/" +msgstr "" + +#: ./doc/common/section_dashboard_customizing.xml:72(para) +msgid "Edit your CSS file to override the Ubuntu customizations in the ubuntu.css file." +msgstr "" + +#: ./doc/common/section_dashboard_customizing.xml:75(para) +msgid "Change the colors and image file names as appropriate, though the relative directory paths should be the same. The following example file shows you how to customize your CSS file:" +msgstr "" + +#: ./doc/common/section_dashboard_customizing.xml:114(para) +msgid "Open the following HTML template in an editor: /usr/share/openstack-dashboard/openstack_dashboard/templates/_stylesheets.html" +msgstr "" + +#: ./doc/common/section_dashboard_customizing.xml:118(para) +msgid "Add a line to include your custom.css file:" +msgstr "" + +#: ./doc/common/section_dashboard_customizing.xml:123(emphasis) +msgid "<link href='{{ STATIC_URL }}dashboard/css/custom.css' media='screen' rel='stylesheet' />" +msgstr "" + +#: ./doc/common/section_dashboard_customizing.xml:127(para) +msgid "Restart apache:" +msgstr "" + +#: ./doc/common/section_dashboard_customizing.xml:128(para) ./doc/common/section_dashboard_sessions.xml:175(para) +msgid "On Ubuntu: " +msgstr "" + +#: ./doc/common/section_dashboard_customizing.xml:131(para) +msgid "On Fedora, RHEL, CentOS: " +msgstr "" + +#: ./doc/common/section_dashboard_customizing.xml:134(para) ./doc/common/section_dashboard_sessions.xml:182(para) +msgid "On openSUSE: " +msgstr "" + +#: ./doc/common/section_dashboard_customizing.xml:139(para) +msgid "Reload the dashboard in your browser to view your changes." +msgstr "" + +#: ./doc/common/section_dashboard_customizing.xml:141(para) +msgid "Modify your CSS file as appropriate." +msgstr "" + +#: ./doc/common/section_cli_version.xml:6(title) +msgid "Get the version for a client" +msgstr "" + +#: ./doc/common/section_cli_version.xml:7(para) +msgid "After you install an OpenStack client, you can get its version number." +msgstr "" + +#: ./doc/common/section_cli_version.xml:11(para) +msgid "Run the following command get the version number for a client:" +msgstr "" + +#: ./doc/common/section_cli_version.xml:13(replaceable) ./doc/common/section_cli_install.xml:121(replaceable) ./doc/common/section_cli_install.xml:136(replaceable) ./doc/common/section_cli_install.xml:147(replaceable) ./doc/common/section_cli_install.xml:171(replaceable) ./doc/common/section_cli_install.xml:173(replaceable) +msgid "PROJECT" +msgstr "" + +#: ./doc/common/section_cli_version.xml:14(para) +msgid "Where PROJECT is one of the following project names:" +msgstr "" + +#: ./doc/common/section_cli_version.xml:19(para) ./doc/common/section_cli_install.xml:179(para) +msgid "nova. Compute API and extensions." +msgstr "" + +#: ./doc/common/section_cli_version.xml:23(para) ./doc/common/section_cli_install.xml:183(para) +msgid "neutron. Networking API." +msgstr "" + +#: ./doc/common/section_cli_version.xml:27(para) ./doc/common/section_cli_install.xml:187(para) +msgid "keystone. Identity Service API." +msgstr "" + +#: ./doc/common/section_cli_version.xml:31(para) ./doc/common/section_cli_install.xml:191(para) +msgid "glance. Image Service API." +msgstr "" + +#: ./doc/common/section_cli_version.xml:35(para) ./doc/common/section_cli_install.xml:195(para) +msgid "swift. Object Storage API." +msgstr "" + +#: ./doc/common/section_cli_version.xml:39(para) ./doc/common/section_cli_install.xml:199(para) +msgid "cinder. Block Storage Service API." +msgstr "" + +#: ./doc/common/section_cli_version.xml:43(para) ./doc/common/section_cli_install.xml:203(para) +msgid "heat. Orchestration API." +msgstr "" + +#: ./doc/common/section_cli_version.xml:47(para) ./doc/common/section_cli_install.xml:207(para) +msgid "ceilometer. Telemetry API." +msgstr "" + +#: ./doc/common/section_cli_version.xml:51(para) +msgid "For example, to see the version of the nova client, run the following command:" +msgstr "" + +#: ./doc/common/section_cli_version.xml:56(para) +msgid "To see the version of the keystone client, run the following command:" +msgstr "" + +#: ./doc/common/section_keystone-concepts-group-management.xml:7(para) +msgid "A group is a collection of users. Administrators can create groups and add users to them. Then, rather than assign a role to each user individually, assign a role to the group. Every group is in a domain. Groups were introduced with version 3 of the Identity API (the Grizzly release of Identity Service)." +msgstr "" + +#: ./doc/common/section_keystone-concepts-group-management.xml:13(para) +msgid "Identity API V3 provides the following group-related operations:" +msgstr "" + +#: ./doc/common/section_keystone-concepts-group-management.xml:17(para) +msgid "Create a group" +msgstr "" + +#: ./doc/common/section_keystone-concepts-group-management.xml:20(para) +msgid "Delete a group" +msgstr "" + +#: ./doc/common/section_keystone-concepts-group-management.xml:23(para) +msgid "Update a group (change its name or description)" +msgstr "" + +#: ./doc/common/section_keystone-concepts-group-management.xml:27(para) +msgid "Add a user to a group" +msgstr "" + +#: ./doc/common/section_keystone-concepts-group-management.xml:30(para) +msgid "Remove a user from a group" +msgstr "" + +#: ./doc/common/section_keystone-concepts-group-management.xml:33(para) +msgid "List group members" +msgstr "" + +#: ./doc/common/section_keystone-concepts-group-management.xml:36(para) +msgid "List groups for a user" +msgstr "" + +#: ./doc/common/section_keystone-concepts-group-management.xml:39(para) +msgid "Assign a role on a tenant to a group" +msgstr "" + +#: ./doc/common/section_keystone-concepts-group-management.xml:42(para) +msgid "Assign a role on a domain to a group" +msgstr "" + +#: ./doc/common/section_keystone-concepts-group-management.xml:45(para) +msgid "Query role assignments to groups" +msgstr "" + +#: ./doc/common/section_keystone-concepts-group-management.xml:49(para) +msgid "The Identity service server might not allow all operations. For example, if using the Identity server with the LDAP Identity back end and group updates are disabled, then a request to create, delete, or update a group fails." +msgstr "" + +#: ./doc/common/section_keystone-concepts-group-management.xml:55(para) +msgid "Here are a couple examples:" +msgstr "" + +#: ./doc/common/section_keystone-concepts-group-management.xml:58(para) +msgid "Group A is granted Role A on Tenant A. If User A is a member of Group A, when User A gets a token scoped to Tenant A, the token also includes Role A." +msgstr "" + +#: ./doc/common/section_keystone-concepts-group-management.xml:64(para) +msgid "Group B is granted Role B on Domain B. If User B is a member of Domain B, if User B gets a token scoped to Domain B, the token also includes Role B." +msgstr "" + +#: ./doc/common/section_cli_overview.xml:15(para) +msgid "You can use the OpenStack command-line clients to run simple commands that make API calls. You can run these commands from the command line or in scripts to automate tasks. As long as you provide OpenStack credentials, you can run these commands on any machine." +msgstr "" + +#: ./doc/common/section_cli_overview.xml:20(para) +msgid "Internally, each client command runs cURL commands that embed API requests. The OpenStack APIs are RESTful APIs that use the HTTP protocol, including methods, URIs, media types, and response codes." +msgstr "" + +#: ./doc/common/section_cli_overview.xml:24(para) +msgid "These open-source Python clients run on Linux or Mac OS X systems and are easy to learn and use. Each OpenStack service has its own command-line client. On some client commands, you can specify a debug parameter to show the underlying API request for the command. This is a good way to become familiar with the OpenStack API calls." +msgstr "" + +#: ./doc/common/section_cli_overview.xml:35(para) +msgid "These command-line clients are available for the respective services' APIs:" +msgstr "" + +#: ./doc/common/section_cli_overview.xml:39(para) +msgid " (python-ceilometerclient). Client for the Telemetry API that lets you create and collect measurements across OpenStack." +msgstr "" + +#: ./doc/common/section_cli_overview.xml:45(para) +msgid " (python-cinderclient). Client for the Block Storage Service API that lets you create and manage volumes." +msgstr "" + +#: ./doc/common/section_cli_overview.xml:51(para) +msgid " (python-glanceclient). Client for the Image Service API that lets you create and manage images." +msgstr "" + +#: ./doc/common/section_cli_overview.xml:57(para) +msgid " (python-heatclient). Client for the Orchestration API that lets you launch stacks from templates, view details of running stacks including events and resources, and update and delete stacks." +msgstr "" + +#: ./doc/common/section_cli_overview.xml:65(para) +msgid " (python-keystoneclient). Client for the Identity Service API that lets you create and manage users, tenants, roles, endpoints, and credentials." +msgstr "" + +#: ./doc/common/section_cli_overview.xml:72(para) +msgid " (python-neutronclient). Client for the Networking API that lets you configure networks for guest servers. This client was previously known as ." +msgstr "" + +#: ./doc/common/section_cli_overview.xml:79(para) +msgid " (python-novaclient). Client for the Compute API and its extensions. Use to create and manage images, instances, and flavors." +msgstr "" + +#: ./doc/common/section_cli_overview.xml:85(para) +msgid " (python-swiftclient). Client for the Object Storage API that lets you gather statistics, list items, update metadata, upload, download and delete files stored by the Object Storage service. Provides access to a swift installation for ad hoc processing." +msgstr "" + +#: ./doc/common/section_cli_overview.xml:94(para) +msgid "An OpenStack client is in development." +msgstr "" + +#: ./doc/common/section_cli_overview.xml:96(para) +msgid "For client installation instructions, see Install the OpenStack command-line clients. For information about the OpenStack RC file, see Download and source the OpenStack RC file. Both topics are in the OpenStack End User Guide." +msgstr "" + +#: ./doc/common/section_rpc.xml:8(para) +msgid "OpenStack projects use AMQP, an open standard for messaging middleware. OpenStack services that run on multiple servers to talk to each other. OpenStack Oslo RPC supports three implementations of AMQP: RabbitMQ, Qpid, and ZeroMQ." +msgstr "" + +#: ./doc/common/section_rpc.xml:16(para) +msgid "OpenStack Oslo RPC uses RabbitMQ by default. Use these options to configure the RabbitMQ message system. The rpc_backend option is not required as long as RabbitMQ is the default messaging system. However, if it is included the configuration, you must set it to nova.openstack.common.rpc.impl_kombu." +msgstr "" + +#: ./doc/common/section_rpc.xml:25(para) +msgid "You can use these additional options to configure the RabbitMQ messaging system. You can configure messaging communication for different installation scenarios, tune retries for RabbitMQ, and define the size of the RPC thread pool. To monitor notifications through RabbitMQ, you must set the option to nova.notifier.rabbit_notifier in the nova.conf file. The default for sending usage data is sixty seconds plus a random number of seconds from zero to sixty." +msgstr "" + +#: ./doc/common/section_rpc.xml:40(para) +msgid "Use these options to configure the Qpid messaging system for OpenStack Oslo RPC. Qpid is not the default messaging system, so you must enable it by setting the option in the nova.conf file." +msgstr "" + +#: ./doc/common/section_rpc.xml:47(para) +msgid "This critical option points the compute nodes to the Qpid broker (server). Set to the host name where the broker runs in the nova.conf file." +msgstr "" + +#: ./doc/common/section_rpc.xml:69(para) +msgid "This table lists additional options that you use to configure the Qpid messaging driver for OpenStack Oslo RPC. These options are used infrequently." +msgstr "" + +#: ./doc/common/section_rpc.xml:76(para) +msgid "Use these options to configure the ZeroMQ messaging system for OpenStack Oslo RPC. ZeroMQ is not the default messaging system, so you must enable it by setting the option in the nova.conf file." +msgstr "" + +#: ./doc/common/section_rpc.xml:86(para) +msgid "Use these options to configure the RabbitMQ and Qpid messaging drivers." +msgstr "" + +#: ./doc/common/section_cli_install.xml:15(title) +msgid "Install the OpenStack command-line clients" +msgstr "" + +#: ./doc/common/section_cli_install.xml:16(para) +msgid "Install the prerequisite software and the Python package for each OpenStack client." +msgstr "" + +#: ./doc/common/section_cli_install.xml:19(para) +msgid "For each command, replace PROJECT with the lower case name of the client to install, such as nova. Repeat for each client." +msgstr "" + +#: ./doc/common/section_cli_install.xml:26(caption) +msgid "Prerequisite software" +msgstr "" + +#: ./doc/common/section_cli_install.xml:31(th) +msgid "Prerequisite" +msgstr "" + +#: ./doc/common/section_cli_install.xml:38(para) +msgid "Python 2.6 or newer" +msgstr "" + +#: ./doc/common/section_cli_install.xml:41(para) +msgid "Currently, the clients do not support Python 3." +msgstr "" + +#: ./doc/common/section_cli_install.xml:47(para) +msgid "setuptools package" +msgstr "" + +#: ./doc/common/section_cli_install.xml:50(para) +msgid "Installed by default on Mac OS X." +msgstr "" + +#: ./doc/common/section_cli_install.xml:51(para) +msgid "Many Linux distributions provide packages to make setuptools easy to install. Search your package manager for setuptools to find an installation package. If you cannot find one, download the setuptools package directly from http://pypi.python.org/pypi/setuptools." +msgstr "" + +#: ./doc/common/section_cli_install.xml:59(para) +msgid "The recommended way to install setuptools on Microsoft Windows is to follow the documentation provided on the setuptools website. Another option is to use the unofficial binary installer maintained by Christoph Gohlke (http://www.lfd.uci.edu/~gohlke/pythonlibs/#setuptools)." +msgstr "" + +#: ./doc/common/section_cli_install.xml:72(package) +msgid "pip" +msgstr "" + +#: ./doc/common/section_cli_install.xml:72(td) +msgid " package" +msgstr "" + +#: ./doc/common/section_cli_install.xml:74(para) +msgid "To install the clients on a Linux, Mac OS X or Microsoft Windows system, use pip. It is easy to use, ensures that you get the latest version of the clients from the Python Package Index, and lets you update or remove the packages later on." +msgstr "" + +#: ./doc/common/section_cli_install.xml:81(para) +msgid "Install pip through the package manager for your system:" +msgstr "" + +#: ./doc/common/section_cli_install.xml:84(title) +msgid "Mac OS X" +msgstr "" + +#: ./doc/common/section_cli_install.xml:89(title) +msgid "Microsoft Windows" +msgstr "" + +#: ./doc/common/section_cli_install.xml:90(para) +msgid "Make sure that the C:\\Python27\\Scripts directory is defined in the PATH environment variable, and use the command from the setuptools package: Another option is to use the unofficial binary installer provided by Christoph Gohlke (http://www.lfd.uci.edu/~gohlke/pythonlibs/#pip)." +msgstr "" + +#: ./doc/common/section_cli_install.xml:103(title) +msgid "Ubuntu 12.04" +msgstr "" + +#: ./doc/common/section_cli_install.xml:104(para) +msgid "A packaged version enables you to use dpkg or aptitude to install the python-novaclient:" +msgstr "" + +#: ./doc/common/section_cli_install.xml:111(title) +msgid "Ubuntu" +msgstr "" + +#: ./doc/common/section_cli_install.xml:115(title) +msgid "RHEL, CentOS, or Fedora" +msgstr "" + +#: ./doc/common/section_cli_install.xml:116(para) +msgid "A packaged version available in RDO enables you to use yum to install the clients: " +msgstr "" + +#: ./doc/common/section_cli_install.xml:123(para) +msgid "Alternatively, install pip and use it to manage client installation:" +msgstr "" + +#: ./doc/common/section_cli_install.xml:128(title) +msgid "openSUSE 12.2 and earlier" +msgstr "" + +#: ./doc/common/section_cli_install.xml:129(para) +msgid "A packaged version available in the Open Build Service enables you to use rpm or zypper to install the python-novaclient:" +msgstr "" + +#: ./doc/common/section_cli_install.xml:137(para) +msgid "Alternatively, install pip and use it to manage client installation: " +msgstr "" + +#: ./doc/common/section_cli_install.xml:142(title) +msgid "openSUSE 12.3 and newer" +msgstr "" + +#: ./doc/common/section_cli_install.xml:143(para) +msgid "A packaged version enables you to use rpm or zypper to install the clients: " +msgstr "" + +#: ./doc/common/section_cli_install.xml:154(title) +msgid "Install the clients" +msgstr "" + +#: ./doc/common/section_cli_install.xml:155(para) +msgid "Use pip to install the OpenStack clients on a Linux, Mac OS X or Microsoft Windows system. It is easy and ensures that you get the latest version of the client from the Python Package Index. Also, pip lets you update or remove a package. After you install the clients, you must source an openrc.sh file to set required environment variables before you can request OpenStack services through the clients or the APIs." +msgstr "" + +#: ./doc/common/section_cli_install.xml:168(para) +msgid "You must install each client separately." +msgstr "" + +#: ./doc/common/section_cli_install.xml:169(para) +msgid "Run this command to install a client package." +msgstr "" + +#: ./doc/common/section_cli_install.xml:170(para) +msgid "For Mac OS X or Linux:" +msgstr "" + +#: ./doc/common/section_cli_install.xml:172(para) +msgid "For Microsoft Windows:" +msgstr "" + +#: ./doc/common/section_cli_install.xml:174(para) +msgid "Where PROJECT is the project name and has one of the following values:" +msgstr "" + +#: ./doc/common/section_cli_install.xml:211(para) +msgid "For example, to install the nova client, run this command:" +msgstr "" + +#: ./doc/common/section_cli_install.xml:214(para) +msgid "To remove the nova client, run this command:" +msgstr "" + +#: ./doc/common/section_cli_install.xml:217(para) +msgid "To upgrade a package, add the --upgrade option to the command." +msgstr "" + +#: ./doc/common/section_cli_install.xml:220(para) +msgid "To update the nova client, run this command:" +msgstr "" + +#: ./doc/common/section_cli_install.xml:225(para) +msgid "Before you can run client commands, you must create and source the openrc.sh file to set environment variables. See ." +msgstr "" + +#: ./doc/common/section_keystone-concepts-service-management.xml:5(title) +msgid "Service management" +msgstr "" + +#: ./doc/common/section_keystone-concepts-service-management.xml:6(para) +msgid "The Identity Service provides identity, token, catalog, and policy services. It consists of:" +msgstr "" + +#: ./doc/common/section_keystone-concepts-service-management.xml:11(para) +msgid "keystone-all. Starts both the service and administrative APIs in a single process to provide Catalog, Authorization, and Authentication services for OpenStack." +msgstr "" + +#: ./doc/common/section_keystone-concepts-service-management.xml:17(para) +msgid "Identity Service functions. Each has a pluggable back end that allows different ways to use the particular service. Most support standard back ends like LDAP or SQL." +msgstr "" + +#: ./doc/common/section_keystone-concepts-service-management.xml:23(para) +msgid "The Identity Service also maintains a user that corresponds to each service, such as, a user named nova for the Compute service, and a special service tenant called service." +msgstr "" + +#: ./doc/common/section_keystone-concepts-service-management.xml:28(para) +msgid "For information about how to create services and endpoints, see the OpenStack Admin User Guide." +msgstr "" + +#: ./doc/common/section_cli_openrc.xml:7(title) +msgid "The OpenStack RC file" +msgstr "" + +#: ./doc/common/section_cli_openrc.xml:8(para) +msgid "To set the required environment variables for the OpenStack command-line clients, you must create an environment file. If your OpenStack installation provides it, you can download the file from the OpenStack dashboard as an administrative user or any other user. This project-specific environment file contains the credentials that all OpenStack services use." +msgstr "" + +#: ./doc/common/section_cli_openrc.xml:16(para) +msgid "When you source the file, environment variables are set for your current shell. The variables enable the OpenStack client commands to communicate with the OpenStack services that run in the cloud." +msgstr "" + +#: ./doc/common/section_cli_openrc.xml:21(title) +msgid "Environment variables on Microsoft Windows" +msgstr "" + +#: ./doc/common/section_cli_openrc.xml:22(para) +msgid "Defining environment variables using an environment file is not a common practice on Microsoft Windows. Environment variables are usually defined in the Advanced tab of the System Properties dialog." +msgstr "" + +#: ./doc/common/section_cli_openrc.xml:28(title) +msgid "Download and source the OpenStack RC file" +msgstr "" + +#: ./doc/common/section_cli_openrc.xml:31(para) +msgid "Log in to the OpenStack dashboard, choose the project for which you want to download the OpenStack RC file, and click Access & Security." +msgstr "" + +#: ./doc/common/section_cli_openrc.xml:37(para) +msgid "Click Download OpenStack RC File and save the file." +msgstr "" + +#: ./doc/common/section_cli_openrc.xml:41(para) +msgid "Copy the openrc.sh file to the machine from where you want to run OpenStack commands." +msgstr "" + +#: ./doc/common/section_cli_openrc.xml:44(para) +msgid "For example, copy the file to the machine from where you want to upload an image with a glance client command." +msgstr "" + +#: ./doc/common/section_cli_openrc.xml:49(para) +msgid "On any shell from where you want to run OpenStack commands, source the openrc.sh file for the respective project." +msgstr "" + +#: ./doc/common/section_cli_openrc.xml:53(para) +msgid "In this example, you source the demo-openrc.sh file for the demo project:" +msgstr "" + +#: ./doc/common/section_cli_openrc.xml:59(para) +msgid "When you are prompted for an OpenStack password, enter the password for the user who downloaded the openrc.sh file." +msgstr "" + +#: ./doc/common/section_cli_openrc.xml:66(title) +msgid "Create and source the OpenStack RC file" +msgstr "" + +#: ./doc/common/section_cli_openrc.xml:67(para) +msgid "Alternatively, you can create the openrc.sh file from scratch." +msgstr "" + +#: ./doc/common/section_cli_openrc.xml:72(para) +msgid "Create the openrc.sh file and add the authentication information:" +msgstr "" + +#: ./doc/common/section_cli_openrc.xml:74(replaceable) +msgid "USERNAME" +msgstr "" + +#: ./doc/common/section_cli_openrc.xml:75(replaceable) +msgid "PASSWORD" +msgstr "" + +#: ./doc/common/section_cli_openrc.xml:76(replaceable) +msgid "PROJECT_NAME" +msgstr "" + +#: ./doc/common/section_cli_openrc.xml:77(replaceable) +msgid "https://IDENTITY_HOST:PORT/v2.0" +msgstr "" + +#: ./doc/common/section_cli_openrc.xml:79(replaceable) +msgid "9d792532ffce494583138c495801d164" +msgstr "" + +#: ./doc/common/section_cli_openrc.xml:80(replaceable) +msgid "RegionOne" +msgstr "" + +#: ./doc/common/section_cli_openrc.xml:82(replaceable) +msgid "ADMIN_PASS" +msgstr "" + +#: ./doc/common/section_cli_openrc.xml:84(replaceable) +msgid "controller" +msgstr "" + +#: ./doc/common/section_cli_openrc.xml:87(para) +msgid "On any shell from where you want to run OpenStack commands, source the openrc.sh file for the respective project:" +msgstr "" + +#: ./doc/common/section_cli_openrc.xml:95(para) +msgid "You are not prompted for the password with this method. The password lives in clear text format in the openrc.sh file. Restrict the permissions on this file to avoid security problems. You can also remove the OS_PASSWORD variable from the file, and use the --password parameter with OpenStack client commands." +msgstr "" + +#: ./doc/common/section_cli_openrc.xml:106(title) +msgid "Override environment variable values" +msgstr "" + +#: ./doc/common/section_cli_openrc.xml:107(para) +msgid "When you run OpenStack client commands, you can override some environment variable settings by using the options that are listed at the end of the output. For example, you can override the setting in the openrc.sh file by specifying a password on a command, as follows:" +msgstr "" + +#: ./doc/common/section_cli_openrc.xml:115(para) +msgid "Where password is your password." +msgstr "" + +#: ./doc/common/section_cli_nova_baremetal.xml:5(title) +msgid "Manage bare metal nodes" +msgstr "" + +#: ./doc/common/section_cli_nova_baremetal.xml:6(para) +msgid "The bare metal driver for OpenStack Compute manages provisioning of physical hardware using common cloud APIs and tools such as Orchestration (Heat). The use case for this driver is for single tenant clouds such as a high-performance computing cluster or deploying OpenStack itself. Development efforts are focused on moving the driver out of the Compute code base in the Icehouse release. If you use the bare metal driver, you must create and add a network interface to a bare metal node. Then, you can launch an instance from a bare metal image." +msgstr "" + +#: ./doc/common/section_cli_nova_baremetal.xml:15(para) +msgid "You can list and delete bare metal nodes. When you delete a node, any associated network interfaces are removed. You can list and remove network interfaces that are associated with a bare metal node." +msgstr "" + +#: ./doc/common/section_cli_nova_baremetal.xml:20(title) +msgid "Commands" +msgstr "" + +#: ./doc/common/section_cli_nova_baremetal.xml:22(para) +msgid ". Adds a network interface to a bare metal node." +msgstr "" + +#: ./doc/common/section_cli_nova_baremetal.xml:26(para) +msgid ". Lists network interfaces associated with a bare metal node." +msgstr "" + +#: ./doc/common/section_cli_nova_baremetal.xml:30(para) +msgid ". Removes a network interface from a bare metal node." +msgstr "" + +#: ./doc/common/section_cli_nova_baremetal.xml:34(para) +msgid ". Creates a bare metal node." +msgstr "" + +#: ./doc/common/section_cli_nova_baremetal.xml:38(para) +msgid ". Removes a bare metal node and any associated interfaces." +msgstr "" + +#: ./doc/common/section_cli_nova_baremetal.xml:42(para) +msgid ". Lists available bare metal nodes." +msgstr "" + +#: ./doc/common/section_cli_nova_baremetal.xml:46(para) +msgid ". Shows information about a bare metal node." +msgstr "" + +#: ./doc/common/section_cli_nova_baremetal.xml:52(para) +msgid "Create a bare metal node:" +msgstr "" + +#: ./doc/common/section_cli_nova_baremetal.xml:72(para) +msgid "Add a network interface to the node:" +msgstr "" + +#: ./doc/common/section_cli_nova_baremetal.xml:84(para) +msgid "Launch an instance from a bare metal image:" +msgstr "" + +#: ./doc/common/section_cli_nova_baremetal.xml:95(para) +msgid "List bare metal nodes and interfaces:" +msgstr "" + +#: ./doc/common/section_cli_nova_baremetal.xml:97(para) +msgid "When a node is in use, its status includes the UUID of the instance that runs on it:" +msgstr "" + +#: ./doc/common/section_cli_nova_baremetal.xml:111(para) +msgid "Show details for a bare metal node:" +msgstr "" + +#: ./doc/common/section_cli_nova_baremetal.xml:133(para) +msgid "Set the --availability_zone parameter to specify which zone or node to use to start the server. Separate the zone from the host name with a comma. For example:" +msgstr "" + +#: ./doc/common/section_cli_nova_baremetal.xml:137(replaceable) +msgid "host" +msgstr "" + +#: ./doc/common/section_cli_nova_baremetal.xml:137(replaceable) +msgid "node" +msgstr "" + +#: ./doc/common/section_cli_nova_baremetal.xml:138(para) +msgid "host is optional for the --availability_zone parameter. zone:,node also works." +msgstr "" + +#: ./doc/common/section_compute_config-api.xml:6(title) +msgid "Configure the Compute API" +msgstr "" + +#: ./doc/common/section_compute_config-api.xml:7(para) +msgid "The Compute API, run by the nova-api daemon, is the component of OpenStack Compute that receives and responds to user requests, whether they be direct API calls, or via the CLI tools or dashboard." +msgstr "" + +#: ./doc/common/section_compute_config-api.xml:13(title) +msgid "Configure Compute API password handling" +msgstr "" + +#: ./doc/common/section_compute_config-api.xml:14(para) +msgid "The OpenStack Compute API enables users to specify an administrative password when they create or rebuild a server instance. If the user does not specify a password, a random password is generated and returned in the API response." +msgstr "" + +#: ./doc/common/section_compute_config-api.xml:19(para) +msgid "In practice, how the admin password is handled depends on the hypervisor in use and might require additional configuration of the instance. For example, you might have to install an agent to handle the password setting. If the hypervisor and instance configuration do not support setting a password at server create time, the password that is returned by the create API call is misleading because it was ignored." +msgstr "" + +#: ./doc/common/section_compute_config-api.xml:27(para) +msgid "To prevent this confusion, use the configuration option to disable the return of the admin password for installations that do not support setting instance passwords." +msgstr "" + +#: ./doc/common/section_compute_config-api.xml:34(title) +msgid "Configure Compute API rate limiting" +msgstr "" + +#: ./doc/common/section_compute_config-api.xml:35(para) +msgid "OpenStack Compute supports API rate limiting for the OpenStack API. The rate limiting allows an administrator to configure limits on the type and number of API calls that can be made in a specific time interval." +msgstr "" + +#: ./doc/common/section_compute_config-api.xml:39(para) +msgid "When API rate limits are exceeded, HTTP requests return an error with a status code of 413Request entity too large, and includes an HTTP Retry-After header. The response body includes the error details and the delay before you should retry the request." +msgstr "" + +#: ./doc/common/section_compute_config-api.xml:45(para) +msgid "Rate limiting is not available for the EC2 API." +msgstr "" + +#: ./doc/common/section_compute_config-api.xml:48(title) +msgid "Define limits" +msgstr "" + +#: ./doc/common/section_compute_config-api.xml:49(para) +msgid "To define limits, set these values:" +msgstr "" + +#: ./doc/common/section_compute_config-api.xml:52(para) +msgid "The HTTP method used in the API call, typically one of GET, PUT, POST, or DELETE." +msgstr "" + +#: ./doc/common/section_compute_config-api.xml:57(para) +msgid "A human readable URI that is used as a friendly description of where the limit is applied." +msgstr "" + +#: ./doc/common/section_compute_config-api.xml:62(para) +msgid "A regular expression. The limit is applied to all URIs that match the regular expression and HTTP method." +msgstr "" + +#: ./doc/common/section_compute_config-api.xml:68(para) +msgid "A limit value that specifies the maximum count of units before the limit takes effect." +msgstr "" + +#: ./doc/common/section_compute_config-api.xml:73(para) +msgid "An interval that specifies time frame to which the limit is applied. The interval can be SECOND, MINUTE, HOUR, or DAY." +msgstr "" + +#: ./doc/common/section_compute_config-api.xml:79(para) +msgid "Rate limits are applied in relative order to the HTTP method, going from least to most specific. For example, although the default threshold for POST to */servers is 50 each day, you cannot POST to */servers more than 10 times in a single minute because the rate limits for any POST is 10 each minute." +msgstr "" + +#: ./doc/common/section_compute_config-api.xml:87(title) +msgid "Default limits" +msgstr "" + +#: ./doc/common/section_compute_config-api.xml:88(para) +msgid "Normally, you install OpenStack Compute with the following limits enabled:" +msgstr "" + +#: ./doc/common/section_compute_config-api.xml:91(caption) +msgid "Default API rate limits" +msgstr "" + +#: ./doc/common/section_compute_config-api.xml:94(td) ./doc/common/section_compute_config-api.xml:159(para) +msgid "HTTP method" +msgstr "" + +#: ./doc/common/section_compute_config-api.xml:95(td) +msgid "API URI" +msgstr "" + +#: ./doc/common/section_compute_config-api.xml:96(td) +msgid "API regular expression" +msgstr "" + +#: ./doc/common/section_compute_config-api.xml:97(td) +msgid "Limit" +msgstr "" + +#: ./doc/common/section_compute_config-api.xml:102(td) ./doc/common/section_compute_config-api.xml:108(td) +msgid "POST" +msgstr "" + +#: ./doc/common/section_compute_config-api.xml:103(td) ./doc/common/section_compute_config-api.xml:115(td) ./doc/common/section_compute_config-api.xml:127(td) +msgid "any URI (*)" +msgstr "" + +#: ./doc/common/section_compute_config-api.xml:104(td) ./doc/common/section_compute_config-api.xml:116(td) ./doc/common/section_compute_config-api.xml:128(td) +msgid ".*" +msgstr "" + +#: ./doc/common/section_compute_config-api.xml:105(td) ./doc/common/section_compute_config-api.xml:117(td) +msgid "10 per minute" +msgstr "" + +#: ./doc/common/section_compute_config-api.xml:109(td) +msgid "/servers" +msgstr "" + +#: ./doc/common/section_compute_config-api.xml:110(td) +msgid "^/servers" +msgstr "" + +#: ./doc/common/section_compute_config-api.xml:111(td) +msgid "50 per day" +msgstr "" + +#: ./doc/common/section_compute_config-api.xml:114(td) +msgid "PUT" +msgstr "" + +#: ./doc/common/section_compute_config-api.xml:120(td) +msgid "GET" +msgstr "" + +#: ./doc/common/section_compute_config-api.xml:121(td) +msgid "*changes-since*" +msgstr "" + +#: ./doc/common/section_compute_config-api.xml:122(td) +msgid ".*changes-since.*" +msgstr "" + +#: ./doc/common/section_compute_config-api.xml:123(td) +msgid "3 per minute" +msgstr "" + +#: ./doc/common/section_compute_config-api.xml:126(td) +msgid "DELETE" +msgstr "" + +#: ./doc/common/section_compute_config-api.xml:129(td) +msgid "100 per minute" +msgstr "" + +#: ./doc/common/section_compute_config-api.xml:135(title) +msgid "Configure and change limits" +msgstr "" + +#: ./doc/common/section_compute_config-api.xml:136(para) +msgid "As part of the WSGI pipeline, the etc/nova/api-paste.ini file defines the actual limits." +msgstr "" + +#: ./doc/common/section_compute_config-api.xml:139(para) +msgid "To enable limits, include the ' filter in the API pipeline specification. If the filter is removed from the pipeline, limiting is disabled. You must also define the rate limit filter. The lines appear as follows:" +msgstr "" + +#: ./doc/common/section_compute_config-api.xml:153(para) +msgid "To modify the limits, add a limits specification to the [filter:ratelimit] section of the file. Specify the limits in this order:" +msgstr "" + +#: ./doc/common/section_compute_config-api.xml:162(para) +msgid "friendly URI" +msgstr "" + +#: ./doc/common/section_compute_config-api.xml:165(para) +msgid "regex" +msgstr "" + +#: ./doc/common/section_compute_config-api.xml:168(para) +msgid "limit" +msgstr "" + +#: ./doc/common/section_compute_config-api.xml:171(para) +msgid "interval" +msgstr "" + +#: ./doc/common/section_compute_config-api.xml:174(para) +msgid "The following example shows the default rate-limiting values:" +msgstr "" + +#: ./doc/common/section_compute_config-api.xml:182(para) +msgid "The following table lists the Compute API configuration options:" +msgstr "" + +#: ./doc/common/section_getstart_block-storage.xml:5(title) +msgid "Block Storage Service" +msgstr "" + +#: ./doc/common/section_getstart_block-storage.xml:6(para) +msgid "The Block Storage Service enables management of volumes, volume snapshots, and volume types. It includes the following components:" +msgstr "" + +#: ./doc/common/section_getstart_block-storage.xml:11(para) +msgid "cinder-api. Accepts API requests and routes them to cinder-volume for action." +msgstr "" + +#: ./doc/common/section_getstart_block-storage.xml:17(para) +msgid "cinder-volume. Responds to requests to read from and write to the Block Storage database to maintain state, interacting with other processes (like cinder-scheduler) through a message queue and directly upon block storage providing hardware or software. It can interact with a variety of storage providers through a driver architecture." +msgstr "" + +#: ./doc/common/section_getstart_block-storage.xml:27(para) +msgid "cinder-scheduler daemon. Like the nova-scheduler, picks the optimal block storage provider node on which to create the volume." +msgstr "" + +#: ./doc/common/section_getstart_block-storage.xml:34(para) +msgid "Messaging queue. Routes information between the Block Storage Service processes." +msgstr "" + +#: ./doc/common/section_getstart_block-storage.xml:38(para) +msgid "The Block Storage Service interacts with Compute to provide volumes for instances." +msgstr "" + +#: ./doc/common/section_getstart_image.xml:5(title) +msgid "Image Service overview" +msgstr "" + +#: ./doc/common/section_getstart_image.xml:6(para) +msgid "The Image Service includes the following components:" +msgstr "" + +#: ./doc/common/section_getstart_image.xml:10(para) +msgid "glance-api. Accepts Image API calls for image discovery, retrieval, and storage." +msgstr "" + +#: ./doc/common/section_getstart_image.xml:15(para) +msgid "glance-registry. Stores, processes, and retrieves metadata about images. Metadata includes items such as size and type." +msgstr "" + +#: ./doc/common/section_getstart_image.xml:21(para) +msgid "Database. Stores image metadata. You can choose your database depending on your preference. Most deployments use MySQL or SQlite." +msgstr "" + +#: ./doc/common/section_getstart_image.xml:26(para) +msgid "Storage repository for image files. In , the Object Storage Service is the image repository. However, you can configure a different repository. The Image Service supports normal file systems, RADOS block devices, Amazon S3, and HTTP. Some choices provide only read-only usage." +msgstr "" + +#: ./doc/common/section_getstart_image.xml:34(para) +msgid "A number of periodic processes run on the Image Service to support caching. Replication services ensures consistency and availability through the cluster. Other periodic processes include auditors, updaters, and reapers." +msgstr "" + +#: ./doc/common/section_getstart_image.xml:38(para) +msgid "As shown in , the Image Service is central to the overall IaaS picture. It accepts API requests for images or image metadata from end users or Compute components and can store its disk files in the Object Storage Service." +msgstr "" + +#. When image changes, this message will be marked fuzzy or untranslated for you. +#. It doesn't matter what you translate it to: it's not used at all. +#: ./doc/common/section_objectstorage-characteristics.xml:50(None) +msgid "@@image: '../common/figures/objectstorage.png'; md5=e26e374ace84070f5fed24e73adcd562" +msgstr "" + +#. ... Old module003-ch003-obj-store-capabilities edited, renamed, and stored in doc/common for use by both Cloud Admin and Operator Training Guides... +#: ./doc/common/section_objectstorage-characteristics.xml:8(title) +msgid "Object Storage characteristics" +msgstr "" + +#: ./doc/common/section_objectstorage-characteristics.xml:9(para) +msgid "The key characteristics of Object Storage are that:" +msgstr "" + +#: ./doc/common/section_objectstorage-characteristics.xml:12(para) +msgid "All objects stored in Object Storage have a URL." +msgstr "" + +#: ./doc/common/section_objectstorage-characteristics.xml:15(para) +msgid "All objects stored are replicated 3✕ in as-unique-as-possible zones, which can be defined as a group of drives, a node, a rack, and so on." +msgstr "" + +#: ./doc/common/section_objectstorage-characteristics.xml:19(para) +msgid "All objects have their own metadata." +msgstr "" + +#: ./doc/common/section_objectstorage-characteristics.xml:22(para) +msgid "Developers interact with the object storage system through a RESTful HTTP API." +msgstr "" + +#: ./doc/common/section_objectstorage-characteristics.xml:26(para) +msgid "Object data can be located anywhere in the cluster." +msgstr "" + +#: ./doc/common/section_objectstorage-characteristics.xml:29(para) +msgid "The cluster scales by adding additional nodes without sacrificing performance, which allows a more cost-effective linear storage expansion than fork-lift upgrades." +msgstr "" + +#: ./doc/common/section_objectstorage-characteristics.xml:34(para) +msgid "Data doesn't have to be migrate to an entirely new storage system." +msgstr "" + +#: ./doc/common/section_objectstorage-characteristics.xml:37(para) +msgid "New nodes can be added to the cluster without downtime." +msgstr "" + +#: ./doc/common/section_objectstorage-characteristics.xml:40(para) +msgid "Failed nodes and disks can be swapped out without downtime." +msgstr "" + +#: ./doc/common/section_objectstorage-characteristics.xml:43(para) +msgid "It runs on industry-standard hardware, such as Dell, HP, and Supermicro." +msgstr "" + +#: ./doc/common/section_objectstorage-characteristics.xml:54(para) +msgid "Developers can either write directly to the Swift API or use one of the many client libraries that exist for all of the popular programming languages, such as Java, Python, Ruby, and C#. Amazon S3 and RackSpace Cloud Files users should be very familiar with Object Storage. Users new to object storage systems will have to adjust to a different approach and mindset than those required for a traditional filesystem." +msgstr "" + +#: ./doc/common/section_dashboard_sessions.xml:6(title) +msgid "Set up session storage for the dashboard" +msgstr "" + +#: ./doc/common/section_dashboard_sessions.xml:7(para) +msgid "The dashboard uses Django sessions framework to handle user session data. However, you can use any available session back end. You customize the session back end through the SESSION_ENGINE setting in your local_settings file (on Fedora/RHEL/CentOS: /etc/openstack-dashboard/local_settings, on Ubuntu and Debian: /etc/openstack-dashboard/local_settings.py and on openSUSE: /usr/share/openstack-dashboard/openstack_dashboard/local/local_settings.py)." +msgstr "" + +#: ./doc/common/section_dashboard_sessions.xml:18(para) +msgid "The following sections describe the pros and cons of each option as it pertains to deploying the dashboard." +msgstr "" + +#: ./doc/common/section_dashboard_sessions.xml:21(title) +msgid "Local memory cache" +msgstr "" + +#: ./doc/common/section_dashboard_sessions.xml:22(para) +msgid "Local memory storage is the quickest and easiest session back end to set up, as it has no external dependencies whatsoever. It has the following significant drawbacks:" +msgstr "" + +#: ./doc/common/section_dashboard_sessions.xml:28(para) +msgid "No shared storage across processes or workers." +msgstr "" + +#: ./doc/common/section_dashboard_sessions.xml:32(para) +msgid "No persistence after a process terminates." +msgstr "" + +#: ./doc/common/section_dashboard_sessions.xml:36(para) +msgid "The local memory back end is enabled as the default for Horizon solely because it has no dependencies. It is not recommended for production use, or even for serious development work. Enabled by:" +msgstr "" + +#: ./doc/common/section_dashboard_sessions.xml:47(title) +msgid "Key-value stores" +msgstr "" + +#: ./doc/common/section_dashboard_sessions.xml:48(para) +msgid "You can use applications such as Memcached or Redis for external caching. These applications offer persistence and shared storage and are useful for small-scale deployments and/or development." +msgstr "" + +#: ./doc/common/section_dashboard_sessions.xml:53(title) +msgid "Memcached" +msgstr "" + +#: ./doc/common/section_dashboard_sessions.xml:54(para) +msgid "Memcached is an high-performance and distributed memory object caching system providing in-memory key-value store for small chunks of arbitrary data." +msgstr "" + +#: ./doc/common/section_dashboard_sessions.xml:56(para) ./doc/common/section_dashboard_sessions.xml:76(para) +msgid "Requirements:" +msgstr "" + +#: ./doc/common/section_dashboard_sessions.xml:59(para) +msgid "Memcached service running and accessible." +msgstr "" + +#: ./doc/common/section_dashboard_sessions.xml:62(para) +msgid "Python module python-memcached installed." +msgstr "" + +#: ./doc/common/section_dashboard_sessions.xml:65(para) ./doc/common/section_dashboard_sessions.xml:85(para) +msgid "Enabled by:" +msgstr "" + +#: ./doc/common/section_dashboard_sessions.xml:73(title) +msgid "Redis" +msgstr "" + +#: ./doc/common/section_dashboard_sessions.xml:74(para) +msgid "Redis is an open source, BSD licensed, advanced key-value store. It is often referred to as a data structure server." +msgstr "" + +#: ./doc/common/section_dashboard_sessions.xml:79(para) +msgid "Redis service running and accessible." +msgstr "" + +#: ./doc/common/section_dashboard_sessions.xml:82(para) +msgid "Python modules redis and django-redis installed." +msgstr "" + +#: ./doc/common/section_dashboard_sessions.xml:99(title) +msgid "Initialize and configure the database" +msgstr "" + +#: ./doc/common/section_dashboard_sessions.xml:100(para) +msgid "Database-backed sessions are scalable, persistent, and can be made high-concurrency and highly-available." +msgstr "" + +#: ./doc/common/section_dashboard_sessions.xml:102(para) +msgid "However, database-backed sessions are one of the slower session storages and incur a high overhead under heavy usage. Proper configuration of your database deployment can also be a substantial undertaking and is far beyond the scope of this documentation." +msgstr "" + +#: ./doc/common/section_dashboard_sessions.xml:109(para) +msgid "Start the mysql command line client:" +msgstr "" + +#: ./doc/common/section_dashboard_sessions.xml:113(para) +msgid "Enter the MySQL root user's password when prompted." +msgstr "" + +#: ./doc/common/section_dashboard_sessions.xml:117(para) +msgid "To configure the MySQL database, create the dash database:" +msgstr "" + +#: ./doc/common/section_dashboard_sessions.xml:122(para) +msgid "Create a MySQL user for the newly-created dash database that has full control of the database. Replace DASH_DBPASS with a password for the new user:" +msgstr "" + +#: ./doc/common/section_dashboard_sessions.xml:126(replaceable) ./doc/common/section_dashboard_sessions.xml:127(replaceable) ./doc/common/section_dashboard_sessions.xml:147(replaceable) +msgid "DASH_DBPASS" +msgstr "" + +#: ./doc/common/section_dashboard_sessions.xml:130(para) +msgid "Enter quit at the mysql> prompt to exit MySQL." +msgstr "" + +#: ./doc/common/section_dashboard_sessions.xml:134(para) +msgid "In the local_settings file (on Fedora/RHEL/CentOS: /etc/openstack-dashboard/local_settings, on Ubuntu/Debian: /etc/openstack-dashboard/local_settings.py and on openSUSE: /usr/share/openstack-dashboard/openstack_dashboard/local/local_settings.py), change these options:" +msgstr "" + +#: ./doc/common/section_dashboard_sessions.xml:154(para) +msgid "After configuring the local_settings as shown, you can run the command to populate this newly-created database." +msgstr "" + +#: ./doc/common/section_dashboard_sessions.xml:159(para) +msgid "As a result, the following output is returned:" +msgstr "" + +#: ./doc/common/section_dashboard_sessions.xml:167(para) +msgid "On Ubuntu: If you want to avoid a warning when you restart apache2, create a blackhole directory in the dashboard directory, as follows:" +msgstr "" + +#: ./doc/common/section_dashboard_sessions.xml:173(para) +msgid "Restart Apache to pick up the default site and symbolic link settings:" +msgstr "" + +#: ./doc/common/section_dashboard_sessions.xml:178(para) +msgid "On Fedora/RHEL/CentOS: " +msgstr "" + +#: ./doc/common/section_dashboard_sessions.xml:187(para) +msgid "On Ubuntu, restart the nova-api service to ensure that the API server can connect to the dashboard without error:" +msgstr "" + +#: ./doc/common/section_dashboard_sessions.xml:195(title) +msgid "Cached database" +msgstr "" + +#: ./doc/common/section_dashboard_sessions.xml:196(para) +msgid "To mitigate the performance issues of database queries, you can use the Django cached_db session back end, which utilizes both your database and caching infrastructure to perform write-through caching and efficient retrieval." +msgstr "" + +#: ./doc/common/section_dashboard_sessions.xml:200(para) +msgid "Enable this hybrid setting by configuring both your database and cache, as discussed previously. Then, set the following value:" +msgstr "" + +#: ./doc/common/section_dashboard_sessions.xml:206(title) +msgid "Cookies" +msgstr "" + +#: ./doc/common/section_dashboard_sessions.xml:207(para) +msgid "If you use Django 1.4 or later, the signed_cookies back end avoids server load and scaling problems." +msgstr "" + +#: ./doc/common/section_dashboard_sessions.xml:209(para) +msgid "This back end stores session data in a cookie, which is stored by the user’s browser. The back end uses a cryptographic signing technique to ensure session data is not tampered with during transport. This is not the same as encryption; session data is still readable by an attacker." +msgstr "" + +#: ./doc/common/section_dashboard_sessions.xml:215(para) +msgid "The pros of this engine are that it requires no additional dependencies or infrastructure overhead, and it scales indefinitely as long as the quantity of session data being stored fits into a normal cookie." +msgstr "" + +#: ./doc/common/section_dashboard_sessions.xml:219(para) +msgid "The biggest downside is that it places session data into storage on the user’s machine and transports it over the wire. It also limits the quantity of session data that can be stored." +msgstr "" + +#: ./doc/common/section_dashboard_sessions.xml:223(para) +msgid "See the Django cookie-based sessions documentation." +msgstr "" + +#: ./doc/common/section_objectstorage-troubleshoot.xml:6(title) +msgid "Troubleshoot Object Storage" +msgstr "" + +#: ./doc/common/section_objectstorage-troubleshoot.xml:7(para) +msgid "For Object Storage, everything is logged in /var/log/syslog (or messages on some distros). Several settings enable further customization of logging, such as log_name, log_facility, and log_level, within the object server configuration files." +msgstr "" + +#: ./doc/common/section_objectstorage-troubleshoot.xml:11(title) +msgid "Drive failure" +msgstr "" + +#: ./doc/common/section_objectstorage-troubleshoot.xml:12(para) +msgid "In the event that a drive has failed, the first step is to make sure the drive is unmounted. This will make it easier for Object Storage to work around the failure until it has been resolved. If the drive is going to be replaced immediately, then it is just best to replace the drive, format it, remount it, and let replication fill it up." +msgstr "" + +#: ./doc/common/section_objectstorage-troubleshoot.xml:16(para) +msgid "If the drive can’t be replaced immediately, then it is best to leave it unmounted, and remove the drive from the ring. This will allow all the replicas that were on that drive to be replicated elsewhere until the drive is replaced. Once the drive is replaced, it can be re-added to the ring." +msgstr "" + +#: ./doc/common/section_objectstorage-troubleshoot.xml:20(para) +msgid "You can look at error messages in /var/log/kern.log for hints of drive failure." +msgstr "" + +#: ./doc/common/section_objectstorage-troubleshoot.xml:23(title) +msgid "Server failure" +msgstr "" + +#: ./doc/common/section_objectstorage-troubleshoot.xml:24(para) +msgid "If a server is having hardware issues, it is a good idea to make sure the Object Storage services are not running. This will allow Object Storage to work around the failure while you troubleshoot." +msgstr "" + +#: ./doc/common/section_objectstorage-troubleshoot.xml:27(para) +msgid "If the server just needs a reboot, or a small amount of work that should only last a couple of hours, then it is probably best to let Object Storage work around the failure and get the machine fixed and back online. When the machine comes back online, replication will make sure that anything that is missing during the downtime will get updated." +msgstr "" + +#: ./doc/common/section_objectstorage-troubleshoot.xml:32(para) +msgid "If the server has more serious issues, then it is probably best to remove all of the server’s devices from the ring. Once the server has been repaired and is back online, the server’s devices can be added back into the ring. It is important that the devices are reformatted before putting them back into the ring as it is likely to be responsible for a different set of partitions than before." +msgstr "" + +#: ./doc/common/section_objectstorage-troubleshoot.xml:40(title) +msgid "Detect failed drives" +msgstr "" + +#: ./doc/common/section_objectstorage-troubleshoot.xml:41(para) +msgid "It has been our experience that when a drive is about to fail, error messages will spew into /var/log/kern.log. There is a script called swift-drive-audit that can be run via cron to watch for bad drives. If errors are detected, it will unmount the bad drive, so that Object Storage can work around it. The script takes a configuration file with the following settings:" +msgstr "" + +#: ./doc/common/section_objectstorage-troubleshoot.xml:47(para) +msgid "This script has only been tested on Ubuntu 10.04, so if you are using a different distro or OS, some care should be taken before using in production." +msgstr "" + +#: ./doc/common/section_objectstorage-troubleshoot.xml:52(title) +msgid "Emergency recovery of ring builder files" +msgstr "" + +#: ./doc/common/section_objectstorage-troubleshoot.xml:53(para) +msgid "You should always keep a backup of Swift ring builder files. However, if an emergency occurs, this procedure may assist in returning your cluster to an operational state." +msgstr "" + +#: ./doc/common/section_objectstorage-troubleshoot.xml:56(para) +msgid "Using existing Swift tools, there is no way to recover a builder file from a ring.gz file. However, if you have a knowledge of Python, it is possible to construct a builder file that is pretty close to the one you have lost. The following is what you will need to do." +msgstr "" + +#: ./doc/common/section_objectstorage-troubleshoot.xml:61(para) +msgid "This procedure is a last-resort for emergency circumstances—it requires knowledge of the swift python code and may not succeed." +msgstr "" + +#: ./doc/common/section_objectstorage-troubleshoot.xml:64(para) +msgid "First, load the ring and a new ringbuilder object in a Python REPL:" +msgstr "" + +#: ./doc/common/section_objectstorage-troubleshoot.xml:67(para) +msgid "Now, start copying the data we have in the ring into the builder." +msgstr "" + +#: ./doc/common/section_objectstorage-troubleshoot.xml:84(para) +msgid "This is the extent of the recoverable fields. For min_part_hours you'll either have to remember what the value you used was, or just make up a new one." +msgstr "" + +#: ./doc/common/section_objectstorage-troubleshoot.xml:89(para) +msgid "Try some validation: if this doesn't raise an exception, you may feel some hope. Not too much, though." +msgstr "" + +#: ./doc/common/section_objectstorage-troubleshoot.xml:92(para) +msgid "Save the builder." +msgstr "" + +#: ./doc/common/section_objectstorage-troubleshoot.xml:96(para) +msgid "You should now have a file called 'account.builder' in the current working directory. Next, run swift-ring-builder account.builder write_ring and compare the new account.ring.gz to the account.ring.gz that you started from. They probably won't be byte-for-byte identical, but if you load them up in a REPL and their _replica2part2dev_id and devs attributes are the same (or nearly so), then you're in good shape." +msgstr "" + +#: ./doc/common/section_objectstorage-troubleshoot.xml:103(para) +msgid "Next, repeat the procedure for container.ring.gz and object.ring.gz, and you might get usable builder files." +msgstr "" + +#: ./doc/common/tables/nova-cells.xml:8(caption) +msgid "Description of configuration options for cells" +msgstr "" + +#: ./doc/common/tables/nova-cells.xml:13(th) ./doc/common/tables/glance-policy.xml:13(th) ./doc/common/tables/neutron-mlnx.xml:13(th) ./doc/common/tables/nova-ipv6.xml:13(th) ./doc/common/tables/cinder-eqlx.xml:13(th) ./doc/common/tables/swift-object-expirer-filter-catch_errors.xml:12(th) ./doc/common/tables/swift-object-expirer-filter-cache.xml:12(th) ./doc/common/tables/swift-proxy-server-filter-cache.xml:12(th) ./doc/common/tables/neutron-ml2_l2pop.xml:13(th) ./doc/common/tables/glance-qpid.xml:13(th) ./doc/common/tables/swift-container-server-DEFAULT.xml:12(th) ./doc/common/tables/nova-volumes.xml:13(th) ./doc/common/tables/glance-gridfs.xml:13(th) ./doc/common/tables/neutron-ml2_arista.xml:13(th) ./doc/common/tables/glance-filesystem.xml:13(th) ./doc/common/tables/swift-container-server-container-updater.xml:12(th) ./doc/common/tables/cinder-storage_gpfs.xml:13(th) ./doc/common/tables/nova-docker.xml:13(th) ./doc/common/tables/cinder-nexenta_iscsi.xml:13(th) ./doc/common/tables/nova-tilera.xml:13(th) ./doc/common/tables/nova-ca.xml:13(th) ./doc/common/tables/swift-account-server-filter-recon.xml:12(th) ./doc/common/tables/cinder-huawei.xml:13(th) ./doc/common/tables/swift-container-server-container-replicator.xml:12(th) ./doc/common/tables/nova-glance.xml:13(th) ./doc/common/tables/nova-neutron.xml:13(th) ./doc/common/tables/cinder-backups_ceph.xml:13(th) ./doc/common/tables/swift-proxy-server-filter-name_check.xml:12(th) ./doc/common/tables/nova-metadata.xml:13(th) ./doc/common/tables/glance-s3.xml:13(th) ./doc/common/tables/neutron-kombu.xml:13(th) ./doc/common/tables/swift-proxy-server-filter-ratelimit.xml:12(th) ./doc/common/tables/cinder-block-device.xml:13(th) ./doc/common/tables/cinder-zones.xml:13(th) ./doc/common/tables/cinder-netapp_7mode_iscsi.xml:13(th) ./doc/common/tables/swift-container-server-container-sync.xml:12(th) ./doc/common/tables/neutron-common.xml:13(th) ./doc/common/tables/swift-object-server-object-auditor.xml:12(th) ./doc/common/tables/neutron-openvswitch_agent.xml:13(th) ./doc/common/tables/cinder-compute.xml:13(th) ./doc/common/tables/cinder-lvm.xml:13(th) ./doc/common/tables/cinder-storage_nfs.xml:13(th) ./doc/common/tables/neutron-plumgrid.xml:13(th) ./doc/common/tables/nova-hypervisor.xml:13(th) ./doc/common/tables/swift-proxy-server-filter-tempurl.xml:12(th) ./doc/common/tables/cinder-quota.xml:13(th) ./doc/common/tables/swift-proxy-server-filter-healthcheck.xml:12(th) ./doc/common/tables/swift-object-expirer-DEFAULT.xml:12(th) ./doc/common/tables/nova-console.xml:13(th) ./doc/common/tables/swift-swift-bench-bench.xml:12(th) ./doc/common/tables/nova-common.xml:13(th) ./doc/common/tables/swift-object-server-object-updater.xml:12(th) ./doc/common/tables/glance-zmq.xml:13(th) ./doc/common/tables/swift-proxy-server-filter-account-quotas.xml:12(th) ./doc/common/tables/swift-proxy-server-app-proxy-server.xml:12(th) ./doc/common/tables/nova-keymgr.xml:13(th) ./doc/common/tables/neutron-api.xml:13(th) ./doc/common/tables/nova-testing.xml:13(th) ./doc/common/tables/cinder-backups.xml:13(th) ./doc/common/tables/swift-container-server-pipeline-main.xml:12(th) ./doc/common/tables/swift-rsyncd-object.xml:12(th) ./doc/common/tables/nova-s3.xml:13(th) ./doc/common/tables/neutron-openvswitch.xml:13(th) ./doc/common/tables/nova-zookeeper.xml:13(th) ./doc/common/tables/cinder-rpc.xml:13(th) ./doc/common/tables/cinder-api.xml:13(th) ./doc/common/tables/cinder-windows.xml:13(th) ./doc/common/tables/swift-object-server-pipeline-main.xml:12(th) ./doc/common/tables/cinder-san.xml:13(th) ./doc/common/tables/swift-account-server-app-account-server.xml:12(th) ./doc/common/tables/cinder-keymgr.xml:13(th) ./doc/common/tables/nova-db.xml:13(th) ./doc/common/tables/neutron-ml2_vxlan.xml:13(th) ./doc/common/tables/glance-logging.xml:13(th) ./doc/common/tables/glance-wsgi.xml:13(th) ./doc/common/tables/nova-periodic.xml:13(th) ./doc/common/tables/swift-account-server-filter-healthcheck.xml:12(th) ./doc/common/tables/cinder-images.xml:13(th) ./doc/common/tables/swift-container-server-app-container-server.xml:12(th) ./doc/common/tables/swift-proxy-server-filter-slo.xml:12(th) ./doc/common/tables/neutron-wsgi.xml:13(th) ./doc/common/tables/neutron-scheduler.xml:13(th) ./doc/common/tables/glance-rbd.xml:13(th) ./doc/common/tables/neutron-metadata.xml:13(th) ./doc/common/tables/cinder-hp3par.xml:13(th) ./doc/common/tables/cinder-storage_ceph.xml:13(th) ./doc/common/tables/nova-livemigration.xml:13(th) ./doc/common/tables/nova-ldap.xml:13(th) ./doc/common/tables/nova-fping.xml:13(th) ./doc/common/tables/neutron-securitygroups.xml:13(th) ./doc/common/tables/cinder-netapp_cdot_iscsi.xml:13(th) ./doc/common/tables/nova-ec2.xml:13(th) ./doc/common/tables/swift-account-server-account-auditor.xml:12(th) ./doc/common/tables/swift-object-server-DEFAULT.xml:12(th) ./doc/common/tables/cinder-nexenta_nfs.xml:13(th) ./doc/common/tables/swift-proxy-server-filter-bulk.xml:12(th) ./doc/common/tables/nova-policy.xml:13(th) ./doc/common/tables/neutron-logging.xml:13(th) ./doc/common/tables/glance-rpc.xml:13(th) ./doc/common/tables/nova-authentication.xml:13(th) ./doc/common/tables/cinder-vmware.xml:13(th) ./doc/common/tables/glance-sheepdog.xml:13(th) ./doc/common/tables/neutron-qpid.xml:13(th) ./doc/common/tables/neutron-hyperv_agent.xml:13(th) ./doc/common/tables/glance-swift.xml:13(th) ./doc/common/tables/swift-account-server-DEFAULT.xml:12(th) ./doc/common/tables/neutron-bigswitch.xml:13(th) ./doc/common/tables/nova-libvirt.xml:13(th) ./doc/common/tables/neutron-lbaas.xml:13(th) ./doc/common/tables/cinder-backups_swift.xml:13(th) ./doc/common/tables/neutron-ml2_cisco.xml:13(th) ./doc/common/tables/nova-pci.xml:13(th) ./doc/common/tables/swift-proxy-server-filter-proxy-logging.xml:12(th) ./doc/common/tables/neutron-varmour.xml:13(th) ./doc/common/tables/glance-imagecache.xml:13(th) ./doc/common/tables/swift-rsyncd-account.xml:12(th) ./doc/common/tables/cinder-storage.xml:13(th) ./doc/common/tables/nova-vpn.xml:13(th) ./doc/common/tables/nova-wsgi.xml:13(th) ./doc/common/tables/cinder-storage_glusterfs.xml:13(th) ./doc/common/tables/swift-container-server-filter-healthcheck.xml:12(th) ./doc/common/tables/nova-availabilityzones.xml:13(th) ./doc/common/tables/nova-vnc.xml:13(th) ./doc/common/tables/swift-swift-swift-constraints.xml:12(th) ./doc/common/tables/neutron-cisco.xml:13(th) ./doc/common/tables/nova-hyperv.xml:13(th) ./doc/common/tables/swift-object-server-filter-recon.xml:12(th) ./doc/common/tables/cinder-coraid.xml:13(th) ./doc/common/tables/swift-container-server-container-auditor.xml:12(th) ./doc/common/tables/swift-proxy-server-filter-catch_errors.xml:12(th) ./doc/common/tables/nova-vmware.xml:13(th) ./doc/common/tables/nova-logging.xml:13(th) ./doc/common/tables/nova-xen.xml:13(th) ./doc/common/tables/swift-proxy-server-filter-list-endpoints.xml:12(th) ./doc/common/tables/neutron-nicira.xml:13(th) ./doc/common/tables/swift-memcache-memcache.xml:12(th) ./doc/common/tables/swift-proxy-server-filter-keystoneauth.xml:12(th) ./doc/common/tables/neutron-ml2.xml:13(th) ./doc/common/tables/neutron-linuxbridge.xml:13(th) ./doc/common/tables/cinder-netapp_7mode_nfs.xml:13(th) ./doc/common/tables/glance-common.xml:13(th) ./doc/common/tables/nova-network.xml:13(th) ./doc/common/tables/cinder-scality.xml:13(th) ./doc/common/tables/neutron-notifier.xml:13(th) ./doc/common/tables/cinder-common.xml:13(th) ./doc/common/tables/nova-trustedcomputing.xml:13(th) ./doc/common/tables/neutron-ml2_flat.xml:13(th) ./doc/common/tables/nova-configdrive.xml:13(th) ./doc/common/tables/cinder-database.xml:13(th) ./doc/common/tables/neutron-rpc.xml:13(th) ./doc/common/tables/nova-zeromq.xml:13(th) ./doc/common/tables/glance-testing.xml:13(th) ./doc/common/tables/swift-proxy-server-filter-tempauth.xml:12(th) ./doc/common/tables/glance-registry.xml:13(th) ./doc/common/tables/ldap-keystone-conf.xml:10(th) ./doc/common/tables/swift-object-server-object-replicator.xml:12(th) ./doc/common/tables/swift-dispersion-dispersion.xml:12(th) ./doc/common/tables/swift-account-server-account-replicator.xml:12(th) ./doc/common/tables/neutron-fwaas.xml:13(th) ./doc/common/tables/glance-rabbitmq.xml:13(th) ./doc/common/tables/cinder-backups_tsm.xml:13(th) ./doc/common/tables/nova-qpid.xml:13(th) ./doc/common/tables/cinder-connection.xml:13(th) ./doc/common/tables/swift-proxy-server-filter-authtoken.xml:12(th) ./doc/common/tables/neutron-zeromq.xml:13(th) ./doc/common/tables/neutron-vpn.xml:13(th) ./doc/common/tables/cinder-log.xml:13(th) ./doc/common/tables/neutron-agent.xml:13(th) ./doc/common/tables/neutron-ryu.xml:13(th) ./doc/common/tables/swift-object-server-app-object-server.xml:12(th) ./doc/common/tables/neutron-policy.xml:13(th) ./doc/common/tables/swift-proxy-server-DEFAULT.xml:12(th) ./doc/common/tables/swift-proxy-server-filter-staticweb.xml:12(th) ./doc/common/tables/swift-object-expirer-app-proxy-server.xml:12(th) ./doc/common/tables/neutron-meta.xml:13(th) ./doc/common/tables/neutron-ssl.xml:13(th) ./doc/common/tables/nova-scheduling.xml:13(th) ./doc/common/tables/swift-drive-audit-drive-audit.xml:12(th) ./doc/common/tables/swift-container-server-filter-recon.xml:12(th) ./doc/common/tables/neutron-db.xml:13(th) ./doc/common/tables/neutron-brocade.xml:13(th) ./doc/common/tables/swift-object-expirer-pipeline-main.xml:12(th) ./doc/common/tables/neutron-linuxbridge_agent.xml:13(th) ./doc/common/tables/cinder-xiv.xml:13(th) ./doc/common/tables/neutron-rabbitmq.xml:13(th) ./doc/common/tables/swift-proxy-server-filter-container-quotas.xml:12(th) ./doc/common/tables/swift-swift-swift-hash.xml:12(th) ./doc/common/tables/cinder-auth.xml:13(th) ./doc/common/tables/nova-kombu.xml:13(th) ./doc/common/tables/swift-proxy-server-filter-formpost.xml:12(th) ./doc/common/tables/cinder-hds.xml:13(th) ./doc/common/tables/nova-spice.xml:13(th) ./doc/common/tables/neutron-midonet.xml:13(th) ./doc/common/tables/cinder-storwize.xml:13(th) ./doc/common/tables/cinder-solidfire.xml:13(th) ./doc/common/tables/glance-ssl.xml:13(th) ./doc/common/tables/nova-apiv3.xml:13(th) ./doc/common/tables/glance-db.xml:13(th) ./doc/common/tables/nova-api.xml:13(th) ./doc/common/tables/swift-rsyncd-container.xml:12(th) ./doc/common/tables/cinder-san-solaris.xml:13(th) ./doc/common/tables/cinder-netapp_cdot_nfs.xml:13(th) ./doc/common/tables/swift-object-server-filter-healthcheck.xml:12(th) ./doc/common/tables/glance-paste.xml:13(th) ./doc/common/tables/neutron-quotas.xml:13(th) ./doc/common/tables/nova-rpc.xml:13(th) ./doc/common/tables/nova-baremetal.xml:13(th) ./doc/common/tables/swift-account-server-pipeline-main.xml:12(th) ./doc/common/tables/glance-api.xml:13(th) ./doc/common/tables/cinder-scheduler.xml:13(th) ./doc/common/tables/neutron-ml2_ncs.xml:13(th) ./doc/common/tables/neutron-nec.xml:13(th) ./doc/common/tables/neutron-testing.xml:13(th) ./doc/common/tables/swift-object-expirer-object-expirer.xml:12(th) ./doc/common/tables/glance-cinder.xml:13(th) ./doc/common/tables/nova-redis.xml:13(th) ./doc/common/tables/neutron-embrane.xml:13(th) ./doc/common/tables/swift-proxy-server-pipeline-main.xml:12(th) ./doc/common/tables/nova-upgrade_levels.xml:13(th) ./doc/common/tables/swift-proxy-server-filter-cname_lookup.xml:12(th) ./doc/common/tables/nova-rabbitmq.xml:13(th) ./doc/common/tables/cinder-zadara.xml:13(th) ./doc/common/tables/swift-account-server-account-reaper.xml:12(th) ./doc/common/tables/nova-quota.xml:13(th) ./doc/common/tables/nova-conductor.xml:13(th) ./doc/common/tables/nova-compute.xml:13(th) ./doc/common/tables/swift-proxy-server-filter-domain_remap.xml:12(th) ./doc/common/tables/neutron-hyperv.xml:13(th) ./doc/common/tables/cinder-storage_xen.xml:13(th) ./doc/common/tables/nova-xvpnvncproxy.xml:13(th) +msgid "Configuration option = Default value" +msgstr "" + +#: ./doc/common/tables/nova-cells.xml:19(th) ./doc/common/tables/nova-db.xml:34(th) ./doc/common/tables/nova-scheduling.xml:114(th) ./doc/common/tables/nova-rpc.xml:62(th) ./doc/common/tables/nova-upgrade_levels.xml:19(th) ./doc/common/tables/nova-quota.xml:82(th) +msgid "[cells]" +msgstr "" + +#: ./doc/common/tables/nova-cells.xml:22(td) +msgid "call_timeout = 60" +msgstr "" + +#: ./doc/common/tables/nova-cells.xml:23(td) +msgid "(IntOpt) Seconds to wait for response from a call to a cell." +msgstr "" + +#: ./doc/common/tables/nova-cells.xml:26(td) +msgid "capabilities = hypervisor=xenserver;kvm, os=linux;windows" +msgstr "" + +#: ./doc/common/tables/nova-cells.xml:27(td) +msgid "(ListOpt) Key/Multi-value list with the capabilities of the cell" +msgstr "" + +#: ./doc/common/tables/nova-cells.xml:30(td) +msgid "cell_type = compute" +msgstr "" + +#: ./doc/common/tables/nova-cells.xml:31(td) +msgid "(StrOpt) Type of cell: api or compute" +msgstr "" + +#: ./doc/common/tables/nova-cells.xml:34(td) +msgid "cells_config = None" +msgstr "" + +#: ./doc/common/tables/nova-cells.xml:35(td) +msgid "(StrOpt) Configuration file from which to read cells configuration. If given, overrides reading cells from the database." +msgstr "" + +#: ./doc/common/tables/nova-cells.xml:38(td) +msgid "driver = nova.cells.rpc_driver.CellsRPCDriver" +msgstr "" + +#: ./doc/common/tables/nova-cells.xml:39(td) +msgid "(StrOpt) Cells communication driver to use" +msgstr "" + +#: ./doc/common/tables/nova-cells.xml:42(td) +msgid "enable = False" +msgstr "" + +#: ./doc/common/tables/nova-cells.xml:43(td) +msgid "(BoolOpt) Enable cell functionality" +msgstr "" + +#: ./doc/common/tables/nova-cells.xml:46(td) +msgid "instance_update_num_instances = 1" +msgstr "" + +#: ./doc/common/tables/nova-cells.xml:47(td) +msgid "(IntOpt) Number of instances to update per periodic task run" +msgstr "" + +#: ./doc/common/tables/nova-cells.xml:50(td) +msgid "instance_updated_at_threshold = 3600" +msgstr "" + +#: ./doc/common/tables/nova-cells.xml:51(td) +msgid "(IntOpt) Number of seconds after an instance was updated or deleted to continue to update cells" +msgstr "" + +#: ./doc/common/tables/nova-cells.xml:54(td) +msgid "manager = nova.cells.manager.CellsManager" +msgstr "" + +#: ./doc/common/tables/nova-cells.xml:55(td) +msgid "(StrOpt) Manager for cells" +msgstr "" + +#: ./doc/common/tables/nova-cells.xml:58(td) +msgid "max_hop_count = 10" +msgstr "" + +#: ./doc/common/tables/nova-cells.xml:59(td) +msgid "(IntOpt) Maximum number of hops for cells routing." +msgstr "" + +#: ./doc/common/tables/nova-cells.xml:62(td) +msgid "mute_child_interval = 300" +msgstr "" + +#: ./doc/common/tables/nova-cells.xml:63(td) +msgid "(IntOpt) Number of seconds after which a lack of capability and capacity updates signals the child cell is to be treated as a mute." +msgstr "" + +#: ./doc/common/tables/nova-cells.xml:66(td) +msgid "mute_weight_multiplier = -10.0" +msgstr "" + +#: ./doc/common/tables/nova-cells.xml:67(td) +msgid "(FloatOpt) Multiplier used to weigh mute children. (The value should be negative.)" +msgstr "" + +#: ./doc/common/tables/nova-cells.xml:70(td) +msgid "mute_weight_value = 1000.0" +msgstr "" + +#: ./doc/common/tables/nova-cells.xml:71(td) +msgid "(FloatOpt) Weight value assigned to mute children. (The value should be positive.)" +msgstr "" + +#: ./doc/common/tables/nova-cells.xml:74(td) +msgid "name = nova" +msgstr "" + +#: ./doc/common/tables/nova-cells.xml:75(td) +msgid "(StrOpt) name of this cell" +msgstr "" + +#: ./doc/common/tables/nova-cells.xml:78(td) +msgid "offset_weight_multiplier = 1.0" +msgstr "" + +#: ./doc/common/tables/nova-cells.xml:79(td) +msgid "(FloatOpt) Multiplier used to weigh offset weigher." +msgstr "" + +#: ./doc/common/tables/nova-cells.xml:82(td) +msgid "reserve_percent = 10.0" +msgstr "" + +#: ./doc/common/tables/nova-cells.xml:83(td) +msgid "(FloatOpt) Percentage of cell capacity to hold in reserve. Affects both memory and disk utilization" +msgstr "" + +#: ./doc/common/tables/nova-cells.xml:86(td) +msgid "topic = cells" +msgstr "" + +#: ./doc/common/tables/nova-cells.xml:87(td) +msgid "(StrOpt) the topic cells nodes listen on" +msgstr "" + +#: ./doc/common/tables/glance-policy.xml:8(caption) ./doc/common/tables/nova-policy.xml:8(caption) ./doc/common/tables/neutron-policy.xml:8(caption) +msgid "Description of configuration options for policy" +msgstr "" + +#: ./doc/common/tables/glance-policy.xml:22(td) ./doc/common/tables/nova-policy.xml:58(td) ./doc/common/tables/cinder-common.xml:146(td) +msgid "policy_default_rule = default" +msgstr "" + +#: ./doc/common/tables/glance-policy.xml:23(td) +msgid "(StrOpt) The default policy to use." +msgstr "" + +#: ./doc/common/tables/glance-policy.xml:26(td) ./doc/common/tables/nova-policy.xml:62(td) ./doc/common/tables/cinder-common.xml:150(td) ./doc/common/tables/neutron-policy.xml:23(td) +msgid "policy_file = policy.json" +msgstr "" + +#: ./doc/common/tables/glance-policy.xml:27(td) +msgid "(StrOpt) The location of the policy file." +msgstr "" + +#: ./doc/common/tables/neutron-mlnx.xml:8(caption) +msgid "Description of configuration options for mlnx" +msgstr "" + +#: ./doc/common/tables/neutron-mlnx.xml:19(td) +msgid "backoff_rate = 2" +msgstr "" + +#: ./doc/common/tables/neutron-mlnx.xml:20(td) +msgid "(IntOpt) backoff rate multiplier for waiting period between retries for request to daemon, i.e. value of 2 will double the request timeout each retry" +msgstr "" + +#: ./doc/common/tables/neutron-mlnx.xml:23(td) +msgid "daemon_endpoint = tcp://127.0.0.1:60001" +msgstr "" + +#: ./doc/common/tables/neutron-mlnx.xml:24(td) +msgid "(StrOpt) eswitch daemon end point" +msgstr "" + +#: ./doc/common/tables/neutron-mlnx.xml:27(td) +msgid "request_timeout = 3000" +msgstr "" + +#: ./doc/common/tables/neutron-mlnx.xml:28(td) +msgid "(IntOpt) The number of milliseconds the agent will wait for response on request to daemon." +msgstr "" + +#: ./doc/common/tables/neutron-mlnx.xml:31(td) +msgid "vnic_type = mlnx_direct" +msgstr "" + +#: ./doc/common/tables/neutron-mlnx.xml:32(td) +msgid "(StrOpt) Type of VM network interface: mlnx_direct or hostdev" +msgstr "" + +#: ./doc/common/tables/nova-ipv6.xml:8(caption) +msgid "Description of configuration options for ipv6" +msgstr "" + +#: ./doc/common/tables/nova-ipv6.xml:22(td) +msgid "fixed_range_v6 = fd00::/48" +msgstr "" + +#: ./doc/common/tables/nova-ipv6.xml:23(td) +msgid "(StrOpt) Fixed IPv6 address block" +msgstr "" + +#: ./doc/common/tables/nova-ipv6.xml:26(td) +msgid "gateway_v6 = None" +msgstr "" + +#: ./doc/common/tables/nova-ipv6.xml:27(td) +msgid "(StrOpt) Default IPv6 gateway" +msgstr "" + +#: ./doc/common/tables/nova-ipv6.xml:30(td) +msgid "ipv6_backend = rfc2462" +msgstr "" + +#: ./doc/common/tables/nova-ipv6.xml:31(td) +msgid "(StrOpt) Backend to use for IPv6 generation" +msgstr "" + +#: ./doc/common/tables/nova-ipv6.xml:34(td) +msgid "use_ipv6 = False" +msgstr "" + +#: ./doc/common/tables/nova-ipv6.xml:35(td) +msgid "(BoolOpt) use ipv6" +msgstr "" + +#: ./doc/common/tables/cinder-eqlx.xml:8(caption) +msgid "Description of configuration options for eqlx" +msgstr "" + +#: ./doc/common/tables/cinder-eqlx.xml:22(td) +msgid "eqlx_chap_login = admin" +msgstr "" + +#: ./doc/common/tables/cinder-eqlx.xml:23(td) +msgid "(StrOpt) Existing CHAP account name" +msgstr "" + +#: ./doc/common/tables/cinder-eqlx.xml:26(td) +msgid "eqlx_chap_password = password" +msgstr "" + +#: ./doc/common/tables/cinder-eqlx.xml:27(td) +msgid "(StrOpt) Password for specified CHAP account name" +msgstr "" + +#: ./doc/common/tables/cinder-eqlx.xml:30(td) +msgid "eqlx_cli_max_retries = 5" +msgstr "" + +#: ./doc/common/tables/cinder-eqlx.xml:31(td) +msgid "(IntOpt) Maximum retry count for reconnection" +msgstr "" + +#: ./doc/common/tables/cinder-eqlx.xml:34(td) +msgid "eqlx_cli_timeout = 30" +msgstr "" + +#: ./doc/common/tables/cinder-eqlx.xml:35(td) +msgid "(IntOpt) Timeout for the Group Manager cli command execution" +msgstr "" + +#: ./doc/common/tables/cinder-eqlx.xml:38(td) +msgid "eqlx_group_name = group-0" +msgstr "" + +#: ./doc/common/tables/cinder-eqlx.xml:39(td) +msgid "(StrOpt) Group name to use for creating volumes" +msgstr "" + +#: ./doc/common/tables/cinder-eqlx.xml:42(td) +msgid "eqlx_pool = default" +msgstr "" + +#: ./doc/common/tables/cinder-eqlx.xml:43(td) +msgid "(StrOpt) Pool in which volumes will be created" +msgstr "" + +#: ./doc/common/tables/cinder-eqlx.xml:46(td) +msgid "eqlx_use_chap = False" +msgstr "" + +#: ./doc/common/tables/cinder-eqlx.xml:47(td) +msgid "(BoolOpt) Use CHAP authentication for targets?" +msgstr "" + +#: ./doc/common/tables/swift-object-expirer-filter-catch_errors.xml:7(literal) ./doc/common/tables/swift-proxy-server-filter-catch_errors.xml:7(literal) +msgid "[filter:catch_errors]" +msgstr "" + +#: ./doc/common/tables/swift-object-expirer-filter-catch_errors.xml:7(literal) ./doc/common/tables/swift-object-expirer-filter-cache.xml:7(literal) ./doc/common/tables/swift-object-expirer-DEFAULT.xml:7(literal) ./doc/common/tables/swift-object-expirer-app-proxy-server.xml:7(literal) ./doc/common/tables/swift-object-expirer-pipeline-main.xml:7(literal) ./doc/common/tables/swift-object-expirer-object-expirer.xml:7(literal) +msgid "object-expirer.conf-sample" +msgstr "" + +#: ./doc/common/tables/swift-object-expirer-filter-catch_errors.xml:7(caption) ./doc/common/tables/swift-object-expirer-filter-cache.xml:7(caption) ./doc/common/tables/swift-proxy-server-filter-cache.xml:7(caption) ./doc/common/tables/swift-container-server-DEFAULT.xml:7(caption) ./doc/common/tables/swift-container-server-container-updater.xml:7(caption) ./doc/common/tables/swift-account-server-filter-recon.xml:7(caption) ./doc/common/tables/swift-container-server-container-replicator.xml:7(caption) ./doc/common/tables/swift-proxy-server-filter-name_check.xml:7(caption) ./doc/common/tables/swift-proxy-server-filter-ratelimit.xml:7(caption) ./doc/common/tables/swift-container-server-container-sync.xml:7(caption) ./doc/common/tables/swift-object-server-object-auditor.xml:7(caption) ./doc/common/tables/swift-proxy-server-filter-tempurl.xml:7(caption) ./doc/common/tables/swift-proxy-server-filter-healthcheck.xml:7(caption) ./doc/common/tables/swift-object-expirer-DEFAULT.xml:7(caption) ./doc/common/tables/swift-swift-bench-bench.xml:7(caption) ./doc/common/tables/swift-object-server-object-updater.xml:7(caption) ./doc/common/tables/swift-proxy-server-filter-account-quotas.xml:7(caption) ./doc/common/tables/swift-proxy-server-app-proxy-server.xml:7(caption) ./doc/common/tables/swift-container-server-pipeline-main.xml:7(caption) ./doc/common/tables/swift-rsyncd-object.xml:7(caption) ./doc/common/tables/swift-object-server-pipeline-main.xml:7(caption) ./doc/common/tables/swift-account-server-app-account-server.xml:7(caption) ./doc/common/tables/swift-account-server-filter-healthcheck.xml:7(caption) ./doc/common/tables/swift-container-server-app-container-server.xml:7(caption) ./doc/common/tables/swift-proxy-server-filter-slo.xml:7(caption) ./doc/common/tables/swift-account-server-account-auditor.xml:7(caption) ./doc/common/tables/swift-object-server-DEFAULT.xml:7(caption) ./doc/common/tables/swift-proxy-server-filter-bulk.xml:7(caption) ./doc/common/tables/swift-account-server-DEFAULT.xml:7(caption) ./doc/common/tables/swift-proxy-server-filter-proxy-logging.xml:7(caption) ./doc/common/tables/swift-rsyncd-account.xml:7(caption) ./doc/common/tables/swift-container-server-filter-healthcheck.xml:7(caption) ./doc/common/tables/swift-swift-swift-constraints.xml:7(caption) ./doc/common/tables/swift-object-server-filter-recon.xml:7(caption) ./doc/common/tables/swift-container-server-container-auditor.xml:7(caption) ./doc/common/tables/swift-proxy-server-filter-catch_errors.xml:7(caption) ./doc/common/tables/swift-proxy-server-filter-list-endpoints.xml:7(caption) ./doc/common/tables/swift-memcache-memcache.xml:7(caption) ./doc/common/tables/swift-proxy-server-filter-keystoneauth.xml:7(caption) ./doc/common/tables/swift-proxy-server-filter-tempauth.xml:7(caption) ./doc/common/tables/swift-object-server-object-replicator.xml:7(caption) ./doc/common/tables/swift-dispersion-dispersion.xml:7(caption) ./doc/common/tables/swift-account-server-account-replicator.xml:7(caption) ./doc/common/tables/swift-proxy-server-filter-authtoken.xml:7(caption) ./doc/common/tables/swift-object-server-app-object-server.xml:7(caption) ./doc/common/tables/swift-proxy-server-DEFAULT.xml:7(caption) ./doc/common/tables/swift-proxy-server-filter-staticweb.xml:7(caption) ./doc/common/tables/swift-object-expirer-app-proxy-server.xml:7(caption) ./doc/common/tables/swift-drive-audit-drive-audit.xml:7(caption) ./doc/common/tables/swift-container-server-filter-recon.xml:7(caption) ./doc/common/tables/swift-object-expirer-pipeline-main.xml:7(caption) ./doc/common/tables/swift-proxy-server-filter-container-quotas.xml:7(caption) ./doc/common/tables/swift-swift-swift-hash.xml:7(caption) ./doc/common/tables/swift-proxy-server-filter-formpost.xml:7(caption) ./doc/common/tables/swift-rsyncd-container.xml:7(caption) ./doc/common/tables/swift-object-server-filter-healthcheck.xml:7(caption) ./doc/common/tables/swift-account-server-pipeline-main.xml:7(caption) ./doc/common/tables/swift-object-expirer-object-expirer.xml:7(caption) ./doc/common/tables/swift-proxy-server-pipeline-main.xml:7(caption) ./doc/common/tables/swift-proxy-server-filter-cname_lookup.xml:7(caption) ./doc/common/tables/swift-account-server-account-reaper.xml:7(caption) ./doc/common/tables/swift-proxy-server-filter-domain_remap.xml:7(caption) +msgid "Description of configuration options for in " +msgstr "" + +#: ./doc/common/tables/swift-object-expirer-filter-catch_errors.xml:18(td) ./doc/common/tables/swift-proxy-server-filter-catch_errors.xml:18(td) +msgid "use = egg:swift#catch_errors" +msgstr "" + +#: ./doc/common/tables/swift-object-expirer-filter-catch_errors.xml:18(td) ./doc/common/tables/swift-object-expirer-filter-cache.xml:18(td) ./doc/common/tables/swift-proxy-server-filter-cache.xml:18(td) ./doc/common/tables/swift-account-server-filter-recon.xml:18(td) ./doc/common/tables/swift-proxy-server-filter-name_check.xml:18(td) ./doc/common/tables/swift-proxy-server-filter-ratelimit.xml:18(td) ./doc/common/tables/swift-proxy-server-filter-healthcheck.xml:18(td) ./doc/common/tables/swift-proxy-server-filter-account-quotas.xml:18(td) ./doc/common/tables/swift-proxy-server-app-proxy-server.xml:18(td) ./doc/common/tables/swift-account-server-app-account-server.xml:18(td) ./doc/common/tables/swift-account-server-filter-healthcheck.xml:18(td) ./doc/common/tables/swift-container-server-app-container-server.xml:18(td) ./doc/common/tables/swift-proxy-server-filter-slo.xml:18(td) ./doc/common/tables/swift-proxy-server-filter-bulk.xml:18(td) ./doc/common/tables/swift-proxy-server-filter-proxy-logging.xml:18(td) ./doc/common/tables/swift-container-server-filter-healthcheck.xml:18(td) ./doc/common/tables/swift-object-server-filter-recon.xml:18(td) ./doc/common/tables/swift-proxy-server-filter-catch_errors.xml:18(td) ./doc/common/tables/swift-proxy-server-filter-list-endpoints.xml:18(td) ./doc/common/tables/swift-proxy-server-filter-keystoneauth.xml:18(td) ./doc/common/tables/swift-proxy-server-filter-tempauth.xml:18(td) ./doc/common/tables/swift-object-server-app-object-server.xml:18(td) ./doc/common/tables/swift-proxy-server-filter-staticweb.xml:18(td) ./doc/common/tables/swift-object-expirer-app-proxy-server.xml:18(td) ./doc/common/tables/swift-container-server-filter-recon.xml:18(td) ./doc/common/tables/swift-proxy-server-filter-container-quotas.xml:18(td) ./doc/common/tables/swift-proxy-server-filter-formpost.xml:18(td) ./doc/common/tables/swift-object-server-filter-healthcheck.xml:18(td) ./doc/common/tables/swift-proxy-server-filter-cname_lookup.xml:18(td) ./doc/common/tables/swift-proxy-server-filter-domain_remap.xml:18(td) +msgid "Entry point of paste.deploy in the server" +msgstr "" + +#: ./doc/common/tables/swift-object-expirer-filter-cache.xml:7(literal) ./doc/common/tables/swift-proxy-server-filter-cache.xml:7(literal) +msgid "[filter:cache]" +msgstr "" + +#: ./doc/common/tables/swift-object-expirer-filter-cache.xml:18(td) ./doc/common/tables/swift-proxy-server-filter-cache.xml:18(td) +msgid "use = egg:swift#memcache" +msgstr "" + +#: ./doc/common/tables/cinder-netapp_cdot_extraspecs.xml:4(caption) +msgid "Description of extra specs options for NetApp Unified Driver with Clustered Data ONTAP" +msgstr "" + +#: ./doc/common/tables/cinder-netapp_cdot_extraspecs.xml:10(th) +msgid "Extra spec" +msgstr "" + +#: ./doc/common/tables/cinder-netapp_cdot_extraspecs.xml:11(th) +msgid "Type" +msgstr "" + +#: ./doc/common/tables/cinder-netapp_cdot_extraspecs.xml:17(literal) +msgid "netapp:raid_type" +msgstr "" + +#: ./doc/common/tables/cinder-netapp_cdot_extraspecs.xml:18(td) ./doc/common/tables/cinder-netapp_cdot_extraspecs.xml:23(td) ./doc/common/tables/cinder-netapp_cdot_extraspecs.xml:29(td) +msgid "String" +msgstr "" + +#: ./doc/common/tables/cinder-netapp_cdot_extraspecs.xml:19(literal) +msgid "raid4, raid_dp" +msgstr "" + +#: ./doc/common/tables/cinder-netapp_cdot_extraspecs.xml:19(td) +msgid "Limit the candidate volume list based on one of the following raid types: ." +msgstr "" + +#: ./doc/common/tables/cinder-netapp_cdot_extraspecs.xml:22(literal) +msgid "netapp:disk_type" +msgstr "" + +#: ./doc/common/tables/cinder-netapp_cdot_extraspecs.xml:24(literal) +msgid "ATA, BSAS, EATA, FCAL, FSAS, LUN, MSATA, SAS, SATA, SCSI, XATA, XSAS, or SSD." +msgstr "" + +#: ./doc/common/tables/cinder-netapp_cdot_extraspecs.xml:24(td) +msgid "Limit the candidate volume list based on one of the following disk types: " +msgstr "" + +#: ./doc/common/tables/cinder-netapp_cdot_extraspecs.xml:28(literal) +msgid "netapp:qos_policy_group" +msgstr "" + +#: ./doc/common/tables/cinder-netapp_cdot_extraspecs.xml:30(td) +msgid "Limit the candidate volume list based on the name of a QoS policy group, which defines measurable Service Level Objectives that apply to the storage objects with which the policy group is associated." +msgstr "" + +#: ./doc/common/tables/cinder-netapp_cdot_extraspecs.xml:34(literal) +msgid "netapp_mirrored" +msgstr "" + +#: ./doc/common/tables/cinder-netapp_cdot_extraspecs.xml:34(para) +msgid "If both the positive and negative specs for a pair are specified (for example, netapp_dedup and netapp_nodedup) and set to the same value within a single extra_specs list, then neither spec will be utilized by the driver." +msgstr "" + +#: ./doc/common/tables/cinder-netapp_cdot_extraspecs.xml:35(td) ./doc/common/tables/cinder-netapp_cdot_extraspecs.xml:40(td) ./doc/common/tables/cinder-netapp_cdot_extraspecs.xml:45(td) ./doc/common/tables/cinder-netapp_cdot_extraspecs.xml:50(td) ./doc/common/tables/cinder-netapp_cdot_extraspecs.xml:55(td) ./doc/common/tables/cinder-netapp_cdot_extraspecs.xml:60(td) ./doc/common/tables/cinder-netapp_cdot_extraspecs.xml:65(td) ./doc/common/tables/cinder-netapp_cdot_extraspecs.xml:70(td) +msgid "Boolean" +msgstr "" + +#: ./doc/common/tables/cinder-netapp_cdot_extraspecs.xml:36(td) +msgid "Limit the candidate volume list to only the ones that are mirrored on the storage controller." +msgstr "" + +#: ./doc/common/tables/cinder-netapp_cdot_extraspecs.xml:39(literal) +msgid "netapp_unmirrored" +msgstr "" + +#: ./doc/common/tables/cinder-netapp_cdot_extraspecs.xml:41(td) +msgid "Limit the candidate volume list to only the ones that are not mirrored on the storage controller." +msgstr "" + +#: ./doc/common/tables/cinder-netapp_cdot_extraspecs.xml:44(literal) +msgid "netapp_dedup" +msgstr "" + +#: ./doc/common/tables/cinder-netapp_cdot_extraspecs.xml:46(td) +msgid "Limit the candidate volume list to only the ones that have deduplication enabled on the storage controller." +msgstr "" + +#: ./doc/common/tables/cinder-netapp_cdot_extraspecs.xml:49(literal) +msgid "netapp_nodedup" +msgstr "" + +#: ./doc/common/tables/cinder-netapp_cdot_extraspecs.xml:51(td) +msgid "Limit the candidate volume list to only the ones that have deduplication disabled on the storage controller." +msgstr "" + +#: ./doc/common/tables/cinder-netapp_cdot_extraspecs.xml:54(literal) +msgid "netapp_compression" +msgstr "" + +#: ./doc/common/tables/cinder-netapp_cdot_extraspecs.xml:56(td) +msgid "Limit the candidate volume list to only the ones that have compression enabled on the storage controller." +msgstr "" + +#: ./doc/common/tables/cinder-netapp_cdot_extraspecs.xml:59(literal) +msgid "netapp_nocompression" +msgstr "" + +#: ./doc/common/tables/cinder-netapp_cdot_extraspecs.xml:61(td) +msgid "Limit the candidate volume list to only the ones that have compression disabled on the storage controller." +msgstr "" + +#: ./doc/common/tables/cinder-netapp_cdot_extraspecs.xml:64(literal) +msgid "netapp_thin_provisioned" +msgstr "" + +#: ./doc/common/tables/cinder-netapp_cdot_extraspecs.xml:66(td) +msgid "Limit the candidate volume list to only the ones that support thin provisioning on the storage controller." +msgstr "" + +#: ./doc/common/tables/cinder-netapp_cdot_extraspecs.xml:69(literal) +msgid "netapp_thick_provisioned" +msgstr "" + +#: ./doc/common/tables/cinder-netapp_cdot_extraspecs.xml:71(td) +msgid "Limit the candidate volume list to only the ones that support thick provisioning on the storage controller." +msgstr "" + +#: ./doc/common/tables/swift-proxy-server-filter-cache.xml:7(literal) ./doc/common/tables/swift-proxy-server-filter-name_check.xml:7(literal) ./doc/common/tables/swift-proxy-server-filter-ratelimit.xml:7(literal) ./doc/common/tables/swift-proxy-server-filter-tempurl.xml:7(literal) ./doc/common/tables/swift-proxy-server-filter-healthcheck.xml:7(literal) ./doc/common/tables/swift-proxy-server-filter-account-quotas.xml:7(literal) ./doc/common/tables/swift-proxy-server-app-proxy-server.xml:7(literal) ./doc/common/tables/swift-proxy-server-filter-slo.xml:7(literal) ./doc/common/tables/swift-proxy-server-filter-bulk.xml:7(literal) ./doc/common/tables/swift-proxy-server-filter-proxy-logging.xml:7(literal) ./doc/common/tables/swift-proxy-server-filter-catch_errors.xml:7(literal) ./doc/common/tables/swift-proxy-server-filter-list-endpoints.xml:7(literal) ./doc/common/tables/swift-proxy-server-filter-keystoneauth.xml:7(literal) ./doc/common/tables/swift-proxy-server-filter-tempauth.xml:7(literal) ./doc/common/tables/swift-proxy-server-filter-authtoken.xml:7(literal) ./doc/common/tables/swift-proxy-server-DEFAULT.xml:7(literal) ./doc/common/tables/swift-proxy-server-filter-staticweb.xml:7(literal) ./doc/common/tables/swift-proxy-server-filter-container-quotas.xml:7(literal) ./doc/common/tables/swift-proxy-server-filter-formpost.xml:7(literal) ./doc/common/tables/swift-proxy-server-pipeline-main.xml:7(literal) ./doc/common/tables/swift-proxy-server-filter-cname_lookup.xml:7(literal) ./doc/common/tables/swift-proxy-server-filter-domain_remap.xml:7(literal) +msgid "proxy-server.conf-sample" +msgstr "" + +#: ./doc/common/tables/swift-proxy-server-filter-cache.xml:21(td) +msgid "set log_name = cache" +msgstr "" + +#: ./doc/common/tables/swift-proxy-server-filter-cache.xml:21(td) ./doc/common/tables/swift-proxy-server-filter-ratelimit.xml:21(td) ./doc/common/tables/swift-proxy-server-app-proxy-server.xml:21(td) ./doc/common/tables/swift-account-server-app-account-server.xml:21(td) ./doc/common/tables/swift-container-server-app-container-server.xml:21(td) ./doc/common/tables/swift-proxy-server-filter-catch_errors.xml:21(td) ./doc/common/tables/swift-proxy-server-filter-tempauth.xml:21(td) ./doc/common/tables/swift-object-server-app-object-server.xml:21(td) ./doc/common/tables/swift-proxy-server-filter-cname_lookup.xml:21(td) ./doc/common/tables/swift-proxy-server-filter-domain_remap.xml:21(td) +msgid "Label to use when logging" +msgstr "" + +#: ./doc/common/tables/swift-proxy-server-filter-cache.xml:24(td) ./doc/common/tables/swift-proxy-server-filter-ratelimit.xml:24(td) ./doc/common/tables/swift-proxy-server-app-proxy-server.xml:24(td) ./doc/common/tables/swift-account-server-app-account-server.xml:24(td) ./doc/common/tables/swift-container-server-app-container-server.xml:24(td) ./doc/common/tables/swift-proxy-server-filter-catch_errors.xml:24(td) ./doc/common/tables/swift-proxy-server-filter-tempauth.xml:24(td) ./doc/common/tables/swift-object-server-app-object-server.xml:24(td) ./doc/common/tables/swift-proxy-server-filter-cname_lookup.xml:24(td) ./doc/common/tables/swift-proxy-server-filter-domain_remap.xml:24(td) +msgid "set log_facility = LOG_LOCAL0" +msgstr "" + +#: ./doc/common/tables/swift-proxy-server-filter-cache.xml:24(td) ./doc/common/tables/swift-container-server-DEFAULT.xml:64(td) ./doc/common/tables/swift-container-server-container-updater.xml:21(td) ./doc/common/tables/swift-container-server-container-replicator.xml:21(td) ./doc/common/tables/swift-proxy-server-filter-ratelimit.xml:24(td) ./doc/common/tables/swift-container-server-container-sync.xml:21(td) ./doc/common/tables/swift-object-server-object-auditor.xml:21(td) ./doc/common/tables/swift-object-expirer-DEFAULT.xml:27(td) ./doc/common/tables/swift-object-server-object-updater.xml:21(td) ./doc/common/tables/swift-proxy-server-app-proxy-server.xml:24(td) ./doc/common/tables/swift-account-server-app-account-server.xml:24(td) ./doc/common/tables/swift-container-server-app-container-server.xml:24(td) ./doc/common/tables/swift-account-server-account-auditor.xml:21(td) ./doc/common/tables/swift-account-server-account-auditor.xml:33(td) ./doc/common/tables/swift-object-server-DEFAULT.xml:64(td) ./doc/common/tables/swift-account-server-DEFAULT.xml:61(td) ./doc/common/tables/swift-container-server-container-auditor.xml:21(td) ./doc/common/tables/swift-proxy-server-filter-catch_errors.xml:24(td) ./doc/common/tables/swift-proxy-server-filter-tempauth.xml:24(td) ./doc/common/tables/swift-object-server-object-replicator.xml:21(td) ./doc/common/tables/swift-account-server-account-replicator.xml:21(td) ./doc/common/tables/swift-object-server-app-object-server.xml:24(td) ./doc/common/tables/swift-proxy-server-DEFAULT.xml:61(td) ./doc/common/tables/swift-drive-audit-drive-audit.xml:21(td) ./doc/common/tables/swift-proxy-server-filter-cname_lookup.xml:24(td) ./doc/common/tables/swift-account-server-account-reaper.xml:21(td) ./doc/common/tables/swift-proxy-server-filter-domain_remap.xml:24(td) +msgid "Syslog log facility" +msgstr "" + +#: ./doc/common/tables/swift-proxy-server-filter-cache.xml:27(td) ./doc/common/tables/swift-proxy-server-filter-ratelimit.xml:27(td) ./doc/common/tables/swift-proxy-server-app-proxy-server.xml:27(td) ./doc/common/tables/swift-account-server-app-account-server.xml:27(td) ./doc/common/tables/swift-container-server-app-container-server.xml:27(td) ./doc/common/tables/swift-proxy-server-filter-catch_errors.xml:27(td) ./doc/common/tables/swift-proxy-server-filter-tempauth.xml:27(td) ./doc/common/tables/swift-object-server-app-object-server.xml:27(td) ./doc/common/tables/swift-proxy-server-filter-cname_lookup.xml:27(td) ./doc/common/tables/swift-proxy-server-filter-domain_remap.xml:27(td) +msgid "set log_level = INFO" +msgstr "" + +#: ./doc/common/tables/swift-proxy-server-filter-cache.xml:27(td) ./doc/common/tables/swift-proxy-server-filter-ratelimit.xml:27(td) ./doc/common/tables/swift-proxy-server-app-proxy-server.xml:27(td) ./doc/common/tables/swift-account-server-app-account-server.xml:27(td) ./doc/common/tables/swift-container-server-app-container-server.xml:27(td) ./doc/common/tables/swift-proxy-server-filter-catch_errors.xml:27(td) ./doc/common/tables/swift-proxy-server-filter-tempauth.xml:27(td) ./doc/common/tables/swift-object-server-app-object-server.xml:27(td) ./doc/common/tables/swift-proxy-server-filter-cname_lookup.xml:27(td) ./doc/common/tables/swift-proxy-server-filter-domain_remap.xml:27(td) +msgid "Log level" +msgstr "" + +#: ./doc/common/tables/swift-proxy-server-filter-cache.xml:30(td) ./doc/common/tables/swift-proxy-server-filter-ratelimit.xml:30(td) ./doc/common/tables/swift-proxy-server-filter-catch_errors.xml:30(td) ./doc/common/tables/swift-proxy-server-filter-tempauth.xml:30(td) ./doc/common/tables/swift-proxy-server-filter-cname_lookup.xml:30(td) ./doc/common/tables/swift-proxy-server-filter-domain_remap.xml:30(td) +msgid "set log_headers = false" +msgstr "" + +#: ./doc/common/tables/swift-proxy-server-filter-cache.xml:30(td) ./doc/common/tables/swift-proxy-server-filter-ratelimit.xml:30(td) ./doc/common/tables/swift-proxy-server-filter-catch_errors.xml:30(td) ./doc/common/tables/swift-proxy-server-filter-tempauth.xml:30(td) ./doc/common/tables/swift-proxy-server-filter-cname_lookup.xml:30(td) ./doc/common/tables/swift-proxy-server-filter-domain_remap.xml:30(td) +msgid "If True, log headers in each request" +msgstr "" + +#: ./doc/common/tables/swift-proxy-server-filter-cache.xml:33(td) ./doc/common/tables/swift-proxy-server-filter-ratelimit.xml:33(td) ./doc/common/tables/swift-proxy-server-app-proxy-server.xml:30(td) ./doc/common/tables/swift-account-server-app-account-server.xml:33(td) ./doc/common/tables/swift-container-server-app-container-server.xml:33(td) ./doc/common/tables/swift-proxy-server-filter-catch_errors.xml:33(td) ./doc/common/tables/swift-proxy-server-filter-tempauth.xml:33(td) ./doc/common/tables/swift-object-server-app-object-server.xml:33(td) ./doc/common/tables/swift-proxy-server-filter-cname_lookup.xml:33(td) ./doc/common/tables/swift-proxy-server-filter-domain_remap.xml:33(td) +msgid "set log_address = /dev/log" +msgstr "" + +#: ./doc/common/tables/swift-proxy-server-filter-cache.xml:33(td) ./doc/common/tables/swift-proxy-server-filter-cache.xml:39(td) ./doc/common/tables/swift-container-server-DEFAULT.xml:58(td) ./doc/common/tables/swift-proxy-server-filter-ratelimit.xml:33(td) ./doc/common/tables/swift-proxy-server-filter-ratelimit.xml:57(td) ./doc/common/tables/swift-proxy-server-filter-ratelimit.xml:60(td) ./doc/common/tables/swift-proxy-server-filter-ratelimit.xml:63(td) ./doc/common/tables/swift-proxy-server-filter-ratelimit.xml:66(td) ./doc/common/tables/swift-proxy-server-filter-ratelimit.xml:69(td) ./doc/common/tables/swift-proxy-server-filter-ratelimit.xml:72(td) ./doc/common/tables/swift-proxy-server-filter-ratelimit.xml:75(td) ./doc/common/tables/swift-object-server-object-auditor.xml:45(td) ./doc/common/tables/swift-proxy-server-filter-healthcheck.xml:21(td) ./doc/common/tables/swift-swift-bench-bench.xml:24(td) ./doc/common/tables/swift-swift-bench-bench.xml:30(td) ./doc/common/tables/swift-swift-bench-bench.xml:36(td) ./doc/common/tables/swift-swift-bench-bench.xml:39(td) ./doc/common/tables/swift-swift-bench-bench.xml:42(td) ./doc/common/tables/swift-swift-bench-bench.xml:48(td) ./doc/common/tables/swift-swift-bench-bench.xml:51(td) ./doc/common/tables/swift-swift-bench-bench.xml:54(td) ./doc/common/tables/swift-swift-bench-bench.xml:57(td) ./doc/common/tables/swift-swift-bench-bench.xml:60(td) ./doc/common/tables/swift-swift-bench-bench.xml:63(td) ./doc/common/tables/swift-swift-bench-bench.xml:66(td) ./doc/common/tables/swift-swift-bench-bench.xml:69(td) ./doc/common/tables/swift-swift-bench-bench.xml:72(td) ./doc/common/tables/swift-swift-bench-bench.xml:75(td) ./doc/common/tables/swift-swift-bench-bench.xml:78(td) ./doc/common/tables/swift-swift-bench-bench.xml:81(td) ./doc/common/tables/swift-swift-bench-bench.xml:87(td) ./doc/common/tables/swift-proxy-server-app-proxy-server.xml:30(td) ./doc/common/tables/swift-proxy-server-app-proxy-server.xml:33(td) ./doc/common/tables/swift-proxy-server-app-proxy-server.xml:75(td) ./doc/common/tables/swift-proxy-server-app-proxy-server.xml:81(td) ./doc/common/tables/swift-proxy-server-app-proxy-server.xml:90(td) ./doc/common/tables/swift-proxy-server-app-proxy-server.xml:93(td) ./doc/common/tables/swift-proxy-server-app-proxy-server.xml:96(td) ./doc/common/tables/swift-proxy-server-app-proxy-server.xml:99(td) ./doc/common/tables/swift-proxy-server-app-proxy-server.xml:105(td) ./doc/common/tables/swift-proxy-server-app-proxy-server.xml:108(td) ./doc/common/tables/swift-proxy-server-app-proxy-server.xml:111(td) ./doc/common/tables/swift-proxy-server-app-proxy-server.xml:114(td) ./doc/common/tables/swift-proxy-server-app-proxy-server.xml:117(td) ./doc/common/tables/swift-container-server-pipeline-main.xml:18(td) ./doc/common/tables/swift-rsyncd-object.xml:18(td) ./doc/common/tables/swift-rsyncd-object.xml:21(td) ./doc/common/tables/swift-rsyncd-object.xml:24(td) ./doc/common/tables/swift-rsyncd-object.xml:27(td) ./doc/common/tables/swift-object-server-pipeline-main.xml:18(td) ./doc/common/tables/swift-account-server-app-account-server.xml:33(td) ./doc/common/tables/swift-account-server-filter-healthcheck.xml:21(td) ./doc/common/tables/swift-container-server-app-container-server.xml:33(td) ./doc/common/tables/swift-proxy-server-filter-slo.xml:21(td) ./doc/common/tables/swift-proxy-server-filter-slo.xml:24(td) ./doc/common/tables/swift-proxy-server-filter-slo.xml:27(td) ./doc/common/tables/swift-object-server-DEFAULT.xml:45(td) ./doc/common/tables/swift-proxy-server-filter-bulk.xml:21(td) ./doc/common/tables/swift-proxy-server-filter-bulk.xml:24(td) ./doc/common/tables/swift-proxy-server-filter-bulk.xml:27(td) ./doc/common/tables/swift-proxy-server-filter-bulk.xml:30(td) ./doc/common/tables/swift-proxy-server-filter-proxy-logging.xml:21(td) ./doc/common/tables/swift-proxy-server-filter-proxy-logging.xml:24(td) ./doc/common/tables/swift-proxy-server-filter-proxy-logging.xml:27(td) ./doc/common/tables/swift-proxy-server-filter-proxy-logging.xml:30(td) ./doc/common/tables/swift-proxy-server-filter-proxy-logging.xml:33(td) ./doc/common/tables/swift-proxy-server-filter-proxy-logging.xml:36(td) ./doc/common/tables/swift-proxy-server-filter-proxy-logging.xml:39(td) ./doc/common/tables/swift-proxy-server-filter-proxy-logging.xml:42(td) ./doc/common/tables/swift-proxy-server-filter-proxy-logging.xml:45(td) ./doc/common/tables/swift-proxy-server-filter-proxy-logging.xml:48(td) ./doc/common/tables/swift-proxy-server-filter-proxy-logging.xml:51(td) ./doc/common/tables/swift-proxy-server-filter-proxy-logging.xml:54(td) ./doc/common/tables/swift-proxy-server-filter-proxy-logging.xml:57(td) ./doc/common/tables/swift-proxy-server-filter-proxy-logging.xml:69(td) ./doc/common/tables/swift-rsyncd-account.xml:18(td) ./doc/common/tables/swift-rsyncd-account.xml:21(td) ./doc/common/tables/swift-rsyncd-account.xml:24(td) ./doc/common/tables/swift-rsyncd-account.xml:27(td) ./doc/common/tables/swift-container-server-filter-healthcheck.xml:21(td) ./doc/common/tables/swift-object-server-filter-recon.xml:24(td) ./doc/common/tables/swift-proxy-server-filter-catch_errors.xml:33(td) ./doc/common/tables/swift-proxy-server-filter-list-endpoints.xml:21(td) ./doc/common/tables/swift-memcache-memcache.xml:21(td) ./doc/common/tables/swift-proxy-server-filter-keystoneauth.xml:21(td) ./doc/common/tables/swift-proxy-server-filter-tempauth.xml:33(td) ./doc/common/tables/swift-proxy-server-filter-tempauth.xml:45(td) ./doc/common/tables/swift-proxy-server-filter-tempauth.xml:51(td) ./doc/common/tables/swift-proxy-server-filter-tempauth.xml:54(td) ./doc/common/tables/swift-proxy-server-filter-tempauth.xml:57(td) ./doc/common/tables/swift-proxy-server-filter-tempauth.xml:60(td) ./doc/common/tables/swift-object-server-object-replicator.xml:48(td) ./doc/common/tables/swift-object-server-object-replicator.xml:69(td) ./doc/common/tables/swift-dispersion-dispersion.xml:24(td) ./doc/common/tables/swift-dispersion-dispersion.xml:33(td) ./doc/common/tables/swift-dispersion-dispersion.xml:42(td) ./doc/common/tables/swift-dispersion-dispersion.xml:48(td) ./doc/common/tables/swift-dispersion-dispersion.xml:51(td) ./doc/common/tables/swift-dispersion-dispersion.xml:57(td) ./doc/common/tables/swift-dispersion-dispersion.xml:60(td) ./doc/common/tables/swift-dispersion-dispersion.xml:63(td) ./doc/common/tables/swift-proxy-server-filter-authtoken.xml:18(td) ./doc/common/tables/swift-proxy-server-filter-authtoken.xml:21(td) ./doc/common/tables/swift-proxy-server-filter-authtoken.xml:24(td) ./doc/common/tables/swift-proxy-server-filter-authtoken.xml:27(td) ./doc/common/tables/swift-proxy-server-filter-authtoken.xml:30(td) ./doc/common/tables/swift-proxy-server-filter-authtoken.xml:33(td) ./doc/common/tables/swift-proxy-server-filter-authtoken.xml:36(td) ./doc/common/tables/swift-proxy-server-filter-authtoken.xml:39(td) ./doc/common/tables/swift-proxy-server-filter-authtoken.xml:42(td) ./doc/common/tables/swift-object-server-app-object-server.xml:33(td) ./doc/common/tables/swift-proxy-server-DEFAULT.xml:55(td) ./doc/common/tables/swift-proxy-server-DEFAULT.xml:67(td) ./doc/common/tables/swift-proxy-server-DEFAULT.xml:73(td) ./doc/common/tables/swift-drive-audit-drive-audit.xml:39(td) ./doc/common/tables/swift-object-expirer-pipeline-main.xml:18(td) ./doc/common/tables/swift-rsyncd-container.xml:18(td) ./doc/common/tables/swift-rsyncd-container.xml:21(td) ./doc/common/tables/swift-rsyncd-container.xml:24(td) ./doc/common/tables/swift-rsyncd-container.xml:27(td) ./doc/common/tables/swift-object-server-filter-healthcheck.xml:21(td) ./doc/common/tables/swift-account-server-pipeline-main.xml:18(td) ./doc/common/tables/swift-object-expirer-object-expirer.xml:24(td) ./doc/common/tables/swift-object-expirer-object-expirer.xml:30(td) ./doc/common/tables/swift-proxy-server-pipeline-main.xml:18(td) ./doc/common/tables/swift-proxy-server-filter-cname_lookup.xml:33(td) ./doc/common/tables/swift-account-server-account-reaper.xml:45(td) ./doc/common/tables/swift-proxy-server-filter-domain_remap.xml:33(td) +msgid "No help text available for this option" +msgstr "" + +#: ./doc/common/tables/swift-proxy-server-filter-cache.xml:36(td) ./doc/common/tables/swift-memcache-memcache.xml:18(td) +msgid "memcache_servers = 127.0.0.1:11211" +msgstr "" + +#: ./doc/common/tables/swift-proxy-server-filter-cache.xml:36(td) ./doc/common/tables/swift-memcache-memcache.xml:18(td) +msgid "Comma separated list of memcached servers ip:port services" +msgstr "" + +#: ./doc/common/tables/swift-proxy-server-filter-cache.xml:39(td) ./doc/common/tables/swift-memcache-memcache.xml:21(td) +msgid "memcache_serialization_support = 2" +msgstr "" + +#: ./doc/common/tables/neutron-ml2_l2pop.xml:8(caption) +msgid "Description of configuration options for ml2_l2pop" +msgstr "" + +#: ./doc/common/tables/neutron-ml2_l2pop.xml:19(td) +msgid "agent_boot_time = 180" +msgstr "" + +#: ./doc/common/tables/neutron-ml2_l2pop.xml:20(td) +msgid "(IntOpt) Delay within which agent is expected to update existing ports whent it restarts" +msgstr "" + +#: ./doc/common/tables/glance-qpid.xml:8(caption) ./doc/common/tables/neutron-qpid.xml:8(caption) ./doc/common/tables/nova-qpid.xml:8(caption) +msgid "Description of configuration options for qpid" +msgstr "" + +#: ./doc/common/tables/glance-qpid.xml:22(td) ./doc/common/tables/cinder-rpc.xml:86(td) ./doc/common/tables/neutron-qpid.xml:19(td) ./doc/common/tables/nova-qpid.xml:22(td) +msgid "qpid_heartbeat = 60" +msgstr "" + +#: ./doc/common/tables/glance-qpid.xml:23(td) ./doc/common/tables/cinder-rpc.xml:87(td) ./doc/common/tables/neutron-qpid.xml:20(td) ./doc/common/tables/nova-qpid.xml:23(td) +msgid "(IntOpt) Seconds between connection keepalive heartbeats" +msgstr "" + +#: ./doc/common/tables/glance-qpid.xml:26(td) ./doc/common/tables/cinder-rpc.xml:90(td) ./doc/common/tables/neutron-qpid.xml:23(td) ./doc/common/tables/nova-qpid.xml:26(td) +msgid "qpid_hostname = localhost" +msgstr "" + +#: ./doc/common/tables/glance-qpid.xml:27(td) ./doc/common/tables/cinder-rpc.xml:91(td) ./doc/common/tables/neutron-qpid.xml:24(td) ./doc/common/tables/nova-qpid.xml:27(td) +msgid "(StrOpt) Qpid broker hostname" +msgstr "" + +#: ./doc/common/tables/glance-qpid.xml:30(td) ./doc/common/tables/cinder-rpc.xml:94(td) ./doc/common/tables/neutron-qpid.xml:27(td) ./doc/common/tables/nova-qpid.xml:30(td) +msgid "qpid_hosts = $qpid_hostname:$qpid_port" +msgstr "" + +#: ./doc/common/tables/glance-qpid.xml:31(td) ./doc/common/tables/cinder-rpc.xml:95(td) ./doc/common/tables/neutron-qpid.xml:28(td) ./doc/common/tables/nova-qpid.xml:31(td) +msgid "(ListOpt) Qpid HA cluster host:port pairs" +msgstr "" + +#: ./doc/common/tables/glance-qpid.xml:34(td) ./doc/common/tables/cinder-rpc.xml:98(td) ./doc/common/tables/neutron-qpid.xml:31(td) ./doc/common/tables/nova-qpid.xml:34(td) +msgid "qpid_password =" +msgstr "" + +#: ./doc/common/tables/glance-qpid.xml:35(td) +msgid "(StrOpt) Password for Qpid connection" +msgstr "" + +#: ./doc/common/tables/glance-qpid.xml:38(td) ./doc/common/tables/cinder-rpc.xml:102(td) ./doc/common/tables/neutron-qpid.xml:35(td) ./doc/common/tables/nova-qpid.xml:38(td) +msgid "qpid_port = 5672" +msgstr "" + +#: ./doc/common/tables/glance-qpid.xml:39(td) ./doc/common/tables/cinder-rpc.xml:103(td) ./doc/common/tables/neutron-qpid.xml:36(td) ./doc/common/tables/nova-qpid.xml:39(td) +msgid "(IntOpt) Qpid broker port" +msgstr "" + +#: ./doc/common/tables/glance-qpid.xml:42(td) ./doc/common/tables/cinder-rpc.xml:106(td) ./doc/common/tables/neutron-qpid.xml:39(td) ./doc/common/tables/nova-qpid.xml:42(td) +msgid "qpid_protocol = tcp" +msgstr "" + +#: ./doc/common/tables/glance-qpid.xml:43(td) ./doc/common/tables/cinder-rpc.xml:107(td) ./doc/common/tables/neutron-qpid.xml:40(td) ./doc/common/tables/nova-qpid.xml:43(td) +msgid "(StrOpt) Transport to use, either 'tcp' or 'ssl'" +msgstr "" + +#: ./doc/common/tables/glance-qpid.xml:46(td) ./doc/common/tables/cinder-rpc.xml:110(td) ./doc/common/tables/neutron-qpid.xml:43(td) ./doc/common/tables/nova-qpid.xml:46(td) +msgid "qpid_sasl_mechanisms =" +msgstr "" + +#: ./doc/common/tables/glance-qpid.xml:47(td) ./doc/common/tables/cinder-rpc.xml:111(td) ./doc/common/tables/neutron-qpid.xml:44(td) ./doc/common/tables/nova-qpid.xml:47(td) +msgid "(StrOpt) Space separated list of SASL mechanisms to use for auth" +msgstr "" + +#: ./doc/common/tables/glance-qpid.xml:50(td) ./doc/common/tables/cinder-rpc.xml:114(td) ./doc/common/tables/neutron-qpid.xml:47(td) ./doc/common/tables/nova-qpid.xml:50(td) +msgid "qpid_tcp_nodelay = True" +msgstr "" + +#: ./doc/common/tables/glance-qpid.xml:51(td) ./doc/common/tables/cinder-rpc.xml:115(td) ./doc/common/tables/neutron-qpid.xml:48(td) ./doc/common/tables/nova-qpid.xml:51(td) +msgid "(BoolOpt) Disable Nagle algorithm" +msgstr "" + +#: ./doc/common/tables/glance-qpid.xml:54(td) ./doc/common/tables/cinder-rpc.xml:118(td) ./doc/common/tables/neutron-qpid.xml:51(td) ./doc/common/tables/nova-qpid.xml:54(td) +msgid "qpid_topology_version = 1" +msgstr "" + +#: ./doc/common/tables/glance-qpid.xml:55(td) ./doc/common/tables/cinder-rpc.xml:119(td) ./doc/common/tables/neutron-qpid.xml:52(td) ./doc/common/tables/nova-qpid.xml:55(td) +msgid "(IntOpt) The qpid topology version to use. Version 1 is what was originally used by impl_qpid. Version 2 includes some backwards-incompatible changes that allow broker federation to work. Users should update to version 2 when they are able to take everything down, as it requires a clean break." +msgstr "" + +#: ./doc/common/tables/glance-qpid.xml:58(td) ./doc/common/tables/cinder-rpc.xml:122(td) ./doc/common/tables/neutron-qpid.xml:55(td) ./doc/common/tables/nova-qpid.xml:58(td) +msgid "qpid_username =" +msgstr "" + +#: ./doc/common/tables/glance-qpid.xml:59(td) +msgid "(StrOpt) Username for Qpid connection" +msgstr "" + +#: ./doc/common/tables/swift-container-server-DEFAULT.xml:7(literal) ./doc/common/tables/swift-container-server-container-updater.xml:7(literal) ./doc/common/tables/swift-container-server-container-replicator.xml:7(literal) ./doc/common/tables/swift-container-server-container-sync.xml:7(literal) ./doc/common/tables/swift-container-server-pipeline-main.xml:7(literal) ./doc/common/tables/swift-container-server-app-container-server.xml:7(literal) ./doc/common/tables/swift-container-server-filter-healthcheck.xml:7(literal) ./doc/common/tables/swift-container-server-container-auditor.xml:7(literal) ./doc/common/tables/swift-container-server-filter-recon.xml:7(literal) +msgid "container-server.conf-sample" +msgstr "" + +#: ./doc/common/tables/swift-container-server-DEFAULT.xml:18(td) ./doc/common/tables/swift-object-server-DEFAULT.xml:18(td) ./doc/common/tables/swift-account-server-DEFAULT.xml:18(td) ./doc/common/tables/swift-proxy-server-DEFAULT.xml:18(td) +msgid "bind_ip = 0.0.0.0" +msgstr "" + +#: ./doc/common/tables/swift-container-server-DEFAULT.xml:18(td) ./doc/common/tables/swift-object-server-DEFAULT.xml:18(td) ./doc/common/tables/swift-account-server-DEFAULT.xml:18(td) ./doc/common/tables/swift-proxy-server-DEFAULT.xml:18(td) +msgid "IP Address for server to bind to" +msgstr "" + +#: ./doc/common/tables/swift-container-server-DEFAULT.xml:21(td) +msgid "bind_port = 6001" +msgstr "" + +#: ./doc/common/tables/swift-container-server-DEFAULT.xml:21(td) ./doc/common/tables/swift-object-server-DEFAULT.xml:21(td) ./doc/common/tables/swift-account-server-DEFAULT.xml:21(td) ./doc/common/tables/swift-proxy-server-DEFAULT.xml:21(td) +msgid "Port for server to bind to" +msgstr "" + +#: ./doc/common/tables/swift-container-server-DEFAULT.xml:24(td) ./doc/common/tables/swift-object-server-DEFAULT.xml:24(td) ./doc/common/tables/swift-account-server-DEFAULT.xml:24(td) ./doc/common/tables/swift-proxy-server-DEFAULT.xml:24(td) +msgid "bind_timeout = 30" +msgstr "" + +#: ./doc/common/tables/swift-container-server-DEFAULT.xml:24(td) ./doc/common/tables/swift-object-server-DEFAULT.xml:24(td) ./doc/common/tables/swift-account-server-DEFAULT.xml:24(td) ./doc/common/tables/swift-proxy-server-DEFAULT.xml:24(td) +msgid "Seconds to attempt bind before giving up" +msgstr "" + +#: ./doc/common/tables/swift-container-server-DEFAULT.xml:27(td) ./doc/common/tables/neutron-wsgi.xml:19(td) ./doc/common/tables/swift-object-server-DEFAULT.xml:27(td) ./doc/common/tables/swift-account-server-DEFAULT.xml:27(td) ./doc/common/tables/glance-common.xml:30(td) ./doc/common/tables/cinder-log.xml:22(td) ./doc/common/tables/swift-proxy-server-DEFAULT.xml:27(td) +msgid "backlog = 4096" +msgstr "" + +#: ./doc/common/tables/swift-container-server-DEFAULT.xml:27(td) ./doc/common/tables/swift-object-server-DEFAULT.xml:27(td) ./doc/common/tables/swift-account-server-DEFAULT.xml:27(td) ./doc/common/tables/swift-proxy-server-DEFAULT.xml:27(td) +msgid "Maximum number of allowed pending TCP connections" +msgstr "" + +#: ./doc/common/tables/swift-container-server-DEFAULT.xml:30(td) ./doc/common/tables/swift-object-expirer-DEFAULT.xml:21(td) ./doc/common/tables/swift-object-server-DEFAULT.xml:30(td) ./doc/common/tables/swift-account-server-DEFAULT.xml:30(td) ./doc/common/tables/swift-proxy-server-DEFAULT.xml:33(td) +msgid "user = swift" +msgstr "" + +#: ./doc/common/tables/swift-container-server-DEFAULT.xml:30(td) ./doc/common/tables/swift-object-expirer-DEFAULT.xml:21(td) ./doc/common/tables/swift-swift-bench-bench.xml:21(td) ./doc/common/tables/swift-object-server-DEFAULT.xml:30(td) ./doc/common/tables/swift-account-server-DEFAULT.xml:30(td) ./doc/common/tables/swift-proxy-server-DEFAULT.xml:33(td) +msgid "User to run as" +msgstr "" + +#: ./doc/common/tables/swift-container-server-DEFAULT.xml:33(td) ./doc/common/tables/swift-object-expirer-DEFAULT.xml:18(td) ./doc/common/tables/swift-object-server-DEFAULT.xml:33(td) ./doc/common/tables/swift-account-server-DEFAULT.xml:33(td) ./doc/common/tables/swift-dispersion-dispersion.xml:45(td) ./doc/common/tables/swift-proxy-server-DEFAULT.xml:30(td) +msgid "swift_dir = /etc/swift" +msgstr "" + +#: ./doc/common/tables/swift-container-server-DEFAULT.xml:33(td) ./doc/common/tables/swift-object-expirer-DEFAULT.xml:18(td) ./doc/common/tables/swift-object-server-DEFAULT.xml:33(td) ./doc/common/tables/swift-account-server-DEFAULT.xml:33(td) ./doc/common/tables/swift-dispersion-dispersion.xml:45(td) ./doc/common/tables/swift-proxy-server-DEFAULT.xml:30(td) +msgid "Swift configuration directory" +msgstr "" + +#: ./doc/common/tables/swift-container-server-DEFAULT.xml:36(td) ./doc/common/tables/swift-object-server-DEFAULT.xml:36(td) ./doc/common/tables/swift-account-server-DEFAULT.xml:36(td) +msgid "devices = /srv/node" +msgstr "" + +#: ./doc/common/tables/swift-container-server-DEFAULT.xml:36(td) ./doc/common/tables/swift-swift-bench-bench.xml:90(td) ./doc/common/tables/swift-object-server-DEFAULT.xml:36(td) ./doc/common/tables/swift-account-server-DEFAULT.xml:36(td) +msgid "Parent directory of where devices are mounted" +msgstr "" + +#: ./doc/common/tables/swift-container-server-DEFAULT.xml:39(td) ./doc/common/tables/swift-object-server-DEFAULT.xml:39(td) ./doc/common/tables/swift-account-server-DEFAULT.xml:39(td) +msgid "mount_check = true" +msgstr "" + +#: ./doc/common/tables/swift-container-server-DEFAULT.xml:39(td) ./doc/common/tables/swift-object-server-DEFAULT.xml:39(td) ./doc/common/tables/swift-account-server-DEFAULT.xml:39(td) +msgid "Whether or not check if the devices are mounted to prevent accidentally writing to the root device" +msgstr "" + +#: ./doc/common/tables/swift-container-server-DEFAULT.xml:42(td) ./doc/common/tables/swift-object-server-DEFAULT.xml:42(td) ./doc/common/tables/swift-account-server-DEFAULT.xml:42(td) +msgid "disable_fallocate = false" +msgstr "" + +#: ./doc/common/tables/swift-container-server-DEFAULT.xml:42(td) ./doc/common/tables/swift-object-server-DEFAULT.xml:42(td) ./doc/common/tables/swift-account-server-DEFAULT.xml:42(td) +msgid "Disable \"fast fail\" fallocate checks if the underlying filesystem does not support it." +msgstr "" + +#: ./doc/common/tables/swift-container-server-DEFAULT.xml:45(td) ./doc/common/tables/swift-object-server-DEFAULT.xml:48(td) ./doc/common/tables/swift-account-server-DEFAULT.xml:45(td) ./doc/common/tables/swift-proxy-server-DEFAULT.xml:36(td) +msgid "workers = auto" +msgstr "" + +#: ./doc/common/tables/swift-container-server-DEFAULT.xml:45(td) ./doc/common/tables/swift-object-server-DEFAULT.xml:48(td) ./doc/common/tables/swift-account-server-DEFAULT.xml:45(td) ./doc/common/tables/swift-proxy-server-DEFAULT.xml:36(td) +msgid "a much higher value, one can reduce the impact of slow file system operations in one request from negatively impacting other requests." +msgstr "" + +#: ./doc/common/tables/swift-container-server-DEFAULT.xml:48(td) ./doc/common/tables/swift-object-server-DEFAULT.xml:51(td) ./doc/common/tables/swift-account-server-DEFAULT.xml:48(td) ./doc/common/tables/swift-proxy-server-DEFAULT.xml:39(td) +msgid "max_clients = 1024" +msgstr "" + +#: ./doc/common/tables/swift-container-server-DEFAULT.xml:48(td) ./doc/common/tables/swift-object-server-DEFAULT.xml:51(td) ./doc/common/tables/swift-account-server-DEFAULT.xml:48(td) ./doc/common/tables/swift-proxy-server-DEFAULT.xml:39(td) +msgid "Maximum number of clients one worker can process simultaneously Lowering the number of clients handled per worker, and raising the number of workers can lessen the impact that a CPU intensive, or blocking, request can have on other requests served by the same worker. If the maximum number of clients is set to one, then a given worker will not perform another call while processing, allowing other workers a chance to process it." +msgstr "" + +#: ./doc/common/tables/swift-container-server-DEFAULT.xml:58(td) +msgid "allowed_sync_hosts = 127.0.0.1" +msgstr "" + +#: ./doc/common/tables/swift-container-server-DEFAULT.xml:61(td) ./doc/common/tables/swift-object-expirer-DEFAULT.xml:24(td) ./doc/common/tables/swift-object-server-DEFAULT.xml:61(td) ./doc/common/tables/swift-account-server-DEFAULT.xml:58(td) ./doc/common/tables/swift-proxy-server-DEFAULT.xml:58(td) +msgid "log_name = swift" +msgstr "" + +#: ./doc/common/tables/swift-container-server-DEFAULT.xml:61(td) ./doc/common/tables/swift-container-server-container-updater.xml:18(td) ./doc/common/tables/swift-container-server-container-replicator.xml:18(td) ./doc/common/tables/swift-container-server-container-sync.xml:18(td) ./doc/common/tables/swift-object-server-object-auditor.xml:18(td) ./doc/common/tables/swift-object-expirer-DEFAULT.xml:24(td) ./doc/common/tables/swift-object-server-object-updater.xml:18(td) ./doc/common/tables/swift-account-server-account-auditor.xml:18(td) ./doc/common/tables/swift-object-server-DEFAULT.xml:61(td) ./doc/common/tables/swift-account-server-DEFAULT.xml:58(td) ./doc/common/tables/swift-container-server-container-auditor.xml:18(td) ./doc/common/tables/swift-object-server-object-replicator.xml:18(td) ./doc/common/tables/swift-account-server-account-replicator.xml:18(td) ./doc/common/tables/swift-proxy-server-DEFAULT.xml:58(td) ./doc/common/tables/swift-account-server-account-reaper.xml:18(td) +msgid "Label used when logging" +msgstr "" + +#: ./doc/common/tables/swift-container-server-DEFAULT.xml:64(td) ./doc/common/tables/swift-container-server-container-updater.xml:21(td) ./doc/common/tables/swift-container-server-container-replicator.xml:21(td) ./doc/common/tables/swift-container-server-container-sync.xml:21(td) ./doc/common/tables/swift-object-server-object-auditor.xml:21(td) ./doc/common/tables/swift-object-expirer-DEFAULT.xml:27(td) ./doc/common/tables/swift-object-server-object-updater.xml:21(td) ./doc/common/tables/swift-account-server-account-auditor.xml:21(td) ./doc/common/tables/swift-account-server-account-auditor.xml:33(td) ./doc/common/tables/swift-object-server-DEFAULT.xml:64(td) ./doc/common/tables/swift-account-server-DEFAULT.xml:61(td) ./doc/common/tables/swift-container-server-container-auditor.xml:21(td) ./doc/common/tables/swift-object-server-object-replicator.xml:21(td) ./doc/common/tables/swift-account-server-account-replicator.xml:21(td) ./doc/common/tables/swift-proxy-server-DEFAULT.xml:61(td) ./doc/common/tables/swift-drive-audit-drive-audit.xml:21(td) ./doc/common/tables/swift-account-server-account-reaper.xml:21(td) +msgid "log_facility = LOG_LOCAL0" +msgstr "" + +#: ./doc/common/tables/swift-container-server-DEFAULT.xml:67(td) ./doc/common/tables/swift-container-server-container-updater.xml:24(td) ./doc/common/tables/swift-container-server-container-replicator.xml:24(td) ./doc/common/tables/swift-container-server-container-sync.xml:24(td) ./doc/common/tables/swift-object-server-object-auditor.xml:24(td) ./doc/common/tables/swift-object-expirer-DEFAULT.xml:30(td) ./doc/common/tables/swift-object-server-object-updater.xml:24(td) ./doc/common/tables/swift-account-server-account-auditor.xml:24(td) ./doc/common/tables/swift-account-server-account-auditor.xml:36(td) ./doc/common/tables/swift-object-server-DEFAULT.xml:67(td) ./doc/common/tables/swift-account-server-DEFAULT.xml:64(td) ./doc/common/tables/swift-container-server-container-auditor.xml:24(td) ./doc/common/tables/swift-object-server-object-replicator.xml:24(td) ./doc/common/tables/swift-account-server-account-replicator.xml:24(td) ./doc/common/tables/swift-proxy-server-DEFAULT.xml:64(td) ./doc/common/tables/swift-drive-audit-drive-audit.xml:24(td) ./doc/common/tables/swift-account-server-account-reaper.xml:24(td) +msgid "log_level = INFO" +msgstr "" + +#: ./doc/common/tables/swift-container-server-DEFAULT.xml:67(td) ./doc/common/tables/swift-container-server-container-updater.xml:24(td) ./doc/common/tables/swift-container-server-container-replicator.xml:24(td) ./doc/common/tables/swift-container-server-container-sync.xml:24(td) ./doc/common/tables/swift-object-server-object-auditor.xml:24(td) ./doc/common/tables/swift-object-expirer-DEFAULT.xml:30(td) ./doc/common/tables/swift-object-server-object-updater.xml:24(td) ./doc/common/tables/swift-account-server-account-auditor.xml:24(td) ./doc/common/tables/swift-account-server-account-auditor.xml:36(td) ./doc/common/tables/swift-object-server-DEFAULT.xml:67(td) ./doc/common/tables/swift-account-server-DEFAULT.xml:64(td) ./doc/common/tables/swift-container-server-container-auditor.xml:24(td) ./doc/common/tables/swift-object-server-object-replicator.xml:24(td) ./doc/common/tables/swift-account-server-account-replicator.xml:24(td) ./doc/common/tables/swift-proxy-server-DEFAULT.xml:64(td) ./doc/common/tables/swift-drive-audit-drive-audit.xml:24(td) ./doc/common/tables/swift-account-server-account-reaper.xml:24(td) +msgid "Logging level" +msgstr "" + +#: ./doc/common/tables/swift-container-server-DEFAULT.xml:70(td) ./doc/common/tables/swift-container-server-container-updater.xml:27(td) ./doc/common/tables/swift-container-server-container-replicator.xml:27(td) ./doc/common/tables/swift-container-server-container-sync.xml:27(td) ./doc/common/tables/swift-object-server-object-auditor.xml:27(td) ./doc/common/tables/swift-object-expirer-DEFAULT.xml:33(td) ./doc/common/tables/swift-object-server-object-updater.xml:27(td) ./doc/common/tables/swift-account-server-account-auditor.xml:27(td) ./doc/common/tables/swift-object-server-DEFAULT.xml:70(td) ./doc/common/tables/swift-account-server-DEFAULT.xml:67(td) ./doc/common/tables/swift-container-server-container-auditor.xml:27(td) ./doc/common/tables/swift-object-server-object-replicator.xml:27(td) ./doc/common/tables/swift-account-server-account-replicator.xml:27(td) ./doc/common/tables/swift-proxy-server-DEFAULT.xml:70(td) ./doc/common/tables/swift-drive-audit-drive-audit.xml:27(td) ./doc/common/tables/swift-account-server-account-reaper.xml:27(td) +msgid "log_address = /dev/log" +msgstr "" + +#: ./doc/common/tables/swift-container-server-DEFAULT.xml:70(td) ./doc/common/tables/swift-container-server-container-updater.xml:27(td) ./doc/common/tables/swift-container-server-container-replicator.xml:27(td) ./doc/common/tables/swift-container-server-container-sync.xml:27(td) ./doc/common/tables/swift-object-server-object-auditor.xml:27(td) ./doc/common/tables/swift-object-expirer-DEFAULT.xml:33(td) ./doc/common/tables/swift-object-server-object-updater.xml:27(td) ./doc/common/tables/swift-account-server-account-auditor.xml:27(td) ./doc/common/tables/swift-object-server-DEFAULT.xml:70(td) ./doc/common/tables/swift-account-server-DEFAULT.xml:67(td) ./doc/common/tables/swift-container-server-container-auditor.xml:27(td) ./doc/common/tables/swift-object-server-object-replicator.xml:27(td) ./doc/common/tables/swift-account-server-account-replicator.xml:27(td) ./doc/common/tables/swift-proxy-server-DEFAULT.xml:70(td) ./doc/common/tables/swift-drive-audit-drive-audit.xml:27(td) ./doc/common/tables/swift-account-server-account-reaper.xml:27(td) +msgid "Location where syslog sends the logs to" +msgstr "" + +#: ./doc/common/tables/swift-container-server-DEFAULT.xml:73(td) ./doc/common/tables/swift-object-expirer-DEFAULT.xml:36(td) ./doc/common/tables/swift-object-server-DEFAULT.xml:73(td) ./doc/common/tables/swift-account-server-DEFAULT.xml:70(td) ./doc/common/tables/swift-proxy-server-DEFAULT.xml:76(td) +msgid "log_custom_handlers =" +msgstr "" + +#: ./doc/common/tables/swift-container-server-DEFAULT.xml:73(td) ./doc/common/tables/swift-object-expirer-DEFAULT.xml:36(td) ./doc/common/tables/swift-object-server-DEFAULT.xml:73(td) ./doc/common/tables/swift-account-server-DEFAULT.xml:70(td) ./doc/common/tables/swift-proxy-server-DEFAULT.xml:76(td) +msgid "Comma-separated list of functions to call to setup custom log handlers." +msgstr "" + +#: ./doc/common/tables/swift-container-server-DEFAULT.xml:76(td) ./doc/common/tables/swift-object-expirer-DEFAULT.xml:39(td) ./doc/common/tables/swift-object-server-DEFAULT.xml:76(td) ./doc/common/tables/swift-account-server-DEFAULT.xml:73(td) ./doc/common/tables/swift-proxy-server-DEFAULT.xml:79(td) +msgid "log_udp_host =" +msgstr "" + +#: ./doc/common/tables/swift-container-server-DEFAULT.xml:76(td) ./doc/common/tables/swift-object-expirer-DEFAULT.xml:39(td) ./doc/common/tables/swift-object-server-DEFAULT.xml:76(td) ./doc/common/tables/swift-account-server-DEFAULT.xml:73(td) ./doc/common/tables/swift-proxy-server-DEFAULT.xml:79(td) +msgid "If not set, the UDB receiver for syslog is disabled." +msgstr "" + +#: ./doc/common/tables/swift-container-server-DEFAULT.xml:79(td) ./doc/common/tables/swift-object-expirer-DEFAULT.xml:42(td) ./doc/common/tables/swift-object-server-DEFAULT.xml:79(td) ./doc/common/tables/swift-account-server-DEFAULT.xml:76(td) ./doc/common/tables/swift-proxy-server-DEFAULT.xml:82(td) +msgid "log_udp_port = 514" +msgstr "" + +#: ./doc/common/tables/swift-container-server-DEFAULT.xml:79(td) ./doc/common/tables/swift-object-expirer-DEFAULT.xml:42(td) ./doc/common/tables/swift-object-server-DEFAULT.xml:79(td) ./doc/common/tables/swift-account-server-DEFAULT.xml:76(td) ./doc/common/tables/swift-proxy-server-DEFAULT.xml:82(td) +msgid "Port value for UDB receiver, if enabled." +msgstr "" + +#: ./doc/common/tables/swift-container-server-DEFAULT.xml:82(td) ./doc/common/tables/swift-object-expirer-DEFAULT.xml:45(td) ./doc/common/tables/swift-object-server-DEFAULT.xml:82(td) ./doc/common/tables/swift-account-server-DEFAULT.xml:79(td) ./doc/common/tables/swift-proxy-server-DEFAULT.xml:85(td) +msgid "log_statsd_host = localhost" +msgstr "" + +#: ./doc/common/tables/swift-container-server-DEFAULT.xml:82(td) ./doc/common/tables/swift-object-expirer-DEFAULT.xml:45(td) ./doc/common/tables/swift-object-server-DEFAULT.xml:82(td) ./doc/common/tables/swift-account-server-DEFAULT.xml:79(td) ./doc/common/tables/swift-proxy-server-DEFAULT.xml:85(td) +msgid "If not set, the StatsD feature is disabled." +msgstr "" + +#: ./doc/common/tables/swift-container-server-DEFAULT.xml:85(td) ./doc/common/tables/swift-object-expirer-DEFAULT.xml:48(td) ./doc/common/tables/swift-object-server-DEFAULT.xml:85(td) ./doc/common/tables/swift-account-server-DEFAULT.xml:82(td) ./doc/common/tables/swift-proxy-server-DEFAULT.xml:88(td) +msgid "log_statsd_port = 8125" +msgstr "" + +#: ./doc/common/tables/swift-container-server-DEFAULT.xml:85(td) ./doc/common/tables/swift-object-expirer-DEFAULT.xml:48(td) ./doc/common/tables/swift-object-server-DEFAULT.xml:85(td) ./doc/common/tables/swift-account-server-DEFAULT.xml:82(td) ./doc/common/tables/swift-proxy-server-DEFAULT.xml:88(td) +msgid "Port value for the StatsD server." +msgstr "" + +#: ./doc/common/tables/swift-container-server-DEFAULT.xml:88(td) ./doc/common/tables/swift-object-expirer-DEFAULT.xml:51(td) ./doc/common/tables/swift-object-server-DEFAULT.xml:88(td) ./doc/common/tables/swift-account-server-DEFAULT.xml:85(td) ./doc/common/tables/swift-proxy-server-DEFAULT.xml:91(td) +msgid "log_statsd_default_sample_rate = 1.0" +msgstr "" + +#: ./doc/common/tables/swift-container-server-DEFAULT.xml:88(td) ./doc/common/tables/swift-object-expirer-DEFAULT.xml:51(td) ./doc/common/tables/swift-object-server-DEFAULT.xml:88(td) ./doc/common/tables/swift-account-server-DEFAULT.xml:85(td) ./doc/common/tables/swift-proxy-server-DEFAULT.xml:91(td) +msgid "Defines the probability of sending a sample for any given event or timing measurement." +msgstr "" + +#: ./doc/common/tables/swift-container-server-DEFAULT.xml:92(td) ./doc/common/tables/swift-object-expirer-DEFAULT.xml:55(td) ./doc/common/tables/swift-object-server-DEFAULT.xml:92(td) ./doc/common/tables/swift-account-server-DEFAULT.xml:89(td) ./doc/common/tables/swift-proxy-server-DEFAULT.xml:95(td) +msgid "log_statsd_sample_rate_factor = 1.0" +msgstr "" + +#: ./doc/common/tables/swift-container-server-DEFAULT.xml:92(td) ./doc/common/tables/swift-object-expirer-DEFAULT.xml:55(td) ./doc/common/tables/swift-object-server-DEFAULT.xml:92(td) ./doc/common/tables/swift-account-server-DEFAULT.xml:89(td) ./doc/common/tables/swift-proxy-server-DEFAULT.xml:95(td) +msgid "Not recommended to set this to a value less than 1.0, if frequency of logging is too high, tune the log_statsd_default_sample_rate instead." +msgstr "" + +#: ./doc/common/tables/swift-container-server-DEFAULT.xml:97(td) ./doc/common/tables/swift-object-expirer-DEFAULT.xml:60(td) ./doc/common/tables/swift-object-server-DEFAULT.xml:97(td) ./doc/common/tables/swift-account-server-DEFAULT.xml:94(td) ./doc/common/tables/swift-proxy-server-DEFAULT.xml:100(td) +msgid "log_statsd_metric_prefix =" +msgstr "" + +#: ./doc/common/tables/swift-container-server-DEFAULT.xml:97(td) ./doc/common/tables/swift-object-expirer-DEFAULT.xml:60(td) ./doc/common/tables/swift-object-server-DEFAULT.xml:97(td) ./doc/common/tables/swift-account-server-DEFAULT.xml:94(td) ./doc/common/tables/swift-proxy-server-DEFAULT.xml:100(td) +msgid "Value will be prepended to every metric sent to the StatsD server." +msgstr "" + +#: ./doc/common/tables/swift-container-server-DEFAULT.xml:100(td) ./doc/common/tables/swift-account-server-DEFAULT.xml:97(td) +msgid "db_preallocation = off" +msgstr "" + +#: ./doc/common/tables/swift-container-server-DEFAULT.xml:100(td) ./doc/common/tables/swift-account-server-DEFAULT.xml:97(td) +msgid "If you don't mind the extra disk space usage in overhead, you can turn this on to preallocate disk space with SQLite databases to decrease fragmentation. underlying filesystem does not support it. to setup custom log handlers. bytes you'd like fallocate to reserve, whether there is space for the given file size or not. This is useful for systems that behave badly when they completely run out of space; you can make the services pretend they're out of space early. server. For most cases, this should be `egg:swift#account`. replication passes account can be reclaimed" +msgstr "" + +#: ./doc/common/tables/swift-container-server-DEFAULT.xml:103(td) ./doc/common/tables/swift-object-server-DEFAULT.xml:100(td) ./doc/common/tables/swift-account-server-DEFAULT.xml:100(td) ./doc/common/tables/swift-proxy-server-DEFAULT.xml:109(td) +msgid "eventlet_debug = false" +msgstr "" + +#: ./doc/common/tables/swift-container-server-DEFAULT.xml:103(td) ./doc/common/tables/swift-object-server-DEFAULT.xml:100(td) ./doc/common/tables/swift-account-server-DEFAULT.xml:100(td) ./doc/common/tables/swift-proxy-server-DEFAULT.xml:109(td) +msgid "If true, turn on debug logging for eventlet" +msgstr "" + +#: ./doc/common/tables/swift-container-server-DEFAULT.xml:106(td) ./doc/common/tables/swift-object-server-DEFAULT.xml:103(td) ./doc/common/tables/swift-account-server-DEFAULT.xml:103(td) +msgid "fallocate_reserve = 0" +msgstr "" + +#: ./doc/common/tables/swift-container-server-DEFAULT.xml:106(td) ./doc/common/tables/swift-object-server-DEFAULT.xml:103(td) ./doc/common/tables/swift-account-server-DEFAULT.xml:103(td) +msgid "You can set fallocate_reserve to the number of bytes you'd like fallocate to reserve, whether there is space for the given file size or not. This is useful for systems that behave badly when they completely run out of space; you can make the services pretend they're out of space early. server. For most cases, this should be `egg:swift#object`." +msgstr "" + +#: ./doc/common/tables/nova-volumes.xml:8(caption) +msgid "Description of configuration options for volumes" +msgstr "" + +#: ./doc/common/tables/nova-volumes.xml:22(td) ./doc/common/tables/glance-cinder.xml:22(td) +msgid "cinder_api_insecure = False" +msgstr "" + +#: ./doc/common/tables/nova-volumes.xml:23(td) ./doc/common/tables/glance-cinder.xml:23(td) +msgid "(BoolOpt) Allow to perform insecure SSL requests to cinder" +msgstr "" + +#: ./doc/common/tables/nova-volumes.xml:26(td) ./doc/common/tables/glance-cinder.xml:26(td) +msgid "cinder_ca_certificates_file = None" +msgstr "" + +#: ./doc/common/tables/nova-volumes.xml:27(td) +msgid "(StrOpt) Location of ca certificates file to use for cinder client requests." +msgstr "" + +#: ./doc/common/tables/nova-volumes.xml:30(td) ./doc/common/tables/glance-cinder.xml:30(td) +msgid "cinder_catalog_info = volume:cinder:publicURL" +msgstr "" + +#: ./doc/common/tables/nova-volumes.xml:31(td) ./doc/common/tables/glance-cinder.xml:31(td) +msgid "(StrOpt) Info to match when looking for cinder in the service catalog. Format is : separated values of the form: <service_type>:<service_name>:<endpoint_type>" +msgstr "" + +#: ./doc/common/tables/nova-volumes.xml:34(td) +msgid "cinder_cross_az_attach = True" +msgstr "" + +#: ./doc/common/tables/nova-volumes.xml:35(td) +msgid "(BoolOpt) Allow attach between instance and volume in different availability zones." +msgstr "" + +#: ./doc/common/tables/nova-volumes.xml:38(td) ./doc/common/tables/glance-cinder.xml:34(td) +msgid "cinder_endpoint_template = None" +msgstr "" + +#: ./doc/common/tables/nova-volumes.xml:39(td) ./doc/common/tables/glance-cinder.xml:35(td) +msgid "(StrOpt) Override service catalog lookup with template for cinder endpoint e.g. http://localhost:8776/v1/%(project_id)s" +msgstr "" + +#: ./doc/common/tables/nova-volumes.xml:42(td) ./doc/common/tables/glance-cinder.xml:38(td) +msgid "cinder_http_retries = 3" +msgstr "" + +#: ./doc/common/tables/nova-volumes.xml:43(td) ./doc/common/tables/glance-cinder.xml:39(td) +msgid "(IntOpt) Number of cinderclient retries on failed http calls" +msgstr "" + +#: ./doc/common/tables/nova-volumes.xml:46(td) ./doc/common/tables/cinder-compute.xml:46(td) ./doc/common/tables/glance-common.xml:82(td) +msgid "os_region_name = None" +msgstr "" + +#: ./doc/common/tables/nova-volumes.xml:47(td) ./doc/common/tables/cinder-compute.xml:47(td) +msgid "(StrOpt) region name of this node" +msgstr "" + +#: ./doc/common/tables/nova-volumes.xml:50(td) +msgid "volume_api_class = nova.volume.cinder.API" +msgstr "" + +#: ./doc/common/tables/nova-volumes.xml:51(td) ./doc/common/tables/cinder-api.xml:75(td) +msgid "(StrOpt) The full class name of the volume API class to use" +msgstr "" + +#: ./doc/common/tables/nova-volumes.xml:54(td) +msgid "volume_usage_poll_interval = 0" +msgstr "" + +#: ./doc/common/tables/nova-volumes.xml:55(td) +msgid "(IntOpt) Interval in seconds for gathering volume usages" +msgstr "" + +#: ./doc/common/tables/nova-volumes.xml:58(th) ./doc/common/tables/nova-tilera.xml:19(th) ./doc/common/tables/nova-baremetal.xml:19(th) +msgid "[baremetal]" +msgstr "" + +#: ./doc/common/tables/nova-volumes.xml:61(td) +msgid "iscsi_iqn_prefix = iqn.2010-10.org.openstack.baremetal" +msgstr "" + +#: ./doc/common/tables/nova-volumes.xml:62(td) +msgid "(StrOpt) iSCSI IQN prefix used in baremetal volume connections." +msgstr "" + +#: ./doc/common/tables/nova-volumes.xml:65(td) +msgid "volume_driver = nova.virt.baremetal.volume_driver.LibvirtVolumeDriver" +msgstr "" + +#: ./doc/common/tables/nova-volumes.xml:66(td) +msgid "(StrOpt) Baremetal volume driver." +msgstr "" + +#: ./doc/common/tables/nova-volumes.xml:69(th) ./doc/common/tables/nova-hyperv.xml:19(th) ./doc/common/tables/nova-configdrive.xml:42(th) +msgid "[hyperv]" +msgstr "" + +#: ./doc/common/tables/nova-volumes.xml:72(td) +msgid "force_volumeutils_v1 = False" +msgstr "" + +#: ./doc/common/tables/nova-volumes.xml:73(td) +msgid "(BoolOpt) Force V1 volume utility class" +msgstr "" + +#: ./doc/common/tables/nova-volumes.xml:76(td) +msgid "volume_attach_retry_count = 10" +msgstr "" + +#: ./doc/common/tables/nova-volumes.xml:77(td) +msgid "(IntOpt) The number of times to retry to attach a volume" +msgstr "" + +#: ./doc/common/tables/nova-volumes.xml:80(td) +msgid "volume_attach_retry_interval = 5" +msgstr "" + +#: ./doc/common/tables/nova-volumes.xml:81(td) +msgid "(IntOpt) Interval between volume attachment attempts, in seconds" +msgstr "" + +#: ./doc/common/tables/nova-volumes.xml:84(th) ./doc/common/tables/nova-hypervisor.xml:54(th) ./doc/common/tables/nova-livemigration.xml:26(th) ./doc/common/tables/nova-libvirt.xml:30(th) ./doc/common/tables/nova-xen.xml:58(th) +msgid "[libvirt]" +msgstr "" + +#: ./doc/common/tables/nova-volumes.xml:87(td) ./doc/common/tables/cinder-storage_glusterfs.xml:22(td) +msgid "glusterfs_mount_point_base = $state_path/mnt" +msgstr "" + +#: ./doc/common/tables/nova-volumes.xml:88(td) +msgid "(StrOpt) Dir where the glusterfs volume is mounted on the compute node" +msgstr "" + +#: ./doc/common/tables/nova-volumes.xml:91(td) ./doc/common/tables/cinder-storage_nfs.xml:22(td) +msgid "nfs_mount_options = None" +msgstr "" + +#: ./doc/common/tables/nova-volumes.xml:92(td) ./doc/common/tables/cinder-nexenta_nfs.xml:23(td) +msgid "(StrOpt) Mount options passed to the nfs client. See section of the nfs man page for details" +msgstr "" + +#: ./doc/common/tables/nova-volumes.xml:95(td) ./doc/common/tables/cinder-storage_nfs.xml:26(td) +msgid "nfs_mount_point_base = $state_path/mnt" +msgstr "" + +#: ./doc/common/tables/nova-volumes.xml:96(td) +msgid "(StrOpt) Dir where the nfs volume is mounted on the compute node" +msgstr "" + +#: ./doc/common/tables/nova-volumes.xml:99(td) +msgid "num_aoe_discover_tries = 3" +msgstr "" + +#: ./doc/common/tables/nova-volumes.xml:100(td) +msgid "(IntOpt) number of times to rediscover AoE target to find volume" +msgstr "" + +#: ./doc/common/tables/nova-volumes.xml:103(td) +msgid "num_iscsi_scan_tries = 3" +msgstr "" + +#: ./doc/common/tables/nova-volumes.xml:104(td) +msgid "(IntOpt) number of times to rescan iSCSI target to find volume" +msgstr "" + +#: ./doc/common/tables/nova-volumes.xml:107(td) ./doc/common/tables/cinder-storage.xml:90(td) +msgid "num_iser_scan_tries = 3" +msgstr "" + +#: ./doc/common/tables/nova-volumes.xml:108(td) +msgid "(IntOpt) number of times to rescan iSER target to find volume" +msgstr "" + +#: ./doc/common/tables/nova-volumes.xml:111(td) +msgid "qemu_allowed_storage_drivers =" +msgstr "" + +#: ./doc/common/tables/nova-volumes.xml:112(td) +msgid "(ListOpt) Protocols listed here will be accessed directly from QEMU. Currently supported protocols: [gluster]" +msgstr "" + +#: ./doc/common/tables/nova-volumes.xml:115(td) ./doc/common/tables/cinder-storage_ceph.xml:38(td) +msgid "rbd_secret_uuid = None" +msgstr "" + +#: ./doc/common/tables/nova-volumes.xml:116(td) ./doc/common/tables/cinder-storage_ceph.xml:39(td) +msgid "(StrOpt) the libvirt uuid of the secret for the rbd_uservolumes" +msgstr "" + +#: ./doc/common/tables/nova-volumes.xml:119(td) ./doc/common/tables/cinder-storage_ceph.xml:42(td) +msgid "rbd_user = None" +msgstr "" + +#: ./doc/common/tables/nova-volumes.xml:120(td) +msgid "(StrOpt) the RADOS client name for accessing rbd volumes" +msgstr "" + +#: ./doc/common/tables/nova-volumes.xml:123(td) ./doc/common/tables/cinder-scality.xml:22(td) +msgid "scality_sofs_config = None" +msgstr "" + +#: ./doc/common/tables/nova-volumes.xml:124(td) ./doc/common/tables/cinder-scality.xml:23(td) +msgid "(StrOpt) Path or URL to Scality SOFS configuration file" +msgstr "" + +#: ./doc/common/tables/nova-volumes.xml:127(td) ./doc/common/tables/cinder-scality.xml:26(td) +msgid "scality_sofs_mount_point = $state_path/scality" +msgstr "" + +#: ./doc/common/tables/nova-volumes.xml:128(td) ./doc/common/tables/cinder-scality.xml:27(td) +msgid "(StrOpt) Base dir where Scality SOFS shall be mounted" +msgstr "" + +#: ./doc/common/tables/nova-volumes.xml:131(th) ./doc/common/tables/nova-xen.xml:65(th) ./doc/common/tables/nova-baremetal.xml:130(th) +msgid "[xenserver]" +msgstr "" + +#: ./doc/common/tables/nova-volumes.xml:134(td) +msgid "block_device_creation_timeout = 10" +msgstr "" + +#: ./doc/common/tables/nova-volumes.xml:135(td) +msgid "(IntOpt) Time to wait for a block device to be created" +msgstr "" + +#: ./doc/common/tables/glance-gridfs.xml:8(caption) +msgid "Description of configuration options for gridfs" +msgstr "" + +#: ./doc/common/tables/glance-gridfs.xml:22(td) +msgid "mongodb_store_db = None" +msgstr "" + +#: ./doc/common/tables/glance-gridfs.xml:23(td) +msgid "(StrOpt) Database to use" +msgstr "" + +#: ./doc/common/tables/glance-gridfs.xml:26(td) +msgid "mongodb_store_uri = None" +msgstr "" + +#: ./doc/common/tables/glance-gridfs.xml:27(td) +msgid "(StrOpt) Hostname or IP address of the instance to connect to, or a mongodb URI, or a list of hostnames / mongodb URIs. If host is an IPv6 literal it must be enclosed in '[' and ']' characters following the RFC2732 URL syntax (e.g. '[::1]' for localhost)" +msgstr "" + +#: ./doc/common/tables/neutron-ml2_arista.xml:8(caption) +msgid "Description of configuration options for ml2_arista" +msgstr "" + +#: ./doc/common/tables/neutron-ml2_arista.xml:19(td) +msgid "eapi_host =" +msgstr "" + +#: ./doc/common/tables/neutron-ml2_arista.xml:20(td) +msgid "(StrOpt) Arista EOS IP address. This is required field.If not set, all communications to Arista EOSwill fail" +msgstr "" + +#: ./doc/common/tables/neutron-ml2_arista.xml:23(td) +msgid "eapi_password =" +msgstr "" + +#: ./doc/common/tables/neutron-ml2_arista.xml:24(td) +msgid "(StrOpt) Password for Arista EOS. This is required field.if not set, all communications to Arista EOSwill fail" +msgstr "" + +#: ./doc/common/tables/neutron-ml2_arista.xml:27(td) +msgid "eapi_username =" +msgstr "" + +#: ./doc/common/tables/neutron-ml2_arista.xml:28(td) +msgid "(StrOpt) Username for Arista EOS. This is required field.if not set, all communications to Arista EOSwill fail" +msgstr "" + +#: ./doc/common/tables/neutron-ml2_arista.xml:31(td) +msgid "region_name = RegionOne" +msgstr "" + +#: ./doc/common/tables/neutron-ml2_arista.xml:32(td) +msgid "(StrOpt) Defines Region Name that is assigned to this OpenStackController. This is useful when multipleOpenStack/Neutron controllers are managing the sameArista HW clusters. Note that this name must match withthe region name registered (or known) to keystoneservice. Authentication with Keysotne is performed byEOS. This is optional. If not set, a value of\"RegionOne\" is assumed" +msgstr "" + +#: ./doc/common/tables/neutron-ml2_arista.xml:35(td) +msgid "sync_interval = 180" +msgstr "" + +#: ./doc/common/tables/neutron-ml2_arista.xml:36(td) +msgid "(IntOpt) Sync interval in seconds between Neutron plugin andEOS. This interval defines how often thesynchronization is performed. This is an optionalfield. If not set, a value of 180 seconds is assumed" +msgstr "" + +#: ./doc/common/tables/neutron-ml2_arista.xml:39(td) +msgid "use_fqdn = True" +msgstr "" + +#: ./doc/common/tables/neutron-ml2_arista.xml:40(td) +msgid "(BoolOpt) Defines if hostnames are sent to Arista EOS as FQDNs(\"node1.domain.com\") or as short names (\"node1\").This is optional. If not set, a value of \"True\"is assumed." +msgstr "" + +#: ./doc/common/tables/glance-filesystem.xml:8(caption) +msgid "Description of configuration options for filesystem" +msgstr "" + +#: ./doc/common/tables/glance-filesystem.xml:22(td) +msgid "filesystem_store_datadir = None" +msgstr "" + +#: ./doc/common/tables/glance-filesystem.xml:23(td) +msgid "(StrOpt) Directory to which the Filesystem backend store writes images." +msgstr "" + +#: ./doc/common/tables/glance-filesystem.xml:26(td) +msgid "filesystem_store_metadata_file = None" +msgstr "" + +#: ./doc/common/tables/glance-filesystem.xml:27(td) +msgid "(StrOpt) The path to a file which contains the metadata to be returned with any location associated with this store. The file must contain a valid JSON dict." +msgstr "" + +#: ./doc/common/tables/swift-container-server-container-updater.xml:7(literal) +msgid "[container-updater]" +msgstr "" + +#: ./doc/common/tables/swift-container-server-container-updater.xml:18(td) +msgid "log_name = container-updater" +msgstr "" + +#: ./doc/common/tables/swift-container-server-container-updater.xml:30(td) ./doc/common/tables/swift-container-server-container-sync.xml:33(td) ./doc/common/tables/swift-object-server-object-updater.xml:30(td) ./doc/common/tables/swift-object-expirer-object-expirer.xml:18(td) +msgid "interval = 300" +msgstr "" + +#: ./doc/common/tables/swift-container-server-container-updater.xml:30(td) ./doc/common/tables/swift-container-server-container-replicator.xml:42(td) ./doc/common/tables/swift-container-server-container-sync.xml:33(td) ./doc/common/tables/swift-object-server-object-updater.xml:30(td) ./doc/common/tables/swift-account-server-account-auditor.xml:30(td) ./doc/common/tables/swift-container-server-container-auditor.xml:30(td) ./doc/common/tables/swift-account-server-account-replicator.xml:42(td) ./doc/common/tables/swift-object-expirer-object-expirer.xml:18(td) ./doc/common/tables/swift-account-server-account-reaper.xml:33(td) +msgid "Minimum time for a pass to take" +msgstr "" + +#: ./doc/common/tables/swift-container-server-container-updater.xml:33(td) +msgid "concurrency = 4" +msgstr "" + +#: ./doc/common/tables/swift-container-server-container-updater.xml:33(td) ./doc/common/tables/swift-container-server-container-replicator.xml:39(td) ./doc/common/tables/swift-swift-bench-bench.xml:45(td) ./doc/common/tables/swift-object-server-object-updater.xml:33(td) ./doc/common/tables/swift-object-server-object-replicator.xml:39(td) ./doc/common/tables/swift-dispersion-dispersion.xml:54(td) ./doc/common/tables/swift-account-server-account-replicator.xml:39(td) ./doc/common/tables/swift-object-expirer-object-expirer.xml:27(td) ./doc/common/tables/swift-account-server-account-reaper.xml:30(td) +msgid "Number of replication workers to spawn" +msgstr "" + +#: ./doc/common/tables/swift-container-server-container-updater.xml:36(td) ./doc/common/tables/swift-container-server-app-container-server.xml:36(td) ./doc/common/tables/swift-object-server-app-object-server.xml:36(td) +msgid "node_timeout = 3" +msgstr "" + +#: ./doc/common/tables/swift-container-server-container-updater.xml:36(td) ./doc/common/tables/swift-container-server-container-replicator.xml:45(td) ./doc/common/tables/swift-object-server-object-updater.xml:36(td) ./doc/common/tables/swift-proxy-server-app-proxy-server.xml:48(td) ./doc/common/tables/swift-container-server-app-container-server.xml:36(td) ./doc/common/tables/swift-account-server-account-replicator.xml:51(td) ./doc/common/tables/swift-object-server-app-object-server.xml:36(td) ./doc/common/tables/swift-account-server-account-reaper.xml:36(td) +msgid "Request timeout to external services" +msgstr "" + +#: ./doc/common/tables/swift-container-server-container-updater.xml:39(td) ./doc/common/tables/swift-container-server-container-replicator.xml:48(td) ./doc/common/tables/swift-object-server-object-updater.xml:39(td) ./doc/common/tables/swift-proxy-server-app-proxy-server.xml:51(td) ./doc/common/tables/swift-container-server-app-container-server.xml:39(td) ./doc/common/tables/swift-account-server-account-replicator.xml:54(td) ./doc/common/tables/swift-object-server-app-object-server.xml:39(td) ./doc/common/tables/swift-account-server-account-reaper.xml:39(td) +msgid "conn_timeout = 0.5" +msgstr "" + +#: ./doc/common/tables/swift-container-server-container-updater.xml:39(td) ./doc/common/tables/swift-container-server-container-replicator.xml:48(td) ./doc/common/tables/swift-object-server-object-updater.xml:39(td) ./doc/common/tables/swift-proxy-server-app-proxy-server.xml:51(td) ./doc/common/tables/swift-container-server-app-container-server.xml:39(td) ./doc/common/tables/swift-account-server-account-replicator.xml:54(td) ./doc/common/tables/swift-object-server-app-object-server.xml:39(td) ./doc/common/tables/swift-account-server-account-reaper.xml:39(td) +msgid "Connection timeout to external services" +msgstr "" + +#: ./doc/common/tables/swift-container-server-container-updater.xml:42(td) ./doc/common/tables/swift-object-server-object-updater.xml:42(td) +msgid "slowdown = 0.01" +msgstr "" + +#: ./doc/common/tables/swift-container-server-container-updater.xml:42(td) ./doc/common/tables/swift-object-server-object-updater.xml:42(td) +msgid "Time in seconds to wait between objects" +msgstr "" + +#: ./doc/common/tables/swift-container-server-container-updater.xml:45(td) +msgid "account_suppression_time = 60" +msgstr "" + +#: ./doc/common/tables/swift-container-server-container-updater.xml:45(td) +msgid "Seconds to suppress updating an account that has generated an error (timeout, not yet found, etc.)" +msgstr "" + +#: ./doc/common/tables/swift-container-server-container-updater.xml:49(td) ./doc/common/tables/swift-account-server-filter-recon.xml:21(td) ./doc/common/tables/swift-container-server-container-replicator.xml:57(td) ./doc/common/tables/swift-object-server-object-auditor.xml:42(td) ./doc/common/tables/swift-object-server-object-updater.xml:45(td) ./doc/common/tables/swift-account-server-account-auditor.xml:42(td) ./doc/common/tables/swift-object-server-filter-recon.xml:21(td) ./doc/common/tables/swift-container-server-container-auditor.xml:36(td) ./doc/common/tables/swift-object-server-object-replicator.xml:66(td) ./doc/common/tables/swift-account-server-account-replicator.xml:63(td) ./doc/common/tables/swift-container-server-filter-recon.xml:21(td) +msgid "recon_cache_path = /var/cache/swift" +msgstr "" + +#: ./doc/common/tables/swift-container-server-container-updater.xml:49(td) ./doc/common/tables/swift-account-server-filter-recon.xml:21(td) ./doc/common/tables/swift-container-server-container-replicator.xml:57(td) ./doc/common/tables/swift-object-server-object-auditor.xml:42(td) ./doc/common/tables/swift-object-server-object-updater.xml:45(td) ./doc/common/tables/swift-account-server-account-auditor.xml:42(td) ./doc/common/tables/swift-object-server-filter-recon.xml:21(td) ./doc/common/tables/swift-container-server-container-auditor.xml:36(td) ./doc/common/tables/swift-object-server-object-replicator.xml:66(td) ./doc/common/tables/swift-account-server-account-replicator.xml:63(td) ./doc/common/tables/swift-container-server-filter-recon.xml:21(td) +msgid "Directory where stats for a few items will be stored" +msgstr "" + +#: ./doc/common/tables/cinder-storage_gpfs.xml:8(caption) +msgid "Description of configuration options for storage_gpfs" +msgstr "" + +#: ./doc/common/tables/cinder-storage_gpfs.xml:22(td) +msgid "gpfs_images_dir = None" +msgstr "" + +#: ./doc/common/tables/cinder-storage_gpfs.xml:23(td) +msgid "(StrOpt) Specifies the path of the Image service repository in GPFS. Leave undefined if not storing images in GPFS." +msgstr "" + +#: ./doc/common/tables/cinder-storage_gpfs.xml:26(td) +msgid "gpfs_images_share_mode = None" +msgstr "" + +#: ./doc/common/tables/cinder-storage_gpfs.xml:27(td) +msgid "(StrOpt) Specifies the type of image copy to be used. Set this when the Image service repository also uses GPFS so that image files can be transferred efficiently from the Image service to the Block Storage service. There are two valid values: \"copy\" specifies that a full copy of the image is made; \"copy_on_write\" specifies that copy-on-write optimization strategy is used and unmodified blocks of the image file are shared efficiently." +msgstr "" + +#: ./doc/common/tables/cinder-storage_gpfs.xml:30(td) +msgid "gpfs_max_clone_depth = 0" +msgstr "" + +#: ./doc/common/tables/cinder-storage_gpfs.xml:31(td) +msgid "(IntOpt) Specifies an upper limit on the number of indirections required to reach a specific block due to snapshots or clones. A lengthy chain of copy-on-write snapshots or clones can have a negative impact on performance, but improves space utilization. 0 indicates unlimited clone depth." +msgstr "" + +#: ./doc/common/tables/cinder-storage_gpfs.xml:34(td) +msgid "gpfs_mount_point_base = None" +msgstr "" + +#: ./doc/common/tables/cinder-storage_gpfs.xml:35(td) +msgid "(StrOpt) Specifies the path of the GPFS directory where Block Storage volume and snapshot files are stored." +msgstr "" + +#: ./doc/common/tables/cinder-storage_gpfs.xml:38(td) +msgid "gpfs_sparse_volumes = True" +msgstr "" + +#: ./doc/common/tables/cinder-storage_gpfs.xml:39(td) +msgid "(BoolOpt) Specifies that volumes are created as sparse files which initially consume no space. If set to False, the volume is created as a fully allocated file, in which case, creation may take a significantly longer time." +msgstr "" + +#: ./doc/common/tables/nova-docker.xml:8(caption) +msgid "Description of configuration options for docker" +msgstr "" + +#: ./doc/common/tables/nova-docker.xml:19(th) +msgid "[docker]" +msgstr "" + +#: ./doc/common/tables/nova-docker.xml:22(td) +msgid "registry_default_port = 5042" +msgstr "" + +#: ./doc/common/tables/nova-docker.xml:23(td) +msgid "(IntOpt) Default TCP port to find the docker-registry container" +msgstr "" + +#: ./doc/common/tables/cinder-nexenta_iscsi.xml:8(caption) +msgid "Description of configuration options for nexenta_iscsi" +msgstr "" + +#: ./doc/common/tables/cinder-nexenta_iscsi.xml:22(td) +msgid "nexenta_blocksize =" +msgstr "" + +#: ./doc/common/tables/cinder-nexenta_iscsi.xml:23(td) +msgid "(StrOpt) block size for volumes (blank=default,8KB)" +msgstr "" + +#: ./doc/common/tables/cinder-nexenta_iscsi.xml:26(td) +msgid "nexenta_host =" +msgstr "" + +#: ./doc/common/tables/cinder-nexenta_iscsi.xml:27(td) +msgid "(StrOpt) IP address of Nexenta SA" +msgstr "" + +#: ./doc/common/tables/cinder-nexenta_iscsi.xml:30(td) +msgid "nexenta_iscsi_target_portal_port = 3260" +msgstr "" + +#: ./doc/common/tables/cinder-nexenta_iscsi.xml:31(td) +msgid "(IntOpt) Nexenta target portal port" +msgstr "" + +#: ./doc/common/tables/cinder-nexenta_iscsi.xml:34(td) +msgid "nexenta_password = nexenta" +msgstr "" + +#: ./doc/common/tables/cinder-nexenta_iscsi.xml:35(td) +msgid "(StrOpt) Password to connect to Nexenta SA" +msgstr "" + +#: ./doc/common/tables/cinder-nexenta_iscsi.xml:38(td) +msgid "nexenta_rest_port = 2000" +msgstr "" + +#: ./doc/common/tables/cinder-nexenta_iscsi.xml:39(td) +msgid "(IntOpt) HTTP port to connect to Nexenta REST API server" +msgstr "" + +#: ./doc/common/tables/cinder-nexenta_iscsi.xml:42(td) +msgid "nexenta_rest_protocol = auto" +msgstr "" + +#: ./doc/common/tables/cinder-nexenta_iscsi.xml:43(td) +msgid "(StrOpt) Use http or https for REST connection (default auto)" +msgstr "" + +#: ./doc/common/tables/cinder-nexenta_iscsi.xml:46(td) +msgid "nexenta_rrmgr_compression = 0" +msgstr "" + +#: ./doc/common/tables/cinder-nexenta_iscsi.xml:47(td) +msgid "(IntOpt) Enable stream compression, level 1..9. 1 - gives best speed; 9 - gives best compression." +msgstr "" + +#: ./doc/common/tables/cinder-nexenta_iscsi.xml:50(td) +msgid "nexenta_rrmgr_connections = 2" +msgstr "" + +#: ./doc/common/tables/cinder-nexenta_iscsi.xml:51(td) +msgid "(IntOpt) Number of TCP connections." +msgstr "" + +#: ./doc/common/tables/cinder-nexenta_iscsi.xml:54(td) +msgid "nexenta_rrmgr_tcp_buf_size = 4096" +msgstr "" + +#: ./doc/common/tables/cinder-nexenta_iscsi.xml:55(td) +msgid "(IntOpt) TCP Buffer size in KiloBytes." +msgstr "" + +#: ./doc/common/tables/cinder-nexenta_iscsi.xml:58(td) +msgid "nexenta_sparse = False" +msgstr "" + +#: ./doc/common/tables/cinder-nexenta_iscsi.xml:59(td) +msgid "(BoolOpt) flag to create sparse volumes" +msgstr "" + +#: ./doc/common/tables/cinder-nexenta_iscsi.xml:62(td) +msgid "nexenta_sparsed_volumes = True" +msgstr "" + +#: ./doc/common/tables/cinder-nexenta_iscsi.xml:63(td) ./doc/common/tables/cinder-storage_nfs.xml:39(td) ./doc/common/tables/cinder-storage_glusterfs.xml:35(td) +msgid "(BoolOpt) Create volumes as sparsed files which take no space.If set to False volume is created as regular file.In such case volume creation takes a lot of time." +msgstr "" + +#: ./doc/common/tables/cinder-nexenta_iscsi.xml:66(td) +msgid "nexenta_target_group_prefix = cinder/" +msgstr "" + +#: ./doc/common/tables/cinder-nexenta_iscsi.xml:67(td) +msgid "(StrOpt) prefix for iSCSI target groups on SA" +msgstr "" + +#: ./doc/common/tables/cinder-nexenta_iscsi.xml:70(td) +msgid "nexenta_target_prefix = iqn.1986-03.com.sun:02:cinder-" +msgstr "" + +#: ./doc/common/tables/cinder-nexenta_iscsi.xml:71(td) +msgid "(StrOpt) IQN prefix for iSCSI targets" +msgstr "" + +#: ./doc/common/tables/cinder-nexenta_iscsi.xml:74(td) +msgid "nexenta_user = admin" +msgstr "" + +#: ./doc/common/tables/cinder-nexenta_iscsi.xml:75(td) +msgid "(StrOpt) User name to connect to Nexenta SA" +msgstr "" + +#: ./doc/common/tables/cinder-nexenta_iscsi.xml:78(td) +msgid "nexenta_volume = cinder" +msgstr "" + +#: ./doc/common/tables/cinder-nexenta_iscsi.xml:79(td) +msgid "(StrOpt) pool on SA that will hold all volumes" +msgstr "" + +#: ./doc/common/tables/nova-tilera.xml:8(caption) +msgid "Description of configuration options for tilera" +msgstr "" + +#: ./doc/common/tables/nova-tilera.xml:22(td) +msgid "tile_pdu_ip = 10.0.100.1" +msgstr "" + +#: ./doc/common/tables/nova-tilera.xml:23(td) +msgid "(StrOpt) ip address of tilera pdu" +msgstr "" + +#: ./doc/common/tables/nova-tilera.xml:26(td) +msgid "tile_pdu_mgr = /tftpboot/pdu_mgr" +msgstr "" + +#: ./doc/common/tables/nova-tilera.xml:27(td) +msgid "(StrOpt) management script for tilera pdu" +msgstr "" + +#: ./doc/common/tables/nova-tilera.xml:30(td) +msgid "tile_pdu_off = 2" +msgstr "" + +#: ./doc/common/tables/nova-tilera.xml:31(td) +msgid "(IntOpt) power status of tilera PDU is OFF" +msgstr "" + +#: ./doc/common/tables/nova-tilera.xml:34(td) +msgid "tile_pdu_on = 1" +msgstr "" + +#: ./doc/common/tables/nova-tilera.xml:35(td) +msgid "(IntOpt) power status of tilera PDU is ON" +msgstr "" + +#: ./doc/common/tables/nova-tilera.xml:38(td) +msgid "tile_pdu_status = 9" +msgstr "" + +#: ./doc/common/tables/nova-tilera.xml:39(td) +msgid "(IntOpt) power status of tilera PDU" +msgstr "" + +#: ./doc/common/tables/nova-tilera.xml:42(td) +msgid "tile_power_wait = 9" +msgstr "" + +#: ./doc/common/tables/nova-tilera.xml:43(td) +msgid "(IntOpt) wait time in seconds until check the result after tilera power operations" +msgstr "" + +#: ./doc/common/tables/nova-ca.xml:8(caption) +msgid "Description of configuration options for ca" +msgstr "" + +#: ./doc/common/tables/nova-ca.xml:22(td) +msgid "ca_file = cacert.pem" +msgstr "" + +#: ./doc/common/tables/nova-ca.xml:23(td) +msgid "(StrOpt) Filename of root CA" +msgstr "" + +#: ./doc/common/tables/nova-ca.xml:26(td) +msgid "ca_path = $state_path/CA" +msgstr "" + +#: ./doc/common/tables/nova-ca.xml:27(td) +msgid "(StrOpt) Where we keep our root CA" +msgstr "" + +#: ./doc/common/tables/nova-ca.xml:30(td) +msgid "cert_manager = nova.cert.manager.CertManager" +msgstr "" + +#: ./doc/common/tables/nova-ca.xml:31(td) +msgid "(StrOpt) full class name for the Manager for cert" +msgstr "" + +#: ./doc/common/tables/nova-ca.xml:34(td) +msgid "cert_topic = cert" +msgstr "" + +#: ./doc/common/tables/nova-ca.xml:35(td) +msgid "(StrOpt) the topic cert nodes listen on" +msgstr "" + +#: ./doc/common/tables/nova-ca.xml:38(td) +msgid "crl_file = crl.pem" +msgstr "" + +#: ./doc/common/tables/nova-ca.xml:39(td) +msgid "(StrOpt) Filename of root Certificate Revocation List" +msgstr "" + +#: ./doc/common/tables/nova-ca.xml:42(td) +msgid "key_file = private/cakey.pem" +msgstr "" + +#: ./doc/common/tables/nova-ca.xml:43(td) +msgid "(StrOpt) Filename of private key" +msgstr "" + +#: ./doc/common/tables/nova-ca.xml:46(td) +msgid "keys_path = $state_path/keys" +msgstr "" + +#: ./doc/common/tables/nova-ca.xml:47(td) +msgid "(StrOpt) Where we keep our keys" +msgstr "" + +#: ./doc/common/tables/nova-ca.xml:50(td) +msgid "project_cert_subject = /C=US/ST=California/O=OpenStack/OU=NovaDev/CN=project-ca-%.16s-%s" +msgstr "" + +#: ./doc/common/tables/nova-ca.xml:51(td) +msgid "(StrOpt) Subject for certificate for projects, %s for project, timestamp" +msgstr "" + +#: ./doc/common/tables/nova-ca.xml:54(td) +msgid "use_project_ca = False" +msgstr "" + +#: ./doc/common/tables/nova-ca.xml:55(td) +msgid "(BoolOpt) Should we use a CA for each project?" +msgstr "" + +#: ./doc/common/tables/nova-ca.xml:58(td) +msgid "user_cert_subject = /C=US/ST=California/O=OpenStack/OU=NovaDev/CN=%.16s-%.16s-%s" +msgstr "" + +#: ./doc/common/tables/nova-ca.xml:59(td) +msgid "(StrOpt) Subject for certificate for users, %s for project, user, timestamp" +msgstr "" + +#: ./doc/common/tables/nova-ca.xml:65(td) ./doc/common/tables/glance-ssl.xml:22(td) +msgid "ca_file = None" +msgstr "" + +#: ./doc/common/tables/nova-ca.xml:66(td) ./doc/common/tables/nova-wsgi.xml:27(td) ./doc/common/tables/cinder-common.xml:191(td) ./doc/common/tables/neutron-ssl.xml:24(td) +msgid "(StrOpt) CA certificate file to use to verify connecting clients" +msgstr "" + +#: ./doc/common/tables/nova-ca.xml:69(td) ./doc/common/tables/glance-ssl.xml:26(td) ./doc/common/tables/neutron-nec.xml:19(td) +msgid "cert_file = None" +msgstr "" + +#: ./doc/common/tables/nova-ca.xml:70(td) ./doc/common/tables/cinder-common.xml:195(td) ./doc/common/tables/neutron-ssl.xml:28(td) +msgid "(StrOpt) Certificate file to use when starting the server securely" +msgstr "" + +#: ./doc/common/tables/nova-ca.xml:73(td) ./doc/common/tables/neutron-ssl.xml:19(td) ./doc/common/tables/glance-ssl.xml:30(td) +msgid "key_file = None" +msgstr "" + +#: ./doc/common/tables/nova-ca.xml:74(td) ./doc/common/tables/cinder-common.xml:199(td) ./doc/common/tables/neutron-ssl.xml:32(td) +msgid "(StrOpt) Private key file to use when starting the server securely" +msgstr "" + +#: ./doc/common/tables/swift-account-server-filter-recon.xml:7(literal) ./doc/common/tables/swift-object-server-filter-recon.xml:7(literal) ./doc/common/tables/swift-container-server-filter-recon.xml:7(literal) +msgid "[filter:recon]" +msgstr "" + +#: ./doc/common/tables/swift-account-server-filter-recon.xml:7(literal) ./doc/common/tables/swift-account-server-app-account-server.xml:7(literal) ./doc/common/tables/swift-account-server-filter-healthcheck.xml:7(literal) ./doc/common/tables/swift-account-server-account-auditor.xml:7(literal) ./doc/common/tables/swift-account-server-DEFAULT.xml:7(literal) ./doc/common/tables/swift-account-server-account-replicator.xml:7(literal) ./doc/common/tables/swift-account-server-pipeline-main.xml:7(literal) ./doc/common/tables/swift-account-server-account-reaper.xml:7(literal) +msgid "account-server.conf-sample" +msgstr "" + +#: ./doc/common/tables/swift-account-server-filter-recon.xml:18(td) ./doc/common/tables/swift-object-server-filter-recon.xml:18(td) ./doc/common/tables/swift-container-server-filter-recon.xml:18(td) +msgid "use = egg:swift#recon" +msgstr "" + +#: ./doc/common/tables/cinder-huawei.xml:8(caption) +msgid "Description of configuration options for huawei" +msgstr "" + +#: ./doc/common/tables/cinder-huawei.xml:22(td) +msgid "cinder_huawei_conf_file = /etc/cinder/cinder_huawei_conf.xml" +msgstr "" + +#: ./doc/common/tables/cinder-huawei.xml:23(td) +msgid "(StrOpt) config data for cinder huawei plugin" +msgstr "" + +#: ./doc/common/tables/swift-container-server-container-replicator.xml:7(literal) +msgid "[container-replicator]" +msgstr "" + +#: ./doc/common/tables/swift-container-server-container-replicator.xml:18(td) +msgid "log_name = container-replicator" +msgstr "" + +#: ./doc/common/tables/swift-container-server-container-replicator.xml:30(td) ./doc/common/tables/swift-object-server-object-replicator.xml:30(td) ./doc/common/tables/swift-account-server-account-replicator.xml:30(td) +msgid "vm_test_mode = no" +msgstr "" + +#: ./doc/common/tables/swift-container-server-container-replicator.xml:30(td) ./doc/common/tables/swift-object-server-object-replicator.xml:30(td) ./doc/common/tables/swift-account-server-account-replicator.xml:30(td) +msgid "Indicates that you are using a VM environment" +msgstr "" + +#: ./doc/common/tables/swift-container-server-container-replicator.xml:33(td) ./doc/common/tables/swift-account-server-account-replicator.xml:33(td) +msgid "per_diff = 1000" +msgstr "" + +#: ./doc/common/tables/swift-container-server-container-replicator.xml:33(td) ./doc/common/tables/swift-account-server-account-replicator.xml:33(td) +msgid "Limit number of items to get per diff" +msgstr "" + +#: ./doc/common/tables/swift-container-server-container-replicator.xml:36(td) ./doc/common/tables/swift-account-server-account-replicator.xml:36(td) +msgid "max_diffs = 100" +msgstr "" + +#: ./doc/common/tables/swift-container-server-container-replicator.xml:36(td) ./doc/common/tables/swift-account-server-account-replicator.xml:36(td) +msgid "Caps how long the replicator spends trying to sync a database per pass" +msgstr "" + +#: ./doc/common/tables/swift-container-server-container-replicator.xml:39(td) ./doc/common/tables/swift-account-server-account-replicator.xml:39(td) +msgid "concurrency = 8" +msgstr "" + +#: ./doc/common/tables/swift-container-server-container-replicator.xml:42(td) ./doc/common/tables/swift-account-server-account-replicator.xml:42(td) +msgid "interval = 30" +msgstr "" + +#: ./doc/common/tables/swift-container-server-container-replicator.xml:45(td) ./doc/common/tables/swift-object-server-object-updater.xml:36(td) ./doc/common/tables/swift-proxy-server-app-proxy-server.xml:48(td) ./doc/common/tables/swift-account-server-account-replicator.xml:51(td) ./doc/common/tables/swift-account-server-account-reaper.xml:36(td) +msgid "node_timeout = 10" +msgstr "" + +#: ./doc/common/tables/swift-container-server-container-replicator.xml:51(td) ./doc/common/tables/swift-object-server-object-replicator.xml:60(td) ./doc/common/tables/swift-account-server-account-replicator.xml:57(td) +msgid "reclaim_age = 604800" +msgstr "" + +#: ./doc/common/tables/swift-container-server-container-replicator.xml:51(td) ./doc/common/tables/swift-object-server-object-replicator.xml:60(td) ./doc/common/tables/swift-account-server-account-replicator.xml:57(td) +msgid "Time elapsed in seconds before an object can be reclaimed" +msgstr "" + +#: ./doc/common/tables/swift-container-server-container-replicator.xml:54(td) ./doc/common/tables/swift-object-server-object-replicator.xml:36(td) ./doc/common/tables/swift-account-server-account-replicator.xml:60(td) +msgid "run_pause = 30" +msgstr "" + +#: ./doc/common/tables/swift-container-server-container-replicator.xml:54(td) ./doc/common/tables/swift-object-server-object-replicator.xml:36(td) ./doc/common/tables/swift-account-server-account-replicator.xml:60(td) +msgid "Time in seconds to wait between replication passes" +msgstr "" + +#: ./doc/common/tables/nova-glance.xml:8(caption) +msgid "Description of configuration options for glance" +msgstr "" + +#: ./doc/common/tables/nova-glance.xml:22(td) ./doc/common/tables/cinder-images.xml:22(td) +msgid "allowed_direct_url_schemes =" +msgstr "" + +#: ./doc/common/tables/nova-glance.xml:23(td) +msgid "(ListOpt) A list of url scheme that can be downloaded directly via the direct_url. Currently supported schemes: [file]." +msgstr "" + +#: ./doc/common/tables/nova-glance.xml:26(td) ./doc/common/tables/cinder-images.xml:26(td) +msgid "glance_api_insecure = False" +msgstr "" + +#: ./doc/common/tables/nova-glance.xml:27(td) ./doc/common/tables/cinder-images.xml:27(td) +msgid "(BoolOpt) Allow to perform insecure SSL (https) requests to glance" +msgstr "" + +#: ./doc/common/tables/nova-glance.xml:30(td) ./doc/common/tables/cinder-images.xml:30(td) +msgid "glance_api_servers = $glance_host:$glance_port" +msgstr "" + +#: ./doc/common/tables/nova-glance.xml:31(td) +msgid "(ListOpt) A list of the glance api servers available to nova. Prefix with https:// for ssl-based glance api servers. ([hostname|ip]:port)" +msgstr "" + +#: ./doc/common/tables/nova-glance.xml:34(td) ./doc/common/tables/cinder-images.xml:42(td) +msgid "glance_host = $my_ip" +msgstr "" + +#: ./doc/common/tables/nova-glance.xml:35(td) ./doc/common/tables/cinder-images.xml:43(td) +msgid "(StrOpt) default glance hostname or ip" +msgstr "" + +#: ./doc/common/tables/nova-glance.xml:38(td) ./doc/common/tables/cinder-images.xml:46(td) +msgid "glance_num_retries = 0" +msgstr "" + +#: ./doc/common/tables/nova-glance.xml:39(td) ./doc/common/tables/cinder-images.xml:47(td) +msgid "(IntOpt) Number retries when downloading an image from glance" +msgstr "" + +#: ./doc/common/tables/nova-glance.xml:42(td) ./doc/common/tables/cinder-images.xml:50(td) +msgid "glance_port = 9292" +msgstr "" + +#: ./doc/common/tables/nova-glance.xml:43(td) ./doc/common/tables/cinder-images.xml:51(td) +msgid "(IntOpt) default glance port" +msgstr "" + +#: ./doc/common/tables/nova-glance.xml:46(td) +msgid "glance_protocol = http" +msgstr "" + +#: ./doc/common/tables/nova-glance.xml:47(td) +msgid "(StrOpt) Default protocol to use when connecting to glance. Set to https for SSL." +msgstr "" + +#: ./doc/common/tables/nova-glance.xml:50(td) +msgid "osapi_glance_link_prefix = None" +msgstr "" + +#: ./doc/common/tables/nova-glance.xml:51(td) +msgid "(StrOpt) Base URL that will be presented to users in links to glance resources" +msgstr "" + +#: ./doc/common/tables/nova-glance.xml:54(th) +msgid "[image_file_url]" +msgstr "" + +#: ./doc/common/tables/nova-glance.xml:57(td) +msgid "filesystems =" +msgstr "" + +#: ./doc/common/tables/nova-glance.xml:58(td) +msgid "(ListOpt) A list of filesystems that will be configured in this file under the sections image_file_url:<list entry name>" +msgstr "" + +#: ./doc/common/tables/nova-neutron.xml:8(caption) +msgid "Description of configuration options for neutron" +msgstr "" + +#: ./doc/common/tables/nova-neutron.xml:22(td) +msgid "neutron_admin_auth_url = http://localhost:5000/v2.0" +msgstr "" + +#: ./doc/common/tables/nova-neutron.xml:23(td) +msgid "(StrOpt) auth url for connecting to neutron in admin context" +msgstr "" + +#: ./doc/common/tables/nova-neutron.xml:26(td) +msgid "neutron_admin_password = None" +msgstr "" + +#: ./doc/common/tables/nova-neutron.xml:27(td) +msgid "(StrOpt) password for connecting to neutron in admin context" +msgstr "" + +#: ./doc/common/tables/nova-neutron.xml:30(td) +msgid "neutron_admin_tenant_name = None" +msgstr "" + +#: ./doc/common/tables/nova-neutron.xml:31(td) +msgid "(StrOpt) tenant name for connecting to neutron in admin context" +msgstr "" + +#: ./doc/common/tables/nova-neutron.xml:34(td) +msgid "neutron_admin_username = None" +msgstr "" + +#: ./doc/common/tables/nova-neutron.xml:35(td) +msgid "(StrOpt) username for connecting to neutron in admin context" +msgstr "" + +#: ./doc/common/tables/nova-neutron.xml:38(td) +msgid "neutron_api_insecure = False" +msgstr "" + +#: ./doc/common/tables/nova-neutron.xml:39(td) +msgid "(BoolOpt) if set, ignore any SSL validation issues" +msgstr "" + +#: ./doc/common/tables/nova-neutron.xml:42(td) +msgid "neutron_auth_strategy = keystone" +msgstr "" + +#: ./doc/common/tables/nova-neutron.xml:43(td) +msgid "(StrOpt) auth strategy for connecting to neutron in admin context" +msgstr "" + +#: ./doc/common/tables/nova-neutron.xml:46(td) +msgid "neutron_ca_certificates_file = None" +msgstr "" + +#: ./doc/common/tables/nova-neutron.xml:47(td) +msgid "(StrOpt) Location of ca certificates file to use for neutron client requests." +msgstr "" + +#: ./doc/common/tables/nova-neutron.xml:50(td) +msgid "neutron_default_tenant_id = default" +msgstr "" + +#: ./doc/common/tables/nova-neutron.xml:51(td) +msgid "(StrOpt) Default tenant id when creating neutron networks" +msgstr "" + +#: ./doc/common/tables/nova-neutron.xml:54(td) +msgid "neutron_extension_sync_interval = 600" +msgstr "" + +#: ./doc/common/tables/nova-neutron.xml:55(td) +msgid "(IntOpt) Number of seconds before querying neutron for extensions" +msgstr "" + +#: ./doc/common/tables/nova-neutron.xml:58(td) +msgid "neutron_metadata_proxy_shared_secret =" +msgstr "" + +#: ./doc/common/tables/nova-neutron.xml:59(td) +msgid "(StrOpt) Shared secret to validate proxies Neutron metadata requests" +msgstr "" + +#: ./doc/common/tables/nova-neutron.xml:62(td) +msgid "neutron_ovs_bridge = br-int" +msgstr "" + +#: ./doc/common/tables/nova-neutron.xml:63(td) ./doc/common/tables/nova-xen.xml:153(td) +msgid "(StrOpt) Name of Integration Bridge used by Open vSwitch" +msgstr "" + +#: ./doc/common/tables/nova-neutron.xml:66(td) +msgid "neutron_region_name = None" +msgstr "" + +#: ./doc/common/tables/nova-neutron.xml:67(td) +msgid "(StrOpt) region name for connecting to neutron in admin context" +msgstr "" + +#: ./doc/common/tables/nova-neutron.xml:70(td) +msgid "neutron_url = http://127.0.0.1:9696" +msgstr "" + +#: ./doc/common/tables/nova-neutron.xml:71(td) +msgid "(StrOpt) URL for connecting to neutron" +msgstr "" + +#: ./doc/common/tables/nova-neutron.xml:74(td) +msgid "neutron_url_timeout = 30" +msgstr "" + +#: ./doc/common/tables/nova-neutron.xml:75(td) +msgid "(IntOpt) timeout value for connecting to neutron in seconds" +msgstr "" + +#: ./doc/common/tables/nova-neutron.xml:78(td) +msgid "service_neutron_metadata_proxy = False" +msgstr "" + +#: ./doc/common/tables/nova-neutron.xml:79(td) +msgid "(BoolOpt) Set flag to indicate Neutron will proxy metadata requests and resolve instance ids." +msgstr "" + +#: ./doc/common/tables/cinder-backups_ceph.xml:8(caption) +msgid "Description of configuration options for backups_ceph" +msgstr "" + +#: ./doc/common/tables/cinder-backups_ceph.xml:22(td) +msgid "backup_ceph_chunk_size = 134217728" +msgstr "" + +#: ./doc/common/tables/cinder-backups_ceph.xml:23(td) +msgid "(IntOpt) the chunk size in bytes that a backup will be broken into before transfer to backup store" +msgstr "" + +#: ./doc/common/tables/cinder-backups_ceph.xml:26(td) +msgid "backup_ceph_conf = /etc/ceph/ceph.conf" +msgstr "" + +#: ./doc/common/tables/cinder-backups_ceph.xml:27(td) +msgid "(StrOpt) Ceph config file to use." +msgstr "" + +#: ./doc/common/tables/cinder-backups_ceph.xml:30(td) +msgid "backup_ceph_pool = backups" +msgstr "" + +#: ./doc/common/tables/cinder-backups_ceph.xml:31(td) +msgid "(StrOpt) the Ceph pool to backup to" +msgstr "" + +#: ./doc/common/tables/cinder-backups_ceph.xml:34(td) +msgid "backup_ceph_stripe_count = 0" +msgstr "" + +#: ./doc/common/tables/cinder-backups_ceph.xml:35(td) +msgid "(IntOpt) RBD stripe count to use when creating a backup image" +msgstr "" + +#: ./doc/common/tables/cinder-backups_ceph.xml:38(td) +msgid "backup_ceph_stripe_unit = 0" +msgstr "" + +#: ./doc/common/tables/cinder-backups_ceph.xml:39(td) +msgid "(IntOpt) RBD stripe unit to use when creating a backup image" +msgstr "" + +#: ./doc/common/tables/cinder-backups_ceph.xml:42(td) +msgid "backup_ceph_user = cinder" +msgstr "" + +#: ./doc/common/tables/cinder-backups_ceph.xml:43(td) +msgid "(StrOpt) the Ceph user to connect with" +msgstr "" + +#: ./doc/common/tables/cinder-backups_ceph.xml:46(td) +msgid "restore_discard_excess_bytes = True" +msgstr "" + +#: ./doc/common/tables/cinder-backups_ceph.xml:47(td) +msgid "(BoolOpt) If True, always discard excess bytes when restoring volumes." +msgstr "" + +#: ./doc/common/tables/swift-proxy-server-filter-name_check.xml:7(literal) +msgid "[filter:name_check]" +msgstr "" + +#: ./doc/common/tables/swift-proxy-server-filter-name_check.xml:18(td) +msgid "use = egg:swift#name_check" +msgstr "" + +#: ./doc/common/tables/swift-proxy-server-filter-name_check.xml:21(td) +msgid "forbidden_chars = '\"`<>" +msgstr "" + +#: ./doc/common/tables/swift-proxy-server-filter-name_check.xml:21(td) +msgid "Characters that are not allowed in a name" +msgstr "" + +#: ./doc/common/tables/swift-proxy-server-filter-name_check.xml:24(td) +msgid "maximum_length = 255" +msgstr "" + +#: ./doc/common/tables/swift-proxy-server-filter-name_check.xml:24(td) +msgid "Maximum length of a name" +msgstr "" + +#: ./doc/common/tables/swift-proxy-server-filter-name_check.xml:27(td) +msgid "forbidden_regexp = /\\./|/\\.\\./|/\\.$|/\\.\\.$" +msgstr "" + +#: ./doc/common/tables/swift-proxy-server-filter-name_check.xml:27(td) +msgid "Substrings to forbid, using regular expression syntax" +msgstr "" + +#: ./doc/common/tables/nova-metadata.xml:8(caption) ./doc/common/tables/neutron-metadata.xml:8(caption) +msgid "Description of configuration options for metadata" +msgstr "" + +#: ./doc/common/tables/nova-metadata.xml:22(td) +msgid "metadata_host = $my_ip" +msgstr "" + +#: ./doc/common/tables/nova-metadata.xml:23(td) +msgid "(StrOpt) the ip for the metadata api server" +msgstr "" + +#: ./doc/common/tables/nova-metadata.xml:26(td) +msgid "metadata_listen = 0.0.0.0" +msgstr "" + +#: ./doc/common/tables/nova-metadata.xml:27(td) +msgid "(StrOpt) The IP address on which the metadata API will listen." +msgstr "" + +#: ./doc/common/tables/nova-metadata.xml:30(td) +msgid "metadata_listen_port = 8775" +msgstr "" + +#: ./doc/common/tables/nova-metadata.xml:31(td) +msgid "(IntOpt) The port on which the metadata API will listen." +msgstr "" + +#: ./doc/common/tables/nova-metadata.xml:34(td) +msgid "metadata_manager = nova.api.manager.MetadataManager" +msgstr "" + +#: ./doc/common/tables/nova-metadata.xml:35(td) +msgid "(StrOpt) OpenStack metadata service manager" +msgstr "" + +#: ./doc/common/tables/nova-metadata.xml:38(td) +msgid "metadata_port = 8775" +msgstr "" + +#: ./doc/common/tables/nova-metadata.xml:39(td) +msgid "(IntOpt) the port for the metadata api port" +msgstr "" + +#: ./doc/common/tables/nova-metadata.xml:42(td) +msgid "metadata_workers = None" +msgstr "" + +#: ./doc/common/tables/nova-metadata.xml:43(td) +msgid "(IntOpt) Number of workers for metadata service" +msgstr "" + +#: ./doc/common/tables/nova-metadata.xml:46(td) +msgid "vendordata_driver = nova.api.metadata.vendordata_json.JsonFileVendorData" +msgstr "" + +#: ./doc/common/tables/nova-metadata.xml:47(td) +msgid "(StrOpt) Driver to use for vendor data" +msgstr "" + +#: ./doc/common/tables/nova-metadata.xml:50(td) +msgid "vendordata_jsonfile_path = None" +msgstr "" + +#: ./doc/common/tables/nova-metadata.xml:51(td) +msgid "(StrOpt) File to load json formatted vendor data from" +msgstr "" + +#: ./doc/common/tables/glance-s3.xml:8(caption) ./doc/common/tables/nova-s3.xml:8(caption) +msgid "Description of configuration options for s3" +msgstr "" + +#: ./doc/common/tables/glance-s3.xml:22(td) +msgid "s3_store_access_key = None" +msgstr "" + +#: ./doc/common/tables/glance-s3.xml:23(td) +msgid "(StrOpt) The S3 query token access key." +msgstr "" + +#: ./doc/common/tables/glance-s3.xml:26(td) +msgid "s3_store_bucket = None" +msgstr "" + +#: ./doc/common/tables/glance-s3.xml:27(td) +msgid "(StrOpt) The S3 bucket to be used to store the Glance data." +msgstr "" + +#: ./doc/common/tables/glance-s3.xml:30(td) +msgid "s3_store_bucket_url_format = subdomain" +msgstr "" + +#: ./doc/common/tables/glance-s3.xml:31(td) +msgid "(StrOpt) The S3 calling format used to determine the bucket. Either subdomain or path can be used." +msgstr "" + +#: ./doc/common/tables/glance-s3.xml:34(td) +msgid "s3_store_create_bucket_on_put = False" +msgstr "" + +#: ./doc/common/tables/glance-s3.xml:35(td) +msgid "(BoolOpt) A boolean to determine if the S3 bucket should be created on upload if it does not exist or if an error should be returned to the user." +msgstr "" + +#: ./doc/common/tables/glance-s3.xml:38(td) +msgid "s3_store_host = None" +msgstr "" + +#: ./doc/common/tables/glance-s3.xml:39(td) +msgid "(StrOpt) The host where the S3 server is listening." +msgstr "" + +#: ./doc/common/tables/glance-s3.xml:42(td) +msgid "s3_store_object_buffer_dir = None" +msgstr "" + +#: ./doc/common/tables/glance-s3.xml:43(td) +msgid "(StrOpt) The local directory where uploads will be staged before they are transferred into S3." +msgstr "" + +#: ./doc/common/tables/glance-s3.xml:46(td) +msgid "s3_store_secret_key = None" +msgstr "" + +#: ./doc/common/tables/glance-s3.xml:47(td) +msgid "(StrOpt) The S3 query token secret key." +msgstr "" + +#: ./doc/common/tables/neutron-kombu.xml:8(caption) ./doc/common/tables/nova-kombu.xml:8(caption) +msgid "Description of configuration options for kombu" +msgstr "" + +#: ./doc/common/tables/neutron-kombu.xml:19(td) ./doc/common/tables/cinder-rpc.xml:46(td) ./doc/common/tables/glance-rabbitmq.xml:26(td) ./doc/common/tables/nova-kombu.xml:22(td) +msgid "kombu_ssl_ca_certs =" +msgstr "" + +#: ./doc/common/tables/neutron-kombu.xml:20(td) ./doc/common/tables/cinder-rpc.xml:47(td) ./doc/common/tables/glance-rabbitmq.xml:27(td) ./doc/common/tables/nova-kombu.xml:23(td) +msgid "(StrOpt) SSL certification authority file (valid only if SSL enabled)" +msgstr "" + +#: ./doc/common/tables/neutron-kombu.xml:23(td) ./doc/common/tables/cinder-rpc.xml:50(td) ./doc/common/tables/glance-rabbitmq.xml:30(td) ./doc/common/tables/nova-kombu.xml:26(td) +msgid "kombu_ssl_certfile =" +msgstr "" + +#: ./doc/common/tables/neutron-kombu.xml:24(td) ./doc/common/tables/cinder-rpc.xml:51(td) ./doc/common/tables/glance-rabbitmq.xml:31(td) ./doc/common/tables/nova-kombu.xml:27(td) +msgid "(StrOpt) SSL cert file (valid only if SSL enabled)" +msgstr "" + +#: ./doc/common/tables/neutron-kombu.xml:27(td) ./doc/common/tables/cinder-rpc.xml:54(td) ./doc/common/tables/glance-rabbitmq.xml:34(td) ./doc/common/tables/nova-kombu.xml:30(td) +msgid "kombu_ssl_keyfile =" +msgstr "" + +#: ./doc/common/tables/neutron-kombu.xml:28(td) ./doc/common/tables/cinder-rpc.xml:55(td) ./doc/common/tables/glance-rabbitmq.xml:35(td) ./doc/common/tables/nova-kombu.xml:31(td) +msgid "(StrOpt) SSL key file (valid only if SSL enabled)" +msgstr "" + +#: ./doc/common/tables/neutron-kombu.xml:31(td) ./doc/common/tables/cinder-rpc.xml:58(td) ./doc/common/tables/glance-rabbitmq.xml:38(td) ./doc/common/tables/nova-kombu.xml:34(td) +msgid "kombu_ssl_version =" +msgstr "" + +#: ./doc/common/tables/neutron-kombu.xml:32(td) ./doc/common/tables/cinder-rpc.xml:59(td) +msgid "(StrOpt) SSL version to use (valid only if SSL enabled)" +msgstr "" + +#: ./doc/common/tables/swift-proxy-server-filter-ratelimit.xml:7(literal) +msgid "[filter:ratelimit]" +msgstr "" + +#: ./doc/common/tables/swift-proxy-server-filter-ratelimit.xml:18(td) +msgid "use = egg:swift#ratelimit" +msgstr "" + +#: ./doc/common/tables/swift-proxy-server-filter-ratelimit.xml:21(td) +msgid "set log_name = ratelimit" +msgstr "" + +#: ./doc/common/tables/swift-proxy-server-filter-ratelimit.xml:36(td) +msgid "clock_accuracy = 1000" +msgstr "" + +#: ./doc/common/tables/swift-proxy-server-filter-ratelimit.xml:36(td) +msgid "Represents how accurate the proxy servers' system clocks are with each other. 1000 means that all the proxies' clock are accurate to each other within 1 millisecond. No ratelimit should be higher than the clock accuracy." +msgstr "" + +#: ./doc/common/tables/swift-proxy-server-filter-ratelimit.xml:39(td) +msgid "max_sleep_time_seconds = 60" +msgstr "" + +#: ./doc/common/tables/swift-proxy-server-filter-ratelimit.xml:39(td) +msgid "App will immediately return a 498 response if the necessary sleep time ever exceeds the given max_sleep_time_seconds." +msgstr "" + +#: ./doc/common/tables/swift-proxy-server-filter-ratelimit.xml:42(td) +msgid "log_sleep_time_seconds = 0" +msgstr "" + +#: ./doc/common/tables/swift-proxy-server-filter-ratelimit.xml:42(td) +msgid "To allow visibility into rate limiting set this value > 0 and all sleeps greater than the number will be logged." +msgstr "" + +#: ./doc/common/tables/swift-proxy-server-filter-ratelimit.xml:45(td) +msgid "rate_buffer_seconds = 5" +msgstr "" + +#: ./doc/common/tables/swift-proxy-server-filter-ratelimit.xml:45(td) +msgid "Number of seconds the rate counter can drop and be allowed to catch up (at a faster than listed rate). A larger number will result in larger spikes in rate but better average accuracy." +msgstr "" + +#: ./doc/common/tables/swift-proxy-server-filter-ratelimit.xml:48(td) +msgid "account_ratelimit = 0" +msgstr "" + +#: ./doc/common/tables/swift-proxy-server-filter-ratelimit.xml:48(td) +msgid "If set, will limit PUT and DELETE requests to /account_name/container_name. Number is in requests per second." +msgstr "" + +#: ./doc/common/tables/swift-proxy-server-filter-ratelimit.xml:51(td) +msgid "account_whitelist = a,b" +msgstr "" + +#: ./doc/common/tables/swift-proxy-server-filter-ratelimit.xml:51(td) +msgid "Comma separated lists of account names that will not be rate limited." +msgstr "" + +#: ./doc/common/tables/swift-proxy-server-filter-ratelimit.xml:54(td) +msgid "account_blacklist = c,d" +msgstr "" + +#: ./doc/common/tables/swift-proxy-server-filter-ratelimit.xml:54(td) +msgid "Comma separated lists of account names that will not be allowed. Returns a 497 response. r: for containers of size x, limit requests per second to r. Will limit PUT, DELETE, and POST requests to /a/c/o. container_listing_ratelimit_x = r: for containers of size x, limit listing requests per second to r. Will limit GET requests to /a/c." +msgstr "" + +#: ./doc/common/tables/swift-proxy-server-filter-ratelimit.xml:57(td) +msgid "with container_limit_x = r" +msgstr "" + +#: ./doc/common/tables/swift-proxy-server-filter-ratelimit.xml:60(td) +msgid "container_ratelimit_0 = 100" +msgstr "" + +#: ./doc/common/tables/swift-proxy-server-filter-ratelimit.xml:63(td) +msgid "container_ratelimit_10 = 50" +msgstr "" + +#: ./doc/common/tables/swift-proxy-server-filter-ratelimit.xml:66(td) +msgid "container_ratelimit_50 = 20" +msgstr "" + +#: ./doc/common/tables/swift-proxy-server-filter-ratelimit.xml:69(td) +msgid "container_listing_ratelimit_0 = 100" +msgstr "" + +#: ./doc/common/tables/swift-proxy-server-filter-ratelimit.xml:72(td) +msgid "container_listing_ratelimit_10 = 50" +msgstr "" + +#: ./doc/common/tables/swift-proxy-server-filter-ratelimit.xml:75(td) +msgid "container_listing_ratelimit_50 = 20" +msgstr "" + +#: ./doc/common/tables/cinder-block-device.xml:8(caption) +msgid "Description of configuration options for block-device" +msgstr "" + +#: ./doc/common/tables/cinder-block-device.xml:22(td) +msgid "available_devices =" +msgstr "" + +#: ./doc/common/tables/cinder-block-device.xml:23(td) +msgid "(ListOpt) List of all available devices" +msgstr "" + +#: ./doc/common/tables/cinder-zones.xml:8(caption) +msgid "Description of configuration options for zones" +msgstr "" + +#: ./doc/common/tables/cinder-zones.xml:22(td) +msgid "cloned_volume_same_az = True" +msgstr "" + +#: ./doc/common/tables/cinder-zones.xml:23(td) +msgid "(BoolOpt) Ensure that the new volumes are the same AZ as snapshot or source volume" +msgstr "" + +#: ./doc/common/tables/cinder-netapp_7mode_iscsi.xml:8(caption) +msgid "Description of configuration options for netapp_7mode_iscsi" +msgstr "" + +#: ./doc/common/tables/cinder-netapp_7mode_iscsi.xml:22(td) ./doc/common/tables/cinder-netapp_cdot_iscsi.xml:22(td) ./doc/common/tables/cinder-netapp_7mode_nfs.xml:26(td) ./doc/common/tables/cinder-netapp_cdot_nfs.xml:26(td) +msgid "netapp_login = None" +msgstr "" + +#: ./doc/common/tables/cinder-netapp_7mode_iscsi.xml:23(td) ./doc/common/tables/cinder-netapp_cdot_iscsi.xml:23(td) ./doc/common/tables/cinder-netapp_7mode_nfs.xml:27(td) ./doc/common/tables/cinder-netapp_cdot_nfs.xml:27(td) +msgid "(StrOpt) Administrative user account name used to access the storage system." +msgstr "" + +#: ./doc/common/tables/cinder-netapp_7mode_iscsi.xml:26(td) ./doc/common/tables/cinder-netapp_cdot_iscsi.xml:26(td) ./doc/common/tables/cinder-netapp_7mode_nfs.xml:30(td) ./doc/common/tables/cinder-netapp_cdot_nfs.xml:30(td) +msgid "netapp_password = None" +msgstr "" + +#: ./doc/common/tables/cinder-netapp_7mode_iscsi.xml:27(td) ./doc/common/tables/cinder-netapp_cdot_iscsi.xml:27(td) ./doc/common/tables/cinder-netapp_7mode_nfs.xml:31(td) ./doc/common/tables/cinder-netapp_cdot_nfs.xml:31(td) +msgid "(StrOpt) Password for the administrative user account specified in the netapp_login option." +msgstr "" + +#: ./doc/common/tables/cinder-netapp_7mode_iscsi.xml:30(td) ./doc/common/tables/cinder-netapp_cdot_iscsi.xml:30(td) ./doc/common/tables/cinder-netapp_7mode_nfs.xml:34(td) ./doc/common/tables/cinder-netapp_cdot_nfs.xml:34(td) +msgid "netapp_server_hostname = None" +msgstr "" + +#: ./doc/common/tables/cinder-netapp_7mode_iscsi.xml:31(td) ./doc/common/tables/cinder-netapp_cdot_iscsi.xml:31(td) ./doc/common/tables/cinder-netapp_7mode_nfs.xml:35(td) ./doc/common/tables/cinder-netapp_cdot_nfs.xml:35(td) +msgid "(StrOpt) The hostname (or IP address) for the storage system." +msgstr "" + +#: ./doc/common/tables/cinder-netapp_7mode_iscsi.xml:34(td) ./doc/common/tables/cinder-netapp_cdot_iscsi.xml:34(td) ./doc/common/tables/cinder-netapp_7mode_nfs.xml:38(td) ./doc/common/tables/cinder-netapp_cdot_nfs.xml:38(td) +msgid "netapp_server_port = 80" +msgstr "" + +#: ./doc/common/tables/cinder-netapp_7mode_iscsi.xml:35(td) ./doc/common/tables/cinder-netapp_cdot_iscsi.xml:35(td) ./doc/common/tables/cinder-netapp_7mode_nfs.xml:39(td) ./doc/common/tables/cinder-netapp_cdot_nfs.xml:39(td) +msgid "(IntOpt) The TCP port to use for communication with ONTAPI on the storage system. Traditionally, port 80 is used for HTTP and port 443 is used for HTTPS; however, this value should be changed if an alternate port has been configured on the storage system." +msgstr "" + +#: ./doc/common/tables/cinder-netapp_7mode_iscsi.xml:38(td) ./doc/common/tables/cinder-netapp_cdot_iscsi.xml:38(td) +msgid "netapp_size_multiplier = 1.2" +msgstr "" + +#: ./doc/common/tables/cinder-netapp_7mode_iscsi.xml:39(td) ./doc/common/tables/cinder-netapp_cdot_iscsi.xml:39(td) +msgid "(FloatOpt) The quantity to be multiplied by the requested volume size to ensure enough space is available on the virtual storage server (Vserver) to fulfill the volume creation request." +msgstr "" + +#: ./doc/common/tables/cinder-netapp_7mode_iscsi.xml:42(td) ./doc/common/tables/cinder-netapp_cdot_iscsi.xml:42(td) ./doc/common/tables/cinder-netapp_7mode_nfs.xml:42(td) ./doc/common/tables/cinder-netapp_cdot_nfs.xml:42(td) +msgid "netapp_storage_family = ontap_cluster" +msgstr "" + +#: ./doc/common/tables/cinder-netapp_7mode_iscsi.xml:43(td) ./doc/common/tables/cinder-netapp_cdot_iscsi.xml:43(td) ./doc/common/tables/cinder-netapp_7mode_nfs.xml:43(td) ./doc/common/tables/cinder-netapp_cdot_nfs.xml:43(td) +msgid "(StrOpt) The storage family type used on the storage system; valid values are ontap_7mode for using Data ONTAP operating in 7-Mode or ontap_cluster for using clustered Data ONTAP." +msgstr "" + +#: ./doc/common/tables/cinder-netapp_7mode_iscsi.xml:46(td) ./doc/common/tables/cinder-netapp_cdot_iscsi.xml:46(td) ./doc/common/tables/cinder-netapp_7mode_nfs.xml:46(td) ./doc/common/tables/cinder-netapp_cdot_nfs.xml:46(td) +msgid "netapp_storage_protocol = None" +msgstr "" + +#: ./doc/common/tables/cinder-netapp_7mode_iscsi.xml:47(td) ./doc/common/tables/cinder-netapp_cdot_iscsi.xml:47(td) ./doc/common/tables/cinder-netapp_7mode_nfs.xml:47(td) ./doc/common/tables/cinder-netapp_cdot_nfs.xml:47(td) +msgid "(StrOpt) The storage protocol to be used on the data path with the storage system; valid values are iscsi or nfs." +msgstr "" + +#: ./doc/common/tables/cinder-netapp_7mode_iscsi.xml:50(td) ./doc/common/tables/cinder-netapp_cdot_iscsi.xml:50(td) ./doc/common/tables/cinder-netapp_7mode_nfs.xml:50(td) ./doc/common/tables/cinder-netapp_cdot_nfs.xml:50(td) +msgid "netapp_transport_type = http" +msgstr "" + +#: ./doc/common/tables/cinder-netapp_7mode_iscsi.xml:51(td) ./doc/common/tables/cinder-netapp_cdot_iscsi.xml:51(td) ./doc/common/tables/cinder-netapp_7mode_nfs.xml:51(td) ./doc/common/tables/cinder-netapp_cdot_nfs.xml:51(td) +msgid "(StrOpt) The transport protocol used when communicating with ONTAPI on the storage system. Valid values are http or https." +msgstr "" + +#: ./doc/common/tables/cinder-netapp_7mode_iscsi.xml:54(td) +msgid "netapp_vfiler = None" +msgstr "" + +#: ./doc/common/tables/cinder-netapp_7mode_iscsi.xml:55(td) +msgid "(StrOpt) The vFiler unit on which provisioning of block storage volumes will be done. This option is only used by the driver when connecting to an instance with a storage family of Data ONTAP operating in 7-Mode and the storage protocol selected is iSCSI. Only use this option when utilizing the MultiStore feature on the NetApp storage system." +msgstr "" + +#: ./doc/common/tables/cinder-netapp_7mode_iscsi.xml:58(td) +msgid "netapp_volume_list = None" +msgstr "" + +#: ./doc/common/tables/cinder-netapp_7mode_iscsi.xml:59(td) +msgid "(StrOpt) This option is only utilized when the storage protocol is configured to use iSCSI. This option is used to restrict provisioning to the specified controller volumes. Specify the value of this option to be a comma separated list of NetApp controller volume names to be used for provisioning." +msgstr "" + +#: ./doc/common/tables/swift-container-server-container-sync.xml:7(literal) +msgid "[container-sync]" +msgstr "" + +#: ./doc/common/tables/swift-container-server-container-sync.xml:18(td) +msgid "log_name = container-sync" +msgstr "" + +#: ./doc/common/tables/swift-container-server-container-sync.xml:30(td) +msgid "sync_proxy = http://127.0.0.1:8888" +msgstr "" + +#: ./doc/common/tables/swift-container-server-container-sync.xml:30(td) +msgid "If you need to use an HTTP proxy, set it here. Defaults to no proxy." +msgstr "" + +#: ./doc/common/tables/swift-container-server-container-sync.xml:36(td) +msgid "container_time = 60" +msgstr "" + +#: ./doc/common/tables/swift-container-server-container-sync.xml:36(td) +msgid "Maximum amount of time to spend syncing each container" +msgstr "" + +#: ./doc/common/tables/neutron-common.xml:8(caption) ./doc/common/tables/nova-common.xml:8(caption) ./doc/common/tables/glance-common.xml:8(caption) ./doc/common/tables/cinder-common.xml:8(caption) +msgid "Description of configuration options for common" +msgstr "" + +#: ./doc/common/tables/neutron-common.xml:19(td) ./doc/common/tables/neutron-common.xml:23(td) ./doc/common/tables/neutron-common.xml:27(td) ./doc/common/tables/glance-registry.xml:22(td) +msgid "admin_password = None" +msgstr "" + +#: ./doc/common/tables/neutron-common.xml:20(td) ./doc/common/tables/neutron-common.xml:24(td) +msgid "(StrOpt) Admin password" +msgstr "" + +#: ./doc/common/tables/neutron-common.xml:28(td) +msgid "(StrOpt) ESM admin password." +msgstr "" + +#: ./doc/common/tables/neutron-common.xml:31(td) ./doc/common/tables/neutron-common.xml:35(td) ./doc/common/tables/glance-registry.xml:26(td) +msgid "admin_tenant_name = None" +msgstr "" + +#: ./doc/common/tables/neutron-common.xml:32(td) ./doc/common/tables/neutron-common.xml:36(td) +msgid "(StrOpt) Admin tenant name" +msgstr "" + +#: ./doc/common/tables/neutron-common.xml:39(td) ./doc/common/tables/neutron-common.xml:43(td) ./doc/common/tables/glance-registry.xml:30(td) +msgid "admin_user = None" +msgstr "" + +#: ./doc/common/tables/neutron-common.xml:40(td) +msgid "(StrOpt) Admin username" +msgstr "" + +#: ./doc/common/tables/neutron-common.xml:44(td) +msgid "(StrOpt) Admin user" +msgstr "" + +#: ./doc/common/tables/neutron-common.xml:47(td) +msgid "allowed_rpc_exception_modules = neutron.openstack.common.exception, nova.exception, cinder.exception, exceptions" +msgstr "" + +#: ./doc/common/tables/neutron-common.xml:48(td) ./doc/common/tables/nova-testing.xml:23(td) ./doc/common/tables/cinder-rpc.xml:23(td) ./doc/common/tables/glance-rpc.xml:23(td) +msgid "(ListOpt) Modules of exceptions that are permitted to be recreatedupon receiving exception data from an rpc call." +msgstr "" + +#: ./doc/common/tables/neutron-common.xml:51(td) +msgid "api_workers = 0" +msgstr "" + +#: ./doc/common/tables/neutron-common.xml:52(td) +msgid "(IntOpt) Number of separate worker processes for service" +msgstr "" + +#: ./doc/common/tables/neutron-common.xml:55(td) ./doc/common/tables/neutron-common.xml:59(td) ./doc/common/tables/glance-registry.xml:34(td) +msgid "auth_region = None" +msgstr "" + +#: ./doc/common/tables/neutron-common.xml:56(td) ./doc/common/tables/neutron-common.xml:60(td) +msgid "(StrOpt) Authentication region" +msgstr "" + +#: ./doc/common/tables/neutron-common.xml:63(td) ./doc/common/tables/neutron-metadata.xml:19(td) +msgid "auth_strategy = keystone" +msgstr "" + +#: ./doc/common/tables/neutron-common.xml:64(td) ./doc/common/tables/neutron-metadata.xml:20(td) +msgid "(StrOpt) The type of authentication to use" +msgstr "" + +#: ./doc/common/tables/neutron-common.xml:67(td) ./doc/common/tables/neutron-common.xml:71(td) ./doc/common/tables/glance-registry.xml:42(td) +msgid "auth_url = None" +msgstr "" + +#: ./doc/common/tables/neutron-common.xml:68(td) ./doc/common/tables/neutron-common.xml:72(td) +msgid "(StrOpt) Authentication URL" +msgstr "" + +#: ./doc/common/tables/neutron-common.xml:75(td) +msgid "base_mac = fa:16:3e:00:00:00" +msgstr "" + +#: ./doc/common/tables/neutron-common.xml:76(td) +msgid "(StrOpt) The base MAC address Neutron will use for VIFs" +msgstr "" + +#: ./doc/common/tables/neutron-common.xml:79(td) ./doc/common/tables/glance-common.xml:34(td) +msgid "bind_host = 0.0.0.0" +msgstr "" + +#: ./doc/common/tables/neutron-common.xml:80(td) +msgid "(StrOpt) The host IP to bind to" +msgstr "" + +#: ./doc/common/tables/neutron-common.xml:83(td) +msgid "bind_port = 9696" +msgstr "" + +#: ./doc/common/tables/neutron-common.xml:84(td) +msgid "(IntOpt) The port to bind to" +msgstr "" + +#: ./doc/common/tables/neutron-common.xml:87(td) +msgid "core_plugin = None" +msgstr "" + +#: ./doc/common/tables/neutron-common.xml:88(td) +msgid "(StrOpt) The core plugin Neutron will use" +msgstr "" + +#: ./doc/common/tables/neutron-common.xml:91(td) +msgid "dhcp_agent_notification = True" +msgstr "" + +#: ./doc/common/tables/neutron-common.xml:92(td) +msgid "(BoolOpt) Allow sending resource operation notification to DHCP agent" +msgstr "" + +#: ./doc/common/tables/neutron-common.xml:95(td) +msgid "dhcp_lease_duration = 86400" +msgstr "" + +#: ./doc/common/tables/neutron-common.xml:96(td) +msgid "(IntOpt) DHCP lease duration" +msgstr "" + +#: ./doc/common/tables/neutron-common.xml:99(td) ./doc/common/tables/nova-common.xml:38(td) ./doc/common/tables/glance-common.xml:46(td) ./doc/common/tables/cinder-common.xml:50(td) +msgid "disable_process_locking = False" +msgstr "" + +#: ./doc/common/tables/neutron-common.xml:100(td) ./doc/common/tables/nova-common.xml:39(td) ./doc/common/tables/glance-common.xml:47(td) ./doc/common/tables/cinder-common.xml:51(td) +msgid "(BoolOpt) Whether to disable inter-process locks" +msgstr "" + +#: ./doc/common/tables/neutron-common.xml:103(td) +msgid "force_gateway_on_subnet = False" +msgstr "" + +#: ./doc/common/tables/neutron-common.xml:104(td) +msgid "(BoolOpt) Ensure that configured gateway is on subnet" +msgstr "" + +#: ./doc/common/tables/neutron-common.xml:107(td) +msgid "host = [hostname]" +msgstr "" + +#: ./doc/common/tables/neutron-common.xml:108(td) +msgid "(StrOpt) The hostname Neutron is running on" +msgstr "" + +#: ./doc/common/tables/neutron-common.xml:111(td) ./doc/common/tables/nova-common.xml:46(td) ./doc/common/tables/glance-common.xml:70(td) ./doc/common/tables/cinder-common.xml:78(td) +msgid "lock_path = None" +msgstr "" + +#: ./doc/common/tables/neutron-common.xml:112(td) ./doc/common/tables/cinder-common.xml:79(td) +msgid "(StrOpt) Directory to use for lock files. Default to a temp directory" +msgstr "" + +#: ./doc/common/tables/neutron-common.xml:115(td) +msgid "mac_generation_retries = 16" +msgstr "" + +#: ./doc/common/tables/neutron-common.xml:116(td) +msgid "(IntOpt) How many times Neutron will retry MAC generation" +msgstr "" + +#: ./doc/common/tables/neutron-common.xml:119(td) +msgid "max_dns_nameservers = 5" +msgstr "" + +#: ./doc/common/tables/neutron-common.xml:120(td) +msgid "(IntOpt) Maximum number of DNS nameservers" +msgstr "" + +#: ./doc/common/tables/neutron-common.xml:123(td) +msgid "max_fixed_ips_per_port = 5" +msgstr "" + +#: ./doc/common/tables/neutron-common.xml:124(td) +msgid "(IntOpt) Maximum number of fixed ips per port" +msgstr "" + +#: ./doc/common/tables/neutron-common.xml:127(td) +msgid "max_subnet_host_routes = 20" +msgstr "" + +#: ./doc/common/tables/neutron-common.xml:128(td) +msgid "(IntOpt) Maximum number of host routes per subnet" +msgstr "" + +#: ./doc/common/tables/neutron-common.xml:131(td) +msgid "meta_flavor_driver_mappings = None" +msgstr "" + +#: ./doc/common/tables/neutron-common.xml:132(td) +msgid "(StrOpt) Mapping between flavor and LinuxInterfaceDriver" +msgstr "" + +#: ./doc/common/tables/neutron-common.xml:135(td) ./doc/common/tables/nova-network.xml:170(td) +msgid "network_device_mtu = None" +msgstr "" + +#: ./doc/common/tables/neutron-common.xml:136(td) +msgid "(IntOpt) MTU setting for device." +msgstr "" + +#: ./doc/common/tables/neutron-common.xml:139(td) ./doc/common/tables/neutron-openvswitch.xml:19(td) ./doc/common/tables/neutron-hyperv.xml:19(td) +msgid "network_vlan_ranges =" +msgstr "" + +#: ./doc/common/tables/neutron-common.xml:140(td) ./doc/common/tables/neutron-openvswitch.xml:20(td) ./doc/common/tables/neutron-hyperv.xml:20(td) +msgid "(ListOpt) List of <physical_network>:<vlan_min>:<vlan_max> or <physical_network>" +msgstr "" + +#: ./doc/common/tables/neutron-common.xml:143(td) +msgid "ovs_integration_bridge = br-int" +msgstr "" + +#: ./doc/common/tables/neutron-common.xml:144(td) +msgid "(StrOpt) Name of Open vSwitch bridge to use" +msgstr "" + +#: ./doc/common/tables/neutron-common.xml:147(td) +msgid "ovs_use_veth = False" +msgstr "" + +#: ./doc/common/tables/neutron-common.xml:148(td) +msgid "(BoolOpt) Uses veth for an interface or not" +msgstr "" + +#: ./doc/common/tables/neutron-common.xml:151(td) +msgid "periodic_fuzzy_delay = 5" +msgstr "" + +#: ./doc/common/tables/neutron-common.xml:152(td) +msgid "(IntOpt) Range of seconds to randomly delay when starting the periodic task scheduler to reduce stampeding. (Disable by setting to 0)" +msgstr "" + +#: ./doc/common/tables/neutron-common.xml:155(td) +msgid "periodic_interval = 40" +msgstr "" + +#: ./doc/common/tables/neutron-common.xml:156(td) +msgid "(IntOpt) Seconds between running periodic tasks" +msgstr "" + +#: ./doc/common/tables/neutron-common.xml:159(td) ./doc/common/tables/neutron-common.xml:163(td) ./doc/common/tables/cinder-common.xml:166(td) +msgid "root_helper = sudo" +msgstr "" + +#: ./doc/common/tables/neutron-common.xml:160(td) ./doc/common/tables/neutron-common.xml:164(td) +msgid "(StrOpt) Root helper application." +msgstr "" + +#: ./doc/common/tables/neutron-common.xml:167(td) +msgid "state_path = /var/lib/neutron" +msgstr "" + +#: ./doc/common/tables/neutron-common.xml:168(td) +msgid "(StrOpt) Where to store Neutron state files. This directory must be writable by the agent." +msgstr "" + +#: ./doc/common/tables/swift-object-server-object-auditor.xml:7(literal) +msgid "[object-auditor]" +msgstr "" + +#: ./doc/common/tables/swift-object-server-object-auditor.xml:7(literal) ./doc/common/tables/swift-object-server-object-updater.xml:7(literal) ./doc/common/tables/swift-object-server-pipeline-main.xml:7(literal) ./doc/common/tables/swift-object-server-DEFAULT.xml:7(literal) ./doc/common/tables/swift-object-server-filter-recon.xml:7(literal) ./doc/common/tables/swift-object-server-object-replicator.xml:7(literal) ./doc/common/tables/swift-object-server-app-object-server.xml:7(literal) ./doc/common/tables/swift-object-server-filter-healthcheck.xml:7(literal) +msgid "object-server.conf-sample" +msgstr "" + +#: ./doc/common/tables/swift-object-server-object-auditor.xml:18(td) +msgid "log_name = object-auditor" +msgstr "" + +#: ./doc/common/tables/swift-object-server-object-auditor.xml:30(td) +msgid "files_per_second = 20" +msgstr "" + +#: ./doc/common/tables/swift-object-server-object-auditor.xml:30(td) +msgid "Maximum files audited per second. Should be tuned according to individual system specs. 0 is unlimited." +msgstr "" + +#: ./doc/common/tables/swift-object-server-object-auditor.xml:33(td) +msgid "bytes_per_second = 10000000" +msgstr "" + +#: ./doc/common/tables/swift-object-server-object-auditor.xml:33(td) +msgid "Maximum bytes audited per second. Should be tuned according to individual system specs. 0 is unlimited. mounted to prevent accidentally writing to the root device process simultaneously (it will actually accept(2) N + 1). Setting this to one (1) will only handle one request at a time, without accepting another request concurrently. By increasing the number of workers to a much higher value, one can reduce the impact of slow file system operations in one request from negatively impacting other requests. underlying filesystem does not support it. to setup custom log handlers. bytes you'd like fallocate to reserve, whether there is space for the given file size or not. This is useful for systems that behave badly when they completely run out of space; you can make the services pretend they're out of space early. container server. For most cases, this should be `egg:swift#container`." +msgstr "" + +#: ./doc/common/tables/swift-object-server-object-auditor.xml:36(td) +msgid "log_time = 3600" +msgstr "" + +#: ./doc/common/tables/swift-object-server-object-auditor.xml:36(td) +msgid "Frequency of status logs in seconds." +msgstr "" + +#: ./doc/common/tables/swift-object-server-object-auditor.xml:39(td) +msgid "zero_byte_files_per_second = 50" +msgstr "" + +#: ./doc/common/tables/swift-object-server-object-auditor.xml:39(td) +msgid "Maximum zero byte files audited per second." +msgstr "" + +#: ./doc/common/tables/swift-object-server-object-auditor.xml:45(td) +msgid "object_size_stats =" +msgstr "" + +#: ./doc/common/tables/neutron-openvswitch_agent.xml:8(caption) +msgid "Description of configuration options for openvswitch_agent" +msgstr "" + +#: ./doc/common/tables/neutron-openvswitch_agent.xml:19(td) ./doc/common/tables/neutron-openvswitch_agent.xml:23(td) +msgid "bridge_mappings =" +msgstr "" + +#: ./doc/common/tables/neutron-openvswitch_agent.xml:20(td) +msgid "(StrOpt) N1K Bridge Mappings" +msgstr "" + +#: ./doc/common/tables/neutron-openvswitch_agent.xml:24(td) +msgid "(ListOpt) List of <physical_network>:<bridge>" +msgstr "" + +#: ./doc/common/tables/neutron-openvswitch_agent.xml:27(td) +msgid "enable_tunneling = True" +msgstr "" + +#: ./doc/common/tables/neutron-openvswitch_agent.xml:28(td) +msgid "(BoolOpt) N1K Enable Tunneling" +msgstr "" + +#: ./doc/common/tables/neutron-openvswitch_agent.xml:31(td) +msgid "enable_tunneling = False" +msgstr "" + +#: ./doc/common/tables/neutron-openvswitch_agent.xml:32(td) +msgid "(BoolOpt) Enable tunneling support" +msgstr "" + +#: ./doc/common/tables/neutron-openvswitch_agent.xml:35(td) +msgid "int_peer_patch_port = patch-tun" +msgstr "" + +#: ./doc/common/tables/neutron-openvswitch_agent.xml:36(td) +msgid "(StrOpt) Peer patch port in integration bridge for tunnel bridge" +msgstr "" + +#: ./doc/common/tables/neutron-openvswitch_agent.xml:39(td) ./doc/common/tables/neutron-openvswitch_agent.xml:43(td) ./doc/common/tables/nova-vmware.xml:46(td) +msgid "integration_bridge = br-int" +msgstr "" + +#: ./doc/common/tables/neutron-openvswitch_agent.xml:40(td) +msgid "(StrOpt) N1K Integration Bridge" +msgstr "" + +#: ./doc/common/tables/neutron-openvswitch_agent.xml:44(td) +msgid "(StrOpt) Integration bridge to use" +msgstr "" + +#: ./doc/common/tables/neutron-openvswitch_agent.xml:47(td) ./doc/common/tables/neutron-linuxbridge_agent.xml:23(td) +msgid "l2_population = False" +msgstr "" + +#: ./doc/common/tables/neutron-openvswitch_agent.xml:48(td) +msgid "(BoolOpt) Use ml2 l2population mechanism driver to learn remote mac and IPs and improve tunnel scalability" +msgstr "" + +#: ./doc/common/tables/neutron-openvswitch_agent.xml:51(td) ./doc/common/tables/neutron-openvswitch_agent.xml:59(td) +msgid "local_ip =" +msgstr "" + +#: ./doc/common/tables/neutron-openvswitch_agent.xml:52(td) +msgid "(StrOpt) Local IP address of the VXLAN endpoints." +msgstr "" + +#: ./doc/common/tables/neutron-openvswitch_agent.xml:55(td) +msgid "local_ip = 10.0.0.3" +msgstr "" + +#: ./doc/common/tables/neutron-openvswitch_agent.xml:56(td) +msgid "(StrOpt) N1K Local IP" +msgstr "" + +#: ./doc/common/tables/neutron-openvswitch_agent.xml:60(td) +msgid "(StrOpt) Local IP address of GRE tunnel endpoints." +msgstr "" + +#: ./doc/common/tables/neutron-openvswitch_agent.xml:63(td) +msgid "minimize_polling = True" +msgstr "" + +#: ./doc/common/tables/neutron-openvswitch_agent.xml:64(td) +msgid "(BoolOpt) Minimize polling by monitoring ovsdb for interface changes." +msgstr "" + +#: ./doc/common/tables/neutron-openvswitch_agent.xml:67(td) +msgid "ovsdb_monitor_respawn_interval = 30" +msgstr "" + +#: ./doc/common/tables/neutron-openvswitch_agent.xml:68(td) +msgid "(IntOpt) The number of seconds to wait before respawning the ovsdb monitor after losing communication with it" +msgstr "" + +#: ./doc/common/tables/neutron-openvswitch_agent.xml:71(td) ./doc/common/tables/neutron-linuxbridge.xml:19(td) ./doc/common/tables/neutron-hyperv.xml:23(td) +msgid "tenant_network_type = local" +msgstr "" + +#: ./doc/common/tables/neutron-openvswitch_agent.xml:72(td) +msgid "(StrOpt) Network type for tenant networks (local, vlan, gre, vxlan, or none)" +msgstr "" + +#: ./doc/common/tables/neutron-openvswitch_agent.xml:75(td) +msgid "tun_peer_patch_port = patch-int" +msgstr "" + +#: ./doc/common/tables/neutron-openvswitch_agent.xml:76(td) +msgid "(StrOpt) Peer patch port in tunnel bridge for integration bridge" +msgstr "" + +#: ./doc/common/tables/neutron-openvswitch_agent.xml:79(td) ./doc/common/tables/neutron-openvswitch_agent.xml:83(td) +msgid "tunnel_bridge = br-tun" +msgstr "" + +#: ./doc/common/tables/neutron-openvswitch_agent.xml:80(td) +msgid "(StrOpt) N1K Tunnel Bridge" +msgstr "" + +#: ./doc/common/tables/neutron-openvswitch_agent.xml:84(td) +msgid "(StrOpt) Tunnel bridge to use" +msgstr "" + +#: ./doc/common/tables/neutron-openvswitch_agent.xml:87(td) ./doc/common/tables/neutron-openvswitch_agent.xml:91(td) +msgid "tunnel_id_ranges =" +msgstr "" + +#: ./doc/common/tables/neutron-openvswitch_agent.xml:88(td) +msgid "(ListOpt) List of <tun_min>:<tun_max>" +msgstr "" + +#: ./doc/common/tables/neutron-openvswitch_agent.xml:92(td) +msgid "(ListOpt) Comma-separated list of <tun_min>:<tun_max> tuples enumerating ranges of GRE tunnel IDs that are available for tenant network allocation" +msgstr "" + +#: ./doc/common/tables/neutron-openvswitch_agent.xml:95(td) +msgid "tunnel_type =" +msgstr "" + +#: ./doc/common/tables/neutron-openvswitch_agent.xml:96(td) +msgid "(StrOpt) The type of tunnels to use when utilizing tunnels, either 'gre' or 'vxlan'" +msgstr "" + +#: ./doc/common/tables/neutron-openvswitch_agent.xml:99(td) +msgid "tunnel_types =" +msgstr "" + +#: ./doc/common/tables/neutron-openvswitch_agent.xml:100(td) +msgid "(ListOpt) Network types supported by the agent (gre and/or vxlan)" +msgstr "" + +#: ./doc/common/tables/neutron-openvswitch_agent.xml:103(td) +msgid "veth_mtu = None" +msgstr "" + +#: ./doc/common/tables/neutron-openvswitch_agent.xml:104(td) +msgid "(IntOpt) MTU size of veth interfaces" +msgstr "" + +#: ./doc/common/tables/neutron-openvswitch_agent.xml:107(td) +msgid "vxlan_udp_port = 4789" +msgstr "" + +#: ./doc/common/tables/neutron-openvswitch_agent.xml:108(td) +msgid "(IntOpt) The UDP port to use for VXLAN tunnels." +msgstr "" + +#: ./doc/common/tables/cinder-compute.xml:8(caption) ./doc/common/tables/nova-compute.xml:8(caption) +msgid "Description of configuration options for compute" +msgstr "" + +#: ./doc/common/tables/cinder-compute.xml:22(td) +msgid "nova_api_insecure = False" +msgstr "" + +#: ./doc/common/tables/cinder-compute.xml:23(td) +msgid "(BoolOpt) Allow to perform insecure SSL requests to nova" +msgstr "" + +#: ./doc/common/tables/cinder-compute.xml:26(td) +msgid "nova_ca_certificates_file = None" +msgstr "" + +#: ./doc/common/tables/cinder-compute.xml:27(td) +msgid "(StrOpt) Location of ca certificates file to use for nova client requests." +msgstr "" + +#: ./doc/common/tables/cinder-compute.xml:30(td) +msgid "nova_catalog_admin_info = compute:nova:adminURL" +msgstr "" + +#: ./doc/common/tables/cinder-compute.xml:31(td) +msgid "(StrOpt) Same as nova_catalog_info, but for admin endpoint." +msgstr "" + +#: ./doc/common/tables/cinder-compute.xml:34(td) +msgid "nova_catalog_info = compute:nova:publicURL" +msgstr "" + +#: ./doc/common/tables/cinder-compute.xml:35(td) +msgid "(StrOpt) Info to match when looking for nova in the service catalog. Format is : separated values of the form: <service_type>:<service_name>:<endpoint_type>" +msgstr "" + +#: ./doc/common/tables/cinder-compute.xml:38(td) +msgid "nova_endpoint_admin_template = None" +msgstr "" + +#: ./doc/common/tables/cinder-compute.xml:39(td) +msgid "(StrOpt) Same as nova_endpoint_template, but for admin endpoint." +msgstr "" + +#: ./doc/common/tables/cinder-compute.xml:42(td) +msgid "nova_endpoint_template = None" +msgstr "" + +#: ./doc/common/tables/cinder-compute.xml:43(td) +msgid "(StrOpt) Override service catalog lookup with template for nova endpoint e.g. http://localhost:8774/v2/%(tenant_id)s" +msgstr "" + +#: ./doc/common/tables/cinder-lvm.xml:8(caption) +msgid "Description of configuration options for lvm" +msgstr "" + +#: ./doc/common/tables/cinder-lvm.xml:22(td) +msgid "lvm_mirrors = 0" +msgstr "" + +#: ./doc/common/tables/cinder-lvm.xml:23(td) +msgid "(IntOpt) If set, create lvms with multiple mirrors. Note that this requires lvm_mirrors + 2 pvs with available space" +msgstr "" + +#: ./doc/common/tables/cinder-lvm.xml:26(td) +msgid "lvm_type = default" +msgstr "" + +#: ./doc/common/tables/cinder-lvm.xml:27(td) +msgid "(StrOpt) Type of LVM volumes to deploy; (default or thin)" +msgstr "" + +#: ./doc/common/tables/cinder-lvm.xml:30(td) +msgid "volume_group = cinder-volumes" +msgstr "" + +#: ./doc/common/tables/cinder-lvm.xml:31(td) +msgid "(StrOpt) Name for the VG that will contain exported volumes" +msgstr "" + +#: ./doc/common/tables/cinder-storage_nfs.xml:8(caption) +msgid "Description of configuration options for storage_nfs" +msgstr "" + +#: ./doc/common/tables/cinder-storage_nfs.xml:23(td) +msgid "(StrOpt) Mount options passed to the nfs client. See section of the nfs man page for details." +msgstr "" + +#: ./doc/common/tables/cinder-storage_nfs.xml:27(td) +msgid "(StrOpt) Base dir containing mount points for nfs shares." +msgstr "" + +#: ./doc/common/tables/cinder-storage_nfs.xml:30(td) +msgid "nfs_oversub_ratio = 1.0" +msgstr "" + +#: ./doc/common/tables/cinder-storage_nfs.xml:31(td) ./doc/common/tables/cinder-nexenta_nfs.xml:35(td) +msgid "(FloatOpt) This will compare the allocated to available space on the volume destination. If the ratio exceeds this number, the destination will no longer be valid." +msgstr "" + +#: ./doc/common/tables/cinder-storage_nfs.xml:34(td) +msgid "nfs_shares_config = /etc/cinder/nfs_shares" +msgstr "" + +#: ./doc/common/tables/cinder-storage_nfs.xml:35(td) ./doc/common/tables/cinder-nexenta_nfs.xml:39(td) +msgid "(StrOpt) File with the list of available nfs shares" +msgstr "" + +#: ./doc/common/tables/cinder-storage_nfs.xml:38(td) +msgid "nfs_sparsed_volumes = True" +msgstr "" + +#: ./doc/common/tables/cinder-storage_nfs.xml:42(td) +msgid "nfs_used_ratio = 0.95" +msgstr "" + +#: ./doc/common/tables/cinder-storage_nfs.xml:43(td) ./doc/common/tables/cinder-nexenta_nfs.xml:43(td) +msgid "(FloatOpt) Percent of ACTUAL usage of the underlying volume before no new volumes can be allocated to the volume destination." +msgstr "" + +#: ./doc/common/tables/neutron-plumgrid.xml:8(caption) +msgid "Description of configuration options for plumgrid" +msgstr "" + +#: ./doc/common/tables/neutron-plumgrid.xml:19(td) +msgid "director_server = localhost" +msgstr "" + +#: ./doc/common/tables/neutron-plumgrid.xml:20(td) +msgid "(StrOpt) PLUMgrid Director server to connect to" +msgstr "" + +#: ./doc/common/tables/neutron-plumgrid.xml:23(td) +msgid "director_server_port = 8080" +msgstr "" + +#: ./doc/common/tables/neutron-plumgrid.xml:24(td) +msgid "(StrOpt) PLUMgrid Director server port to connect to" +msgstr "" + +#: ./doc/common/tables/neutron-plumgrid.xml:27(td) +msgid "password = password" +msgstr "" + +#: ./doc/common/tables/neutron-plumgrid.xml:28(td) +msgid "(StrOpt) PLUMgrid Director admin password" +msgstr "" + +#: ./doc/common/tables/neutron-plumgrid.xml:31(td) +msgid "servertimeout = 5" +msgstr "" + +#: ./doc/common/tables/neutron-plumgrid.xml:32(td) +msgid "(IntOpt) PLUMgrid Director server timeout" +msgstr "" + +#: ./doc/common/tables/neutron-plumgrid.xml:35(td) +msgid "username = username" +msgstr "" + +#: ./doc/common/tables/neutron-plumgrid.xml:36(td) +msgid "(StrOpt) PLUMgrid Director admin username" +msgstr "" + +#: ./doc/common/tables/nova-hypervisor.xml:8(caption) +msgid "Description of configuration options for hypervisor" +msgstr "" + +#: ./doc/common/tables/nova-hypervisor.xml:22(td) +msgid "default_ephemeral_format = None" +msgstr "" + +#: ./doc/common/tables/nova-hypervisor.xml:23(td) +msgid "(StrOpt) The default format an ephemeral_volume will be formatted with on creation." +msgstr "" + +#: ./doc/common/tables/nova-hypervisor.xml:26(td) +msgid "force_raw_images = True" +msgstr "" + +#: ./doc/common/tables/nova-hypervisor.xml:27(td) +msgid "(BoolOpt) Force backing images to raw format" +msgstr "" + +#: ./doc/common/tables/nova-hypervisor.xml:30(td) +msgid "preallocate_images = none" +msgstr "" + +#: ./doc/common/tables/nova-hypervisor.xml:31(td) +msgid "(StrOpt) VM image preallocation mode: \"none\" => no storage provisioning is done up front, \"space\" => storage is fully allocated at instance start" +msgstr "" + +#: ./doc/common/tables/nova-hypervisor.xml:34(td) +msgid "rescue_timeout = 0" +msgstr "" + +#: ./doc/common/tables/nova-hypervisor.xml:35(td) +msgid "(IntOpt) Automatically unrescue an instance after N seconds. Set to 0 to disable." +msgstr "" + +#: ./doc/common/tables/nova-hypervisor.xml:38(td) +msgid "timeout_nbd = 10" +msgstr "" + +#: ./doc/common/tables/nova-hypervisor.xml:39(td) +msgid "(IntOpt) time to wait for a NBD device coming up" +msgstr "" + +#: ./doc/common/tables/nova-hypervisor.xml:42(td) +msgid "use_cow_images = True" +msgstr "" + +#: ./doc/common/tables/nova-hypervisor.xml:43(td) +msgid "(BoolOpt) Whether to use cow images" +msgstr "" + +#: ./doc/common/tables/nova-hypervisor.xml:46(td) +msgid "vcpu_pin_set = None" +msgstr "" + +#: ./doc/common/tables/nova-hypervisor.xml:47(td) +msgid "(StrOpt) Which pcpus can be used by vcpus of instance e.g: \"4-12,^8,15\"" +msgstr "" + +#: ./doc/common/tables/nova-hypervisor.xml:50(td) +msgid "virt_mkfs = []" +msgstr "" + +#: ./doc/common/tables/nova-hypervisor.xml:51(td) +msgid "(MultiStrOpt) mkfs commands for ephemeral device. The format is <os_type>=<mkfs command>" +msgstr "" + +#: ./doc/common/tables/nova-hypervisor.xml:57(td) +msgid "block_migration_flag = VIR_MIGRATE_UNDEFINE_SOURCE, VIR_MIGRATE_PEER2PEER, VIR_MIGRATE_NON_SHARED_INC" +msgstr "" + +#: ./doc/common/tables/nova-hypervisor.xml:58(td) +msgid "(StrOpt) Migration flags to be set for block migration" +msgstr "" + +#: ./doc/common/tables/nova-hypervisor.xml:61(td) +msgid "disk_cachemodes =" +msgstr "" + +#: ./doc/common/tables/nova-hypervisor.xml:62(td) +msgid "(ListOpt) Specific cachemodes to use for different disk types e.g: file=directsync,block=none" +msgstr "" + +#: ./doc/common/tables/nova-hypervisor.xml:65(td) +msgid "images_rbd_ceph_conf =" +msgstr "" + +#: ./doc/common/tables/nova-hypervisor.xml:66(td) ./doc/common/tables/cinder-storage_ceph.xml:23(td) +msgid "(StrOpt) path to the ceph configuration file to use" +msgstr "" + +#: ./doc/common/tables/nova-hypervisor.xml:69(td) +msgid "images_rbd_pool = rbd" +msgstr "" + +#: ./doc/common/tables/nova-hypervisor.xml:70(td) ./doc/common/tables/cinder-storage_ceph.xml:35(td) +msgid "(StrOpt) the RADOS pool in which rbd volumes are stored" +msgstr "" + +#: ./doc/common/tables/nova-hypervisor.xml:73(td) +msgid "images_type = default" +msgstr "" + +#: ./doc/common/tables/nova-hypervisor.xml:74(td) +msgid "(StrOpt) VM Images format. Acceptable values are: raw, qcow2, lvm,rbd, default. If default is specified, then use_cow_images flag is used instead of this one." +msgstr "" + +#: ./doc/common/tables/nova-hypervisor.xml:77(td) +msgid "images_volume_group = None" +msgstr "" + +#: ./doc/common/tables/nova-hypervisor.xml:78(td) +msgid "(StrOpt) LVM Volume Group that is used for VM images, when you specify images_type=lvm." +msgstr "" + +#: ./doc/common/tables/nova-hypervisor.xml:81(td) +msgid "inject_key = True" +msgstr "" + +#: ./doc/common/tables/nova-hypervisor.xml:82(td) +msgid "(BoolOpt) Inject the ssh public key at boot time" +msgstr "" + +#: ./doc/common/tables/nova-hypervisor.xml:85(td) +msgid "inject_partition = 1" +msgstr "" + +#: ./doc/common/tables/nova-hypervisor.xml:86(td) +msgid "(IntOpt) The partition to inject to : -2 => disable, -1 => inspect (libguestfs only), 0 => not partitioned, >0 => partition number" +msgstr "" + +#: ./doc/common/tables/nova-hypervisor.xml:89(td) +msgid "inject_password = False" +msgstr "" + +#: ./doc/common/tables/nova-hypervisor.xml:90(td) +msgid "(BoolOpt) Inject the admin password at boot time, without an agent." +msgstr "" + +#: ./doc/common/tables/nova-hypervisor.xml:93(td) +msgid "iscsi_use_multipath = False" +msgstr "" + +#: ./doc/common/tables/nova-hypervisor.xml:94(td) +msgid "(BoolOpt) use multipath connection of the iSCSI volume" +msgstr "" + +#: ./doc/common/tables/nova-hypervisor.xml:97(td) +msgid "iser_use_multipath = False" +msgstr "" + +#: ./doc/common/tables/nova-hypervisor.xml:98(td) +msgid "(BoolOpt) use multipath connection of the iSER volume" +msgstr "" + +#: ./doc/common/tables/nova-hypervisor.xml:101(td) +msgid "lvm_snapshot_size = 1000" +msgstr "" + +#: ./doc/common/tables/nova-hypervisor.xml:102(td) +msgid "(IntOpt) The amount of storage (in megabytes) to allocate for LVM snapshot copy-on-write blocks." +msgstr "" + +#: ./doc/common/tables/nova-hypervisor.xml:105(td) +msgid "rescue_image_id = None" +msgstr "" + +#: ./doc/common/tables/nova-hypervisor.xml:106(td) +msgid "(StrOpt) Rescue ami image" +msgstr "" + +#: ./doc/common/tables/nova-hypervisor.xml:109(td) +msgid "rescue_kernel_id = None" +msgstr "" + +#: ./doc/common/tables/nova-hypervisor.xml:110(td) +msgid "(StrOpt) Rescue aki image" +msgstr "" + +#: ./doc/common/tables/nova-hypervisor.xml:113(td) +msgid "rescue_ramdisk_id = None" +msgstr "" + +#: ./doc/common/tables/nova-hypervisor.xml:114(td) +msgid "(StrOpt) Rescue ari image" +msgstr "" + +#: ./doc/common/tables/nova-hypervisor.xml:117(td) +msgid "snapshot_compression = False" +msgstr "" + +#: ./doc/common/tables/nova-hypervisor.xml:118(td) +msgid "(BoolOpt) Compress snapshot images when possible. This currently applies exclusively to qcow2 images" +msgstr "" + +#: ./doc/common/tables/nova-hypervisor.xml:121(td) +msgid "snapshot_image_format = None" +msgstr "" + +#: ./doc/common/tables/nova-hypervisor.xml:122(td) +msgid "(StrOpt) Snapshot image format (valid options are : raw, qcow2, vmdk, vdi). Defaults to same as source image" +msgstr "" + +#: ./doc/common/tables/nova-hypervisor.xml:125(td) +msgid "sparse_logical_volumes = False" +msgstr "" + +#: ./doc/common/tables/nova-hypervisor.xml:126(td) +msgid "(BoolOpt) Create sparse logical volumes (with virtualsize) if this flag is set to True." +msgstr "" + +#: ./doc/common/tables/nova-hypervisor.xml:129(td) +msgid "use_usb_tablet = True" +msgstr "" + +#: ./doc/common/tables/nova-hypervisor.xml:130(td) +msgid "(BoolOpt) Sync virtual and real mouse cursors in Windows VMs" +msgstr "" + +#: ./doc/common/tables/nova-hypervisor.xml:133(td) +msgid "use_virtio_for_bridges = True" +msgstr "" + +#: ./doc/common/tables/nova-hypervisor.xml:134(td) +msgid "(BoolOpt) Use virtio for bridge interfaces with KVM/QEMU" +msgstr "" + +#: ./doc/common/tables/swift-proxy-server-filter-tempurl.xml:7(literal) +msgid "[filter:tempurl]" +msgstr "" + +#: ./doc/common/tables/swift-proxy-server-filter-tempurl.xml:18(td) +msgid "use = egg:swift#tempurl" +msgstr "" + +#: ./doc/common/tables/swift-proxy-server-filter-tempurl.xml:18(td) +msgid "Entry point of paste.deploy in the server. You should not ever need to change this." +msgstr "" + +#: ./doc/common/tables/swift-proxy-server-filter-tempurl.xml:21(td) +msgid "methods = GET HEAD PUT" +msgstr "" + +#: ./doc/common/tables/swift-proxy-server-filter-tempurl.xml:21(td) +msgid "HTTP methods allowed with Temporary URLs" +msgstr "" + +#: ./doc/common/tables/swift-proxy-server-filter-tempurl.xml:24(td) +msgid "incoming_remove_headers = x-timestamp" +msgstr "" + +#: ./doc/common/tables/swift-proxy-server-filter-tempurl.xml:24(td) +msgid "Headers to remove from incoming requests. Simply a whitespace delimited list of header names and names can optionally end with '*' to indicate a prefix match." +msgstr "" + +#: ./doc/common/tables/swift-proxy-server-filter-tempurl.xml:28(td) +msgid "incoming_allow_headers =" +msgstr "" + +#: ./doc/common/tables/swift-proxy-server-filter-tempurl.xml:29(td) +msgid "Headers allowed as exceptions to incoming_remove_headers. Simply a whitespace delimited list of header names and names can optionally end with '*' to indicate a prefix match." +msgstr "" + +#: ./doc/common/tables/swift-proxy-server-filter-tempurl.xml:34(td) +msgid "outgoing_remove_headers = x-object-meta-*" +msgstr "" + +#: ./doc/common/tables/swift-proxy-server-filter-tempurl.xml:35(td) +msgid "Headers to remove from outgoing responses. Simply a whitespace delimited list of header names and names can optionally end with '*' to indicate a prefix match." +msgstr "" + +#: ./doc/common/tables/swift-proxy-server-filter-tempurl.xml:40(td) +msgid "outgoing_allow_headers = x-object-meta-public-*" +msgstr "" + +#: ./doc/common/tables/swift-proxy-server-filter-tempurl.xml:40(td) +msgid "Headers allowed as exceptions to outgoing_allow_headers. Simply a whitespace delimited list of header names and names can optionally end with '*' to indicate a prefix match." +msgstr "" + +#: ./doc/common/tables/cinder-quota.xml:8(caption) ./doc/common/tables/nova-quota.xml:8(caption) +msgid "Description of configuration options for quota" +msgstr "" + +#: ./doc/common/tables/cinder-quota.xml:22(td) ./doc/common/tables/nova-policy.xml:34(td) +msgid "max_age = 0" +msgstr "" + +#: ./doc/common/tables/cinder-quota.xml:23(td) ./doc/common/tables/nova-policy.xml:35(td) +msgid "(IntOpt) number of seconds between subsequent usage refreshes" +msgstr "" + +#: ./doc/common/tables/cinder-quota.xml:26(td) +msgid "quota_driver = cinder.quota.DbQuotaDriver" +msgstr "" + +#: ./doc/common/tables/cinder-quota.xml:27(td) ./doc/common/tables/nova-quota.xml:35(td) +msgid "(StrOpt) default driver to use for quota checks" +msgstr "" + +#: ./doc/common/tables/cinder-quota.xml:30(td) +msgid "quota_gigabytes = 1000" +msgstr "" + +#: ./doc/common/tables/cinder-quota.xml:31(td) +msgid "(IntOpt) number of volume gigabytes (snapshots are also included) allowed per project" +msgstr "" + +#: ./doc/common/tables/cinder-quota.xml:34(td) +msgid "quota_snapshots = 10" +msgstr "" + +#: ./doc/common/tables/cinder-quota.xml:35(td) +msgid "(IntOpt) number of volume snapshots allowed per project" +msgstr "" + +#: ./doc/common/tables/cinder-quota.xml:38(td) +msgid "quota_volumes = 10" +msgstr "" + +#: ./doc/common/tables/cinder-quota.xml:39(td) +msgid "(IntOpt) number of volumes allowed per project" +msgstr "" + +#: ./doc/common/tables/cinder-quota.xml:42(td) ./doc/common/tables/nova-policy.xml:66(td) +msgid "reservation_expire = 86400" +msgstr "" + +#: ./doc/common/tables/cinder-quota.xml:43(td) ./doc/common/tables/nova-policy.xml:67(td) +msgid "(IntOpt) number of seconds until a reservation expires" +msgstr "" + +#: ./doc/common/tables/cinder-quota.xml:46(td) +msgid "use_default_quota_class = True" +msgstr "" + +#: ./doc/common/tables/cinder-quota.xml:47(td) +msgid "(BoolOpt) whether to use default quota class for default quota" +msgstr "" + +#: ./doc/common/tables/swift-proxy-server-filter-healthcheck.xml:7(literal) ./doc/common/tables/swift-account-server-filter-healthcheck.xml:7(literal) ./doc/common/tables/swift-container-server-filter-healthcheck.xml:7(literal) ./doc/common/tables/swift-object-server-filter-healthcheck.xml:7(literal) +msgid "[filter:healthcheck]" +msgstr "" + +#: ./doc/common/tables/swift-proxy-server-filter-healthcheck.xml:18(td) ./doc/common/tables/swift-account-server-filter-healthcheck.xml:18(td) ./doc/common/tables/swift-container-server-filter-healthcheck.xml:18(td) ./doc/common/tables/swift-object-server-filter-healthcheck.xml:18(td) +msgid "use = egg:swift#healthcheck" +msgstr "" + +#: ./doc/common/tables/swift-proxy-server-filter-healthcheck.xml:21(td) ./doc/common/tables/swift-account-server-filter-healthcheck.xml:21(td) ./doc/common/tables/swift-container-server-filter-healthcheck.xml:21(td) ./doc/common/tables/swift-object-server-filter-healthcheck.xml:21(td) +msgid "disable_path =" +msgstr "" + +#: ./doc/common/tables/nova-console.xml:8(caption) +msgid "Description of configuration options for console" +msgstr "" + +#: ./doc/common/tables/nova-console.xml:22(td) +msgid "console_public_hostname = oslo" +msgstr "" + +#: ./doc/common/tables/nova-console.xml:23(td) +msgid "(StrOpt) Publicly visible name for this console host" +msgstr "" + +#: ./doc/common/tables/nova-console.xml:26(td) +msgid "console_token_ttl = 600" +msgstr "" + +#: ./doc/common/tables/nova-console.xml:27(td) +msgid "(IntOpt) How many seconds before deleting tokens" +msgstr "" + +#: ./doc/common/tables/nova-console.xml:30(td) +msgid "consoleauth_manager = nova.consoleauth.manager.ConsoleAuthManager" +msgstr "" + +#: ./doc/common/tables/nova-console.xml:31(td) +msgid "(StrOpt) Manager for console auth" +msgstr "" + +#: ./doc/common/tables/swift-swift-bench-bench.xml:7(literal) +msgid "[bench]" +msgstr "" + +#: ./doc/common/tables/swift-swift-bench-bench.xml:7(literal) +msgid "swift-bench.conf-sample" +msgstr "" + +#: ./doc/common/tables/swift-swift-bench-bench.xml:18(td) +msgid "auth = http://localhost:8080/auth/v1.0" +msgstr "" + +#: ./doc/common/tables/swift-swift-bench-bench.xml:18(td) +msgid "Swift storage accounts and auth tokens will begin with this prefix." +msgstr "" + +#: ./doc/common/tables/swift-swift-bench-bench.xml:21(td) +msgid "user = test:tester" +msgstr "" + +#: ./doc/common/tables/swift-swift-bench-bench.xml:24(td) +msgid "key = testing" +msgstr "" + +#: ./doc/common/tables/swift-swift-bench-bench.xml:27(td) +msgid "auth_version = 1.0" +msgstr "" + +#: ./doc/common/tables/swift-swift-bench-bench.xml:27(td) ./doc/common/tables/swift-dispersion-dispersion.xml:36(td) +msgid "Indicates which version of auth" +msgstr "" + +#: ./doc/common/tables/swift-swift-bench-bench.xml:30(td) +msgid "log-level = INFO" +msgstr "" + +#: ./doc/common/tables/swift-swift-bench-bench.xml:33(td) ./doc/common/tables/neutron-ml2_ncs.xml:19(td) +msgid "timeout = 10" +msgstr "" + +#: ./doc/common/tables/swift-swift-bench-bench.xml:33(td) +msgid "Timeout value sent to rsync --timeout and --contimeout options" +msgstr "" + +#: ./doc/common/tables/swift-swift-bench-bench.xml:36(td) +msgid "put_concurrency = 10" +msgstr "" + +#: ./doc/common/tables/swift-swift-bench-bench.xml:39(td) +msgid "get_concurrency = 10" +msgstr "" + +#: ./doc/common/tables/swift-swift-bench-bench.xml:42(td) +msgid "del_concurrency = 10" +msgstr "" + +#: ./doc/common/tables/swift-swift-bench-bench.xml:45(td) +msgid "concurrency =" +msgstr "" + +#: ./doc/common/tables/swift-swift-bench-bench.xml:48(td) +msgid "object_sources =" +msgstr "" + +#: ./doc/common/tables/swift-swift-bench-bench.xml:51(td) +msgid "lower_object_size = 10" +msgstr "" + +#: ./doc/common/tables/swift-swift-bench-bench.xml:54(td) +msgid "upper_object_size = 10" +msgstr "" + +#: ./doc/common/tables/swift-swift-bench-bench.xml:57(td) +msgid "object_size = 1" +msgstr "" + +#: ./doc/common/tables/swift-swift-bench-bench.xml:60(td) +msgid "num_objects = 1000" +msgstr "" + +#: ./doc/common/tables/swift-swift-bench-bench.xml:63(td) +msgid "num_gets = 10000" +msgstr "" + +#: ./doc/common/tables/swift-swift-bench-bench.xml:66(td) +msgid "num_containers = 20" +msgstr "" + +#: ./doc/common/tables/swift-swift-bench-bench.xml:69(td) +msgid "container_name = (randomly-chosen uuid4)" +msgstr "" + +#: ./doc/common/tables/swift-swift-bench-bench.xml:72(td) +msgid "delete = yes" +msgstr "" + +#: ./doc/common/tables/swift-swift-bench-bench.xml:75(td) +msgid "use_proxy = yes" +msgstr "" + +#: ./doc/common/tables/swift-swift-bench-bench.xml:78(td) +msgid "use_proxy = no, this setting is required and used as the X-Storage-Url when" +msgstr "" + +#: ./doc/common/tables/swift-swift-bench-bench.xml:81(td) +msgid "url =" +msgstr "" + +#: ./doc/common/tables/swift-swift-bench-bench.xml:84(td) +msgid "account =" +msgstr "" + +#: ./doc/common/tables/swift-swift-bench-bench.xml:84(td) +msgid "has generated an error (timeout, not yet found, etc.)" +msgstr "" + +#: ./doc/common/tables/swift-swift-bench-bench.xml:87(td) +msgid "use_proxy = no." +msgstr "" + +#: ./doc/common/tables/swift-swift-bench-bench.xml:90(td) +msgid "devices = sdb1" +msgstr "" + +#: ./doc/common/tables/nova-common.xml:22(td) +msgid "bindir = /usr/local/bin" +msgstr "" + +#: ./doc/common/tables/nova-common.xml:23(td) +msgid "(StrOpt) Directory where nova binaries are installed" +msgstr "" + +#: ./doc/common/tables/nova-common.xml:26(td) +msgid "compute_topic = compute" +msgstr "" + +#: ./doc/common/tables/nova-common.xml:27(td) +msgid "(StrOpt) the topic compute nodes listen on" +msgstr "" + +#: ./doc/common/tables/nova-common.xml:30(td) +msgid "console_topic = console" +msgstr "" + +#: ./doc/common/tables/nova-common.xml:31(td) +msgid "(StrOpt) the topic console proxy nodes listen on" +msgstr "" + +#: ./doc/common/tables/nova-common.xml:34(td) +msgid "consoleauth_topic = consoleauth" +msgstr "" + +#: ./doc/common/tables/nova-common.xml:35(td) +msgid "(StrOpt) the topic console auth proxy nodes listen on" +msgstr "" + +#: ./doc/common/tables/nova-common.xml:42(td) ./doc/common/tables/cinder-common.xml:66(td) +msgid "host = oslo" +msgstr "" + +#: ./doc/common/tables/nova-common.xml:43(td) +msgid "(StrOpt) Name of this node. This can be an opaque identifier. It is not necessarily a hostname, FQDN, or IP address. However, the node name must be valid within an AMQP key, and if using ZeroMQ, a valid hostname, FQDN, or IP address" +msgstr "" + +#: ./doc/common/tables/nova-common.xml:47(td) ./doc/common/tables/glance-common.xml:71(td) +msgid "(StrOpt) Directory to use for lock files." +msgstr "" + +#: ./doc/common/tables/nova-common.xml:50(td) +msgid "memcached_servers = None" +msgstr "" + +#: ./doc/common/tables/nova-common.xml:51(td) +msgid "(ListOpt) Memcached servers or None for in process cache." +msgstr "" + +#: ./doc/common/tables/nova-common.xml:54(td) ./doc/common/tables/cinder-common.xml:126(td) +msgid "my_ip = 10.0.0.1" +msgstr "" + +#: ./doc/common/tables/nova-common.xml:55(td) ./doc/common/tables/cinder-common.xml:127(td) +msgid "(StrOpt) ip address of this host" +msgstr "" + +#: ./doc/common/tables/nova-common.xml:58(td) ./doc/common/tables/cinder-rpc.xml:74(td) ./doc/common/tables/neutron-notifier.xml:27(td) +msgid "notification_driver = []" +msgstr "" + +#: ./doc/common/tables/nova-common.xml:59(td) ./doc/common/tables/cinder-rpc.xml:75(td) ./doc/common/tables/neutron-notifier.xml:28(td) +msgid "(MultiStrOpt) Driver or drivers to handle sending notifications" +msgstr "" + +#: ./doc/common/tables/nova-common.xml:62(td) ./doc/common/tables/cinder-rpc.xml:78(td) ./doc/common/tables/neutron-notifier.xml:31(td) +msgid "notification_topics = notifications" +msgstr "" + +#: ./doc/common/tables/nova-common.xml:63(td) ./doc/common/tables/cinder-rpc.xml:79(td) +msgid "(ListOpt) AMQP topic used for OpenStack notifications" +msgstr "" + +#: ./doc/common/tables/nova-common.xml:66(td) +msgid "notify_api_faults = False" +msgstr "" + +#: ./doc/common/tables/nova-common.xml:67(td) +msgid "(BoolOpt) If set, send api.fault notifications on caught exceptions in the API service." +msgstr "" + +#: ./doc/common/tables/nova-common.xml:70(td) +msgid "notify_on_state_change = None" +msgstr "" + +#: ./doc/common/tables/nova-common.xml:71(td) +msgid "(StrOpt) If set, send compute.instance.update notifications on instance state changes. Valid values are None for no notifications, \"vm_state\" for notifications on VM state changes, or \"vm_and_task_state\" for notifications on VM and task state changes." +msgstr "" + +#: ./doc/common/tables/nova-common.xml:74(td) ./doc/common/tables/cinder-common.xml:154(td) +msgid "pybasedir = /usr/lib/python/site-packages" +msgstr "" + +#: ./doc/common/tables/nova-common.xml:75(td) +msgid "(StrOpt) Directory where the nova python module is installed" +msgstr "" + +#: ./doc/common/tables/nova-common.xml:78(td) ./doc/common/tables/cinder-common.xml:158(td) +msgid "report_interval = 10" +msgstr "" + +#: ./doc/common/tables/nova-common.xml:79(td) ./doc/common/tables/cinder-common.xml:159(td) +msgid "(IntOpt) seconds between nodes reporting state to datastore" +msgstr "" + +#: ./doc/common/tables/nova-common.xml:82(td) +msgid "rootwrap_config = /etc/nova/rootwrap.conf" +msgstr "" + +#: ./doc/common/tables/nova-common.xml:83(td) ./doc/common/tables/cinder-common.xml:171(td) +msgid "(StrOpt) Path to the rootwrap configuration file to use for running commands as root" +msgstr "" + +#: ./doc/common/tables/nova-common.xml:86(td) ./doc/common/tables/cinder-common.xml:178(td) +msgid "service_down_time = 60" +msgstr "" + +#: ./doc/common/tables/nova-common.xml:87(td) ./doc/common/tables/cinder-common.xml:179(td) +msgid "(IntOpt) maximum time since last check-in for up service" +msgstr "" + +#: ./doc/common/tables/nova-common.xml:90(td) ./doc/common/tables/cinder-common.xml:202(td) +msgid "state_path = $pybasedir" +msgstr "" + +#: ./doc/common/tables/nova-common.xml:91(td) +msgid "(StrOpt) Top-level directory for maintaining nova's state" +msgstr "" + +#: ./doc/common/tables/nova-common.xml:94(td) +msgid "tempdir = None" +msgstr "" + +#: ./doc/common/tables/nova-common.xml:95(td) +msgid "(StrOpt) Explicitly specify the temporary working directory" +msgstr "" + +#: ./doc/common/tables/swift-object-server-object-updater.xml:7(literal) +msgid "[object-updater]" +msgstr "" + +#: ./doc/common/tables/swift-object-server-object-updater.xml:18(td) +msgid "log_name = object-updater" +msgstr "" + +#: ./doc/common/tables/swift-object-server-object-updater.xml:33(td) ./doc/common/tables/swift-object-server-object-replicator.xml:39(td) ./doc/common/tables/swift-object-expirer-object-expirer.xml:27(td) +msgid "concurrency = 1" +msgstr "" + +#: ./doc/common/tables/glance-zmq.xml:8(caption) +msgid "Description of configuration options for zmq" +msgstr "" + +#: ./doc/common/tables/glance-zmq.xml:22(td) ./doc/common/tables/cinder-rpc.xml:174(td) ./doc/common/tables/neutron-rpc.xml:59(td) ./doc/common/tables/nova-rpc.xml:46(td) +msgid "rpc_cast_timeout = 30" +msgstr "" + +#: ./doc/common/tables/glance-zmq.xml:23(td) ./doc/common/tables/cinder-rpc.xml:175(td) ./doc/common/tables/neutron-rpc.xml:60(td) ./doc/common/tables/nova-rpc.xml:47(td) +msgid "(IntOpt) Seconds to wait before a cast expires (TTL). Only supported by impl_zmq." +msgstr "" + +#: ./doc/common/tables/glance-zmq.xml:26(td) ./doc/common/tables/cinder-rpc.xml:190(td) ./doc/common/tables/nova-zeromq.xml:22(td) ./doc/common/tables/neutron-zeromq.xml:19(td) +msgid "rpc_zmq_bind_address = *" +msgstr "" + +#: ./doc/common/tables/glance-zmq.xml:27(td) ./doc/common/tables/cinder-rpc.xml:191(td) ./doc/common/tables/nova-zeromq.xml:23(td) ./doc/common/tables/neutron-zeromq.xml:20(td) +msgid "(StrOpt) ZeroMQ bind address. Should be a wildcard (*), an ethernet interface, or IP. The \"host\" option should point or resolve to this address." +msgstr "" + +#: ./doc/common/tables/glance-zmq.xml:30(td) ./doc/common/tables/cinder-rpc.xml:194(td) ./doc/common/tables/nova-zeromq.xml:26(td) ./doc/common/tables/neutron-zeromq.xml:23(td) +msgid "rpc_zmq_contexts = 1" +msgstr "" + +#: ./doc/common/tables/glance-zmq.xml:31(td) ./doc/common/tables/cinder-rpc.xml:195(td) ./doc/common/tables/nova-zeromq.xml:27(td) ./doc/common/tables/neutron-zeromq.xml:24(td) +msgid "(IntOpt) Number of ZeroMQ contexts, defaults to 1" +msgstr "" + +#: ./doc/common/tables/glance-zmq.xml:34(td) ./doc/common/tables/cinder-rpc.xml:198(td) ./doc/common/tables/nova-zeromq.xml:30(td) +msgid "rpc_zmq_host = oslo" +msgstr "" + +#: ./doc/common/tables/glance-zmq.xml:35(td) ./doc/common/tables/cinder-rpc.xml:199(td) ./doc/common/tables/nova-zeromq.xml:31(td) ./doc/common/tables/neutron-zeromq.xml:28(td) +msgid "(StrOpt) Name of this node. Must be a valid hostname, FQDN, or IP address. Must match \"host\" option, if running Nova." +msgstr "" + +#: ./doc/common/tables/glance-zmq.xml:38(td) ./doc/common/tables/cinder-rpc.xml:202(td) ./doc/common/tables/nova-zeromq.xml:34(td) ./doc/common/tables/neutron-zeromq.xml:31(td) +msgid "rpc_zmq_ipc_dir = /var/run/openstack" +msgstr "" + +#: ./doc/common/tables/glance-zmq.xml:39(td) ./doc/common/tables/cinder-rpc.xml:203(td) ./doc/common/tables/nova-zeromq.xml:35(td) ./doc/common/tables/neutron-zeromq.xml:32(td) +msgid "(StrOpt) Directory for holding IPC sockets" +msgstr "" + +#: ./doc/common/tables/glance-zmq.xml:42(td) +msgid "rpc_zmq_matchmaker = oslo.messaging._drivers.matchmaker.MatchMakerLocalhost" +msgstr "" + +#: ./doc/common/tables/glance-zmq.xml:43(td) ./doc/common/tables/cinder-rpc.xml:207(td) ./doc/common/tables/nova-zeromq.xml:39(td) ./doc/common/tables/neutron-zeromq.xml:36(td) +msgid "(StrOpt) MatchMaker driver" +msgstr "" + +#: ./doc/common/tables/glance-zmq.xml:46(td) ./doc/common/tables/cinder-rpc.xml:210(td) ./doc/common/tables/nova-zeromq.xml:42(td) ./doc/common/tables/neutron-zeromq.xml:39(td) +msgid "rpc_zmq_port = 9501" +msgstr "" + +#: ./doc/common/tables/glance-zmq.xml:47(td) ./doc/common/tables/cinder-rpc.xml:211(td) ./doc/common/tables/nova-zeromq.xml:43(td) ./doc/common/tables/neutron-zeromq.xml:40(td) +msgid "(IntOpt) ZeroMQ receiver listening port" +msgstr "" + +#: ./doc/common/tables/glance-zmq.xml:50(td) ./doc/common/tables/cinder-rpc.xml:214(td) ./doc/common/tables/nova-zeromq.xml:46(td) ./doc/common/tables/neutron-zeromq.xml:43(td) +msgid "rpc_zmq_topic_backlog = None" +msgstr "" + +#: ./doc/common/tables/glance-zmq.xml:51(td) ./doc/common/tables/cinder-rpc.xml:215(td) ./doc/common/tables/nova-zeromq.xml:47(td) ./doc/common/tables/neutron-zeromq.xml:44(td) +msgid "(IntOpt) Maximum number of ingress messages to locally buffer per topic. Default is unlimited." +msgstr "" + +#: ./doc/common/tables/swift-proxy-server-filter-account-quotas.xml:7(literal) +msgid "[filter:account-quotas]" +msgstr "" + +#: ./doc/common/tables/swift-proxy-server-filter-account-quotas.xml:18(td) +msgid "use = egg:swift#account_quotas" +msgstr "" + +#: ./doc/common/tables/swift-proxy-server-app-proxy-server.xml:7(literal) ./doc/common/tables/swift-object-expirer-app-proxy-server.xml:7(literal) +msgid "[app:proxy-server]" +msgstr "" + +#: ./doc/common/tables/swift-proxy-server-app-proxy-server.xml:18(td) ./doc/common/tables/swift-object-expirer-app-proxy-server.xml:18(td) +msgid "use = egg:swift#proxy" +msgstr "" + +#: ./doc/common/tables/swift-proxy-server-app-proxy-server.xml:21(td) +msgid "set log_name = proxy-server" +msgstr "" + +#: ./doc/common/tables/swift-proxy-server-app-proxy-server.xml:33(td) +msgid "log_handoffs = true" +msgstr "" + +#: ./doc/common/tables/swift-proxy-server-app-proxy-server.xml:36(td) +msgid "recheck_account_existence = 60" +msgstr "" + +#: ./doc/common/tables/swift-proxy-server-app-proxy-server.xml:36(td) +msgid "Cache timeout in seconds to send memcached for account existence" +msgstr "" + +#: ./doc/common/tables/swift-proxy-server-app-proxy-server.xml:39(td) +msgid "recheck_container_existence = 60" +msgstr "" + +#: ./doc/common/tables/swift-proxy-server-app-proxy-server.xml:39(td) +msgid "Cache timeout in seconds to send memcached for container existence" +msgstr "" + +#: ./doc/common/tables/swift-proxy-server-app-proxy-server.xml:42(td) +msgid "object_chunk_size = 8192" +msgstr "" + +#: ./doc/common/tables/swift-proxy-server-app-proxy-server.xml:42(td) +msgid "Chunk size to read from object servers" +msgstr "" + +#: ./doc/common/tables/swift-proxy-server-app-proxy-server.xml:45(td) +msgid "client_chunk_size = 8192" +msgstr "" + +#: ./doc/common/tables/swift-proxy-server-app-proxy-server.xml:45(td) +msgid "Chunk size to read from clients" +msgstr "" + +#: ./doc/common/tables/swift-proxy-server-app-proxy-server.xml:54(td) ./doc/common/tables/swift-account-server-account-replicator.xml:45(td) +msgid "error_suppression_interval = 60" +msgstr "" + +#: ./doc/common/tables/swift-proxy-server-app-proxy-server.xml:54(td) ./doc/common/tables/swift-account-server-account-replicator.xml:45(td) +msgid "Time in seconds that must elapse since the last error for a node to be considered no longer error limited" +msgstr "" + +#: ./doc/common/tables/swift-proxy-server-app-proxy-server.xml:57(td) ./doc/common/tables/swift-account-server-account-replicator.xml:48(td) +msgid "error_suppression_limit = 10" +msgstr "" + +#: ./doc/common/tables/swift-proxy-server-app-proxy-server.xml:57(td) ./doc/common/tables/swift-account-server-account-replicator.xml:48(td) +msgid "Error count to consider a node error limited" +msgstr "" + +#: ./doc/common/tables/swift-proxy-server-app-proxy-server.xml:60(td) +msgid "allow_account_management = false" +msgstr "" + +#: ./doc/common/tables/swift-proxy-server-app-proxy-server.xml:60(td) +msgid "Whether account PUTs and DELETEs are even callable" +msgstr "" + +#: ./doc/common/tables/swift-proxy-server-app-proxy-server.xml:63(td) +msgid "object_post_as_copy = true" +msgstr "" + +#: ./doc/common/tables/swift-proxy-server-app-proxy-server.xml:63(td) +msgid "Set object_post_as_copy = false to turn on fast posts where only the metadata changes are stored anew and the original data file is kept in place. This makes for quicker posts; but since the container metadata isn't updated in this mode, features like container sync won't be able to sync posts." +msgstr "" + +#: ./doc/common/tables/swift-proxy-server-app-proxy-server.xml:66(td) +msgid "account_autocreate = false" +msgstr "" + +#: ./doc/common/tables/swift-proxy-server-app-proxy-server.xml:66(td) +msgid "If set to 'true' authorized accounts that do not yet exist within the Swift cluster will be automatically created." +msgstr "" + +#: ./doc/common/tables/swift-proxy-server-app-proxy-server.xml:69(td) +msgid "max_containers_per_account = 0" +msgstr "" + +#: ./doc/common/tables/swift-proxy-server-app-proxy-server.xml:69(td) +msgid "If set to a positive value, trying to create a container when the account already has at least this maximum containers will result in a 403 Forbidden. Note: This is a soft limit, meaning a user might exceed the cap for recheck_account_existence before the 403s kick in." +msgstr "" + +#: ./doc/common/tables/swift-proxy-server-app-proxy-server.xml:72(td) +msgid "max_containers_whitelist =" +msgstr "" + +#: ./doc/common/tables/swift-proxy-server-app-proxy-server.xml:72(td) +msgid "is a comma separated list of account names that ignore the max_containers_per_account cap." +msgstr "" + +#: ./doc/common/tables/swift-proxy-server-app-proxy-server.xml:75(td) +msgid "deny_host_headers =" +msgstr "" + +#: ./doc/common/tables/swift-proxy-server-app-proxy-server.xml:78(td) ./doc/common/tables/swift-account-server-app-account-server.xml:36(td) ./doc/common/tables/swift-container-server-app-container-server.xml:45(td) ./doc/common/tables/swift-object-server-app-object-server.xml:66(td) ./doc/common/tables/swift-object-expirer-object-expirer.xml:21(td) +msgid "auto_create_account_prefix = ." +msgstr "" + +#: ./doc/common/tables/swift-proxy-server-app-proxy-server.xml:78(td) ./doc/common/tables/swift-account-server-app-account-server.xml:36(td) ./doc/common/tables/swift-container-server-app-container-server.xml:45(td) ./doc/common/tables/swift-object-server-app-object-server.xml:66(td) ./doc/common/tables/swift-object-expirer-object-expirer.xml:21(td) +msgid "Prefix to use when automatically creating accounts" +msgstr "" + +#: ./doc/common/tables/swift-proxy-server-app-proxy-server.xml:81(td) +msgid "put_queue_depth = 10" +msgstr "" + +#: ./doc/common/tables/swift-proxy-server-app-proxy-server.xml:84(td) +msgid "rate_limit_after_segment = 10" +msgstr "" + +#: ./doc/common/tables/swift-proxy-server-app-proxy-server.xml:84(td) +msgid "Rate limit the download of large object segments after this segment is downloaded." +msgstr "" + +#: ./doc/common/tables/swift-proxy-server-app-proxy-server.xml:87(td) +msgid "rate_limit_segments_per_sec = 1" +msgstr "" + +#: ./doc/common/tables/swift-proxy-server-app-proxy-server.xml:87(td) +msgid "Rate limit large object downloads at this rate. contact for a normal request. You can use '* replicas' at the end to have it use the number given times the number of replicas for the ring being used for the request. paste.deploy to use for auth. To use tempauth set to: `egg:swift#tempauth` each request" +msgstr "" + +#: ./doc/common/tables/swift-proxy-server-app-proxy-server.xml:90(td) +msgid "sorting_method = shuffle" +msgstr "" + +#: ./doc/common/tables/swift-proxy-server-app-proxy-server.xml:93(td) +msgid "timing_expiry = 300" +msgstr "" + +#: ./doc/common/tables/swift-proxy-server-app-proxy-server.xml:96(td) +msgid "allow_static_large_object = true" +msgstr "" + +#: ./doc/common/tables/swift-proxy-server-app-proxy-server.xml:99(td) +msgid "max_large_object_get_time = 86400" +msgstr "" + +#: ./doc/common/tables/swift-proxy-server-app-proxy-server.xml:102(td) +msgid "request_node_count = 2 * replicas" +msgstr "" + +#: ./doc/common/tables/swift-proxy-server-app-proxy-server.xml:102(td) +msgid "* replicas Set to the number of nodes to contact for a normal request. You can use '* replicas' at the end to have it use the number given times the number of replicas for the ring being used for the request. conf file for values will only be shown to the list of swift_owners. The exact default definition of a swift_owner is headers> up to the auth system in use, but usually indicates administrative responsibilities. paste.deploy to use for auth. To use tempauth set to: `egg:swift#tempauth` each request" +msgstr "" + +#: ./doc/common/tables/swift-proxy-server-app-proxy-server.xml:105(td) +msgid "read_affinity = r1z1=100, r1z2=200, r2=300" +msgstr "" + +#: ./doc/common/tables/swift-proxy-server-app-proxy-server.xml:108(td) +msgid "read_affinity =" +msgstr "" + +#: ./doc/common/tables/swift-proxy-server-app-proxy-server.xml:111(td) +msgid "write_affinity = r1, r2" +msgstr "" + +#: ./doc/common/tables/swift-proxy-server-app-proxy-server.xml:114(td) +msgid "write_affinity =" +msgstr "" + +#: ./doc/common/tables/swift-proxy-server-app-proxy-server.xml:117(td) +msgid "write_affinity_node_count = 2 * replicas" +msgstr "" + +#: ./doc/common/tables/swift-proxy-server-app-proxy-server.xml:120(td) +msgid "swift_owner_headers = x-container-read, x-container-write, x-container-sync-key, x-container-sync-to, x-account-meta-temp-url-key, x-account-meta-temp-url-key-2" +msgstr "" + +#: ./doc/common/tables/swift-proxy-server-app-proxy-server.xml:120(td) +msgid "the sample These are the headers whose conf file for values will only be shown to the list of swift_owners. The exact default definition of a swift_owner is headers> up to the auth system in use, but usually indicates administrative responsibilities. paste.deploy to use for auth. To use tempauth set to: `egg:swift#tempauth` each request" +msgstr "" + +#: ./doc/common/tables/nova-keymgr.xml:8(caption) ./doc/common/tables/cinder-keymgr.xml:8(caption) +msgid "Description of configuration options for keymgr" +msgstr "" + +#: ./doc/common/tables/nova-keymgr.xml:19(th) ./doc/common/tables/cinder-keymgr.xml:19(th) +msgid "[keymgr]" +msgstr "" + +#: ./doc/common/tables/nova-keymgr.xml:22(td) +msgid "api_class = nova.keymgr.conf_key_mgr.ConfKeyManager" +msgstr "" + +#: ./doc/common/tables/nova-keymgr.xml:23(td) ./doc/common/tables/cinder-keymgr.xml:23(td) +msgid "(StrOpt) The full class name of the key manager API class" +msgstr "" + +#: ./doc/common/tables/nova-keymgr.xml:26(td) ./doc/common/tables/cinder-keymgr.xml:26(td) +msgid "fixed_key = None" +msgstr "" + +#: ./doc/common/tables/nova-keymgr.xml:27(td) ./doc/common/tables/cinder-keymgr.xml:27(td) +msgid "(StrOpt) Fixed key returned by key manager, specified in hex" +msgstr "" + +#: ./doc/common/tables/neutron-api.xml:8(caption) ./doc/common/tables/cinder-api.xml:8(caption) ./doc/common/tables/nova-api.xml:8(caption) ./doc/common/tables/glance-api.xml:8(caption) +msgid "Description of configuration options for api" +msgstr "" + +#: ./doc/common/tables/neutron-api.xml:19(td) +msgid "allow_bulk = True" +msgstr "" + +#: ./doc/common/tables/neutron-api.xml:20(td) +msgid "(BoolOpt) Allow the usage of the bulk API" +msgstr "" + +#: ./doc/common/tables/neutron-api.xml:23(td) +msgid "allow_pagination = False" +msgstr "" + +#: ./doc/common/tables/neutron-api.xml:24(td) +msgid "(BoolOpt) Allow the usage of the pagination" +msgstr "" + +#: ./doc/common/tables/neutron-api.xml:27(td) +msgid "allow_sorting = False" +msgstr "" + +#: ./doc/common/tables/neutron-api.xml:28(td) +msgid "(BoolOpt) Allow the usage of the sorting" +msgstr "" + +#: ./doc/common/tables/neutron-api.xml:31(td) +msgid "api_extensions_path =" +msgstr "" + +#: ./doc/common/tables/neutron-api.xml:32(td) +msgid "(StrOpt) The path for API extensions" +msgstr "" + +#: ./doc/common/tables/neutron-api.xml:35(td) ./doc/common/tables/cinder-api.xml:22(td) ./doc/common/tables/nova-wsgi.xml:22(td) +msgid "api_paste_config = api-paste.ini" +msgstr "" + +#: ./doc/common/tables/neutron-api.xml:36(td) +msgid "(StrOpt) The API paste config file to use" +msgstr "" + +#: ./doc/common/tables/neutron-api.xml:39(td) +msgid "pagination_max_limit = -1" +msgstr "" + +#: ./doc/common/tables/neutron-api.xml:40(td) +msgid "(StrOpt) The maximum number of items returned in a single response, value was 'infinite' or negative integer means no limit" +msgstr "" + +#: ./doc/common/tables/neutron-api.xml:43(td) ./doc/common/tables/nova-periodic.xml:30(td) ./doc/common/tables/cinder-common.xml:174(td) +msgid "run_external_periodic_tasks = True" +msgstr "" + +#: ./doc/common/tables/neutron-api.xml:44(td) ./doc/common/tables/nova-periodic.xml:31(td) ./doc/common/tables/cinder-common.xml:175(td) +msgid "(BoolOpt) Some periodic tasks can be run in a separate process. Should we run them here?" +msgstr "" + +#: ./doc/common/tables/neutron-api.xml:47(td) +msgid "service_plugins =" +msgstr "" + +#: ./doc/common/tables/neutron-api.xml:48(td) +msgid "(ListOpt) The service plugins Neutron will use" +msgstr "" + +#: ./doc/common/tables/neutron-api.xml:51(td) +msgid "service_provider = []" +msgstr "" + +#: ./doc/common/tables/neutron-api.xml:52(td) +msgid "(MultiStrOpt) Defines providers for advanced services using the format: <service_type>:<name>:<driver>[:default]" +msgstr "" + +#: ./doc/common/tables/nova-testing.xml:8(caption) ./doc/common/tables/glance-testing.xml:8(caption) ./doc/common/tables/neutron-testing.xml:8(caption) +msgid "Description of configuration options for testing" +msgstr "" + +#: ./doc/common/tables/nova-testing.xml:22(td) ./doc/common/tables/cinder-rpc.xml:22(td) +msgid "allowed_rpc_exception_modules = nova.exception, cinder.exception, exceptions" +msgstr "" + +#: ./doc/common/tables/nova-testing.xml:26(td) ./doc/common/tables/cinder-api.xml:30(td) ./doc/common/tables/glance-wsgi.xml:22(td) ./doc/common/tables/neutron-testing.xml:19(td) +msgid "backdoor_port = None" +msgstr "" + +#: ./doc/common/tables/nova-testing.xml:27(td) +msgid "(StrOpt) Enable eventlet backdoor. Acceptable values are 0, <port> and <start>:<end>, where 0 results in listening on a random tcp port number, <port> results in listening on the specified port number and not enabling backdoorif it is in use and <start>:<end> results in listening on the smallest unused port number within the specified range of port numbers. The chosen port is displayed in the service's log file." +msgstr "" + +#: ./doc/common/tables/nova-testing.xml:30(td) +msgid "fake_call = False" +msgstr "" + +#: ./doc/common/tables/nova-testing.xml:31(td) +msgid "(BoolOpt) If True, skip using the queue and make local calls" +msgstr "" + +#: ./doc/common/tables/nova-testing.xml:34(td) +msgid "fake_network = False" +msgstr "" + +#: ./doc/common/tables/nova-testing.xml:35(td) +msgid "(BoolOpt) If passed, use fake network devices and addresses" +msgstr "" + +#: ./doc/common/tables/nova-testing.xml:38(td) ./doc/common/tables/cinder-rpc.xml:42(td) ./doc/common/tables/glance-rabbitmq.xml:22(td) ./doc/common/tables/neutron-testing.xml:23(td) +msgid "fake_rabbit = False" +msgstr "" + +#: ./doc/common/tables/nova-testing.xml:39(td) ./doc/common/tables/cinder-rpc.xml:43(td) ./doc/common/tables/glance-rabbitmq.xml:23(td) ./doc/common/tables/neutron-testing.xml:24(td) +msgid "(BoolOpt) If passed, use a fake RabbitMQ provider" +msgstr "" + +#: ./doc/common/tables/nova-testing.xml:42(td) ./doc/common/tables/cinder-common.xml:118(td) +msgid "monkey_patch = False" +msgstr "" + +#: ./doc/common/tables/nova-testing.xml:43(td) +msgid "(BoolOpt) Whether to log monkey patching" +msgstr "" + +#: ./doc/common/tables/nova-testing.xml:46(td) +msgid "monkey_patch_modules = nova.api.ec2.cloud:nova.notifications.notify_decorator, nova.compute.api:nova.notifications.notify_decorator" +msgstr "" + +#: ./doc/common/tables/nova-testing.xml:47(td) ./doc/common/tables/cinder-common.xml:123(td) +msgid "(ListOpt) List of modules/decorators to monkey patch" +msgstr "" + +#: ./doc/common/tables/cinder-backups.xml:8(caption) +msgid "Description of configuration options for backups" +msgstr "" + +#: ./doc/common/tables/cinder-backups.xml:22(td) +msgid "backup_api_class = cinder.backup.api.API" +msgstr "" + +#: ./doc/common/tables/cinder-backups.xml:23(td) +msgid "(StrOpt) The full class name of the volume backup API class" +msgstr "" + +#: ./doc/common/tables/cinder-backups.xml:26(td) +msgid "backup_compression_algorithm = zlib" +msgstr "" + +#: ./doc/common/tables/cinder-backups.xml:27(td) +msgid "(StrOpt) Compression algorithm (None to disable)" +msgstr "" + +#: ./doc/common/tables/cinder-backups.xml:30(td) +msgid "backup_driver = cinder.backup.drivers.swift" +msgstr "" + +#: ./doc/common/tables/cinder-backups.xml:31(td) +msgid "(StrOpt) Driver to use for backups." +msgstr "" + +#: ./doc/common/tables/cinder-backups.xml:34(td) +msgid "backup_manager = cinder.backup.manager.BackupManager" +msgstr "" + +#: ./doc/common/tables/cinder-backups.xml:35(td) +msgid "(StrOpt) full class name for the Manager for volume backup" +msgstr "" + +#: ./doc/common/tables/cinder-backups.xml:38(td) +msgid "backup_name_template = backup-%s" +msgstr "" + +#: ./doc/common/tables/cinder-backups.xml:39(td) +msgid "(StrOpt) Template string to be used to generate backup names" +msgstr "" + +#: ./doc/common/tables/cinder-backups.xml:42(td) +msgid "backup_topic = cinder-backup" +msgstr "" + +#: ./doc/common/tables/cinder-backups.xml:43(td) +msgid "(StrOpt) the topic volume backup nodes listen on" +msgstr "" + +#: ./doc/common/tables/cinder-backups.xml:46(td) ./doc/common/tables/nova-api.xml:82(td) +msgid "snapshot_name_template = snapshot-%s" +msgstr "" + +#: ./doc/common/tables/cinder-backups.xml:47(td) ./doc/common/tables/nova-api.xml:83(td) +msgid "(StrOpt) Template string to be used to generate snapshot names" +msgstr "" + +#: ./doc/common/tables/cinder-backups.xml:50(td) +msgid "snapshot_same_host = True" +msgstr "" + +#: ./doc/common/tables/cinder-backups.xml:51(td) +msgid "(BoolOpt) Create volume from snapshot at the host where snapshot resides" +msgstr "" + +#: ./doc/common/tables/swift-container-server-pipeline-main.xml:7(literal) ./doc/common/tables/swift-object-server-pipeline-main.xml:7(literal) ./doc/common/tables/swift-object-expirer-pipeline-main.xml:7(literal) ./doc/common/tables/swift-account-server-pipeline-main.xml:7(literal) ./doc/common/tables/swift-proxy-server-pipeline-main.xml:7(literal) +msgid "[pipeline:main]" +msgstr "" + +#: ./doc/common/tables/swift-container-server-pipeline-main.xml:18(td) +msgid "pipeline = healthcheck recon container-server" +msgstr "" + +#: ./doc/common/tables/swift-rsyncd-object.xml:7(literal) +msgid "[object]" +msgstr "" + +#: ./doc/common/tables/swift-rsyncd-object.xml:7(literal) ./doc/common/tables/swift-rsyncd-account.xml:7(literal) ./doc/common/tables/swift-rsyncd-container.xml:7(literal) +msgid "rsyncd.conf-sample" +msgstr "" + +#: ./doc/common/tables/swift-rsyncd-object.xml:18(td) +msgid "max connections = 8" +msgstr "" + +#: ./doc/common/tables/swift-rsyncd-object.xml:21(td) ./doc/common/tables/swift-rsyncd-account.xml:21(td) ./doc/common/tables/swift-rsyncd-container.xml:21(td) +msgid "path = /srv/node" +msgstr "" + +#: ./doc/common/tables/swift-rsyncd-object.xml:24(td) ./doc/common/tables/swift-rsyncd-account.xml:24(td) ./doc/common/tables/swift-rsyncd-container.xml:24(td) +msgid "read only = false" +msgstr "" + +#: ./doc/common/tables/swift-rsyncd-object.xml:27(td) +msgid "lock file = /var/lock/object.lock" +msgstr "" + +#: ./doc/common/tables/nova-s3.xml:22(td) +msgid "buckets_path = $state_path/buckets" +msgstr "" + +#: ./doc/common/tables/nova-s3.xml:23(td) +msgid "(StrOpt) path to s3 buckets" +msgstr "" + +#: ./doc/common/tables/nova-s3.xml:26(td) +msgid "image_decryption_dir = /tmp" +msgstr "" + +#: ./doc/common/tables/nova-s3.xml:27(td) +msgid "(StrOpt) parent dir for tempdir used for image decryption" +msgstr "" + +#: ./doc/common/tables/nova-s3.xml:30(td) +msgid "s3_access_key = notchecked" +msgstr "" + +#: ./doc/common/tables/nova-s3.xml:31(td) +msgid "(StrOpt) access key to use for s3 server for images" +msgstr "" + +#: ./doc/common/tables/nova-s3.xml:34(td) +msgid "s3_affix_tenant = False" +msgstr "" + +#: ./doc/common/tables/nova-s3.xml:35(td) +msgid "(BoolOpt) whether to affix the tenant id to the access key when downloading from s3" +msgstr "" + +#: ./doc/common/tables/nova-s3.xml:38(td) +msgid "s3_host = $my_ip" +msgstr "" + +#: ./doc/common/tables/nova-s3.xml:39(td) +msgid "(StrOpt) hostname or ip for OpenStack to use when accessing the s3 api" +msgstr "" + +#: ./doc/common/tables/nova-s3.xml:42(td) +msgid "s3_listen = 0.0.0.0" +msgstr "" + +#: ./doc/common/tables/nova-s3.xml:43(td) +msgid "(StrOpt) IP address for S3 API to listen" +msgstr "" + +#: ./doc/common/tables/nova-s3.xml:46(td) +msgid "s3_listen_port = 3333" +msgstr "" + +#: ./doc/common/tables/nova-s3.xml:47(td) +msgid "(IntOpt) port for s3 api to listen" +msgstr "" + +#: ./doc/common/tables/nova-s3.xml:50(td) +msgid "s3_port = 3333" +msgstr "" + +#: ./doc/common/tables/nova-s3.xml:51(td) +msgid "(IntOpt) port used when accessing the s3 api" +msgstr "" + +#: ./doc/common/tables/nova-s3.xml:54(td) +msgid "s3_secret_key = notchecked" +msgstr "" + +#: ./doc/common/tables/nova-s3.xml:55(td) +msgid "(StrOpt) secret key to use for s3 server for images" +msgstr "" + +#: ./doc/common/tables/nova-s3.xml:58(td) +msgid "s3_use_ssl = False" +msgstr "" + +#: ./doc/common/tables/nova-s3.xml:59(td) +msgid "(BoolOpt) whether to use ssl when talking to s3" +msgstr "" + +#: ./doc/common/tables/neutron-openvswitch.xml:8(caption) +msgid "Description of configuration options for openvswitch" +msgstr "" + +#: ./doc/common/tables/nova-zookeeper.xml:8(caption) +msgid "Description of configuration options for zookeeper" +msgstr "" + +#: ./doc/common/tables/nova-zookeeper.xml:19(th) +msgid "[zookeeper]" +msgstr "" + +#: ./doc/common/tables/nova-zookeeper.xml:22(td) +msgid "address = None" +msgstr "" + +#: ./doc/common/tables/nova-zookeeper.xml:23(td) +msgid "(StrOpt) The ZooKeeper addresses for servicegroup service in the format of host1:port,host2:port,host3:port" +msgstr "" + +#: ./doc/common/tables/nova-zookeeper.xml:26(td) +msgid "recv_timeout = 4000" +msgstr "" + +#: ./doc/common/tables/nova-zookeeper.xml:27(td) +msgid "(IntOpt) recv_timeout parameter for the zk session" +msgstr "" + +#: ./doc/common/tables/nova-zookeeper.xml:30(td) +msgid "sg_prefix = /servicegroups" +msgstr "" + +#: ./doc/common/tables/nova-zookeeper.xml:31(td) +msgid "(StrOpt) The prefix used in ZooKeeper to store ephemeral nodes" +msgstr "" + +#: ./doc/common/tables/nova-zookeeper.xml:34(td) +msgid "sg_retry_interval = 5" +msgstr "" + +#: ./doc/common/tables/nova-zookeeper.xml:35(td) +msgid "(IntOpt) Number of seconds to wait until retrying to join the session" +msgstr "" + +#: ./doc/common/tables/cinder-rpc.xml:8(caption) ./doc/common/tables/glance-rpc.xml:8(caption) ./doc/common/tables/neutron-rpc.xml:8(caption) ./doc/common/tables/nova-rpc.xml:8(caption) +msgid "Description of configuration options for rpc" +msgstr "" + +#: ./doc/common/tables/cinder-rpc.xml:26(td) ./doc/common/tables/neutron-rpc.xml:19(td) ./doc/common/tables/nova-rpc.xml:22(td) +msgid "amqp_auto_delete = False" +msgstr "" + +#: ./doc/common/tables/cinder-rpc.xml:27(td) ./doc/common/tables/neutron-rpc.xml:20(td) ./doc/common/tables/nova-rpc.xml:23(td) +msgid "(BoolOpt) Auto-delete queues in amqp." +msgstr "" + +#: ./doc/common/tables/cinder-rpc.xml:30(td) ./doc/common/tables/neutron-rpc.xml:23(td) ./doc/common/tables/nova-rpc.xml:26(td) +msgid "amqp_durable_queues = False" +msgstr "" + +#: ./doc/common/tables/cinder-rpc.xml:31(td) ./doc/common/tables/neutron-rpc.xml:24(td) ./doc/common/tables/nova-rpc.xml:27(td) +msgid "(BoolOpt) Use durable queues in amqp." +msgstr "" + +#: ./doc/common/tables/cinder-rpc.xml:34(td) +msgid "amqp_rpc_single_reply_queue = False" +msgstr "" + +#: ./doc/common/tables/cinder-rpc.xml:35(td) +msgid "(BoolOpt) Enable a fast single reply queue if using AMQP based RPC like RabbitMQ or Qpid." +msgstr "" + +#: ./doc/common/tables/cinder-rpc.xml:38(td) ./doc/common/tables/nova-rpc.xml:30(td) +msgid "control_exchange = openstack" +msgstr "" + +#: ./doc/common/tables/cinder-rpc.xml:39(td) ./doc/common/tables/neutron-rpc.xml:28(td) ./doc/common/tables/nova-rpc.xml:31(td) +msgid "(StrOpt) AMQP exchange to connect to if using RabbitMQ or Qpid" +msgstr "" + +#: ./doc/common/tables/cinder-rpc.xml:62(td) ./doc/common/tables/neutron-rpc.xml:35(td) ./doc/common/tables/nova-rpc.xml:34(td) +msgid "matchmaker_heartbeat_freq = 300" +msgstr "" + +#: ./doc/common/tables/cinder-rpc.xml:63(td) ./doc/common/tables/neutron-rpc.xml:36(td) ./doc/common/tables/nova-rpc.xml:35(td) +msgid "(IntOpt) Heartbeat frequency" +msgstr "" + +#: ./doc/common/tables/cinder-rpc.xml:66(td) ./doc/common/tables/neutron-rpc.xml:39(td) ./doc/common/tables/nova-rpc.xml:38(td) +msgid "matchmaker_heartbeat_ttl = 600" +msgstr "" + +#: ./doc/common/tables/cinder-rpc.xml:67(td) ./doc/common/tables/neutron-rpc.xml:40(td) ./doc/common/tables/nova-rpc.xml:39(td) +msgid "(IntOpt) Heartbeat time-to-live." +msgstr "" + +#: ./doc/common/tables/cinder-rpc.xml:70(td) +msgid "matchmaker_ringfile = /etc/nova/matchmaker_ring.json" +msgstr "" + +#: ./doc/common/tables/cinder-rpc.xml:71(td) ./doc/common/tables/cinder-rpc.xml:226(td) ./doc/common/tables/neutron-rpc.xml:52(td) ./doc/common/tables/nova-rpc.xml:73(td) +msgid "(StrOpt) Matchmaker ring file (JSON)" +msgstr "" + +#: ./doc/common/tables/cinder-rpc.xml:82(td) ./doc/common/tables/glance-logging.xml:78(td) ./doc/common/tables/neutron-logging.xml:75(td) ./doc/common/tables/nova-logging.xml:82(td) +msgid "publish_errors = False" +msgstr "" + +#: ./doc/common/tables/cinder-rpc.xml:83(td) ./doc/common/tables/glance-logging.xml:79(td) ./doc/common/tables/neutron-logging.xml:76(td) ./doc/common/tables/nova-logging.xml:83(td) +msgid "(BoolOpt) publish error events" +msgstr "" + +#: ./doc/common/tables/cinder-rpc.xml:99(td) ./doc/common/tables/neutron-qpid.xml:32(td) ./doc/common/tables/nova-qpid.xml:35(td) +msgid "(StrOpt) Password for qpid connection" +msgstr "" + +#: ./doc/common/tables/cinder-rpc.xml:123(td) ./doc/common/tables/neutron-qpid.xml:56(td) ./doc/common/tables/nova-qpid.xml:59(td) +msgid "(StrOpt) Username for qpid connection" +msgstr "" + +#: ./doc/common/tables/cinder-rpc.xml:126(td) ./doc/common/tables/glance-rabbitmq.xml:42(td) ./doc/common/tables/neutron-rabbitmq.xml:19(td) ./doc/common/tables/nova-rabbitmq.xml:22(td) +msgid "rabbit_ha_queues = False" +msgstr "" + +#: ./doc/common/tables/cinder-rpc.xml:127(td) ./doc/common/tables/glance-rabbitmq.xml:43(td) ./doc/common/tables/neutron-rabbitmq.xml:20(td) ./doc/common/tables/nova-rabbitmq.xml:23(td) +msgid "(BoolOpt) use H/A queues in RabbitMQ (x-ha-policy: all).You need to wipe RabbitMQ database when changing this option." +msgstr "" + +#: ./doc/common/tables/cinder-rpc.xml:130(td) ./doc/common/tables/glance-rabbitmq.xml:46(td) ./doc/common/tables/neutron-rabbitmq.xml:23(td) ./doc/common/tables/nova-rabbitmq.xml:26(td) +msgid "rabbit_host = localhost" +msgstr "" + +#: ./doc/common/tables/cinder-rpc.xml:131(td) ./doc/common/tables/glance-rabbitmq.xml:47(td) ./doc/common/tables/neutron-rabbitmq.xml:24(td) ./doc/common/tables/nova-rabbitmq.xml:27(td) +msgid "(StrOpt) The RabbitMQ broker address where a single node is used" +msgstr "" + +#: ./doc/common/tables/cinder-rpc.xml:134(td) ./doc/common/tables/glance-rabbitmq.xml:50(td) ./doc/common/tables/neutron-rabbitmq.xml:27(td) ./doc/common/tables/nova-rabbitmq.xml:30(td) +msgid "rabbit_hosts = $rabbit_host:$rabbit_port" +msgstr "" + +#: ./doc/common/tables/cinder-rpc.xml:135(td) ./doc/common/tables/glance-rabbitmq.xml:51(td) ./doc/common/tables/neutron-rabbitmq.xml:28(td) ./doc/common/tables/nova-rabbitmq.xml:31(td) +msgid "(ListOpt) RabbitMQ HA cluster host:port pairs" +msgstr "" + +#: ./doc/common/tables/cinder-rpc.xml:138(td) ./doc/common/tables/glance-rabbitmq.xml:54(td) ./doc/common/tables/neutron-rabbitmq.xml:31(td) ./doc/common/tables/nova-rabbitmq.xml:34(td) +msgid "rabbit_max_retries = 0" +msgstr "" + +#: ./doc/common/tables/cinder-rpc.xml:139(td) ./doc/common/tables/glance-rabbitmq.xml:55(td) ./doc/common/tables/neutron-rabbitmq.xml:32(td) ./doc/common/tables/nova-rabbitmq.xml:35(td) +msgid "(IntOpt) maximum retries with trying to connect to RabbitMQ (the default of 0 implies an infinite retry count)" +msgstr "" + +#: ./doc/common/tables/cinder-rpc.xml:142(td) ./doc/common/tables/glance-rabbitmq.xml:58(td) ./doc/common/tables/neutron-rabbitmq.xml:35(td) ./doc/common/tables/nova-rabbitmq.xml:38(td) +msgid "rabbit_password = guest" +msgstr "" + +#: ./doc/common/tables/cinder-rpc.xml:143(td) ./doc/common/tables/glance-rabbitmq.xml:59(td) ./doc/common/tables/neutron-rabbitmq.xml:36(td) ./doc/common/tables/nova-rabbitmq.xml:39(td) +msgid "(StrOpt) the RabbitMQ password" +msgstr "" + +#: ./doc/common/tables/cinder-rpc.xml:146(td) ./doc/common/tables/glance-rabbitmq.xml:62(td) ./doc/common/tables/neutron-rabbitmq.xml:39(td) ./doc/common/tables/nova-rabbitmq.xml:42(td) +msgid "rabbit_port = 5672" +msgstr "" + +#: ./doc/common/tables/cinder-rpc.xml:147(td) ./doc/common/tables/glance-rabbitmq.xml:63(td) ./doc/common/tables/neutron-rabbitmq.xml:40(td) ./doc/common/tables/nova-rabbitmq.xml:43(td) +msgid "(IntOpt) The RabbitMQ broker port where a single node is used" +msgstr "" + +#: ./doc/common/tables/cinder-rpc.xml:150(td) ./doc/common/tables/glance-rabbitmq.xml:66(td) ./doc/common/tables/neutron-rabbitmq.xml:43(td) ./doc/common/tables/nova-rabbitmq.xml:46(td) +msgid "rabbit_retry_backoff = 2" +msgstr "" + +#: ./doc/common/tables/cinder-rpc.xml:151(td) ./doc/common/tables/glance-rabbitmq.xml:67(td) ./doc/common/tables/neutron-rabbitmq.xml:44(td) ./doc/common/tables/nova-rabbitmq.xml:47(td) +msgid "(IntOpt) how long to backoff for between retries when connecting to RabbitMQ" +msgstr "" + +#: ./doc/common/tables/cinder-rpc.xml:154(td) ./doc/common/tables/glance-rabbitmq.xml:70(td) ./doc/common/tables/neutron-rabbitmq.xml:47(td) ./doc/common/tables/nova-rabbitmq.xml:50(td) +msgid "rabbit_retry_interval = 1" +msgstr "" + +#: ./doc/common/tables/cinder-rpc.xml:155(td) ./doc/common/tables/glance-rabbitmq.xml:71(td) ./doc/common/tables/neutron-rabbitmq.xml:48(td) ./doc/common/tables/nova-rabbitmq.xml:51(td) +msgid "(IntOpt) how frequently to retry connecting with RabbitMQ" +msgstr "" + +#: ./doc/common/tables/cinder-rpc.xml:158(td) ./doc/common/tables/glance-rabbitmq.xml:74(td) ./doc/common/tables/neutron-rabbitmq.xml:51(td) ./doc/common/tables/nova-rabbitmq.xml:54(td) +msgid "rabbit_use_ssl = False" +msgstr "" + +#: ./doc/common/tables/cinder-rpc.xml:159(td) ./doc/common/tables/glance-rabbitmq.xml:75(td) ./doc/common/tables/neutron-rabbitmq.xml:52(td) ./doc/common/tables/nova-rabbitmq.xml:55(td) +msgid "(BoolOpt) connect over SSL for RabbitMQ" +msgstr "" + +#: ./doc/common/tables/cinder-rpc.xml:162(td) ./doc/common/tables/glance-rabbitmq.xml:78(td) ./doc/common/tables/neutron-rabbitmq.xml:55(td) ./doc/common/tables/nova-rabbitmq.xml:58(td) +msgid "rabbit_userid = guest" +msgstr "" + +#: ./doc/common/tables/cinder-rpc.xml:163(td) ./doc/common/tables/glance-rabbitmq.xml:79(td) ./doc/common/tables/neutron-rabbitmq.xml:56(td) ./doc/common/tables/nova-rabbitmq.xml:59(td) +msgid "(StrOpt) the RabbitMQ userid" +msgstr "" + +#: ./doc/common/tables/cinder-rpc.xml:166(td) ./doc/common/tables/glance-rabbitmq.xml:82(td) ./doc/common/tables/neutron-rabbitmq.xml:59(td) ./doc/common/tables/nova-rabbitmq.xml:62(td) +msgid "rabbit_virtual_host = /" +msgstr "" + +#: ./doc/common/tables/cinder-rpc.xml:167(td) ./doc/common/tables/glance-rabbitmq.xml:83(td) ./doc/common/tables/neutron-rabbitmq.xml:60(td) ./doc/common/tables/nova-rabbitmq.xml:63(td) +msgid "(StrOpt) the RabbitMQ virtual host" +msgstr "" + +#: ./doc/common/tables/cinder-rpc.xml:170(td) +msgid "rpc_backend = cinder.openstack.common.rpc.impl_kombu" +msgstr "" + +#: ./doc/common/tables/cinder-rpc.xml:171(td) ./doc/common/tables/neutron-rpc.xml:56(td) ./doc/common/tables/nova-rpc.xml:43(td) +msgid "(StrOpt) The messaging module to use, defaults to kombu." +msgstr "" + +#: ./doc/common/tables/cinder-rpc.xml:178(td) ./doc/common/tables/neutron-rpc.xml:63(td) ./doc/common/tables/nova-rpc.xml:50(td) +msgid "rpc_conn_pool_size = 30" +msgstr "" + +#: ./doc/common/tables/cinder-rpc.xml:179(td) ./doc/common/tables/neutron-rpc.xml:64(td) ./doc/common/tables/nova-rpc.xml:51(td) +msgid "(IntOpt) Size of RPC connection pool" +msgstr "" + +#: ./doc/common/tables/cinder-rpc.xml:182(td) ./doc/common/tables/neutron-rpc.xml:67(td) ./doc/common/tables/nova-rpc.xml:54(td) +msgid "rpc_response_timeout = 60" +msgstr "" + +#: ./doc/common/tables/cinder-rpc.xml:183(td) ./doc/common/tables/neutron-rpc.xml:68(td) ./doc/common/tables/nova-rpc.xml:55(td) +msgid "(IntOpt) Seconds to wait for a response from call or multicall" +msgstr "" + +#: ./doc/common/tables/cinder-rpc.xml:186(td) ./doc/common/tables/neutron-rpc.xml:75(td) ./doc/common/tables/nova-rpc.xml:58(td) +msgid "rpc_thread_pool_size = 64" +msgstr "" + +#: ./doc/common/tables/cinder-rpc.xml:187(td) ./doc/common/tables/neutron-rpc.xml:76(td) ./doc/common/tables/nova-rpc.xml:59(td) +msgid "(IntOpt) Size of RPC thread pool" +msgstr "" + +#: ./doc/common/tables/cinder-rpc.xml:206(td) +msgid "rpc_zmq_matchmaker = cinder.openstack.common.rpc.matchmaker.MatchMakerLocalhost" +msgstr "" + +#: ./doc/common/tables/cinder-rpc.xml:218(td) +msgid "volume_topic = cinder-volume" +msgstr "" + +#: ./doc/common/tables/cinder-rpc.xml:219(td) +msgid "(StrOpt) the topic volume nodes listen on" +msgstr "" + +#: ./doc/common/tables/cinder-rpc.xml:222(th) ./doc/common/tables/nova-rpc.xml:69(th) +msgid "[matchmaker_ring]" +msgstr "" + +#: ./doc/common/tables/cinder-rpc.xml:225(td) ./doc/common/tables/neutron-rpc.xml:51(td) ./doc/common/tables/nova-rpc.xml:72(td) +msgid "ringfile = /etc/oslo/matchmaker_ring.json" +msgstr "" + +#: ./doc/common/tables/cinder-api.xml:23(td) +msgid "(StrOpt) File name for the paste.deploy config for cinder-api" +msgstr "" + +#: ./doc/common/tables/cinder-api.xml:26(td) +msgid "api_rate_limit = True" +msgstr "" + +#: ./doc/common/tables/cinder-api.xml:27(td) +msgid "(BoolOpt) whether to rate limit the api" +msgstr "" + +#: ./doc/common/tables/cinder-api.xml:31(td) +msgid "(StrOpt) Enable eventlet backdoor. Acceptable values are 0, <port>, and <start>:<end>, where 0 results in listening on a random tcp port number; <port> results in listening on the specified port number (and not enabling backdoor if that port is in use); and <start>:<end> results in listening on the smallest unused port number within the specified range of port numbers. The chosen port is displayed in the service's log file." +msgstr "" + +#: ./doc/common/tables/cinder-api.xml:34(td) ./doc/common/tables/glance-api.xml:38(td) +msgid "enable_v1_api = True" +msgstr "" + +#: ./doc/common/tables/cinder-api.xml:35(td) +msgid "(BoolOpt) Deploy v1 of the Cinder API." +msgstr "" + +#: ./doc/common/tables/cinder-api.xml:38(td) ./doc/common/tables/glance-api.xml:42(td) +msgid "enable_v2_api = True" +msgstr "" + +#: ./doc/common/tables/cinder-api.xml:39(td) +msgid "(BoolOpt) Deploy v2 of the Cinder API." +msgstr "" + +#: ./doc/common/tables/cinder-api.xml:42(td) ./doc/common/tables/nova-policy.xml:46(td) +msgid "osapi_max_limit = 1000" +msgstr "" + +#: ./doc/common/tables/cinder-api.xml:43(td) ./doc/common/tables/nova-policy.xml:47(td) +msgid "(IntOpt) the maximum number of items returned in a single response from a collection resource" +msgstr "" + +#: ./doc/common/tables/cinder-api.xml:46(td) ./doc/common/tables/nova-policy.xml:50(td) +msgid "osapi_max_request_body_size = 114688" +msgstr "" + +#: ./doc/common/tables/cinder-api.xml:47(td) +msgid "(IntOpt) Max size for body of a request" +msgstr "" + +#: ./doc/common/tables/cinder-api.xml:50(td) +msgid "osapi_volume_base_URL = None" +msgstr "" + +#: ./doc/common/tables/cinder-api.xml:51(td) +msgid "(StrOpt) Base URL that will be presented to users in links to the OpenStack Volume API" +msgstr "" + +#: ./doc/common/tables/cinder-api.xml:54(td) +msgid "osapi_volume_ext_list =" +msgstr "" + +#: ./doc/common/tables/cinder-api.xml:55(td) +msgid "(ListOpt) Specify list of extensions to load when using osapi_volume_extension option with cinder.api.contrib.select_extensions" +msgstr "" + +#: ./doc/common/tables/cinder-api.xml:58(td) +msgid "osapi_volume_extension = ['cinder.api.contrib.standard_extensions']" +msgstr "" + +#: ./doc/common/tables/cinder-api.xml:59(td) +msgid "(MultiStrOpt) osapi volume extension to load" +msgstr "" + +#: ./doc/common/tables/cinder-api.xml:62(td) +msgid "osapi_volume_listen = 0.0.0.0" +msgstr "" + +#: ./doc/common/tables/cinder-api.xml:63(td) +msgid "(StrOpt) IP address for OpenStack Volume API to listen" +msgstr "" + +#: ./doc/common/tables/cinder-api.xml:66(td) +msgid "osapi_volume_listen_port = 8776" +msgstr "" + +#: ./doc/common/tables/cinder-api.xml:67(td) +msgid "(IntOpt) port for os volume api to listen" +msgstr "" + +#: ./doc/common/tables/cinder-api.xml:70(td) +msgid "transfer_api_class = cinder.transfer.api.API" +msgstr "" + +#: ./doc/common/tables/cinder-api.xml:71(td) +msgid "(StrOpt) The full class name of the volume transfer API class" +msgstr "" + +#: ./doc/common/tables/cinder-api.xml:74(td) +msgid "volume_api_class = cinder.volume.api.API" +msgstr "" + +#: ./doc/common/tables/cinder-api.xml:78(td) +msgid "volume_name_template = volume-%s" +msgstr "" + +#: ./doc/common/tables/cinder-api.xml:79(td) +msgid "(StrOpt) Template string to be used to generate volume names" +msgstr "" + +#: ./doc/common/tables/cinder-windows.xml:8(caption) +msgid "Description of configuration options for windows" +msgstr "" + +#: ./doc/common/tables/cinder-windows.xml:22(td) +msgid "windows_iscsi_lun_path = C:\\iSCSIVirtualDisks" +msgstr "" + +#: ./doc/common/tables/cinder-windows.xml:23(td) +msgid "(StrOpt) Path to store VHD backed volumes" +msgstr "" + +#: ./doc/common/tables/swift-object-server-pipeline-main.xml:18(td) +msgid "pipeline = healthcheck recon object-server" +msgstr "" + +#: ./doc/common/tables/cinder-san.xml:8(caption) +msgid "Description of configuration options for san" +msgstr "" + +#: ./doc/common/tables/cinder-san.xml:22(td) +msgid "san_clustername =" +msgstr "" + +#: ./doc/common/tables/cinder-san.xml:23(td) +msgid "(StrOpt) Cluster name to use for creating volumes" +msgstr "" + +#: ./doc/common/tables/cinder-san.xml:26(td) +msgid "san_ip =" +msgstr "" + +#: ./doc/common/tables/cinder-san.xml:27(td) +msgid "(StrOpt) IP address of SAN controller" +msgstr "" + +#: ./doc/common/tables/cinder-san.xml:30(td) +msgid "san_is_local = False" +msgstr "" + +#: ./doc/common/tables/cinder-san.xml:31(td) +msgid "(BoolOpt) Execute commands locally instead of over SSH; use if the volume service is running on the SAN device" +msgstr "" + +#: ./doc/common/tables/cinder-san.xml:34(td) +msgid "san_login = admin" +msgstr "" + +#: ./doc/common/tables/cinder-san.xml:35(td) +msgid "(StrOpt) Username for SAN controller" +msgstr "" + +#: ./doc/common/tables/cinder-san.xml:38(td) +msgid "san_password =" +msgstr "" + +#: ./doc/common/tables/cinder-san.xml:39(td) +msgid "(StrOpt) Password for SAN controller" +msgstr "" + +#: ./doc/common/tables/cinder-san.xml:42(td) +msgid "san_private_key =" +msgstr "" + +#: ./doc/common/tables/cinder-san.xml:43(td) +msgid "(StrOpt) Filename of private key to use for SSH authentication" +msgstr "" + +#: ./doc/common/tables/cinder-san.xml:46(td) +msgid "san_ssh_port = 22" +msgstr "" + +#: ./doc/common/tables/cinder-san.xml:47(td) +msgid "(IntOpt) SSH port to use with SAN" +msgstr "" + +#: ./doc/common/tables/cinder-san.xml:50(td) +msgid "san_thin_provision = True" +msgstr "" + +#: ./doc/common/tables/cinder-san.xml:51(td) +msgid "(BoolOpt) Use thin provisioning for SAN volumes?" +msgstr "" + +#: ./doc/common/tables/cinder-san.xml:54(td) +msgid "ssh_conn_timeout = 30" +msgstr "" + +#: ./doc/common/tables/cinder-san.xml:55(td) +msgid "(IntOpt) SSH connection timeout in seconds" +msgstr "" + +#: ./doc/common/tables/cinder-san.xml:58(td) +msgid "ssh_max_pool_conn = 5" +msgstr "" + +#: ./doc/common/tables/cinder-san.xml:59(td) +msgid "(IntOpt) Maximum ssh connections in the pool" +msgstr "" + +#: ./doc/common/tables/cinder-san.xml:62(td) +msgid "ssh_min_pool_conn = 1" +msgstr "" + +#: ./doc/common/tables/cinder-san.xml:63(td) +msgid "(IntOpt) Minimum ssh connections in the pool" +msgstr "" + +#: ./doc/common/tables/swift-account-server-app-account-server.xml:7(literal) +msgid "[app:account-server]" +msgstr "" + +#: ./doc/common/tables/swift-account-server-app-account-server.xml:18(td) +msgid "use = egg:swift#account" +msgstr "" + +#: ./doc/common/tables/swift-account-server-app-account-server.xml:21(td) +msgid "set log_name = account-server" +msgstr "" + +#: ./doc/common/tables/swift-account-server-app-account-server.xml:30(td) ./doc/common/tables/swift-container-server-app-container-server.xml:30(td) ./doc/common/tables/swift-object-server-app-object-server.xml:30(td) +msgid "set log_requests = true" +msgstr "" + +#: ./doc/common/tables/swift-account-server-app-account-server.xml:30(td) ./doc/common/tables/swift-container-server-app-container-server.xml:30(td) ./doc/common/tables/swift-object-server-app-object-server.xml:30(td) +msgid "Whether or not to log requests" +msgstr "" + +#: ./doc/common/tables/swift-account-server-app-account-server.xml:39(td) ./doc/common/tables/swift-container-server-app-container-server.xml:48(td) ./doc/common/tables/swift-object-server-app-object-server.xml:69(td) +msgid "replication_server = false" +msgstr "" + +#: ./doc/common/tables/swift-account-server-app-account-server.xml:39(td) ./doc/common/tables/swift-container-server-app-container-server.xml:48(td) ./doc/common/tables/swift-object-server-app-object-server.xml:69(td) +msgid "If defined, tells server how to handle replication verbs in requests. When set to True (or 1), only replication verbs will be accepted. When set to False, replication verbs will be rejected. When undefined, server will accept any verb in the request." +msgstr "" + +#: ./doc/common/tables/cinder-keymgr.xml:22(td) +msgid "api_class = cinder.keymgr.conf_key_mgr.ConfKeyManager" +msgstr "" + +#: ./doc/common/tables/nova-db.xml:8(caption) ./doc/common/tables/neutron-db.xml:8(caption) ./doc/common/tables/glance-db.xml:8(caption) +msgid "Description of configuration options for db" +msgstr "" + +#: ./doc/common/tables/nova-db.xml:22(td) +msgid "db_driver = nova.db" +msgstr "" + +#: ./doc/common/tables/nova-db.xml:23(td) ./doc/common/tables/cinder-database.xml:27(td) +msgid "(StrOpt) driver to use for database access" +msgstr "" + +#: ./doc/common/tables/nova-db.xml:26(td) +msgid "sqlite_db = nova.sqlite" +msgstr "" + +#: ./doc/common/tables/nova-db.xml:27(td) ./doc/common/tables/cinder-common.xml:183(td) ./doc/common/tables/neutron-db.xml:72(td) ./doc/common/tables/glance-db.xml:23(td) +msgid "(StrOpt) the filename to use with sqlite" +msgstr "" + +#: ./doc/common/tables/nova-db.xml:30(td) ./doc/common/tables/cinder-common.xml:186(td) ./doc/common/tables/neutron-db.xml:75(td) ./doc/common/tables/glance-db.xml:26(td) +msgid "sqlite_synchronous = True" +msgstr "" + +#: ./doc/common/tables/nova-db.xml:31(td) ./doc/common/tables/cinder-common.xml:187(td) ./doc/common/tables/neutron-db.xml:76(td) ./doc/common/tables/glance-db.xml:27(td) +msgid "(BoolOpt) If true, use synchronous mode for sqlite" +msgstr "" + +#: ./doc/common/tables/nova-db.xml:37(td) +msgid "db_check_interval = 60" +msgstr "" + +#: ./doc/common/tables/nova-db.xml:38(td) +msgid "(IntOpt) Seconds between getting fresh cell info from db." +msgstr "" + +#: ./doc/common/tables/nova-db.xml:41(th) ./doc/common/tables/cinder-storage.xml:138(th) ./doc/common/tables/glance-common.xml:106(th) ./doc/common/tables/cinder-common.xml:238(th) ./doc/common/tables/cinder-connection.xml:19(th) ./doc/common/tables/glance-db.xml:30(th) ./doc/common/tables/nova-api.xml:90(th) +msgid "[database]" +msgstr "" + +#: ./doc/common/tables/nova-db.xml:44(td) ./doc/common/tables/cinder-storage.xml:141(td) ./doc/common/tables/neutron-db.xml:19(td) ./doc/common/tables/glance-db.xml:33(td) +msgid "backend = sqlalchemy" +msgstr "" + +#: ./doc/common/tables/nova-db.xml:45(td) ./doc/common/tables/cinder-storage.xml:142(td) ./doc/common/tables/cinder-database.xml:23(td) ./doc/common/tables/neutron-db.xml:20(td) ./doc/common/tables/glance-db.xml:34(td) +msgid "(StrOpt) The backend to use for db" +msgstr "" + +#: ./doc/common/tables/nova-db.xml:48(td) +msgid "connection = sqlite:////home/shaunm/Projects/nova/nova/openstack/common/db/$sqlite_db" +msgstr "" + +#: ./doc/common/tables/nova-db.xml:49(td) ./doc/common/tables/cinder-connection.xml:23(td) ./doc/common/tables/neutron-db.xml:24(td) ./doc/common/tables/glance-db.xml:38(td) +msgid "(StrOpt) The SQLAlchemy connection string used to connect to the database" +msgstr "" + +#: ./doc/common/tables/nova-db.xml:52(td) ./doc/common/tables/cinder-connection.xml:26(td) ./doc/common/tables/neutron-db.xml:27(td) ./doc/common/tables/glance-db.xml:41(td) +msgid "connection_debug = 0" +msgstr "" + +#: ./doc/common/tables/nova-db.xml:53(td) ./doc/common/tables/cinder-connection.xml:27(td) ./doc/common/tables/neutron-db.xml:28(td) ./doc/common/tables/glance-db.xml:42(td) +msgid "(IntOpt) Verbosity of SQL debugging information. 0=None, 100=Everything" +msgstr "" + +#: ./doc/common/tables/nova-db.xml:56(td) ./doc/common/tables/cinder-connection.xml:30(td) ./doc/common/tables/neutron-db.xml:31(td) ./doc/common/tables/glance-db.xml:45(td) +msgid "connection_trace = False" +msgstr "" + +#: ./doc/common/tables/nova-db.xml:57(td) ./doc/common/tables/cinder-connection.xml:31(td) ./doc/common/tables/neutron-db.xml:32(td) ./doc/common/tables/glance-db.xml:46(td) +msgid "(BoolOpt) Add python stack traces to SQL as comment strings" +msgstr "" + +#: ./doc/common/tables/nova-db.xml:60(td) ./doc/common/tables/cinder-common.xml:241(td) ./doc/common/tables/neutron-db.xml:39(td) ./doc/common/tables/glance-db.xml:49(td) +msgid "idle_timeout = 3600" +msgstr "" + +#: ./doc/common/tables/nova-db.xml:61(td) ./doc/common/tables/cinder-common.xml:242(td) ./doc/common/tables/neutron-db.xml:40(td) ./doc/common/tables/glance-db.xml:50(td) +msgid "(IntOpt) timeout before idle sql connections are reaped" +msgstr "" + +#: ./doc/common/tables/nova-db.xml:64(td) ./doc/common/tables/cinder-storage.xml:145(td) ./doc/common/tables/glance-db.xml:53(td) +msgid "max_overflow = None" +msgstr "" + +#: ./doc/common/tables/nova-db.xml:65(td) ./doc/common/tables/cinder-storage.xml:146(td) ./doc/common/tables/neutron-db.xml:44(td) ./doc/common/tables/glance-db.xml:54(td) +msgid "(IntOpt) If set, use this value for max_overflow with sqlalchemy" +msgstr "" + +#: ./doc/common/tables/nova-db.xml:68(td) ./doc/common/tables/glance-db.xml:57(td) +msgid "max_pool_size = None" +msgstr "" + +#: ./doc/common/tables/nova-db.xml:69(td) ./doc/common/tables/cinder-storage.xml:150(td) ./doc/common/tables/neutron-db.xml:48(td) ./doc/common/tables/glance-db.xml:58(td) +msgid "(IntOpt) Maximum number of SQL connections to keep open in a pool" +msgstr "" + +#: ./doc/common/tables/nova-db.xml:72(td) ./doc/common/tables/cinder-storage.xml:153(td) ./doc/common/tables/neutron-db.xml:51(td) ./doc/common/tables/glance-db.xml:61(td) +msgid "max_retries = 10" +msgstr "" + +#: ./doc/common/tables/nova-db.xml:73(td) ./doc/common/tables/cinder-storage.xml:154(td) ./doc/common/tables/neutron-db.xml:52(td) ./doc/common/tables/glance-db.xml:62(td) +msgid "(IntOpt) maximum db connection retries during startup. (setting -1 implies an infinite retry count)" +msgstr "" + +#: ./doc/common/tables/nova-db.xml:76(td) ./doc/common/tables/cinder-storage.xml:157(td) ./doc/common/tables/neutron-db.xml:55(td) ./doc/common/tables/glance-db.xml:65(td) +msgid "min_pool_size = 1" +msgstr "" + +#: ./doc/common/tables/nova-db.xml:77(td) ./doc/common/tables/cinder-storage.xml:158(td) ./doc/common/tables/neutron-db.xml:56(td) ./doc/common/tables/glance-db.xml:66(td) +msgid "(IntOpt) Minimum number of SQL connections to keep open in a pool" +msgstr "" + +#: ./doc/common/tables/nova-db.xml:80(td) ./doc/common/tables/glance-db.xml:69(td) +msgid "pool_timeout = None" +msgstr "" + +#: ./doc/common/tables/nova-db.xml:81(td) ./doc/common/tables/neutron-db.xml:60(td) ./doc/common/tables/glance-db.xml:70(td) +msgid "(IntOpt) If set, use this value for pool_timeout with sqlalchemy" +msgstr "" + +#: ./doc/common/tables/nova-db.xml:84(td) ./doc/common/tables/cinder-common.xml:245(td) ./doc/common/tables/neutron-db.xml:63(td) ./doc/common/tables/glance-db.xml:73(td) +msgid "retry_interval = 10" +msgstr "" + +#: ./doc/common/tables/nova-db.xml:85(td) ./doc/common/tables/cinder-common.xml:246(td) ./doc/common/tables/neutron-db.xml:64(td) ./doc/common/tables/glance-db.xml:74(td) +msgid "(IntOpt) interval between retries of opening a sql connection" +msgstr "" + +#: ./doc/common/tables/nova-db.xml:88(td) ./doc/common/tables/neutron-db.xml:67(td) ./doc/common/tables/glance-db.xml:77(td) +msgid "slave_connection =" +msgstr "" + +#: ./doc/common/tables/nova-db.xml:89(td) ./doc/common/tables/neutron-db.xml:68(td) ./doc/common/tables/glance-db.xml:78(td) +msgid "(StrOpt) The SQLAlchemy connection string used to connect to the slave database" +msgstr "" + +#: ./doc/common/tables/neutron-ml2_vxlan.xml:8(caption) +msgid "Description of configuration options for ml2_vxlan" +msgstr "" + +#: ./doc/common/tables/neutron-ml2_vxlan.xml:19(td) +msgid "vni_ranges =" +msgstr "" + +#: ./doc/common/tables/neutron-ml2_vxlan.xml:20(td) +msgid "(ListOpt) Comma-separated list of <vni_min>:<vni_max> tuples enumerating ranges of VXLAN VNI IDs that are available for tenant network allocation" +msgstr "" + +#: ./doc/common/tables/neutron-ml2_vxlan.xml:23(td) +msgid "vxlan_group = None" +msgstr "" + +#: ./doc/common/tables/neutron-ml2_vxlan.xml:24(td) +msgid "(StrOpt) Multicast group for VXLAN. If unset, disables VXLAN multicast mode." +msgstr "" + +#: ./doc/common/tables/glance-logging.xml:8(caption) ./doc/common/tables/neutron-logging.xml:8(caption) ./doc/common/tables/nova-logging.xml:8(caption) +msgid "Description of configuration options for logging" +msgstr "" + +#: ./doc/common/tables/glance-logging.xml:22(td) ./doc/common/tables/neutron-logging.xml:19(td) ./doc/common/tables/nova-logging.xml:22(td) ./doc/common/tables/cinder-common.xml:26(td) +msgid "debug = False" +msgstr "" + +#: ./doc/common/tables/glance-logging.xml:23(td) ./doc/common/tables/neutron-logging.xml:20(td) ./doc/common/tables/nova-logging.xml:23(td) ./doc/common/tables/cinder-common.xml:27(td) +msgid "(BoolOpt) Print debugging output (set logging level to DEBUG instead of default WARNING level)." +msgstr "" + +#: ./doc/common/tables/glance-logging.xml:26(td) ./doc/common/tables/neutron-logging.xml:23(td) ./doc/common/tables/nova-logging.xml:26(td) ./doc/common/tables/cinder-common.xml:34(td) +msgid "default_log_levels = amqp=WARN, amqplib=WARN, boto=WARN, keystone=INFO, qpid=WARN, sqlalchemy=WARN, suds=INFO, iso8601=WARN" +msgstr "" + +#: ./doc/common/tables/glance-logging.xml:27(td) ./doc/common/tables/neutron-logging.xml:24(td) ./doc/common/tables/nova-logging.xml:27(td) ./doc/common/tables/cinder-common.xml:35(td) +msgid "(ListOpt) list of logger=LEVEL pairs" +msgstr "" + +#: ./doc/common/tables/glance-logging.xml:30(td) ./doc/common/tables/neutron-logging.xml:27(td) ./doc/common/tables/nova-logging.xml:30(td) ./doc/common/tables/cinder-common.xml:58(td) +msgid "fatal_deprecations = False" +msgstr "" + +#: ./doc/common/tables/glance-logging.xml:31(td) ./doc/common/tables/neutron-logging.xml:28(td) ./doc/common/tables/nova-logging.xml:31(td) ./doc/common/tables/cinder-common.xml:59(td) +msgid "(BoolOpt) make deprecations fatal" +msgstr "" + +#: ./doc/common/tables/glance-logging.xml:34(td) ./doc/common/tables/cinder-images.xml:62(td) ./doc/common/tables/nova-logging.xml:38(td) +msgid "instance_format = \"[instance: %(uuid)s] \"" +msgstr "" + +#: ./doc/common/tables/glance-logging.xml:35(td) ./doc/common/tables/cinder-images.xml:63(td) ./doc/common/tables/neutron-logging.xml:32(td) ./doc/common/tables/nova-logging.xml:39(td) +msgid "(StrOpt) If an instance is passed with the log message, format it like this" +msgstr "" + +#: ./doc/common/tables/glance-logging.xml:38(td) ./doc/common/tables/cinder-images.xml:66(td) ./doc/common/tables/nova-logging.xml:42(td) +msgid "instance_uuid_format = \"[instance: %(uuid)s] \"" +msgstr "" + +#: ./doc/common/tables/glance-logging.xml:39(td) ./doc/common/tables/cinder-images.xml:67(td) ./doc/common/tables/neutron-logging.xml:36(td) ./doc/common/tables/nova-logging.xml:43(td) +msgid "(StrOpt) If an instance UUID is passed with the log message, format it like this" +msgstr "" + +#: ./doc/common/tables/glance-logging.xml:42(td) ./doc/common/tables/nova-logging.xml:46(td) ./doc/common/tables/cinder-common.xml:82(td) +msgid "log-config-append = None" +msgstr "" + +#: ./doc/common/tables/glance-logging.xml:43(td) ./doc/common/tables/neutron-logging.xml:40(td) ./doc/common/tables/nova-logging.xml:47(td) ./doc/common/tables/cinder-common.xml:83(td) +msgid "(StrOpt) The name of logging configuration file. It does not disable existing loggers, but just appends specified logging configuration to any other existing logging options. Please see the Python logging module documentation for details on logging configuration files." +msgstr "" + +#: ./doc/common/tables/glance-logging.xml:46(td) ./doc/common/tables/nova-logging.xml:50(td) ./doc/common/tables/cinder-common.xml:86(td) +msgid "log-date-format = %Y-%m-%d %H:%M:%S" +msgstr "" + +#: ./doc/common/tables/glance-logging.xml:47(td) ./doc/common/tables/neutron-logging.xml:44(td) ./doc/common/tables/nova-logging.xml:51(td) ./doc/common/tables/cinder-common.xml:87(td) +msgid "(StrOpt) Format string for %%(asctime)s in log records. Default: %(default)s" +msgstr "" + +#: ./doc/common/tables/glance-logging.xml:50(td) ./doc/common/tables/nova-logging.xml:54(td) ./doc/common/tables/cinder-common.xml:90(td) +msgid "log-dir = None" +msgstr "" + +#: ./doc/common/tables/glance-logging.xml:51(td) ./doc/common/tables/neutron-logging.xml:48(td) ./doc/common/tables/nova-logging.xml:55(td) ./doc/common/tables/cinder-common.xml:91(td) +msgid "(StrOpt) (Optional) The base directory used for relative --log-file paths" +msgstr "" + +#: ./doc/common/tables/glance-logging.xml:54(td) ./doc/common/tables/nova-logging.xml:58(td) ./doc/common/tables/cinder-common.xml:94(td) +msgid "log-file = None" +msgstr "" + +#: ./doc/common/tables/glance-logging.xml:55(td) ./doc/common/tables/neutron-logging.xml:52(td) ./doc/common/tables/nova-logging.xml:59(td) ./doc/common/tables/cinder-common.xml:95(td) +msgid "(StrOpt) (Optional) Name of log file to output to. If no default is set, logging will go to stdout." +msgstr "" + +#: ./doc/common/tables/glance-logging.xml:58(td) ./doc/common/tables/nova-logging.xml:62(td) ./doc/common/tables/cinder-common.xml:98(td) +msgid "log-format = None" +msgstr "" + +#: ./doc/common/tables/glance-logging.xml:59(td) ./doc/common/tables/neutron-logging.xml:56(td) ./doc/common/tables/nova-logging.xml:63(td) ./doc/common/tables/cinder-common.xml:99(td) +msgid "(StrOpt) DEPRECATED. A logging.Formatter log message format string which may use any of the available logging.LogRecord attributes. This option is deprecated. Please use logging_context_format_string and logging_default_format_string instead." +msgstr "" + +#: ./doc/common/tables/glance-logging.xml:62(td) ./doc/common/tables/neutron-logging.xml:59(td) ./doc/common/tables/nova-logging.xml:66(td) ./doc/common/tables/cinder-common.xml:102(td) +msgid "logging_context_format_string = %(asctime)s.%(msecs)03d %(process)d %(levelname)s %(name)s [%(request_id)s %(user)s %(tenant)s] %(instance)s%(message)s" +msgstr "" + +#: ./doc/common/tables/glance-logging.xml:63(td) ./doc/common/tables/neutron-logging.xml:60(td) ./doc/common/tables/nova-logging.xml:67(td) ./doc/common/tables/cinder-common.xml:103(td) +msgid "(StrOpt) format string to use for log messages with context" +msgstr "" + +#: ./doc/common/tables/glance-logging.xml:66(td) ./doc/common/tables/neutron-logging.xml:63(td) ./doc/common/tables/nova-logging.xml:70(td) ./doc/common/tables/cinder-common.xml:106(td) +msgid "logging_debug_format_suffix = %(funcName)s %(pathname)s:%(lineno)d" +msgstr "" + +#: ./doc/common/tables/glance-logging.xml:67(td) ./doc/common/tables/neutron-logging.xml:64(td) ./doc/common/tables/nova-logging.xml:71(td) ./doc/common/tables/cinder-common.xml:107(td) +msgid "(StrOpt) data to append to log format when level is DEBUG" +msgstr "" + +#: ./doc/common/tables/glance-logging.xml:70(td) ./doc/common/tables/neutron-logging.xml:67(td) ./doc/common/tables/nova-logging.xml:74(td) ./doc/common/tables/cinder-common.xml:110(td) +msgid "logging_default_format_string = %(asctime)s.%(msecs)03d %(process)d %(levelname)s %(name)s [-] %(instance)s%(message)s" +msgstr "" + +#: ./doc/common/tables/glance-logging.xml:71(td) ./doc/common/tables/neutron-logging.xml:68(td) ./doc/common/tables/nova-logging.xml:75(td) ./doc/common/tables/cinder-common.xml:111(td) +msgid "(StrOpt) format string to use for log messages without context" +msgstr "" + +#: ./doc/common/tables/glance-logging.xml:74(td) ./doc/common/tables/neutron-logging.xml:71(td) ./doc/common/tables/nova-logging.xml:78(td) ./doc/common/tables/cinder-common.xml:114(td) +msgid "logging_exception_prefix = %(asctime)s.%(msecs)03d %(process)d TRACE %(name)s %(instance)s" +msgstr "" + +#: ./doc/common/tables/glance-logging.xml:75(td) ./doc/common/tables/neutron-logging.xml:72(td) ./doc/common/tables/nova-logging.xml:79(td) ./doc/common/tables/cinder-common.xml:115(td) +msgid "(StrOpt) prefix each line of exception output with this format" +msgstr "" + +#: ./doc/common/tables/glance-logging.xml:82(td) ./doc/common/tables/nova-logging.xml:86(td) ./doc/common/tables/cinder-common.xml:210(td) +msgid "syslog-log-facility = LOG_USER" +msgstr "" + +#: ./doc/common/tables/glance-logging.xml:83(td) ./doc/common/tables/neutron-logging.xml:80(td) ./doc/common/tables/nova-logging.xml:87(td) ./doc/common/tables/cinder-common.xml:211(td) +msgid "(StrOpt) syslog facility to receive log lines" +msgstr "" + +#: ./doc/common/tables/glance-logging.xml:86(td) ./doc/common/tables/nova-logging.xml:90(td) ./doc/common/tables/cinder-common.xml:222(td) +msgid "use-syslog = False" +msgstr "" + +#: ./doc/common/tables/glance-logging.xml:87(td) ./doc/common/tables/neutron-logging.xml:88(td) ./doc/common/tables/nova-logging.xml:91(td) ./doc/common/tables/cinder-common.xml:223(td) +msgid "(BoolOpt) Use syslog for logging." +msgstr "" + +#: ./doc/common/tables/glance-logging.xml:90(td) ./doc/common/tables/neutron-logging.xml:83(td) ./doc/common/tables/nova-logging.xml:94(td) ./doc/common/tables/cinder-common.xml:230(td) +msgid "use_stderr = True" +msgstr "" + +#: ./doc/common/tables/glance-logging.xml:91(td) ./doc/common/tables/neutron-logging.xml:84(td) ./doc/common/tables/nova-logging.xml:95(td) ./doc/common/tables/cinder-common.xml:231(td) +msgid "(BoolOpt) Log output to standard error" +msgstr "" + +#: ./doc/common/tables/glance-logging.xml:94(td) ./doc/common/tables/neutron-logging.xml:91(td) ./doc/common/tables/nova-logging.xml:98(td) ./doc/common/tables/cinder-common.xml:234(td) +msgid "verbose = False" +msgstr "" + +#: ./doc/common/tables/glance-logging.xml:95(td) ./doc/common/tables/neutron-logging.xml:92(td) ./doc/common/tables/nova-logging.xml:99(td) ./doc/common/tables/cinder-common.xml:235(td) +msgid "(BoolOpt) Print more verbose output (set logging level to INFO instead of default WARNING level)." +msgstr "" + +#: ./doc/common/tables/glance-wsgi.xml:8(caption) ./doc/common/tables/neutron-wsgi.xml:8(caption) ./doc/common/tables/nova-wsgi.xml:8(caption) +msgid "Description of configuration options for wsgi" +msgstr "" + +#: ./doc/common/tables/glance-wsgi.xml:23(td) ./doc/common/tables/neutron-testing.xml:20(td) +msgid "(IntOpt) port for eventlet backdoor to listen" +msgstr "" + +#: ./doc/common/tables/glance-wsgi.xml:26(td) +msgid "eventlet_hub = poll" +msgstr "" + +#: ./doc/common/tables/glance-wsgi.xml:27(td) +msgid "(StrOpt) Name of eventlet hub to use. Traditionally, we have only supported 'poll', however 'selects' may be appropriate for some platforms. See http://eventlet.net/doc/hubs.html for more details." +msgstr "" + +#: ./doc/common/tables/glance-wsgi.xml:30(td) +msgid "max_header_line = 16384" +msgstr "" + +#: ./doc/common/tables/glance-wsgi.xml:31(td) +msgid "(IntOpt) Maximum line size of message headers to be accepted. max_header_line may need to be increased when using large tokens (typically those generated by the Keystone v3 API with big service catalogs" +msgstr "" + +#: ./doc/common/tables/glance-wsgi.xml:34(td) ./doc/common/tables/neutron-wsgi.xml:27(td) ./doc/common/tables/nova-wsgi.xml:38(td) ./doc/common/tables/cinder-common.xml:214(td) +msgid "tcp_keepidle = 600" +msgstr "" + +#: ./doc/common/tables/glance-wsgi.xml:35(td) +msgid "(IntOpt) The value for the socket option TCP_KEEPIDLE. This is the time in seconds that the connection must be idle before TCP starts sending keepalive probes." +msgstr "" + +#: ./doc/common/tables/nova-periodic.xml:8(caption) +msgid "Description of configuration options for periodic" +msgstr "" + +#: ./doc/common/tables/nova-periodic.xml:22(td) +msgid "periodic_enable = True" +msgstr "" + +#: ./doc/common/tables/nova-periodic.xml:23(td) +msgid "(BoolOpt) enable periodic tasks" +msgstr "" + +#: ./doc/common/tables/nova-periodic.xml:26(td) ./doc/common/tables/cinder-common.xml:138(td) +msgid "periodic_fuzzy_delay = 60" +msgstr "" + +#: ./doc/common/tables/nova-periodic.xml:27(td) ./doc/common/tables/cinder-common.xml:139(td) +msgid "(IntOpt) range of seconds to randomly delay when starting the periodic task scheduler to reduce stampeding. (Disable by setting to 0)" +msgstr "" + +#: ./doc/common/tables/cinder-images.xml:8(caption) +msgid "Description of configuration options for images" +msgstr "" + +#: ./doc/common/tables/cinder-images.xml:23(td) +msgid "(ListOpt) A list of url schemes that can be downloaded directly via the direct_url. Currently supported schemes: [file]." +msgstr "" + +#: ./doc/common/tables/cinder-images.xml:31(td) +msgid "(ListOpt) A list of the glance api servers available to cinder ([hostname|ip]:port)" +msgstr "" + +#: ./doc/common/tables/cinder-images.xml:34(td) +msgid "glance_api_ssl_compression = False" +msgstr "" + +#: ./doc/common/tables/cinder-images.xml:35(td) +msgid "(BoolOpt) Whether to attempt to negotiate SSL layer compression when using SSL (https) requests. Set to False to disable SSL layer compression. In some cases disabling this may improve data throughput, eg when high network bandwidth is available and you are using already compressed image formats such as qcow2 ." +msgstr "" + +#: ./doc/common/tables/cinder-images.xml:38(td) +msgid "glance_api_version = 1" +msgstr "" + +#: ./doc/common/tables/cinder-images.xml:39(td) +msgid "(IntOpt) Version of the glance api to use" +msgstr "" + +#: ./doc/common/tables/cinder-images.xml:54(td) +msgid "glance_request_timeout = None" +msgstr "" + +#: ./doc/common/tables/cinder-images.xml:55(td) +msgid "(IntOpt) http/https timeout value for glance operations. If no value (None) is supplied here, the glanceclient default value is used." +msgstr "" + +#: ./doc/common/tables/cinder-images.xml:58(td) +msgid "image_conversion_dir = $state_path/conversion" +msgstr "" + +#: ./doc/common/tables/cinder-images.xml:59(td) +msgid "(StrOpt) Directory used for temporary storage during image conversion" +msgstr "" + +#: ./doc/common/tables/cinder-images.xml:70(td) +msgid "use_multipath_for_image_xfer = False" +msgstr "" + +#: ./doc/common/tables/cinder-images.xml:71(td) +msgid "(BoolOpt) Do we attach/detach volumes in cinder using multipath for volume to image and image to volume transfers?" +msgstr "" + +#: ./doc/common/tables/swift-container-server-app-container-server.xml:7(literal) +msgid "[app:container-server]" +msgstr "" + +#: ./doc/common/tables/swift-container-server-app-container-server.xml:18(td) +msgid "use = egg:swift#container" +msgstr "" + +#: ./doc/common/tables/swift-container-server-app-container-server.xml:21(td) +msgid "set log_name = container-server" +msgstr "" + +#: ./doc/common/tables/swift-container-server-app-container-server.xml:42(td) +msgid "allow_versions = false" +msgstr "" + +#: ./doc/common/tables/swift-container-server-app-container-server.xml:42(td) +msgid "Enable/Disable object versioning feature" +msgstr "" + +#: ./doc/common/tables/swift-proxy-server-filter-slo.xml:7(literal) +msgid "[filter:slo]" +msgstr "" + +#: ./doc/common/tables/swift-proxy-server-filter-slo.xml:18(td) +msgid "use = egg:swift#slo" +msgstr "" + +#: ./doc/common/tables/swift-proxy-server-filter-slo.xml:21(td) +msgid "max_manifest_segments = 1000" +msgstr "" + +#: ./doc/common/tables/swift-proxy-server-filter-slo.xml:24(td) +msgid "max_manifest_size = 2097152" +msgstr "" + +#: ./doc/common/tables/swift-proxy-server-filter-slo.xml:27(td) +msgid "min_segment_size = 1048576" +msgstr "" + +#: ./doc/common/tables/neutron-wsgi.xml:20(td) ./doc/common/tables/cinder-log.xml:23(td) +msgid "(IntOpt) Number of backlog requests to configure the socket with" +msgstr "" + +#: ./doc/common/tables/neutron-wsgi.xml:23(td) +msgid "retry_until_window = 30" +msgstr "" + +#: ./doc/common/tables/neutron-wsgi.xml:24(td) +msgid "(IntOpt) Number of seconds to keep retrying to listen" +msgstr "" + +#: ./doc/common/tables/neutron-wsgi.xml:28(td) ./doc/common/tables/nova-wsgi.xml:39(td) ./doc/common/tables/cinder-common.xml:215(td) +msgid "(IntOpt) Sets the value of TCP_KEEPIDLE in seconds for each server socket. Not supported on OS X." +msgstr "" + +#: ./doc/common/tables/neutron-scheduler.xml:8(caption) ./doc/common/tables/cinder-scheduler.xml:8(caption) +msgid "Description of configuration options for scheduler" +msgstr "" + +#: ./doc/common/tables/neutron-scheduler.xml:19(td) +msgid "network_auto_schedule = True" +msgstr "" + +#: ./doc/common/tables/neutron-scheduler.xml:20(td) +msgid "(BoolOpt) Allow auto scheduling networks to DHCP agent." +msgstr "" + +#: ./doc/common/tables/neutron-scheduler.xml:23(td) +msgid "network_scheduler_driver = neutron.scheduler.dhcp_agent_scheduler.ChanceScheduler" +msgstr "" + +#: ./doc/common/tables/neutron-scheduler.xml:24(td) +msgid "(StrOpt) Driver to use for scheduling network to DHCP agent" +msgstr "" + +#: ./doc/common/tables/neutron-scheduler.xml:27(td) +msgid "router_auto_schedule = True" +msgstr "" + +#: ./doc/common/tables/neutron-scheduler.xml:28(td) +msgid "(BoolOpt) Allow auto scheduling of routers to L3 agent." +msgstr "" + +#: ./doc/common/tables/neutron-scheduler.xml:31(td) +msgid "router_scheduler_driver = neutron.scheduler.l3_agent_scheduler.ChanceScheduler" +msgstr "" + +#: ./doc/common/tables/neutron-scheduler.xml:32(td) +msgid "(StrOpt) Driver to use for scheduling router to a default L3 agent" +msgstr "" + +#: ./doc/common/tables/glance-rbd.xml:8(caption) +msgid "Description of configuration options for rbd" +msgstr "" + +#: ./doc/common/tables/glance-rbd.xml:22(td) +msgid "rbd_store_ceph_conf = /etc/ceph/ceph.conf" +msgstr "" + +#: ./doc/common/tables/glance-rbd.xml:23(td) +msgid "(StrOpt) Ceph configuration file path. If <None>, librados will locate the default config. If using cephx authentication, this file should include a reference to the right keyring in a client.<USER> section" +msgstr "" + +#: ./doc/common/tables/glance-rbd.xml:26(td) +msgid "rbd_store_chunk_size = 8" +msgstr "" + +#: ./doc/common/tables/glance-rbd.xml:27(td) +msgid "(IntOpt) RADOS images will be chunked into objects of this size (in megabytes). For best performance, this should be a power of two." +msgstr "" + +#: ./doc/common/tables/glance-rbd.xml:30(td) +msgid "rbd_store_pool = images" +msgstr "" + +#: ./doc/common/tables/glance-rbd.xml:31(td) +msgid "(StrOpt) RADOS pool in which images are stored." +msgstr "" + +#: ./doc/common/tables/glance-rbd.xml:34(td) +msgid "rbd_store_user = None" +msgstr "" + +#: ./doc/common/tables/glance-rbd.xml:35(td) +msgid "(StrOpt) RADOS user to authenticate as (only applicable if using Cephx. If <None>, a default will be chosen based on the client. section in rbd_store_ceph_conf)" +msgstr "" + +#: ./doc/common/tables/cinder-hp3par.xml:8(caption) +msgid "Description of configuration options for hp3par" +msgstr "" + +#: ./doc/common/tables/cinder-hp3par.xml:22(td) +msgid "hp3par_api_url =" +msgstr "" + +#: ./doc/common/tables/cinder-hp3par.xml:23(td) +msgid "(StrOpt) 3PAR WSAPI Server Url like https://<3par ip>:8080/api/v1" +msgstr "" + +#: ./doc/common/tables/cinder-hp3par.xml:26(td) +msgid "hp3par_cpg = OpenStack" +msgstr "" + +#: ./doc/common/tables/cinder-hp3par.xml:27(td) +msgid "(StrOpt) The CPG to use for volume creation" +msgstr "" + +#: ./doc/common/tables/cinder-hp3par.xml:30(td) +msgid "hp3par_cpg_snap =" +msgstr "" + +#: ./doc/common/tables/cinder-hp3par.xml:31(td) +msgid "(StrOpt) The CPG to use for Snapshots for volumes. If empty hp3par_cpg will be used" +msgstr "" + +#: ./doc/common/tables/cinder-hp3par.xml:34(td) +msgid "hp3par_debug = False" +msgstr "" + +#: ./doc/common/tables/cinder-hp3par.xml:35(td) +msgid "(BoolOpt) Enable HTTP debugging to 3PAR" +msgstr "" + +#: ./doc/common/tables/cinder-hp3par.xml:38(td) +msgid "hp3par_iscsi_ips =" +msgstr "" + +#: ./doc/common/tables/cinder-hp3par.xml:39(td) +msgid "(ListOpt) List of target iSCSI addresses to use." +msgstr "" + +#: ./doc/common/tables/cinder-hp3par.xml:42(td) +msgid "hp3par_password =" +msgstr "" + +#: ./doc/common/tables/cinder-hp3par.xml:43(td) +msgid "(StrOpt) 3PAR Super user password" +msgstr "" + +#: ./doc/common/tables/cinder-hp3par.xml:46(td) +msgid "hp3par_snapshot_expiration =" +msgstr "" + +#: ./doc/common/tables/cinder-hp3par.xml:47(td) +msgid "(StrOpt) The time in hours when a snapshot expires and is deleted. This must be larger than expiration" +msgstr "" + +#: ./doc/common/tables/cinder-hp3par.xml:50(td) +msgid "hp3par_snapshot_retention =" +msgstr "" + +#: ./doc/common/tables/cinder-hp3par.xml:51(td) +msgid "(StrOpt) The time in hours to retain a snapshot. You can't delete it before this expires." +msgstr "" + +#: ./doc/common/tables/cinder-hp3par.xml:54(td) +msgid "hp3par_username =" +msgstr "" + +#: ./doc/common/tables/cinder-hp3par.xml:55(td) +msgid "(StrOpt) 3PAR Super user username" +msgstr "" + +#: ./doc/common/tables/cinder-storage_ceph.xml:8(caption) +msgid "Description of configuration options for storage_ceph" +msgstr "" + +#: ./doc/common/tables/cinder-storage_ceph.xml:22(td) +msgid "rbd_ceph_conf =" +msgstr "" + +#: ./doc/common/tables/cinder-storage_ceph.xml:26(td) +msgid "rbd_flatten_volume_from_snapshot = False" +msgstr "" + +#: ./doc/common/tables/cinder-storage_ceph.xml:27(td) +msgid "(BoolOpt) flatten volumes created from snapshots to remove dependency" +msgstr "" + +#: ./doc/common/tables/cinder-storage_ceph.xml:30(td) +msgid "rbd_max_clone_depth = 5" +msgstr "" + +#: ./doc/common/tables/cinder-storage_ceph.xml:31(td) +msgid "(IntOpt) maximum number of nested clones that can be taken of a volume before enforcing a flatten prior to next clone. A value of zero disables cloning" +msgstr "" + +#: ./doc/common/tables/cinder-storage_ceph.xml:34(td) +msgid "rbd_pool = rbd" +msgstr "" + +#: ./doc/common/tables/cinder-storage_ceph.xml:43(td) +msgid "(StrOpt) the RADOS client name for accessing rbd volumes - only set when using cephx authentication" +msgstr "" + +#: ./doc/common/tables/cinder-storage_ceph.xml:46(td) +msgid "volume_tmp_dir = None" +msgstr "" + +#: ./doc/common/tables/cinder-storage_ceph.xml:47(td) +msgid "(StrOpt) where to store temporary image files if the volume driver does not write them directly to the volume" +msgstr "" + +#: ./doc/common/tables/nova-livemigration.xml:8(caption) +msgid "Description of configuration options for livemigration" +msgstr "" + +#: ./doc/common/tables/nova-livemigration.xml:22(td) +msgid "live_migration_retry_count = 30" +msgstr "" + +#: ./doc/common/tables/nova-livemigration.xml:23(td) +msgid "(IntOpt) Number of 1 second retries needed in live_migration" +msgstr "" + +#: ./doc/common/tables/nova-livemigration.xml:29(td) +msgid "live_migration_bandwidth = 0" +msgstr "" + +#: ./doc/common/tables/nova-livemigration.xml:30(td) +msgid "(IntOpt) Maximum bandwidth to be used during migration, in Mbps" +msgstr "" + +#: ./doc/common/tables/nova-livemigration.xml:33(td) +msgid "live_migration_flag = VIR_MIGRATE_UNDEFINE_SOURCE, VIR_MIGRATE_PEER2PEER" +msgstr "" + +#: ./doc/common/tables/nova-livemigration.xml:34(td) +msgid "(StrOpt) Migration flags to be set for live migration" +msgstr "" + +#: ./doc/common/tables/nova-livemigration.xml:37(td) +msgid "live_migration_uri = qemu+tcp://%s/system" +msgstr "" + +#: ./doc/common/tables/nova-livemigration.xml:38(td) +msgid "(StrOpt) Migration target URI (any included \"%s\" is replaced with the migration target hostname)" +msgstr "" + +#: ./doc/common/tables/nova-ldap.xml:8(caption) +msgid "Description of configuration options for ldap" +msgstr "" + +#: ./doc/common/tables/nova-ldap.xml:22(td) +msgid "ldap_dns_base_dn = ou=hosts,dc=example,dc=org" +msgstr "" + +#: ./doc/common/tables/nova-ldap.xml:23(td) +msgid "(StrOpt) Base DN for DNS entries in ldap" +msgstr "" + +#: ./doc/common/tables/nova-ldap.xml:26(td) +msgid "ldap_dns_password = password" +msgstr "" + +#: ./doc/common/tables/nova-ldap.xml:27(td) +msgid "(StrOpt) password for ldap DNS" +msgstr "" + +#: ./doc/common/tables/nova-ldap.xml:30(td) +msgid "ldap_dns_servers = ['dns.example.org']" +msgstr "" + +#: ./doc/common/tables/nova-ldap.xml:31(td) +msgid "(MultiStrOpt) DNS Servers for ldap dns driver" +msgstr "" + +#: ./doc/common/tables/nova-ldap.xml:34(td) +msgid "ldap_dns_soa_expiry = 86400" +msgstr "" + +#: ./doc/common/tables/nova-ldap.xml:35(td) +msgid "(StrOpt) Expiry interval (in seconds) for ldap dns driver Statement of Authority" +msgstr "" + +#: ./doc/common/tables/nova-ldap.xml:38(td) +msgid "ldap_dns_soa_hostmaster = hostmaster@example.org" +msgstr "" + +#: ./doc/common/tables/nova-ldap.xml:39(td) +msgid "(StrOpt) Hostmaster for ldap dns driver Statement of Authority" +msgstr "" + +#: ./doc/common/tables/nova-ldap.xml:42(td) +msgid "ldap_dns_soa_minimum = 7200" +msgstr "" + +#: ./doc/common/tables/nova-ldap.xml:43(td) +msgid "(StrOpt) Minimum interval (in seconds) for ldap dns driver Statement of Authority" +msgstr "" + +#: ./doc/common/tables/nova-ldap.xml:46(td) +msgid "ldap_dns_soa_refresh = 1800" +msgstr "" + +#: ./doc/common/tables/nova-ldap.xml:47(td) +msgid "(StrOpt) Refresh interval (in seconds) for ldap dns driver Statement of Authority" +msgstr "" + +#: ./doc/common/tables/nova-ldap.xml:50(td) +msgid "ldap_dns_soa_retry = 3600" +msgstr "" + +#: ./doc/common/tables/nova-ldap.xml:51(td) +msgid "(StrOpt) Retry interval (in seconds) for ldap dns driver Statement of Authority" +msgstr "" + +#: ./doc/common/tables/nova-ldap.xml:54(td) +msgid "ldap_dns_url = ldap://ldap.example.com:389" +msgstr "" + +#: ./doc/common/tables/nova-ldap.xml:55(td) +msgid "(StrOpt) URL for ldap server which will store dns entries" +msgstr "" + +#: ./doc/common/tables/nova-ldap.xml:58(td) +msgid "ldap_dns_user = uid=admin,ou=people,dc=example,dc=org" +msgstr "" + +#: ./doc/common/tables/nova-ldap.xml:59(td) +msgid "(StrOpt) user for ldap DNS" +msgstr "" + +#: ./doc/common/tables/nova-fping.xml:8(caption) +msgid "Description of configuration options for fping" +msgstr "" + +#: ./doc/common/tables/nova-fping.xml:22(td) +msgid "fping_path = /usr/sbin/fping" +msgstr "" + +#: ./doc/common/tables/nova-fping.xml:23(td) +msgid "(StrOpt) Full path to fping." +msgstr "" + +#: ./doc/common/tables/neutron-securitygroups.xml:8(caption) +msgid "Description of configuration options for securitygroups" +msgstr "" + +#: ./doc/common/tables/neutron-securitygroups.xml:19(td) +msgid "firewall_driver = neutron.agent.firewall.NoopFirewallDriver" +msgstr "" + +#: ./doc/common/tables/neutron-securitygroups.xml:20(td) +msgid "(StrOpt) Driver for Security Groups Firewall" +msgstr "" + +#: ./doc/common/tables/cinder-netapp_cdot_iscsi.xml:8(caption) +msgid "Description of configuration options for netapp_cdot_iscsi" +msgstr "" + +#: ./doc/common/tables/cinder-netapp_cdot_iscsi.xml:54(td) ./doc/common/tables/cinder-netapp_cdot_nfs.xml:54(td) +msgid "netapp_vserver = None" +msgstr "" + +#: ./doc/common/tables/cinder-netapp_cdot_iscsi.xml:55(td) ./doc/common/tables/cinder-netapp_cdot_nfs.xml:55(td) +msgid "(StrOpt) This option specifies the virtual storage server (Vserver) name on the storage cluster on which provisioning of block storage volumes should occur. If using the NFS storage protocol, this parameter is mandatory for storage service catalog support (utilized by Cinder volume type extra_specs support). If this option is specified, the exports belonging to the Vserver will only be used for provisioning in the future. Block storage volumes on exports not belonging to the Vserver specified by this option will continue to function normally." +msgstr "" + +#: ./doc/common/tables/nova-ec2.xml:8(caption) +msgid "Description of configuration options for ec2" +msgstr "" + +#: ./doc/common/tables/nova-ec2.xml:22(td) +msgid "ec2_dmz_host = $my_ip" +msgstr "" + +#: ./doc/common/tables/nova-ec2.xml:23(td) +msgid "(StrOpt) the internal ip of the ec2 api server" +msgstr "" + +#: ./doc/common/tables/nova-ec2.xml:26(td) +msgid "ec2_host = $my_ip" +msgstr "" + +#: ./doc/common/tables/nova-ec2.xml:27(td) +msgid "(StrOpt) the ip of the ec2 api server" +msgstr "" + +#: ./doc/common/tables/nova-ec2.xml:30(td) +msgid "ec2_listen = 0.0.0.0" +msgstr "" + +#: ./doc/common/tables/nova-ec2.xml:31(td) +msgid "(StrOpt) The IP address on which the EC2 API will listen." +msgstr "" + +#: ./doc/common/tables/nova-ec2.xml:34(td) +msgid "ec2_listen_port = 8773" +msgstr "" + +#: ./doc/common/tables/nova-ec2.xml:35(td) +msgid "(IntOpt) The port on which the EC2 API will listen." +msgstr "" + +#: ./doc/common/tables/nova-ec2.xml:38(td) +msgid "ec2_path = /services/Cloud" +msgstr "" + +#: ./doc/common/tables/nova-ec2.xml:39(td) +msgid "(StrOpt) the path prefix used to call the ec2 api server" +msgstr "" + +#: ./doc/common/tables/nova-ec2.xml:42(td) +msgid "ec2_port = 8773" +msgstr "" + +#: ./doc/common/tables/nova-ec2.xml:43(td) +msgid "(IntOpt) the port of the ec2 api server" +msgstr "" + +#: ./doc/common/tables/nova-ec2.xml:46(td) +msgid "ec2_private_dns_show_ip = False" +msgstr "" + +#: ./doc/common/tables/nova-ec2.xml:47(td) +msgid "(BoolOpt) Return the IP address as private dns hostname in describe instances" +msgstr "" + +#: ./doc/common/tables/nova-ec2.xml:50(td) +msgid "ec2_scheme = http" +msgstr "" + +#: ./doc/common/tables/nova-ec2.xml:51(td) +msgid "(StrOpt) the protocol to use when connecting to the ec2 api server (http, https)" +msgstr "" + +#: ./doc/common/tables/nova-ec2.xml:54(td) +msgid "ec2_strict_validation = True" +msgstr "" + +#: ./doc/common/tables/nova-ec2.xml:55(td) +msgid "(BoolOpt) Validate security group names according to EC2 specification" +msgstr "" + +#: ./doc/common/tables/nova-ec2.xml:58(td) +msgid "ec2_timestamp_expiry = 300" +msgstr "" + +#: ./doc/common/tables/nova-ec2.xml:59(td) +msgid "(IntOpt) Time in seconds before ec2 timestamp expires" +msgstr "" + +#: ./doc/common/tables/nova-ec2.xml:62(td) +msgid "ec2_workers = None" +msgstr "" + +#: ./doc/common/tables/nova-ec2.xml:63(td) +msgid "(IntOpt) Number of workers for EC2 API service" +msgstr "" + +#: ./doc/common/tables/nova-ec2.xml:66(td) +msgid "keystone_ec2_url = http://localhost:5000/v2.0/ec2tokens" +msgstr "" + +#: ./doc/common/tables/nova-ec2.xml:67(td) +msgid "(StrOpt) URL to get token from ec2 request." +msgstr "" + +#: ./doc/common/tables/nova-ec2.xml:70(td) +msgid "lockout_attempts = 5" +msgstr "" + +#: ./doc/common/tables/nova-ec2.xml:71(td) +msgid "(IntOpt) Number of failed auths before lockout." +msgstr "" + +#: ./doc/common/tables/nova-ec2.xml:74(td) +msgid "lockout_minutes = 15" +msgstr "" + +#: ./doc/common/tables/nova-ec2.xml:75(td) +msgid "(IntOpt) Number of minutes to lockout if triggered." +msgstr "" + +#: ./doc/common/tables/nova-ec2.xml:78(td) +msgid "lockout_window = 15" +msgstr "" + +#: ./doc/common/tables/nova-ec2.xml:79(td) +msgid "(IntOpt) Number of minutes for lockout window." +msgstr "" + +#: ./doc/common/tables/nova-ec2.xml:82(td) +msgid "region_list =" +msgstr "" + +#: ./doc/common/tables/nova-ec2.xml:83(td) +msgid "(ListOpt) list of region=fqdn pairs separated by commas" +msgstr "" + +#: ./doc/common/tables/swift-account-server-account-auditor.xml:7(literal) +msgid "[account-auditor]" +msgstr "" + +#: ./doc/common/tables/swift-account-server-account-auditor.xml:18(td) +msgid "log_name = account-auditor" +msgstr "" + +#: ./doc/common/tables/swift-account-server-account-auditor.xml:30(td) ./doc/common/tables/swift-container-server-container-auditor.xml:30(td) +msgid "interval = 1800" +msgstr "" + +#: ./doc/common/tables/swift-account-server-account-auditor.xml:39(td) +msgid "accounts_per_second = 200" +msgstr "" + +#: ./doc/common/tables/swift-account-server-account-auditor.xml:39(td) +msgid "Maximum accounts audited per second. Should be tuned according to individual system specs. 0 is unlimited." +msgstr "" + +#: ./doc/common/tables/swift-object-server-DEFAULT.xml:21(td) +msgid "bind_port = 6000" +msgstr "" + +#: ./doc/common/tables/swift-object-server-DEFAULT.xml:45(td) ./doc/common/tables/swift-proxy-server-DEFAULT.xml:55(td) +msgid "expiring_objects_container_divisor = 86400" +msgstr "" + +#: ./doc/common/tables/cinder-nexenta_nfs.xml:8(caption) +msgid "Description of configuration options for nexenta_nfs" +msgstr "" + +#: ./doc/common/tables/cinder-nexenta_nfs.xml:22(td) +msgid "nexenta_mount_options = None" +msgstr "" + +#: ./doc/common/tables/cinder-nexenta_nfs.xml:26(td) +msgid "nexenta_mount_point_base = $state_path/mnt" +msgstr "" + +#: ./doc/common/tables/cinder-nexenta_nfs.xml:27(td) +msgid "(StrOpt) Base dir containing mount points for nfs shares" +msgstr "" + +#: ./doc/common/tables/cinder-nexenta_nfs.xml:30(td) +msgid "nexenta_nms_cache_volroot = True" +msgstr "" + +#: ./doc/common/tables/cinder-nexenta_nfs.xml:31(td) +msgid "(BoolOpt) If set True cache NexentaStor appliance volroot option value." +msgstr "" + +#: ./doc/common/tables/cinder-nexenta_nfs.xml:34(td) +msgid "nexenta_oversub_ratio = 1.0" +msgstr "" + +#: ./doc/common/tables/cinder-nexenta_nfs.xml:38(td) +msgid "nexenta_shares_config = /etc/cinder/nfs_shares" +msgstr "" + +#: ./doc/common/tables/cinder-nexenta_nfs.xml:42(td) +msgid "nexenta_used_ratio = 0.95" +msgstr "" + +#: ./doc/common/tables/cinder-nexenta_nfs.xml:46(td) +msgid "nexenta_volume_compression = on" +msgstr "" + +#: ./doc/common/tables/cinder-nexenta_nfs.xml:47(td) +msgid "(StrOpt) Default compression value for new ZFS folders." +msgstr "" + +#: ./doc/common/tables/swift-proxy-server-filter-bulk.xml:7(literal) +msgid "[filter:bulk]" +msgstr "" + +#: ./doc/common/tables/swift-proxy-server-filter-bulk.xml:18(td) +msgid "use = egg:swift#bulk" +msgstr "" + +#: ./doc/common/tables/swift-proxy-server-filter-bulk.xml:21(td) +msgid "max_containers_per_extraction = 10000" +msgstr "" + +#: ./doc/common/tables/swift-proxy-server-filter-bulk.xml:24(td) +msgid "max_failed_extractions = 1000" +msgstr "" + +#: ./doc/common/tables/swift-proxy-server-filter-bulk.xml:27(td) +msgid "max_deletes_per_request = 10000" +msgstr "" + +#: ./doc/common/tables/swift-proxy-server-filter-bulk.xml:30(td) +msgid "yield_frequency = 60" +msgstr "" + +#: ./doc/common/tables/nova-policy.xml:22(td) +msgid "allow_instance_snapshots = True" +msgstr "" + +#: ./doc/common/tables/nova-policy.xml:23(td) +msgid "(BoolOpt) Permit instance snapshot operations." +msgstr "" + +#: ./doc/common/tables/nova-policy.xml:26(td) +msgid "allow_migrate_to_same_host = False" +msgstr "" + +#: ./doc/common/tables/nova-policy.xml:27(td) +msgid "(BoolOpt) Allow migrate machine to the same host. Useful when testing in single-host environments." +msgstr "" + +#: ./doc/common/tables/nova-policy.xml:30(td) +msgid "allow_resize_to_same_host = False" +msgstr "" + +#: ./doc/common/tables/nova-policy.xml:31(td) +msgid "(BoolOpt) Allow destination machine to match source for resize. Useful when testing in single-host environments." +msgstr "" + +#: ./doc/common/tables/nova-policy.xml:38(td) +msgid "max_local_block_devices = 3" +msgstr "" + +#: ./doc/common/tables/nova-policy.xml:39(td) +msgid "(IntOpt) Maximum number of devices that will result in a local image being created on the hypervisor node. Setting this to 0 means nova will allow only boot from volume. A negative number means unlimited." +msgstr "" + +#: ./doc/common/tables/nova-policy.xml:42(td) +msgid "osapi_compute_unique_server_name_scope =" +msgstr "" + +#: ./doc/common/tables/nova-policy.xml:43(td) +msgid "(StrOpt) When set, compute API will consider duplicate hostnames invalid within the specified scope, regardless of case. Should be empty, \"project\" or \"global\"." +msgstr "" + +#: ./doc/common/tables/nova-policy.xml:51(td) +msgid "(IntOpt) the maximum body size per each osapi request(bytes)" +msgstr "" + +#: ./doc/common/tables/nova-policy.xml:54(td) +msgid "password_length = 12" +msgstr "" + +#: ./doc/common/tables/nova-policy.xml:55(td) +msgid "(IntOpt) Length of generated instance admin passwords" +msgstr "" + +#: ./doc/common/tables/nova-policy.xml:59(td) ./doc/common/tables/cinder-common.xml:147(td) +msgid "(StrOpt) Rule checked when requested rule is not found" +msgstr "" + +#: ./doc/common/tables/nova-policy.xml:63(td) ./doc/common/tables/cinder-common.xml:151(td) +msgid "(StrOpt) JSON file representing policy" +msgstr "" + +#: ./doc/common/tables/nova-policy.xml:70(td) +msgid "resize_fs_using_block_device = False" +msgstr "" + +#: ./doc/common/tables/nova-policy.xml:71(td) +msgid "(BoolOpt) Attempt to resize the filesystem by accessing the image over a block device. This is done by the host and may not be necessary if the image contains a recent version of cloud-init. Possible mechanisms require the nbd driver (for qcow and raw), or loop (for raw)." +msgstr "" + +#: ./doc/common/tables/nova-policy.xml:74(td) ./doc/common/tables/cinder-common.xml:218(td) +msgid "until_refresh = 0" +msgstr "" + +#: ./doc/common/tables/nova-policy.xml:75(td) ./doc/common/tables/cinder-common.xml:219(td) +msgid "(IntOpt) count of reservations until usage is refreshed" +msgstr "" + +#: ./doc/common/tables/neutron-logging.xml:31(td) +msgid "instance_format = [instance: %(uuid)s]" +msgstr "" + +#: ./doc/common/tables/neutron-logging.xml:35(td) +msgid "instance_uuid_format = [instance: %(uuid)s]" +msgstr "" + +#: ./doc/common/tables/neutron-logging.xml:39(td) +msgid "log_config_append = None" +msgstr "" + +#: ./doc/common/tables/neutron-logging.xml:43(td) +msgid "log_date_format = %Y-%m-%d %H:%M:%S" +msgstr "" + +#: ./doc/common/tables/neutron-logging.xml:47(td) +msgid "log_dir = None" +msgstr "" + +#: ./doc/common/tables/neutron-logging.xml:51(td) +msgid "log_file = None" +msgstr "" + +#: ./doc/common/tables/neutron-logging.xml:55(td) +msgid "log_format = None" +msgstr "" + +#: ./doc/common/tables/neutron-logging.xml:79(td) +msgid "syslog_log_facility = LOG_USER" +msgstr "" + +#: ./doc/common/tables/neutron-logging.xml:87(td) +msgid "use_syslog = False" +msgstr "" + +#: ./doc/common/tables/glance-rpc.xml:22(td) +msgid "allowed_rpc_exception_modules = openstack.common.exception, glance.common.exception, exceptions" +msgstr "" + +#: ./doc/common/tables/nova-authentication.xml:8(caption) +msgid "Description of configuration options for authentication" +msgstr "" + +#: ./doc/common/tables/nova-authentication.xml:22(td) +msgid "api_rate_limit = False" +msgstr "" + +#: ./doc/common/tables/nova-authentication.xml:23(td) +msgid "(BoolOpt) whether to use per-user rate limiting for the api. This option is only used by v2 api. rate limiting is removed from v3 api." +msgstr "" + +#: ./doc/common/tables/nova-authentication.xml:26(td) ./doc/common/tables/glance-registry.xml:38(td) ./doc/common/tables/cinder-auth.xml:22(td) +msgid "auth_strategy = noauth" +msgstr "" + +#: ./doc/common/tables/nova-authentication.xml:27(td) +msgid "(StrOpt) The strategy to use for auth: noauth or keystone." +msgstr "" + +#: ./doc/common/tables/cinder-vmware.xml:8(caption) ./doc/common/tables/nova-vmware.xml:8(caption) +msgid "Description of configuration options for vmware" +msgstr "" + +#: ./doc/common/tables/cinder-vmware.xml:22(td) +msgid "vmware_api_retry_count = 10" +msgstr "" + +#: ./doc/common/tables/cinder-vmware.xml:23(td) +msgid "(IntOpt) Number of times VMware ESX/VC server API must be retried upon connection related issues." +msgstr "" + +#: ./doc/common/tables/cinder-vmware.xml:26(td) +msgid "vmware_host_ip = None" +msgstr "" + +#: ./doc/common/tables/cinder-vmware.xml:27(td) +msgid "(StrOpt) IP address for connecting to VMware ESX/VC server." +msgstr "" + +#: ./doc/common/tables/cinder-vmware.xml:30(td) +msgid "vmware_host_password = None" +msgstr "" + +#: ./doc/common/tables/cinder-vmware.xml:31(td) +msgid "(StrOpt) Password for authenticating with VMware ESX/VC server." +msgstr "" + +#: ./doc/common/tables/cinder-vmware.xml:34(td) +msgid "vmware_host_username = None" +msgstr "" + +#: ./doc/common/tables/cinder-vmware.xml:35(td) +msgid "(StrOpt) Username for authenticating with VMware ESX/VC server." +msgstr "" + +#: ./doc/common/tables/cinder-vmware.xml:38(td) +msgid "vmware_image_transfer_timeout_secs = 7200" +msgstr "" + +#: ./doc/common/tables/cinder-vmware.xml:39(td) +msgid "(IntOpt) Timeout in seconds for VMDK volume transfer between Cinder and Glance." +msgstr "" + +#: ./doc/common/tables/cinder-vmware.xml:42(td) +msgid "vmware_max_objects_retrieval = 100" +msgstr "" + +#: ./doc/common/tables/cinder-vmware.xml:43(td) +msgid "(IntOpt) Max number of objects to be retrieved per batch. Query results will be obtained in batches from the server and not in one shot. Server may still limit the count to something less than the configured value." +msgstr "" + +#: ./doc/common/tables/cinder-vmware.xml:46(td) +msgid "vmware_task_poll_interval = 5" +msgstr "" + +#: ./doc/common/tables/cinder-vmware.xml:47(td) +msgid "(IntOpt) The interval used for polling remote tasks invoked on VMware ESX/VC server." +msgstr "" + +#: ./doc/common/tables/cinder-vmware.xml:50(td) +msgid "vmware_volume_folder = cinder-volumes" +msgstr "" + +#: ./doc/common/tables/cinder-vmware.xml:51(td) +msgid "(StrOpt) Name for the folder in the VC datacenter that will contain cinder volumes." +msgstr "" + +#: ./doc/common/tables/cinder-vmware.xml:54(td) +msgid "vmware_wsdl_location = None" +msgstr "" + +#: ./doc/common/tables/cinder-vmware.xml:55(td) +msgid "(StrOpt) Optional VIM service WSDL Location e.g http://<server>/vimService.wsdl. Optional over-ride to default location for bug work-arounds." +msgstr "" + +#: ./doc/common/tables/glance-sheepdog.xml:8(caption) +msgid "Description of configuration options for sheepdog" +msgstr "" + +#: ./doc/common/tables/glance-sheepdog.xml:22(td) +msgid "sheepdog_store_address = localhost" +msgstr "" + +#: ./doc/common/tables/glance-sheepdog.xml:23(td) +msgid "(StrOpt) IP address of sheep daemon." +msgstr "" + +#: ./doc/common/tables/glance-sheepdog.xml:26(td) +msgid "sheepdog_store_chunk_size = 64" +msgstr "" + +#: ./doc/common/tables/glance-sheepdog.xml:27(td) +msgid "(IntOpt) Images will be chunked into objects of this size (in megabytes). For best performance, this should be a power of two." +msgstr "" + +#: ./doc/common/tables/glance-sheepdog.xml:30(td) +msgid "sheepdog_store_port = 7000" +msgstr "" + +#: ./doc/common/tables/glance-sheepdog.xml:31(td) +msgid "(IntOpt) Port of sheep daemon." +msgstr "" + +#: ./doc/common/tables/neutron-hyperv_agent.xml:8(caption) +msgid "Description of configuration options for hyperv_agent" +msgstr "" + +#: ./doc/common/tables/neutron-hyperv_agent.xml:19(td) +msgid "enable_metrics_collection = False" +msgstr "" + +#: ./doc/common/tables/neutron-hyperv_agent.xml:20(td) +msgid "(BoolOpt) Enables metrics collections for switch ports by using Hyper-V's metric APIs. Collected data can by retrieved by other apps and services, e.g.: Ceilometer. Requires Hyper-V / Windows Server 2012 and above" +msgstr "" + +#: ./doc/common/tables/neutron-hyperv_agent.xml:23(td) ./doc/common/tables/nova-hyperv.xml:30(td) +msgid "force_hyperv_utils_v1 = False" +msgstr "" + +#: ./doc/common/tables/neutron-hyperv_agent.xml:24(td) ./doc/common/tables/nova-hyperv.xml:31(td) +msgid "(BoolOpt) Force V1 WMI utility classes" +msgstr "" + +#: ./doc/common/tables/neutron-hyperv_agent.xml:27(td) +msgid "local_network_vswitch = private" +msgstr "" + +#: ./doc/common/tables/neutron-hyperv_agent.xml:28(td) +msgid "(StrOpt) Private vswitch name used for local networks" +msgstr "" + +#: ./doc/common/tables/neutron-hyperv_agent.xml:31(td) +msgid "physical_network_vswitch_mappings =" +msgstr "" + +#: ./doc/common/tables/neutron-hyperv_agent.xml:32(td) +msgid "(ListOpt) List of <physical_network>:<vswitch> where the physical networks can be expressed with wildcards, e.g.: .\"*:external\"" +msgstr "" + +#: ./doc/common/tables/neutron-hyperv_agent.xml:35(td) +msgid "polling_interval = 2" +msgstr "" + +#: ./doc/common/tables/neutron-hyperv_agent.xml:36(td) +msgid "(IntOpt) The number of seconds the agent will wait between polling for local device changes." +msgstr "" + +#: ./doc/common/tables/glance-swift.xml:8(caption) +msgid "Description of configuration options for swift" +msgstr "" + +#: ./doc/common/tables/glance-swift.xml:22(td) +msgid "swift_enable_snet = False" +msgstr "" + +#: ./doc/common/tables/glance-swift.xml:23(td) +msgid "(BoolOpt) Whether to use ServiceNET to communicate with the Swift storage servers." +msgstr "" + +#: ./doc/common/tables/glance-swift.xml:26(td) +msgid "swift_store_admin_tenants =" +msgstr "" + +#: ./doc/common/tables/glance-swift.xml:27(td) +msgid "(ListOpt) A list of tenants that will be granted read/write access on all Swift containers created by Glance in multi-tenant mode." +msgstr "" + +#: ./doc/common/tables/glance-swift.xml:30(td) +msgid "swift_store_auth_address = None" +msgstr "" + +#: ./doc/common/tables/glance-swift.xml:31(td) +msgid "(StrOpt) The address where the Swift authentication service is listening." +msgstr "" + +#: ./doc/common/tables/glance-swift.xml:34(td) +msgid "swift_store_auth_insecure = False" +msgstr "" + +#: ./doc/common/tables/glance-swift.xml:35(td) +msgid "(BoolOpt) If True, swiftclient won't check for a valid SSL certificate when authenticating." +msgstr "" + +#: ./doc/common/tables/glance-swift.xml:38(td) +msgid "swift_store_auth_version = 2" +msgstr "" + +#: ./doc/common/tables/glance-swift.xml:39(td) +msgid "(StrOpt) Version of the authentication service to use. Valid versions are 2 for keystone and 1 for swauth and rackspace" +msgstr "" + +#: ./doc/common/tables/glance-swift.xml:42(td) +msgid "swift_store_container = glance" +msgstr "" + +#: ./doc/common/tables/glance-swift.xml:43(td) +msgid "(StrOpt) Container within the account that the account should use for storing images in Swift." +msgstr "" + +#: ./doc/common/tables/glance-swift.xml:46(td) +msgid "swift_store_create_container_on_put = False" +msgstr "" + +#: ./doc/common/tables/glance-swift.xml:47(td) +msgid "(BoolOpt) A boolean value that determines if we create the container if it does not exist." +msgstr "" + +#: ./doc/common/tables/glance-swift.xml:50(td) +msgid "swift_store_endpoint_type = publicURL" +msgstr "" + +#: ./doc/common/tables/glance-swift.xml:51(td) +msgid "(StrOpt) A string giving the endpoint type of the swift service to use (publicURL, adminURL or internalURL). This setting is only used if swift_store_auth_version is 2." +msgstr "" + +#: ./doc/common/tables/glance-swift.xml:54(td) +msgid "swift_store_key = None" +msgstr "" + +#: ./doc/common/tables/glance-swift.xml:55(td) +msgid "(StrOpt) Auth key for the user authenticating against the Swift authentication service." +msgstr "" + +#: ./doc/common/tables/glance-swift.xml:58(td) +msgid "swift_store_large_object_chunk_size = 200" +msgstr "" + +#: ./doc/common/tables/glance-swift.xml:59(td) +msgid "(IntOpt) The amount of data written to a temporary disk buffer during the process of chunking the image file." +msgstr "" + +#: ./doc/common/tables/glance-swift.xml:62(td) +msgid "swift_store_large_object_size = 5120" +msgstr "" + +#: ./doc/common/tables/glance-swift.xml:63(td) +msgid "(IntOpt) The size, in MB, that Glance will start chunking image files and do a large object manifest in Swift" +msgstr "" + +#: ./doc/common/tables/glance-swift.xml:66(td) +msgid "swift_store_multi_tenant = False" +msgstr "" + +#: ./doc/common/tables/glance-swift.xml:67(td) +msgid "(BoolOpt) If set to True, enables multi-tenant storage mode which causes Glance images to be stored in tenant specific Swift accounts." +msgstr "" + +#: ./doc/common/tables/glance-swift.xml:70(td) +msgid "swift_store_region = None" +msgstr "" + +#: ./doc/common/tables/glance-swift.xml:71(td) +msgid "(StrOpt) The region of the swift endpoint to be used for single tenant. This setting is only necessary if the tenant has multiple swift endpoints." +msgstr "" + +#: ./doc/common/tables/glance-swift.xml:74(td) +msgid "swift_store_service_type = object-store" +msgstr "" + +#: ./doc/common/tables/glance-swift.xml:75(td) +msgid "(StrOpt) A string giving the service type of the swift service to use. This setting is only used if swift_store_auth_version is 2." +msgstr "" + +#: ./doc/common/tables/glance-swift.xml:78(td) +msgid "swift_store_ssl_compression = True" +msgstr "" + +#: ./doc/common/tables/glance-swift.xml:79(td) +msgid "(BoolOpt) If set to False, disables SSL layer compression of https swift requests. Setting to False may improve performance for images which are already in a compressed format, eg qcow2." +msgstr "" + +#: ./doc/common/tables/glance-swift.xml:82(td) +msgid "swift_store_user = None" +msgstr "" + +#: ./doc/common/tables/glance-swift.xml:83(td) +msgid "(StrOpt) The user to authenticate against the Swift authentication service" +msgstr "" + +#: ./doc/common/tables/swift-account-server-DEFAULT.xml:21(td) +msgid "bind_port = 6002" +msgstr "" + +#: ./doc/common/tables/neutron-bigswitch.xml:8(caption) +msgid "Description of configuration options for bigswitch" +msgstr "" + +#: ./doc/common/tables/neutron-bigswitch.xml:19(td) +msgid "add_meta_server_route = True" +msgstr "" + +#: ./doc/common/tables/neutron-bigswitch.xml:20(td) +msgid "(BoolOpt) Flag to decide if a route to the metadata server should be injected into the VM" +msgstr "" + +#: ./doc/common/tables/neutron-bigswitch.xml:23(td) +msgid "max_router_rules = 200" +msgstr "" + +#: ./doc/common/tables/neutron-bigswitch.xml:24(td) +msgid "(IntOpt) Maximum number of router rules" +msgstr "" + +#: ./doc/common/tables/neutron-bigswitch.xml:27(td) +msgid "neutron_id = neutron-[hostname]" +msgstr "" + +#: ./doc/common/tables/neutron-bigswitch.xml:28(td) +msgid "(StrOpt) User defined identifier for this Neutron deployment" +msgstr "" + +#: ./doc/common/tables/neutron-bigswitch.xml:31(td) +msgid "node_override_vif_802.1qbg =" +msgstr "" + +#: ./doc/common/tables/neutron-bigswitch.xml:32(td) +msgid "(ListOpt) Nova compute nodes to manually set VIF type to 802.1qbg" +msgstr "" + +#: ./doc/common/tables/neutron-bigswitch.xml:35(td) +msgid "node_override_vif_802.1qbh =" +msgstr "" + +#: ./doc/common/tables/neutron-bigswitch.xml:36(td) +msgid "(ListOpt) Nova compute nodes to manually set VIF type to 802.1qbh" +msgstr "" + +#: ./doc/common/tables/neutron-bigswitch.xml:39(td) +msgid "node_override_vif_binding_failed =" +msgstr "" + +#: ./doc/common/tables/neutron-bigswitch.xml:40(td) +msgid "(ListOpt) Nova compute nodes to manually set VIF type to binding_failed" +msgstr "" + +#: ./doc/common/tables/neutron-bigswitch.xml:43(td) +msgid "node_override_vif_bridge =" +msgstr "" + +#: ./doc/common/tables/neutron-bigswitch.xml:44(td) +msgid "(ListOpt) Nova compute nodes to manually set VIF type to bridge" +msgstr "" + +#: ./doc/common/tables/neutron-bigswitch.xml:47(td) +msgid "node_override_vif_hyperv =" +msgstr "" + +#: ./doc/common/tables/neutron-bigswitch.xml:48(td) +msgid "(ListOpt) Nova compute nodes to manually set VIF type to hyperv" +msgstr "" + +#: ./doc/common/tables/neutron-bigswitch.xml:51(td) +msgid "node_override_vif_ivs =" +msgstr "" + +#: ./doc/common/tables/neutron-bigswitch.xml:52(td) +msgid "(ListOpt) Nova compute nodes to manually set VIF type to ivs" +msgstr "" + +#: ./doc/common/tables/neutron-bigswitch.xml:55(td) +msgid "node_override_vif_midonet =" +msgstr "" + +#: ./doc/common/tables/neutron-bigswitch.xml:56(td) +msgid "(ListOpt) Nova compute nodes to manually set VIF type to midonet" +msgstr "" + +#: ./doc/common/tables/neutron-bigswitch.xml:59(td) +msgid "node_override_vif_other =" +msgstr "" + +#: ./doc/common/tables/neutron-bigswitch.xml:60(td) +msgid "(ListOpt) Nova compute nodes to manually set VIF type to other" +msgstr "" + +#: ./doc/common/tables/neutron-bigswitch.xml:63(td) +msgid "node_override_vif_ovs =" +msgstr "" + +#: ./doc/common/tables/neutron-bigswitch.xml:64(td) +msgid "(ListOpt) Nova compute nodes to manually set VIF type to ovs" +msgstr "" + +#: ./doc/common/tables/neutron-bigswitch.xml:67(td) +msgid "node_override_vif_unbound =" +msgstr "" + +#: ./doc/common/tables/neutron-bigswitch.xml:68(td) +msgid "(ListOpt) Nova compute nodes to manually set VIF type to unbound" +msgstr "" + +#: ./doc/common/tables/neutron-bigswitch.xml:71(td) +msgid "server_auth = username:password" +msgstr "" + +#: ./doc/common/tables/neutron-bigswitch.xml:72(td) +msgid "(StrOpt) The username and password for authenticating against the BigSwitch or Floodlight controller." +msgstr "" + +#: ./doc/common/tables/neutron-bigswitch.xml:75(td) +msgid "server_ssl = False" +msgstr "" + +#: ./doc/common/tables/neutron-bigswitch.xml:76(td) +msgid "(BoolOpt) If True, Use SSL when connecting to the BigSwitch or Floodlight controller." +msgstr "" + +#: ./doc/common/tables/neutron-bigswitch.xml:79(td) +msgid "server_timeout = 10" +msgstr "" + +#: ./doc/common/tables/neutron-bigswitch.xml:80(td) +msgid "(IntOpt) Maximum number of seconds to wait for proxy request to connect and complete." +msgstr "" + +#: ./doc/common/tables/neutron-bigswitch.xml:83(td) +msgid "servers = localhost:8800" +msgstr "" + +#: ./doc/common/tables/neutron-bigswitch.xml:84(td) +msgid "(StrOpt) A comma separated list of BigSwitch or Floodlight servers and port numbers. The plugin proxies the requests to the BigSwitch/Floodlight server, which performs the networking configuration. Note that only one server is needed per deployment, but you may wish to deploy multiple servers to support failover." +msgstr "" + +#: ./doc/common/tables/neutron-bigswitch.xml:87(td) +msgid "sync_data = False" +msgstr "" + +#: ./doc/common/tables/neutron-bigswitch.xml:88(td) +msgid "(BoolOpt) Sync data on connect" +msgstr "" + +#: ./doc/common/tables/neutron-bigswitch.xml:91(td) +msgid "tenant_default_router_rule = ['*:any:any:permit']" +msgstr "" + +#: ./doc/common/tables/neutron-bigswitch.xml:92(td) +msgid "(MultiStrOpt) The default router rules installed in new tenant routers. Repeat the config option for each rule. Format is <tenant>:<source>:<destination>:<action> Use an * to specify default for all tenants." +msgstr "" + +#: ./doc/common/tables/neutron-bigswitch.xml:95(td) +msgid "vif_type = ovs" +msgstr "" + +#: ./doc/common/tables/neutron-bigswitch.xml:96(td) +msgid "(StrOpt) Virtual interface type to configure on Nova compute nodes" +msgstr "" + +#: ./doc/common/tables/neutron-bigswitch.xml:99(td) +msgid "vif_types = unbound, binding_failed, ovs, ivs, bridge, 802.1qbg, 802.1qbh, hyperv, midonet, other" +msgstr "" + +#: ./doc/common/tables/neutron-bigswitch.xml:100(td) +msgid "(ListOpt) List of allowed vif_type values." +msgstr "" + +#: ./doc/common/tables/nova-libvirt.xml:8(caption) +msgid "Description of configuration options for libvirt" +msgstr "" + +#: ./doc/common/tables/nova-libvirt.xml:22(td) +msgid "remove_unused_base_images = True" +msgstr "" + +#: ./doc/common/tables/nova-libvirt.xml:23(td) +msgid "(BoolOpt) Should unused base images be removed?" +msgstr "" + +#: ./doc/common/tables/nova-libvirt.xml:26(td) +msgid "remove_unused_original_minimum_age_seconds = 86400" +msgstr "" + +#: ./doc/common/tables/nova-libvirt.xml:27(td) +msgid "(IntOpt) Unused unresized base images younger than this will not be removed" +msgstr "" + +#: ./doc/common/tables/nova-libvirt.xml:33(td) +msgid "checksum_base_images = False" +msgstr "" + +#: ./doc/common/tables/nova-libvirt.xml:34(td) +msgid "(BoolOpt) Write a checksum for files in _base to disk" +msgstr "" + +#: ./doc/common/tables/nova-libvirt.xml:37(td) +msgid "checksum_interval_seconds = 3600" +msgstr "" + +#: ./doc/common/tables/nova-libvirt.xml:38(td) +msgid "(IntOpt) How frequently to checksum base images" +msgstr "" + +#: ./doc/common/tables/nova-libvirt.xml:41(td) +msgid "connection_uri =" +msgstr "" + +#: ./doc/common/tables/nova-libvirt.xml:42(td) +msgid "(StrOpt) Override the default libvirt URI (which is dependent on virt_type)" +msgstr "" + +#: ./doc/common/tables/nova-libvirt.xml:45(td) +msgid "cpu_mode = None" +msgstr "" + +#: ./doc/common/tables/nova-libvirt.xml:46(td) +msgid "(StrOpt) Set to \"host-model\" to clone the host CPU feature flags; to \"host-passthrough\" to use the host CPU model exactly; to \"custom\" to use a named CPU model; to \"none\" to not set any CPU model. If virt_type=\"kvm|qemu\", it will default to \"host-model\", otherwise it will default to \"none\"" +msgstr "" + +#: ./doc/common/tables/nova-libvirt.xml:49(td) +msgid "cpu_model = None" +msgstr "" + +#: ./doc/common/tables/nova-libvirt.xml:50(td) +msgid "(StrOpt) Set to a named libvirt CPU model (see names listed in /usr/share/libvirt/cpu_map.xml). Only has effect if cpu_mode=\"custom\" and virt_type=\"kvm|qemu\"" +msgstr "" + +#: ./doc/common/tables/nova-libvirt.xml:53(td) +msgid "disk_prefix = None" +msgstr "" + +#: ./doc/common/tables/nova-libvirt.xml:54(td) +msgid "(StrOpt) Override the default disk prefix for the devices attached to a server, which is dependent on virt_type. (valid options are: sd, xvd, uvd, vd)" +msgstr "" + +#: ./doc/common/tables/nova-libvirt.xml:57(td) +msgid "image_info_filename_pattern = $instances_path/$image_cache_subdirectory_name/%(image)s.info" +msgstr "" + +#: ./doc/common/tables/nova-libvirt.xml:58(td) +msgid "(StrOpt) Allows image information files to be stored in non-standard locations" +msgstr "" + +#: ./doc/common/tables/nova-libvirt.xml:61(td) +msgid "remove_unused_kernels = False" +msgstr "" + +#: ./doc/common/tables/nova-libvirt.xml:62(td) +msgid "(BoolOpt) Should unused kernel images be removed? This is only safe to enable if all compute nodes have been updated to support this option. This will be enabled by default in future." +msgstr "" + +#: ./doc/common/tables/nova-libvirt.xml:65(td) +msgid "remove_unused_resized_minimum_age_seconds = 3600" +msgstr "" + +#: ./doc/common/tables/nova-libvirt.xml:66(td) +msgid "(IntOpt) Unused resized base images younger than this will not be removed" +msgstr "" + +#: ./doc/common/tables/nova-libvirt.xml:69(td) +msgid "snapshots_directory = $instances_path/snapshots" +msgstr "" + +#: ./doc/common/tables/nova-libvirt.xml:70(td) +msgid "(StrOpt) Location where libvirt driver will store snapshots before uploading them to image service" +msgstr "" + +#: ./doc/common/tables/nova-libvirt.xml:73(td) +msgid "vif_driver = nova.virt.libvirt.vif.LibvirtGenericVIFDriver" +msgstr "" + +#: ./doc/common/tables/nova-libvirt.xml:74(td) +msgid "(StrOpt) The libvirt VIF driver to configure the VIFs." +msgstr "" + +#: ./doc/common/tables/nova-libvirt.xml:77(td) +msgid "virt_type = kvm" +msgstr "" + +#: ./doc/common/tables/nova-libvirt.xml:78(td) +msgid "(StrOpt) Libvirt domain type (valid options are: kvm, lxc, qemu, uml, xen)" +msgstr "" + +#: ./doc/common/tables/nova-libvirt.xml:81(td) +msgid "volume_drivers = iscsi=nova.virt.libvirt.volume.LibvirtISCSIVolumeDriver, iser=nova.virt.libvirt.volume.LibvirtISERVolumeDriver, local=nova.virt.libvirt.volume.LibvirtVolumeDriver, fake=nova.virt.libvirt.volume.LibvirtFakeVolumeDriver, rbd=nova.virt.libvirt.volume.LibvirtNetVolumeDriver, sheepdog=nova.virt.libvirt.volume.LibvirtNetVolumeDriver, nfs=nova.virt.libvirt.volume.LibvirtNFSVolumeDriver, aoe=nova.virt.libvirt.volume.LibvirtAOEVolumeDriver, glusterfs=nova.virt.libvirt.volume.LibvirtGlusterfsVolumeDriver, fibre_channel=nova.virt.libvirt.volume.LibvirtFibreChannelVolumeDriver, scality=nova.virt.libvirt.volume.LibvirtScalityVolumeDriver" +msgstr "" + +#: ./doc/common/tables/nova-libvirt.xml:82(td) +msgid "(ListOpt) Libvirt handlers for remote volumes." +msgstr "" + +#: ./doc/common/tables/nova-libvirt.xml:85(td) +msgid "wait_soft_reboot_seconds = 120" +msgstr "" + +#: ./doc/common/tables/nova-libvirt.xml:86(td) +msgid "(IntOpt) Number of seconds to wait for instance to shut down after soft reboot request is made. We fall back to hard reboot if instance does not shutdown within this window." +msgstr "" + +#: ./doc/common/tables/neutron-lbaas.xml:8(caption) +msgid "Description of configuration options for lbaas" +msgstr "" + +#: ./doc/common/tables/neutron-lbaas.xml:19(td) +msgid "actions_to_skip = setup_l2_l3" +msgstr "" + +#: ./doc/common/tables/neutron-lbaas.xml:20(td) +msgid "(ListOpt) List of actions that we dont want to push to the completion queue" +msgstr "" + +#: ./doc/common/tables/neutron-lbaas.xml:23(td) +msgid "l2_l3_ctor_params = {'ha_ip_pool_name': 'default', 'allocate_ha_vrrp': True, 'ha_network_name': 'HA-Network', 'service': '_REPLACE_', 'allocate_ha_ips': True}" +msgstr "" + +#: ./doc/common/tables/neutron-lbaas.xml:24(td) +msgid "(DictOpt) l2_l3 workflow constructor params" +msgstr "" + +#: ./doc/common/tables/neutron-lbaas.xml:27(td) +msgid "l2_l3_setup_params = {'data_ip_address': '192.168.200.99', 'data_port': 1, 'gateway': '192.168.200.1', 'ha_port': 2, 'data_ip_mask': '255.255.255.0'}" +msgstr "" + +#: ./doc/common/tables/neutron-lbaas.xml:28(td) +msgid "(DictOpt) l2_l3 workflow setup params" +msgstr "" + +#: ./doc/common/tables/neutron-lbaas.xml:31(td) +msgid "l2_l3_workflow_name = openstack_l2_l3" +msgstr "" + +#: ./doc/common/tables/neutron-lbaas.xml:32(td) +msgid "(StrOpt) l2_l3 workflow name" +msgstr "" + +#: ./doc/common/tables/neutron-lbaas.xml:35(td) +msgid "l4_action_name = BaseCreate" +msgstr "" + +#: ./doc/common/tables/neutron-lbaas.xml:36(td) +msgid "(StrOpt) l4 workflow action name" +msgstr "" + +#: ./doc/common/tables/neutron-lbaas.xml:39(td) +msgid "l4_workflow_name = openstack_l4" +msgstr "" + +#: ./doc/common/tables/neutron-lbaas.xml:40(td) +msgid "(StrOpt) l4 workflow name" +msgstr "" + +#: ./doc/common/tables/neutron-lbaas.xml:43(td) +msgid "loadbalancer_pool_scheduler_driver = neutron.services.loadbalancer.agent_scheduler.ChanceScheduler" +msgstr "" + +#: ./doc/common/tables/neutron-lbaas.xml:44(td) +msgid "(StrOpt) Driver to use for scheduling pool to a default loadbalancer agent" +msgstr "" + +#: ./doc/common/tables/neutron-lbaas.xml:47(td) +msgid "loadbalancer_state_path = $state_path/lbaas" +msgstr "" + +#: ./doc/common/tables/neutron-lbaas.xml:48(td) +msgid "(StrOpt) Location to store config and state files" +msgstr "" + +#: ./doc/common/tables/neutron-lbaas.xml:51(td) +msgid "service_adc_type = VA" +msgstr "" + +#: ./doc/common/tables/neutron-lbaas.xml:52(td) +msgid "(StrOpt) Service ADC type" +msgstr "" + +#: ./doc/common/tables/neutron-lbaas.xml:55(td) +msgid "service_adc_version =" +msgstr "" + +#: ./doc/common/tables/neutron-lbaas.xml:56(td) +msgid "(StrOpt) Service ADC version" +msgstr "" + +#: ./doc/common/tables/neutron-lbaas.xml:59(td) +msgid "service_cache = 20" +msgstr "" + +#: ./doc/common/tables/neutron-lbaas.xml:60(td) +msgid "(IntOpt) service cache" +msgstr "" + +#: ./doc/common/tables/neutron-lbaas.xml:63(td) +msgid "service_compression_throughput = 100" +msgstr "" + +#: ./doc/common/tables/neutron-lbaas.xml:64(td) +msgid "(IntOpt) service compression throughtput" +msgstr "" + +#: ./doc/common/tables/neutron-lbaas.xml:67(td) +msgid "service_ha_pair = False" +msgstr "" + +#: ./doc/common/tables/neutron-lbaas.xml:68(td) +msgid "(BoolOpt) service HA pair" +msgstr "" + +#: ./doc/common/tables/neutron-lbaas.xml:71(td) +msgid "service_isl_vlan = -1" +msgstr "" + +#: ./doc/common/tables/neutron-lbaas.xml:72(td) +msgid "(IntOpt) A required VLAN for the interswitch link to use" +msgstr "" + +#: ./doc/common/tables/neutron-lbaas.xml:75(td) +msgid "service_resource_pool_ids =" +msgstr "" + +#: ./doc/common/tables/neutron-lbaas.xml:76(td) +msgid "(ListOpt) Resource pool ids" +msgstr "" + +#: ./doc/common/tables/neutron-lbaas.xml:79(td) +msgid "service_session_mirroring_enabled = False" +msgstr "" + +#: ./doc/common/tables/neutron-lbaas.xml:80(td) +msgid "(BoolOpt) Support an Alteon interswitch link for stateful session failover" +msgstr "" + +#: ./doc/common/tables/neutron-lbaas.xml:83(td) +msgid "service_ssl_throughput = 100" +msgstr "" + +#: ./doc/common/tables/neutron-lbaas.xml:84(td) +msgid "(IntOpt) service ssl throughtput" +msgstr "" + +#: ./doc/common/tables/neutron-lbaas.xml:87(td) +msgid "service_throughput = 1000" +msgstr "" + +#: ./doc/common/tables/neutron-lbaas.xml:88(td) +msgid "(IntOpt) service throughtput" +msgstr "" + +#: ./doc/common/tables/neutron-lbaas.xml:91(td) +msgid "user_group = nogroup" +msgstr "" + +#: ./doc/common/tables/neutron-lbaas.xml:92(td) +msgid "(StrOpt) The user group" +msgstr "" + +#: ./doc/common/tables/neutron-lbaas.xml:95(td) +msgid "vdirect_address = None" +msgstr "" + +#: ./doc/common/tables/neutron-lbaas.xml:96(td) +msgid "(StrOpt) vdirect server IP address" +msgstr "" + +#: ./doc/common/tables/neutron-lbaas.xml:99(td) +msgid "vdirect_password = radware" +msgstr "" + +#: ./doc/common/tables/neutron-lbaas.xml:100(td) +msgid "(StrOpt) vdirect user password" +msgstr "" + +#: ./doc/common/tables/neutron-lbaas.xml:103(td) +msgid "vdirect_user = vDirect" +msgstr "" + +#: ./doc/common/tables/neutron-lbaas.xml:104(td) +msgid "(StrOpt) vdirect user name" +msgstr "" + +#: ./doc/common/tables/cinder-backups_swift.xml:8(caption) +msgid "Description of configuration options for backups_swift" +msgstr "" + +#: ./doc/common/tables/cinder-backups_swift.xml:22(td) +msgid "backup_swift_auth = per_user" +msgstr "" + +#: ./doc/common/tables/cinder-backups_swift.xml:23(td) +msgid "(StrOpt) Swift authentication mechanism" +msgstr "" + +#: ./doc/common/tables/cinder-backups_swift.xml:26(td) +msgid "backup_swift_container = volumebackups" +msgstr "" + +#: ./doc/common/tables/cinder-backups_swift.xml:27(td) +msgid "(StrOpt) The default Swift container to use" +msgstr "" + +#: ./doc/common/tables/cinder-backups_swift.xml:30(td) +msgid "backup_swift_key = None" +msgstr "" + +#: ./doc/common/tables/cinder-backups_swift.xml:31(td) +msgid "(StrOpt) Swift key for authentication" +msgstr "" + +#: ./doc/common/tables/cinder-backups_swift.xml:34(td) +msgid "backup_swift_object_size = 52428800" +msgstr "" + +#: ./doc/common/tables/cinder-backups_swift.xml:35(td) +msgid "(IntOpt) The size in bytes of Swift backup objects" +msgstr "" + +#: ./doc/common/tables/cinder-backups_swift.xml:38(td) +msgid "backup_swift_retry_attempts = 3" +msgstr "" + +#: ./doc/common/tables/cinder-backups_swift.xml:39(td) +msgid "(IntOpt) The number of retries to make for Swift operations" +msgstr "" + +#: ./doc/common/tables/cinder-backups_swift.xml:42(td) +msgid "backup_swift_retry_backoff = 2" +msgstr "" + +#: ./doc/common/tables/cinder-backups_swift.xml:43(td) +msgid "(IntOpt) The backoff time in seconds between Swift retries" +msgstr "" + +#: ./doc/common/tables/cinder-backups_swift.xml:46(td) +msgid "backup_swift_url = http://localhost:8080/v1/AUTH_" +msgstr "" + +#: ./doc/common/tables/cinder-backups_swift.xml:47(td) +msgid "(StrOpt) The URL of the Swift endpoint" +msgstr "" + +#: ./doc/common/tables/cinder-backups_swift.xml:50(td) +msgid "backup_swift_user = None" +msgstr "" + +#: ./doc/common/tables/cinder-backups_swift.xml:51(td) +msgid "(StrOpt) Swift user name" +msgstr "" + +#: ./doc/common/tables/neutron-ml2_cisco.xml:8(caption) +msgid "Description of configuration options for ml2_cisco" +msgstr "" + +#: ./doc/common/tables/neutron-ml2_cisco.xml:19(td) +msgid "managed_physical_network = None" +msgstr "" + +#: ./doc/common/tables/neutron-ml2_cisco.xml:20(td) +msgid "(StrOpt) The physical network managed by the switches." +msgstr "" + +#: ./doc/common/tables/nova-pci.xml:8(caption) +msgid "Description of configuration options for pci" +msgstr "" + +#: ./doc/common/tables/nova-pci.xml:22(td) +msgid "pci_alias = []" +msgstr "" + +#: ./doc/common/tables/nova-pci.xml:23(td) +msgid "(MultiStrOpt) An alias for a PCI passthrough device requirement. This allows users to specify the alias in the extra_spec for a flavor, without needing to repeat all the PCI property requirements. For example: pci_alias = { \"name\": \"QuicAssist\", \"product_id\": \"0443\", \"vendor_id\": \"8086\", \"device_type\": \"ACCEL\" } defines an alias for the Intel QuickAssist card. (multi valued)" +msgstr "" + +#: ./doc/common/tables/nova-pci.xml:26(td) +msgid "pci_passthrough_whitelist = []" +msgstr "" + +#: ./doc/common/tables/nova-pci.xml:27(td) +msgid "(MultiStrOpt) White list of PCI devices available to VMs. For example: pci_passthrough_whitelist = [{\"vendor_id\": \"8086\", \"product_id\": \"0443\"}]" +msgstr "" + +#: ./doc/common/tables/swift-proxy-server-filter-proxy-logging.xml:7(literal) +msgid "[filter:proxy-logging]" +msgstr "" + +#: ./doc/common/tables/swift-proxy-server-filter-proxy-logging.xml:18(td) +msgid "use = egg:swift#proxy_logging" +msgstr "" + +#: ./doc/common/tables/swift-proxy-server-filter-proxy-logging.xml:21(td) +msgid "access_log_name = swift" +msgstr "" + +#: ./doc/common/tables/swift-proxy-server-filter-proxy-logging.xml:24(td) +msgid "access_log_facility = LOG_LOCAL0" +msgstr "" + +#: ./doc/common/tables/swift-proxy-server-filter-proxy-logging.xml:27(td) +msgid "access_log_level = INFO" +msgstr "" + +#: ./doc/common/tables/swift-proxy-server-filter-proxy-logging.xml:30(td) +msgid "access_log_address = /dev/log" +msgstr "" + +#: ./doc/common/tables/swift-proxy-server-filter-proxy-logging.xml:33(td) +msgid "access_log_udp_host =" +msgstr "" + +#: ./doc/common/tables/swift-proxy-server-filter-proxy-logging.xml:36(td) +msgid "access_log_udp_port = 514" +msgstr "" + +#: ./doc/common/tables/swift-proxy-server-filter-proxy-logging.xml:39(td) +msgid "access_log_statsd_host = localhost" +msgstr "" + +#: ./doc/common/tables/swift-proxy-server-filter-proxy-logging.xml:42(td) +msgid "access_log_statsd_port = 8125" +msgstr "" + +#: ./doc/common/tables/swift-proxy-server-filter-proxy-logging.xml:45(td) +msgid "access_log_statsd_default_sample_rate = 1.0" +msgstr "" + +#: ./doc/common/tables/swift-proxy-server-filter-proxy-logging.xml:48(td) +msgid "access_log_statsd_sample_rate_factor = 1.0" +msgstr "" + +#: ./doc/common/tables/swift-proxy-server-filter-proxy-logging.xml:51(td) +msgid "access_log_statsd_metric_prefix =" +msgstr "" + +#: ./doc/common/tables/swift-proxy-server-filter-proxy-logging.xml:54(td) +msgid "access_log_headers = false" +msgstr "" + +#: ./doc/common/tables/swift-proxy-server-filter-proxy-logging.xml:57(td) +msgid "logged with access_log_headers = True." +msgstr "" + +#: ./doc/common/tables/swift-proxy-server-filter-proxy-logging.xml:60(td) +msgid "reveal_sensitive_prefix = 8192" +msgstr "" + +#: ./doc/common/tables/swift-proxy-server-filter-proxy-logging.xml:60(td) +msgid "The X-Auth-Token is sensitive data. If revealed to an unauthorised person, they can now make requests against an account until the token expires. Set reveal_sensitive_prefix to the number of characters of the token that are logged. For example reveal_sensitive_prefix = 12 so only first 12 characters of the token are logged. Or, set to 0 to completely remove the token." +msgstr "" + +#: ./doc/common/tables/swift-proxy-server-filter-proxy-logging.xml:69(td) +msgid "log_statsd_valid_http_methods = GET,HEAD,POST,PUT,DELETE,COPY,OPTIONS" +msgstr "" + +#: ./doc/common/tables/neutron-varmour.xml:8(caption) +msgid "Description of configuration options for varmour" +msgstr "" + +#: ./doc/common/tables/neutron-varmour.xml:19(td) +msgid "director = localhost" +msgstr "" + +#: ./doc/common/tables/neutron-varmour.xml:20(td) +msgid "(StrOpt) vArmour director ip" +msgstr "" + +#: ./doc/common/tables/neutron-varmour.xml:23(td) +msgid "director_port = 443" +msgstr "" + +#: ./doc/common/tables/neutron-varmour.xml:24(td) +msgid "(StrOpt) vArmour director port" +msgstr "" + +#: ./doc/common/tables/neutron-varmour.xml:27(td) +msgid "password = varmour" +msgstr "" + +#: ./doc/common/tables/neutron-varmour.xml:28(td) +msgid "(StrOpt) vArmour director password" +msgstr "" + +#: ./doc/common/tables/glance-imagecache.xml:8(caption) +msgid "Description of configuration options for imagecache" +msgstr "" + +#: ./doc/common/tables/glance-imagecache.xml:22(td) +msgid "cleanup_scrubber = False" +msgstr "" + +#: ./doc/common/tables/glance-imagecache.xml:23(td) +msgid "(BoolOpt) A boolean that determines if the scrubber should clean up the files it uses for taking data. Only one server in your deployment should be designated the cleanup host." +msgstr "" + +#: ./doc/common/tables/glance-imagecache.xml:26(td) +msgid "cleanup_scrubber_time = 86400" +msgstr "" + +#: ./doc/common/tables/glance-imagecache.xml:27(td) +msgid "(IntOpt) Items must have a modified time that is older than this value in order to be candidates for cleanup." +msgstr "" + +#: ./doc/common/tables/glance-imagecache.xml:30(td) +msgid "delayed_delete = False" +msgstr "" + +#: ./doc/common/tables/glance-imagecache.xml:31(td) +msgid "(BoolOpt) Turn on/off delayed delete." +msgstr "" + +#: ./doc/common/tables/glance-imagecache.xml:34(td) +msgid "image_cache_dir = None" +msgstr "" + +#: ./doc/common/tables/glance-imagecache.xml:35(td) +msgid "(StrOpt) Base directory that the Image Cache uses." +msgstr "" + +#: ./doc/common/tables/glance-imagecache.xml:38(td) +msgid "image_cache_driver = sqlite" +msgstr "" + +#: ./doc/common/tables/glance-imagecache.xml:39(td) +msgid "(StrOpt) The driver to use for image cache management." +msgstr "" + +#: ./doc/common/tables/glance-imagecache.xml:42(td) +msgid "image_cache_max_size = 10737418240" +msgstr "" + +#: ./doc/common/tables/glance-imagecache.xml:43(td) +msgid "(IntOpt) The maximum size in bytes that the cache can use." +msgstr "" + +#: ./doc/common/tables/glance-imagecache.xml:46(td) +msgid "image_cache_sqlite_db = cache.db" +msgstr "" + +#: ./doc/common/tables/glance-imagecache.xml:47(td) +msgid "(StrOpt) The path to the sqlite file database that will be used for image cache management." +msgstr "" + +#: ./doc/common/tables/glance-imagecache.xml:50(td) +msgid "image_cache_stall_time = 86400" +msgstr "" + +#: ./doc/common/tables/glance-imagecache.xml:51(td) +msgid "(IntOpt) The amount of time to let an image remain in the cache without being accessed" +msgstr "" + +#: ./doc/common/tables/glance-imagecache.xml:54(td) +msgid "scrub_time = 0" +msgstr "" + +#: ./doc/common/tables/glance-imagecache.xml:55(td) +msgid "(IntOpt) The amount of time in seconds to delay before performing a delete." +msgstr "" + +#: ./doc/common/tables/glance-imagecache.xml:58(td) +msgid "scrubber_datadir = /var/lib/glance/scrubber" +msgstr "" + +#: ./doc/common/tables/glance-imagecache.xml:59(td) +msgid "(StrOpt) Directory that the scrubber will use to track information about what to delete. Make sure this is set in glance-api.conf and glance-scrubber.conf" +msgstr "" + +#: ./doc/common/tables/swift-rsyncd-account.xml:7(literal) +msgid "[account]" +msgstr "" + +#: ./doc/common/tables/swift-rsyncd-account.xml:18(td) +msgid "max connections = 2" +msgstr "" + +#: ./doc/common/tables/swift-rsyncd-account.xml:27(td) +msgid "lock file = /var/lock/account.lock" +msgstr "" + +#: ./doc/common/tables/cinder-storage.xml:8(caption) +msgid "Description of configuration options for storage" +msgstr "" + +#: ./doc/common/tables/cinder-storage.xml:22(td) +msgid "allocated_capacity_weight_multiplier = -1.0" +msgstr "" + +#: ./doc/common/tables/cinder-storage.xml:23(td) ./doc/common/tables/cinder-storage.xml:31(td) +msgid "(FloatOpt) Multiplier used for weighing volume capacity. Negative numbers mean to stack vs spread." +msgstr "" + +#: ./doc/common/tables/cinder-storage.xml:26(td) +msgid "bindir = $pybasedir/bin" +msgstr "" + +#: ./doc/common/tables/cinder-storage.xml:27(td) +msgid "(StrOpt) Directory where cinder binaries are installed" +msgstr "" + +#: ./doc/common/tables/cinder-storage.xml:30(td) +msgid "capacity_weight_multiplier = 1.0" +msgstr "" + +#: ./doc/common/tables/cinder-storage.xml:34(td) +msgid "enabled_backends = None" +msgstr "" + +#: ./doc/common/tables/cinder-storage.xml:35(td) +msgid "(ListOpt) A list of backend names to use. These backend names should be backed by a unique [CONFIG] group with its options" +msgstr "" + +#: ./doc/common/tables/cinder-storage.xml:38(td) +msgid "iscsi_helper = tgtadm" +msgstr "" + +#: ./doc/common/tables/cinder-storage.xml:39(td) +msgid "(StrOpt) iscsi target user-land tool to use" +msgstr "" + +#: ./doc/common/tables/cinder-storage.xml:42(td) +msgid "iscsi_iotype = fileio" +msgstr "" + +#: ./doc/common/tables/cinder-storage.xml:43(td) +msgid "(StrOpt) Sets the behavior of the iSCSI target to either perform blockio or fileio optionally, auto can be set and Cinder will autodetect type of backing device" +msgstr "" + +#: ./doc/common/tables/cinder-storage.xml:46(td) +msgid "iscsi_ip_address = $my_ip" +msgstr "" + +#: ./doc/common/tables/cinder-storage.xml:47(td) +msgid "(StrOpt) The IP address that the iSCSI daemon is listening on" +msgstr "" + +#: ./doc/common/tables/cinder-storage.xml:50(td) +msgid "iscsi_num_targets = 100" +msgstr "" + +#: ./doc/common/tables/cinder-storage.xml:51(td) +msgid "(IntOpt) The maximum number of iscsi target ids per host" +msgstr "" + +#: ./doc/common/tables/cinder-storage.xml:54(td) +msgid "iscsi_port = 3260" +msgstr "" + +#: ./doc/common/tables/cinder-storage.xml:55(td) +msgid "(IntOpt) The port that the iSCSI daemon is listening on" +msgstr "" + +#: ./doc/common/tables/cinder-storage.xml:58(td) +msgid "iscsi_target_prefix = iqn.2010-10.org.openstack:" +msgstr "" + +#: ./doc/common/tables/cinder-storage.xml:59(td) +msgid "(StrOpt) prefix for iscsi volumes" +msgstr "" + +#: ./doc/common/tables/cinder-storage.xml:62(td) +msgid "iser_helper = tgtadm" +msgstr "" + +#: ./doc/common/tables/cinder-storage.xml:63(td) +msgid "(StrOpt) iser target user-land tool to use" +msgstr "" + +#: ./doc/common/tables/cinder-storage.xml:66(td) +msgid "iser_ip_address = $my_ip" +msgstr "" + +#: ./doc/common/tables/cinder-storage.xml:67(td) +msgid "(StrOpt) The IP address that the iSER daemon is listening on" +msgstr "" + +#: ./doc/common/tables/cinder-storage.xml:70(td) +msgid "iser_num_targets = 100" +msgstr "" + +#: ./doc/common/tables/cinder-storage.xml:71(td) +msgid "(IntOpt) The maximum number of iser target ids per host" +msgstr "" + +#: ./doc/common/tables/cinder-storage.xml:74(td) +msgid "iser_port = 3260" +msgstr "" + +#: ./doc/common/tables/cinder-storage.xml:75(td) +msgid "(IntOpt) The port that the iSER daemon is listening on" +msgstr "" + +#: ./doc/common/tables/cinder-storage.xml:78(td) +msgid "iser_target_prefix = iqn.2010-10.org.iser.openstack:" +msgstr "" + +#: ./doc/common/tables/cinder-storage.xml:79(td) +msgid "(StrOpt) prefix for iser volumes" +msgstr "" + +#: ./doc/common/tables/cinder-storage.xml:82(td) +msgid "max_gigabytes = 10000" +msgstr "" + +#: ./doc/common/tables/cinder-storage.xml:83(td) +msgid "(IntOpt) This configure option has been deprecated along with the SimpleScheduler. New scheduler is able to gather capacity information for each host, thus setting the maximum number of volume gigabytes for host is no longer needed. It's safe to remove this configure from cinder.conf." +msgstr "" + +#: ./doc/common/tables/cinder-storage.xml:86(td) +msgid "migration_create_volume_timeout_secs = 300" +msgstr "" + +#: ./doc/common/tables/cinder-storage.xml:87(td) +msgid "(IntOpt) Timeout for creating the volume to migrate to when performing volume migration (seconds)" +msgstr "" + +#: ./doc/common/tables/cinder-storage.xml:91(td) +msgid "(IntOpt) The maximum number of times to rescan iSER targetto find volume" +msgstr "" + +#: ./doc/common/tables/cinder-storage.xml:94(td) +msgid "num_volume_device_scan_tries = 3" +msgstr "" + +#: ./doc/common/tables/cinder-storage.xml:95(td) +msgid "(IntOpt) The maximum number of times to rescan targets to find volume" +msgstr "" + +#: ./doc/common/tables/cinder-storage.xml:98(td) +msgid "volume_backend_name = None" +msgstr "" + +#: ./doc/common/tables/cinder-storage.xml:99(td) +msgid "(StrOpt) The backend name for a given driver implementation" +msgstr "" + +#: ./doc/common/tables/cinder-storage.xml:102(td) +msgid "volume_clear = zero" +msgstr "" + +#: ./doc/common/tables/cinder-storage.xml:103(td) +msgid "(StrOpt) Method used to wipe old voumes (valid options are: none, zero, shred)" +msgstr "" + +#: ./doc/common/tables/cinder-storage.xml:106(td) +msgid "volume_clear_size = 0" +msgstr "" + +#: ./doc/common/tables/cinder-storage.xml:107(td) +msgid "(IntOpt) Size in MiB to wipe at start of old volumes. 0 => all" +msgstr "" + +#: ./doc/common/tables/cinder-storage.xml:110(td) +msgid "volume_dd_blocksize = 1M" +msgstr "" + +#: ./doc/common/tables/cinder-storage.xml:111(td) +msgid "(StrOpt) The default block size used when copying/clearing volumes" +msgstr "" + +#: ./doc/common/tables/cinder-storage.xml:114(td) +msgid "volume_driver = cinder.volume.drivers.lvm.LVMISCSIDriver" +msgstr "" + +#: ./doc/common/tables/cinder-storage.xml:115(td) +msgid "(StrOpt) Driver to use for volume creation" +msgstr "" + +#: ./doc/common/tables/cinder-storage.xml:118(td) +msgid "volume_manager = cinder.volume.manager.VolumeManager" +msgstr "" + +#: ./doc/common/tables/cinder-storage.xml:119(td) +msgid "(StrOpt) full class name for the Manager for volume" +msgstr "" + +#: ./doc/common/tables/cinder-storage.xml:122(td) +msgid "volume_service_inithost_offload = False" +msgstr "" + +#: ./doc/common/tables/cinder-storage.xml:123(td) +msgid "(BoolOpt) Offload pending volume delete during volume service startup" +msgstr "" + +#: ./doc/common/tables/cinder-storage.xml:126(td) +msgid "volume_usage_audit_period = month" +msgstr "" + +#: ./doc/common/tables/cinder-storage.xml:127(td) +msgid "(StrOpt) time period to generate volume usages for. Time period must be hour, day, month or year" +msgstr "" + +#: ./doc/common/tables/cinder-storage.xml:130(td) +msgid "volumes_dir = $state_path/volumes" +msgstr "" + +#: ./doc/common/tables/cinder-storage.xml:131(td) +msgid "(StrOpt) Volume configuration file storage directory" +msgstr "" + +#: ./doc/common/tables/cinder-storage.xml:134(td) +msgid "zadara_default_stripesize = 64" +msgstr "" + +#: ./doc/common/tables/cinder-storage.xml:135(td) +msgid "(StrOpt) Default stripe size for volumes" +msgstr "" + +#: ./doc/common/tables/cinder-storage.xml:149(td) +msgid "max_pool_size = 5" +msgstr "" + +#: ./doc/common/tables/nova-vpn.xml:8(caption) ./doc/common/tables/neutron-vpn.xml:8(caption) +msgid "Description of configuration options for vpn" +msgstr "" + +#: ./doc/common/tables/nova-vpn.xml:22(td) +msgid "boot_script_template = $pybasedir/nova/cloudpipe/bootscript.template" +msgstr "" + +#: ./doc/common/tables/nova-vpn.xml:23(td) +msgid "(StrOpt) Template for cloudpipe instance boot script" +msgstr "" + +#: ./doc/common/tables/nova-vpn.xml:26(td) +msgid "dmz_cidr =" +msgstr "" + +#: ./doc/common/tables/nova-vpn.xml:27(td) +msgid "(ListOpt) A list of dmz range that should be accepted" +msgstr "" + +#: ./doc/common/tables/nova-vpn.xml:30(td) +msgid "dmz_mask = 255.255.255.0" +msgstr "" + +#: ./doc/common/tables/nova-vpn.xml:31(td) +msgid "(StrOpt) Netmask to push into openvpn config" +msgstr "" + +#: ./doc/common/tables/nova-vpn.xml:34(td) +msgid "dmz_net = 10.0.0.0" +msgstr "" + +#: ./doc/common/tables/nova-vpn.xml:35(td) +msgid "(StrOpt) Network to push into openvpn config" +msgstr "" + +#: ./doc/common/tables/nova-vpn.xml:38(td) +msgid "vpn_flavor = m1.tiny" +msgstr "" + +#: ./doc/common/tables/nova-vpn.xml:39(td) +msgid "(StrOpt) Flavor for vpn instances" +msgstr "" + +#: ./doc/common/tables/nova-vpn.xml:42(td) +msgid "vpn_image_id = 0" +msgstr "" + +#: ./doc/common/tables/nova-vpn.xml:43(td) +msgid "(StrOpt) image id used when starting up a cloudpipe vpn server" +msgstr "" + +#: ./doc/common/tables/nova-vpn.xml:46(td) +msgid "vpn_ip = $my_ip" +msgstr "" + +#: ./doc/common/tables/nova-vpn.xml:47(td) +msgid "(StrOpt) Public IP for the cloudpipe VPN servers" +msgstr "" + +#: ./doc/common/tables/nova-vpn.xml:50(td) +msgid "vpn_key_suffix = -vpn" +msgstr "" + +#: ./doc/common/tables/nova-vpn.xml:51(td) +msgid "(StrOpt) Suffix to add to project name for vpn key and secgroups" +msgstr "" + +#: ./doc/common/tables/nova-vpn.xml:54(td) +msgid "vpn_start = 1000" +msgstr "" + +#: ./doc/common/tables/nova-vpn.xml:55(td) +msgid "(IntOpt) First Vpn port for private networks" +msgstr "" + +#: ./doc/common/tables/nova-wsgi.xml:23(td) +msgid "(StrOpt) File name for the paste.deploy config for nova-api" +msgstr "" + +#: ./doc/common/tables/nova-wsgi.xml:26(td) ./doc/common/tables/cinder-common.xml:190(td) ./doc/common/tables/neutron-ssl.xml:23(td) +msgid "ssl_ca_file = None" +msgstr "" + +#: ./doc/common/tables/nova-wsgi.xml:30(td) ./doc/common/tables/cinder-common.xml:194(td) ./doc/common/tables/neutron-ssl.xml:27(td) +msgid "ssl_cert_file = None" +msgstr "" + +#: ./doc/common/tables/nova-wsgi.xml:31(td) +msgid "(StrOpt) SSL certificate of API server" +msgstr "" + +#: ./doc/common/tables/nova-wsgi.xml:34(td) ./doc/common/tables/cinder-common.xml:198(td) ./doc/common/tables/neutron-ssl.xml:31(td) +msgid "ssl_key_file = None" +msgstr "" + +#: ./doc/common/tables/nova-wsgi.xml:35(td) +msgid "(StrOpt) SSL private key of API server" +msgstr "" + +#: ./doc/common/tables/nova-wsgi.xml:42(td) +msgid "wsgi_default_pool_size = 1000" +msgstr "" + +#: ./doc/common/tables/nova-wsgi.xml:43(td) +msgid "(IntOpt) Size of the pool of greenthreads used by wsgi" +msgstr "" + +#: ./doc/common/tables/nova-wsgi.xml:46(td) +msgid "wsgi_log_format = %(client_ip)s \"%(request_line)s\" status: %(status_code)s len: %(body_length)s time: %(wall_seconds).7f" +msgstr "" + +#: ./doc/common/tables/nova-wsgi.xml:47(td) +msgid "(StrOpt) A python format string that is used as the template to generate log lines. The following values can be formatted into it: client_ip, date_time, request_line, status_code, body_length, wall_seconds." +msgstr "" + +#: ./doc/common/tables/cinder-storage_glusterfs.xml:8(caption) +msgid "Description of configuration options for storage_glusterfs" +msgstr "" + +#: ./doc/common/tables/cinder-storage_glusterfs.xml:23(td) +msgid "(StrOpt) Base dir containing mount points for gluster shares." +msgstr "" + +#: ./doc/common/tables/cinder-storage_glusterfs.xml:26(td) +msgid "glusterfs_qcow2_volumes = False" +msgstr "" + +#: ./doc/common/tables/cinder-storage_glusterfs.xml:27(td) +msgid "(BoolOpt) Create volumes as QCOW2 files rather than raw files." +msgstr "" + +#: ./doc/common/tables/cinder-storage_glusterfs.xml:30(td) +msgid "glusterfs_shares_config = /etc/cinder/glusterfs_shares" +msgstr "" + +#: ./doc/common/tables/cinder-storage_glusterfs.xml:31(td) +msgid "(StrOpt) File with the list of available gluster shares" +msgstr "" + +#: ./doc/common/tables/cinder-storage_glusterfs.xml:34(td) +msgid "glusterfs_sparsed_volumes = True" +msgstr "" + +#: ./doc/common/tables/nova-availabilityzones.xml:8(caption) +msgid "Description of configuration options for availabilityzones" +msgstr "" + +#: ./doc/common/tables/nova-availabilityzones.xml:22(td) +msgid "default_availability_zone = nova" +msgstr "" + +#: ./doc/common/tables/nova-availabilityzones.xml:23(td) +msgid "(StrOpt) default compute node availability_zone" +msgstr "" + +#: ./doc/common/tables/nova-availabilityzones.xml:26(td) +msgid "default_schedule_zone = None" +msgstr "" + +#: ./doc/common/tables/nova-availabilityzones.xml:27(td) +msgid "(StrOpt) availability zone to use when user doesn't specify one" +msgstr "" + +#: ./doc/common/tables/nova-availabilityzones.xml:30(td) +msgid "internal_service_availability_zone = internal" +msgstr "" + +#: ./doc/common/tables/nova-availabilityzones.xml:31(td) +msgid "(StrOpt) availability_zone to show internal services under" +msgstr "" + +#: ./doc/common/tables/nova-vnc.xml:8(caption) +msgid "Description of configuration options for vnc" +msgstr "" + +#: ./doc/common/tables/nova-vnc.xml:22(td) +msgid "novncproxy_base_url = http://127.0.0.1:6080/vnc_auto.html" +msgstr "" + +#: ./doc/common/tables/nova-vnc.xml:23(td) +msgid "(StrOpt) location of vnc console proxy, in the form \"http://127.0.0.1:6080/vnc_auto.html\"" +msgstr "" + +#: ./doc/common/tables/nova-vnc.xml:26(td) +msgid "vnc_enabled = True" +msgstr "" + +#: ./doc/common/tables/nova-vnc.xml:27(td) +msgid "(BoolOpt) enable vnc related features" +msgstr "" + +#: ./doc/common/tables/nova-vnc.xml:30(td) +msgid "vnc_keymap = en-us" +msgstr "" + +#: ./doc/common/tables/nova-vnc.xml:31(td) +msgid "(StrOpt) keymap for vnc" +msgstr "" + +#: ./doc/common/tables/nova-vnc.xml:34(td) +msgid "vncserver_listen = 127.0.0.1" +msgstr "" + +#: ./doc/common/tables/nova-vnc.xml:35(td) +msgid "(StrOpt) IP address on which instance vncservers should listen" +msgstr "" + +#: ./doc/common/tables/nova-vnc.xml:38(td) +msgid "vncserver_proxyclient_address = 127.0.0.1" +msgstr "" + +#: ./doc/common/tables/nova-vnc.xml:39(td) +msgid "(StrOpt) the address to which proxy clients (like nova-xvpvncproxy) should connect" +msgstr "" + +#: ./doc/common/tables/nova-vnc.xml:42(th) ./doc/common/tables/nova-vmware.xml:19(th) ./doc/common/tables/nova-network.xml:254(th) +msgid "[vmware]" +msgstr "" + +#: ./doc/common/tables/nova-vnc.xml:45(td) +msgid "vnc_port = 5900" +msgstr "" + +#: ./doc/common/tables/nova-vnc.xml:46(td) +msgid "(IntOpt) VNC starting port" +msgstr "" + +#: ./doc/common/tables/nova-vnc.xml:49(td) +msgid "vnc_port_total = 10000" +msgstr "" + +#: ./doc/common/tables/nova-vnc.xml:50(td) +msgid "(IntOpt) Total number of VNC ports" +msgstr "" + +#: ./doc/common/tables/swift-swift-swift-constraints.xml:7(literal) +msgid "[swift-constraints]" +msgstr "" + +#: ./doc/common/tables/swift-swift-swift-constraints.xml:7(literal) ./doc/common/tables/swift-swift-swift-hash.xml:7(literal) +msgid "swift.conf-sample" +msgstr "" + +#: ./doc/common/tables/swift-swift-swift-constraints.xml:18(td) +msgid "max_file_size = 5368709122" +msgstr "" + +#: ./doc/common/tables/swift-swift-swift-constraints.xml:19(td) +msgid "The largest normal object that can be saved in the cluster. This is also the limit on the size of each segment of a large object when using the large object manifest support. This value is set in bytes. Setting it to lower than 1MiB will cause some tests to fail. It is STRONGLY recommended to leave this value at the default (5 * 2**30 + 2)." +msgstr "" + +#: ./doc/common/tables/swift-swift-swift-constraints.xml:30(td) +msgid "max_meta_name_length = 128" +msgstr "" + +#: ./doc/common/tables/swift-swift-swift-constraints.xml:31(td) +msgid "The maximum number of bytes in the utf8 encoding of the name portion of a metadata header." +msgstr "" + +#: ./doc/common/tables/swift-swift-swift-constraints.xml:36(td) +msgid "max_meta_value_length = 256" +msgstr "" + +#: ./doc/common/tables/swift-swift-swift-constraints.xml:37(td) +msgid "The max number of bytes in the utf8 encoding of a metadata value." +msgstr "" + +#: ./doc/common/tables/swift-swift-swift-constraints.xml:41(td) +msgid "max_meta_count = 90" +msgstr "" + +#: ./doc/common/tables/swift-swift-swift-constraints.xml:42(td) +msgid "The maximum number of metadata keys that can be stored on a single account, container, or object." +msgstr "" + +#: ./doc/common/tables/swift-swift-swift-constraints.xml:47(td) +msgid "max_meta_overall_size = 4096" +msgstr "" + +#: ./doc/common/tables/swift-swift-swift-constraints.xml:48(td) +msgid "The maximum number of bytes in the utf8 encoding of the metadata (keys + values)." +msgstr "" + +#: ./doc/common/tables/swift-swift-swift-constraints.xml:53(td) +msgid "max_header_size = 8192" +msgstr "" + +#: ./doc/common/tables/swift-swift-swift-constraints.xml:54(td) +msgid "The maximum number of bytes in the utf8 encoding of each header." +msgstr "" + +#: ./doc/common/tables/swift-swift-swift-constraints.xml:58(td) +msgid "max_object_name_length = 1024" +msgstr "" + +#: ./doc/common/tables/swift-swift-swift-constraints.xml:59(td) +msgid "The maximum number of bytes in the utf8 encoding of an object name." +msgstr "" + +#: ./doc/common/tables/swift-swift-swift-constraints.xml:63(td) +msgid "container_listing_limit = 10000" +msgstr "" + +#: ./doc/common/tables/swift-swift-swift-constraints.xml:64(td) +msgid "The default (and maximum) number of items returned for a container listing request." +msgstr "" + +#: ./doc/common/tables/swift-swift-swift-constraints.xml:69(td) +msgid "account_listing_limit = 10000" +msgstr "" + +#: ./doc/common/tables/swift-swift-swift-constraints.xml:70(td) +msgid "The default (and maximum) number of items returned for an account listing request." +msgstr "" + +#: ./doc/common/tables/swift-swift-swift-constraints.xml:74(td) +msgid "max_account_name_length = 256" +msgstr "" + +#: ./doc/common/tables/swift-swift-swift-constraints.xml:75(td) +msgid "The maximum number of bytes in the utf8 encoding of an account name." +msgstr "" + +#: ./doc/common/tables/swift-swift-swift-constraints.xml:79(td) +msgid "max_container_name_length = 256" +msgstr "" + +#: ./doc/common/tables/swift-swift-swift-constraints.xml:80(td) +msgid "The maximum number of bytes in the utf8 encoding of a container name." +msgstr "" + +#: ./doc/common/tables/neutron-cisco.xml:8(caption) +msgid "Description of configuration options for cisco" +msgstr "" + +#: ./doc/common/tables/neutron-cisco.xml:19(td) +msgid "default_network_profile = default_network_profile" +msgstr "" + +#: ./doc/common/tables/neutron-cisco.xml:20(td) +msgid "(StrOpt) N1K default network profile" +msgstr "" + +#: ./doc/common/tables/neutron-cisco.xml:23(td) +msgid "default_policy_profile = service_profile" +msgstr "" + +#: ./doc/common/tables/neutron-cisco.xml:24(td) +msgid "(StrOpt) N1K default policy profile" +msgstr "" + +#: ./doc/common/tables/neutron-cisco.xml:27(td) +msgid "model_class = neutron.plugins.cisco.models.virt_phy_sw_v2.VirtualPhysicalSwitchModelV2" +msgstr "" + +#: ./doc/common/tables/neutron-cisco.xml:28(td) +msgid "(StrOpt) Model Class" +msgstr "" + +#: ./doc/common/tables/neutron-cisco.xml:31(td) +msgid "network_node_policy_profile = dhcp_pp" +msgstr "" + +#: ./doc/common/tables/neutron-cisco.xml:32(td) +msgid "(StrOpt) N1K policy profile for network node" +msgstr "" + +#: ./doc/common/tables/neutron-cisco.xml:35(td) +msgid "nexus_driver = neutron.plugins.cisco.test.nexus.fake_nexus_driver.CiscoNEXUSFakeDriver" +msgstr "" + +#: ./doc/common/tables/neutron-cisco.xml:36(td) +msgid "(StrOpt) Nexus Driver Name" +msgstr "" + +#: ./doc/common/tables/neutron-cisco.xml:39(td) +msgid "nexus_l3_enable = False" +msgstr "" + +#: ./doc/common/tables/neutron-cisco.xml:40(td) +msgid "(BoolOpt) Enable L3 support on the Nexus switches" +msgstr "" + +#: ./doc/common/tables/neutron-cisco.xml:43(td) +msgid "nexus_plugin = neutron.plugins.cisco.nexus.cisco_nexus_plugin_v2.NexusPlugin" +msgstr "" + +#: ./doc/common/tables/neutron-cisco.xml:44(td) +msgid "(StrOpt) Nexus Switch to use" +msgstr "" + +#: ./doc/common/tables/neutron-cisco.xml:47(td) +msgid "poll_duration = 10" +msgstr "" + +#: ./doc/common/tables/neutron-cisco.xml:48(td) +msgid "(StrOpt) N1K Policy profile polling duration in seconds" +msgstr "" + +#: ./doc/common/tables/neutron-cisco.xml:51(td) +msgid "provider_vlan_auto_create = True" +msgstr "" + +#: ./doc/common/tables/neutron-cisco.xml:52(td) +msgid "(BoolOpt) Provider VLANs are automatically created as needed on the Nexus switch" +msgstr "" + +#: ./doc/common/tables/neutron-cisco.xml:55(td) +msgid "provider_vlan_auto_trunk = True" +msgstr "" + +#: ./doc/common/tables/neutron-cisco.xml:56(td) +msgid "(BoolOpt) Provider VLANs are automatically trunked as needed on the ports of the Nexus switch" +msgstr "" + +#: ./doc/common/tables/neutron-cisco.xml:59(td) +msgid "provider_vlan_name_prefix = p-" +msgstr "" + +#: ./doc/common/tables/neutron-cisco.xml:60(td) +msgid "(StrOpt) VLAN Name prefix for provider vlans" +msgstr "" + +#: ./doc/common/tables/neutron-cisco.xml:63(td) ./doc/common/tables/neutron-cisco.xml:67(td) +msgid "svi_round_robin = False" +msgstr "" + +#: ./doc/common/tables/neutron-cisco.xml:64(td) ./doc/common/tables/neutron-cisco.xml:68(td) +msgid "(BoolOpt) Distribute SVI interfaces over all switches" +msgstr "" + +#: ./doc/common/tables/neutron-cisco.xml:71(td) ./doc/common/tables/neutron-cisco.xml:75(td) +msgid "vlan_name_prefix = q-" +msgstr "" + +#: ./doc/common/tables/neutron-cisco.xml:72(td) ./doc/common/tables/neutron-cisco.xml:76(td) +msgid "(StrOpt) VLAN Name prefix" +msgstr "" + +#: ./doc/common/tables/neutron-cisco.xml:79(td) +msgid "vswitch_plugin = neutron.plugins.openvswitch.ovs_neutron_plugin.OVSNeutronPluginV2" +msgstr "" + +#: ./doc/common/tables/neutron-cisco.xml:80(td) +msgid "(StrOpt) Virtual Switch to use" +msgstr "" + +#: ./doc/common/tables/neutron-cisco.xml:83(td) +msgid "vxlan_id_ranges = 5000:10000" +msgstr "" + +#: ./doc/common/tables/neutron-cisco.xml:84(td) +msgid "(StrOpt) N1K VXLAN ID Ranges" +msgstr "" + +#: ./doc/common/tables/nova-hyperv.xml:8(caption) ./doc/common/tables/neutron-hyperv.xml:8(caption) +msgid "Description of configuration options for hyperv" +msgstr "" + +#: ./doc/common/tables/nova-hyperv.xml:22(td) +msgid "dynamic_memory_ratio = 1.0" +msgstr "" + +#: ./doc/common/tables/nova-hyperv.xml:23(td) +msgid "(FloatOpt) Enables dynamic memory allocation (ballooning) when set to a value greater than 1. The value expresses the ratio between the total RAM assigned to an instance and its startup RAM amount. For example a ratio of 2.0 for an instance with 1024MB of RAM implies 512MB of RAM allocated at startup" +msgstr "" + +#: ./doc/common/tables/nova-hyperv.xml:26(td) +msgid "enable_instance_metrics_collection = False" +msgstr "" + +#: ./doc/common/tables/nova-hyperv.xml:27(td) +msgid "(BoolOpt) Enables metrics collections for an instance by using Hyper-V's metric APIs. Collected data can by retrieved by other apps and services, e.g.: Ceilometer. Requires Hyper-V / Windows Server 2012 and above" +msgstr "" + +#: ./doc/common/tables/nova-hyperv.xml:34(td) +msgid "instances_path_share =" +msgstr "" + +#: ./doc/common/tables/nova-hyperv.xml:35(td) +msgid "(StrOpt) The name of a Windows share name mapped to the \"instances_path\" dir and used by the resize feature to copy files to the target host. If left blank, an administrative share will be used, looking for the same \"instances_path\" used locally" +msgstr "" + +#: ./doc/common/tables/nova-hyperv.xml:38(td) +msgid "limit_cpu_features = False" +msgstr "" + +#: ./doc/common/tables/nova-hyperv.xml:39(td) +msgid "(BoolOpt) Required for live migration among hosts with different CPU features" +msgstr "" + +#: ./doc/common/tables/nova-hyperv.xml:42(td) +msgid "qemu_img_cmd = qemu-img.exe" +msgstr "" + +#: ./doc/common/tables/nova-hyperv.xml:43(td) +msgid "(StrOpt) qemu-img is used to convert between different image types" +msgstr "" + +#: ./doc/common/tables/nova-hyperv.xml:46(td) +msgid "vswitch_name = None" +msgstr "" + +#: ./doc/common/tables/nova-hyperv.xml:47(td) +msgid "(StrOpt) External virtual switch Name, if not provided, the first external virtual switch is used" +msgstr "" + +#: ./doc/common/tables/swift-object-server-filter-recon.xml:24(td) +msgid "recon_lock_path = /var/lock" +msgstr "" + +#: ./doc/common/tables/cinder-coraid.xml:8(caption) +msgid "Description of configuration options for coraid" +msgstr "" + +#: ./doc/common/tables/cinder-coraid.xml:22(td) +msgid "coraid_esm_address =" +msgstr "" + +#: ./doc/common/tables/cinder-coraid.xml:23(td) +msgid "(StrOpt) IP address of Coraid ESM" +msgstr "" + +#: ./doc/common/tables/cinder-coraid.xml:26(td) +msgid "coraid_group = admin" +msgstr "" + +#: ./doc/common/tables/cinder-coraid.xml:27(td) +msgid "(StrOpt) Name of group on Coraid ESM to which coraid_user belongs (must have admin privilege)" +msgstr "" + +#: ./doc/common/tables/cinder-coraid.xml:30(td) +msgid "coraid_password = password" +msgstr "" + +#: ./doc/common/tables/cinder-coraid.xml:31(td) +msgid "(StrOpt) Password to connect to Coraid ESM" +msgstr "" + +#: ./doc/common/tables/cinder-coraid.xml:34(td) +msgid "coraid_repository_key = coraid_repository" +msgstr "" + +#: ./doc/common/tables/cinder-coraid.xml:35(td) +msgid "(StrOpt) Volume Type key name to store ESM Repository Name" +msgstr "" + +#: ./doc/common/tables/cinder-coraid.xml:38(td) +msgid "coraid_user = admin" +msgstr "" + +#: ./doc/common/tables/cinder-coraid.xml:39(td) +msgid "(StrOpt) User name to connect to Coraid ESM" +msgstr "" + +#: ./doc/common/tables/swift-container-server-container-auditor.xml:7(literal) +msgid "[container-auditor]" +msgstr "" + +#: ./doc/common/tables/swift-container-server-container-auditor.xml:18(td) +msgid "log_name = container-auditor" +msgstr "" + +#: ./doc/common/tables/swift-container-server-container-auditor.xml:33(td) +msgid "containers_per_second = 200" +msgstr "" + +#: ./doc/common/tables/swift-container-server-container-auditor.xml:33(td) +msgid "Maximum containers audited per second. Should be tuned according to individual system specs. 0 is unlimited. mounted to prevent accidentally writing to the root device process simultaneously (it will actually accept(2) N + 1). Setting this to one (1) will only handle one request at a time, without accepting another request concurrently. By increasing the number of workers to a much higher value, one can reduce the impact of slow file system operations in one request from negatively impacting other requests." +msgstr "" + +#: ./doc/common/tables/swift-proxy-server-filter-catch_errors.xml:21(td) +msgid "set log_name = catch_errors" +msgstr "" + +#: ./doc/common/tables/nova-vmware.xml:22(td) +msgid "api_retry_count = 10" +msgstr "" + +#: ./doc/common/tables/nova-vmware.xml:23(td) +msgid "(IntOpt) The number of times we retry on failures, e.g., socket error, etc." +msgstr "" + +#: ./doc/common/tables/nova-vmware.xml:26(td) +msgid "cluster_name = None" +msgstr "" + +#: ./doc/common/tables/nova-vmware.xml:27(td) +msgid "(MultiStrOpt) Name of a VMware Cluster ComputeResource. Used only if compute_driver is vmwareapi.VMwareVCDriver." +msgstr "" + +#: ./doc/common/tables/nova-vmware.xml:30(td) +msgid "datastore_regex = None" +msgstr "" + +#: ./doc/common/tables/nova-vmware.xml:31(td) +msgid "(StrOpt) Regex to match the name of a datastore. Used only if compute_driver is vmwareapi.VMwareVCDriver." +msgstr "" + +#: ./doc/common/tables/nova-vmware.xml:34(td) +msgid "host_ip = None" +msgstr "" + +#: ./doc/common/tables/nova-vmware.xml:35(td) +msgid "(StrOpt) URL for connection to VMware ESX/VC host." +msgstr "" + +#: ./doc/common/tables/nova-vmware.xml:38(td) +msgid "host_password = None" +msgstr "" + +#: ./doc/common/tables/nova-vmware.xml:39(td) +msgid "(StrOpt) Password for connection to VMware ESX/VC host." +msgstr "" + +#: ./doc/common/tables/nova-vmware.xml:42(td) +msgid "host_username = None" +msgstr "" + +#: ./doc/common/tables/nova-vmware.xml:43(td) +msgid "(StrOpt) Username for connection to VMware ESX/VC host." +msgstr "" + +#: ./doc/common/tables/nova-vmware.xml:47(td) +msgid "(StrOpt) Name of Integration Bridge" +msgstr "" + +#: ./doc/common/tables/nova-vmware.xml:50(td) +msgid "maximum_objects = 100" +msgstr "" + +#: ./doc/common/tables/nova-vmware.xml:51(td) +msgid "(IntOpt) The maximum number of ObjectContent data objects that should be returned in a single result. A positive value will cause the operation to suspend the retrieval when the count of objects reaches the specified maximum. The server may still limit the count to something less than the configured value. Any remaining objects may be retrieved with additional requests." +msgstr "" + +#: ./doc/common/tables/nova-vmware.xml:54(td) +msgid "task_poll_interval = 5.0" +msgstr "" + +#: ./doc/common/tables/nova-vmware.xml:55(td) +msgid "(FloatOpt) The interval used for polling of remote tasks." +msgstr "" + +#: ./doc/common/tables/nova-vmware.xml:58(td) +msgid "use_linked_clone = True" +msgstr "" + +#: ./doc/common/tables/nova-vmware.xml:59(td) +msgid "(BoolOpt) Whether to use linked clone" +msgstr "" + +#: ./doc/common/tables/nova-vmware.xml:62(td) +msgid "wsdl_location = None" +msgstr "" + +#: ./doc/common/tables/nova-vmware.xml:63(td) +msgid "(StrOpt) Optional VIM Service WSDL Location e.g http://<server>/vimService.wsdl. Optional over-ride to default location for bug work-arounds" +msgstr "" + +#: ./doc/common/tables/nova-logging.xml:34(td) ./doc/common/tables/cinder-common.xml:62(td) +msgid "fatal_exception_format_errors = False" +msgstr "" + +#: ./doc/common/tables/nova-logging.xml:35(td) ./doc/common/tables/cinder-common.xml:63(td) +msgid "(BoolOpt) make exception message format errors fatal" +msgstr "" + +#: ./doc/common/tables/nova-xen.xml:8(caption) +msgid "Description of configuration options for xen" +msgstr "" + +#: ./doc/common/tables/nova-xen.xml:22(td) +msgid "console_driver = nova.console.xvp.XVPConsoleProxy" +msgstr "" + +#: ./doc/common/tables/nova-xen.xml:23(td) +msgid "(StrOpt) Driver to use for the console proxy" +msgstr "" + +#: ./doc/common/tables/nova-xen.xml:26(td) +msgid "console_vmrc_error_retries = 10" +msgstr "" + +#: ./doc/common/tables/nova-xen.xml:27(td) +msgid "(IntOpt) number of retries for retrieving VMRC information" +msgstr "" + +#: ./doc/common/tables/nova-xen.xml:30(td) +msgid "console_vmrc_port = 443" +msgstr "" + +#: ./doc/common/tables/nova-xen.xml:31(td) +msgid "(IntOpt) port for VMware VMRC connections" +msgstr "" + +#: ./doc/common/tables/nova-xen.xml:34(td) +msgid "console_xvp_conf = /etc/xvp.conf" +msgstr "" + +#: ./doc/common/tables/nova-xen.xml:35(td) +msgid "(StrOpt) generated XVP conf file" +msgstr "" + +#: ./doc/common/tables/nova-xen.xml:38(td) +msgid "console_xvp_conf_template = $pybasedir/nova/console/xvp.conf.template" +msgstr "" + +#: ./doc/common/tables/nova-xen.xml:39(td) +msgid "(StrOpt) XVP conf template" +msgstr "" + +#: ./doc/common/tables/nova-xen.xml:42(td) +msgid "console_xvp_log = /var/log/xvp.log" +msgstr "" + +#: ./doc/common/tables/nova-xen.xml:43(td) +msgid "(StrOpt) XVP log file" +msgstr "" + +#: ./doc/common/tables/nova-xen.xml:46(td) +msgid "console_xvp_multiplex_port = 5900" +msgstr "" + +#: ./doc/common/tables/nova-xen.xml:47(td) +msgid "(IntOpt) port for XVP to multiplex VNC connections on" +msgstr "" + +#: ./doc/common/tables/nova-xen.xml:50(td) +msgid "console_xvp_pid = /var/run/xvp.pid" +msgstr "" + +#: ./doc/common/tables/nova-xen.xml:51(td) +msgid "(StrOpt) XVP master process pid file" +msgstr "" + +#: ./doc/common/tables/nova-xen.xml:54(td) +msgid "stub_compute = False" +msgstr "" + +#: ./doc/common/tables/nova-xen.xml:55(td) +msgid "(BoolOpt) Stub calls to compute worker for tests" +msgstr "" + +#: ./doc/common/tables/nova-xen.xml:61(td) +msgid "xen_hvmloader_path = /usr/lib/xen/boot/hvmloader" +msgstr "" + +#: ./doc/common/tables/nova-xen.xml:62(td) +msgid "(StrOpt) Location where the Xen hvmloader is kept" +msgstr "" + +#: ./doc/common/tables/nova-xen.xml:68(td) +msgid "agent_path = usr/sbin/xe-update-networking" +msgstr "" + +#: ./doc/common/tables/nova-xen.xml:69(td) +msgid "(StrOpt) Specifies the path in which the xenapi guest agent should be located. If the agent is present, network configuration is not injected into the image. Used if compute_driver=xenapi.XenAPIDriver and flat_injected=True" +msgstr "" + +#: ./doc/common/tables/nova-xen.xml:72(td) +msgid "agent_resetnetwork_timeout = 60" +msgstr "" + +#: ./doc/common/tables/nova-xen.xml:73(td) +msgid "(IntOpt) number of seconds to wait for agent reply to resetnetwork request" +msgstr "" + +#: ./doc/common/tables/nova-xen.xml:76(td) +msgid "agent_timeout = 30" +msgstr "" + +#: ./doc/common/tables/nova-xen.xml:77(td) +msgid "(IntOpt) number of seconds to wait for agent reply" +msgstr "" + +#: ./doc/common/tables/nova-xen.xml:80(td) +msgid "agent_version_timeout = 300" +msgstr "" + +#: ./doc/common/tables/nova-xen.xml:81(td) +msgid "(IntOpt) number of seconds to wait for agent to be fully operational" +msgstr "" + +#: ./doc/common/tables/nova-xen.xml:84(td) +msgid "cache_images = all" +msgstr "" + +#: ./doc/common/tables/nova-xen.xml:85(td) +msgid "(StrOpt) Cache glance images locally. `all` will cache all images, `some` will only cache images that have the image_property `cache_in_nova=True`, and `none` turns off caching entirely" +msgstr "" + +#: ./doc/common/tables/nova-xen.xml:88(td) +msgid "check_host = True" +msgstr "" + +#: ./doc/common/tables/nova-xen.xml:89(td) +msgid "(BoolOpt) Ensure compute service is running on host XenAPI connects to." +msgstr "" + +#: ./doc/common/tables/nova-xen.xml:92(td) +msgid "connection_concurrent = 5" +msgstr "" + +#: ./doc/common/tables/nova-xen.xml:93(td) +msgid "(IntOpt) Maximum number of concurrent XenAPI connections. Used only if compute_driver=xenapi.XenAPIDriver" +msgstr "" + +#: ./doc/common/tables/nova-xen.xml:96(td) +msgid "connection_password = None" +msgstr "" + +#: ./doc/common/tables/nova-xen.xml:97(td) +msgid "(StrOpt) Password for connection to XenServer/Xen Cloud Platform. Used only if compute_driver=xenapi.XenAPIDriver" +msgstr "" + +#: ./doc/common/tables/nova-xen.xml:100(td) +msgid "connection_url = None" +msgstr "" + +#: ./doc/common/tables/nova-xen.xml:101(td) +msgid "(StrOpt) URL for connection to XenServer/Xen Cloud Platform. A special value of unix://local can be used to connect to the local unix socket. Required if compute_driver=xenapi.XenAPIDriver" +msgstr "" + +#: ./doc/common/tables/nova-xen.xml:104(td) +msgid "connection_username = root" +msgstr "" + +#: ./doc/common/tables/nova-xen.xml:105(td) +msgid "(StrOpt) Username for connection to XenServer/Xen Cloud Platform. Used only if compute_driver=xenapi.XenAPIDriver" +msgstr "" + +#: ./doc/common/tables/nova-xen.xml:108(td) +msgid "default_os_type = linux" +msgstr "" + +#: ./doc/common/tables/nova-xen.xml:109(td) +msgid "(StrOpt) Default OS type" +msgstr "" + +#: ./doc/common/tables/nova-xen.xml:112(td) +msgid "disable_agent = False" +msgstr "" + +#: ./doc/common/tables/nova-xen.xml:113(td) +msgid "(BoolOpt) Disables the use of the XenAPI agent in any image regardless of what image properties are present." +msgstr "" + +#: ./doc/common/tables/nova-xen.xml:116(td) +msgid "image_compression_level = None" +msgstr "" + +#: ./doc/common/tables/nova-xen.xml:117(td) +msgid "(IntOpt) Compression level for images, e.g., 9 for gzip -9. Range is 1-9, 9 being most compressed but most CPU intensive on dom0." +msgstr "" + +#: ./doc/common/tables/nova-xen.xml:120(td) +msgid "image_upload_handler = nova.virt.xenapi.image.glance.GlanceStore" +msgstr "" + +#: ./doc/common/tables/nova-xen.xml:121(td) +msgid "(StrOpt) Dom0 plugin driver used to handle image uploads." +msgstr "" + +#: ./doc/common/tables/nova-xen.xml:124(td) +msgid "ipxe_boot_menu_url = None" +msgstr "" + +#: ./doc/common/tables/nova-xen.xml:125(td) +msgid "(StrOpt) URL to the iPXE boot menu" +msgstr "" + +#: ./doc/common/tables/nova-xen.xml:128(td) +msgid "ipxe_mkisofs_cmd = mkisofs" +msgstr "" + +#: ./doc/common/tables/nova-xen.xml:129(td) ./doc/common/tables/nova-configdrive.xml:39(td) +msgid "(StrOpt) Name and optionally path of the tool used for ISO image creation" +msgstr "" + +#: ./doc/common/tables/nova-xen.xml:132(td) +msgid "ipxe_network_name = None" +msgstr "" + +#: ./doc/common/tables/nova-xen.xml:133(td) +msgid "(StrOpt) Name of network to use for booting iPXE ISOs" +msgstr "" + +#: ./doc/common/tables/nova-xen.xml:136(td) +msgid "iqn_prefix = iqn.2010-10.org.openstack" +msgstr "" + +#: ./doc/common/tables/nova-xen.xml:137(td) +msgid "(StrOpt) IQN Prefix" +msgstr "" + +#: ./doc/common/tables/nova-xen.xml:140(td) +msgid "login_timeout = 10" +msgstr "" + +#: ./doc/common/tables/nova-xen.xml:141(td) +msgid "(IntOpt) Timeout in seconds for XenAPI login." +msgstr "" + +#: ./doc/common/tables/nova-xen.xml:144(td) +msgid "max_kernel_ramdisk_size = 16777216" +msgstr "" + +#: ./doc/common/tables/nova-xen.xml:145(td) +msgid "(IntOpt) Maximum size in bytes of kernel or ramdisk images" +msgstr "" + +#: ./doc/common/tables/nova-xen.xml:148(td) +msgid "num_vbd_unplug_retries = 10" +msgstr "" + +#: ./doc/common/tables/nova-xen.xml:149(td) +msgid "(IntOpt) Maximum number of retries to unplug VBD" +msgstr "" + +#: ./doc/common/tables/nova-xen.xml:152(td) +msgid "ovs_integration_bridge = xapi1" +msgstr "" + +#: ./doc/common/tables/nova-xen.xml:156(td) +msgid "remap_vbd_dev = False" +msgstr "" + +#: ./doc/common/tables/nova-xen.xml:157(td) +msgid "(BoolOpt) Used to enable the remapping of VBD dev (Works around an issue in Ubuntu Maverick)" +msgstr "" + +#: ./doc/common/tables/nova-xen.xml:160(td) +msgid "remap_vbd_dev_prefix = sd" +msgstr "" + +#: ./doc/common/tables/nova-xen.xml:161(td) +msgid "(StrOpt) Specify prefix to remap VBD dev to (ex. /dev/xvdb -> /dev/sdb)" +msgstr "" + +#: ./doc/common/tables/nova-xen.xml:164(td) +msgid "running_timeout = 60" +msgstr "" + +#: ./doc/common/tables/nova-xen.xml:165(td) +msgid "(IntOpt) number of seconds to wait for instance to go to running state" +msgstr "" + +#: ./doc/common/tables/nova-xen.xml:168(td) +msgid "sparse_copy = True" +msgstr "" + +#: ./doc/common/tables/nova-xen.xml:169(td) +msgid "(BoolOpt) Whether to use sparse_copy for copying data on a resize down (False will use standard dd). This speeds up resizes down considerably since large runs of zeros won't have to be rsynced" +msgstr "" + +#: ./doc/common/tables/nova-xen.xml:172(td) +msgid "sr_base_path = /var/run/sr-mount" +msgstr "" + +#: ./doc/common/tables/nova-xen.xml:173(td) ./doc/common/tables/cinder-storage_xen.xml:43(td) +msgid "(StrOpt) Base path to the storage repository" +msgstr "" + +#: ./doc/common/tables/nova-xen.xml:176(td) +msgid "sr_matching_filter = default-sr:true" +msgstr "" + +#: ./doc/common/tables/nova-xen.xml:177(td) +msgid "(StrOpt) Filter for finding the SR to be used to install guest instances on. To use the Local Storage in default XenServer/XCP installations set this flag to other-config:i18n-key=local-storage. To select an SR with a different matching criteria, you could set it to other-config:my_favorite_sr=true. On the other hand, to fall back on the Default SR, as displayed by XenCenter, set this flag to: default-sr:true" +msgstr "" + +#: ./doc/common/tables/nova-xen.xml:180(td) +msgid "target_host = None" +msgstr "" + +#: ./doc/common/tables/nova-xen.xml:181(td) +msgid "(StrOpt) iSCSI Target Host" +msgstr "" + +#: ./doc/common/tables/nova-xen.xml:184(td) +msgid "target_port = 3260" +msgstr "" + +#: ./doc/common/tables/nova-xen.xml:185(td) +msgid "(StrOpt) iSCSI Target Port, 3260 Default" +msgstr "" + +#: ./doc/common/tables/nova-xen.xml:188(td) +msgid "torrent_base_url = None" +msgstr "" + +#: ./doc/common/tables/nova-xen.xml:189(td) +msgid "(StrOpt) Base URL for torrent files." +msgstr "" + +#: ./doc/common/tables/nova-xen.xml:192(td) +msgid "torrent_download_stall_cutoff = 600" +msgstr "" + +#: ./doc/common/tables/nova-xen.xml:193(td) +msgid "(IntOpt) Number of seconds a download can remain at the same progress percentage w/o being considered a stall" +msgstr "" + +#: ./doc/common/tables/nova-xen.xml:196(td) +msgid "torrent_images = none" +msgstr "" + +#: ./doc/common/tables/nova-xen.xml:197(td) +msgid "(StrOpt) Whether or not to download images via Bit Torrent (all|some|none)." +msgstr "" + +#: ./doc/common/tables/nova-xen.xml:200(td) +msgid "torrent_listen_port_end = 6891" +msgstr "" + +#: ./doc/common/tables/nova-xen.xml:201(td) +msgid "(IntOpt) End of port range to listen on" +msgstr "" + +#: ./doc/common/tables/nova-xen.xml:204(td) +msgid "torrent_listen_port_start = 6881" +msgstr "" + +#: ./doc/common/tables/nova-xen.xml:205(td) +msgid "(IntOpt) Beginning of port range to listen on" +msgstr "" + +#: ./doc/common/tables/nova-xen.xml:208(td) +msgid "torrent_max_last_accessed = 86400" +msgstr "" + +#: ./doc/common/tables/nova-xen.xml:209(td) +msgid "(IntOpt) Cached torrent files not accessed within this number of seconds can be reaped" +msgstr "" + +#: ./doc/common/tables/nova-xen.xml:212(td) +msgid "torrent_max_seeder_processes_per_host = 1" +msgstr "" + +#: ./doc/common/tables/nova-xen.xml:213(td) +msgid "(IntOpt) Maximum number of seeder processes to run concurrently within a given dom0. (-1 = no limit)" +msgstr "" + +#: ./doc/common/tables/nova-xen.xml:216(td) +msgid "torrent_seed_chance = 1.0" +msgstr "" + +#: ./doc/common/tables/nova-xen.xml:217(td) +msgid "(FloatOpt) Probability that peer will become a seeder. (1.0 = 100%)" +msgstr "" + +#: ./doc/common/tables/nova-xen.xml:220(td) +msgid "torrent_seed_duration = 3600" +msgstr "" + +#: ./doc/common/tables/nova-xen.xml:221(td) +msgid "(IntOpt) Number of seconds after downloading an image via BitTorrent that it should be seeded for other peers." +msgstr "" + +#: ./doc/common/tables/nova-xen.xml:224(td) +msgid "use_agent_default = False" +msgstr "" + +#: ./doc/common/tables/nova-xen.xml:225(td) +msgid "(BoolOpt) Determines if the xenapi agent should be used when the image used does not contain a hint to declare if the agent is present or not. The hint is a glance property \"xenapi_use_agent\" that has the value \"true\" or \"false\". Note that waiting for the agent when it is not present will significantly increase server boot times." +msgstr "" + +#: ./doc/common/tables/nova-xen.xml:228(td) +msgid "use_join_force = True" +msgstr "" + +#: ./doc/common/tables/nova-xen.xml:229(td) +msgid "(BoolOpt) To use for hosts with different CPUs" +msgstr "" + +#: ./doc/common/tables/nova-xen.xml:232(td) +msgid "vhd_coalesce_max_attempts = 5" +msgstr "" + +#: ./doc/common/tables/nova-xen.xml:233(td) +msgid "(IntOpt) Max number of times to poll for VHD to coalesce. Used only if compute_driver=xenapi.XenAPIDriver" +msgstr "" + +#: ./doc/common/tables/nova-xen.xml:236(td) +msgid "vhd_coalesce_poll_interval = 5.0" +msgstr "" + +#: ./doc/common/tables/nova-xen.xml:237(td) +msgid "(FloatOpt) The interval used for polling of coalescing vhds. Used only if compute_driver=xenapi.XenAPIDriver" +msgstr "" + +#: ./doc/common/tables/swift-proxy-server-filter-list-endpoints.xml:7(literal) +msgid "[filter:list-endpoints]" +msgstr "" + +#: ./doc/common/tables/swift-proxy-server-filter-list-endpoints.xml:18(td) +msgid "use = egg:swift#list_endpoints" +msgstr "" + +#: ./doc/common/tables/swift-proxy-server-filter-list-endpoints.xml:21(td) +msgid "list_endpoints_path = /endpoints/" +msgstr "" + +#: ./doc/common/tables/neutron-nicira.xml:8(caption) +msgid "Description of configuration options for nicira" +msgstr "" + +#: ./doc/common/tables/neutron-nicira.xml:19(td) +msgid "agent_mode = agent" +msgstr "" + +#: ./doc/common/tables/neutron-nicira.xml:20(td) +msgid "(StrOpt) The mode used to implement DHCP/metadata services." +msgstr "" + +#: ./doc/common/tables/neutron-nicira.xml:23(td) +msgid "always_read_status = False" +msgstr "" + +#: ./doc/common/tables/neutron-nicira.xml:24(td) +msgid "(BoolOpt) Always read operational status from backend on show operations. Enabling this option might slow down the system." +msgstr "" + +#: ./doc/common/tables/neutron-nicira.xml:27(td) +msgid "concurrent_connections = 10" +msgstr "" + +#: ./doc/common/tables/neutron-nicira.xml:28(td) +msgid "(IntOpt) Maximum concurrent connections to each NSX controller." +msgstr "" + +#: ./doc/common/tables/neutron-nicira.xml:31(td) +msgid "datacenter_moid = None" +msgstr "" + +#: ./doc/common/tables/neutron-nicira.xml:32(td) +msgid "(StrOpt) Optional parameter identifying the ID of datacenter to deploy NSX Edges" +msgstr "" + +#: ./doc/common/tables/neutron-nicira.xml:35(td) +msgid "datastore_id = None" +msgstr "" + +#: ./doc/common/tables/neutron-nicira.xml:36(td) ./doc/common/tables/neutron-nicira.xml:64(td) +msgid "(StrOpt) Optional parameter identifying the ID of datastore to deploy NSX Edges" +msgstr "" + +#: ./doc/common/tables/neutron-nicira.xml:39(td) +msgid "default_interface_name = breth0" +msgstr "" + +#: ./doc/common/tables/neutron-nicira.xml:40(td) +msgid "(StrOpt) Name of the interface on a L2 Gateway transport nodewhich should be used by default when setting up a network connection" +msgstr "" + +#: ./doc/common/tables/neutron-nicira.xml:43(td) +msgid "default_l2_gw_service_uuid = None" +msgstr "" + +#: ./doc/common/tables/neutron-nicira.xml:44(td) +msgid "(StrOpt) Unique identifier of the NSX L2 Gateway service which will be used by default for network gateways" +msgstr "" + +#: ./doc/common/tables/neutron-nicira.xml:47(td) +msgid "default_l3_gw_service_uuid = None" +msgstr "" + +#: ./doc/common/tables/neutron-nicira.xml:48(td) +msgid "(StrOpt) Unique identifier of the NSX L3 Gateway service which will be used for implementing routers and floating IPs" +msgstr "" + +#: ./doc/common/tables/neutron-nicira.xml:51(td) +msgid "default_service_cluster_uuid = None" +msgstr "" + +#: ./doc/common/tables/neutron-nicira.xml:52(td) +msgid "(StrOpt) Unique identifier of the Service Cluster which will be used by logical services like dhcp and metadata" +msgstr "" + +#: ./doc/common/tables/neutron-nicira.xml:55(td) +msgid "default_transport_type = stt" +msgstr "" + +#: ./doc/common/tables/neutron-nicira.xml:56(td) +msgid "(StrOpt) The default network tranport type to use (stt, gre, bridge, ipsec_gre, or ipsec_stt)" +msgstr "" + +#: ./doc/common/tables/neutron-nicira.xml:59(td) +msgid "default_tz_uuid = None" +msgstr "" + +#: ./doc/common/tables/neutron-nicira.xml:60(td) +msgid "(StrOpt) This is uuid of the default NSX Transport zone that will be used for creating tunneled isolated \"Neutron\" networks. It needs to be created in NSX before starting Neutron with the nsx plugin." +msgstr "" + +#: ./doc/common/tables/neutron-nicira.xml:63(td) +msgid "deployment_container_id = None" +msgstr "" + +#: ./doc/common/tables/neutron-nicira.xml:67(td) +msgid "external_network = None" +msgstr "" + +#: ./doc/common/tables/neutron-nicira.xml:68(td) +msgid "(StrOpt) Network ID for physical network connectivity" +msgstr "" + +#: ./doc/common/tables/neutron-nicira.xml:71(td) +msgid "http_timeout = 10" +msgstr "" + +#: ./doc/common/tables/neutron-nicira.xml:72(td) +msgid "(IntOpt) Time before aborting a request" +msgstr "" + +#: ./doc/common/tables/neutron-nicira.xml:75(td) +msgid "manager_uri = None" +msgstr "" + +#: ./doc/common/tables/neutron-nicira.xml:76(td) +msgid "(StrOpt) uri for vsm" +msgstr "" + +#: ./doc/common/tables/neutron-nicira.xml:79(td) +msgid "max_lp_per_bridged_ls = 5000" +msgstr "" + +#: ./doc/common/tables/neutron-nicira.xml:80(td) +msgid "(IntOpt) Maximum number of ports of a logical switch on a bridged transport zone (default 5000)" +msgstr "" + +#: ./doc/common/tables/neutron-nicira.xml:83(td) +msgid "max_lp_per_overlay_ls = 256" +msgstr "" + +#: ./doc/common/tables/neutron-nicira.xml:84(td) +msgid "(IntOpt) Maximum number of ports of a logical switch on an overlay transport zone (default 256)" +msgstr "" + +#: ./doc/common/tables/neutron-nicira.xml:87(td) +msgid "max_random_sync_delay = 0" +msgstr "" + +#: ./doc/common/tables/neutron-nicira.xml:88(td) +msgid "(IntOpt) Maximum value for the additional random delay in seconds between runs of the state synchronization task" +msgstr "" + +#: ./doc/common/tables/neutron-nicira.xml:91(td) +msgid "metadata_mode = access_network" +msgstr "" + +#: ./doc/common/tables/neutron-nicira.xml:92(td) +msgid "(StrOpt) If set to access_network this enables a dedicated connection to the metadata proxy for metadata server access via Neutron router. If set to dhcp_host_route this enables host route injection via the dhcp agent. This option is only useful if running on a host that does not support namespaces otherwise access_network should be used." +msgstr "" + +#: ./doc/common/tables/neutron-nicira.xml:95(td) +msgid "min_chunk_size = 500" +msgstr "" + +#: ./doc/common/tables/neutron-nicira.xml:96(td) +msgid "(IntOpt) Minimum number of resources to be retrieved from NSX during state synchronization" +msgstr "" + +#: ./doc/common/tables/neutron-nicira.xml:99(td) +msgid "min_sync_req_delay = 10" +msgstr "" + +#: ./doc/common/tables/neutron-nicira.xml:100(td) +msgid "(IntOpt) Minimum delay, in seconds, between two state synchronization queries to NSX. It must not exceed state_sync_interval" +msgstr "" + +#: ./doc/common/tables/neutron-nicira.xml:103(td) +msgid "nsx_controllers = None" +msgstr "" + +#: ./doc/common/tables/neutron-nicira.xml:104(td) +msgid "(ListOpt) Lists the NSX controllers in this cluster" +msgstr "" + +#: ./doc/common/tables/neutron-nicira.xml:107(td) +msgid "nsx_gen_timeout = -1" +msgstr "" + +#: ./doc/common/tables/neutron-nicira.xml:108(td) +msgid "(IntOpt) Number of seconds a generation id should be valid for (default -1 meaning do not time out)" +msgstr "" + +#: ./doc/common/tables/neutron-nicira.xml:111(td) +msgid "nsx_password = admin" +msgstr "" + +#: ./doc/common/tables/neutron-nicira.xml:112(td) +msgid "(StrOpt) Password for NSX controllers in this cluster" +msgstr "" + +#: ./doc/common/tables/neutron-nicira.xml:115(td) +msgid "nsx_user = admin" +msgstr "" + +#: ./doc/common/tables/neutron-nicira.xml:116(td) +msgid "(StrOpt) User name for NSX controllers in this cluster" +msgstr "" + +#: ./doc/common/tables/neutron-nicira.xml:119(td) +msgid "redirects = 2" +msgstr "" + +#: ./doc/common/tables/neutron-nicira.xml:120(td) +msgid "(IntOpt) Number of times a redirect should be followed" +msgstr "" + +#: ./doc/common/tables/neutron-nicira.xml:123(td) +msgid "req_timeout = 30" +msgstr "" + +#: ./doc/common/tables/neutron-nicira.xml:124(td) +msgid "(IntOpt) Total time limit for a cluster request" +msgstr "" + +#: ./doc/common/tables/neutron-nicira.xml:127(td) +msgid "resource_pool_id = None" +msgstr "" + +#: ./doc/common/tables/neutron-nicira.xml:128(td) +msgid "(StrOpt) Optional parameter identifying the ID of resource to deploy NSX Edges" +msgstr "" + +#: ./doc/common/tables/neutron-nicira.xml:131(td) +msgid "retries = 2" +msgstr "" + +#: ./doc/common/tables/neutron-nicira.xml:132(td) +msgid "(IntOpt) Number of time a request should be retried" +msgstr "" + +#: ./doc/common/tables/neutron-nicira.xml:135(td) +msgid "retries = 3" +msgstr "" + +#: ./doc/common/tables/neutron-nicira.xml:136(td) +msgid "(IntOpt) The number of retries the agent will send request to daemon before giving up" +msgstr "" + +#: ./doc/common/tables/neutron-nicira.xml:139(td) +msgid "state_sync_interval = 120" +msgstr "" + +#: ./doc/common/tables/neutron-nicira.xml:140(td) +msgid "(IntOpt) Interval in seconds between runs of the state synchronization task. Set it to 0 to disable it" +msgstr "" + +#: ./doc/common/tables/neutron-nicira.xml:143(td) +msgid "task_status_check_interval = 2000" +msgstr "" + +#: ./doc/common/tables/neutron-nicira.xml:144(td) +msgid "(IntOpt) Task status check interval" +msgstr "" + +#: ./doc/common/tables/neutron-nicira.xml:147(td) +msgid "user = admin" +msgstr "" + +#: ./doc/common/tables/neutron-nicira.xml:148(td) +msgid "(StrOpt) User name for vsm" +msgstr "" + +#: ./doc/common/tables/swift-memcache-memcache.xml:7(literal) +msgid "[memcache]" +msgstr "" + +#: ./doc/common/tables/swift-memcache-memcache.xml:7(literal) +msgid "memcache.conf-sample" +msgstr "" + +#: ./doc/common/tables/swift-proxy-server-filter-keystoneauth.xml:7(literal) +msgid "[filter:keystoneauth]" +msgstr "" + +#: ./doc/common/tables/swift-proxy-server-filter-keystoneauth.xml:18(td) +msgid "use = egg:swift#keystoneauth" +msgstr "" + +#: ./doc/common/tables/swift-proxy-server-filter-keystoneauth.xml:21(td) +msgid "operator_roles = admin, swiftoperator" +msgstr "" + +#: ./doc/common/tables/neutron-ml2.xml:8(caption) +msgid "Description of configuration options for ml2" +msgstr "" + +#: ./doc/common/tables/neutron-ml2.xml:19(td) +msgid "mechanism_drivers =" +msgstr "" + +#: ./doc/common/tables/neutron-ml2.xml:20(td) +msgid "(ListOpt) An ordered list of networking mechanism driver entrypoints to be loaded from the neutron.ml2.mechanism_drivers namespace." +msgstr "" + +#: ./doc/common/tables/neutron-ml2.xml:23(td) +msgid "tenant_network_types = local" +msgstr "" + +#: ./doc/common/tables/neutron-ml2.xml:24(td) +msgid "(ListOpt) Ordered list of network_types to allocate as tenant networks." +msgstr "" + +#: ./doc/common/tables/neutron-ml2.xml:27(td) +msgid "type_drivers = local, flat, vlan, gre, vxlan" +msgstr "" + +#: ./doc/common/tables/neutron-ml2.xml:28(td) +msgid "(ListOpt) List of network type driver entrypoints to be loaded from the neutron.ml2.type_drivers namespace." +msgstr "" + +#: ./doc/common/tables/neutron-linuxbridge.xml:8(caption) +msgid "Description of configuration options for linuxbridge" +msgstr "" + +#: ./doc/common/tables/neutron-linuxbridge.xml:20(td) +msgid "(StrOpt) Network type for tenant networks (local, vlan, or none)" +msgstr "" + +#: ./doc/common/tables/cinder-netapp_7mode_nfs.xml:8(caption) +msgid "Description of configuration options for netapp_7mode_nfs" +msgstr "" + +#: ./doc/common/tables/cinder-netapp_7mode_nfs.xml:22(td) ./doc/common/tables/cinder-netapp_cdot_nfs.xml:22(td) +msgid "expiry_thres_minutes = 720" +msgstr "" + +#: ./doc/common/tables/cinder-netapp_7mode_nfs.xml:23(td) ./doc/common/tables/cinder-netapp_cdot_nfs.xml:23(td) +msgid "(IntOpt) This option specifies the threshold for last access time for images in the NFS image cache. When a cache cleaning cycle begins, images in the cache that have not been accessed in the last M minutes, where M is the value of this parameter, will be deleted from the cache to create free space on the NFS share." +msgstr "" + +#: ./doc/common/tables/cinder-netapp_7mode_nfs.xml:54(td) ./doc/common/tables/cinder-netapp_cdot_nfs.xml:58(td) +msgid "thres_avl_size_perc_start = 20" +msgstr "" + +#: ./doc/common/tables/cinder-netapp_7mode_nfs.xml:55(td) ./doc/common/tables/cinder-netapp_cdot_nfs.xml:59(td) +msgid "(IntOpt) If the percentage of available space for an NFS share has dropped below the value specified by this option, the NFS image cache will be cleaned." +msgstr "" + +#: ./doc/common/tables/cinder-netapp_7mode_nfs.xml:58(td) ./doc/common/tables/cinder-netapp_cdot_nfs.xml:62(td) +msgid "thres_avl_size_perc_stop = 60" +msgstr "" + +#: ./doc/common/tables/cinder-netapp_7mode_nfs.xml:59(td) ./doc/common/tables/cinder-netapp_cdot_nfs.xml:63(td) +msgid "(IntOpt) When the percentage of available space on an NFS share has reached the percentage specified by this option, the driver will stop clearing files from the NFS image cache that have not been accessed in the last M minutes, where M is the value of the expiry_thres_minutes configuration option." +msgstr "" + +#: ./doc/common/tables/glance-common.xml:22(td) +msgid "allow_additional_image_properties = True" +msgstr "" + +#: ./doc/common/tables/glance-common.xml:23(td) +msgid "(BoolOpt) Whether to allow users to specify image properties beyond what the image schema provides" +msgstr "" + +#: ./doc/common/tables/glance-common.xml:26(td) +msgid "api_limit_max = 1000" +msgstr "" + +#: ./doc/common/tables/glance-common.xml:27(td) +msgid "(IntOpt) Maximum permissible number of items that could be returned by a request" +msgstr "" + +#: ./doc/common/tables/glance-common.xml:31(td) +msgid "(IntOpt) The backlog value that will be used when creating the TCP listener socket." +msgstr "" + +#: ./doc/common/tables/glance-common.xml:35(td) +msgid "(StrOpt) Address to bind the server. Useful when selecting a particular network interface." +msgstr "" + +#: ./doc/common/tables/glance-common.xml:38(td) +msgid "bind_port = None" +msgstr "" + +#: ./doc/common/tables/glance-common.xml:39(td) +msgid "(IntOpt) The port on which the server will listen." +msgstr "" + +#: ./doc/common/tables/glance-common.xml:42(td) +msgid "data_api = glance.db.sqlalchemy.api" +msgstr "" + +#: ./doc/common/tables/glance-common.xml:43(td) +msgid "(StrOpt) Python module path of data access API" +msgstr "" + +#: ./doc/common/tables/glance-common.xml:50(td) +msgid "image_location_quota = 10" +msgstr "" + +#: ./doc/common/tables/glance-common.xml:51(td) +msgid "(IntOpt) Maximum number of locations allowed on an image. Negative values evaluate to unlimited." +msgstr "" + +#: ./doc/common/tables/glance-common.xml:54(td) +msgid "image_member_quota = 128" +msgstr "" + +#: ./doc/common/tables/glance-common.xml:55(td) +msgid "(IntOpt) Maximum number of image members per image. Negative values evaluate to unlimited." +msgstr "" + +#: ./doc/common/tables/glance-common.xml:58(td) +msgid "image_property_quota = 128" +msgstr "" + +#: ./doc/common/tables/glance-common.xml:59(td) +msgid "(IntOpt) Maximum number of properties allowed on an image. Negative values evaluate to unlimited." +msgstr "" + +#: ./doc/common/tables/glance-common.xml:62(td) +msgid "image_tag_quota = 128" +msgstr "" + +#: ./doc/common/tables/glance-common.xml:63(td) +msgid "(IntOpt) Maximum number of tags allowed on an image. Negative values evaluate to unlimited." +msgstr "" + +#: ./doc/common/tables/glance-common.xml:66(td) +msgid "limit_param_default = 25" +msgstr "" + +#: ./doc/common/tables/glance-common.xml:67(td) +msgid "(IntOpt) Default value for the number of items returned by a request if not specified explicitly in the request" +msgstr "" + +#: ./doc/common/tables/glance-common.xml:74(td) +msgid "metadata_encryption_key = None" +msgstr "" + +#: ./doc/common/tables/glance-common.xml:75(td) +msgid "(StrOpt) Key used for encrypting sensitive metadata while talking to the registry or database." +msgstr "" + +#: ./doc/common/tables/glance-common.xml:78(td) +msgid "notifier_strategy = default" +msgstr "" + +#: ./doc/common/tables/glance-common.xml:79(td) +msgid "(StrOpt) Notifications can be sent when images are create, updated or deleted. There are three methods of sending notifications, logging (via the log_file directive), rabbit (via a rabbitmq queue), qpid (via a Qpid message queue), or noop (no notifications sent, the default). (DEPRECATED)" +msgstr "" + +#: ./doc/common/tables/glance-common.xml:83(td) +msgid "(StrOpt) Region name of this node" +msgstr "" + +#: ./doc/common/tables/glance-common.xml:86(td) +msgid "property_protection_file = None" +msgstr "" + +#: ./doc/common/tables/glance-common.xml:87(td) +msgid "(StrOpt) The location of the property protection file." +msgstr "" + +#: ./doc/common/tables/glance-common.xml:90(td) +msgid "property_protection_rule_format = roles" +msgstr "" + +#: ./doc/common/tables/glance-common.xml:91(td) +msgid "(StrOpt) This config value indicates whether \"roles\" or \"policies\" are used in the property protection file." +msgstr "" + +#: ./doc/common/tables/glance-common.xml:94(td) +msgid "show_image_direct_url = False" +msgstr "" + +#: ./doc/common/tables/glance-common.xml:95(td) +msgid "(BoolOpt) Whether to include the backend image storage location in image properties. Revealing storage location can be a security risk, so use this setting with caution!" +msgstr "" + +#: ./doc/common/tables/glance-common.xml:98(td) +msgid "user_storage_quota = 0" +msgstr "" + +#: ./doc/common/tables/glance-common.xml:99(td) +msgid "(IntOpt) Set a system wide quota for every user. This value is the total number of bytes that a user can use across all storage systems. A value of 0 means unlimited." +msgstr "" + +#: ./doc/common/tables/glance-common.xml:102(td) +msgid "workers = 1" +msgstr "" + +#: ./doc/common/tables/glance-common.xml:103(td) +msgid "(IntOpt) The number of child process workers that will be created to service API requests." +msgstr "" + +#: ./doc/common/tables/glance-common.xml:109(td) ./doc/common/tables/cinder-common.xml:249(td) ./doc/common/tables/neutron-db.xml:79(td) ./doc/common/tables/nova-api.xml:93(td) +msgid "use_tpool = False" +msgstr "" + +#: ./doc/common/tables/glance-common.xml:110(td) ./doc/common/tables/cinder-common.xml:250(td) ./doc/common/tables/neutron-db.xml:80(td) ./doc/common/tables/nova-api.xml:94(td) +msgid "(BoolOpt) Enable the experimental use of thread pooling for all DB API calls" +msgstr "" + +#: ./doc/common/tables/glance-common.xml:113(th) +msgid "[image_format]" +msgstr "" + +#: ./doc/common/tables/glance-common.xml:116(td) +msgid "container_formats = ami, ari, aki, bare, ovf" +msgstr "" + +#: ./doc/common/tables/glance-common.xml:117(td) +msgid "(ListOpt) Supported values for the 'container_format' image attribute" +msgstr "" + +#: ./doc/common/tables/glance-common.xml:120(td) +msgid "disk_formats = ami, ari, aki, vhd, vmdk, raw, qcow2, vdi, iso" +msgstr "" + +#: ./doc/common/tables/glance-common.xml:121(td) +msgid "(ListOpt) Supported values for the 'disk_format' image attribute" +msgstr "" + +#: ./doc/common/tables/glance-common.xml:124(th) +msgid "[task]" +msgstr "" + +#: ./doc/common/tables/glance-common.xml:127(td) +msgid "task_time_to_live = 48" +msgstr "" + +#: ./doc/common/tables/glance-common.xml:128(td) +msgid "(IntOpt) Time in hours for which a task lives after, either succeeding or failing" +msgstr "" + +#: ./doc/common/tables/nova-network.xml:8(caption) +msgid "Description of configuration options for network" +msgstr "" + +#: ./doc/common/tables/nova-network.xml:22(td) +msgid "allow_same_net_traffic = True" +msgstr "" + +#: ./doc/common/tables/nova-network.xml:23(td) +msgid "(BoolOpt) Whether to allow network traffic from same network" +msgstr "" + +#: ./doc/common/tables/nova-network.xml:26(td) +msgid "auto_assign_floating_ip = False" +msgstr "" + +#: ./doc/common/tables/nova-network.xml:27(td) +msgid "(BoolOpt) Autoassigning floating ip to VM" +msgstr "" + +#: ./doc/common/tables/nova-network.xml:30(td) +msgid "cnt_vpn_clients = 0" +msgstr "" + +#: ./doc/common/tables/nova-network.xml:31(td) +msgid "(IntOpt) Number of addresses reserved for vpn clients" +msgstr "" + +#: ./doc/common/tables/nova-network.xml:34(td) +msgid "create_unique_mac_address_attempts = 5" +msgstr "" + +#: ./doc/common/tables/nova-network.xml:35(td) +msgid "(IntOpt) Number of attempts to create unique mac address" +msgstr "" + +#: ./doc/common/tables/nova-network.xml:38(td) +msgid "default_access_ip_network_name = None" +msgstr "" + +#: ./doc/common/tables/nova-network.xml:39(td) +msgid "(StrOpt) Name of network to use to set access ips for instances" +msgstr "" + +#: ./doc/common/tables/nova-network.xml:42(td) +msgid "default_floating_pool = nova" +msgstr "" + +#: ./doc/common/tables/nova-network.xml:43(td) +msgid "(StrOpt) Default pool for floating ips" +msgstr "" + +#: ./doc/common/tables/nova-network.xml:46(td) +msgid "defer_iptables_apply = False" +msgstr "" + +#: ./doc/common/tables/nova-network.xml:47(td) +msgid "(BoolOpt) Whether to batch up the application of IPTables rules during a host restart and apply all at the end of the init phase" +msgstr "" + +#: ./doc/common/tables/nova-network.xml:50(td) +msgid "dhcp_domain = novalocal" +msgstr "" + +#: ./doc/common/tables/nova-network.xml:51(td) +msgid "(StrOpt) domain to use for building the hostnames" +msgstr "" + +#: ./doc/common/tables/nova-network.xml:54(td) +msgid "dhcp_lease_time = 120" +msgstr "" + +#: ./doc/common/tables/nova-network.xml:55(td) +msgid "(IntOpt) Lifetime of a DHCP lease in seconds" +msgstr "" + +#: ./doc/common/tables/nova-network.xml:58(td) +msgid "dhcpbridge = $bindir/nova-dhcpbridge" +msgstr "" + +#: ./doc/common/tables/nova-network.xml:59(td) +msgid "(StrOpt) location of nova-dhcpbridge" +msgstr "" + +#: ./doc/common/tables/nova-network.xml:62(td) +msgid "dhcpbridge_flagfile = ['/etc/nova/nova-dhcpbridge.conf']" +msgstr "" + +#: ./doc/common/tables/nova-network.xml:63(td) +msgid "(MultiStrOpt) location of flagfiles for dhcpbridge" +msgstr "" + +#: ./doc/common/tables/nova-network.xml:66(td) +msgid "dns_server = []" +msgstr "" + +#: ./doc/common/tables/nova-network.xml:67(td) +msgid "(MultiStrOpt) if set, uses specific dns server for dnsmasq. Canbe specified multiple times." +msgstr "" + +#: ./doc/common/tables/nova-network.xml:70(td) +msgid "dns_update_periodic_interval = -1" +msgstr "" + +#: ./doc/common/tables/nova-network.xml:71(td) +msgid "(IntOpt) Number of seconds to wait between runs of updates to DNS entries." +msgstr "" + +#: ./doc/common/tables/nova-network.xml:74(td) +msgid "dnsmasq_config_file =" +msgstr "" + +#: ./doc/common/tables/nova-network.xml:75(td) +msgid "(StrOpt) Override the default dnsmasq settings with this file" +msgstr "" + +#: ./doc/common/tables/nova-network.xml:78(td) +msgid "firewall_driver = None" +msgstr "" + +#: ./doc/common/tables/nova-network.xml:79(td) +msgid "(StrOpt) Firewall driver (defaults to hypervisor specific iptables driver)" +msgstr "" + +#: ./doc/common/tables/nova-network.xml:82(td) +msgid "fixed_ip_disassociate_timeout = 600" +msgstr "" + +#: ./doc/common/tables/nova-network.xml:83(td) +msgid "(IntOpt) Seconds after which a deallocated ip is disassociated" +msgstr "" + +#: ./doc/common/tables/nova-network.xml:86(td) +msgid "flat_injected = False" +msgstr "" + +#: ./doc/common/tables/nova-network.xml:87(td) +msgid "(BoolOpt) Whether to attempt to inject network setup into guest" +msgstr "" + +#: ./doc/common/tables/nova-network.xml:90(td) +msgid "flat_interface = None" +msgstr "" + +#: ./doc/common/tables/nova-network.xml:91(td) +msgid "(StrOpt) FlatDhcp will bridge into this interface if set" +msgstr "" + +#: ./doc/common/tables/nova-network.xml:94(td) +msgid "flat_network_bridge = None" +msgstr "" + +#: ./doc/common/tables/nova-network.xml:95(td) +msgid "(StrOpt) Bridge for simple network instances" +msgstr "" + +#: ./doc/common/tables/nova-network.xml:98(td) +msgid "flat_network_dns = 8.8.4.4" +msgstr "" + +#: ./doc/common/tables/nova-network.xml:99(td) +msgid "(StrOpt) Dns for simple network" +msgstr "" + +#: ./doc/common/tables/nova-network.xml:102(td) +msgid "floating_ip_dns_manager = nova.network.noop_dns_driver.NoopDNSDriver" +msgstr "" + +#: ./doc/common/tables/nova-network.xml:103(td) +msgid "(StrOpt) full class name for the DNS Manager for floating IPs" +msgstr "" + +#: ./doc/common/tables/nova-network.xml:106(td) +msgid "force_dhcp_release = True" +msgstr "" + +#: ./doc/common/tables/nova-network.xml:107(td) +msgid "(BoolOpt) If True, send a dhcp release on instance termination" +msgstr "" + +#: ./doc/common/tables/nova-network.xml:110(td) +msgid "force_snat_range = []" +msgstr "" + +#: ./doc/common/tables/nova-network.xml:111(td) +msgid "(MultiStrOpt) Traffic to this range will always be snatted to the fallback ip, even if it would normally be bridged out of the node. Can be specified multiple times." +msgstr "" + +#: ./doc/common/tables/nova-network.xml:114(td) +msgid "forward_bridge_interface = ['all']" +msgstr "" + +#: ./doc/common/tables/nova-network.xml:115(td) +msgid "(MultiStrOpt) An interface that bridges can forward to. If this is set to all then all traffic will be forwarded. Can be specified multiple times." +msgstr "" + +#: ./doc/common/tables/nova-network.xml:118(td) +msgid "gateway = None" +msgstr "" + +#: ./doc/common/tables/nova-network.xml:119(td) +msgid "(StrOpt) Default IPv4 gateway" +msgstr "" + +#: ./doc/common/tables/nova-network.xml:122(td) +msgid "injected_network_template = $pybasedir/nova/virt/interfaces.template" +msgstr "" + +#: ./doc/common/tables/nova-network.xml:123(td) +msgid "(StrOpt) Template file for injected network" +msgstr "" + +#: ./doc/common/tables/nova-network.xml:126(td) +msgid "instance_dns_domain =" +msgstr "" + +#: ./doc/common/tables/nova-network.xml:127(td) +msgid "(StrOpt) full class name for the DNS Zone for instance IPs" +msgstr "" + +#: ./doc/common/tables/nova-network.xml:130(td) +msgid "instance_dns_manager = nova.network.noop_dns_driver.NoopDNSDriver" +msgstr "" + +#: ./doc/common/tables/nova-network.xml:131(td) +msgid "(StrOpt) full class name for the DNS Manager for instance IPs" +msgstr "" + +#: ./doc/common/tables/nova-network.xml:134(td) +msgid "iptables_bottom_regex =" +msgstr "" + +#: ./doc/common/tables/nova-network.xml:135(td) +msgid "(StrOpt) Regular expression to match iptables rule that should always be on the bottom." +msgstr "" + +#: ./doc/common/tables/nova-network.xml:138(td) +msgid "iptables_drop_action = DROP" +msgstr "" + +#: ./doc/common/tables/nova-network.xml:139(td) +msgid "(StrOpt) The table that iptables to jump to when a packet is to be dropped." +msgstr "" + +#: ./doc/common/tables/nova-network.xml:142(td) +msgid "iptables_top_regex =" +msgstr "" + +#: ./doc/common/tables/nova-network.xml:143(td) +msgid "(StrOpt) Regular expression to match iptables rule that should always be on the top." +msgstr "" + +#: ./doc/common/tables/nova-network.xml:146(td) +msgid "l3_lib = nova.network.l3.LinuxNetL3" +msgstr "" + +#: ./doc/common/tables/nova-network.xml:147(td) +msgid "(StrOpt) Indicates underlying L3 management library" +msgstr "" + +#: ./doc/common/tables/nova-network.xml:150(td) +msgid "linuxnet_interface_driver = nova.network.linux_net.LinuxBridgeInterfaceDriver" +msgstr "" + +#: ./doc/common/tables/nova-network.xml:151(td) +msgid "(StrOpt) Driver used to create ethernet devices." +msgstr "" + +#: ./doc/common/tables/nova-network.xml:154(td) +msgid "linuxnet_ovs_integration_bridge = br-int" +msgstr "" + +#: ./doc/common/tables/nova-network.xml:155(td) +msgid "(StrOpt) Name of Open vSwitch bridge used with linuxnet" +msgstr "" + +#: ./doc/common/tables/nova-network.xml:158(td) +msgid "multi_host = False" +msgstr "" + +#: ./doc/common/tables/nova-network.xml:159(td) +msgid "(BoolOpt) Default value for multi_host in networks. Also, if set, some rpc network calls will be sent directly to host." +msgstr "" + +#: ./doc/common/tables/nova-network.xml:162(td) +msgid "network_allocate_retries = 0" +msgstr "" + +#: ./doc/common/tables/nova-network.xml:163(td) +msgid "(IntOpt) Number of times to retry network allocation on failures" +msgstr "" + +#: ./doc/common/tables/nova-network.xml:166(td) +msgid "network_api_class = nova.network.api.API" +msgstr "" + +#: ./doc/common/tables/nova-network.xml:167(td) +msgid "(StrOpt) The full class name of the network API class to use" +msgstr "" + +#: ./doc/common/tables/nova-network.xml:171(td) +msgid "(IntOpt) MTU setting for network interface" +msgstr "" + +#: ./doc/common/tables/nova-network.xml:174(td) +msgid "network_driver = nova.network.linux_net" +msgstr "" + +#: ./doc/common/tables/nova-network.xml:175(td) +msgid "(StrOpt) Driver to use for network creation" +msgstr "" + +#: ./doc/common/tables/nova-network.xml:178(td) +msgid "network_manager = nova.network.manager.VlanManager" +msgstr "" + +#: ./doc/common/tables/nova-network.xml:179(td) +msgid "(StrOpt) full class name for the Manager for network" +msgstr "" + +#: ./doc/common/tables/nova-network.xml:182(td) +msgid "network_size = 256" +msgstr "" + +#: ./doc/common/tables/nova-network.xml:183(td) +msgid "(IntOpt) Number of addresses in each private subnet" +msgstr "" + +#: ./doc/common/tables/nova-network.xml:186(td) +msgid "network_topic = network" +msgstr "" + +#: ./doc/common/tables/nova-network.xml:187(td) +msgid "(StrOpt) the topic network nodes listen on" +msgstr "" + +#: ./doc/common/tables/nova-network.xml:190(td) +msgid "networks_path = $state_path/networks" +msgstr "" + +#: ./doc/common/tables/nova-network.xml:191(td) +msgid "(StrOpt) Location to keep network config files" +msgstr "" + +#: ./doc/common/tables/nova-network.xml:194(td) +msgid "num_networks = 1" +msgstr "" + +#: ./doc/common/tables/nova-network.xml:195(td) +msgid "(IntOpt) Number of networks to support" +msgstr "" + +#: ./doc/common/tables/nova-network.xml:198(td) +msgid "ovs_vsctl_timeout = 120" +msgstr "" + +#: ./doc/common/tables/nova-network.xml:199(td) +msgid "(IntOpt) Amount of time, in seconds, that ovs_vsctl should wait for a response from the database. 0 is to wait forever." +msgstr "" + +#: ./doc/common/tables/nova-network.xml:202(td) +msgid "public_interface = eth0" +msgstr "" + +#: ./doc/common/tables/nova-network.xml:203(td) +msgid "(StrOpt) Interface for public IP addresses" +msgstr "" + +#: ./doc/common/tables/nova-network.xml:206(td) +msgid "routing_source_ip = $my_ip" +msgstr "" + +#: ./doc/common/tables/nova-network.xml:207(td) +msgid "(StrOpt) Public IP of network host" +msgstr "" + +#: ./doc/common/tables/nova-network.xml:210(td) +msgid "security_group_api = nova" +msgstr "" + +#: ./doc/common/tables/nova-network.xml:211(td) +msgid "(StrOpt) The full class name of the security API class" +msgstr "" + +#: ./doc/common/tables/nova-network.xml:214(td) +msgid "send_arp_for_ha = False" +msgstr "" + +#: ./doc/common/tables/nova-network.xml:215(td) +msgid "(BoolOpt) send gratuitous ARPs for HA setup" +msgstr "" + +#: ./doc/common/tables/nova-network.xml:218(td) +msgid "send_arp_for_ha_count = 3" +msgstr "" + +#: ./doc/common/tables/nova-network.xml:219(td) +msgid "(IntOpt) send this many gratuitous ARPs for HA setup" +msgstr "" + +#: ./doc/common/tables/nova-network.xml:222(td) +msgid "share_dhcp_address = False" +msgstr "" + +#: ./doc/common/tables/nova-network.xml:223(td) +msgid "(BoolOpt) If True in multi_host mode, all compute hosts share the same dhcp address. The same IP address used for DHCP will be added on each nova-network node which is only visible to the vms on the same host." +msgstr "" + +#: ./doc/common/tables/nova-network.xml:226(td) +msgid "teardown_unused_network_gateway = False" +msgstr "" + +#: ./doc/common/tables/nova-network.xml:227(td) +msgid "(BoolOpt) If True, unused gateway devices (VLAN and bridge) are deleted in VLAN network mode with multi hosted networks" +msgstr "" + +#: ./doc/common/tables/nova-network.xml:230(td) +msgid "update_dns_entries = False" +msgstr "" + +#: ./doc/common/tables/nova-network.xml:231(td) +msgid "(BoolOpt) If True, when a DNS entry must be updated, it sends a fanout cast to all network hosts to update their DNS entries in multi host mode" +msgstr "" + +#: ./doc/common/tables/nova-network.xml:234(td) +msgid "use_network_dns_servers = False" +msgstr "" + +#: ./doc/common/tables/nova-network.xml:235(td) +msgid "(BoolOpt) if set, uses the dns1 and dns2 from the network ref.as dns servers." +msgstr "" + +#: ./doc/common/tables/nova-network.xml:238(td) +msgid "use_neutron_default_nets = False" +msgstr "" + +#: ./doc/common/tables/nova-network.xml:239(td) +msgid "(StrOpt) Control for checking for default networks" +msgstr "" + +#: ./doc/common/tables/nova-network.xml:242(td) +msgid "use_single_default_gateway = False" +msgstr "" + +#: ./doc/common/tables/nova-network.xml:243(td) +msgid "(BoolOpt) Use single default gateway. Only first nic of vm will get default gateway from dhcp server" +msgstr "" + +#: ./doc/common/tables/nova-network.xml:246(td) +msgid "vlan_interface = None" +msgstr "" + +#: ./doc/common/tables/nova-network.xml:247(td) +msgid "(StrOpt) vlans will bridge into this interface if set" +msgstr "" + +#: ./doc/common/tables/nova-network.xml:250(td) +msgid "vlan_start = 100" +msgstr "" + +#: ./doc/common/tables/nova-network.xml:251(td) +msgid "(IntOpt) First VLAN for private networks" +msgstr "" + +#: ./doc/common/tables/nova-network.xml:257(td) +msgid "vlan_interface = vmnic0" +msgstr "" + +#: ./doc/common/tables/nova-network.xml:258(td) +msgid "(StrOpt) Physical ethernet adapter name for vlan networking" +msgstr "" + +#: ./doc/common/tables/cinder-scality.xml:8(caption) +msgid "Description of configuration options for scality" +msgstr "" + +#: ./doc/common/tables/cinder-scality.xml:30(td) +msgid "scality_sofs_volume_dir = cinder/volumes" +msgstr "" + +#: ./doc/common/tables/cinder-scality.xml:31(td) +msgid "(StrOpt) Path from Scality SOFS root to volume dir" +msgstr "" + +#: ./doc/common/tables/neutron-notifier.xml:8(caption) +msgid "Description of configuration options for notifier" +msgstr "" + +#: ./doc/common/tables/neutron-notifier.xml:19(td) ./doc/common/tables/cinder-common.xml:38(td) ./doc/common/tables/nova-compute.xml:54(td) +msgid "default_notification_level = INFO" +msgstr "" + +#: ./doc/common/tables/neutron-notifier.xml:20(td) ./doc/common/tables/cinder-common.xml:39(td) ./doc/common/tables/nova-compute.xml:55(td) +msgid "(StrOpt) Default notification level for outgoing notifications" +msgstr "" + +#: ./doc/common/tables/neutron-notifier.xml:23(td) +msgid "default_publisher_id = $host" +msgstr "" + +#: ./doc/common/tables/neutron-notifier.xml:24(td) ./doc/common/tables/cinder-common.xml:43(td) ./doc/common/tables/glance-api.xml:31(td) ./doc/common/tables/nova-compute.xml:59(td) +msgid "(StrOpt) Default publisher_id for outgoing notifications" +msgstr "" + +#: ./doc/common/tables/neutron-notifier.xml:32(td) +msgid "(ListOpt) AMQP topic used for openstack notifications" +msgstr "" + +#: ./doc/common/tables/cinder-common.xml:22(td) +msgid "compute_api_class = cinder.compute.nova.API" +msgstr "" + +#: ./doc/common/tables/cinder-common.xml:23(td) +msgid "(StrOpt) The full class name of the compute API class to use" +msgstr "" + +#: ./doc/common/tables/cinder-common.xml:30(td) +msgid "default_availability_zone = None" +msgstr "" + +#: ./doc/common/tables/cinder-common.xml:31(td) +msgid "(StrOpt) default availability zone to use when creating a new volume. If this is not set then we use the value from the storage_availability_zone option as the default availability_zone for new volumes." +msgstr "" + +#: ./doc/common/tables/cinder-common.xml:42(td) ./doc/common/tables/nova-compute.xml:58(td) +msgid "default_publisher_id = None" +msgstr "" + +#: ./doc/common/tables/cinder-common.xml:46(td) +msgid "default_volume_type = None" +msgstr "" + +#: ./doc/common/tables/cinder-common.xml:47(td) +msgid "(StrOpt) default volume type to use" +msgstr "" + +#: ./doc/common/tables/cinder-common.xml:54(td) ./doc/common/tables/nova-api.xml:22(td) +msgid "enable_new_services = True" +msgstr "" + +#: ./doc/common/tables/cinder-common.xml:55(td) ./doc/common/tables/nova-api.xml:23(td) +msgid "(BoolOpt) Services to be added to the available pool on create" +msgstr "" + +#: ./doc/common/tables/cinder-common.xml:67(td) +msgid "(StrOpt) Name of this node. This can be an opaque identifier. It is not necessarily a hostname, FQDN, or IP address." +msgstr "" + +#: ./doc/common/tables/cinder-common.xml:70(td) +msgid "iet_conf = /etc/iet/ietd.conf" +msgstr "" + +#: ./doc/common/tables/cinder-common.xml:71(td) +msgid "(StrOpt) IET configuration file" +msgstr "" + +#: ./doc/common/tables/cinder-common.xml:74(td) +msgid "lio_initiator_iqns =" +msgstr "" + +#: ./doc/common/tables/cinder-common.xml:75(td) +msgid "(StrOpt) Comma-separated list of initiator IQNs allowed to connect to the iSCSI target. (From Nova compute nodes.)" +msgstr "" + +#: ./doc/common/tables/cinder-common.xml:119(td) +msgid "(BoolOpt) Enable monkey patching" +msgstr "" + +#: ./doc/common/tables/cinder-common.xml:122(td) +msgid "monkey_patch_modules =" +msgstr "" + +#: ./doc/common/tables/cinder-common.xml:130(td) +msgid "no_snapshot_gb_quota = False" +msgstr "" + +#: ./doc/common/tables/cinder-common.xml:131(td) +msgid "(BoolOpt) Whether snapshots count against GigaByte quota" +msgstr "" + +#: ./doc/common/tables/cinder-common.xml:134(td) +msgid "num_shell_tries = 3" +msgstr "" + +#: ./doc/common/tables/cinder-common.xml:135(td) +msgid "(IntOpt) number of times to attempt to run flakey shell commands" +msgstr "" + +#: ./doc/common/tables/cinder-common.xml:142(td) +msgid "periodic_interval = 60" +msgstr "" + +#: ./doc/common/tables/cinder-common.xml:143(td) +msgid "(IntOpt) seconds between running periodic tasks" +msgstr "" + +#: ./doc/common/tables/cinder-common.xml:155(td) +msgid "(StrOpt) Directory where the cinder python module is installed" +msgstr "" + +#: ./doc/common/tables/cinder-common.xml:162(td) +msgid "reserved_percentage = 0" +msgstr "" + +#: ./doc/common/tables/cinder-common.xml:163(td) +msgid "(IntOpt) The percentage of backend capacity is reserved" +msgstr "" + +#: ./doc/common/tables/cinder-common.xml:167(td) +msgid "(StrOpt) Deprecated: command to use for running commands as root" +msgstr "" + +#: ./doc/common/tables/cinder-common.xml:170(td) +msgid "rootwrap_config = /etc/cinder/rootwrap.conf" +msgstr "" + +#: ./doc/common/tables/cinder-common.xml:182(td) +msgid "sqlite_db = cinder.sqlite" +msgstr "" + +#: ./doc/common/tables/cinder-common.xml:203(td) +msgid "(StrOpt) Top-level directory for maintaining cinder's state" +msgstr "" + +#: ./doc/common/tables/cinder-common.xml:206(td) +msgid "storage_availability_zone = nova" +msgstr "" + +#: ./doc/common/tables/cinder-common.xml:207(td) +msgid "(StrOpt) availability zone of this node" +msgstr "" + +#: ./doc/common/tables/cinder-common.xml:226(td) ./doc/common/tables/nova-api.xml:86(td) +msgid "use_forwarded_for = False" +msgstr "" + +#: ./doc/common/tables/cinder-common.xml:227(td) ./doc/common/tables/nova-api.xml:87(td) +msgid "(BoolOpt) Treat X-Forwarded-For as the canonical remote address. Only enable this if you have a sanitizing proxy." +msgstr "" + +#: ./doc/common/tables/cinder-common.xml:253(th) ./doc/common/tables/nova-redis.xml:19(th) +msgid "[matchmaker_redis]" +msgstr "" + +#: ./doc/common/tables/cinder-common.xml:256(td) ./doc/common/tables/neutron-rpc.xml:31(td) ./doc/common/tables/neutron-nec.xml:39(td) ./doc/common/tables/nova-redis.xml:22(td) +msgid "host = 127.0.0.1" +msgstr "" + +#: ./doc/common/tables/cinder-common.xml:257(td) ./doc/common/tables/neutron-rpc.xml:32(td) ./doc/common/tables/nova-redis.xml:23(td) +msgid "(StrOpt) Host to locate redis" +msgstr "" + +#: ./doc/common/tables/cinder-common.xml:260(td) ./doc/common/tables/neutron-rpc.xml:43(td) ./doc/common/tables/ldap-keystone-conf.xml:25(td) ./doc/common/tables/nova-redis.xml:26(td) +msgid "password = None" +msgstr "" + +#: ./doc/common/tables/cinder-common.xml:261(td) ./doc/common/tables/nova-redis.xml:27(td) +msgid "(StrOpt) Password for Redis server. (optional)" +msgstr "" + +#: ./doc/common/tables/cinder-common.xml:264(td) ./doc/common/tables/neutron-rpc.xml:47(td) ./doc/common/tables/nova-redis.xml:30(td) +msgid "port = 6379" +msgstr "" + +#: ./doc/common/tables/cinder-common.xml:265(td) ./doc/common/tables/neutron-rpc.xml:48(td) ./doc/common/tables/nova-redis.xml:31(td) +msgid "(IntOpt) Use this port to connect to redis host." +msgstr "" + +#: ./doc/common/tables/cinder-common.xml:268(th) ./doc/common/tables/nova-rpc.xml:76(th) +msgid "[rpc_notifier2]" +msgstr "" + +#: ./doc/common/tables/cinder-common.xml:271(td) ./doc/common/tables/neutron-rpc.xml:79(td) ./doc/common/tables/nova-rpc.xml:79(td) +msgid "topics = notifications" +msgstr "" + +#: ./doc/common/tables/cinder-common.xml:272(td) ./doc/common/tables/nova-rpc.xml:80(td) +msgid "(ListOpt) AMQP topic(s) used for OpenStack notifications" +msgstr "" + +#: ./doc/common/tables/nova-trustedcomputing.xml:8(caption) +msgid "Description of configuration options for trustedcomputing" +msgstr "" + +#: ./doc/common/tables/nova-trustedcomputing.xml:19(th) +msgid "[trusted_computing]" +msgstr "" + +#: ./doc/common/tables/nova-trustedcomputing.xml:22(td) +msgid "attestation_api_url = /OpenAttestationWebServices/V1.0" +msgstr "" + +#: ./doc/common/tables/nova-trustedcomputing.xml:23(td) +msgid "(StrOpt) attestation web API URL" +msgstr "" + +#: ./doc/common/tables/nova-trustedcomputing.xml:26(td) +msgid "attestation_auth_blob = None" +msgstr "" + +#: ./doc/common/tables/nova-trustedcomputing.xml:27(td) +msgid "(StrOpt) attestation authorization blob - must change" +msgstr "" + +#: ./doc/common/tables/nova-trustedcomputing.xml:30(td) +msgid "attestation_auth_timeout = 60" +msgstr "" + +#: ./doc/common/tables/nova-trustedcomputing.xml:31(td) +msgid "(IntOpt) Attestation status cache valid period length" +msgstr "" + +#: ./doc/common/tables/nova-trustedcomputing.xml:34(td) +msgid "attestation_port = 8443" +msgstr "" + +#: ./doc/common/tables/nova-trustedcomputing.xml:35(td) +msgid "(StrOpt) attestation server port" +msgstr "" + +#: ./doc/common/tables/nova-trustedcomputing.xml:38(td) +msgid "attestation_server = None" +msgstr "" + +#: ./doc/common/tables/nova-trustedcomputing.xml:39(td) +msgid "(StrOpt) attestation server http" +msgstr "" + +#: ./doc/common/tables/nova-trustedcomputing.xml:42(td) +msgid "attestation_server_ca_file = None" +msgstr "" + +#: ./doc/common/tables/nova-trustedcomputing.xml:43(td) +msgid "(StrOpt) attestation server Cert file for Identity verification" +msgstr "" + +#: ./doc/common/tables/neutron-ml2_flat.xml:8(caption) +msgid "Description of configuration options for ml2_flat" +msgstr "" + +#: ./doc/common/tables/neutron-ml2_flat.xml:19(td) +msgid "flat_networks =" +msgstr "" + +#: ./doc/common/tables/neutron-ml2_flat.xml:20(td) +msgid "(ListOpt) List of physical_network names with which flat networks can be created. Use * to allow flat networks with arbitrary physical_network names." +msgstr "" + +#: ./doc/common/tables/nova-configdrive.xml:8(caption) +msgid "Description of configuration options for configdrive" +msgstr "" + +#: ./doc/common/tables/nova-configdrive.xml:22(td) +msgid "config_drive_format = iso9660" +msgstr "" + +#: ./doc/common/tables/nova-configdrive.xml:23(td) +msgid "(StrOpt) Config drive format. One of iso9660 (default) or vfat" +msgstr "" + +#: ./doc/common/tables/nova-configdrive.xml:26(td) +msgid "config_drive_skip_versions = 1.0 2007-01-19 2007-03-01 2007-08-29 2007-10-10 2007-12-15 2008-02-01 2008-09-01" +msgstr "" + +#: ./doc/common/tables/nova-configdrive.xml:27(td) +msgid "(StrOpt) List of metadata versions to skip placing into the config drive" +msgstr "" + +#: ./doc/common/tables/nova-configdrive.xml:30(td) +msgid "config_drive_tempdir = None" +msgstr "" + +#: ./doc/common/tables/nova-configdrive.xml:31(td) +msgid "(StrOpt) Where to put temporary files associated with config drive creation" +msgstr "" + +#: ./doc/common/tables/nova-configdrive.xml:34(td) +msgid "force_config_drive = None" +msgstr "" + +#: ./doc/common/tables/nova-configdrive.xml:35(td) +msgid "(StrOpt) Set to force injection to take place on a config drive (if set, valid options are: always)" +msgstr "" + +#: ./doc/common/tables/nova-configdrive.xml:38(td) +msgid "mkisofs_cmd = genisoimage" +msgstr "" + +#: ./doc/common/tables/nova-configdrive.xml:45(td) +msgid "config_drive_cdrom = False" +msgstr "" + +#: ./doc/common/tables/nova-configdrive.xml:46(td) +msgid "(BoolOpt) Attaches the Config Drive image as a cdrom drive instead of a disk drive" +msgstr "" + +#: ./doc/common/tables/nova-configdrive.xml:49(td) +msgid "config_drive_inject_password = False" +msgstr "" + +#: ./doc/common/tables/nova-configdrive.xml:50(td) +msgid "(BoolOpt) Sets the admin password in the config drive image" +msgstr "" + +#: ./doc/common/tables/cinder-database.xml:8(caption) +msgid "Description of configuration options for database" +msgstr "" + +#: ./doc/common/tables/cinder-database.xml:22(td) ./doc/common/tables/nova-baremetal.xml:22(td) +msgid "db_backend = sqlalchemy" +msgstr "" + +#: ./doc/common/tables/cinder-database.xml:26(td) +msgid "db_driver = cinder.db" +msgstr "" + +#: ./doc/common/tables/neutron-rpc.xml:27(td) +msgid "control_exchange = neutron" +msgstr "" + +#: ./doc/common/tables/neutron-rpc.xml:44(td) +msgid "(StrOpt) HTTP password for authentication" +msgstr "" + +#: ./doc/common/tables/neutron-rpc.xml:55(td) +msgid "rpc_backend = neutron.openstack.common.rpc.impl_kombu" +msgstr "" + +#: ./doc/common/tables/neutron-rpc.xml:71(td) +msgid "rpc_support_old_agents = False" +msgstr "" + +#: ./doc/common/tables/neutron-rpc.xml:72(td) +msgid "(BoolOpt) Enable server RPC compatibility with old agents" +msgstr "" + +#: ./doc/common/tables/neutron-rpc.xml:80(td) +msgid "(ListOpt) AMQP topic(s) used for openstack notifications" +msgstr "" + +#: ./doc/common/tables/nova-zeromq.xml:8(caption) ./doc/common/tables/neutron-zeromq.xml:8(caption) +msgid "Description of configuration options for zeromq" +msgstr "" + +#: ./doc/common/tables/nova-zeromq.xml:38(td) +msgid "rpc_zmq_matchmaker = nova.openstack.common.rpc.matchmaker.MatchMakerLocalhost" +msgstr "" + +#: ./doc/common/tables/glance-testing.xml:22(td) +msgid "pydev_worker_debug_host = None" +msgstr "" + +#: ./doc/common/tables/glance-testing.xml:23(td) +msgid "(StrOpt) The hostname/IP of the pydev process listening for debug connections" +msgstr "" + +#: ./doc/common/tables/glance-testing.xml:26(td) +msgid "pydev_worker_debug_port = 5678" +msgstr "" + +#: ./doc/common/tables/glance-testing.xml:27(td) +msgid "(IntOpt) The port on which a pydev process is listening for connections." +msgstr "" + +#: ./doc/common/tables/swift-proxy-server-filter-tempauth.xml:7(literal) +msgid "[filter:tempauth]" +msgstr "" + +#: ./doc/common/tables/swift-proxy-server-filter-tempauth.xml:18(td) +msgid "use = egg:swift#tempauth" +msgstr "" + +#: ./doc/common/tables/swift-proxy-server-filter-tempauth.xml:21(td) +msgid "set log_name = tempauth" +msgstr "" + +#: ./doc/common/tables/swift-proxy-server-filter-tempauth.xml:36(td) +msgid "reseller_prefix = AUTH" +msgstr "" + +#: ./doc/common/tables/swift-proxy-server-filter-tempauth.xml:36(td) +msgid "The naming scope for the auth service. Swift" +msgstr "" + +#: ./doc/common/tables/swift-proxy-server-filter-tempauth.xml:39(td) +msgid "auth_prefix = /auth/" +msgstr "" + +#: ./doc/common/tables/swift-proxy-server-filter-tempauth.xml:39(td) +msgid "The HTTP request path prefix for the auth service. Swift itself reserves anything beginning with the letter `v`." +msgstr "" + +#: ./doc/common/tables/swift-proxy-server-filter-tempauth.xml:42(td) +msgid "token_life = 86400" +msgstr "" + +#: ./doc/common/tables/swift-proxy-server-filter-tempauth.xml:42(td) +msgid "The number of seconds a token is valid." +msgstr "" + +#: ./doc/common/tables/swift-proxy-server-filter-tempauth.xml:45(td) +msgid "allow_overrides = true" +msgstr "" + +#: ./doc/common/tables/swift-proxy-server-filter-tempauth.xml:48(td) +msgid "storage_url_scheme = default" +msgstr "" + +#: ./doc/common/tables/swift-proxy-server-filter-tempauth.xml:48(td) +msgid "Scheme to return with storage urls: http, https, or default (chooses based on what the server is running as) This can be useful with an SSL load balancer in front of a non-SSL server." +msgstr "" + +#: ./doc/common/tables/swift-proxy-server-filter-tempauth.xml:51(td) +msgid "user_admin_admin = admin .admin .reseller_admin" +msgstr "" + +#: ./doc/common/tables/swift-proxy-server-filter-tempauth.xml:54(td) +msgid "user_test_tester = testing .admin" +msgstr "" + +#: ./doc/common/tables/swift-proxy-server-filter-tempauth.xml:57(td) +msgid "user_test2_tester2 = testing2 .admin" +msgstr "" + +#: ./doc/common/tables/swift-proxy-server-filter-tempauth.xml:60(td) +msgid "user_test_tester3 = testing3" +msgstr "" + +#: ./doc/common/tables/glance-registry.xml:8(caption) +msgid "Description of configuration options for registry" +msgstr "" + +#: ./doc/common/tables/glance-registry.xml:23(td) +msgid "(StrOpt) The administrators password." +msgstr "" + +#: ./doc/common/tables/glance-registry.xml:27(td) +msgid "(StrOpt) The tenant name of the administrative user." +msgstr "" + +#: ./doc/common/tables/glance-registry.xml:31(td) +msgid "(StrOpt) The administrators user name." +msgstr "" + +#: ./doc/common/tables/glance-registry.xml:35(td) +msgid "(StrOpt) The region for the authentication service." +msgstr "" + +#: ./doc/common/tables/glance-registry.xml:39(td) +msgid "(StrOpt) The strategy to use for authentication." +msgstr "" + +#: ./doc/common/tables/glance-registry.xml:43(td) +msgid "(StrOpt) The URL to the keystone service." +msgstr "" + +#: ./doc/common/tables/glance-registry.xml:46(td) +msgid "registry_client_ca_file = None" +msgstr "" + +#: ./doc/common/tables/glance-registry.xml:47(td) +msgid "(StrOpt) The path to the certifying authority cert file to use in SSL connections to the registry server." +msgstr "" + +#: ./doc/common/tables/glance-registry.xml:50(td) +msgid "registry_client_cert_file = None" +msgstr "" + +#: ./doc/common/tables/glance-registry.xml:51(td) +msgid "(StrOpt) The path to the cert file to use in SSL connections to the registry server." +msgstr "" + +#: ./doc/common/tables/glance-registry.xml:54(td) +msgid "registry_client_insecure = False" +msgstr "" + +#: ./doc/common/tables/glance-registry.xml:55(td) +msgid "(BoolOpt) When using SSL in connections to the registry server, do not require validation via a certifying authority." +msgstr "" + +#: ./doc/common/tables/glance-registry.xml:58(td) +msgid "registry_client_key_file = None" +msgstr "" + +#: ./doc/common/tables/glance-registry.xml:59(td) +msgid "(StrOpt) The path to the key file to use in SSL connections to the registry server." +msgstr "" + +#: ./doc/common/tables/glance-registry.xml:62(td) +msgid "registry_client_protocol = http" +msgstr "" + +#: ./doc/common/tables/glance-registry.xml:63(td) +msgid "(StrOpt) The protocol to use for communication with the registry server. Either http or https." +msgstr "" + +#: ./doc/common/tables/glance-registry.xml:66(td) +msgid "registry_client_timeout = 600" +msgstr "" + +#: ./doc/common/tables/glance-registry.xml:67(td) +msgid "(IntOpt) The period of time, in seconds, that the API server will wait for a registry request to complete. A value of 0 implies no timeout." +msgstr "" + +#: ./doc/common/tables/glance-registry.xml:70(td) +msgid "registry_host = 0.0.0.0" +msgstr "" + +#: ./doc/common/tables/glance-registry.xml:71(td) +msgid "(StrOpt) Address to find the registry server." +msgstr "" + +#: ./doc/common/tables/glance-registry.xml:74(td) +msgid "registry_port = 9191" +msgstr "" + +#: ./doc/common/tables/glance-registry.xml:75(td) +msgid "(IntOpt) Port the registry server is listening on." +msgstr "" + +#: ./doc/common/tables/ldap-keystone-conf.xml:4(caption) +msgid "Description of keystone.conf file configuration options for LDAP" +msgstr "" + +#: ./doc/common/tables/ldap-keystone-conf.xml:11(th) +msgid "(Type) Description" +msgstr "" + +#: ./doc/common/tables/ldap-keystone-conf.xml:16(td) +msgid "url = ldap://localhost" +msgstr "" + +#: ./doc/common/tables/ldap-keystone-conf.xml:17(td) +msgid "The location for the ldap server." +msgstr "" + +#: ./doc/common/tables/ldap-keystone-conf.xml:20(td) +msgid "user = dc=Manager,dc=example,dc=com" +msgstr "" + +#: ./doc/common/tables/ldap-keystone-conf.xml:22(td) +msgid "(StrOpt) User for the LDAP server to use as default." +msgstr "" + +#: ./doc/common/tables/ldap-keystone-conf.xml:26(td) +msgid "(StrOpt) Password for LDAP server to connect to." +msgstr "" + +#: ./doc/common/tables/ldap-keystone-conf.xml:29(td) +msgid "suffix = cn=example,cn=com" +msgstr "" + +#: ./doc/common/tables/ldap-keystone-conf.xml:31(td) +msgid "(StrOpt) Default suffix for your LDAP server." +msgstr "" + +#: ./doc/common/tables/ldap-keystone-conf.xml:33(td) +msgid "use_dumb_member = False" +msgstr "" + +#: ./doc/common/tables/ldap-keystone-conf.xml:34(td) +msgid "(Bool) Indicates whether dumb_member settings are in use." +msgstr "" + +#: ./doc/common/tables/ldap-keystone-conf.xml:36(td) +msgid "allow_subtree_delete = False" +msgstr "" + +#: ./doc/common/tables/ldap-keystone-conf.xml:38(td) +msgid "(Bool) Determine whether to delete LDAP subtrees." +msgstr "" + +#: ./doc/common/tables/ldap-keystone-conf.xml:41(td) +msgid "dumb_member = cn=dumb,dc=example,dc=com" +msgstr "" + +#: ./doc/common/tables/ldap-keystone-conf.xml:43(td) +msgid "Mockup member as placeholder, for testing purposes." +msgstr "" + +#: ./doc/common/tables/ldap-keystone-conf.xml:45(td) +msgid "query_scope = one" +msgstr "" + +#: ./doc/common/tables/ldap-keystone-conf.xml:47(td) +msgid "The LDAP scope for queries, this can be either 'one' (onelevel/singleLevel) or 'sub' (subtree/wholeSubtree)" +msgstr "" + +#: ./doc/common/tables/ldap-keystone-conf.xml:49(td) +msgid "user_tree_dn = ou=Users,dc=example,dc=com" +msgstr "" + +#: ./doc/common/tables/ldap-keystone-conf.xml:53(td) +msgid "user_filter =" +msgstr "" + +#: ./doc/common/tables/ldap-keystone-conf.xml:57(td) +msgid "user_objectclass = inetOrgPerson" +msgstr "" + +#: ./doc/common/tables/ldap-keystone-conf.xml:61(td) +msgid "user_id_attribute = cn" +msgstr "" + +#: ./doc/common/tables/ldap-keystone-conf.xml:65(td) +msgid "user_name_attribute = sn" +msgstr "" + +#: ./doc/common/tables/ldap-keystone-conf.xml:69(td) +msgid "user_mail_attribute = email" +msgstr "" + +#: ./doc/common/tables/ldap-keystone-conf.xml:73(td) +msgid "user_pass_attribute = userPassword" +msgstr "" + +#: ./doc/common/tables/ldap-keystone-conf.xml:77(td) +msgid "user_enabled_attribute = enabled" +msgstr "" + +#: ./doc/common/tables/ldap-keystone-conf.xml:79(td) +msgid "Example, userAccountControl. Combines with user_enabled_mask and user_enabled_default settings below to extract the value from an integer attribute like in Active Directory." +msgstr "" + +#: ./doc/common/tables/ldap-keystone-conf.xml:82(td) +msgid "user_enabled_mask = 0" +msgstr "" + +#: ./doc/common/tables/ldap-keystone-conf.xml:86(td) +msgid "user_enabled_default = True" +msgstr "" + +#: ./doc/common/tables/ldap-keystone-conf.xml:90(td) +msgid "user_attribute_ignore = tenant_id,tenants" +msgstr "" + +#: ./doc/common/tables/ldap-keystone-conf.xml:94(td) +msgid "user_allow_create = True" +msgstr "" + +#: ./doc/common/tables/ldap-keystone-conf.xml:96(td) +msgid "If the users are managed by another tool and you have only read access, you would set this to False." +msgstr "" + +#: ./doc/common/tables/ldap-keystone-conf.xml:98(td) +msgid "user_allow_update = True" +msgstr "" + +#: ./doc/common/tables/ldap-keystone-conf.xml:102(td) +msgid "user_allow_delete = True" +msgstr "" + +#: ./doc/common/tables/ldap-keystone-conf.xml:107(td) +msgid "tenant_tree_dn = ou=Groups,dc=example,dc=com" +msgstr "" + +#: ./doc/common/tables/ldap-keystone-conf.xml:112(td) +msgid "tenant_filter =" +msgstr "" + +#: ./doc/common/tables/ldap-keystone-conf.xml:114(td) +msgid "If the backend is providing too much output, you can set a filter to blank so tenants are not passed through." +msgstr "" + +#: ./doc/common/tables/ldap-keystone-conf.xml:116(td) +msgid "tenant_objectclass = groupOfNames" +msgstr "" + +#: ./doc/common/tables/ldap-keystone-conf.xml:120(td) +msgid "tenant_id_attribute = cn" +msgstr "" + +#: ./doc/common/tables/ldap-keystone-conf.xml:124(td) +msgid "tenant_member_attribute = member" +msgstr "" + +#: ./doc/common/tables/ldap-keystone-conf.xml:128(td) +msgid "tenant_name_attribute = ou" +msgstr "" + +#: ./doc/common/tables/ldap-keystone-conf.xml:132(td) +msgid "tenant_desc_attribute = desc" +msgstr "" + +#: ./doc/common/tables/ldap-keystone-conf.xml:136(td) +msgid "tenant_enabled_attribute = enabled" +msgstr "" + +#: ./doc/common/tables/ldap-keystone-conf.xml:140(td) +msgid "tenant_attribute_ignore =" +msgstr "" + +#: ./doc/common/tables/ldap-keystone-conf.xml:144(td) +msgid "tenant_allow_create = True" +msgstr "" + +#: ./doc/common/tables/ldap-keystone-conf.xml:148(td) +msgid "tenant_allow_update = True" +msgstr "" + +#: ./doc/common/tables/ldap-keystone-conf.xml:153(td) +msgid "tenant_allow_delete = True" +msgstr "" + +#: ./doc/common/tables/ldap-keystone-conf.xml:158(td) +msgid "role_tree_dn = ou=Roles,dc=example,dc=com" +msgstr "" + +#: ./doc/common/tables/ldap-keystone-conf.xml:163(td) +msgid "role_filter =" +msgstr "" + +#: ./doc/common/tables/ldap-keystone-conf.xml:168(td) +msgid "role_objectclass = organizationalRole" +msgstr "" + +#: ./doc/common/tables/ldap-keystone-conf.xml:173(td) +msgid "role_id_attribute = cn" +msgstr "" + +#: ./doc/common/tables/ldap-keystone-conf.xml:178(td) +msgid "role_name_attribute = ou" +msgstr "" + +#: ./doc/common/tables/ldap-keystone-conf.xml:183(td) +msgid "role_member_attribute = roleOccupant" +msgstr "" + +#: ./doc/common/tables/ldap-keystone-conf.xml:188(td) +msgid "role_attribute_ignore =" +msgstr "" + +#: ./doc/common/tables/ldap-keystone-conf.xml:193(td) +msgid "role_allow_create = True" +msgstr "" + +#: ./doc/common/tables/ldap-keystone-conf.xml:198(td) +msgid "role_allow_update = True" +msgstr "" + +#: ./doc/common/tables/ldap-keystone-conf.xml:203(td) +msgid "role_allow_delete = True" +msgstr "" + +#: ./doc/common/tables/ldap-keystone-conf.xml:208(td) +msgid "group_tree_dn =" +msgstr "" + +#: ./doc/common/tables/ldap-keystone-conf.xml:213(td) +msgid "group_filter =" +msgstr "" + +#: ./doc/common/tables/ldap-keystone-conf.xml:218(td) +msgid "group_objectclass = groupOfNames" +msgstr "" + +#: ./doc/common/tables/ldap-keystone-conf.xml:223(td) +msgid "group_id_attribute = cn" +msgstr "" + +#: ./doc/common/tables/ldap-keystone-conf.xml:228(td) +msgid "group_name_attribute = ou" +msgstr "" + +#: ./doc/common/tables/ldap-keystone-conf.xml:233(td) +msgid "group_member_attribute = member" +msgstr "" + +#: ./doc/common/tables/ldap-keystone-conf.xml:238(td) +msgid "group_desc_attribute = desc" +msgstr "" + +#: ./doc/common/tables/ldap-keystone-conf.xml:243(td) +msgid "group_attribute_ignore =" +msgstr "" + +#: ./doc/common/tables/ldap-keystone-conf.xml:248(td) +msgid "group_allow_create = True" +msgstr "" + +#: ./doc/common/tables/ldap-keystone-conf.xml:253(td) +msgid "group_allow_update = True" +msgstr "" + +#: ./doc/common/tables/ldap-keystone-conf.xml:258(td) +msgid "group_allow_delete = True" +msgstr "" + +#: ./doc/common/tables/swift-object-server-object-replicator.xml:7(literal) +msgid "[object-replicator]" +msgstr "" + +#: ./doc/common/tables/swift-object-server-object-replicator.xml:18(td) +msgid "log_name = object-replicator" +msgstr "" + +#: ./doc/common/tables/swift-object-server-object-replicator.xml:33(td) +msgid "daemonize = on" +msgstr "" + +#: ./doc/common/tables/swift-object-server-object-replicator.xml:33(td) +msgid "Whether or not to run replication as a daemon" +msgstr "" + +#: ./doc/common/tables/swift-object-server-object-replicator.xml:42(td) +msgid "stats_interval = 300" +msgstr "" + +#: ./doc/common/tables/swift-object-server-object-replicator.xml:42(td) +msgid "Interval in seconds between logging replication statistics" +msgstr "" + +#: ./doc/common/tables/swift-object-server-object-replicator.xml:45(td) +msgid "rsync_timeout = 900" +msgstr "" + +#: ./doc/common/tables/swift-object-server-object-replicator.xml:45(td) +msgid "Max duration (seconds) of a partition rsync" +msgstr "" + +#: ./doc/common/tables/swift-object-server-object-replicator.xml:48(td) +msgid "rsync_bwlimit = 0" +msgstr "" + +#: ./doc/common/tables/swift-object-server-object-replicator.xml:51(td) +msgid "rsync_io_timeout = 30" +msgstr "" + +#: ./doc/common/tables/swift-object-server-object-replicator.xml:51(td) +msgid "Passed to rsync for a max duration (seconds) of an I/O op" +msgstr "" + +#: ./doc/common/tables/swift-object-server-object-replicator.xml:54(td) +msgid "http_timeout = 60" +msgstr "" + +#: ./doc/common/tables/swift-object-server-object-replicator.xml:54(td) +msgid "Maximum duration for an HTTP request" +msgstr "" + +#: ./doc/common/tables/swift-object-server-object-replicator.xml:57(td) +msgid "lockup_timeout = 1800" +msgstr "" + +#: ./doc/common/tables/swift-object-server-object-replicator.xml:57(td) +msgid "Attempts to kill all workers if nothing replications for lockup_timeout seconds" +msgstr "" + +#: ./doc/common/tables/swift-object-server-object-replicator.xml:63(td) +msgid "ring_check_interval = 15" +msgstr "" + +#: ./doc/common/tables/swift-object-server-object-replicator.xml:63(td) +msgid "How often (in seconds) to check the ring" +msgstr "" + +#: ./doc/common/tables/swift-object-server-object-replicator.xml:69(td) +msgid "rsync_error_log_line_length = 0" +msgstr "" + +#: ./doc/common/tables/swift-dispersion-dispersion.xml:7(literal) +msgid "[dispersion]" +msgstr "" + +#: ./doc/common/tables/swift-dispersion-dispersion.xml:7(literal) +msgid "dispersion.conf-sample" +msgstr "" + +#: ./doc/common/tables/swift-dispersion-dispersion.xml:18(td) +msgid "auth_url = http://localhost:8080/auth/v1.0" +msgstr "" + +#: ./doc/common/tables/swift-dispersion-dispersion.xml:18(td) ./doc/common/tables/swift-dispersion-dispersion.xml:27(td) +msgid "Endpoint for auth server, such as keystone" +msgstr "" + +#: ./doc/common/tables/swift-dispersion-dispersion.xml:21(td) ./doc/common/tables/swift-dispersion-dispersion.xml:30(td) +msgid "auth_user = test:tester" +msgstr "" + +#: ./doc/common/tables/swift-dispersion-dispersion.xml:21(td) ./doc/common/tables/swift-dispersion-dispersion.xml:30(td) +msgid "Default user for dispersion in this context" +msgstr "" + +#: ./doc/common/tables/swift-dispersion-dispersion.xml:24(td) ./doc/common/tables/swift-dispersion-dispersion.xml:33(td) +msgid "auth_key = testing" +msgstr "" + +#: ./doc/common/tables/swift-dispersion-dispersion.xml:27(td) +msgid "auth_url = http://saio:5000/v2.0/" +msgstr "" + +#: ./doc/common/tables/swift-dispersion-dispersion.xml:36(td) +msgid "auth_version = 2.0" +msgstr "" + +#: ./doc/common/tables/swift-dispersion-dispersion.xml:39(td) +msgid "endpoint_type = publicURL" +msgstr "" + +#: ./doc/common/tables/swift-dispersion-dispersion.xml:39(td) +msgid "Indicates whether endpoint for auth is public or internal" +msgstr "" + +#: ./doc/common/tables/swift-dispersion-dispersion.xml:42(td) +msgid "keystone_api_insecure = no" +msgstr "" + +#: ./doc/common/tables/swift-dispersion-dispersion.xml:48(td) +msgid "dispersion_coverage = 1.0" +msgstr "" + +#: ./doc/common/tables/swift-dispersion-dispersion.xml:51(td) +msgid "retries = 5" +msgstr "" + +#: ./doc/common/tables/swift-dispersion-dispersion.xml:54(td) ./doc/common/tables/swift-account-server-account-reaper.xml:30(td) +msgid "concurrency = 25" +msgstr "" + +#: ./doc/common/tables/swift-dispersion-dispersion.xml:57(td) +msgid "container_report = yes" +msgstr "" + +#: ./doc/common/tables/swift-dispersion-dispersion.xml:60(td) +msgid "object_report = yes" +msgstr "" + +#: ./doc/common/tables/swift-dispersion-dispersion.xml:63(td) +msgid "dump_json = no" +msgstr "" + +#: ./doc/common/tables/swift-account-server-account-replicator.xml:7(literal) +msgid "[account-replicator]" +msgstr "" + +#: ./doc/common/tables/swift-account-server-account-replicator.xml:18(td) +msgid "log_name = account-replicator" +msgstr "" + +#: ./doc/common/tables/neutron-fwaas.xml:8(caption) +msgid "Description of configuration options for fwaas" +msgstr "" + +#: ./doc/common/tables/neutron-fwaas.xml:19(td) ./doc/common/tables/nova-spice.xml:26(td) ./doc/common/tables/nova-apiv3.xml:22(td) +msgid "enabled = False" +msgstr "" + +#: ./doc/common/tables/neutron-fwaas.xml:20(td) +msgid "(BoolOpt) Enable FWaaS" +msgstr "" + +#: ./doc/common/tables/glance-rabbitmq.xml:8(caption) ./doc/common/tables/neutron-rabbitmq.xml:8(caption) ./doc/common/tables/nova-rabbitmq.xml:8(caption) +msgid "Description of configuration options for rabbitmq" +msgstr "" + +#: ./doc/common/tables/glance-rabbitmq.xml:39(td) ./doc/common/tables/nova-kombu.xml:35(td) +msgid "(StrOpt) SSL version to use (valid only if SSL enabled). valid values are TLSv1, SSLv23 and SSLv3. SSLv2 may be available on some distributions" +msgstr "" + +#: ./doc/common/tables/cinder-backups_tsm.xml:8(caption) +msgid "Description of configuration options for backups_tsm" +msgstr "" + +#: ./doc/common/tables/cinder-backups_tsm.xml:22(td) +msgid "backup_tsm_compression = True" +msgstr "" + +#: ./doc/common/tables/cinder-backups_tsm.xml:23(td) +msgid "(BoolOpt) Enable or Disable compression for backups" +msgstr "" + +#: ./doc/common/tables/cinder-backups_tsm.xml:26(td) +msgid "backup_tsm_password = password" +msgstr "" + +#: ./doc/common/tables/cinder-backups_tsm.xml:27(td) +msgid "(StrOpt) TSM password for the running username" +msgstr "" + +#: ./doc/common/tables/cinder-backups_tsm.xml:30(td) +msgid "backup_tsm_volume_prefix = backup" +msgstr "" + +#: ./doc/common/tables/cinder-backups_tsm.xml:31(td) +msgid "(StrOpt) Volume prefix for the backup id when backing up to TSM" +msgstr "" + +#: ./doc/common/tables/cinder-connection.xml:8(caption) +msgid "Description of configuration options for connection" +msgstr "" + +#: ./doc/common/tables/cinder-connection.xml:22(td) +msgid "connection = sqlite:///$state_path/$sqlite_db" +msgstr "" + +#: ./doc/common/tables/swift-proxy-server-filter-authtoken.xml:7(literal) +msgid "[filter:authtoken]" +msgstr "" + +#: ./doc/common/tables/swift-proxy-server-filter-authtoken.xml:18(td) +msgid "auth_host = keystonehost" +msgstr "" + +#: ./doc/common/tables/swift-proxy-server-filter-authtoken.xml:21(td) +msgid "auth_port = 35357" +msgstr "" + +#: ./doc/common/tables/swift-proxy-server-filter-authtoken.xml:24(td) +msgid "auth_protocol = http" +msgstr "" + +#: ./doc/common/tables/swift-proxy-server-filter-authtoken.xml:27(td) +msgid "auth_uri = http://keystonehost:5000/" +msgstr "" + +#: ./doc/common/tables/swift-proxy-server-filter-authtoken.xml:30(td) +msgid "admin_tenant_name = service" +msgstr "" + +#: ./doc/common/tables/swift-proxy-server-filter-authtoken.xml:33(td) +msgid "admin_user = swift" +msgstr "" + +#: ./doc/common/tables/swift-proxy-server-filter-authtoken.xml:36(td) +msgid "admin_password = password" +msgstr "" + +#: ./doc/common/tables/swift-proxy-server-filter-authtoken.xml:39(td) +msgid "delay_auth_decision = 1" +msgstr "" + +#: ./doc/common/tables/swift-proxy-server-filter-authtoken.xml:42(td) +msgid "cache = swift.cache" +msgstr "" + +#: ./doc/common/tables/neutron-zeromq.xml:27(td) +msgid "rpc_zmq_host = [hostname]" +msgstr "" + +#: ./doc/common/tables/neutron-zeromq.xml:35(td) +msgid "rpc_zmq_matchmaker = neutron.openstack.common.rpc.matchmaker.MatchMakerLocalhost" +msgstr "" + +#: ./doc/common/tables/neutron-vpn.xml:19(td) +msgid "config_base_dir = $state_path/ipsec" +msgstr "" + +#: ./doc/common/tables/neutron-vpn.xml:20(td) +msgid "(StrOpt) Location to store ipsec server config files" +msgstr "" + +#: ./doc/common/tables/neutron-vpn.xml:23(td) +msgid "ipsec_config_template = /usr/lib/python2.7/site-packages/neutron/services/vpn/device_drivers/template/openswan/ipsec.conf.template" +msgstr "" + +#: ./doc/common/tables/neutron-vpn.xml:24(td) +msgid "(StrOpt) Template file for ipsec configuration" +msgstr "" + +#: ./doc/common/tables/neutron-vpn.xml:27(td) +msgid "ipsec_secret_template = /usr/lib/python2.7/site-packages/neutron/services/vpn/device_drivers/template/openswan/ipsec.secret.template" +msgstr "" + +#: ./doc/common/tables/neutron-vpn.xml:28(td) +msgid "(StrOpt) Template file for ipsec secret configuration" +msgstr "" + +#: ./doc/common/tables/neutron-vpn.xml:31(td) +msgid "ipsec_status_check_interval = 60" +msgstr "" + +#: ./doc/common/tables/neutron-vpn.xml:32(td) +msgid "(IntOpt) Interval for checking ipsec status" +msgstr "" + +#: ./doc/common/tables/neutron-vpn.xml:35(td) +msgid "vpn_device_driver = ['neutron.services.vpn.device_drivers.ipsec.OpenSwanDriver']" +msgstr "" + +#: ./doc/common/tables/neutron-vpn.xml:36(td) +msgid "(MultiStrOpt) The vpn device drivers Neutron will use" +msgstr "" + +#: ./doc/common/tables/cinder-log.xml:8(caption) +msgid "Description of configuration options for log" +msgstr "" + +#: ./doc/common/tables/neutron-agent.xml:8(caption) +msgid "Description of configuration options for agent" +msgstr "" + +#: ./doc/common/tables/neutron-agent.xml:19(td) +msgid "agent_down_time = 9" +msgstr "" + +#: ./doc/common/tables/neutron-agent.xml:20(td) +msgid "(IntOpt) Seconds to regard the agent is down; should be at least twice report_interval, to be sure the agent is down for good." +msgstr "" + +#: ./doc/common/tables/neutron-agent.xml:23(td) +msgid "external_pids = $state_path/external/pids" +msgstr "" + +#: ./doc/common/tables/neutron-agent.xml:24(td) +msgid "(StrOpt) Location to store child pid files" +msgstr "" + +#: ./doc/common/tables/neutron-agent.xml:27(td) +msgid "interface_driver = None" +msgstr "" + +#: ./doc/common/tables/neutron-agent.xml:28(td) +msgid "(StrOpt) The driver used to manage the virtual interface." +msgstr "" + +#: ./doc/common/tables/neutron-agent.xml:31(td) +msgid "report_interval = 4" +msgstr "" + +#: ./doc/common/tables/neutron-agent.xml:32(td) +msgid "(FloatOpt) Seconds between nodes reporting state to server; should be less than agent_down_time, best if it is half or less than agent_down_time." +msgstr "" + +#: ./doc/common/tables/neutron-agent.xml:35(td) +msgid "use_namespaces = True" +msgstr "" + +#: ./doc/common/tables/neutron-agent.xml:36(td) +msgid "(BoolOpt) Allow overlapping IP." +msgstr "" + +#: ./doc/common/tables/neutron-ryu.xml:8(caption) +msgid "Description of configuration options for ryu" +msgstr "" + +#: ./doc/common/tables/neutron-ryu.xml:19(td) +msgid "openflow_rest_api = 127.0.0.1:8080" +msgstr "" + +#: ./doc/common/tables/neutron-ryu.xml:20(td) +msgid "(StrOpt) OpenFlow REST API location" +msgstr "" + +#: ./doc/common/tables/neutron-ryu.xml:23(td) +msgid "ovsdb_interface = None" +msgstr "" + +#: ./doc/common/tables/neutron-ryu.xml:24(td) +msgid "(StrOpt) OVSDB interface to connect to" +msgstr "" + +#: ./doc/common/tables/neutron-ryu.xml:27(td) +msgid "ovsdb_ip = None" +msgstr "" + +#: ./doc/common/tables/neutron-ryu.xml:28(td) +msgid "(StrOpt) OVSDB IP to connect to" +msgstr "" + +#: ./doc/common/tables/neutron-ryu.xml:31(td) +msgid "ovsdb_port = 6634" +msgstr "" + +#: ./doc/common/tables/neutron-ryu.xml:32(td) +msgid "(IntOpt) OVSDB port to connect to" +msgstr "" + +#: ./doc/common/tables/neutron-ryu.xml:35(td) +msgid "tunnel_interface = None" +msgstr "" + +#: ./doc/common/tables/neutron-ryu.xml:36(td) +msgid "(StrOpt) Tunnel interface to use" +msgstr "" + +#: ./doc/common/tables/neutron-ryu.xml:39(td) +msgid "tunnel_ip = None" +msgstr "" + +#: ./doc/common/tables/neutron-ryu.xml:40(td) +msgid "(StrOpt) Tunnel IP to use" +msgstr "" + +#: ./doc/common/tables/neutron-ryu.xml:43(td) +msgid "tunnel_key_max = 16777215" +msgstr "" + +#: ./doc/common/tables/neutron-ryu.xml:44(td) +msgid "(IntOpt) Maximum tunnel ID to use" +msgstr "" + +#: ./doc/common/tables/neutron-ryu.xml:47(td) +msgid "tunnel_key_min = 1" +msgstr "" + +#: ./doc/common/tables/neutron-ryu.xml:48(td) +msgid "(IntOpt) Minimum tunnel ID to use" +msgstr "" + +#: ./doc/common/tables/swift-object-server-app-object-server.xml:7(literal) +msgid "[app:object-server]" +msgstr "" + +#: ./doc/common/tables/swift-object-server-app-object-server.xml:18(td) +msgid "use = egg:swift#object" +msgstr "" + +#: ./doc/common/tables/swift-object-server-app-object-server.xml:21(td) +msgid "set log_name = object-server" +msgstr "" + +#: ./doc/common/tables/swift-object-server-app-object-server.xml:42(td) +msgid "network_chunk_size = 65536" +msgstr "" + +#: ./doc/common/tables/swift-object-server-app-object-server.xml:42(td) +msgid "Size of chunks to read/write over the network" +msgstr "" + +#: ./doc/common/tables/swift-object-server-app-object-server.xml:45(td) +msgid "disk_chunk_size = 65536" +msgstr "" + +#: ./doc/common/tables/swift-object-server-app-object-server.xml:45(td) +msgid "Size of chunks to read/write to disk" +msgstr "" + +#: ./doc/common/tables/swift-object-server-app-object-server.xml:48(td) +msgid "max_upload_time = 86400" +msgstr "" + +#: ./doc/common/tables/swift-object-server-app-object-server.xml:48(td) +msgid "Maximum time allowed to upload an object" +msgstr "" + +#: ./doc/common/tables/swift-object-server-app-object-server.xml:51(td) +msgid "slow = 0" +msgstr "" + +#: ./doc/common/tables/swift-object-server-app-object-server.xml:51(td) +msgid "If > 0, Minimum time in seconds for a PUT or DELETE request to complete" +msgstr "" + +#: ./doc/common/tables/swift-object-server-app-object-server.xml:54(td) +msgid "keep_cache_size = 5424880" +msgstr "" + +#: ./doc/common/tables/swift-object-server-app-object-server.xml:54(td) +msgid "Largest object size to keep in buffer cache" +msgstr "" + +#: ./doc/common/tables/swift-object-server-app-object-server.xml:57(td) +msgid "keep_cache_private = false" +msgstr "" + +#: ./doc/common/tables/swift-object-server-app-object-server.xml:57(td) +msgid "Allow non-public objects to stay in kernel's buffer cache" +msgstr "" + +#: ./doc/common/tables/swift-object-server-app-object-server.xml:60(td) +msgid "mb_per_sync = 512" +msgstr "" + +#: ./doc/common/tables/swift-object-server-app-object-server.xml:60(td) +msgid "On PUT requests, sync file every n MB" +msgstr "" + +#: ./doc/common/tables/swift-object-server-app-object-server.xml:63(td) +msgid "allowed_headers = Content-Disposition, Content-Encoding, X-Delete-At, X-Object-Manifest, X-Static-Large-Object" +msgstr "" + +#: ./doc/common/tables/swift-object-server-app-object-server.xml:63(td) +msgid "Comma-separated list of headers that can be set in metadata of an object" +msgstr "" + +#: ./doc/common/tables/swift-object-server-app-object-server.xml:72(td) +msgid "threads_per_disk = 0" +msgstr "" + +#: ./doc/common/tables/swift-object-server-app-object-server.xml:72(td) +msgid "Size of the per-disk thread pool used for performing disk I/O. The default of 0 means to not use a per-disk thread pool. It is recommended to keep this value small, as large values can result in high read latencies due to large queue depths. A good starting point is 4 threads per disk." +msgstr "" + +#: ./doc/common/tables/neutron-policy.xml:19(td) +msgid "allow_overlapping_ips = False" +msgstr "" + +#: ./doc/common/tables/neutron-policy.xml:20(td) +msgid "(BoolOpt) Allow overlapping IP support in Neutron" +msgstr "" + +#: ./doc/common/tables/neutron-policy.xml:24(td) +msgid "(StrOpt) The policy file to use" +msgstr "" + +#: ./doc/common/tables/swift-proxy-server-DEFAULT.xml:21(td) +msgid "bind_port = 80" +msgstr "" + +#: ./doc/common/tables/swift-proxy-server-DEFAULT.xml:49(td) +msgid "cert_file = /etc/swift/proxy.crt" +msgstr "" + +#: ./doc/common/tables/swift-proxy-server-DEFAULT.xml:49(td) +msgid "to the ssl .crt. This should be enabled for testing purposes only." +msgstr "" + +#: ./doc/common/tables/swift-proxy-server-DEFAULT.xml:52(td) +msgid "key_file = /etc/swift/proxy.key" +msgstr "" + +#: ./doc/common/tables/swift-proxy-server-DEFAULT.xml:52(td) +msgid "to the ssl .key. This should be enabled for testing purposes only." +msgstr "" + +#: ./doc/common/tables/swift-proxy-server-DEFAULT.xml:67(td) +msgid "log_headers = false" +msgstr "" + +#: ./doc/common/tables/swift-proxy-server-DEFAULT.xml:73(td) +msgid "trans_id_suffix =" +msgstr "" + +#: ./doc/common/tables/swift-proxy-server-DEFAULT.xml:103(td) +msgid "cors_allow_origin =" +msgstr "" + +#: ./doc/common/tables/swift-proxy-server-DEFAULT.xml:103(td) +msgid "is a list of hosts that are included with any CORS request by default and returned with the Access-Control-Allow-Origin header in addition to what the container has set. to call to setup custom log handlers. for eventlet the proxy server. For most cases, this should be `egg:swift#proxy`. request whenever it has to failover to a handoff node" +msgstr "" + +#: ./doc/common/tables/swift-proxy-server-DEFAULT.xml:106(td) +msgid "client_timeout = 60" +msgstr "" + +#: ./doc/common/tables/swift-proxy-server-DEFAULT.xml:106(td) +msgid "Timeout to read one chunk from a client external services" +msgstr "" + +#: ./doc/common/tables/swift-proxy-server-filter-staticweb.xml:7(literal) +msgid "[filter:staticweb]" +msgstr "" + +#: ./doc/common/tables/swift-proxy-server-filter-staticweb.xml:18(td) +msgid "use = egg:swift#staticweb" +msgstr "" + +#: ./doc/common/tables/neutron-meta.xml:8(caption) +msgid "Description of configuration options for meta" +msgstr "" + +#: ./doc/common/tables/neutron-meta.xml:19(td) +msgid "default_flavor =" +msgstr "" + +#: ./doc/common/tables/neutron-meta.xml:20(td) +msgid "(StrOpt) Default flavor to use" +msgstr "" + +#: ./doc/common/tables/neutron-meta.xml:23(td) +msgid "default_l3_flavor =" +msgstr "" + +#: ./doc/common/tables/neutron-meta.xml:24(td) +msgid "(StrOpt) Default L3 flavor to use" +msgstr "" + +#: ./doc/common/tables/neutron-meta.xml:27(td) +msgid "extension_map =" +msgstr "" + +#: ./doc/common/tables/neutron-meta.xml:28(td) +msgid "(StrOpt) A list of extensions, per plugin, to load." +msgstr "" + +#: ./doc/common/tables/neutron-meta.xml:31(td) +msgid "l3_plugin_list =" +msgstr "" + +#: ./doc/common/tables/neutron-meta.xml:32(td) +msgid "(StrOpt) List of L3 plugins to load" +msgstr "" + +#: ./doc/common/tables/neutron-meta.xml:35(td) +msgid "plugin_list =" +msgstr "" + +#: ./doc/common/tables/neutron-meta.xml:36(td) +msgid "(StrOpt) List of plugins to load" +msgstr "" + +#: ./doc/common/tables/neutron-meta.xml:39(td) +msgid "supported_extension_aliases =" +msgstr "" + +#: ./doc/common/tables/neutron-meta.xml:40(td) +msgid "(StrOpt) Supported extension aliases" +msgstr "" + +#: ./doc/common/tables/neutron-ssl.xml:8(caption) ./doc/common/tables/glance-ssl.xml:8(caption) +msgid "Description of configuration options for ssl" +msgstr "" + +#: ./doc/common/tables/neutron-ssl.xml:20(td) +msgid "(StrOpt) Key file" +msgstr "" + +#: ./doc/common/tables/neutron-ssl.xml:35(td) ./doc/common/tables/neutron-nec.xml:51(td) +msgid "use_ssl = False" +msgstr "" + +#: ./doc/common/tables/neutron-ssl.xml:36(td) +msgid "(BoolOpt) Enable SSL on the API server" +msgstr "" + +#: ./doc/common/tables/nova-scheduling.xml:8(caption) +msgid "Description of configuration options for scheduling" +msgstr "" + +#: ./doc/common/tables/nova-scheduling.xml:22(td) +msgid "aggregate_image_properties_isolation_namespace = None" +msgstr "" + +#: ./doc/common/tables/nova-scheduling.xml:23(td) +msgid "(StrOpt) Force the filter to consider only keys matching the given namespace." +msgstr "" + +#: ./doc/common/tables/nova-scheduling.xml:26(td) +msgid "aggregate_image_properties_isolation_separator = ." +msgstr "" + +#: ./doc/common/tables/nova-scheduling.xml:27(td) +msgid "(StrOpt) The separator used between the namespace and keys" +msgstr "" + +#: ./doc/common/tables/nova-scheduling.xml:30(td) +msgid "cpu_allocation_ratio = 16.0" +msgstr "" + +#: ./doc/common/tables/nova-scheduling.xml:31(td) +msgid "(FloatOpt) Virtual CPU to physical CPU allocation ratio which affects all CPU filters. This configuration specifies a global ratio for CoreFilter. For AggregateCoreFilter, it will fall back to this configuration value if no per-aggregate setting found." +msgstr "" + +#: ./doc/common/tables/nova-scheduling.xml:34(td) +msgid "disk_allocation_ratio = 1.0" +msgstr "" + +#: ./doc/common/tables/nova-scheduling.xml:35(td) +msgid "(FloatOpt) virtual disk to physical disk allocation ratio" +msgstr "" + +#: ./doc/common/tables/nova-scheduling.xml:38(td) +msgid "isolated_hosts =" +msgstr "" + +#: ./doc/common/tables/nova-scheduling.xml:39(td) +msgid "(ListOpt) Host reserved for specific images" +msgstr "" + +#: ./doc/common/tables/nova-scheduling.xml:42(td) +msgid "isolated_images =" +msgstr "" + +#: ./doc/common/tables/nova-scheduling.xml:43(td) +msgid "(ListOpt) Images to run on isolated host" +msgstr "" + +#: ./doc/common/tables/nova-scheduling.xml:46(td) +msgid "max_instances_per_host = 50" +msgstr "" + +#: ./doc/common/tables/nova-scheduling.xml:47(td) +msgid "(IntOpt) Ignore hosts that have too many instances" +msgstr "" + +#: ./doc/common/tables/nova-scheduling.xml:50(td) +msgid "max_io_ops_per_host = 8" +msgstr "" + +#: ./doc/common/tables/nova-scheduling.xml:51(td) +msgid "(IntOpt) Ignore hosts that have too many builds/resizes/snaps/migrations" +msgstr "" + +#: ./doc/common/tables/nova-scheduling.xml:54(td) +msgid "ram_allocation_ratio = 1.5" +msgstr "" + +#: ./doc/common/tables/nova-scheduling.xml:55(td) +msgid "(FloatOpt) Virtual ram to physical ram allocation ratio which affects all ram filters. This configuration specifies a global ratio for RamFilter. For AggregateRamFilter, it will fall back to this configuration value if no per-aggregate setting found." +msgstr "" + +#: ./doc/common/tables/nova-scheduling.xml:58(td) +msgid "ram_weight_multiplier = 1.0" +msgstr "" + +#: ./doc/common/tables/nova-scheduling.xml:59(td) ./doc/common/tables/nova-scheduling.xml:118(td) +msgid "(FloatOpt) Multiplier used for weighing ram. Negative numbers mean to stack vs spread." +msgstr "" + +#: ./doc/common/tables/nova-scheduling.xml:62(td) +msgid "reserved_host_disk_mb = 0" +msgstr "" + +#: ./doc/common/tables/nova-scheduling.xml:63(td) +msgid "(IntOpt) Amount of disk in MB to reserve for the host" +msgstr "" + +#: ./doc/common/tables/nova-scheduling.xml:66(td) +msgid "reserved_host_memory_mb = 512" +msgstr "" + +#: ./doc/common/tables/nova-scheduling.xml:67(td) +msgid "(IntOpt) Amount of memory in MB to reserve for the host" +msgstr "" + +#: ./doc/common/tables/nova-scheduling.xml:70(td) +msgid "restrict_isolated_hosts_to_isolated_images = True" +msgstr "" + +#: ./doc/common/tables/nova-scheduling.xml:71(td) +msgid "(BoolOpt) Whether to force isolated hosts to run only isolated images" +msgstr "" + +#: ./doc/common/tables/nova-scheduling.xml:74(td) +msgid "scheduler_available_filters = ['nova.scheduler.filters.all_filters']" +msgstr "" + +#: ./doc/common/tables/nova-scheduling.xml:75(td) +msgid "(MultiStrOpt) Filter classes available to the scheduler which may be specified more than once. An entry of \"nova.scheduler.filters.standard_filters\" maps to all filters included with nova." +msgstr "" + +#: ./doc/common/tables/nova-scheduling.xml:78(td) +msgid "scheduler_default_filters = RetryFilter, AvailabilityZoneFilter, RamFilter, ComputeFilter, ComputeCapabilitiesFilter, ImagePropertiesFilter" +msgstr "" + +#: ./doc/common/tables/nova-scheduling.xml:79(td) ./doc/common/tables/cinder-scheduler.xml:23(td) +msgid "(ListOpt) Which filter class names to use for filtering hosts when not specified in the request." +msgstr "" + +#: ./doc/common/tables/nova-scheduling.xml:82(td) +msgid "scheduler_driver = nova.scheduler.filter_scheduler.FilterScheduler" +msgstr "" + +#: ./doc/common/tables/nova-scheduling.xml:83(td) +msgid "(StrOpt) Default driver to use for the scheduler" +msgstr "" + +#: ./doc/common/tables/nova-scheduling.xml:86(td) +msgid "scheduler_host_manager = nova.scheduler.host_manager.HostManager" +msgstr "" + +#: ./doc/common/tables/nova-scheduling.xml:87(td) ./doc/common/tables/cinder-scheduler.xml:35(td) +msgid "(StrOpt) The scheduler host manager class to use" +msgstr "" + +#: ./doc/common/tables/nova-scheduling.xml:90(td) +msgid "scheduler_host_subset_size = 1" +msgstr "" + +#: ./doc/common/tables/nova-scheduling.xml:91(td) +msgid "(IntOpt) New instances will be scheduled on a host chosen randomly from a subset of the N best hosts. This property defines the subset size that a host is chosen from. A value of 1 chooses the first host returned by the weighing functions. This value must be at least 1. Any value less than 1 will be ignored, and 1 will be used instead" +msgstr "" + +#: ./doc/common/tables/nova-scheduling.xml:94(td) ./doc/common/tables/cinder-scheduler.xml:38(td) +msgid "scheduler_json_config_location =" +msgstr "" + +#: ./doc/common/tables/nova-scheduling.xml:95(td) ./doc/common/tables/cinder-scheduler.xml:39(td) +msgid "(StrOpt) Absolute path to scheduler configuration JSON file." +msgstr "" + +#: ./doc/common/tables/nova-scheduling.xml:98(td) +msgid "scheduler_manager = nova.scheduler.manager.SchedulerManager" +msgstr "" + +#: ./doc/common/tables/nova-scheduling.xml:99(td) ./doc/common/tables/cinder-scheduler.xml:43(td) +msgid "(StrOpt) full class name for the Manager for scheduler" +msgstr "" + +#: ./doc/common/tables/nova-scheduling.xml:102(td) ./doc/common/tables/cinder-scheduler.xml:46(td) +msgid "scheduler_max_attempts = 3" +msgstr "" + +#: ./doc/common/tables/nova-scheduling.xml:103(td) +msgid "(IntOpt) Maximum number of attempts to schedule an instance" +msgstr "" + +#: ./doc/common/tables/nova-scheduling.xml:106(td) +msgid "scheduler_topic = scheduler" +msgstr "" + +#: ./doc/common/tables/nova-scheduling.xml:107(td) ./doc/common/tables/cinder-scheduler.xml:51(td) +msgid "(StrOpt) the topic scheduler nodes listen on" +msgstr "" + +#: ./doc/common/tables/nova-scheduling.xml:110(td) +msgid "scheduler_weight_classes = nova.scheduler.weights.all_weighers" +msgstr "" + +#: ./doc/common/tables/nova-scheduling.xml:111(td) +msgid "(ListOpt) Which weight class names to use for weighing hosts" +msgstr "" + +#: ./doc/common/tables/nova-scheduling.xml:117(td) +msgid "ram_weight_multiplier = 10.0" +msgstr "" + +#: ./doc/common/tables/nova-scheduling.xml:121(td) +msgid "scheduler_filter_classes = nova.cells.filters.all_filters" +msgstr "" + +#: ./doc/common/tables/nova-scheduling.xml:122(td) +msgid "(ListOpt) Filter classes the cells scheduler should use. An entry of \"nova.cells.filters.all_filters\"maps to all cells filters included with nova." +msgstr "" + +#: ./doc/common/tables/nova-scheduling.xml:125(td) +msgid "scheduler_retries = 10" +msgstr "" + +#: ./doc/common/tables/nova-scheduling.xml:126(td) +msgid "(IntOpt) How many retries when no cells are available." +msgstr "" + +#: ./doc/common/tables/nova-scheduling.xml:129(td) +msgid "scheduler_retry_delay = 2" +msgstr "" + +#: ./doc/common/tables/nova-scheduling.xml:130(td) +msgid "(IntOpt) How often to retry in seconds when no cells are available." +msgstr "" + +#: ./doc/common/tables/nova-scheduling.xml:133(td) +msgid "scheduler_weight_classes = nova.cells.weights.all_weighers" +msgstr "" + +#: ./doc/common/tables/nova-scheduling.xml:134(td) +msgid "(ListOpt) Weigher classes the cells scheduler should use. An entry of \"nova.cells.weights.all_weighers\"maps to all cell weighers included with nova." +msgstr "" + +#: ./doc/common/tables/nova-scheduling.xml:137(th) +msgid "[metrics]" +msgstr "" + +#: ./doc/common/tables/nova-scheduling.xml:140(td) +msgid "weight_multiplier = 1.0" +msgstr "" + +#: ./doc/common/tables/nova-scheduling.xml:141(td) +msgid "(FloatOpt) Multiplier used for weighing metrics." +msgstr "" + +#: ./doc/common/tables/nova-scheduling.xml:144(td) +msgid "weight_setting =" +msgstr "" + +#: ./doc/common/tables/nova-scheduling.xml:145(td) +msgid "(ListOpt) How the metrics are going to be weighed. This should be in the form of \"<name1>=<ratio1>, <name2>=<ratio2>, ...\", where <nameX> is one of the metric to be weighed, and <ratioX> is the corresponding ratio. So for \"name1=1.0, name2=-1.0\" The final weight would be name1.value * 1.0 + name2.value * -1.0." +msgstr "" + +#: ./doc/common/tables/swift-drive-audit-drive-audit.xml:7(literal) +msgid "[drive-audit]" +msgstr "" + +#: ./doc/common/tables/swift-drive-audit-drive-audit.xml:7(literal) +msgid "drive-audit.conf-sample" +msgstr "" + +#: ./doc/common/tables/swift-drive-audit-drive-audit.xml:18(td) +msgid "device_dir = /srv/node" +msgstr "" + +#: ./doc/common/tables/swift-drive-audit-drive-audit.xml:18(td) +msgid "Directory devices are mounted under" +msgstr "" + +#: ./doc/common/tables/swift-drive-audit-drive-audit.xml:30(td) +msgid "minutes = 60" +msgstr "" + +#: ./doc/common/tables/swift-drive-audit-drive-audit.xml:30(td) +msgid "Number of minutes to look back in `/var/log/kern.log`" +msgstr "" + +#: ./doc/common/tables/swift-drive-audit-drive-audit.xml:33(td) +msgid "error_limit = 1" +msgstr "" + +#: ./doc/common/tables/swift-drive-audit-drive-audit.xml:33(td) +msgid "Number of errors to find before a device is unmounted" +msgstr "" + +#: ./doc/common/tables/swift-drive-audit-drive-audit.xml:36(td) +msgid "log_file_pattern = /var/log/kern*" +msgstr "" + +#: ./doc/common/tables/swift-drive-audit-drive-audit.xml:36(td) +msgid "Location of the log file with globbing pattern to check against device errors locate device blocks with errors in the log file" +msgstr "" + +#: ./doc/common/tables/swift-drive-audit-drive-audit.xml:39(td) +msgid "regex_pattern_1 = \\berror\\b.*\\b(dm-[0-9]{1,2}\\d?)\\b" +msgstr "" + +#: ./doc/common/tables/neutron-db.xml:23(td) +msgid "connection = sqlite://" +msgstr "" + +#: ./doc/common/tables/neutron-db.xml:35(td) +msgid "dhcp_agents_per_network = 1" +msgstr "" + +#: ./doc/common/tables/neutron-db.xml:36(td) +msgid "(IntOpt) Number of DHCP agents scheduled to host a network." +msgstr "" + +#: ./doc/common/tables/neutron-db.xml:43(td) +msgid "max_overflow = 20" +msgstr "" + +#: ./doc/common/tables/neutron-db.xml:47(td) +msgid "max_pool_size = 10" +msgstr "" + +#: ./doc/common/tables/neutron-db.xml:59(td) +msgid "pool_timeout = 10" +msgstr "" + +#: ./doc/common/tables/neutron-db.xml:71(td) +msgid "sqlite_db =" +msgstr "" + +#: ./doc/common/tables/neutron-brocade.xml:8(caption) +msgid "Description of configuration options for brocade" +msgstr "" + +#: ./doc/common/tables/neutron-brocade.xml:19(td) +msgid "address =" +msgstr "" + +#: ./doc/common/tables/neutron-brocade.xml:20(td) +msgid "(StrOpt) The address of the host to SSH to" +msgstr "" + +#: ./doc/common/tables/neutron-brocade.xml:23(td) +msgid "ostype = NOS" +msgstr "" + +#: ./doc/common/tables/neutron-brocade.xml:24(td) +msgid "(StrOpt) Currently unused" +msgstr "" + +#: ./doc/common/tables/neutron-brocade.xml:27(td) +msgid "password =" +msgstr "" + +#: ./doc/common/tables/neutron-brocade.xml:28(td) +msgid "(StrOpt) The SSH password to use" +msgstr "" + +#: ./doc/common/tables/neutron-brocade.xml:31(td) +msgid "physical_interface = eth0" +msgstr "" + +#: ./doc/common/tables/neutron-brocade.xml:32(td) +msgid "(StrOpt) The network interface to use when creatinga port" +msgstr "" + +#: ./doc/common/tables/neutron-brocade.xml:35(td) +msgid "username =" +msgstr "" + +#: ./doc/common/tables/neutron-brocade.xml:36(td) +msgid "(StrOpt) The SSH username to use" +msgstr "" + +#: ./doc/common/tables/swift-object-expirer-pipeline-main.xml:18(td) +msgid "pipeline = catch_errors cache proxy-server" +msgstr "" + +#: ./doc/common/tables/neutron-linuxbridge_agent.xml:8(caption) +msgid "Description of configuration options for linuxbridge_agent" +msgstr "" + +#: ./doc/common/tables/neutron-linuxbridge_agent.xml:19(td) +msgid "enable_vxlan = False" +msgstr "" + +#: ./doc/common/tables/neutron-linuxbridge_agent.xml:20(td) +msgid "(BoolOpt) Enable VXLAN on the agent. Can be enabled when agent is managed by ml2 plugin using linuxbridge mechanism driver" +msgstr "" + +#: ./doc/common/tables/neutron-linuxbridge_agent.xml:24(td) +msgid "(BoolOpt) Extension to use alongside ml2 plugin's l2population mechanism driver. It enables the plugin to populate VXLAN forwarding table." +msgstr "" + +#: ./doc/common/tables/neutron-linuxbridge_agent.xml:27(td) ./doc/common/tables/neutron-linuxbridge_agent.xml:31(td) +msgid "physical_interface_mappings =" +msgstr "" + +#: ./doc/common/tables/neutron-linuxbridge_agent.xml:28(td) ./doc/common/tables/neutron-linuxbridge_agent.xml:32(td) +msgid "(ListOpt) List of <physical_network>:<physical_interface>" +msgstr "" + +#: ./doc/common/tables/neutron-linuxbridge_agent.xml:35(td) +msgid "tos = None" +msgstr "" + +#: ./doc/common/tables/neutron-linuxbridge_agent.xml:36(td) +msgid "(IntOpt) TOS for vxlan interface protocol packets." +msgstr "" + +#: ./doc/common/tables/neutron-linuxbridge_agent.xml:39(td) +msgid "ttl = None" +msgstr "" + +#: ./doc/common/tables/neutron-linuxbridge_agent.xml:40(td) +msgid "(IntOpt) TTL for vxlan interface protocol packets." +msgstr "" + +#: ./doc/common/tables/neutron-linuxbridge_agent.xml:43(td) +msgid "vxlan_group = 224.0.0.1" +msgstr "" + +#: ./doc/common/tables/neutron-linuxbridge_agent.xml:44(td) +msgid "(StrOpt) Multicast group for vxlan interface." +msgstr "" + +#: ./doc/common/tables/cinder-xiv.xml:8(caption) +msgid "Description of configuration options for xiv" +msgstr "" + +#: ./doc/common/tables/cinder-xiv.xml:22(td) +msgid "xiv_ds8k_connection_type = iscsi" +msgstr "" + +#: ./doc/common/tables/cinder-xiv.xml:23(td) +msgid "(StrOpt) Connection type to the IBM Storage Array (fibre_channel|iscsi)" +msgstr "" + +#: ./doc/common/tables/cinder-xiv.xml:26(td) +msgid "xiv_ds8k_proxy = xiv_ds8k_openstack.nova_proxy.XIVDS8KNovaProxy" +msgstr "" + +#: ./doc/common/tables/cinder-xiv.xml:27(td) +msgid "(StrOpt) Proxy driver that connects to the IBM Storage Array" +msgstr "" + +#: ./doc/common/tables/swift-proxy-server-filter-container-quotas.xml:7(literal) +msgid "[filter:container-quotas]" +msgstr "" + +#: ./doc/common/tables/swift-proxy-server-filter-container-quotas.xml:18(td) +msgid "use = egg:swift#container_quotas" +msgstr "" + +#: ./doc/common/tables/swift-swift-swift-hash.xml:7(literal) +msgid "[swift-hash]" +msgstr "" + +#: ./doc/common/tables/swift-swift-swift-hash.xml:18(td) +msgid "swift_hash_path_suffix = changeme" +msgstr "" + +#: ./doc/common/tables/swift-swift-swift-hash.xml:18(td) +msgid "A suffix used by hash_path to offer a bit more security when generating hashes for paths. It simply appends this value to all paths; if someone knows this suffix, it's easier for them to guess the hash a path will end up with. New installations are advised to set this parameter to a random secret, which would not be disclosed ouside the organization. The same secret needs to be used by all swift servers of the same cluster. Existing installations should set this parameter to an empty string." +msgstr "" + +#: ./doc/common/tables/swift-swift-swift-hash.xml:29(td) +msgid "swift_hash_path_prefix = changeme" +msgstr "" + +#: ./doc/common/tables/swift-swift-swift-hash.xml:29(td) +msgid "A prefix used by hash_path to offer a bit more security when generating hashes for paths. It simply appends this value to all paths; if someone knows this suffix, it's easier for them to guess the hash a path will end up with. New installations are advised to set this parameter to a random secret, which would not be disclosed ouside the organization. The same secret needs to be used by all swift servers of the same cluster. Existing installations should set this parameter to an empty string." +msgstr "" + +#: ./doc/common/tables/cinder-auth.xml:8(caption) +msgid "Description of configuration options for auth" +msgstr "" + +#: ./doc/common/tables/cinder-auth.xml:23(td) +msgid "(StrOpt) The strategy to use for auth. Supports noauth, keystone, and deprecated." +msgstr "" + +#: ./doc/common/tables/swift-proxy-server-filter-formpost.xml:7(literal) +msgid "[filter:formpost]" +msgstr "" + +#: ./doc/common/tables/swift-proxy-server-filter-formpost.xml:18(td) +msgid "use = egg:swift#formpost" +msgstr "" + +#: ./doc/common/tables/cinder-hds.xml:8(caption) +msgid "Description of configuration options for hds" +msgstr "" + +#: ./doc/common/tables/cinder-hds.xml:22(td) +msgid "hds_cinder_config_file = /opt/hds/hus/cinder_hus_conf.xml" +msgstr "" + +#: ./doc/common/tables/cinder-hds.xml:23(td) +msgid "(StrOpt) configuration file for HDS cinder plugin for HUS" +msgstr "" + +#: ./doc/common/tables/nova-spice.xml:8(caption) +msgid "Description of configuration options for spice" +msgstr "" + +#: ./doc/common/tables/nova-spice.xml:19(th) +msgid "[spice]" +msgstr "" + +#: ./doc/common/tables/nova-spice.xml:22(td) +msgid "agent_enabled = True" +msgstr "" + +#: ./doc/common/tables/nova-spice.xml:23(td) +msgid "(BoolOpt) enable spice guest agent support" +msgstr "" + +#: ./doc/common/tables/nova-spice.xml:27(td) +msgid "(BoolOpt) enable spice related features" +msgstr "" + +#: ./doc/common/tables/nova-spice.xml:30(td) +msgid "html5proxy_base_url = http://127.0.0.1:6082/spice_auto.html" +msgstr "" + +#: ./doc/common/tables/nova-spice.xml:31(td) +msgid "(StrOpt) location of spice html5 console proxy, in the form \"http://127.0.0.1:6082/spice_auto.html\"" +msgstr "" + +#: ./doc/common/tables/nova-spice.xml:34(td) +msgid "keymap = en-us" +msgstr "" + +#: ./doc/common/tables/nova-spice.xml:35(td) +msgid "(StrOpt) keymap for spice" +msgstr "" + +#: ./doc/common/tables/nova-spice.xml:38(td) +msgid "server_listen = 127.0.0.1" +msgstr "" + +#: ./doc/common/tables/nova-spice.xml:39(td) +msgid "(StrOpt) IP address on which instance spice server should listen" +msgstr "" + +#: ./doc/common/tables/nova-spice.xml:42(td) +msgid "server_proxyclient_address = 127.0.0.1" +msgstr "" + +#: ./doc/common/tables/nova-spice.xml:43(td) +msgid "(StrOpt) the address to which proxy clients (like nova-spicehtml5proxy) should connect" +msgstr "" + +#: ./doc/common/tables/neutron-midonet.xml:8(caption) +msgid "Description of configuration options for midonet" +msgstr "" + +#: ./doc/common/tables/neutron-midonet.xml:19(td) +msgid "midonet_host_uuid_path = /etc/midolman/host_uuid.properties" +msgstr "" + +#: ./doc/common/tables/neutron-midonet.xml:20(td) +msgid "(StrOpt) Path to midonet host uuid file" +msgstr "" + +#: ./doc/common/tables/neutron-midonet.xml:23(td) +msgid "midonet_uri = http://localhost:8080/midonet-api" +msgstr "" + +#: ./doc/common/tables/neutron-midonet.xml:24(td) +msgid "(StrOpt) MidoNet API server URI." +msgstr "" + +#: ./doc/common/tables/neutron-midonet.xml:27(td) +msgid "mode = dev" +msgstr "" + +#: ./doc/common/tables/neutron-midonet.xml:28(td) +msgid "(StrOpt) Operational mode. Internal dev use only." +msgstr "" + +#: ./doc/common/tables/neutron-midonet.xml:31(td) +msgid "password = passw0rd" +msgstr "" + +#: ./doc/common/tables/neutron-midonet.xml:32(td) +msgid "(StrOpt) MidoNet admin password." +msgstr "" + +#: ./doc/common/tables/neutron-midonet.xml:35(td) +msgid "project_id = 77777777-7777-7777-7777-777777777777" +msgstr "" + +#: ./doc/common/tables/neutron-midonet.xml:36(td) +msgid "(StrOpt) ID of the project that MidoNet admin userbelongs to." +msgstr "" + +#: ./doc/common/tables/neutron-midonet.xml:39(td) +msgid "provider_router_id = None" +msgstr "" + +#: ./doc/common/tables/neutron-midonet.xml:40(td) +msgid "(StrOpt) Virtual provider router ID." +msgstr "" + +#: ./doc/common/tables/neutron-midonet.xml:43(td) +msgid "username = admin" +msgstr "" + +#: ./doc/common/tables/neutron-midonet.xml:44(td) +msgid "(StrOpt) MidoNet admin username." +msgstr "" + +#: ./doc/common/tables/cinder-storwize.xml:8(caption) +msgid "Description of configuration options for storwize" +msgstr "" + +#: ./doc/common/tables/cinder-storwize.xml:22(td) +msgid "storwize_svc_connection_protocol = iSCSI" +msgstr "" + +#: ./doc/common/tables/cinder-storwize.xml:23(td) +msgid "(StrOpt) Connection protocol (iSCSI/FC)" +msgstr "" + +#: ./doc/common/tables/cinder-storwize.xml:26(td) +msgid "storwize_svc_flashcopy_timeout = 120" +msgstr "" + +#: ./doc/common/tables/cinder-storwize.xml:27(td) +msgid "(IntOpt) Maximum number of seconds to wait for FlashCopy to be prepared. Maximum value is 600 seconds (10 minutes)" +msgstr "" + +#: ./doc/common/tables/cinder-storwize.xml:30(td) +msgid "storwize_svc_iscsi_chap_enabled = True" +msgstr "" + +#: ./doc/common/tables/cinder-storwize.xml:31(td) +msgid "(BoolOpt) Configure CHAP authentication for iSCSI connections (Default: Enabled)" +msgstr "" + +#: ./doc/common/tables/cinder-storwize.xml:34(td) +msgid "storwize_svc_multihostmap_enabled = True" +msgstr "" + +#: ./doc/common/tables/cinder-storwize.xml:35(td) +msgid "(BoolOpt) Allows vdisk to multi host mapping" +msgstr "" + +#: ./doc/common/tables/cinder-storwize.xml:38(td) +msgid "storwize_svc_multipath_enabled = False" +msgstr "" + +#: ./doc/common/tables/cinder-storwize.xml:39(td) +msgid "(BoolOpt) Connect with multipath (FC only; iSCSI multipath is controlled by Nova)" +msgstr "" + +#: ./doc/common/tables/cinder-storwize.xml:42(td) +msgid "storwize_svc_vol_autoexpand = True" +msgstr "" + +#: ./doc/common/tables/cinder-storwize.xml:43(td) +msgid "(BoolOpt) Storage system autoexpand parameter for volumes (True/False)" +msgstr "" + +#: ./doc/common/tables/cinder-storwize.xml:46(td) +msgid "storwize_svc_vol_compression = False" +msgstr "" + +#: ./doc/common/tables/cinder-storwize.xml:47(td) +msgid "(BoolOpt) Storage system compression option for volumes" +msgstr "" + +#: ./doc/common/tables/cinder-storwize.xml:50(td) +msgid "storwize_svc_vol_easytier = True" +msgstr "" + +#: ./doc/common/tables/cinder-storwize.xml:51(td) +msgid "(BoolOpt) Enable Easy Tier for volumes" +msgstr "" + +#: ./doc/common/tables/cinder-storwize.xml:54(td) +msgid "storwize_svc_vol_grainsize = 256" +msgstr "" + +#: ./doc/common/tables/cinder-storwize.xml:55(td) +msgid "(IntOpt) Storage system grain size parameter for volumes (32/64/128/256)" +msgstr "" + +#: ./doc/common/tables/cinder-storwize.xml:58(td) +msgid "storwize_svc_vol_iogrp = 0" +msgstr "" + +#: ./doc/common/tables/cinder-storwize.xml:59(td) +msgid "(IntOpt) The I/O group in which to allocate volumes" +msgstr "" + +#: ./doc/common/tables/cinder-storwize.xml:62(td) +msgid "storwize_svc_vol_rsize = 2" +msgstr "" + +#: ./doc/common/tables/cinder-storwize.xml:63(td) +msgid "(IntOpt) Storage system space-efficiency parameter for volumes (percentage)" +msgstr "" + +#: ./doc/common/tables/cinder-storwize.xml:66(td) +msgid "storwize_svc_vol_warning = 0" +msgstr "" + +#: ./doc/common/tables/cinder-storwize.xml:67(td) +msgid "(IntOpt) Storage system threshold for volume capacity warnings (percentage)" +msgstr "" + +#: ./doc/common/tables/cinder-storwize.xml:70(td) +msgid "storwize_svc_volpool_name = volpool" +msgstr "" + +#: ./doc/common/tables/cinder-storwize.xml:71(td) +msgid "(StrOpt) Storage system storage pool for volumes" +msgstr "" + +#: ./doc/common/tables/cinder-solidfire.xml:8(caption) +msgid "Description of configuration options for solidfire" +msgstr "" + +#: ./doc/common/tables/cinder-solidfire.xml:22(td) +msgid "sf_account_prefix = None" +msgstr "" + +#: ./doc/common/tables/cinder-solidfire.xml:23(td) +msgid "(StrOpt) Create SolidFire accounts with this prefix. Any string can be used here, but the string \"hostname\" is special and will create a prefix using the cinder node hostsname (previous default behavior). The default is NO prefix." +msgstr "" + +#: ./doc/common/tables/cinder-solidfire.xml:26(td) +msgid "sf_allow_tenant_qos = False" +msgstr "" + +#: ./doc/common/tables/cinder-solidfire.xml:27(td) +msgid "(BoolOpt) Allow tenants to specify QOS on create" +msgstr "" + +#: ./doc/common/tables/cinder-solidfire.xml:30(td) +msgid "sf_api_port = 443" +msgstr "" + +#: ./doc/common/tables/cinder-solidfire.xml:31(td) +msgid "(IntOpt) SolidFire API port. Useful if the device api is behind a proxy on a different port." +msgstr "" + +#: ./doc/common/tables/cinder-solidfire.xml:34(td) +msgid "sf_emulate_512 = True" +msgstr "" + +#: ./doc/common/tables/cinder-solidfire.xml:35(td) +msgid "(BoolOpt) Set 512 byte emulation on volume creation;" +msgstr "" + +#: ./doc/common/tables/glance-ssl.xml:23(td) +msgid "(StrOpt) CA certificate file to use to verify connecting clients." +msgstr "" + +#: ./doc/common/tables/glance-ssl.xml:27(td) +msgid "(StrOpt) Certificate file to use when starting API server securely." +msgstr "" + +#: ./doc/common/tables/glance-ssl.xml:31(td) +msgid "(StrOpt) Private key file to use when starting API server securely." +msgstr "" + +#: ./doc/common/tables/nova-apiv3.xml:8(caption) +msgid "Description of configuration options for apiv3" +msgstr "" + +#: ./doc/common/tables/nova-apiv3.xml:19(th) +msgid "[osapi_v3]" +msgstr "" + +#: ./doc/common/tables/nova-apiv3.xml:23(td) +msgid "(BoolOpt) Whether the V3 API is enabled or not" +msgstr "" + +#: ./doc/common/tables/nova-apiv3.xml:26(td) +msgid "extensions_blacklist =" +msgstr "" + +#: ./doc/common/tables/nova-apiv3.xml:27(td) +msgid "(ListOpt) A list of v3 API extensions to never load. Specify the extension aliases here." +msgstr "" + +#: ./doc/common/tables/nova-apiv3.xml:30(td) +msgid "extensions_whitelist =" +msgstr "" + +#: ./doc/common/tables/nova-apiv3.xml:31(td) +msgid "(ListOpt) If the list is not empty then a v3 API extension will only be loaded if it exists in this list. Specify the extension aliases here." +msgstr "" + +#: ./doc/common/tables/glance-db.xml:22(td) +msgid "sqlite_db = glance.sqlite" +msgstr "" + +#: ./doc/common/tables/glance-db.xml:37(td) +msgid "connection = sqlite:////home/shaunm/Projects/glance/glance/openstack/common/db/$sqlite_db" +msgstr "" + +#: ./doc/common/tables/nova-api.xml:26(td) +msgid "enabled_apis = ec2, osapi_compute, metadata" +msgstr "" + +#: ./doc/common/tables/nova-api.xml:27(td) +msgid "(ListOpt) a list of APIs to enable by default" +msgstr "" + +#: ./doc/common/tables/nova-api.xml:30(td) +msgid "enabled_ssl_apis =" +msgstr "" + +#: ./doc/common/tables/nova-api.xml:31(td) +msgid "(ListOpt) a list of APIs with enabled SSL" +msgstr "" + +#: ./doc/common/tables/nova-api.xml:34(td) +msgid "instance_name_template = instance-%08x" +msgstr "" + +#: ./doc/common/tables/nova-api.xml:35(td) +msgid "(StrOpt) Template string to be used to generate instance names" +msgstr "" + +#: ./doc/common/tables/nova-api.xml:38(td) +msgid "multi_instance_display_name_template = %(name)s-%(uuid)s" +msgstr "" + +#: ./doc/common/tables/nova-api.xml:39(td) +msgid "(StrOpt) When creating multiple instances with a single request using the os-multiple-create API extension, this template will be used to build the display name for each instance. The benefit is that the instances end up with different hostnames. To restore legacy behavior of every instance having the same name, set this option to \"%(name)s\". Valid keys for the template are: name, uuid, count." +msgstr "" + +#: ./doc/common/tables/nova-api.xml:42(td) +msgid "non_inheritable_image_properties = cache_in_nova, bittorrent" +msgstr "" + +#: ./doc/common/tables/nova-api.xml:43(td) +msgid "(ListOpt) These are image properties which a snapshot should not inherit from an instance" +msgstr "" + +#: ./doc/common/tables/nova-api.xml:46(td) +msgid "null_kernel = nokernel" +msgstr "" + +#: ./doc/common/tables/nova-api.xml:47(td) +msgid "(StrOpt) kernel image that indicates not to use a kernel, but to use a raw disk image instead" +msgstr "" + +#: ./doc/common/tables/nova-api.xml:50(td) +msgid "osapi_compute_ext_list =" +msgstr "" + +#: ./doc/common/tables/nova-api.xml:51(td) +msgid "(ListOpt) Specify list of extensions to load when using osapi_compute_extension option with nova.api.openstack.compute.contrib.select_extensions" +msgstr "" + +#: ./doc/common/tables/nova-api.xml:54(td) +msgid "osapi_compute_extension = ['nova.api.openstack.compute.contrib.standard_extensions']" +msgstr "" + +#: ./doc/common/tables/nova-api.xml:55(td) +msgid "(MultiStrOpt) osapi compute extension to load" +msgstr "" + +#: ./doc/common/tables/nova-api.xml:58(td) +msgid "osapi_compute_link_prefix = None" +msgstr "" + +#: ./doc/common/tables/nova-api.xml:59(td) +msgid "(StrOpt) Base URL that will be presented to users in links to the OpenStack Compute API" +msgstr "" + +#: ./doc/common/tables/nova-api.xml:62(td) +msgid "osapi_compute_listen = 0.0.0.0" +msgstr "" + +#: ./doc/common/tables/nova-api.xml:63(td) +msgid "(StrOpt) The IP address on which the OpenStack API will listen." +msgstr "" + +#: ./doc/common/tables/nova-api.xml:66(td) +msgid "osapi_compute_listen_port = 8774" +msgstr "" + +#: ./doc/common/tables/nova-api.xml:67(td) +msgid "(IntOpt) The port on which the OpenStack API will listen." +msgstr "" + +#: ./doc/common/tables/nova-api.xml:70(td) +msgid "osapi_compute_workers = None" +msgstr "" + +#: ./doc/common/tables/nova-api.xml:71(td) +msgid "(IntOpt) Number of workers for OpenStack API service" +msgstr "" + +#: ./doc/common/tables/nova-api.xml:74(td) +msgid "osapi_hide_server_address_states = building" +msgstr "" + +#: ./doc/common/tables/nova-api.xml:75(td) +msgid "(ListOpt) List of instance states that should hide network info" +msgstr "" + +#: ./doc/common/tables/nova-api.xml:78(td) +msgid "servicegroup_driver = db" +msgstr "" + +#: ./doc/common/tables/nova-api.xml:79(td) +msgid "(StrOpt) The driver for servicegroup service (valid options are: db, zk, mc)" +msgstr "" + +#: ./doc/common/tables/swift-rsyncd-container.xml:7(literal) +msgid "[container]" +msgstr "" + +#: ./doc/common/tables/swift-rsyncd-container.xml:18(td) +msgid "max connections = 4" +msgstr "" + +#: ./doc/common/tables/swift-rsyncd-container.xml:27(td) +msgid "lock file = /var/lock/container.lock" +msgstr "" + +#: ./doc/common/tables/cinder-san-solaris.xml:8(caption) +msgid "Description of configuration options for san-solaris" +msgstr "" + +#: ./doc/common/tables/cinder-san-solaris.xml:22(td) +msgid "san_zfs_volume_base = rpool/" +msgstr "" + +#: ./doc/common/tables/cinder-san-solaris.xml:23(td) +msgid "(StrOpt) The ZFS path under which to create zvols for volumes." +msgstr "" + +#: ./doc/common/tables/cinder-netapp_cdot_nfs.xml:8(caption) +msgid "Description of configuration options for netapp_cdot_nfs" +msgstr "" + +#: ./doc/common/tables/glance-paste.xml:8(caption) +msgid "Description of configuration options for paste" +msgstr "" + +#: ./doc/common/tables/glance-paste.xml:19(th) +msgid "[paste_deploy]" +msgstr "" + +#: ./doc/common/tables/glance-paste.xml:22(td) +msgid "config_file = None" +msgstr "" + +#: ./doc/common/tables/glance-paste.xml:23(td) +msgid "(StrOpt) Name of the paste configuration file." +msgstr "" + +#: ./doc/common/tables/glance-paste.xml:26(td) +msgid "flavor = None" +msgstr "" + +#: ./doc/common/tables/glance-paste.xml:27(td) +msgid "(StrOpt) Partial name of a pipeline in your paste configuration file with the service name removed. For example, if your paste section name is [pipeline:glance-api-keystone] use the value \"keystone\"" +msgstr "" + +#: ./doc/common/tables/neutron-quotas.xml:8(caption) +msgid "Description of configuration options for quotas" +msgstr "" + +#: ./doc/common/tables/neutron-quotas.xml:19(td) +msgid "default_quota = -1" +msgstr "" + +#: ./doc/common/tables/neutron-quotas.xml:20(td) +msgid "(IntOpt) Default number of resource allowed per tenant. A negative value means unlimited." +msgstr "" + +#: ./doc/common/tables/neutron-quotas.xml:23(td) +msgid "max_routes = 30" +msgstr "" + +#: ./doc/common/tables/neutron-quotas.xml:24(td) +msgid "(IntOpt) Maximum number of routes" +msgstr "" + +#: ./doc/common/tables/neutron-quotas.xml:27(td) +msgid "quota_driver = neutron.db.quota_db.DbQuotaDriver" +msgstr "" + +#: ./doc/common/tables/neutron-quotas.xml:28(td) +msgid "(StrOpt) Default driver to use for quota checks" +msgstr "" + +#: ./doc/common/tables/neutron-quotas.xml:31(td) +msgid "quota_firewall = 1" +msgstr "" + +#: ./doc/common/tables/neutron-quotas.xml:32(td) +msgid "(IntOpt) Number of firewalls allowed per tenant. A negative value means unlimited." +msgstr "" + +#: ./doc/common/tables/neutron-quotas.xml:35(td) +msgid "quota_firewall_policy = 1" +msgstr "" + +#: ./doc/common/tables/neutron-quotas.xml:36(td) +msgid "(IntOpt) Number of firewall policies allowed per tenant. A negative value means unlimited." +msgstr "" + +#: ./doc/common/tables/neutron-quotas.xml:39(td) +msgid "quota_firewall_rule = -1" +msgstr "" + +#: ./doc/common/tables/neutron-quotas.xml:40(td) +msgid "(IntOpt) Number of firewall rules allowed per tenant. A negative value means unlimited." +msgstr "" + +#: ./doc/common/tables/neutron-quotas.xml:43(td) +msgid "quota_floatingip = 50" +msgstr "" + +#: ./doc/common/tables/neutron-quotas.xml:44(td) +msgid "(IntOpt) Number of floating IPs allowed per tenant. A negative value means unlimited." +msgstr "" + +#: ./doc/common/tables/neutron-quotas.xml:47(td) +msgid "quota_items = network, subnet, port" +msgstr "" + +#: ./doc/common/tables/neutron-quotas.xml:48(td) +msgid "(ListOpt) Resource name(s) that are supported in quota features" +msgstr "" + +#: ./doc/common/tables/neutron-quotas.xml:51(td) +msgid "quota_network = 10" +msgstr "" + +#: ./doc/common/tables/neutron-quotas.xml:52(td) +msgid "(IntOpt) Number of networks allowed per tenant.A negative value means unlimited." +msgstr "" + +#: ./doc/common/tables/neutron-quotas.xml:55(td) +msgid "quota_network_gateway = 5" +msgstr "" + +#: ./doc/common/tables/neutron-quotas.xml:56(td) +msgid "(IntOpt) Number of network gateways allowed per tenant, -1 for unlimited" +msgstr "" + +#: ./doc/common/tables/neutron-quotas.xml:59(td) +msgid "quota_packet_filter = 100" +msgstr "" + +#: ./doc/common/tables/neutron-quotas.xml:60(td) +msgid "(IntOpt) Number of packet_filters allowed per tenant, -1 for unlimited" +msgstr "" + +#: ./doc/common/tables/neutron-quotas.xml:63(td) +msgid "quota_port = 50" +msgstr "" + +#: ./doc/common/tables/neutron-quotas.xml:64(td) +msgid "(IntOpt) Number of ports allowed per tenant. A negative value means unlimited." +msgstr "" + +#: ./doc/common/tables/neutron-quotas.xml:67(td) +msgid "quota_router = 10" +msgstr "" + +#: ./doc/common/tables/neutron-quotas.xml:68(td) +msgid "(IntOpt) Number of routers allowed per tenant. A negative value means unlimited." +msgstr "" + +#: ./doc/common/tables/neutron-quotas.xml:71(td) +msgid "quota_security_group = 10" +msgstr "" + +#: ./doc/common/tables/neutron-quotas.xml:72(td) +msgid "(IntOpt) Number of security groups allowed per tenant. A negative value means unlimited." +msgstr "" + +#: ./doc/common/tables/neutron-quotas.xml:75(td) +msgid "quota_security_group_rule = 100" +msgstr "" + +#: ./doc/common/tables/neutron-quotas.xml:76(td) +msgid "(IntOpt) Number of security rules allowed per tenant. A negative value means unlimited." +msgstr "" + +#: ./doc/common/tables/neutron-quotas.xml:79(td) +msgid "quota_subnet = 10" +msgstr "" + +#: ./doc/common/tables/neutron-quotas.xml:80(td) +msgid "(IntOpt) Number of subnets allowed per tenant, A negative value means unlimited." +msgstr "" + +#: ./doc/common/tables/nova-rpc.xml:42(td) +msgid "rpc_backend = nova.openstack.common.rpc.impl_kombu" +msgstr "" + +#: ./doc/common/tables/nova-rpc.xml:65(td) +msgid "rpc_driver_queue_base = cells.intercell" +msgstr "" + +#: ./doc/common/tables/nova-rpc.xml:66(td) +msgid "(StrOpt) Base queue name to use when communicating between cells. Various topics by message type will be appended to this." +msgstr "" + +#: ./doc/common/tables/nova-rpc.xml:83(th) ./doc/common/tables/nova-upgrade_levels.xml:26(th) +msgid "[upgrade_levels]" +msgstr "" + +#: ./doc/common/tables/nova-rpc.xml:86(td) +msgid "baseapi = None" +msgstr "" + +#: ./doc/common/tables/nova-rpc.xml:87(td) +msgid "(StrOpt) Set a version cap for messages sent to the base api in any service" +msgstr "" + +#: ./doc/common/tables/nova-baremetal.xml:8(caption) +msgid "Description of configuration options for baremetal" +msgstr "" + +#: ./doc/common/tables/nova-baremetal.xml:23(td) +msgid "(StrOpt) The backend to use for bare-metal database" +msgstr "" + +#: ./doc/common/tables/nova-baremetal.xml:26(td) +msgid "deploy_kernel = None" +msgstr "" + +#: ./doc/common/tables/nova-baremetal.xml:27(td) +msgid "(StrOpt) Default kernel image ID used in deployment phase" +msgstr "" + +#: ./doc/common/tables/nova-baremetal.xml:30(td) +msgid "deploy_ramdisk = None" +msgstr "" + +#: ./doc/common/tables/nova-baremetal.xml:31(td) +msgid "(StrOpt) Default ramdisk image ID used in deployment phase" +msgstr "" + +#: ./doc/common/tables/nova-baremetal.xml:34(td) +msgid "driver = nova.virt.baremetal.pxe.PXE" +msgstr "" + +#: ./doc/common/tables/nova-baremetal.xml:35(td) +msgid "(StrOpt) Baremetal driver back-end (pxe or tilera)" +msgstr "" + +#: ./doc/common/tables/nova-baremetal.xml:38(td) +msgid "flavor_extra_specs =" +msgstr "" + +#: ./doc/common/tables/nova-baremetal.xml:39(td) +msgid "(ListOpt) a list of additional capabilities corresponding to flavor_extra_specs for this compute host to advertise. Valid entries are name=value, pairs For example, \"key1:val1, key2:val2\"" +msgstr "" + +#: ./doc/common/tables/nova-baremetal.xml:42(td) +msgid "ipmi_power_retry = 10" +msgstr "" + +#: ./doc/common/tables/nova-baremetal.xml:43(td) +msgid "(IntOpt) maximal number of retries for IPMI operations" +msgstr "" + +#: ./doc/common/tables/nova-baremetal.xml:46(td) +msgid "net_config_template = $pybasedir/nova/virt/baremetal/net-dhcp.ubuntu.template" +msgstr "" + +#: ./doc/common/tables/nova-baremetal.xml:47(td) +msgid "(StrOpt) Template file for injected network config" +msgstr "" + +#: ./doc/common/tables/nova-baremetal.xml:50(td) +msgid "power_manager = nova.virt.baremetal.ipmi.IPMI" +msgstr "" + +#: ./doc/common/tables/nova-baremetal.xml:51(td) +msgid "(StrOpt) Baremetal power management method" +msgstr "" + +#: ./doc/common/tables/nova-baremetal.xml:54(td) +msgid "pxe_append_params = nofb nomodeset vga=normal" +msgstr "" + +#: ./doc/common/tables/nova-baremetal.xml:55(td) +msgid "(StrOpt) additional append parameters for baremetal PXE boot" +msgstr "" + +#: ./doc/common/tables/nova-baremetal.xml:58(td) +msgid "pxe_bootfile_name = pxelinux.0" +msgstr "" + +#: ./doc/common/tables/nova-baremetal.xml:59(td) +msgid "(StrOpt) This gets passed to Neutron as the bootfile dhcp parameter when the dhcp_options_enabled is set." +msgstr "" + +#: ./doc/common/tables/nova-baremetal.xml:62(td) +msgid "pxe_config_template = $pybasedir/nova/virt/baremetal/pxe_config.template" +msgstr "" + +#: ./doc/common/tables/nova-baremetal.xml:63(td) +msgid "(StrOpt) Template file for PXE configuration" +msgstr "" + +#: ./doc/common/tables/nova-baremetal.xml:66(td) +msgid "pxe_deploy_timeout = 0" +msgstr "" + +#: ./doc/common/tables/nova-baremetal.xml:67(td) +msgid "(IntOpt) Timeout for PXE deployments. Default: 0 (unlimited)" +msgstr "" + +#: ./doc/common/tables/nova-baremetal.xml:70(td) +msgid "pxe_network_config = False" +msgstr "" + +#: ./doc/common/tables/nova-baremetal.xml:71(td) +msgid "(BoolOpt) If set, pass the network configuration details to the initramfs via cmdline." +msgstr "" + +#: ./doc/common/tables/nova-baremetal.xml:74(td) +msgid "sql_connection = sqlite:///$state_path/baremetal_$sqlite_db" +msgstr "" + +#: ./doc/common/tables/nova-baremetal.xml:75(td) +msgid "(StrOpt) The SQLAlchemy connection string used to connect to the bare-metal database" +msgstr "" + +#: ./doc/common/tables/nova-baremetal.xml:78(td) +msgid "terminal = shellinaboxd" +msgstr "" + +#: ./doc/common/tables/nova-baremetal.xml:79(td) +msgid "(StrOpt) path to baremetal terminal program" +msgstr "" + +#: ./doc/common/tables/nova-baremetal.xml:82(td) +msgid "terminal_cert_dir = None" +msgstr "" + +#: ./doc/common/tables/nova-baremetal.xml:83(td) +msgid "(StrOpt) path to baremetal terminal SSL cert(PEM)" +msgstr "" + +#: ./doc/common/tables/nova-baremetal.xml:86(td) +msgid "terminal_pid_dir = $state_path/baremetal/console" +msgstr "" + +#: ./doc/common/tables/nova-baremetal.xml:87(td) +msgid "(StrOpt) path to directory stores pidfiles of baremetal_terminal" +msgstr "" + +#: ./doc/common/tables/nova-baremetal.xml:90(td) +msgid "tftp_root = /tftpboot" +msgstr "" + +#: ./doc/common/tables/nova-baremetal.xml:91(td) +msgid "(StrOpt) Baremetal compute node's tftp root path" +msgstr "" + +#: ./doc/common/tables/nova-baremetal.xml:94(td) +msgid "use_file_injection = True" +msgstr "" + +#: ./doc/common/tables/nova-baremetal.xml:95(td) +msgid "(BoolOpt) If True, enable file injection for network info, files and admin password" +msgstr "" + +#: ./doc/common/tables/nova-baremetal.xml:98(td) +msgid "use_unsafe_iscsi = False" +msgstr "" + +#: ./doc/common/tables/nova-baremetal.xml:99(td) +msgid "(BoolOpt) Do not set this out of dev/test environments. If a node does not have a fixed PXE IP address, volumes are exported with globally opened ACL" +msgstr "" + +#: ./doc/common/tables/nova-baremetal.xml:102(td) +msgid "vif_driver = nova.virt.baremetal.vif_driver.BareMetalVIFDriver" +msgstr "" + +#: ./doc/common/tables/nova-baremetal.xml:103(td) +msgid "(StrOpt) Baremetal VIF driver." +msgstr "" + +#: ./doc/common/tables/nova-baremetal.xml:106(td) +msgid "virtual_power_host_key = None" +msgstr "" + +#: ./doc/common/tables/nova-baremetal.xml:107(td) +msgid "(StrOpt) ssh key for virtual power host_user" +msgstr "" + +#: ./doc/common/tables/nova-baremetal.xml:110(td) +msgid "virtual_power_host_pass =" +msgstr "" + +#: ./doc/common/tables/nova-baremetal.xml:111(td) +msgid "(StrOpt) password for virtual power host_user" +msgstr "" + +#: ./doc/common/tables/nova-baremetal.xml:114(td) +msgid "virtual_power_host_user =" +msgstr "" + +#: ./doc/common/tables/nova-baremetal.xml:115(td) +msgid "(StrOpt) user to execute virtual power commands as" +msgstr "" + +#: ./doc/common/tables/nova-baremetal.xml:118(td) +msgid "virtual_power_ssh_host =" +msgstr "" + +#: ./doc/common/tables/nova-baremetal.xml:119(td) +msgid "(StrOpt) ip or name to virtual power host" +msgstr "" + +#: ./doc/common/tables/nova-baremetal.xml:122(td) +msgid "virtual_power_ssh_port = 22" +msgstr "" + +#: ./doc/common/tables/nova-baremetal.xml:123(td) +msgid "(IntOpt) Port to use for ssh to virtual power host" +msgstr "" + +#: ./doc/common/tables/nova-baremetal.xml:126(td) +msgid "virtual_power_type = virsh" +msgstr "" + +#: ./doc/common/tables/nova-baremetal.xml:127(td) +msgid "(StrOpt) base command to use for virtual power(vbox,virsh)" +msgstr "" + +#: ./doc/common/tables/nova-baremetal.xml:133(td) +msgid "vif_driver = nova.virt.xenapi.vif.XenAPIBridgeDriver" +msgstr "" + +#: ./doc/common/tables/nova-baremetal.xml:134(td) +msgid "(StrOpt) The XenAPI VIF driver using XenServer Network APIs." +msgstr "" + +#: ./doc/common/tables/swift-account-server-pipeline-main.xml:18(td) +msgid "pipeline = healthcheck recon account-server" +msgstr "" + +#: ./doc/common/tables/glance-api.xml:22(td) +msgid "admin_role = admin" +msgstr "" + +#: ./doc/common/tables/glance-api.xml:23(td) +msgid "(StrOpt) Role used to identify an authenticated user as administrator." +msgstr "" + +#: ./doc/common/tables/glance-api.xml:26(td) +msgid "allow_anonymous_access = False" +msgstr "" + +#: ./doc/common/tables/glance-api.xml:27(td) +msgid "(BoolOpt) Allow unauthenticated users to access the API with read-only privileges. This only applies when using ContextMiddleware." +msgstr "" + +#: ./doc/common/tables/glance-api.xml:30(td) +msgid "default_publisher_id = image.localhost" +msgstr "" + +#: ./doc/common/tables/glance-api.xml:34(td) +msgid "default_store = file" +msgstr "" + +#: ./doc/common/tables/glance-api.xml:35(td) +msgid "(StrOpt) Default scheme to use to store image data. The scheme must be registered by one of the stores defined by the 'known_stores' config option." +msgstr "" + +#: ./doc/common/tables/glance-api.xml:39(td) +msgid "(BoolOpt) Deploy the v1 OpenStack Images API." +msgstr "" + +#: ./doc/common/tables/glance-api.xml:43(td) +msgid "(BoolOpt) Deploy the v2 OpenStack Images API." +msgstr "" + +#: ./doc/common/tables/glance-api.xml:46(td) +msgid "image_size_cap = 1099511627776" +msgstr "" + +#: ./doc/common/tables/glance-api.xml:47(td) +msgid "(IntOpt) Maximum size of image a user can upload in bytes. Defaults to 1099511627776 bytes (1 TB)." +msgstr "" + +#: ./doc/common/tables/glance-api.xml:50(td) +msgid "known_stores = glance.store.filesystem.Store, glance.store.http.Store, glance.store.rbd.Store, glance.store.s3.Store, glance.store.swift.Store, glance.store.sheepdog.Store, glance.store.cinder.Store" +msgstr "" + +#: ./doc/common/tables/glance-api.xml:51(td) +msgid "(ListOpt) List of which store classes and store class locations are currently known to glance at startup." +msgstr "" + +#: ./doc/common/tables/glance-api.xml:54(td) +msgid "owner_is_tenant = True" +msgstr "" + +#: ./doc/common/tables/glance-api.xml:55(td) +msgid "(BoolOpt) When true, this option sets the owner of an image to be the tenant. Otherwise, the owner of the image will be the authenticated user issuing the request." +msgstr "" + +#: ./doc/common/tables/glance-api.xml:58(td) +msgid "send_identity_headers = False" +msgstr "" + +#: ./doc/common/tables/glance-api.xml:59(td) +msgid "(BoolOpt) Whether to pass through headers containing user and tenant information when making requests to the registry. This allows the registry to use the context middleware without the keystoneclients' auth_token middleware, removing calls to the keystone auth service. It is recommended that when using this option, secure communication between glance api and glance registry is ensured by means other than auth_token middleware." +msgstr "" + +#: ./doc/common/tables/glance-api.xml:62(td) +msgid "show_multiple_locations = False" +msgstr "" + +#: ./doc/common/tables/glance-api.xml:63(td) +msgid "(BoolOpt) Whether to include the backend image locations in image properties. Revealing storage location can be a security risk, so use this setting with caution! The overrides show_image_direct_url." +msgstr "" + +#: ./doc/common/tables/glance-api.xml:66(td) +msgid "use_user_token = True" +msgstr "" + +#: ./doc/common/tables/glance-api.xml:67(td) +msgid "(BoolOpt) Whether to pass through the user token when making requests to the registry." +msgstr "" + +#: ./doc/common/tables/cinder-scheduler.xml:22(td) +msgid "scheduler_default_filters = AvailabilityZoneFilter, CapacityFilter, CapabilitiesFilter" +msgstr "" + +#: ./doc/common/tables/cinder-scheduler.xml:26(td) +msgid "scheduler_default_weighers = CapacityWeigher" +msgstr "" + +#: ./doc/common/tables/cinder-scheduler.xml:27(td) +msgid "(ListOpt) Which weigher class names to use for weighing hosts." +msgstr "" + +#: ./doc/common/tables/cinder-scheduler.xml:30(td) +msgid "scheduler_driver = cinder.scheduler.filter_scheduler.FilterScheduler" +msgstr "" + +#: ./doc/common/tables/cinder-scheduler.xml:31(td) +msgid "(StrOpt) Default scheduler driver to use" +msgstr "" + +#: ./doc/common/tables/cinder-scheduler.xml:34(td) +msgid "scheduler_host_manager = cinder.scheduler.host_manager.HostManager" +msgstr "" + +#: ./doc/common/tables/cinder-scheduler.xml:42(td) +msgid "scheduler_manager = cinder.scheduler.manager.SchedulerManager" +msgstr "" + +#: ./doc/common/tables/cinder-scheduler.xml:47(td) +msgid "(IntOpt) Maximum number of attempts to schedule an volume" +msgstr "" + +#: ./doc/common/tables/cinder-scheduler.xml:50(td) +msgid "scheduler_topic = cinder-scheduler" +msgstr "" + +#: ./doc/common/tables/neutron-ml2_ncs.xml:8(caption) +msgid "Description of configuration options for ml2_ncs" +msgstr "" + +#: ./doc/common/tables/neutron-ml2_ncs.xml:20(td) +msgid "(IntOpt) HTTP timeout in seconds." +msgstr "" + +#: ./doc/common/tables/neutron-ml2_ncs.xml:23(td) +msgid "url = None" +msgstr "" + +#: ./doc/common/tables/neutron-ml2_ncs.xml:24(td) +msgid "(StrOpt) HTTP URL of Tail-f NCS REST interface." +msgstr "" + +#: ./doc/common/tables/neutron-nec.xml:8(caption) +msgid "Description of configuration options for nec" +msgstr "" + +#: ./doc/common/tables/neutron-nec.xml:20(td) +msgid "(StrOpt) Certificate file" +msgstr "" + +#: ./doc/common/tables/neutron-nec.xml:23(td) +msgid "default_router_provider = l3-agent" +msgstr "" + +#: ./doc/common/tables/neutron-nec.xml:24(td) +msgid "(StrOpt) Default router provider to use." +msgstr "" + +#: ./doc/common/tables/neutron-nec.xml:27(td) +msgid "driver = neutron.services.firewall.drivers.fwaas_base.NoopFwaasDriver" +msgstr "" + +#: ./doc/common/tables/neutron-nec.xml:28(td) +msgid "(StrOpt) Name of the FWaaS Driver" +msgstr "" + +#: ./doc/common/tables/neutron-nec.xml:31(td) +msgid "driver = trema" +msgstr "" + +#: ./doc/common/tables/neutron-nec.xml:32(td) +msgid "(StrOpt) Driver to use" +msgstr "" + +#: ./doc/common/tables/neutron-nec.xml:35(td) +msgid "enable_packet_filter = True" +msgstr "" + +#: ./doc/common/tables/neutron-nec.xml:36(td) +msgid "(BoolOpt) Enable packet filter" +msgstr "" + +#: ./doc/common/tables/neutron-nec.xml:40(td) +msgid "(StrOpt) Host to connect to" +msgstr "" + +#: ./doc/common/tables/neutron-nec.xml:43(td) +msgid "port = 8888" +msgstr "" + +#: ./doc/common/tables/neutron-nec.xml:44(td) +msgid "(StrOpt) Port to connect to" +msgstr "" + +#: ./doc/common/tables/neutron-nec.xml:47(td) +msgid "router_providers = l3-agent, openflow" +msgstr "" + +#: ./doc/common/tables/neutron-nec.xml:48(td) +msgid "(ListOpt) List of enabled router providers." +msgstr "" + +#: ./doc/common/tables/neutron-nec.xml:52(td) +msgid "(BoolOpt) Use SSL to connect" +msgstr "" + +#: ./doc/common/tables/swift-object-expirer-object-expirer.xml:7(literal) +msgid "[object-expirer]" +msgstr "" + +#: ./doc/common/tables/swift-object-expirer-object-expirer.xml:24(td) +msgid "report_interval = 300" +msgstr "" + +#: ./doc/common/tables/swift-object-expirer-object-expirer.xml:30(td) +msgid "processes = 0" +msgstr "" + +#: ./doc/common/tables/swift-object-expirer-object-expirer.xml:33(td) +msgid "process = 0" +msgstr "" + +#: ./doc/common/tables/swift-object-expirer-object-expirer.xml:33(td) +msgid "(it will actually accept(2) N + 1). Setting this to one (1) will only handle one request at a time, without accepting another request concurrently." +msgstr "" + +#: ./doc/common/tables/glance-cinder.xml:8(caption) +msgid "Description of configuration options for cinder" +msgstr "" + +#: ./doc/common/tables/glance-cinder.xml:27(td) +msgid "(StrOpt) Location of ca certicates file to use for cinder client requests." +msgstr "" + +#: ./doc/common/tables/nova-redis.xml:8(caption) +msgid "Description of configuration options for redis" +msgstr "" + +#: ./doc/common/tables/nova-redis.xml:34(th) +msgid "[remote_debug]" +msgstr "" + +#: ./doc/common/tables/nova-redis.xml:37(td) +msgid "host = None" +msgstr "" + +#: ./doc/common/tables/nova-redis.xml:38(td) +msgid "(StrOpt) Debug host (ip or name) to connect. Note that using the remote debug option changes how Nova uses the eventlet library to support async IO. This could result in failures that do not occur under normal operation. Use at your own risk." +msgstr "" + +#: ./doc/common/tables/nova-redis.xml:41(td) +msgid "port = None" +msgstr "" + +#: ./doc/common/tables/nova-redis.xml:42(td) +msgid "(IntOpt) Debug port to connect. Note that using the remote debug option changes how Nova uses the eventlet library to support async IO. This could result in failures that do not occur under normal operation. Use at your own risk." +msgstr "" + +#: ./doc/common/tables/neutron-embrane.xml:8(caption) +msgid "Description of configuration options for embrane" +msgstr "" + +#: ./doc/common/tables/neutron-embrane.xml:19(td) +msgid "admin_username = admin" +msgstr "" + +#: ./doc/common/tables/neutron-embrane.xml:20(td) +msgid "(StrOpt) ESM admin username." +msgstr "" + +#: ./doc/common/tables/neutron-embrane.xml:23(td) +msgid "async_requests = True" +msgstr "" + +#: ./doc/common/tables/neutron-embrane.xml:24(td) +msgid "(BoolOpt) Define if the requests have run asynchronously or not" +msgstr "" + +#: ./doc/common/tables/neutron-embrane.xml:27(td) +msgid "dummy_utif_id = None" +msgstr "" + +#: ./doc/common/tables/neutron-embrane.xml:28(td) +msgid "(StrOpt) Dummy user traffic Security Zone id" +msgstr "" + +#: ./doc/common/tables/neutron-embrane.xml:31(td) +msgid "esm_mgmt = None" +msgstr "" + +#: ./doc/common/tables/neutron-embrane.xml:32(td) +msgid "(StrOpt) ESM management root address" +msgstr "" + +#: ./doc/common/tables/neutron-embrane.xml:35(td) +msgid "inband_id = None" +msgstr "" + +#: ./doc/common/tables/neutron-embrane.xml:36(td) +msgid "(StrOpt) In band Security Zone id" +msgstr "" + +#: ./doc/common/tables/neutron-embrane.xml:39(td) +msgid "mgmt_id = None" +msgstr "" + +#: ./doc/common/tables/neutron-embrane.xml:40(td) +msgid "(StrOpt) Management Security Zone id" +msgstr "" + +#: ./doc/common/tables/neutron-embrane.xml:43(td) +msgid "oob_id = None" +msgstr "" + +#: ./doc/common/tables/neutron-embrane.xml:44(td) +msgid "(StrOpt) Out of band Security Zone id" +msgstr "" + +#: ./doc/common/tables/neutron-embrane.xml:47(td) +msgid "resource_pool_id = default" +msgstr "" + +#: ./doc/common/tables/neutron-embrane.xml:48(td) +msgid "(StrOpt) Shared resource pool id" +msgstr "" + +#: ./doc/common/tables/neutron-embrane.xml:51(td) +msgid "router_image = None" +msgstr "" + +#: ./doc/common/tables/neutron-embrane.xml:52(td) +msgid "(StrOpt) Router image id (Embrane FW/VPN)" +msgstr "" + +#: ./doc/common/tables/swift-proxy-server-pipeline-main.xml:18(td) +msgid "pipeline = catch_errors healthcheck proxy-logging cache bulk slo ratelimit tempauth container-quotas account-quotas proxy-logging proxy-server" +msgstr "" + +#: ./doc/common/tables/nova-upgrade_levels.xml:8(caption) +msgid "Description of configuration options for upgrade_levels" +msgstr "" + +#: ./doc/common/tables/nova-upgrade_levels.xml:22(td) +msgid "scheduler = nova.cells.scheduler.CellsScheduler" +msgstr "" + +#: ./doc/common/tables/nova-upgrade_levels.xml:23(td) +msgid "(StrOpt) Cells scheduler to use" +msgstr "" + +#: ./doc/common/tables/nova-upgrade_levels.xml:29(td) +msgid "cells = None" +msgstr "" + +#: ./doc/common/tables/nova-upgrade_levels.xml:30(td) +msgid "(StrOpt) Set a version cap for messages sent to local cells services" +msgstr "" + +#: ./doc/common/tables/nova-upgrade_levels.xml:33(td) +msgid "cert = None" +msgstr "" + +#: ./doc/common/tables/nova-upgrade_levels.xml:34(td) +msgid "(StrOpt) Set a version cap for messages sent to cert services" +msgstr "" + +#: ./doc/common/tables/nova-upgrade_levels.xml:37(td) +msgid "compute = None" +msgstr "" + +#: ./doc/common/tables/nova-upgrade_levels.xml:38(td) +msgid "(StrOpt) Set a version cap for messages sent to compute services" +msgstr "" + +#: ./doc/common/tables/nova-upgrade_levels.xml:41(td) +msgid "conductor = None" +msgstr "" + +#: ./doc/common/tables/nova-upgrade_levels.xml:42(td) +msgid "(StrOpt) Set a version cap for messages sent to conductor services" +msgstr "" + +#: ./doc/common/tables/nova-upgrade_levels.xml:45(td) +msgid "console = None" +msgstr "" + +#: ./doc/common/tables/nova-upgrade_levels.xml:46(td) +msgid "(StrOpt) Set a version cap for messages sent to console services" +msgstr "" + +#: ./doc/common/tables/nova-upgrade_levels.xml:49(td) +msgid "consoleauth = None" +msgstr "" + +#: ./doc/common/tables/nova-upgrade_levels.xml:50(td) +msgid "(StrOpt) Set a version cap for messages sent to consoleauth services" +msgstr "" + +#: ./doc/common/tables/nova-upgrade_levels.xml:53(td) +msgid "intercell = None" +msgstr "" + +#: ./doc/common/tables/nova-upgrade_levels.xml:54(td) +msgid "(StrOpt) Set a version cap for messages sent between cells services" +msgstr "" + +#: ./doc/common/tables/nova-upgrade_levels.xml:57(td) +msgid "network = None" +msgstr "" + +#: ./doc/common/tables/nova-upgrade_levels.xml:58(td) +msgid "(StrOpt) Set a version cap for messages sent to network services" +msgstr "" + +#: ./doc/common/tables/nova-upgrade_levels.xml:61(td) +msgid "scheduler = None" +msgstr "" + +#: ./doc/common/tables/nova-upgrade_levels.xml:62(td) +msgid "(StrOpt) Set a version cap for messages sent to scheduler services" +msgstr "" + +#: ./doc/common/tables/swift-proxy-server-filter-cname_lookup.xml:7(literal) +msgid "[filter:cname_lookup]" +msgstr "" + +#: ./doc/common/tables/swift-proxy-server-filter-cname_lookup.xml:18(td) +msgid "use = egg:swift#cname_lookup" +msgstr "" + +#: ./doc/common/tables/swift-proxy-server-filter-cname_lookup.xml:21(td) +msgid "set log_name = cname_lookup" +msgstr "" + +#: ./doc/common/tables/swift-proxy-server-filter-cname_lookup.xml:36(td) ./doc/common/tables/swift-proxy-server-filter-domain_remap.xml:36(td) +msgid "storage_domain = example.com" +msgstr "" + +#: ./doc/common/tables/swift-proxy-server-filter-cname_lookup.xml:36(td) ./doc/common/tables/swift-proxy-server-filter-domain_remap.xml:36(td) +msgid "Domain to use for remap" +msgstr "" + +#: ./doc/common/tables/swift-proxy-server-filter-cname_lookup.xml:39(td) +msgid "lookup_depth = 1" +msgstr "" + +#: ./doc/common/tables/swift-proxy-server-filter-cname_lookup.xml:39(td) +msgid "As CNAMES can be recursive, how many levels to search through" +msgstr "" + +#: ./doc/common/tables/cinder-zadara.xml:8(caption) +msgid "Description of configuration options for zadara" +msgstr "" + +#: ./doc/common/tables/cinder-zadara.xml:22(td) +msgid "zadara_default_striping_mode = simple" +msgstr "" + +#: ./doc/common/tables/cinder-zadara.xml:23(td) +msgid "(StrOpt) Default striping mode for volumes" +msgstr "" + +#: ./doc/common/tables/cinder-zadara.xml:26(td) +msgid "zadara_password = None" +msgstr "" + +#: ./doc/common/tables/cinder-zadara.xml:27(td) +msgid "(StrOpt) Password for the VPSA" +msgstr "" + +#: ./doc/common/tables/cinder-zadara.xml:30(td) +msgid "zadara_user = None" +msgstr "" + +#: ./doc/common/tables/cinder-zadara.xml:31(td) +msgid "(StrOpt) User name for the VPSA" +msgstr "" + +#: ./doc/common/tables/cinder-zadara.xml:34(td) +msgid "zadara_vol_encrypt = False" +msgstr "" + +#: ./doc/common/tables/cinder-zadara.xml:35(td) +msgid "(BoolOpt) Default encryption policy for volumes" +msgstr "" + +#: ./doc/common/tables/cinder-zadara.xml:38(td) +msgid "zadara_vol_name_template = OS_%s" +msgstr "" + +#: ./doc/common/tables/cinder-zadara.xml:39(td) +msgid "(StrOpt) Default template for VPSA volume names" +msgstr "" + +#: ./doc/common/tables/cinder-zadara.xml:42(td) +msgid "zadara_vol_thin = True" +msgstr "" + +#: ./doc/common/tables/cinder-zadara.xml:43(td) +msgid "(BoolOpt) Default thin provisioning policy for volumes" +msgstr "" + +#: ./doc/common/tables/cinder-zadara.xml:46(td) +msgid "zadara_vpsa_allow_nonexistent_delete = True" +msgstr "" + +#: ./doc/common/tables/cinder-zadara.xml:47(td) +msgid "(BoolOpt) Don't halt on deletion of non-existing volumes" +msgstr "" + +#: ./doc/common/tables/cinder-zadara.xml:50(td) +msgid "zadara_vpsa_auto_detach_on_delete = True" +msgstr "" + +#: ./doc/common/tables/cinder-zadara.xml:51(td) +msgid "(BoolOpt) Automatically detach from servers on volume delete" +msgstr "" + +#: ./doc/common/tables/cinder-zadara.xml:54(td) +msgid "zadara_vpsa_ip = None" +msgstr "" + +#: ./doc/common/tables/cinder-zadara.xml:55(td) +msgid "(StrOpt) Management IP of Zadara VPSA" +msgstr "" + +#: ./doc/common/tables/cinder-zadara.xml:58(td) +msgid "zadara_vpsa_poolname = None" +msgstr "" + +#: ./doc/common/tables/cinder-zadara.xml:59(td) +msgid "(StrOpt) Name of VPSA storage pool for volumes" +msgstr "" + +#: ./doc/common/tables/cinder-zadara.xml:62(td) +msgid "zadara_vpsa_port = None" +msgstr "" + +#: ./doc/common/tables/cinder-zadara.xml:63(td) +msgid "(StrOpt) Zadara VPSA port number" +msgstr "" + +#: ./doc/common/tables/cinder-zadara.xml:66(td) +msgid "zadara_vpsa_use_ssl = False" +msgstr "" + +#: ./doc/common/tables/cinder-zadara.xml:67(td) +msgid "(BoolOpt) Use SSL connection" +msgstr "" + +#: ./doc/common/tables/swift-account-server-account-reaper.xml:7(literal) +msgid "[account-reaper]" +msgstr "" + +#: ./doc/common/tables/swift-account-server-account-reaper.xml:18(td) +msgid "log_name = account-reaper" +msgstr "" + +#: ./doc/common/tables/swift-account-server-account-reaper.xml:33(td) +msgid "interval = 3600" +msgstr "" + +#: ./doc/common/tables/swift-account-server-account-reaper.xml:42(td) +msgid "delay_reaping = 0" +msgstr "" + +#: ./doc/common/tables/swift-account-server-account-reaper.xml:42(td) +msgid "Normally, the reaper begins deleting account information for deleted accounts immediately; you can set this to delay its work however. The value is in seconds, 2592000 = 30 days, for example. bind to giving up worker can process simultaneously (it will actually accept(2) N + 1). Setting this to one (1) will only handle one request at a time, without accepting another request concurrently. By increasing the number of workers to a much higher value, one can reduce the impact of slow file system operations in one request from negatively impacting other requests." +msgstr "" + +#: ./doc/common/tables/swift-account-server-account-reaper.xml:45(td) +msgid "reap_warn_after = 2592000" +msgstr "" + +#: ./doc/common/tables/nova-quota.xml:22(td) +msgid "bandwidth_poll_interval = 600" +msgstr "" + +#: ./doc/common/tables/nova-quota.xml:23(td) +msgid "(IntOpt) interval to pull bandwidth usage info" +msgstr "" + +#: ./doc/common/tables/nova-quota.xml:26(td) +msgid "enable_network_quota = False" +msgstr "" + +#: ./doc/common/tables/nova-quota.xml:27(td) +msgid "(BoolOpt) Enables or disables quota checking for tenant networks" +msgstr "" + +#: ./doc/common/tables/nova-quota.xml:30(td) +msgid "quota_cores = 20" +msgstr "" + +#: ./doc/common/tables/nova-quota.xml:31(td) +msgid "(IntOpt) number of instance cores allowed per project" +msgstr "" + +#: ./doc/common/tables/nova-quota.xml:34(td) +msgid "quota_driver = nova.quota.DbQuotaDriver" +msgstr "" + +#: ./doc/common/tables/nova-quota.xml:38(td) +msgid "quota_fixed_ips = -1" +msgstr "" + +#: ./doc/common/tables/nova-quota.xml:39(td) +msgid "(IntOpt) number of fixed ips allowed per project (this should be at least the number of instances allowed)" +msgstr "" + +#: ./doc/common/tables/nova-quota.xml:42(td) +msgid "quota_floating_ips = 10" +msgstr "" + +#: ./doc/common/tables/nova-quota.xml:43(td) +msgid "(IntOpt) number of floating ips allowed per project" +msgstr "" + +#: ./doc/common/tables/nova-quota.xml:46(td) +msgid "quota_injected_file_content_bytes = 10240" +msgstr "" + +#: ./doc/common/tables/nova-quota.xml:47(td) +msgid "(IntOpt) number of bytes allowed per injected file" +msgstr "" + +#: ./doc/common/tables/nova-quota.xml:50(td) +msgid "quota_injected_file_path_bytes = 255" +msgstr "" + +#: ./doc/common/tables/nova-quota.xml:51(td) +msgid "(IntOpt) number of bytes allowed per injected file path" +msgstr "" + +#: ./doc/common/tables/nova-quota.xml:54(td) +msgid "quota_injected_files = 5" +msgstr "" + +#: ./doc/common/tables/nova-quota.xml:55(td) +msgid "(IntOpt) number of injected files allowed" +msgstr "" + +#: ./doc/common/tables/nova-quota.xml:58(td) +msgid "quota_instances = 10" +msgstr "" + +#: ./doc/common/tables/nova-quota.xml:59(td) +msgid "(IntOpt) number of instances allowed per project" +msgstr "" + +#: ./doc/common/tables/nova-quota.xml:62(td) +msgid "quota_key_pairs = 100" +msgstr "" + +#: ./doc/common/tables/nova-quota.xml:63(td) +msgid "(IntOpt) number of key pairs per user" +msgstr "" + +#: ./doc/common/tables/nova-quota.xml:66(td) +msgid "quota_metadata_items = 128" +msgstr "" + +#: ./doc/common/tables/nova-quota.xml:67(td) +msgid "(IntOpt) number of metadata items allowed per instance" +msgstr "" + +#: ./doc/common/tables/nova-quota.xml:70(td) +msgid "quota_ram = 51200" +msgstr "" + +#: ./doc/common/tables/nova-quota.xml:71(td) +msgid "(IntOpt) megabytes of instance ram allowed per project" +msgstr "" + +#: ./doc/common/tables/nova-quota.xml:74(td) +msgid "quota_security_group_rules = 20" +msgstr "" + +#: ./doc/common/tables/nova-quota.xml:75(td) +msgid "(IntOpt) number of security rules per security group" +msgstr "" + +#: ./doc/common/tables/nova-quota.xml:78(td) +msgid "quota_security_groups = 10" +msgstr "" + +#: ./doc/common/tables/nova-quota.xml:79(td) +msgid "(IntOpt) number of security groups per project" +msgstr "" + +#: ./doc/common/tables/nova-quota.xml:85(td) +msgid "bandwidth_update_interval = 600" +msgstr "" + +#: ./doc/common/tables/nova-quota.xml:86(td) +msgid "(IntOpt) Seconds between bandwidth updates for cells." +msgstr "" + +#: ./doc/common/tables/nova-conductor.xml:8(caption) +msgid "Description of configuration options for conductor" +msgstr "" + +#: ./doc/common/tables/nova-conductor.xml:22(td) +msgid "migrate_max_retries = -1" +msgstr "" + +#: ./doc/common/tables/nova-conductor.xml:23(td) +msgid "(IntOpt) Number of times to retry live-migration before failing. If == -1, try until out of hosts. If == 0, only try once, no retries." +msgstr "" + +#: ./doc/common/tables/nova-conductor.xml:26(th) +msgid "[conductor]" +msgstr "" + +#: ./doc/common/tables/nova-conductor.xml:29(td) +msgid "manager = nova.conductor.manager.ConductorManager" +msgstr "" + +#: ./doc/common/tables/nova-conductor.xml:30(td) +msgid "(StrOpt) full class name for the Manager for conductor" +msgstr "" + +#: ./doc/common/tables/nova-conductor.xml:33(td) +msgid "topic = conductor" +msgstr "" + +#: ./doc/common/tables/nova-conductor.xml:34(td) +msgid "(StrOpt) the topic conductor nodes listen on" +msgstr "" + +#: ./doc/common/tables/nova-conductor.xml:37(td) +msgid "use_local = False" +msgstr "" + +#: ./doc/common/tables/nova-conductor.xml:38(td) +msgid "(BoolOpt) Perform nova-conductor operations locally" +msgstr "" + +#: ./doc/common/tables/nova-conductor.xml:41(td) +msgid "workers = None" +msgstr "" + +#: ./doc/common/tables/nova-conductor.xml:42(td) +msgid "(IntOpt) Number of workers for OpenStack Conductor service" +msgstr "" + +#: ./doc/common/tables/nova-compute.xml:22(td) +msgid "compute_available_monitors = ['nova.compute.monitors.all_monitors']" +msgstr "" + +#: ./doc/common/tables/nova-compute.xml:23(td) +msgid "(MultiStrOpt) Monitor classes available to the compute which may be specified more than once." +msgstr "" + +#: ./doc/common/tables/nova-compute.xml:26(td) +msgid "compute_driver = None" +msgstr "" + +#: ./doc/common/tables/nova-compute.xml:27(td) +msgid "(StrOpt) Driver to use for controlling virtualization. Options include: libvirt.LibvirtDriver, xenapi.XenAPIDriver, fake.FakeDriver, baremetal.BareMetalDriver, vmwareapi.VMwareESXDriver, vmwareapi.VMwareVCDriver" +msgstr "" + +#: ./doc/common/tables/nova-compute.xml:30(td) +msgid "compute_manager = nova.compute.manager.ComputeManager" +msgstr "" + +#: ./doc/common/tables/nova-compute.xml:31(td) +msgid "(StrOpt) full class name for the Manager for compute" +msgstr "" + +#: ./doc/common/tables/nova-compute.xml:34(td) +msgid "compute_monitors =" +msgstr "" + +#: ./doc/common/tables/nova-compute.xml:35(td) +msgid "(ListOpt) A list of monitors that can be used for getting compute metrics." +msgstr "" + +#: ./doc/common/tables/nova-compute.xml:38(td) +msgid "compute_stats_class = nova.compute.stats.Stats" +msgstr "" + +#: ./doc/common/tables/nova-compute.xml:39(td) +msgid "(StrOpt) Class that will manage stats for the local compute host" +msgstr "" + +#: ./doc/common/tables/nova-compute.xml:42(td) +msgid "console_host = oslo" +msgstr "" + +#: ./doc/common/tables/nova-compute.xml:43(td) +msgid "(StrOpt) Console proxy host to use to connect to instances on this host." +msgstr "" + +#: ./doc/common/tables/nova-compute.xml:46(td) +msgid "console_manager = nova.console.manager.ConsoleProxyManager" +msgstr "" + +#: ./doc/common/tables/nova-compute.xml:47(td) +msgid "(StrOpt) full class name for the Manager for console proxy" +msgstr "" + +#: ./doc/common/tables/nova-compute.xml:50(td) +msgid "default_flavor = m1.small" +msgstr "" + +#: ./doc/common/tables/nova-compute.xml:51(td) +msgid "(StrOpt) default flavor to use for the EC2 API only. The Nova API does not support a default flavor." +msgstr "" + +#: ./doc/common/tables/nova-compute.xml:62(td) +msgid "enable_instance_password = True" +msgstr "" + +#: ./doc/common/tables/nova-compute.xml:63(td) +msgid "(BoolOpt) Enables returning of the instance password by the relevant server API calls such as create, rebuild or rescue, If the hypervisor does not support password injection then the password returned will not be correct" +msgstr "" + +#: ./doc/common/tables/nova-compute.xml:66(td) +msgid "heal_instance_info_cache_interval = 60" +msgstr "" + +#: ./doc/common/tables/nova-compute.xml:67(td) +msgid "(IntOpt) Number of seconds between instance info_cache self healing updates" +msgstr "" + +#: ./doc/common/tables/nova-compute.xml:70(td) +msgid "host_state_interval = 120" +msgstr "" + +#: ./doc/common/tables/nova-compute.xml:71(td) +msgid "(IntOpt) Interval in seconds for querying the host status" +msgstr "" + +#: ./doc/common/tables/nova-compute.xml:74(td) +msgid "image_cache_manager_interval = 2400" +msgstr "" + +#: ./doc/common/tables/nova-compute.xml:75(td) +msgid "(IntOpt) Number of seconds to wait between runs of the image cache manager" +msgstr "" + +#: ./doc/common/tables/nova-compute.xml:78(td) +msgid "image_cache_subdirectory_name = _base" +msgstr "" + +#: ./doc/common/tables/nova-compute.xml:79(td) +msgid "(StrOpt) Where cached images are stored under $instances_path. This is NOT the full path - just a folder name. For per-compute-host cached images, set to _base_$my_ip" +msgstr "" + +#: ./doc/common/tables/nova-compute.xml:82(td) +msgid "instance_build_timeout = 0" +msgstr "" + +#: ./doc/common/tables/nova-compute.xml:83(td) +msgid "(IntOpt) Amount of time in seconds an instance can be in BUILD before going into ERROR status.Set to 0 to disable." +msgstr "" + +#: ./doc/common/tables/nova-compute.xml:86(td) +msgid "instance_delete_interval = 300" +msgstr "" + +#: ./doc/common/tables/nova-compute.xml:87(td) +msgid "(IntOpt) Interval in seconds for retrying failed instance file deletes" +msgstr "" + +#: ./doc/common/tables/nova-compute.xml:90(td) +msgid "instance_usage_audit = False" +msgstr "" + +#: ./doc/common/tables/nova-compute.xml:91(td) +msgid "(BoolOpt) Generate periodic compute.instance.exists notifications" +msgstr "" + +#: ./doc/common/tables/nova-compute.xml:94(td) +msgid "instance_usage_audit_period = month" +msgstr "" + +#: ./doc/common/tables/nova-compute.xml:95(td) +msgid "(StrOpt) time period to generate instance usages for. Time period must be hour, day, month or year" +msgstr "" + +#: ./doc/common/tables/nova-compute.xml:98(td) +msgid "instances_path = $state_path/instances" +msgstr "" + +#: ./doc/common/tables/nova-compute.xml:99(td) +msgid "(StrOpt) where instances are stored on disk" +msgstr "" + +#: ./doc/common/tables/nova-compute.xml:102(td) +msgid "maximum_instance_delete_attempts = 5" +msgstr "" + +#: ./doc/common/tables/nova-compute.xml:103(td) +msgid "(IntOpt) The number of times to attempt to reap an instance's files." +msgstr "" + +#: ./doc/common/tables/nova-compute.xml:106(td) +msgid "reboot_timeout = 0" +msgstr "" + +#: ./doc/common/tables/nova-compute.xml:107(td) +msgid "(IntOpt) Automatically hard reboot an instance if it has been stuck in a rebooting state longer than N seconds. Set to 0 to disable." +msgstr "" + +#: ./doc/common/tables/nova-compute.xml:110(td) +msgid "reclaim_instance_interval = 0" +msgstr "" + +#: ./doc/common/tables/nova-compute.xml:111(td) +msgid "(IntOpt) Interval in seconds for reclaiming deleted instances" +msgstr "" + +#: ./doc/common/tables/nova-compute.xml:114(td) +msgid "resize_confirm_window = 0" +msgstr "" + +#: ./doc/common/tables/nova-compute.xml:115(td) +msgid "(IntOpt) Automatically confirm resizes after N seconds. Set to 0 to disable." +msgstr "" + +#: ./doc/common/tables/nova-compute.xml:118(td) +msgid "resume_guests_state_on_host_boot = False" +msgstr "" + +#: ./doc/common/tables/nova-compute.xml:119(td) +msgid "(BoolOpt) Whether to start guests that were running before the host rebooted" +msgstr "" + +#: ./doc/common/tables/nova-compute.xml:122(td) +msgid "running_deleted_instance_action = reap" +msgstr "" + +#: ./doc/common/tables/nova-compute.xml:123(td) +msgid "(StrOpt) Action to take if a running deleted instance is detected.Valid options are 'noop', 'log', 'shutdown', or 'reap'. Set to 'noop' to take no action." +msgstr "" + +#: ./doc/common/tables/nova-compute.xml:126(td) +msgid "running_deleted_instance_poll_interval = 1800" +msgstr "" + +#: ./doc/common/tables/nova-compute.xml:127(td) +msgid "(IntOpt) Number of seconds to wait between runs of the cleanup task." +msgstr "" + +#: ./doc/common/tables/nova-compute.xml:130(td) +msgid "running_deleted_instance_timeout = 0" +msgstr "" + +#: ./doc/common/tables/nova-compute.xml:131(td) +msgid "(IntOpt) Number of seconds after being deleted when a running instance should be considered eligible for cleanup." +msgstr "" + +#: ./doc/common/tables/nova-compute.xml:134(td) +msgid "shelved_offload_time = 0" +msgstr "" + +#: ./doc/common/tables/nova-compute.xml:135(td) +msgid "(IntOpt) Time in seconds before a shelved instance is eligible for removing from a host. -1 never offload, 0 offload when shelved" +msgstr "" + +#: ./doc/common/tables/nova-compute.xml:138(td) +msgid "shelved_poll_interval = 3600" +msgstr "" + +#: ./doc/common/tables/nova-compute.xml:139(td) +msgid "(IntOpt) Interval in seconds for polling shelved instances to offload" +msgstr "" + +#: ./doc/common/tables/nova-compute.xml:142(td) +msgid "sync_power_state_interval = 600" +msgstr "" + +#: ./doc/common/tables/nova-compute.xml:143(td) +msgid "(IntOpt) interval to sync power states between the database and the hypervisor" +msgstr "" + +#: ./doc/common/tables/swift-proxy-server-filter-domain_remap.xml:7(literal) +msgid "[filter:domain_remap]" +msgstr "" + +#: ./doc/common/tables/swift-proxy-server-filter-domain_remap.xml:18(td) +msgid "use = egg:swift#domain_remap" +msgstr "" + +#: ./doc/common/tables/swift-proxy-server-filter-domain_remap.xml:21(td) +msgid "set log_name = domain_remap" +msgstr "" + +#: ./doc/common/tables/swift-proxy-server-filter-domain_remap.xml:39(td) +msgid "path_root = v1" +msgstr "" + +#: ./doc/common/tables/swift-proxy-server-filter-domain_remap.xml:39(td) +msgid "Root path" +msgstr "" + +#: ./doc/common/tables/swift-proxy-server-filter-domain_remap.xml:42(td) +msgid "reseller_prefixes = AUTH" +msgstr "" + +#: ./doc/common/tables/swift-proxy-server-filter-domain_remap.xml:42(td) +msgid "Reseller prefix" +msgstr "" + +#: ./doc/common/tables/neutron-hyperv.xml:24(td) +msgid "(StrOpt) Network type for tenant networks (local, flat, vlan or none)" +msgstr "" + +#: ./doc/common/tables/cinder-storage_xen.xml:8(caption) +msgid "Description of configuration options for storage_xen" +msgstr "" + +#: ./doc/common/tables/cinder-storage_xen.xml:22(td) +msgid "xenapi_connection_password = None" +msgstr "" + +#: ./doc/common/tables/cinder-storage_xen.xml:23(td) +msgid "(StrOpt) Password for XenAPI connection" +msgstr "" + +#: ./doc/common/tables/cinder-storage_xen.xml:26(td) +msgid "xenapi_connection_url = None" +msgstr "" + +#: ./doc/common/tables/cinder-storage_xen.xml:27(td) +msgid "(StrOpt) URL for XenAPI connection" +msgstr "" + +#: ./doc/common/tables/cinder-storage_xen.xml:30(td) +msgid "xenapi_connection_username = root" +msgstr "" + +#: ./doc/common/tables/cinder-storage_xen.xml:31(td) +msgid "(StrOpt) Username for XenAPI connection" +msgstr "" + +#: ./doc/common/tables/cinder-storage_xen.xml:34(td) +msgid "xenapi_nfs_server = None" +msgstr "" + +#: ./doc/common/tables/cinder-storage_xen.xml:35(td) +msgid "(StrOpt) NFS server to be used by XenAPINFSDriver" +msgstr "" + +#: ./doc/common/tables/cinder-storage_xen.xml:38(td) +msgid "xenapi_nfs_serverpath = None" +msgstr "" + +#: ./doc/common/tables/cinder-storage_xen.xml:39(td) +msgid "(StrOpt) Path of exported NFS, used by XenAPINFSDriver" +msgstr "" + +#: ./doc/common/tables/cinder-storage_xen.xml:42(td) +msgid "xenapi_sr_base_path = /var/run/sr-mount" +msgstr "" + +#: ./doc/common/tables/nova-xvpnvncproxy.xml:8(caption) +msgid "Description of configuration options for xvpnvncproxy" +msgstr "" + +#: ./doc/common/tables/nova-xvpnvncproxy.xml:22(td) +msgid "xvpvncproxy_base_url = http://127.0.0.1:6081/console" +msgstr "" + +#: ./doc/common/tables/nova-xvpnvncproxy.xml:23(td) +msgid "(StrOpt) location of nova xvp vnc console proxy, in the form \"http://127.0.0.1:6081/console\"" +msgstr "" + +#: ./doc/common/tables/nova-xvpnvncproxy.xml:26(td) +msgid "xvpvncproxy_host = 0.0.0.0" +msgstr "" + +#: ./doc/common/tables/nova-xvpnvncproxy.xml:27(td) +msgid "(StrOpt) Address that the XCP VNC proxy should bind to" +msgstr "" + +#: ./doc/common/tables/nova-xvpnvncproxy.xml:30(td) +msgid "xvpvncproxy_port = 6081" +msgstr "" + +#: ./doc/common/tables/nova-xvpnvncproxy.xml:31(td) +msgid "(IntOpt) Port that the XCP VNC proxy should bind to" +msgstr "" + +#. Put one translator per line, in the form of NAME , YEAR1, YEAR2 +#: ./doc/common/tables/nova-xvpnvncproxy.xml:0(None) +msgid "translator-credits" +msgstr "" + diff --git a/doc/common/locale/he_IL.po b/doc/common/locale/he_IL.po new file mode 100644 index 0000000000..36c99670d8 --- /dev/null +++ b/doc/common/locale/he_IL.po @@ -0,0 +1,30292 @@ +# +# Translators: +msgid "" +msgstr "" +"Project-Id-Version: OpenStack Manuals\n" +"POT-Creation-Date: 2014-01-30 06:24+0000\n" +"PO-Revision-Date: 2014-01-25 09:57+0000\n" +"Last-Translator: openstackjenkins \n" +"Language-Team: Hebrew (Israel) (http://www.transifex.com/projects/p/openstack/language/he_IL/)\n" +"MIME-Version: 1.0\n" +"Content-Type: text/plain; charset=UTF-8\n" +"Content-Transfer-Encoding: 8bit\n" +"Language: he_IL\n" +"Plural-Forms: nplurals=2; plural=(n != 1);\n" + +#: ./doc/common/app_support.xml7(title) +msgid "Community support" +msgstr "" + +#: ./doc/common/app_support.xml9(para) +msgid "" +"Many resources are available to help you run and use OpenStack. Members of " +"the OpenStack community can answer questions and help with bug suspicions. " +"We are constantly improving and adding to the main features of OpenStack, " +"but if you have any problems, do not hesitate to ask. Use the following " +"resources to get OpenStack support and troubleshoot your existing " +"installations." +msgstr "" + +#: ./doc/common/app_support.xml18(title) +msgid "Documentation" +msgstr "" + +#: ./doc/common/app_support.xml19(para) +msgid "" +"For the available OpenStack documentation, see docs.openstack.org." +msgstr "" + +#: ./doc/common/app_support.xml22(para) ./doc/common/app_support.xml342(para) +#: ./doc/common/ch_getstart.xml174(para) +msgid "" +"To provide feedback on documentation, join and use the openstack-" +"docs@lists.openstack.org mailing list at OpenStack Documentation Mailing List, or report a " +"bug." +msgstr "" + +#: ./doc/common/app_support.xml30(para) +msgid "" +"The following books explain how to install an OpenStack cloud and its " +"associated components:" +msgstr "" + +#: ./doc/common/app_support.xml37(citetitle) +msgid "Installation Guide for Debian 7.0" +msgstr "" + +#: ./doc/common/app_support.xml44(citetitle) +msgid "Installation Guide for openSUSE and SUSE Linux Enterprise Server" +msgstr "" + +#: ./doc/common/app_support.xml51(citetitle) +msgid "Installation Guide for Red Hat Enterprise Linux, CentOS, and Fedora" +msgstr "" + +#: ./doc/common/app_support.xml59(citetitle) +msgid "Installation Guide for Ubuntu 12.04 (LTS)" +msgstr "" + +#: ./doc/common/app_support.xml64(para) +msgid "" +"The following books explain how to configure and run an OpenStack cloud:" +msgstr "" + +#: ./doc/common/app_support.xml71(citetitle) +msgid "Cloud Administrator Guide" +msgstr "" + +#: ./doc/common/app_support.xml77(citetitle) +msgid "Configuration Reference" +msgstr "" + +#: ./doc/common/app_support.xml83(citetitle) +msgid "Operations Guide" +msgstr "" + +#: ./doc/common/app_support.xml88(citetitle) +msgid "High Availability Guide" +msgstr "" + +#: ./doc/common/app_support.xml94(citetitle) +msgid "Security Guide" +msgstr "" + +#: ./doc/common/app_support.xml100(citetitle) +msgid "Virtual Machine Image Guide" +msgstr "" + +#: ./doc/common/app_support.xml104(para) +msgid "" +"The following books explain how to use the OpenStack dashboard and command-" +"line clients:" +msgstr "" + +#: ./doc/common/app_support.xml111(citetitle) +msgid "API Quick Start" +msgstr "" + +#: ./doc/common/app_support.xml118(citetitle) +msgid "End User Guide" +msgstr "" + +#: ./doc/common/app_support.xml125(citetitle) +msgid "Admin User Guide" +msgstr "" + +#: ./doc/common/app_support.xml129(para) +msgid "" +"The following documentation provides reference and guidance information for " +"the OpenStack APIs:" +msgstr "" + +#: ./doc/common/app_support.xml131(link) +msgid "OpenStack API Reference" +msgstr "" + +#: ./doc/common/app_support.xml135(citetitle) +msgid "OpenStack Block Storage Service API v2 Reference" +msgstr "" + +#: ./doc/common/app_support.xml142(citetitle) +msgid "OpenStack Compute API v2 and Extensions Reference" +msgstr "" + +#: ./doc/common/app_support.xml147(citetitle) +msgid "OpenStack Identity Service API v2.0 Reference" +msgstr "" + +#: ./doc/common/app_support.xml152(citetitle) +msgid "OpenStack Image Service API v2 Reference" +msgstr "" + +#: ./doc/common/app_support.xml157(citetitle) +msgid "OpenStack Networking API v2.0 Reference" +msgstr "" + +#: ./doc/common/app_support.xml162(citetitle) +msgid "OpenStack Object Storage API v1 Reference" +msgstr "" + +#: ./doc/common/app_support.xml164(para) +msgid "" +"The Training Guides offer " +"software training for cloud administration and management." +msgstr "" + +#: ./doc/common/app_support.xml170(title) +msgid "ask.openstack.org" +msgstr "" + +#: ./doc/common/app_support.xml171(para) +msgid "" +"During the set up or testing of OpenStack, you might have questions about " +"how a specific task is completed or be in a situation where a feature does " +"not work correctly. Use the ask.openstack.org site to ask " +"questions and get answers. When you visit the http://ask.openstack.org site, scan" +" the recently asked questions to see whether your question has already been " +"answered. If not, ask a new question. Be sure to give a clear, concise " +"summary in the title and provide as much detail as possible in the " +"description. Paste in your command output or stack traces, links to screen " +"shots, and so on." +msgstr "" + +#: ./doc/common/app_support.xml186(title) +msgid "OpenStack mailing lists" +msgstr "" + +#: ./doc/common/app_support.xml187(para) +msgid "" +"A great way to get answers and insights is to post your question or " +"problematic scenario to the OpenStack mailing list. You can learn from and " +"help others who might have similar issues. To subscribe or view the " +"archives, go to http://lists.openstack.org/cgi-" +"bin/mailman/listinfo/openstack. You might be interested in the other " +"mailing lists for specific projects or development, which you can find on the wiki. A " +"description of all mailing lists is available at http://wiki.openstack.org/MailingLists." +msgstr "" + +#: ./doc/common/app_support.xml203(title) +msgid "The OpenStack wiki" +msgstr "" + +#: ./doc/common/app_support.xml204(para) +msgid "" +"The OpenStack wiki contains" +" a broad range of topics but some of the information can be difficult to " +"find or is a few pages deep. Fortunately, the wiki search feature enables " +"you to search by title or content. If you search for specific information, " +"such as about networking or nova, you can find lots of relevant material. " +"More is being added all the time, so be sure to check back often. You can " +"find the search box in the upper right corner of any OpenStack wiki page." +msgstr "" + +#: ./doc/common/app_support.xml216(title) +msgid "The Launchpad Bugs area" +msgstr "" + +#: ./doc/common/app_support.xml217(para) +msgid "" +"The OpenStack community values your set up and testing efforts and wants " +"your feedback. To log a bug, you must sign up for a Launchpad account at " +"https://launchpad.net/+login. " +"You can view existing bugs and report bugs in the Launchpad Bugs area. Use " +"the search feature to determine whether the bug has already been reported or" +" even better, already fixed. If it still seems like your bug is unreported, " +"fill out a bug report." +msgstr "" + +#: ./doc/common/app_support.xml227(para) +msgid "Some tips:" +msgstr "" + +#: ./doc/common/app_support.xml230(para) +msgid "Give a clear, concise summary!" +msgstr "" + +#: ./doc/common/app_support.xml233(para) +msgid "" +"Provide as much detail as possible in the description. Paste in your command" +" output or stack traces, links to screen shots, and so on." +msgstr "" + +#: ./doc/common/app_support.xml238(para) +msgid "" +"Be sure to include the software and package versions that you are using, " +"especially if you are using a development branch, such as, " +"\"Grizzly release\" vs git commit " +"bc79c3ecc55929bac585d04a03475b72e06a3208." +msgstr "" + +#: ./doc/common/app_support.xml244(para) +msgid "" +"Any deployment specific information is helpful, such as Ubuntu 12.04 or " +"multi-node install." +msgstr "" + +#: ./doc/common/app_support.xml248(para) +msgid "The Launchpad Bugs areas are available here:" +msgstr "" + +#: ./doc/common/app_support.xml251(link) +msgid "Bugs: OpenStack Compute (nova)" +msgstr "" + +#: ./doc/common/app_support.xml255(link) +msgid "Bugs: OpenStack Object Storage (swift)" +msgstr "" + +#: ./doc/common/app_support.xml259(link) +msgid "Bugs: OpenStack Image Service (glance)" +msgstr "" + +#: ./doc/common/app_support.xml264(link) +msgid "Bugs: OpenStack Identity (keystone)" +msgstr "" + +#: ./doc/common/app_support.xml267(link) +msgid "Bugs: OpenStack Dashboard (horizon)" +msgstr "" + +#: ./doc/common/app_support.xml271(link) +msgid "Bugs: OpenStack Networking (neutron)" +msgstr "" + +#: ./doc/common/app_support.xml275(link) +msgid "Bugs: OpenStack Orchestration (heat)" +msgstr "" + +#: ./doc/common/app_support.xml280(link) +msgid "Bugs: OpenStack Telemetry (ceilometer)" +msgstr "" + +#: ./doc/common/app_support.xml284(link) +msgid "Bugs: Database Service (trove)" +msgstr "" + +#: ./doc/common/app_support.xml288(link) +msgid "Bugs: Bare Metal (ironic)" +msgstr "" + +#: ./doc/common/app_support.xml292(link) +msgid "Bugs: OpenStack Queue Service (marconi)" +msgstr "" + +#: ./doc/common/app_support.xml296(link) +msgid "Bugs: OpenStack Data Processing Service (savanna)" +msgstr "" + +#: ./doc/common/app_support.xml301(link) +msgid "Bugs: OpenStack Documentation (docs.openstack.org)" +msgstr "" + +#: ./doc/common/app_support.xml307(link) +msgid "Bugs: OpenStack API Documentation (api.openstack.org)" +msgstr "" + +#: ./doc/common/app_support.xml313(title) +msgid "The OpenStack IRC channel" +msgstr "" + +#: ./doc/common/app_support.xml314(para) +msgid "" +"The OpenStack community lives and breathes in the #openstack IRC channel on " +"the Freenode network. You can hang out, ask questions, or get immediate " +"feedback for urgent and pressing issues. To install an IRC client or use a " +"browser-based client, go to http://webchat.freenode.net/. " +"You can also use Colloquy (Mac OS X, http://colloquy.info/), mIRC (Windows," +" http://www.mirc.com/), or XChat " +"(Linux). When you are in the IRC channel and want to share code or command " +"output, the generally accepted method is to use a Paste Bin. The OpenStack " +"project has one at http://paste.openstack.org. Just " +"paste your longer amounts of text or logs in the web form and you get a URL " +"you can paste into the channel. The OpenStack IRC channel is: " +"#openstack on irc.freenode.net. You " +"can find a list of all OpenStack-related IRC channels at https://wiki.openstack.org/wiki/IRC." +msgstr "" + +#: ./doc/common/app_support.xml340(title) +msgid "Documentation feedback" +msgstr "" + +#: ./doc/common/app_support.xml354(title) +msgid "OpenStack distribution packages" +msgstr "" + +#: ./doc/common/app_support.xml355(para) +msgid "" +"The following Linux distributions provide community-supported packages for " +"OpenStack:" +msgstr "" + +#: ./doc/common/app_support.xml361(emphasis) +msgid "Debian:" +msgstr "" + +#: ./doc/common/app_support.xml362(link) +msgid "http://wiki.debian.org/OpenStack" +msgstr "" + +#: ./doc/common/app_support.xml365(emphasis) +msgid "CentOS, Fedora, and Red Hat Enterprise Linux:" +msgstr "" + +#: ./doc/common/app_support.xml367(link) +msgid "http://openstack.redhat.com/" +msgstr "" + +#: ./doc/common/app_support.xml371(emphasis) +msgid "openSUSE and SUSE Linux Enterprise Server:" +msgstr "" + +#: ./doc/common/app_support.xml374(link) +msgid "http://en.opensuse.org/Portal:OpenStack" +msgstr "" + +#: ./doc/common/app_support.xml378(emphasis) +msgid "Ubuntu:" +msgstr "" + +#: ./doc/common/app_support.xml380(link) +msgid "https://wiki.ubuntu.com/ServerTeam/CloudArchive" +msgstr "" + +#: ./doc/common/section_cli_glance_manage_images.xml7(title) +msgid "Manage images" +msgstr "" + +#: ./doc/common/section_cli_glance_manage_images.xml8(para) +msgid "" +"The cloud operator assigns roles to users. Roles determine who can upload " +"and manage images. The operator might restrict image upload and management " +"to only cloud administrators or operators." +msgstr "" + +#: ./doc/common/section_cli_glance_manage_images.xml12(para) +msgid "" +"You can upload images through the glance client or the Image Service API. " +"You can also use the nova client to list images, set, and delete image " +"metadata, delete images, and take a snapshot of a running instance to create" +" an image. After you upload an image, you cannot change it." +msgstr "" + +#: ./doc/common/section_cli_glance_manage_images.xml16(para) +msgid "" +"For details about image creation, see the Virtual " +"Machine Image Guide." +msgstr "" + +#: ./doc/common/section_cli_glance_manage_images.xml21(title) +msgid "List or get details for images (glance)" +msgstr "" + +#: ./doc/common/section_cli_glance_manage_images.xml24(para) +msgid "To list the available images:" +msgstr "" + +#: ./doc/common/section_cli_glance_manage_images.xml34(para) +msgid "You can use grep to filter the list, as follows:" +msgstr "" + +#: ./doc/common/section_cli_glance_manage_images.xml42(para) +msgid "To get image details, by name or ID:" +msgstr "" + +#: ./doc/common/section_cli_glance_manage_images.xml82(para) +msgid "" +"To store location metadata for images, which enables direct file access for " +"a client, update the /etc/glance/glance.conf file with " +"the following statements:" +msgstr "" + +#: ./doc/common/section_cli_glance_manage_images.xml89(code) +msgid "show_multiple_locations = True" +msgstr "" + +#: ./doc/common/section_cli_glance_manage_images.xml92(para) +msgid "" +"filesystem_store_metadata_file = " +"filePath, where " +"filePath points to a JSON file that defines the " +"mount point for OpenStack images on your system and a unique ID. For " +"example: " +msgstr "" + +#: ./doc/common/section_cli_glance_manage_images.xml108(para) +msgid "" +"After you restart the Image Service, you can use the following syntax to " +"view the image's location information:" +msgstr "" + +#: ./doc/common/section_cli_glance_manage_images.xml109(replaceable) +msgid "imageID" +msgstr "" + +#: ./doc/common/section_cli_glance_manage_images.xml110(para) +#: ./doc/common/section_cli_nova_quotas.xml190(para) +#: ./doc/common/section_cli_nova_quotas.xml214(para) +#: ./doc/common/section_cli_nova_quotas.xml228(para) +#: ./doc/common/section_cli_nova_quotas.xml256(para) +#: ./doc/common/section_cli_nova_quotas.xml299(para) +#: ./doc/common/section_cli_nova_quotas.xml331(para) +#: ./doc/common/section_cli_keystone_services.xml100(para) +#: ./doc/common/section_keystone_certificates-for-pki.xml180(para) +#: ./doc/common/section_cli_cinder_manage_volumes.xml352(para) +#: ./doc/common/section_cli_cinder_manage_volumes.xml366(para) +#: ./doc/common/section_cli_cinder_manage_volumes.xml410(para) +#: ./doc/common/section_objectstorage-ringbuilder.xml83(para) +msgid "For example:" +msgstr "" + +#: ./doc/common/section_cli_glance_manage_images.xml116(title) +msgid "Create or update an image (glance)" +msgstr "" + +#: ./doc/common/section_cli_glance_manage_images.xml119(para) +msgid "" +"To upload a CentOS 6.3 image in qcow2 format and configure it for public " +"access:" +msgstr "" + +#: ./doc/common/section_cli_glance_manage_images.xml125(para) +msgid "To update an image by name or ID:" +msgstr "" + +#: ./doc/common/section_cli_glance_manage_images.xml126(replaceable) +#: ./doc/common/section_cli_nova_manage_images.xml44(replaceable) +#: ./doc/common/section_cli_nova_images.xml45(replaceable) +msgid "IMAGE" +msgstr "" + +#: ./doc/common/section_cli_glance_manage_images.xml127(para) +msgid "To modify image properties, use the following optional arguments:" +msgstr "" + +#: ./doc/common/section_cli_glance_manage_images.xml134(replaceable) +#: ./doc/common/section_cli_nova_boot_from_volume.xml67(replaceable) +#: ./doc/common/section_cli_nova_boot_from_volume.xml140(replaceable) +msgid "NAME" +msgstr "" + +#: ./doc/common/section_cli_glance_manage_images.xml133(parameter) +msgid "--name " +msgstr "" + +#: ./doc/common/section_cli_glance_manage_images.xml135(para) +msgid "The name of the image." +msgstr "" + +#: ./doc/common/section_cli_glance_manage_images.xml140(replaceable) +msgid "DISK_FORMAT" +msgstr "" + +#: ./doc/common/section_cli_glance_manage_images.xml139(parameter) +msgid "--disk-format " +msgstr "" + +#: ./doc/common/section_cli_glance_manage_images.xml141(para) +msgid "" +"The disk format of the image. Acceptable formats are ami, ari, aki, vhd, " +"vmdk, raw, qcow2, vdi, and iso." +msgstr "" + +#: ./doc/common/section_cli_glance_manage_images.xml149(replaceable) +msgid "CONTAINER_FORMAT" +msgstr "" + +#: ./doc/common/section_cli_glance_manage_images.xml148(parameter) +msgid "--container-format " +msgstr "" + +#: ./doc/common/section_cli_glance_manage_images.xml150(para) +msgid "" +"The container format of the image. Acceptable formats are ami, ari, aki, " +"bare, and ovf." +msgstr "" + +#: ./doc/common/section_cli_glance_manage_images.xml157(replaceable) +msgid "TENANT_ID" +msgstr "" + +#: ./doc/common/section_cli_glance_manage_images.xml156(parameter) +msgid "--owner " +msgstr "" + +#: ./doc/common/section_cli_glance_manage_images.xml158(para) +msgid "The tenant who should own the image." +msgstr "" + +#: ./doc/common/section_cli_glance_manage_images.xml164(replaceable) +#: ./doc/common/section_cli_nova_boot_from_volume.xml67(replaceable) +msgid "SIZE" +msgstr "" + +#: ./doc/common/section_cli_glance_manage_images.xml163(parameter) +msgid "--size " +msgstr "" + +#: ./doc/common/section_cli_glance_manage_images.xml165(para) +msgid "The size of image data, in bytes." +msgstr "" + +#: ./doc/common/section_cli_glance_manage_images.xml171(replaceable) +msgid "DISK_GB" +msgstr "" + +#: ./doc/common/section_cli_glance_manage_images.xml170(parameter) +msgid "--min-disk " +msgstr "" + +#: ./doc/common/section_cli_glance_manage_images.xml172(para) +msgid "The minimum size of disk needed to boot image, in gigabytes." +msgstr "" + +#: ./doc/common/section_cli_glance_manage_images.xml178(replaceable) +msgid "DISK_RAM" +msgstr "" + +#: ./doc/common/section_cli_glance_manage_images.xml177(parameter) +msgid "--min-ram " +msgstr "" + +#: ./doc/common/section_cli_glance_manage_images.xml179(para) +msgid "The minimum amount of ram needed to boot image, in megabytes." +msgstr "" + +#: ./doc/common/section_cli_glance_manage_images.xml185(replaceable) +#: ./doc/common/section_cli_glance_manage_images.xml211(replaceable) +msgid "IMAGE_URL" +msgstr "" + +#: ./doc/common/section_cli_glance_manage_images.xml184(parameter) +msgid "--location " +msgstr "" + +#: ./doc/common/section_cli_glance_manage_images.xml186(para) +msgid "" +"The URL where the data for this image resides. For example, if the image " +"data is stored in swift, you could specify " +"swift://account:key@example.com/container/obj." +msgstr "" + +#: ./doc/common/section_cli_glance_manage_images.xml195(replaceable) +msgid "FILE" +msgstr "" + +#: ./doc/common/section_cli_glance_manage_images.xml194(parameter) +msgid "--file " +msgstr "" + +#: ./doc/common/section_cli_glance_manage_images.xml196(para) +msgid "" +"Local file that contains disk image to be uploaded during update. " +"Alternatively, you can pass images to the client through stdin." +msgstr "" + +#: ./doc/common/section_cli_glance_manage_images.xml204(replaceable) +msgid "CHECKSUM" +msgstr "" + +#: ./doc/common/section_cli_glance_manage_images.xml203(parameter) +msgid "--checksum " +msgstr "" + +#: ./doc/common/section_cli_glance_manage_images.xml205(para) +msgid "Hash of image data to use for verification." +msgstr "" + +#: ./doc/common/section_cli_glance_manage_images.xml210(parameter) +msgid "--copy-from " +msgstr "" + +#: ./doc/common/section_cli_glance_manage_images.xml212(para) +msgid "" +"Similar to --location in usage, but indicates that " +"the Image server should immediately copy the data and store it in its " +"configured image store." +msgstr "" + +#: ./doc/common/section_cli_glance_manage_images.xml221(parameter) +msgid "--is-public [True|False]" +msgstr "" + +#: ./doc/common/section_cli_glance_manage_images.xml223(para) +msgid "Makes an image accessible to the public." +msgstr "" + +#: ./doc/common/section_cli_glance_manage_images.xml228(parameter) +msgid "--is-protected [True|False]" +msgstr "" + +#: ./doc/common/section_cli_glance_manage_images.xml230(para) +msgid "Prevents an image from being deleted." +msgstr "" + +#: ./doc/common/section_cli_glance_manage_images.xml236(replaceable) +msgid "KEY" +msgstr "" + +#: ./doc/common/section_cli_glance_manage_images.xml236(replaceable) +msgid "VALUE" +msgstr "" + +#: ./doc/common/section_cli_glance_manage_images.xml235(parameter) +msgid "--property =" +msgstr "" + +#: ./doc/common/section_cli_glance_manage_images.xml237(para) +msgid "" +"Arbitrary property to associate with image. Can be used multiple times." +msgstr "" + +#: ./doc/common/section_cli_glance_manage_images.xml243(parameter) +msgid "--purge-props" +msgstr "" + +#: ./doc/common/section_cli_glance_manage_images.xml244(para) +msgid "" +"Deletes all image properties that are not explicitly set in the update " +"request. Otherwise, those properties not referenced are preserved." +msgstr "" + +#: ./doc/common/section_cli_glance_manage_images.xml251(parameter) +msgid "--human-readable" +msgstr "" + +#: ./doc/common/section_cli_glance_manage_images.xml252(para) +msgid "Prints image size in a human-friendly format." +msgstr "" + +#: ./doc/common/section_cli_glance_manage_images.xml259(para) +msgid "" +"To annotate an image with a property that describes the " +"disk_bus, cdrom_bus, and " +"vif_model:" +msgstr "" + +#: ./doc/common/section_cli_glance_manage_images.xml266(para) +msgid "" +"Currently libvirt will determine the disk/cdrom/vif device models based on " +"the configured hypervisor type (libvirt_type in " +"/etc/nova/nova.conf). For the sake of optimal " +"performance, it will default to using virtio for both disk and VIF (NIC) " +"models. The downside of this approach is that it is not possible to run " +"operating systems that lack virtio drivers, for example, BSD, Solaris, old " +"Linux, and old Windows." +msgstr "" + +#: ./doc/common/section_cli_glance_manage_images.xml273(para) +msgid "" +"If you specify a disk or CD-ROM bus model that is not supported, see . If you specify a VIF model that is not supported, " +"the instance fails to launch. See ." +msgstr "" + +#: ./doc/common/section_cli_glance_manage_images.xml279(para) +msgid "" +"The valid model values depend on the libvirt_type " +"setting, as shown in the following tables:" +msgstr "" + +#: ./doc/common/section_cli_glance_manage_images.xml283(caption) +msgid "Disk and CD-ROM bus model values" +msgstr "" + +#: ./doc/common/section_cli_glance_manage_images.xml288(th) +#: ./doc/common/section_cli_glance_manage_images.xml335(th) +msgid "libvirt_type setting" +msgstr "" + +#: ./doc/common/section_cli_glance_manage_images.xml289(th) +#: ./doc/common/section_cli_glance_manage_images.xml336(th) +msgid "Supported model values" +msgstr "" + +#: ./doc/common/section_cli_glance_manage_images.xml294(td) +#: ./doc/common/section_cli_glance_manage_images.xml341(td) +msgid "qemu or kvm" +msgstr "" + +#: ./doc/common/section_cli_glance_manage_images.xml299(para) +#: ./doc/common/section_cli_glance_manage_images.xml308(para) +#: ./doc/common/section_cli_glance_manage_images.xml346(para) +msgid "virtio" +msgstr "" + +#: ./doc/common/section_cli_glance_manage_images.xml302(para) +msgid "scsi" +msgstr "" + +#: ./doc/common/section_cli_glance_manage_images.xml305(para) +#: ./doc/common/section_cli_glance_manage_images.xml322(para) +msgid "ide" +msgstr "" + +#: ./doc/common/section_cli_glance_manage_images.xml315(td) +#: ./doc/common/section_cli_glance_manage_images.xml319(para) +#: ./doc/common/section_cli_glance_manage_images.xml365(td) +msgid "xen" +msgstr "" + +#: ./doc/common/section_cli_glance_manage_images.xml330(caption) +msgid "VIF model values" +msgstr "" + +#: ./doc/common/section_cli_glance_manage_images.xml349(para) +#: ./doc/common/section_cli_glance_manage_images.xml372(para) +msgid "ne2k_pci" +msgstr "" + +#: ./doc/common/section_cli_glance_manage_images.xml352(para) +#: ./doc/common/section_cli_glance_manage_images.xml375(para) +msgid "pcnet" +msgstr "" + +#: ./doc/common/section_cli_glance_manage_images.xml355(para) +#: ./doc/common/section_cli_glance_manage_images.xml378(para) +msgid "rtl8139" +msgstr "" + +#: ./doc/common/section_cli_glance_manage_images.xml358(para) +#: ./doc/common/section_cli_glance_manage_images.xml381(para) +msgid "e1000" +msgstr "" + +#: ./doc/common/section_cli_glance_manage_images.xml369(para) +msgid "netfront" +msgstr "" + +#: ./doc/common/section_cli_glance_manage_images.xml387(td) +msgid "vmware" +msgstr "" + +#: ./doc/common/section_cli_glance_manage_images.xml392(para) +msgid "VirtualE1000" +msgstr "" + +#: ./doc/common/section_cli_glance_manage_images.xml395(para) +msgid "VirtualPCNet32" +msgstr "" + +#: ./doc/common/section_cli_glance_manage_images.xml398(para) +msgid "VirtualVmxnet" +msgstr "" + +#: ./doc/common/section_cli_glance_manage_images.xml409(title) +#: ./doc/common/section_cli_nova_images.xml125(title) +msgid "Troubleshoot image creation" +msgstr "" + +#: ./doc/common/section_cli_glance_manage_images.xml412(para) +#: ./doc/common/section_cli_nova_manage_images.xml12(para) +#: ./doc/common/section_cli_nova_images.xml12(para) +#: ./doc/common/section_cli_nova_images.xml128(para) +msgid "" +"You cannot create a snapshot from an instance that has an attached volume. " +"Detach the volume, create the image, and re-mount the volume." +msgstr "" + +#: ./doc/common/section_cli_glance_manage_images.xml417(para) +#: ./doc/common/section_cli_nova_images.xml133(para) +msgid "" +"Make sure the version of qemu you are using is version 0.14 or greater. " +"Older versions of qemu result in an \"unknown option -s\"" +" error message in the nova-compute.log." +msgstr "" + +#: ./doc/common/section_cli_glance_manage_images.xml424(para) +#: ./doc/common/section_cli_nova_images.xml140(para) +msgid "" +"Examine the /var/log/nova-api.log and " +"/var/log/nova-compute.log log files for error messages." +msgstr "" + +#: ./doc/common/section_cli_nova_manage_images.xml6(title) +msgid "Create image (nova)" +msgstr "" + +#: ./doc/common/section_cli_nova_manage_images.xml7(para) +#: ./doc/common/section_cli_nova_images.xml7(para) +msgid "" +"You can use the nova client to list images, set and delete image metadata, " +"delete images, and take a snapshot of a running instance to create an image." +msgstr "" + +#: ./doc/common/section_cli_nova_manage_images.xml10(para) +#: ./doc/common/section_cli_nova_images.xml10(para) +msgid "" +"The safest approach is to shut down the instance before you take a snapshot." +msgstr "" + +#: ./doc/common/section_cli_nova_manage_images.xml17(para) +#: ./doc/common/section_cli_nova_images.xml18(para) +msgid "Write any buffered data to disk." +msgstr "" + +#: ./doc/common/section_cli_nova_manage_images.xml18(para) +msgid "" +"For more information, see Taking Snapshots in the " +"OpenStack Operations Guide." +msgstr "" + +#: ./doc/common/section_cli_nova_manage_images.xml25(para) +#: ./doc/common/section_cli_nova_images.xml26(para) +msgid "To create the image, list instances to get the server ID:" +msgstr "" + +#: ./doc/common/section_cli_nova_manage_images.xml33(para) +#: ./doc/common/section_cli_nova_images.xml34(para) +msgid "" +"In this example, the server is named myCirrosServer. Use " +"this server to create a snapshot, as follows: The command " +"creates a qemu snapshot and automatically uploads the image to your " +"repository. Only the tenant that creates the image has access to it." +msgstr "" + +#: ./doc/common/section_cli_nova_manage_images.xml42(para) +#: ./doc/common/section_cli_nova_images.xml43(para) +msgid "Get details for your image to check its status:" +msgstr "" + +#: ./doc/common/section_cli_nova_manage_images.xml78(para) +#: ./doc/common/section_cli_nova_images.xml79(para) +msgid "" +"The image status changes from SAVING to " +"ACTIVE. Only the tenant who creates the image has access " +"to it." +msgstr "" + +#: ./doc/common/section_cli_nova_manage_images.xml84(para) +#: ./doc/common/section_cli_nova_images.xml89(para) +msgid "" +"To launch an instance from your image, include the image ID and flavor ID, " +"as follows:" +msgstr "" + +#. When image changes, this message will be marked fuzzy or untranslated for +#. you. +#. It doesn't matter what you translate it to: it's not used at all. +#: ./doc/common/section_compute-configure-vnc.xml63(None) +msgid "" +"@@image: '../common/figures/novnc/SCH_5009_V00_NUAC-VNC_OpenStack.png'; " +"md5=182dc38019a220c851e1c94aa50f4565" +msgstr "" + +#: ./doc/common/section_compute-configure-vnc.xml6(title) +msgid "VNC console proxy" +msgstr "" + +#: ./doc/common/section_compute-configure-vnc.xml7(para) +msgid "" +"The VNC proxy is an OpenStack component that enables compute service users " +"to access their instances through VNC clients." +msgstr "" + +#: ./doc/common/section_compute-configure-vnc.xml10(para) +msgid "The VNC console connection works as follows:" +msgstr "" + +#: ./doc/common/section_compute-configure-vnc.xml13(para) +msgid "" +"A user connects to the API and gets an access_url such " +"as, http://ip:port/?token=xyz." +msgstr "" + +#: ./doc/common/section_compute-configure-vnc.xml19(para) +msgid "The user pastes the URL in a browser or uses it as a client parameter." +msgstr "" + +#: ./doc/common/section_compute-configure-vnc.xml23(para) +msgid "The browser or client connects to the proxy." +msgstr "" + +#: ./doc/common/section_compute-configure-vnc.xml26(para) +msgid "" +"The proxy talks to nova-" +"consoleauth to authorize the token for the user, and maps the " +"token to the private host and port of the VNC server " +"for an instance." +msgstr "" + +#: ./doc/common/section_compute-configure-vnc.xml31(para) +msgid "" +"The compute host specifies the address that the proxy should use to connect " +"through the nova.conf file option, " +". In this way, the VNC proxy " +"works as a bridge between the public network and private host network." +msgstr "" + +#: ./doc/common/section_compute-configure-vnc.xml39(para) +msgid "" +"The proxy initiates the connection to VNC server and continues to proxy " +"until the session ends." +msgstr "" + +#: ./doc/common/section_compute-configure-vnc.xml43(para) +msgid "" +"The proxy also tunnels the VNC protocol over WebSockets so that the noVNC " +"client can talk VNC." +msgstr "" + +#: ./doc/common/section_compute-configure-vnc.xml45(para) +msgid "In general, the VNC proxy:" +msgstr "" + +#: ./doc/common/section_compute-configure-vnc.xml48(para) +msgid "" +"Bridges between the public network where the clients live and the private " +"network where vncservers live." +msgstr "" + +#: ./doc/common/section_compute-configure-vnc.xml52(para) +msgid "Mediates token authentication." +msgstr "" + +#: ./doc/common/section_compute-configure-vnc.xml55(para) +msgid "" +"Transparently deals with hypervisor-specific connection details to provide a" +" uniform client experience." +msgstr "" + +#: ./doc/common/section_compute-configure-vnc.xml58(title) +msgid "noVNC process" +msgstr "" + +#: ./doc/common/section_compute-configure-vnc.xml71(title) +msgid "About nova-consoleauth" +msgstr "" + +#: ./doc/common/section_compute-configure-vnc.xml73(para) +msgid "" +"Both client proxies leverage a shared service to manage token authentication" +" called nova-consoleauth. This " +"service must be running for either proxy to work. Many proxies of either " +"type can be run against a single nova-" +"consoleauth service in a cluster configuration." +msgstr "" + +#: ./doc/common/section_compute-configure-vnc.xml80(para) +msgid "" +"Do not confuse the nova-" +"consoleauth shared service with nova-" +"console, which is a XenAPI-specific service that most recent VNC " +"proxy architectures do not use." +msgstr "" + +#: ./doc/common/section_compute-configure-vnc.xml87(title) +msgid "Typical deployment" +msgstr "" + +#: ./doc/common/section_compute-configure-vnc.xml88(para) +msgid "A typical deployment has the following components:" +msgstr "" + +#: ./doc/common/section_compute-configure-vnc.xml91(para) +msgid "" +"A nova-consoleauth process. " +"Typically runs on the controller host." +msgstr "" + +#: ./doc/common/section_compute-configure-vnc.xml96(para) +msgid "" +"One or more nova-novncproxy " +"services. Supports browser-based noVNC clients. For simple deployments, this" +" service typically runs on the same machine as nova-api because it operates as a proxy between the public " +"network and the private compute host network." +msgstr "" + +#: ./doc/common/section_compute-configure-vnc.xml105(para) +msgid "" +"One or more nova-xvpvncproxy services. Supports the " +"special Java client discussed here. For simple deployments, this service " +"typically runs on the same machine as nova-" +"api because it acts as a proxy between the public network and " +"the private compute host network." +msgstr "" + +#: ./doc/common/section_compute-configure-vnc.xml114(para) +msgid "" +"One or more compute hosts. These compute hosts must have correctly " +"configured options, as follows." +msgstr "" + +#: ./doc/common/section_compute-configure-vnc.xml120(title) +msgid "VNC configuration options" +msgstr "" + +#: ./doc/common/section_compute-configure-vnc.xml123(para) +msgid "" +"To support live migration, you cannot " +"specify a specific IP address for vncserver_listen, " +"because that IP address does not exist on the destination host." +msgstr "" + +#: ./doc/common/section_compute-configure-vnc.xml130(para) +msgid "" +"The vncserver_proxyclient_address defaults to " +"127.0.0.1, which is the address of the compute host that " +"nova instructs proxies to use when connecting to instance servers." +msgstr "" + +#: ./doc/common/section_compute-configure-vnc.xml134(para) +msgid "For all-in-one XenServer domU deployments, set this to 169.254.0.1." +msgstr "" + +#: ./doc/common/section_compute-configure-vnc.xml136(para) +msgid "" +"For multi-host XenServer domU deployments, set to a dom0 management IP on " +"the same network as the proxies." +msgstr "" + +#: ./doc/common/section_compute-configure-vnc.xml138(para) +msgid "" +"For multi-host libvirt deployments, set to a host management IP on the same " +"network as the proxies." +msgstr "" + +#: ./doc/common/section_compute-configure-vnc.xml144(title) +msgid "nova-novncproxy (noVNC)" +msgstr "" + +#: ./doc/common/section_compute-configure-vnc.xml146(para) +msgid "" +"You must install the noVNC package, which contains the nova-novncproxy service." +msgstr "" + +#: ./doc/common/section_compute-configure-vnc.xml149(para) +msgid "As root, run the following command:" +msgstr "" + +#: ./doc/common/section_compute-configure-vnc.xml151(para) +msgid "The service starts automatically on installation." +msgstr "" + +#: ./doc/common/section_compute-configure-vnc.xml152(para) +msgid "To restart it, run the following command:" +msgstr "" + +#: ./doc/common/section_compute-configure-vnc.xml154(para) +msgid "" +"The configuration option parameter should point to your " +"nova.conf file, which includes the message queue server" +" address and credentials." +msgstr "" + +#: ./doc/common/section_compute-configure-vnc.xml157(para) +msgid "" +"By default, nova-novncproxy binds" +" on 0.0.0.0:6080." +msgstr "" + +#: ./doc/common/section_compute-configure-vnc.xml160(para) +msgid "" +"To connect the service to your nova deployment, add the following " +"configuration options to your nova.conf file:" +msgstr "" + +#: ./doc/common/section_compute-configure-vnc.xml165(para) +msgid "vncserver_listen=0.0.0.0" +msgstr "" + +#: ./doc/common/section_compute-configure-vnc.xml168(para) +msgid "" +"Specifies the address on which the VNC service should bind. Make sure it is " +"assigned one of the compute node interfaces. This address is the one used by" +" your domain file." +msgstr "" + +#: ./doc/common/section_compute-configure-vnc.xml174(para) +msgid "" +"To use live migration, use the 0.0.0.0 address." +msgstr "" + +#: ./doc/common/section_compute-configure-vnc.xml179(para) +msgid "" +"vncserver_ proxyclient_ address " +"=127.0.0.1" +msgstr "" + +#: ./doc/common/section_compute-configure-vnc.xml183(para) +msgid "" +"The address of the compute host that nova instructs proxies to use when " +"connecting to instance vncservers." +msgstr "" + +#: ./doc/common/section_compute-configure-vnc.xml191(title) +msgid "Frequently asked questions about VNC access to virtual machines" +msgstr "" + +#: ./doc/common/section_compute-configure-vnc.xml197(literal) +msgid "nova-xvpvncproxy" +msgstr "" + +#: ./doc/common/section_compute-configure-vnc.xml198(systemitem) +msgid "nova-novncproxy" +msgstr "" + +#: ./doc/common/section_compute-configure-vnc.xml196(emphasis) +msgid "" +"Q: What is the difference between and ?" +msgstr "" + +#: ./doc/common/section_compute-configure-vnc.xml200(para) +msgid "" +"A: nova-xvpvncproxy, which ships with nova, is a proxy " +"that supports a simple Java client. nova-" +"novncproxy uses noVNC to provide VNC support through a web " +"browser." +msgstr "" + +#: ./doc/common/section_compute-configure-vnc.xml207(emphasis) +msgid "Q: I want VNC support in the Dashboard. What services do I need?" +msgstr "" + +#: ./doc/common/section_compute-configure-vnc.xml209(para) +msgid "" +"A: You need nova-novncproxy, " +"nova-consoleauth, and correctly " +"configured compute hosts." +msgstr "" + +#: ./doc/common/section_compute-configure-vnc.xml215(emphasis) +msgid "" +"Q: When I use or click on the VNC tab of the Dashboard, it " +"hangs. Why?" +msgstr "" + +#: ./doc/common/section_compute-configure-vnc.xml218(para) +msgid "" +"A: Make sure you are running nova-" +"consoleauth (in addition to nova-" +"novncproxy). The proxies rely on nova-consoleauth to validate tokens, and waits for a reply " +"from them until a timeout is reached." +msgstr "" + +#: ./doc/common/section_compute-configure-vnc.xml227(emphasis) +msgid "" +"Q: My VNC proxy worked fine during my all-in-one test, but now it doesn't " +"work on multi host. Why?" +msgstr "" + +#: ./doc/common/section_compute-configure-vnc.xml230(para) +msgid "" +"A: The default options work for an all-in-one install, but changes must be " +"made on your compute hosts once you start to build a cluster. As an example," +" suppose you have two servers:" +msgstr "" + +#: ./doc/common/section_compute-configure-vnc.xml236(para) +msgid "" +"Your nova-compute configuration " +"file must set the following values:" +msgstr "" + +#: ./doc/common/section_compute-configure-vnc.xml248(para) +msgid "" +"novncproxy_base_url and " +"xvpvncproxy_base_url use a public IP; this is the URL " +"that is ultimately returned to clients, which generally do not have access " +"to your private network. Your PROXYSERVER must be able to reach " +"vncserver_proxyclient_address, because that is the " +"address over which the VNC connection is proxied." +msgstr "" + +#: ./doc/common/section_compute-configure-vnc.xml260(emphasis) +msgid "Q: My noVNC does not work with recent versions of web browsers. Why?" +msgstr "" + +#: ./doc/common/section_compute-configure-vnc.xml263(para) +msgid "" +"A: Make sure you have installed python-numpy, which is " +"required to support a newer version of the WebSocket protocol (HyBi-07+)." +msgstr "" + +#: ./doc/common/section_compute-configure-vnc.xml270(emphasis) +msgid "" +"Q: How do I adjust the dimensions of the VNC window image in the OpenStack " +"dashboard?" +msgstr "" + +#: ./doc/common/section_compute-configure-vnc.xml273(para) +msgid "" +"A: These values are hard-coded in a Django HTML template. To alter them, " +"edit the _detail_vnc.html template file. The location " +"of this file varies based on Linux distribution. On Ubuntu 12.04, the file " +"is at " +"/usr/share/pyshared/horizon/dashboards/nova/instances/templates/instances/_detail_vnc.html." +msgstr "" + +#: ./doc/common/section_compute-configure-vnc.xml279(para) +msgid "" +"Modify the and options, as " +"follows:" +msgstr "" + +#: ./doc/common/section_cli_cinder_commands.xml11(title) +msgid "cinder commands" +msgstr "" + +#: ./doc/common/section_cli_cinder_commands.xml12(para) +msgid "" +"The cinder client is the command-line interface (CLI) for the OpenStack " +"Block Storage API and its extensions." +msgstr "" + +#: ./doc/common/section_cli_cinder_commands.xml14(para) +#: ./doc/common/section_cli_keystone_commands.xml14(para) +#: ./doc/common/section_cli_ceilometer_commands.xml14(para) +#: ./doc/common/section_cli_swift_commands.xml14(para) +#: ./doc/common/section_cli_neutron_commands.xml14(para) +#: ./doc/common/section_cli_heat_commands.xml14(para) +#: ./doc/common/section_cli_nova_commands.xml14(para) +#: ./doc/common/section_cli_glance_commands.xml14(para) +msgid "For help on a specific command, enter:" +msgstr "" + +#: ./doc/common/section_cli_cinder_commands.xml17(option) +#: ./doc/common/section_cli_keystone_commands.xml17(option) +#: ./doc/common/section_cli_ceilometer_commands.xml17(option) +#: ./doc/common/section_cli_swift_commands.xml17(option) +#: ./doc/common/section_cli_neutron_commands.xml17(option) +#: ./doc/common/section_cli_heat_commands.xml17(option) +#: ./doc/common/section_cli_nova_commands.xml17(option) +#: ./doc/common/section_cli_glance_commands.xml17(option) +msgid "help" +msgstr "" + +#: ./doc/common/section_cli_cinder_commands.xml17(replaceable) +#: ./doc/common/section_cli_keystone_commands.xml17(replaceable) +#: ./doc/common/section_cli_ceilometer_commands.xml17(replaceable) +#: ./doc/common/section_cli_swift_commands.xml17(replaceable) +#: ./doc/common/section_cli_neutron_commands.xml17(replaceable) +#: ./doc/common/section_cli_keystone_example_usage.xml12(replaceable) +#: ./doc/common/section_cli_heat_commands.xml17(replaceable) +#: ./doc/common/section_cli_nova_commands.xml17(replaceable) +#: ./doc/common/section_cli_glance_commands.xml17(replaceable) +msgid "COMMAND" +msgstr "" + +#: ./doc/common/section_cli_cinder_commands.xml20(title) +msgid "cinder usage" +msgstr "" + +#: ./doc/common/section_cli_cinder_commands.xml33(title) +msgid "cinder positional arguments" +msgstr "" + +#: ./doc/common/section_cli_cinder_commands.xml124(title) +msgid "cinder optional arguments" +msgstr "" + +#: ./doc/common/section_cli_cinder_commands.xml156(title) +msgid "cinder absolute-limits command" +msgstr "" + +#: ./doc/common/section_cli_cinder_commands.xml164(title) +msgid "cinder availability-zone-list command" +msgstr "" + +#: ./doc/common/section_cli_cinder_commands.xml172(title) +msgid "cinder backup-create command" +msgstr "" + +#: ./doc/common/section_cli_cinder_commands.xml194(title) +msgid "cinder backup-delete command" +msgstr "" + +#: ./doc/common/section_cli_cinder_commands.xml205(title) +msgid "cinder backup-list command" +msgstr "" + +#: ./doc/common/section_cli_cinder_commands.xml213(title) +msgid "cinder backup-restore command" +msgstr "" + +#: ./doc/common/section_cli_cinder_commands.xml227(title) +msgid "cinder backup-show command" +msgstr "" + +#: ./doc/common/section_cli_cinder_commands.xml238(title) +msgid "cinder create command" +msgstr "" + +#: ./doc/common/section_cli_cinder_commands.xml275(title) +msgid "cinder credentials command" +msgstr "" + +#: ./doc/common/section_cli_cinder_commands.xml283(title) +msgid "cinder delete command" +msgstr "" + +#: ./doc/common/section_cli_cinder_commands.xml294(title) +msgid "cinder encryption-type-create command" +msgstr "" + +#: ./doc/common/section_cli_cinder_commands.xml321(title) +msgid "cinder encryption-type-list command" +msgstr "" + +#: ./doc/common/section_cli_cinder_commands.xml329(title) +msgid "cinder encryption-type-show command" +msgstr "" + +#: ./doc/common/section_cli_cinder_commands.xml340(title) +msgid "cinder endpoints command" +msgstr "" + +#: ./doc/common/section_cli_cinder_commands.xml348(title) +msgid "cinder extend command" +msgstr "" + +#: ./doc/common/section_cli_cinder_commands.xml360(title) +msgid "cinder extra-specs-list command" +msgstr "" + +#: ./doc/common/section_cli_cinder_commands.xml368(title) +msgid "cinder force-delete command" +msgstr "" + +#: ./doc/common/section_cli_cinder_commands.xml379(title) +msgid "cinder list command" +msgstr "" + +#: ./doc/common/section_cli_cinder_commands.xml398(title) +msgid "cinder list-extensions command" +msgstr "" + +#: ./doc/common/section_cli_cinder_commands.xml406(title) +msgid "cinder metadata command" +msgstr "" + +#: ./doc/common/section_cli_cinder_commands.xml419(title) +msgid "cinder metadata-show command" +msgstr "" + +#: ./doc/common/section_cli_cinder_commands.xml430(title) +msgid "cinder metadata-update-all command" +msgstr "" + +#: ./doc/common/section_cli_cinder_commands.xml442(title) +msgid "cinder migrate command" +msgstr "" + +#: ./doc/common/section_cli_cinder_commands.xml460(title) +msgid "cinder qos-associate command" +msgstr "" + +#: ./doc/common/section_cli_cinder_commands.xml472(title) +msgid "cinder qos-create command" +msgstr "" + +#: ./doc/common/section_cli_cinder_commands.xml484(title) +msgid "cinder qos-delete command" +msgstr "" + +#: ./doc/common/section_cli_cinder_commands.xml499(title) +msgid "cinder qos-disassociate command" +msgstr "" + +#: ./doc/common/section_cli_cinder_commands.xml511(title) +msgid "cinder qos-disassociate-all command" +msgstr "" + +#: ./doc/common/section_cli_cinder_commands.xml522(title) +msgid "cinder qos-get-association command" +msgstr "" + +#: ./doc/common/section_cli_cinder_commands.xml533(title) +msgid "cinder qos-key command" +msgstr "" + +#: ./doc/common/section_cli_cinder_commands.xml546(title) +msgid "cinder qos-list command" +msgstr "" + +#: ./doc/common/section_cli_cinder_commands.xml554(title) +msgid "cinder qos-show command" +msgstr "" + +#: ./doc/common/section_cli_cinder_commands.xml565(title) +msgid "cinder quota-class-show command" +msgstr "" + +#: ./doc/common/section_cli_cinder_commands.xml576(title) +msgid "cinder quota-class-update command" +msgstr "" + +#: ./doc/common/section_cli_cinder_commands.xml600(title) +msgid "cinder quota-defaults command" +msgstr "" + +#: ./doc/common/section_cli_cinder_commands.xml611(title) +msgid "cinder quota-show command" +msgstr "" + +#: ./doc/common/section_cli_cinder_commands.xml622(title) +msgid "cinder quota-update command" +msgstr "" + +#: ./doc/common/section_cli_cinder_commands.xml645(title) +msgid "cinder quota-usage command" +msgstr "" + +#: ./doc/common/section_cli_cinder_commands.xml656(title) +msgid "cinder rate-limits command" +msgstr "" + +#: ./doc/common/section_cli_cinder_commands.xml664(title) +msgid "cinder readonly-mode-update command" +msgstr "" + +#: ./doc/common/section_cli_cinder_commands.xml678(title) +msgid "cinder rename command" +msgstr "" + +#: ./doc/common/section_cli_cinder_commands.xml695(title) +msgid "cinder reset-state command" +msgstr "" + +#: ./doc/common/section_cli_cinder_commands.xml711(title) +msgid "cinder service-disable command" +msgstr "" + +#: ./doc/common/section_cli_cinder_commands.xml723(title) +msgid "cinder service-enable command" +msgstr "" + +#: ./doc/common/section_cli_cinder_commands.xml735(title) +msgid "cinder service-list command" +msgstr "" + +#: ./doc/common/section_cli_cinder_commands.xml747(title) +msgid "cinder show command" +msgstr "" + +#: ./doc/common/section_cli_cinder_commands.xml758(title) +msgid "cinder snapshot-create command" +msgstr "" + +#: ./doc/common/section_cli_cinder_commands.xml780(title) +msgid "cinder snapshot-delete command" +msgstr "" + +#: ./doc/common/section_cli_cinder_commands.xml791(title) +msgid "cinder snapshot-list command" +msgstr "" + +#: ./doc/common/section_cli_cinder_commands.xml810(title) +msgid "cinder snapshot-metadata command" +msgstr "" + +#: ./doc/common/section_cli_cinder_commands.xml824(title) +msgid "cinder snapshot-metadata-show command" +msgstr "" + +#: ./doc/common/section_cli_cinder_commands.xml835(title) +msgid "cinder snapshot-metadata-update-all command" +msgstr "" + +#: ./doc/common/section_cli_cinder_commands.xml848(title) +msgid "cinder snapshot-rename command" +msgstr "" + +#: ./doc/common/section_cli_cinder_commands.xml865(title) +msgid "cinder snapshot-reset-state command" +msgstr "" + +#: ./doc/common/section_cli_cinder_commands.xml883(title) +msgid "cinder snapshot-show command" +msgstr "" + +#: ./doc/common/section_cli_cinder_commands.xml894(title) +msgid "cinder transfer-accept command" +msgstr "" + +#: ./doc/common/section_cli_cinder_commands.xml906(title) +msgid "cinder transfer-create command" +msgstr "" + +#: ./doc/common/section_cli_cinder_commands.xml921(title) +msgid "cinder transfer-delete command" +msgstr "" + +#: ./doc/common/section_cli_cinder_commands.xml932(title) +msgid "cinder transfer-list command" +msgstr "" + +#: ./doc/common/section_cli_cinder_commands.xml940(title) +msgid "cinder transfer-show command" +msgstr "" + +#: ./doc/common/section_cli_cinder_commands.xml951(title) +msgid "cinder type-create command" +msgstr "" + +#: ./doc/common/section_cli_cinder_commands.xml962(title) +msgid "cinder type-delete command" +msgstr "" + +#: ./doc/common/section_cli_cinder_commands.xml973(title) +msgid "cinder type-key command" +msgstr "" + +#: ./doc/common/section_cli_cinder_commands.xml986(title) +msgid "cinder type-list command" +msgstr "" + +#: ./doc/common/section_cli_cinder_commands.xml994(title) +msgid "cinder upload-to-image command" +msgstr "" + +#: ./doc/common/section_cli_nova_resizerebuild.xml6(title) +msgid "Change the size of your server" +msgstr "" + +#: ./doc/common/section_cli_nova_resizerebuild.xml7(para) +msgid "You change the size of a server by changing its flavor." +msgstr "" + +#: ./doc/common/section_cli_nova_resizerebuild.xml10(para) +#: ./doc/common/section_cli_nova_boot.xml102(para) +msgid "List the available flavors:" +msgstr "" + +#: ./doc/common/section_cli_nova_resizerebuild.xml23(para) +msgid "Show information about your server, including its size:" +msgstr "" + +#: ./doc/common/section_cli_nova_resizerebuild.xml57(para) +msgid "The size of the server is m1.small (2)." +msgstr "" + +#: ./doc/common/section_cli_nova_resizerebuild.xml61(para) +msgid "" +"To resize the server, pass the server ID and the desired flavor to the nova " +" command. Include the --poll parameter to" +" report the resize progress." +msgstr "" + +#: ./doc/common/section_cli_nova_resizerebuild.xml70(para) +msgid "Show the status for your server:" +msgstr "" + +#: ./doc/common/section_cli_nova_resizerebuild.xml79(para) +msgid "" +"When the resize completes, the status becomes " +"VERIFY_RESIZE. To confirm the resize:" +msgstr "" + +#: ./doc/common/section_cli_nova_resizerebuild.xml83(para) +#: ./doc/common/section_cli_nova_resizerebuild.xml89(para) +msgid "The server status becomes ACTIVE." +msgstr "" + +#: ./doc/common/section_cli_nova_resizerebuild.xml86(para) +msgid "" +"If the resize fails or does not work as expected, you can revert the resize:" +msgstr "" + +#. When image changes, this message will be marked fuzzy or untranslated for +#. you. +#. It doesn't matter what you translate it to: it's not used at all. +#: ./doc/common/section_getstart_dashboard.xml14(None) +msgid "" +"@@image: 'figures/horizon-screenshot.jpg'; " +"md5=9471047adf0d93713be7f54b9db2b53c" +msgstr "" + +#: ./doc/common/section_getstart_dashboard.xml5(title) +#: ./doc/common/ch_getstart.xml36(link) +msgid "Dashboard" +msgstr "" + +#: ./doc/common/section_getstart_dashboard.xml6(para) +msgid "" +"The dashboard is a modular Django web application that " +"provides a graphical interface to OpenStack services." +msgstr "" + +#: ./doc/common/section_getstart_dashboard.xml18(para) +msgid "" +"The dashboard is usually deployed through mod_wsgi in Apache. You " +"can modify the dashboard code to make it suitable for different sites." +msgstr "" + +#: ./doc/common/section_getstart_dashboard.xml22(para) +msgid "" +"From a network architecture point of view, this service must be accessible " +"to customers and the public API for each OpenStack service. To use the " +"administrator functionality for other services, it must also connect to " +"Admin API endpoints, which should not be accessible by customers." +msgstr "" + +#: ./doc/common/section_cli_nova_quotas.xml13(title) +msgid "Manage Compute service quotas" +msgstr "" + +#: ./doc/common/section_cli_nova_quotas.xml14(para) +msgid "" +"As an administrative user, you can use the commands, which " +"are provided by the python-novaclient package, to update " +"the Compute Service quotas for a specific tenant or tenant user, as well as " +"update the quota defaults for a new tenant." +msgstr "" + +#: ./doc/common/section_cli_nova_quotas.xml19(caption) +msgid "Compute Quota Descriptions" +msgstr "" + +#: ./doc/common/section_cli_nova_quotas.xml24(td) +msgid "Quota Name" +msgstr "" + +#: ./doc/common/section_cli_nova_quotas.xml27(td) +#: ./doc/common/section_cli_nova_boot_from_volume.xml73(th) +#: ./doc/common/ch_getstart.xml29(th) +#: ./doc/common/section_cli_nova_customize_flavors.xml35(td) +#: ./doc/common/section_identity-configure.xml27(td) +#: ./doc/common/section_cli_install.xml32(th) +#: ./doc/common/tables/nova-cells.xml14(th) +#: ./doc/common/tables/glance-policy.xml14(th) +#: ./doc/common/tables/neutron-mlnx.xml14(th) +#: ./doc/common/tables/nova-ipv6.xml14(th) +#: ./doc/common/tables/cinder-eqlx.xml14(th) +#: ./doc/common/tables/swift-object-expirer-filter-catch_errors.xml13(th) +#: ./doc/common/tables/swift-object-expirer-filter-cache.xml13(th) +#: ./doc/common/tables/cinder-netapp_cdot_extraspecs.xml12(th) +#: ./doc/common/tables/swift-proxy-server-filter-cache.xml13(th) +#: ./doc/common/tables/neutron-ml2_l2pop.xml14(th) +#: ./doc/common/tables/glance-qpid.xml14(th) +#: ./doc/common/tables/swift-container-server-DEFAULT.xml13(th) +#: ./doc/common/tables/nova-volumes.xml14(th) +#: ./doc/common/tables/glance-gridfs.xml14(th) +#: ./doc/common/tables/neutron-ml2_arista.xml14(th) +#: ./doc/common/tables/glance-filesystem.xml14(th) +#: ./doc/common/tables/swift-container-server-container-updater.xml13(th) +#: ./doc/common/tables/cinder-storage_gpfs.xml14(th) +#: ./doc/common/tables/nova-docker.xml14(th) +#: ./doc/common/tables/cinder-nexenta_iscsi.xml14(th) +#: ./doc/common/tables/nova-tilera.xml14(th) +#: ./doc/common/tables/nova-ca.xml14(th) +#: ./doc/common/tables/swift-account-server-filter-recon.xml13(th) +#: ./doc/common/tables/cinder-huawei.xml14(th) +#: ./doc/common/tables/swift-container-server-container-replicator.xml13(th) +#: ./doc/common/tables/nova-glance.xml14(th) +#: ./doc/common/tables/nova-neutron.xml14(th) +#: ./doc/common/tables/cinder-backups_ceph.xml14(th) +#: ./doc/common/tables/swift-proxy-server-filter-name_check.xml13(th) +#: ./doc/common/tables/nova-metadata.xml14(th) +#: ./doc/common/tables/glance-s3.xml14(th) +#: ./doc/common/tables/neutron-kombu.xml14(th) +#: ./doc/common/tables/swift-proxy-server-filter-ratelimit.xml13(th) +#: ./doc/common/tables/cinder-block-device.xml14(th) +#: ./doc/common/tables/cinder-zones.xml14(th) +#: ./doc/common/tables/cinder-netapp_7mode_iscsi.xml14(th) +#: ./doc/common/tables/swift-container-server-container-sync.xml13(th) +#: ./doc/common/tables/neutron-common.xml14(th) +#: ./doc/common/tables/swift-object-server-object-auditor.xml13(th) +#: ./doc/common/tables/neutron-openvswitch_agent.xml14(th) +#: ./doc/common/tables/cinder-compute.xml14(th) +#: ./doc/common/tables/cinder-lvm.xml14(th) +#: ./doc/common/tables/cinder-storage_nfs.xml14(th) +#: ./doc/common/tables/neutron-plumgrid.xml14(th) +#: ./doc/common/tables/nova-hypervisor.xml14(th) +#: ./doc/common/tables/swift-proxy-server-filter-tempurl.xml13(th) +#: ./doc/common/tables/cinder-quota.xml14(th) +#: ./doc/common/tables/swift-proxy-server-filter-healthcheck.xml13(th) +#: ./doc/common/tables/swift-object-expirer-DEFAULT.xml13(th) +#: ./doc/common/tables/nova-console.xml14(th) +#: ./doc/common/tables/swift-swift-bench-bench.xml13(th) +#: ./doc/common/tables/nova-common.xml14(th) +#: ./doc/common/tables/swift-object-server-object-updater.xml13(th) +#: ./doc/common/tables/glance-zmq.xml14(th) +#: ./doc/common/tables/swift-proxy-server-filter-account-quotas.xml13(th) +#: ./doc/common/tables/swift-proxy-server-app-proxy-server.xml13(th) +#: ./doc/common/tables/nova-keymgr.xml14(th) +#: ./doc/common/tables/neutron-api.xml14(th) +#: ./doc/common/tables/nova-testing.xml14(th) +#: ./doc/common/tables/cinder-backups.xml14(th) +#: ./doc/common/tables/swift-container-server-pipeline-main.xml13(th) +#: ./doc/common/tables/swift-rsyncd-object.xml13(th) +#: ./doc/common/tables/nova-s3.xml14(th) +#: ./doc/common/tables/neutron-openvswitch.xml14(th) +#: ./doc/common/tables/nova-zookeeper.xml14(th) +#: ./doc/common/tables/cinder-rpc.xml14(th) +#: ./doc/common/tables/cinder-api.xml14(th) +#: ./doc/common/tables/cinder-windows.xml14(th) +#: ./doc/common/tables/swift-object-server-pipeline-main.xml13(th) +#: ./doc/common/tables/cinder-san.xml14(th) +#: ./doc/common/tables/swift-account-server-app-account-server.xml13(th) +#: ./doc/common/tables/cinder-keymgr.xml14(th) +#: ./doc/common/tables/nova-db.xml14(th) +#: ./doc/common/tables/neutron-ml2_vxlan.xml14(th) +#: ./doc/common/tables/glance-logging.xml14(th) +#: ./doc/common/tables/glance-wsgi.xml14(th) +#: ./doc/common/tables/nova-periodic.xml14(th) +#: ./doc/common/tables/swift-account-server-filter-healthcheck.xml13(th) +#: ./doc/common/tables/cinder-images.xml14(th) +#: ./doc/common/tables/swift-container-server-app-container-server.xml13(th) +#: ./doc/common/tables/swift-proxy-server-filter-slo.xml13(th) +#: ./doc/common/tables/neutron-wsgi.xml14(th) +#: ./doc/common/tables/neutron-scheduler.xml14(th) +#: ./doc/common/tables/glance-rbd.xml14(th) +#: ./doc/common/tables/neutron-metadata.xml14(th) +#: ./doc/common/tables/cinder-hp3par.xml14(th) +#: ./doc/common/tables/cinder-storage_ceph.xml14(th) +#: ./doc/common/tables/nova-livemigration.xml14(th) +#: ./doc/common/tables/nova-ldap.xml14(th) +#: ./doc/common/tables/nova-fping.xml14(th) +#: ./doc/common/tables/neutron-securitygroups.xml14(th) +#: ./doc/common/tables/cinder-netapp_cdot_iscsi.xml14(th) +#: ./doc/common/tables/nova-ec2.xml14(th) +#: ./doc/common/tables/swift-account-server-account-auditor.xml13(th) +#: ./doc/common/tables/swift-object-server-DEFAULT.xml13(th) +#: ./doc/common/tables/cinder-nexenta_nfs.xml14(th) +#: ./doc/common/tables/swift-proxy-server-filter-bulk.xml13(th) +#: ./doc/common/tables/nova-policy.xml14(th) +#: ./doc/common/tables/neutron-logging.xml14(th) +#: ./doc/common/tables/glance-rpc.xml14(th) +#: ./doc/common/tables/nova-authentication.xml14(th) +#: ./doc/common/tables/cinder-vmware.xml14(th) +#: ./doc/common/tables/glance-sheepdog.xml14(th) +#: ./doc/common/tables/neutron-qpid.xml14(th) +#: ./doc/common/tables/neutron-hyperv_agent.xml14(th) +#: ./doc/common/tables/glance-swift.xml14(th) +#: ./doc/common/tables/swift-account-server-DEFAULT.xml13(th) +#: ./doc/common/tables/neutron-bigswitch.xml14(th) +#: ./doc/common/tables/nova-libvirt.xml14(th) +#: ./doc/common/tables/neutron-lbaas.xml14(th) +#: ./doc/common/tables/cinder-backups_swift.xml14(th) +#: ./doc/common/tables/neutron-ml2_cisco.xml14(th) +#: ./doc/common/tables/nova-pci.xml14(th) +#: ./doc/common/tables/swift-proxy-server-filter-proxy-logging.xml13(th) +#: ./doc/common/tables/neutron-varmour.xml14(th) +#: ./doc/common/tables/glance-imagecache.xml14(th) +#: ./doc/common/tables/swift-rsyncd-account.xml13(th) +#: ./doc/common/tables/cinder-storage.xml14(th) +#: ./doc/common/tables/nova-vpn.xml14(th) +#: ./doc/common/tables/nova-wsgi.xml14(th) +#: ./doc/common/tables/cinder-storage_glusterfs.xml14(th) +#: ./doc/common/tables/swift-container-server-filter-healthcheck.xml13(th) +#: ./doc/common/tables/nova-availabilityzones.xml14(th) +#: ./doc/common/tables/nova-vnc.xml14(th) +#: ./doc/common/tables/swift-swift-swift-constraints.xml13(th) +#: ./doc/common/tables/neutron-cisco.xml14(th) +#: ./doc/common/tables/nova-hyperv.xml14(th) +#: ./doc/common/tables/swift-object-server-filter-recon.xml13(th) +#: ./doc/common/tables/cinder-coraid.xml14(th) +#: ./doc/common/tables/swift-container-server-container-auditor.xml13(th) +#: ./doc/common/tables/swift-proxy-server-filter-catch_errors.xml13(th) +#: ./doc/common/tables/nova-vmware.xml14(th) +#: ./doc/common/tables/nova-logging.xml14(th) +#: ./doc/common/tables/nova-xen.xml14(th) +#: ./doc/common/tables/swift-proxy-server-filter-list-endpoints.xml13(th) +#: ./doc/common/tables/neutron-nicira.xml14(th) +#: ./doc/common/tables/swift-memcache-memcache.xml13(th) +#: ./doc/common/tables/swift-proxy-server-filter-keystoneauth.xml13(th) +#: ./doc/common/tables/neutron-ml2.xml14(th) +#: ./doc/common/tables/neutron-linuxbridge.xml14(th) +#: ./doc/common/tables/cinder-netapp_7mode_nfs.xml14(th) +#: ./doc/common/tables/glance-common.xml14(th) +#: ./doc/common/tables/nova-network.xml14(th) +#: ./doc/common/tables/cinder-scality.xml14(th) +#: ./doc/common/tables/neutron-notifier.xml14(th) +#: ./doc/common/tables/cinder-common.xml14(th) +#: ./doc/common/tables/nova-trustedcomputing.xml14(th) +#: ./doc/common/tables/neutron-ml2_flat.xml14(th) +#: ./doc/common/tables/nova-configdrive.xml14(th) +#: ./doc/common/tables/cinder-database.xml14(th) +#: ./doc/common/tables/neutron-rpc.xml14(th) +#: ./doc/common/tables/nova-zeromq.xml14(th) +#: ./doc/common/tables/glance-testing.xml14(th) +#: ./doc/common/tables/swift-proxy-server-filter-tempauth.xml13(th) +#: ./doc/common/tables/glance-registry.xml14(th) +#: ./doc/common/tables/swift-object-server-object-replicator.xml13(th) +#: ./doc/common/tables/swift-dispersion-dispersion.xml13(th) +#: ./doc/common/tables/swift-account-server-account-replicator.xml13(th) +#: ./doc/common/tables/neutron-fwaas.xml14(th) +#: ./doc/common/tables/glance-rabbitmq.xml14(th) +#: ./doc/common/tables/cinder-backups_tsm.xml14(th) +#: ./doc/common/tables/nova-qpid.xml14(th) +#: ./doc/common/tables/cinder-connection.xml14(th) +#: ./doc/common/tables/swift-proxy-server-filter-authtoken.xml13(th) +#: ./doc/common/tables/neutron-zeromq.xml14(th) +#: ./doc/common/tables/neutron-vpn.xml14(th) +#: ./doc/common/tables/cinder-log.xml14(th) +#: ./doc/common/tables/neutron-agent.xml14(th) +#: ./doc/common/tables/neutron-ryu.xml14(th) +#: ./doc/common/tables/swift-object-server-app-object-server.xml13(th) +#: ./doc/common/tables/neutron-policy.xml14(th) +#: ./doc/common/tables/swift-proxy-server-DEFAULT.xml13(th) +#: ./doc/common/tables/swift-proxy-server-filter-staticweb.xml13(th) +#: ./doc/common/tables/swift-object-expirer-app-proxy-server.xml13(th) +#: ./doc/common/tables/neutron-meta.xml14(th) +#: ./doc/common/tables/neutron-ssl.xml14(th) +#: ./doc/common/tables/nova-scheduling.xml14(th) +#: ./doc/common/tables/swift-drive-audit-drive-audit.xml13(th) +#: ./doc/common/tables/swift-container-server-filter-recon.xml13(th) +#: ./doc/common/tables/neutron-db.xml14(th) +#: ./doc/common/tables/neutron-brocade.xml14(th) +#: ./doc/common/tables/swift-object-expirer-pipeline-main.xml13(th) +#: ./doc/common/tables/neutron-linuxbridge_agent.xml14(th) +#: ./doc/common/tables/cinder-xiv.xml14(th) +#: ./doc/common/tables/neutron-rabbitmq.xml14(th) +#: ./doc/common/tables/swift-proxy-server-filter-container-quotas.xml13(th) +#: ./doc/common/tables/swift-swift-swift-hash.xml13(th) +#: ./doc/common/tables/cinder-auth.xml14(th) +#: ./doc/common/tables/nova-kombu.xml14(th) +#: ./doc/common/tables/swift-proxy-server-filter-formpost.xml13(th) +#: ./doc/common/tables/cinder-hds.xml14(th) +#: ./doc/common/tables/nova-spice.xml14(th) +#: ./doc/common/tables/neutron-midonet.xml14(th) +#: ./doc/common/tables/cinder-storwize.xml14(th) +#: ./doc/common/tables/cinder-solidfire.xml14(th) +#: ./doc/common/tables/glance-ssl.xml14(th) +#: ./doc/common/tables/nova-apiv3.xml14(th) +#: ./doc/common/tables/glance-db.xml14(th) +#: ./doc/common/tables/nova-api.xml14(th) +#: ./doc/common/tables/swift-rsyncd-container.xml13(th) +#: ./doc/common/tables/cinder-san-solaris.xml14(th) +#: ./doc/common/tables/cinder-netapp_cdot_nfs.xml14(th) +#: ./doc/common/tables/swift-object-server-filter-healthcheck.xml13(th) +#: ./doc/common/tables/glance-paste.xml14(th) +#: ./doc/common/tables/neutron-quotas.xml14(th) +#: ./doc/common/tables/nova-rpc.xml14(th) +#: ./doc/common/tables/nova-baremetal.xml14(th) +#: ./doc/common/tables/swift-account-server-pipeline-main.xml13(th) +#: ./doc/common/tables/glance-api.xml14(th) +#: ./doc/common/tables/cinder-scheduler.xml14(th) +#: ./doc/common/tables/neutron-ml2_ncs.xml14(th) +#: ./doc/common/tables/neutron-nec.xml14(th) +#: ./doc/common/tables/neutron-testing.xml14(th) +#: ./doc/common/tables/swift-object-expirer-object-expirer.xml13(th) +#: ./doc/common/tables/glance-cinder.xml14(th) +#: ./doc/common/tables/nova-redis.xml14(th) +#: ./doc/common/tables/neutron-embrane.xml14(th) +#: ./doc/common/tables/swift-proxy-server-pipeline-main.xml13(th) +#: ./doc/common/tables/nova-upgrade_levels.xml14(th) +#: ./doc/common/tables/swift-proxy-server-filter-cname_lookup.xml13(th) +#: ./doc/common/tables/nova-rabbitmq.xml14(th) +#: ./doc/common/tables/cinder-zadara.xml14(th) +#: ./doc/common/tables/swift-account-server-account-reaper.xml13(th) +#: ./doc/common/tables/nova-quota.xml14(th) +#: ./doc/common/tables/nova-conductor.xml14(th) +#: ./doc/common/tables/nova-compute.xml14(th) +#: ./doc/common/tables/swift-proxy-server-filter-domain_remap.xml13(th) +#: ./doc/common/tables/neutron-hyperv.xml14(th) +#: ./doc/common/tables/cinder-storage_xen.xml14(th) +#: ./doc/common/tables/nova-xvpnvncproxy.xml14(th) +msgid "Description" +msgstr "" + +#: ./doc/common/section_cli_nova_quotas.xml36(systemitem) +msgid "cores" +msgstr "" + +#: ./doc/common/section_cli_nova_quotas.xml40(para) +msgid "Number of instance cores (VCPUs) allowed per tenant." +msgstr "" + +#: ./doc/common/section_cli_nova_quotas.xml48(systemitem) +msgid "fixed-ips" +msgstr "" + +#: ./doc/common/section_cli_nova_quotas.xml52(para) +msgid "" +"Number of fixed IP addresses allowed per tenant. This number must be equal " +"to or greater than the number of allowed instances." +msgstr "" + +#: ./doc/common/section_cli_nova_quotas.xml62(systemitem) +msgid "floating-ips" +msgstr "" + +#: ./doc/common/section_cli_nova_quotas.xml66(para) +msgid "Number of floating IP addresses allowed per tenant." +msgstr "" + +#: ./doc/common/section_cli_nova_quotas.xml74(systemitem) +msgid "injected-file-content-bytes" +msgstr "" + +#: ./doc/common/section_cli_nova_quotas.xml78(para) +msgid "Number of content bytes allowed per injected file." +msgstr "" + +#: ./doc/common/section_cli_nova_quotas.xml86(systemitem) +msgid "injected-file-path-bytes" +msgstr "" + +#: ./doc/common/section_cli_nova_quotas.xml90(para) +msgid "Number of bytes allowed per injected file path." +msgstr "" + +#: ./doc/common/section_cli_nova_quotas.xml98(systemitem) +msgid "injected-files" +msgstr "" + +#: ./doc/common/section_cli_nova_quotas.xml102(para) +msgid "Number of injected files allowed per tenant." +msgstr "" + +#: ./doc/common/section_cli_nova_quotas.xml111(systemitem) +msgid "instances" +msgstr "" + +#: ./doc/common/section_cli_nova_quotas.xml115(para) +msgid "Number of instances allowed per tenant." +msgstr "" + +#: ./doc/common/section_cli_nova_quotas.xml123(systemitem) +msgid "key-pairs" +msgstr "" + +#: ./doc/common/section_cli_nova_quotas.xml127(para) +msgid "Number of key pairs allowed per user." +msgstr "" + +#: ./doc/common/section_cli_nova_quotas.xml135(systemitem) +msgid "metadata-items" +msgstr "" + +#: ./doc/common/section_cli_nova_quotas.xml139(para) +msgid "Number of metadata items allowed per instance." +msgstr "" + +#: ./doc/common/section_cli_nova_quotas.xml147(systemitem) +msgid "ram" +msgstr "" + +#: ./doc/common/section_cli_nova_quotas.xml151(para) +msgid "Megabytes of instance ram allowed per tenant." +msgstr "" + +#: ./doc/common/section_cli_nova_quotas.xml159(systemitem) +msgid "security-groups" +msgstr "" + +#: ./doc/common/section_cli_nova_quotas.xml163(para) +msgid "Number of security groups per tenant." +msgstr "" + +#: ./doc/common/section_cli_nova_quotas.xml171(systemitem) +msgid "security-group-rules" +msgstr "" + +#: ./doc/common/section_cli_nova_quotas.xml175(para) +msgid "Number of rules per security group." +msgstr "" + +#: ./doc/common/section_cli_nova_quotas.xml184(title) +msgid "View and update Compute quotas for a tenant (project)" +msgstr "" + +#: ./doc/common/section_cli_nova_quotas.xml186(title) +msgid "To view and update default quota values" +msgstr "" + +#: ./doc/common/section_cli_nova_quotas.xml188(para) +msgid "List all default quotas for all tenants, as follows:" +msgstr "" + +#: ./doc/common/section_cli_nova_quotas.xml211(para) +msgid "Update a default value for a new tenant, as follows:" +msgstr "" + +#: ./doc/common/section_cli_nova_quotas.xml213(replaceable) +msgid "key" +msgstr "" + +#: ./doc/common/section_cli_nova_quotas.xml213(replaceable) +msgid "value" +msgstr "" + +#: ./doc/common/section_cli_nova_quotas.xml220(title) +msgid "To view quota values for an existing tenant (project)" +msgstr "" + +#: ./doc/common/section_cli_nova_quotas.xml221(para) +msgid "Place the tenant ID in a usable variable, as follows:" +msgstr "" + +#: ./doc/common/section_cli_nova_quotas.xml222(replaceable) +#: ./doc/common/section_cli_nova_quotas.xml251(replaceable) +#: ./doc/common/section_cli_nova_quotas.xml293(replaceable) +msgid "tenantName" +msgstr "" + +#: ./doc/common/section_cli_nova_quotas.xml225(para) +msgid "List the currently set quota values for a tenant, as follows:" +msgstr "" + +#: ./doc/common/section_cli_nova_quotas.xml249(title) +msgid "To update quota values for an existing tenant (project)" +msgstr "" + +#: ./doc/common/section_cli_nova_quotas.xml250(para) +msgid "Obtain the tenant ID, as follows:" +msgstr "" + +#: ./doc/common/section_cli_nova_quotas.xml254(para) +#: ./doc/common/section_cli_nova_quotas.xml329(para) +msgid "Update a particular quota value, as follows:" +msgstr "" + +#: ./doc/common/section_cli_nova_quotas.xml255(replaceable) +#: ./doc/common/section_cli_nova_quotas.xml330(replaceable) +msgid "quotaName" +msgstr "" + +#: ./doc/common/section_cli_nova_quotas.xml255(replaceable) +#: ./doc/common/section_cli_nova_quotas.xml330(replaceable) +msgid "quotaValue" +msgstr "" + +#: ./doc/common/section_cli_nova_quotas.xml255(replaceable) +msgid "tenantID" +msgstr "" + +#: ./doc/common/section_cli_nova_quotas.xml277(para) +#: ./doc/common/section_cli_nova_quotas.xml352(para) +msgid "To view a list of options for the command, run:" +msgstr "" + +#: ./doc/common/section_cli_nova_quotas.xml285(title) +msgid "View and update Compute quotas for a tenant user" +msgstr "" + +#: ./doc/common/section_cli_nova_quotas.xml287(title) +msgid "To view quota values for a tenant user" +msgstr "" + +#: ./doc/common/section_cli_nova_quotas.xml288(para) +#: ./doc/common/section_cli_nova_quotas.xml322(para) +msgid "Place the user ID in a usable variable, as follows:" +msgstr "" + +#: ./doc/common/section_cli_nova_quotas.xml289(replaceable) +#: ./doc/common/section_cli_nova_quotas.xml323(replaceable) +#: ./doc/common/section_cli_nova_quotas.xml326(replaceable) +msgid "userName" +msgstr "" + +#: ./doc/common/section_cli_nova_quotas.xml292(para) +#: ./doc/common/section_cli_nova_quotas.xml325(para) +msgid "Place the user's tenant ID in a usable variable, as follows:" +msgstr "" + +#: ./doc/common/section_cli_nova_quotas.xml296(para) +msgid "List the currently set quota values for a tenant user, as follows:" +msgstr "" + +#: ./doc/common/section_cli_nova_quotas.xml321(title) +msgid "To update quota values for a tenant user" +msgstr "" + +#. ... Old module003-ch001-intro-objstore edited, renamed, and stored in +#. doc/common for use by both Cloud Admin and Operator Training Guides... +#: ./doc/common/section_objectstorage-intro.xml8(title) +#: ./doc/common/section_about-object-storage.xml7(title) +msgid "Introduction to Object Storage" +msgstr "" + +#: ./doc/common/section_objectstorage-intro.xml9(para) +msgid "" +"OpenStack Object Storage (code-named Swift) is open source software for " +"creating redundant, scalable data storage using clusters of standardized " +"servers to store petabytes of accessible data. It is a long-term storage " +"system for large amounts of static data that can be retrieved, leveraged, " +"and updated. Object Storage uses a distributed architecture with no central " +"point of control, providing greater scalability, redundancy, and permanence." +" Objects are written to multiple hardware devices, with the OpenStack " +"software responsible for ensuring data replication and integrity across the " +"cluster. Storage clusters scale horizontally by adding new nodes. Should a " +"node fail, OpenStack works to replicate its content from other active nodes." +" Because OpenStack uses software logic to ensure data replication and " +"distribution across different devices, inexpensive commodity hard drives and" +" servers can be used in lieu of more expensive equipment." +msgstr "" + +#: ./doc/common/section_objectstorage-intro.xml20(para) +msgid "" +"Object Storage is ideal for cost effective, scale-out storage. It provides a" +" fully distributed, API-accessible storage platform that can be integrated " +"directly into applications or used for backup, archiving, and data " +"retention." +msgstr "" + +#: ./doc/common/section_cli_keystone_commands.xml11(title) +msgid "keystone commands" +msgstr "" + +#: ./doc/common/section_cli_keystone_commands.xml12(para) +msgid "" +"The keystone client is the command-line interface (CLI) for the OpenStack " +"Identity API and its extensions." +msgstr "" + +#: ./doc/common/section_cli_keystone_commands.xml20(title) +msgid "keystone usage" +msgstr "" + +#: ./doc/common/section_cli_keystone_commands.xml35(title) +msgid "keystone positional arguments" +msgstr "" + +#: ./doc/common/section_cli_keystone_commands.xml86(title) +msgid "keystone optional arguments" +msgstr "" + +#: ./doc/common/section_cli_keystone_commands.xml139(title) +msgid "keystone bootstrap command" +msgstr "" + +#: ./doc/common/section_cli_keystone_commands.xml160(title) +msgid "keystone catalog command" +msgstr "" + +#: ./doc/common/section_cli_keystone_commands.xml172(title) +msgid "keystone discover command" +msgstr "" + +#: ./doc/common/section_cli_keystone_commands.xml186(title) +msgid "keystone ec2-credentials-create command" +msgstr "" + +#: ./doc/common/section_cli_keystone_commands.xml200(title) +msgid "keystone ec2-credentials-delete command" +msgstr "" + +#: ./doc/common/section_cli_keystone_commands.xml214(title) +msgid "keystone ec2-credentials-get command" +msgstr "" + +#: ./doc/common/section_cli_keystone_commands.xml228(title) +msgid "keystone ec2-credentials-list command" +msgstr "" + +#: ./doc/common/section_cli_keystone_commands.xml239(title) +msgid "keystone endpoint-create command" +msgstr "" + +#: ./doc/common/section_cli_keystone_commands.xml262(title) +msgid "keystone endpoint-delete command" +msgstr "" + +#: ./doc/common/section_cli_keystone_commands.xml273(title) +msgid "keystone endpoint-get command" +msgstr "" + +#: ./doc/common/section_cli_keystone_commands.xml292(title) +msgid "keystone endpoint-list command" +msgstr "" + +#: ./doc/common/section_cli_keystone_commands.xml300(title) +msgid "keystone password-update command" +msgstr "" + +#: ./doc/common/section_cli_keystone_commands.xml316(title) +msgid "keystone role-create command" +msgstr "" + +#: ./doc/common/section_cli_keystone_commands.xml327(title) +msgid "keystone role-delete command" +msgstr "" + +#: ./doc/common/section_cli_keystone_commands.xml338(title) +msgid "keystone role-get command" +msgstr "" + +#: ./doc/common/section_cli_keystone_commands.xml349(title) +msgid "keystone role-list command" +msgstr "" + +#: ./doc/common/section_cli_keystone_commands.xml357(title) +msgid "keystone service-create command" +msgstr "" + +#: ./doc/common/section_cli_keystone_commands.xml374(title) +msgid "keystone service-delete command" +msgstr "" + +#: ./doc/common/section_cli_keystone_commands.xml385(title) +msgid "keystone service-get command" +msgstr "" + +#: ./doc/common/section_cli_keystone_commands.xml396(title) +msgid "keystone service-list command" +msgstr "" + +#: ./doc/common/section_cli_keystone_commands.xml404(title) +msgid "keystone tenant-create command" +msgstr "" + +#: ./doc/common/section_cli_keystone_commands.xml421(title) +msgid "keystone tenant-delete command" +msgstr "" + +#: ./doc/common/section_cli_keystone_commands.xml432(title) +msgid "keystone tenant-get command" +msgstr "" + +#: ./doc/common/section_cli_keystone_commands.xml443(title) +msgid "keystone tenant-list command" +msgstr "" + +#: ./doc/common/section_cli_keystone_commands.xml451(title) +msgid "keystone tenant-update command" +msgstr "" + +#: ./doc/common/section_cli_keystone_commands.xml470(title) +msgid "keystone token-get command" +msgstr "" + +#: ./doc/common/section_cli_keystone_commands.xml481(title) +msgid "keystone user-create command" +msgstr "" + +#: ./doc/common/section_cli_keystone_commands.xml500(title) +msgid "keystone user-delete command" +msgstr "" + +#: ./doc/common/section_cli_keystone_commands.xml511(title) +msgid "keystone user-get command" +msgstr "" + +#: ./doc/common/section_cli_keystone_commands.xml522(title) +msgid "keystone user-list command" +msgstr "" + +#: ./doc/common/section_cli_keystone_commands.xml534(title) +msgid "keystone user-password-update command" +msgstr "" + +#: ./doc/common/section_cli_keystone_commands.xml546(title) +msgid "keystone user-role-add command" +msgstr "" + +#: ./doc/common/section_cli_keystone_commands.xml562(title) +msgid "keystone user-role-list command" +msgstr "" + +#: ./doc/common/section_cli_keystone_commands.xml576(title) +msgid "keystone user-role-remove command" +msgstr "" + +#: ./doc/common/section_cli_keystone_commands.xml593(title) +msgid "keystone user-update command" +msgstr "" + +#: ./doc/common/section_cli_keystone_credentials.xml6(title) +msgid "Set up credentials for the keystone client" +msgstr "" + +#: ./doc/common/section_cli_keystone_credentials.xml7(para) +msgid "" +"You can configure the python-keystoneclient with admin " +"credentials with either an authentication token or a user name and password." +msgstr "" + +#: ./doc/common/section_cli_keystone_credentials.xml12(title) +msgid "To configure the keystone client with an authentication token" +msgstr "" + +#: ./doc/common/section_cli_keystone_credentials.xml15(para) +msgid "" +"Export your keystone endpoint to the OS_SERVICE_ENDPOINT " +"environment variable:" +msgstr "" + +#: ./doc/common/section_cli_keystone_credentials.xml21(para) +msgid "" +"Export the administrator service token to the " +"OS_SERVICE_TOKEN environment variable:" +msgstr "" + +#: ./doc/common/section_cli_keystone_credentials.xml26(para) +#: ./doc/common/section_cli_keystone_credentials.xml80(para) +msgid "" +"Alternatively, you can specify these parameters on any keystone client " +"command:" +msgstr "" + +#: ./doc/common/section_cli_keystone_credentials.xml30(para) +msgid "" +"--os-endpoint " +"SERVICE_ENDPOINT. An endpoint to use " +"instead of the one in the service catalog. Defaults to " +"env[OS_SERVICE_ENDPOINT]." +msgstr "" + +#: ./doc/common/section_cli_keystone_credentials.xml39(para) +msgid "" +"--os-token SERVICE_TOKEN. " +"An existing token to use instead of the one generated by authentication. " +"Defaults to env[OS_SERVICE_TOKEN]." +msgstr "" + +#: ./doc/common/section_cli_keystone_credentials.xml52(title) +msgid "To configure the keystone client with a user name and password" +msgstr "" + +#: ./doc/common/section_cli_keystone_credentials.xml55(para) +msgid "" +"Export the administrator user name to the OS_USERNAME " +"environment variable:" +msgstr "" + +#: ./doc/common/section_cli_keystone_credentials.xml61(para) +msgid "" +"Export the administrator password to the OS_PASSWORD " +"environment variable:" +msgstr "" + +#: ./doc/common/section_cli_keystone_credentials.xml67(para) +msgid "" +"Export the tenant name to the OS_TENANT_NAME environment " +"variable:" +msgstr "" + +#: ./doc/common/section_cli_keystone_credentials.xml73(para) +msgid "" +"Export the URL of the keystone auth server, for example http://localhost:5000/v2.0', to " +"the OS_AUTH_URL environment variable:" +msgstr "" + +#: ./doc/common/section_cli_keystone_credentials.xml84(para) +msgid "" +"--os-username OS_USERNAME. " +"Name used for authentication with the Identity Service. Defaults to " +"env[OS_USERNAME]." +msgstr "" + +#: ./doc/common/section_cli_keystone_credentials.xml92(para) +msgid "" +"--os-password OS_PASSWORD. " +"Password used for authentication with the Identity Service. Defaults to " +"env[OS_PASSWORD]." +msgstr "" + +#: ./doc/common/section_cli_keystone_credentials.xml100(para) +msgid "" +"--os-tenant_name " +"OS_TENANT_NAME. Tenant for which to " +"request authentication. Defaults to env[OS_TENANT_NAME]." +msgstr "" + +#: ./doc/common/section_cli_keystone_credentials.xml108(para) +msgid "" +"--os-auth_url OS_AUTH_URL. The" +" Identity Service endpoint to use for authentication. Defaults to " +"env[OS_AUTH_URL]." +msgstr "" + +#: ./doc/common/section_using-vnc-console.xml6(title) +msgid "Use the VNC console" +msgstr "" + +#: ./doc/common/section_using-vnc-console.xml7(para) +msgid "" +"To interact through the VNC console, you can use a VNC client directly, a " +"special Java client, or a web browser. For information about how to " +"configure the console, see ." +msgstr "" + +#: ./doc/common/section_using-vnc-console.xml15(title) +msgid "Get an access URL" +msgstr "" + +#: ./doc/common/section_using-vnc-console.xml16(para) +msgid "" +"The Compute Service enables you to create access_urls through the os-" +"consoles extension. Support for accessing this URL is provided by the nova " +"client:" +msgstr "" + +#: ./doc/common/section_using-vnc-console.xml19(replaceable) +#: ./doc/common/section_using-vnc-console.xml25(replaceable) +#: ./doc/common/section_using-vnc-console.xml52(replaceable) +#: ./doc/common/section_using-vnc-console.xml65(replaceable) +msgid "[server_id]" +msgstr "" + +#: ./doc/common/section_using-vnc-console.xml19(replaceable) +msgid "[novnc|xvpvnc]" +msgstr "" + +#: ./doc/common/section_using-vnc-console.xml20(para) +msgid "" +"Specify 'novnc' to get a URL suitable for pasting into a " +"web browser." +msgstr "" + +#: ./doc/common/section_using-vnc-console.xml22(para) +msgid "" +"Specify 'xvpvnc' for a URL suitable for pasting into the " +"Java client." +msgstr "" + +#: ./doc/common/section_using-vnc-console.xml24(para) +msgid "To request a web browser URL:" +msgstr "" + +#: ./doc/common/section_using-vnc-console.xml28(title) +msgid "Access a VNC console with a Java client" +msgstr "" + +#: ./doc/common/section_using-vnc-console.xml29(para) +msgid "" +"To enable support for the OpenStack Java VNC client in compute, run the " +"nova-xvpvncproxy service." +msgstr "" + +#: ./doc/common/section_using-vnc-console.xml34(para) +msgid "" +"xvpvncproxy_port=[port] - port" +" to bind (defaults to 6081)" +msgstr "" + +#: ./doc/common/section_using-vnc-console.xml38(para) +msgid "" +"xvpvncproxy_host=[host] - host" +" to bind (defaults to 0.0.0.0)" +msgstr "" + +#: ./doc/common/section_using-vnc-console.xml42(para) +msgid "" +"As a client, you need a special Java client, which is a slightly modified " +"version of TightVNC that supports our token auth:" +msgstr "" + +#: ./doc/common/section_using-vnc-console.xml48(para) +msgid "" +"To create a session, request an access URL by using . Then, " +"run the client as follows." +msgstr "" + +#: ./doc/common/section_using-vnc-console.xml51(para) +msgid "To get an access URL:" +msgstr "" + +#: ./doc/common/section_using-vnc-console.xml53(para) +msgid "To run the client:" +msgstr "" + +#: ./doc/common/section_using-vnc-console.xml54(replaceable) +msgid "[access_url]" +msgstr "" + +#: ./doc/common/section_using-vnc-console.xml59(title) +msgid "Access a VNC console with a web browser" +msgstr "" + +#: ./doc/common/section_using-vnc-console.xml61(para) +msgid "" +"Retrieving an access_url for a web browser is similar to the flow for the " +"Java client." +msgstr "" + +#: ./doc/common/section_using-vnc-console.xml63(para) +msgid "To get the access URL, run the following command:" +msgstr "" + +#: ./doc/common/section_using-vnc-console.xml66(para) +msgid "Paste the URL into your web browser." +msgstr "" + +#: ./doc/common/section_using-vnc-console.xml68(para) +msgid "" +"Additionally, you can use the OpenStack dashboard, known as horizon, to " +"access browser-based VNC consoles for instances." +msgstr "" + +#: ./doc/common/section_objectstorage_tenant-specific-image-storage.xml6(title) +msgid "Configure tenant-specific image locations with Object Storage" +msgstr "" + +#: ./doc/common/section_objectstorage_tenant-specific-image-storage.xml14(para) +msgid "The tenant who owns the image" +msgstr "" + +#: ./doc/common/section_objectstorage_tenant-specific-image-storage.xml17(para) +msgid "" +"Tenants that are defined in and " +"that have admin-level accounts" +msgstr "" + +#: ./doc/common/section_objectstorage_tenant-specific-image-storage.xml8(para) +msgid "" +"For some deployers, it is not ideal to store all images in one place to " +"enable all tenants and users to access them. You can configure the Image " +"Service to store image data in tenant-specific image locations. Then, only " +"the following tenants can use the Image Service to access the created " +"image:" +msgstr "" + +#: ./doc/common/section_objectstorage_tenant-specific-image-storage.xml23(title) +msgid "To configure tenant-specific image locations" +msgstr "" + +#: ./doc/common/section_objectstorage_tenant-specific-image-storage.xml25(para) +msgid "" +"Configure swift as your in the glance-api.conf file." +msgstr "" + +#: ./doc/common/section_objectstorage_tenant-specific-image-storage.xml33(para) +msgid "" +". Set to True to" +" enable tenant-specific storage locations. Default is " +"False." +msgstr "" + +#: ./doc/common/section_objectstorage_tenant-specific-image-storage.xml39(para) +msgid "" +". Specify a list of tenant IDs " +"that can grant read and write access to all Object Storage containers that " +"are created by the Image Service." +msgstr "" + +#: ./doc/common/section_objectstorage_tenant-specific-image-storage.xml30(para) +msgid "" +"Set these configuration options in the glance-api.conf " +"file: " +msgstr "" + +#: ./doc/common/section_objectstorage_tenant-specific-image-storage.xml48(para) +msgid "" +"With this configuration, images are stored in an Object Storage service " +"(swift) endpoint that is pulled from the service catalog for the " +"authenticated user." +msgstr "" + +#: ./doc/common/section_cli_ceilometer_commands.xml11(title) +msgid "ceilometer commands" +msgstr "" + +#: ./doc/common/section_cli_ceilometer_commands.xml12(para) +msgid "" +"The ceilometer client is the command-line interface (CLI) for the OpenStack " +"Telemetry API and its extensions." +msgstr "" + +#: ./doc/common/section_cli_ceilometer_commands.xml20(title) +msgid "ceilometer usage" +msgstr "" + +#: ./doc/common/section_cli_ceilometer_commands.xml36(title) +msgid "ceilometer positional arguments" +msgstr "" + +#: ./doc/common/section_cli_ceilometer_commands.xml74(title) +msgid "ceilometer optional arguments" +msgstr "" + +#: ./doc/common/section_cli_ceilometer_commands.xml121(title) +msgid "ceilometer alarm-combination-create command" +msgstr "" + +#: ./doc/common/section_cli_ceilometer_commands.xml171(title) +msgid "ceilometer alarm-combination-update command" +msgstr "" + +#: ./doc/common/section_cli_ceilometer_commands.xml222(title) +msgid "ceilometer alarm-delete command" +msgstr "" + +#: ./doc/common/section_cli_ceilometer_commands.xml234(title) +msgid "ceilometer alarm-history command" +msgstr "" + +#: ./doc/common/section_cli_ceilometer_commands.xml250(title) +msgid "ceilometer alarm-list command" +msgstr "" + +#: ./doc/common/section_cli_ceilometer_commands.xml264(title) +msgid "ceilometer alarm-show command" +msgstr "" + +#: ./doc/common/section_cli_ceilometer_commands.xml276(title) +msgid "ceilometer alarm-state-get command" +msgstr "" + +#: ./doc/common/section_cli_ceilometer_commands.xml288(title) +msgid "ceilometer alarm-state-set command" +msgstr "" + +#: ./doc/common/section_cli_ceilometer_commands.xml302(title) +msgid "ceilometer alarm-threshold-create command" +msgstr "" + +#: ./doc/common/section_cli_ceilometer_commands.xml369(title) +msgid "ceilometer alarm-threshold-update command" +msgstr "" + +#: ./doc/common/section_cli_ceilometer_commands.xml438(title) +msgid "ceilometer alarm-update command" +msgstr "" + +#: ./doc/common/section_cli_ceilometer_commands.xml506(title) +msgid "ceilometer event-list command" +msgstr "" + +#: ./doc/common/section_cli_ceilometer_commands.xml520(title) +msgid "ceilometer event-show command" +msgstr "" + +#: ./doc/common/section_cli_ceilometer_commands.xml532(title) +msgid "ceilometer event-type-list command" +msgstr "" + +#: ./doc/common/section_cli_ceilometer_commands.xml540(title) +msgid "ceilometer meter-list command" +msgstr "" + +#: ./doc/common/section_cli_ceilometer_commands.xml554(title) +msgid "ceilometer resource-list command" +msgstr "" + +#: ./doc/common/section_cli_ceilometer_commands.xml568(title) +msgid "ceilometer resource-show command" +msgstr "" + +#: ./doc/common/section_cli_ceilometer_commands.xml580(title) +msgid "ceilometer sample-create command" +msgstr "" + +#: ./doc/common/section_cli_ceilometer_commands.xml615(title) +msgid "ceilometer sample-list command" +msgstr "" + +#: ./doc/common/section_cli_ceilometer_commands.xml633(title) +msgid "ceilometer statistics command" +msgstr "" + +#: ./doc/common/section_cli_ceilometer_commands.xml651(title) +msgid "ceilometer trait-description-list command" +msgstr "" + +#: ./doc/common/section_cli_ceilometer_commands.xml664(title) +msgid "ceilometer trait-list command" +msgstr "" + +#: ./doc/common/app_command_reference.xml17(title) +msgid "Command reference" +msgstr "" + +#: ./doc/common/section_cli_keystone_services.xml7(title) +msgid "Create and manage services and service users" +msgstr "" + +#: ./doc/common/section_cli_keystone_services.xml8(para) +msgid "The Identity Service enables you to define services, as follows:" +msgstr "" + +#: ./doc/common/section_cli_keystone_services.xml12(para) +msgid "" +"Service catalog template. The Identity Service acts as a service catalog of " +"endpoints for other OpenStack services. The " +"etc/default_catalog.templates template file defines the " +"endpoints for services. When the Identity Service uses a template file back " +"end, any changes that are made to the endpoints are cached. These changes do" +" not persist when you restart the service or reboot the machine." +msgstr "" + +#: ./doc/common/section_cli_keystone_services.xml23(para) +msgid "" +"A SQL back end for the catalog service. When the Identity Service is online," +" you must add the services to the catalog. When you deploy a system for " +"production, use the SQL back end." +msgstr "" + +#: ./doc/common/section_cli_keystone_services.xml29(para) +msgid "" +"The auth_token middleware supports the use of either a " +"shared secret or users for each service." +msgstr "" + +#: ./doc/common/section_cli_keystone_services.xml32(para) +msgid "" +"To authenticate users against the Identity Service, you must create a " +"service user for each OpenStack service. For example, create a service user " +"for the Compute, Block Storage, and Networking services." +msgstr "" + +#: ./doc/common/section_cli_keystone_services.xml36(para) +msgid "" +"To configure the OpenStack services with service users, create a project for" +" all services and create users for each service. Assign the admin role to " +"each service user and project pair. This role enables users to validate " +"tokens and authenticate and authorize other user requests." +msgstr "" + +#: ./doc/common/section_cli_keystone_services.xml42(title) +msgid "Create a service" +msgstr "" + +#: ./doc/common/section_cli_keystone_services.xml45(para) +msgid "List the available services:" +msgstr "" + +#: ./doc/common/section_cli_keystone_services.xml59(para) +msgid "To create a service, run this command:" +msgstr "" + +#: ./doc/common/section_cli_keystone_services.xml60(replaceable) +msgid "service_name" +msgstr "" + +#: ./doc/common/section_cli_keystone_services.xml60(replaceable) +msgid "service_type" +msgstr "" + +#: ./doc/common/section_cli_keystone_services.xml60(replaceable) +msgid "service_description" +msgstr "" + +#: ./doc/common/section_cli_keystone_services.xml61(para) +msgid "The arguments are:" +msgstr "" + +#: ./doc/common/section_cli_keystone_services.xml64(para) +msgid "" +"service_name. The unique name of the" +" new service." +msgstr "" + +#: ./doc/common/section_cli_keystone_services.xml68(para) +msgid "" +"service_type. The service type, such" +" as identity, compute, network, " +"image, object-store or any other service " +"identifier string." +msgstr "" + +#: ./doc/common/section_cli_keystone_services.xml78(para) +msgid "" +"service_description. The description" +" of the service." +msgstr "" + +#: ./doc/common/section_cli_keystone_services.xml82(para) +msgid "" +"For example, to create a swift service of type object-store, run this command:" +msgstr "" + +#: ./doc/common/section_cli_keystone_services.xml97(para) +msgid "To get details for a service, run this command:" +msgstr "" + +#: ./doc/common/section_cli_keystone_services.xml99(replaceable) +msgid "service_ID" +msgstr "" + +#: ./doc/common/section_cli_keystone_services.xml114(title) +msgid "Create service users" +msgstr "" + +#: ./doc/common/section_cli_keystone_services.xml117(para) +msgid "" +"Create a project for the service users. Typically, this project is named " +"service, but choose any name you like:" +msgstr "" + +#: ./doc/common/section_cli_keystone_services.xml122(para) +msgid "The output shows the ID for the project." +msgstr "" + +#: ./doc/common/section_cli_keystone_services.xml123(para) +msgid "" +"Make a note of this ID. You need it to create service users and assign " +"roles." +msgstr "" + +#: ./doc/common/section_cli_keystone_services.xml135(para) +msgid "Create service users for the relevant services for your deployment." +msgstr "" + +#: ./doc/common/section_cli_keystone_services.xml139(para) +msgid "" +"To assign the admin role to the service user-project pairs, run this command" +" to get the ID of the admin role:" +msgstr "" + +#: ./doc/common/section_cli_keystone_services.xml155(para) +msgid "Assign the admin role to the user-project pair:" +msgstr "" + +#: ./doc/common/section_cli_keystone_services.xml157(replaceable) +msgid "SERVICE_USER_ID" +msgstr "" + +#: ./doc/common/section_cli_keystone_services.xml157(replaceable) +msgid "ADMIN_ROLE_ID" +msgstr "" + +#: ./doc/common/section_cli_keystone_services.xml157(replaceable) +msgid "SERVICE_PROJECT_ID" +msgstr "" + +#: ./doc/common/section_cli_keystone_services.xml162(title) +msgid "Delete a service" +msgstr "" + +#: ./doc/common/section_cli_keystone_services.xml163(para) +msgid "To delete a specified service, specify its ID:" +msgstr "" + +#: ./doc/common/section_cli_keystone_services.xml164(replaceable) +msgid "SERVICE_ID" +msgstr "" + +#: ./doc/common/section_cli_nova_boot_from_volume.xml6(title) +msgid "Launch an instance from a volume" +msgstr "" + +#: ./doc/common/section_cli_nova_boot_from_volume.xml7(para) +msgid "" +"After you create a bootable volume, you can launch an instance from that " +"volume." +msgstr "" + +#: ./doc/common/section_cli_nova_boot_from_volume.xml9(para) +msgid "" +"Optionally, to configure your volume, see the OpenStack Configuration " +"Reference." +msgstr "" + +#: ./doc/common/section_cli_nova_boot_from_volume.xml15(para) +msgid "" +"For a list of images to choose from to create a bootable volume, run this " +"command:" +msgstr "" + +#: ./doc/common/section_cli_nova_boot_from_volume.xml27(para) +msgid "" +"To create a bootable volume from an image, include the image ID in the " +"command:" +msgstr "" + +#: ./doc/common/section_cli_nova_boot_from_volume.xml48(para) +msgid "" +"Before the volume builds, its bootable state is " +"false." +msgstr "" + +#: ./doc/common/section_cli_nova_boot_from_volume.xml52(para) +msgid "To list volumes, run the following command:" +msgstr "" + +#: ./doc/common/section_cli_nova_boot_from_volume.xml59(para) +msgid "" +"Note that the bootable state is now " +"true. Copy the value in the ID field " +"for your volume." +msgstr "" + +#: ./doc/common/section_cli_nova_boot_from_volume.xml64(para) +msgid "" +"To launch an instance, include the " +"--block_device_mapping parameter:" +msgstr "" + +#: ./doc/common/section_cli_nova_boot_from_volume.xml67(replaceable) +#: ./doc/common/section_cli_nova_boot_from_volume.xml80(replaceable) +msgid "FLAVOR" +msgstr "" + +#: ./doc/common/section_cli_nova_boot_from_volume.xml67(replaceable) +msgid "DEVNAME" +msgstr "" + +#: ./doc/common/section_cli_nova_boot_from_volume.xml67(replaceable) +msgid "ID" +msgstr "" + +#: ./doc/common/section_cli_nova_boot_from_volume.xml67(replaceable) +msgid "TYPE" +msgstr "" + +#: ./doc/common/section_cli_nova_boot_from_volume.xml67(replaceable) +msgid "DELETE_ON_TERMINATE" +msgstr "" + +#: ./doc/common/section_cli_nova_boot_from_volume.xml68(para) +msgid "The command arguments are:" +msgstr "" + +#: ./doc/common/section_cli_nova_boot_from_volume.xml72(th) +msgid "Parameter" +msgstr "" + +#: ./doc/common/section_cli_nova_boot_from_volume.xml79(parameter) +msgid "--flavor" +msgstr "" + +#: ./doc/common/section_cli_nova_boot_from_volume.xml83(para) +msgid "The flavor ID." +msgstr "" + +#: ./doc/common/section_cli_nova_boot_from_volume.xml88(para) +msgid "" +"--block_device_mappingDEVNAME=ID:type:size:delete-on-terminate" +msgstr "" + +#: ./doc/common/section_cli_nova_boot_from_volume.xml94(para) +msgid "" +"DEVNAME. A device name where the volume is " +"attached in the system at " +"/dev/dev_name. This value is" +" typically vda." +msgstr "" + +#: ./doc/common/section_cli_nova_boot_from_volume.xml101(para) +msgid "" +"ID. The ID of the volume to boot from, as shown " +"in the output of ." +msgstr "" + +#: ./doc/common/section_cli_nova_boot_from_volume.xml106(para) +msgid "" +"type. Either snap or any other" +" value, including a blank string. snap means that the " +"volume was created from a snapshot." +msgstr "" + +#: ./doc/common/section_cli_nova_boot_from_volume.xml113(para) +msgid "" +"size. The size of the volume, in GBs. It is safe " +"to leave this blank and have the Compute service infer the size." +msgstr "" + +#: ./doc/common/section_cli_nova_boot_from_volume.xml119(para) +msgid "" +"delete-on-terminate. Boolean. Indicates whether " +"the volume is deleted when the instance is deleted. You can specify:" +msgstr "" + +#: ./doc/common/section_cli_nova_boot_from_volume.xml125(para) +msgid "True or 1" +msgstr "" + +#: ./doc/common/section_cli_nova_boot_from_volume.xml130(para) +msgid "False or 0" +msgstr "" + +#: ./doc/common/section_cli_nova_boot_from_volume.xml143(para) +msgid "The name for the server." +msgstr "" + +#: ./doc/common/section_cli_nova_boot_from_volume.xml148(para) +msgid "" +"You can also attach a swap disk on boot with the " +"--swap flag, or you can attach an ephemeral disk on " +"boot with the --ephemeral flag." +msgstr "" + +#: ./doc/common/section_cli_nova_boot_from_volume.xml152(para) +msgid "" +"For example, you might enter the following command to boot from a volume. " +"The volume is not deleted when the instance is terminated:" +msgstr "" + +#: ./doc/common/section_cli_nova_boot_from_volume.xml187(para) +msgid "Now when you list volumes, the volume is attached to a server:" +msgstr "" + +#: ./doc/common/section_cli_nova_images.xml6(title) +msgid "Manage images with the nova client" +msgstr "" + +#: ./doc/common/section_cli_nova_images.xml16(title) +msgid "To create an image" +msgstr "" + +#: ./doc/common/section_cli_nova_images.xml19(para) +msgid "" +"For more information, see the Taking Snapshots in the " +"OpenStack Operations Guide." +msgstr "" + +#: ./doc/common/section_cli_nova_images.xml86(title) +msgid "To launch an instance from your image" +msgstr "" + +#: ./doc/common/section_keystone-external-auth.xml7(title) +msgid "External authentication with the Identity Service" +msgstr "" + +#: ./doc/common/section_keystone-external-auth.xml9(para) +msgid "" +"When the Identity Service runs in apache-httpd, you can " +"use external authentication methods that differ from the authentication " +"provided by the identity store back-end. For example, you can use an SQL " +"identity back-end together with X.509 authentication, Kerberos, and so on " +"instead of using the user name and password combination." +msgstr "" + +#: ./doc/common/section_keystone-external-auth.xml16(title) +msgid "Use HTTPD authentication" +msgstr "" + +#: ./doc/common/section_keystone-external-auth.xml17(para) +msgid "" +"Web servers, like Apache HTTP, support many methods of authentication. The " +"Identity Service can allow the web server to perform the authentication. The" +" web server then passes the authenticated user to the Identity Service by " +"using the REMOTE_USER environment variable. This user " +"must already exist in the Identity Service back-end so as to get a token " +"from the controller. To use this method, the Identity Service should run on " +"apache-httpd." +msgstr "" + +#: ./doc/common/section_keystone-external-auth.xml28(title) +msgid "Use X.509" +msgstr "" + +#: ./doc/common/section_keystone-external-auth.xml29(para) +msgid "" +"The following Apache configuration snippet authenticates the user based on a" +" valid X.509 certificate from a known CA:" +msgstr "" + +#: ./doc/common/section_getstart_orchestration.xml5(title) +msgid "Orchestration service overview" +msgstr "" + +#: ./doc/common/section_getstart_orchestration.xml6(para) +msgid "" +"The Orchestration service provides a template-based orchestration for " +"describing a cloud application by running OpenStack API calls to generate " +"running cloud applications. The software integrates other core components of" +" OpenStack into a one-file template system. The templates enable you to " +"create most OpenStack resource types, such as instances, floating IPs, " +"volumes, security groups, users, and so on. Also, provides some more " +"advanced functionality, such as instance high availability, instance auto-" +"scaling, and nested stacks. By providing very tight integration with other " +"OpenStack core projects, all OpenStack core projects could receive a larger " +"user base." +msgstr "" + +#: ./doc/common/section_getstart_orchestration.xml17(para) +msgid "" +"The service enables deployers to integrate with the Orchestration service " +"directly or through custom plug-ins." +msgstr "" + +#: ./doc/common/section_getstart_orchestration.xml19(para) +msgid "The Orchestration service consists of the following components:" +msgstr "" + +#: ./doc/common/section_getstart_orchestration.xml23(para) +msgid "" +"heat command-line client. A CLI that communicates with the " +"heat-api to run AWS CloudFormation APIs. End developers could also use the " +"Orchestration REST API directly." +msgstr "" + +#: ./doc/common/section_getstart_orchestration.xml28(para) +msgid "" +"heat-api component. Provides an OpenStack-native REST API that " +"processes API requests by sending them to the heat-engine over RPC." +msgstr "" + +#: ./doc/common/section_getstart_orchestration.xml33(para) +msgid "" +"heat-api-cfn component. Provides an AWS Query API that is " +"compatible with AWS CloudFormation and processes API requests by sending " +"them to the heat-engine over RPC." +msgstr "" + +#: ./doc/common/section_getstart_orchestration.xml39(para) +msgid "" +"heat-engine. Orchestrates the launching of templates and " +"provides events back to the API consumer." +msgstr "" + +#: ./doc/common/section_getstart_networking.xml5(title) +msgid "Networking service overview" +msgstr "" + +#: ./doc/common/section_getstart_networking.xml6(para) +msgid "" +"Provides network-connectivity-as-a-service between interface devices that " +"are managed by other OpenStack services, usually Compute. Enables users to " +"create and attach interfaces to networks. Like many OpenStack services, " +"OpenStack Networking is highly configurable due to its plug-in architecture." +" These plug-ins accommodate different networking equipment and software. " +"Consequently, the architecture and deployment vary dramatically." +msgstr "" + +#: ./doc/common/section_getstart_networking.xml14(para) +msgid "Includes the following components:" +msgstr "" + +#: ./doc/common/section_getstart_networking.xml17(para) +msgid "" +"neutron-server. Accepts and " +"routes API requests to the appropriate OpenStack Networking plug-in for " +"action." +msgstr "" + +#: ./doc/common/section_getstart_networking.xml22(para) +msgid "" +"OpenStack Networking plug-ins and agents. Plugs and unplugs ports, creates " +"networks or subnets, and provides IP addressing. These plug-ins and agents " +"differ depending on the vendor and technologies used in the particular " +"cloud. OpenStack Networking ships with plug-ins and agents for Cisco virtual" +" and physical switches, Nicira NVP product, NEC OpenFlow products, Open " +"vSwitch, Linux bridging, and the Ryu Network Operating System." +msgstr "" + +#: ./doc/common/section_getstart_networking.xml30(para) +msgid "" +"The common agents are L3 (layer 3), DHCP (dynamic host IP addressing), and a" +" plug-in agent." +msgstr "" + +#: ./doc/common/section_getstart_networking.xml34(para) +msgid "" +"Messaging queue. Most OpenStack Networking installations make use of a " +"messaging queue to route information between the neutron-server and various " +"agents as well as a database to store networking state for particular plug-" +"ins." +msgstr "" + +#: ./doc/common/section_getstart_networking.xml40(para) +msgid "" +"OpenStack Networking interacts mainly with OpenStack Compute, where it " +"provides networks and connectivity for its instances." +msgstr "" + +#: ./doc/common/section_user-data.xml6(title) +msgid "Configure instances at boot" +msgstr "" + +#: ./doc/common/section_user-data.xml7(para) +msgid "" +"When you boot instances in an OpenStack cloud, you can use user data or " +"cloud-init to automatically configure instances at boot " +"time. You might want to install some packages, start services, or manage " +"your instance by using a Puppet or Chef server." +msgstr "" + +#: ./doc/common/section_user-data.xml13(title) +msgid "User data" +msgstr "" + +#: ./doc/common/section_user-data.xml14(para) +msgid "" +"User data is the mechanism by which a user can pass information contained in" +" a local file to an instance at launch time. The typical use case is to pass" +" something like a shell script or a configuration file as user data." +msgstr "" + +#: ./doc/common/section_user-data.xml19(para) +msgid "" +"User data is sent using the --user-data " +"/path/to/filename option when calling " +". This example creates a text file and sends its contents as" +" user data to the instance:" +msgstr "" + +#: ./doc/common/section_user-data.xml26(para) +msgid "" +"The instance can get user data by querying the metadata service through " +"either the OpenStack metadata API or the EC2 compatibility API:" +msgstr "" + +#: ./doc/common/section_user-data.xml34(para) +msgid "" +"The Compute service treats user data as a blob. While the previous example " +"uses a text file, user data can be in any format." +msgstr "" + +#: ./doc/common/section_user-data.xml38(para) +msgid "For more information, see ." +msgstr "" + +#: ./doc/common/section_user-data.xml42(package) +msgid "cloud-init" +msgstr "" + +#: ./doc/common/section_user-data.xml43(para) +msgid "" +"To do something useful with the user data, you must configure the virtual " +"machine image to run a service on boot that gets user data from the metadata" +" service and takes some action based on the contents of the data. The " +"cloud-init package does exactly this. This package is " +"compatible with the Compute metadata service and the Compute configuration " +"drive." +msgstr "" + +#: ./doc/common/section_user-data.xml51(para) +msgid "" +"The cloud-init package supports multiple cloud providers." +" You can use the same virtual machine image in different clouds without " +"modification. The cloud-init package is an open source " +"project and the source code is available on Launchpad. It is maintained " +"by Canonical, the company that runs the Ubuntu project. All Ubuntu cloud " +"images come pre-installed with cloud-init. However, " +"cloud-init is not designed to be Ubuntu-specific and has " +"been successfully ported to several other platforms including Fedora." +msgstr "" + +#: ./doc/common/section_user-data.xml66(para) +msgid "" +"Even if you do not use user data to configure instance behavior at boot " +"time, install cloud-init on images that you create " +"because this package provides useful functionality. For example, the " +"cloud-init package enables you to copy the public key to " +"an account (the ubuntu account by default on Ubuntu " +"instances, the ec2-user by default in Fedora instances)." +msgstr "" + +#: ./doc/common/section_user-data.xml75(para) +msgid "" +"If you do not have cloud-init installed, you must " +"manually configure your image to get the public key from the metadata " +"service on boot and copy it to the appropriate account." +msgstr "" + +#: ./doc/common/section_user-data.xml81(title) +msgid "cloud-init supported formats and documentation" +msgstr "" + +#: ./doc/common/section_user-data.xml83(para) +msgid "" +"Look at the cloud-initdoc/userdata.txt file the " +"examples directory and the " +"Ubuntu community " +"documentation for details about how to use cloud-" +"init. Some basic examples are provided here." +msgstr "" + +#: ./doc/common/section_user-data.xml96(para) +msgid "Shell scripts (starts with #!)" +msgstr "" + +#: ./doc/common/section_user-data.xml100(para) +msgid "Cloud config files (starts with #cloud-config)" +msgstr "" + +#: ./doc/common/section_user-data.xml93(para) +msgid "" +"cloud-init supports several different input formats for " +"user data. Two commonly used formats are:" +msgstr "" + +#: ./doc/common/section_user-data.xml106(title) +msgid "Run a shell script on boot" +msgstr "" + +#: ./doc/common/section_user-data.xml107(para) +msgid "" +"Assuming you have cloud-init installed, the simplest way " +"to configure an instance on boot is to pass a shell script as user data. The" +" shell file must begin with #! in order for cloud-init to recognize it as a shell script. This example shows " +"a script that creates a clouduser account:" +msgstr "" + +#: ./doc/common/section_user-data.xml116(para) +msgid "" +"Sending a shell script as user data has a similar effect to writing an " +"/etc/rc.local script: it executes very late in the boot" +" sequence as root." +msgstr "" + +#: ./doc/common/section_user-data.xml121(title) +msgid "Cloud-config format" +msgstr "" + +#: ./doc/common/section_user-data.xml122(para) +msgid "" +"cloud-init supports a YAML-based config format that " +"allows the user to configure a large number of options on a system. User " +"data that begins with #cloud-config will be interpreted " +"by cloud-init as cloud-config format." +msgstr "" + +#: ./doc/common/section_user-data.xml130(title) +msgid "Example: Set the host name" +msgstr "" + +#: ./doc/common/section_user-data.xml131(para) +msgid "" +"This cloud-init user data example sets the hostname and " +"the FQDN, as well as updating /etc/hosts on the " +"instance:" +msgstr "" + +#: ./doc/common/section_user-data.xml143(title) +msgid "Example: Configure instances with Puppet" +msgstr "" + +#: ./doc/common/section_user-data.xml144(para) +msgid "" +"This cloud-init user data example, based on doc/examples" +"/cloud-config-puppet.txt, would configure the instance to contact a " +"Puppet server at puppetmaster.example.org and verify its identity using a " +"certificate. " +msgstr "" + +#: ./doc/common/section_user-data.xml172(title) +msgid "Example: Configure instances with Chef" +msgstr "" + +#: ./doc/common/section_user-data.xml173(para) +msgid "" +"This cloud-init user data example, based on doc/examples" +"/cloud-config/chef.txt and intended for use in an Ubuntu image, adds " +"the Chef apt repository, installs Chef, connects to a Chef server at " +"https://chefserver.example.com:4000, and installs " +"Apache:" +msgstr "" + +#: ./doc/common/section_cli_nova_secgroups.xml8(title) +msgid "Add security group and rules" +msgstr "" + +#: ./doc/common/section_cli_nova_secgroups.xml9(para) +msgid "" +"The following procedure shows you how to add security groups and add rules " +"to the default security group." +msgstr "" + +#: ./doc/common/section_cli_nova_secgroups.xml12(title) +msgid "Add or delete a security group" +msgstr "" + +#: ./doc/common/section_cli_nova_secgroups.xml13(para) +msgid "Security groups can be added with ." +msgstr "" + +#: ./doc/common/section_cli_nova_secgroups.xml15(para) +msgid "" +"The following example shows the creation of the security group " +"secure1. After the group is created, it can be viewed in " +"the security group list." +msgstr "" + +#: ./doc/common/section_cli_nova_secgroups.xml39(para) +msgid "" +"All the traffic originated by the instances (outbound traffic) is allowed" +msgstr "" + +#: ./doc/common/section_cli_nova_secgroups.xml43(para) +msgid "All the traffic destined to instances (inbound traffic) is denied" +msgstr "" + +#: ./doc/common/section_cli_nova_secgroups.xml47(para) +msgid "All the instances inside the group are allowed to talk to each other" +msgstr "" + +#: ./doc/common/section_cli_nova_secgroups.xml52(para) +msgid "" +"You can add extra rules into the default security group for handling the " +"egress traffic. Rules are ingress only at this time." +msgstr "" + +#: ./doc/common/section_cli_nova_secgroups.xml35(para) +msgid "" +"Security groups can be deleted with . The default security " +"group cannot be deleted. The default security group contains these initial " +"settings:" +msgstr "" + +#: ./doc/common/section_cli_nova_secgroups.xml56(para) +msgid "" +"In the following example, the group secure1 is deleted. " +"When you view the security group list, it no longer appears." +msgstr "" + +#: ./doc/common/section_cli_nova_secgroups.xml71(title) +msgid "Modify security group rules" +msgstr "" + +#: ./doc/common/section_cli_nova_secgroups.xml74(para) +msgid "It is not possible to change the default outbound behaviour." +msgstr "" + +#: ./doc/common/section_cli_nova_secgroups.xml83(para) +#: ./doc/common/section_cli_nova_secgroups.xml101(para) +#: ./doc/common/section_cli_nova_secgroups.xml167(para) +msgid "<secgroup> ID of security group." +msgstr "" + +#: ./doc/common/section_cli_nova_secgroups.xml86(para) +#: ./doc/common/section_cli_nova_secgroups.xml170(para) +msgid "<ip_proto> IP protocol (icmp, tcp, udp)." +msgstr "" + +#: ./doc/common/section_cli_nova_secgroups.xml89(para) +#: ./doc/common/section_cli_nova_secgroups.xml173(para) +msgid "<from_port> Port at start of range." +msgstr "" + +#: ./doc/common/section_cli_nova_secgroups.xml92(para) +#: ./doc/common/section_cli_nova_secgroups.xml176(para) +msgid "<to_port> Port at end of range." +msgstr "" + +#: ./doc/common/section_cli_nova_secgroups.xml95(para) +#: ./doc/common/section_cli_nova_secgroups.xml179(para) +msgid "<cidr> CIDR for address range." +msgstr "" + +#: ./doc/common/section_cli_nova_secgroups.xml72(para) +msgid "" +"The security group rules control the incoming traffic that is allowed to the" +" instances in the group, while all outbound traffic is automatically " +"allowed. Every security group rule is a policy which allows " +"you to specify inbound connections that are allowed to access the instance, " +"by source address, destination port and IP protocol,(TCP, UDP or ICMP). " +"Currently, ipv6 and other protocols cannot be managed with the security " +"rules, making them permitted by default. To manage such, you can deploy a " +"firewall in front of your OpenStack cloud to control other types of traffic." +" The command requires the following arguments for both TCP and UDP rules : " +"" +msgstr "" + +#: ./doc/common/section_cli_nova_secgroups.xml104(para) +msgid "<ip_proto> IP protocol (with icmp specified)." +msgstr "" + +#: ./doc/common/section_cli_nova_secgroups.xml107(para) +msgid "<ICMP_code> The ICMP code." +msgstr "" + +#: ./doc/common/section_cli_nova_secgroups.xml110(para) +msgid "<ICMP_type> The ICMP type." +msgstr "" + +#: ./doc/common/section_cli_nova_secgroups.xml113(para) +msgid "<cidr> CIDR for the source address range." +msgstr "" + +#: ./doc/common/section_cli_nova_secgroups.xml117(para) +msgid "" +"Entering \"-1\" for both code and type indicates that all ICMP codes and " +"types should be allowed." +msgstr "" + +#: ./doc/common/section_cli_nova_secgroups.xml98(para) +msgid "" +"For ICMP rules, instead of specifying a begin and end port, you specify the " +"allowed ICMP code and ICMP type: " +msgstr "" + +#: ./doc/common/section_cli_nova_secgroups.xml124(title) +msgid "The CIDR notation" +msgstr "" + +#: ./doc/common/section_cli_nova_secgroups.xml125(para) +msgid "" +"That notation allows you to specify a base IP address and a suffix that " +"designates the number of significant bits in the IP address used to identify" +" the network. For example, by specifying a 88.170.60.32/27, you specify " +"88.170.60.32 as the base IP and 27 as the" +" suffix. Since you use an IPV4 format, " +"there are only 5 bits available for the host part (32 minus 27). The " +"0.0.0.0/0 notation means you allow the entire IPV4 range, meaning allowing " +"all addresses." +msgstr "" + +#: ./doc/common/section_cli_nova_secgroups.xml135(para) +msgid "" +"For example, in order to allow any IP address to access to a web server " +"running on one of your instance inside the default security " +"group:" +msgstr "" + +#: ./doc/common/section_cli_nova_secgroups.xml145(para) +msgid "" +"In order to allow any IP address to ping an instance inside the default " +"security group (Code 0, Type 8 for the ECHO request.):" +msgstr "" + +#: ./doc/common/section_cli_nova_secgroups.xml164(para) +msgid "" +"In order to delete a rule, you need to specify the exact same arguments you " +"used to create it:" +msgstr "" + +#: ./doc/common/section_keystone-concepts-domain-management.xml6(title) +#: ./doc/common/section_dashboard_access.xml347(guilabel) +msgid "Domains" +msgstr "" + +#: ./doc/common/section_keystone-concepts-domain-management.xml7(para) +msgid "" +"A domain defines administrative boundaries for the management of Identity " +"entities. A domain may represent an individual, company, or operator-owned " +"space. It is used for exposing administrative activities directly to the " +"system users." +msgstr "" + +#: ./doc/common/section_keystone-concepts-domain-management.xml10(para) +msgid "" +"A domain is a collection of tenants, users, and roles. Users may be given a " +"domain's administrator role. A domain administrator may create tenants, " +"users, and groups within a domain and assign roles to users and groups." +msgstr "" + +#: ./doc/common/section_cli_nova_get_console.xml7(title) +msgid "Get a console to access an instance" +msgstr "" + +#: ./doc/common/section_cli_nova_get_console.xml8(para) +msgid "To get a VNC console to access an instance, run the following command:" +msgstr "" + +#: ./doc/common/section_cli_nova_get_console.xml10(para) +msgid "The command returns a URL from which you can access your instance:" +msgstr "" + +#: ./doc/common/section_cli_nova_get_console.xml16(para) +msgid "" +"To get a non-VNC console, specify the novnc parameter" +" instead of the xvpvnc parameter." +msgstr "" + +#: ./doc/common/section_getstart_telemetry.xml5(title) +msgid "The Telemetry Service" +msgstr "" + +#: ./doc/common/section_getstart_telemetry.xml6(para) +msgid "The OpenStack Telemetry service:" +msgstr "" + +#: ./doc/common/section_getstart_telemetry.xml10(para) +msgid "" +"Efficiently collects the metering data about the CPU and network costs." +msgstr "" + +#: ./doc/common/section_getstart_telemetry.xml14(para) +msgid "" +"Collects data by monitoring notifications sent from services or by polling " +"the infrastructure." +msgstr "" + +#: ./doc/common/section_getstart_telemetry.xml18(para) +msgid "" +"Configures the type of collected data to meet various operating " +"requirements. Accessing and inserting the metering data through the REST " +"API." +msgstr "" + +#: ./doc/common/section_getstart_telemetry.xml23(para) +msgid "" +"Expands the framework to collect custom usage data by additional plug-ins." +msgstr "" + +#: ./doc/common/section_getstart_telemetry.xml27(para) +msgid "Produces signed metering messages that cannot be repudiated." +msgstr "" + +#: ./doc/common/section_getstart_telemetry.xml32(para) +msgid "The system consists of the following basic components:" +msgstr "" + +#: ./doc/common/section_getstart_telemetry.xml36(para) +msgid "" +"A compute agent (ceilometer-agent-" +"compute). Runs on each compute node and polls for resource " +"utilization statistics. There may be other types of agents in the future, " +"but for now we will focus on creating the compute agent." +msgstr "" + +#: ./doc/common/section_getstart_telemetry.xml44(para) +msgid "" +"A central agent (ceilometer-agent-" +"central). Runs on a central management server to poll for " +"resource utilization statistics for resources not tied to instances or " +"compute nodes." +msgstr "" + +#: ./doc/common/section_getstart_telemetry.xml51(para) +msgid "" +"A collector (ceilometer-" +"collector). Runs on one or more central management servers to " +"monitor the message queues (for notifications and for metering data coming " +"from the agent). Notification messages are processed and turned into " +"metering messages and sent back out onto the message bus using the " +"appropriate topic. Telemetry messages are written to the data store without " +"modification." +msgstr "" + +#: ./doc/common/section_getstart_telemetry.xml62(para) +msgid "" +"An alarm notifier (ceilometer-alarm-" +"notifier). Runs on one or more central management servers to " +"allow settting alarms based on threshold evaluation for a collection of " +"samples." +msgstr "" + +#: ./doc/common/section_getstart_telemetry.xml69(para) +msgid "" +"A data store. A database capable of handling concurrent writes (from one or " +"more collector instances) and reads (from the API server)." +msgstr "" + +#: ./doc/common/section_getstart_telemetry.xml74(para) +msgid "" +"An API server (ceilometer-api). " +"Runs on one or more central management servers to provide access to the data" +" from the data store. These services communicate using the standard " +"OpenStack messaging bus. Only the collector and API server have access to " +"the data store." +msgstr "" + +#: ./doc/common/section_getstart_telemetry.xml83(para) +msgid "" +"These services communicate by using the standard OpenStack messaging bus. " +"Only the collector and API server have access to the data store." +msgstr "" + +#: ./doc/common/section_compute-configure-quotas.xml9(title) +msgid "Configure quotas" +msgstr "" + +#: ./doc/common/section_compute-configure-quotas.xml10(para) +msgid "" +"To prevent system capacities from being exhausted without notification, you " +"can set up quotas. Quotas are operational limits. For example, the number of" +" gigabytes allowed per tenant can be controlled so that cloud resources are " +"optimized. Quotas are currently enforced at the tenant (or project) level, " +"rather than by user." +msgstr "" + +#: ./doc/common/section_cli_swift_commands.xml11(title) +msgid "swift commands" +msgstr "" + +#: ./doc/common/section_cli_swift_commands.xml12(para) +msgid "" +"The swift client is the command-line interface (CLI) for the OpenStack " +"Object Storage API and its extensions." +msgstr "" + +#: ./doc/common/section_cli_swift_commands.xml20(title) +msgid "swift usage" +msgstr "" + +#: ./doc/common/section_cli_swift_commands.xml36(title) +msgid "swift positional arguments" +msgstr "" + +#: ./doc/common/section_cli_swift_commands.xml50(title) +msgid "swift examples" +msgstr "" + +#: ./doc/common/section_cli_swift_commands.xml61(title) +msgid "swift optional arguments" +msgstr "" + +#: ./doc/common/section_cli_swift_commands.xml118(title) +msgid "swift delete command" +msgstr "" + +#: ./doc/common/section_cli_swift_commands.xml200(title) +msgid "swift download command" +msgstr "" + +#: ./doc/common/section_cli_swift_commands.xml309(title) +msgid "swift list command" +msgstr "" + +#: ./doc/common/section_cli_swift_commands.xml391(title) +msgid "swift post command" +msgstr "" + +#: ./doc/common/section_cli_swift_commands.xml491(title) +msgid "swift stat command" +msgstr "" + +#: ./doc/common/section_cli_swift_commands.xml561(title) +msgid "swift upload command" +msgstr "" + +#: ./doc/common/section_xen-install.xml6(title) +msgid "Install XenServer and XCP" +msgstr "" + +#: ./doc/common/section_xen-install.xml8(para) +msgid "" +"Before you can run OpenStack with XCP or XenServer, you must install the " +"software on an" +" appropriate server." +msgstr "" + +#: ./doc/common/section_xen-install.xml13(para) +msgid "" +"Xen is a type 1 hypervisor: When your server starts, Xen is the first " +"software that runs. Consequently, you must install XenServer or XCP before " +"you install the operating system where you want to run OpenStack code. The " +"OpenStack services then run in a virtual machine that you install on top of " +"XenServer." +msgstr "" + +#: ./doc/common/section_xen-install.xml20(para) +msgid "" +"Before you can install your system, decide whether to install a free or paid" +" edition of Citrix XenServer or Xen Cloud Platform from Xen.org. Download " +"the software from these locations:" +msgstr "" + +#: ./doc/common/section_xen-install.xml28(link) +msgid "http://www.citrix.com/XenServer/download" +msgstr "" + +#: ./doc/common/section_xen-install.xml33(link) +msgid "http://www.xen.org/download/xcp/index.html" +msgstr "" + +#: ./doc/common/section_xen-install.xml36(para) +msgid "" +"When you install many servers, you might find it easier to perform PXE" +" boot installations of XenServer or XCP. You can also package any " +"post-installation changes that you want to make to your XenServer by creating" +" your own XenServer supplemental pack." +msgstr "" + +#: ./doc/common/section_xen-install.xml46(para) +msgid "" +"You can also install the xcp-xenapi package on Debian-" +"based distributions to get XCP. However, this is not as mature or feature " +"complete as above distributions. This modifies your boot loader to first " +"boot Xen and boot your existing OS on top of Xen as Dom0. The xapi daemon " +"runs in Dom0. Find more details at http://wiki.xen.org/wiki/Project_Kronos." +msgstr "" + +#: ./doc/common/section_xen-install.xml55(para) +msgid "" +"Make sure you use the EXT type of storage repository (SR). Features that " +"require access to VHD files (such as copy on write, snapshot and migration) " +"do not work when you use the LVM SR. Storage repository (SR) is a XenAPI-" +"specific term relating to the physical storage where virtual disks are " +"stored." +msgstr "" + +#: ./doc/common/section_xen-install.xml61(para) +msgid "" +"On the XenServer/XCP installation screen, choose the XenDesktop " +"Optimized option. If you use an answer file, make sure you use " +"srtype=\"ext\" in the tag " +"of the answer file." +msgstr "" + +#: ./doc/common/section_xen-install.xml69(title) +msgid "Post-installation steps" +msgstr "" + +#: ./doc/common/section_xen-install.xml70(para) +msgid "Complete these steps to install OpenStack in your XenServer system:" +msgstr "" + +#: ./doc/common/section_xen-install.xml74(para) +msgid "" +"For resize and migrate functionality, complete the changes described in the " +"Configure resize section in the OpenStack " +"Configuration Reference." +msgstr "" + +#: ./doc/common/section_xen-install.xml82(para) +msgid "" +"Install the VIF isolation rules to help prevent mac and IP address spoofing." +msgstr "" + +#: ./doc/common/section_xen-install.xml86(para) +msgid "Install the XenAPI plug-ins. See the following section." +msgstr "" + +#: ./doc/common/section_xen-install.xml90(para) +msgid "" +"To support AMI type images, you must set up /boot/guest " +"symlink/directory in Dom0. For detailed instructions, see next section." +msgstr "" + +#: ./doc/common/section_xen-install.xml96(para) +msgid "" +"To support resize/migration, set up an ssh trust relation between your " +"XenServer hosts, and ensure /images is properly set up. " +"See next section for more details." +msgstr "" + +#: ./doc/common/section_xen-install.xml102(para) +msgid "" +"Create a Paravirtualized virtual machine that can run the OpenStack compute " +"code." +msgstr "" + +#: ./doc/common/section_xen-install.xml106(para) +msgid "" +"Install and configure the nova-" +"compute in the above virtual machine." +msgstr "" + +#: ./doc/common/section_xen-install.xml111(para) +msgid "" +"For more information, see how DevStack performs the last three steps for " +"developer deployments. For more information about DevStack, see " +"Getting Started With XenServer and Devstack (https://github.com/openstack-" +"dev/devstack/blob/master/tools/xen/README.md). Find more information " +"about the first step, see Multi Tenancy Networking Protections in" +" XenServer (https://github.com/openstack/nova/blob/master/plugins/xenserver/doc/networking.rst)." +" For information about how to install the XenAPI plug-ins, see " +"XenAPI README (https://github.com/openstack/nova/blob/master/plugins/xenserver/xenapi/README)." +msgstr "" + +#: ./doc/common/section_xen-install.xml131(title) +msgid "Xen boot from ISO" +msgstr "" + +#: ./doc/common/section_xen-install.xml132(para) +msgid "" +"XenServer, through the XenAPI integration with OpenStack, provides a feature" +" to boot instances from an ISO file. To activate the Boot From ISO feature, " +"you must configure the SR elements on XenServer host, as follows:" +msgstr "" + +#: ./doc/common/section_xen-install.xml139(para) +msgid "" +"Create an ISO-typed SR, such as an NFS ISO library, for instance. For this, " +"using XenCenter is a simple method. You must export an NFS volume from a " +"remote NFS server. Make sure it is exported in read-write mode." +msgstr "" + +#: ./doc/common/section_xen-install.xml146(para) +msgid "On the compute host, find and record the uuid of this ISO SR:" +msgstr "" + +#: ./doc/common/section_xen-install.xml151(para) +msgid "Locate the uuid of the NFS ISO library:" +msgstr "" + +#: ./doc/common/section_xen-install.xml155(para) +msgid "" +"Set the uuid and configuration. Even if an NFS mount point is not local, you" +" must specify local-storage-iso." +msgstr "" + +#: ./doc/common/section_xen-install.xml161(para) +msgid "" +"Make sure the host-uuid from xe pbd-list equals the uuid " +"of the host you found previously:" +msgstr "" + +#: ./doc/common/section_xen-install.xml167(para) +msgid "" +"You can now add images through the OpenStack Image Service with disk-format=iso, and boot them in OpenStack Compute:" +msgstr "" + +#. When image changes, this message will be marked fuzzy or untranslated for +#. you. +#. It doesn't matter what you translate it to: it's not used at all. +#: ./doc/common/section_getstart_conceptual_arch.xml16(None) +msgid "" +"@@image: 'figures/openstack_havana_conceptual_arch.png'; " +"md5=96e1d5492d4c865fc9145710bb294a91" +msgstr "" + +#: ./doc/common/section_getstart_conceptual_arch.xml6(title) +msgid "Conceptual architecture" +msgstr "" + +#: ./doc/common/section_getstart_conceptual_arch.xml7(para) +msgid "" +"The following diagram shows the relationships among the OpenStack services:" +msgstr "" + +#: ./doc/common/section_getstart_conceptual_arch.xml11(title) +msgid "OpenStack conceptual architecture" +msgstr "" + +#: ./doc/common/section_cli_nova_metadata.xml9(title) +msgid "Insert metadata during launch" +msgstr "" + +#: ./doc/common/section_cli_nova_metadata.xml10(para) +msgid "" +"When booting a server, you can also add metadata, so that you can more " +"easily identify it amongst your ever-growing elastic cloud. Use the " +"--meta option with a key=value pair, where you can make " +"up the string for both the key and the value. For example, you could add a " +"description and also the creator of the server. " +msgstr "" + +#: ./doc/common/section_cli_nova_metadata.xml18(para) +msgid "" +"When viewing the server information, you can see the metadata included on " +"the metadata line: " +msgstr "" + +#. When image changes, this message will be marked fuzzy or untranslated for +#. you. +#. It doesn't matter what you translate it to: it's not used at all. +#: ./doc/common/section_objectstorage-arch.xml20(None) +msgid "" +"@@image: '../common/figures/objectstorage-arch.png'; " +"md5=90f6c7cf3947d7987eeb55d657cdc927" +msgstr "" + +#. When image changes, this message will be marked fuzzy or untranslated for +#. you. +#. It doesn't matter what you translate it to: it's not used at all. +#: ./doc/common/section_objectstorage-arch.xml57(None) +msgid "" +"@@image: '../common/figures/objectstorage-nodes.png'; " +"md5=2aa7eb3bddcf6826f33469920dc2a9c3" +msgstr "" + +#. ... Old module003-ch007-swift-cluster-architecture edited, renamed, and +#. stored in doc/common for use by both Cloud Admin and Operator Training +#. Guides... +#: ./doc/common/section_objectstorage-arch.xml8(title) +msgid "Cluster architecture" +msgstr "" + +#: ./doc/common/section_objectstorage-arch.xml10(title) +msgid "Access tier" +msgstr "" + +#: ./doc/common/section_objectstorage-arch.xml11(para) +msgid "" +"Large-scale deployments segment off an access tier, which is considered the " +"Object Storage system's central hub. The access tier fields the incoming API" +" requests from clients and moves data in and out of the system. This tier " +"consists of front-end load balancers, ssl-terminators, and authentication " +"services. It runs the (distributed) brain of the Object Storage system—the " +"proxy server processes." +msgstr "" + +#: ./doc/common/section_objectstorage-arch.xml17(title) +msgid "Object Storage architecture" +msgstr "" + +#: ./doc/common/section_objectstorage-arch.xml24(para) +msgid "" +"Because access servers are collocated in their own tier, you can scale out " +"read/write access regardless of the storage capacity. For example, if a " +"cluster is on the public Internet, requires SSL termination, and has a high " +"demand for data access, you can provision many access servers. However, if " +"the cluster is on a private network and used primarily for archival " +"purposes, you need fewer access servers." +msgstr "" + +#: ./doc/common/section_objectstorage-arch.xml29(para) +msgid "" +"Since this is an HTTP addressable storage service, you may incorporate a " +"load balancer into the access tier." +msgstr "" + +#: ./doc/common/section_objectstorage-arch.xml31(para) +msgid "" +"Typically, the tier consists of a collection of 1U servers. These machines " +"use a moderate amount of RAM and are network I/O intensive. Since these " +"systems field each incoming API request, you should provision them with two " +"high-throughput (10GbE) interfaces—one for the incoming \"front-end\" " +"requests and the other for the \"back-end\" access to the object storage " +"nodes to put and fetch data." +msgstr "" + +#: ./doc/common/section_objectstorage-arch.xml37(title) +#: ./doc/common/section_objectstorage-arch.xml65(title) +msgid "Factors to consider" +msgstr "" + +#: ./doc/common/section_objectstorage-arch.xml38(para) +msgid "" +"For most publicly facing deployments as well as private deployments " +"available across a wide-reaching corporate network, you use SSL to encrypt " +"traffic to the client. SSL adds significant processing load to establish " +"sessions between clients, which is why you have to provision more capacity " +"in the access layer. SSL may not be required for private deployments on " +"trusted networks." +msgstr "" + +#: ./doc/common/section_objectstorage-arch.xml46(title) +msgid "Storage nodes" +msgstr "" + +#: ./doc/common/section_objectstorage-arch.xml47(para) +msgid "" +"In most configurations, each of the five zones should have an equal amount " +"of storage capacity. Storage nodes use a reasonable amount of memory and " +"CPU. Metadata needs to be readily available to return objects quickly. The " +"object stores run services not only to field incoming requests from the " +"access tier, but to also run replicators, auditors, and reapers. You can " +"provision object stores provisioned with single gigabit or 10 gigabit " +"network interface depending on the expected workload and desired " +"performance." +msgstr "" + +#: ./doc/common/section_objectstorage-arch.xml54(title) +#: ./doc/common/section_storage-concepts.xml17(td) +#: ./doc/common/section_objectstorage-characteristics.xml47(title) +msgid "Object Storage (Swift)" +msgstr "" + +#: ./doc/common/section_objectstorage-arch.xml61(para) +msgid "" +"Currently, 2TB or 3TB SATA disks deliver good price/performance value. You " +"can use desktop-grade drives if you have responsive remote hands in the " +"datacenter and enterprise-grade drives if you don't." +msgstr "" + +#: ./doc/common/section_objectstorage-arch.xml66(para) +msgid "" +"You should keep in mind the desired I/O performance for single-threaded " +"requests . This system does not use RAID, so a single disk handles each " +"request for an object. Disk performance impacts single-threaded response " +"rates." +msgstr "" + +#: ./doc/common/section_objectstorage-arch.xml69(para) +msgid "" +"To achieve apparent higher throughput, the object storage system is designed" +" to handle concurrent uploads/downloads. The network I/O capacity (1GbE, " +"bonded 1GbE pair, or 10GbE) should match your desired concurrent throughput " +"needs for reads and writes." +msgstr "" + +#: ./doc/common/section_dochistory.xml6(title) +msgid "Document change history" +msgstr "" + +#: ./doc/common/section_dochistory.xml8(para) +msgid "" +"This version of the guide replaces and obsoletes all previous versions. The " +"following table describes the most recent changes:" +msgstr "" + +#: ./doc/common/section_cli_nova_host_aggregates.xml6(title) +msgid "Host aggregates" +msgstr "" + +#: ./doc/common/section_cli_nova_host_aggregates.xml7(para) +msgid "" +"Host aggregates are a mechanism to further partition an availability zone; " +"while availability zones are visible to users, host aggregates are only " +"visible to administrators. Host Aggregates provide a mechanism to allow " +"administrators to assign key-value pairs to groups of machines. Each node " +"can have multiple aggregates, each aggregate can have multiple key-value " +"pairs, and the same key-value pair can be assigned to multiple aggregates. " +"This information can be used in the scheduler to enable advanced scheduling," +" to set up hypervisor resource pools or to define logical groups for " +"migration." +msgstr "" + +#: ./doc/common/section_cli_nova_host_aggregates.xml19(title) +msgid "Command-line interface" +msgstr "" + +#: ./doc/common/section_cli_nova_host_aggregates.xml26(para) +msgid "Print a list of all aggregates." +msgstr "" + +#: ./doc/common/section_cli_nova_host_aggregates.xml31(replaceable) +#: ./doc/common/section_cli_nova_host_aggregates.xml107(replaceable) +msgid "<name>" +msgstr "" + +#: ./doc/common/section_cli_nova_host_aggregates.xml32(replaceable) +msgid "<availability-zone>" +msgstr "" + +#: ./doc/common/section_cli_nova_host_aggregates.xml34(para) +msgid "" +"Create a new aggregate named <name> in " +"availability zone <availability-zone>. " +"Returns the ID of the newly created aggregate. Hosts can be made available " +"to multiple availability zones, but administrators should be careful when " +"adding the host to a different host aggregate within the same availability " +"zone and pay attention when using the and " +"commands to avoid user confusion when they boot instances in different " +"availability zones. An error occurs if you cannot add a particular host to " +"an aggregate zone for which it is not intended." +msgstr "" + +#: ./doc/common/section_cli_nova_host_aggregates.xml56(replaceable) +#: ./doc/common/section_cli_nova_host_aggregates.xml64(replaceable) +#: ./doc/common/section_cli_nova_host_aggregates.xml72(replaceable) +#: ./doc/common/section_cli_nova_host_aggregates.xml83(replaceable) +#: ./doc/common/section_cli_nova_host_aggregates.xml94(replaceable) +#: ./doc/common/section_cli_nova_host_aggregates.xml106(replaceable) +msgid "<id>" +msgstr "" + +#: ./doc/common/section_cli_nova_host_aggregates.xml58(para) +msgid "Delete an aggregate with id <id>." +msgstr "" + +#: ./doc/common/section_cli_nova_host_aggregates.xml66(para) +msgid "" +"Show details of the aggregate with id <id>." +msgstr "" + +#: ./doc/common/section_cli_nova_host_aggregates.xml73(replaceable) +#: ./doc/common/section_cli_nova_host_aggregates.xml84(replaceable) +msgid "<host>" +msgstr "" + +#: ./doc/common/section_cli_nova_host_aggregates.xml75(para) +msgid "" +"Add host with name <host> to aggregate with" +" id <id>." +msgstr "" + +#: ./doc/common/section_cli_nova_host_aggregates.xml86(para) +msgid "" +"Remove the host with name <host> from the " +"aggregate with id <id>." +msgstr "" + +#: ./doc/common/section_cli_nova_host_aggregates.xml95(replaceable) +#: ./doc/common/section_cli_nova_host_aggregates.xml96(replaceable) +msgid "<key=value>" +msgstr "" + +#: ./doc/common/section_cli_nova_host_aggregates.xml99(para) +msgid "" +"Add or update metadata (key-value pairs) associated with the aggregate with " +"id <id>." +msgstr "" + +#: ./doc/common/section_cli_nova_host_aggregates.xml108(replaceable) +msgid "<availability_zone>" +msgstr "" + +#: ./doc/common/section_cli_nova_host_aggregates.xml110(para) +msgid "Update the name and availability zone (optional) for the aggregate." +msgstr "" + +#: ./doc/common/section_cli_nova_host_aggregates.xml117(para) +msgid "List all hosts by service." +msgstr "" + +#: ./doc/common/section_cli_nova_host_aggregates.xml124(para) +msgid "Put/resume host into/from maintenance." +msgstr "" + +#: ./doc/common/section_cli_nova_host_aggregates.xml20(para) +msgid "" +"The command-line tool supports the following aggregate-" +"related commands. " +msgstr "" + +#: ./doc/common/section_cli_nova_host_aggregates.xml130(para) +msgid "" +"Only administrators can access these commands. If you try to use these " +"commands and the user name and tenant that you use to access the Compute " +"service do not have the admin role or the appropriate " +"privileges, these errors occur:" +msgstr "" + +#: ./doc/common/section_cli_nova_host_aggregates.xml142(title) +msgid "Configure scheduler to support host aggregates" +msgstr "" + +#: ./doc/common/section_cli_nova_host_aggregates.xml143(para) +msgid "" +"One common use case for host aggregates is when you want to support " +"scheduling instances to a subset of compute hosts because they have a " +"specific capability. For example, you may want to allow users to request " +"compute hosts that have SSD drives if they need access to faster disk I/O, " +"or access to compute hosts that have GPU cards to take advantage of GPU-" +"accelerated code." +msgstr "" + +#: ./doc/common/section_cli_nova_host_aggregates.xml150(para) +msgid "" +"To configure the scheduler to support host aggregates, the " +"scheduler_default_filters configuration option must " +"contain the AggregateInstanceExtraSpecsFilter in addition" +" to the other filters used by the scheduler. Add the following line to " +"/etc/nova/nova.conf on the host that runs the " +"nova-scheduler service to enable " +"host aggregates filtering, as well as the other filters that are typically " +"enabled:" +msgstr "" + +#: ./doc/common/section_cli_nova_host_aggregates.xml164(title) +msgid "Example: Specify compute hosts with SSDs" +msgstr "" + +#: ./doc/common/section_cli_nova_host_aggregates.xml165(para) +msgid "" +"This example configures the Compute service to enable users to request nodes" +" that have solid-state drives (SSDs). You create a fast-" +"io host aggregate in the nova availability zone" +" and you add the ssd=true key-value pair to the " +"aggregate. Then, you add the node1, and " +"node2 compute nodes to it." +msgstr "" + +#: ./doc/common/section_cli_nova_host_aggregates.xml201(para) +msgid "" +"Use the command to create the ssd.large " +"flavor called with an ID of 6, 8GB of RAM, 80GB root disk, and 4 vCPUs." +msgstr "" + +#: ./doc/common/section_cli_nova_host_aggregates.xml211(para) +msgid "" +"Once the flavor is created, specify one or more key-value pairs that match " +"the key-value pairs on the host aggregates. In this case, that is the " +"ssd=true key-value pair. Setting a key-value pair on a " +"flavor is done using the command." +msgstr "" + +#: ./doc/common/section_cli_nova_host_aggregates.xml218(para) +msgid "" +"Once it is set, you should see the extra_specs property " +"of the ssd.large flavor populated with a key of " +"ssd and a corresponding value of true." +msgstr "" + +#: ./doc/common/section_cli_nova_host_aggregates.xml239(para) +msgid "" +"Now, when a user requests an instance with the ssd.large " +"flavor, the scheduler only considers hosts with the " +"ssd=true key-value pair. In this example, these are " +"node1 and node2." +msgstr "" + +#: ./doc/common/section_cli_nova_host_aggregates.xml247(title) +msgid "XenServer hypervisor pools to support live migration" +msgstr "" + +#: ./doc/common/section_cli_nova_host_aggregates.xml249(para) +msgid "" +"When using the XenAPI-based hypervisor, the Compute service uses host " +"aggregates to manage XenServer Resource pools, which are used in supporting " +"live migration." +msgstr "" + +#: ./doc/common/section_keystone_db_sync.xml6(title) +msgid "Migrate the Identity Service database" +msgstr "" + +#: ./doc/common/section_keystone_db_sync.xml7(para) +msgid "" +"Between revisions of the Identity Service project, you might need to " +"complete SQL migrations. The Identity Service project uses SQLAlchemy-" +"migrate (see http://code.google.com/p/sqlalchemy-migrate/) to migrate " +"the SQL database between revisions. For core components, the source code " +"stores migrations in a central repository under a " +"keystone/common/sql/migrate_repo directory." +msgstr "" + +#: ./doc/common/section_keystone_db_sync.xml17(para) +msgid "" +"Extensions to the Identity Service might also require SQL migrations. The " +"directory keystone/contrib/example in the keystone " +"repository contains a sample extension migration." +msgstr "" + +#: ./doc/common/section_keystone_db_sync.xml23(title) +msgid "To set up a migration for an extension" +msgstr "" + +#: ./doc/common/section_keystone_db_sync.xml25(para) +msgid "" +"Create a directory structure where my_extension is the " +"name of the extension, as follows: " +"keystone/contrib/my_extension/migrate_repo/versions/." +msgstr "" + +#: ./doc/common/section_keystone_db_sync.xml31(para) +msgid "" +"Create empty __init__.py files in the " +"migrate_repo and versions " +"subdirectories." +msgstr "" + +#: ./doc/common/section_keystone_db_sync.xml37(para) +msgid "" +"Create a migrate.cfg configuration file in the " +"migrate_repo subdirectory, which conforms to a " +"key/value .ini file format." +msgstr "" + +#: ./doc/common/section_keystone_db_sync.xml41(para) +msgid "An example configuration file:" +msgstr "" + +#: ./doc/common/section_keystone_db_sync.xml49(title) +msgid "To test a migration for a specific extension" +msgstr "" + +#: ./doc/common/section_keystone_db_sync.xml50(para) +msgid "" +"You can use the command with the " +"--extension parameter for both the " +"and commands. Ensure that the required configuration files " +"exist before completing these steps." +msgstr "" + +#: ./doc/common/section_keystone_db_sync.xml57(para) +msgid "Test your migrations with an example extension:" +msgstr "" + +#: ./doc/common/section_keystone_db_sync.xml62(para) +msgid "Migrate to version 1:" +msgstr "" + +#: ./doc/common/section_keystone_db_sync.xml66(para) +msgid "Migrate back to version 0:" +msgstr "" + +#: ./doc/common/section_keystone_db_sync.xml70(para) +msgid "Check the version:" +msgstr "" + +#: ./doc/common/section_cli_neutron_commands.xml11(title) +msgid "neutron commands" +msgstr "" + +#: ./doc/common/section_cli_neutron_commands.xml12(para) +msgid "" +"The neutron client is the command-line interface (CLI) for the OpenStack " +"Networking API and its extensions." +msgstr "" + +#: ./doc/common/section_cli_neutron_commands.xml20(title) +msgid "neutron usage" +msgstr "" + +#: ./doc/common/section_cli_neutron_commands.xml218(title) +msgid "neutron agent-delete command" +msgstr "" + +#: ./doc/common/section_cli_neutron_commands.xml234(title) +msgid "neutron agent-list command" +msgstr "" + +#: ./doc/common/section_cli_neutron_commands.xml265(title) +msgid "neutron agent-show command" +msgstr "" + +#: ./doc/common/section_cli_neutron_commands.xml302(title) +msgid "neutron agent-update command" +msgstr "" + +#: ./doc/common/section_cli_neutron_commands.xml318(title) +msgid "neutron cisco-credential-create command" +msgstr "" + +#: ./doc/common/section_cli_neutron_commands.xml359(title) +msgid "neutron cisco-credential-delete command" +msgstr "" + +#: ./doc/common/section_cli_neutron_commands.xml376(title) +msgid "neutron cisco-credential-list command" +msgstr "" + +#: ./doc/common/section_cli_neutron_commands.xml408(title) +msgid "neutron cisco-credential-show command" +msgstr "" + +#: ./doc/common/section_cli_neutron_commands.xml446(title) +msgid "neutron cisco-network-profile-create command" +msgstr "" + +#: ./doc/common/section_cli_neutron_commands.xml502(title) +msgid "neutron cisco-network-profile-delete command" +msgstr "" + +#: ./doc/common/section_cli_neutron_commands.xml519(title) +msgid "neutron cisco-network-profile-list command" +msgstr "" + +#: ./doc/common/section_cli_neutron_commands.xml551(title) +msgid "neutron cisco-network-profile-show command" +msgstr "" + +#: ./doc/common/section_cli_neutron_commands.xml590(title) +msgid "neutron cisco-network-profile-update command" +msgstr "" + +#: ./doc/common/section_cli_neutron_commands.xml607(title) +msgid "neutron cisco-policy-profile-list command" +msgstr "" + +#: ./doc/common/section_cli_neutron_commands.xml639(title) +msgid "neutron cisco-policy-profile-show command" +msgstr "" + +#: ./doc/common/section_cli_neutron_commands.xml678(title) +msgid "neutron cisco-policy-profile-update command" +msgstr "" + +#: ./doc/common/section_cli_neutron_commands.xml695(title) +msgid "neutron dhcp-agent-list-hosting-net command" +msgstr "" + +#: ./doc/common/section_cli_neutron_commands.xml731(title) +msgid "neutron dhcp-agent-network-add command" +msgstr "" + +#: ./doc/common/section_cli_neutron_commands.xml749(title) +msgid "neutron dhcp-agent-network-remove command" +msgstr "" + +#: ./doc/common/section_cli_neutron_commands.xml767(title) +msgid "neutron ext-list command" +msgstr "" + +#: ./doc/common/section_cli_neutron_commands.xml798(title) +msgid "neutron ext-show command" +msgstr "" + +#: ./doc/common/section_cli_neutron_commands.xml835(title) +msgid "neutron firewall-create command" +msgstr "" + +#: ./doc/common/section_cli_neutron_commands.xml878(title) +msgid "neutron firewall-delete command" +msgstr "" + +#: ./doc/common/section_cli_neutron_commands.xml894(title) +msgid "neutron firewall-list command" +msgstr "" + +#: ./doc/common/section_cli_neutron_commands.xml938(title) +msgid "neutron firewall-policy-create command" +msgstr "" + +#: ./doc/common/section_cli_neutron_commands.xml984(title) +msgid "neutron firewall-policy-delete command" +msgstr "" + +#: ./doc/common/section_cli_neutron_commands.xml1001(title) +msgid "neutron firewall-policy-insert-rule command" +msgstr "" + +#: ./doc/common/section_cli_neutron_commands.xml1025(title) +msgid "neutron firewall-policy-list command" +msgstr "" + +#: ./doc/common/section_cli_neutron_commands.xml1069(title) +msgid "neutron firewall-policy-remove-rule command" +msgstr "" + +#: ./doc/common/section_cli_neutron_commands.xml1087(title) +msgid "neutron firewall-policy-show command" +msgstr "" + +#: ./doc/common/section_cli_neutron_commands.xml1125(title) +msgid "neutron firewall-policy-update command" +msgstr "" + +#: ./doc/common/section_cli_neutron_commands.xml1142(title) +msgid "neutron firewall-rule-create command" +msgstr "" + +#: ./doc/common/section_cli_neutron_commands.xml1199(title) +msgid "neutron firewall-rule-delete command" +msgstr "" + +#: ./doc/common/section_cli_neutron_commands.xml1216(title) +msgid "neutron firewall-rule-list command" +msgstr "" + +#: ./doc/common/section_cli_neutron_commands.xml1260(title) +msgid "neutron firewall-rule-show command" +msgstr "" + +#: ./doc/common/section_cli_neutron_commands.xml1298(title) +msgid "neutron firewall-rule-update command" +msgstr "" + +#: ./doc/common/section_cli_neutron_commands.xml1318(title) +msgid "neutron firewall-show command" +msgstr "" + +#: ./doc/common/section_cli_neutron_commands.xml1355(title) +msgid "neutron firewall-update command" +msgstr "" + +#: ./doc/common/section_cli_neutron_commands.xml1371(title) +msgid "neutron floatingip-associate command" +msgstr "" + +#: ./doc/common/section_cli_neutron_commands.xml1394(title) +msgid "neutron floatingip-create command" +msgstr "" + +#: ./doc/common/section_cli_neutron_commands.xml1435(title) +msgid "neutron floatingip-delete command" +msgstr "" + +#: ./doc/common/section_cli_neutron_commands.xml1451(title) +msgid "neutron floatingip-disassociate command" +msgstr "" + +#: ./doc/common/section_cli_neutron_commands.xml1468(title) +msgid "neutron floatingip-list command" +msgstr "" + +#: ./doc/common/section_cli_neutron_commands.xml1512(title) +msgid "neutron floatingip-show command" +msgstr "" + +#: ./doc/common/section_cli_neutron_commands.xml1549(title) +msgid "neutron ipsec-site-connection-create command" +msgstr "" + +#: ./doc/common/section_cli_neutron_commands.xml1620(title) +msgid "neutron ipsec-site-connection-delete command" +msgstr "" + +#: ./doc/common/section_cli_neutron_commands.xml1638(title) +msgid "neutron ipsec-site-connection-list command" +msgstr "" + +#: ./doc/common/section_cli_neutron_commands.xml1683(title) +msgid "neutron ipsec-site-connection-show command" +msgstr "" + +#: ./doc/common/section_cli_neutron_commands.xml1723(title) +msgid "neutron ipsec-site-connection-update command" +msgstr "" + +#: ./doc/common/section_cli_neutron_commands.xml1749(title) +msgid "neutron l3-agent-list-hosting-router command" +msgstr "" + +#: ./doc/common/section_cli_neutron_commands.xml1785(title) +msgid "neutron l3-agent-router-add command" +msgstr "" + +#: ./doc/common/section_cli_neutron_commands.xml1803(title) +msgid "neutron l3-agent-router-remove command" +msgstr "" + +#: ./doc/common/section_cli_neutron_commands.xml1821(title) +msgid "neutron lb-agent-hosting-pool command" +msgstr "" + +#: ./doc/common/section_cli_neutron_commands.xml1859(title) +msgid "neutron lb-healthmonitor-associate command" +msgstr "" + +#: ./doc/common/section_cli_neutron_commands.xml1878(title) +msgid "neutron lb-healthmonitor-create command" +msgstr "" + +#: ./doc/common/section_cli_neutron_commands.xml1938(title) +msgid "neutron lb-healthmonitor-delete command" +msgstr "" + +#: ./doc/common/section_cli_neutron_commands.xml1955(title) +msgid "neutron lb-healthmonitor-disassociate command" +msgstr "" + +#: ./doc/common/section_cli_neutron_commands.xml1975(title) +msgid "neutron lb-healthmonitor-list command" +msgstr "" + +#: ./doc/common/section_cli_neutron_commands.xml2019(title) +msgid "neutron lb-healthmonitor-show command" +msgstr "" + +#: ./doc/common/section_cli_neutron_commands.xml2057(title) +msgid "neutron lb-healthmonitor-update command" +msgstr "" + +#: ./doc/common/section_cli_neutron_commands.xml2074(title) +msgid "neutron lb-member-create command" +msgstr "" + +#: ./doc/common/section_cli_neutron_commands.xml2119(title) +msgid "neutron lb-member-delete command" +msgstr "" + +#: ./doc/common/section_cli_neutron_commands.xml2135(title) +msgid "neutron lb-member-list command" +msgstr "" + +#: ./doc/common/section_cli_neutron_commands.xml2179(title) +msgid "neutron lb-member-show command" +msgstr "" + +#: ./doc/common/section_cli_neutron_commands.xml2216(title) +msgid "neutron lb-member-update command" +msgstr "" + +#: ./doc/common/section_cli_neutron_commands.xml2232(title) +msgid "neutron lb-pool-create command" +msgstr "" + +#: ./doc/common/section_cli_neutron_commands.xml2280(title) +msgid "neutron lb-pool-delete command" +msgstr "" + +#: ./doc/common/section_cli_neutron_commands.xml2296(title) +msgid "neutron lb-pool-list command" +msgstr "" + +#: ./doc/common/section_cli_neutron_commands.xml2340(title) +msgid "neutron lb-pool-list-on-agent command" +msgstr "" + +#: ./doc/common/section_cli_neutron_commands.xml2376(title) +msgid "neutron lb-pool-show command" +msgstr "" + +#: ./doc/common/section_cli_neutron_commands.xml2413(title) +msgid "neutron lb-pool-stats command" +msgstr "" + +#: ./doc/common/section_cli_neutron_commands.xml2450(title) +msgid "neutron lb-pool-update command" +msgstr "" + +#: ./doc/common/section_cli_neutron_commands.xml2466(title) +msgid "neutron lb-vip-create command" +msgstr "" + +#: ./doc/common/section_cli_neutron_commands.xml2522(title) +msgid "neutron lb-vip-delete command" +msgstr "" + +#: ./doc/common/section_cli_neutron_commands.xml2538(title) +msgid "neutron lb-vip-list command" +msgstr "" + +#: ./doc/common/section_cli_neutron_commands.xml2582(title) +msgid "neutron lb-vip-show command" +msgstr "" + +#: ./doc/common/section_cli_neutron_commands.xml2619(title) +msgid "neutron lb-vip-update command" +msgstr "" + +#: ./doc/common/section_cli_neutron_commands.xml2635(title) +msgid "neutron meter-label-create command" +msgstr "" + +#: ./doc/common/section_cli_neutron_commands.xml2674(title) +msgid "neutron meter-label-delete command" +msgstr "" + +#: ./doc/common/section_cli_neutron_commands.xml2691(title) +msgid "neutron meter-label-list command" +msgstr "" + +#: ./doc/common/section_cli_neutron_commands.xml2735(title) +msgid "neutron meter-label-rule-create command" +msgstr "" + +#: ./doc/common/section_cli_neutron_commands.xml2777(title) +msgid "neutron meter-label-rule-delete command" +msgstr "" + +#: ./doc/common/section_cli_neutron_commands.xml2794(title) +msgid "neutron meter-label-rule-list command" +msgstr "" + +#: ./doc/common/section_cli_neutron_commands.xml2838(title) +msgid "neutron meter-label-rule-show command" +msgstr "" + +#: ./doc/common/section_cli_neutron_commands.xml2876(title) +msgid "neutron meter-label-show command" +msgstr "" + +#: ./doc/common/section_cli_neutron_commands.xml2913(title) +msgid "neutron net-create command" +msgstr "" + +#: ./doc/common/section_cli_neutron_commands.xml2952(title) +msgid "neutron net-delete command" +msgstr "" + +#: ./doc/common/section_cli_neutron_commands.xml2968(title) +msgid "neutron net-external-list command" +msgstr "" + +#: ./doc/common/section_cli_neutron_commands.xml3012(title) +msgid "neutron net-gateway-connect command" +msgstr "" + +#: ./doc/common/section_cli_neutron_commands.xml3038(title) +msgid "neutron net-gateway-create command" +msgstr "" + +#: ./doc/common/section_cli_neutron_commands.xml3077(title) +msgid "neutron net-gateway-delete command" +msgstr "" + +#: ./doc/common/section_cli_neutron_commands.xml3094(title) +msgid "neutron net-gateway-disconnect command" +msgstr "" + +#: ./doc/common/section_cli_neutron_commands.xml3120(title) +msgid "neutron net-gateway-list command" +msgstr "" + +#: ./doc/common/section_cli_neutron_commands.xml3151(title) +msgid "neutron net-gateway-show command" +msgstr "" + +#: ./doc/common/section_cli_neutron_commands.xml3188(title) +msgid "neutron net-gateway-update command" +msgstr "" + +#: ./doc/common/section_cli_neutron_commands.xml3205(title) +msgid "neutron net-list command" +msgstr "" + +#: ./doc/common/section_cli_neutron_commands.xml3248(title) +msgid "neutron net-list-on-dhcp-agent command" +msgstr "" + +#: ./doc/common/section_cli_neutron_commands.xml3296(title) +msgid "neutron net-show command" +msgstr "" + +#: ./doc/common/section_cli_neutron_commands.xml3333(title) +msgid "neutron net-update command" +msgstr "" + +#: ./doc/common/section_cli_neutron_commands.xml3349(title) +msgid "neutron port-create command" +msgstr "" + +#: ./doc/common/section_cli_neutron_commands.xml3408(title) +msgid "neutron port-delete command" +msgstr "" + +#: ./doc/common/section_cli_neutron_commands.xml3424(title) +msgid "neutron port-list command" +msgstr "" + +#: ./doc/common/section_cli_neutron_commands.xml3467(title) +msgid "neutron port-show command" +msgstr "" + +#: ./doc/common/section_cli_neutron_commands.xml3504(title) +msgid "neutron port-update command" +msgstr "" + +#: ./doc/common/section_cli_neutron_commands.xml3531(title) +msgid "neutron queue-create command" +msgstr "" + +#: ./doc/common/section_cli_neutron_commands.xml3576(title) +msgid "neutron queue-delete command" +msgstr "" + +#: ./doc/common/section_cli_neutron_commands.xml3592(title) +msgid "neutron queue-list command" +msgstr "" + +#: ./doc/common/section_cli_neutron_commands.xml3623(title) +msgid "neutron queue-show command" +msgstr "" + +#: ./doc/common/section_cli_neutron_commands.xml3660(title) +msgid "neutron quota-delete command" +msgstr "" + +#: ./doc/common/section_cli_neutron_commands.xml3676(title) +msgid "neutron quota-list command" +msgstr "" + +#: ./doc/common/section_cli_neutron_commands.xml3703(title) +msgid "neutron quota-show command" +msgstr "" + +#: ./doc/common/section_cli_neutron_commands.xml3735(title) +msgid "neutron quota-update command" +msgstr "" + +#: ./doc/common/section_cli_neutron_commands.xml3781(title) +msgid "neutron router-create command" +msgstr "" + +#: ./doc/common/section_cli_neutron_commands.xml3819(title) +msgid "neutron router-delete command" +msgstr "" + +#: ./doc/common/section_cli_neutron_commands.xml3835(title) +msgid "neutron router-gateway-clear command" +msgstr "" + +#: ./doc/common/section_cli_neutron_commands.xml3852(title) +msgid "neutron router-gateway-set command" +msgstr "" + +#: ./doc/common/section_cli_neutron_commands.xml3872(title) +msgid "neutron router-interface-add command" +msgstr "" + +#: ./doc/common/section_cli_neutron_commands.xml3893(title) +msgid "neutron router-interface-delete command" +msgstr "" + +#: ./doc/common/section_cli_neutron_commands.xml3914(title) +msgid "neutron router-list command" +msgstr "" + +#: ./doc/common/section_cli_neutron_commands.xml3958(title) +msgid "neutron router-list-on-l3-agent command" +msgstr "" + +#: ./doc/common/section_cli_neutron_commands.xml3994(title) +msgid "neutron router-port-list command" +msgstr "" + +#: ./doc/common/section_cli_neutron_commands.xml4042(title) +msgid "neutron router-show command" +msgstr "" + +#: ./doc/common/section_cli_neutron_commands.xml4079(title) +msgid "neutron router-update command" +msgstr "" + +#: ./doc/common/section_cli_neutron_commands.xml4095(title) +msgid "neutron security-group-create command" +msgstr "" + +#: ./doc/common/section_cli_neutron_commands.xml4134(title) +msgid "neutron security-group-delete command" +msgstr "" + +#: ./doc/common/section_cli_neutron_commands.xml4151(title) +msgid "neutron security-group-list command" +msgstr "" + +#: ./doc/common/section_cli_neutron_commands.xml4195(title) +msgid "neutron security-group-rule-create command" +msgstr "" + +#: ./doc/common/section_cli_neutron_commands.xml4252(title) +msgid "neutron security-group-rule-delete command" +msgstr "" + +#: ./doc/common/section_cli_neutron_commands.xml4269(title) +msgid "neutron security-group-rule-list command" +msgstr "" + +#: ./doc/common/section_cli_neutron_commands.xml4316(title) +msgid "neutron security-group-rule-show command" +msgstr "" + +#: ./doc/common/section_cli_neutron_commands.xml4355(title) +msgid "neutron security-group-show command" +msgstr "" + +#: ./doc/common/section_cli_neutron_commands.xml4393(title) +msgid "neutron security-group-update command" +msgstr "" + +#: ./doc/common/section_cli_neutron_commands.xml4414(title) +msgid "neutron service-provider-list command" +msgstr "" + +#: ./doc/common/section_cli_neutron_commands.xml4458(title) +msgid "neutron subnet-create command" +msgstr "" + +#: ./doc/common/section_cli_neutron_commands.xml4514(title) +msgid "neutron subnet-delete command" +msgstr "" + +#: ./doc/common/section_cli_neutron_commands.xml4530(title) +msgid "neutron subnet-list command" +msgstr "" + +#: ./doc/common/section_cli_neutron_commands.xml4574(title) +msgid "neutron subnet-show command" +msgstr "" + +#: ./doc/common/section_cli_neutron_commands.xml4611(title) +msgid "neutron subnet-update command" +msgstr "" + +#: ./doc/common/section_cli_neutron_commands.xml4627(title) +msgid "neutron vpn-ikepolicy-create command" +msgstr "" + +#: ./doc/common/section_cli_neutron_commands.xml4686(title) +msgid "neutron vpn-ikepolicy-delete command" +msgstr "" + +#: ./doc/common/section_cli_neutron_commands.xml4703(title) +msgid "neutron vpn-ikepolicy-list command" +msgstr "" + +#: ./doc/common/section_cli_neutron_commands.xml4747(title) +msgid "neutron vpn-ikepolicy-show command" +msgstr "" + +#: ./doc/common/section_cli_neutron_commands.xml4785(title) +msgid "neutron vpn-ikepolicy-update command" +msgstr "" + +#: ./doc/common/section_cli_neutron_commands.xml4807(title) +msgid "neutron vpn-ipsecpolicy-create command" +msgstr "" + +#: ./doc/common/section_cli_neutron_commands.xml4866(title) +msgid "neutron vpn-ipsecpolicy-delete command" +msgstr "" + +#: ./doc/common/section_cli_neutron_commands.xml4883(title) +msgid "neutron vpn-ipsecpolicy-list command" +msgstr "" + +#: ./doc/common/section_cli_neutron_commands.xml4927(title) +msgid "neutron vpn-ipsecpolicy-show command" +msgstr "" + +#: ./doc/common/section_cli_neutron_commands.xml4965(title) +msgid "neutron vpn-ipsecpolicy-update command" +msgstr "" + +#: ./doc/common/section_cli_neutron_commands.xml4987(title) +msgid "neutron vpn-service-create command" +msgstr "" + +#: ./doc/common/section_cli_neutron_commands.xml5029(title) +msgid "neutron vpn-service-delete command" +msgstr "" + +#: ./doc/common/section_cli_neutron_commands.xml5046(title) +msgid "neutron vpn-service-list command" +msgstr "" + +#: ./doc/common/section_cli_neutron_commands.xml5090(title) +msgid "neutron vpn-service-show command" +msgstr "" + +#: ./doc/common/section_cli_neutron_commands.xml5127(title) +msgid "neutron vpn-service-update command" +msgstr "" + +#: ./doc/common/section_cli_neutron-quotas.xml6(title) +msgid "Manage Networking service quotas" +msgstr "" + +#: ./doc/common/section_cli_neutron-quotas.xml7(para) +msgid "" +"A quota limits the number of available resources. A default quota might be " +"enforced for all tenants. When you try to create more resources than the " +"quota allows, an error occurs:" +msgstr "" + +#: ./doc/common/section_cli_neutron-quotas.xml12(para) +msgid "" +"Per-tenant quota configuration is also supported by the quota extension API." +" See Per-tenant quota " +"configuration for details." +msgstr "" + +#: ./doc/common/section_cli_neutron-quotas.xml16(title) +msgid "Basic quota configuration" +msgstr "" + +#: ./doc/common/section_cli_neutron-quotas.xml17(para) +msgid "" +"In the Networking default quota mechanism, all tenants have the same quota " +"values, such as the number of resources that a tenant can create." +msgstr "" + +#: ./doc/common/section_cli_neutron-quotas.xml20(para) +msgid "" +"The quota value is defined in the OpenStack Networking " +"neutron.conf configuration file. To disable quotas for " +"a specific resource, such as network, subnet, or port, remove a " +"corresponding item from . This example shows the" +" default quota values:" +msgstr "" + +#: ./doc/common/section_cli_neutron-quotas.xml41(para) +msgid "" +"OpenStack Networking also supports quotas for L3 resources: router and " +"floating IP. Add these lines to the quotas section in the" +" neutron.conf file." +msgstr "" + +#: ./doc/common/section_cli_neutron-quotas.xml52(para) +#: ./doc/common/section_cli_neutron-quotas.xml67(para) +msgid "The option does not affect these quotas." +msgstr "" + +#: ./doc/common/section_cli_neutron-quotas.xml55(para) +msgid "" +"OpenStack Networking also supports quotas for security group resources: " +"number of security groups and the number of rules for each security group. " +"Add these lines to the quotas section in the " +"neutron.conf file:" +msgstr "" + +#: ./doc/common/section_cli_neutron-quotas.xml72(title) +msgid "Configure per-tenant quotas" +msgstr "" + +#: ./doc/common/section_cli_neutron-quotas.xml73(para) +msgid "" +"OpenStack Networking also supports per-tenant quota limit by quota extension" +" API." +msgstr "" + +#: ./doc/common/section_cli_neutron-quotas.xml77(para) +msgid ". Deletes defined quotas for a specified tenant." +msgstr "" + +#: ./doc/common/section_cli_neutron-quotas.xml81(para) +msgid ". Lists defined quotas for all tenants." +msgstr "" + +#: ./doc/common/section_cli_neutron-quotas.xml85(para) +msgid ". Shows quotas for a specified tenant." +msgstr "" + +#: ./doc/common/section_cli_neutron-quotas.xml89(para) +msgid ". Updates quotas for a specified tenant." +msgstr "" + +#: ./doc/common/section_cli_neutron-quotas.xml75(para) +msgid "" +"Use these commands to manage per-tenant quotas:Only users " +"with the admin role can change a quota value. By default," +" the default set of quotas are enforced for all tenants, so no " +" command exists." +msgstr "" + +#: ./doc/common/section_cli_neutron-quotas.xml98(title) +msgid "Configure Networking to show per-tenant quotas" +msgstr "" + +#: ./doc/common/section_cli_neutron-quotas.xml99(para) +msgid "" +"Set the quota_driver option in the " +"neutron.conf file:" +msgstr "" + +#: ./doc/common/section_cli_neutron-quotas.xml102(para) +msgid "" +"When you set this option, the output for Networking commands shows " +"quotas." +msgstr "" + +#: ./doc/common/section_cli_neutron-quotas.xml106(title) +msgid "List Networking extensions" +msgstr "" + +#: ./doc/common/section_cli_neutron-quotas.xml107(para) +msgid "To list the Networking extensions, run this command:" +msgstr "" + +#: ./doc/common/section_cli_neutron-quotas.xml110(para) +msgid "" +"The command shows the quotas extension, which provides " +"per-tenant quota management support:" +msgstr "" + +#: ./doc/common/section_cli_neutron-quotas.xml128(title) +msgid "Show information for the quotas extension" +msgstr "" + +#: ./doc/common/section_cli_neutron-quotas.xml129(para) +msgid "" +"To show information for the quotas extension, run this " +"command:" +msgstr "" + +#: ./doc/common/section_cli_neutron-quotas.xml143(para) +msgid "" +"Only some plug-ins support per-tenant quotas. Specifically, Open vSwitch, " +"Linux Bridge, and Nicira NVP support them, but new versions of other plug-" +"ins might bring additional functionality. See the documentation for each " +"plug-in." +msgstr "" + +#: ./doc/common/section_cli_neutron-quotas.xml151(title) +msgid "List tenants who have per-tenant quota support" +msgstr "" + +#: ./doc/common/section_cli_neutron-quotas.xml152(para) +msgid "" +"The command lists tenants for which the per-tenant quota is" +" enabled. The command does not list tenants with default quota support. You " +"must be an administrative user to run this command:" +msgstr "" + +#: ./doc/common/section_cli_neutron-quotas.xml165(title) +msgid "Show per-tenant quota values" +msgstr "" + +#: ./doc/common/section_cli_neutron-quotas.xml166(para) +msgid "" +"The reports the current set of quota limits for the " +"specified tenant. Non-administrative users can run this command without the " +"--tenant_id parameter. If per-tenant quota limits are" +" not enabled for the tenant, the command shows the default set of quotas:" +msgstr "" + +#: ./doc/common/section_cli_neutron-quotas.xml182(para) +msgid "" +"The following command shows the command output for a non-administrative " +"user:" +msgstr "" + +#: ./doc/common/section_cli_neutron-quotas.xml196(title) +msgid "Update quota values for a specified tenant" +msgstr "" + +#: ./doc/common/section_cli_neutron-quotas.xml197(para) +msgid "" +"Use the command to update a quota for a specified tenant:" +msgstr "" + +#: ./doc/common/section_cli_neutron-quotas.xml209(para) +msgid "You can update quotas for multiple resources through one command:" +msgstr "" + +#: ./doc/common/section_cli_neutron-quotas.xml221(para) +msgid "" +"To update the limits for an L3 resource such as, router or floating IP, you " +"must define new values for the quotas after the -- " +"directive." +msgstr "" + +#: ./doc/common/section_cli_neutron-quotas.xml224(para) +msgid "" +"This example updates the limit of the number of floating IPs for the " +"specified tenant:" +msgstr "" + +#: ./doc/common/section_cli_neutron-quotas.xml236(para) +msgid "" +"You can update the limits of multiple resources by including L2 resources " +"and L3 resource through one command." +msgstr "" + +#: ./doc/common/section_cli_neutron-quotas.xml251(title) +msgid "Delete per-tenant quota values" +msgstr "" + +#: ./doc/common/section_cli_neutron-quotas.xml252(para) +msgid "To clear per-tenant quota limits, use the command:" +msgstr "" + +#: ./doc/common/section_cli_neutron-quotas.xml256(para) +msgid "" +"After you run this command, you can see that quota values for the tenant are" +" reset to the default values:" +msgstr "" + +#: ./doc/common/section_cli_nova_terminate.xml8(title) +msgid "Delete an instance" +msgstr "" + +#: ./doc/common/section_cli_nova_terminate.xml9(para) +msgid "When you no longer need an instance, you can delete it." +msgstr "" + +#: ./doc/common/section_cli_nova_terminate.xml11(para) +msgid "List all instances:" +msgstr "" + +#: ./doc/common/section_cli_nova_terminate.xml21(para) +msgid "" +"Use the following command to delete the newServer " +"instance, which is in ERROR state:" +msgstr "" + +#: ./doc/common/section_cli_nova_terminate.xml25(para) +msgid "The command does not notify that your server was deleted." +msgstr "" + +#: ./doc/common/section_cli_nova_terminate.xml26(para) +msgid "Instead, run the command:" +msgstr "" + +#: ./doc/common/section_cli_nova_terminate.xml35(para) +msgid "The deleted instance does not appear in the list." +msgstr "" + +#: ./doc/common/section_cli_keystone_example_usage.xml6(title) +msgid "keystone command-line client example usage" +msgstr "" + +#: ./doc/common/section_cli_keystone_example_usage.xml7(para) +msgid "" +"Before you can use keystone client commands, you must download and source an" +" OpenStack RC file. For information, see the OpenStack Admin User" +" Guide." +msgstr "" + +#: ./doc/common/section_cli_keystone_example_usage.xml10(para) +msgid "The keystone command-line client uses the following syntax:" +msgstr "" + +#: ./doc/common/section_cli_keystone_example_usage.xml12(replaceable) +msgid "PARAMETER" +msgstr "" + +#: ./doc/common/section_cli_keystone_example_usage.xml12(replaceable) +msgid "ARGUMENT" +msgstr "" + +#: ./doc/common/section_cli_keystone_example_usage.xml13(para) +msgid "" +"For example, you can run the and commands," +" as follows:" +msgstr "" + +#: ./doc/common/section_cli_keystone_example_usage.xml22(replaceable) +#: ./doc/common/section_cli_keystone_example_usage.xml23(replaceable) +msgid "token" +msgstr "" + +#: ./doc/common/section_cli_keystone_example_usage.xml22(replaceable) +#: ./doc/common/section_cli_keystone_example_usage.xml23(replaceable) +msgid "endpoint" +msgstr "" + +#: ./doc/common/section_cli_keystone_example_usage.xml31(replaceable) +msgid "id" +msgstr "" + +#: ./doc/common/section_cli_keystone_example_usage.xml34(para) +msgid "" +"For information about using the keystone client commands to create and " +"manage users, roles, and projects, see the OpenStack Admin User " +"Guide." +msgstr "" + +#: ./doc/common/section_cli_nova_volumes.xml8(title) +#: ./doc/common/section_dashboard_access.xml108(guilabel) +#: ./doc/common/section_dashboard_access.xml274(guilabel) +msgid "Volumes" +msgstr "" + +#: ./doc/common/section_cli_nova_volumes.xml9(para) +msgid "" +"Depending on the setup of your cloud provider, they may give you an endpoint" +" to use to manage volumes, or there may be an extension under the covers. In" +" either case, you can use the nova CLI to manage volumes." +msgstr "" + +#: ./doc/common/section_getstart_object-storage.xml5(title) +msgid "Object Storage service" +msgstr "" + +#: ./doc/common/section_getstart_object-storage.xml6(para) +msgid "" +"The Object Storage service is a highly scalable and durable multi-tenant " +"object storage system for large amounts of unstructured data at low cost " +"through a RESTful HTTP API." +msgstr "" + +#: ./doc/common/section_getstart_object-storage.xml9(para) +msgid "It includes the following components:" +msgstr "" + +#: ./doc/common/section_getstart_object-storage.xml12(para) +msgid "" +"Proxy servers (swift-proxy-" +"server). Accepts Object Storage API and raw HTTP requests to " +"upload files, modify metadata, and create containers. It also serves file or" +" container listings to web browsers. To improve performance, the proxy " +"server can use an optional cache usually deployed with memcache." +msgstr "" + +#: ./doc/common/section_getstart_object-storage.xml21(para) +msgid "" +"Account servers (swift-account-" +"server). Manage accounts defined with the Object Storage " +"service." +msgstr "" + +#: ./doc/common/section_getstart_object-storage.xml26(para) +msgid "" +"Container servers (swift-container-" +"server). Manage a mapping of containers, or folders, within the" +" Object Storage service." +msgstr "" + +#: ./doc/common/section_getstart_object-storage.xml32(para) +msgid "" +"Object servers (swift-object-" +"server). Manage actual objects, such as files, on the storage " +"nodes." +msgstr "" + +#: ./doc/common/section_getstart_object-storage.xml37(para) +msgid "" +"A number of periodic processes. Performs housekeeping tasks on the large " +"data store. The replication services ensure consistency and availability " +"through the cluster. Other periodic processes include auditors, updaters, " +"and reapers." +msgstr "" + +#: ./doc/common/section_getstart_object-storage.xml44(para) +msgid "" +"Configurable WSGI middleware that handles authentication. Usually the " +"Identity Service." +msgstr "" + +#: ./doc/common/section_rpc-for-networking.xml7(title) +#: ./doc/common/section_rpc.xml7(title) +msgid "Configure the Oslo RPC messaging system" +msgstr "" + +#: ./doc/common/section_rpc-for-networking.xml9(para) +msgid "" +"OpenStack projects use an open standard for messaging middleware known as " +"AMQP. This messaging middleware enables the OpenStack services that run on " +"multiple servers to talk to each other. OpenStack Oslo RPC supports three " +"implementations of AMQP: RabbitMQ, " +"Qpid, and ZeroMQ." +msgstr "" + +#: ./doc/common/section_rpc-for-networking.xml18(title) +#: ./doc/common/section_rpc.xml15(title) +msgid "Configure RabbitMQ" +msgstr "" + +#: ./doc/common/section_rpc-for-networking.xml20(para) +msgid "" +"OpenStack Oslo RPC uses RabbitMQ by default. Use " +"these options to configure the RabbitMQ message " +"system. The option is optional as long as " +"RabbitMQ is the default messaging system. " +"However, if it is included the configuration, you must set it to " +"neutron.openstack.common.rpc.impl_kombu." +msgstr "" + +#: ./doc/common/section_rpc-for-networking.xml34(para) +msgid "" +"Use these options to configure the RabbitMQ " +"messaging system. You can configure messaging communication for different " +"installation scenarios, tune retries for RabbitMQ, and define the size of " +"the RPC thread pool. To monitor notifications through RabbitMQ, you must set" +" the option to " +"neutron.notifier.rabbit_notifier in the " +"neutron.conf file:" +msgstr "" + +#: ./doc/common/section_rpc-for-networking.xml46(title) +#: ./doc/common/section_rpc.xml39(title) +msgid "Configure Qpid" +msgstr "" + +#: ./doc/common/section_rpc-for-networking.xml47(para) +msgid "" +"Use these options to configure the Qpid messaging" +" system for OpenStack Oslo RPC. Qpid is not the " +"default messaging system, so you must enable it by setting the " +" option in the neutron.conf" +" file:" +msgstr "" + +#: ./doc/common/section_rpc-for-networking.xml56(para) +msgid "" +"This critical option points the compute nodes to the " +"Qpid broker (server). Set the " +" option to the host name where the broker runs" +" in the neutron.conf file." +msgstr "" + +#: ./doc/common/section_rpc-for-networking.xml62(para) +#: ./doc/common/section_rpc.xml52(para) +msgid "" +"The option accepts a host name or IP " +"address value." +msgstr "" + +#: ./doc/common/section_rpc-for-networking.xml69(para) +#: ./doc/common/section_rpc.xml56(para) +msgid "" +"If the Qpid broker listens on a port other than " +"the AMQP default of 5672, you must set the " +" option to that value:" +msgstr "" + +#: ./doc/common/section_rpc-for-networking.xml78(para) +#: ./doc/common/section_rpc.xml61(para) +msgid "" +"If you configure the Qpid broker to require " +"authentication, you must add a user name and password to the configuration:" +msgstr "" + +#: ./doc/common/section_rpc-for-networking.xml87(para) +#: ./doc/common/section_rpc.xml66(para) +msgid "" +"By default, TCP is used as the transport. To enable SSL, set the " +" option:" +msgstr "" + +#: ./doc/common/section_rpc-for-networking.xml94(para) +msgid "" +"Use these additional options to configure the Qpid messaging driver for " +"OpenStack Oslo RPC. These options are used infrequently." +msgstr "" + +#: ./doc/common/section_rpc-for-networking.xml102(title) +#: ./doc/common/section_rpc.xml75(title) +msgid "Configure ZeroMQ" +msgstr "" + +#: ./doc/common/section_rpc-for-networking.xml103(para) +msgid "" +"Use these options to configure the ZeroMQ " +"messaging system for OpenStack Oslo RPC. ZeroMQ " +"is not the default messaging system, so you must enable it by setting the " +" option in the neutron.conf" +" file:" +msgstr "" + +#: ./doc/common/section_rpc-for-networking.xml112(title) +#: ./doc/common/section_rpc.xml85(title) +msgid "Configure messaging" +msgstr "" + +#: ./doc/common/section_rpc-for-networking.xml114(para) +msgid "" +"Use these common options to configure the " +"RabbitMQ, Qpid, and " +"ZeroMq messaging drivers:" +msgstr "" + +#: ./doc/common/section_fibrechannel.xml5(title) +msgid "Fibre Channel support in Compute" +msgstr "" + +#: ./doc/common/section_fibrechannel.xml6(para) +msgid "" +"Fibre Channel support in OpenStack Compute is remote block storage attached " +"to Compute nodes for VMs." +msgstr "" + +#: ./doc/common/section_fibrechannel.xml8(para) +msgid "" +"In the Grizzly release, Fibre Channel supported only the KVM hypervisor." +msgstr "" + +#: ./doc/common/section_fibrechannel.xml10(para) +msgid "" +"Compute and Block Storage for Fibre Channel do not support automatic zoning." +" Fibre Channel arrays must be pre-zoned or directly attached to the KVM " +"hosts." +msgstr "" + +#: ./doc/common/section_fibrechannel.xml14(title) +msgid "KVM host requirements" +msgstr "" + +#: ./doc/common/section_fibrechannel.xml15(para) +msgid "You must install these packages on the KVM host:" +msgstr "" + +#: ./doc/common/section_fibrechannel.xml18(para) +msgid "" +"sysfstools - Nova uses the systool " +"application in this package." +msgstr "" + +#: ./doc/common/section_fibrechannel.xml24(para) +msgid "" +"sg3-utils - Nova uses the sg_scan and " +"sginfo applications." +msgstr "" + +#: ./doc/common/section_fibrechannel.xml30(para) +msgid "Installing the multipath-tools package is optional." +msgstr "" + +#: ./doc/common/section_fibrechannel.xml34(title) +msgid "Install required packages" +msgstr "" + +#: ./doc/common/section_fibrechannel.xml35(para) +msgid "Use these commands to install the system packages:" +msgstr "" + +#: ./doc/common/section_fibrechannel.xml39(para) +msgid "For systems running Ubuntu:" +msgstr "" + +#: ./doc/common/section_fibrechannel.xml45(para) +msgid "For systems running Red Hat:" +msgstr "" + +#: ./doc/common/section_cli_help.xml6(title) +msgid "Get help for client commands" +msgstr "" + +#: ./doc/common/section_cli_help.xml7(para) +msgid "" +"To get usage information, including a list of commands with descriptions, " +"for a client, run the following command:" +msgstr "" + +#: ./doc/common/section_cli_help.xml9(replaceable) +#: ./doc/common/section_cli_help.xml59(replaceable) +msgid "CLIENT_NAME" +msgstr "" + +#: ./doc/common/section_cli_help.xml10(para) +msgid "" +"For example, to get help information for the swift client, run the following" +" command:" +msgstr "" + +#: ./doc/common/section_cli_help.xml54(para) +msgid "" +"Depending on your credentials, you might not have permission to use every " +"command." +msgstr "" + +#: ./doc/common/section_cli_help.xml57(para) +msgid "" +"After the command, you can enter a command name to get" +" help for that command, as follows:" +msgstr "" + +#: ./doc/common/section_cli_help.xml59(replaceable) +msgid "COMMAND_NAME" +msgstr "" + +#: ./doc/common/section_cli_help.xml60(para) +msgid "" +"For example, to get help for the glance command, enter the " +"following command:" +msgstr "" + +#: ./doc/common/section_cli_help.xml64(para) +msgid "" +"The command returns a description of the command and its positional and " +"optional arguments:" +msgstr "" + +#: ./doc/common/ch_getstart.xml6(title) +msgid "Get started with OpenStack" +msgstr "" + +#: ./doc/common/ch_getstart.xml8(para) +msgid "" +"The OpenStack project is an open source cloud computing platform for all " +"types of clouds, which aims to be simple to implement, massively scalable, " +"and feature rich. Developers and cloud computing technologists from around " +"the world create the OpenStack project." +msgstr "" + +#: ./doc/common/ch_getstart.xml13(para) +msgid "" +"OpenStack provides an Infrastructure as a Service (IaaS) solution through a " +"set of interrelated services. Each service offers an application programming" +" interface (API) that facilitates this integration. Depending on your needs," +" you can install some or all services." +msgstr "" + +#: ./doc/common/ch_getstart.xml18(para) +msgid "" +"The following table describes the OpenStack services that make up the " +"OpenStack architecture:" +msgstr "" + +#: ./doc/common/ch_getstart.xml21(caption) +#: ./doc/common/ch_getstart.xml154(title) +msgid "OpenStack services" +msgstr "" + +#: ./doc/common/ch_getstart.xml27(th) +#: ./doc/common/section_keystone-concepts.xml89(emphasis) +msgid "Service" +msgstr "" + +#: ./doc/common/ch_getstart.xml28(th) +msgid "Project name" +msgstr "" + +#: ./doc/common/ch_getstart.xml39(link) +msgid "Horizon" +msgstr "" + +#: ./doc/common/ch_getstart.xml40(td) +msgid "" +"Provides a web-based self-service portal to interact with underlying " +"OpenStack services, such as launching an instance, assigning IP addresses " +"and configuring access controls." +msgstr "" + +#: ./doc/common/ch_getstart.xml48(link) +msgid "Compute" +msgstr "" + +#: ./doc/common/ch_getstart.xml51(link) +msgid "Nova" +msgstr "" + +#: ./doc/common/ch_getstart.xml52(td) +msgid "" +"Manages the lifecycle of compute instances in an OpenStack environment. " +"Responsibilities include spawning, scheduling and decomissioning of machines" +" on demand." +msgstr "" + +#: ./doc/common/ch_getstart.xml60(link) +msgid "Networking" +msgstr "" + +#: ./doc/common/ch_getstart.xml63(link) +msgid "Neutron" +msgstr "" + +#: ./doc/common/ch_getstart.xml64(td) +msgid "" +"Enables network connectivity as a service for other OpenStack services, such" +" as OpenStack Compute. Provides an API for users to define networks and the " +"attachments into them. Has a pluggable architecture that supports many " +"popular networking vendors and technologies." +msgstr "" + +#: ./doc/common/ch_getstart.xml71(th) +msgid "Storage" +msgstr "" + +#: ./doc/common/ch_getstart.xml75(link) +msgid "Object Storage" +msgstr "" + +#: ./doc/common/ch_getstart.xml78(link) +msgid "Swift" +msgstr "" + +#: ./doc/common/ch_getstart.xml80(glossterm) +msgid "RESTful" +msgstr "" + +#: ./doc/common/ch_getstart.xml79(td) +msgid "" +"Stores and retrieves arbitrary unstructured data objects via a " +", HTTP based API. It is highly fault tolerant with its data " +"replication and scale out architecture. Its implementation is not like a " +"file server with mountable directories." +msgstr "" + +#: ./doc/common/ch_getstart.xml89(link) +msgid "Block Storage" +msgstr "" + +#: ./doc/common/ch_getstart.xml92(link) +msgid "Cinder" +msgstr "" + +#: ./doc/common/ch_getstart.xml93(td) +msgid "" +"Provides persistent block storage to running instances. Its pluggable driver" +" architecture facilitates the creation and management of block storage " +"devices." +msgstr "" + +#: ./doc/common/ch_getstart.xml98(th) +msgid "Shared services" +msgstr "" + +#: ./doc/common/ch_getstart.xml102(link) +msgid "Identity Service" +msgstr "" + +#: ./doc/common/ch_getstart.xml105(link) +msgid "Keystone" +msgstr "" + +#: ./doc/common/ch_getstart.xml106(td) +msgid "" +"Provides an authentication and authorization service for other OpenStack " +"services. Provides a catalog of endpoints for all OpenStack services." +msgstr "" + +#: ./doc/common/ch_getstart.xml113(link) +msgid "Image Service" +msgstr "" + +#: ./doc/common/ch_getstart.xml116(link) +msgid "Glance" +msgstr "" + +#: ./doc/common/ch_getstart.xml117(td) +msgid "" +"Stores and retrieves virtual machine disk images. OpenStack Compute makes " +"use of this during instance provisioning." +msgstr "" + +#: ./doc/common/ch_getstart.xml126(link) +msgid "Telemetry Service" +msgstr "" + +#: ./doc/common/ch_getstart.xml129(link) +msgid "Ceilometer" +msgstr "" + +#: ./doc/common/ch_getstart.xml130(td) +msgid "" +"Monitors and meters the OpenStack cloud for billing, benchmarking, " +"scalability, and statistical purposes." +msgstr "" + +#: ./doc/common/ch_getstart.xml134(th) +msgid "Higher-level services" +msgstr "" + +#: ./doc/common/ch_getstart.xml138(link) +msgid "Orchestration Service" +msgstr "" + +#: ./doc/common/ch_getstart.xml141(link) +msgid "Heat" +msgstr "" + +#: ./doc/common/ch_getstart.xml142(td) +msgid "" +"Orchestrates multiple composite cloud applications by using either the " +"native HOT template format or the AWS CloudFormation template format, " +"through both an OpenStack-native REST API and a CloudFormation-compatible " +"Query API." +msgstr "" + +#: ./doc/common/ch_getstart.xml155(para) +msgid "This section describes OpenStack services in detail." +msgstr "" + +#: ./doc/common/ch_getstart.xml173(title) +msgid "Feedback" +msgstr "" + +#: ./doc/common/section_getstart_compute.xml5(title) +msgid "Compute service" +msgstr "" + +#: ./doc/common/section_getstart_compute.xml6(para) +msgid "" +"The Compute service is a cloud computing fabric controller, which is the " +"main part of an IaaS system. Use it to host and manage cloud computing " +"systems. The main modules are implemented in Python." +msgstr "" + +#: ./doc/common/section_getstart_compute.xml10(para) +msgid "" +"Compute interacts with the Identity Service for authentication, Image " +"Service for images, and the Dashboard for the user and administrative " +"interface. Access to images is limited by project and by user; quotas are " +"limited per project (for example, the number of instances). The Compute " +"service scales horizontally on standard hardware, and downloads images to " +"launch instances as required." +msgstr "" + +#: ./doc/common/section_getstart_compute.xml17(para) +msgid "" +"The Compute Service is made up of the following functional areas and their " +"underlying components:" +msgstr "" + +#: ./doc/common/section_getstart_compute.xml20(title) +msgid "API" +msgstr "" + +#: ./doc/common/section_getstart_compute.xml22(para) +msgid "" +"nova-api service. Accepts and " +"responds to end user compute API calls. Supports the OpenStack Compute API, " +"the Amazon EC2 API, and a special Admin API for privileged users to perform " +"administrative actions. Also, initiates most orchestration activities, such " +"as running an instance, and enforces some policies." +msgstr "" + +#: ./doc/common/section_getstart_compute.xml30(para) +msgid "" +"nova-api-metadata service. " +"Accepts metadata requests from instances. The nova-api-metadata service is generally only used when you " +"run in multi-host mode with nova-" +"network installations. For details, see Metadata service in the Cloud Administrator" +" Guide." +msgstr "" + +#: ./doc/common/section_getstart_compute.xml39(para) +msgid "" +"On Debian systems, it is included in the nova-" +"api package, and can be selected through " +"debconf." +msgstr "" + +#: ./doc/common/section_getstart_compute.xml45(title) +msgid "Compute core" +msgstr "" + +#: ./doc/common/section_getstart_compute.xml47(para) +msgid "" +"nova-compute process. A worker " +"daemon that creates and terminates virtual machine instances through " +"hypervisor APIs. For example, XenAPI for XenServer/XCP, libvirt for KVM or " +"QEMU, VMwareAPI for VMware, and so on. The process by which it does so is " +"fairly complex but the basics are simple: Accept actions from the queue and " +"perform a series of system commands, like launching a KVM instance, to carry" +" them out while updating state in the database." +msgstr "" + +#: ./doc/common/section_getstart_compute.xml58(para) +msgid "" +"nova-scheduler process. " +"Conceptually the simplest piece of code in Compute. Takes a virtual machine " +"instance request from the queue and determines on which compute server host " +"it should run." +msgstr "" + +#: ./doc/common/section_getstart_compute.xml64(para) +msgid "" +"nova-conductor module. Mediates " +"interactions between nova-compute" +" and the database. Aims to eliminate direct accesses to the cloud database " +"made by nova-compute. The " +"nova-conductor module scales " +"horizontally. However, do not deploy it on any nodes where nova-compute runs. For more information, see " +"A new Nova service: nova-conductor." +msgstr "" + +#: ./doc/common/section_getstart_compute.xml79(title) +msgid "Networking for VMs" +msgstr "" + +#: ./doc/common/section_getstart_compute.xml81(para) +msgid "" +"nova-network worker daemon. " +"Similar to nova-compute, it " +"accepts networking tasks from the queue and performs tasks to manipulate the" +" network, such as setting up bridging interfaces or changing iptables rules." +" This functionality is being migrated to OpenStack Networking, which is a " +"separate OpenStack service." +msgstr "" + +#: ./doc/common/section_getstart_compute.xml90(para) +msgid "" +"nova-dhcpbridge script. Tracks IP" +" address leases and records them in the database by using the dnsmasq " +"dhcp-script facility. This functionality is being " +"migrated to OpenStack Networking. OpenStack Networking provides a different " +"script." +msgstr "" + +#: ./doc/common/section_getstart_compute.xml100(title) +msgid "Console interface" +msgstr "" + +#: ./doc/common/section_getstart_compute.xml102(para) +msgid "" +"nova-consoleauth daemon. " +"Authorizes tokens for users that console proxies provide. See nova-novncproxy and nova-xvpnvcproxy. This service must be " +"running for console proxies to work. Many proxies of either type can be run " +"against a single nova-consoleauth" +" service in a cluster configuration. For information, see About nova-consoleauth." +msgstr "" + +#: ./doc/common/section_getstart_compute.xml115(para) +msgid "" +"nova-novncproxy daemon. Provides " +"a proxy for accessing running instances through a VNC connection. Supports " +"browser-based novnc clients." +msgstr "" + +#: ./doc/common/section_getstart_compute.xml121(para) +msgid "" +"nova-console daemon. Deprecated " +"for use with Grizzly. Instead, the nova-" +"xvpnvncproxy is used." +msgstr "" + +#: ./doc/common/section_getstart_compute.xml127(para) +msgid "" +"nova-xvpnvncproxy daemon. A proxy" +" for accessing running instances through a VNC connection. Supports a Java " +"client specifically designed for OpenStack." +msgstr "" + +#: ./doc/common/section_getstart_compute.xml133(para) +msgid "" +"nova-cert daemon. Manages x509 " +"certificates." +msgstr "" + +#: ./doc/common/section_getstart_compute.xml137(para) +msgid "" +"In Debian, a unique nova-consoleproxy package provides " +"the nova-novncproxy, nova-" +"spicehtml5proxy, and nova-xvpvncproxy packages." +" To select packages, edit the /etc/default/nova-" +"consoleproxy file or use the debconf " +"interface. You can also manually edit the /etc/default/nova-" +"consoleproxy file and stop and start the console daemons." +msgstr "" + +#: ./doc/common/section_getstart_compute.xml148(title) +msgid "Image management (EC2 scenario)" +msgstr "" + +#: ./doc/common/section_getstart_compute.xml150(para) +msgid "" +"nova-objectstore daemon. Provides" +" an S3 interface for registering images with the Image Service. Mainly used " +"for installations that must support euca2ools. The euca2ools tools talk to " +"nova-objectstore in S3 language, and nova-objectstore translates S3 requests into Image Service " +"requests." +msgstr "" + +#: ./doc/common/section_getstart_compute.xml160(para) +msgid "" +"euca2ools client. A set of command-line interpreter commands for managing " +"cloud resources. Though not an OpenStack module, you can configure " +"nova-api to support this EC2 " +"interface. For more information, see the Eucalyptus 2.0 Documentation." +msgstr "" + +#: ./doc/common/section_getstart_compute.xml170(title) +msgid "Command-line clients and other interfaces" +msgstr "" + +#: ./doc/common/section_getstart_compute.xml172(para) +msgid "" +"nova client. Enables users to submit commands as a tenant administrator or " +"end user." +msgstr "" + +#: ./doc/common/section_getstart_compute.xml176(para) +msgid "nova-manage client. Enables cloud administrators to submit commands." +msgstr "" + +#: ./doc/common/section_getstart_compute.xml181(title) +msgid "Other components" +msgstr "" + +#: ./doc/common/section_getstart_compute.xml183(para) +msgid "" +"The queue. A central hub for passing messages between daemons. Usually " +"implemented with RabbitMQ, " +"but could be any AMPQ message queue, such as Apache Qpid or Zero MQ." +msgstr "" + +#: ./doc/common/section_getstart_compute.xml192(para) +msgid "" +"SQL database. Stores most build-time and runtime states for a cloud " +"infrastructure. Includes instance types that are available for use, " +"instances in use, available networks, and projects. Theoretically, OpenStack" +" Compute can support any database that SQL-Alchemy supports, but the only " +"databases widely used are sqlite3 databases (only appropriate for test and " +"development work), MySQL, and PostgreSQL." +msgstr "" + +#: ./doc/common/section_getstart_compute.xml201(para) +msgid "" +"The Compute Service interacts with other OpenStack services: Identity " +"Service for authentication, Image Service for images, and the OpenStack " +"dashboard for a web interface." +msgstr "" + +#: ./doc/common/section_compute-configure-console.xml5(title) +msgid "Configure remote console access" +msgstr "" + +#. +#: ./doc/common/section_compute-configure-console.xml7(para) +msgid "" +"To provide a remote console or remote desktop access to guest virtual " +"machines, use VNC or SPICE HTML5 through either the OpenStack dashboard or " +"the command line. Best practice is to select one or the other to run." +msgstr "" + +#: ./doc/common/section_xapi-resize-setup.xml7(title) +msgid "Modify Dom0 for resize/migration support" +msgstr "" + +#: ./doc/common/section_xapi-resize-setup.xml8(para) +msgid "To resize servers with XenServer and XCP, you must:" +msgstr "" + +#: ./doc/common/section_xapi-resize-setup.xml11(para) +msgid "" +"Establish a root trust between all hypervisor nodes of your deployment:" +msgstr "" + +#: ./doc/common/section_xapi-resize-setup.xml13(para) +msgid "" +"To do so, generate an ssh key-pair with the command. Ensure" +" that each of your dom0's authorized_keys file (located" +" in /root/.ssh/authorized_keys) contains the public key" +" fingerprint (located in /root/.ssh/id_rsa.pub)." +msgstr "" + +#: ./doc/common/section_xapi-resize-setup.xml22(para) +msgid "" +"Provide an /images mount point to the dom0 for your " +"hypervisor:" +msgstr "" + +#: ./doc/common/section_xapi-resize-setup.xml24(para) +msgid "" +"Dom0 space is at a premium so creating a directory in dom0 is potentially " +"dangerous and likely to fail especially when you resize large servers. The " +"least you can do is to symlink /images to your local " +"storage SR. The following instructions work for an English-based " +"installation of XenServer (and XCP) and in the case of ext3-based SR (with " +"which the resize functionality is known to work correctly)." +msgstr "" + +#: ./doc/common/section_cli_nova_sshkeys.xml6(title) +msgid "Add keypair" +msgstr "" + +#: ./doc/common/section_cli_nova_sshkeys.xml7(para) +msgid "" +"Create at least one keypair for each project. If you have generated a " +"keypair with an external tool, you can import it into OpenStack. The keypair" +" can be used for multiple instances that belong to a project." +msgstr "" + +#: ./doc/common/section_cli_nova_sshkeys.xml13(para) +msgid "Create a key." +msgstr "" + +#: ./doc/common/section_cli_nova_sshkeys.xml14(para) +msgid "" +"To create a mykey key that you can associate with " +"instances, run the following command:" +msgstr "" + +#: ./doc/common/section_cli_nova_sshkeys.xml17(para) +msgid "" +"Save the mykey.pem file to a secure location. It " +"enables root access to any instances with which the mykey" +" key is associated." +msgstr "" + +#: ./doc/common/section_cli_nova_sshkeys.xml22(para) +msgid "Alternatively, you can import a keypair." +msgstr "" + +#: ./doc/common/section_cli_nova_sshkeys.xml23(para) +msgid "" +"To import an existing public key, mykey.pub, and " +"associate it with the mykey key, run the following " +"command:" +msgstr "" + +#: ./doc/common/section_cli_nova_sshkeys.xml28(para) +msgid "" +"You must have the matching private key to access instances that are " +"associated with this key." +msgstr "" + +#: ./doc/common/section_dashboard-configure-https.xml4(title) +msgid "Configure the dashboard for HTTPS" +msgstr "" + +#: ./doc/common/section_dashboard-configure-https.xml5(para) +#: ./doc/common/section_dashboard-configure.xml10(para) +msgid "" +"You can configure the dashboard for a secured HTTPS deployment. While the " +"standard installation uses a non-encrypted HTTP channel, you can enable SSL " +"support for the dashboard." +msgstr "" + +#: ./doc/common/section_dashboard-configure-https.xml9(para) +msgid "" +"The following example uses the domain, \"http://openstack.example.com.\" Use" +" a domain that fits your current setup." +msgstr "" + +#: ./doc/common/section_dashboard-configure-https.xml13(para) +msgid "" +"In/etc/openstack-dashboard/local_settings.py update the" +" following directives:" +msgstr "" + +#: ./doc/common/section_dashboard-configure-https.xml19(para) +msgid "" +"The first option is required to enable HTTPS. The other recommended settings" +" defend against cross-site scripting and require HTTPS." +msgstr "" + +#: ./doc/common/section_dashboard-configure-https.xml24(para) +msgid "" +"Edit /etc/apache2/ports.conf and add the following " +"line:" +msgstr "" + +#: ./doc/common/section_dashboard-configure-https.xml30(para) +msgid "" +"Edit /etc/apache2/conf.d/openstack-dashboard.conf:" +msgstr "" + +#: ./doc/common/section_dashboard-configure-https.xml33(para) +msgid "Before:" +msgstr "" + +#: ./doc/common/section_dashboard-configure-https.xml46(para) +msgid "After:" +msgstr "" + +#: ./doc/common/section_dashboard-configure-https.xml87(para) +msgid "" +"In this configuration, Apache http server listens on the port 443 and " +"redirects all the hits to the HTTPS protocol for all the non-secured " +"requests. The secured section defines the private key, public key, and " +"certificate to use." +msgstr "" + +#: ./doc/common/section_dashboard-configure-https.xml94(para) +msgid "Restart Apache http server. For Debian/Ubuntu/SUSE:" +msgstr "" + +#: ./doc/common/section_dashboard-configure-https.xml96(para) +msgid "Or for Fedora/RHEL/CentOS:" +msgstr "" + +#: ./doc/common/section_dashboard-configure-https.xml98(para) +#: ./doc/common/section_dashboard-configure-http.xml32(para) +msgid "Next, restart memcached:" +msgstr "" + +#: ./doc/common/section_dashboard-configure-https.xml100(para) +msgid "" +"If you try to access the dashboard through HTTP, the browser redirects you " +"to the HTTPS page." +msgstr "" + +#. When image changes, this message will be marked fuzzy or untranslated for +#. you. +#. It doesn't matter what you translate it to: it's not used at all. +#: ./doc/common/section_getstart_logical_arch.xml34(None) +msgid "" +"@@image: 'figures/openstack-arch-havana-logical-v1.jpg'; " +"md5=e7acaaee72722626b045eda3fae81841" +msgstr "" + +#: ./doc/common/section_getstart_logical_arch.xml5(title) +#: ./doc/common/section_getstart_logical_arch.xml29(title) +msgid "Logical architecture" +msgstr "" + +#: ./doc/common/section_getstart_logical_arch.xml6(para) +msgid "" +"To design, install, and configure a cloud, cloud administrators must " +"understand the logical architecture." +msgstr "" + +#: ./doc/common/section_getstart_logical_arch.xml8(para) +msgid "OpenStack modules are one of the following types:" +msgstr "" + +#: ./doc/common/section_getstart_logical_arch.xml11(para) +msgid "" +"Daemon. Runs as a daemon. On Linux platforms, a daemon is usually installed " +"as a service." +msgstr "" + +#: ./doc/common/section_getstart_logical_arch.xml15(para) +msgid "" +"Script. Installs and tests of a virtual environment. For example, the " +"run_tests.sh script installs and optionally tests a virtual " +"environment for a service." +msgstr "" + +#: ./doc/common/section_getstart_logical_arch.xml20(para) +msgid "" +"Command-line interface (CLI). Enables users to submit API calls to OpenStack" +" services through easy-to-use commands." +msgstr "" + +#: ./doc/common/section_getstart_logical_arch.xml25(para) +msgid "" +"The following diagram shows the most common, but not the only, architecture " +"for an OpenStack cloud:" +msgstr "" + +#: ./doc/common/section_getstart_logical_arch.xml38(para) +msgid "" +"As in , end users can interact through the " +"dashboard, CLIs, and APIs. All services authenticate through a common " +"Identity Service and individual services interact with each other through " +"public APIs, except where privileged administrator commands are necessary." +msgstr "" + +#. When image changes, this message will be marked fuzzy or untranslated for +#. you. +#. It doesn't matter what you translate it to: it's not used at all. +#: ./doc/common/section_keystone-concepts.xml132(None) +#: ./doc/common/section_keystone-concepts.xml137(None) +msgid "" +"@@image: 'figures/SCH_5002_V00_NUAC-Keystone.png'; " +"md5=657851bcb185467ac322b4b4008fdf39" +msgstr "" + +#: ./doc/common/section_keystone-concepts.xml7(title) +msgid "Identity Service concepts" +msgstr "" + +#: ./doc/common/section_keystone-concepts.xml8(para) +msgid "" +"The Identity Service performs the following " +"functions:" +msgstr "" + +#: ./doc/common/section_keystone-concepts.xml12(para) +msgid "User management. Tracks users and their permissions." +msgstr "" + +#: ./doc/common/section_keystone-concepts.xml16(para) +msgid "" +"Service catalog. " +"Provides a catalog of available services with their API endpoints." +msgstr "" + +#: ./doc/common/section_keystone-concepts.xml21(para) +msgid "" +"To understand the Identity Service, you must understand the following " +"concepts:" +msgstr "" + +#: ./doc/common/section_keystone-concepts.xml25(emphasis) +msgid "User" +msgstr "" + +#: ./doc/common/section_keystone-concepts.xml27(para) +msgid "" +"Digital representation of a person, system, or service who uses OpenStack " +"cloud services. The Identity Service validates that incoming requests are " +"made by the user who claims to be making the call. Users have a login and " +"may be assigned tokens to access resources. Users can be directly assigned " +"to a particular tenant and behave as if they are contained in that tenant." +msgstr "" + +#: ./doc/common/section_keystone-concepts.xml38(emphasis) +msgid "Credentials" +msgstr "" + +#: ./doc/common/section_keystone-concepts.xml40(para) +msgid "" +"Data that is known only by a user that proves who they are. In the Identity " +"Service, examples are: User name and password, user name and API key, or an " +"authentication token provided by the Identity Service." +msgstr "" + +#: ./doc/common/section_keystone-concepts.xml49(emphasis) +msgid "Authentication" +msgstr "" + +#: ./doc/common/section_keystone-concepts.xml51(para) +msgid "" +"The act of confirming the identity of a user. The Identity Service confirms " +"an incoming request by validating a set of credentials supplied by the user." +msgstr "" + +#: ./doc/common/section_keystone-concepts.xml55(para) +msgid "" +"These credentials are initially a user name and password or a user name and " +"API key. In response to these credentials, the Identity Service issues an " +"authentication token to the user, which the user provides in subsequent " +"requests." +msgstr "" + +#: ./doc/common/section_keystone-concepts.xml63(emphasis) +msgid "Token" +msgstr "" + +#: ./doc/common/section_keystone-concepts.xml65(para) +msgid "" +"An arbitrary bit of text that is used to access resources. Each token has a " +"scope which describes which resources are accessible with it. A token may be" +" revoked at any time and is valid for a finite duration." +msgstr "" + +#: ./doc/common/section_keystone-concepts.xml70(para) +msgid "" +"While the Identity Service supports token-based authentication in this " +"release, the intention is for it to support additional protocols in the " +"future. The intent is for it to be an integration service foremost, and not " +"aspire to be a full-fledged identity store and management solution." +msgstr "" + +#: ./doc/common/section_keystone-concepts.xml80(emphasis) +msgid "Tenant" +msgstr "" + +#: ./doc/common/section_keystone-concepts.xml82(para) +msgid "" +"A container used to group or isolate resources and/or identity objects. " +"Depending on the service operator, a tenant may map to a customer, account, " +"organization, or project." +msgstr "" + +#: ./doc/common/section_keystone-concepts.xml91(para) +msgid "" +"An OpenStack service, such as Compute (Nova), Object Storage (Swift), or " +"Image Service (Glance). Provides one or more endpoints through which users " +"can access resources and perform operations." +msgstr "" + +#: ./doc/common/section_keystone-concepts.xml99(emphasis) +msgid "Endpoint" +msgstr "" + +#: ./doc/common/section_keystone-concepts.xml101(para) +msgid "" +"A network-accessible address, usually described by a URL, from where you " +"access a service. If using an extension for templates, you can create an " +"endpoint template, which represents the templates of all the consumable " +"services that are available across the regions." +msgstr "" + +#: ./doc/common/section_keystone-concepts.xml110(emphasis) +msgid "Role" +msgstr "" + +#: ./doc/common/section_keystone-concepts.xml112(para) +msgid "" +"A personality that a user assumes that enables them to perform a specific " +"set of operations. A role includes a set of rights and privileges. A user " +"assuming that role inherits those rights and privileges." +msgstr "" + +#: ./doc/common/section_keystone-concepts.xml117(para) +msgid "" +"In the Identity Service, a token that is issued to a user includes the list " +"of roles that user has. Services that are being called by that user " +"determine how they interpret the set of roles a user has and to which " +"operations or resources each role grants access." +msgstr "" + +#: ./doc/common/section_keystone-concepts.xml126(para) +msgid "The following diagram shows the Identity Service process flow:" +msgstr "" + +#: ./doc/common/section_kvm_enable.xml6(title) +msgid "Enable KVM" +msgstr "" + +#: ./doc/common/section_kvm_enable.xml7(para) +msgid "" +"To perform these steps, you must be logged in as the " +"root user." +msgstr "" + +#: ./doc/common/section_kvm_enable.xml11(para) +msgid "" +"To determine whether the svm or vmx " +"CPU extensions are present, run this command:" +msgstr "" + +#: ./doc/common/section_kvm_enable.xml15(para) +msgid "" +"This command generates output if the CPU is hardware-virtualization capable." +" Even if output is shown, you might still need to enable virtualization in " +"the system BIOS for full support." +msgstr "" + +#: ./doc/common/section_kvm_enable.xml19(para) +msgid "" +"If no output appears, consult your system documentation to ensure that your " +"CPU and motherboard support hardware virtualization. Verify that any " +"relevant hardware virtualization options are enabled in the system BIOS." +msgstr "" + +#: ./doc/common/section_kvm_enable.xml24(para) +msgid "" +"The BIOS for each manufacturer is different. If you must enable " +"virtualization in the BIOS, look for an option containing the words " +"virtualization, VT, " +"VMX, or SVM." +msgstr "" + +#: ./doc/common/section_kvm_enable.xml32(para) +msgid "" +"To list the loaded kernel modules and verify that the kvm" +" modules are loaded, run this command:" +msgstr "" + +#: ./doc/common/section_kvm_enable.xml36(para) +msgid "" +"If the output includes kvm_intel or " +"kvm_amd, the kvm hardware " +"virtualization modules are loaded and your kernel meets the module " +"requirements for OpenStack Compute." +msgstr "" + +#: ./doc/common/section_kvm_enable.xml43(para) +msgid "" +"If the output does not show that the kvm module is " +"loaded, run this command to load it:" +msgstr "" + +#: ./doc/common/section_kvm_enable.xml47(para) +msgid "Run the command for your CPU. For Intel, run this command:" +msgstr "" + +#: ./doc/common/section_kvm_enable.xml50(para) +msgid "For AMD, run this command:" +msgstr "" + +#: ./doc/common/section_kvm_enable.xml52(para) +msgid "" +"Because a KVM installation can change user group membership, you might need " +"to log in again for changes to take effect." +msgstr "" + +#: ./doc/common/section_kvm_enable.xml55(para) +msgid "" +"If the kernel modules do not load automatically, use the procedures listed " +"in these subsections." +msgstr "" + +#: ./doc/common/section_kvm_enable.xml59(para) +msgid "" +"If the checks indicate that required hardware virtualization support or " +"kernel modules are disabled or unavailable, you must either enable this " +"support on the system or find a system with this support." +msgstr "" + +#: ./doc/common/section_kvm_enable.xml64(para) +msgid "" +"Some systems require that you enable VT support in the system BIOS. If you " +"believe your processor supports hardware acceleration but the previous " +"command did not produce output, reboot your machine, enter the system BIOS, " +"and enable the VT option." +msgstr "" + +#: ./doc/common/section_kvm_enable.xml70(para) +msgid "" +"If KVM acceleration is not supported, configure Compute to use a different " +"hypervisor, such as QEMU or Xen." +msgstr "" + +#: ./doc/common/section_kvm_enable.xml76(para) +msgid "" +"These procedures help you load the kernel modules for Intel-based and AMD-" +"based processors if they do not load automatically during KVM installation." +msgstr "" + +#: ./doc/common/section_kvm_enable.xml80(title) +msgid "Intel-based processors" +msgstr "" + +#: ./doc/common/section_kvm_enable.xml81(para) +msgid "" +"If your compute host is Intel-based, run these commands as root to load the " +"kernel modules:" +msgstr "" + +#: ./doc/common/section_kvm_enable.xml85(para) +msgid "" +"Add these lines to the /etc/modules file so that these " +"modules load on reboot:" +msgstr "" + +#: ./doc/common/section_kvm_enable.xml91(title) +msgid "AMD-based processors" +msgstr "" + +#: ./doc/common/section_kvm_enable.xml92(para) +msgid "" +"If your compute host is AMD-based, run these commands as root to load the " +"kernel modules:" +msgstr "" + +#: ./doc/common/section_kvm_enable.xml96(para) +msgid "" +"Add these lines to /etc/modules file so that these " +"modules load on reboot:" +msgstr "" + +#: ./doc/common/section_xapi-install-plugins.xml7(title) +msgid "Install the XenAPI plug-ins" +msgstr "" + +#: ./doc/common/section_xapi-install-plugins.xml8(para) +msgid "" +"When you use Xen as the hypervisor for OpenStack Compute, you can install a " +"Python script (or any executable) on the host side, and call that through " +"the XenAPI. These scripts are called plug-ins. The XenAPI plug-ins live in " +"the nova code repository. These plug-ins have to be copied to the Dom0 for " +"the hypervisor, to the appropriate directory, where xapi can find them. " +"There are several options for the installation. The important thing is to " +"ensure that the version of the plug-ins are in line with the nova " +"installation by only installing plug-ins from a matching nova repository." +msgstr "" + +#: ./doc/common/section_xapi-install-plugins.xml19(title) +msgid "Manually install the plug-in" +msgstr "" + +#: ./doc/common/section_xapi-install-plugins.xml22(para) +msgid "Create temporary files/directories:" +msgstr "" + +#: ./doc/common/section_xapi-install-plugins.xml27(para) +msgid "" +"Get the source from github. The example assumes the master branch is used. " +"Amend the URL to match the version being used:" +msgstr "" + +#: ./doc/common/section_xapi-install-plugins.xml32(para) +msgid "" +"(Alternatively) To use the official Ubuntu packages, use the following " +"commands to get the nova code base:" +msgstr "" + +#: ./doc/common/section_xapi-install-plugins.xml39(para) +msgid "Copy the plug-ins to the hypervisor:" +msgstr "" + +#: ./doc/common/section_xapi-install-plugins.xml44(para) +msgid "Remove the temporary files/directories:" +msgstr "" + +#: ./doc/common/section_xapi-install-plugins.xml51(title) +msgid "Package a XenServer supplemental pack" +msgstr "" + +#: ./doc/common/section_xapi-install-plugins.xml52(para) +msgid "" +"Follow these steps to produce a supplemental pack from the nova sources, and" +" package it as a XenServer supplemental pack." +msgstr "" + +#: ./doc/common/section_xapi-install-plugins.xml57(para) +msgid "" +"Create RPM packages. Given you have the nova sources. Use one of the methods" +" in :" +msgstr "" + +#: ./doc/common/section_xapi-install-plugins.xml62(para) +msgid "" +"These commands leave an .rpm file in the " +"rpmbuild/RPMS/noarch/ directory." +msgstr "" + +#: ./doc/common/section_xapi-install-plugins.xml68(para) +msgid "" +"Pack the RPM packages to a Supplemental Pack, using the XenServer DDK (the " +"following command should be issued on the XenServer DDK virtual appliance, " +"after the produced rpm file has been copied over):" +msgstr "" + +#: ./doc/common/section_xapi-install-plugins.xml81(para) +msgid "" +"This command produces an .iso file in the output " +"directory specified. Copy that file to the hypervisor." +msgstr "" + +#: ./doc/common/section_xapi-install-plugins.xml87(para) +msgid "Install the Supplemental Pack. Log in to the hypervisor, and issue:" +msgstr "" + +#: ./doc/common/section_dashboard-configure-vnc-window.xml6(title) +msgid "Change the size of the dashboard VNC window" +msgstr "" + +#: ./doc/common/section_dashboard-configure-vnc-window.xml7(para) +msgid "" +"The _detail_vnc.html file defines the size of the VNC " +"window. To change the window size, edit this file." +msgstr "" + +#: ./doc/common/section_dashboard-configure-vnc-window.xml12(para) +msgid "" +"Edit " +"/usr/share/pyshared/horizon/dashboards/nova/instances/templates/instances/_detail_vnc.html." +msgstr "" + +#: ./doc/common/section_dashboard-configure-vnc-window.xml16(para) +msgid "" +"Modify the width and height " +"parameters, as follows:" +msgstr "" + +#: ./doc/common/section_cli_nova_fileinjection.xml10(title) +msgid "Inject files into instances" +msgstr "" + +#: ./doc/common/section_cli_nova_fileinjection.xml11(para) +msgid "" +"You can inject local files into the instance file system when you launch an " +"instance." +msgstr "" + +#: ./doc/common/section_cli_nova_fileinjection.xml13(para) +msgid "" +"Use the --file dst-path=src-path parameter on the " +"nova command." +msgstr "" + +#: ./doc/common/section_cli_nova_fileinjection.xml15(para) +msgid "You can inject up to five files." +msgstr "" + +#: ./doc/common/section_cli_nova_fileinjection.xml16(para) +msgid "" +"For example, you might inject the " +"special_authorized_keysfile file into the instance " +"rather than using the regular ssh key injection." +msgstr "" + +#: ./doc/common/section_cli_nova_fileinjection.xml19(para) +msgid "Run the following command:" +msgstr "" + +#: ./doc/common/section_keystone_certificates-for-pki.xml7(title) +msgid "Certificates for PKI" +msgstr "" + +#: ./doc/common/section_keystone_certificates-for-pki.xml8(para) +msgid "" +"PKI stands for Public Key Infrastructure. Tokens are documents, " +"cryptographically signed using the X509 standard. In order to work correctly" +" token generation requires a public/private key pair. The public key must be" +" signed in an X509 certificate, and the certificate used to sign it must be " +"available as Certificate Authority (CA) certificate. These files can be " +"generated either using the utility, or externally " +"generated. The files need to be in the locations specified by the top level " +"Identity Service configuration file keystone.conf as " +"specified in the above section. Additionally, the private key should only be" +" readable by the system user that will run the Identity Service." +msgstr "" + +#: ./doc/common/section_keystone_certificates-for-pki.xml23(para) +msgid "" +"The certificates can be world readable, but the private key cannot be. The " +"private key should only be readable by the account that is going to sign " +"tokens. When generating files with the command, your best " +"option is to run as the pki user. If you run nova-manage as root, you can " +"append --keystone-user and --keystone-group parameters to set the username " +"and group keystone is going to run under." +msgstr "" + +#: ./doc/common/section_keystone_certificates-for-pki.xml33(para) +msgid "" +"The values that specify where to read the certificates are under the " +"[signing] section of the configuration file. The " +"configuration values are:" +msgstr "" + +#: ./doc/common/section_keystone_certificates-for-pki.xml38(para) +msgid "" +"token_format - Determines the algorithm used to generate " +"tokens. Can be either UUID or PKI. " +"Defaults to PKI." +msgstr "" + +#: ./doc/common/section_keystone_certificates-for-pki.xml45(para) +msgid "" +"certfile - Location of certificate used to verify tokens." +" Default is /etc/keystone/ssl/certs/signing_cert.pem." +msgstr "" + +#: ./doc/common/section_keystone_certificates-for-pki.xml51(para) +msgid "" +"keyfile - Location of private key used to sign tokens. " +"Default is /etc/keystone/ssl/private/signing_key.pem." +msgstr "" + +#: ./doc/common/section_keystone_certificates-for-pki.xml57(para) +msgid "" +"ca_certs - Location of certificate for the authority that" +" issued the above certificate. Default is " +"/etc/keystone/ssl/certs/ca.pem." +msgstr "" + +#: ./doc/common/section_keystone_certificates-for-pki.xml64(para) +msgid "key_size - Default is 1024." +msgstr "" + +#: ./doc/common/section_keystone_certificates-for-pki.xml69(para) +msgid "valid_days - Default is 3650." +msgstr "" + +#: ./doc/common/section_keystone_certificates-for-pki.xml74(para) +msgid "" +"ca_password - Password required to read the " +"ca_file. Default is None." +msgstr "" + +#: ./doc/common/section_keystone_certificates-for-pki.xml80(para) +msgid "" +"If token_format=UUID, a typical token looks like " +"53f7f6ef0cc344b5be706bcc8b1479e1. If " +"token_format=PKI, a typical token is a much longer " +"string, such as:" +msgstr "" + +#: ./doc/common/section_keystone_certificates-for-pki.xml113(title) +msgid "Sign certificate issued by external CA" +msgstr "" + +#: ./doc/common/section_keystone_certificates-for-pki.xml114(para) +msgid "" +"You can use a signing certificate issued by an external CA instead of " +"generated by . However, certificate issued by external CA " +"must satisfy the following conditions:" +msgstr "" + +#: ./doc/common/section_keystone_certificates-for-pki.xml121(para) +msgid "" +"all certificate and key files must be in Privacy Enhanced Mail (PEM) format" +msgstr "" + +#: ./doc/common/section_keystone_certificates-for-pki.xml125(para) +msgid "private key files must not be protected by a password" +msgstr "" + +#: ./doc/common/section_keystone_certificates-for-pki.xml129(para) +msgid "" +"When using signing certificate issued by an external CA, you do not need to " +"specify key_size, valid_days, and " +"ca_password as they will be ignored." +msgstr "" + +#: ./doc/common/section_keystone_certificates-for-pki.xml134(para) +msgid "" +"The basic workflow for using a signing certificate issued by an external CA " +"involves:" +msgstr "" + +#: ./doc/common/section_keystone_certificates-for-pki.xml138(para) +msgid "Request Signing Certificate from External CA" +msgstr "" + +#: ./doc/common/section_keystone_certificates-for-pki.xml142(para) +msgid "Convert certificate and private key to PEM if needed" +msgstr "" + +#: ./doc/common/section_keystone_certificates-for-pki.xml146(para) +msgid "Install External Signing Certificate" +msgstr "" + +#: ./doc/common/section_keystone_certificates-for-pki.xml151(title) +msgid "Request a signing certificate from an external CA" +msgstr "" + +#: ./doc/common/section_keystone_certificates-for-pki.xml153(para) +msgid "" +"One way to request a signing certificate from an external CA is to first " +"generate a PKCS #10 Certificate Request Syntax (CRS) using OpenSSL CLI." +msgstr "" + +#: ./doc/common/section_keystone_certificates-for-pki.xml156(para) +msgid "" +"Create a certificate request configuration file. For example, create the " +"cert_req.conf file, as follows:" +msgstr "" + +#: ./doc/common/section_keystone_certificates-for-pki.xml176(para) +msgid "" +"Then generate a CRS with OpenSSL CLI. Do not " +"encrypt the generated private key. Must use the -nodes option." +msgstr "" + +#: ./doc/common/section_keystone_certificates-for-pki.xml183(para) +msgid "" +"If everything is successfully, you should end up with " +"signing_cert_req.pem and " +"signing_key.pem. Send " +"signing_cert_req.pem to your CA to request a token " +"signing certificate and make sure to ask the certificate to be in PEM " +"format. Also, make sure your trusted CA certificate chain is also in PEM " +"format." +msgstr "" + +#: ./doc/common/section_keystone_certificates-for-pki.xml193(title) +msgid "Install an external signing certificate" +msgstr "" + +#: ./doc/common/section_keystone_certificates-for-pki.xml194(para) +msgid "Assuming you have the following already:" +msgstr "" + +#: ./doc/common/section_keystone_certificates-for-pki.xml197(para) +msgid "" +"signing_cert.pem - (Keystone token) signing certificate" +" in PEM format" +msgstr "" + +#: ./doc/common/section_keystone_certificates-for-pki.xml202(para) +msgid "" +"signing_key.pem - corresponding (non-encrypted) private" +" key in PEM format" +msgstr "" + +#: ./doc/common/section_keystone_certificates-for-pki.xml208(para) +msgid "" +"cacert.pem - trust CA certificate chain in PEM format" +msgstr "" + +#: ./doc/common/section_keystone_certificates-for-pki.xml213(para) +msgid "Copy the above to your certificate directory. For example:" +msgstr "" + +#: ./doc/common/section_keystone_certificates-for-pki.xml222(para) +msgid "Make sure the certificate directory is only accessible by root." +msgstr "" + +#: ./doc/common/section_keystone_certificates-for-pki.xml225(para) +msgid "" +"If your certificate directory path is different from the default " +"/etc/keystone/ssl/certs, make sure it is reflected in " +"the [signing] section of the configuration file." +msgstr "" + +#: ./doc/common/section_cli_nova_customize_flavors.xml6(title) +#: ./doc/common/section_dashboard_access.xml281(guilabel) +msgid "Flavors" +msgstr "" + +#: ./doc/common/section_cli_nova_customize_flavors.xml7(para) +msgid "" +"Authorized users can use the command to create flavors. To " +"see the available flavor-related commands, run:" +msgstr "" + +#: ./doc/common/section_cli_nova_customize_flavors.xml22(para) +msgid "" +"To modify an existing flavor in the dashboard, you must delete the flavor " +"and create a modified one with the same name." +msgstr "" + +#: ./doc/common/section_cli_nova_customize_flavors.xml26(para) +msgid "Flavors define these elements:" +msgstr "" + +#: ./doc/common/section_cli_nova_customize_flavors.xml28(caption) +msgid "Identity Service configuration file sections" +msgstr "" + +#: ./doc/common/section_cli_nova_customize_flavors.xml34(td) +msgid "Element" +msgstr "" + +#: ./doc/common/section_cli_nova_customize_flavors.xml40(literal) +msgid "Name" +msgstr "" + +#: ./doc/common/section_cli_nova_customize_flavors.xml42(replaceable) +msgid "xx" +msgstr "" + +#: ./doc/common/section_cli_nova_customize_flavors.xml42(replaceable) +msgid "size_name" +msgstr "" + +#: ./doc/common/section_cli_nova_customize_flavors.xml41(td) +msgid "" +"A descriptive name. . is typically not " +"required, though some third party tools may rely on it." +msgstr "" + +#: ./doc/common/section_cli_nova_customize_flavors.xml47(literal) +msgid "Memory_MB" +msgstr "" + +#: ./doc/common/section_cli_nova_customize_flavors.xml48(td) +msgid "Virtual machine memory in megabytes." +msgstr "" + +#: ./doc/common/section_cli_nova_customize_flavors.xml51(literal) +msgid "Disk" +msgstr "" + +#: ./doc/common/section_cli_nova_customize_flavors.xml52(td) +msgid "" +"Virtual root disk size in gigabytes. This is an ephemeral disk that the base" +" image is copied into. When booting from a persistent volume it is not used." +" The \"0\" size is a special case which uses the native base image size as " +"the size of the ephemeral root volume." +msgstr "" + +#: ./doc/common/section_cli_nova_customize_flavors.xml60(literal) +msgid "Ephemeral" +msgstr "" + +#: ./doc/common/section_cli_nova_customize_flavors.xml61(td) +msgid "" +"Specifies the size of a secondary ephemeral data disk. This is an empty, " +"unformatted disk and exists only for the life of the instance." +msgstr "" + +#: ./doc/common/section_cli_nova_customize_flavors.xml66(literal) +msgid "Swap" +msgstr "" + +#: ./doc/common/section_cli_nova_customize_flavors.xml67(td) +msgid "Optional swap space allocation for the instance." +msgstr "" + +#: ./doc/common/section_cli_nova_customize_flavors.xml71(literal) +msgid "VCPUs" +msgstr "" + +#: ./doc/common/section_cli_nova_customize_flavors.xml72(td) +msgid "Number of virtual CPUs presented to the instance." +msgstr "" + +#: ./doc/common/section_cli_nova_customize_flavors.xml76(literal) +msgid "RXTX_Factor" +msgstr "" + +#: ./doc/common/section_cli_nova_customize_flavors.xml77(td) +msgid "" +"Optional property allows created servers to have a different bandwidth cap " +"than that defined in the network they are attached to. This factor is " +"multiplied by the rxtx_base property of the network. Default value is 1.0. " +"That is, the same as attached network." +msgstr "" + +#: ./doc/common/section_cli_nova_customize_flavors.xml85(literal) +msgid "Is_Public" +msgstr "" + +#: ./doc/common/section_cli_nova_customize_flavors.xml86(td) +msgid "" +"Boolean value, whether flavor is available to all users or private to the " +"tenant it was created in. Defaults to True." +msgstr "" + +#: ./doc/common/section_cli_nova_customize_flavors.xml91(literal) +msgid "extra_specs" +msgstr "" + +#: ./doc/common/section_cli_nova_customize_flavors.xml92(td) +msgid "" +"Key and value pairs that define on which compute nodes a flavor can run. " +"These pairs must match corresponding pairs on the compute nodes. Use to " +"implement special resources, such as flavors that run on only compute nodes " +"with GPU hardware." +msgstr "" + +#: ./doc/common/section_cli_nova_customize_flavors.xml100(para) +msgid "" +"Flavor customization can be limited by the hypervisor in use, for example " +"the libvirt driver enables quotas on CPUs available to a VM, disk tuning, " +"bandwidth I/O, and instance VIF traffic control." +msgstr "" + +#: ./doc/common/section_cli_nova_customize_flavors.xml104(para) +msgid "" +"You can configure the CPU limits with control parameters with the nova tool." +" For example, to configure the I/O limit:" +msgstr "" + +#: ./doc/common/section_cli_nova_customize_flavors.xml109(para) +msgid "" +"There are CPU control parameters for weight shares, enforcement intervals " +"for runtime quotas, and a quota for maximum allowed bandwidth." +msgstr "" + +#: ./doc/common/section_cli_nova_customize_flavors.xml112(para) +msgid "" +"The optional cpu_shares element specifies the " +"proportional weighted share for the domain. If this element is omitted, the " +"service defaults to the OS provided defaults. There is no unit for the " +"value. It is a relative measure based on the setting of other VMs. For " +"example, a VM configured with value 2048 gets twice as much CPU time as a VM" +" configured with value 1024." +msgstr "" + +#: ./doc/common/section_cli_nova_customize_flavors.xml119(para) +msgid "" +"The optional cpu_period element specifies the enforcement" +" interval (unit: microseconds) for QEMU and LXC hypervisors. Within a " +"period, each VCPU of the domain is not allowed to consume more than the " +"quota worth of runtime. The value should be in range [1000, " +"1000000]. A period with value 0 means no value." +msgstr "" + +#: ./doc/common/section_cli_nova_customize_flavors.xml125(para) +msgid "" +"The optional cpu_quota element specifies the maximum " +"allowed bandwidth (unit: microseconds). A domain with a quota with a " +"negative value indicates that the domain has infinite bandwidth, which means" +" that it is not bandwidth controlled. The value should be in range " +"[1000, 18446744073709551] or less than 0. A quota with " +"value 0 means no value. You can use this feature to ensure that all vcpus " +"run at the same speed. For example:" +msgstr "" + +#: ./doc/common/section_cli_nova_customize_flavors.xml135(para) +msgid "" +"In this example, the instance of m1.low_cpu can only " +"consume a maximum of 50% CPU of a physical CPU computing capability." +msgstr "" + +#: ./doc/common/section_cli_nova_customize_flavors.xml138(para) +msgid "" +"Through disk I/O quotas, you can set maximum disk write to 10 MB per second " +"for a VM user. For example:" +msgstr "" + +#: ./doc/common/section_cli_nova_customize_flavors.xml141(para) +msgid "The disk I/O options are:" +msgstr "" + +#: ./doc/common/section_cli_nova_customize_flavors.xml144(para) +msgid "disk_read_bytes_sec" +msgstr "" + +#: ./doc/common/section_cli_nova_customize_flavors.xml147(para) +msgid "disk_read_iops_sec" +msgstr "" + +#: ./doc/common/section_cli_nova_customize_flavors.xml150(para) +msgid "disk_write_bytes_sec" +msgstr "" + +#: ./doc/common/section_cli_nova_customize_flavors.xml153(para) +msgid "disk_write_iops_sec" +msgstr "" + +#: ./doc/common/section_cli_nova_customize_flavors.xml156(para) +msgid "disk_total_bytes_sec" +msgstr "" + +#: ./doc/common/section_cli_nova_customize_flavors.xml159(para) +msgid "disk_total_iops_sec" +msgstr "" + +#: ./doc/common/section_cli_nova_customize_flavors.xml162(para) +msgid "The vif I/O options are:" +msgstr "" + +#: ./doc/common/section_cli_nova_customize_flavors.xml165(para) +msgid "vif_inbound_ average" +msgstr "" + +#: ./doc/common/section_cli_nova_customize_flavors.xml168(para) +msgid "vif_inbound_burst" +msgstr "" + +#: ./doc/common/section_cli_nova_customize_flavors.xml171(para) +msgid "vif_inbound_peak" +msgstr "" + +#: ./doc/common/section_cli_nova_customize_flavors.xml174(para) +msgid "vif_outbound_ average" +msgstr "" + +#: ./doc/common/section_cli_nova_customize_flavors.xml177(para) +msgid "vif_outbound_burst" +msgstr "" + +#: ./doc/common/section_cli_nova_customize_flavors.xml180(para) +msgid "vif_outbound_peak" +msgstr "" + +#: ./doc/common/section_cli_nova_customize_flavors.xml183(para) +msgid "" +"Incoming and outgoing traffic can be shaped independently. The bandwidth " +"element can have at most one inbound and at most one outbound child element." +" Leaving any of these children element out result in no quality of service " +"(QoS) applied on that traffic direction. So, when you want to shape only the" +" network's incoming traffic, use inbound only, and vice versa. Each of these" +" elements have one mandatory attribute average." +msgstr "" + +#: ./doc/common/section_cli_nova_customize_flavors.xml191(para) +msgid "" +"It specifies average bit rate on the interface being shaped. Then there are " +"two optional attributes: peak, which specifies maximum rate at which bridge " +"can send data, and burst, amount of bytes that can be burst at peak speed. " +"Accepted values for attributes are integer numbers, The units for average " +"and peak attributes are kilobytes per second, and for the burst just " +"kilobytes. The rate is shared equally within domains connected to the " +"network." +msgstr "" + +#: ./doc/common/section_cli_nova_customize_flavors.xml199(para) +msgid "" +"This example configures a bandwidth limit for instance network traffic:" +msgstr "" + +#: ./doc/common/section_cli_nova_customize_flavors.xml203(para) +msgid "" +"Flavors can also be assigned to particular projects. By default, a flavor is" +" public and available to all projects. Private flavors are only accessible " +"to those on the access list and are invisible to other projects. To create " +"and assign a private flavor to a project, run these commands:" +msgstr "" + +#: ./doc/common/section_cli_nova_evacuate.xml6(title) +msgid "Evacuate instances" +msgstr "" + +#: ./doc/common/section_cli_nova_evacuate.xml7(para) +msgid "" +"If a cloud compute node fails due to a hardware malfunction or another " +"reason, you can evacuate instances to make them available again." +msgstr "" + +#: ./doc/common/section_cli_nova_evacuate.xml10(para) +msgid "You can choose evacuation parameters for your use case." +msgstr "" + +#: ./doc/common/section_cli_nova_evacuate.xml12(para) +msgid "" +"To preserve user data on server disk, you must configure shared storage on " +"the target host. Also, you must validate that the current VM host is down. " +"Otherwise the evacuation fails with an error." +msgstr "" + +#: ./doc/common/section_cli_nova_evacuate.xml18(para) +msgid "" +"To find a different host for the evacuated instance, run this command to " +"list hosts:" +msgstr "" + +#: ./doc/common/section_cli_nova_evacuate.xml23(para) +msgid "" +"You can pass the instance password to the command by using the " +"--password <pwd> option. If you do not specify a " +"password, one is generated and printed after the command finishes " +"successfully. The following command evacuates a server without shared " +"storage:" +msgstr "" + +#: ./doc/common/section_cli_nova_evacuate.xml29(replaceable) +#: ./doc/common/section_cli_nova_evacuate.xml50(replaceable) +msgid "evacuated_server_name" +msgstr "" + +#: ./doc/common/section_cli_nova_evacuate.xml29(replaceable) +#: ./doc/common/section_cli_nova_evacuate.xml50(replaceable) +msgid "host_b" +msgstr "" + +#: ./doc/common/section_cli_nova_evacuate.xml30(para) +msgid "" +"The command evacuates an instance from a down host to a specified host. The " +"instance is booted from a new disk, but preserves its configuration " +"including its ID, name, uid, IP address, and so on. The command returns a " +"password:" +msgstr "" + +#: ./doc/common/section_cli_nova_evacuate.xml42(para) +msgid "" +"To preserve the user disk data on the evacuated server, deploy OpenStack " +"Compute with shared file system. To configure your system, see Configure migrations in OpenStack " +"Configuration Reference. In this example, the password remains " +"unchanged." +msgstr "" + +#: ./doc/common/section_cli_neutron_manage_networks.xml8(title) +msgid "Create and manage networks" +msgstr "" + +#: ./doc/common/section_cli_neutron_manage_networks.xml9(para) +msgid "Before you run commands, set the following environment variables:" +msgstr "" + +#: ./doc/common/section_cli_neutron_manage_networks.xml16(title) +msgid "Create networks" +msgstr "" + +#: ./doc/common/section_cli_neutron_manage_networks.xml19(para) +msgid "List the extensions of the system:" +msgstr "" + +#: ./doc/common/section_cli_neutron_manage_networks.xml35(para) +msgid "Create a network:" +msgstr "" + +#: ./doc/common/section_cli_neutron_manage_networks.xml54(para) +msgid "Some fields of the created network are invisible to non-admin users." +msgstr "" + +#: ./doc/common/section_cli_neutron_manage_networks.xml59(para) +msgid "Create a network with specified provider network type:" +msgstr "" + +#: ./doc/common/section_cli_neutron_manage_networks.xml78(para) +msgid "" +"Just as shown previous, the unknown option --provider:network-" +"type is used to create a local provider " +"network." +msgstr "" + +#: ./doc/common/section_cli_neutron_manage_networks.xml86(title) +msgid "Create subnets" +msgstr "" + +#: ./doc/common/section_cli_neutron_manage_networks.xml89(para) +msgid "Create a subnet:" +msgstr "" + +#: ./doc/common/section_cli_neutron_manage_networks.xml107(para) +msgid "" +"In the previous command, net1 is the network name, " +"192.168.2.0/24 is the subnet's CIDR. They are positional " +"arguments. --name subnet1 is an unknown option, which " +"specifies the subnet's name." +msgstr "" + +#: ./doc/common/section_cli_neutron_manage_networks.xml118(title) +msgid "Create ports" +msgstr "" + +#: ./doc/common/section_cli_neutron_manage_networks.xml121(para) +msgid "Create a port with specified IP address:" +msgstr "" + +#: ./doc/common/section_cli_neutron_manage_networks.xml140(para) +msgid "" +"In the previous command, net1 is the network name, which " +"is a positional argument. --fixed-ip " +"ip_address=192.168.2.40 is an option, which specifies the port's " +"fixed IP address we wanted." +msgstr "" + +#: ./doc/common/section_cli_neutron_manage_networks.xml148(para) +msgid "Create a port without specified IP address:" +msgstr "" + +#: ./doc/common/section_cli_neutron_manage_networks.xml168(para) +msgid "" +"We can see that the system will allocate one IP address if we don't specify " +"the IP address in command line." +msgstr "" + +#: ./doc/common/section_cli_neutron_manage_networks.xml173(para) +msgid "Query ports with specified fixed IP addresses:" +msgstr "" + +#: ./doc/common/section_cli_neutron_manage_networks.xml182(para) +msgid "" +"--fixed-ips ip_address=192.168.2.2 " +"ip_address=192.168.2.40 is one unknown option." +msgstr "" + +#: ./doc/common/section_cli_neutron_manage_networks.xml185(para) +msgid "" +"How to find unknown options? The unknown " +"options can be easily found by watching the output of " +"create_xxx or show_xxx command. For " +"example, in the port creation command, we see the fixed_ips fields, which " +"can be used as an unknown option." +msgstr "" + +#: ./doc/common/section_cli_keystone_apiv3.xml5(title) +msgid "Use Identity Service API v3 instead of API v2.0" +msgstr "" + +#: ./doc/common/section_cli_keystone_apiv3.xml6(para) +msgid "" +"Use the following parameters in combination on any keystone command to " +"specify which version of the API to use:" +msgstr "" + +#: ./doc/common/section_cli_keystone_apiv3.xml11(para) +msgid "" +"--os-endpoint. The endpoint to use instead of the one" +" in the service catalog. Defaults to env[OS_SERVICE_ENDPOINT]." +msgstr "" + +#: ./doc/common/section_cli_keystone_apiv3.xml15(para) +msgid "" +"The keystone client detects the version of the API from " +"this parameter." +msgstr "" + +#: ./doc/common/section_cli_keystone_apiv3.xml19(para) +msgid "" +"--os-auth_url. The Identity Service endpoint to use " +"for authentication. Defaults to env[OS_AUTH_URL]." +msgstr "" + +#: ./doc/common/section_cli_keystone_apiv3.xml25(para) +msgid "" +"--os-identity-api-version. The Identity Service API " +"version. Defaults to env[OS_IDENTITY_API_VERSION] or " +"2.0." +msgstr "" + +#: ./doc/common/section_cli_keystone_apiv3.xml31(para) +msgid "For example, use the following parameters to use API v3:" +msgstr "" + +#: ./doc/common/section_cli_keystone_apiv3.xml33(parameter) +#: ./doc/common/section_cli_keystone_apiv3.xml35(parameter) +msgid "--os-auth_url" +msgstr "" + +#: ./doc/common/section_cli_keystone_apiv3.xml33(parameter) +#: ./doc/common/section_cli_keystone_apiv3.xml35(parameter) +msgid "--os-identity-api-version" +msgstr "" + +#: ./doc/common/section_cli_keystone_apiv3.xml34(para) +msgid "Use the following parameters to use API v2.0:" +msgstr "" + +#. When image changes, this message will be marked fuzzy or untranslated for +#. you. +#. It doesn't matter what you translate it to: it's not used at all. +#: ./doc/common/section_trusted-compute-pools.xml48(None) +#: ./doc/common/section_trusted-compute-pools.xml53(None) +msgid "" +"@@image: 'figures/OpenStackTrustedComputePool1.png'; " +"md5=858fbd6148b927723cea5ad2c88d54bd" +msgstr "" + +#. When image changes, this message will be marked fuzzy or untranslated for +#. you. +#. It doesn't matter what you translate it to: it's not used at all. +#: ./doc/common/section_trusted-compute-pools.xml161(None) +#: ./doc/common/section_trusted-compute-pools.xml166(None) +msgid "" +"@@image: 'figures/OpenStackTrustedComputePool2.png'; " +"md5=077261c595464638c4b3fcc92b6afb9a" +msgstr "" + +#: ./doc/common/section_trusted-compute-pools.xml6(title) +msgid "Trusted compute pools" +msgstr "" + +#: ./doc/common/section_trusted-compute-pools.xml7(para) +msgid "" +"Trusted compute pools enable administrators to designate a group of compute " +"hosts as trusted. These hosts use hardware-based security features, such as " +"the Intel Trusted Execution Technology (TXT), to provide an additional level" +" of security. Combined with an external stand-alone web-based remote " +"attestation server, cloud providers can ensure that the compute node runs " +"only software with verified measurements and can ensure a secure cloud " +"stack." +msgstr "" + +#: ./doc/common/section_trusted-compute-pools.xml15(para) +msgid "" +"Through the trusted compute pools, cloud subscribers can request services to" +" run on verified compute nodes." +msgstr "" + +#: ./doc/common/section_trusted-compute-pools.xml17(para) +msgid "The remote attestation server performs node verification as follows:" +msgstr "" + +#: ./doc/common/section_trusted-compute-pools.xml21(para) +msgid "Compute nodes boot with Intel TXT technology enabled." +msgstr "" + +#: ./doc/common/section_trusted-compute-pools.xml25(para) +msgid "The compute node BIOS, hypervisor, and OS are measured." +msgstr "" + +#: ./doc/common/section_trusted-compute-pools.xml29(para) +msgid "" +"Measured data is sent to the attestation server when challenged by " +"attestation server." +msgstr "" + +#: ./doc/common/section_trusted-compute-pools.xml33(para) +msgid "" +"The attestation server verifies those measurements against a good and known " +"database to determine nodes' trustworthiness." +msgstr "" + +#: ./doc/common/section_trusted-compute-pools.xml38(para) +msgid "" +"A description of how to set up an attestation service is beyond the scope of" +" this document. For an open source project that you can use to implement an " +"attestation service, see the Open " +"Attestation project." +msgstr "" + +#: ./doc/common/section_trusted-compute-pools.xml57(title) +msgid "Configure Compute to use trusted compute pools" +msgstr "" + +#: ./doc/common/section_trusted-compute-pools.xml60(para) +msgid "" +"Configure the Compute service with the connection information for the " +"attestation service." +msgstr "" + +#: ./doc/common/section_trusted-compute-pools.xml63(para) +msgid "" +"Specify these connection options in the trusted_computing" +" section in the nova.conf configuration file:" +msgstr "" + +#: ./doc/common/section_trusted-compute-pools.xml69(term) +msgid "server" +msgstr "" + +#: ./doc/common/section_trusted-compute-pools.xml71(para) +msgid "Host name or IP address of the host that runs the attestation service" +msgstr "" + +#: ./doc/common/section_trusted-compute-pools.xml77(term) +msgid "port" +msgstr "" + +#: ./doc/common/section_trusted-compute-pools.xml79(para) +msgid "HTTPS port for the attestation service" +msgstr "" + +#: ./doc/common/section_trusted-compute-pools.xml84(term) +msgid "server_ca_file" +msgstr "" + +#: ./doc/common/section_trusted-compute-pools.xml86(para) +msgid "Certificate file used to verify the attestation server's identity." +msgstr "" + +#: ./doc/common/section_trusted-compute-pools.xml91(term) +msgid "api_url" +msgstr "" + +#: ./doc/common/section_trusted-compute-pools.xml93(para) +msgid "The attestation service URL path." +msgstr "" + +#: ./doc/common/section_trusted-compute-pools.xml98(term) +msgid "auth_blob" +msgstr "" + +#: ./doc/common/section_trusted-compute-pools.xml100(para) +msgid "An authentication blob, which is required by the attestation service." +msgstr "" + +#: ./doc/common/section_trusted-compute-pools.xml108(para) +msgid "" +"To enable scheduling support for trusted compute pools, add the following " +"lines to the DEFAULT and " +"trusted_computing sections in the " +"/etc/nova/nova.conf file. Edit the details in the " +"trusted_computing section based on the details of your " +"attestation service:" +msgstr "" + +#: ./doc/common/section_trusted-compute-pools.xml133(para) +msgid "" +"Restart the nova-compute and " +"nova-scheduler services." +msgstr "" + +#: ./doc/common/section_trusted-compute-pools.xml140(title) +#: ./doc/common/section_compute_config-api.xml181(title) +msgid "Configuration reference" +msgstr "" + +#: ./doc/common/section_trusted-compute-pools.xml145(title) +msgid "Specify trusted flavors" +msgstr "" + +#: ./doc/common/section_trusted-compute-pools.xml146(para) +msgid "" +"You must configure one or more flavors as trusted. Users can request trusted" +" nodes by specifying a trusted flavor when they boot an instance." +msgstr "" + +#: ./doc/common/section_trusted-compute-pools.xml150(para) +msgid "" +"Use the command to set a flavor as trusted. For example, to" +" set the m1.tiny flavor as trusted:" +msgstr "" + +#: ./doc/common/section_trusted-compute-pools.xml154(para) +msgid "" +"To request that their instances run on a trusted host, users can specify a " +"trusted flavor on the command:" +msgstr "" + +#: ./doc/common/section_compute-configure-ec2.xml9(title) +msgid "Configure the EC2 API" +msgstr "" + +#: ./doc/common/section_compute-configure-ec2.xml10(para) +msgid "" +"You can set options in the nova.conf configuration file" +" to control which network address and port the EC2 API listens on, the " +"formatting of some API responses, and authentication related options." +msgstr "" + +#: ./doc/common/section_compute-configure-ec2.xml14(para) +msgid "" +"To customize these options for OpenStack EC2 API, use these configuration " +"option settings:" +msgstr "" + +#. ... Old module003-ch002-features-benefits edited, renamed, and stored in +#. doc/common for use by both Cloud Admin and Operator Training Guides... +#: ./doc/common/section_objectstorage-features.xml8(title) +msgid "Features and benefits" +msgstr "" + +#: ./doc/common/section_objectstorage-features.xml13(th) +msgid "Features" +msgstr "" + +#: ./doc/common/section_objectstorage-features.xml14(th) +msgid "Benefits" +msgstr "" + +#: ./doc/common/section_objectstorage-features.xml18(emphasis) +msgid "Leverages commodity hardware" +msgstr "" + +#: ./doc/common/section_objectstorage-features.xml21(td) +msgid "No lock-in, lower price/GB" +msgstr "" + +#: ./doc/common/section_objectstorage-features.xml27(emphasis) +msgid "HDD/node failure agnostic" +msgstr "" + +#: ./doc/common/section_objectstorage-features.xml28(td) +msgid "Self-healing, reliable, data redundancy protects from failures" +msgstr "" + +#: ./doc/common/section_objectstorage-features.xml33(emphasis) +msgid "Unlimited storage" +msgstr "" + +#: ./doc/common/section_objectstorage-features.xml34(td) +msgid "" +"Large and flat namespace, highly scalable read/write access, able to serve " +"content directly from storage system" +msgstr "" + +#: ./doc/common/section_objectstorage-features.xml39(emphasis) +msgid "Multi-dimensional scalability" +msgstr "" + +#: ./doc/common/section_objectstorage-features.xml41(td) +msgid "" +"Scale-out architecture—Scale vertically and horizontally-distributed storage" +" Backs up and archives large amounts of data with linear performance" +msgstr "" + +#: ./doc/common/section_objectstorage-features.xml46(emphasis) +msgid "Account/container/object structure" +msgstr "" + +#: ./doc/common/section_objectstorage-features.xml48(td) +msgid "" +"No nesting, not a traditional file system—Optimized for scale, it scales to " +"multiple petabytes and billions of objects" +msgstr "" + +#: ./doc/common/section_objectstorage-features.xml53(emphasis) +msgid "Built-in replication 3✕ + data redundancy (compared with 2✕ on RAID)" +msgstr "" + +#: ./doc/common/section_objectstorage-features.xml55(td) +msgid "" +"A configurable number of accounts, containers and object copies for high " +"availability" +msgstr "" + +#: ./doc/common/section_objectstorage-features.xml60(emphasis) +msgid "Easily add capacity (unlike RAID resize)" +msgstr "" + +#: ./doc/common/section_objectstorage-features.xml63(td) +msgid "Elastic data scaling with ease" +msgstr "" + +#: ./doc/common/section_objectstorage-features.xml69(emphasis) +msgid "No central database" +msgstr "" + +#: ./doc/common/section_objectstorage-features.xml71(td) +msgid "Higher performance, no bottlenecks" +msgstr "" + +#: ./doc/common/section_objectstorage-features.xml77(emphasis) +msgid "RAID not required" +msgstr "" + +#: ./doc/common/section_objectstorage-features.xml78(td) +msgid "Handle many small, random reads and writes efficiently" +msgstr "" + +#: ./doc/common/section_objectstorage-features.xml83(emphasis) +msgid "Built-in management utilities" +msgstr "" + +#: ./doc/common/section_objectstorage-features.xml85(td) +msgid "" +"Account management—Create, add, verify, and delete users; Container " +"management—Upload, download, and verify; Monitoring—Capacity, host, network," +" log trawling, and cluster health" +msgstr "" + +#: ./doc/common/section_objectstorage-features.xml92(emphasis) +msgid "Drive auditing" +msgstr "" + +#: ./doc/common/section_objectstorage-features.xml94(td) +msgid "Detect drive failures preempting data corruption" +msgstr "" + +#: ./doc/common/section_objectstorage-features.xml100(emphasis) +msgid "Expiring objects" +msgstr "" + +#: ./doc/common/section_objectstorage-features.xml102(td) +msgid "" +"Users can set an expiration time or a TTL on an object to control access" +msgstr "" + +#: ./doc/common/section_objectstorage-features.xml109(emphasis) +msgid "Direct object access" +msgstr "" + +#: ./doc/common/section_objectstorage-features.xml111(td) +msgid "Enable direct browser access to content, such as for a control panel" +msgstr "" + +#: ./doc/common/section_objectstorage-features.xml118(emphasis) +msgid "Realtime visibility into client requests" +msgstr "" + +#: ./doc/common/section_objectstorage-features.xml121(td) +msgid "Know what users are requesting" +msgstr "" + +#: ./doc/common/section_objectstorage-features.xml127(emphasis) +msgid "Supports S3 API" +msgstr "" + +#: ./doc/common/section_objectstorage-features.xml129(td) +msgid "Utilize tools that were designed for the popular S3 API" +msgstr "" + +#: ./doc/common/section_objectstorage-features.xml135(emphasis) +msgid "Restrict containers per account" +msgstr "" + +#: ./doc/common/section_objectstorage-features.xml138(td) +msgid "Limit access to control usage by user" +msgstr "" + +#: ./doc/common/section_objectstorage-features.xml144(emphasis) +msgid "Support for NetApp, Nexenta, SolidFire" +msgstr "" + +#: ./doc/common/section_objectstorage-features.xml147(td) +msgid "Unified support for block volumes using a variety of storage systems" +msgstr "" + +#: ./doc/common/section_objectstorage-features.xml154(emphasis) +msgid "Snapshot and backup API for block volumes" +msgstr "" + +#: ./doc/common/section_objectstorage-features.xml157(td) +msgid "Data protection and recovery for VM data" +msgstr "" + +#: ./doc/common/section_objectstorage-features.xml163(emphasis) +msgid "Standalone volume API available" +msgstr "" + +#: ./doc/common/section_objectstorage-features.xml166(td) +msgid "Separate endpoint and API for integration with other compute systems" +msgstr "" + +#: ./doc/common/section_objectstorage-features.xml173(emphasis) +msgid "Integration with Compute" +msgstr "" + +#: ./doc/common/section_objectstorage-features.xml174(td) +msgid "" +"Fully integrated with Compute for attaching block volumes and reporting on " +"usage" +msgstr "" + +#: ./doc/common/section_cli_heat_commands.xml11(title) +msgid "heat commands" +msgstr "" + +#: ./doc/common/section_cli_heat_commands.xml12(para) +msgid "" +"The heat client is the command-line interface (CLI) for the OpenStack " +"Orchestration API and its extensions." +msgstr "" + +#: ./doc/common/section_cli_heat_commands.xml20(title) +msgid "heat usage" +msgstr "" + +#: ./doc/common/section_cli_heat_commands.xml32(title) +msgid "heat positional arguments" +msgstr "" + +#: ./doc/common/section_cli_heat_commands.xml66(title) +msgid "heat optional arguments" +msgstr "" + +#: ./doc/common/section_cli_heat_commands.xml112(title) +msgid "heat action-resume command" +msgstr "" + +#: ./doc/common/section_cli_heat_commands.xml123(title) +msgid "heat action-suspend command" +msgstr "" + +#: ./doc/common/section_cli_heat_commands.xml134(title) +msgid "heat event-list command" +msgstr "" + +#: ./doc/common/section_cli_heat_commands.xml149(title) +msgid "heat event-show command" +msgstr "" + +#: ./doc/common/section_cli_heat_commands.xml162(title) +msgid "heat resource-list command" +msgstr "" + +#: ./doc/common/section_cli_heat_commands.xml173(title) +msgid "heat resource-metadata command" +msgstr "" + +#: ./doc/common/section_cli_heat_commands.xml185(title) +msgid "heat resource-show command" +msgstr "" + +#: ./doc/common/section_cli_heat_commands.xml197(title) +msgid "heat resource-template command" +msgstr "" + +#: ./doc/common/section_cli_heat_commands.xml212(title) +msgid "heat resource-type-list command" +msgstr "" + +#: ./doc/common/section_cli_heat_commands.xml220(title) +msgid "heat resource-type-show command" +msgstr "" + +#: ./doc/common/section_cli_heat_commands.xml231(title) +msgid "heat stack-create command" +msgstr "" + +#: ./doc/common/section_cli_heat_commands.xml262(title) +msgid "heat stack-delete command" +msgstr "" + +#: ./doc/common/section_cli_heat_commands.xml273(title) +msgid "heat stack-list command" +msgstr "" + +#: ./doc/common/section_cli_heat_commands.xml281(title) +msgid "heat stack-show command" +msgstr "" + +#: ./doc/common/section_cli_heat_commands.xml292(title) +msgid "heat stack-update command" +msgstr "" + +#: ./doc/common/section_cli_heat_commands.xml319(title) +msgid "heat template-show command" +msgstr "" + +#: ./doc/common/section_cli_heat_commands.xml330(title) +msgid "heat template-validate command" +msgstr "" + +#: ./doc/common/section_keystone-concepts-user-management.xml6(title) +msgid "User management" +msgstr "" + +#: ./doc/common/section_keystone-concepts-user-management.xml7(para) +msgid "The main components of Identity user management are:" +msgstr "" + +#: ./doc/common/section_keystone-concepts-user-management.xml10(para) +msgid "" +"User. Represents a human user. Has " +"associated information such as user name, password, and email. This example " +"creates a user named alice:" +msgstr "" + +#: ./doc/common/section_keystone-concepts-user-management.xml17(para) +msgid "" +"Tenant. A project, group, or " +"organization. When you make requests to OpenStack services, you must specify" +" a tenant. For example, if you query the Compute service for a list of " +"running instances, you get a list of all running instances in the tenant " +"that you specified in your query. This example creates a tenant named " +"acme:" +msgstr "" + +#: ./doc/common/section_keystone-concepts-user-management.xml27(para) +msgid "" +"Because the term project was used instead of " +"tenant in earlier versions of OpenStack Compute, some " +"command-line tools use --project_id instead of --tenant-id or --os-tenant-id to refer to a " +"tenant ID." +msgstr "" + +#: ./doc/common/section_keystone-concepts-user-management.xml38(para) +msgid "" +"Role. Captures the operations that a user" +" can perform in a given tenant." +msgstr "" + +#: ./doc/common/section_keystone-concepts-user-management.xml40(para) +msgid "This example creates a role named compute-user:" +msgstr "" + +#: ./doc/common/section_keystone-concepts-user-management.xml44(para) +msgid "" +"Individual services, such as Compute and the Image Service, assign meaning " +"to roles. In the Identity Service, a role is simply a name." +msgstr "" + +#: ./doc/common/section_keystone-concepts-user-management.xml51(para) +msgid "" +"The Identity Service assigns a tenant and a role to a user. You might assign" +" the compute-user role to the alice " +"user in the acme tenant:" +msgstr "" + +#: ./doc/common/section_keystone-concepts-user-management.xml74(para) +msgid "" +"A user can have different roles in different tenants. For example, Alice " +"might also have the admin role in the " +"Cyberdyne tenant. A user can also have multiple roles in " +"the same tenant." +msgstr "" + +#: ./doc/common/section_keystone-concepts-user-management.xml78(para) +msgid "" +"The " +"/etc/[SERVICE_CODENAME]/policy.json" +" file controls the tasks that users can perform for a given service. For " +"example, /etc/nova/policy.json specifies the access " +"policy for the Compute service, /etc/glance/policy.json" +" specifies the access policy for the Image service, and " +"/etc/keystone/policy.json specifies the access policy " +"for the Identity Service." +msgstr "" + +#: ./doc/common/section_keystone-concepts-user-management.xml88(para) +msgid "" +"The default policy.json files in the Compute, Identity," +" and Image service recognize only the admin role: all " +"operations that do not require the admin role are " +"accessible by any user that has any role in a tenant." +msgstr "" + +#: ./doc/common/section_keystone-concepts-user-management.xml93(para) +msgid "" +"If you wish to restrict users from performing operations in, say, the " +"Compute service, you need to create a role in the Identity Service and then " +"modify /etc/nova/policy.json so that this role is " +"required for Compute operations." +msgstr "" + +#: ./doc/common/section_keystone-concepts-user-management.xml99(para) +msgid "" +"For example, this line in /etc/nova/policy.json " +"specifies that there are no restrictions on which users can create volumes: " +"if the user has any role in a tenant, they can create volumes in that " +"tenant." +msgstr "" + +#: ./doc/common/section_keystone-concepts-user-management.xml105(para) +msgid "" +"To restrict creation of volumes to users who had the compute-" +"user role in a particular tenant, you would add \"role" +":compute-user\", like so:" +msgstr "" + +#: ./doc/common/section_keystone-concepts-user-management.xml110(para) +msgid "" +"To restrict all Compute service requests to require this role, the resulting" +" file would look like:" +msgstr "" + +#: ./doc/common/section_cli_nova_commands.xml11(title) +msgid "nova commands" +msgstr "" + +#: ./doc/common/section_cli_nova_commands.xml12(para) +msgid "" +"The nova client is the command-line interface (CLI) for the OpenStack " +"Compute API and its extensions." +msgstr "" + +#: ./doc/common/section_cli_nova_commands.xml20(title) +msgid "nova usage" +msgstr "" + +#: ./doc/common/section_cli_nova_commands.xml35(title) +msgid "nova positional arguments" +msgstr "" + +#: ./doc/common/section_cli_nova_commands.xml270(title) +msgid "nova optional arguments" +msgstr "" + +#: ./doc/common/section_cli_nova_commands.xml316(title) +msgid "nova absolute-limits command" +msgstr "" + +#: ./doc/common/section_cli_nova_commands.xml328(title) +msgid "nova add-fixed-ip command" +msgstr "" + +#: ./doc/common/section_cli_nova_commands.xml340(title) +msgid "nova add-secgroup command" +msgstr "" + +#: ./doc/common/section_cli_nova_commands.xml352(title) +msgid "nova agent-create command" +msgstr "" + +#: ./doc/common/section_cli_nova_commands.xml369(title) +msgid "nova agent-delete command" +msgstr "" + +#: ./doc/common/section_cli_nova_commands.xml380(title) +msgid "nova agent-list command" +msgstr "" + +#: ./doc/common/section_cli_nova_commands.xml392(title) +msgid "nova agent-modify command" +msgstr "" + +#: ./doc/common/section_cli_nova_commands.xml406(title) +msgid "nova aggregate-add-host command" +msgstr "" + +#: ./doc/common/section_cli_nova_commands.xml418(title) +msgid "nova aggregate-create command" +msgstr "" + +#: ./doc/common/section_cli_nova_commands.xml430(title) +msgid "nova aggregate-delete command" +msgstr "" + +#: ./doc/common/section_cli_nova_commands.xml441(title) +msgid "nova aggregate-details command" +msgstr "" + +#: ./doc/common/section_cli_nova_commands.xml452(title) +msgid "nova aggregate-list command" +msgstr "" + +#: ./doc/common/section_cli_nova_commands.xml460(title) +msgid "nova aggregate-remove-host command" +msgstr "" + +#: ./doc/common/section_cli_nova_commands.xml472(title) +msgid "nova aggregate-set-metadata command" +msgstr "" + +#: ./doc/common/section_cli_nova_commands.xml484(title) +msgid "nova aggregate-update command" +msgstr "" + +#: ./doc/common/section_cli_nova_commands.xml497(title) +msgid "nova availability-zone-list command" +msgstr "" + +#: ./doc/common/section_cli_nova_commands.xml505(title) +msgid "nova backup command" +msgstr "" + +#: ./doc/common/section_cli_nova_commands.xml519(title) +msgid "nova baremetal-interface-add command" +msgstr "" + +#: ./doc/common/section_cli_nova_commands.xml538(title) +msgid "nova baremetal-interface-list command" +msgstr "" + +#: ./doc/common/section_cli_nova_commands.xml549(title) +msgid "nova baremetal-interface-remove command" +msgstr "" + +#: ./doc/common/section_cli_nova_commands.xml561(title) +msgid "nova baremetal-node-create command" +msgstr "" + +#: ./doc/common/section_cli_nova_commands.xml591(title) +msgid "nova baremetal-node-delete command" +msgstr "" + +#: ./doc/common/section_cli_nova_commands.xml602(title) +msgid "nova baremetal-node-list command" +msgstr "" + +#: ./doc/common/section_cli_nova_commands.xml610(title) +msgid "nova baremetal-node-show command" +msgstr "" + +#: ./doc/common/section_cli_nova_commands.xml621(title) +msgid "nova boot command" +msgstr "" + +#: ./doc/common/section_cli_nova_commands.xml706(title) +msgid "nova cell-capacities command" +msgstr "" + +#: ./doc/common/section_cli_nova_commands.xml717(title) +msgid "nova cell-show command" +msgstr "" + +#: ./doc/common/section_cli_nova_commands.xml728(title) +msgid "nova clear-password command" +msgstr "" + +#: ./doc/common/section_cli_nova_commands.xml739(title) +msgid "nova cloudpipe-configure command" +msgstr "" + +#: ./doc/common/section_cli_nova_commands.xml751(title) +msgid "nova cloudpipe-create command" +msgstr "" + +#: ./doc/common/section_cli_nova_commands.xml762(title) +msgid "nova cloudpipe-list command" +msgstr "" + +#: ./doc/common/section_cli_nova_commands.xml770(title) +msgid "nova console-log command" +msgstr "" + +#: ./doc/common/section_cli_nova_commands.xml784(title) +msgid "nova credentials command" +msgstr "" + +#: ./doc/common/section_cli_nova_commands.xml795(title) +msgid "nova delete command" +msgstr "" + +#: ./doc/common/section_cli_nova_commands.xml806(title) +msgid "nova diagnostics command" +msgstr "" + +#: ./doc/common/section_cli_nova_commands.xml817(title) +msgid "nova dns-create command" +msgstr "" + +#: ./doc/common/section_cli_nova_commands.xml833(title) +msgid "nova dns-create-private-domain command" +msgstr "" + +#: ./doc/common/section_cli_nova_commands.xml851(title) +msgid "nova dns-create-public-domain command" +msgstr "" + +#: ./doc/common/section_cli_nova_commands.xml866(title) +msgid "nova dns-delete command" +msgstr "" + +#: ./doc/common/section_cli_nova_commands.xml878(title) +msgid "nova dns-delete-domain command" +msgstr "" + +#: ./doc/common/section_cli_nova_commands.xml889(title) +msgid "nova dns-domains command" +msgstr "" + +#: ./doc/common/section_cli_nova_commands.xml897(title) +msgid "nova dns-list command" +msgstr "" + +#: ./doc/common/section_cli_nova_commands.xml912(title) +msgid "nova endpoints command" +msgstr "" + +#: ./doc/common/section_cli_nova_commands.xml920(title) +msgid "nova evacuate command" +msgstr "" + +#: ./doc/common/section_cli_nova_commands.xml940(title) +msgid "nova fixed-ip-get command" +msgstr "" + +#: ./doc/common/section_cli_nova_commands.xml951(title) +msgid "nova fixed-ip-reserve command" +msgstr "" + +#: ./doc/common/section_cli_nova_commands.xml962(title) +msgid "nova fixed-ip-unreserve command" +msgstr "" + +#: ./doc/common/section_cli_nova_commands.xml973(title) +msgid "nova flavor-access-add command" +msgstr "" + +#: ./doc/common/section_cli_nova_commands.xml985(title) +msgid "nova flavor-access-list command" +msgstr "" + +#: ./doc/common/section_cli_nova_commands.xml997(title) +msgid "nova flavor-access-remove command" +msgstr "" + +#: ./doc/common/section_cli_nova_commands.xml1009(title) +msgid "nova flavor-create command" +msgstr "" + +#: ./doc/common/section_cli_nova_commands.xml1036(title) +msgid "nova flavor-delete command" +msgstr "" + +#: ./doc/common/section_cli_nova_commands.xml1047(title) +msgid "nova flavor-key command" +msgstr "" + +#: ./doc/common/section_cli_nova_commands.xml1060(title) +msgid "nova flavor-list command" +msgstr "" + +#: ./doc/common/section_cli_nova_commands.xml1072(title) +msgid "nova flavor-show command" +msgstr "" + +#: ./doc/common/section_cli_nova_commands.xml1083(title) +msgid "nova floating-ip-associate command" +msgstr "" + +#: ./doc/common/section_cli_nova_commands.xml1100(title) +msgid "nova floating-ip-bulk-create command" +msgstr "" + +#: ./doc/common/section_cli_nova_commands.xml1117(title) +msgid "nova floating-ip-bulk-delete command" +msgstr "" + +#: ./doc/common/section_cli_nova_commands.xml1128(title) +msgid "nova floating-ip-bulk-list command" +msgstr "" + +#: ./doc/common/section_cli_nova_commands.xml1139(title) +msgid "nova floating-ip-create command" +msgstr "" + +#: ./doc/common/section_cli_nova_commands.xml1150(title) +msgid "nova floating-ip-delete command" +msgstr "" + +#: ./doc/common/section_cli_nova_commands.xml1161(title) +msgid "nova floating-ip-disassociate command" +msgstr "" + +#: ./doc/common/section_cli_nova_commands.xml1173(title) +msgid "nova floating-ip-list command" +msgstr "" + +#: ./doc/common/section_cli_nova_commands.xml1181(title) +msgid "nova floating-ip-pool-list command" +msgstr "" + +#: ./doc/common/section_cli_nova_commands.xml1189(title) +msgid "nova force-delete command" +msgstr "" + +#: ./doc/common/section_cli_nova_commands.xml1200(title) +msgid "nova get-password command" +msgstr "" + +#: ./doc/common/section_cli_nova_commands.xml1215(title) +msgid "nova get-spice-console command" +msgstr "" + +#: ./doc/common/section_cli_nova_commands.xml1227(title) +msgid "nova get-vnc-console command" +msgstr "" + +#: ./doc/common/section_cli_nova_commands.xml1239(title) +msgid "nova host-action command" +msgstr "" + +#: ./doc/common/section_cli_nova_commands.xml1253(title) +msgid "nova host-describe command" +msgstr "" + +#: ./doc/common/section_cli_nova_commands.xml1264(title) +msgid "nova host-evacuate command" +msgstr "" + +#: ./doc/common/section_cli_nova_commands.xml1282(title) +msgid "nova host-list command" +msgstr "" + +#: ./doc/common/section_cli_nova_commands.xml1294(title) +msgid "nova host-meta command" +msgstr "" + +#: ./doc/common/section_cli_nova_commands.xml1307(title) +msgid "nova host-servers-migrate command" +msgstr "" + +#: ./doc/common/section_cli_nova_commands.xml1318(title) +msgid "nova host-update command" +msgstr "" + +#: ./doc/common/section_cli_nova_commands.xml1337(title) +msgid "nova hypervisor-list command" +msgstr "" + +#: ./doc/common/section_cli_nova_commands.xml1349(title) +msgid "nova hypervisor-servers command" +msgstr "" + +#: ./doc/common/section_cli_nova_commands.xml1360(title) +msgid "nova hypervisor-show command" +msgstr "" + +#: ./doc/common/section_cli_nova_commands.xml1371(title) +msgid "nova hypervisor-stats command" +msgstr "" + +#: ./doc/common/section_cli_nova_commands.xml1379(title) +msgid "nova hypervisor-uptime command" +msgstr "" + +#: ./doc/common/section_cli_nova_commands.xml1390(title) +msgid "nova image-create command" +msgstr "" + +#: ./doc/common/section_cli_nova_commands.xml1406(title) +msgid "nova image-delete command" +msgstr "" + +#: ./doc/common/section_cli_nova_commands.xml1417(title) +msgid "nova image-list command" +msgstr "" + +#: ./doc/common/section_cli_nova_commands.xml1428(title) +msgid "nova image-meta command" +msgstr "" + +#: ./doc/common/section_cli_nova_commands.xml1442(title) +msgid "nova image-show command" +msgstr "" + +#: ./doc/common/section_cli_nova_commands.xml1453(title) +msgid "nova instance-action command" +msgstr "" + +#: ./doc/common/section_cli_nova_commands.xml1465(title) +msgid "nova instance-action-list command" +msgstr "" + +#: ./doc/common/section_cli_nova_commands.xml1476(title) +msgid "nova interface-attach command" +msgstr "" + +#: ./doc/common/section_cli_nova_commands.xml1495(title) +msgid "nova interface-detach command" +msgstr "" + +#: ./doc/common/section_cli_nova_commands.xml1507(title) +msgid "nova interface-list command" +msgstr "" + +#: ./doc/common/section_cli_nova_commands.xml1518(title) +msgid "nova keypair-add command" +msgstr "" + +#: ./doc/common/section_cli_nova_commands.xml1532(title) +msgid "nova keypair-delete command" +msgstr "" + +#: ./doc/common/section_cli_nova_commands.xml1543(title) +msgid "nova keypair-list command" +msgstr "" + +#: ./doc/common/section_cli_nova_commands.xml1551(title) +msgid "nova keypair-show command" +msgstr "" + +#: ./doc/common/section_cli_nova_commands.xml1562(title) +msgid "nova list command" +msgstr "" + +#: ./doc/common/section_cli_nova_commands.xml1599(title) +msgid "nova list-extensions command" +msgstr "" + +#: ./doc/common/section_cli_nova_commands.xml1607(title) +msgid "nova list-secgroup command" +msgstr "" + +#: ./doc/common/section_cli_nova_commands.xml1618(title) +msgid "nova live-migration command" +msgstr "" + +#: ./doc/common/section_cli_nova_commands.xml1636(title) +msgid "nova lock command" +msgstr "" + +#: ./doc/common/section_cli_nova_commands.xml1647(title) +msgid "nova meta command" +msgstr "" + +#: ./doc/common/section_cli_nova_commands.xml1660(title) +msgid "nova migrate command" +msgstr "" + +#: ./doc/common/section_cli_nova_commands.xml1674(title) +msgid "nova migration-list command" +msgstr "" + +#: ./doc/common/section_cli_nova_commands.xml1689(title) +msgid "nova net command" +msgstr "" + +#: ./doc/common/section_cli_nova_commands.xml1700(title) +msgid "nova net-create command" +msgstr "" + +#: ./doc/common/section_cli_nova_commands.xml1713(title) +msgid "nova net-delete command" +msgstr "" + +#: ./doc/common/section_cli_nova_commands.xml1724(title) +msgid "nova net-list command" +msgstr "" + +#: ./doc/common/section_cli_nova_commands.xml1732(title) +msgid "nova network-associate-host command" +msgstr "" + +#: ./doc/common/section_cli_nova_commands.xml1744(title) +msgid "nova network-associate-project command" +msgstr "" + +#: ./doc/common/section_cli_nova_commands.xml1755(title) +msgid "nova network-create command" +msgstr "" + +#: ./doc/common/section_cli_nova_commands.xml1800(title) +msgid "nova network-disassociate command" +msgstr "" + +#: ./doc/common/section_cli_nova_commands.xml1817(title) +msgid "nova network-list command" +msgstr "" + +#: ./doc/common/section_cli_nova_commands.xml1825(title) +msgid "nova network-show command" +msgstr "" + +#: ./doc/common/section_cli_nova_commands.xml1836(title) +msgid "nova pause command" +msgstr "" + +#: ./doc/common/section_cli_nova_commands.xml1847(title) +msgid "nova quota-class-show command" +msgstr "" + +#: ./doc/common/section_cli_nova_commands.xml1858(title) +msgid "nova quota-class-update command" +msgstr "" + +#: ./doc/common/section_cli_nova_commands.xml1905(title) +msgid "nova quota-defaults command" +msgstr "" + +#: ./doc/common/section_cli_nova_commands.xml1916(title) +msgid "nova quota-delete command" +msgstr "" + +#: ./doc/common/section_cli_nova_commands.xml1928(title) +msgid "nova quota-show command" +msgstr "" + +#: ./doc/common/section_cli_nova_commands.xml1940(title) +msgid "nova quota-update command" +msgstr "" + +#: ./doc/common/section_cli_nova_commands.xml1994(title) +msgid "nova rate-limits command" +msgstr "" + +#: ./doc/common/section_cli_nova_commands.xml2002(title) +msgid "nova reboot command" +msgstr "" + +#: ./doc/common/section_cli_nova_commands.xml2017(title) +msgid "nova rebuild command" +msgstr "" + +#: ./doc/common/section_cli_nova_commands.xml2040(title) +msgid "nova remove-fixed-ip command" +msgstr "" + +#: ./doc/common/section_cli_nova_commands.xml2052(title) +msgid "nova remove-secgroup command" +msgstr "" + +#: ./doc/common/section_cli_nova_commands.xml2064(title) +msgid "nova rename command" +msgstr "" + +#: ./doc/common/section_cli_nova_commands.xml2076(title) +msgid "nova rescue command" +msgstr "" + +#: ./doc/common/section_cli_nova_commands.xml2087(title) +msgid "nova reset-network command" +msgstr "" + +#: ./doc/common/section_cli_nova_commands.xml2098(title) +msgid "nova reset-state command" +msgstr "" + +#: ./doc/common/section_cli_nova_commands.xml2113(title) +msgid "nova resize command" +msgstr "" + +#: ./doc/common/section_cli_nova_commands.xml2128(title) +msgid "nova resize-confirm command" +msgstr "" + +#: ./doc/common/section_cli_nova_commands.xml2139(title) +msgid "nova resize-revert command" +msgstr "" + +#: ./doc/common/section_cli_nova_commands.xml2150(title) +msgid "nova restore command" +msgstr "" + +#: ./doc/common/section_cli_nova_commands.xml2161(title) +msgid "nova resume command" +msgstr "" + +#: ./doc/common/section_cli_nova_commands.xml2172(title) +msgid "nova root-password command" +msgstr "" + +#: ./doc/common/section_cli_nova_commands.xml2183(title) +msgid "nova scrub command" +msgstr "" + +#: ./doc/common/section_cli_nova_commands.xml2194(title) +msgid "nova secgroup-add-group-rule command" +msgstr "" + +#: ./doc/common/section_cli_nova_commands.xml2210(title) +msgid "nova secgroup-add-rule command" +msgstr "" + +#: ./doc/common/section_cli_nova_commands.xml2226(title) +msgid "nova secgroup-create command" +msgstr "" + +#: ./doc/common/section_cli_nova_commands.xml2238(title) +msgid "nova secgroup-delete command" +msgstr "" + +#: ./doc/common/section_cli_nova_commands.xml2249(title) +msgid "nova secgroup-delete-group-rule command" +msgstr "" + +#: ./doc/common/section_cli_nova_commands.xml2265(title) +msgid "nova secgroup-delete-rule command" +msgstr "" + +#: ./doc/common/section_cli_nova_commands.xml2281(title) +msgid "nova secgroup-list command" +msgstr "" + +#: ./doc/common/section_cli_nova_commands.xml2293(title) +msgid "nova secgroup-list-rules command" +msgstr "" + +#: ./doc/common/section_cli_nova_commands.xml2304(title) +msgid "nova secgroup-update command" +msgstr "" + +#: ./doc/common/section_cli_nova_commands.xml2317(title) +msgid "nova service-disable command" +msgstr "" + +#: ./doc/common/section_cli_nova_commands.xml2332(title) +msgid "nova service-enable command" +msgstr "" + +#: ./doc/common/section_cli_nova_commands.xml2344(title) +msgid "nova service-list command" +msgstr "" + +#: ./doc/common/section_cli_nova_commands.xml2356(title) +msgid "nova shelve command" +msgstr "" + +#: ./doc/common/section_cli_nova_commands.xml2367(title) +msgid "nova shelve-offload command" +msgstr "" + +#: ./doc/common/section_cli_nova_commands.xml2378(title) +msgid "nova show command" +msgstr "" + +#: ./doc/common/section_cli_nova_commands.xml2392(title) +msgid "nova ssh command" +msgstr "" + +#: ./doc/common/section_cli_nova_commands.xml2420(title) +msgid "nova start command" +msgstr "" + +#: ./doc/common/section_cli_nova_commands.xml2431(title) +msgid "nova stop command" +msgstr "" + +#: ./doc/common/section_cli_nova_commands.xml2442(title) +msgid "nova suspend command" +msgstr "" + +#: ./doc/common/section_cli_nova_commands.xml2453(title) +msgid "nova unlock command" +msgstr "" + +#: ./doc/common/section_cli_nova_commands.xml2464(title) +msgid "nova unpause command" +msgstr "" + +#: ./doc/common/section_cli_nova_commands.xml2475(title) +msgid "nova unrescue command" +msgstr "" + +#: ./doc/common/section_cli_nova_commands.xml2486(title) +msgid "nova unshelve command" +msgstr "" + +#: ./doc/common/section_cli_nova_commands.xml2497(title) +msgid "nova usage command" +msgstr "" + +#: ./doc/common/section_cli_nova_commands.xml2512(title) +msgid "nova usage-list command" +msgstr "" + +#: ./doc/common/section_cli_nova_commands.xml2524(title) +msgid "nova volume-attach command" +msgstr "" + +#: ./doc/common/section_cli_nova_commands.xml2538(title) +msgid "nova volume-create command" +msgstr "" + +#: ./doc/common/section_cli_nova_commands.xml2571(title) +msgid "nova volume-delete command" +msgstr "" + +#: ./doc/common/section_cli_nova_commands.xml2582(title) +msgid "nova volume-detach command" +msgstr "" + +#: ./doc/common/section_cli_nova_commands.xml2594(title) +msgid "nova volume-list command" +msgstr "" + +#: ./doc/common/section_cli_nova_commands.xml2606(title) +msgid "nova volume-show command" +msgstr "" + +#: ./doc/common/section_cli_nova_commands.xml2617(title) +msgid "nova volume-snapshot-create command" +msgstr "" + +#: ./doc/common/section_cli_nova_commands.xml2639(title) +msgid "nova volume-snapshot-delete command" +msgstr "" + +#: ./doc/common/section_cli_nova_commands.xml2650(title) +msgid "nova volume-snapshot-list command" +msgstr "" + +#: ./doc/common/section_cli_nova_commands.xml2658(title) +msgid "nova volume-snapshot-show command" +msgstr "" + +#: ./doc/common/section_cli_nova_commands.xml2669(title) +msgid "nova volume-type-create command" +msgstr "" + +#: ./doc/common/section_cli_nova_commands.xml2680(title) +msgid "nova volume-type-delete command" +msgstr "" + +#: ./doc/common/section_cli_nova_commands.xml2691(title) +msgid "nova volume-type-list command" +msgstr "" + +#: ./doc/common/section_cli_nova_commands.xml2699(title) +msgid "nova volume-update command" +msgstr "" + +#: ./doc/common/section_cli_nova_commands.xml2712(title) +msgid "nova x509-create-cert command" +msgstr "" + +#: ./doc/common/section_cli_nova_commands.xml2725(title) +msgid "nova x509-get-root-cert command" +msgstr "" + +#: ./doc/common/section_compute-configure-spice.xml6(title) +msgid "SPICE console" +msgstr "" + +#: ./doc/common/section_compute-configure-spice.xml7(para) +msgid "" +"OpenStack Compute supports VNC consoles to guests. The VNC protocol is " +"fairly limited, lacking support for multiple monitors, bi-directional audio," +" reliable cut-and-paste, video streaming and more. SPICE is a new protocol " +"that aims to address the limitations in VNC and provide good remote desktop " +"support." +msgstr "" + +#: ./doc/common/section_compute-configure-spice.xml19(para) +msgid "If you do not configure SPICE correctly, Compute falls back on VNC." +msgstr "" + +#: ./doc/common/section_compute-configure-spice.xml12(para) +msgid "" +"SPICE support in OpenStack Compute shares a similar architecture to the VNC " +"implementation. The OpenStack dashboard uses a SPICE-HTML5 widget in its " +"console tab that communicates to the nova-" +"spicehtml5proxy service by using SPICE-over-websockets. The " +"nova-spicehtml5proxy service " +"communicates directly with the hypervisor process by using " +"SPICE." +msgstr "" + +#: ./doc/common/section_compute-configure-spice.xml22(para) +msgid "" +"The following table shows the options to configure SPICE as the console for " +"OpenStack Compute:" +msgstr "" + +#: ./doc/common/section_dashboard-configure.xml6(title) +msgid "Configure the dashboard" +msgstr "" + +#: ./doc/common/section_dashboard-configure.xml8(para) +msgid "You can configure the dashboard for a simple HTTP deployment." +msgstr "" + +#: ./doc/common/section_dashboard-configure.xml14(para) +msgid "Also, you can configure the size of the VNC window in the dashboard." +msgstr "" + +#: ./doc/common/section_dashboard-configure-http.xml6(title) +msgid "Configure the dashboard for HTTP" +msgstr "" + +#: ./doc/common/section_dashboard-configure-http.xml8(para) +msgid "" +"You can configure the dashboard for a simple HTTP deployment. The standard " +"installation uses a non-encrypted HTTP channel." +msgstr "" + +#: ./doc/common/section_dashboard-configure-http.xml12(para) +msgid "" +"Specify the host for your OpenStack Identity Service endpoint in the " +"/etc/openstack-dashboard/local_settings.py file with " +"the OPENSTACK_HOST setting." +msgstr "" + +#: ./doc/common/section_dashboard-configure-http.xml17(para) +msgid "The following example shows this setting:" +msgstr "" + +#: ./doc/common/section_dashboard-configure-http.xml19(para) +msgid "" +"The service catalog configuration in the Identity Service determines whether" +" a service appears in the dashboard. For the full listing, see Horizon" +" Settings and Configuration." +msgstr "" + +#: ./doc/common/section_dashboard-configure-http.xml28(para) +msgid "Restart Apache http server. For Ubuntu/Debian/SUSE:" +msgstr "" + +#: ./doc/common/section_dashboard-configure-http.xml30(para) +msgid "or for Fedora/RHEL/CentOS:" +msgstr "" + +#. When image changes, this message will be marked fuzzy or untranslated for +#. you. +#. It doesn't matter what you translate it to: it's not used at all. +#: ./doc/common/section_dashboard_access.xml86(None) +msgid "" +"@@image: 'figures/dashboard-project-tab.png'; " +"md5=d3d853ce44ba4f82a5c957ea1302430c" +msgstr "" + +#. When image changes, this message will be marked fuzzy or untranslated for +#. you. +#. It doesn't matter what you translate it to: it's not used at all. +#: ./doc/common/section_dashboard_access.xml209(None) +msgid "" +"@@image: 'figures/dashboard-admin-tab.png'; " +"md5=badc7ae21a0956572dcabeacd7117971" +msgstr "" + +#: ./doc/common/section_dashboard_access.xml14(title) +msgid "Log in to the dashboard" +msgstr "" + +#: ./doc/common/section_dashboard_access.xml15(para) +msgid "" +"The dashboard is available on the node with the nova-" +"dashboard server role." +msgstr "" + +#: ./doc/common/section_dashboard_access.xml19(para) +msgid "" +"Ask the cloud operator for the host name or public IP address from which you" +" can access the dashboard, and your user name and password." +msgstr "" + +#: ./doc/common/section_dashboard_access.xml24(para) +msgid "Open a Web browser. Make sure that JavaScript and cookies are enabled." +msgstr "" + +#: ./doc/common/section_dashboard_access.xml27(para) +msgid "" +"To use the Virtual Network Computing (VNC) client for the dashboard, your " +"browser must support HTML5 Canvas and HTML5 WebSockets. The VNC client is " +"based on noVNC. For details, see noVNC: HTML5 " +"VNC Client. For a list of supported browsers, see Browser support." +msgstr "" + +#: ./doc/common/section_dashboard_access.xml40(para) +msgid "" +"In the address bar, type the host name or IP address for the dashboard:" +msgstr "" + +#: ./doc/common/section_dashboard_access.xml42(replaceable) +msgid "IP_ADDRESS_OR_HOSTNAME" +msgstr "" + +#: ./doc/common/section_dashboard_access.xml44(title) +msgid "Certificate warning" +msgstr "" + +#: ./doc/common/section_dashboard_access.xml45(para) +msgid "" +"If a certificate warning appears when you try to access the URL for the " +"first time, a self-signed certificate is in use, which is not considered " +"trustworthy by default. Verify the certificate or add an exception in the " +"browser to bypass the warning." +msgstr "" + +#: ./doc/common/section_dashboard_access.xml54(para) +msgid "" +"On the Log In page, enter your user name and password, " +"and click Sign In." +msgstr "" + +#: ./doc/common/section_dashboard_access.xml57(para) +msgid "" +"The top-level row shows your user name. You can also access " +"Settings or sign out of the dashboard." +msgstr "" + +#: ./doc/common/section_dashboard_access.xml60(para) +msgid "" +"The visible tabs and functions in the dashboard depend on the access " +"permissions, or roles, of the user you " +"are logged in as." +msgstr "" + +#: ./doc/common/section_dashboard_access.xml64(para) +msgid "" +"If you are logged in as an end user, the main screen shows the Project tab." +msgstr "" + +#: ./doc/common/section_dashboard_access.xml67(para) +msgid "" +"If you are logged in as an administrator, the main screen shows the Project tab and Admin tab." +msgstr "" + +#: ./doc/common/section_dashboard_access.xml75(title) +msgid "OpenStack dashboard—Project tab" +msgstr "" + +#: ./doc/common/section_dashboard_access.xml76(para) +msgid "" +"Select a project from the CURRENT PROJECT drop-down " +"list on the left side to view and manage resources in that project." +msgstr "" + +#: ./doc/common/section_dashboard_access.xml79(para) +msgid "" +"The Project tab displays the details of the selected " +"project." +msgstr "" + +#: ./doc/common/section_dashboard_access.xml82(title) +msgid "Dashboard projects" +msgstr "" + +#: ./doc/common/section_dashboard_access.xml90(para) +msgid "Access the following tabs:" +msgstr "" + +#: ./doc/common/section_dashboard_access.xml91(para) +msgid "Manage Compute tab" +msgstr "" + +#: ./doc/common/section_dashboard_access.xml94(guilabel) +#: ./doc/common/section_dashboard_access.xml216(guilabel) +#: ./doc/common/section_cli_overview.xml14(title) +msgid "Overview" +msgstr "" + +#: ./doc/common/section_dashboard_access.xml96(para) +msgid "View reports for the project." +msgstr "" + +#: ./doc/common/section_dashboard_access.xml100(guilabel) +#: ./doc/common/section_dashboard_access.xml264(guilabel) +msgid "Instances" +msgstr "" + +#: ./doc/common/section_dashboard_access.xml102(para) +msgid "" +"View, launch, create a snapshot from, stop, pause, or reboot instances, or " +"connect to them through VNC." +msgstr "" + +#: ./doc/common/section_dashboard_access.xml110(para) +msgid "View, create, edit, and delete volumes." +msgstr "" + +#: ./doc/common/section_dashboard_access.xml115(guilabel) +msgid "Images & Snapshots" +msgstr "" + +#: ./doc/common/section_dashboard_access.xml118(para) +msgid "" +"View images, instance snapshots, and volume snapshots created project users," +" plus any images that are publicly available. Create, edit, and delete " +"images, and launch instances from images and snapshots." +msgstr "" + +#: ./doc/common/section_dashboard_access.xml126(guilabel) +msgid "Access & Security" +msgstr "" + +#: ./doc/common/section_dashboard_access.xml129(para) +msgid "Use the following tabs to complete these tasks:" +msgstr "" + +#: ./doc/common/section_dashboard_access.xml132(title) +msgid "Security Groups tab" +msgstr "" + +#: ./doc/common/section_dashboard_access.xml134(para) +msgid "" +"View, create, edit, and delete security groups and security group rules." +msgstr "" + +#: ./doc/common/section_dashboard_access.xml138(title) +msgid "Keypairs tab" +msgstr "" + +#: ./doc/common/section_dashboard_access.xml140(para) +msgid "View, create, edit, and import keypairs, and delete keypairs." +msgstr "" + +#: ./doc/common/section_dashboard_access.xml144(title) +msgid "Floating IPs tab" +msgstr "" + +#: ./doc/common/section_dashboard_access.xml146(para) +msgid "Allocate an IP address to or release it from a project." +msgstr "" + +#: ./doc/common/section_dashboard_access.xml150(title) +msgid "API Access tab" +msgstr "" + +#: ./doc/common/section_dashboard_access.xml152(para) +msgid "View API endpoints." +msgstr "" + +#: ./doc/common/section_dashboard_access.xml157(para) +msgid "Manage Network tab" +msgstr "" + +#: ./doc/common/section_dashboard_access.xml160(guilabel) +#: ./doc/common/section_dashboard_access.xml296(guilabel) +msgid "Networks" +msgstr "" + +#: ./doc/common/section_dashboard_access.xml162(para) +msgid "Create and manage public and private networks." +msgstr "" + +#: ./doc/common/section_dashboard_access.xml166(guilabel) +#: ./doc/common/section_dashboard_access.xml303(guilabel) +msgid "Routers" +msgstr "" + +#: ./doc/common/section_dashboard_access.xml168(para) +msgid "Create and manage subnets." +msgstr "" + +#: ./doc/common/section_dashboard_access.xml172(guilabel) +msgid "Network Topology" +msgstr "" + +#: ./doc/common/section_dashboard_access.xml174(para) +msgid "View the network topology." +msgstr "" + +#: ./doc/common/section_dashboard_access.xml178(para) +msgid "Object Store tab" +msgstr "" + +#: ./doc/common/section_dashboard_access.xml181(guilabel) +msgid "Containers" +msgstr "" + +#: ./doc/common/section_dashboard_access.xml183(para) +msgid "Create and manage object storage." +msgstr "" + +#: ./doc/common/section_dashboard_access.xml187(para) +msgid "Orchestration tab" +msgstr "" + +#: ./doc/common/section_dashboard_access.xml190(guilabel) +msgid "Stacks" +msgstr "" + +#: ./doc/common/section_dashboard_access.xml192(para) +msgid "Use REST API to orchestrate multiple composite cloud applications" +msgstr "" + +#: ./doc/common/section_dashboard_access.xml199(title) +msgid "OpenStack dashboard—Admin tab" +msgstr "" + +#: ./doc/common/section_dashboard_access.xml200(para) +msgid "" +"Enables administrative users to view usage and manage instances, volumes, " +"flavors, images, projects, users, services, and quotas." +msgstr "" + +#: ./doc/common/section_dashboard_access.xml204(title) +msgid "Admin tab" +msgstr "" + +#: ./doc/common/section_dashboard_access.xml213(para) +msgid "Access the following categories to complete these tasks:" +msgstr "" + +#: ./doc/common/section_dashboard_access.xml218(para) +msgid "View basic reports." +msgstr "" + +#: ./doc/common/section_dashboard_access.xml222(guilabel) +msgid "Resource Usage" +msgstr "" + +#: ./doc/common/section_dashboard_access.xml224(para) +msgid "Use the following tabs to view the following usages:" +msgstr "" + +#: ./doc/common/section_dashboard_access.xml226(title) +msgid "Global Disk Usage tab" +msgstr "" + +#: ./doc/common/section_dashboard_access.xml228(para) +msgid "" +"View the global disk usage for all tenants as an average over the last 30 " +"days." +msgstr "" + +#: ./doc/common/section_dashboard_access.xml232(title) +msgid "Global Network Traffic Usage tab" +msgstr "" + +#: ./doc/common/section_dashboard_access.xml234(para) +#: ./doc/common/section_dashboard_access.xml247(para) +msgid "" +"View the global network usage for all tenants as an average over the last 30" +" days." +msgstr "" + +#: ./doc/common/section_dashboard_access.xml238(title) +msgid "Global Object Storage Usage tab" +msgstr "" + +#: ./doc/common/section_dashboard_access.xml240(para) +msgid "" +"View the global object storage usage for all tenants as an average over the " +"last 30 days." +msgstr "" + +#: ./doc/common/section_dashboard_access.xml245(title) +msgid "Global Network Usage tab" +msgstr "" + +#: ./doc/common/section_dashboard_access.xml251(title) +msgid "Stats tab" +msgstr "" + +#: ./doc/common/section_dashboard_access.xml253(para) +msgid "View the statistics of all resources." +msgstr "" + +#: ./doc/common/section_dashboard_access.xml258(guilabel) +msgid "Hypervisors" +msgstr "" + +#: ./doc/common/section_dashboard_access.xml260(para) +msgid "View the hypervisor summary." +msgstr "" + +#: ./doc/common/section_dashboard_access.xml266(para) +msgid "" +"View, pause, resume, suspend, migrate, soft or hard reboot, and delete " +"running instances that belong to users of some, but not all, projects. Also," +" view the log for an instance or access an instance through VNC." +msgstr "" + +#: ./doc/common/section_dashboard_access.xml276(para) +msgid "View, create, edit, and delete volumes and volume types." +msgstr "" + +#: ./doc/common/section_dashboard_access.xml283(para) +msgid "" +"View, create, edit, view extra specs for, and delete flavors. A flavor is " +"size for an instance." +msgstr "" + +#: ./doc/common/section_dashboard_access.xml289(guilabel) +msgid "Images" +msgstr "" + +#: ./doc/common/section_dashboard_access.xml291(para) +msgid "View, create, edit properties for, and delete custom images." +msgstr "" + +#: ./doc/common/section_dashboard_access.xml298(para) +msgid "View, create, edit properties for, and delete networks." +msgstr "" + +#: ./doc/common/section_dashboard_access.xml305(para) +msgid "View, create, edit properties for, and delete routers." +msgstr "" + +#: ./doc/common/section_dashboard_access.xml310(guilabel) +msgid "Defaults" +msgstr "" + +#: ./doc/common/section_dashboard_access.xml312(para) +msgid "" +"View default quota values. Quotas are hard-coded in OpenStack Compute and " +"define the maximum allowable size and number of resources." +msgstr "" + +#: ./doc/common/section_dashboard_access.xml319(guilabel) +msgid "System Info" +msgstr "" + +#: ./doc/common/section_dashboard_access.xml321(para) +msgid "Use the following tabs to view the service info:" +msgstr "" + +#: ./doc/common/section_dashboard_access.xml323(title) +msgid "Services tab" +msgstr "" + +#: ./doc/common/section_dashboard_access.xml324(para) +msgid "View a list of the services." +msgstr "" + +#: ./doc/common/section_dashboard_access.xml327(title) +msgid "Compute Services tab" +msgstr "" + +#: ./doc/common/section_dashboard_access.xml328(para) +msgid "View a list of all Compute services." +msgstr "" + +#: ./doc/common/section_dashboard_access.xml331(title) +msgid "Availability Zones tab" +msgstr "" + +#: ./doc/common/section_dashboard_access.xml333(para) +msgid "View the availability zones." +msgstr "" + +#: ./doc/common/section_dashboard_access.xml336(title) +msgid "Host Aggregates tab" +msgstr "" + +#: ./doc/common/section_dashboard_access.xml337(para) +msgid "View host aggregates." +msgstr "" + +#: ./doc/common/section_dashboard_access.xml340(title) +msgid "Network Agents tab" +msgstr "" + +#: ./doc/common/section_dashboard_access.xml342(para) +msgid "View the network agents." +msgstr "" + +#: ./doc/common/section_dashboard_access.xml349(para) +msgid "View domains." +msgstr "" + +#: ./doc/common/section_dashboard_access.xml353(guilabel) +msgid "Projects" +msgstr "" + +#: ./doc/common/section_dashboard_access.xml355(para) +msgid "View, create, assign users to, remove users from, and delete projects." +msgstr "" + +#: ./doc/common/section_dashboard_access.xml360(guilabel) +msgid "Users" +msgstr "" + +#: ./doc/common/section_dashboard_access.xml362(para) +msgid "View, create, enable, disable, and delete users." +msgstr "" + +#: ./doc/common/section_dashboard_access.xml367(guilabel) +#: ./doc/common/section_keystone-concepts-group-management.xml6(title) +msgid "Groups" +msgstr "" + +#: ./doc/common/section_dashboard_access.xml369(para) +msgid "View, create, enable, disable, and delete groups." +msgstr "" + +#: ./doc/common/section_dashboard_access.xml374(guilabel) +msgid "Roles" +msgstr "" + +#: ./doc/common/section_dashboard_access.xml376(para) +msgid "View, create, enable, disable, and delete roles." +msgstr "" + +#: ./doc/common/ch_using_openstack_overview.xml10(title) +msgid "" +"How can I useadminister an OpenStack cloud?" +msgstr "" + +#: ./doc/common/ch_using_openstack_overview.xml14(para) +msgid "" +"As an OpenStack cloud end user, you can provision your own resources within " +"the limits set by administrators." +msgstr "" + +#: ./doc/common/ch_using_openstack_overview.xml17(para) +msgid "" +"As an OpenStack cloud administrative user, you can manage tenants, known as " +"projects, users, services, " +"images, flavors, and quotas." +msgstr "" + +#: ./doc/common/ch_using_openstack_overview.xml21(para) +msgid "" +"The examples in this guide show you how to complete these tasks with either:" +msgstr "" + +#: ./doc/common/ch_using_openstack_overview.xml25(para) +msgid "" +"The OpenStack dashboard. Use this Web-based graphical interface, code named " +"horizon, to " +"view, create, and manage resources and " +"services." +msgstr "" + +#: ./doc/common/ch_using_openstack_overview.xml33(para) +msgid "" +"The OpenStack command-line clients. Each core OpenStack project has a " +"command-line client that lets you run simple commands to view, create, and " +"manage resources and services in a " +"cloud and automate tasks by using scripts." +msgstr "" + +#: ./doc/common/ch_using_openstack_overview.xml41(para) +msgid "You can modify these examples for your specific use cases." +msgstr "" + +#: ./doc/common/ch_using_openstack_overview.xml43(para) +msgid "" +"In addition to these ways of interacting with a cloud, you can access the " +"OpenStack APIs directly or indirectly through cURL commands or open SDKs. You can " +"automate access or build tools to manage resources and services by using the" +" native OpenStack APIs or the EC2 compatibility API." +msgstr "" + +#: ./doc/common/ch_using_openstack_overview.xml49(para) +msgid "" +"To use the OpenStack APIs, it helps to be familiar with HTTP/1.1, RESTful " +"web services, the OpenStack services, and JSON or XML data serialization " +"formats." +msgstr "" + +#: ./doc/common/section_xapi-ami-setup.xml7(title) +msgid "Prepare for AMI type images" +msgstr "" + +#: ./doc/common/section_xapi-ami-setup.xml8(para) +msgid "" +"To support AMI type images in your OpenStack installation, you must create a" +" /boot/guest directory inside Dom0. The OpenStack VM " +"extracts the kernel and ramdisk from the AKI and ARI images puts them in " +"this location." +msgstr "" + +#: ./doc/common/section_xapi-ami-setup.xml12(para) +msgid "" +"OpenStack maintains the contents of this directory and its size should not " +"increase during normal operation. However, in case of power failures or " +"accidental shutdowns, some files might be left over. To prevent these files " +"from filling the Dom0 disk, set up this directory as a symlink that points " +"to a subdirectory of the local SR." +msgstr "" + +#: ./doc/common/section_xapi-ami-setup.xml18(para) +msgid "Run these commands in Dom0 to achieve this setup:" +msgstr "" + +#: ./doc/common/section_about-object-storage.xml8(para) +msgid "" +"Object Storage is a robust, highly scalable and fault tolerant storage " +"platform for unstructured data such as objects. Objects are stored bits, " +"accessed through a RESTful, HTTP-based interface. You cannot access data at " +"the block or file level. Object Storage is commonly used to archive and back" +" up data, with use cases in virtual machine image, photo, video and music " +"storage." +msgstr "" + +#: ./doc/common/section_about-object-storage.xml15(para) +msgid "" +"Object Storage provides a high degree of availability, throughput, and " +"performance with its scale out architecture. Each object is replicated " +"across multiple servers, residing within the same data center or across data" +" centers, which mitigates the risk of network and hardware failure. In the " +"event of hardware failure, Object Storage will automatically copy objects to" +" a new location to ensure that there are always three copies available. " +"Object Storage is an eventually consistent distributed storage platform; it " +"sacrifices consistency for maximum availability and partition tolerance. " +"Object Storage enables you to create a reliable platform by using commodity " +"hardware and inexpensive storage." +msgstr "" + +#: ./doc/common/section_about-object-storage.xml27(para) +msgid "" +"For more information, review the key concepts in the developer documentation" +" at docs.openstack.org/developer/swift/." +msgstr "" + +#: ./doc/common/section_cli_cinder_manage_volumes.xml7(title) +msgid "Manage volumes" +msgstr "" + +#: ./doc/common/section_cli_cinder_manage_volumes.xml8(para) +msgid "" +"A volume is a detachable block storage device, similar to a USB hard drive. " +"You can attach a volume to only one instance. To create and manage volumes, " +"you use a combination of nova and cinder client commands." +msgstr "" + +#: ./doc/common/section_cli_cinder_manage_volumes.xml12(para) +msgid "" +"This example creates a my-new-volume volume based on an " +"image." +msgstr "" + +#: ./doc/common/section_cli_cinder_manage_volumes.xml16(title) +msgid "Migrate a volume" +msgstr "" + +#: ./doc/common/section_cli_cinder_manage_volumes.xml17(para) +msgid "" +"As an administrator, you can migrate a volume with its data from one " +"location to another in a manner that is transparent to users and workloads. " +"You can migrate only detached volumes with no snapshots." +msgstr "" + +#: ./doc/common/section_cli_cinder_manage_volumes.xml21(para) +msgid "Possible use cases for data migration:" +msgstr "" + +#: ./doc/common/section_cli_cinder_manage_volumes.xml24(para) +msgid "" +"Bring down a physical storage device for maintenance without disrupting " +"workloads." +msgstr "" + +#: ./doc/common/section_cli_cinder_manage_volumes.xml28(para) +msgid "Modify the properties of a volume." +msgstr "" + +#: ./doc/common/section_cli_cinder_manage_volumes.xml31(para) +msgid "Free up space in a thinly-provisioned back end." +msgstr "" + +#: ./doc/common/section_cli_cinder_manage_volumes.xml35(para) +msgid "Migrate a volume, as follows:" +msgstr "" + +#: ./doc/common/section_cli_cinder_manage_volumes.xml36(replaceable) +#: ./doc/common/section_cli_cinder_manage_volumes.xml288(replaceable) +msgid "volumeID" +msgstr "" + +#: ./doc/common/section_cli_cinder_manage_volumes.xml36(replaceable) +msgid "destinationHost" +msgstr "" + +#: ./doc/common/section_cli_cinder_manage_volumes.xml36(replaceable) +msgid "True|False" +msgstr "" + +#: ./doc/common/section_cli_cinder_manage_volumes.xml37(para) +msgid "" +"Where --force-host-copy=True forces the generic host-" +"based migration mechanism and bypasses any driver optimizations." +msgstr "" + +#: ./doc/common/section_cli_cinder_manage_volumes.xml41(para) +msgid "" +"If the volume is in use or has snapshots, the specified host destination " +"cannot accept the volume." +msgstr "" + +#: ./doc/common/section_cli_cinder_manage_volumes.xml44(para) +msgid "If the user is not an administrator, the migration fails." +msgstr "" + +#: ./doc/common/section_cli_cinder_manage_volumes.xml49(title) +msgid "Create a volume" +msgstr "" + +#: ./doc/common/section_cli_cinder_manage_volumes.xml52(para) +msgid "List images, and note the ID of the image to use for your volume:" +msgstr "" + +#: ./doc/common/section_cli_cinder_manage_volumes.xml66(para) +msgid "" +"List the availability zones, and note the ID of the availability zone in " +"which to create your volume:" +msgstr "" + +#: ./doc/common/section_cli_cinder_manage_volumes.xml86(para) +msgid "" +"Create a volume with 8 GBs of space. Specify the availability zone and " +"image:" +msgstr "" + +#: ./doc/common/section_cli_cinder_manage_volumes.xml109(para) +msgid "" +"To verify that your volume was created successfully, list the available " +"volumes:" +msgstr "" + +#: ./doc/common/section_cli_cinder_manage_volumes.xml118(para) +msgid "" +"If your volume was created successfully, its status is " +"available. If its status is error, you" +" might have exceeded your quota." +msgstr "" + +#: ./doc/common/section_cli_cinder_manage_volumes.xml126(title) +msgid "Attach a volume to an instance" +msgstr "" + +#: ./doc/common/section_cli_cinder_manage_volumes.xml129(para) +msgid "Attach your volume to a server:" +msgstr "" + +#: ./doc/common/section_cli_cinder_manage_volumes.xml139(para) +msgid "Note the ID of your volume." +msgstr "" + +#: ./doc/common/section_cli_cinder_manage_volumes.xml142(para) +msgid "Show information for your volume:" +msgstr "" + +#: ./doc/common/section_cli_cinder_manage_volumes.xml164(para) +msgid "" +"The output shows that the volume is attached to the server with ID 84c6e57d-a6b1-44b6-81eb-fcb36afd31b5, is in the nova availability" +" zone, and is bootable." +msgstr "" + +#: ./doc/common/section_cli_cinder_manage_volumes.xml173(title) +msgid "Resize a volume" +msgstr "" + +#: ./doc/common/section_cli_cinder_manage_volumes.xml176(para) +msgid "To resize your volume, you must first detach it from the server." +msgstr "" + +#: ./doc/common/section_cli_cinder_manage_volumes.xml178(para) +msgid "" +"To detach the volume from your server, pass the server ID and volume ID to " +"the command:" +msgstr "" + +#: ./doc/common/section_cli_cinder_manage_volumes.xml181(para) +#: ./doc/common/section_cli_cinder_manage_volumes.xml200(para) +msgid "The command does not return any output." +msgstr "" + +#: ./doc/common/section_cli_cinder_manage_volumes.xml185(para) +msgid "List volumes:" +msgstr "" + +#: ./doc/common/section_cli_cinder_manage_volumes.xml193(para) +msgid "Note that the volume is now available." +msgstr "" + +#: ./doc/common/section_cli_cinder_manage_volumes.xml196(para) +msgid "" +"Resize the volume by passing the volume ID and the new size (a value greater" +" than the old one) as parameters:" +msgstr "" + +#: ./doc/common/section_cli_cinder_manage_volumes.xml199(replaceable) +msgid "573e024d-5235-49ce-8332-be1576d323f8" +msgstr "" + +#: ./doc/common/section_cli_cinder_manage_volumes.xml199(replaceable) +msgid "10" +msgstr "" + +#: ./doc/common/section_cli_cinder_manage_volumes.xml206(title) +msgid "Delete a volume" +msgstr "" + +#: ./doc/common/section_cli_cinder_manage_volumes.xml209(para) +msgid "To delete your volume, you must first detach it from the server." +msgstr "" + +#: ./doc/common/section_cli_cinder_manage_volumes.xml211(para) +msgid "" +"To detach the volume from your server and check for the list of existing " +"volumes, see steps 1 and 2 mentioned in ." +msgstr "" + +#: ./doc/common/section_cli_cinder_manage_volumes.xml217(para) +#: ./doc/common/section_cli_cinder_manage_volumes.xml408(para) +msgid "Delete the volume:" +msgstr "" + +#: ./doc/common/section_cli_cinder_manage_volumes.xml219(para) +msgid "The delete command does not return any output." +msgstr "" + +#: ./doc/common/section_cli_cinder_manage_volumes.xml223(para) +msgid "" +"List the volumes again, and note that the status of your volume is " +"deleting:" +msgstr "" + +#: ./doc/common/section_cli_cinder_manage_volumes.xml233(para) +msgid "" +"When the volume is fully deleted, it disappears from the list of volumes:" +msgstr "" + +#: ./doc/common/section_cli_cinder_manage_volumes.xml245(title) +msgid "Transfer a volume" +msgstr "" + +#: ./doc/common/section_cli_cinder_manage_volumes.xml246(para) +msgid "" +"You can transfer a volume from one owner to another by using the " +" commands. The volume donor, or original owner, creates a " +"transfer request and sends the created transfer ID and authorization key to " +"the volume recipient. The volume recipient, or new owner, accepts the " +"transfer by using the ID and key." +msgstr "" + +#: ./doc/common/section_cli_cinder_manage_volumes.xml254(para) +msgid "" +"The procedure for volume transfer is intended for tenants (both the volume " +"donor and recipient) within the same cloud." +msgstr "" + +#: ./doc/common/section_cli_cinder_manage_volumes.xml256(para) +msgid "Use cases include:" +msgstr "" + +#: ./doc/common/section_cli_cinder_manage_volumes.xml259(para) +msgid "" +"Create a custom bootable volume or a volume with a large data set and " +"transfer it to the end customer." +msgstr "" + +#: ./doc/common/section_cli_cinder_manage_volumes.xml264(para) +msgid "" +"For bulk import of data to the cloud, the data ingress system creates a new " +"Block Storage volume, copies data from the physical device, and transfers " +"device ownership to the end user." +msgstr "" + +#: ./doc/common/section_cli_cinder_manage_volumes.xml271(title) +msgid "Create a volume transfer request" +msgstr "" + +#: ./doc/common/section_cli_cinder_manage_volumes.xml274(para) +msgid "While logged in as the volume donor, list available volumes:" +msgstr "" + +#: ./doc/common/section_cli_cinder_manage_volumes.xml285(para) +msgid "" +"As the volume donor, request a volume transfer authorization code for a " +"specific volume:" +msgstr "" + +#: ./doc/common/section_cli_cinder_manage_volumes.xml289(para) +msgid "" +"The volume must be in an ‘available’ state or the request will be denied. If" +" the transfer request is valid in the database (that is, it has not expired " +"or been deleted), the volume is placed in an awaiting " +"transfer state. For example:" +msgstr "" + +#: ./doc/common/section_cli_cinder_manage_volumes.xml307(para) +msgid "" +"Optionally, you can specify a name for the transfer by using the --display-name displayName parameter." +msgstr "" + +#: ./doc/common/section_cli_cinder_manage_volumes.xml315(para) +msgid "" +"Send the volume transfer ID and authorization key to the new owner (for " +"example, by email)." +msgstr "" + +#: ./doc/common/section_cli_cinder_manage_volumes.xml320(para) +msgid "View pending transfers:" +msgstr "" + +#: ./doc/common/section_cli_cinder_manage_volumes.xml329(para) +msgid "" +"After the volume recipient, or new owner, accepts the transfer, you can see " +"that the transfer is no longer available:" +msgstr "" + +#: ./doc/common/section_cli_cinder_manage_volumes.xml341(title) +msgid "Accept a volume transfer request" +msgstr "" + +#: ./doc/common/section_cli_cinder_manage_volumes.xml344(para) +msgid "" +"As the volume recipient, you must first obtain the transfer ID and " +"authorization key from the original owner." +msgstr "" + +#: ./doc/common/section_cli_cinder_manage_volumes.xml349(para) +msgid "Display the transfer request details using the ID:" +msgstr "" + +#: ./doc/common/section_cli_cinder_manage_volumes.xml351(replaceable) +#: ./doc/common/section_cli_cinder_manage_volumes.xml365(replaceable) +#: ./doc/common/section_cli_cinder_manage_volumes.xml409(replaceable) +msgid "transferID" +msgstr "" + +#: ./doc/common/section_cli_cinder_manage_volumes.xml364(para) +msgid "Accept the request:" +msgstr "" + +#: ./doc/common/section_cli_cinder_manage_volumes.xml365(replaceable) +msgid "authKey" +msgstr "" + +#: ./doc/common/section_cli_cinder_manage_volumes.xml376(para) +msgid "" +"If you do not have a sufficient quota for the transfer, the transfer is " +"refused." +msgstr "" + +#: ./doc/common/section_cli_cinder_manage_volumes.xml384(title) +msgid "Delete a volume transfer" +msgstr "" + +#: ./doc/common/section_cli_cinder_manage_volumes.xml388(para) +msgid "List available volumes and their statuses:" +msgstr "" + +#: ./doc/common/section_cli_cinder_manage_volumes.xml399(para) +msgid "Find the matching transfer ID:" +msgstr "" + +#: ./doc/common/section_cli_cinder_manage_volumes.xml414(para) +msgid "" +"The transfer list is now empty and the volume is again available for " +"transfer:" +msgstr "" + +#: ./doc/common/section_cli_glance_commands.xml11(title) +msgid "glance commands" +msgstr "" + +#: ./doc/common/section_cli_glance_commands.xml12(para) +msgid "" +"The glance client is the command-line interface (CLI) for the OpenStack " +"Image Service API and its extensions." +msgstr "" + +#: ./doc/common/section_cli_glance_commands.xml20(title) +msgid "glance usage" +msgstr "" + +#: ./doc/common/section_cli_glance_commands.xml37(title) +msgid "glance positional arguments" +msgstr "" + +#: ./doc/common/section_cli_glance_commands.xml64(title) +msgid "glance optional arguments" +msgstr "" + +#: ./doc/common/section_cli_glance_commands.xml135(title) +msgid "glance image-create command" +msgstr "" + +#: ./doc/common/section_cli_glance_commands.xml195(title) +msgid "glance image-delete command" +msgstr "" + +#: ./doc/common/section_cli_glance_commands.xml206(title) +msgid "glance image-list command" +msgstr "" + +#: ./doc/common/section_cli_glance_commands.xml255(title) +msgid "glance image-show command" +msgstr "" + +#: ./doc/common/section_cli_glance_commands.xml269(title) +msgid "glance image-update command" +msgstr "" + +#: ./doc/common/section_cli_glance_commands.xml332(title) +msgid "glance member-create command" +msgstr "" + +#: ./doc/common/section_cli_glance_commands.xml347(title) +msgid "glance member-delete command" +msgstr "" + +#: ./doc/common/section_cli_glance_commands.xml359(title) +msgid "glance member-list command" +msgstr "" + +#: ./doc/common/section_cli_nova_usage_statistics.xml4(title) +msgid "Show usage statistics for hosts and instances" +msgstr "" + +#: ./doc/common/section_cli_nova_usage_statistics.xml4(para) +msgid "" +"You can show basic statistics on resource usage for hosts and instances." +msgstr "" + +#: ./doc/common/section_cli_nova_usage_statistics.xml6(para) +msgid "" +"For more sophisticated monitoring, see the Ceilometer project, which " +"is under development. You can also use tools, such as Ganglia or Graphite, to gather more " +"detailed data." +msgstr "" + +#: ./doc/common/section_cli_nova_usage_statistics.xml15(title) +msgid "To show host usage statistics" +msgstr "" + +#: ./doc/common/section_cli_nova_usage_statistics.xml16(para) +msgid "List the hosts and the nova-related services that run on them:" +msgstr "" + +#: ./doc/common/section_cli_nova_usage_statistics.xml29(para) +msgid "" +"Get a summary of resource usage of all of the instances running on the host." +msgstr "" + +#: ./doc/common/section_cli_nova_usage_statistics.xml31(replaceable) +msgid "devstack-grizzly" +msgstr "" + +#: ./doc/common/section_cli_nova_usage_statistics.xml41(para) +msgid "" +"The cpu column shows the sum of the virtual CPUs for " +"instances running on the host." +msgstr "" + +#: ./doc/common/section_cli_nova_usage_statistics.xml43(para) +msgid "" +"The memory_mb column shows the sum of the memory (in MB) " +"allocated to the instances that run on the hosts." +msgstr "" + +#: ./doc/common/section_cli_nova_usage_statistics.xml46(para) +msgid "" +"The disk_gb column shows the sum of the root and " +"ephemeral disk sizes (in GB) of the instances that run on the hosts." +msgstr "" + +#: ./doc/common/section_cli_nova_usage_statistics.xml49(para) +msgid "" +"The used_now row shows the sum of the resources allocated" +" to the instances that run on the host plus the resources allocated to the " +"virtual machine of the host itself." +msgstr "" + +#: ./doc/common/section_cli_nova_usage_statistics.xml53(para) +msgid "" +"The used_max row shows the sum of the resources allocated" +" to the instances that run on the host." +msgstr "" + +#: ./doc/common/section_cli_nova_usage_statistics.xml56(para) +msgid "" +"These values are computed by using only information about the flavors of the" +" instances that run on the hosts. This command does not query the CPU usage," +" memory usage, or hard disk usage of the physical host." +msgstr "" + +#: ./doc/common/section_cli_nova_usage_statistics.xml62(title) +msgid "To show instance usage statistics" +msgstr "" + +#: ./doc/common/section_cli_nova_usage_statistics.xml64(para) +msgid "Get CPU, memory, I/O, and network statistics for an instance." +msgstr "" + +#: ./doc/common/section_cli_nova_usage_statistics.xml66(para) +msgid "First, list instances:" +msgstr "" + +#: ./doc/common/section_cli_nova_usage_statistics.xml74(para) +msgid "Then, get diagnostic statistics:" +msgstr "" + +#: ./doc/common/section_cli_nova_usage_statistics.xml96(para) +msgid "Get summary statistics for each tenant:" +msgstr "" + +#: ./doc/common/section_cli_nova_userdata.xml7(title) +msgid "Provide user data to instances" +msgstr "" + +#: ./doc/common/section_cli_nova_userdata.xml8(para) +msgid "" +"User data is a special key in " +"the metadata service that holds a file that cloud-aware applications in the " +"guest instance can access. For example the cloudinit" +" system is a Ubuntu open source package that handles early initialization of" +" a cloud instance and that makes use of user data." +msgstr "" + +#: ./doc/common/section_cli_nova_userdata.xml17(para) +msgid "" +"You can place user data in a local file and pass it through the --user-data <user-data-file> parameter at instance " +"creation:" +msgstr "" + +#. ... Old module003-ch009-replication edited, renamed, and stored in +#. doc/common for use by both Cloud Admin and Operator Training Guides... +#: ./doc/common/section_objectstorage-replication.xml7(title) +#: ./doc/common/section_objectstorage-components.xml193(title) +msgid "Replication" +msgstr "" + +#: ./doc/common/section_objectstorage-replication.xml8(para) +msgid "" +"Because each replica in Object Storage functions independently and clients " +"generally require only a simple majority of nodes to respond to consider an " +"operation successful, transient failures like network partitions can quickly" +" cause replicas to diverge. These differences are eventually reconciled by " +"asynchronous, peer-to-peer replicator processes. The replicator processes " +"traverse their local file systems and concurrently perform operations in a " +"manner that balances load across physical disks." +msgstr "" + +#: ./doc/common/section_objectstorage-replication.xml17(para) +msgid "" +"Replication uses a push model, with records and files generally only being " +"copied from local to remote replicas. This is important because data on the " +"node might not belong there (as in the case of hand offs and ring changes), " +"and a replicator cannot know which data it should pull in from elsewhere in " +"the cluster. Any node that contains data must ensure that data gets to where" +" it belongs. The ring handles replica placement." +msgstr "" + +#: ./doc/common/section_objectstorage-replication.xml25(para) +msgid "" +"To replicate deletions in addition to creations, every deleted record or " +"file in the system is marked by a tombstone. The replication process cleans " +"up tombstones after a time period known as the consistency window. This window defines the " +"duration of the replication and how long transient failure can remove a node" +" from the cluster. Tombstone cleanup must be tied to replication to reach " +"replica convergence." +msgstr "" + +#: ./doc/common/section_objectstorage-replication.xml33(para) +msgid "" +"If a replicator detects that a remote drive has failed, the replicator uses " +"the get_more_nodes interface for the ring to choose an " +"alternate node with which to synchronize. The replicator can maintain " +"desired levels of replication during disk failures, though some replicas " +"might not be in an immediately usable location." +msgstr "" + +#: ./doc/common/section_objectstorage-replication.xml40(para) +msgid "" +"The replicator does not maintain desired levels of replication when failures" +" such as entire node failures occur; most failures are transient." +msgstr "" + +#: ./doc/common/section_objectstorage-replication.xml44(para) +msgid "The main replication types are:" +msgstr "" + +#: ./doc/common/section_objectstorage-replication.xml47(para) +msgid "" +"Database replication. Replicates " +"containers and objects." +msgstr "" + +#: ./doc/common/section_objectstorage-replication.xml52(para) +msgid "" +"Object replication. Replicates object " +"data." +msgstr "" + +#: ./doc/common/section_objectstorage-replication.xml57(title) +msgid "Database replication" +msgstr "" + +#: ./doc/common/section_objectstorage-replication.xml58(para) +msgid "" +"Database replication completes a low-cost hash comparison to determine " +"whether two replicas already match. Normally, this check can quickly verify " +"that most databases in the system are already synchronized. If the hashes " +"differ, the replicator synchronizes the databases by sharing records added " +"since the last synchronization point." +msgstr "" + +#: ./doc/common/section_objectstorage-replication.xml65(para) +msgid "" +"This synchronization point is a high water mark that notes the last record " +"at which two databases were known to be synchronized, and is stored in each " +"database as a tuple of the remote database ID and record ID. Database IDs " +"are unique across all replicas of the database, and record IDs are " +"monotonically increasing integers. After all new records are pushed to the " +"remote database, the entire synchronization table of the local database is " +"pushed, so the remote database can guarantee that it is synchronized with " +"everything with which the local database was previously synchronized." +msgstr "" + +#: ./doc/common/section_objectstorage-replication.xml76(para) +msgid "" +"If a replica is missing, the whole local database file is transmitted to the" +" peer by using rsync(1) and is assigned a new unique ID." +msgstr "" + +#: ./doc/common/section_objectstorage-replication.xml79(para) +msgid "" +"In practice, database replication can process hundreds of databases per " +"concurrency setting per second (up to the number of available CPUs or disks)" +" and is bound by the number of database transactions that must be performed." +msgstr "" + +#: ./doc/common/section_objectstorage-replication.xml86(title) +msgid "Object replication" +msgstr "" + +#: ./doc/common/section_objectstorage-replication.xml87(para) +msgid "" +"The initial implementation of object replication performed an rsync to push " +"data from a local partition to all remote servers where it was expected to " +"reside. While this worked at small scale, replication times skyrocketed once" +" directory structures could no longer be held in RAM. This scheme was " +"modified to save a hash of the contents for each suffix directory to a per-" +"partition hashes file. The hash for a suffix directory is no longer valid " +"when the contents of that suffix directory is modified." +msgstr "" + +#: ./doc/common/section_objectstorage-replication.xml96(para) +msgid "" +"The object replication process reads in hash files and calculates any " +"invalidated hashes. Then, it transmits the hashes to each remote server that" +" should hold the partition, and only suffix directories with differing " +"hashes on the remote server are rsynced. After pushing files to the remote " +"server, the replication process notifies it to recalculate hashes for the " +"rsynced suffix directories." +msgstr "" + +#: ./doc/common/section_objectstorage-replication.xml104(para) +msgid "" +"The number of uncached directories that object replication must traverse, " +"usually as a result of invalidated suffix directory hashes, impedes " +"performance. To provide acceptable replication speeds, object replication is" +" designed to invalidate around 2 percent of the hash space on a normal node " +"each day." +msgstr "" + +#: ./doc/common/section_cli_nova_reboot.xml5(title) +msgid "Reboot an instance" +msgstr "" + +#: ./doc/common/section_cli_nova_reboot.xml6(para) +msgid "" +"You can soft or hard reboot a running instance. A soft reboot attempts a " +"graceful shut down and restart of the instance. A hard reboot power cycles " +"the instance." +msgstr "" + +#: ./doc/common/section_cli_nova_reboot.xml9(para) +msgid "By default, when you reboot a server, it is a soft reboot." +msgstr "" + +#: ./doc/common/section_cli_nova_reboot.xml10(replaceable) +#: ./doc/common/section_cli_nova_reboot.xml12(replaceable) +#: ./doc/common/section_cli_nova_startstop.xml14(replaceable) +#: ./doc/common/section_cli_nova_startstop.xml19(replaceable) +#: ./doc/common/section_cli_nova_startstop.xml36(replaceable) +#: ./doc/common/section_cli_nova_startstop.xml40(replaceable) +msgid "SERVER" +msgstr "" + +#: ./doc/common/section_cli_nova_reboot.xml11(para) +msgid "" +"To perform a hard reboot, pass the --hard parameter, " +"as follows:" +msgstr "" + +#. ... Old module003-ch005-the-ring edited, renamed, and stored in doc/common +#. for use by both Cloud Admin and Operator Training Guides... +#: ./doc/common/section_objectstorage-ringbuilder.xml7(title) +msgid "Ring-builder" +msgstr "" + +#: ./doc/common/section_objectstorage-ringbuilder.xml8(para) +msgid "" +"Use the swift-ring-builder utility to build and manage rings. This utility " +"assigns partitions to devices and writes an optimized Python structure to a " +"gzipped, serialized file on disk for transmission to the servers. The server" +" processes occasionally check the modification time of the file and reload " +"in-memory copies of the ring structure as needed. If you use a slightly " +"older version of the ring, one of the three replicas for a partition subset " +"will be incorrect because of the way the ring-builder manages changes to the" +" ring. You can work around this issue." +msgstr "" + +#: ./doc/common/section_objectstorage-ringbuilder.xml18(para) +msgid "" +"The ring-builder also keeps its own builder file with the ring information " +"and additional data required to build future rings. It is very important to " +"keep multiple backup copies of these builder files. One option is to copy " +"the builder files out to every server while copying the ring files " +"themselves. Another is to upload the builder files into the cluster itself. " +"If you lose the builder file, you have to create a new ring from scratch. " +"Nearly all partitions would be assigned to different devices and, therefore," +" nearly all of the stored data would have to be replicated to new locations." +" So, recovery from a builder file loss is possible, but data would be " +"unreachable for an extended time." +msgstr "" + +#: ./doc/common/section_objectstorage-ringbuilder.xml31(title) +msgid "Ring data structure" +msgstr "" + +#: ./doc/common/section_objectstorage-ringbuilder.xml32(para) +msgid "" +"The ring data structure consists of three top level fields: a list of " +"devices in the cluster, a list of lists of device ids indicating partition " +"to device assignments, and an integer indicating the number of bits to shift" +" an MD5 hash to calculate the partition for the hash." +msgstr "" + +#: ./doc/common/section_objectstorage-ringbuilder.xml39(title) +msgid "Partition assignment list" +msgstr "" + +#: ./doc/common/section_objectstorage-ringbuilder.xml40(para) +msgid "" +"This is a list of array(‘H’) of devices ids. The " +"outermost list contains an array(‘H’) for each replica. " +"Each array(‘H’) has a length equal to the partition count" +" for the ring. Each integer in the array(‘H’) is an index" +" into the above list of devices. The partition list is known internally to " +"the Ring class as _replica2part2dev_id." +msgstr "" + +#: ./doc/common/section_objectstorage-ringbuilder.xml49(para) +msgid "" +"So, to create a list of device dictionaries assigned to a partition, the " +"Python code would look like: " +msgstr "" + +#: ./doc/common/section_objectstorage-ringbuilder.xml53(para) +msgid "" +"That code is a little simplistic because it does not account for the removal" +" of duplicate devices. If a ring has more replicas than devices, a partition" +" will have more than one replica on a device." +msgstr "" + +#: ./doc/common/section_objectstorage-ringbuilder.xml57(para) +msgid "" +"array(‘H’) is used for memory conservation as there may " +"be millions of partitions." +msgstr "" + +#: ./doc/common/section_objectstorage-ringbuilder.xml62(title) +msgid "Replica counts" +msgstr "" + +#: ./doc/common/section_objectstorage-ringbuilder.xml63(para) +msgid "" +"To support the gradual change in replica counts, a ring can have a real " +"number of replicas and is not restricted to an integer number of replicas." +msgstr "" + +#: ./doc/common/section_objectstorage-ringbuilder.xml66(para) +msgid "" +"A fractional replica count is for the whole ring and not for individual " +"partitions. It indicates the average number of replicas for each partition. " +"For example, a replica count of 3.2 means that 20 percent of partitions have" +" four replicas and 80 percent have three replicas." +msgstr "" + +#: ./doc/common/section_objectstorage-ringbuilder.xml71(para) +msgid "The replica count is adjustable." +msgstr "" + +#: ./doc/common/section_objectstorage-ringbuilder.xml72(para) +msgid "Example:" +msgstr "" + +#: ./doc/common/section_objectstorage-ringbuilder.xml75(para) +msgid "" +"You must rebalance the replica ring in globally distributed clusters. " +"Operators of these clusters generally want an equal number of replicas and " +"regions. Therefore, when an operator adds or removes a region, the operator " +"adds or removes a replica. Removing unneeded replicas saves on the cost of " +"disks." +msgstr "" + +#: ./doc/common/section_objectstorage-ringbuilder.xml81(para) +msgid "" +"You can gradually increase the replica count at a rate that does not " +"adversely affect cluster performance." +msgstr "" + +#: ./doc/common/section_objectstorage-ringbuilder.xml92(para) +msgid "" +"Changes take effect after the ring is rebalanced. Therefore, if you intend " +"to change from 3 replicas to 3.01 but you accidentally type " +"2.01, no data is lost." +msgstr "" + +#: ./doc/common/section_objectstorage-ringbuilder.xml97(replaceable) +msgid "X.builder" +msgstr "" + +#: ./doc/common/section_objectstorage-ringbuilder.xml96(para) +msgid "" +"Additionally, can now take a decimal argument for the " +"number of replicas." +msgstr "" + +#: ./doc/common/section_objectstorage-ringbuilder.xml102(title) +msgid "Partition shift value" +msgstr "" + +#: ./doc/common/section_objectstorage-ringbuilder.xml103(para) +msgid "" +"The partition shift value is known internally to the Ring class as " +"_part_shift. This value is used to shift an MD5 hash to " +"calculate the partition where the data for that hash should reside. Only the" +" top four bytes of the hash is used in this process. For example, to compute" +" the partition for the /account/container/object path, " +"the Python code might look like the following code: " +msgstr "" + +#: ./doc/common/section_objectstorage-ringbuilder.xml114(para) +msgid "" +"For a ring generated with part_power P, the partition shift value is " +"32 - P." +msgstr "" + +#: ./doc/common/section_objectstorage-ringbuilder.xml118(title) +msgid "Build the ring" +msgstr "" + +#: ./doc/common/section_objectstorage-ringbuilder.xml119(para) +msgid "The ring builder process includes these high-level steps:" +msgstr "" + +#: ./doc/common/section_objectstorage-ringbuilder.xml123(para) +msgid "" +"The utility calculates the number of partitions to assign to each device " +"based on the weight of the device. For example, for a partition at the power" +" of 20, the ring has 1,048,576 partitions. One thousand devices of equal " +"weight will each want 1,048.576 partitions. The devices are sorted by the " +"number of partitions they desire and kept in order throughout the " +"initialization process." +msgstr "" + +#: ./doc/common/section_objectstorage-ringbuilder.xml133(para) +msgid "" +"Each device is also assigned a random tiebreaker value that is used when two" +" devices desire the same number of partitions. This tiebreaker is not stored" +" on disk anywhere, and so two different rings created with the same " +"parameters will have different partition assignments. For repeatable " +"partition assignments, RingBuilder.rebalance() takes an " +"optional seed value that seeds the Python pseudo-random number generator." +msgstr "" + +#: ./doc/common/section_objectstorage-ringbuilder.xml147(para) +msgid "" +"The ring builder assigns each partition replica to the device that requires " +"most partitions at that point while keeping it as far away as possible from " +"other replicas. The ring builder prefers to assign a replica to a device in " +"a region that does not already have a replica. If no such region is " +"available, the ring builder searches for a device in a different zone, or on" +" a different server. If it does not find one, it looks for a device with no " +"replicas. Finally, if all options are exhausted, the ring builder assigns " +"the replica to the device that has the fewest replicas already assigned." +msgstr "" + +#: ./doc/common/section_objectstorage-ringbuilder.xml161(para) +msgid "" +"The ring builder assigns multiple replicas to one device only if the ring " +"has fewer devices than it has replicas." +msgstr "" + +#: ./doc/common/section_objectstorage-ringbuilder.xml167(para) +msgid "" +"When building a new ring from an old ring, the ring builder recalculates the" +" desired number of partitions that each device wants." +msgstr "" + +#: ./doc/common/section_objectstorage-ringbuilder.xml176(para) +msgid "" +"The ring builder unassigns any assigned partitions from any removed devices " +"and adds these partitions to the gathered list." +msgstr "" + +#: ./doc/common/section_objectstorage-ringbuilder.xml182(para) +msgid "" +"The ring builder unassigns any partition replicas that can be spread out for" +" better durability and adds these partitions to the gathered list." +msgstr "" + +#: ./doc/common/section_objectstorage-ringbuilder.xml189(para) +msgid "" +"The ring builder unassigns random partitions from any devices that have more" +" partitions than they need and adds these partitions to the gathered list." +msgstr "" + +#: ./doc/common/section_objectstorage-ringbuilder.xml172(para) +msgid "" +"The ring builder unassigns partitions and gathers these partitions for " +"reassignment, as follows: " +msgstr "" + +#: ./doc/common/section_objectstorage-ringbuilder.xml199(para) +msgid "" +"The ring builder reassigns the gathered partitions to devices by using a " +"similar method to the one described previously." +msgstr "" + +#: ./doc/common/section_objectstorage-ringbuilder.xml204(para) +msgid "" +"When the ring builder reassigns a replica to a partition, the ring builder " +"records the time of the reassignment. The ring builder uses this value when " +"it gathers partitions for reassignment so that no partition is moved twice " +"in a configurable amount of time. The RingBuilder class knows this " +"configurable amount of time as min_part_hours. The ring " +"builder ignores this restriction for replicas of partitions on removed " +"devices because removal of a device happens on device failure only, and " +"reassignment is the only choice." +msgstr "" + +#: ./doc/common/section_objectstorage-ringbuilder.xml218(para) +msgid "" +"Theses steps do not always perfectly rebalance a ring due to the random " +"nature of gathering partitions for reassignment. To help reach a more " +"balanced ring, the rebalance process is repeated until near perfect (less " +"than 1 percent off) or when the balance does not improve by at least 1 " +"percent (indicating we probably cannot get perfect balance due to wildly " +"imbalanced zones or too many partitions recently moved)." +msgstr "" + +#. ... Old module003-ch008-account-reaper edited, renamed, and stored in +#. doc/common for use by both Cloud Admin and Operator Training Guides... +#: ./doc/common/section_objectstorage-account-reaper.xml8(title) +msgid "Account reaper" +msgstr "" + +#: ./doc/common/section_objectstorage-account-reaper.xml9(para) +msgid "" +"In the background, the account reaper removes data from the deleted " +"accounts." +msgstr "" + +#: ./doc/common/section_objectstorage-account-reaper.xml10(para) +msgid "" +"A reseller marks an account for deletion by issuing a DELETE " +"request on the account’s storage URL. This action sets the " +"status column of the account_stat table in the account database" +" and replicas to DELETED, marking the account's data for " +"deletion." +msgstr "" + +#: ./doc/common/section_objectstorage-account-reaper.xml18(para) +msgid "" +"It's on the developers' to-do list to write a utility that performs this " +"task, preferably through a ReST call." +msgstr "" + +#: ./doc/common/section_objectstorage-account-reaper.xml13(para) +msgid "" +"Typically, a specific retention time or undelete are not provided. However, " +"you can set a delay_reaping value in the [account-" +"reaper] section of the account-server.conf to delay the actual " +"deletion of data. At this time, to undelete you have to update the account " +"database replicas directly, setting the status column to an empty string and" +" updating the put_timestamp to be greater than the delete_timestamp. " +"" +msgstr "" + +#: ./doc/common/section_objectstorage-account-reaper.xml21(para) +msgid "" +"The account reaper runs on each account server and scans the server " +"occasionally for account databases marked for deletion. It only fires up on " +"the accounts for which the server is the primary node, so that multiple " +"account servers aren’t trying to do it simultaneously. Using multiple " +"servers to delete one account might improve the deletion speed but requires " +"coordination to avoid duplication. Speed really is not a big concern with " +"data deletion, and large accounts aren’t deleted often." +msgstr "" + +#: ./doc/common/section_objectstorage-account-reaper.xml27(para) +msgid "" +"Deleting an account is simple. For each account container, all objects are " +"deleted and then the container is deleted. Deletion requests that fail will " +"not stop the overall process but will cause the overall process to fail " +"eventually (for example, if an object delete times out, you will not be able" +" to delete the container or the account). The account reaper keeps trying to" +" delete an account until it is empty, at which point the database reclaim " +"process within the db_replicator will remove the database files." +msgstr "" + +#: ./doc/common/section_objectstorage-account-reaper.xml33(para) +msgid "" +"A persistent error state may prevent the deletion of an object or container." +" If this happens, you will see a message such as “Account <name>" +" has not been reaped since <date>” in the log. You can control " +"when this is logged with the reap_warn_after value in the [account-reaper] section of the account-server.conf file. The " +"default value is 30 days." +msgstr "" + +#: ./doc/common/section_support-compute.xml6(title) +msgid "Troubleshoot Compute" +msgstr "" + +#: ./doc/common/section_support-compute.xml7(para) +msgid "" +"Common problems for Compute typically involve misconfigured networking or " +"credentials that are not sourced properly in the environment. Also, most " +"flat networking configurations do not enable or " +" from a compute node to the instances that run on that node." +" Another common problem is trying to run 32-bit images on a 64-bit compute " +"node. This section shows you how to troubleshoot Compute." +msgstr "" + +#: ./doc/common/section_support-compute.xml16(title) +msgid "Compute log files" +msgstr "" + +#: ./doc/common/section_support-compute.xml17(para) +msgid "" +"Compute stores a log file for each service in " +"/var/log/nova. For example, nova-" +"compute.log is the log for the nova-compute service. You can set the following options to " +"format log strings for the nova.log module in the " +"nova.conf file:" +msgstr "" + +#: ./doc/common/section_support-compute.xml26(literal) +msgid "logging_context_format_string" +msgstr "" + +#: ./doc/common/section_support-compute.xml29(literal) +msgid "logging_default_format_string" +msgstr "" + +#: ./doc/common/section_support-compute.xml32(para) +msgid "" +"If the log level is set to debug, you can also specify " +"logging_debug_format_suffix to append extra formatting. " +"For information about what variables are available for the formatter see: " +"http://docs.python.org/library/logging.html#formatter." +msgstr "" + +#: ./doc/common/section_support-compute.xml39(para) +msgid "" +"You have two options for logging for OpenStack Compute based on " +"configuration settings. In nova.conf, include the " +"logfile option to enable logging. Alternatively you can " +"set use_syslog=1 so that the nova daemon logs to syslog." +msgstr "" + +#: ./doc/common/section_support-compute.xml47(title) +msgid "Common errors and fixes for Compute" +msgstr "" + +#: ./doc/common/section_support-compute.xml48(para) +msgid "" +"The ask.openstack.org site offers a " +"place to ask and answer questions, and you can also mark questions as " +"frequently asked questions. This section describes some errors people have " +"posted previously. Bugs are constantly being fixed, so online resources are " +"a great way to get the most up-to-date errors and fixes." +msgstr "" + +#: ./doc/common/section_support-compute.xml56(title) +msgid "Credential errors, 401, and 403 forbidden errors" +msgstr "" + +#: ./doc/common/section_support-compute.xml63(para) +msgid "" +"Manual method. Get get the " +"novarc file from the project ZIP file, save existing " +"credentials in case of override. and manually source the " +"novarc file." +msgstr "" + +#: ./doc/common/section_support-compute.xml73(para) +msgid "" +"Script method. Generates " +"novarc from the project ZIP file and sources it for " +"you." +msgstr "" + +#: ./doc/common/section_support-compute.xml58(para) +msgid "" +"Missing credentials cause a " +"403forbidden error. To resolve" +" this issue, use one of these methods:" +msgstr "" + +#: ./doc/common/section_support-compute.xml80(para) +msgid "" +"When you run nova-api the first " +"time, it generates the certificate authority information, including " +"openssl.cnf. If you start the CA services before this, " +"you might not be able to create your ZIP file. Restart the services. When " +"your CA information is available, create your ZIP file." +msgstr "" + +#: ./doc/common/section_support-compute.xml88(para) +msgid "" +"Also, check your HTTP proxy settings to see whether they cause problems with" +" novarc creation." +msgstr "" + +#: ./doc/common/section_support-compute.xml93(title) +msgid "Instance errors" +msgstr "" + +#: ./doc/common/section_support-compute.xml94(para) +msgid "" +"Sometimes a particular instance shows pending or you " +"cannot SSH to it. Sometimes the image itself is the problem. For example, " +"when you use flat manager networking, you do not have a DHCP server and " +"certain images do not support interface injection; you cannot connect to " +"them. The fix for this problem is to use an image that does support this " +"method, such as Ubuntu, which obtains an IP address correctly with " +"FlatManager network settings." +msgstr "" + +#: ./doc/common/section_support-compute.xml104(para) +msgid "" +"To troubleshoot other possible problems with an instance, such as an " +"instance that stays in a spawning state, check the directory for the " +"particular instance under /var/lib/nova/instances on " +"the nova-compute host and make " +"sure that these files are present:" +msgstr "" + +#: ./doc/common/section_support-compute.xml113(filename) +msgid "libvirt.xml" +msgstr "" + +#: ./doc/common/section_support-compute.xml116(filename) +msgid "disk" +msgstr "" + +#: ./doc/common/section_support-compute.xml119(filename) +msgid "disk-raw" +msgstr "" + +#: ./doc/common/section_support-compute.xml122(filename) +msgid "kernel" +msgstr "" + +#: ./doc/common/section_support-compute.xml125(filename) +msgid "ramdisk" +msgstr "" + +#: ./doc/common/section_support-compute.xml128(para) +msgid "After the instance starts, console.log" +msgstr "" + +#: ./doc/common/section_support-compute.xml132(para) +msgid "" +"If any files are missing, empty, or very small, the nova-compute service did not successfully " +"download the images from the Image Service." +msgstr "" + +#: ./doc/common/section_support-compute.xml137(para) +msgid "" +"Also check nova-compute.log for exceptions. Sometimes " +"they do not appear in the console output." +msgstr "" + +#: ./doc/common/section_support-compute.xml140(para) +msgid "" +"Next, check the log file for the instance in the " +"/var/log/libvirt/qemu directory to see if it exists and" +" has any useful error messages in it." +msgstr "" + +#: ./doc/common/section_support-compute.xml144(para) +msgid "" +"Finally, from the /var/lib/nova/instances directory for" +" the instance, see if this command returns an error:" +msgstr "" + +#: ./doc/common/section_support-compute.xml152(title) +msgid "Reset the state of an instance" +msgstr "" + +#: ./doc/common/section_support-compute.xml153(para) +msgid "" +"If an instance remains in an intermediate state, such as " +"deleting, you can use the command to " +"manually reset the state of an instance to an error state. You can then " +"delete the instance. For example:" +msgstr "" + +#: ./doc/common/section_support-compute.xml160(para) +msgid "" +"You can also use the --active parameter to force the " +"instance back to an active state instead of an error state. For example:" +msgstr "" + +#: ./doc/common/section_support-compute.xml166(title) +msgid "Injection problems" +msgstr "" + +#: ./doc/common/section_support-compute.xml167(para) +msgid "" +"If instances do not boot or boot slowly, investigate file injection as a " +"cause." +msgstr "" + +#: ./doc/common/section_support-compute.xml169(para) +msgid "" +"To disable injection in libvirt, set " +" to -2." +msgstr "" + +#: ./doc/common/section_support-compute.xml173(para) +msgid "" +"If you have not enabled the configuration drive and you want to make user-" +"specified files available from the metadata server for to improve " +"performance and avoid boot failure if injection fails, you must disable " +"injection." +msgstr "" + +#: ./doc/common/section_keystone-sample-conf-files.xml6(title) +msgid "Identity Service sample configuration files" +msgstr "" + +#: ./doc/common/section_keystone-sample-conf-files.xml10(filename) +msgid "etc/keystone.conf.sample" +msgstr "" + +#: ./doc/common/section_keystone-sample-conf-files.xml17(filename) +msgid "etc/keystone-paste.ini" +msgstr "" + +#: ./doc/common/section_keystone-sample-conf-files.xml24(literal) +msgid "etc/logging.conf.sample" +msgstr "" + +#: ./doc/common/section_identity-configure.xml6(title) +msgid "Identity Service configuration files" +msgstr "" + +#: ./doc/common/section_identity-configure.xml9(term) +msgid "keystone.conf" +msgstr "" + +#: ./doc/common/section_identity-configure.xml11(para) +msgid "" +"The Identity Service /etc/keystone/keystone.conf " +"configuration file is an INI-format file with sections." +msgstr "" + +#: ./doc/common/section_identity-configure.xml15(para) +msgid "" +"The [DEFAULT] section configures general configuration " +"values." +msgstr "" + +#: ./doc/common/section_identity-configure.xml17(para) +msgid "" +"Specific sections, such as the [sql] and " +"[ec2] sections, configure individual services." +msgstr "" + +#: ./doc/common/section_identity-configure.xml21(caption) +msgid "keystone.conf file sections" +msgstr "" + +#: ./doc/common/section_identity-configure.xml26(td) +msgid "Section" +msgstr "" + +#: ./doc/common/section_identity-configure.xml32(literal) +#: ./doc/common/tables/glance-policy.xml19(th) +#: ./doc/common/tables/nova-ipv6.xml19(th) +#: ./doc/common/tables/cinder-eqlx.xml19(th) +#: ./doc/common/tables/glance-qpid.xml19(th) +#: ./doc/common/tables/swift-container-server-DEFAULT.xml7(literal) +#: ./doc/common/tables/nova-volumes.xml19(th) +#: ./doc/common/tables/glance-gridfs.xml19(th) +#: ./doc/common/tables/glance-filesystem.xml19(th) +#: ./doc/common/tables/cinder-storage_gpfs.xml19(th) +#: ./doc/common/tables/cinder-nexenta_iscsi.xml19(th) +#: ./doc/common/tables/nova-ca.xml19(th) +#: ./doc/common/tables/cinder-huawei.xml19(th) +#: ./doc/common/tables/nova-glance.xml19(th) +#: ./doc/common/tables/nova-neutron.xml19(th) +#: ./doc/common/tables/cinder-backups_ceph.xml19(th) +#: ./doc/common/tables/nova-metadata.xml19(th) +#: ./doc/common/tables/glance-s3.xml19(th) +#: ./doc/common/tables/cinder-block-device.xml19(th) +#: ./doc/common/tables/cinder-zones.xml19(th) +#: ./doc/common/tables/cinder-netapp_7mode_iscsi.xml19(th) +#: ./doc/common/tables/cinder-compute.xml19(th) +#: ./doc/common/tables/cinder-lvm.xml19(th) +#: ./doc/common/tables/cinder-storage_nfs.xml19(th) +#: ./doc/common/tables/nova-hypervisor.xml19(th) +#: ./doc/common/tables/cinder-quota.xml19(th) +#: ./doc/common/tables/swift-object-expirer-DEFAULT.xml7(literal) +#: ./doc/common/tables/nova-console.xml19(th) +#: ./doc/common/tables/nova-common.xml19(th) +#: ./doc/common/tables/glance-zmq.xml19(th) +#: ./doc/common/tables/nova-testing.xml19(th) +#: ./doc/common/tables/cinder-backups.xml19(th) +#: ./doc/common/tables/nova-s3.xml19(th) +#: ./doc/common/tables/cinder-rpc.xml19(th) +#: ./doc/common/tables/cinder-api.xml19(th) +#: ./doc/common/tables/cinder-windows.xml19(th) +#: ./doc/common/tables/cinder-san.xml19(th) +#: ./doc/common/tables/nova-db.xml19(th) +#: ./doc/common/tables/glance-logging.xml19(th) +#: ./doc/common/tables/glance-wsgi.xml19(th) +#: ./doc/common/tables/nova-periodic.xml19(th) +#: ./doc/common/tables/cinder-images.xml19(th) +#: ./doc/common/tables/glance-rbd.xml19(th) +#: ./doc/common/tables/cinder-hp3par.xml19(th) +#: ./doc/common/tables/cinder-storage_ceph.xml19(th) +#: ./doc/common/tables/nova-livemigration.xml19(th) +#: ./doc/common/tables/nova-ldap.xml19(th) +#: ./doc/common/tables/nova-fping.xml19(th) +#: ./doc/common/tables/cinder-netapp_cdot_iscsi.xml19(th) +#: ./doc/common/tables/nova-ec2.xml19(th) +#: ./doc/common/tables/swift-object-server-DEFAULT.xml7(literal) +#: ./doc/common/tables/cinder-nexenta_nfs.xml19(th) +#: ./doc/common/tables/nova-policy.xml19(th) +#: ./doc/common/tables/glance-rpc.xml19(th) +#: ./doc/common/tables/nova-authentication.xml19(th) +#: ./doc/common/tables/cinder-vmware.xml19(th) +#: ./doc/common/tables/glance-sheepdog.xml19(th) +#: ./doc/common/tables/glance-swift.xml19(th) +#: ./doc/common/tables/swift-account-server-DEFAULT.xml7(literal) +#: ./doc/common/tables/nova-libvirt.xml19(th) +#: ./doc/common/tables/cinder-backups_swift.xml19(th) +#: ./doc/common/tables/nova-pci.xml19(th) +#: ./doc/common/tables/glance-imagecache.xml19(th) +#: ./doc/common/tables/cinder-storage.xml19(th) +#: ./doc/common/tables/nova-vpn.xml19(th) +#: ./doc/common/tables/nova-wsgi.xml19(th) +#: ./doc/common/tables/cinder-storage_glusterfs.xml19(th) +#: ./doc/common/tables/nova-availabilityzones.xml19(th) +#: ./doc/common/tables/nova-vnc.xml19(th) +#: ./doc/common/tables/cinder-coraid.xml19(th) +#: ./doc/common/tables/nova-logging.xml19(th) +#: ./doc/common/tables/nova-xen.xml19(th) +#: ./doc/common/tables/cinder-netapp_7mode_nfs.xml19(th) +#: ./doc/common/tables/glance-common.xml19(th) +#: ./doc/common/tables/nova-network.xml19(th) +#: ./doc/common/tables/cinder-scality.xml19(th) +#: ./doc/common/tables/cinder-common.xml19(th) +#: ./doc/common/tables/nova-configdrive.xml19(th) +#: ./doc/common/tables/cinder-database.xml19(th) +#: ./doc/common/tables/nova-zeromq.xml19(th) +#: ./doc/common/tables/glance-testing.xml19(th) +#: ./doc/common/tables/glance-registry.xml19(th) +#: ./doc/common/tables/glance-rabbitmq.xml19(th) +#: ./doc/common/tables/cinder-backups_tsm.xml19(th) +#: ./doc/common/tables/nova-qpid.xml19(th) +#: ./doc/common/tables/cinder-log.xml19(th) +#: ./doc/common/tables/swift-proxy-server-DEFAULT.xml7(literal) +#: ./doc/common/tables/nova-scheduling.xml19(th) +#: ./doc/common/tables/cinder-xiv.xml19(th) +#: ./doc/common/tables/cinder-auth.xml19(th) +#: ./doc/common/tables/nova-kombu.xml19(th) +#: ./doc/common/tables/cinder-hds.xml19(th) +#: ./doc/common/tables/cinder-storwize.xml19(th) +#: ./doc/common/tables/cinder-solidfire.xml19(th) +#: ./doc/common/tables/glance-ssl.xml19(th) +#: ./doc/common/tables/glance-db.xml19(th) +#: ./doc/common/tables/nova-api.xml19(th) +#: ./doc/common/tables/cinder-san-solaris.xml19(th) +#: ./doc/common/tables/cinder-netapp_cdot_nfs.xml19(th) +#: ./doc/common/tables/nova-rpc.xml19(th) +#: ./doc/common/tables/glance-api.xml19(th) +#: ./doc/common/tables/cinder-scheduler.xml19(th) +#: ./doc/common/tables/glance-cinder.xml19(th) +#: ./doc/common/tables/nova-rabbitmq.xml19(th) +#: ./doc/common/tables/cinder-zadara.xml19(th) +#: ./doc/common/tables/nova-quota.xml19(th) +#: ./doc/common/tables/nova-conductor.xml19(th) +#: ./doc/common/tables/nova-compute.xml19(th) +#: ./doc/common/tables/cinder-storage_xen.xml19(th) +#: ./doc/common/tables/nova-xvpnvncproxy.xml19(th) +msgid "[DEFAULT]" +msgstr "" + +#: ./doc/common/section_identity-configure.xml33(td) +msgid "General configuration." +msgstr "" + +#: ./doc/common/section_identity-configure.xml36(literal) +msgid "[sql]" +msgstr "" + +#: ./doc/common/section_identity-configure.xml37(td) +msgid "Optional storage back-end configuration." +msgstr "" + +#: ./doc/common/section_identity-configure.xml40(literal) +msgid "[ec2]" +msgstr "" + +#: ./doc/common/section_identity-configure.xml41(td) +msgid "Amazon EC2 authentication driver configuration." +msgstr "" + +#: ./doc/common/section_identity-configure.xml44(literal) +msgid "[s3]" +msgstr "" + +#: ./doc/common/section_identity-configure.xml45(td) +msgid "Amazon S3 authentication driver configuration." +msgstr "" + +#: ./doc/common/section_identity-configure.xml48(literal) +msgid "[identity]" +msgstr "" + +#: ./doc/common/section_identity-configure.xml49(td) +msgid "Identity Service system driver configuration." +msgstr "" + +#: ./doc/common/section_identity-configure.xml52(literal) +msgid "[catalog]" +msgstr "" + +#: ./doc/common/section_identity-configure.xml53(td) +msgid "Service catalog driver configuration." +msgstr "" + +#: ./doc/common/section_identity-configure.xml56(literal) +msgid "[token]" +msgstr "" + +#: ./doc/common/section_identity-configure.xml57(td) +msgid "Token driver configuration." +msgstr "" + +#: ./doc/common/section_identity-configure.xml60(literal) +msgid "[policy]" +msgstr "" + +#: ./doc/common/section_identity-configure.xml61(td) +msgid "Policy system driver configuration for RBAC." +msgstr "" + +#: ./doc/common/section_identity-configure.xml64(literal) +msgid "[signing]" +msgstr "" + +#: ./doc/common/section_identity-configure.xml65(td) +msgid "Cryptographic signatures for PKI based tokens." +msgstr "" + +#: ./doc/common/section_identity-configure.xml68(literal) +#: ./doc/common/tables/nova-ca.xml62(th) +msgid "[ssl]" +msgstr "" + +#: ./doc/common/section_identity-configure.xml69(td) +msgid "SSL configuration." +msgstr "" + +#: ./doc/common/section_identity-configure.xml73(para) +msgid "" +"When you start the Identity Service, you can use the --config-" +"file parameter to specify a configuration file." +msgstr "" + +#: ./doc/common/section_identity-configure.xml76(para) +msgid "" +"If you do not specify a configuration file, the Identity Service looks for " +"the keystone.conf configuration file in these " +"directories in this order:" +msgstr "" + +#: ./doc/common/section_identity-configure.xml83(literal) +msgid "~/.keystone" +msgstr "" + +#: ./doc/common/section_identity-configure.xml88(literal) +msgid "~/" +msgstr "" + +#: ./doc/common/section_identity-configure.xml93(literal) +msgid "/etc/keystone" +msgstr "" + +#: ./doc/common/section_identity-configure.xml98(literal) +msgid "/etc" +msgstr "" + +#: ./doc/common/section_identity-configure.xml105(term) +msgid "keystone-paste.ini" +msgstr "" + +#: ./doc/common/section_identity-configure.xml107(para) +msgid "" +"The /etc/keystone/keystone-paste.ini file configures " +"the Identity Service WSGI middleware pipeline." +msgstr "" + +#: ./doc/common/section_keystone-ssl-config.xml7(title) +msgid "Configure the Identity Service with SSL" +msgstr "" + +#: ./doc/common/section_keystone-ssl-config.xml8(para) +msgid "You can configure the Identity Service to support two-way SSL." +msgstr "" + +#: ./doc/common/section_keystone-ssl-config.xml10(para) +msgid "You must obtain the x509 certificates externally and configure them." +msgstr "" + +#: ./doc/common/section_keystone-ssl-config.xml12(para) +msgid "" +"The Identity Service provides a set of sample certificates in the examples/pki/certs and examples/pki/private directories:" +msgstr "" + +#: ./doc/common/section_keystone-ssl-config.xml18(title) +msgid "Certificate types" +msgstr "" + +#: ./doc/common/section_keystone-ssl-config.xml20(term) +msgid "cacert.pem" +msgstr "" + +#: ./doc/common/section_keystone-ssl-config.xml22(para) +msgid "Certificate Authority chain to validate against." +msgstr "" + +#: ./doc/common/section_keystone-ssl-config.xml27(term) +msgid "ssl_cert.pem" +msgstr "" + +#: ./doc/common/section_keystone-ssl-config.xml29(para) +msgid "Public certificate for Identity Service server." +msgstr "" + +#: ./doc/common/section_keystone-ssl-config.xml34(term) +msgid "middleware.pem" +msgstr "" + +#: ./doc/common/section_keystone-ssl-config.xml36(para) +msgid "Public and private certificate for Identity Service middleware/client." +msgstr "" + +#: ./doc/common/section_keystone-ssl-config.xml41(term) +msgid "cakey.pem" +msgstr "" + +#: ./doc/common/section_keystone-ssl-config.xml43(para) +msgid "Private key for the CA." +msgstr "" + +#: ./doc/common/section_keystone-ssl-config.xml47(term) +msgid "ssl_key.pem" +msgstr "" + +#: ./doc/common/section_keystone-ssl-config.xml49(para) +msgid "Private key for the Identity Service server." +msgstr "" + +#: ./doc/common/section_keystone-ssl-config.xml55(para) +msgid "" +"You can choose names for these certificates. You can also combine the " +"public/private keys in the same file, if you wish. These certificates are " +"provided as an example." +msgstr "" + +#: ./doc/common/section_keystone-ssl-config.xml61(title) +msgid "SSL configuration" +msgstr "" + +#: ./doc/common/section_keystone-ssl-config.xml62(para) +msgid "" +"To enable SSL with client authentication, modify the " +"[ssl] section in the " +"etc/keystone.conf file. The following SSL configuration" +" example uses the included sample certificates:" +msgstr "" + +#: ./doc/common/section_keystone-ssl-config.xml74(title) +msgid "Options" +msgstr "" + +#: ./doc/common/section_keystone-ssl-config.xml76(para) +msgid "enable. True enables SSL. Default is False." +msgstr "" + +#: ./doc/common/section_keystone-ssl-config.xml80(para) +msgid "" +"certfile. Path to the Identity Service public certificate" +" file." +msgstr "" + +#: ./doc/common/section_keystone-ssl-config.xml84(para) +msgid "" +"keyfile. Path to the Identity Service private certificate" +" file. If you include the private key in the certfile, you can omit the " +"keyfile." +msgstr "" + +#: ./doc/common/section_keystone-ssl-config.xml90(para) +msgid "ca_certs. Path to the CA trust chain." +msgstr "" + +#: ./doc/common/section_keystone-ssl-config.xml94(para) +msgid "" +"cert_required. Requires client certificate. Default is " +"False." +msgstr "" + +#: ./doc/common/section_cli_nova_startstop.xml6(title) +msgid "Stop and start an instance" +msgstr "" + +#: ./doc/common/section_cli_nova_startstop.xml7(para) +msgid "Use one of the following methods to stop and start an instance." +msgstr "" + +#: ./doc/common/section_cli_nova_startstop.xml10(title) +msgid "Pause and un-pause an instance" +msgstr "" + +#: ./doc/common/section_cli_nova_startstop.xml13(para) +msgid "To pause a server, run the following command:" +msgstr "" + +#: ./doc/common/section_cli_nova_startstop.xml15(para) +msgid "" +"This command stores the state of the VM in RAM. A paused instance continues " +"to run in a frozen state." +msgstr "" + +#: ./doc/common/section_cli_nova_startstop.xml17(para) +msgid "To un-pause the server, run the following command:" +msgstr "" + +#: ./doc/common/section_cli_nova_startstop.xml24(title) +msgid "Suspend and resume an instance" +msgstr "" + +#: ./doc/common/section_cli_nova_startstop.xml26(para) +msgid "" +"Administrative users might want to suspend an infrequently used instance or " +"to perform system maintenance." +msgstr "" + +#: ./doc/common/section_cli_nova_startstop.xml29(para) +msgid "" +"When you suspend an instance, its VM state is stored on disk, all memory is " +"written to disk, and the virtual machine is stopped. Suspending an instance " +"is similar to placing a device in hibernation; memory and vCPUs become " +"available." +msgstr "" + +#: ./doc/common/section_cli_nova_startstop.xml34(para) +msgid "" +"To initiate a hypervisor-level suspend operation, run the following command:" +msgstr "" + +#: ./doc/common/section_cli_nova_startstop.xml39(para) +msgid "To resume a suspended server:" +msgstr "" + +#. When image changes, this message will be marked fuzzy or untranslated for +#. you. +#. It doesn't matter what you translate it to: it's not used at all. +#: ./doc/common/section_objectstorage-components.xml44(None) +msgid "" +"@@image: '../common/figures/objectstorage-buildingblocks.png'; " +"md5=ed79466c8464513dbeaf1e0954280e5e" +msgstr "" + +#. When image changes, this message will be marked fuzzy or untranslated for +#. you. +#. It doesn't matter what you translate it to: it's not used at all. +#: ./doc/common/section_objectstorage-components.xml87(None) +msgid "" +"@@image: '../common/figures/objectstorage-ring.png'; " +"md5=a94e26734cec6980c3684d9e824eac2d" +msgstr "" + +#. When image changes, this message will be marked fuzzy or untranslated for +#. you. +#. It doesn't matter what you translate it to: it's not used at all. +#: ./doc/common/section_objectstorage-components.xml127(None) +msgid "" +"@@image: '../common/figures/objectstorage-zones.png'; " +"md5=1b1dc0abe6ea0c516f22ce399deb75ed" +msgstr "" + +#. When image changes, this message will be marked fuzzy or untranslated for +#. you. +#. It doesn't matter what you translate it to: it's not used at all. +#: ./doc/common/section_objectstorage-components.xml145(None) +msgid "" +"@@image: '../common/figures/objectstorage-accountscontainers.png'; " +"md5=4b15e5a202db5bde53c9b369058aeab8" +msgstr "" + +#. When image changes, this message will be marked fuzzy or untranslated for +#. you. +#. It doesn't matter what you translate it to: it's not used at all. +#: ./doc/common/section_objectstorage-components.xml170(None) +msgid "" +"@@image: '../common/figures/objectstorage-partitions.png'; " +"md5=2c161c2e92d6fefc8140ec86e79e9492" +msgstr "" + +#. When image changes, this message will be marked fuzzy or untranslated for +#. you. +#. It doesn't matter what you translate it to: it's not used at all. +#: ./doc/common/section_objectstorage-components.xml196(None) +msgid "" +"@@image: '../common/figures/objectstorage-replication.png'; " +"md5=9d55594d7f445764569ab04d8d4373b2" +msgstr "" + +#. When image changes, this message will be marked fuzzy or untranslated for +#. you. +#. It doesn't matter what you translate it to: it's not used at all. +#: ./doc/common/section_objectstorage-components.xml223(None) +msgid "" +"@@image: '../common/figures/objectstorage-usecase.png'; " +"md5=07480e7175b383171173775fb96d70d7" +msgstr "" + +#. ... Old module003-ch004-swift-building-blocks edited, renamed, and stored +#. in doc/common for use by both Cloud Admin and Operator Training Guides... +#: ./doc/common/section_objectstorage-components.xml8(title) +msgid "Components" +msgstr "" + +#: ./doc/common/section_objectstorage-components.xml9(para) +msgid "" +"The components that enable Object Storage to deliver high availability, high" +" durability, and high concurrency are:" +msgstr "" + +#: ./doc/common/section_objectstorage-components.xml13(para) +msgid "" +"Proxy servers—Handle all of the incoming " +"API requests." +msgstr "" + +#: ./doc/common/section_objectstorage-components.xml17(para) +msgid "" +"Rings—Map logical names of data to " +"locations on particular disks." +msgstr "" + +#: ./doc/common/section_objectstorage-components.xml21(para) +msgid "" +"Zones—Isolate data from other zones. A " +"failure in one zone doesn’t impact the rest of the cluster because data is " +"replicated across zones." +msgstr "" + +#: ./doc/common/section_objectstorage-components.xml26(para) +msgid "" +"Accounts and containers—Each account and " +"container are individual databases that are distributed across the cluster. " +"An account database contains the list of containers in that account. A " +"container database contains the list of objects in that container." +msgstr "" + +#: ./doc/common/section_objectstorage-components.xml32(para) +msgid "Objects—The data itself." +msgstr "" + +#: ./doc/common/section_objectstorage-components.xml35(para) +msgid "" +"Partitions—A partition stores objects, " +"account databases, and container databases and helps manage locations where " +"data lives in the cluster." +msgstr "" + +#: ./doc/common/section_objectstorage-components.xml41(title) +msgid "Object Storage building blocks" +msgstr "" + +#: ./doc/common/section_objectstorage-components.xml49(title) +msgid "Proxy servers" +msgstr "" + +#: ./doc/common/section_objectstorage-components.xml50(para) +msgid "" +"Proxy servers are the public face of Object Storage and handle all of the " +"incoming API requests. Once a proxy server receives a request, it determines" +" the storage node based on the object's URL, for example, " +"https://swift.example.com/v1/account/container/object. Proxy servers also " +"coordinate responses, handle failures, and coordinate timestamps." +msgstr "" + +#: ./doc/common/section_objectstorage-components.xml55(para) +msgid "" +"Proxy servers use a shared-nothing architecture and can be scaled as needed " +"based on projected workloads. A minimum of two proxy servers should be " +"deployed for redundancy. If one proxy server fails, the others take over." +msgstr "" + +#: ./doc/common/section_objectstorage-components.xml60(title) +msgid "Rings" +msgstr "" + +#: ./doc/common/section_objectstorage-components.xml61(para) +msgid "" +"A ring represents a mapping between the names of entities stored on disk and" +" their physical locations. There are separate rings for accounts, " +"containers, and objects. When other components need to perform any operation" +" on an object, container, or account, they need to interact with the " +"appropriate ring to determine their location in the cluster." +msgstr "" + +#: ./doc/common/section_objectstorage-components.xml66(para) +msgid "" +"The ring maintains this mapping using zones, devices, partitions, and " +"replicas. Each partition in the ring is replicated, by default, three times " +"across the cluster, and partition locations are stored in the mapping " +"maintained by the ring. The ring is also responsible for determining which " +"devices are used for handoff in failure scenarios." +msgstr "" + +#: ./doc/common/section_objectstorage-components.xml71(para) +msgid "" +"Data can be isolated into zones in the ring. Each partition replica is " +"guaranteed to reside in a different zone. A zone could represent a drive, a " +"server, a cabinet, a switch, or even a data center." +msgstr "" + +#: ./doc/common/section_objectstorage-components.xml74(para) +msgid "" +"The partitions of the ring are equally divided among all of the devices in " +"the Object Storage installation. When partitions need to be moved around " +"(for example, if a device is added to the cluster), the ring ensures that a " +"minimum number of partitions are moved at a time, and only one replica of a " +"partition is moved at a time." +msgstr "" + +#: ./doc/common/section_objectstorage-components.xml78(para) +msgid "" +"Weights can be used to balance the distribution of partitions on drives " +"across the cluster. This can be useful, for example, when differently sized " +"drives are used in a cluster." +msgstr "" + +#: ./doc/common/section_objectstorage-components.xml81(para) +msgid "" +"The ring is used by the proxy server and several background processes (like " +"replication)." +msgstr "" + +#: ./doc/common/section_objectstorage-components.xml84(title) +msgid "The ring" +msgstr "" + +#: ./doc/common/section_objectstorage-components.xml91(para) +msgid "" +"These rings are externally managed, in that the server processes themselves " +"do not modify the rings, they are instead given new rings modified by other " +"tools." +msgstr "" + +#: ./doc/common/section_objectstorage-components.xml93(para) +msgid "" +"The ring uses a configurable number of bits from a path’s MD5 hash as a " +"partition index that designates a device. The number of bits kept from the " +"hash is known as the partition power, and 2 to the partition power indicates" +" the partition count. Partitioning the full MD5 hash ring allows other parts" +" of the cluster to work in batches of items at once which ends up either " +"more efficient or at least less complex than working with each item " +"separately or the entire cluster all at once." +msgstr "" + +#: ./doc/common/section_objectstorage-components.xml102(para) +msgid "" +"Another configurable value is the replica count, which indicates how many of" +" the partition-device assignments make up a single ring. For a given " +"partition number, each replica’s device will not be in the same zone as any " +"other replica's device. Zones can be used to group devices based on physical" +" locations, power separations, network separations, or any other attribute " +"that would improve the availability of multiple replicas at the same time." +msgstr "" + +#: ./doc/common/section_objectstorage-components.xml110(title) +#: ./doc/common/section_objectstorage-components.xml124(title) +msgid "Zones" +msgstr "" + +#: ./doc/common/section_objectstorage-components.xml111(para) +msgid "" +"Object Storage allows configuring zones in order to isolate failure " +"boundaries. Each data replica resides in a separate zone, if possible. At " +"the smallest level, a zone could be a single drive or a grouping of a few " +"drives. If there were five object storage servers, then each server would " +"represent its own zone. Larger deployments would have an entire rack (or " +"multiple racks) of object servers, each representing a zone. The goal of " +"zones is to allow the cluster to tolerate significant outages of storage " +"servers without losing all replicas of the data." +msgstr "" + +#: ./doc/common/section_objectstorage-components.xml118(para) +msgid "" +"As mentioned earlier, everything in Object Storage is stored, by default, " +"three times. Swift will place each replica \"as-uniquely-as-possible\" to " +"ensure both high availability and high durability. This means that when " +"chosing a replica location, Object Storage chooses a server in an unused " +"zone before an unused server in a zone that already has a replica of the " +"data." +msgstr "" + +#: ./doc/common/section_objectstorage-components.xml131(para) +msgid "" +"When a disk fails, replica data is automatically distributed to the other " +"zones to ensure there are three copies of the data." +msgstr "" + +#: ./doc/common/section_objectstorage-components.xml135(title) +#: ./doc/common/section_objectstorage-components.xml142(title) +msgid "Accounts and containers" +msgstr "" + +#: ./doc/common/section_objectstorage-components.xml136(para) +msgid "" +"Each account and container is an individual SQLite database that is " +"distributed across the cluster. An account database contains the list of " +"containers in that account. A container database contains the list of " +"objects in that container." +msgstr "" + +#: ./doc/common/section_objectstorage-components.xml149(para) +msgid "" +"To keep track of object data locations, each account in the system has a " +"database that references all of its containers, and each container database " +"references each object." +msgstr "" + +#: ./doc/common/section_objectstorage-components.xml154(title) +#: ./doc/common/section_objectstorage-components.xml167(title) +msgid "Partitions" +msgstr "" + +#: ./doc/common/section_objectstorage-components.xml155(para) +msgid "" +"A partition is a collection of stored data, including account databases, " +"container databases, and objects. Partitions are core to the replication " +"system." +msgstr "" + +#: ./doc/common/section_objectstorage-components.xml157(para) +msgid "" +"Think of a partition as a bin moving throughout a fulfillment center " +"warehouse. Individual orders get thrown into the bin. The system treats that" +" bin as a cohesive entity as it moves throughout the system. A bin is easier" +" to deal with than many little things. It makes for fewer moving parts " +"throughout the system." +msgstr "" + +#: ./doc/common/section_objectstorage-components.xml161(para) +msgid "" +"System replicators and object uploads/downloads operate on partitions. As " +"the system scales up, its behavior continues to be predictable because the " +"number of partitions is a fixed number." +msgstr "" + +#: ./doc/common/section_objectstorage-components.xml164(para) +msgid "" +"Implementing a partition is conceptually simple—a partition is just a " +"directory sitting on a disk with a corresponding hash table of what it " +"contains." +msgstr "" + +#: ./doc/common/section_objectstorage-components.xml176(title) +msgid "Replicators" +msgstr "" + +#: ./doc/common/section_objectstorage-components.xml177(para) +msgid "" +"In order to ensure that there are three copies of the data everywhere, " +"replicators continuously examine each partition. For each local partition, " +"the replicator compares it against the replicated copies in the other zones " +"to see if there are any differences." +msgstr "" + +#: ./doc/common/section_objectstorage-components.xml181(para) +msgid "" +"The replicator knowd if replication needs to take plac by examining hashes. " +"A hash file is created for each partition, which contains hashes of each " +"directory in the partition. Each of the three hash files is compared. For a " +"given partition, the hash files for each of the partition's copies are " +"compared. If the hashes are different, then it is time to replicate, and the" +" directory that needs to be replicated is copied over." +msgstr "" + +#: ./doc/common/section_objectstorage-components.xml187(para) +msgid "" +"This is where partitions come in handy. With fewer things in the system, " +"larger chunks of data are transferred around (rather than lots of little TCP" +" connections, which is inefficient) and there is a consistent number of " +"hashes to compare." +msgstr "" + +#: ./doc/common/section_objectstorage-components.xml190(para) +msgid "" +"The cluster eventually has a consistent behavior where the newest data has a" +" priority." +msgstr "" + +#: ./doc/common/section_objectstorage-components.xml200(para) +msgid "" +"If a zone goes down, one of the nodes containing a replica notices and " +"proactively copies data to a handoff location." +msgstr "" + +#: ./doc/common/section_objectstorage-components.xml204(title) +msgid "Use cases" +msgstr "" + +#: ./doc/common/section_objectstorage-components.xml205(para) +msgid "" +"The following sections show use cases for object uploads and downloads and " +"introduce the components." +msgstr "" + +#: ./doc/common/section_objectstorage-components.xml207(title) +msgid "Upload" +msgstr "" + +#: ./doc/common/section_objectstorage-components.xml208(para) +msgid "" +"A client uses the REST API to make a HTTP request to PUT an object into an " +"existing container. The cluster receives the request. First, the system must" +" figure out where the data is going to go. To do this, the account name, " +"container name, and object name are all used to determine the partition " +"where this object should live." +msgstr "" + +#: ./doc/common/section_objectstorage-components.xml212(para) +msgid "" +"Then a lookup in the ring figures out which storage nodes contain the " +"partitions in question." +msgstr "" + +#: ./doc/common/section_objectstorage-components.xml214(para) +msgid "" +"The data is then sent to each storage node where it is placed in the " +"appropriate partition. At least two of the three writes must be successful " +"before the client is notified that the upload was successful." +msgstr "" + +#: ./doc/common/section_objectstorage-components.xml217(para) +msgid "" +"Next, the container database is updated asynchronously to reflect that there" +" is a new object in it." +msgstr "" + +#: ./doc/common/section_objectstorage-components.xml220(title) +msgid "Object Storage in use" +msgstr "" + +#: ./doc/common/section_objectstorage-components.xml229(title) +msgid "Download" +msgstr "" + +#: ./doc/common/section_objectstorage-components.xml230(para) +msgid "" +"A request comes in for an acount/container/object. Using the same consistent" +" hashing, the partition name is generated. A lookup in the ring reveals " +"which storage nodes contain that partition. A request is made to one of the " +"storage nodes to fetch the object and, if that fails, requests are made to " +"the other nodes." +msgstr "" + +#: ./doc/common/section_storage-concepts.xml6(title) +msgid "Storage concepts" +msgstr "" + +#: ./doc/common/section_storage-concepts.xml7(para) +msgid "The OpenStack stack uses the following storage types:" +msgstr "" + +#: ./doc/common/section_storage-concepts.xml9(caption) +msgid "Storage types" +msgstr "" + +#: ./doc/common/section_storage-concepts.xml15(td) +msgid "On-instance / ephemeral" +msgstr "" + +#: ./doc/common/section_storage-concepts.xml16(td) +msgid "Block storage (Cinder)" +msgstr "" + +#: ./doc/common/section_storage-concepts.xml22(td) +msgid "Runs operating systems and provides scratch space" +msgstr "" + +#: ./doc/common/section_storage-concepts.xml23(td) +msgid "" +"Used for adding additional persistent storage to a virtual machine (VM)" +msgstr "" + +#: ./doc/common/section_storage-concepts.xml25(td) +msgid "Used for storing virtual machine images and data" +msgstr "" + +#: ./doc/common/section_storage-concepts.xml28(td) +msgid "Persists until VM is terminated" +msgstr "" + +#: ./doc/common/section_storage-concepts.xml29(td) +#: ./doc/common/section_storage-concepts.xml30(td) +msgid "Persists until deleted" +msgstr "" + +#: ./doc/common/section_storage-concepts.xml33(td) +#: ./doc/common/section_storage-concepts.xml34(td) +msgid "Access associated with a VM" +msgstr "" + +#: ./doc/common/section_storage-concepts.xml35(td) +msgid "Available from anywhere" +msgstr "" + +#: ./doc/common/section_storage-concepts.xml38(td) +msgid "Implemented as a filesystem underlying OpenStack Compute" +msgstr "" + +#: ./doc/common/section_storage-concepts.xml40(td) +msgid "" +"Mounted via OpenStack Block-Storage controlled protocol (for example, iSCSI)" +msgstr "" + +#: ./doc/common/section_storage-concepts.xml42(td) +msgid "REST API" +msgstr "" + +#: ./doc/common/section_storage-concepts.xml45(td) +msgid "Administrator configures size setting, based on flavors" +msgstr "" + +#: ./doc/common/section_storage-concepts.xml47(td) +msgid "Sizings based on need" +msgstr "" + +#: ./doc/common/section_storage-concepts.xml48(td) +msgid "Easily scalable for future growth" +msgstr "" + +#: ./doc/common/section_storage-concepts.xml51(td) +msgid "Example: 10GB first disk, 30GB/core second disk" +msgstr "" + +#: ./doc/common/section_storage-concepts.xml52(td) +msgid "Example: 1TB \"extra hard drive\"" +msgstr "" + +#: ./doc/common/section_storage-concepts.xml53(td) +msgid "Example: 10s of TBs of data set storage" +msgstr "" + +#: ./doc/common/section_storage-concepts.xml60(para) +msgid "" +"OpenStack Object Storage is not used like a traditional hard " +"drive. Object storage is all about relaxing some of the " +"constraints of a POSIX-style file system. The access to it is API-based (and" +" the API uses http). This is a good idea as if you don't have to provide " +"atomic operations (that is, you can rely on eventual consistency), you can " +"much more easily scale a storage system and avoid a central point of " +"failure." +msgstr "" + +#: ./doc/common/section_storage-concepts.xml70(para) +msgid "" +"The OpenStack Image Service is used to manage the virtual machine " +"images in an OpenStack cluster, not store them. Instead, it " +"provides an abstraction to different methods for storage - a bridge to the " +"storage, not the storage itself." +msgstr "" + +#: ./doc/common/section_storage-concepts.xml77(para) +msgid "" +"OpenStack Object Storage can function on its own. The " +"Object Storage (swift) product can be used independently of the Compute " +"(nova) product." +msgstr "" + +#: ./doc/common/section_storage-concepts.xml58(para) +msgid "Other points of note include: " +msgstr "" + +#: ./doc/common/section_cli_nova_boot.xml6(title) +msgid "Launch instances" +msgstr "" + +#: ./doc/common/section_cli_nova_boot.xml7(para) +#: ./doc/common/section_dashboard_launch_instances_from_image.xml8(para) +msgid "Instances are virtual machines that run inside the cloud." +msgstr "" + +#: ./doc/common/section_cli_nova_boot.xml9(para) +msgid "Before you can launch an instance, gather the following parameters:" +msgstr "" + +#: ./doc/common/section_cli_nova_boot.xml13(para) +#: ./doc/common/section_dashboard_launch_instances_from_image.xml22(para) +msgid "" +"The instance source, which is an image or snapshot. " +"Alternatively, you can boot from a volume, which is block storage, to which " +"you've copied an image or snapshot." +msgstr "" + +#: ./doc/common/section_cli_nova_boot.xml19(para) +#: ./doc/common/section_dashboard_launch_instances_from_image.xml28(para) +msgid "" +"The image or snapshot, which " +"represents the operating system." +msgstr "" + +#: ./doc/common/section_cli_nova_boot.xml24(para) +#: ./doc/common/section_dashboard_launch_instances_from_image.xml33(para) +msgid "A name for your instance." +msgstr "" + +#: ./doc/common/section_cli_nova_boot.xml28(para) +msgid "" +"The flavor for your instance, which " +"defines the compute, memory, and storage capacity of nova computing " +"instances. A flavor is an available hardware configuration for a server. It " +"defines the \"size\" of a virtual server that can be launched." +msgstr "" + +#: ./doc/common/section_cli_nova_boot.xml36(para) +msgid "" +"User Data is a special key in the metadata service that " +"holds a file that cloud-aware applications in the guest instance can access." +" For example. the cloudinit system" +" is an open-source package from Ubuntu that is available on various Linux " +"distributions including Ubuntu, Fedora, and openSUSE and that handles early " +"initialization of a cloud instance that uses user data." +msgstr "" + +#: ./doc/common/section_cli_nova_boot.xml49(para) +#: ./doc/common/section_dashboard_launch_instances_from_image.xml45(para) +msgid "" +"Access and security credentials, which include one or both of the following " +"credentials:" +msgstr "" + +#: ./doc/common/section_cli_nova_boot.xml53(para) +#: ./doc/common/section_dashboard_launch_instances_from_image.xml49(para) +msgid "" +"A keypair for your instance, which are " +"SSH credentials that are injected into images when they are launched. For " +"this to work, the image must contain the cloud-init " +"package. Create at least one keypair for each project. If you already have " +"generated a keypair with an external tool, you can import it into OpenStack." +" You can use the keypair for multiple instances that belong to that project." +msgstr "" + +#: ./doc/common/section_cli_nova_boot.xml66(para) +#: ./doc/common/section_dashboard_launch_instances_from_image.xml62(para) +msgid "" +"A security group, which defines which " +"incoming network traffic is forwarded to instances. Security groups hold a " +"set of firewall policies, known as security group " +"rules." +msgstr "" + +#: ./doc/common/section_cli_nova_boot.xml77(para) +#: ./doc/common/section_dashboard_launch_instances_from_image.xml73(para) +msgid "" +"If needed, you can assign a floating (public) IP " +"address to a running instance and attach a block storage device, " +"or volume, for persistent storage." +msgstr "" + +#: ./doc/common/section_cli_nova_boot.xml83(para) +msgid "" +"After you gather the parameters you need to launch an instance, you can " +"launch it from an image or a " +"volume." +msgstr "" + +#: ./doc/common/section_cli_nova_boot.xml87(para) +msgid "" +"You can launch an instance directly from one of the available OpenStack " +"images or from an image that you have copied to a persistent volume. The " +"OpenStack Image Service provides a pool of images that are accessible to " +"members of different projects." +msgstr "" + +#: ./doc/common/section_cli_nova_boot.xml94(title) +msgid "Gather parameters to launch an instance" +msgstr "" + +#: ./doc/common/section_cli_nova_boot.xml98(para) +msgid "" +"On a shell, source the OpenStack RC file. See ." +msgstr "" + +#: ./doc/common/section_cli_nova_boot.xml113(para) +msgid "Note the ID of the flavor that you want to use for your instance." +msgstr "" + +#: ./doc/common/section_cli_nova_boot.xml117(para) +msgid "List the available images:" +msgstr "" + +#: ./doc/common/section_cli_nova_boot.xml126(para) +msgid "" +"You can also filter the image list by using grep to find a specific image, " +"like this:" +msgstr "" + +#: ./doc/common/section_cli_nova_boot.xml130(para) +msgid "Note the ID of the image that you want to boot your instance from." +msgstr "" + +#: ./doc/common/section_cli_nova_boot.xml134(para) +msgid "List the available security groups:" +msgstr "" + +#: ./doc/common/section_cli_nova_boot.xml136(para) +msgid "" +"If you are an admin user, specify the --all-tenants " +"parameter to list groups for all tenants." +msgstr "" + +#: ./doc/common/section_cli_nova_boot.xml147(para) +msgid "" +"If you have not created any security groups, you can assign the instance to " +"only the default security group." +msgstr "" + +#: ./doc/common/section_cli_nova_boot.xml150(para) +msgid "You can also list rules for a specified security group:" +msgstr "" + +#: ./doc/common/section_cli_nova_boot.xml153(para) +msgid "" +"This example modifies the default security group to allow HTTP traffic on " +"the instance by permitting TCP traffic on Port 80." +msgstr "" + +#: ./doc/common/section_cli_nova_boot.xml158(para) +msgid "List the available keypairs." +msgstr "" + +#: ./doc/common/section_cli_nova_boot.xml160(para) +msgid "Note the name of the keypair that you use for SSH access." +msgstr "" + +#: ./doc/common/section_cli_nova_boot.xml167(title) +#: ./doc/common/section_dashboard_launch_instances_from_image.xml6(title) +msgid "Launch an instance from an image" +msgstr "" + +#: ./doc/common/section_cli_nova_boot.xml170(para) +msgid "" +"Now you have all parameters required to launch an instance, run the " +"following command and specify the server name, flavor ID, and image ID. " +"Optionally, you can provide a key name for access control and security group" +" for security. You can also include metadata key and value pairs. For " +"example you can add a description for your server by providing the " +"--meta description=\"My Server\" parameter." +msgstr "" + +#: ./doc/common/section_cli_nova_boot.xml179(para) +msgid "" +"You can pass user data in a local file at instance launch by using the flag " +"--user-data USER-DATA-FILE" +" parameter." +msgstr "" + +#: ./doc/common/section_cli_nova_boot.xml184(replaceable) +msgid "FLAVOR_ID" +msgstr "" + +#: ./doc/common/section_cli_nova_boot.xml184(replaceable) +msgid "IMAGE_ID" +msgstr "" + +#: ./doc/common/section_cli_nova_boot.xml184(replaceable) +msgid "KEY_NAME" +msgstr "" + +#: ./doc/common/section_cli_nova_boot.xml185(replaceable) +msgid "SEC_GROUP NAME_FOR_INSTANCE" +msgstr "" + +#: ./doc/common/section_cli_nova_boot.xml186(replaceable) +#: ./doc/common/section_cli_nova_boot.xml187(replaceable) +msgid "KEY=VALUE" +msgstr "" + +#: ./doc/common/section_cli_nova_boot.xml188(replaceable) +msgid "SERVER_NAME" +msgstr "" + +#: ./doc/common/section_cli_nova_boot.xml189(para) +msgid "" +"Depending on the parameters that you provide, the command returns a list of " +"server properties." +msgstr "" + +#: ./doc/common/section_cli_nova_boot.xml192(para) +msgid "" +"A status of BUILD indicates that the instance has " +"started, but is not yet online." +msgstr "" + +#: ./doc/common/section_cli_nova_boot.xml195(para) +msgid "" +"A status of ACTIVE indicates that the instance is active." +msgstr "" + +#: ./doc/common/section_cli_nova_boot.xml227(para) +msgid "" +"Copy the server ID value from the id field in the output." +" You use this ID to get details for or delete your server." +msgstr "" + +#: ./doc/common/section_cli_nova_boot.xml231(para) +msgid "" +"Copy the administrative password value from the adminPass" +" field. You use this value to log into your server." +msgstr "" + +#: ./doc/common/section_cli_nova_boot.xml235(para) +msgid "" +"Arbitrary local files can also be placed into the instance file system at " +"creation time using the --file <dst-path=src-path> " +"option. You may store up to 5 files. For example if you have a special " +"authorized_keys file named special_authorized_keysfile " +"that you want to put on the instance rather than using the regular ssh key " +"injection, you can use the following command:" +msgstr "" + +#: ./doc/common/section_cli_nova_boot.xml251(para) +msgid "Check if the instance is online:" +msgstr "" + +#: ./doc/common/section_cli_nova_boot.xml253(para) +msgid "" +"The list shows the ID, name, status, and private (and if assigned, public) " +"IP addresses for all instances in the project that you belong to:" +msgstr "" + +#: ./doc/common/section_cli_nova_boot.xml263(para) +msgid "If the status for the instance is ACTIVE, the instance is online." +msgstr "" + +#: ./doc/common/section_cli_nova_boot.xml265(para) +msgid "" +"To view the available options for the command, run the " +"following command:" +msgstr "" + +#: ./doc/common/section_cli_nova_boot.xml271(para) +msgid "" +"If you did not provide a keypair, security groups, or rules, you can only " +"access the instance from inside the cloud through VNC. Even pinging the " +"instance is not possible." +msgstr "" + +#: ./doc/common/section_keystone_config_ldap.xml6(title) +msgid "Configure the Identity Service with an LDAP back-end" +msgstr "" + +#: ./doc/common/section_keystone_config_ldap.xml8(para) +msgid "" +"As an alternative to the SQL database backing store, the Identity Service " +"can use a directory server to provide the Identity Service, for example:" +msgstr "" + +#: ./doc/common/section_keystone_config_ldap.xml31(para) +msgid "" +"The corresponding entries in the keystone.conf " +"configuration file are:" +msgstr "" + +#: ./doc/common/section_keystone_config_ldap.xml50(para) +msgid "" +"The default object classes and attributes are intentionally simple. They " +"reflect the common standard objects according to the LDAP RFCs. However, in " +"a live deployment, you can override the correct attributes to support a " +"preexisting, complex schema. For example, in the user object, the " +"objectClass posixAccount from RFC2307 is very common. If this is the " +"underlying objectclass, then the uid field should " +"probably be uidNumber and username" +" field either uid or cn. To change" +" these two fields, the corresponding entries in the Keystone configuration " +"file are:" +msgstr "" + +#: ./doc/common/section_keystone_config_ldap.xml65(para) +msgid "" +"Depending on your deployment, you can modify a set of allowed actions for " +"each object type. For example, you might set the following options:" +msgstr "" + +#: ./doc/common/section_keystone_config_ldap.xml80(para) +msgid "" +"If the back-end provides too much output, you can filter users, tenants, and" +" roles. For example:" +msgstr "" + +#: ./doc/common/section_keystone_config_ldap.xml86(para) +msgid "" +"If the directory server has not enabled the boolean type " +"for the user, you can use configuration options to extract the value from an" +" integer attribute. For example, in an Active Directory, as follows:" +msgstr "" + +#: ./doc/common/section_keystone_config_ldap.xml95(para) +msgid "" +"The attribute is an integer. Bit 1 contains the enabled attribute. If the " +"user_enabled_mask mask is not 0, it gets its value from" +" the field and it performs an ADD " +"operation by using the user_enabled_mask value. If the " +"value matches the mask, the account is disabled." +msgstr "" + +#: ./doc/common/section_keystone_config_ldap.xml102(para) +msgid "" +"It also saves the value without mask to the identity user" +" in the attribute. In case you must change " +"it to enable or disable a user, you can use this value because it contains " +"more information than the status such as, password expiration. The " +"user_enabled_mask value is required to create a default" +" value on the integer attribute (512 = NORMAL ACCOUNT on AD)." +msgstr "" + +#: ./doc/common/section_keystone_config_ldap.xml111(para) +msgid "" +"If Active Directory classes and attributes do not match the specified " +"classes in the LDAP module, so you can modify them, as follows:" +msgstr "" + +#. When image changes, this message will be marked fuzzy or untranslated for +#. you. +#. It doesn't matter what you translate it to: it's not used at all. +#: ./doc/common/section_dashboard_launch_instances_from_image.xml106(None) +msgid "" +"@@image: 'figures/launch_instances.png'; " +"md5=8a7e6864bce97f6478db572daf3ef5de" +msgstr "" + +#. When image changes, this message will be marked fuzzy or untranslated for +#. you. +#. It doesn't matter what you translate it to: it's not used at all. +#: ./doc/common/section_dashboard_launch_instances_from_image.xml164(None) +msgid "@@image: 'figures/instances.png'; md5=6b0f5cb3009d447334ff8b5c5b2cd121" +msgstr "" + +#: ./doc/common/section_dashboard_launch_instances_from_image.xml10(para) +msgid "" +"You can launch an instance directly from one of the available OpenStack " +"images. The OpenStack Image Service provides a pool of images that are " +"accessible to members of different projects. When you launch an instance " +"from an image, OpenStack creates a local copy of the image on the respective" +" compute node where the instance is started." +msgstr "" + +#: ./doc/common/section_dashboard_launch_instances_from_image.xml16(para) +msgid "" +"Alternatively, you can launch an instance from an image that you have copied" +" to a persistent volume." +msgstr "" + +#: ./doc/common/section_dashboard_launch_instances_from_image.xml18(para) +msgid "To launch an instance, specify the following parameters:" +msgstr "" + +#: ./doc/common/section_dashboard_launch_instances_from_image.xml37(para) +msgid "" +"The flavor for your instance, which " +"defines the compute, memory, and storage capacity of nova computing " +"instances. A flavor is an available hardware configuration for a server. It " +"defines the size of a virtual server that can be launched." +msgstr "" + +#: ./doc/common/section_dashboard_launch_instances_from_image.xml80(title) +msgid "To launch an instance:" +msgstr "" + +#: ./doc/common/section_dashboard_launch_instances_from_image.xml82(para) +msgid "Log in to the OpenStack dashboard." +msgstr "" + +#: ./doc/common/section_dashboard_launch_instances_from_image.xml85(para) +msgid "" +"If you are a member of multiple projects, select a project from the drop-" +"down list at the top of the Project tab." +msgstr "" + +#: ./doc/common/section_dashboard_launch_instances_from_image.xml90(para) +msgid "Click the Images & Snapshot category." +msgstr "" + +#: ./doc/common/section_dashboard_launch_instances_from_image.xml92(para) +msgid "" +"The dashboard shows the images that have been uploaded to OpenStack Image " +"Service and are available for this project." +msgstr "" + +#: ./doc/common/section_dashboard_launch_instances_from_image.xml100(title) +msgid "OpenStack dashboard - Launch Instances window" +msgstr "" + +#: ./doc/common/section_dashboard_launch_instances_from_image.xml97(para) +msgid "" +"Select an image and click Launch. The " +"Launch Image window appears: " +msgstr "" + +#: ./doc/common/section_dashboard_launch_instances_from_image.xml112(para) +msgid "Specify the following parameters:" +msgstr "" + +#: ./doc/common/section_dashboard_launch_instances_from_image.xml116(para) +msgid "Enter an instance name to assign to the virtual machine." +msgstr "" + +#: ./doc/common/section_dashboard_launch_instances_from_image.xml120(para) +msgid "" +"From the Flavor drop-down list, select the size of the " +"virtual machine to launch." +msgstr "" + +#: ./doc/common/section_dashboard_launch_instances_from_image.xml125(para) +msgid "Optionally, select a keypair." +msgstr "" + +#: ./doc/common/section_dashboard_launch_instances_from_image.xml126(para) +msgid "" +"In case an image uses a static root password or a static key set (neither is" +" recommended), you do not need to provide a keypair on starting the " +"instance." +msgstr "" + +#: ./doc/common/section_dashboard_launch_instances_from_image.xml132(para) +msgid "" +"In Instance Count, enter the number of virtual machines" +" to launch from this image." +msgstr "" + +#: ./doc/common/section_dashboard_launch_instances_from_image.xml137(para) +msgid "" +"Assign the instance to the default security group. If you added rules to " +"this group, the instance implements these rules." +msgstr "" + +#: ./doc/common/section_dashboard_launch_instances_from_image.xml150(para) +msgid "" +"Click Launch Instance. The instance is launched on " +"any of the compute nodes in the cloud." +msgstr "" + +#: ./doc/common/section_dashboard_launch_instances_from_image.xml155(para) +msgid "" +"After you have launched an instance, switch to the Instances &" +" Volumes category to view the instance name, its (private or " +"public) IP address, size, status, task, and power state." +msgstr "" + +#: ./doc/common/section_dashboard_launch_instances_from_image.xml160(title) +msgid "OpenStack dashboard - Instances" +msgstr "" + +#: ./doc/common/section_dashboard_launch_instances_from_image.xml168(para) +msgid "" +"If you did not provide a keypair on starting and have not touched security " +"groups or rules so far, by default the instance can only be accessed from " +"inside the cloud through VNC at this point. Even pinging the instance is not" +" possible." +msgstr "" + +#: ./doc/common/section_identity-troubleshooting.xml6(title) +msgid "Troubleshoot the Identity Service" +msgstr "" + +#: ./doc/common/section_identity-troubleshooting.xml7(para) +msgid "" +"To troubleshoot the Identity Service, review the logs in the " +"/var/log/keystone.log file." +msgstr "" + +#: ./doc/common/section_identity-troubleshooting.xml10(para) +msgid "" +"Use the /etc/keystone/logging.conf file to configure " +"the location of log files." +msgstr "" + +#: ./doc/common/section_identity-troubleshooting.xml13(para) +msgid "" +"The logs show the components that have come in to the WSGI request, and " +"ideally show an error that explains why an authorization request failed. If " +"you do not see the request in the logs, run keystone with " +"--debug parameter. Pass the " +"--debug parameter before the command parameters." +msgstr "" + +#: ./doc/common/section_identity-troubleshooting.xml20(title) +msgid "Debug PKI middleware" +msgstr "" + +#: ./doc/common/section_identity-troubleshooting.xml21(para) +msgid "" +"If you receive an Invalid OpenStack Identity Credentials " +"message when you talk to an OpenStack service, it might be caused by the " +"changeover from UUID tokens to PKI tokens in the Grizzly release. Learn how " +"to troubleshoot this error." +msgstr "" + +#: ./doc/common/section_identity-troubleshooting.xml26(para) +msgid "" +"The PKI-based token validation scheme relies on certificates from the " +"Identity Service that are fetched through HTTP and stored in a local " +"directory. The location for this directory is specified by the " +"signing_dir configuration option. In your services " +"configuration file, look for a section like this:" +msgstr "" + +#: ./doc/common/section_identity-troubleshooting.xml41(para) +msgid "" +"If your service lacks this stanza, the keystoneclient/middleware/auth_token.py" +" file specifies the defaults. If no value is specified for this directory, " +"it defaults" +" to a secure temporary directory. Initialization code for the service" +" checks that the directory exists and is writable. If it does not exist, the" +" code tries to create it. If this fails, the service fails to start. " +"However, it often succeeds but problems occur later." +msgstr "" + +#: ./doc/common/section_identity-troubleshooting.xml53(para) +msgid "" +"The first thing to check is that the signing_dir does, in" +" fact, exist. If it does, check for the presence of the certificate files " +"inside there:" +msgstr "" + +#: ./doc/common/section_identity-troubleshooting.xml64(para) +msgid "" +"This directory contains two certificates and the token revocation list. If " +"these files are not present, your service cannot fetch them from the " +"Identity Service. To troubleshoot, try to talk to the Identity Service to " +"make sure it is serving out the files, as follows:" +msgstr "" + +#: ./doc/common/section_identity-troubleshooting.xml70(para) +msgid "This command fetches the signing certificate:" +msgstr "" + +#: ./doc/common/section_identity-troubleshooting.xml81(para) +msgid "Note the expiration dates of the certificate:" +msgstr "" + +#: ./doc/common/section_identity-troubleshooting.xml84(para) +msgid "" +"The token revocation list is updated once a minute, but the certificates are" +" not. One possible problem is that the certificates are the wrong files or " +"garbage. You can remove these files and run another command against your " +"server: They are fetched on demand." +msgstr "" + +#: ./doc/common/section_identity-troubleshooting.xml89(para) +msgid "" +"The Identity Service log should show the access of the certificate files. " +"You might have to turn up your logging levels. Set debug = " +"True and verbose = True in your Identity " +"Service configuration file and restart the Identity Service server." +msgstr "" + +#: ./doc/common/section_identity-troubleshooting.xml99(para) +msgid "" +"If the files do not appear in your directory after this, it is likely one of" +" the following issues:" +msgstr "" + +#: ./doc/common/section_identity-troubleshooting.xml103(para) +msgid "" +"Your service is configured incorrectly and cannot talk to the Identity " +"Service. Check the auth_port and " +"auth_host values and make sure that you can talk to that " +"service through cURL, as shown previously." +msgstr "" + +#: ./doc/common/section_identity-troubleshooting.xml111(para) +msgid "" +"Your signing directory is not writable. Use the command to " +"change its permissions so that the service (POSIX) user can write to it. " +"Verify the change through and commands." +msgstr "" + +#: ./doc/common/section_identity-troubleshooting.xml119(para) +msgid "The SELinux policy is denying access to the directory." +msgstr "" + +#: ./doc/common/section_identity-troubleshooting.xml123(para) +msgid "" +"SELinux troubles often when you use Fedora/RHEL-based packages and you " +"choose configuration options that do not match the standard policy. Run the " +" command. If that makes a different, you should relabel the " +"directory. If you are using a sub-directory of the " +"/var/cache/ directory, run the following command:" +msgstr "" + +#: ./doc/common/section_identity-troubleshooting.xml132(para) +msgid "" +"If you are not using a /var/cache sub-directory, you " +"should. Modify the signing_dir configuration option for " +"your service and restart." +msgstr "" + +#: ./doc/common/section_identity-troubleshooting.xml136(para) +msgid "" +"Set back to setenforce enforcing to confirm that your " +"changes solve the problem." +msgstr "" + +#: ./doc/common/section_identity-troubleshooting.xml138(para) +msgid "" +"If your certificates are fetched on demand, the PKI validation is working " +"properly. Most likely, the token from the Identity Service is not valid for " +"the operation you are attempting to perform, and your user needs a different" +" role for the operation." +msgstr "" + +#: ./doc/common/section_identity-troubleshooting.xml145(title) +msgid "Debug signing key file errors" +msgstr "" + +#: ./doc/common/section_identity-troubleshooting.xml146(para) +msgid "" +"If an error occurs when the signing key file opens, it is possible that the " +"person who ran the command to generate certificates and " +"keys did not use the correct user. When you run the " +"command, the Identity Service generates a set of certificates and keys in " +"/etc/keystone/ssl*, which is owned by root:root." +msgstr "" + +#: ./doc/common/section_identity-troubleshooting.xml155(para) +msgid "" +"This can present a problem when you run the Identity Service daemon under " +"the keystone user account (nologin) when you try to run PKI. Unless you run " +"the command against the files keystone:keystone or run the " +" command with the --keystone-user and" +" --keystone-group parameters, you get an error, as " +"follows:" +msgstr "" + +#: ./doc/common/section_dashboard_customizing.xml6(title) +msgid "Customize the dashboard" +msgstr "" + +#: ./doc/common/section_dashboard_customizing.xml7(para) +msgid "" +"Adapted from How To Custom Brand The " +"OpenStack “Horizon” Dashboard." +msgstr "" + +#: ./doc/common/section_dashboard_customizing.xml11(para) +msgid "" +"You install the OpenStack dashboard through the openstack-" +"dashboard package. You can customize the dashboard with your own " +"colors, logo, and site title through a CSS file." +msgstr "" + +#: ./doc/common/section_dashboard_customizing.xml15(para) +msgid "" +"Canonical also provides an openstack-dashboard-ubuntu-" +"theme package that brands the Python-based Django interface." +msgstr "" + +#: ./doc/common/section_dashboard_customizing.xml47(para) +msgid "" +"Create a graphical logo with a transparent background. The text " +"TGen Cloud in this example is rendered through " +".png files of multiple sizes created with a graphics " +"program." +msgstr "" + +#: ./doc/common/section_dashboard_customizing.xml52(para) +msgid "" +"Use a 200×27 for the logged-in banner graphic, and 365×50 for the login " +"screen graphic." +msgstr "" + +#: ./doc/common/section_dashboard_customizing.xml56(para) +msgid "" +"Set the HTML title, which appears at the top of the browser window, by " +"adding the following line to /etc/openstack-" +"dashboard/local_settings.py:" +msgstr "" + +#: ./doc/common/section_dashboard_customizing.xml59(code) +msgid "SITE_BRANDING = \"Example, Inc. Cloud\"" +msgstr "" + +#: ./doc/common/section_dashboard_customizing.xml63(para) +msgid "" +"Upload your new graphic files to the following location: " +"/usr/share/openstack-" +"dashboard/openstack_dashboard/static/dashboard/img/" +msgstr "" + +#: ./doc/common/section_dashboard_customizing.xml68(para) +msgid "" +"Create a CSS style sheet in the following directory: /usr/share" +"/openstack-dashboard/openstack_dashboard/static/dashboard/css/" +msgstr "" + +#: ./doc/common/section_dashboard_customizing.xml72(para) +msgid "" +"Edit your CSS file to override the Ubuntu customizations in the " +"ubuntu.css file." +msgstr "" + +#: ./doc/common/section_dashboard_customizing.xml75(para) +msgid "" +"Change the colors and image file names as appropriate, though the relative " +"directory paths should be the same. The following example file shows you how" +" to customize your CSS file:" +msgstr "" + +#: ./doc/common/section_dashboard_customizing.xml114(para) +msgid "" +"Open the following HTML template in an editor: /usr/share" +"/openstack-" +"dashboard/openstack_dashboard/templates/_stylesheets.html" +msgstr "" + +#: ./doc/common/section_dashboard_customizing.xml118(para) +msgid "Add a line to include your custom.css file:" +msgstr "" + +#: ./doc/common/section_dashboard_customizing.xml123(emphasis) +msgid "" +"<link href='{{ STATIC_URL }}dashboard/css/custom.css' media='screen' " +"rel='stylesheet' />" +msgstr "" + +#: ./doc/common/section_dashboard_customizing.xml127(para) +msgid "Restart apache:" +msgstr "" + +#: ./doc/common/section_dashboard_customizing.xml128(para) +#: ./doc/common/section_dashboard_sessions.xml175(para) +msgid "On Ubuntu: " +msgstr "" + +#: ./doc/common/section_dashboard_customizing.xml131(para) +msgid "On Fedora, RHEL, CentOS: " +msgstr "" + +#: ./doc/common/section_dashboard_customizing.xml134(para) +#: ./doc/common/section_dashboard_sessions.xml182(para) +msgid "On openSUSE: " +msgstr "" + +#: ./doc/common/section_dashboard_customizing.xml139(para) +msgid "Reload the dashboard in your browser to view your changes." +msgstr "" + +#: ./doc/common/section_dashboard_customizing.xml141(para) +msgid "Modify your CSS file as appropriate." +msgstr "" + +#: ./doc/common/section_cli_version.xml6(title) +msgid "Get the version for a client" +msgstr "" + +#: ./doc/common/section_cli_version.xml7(para) +msgid "After you install an OpenStack client, you can get its version number." +msgstr "" + +#: ./doc/common/section_cli_version.xml11(para) +msgid "Run the following command get the version number for a client:" +msgstr "" + +#: ./doc/common/section_cli_version.xml13(replaceable) +#: ./doc/common/section_cli_install.xml121(replaceable) +#: ./doc/common/section_cli_install.xml136(replaceable) +#: ./doc/common/section_cli_install.xml147(replaceable) +#: ./doc/common/section_cli_install.xml171(replaceable) +#: ./doc/common/section_cli_install.xml173(replaceable) +msgid "PROJECT" +msgstr "" + +#: ./doc/common/section_cli_version.xml14(para) +msgid "" +"Where PROJECT is one of the following project " +"names:" +msgstr "" + +#: ./doc/common/section_cli_version.xml19(para) +#: ./doc/common/section_cli_install.xml179(para) +msgid "nova. Compute API and extensions." +msgstr "" + +#: ./doc/common/section_cli_version.xml23(para) +#: ./doc/common/section_cli_install.xml183(para) +msgid "neutron. Networking API." +msgstr "" + +#: ./doc/common/section_cli_version.xml27(para) +#: ./doc/common/section_cli_install.xml187(para) +msgid "keystone. Identity Service API." +msgstr "" + +#: ./doc/common/section_cli_version.xml31(para) +#: ./doc/common/section_cli_install.xml191(para) +msgid "glance. Image Service API." +msgstr "" + +#: ./doc/common/section_cli_version.xml35(para) +#: ./doc/common/section_cli_install.xml195(para) +msgid "swift. Object Storage API." +msgstr "" + +#: ./doc/common/section_cli_version.xml39(para) +#: ./doc/common/section_cli_install.xml199(para) +msgid "cinder. Block Storage Service API." +msgstr "" + +#: ./doc/common/section_cli_version.xml43(para) +#: ./doc/common/section_cli_install.xml203(para) +msgid "heat. Orchestration API." +msgstr "" + +#: ./doc/common/section_cli_version.xml47(para) +#: ./doc/common/section_cli_install.xml207(para) +msgid "ceilometer. Telemetry API." +msgstr "" + +#: ./doc/common/section_cli_version.xml51(para) +msgid "" +"For example, to see the version of the nova client, run the following " +"command:" +msgstr "" + +#: ./doc/common/section_cli_version.xml56(para) +msgid "To see the version of the keystone client, run the following command:" +msgstr "" + +#: ./doc/common/section_keystone-concepts-group-management.xml7(para) +msgid "" +"A group is a collection of users. Administrators can create groups and add " +"users to them. Then, rather than assign a role to each user individually, " +"assign a role to the group. Every group is in a domain. Groups were " +"introduced with version 3 of the Identity API (the Grizzly release of " +"Identity Service)." +msgstr "" + +#: ./doc/common/section_keystone-concepts-group-management.xml13(para) +msgid "Identity API V3 provides the following group-related operations:" +msgstr "" + +#: ./doc/common/section_keystone-concepts-group-management.xml17(para) +msgid "Create a group" +msgstr "" + +#: ./doc/common/section_keystone-concepts-group-management.xml20(para) +msgid "Delete a group" +msgstr "" + +#: ./doc/common/section_keystone-concepts-group-management.xml23(para) +msgid "Update a group (change its name or description)" +msgstr "" + +#: ./doc/common/section_keystone-concepts-group-management.xml27(para) +msgid "Add a user to a group" +msgstr "" + +#: ./doc/common/section_keystone-concepts-group-management.xml30(para) +msgid "Remove a user from a group" +msgstr "" + +#: ./doc/common/section_keystone-concepts-group-management.xml33(para) +msgid "List group members" +msgstr "" + +#: ./doc/common/section_keystone-concepts-group-management.xml36(para) +msgid "List groups for a user" +msgstr "" + +#: ./doc/common/section_keystone-concepts-group-management.xml39(para) +msgid "Assign a role on a tenant to a group" +msgstr "" + +#: ./doc/common/section_keystone-concepts-group-management.xml42(para) +msgid "Assign a role on a domain to a group" +msgstr "" + +#: ./doc/common/section_keystone-concepts-group-management.xml45(para) +msgid "Query role assignments to groups" +msgstr "" + +#: ./doc/common/section_keystone-concepts-group-management.xml49(para) +msgid "" +"The Identity service server might not allow all operations. For example, if " +"using the Identity server with the LDAP Identity back end and group updates " +"are disabled, then a request to create, delete, or update a group fails." +msgstr "" + +#: ./doc/common/section_keystone-concepts-group-management.xml55(para) +msgid "Here are a couple examples:" +msgstr "" + +#: ./doc/common/section_keystone-concepts-group-management.xml58(para) +msgid "" +"Group A is granted Role A on Tenant A. If User A is a member of Group A, " +"when User A gets a token scoped to Tenant A, the token also includes Role A." +msgstr "" + +#: ./doc/common/section_keystone-concepts-group-management.xml64(para) +msgid "" +"Group B is granted Role B on Domain B. If User B is a member of Domain B, if" +" User B gets a token scoped to Domain B, the token also includes Role B." +msgstr "" + +#: ./doc/common/section_cli_overview.xml15(para) +msgid "" +"You can use the OpenStack command-line clients to run simple commands that " +"make API calls. You can run these commands from the command line or in " +"scripts to automate tasks. As long as you provide OpenStack credentials, you" +" can run these commands on any machine." +msgstr "" + +#: ./doc/common/section_cli_overview.xml20(para) +msgid "" +"Internally, each client command runs cURL commands that embed API requests. " +"The OpenStack APIs are RESTful APIs that use the HTTP protocol, including " +"methods, URIs, media types, and response codes." +msgstr "" + +#: ./doc/common/section_cli_overview.xml24(para) +msgid "" +"These open-source Python clients run on Linux or Mac OS X systems and are " +"easy to learn and use. Each OpenStack service has its own command-line " +"client. On some client commands, you can specify a " +"debug parameter to show the underlying API request " +"for the command. This is a good way to become familiar with the OpenStack " +"API calls." +msgstr "" + +#: ./doc/common/section_cli_overview.xml35(para) +msgid "" +"These command-line clients are available for the respective services' APIs:" +msgstr "" + +#: ./doc/common/section_cli_overview.xml39(para) +msgid "" +" (python-ceilometerclient). Client for " +"the Telemetry API that lets you create and collect measurements across " +"OpenStack." +msgstr "" + +#: ./doc/common/section_cli_overview.xml45(para) +msgid "" +" (python-cinderclient). Client for the " +"Block Storage Service API that lets you create and manage volumes." +msgstr "" + +#: ./doc/common/section_cli_overview.xml51(para) +msgid "" +" (python-glanceclient). Client for the " +"Image Service API that lets you create and manage images." +msgstr "" + +#: ./doc/common/section_cli_overview.xml57(para) +msgid "" +" (python-heatclient). Client for the " +"Orchestration API that lets you launch stacks from templates, view details " +"of running stacks including events and resources, and update and delete " +"stacks." +msgstr "" + +#: ./doc/common/section_cli_overview.xml65(para) +msgid "" +" (python-keystoneclient). Client for the " +"Identity Service API that lets you create and manage users, tenants, roles, " +"endpoints, and credentials." +msgstr "" + +#: ./doc/common/section_cli_overview.xml72(para) +msgid "" +" (python-neutronclient). Client for the " +"Networking API that lets you configure networks for guest servers. This " +"client was previously known as ." +msgstr "" + +#: ./doc/common/section_cli_overview.xml79(para) +msgid "" +" (python-novaclient). Client for the " +"Compute API and its extensions. Use to create and manage images, instances, " +"and flavors." +msgstr "" + +#: ./doc/common/section_cli_overview.xml85(para) +msgid "" +" (python-swiftclient). Client for the " +"Object Storage API that lets you gather statistics, list items, update " +"metadata, upload, download and delete files stored by the Object Storage " +"service. Provides access to a swift installation for ad hoc processing." +msgstr "" + +#: ./doc/common/section_cli_overview.xml94(para) +msgid "An OpenStack client is in development." +msgstr "" + +#: ./doc/common/section_cli_overview.xml96(para) +msgid "" +"For client installation instructions, see Install the OpenStack command-line " +"clients. For information about the OpenStack RC file, see Download and source the OpenStack RC " +"file. Both topics are in the OpenStack End User " +"Guide." +msgstr "" + +#: ./doc/common/section_rpc.xml8(para) +msgid "" +"OpenStack projects use AMQP, an open standard for messaging middleware. " +"OpenStack services that run on multiple servers to talk to each other. " +"OpenStack Oslo RPC supports three implementations of AMQP: " +"RabbitMQ, Qpid, and " +"ZeroMQ." +msgstr "" + +#: ./doc/common/section_rpc.xml16(para) +msgid "" +"OpenStack Oslo RPC uses RabbitMQ by default. Use " +"these options to configure the RabbitMQ message " +"system. The rpc_backend option is not required as long as" +" RabbitMQ is the default messaging system. " +"However, if it is included the configuration, you must set it to " +"nova.openstack.common.rpc.impl_kombu." +msgstr "" + +#: ./doc/common/section_rpc.xml25(para) +msgid "" +"You can use these additional options to configure the " +"RabbitMQ messaging system. You can configure " +"messaging communication for different installation scenarios, tune retries " +"for RabbitMQ, and define the size of the RPC thread pool. To monitor " +"notifications through RabbitMQ, you must set the " +" option to " +"nova.notifier.rabbit_notifier in the " +"nova.conf file. The default for sending usage data is " +"sixty seconds plus a random number of seconds from zero to sixty." +msgstr "" + +#: ./doc/common/section_rpc.xml40(para) +msgid "" +"Use these options to configure the Qpid messaging" +" system for OpenStack Oslo RPC. Qpid is not the " +"default messaging system, so you must enable it by setting the " +" option in the nova.conf " +"file." +msgstr "" + +#: ./doc/common/section_rpc.xml47(para) +msgid "" +"This critical option points the compute nodes to the " +"Qpid broker (server). Set " +" to the host name where the broker runs in the" +" nova.conf file." +msgstr "" + +#: ./doc/common/section_rpc.xml69(para) +msgid "" +"This table lists additional options that you use to configure the Qpid " +"messaging driver for OpenStack Oslo RPC. These options are used " +"infrequently." +msgstr "" + +#: ./doc/common/section_rpc.xml76(para) +msgid "" +"Use these options to configure the ZeroMQ " +"messaging system for OpenStack Oslo RPC. ZeroMQ " +"is not the default messaging system, so you must enable it by setting the " +" option in the nova.conf " +"file." +msgstr "" + +#: ./doc/common/section_rpc.xml86(para) +msgid "" +"Use these options to configure the RabbitMQ and " +"Qpid messaging drivers." +msgstr "" + +#: ./doc/common/section_cli_install.xml15(title) +msgid "Install the OpenStack command-line clients" +msgstr "" + +#: ./doc/common/section_cli_install.xml16(para) +msgid "" +"Install the prerequisite software and the Python package for each OpenStack " +"client." +msgstr "" + +#: ./doc/common/section_cli_install.xml19(para) +msgid "" +"For each command, replace PROJECT with the lower " +"case name of the client to install, such as nova. Repeat " +"for each client." +msgstr "" + +#: ./doc/common/section_cli_install.xml26(caption) +msgid "Prerequisite software" +msgstr "" + +#: ./doc/common/section_cli_install.xml31(th) +msgid "Prerequisite" +msgstr "" + +#: ./doc/common/section_cli_install.xml38(para) +msgid "Python 2.6 or newer" +msgstr "" + +#: ./doc/common/section_cli_install.xml41(para) +msgid "Currently, the clients do not support Python 3." +msgstr "" + +#: ./doc/common/section_cli_install.xml47(para) +msgid "setuptools package" +msgstr "" + +#: ./doc/common/section_cli_install.xml50(para) +msgid "Installed by default on Mac OS X." +msgstr "" + +#: ./doc/common/section_cli_install.xml51(para) +msgid "" +"Many Linux distributions provide packages to make " +"setuptools easy to install. Search your package manager " +"for setuptools to find an installation package. If you " +"cannot find one, download the setuptools package directly" +" from http://pypi.python.org/pypi/setuptools." +msgstr "" + +#: ./doc/common/section_cli_install.xml59(para) +msgid "" +"The recommended way to install setuptools on Microsoft " +"Windows is to follow the documentation provided on the setuptools " +"website. Another option is to use the unofficial binary installer " +"maintained by Christoph Gohlke (http://www.lfd.uci.edu/~gohlke/pythonlibs/#setuptools)." +msgstr "" + +#: ./doc/common/section_cli_install.xml72(package) +msgid "pip" +msgstr "" + +#: ./doc/common/section_cli_install.xml72(td) +msgid " package" +msgstr "" + +#: ./doc/common/section_cli_install.xml74(para) +msgid "" +"To install the clients on a Linux, Mac OS X or Microsoft Windows system, use" +" pip. It is easy to use, ensures that you get the latest " +"version of the clients from the Python Package Index, and lets you update or " +"remove the packages later on." +msgstr "" + +#: ./doc/common/section_cli_install.xml81(para) +msgid "" +"Install pip through the package manager for your system:" +msgstr "" + +#: ./doc/common/section_cli_install.xml84(title) +msgid "Mac OS X" +msgstr "" + +#: ./doc/common/section_cli_install.xml89(title) +msgid "Microsoft Windows" +msgstr "" + +#: ./doc/common/section_cli_install.xml90(para) +msgid "" +"Make sure that the C:\\Python27\\Scripts directory is " +"defined in the PATH environment variable, and use the " +" command from the setuptools package: " +" Another option is to use the unofficial binary installer " +"provided by Christoph Gohlke (http://www.lfd.uci.edu/~gohlke/pythonlibs/#pip)." +msgstr "" + +#: ./doc/common/section_cli_install.xml103(title) +msgid "Ubuntu 12.04" +msgstr "" + +#: ./doc/common/section_cli_install.xml104(para) +msgid "" +"A packaged version enables you to use dpkg or " +"aptitude to install the python-" +"novaclient:" +msgstr "" + +#: ./doc/common/section_cli_install.xml111(title) +msgid "Ubuntu" +msgstr "" + +#: ./doc/common/section_cli_install.xml115(title) +msgid "RHEL, CentOS, or Fedora" +msgstr "" + +#: ./doc/common/section_cli_install.xml116(para) +msgid "" +"A packaged version available in RDO enables you to use " +"yum to install the clients: " +msgstr "" + +#: ./doc/common/section_cli_install.xml123(para) +msgid "" +"Alternatively, install pip and use it to manage client " +"installation:" +msgstr "" + +#: ./doc/common/section_cli_install.xml128(title) +msgid "openSUSE 12.2 and earlier" +msgstr "" + +#: ./doc/common/section_cli_install.xml129(para) +msgid "" +"A packaged version available " +"in the Open Build Service enables you to use rpm " +"or zypper to install the python-" +"novaclient:" +msgstr "" + +#: ./doc/common/section_cli_install.xml137(para) +msgid "" +"Alternatively, install pip and use it to manage client " +"installation: " +msgstr "" + +#: ./doc/common/section_cli_install.xml142(title) +msgid "openSUSE 12.3 and newer" +msgstr "" + +#: ./doc/common/section_cli_install.xml143(para) +msgid "" +"A packaged version enables you to use rpm or " +"zypper to install the clients: " +msgstr "" + +#: ./doc/common/section_cli_install.xml154(title) +msgid "Install the clients" +msgstr "" + +#: ./doc/common/section_cli_install.xml155(para) +msgid "" +"Use pip to install the OpenStack clients on a Linux, Mac " +"OS X or Microsoft Windows system. It is easy and ensures that you get the " +"latest version of the client from the Python Package Index. Also, " +"pip lets you update or remove a package. After you " +"install the clients, you must source an openrc.sh file " +"to set required environment variables before you can request OpenStack " +"services through the clients or the APIs." +msgstr "" + +#: ./doc/common/section_cli_install.xml168(para) +msgid "You must install each client separately." +msgstr "" + +#: ./doc/common/section_cli_install.xml169(para) +msgid "Run this command to install a client package." +msgstr "" + +#: ./doc/common/section_cli_install.xml170(para) +msgid "For Mac OS X or Linux:" +msgstr "" + +#: ./doc/common/section_cli_install.xml172(para) +msgid "For Microsoft Windows:" +msgstr "" + +#: ./doc/common/section_cli_install.xml174(para) +msgid "" +"Where PROJECT is the project name and has one of " +"the following values:" +msgstr "" + +#: ./doc/common/section_cli_install.xml211(para) +msgid "For example, to install the nova client, run this command:" +msgstr "" + +#: ./doc/common/section_cli_install.xml214(para) +msgid "To remove the nova client, run this command:" +msgstr "" + +#: ./doc/common/section_cli_install.xml217(para) +msgid "" +"To upgrade a package, add the --upgrade option to the " +" command." +msgstr "" + +#: ./doc/common/section_cli_install.xml220(para) +msgid "To update the nova client, run this command:" +msgstr "" + +#: ./doc/common/section_cli_install.xml225(para) +msgid "" +"Before you can run client commands, you must create and source the " +"openrc.sh file to set environment variables. See ." +msgstr "" + +#: ./doc/common/section_keystone-concepts-service-management.xml5(title) +msgid "Service management" +msgstr "" + +#: ./doc/common/section_keystone-concepts-service-management.xml6(para) +msgid "" +"The Identity Service provides identity, token, catalog, and policy services." +" It consists of:" +msgstr "" + +#: ./doc/common/section_keystone-concepts-service-management.xml11(para) +msgid "" +"keystone-all. Starts both the " +"service and administrative APIs in a single process to provide Catalog, " +"Authorization, and Authentication services for OpenStack." +msgstr "" + +#: ./doc/common/section_keystone-concepts-service-management.xml17(para) +msgid "" +"Identity Service functions. Each has a pluggable back end that allows " +"different ways to use the particular service. Most support standard back " +"ends like LDAP or SQL." +msgstr "" + +#: ./doc/common/section_keystone-concepts-service-management.xml23(para) +msgid "" +"The Identity Service also maintains a user that corresponds to each service," +" such as, a user named nova for the Compute service, " +"and a special service tenant called service." +msgstr "" + +#: ./doc/common/section_keystone-concepts-service-management.xml28(para) +msgid "" +"For information about how to create services and endpoints, see the OpenStack Admin User " +"Guide." +msgstr "" + +#: ./doc/common/section_cli_openrc.xml7(title) +msgid "The OpenStack RC file" +msgstr "" + +#: ./doc/common/section_cli_openrc.xml8(para) +msgid "" +"To set the required environment variables for the OpenStack command-line " +"clients, you must create an environment file. " +"If your OpenStack installation provides it, you can download the file from " +"the OpenStack dashboard as an administrative user or any other " +"user. This project-specific environment file contains the " +"credentials that all OpenStack services use." +msgstr "" + +#: ./doc/common/section_cli_openrc.xml16(para) +msgid "" +"When you source the file, environment variables are set for your current " +"shell. The variables enable the OpenStack client commands to communicate " +"with the OpenStack services that run in the cloud." +msgstr "" + +#: ./doc/common/section_cli_openrc.xml21(title) +msgid "Environment variables on Microsoft Windows" +msgstr "" + +#: ./doc/common/section_cli_openrc.xml22(para) +msgid "" +"Defining environment variables using an environment file is not a common " +"practice on Microsoft Windows. Environment variables are usually defined in " +"the Advanced tab of the System " +"Properties dialog." +msgstr "" + +#: ./doc/common/section_cli_openrc.xml28(title) +msgid "Download and source the OpenStack RC file" +msgstr "" + +#: ./doc/common/section_cli_openrc.xml31(para) +msgid "" +"Log in to the OpenStack dashboard, choose the project for which you want to " +"download the OpenStack RC file, and click Access & " +"Security." +msgstr "" + +#: ./doc/common/section_cli_openrc.xml37(para) +msgid "" +"Click Download OpenStack RC File and save the file." +msgstr "" + +#: ./doc/common/section_cli_openrc.xml41(para) +msgid "" +"Copy the openrc.sh file to the machine from where you " +"want to run OpenStack commands." +msgstr "" + +#: ./doc/common/section_cli_openrc.xml44(para) +msgid "" +"For example, copy the file to the machine from where you want to upload an " +"image with a glance client command." +msgstr "" + +#: ./doc/common/section_cli_openrc.xml49(para) +msgid "" +"On any shell from where you want to run OpenStack commands, source the " +"openrc.sh file for the respective project." +msgstr "" + +#: ./doc/common/section_cli_openrc.xml53(para) +msgid "" +"In this example, you source the demo-openrc.sh file for" +" the demo project:" +msgstr "" + +#: ./doc/common/section_cli_openrc.xml59(para) +msgid "" +"When you are prompted for an OpenStack password, enter the password for the " +"user who downloaded the openrc.sh file." +msgstr "" + +#: ./doc/common/section_cli_openrc.xml66(title) +msgid "Create and source the OpenStack RC file" +msgstr "" + +#: ./doc/common/section_cli_openrc.xml67(para) +msgid "" +"Alternatively, you can create the openrc.sh file from " +"scratch." +msgstr "" + +#: ./doc/common/section_cli_openrc.xml72(para) +msgid "" +"Create the openrc.sh file and add the authentication " +"information:" +msgstr "" + +#: ./doc/common/section_cli_openrc.xml74(replaceable) +msgid "USERNAME" +msgstr "" + +#: ./doc/common/section_cli_openrc.xml75(replaceable) +msgid "PASSWORD" +msgstr "" + +#: ./doc/common/section_cli_openrc.xml76(replaceable) +msgid "PROJECT_NAME" +msgstr "" + +#: ./doc/common/section_cli_openrc.xml77(replaceable) +msgid "https://IDENTITY_HOST:PORT/v2.0" +msgstr "" + +#: ./doc/common/section_cli_openrc.xml79(replaceable) +msgid "9d792532ffce494583138c495801d164" +msgstr "" + +#: ./doc/common/section_cli_openrc.xml80(replaceable) +msgid "RegionOne" +msgstr "" + +#: ./doc/common/section_cli_openrc.xml82(replaceable) +msgid "ADMIN_PASS" +msgstr "" + +#: ./doc/common/section_cli_openrc.xml84(replaceable) +msgid "controller" +msgstr "" + +#: ./doc/common/section_cli_openrc.xml87(para) +msgid "" +"On any shell from where you want to run OpenStack commands, source the " +"openrc.sh file for the respective project:" +msgstr "" + +#: ./doc/common/section_cli_openrc.xml95(para) +msgid "" +"You are not prompted for the password with this method. The password lives " +"in clear text format in the openrc.sh file. Restrict " +"the permissions on this file to avoid security problems. You can also remove" +" the OS_PASSWORD variable from the file, and use the " +"--password parameter with OpenStack client commands." +msgstr "" + +#: ./doc/common/section_cli_openrc.xml106(title) +msgid "Override environment variable values" +msgstr "" + +#: ./doc/common/section_cli_openrc.xml107(para) +msgid "" +"When you run OpenStack client commands, you can override some environment " +"variable settings by using the options that are listed at the end of the " +" output. For example, you can override the " +" setting in the openrc.sh " +"file by specifying a password on a command, as follows:" +msgstr "" + +#: ./doc/common/section_cli_openrc.xml115(para) +msgid "Where password is your password." +msgstr "" + +#: ./doc/common/section_cli_nova_baremetal.xml5(title) +msgid "Manage bare metal nodes" +msgstr "" + +#: ./doc/common/section_cli_nova_baremetal.xml6(para) +msgid "" +"The bare metal driver for OpenStack Compute manages provisioning of physical" +" hardware using common cloud APIs and tools such as Orchestration (Heat). " +"The use case for this driver is for single tenant clouds such as a high-" +"performance computing cluster or deploying OpenStack itself. Development " +"efforts are focused on moving the driver out of the Compute code base in the" +" Icehouse release. If you use the bare metal driver, you must create and add" +" a network interface to a bare metal node. Then, you can launch an instance " +"from a bare metal image." +msgstr "" + +#: ./doc/common/section_cli_nova_baremetal.xml15(para) +msgid "" +"You can list and delete bare metal nodes. When you delete a node, any " +"associated network interfaces are removed. You can list and remove network " +"interfaces that are associated with a bare metal node." +msgstr "" + +#: ./doc/common/section_cli_nova_baremetal.xml20(title) +msgid "Commands" +msgstr "" + +#: ./doc/common/section_cli_nova_baremetal.xml22(para) +msgid ". Adds a network interface to a bare metal node." +msgstr "" + +#: ./doc/common/section_cli_nova_baremetal.xml26(para) +msgid "" +". Lists network interfaces associated with a bare metal " +"node." +msgstr "" + +#: ./doc/common/section_cli_nova_baremetal.xml30(para) +msgid ". Removes a network interface from a bare metal node." +msgstr "" + +#: ./doc/common/section_cli_nova_baremetal.xml34(para) +msgid ". Creates a bare metal node." +msgstr "" + +#: ./doc/common/section_cli_nova_baremetal.xml38(para) +msgid "" +". Removes a bare metal node and any associated interfaces." +msgstr "" + +#: ./doc/common/section_cli_nova_baremetal.xml42(para) +msgid ". Lists available bare metal nodes." +msgstr "" + +#: ./doc/common/section_cli_nova_baremetal.xml46(para) +msgid ". Shows information about a bare metal node." +msgstr "" + +#: ./doc/common/section_cli_nova_baremetal.xml52(para) +msgid "Create a bare metal node:" +msgstr "" + +#: ./doc/common/section_cli_nova_baremetal.xml72(para) +msgid "Add a network interface to the node:" +msgstr "" + +#: ./doc/common/section_cli_nova_baremetal.xml84(para) +msgid "Launch an instance from a bare metal image:" +msgstr "" + +#: ./doc/common/section_cli_nova_baremetal.xml95(para) +msgid "List bare metal nodes and interfaces:" +msgstr "" + +#: ./doc/common/section_cli_nova_baremetal.xml97(para) +msgid "" +"When a node is in use, its status includes the UUID of the instance that " +"runs on it:" +msgstr "" + +#: ./doc/common/section_cli_nova_baremetal.xml111(para) +msgid "Show details for a bare metal node:" +msgstr "" + +#: ./doc/common/section_cli_nova_baremetal.xml133(para) +msgid "" +"Set the --availability_zone parameter to specify " +"which zone or node to use to start the server. Separate the zone from the " +"host name with a comma. For example:" +msgstr "" + +#: ./doc/common/section_cli_nova_baremetal.xml137(replaceable) +msgid "host" +msgstr "" + +#: ./doc/common/section_cli_nova_baremetal.xml137(replaceable) +msgid "node" +msgstr "" + +#: ./doc/common/section_cli_nova_baremetal.xml138(para) +msgid "" +"host is optional for the " +"--availability_zone parameter. " +"zone:,node also works." +msgstr "" + +#: ./doc/common/section_compute_config-api.xml6(title) +msgid "Configure the Compute API" +msgstr "" + +#: ./doc/common/section_compute_config-api.xml7(para) +msgid "" +"The Compute API, run by the nova-" +"api daemon, is the component of OpenStack Compute that receives" +" and responds to user requests, whether they be direct API calls, or via the" +" CLI tools or dashboard." +msgstr "" + +#: ./doc/common/section_compute_config-api.xml13(title) +msgid "Configure Compute API password handling" +msgstr "" + +#: ./doc/common/section_compute_config-api.xml14(para) +msgid "" +"The OpenStack Compute API enables users to specify an administrative " +"password when they create or rebuild a server instance. If the user does not" +" specify a password, a random password is generated and returned in the API " +"response." +msgstr "" + +#: ./doc/common/section_compute_config-api.xml19(para) +msgid "" +"In practice, how the admin password is handled depends on the hypervisor in " +"use and might require additional configuration of the instance. For example," +" you might have to install an agent to handle the password setting. If the " +"hypervisor and instance configuration do not support setting a password at " +"server create time, the password that is returned by the create API call is " +"misleading because it was ignored." +msgstr "" + +#: ./doc/common/section_compute_config-api.xml27(para) +msgid "" +"To prevent this confusion, use the " +" configuration option to disable the return of the admin password for " +"installations that do not support setting instance passwords." +msgstr "" + +#: ./doc/common/section_compute_config-api.xml34(title) +msgid "Configure Compute API rate limiting" +msgstr "" + +#: ./doc/common/section_compute_config-api.xml35(para) +msgid "" +"OpenStack Compute supports API rate limiting for the OpenStack API. The rate" +" limiting allows an administrator to configure limits on the type and number" +" of API calls that can be made in a specific time interval." +msgstr "" + +#: ./doc/common/section_compute_config-api.xml39(para) +msgid "" +"When API rate limits are exceeded, HTTP requests return an error with a " +"status code of 413Request entity too " +"large, and includes an HTTP Retry-After " +"header. The response body includes the error details and the delay before " +"you should retry the request." +msgstr "" + +#: ./doc/common/section_compute_config-api.xml45(para) +msgid "Rate limiting is not available for the EC2 API." +msgstr "" + +#: ./doc/common/section_compute_config-api.xml48(title) +msgid "Define limits" +msgstr "" + +#: ./doc/common/section_compute_config-api.xml49(para) +msgid "To define limits, set these values:" +msgstr "" + +#: ./doc/common/section_compute_config-api.xml52(para) +msgid "" +"The HTTP method used in the API call, " +"typically one of GET, PUT, POST, or DELETE." +msgstr "" + +#: ./doc/common/section_compute_config-api.xml57(para) +msgid "" +"A human readable URI that is used as a " +"friendly description of where the limit is applied." +msgstr "" + +#: ./doc/common/section_compute_config-api.xml62(para) +msgid "" +"A regular expression. The limit is " +"applied to all URIs that match the regular expression and HTTP method." +msgstr "" + +#: ./doc/common/section_compute_config-api.xml68(para) +msgid "" +"A limit value that specifies the maximum" +" count of units before the limit takes effect." +msgstr "" + +#: ./doc/common/section_compute_config-api.xml73(para) +msgid "" +"An interval that specifies time frame to " +"which the limit is applied. The interval can be SECOND, MINUTE, HOUR, or " +"DAY." +msgstr "" + +#: ./doc/common/section_compute_config-api.xml79(para) +msgid "" +"Rate limits are applied in relative order to the HTTP method, going from " +"least to most specific. For example, although the default threshold for POST" +" to */servers is 50 each day, you cannot POST to */servers more than 10 " +"times in a single minute because the rate limits for any POST is 10 each " +"minute." +msgstr "" + +#: ./doc/common/section_compute_config-api.xml87(title) +msgid "Default limits" +msgstr "" + +#: ./doc/common/section_compute_config-api.xml88(para) +msgid "" +"Normally, you install OpenStack Compute with the following limits enabled:" +msgstr "" + +#: ./doc/common/section_compute_config-api.xml91(caption) +msgid "Default API rate limits" +msgstr "" + +#: ./doc/common/section_compute_config-api.xml94(td) +#: ./doc/common/section_compute_config-api.xml159(para) +msgid "HTTP method" +msgstr "" + +#: ./doc/common/section_compute_config-api.xml95(td) +msgid "API URI" +msgstr "" + +#: ./doc/common/section_compute_config-api.xml96(td) +msgid "API regular expression" +msgstr "" + +#: ./doc/common/section_compute_config-api.xml97(td) +msgid "Limit" +msgstr "" + +#: ./doc/common/section_compute_config-api.xml102(td) +#: ./doc/common/section_compute_config-api.xml108(td) +msgid "POST" +msgstr "" + +#: ./doc/common/section_compute_config-api.xml103(td) +#: ./doc/common/section_compute_config-api.xml115(td) +#: ./doc/common/section_compute_config-api.xml127(td) +msgid "any URI (*)" +msgstr "" + +#: ./doc/common/section_compute_config-api.xml104(td) +#: ./doc/common/section_compute_config-api.xml116(td) +#: ./doc/common/section_compute_config-api.xml128(td) +msgid ".*" +msgstr "" + +#: ./doc/common/section_compute_config-api.xml105(td) +#: ./doc/common/section_compute_config-api.xml117(td) +msgid "10 per minute" +msgstr "" + +#: ./doc/common/section_compute_config-api.xml109(td) +msgid "/servers" +msgstr "" + +#: ./doc/common/section_compute_config-api.xml110(td) +msgid "^/servers" +msgstr "" + +#: ./doc/common/section_compute_config-api.xml111(td) +msgid "50 per day" +msgstr "" + +#: ./doc/common/section_compute_config-api.xml114(td) +msgid "PUT" +msgstr "" + +#: ./doc/common/section_compute_config-api.xml120(td) +msgid "GET" +msgstr "" + +#: ./doc/common/section_compute_config-api.xml121(td) +msgid "*changes-since*" +msgstr "" + +#: ./doc/common/section_compute_config-api.xml122(td) +msgid ".*changes-since.*" +msgstr "" + +#: ./doc/common/section_compute_config-api.xml123(td) +msgid "3 per minute" +msgstr "" + +#: ./doc/common/section_compute_config-api.xml126(td) +msgid "DELETE" +msgstr "" + +#: ./doc/common/section_compute_config-api.xml129(td) +msgid "100 per minute" +msgstr "" + +#: ./doc/common/section_compute_config-api.xml135(title) +msgid "Configure and change limits" +msgstr "" + +#: ./doc/common/section_compute_config-api.xml136(para) +msgid "" +"As part of the WSGI pipeline, the etc/nova/api-" +"paste.ini file defines the actual limits." +msgstr "" + +#: ./doc/common/section_compute_config-api.xml139(para) +msgid "" +"To enable limits, include the ' filter in the API " +"pipeline specification. If the filter is removed " +"from the pipeline, limiting is disabled. You must also define the rate limit" +" filter. The lines appear as follows:" +msgstr "" + +#: ./doc/common/section_compute_config-api.xml153(para) +msgid "" +"To modify the limits, add a limits specification to the " +"[filter:ratelimit] section of the file. Specify the " +"limits in this order:" +msgstr "" + +#: ./doc/common/section_compute_config-api.xml162(para) +msgid "friendly URI" +msgstr "" + +#: ./doc/common/section_compute_config-api.xml165(para) +msgid "regex" +msgstr "" + +#: ./doc/common/section_compute_config-api.xml168(para) +msgid "limit" +msgstr "" + +#: ./doc/common/section_compute_config-api.xml171(para) +msgid "interval" +msgstr "" + +#: ./doc/common/section_compute_config-api.xml174(para) +msgid "The following example shows the default rate-limiting values:" +msgstr "" + +#: ./doc/common/section_compute_config-api.xml182(para) +msgid "The following table lists the Compute API configuration options:" +msgstr "" + +#: ./doc/common/section_getstart_block-storage.xml5(title) +msgid "Block Storage Service" +msgstr "" + +#: ./doc/common/section_getstart_block-storage.xml6(para) +msgid "" +"The Block Storage Service enables management of volumes, volume snapshots, " +"and volume types. It includes the following components:" +msgstr "" + +#: ./doc/common/section_getstart_block-storage.xml11(para) +msgid "" +"cinder-api. Accepts API requests " +"and routes them to cinder-volume " +"for action." +msgstr "" + +#: ./doc/common/section_getstart_block-storage.xml17(para) +msgid "" +"cinder-volume. Responds to " +"requests to read from and write to the Block Storage database to maintain " +"state, interacting with other processes (like cinder-scheduler) through a message queue and directly upon " +"block storage providing hardware or software. It can interact with a variety" +" of storage providers through a driver architecture." +msgstr "" + +#: ./doc/common/section_getstart_block-storage.xml27(para) +msgid "" +"cinder-scheduler daemon. Like the" +" nova-scheduler, picks the " +"optimal block storage provider node on which to create the volume." +msgstr "" + +#: ./doc/common/section_getstart_block-storage.xml34(para) +msgid "" +"Messaging queue. Routes information between the Block Storage Service " +"processes." +msgstr "" + +#: ./doc/common/section_getstart_block-storage.xml38(para) +msgid "" +"The Block Storage Service interacts with Compute to provide volumes for " +"instances." +msgstr "" + +#: ./doc/common/section_getstart_image.xml5(title) +msgid "Image Service overview" +msgstr "" + +#: ./doc/common/section_getstart_image.xml6(para) +msgid "The Image Service includes the following components:" +msgstr "" + +#: ./doc/common/section_getstart_image.xml10(para) +msgid "" +"glance-api. Accepts Image API " +"calls for image discovery, retrieval, and storage." +msgstr "" + +#: ./doc/common/section_getstart_image.xml15(para) +msgid "" +"glance-registry. Stores, " +"processes, and retrieves metadata about images. Metadata includes items such" +" as size and type." +msgstr "" + +#: ./doc/common/section_getstart_image.xml21(para) +msgid "" +"Database. Stores image metadata. You can choose your database depending on " +"your preference. Most deployments use MySQL or SQlite." +msgstr "" + +#: ./doc/common/section_getstart_image.xml26(para) +msgid "" +"Storage repository for image files. In , " +"the Object Storage Service is the image repository. However, you can " +"configure a different repository. The Image Service supports normal file " +"systems, RADOS block devices, Amazon S3, and HTTP. Some choices provide only" +" read-only usage." +msgstr "" + +#: ./doc/common/section_getstart_image.xml34(para) +msgid "" +"A number of periodic processes run on the Image Service to support caching. " +"Replication services ensures consistency and availability through the " +"cluster. Other periodic processes include auditors, updaters, and reapers." +msgstr "" + +#: ./doc/common/section_getstart_image.xml38(para) +msgid "" +"As shown in , the Image Service " +"is central to the overall IaaS picture. It accepts API requests for images " +"or image metadata from end users or Compute components and can store its " +"disk files in the Object Storage Service." +msgstr "" + +#. When image changes, this message will be marked fuzzy or untranslated for +#. you. +#. It doesn't matter what you translate it to: it's not used at all. +#: ./doc/common/section_objectstorage-characteristics.xml50(None) +msgid "" +"@@image: '../common/figures/objectstorage.png'; " +"md5=e26e374ace84070f5fed24e73adcd562" +msgstr "" + +#. ... Old module003-ch003-obj-store-capabilities edited, renamed, and stored +#. in doc/common for use by both Cloud Admin and Operator Training Guides... +#: ./doc/common/section_objectstorage-characteristics.xml8(title) +msgid "Object Storage characteristics" +msgstr "" + +#: ./doc/common/section_objectstorage-characteristics.xml9(para) +msgid "The key characteristics of Object Storage are that:" +msgstr "" + +#: ./doc/common/section_objectstorage-characteristics.xml12(para) +msgid "All objects stored in Object Storage have a URL." +msgstr "" + +#: ./doc/common/section_objectstorage-characteristics.xml15(para) +msgid "" +"All objects stored are replicated 3✕ in as-unique-as-possible zones, which " +"can be defined as a group of drives, a node, a rack, and so on." +msgstr "" + +#: ./doc/common/section_objectstorage-characteristics.xml19(para) +msgid "All objects have their own metadata." +msgstr "" + +#: ./doc/common/section_objectstorage-characteristics.xml22(para) +msgid "" +"Developers interact with the object storage system through a RESTful HTTP " +"API." +msgstr "" + +#: ./doc/common/section_objectstorage-characteristics.xml26(para) +msgid "Object data can be located anywhere in the cluster." +msgstr "" + +#: ./doc/common/section_objectstorage-characteristics.xml29(para) +msgid "" +"The cluster scales by adding additional nodes without sacrificing " +"performance, which allows a more cost-effective linear storage expansion " +"than fork-lift upgrades." +msgstr "" + +#: ./doc/common/section_objectstorage-characteristics.xml34(para) +msgid "Data doesn't have to be migrate to an entirely new storage system." +msgstr "" + +#: ./doc/common/section_objectstorage-characteristics.xml37(para) +msgid "New nodes can be added to the cluster without downtime." +msgstr "" + +#: ./doc/common/section_objectstorage-characteristics.xml40(para) +msgid "Failed nodes and disks can be swapped out without downtime." +msgstr "" + +#: ./doc/common/section_objectstorage-characteristics.xml43(para) +msgid "" +"It runs on industry-standard hardware, such as Dell, HP, and Supermicro." +msgstr "" + +#: ./doc/common/section_objectstorage-characteristics.xml54(para) +msgid "" +"Developers can either write directly to the Swift API or use one of the many" +" client libraries that exist for all of the popular programming languages, " +"such as Java, Python, Ruby, and C#. Amazon S3 and RackSpace Cloud Files " +"users should be very familiar with Object Storage. Users new to object " +"storage systems will have to adjust to a different approach and mindset than" +" those required for a traditional filesystem." +msgstr "" + +#: ./doc/common/section_dashboard_sessions.xml6(title) +msgid "Set up session storage for the dashboard" +msgstr "" + +#: ./doc/common/section_dashboard_sessions.xml7(para) +msgid "" +"The dashboard uses Django " +"sessions framework to handle user session data. However, you can use " +"any available session back end. You customize the session back end through " +"the SESSION_ENGINE setting in your " +"local_settings file (on Fedora/RHEL/CentOS: " +"/etc/openstack-dashboard/local_settings, on Ubuntu and Debian: " +"/etc/openstack-dashboard/local_settings.py and on " +"openSUSE: /usr/share/openstack-" +"dashboard/openstack_dashboard/local/local_settings.py)." +msgstr "" + +#: ./doc/common/section_dashboard_sessions.xml18(para) +msgid "" +"The following sections describe the pros and cons of each option as it " +"pertains to deploying the dashboard." +msgstr "" + +#: ./doc/common/section_dashboard_sessions.xml21(title) +msgid "Local memory cache" +msgstr "" + +#: ./doc/common/section_dashboard_sessions.xml22(para) +msgid "" +"Local memory storage is the quickest and easiest session back end to set up," +" as it has no external dependencies whatsoever. It has the following " +"significant drawbacks:" +msgstr "" + +#: ./doc/common/section_dashboard_sessions.xml28(para) +msgid "No shared storage across processes or workers." +msgstr "" + +#: ./doc/common/section_dashboard_sessions.xml32(para) +msgid "No persistence after a process terminates." +msgstr "" + +#: ./doc/common/section_dashboard_sessions.xml36(para) +msgid "" +"The local memory back end is enabled as the default for Horizon solely " +"because it has no dependencies. It is not recommended for production use, or" +" even for serious development work. Enabled by:" +msgstr "" + +#: ./doc/common/section_dashboard_sessions.xml47(title) +msgid "Key-value stores" +msgstr "" + +#: ./doc/common/section_dashboard_sessions.xml48(para) +msgid "" +"You can use applications such as Memcached or Redis for external caching. " +"These applications offer persistence and shared storage and are useful for " +"small-scale deployments and/or development." +msgstr "" + +#: ./doc/common/section_dashboard_sessions.xml53(title) +msgid "Memcached" +msgstr "" + +#: ./doc/common/section_dashboard_sessions.xml54(para) +msgid "" +"Memcached is an high-performance and distributed memory object caching " +"system providing in-memory key-value store for small chunks of arbitrary " +"data." +msgstr "" + +#: ./doc/common/section_dashboard_sessions.xml56(para) +#: ./doc/common/section_dashboard_sessions.xml76(para) +msgid "Requirements:" +msgstr "" + +#: ./doc/common/section_dashboard_sessions.xml59(para) +msgid "Memcached service running and accessible." +msgstr "" + +#: ./doc/common/section_dashboard_sessions.xml62(para) +msgid "Python module python-memcached installed." +msgstr "" + +#: ./doc/common/section_dashboard_sessions.xml65(para) +#: ./doc/common/section_dashboard_sessions.xml85(para) +msgid "Enabled by:" +msgstr "" + +#: ./doc/common/section_dashboard_sessions.xml73(title) +msgid "Redis" +msgstr "" + +#: ./doc/common/section_dashboard_sessions.xml74(para) +msgid "" +"Redis is an open source, BSD licensed, advanced key-value store. It is often" +" referred to as a data structure server." +msgstr "" + +#: ./doc/common/section_dashboard_sessions.xml79(para) +msgid "Redis service running and accessible." +msgstr "" + +#: ./doc/common/section_dashboard_sessions.xml82(para) +msgid "" +"Python modules redis and django-redis " +"installed." +msgstr "" + +#: ./doc/common/section_dashboard_sessions.xml99(title) +msgid "Initialize and configure the database" +msgstr "" + +#: ./doc/common/section_dashboard_sessions.xml100(para) +msgid "" +"Database-backed sessions are scalable, persistent, and can be made high-" +"concurrency and highly-available." +msgstr "" + +#: ./doc/common/section_dashboard_sessions.xml102(para) +msgid "" +"However, database-backed sessions are one of the slower session storages and" +" incur a high overhead under heavy usage. Proper configuration of your " +"database deployment can also be a substantial undertaking and is far beyond " +"the scope of this documentation." +msgstr "" + +#: ./doc/common/section_dashboard_sessions.xml109(para) +msgid "Start the mysql command line client:" +msgstr "" + +#: ./doc/common/section_dashboard_sessions.xml113(para) +msgid "Enter the MySQL root user's password when prompted." +msgstr "" + +#: ./doc/common/section_dashboard_sessions.xml117(para) +msgid "To configure the MySQL database, create the dash database:" +msgstr "" + +#: ./doc/common/section_dashboard_sessions.xml122(para) +msgid "" +"Create a MySQL user for the newly-created dash database that has full " +"control of the database. Replace DASH_DBPASS with" +" a password for the new user:" +msgstr "" + +#: ./doc/common/section_dashboard_sessions.xml126(replaceable) +#: ./doc/common/section_dashboard_sessions.xml127(replaceable) +#: ./doc/common/section_dashboard_sessions.xml147(replaceable) +msgid "DASH_DBPASS" +msgstr "" + +#: ./doc/common/section_dashboard_sessions.xml130(para) +msgid "Enter quit at the mysql> prompt to exit MySQL." +msgstr "" + +#: ./doc/common/section_dashboard_sessions.xml134(para) +msgid "" +"In the local_settings file (on Fedora/RHEL/CentOS: " +" /etc/openstack-dashboard/local_settings, on " +"Ubuntu/Debian: /etc/openstack-" +"dashboard/local_settings.py and on openSUSE: /usr/share" +"/openstack-" +"dashboard/openstack_dashboard/local/local_settings.py), change " +"these options:" +msgstr "" + +#: ./doc/common/section_dashboard_sessions.xml154(para) +msgid "" +"After configuring the local_settings as shown, you can " +"run the command to populate this newly-created database." +msgstr "" + +#: ./doc/common/section_dashboard_sessions.xml159(para) +msgid "As a result, the following output is returned:" +msgstr "" + +#: ./doc/common/section_dashboard_sessions.xml167(para) +msgid "" +"On Ubuntu: If you want to avoid a warning when you restart apache2, create a" +" blackhole directory in the dashboard directory, as follows:" +msgstr "" + +#: ./doc/common/section_dashboard_sessions.xml173(para) +msgid "Restart Apache to pick up the default site and symbolic link settings:" +msgstr "" + +#: ./doc/common/section_dashboard_sessions.xml178(para) +msgid "On Fedora/RHEL/CentOS: " +msgstr "" + +#: ./doc/common/section_dashboard_sessions.xml187(para) +msgid "" +"On Ubuntu, restart the nova-api " +"service to ensure that the API server can connect to the dashboard without " +"error:" +msgstr "" + +#: ./doc/common/section_dashboard_sessions.xml195(title) +msgid "Cached database" +msgstr "" + +#: ./doc/common/section_dashboard_sessions.xml196(para) +msgid "" +"To mitigate the performance issues of database queries, you can use the " +"Django cached_db session back end, which utilizes both your database and " +"caching infrastructure to perform write-through caching and efficient " +"retrieval." +msgstr "" + +#: ./doc/common/section_dashboard_sessions.xml200(para) +msgid "" +"Enable this hybrid setting by configuring both your database and cache, as " +"discussed previously. Then, set the following value:" +msgstr "" + +#: ./doc/common/section_dashboard_sessions.xml206(title) +msgid "Cookies" +msgstr "" + +#: ./doc/common/section_dashboard_sessions.xml207(para) +msgid "" +"If you use Django 1.4 or later, the signed_cookies back end avoids server " +"load and scaling problems." +msgstr "" + +#: ./doc/common/section_dashboard_sessions.xml209(para) +msgid "" +"This back end stores session data in a cookie, which is stored by the user’s" +" browser. The back end uses a cryptographic signing technique to ensure " +"session data is not tampered with during transport. This is not the same as " +"encryption; session data is still readable by an attacker." +msgstr "" + +#: ./doc/common/section_dashboard_sessions.xml215(para) +msgid "" +"The pros of this engine are that it requires no additional dependencies or " +"infrastructure overhead, and it scales indefinitely as long as the quantity " +"of session data being stored fits into a normal cookie." +msgstr "" + +#: ./doc/common/section_dashboard_sessions.xml219(para) +msgid "" +"The biggest downside is that it places session data into storage on the " +"user’s machine and transports it over the wire. It also limits the quantity " +"of session data that can be stored." +msgstr "" + +#: ./doc/common/section_dashboard_sessions.xml223(para) +msgid "" +"See the Django cookie-based sessions documentation." +msgstr "" + +#: ./doc/common/section_objectstorage-troubleshoot.xml6(title) +msgid "Troubleshoot Object Storage" +msgstr "" + +#: ./doc/common/section_objectstorage-troubleshoot.xml7(para) +msgid "" +"For Object Storage, everything is logged in " +"/var/log/syslog (or messages on some distros). Several " +"settings enable further customization of logging, such as " +"log_name, log_facility, and " +"log_level, within the object server configuration files." +msgstr "" + +#: ./doc/common/section_objectstorage-troubleshoot.xml11(title) +msgid "Drive failure" +msgstr "" + +#: ./doc/common/section_objectstorage-troubleshoot.xml12(para) +msgid "" +"In the event that a drive has failed, the first step is to make sure the " +"drive is unmounted. This will make it easier for Object Storage to work " +"around the failure until it has been resolved. If the drive is going to be " +"replaced immediately, then it is just best to replace the drive, format it, " +"remount it, and let replication fill it up." +msgstr "" + +#: ./doc/common/section_objectstorage-troubleshoot.xml16(para) +msgid "" +"If the drive can’t be replaced immediately, then it is best to leave it " +"unmounted, and remove the drive from the ring. This will allow all the " +"replicas that were on that drive to be replicated elsewhere until the drive " +"is replaced. Once the drive is replaced, it can be re-added to the ring." +msgstr "" + +#: ./doc/common/section_objectstorage-troubleshoot.xml20(para) +msgid "" +"You can look at error messages in /var/log/kern.log for" +" hints of drive failure." +msgstr "" + +#: ./doc/common/section_objectstorage-troubleshoot.xml23(title) +msgid "Server failure" +msgstr "" + +#: ./doc/common/section_objectstorage-troubleshoot.xml24(para) +msgid "" +"If a server is having hardware issues, it is a good idea to make sure the " +"Object Storage services are not running. This will allow Object Storage to " +"work around the failure while you troubleshoot." +msgstr "" + +#: ./doc/common/section_objectstorage-troubleshoot.xml27(para) +msgid "" +"If the server just needs a reboot, or a small amount of work that should " +"only last a couple of hours, then it is probably best to let Object Storage " +"work around the failure and get the machine fixed and back online. When the " +"machine comes back online, replication will make sure that anything that is " +"missing during the downtime will get updated." +msgstr "" + +#: ./doc/common/section_objectstorage-troubleshoot.xml32(para) +msgid "" +"If the server has more serious issues, then it is probably best to remove " +"all of the server’s devices from the ring. Once the server has been repaired" +" and is back online, the server’s devices can be added back into the ring. " +"It is important that the devices are reformatted before putting them back " +"into the ring as it is likely to be responsible for a different set of " +"partitions than before." +msgstr "" + +#: ./doc/common/section_objectstorage-troubleshoot.xml40(title) +msgid "Detect failed drives" +msgstr "" + +#: ./doc/common/section_objectstorage-troubleshoot.xml41(para) +msgid "" +"It has been our experience that when a drive is about to fail, error " +"messages will spew into /var/log/kern.log. There is a script called swift-" +"drive-audit that can be run via cron to watch for bad drives. If errors are " +"detected, it will unmount the bad drive, so that Object Storage can work " +"around it. The script takes a configuration file with the following " +"settings:" +msgstr "" + +#: ./doc/common/section_objectstorage-troubleshoot.xml47(para) +msgid "" +"This script has only been tested on Ubuntu 10.04, so if you are using a " +"different distro or OS, some care should be taken before using in " +"production." +msgstr "" + +#: ./doc/common/section_objectstorage-troubleshoot.xml52(title) +msgid "Emergency recovery of ring builder files" +msgstr "" + +#: ./doc/common/section_objectstorage-troubleshoot.xml53(para) +msgid "" +"You should always keep a backup of Swift ring builder files. However, if an " +"emergency occurs, this procedure may assist in returning your cluster to an " +"operational state." +msgstr "" + +#: ./doc/common/section_objectstorage-troubleshoot.xml56(para) +msgid "" +"Using existing Swift tools, there is no way to recover a builder file from a" +" ring.gz file. However, if you have a knowledge of " +"Python, it is possible to construct a builder file that is pretty close to " +"the one you have lost. The following is what you will need to do." +msgstr "" + +#: ./doc/common/section_objectstorage-troubleshoot.xml61(para) +msgid "" +"This procedure is a last-resort for emergency circumstances—it requires " +"knowledge of the swift python code and may not succeed." +msgstr "" + +#: ./doc/common/section_objectstorage-troubleshoot.xml64(para) +msgid "First, load the ring and a new ringbuilder object in a Python REPL:" +msgstr "" + +#: ./doc/common/section_objectstorage-troubleshoot.xml67(para) +msgid "Now, start copying the data we have in the ring into the builder." +msgstr "" + +#: ./doc/common/section_objectstorage-troubleshoot.xml84(para) +msgid "" +"This is the extent of the recoverable fields. For " +"min_part_hours you'll either have to remember what the " +"value you used was, or just make up a new one." +msgstr "" + +#: ./doc/common/section_objectstorage-troubleshoot.xml89(para) +msgid "" +"Try some validation: if this doesn't raise an exception, you may feel some " +"hope. Not too much, though." +msgstr "" + +#: ./doc/common/section_objectstorage-troubleshoot.xml92(para) +msgid "Save the builder." +msgstr "" + +#: ./doc/common/section_objectstorage-troubleshoot.xml96(para) +msgid "" +"You should now have a file called 'account.builder' in the current working " +"directory. Next, run swift-ring-builder account.builder " +"write_ring and compare the new account.ring.gz to the " +"account.ring.gz that you started from. They probably won't be byte-for-byte " +"identical, but if you load them up in a REPL and their " +"_replica2part2dev_id and devs " +"attributes are the same (or nearly so), then you're in good shape." +msgstr "" + +#: ./doc/common/section_objectstorage-troubleshoot.xml103(para) +msgid "" +"Next, repeat the procedure for container.ring.gz and " +"object.ring.gz, and you might get usable builder files." +msgstr "" + +#: ./doc/common/tables/nova-cells.xml8(caption) +msgid "Description of configuration options for cells" +msgstr "" + +#: ./doc/common/tables/nova-cells.xml13(th) +#: ./doc/common/tables/glance-policy.xml13(th) +#: ./doc/common/tables/neutron-mlnx.xml13(th) +#: ./doc/common/tables/nova-ipv6.xml13(th) +#: ./doc/common/tables/cinder-eqlx.xml13(th) +#: ./doc/common/tables/swift-object-expirer-filter-catch_errors.xml12(th) +#: ./doc/common/tables/swift-object-expirer-filter-cache.xml12(th) +#: ./doc/common/tables/swift-proxy-server-filter-cache.xml12(th) +#: ./doc/common/tables/neutron-ml2_l2pop.xml13(th) +#: ./doc/common/tables/glance-qpid.xml13(th) +#: ./doc/common/tables/swift-container-server-DEFAULT.xml12(th) +#: ./doc/common/tables/nova-volumes.xml13(th) +#: ./doc/common/tables/glance-gridfs.xml13(th) +#: ./doc/common/tables/neutron-ml2_arista.xml13(th) +#: ./doc/common/tables/glance-filesystem.xml13(th) +#: ./doc/common/tables/swift-container-server-container-updater.xml12(th) +#: ./doc/common/tables/cinder-storage_gpfs.xml13(th) +#: ./doc/common/tables/nova-docker.xml13(th) +#: ./doc/common/tables/cinder-nexenta_iscsi.xml13(th) +#: ./doc/common/tables/nova-tilera.xml13(th) +#: ./doc/common/tables/nova-ca.xml13(th) +#: ./doc/common/tables/swift-account-server-filter-recon.xml12(th) +#: ./doc/common/tables/cinder-huawei.xml13(th) +#: ./doc/common/tables/swift-container-server-container-replicator.xml12(th) +#: ./doc/common/tables/nova-glance.xml13(th) +#: ./doc/common/tables/nova-neutron.xml13(th) +#: ./doc/common/tables/cinder-backups_ceph.xml13(th) +#: ./doc/common/tables/swift-proxy-server-filter-name_check.xml12(th) +#: ./doc/common/tables/nova-metadata.xml13(th) +#: ./doc/common/tables/glance-s3.xml13(th) +#: ./doc/common/tables/neutron-kombu.xml13(th) +#: ./doc/common/tables/swift-proxy-server-filter-ratelimit.xml12(th) +#: ./doc/common/tables/cinder-block-device.xml13(th) +#: ./doc/common/tables/cinder-zones.xml13(th) +#: ./doc/common/tables/cinder-netapp_7mode_iscsi.xml13(th) +#: ./doc/common/tables/swift-container-server-container-sync.xml12(th) +#: ./doc/common/tables/neutron-common.xml13(th) +#: ./doc/common/tables/swift-object-server-object-auditor.xml12(th) +#: ./doc/common/tables/neutron-openvswitch_agent.xml13(th) +#: ./doc/common/tables/cinder-compute.xml13(th) +#: ./doc/common/tables/cinder-lvm.xml13(th) +#: ./doc/common/tables/cinder-storage_nfs.xml13(th) +#: ./doc/common/tables/neutron-plumgrid.xml13(th) +#: ./doc/common/tables/nova-hypervisor.xml13(th) +#: ./doc/common/tables/swift-proxy-server-filter-tempurl.xml12(th) +#: ./doc/common/tables/cinder-quota.xml13(th) +#: ./doc/common/tables/swift-proxy-server-filter-healthcheck.xml12(th) +#: ./doc/common/tables/swift-object-expirer-DEFAULT.xml12(th) +#: ./doc/common/tables/nova-console.xml13(th) +#: ./doc/common/tables/swift-swift-bench-bench.xml12(th) +#: ./doc/common/tables/nova-common.xml13(th) +#: ./doc/common/tables/swift-object-server-object-updater.xml12(th) +#: ./doc/common/tables/glance-zmq.xml13(th) +#: ./doc/common/tables/swift-proxy-server-filter-account-quotas.xml12(th) +#: ./doc/common/tables/swift-proxy-server-app-proxy-server.xml12(th) +#: ./doc/common/tables/nova-keymgr.xml13(th) +#: ./doc/common/tables/neutron-api.xml13(th) +#: ./doc/common/tables/nova-testing.xml13(th) +#: ./doc/common/tables/cinder-backups.xml13(th) +#: ./doc/common/tables/swift-container-server-pipeline-main.xml12(th) +#: ./doc/common/tables/swift-rsyncd-object.xml12(th) +#: ./doc/common/tables/nova-s3.xml13(th) +#: ./doc/common/tables/neutron-openvswitch.xml13(th) +#: ./doc/common/tables/nova-zookeeper.xml13(th) +#: ./doc/common/tables/cinder-rpc.xml13(th) +#: ./doc/common/tables/cinder-api.xml13(th) +#: ./doc/common/tables/cinder-windows.xml13(th) +#: ./doc/common/tables/swift-object-server-pipeline-main.xml12(th) +#: ./doc/common/tables/cinder-san.xml13(th) +#: ./doc/common/tables/swift-account-server-app-account-server.xml12(th) +#: ./doc/common/tables/cinder-keymgr.xml13(th) +#: ./doc/common/tables/nova-db.xml13(th) +#: ./doc/common/tables/neutron-ml2_vxlan.xml13(th) +#: ./doc/common/tables/glance-logging.xml13(th) +#: ./doc/common/tables/glance-wsgi.xml13(th) +#: ./doc/common/tables/nova-periodic.xml13(th) +#: ./doc/common/tables/swift-account-server-filter-healthcheck.xml12(th) +#: ./doc/common/tables/cinder-images.xml13(th) +#: ./doc/common/tables/swift-container-server-app-container-server.xml12(th) +#: ./doc/common/tables/swift-proxy-server-filter-slo.xml12(th) +#: ./doc/common/tables/neutron-wsgi.xml13(th) +#: ./doc/common/tables/neutron-scheduler.xml13(th) +#: ./doc/common/tables/glance-rbd.xml13(th) +#: ./doc/common/tables/neutron-metadata.xml13(th) +#: ./doc/common/tables/cinder-hp3par.xml13(th) +#: ./doc/common/tables/cinder-storage_ceph.xml13(th) +#: ./doc/common/tables/nova-livemigration.xml13(th) +#: ./doc/common/tables/nova-ldap.xml13(th) +#: ./doc/common/tables/nova-fping.xml13(th) +#: ./doc/common/tables/neutron-securitygroups.xml13(th) +#: ./doc/common/tables/cinder-netapp_cdot_iscsi.xml13(th) +#: ./doc/common/tables/nova-ec2.xml13(th) +#: ./doc/common/tables/swift-account-server-account-auditor.xml12(th) +#: ./doc/common/tables/swift-object-server-DEFAULT.xml12(th) +#: ./doc/common/tables/cinder-nexenta_nfs.xml13(th) +#: ./doc/common/tables/swift-proxy-server-filter-bulk.xml12(th) +#: ./doc/common/tables/nova-policy.xml13(th) +#: ./doc/common/tables/neutron-logging.xml13(th) +#: ./doc/common/tables/glance-rpc.xml13(th) +#: ./doc/common/tables/nova-authentication.xml13(th) +#: ./doc/common/tables/cinder-vmware.xml13(th) +#: ./doc/common/tables/glance-sheepdog.xml13(th) +#: ./doc/common/tables/neutron-qpid.xml13(th) +#: ./doc/common/tables/neutron-hyperv_agent.xml13(th) +#: ./doc/common/tables/glance-swift.xml13(th) +#: ./doc/common/tables/swift-account-server-DEFAULT.xml12(th) +#: ./doc/common/tables/neutron-bigswitch.xml13(th) +#: ./doc/common/tables/nova-libvirt.xml13(th) +#: ./doc/common/tables/neutron-lbaas.xml13(th) +#: ./doc/common/tables/cinder-backups_swift.xml13(th) +#: ./doc/common/tables/neutron-ml2_cisco.xml13(th) +#: ./doc/common/tables/nova-pci.xml13(th) +#: ./doc/common/tables/swift-proxy-server-filter-proxy-logging.xml12(th) +#: ./doc/common/tables/neutron-varmour.xml13(th) +#: ./doc/common/tables/glance-imagecache.xml13(th) +#: ./doc/common/tables/swift-rsyncd-account.xml12(th) +#: ./doc/common/tables/cinder-storage.xml13(th) +#: ./doc/common/tables/nova-vpn.xml13(th) +#: ./doc/common/tables/nova-wsgi.xml13(th) +#: ./doc/common/tables/cinder-storage_glusterfs.xml13(th) +#: ./doc/common/tables/swift-container-server-filter-healthcheck.xml12(th) +#: ./doc/common/tables/nova-availabilityzones.xml13(th) +#: ./doc/common/tables/nova-vnc.xml13(th) +#: ./doc/common/tables/swift-swift-swift-constraints.xml12(th) +#: ./doc/common/tables/neutron-cisco.xml13(th) +#: ./doc/common/tables/nova-hyperv.xml13(th) +#: ./doc/common/tables/swift-object-server-filter-recon.xml12(th) +#: ./doc/common/tables/cinder-coraid.xml13(th) +#: ./doc/common/tables/swift-container-server-container-auditor.xml12(th) +#: ./doc/common/tables/swift-proxy-server-filter-catch_errors.xml12(th) +#: ./doc/common/tables/nova-vmware.xml13(th) +#: ./doc/common/tables/nova-logging.xml13(th) +#: ./doc/common/tables/nova-xen.xml13(th) +#: ./doc/common/tables/swift-proxy-server-filter-list-endpoints.xml12(th) +#: ./doc/common/tables/neutron-nicira.xml13(th) +#: ./doc/common/tables/swift-memcache-memcache.xml12(th) +#: ./doc/common/tables/swift-proxy-server-filter-keystoneauth.xml12(th) +#: ./doc/common/tables/neutron-ml2.xml13(th) +#: ./doc/common/tables/neutron-linuxbridge.xml13(th) +#: ./doc/common/tables/cinder-netapp_7mode_nfs.xml13(th) +#: ./doc/common/tables/glance-common.xml13(th) +#: ./doc/common/tables/nova-network.xml13(th) +#: ./doc/common/tables/cinder-scality.xml13(th) +#: ./doc/common/tables/neutron-notifier.xml13(th) +#: ./doc/common/tables/cinder-common.xml13(th) +#: ./doc/common/tables/nova-trustedcomputing.xml13(th) +#: ./doc/common/tables/neutron-ml2_flat.xml13(th) +#: ./doc/common/tables/nova-configdrive.xml13(th) +#: ./doc/common/tables/cinder-database.xml13(th) +#: ./doc/common/tables/neutron-rpc.xml13(th) +#: ./doc/common/tables/nova-zeromq.xml13(th) +#: ./doc/common/tables/glance-testing.xml13(th) +#: ./doc/common/tables/swift-proxy-server-filter-tempauth.xml12(th) +#: ./doc/common/tables/glance-registry.xml13(th) +#: ./doc/common/tables/ldap-keystone-conf.xml10(th) +#: ./doc/common/tables/swift-object-server-object-replicator.xml12(th) +#: ./doc/common/tables/swift-dispersion-dispersion.xml12(th) +#: ./doc/common/tables/swift-account-server-account-replicator.xml12(th) +#: ./doc/common/tables/neutron-fwaas.xml13(th) +#: ./doc/common/tables/glance-rabbitmq.xml13(th) +#: ./doc/common/tables/cinder-backups_tsm.xml13(th) +#: ./doc/common/tables/nova-qpid.xml13(th) +#: ./doc/common/tables/cinder-connection.xml13(th) +#: ./doc/common/tables/swift-proxy-server-filter-authtoken.xml12(th) +#: ./doc/common/tables/neutron-zeromq.xml13(th) +#: ./doc/common/tables/neutron-vpn.xml13(th) +#: ./doc/common/tables/cinder-log.xml13(th) +#: ./doc/common/tables/neutron-agent.xml13(th) +#: ./doc/common/tables/neutron-ryu.xml13(th) +#: ./doc/common/tables/swift-object-server-app-object-server.xml12(th) +#: ./doc/common/tables/neutron-policy.xml13(th) +#: ./doc/common/tables/swift-proxy-server-DEFAULT.xml12(th) +#: ./doc/common/tables/swift-proxy-server-filter-staticweb.xml12(th) +#: ./doc/common/tables/swift-object-expirer-app-proxy-server.xml12(th) +#: ./doc/common/tables/neutron-meta.xml13(th) +#: ./doc/common/tables/neutron-ssl.xml13(th) +#: ./doc/common/tables/nova-scheduling.xml13(th) +#: ./doc/common/tables/swift-drive-audit-drive-audit.xml12(th) +#: ./doc/common/tables/swift-container-server-filter-recon.xml12(th) +#: ./doc/common/tables/neutron-db.xml13(th) +#: ./doc/common/tables/neutron-brocade.xml13(th) +#: ./doc/common/tables/swift-object-expirer-pipeline-main.xml12(th) +#: ./doc/common/tables/neutron-linuxbridge_agent.xml13(th) +#: ./doc/common/tables/cinder-xiv.xml13(th) +#: ./doc/common/tables/neutron-rabbitmq.xml13(th) +#: ./doc/common/tables/swift-proxy-server-filter-container-quotas.xml12(th) +#: ./doc/common/tables/swift-swift-swift-hash.xml12(th) +#: ./doc/common/tables/cinder-auth.xml13(th) +#: ./doc/common/tables/nova-kombu.xml13(th) +#: ./doc/common/tables/swift-proxy-server-filter-formpost.xml12(th) +#: ./doc/common/tables/cinder-hds.xml13(th) +#: ./doc/common/tables/nova-spice.xml13(th) +#: ./doc/common/tables/neutron-midonet.xml13(th) +#: ./doc/common/tables/cinder-storwize.xml13(th) +#: ./doc/common/tables/cinder-solidfire.xml13(th) +#: ./doc/common/tables/glance-ssl.xml13(th) +#: ./doc/common/tables/nova-apiv3.xml13(th) +#: ./doc/common/tables/glance-db.xml13(th) +#: ./doc/common/tables/nova-api.xml13(th) +#: ./doc/common/tables/swift-rsyncd-container.xml12(th) +#: ./doc/common/tables/cinder-san-solaris.xml13(th) +#: ./doc/common/tables/cinder-netapp_cdot_nfs.xml13(th) +#: ./doc/common/tables/swift-object-server-filter-healthcheck.xml12(th) +#: ./doc/common/tables/glance-paste.xml13(th) +#: ./doc/common/tables/neutron-quotas.xml13(th) +#: ./doc/common/tables/nova-rpc.xml13(th) +#: ./doc/common/tables/nova-baremetal.xml13(th) +#: ./doc/common/tables/swift-account-server-pipeline-main.xml12(th) +#: ./doc/common/tables/glance-api.xml13(th) +#: ./doc/common/tables/cinder-scheduler.xml13(th) +#: ./doc/common/tables/neutron-ml2_ncs.xml13(th) +#: ./doc/common/tables/neutron-nec.xml13(th) +#: ./doc/common/tables/neutron-testing.xml13(th) +#: ./doc/common/tables/swift-object-expirer-object-expirer.xml12(th) +#: ./doc/common/tables/glance-cinder.xml13(th) +#: ./doc/common/tables/nova-redis.xml13(th) +#: ./doc/common/tables/neutron-embrane.xml13(th) +#: ./doc/common/tables/swift-proxy-server-pipeline-main.xml12(th) +#: ./doc/common/tables/nova-upgrade_levels.xml13(th) +#: ./doc/common/tables/swift-proxy-server-filter-cname_lookup.xml12(th) +#: ./doc/common/tables/nova-rabbitmq.xml13(th) +#: ./doc/common/tables/cinder-zadara.xml13(th) +#: ./doc/common/tables/swift-account-server-account-reaper.xml12(th) +#: ./doc/common/tables/nova-quota.xml13(th) +#: ./doc/common/tables/nova-conductor.xml13(th) +#: ./doc/common/tables/nova-compute.xml13(th) +#: ./doc/common/tables/swift-proxy-server-filter-domain_remap.xml12(th) +#: ./doc/common/tables/neutron-hyperv.xml13(th) +#: ./doc/common/tables/cinder-storage_xen.xml13(th) +#: ./doc/common/tables/nova-xvpnvncproxy.xml13(th) +msgid "Configuration option = Default value" +msgstr "" + +#: ./doc/common/tables/nova-cells.xml19(th) +#: ./doc/common/tables/nova-db.xml34(th) +#: ./doc/common/tables/nova-scheduling.xml114(th) +#: ./doc/common/tables/nova-rpc.xml62(th) +#: ./doc/common/tables/nova-upgrade_levels.xml19(th) +#: ./doc/common/tables/nova-quota.xml82(th) +msgid "[cells]" +msgstr "" + +#: ./doc/common/tables/nova-cells.xml22(td) +msgid "call_timeout = 60" +msgstr "" + +#: ./doc/common/tables/nova-cells.xml23(td) +msgid "(IntOpt) Seconds to wait for response from a call to a cell." +msgstr "" + +#: ./doc/common/tables/nova-cells.xml26(td) +msgid "capabilities = hypervisor=xenserver;kvm, os=linux;windows" +msgstr "" + +#: ./doc/common/tables/nova-cells.xml27(td) +msgid "(ListOpt) Key/Multi-value list with the capabilities of the cell" +msgstr "" + +#: ./doc/common/tables/nova-cells.xml30(td) +msgid "cell_type = compute" +msgstr "" + +#: ./doc/common/tables/nova-cells.xml31(td) +msgid "(StrOpt) Type of cell: api or compute" +msgstr "" + +#: ./doc/common/tables/nova-cells.xml34(td) +msgid "cells_config = None" +msgstr "" + +#: ./doc/common/tables/nova-cells.xml35(td) +msgid "" +"(StrOpt) Configuration file from which to read cells configuration. If " +"given, overrides reading cells from the database." +msgstr "" + +#: ./doc/common/tables/nova-cells.xml38(td) +msgid "driver = nova.cells.rpc_driver.CellsRPCDriver" +msgstr "" + +#: ./doc/common/tables/nova-cells.xml39(td) +msgid "(StrOpt) Cells communication driver to use" +msgstr "" + +#: ./doc/common/tables/nova-cells.xml42(td) +msgid "enable = False" +msgstr "" + +#: ./doc/common/tables/nova-cells.xml43(td) +msgid "(BoolOpt) Enable cell functionality" +msgstr "" + +#: ./doc/common/tables/nova-cells.xml46(td) +msgid "instance_update_num_instances = 1" +msgstr "" + +#: ./doc/common/tables/nova-cells.xml47(td) +msgid "(IntOpt) Number of instances to update per periodic task run" +msgstr "" + +#: ./doc/common/tables/nova-cells.xml50(td) +msgid "instance_updated_at_threshold = 3600" +msgstr "" + +#: ./doc/common/tables/nova-cells.xml51(td) +msgid "" +"(IntOpt) Number of seconds after an instance was updated or deleted to " +"continue to update cells" +msgstr "" + +#: ./doc/common/tables/nova-cells.xml54(td) +msgid "manager = nova.cells.manager.CellsManager" +msgstr "" + +#: ./doc/common/tables/nova-cells.xml55(td) +msgid "(StrOpt) Manager for cells" +msgstr "" + +#: ./doc/common/tables/nova-cells.xml58(td) +msgid "max_hop_count = 10" +msgstr "" + +#: ./doc/common/tables/nova-cells.xml59(td) +msgid "(IntOpt) Maximum number of hops for cells routing." +msgstr "" + +#: ./doc/common/tables/nova-cells.xml62(td) +msgid "mute_child_interval = 300" +msgstr "" + +#: ./doc/common/tables/nova-cells.xml63(td) +msgid "" +"(IntOpt) Number of seconds after which a lack of capability and capacity " +"updates signals the child cell is to be treated as a mute." +msgstr "" + +#: ./doc/common/tables/nova-cells.xml66(td) +msgid "mute_weight_multiplier = -10.0" +msgstr "" + +#: ./doc/common/tables/nova-cells.xml67(td) +msgid "" +"(FloatOpt) Multiplier used to weigh mute children. (The value should be " +"negative.)" +msgstr "" + +#: ./doc/common/tables/nova-cells.xml70(td) +msgid "mute_weight_value = 1000.0" +msgstr "" + +#: ./doc/common/tables/nova-cells.xml71(td) +msgid "" +"(FloatOpt) Weight value assigned to mute children. (The value should be " +"positive.)" +msgstr "" + +#: ./doc/common/tables/nova-cells.xml74(td) +msgid "name = nova" +msgstr "" + +#: ./doc/common/tables/nova-cells.xml75(td) +msgid "(StrOpt) name of this cell" +msgstr "" + +#: ./doc/common/tables/nova-cells.xml78(td) +msgid "offset_weight_multiplier = 1.0" +msgstr "" + +#: ./doc/common/tables/nova-cells.xml79(td) +msgid "(FloatOpt) Multiplier used to weigh offset weigher." +msgstr "" + +#: ./doc/common/tables/nova-cells.xml82(td) +msgid "reserve_percent = 10.0" +msgstr "" + +#: ./doc/common/tables/nova-cells.xml83(td) +msgid "" +"(FloatOpt) Percentage of cell capacity to hold in reserve. Affects both " +"memory and disk utilization" +msgstr "" + +#: ./doc/common/tables/nova-cells.xml86(td) +msgid "topic = cells" +msgstr "" + +#: ./doc/common/tables/nova-cells.xml87(td) +msgid "(StrOpt) the topic cells nodes listen on" +msgstr "" + +#: ./doc/common/tables/glance-policy.xml8(caption) +#: ./doc/common/tables/nova-policy.xml8(caption) +#: ./doc/common/tables/neutron-policy.xml8(caption) +msgid "Description of configuration options for policy" +msgstr "" + +#: ./doc/common/tables/glance-policy.xml22(td) +#: ./doc/common/tables/nova-policy.xml58(td) +#: ./doc/common/tables/cinder-common.xml146(td) +msgid "policy_default_rule = default" +msgstr "" + +#: ./doc/common/tables/glance-policy.xml23(td) +msgid "(StrOpt) The default policy to use." +msgstr "" + +#: ./doc/common/tables/glance-policy.xml26(td) +#: ./doc/common/tables/nova-policy.xml62(td) +#: ./doc/common/tables/cinder-common.xml150(td) +#: ./doc/common/tables/neutron-policy.xml23(td) +msgid "policy_file = policy.json" +msgstr "" + +#: ./doc/common/tables/glance-policy.xml27(td) +msgid "(StrOpt) The location of the policy file." +msgstr "" + +#: ./doc/common/tables/neutron-mlnx.xml8(caption) +msgid "Description of configuration options for mlnx" +msgstr "" + +#: ./doc/common/tables/neutron-mlnx.xml19(td) +msgid "backoff_rate = 2" +msgstr "" + +#: ./doc/common/tables/neutron-mlnx.xml20(td) +msgid "" +"(IntOpt) backoff rate multiplier for waiting period between retries for " +"request to daemon, i.e. value of 2 will double the request timeout each " +"retry" +msgstr "" + +#: ./doc/common/tables/neutron-mlnx.xml23(td) +msgid "daemon_endpoint = tcp://127.0.0.1:60001" +msgstr "" + +#: ./doc/common/tables/neutron-mlnx.xml24(td) +msgid "(StrOpt) eswitch daemon end point" +msgstr "" + +#: ./doc/common/tables/neutron-mlnx.xml27(td) +msgid "request_timeout = 3000" +msgstr "" + +#: ./doc/common/tables/neutron-mlnx.xml28(td) +msgid "" +"(IntOpt) The number of milliseconds the agent will wait for response on " +"request to daemon." +msgstr "" + +#: ./doc/common/tables/neutron-mlnx.xml31(td) +msgid "vnic_type = mlnx_direct" +msgstr "" + +#: ./doc/common/tables/neutron-mlnx.xml32(td) +msgid "(StrOpt) Type of VM network interface: mlnx_direct or hostdev" +msgstr "" + +#: ./doc/common/tables/nova-ipv6.xml8(caption) +msgid "Description of configuration options for ipv6" +msgstr "" + +#: ./doc/common/tables/nova-ipv6.xml22(td) +msgid "fixed_range_v6 = fd00::/48" +msgstr "" + +#: ./doc/common/tables/nova-ipv6.xml23(td) +msgid "(StrOpt) Fixed IPv6 address block" +msgstr "" + +#: ./doc/common/tables/nova-ipv6.xml26(td) +msgid "gateway_v6 = None" +msgstr "" + +#: ./doc/common/tables/nova-ipv6.xml27(td) +msgid "(StrOpt) Default IPv6 gateway" +msgstr "" + +#: ./doc/common/tables/nova-ipv6.xml30(td) +msgid "ipv6_backend = rfc2462" +msgstr "" + +#: ./doc/common/tables/nova-ipv6.xml31(td) +msgid "(StrOpt) Backend to use for IPv6 generation" +msgstr "" + +#: ./doc/common/tables/nova-ipv6.xml34(td) +msgid "use_ipv6 = False" +msgstr "" + +#: ./doc/common/tables/nova-ipv6.xml35(td) +msgid "(BoolOpt) use ipv6" +msgstr "" + +#: ./doc/common/tables/cinder-eqlx.xml8(caption) +msgid "Description of configuration options for eqlx" +msgstr "" + +#: ./doc/common/tables/cinder-eqlx.xml22(td) +msgid "eqlx_chap_login = admin" +msgstr "" + +#: ./doc/common/tables/cinder-eqlx.xml23(td) +msgid "(StrOpt) Existing CHAP account name" +msgstr "" + +#: ./doc/common/tables/cinder-eqlx.xml26(td) +msgid "eqlx_chap_password = password" +msgstr "" + +#: ./doc/common/tables/cinder-eqlx.xml27(td) +msgid "(StrOpt) Password for specified CHAP account name" +msgstr "" + +#: ./doc/common/tables/cinder-eqlx.xml30(td) +msgid "eqlx_cli_max_retries = 5" +msgstr "" + +#: ./doc/common/tables/cinder-eqlx.xml31(td) +msgid "(IntOpt) Maximum retry count for reconnection" +msgstr "" + +#: ./doc/common/tables/cinder-eqlx.xml34(td) +msgid "eqlx_cli_timeout = 30" +msgstr "" + +#: ./doc/common/tables/cinder-eqlx.xml35(td) +msgid "(IntOpt) Timeout for the Group Manager cli command execution" +msgstr "" + +#: ./doc/common/tables/cinder-eqlx.xml38(td) +msgid "eqlx_group_name = group-0" +msgstr "" + +#: ./doc/common/tables/cinder-eqlx.xml39(td) +msgid "(StrOpt) Group name to use for creating volumes" +msgstr "" + +#: ./doc/common/tables/cinder-eqlx.xml42(td) +msgid "eqlx_pool = default" +msgstr "" + +#: ./doc/common/tables/cinder-eqlx.xml43(td) +msgid "(StrOpt) Pool in which volumes will be created" +msgstr "" + +#: ./doc/common/tables/cinder-eqlx.xml46(td) +msgid "eqlx_use_chap = False" +msgstr "" + +#: ./doc/common/tables/cinder-eqlx.xml47(td) +msgid "(BoolOpt) Use CHAP authentication for targets?" +msgstr "" + +#: ./doc/common/tables/swift-object-expirer-filter-catch_errors.xml7(literal) +#: ./doc/common/tables/swift-proxy-server-filter-catch_errors.xml7(literal) +msgid "[filter:catch_errors]" +msgstr "" + +#: ./doc/common/tables/swift-object-expirer-filter-catch_errors.xml7(literal) +#: ./doc/common/tables/swift-object-expirer-filter-cache.xml7(literal) +#: ./doc/common/tables/swift-object-expirer-DEFAULT.xml7(literal) +#: ./doc/common/tables/swift-object-expirer-app-proxy-server.xml7(literal) +#: ./doc/common/tables/swift-object-expirer-pipeline-main.xml7(literal) +#: ./doc/common/tables/swift-object-expirer-object-expirer.xml7(literal) +msgid "object-expirer.conf-sample" +msgstr "" + +#: ./doc/common/tables/swift-object-expirer-filter-catch_errors.xml7(caption) +#: ./doc/common/tables/swift-object-expirer-filter-cache.xml7(caption) +#: ./doc/common/tables/swift-proxy-server-filter-cache.xml7(caption) +#: ./doc/common/tables/swift-container-server-DEFAULT.xml7(caption) +#: ./doc/common/tables/swift-container-server-container-updater.xml7(caption) +#: ./doc/common/tables/swift-account-server-filter-recon.xml7(caption) +#: ./doc/common/tables/swift-container-server-container-replicator.xml7(caption) +#: ./doc/common/tables/swift-proxy-server-filter-name_check.xml7(caption) +#: ./doc/common/tables/swift-proxy-server-filter-ratelimit.xml7(caption) +#: ./doc/common/tables/swift-container-server-container-sync.xml7(caption) +#: ./doc/common/tables/swift-object-server-object-auditor.xml7(caption) +#: ./doc/common/tables/swift-proxy-server-filter-tempurl.xml7(caption) +#: ./doc/common/tables/swift-proxy-server-filter-healthcheck.xml7(caption) +#: ./doc/common/tables/swift-object-expirer-DEFAULT.xml7(caption) +#: ./doc/common/tables/swift-swift-bench-bench.xml7(caption) +#: ./doc/common/tables/swift-object-server-object-updater.xml7(caption) +#: ./doc/common/tables/swift-proxy-server-filter-account-quotas.xml7(caption) +#: ./doc/common/tables/swift-proxy-server-app-proxy-server.xml7(caption) +#: ./doc/common/tables/swift-container-server-pipeline-main.xml7(caption) +#: ./doc/common/tables/swift-rsyncd-object.xml7(caption) +#: ./doc/common/tables/swift-object-server-pipeline-main.xml7(caption) +#: ./doc/common/tables/swift-account-server-app-account-server.xml7(caption) +#: ./doc/common/tables/swift-account-server-filter-healthcheck.xml7(caption) +#: ./doc/common/tables/swift-container-server-app-container-server.xml7(caption) +#: ./doc/common/tables/swift-proxy-server-filter-slo.xml7(caption) +#: ./doc/common/tables/swift-account-server-account-auditor.xml7(caption) +#: ./doc/common/tables/swift-object-server-DEFAULT.xml7(caption) +#: ./doc/common/tables/swift-proxy-server-filter-bulk.xml7(caption) +#: ./doc/common/tables/swift-account-server-DEFAULT.xml7(caption) +#: ./doc/common/tables/swift-proxy-server-filter-proxy-logging.xml7(caption) +#: ./doc/common/tables/swift-rsyncd-account.xml7(caption) +#: ./doc/common/tables/swift-container-server-filter-healthcheck.xml7(caption) +#: ./doc/common/tables/swift-swift-swift-constraints.xml7(caption) +#: ./doc/common/tables/swift-object-server-filter-recon.xml7(caption) +#: ./doc/common/tables/swift-container-server-container-auditor.xml7(caption) +#: ./doc/common/tables/swift-proxy-server-filter-catch_errors.xml7(caption) +#: ./doc/common/tables/swift-proxy-server-filter-list-endpoints.xml7(caption) +#: ./doc/common/tables/swift-memcache-memcache.xml7(caption) +#: ./doc/common/tables/swift-proxy-server-filter-keystoneauth.xml7(caption) +#: ./doc/common/tables/swift-proxy-server-filter-tempauth.xml7(caption) +#: ./doc/common/tables/swift-object-server-object-replicator.xml7(caption) +#: ./doc/common/tables/swift-dispersion-dispersion.xml7(caption) +#: ./doc/common/tables/swift-account-server-account-replicator.xml7(caption) +#: ./doc/common/tables/swift-proxy-server-filter-authtoken.xml7(caption) +#: ./doc/common/tables/swift-object-server-app-object-server.xml7(caption) +#: ./doc/common/tables/swift-proxy-server-DEFAULT.xml7(caption) +#: ./doc/common/tables/swift-proxy-server-filter-staticweb.xml7(caption) +#: ./doc/common/tables/swift-object-expirer-app-proxy-server.xml7(caption) +#: ./doc/common/tables/swift-drive-audit-drive-audit.xml7(caption) +#: ./doc/common/tables/swift-container-server-filter-recon.xml7(caption) +#: ./doc/common/tables/swift-object-expirer-pipeline-main.xml7(caption) +#: ./doc/common/tables/swift-proxy-server-filter-container-quotas.xml7(caption) +#: ./doc/common/tables/swift-swift-swift-hash.xml7(caption) +#: ./doc/common/tables/swift-proxy-server-filter-formpost.xml7(caption) +#: ./doc/common/tables/swift-rsyncd-container.xml7(caption) +#: ./doc/common/tables/swift-object-server-filter-healthcheck.xml7(caption) +#: ./doc/common/tables/swift-account-server-pipeline-main.xml7(caption) +#: ./doc/common/tables/swift-object-expirer-object-expirer.xml7(caption) +#: ./doc/common/tables/swift-proxy-server-pipeline-main.xml7(caption) +#: ./doc/common/tables/swift-proxy-server-filter-cname_lookup.xml7(caption) +#: ./doc/common/tables/swift-account-server-account-reaper.xml7(caption) +#: ./doc/common/tables/swift-proxy-server-filter-domain_remap.xml7(caption) +msgid "" +"Description of configuration options for in " +"" +msgstr "" + +#: ./doc/common/tables/swift-object-expirer-filter-catch_errors.xml18(td) +#: ./doc/common/tables/swift-proxy-server-filter-catch_errors.xml18(td) +msgid "use = egg:swift#catch_errors" +msgstr "" + +#: ./doc/common/tables/swift-object-expirer-filter-catch_errors.xml18(td) +#: ./doc/common/tables/swift-object-expirer-filter-cache.xml18(td) +#: ./doc/common/tables/swift-proxy-server-filter-cache.xml18(td) +#: ./doc/common/tables/swift-account-server-filter-recon.xml18(td) +#: ./doc/common/tables/swift-proxy-server-filter-name_check.xml18(td) +#: ./doc/common/tables/swift-proxy-server-filter-ratelimit.xml18(td) +#: ./doc/common/tables/swift-proxy-server-filter-healthcheck.xml18(td) +#: ./doc/common/tables/swift-proxy-server-filter-account-quotas.xml18(td) +#: ./doc/common/tables/swift-proxy-server-app-proxy-server.xml18(td) +#: ./doc/common/tables/swift-account-server-app-account-server.xml18(td) +#: ./doc/common/tables/swift-account-server-filter-healthcheck.xml18(td) +#: ./doc/common/tables/swift-container-server-app-container-server.xml18(td) +#: ./doc/common/tables/swift-proxy-server-filter-slo.xml18(td) +#: ./doc/common/tables/swift-proxy-server-filter-bulk.xml18(td) +#: ./doc/common/tables/swift-proxy-server-filter-proxy-logging.xml18(td) +#: ./doc/common/tables/swift-container-server-filter-healthcheck.xml18(td) +#: ./doc/common/tables/swift-object-server-filter-recon.xml18(td) +#: ./doc/common/tables/swift-proxy-server-filter-catch_errors.xml18(td) +#: ./doc/common/tables/swift-proxy-server-filter-list-endpoints.xml18(td) +#: ./doc/common/tables/swift-proxy-server-filter-keystoneauth.xml18(td) +#: ./doc/common/tables/swift-proxy-server-filter-tempauth.xml18(td) +#: ./doc/common/tables/swift-object-server-app-object-server.xml18(td) +#: ./doc/common/tables/swift-proxy-server-filter-staticweb.xml18(td) +#: ./doc/common/tables/swift-object-expirer-app-proxy-server.xml18(td) +#: ./doc/common/tables/swift-container-server-filter-recon.xml18(td) +#: ./doc/common/tables/swift-proxy-server-filter-container-quotas.xml18(td) +#: ./doc/common/tables/swift-proxy-server-filter-formpost.xml18(td) +#: ./doc/common/tables/swift-object-server-filter-healthcheck.xml18(td) +#: ./doc/common/tables/swift-proxy-server-filter-cname_lookup.xml18(td) +#: ./doc/common/tables/swift-proxy-server-filter-domain_remap.xml18(td) +msgid "Entry point of paste.deploy in the server" +msgstr "" + +#: ./doc/common/tables/swift-object-expirer-filter-cache.xml7(literal) +#: ./doc/common/tables/swift-proxy-server-filter-cache.xml7(literal) +msgid "[filter:cache]" +msgstr "" + +#: ./doc/common/tables/swift-object-expirer-filter-cache.xml18(td) +#: ./doc/common/tables/swift-proxy-server-filter-cache.xml18(td) +msgid "use = egg:swift#memcache" +msgstr "" + +#: ./doc/common/tables/cinder-netapp_cdot_extraspecs.xml4(caption) +msgid "" +"Description of extra specs options for NetApp Unified Driver with Clustered " +"Data ONTAP" +msgstr "" + +#: ./doc/common/tables/cinder-netapp_cdot_extraspecs.xml10(th) +msgid "Extra spec" +msgstr "" + +#: ./doc/common/tables/cinder-netapp_cdot_extraspecs.xml11(th) +msgid "Type" +msgstr "" + +#: ./doc/common/tables/cinder-netapp_cdot_extraspecs.xml17(literal) +msgid "netapp:raid_type" +msgstr "" + +#: ./doc/common/tables/cinder-netapp_cdot_extraspecs.xml18(td) +#: ./doc/common/tables/cinder-netapp_cdot_extraspecs.xml23(td) +#: ./doc/common/tables/cinder-netapp_cdot_extraspecs.xml29(td) +msgid "String" +msgstr "" + +#: ./doc/common/tables/cinder-netapp_cdot_extraspecs.xml19(literal) +msgid "raid4, raid_dp" +msgstr "" + +#: ./doc/common/tables/cinder-netapp_cdot_extraspecs.xml19(td) +msgid "" +"Limit the candidate volume list based on one of the following raid types: " +"." +msgstr "" + +#: ./doc/common/tables/cinder-netapp_cdot_extraspecs.xml22(literal) +msgid "netapp:disk_type" +msgstr "" + +#: ./doc/common/tables/cinder-netapp_cdot_extraspecs.xml24(literal) +msgid "" +"ATA, BSAS, EATA, FCAL, FSAS, LUN, MSATA, SAS, SATA, SCSI, XATA, XSAS, or " +"SSD." +msgstr "" + +#: ./doc/common/tables/cinder-netapp_cdot_extraspecs.xml24(td) +msgid "" +"Limit the candidate volume list based on one of the following disk types: " +"" +msgstr "" + +#: ./doc/common/tables/cinder-netapp_cdot_extraspecs.xml28(literal) +msgid "netapp:qos_policy_group" +msgstr "" + +#: ./doc/common/tables/cinder-netapp_cdot_extraspecs.xml30(td) +msgid "" +"Limit the candidate volume list based on the name of a QoS policy group, " +"which defines measurable Service Level Objectives that apply to the storage " +"objects with which the policy group is associated." +msgstr "" + +#: ./doc/common/tables/cinder-netapp_cdot_extraspecs.xml34(literal) +msgid "netapp_mirrored" +msgstr "" + +#: ./doc/common/tables/cinder-netapp_cdot_extraspecs.xml34(para) +msgid "" +"If both the positive and negative specs for a pair are specified (for " +"example, netapp_dedup and " +"netapp_nodedup) and set to the same value within a single" +" extra_specs list, then neither spec will be utilized by " +"the driver." +msgstr "" + +#: ./doc/common/tables/cinder-netapp_cdot_extraspecs.xml35(td) +#: ./doc/common/tables/cinder-netapp_cdot_extraspecs.xml40(td) +#: ./doc/common/tables/cinder-netapp_cdot_extraspecs.xml45(td) +#: ./doc/common/tables/cinder-netapp_cdot_extraspecs.xml50(td) +#: ./doc/common/tables/cinder-netapp_cdot_extraspecs.xml55(td) +#: ./doc/common/tables/cinder-netapp_cdot_extraspecs.xml60(td) +#: ./doc/common/tables/cinder-netapp_cdot_extraspecs.xml65(td) +#: ./doc/common/tables/cinder-netapp_cdot_extraspecs.xml70(td) +msgid "Boolean" +msgstr "" + +#: ./doc/common/tables/cinder-netapp_cdot_extraspecs.xml36(td) +msgid "" +"Limit the candidate volume list to only the ones that are mirrored on the " +"storage controller." +msgstr "" + +#: ./doc/common/tables/cinder-netapp_cdot_extraspecs.xml39(literal) +msgid "netapp_unmirrored" +msgstr "" + +#: ./doc/common/tables/cinder-netapp_cdot_extraspecs.xml41(td) +msgid "" +"Limit the candidate volume list to only the ones that are not mirrored on " +"the storage controller." +msgstr "" + +#: ./doc/common/tables/cinder-netapp_cdot_extraspecs.xml44(literal) +msgid "netapp_dedup" +msgstr "" + +#: ./doc/common/tables/cinder-netapp_cdot_extraspecs.xml46(td) +msgid "" +"Limit the candidate volume list to only the ones that have deduplication " +"enabled on the storage controller." +msgstr "" + +#: ./doc/common/tables/cinder-netapp_cdot_extraspecs.xml49(literal) +msgid "netapp_nodedup" +msgstr "" + +#: ./doc/common/tables/cinder-netapp_cdot_extraspecs.xml51(td) +msgid "" +"Limit the candidate volume list to only the ones that have deduplication " +"disabled on the storage controller." +msgstr "" + +#: ./doc/common/tables/cinder-netapp_cdot_extraspecs.xml54(literal) +msgid "netapp_compression" +msgstr "" + +#: ./doc/common/tables/cinder-netapp_cdot_extraspecs.xml56(td) +msgid "" +"Limit the candidate volume list to only the ones that have compression " +"enabled on the storage controller." +msgstr "" + +#: ./doc/common/tables/cinder-netapp_cdot_extraspecs.xml59(literal) +msgid "netapp_nocompression" +msgstr "" + +#: ./doc/common/tables/cinder-netapp_cdot_extraspecs.xml61(td) +msgid "" +"Limit the candidate volume list to only the ones that have compression " +"disabled on the storage controller." +msgstr "" + +#: ./doc/common/tables/cinder-netapp_cdot_extraspecs.xml64(literal) +msgid "netapp_thin_provisioned" +msgstr "" + +#: ./doc/common/tables/cinder-netapp_cdot_extraspecs.xml66(td) +msgid "" +"Limit the candidate volume list to only the ones that support thin " +"provisioning on the storage controller." +msgstr "" + +#: ./doc/common/tables/cinder-netapp_cdot_extraspecs.xml69(literal) +msgid "netapp_thick_provisioned" +msgstr "" + +#: ./doc/common/tables/cinder-netapp_cdot_extraspecs.xml71(td) +msgid "" +"Limit the candidate volume list to only the ones that support thick " +"provisioning on the storage controller." +msgstr "" + +#: ./doc/common/tables/swift-proxy-server-filter-cache.xml7(literal) +#: ./doc/common/tables/swift-proxy-server-filter-name_check.xml7(literal) +#: ./doc/common/tables/swift-proxy-server-filter-ratelimit.xml7(literal) +#: ./doc/common/tables/swift-proxy-server-filter-tempurl.xml7(literal) +#: ./doc/common/tables/swift-proxy-server-filter-healthcheck.xml7(literal) +#: ./doc/common/tables/swift-proxy-server-filter-account-quotas.xml7(literal) +#: ./doc/common/tables/swift-proxy-server-app-proxy-server.xml7(literal) +#: ./doc/common/tables/swift-proxy-server-filter-slo.xml7(literal) +#: ./doc/common/tables/swift-proxy-server-filter-bulk.xml7(literal) +#: ./doc/common/tables/swift-proxy-server-filter-proxy-logging.xml7(literal) +#: ./doc/common/tables/swift-proxy-server-filter-catch_errors.xml7(literal) +#: ./doc/common/tables/swift-proxy-server-filter-list-endpoints.xml7(literal) +#: ./doc/common/tables/swift-proxy-server-filter-keystoneauth.xml7(literal) +#: ./doc/common/tables/swift-proxy-server-filter-tempauth.xml7(literal) +#: ./doc/common/tables/swift-proxy-server-filter-authtoken.xml7(literal) +#: ./doc/common/tables/swift-proxy-server-DEFAULT.xml7(literal) +#: ./doc/common/tables/swift-proxy-server-filter-staticweb.xml7(literal) +#: ./doc/common/tables/swift-proxy-server-filter-container-quotas.xml7(literal) +#: ./doc/common/tables/swift-proxy-server-filter-formpost.xml7(literal) +#: ./doc/common/tables/swift-proxy-server-pipeline-main.xml7(literal) +#: ./doc/common/tables/swift-proxy-server-filter-cname_lookup.xml7(literal) +#: ./doc/common/tables/swift-proxy-server-filter-domain_remap.xml7(literal) +msgid "proxy-server.conf-sample" +msgstr "" + +#: ./doc/common/tables/swift-proxy-server-filter-cache.xml21(td) +msgid "set log_name = cache" +msgstr "" + +#: ./doc/common/tables/swift-proxy-server-filter-cache.xml21(td) +#: ./doc/common/tables/swift-proxy-server-filter-ratelimit.xml21(td) +#: ./doc/common/tables/swift-proxy-server-app-proxy-server.xml21(td) +#: ./doc/common/tables/swift-account-server-app-account-server.xml21(td) +#: ./doc/common/tables/swift-container-server-app-container-server.xml21(td) +#: ./doc/common/tables/swift-proxy-server-filter-catch_errors.xml21(td) +#: ./doc/common/tables/swift-proxy-server-filter-tempauth.xml21(td) +#: ./doc/common/tables/swift-object-server-app-object-server.xml21(td) +#: ./doc/common/tables/swift-proxy-server-filter-cname_lookup.xml21(td) +#: ./doc/common/tables/swift-proxy-server-filter-domain_remap.xml21(td) +msgid "Label to use when logging" +msgstr "" + +#: ./doc/common/tables/swift-proxy-server-filter-cache.xml24(td) +#: ./doc/common/tables/swift-proxy-server-filter-ratelimit.xml24(td) +#: ./doc/common/tables/swift-proxy-server-app-proxy-server.xml24(td) +#: ./doc/common/tables/swift-account-server-app-account-server.xml24(td) +#: ./doc/common/tables/swift-container-server-app-container-server.xml24(td) +#: ./doc/common/tables/swift-proxy-server-filter-catch_errors.xml24(td) +#: ./doc/common/tables/swift-proxy-server-filter-tempauth.xml24(td) +#: ./doc/common/tables/swift-object-server-app-object-server.xml24(td) +#: ./doc/common/tables/swift-proxy-server-filter-cname_lookup.xml24(td) +#: ./doc/common/tables/swift-proxy-server-filter-domain_remap.xml24(td) +msgid "set log_facility = LOG_LOCAL0" +msgstr "" + +#: ./doc/common/tables/swift-proxy-server-filter-cache.xml24(td) +#: ./doc/common/tables/swift-container-server-DEFAULT.xml64(td) +#: ./doc/common/tables/swift-container-server-container-updater.xml21(td) +#: ./doc/common/tables/swift-container-server-container-replicator.xml21(td) +#: ./doc/common/tables/swift-proxy-server-filter-ratelimit.xml24(td) +#: ./doc/common/tables/swift-container-server-container-sync.xml21(td) +#: ./doc/common/tables/swift-object-server-object-auditor.xml21(td) +#: ./doc/common/tables/swift-object-expirer-DEFAULT.xml27(td) +#: ./doc/common/tables/swift-object-server-object-updater.xml21(td) +#: ./doc/common/tables/swift-proxy-server-app-proxy-server.xml24(td) +#: ./doc/common/tables/swift-account-server-app-account-server.xml24(td) +#: ./doc/common/tables/swift-container-server-app-container-server.xml24(td) +#: ./doc/common/tables/swift-account-server-account-auditor.xml21(td) +#: ./doc/common/tables/swift-account-server-account-auditor.xml33(td) +#: ./doc/common/tables/swift-object-server-DEFAULT.xml64(td) +#: ./doc/common/tables/swift-account-server-DEFAULT.xml61(td) +#: ./doc/common/tables/swift-container-server-container-auditor.xml21(td) +#: ./doc/common/tables/swift-proxy-server-filter-catch_errors.xml24(td) +#: ./doc/common/tables/swift-proxy-server-filter-tempauth.xml24(td) +#: ./doc/common/tables/swift-object-server-object-replicator.xml21(td) +#: ./doc/common/tables/swift-account-server-account-replicator.xml21(td) +#: ./doc/common/tables/swift-object-server-app-object-server.xml24(td) +#: ./doc/common/tables/swift-proxy-server-DEFAULT.xml61(td) +#: ./doc/common/tables/swift-drive-audit-drive-audit.xml21(td) +#: ./doc/common/tables/swift-proxy-server-filter-cname_lookup.xml24(td) +#: ./doc/common/tables/swift-account-server-account-reaper.xml21(td) +#: ./doc/common/tables/swift-proxy-server-filter-domain_remap.xml24(td) +msgid "Syslog log facility" +msgstr "" + +#: ./doc/common/tables/swift-proxy-server-filter-cache.xml27(td) +#: ./doc/common/tables/swift-proxy-server-filter-ratelimit.xml27(td) +#: ./doc/common/tables/swift-proxy-server-app-proxy-server.xml27(td) +#: ./doc/common/tables/swift-account-server-app-account-server.xml27(td) +#: ./doc/common/tables/swift-container-server-app-container-server.xml27(td) +#: ./doc/common/tables/swift-proxy-server-filter-catch_errors.xml27(td) +#: ./doc/common/tables/swift-proxy-server-filter-tempauth.xml27(td) +#: ./doc/common/tables/swift-object-server-app-object-server.xml27(td) +#: ./doc/common/tables/swift-proxy-server-filter-cname_lookup.xml27(td) +#: ./doc/common/tables/swift-proxy-server-filter-domain_remap.xml27(td) +msgid "set log_level = INFO" +msgstr "" + +#: ./doc/common/tables/swift-proxy-server-filter-cache.xml27(td) +#: ./doc/common/tables/swift-proxy-server-filter-ratelimit.xml27(td) +#: ./doc/common/tables/swift-proxy-server-app-proxy-server.xml27(td) +#: ./doc/common/tables/swift-account-server-app-account-server.xml27(td) +#: ./doc/common/tables/swift-container-server-app-container-server.xml27(td) +#: ./doc/common/tables/swift-proxy-server-filter-catch_errors.xml27(td) +#: ./doc/common/tables/swift-proxy-server-filter-tempauth.xml27(td) +#: ./doc/common/tables/swift-object-server-app-object-server.xml27(td) +#: ./doc/common/tables/swift-proxy-server-filter-cname_lookup.xml27(td) +#: ./doc/common/tables/swift-proxy-server-filter-domain_remap.xml27(td) +msgid "Log level" +msgstr "" + +#: ./doc/common/tables/swift-proxy-server-filter-cache.xml30(td) +#: ./doc/common/tables/swift-proxy-server-filter-ratelimit.xml30(td) +#: ./doc/common/tables/swift-proxy-server-filter-catch_errors.xml30(td) +#: ./doc/common/tables/swift-proxy-server-filter-tempauth.xml30(td) +#: ./doc/common/tables/swift-proxy-server-filter-cname_lookup.xml30(td) +#: ./doc/common/tables/swift-proxy-server-filter-domain_remap.xml30(td) +msgid "set log_headers = false" +msgstr "" + +#: ./doc/common/tables/swift-proxy-server-filter-cache.xml30(td) +#: ./doc/common/tables/swift-proxy-server-filter-ratelimit.xml30(td) +#: ./doc/common/tables/swift-proxy-server-filter-catch_errors.xml30(td) +#: ./doc/common/tables/swift-proxy-server-filter-tempauth.xml30(td) +#: ./doc/common/tables/swift-proxy-server-filter-cname_lookup.xml30(td) +#: ./doc/common/tables/swift-proxy-server-filter-domain_remap.xml30(td) +msgid "If True, log headers in each request" +msgstr "" + +#: ./doc/common/tables/swift-proxy-server-filter-cache.xml33(td) +#: ./doc/common/tables/swift-proxy-server-filter-ratelimit.xml33(td) +#: ./doc/common/tables/swift-proxy-server-app-proxy-server.xml30(td) +#: ./doc/common/tables/swift-account-server-app-account-server.xml33(td) +#: ./doc/common/tables/swift-container-server-app-container-server.xml33(td) +#: ./doc/common/tables/swift-proxy-server-filter-catch_errors.xml33(td) +#: ./doc/common/tables/swift-proxy-server-filter-tempauth.xml33(td) +#: ./doc/common/tables/swift-object-server-app-object-server.xml33(td) +#: ./doc/common/tables/swift-proxy-server-filter-cname_lookup.xml33(td) +#: ./doc/common/tables/swift-proxy-server-filter-domain_remap.xml33(td) +msgid "set log_address = /dev/log" +msgstr "" + +#: ./doc/common/tables/swift-proxy-server-filter-cache.xml33(td) +#: ./doc/common/tables/swift-proxy-server-filter-cache.xml39(td) +#: ./doc/common/tables/swift-container-server-DEFAULT.xml58(td) +#: ./doc/common/tables/swift-proxy-server-filter-ratelimit.xml33(td) +#: ./doc/common/tables/swift-proxy-server-filter-ratelimit.xml57(td) +#: ./doc/common/tables/swift-proxy-server-filter-ratelimit.xml60(td) +#: ./doc/common/tables/swift-proxy-server-filter-ratelimit.xml63(td) +#: ./doc/common/tables/swift-proxy-server-filter-ratelimit.xml66(td) +#: ./doc/common/tables/swift-proxy-server-filter-ratelimit.xml69(td) +#: ./doc/common/tables/swift-proxy-server-filter-ratelimit.xml72(td) +#: ./doc/common/tables/swift-proxy-server-filter-ratelimit.xml75(td) +#: ./doc/common/tables/swift-object-server-object-auditor.xml45(td) +#: ./doc/common/tables/swift-proxy-server-filter-healthcheck.xml21(td) +#: ./doc/common/tables/swift-swift-bench-bench.xml24(td) +#: ./doc/common/tables/swift-swift-bench-bench.xml30(td) +#: ./doc/common/tables/swift-swift-bench-bench.xml36(td) +#: ./doc/common/tables/swift-swift-bench-bench.xml39(td) +#: ./doc/common/tables/swift-swift-bench-bench.xml42(td) +#: ./doc/common/tables/swift-swift-bench-bench.xml48(td) +#: ./doc/common/tables/swift-swift-bench-bench.xml51(td) +#: ./doc/common/tables/swift-swift-bench-bench.xml54(td) +#: ./doc/common/tables/swift-swift-bench-bench.xml57(td) +#: ./doc/common/tables/swift-swift-bench-bench.xml60(td) +#: ./doc/common/tables/swift-swift-bench-bench.xml63(td) +#: ./doc/common/tables/swift-swift-bench-bench.xml66(td) +#: ./doc/common/tables/swift-swift-bench-bench.xml69(td) +#: ./doc/common/tables/swift-swift-bench-bench.xml72(td) +#: ./doc/common/tables/swift-swift-bench-bench.xml75(td) +#: ./doc/common/tables/swift-swift-bench-bench.xml78(td) +#: ./doc/common/tables/swift-swift-bench-bench.xml81(td) +#: ./doc/common/tables/swift-swift-bench-bench.xml87(td) +#: ./doc/common/tables/swift-proxy-server-app-proxy-server.xml30(td) +#: ./doc/common/tables/swift-proxy-server-app-proxy-server.xml33(td) +#: ./doc/common/tables/swift-proxy-server-app-proxy-server.xml75(td) +#: ./doc/common/tables/swift-proxy-server-app-proxy-server.xml81(td) +#: ./doc/common/tables/swift-proxy-server-app-proxy-server.xml90(td) +#: ./doc/common/tables/swift-proxy-server-app-proxy-server.xml93(td) +#: ./doc/common/tables/swift-proxy-server-app-proxy-server.xml96(td) +#: ./doc/common/tables/swift-proxy-server-app-proxy-server.xml99(td) +#: ./doc/common/tables/swift-proxy-server-app-proxy-server.xml105(td) +#: ./doc/common/tables/swift-proxy-server-app-proxy-server.xml108(td) +#: ./doc/common/tables/swift-proxy-server-app-proxy-server.xml111(td) +#: ./doc/common/tables/swift-proxy-server-app-proxy-server.xml114(td) +#: ./doc/common/tables/swift-proxy-server-app-proxy-server.xml117(td) +#: ./doc/common/tables/swift-container-server-pipeline-main.xml18(td) +#: ./doc/common/tables/swift-rsyncd-object.xml18(td) +#: ./doc/common/tables/swift-rsyncd-object.xml21(td) +#: ./doc/common/tables/swift-rsyncd-object.xml24(td) +#: ./doc/common/tables/swift-rsyncd-object.xml27(td) +#: ./doc/common/tables/swift-object-server-pipeline-main.xml18(td) +#: ./doc/common/tables/swift-account-server-app-account-server.xml33(td) +#: ./doc/common/tables/swift-account-server-filter-healthcheck.xml21(td) +#: ./doc/common/tables/swift-container-server-app-container-server.xml33(td) +#: ./doc/common/tables/swift-proxy-server-filter-slo.xml21(td) +#: ./doc/common/tables/swift-proxy-server-filter-slo.xml24(td) +#: ./doc/common/tables/swift-proxy-server-filter-slo.xml27(td) +#: ./doc/common/tables/swift-object-server-DEFAULT.xml45(td) +#: ./doc/common/tables/swift-proxy-server-filter-bulk.xml21(td) +#: ./doc/common/tables/swift-proxy-server-filter-bulk.xml24(td) +#: ./doc/common/tables/swift-proxy-server-filter-bulk.xml27(td) +#: ./doc/common/tables/swift-proxy-server-filter-bulk.xml30(td) +#: ./doc/common/tables/swift-proxy-server-filter-proxy-logging.xml21(td) +#: ./doc/common/tables/swift-proxy-server-filter-proxy-logging.xml24(td) +#: ./doc/common/tables/swift-proxy-server-filter-proxy-logging.xml27(td) +#: ./doc/common/tables/swift-proxy-server-filter-proxy-logging.xml30(td) +#: ./doc/common/tables/swift-proxy-server-filter-proxy-logging.xml33(td) +#: ./doc/common/tables/swift-proxy-server-filter-proxy-logging.xml36(td) +#: ./doc/common/tables/swift-proxy-server-filter-proxy-logging.xml39(td) +#: ./doc/common/tables/swift-proxy-server-filter-proxy-logging.xml42(td) +#: ./doc/common/tables/swift-proxy-server-filter-proxy-logging.xml45(td) +#: ./doc/common/tables/swift-proxy-server-filter-proxy-logging.xml48(td) +#: ./doc/common/tables/swift-proxy-server-filter-proxy-logging.xml51(td) +#: ./doc/common/tables/swift-proxy-server-filter-proxy-logging.xml54(td) +#: ./doc/common/tables/swift-proxy-server-filter-proxy-logging.xml57(td) +#: ./doc/common/tables/swift-proxy-server-filter-proxy-logging.xml69(td) +#: ./doc/common/tables/swift-rsyncd-account.xml18(td) +#: ./doc/common/tables/swift-rsyncd-account.xml21(td) +#: ./doc/common/tables/swift-rsyncd-account.xml24(td) +#: ./doc/common/tables/swift-rsyncd-account.xml27(td) +#: ./doc/common/tables/swift-container-server-filter-healthcheck.xml21(td) +#: ./doc/common/tables/swift-object-server-filter-recon.xml24(td) +#: ./doc/common/tables/swift-proxy-server-filter-catch_errors.xml33(td) +#: ./doc/common/tables/swift-proxy-server-filter-list-endpoints.xml21(td) +#: ./doc/common/tables/swift-memcache-memcache.xml21(td) +#: ./doc/common/tables/swift-proxy-server-filter-keystoneauth.xml21(td) +#: ./doc/common/tables/swift-proxy-server-filter-tempauth.xml33(td) +#: ./doc/common/tables/swift-proxy-server-filter-tempauth.xml45(td) +#: ./doc/common/tables/swift-proxy-server-filter-tempauth.xml51(td) +#: ./doc/common/tables/swift-proxy-server-filter-tempauth.xml54(td) +#: ./doc/common/tables/swift-proxy-server-filter-tempauth.xml57(td) +#: ./doc/common/tables/swift-proxy-server-filter-tempauth.xml60(td) +#: ./doc/common/tables/swift-object-server-object-replicator.xml48(td) +#: ./doc/common/tables/swift-object-server-object-replicator.xml69(td) +#: ./doc/common/tables/swift-dispersion-dispersion.xml24(td) +#: ./doc/common/tables/swift-dispersion-dispersion.xml33(td) +#: ./doc/common/tables/swift-dispersion-dispersion.xml42(td) +#: ./doc/common/tables/swift-dispersion-dispersion.xml48(td) +#: ./doc/common/tables/swift-dispersion-dispersion.xml51(td) +#: ./doc/common/tables/swift-dispersion-dispersion.xml57(td) +#: ./doc/common/tables/swift-dispersion-dispersion.xml60(td) +#: ./doc/common/tables/swift-dispersion-dispersion.xml63(td) +#: ./doc/common/tables/swift-proxy-server-filter-authtoken.xml18(td) +#: ./doc/common/tables/swift-proxy-server-filter-authtoken.xml21(td) +#: ./doc/common/tables/swift-proxy-server-filter-authtoken.xml24(td) +#: ./doc/common/tables/swift-proxy-server-filter-authtoken.xml27(td) +#: ./doc/common/tables/swift-proxy-server-filter-authtoken.xml30(td) +#: ./doc/common/tables/swift-proxy-server-filter-authtoken.xml33(td) +#: ./doc/common/tables/swift-proxy-server-filter-authtoken.xml36(td) +#: ./doc/common/tables/swift-proxy-server-filter-authtoken.xml39(td) +#: ./doc/common/tables/swift-proxy-server-filter-authtoken.xml42(td) +#: ./doc/common/tables/swift-object-server-app-object-server.xml33(td) +#: ./doc/common/tables/swift-proxy-server-DEFAULT.xml55(td) +#: ./doc/common/tables/swift-proxy-server-DEFAULT.xml67(td) +#: ./doc/common/tables/swift-proxy-server-DEFAULT.xml73(td) +#: ./doc/common/tables/swift-drive-audit-drive-audit.xml39(td) +#: ./doc/common/tables/swift-object-expirer-pipeline-main.xml18(td) +#: ./doc/common/tables/swift-rsyncd-container.xml18(td) +#: ./doc/common/tables/swift-rsyncd-container.xml21(td) +#: ./doc/common/tables/swift-rsyncd-container.xml24(td) +#: ./doc/common/tables/swift-rsyncd-container.xml27(td) +#: ./doc/common/tables/swift-object-server-filter-healthcheck.xml21(td) +#: ./doc/common/tables/swift-account-server-pipeline-main.xml18(td) +#: ./doc/common/tables/swift-object-expirer-object-expirer.xml24(td) +#: ./doc/common/tables/swift-object-expirer-object-expirer.xml30(td) +#: ./doc/common/tables/swift-proxy-server-pipeline-main.xml18(td) +#: ./doc/common/tables/swift-proxy-server-filter-cname_lookup.xml33(td) +#: ./doc/common/tables/swift-account-server-account-reaper.xml45(td) +#: ./doc/common/tables/swift-proxy-server-filter-domain_remap.xml33(td) +msgid "No help text available for this option" +msgstr "" + +#: ./doc/common/tables/swift-proxy-server-filter-cache.xml36(td) +#: ./doc/common/tables/swift-memcache-memcache.xml18(td) +msgid "memcache_servers = 127.0.0.1:11211" +msgstr "" + +#: ./doc/common/tables/swift-proxy-server-filter-cache.xml36(td) +#: ./doc/common/tables/swift-memcache-memcache.xml18(td) +msgid "Comma separated list of memcached servers ip:port services" +msgstr "" + +#: ./doc/common/tables/swift-proxy-server-filter-cache.xml39(td) +#: ./doc/common/tables/swift-memcache-memcache.xml21(td) +msgid "memcache_serialization_support = 2" +msgstr "" + +#: ./doc/common/tables/neutron-ml2_l2pop.xml8(caption) +msgid "Description of configuration options for ml2_l2pop" +msgstr "" + +#: ./doc/common/tables/neutron-ml2_l2pop.xml19(td) +msgid "agent_boot_time = 180" +msgstr "" + +#: ./doc/common/tables/neutron-ml2_l2pop.xml20(td) +msgid "" +"(IntOpt) Delay within which agent is expected to update existing ports whent" +" it restarts" +msgstr "" + +#: ./doc/common/tables/glance-qpid.xml8(caption) +#: ./doc/common/tables/neutron-qpid.xml8(caption) +#: ./doc/common/tables/nova-qpid.xml8(caption) +msgid "Description of configuration options for qpid" +msgstr "" + +#: ./doc/common/tables/glance-qpid.xml22(td) +#: ./doc/common/tables/cinder-rpc.xml86(td) +#: ./doc/common/tables/neutron-qpid.xml19(td) +#: ./doc/common/tables/nova-qpid.xml22(td) +msgid "qpid_heartbeat = 60" +msgstr "" + +#: ./doc/common/tables/glance-qpid.xml23(td) +#: ./doc/common/tables/cinder-rpc.xml87(td) +#: ./doc/common/tables/neutron-qpid.xml20(td) +#: ./doc/common/tables/nova-qpid.xml23(td) +msgid "(IntOpt) Seconds between connection keepalive heartbeats" +msgstr "" + +#: ./doc/common/tables/glance-qpid.xml26(td) +#: ./doc/common/tables/cinder-rpc.xml90(td) +#: ./doc/common/tables/neutron-qpid.xml23(td) +#: ./doc/common/tables/nova-qpid.xml26(td) +msgid "qpid_hostname = localhost" +msgstr "" + +#: ./doc/common/tables/glance-qpid.xml27(td) +#: ./doc/common/tables/cinder-rpc.xml91(td) +#: ./doc/common/tables/neutron-qpid.xml24(td) +#: ./doc/common/tables/nova-qpid.xml27(td) +msgid "(StrOpt) Qpid broker hostname" +msgstr "" + +#: ./doc/common/tables/glance-qpid.xml30(td) +#: ./doc/common/tables/cinder-rpc.xml94(td) +#: ./doc/common/tables/neutron-qpid.xml27(td) +#: ./doc/common/tables/nova-qpid.xml30(td) +msgid "qpid_hosts = $qpid_hostname:$qpid_port" +msgstr "" + +#: ./doc/common/tables/glance-qpid.xml31(td) +#: ./doc/common/tables/cinder-rpc.xml95(td) +#: ./doc/common/tables/neutron-qpid.xml28(td) +#: ./doc/common/tables/nova-qpid.xml31(td) +msgid "(ListOpt) Qpid HA cluster host:port pairs" +msgstr "" + +#: ./doc/common/tables/glance-qpid.xml34(td) +#: ./doc/common/tables/cinder-rpc.xml98(td) +#: ./doc/common/tables/neutron-qpid.xml31(td) +#: ./doc/common/tables/nova-qpid.xml34(td) +msgid "qpid_password =" +msgstr "" + +#: ./doc/common/tables/glance-qpid.xml35(td) +msgid "(StrOpt) Password for Qpid connection" +msgstr "" + +#: ./doc/common/tables/glance-qpid.xml38(td) +#: ./doc/common/tables/cinder-rpc.xml102(td) +#: ./doc/common/tables/neutron-qpid.xml35(td) +#: ./doc/common/tables/nova-qpid.xml38(td) +msgid "qpid_port = 5672" +msgstr "" + +#: ./doc/common/tables/glance-qpid.xml39(td) +#: ./doc/common/tables/cinder-rpc.xml103(td) +#: ./doc/common/tables/neutron-qpid.xml36(td) +#: ./doc/common/tables/nova-qpid.xml39(td) +msgid "(IntOpt) Qpid broker port" +msgstr "" + +#: ./doc/common/tables/glance-qpid.xml42(td) +#: ./doc/common/tables/cinder-rpc.xml106(td) +#: ./doc/common/tables/neutron-qpid.xml39(td) +#: ./doc/common/tables/nova-qpid.xml42(td) +msgid "qpid_protocol = tcp" +msgstr "" + +#: ./doc/common/tables/glance-qpid.xml43(td) +#: ./doc/common/tables/cinder-rpc.xml107(td) +#: ./doc/common/tables/neutron-qpid.xml40(td) +#: ./doc/common/tables/nova-qpid.xml43(td) +msgid "(StrOpt) Transport to use, either 'tcp' or 'ssl'" +msgstr "" + +#: ./doc/common/tables/glance-qpid.xml46(td) +#: ./doc/common/tables/cinder-rpc.xml110(td) +#: ./doc/common/tables/neutron-qpid.xml43(td) +#: ./doc/common/tables/nova-qpid.xml46(td) +msgid "qpid_sasl_mechanisms =" +msgstr "" + +#: ./doc/common/tables/glance-qpid.xml47(td) +#: ./doc/common/tables/cinder-rpc.xml111(td) +#: ./doc/common/tables/neutron-qpid.xml44(td) +#: ./doc/common/tables/nova-qpid.xml47(td) +msgid "(StrOpt) Space separated list of SASL mechanisms to use for auth" +msgstr "" + +#: ./doc/common/tables/glance-qpid.xml50(td) +#: ./doc/common/tables/cinder-rpc.xml114(td) +#: ./doc/common/tables/neutron-qpid.xml47(td) +#: ./doc/common/tables/nova-qpid.xml50(td) +msgid "qpid_tcp_nodelay = True" +msgstr "" + +#: ./doc/common/tables/glance-qpid.xml51(td) +#: ./doc/common/tables/cinder-rpc.xml115(td) +#: ./doc/common/tables/neutron-qpid.xml48(td) +#: ./doc/common/tables/nova-qpid.xml51(td) +msgid "(BoolOpt) Disable Nagle algorithm" +msgstr "" + +#: ./doc/common/tables/glance-qpid.xml54(td) +#: ./doc/common/tables/cinder-rpc.xml118(td) +#: ./doc/common/tables/neutron-qpid.xml51(td) +#: ./doc/common/tables/nova-qpid.xml54(td) +msgid "qpid_topology_version = 1" +msgstr "" + +#: ./doc/common/tables/glance-qpid.xml55(td) +#: ./doc/common/tables/cinder-rpc.xml119(td) +#: ./doc/common/tables/neutron-qpid.xml52(td) +#: ./doc/common/tables/nova-qpid.xml55(td) +msgid "" +"(IntOpt) The qpid topology version to use. Version 1 is what was originally " +"used by impl_qpid. Version 2 includes some backwards-incompatible changes " +"that allow broker federation to work. Users should update to version 2 when " +"they are able to take everything down, as it requires a clean break." +msgstr "" + +#: ./doc/common/tables/glance-qpid.xml58(td) +#: ./doc/common/tables/cinder-rpc.xml122(td) +#: ./doc/common/tables/neutron-qpid.xml55(td) +#: ./doc/common/tables/nova-qpid.xml58(td) +msgid "qpid_username =" +msgstr "" + +#: ./doc/common/tables/glance-qpid.xml59(td) +msgid "(StrOpt) Username for Qpid connection" +msgstr "" + +#: ./doc/common/tables/swift-container-server-DEFAULT.xml7(literal) +#: ./doc/common/tables/swift-container-server-container-updater.xml7(literal) +#: ./doc/common/tables/swift-container-server-container-replicator.xml7(literal) +#: ./doc/common/tables/swift-container-server-container-sync.xml7(literal) +#: ./doc/common/tables/swift-container-server-pipeline-main.xml7(literal) +#: ./doc/common/tables/swift-container-server-app-container-server.xml7(literal) +#: ./doc/common/tables/swift-container-server-filter-healthcheck.xml7(literal) +#: ./doc/common/tables/swift-container-server-container-auditor.xml7(literal) +#: ./doc/common/tables/swift-container-server-filter-recon.xml7(literal) +msgid "container-server.conf-sample" +msgstr "" + +#: ./doc/common/tables/swift-container-server-DEFAULT.xml18(td) +#: ./doc/common/tables/swift-object-server-DEFAULT.xml18(td) +#: ./doc/common/tables/swift-account-server-DEFAULT.xml18(td) +#: ./doc/common/tables/swift-proxy-server-DEFAULT.xml18(td) +msgid "bind_ip = 0.0.0.0" +msgstr "" + +#: ./doc/common/tables/swift-container-server-DEFAULT.xml18(td) +#: ./doc/common/tables/swift-object-server-DEFAULT.xml18(td) +#: ./doc/common/tables/swift-account-server-DEFAULT.xml18(td) +#: ./doc/common/tables/swift-proxy-server-DEFAULT.xml18(td) +msgid "IP Address for server to bind to" +msgstr "" + +#: ./doc/common/tables/swift-container-server-DEFAULT.xml21(td) +msgid "bind_port = 6001" +msgstr "" + +#: ./doc/common/tables/swift-container-server-DEFAULT.xml21(td) +#: ./doc/common/tables/swift-object-server-DEFAULT.xml21(td) +#: ./doc/common/tables/swift-account-server-DEFAULT.xml21(td) +#: ./doc/common/tables/swift-proxy-server-DEFAULT.xml21(td) +msgid "Port for server to bind to" +msgstr "" + +#: ./doc/common/tables/swift-container-server-DEFAULT.xml24(td) +#: ./doc/common/tables/swift-object-server-DEFAULT.xml24(td) +#: ./doc/common/tables/swift-account-server-DEFAULT.xml24(td) +#: ./doc/common/tables/swift-proxy-server-DEFAULT.xml24(td) +msgid "bind_timeout = 30" +msgstr "" + +#: ./doc/common/tables/swift-container-server-DEFAULT.xml24(td) +#: ./doc/common/tables/swift-object-server-DEFAULT.xml24(td) +#: ./doc/common/tables/swift-account-server-DEFAULT.xml24(td) +#: ./doc/common/tables/swift-proxy-server-DEFAULT.xml24(td) +msgid "Seconds to attempt bind before giving up" +msgstr "" + +#: ./doc/common/tables/swift-container-server-DEFAULT.xml27(td) +#: ./doc/common/tables/neutron-wsgi.xml19(td) +#: ./doc/common/tables/swift-object-server-DEFAULT.xml27(td) +#: ./doc/common/tables/swift-account-server-DEFAULT.xml27(td) +#: ./doc/common/tables/glance-common.xml30(td) +#: ./doc/common/tables/cinder-log.xml22(td) +#: ./doc/common/tables/swift-proxy-server-DEFAULT.xml27(td) +msgid "backlog = 4096" +msgstr "" + +#: ./doc/common/tables/swift-container-server-DEFAULT.xml27(td) +#: ./doc/common/tables/swift-object-server-DEFAULT.xml27(td) +#: ./doc/common/tables/swift-account-server-DEFAULT.xml27(td) +#: ./doc/common/tables/swift-proxy-server-DEFAULT.xml27(td) +msgid "Maximum number of allowed pending TCP connections" +msgstr "" + +#: ./doc/common/tables/swift-container-server-DEFAULT.xml30(td) +#: ./doc/common/tables/swift-object-expirer-DEFAULT.xml21(td) +#: ./doc/common/tables/swift-object-server-DEFAULT.xml30(td) +#: ./doc/common/tables/swift-account-server-DEFAULT.xml30(td) +#: ./doc/common/tables/swift-proxy-server-DEFAULT.xml33(td) +msgid "user = swift" +msgstr "" + +#: ./doc/common/tables/swift-container-server-DEFAULT.xml30(td) +#: ./doc/common/tables/swift-object-expirer-DEFAULT.xml21(td) +#: ./doc/common/tables/swift-swift-bench-bench.xml21(td) +#: ./doc/common/tables/swift-object-server-DEFAULT.xml30(td) +#: ./doc/common/tables/swift-account-server-DEFAULT.xml30(td) +#: ./doc/common/tables/swift-proxy-server-DEFAULT.xml33(td) +msgid "User to run as" +msgstr "" + +#: ./doc/common/tables/swift-container-server-DEFAULT.xml33(td) +#: ./doc/common/tables/swift-object-expirer-DEFAULT.xml18(td) +#: ./doc/common/tables/swift-object-server-DEFAULT.xml33(td) +#: ./doc/common/tables/swift-account-server-DEFAULT.xml33(td) +#: ./doc/common/tables/swift-dispersion-dispersion.xml45(td) +#: ./doc/common/tables/swift-proxy-server-DEFAULT.xml30(td) +msgid "swift_dir = /etc/swift" +msgstr "" + +#: ./doc/common/tables/swift-container-server-DEFAULT.xml33(td) +#: ./doc/common/tables/swift-object-expirer-DEFAULT.xml18(td) +#: ./doc/common/tables/swift-object-server-DEFAULT.xml33(td) +#: ./doc/common/tables/swift-account-server-DEFAULT.xml33(td) +#: ./doc/common/tables/swift-dispersion-dispersion.xml45(td) +#: ./doc/common/tables/swift-proxy-server-DEFAULT.xml30(td) +msgid "Swift configuration directory" +msgstr "" + +#: ./doc/common/tables/swift-container-server-DEFAULT.xml36(td) +#: ./doc/common/tables/swift-object-server-DEFAULT.xml36(td) +#: ./doc/common/tables/swift-account-server-DEFAULT.xml36(td) +msgid "devices = /srv/node" +msgstr "" + +#: ./doc/common/tables/swift-container-server-DEFAULT.xml36(td) +#: ./doc/common/tables/swift-swift-bench-bench.xml90(td) +#: ./doc/common/tables/swift-object-server-DEFAULT.xml36(td) +#: ./doc/common/tables/swift-account-server-DEFAULT.xml36(td) +msgid "Parent directory of where devices are mounted" +msgstr "" + +#: ./doc/common/tables/swift-container-server-DEFAULT.xml39(td) +#: ./doc/common/tables/swift-object-server-DEFAULT.xml39(td) +#: ./doc/common/tables/swift-account-server-DEFAULT.xml39(td) +msgid "mount_check = true" +msgstr "" + +#: ./doc/common/tables/swift-container-server-DEFAULT.xml39(td) +#: ./doc/common/tables/swift-object-server-DEFAULT.xml39(td) +#: ./doc/common/tables/swift-account-server-DEFAULT.xml39(td) +msgid "" +"Whether or not check if the devices are mounted to prevent accidentally " +"writing to the root device" +msgstr "" + +#: ./doc/common/tables/swift-container-server-DEFAULT.xml42(td) +#: ./doc/common/tables/swift-object-server-DEFAULT.xml42(td) +#: ./doc/common/tables/swift-account-server-DEFAULT.xml42(td) +msgid "disable_fallocate = false" +msgstr "" + +#: ./doc/common/tables/swift-container-server-DEFAULT.xml42(td) +#: ./doc/common/tables/swift-object-server-DEFAULT.xml42(td) +#: ./doc/common/tables/swift-account-server-DEFAULT.xml42(td) +msgid "" +"Disable \"fast fail\" fallocate checks if the underlying filesystem does not" +" support it." +msgstr "" + +#: ./doc/common/tables/swift-container-server-DEFAULT.xml45(td) +#: ./doc/common/tables/swift-object-server-DEFAULT.xml48(td) +#: ./doc/common/tables/swift-account-server-DEFAULT.xml45(td) +#: ./doc/common/tables/swift-proxy-server-DEFAULT.xml36(td) +msgid "workers = auto" +msgstr "" + +#: ./doc/common/tables/swift-container-server-DEFAULT.xml45(td) +#: ./doc/common/tables/swift-object-server-DEFAULT.xml48(td) +#: ./doc/common/tables/swift-account-server-DEFAULT.xml45(td) +#: ./doc/common/tables/swift-proxy-server-DEFAULT.xml36(td) +msgid "" +"a much higher value, one can reduce the impact of slow file system " +"operations in one request from negatively impacting other requests." +msgstr "" + +#: ./doc/common/tables/swift-container-server-DEFAULT.xml48(td) +#: ./doc/common/tables/swift-object-server-DEFAULT.xml51(td) +#: ./doc/common/tables/swift-account-server-DEFAULT.xml48(td) +#: ./doc/common/tables/swift-proxy-server-DEFAULT.xml39(td) +msgid "max_clients = 1024" +msgstr "" + +#: ./doc/common/tables/swift-container-server-DEFAULT.xml48(td) +#: ./doc/common/tables/swift-object-server-DEFAULT.xml51(td) +#: ./doc/common/tables/swift-account-server-DEFAULT.xml48(td) +#: ./doc/common/tables/swift-proxy-server-DEFAULT.xml39(td) +msgid "" +"Maximum number of clients one worker can process simultaneously Lowering the" +" number of clients handled per worker, and raising the number of workers can" +" lessen the impact that a CPU intensive, or blocking, request can have on " +"other requests served by the same worker. If the maximum number of clients " +"is set to one, then a given worker will not perform another call while " +"processing, allowing other workers a chance to process it." +msgstr "" + +#: ./doc/common/tables/swift-container-server-DEFAULT.xml58(td) +msgid "allowed_sync_hosts = 127.0.0.1" +msgstr "" + +#: ./doc/common/tables/swift-container-server-DEFAULT.xml61(td) +#: ./doc/common/tables/swift-object-expirer-DEFAULT.xml24(td) +#: ./doc/common/tables/swift-object-server-DEFAULT.xml61(td) +#: ./doc/common/tables/swift-account-server-DEFAULT.xml58(td) +#: ./doc/common/tables/swift-proxy-server-DEFAULT.xml58(td) +msgid "log_name = swift" +msgstr "" + +#: ./doc/common/tables/swift-container-server-DEFAULT.xml61(td) +#: ./doc/common/tables/swift-container-server-container-updater.xml18(td) +#: ./doc/common/tables/swift-container-server-container-replicator.xml18(td) +#: ./doc/common/tables/swift-container-server-container-sync.xml18(td) +#: ./doc/common/tables/swift-object-server-object-auditor.xml18(td) +#: ./doc/common/tables/swift-object-expirer-DEFAULT.xml24(td) +#: ./doc/common/tables/swift-object-server-object-updater.xml18(td) +#: ./doc/common/tables/swift-account-server-account-auditor.xml18(td) +#: ./doc/common/tables/swift-object-server-DEFAULT.xml61(td) +#: ./doc/common/tables/swift-account-server-DEFAULT.xml58(td) +#: ./doc/common/tables/swift-container-server-container-auditor.xml18(td) +#: ./doc/common/tables/swift-object-server-object-replicator.xml18(td) +#: ./doc/common/tables/swift-account-server-account-replicator.xml18(td) +#: ./doc/common/tables/swift-proxy-server-DEFAULT.xml58(td) +#: ./doc/common/tables/swift-account-server-account-reaper.xml18(td) +msgid "Label used when logging" +msgstr "" + +#: ./doc/common/tables/swift-container-server-DEFAULT.xml64(td) +#: ./doc/common/tables/swift-container-server-container-updater.xml21(td) +#: ./doc/common/tables/swift-container-server-container-replicator.xml21(td) +#: ./doc/common/tables/swift-container-server-container-sync.xml21(td) +#: ./doc/common/tables/swift-object-server-object-auditor.xml21(td) +#: ./doc/common/tables/swift-object-expirer-DEFAULT.xml27(td) +#: ./doc/common/tables/swift-object-server-object-updater.xml21(td) +#: ./doc/common/tables/swift-account-server-account-auditor.xml21(td) +#: ./doc/common/tables/swift-account-server-account-auditor.xml33(td) +#: ./doc/common/tables/swift-object-server-DEFAULT.xml64(td) +#: ./doc/common/tables/swift-account-server-DEFAULT.xml61(td) +#: ./doc/common/tables/swift-container-server-container-auditor.xml21(td) +#: ./doc/common/tables/swift-object-server-object-replicator.xml21(td) +#: ./doc/common/tables/swift-account-server-account-replicator.xml21(td) +#: ./doc/common/tables/swift-proxy-server-DEFAULT.xml61(td) +#: ./doc/common/tables/swift-drive-audit-drive-audit.xml21(td) +#: ./doc/common/tables/swift-account-server-account-reaper.xml21(td) +msgid "log_facility = LOG_LOCAL0" +msgstr "" + +#: ./doc/common/tables/swift-container-server-DEFAULT.xml67(td) +#: ./doc/common/tables/swift-container-server-container-updater.xml24(td) +#: ./doc/common/tables/swift-container-server-container-replicator.xml24(td) +#: ./doc/common/tables/swift-container-server-container-sync.xml24(td) +#: ./doc/common/tables/swift-object-server-object-auditor.xml24(td) +#: ./doc/common/tables/swift-object-expirer-DEFAULT.xml30(td) +#: ./doc/common/tables/swift-object-server-object-updater.xml24(td) +#: ./doc/common/tables/swift-account-server-account-auditor.xml24(td) +#: ./doc/common/tables/swift-account-server-account-auditor.xml36(td) +#: ./doc/common/tables/swift-object-server-DEFAULT.xml67(td) +#: ./doc/common/tables/swift-account-server-DEFAULT.xml64(td) +#: ./doc/common/tables/swift-container-server-container-auditor.xml24(td) +#: ./doc/common/tables/swift-object-server-object-replicator.xml24(td) +#: ./doc/common/tables/swift-account-server-account-replicator.xml24(td) +#: ./doc/common/tables/swift-proxy-server-DEFAULT.xml64(td) +#: ./doc/common/tables/swift-drive-audit-drive-audit.xml24(td) +#: ./doc/common/tables/swift-account-server-account-reaper.xml24(td) +msgid "log_level = INFO" +msgstr "" + +#: ./doc/common/tables/swift-container-server-DEFAULT.xml67(td) +#: ./doc/common/tables/swift-container-server-container-updater.xml24(td) +#: ./doc/common/tables/swift-container-server-container-replicator.xml24(td) +#: ./doc/common/tables/swift-container-server-container-sync.xml24(td) +#: ./doc/common/tables/swift-object-server-object-auditor.xml24(td) +#: ./doc/common/tables/swift-object-expirer-DEFAULT.xml30(td) +#: ./doc/common/tables/swift-object-server-object-updater.xml24(td) +#: ./doc/common/tables/swift-account-server-account-auditor.xml24(td) +#: ./doc/common/tables/swift-account-server-account-auditor.xml36(td) +#: ./doc/common/tables/swift-object-server-DEFAULT.xml67(td) +#: ./doc/common/tables/swift-account-server-DEFAULT.xml64(td) +#: ./doc/common/tables/swift-container-server-container-auditor.xml24(td) +#: ./doc/common/tables/swift-object-server-object-replicator.xml24(td) +#: ./doc/common/tables/swift-account-server-account-replicator.xml24(td) +#: ./doc/common/tables/swift-proxy-server-DEFAULT.xml64(td) +#: ./doc/common/tables/swift-drive-audit-drive-audit.xml24(td) +#: ./doc/common/tables/swift-account-server-account-reaper.xml24(td) +msgid "Logging level" +msgstr "" + +#: ./doc/common/tables/swift-container-server-DEFAULT.xml70(td) +#: ./doc/common/tables/swift-container-server-container-updater.xml27(td) +#: ./doc/common/tables/swift-container-server-container-replicator.xml27(td) +#: ./doc/common/tables/swift-container-server-container-sync.xml27(td) +#: ./doc/common/tables/swift-object-server-object-auditor.xml27(td) +#: ./doc/common/tables/swift-object-expirer-DEFAULT.xml33(td) +#: ./doc/common/tables/swift-object-server-object-updater.xml27(td) +#: ./doc/common/tables/swift-account-server-account-auditor.xml27(td) +#: ./doc/common/tables/swift-object-server-DEFAULT.xml70(td) +#: ./doc/common/tables/swift-account-server-DEFAULT.xml67(td) +#: ./doc/common/tables/swift-container-server-container-auditor.xml27(td) +#: ./doc/common/tables/swift-object-server-object-replicator.xml27(td) +#: ./doc/common/tables/swift-account-server-account-replicator.xml27(td) +#: ./doc/common/tables/swift-proxy-server-DEFAULT.xml70(td) +#: ./doc/common/tables/swift-drive-audit-drive-audit.xml27(td) +#: ./doc/common/tables/swift-account-server-account-reaper.xml27(td) +msgid "log_address = /dev/log" +msgstr "" + +#: ./doc/common/tables/swift-container-server-DEFAULT.xml70(td) +#: ./doc/common/tables/swift-container-server-container-updater.xml27(td) +#: ./doc/common/tables/swift-container-server-container-replicator.xml27(td) +#: ./doc/common/tables/swift-container-server-container-sync.xml27(td) +#: ./doc/common/tables/swift-object-server-object-auditor.xml27(td) +#: ./doc/common/tables/swift-object-expirer-DEFAULT.xml33(td) +#: ./doc/common/tables/swift-object-server-object-updater.xml27(td) +#: ./doc/common/tables/swift-account-server-account-auditor.xml27(td) +#: ./doc/common/tables/swift-object-server-DEFAULT.xml70(td) +#: ./doc/common/tables/swift-account-server-DEFAULT.xml67(td) +#: ./doc/common/tables/swift-container-server-container-auditor.xml27(td) +#: ./doc/common/tables/swift-object-server-object-replicator.xml27(td) +#: ./doc/common/tables/swift-account-server-account-replicator.xml27(td) +#: ./doc/common/tables/swift-proxy-server-DEFAULT.xml70(td) +#: ./doc/common/tables/swift-drive-audit-drive-audit.xml27(td) +#: ./doc/common/tables/swift-account-server-account-reaper.xml27(td) +msgid "Location where syslog sends the logs to" +msgstr "" + +#: ./doc/common/tables/swift-container-server-DEFAULT.xml73(td) +#: ./doc/common/tables/swift-object-expirer-DEFAULT.xml36(td) +#: ./doc/common/tables/swift-object-server-DEFAULT.xml73(td) +#: ./doc/common/tables/swift-account-server-DEFAULT.xml70(td) +#: ./doc/common/tables/swift-proxy-server-DEFAULT.xml76(td) +msgid "log_custom_handlers =" +msgstr "" + +#: ./doc/common/tables/swift-container-server-DEFAULT.xml73(td) +#: ./doc/common/tables/swift-object-expirer-DEFAULT.xml36(td) +#: ./doc/common/tables/swift-object-server-DEFAULT.xml73(td) +#: ./doc/common/tables/swift-account-server-DEFAULT.xml70(td) +#: ./doc/common/tables/swift-proxy-server-DEFAULT.xml76(td) +msgid "" +"Comma-separated list of functions to call to setup custom log handlers." +msgstr "" + +#: ./doc/common/tables/swift-container-server-DEFAULT.xml76(td) +#: ./doc/common/tables/swift-object-expirer-DEFAULT.xml39(td) +#: ./doc/common/tables/swift-object-server-DEFAULT.xml76(td) +#: ./doc/common/tables/swift-account-server-DEFAULT.xml73(td) +#: ./doc/common/tables/swift-proxy-server-DEFAULT.xml79(td) +msgid "log_udp_host =" +msgstr "" + +#: ./doc/common/tables/swift-container-server-DEFAULT.xml76(td) +#: ./doc/common/tables/swift-object-expirer-DEFAULT.xml39(td) +#: ./doc/common/tables/swift-object-server-DEFAULT.xml76(td) +#: ./doc/common/tables/swift-account-server-DEFAULT.xml73(td) +#: ./doc/common/tables/swift-proxy-server-DEFAULT.xml79(td) +msgid "If not set, the UDB receiver for syslog is disabled." +msgstr "" + +#: ./doc/common/tables/swift-container-server-DEFAULT.xml79(td) +#: ./doc/common/tables/swift-object-expirer-DEFAULT.xml42(td) +#: ./doc/common/tables/swift-object-server-DEFAULT.xml79(td) +#: ./doc/common/tables/swift-account-server-DEFAULT.xml76(td) +#: ./doc/common/tables/swift-proxy-server-DEFAULT.xml82(td) +msgid "log_udp_port = 514" +msgstr "" + +#: ./doc/common/tables/swift-container-server-DEFAULT.xml79(td) +#: ./doc/common/tables/swift-object-expirer-DEFAULT.xml42(td) +#: ./doc/common/tables/swift-object-server-DEFAULT.xml79(td) +#: ./doc/common/tables/swift-account-server-DEFAULT.xml76(td) +#: ./doc/common/tables/swift-proxy-server-DEFAULT.xml82(td) +msgid "Port value for UDB receiver, if enabled." +msgstr "" + +#: ./doc/common/tables/swift-container-server-DEFAULT.xml82(td) +#: ./doc/common/tables/swift-object-expirer-DEFAULT.xml45(td) +#: ./doc/common/tables/swift-object-server-DEFAULT.xml82(td) +#: ./doc/common/tables/swift-account-server-DEFAULT.xml79(td) +#: ./doc/common/tables/swift-proxy-server-DEFAULT.xml85(td) +msgid "log_statsd_host = localhost" +msgstr "" + +#: ./doc/common/tables/swift-container-server-DEFAULT.xml82(td) +#: ./doc/common/tables/swift-object-expirer-DEFAULT.xml45(td) +#: ./doc/common/tables/swift-object-server-DEFAULT.xml82(td) +#: ./doc/common/tables/swift-account-server-DEFAULT.xml79(td) +#: ./doc/common/tables/swift-proxy-server-DEFAULT.xml85(td) +msgid "If not set, the StatsD feature is disabled." +msgstr "" + +#: ./doc/common/tables/swift-container-server-DEFAULT.xml85(td) +#: ./doc/common/tables/swift-object-expirer-DEFAULT.xml48(td) +#: ./doc/common/tables/swift-object-server-DEFAULT.xml85(td) +#: ./doc/common/tables/swift-account-server-DEFAULT.xml82(td) +#: ./doc/common/tables/swift-proxy-server-DEFAULT.xml88(td) +msgid "log_statsd_port = 8125" +msgstr "" + +#: ./doc/common/tables/swift-container-server-DEFAULT.xml85(td) +#: ./doc/common/tables/swift-object-expirer-DEFAULT.xml48(td) +#: ./doc/common/tables/swift-object-server-DEFAULT.xml85(td) +#: ./doc/common/tables/swift-account-server-DEFAULT.xml82(td) +#: ./doc/common/tables/swift-proxy-server-DEFAULT.xml88(td) +msgid "Port value for the StatsD server." +msgstr "" + +#: ./doc/common/tables/swift-container-server-DEFAULT.xml88(td) +#: ./doc/common/tables/swift-object-expirer-DEFAULT.xml51(td) +#: ./doc/common/tables/swift-object-server-DEFAULT.xml88(td) +#: ./doc/common/tables/swift-account-server-DEFAULT.xml85(td) +#: ./doc/common/tables/swift-proxy-server-DEFAULT.xml91(td) +msgid "log_statsd_default_sample_rate = 1.0" +msgstr "" + +#: ./doc/common/tables/swift-container-server-DEFAULT.xml88(td) +#: ./doc/common/tables/swift-object-expirer-DEFAULT.xml51(td) +#: ./doc/common/tables/swift-object-server-DEFAULT.xml88(td) +#: ./doc/common/tables/swift-account-server-DEFAULT.xml85(td) +#: ./doc/common/tables/swift-proxy-server-DEFAULT.xml91(td) +msgid "" +"Defines the probability of sending a sample for any given event or timing " +"measurement." +msgstr "" + +#: ./doc/common/tables/swift-container-server-DEFAULT.xml92(td) +#: ./doc/common/tables/swift-object-expirer-DEFAULT.xml55(td) +#: ./doc/common/tables/swift-object-server-DEFAULT.xml92(td) +#: ./doc/common/tables/swift-account-server-DEFAULT.xml89(td) +#: ./doc/common/tables/swift-proxy-server-DEFAULT.xml95(td) +msgid "log_statsd_sample_rate_factor = 1.0" +msgstr "" + +#: ./doc/common/tables/swift-container-server-DEFAULT.xml92(td) +#: ./doc/common/tables/swift-object-expirer-DEFAULT.xml55(td) +#: ./doc/common/tables/swift-object-server-DEFAULT.xml92(td) +#: ./doc/common/tables/swift-account-server-DEFAULT.xml89(td) +#: ./doc/common/tables/swift-proxy-server-DEFAULT.xml95(td) +msgid "" +"Not recommended to set this to a value less than 1.0, if frequency of " +"logging is too high, tune the log_statsd_default_sample_rate instead." +msgstr "" + +#: ./doc/common/tables/swift-container-server-DEFAULT.xml97(td) +#: ./doc/common/tables/swift-object-expirer-DEFAULT.xml60(td) +#: ./doc/common/tables/swift-object-server-DEFAULT.xml97(td) +#: ./doc/common/tables/swift-account-server-DEFAULT.xml94(td) +#: ./doc/common/tables/swift-proxy-server-DEFAULT.xml100(td) +msgid "log_statsd_metric_prefix =" +msgstr "" + +#: ./doc/common/tables/swift-container-server-DEFAULT.xml97(td) +#: ./doc/common/tables/swift-object-expirer-DEFAULT.xml60(td) +#: ./doc/common/tables/swift-object-server-DEFAULT.xml97(td) +#: ./doc/common/tables/swift-account-server-DEFAULT.xml94(td) +#: ./doc/common/tables/swift-proxy-server-DEFAULT.xml100(td) +msgid "Value will be prepended to every metric sent to the StatsD server." +msgstr "" + +#: ./doc/common/tables/swift-container-server-DEFAULT.xml100(td) +#: ./doc/common/tables/swift-account-server-DEFAULT.xml97(td) +msgid "db_preallocation = off" +msgstr "" + +#: ./doc/common/tables/swift-container-server-DEFAULT.xml100(td) +#: ./doc/common/tables/swift-account-server-DEFAULT.xml97(td) +msgid "" +"If you don't mind the extra disk space usage in overhead, you can turn this " +"on to preallocate disk space with SQLite databases to decrease " +"fragmentation. underlying filesystem does not support it. to setup custom " +"log handlers. bytes you'd like fallocate to reserve, whether there is space " +"for the given file size or not. This is useful for systems that behave badly" +" when they completely run out of space; you can make the services pretend " +"they're out of space early. server. For most cases, this should be " +"`egg:swift#account`. replication passes account can be reclaimed" +msgstr "" + +#: ./doc/common/tables/swift-container-server-DEFAULT.xml103(td) +#: ./doc/common/tables/swift-object-server-DEFAULT.xml100(td) +#: ./doc/common/tables/swift-account-server-DEFAULT.xml100(td) +#: ./doc/common/tables/swift-proxy-server-DEFAULT.xml109(td) +msgid "eventlet_debug = false" +msgstr "" + +#: ./doc/common/tables/swift-container-server-DEFAULT.xml103(td) +#: ./doc/common/tables/swift-object-server-DEFAULT.xml100(td) +#: ./doc/common/tables/swift-account-server-DEFAULT.xml100(td) +#: ./doc/common/tables/swift-proxy-server-DEFAULT.xml109(td) +msgid "If true, turn on debug logging for eventlet" +msgstr "" + +#: ./doc/common/tables/swift-container-server-DEFAULT.xml106(td) +#: ./doc/common/tables/swift-object-server-DEFAULT.xml103(td) +#: ./doc/common/tables/swift-account-server-DEFAULT.xml103(td) +msgid "fallocate_reserve = 0" +msgstr "" + +#: ./doc/common/tables/swift-container-server-DEFAULT.xml106(td) +#: ./doc/common/tables/swift-object-server-DEFAULT.xml103(td) +#: ./doc/common/tables/swift-account-server-DEFAULT.xml103(td) +msgid "" +"You can set fallocate_reserve to the number of bytes you'd like fallocate to" +" reserve, whether there is space for the given file size or not. This is " +"useful for systems that behave badly when they completely run out of space; " +"you can make the services pretend they're out of space early. server. For " +"most cases, this should be `egg:swift#object`." +msgstr "" + +#: ./doc/common/tables/nova-volumes.xml8(caption) +msgid "Description of configuration options for volumes" +msgstr "" + +#: ./doc/common/tables/nova-volumes.xml22(td) +#: ./doc/common/tables/glance-cinder.xml22(td) +msgid "cinder_api_insecure = False" +msgstr "" + +#: ./doc/common/tables/nova-volumes.xml23(td) +#: ./doc/common/tables/glance-cinder.xml23(td) +msgid "(BoolOpt) Allow to perform insecure SSL requests to cinder" +msgstr "" + +#: ./doc/common/tables/nova-volumes.xml26(td) +#: ./doc/common/tables/glance-cinder.xml26(td) +msgid "cinder_ca_certificates_file = None" +msgstr "" + +#: ./doc/common/tables/nova-volumes.xml27(td) +msgid "" +"(StrOpt) Location of ca certificates file to use for cinder client requests." +msgstr "" + +#: ./doc/common/tables/nova-volumes.xml30(td) +#: ./doc/common/tables/glance-cinder.xml30(td) +msgid "cinder_catalog_info = volume:cinder:publicURL" +msgstr "" + +#: ./doc/common/tables/nova-volumes.xml31(td) +#: ./doc/common/tables/glance-cinder.xml31(td) +msgid "" +"(StrOpt) Info to match when looking for cinder in the service catalog. " +"Format is : separated values of the form: " +"<service_type>:<service_name>:<endpoint_type>" +msgstr "" + +#: ./doc/common/tables/nova-volumes.xml34(td) +msgid "cinder_cross_az_attach = True" +msgstr "" + +#: ./doc/common/tables/nova-volumes.xml35(td) +msgid "" +"(BoolOpt) Allow attach between instance and volume in different availability" +" zones." +msgstr "" + +#: ./doc/common/tables/nova-volumes.xml38(td) +#: ./doc/common/tables/glance-cinder.xml34(td) +msgid "cinder_endpoint_template = None" +msgstr "" + +#: ./doc/common/tables/nova-volumes.xml39(td) +#: ./doc/common/tables/glance-cinder.xml35(td) +msgid "" +"(StrOpt) Override service catalog lookup with template for cinder endpoint " +"e.g. http://localhost:8776/v1/%(project_id)s" +msgstr "" + +#: ./doc/common/tables/nova-volumes.xml42(td) +#: ./doc/common/tables/glance-cinder.xml38(td) +msgid "cinder_http_retries = 3" +msgstr "" + +#: ./doc/common/tables/nova-volumes.xml43(td) +#: ./doc/common/tables/glance-cinder.xml39(td) +msgid "(IntOpt) Number of cinderclient retries on failed http calls" +msgstr "" + +#: ./doc/common/tables/nova-volumes.xml46(td) +#: ./doc/common/tables/cinder-compute.xml46(td) +#: ./doc/common/tables/glance-common.xml82(td) +msgid "os_region_name = None" +msgstr "" + +#: ./doc/common/tables/nova-volumes.xml47(td) +#: ./doc/common/tables/cinder-compute.xml47(td) +msgid "(StrOpt) region name of this node" +msgstr "" + +#: ./doc/common/tables/nova-volumes.xml50(td) +msgid "volume_api_class = nova.volume.cinder.API" +msgstr "" + +#: ./doc/common/tables/nova-volumes.xml51(td) +#: ./doc/common/tables/cinder-api.xml75(td) +msgid "(StrOpt) The full class name of the volume API class to use" +msgstr "" + +#: ./doc/common/tables/nova-volumes.xml54(td) +msgid "volume_usage_poll_interval = 0" +msgstr "" + +#: ./doc/common/tables/nova-volumes.xml55(td) +msgid "(IntOpt) Interval in seconds for gathering volume usages" +msgstr "" + +#: ./doc/common/tables/nova-volumes.xml58(th) +#: ./doc/common/tables/nova-tilera.xml19(th) +#: ./doc/common/tables/nova-baremetal.xml19(th) +msgid "[baremetal]" +msgstr "" + +#: ./doc/common/tables/nova-volumes.xml61(td) +msgid "iscsi_iqn_prefix = iqn.2010-10.org.openstack.baremetal" +msgstr "" + +#: ./doc/common/tables/nova-volumes.xml62(td) +msgid "(StrOpt) iSCSI IQN prefix used in baremetal volume connections." +msgstr "" + +#: ./doc/common/tables/nova-volumes.xml65(td) +msgid "volume_driver = nova.virt.baremetal.volume_driver.LibvirtVolumeDriver" +msgstr "" + +#: ./doc/common/tables/nova-volumes.xml66(td) +msgid "(StrOpt) Baremetal volume driver." +msgstr "" + +#: ./doc/common/tables/nova-volumes.xml69(th) +#: ./doc/common/tables/nova-hyperv.xml19(th) +#: ./doc/common/tables/nova-configdrive.xml42(th) +msgid "[hyperv]" +msgstr "" + +#: ./doc/common/tables/nova-volumes.xml72(td) +msgid "force_volumeutils_v1 = False" +msgstr "" + +#: ./doc/common/tables/nova-volumes.xml73(td) +msgid "(BoolOpt) Force V1 volume utility class" +msgstr "" + +#: ./doc/common/tables/nova-volumes.xml76(td) +msgid "volume_attach_retry_count = 10" +msgstr "" + +#: ./doc/common/tables/nova-volumes.xml77(td) +msgid "(IntOpt) The number of times to retry to attach a volume" +msgstr "" + +#: ./doc/common/tables/nova-volumes.xml80(td) +msgid "volume_attach_retry_interval = 5" +msgstr "" + +#: ./doc/common/tables/nova-volumes.xml81(td) +msgid "(IntOpt) Interval between volume attachment attempts, in seconds" +msgstr "" + +#: ./doc/common/tables/nova-volumes.xml84(th) +#: ./doc/common/tables/nova-hypervisor.xml54(th) +#: ./doc/common/tables/nova-livemigration.xml26(th) +#: ./doc/common/tables/nova-libvirt.xml30(th) +#: ./doc/common/tables/nova-xen.xml58(th) +msgid "[libvirt]" +msgstr "" + +#: ./doc/common/tables/nova-volumes.xml87(td) +#: ./doc/common/tables/cinder-storage_glusterfs.xml22(td) +msgid "glusterfs_mount_point_base = $state_path/mnt" +msgstr "" + +#: ./doc/common/tables/nova-volumes.xml88(td) +msgid "(StrOpt) Dir where the glusterfs volume is mounted on the compute node" +msgstr "" + +#: ./doc/common/tables/nova-volumes.xml91(td) +#: ./doc/common/tables/cinder-storage_nfs.xml22(td) +msgid "nfs_mount_options = None" +msgstr "" + +#: ./doc/common/tables/nova-volumes.xml92(td) +#: ./doc/common/tables/cinder-nexenta_nfs.xml23(td) +msgid "" +"(StrOpt) Mount options passed to the nfs client. See section of the nfs man " +"page for details" +msgstr "" + +#: ./doc/common/tables/nova-volumes.xml95(td) +#: ./doc/common/tables/cinder-storage_nfs.xml26(td) +msgid "nfs_mount_point_base = $state_path/mnt" +msgstr "" + +#: ./doc/common/tables/nova-volumes.xml96(td) +msgid "(StrOpt) Dir where the nfs volume is mounted on the compute node" +msgstr "" + +#: ./doc/common/tables/nova-volumes.xml99(td) +msgid "num_aoe_discover_tries = 3" +msgstr "" + +#: ./doc/common/tables/nova-volumes.xml100(td) +msgid "(IntOpt) number of times to rediscover AoE target to find volume" +msgstr "" + +#: ./doc/common/tables/nova-volumes.xml103(td) +msgid "num_iscsi_scan_tries = 3" +msgstr "" + +#: ./doc/common/tables/nova-volumes.xml104(td) +msgid "(IntOpt) number of times to rescan iSCSI target to find volume" +msgstr "" + +#: ./doc/common/tables/nova-volumes.xml107(td) +#: ./doc/common/tables/cinder-storage.xml90(td) +msgid "num_iser_scan_tries = 3" +msgstr "" + +#: ./doc/common/tables/nova-volumes.xml108(td) +msgid "(IntOpt) number of times to rescan iSER target to find volume" +msgstr "" + +#: ./doc/common/tables/nova-volumes.xml111(td) +msgid "qemu_allowed_storage_drivers =" +msgstr "" + +#: ./doc/common/tables/nova-volumes.xml112(td) +msgid "" +"(ListOpt) Protocols listed here will be accessed directly from QEMU. " +"Currently supported protocols: [gluster]" +msgstr "" + +#: ./doc/common/tables/nova-volumes.xml115(td) +#: ./doc/common/tables/cinder-storage_ceph.xml38(td) +msgid "rbd_secret_uuid = None" +msgstr "" + +#: ./doc/common/tables/nova-volumes.xml116(td) +#: ./doc/common/tables/cinder-storage_ceph.xml39(td) +msgid "(StrOpt) the libvirt uuid of the secret for the rbd_uservolumes" +msgstr "" + +#: ./doc/common/tables/nova-volumes.xml119(td) +#: ./doc/common/tables/cinder-storage_ceph.xml42(td) +msgid "rbd_user = None" +msgstr "" + +#: ./doc/common/tables/nova-volumes.xml120(td) +msgid "(StrOpt) the RADOS client name for accessing rbd volumes" +msgstr "" + +#: ./doc/common/tables/nova-volumes.xml123(td) +#: ./doc/common/tables/cinder-scality.xml22(td) +msgid "scality_sofs_config = None" +msgstr "" + +#: ./doc/common/tables/nova-volumes.xml124(td) +#: ./doc/common/tables/cinder-scality.xml23(td) +msgid "(StrOpt) Path or URL to Scality SOFS configuration file" +msgstr "" + +#: ./doc/common/tables/nova-volumes.xml127(td) +#: ./doc/common/tables/cinder-scality.xml26(td) +msgid "scality_sofs_mount_point = $state_path/scality" +msgstr "" + +#: ./doc/common/tables/nova-volumes.xml128(td) +#: ./doc/common/tables/cinder-scality.xml27(td) +msgid "(StrOpt) Base dir where Scality SOFS shall be mounted" +msgstr "" + +#: ./doc/common/tables/nova-volumes.xml131(th) +#: ./doc/common/tables/nova-xen.xml65(th) +#: ./doc/common/tables/nova-baremetal.xml130(th) +msgid "[xenserver]" +msgstr "" + +#: ./doc/common/tables/nova-volumes.xml134(td) +msgid "block_device_creation_timeout = 10" +msgstr "" + +#: ./doc/common/tables/nova-volumes.xml135(td) +msgid "(IntOpt) Time to wait for a block device to be created" +msgstr "" + +#: ./doc/common/tables/glance-gridfs.xml8(caption) +msgid "Description of configuration options for gridfs" +msgstr "" + +#: ./doc/common/tables/glance-gridfs.xml22(td) +msgid "mongodb_store_db = None" +msgstr "" + +#: ./doc/common/tables/glance-gridfs.xml23(td) +msgid "(StrOpt) Database to use" +msgstr "" + +#: ./doc/common/tables/glance-gridfs.xml26(td) +msgid "mongodb_store_uri = None" +msgstr "" + +#: ./doc/common/tables/glance-gridfs.xml27(td) +msgid "" +"(StrOpt) Hostname or IP address of the instance to connect to, or a mongodb " +"URI, or a list of hostnames / mongodb URIs. If host is an IPv6 literal it " +"must be enclosed in '[' and ']' characters following the RFC2732 URL syntax " +"(e.g. '[::1]' for localhost)" +msgstr "" + +#: ./doc/common/tables/neutron-ml2_arista.xml8(caption) +msgid "Description of configuration options for ml2_arista" +msgstr "" + +#: ./doc/common/tables/neutron-ml2_arista.xml19(td) +msgid "eapi_host =" +msgstr "" + +#: ./doc/common/tables/neutron-ml2_arista.xml20(td) +msgid "" +"(StrOpt) Arista EOS IP address. This is required field.If not set, all " +"communications to Arista EOSwill fail" +msgstr "" + +#: ./doc/common/tables/neutron-ml2_arista.xml23(td) +msgid "eapi_password =" +msgstr "" + +#: ./doc/common/tables/neutron-ml2_arista.xml24(td) +msgid "" +"(StrOpt) Password for Arista EOS. This is required field.if not set, all " +"communications to Arista EOSwill fail" +msgstr "" + +#: ./doc/common/tables/neutron-ml2_arista.xml27(td) +msgid "eapi_username =" +msgstr "" + +#: ./doc/common/tables/neutron-ml2_arista.xml28(td) +msgid "" +"(StrOpt) Username for Arista EOS. This is required field.if not set, all " +"communications to Arista EOSwill fail" +msgstr "" + +#: ./doc/common/tables/neutron-ml2_arista.xml31(td) +msgid "region_name = RegionOne" +msgstr "" + +#: ./doc/common/tables/neutron-ml2_arista.xml32(td) +msgid "" +"(StrOpt) Defines Region Name that is assigned to this OpenStackController. " +"This is useful when multipleOpenStack/Neutron controllers are managing the " +"sameArista HW clusters. Note that this name must match withthe region name " +"registered (or known) to keystoneservice. Authentication with Keysotne is " +"performed byEOS. This is optional. If not set, a value of\"RegionOne\" is " +"assumed" +msgstr "" + +#: ./doc/common/tables/neutron-ml2_arista.xml35(td) +msgid "sync_interval = 180" +msgstr "" + +#: ./doc/common/tables/neutron-ml2_arista.xml36(td) +msgid "" +"(IntOpt) Sync interval in seconds between Neutron plugin andEOS. This " +"interval defines how often thesynchronization is performed. This is an " +"optionalfield. If not set, a value of 180 seconds is assumed" +msgstr "" + +#: ./doc/common/tables/neutron-ml2_arista.xml39(td) +msgid "use_fqdn = True" +msgstr "" + +#: ./doc/common/tables/neutron-ml2_arista.xml40(td) +msgid "" +"(BoolOpt) Defines if hostnames are sent to Arista EOS as " +"FQDNs(\"node1.domain.com\") or as short names (\"node1\").This is optional. " +"If not set, a value of \"True\"is assumed." +msgstr "" + +#: ./doc/common/tables/glance-filesystem.xml8(caption) +msgid "Description of configuration options for filesystem" +msgstr "" + +#: ./doc/common/tables/glance-filesystem.xml22(td) +msgid "filesystem_store_datadir = None" +msgstr "" + +#: ./doc/common/tables/glance-filesystem.xml23(td) +msgid "" +"(StrOpt) Directory to which the Filesystem backend store writes images." +msgstr "" + +#: ./doc/common/tables/glance-filesystem.xml26(td) +msgid "filesystem_store_metadata_file = None" +msgstr "" + +#: ./doc/common/tables/glance-filesystem.xml27(td) +msgid "" +"(StrOpt) The path to a file which contains the metadata to be returned with " +"any location associated with this store. The file must contain a valid JSON " +"dict." +msgstr "" + +#: ./doc/common/tables/swift-container-server-container-updater.xml7(literal) +msgid "[container-updater]" +msgstr "" + +#: ./doc/common/tables/swift-container-server-container-updater.xml18(td) +msgid "log_name = container-updater" +msgstr "" + +#: ./doc/common/tables/swift-container-server-container-updater.xml30(td) +#: ./doc/common/tables/swift-container-server-container-sync.xml33(td) +#: ./doc/common/tables/swift-object-server-object-updater.xml30(td) +#: ./doc/common/tables/swift-object-expirer-object-expirer.xml18(td) +msgid "interval = 300" +msgstr "" + +#: ./doc/common/tables/swift-container-server-container-updater.xml30(td) +#: ./doc/common/tables/swift-container-server-container-replicator.xml42(td) +#: ./doc/common/tables/swift-container-server-container-sync.xml33(td) +#: ./doc/common/tables/swift-object-server-object-updater.xml30(td) +#: ./doc/common/tables/swift-account-server-account-auditor.xml30(td) +#: ./doc/common/tables/swift-container-server-container-auditor.xml30(td) +#: ./doc/common/tables/swift-account-server-account-replicator.xml42(td) +#: ./doc/common/tables/swift-object-expirer-object-expirer.xml18(td) +#: ./doc/common/tables/swift-account-server-account-reaper.xml33(td) +msgid "Minimum time for a pass to take" +msgstr "" + +#: ./doc/common/tables/swift-container-server-container-updater.xml33(td) +msgid "concurrency = 4" +msgstr "" + +#: ./doc/common/tables/swift-container-server-container-updater.xml33(td) +#: ./doc/common/tables/swift-container-server-container-replicator.xml39(td) +#: ./doc/common/tables/swift-swift-bench-bench.xml45(td) +#: ./doc/common/tables/swift-object-server-object-updater.xml33(td) +#: ./doc/common/tables/swift-object-server-object-replicator.xml39(td) +#: ./doc/common/tables/swift-dispersion-dispersion.xml54(td) +#: ./doc/common/tables/swift-account-server-account-replicator.xml39(td) +#: ./doc/common/tables/swift-object-expirer-object-expirer.xml27(td) +#: ./doc/common/tables/swift-account-server-account-reaper.xml30(td) +msgid "Number of replication workers to spawn" +msgstr "" + +#: ./doc/common/tables/swift-container-server-container-updater.xml36(td) +#: ./doc/common/tables/swift-container-server-app-container-server.xml36(td) +#: ./doc/common/tables/swift-object-server-app-object-server.xml36(td) +msgid "node_timeout = 3" +msgstr "" + +#: ./doc/common/tables/swift-container-server-container-updater.xml36(td) +#: ./doc/common/tables/swift-container-server-container-replicator.xml45(td) +#: ./doc/common/tables/swift-object-server-object-updater.xml36(td) +#: ./doc/common/tables/swift-proxy-server-app-proxy-server.xml48(td) +#: ./doc/common/tables/swift-container-server-app-container-server.xml36(td) +#: ./doc/common/tables/swift-account-server-account-replicator.xml51(td) +#: ./doc/common/tables/swift-object-server-app-object-server.xml36(td) +#: ./doc/common/tables/swift-account-server-account-reaper.xml36(td) +msgid "Request timeout to external services" +msgstr "" + +#: ./doc/common/tables/swift-container-server-container-updater.xml39(td) +#: ./doc/common/tables/swift-container-server-container-replicator.xml48(td) +#: ./doc/common/tables/swift-object-server-object-updater.xml39(td) +#: ./doc/common/tables/swift-proxy-server-app-proxy-server.xml51(td) +#: ./doc/common/tables/swift-container-server-app-container-server.xml39(td) +#: ./doc/common/tables/swift-account-server-account-replicator.xml54(td) +#: ./doc/common/tables/swift-object-server-app-object-server.xml39(td) +#: ./doc/common/tables/swift-account-server-account-reaper.xml39(td) +msgid "conn_timeout = 0.5" +msgstr "" + +#: ./doc/common/tables/swift-container-server-container-updater.xml39(td) +#: ./doc/common/tables/swift-container-server-container-replicator.xml48(td) +#: ./doc/common/tables/swift-object-server-object-updater.xml39(td) +#: ./doc/common/tables/swift-proxy-server-app-proxy-server.xml51(td) +#: ./doc/common/tables/swift-container-server-app-container-server.xml39(td) +#: ./doc/common/tables/swift-account-server-account-replicator.xml54(td) +#: ./doc/common/tables/swift-object-server-app-object-server.xml39(td) +#: ./doc/common/tables/swift-account-server-account-reaper.xml39(td) +msgid "Connection timeout to external services" +msgstr "" + +#: ./doc/common/tables/swift-container-server-container-updater.xml42(td) +#: ./doc/common/tables/swift-object-server-object-updater.xml42(td) +msgid "slowdown = 0.01" +msgstr "" + +#: ./doc/common/tables/swift-container-server-container-updater.xml42(td) +#: ./doc/common/tables/swift-object-server-object-updater.xml42(td) +msgid "Time in seconds to wait between objects" +msgstr "" + +#: ./doc/common/tables/swift-container-server-container-updater.xml45(td) +msgid "account_suppression_time = 60" +msgstr "" + +#: ./doc/common/tables/swift-container-server-container-updater.xml45(td) +msgid "" +"Seconds to suppress updating an account that has generated an error " +"(timeout, not yet found, etc.)" +msgstr "" + +#: ./doc/common/tables/swift-container-server-container-updater.xml49(td) +#: ./doc/common/tables/swift-account-server-filter-recon.xml21(td) +#: ./doc/common/tables/swift-container-server-container-replicator.xml57(td) +#: ./doc/common/tables/swift-object-server-object-auditor.xml42(td) +#: ./doc/common/tables/swift-object-server-object-updater.xml45(td) +#: ./doc/common/tables/swift-account-server-account-auditor.xml42(td) +#: ./doc/common/tables/swift-object-server-filter-recon.xml21(td) +#: ./doc/common/tables/swift-container-server-container-auditor.xml36(td) +#: ./doc/common/tables/swift-object-server-object-replicator.xml66(td) +#: ./doc/common/tables/swift-account-server-account-replicator.xml63(td) +#: ./doc/common/tables/swift-container-server-filter-recon.xml21(td) +msgid "recon_cache_path = /var/cache/swift" +msgstr "" + +#: ./doc/common/tables/swift-container-server-container-updater.xml49(td) +#: ./doc/common/tables/swift-account-server-filter-recon.xml21(td) +#: ./doc/common/tables/swift-container-server-container-replicator.xml57(td) +#: ./doc/common/tables/swift-object-server-object-auditor.xml42(td) +#: ./doc/common/tables/swift-object-server-object-updater.xml45(td) +#: ./doc/common/tables/swift-account-server-account-auditor.xml42(td) +#: ./doc/common/tables/swift-object-server-filter-recon.xml21(td) +#: ./doc/common/tables/swift-container-server-container-auditor.xml36(td) +#: ./doc/common/tables/swift-object-server-object-replicator.xml66(td) +#: ./doc/common/tables/swift-account-server-account-replicator.xml63(td) +#: ./doc/common/tables/swift-container-server-filter-recon.xml21(td) +msgid "Directory where stats for a few items will be stored" +msgstr "" + +#: ./doc/common/tables/cinder-storage_gpfs.xml8(caption) +msgid "Description of configuration options for storage_gpfs" +msgstr "" + +#: ./doc/common/tables/cinder-storage_gpfs.xml22(td) +msgid "gpfs_images_dir = None" +msgstr "" + +#: ./doc/common/tables/cinder-storage_gpfs.xml23(td) +msgid "" +"(StrOpt) Specifies the path of the Image service repository in GPFS. Leave " +"undefined if not storing images in GPFS." +msgstr "" + +#: ./doc/common/tables/cinder-storage_gpfs.xml26(td) +msgid "gpfs_images_share_mode = None" +msgstr "" + +#: ./doc/common/tables/cinder-storage_gpfs.xml27(td) +msgid "" +"(StrOpt) Specifies the type of image copy to be used. Set this when the " +"Image service repository also uses GPFS so that image files can be " +"transferred efficiently from the Image service to the Block Storage service." +" There are two valid values: \"copy\" specifies that a full copy of the " +"image is made; \"copy_on_write\" specifies that copy-on-write optimization " +"strategy is used and unmodified blocks of the image file are shared " +"efficiently." +msgstr "" + +#: ./doc/common/tables/cinder-storage_gpfs.xml30(td) +msgid "gpfs_max_clone_depth = 0" +msgstr "" + +#: ./doc/common/tables/cinder-storage_gpfs.xml31(td) +msgid "" +"(IntOpt) Specifies an upper limit on the number of indirections required to " +"reach a specific block due to snapshots or clones. A lengthy chain of copy-" +"on-write snapshots or clones can have a negative impact on performance, but " +"improves space utilization. 0 indicates unlimited clone depth." +msgstr "" + +#: ./doc/common/tables/cinder-storage_gpfs.xml34(td) +msgid "gpfs_mount_point_base = None" +msgstr "" + +#: ./doc/common/tables/cinder-storage_gpfs.xml35(td) +msgid "" +"(StrOpt) Specifies the path of the GPFS directory where Block Storage volume" +" and snapshot files are stored." +msgstr "" + +#: ./doc/common/tables/cinder-storage_gpfs.xml38(td) +msgid "gpfs_sparse_volumes = True" +msgstr "" + +#: ./doc/common/tables/cinder-storage_gpfs.xml39(td) +msgid "" +"(BoolOpt) Specifies that volumes are created as sparse files which initially" +" consume no space. If set to False, the volume is created as a fully " +"allocated file, in which case, creation may take a significantly longer " +"time." +msgstr "" + +#: ./doc/common/tables/nova-docker.xml8(caption) +msgid "Description of configuration options for docker" +msgstr "" + +#: ./doc/common/tables/nova-docker.xml19(th) +msgid "[docker]" +msgstr "" + +#: ./doc/common/tables/nova-docker.xml22(td) +msgid "registry_default_port = 5042" +msgstr "" + +#: ./doc/common/tables/nova-docker.xml23(td) +msgid "(IntOpt) Default TCP port to find the docker-registry container" +msgstr "" + +#: ./doc/common/tables/cinder-nexenta_iscsi.xml8(caption) +msgid "Description of configuration options for nexenta_iscsi" +msgstr "" + +#: ./doc/common/tables/cinder-nexenta_iscsi.xml22(td) +msgid "nexenta_blocksize =" +msgstr "" + +#: ./doc/common/tables/cinder-nexenta_iscsi.xml23(td) +msgid "(StrOpt) block size for volumes (blank=default,8KB)" +msgstr "" + +#: ./doc/common/tables/cinder-nexenta_iscsi.xml26(td) +msgid "nexenta_host =" +msgstr "" + +#: ./doc/common/tables/cinder-nexenta_iscsi.xml27(td) +msgid "(StrOpt) IP address of Nexenta SA" +msgstr "" + +#: ./doc/common/tables/cinder-nexenta_iscsi.xml30(td) +msgid "nexenta_iscsi_target_portal_port = 3260" +msgstr "" + +#: ./doc/common/tables/cinder-nexenta_iscsi.xml31(td) +msgid "(IntOpt) Nexenta target portal port" +msgstr "" + +#: ./doc/common/tables/cinder-nexenta_iscsi.xml34(td) +msgid "nexenta_password = nexenta" +msgstr "" + +#: ./doc/common/tables/cinder-nexenta_iscsi.xml35(td) +msgid "(StrOpt) Password to connect to Nexenta SA" +msgstr "" + +#: ./doc/common/tables/cinder-nexenta_iscsi.xml38(td) +msgid "nexenta_rest_port = 2000" +msgstr "" + +#: ./doc/common/tables/cinder-nexenta_iscsi.xml39(td) +msgid "(IntOpt) HTTP port to connect to Nexenta REST API server" +msgstr "" + +#: ./doc/common/tables/cinder-nexenta_iscsi.xml42(td) +msgid "nexenta_rest_protocol = auto" +msgstr "" + +#: ./doc/common/tables/cinder-nexenta_iscsi.xml43(td) +msgid "(StrOpt) Use http or https for REST connection (default auto)" +msgstr "" + +#: ./doc/common/tables/cinder-nexenta_iscsi.xml46(td) +msgid "nexenta_rrmgr_compression = 0" +msgstr "" + +#: ./doc/common/tables/cinder-nexenta_iscsi.xml47(td) +msgid "" +"(IntOpt) Enable stream compression, level 1..9. 1 - gives best speed; 9 - " +"gives best compression." +msgstr "" + +#: ./doc/common/tables/cinder-nexenta_iscsi.xml50(td) +msgid "nexenta_rrmgr_connections = 2" +msgstr "" + +#: ./doc/common/tables/cinder-nexenta_iscsi.xml51(td) +msgid "(IntOpt) Number of TCP connections." +msgstr "" + +#: ./doc/common/tables/cinder-nexenta_iscsi.xml54(td) +msgid "nexenta_rrmgr_tcp_buf_size = 4096" +msgstr "" + +#: ./doc/common/tables/cinder-nexenta_iscsi.xml55(td) +msgid "(IntOpt) TCP Buffer size in KiloBytes." +msgstr "" + +#: ./doc/common/tables/cinder-nexenta_iscsi.xml58(td) +msgid "nexenta_sparse = False" +msgstr "" + +#: ./doc/common/tables/cinder-nexenta_iscsi.xml59(td) +msgid "(BoolOpt) flag to create sparse volumes" +msgstr "" + +#: ./doc/common/tables/cinder-nexenta_iscsi.xml62(td) +msgid "nexenta_sparsed_volumes = True" +msgstr "" + +#: ./doc/common/tables/cinder-nexenta_iscsi.xml63(td) +#: ./doc/common/tables/cinder-storage_nfs.xml39(td) +#: ./doc/common/tables/cinder-storage_glusterfs.xml35(td) +msgid "" +"(BoolOpt) Create volumes as sparsed files which take no space.If set to " +"False volume is created as regular file.In such case volume creation takes a" +" lot of time." +msgstr "" + +#: ./doc/common/tables/cinder-nexenta_iscsi.xml66(td) +msgid "nexenta_target_group_prefix = cinder/" +msgstr "" + +#: ./doc/common/tables/cinder-nexenta_iscsi.xml67(td) +msgid "(StrOpt) prefix for iSCSI target groups on SA" +msgstr "" + +#: ./doc/common/tables/cinder-nexenta_iscsi.xml70(td) +msgid "nexenta_target_prefix = iqn.1986-03.com.sun:02:cinder-" +msgstr "" + +#: ./doc/common/tables/cinder-nexenta_iscsi.xml71(td) +msgid "(StrOpt) IQN prefix for iSCSI targets" +msgstr "" + +#: ./doc/common/tables/cinder-nexenta_iscsi.xml74(td) +msgid "nexenta_user = admin" +msgstr "" + +#: ./doc/common/tables/cinder-nexenta_iscsi.xml75(td) +msgid "(StrOpt) User name to connect to Nexenta SA" +msgstr "" + +#: ./doc/common/tables/cinder-nexenta_iscsi.xml78(td) +msgid "nexenta_volume = cinder" +msgstr "" + +#: ./doc/common/tables/cinder-nexenta_iscsi.xml79(td) +msgid "(StrOpt) pool on SA that will hold all volumes" +msgstr "" + +#: ./doc/common/tables/nova-tilera.xml8(caption) +msgid "Description of configuration options for tilera" +msgstr "" + +#: ./doc/common/tables/nova-tilera.xml22(td) +msgid "tile_pdu_ip = 10.0.100.1" +msgstr "" + +#: ./doc/common/tables/nova-tilera.xml23(td) +msgid "(StrOpt) ip address of tilera pdu" +msgstr "" + +#: ./doc/common/tables/nova-tilera.xml26(td) +msgid "tile_pdu_mgr = /tftpboot/pdu_mgr" +msgstr "" + +#: ./doc/common/tables/nova-tilera.xml27(td) +msgid "(StrOpt) management script for tilera pdu" +msgstr "" + +#: ./doc/common/tables/nova-tilera.xml30(td) +msgid "tile_pdu_off = 2" +msgstr "" + +#: ./doc/common/tables/nova-tilera.xml31(td) +msgid "(IntOpt) power status of tilera PDU is OFF" +msgstr "" + +#: ./doc/common/tables/nova-tilera.xml34(td) +msgid "tile_pdu_on = 1" +msgstr "" + +#: ./doc/common/tables/nova-tilera.xml35(td) +msgid "(IntOpt) power status of tilera PDU is ON" +msgstr "" + +#: ./doc/common/tables/nova-tilera.xml38(td) +msgid "tile_pdu_status = 9" +msgstr "" + +#: ./doc/common/tables/nova-tilera.xml39(td) +msgid "(IntOpt) power status of tilera PDU" +msgstr "" + +#: ./doc/common/tables/nova-tilera.xml42(td) +msgid "tile_power_wait = 9" +msgstr "" + +#: ./doc/common/tables/nova-tilera.xml43(td) +msgid "" +"(IntOpt) wait time in seconds until check the result after tilera power " +"operations" +msgstr "" + +#: ./doc/common/tables/nova-ca.xml8(caption) +msgid "Description of configuration options for ca" +msgstr "" + +#: ./doc/common/tables/nova-ca.xml22(td) +msgid "ca_file = cacert.pem" +msgstr "" + +#: ./doc/common/tables/nova-ca.xml23(td) +msgid "(StrOpt) Filename of root CA" +msgstr "" + +#: ./doc/common/tables/nova-ca.xml26(td) +msgid "ca_path = $state_path/CA" +msgstr "" + +#: ./doc/common/tables/nova-ca.xml27(td) +msgid "(StrOpt) Where we keep our root CA" +msgstr "" + +#: ./doc/common/tables/nova-ca.xml30(td) +msgid "cert_manager = nova.cert.manager.CertManager" +msgstr "" + +#: ./doc/common/tables/nova-ca.xml31(td) +msgid "(StrOpt) full class name for the Manager for cert" +msgstr "" + +#: ./doc/common/tables/nova-ca.xml34(td) +msgid "cert_topic = cert" +msgstr "" + +#: ./doc/common/tables/nova-ca.xml35(td) +msgid "(StrOpt) the topic cert nodes listen on" +msgstr "" + +#: ./doc/common/tables/nova-ca.xml38(td) +msgid "crl_file = crl.pem" +msgstr "" + +#: ./doc/common/tables/nova-ca.xml39(td) +msgid "(StrOpt) Filename of root Certificate Revocation List" +msgstr "" + +#: ./doc/common/tables/nova-ca.xml42(td) +msgid "key_file = private/cakey.pem" +msgstr "" + +#: ./doc/common/tables/nova-ca.xml43(td) +msgid "(StrOpt) Filename of private key" +msgstr "" + +#: ./doc/common/tables/nova-ca.xml46(td) +msgid "keys_path = $state_path/keys" +msgstr "" + +#: ./doc/common/tables/nova-ca.xml47(td) +msgid "(StrOpt) Where we keep our keys" +msgstr "" + +#: ./doc/common/tables/nova-ca.xml50(td) +msgid "" +"project_cert_subject = /C=US/ST=California/O=OpenStack/OU=NovaDev/CN" +"=project-ca-%.16s-%s" +msgstr "" + +#: ./doc/common/tables/nova-ca.xml51(td) +msgid "" +"(StrOpt) Subject for certificate for projects, %s for project, timestamp" +msgstr "" + +#: ./doc/common/tables/nova-ca.xml54(td) +msgid "use_project_ca = False" +msgstr "" + +#: ./doc/common/tables/nova-ca.xml55(td) +msgid "(BoolOpt) Should we use a CA for each project?" +msgstr "" + +#: ./doc/common/tables/nova-ca.xml58(td) +msgid "" +"user_cert_subject = " +"/C=US/ST=California/O=OpenStack/OU=NovaDev/CN=%.16s-%.16s-%s" +msgstr "" + +#: ./doc/common/tables/nova-ca.xml59(td) +msgid "" +"(StrOpt) Subject for certificate for users, %s for project, user, timestamp" +msgstr "" + +#: ./doc/common/tables/nova-ca.xml65(td) +#: ./doc/common/tables/glance-ssl.xml22(td) +msgid "ca_file = None" +msgstr "" + +#: ./doc/common/tables/nova-ca.xml66(td) +#: ./doc/common/tables/nova-wsgi.xml27(td) +#: ./doc/common/tables/cinder-common.xml191(td) +#: ./doc/common/tables/neutron-ssl.xml24(td) +msgid "(StrOpt) CA certificate file to use to verify connecting clients" +msgstr "" + +#: ./doc/common/tables/nova-ca.xml69(td) +#: ./doc/common/tables/glance-ssl.xml26(td) +#: ./doc/common/tables/neutron-nec.xml19(td) +msgid "cert_file = None" +msgstr "" + +#: ./doc/common/tables/nova-ca.xml70(td) +#: ./doc/common/tables/cinder-common.xml195(td) +#: ./doc/common/tables/neutron-ssl.xml28(td) +msgid "(StrOpt) Certificate file to use when starting the server securely" +msgstr "" + +#: ./doc/common/tables/nova-ca.xml73(td) +#: ./doc/common/tables/neutron-ssl.xml19(td) +#: ./doc/common/tables/glance-ssl.xml30(td) +msgid "key_file = None" +msgstr "" + +#: ./doc/common/tables/nova-ca.xml74(td) +#: ./doc/common/tables/cinder-common.xml199(td) +#: ./doc/common/tables/neutron-ssl.xml32(td) +msgid "(StrOpt) Private key file to use when starting the server securely" +msgstr "" + +#: ./doc/common/tables/swift-account-server-filter-recon.xml7(literal) +#: ./doc/common/tables/swift-object-server-filter-recon.xml7(literal) +#: ./doc/common/tables/swift-container-server-filter-recon.xml7(literal) +msgid "[filter:recon]" +msgstr "" + +#: ./doc/common/tables/swift-account-server-filter-recon.xml7(literal) +#: ./doc/common/tables/swift-account-server-app-account-server.xml7(literal) +#: ./doc/common/tables/swift-account-server-filter-healthcheck.xml7(literal) +#: ./doc/common/tables/swift-account-server-account-auditor.xml7(literal) +#: ./doc/common/tables/swift-account-server-DEFAULT.xml7(literal) +#: ./doc/common/tables/swift-account-server-account-replicator.xml7(literal) +#: ./doc/common/tables/swift-account-server-pipeline-main.xml7(literal) +#: ./doc/common/tables/swift-account-server-account-reaper.xml7(literal) +msgid "account-server.conf-sample" +msgstr "" + +#: ./doc/common/tables/swift-account-server-filter-recon.xml18(td) +#: ./doc/common/tables/swift-object-server-filter-recon.xml18(td) +#: ./doc/common/tables/swift-container-server-filter-recon.xml18(td) +msgid "use = egg:swift#recon" +msgstr "" + +#: ./doc/common/tables/cinder-huawei.xml8(caption) +msgid "Description of configuration options for huawei" +msgstr "" + +#: ./doc/common/tables/cinder-huawei.xml22(td) +msgid "cinder_huawei_conf_file = /etc/cinder/cinder_huawei_conf.xml" +msgstr "" + +#: ./doc/common/tables/cinder-huawei.xml23(td) +msgid "(StrOpt) config data for cinder huawei plugin" +msgstr "" + +#: ./doc/common/tables/swift-container-server-container-replicator.xml7(literal) +msgid "[container-replicator]" +msgstr "" + +#: ./doc/common/tables/swift-container-server-container-replicator.xml18(td) +msgid "log_name = container-replicator" +msgstr "" + +#: ./doc/common/tables/swift-container-server-container-replicator.xml30(td) +#: ./doc/common/tables/swift-object-server-object-replicator.xml30(td) +#: ./doc/common/tables/swift-account-server-account-replicator.xml30(td) +msgid "vm_test_mode = no" +msgstr "" + +#: ./doc/common/tables/swift-container-server-container-replicator.xml30(td) +#: ./doc/common/tables/swift-object-server-object-replicator.xml30(td) +#: ./doc/common/tables/swift-account-server-account-replicator.xml30(td) +msgid "Indicates that you are using a VM environment" +msgstr "" + +#: ./doc/common/tables/swift-container-server-container-replicator.xml33(td) +#: ./doc/common/tables/swift-account-server-account-replicator.xml33(td) +msgid "per_diff = 1000" +msgstr "" + +#: ./doc/common/tables/swift-container-server-container-replicator.xml33(td) +#: ./doc/common/tables/swift-account-server-account-replicator.xml33(td) +msgid "Limit number of items to get per diff" +msgstr "" + +#: ./doc/common/tables/swift-container-server-container-replicator.xml36(td) +#: ./doc/common/tables/swift-account-server-account-replicator.xml36(td) +msgid "max_diffs = 100" +msgstr "" + +#: ./doc/common/tables/swift-container-server-container-replicator.xml36(td) +#: ./doc/common/tables/swift-account-server-account-replicator.xml36(td) +msgid "Caps how long the replicator spends trying to sync a database per pass" +msgstr "" + +#: ./doc/common/tables/swift-container-server-container-replicator.xml39(td) +#: ./doc/common/tables/swift-account-server-account-replicator.xml39(td) +msgid "concurrency = 8" +msgstr "" + +#: ./doc/common/tables/swift-container-server-container-replicator.xml42(td) +#: ./doc/common/tables/swift-account-server-account-replicator.xml42(td) +msgid "interval = 30" +msgstr "" + +#: ./doc/common/tables/swift-container-server-container-replicator.xml45(td) +#: ./doc/common/tables/swift-object-server-object-updater.xml36(td) +#: ./doc/common/tables/swift-proxy-server-app-proxy-server.xml48(td) +#: ./doc/common/tables/swift-account-server-account-replicator.xml51(td) +#: ./doc/common/tables/swift-account-server-account-reaper.xml36(td) +msgid "node_timeout = 10" +msgstr "" + +#: ./doc/common/tables/swift-container-server-container-replicator.xml51(td) +#: ./doc/common/tables/swift-object-server-object-replicator.xml60(td) +#: ./doc/common/tables/swift-account-server-account-replicator.xml57(td) +msgid "reclaim_age = 604800" +msgstr "" + +#: ./doc/common/tables/swift-container-server-container-replicator.xml51(td) +#: ./doc/common/tables/swift-object-server-object-replicator.xml60(td) +#: ./doc/common/tables/swift-account-server-account-replicator.xml57(td) +msgid "Time elapsed in seconds before an object can be reclaimed" +msgstr "" + +#: ./doc/common/tables/swift-container-server-container-replicator.xml54(td) +#: ./doc/common/tables/swift-object-server-object-replicator.xml36(td) +#: ./doc/common/tables/swift-account-server-account-replicator.xml60(td) +msgid "run_pause = 30" +msgstr "" + +#: ./doc/common/tables/swift-container-server-container-replicator.xml54(td) +#: ./doc/common/tables/swift-object-server-object-replicator.xml36(td) +#: ./doc/common/tables/swift-account-server-account-replicator.xml60(td) +msgid "Time in seconds to wait between replication passes" +msgstr "" + +#: ./doc/common/tables/nova-glance.xml8(caption) +msgid "Description of configuration options for glance" +msgstr "" + +#: ./doc/common/tables/nova-glance.xml22(td) +#: ./doc/common/tables/cinder-images.xml22(td) +msgid "allowed_direct_url_schemes =" +msgstr "" + +#: ./doc/common/tables/nova-glance.xml23(td) +msgid "" +"(ListOpt) A list of url scheme that can be downloaded directly via the " +"direct_url. Currently supported schemes: [file]." +msgstr "" + +#: ./doc/common/tables/nova-glance.xml26(td) +#: ./doc/common/tables/cinder-images.xml26(td) +msgid "glance_api_insecure = False" +msgstr "" + +#: ./doc/common/tables/nova-glance.xml27(td) +#: ./doc/common/tables/cinder-images.xml27(td) +msgid "(BoolOpt) Allow to perform insecure SSL (https) requests to glance" +msgstr "" + +#: ./doc/common/tables/nova-glance.xml30(td) +#: ./doc/common/tables/cinder-images.xml30(td) +msgid "glance_api_servers = $glance_host:$glance_port" +msgstr "" + +#: ./doc/common/tables/nova-glance.xml31(td) +msgid "" +"(ListOpt) A list of the glance api servers available to nova. Prefix with " +"https:// for ssl-based glance api servers. ([hostname|ip]:port)" +msgstr "" + +#: ./doc/common/tables/nova-glance.xml34(td) +#: ./doc/common/tables/cinder-images.xml42(td) +msgid "glance_host = $my_ip" +msgstr "" + +#: ./doc/common/tables/nova-glance.xml35(td) +#: ./doc/common/tables/cinder-images.xml43(td) +msgid "(StrOpt) default glance hostname or ip" +msgstr "" + +#: ./doc/common/tables/nova-glance.xml38(td) +#: ./doc/common/tables/cinder-images.xml46(td) +msgid "glance_num_retries = 0" +msgstr "" + +#: ./doc/common/tables/nova-glance.xml39(td) +#: ./doc/common/tables/cinder-images.xml47(td) +msgid "(IntOpt) Number retries when downloading an image from glance" +msgstr "" + +#: ./doc/common/tables/nova-glance.xml42(td) +#: ./doc/common/tables/cinder-images.xml50(td) +msgid "glance_port = 9292" +msgstr "" + +#: ./doc/common/tables/nova-glance.xml43(td) +#: ./doc/common/tables/cinder-images.xml51(td) +msgid "(IntOpt) default glance port" +msgstr "" + +#: ./doc/common/tables/nova-glance.xml46(td) +msgid "glance_protocol = http" +msgstr "" + +#: ./doc/common/tables/nova-glance.xml47(td) +msgid "" +"(StrOpt) Default protocol to use when connecting to glance. Set to https for" +" SSL." +msgstr "" + +#: ./doc/common/tables/nova-glance.xml50(td) +msgid "osapi_glance_link_prefix = None" +msgstr "" + +#: ./doc/common/tables/nova-glance.xml51(td) +msgid "" +"(StrOpt) Base URL that will be presented to users in links to glance " +"resources" +msgstr "" + +#: ./doc/common/tables/nova-glance.xml54(th) +msgid "[image_file_url]" +msgstr "" + +#: ./doc/common/tables/nova-glance.xml57(td) +msgid "filesystems =" +msgstr "" + +#: ./doc/common/tables/nova-glance.xml58(td) +msgid "" +"(ListOpt) A list of filesystems that will be configured in this file under " +"the sections image_file_url:<list entry name>" +msgstr "" + +#: ./doc/common/tables/nova-neutron.xml8(caption) +msgid "Description of configuration options for neutron" +msgstr "" + +#: ./doc/common/tables/nova-neutron.xml22(td) +msgid "neutron_admin_auth_url = http://localhost:5000/v2.0" +msgstr "" + +#: ./doc/common/tables/nova-neutron.xml23(td) +msgid "(StrOpt) auth url for connecting to neutron in admin context" +msgstr "" + +#: ./doc/common/tables/nova-neutron.xml26(td) +msgid "neutron_admin_password = None" +msgstr "" + +#: ./doc/common/tables/nova-neutron.xml27(td) +msgid "(StrOpt) password for connecting to neutron in admin context" +msgstr "" + +#: ./doc/common/tables/nova-neutron.xml30(td) +msgid "neutron_admin_tenant_name = None" +msgstr "" + +#: ./doc/common/tables/nova-neutron.xml31(td) +msgid "(StrOpt) tenant name for connecting to neutron in admin context" +msgstr "" + +#: ./doc/common/tables/nova-neutron.xml34(td) +msgid "neutron_admin_username = None" +msgstr "" + +#: ./doc/common/tables/nova-neutron.xml35(td) +msgid "(StrOpt) username for connecting to neutron in admin context" +msgstr "" + +#: ./doc/common/tables/nova-neutron.xml38(td) +msgid "neutron_api_insecure = False" +msgstr "" + +#: ./doc/common/tables/nova-neutron.xml39(td) +msgid "(BoolOpt) if set, ignore any SSL validation issues" +msgstr "" + +#: ./doc/common/tables/nova-neutron.xml42(td) +msgid "neutron_auth_strategy = keystone" +msgstr "" + +#: ./doc/common/tables/nova-neutron.xml43(td) +msgid "(StrOpt) auth strategy for connecting to neutron in admin context" +msgstr "" + +#: ./doc/common/tables/nova-neutron.xml46(td) +msgid "neutron_ca_certificates_file = None" +msgstr "" + +#: ./doc/common/tables/nova-neutron.xml47(td) +msgid "" +"(StrOpt) Location of ca certificates file to use for neutron client " +"requests." +msgstr "" + +#: ./doc/common/tables/nova-neutron.xml50(td) +msgid "neutron_default_tenant_id = default" +msgstr "" + +#: ./doc/common/tables/nova-neutron.xml51(td) +msgid "(StrOpt) Default tenant id when creating neutron networks" +msgstr "" + +#: ./doc/common/tables/nova-neutron.xml54(td) +msgid "neutron_extension_sync_interval = 600" +msgstr "" + +#: ./doc/common/tables/nova-neutron.xml55(td) +msgid "(IntOpt) Number of seconds before querying neutron for extensions" +msgstr "" + +#: ./doc/common/tables/nova-neutron.xml58(td) +msgid "neutron_metadata_proxy_shared_secret =" +msgstr "" + +#: ./doc/common/tables/nova-neutron.xml59(td) +msgid "(StrOpt) Shared secret to validate proxies Neutron metadata requests" +msgstr "" + +#: ./doc/common/tables/nova-neutron.xml62(td) +msgid "neutron_ovs_bridge = br-int" +msgstr "" + +#: ./doc/common/tables/nova-neutron.xml63(td) +#: ./doc/common/tables/nova-xen.xml153(td) +msgid "(StrOpt) Name of Integration Bridge used by Open vSwitch" +msgstr "" + +#: ./doc/common/tables/nova-neutron.xml66(td) +msgid "neutron_region_name = None" +msgstr "" + +#: ./doc/common/tables/nova-neutron.xml67(td) +msgid "(StrOpt) region name for connecting to neutron in admin context" +msgstr "" + +#: ./doc/common/tables/nova-neutron.xml70(td) +msgid "neutron_url = http://127.0.0.1:9696" +msgstr "" + +#: ./doc/common/tables/nova-neutron.xml71(td) +msgid "(StrOpt) URL for connecting to neutron" +msgstr "" + +#: ./doc/common/tables/nova-neutron.xml74(td) +msgid "neutron_url_timeout = 30" +msgstr "" + +#: ./doc/common/tables/nova-neutron.xml75(td) +msgid "(IntOpt) timeout value for connecting to neutron in seconds" +msgstr "" + +#: ./doc/common/tables/nova-neutron.xml78(td) +msgid "service_neutron_metadata_proxy = False" +msgstr "" + +#: ./doc/common/tables/nova-neutron.xml79(td) +msgid "" +"(BoolOpt) Set flag to indicate Neutron will proxy metadata requests and " +"resolve instance ids." +msgstr "" + +#: ./doc/common/tables/cinder-backups_ceph.xml8(caption) +msgid "Description of configuration options for backups_ceph" +msgstr "" + +#: ./doc/common/tables/cinder-backups_ceph.xml22(td) +msgid "backup_ceph_chunk_size = 134217728" +msgstr "" + +#: ./doc/common/tables/cinder-backups_ceph.xml23(td) +msgid "" +"(IntOpt) the chunk size in bytes that a backup will be broken into before " +"transfer to backup store" +msgstr "" + +#: ./doc/common/tables/cinder-backups_ceph.xml26(td) +msgid "backup_ceph_conf = /etc/ceph/ceph.conf" +msgstr "" + +#: ./doc/common/tables/cinder-backups_ceph.xml27(td) +msgid "(StrOpt) Ceph config file to use." +msgstr "" + +#: ./doc/common/tables/cinder-backups_ceph.xml30(td) +msgid "backup_ceph_pool = backups" +msgstr "" + +#: ./doc/common/tables/cinder-backups_ceph.xml31(td) +msgid "(StrOpt) the Ceph pool to backup to" +msgstr "" + +#: ./doc/common/tables/cinder-backups_ceph.xml34(td) +msgid "backup_ceph_stripe_count = 0" +msgstr "" + +#: ./doc/common/tables/cinder-backups_ceph.xml35(td) +msgid "(IntOpt) RBD stripe count to use when creating a backup image" +msgstr "" + +#: ./doc/common/tables/cinder-backups_ceph.xml38(td) +msgid "backup_ceph_stripe_unit = 0" +msgstr "" + +#: ./doc/common/tables/cinder-backups_ceph.xml39(td) +msgid "(IntOpt) RBD stripe unit to use when creating a backup image" +msgstr "" + +#: ./doc/common/tables/cinder-backups_ceph.xml42(td) +msgid "backup_ceph_user = cinder" +msgstr "" + +#: ./doc/common/tables/cinder-backups_ceph.xml43(td) +msgid "(StrOpt) the Ceph user to connect with" +msgstr "" + +#: ./doc/common/tables/cinder-backups_ceph.xml46(td) +msgid "restore_discard_excess_bytes = True" +msgstr "" + +#: ./doc/common/tables/cinder-backups_ceph.xml47(td) +msgid "(BoolOpt) If True, always discard excess bytes when restoring volumes." +msgstr "" + +#: ./doc/common/tables/swift-proxy-server-filter-name_check.xml7(literal) +msgid "[filter:name_check]" +msgstr "" + +#: ./doc/common/tables/swift-proxy-server-filter-name_check.xml18(td) +msgid "use = egg:swift#name_check" +msgstr "" + +#: ./doc/common/tables/swift-proxy-server-filter-name_check.xml21(td) +msgid "forbidden_chars = '\"`<>" +msgstr "" + +#: ./doc/common/tables/swift-proxy-server-filter-name_check.xml21(td) +msgid "Characters that are not allowed in a name" +msgstr "" + +#: ./doc/common/tables/swift-proxy-server-filter-name_check.xml24(td) +msgid "maximum_length = 255" +msgstr "" + +#: ./doc/common/tables/swift-proxy-server-filter-name_check.xml24(td) +msgid "Maximum length of a name" +msgstr "" + +#: ./doc/common/tables/swift-proxy-server-filter-name_check.xml27(td) +msgid "forbidden_regexp = /\\./|/\\.\\./|/\\.$|/\\.\\.$" +msgstr "" + +#: ./doc/common/tables/swift-proxy-server-filter-name_check.xml27(td) +msgid "Substrings to forbid, using regular expression syntax" +msgstr "" + +#: ./doc/common/tables/nova-metadata.xml8(caption) +#: ./doc/common/tables/neutron-metadata.xml8(caption) +msgid "Description of configuration options for metadata" +msgstr "" + +#: ./doc/common/tables/nova-metadata.xml22(td) +msgid "metadata_host = $my_ip" +msgstr "" + +#: ./doc/common/tables/nova-metadata.xml23(td) +msgid "(StrOpt) the ip for the metadata api server" +msgstr "" + +#: ./doc/common/tables/nova-metadata.xml26(td) +msgid "metadata_listen = 0.0.0.0" +msgstr "" + +#: ./doc/common/tables/nova-metadata.xml27(td) +msgid "(StrOpt) The IP address on which the metadata API will listen." +msgstr "" + +#: ./doc/common/tables/nova-metadata.xml30(td) +msgid "metadata_listen_port = 8775" +msgstr "" + +#: ./doc/common/tables/nova-metadata.xml31(td) +msgid "(IntOpt) The port on which the metadata API will listen." +msgstr "" + +#: ./doc/common/tables/nova-metadata.xml34(td) +msgid "metadata_manager = nova.api.manager.MetadataManager" +msgstr "" + +#: ./doc/common/tables/nova-metadata.xml35(td) +msgid "(StrOpt) OpenStack metadata service manager" +msgstr "" + +#: ./doc/common/tables/nova-metadata.xml38(td) +msgid "metadata_port = 8775" +msgstr "" + +#: ./doc/common/tables/nova-metadata.xml39(td) +msgid "(IntOpt) the port for the metadata api port" +msgstr "" + +#: ./doc/common/tables/nova-metadata.xml42(td) +msgid "metadata_workers = None" +msgstr "" + +#: ./doc/common/tables/nova-metadata.xml43(td) +msgid "(IntOpt) Number of workers for metadata service" +msgstr "" + +#: ./doc/common/tables/nova-metadata.xml46(td) +msgid "" +"vendordata_driver = nova.api.metadata.vendordata_json.JsonFileVendorData" +msgstr "" + +#: ./doc/common/tables/nova-metadata.xml47(td) +msgid "(StrOpt) Driver to use for vendor data" +msgstr "" + +#: ./doc/common/tables/nova-metadata.xml50(td) +msgid "vendordata_jsonfile_path = None" +msgstr "" + +#: ./doc/common/tables/nova-metadata.xml51(td) +msgid "(StrOpt) File to load json formatted vendor data from" +msgstr "" + +#: ./doc/common/tables/glance-s3.xml8(caption) +#: ./doc/common/tables/nova-s3.xml8(caption) +msgid "Description of configuration options for s3" +msgstr "" + +#: ./doc/common/tables/glance-s3.xml22(td) +msgid "s3_store_access_key = None" +msgstr "" + +#: ./doc/common/tables/glance-s3.xml23(td) +msgid "(StrOpt) The S3 query token access key." +msgstr "" + +#: ./doc/common/tables/glance-s3.xml26(td) +msgid "s3_store_bucket = None" +msgstr "" + +#: ./doc/common/tables/glance-s3.xml27(td) +msgid "(StrOpt) The S3 bucket to be used to store the Glance data." +msgstr "" + +#: ./doc/common/tables/glance-s3.xml30(td) +msgid "s3_store_bucket_url_format = subdomain" +msgstr "" + +#: ./doc/common/tables/glance-s3.xml31(td) +msgid "" +"(StrOpt) The S3 calling format used to determine the bucket. Either " +"subdomain or path can be used." +msgstr "" + +#: ./doc/common/tables/glance-s3.xml34(td) +msgid "s3_store_create_bucket_on_put = False" +msgstr "" + +#: ./doc/common/tables/glance-s3.xml35(td) +msgid "" +"(BoolOpt) A boolean to determine if the S3 bucket should be created on " +"upload if it does not exist or if an error should be returned to the user." +msgstr "" + +#: ./doc/common/tables/glance-s3.xml38(td) +msgid "s3_store_host = None" +msgstr "" + +#: ./doc/common/tables/glance-s3.xml39(td) +msgid "(StrOpt) The host where the S3 server is listening." +msgstr "" + +#: ./doc/common/tables/glance-s3.xml42(td) +msgid "s3_store_object_buffer_dir = None" +msgstr "" + +#: ./doc/common/tables/glance-s3.xml43(td) +msgid "" +"(StrOpt) The local directory where uploads will be staged before they are " +"transferred into S3." +msgstr "" + +#: ./doc/common/tables/glance-s3.xml46(td) +msgid "s3_store_secret_key = None" +msgstr "" + +#: ./doc/common/tables/glance-s3.xml47(td) +msgid "(StrOpt) The S3 query token secret key." +msgstr "" + +#: ./doc/common/tables/neutron-kombu.xml8(caption) +#: ./doc/common/tables/nova-kombu.xml8(caption) +msgid "Description of configuration options for kombu" +msgstr "" + +#: ./doc/common/tables/neutron-kombu.xml19(td) +#: ./doc/common/tables/cinder-rpc.xml46(td) +#: ./doc/common/tables/glance-rabbitmq.xml26(td) +#: ./doc/common/tables/nova-kombu.xml22(td) +msgid "kombu_ssl_ca_certs =" +msgstr "" + +#: ./doc/common/tables/neutron-kombu.xml20(td) +#: ./doc/common/tables/cinder-rpc.xml47(td) +#: ./doc/common/tables/glance-rabbitmq.xml27(td) +#: ./doc/common/tables/nova-kombu.xml23(td) +msgid "(StrOpt) SSL certification authority file (valid only if SSL enabled)" +msgstr "" + +#: ./doc/common/tables/neutron-kombu.xml23(td) +#: ./doc/common/tables/cinder-rpc.xml50(td) +#: ./doc/common/tables/glance-rabbitmq.xml30(td) +#: ./doc/common/tables/nova-kombu.xml26(td) +msgid "kombu_ssl_certfile =" +msgstr "" + +#: ./doc/common/tables/neutron-kombu.xml24(td) +#: ./doc/common/tables/cinder-rpc.xml51(td) +#: ./doc/common/tables/glance-rabbitmq.xml31(td) +#: ./doc/common/tables/nova-kombu.xml27(td) +msgid "(StrOpt) SSL cert file (valid only if SSL enabled)" +msgstr "" + +#: ./doc/common/tables/neutron-kombu.xml27(td) +#: ./doc/common/tables/cinder-rpc.xml54(td) +#: ./doc/common/tables/glance-rabbitmq.xml34(td) +#: ./doc/common/tables/nova-kombu.xml30(td) +msgid "kombu_ssl_keyfile =" +msgstr "" + +#: ./doc/common/tables/neutron-kombu.xml28(td) +#: ./doc/common/tables/cinder-rpc.xml55(td) +#: ./doc/common/tables/glance-rabbitmq.xml35(td) +#: ./doc/common/tables/nova-kombu.xml31(td) +msgid "(StrOpt) SSL key file (valid only if SSL enabled)" +msgstr "" + +#: ./doc/common/tables/neutron-kombu.xml31(td) +#: ./doc/common/tables/cinder-rpc.xml58(td) +#: ./doc/common/tables/glance-rabbitmq.xml38(td) +#: ./doc/common/tables/nova-kombu.xml34(td) +msgid "kombu_ssl_version =" +msgstr "" + +#: ./doc/common/tables/neutron-kombu.xml32(td) +#: ./doc/common/tables/cinder-rpc.xml59(td) +msgid "(StrOpt) SSL version to use (valid only if SSL enabled)" +msgstr "" + +#: ./doc/common/tables/swift-proxy-server-filter-ratelimit.xml7(literal) +msgid "[filter:ratelimit]" +msgstr "" + +#: ./doc/common/tables/swift-proxy-server-filter-ratelimit.xml18(td) +msgid "use = egg:swift#ratelimit" +msgstr "" + +#: ./doc/common/tables/swift-proxy-server-filter-ratelimit.xml21(td) +msgid "set log_name = ratelimit" +msgstr "" + +#: ./doc/common/tables/swift-proxy-server-filter-ratelimit.xml36(td) +msgid "clock_accuracy = 1000" +msgstr "" + +#: ./doc/common/tables/swift-proxy-server-filter-ratelimit.xml36(td) +msgid "" +"Represents how accurate the proxy servers' system clocks are with each " +"other. 1000 means that all the proxies' clock are accurate to each other " +"within 1 millisecond. No ratelimit should be higher than the clock accuracy." +msgstr "" + +#: ./doc/common/tables/swift-proxy-server-filter-ratelimit.xml39(td) +msgid "max_sleep_time_seconds = 60" +msgstr "" + +#: ./doc/common/tables/swift-proxy-server-filter-ratelimit.xml39(td) +msgid "" +"App will immediately return a 498 response if the necessary sleep time ever " +"exceeds the given max_sleep_time_seconds." +msgstr "" + +#: ./doc/common/tables/swift-proxy-server-filter-ratelimit.xml42(td) +msgid "log_sleep_time_seconds = 0" +msgstr "" + +#: ./doc/common/tables/swift-proxy-server-filter-ratelimit.xml42(td) +msgid "" +"To allow visibility into rate limiting set this value > 0 and all sleeps " +"greater than the number will be logged." +msgstr "" + +#: ./doc/common/tables/swift-proxy-server-filter-ratelimit.xml45(td) +msgid "rate_buffer_seconds = 5" +msgstr "" + +#: ./doc/common/tables/swift-proxy-server-filter-ratelimit.xml45(td) +msgid "" +"Number of seconds the rate counter can drop and be allowed to catch up (at a" +" faster than listed rate). A larger number will result in larger spikes in " +"rate but better average accuracy." +msgstr "" + +#: ./doc/common/tables/swift-proxy-server-filter-ratelimit.xml48(td) +msgid "account_ratelimit = 0" +msgstr "" + +#: ./doc/common/tables/swift-proxy-server-filter-ratelimit.xml48(td) +msgid "" +"If set, will limit PUT and DELETE requests to /account_name/container_name. " +"Number is in requests per second." +msgstr "" + +#: ./doc/common/tables/swift-proxy-server-filter-ratelimit.xml51(td) +msgid "account_whitelist = a,b" +msgstr "" + +#: ./doc/common/tables/swift-proxy-server-filter-ratelimit.xml51(td) +msgid "Comma separated lists of account names that will not be rate limited." +msgstr "" + +#: ./doc/common/tables/swift-proxy-server-filter-ratelimit.xml54(td) +msgid "account_blacklist = c,d" +msgstr "" + +#: ./doc/common/tables/swift-proxy-server-filter-ratelimit.xml54(td) +msgid "" +"Comma separated lists of account names that will not be allowed. Returns a " +"497 response. r: for containers of size x, limit requests per second to r. " +"Will limit PUT, DELETE, and POST requests to /a/c/o. " +"container_listing_ratelimit_x = r: for containers of size x, limit listing " +"requests per second to r. Will limit GET requests to /a/c." +msgstr "" + +#: ./doc/common/tables/swift-proxy-server-filter-ratelimit.xml57(td) +msgid "with container_limit_x = r" +msgstr "" + +#: ./doc/common/tables/swift-proxy-server-filter-ratelimit.xml60(td) +msgid "container_ratelimit_0 = 100" +msgstr "" + +#: ./doc/common/tables/swift-proxy-server-filter-ratelimit.xml63(td) +msgid "container_ratelimit_10 = 50" +msgstr "" + +#: ./doc/common/tables/swift-proxy-server-filter-ratelimit.xml66(td) +msgid "container_ratelimit_50 = 20" +msgstr "" + +#: ./doc/common/tables/swift-proxy-server-filter-ratelimit.xml69(td) +msgid "container_listing_ratelimit_0 = 100" +msgstr "" + +#: ./doc/common/tables/swift-proxy-server-filter-ratelimit.xml72(td) +msgid "container_listing_ratelimit_10 = 50" +msgstr "" + +#: ./doc/common/tables/swift-proxy-server-filter-ratelimit.xml75(td) +msgid "container_listing_ratelimit_50 = 20" +msgstr "" + +#: ./doc/common/tables/cinder-block-device.xml8(caption) +msgid "Description of configuration options for block-device" +msgstr "" + +#: ./doc/common/tables/cinder-block-device.xml22(td) +msgid "available_devices =" +msgstr "" + +#: ./doc/common/tables/cinder-block-device.xml23(td) +msgid "(ListOpt) List of all available devices" +msgstr "" + +#: ./doc/common/tables/cinder-zones.xml8(caption) +msgid "Description of configuration options for zones" +msgstr "" + +#: ./doc/common/tables/cinder-zones.xml22(td) +msgid "cloned_volume_same_az = True" +msgstr "" + +#: ./doc/common/tables/cinder-zones.xml23(td) +msgid "" +"(BoolOpt) Ensure that the new volumes are the same AZ as snapshot or source " +"volume" +msgstr "" + +#: ./doc/common/tables/cinder-netapp_7mode_iscsi.xml8(caption) +msgid "Description of configuration options for netapp_7mode_iscsi" +msgstr "" + +#: ./doc/common/tables/cinder-netapp_7mode_iscsi.xml22(td) +#: ./doc/common/tables/cinder-netapp_cdot_iscsi.xml22(td) +#: ./doc/common/tables/cinder-netapp_7mode_nfs.xml26(td) +#: ./doc/common/tables/cinder-netapp_cdot_nfs.xml26(td) +msgid "netapp_login = None" +msgstr "" + +#: ./doc/common/tables/cinder-netapp_7mode_iscsi.xml23(td) +#: ./doc/common/tables/cinder-netapp_cdot_iscsi.xml23(td) +#: ./doc/common/tables/cinder-netapp_7mode_nfs.xml27(td) +#: ./doc/common/tables/cinder-netapp_cdot_nfs.xml27(td) +msgid "" +"(StrOpt) Administrative user account name used to access the storage system." +msgstr "" + +#: ./doc/common/tables/cinder-netapp_7mode_iscsi.xml26(td) +#: ./doc/common/tables/cinder-netapp_cdot_iscsi.xml26(td) +#: ./doc/common/tables/cinder-netapp_7mode_nfs.xml30(td) +#: ./doc/common/tables/cinder-netapp_cdot_nfs.xml30(td) +msgid "netapp_password = None" +msgstr "" + +#: ./doc/common/tables/cinder-netapp_7mode_iscsi.xml27(td) +#: ./doc/common/tables/cinder-netapp_cdot_iscsi.xml27(td) +#: ./doc/common/tables/cinder-netapp_7mode_nfs.xml31(td) +#: ./doc/common/tables/cinder-netapp_cdot_nfs.xml31(td) +msgid "" +"(StrOpt) Password for the administrative user account specified in the " +"netapp_login option." +msgstr "" + +#: ./doc/common/tables/cinder-netapp_7mode_iscsi.xml30(td) +#: ./doc/common/tables/cinder-netapp_cdot_iscsi.xml30(td) +#: ./doc/common/tables/cinder-netapp_7mode_nfs.xml34(td) +#: ./doc/common/tables/cinder-netapp_cdot_nfs.xml34(td) +msgid "netapp_server_hostname = None" +msgstr "" + +#: ./doc/common/tables/cinder-netapp_7mode_iscsi.xml31(td) +#: ./doc/common/tables/cinder-netapp_cdot_iscsi.xml31(td) +#: ./doc/common/tables/cinder-netapp_7mode_nfs.xml35(td) +#: ./doc/common/tables/cinder-netapp_cdot_nfs.xml35(td) +msgid "(StrOpt) The hostname (or IP address) for the storage system." +msgstr "" + +#: ./doc/common/tables/cinder-netapp_7mode_iscsi.xml34(td) +#: ./doc/common/tables/cinder-netapp_cdot_iscsi.xml34(td) +#: ./doc/common/tables/cinder-netapp_7mode_nfs.xml38(td) +#: ./doc/common/tables/cinder-netapp_cdot_nfs.xml38(td) +msgid "netapp_server_port = 80" +msgstr "" + +#: ./doc/common/tables/cinder-netapp_7mode_iscsi.xml35(td) +#: ./doc/common/tables/cinder-netapp_cdot_iscsi.xml35(td) +#: ./doc/common/tables/cinder-netapp_7mode_nfs.xml39(td) +#: ./doc/common/tables/cinder-netapp_cdot_nfs.xml39(td) +msgid "" +"(IntOpt) The TCP port to use for communication with ONTAPI on the storage " +"system. Traditionally, port 80 is used for HTTP and port 443 is used for " +"HTTPS; however, this value should be changed if an alternate port has been " +"configured on the storage system." +msgstr "" + +#: ./doc/common/tables/cinder-netapp_7mode_iscsi.xml38(td) +#: ./doc/common/tables/cinder-netapp_cdot_iscsi.xml38(td) +msgid "netapp_size_multiplier = 1.2" +msgstr "" + +#: ./doc/common/tables/cinder-netapp_7mode_iscsi.xml39(td) +#: ./doc/common/tables/cinder-netapp_cdot_iscsi.xml39(td) +msgid "" +"(FloatOpt) The quantity to be multiplied by the requested volume size to " +"ensure enough space is available on the virtual storage server (Vserver) to " +"fulfill the volume creation request." +msgstr "" + +#: ./doc/common/tables/cinder-netapp_7mode_iscsi.xml42(td) +#: ./doc/common/tables/cinder-netapp_cdot_iscsi.xml42(td) +#: ./doc/common/tables/cinder-netapp_7mode_nfs.xml42(td) +#: ./doc/common/tables/cinder-netapp_cdot_nfs.xml42(td) +msgid "netapp_storage_family = ontap_cluster" +msgstr "" + +#: ./doc/common/tables/cinder-netapp_7mode_iscsi.xml43(td) +#: ./doc/common/tables/cinder-netapp_cdot_iscsi.xml43(td) +#: ./doc/common/tables/cinder-netapp_7mode_nfs.xml43(td) +#: ./doc/common/tables/cinder-netapp_cdot_nfs.xml43(td) +msgid "" +"(StrOpt) The storage family type used on the storage system; valid values " +"are ontap_7mode for using Data ONTAP operating in 7-Mode or ontap_cluster " +"for using clustered Data ONTAP." +msgstr "" + +#: ./doc/common/tables/cinder-netapp_7mode_iscsi.xml46(td) +#: ./doc/common/tables/cinder-netapp_cdot_iscsi.xml46(td) +#: ./doc/common/tables/cinder-netapp_7mode_nfs.xml46(td) +#: ./doc/common/tables/cinder-netapp_cdot_nfs.xml46(td) +msgid "netapp_storage_protocol = None" +msgstr "" + +#: ./doc/common/tables/cinder-netapp_7mode_iscsi.xml47(td) +#: ./doc/common/tables/cinder-netapp_cdot_iscsi.xml47(td) +#: ./doc/common/tables/cinder-netapp_7mode_nfs.xml47(td) +#: ./doc/common/tables/cinder-netapp_cdot_nfs.xml47(td) +msgid "" +"(StrOpt) The storage protocol to be used on the data path with the storage " +"system; valid values are iscsi or nfs." +msgstr "" + +#: ./doc/common/tables/cinder-netapp_7mode_iscsi.xml50(td) +#: ./doc/common/tables/cinder-netapp_cdot_iscsi.xml50(td) +#: ./doc/common/tables/cinder-netapp_7mode_nfs.xml50(td) +#: ./doc/common/tables/cinder-netapp_cdot_nfs.xml50(td) +msgid "netapp_transport_type = http" +msgstr "" + +#: ./doc/common/tables/cinder-netapp_7mode_iscsi.xml51(td) +#: ./doc/common/tables/cinder-netapp_cdot_iscsi.xml51(td) +#: ./doc/common/tables/cinder-netapp_7mode_nfs.xml51(td) +#: ./doc/common/tables/cinder-netapp_cdot_nfs.xml51(td) +msgid "" +"(StrOpt) The transport protocol used when communicating with ONTAPI on the " +"storage system. Valid values are http or https." +msgstr "" + +#: ./doc/common/tables/cinder-netapp_7mode_iscsi.xml54(td) +msgid "netapp_vfiler = None" +msgstr "" + +#: ./doc/common/tables/cinder-netapp_7mode_iscsi.xml55(td) +msgid "" +"(StrOpt) The vFiler unit on which provisioning of block storage volumes will" +" be done. This option is only used by the driver when connecting to an " +"instance with a storage family of Data ONTAP operating in 7-Mode and the " +"storage protocol selected is iSCSI. Only use this option when utilizing the " +"MultiStore feature on the NetApp storage system." +msgstr "" + +#: ./doc/common/tables/cinder-netapp_7mode_iscsi.xml58(td) +msgid "netapp_volume_list = None" +msgstr "" + +#: ./doc/common/tables/cinder-netapp_7mode_iscsi.xml59(td) +msgid "" +"(StrOpt) This option is only utilized when the storage protocol is " +"configured to use iSCSI. This option is used to restrict provisioning to the" +" specified controller volumes. Specify the value of this option to be a " +"comma separated list of NetApp controller volume names to be used for " +"provisioning." +msgstr "" + +#: ./doc/common/tables/swift-container-server-container-sync.xml7(literal) +msgid "[container-sync]" +msgstr "" + +#: ./doc/common/tables/swift-container-server-container-sync.xml18(td) +msgid "log_name = container-sync" +msgstr "" + +#: ./doc/common/tables/swift-container-server-container-sync.xml30(td) +msgid "sync_proxy = http://127.0.0.1:8888" +msgstr "" + +#: ./doc/common/tables/swift-container-server-container-sync.xml30(td) +msgid "If you need to use an HTTP proxy, set it here. Defaults to no proxy." +msgstr "" + +#: ./doc/common/tables/swift-container-server-container-sync.xml36(td) +msgid "container_time = 60" +msgstr "" + +#: ./doc/common/tables/swift-container-server-container-sync.xml36(td) +msgid "Maximum amount of time to spend syncing each container" +msgstr "" + +#: ./doc/common/tables/neutron-common.xml8(caption) +#: ./doc/common/tables/nova-common.xml8(caption) +#: ./doc/common/tables/glance-common.xml8(caption) +#: ./doc/common/tables/cinder-common.xml8(caption) +msgid "Description of configuration options for common" +msgstr "" + +#: ./doc/common/tables/neutron-common.xml19(td) +#: ./doc/common/tables/neutron-common.xml23(td) +#: ./doc/common/tables/neutron-common.xml27(td) +#: ./doc/common/tables/glance-registry.xml22(td) +msgid "admin_password = None" +msgstr "" + +#: ./doc/common/tables/neutron-common.xml20(td) +#: ./doc/common/tables/neutron-common.xml24(td) +msgid "(StrOpt) Admin password" +msgstr "" + +#: ./doc/common/tables/neutron-common.xml28(td) +msgid "(StrOpt) ESM admin password." +msgstr "" + +#: ./doc/common/tables/neutron-common.xml31(td) +#: ./doc/common/tables/neutron-common.xml35(td) +#: ./doc/common/tables/glance-registry.xml26(td) +msgid "admin_tenant_name = None" +msgstr "" + +#: ./doc/common/tables/neutron-common.xml32(td) +#: ./doc/common/tables/neutron-common.xml36(td) +msgid "(StrOpt) Admin tenant name" +msgstr "" + +#: ./doc/common/tables/neutron-common.xml39(td) +#: ./doc/common/tables/neutron-common.xml43(td) +#: ./doc/common/tables/glance-registry.xml30(td) +msgid "admin_user = None" +msgstr "" + +#: ./doc/common/tables/neutron-common.xml40(td) +msgid "(StrOpt) Admin username" +msgstr "" + +#: ./doc/common/tables/neutron-common.xml44(td) +msgid "(StrOpt) Admin user" +msgstr "" + +#: ./doc/common/tables/neutron-common.xml47(td) +msgid "" +"allowed_rpc_exception_modules = neutron.openstack.common.exception, " +"nova.exception, cinder.exception, exceptions" +msgstr "" + +#: ./doc/common/tables/neutron-common.xml48(td) +#: ./doc/common/tables/nova-testing.xml23(td) +#: ./doc/common/tables/cinder-rpc.xml23(td) +#: ./doc/common/tables/glance-rpc.xml23(td) +msgid "" +"(ListOpt) Modules of exceptions that are permitted to be recreatedupon " +"receiving exception data from an rpc call." +msgstr "" + +#: ./doc/common/tables/neutron-common.xml51(td) +msgid "api_workers = 0" +msgstr "" + +#: ./doc/common/tables/neutron-common.xml52(td) +msgid "(IntOpt) Number of separate worker processes for service" +msgstr "" + +#: ./doc/common/tables/neutron-common.xml55(td) +#: ./doc/common/tables/neutron-common.xml59(td) +#: ./doc/common/tables/glance-registry.xml34(td) +msgid "auth_region = None" +msgstr "" + +#: ./doc/common/tables/neutron-common.xml56(td) +#: ./doc/common/tables/neutron-common.xml60(td) +msgid "(StrOpt) Authentication region" +msgstr "" + +#: ./doc/common/tables/neutron-common.xml63(td) +#: ./doc/common/tables/neutron-metadata.xml19(td) +msgid "auth_strategy = keystone" +msgstr "" + +#: ./doc/common/tables/neutron-common.xml64(td) +#: ./doc/common/tables/neutron-metadata.xml20(td) +msgid "(StrOpt) The type of authentication to use" +msgstr "" + +#: ./doc/common/tables/neutron-common.xml67(td) +#: ./doc/common/tables/neutron-common.xml71(td) +#: ./doc/common/tables/glance-registry.xml42(td) +msgid "auth_url = None" +msgstr "" + +#: ./doc/common/tables/neutron-common.xml68(td) +#: ./doc/common/tables/neutron-common.xml72(td) +msgid "(StrOpt) Authentication URL" +msgstr "" + +#: ./doc/common/tables/neutron-common.xml75(td) +msgid "base_mac = fa:16:3e:00:00:00" +msgstr "" + +#: ./doc/common/tables/neutron-common.xml76(td) +msgid "(StrOpt) The base MAC address Neutron will use for VIFs" +msgstr "" + +#: ./doc/common/tables/neutron-common.xml79(td) +#: ./doc/common/tables/glance-common.xml34(td) +msgid "bind_host = 0.0.0.0" +msgstr "" + +#: ./doc/common/tables/neutron-common.xml80(td) +msgid "(StrOpt) The host IP to bind to" +msgstr "" + +#: ./doc/common/tables/neutron-common.xml83(td) +msgid "bind_port = 9696" +msgstr "" + +#: ./doc/common/tables/neutron-common.xml84(td) +msgid "(IntOpt) The port to bind to" +msgstr "" + +#: ./doc/common/tables/neutron-common.xml87(td) +msgid "core_plugin = None" +msgstr "" + +#: ./doc/common/tables/neutron-common.xml88(td) +msgid "(StrOpt) The core plugin Neutron will use" +msgstr "" + +#: ./doc/common/tables/neutron-common.xml91(td) +msgid "dhcp_agent_notification = True" +msgstr "" + +#: ./doc/common/tables/neutron-common.xml92(td) +msgid "(BoolOpt) Allow sending resource operation notification to DHCP agent" +msgstr "" + +#: ./doc/common/tables/neutron-common.xml95(td) +msgid "dhcp_lease_duration = 86400" +msgstr "" + +#: ./doc/common/tables/neutron-common.xml96(td) +msgid "(IntOpt) DHCP lease duration" +msgstr "" + +#: ./doc/common/tables/neutron-common.xml99(td) +#: ./doc/common/tables/nova-common.xml38(td) +#: ./doc/common/tables/glance-common.xml46(td) +#: ./doc/common/tables/cinder-common.xml50(td) +msgid "disable_process_locking = False" +msgstr "" + +#: ./doc/common/tables/neutron-common.xml100(td) +#: ./doc/common/tables/nova-common.xml39(td) +#: ./doc/common/tables/glance-common.xml47(td) +#: ./doc/common/tables/cinder-common.xml51(td) +msgid "(BoolOpt) Whether to disable inter-process locks" +msgstr "" + +#: ./doc/common/tables/neutron-common.xml103(td) +msgid "force_gateway_on_subnet = False" +msgstr "" + +#: ./doc/common/tables/neutron-common.xml104(td) +msgid "(BoolOpt) Ensure that configured gateway is on subnet" +msgstr "" + +#: ./doc/common/tables/neutron-common.xml107(td) +msgid "host = [hostname]" +msgstr "" + +#: ./doc/common/tables/neutron-common.xml108(td) +msgid "(StrOpt) The hostname Neutron is running on" +msgstr "" + +#: ./doc/common/tables/neutron-common.xml111(td) +#: ./doc/common/tables/nova-common.xml46(td) +#: ./doc/common/tables/glance-common.xml70(td) +#: ./doc/common/tables/cinder-common.xml78(td) +msgid "lock_path = None" +msgstr "" + +#: ./doc/common/tables/neutron-common.xml112(td) +#: ./doc/common/tables/cinder-common.xml79(td) +msgid "(StrOpt) Directory to use for lock files. Default to a temp directory" +msgstr "" + +#: ./doc/common/tables/neutron-common.xml115(td) +msgid "mac_generation_retries = 16" +msgstr "" + +#: ./doc/common/tables/neutron-common.xml116(td) +msgid "(IntOpt) How many times Neutron will retry MAC generation" +msgstr "" + +#: ./doc/common/tables/neutron-common.xml119(td) +msgid "max_dns_nameservers = 5" +msgstr "" + +#: ./doc/common/tables/neutron-common.xml120(td) +msgid "(IntOpt) Maximum number of DNS nameservers" +msgstr "" + +#: ./doc/common/tables/neutron-common.xml123(td) +msgid "max_fixed_ips_per_port = 5" +msgstr "" + +#: ./doc/common/tables/neutron-common.xml124(td) +msgid "(IntOpt) Maximum number of fixed ips per port" +msgstr "" + +#: ./doc/common/tables/neutron-common.xml127(td) +msgid "max_subnet_host_routes = 20" +msgstr "" + +#: ./doc/common/tables/neutron-common.xml128(td) +msgid "(IntOpt) Maximum number of host routes per subnet" +msgstr "" + +#: ./doc/common/tables/neutron-common.xml131(td) +msgid "meta_flavor_driver_mappings = None" +msgstr "" + +#: ./doc/common/tables/neutron-common.xml132(td) +msgid "(StrOpt) Mapping between flavor and LinuxInterfaceDriver" +msgstr "" + +#: ./doc/common/tables/neutron-common.xml135(td) +#: ./doc/common/tables/nova-network.xml170(td) +msgid "network_device_mtu = None" +msgstr "" + +#: ./doc/common/tables/neutron-common.xml136(td) +msgid "(IntOpt) MTU setting for device." +msgstr "" + +#: ./doc/common/tables/neutron-common.xml139(td) +#: ./doc/common/tables/neutron-openvswitch.xml19(td) +#: ./doc/common/tables/neutron-hyperv.xml19(td) +msgid "network_vlan_ranges =" +msgstr "" + +#: ./doc/common/tables/neutron-common.xml140(td) +#: ./doc/common/tables/neutron-openvswitch.xml20(td) +#: ./doc/common/tables/neutron-hyperv.xml20(td) +msgid "" +"(ListOpt) List of <physical_network>:<vlan_min>:<vlan_max>" +" or <physical_network>" +msgstr "" + +#: ./doc/common/tables/neutron-common.xml143(td) +msgid "ovs_integration_bridge = br-int" +msgstr "" + +#: ./doc/common/tables/neutron-common.xml144(td) +msgid "(StrOpt) Name of Open vSwitch bridge to use" +msgstr "" + +#: ./doc/common/tables/neutron-common.xml147(td) +msgid "ovs_use_veth = False" +msgstr "" + +#: ./doc/common/tables/neutron-common.xml148(td) +msgid "(BoolOpt) Uses veth for an interface or not" +msgstr "" + +#: ./doc/common/tables/neutron-common.xml151(td) +msgid "periodic_fuzzy_delay = 5" +msgstr "" + +#: ./doc/common/tables/neutron-common.xml152(td) +msgid "" +"(IntOpt) Range of seconds to randomly delay when starting the periodic task " +"scheduler to reduce stampeding. (Disable by setting to 0)" +msgstr "" + +#: ./doc/common/tables/neutron-common.xml155(td) +msgid "periodic_interval = 40" +msgstr "" + +#: ./doc/common/tables/neutron-common.xml156(td) +msgid "(IntOpt) Seconds between running periodic tasks" +msgstr "" + +#: ./doc/common/tables/neutron-common.xml159(td) +#: ./doc/common/tables/neutron-common.xml163(td) +#: ./doc/common/tables/cinder-common.xml166(td) +msgid "root_helper = sudo" +msgstr "" + +#: ./doc/common/tables/neutron-common.xml160(td) +#: ./doc/common/tables/neutron-common.xml164(td) +msgid "(StrOpt) Root helper application." +msgstr "" + +#: ./doc/common/tables/neutron-common.xml167(td) +msgid "state_path = /var/lib/neutron" +msgstr "" + +#: ./doc/common/tables/neutron-common.xml168(td) +msgid "" +"(StrOpt) Where to store Neutron state files. This directory must be writable" +" by the agent." +msgstr "" + +#: ./doc/common/tables/swift-object-server-object-auditor.xml7(literal) +msgid "[object-auditor]" +msgstr "" + +#: ./doc/common/tables/swift-object-server-object-auditor.xml7(literal) +#: ./doc/common/tables/swift-object-server-object-updater.xml7(literal) +#: ./doc/common/tables/swift-object-server-pipeline-main.xml7(literal) +#: ./doc/common/tables/swift-object-server-DEFAULT.xml7(literal) +#: ./doc/common/tables/swift-object-server-filter-recon.xml7(literal) +#: ./doc/common/tables/swift-object-server-object-replicator.xml7(literal) +#: ./doc/common/tables/swift-object-server-app-object-server.xml7(literal) +#: ./doc/common/tables/swift-object-server-filter-healthcheck.xml7(literal) +msgid "object-server.conf-sample" +msgstr "" + +#: ./doc/common/tables/swift-object-server-object-auditor.xml18(td) +msgid "log_name = object-auditor" +msgstr "" + +#: ./doc/common/tables/swift-object-server-object-auditor.xml30(td) +msgid "files_per_second = 20" +msgstr "" + +#: ./doc/common/tables/swift-object-server-object-auditor.xml30(td) +msgid "" +"Maximum files audited per second. Should be tuned according to individual " +"system specs. 0 is unlimited." +msgstr "" + +#: ./doc/common/tables/swift-object-server-object-auditor.xml33(td) +msgid "bytes_per_second = 10000000" +msgstr "" + +#: ./doc/common/tables/swift-object-server-object-auditor.xml33(td) +msgid "" +"Maximum bytes audited per second. Should be tuned according to individual " +"system specs. 0 is unlimited. mounted to prevent accidentally writing to the" +" root device process simultaneously (it will actually accept(2) N + 1). " +"Setting this to one (1) will only handle one request at a time, without " +"accepting another request concurrently. By increasing the number of workers " +"to a much higher value, one can reduce the impact of slow file system " +"operations in one request from negatively impacting other requests. " +"underlying filesystem does not support it. to setup custom log handlers. " +"bytes you'd like fallocate to reserve, whether there is space for the given " +"file size or not. This is useful for systems that behave badly when they " +"completely run out of space; you can make the services pretend they're out " +"of space early. container server. For most cases, this should be " +"`egg:swift#container`." +msgstr "" + +#: ./doc/common/tables/swift-object-server-object-auditor.xml36(td) +msgid "log_time = 3600" +msgstr "" + +#: ./doc/common/tables/swift-object-server-object-auditor.xml36(td) +msgid "Frequency of status logs in seconds." +msgstr "" + +#: ./doc/common/tables/swift-object-server-object-auditor.xml39(td) +msgid "zero_byte_files_per_second = 50" +msgstr "" + +#: ./doc/common/tables/swift-object-server-object-auditor.xml39(td) +msgid "Maximum zero byte files audited per second." +msgstr "" + +#: ./doc/common/tables/swift-object-server-object-auditor.xml45(td) +msgid "object_size_stats =" +msgstr "" + +#: ./doc/common/tables/neutron-openvswitch_agent.xml8(caption) +msgid "Description of configuration options for openvswitch_agent" +msgstr "" + +#: ./doc/common/tables/neutron-openvswitch_agent.xml19(td) +#: ./doc/common/tables/neutron-openvswitch_agent.xml23(td) +msgid "bridge_mappings =" +msgstr "" + +#: ./doc/common/tables/neutron-openvswitch_agent.xml20(td) +msgid "(StrOpt) N1K Bridge Mappings" +msgstr "" + +#: ./doc/common/tables/neutron-openvswitch_agent.xml24(td) +msgid "(ListOpt) List of <physical_network>:<bridge>" +msgstr "" + +#: ./doc/common/tables/neutron-openvswitch_agent.xml27(td) +msgid "enable_tunneling = True" +msgstr "" + +#: ./doc/common/tables/neutron-openvswitch_agent.xml28(td) +msgid "(BoolOpt) N1K Enable Tunneling" +msgstr "" + +#: ./doc/common/tables/neutron-openvswitch_agent.xml31(td) +msgid "enable_tunneling = False" +msgstr "" + +#: ./doc/common/tables/neutron-openvswitch_agent.xml32(td) +msgid "(BoolOpt) Enable tunneling support" +msgstr "" + +#: ./doc/common/tables/neutron-openvswitch_agent.xml35(td) +msgid "int_peer_patch_port = patch-tun" +msgstr "" + +#: ./doc/common/tables/neutron-openvswitch_agent.xml36(td) +msgid "(StrOpt) Peer patch port in integration bridge for tunnel bridge" +msgstr "" + +#: ./doc/common/tables/neutron-openvswitch_agent.xml39(td) +#: ./doc/common/tables/neutron-openvswitch_agent.xml43(td) +#: ./doc/common/tables/nova-vmware.xml46(td) +msgid "integration_bridge = br-int" +msgstr "" + +#: ./doc/common/tables/neutron-openvswitch_agent.xml40(td) +msgid "(StrOpt) N1K Integration Bridge" +msgstr "" + +#: ./doc/common/tables/neutron-openvswitch_agent.xml44(td) +msgid "(StrOpt) Integration bridge to use" +msgstr "" + +#: ./doc/common/tables/neutron-openvswitch_agent.xml47(td) +#: ./doc/common/tables/neutron-linuxbridge_agent.xml23(td) +msgid "l2_population = False" +msgstr "" + +#: ./doc/common/tables/neutron-openvswitch_agent.xml48(td) +msgid "" +"(BoolOpt) Use ml2 l2population mechanism driver to learn remote mac and IPs " +"and improve tunnel scalability" +msgstr "" + +#: ./doc/common/tables/neutron-openvswitch_agent.xml51(td) +#: ./doc/common/tables/neutron-openvswitch_agent.xml59(td) +msgid "local_ip =" +msgstr "" + +#: ./doc/common/tables/neutron-openvswitch_agent.xml52(td) +msgid "(StrOpt) Local IP address of the VXLAN endpoints." +msgstr "" + +#: ./doc/common/tables/neutron-openvswitch_agent.xml55(td) +msgid "local_ip = 10.0.0.3" +msgstr "" + +#: ./doc/common/tables/neutron-openvswitch_agent.xml56(td) +msgid "(StrOpt) N1K Local IP" +msgstr "" + +#: ./doc/common/tables/neutron-openvswitch_agent.xml60(td) +msgid "(StrOpt) Local IP address of GRE tunnel endpoints." +msgstr "" + +#: ./doc/common/tables/neutron-openvswitch_agent.xml63(td) +msgid "minimize_polling = True" +msgstr "" + +#: ./doc/common/tables/neutron-openvswitch_agent.xml64(td) +msgid "(BoolOpt) Minimize polling by monitoring ovsdb for interface changes." +msgstr "" + +#: ./doc/common/tables/neutron-openvswitch_agent.xml67(td) +msgid "ovsdb_monitor_respawn_interval = 30" +msgstr "" + +#: ./doc/common/tables/neutron-openvswitch_agent.xml68(td) +msgid "" +"(IntOpt) The number of seconds to wait before respawning the ovsdb monitor " +"after losing communication with it" +msgstr "" + +#: ./doc/common/tables/neutron-openvswitch_agent.xml71(td) +#: ./doc/common/tables/neutron-linuxbridge.xml19(td) +#: ./doc/common/tables/neutron-hyperv.xml23(td) +msgid "tenant_network_type = local" +msgstr "" + +#: ./doc/common/tables/neutron-openvswitch_agent.xml72(td) +msgid "" +"(StrOpt) Network type for tenant networks (local, vlan, gre, vxlan, or none)" +msgstr "" + +#: ./doc/common/tables/neutron-openvswitch_agent.xml75(td) +msgid "tun_peer_patch_port = patch-int" +msgstr "" + +#: ./doc/common/tables/neutron-openvswitch_agent.xml76(td) +msgid "(StrOpt) Peer patch port in tunnel bridge for integration bridge" +msgstr "" + +#: ./doc/common/tables/neutron-openvswitch_agent.xml79(td) +#: ./doc/common/tables/neutron-openvswitch_agent.xml83(td) +msgid "tunnel_bridge = br-tun" +msgstr "" + +#: ./doc/common/tables/neutron-openvswitch_agent.xml80(td) +msgid "(StrOpt) N1K Tunnel Bridge" +msgstr "" + +#: ./doc/common/tables/neutron-openvswitch_agent.xml84(td) +msgid "(StrOpt) Tunnel bridge to use" +msgstr "" + +#: ./doc/common/tables/neutron-openvswitch_agent.xml87(td) +#: ./doc/common/tables/neutron-openvswitch_agent.xml91(td) +msgid "tunnel_id_ranges =" +msgstr "" + +#: ./doc/common/tables/neutron-openvswitch_agent.xml88(td) +msgid "(ListOpt) List of <tun_min>:<tun_max>" +msgstr "" + +#: ./doc/common/tables/neutron-openvswitch_agent.xml92(td) +msgid "" +"(ListOpt) Comma-separated list of <tun_min>:<tun_max> tuples " +"enumerating ranges of GRE tunnel IDs that are available for tenant network " +"allocation" +msgstr "" + +#: ./doc/common/tables/neutron-openvswitch_agent.xml95(td) +msgid "tunnel_type =" +msgstr "" + +#: ./doc/common/tables/neutron-openvswitch_agent.xml96(td) +msgid "" +"(StrOpt) The type of tunnels to use when utilizing tunnels, either 'gre' or " +"'vxlan'" +msgstr "" + +#: ./doc/common/tables/neutron-openvswitch_agent.xml99(td) +msgid "tunnel_types =" +msgstr "" + +#: ./doc/common/tables/neutron-openvswitch_agent.xml100(td) +msgid "(ListOpt) Network types supported by the agent (gre and/or vxlan)" +msgstr "" + +#: ./doc/common/tables/neutron-openvswitch_agent.xml103(td) +msgid "veth_mtu = None" +msgstr "" + +#: ./doc/common/tables/neutron-openvswitch_agent.xml104(td) +msgid "(IntOpt) MTU size of veth interfaces" +msgstr "" + +#: ./doc/common/tables/neutron-openvswitch_agent.xml107(td) +msgid "vxlan_udp_port = 4789" +msgstr "" + +#: ./doc/common/tables/neutron-openvswitch_agent.xml108(td) +msgid "(IntOpt) The UDP port to use for VXLAN tunnels." +msgstr "" + +#: ./doc/common/tables/cinder-compute.xml8(caption) +#: ./doc/common/tables/nova-compute.xml8(caption) +msgid "Description of configuration options for compute" +msgstr "" + +#: ./doc/common/tables/cinder-compute.xml22(td) +msgid "nova_api_insecure = False" +msgstr "" + +#: ./doc/common/tables/cinder-compute.xml23(td) +msgid "(BoolOpt) Allow to perform insecure SSL requests to nova" +msgstr "" + +#: ./doc/common/tables/cinder-compute.xml26(td) +msgid "nova_ca_certificates_file = None" +msgstr "" + +#: ./doc/common/tables/cinder-compute.xml27(td) +msgid "" +"(StrOpt) Location of ca certificates file to use for nova client requests." +msgstr "" + +#: ./doc/common/tables/cinder-compute.xml30(td) +msgid "nova_catalog_admin_info = compute:nova:adminURL" +msgstr "" + +#: ./doc/common/tables/cinder-compute.xml31(td) +msgid "(StrOpt) Same as nova_catalog_info, but for admin endpoint." +msgstr "" + +#: ./doc/common/tables/cinder-compute.xml34(td) +msgid "nova_catalog_info = compute:nova:publicURL" +msgstr "" + +#: ./doc/common/tables/cinder-compute.xml35(td) +msgid "" +"(StrOpt) Info to match when looking for nova in the service catalog. Format " +"is : separated values of the form: " +"<service_type>:<service_name>:<endpoint_type>" +msgstr "" + +#: ./doc/common/tables/cinder-compute.xml38(td) +msgid "nova_endpoint_admin_template = None" +msgstr "" + +#: ./doc/common/tables/cinder-compute.xml39(td) +msgid "(StrOpt) Same as nova_endpoint_template, but for admin endpoint." +msgstr "" + +#: ./doc/common/tables/cinder-compute.xml42(td) +msgid "nova_endpoint_template = None" +msgstr "" + +#: ./doc/common/tables/cinder-compute.xml43(td) +msgid "" +"(StrOpt) Override service catalog lookup with template for nova endpoint " +"e.g. http://localhost:8774/v2/%(tenant_id)s" +msgstr "" + +#: ./doc/common/tables/cinder-lvm.xml8(caption) +msgid "Description of configuration options for lvm" +msgstr "" + +#: ./doc/common/tables/cinder-lvm.xml22(td) +msgid "lvm_mirrors = 0" +msgstr "" + +#: ./doc/common/tables/cinder-lvm.xml23(td) +msgid "" +"(IntOpt) If set, create lvms with multiple mirrors. Note that this requires " +"lvm_mirrors + 2 pvs with available space" +msgstr "" + +#: ./doc/common/tables/cinder-lvm.xml26(td) +msgid "lvm_type = default" +msgstr "" + +#: ./doc/common/tables/cinder-lvm.xml27(td) +msgid "(StrOpt) Type of LVM volumes to deploy; (default or thin)" +msgstr "" + +#: ./doc/common/tables/cinder-lvm.xml30(td) +msgid "volume_group = cinder-volumes" +msgstr "" + +#: ./doc/common/tables/cinder-lvm.xml31(td) +msgid "(StrOpt) Name for the VG that will contain exported volumes" +msgstr "" + +#: ./doc/common/tables/cinder-storage_nfs.xml8(caption) +msgid "Description of configuration options for storage_nfs" +msgstr "" + +#: ./doc/common/tables/cinder-storage_nfs.xml23(td) +msgid "" +"(StrOpt) Mount options passed to the nfs client. See section of the nfs man " +"page for details." +msgstr "" + +#: ./doc/common/tables/cinder-storage_nfs.xml27(td) +msgid "(StrOpt) Base dir containing mount points for nfs shares." +msgstr "" + +#: ./doc/common/tables/cinder-storage_nfs.xml30(td) +msgid "nfs_oversub_ratio = 1.0" +msgstr "" + +#: ./doc/common/tables/cinder-storage_nfs.xml31(td) +#: ./doc/common/tables/cinder-nexenta_nfs.xml35(td) +msgid "" +"(FloatOpt) This will compare the allocated to available space on the volume " +"destination. If the ratio exceeds this number, the destination will no " +"longer be valid." +msgstr "" + +#: ./doc/common/tables/cinder-storage_nfs.xml34(td) +msgid "nfs_shares_config = /etc/cinder/nfs_shares" +msgstr "" + +#: ./doc/common/tables/cinder-storage_nfs.xml35(td) +#: ./doc/common/tables/cinder-nexenta_nfs.xml39(td) +msgid "(StrOpt) File with the list of available nfs shares" +msgstr "" + +#: ./doc/common/tables/cinder-storage_nfs.xml38(td) +msgid "nfs_sparsed_volumes = True" +msgstr "" + +#: ./doc/common/tables/cinder-storage_nfs.xml42(td) +msgid "nfs_used_ratio = 0.95" +msgstr "" + +#: ./doc/common/tables/cinder-storage_nfs.xml43(td) +#: ./doc/common/tables/cinder-nexenta_nfs.xml43(td) +msgid "" +"(FloatOpt) Percent of ACTUAL usage of the underlying volume before no new " +"volumes can be allocated to the volume destination." +msgstr "" + +#: ./doc/common/tables/neutron-plumgrid.xml8(caption) +msgid "Description of configuration options for plumgrid" +msgstr "" + +#: ./doc/common/tables/neutron-plumgrid.xml19(td) +msgid "director_server = localhost" +msgstr "" + +#: ./doc/common/tables/neutron-plumgrid.xml20(td) +msgid "(StrOpt) PLUMgrid Director server to connect to" +msgstr "" + +#: ./doc/common/tables/neutron-plumgrid.xml23(td) +msgid "director_server_port = 8080" +msgstr "" + +#: ./doc/common/tables/neutron-plumgrid.xml24(td) +msgid "(StrOpt) PLUMgrid Director server port to connect to" +msgstr "" + +#: ./doc/common/tables/neutron-plumgrid.xml27(td) +msgid "password = password" +msgstr "" + +#: ./doc/common/tables/neutron-plumgrid.xml28(td) +msgid "(StrOpt) PLUMgrid Director admin password" +msgstr "" + +#: ./doc/common/tables/neutron-plumgrid.xml31(td) +msgid "servertimeout = 5" +msgstr "" + +#: ./doc/common/tables/neutron-plumgrid.xml32(td) +msgid "(IntOpt) PLUMgrid Director server timeout" +msgstr "" + +#: ./doc/common/tables/neutron-plumgrid.xml35(td) +msgid "username = username" +msgstr "" + +#: ./doc/common/tables/neutron-plumgrid.xml36(td) +msgid "(StrOpt) PLUMgrid Director admin username" +msgstr "" + +#: ./doc/common/tables/nova-hypervisor.xml8(caption) +msgid "Description of configuration options for hypervisor" +msgstr "" + +#: ./doc/common/tables/nova-hypervisor.xml22(td) +msgid "default_ephemeral_format = None" +msgstr "" + +#: ./doc/common/tables/nova-hypervisor.xml23(td) +msgid "" +"(StrOpt) The default format an ephemeral_volume will be formatted with on " +"creation." +msgstr "" + +#: ./doc/common/tables/nova-hypervisor.xml26(td) +msgid "force_raw_images = True" +msgstr "" + +#: ./doc/common/tables/nova-hypervisor.xml27(td) +msgid "(BoolOpt) Force backing images to raw format" +msgstr "" + +#: ./doc/common/tables/nova-hypervisor.xml30(td) +msgid "preallocate_images = none" +msgstr "" + +#: ./doc/common/tables/nova-hypervisor.xml31(td) +msgid "" +"(StrOpt) VM image preallocation mode: \"none\" => no storage provisioning" +" is done up front, \"space\" => storage is fully allocated at instance " +"start" +msgstr "" + +#: ./doc/common/tables/nova-hypervisor.xml34(td) +msgid "rescue_timeout = 0" +msgstr "" + +#: ./doc/common/tables/nova-hypervisor.xml35(td) +msgid "" +"(IntOpt) Automatically unrescue an instance after N seconds. Set to 0 to " +"disable." +msgstr "" + +#: ./doc/common/tables/nova-hypervisor.xml38(td) +msgid "timeout_nbd = 10" +msgstr "" + +#: ./doc/common/tables/nova-hypervisor.xml39(td) +msgid "(IntOpt) time to wait for a NBD device coming up" +msgstr "" + +#: ./doc/common/tables/nova-hypervisor.xml42(td) +msgid "use_cow_images = True" +msgstr "" + +#: ./doc/common/tables/nova-hypervisor.xml43(td) +msgid "(BoolOpt) Whether to use cow images" +msgstr "" + +#: ./doc/common/tables/nova-hypervisor.xml46(td) +msgid "vcpu_pin_set = None" +msgstr "" + +#: ./doc/common/tables/nova-hypervisor.xml47(td) +msgid "(StrOpt) Which pcpus can be used by vcpus of instance e.g: \"4-12,^8,15\"" +msgstr "" + +#: ./doc/common/tables/nova-hypervisor.xml50(td) +msgid "virt_mkfs = []" +msgstr "" + +#: ./doc/common/tables/nova-hypervisor.xml51(td) +msgid "" +"(MultiStrOpt) mkfs commands for ephemeral device. The format is " +"<os_type>=<mkfs command>" +msgstr "" + +#: ./doc/common/tables/nova-hypervisor.xml57(td) +msgid "" +"block_migration_flag = VIR_MIGRATE_UNDEFINE_SOURCE, VIR_MIGRATE_PEER2PEER, " +"VIR_MIGRATE_NON_SHARED_INC" +msgstr "" + +#: ./doc/common/tables/nova-hypervisor.xml58(td) +msgid "(StrOpt) Migration flags to be set for block migration" +msgstr "" + +#: ./doc/common/tables/nova-hypervisor.xml61(td) +msgid "disk_cachemodes =" +msgstr "" + +#: ./doc/common/tables/nova-hypervisor.xml62(td) +msgid "" +"(ListOpt) Specific cachemodes to use for different disk types e.g: " +"file=directsync,block=none" +msgstr "" + +#: ./doc/common/tables/nova-hypervisor.xml65(td) +msgid "images_rbd_ceph_conf =" +msgstr "" + +#: ./doc/common/tables/nova-hypervisor.xml66(td) +#: ./doc/common/tables/cinder-storage_ceph.xml23(td) +msgid "(StrOpt) path to the ceph configuration file to use" +msgstr "" + +#: ./doc/common/tables/nova-hypervisor.xml69(td) +msgid "images_rbd_pool = rbd" +msgstr "" + +#: ./doc/common/tables/nova-hypervisor.xml70(td) +#: ./doc/common/tables/cinder-storage_ceph.xml35(td) +msgid "(StrOpt) the RADOS pool in which rbd volumes are stored" +msgstr "" + +#: ./doc/common/tables/nova-hypervisor.xml73(td) +msgid "images_type = default" +msgstr "" + +#: ./doc/common/tables/nova-hypervisor.xml74(td) +msgid "" +"(StrOpt) VM Images format. Acceptable values are: raw, qcow2, lvm,rbd, " +"default. If default is specified, then use_cow_images flag is used instead " +"of this one." +msgstr "" + +#: ./doc/common/tables/nova-hypervisor.xml77(td) +msgid "images_volume_group = None" +msgstr "" + +#: ./doc/common/tables/nova-hypervisor.xml78(td) +msgid "" +"(StrOpt) LVM Volume Group that is used for VM images, when you specify " +"images_type=lvm." +msgstr "" + +#: ./doc/common/tables/nova-hypervisor.xml81(td) +msgid "inject_key = True" +msgstr "" + +#: ./doc/common/tables/nova-hypervisor.xml82(td) +msgid "(BoolOpt) Inject the ssh public key at boot time" +msgstr "" + +#: ./doc/common/tables/nova-hypervisor.xml85(td) +msgid "inject_partition = 1" +msgstr "" + +#: ./doc/common/tables/nova-hypervisor.xml86(td) +msgid "" +"(IntOpt) The partition to inject to : -2 => disable, -1 => inspect " +"(libguestfs only), 0 => not partitioned, >0 => partition number" +msgstr "" + +#: ./doc/common/tables/nova-hypervisor.xml89(td) +msgid "inject_password = False" +msgstr "" + +#: ./doc/common/tables/nova-hypervisor.xml90(td) +msgid "(BoolOpt) Inject the admin password at boot time, without an agent." +msgstr "" + +#: ./doc/common/tables/nova-hypervisor.xml93(td) +msgid "iscsi_use_multipath = False" +msgstr "" + +#: ./doc/common/tables/nova-hypervisor.xml94(td) +msgid "(BoolOpt) use multipath connection of the iSCSI volume" +msgstr "" + +#: ./doc/common/tables/nova-hypervisor.xml97(td) +msgid "iser_use_multipath = False" +msgstr "" + +#: ./doc/common/tables/nova-hypervisor.xml98(td) +msgid "(BoolOpt) use multipath connection of the iSER volume" +msgstr "" + +#: ./doc/common/tables/nova-hypervisor.xml101(td) +msgid "lvm_snapshot_size = 1000" +msgstr "" + +#: ./doc/common/tables/nova-hypervisor.xml102(td) +msgid "" +"(IntOpt) The amount of storage (in megabytes) to allocate for LVM snapshot " +"copy-on-write blocks." +msgstr "" + +#: ./doc/common/tables/nova-hypervisor.xml105(td) +msgid "rescue_image_id = None" +msgstr "" + +#: ./doc/common/tables/nova-hypervisor.xml106(td) +msgid "(StrOpt) Rescue ami image" +msgstr "" + +#: ./doc/common/tables/nova-hypervisor.xml109(td) +msgid "rescue_kernel_id = None" +msgstr "" + +#: ./doc/common/tables/nova-hypervisor.xml110(td) +msgid "(StrOpt) Rescue aki image" +msgstr "" + +#: ./doc/common/tables/nova-hypervisor.xml113(td) +msgid "rescue_ramdisk_id = None" +msgstr "" + +#: ./doc/common/tables/nova-hypervisor.xml114(td) +msgid "(StrOpt) Rescue ari image" +msgstr "" + +#: ./doc/common/tables/nova-hypervisor.xml117(td) +msgid "snapshot_compression = False" +msgstr "" + +#: ./doc/common/tables/nova-hypervisor.xml118(td) +msgid "" +"(BoolOpt) Compress snapshot images when possible. This currently applies " +"exclusively to qcow2 images" +msgstr "" + +#: ./doc/common/tables/nova-hypervisor.xml121(td) +msgid "snapshot_image_format = None" +msgstr "" + +#: ./doc/common/tables/nova-hypervisor.xml122(td) +msgid "" +"(StrOpt) Snapshot image format (valid options are : raw, qcow2, vmdk, vdi). " +"Defaults to same as source image" +msgstr "" + +#: ./doc/common/tables/nova-hypervisor.xml125(td) +msgid "sparse_logical_volumes = False" +msgstr "" + +#: ./doc/common/tables/nova-hypervisor.xml126(td) +msgid "" +"(BoolOpt) Create sparse logical volumes (with virtualsize) if this flag is " +"set to True." +msgstr "" + +#: ./doc/common/tables/nova-hypervisor.xml129(td) +msgid "use_usb_tablet = True" +msgstr "" + +#: ./doc/common/tables/nova-hypervisor.xml130(td) +msgid "(BoolOpt) Sync virtual and real mouse cursors in Windows VMs" +msgstr "" + +#: ./doc/common/tables/nova-hypervisor.xml133(td) +msgid "use_virtio_for_bridges = True" +msgstr "" + +#: ./doc/common/tables/nova-hypervisor.xml134(td) +msgid "(BoolOpt) Use virtio for bridge interfaces with KVM/QEMU" +msgstr "" + +#: ./doc/common/tables/swift-proxy-server-filter-tempurl.xml7(literal) +msgid "[filter:tempurl]" +msgstr "" + +#: ./doc/common/tables/swift-proxy-server-filter-tempurl.xml18(td) +msgid "use = egg:swift#tempurl" +msgstr "" + +#: ./doc/common/tables/swift-proxy-server-filter-tempurl.xml18(td) +msgid "" +"Entry point of paste.deploy in the server. You should not ever need to " +"change this." +msgstr "" + +#: ./doc/common/tables/swift-proxy-server-filter-tempurl.xml21(td) +msgid "methods = GET HEAD PUT" +msgstr "" + +#: ./doc/common/tables/swift-proxy-server-filter-tempurl.xml21(td) +msgid "HTTP methods allowed with Temporary URLs" +msgstr "" + +#: ./doc/common/tables/swift-proxy-server-filter-tempurl.xml24(td) +msgid "incoming_remove_headers = x-timestamp" +msgstr "" + +#: ./doc/common/tables/swift-proxy-server-filter-tempurl.xml24(td) +msgid "" +"Headers to remove from incoming requests. Simply a whitespace delimited list" +" of header names and names can optionally end with '*' to indicate a prefix " +"match." +msgstr "" + +#: ./doc/common/tables/swift-proxy-server-filter-tempurl.xml28(td) +msgid "incoming_allow_headers =" +msgstr "" + +#: ./doc/common/tables/swift-proxy-server-filter-tempurl.xml29(td) +msgid "" +"Headers allowed as exceptions to incoming_remove_headers. Simply a " +"whitespace delimited list of header names and names can optionally end with " +"'*' to indicate a prefix match." +msgstr "" + +#: ./doc/common/tables/swift-proxy-server-filter-tempurl.xml34(td) +msgid "outgoing_remove_headers = x-object-meta-*" +msgstr "" + +#: ./doc/common/tables/swift-proxy-server-filter-tempurl.xml35(td) +msgid "" +"Headers to remove from outgoing responses. Simply a whitespace delimited " +"list of header names and names can optionally end with '*' to indicate a " +"prefix match." +msgstr "" + +#: ./doc/common/tables/swift-proxy-server-filter-tempurl.xml40(td) +msgid "outgoing_allow_headers = x-object-meta-public-*" +msgstr "" + +#: ./doc/common/tables/swift-proxy-server-filter-tempurl.xml40(td) +msgid "" +"Headers allowed as exceptions to outgoing_allow_headers. Simply a whitespace" +" delimited list of header names and names can optionally end with '*' to " +"indicate a prefix match." +msgstr "" + +#: ./doc/common/tables/cinder-quota.xml8(caption) +#: ./doc/common/tables/nova-quota.xml8(caption) +msgid "Description of configuration options for quota" +msgstr "" + +#: ./doc/common/tables/cinder-quota.xml22(td) +#: ./doc/common/tables/nova-policy.xml34(td) +msgid "max_age = 0" +msgstr "" + +#: ./doc/common/tables/cinder-quota.xml23(td) +#: ./doc/common/tables/nova-policy.xml35(td) +msgid "(IntOpt) number of seconds between subsequent usage refreshes" +msgstr "" + +#: ./doc/common/tables/cinder-quota.xml26(td) +msgid "quota_driver = cinder.quota.DbQuotaDriver" +msgstr "" + +#: ./doc/common/tables/cinder-quota.xml27(td) +#: ./doc/common/tables/nova-quota.xml35(td) +msgid "(StrOpt) default driver to use for quota checks" +msgstr "" + +#: ./doc/common/tables/cinder-quota.xml30(td) +msgid "quota_gigabytes = 1000" +msgstr "" + +#: ./doc/common/tables/cinder-quota.xml31(td) +msgid "" +"(IntOpt) number of volume gigabytes (snapshots are also included) allowed " +"per project" +msgstr "" + +#: ./doc/common/tables/cinder-quota.xml34(td) +msgid "quota_snapshots = 10" +msgstr "" + +#: ./doc/common/tables/cinder-quota.xml35(td) +msgid "(IntOpt) number of volume snapshots allowed per project" +msgstr "" + +#: ./doc/common/tables/cinder-quota.xml38(td) +msgid "quota_volumes = 10" +msgstr "" + +#: ./doc/common/tables/cinder-quota.xml39(td) +msgid "(IntOpt) number of volumes allowed per project" +msgstr "" + +#: ./doc/common/tables/cinder-quota.xml42(td) +#: ./doc/common/tables/nova-policy.xml66(td) +msgid "reservation_expire = 86400" +msgstr "" + +#: ./doc/common/tables/cinder-quota.xml43(td) +#: ./doc/common/tables/nova-policy.xml67(td) +msgid "(IntOpt) number of seconds until a reservation expires" +msgstr "" + +#: ./doc/common/tables/cinder-quota.xml46(td) +msgid "use_default_quota_class = True" +msgstr "" + +#: ./doc/common/tables/cinder-quota.xml47(td) +msgid "(BoolOpt) whether to use default quota class for default quota" +msgstr "" + +#: ./doc/common/tables/swift-proxy-server-filter-healthcheck.xml7(literal) +#: ./doc/common/tables/swift-account-server-filter-healthcheck.xml7(literal) +#: ./doc/common/tables/swift-container-server-filter-healthcheck.xml7(literal) +#: ./doc/common/tables/swift-object-server-filter-healthcheck.xml7(literal) +msgid "[filter:healthcheck]" +msgstr "" + +#: ./doc/common/tables/swift-proxy-server-filter-healthcheck.xml18(td) +#: ./doc/common/tables/swift-account-server-filter-healthcheck.xml18(td) +#: ./doc/common/tables/swift-container-server-filter-healthcheck.xml18(td) +#: ./doc/common/tables/swift-object-server-filter-healthcheck.xml18(td) +msgid "use = egg:swift#healthcheck" +msgstr "" + +#: ./doc/common/tables/swift-proxy-server-filter-healthcheck.xml21(td) +#: ./doc/common/tables/swift-account-server-filter-healthcheck.xml21(td) +#: ./doc/common/tables/swift-container-server-filter-healthcheck.xml21(td) +#: ./doc/common/tables/swift-object-server-filter-healthcheck.xml21(td) +msgid "disable_path =" +msgstr "" + +#: ./doc/common/tables/nova-console.xml8(caption) +msgid "Description of configuration options for console" +msgstr "" + +#: ./doc/common/tables/nova-console.xml22(td) +msgid "console_public_hostname = oslo" +msgstr "" + +#: ./doc/common/tables/nova-console.xml23(td) +msgid "(StrOpt) Publicly visible name for this console host" +msgstr "" + +#: ./doc/common/tables/nova-console.xml26(td) +msgid "console_token_ttl = 600" +msgstr "" + +#: ./doc/common/tables/nova-console.xml27(td) +msgid "(IntOpt) How many seconds before deleting tokens" +msgstr "" + +#: ./doc/common/tables/nova-console.xml30(td) +msgid "consoleauth_manager = nova.consoleauth.manager.ConsoleAuthManager" +msgstr "" + +#: ./doc/common/tables/nova-console.xml31(td) +msgid "(StrOpt) Manager for console auth" +msgstr "" + +#: ./doc/common/tables/swift-swift-bench-bench.xml7(literal) +msgid "[bench]" +msgstr "" + +#: ./doc/common/tables/swift-swift-bench-bench.xml7(literal) +msgid "swift-bench.conf-sample" +msgstr "" + +#: ./doc/common/tables/swift-swift-bench-bench.xml18(td) +msgid "auth = http://localhost:8080/auth/v1.0" +msgstr "" + +#: ./doc/common/tables/swift-swift-bench-bench.xml18(td) +msgid "Swift storage accounts and auth tokens will begin with this prefix." +msgstr "" + +#: ./doc/common/tables/swift-swift-bench-bench.xml21(td) +msgid "user = test:tester" +msgstr "" + +#: ./doc/common/tables/swift-swift-bench-bench.xml24(td) +msgid "key = testing" +msgstr "" + +#: ./doc/common/tables/swift-swift-bench-bench.xml27(td) +msgid "auth_version = 1.0" +msgstr "" + +#: ./doc/common/tables/swift-swift-bench-bench.xml27(td) +#: ./doc/common/tables/swift-dispersion-dispersion.xml36(td) +msgid "Indicates which version of auth" +msgstr "" + +#: ./doc/common/tables/swift-swift-bench-bench.xml30(td) +msgid "log-level = INFO" +msgstr "" + +#: ./doc/common/tables/swift-swift-bench-bench.xml33(td) +#: ./doc/common/tables/neutron-ml2_ncs.xml19(td) +msgid "timeout = 10" +msgstr "" + +#: ./doc/common/tables/swift-swift-bench-bench.xml33(td) +msgid "Timeout value sent to rsync --timeout and --contimeout options" +msgstr "" + +#: ./doc/common/tables/swift-swift-bench-bench.xml36(td) +msgid "put_concurrency = 10" +msgstr "" + +#: ./doc/common/tables/swift-swift-bench-bench.xml39(td) +msgid "get_concurrency = 10" +msgstr "" + +#: ./doc/common/tables/swift-swift-bench-bench.xml42(td) +msgid "del_concurrency = 10" +msgstr "" + +#: ./doc/common/tables/swift-swift-bench-bench.xml45(td) +msgid "concurrency =" +msgstr "" + +#: ./doc/common/tables/swift-swift-bench-bench.xml48(td) +msgid "object_sources =" +msgstr "" + +#: ./doc/common/tables/swift-swift-bench-bench.xml51(td) +msgid "lower_object_size = 10" +msgstr "" + +#: ./doc/common/tables/swift-swift-bench-bench.xml54(td) +msgid "upper_object_size = 10" +msgstr "" + +#: ./doc/common/tables/swift-swift-bench-bench.xml57(td) +msgid "object_size = 1" +msgstr "" + +#: ./doc/common/tables/swift-swift-bench-bench.xml60(td) +msgid "num_objects = 1000" +msgstr "" + +#: ./doc/common/tables/swift-swift-bench-bench.xml63(td) +msgid "num_gets = 10000" +msgstr "" + +#: ./doc/common/tables/swift-swift-bench-bench.xml66(td) +msgid "num_containers = 20" +msgstr "" + +#: ./doc/common/tables/swift-swift-bench-bench.xml69(td) +msgid "container_name = (randomly-chosen uuid4)" +msgstr "" + +#: ./doc/common/tables/swift-swift-bench-bench.xml72(td) +msgid "delete = yes" +msgstr "" + +#: ./doc/common/tables/swift-swift-bench-bench.xml75(td) +msgid "use_proxy = yes" +msgstr "" + +#: ./doc/common/tables/swift-swift-bench-bench.xml78(td) +msgid "" +"use_proxy = no, this setting is required and used as the X-Storage-Url when" +msgstr "" + +#: ./doc/common/tables/swift-swift-bench-bench.xml81(td) +msgid "url =" +msgstr "" + +#: ./doc/common/tables/swift-swift-bench-bench.xml84(td) +msgid "account =" +msgstr "" + +#: ./doc/common/tables/swift-swift-bench-bench.xml84(td) +msgid "has generated an error (timeout, not yet found, etc.)" +msgstr "" + +#: ./doc/common/tables/swift-swift-bench-bench.xml87(td) +msgid "use_proxy = no." +msgstr "" + +#: ./doc/common/tables/swift-swift-bench-bench.xml90(td) +msgid "devices = sdb1" +msgstr "" + +#: ./doc/common/tables/nova-common.xml22(td) +msgid "bindir = /usr/local/bin" +msgstr "" + +#: ./doc/common/tables/nova-common.xml23(td) +msgid "(StrOpt) Directory where nova binaries are installed" +msgstr "" + +#: ./doc/common/tables/nova-common.xml26(td) +msgid "compute_topic = compute" +msgstr "" + +#: ./doc/common/tables/nova-common.xml27(td) +msgid "(StrOpt) the topic compute nodes listen on" +msgstr "" + +#: ./doc/common/tables/nova-common.xml30(td) +msgid "console_topic = console" +msgstr "" + +#: ./doc/common/tables/nova-common.xml31(td) +msgid "(StrOpt) the topic console proxy nodes listen on" +msgstr "" + +#: ./doc/common/tables/nova-common.xml34(td) +msgid "consoleauth_topic = consoleauth" +msgstr "" + +#: ./doc/common/tables/nova-common.xml35(td) +msgid "(StrOpt) the topic console auth proxy nodes listen on" +msgstr "" + +#: ./doc/common/tables/nova-common.xml42(td) +#: ./doc/common/tables/cinder-common.xml66(td) +msgid "host = oslo" +msgstr "" + +#: ./doc/common/tables/nova-common.xml43(td) +msgid "" +"(StrOpt) Name of this node. This can be an opaque identifier. It is not " +"necessarily a hostname, FQDN, or IP address. However, the node name must be " +"valid within an AMQP key, and if using ZeroMQ, a valid hostname, FQDN, or IP" +" address" +msgstr "" + +#: ./doc/common/tables/nova-common.xml47(td) +#: ./doc/common/tables/glance-common.xml71(td) +msgid "(StrOpt) Directory to use for lock files." +msgstr "" + +#: ./doc/common/tables/nova-common.xml50(td) +msgid "memcached_servers = None" +msgstr "" + +#: ./doc/common/tables/nova-common.xml51(td) +msgid "(ListOpt) Memcached servers or None for in process cache." +msgstr "" + +#: ./doc/common/tables/nova-common.xml54(td) +#: ./doc/common/tables/cinder-common.xml126(td) +msgid "my_ip = 10.0.0.1" +msgstr "" + +#: ./doc/common/tables/nova-common.xml55(td) +#: ./doc/common/tables/cinder-common.xml127(td) +msgid "(StrOpt) ip address of this host" +msgstr "" + +#: ./doc/common/tables/nova-common.xml58(td) +#: ./doc/common/tables/cinder-rpc.xml74(td) +#: ./doc/common/tables/neutron-notifier.xml27(td) +msgid "notification_driver = []" +msgstr "" + +#: ./doc/common/tables/nova-common.xml59(td) +#: ./doc/common/tables/cinder-rpc.xml75(td) +#: ./doc/common/tables/neutron-notifier.xml28(td) +msgid "(MultiStrOpt) Driver or drivers to handle sending notifications" +msgstr "" + +#: ./doc/common/tables/nova-common.xml62(td) +#: ./doc/common/tables/cinder-rpc.xml78(td) +#: ./doc/common/tables/neutron-notifier.xml31(td) +msgid "notification_topics = notifications" +msgstr "" + +#: ./doc/common/tables/nova-common.xml63(td) +#: ./doc/common/tables/cinder-rpc.xml79(td) +msgid "(ListOpt) AMQP topic used for OpenStack notifications" +msgstr "" + +#: ./doc/common/tables/nova-common.xml66(td) +msgid "notify_api_faults = False" +msgstr "" + +#: ./doc/common/tables/nova-common.xml67(td) +msgid "" +"(BoolOpt) If set, send api.fault notifications on caught exceptions in the " +"API service." +msgstr "" + +#: ./doc/common/tables/nova-common.xml70(td) +msgid "notify_on_state_change = None" +msgstr "" + +#: ./doc/common/tables/nova-common.xml71(td) +msgid "" +"(StrOpt) If set, send compute.instance.update notifications on instance " +"state changes. Valid values are None for no notifications, \"vm_state\" for " +"notifications on VM state changes, or \"vm_and_task_state\" for " +"notifications on VM and task state changes." +msgstr "" + +#: ./doc/common/tables/nova-common.xml74(td) +#: ./doc/common/tables/cinder-common.xml154(td) +msgid "pybasedir = /usr/lib/python/site-packages" +msgstr "" + +#: ./doc/common/tables/nova-common.xml75(td) +msgid "(StrOpt) Directory where the nova python module is installed" +msgstr "" + +#: ./doc/common/tables/nova-common.xml78(td) +#: ./doc/common/tables/cinder-common.xml158(td) +msgid "report_interval = 10" +msgstr "" + +#: ./doc/common/tables/nova-common.xml79(td) +#: ./doc/common/tables/cinder-common.xml159(td) +msgid "(IntOpt) seconds between nodes reporting state to datastore" +msgstr "" + +#: ./doc/common/tables/nova-common.xml82(td) +msgid "rootwrap_config = /etc/nova/rootwrap.conf" +msgstr "" + +#: ./doc/common/tables/nova-common.xml83(td) +#: ./doc/common/tables/cinder-common.xml171(td) +msgid "" +"(StrOpt) Path to the rootwrap configuration file to use for running commands" +" as root" +msgstr "" + +#: ./doc/common/tables/nova-common.xml86(td) +#: ./doc/common/tables/cinder-common.xml178(td) +msgid "service_down_time = 60" +msgstr "" + +#: ./doc/common/tables/nova-common.xml87(td) +#: ./doc/common/tables/cinder-common.xml179(td) +msgid "(IntOpt) maximum time since last check-in for up service" +msgstr "" + +#: ./doc/common/tables/nova-common.xml90(td) +#: ./doc/common/tables/cinder-common.xml202(td) +msgid "state_path = $pybasedir" +msgstr "" + +#: ./doc/common/tables/nova-common.xml91(td) +msgid "(StrOpt) Top-level directory for maintaining nova's state" +msgstr "" + +#: ./doc/common/tables/nova-common.xml94(td) +msgid "tempdir = None" +msgstr "" + +#: ./doc/common/tables/nova-common.xml95(td) +msgid "(StrOpt) Explicitly specify the temporary working directory" +msgstr "" + +#: ./doc/common/tables/swift-object-server-object-updater.xml7(literal) +msgid "[object-updater]" +msgstr "" + +#: ./doc/common/tables/swift-object-server-object-updater.xml18(td) +msgid "log_name = object-updater" +msgstr "" + +#: ./doc/common/tables/swift-object-server-object-updater.xml33(td) +#: ./doc/common/tables/swift-object-server-object-replicator.xml39(td) +#: ./doc/common/tables/swift-object-expirer-object-expirer.xml27(td) +msgid "concurrency = 1" +msgstr "" + +#: ./doc/common/tables/glance-zmq.xml8(caption) +msgid "Description of configuration options for zmq" +msgstr "" + +#: ./doc/common/tables/glance-zmq.xml22(td) +#: ./doc/common/tables/cinder-rpc.xml174(td) +#: ./doc/common/tables/neutron-rpc.xml59(td) +#: ./doc/common/tables/nova-rpc.xml46(td) +msgid "rpc_cast_timeout = 30" +msgstr "" + +#: ./doc/common/tables/glance-zmq.xml23(td) +#: ./doc/common/tables/cinder-rpc.xml175(td) +#: ./doc/common/tables/neutron-rpc.xml60(td) +#: ./doc/common/tables/nova-rpc.xml47(td) +msgid "" +"(IntOpt) Seconds to wait before a cast expires (TTL). Only supported by " +"impl_zmq." +msgstr "" + +#: ./doc/common/tables/glance-zmq.xml26(td) +#: ./doc/common/tables/cinder-rpc.xml190(td) +#: ./doc/common/tables/nova-zeromq.xml22(td) +#: ./doc/common/tables/neutron-zeromq.xml19(td) +msgid "rpc_zmq_bind_address = *" +msgstr "" + +#: ./doc/common/tables/glance-zmq.xml27(td) +#: ./doc/common/tables/cinder-rpc.xml191(td) +#: ./doc/common/tables/nova-zeromq.xml23(td) +#: ./doc/common/tables/neutron-zeromq.xml20(td) +msgid "" +"(StrOpt) ZeroMQ bind address. Should be a wildcard (*), an ethernet " +"interface, or IP. The \"host\" option should point or resolve to this " +"address." +msgstr "" + +#: ./doc/common/tables/glance-zmq.xml30(td) +#: ./doc/common/tables/cinder-rpc.xml194(td) +#: ./doc/common/tables/nova-zeromq.xml26(td) +#: ./doc/common/tables/neutron-zeromq.xml23(td) +msgid "rpc_zmq_contexts = 1" +msgstr "" + +#: ./doc/common/tables/glance-zmq.xml31(td) +#: ./doc/common/tables/cinder-rpc.xml195(td) +#: ./doc/common/tables/nova-zeromq.xml27(td) +#: ./doc/common/tables/neutron-zeromq.xml24(td) +msgid "(IntOpt) Number of ZeroMQ contexts, defaults to 1" +msgstr "" + +#: ./doc/common/tables/glance-zmq.xml34(td) +#: ./doc/common/tables/cinder-rpc.xml198(td) +#: ./doc/common/tables/nova-zeromq.xml30(td) +msgid "rpc_zmq_host = oslo" +msgstr "" + +#: ./doc/common/tables/glance-zmq.xml35(td) +#: ./doc/common/tables/cinder-rpc.xml199(td) +#: ./doc/common/tables/nova-zeromq.xml31(td) +#: ./doc/common/tables/neutron-zeromq.xml28(td) +msgid "" +"(StrOpt) Name of this node. Must be a valid hostname, FQDN, or IP address. " +"Must match \"host\" option, if running Nova." +msgstr "" + +#: ./doc/common/tables/glance-zmq.xml38(td) +#: ./doc/common/tables/cinder-rpc.xml202(td) +#: ./doc/common/tables/nova-zeromq.xml34(td) +#: ./doc/common/tables/neutron-zeromq.xml31(td) +msgid "rpc_zmq_ipc_dir = /var/run/openstack" +msgstr "" + +#: ./doc/common/tables/glance-zmq.xml39(td) +#: ./doc/common/tables/cinder-rpc.xml203(td) +#: ./doc/common/tables/nova-zeromq.xml35(td) +#: ./doc/common/tables/neutron-zeromq.xml32(td) +msgid "(StrOpt) Directory for holding IPC sockets" +msgstr "" + +#: ./doc/common/tables/glance-zmq.xml42(td) +msgid "" +"rpc_zmq_matchmaker = oslo.messaging._drivers.matchmaker.MatchMakerLocalhost" +msgstr "" + +#: ./doc/common/tables/glance-zmq.xml43(td) +#: ./doc/common/tables/cinder-rpc.xml207(td) +#: ./doc/common/tables/nova-zeromq.xml39(td) +#: ./doc/common/tables/neutron-zeromq.xml36(td) +msgid "(StrOpt) MatchMaker driver" +msgstr "" + +#: ./doc/common/tables/glance-zmq.xml46(td) +#: ./doc/common/tables/cinder-rpc.xml210(td) +#: ./doc/common/tables/nova-zeromq.xml42(td) +#: ./doc/common/tables/neutron-zeromq.xml39(td) +msgid "rpc_zmq_port = 9501" +msgstr "" + +#: ./doc/common/tables/glance-zmq.xml47(td) +#: ./doc/common/tables/cinder-rpc.xml211(td) +#: ./doc/common/tables/nova-zeromq.xml43(td) +#: ./doc/common/tables/neutron-zeromq.xml40(td) +msgid "(IntOpt) ZeroMQ receiver listening port" +msgstr "" + +#: ./doc/common/tables/glance-zmq.xml50(td) +#: ./doc/common/tables/cinder-rpc.xml214(td) +#: ./doc/common/tables/nova-zeromq.xml46(td) +#: ./doc/common/tables/neutron-zeromq.xml43(td) +msgid "rpc_zmq_topic_backlog = None" +msgstr "" + +#: ./doc/common/tables/glance-zmq.xml51(td) +#: ./doc/common/tables/cinder-rpc.xml215(td) +#: ./doc/common/tables/nova-zeromq.xml47(td) +#: ./doc/common/tables/neutron-zeromq.xml44(td) +msgid "" +"(IntOpt) Maximum number of ingress messages to locally buffer per topic. " +"Default is unlimited." +msgstr "" + +#: ./doc/common/tables/swift-proxy-server-filter-account-quotas.xml7(literal) +msgid "[filter:account-quotas]" +msgstr "" + +#: ./doc/common/tables/swift-proxy-server-filter-account-quotas.xml18(td) +msgid "use = egg:swift#account_quotas" +msgstr "" + +#: ./doc/common/tables/swift-proxy-server-app-proxy-server.xml7(literal) +#: ./doc/common/tables/swift-object-expirer-app-proxy-server.xml7(literal) +msgid "[app:proxy-server]" +msgstr "" + +#: ./doc/common/tables/swift-proxy-server-app-proxy-server.xml18(td) +#: ./doc/common/tables/swift-object-expirer-app-proxy-server.xml18(td) +msgid "use = egg:swift#proxy" +msgstr "" + +#: ./doc/common/tables/swift-proxy-server-app-proxy-server.xml21(td) +msgid "set log_name = proxy-server" +msgstr "" + +#: ./doc/common/tables/swift-proxy-server-app-proxy-server.xml33(td) +msgid "log_handoffs = true" +msgstr "" + +#: ./doc/common/tables/swift-proxy-server-app-proxy-server.xml36(td) +msgid "recheck_account_existence = 60" +msgstr "" + +#: ./doc/common/tables/swift-proxy-server-app-proxy-server.xml36(td) +msgid "Cache timeout in seconds to send memcached for account existence" +msgstr "" + +#: ./doc/common/tables/swift-proxy-server-app-proxy-server.xml39(td) +msgid "recheck_container_existence = 60" +msgstr "" + +#: ./doc/common/tables/swift-proxy-server-app-proxy-server.xml39(td) +msgid "Cache timeout in seconds to send memcached for container existence" +msgstr "" + +#: ./doc/common/tables/swift-proxy-server-app-proxy-server.xml42(td) +msgid "object_chunk_size = 8192" +msgstr "" + +#: ./doc/common/tables/swift-proxy-server-app-proxy-server.xml42(td) +msgid "Chunk size to read from object servers" +msgstr "" + +#: ./doc/common/tables/swift-proxy-server-app-proxy-server.xml45(td) +msgid "client_chunk_size = 8192" +msgstr "" + +#: ./doc/common/tables/swift-proxy-server-app-proxy-server.xml45(td) +msgid "Chunk size to read from clients" +msgstr "" + +#: ./doc/common/tables/swift-proxy-server-app-proxy-server.xml54(td) +#: ./doc/common/tables/swift-account-server-account-replicator.xml45(td) +msgid "error_suppression_interval = 60" +msgstr "" + +#: ./doc/common/tables/swift-proxy-server-app-proxy-server.xml54(td) +#: ./doc/common/tables/swift-account-server-account-replicator.xml45(td) +msgid "" +"Time in seconds that must elapse since the last error for a node to be " +"considered no longer error limited" +msgstr "" + +#: ./doc/common/tables/swift-proxy-server-app-proxy-server.xml57(td) +#: ./doc/common/tables/swift-account-server-account-replicator.xml48(td) +msgid "error_suppression_limit = 10" +msgstr "" + +#: ./doc/common/tables/swift-proxy-server-app-proxy-server.xml57(td) +#: ./doc/common/tables/swift-account-server-account-replicator.xml48(td) +msgid "Error count to consider a node error limited" +msgstr "" + +#: ./doc/common/tables/swift-proxy-server-app-proxy-server.xml60(td) +msgid "allow_account_management = false" +msgstr "" + +#: ./doc/common/tables/swift-proxy-server-app-proxy-server.xml60(td) +msgid "Whether account PUTs and DELETEs are even callable" +msgstr "" + +#: ./doc/common/tables/swift-proxy-server-app-proxy-server.xml63(td) +msgid "object_post_as_copy = true" +msgstr "" + +#: ./doc/common/tables/swift-proxy-server-app-proxy-server.xml63(td) +msgid "" +"Set object_post_as_copy = false to turn on fast posts where only the " +"metadata changes are stored anew and the original data file is kept in " +"place. This makes for quicker posts; but since the container metadata isn't " +"updated in this mode, features like container sync won't be able to sync " +"posts." +msgstr "" + +#: ./doc/common/tables/swift-proxy-server-app-proxy-server.xml66(td) +msgid "account_autocreate = false" +msgstr "" + +#: ./doc/common/tables/swift-proxy-server-app-proxy-server.xml66(td) +msgid "" +"If set to 'true' authorized accounts that do not yet exist within the Swift " +"cluster will be automatically created." +msgstr "" + +#: ./doc/common/tables/swift-proxy-server-app-proxy-server.xml69(td) +msgid "max_containers_per_account = 0" +msgstr "" + +#: ./doc/common/tables/swift-proxy-server-app-proxy-server.xml69(td) +msgid "" +"If set to a positive value, trying to create a container when the account " +"already has at least this maximum containers will result in a 403 Forbidden." +" Note: This is a soft limit, meaning a user might exceed the cap for " +"recheck_account_existence before the 403s kick in." +msgstr "" + +#: ./doc/common/tables/swift-proxy-server-app-proxy-server.xml72(td) +msgid "max_containers_whitelist =" +msgstr "" + +#: ./doc/common/tables/swift-proxy-server-app-proxy-server.xml72(td) +msgid "" +"is a comma separated list of account names that ignore the " +"max_containers_per_account cap." +msgstr "" + +#: ./doc/common/tables/swift-proxy-server-app-proxy-server.xml75(td) +msgid "deny_host_headers =" +msgstr "" + +#: ./doc/common/tables/swift-proxy-server-app-proxy-server.xml78(td) +#: ./doc/common/tables/swift-account-server-app-account-server.xml36(td) +#: ./doc/common/tables/swift-container-server-app-container-server.xml45(td) +#: ./doc/common/tables/swift-object-server-app-object-server.xml66(td) +#: ./doc/common/tables/swift-object-expirer-object-expirer.xml21(td) +msgid "auto_create_account_prefix = ." +msgstr "" + +#: ./doc/common/tables/swift-proxy-server-app-proxy-server.xml78(td) +#: ./doc/common/tables/swift-account-server-app-account-server.xml36(td) +#: ./doc/common/tables/swift-container-server-app-container-server.xml45(td) +#: ./doc/common/tables/swift-object-server-app-object-server.xml66(td) +#: ./doc/common/tables/swift-object-expirer-object-expirer.xml21(td) +msgid "Prefix to use when automatically creating accounts" +msgstr "" + +#: ./doc/common/tables/swift-proxy-server-app-proxy-server.xml81(td) +msgid "put_queue_depth = 10" +msgstr "" + +#: ./doc/common/tables/swift-proxy-server-app-proxy-server.xml84(td) +msgid "rate_limit_after_segment = 10" +msgstr "" + +#: ./doc/common/tables/swift-proxy-server-app-proxy-server.xml84(td) +msgid "" +"Rate limit the download of large object segments after this segment is " +"downloaded." +msgstr "" + +#: ./doc/common/tables/swift-proxy-server-app-proxy-server.xml87(td) +msgid "rate_limit_segments_per_sec = 1" +msgstr "" + +#: ./doc/common/tables/swift-proxy-server-app-proxy-server.xml87(td) +msgid "" +"Rate limit large object downloads at this rate. contact for a normal " +"request. You can use '* replicas' at the end to have it use the number given" +" times the number of replicas for the ring being used for the request. " +"paste.deploy to use for auth. To use tempauth set to: `egg:swift#tempauth` " +"each request" +msgstr "" + +#: ./doc/common/tables/swift-proxy-server-app-proxy-server.xml90(td) +msgid "sorting_method = shuffle" +msgstr "" + +#: ./doc/common/tables/swift-proxy-server-app-proxy-server.xml93(td) +msgid "timing_expiry = 300" +msgstr "" + +#: ./doc/common/tables/swift-proxy-server-app-proxy-server.xml96(td) +msgid "allow_static_large_object = true" +msgstr "" + +#: ./doc/common/tables/swift-proxy-server-app-proxy-server.xml99(td) +msgid "max_large_object_get_time = 86400" +msgstr "" + +#: ./doc/common/tables/swift-proxy-server-app-proxy-server.xml102(td) +msgid "request_node_count = 2 * replicas" +msgstr "" + +#: ./doc/common/tables/swift-proxy-server-app-proxy-server.xml102(td) +msgid "" +"* replicas Set to the number of nodes to contact for a normal request. You " +"can use '* replicas' at the end to have it use the number given times the " +"number of replicas for the ring being used for the request. conf file for " +"values will only be shown to the list of swift_owners. The exact default " +"definition of a swift_owner is headers> up to the auth system in use, but" +" usually indicates administrative responsibilities. paste.deploy to use for " +"auth. To use tempauth set to: `egg:swift#tempauth` each request" +msgstr "" + +#: ./doc/common/tables/swift-proxy-server-app-proxy-server.xml105(td) +msgid "read_affinity = r1z1=100, r1z2=200, r2=300" +msgstr "" + +#: ./doc/common/tables/swift-proxy-server-app-proxy-server.xml108(td) +msgid "read_affinity =" +msgstr "" + +#: ./doc/common/tables/swift-proxy-server-app-proxy-server.xml111(td) +msgid "write_affinity = r1, r2" +msgstr "" + +#: ./doc/common/tables/swift-proxy-server-app-proxy-server.xml114(td) +msgid "write_affinity =" +msgstr "" + +#: ./doc/common/tables/swift-proxy-server-app-proxy-server.xml117(td) +msgid "write_affinity_node_count = 2 * replicas" +msgstr "" + +#: ./doc/common/tables/swift-proxy-server-app-proxy-server.xml120(td) +msgid "" +"swift_owner_headers = x-container-read, x-container-write, x-container-sync-" +"key, x-container-sync-to, x-account-meta-temp-url-key, x-account-meta-temp-" +"url-key-2" +msgstr "" + +#: ./doc/common/tables/swift-proxy-server-app-proxy-server.xml120(td) +msgid "" +"the sample These are the headers whose conf file for values will only be " +"shown to the list of swift_owners. The exact default definition of a " +"swift_owner is headers> up to the auth system in use, but usually " +"indicates administrative responsibilities. paste.deploy to use for auth. To " +"use tempauth set to: `egg:swift#tempauth` each request" +msgstr "" + +#: ./doc/common/tables/nova-keymgr.xml8(caption) +#: ./doc/common/tables/cinder-keymgr.xml8(caption) +msgid "Description of configuration options for keymgr" +msgstr "" + +#: ./doc/common/tables/nova-keymgr.xml19(th) +#: ./doc/common/tables/cinder-keymgr.xml19(th) +msgid "[keymgr]" +msgstr "" + +#: ./doc/common/tables/nova-keymgr.xml22(td) +msgid "api_class = nova.keymgr.conf_key_mgr.ConfKeyManager" +msgstr "" + +#: ./doc/common/tables/nova-keymgr.xml23(td) +#: ./doc/common/tables/cinder-keymgr.xml23(td) +msgid "(StrOpt) The full class name of the key manager API class" +msgstr "" + +#: ./doc/common/tables/nova-keymgr.xml26(td) +#: ./doc/common/tables/cinder-keymgr.xml26(td) +msgid "fixed_key = None" +msgstr "" + +#: ./doc/common/tables/nova-keymgr.xml27(td) +#: ./doc/common/tables/cinder-keymgr.xml27(td) +msgid "(StrOpt) Fixed key returned by key manager, specified in hex" +msgstr "" + +#: ./doc/common/tables/neutron-api.xml8(caption) +#: ./doc/common/tables/cinder-api.xml8(caption) +#: ./doc/common/tables/nova-api.xml8(caption) +#: ./doc/common/tables/glance-api.xml8(caption) +msgid "Description of configuration options for api" +msgstr "" + +#: ./doc/common/tables/neutron-api.xml19(td) +msgid "allow_bulk = True" +msgstr "" + +#: ./doc/common/tables/neutron-api.xml20(td) +msgid "(BoolOpt) Allow the usage of the bulk API" +msgstr "" + +#: ./doc/common/tables/neutron-api.xml23(td) +msgid "allow_pagination = False" +msgstr "" + +#: ./doc/common/tables/neutron-api.xml24(td) +msgid "(BoolOpt) Allow the usage of the pagination" +msgstr "" + +#: ./doc/common/tables/neutron-api.xml27(td) +msgid "allow_sorting = False" +msgstr "" + +#: ./doc/common/tables/neutron-api.xml28(td) +msgid "(BoolOpt) Allow the usage of the sorting" +msgstr "" + +#: ./doc/common/tables/neutron-api.xml31(td) +msgid "api_extensions_path =" +msgstr "" + +#: ./doc/common/tables/neutron-api.xml32(td) +msgid "(StrOpt) The path for API extensions" +msgstr "" + +#: ./doc/common/tables/neutron-api.xml35(td) +#: ./doc/common/tables/cinder-api.xml22(td) +#: ./doc/common/tables/nova-wsgi.xml22(td) +msgid "api_paste_config = api-paste.ini" +msgstr "" + +#: ./doc/common/tables/neutron-api.xml36(td) +msgid "(StrOpt) The API paste config file to use" +msgstr "" + +#: ./doc/common/tables/neutron-api.xml39(td) +msgid "pagination_max_limit = -1" +msgstr "" + +#: ./doc/common/tables/neutron-api.xml40(td) +msgid "" +"(StrOpt) The maximum number of items returned in a single response, value " +"was 'infinite' or negative integer means no limit" +msgstr "" + +#: ./doc/common/tables/neutron-api.xml43(td) +#: ./doc/common/tables/nova-periodic.xml30(td) +#: ./doc/common/tables/cinder-common.xml174(td) +msgid "run_external_periodic_tasks = True" +msgstr "" + +#: ./doc/common/tables/neutron-api.xml44(td) +#: ./doc/common/tables/nova-periodic.xml31(td) +#: ./doc/common/tables/cinder-common.xml175(td) +msgid "" +"(BoolOpt) Some periodic tasks can be run in a separate process. Should we " +"run them here?" +msgstr "" + +#: ./doc/common/tables/neutron-api.xml47(td) +msgid "service_plugins =" +msgstr "" + +#: ./doc/common/tables/neutron-api.xml48(td) +msgid "(ListOpt) The service plugins Neutron will use" +msgstr "" + +#: ./doc/common/tables/neutron-api.xml51(td) +msgid "service_provider = []" +msgstr "" + +#: ./doc/common/tables/neutron-api.xml52(td) +msgid "" +"(MultiStrOpt) Defines providers for advanced services using the format: " +"<service_type>:<name>:<driver>[:default]" +msgstr "" + +#: ./doc/common/tables/nova-testing.xml8(caption) +#: ./doc/common/tables/glance-testing.xml8(caption) +#: ./doc/common/tables/neutron-testing.xml8(caption) +msgid "Description of configuration options for testing" +msgstr "" + +#: ./doc/common/tables/nova-testing.xml22(td) +#: ./doc/common/tables/cinder-rpc.xml22(td) +msgid "" +"allowed_rpc_exception_modules = nova.exception, cinder.exception, exceptions" +msgstr "" + +#: ./doc/common/tables/nova-testing.xml26(td) +#: ./doc/common/tables/cinder-api.xml30(td) +#: ./doc/common/tables/glance-wsgi.xml22(td) +#: ./doc/common/tables/neutron-testing.xml19(td) +msgid "backdoor_port = None" +msgstr "" + +#: ./doc/common/tables/nova-testing.xml27(td) +msgid "" +"(StrOpt) Enable eventlet backdoor. Acceptable values are 0, <port> and" +" <start>:<end>, where 0 results in listening on a random tcp " +"port number, <port> results in listening on the specified port number " +"and not enabling backdoorif it is in use and <start>:<end> " +"results in listening on the smallest unused port number within the specified" +" range of port numbers. The chosen port is displayed in the service's log " +"file." +msgstr "" + +#: ./doc/common/tables/nova-testing.xml30(td) +msgid "fake_call = False" +msgstr "" + +#: ./doc/common/tables/nova-testing.xml31(td) +msgid "(BoolOpt) If True, skip using the queue and make local calls" +msgstr "" + +#: ./doc/common/tables/nova-testing.xml34(td) +msgid "fake_network = False" +msgstr "" + +#: ./doc/common/tables/nova-testing.xml35(td) +msgid "(BoolOpt) If passed, use fake network devices and addresses" +msgstr "" + +#: ./doc/common/tables/nova-testing.xml38(td) +#: ./doc/common/tables/cinder-rpc.xml42(td) +#: ./doc/common/tables/glance-rabbitmq.xml22(td) +#: ./doc/common/tables/neutron-testing.xml23(td) +msgid "fake_rabbit = False" +msgstr "" + +#: ./doc/common/tables/nova-testing.xml39(td) +#: ./doc/common/tables/cinder-rpc.xml43(td) +#: ./doc/common/tables/glance-rabbitmq.xml23(td) +#: ./doc/common/tables/neutron-testing.xml24(td) +msgid "(BoolOpt) If passed, use a fake RabbitMQ provider" +msgstr "" + +#: ./doc/common/tables/nova-testing.xml42(td) +#: ./doc/common/tables/cinder-common.xml118(td) +msgid "monkey_patch = False" +msgstr "" + +#: ./doc/common/tables/nova-testing.xml43(td) +msgid "(BoolOpt) Whether to log monkey patching" +msgstr "" + +#: ./doc/common/tables/nova-testing.xml46(td) +msgid "" +"monkey_patch_modules = " +"nova.api.ec2.cloud:nova.notifications.notify_decorator, " +"nova.compute.api:nova.notifications.notify_decorator" +msgstr "" + +#: ./doc/common/tables/nova-testing.xml47(td) +#: ./doc/common/tables/cinder-common.xml123(td) +msgid "(ListOpt) List of modules/decorators to monkey patch" +msgstr "" + +#: ./doc/common/tables/cinder-backups.xml8(caption) +msgid "Description of configuration options for backups" +msgstr "" + +#: ./doc/common/tables/cinder-backups.xml22(td) +msgid "backup_api_class = cinder.backup.api.API" +msgstr "" + +#: ./doc/common/tables/cinder-backups.xml23(td) +msgid "(StrOpt) The full class name of the volume backup API class" +msgstr "" + +#: ./doc/common/tables/cinder-backups.xml26(td) +msgid "backup_compression_algorithm = zlib" +msgstr "" + +#: ./doc/common/tables/cinder-backups.xml27(td) +msgid "(StrOpt) Compression algorithm (None to disable)" +msgstr "" + +#: ./doc/common/tables/cinder-backups.xml30(td) +msgid "backup_driver = cinder.backup.drivers.swift" +msgstr "" + +#: ./doc/common/tables/cinder-backups.xml31(td) +msgid "(StrOpt) Driver to use for backups." +msgstr "" + +#: ./doc/common/tables/cinder-backups.xml34(td) +msgid "backup_manager = cinder.backup.manager.BackupManager" +msgstr "" + +#: ./doc/common/tables/cinder-backups.xml35(td) +msgid "(StrOpt) full class name for the Manager for volume backup" +msgstr "" + +#: ./doc/common/tables/cinder-backups.xml38(td) +msgid "backup_name_template = backup-%s" +msgstr "" + +#: ./doc/common/tables/cinder-backups.xml39(td) +msgid "(StrOpt) Template string to be used to generate backup names" +msgstr "" + +#: ./doc/common/tables/cinder-backups.xml42(td) +msgid "backup_topic = cinder-backup" +msgstr "" + +#: ./doc/common/tables/cinder-backups.xml43(td) +msgid "(StrOpt) the topic volume backup nodes listen on" +msgstr "" + +#: ./doc/common/tables/cinder-backups.xml46(td) +#: ./doc/common/tables/nova-api.xml82(td) +msgid "snapshot_name_template = snapshot-%s" +msgstr "" + +#: ./doc/common/tables/cinder-backups.xml47(td) +#: ./doc/common/tables/nova-api.xml83(td) +msgid "(StrOpt) Template string to be used to generate snapshot names" +msgstr "" + +#: ./doc/common/tables/cinder-backups.xml50(td) +msgid "snapshot_same_host = True" +msgstr "" + +#: ./doc/common/tables/cinder-backups.xml51(td) +msgid "" +"(BoolOpt) Create volume from snapshot at the host where snapshot resides" +msgstr "" + +#: ./doc/common/tables/swift-container-server-pipeline-main.xml7(literal) +#: ./doc/common/tables/swift-object-server-pipeline-main.xml7(literal) +#: ./doc/common/tables/swift-object-expirer-pipeline-main.xml7(literal) +#: ./doc/common/tables/swift-account-server-pipeline-main.xml7(literal) +#: ./doc/common/tables/swift-proxy-server-pipeline-main.xml7(literal) +msgid "[pipeline:main]" +msgstr "" + +#: ./doc/common/tables/swift-container-server-pipeline-main.xml18(td) +msgid "pipeline = healthcheck recon container-server" +msgstr "" + +#: ./doc/common/tables/swift-rsyncd-object.xml7(literal) +msgid "[object]" +msgstr "" + +#: ./doc/common/tables/swift-rsyncd-object.xml7(literal) +#: ./doc/common/tables/swift-rsyncd-account.xml7(literal) +#: ./doc/common/tables/swift-rsyncd-container.xml7(literal) +msgid "rsyncd.conf-sample" +msgstr "" + +#: ./doc/common/tables/swift-rsyncd-object.xml18(td) +msgid "max connections = 8" +msgstr "" + +#: ./doc/common/tables/swift-rsyncd-object.xml21(td) +#: ./doc/common/tables/swift-rsyncd-account.xml21(td) +#: ./doc/common/tables/swift-rsyncd-container.xml21(td) +msgid "path = /srv/node" +msgstr "" + +#: ./doc/common/tables/swift-rsyncd-object.xml24(td) +#: ./doc/common/tables/swift-rsyncd-account.xml24(td) +#: ./doc/common/tables/swift-rsyncd-container.xml24(td) +msgid "read only = false" +msgstr "" + +#: ./doc/common/tables/swift-rsyncd-object.xml27(td) +msgid "lock file = /var/lock/object.lock" +msgstr "" + +#: ./doc/common/tables/nova-s3.xml22(td) +msgid "buckets_path = $state_path/buckets" +msgstr "" + +#: ./doc/common/tables/nova-s3.xml23(td) +msgid "(StrOpt) path to s3 buckets" +msgstr "" + +#: ./doc/common/tables/nova-s3.xml26(td) +msgid "image_decryption_dir = /tmp" +msgstr "" + +#: ./doc/common/tables/nova-s3.xml27(td) +msgid "(StrOpt) parent dir for tempdir used for image decryption" +msgstr "" + +#: ./doc/common/tables/nova-s3.xml30(td) +msgid "s3_access_key = notchecked" +msgstr "" + +#: ./doc/common/tables/nova-s3.xml31(td) +msgid "(StrOpt) access key to use for s3 server for images" +msgstr "" + +#: ./doc/common/tables/nova-s3.xml34(td) +msgid "s3_affix_tenant = False" +msgstr "" + +#: ./doc/common/tables/nova-s3.xml35(td) +msgid "" +"(BoolOpt) whether to affix the tenant id to the access key when downloading " +"from s3" +msgstr "" + +#: ./doc/common/tables/nova-s3.xml38(td) +msgid "s3_host = $my_ip" +msgstr "" + +#: ./doc/common/tables/nova-s3.xml39(td) +msgid "(StrOpt) hostname or ip for OpenStack to use when accessing the s3 api" +msgstr "" + +#: ./doc/common/tables/nova-s3.xml42(td) +msgid "s3_listen = 0.0.0.0" +msgstr "" + +#: ./doc/common/tables/nova-s3.xml43(td) +msgid "(StrOpt) IP address for S3 API to listen" +msgstr "" + +#: ./doc/common/tables/nova-s3.xml46(td) +msgid "s3_listen_port = 3333" +msgstr "" + +#: ./doc/common/tables/nova-s3.xml47(td) +msgid "(IntOpt) port for s3 api to listen" +msgstr "" + +#: ./doc/common/tables/nova-s3.xml50(td) +msgid "s3_port = 3333" +msgstr "" + +#: ./doc/common/tables/nova-s3.xml51(td) +msgid "(IntOpt) port used when accessing the s3 api" +msgstr "" + +#: ./doc/common/tables/nova-s3.xml54(td) +msgid "s3_secret_key = notchecked" +msgstr "" + +#: ./doc/common/tables/nova-s3.xml55(td) +msgid "(StrOpt) secret key to use for s3 server for images" +msgstr "" + +#: ./doc/common/tables/nova-s3.xml58(td) +msgid "s3_use_ssl = False" +msgstr "" + +#: ./doc/common/tables/nova-s3.xml59(td) +msgid "(BoolOpt) whether to use ssl when talking to s3" +msgstr "" + +#: ./doc/common/tables/neutron-openvswitch.xml8(caption) +msgid "Description of configuration options for openvswitch" +msgstr "" + +#: ./doc/common/tables/nova-zookeeper.xml8(caption) +msgid "Description of configuration options for zookeeper" +msgstr "" + +#: ./doc/common/tables/nova-zookeeper.xml19(th) +msgid "[zookeeper]" +msgstr "" + +#: ./doc/common/tables/nova-zookeeper.xml22(td) +msgid "address = None" +msgstr "" + +#: ./doc/common/tables/nova-zookeeper.xml23(td) +msgid "" +"(StrOpt) The ZooKeeper addresses for servicegroup service in the format of " +"host1:port,host2:port,host3:port" +msgstr "" + +#: ./doc/common/tables/nova-zookeeper.xml26(td) +msgid "recv_timeout = 4000" +msgstr "" + +#: ./doc/common/tables/nova-zookeeper.xml27(td) +msgid "(IntOpt) recv_timeout parameter for the zk session" +msgstr "" + +#: ./doc/common/tables/nova-zookeeper.xml30(td) +msgid "sg_prefix = /servicegroups" +msgstr "" + +#: ./doc/common/tables/nova-zookeeper.xml31(td) +msgid "(StrOpt) The prefix used in ZooKeeper to store ephemeral nodes" +msgstr "" + +#: ./doc/common/tables/nova-zookeeper.xml34(td) +msgid "sg_retry_interval = 5" +msgstr "" + +#: ./doc/common/tables/nova-zookeeper.xml35(td) +msgid "(IntOpt) Number of seconds to wait until retrying to join the session" +msgstr "" + +#: ./doc/common/tables/cinder-rpc.xml8(caption) +#: ./doc/common/tables/glance-rpc.xml8(caption) +#: ./doc/common/tables/neutron-rpc.xml8(caption) +#: ./doc/common/tables/nova-rpc.xml8(caption) +msgid "Description of configuration options for rpc" +msgstr "" + +#: ./doc/common/tables/cinder-rpc.xml26(td) +#: ./doc/common/tables/neutron-rpc.xml19(td) +#: ./doc/common/tables/nova-rpc.xml22(td) +msgid "amqp_auto_delete = False" +msgstr "" + +#: ./doc/common/tables/cinder-rpc.xml27(td) +#: ./doc/common/tables/neutron-rpc.xml20(td) +#: ./doc/common/tables/nova-rpc.xml23(td) +msgid "(BoolOpt) Auto-delete queues in amqp." +msgstr "" + +#: ./doc/common/tables/cinder-rpc.xml30(td) +#: ./doc/common/tables/neutron-rpc.xml23(td) +#: ./doc/common/tables/nova-rpc.xml26(td) +msgid "amqp_durable_queues = False" +msgstr "" + +#: ./doc/common/tables/cinder-rpc.xml31(td) +#: ./doc/common/tables/neutron-rpc.xml24(td) +#: ./doc/common/tables/nova-rpc.xml27(td) +msgid "(BoolOpt) Use durable queues in amqp." +msgstr "" + +#: ./doc/common/tables/cinder-rpc.xml34(td) +msgid "amqp_rpc_single_reply_queue = False" +msgstr "" + +#: ./doc/common/tables/cinder-rpc.xml35(td) +msgid "" +"(BoolOpt) Enable a fast single reply queue if using AMQP based RPC like " +"RabbitMQ or Qpid." +msgstr "" + +#: ./doc/common/tables/cinder-rpc.xml38(td) +#: ./doc/common/tables/nova-rpc.xml30(td) +msgid "control_exchange = openstack" +msgstr "" + +#: ./doc/common/tables/cinder-rpc.xml39(td) +#: ./doc/common/tables/neutron-rpc.xml28(td) +#: ./doc/common/tables/nova-rpc.xml31(td) +msgid "(StrOpt) AMQP exchange to connect to if using RabbitMQ or Qpid" +msgstr "" + +#: ./doc/common/tables/cinder-rpc.xml62(td) +#: ./doc/common/tables/neutron-rpc.xml35(td) +#: ./doc/common/tables/nova-rpc.xml34(td) +msgid "matchmaker_heartbeat_freq = 300" +msgstr "" + +#: ./doc/common/tables/cinder-rpc.xml63(td) +#: ./doc/common/tables/neutron-rpc.xml36(td) +#: ./doc/common/tables/nova-rpc.xml35(td) +msgid "(IntOpt) Heartbeat frequency" +msgstr "" + +#: ./doc/common/tables/cinder-rpc.xml66(td) +#: ./doc/common/tables/neutron-rpc.xml39(td) +#: ./doc/common/tables/nova-rpc.xml38(td) +msgid "matchmaker_heartbeat_ttl = 600" +msgstr "" + +#: ./doc/common/tables/cinder-rpc.xml67(td) +#: ./doc/common/tables/neutron-rpc.xml40(td) +#: ./doc/common/tables/nova-rpc.xml39(td) +msgid "(IntOpt) Heartbeat time-to-live." +msgstr "" + +#: ./doc/common/tables/cinder-rpc.xml70(td) +msgid "matchmaker_ringfile = /etc/nova/matchmaker_ring.json" +msgstr "" + +#: ./doc/common/tables/cinder-rpc.xml71(td) +#: ./doc/common/tables/cinder-rpc.xml226(td) +#: ./doc/common/tables/neutron-rpc.xml52(td) +#: ./doc/common/tables/nova-rpc.xml73(td) +msgid "(StrOpt) Matchmaker ring file (JSON)" +msgstr "" + +#: ./doc/common/tables/cinder-rpc.xml82(td) +#: ./doc/common/tables/glance-logging.xml78(td) +#: ./doc/common/tables/neutron-logging.xml75(td) +#: ./doc/common/tables/nova-logging.xml82(td) +msgid "publish_errors = False" +msgstr "" + +#: ./doc/common/tables/cinder-rpc.xml83(td) +#: ./doc/common/tables/glance-logging.xml79(td) +#: ./doc/common/tables/neutron-logging.xml76(td) +#: ./doc/common/tables/nova-logging.xml83(td) +msgid "(BoolOpt) publish error events" +msgstr "" + +#: ./doc/common/tables/cinder-rpc.xml99(td) +#: ./doc/common/tables/neutron-qpid.xml32(td) +#: ./doc/common/tables/nova-qpid.xml35(td) +msgid "(StrOpt) Password for qpid connection" +msgstr "" + +#: ./doc/common/tables/cinder-rpc.xml123(td) +#: ./doc/common/tables/neutron-qpid.xml56(td) +#: ./doc/common/tables/nova-qpid.xml59(td) +msgid "(StrOpt) Username for qpid connection" +msgstr "" + +#: ./doc/common/tables/cinder-rpc.xml126(td) +#: ./doc/common/tables/glance-rabbitmq.xml42(td) +#: ./doc/common/tables/neutron-rabbitmq.xml19(td) +#: ./doc/common/tables/nova-rabbitmq.xml22(td) +msgid "rabbit_ha_queues = False" +msgstr "" + +#: ./doc/common/tables/cinder-rpc.xml127(td) +#: ./doc/common/tables/glance-rabbitmq.xml43(td) +#: ./doc/common/tables/neutron-rabbitmq.xml20(td) +#: ./doc/common/tables/nova-rabbitmq.xml23(td) +msgid "" +"(BoolOpt) use H/A queues in RabbitMQ (x-ha-policy: all).You need to wipe " +"RabbitMQ database when changing this option." +msgstr "" + +#: ./doc/common/tables/cinder-rpc.xml130(td) +#: ./doc/common/tables/glance-rabbitmq.xml46(td) +#: ./doc/common/tables/neutron-rabbitmq.xml23(td) +#: ./doc/common/tables/nova-rabbitmq.xml26(td) +msgid "rabbit_host = localhost" +msgstr "" + +#: ./doc/common/tables/cinder-rpc.xml131(td) +#: ./doc/common/tables/glance-rabbitmq.xml47(td) +#: ./doc/common/tables/neutron-rabbitmq.xml24(td) +#: ./doc/common/tables/nova-rabbitmq.xml27(td) +msgid "(StrOpt) The RabbitMQ broker address where a single node is used" +msgstr "" + +#: ./doc/common/tables/cinder-rpc.xml134(td) +#: ./doc/common/tables/glance-rabbitmq.xml50(td) +#: ./doc/common/tables/neutron-rabbitmq.xml27(td) +#: ./doc/common/tables/nova-rabbitmq.xml30(td) +msgid "rabbit_hosts = $rabbit_host:$rabbit_port" +msgstr "" + +#: ./doc/common/tables/cinder-rpc.xml135(td) +#: ./doc/common/tables/glance-rabbitmq.xml51(td) +#: ./doc/common/tables/neutron-rabbitmq.xml28(td) +#: ./doc/common/tables/nova-rabbitmq.xml31(td) +msgid "(ListOpt) RabbitMQ HA cluster host:port pairs" +msgstr "" + +#: ./doc/common/tables/cinder-rpc.xml138(td) +#: ./doc/common/tables/glance-rabbitmq.xml54(td) +#: ./doc/common/tables/neutron-rabbitmq.xml31(td) +#: ./doc/common/tables/nova-rabbitmq.xml34(td) +msgid "rabbit_max_retries = 0" +msgstr "" + +#: ./doc/common/tables/cinder-rpc.xml139(td) +#: ./doc/common/tables/glance-rabbitmq.xml55(td) +#: ./doc/common/tables/neutron-rabbitmq.xml32(td) +#: ./doc/common/tables/nova-rabbitmq.xml35(td) +msgid "" +"(IntOpt) maximum retries with trying to connect to RabbitMQ (the default of " +"0 implies an infinite retry count)" +msgstr "" + +#: ./doc/common/tables/cinder-rpc.xml142(td) +#: ./doc/common/tables/glance-rabbitmq.xml58(td) +#: ./doc/common/tables/neutron-rabbitmq.xml35(td) +#: ./doc/common/tables/nova-rabbitmq.xml38(td) +msgid "rabbit_password = guest" +msgstr "" + +#: ./doc/common/tables/cinder-rpc.xml143(td) +#: ./doc/common/tables/glance-rabbitmq.xml59(td) +#: ./doc/common/tables/neutron-rabbitmq.xml36(td) +#: ./doc/common/tables/nova-rabbitmq.xml39(td) +msgid "(StrOpt) the RabbitMQ password" +msgstr "" + +#: ./doc/common/tables/cinder-rpc.xml146(td) +#: ./doc/common/tables/glance-rabbitmq.xml62(td) +#: ./doc/common/tables/neutron-rabbitmq.xml39(td) +#: ./doc/common/tables/nova-rabbitmq.xml42(td) +msgid "rabbit_port = 5672" +msgstr "" + +#: ./doc/common/tables/cinder-rpc.xml147(td) +#: ./doc/common/tables/glance-rabbitmq.xml63(td) +#: ./doc/common/tables/neutron-rabbitmq.xml40(td) +#: ./doc/common/tables/nova-rabbitmq.xml43(td) +msgid "(IntOpt) The RabbitMQ broker port where a single node is used" +msgstr "" + +#: ./doc/common/tables/cinder-rpc.xml150(td) +#: ./doc/common/tables/glance-rabbitmq.xml66(td) +#: ./doc/common/tables/neutron-rabbitmq.xml43(td) +#: ./doc/common/tables/nova-rabbitmq.xml46(td) +msgid "rabbit_retry_backoff = 2" +msgstr "" + +#: ./doc/common/tables/cinder-rpc.xml151(td) +#: ./doc/common/tables/glance-rabbitmq.xml67(td) +#: ./doc/common/tables/neutron-rabbitmq.xml44(td) +#: ./doc/common/tables/nova-rabbitmq.xml47(td) +msgid "" +"(IntOpt) how long to backoff for between retries when connecting to RabbitMQ" +msgstr "" + +#: ./doc/common/tables/cinder-rpc.xml154(td) +#: ./doc/common/tables/glance-rabbitmq.xml70(td) +#: ./doc/common/tables/neutron-rabbitmq.xml47(td) +#: ./doc/common/tables/nova-rabbitmq.xml50(td) +msgid "rabbit_retry_interval = 1" +msgstr "" + +#: ./doc/common/tables/cinder-rpc.xml155(td) +#: ./doc/common/tables/glance-rabbitmq.xml71(td) +#: ./doc/common/tables/neutron-rabbitmq.xml48(td) +#: ./doc/common/tables/nova-rabbitmq.xml51(td) +msgid "(IntOpt) how frequently to retry connecting with RabbitMQ" +msgstr "" + +#: ./doc/common/tables/cinder-rpc.xml158(td) +#: ./doc/common/tables/glance-rabbitmq.xml74(td) +#: ./doc/common/tables/neutron-rabbitmq.xml51(td) +#: ./doc/common/tables/nova-rabbitmq.xml54(td) +msgid "rabbit_use_ssl = False" +msgstr "" + +#: ./doc/common/tables/cinder-rpc.xml159(td) +#: ./doc/common/tables/glance-rabbitmq.xml75(td) +#: ./doc/common/tables/neutron-rabbitmq.xml52(td) +#: ./doc/common/tables/nova-rabbitmq.xml55(td) +msgid "(BoolOpt) connect over SSL for RabbitMQ" +msgstr "" + +#: ./doc/common/tables/cinder-rpc.xml162(td) +#: ./doc/common/tables/glance-rabbitmq.xml78(td) +#: ./doc/common/tables/neutron-rabbitmq.xml55(td) +#: ./doc/common/tables/nova-rabbitmq.xml58(td) +msgid "rabbit_userid = guest" +msgstr "" + +#: ./doc/common/tables/cinder-rpc.xml163(td) +#: ./doc/common/tables/glance-rabbitmq.xml79(td) +#: ./doc/common/tables/neutron-rabbitmq.xml56(td) +#: ./doc/common/tables/nova-rabbitmq.xml59(td) +msgid "(StrOpt) the RabbitMQ userid" +msgstr "" + +#: ./doc/common/tables/cinder-rpc.xml166(td) +#: ./doc/common/tables/glance-rabbitmq.xml82(td) +#: ./doc/common/tables/neutron-rabbitmq.xml59(td) +#: ./doc/common/tables/nova-rabbitmq.xml62(td) +msgid "rabbit_virtual_host = /" +msgstr "" + +#: ./doc/common/tables/cinder-rpc.xml167(td) +#: ./doc/common/tables/glance-rabbitmq.xml83(td) +#: ./doc/common/tables/neutron-rabbitmq.xml60(td) +#: ./doc/common/tables/nova-rabbitmq.xml63(td) +msgid "(StrOpt) the RabbitMQ virtual host" +msgstr "" + +#: ./doc/common/tables/cinder-rpc.xml170(td) +msgid "rpc_backend = cinder.openstack.common.rpc.impl_kombu" +msgstr "" + +#: ./doc/common/tables/cinder-rpc.xml171(td) +#: ./doc/common/tables/neutron-rpc.xml56(td) +#: ./doc/common/tables/nova-rpc.xml43(td) +msgid "(StrOpt) The messaging module to use, defaults to kombu." +msgstr "" + +#: ./doc/common/tables/cinder-rpc.xml178(td) +#: ./doc/common/tables/neutron-rpc.xml63(td) +#: ./doc/common/tables/nova-rpc.xml50(td) +msgid "rpc_conn_pool_size = 30" +msgstr "" + +#: ./doc/common/tables/cinder-rpc.xml179(td) +#: ./doc/common/tables/neutron-rpc.xml64(td) +#: ./doc/common/tables/nova-rpc.xml51(td) +msgid "(IntOpt) Size of RPC connection pool" +msgstr "" + +#: ./doc/common/tables/cinder-rpc.xml182(td) +#: ./doc/common/tables/neutron-rpc.xml67(td) +#: ./doc/common/tables/nova-rpc.xml54(td) +msgid "rpc_response_timeout = 60" +msgstr "" + +#: ./doc/common/tables/cinder-rpc.xml183(td) +#: ./doc/common/tables/neutron-rpc.xml68(td) +#: ./doc/common/tables/nova-rpc.xml55(td) +msgid "(IntOpt) Seconds to wait for a response from call or multicall" +msgstr "" + +#: ./doc/common/tables/cinder-rpc.xml186(td) +#: ./doc/common/tables/neutron-rpc.xml75(td) +#: ./doc/common/tables/nova-rpc.xml58(td) +msgid "rpc_thread_pool_size = 64" +msgstr "" + +#: ./doc/common/tables/cinder-rpc.xml187(td) +#: ./doc/common/tables/neutron-rpc.xml76(td) +#: ./doc/common/tables/nova-rpc.xml59(td) +msgid "(IntOpt) Size of RPC thread pool" +msgstr "" + +#: ./doc/common/tables/cinder-rpc.xml206(td) +msgid "" +"rpc_zmq_matchmaker = " +"cinder.openstack.common.rpc.matchmaker.MatchMakerLocalhost" +msgstr "" + +#: ./doc/common/tables/cinder-rpc.xml218(td) +msgid "volume_topic = cinder-volume" +msgstr "" + +#: ./doc/common/tables/cinder-rpc.xml219(td) +msgid "(StrOpt) the topic volume nodes listen on" +msgstr "" + +#: ./doc/common/tables/cinder-rpc.xml222(th) +#: ./doc/common/tables/nova-rpc.xml69(th) +msgid "[matchmaker_ring]" +msgstr "" + +#: ./doc/common/tables/cinder-rpc.xml225(td) +#: ./doc/common/tables/neutron-rpc.xml51(td) +#: ./doc/common/tables/nova-rpc.xml72(td) +msgid "ringfile = /etc/oslo/matchmaker_ring.json" +msgstr "" + +#: ./doc/common/tables/cinder-api.xml23(td) +msgid "(StrOpt) File name for the paste.deploy config for cinder-api" +msgstr "" + +#: ./doc/common/tables/cinder-api.xml26(td) +msgid "api_rate_limit = True" +msgstr "" + +#: ./doc/common/tables/cinder-api.xml27(td) +msgid "(BoolOpt) whether to rate limit the api" +msgstr "" + +#: ./doc/common/tables/cinder-api.xml31(td) +msgid "" +"(StrOpt) Enable eventlet backdoor. Acceptable values are 0, <port>, " +"and <start>:<end>, where 0 results in listening on a random tcp " +"port number; <port> results in listening on the specified port number " +"(and not enabling backdoor if that port is in use); and " +"<start>:<end> results in listening on the smallest unused port " +"number within the specified range of port numbers. The chosen port is " +"displayed in the service's log file." +msgstr "" + +#: ./doc/common/tables/cinder-api.xml34(td) +#: ./doc/common/tables/glance-api.xml38(td) +msgid "enable_v1_api = True" +msgstr "" + +#: ./doc/common/tables/cinder-api.xml35(td) +msgid "(BoolOpt) Deploy v1 of the Cinder API." +msgstr "" + +#: ./doc/common/tables/cinder-api.xml38(td) +#: ./doc/common/tables/glance-api.xml42(td) +msgid "enable_v2_api = True" +msgstr "" + +#: ./doc/common/tables/cinder-api.xml39(td) +msgid "(BoolOpt) Deploy v2 of the Cinder API." +msgstr "" + +#: ./doc/common/tables/cinder-api.xml42(td) +#: ./doc/common/tables/nova-policy.xml46(td) +msgid "osapi_max_limit = 1000" +msgstr "" + +#: ./doc/common/tables/cinder-api.xml43(td) +#: ./doc/common/tables/nova-policy.xml47(td) +msgid "" +"(IntOpt) the maximum number of items returned in a single response from a " +"collection resource" +msgstr "" + +#: ./doc/common/tables/cinder-api.xml46(td) +#: ./doc/common/tables/nova-policy.xml50(td) +msgid "osapi_max_request_body_size = 114688" +msgstr "" + +#: ./doc/common/tables/cinder-api.xml47(td) +msgid "(IntOpt) Max size for body of a request" +msgstr "" + +#: ./doc/common/tables/cinder-api.xml50(td) +msgid "osapi_volume_base_URL = None" +msgstr "" + +#: ./doc/common/tables/cinder-api.xml51(td) +msgid "" +"(StrOpt) Base URL that will be presented to users in links to the OpenStack " +"Volume API" +msgstr "" + +#: ./doc/common/tables/cinder-api.xml54(td) +msgid "osapi_volume_ext_list =" +msgstr "" + +#: ./doc/common/tables/cinder-api.xml55(td) +msgid "" +"(ListOpt) Specify list of extensions to load when using " +"osapi_volume_extension option with cinder.api.contrib.select_extensions" +msgstr "" + +#: ./doc/common/tables/cinder-api.xml58(td) +msgid "osapi_volume_extension = ['cinder.api.contrib.standard_extensions']" +msgstr "" + +#: ./doc/common/tables/cinder-api.xml59(td) +msgid "(MultiStrOpt) osapi volume extension to load" +msgstr "" + +#: ./doc/common/tables/cinder-api.xml62(td) +msgid "osapi_volume_listen = 0.0.0.0" +msgstr "" + +#: ./doc/common/tables/cinder-api.xml63(td) +msgid "(StrOpt) IP address for OpenStack Volume API to listen" +msgstr "" + +#: ./doc/common/tables/cinder-api.xml66(td) +msgid "osapi_volume_listen_port = 8776" +msgstr "" + +#: ./doc/common/tables/cinder-api.xml67(td) +msgid "(IntOpt) port for os volume api to listen" +msgstr "" + +#: ./doc/common/tables/cinder-api.xml70(td) +msgid "transfer_api_class = cinder.transfer.api.API" +msgstr "" + +#: ./doc/common/tables/cinder-api.xml71(td) +msgid "(StrOpt) The full class name of the volume transfer API class" +msgstr "" + +#: ./doc/common/tables/cinder-api.xml74(td) +msgid "volume_api_class = cinder.volume.api.API" +msgstr "" + +#: ./doc/common/tables/cinder-api.xml78(td) +msgid "volume_name_template = volume-%s" +msgstr "" + +#: ./doc/common/tables/cinder-api.xml79(td) +msgid "(StrOpt) Template string to be used to generate volume names" +msgstr "" + +#: ./doc/common/tables/cinder-windows.xml8(caption) +msgid "Description of configuration options for windows" +msgstr "" + +#: ./doc/common/tables/cinder-windows.xml22(td) +msgid "windows_iscsi_lun_path = C:\\iSCSIVirtualDisks" +msgstr "" + +#: ./doc/common/tables/cinder-windows.xml23(td) +msgid "(StrOpt) Path to store VHD backed volumes" +msgstr "" + +#: ./doc/common/tables/swift-object-server-pipeline-main.xml18(td) +msgid "pipeline = healthcheck recon object-server" +msgstr "" + +#: ./doc/common/tables/cinder-san.xml8(caption) +msgid "Description of configuration options for san" +msgstr "" + +#: ./doc/common/tables/cinder-san.xml22(td) +msgid "san_clustername =" +msgstr "" + +#: ./doc/common/tables/cinder-san.xml23(td) +msgid "(StrOpt) Cluster name to use for creating volumes" +msgstr "" + +#: ./doc/common/tables/cinder-san.xml26(td) +msgid "san_ip =" +msgstr "" + +#: ./doc/common/tables/cinder-san.xml27(td) +msgid "(StrOpt) IP address of SAN controller" +msgstr "" + +#: ./doc/common/tables/cinder-san.xml30(td) +msgid "san_is_local = False" +msgstr "" + +#: ./doc/common/tables/cinder-san.xml31(td) +msgid "" +"(BoolOpt) Execute commands locally instead of over SSH; use if the volume " +"service is running on the SAN device" +msgstr "" + +#: ./doc/common/tables/cinder-san.xml34(td) +msgid "san_login = admin" +msgstr "" + +#: ./doc/common/tables/cinder-san.xml35(td) +msgid "(StrOpt) Username for SAN controller" +msgstr "" + +#: ./doc/common/tables/cinder-san.xml38(td) +msgid "san_password =" +msgstr "" + +#: ./doc/common/tables/cinder-san.xml39(td) +msgid "(StrOpt) Password for SAN controller" +msgstr "" + +#: ./doc/common/tables/cinder-san.xml42(td) +msgid "san_private_key =" +msgstr "" + +#: ./doc/common/tables/cinder-san.xml43(td) +msgid "(StrOpt) Filename of private key to use for SSH authentication" +msgstr "" + +#: ./doc/common/tables/cinder-san.xml46(td) +msgid "san_ssh_port = 22" +msgstr "" + +#: ./doc/common/tables/cinder-san.xml47(td) +msgid "(IntOpt) SSH port to use with SAN" +msgstr "" + +#: ./doc/common/tables/cinder-san.xml50(td) +msgid "san_thin_provision = True" +msgstr "" + +#: ./doc/common/tables/cinder-san.xml51(td) +msgid "(BoolOpt) Use thin provisioning for SAN volumes?" +msgstr "" + +#: ./doc/common/tables/cinder-san.xml54(td) +msgid "ssh_conn_timeout = 30" +msgstr "" + +#: ./doc/common/tables/cinder-san.xml55(td) +msgid "(IntOpt) SSH connection timeout in seconds" +msgstr "" + +#: ./doc/common/tables/cinder-san.xml58(td) +msgid "ssh_max_pool_conn = 5" +msgstr "" + +#: ./doc/common/tables/cinder-san.xml59(td) +msgid "(IntOpt) Maximum ssh connections in the pool" +msgstr "" + +#: ./doc/common/tables/cinder-san.xml62(td) +msgid "ssh_min_pool_conn = 1" +msgstr "" + +#: ./doc/common/tables/cinder-san.xml63(td) +msgid "(IntOpt) Minimum ssh connections in the pool" +msgstr "" + +#: ./doc/common/tables/swift-account-server-app-account-server.xml7(literal) +msgid "[app:account-server]" +msgstr "" + +#: ./doc/common/tables/swift-account-server-app-account-server.xml18(td) +msgid "use = egg:swift#account" +msgstr "" + +#: ./doc/common/tables/swift-account-server-app-account-server.xml21(td) +msgid "set log_name = account-server" +msgstr "" + +#: ./doc/common/tables/swift-account-server-app-account-server.xml30(td) +#: ./doc/common/tables/swift-container-server-app-container-server.xml30(td) +#: ./doc/common/tables/swift-object-server-app-object-server.xml30(td) +msgid "set log_requests = true" +msgstr "" + +#: ./doc/common/tables/swift-account-server-app-account-server.xml30(td) +#: ./doc/common/tables/swift-container-server-app-container-server.xml30(td) +#: ./doc/common/tables/swift-object-server-app-object-server.xml30(td) +msgid "Whether or not to log requests" +msgstr "" + +#: ./doc/common/tables/swift-account-server-app-account-server.xml39(td) +#: ./doc/common/tables/swift-container-server-app-container-server.xml48(td) +#: ./doc/common/tables/swift-object-server-app-object-server.xml69(td) +msgid "replication_server = false" +msgstr "" + +#: ./doc/common/tables/swift-account-server-app-account-server.xml39(td) +#: ./doc/common/tables/swift-container-server-app-container-server.xml48(td) +#: ./doc/common/tables/swift-object-server-app-object-server.xml69(td) +msgid "" +"If defined, tells server how to handle replication verbs in requests. When " +"set to True (or 1), only replication verbs will be accepted. When set to " +"False, replication verbs will be rejected. When undefined, server will " +"accept any verb in the request." +msgstr "" + +#: ./doc/common/tables/cinder-keymgr.xml22(td) +msgid "api_class = cinder.keymgr.conf_key_mgr.ConfKeyManager" +msgstr "" + +#: ./doc/common/tables/nova-db.xml8(caption) +#: ./doc/common/tables/neutron-db.xml8(caption) +#: ./doc/common/tables/glance-db.xml8(caption) +msgid "Description of configuration options for db" +msgstr "" + +#: ./doc/common/tables/nova-db.xml22(td) +msgid "db_driver = nova.db" +msgstr "" + +#: ./doc/common/tables/nova-db.xml23(td) +#: ./doc/common/tables/cinder-database.xml27(td) +msgid "(StrOpt) driver to use for database access" +msgstr "" + +#: ./doc/common/tables/nova-db.xml26(td) +msgid "sqlite_db = nova.sqlite" +msgstr "" + +#: ./doc/common/tables/nova-db.xml27(td) +#: ./doc/common/tables/cinder-common.xml183(td) +#: ./doc/common/tables/neutron-db.xml72(td) +#: ./doc/common/tables/glance-db.xml23(td) +msgid "(StrOpt) the filename to use with sqlite" +msgstr "" + +#: ./doc/common/tables/nova-db.xml30(td) +#: ./doc/common/tables/cinder-common.xml186(td) +#: ./doc/common/tables/neutron-db.xml75(td) +#: ./doc/common/tables/glance-db.xml26(td) +msgid "sqlite_synchronous = True" +msgstr "" + +#: ./doc/common/tables/nova-db.xml31(td) +#: ./doc/common/tables/cinder-common.xml187(td) +#: ./doc/common/tables/neutron-db.xml76(td) +#: ./doc/common/tables/glance-db.xml27(td) +msgid "(BoolOpt) If true, use synchronous mode for sqlite" +msgstr "" + +#: ./doc/common/tables/nova-db.xml37(td) +msgid "db_check_interval = 60" +msgstr "" + +#: ./doc/common/tables/nova-db.xml38(td) +msgid "(IntOpt) Seconds between getting fresh cell info from db." +msgstr "" + +#: ./doc/common/tables/nova-db.xml41(th) +#: ./doc/common/tables/cinder-storage.xml138(th) +#: ./doc/common/tables/glance-common.xml106(th) +#: ./doc/common/tables/cinder-common.xml238(th) +#: ./doc/common/tables/cinder-connection.xml19(th) +#: ./doc/common/tables/glance-db.xml30(th) +#: ./doc/common/tables/nova-api.xml90(th) +msgid "[database]" +msgstr "" + +#: ./doc/common/tables/nova-db.xml44(td) +#: ./doc/common/tables/cinder-storage.xml141(td) +#: ./doc/common/tables/neutron-db.xml19(td) +#: ./doc/common/tables/glance-db.xml33(td) +msgid "backend = sqlalchemy" +msgstr "" + +#: ./doc/common/tables/nova-db.xml45(td) +#: ./doc/common/tables/cinder-storage.xml142(td) +#: ./doc/common/tables/cinder-database.xml23(td) +#: ./doc/common/tables/neutron-db.xml20(td) +#: ./doc/common/tables/glance-db.xml34(td) +msgid "(StrOpt) The backend to use for db" +msgstr "" + +#: ./doc/common/tables/nova-db.xml48(td) +msgid "" +"connection = " +"sqlite:////home/shaunm/Projects/nova/nova/openstack/common/db/$sqlite_db" +msgstr "" + +#: ./doc/common/tables/nova-db.xml49(td) +#: ./doc/common/tables/cinder-connection.xml23(td) +#: ./doc/common/tables/neutron-db.xml24(td) +#: ./doc/common/tables/glance-db.xml38(td) +msgid "" +"(StrOpt) The SQLAlchemy connection string used to connect to the database" +msgstr "" + +#: ./doc/common/tables/nova-db.xml52(td) +#: ./doc/common/tables/cinder-connection.xml26(td) +#: ./doc/common/tables/neutron-db.xml27(td) +#: ./doc/common/tables/glance-db.xml41(td) +msgid "connection_debug = 0" +msgstr "" + +#: ./doc/common/tables/nova-db.xml53(td) +#: ./doc/common/tables/cinder-connection.xml27(td) +#: ./doc/common/tables/neutron-db.xml28(td) +#: ./doc/common/tables/glance-db.xml42(td) +msgid "" +"(IntOpt) Verbosity of SQL debugging information. 0=None, 100=Everything" +msgstr "" + +#: ./doc/common/tables/nova-db.xml56(td) +#: ./doc/common/tables/cinder-connection.xml30(td) +#: ./doc/common/tables/neutron-db.xml31(td) +#: ./doc/common/tables/glance-db.xml45(td) +msgid "connection_trace = False" +msgstr "" + +#: ./doc/common/tables/nova-db.xml57(td) +#: ./doc/common/tables/cinder-connection.xml31(td) +#: ./doc/common/tables/neutron-db.xml32(td) +#: ./doc/common/tables/glance-db.xml46(td) +msgid "(BoolOpt) Add python stack traces to SQL as comment strings" +msgstr "" + +#: ./doc/common/tables/nova-db.xml60(td) +#: ./doc/common/tables/cinder-common.xml241(td) +#: ./doc/common/tables/neutron-db.xml39(td) +#: ./doc/common/tables/glance-db.xml49(td) +msgid "idle_timeout = 3600" +msgstr "" + +#: ./doc/common/tables/nova-db.xml61(td) +#: ./doc/common/tables/cinder-common.xml242(td) +#: ./doc/common/tables/neutron-db.xml40(td) +#: ./doc/common/tables/glance-db.xml50(td) +msgid "(IntOpt) timeout before idle sql connections are reaped" +msgstr "" + +#: ./doc/common/tables/nova-db.xml64(td) +#: ./doc/common/tables/cinder-storage.xml145(td) +#: ./doc/common/tables/glance-db.xml53(td) +msgid "max_overflow = None" +msgstr "" + +#: ./doc/common/tables/nova-db.xml65(td) +#: ./doc/common/tables/cinder-storage.xml146(td) +#: ./doc/common/tables/neutron-db.xml44(td) +#: ./doc/common/tables/glance-db.xml54(td) +msgid "(IntOpt) If set, use this value for max_overflow with sqlalchemy" +msgstr "" + +#: ./doc/common/tables/nova-db.xml68(td) +#: ./doc/common/tables/glance-db.xml57(td) +msgid "max_pool_size = None" +msgstr "" + +#: ./doc/common/tables/nova-db.xml69(td) +#: ./doc/common/tables/cinder-storage.xml150(td) +#: ./doc/common/tables/neutron-db.xml48(td) +#: ./doc/common/tables/glance-db.xml58(td) +msgid "(IntOpt) Maximum number of SQL connections to keep open in a pool" +msgstr "" + +#: ./doc/common/tables/nova-db.xml72(td) +#: ./doc/common/tables/cinder-storage.xml153(td) +#: ./doc/common/tables/neutron-db.xml51(td) +#: ./doc/common/tables/glance-db.xml61(td) +msgid "max_retries = 10" +msgstr "" + +#: ./doc/common/tables/nova-db.xml73(td) +#: ./doc/common/tables/cinder-storage.xml154(td) +#: ./doc/common/tables/neutron-db.xml52(td) +#: ./doc/common/tables/glance-db.xml62(td) +msgid "" +"(IntOpt) maximum db connection retries during startup. (setting -1 implies " +"an infinite retry count)" +msgstr "" + +#: ./doc/common/tables/nova-db.xml76(td) +#: ./doc/common/tables/cinder-storage.xml157(td) +#: ./doc/common/tables/neutron-db.xml55(td) +#: ./doc/common/tables/glance-db.xml65(td) +msgid "min_pool_size = 1" +msgstr "" + +#: ./doc/common/tables/nova-db.xml77(td) +#: ./doc/common/tables/cinder-storage.xml158(td) +#: ./doc/common/tables/neutron-db.xml56(td) +#: ./doc/common/tables/glance-db.xml66(td) +msgid "(IntOpt) Minimum number of SQL connections to keep open in a pool" +msgstr "" + +#: ./doc/common/tables/nova-db.xml80(td) +#: ./doc/common/tables/glance-db.xml69(td) +msgid "pool_timeout = None" +msgstr "" + +#: ./doc/common/tables/nova-db.xml81(td) +#: ./doc/common/tables/neutron-db.xml60(td) +#: ./doc/common/tables/glance-db.xml70(td) +msgid "(IntOpt) If set, use this value for pool_timeout with sqlalchemy" +msgstr "" + +#: ./doc/common/tables/nova-db.xml84(td) +#: ./doc/common/tables/cinder-common.xml245(td) +#: ./doc/common/tables/neutron-db.xml63(td) +#: ./doc/common/tables/glance-db.xml73(td) +msgid "retry_interval = 10" +msgstr "" + +#: ./doc/common/tables/nova-db.xml85(td) +#: ./doc/common/tables/cinder-common.xml246(td) +#: ./doc/common/tables/neutron-db.xml64(td) +#: ./doc/common/tables/glance-db.xml74(td) +msgid "(IntOpt) interval between retries of opening a sql connection" +msgstr "" + +#: ./doc/common/tables/nova-db.xml88(td) +#: ./doc/common/tables/neutron-db.xml67(td) +#: ./doc/common/tables/glance-db.xml77(td) +msgid "slave_connection =" +msgstr "" + +#: ./doc/common/tables/nova-db.xml89(td) +#: ./doc/common/tables/neutron-db.xml68(td) +#: ./doc/common/tables/glance-db.xml78(td) +msgid "" +"(StrOpt) The SQLAlchemy connection string used to connect to the slave " +"database" +msgstr "" + +#: ./doc/common/tables/neutron-ml2_vxlan.xml8(caption) +msgid "Description of configuration options for ml2_vxlan" +msgstr "" + +#: ./doc/common/tables/neutron-ml2_vxlan.xml19(td) +msgid "vni_ranges =" +msgstr "" + +#: ./doc/common/tables/neutron-ml2_vxlan.xml20(td) +msgid "" +"(ListOpt) Comma-separated list of <vni_min>:<vni_max> tuples " +"enumerating ranges of VXLAN VNI IDs that are available for tenant network " +"allocation" +msgstr "" + +#: ./doc/common/tables/neutron-ml2_vxlan.xml23(td) +msgid "vxlan_group = None" +msgstr "" + +#: ./doc/common/tables/neutron-ml2_vxlan.xml24(td) +msgid "" +"(StrOpt) Multicast group for VXLAN. If unset, disables VXLAN multicast mode." +msgstr "" + +#: ./doc/common/tables/glance-logging.xml8(caption) +#: ./doc/common/tables/neutron-logging.xml8(caption) +#: ./doc/common/tables/nova-logging.xml8(caption) +msgid "Description of configuration options for logging" +msgstr "" + +#: ./doc/common/tables/glance-logging.xml22(td) +#: ./doc/common/tables/neutron-logging.xml19(td) +#: ./doc/common/tables/nova-logging.xml22(td) +#: ./doc/common/tables/cinder-common.xml26(td) +msgid "debug = False" +msgstr "" + +#: ./doc/common/tables/glance-logging.xml23(td) +#: ./doc/common/tables/neutron-logging.xml20(td) +#: ./doc/common/tables/nova-logging.xml23(td) +#: ./doc/common/tables/cinder-common.xml27(td) +msgid "" +"(BoolOpt) Print debugging output (set logging level to DEBUG instead of " +"default WARNING level)." +msgstr "" + +#: ./doc/common/tables/glance-logging.xml26(td) +#: ./doc/common/tables/neutron-logging.xml23(td) +#: ./doc/common/tables/nova-logging.xml26(td) +#: ./doc/common/tables/cinder-common.xml34(td) +msgid "" +"default_log_levels = amqp=WARN, amqplib=WARN, boto=WARN, keystone=INFO, " +"qpid=WARN, sqlalchemy=WARN, suds=INFO, iso8601=WARN" +msgstr "" + +#: ./doc/common/tables/glance-logging.xml27(td) +#: ./doc/common/tables/neutron-logging.xml24(td) +#: ./doc/common/tables/nova-logging.xml27(td) +#: ./doc/common/tables/cinder-common.xml35(td) +msgid "(ListOpt) list of logger=LEVEL pairs" +msgstr "" + +#: ./doc/common/tables/glance-logging.xml30(td) +#: ./doc/common/tables/neutron-logging.xml27(td) +#: ./doc/common/tables/nova-logging.xml30(td) +#: ./doc/common/tables/cinder-common.xml58(td) +msgid "fatal_deprecations = False" +msgstr "" + +#: ./doc/common/tables/glance-logging.xml31(td) +#: ./doc/common/tables/neutron-logging.xml28(td) +#: ./doc/common/tables/nova-logging.xml31(td) +#: ./doc/common/tables/cinder-common.xml59(td) +msgid "(BoolOpt) make deprecations fatal" +msgstr "" + +#: ./doc/common/tables/glance-logging.xml34(td) +#: ./doc/common/tables/cinder-images.xml62(td) +#: ./doc/common/tables/nova-logging.xml38(td) +msgid "instance_format = \"[instance: %(uuid)s] \"" +msgstr "" + +#: ./doc/common/tables/glance-logging.xml35(td) +#: ./doc/common/tables/cinder-images.xml63(td) +#: ./doc/common/tables/neutron-logging.xml32(td) +#: ./doc/common/tables/nova-logging.xml39(td) +msgid "" +"(StrOpt) If an instance is passed with the log message, format it like this" +msgstr "" + +#: ./doc/common/tables/glance-logging.xml38(td) +#: ./doc/common/tables/cinder-images.xml66(td) +#: ./doc/common/tables/nova-logging.xml42(td) +msgid "instance_uuid_format = \"[instance: %(uuid)s] \"" +msgstr "" + +#: ./doc/common/tables/glance-logging.xml39(td) +#: ./doc/common/tables/cinder-images.xml67(td) +#: ./doc/common/tables/neutron-logging.xml36(td) +#: ./doc/common/tables/nova-logging.xml43(td) +msgid "" +"(StrOpt) If an instance UUID is passed with the log message, format it like " +"this" +msgstr "" + +#: ./doc/common/tables/glance-logging.xml42(td) +#: ./doc/common/tables/nova-logging.xml46(td) +#: ./doc/common/tables/cinder-common.xml82(td) +msgid "log-config-append = None" +msgstr "" + +#: ./doc/common/tables/glance-logging.xml43(td) +#: ./doc/common/tables/neutron-logging.xml40(td) +#: ./doc/common/tables/nova-logging.xml47(td) +#: ./doc/common/tables/cinder-common.xml83(td) +msgid "" +"(StrOpt) The name of logging configuration file. It does not disable " +"existing loggers, but just appends specified logging configuration to any " +"other existing logging options. Please see the Python logging module " +"documentation for details on logging configuration files." +msgstr "" + +#: ./doc/common/tables/glance-logging.xml46(td) +#: ./doc/common/tables/nova-logging.xml50(td) +#: ./doc/common/tables/cinder-common.xml86(td) +msgid "log-date-format = %Y-%m-%d %H:%M:%S" +msgstr "" + +#: ./doc/common/tables/glance-logging.xml47(td) +#: ./doc/common/tables/neutron-logging.xml44(td) +#: ./doc/common/tables/nova-logging.xml51(td) +#: ./doc/common/tables/cinder-common.xml87(td) +msgid "" +"(StrOpt) Format string for %%(asctime)s in log records. Default: %(default)s" +msgstr "" + +#: ./doc/common/tables/glance-logging.xml50(td) +#: ./doc/common/tables/nova-logging.xml54(td) +#: ./doc/common/tables/cinder-common.xml90(td) +msgid "log-dir = None" +msgstr "" + +#: ./doc/common/tables/glance-logging.xml51(td) +#: ./doc/common/tables/neutron-logging.xml48(td) +#: ./doc/common/tables/nova-logging.xml55(td) +#: ./doc/common/tables/cinder-common.xml91(td) +msgid "" +"(StrOpt) (Optional) The base directory used for relative --log-file paths" +msgstr "" + +#: ./doc/common/tables/glance-logging.xml54(td) +#: ./doc/common/tables/nova-logging.xml58(td) +#: ./doc/common/tables/cinder-common.xml94(td) +msgid "log-file = None" +msgstr "" + +#: ./doc/common/tables/glance-logging.xml55(td) +#: ./doc/common/tables/neutron-logging.xml52(td) +#: ./doc/common/tables/nova-logging.xml59(td) +#: ./doc/common/tables/cinder-common.xml95(td) +msgid "" +"(StrOpt) (Optional) Name of log file to output to. If no default is set, " +"logging will go to stdout." +msgstr "" + +#: ./doc/common/tables/glance-logging.xml58(td) +#: ./doc/common/tables/nova-logging.xml62(td) +#: ./doc/common/tables/cinder-common.xml98(td) +msgid "log-format = None" +msgstr "" + +#: ./doc/common/tables/glance-logging.xml59(td) +#: ./doc/common/tables/neutron-logging.xml56(td) +#: ./doc/common/tables/nova-logging.xml63(td) +#: ./doc/common/tables/cinder-common.xml99(td) +msgid "" +"(StrOpt) DEPRECATED. A logging.Formatter log message format string which may" +" use any of the available logging.LogRecord attributes. This option is " +"deprecated. Please use logging_context_format_string and " +"logging_default_format_string instead." +msgstr "" + +#: ./doc/common/tables/glance-logging.xml62(td) +#: ./doc/common/tables/neutron-logging.xml59(td) +#: ./doc/common/tables/nova-logging.xml66(td) +#: ./doc/common/tables/cinder-common.xml102(td) +msgid "" +"logging_context_format_string = %(asctime)s.%(msecs)03d %(process)d " +"%(levelname)s %(name)s [%(request_id)s %(user)s %(tenant)s] " +"%(instance)s%(message)s" +msgstr "" + +#: ./doc/common/tables/glance-logging.xml63(td) +#: ./doc/common/tables/neutron-logging.xml60(td) +#: ./doc/common/tables/nova-logging.xml67(td) +#: ./doc/common/tables/cinder-common.xml103(td) +msgid "(StrOpt) format string to use for log messages with context" +msgstr "" + +#: ./doc/common/tables/glance-logging.xml66(td) +#: ./doc/common/tables/neutron-logging.xml63(td) +#: ./doc/common/tables/nova-logging.xml70(td) +#: ./doc/common/tables/cinder-common.xml106(td) +msgid "logging_debug_format_suffix = %(funcName)s %(pathname)s:%(lineno)d" +msgstr "" + +#: ./doc/common/tables/glance-logging.xml67(td) +#: ./doc/common/tables/neutron-logging.xml64(td) +#: ./doc/common/tables/nova-logging.xml71(td) +#: ./doc/common/tables/cinder-common.xml107(td) +msgid "(StrOpt) data to append to log format when level is DEBUG" +msgstr "" + +#: ./doc/common/tables/glance-logging.xml70(td) +#: ./doc/common/tables/neutron-logging.xml67(td) +#: ./doc/common/tables/nova-logging.xml74(td) +#: ./doc/common/tables/cinder-common.xml110(td) +msgid "" +"logging_default_format_string = %(asctime)s.%(msecs)03d %(process)d " +"%(levelname)s %(name)s [-] %(instance)s%(message)s" +msgstr "" + +#: ./doc/common/tables/glance-logging.xml71(td) +#: ./doc/common/tables/neutron-logging.xml68(td) +#: ./doc/common/tables/nova-logging.xml75(td) +#: ./doc/common/tables/cinder-common.xml111(td) +msgid "(StrOpt) format string to use for log messages without context" +msgstr "" + +#: ./doc/common/tables/glance-logging.xml74(td) +#: ./doc/common/tables/neutron-logging.xml71(td) +#: ./doc/common/tables/nova-logging.xml78(td) +#: ./doc/common/tables/cinder-common.xml114(td) +msgid "" +"logging_exception_prefix = %(asctime)s.%(msecs)03d %(process)d TRACE " +"%(name)s %(instance)s" +msgstr "" + +#: ./doc/common/tables/glance-logging.xml75(td) +#: ./doc/common/tables/neutron-logging.xml72(td) +#: ./doc/common/tables/nova-logging.xml79(td) +#: ./doc/common/tables/cinder-common.xml115(td) +msgid "(StrOpt) prefix each line of exception output with this format" +msgstr "" + +#: ./doc/common/tables/glance-logging.xml82(td) +#: ./doc/common/tables/nova-logging.xml86(td) +#: ./doc/common/tables/cinder-common.xml210(td) +msgid "syslog-log-facility = LOG_USER" +msgstr "" + +#: ./doc/common/tables/glance-logging.xml83(td) +#: ./doc/common/tables/neutron-logging.xml80(td) +#: ./doc/common/tables/nova-logging.xml87(td) +#: ./doc/common/tables/cinder-common.xml211(td) +msgid "(StrOpt) syslog facility to receive log lines" +msgstr "" + +#: ./doc/common/tables/glance-logging.xml86(td) +#: ./doc/common/tables/nova-logging.xml90(td) +#: ./doc/common/tables/cinder-common.xml222(td) +msgid "use-syslog = False" +msgstr "" + +#: ./doc/common/tables/glance-logging.xml87(td) +#: ./doc/common/tables/neutron-logging.xml88(td) +#: ./doc/common/tables/nova-logging.xml91(td) +#: ./doc/common/tables/cinder-common.xml223(td) +msgid "(BoolOpt) Use syslog for logging." +msgstr "" + +#: ./doc/common/tables/glance-logging.xml90(td) +#: ./doc/common/tables/neutron-logging.xml83(td) +#: ./doc/common/tables/nova-logging.xml94(td) +#: ./doc/common/tables/cinder-common.xml230(td) +msgid "use_stderr = True" +msgstr "" + +#: ./doc/common/tables/glance-logging.xml91(td) +#: ./doc/common/tables/neutron-logging.xml84(td) +#: ./doc/common/tables/nova-logging.xml95(td) +#: ./doc/common/tables/cinder-common.xml231(td) +msgid "(BoolOpt) Log output to standard error" +msgstr "" + +#: ./doc/common/tables/glance-logging.xml94(td) +#: ./doc/common/tables/neutron-logging.xml91(td) +#: ./doc/common/tables/nova-logging.xml98(td) +#: ./doc/common/tables/cinder-common.xml234(td) +msgid "verbose = False" +msgstr "" + +#: ./doc/common/tables/glance-logging.xml95(td) +#: ./doc/common/tables/neutron-logging.xml92(td) +#: ./doc/common/tables/nova-logging.xml99(td) +#: ./doc/common/tables/cinder-common.xml235(td) +msgid "" +"(BoolOpt) Print more verbose output (set logging level to INFO instead of " +"default WARNING level)." +msgstr "" + +#: ./doc/common/tables/glance-wsgi.xml8(caption) +#: ./doc/common/tables/neutron-wsgi.xml8(caption) +#: ./doc/common/tables/nova-wsgi.xml8(caption) +msgid "Description of configuration options for wsgi" +msgstr "" + +#: ./doc/common/tables/glance-wsgi.xml23(td) +#: ./doc/common/tables/neutron-testing.xml20(td) +msgid "(IntOpt) port for eventlet backdoor to listen" +msgstr "" + +#: ./doc/common/tables/glance-wsgi.xml26(td) +msgid "eventlet_hub = poll" +msgstr "" + +#: ./doc/common/tables/glance-wsgi.xml27(td) +msgid "" +"(StrOpt) Name of eventlet hub to use. Traditionally, we have only supported " +"'poll', however 'selects' may be appropriate for some platforms. See " +"http://eventlet.net/doc/hubs.html for more details." +msgstr "" + +#: ./doc/common/tables/glance-wsgi.xml30(td) +msgid "max_header_line = 16384" +msgstr "" + +#: ./doc/common/tables/glance-wsgi.xml31(td) +msgid "" +"(IntOpt) Maximum line size of message headers to be accepted. " +"max_header_line may need to be increased when using large tokens (typically " +"those generated by the Keystone v3 API with big service catalogs" +msgstr "" + +#: ./doc/common/tables/glance-wsgi.xml34(td) +#: ./doc/common/tables/neutron-wsgi.xml27(td) +#: ./doc/common/tables/nova-wsgi.xml38(td) +#: ./doc/common/tables/cinder-common.xml214(td) +msgid "tcp_keepidle = 600" +msgstr "" + +#: ./doc/common/tables/glance-wsgi.xml35(td) +msgid "" +"(IntOpt) The value for the socket option TCP_KEEPIDLE. This is the time in " +"seconds that the connection must be idle before TCP starts sending keepalive" +" probes." +msgstr "" + +#: ./doc/common/tables/nova-periodic.xml8(caption) +msgid "Description of configuration options for periodic" +msgstr "" + +#: ./doc/common/tables/nova-periodic.xml22(td) +msgid "periodic_enable = True" +msgstr "" + +#: ./doc/common/tables/nova-periodic.xml23(td) +msgid "(BoolOpt) enable periodic tasks" +msgstr "" + +#: ./doc/common/tables/nova-periodic.xml26(td) +#: ./doc/common/tables/cinder-common.xml138(td) +msgid "periodic_fuzzy_delay = 60" +msgstr "" + +#: ./doc/common/tables/nova-periodic.xml27(td) +#: ./doc/common/tables/cinder-common.xml139(td) +msgid "" +"(IntOpt) range of seconds to randomly delay when starting the periodic task " +"scheduler to reduce stampeding. (Disable by setting to 0)" +msgstr "" + +#: ./doc/common/tables/cinder-images.xml8(caption) +msgid "Description of configuration options for images" +msgstr "" + +#: ./doc/common/tables/cinder-images.xml23(td) +msgid "" +"(ListOpt) A list of url schemes that can be downloaded directly via the " +"direct_url. Currently supported schemes: [file]." +msgstr "" + +#: ./doc/common/tables/cinder-images.xml31(td) +msgid "" +"(ListOpt) A list of the glance api servers available to cinder " +"([hostname|ip]:port)" +msgstr "" + +#: ./doc/common/tables/cinder-images.xml34(td) +msgid "glance_api_ssl_compression = False" +msgstr "" + +#: ./doc/common/tables/cinder-images.xml35(td) +msgid "" +"(BoolOpt) Whether to attempt to negotiate SSL layer compression when using " +"SSL (https) requests. Set to False to disable SSL layer compression. In some" +" cases disabling this may improve data throughput, eg when high network " +"bandwidth is available and you are using already compressed image formats " +"such as qcow2 ." +msgstr "" + +#: ./doc/common/tables/cinder-images.xml38(td) +msgid "glance_api_version = 1" +msgstr "" + +#: ./doc/common/tables/cinder-images.xml39(td) +msgid "(IntOpt) Version of the glance api to use" +msgstr "" + +#: ./doc/common/tables/cinder-images.xml54(td) +msgid "glance_request_timeout = None" +msgstr "" + +#: ./doc/common/tables/cinder-images.xml55(td) +msgid "" +"(IntOpt) http/https timeout value for glance operations. If no value (None) " +"is supplied here, the glanceclient default value is used." +msgstr "" + +#: ./doc/common/tables/cinder-images.xml58(td) +msgid "image_conversion_dir = $state_path/conversion" +msgstr "" + +#: ./doc/common/tables/cinder-images.xml59(td) +msgid "(StrOpt) Directory used for temporary storage during image conversion" +msgstr "" + +#: ./doc/common/tables/cinder-images.xml70(td) +msgid "use_multipath_for_image_xfer = False" +msgstr "" + +#: ./doc/common/tables/cinder-images.xml71(td) +msgid "" +"(BoolOpt) Do we attach/detach volumes in cinder using multipath for volume " +"to image and image to volume transfers?" +msgstr "" + +#: ./doc/common/tables/swift-container-server-app-container-server.xml7(literal) +msgid "[app:container-server]" +msgstr "" + +#: ./doc/common/tables/swift-container-server-app-container-server.xml18(td) +msgid "use = egg:swift#container" +msgstr "" + +#: ./doc/common/tables/swift-container-server-app-container-server.xml21(td) +msgid "set log_name = container-server" +msgstr "" + +#: ./doc/common/tables/swift-container-server-app-container-server.xml42(td) +msgid "allow_versions = false" +msgstr "" + +#: ./doc/common/tables/swift-container-server-app-container-server.xml42(td) +msgid "Enable/Disable object versioning feature" +msgstr "" + +#: ./doc/common/tables/swift-proxy-server-filter-slo.xml7(literal) +msgid "[filter:slo]" +msgstr "" + +#: ./doc/common/tables/swift-proxy-server-filter-slo.xml18(td) +msgid "use = egg:swift#slo" +msgstr "" + +#: ./doc/common/tables/swift-proxy-server-filter-slo.xml21(td) +msgid "max_manifest_segments = 1000" +msgstr "" + +#: ./doc/common/tables/swift-proxy-server-filter-slo.xml24(td) +msgid "max_manifest_size = 2097152" +msgstr "" + +#: ./doc/common/tables/swift-proxy-server-filter-slo.xml27(td) +msgid "min_segment_size = 1048576" +msgstr "" + +#: ./doc/common/tables/neutron-wsgi.xml20(td) +#: ./doc/common/tables/cinder-log.xml23(td) +msgid "(IntOpt) Number of backlog requests to configure the socket with" +msgstr "" + +#: ./doc/common/tables/neutron-wsgi.xml23(td) +msgid "retry_until_window = 30" +msgstr "" + +#: ./doc/common/tables/neutron-wsgi.xml24(td) +msgid "(IntOpt) Number of seconds to keep retrying to listen" +msgstr "" + +#: ./doc/common/tables/neutron-wsgi.xml28(td) +#: ./doc/common/tables/nova-wsgi.xml39(td) +#: ./doc/common/tables/cinder-common.xml215(td) +msgid "" +"(IntOpt) Sets the value of TCP_KEEPIDLE in seconds for each server socket. " +"Not supported on OS X." +msgstr "" + +#: ./doc/common/tables/neutron-scheduler.xml8(caption) +#: ./doc/common/tables/cinder-scheduler.xml8(caption) +msgid "Description of configuration options for scheduler" +msgstr "" + +#: ./doc/common/tables/neutron-scheduler.xml19(td) +msgid "network_auto_schedule = True" +msgstr "" + +#: ./doc/common/tables/neutron-scheduler.xml20(td) +msgid "(BoolOpt) Allow auto scheduling networks to DHCP agent." +msgstr "" + +#: ./doc/common/tables/neutron-scheduler.xml23(td) +msgid "" +"network_scheduler_driver = " +"neutron.scheduler.dhcp_agent_scheduler.ChanceScheduler" +msgstr "" + +#: ./doc/common/tables/neutron-scheduler.xml24(td) +msgid "(StrOpt) Driver to use for scheduling network to DHCP agent" +msgstr "" + +#: ./doc/common/tables/neutron-scheduler.xml27(td) +msgid "router_auto_schedule = True" +msgstr "" + +#: ./doc/common/tables/neutron-scheduler.xml28(td) +msgid "(BoolOpt) Allow auto scheduling of routers to L3 agent." +msgstr "" + +#: ./doc/common/tables/neutron-scheduler.xml31(td) +msgid "" +"router_scheduler_driver = " +"neutron.scheduler.l3_agent_scheduler.ChanceScheduler" +msgstr "" + +#: ./doc/common/tables/neutron-scheduler.xml32(td) +msgid "(StrOpt) Driver to use for scheduling router to a default L3 agent" +msgstr "" + +#: ./doc/common/tables/glance-rbd.xml8(caption) +msgid "Description of configuration options for rbd" +msgstr "" + +#: ./doc/common/tables/glance-rbd.xml22(td) +msgid "rbd_store_ceph_conf = /etc/ceph/ceph.conf" +msgstr "" + +#: ./doc/common/tables/glance-rbd.xml23(td) +msgid "" +"(StrOpt) Ceph configuration file path. If <None>, librados will locate" +" the default config. If using cephx authentication, this file should include" +" a reference to the right keyring in a client.<USER> section" +msgstr "" + +#: ./doc/common/tables/glance-rbd.xml26(td) +msgid "rbd_store_chunk_size = 8" +msgstr "" + +#: ./doc/common/tables/glance-rbd.xml27(td) +msgid "" +"(IntOpt) RADOS images will be chunked into objects of this size (in " +"megabytes). For best performance, this should be a power of two." +msgstr "" + +#: ./doc/common/tables/glance-rbd.xml30(td) +msgid "rbd_store_pool = images" +msgstr "" + +#: ./doc/common/tables/glance-rbd.xml31(td) +msgid "(StrOpt) RADOS pool in which images are stored." +msgstr "" + +#: ./doc/common/tables/glance-rbd.xml34(td) +msgid "rbd_store_user = None" +msgstr "" + +#: ./doc/common/tables/glance-rbd.xml35(td) +msgid "" +"(StrOpt) RADOS user to authenticate as (only applicable if using Cephx. If " +"<None>, a default will be chosen based on the client. section in " +"rbd_store_ceph_conf)" +msgstr "" + +#: ./doc/common/tables/cinder-hp3par.xml8(caption) +msgid "Description of configuration options for hp3par" +msgstr "" + +#: ./doc/common/tables/cinder-hp3par.xml22(td) +msgid "hp3par_api_url =" +msgstr "" + +#: ./doc/common/tables/cinder-hp3par.xml23(td) +msgid "" +"(StrOpt) 3PAR WSAPI Server Url like https://<3par ip>:8080/api/v1" +msgstr "" + +#: ./doc/common/tables/cinder-hp3par.xml26(td) +msgid "hp3par_cpg = OpenStack" +msgstr "" + +#: ./doc/common/tables/cinder-hp3par.xml27(td) +msgid "(StrOpt) The CPG to use for volume creation" +msgstr "" + +#: ./doc/common/tables/cinder-hp3par.xml30(td) +msgid "hp3par_cpg_snap =" +msgstr "" + +#: ./doc/common/tables/cinder-hp3par.xml31(td) +msgid "" +"(StrOpt) The CPG to use for Snapshots for volumes. If empty hp3par_cpg will " +"be used" +msgstr "" + +#: ./doc/common/tables/cinder-hp3par.xml34(td) +msgid "hp3par_debug = False" +msgstr "" + +#: ./doc/common/tables/cinder-hp3par.xml35(td) +msgid "(BoolOpt) Enable HTTP debugging to 3PAR" +msgstr "" + +#: ./doc/common/tables/cinder-hp3par.xml38(td) +msgid "hp3par_iscsi_ips =" +msgstr "" + +#: ./doc/common/tables/cinder-hp3par.xml39(td) +msgid "(ListOpt) List of target iSCSI addresses to use." +msgstr "" + +#: ./doc/common/tables/cinder-hp3par.xml42(td) +msgid "hp3par_password =" +msgstr "" + +#: ./doc/common/tables/cinder-hp3par.xml43(td) +msgid "(StrOpt) 3PAR Super user password" +msgstr "" + +#: ./doc/common/tables/cinder-hp3par.xml46(td) +msgid "hp3par_snapshot_expiration =" +msgstr "" + +#: ./doc/common/tables/cinder-hp3par.xml47(td) +msgid "" +"(StrOpt) The time in hours when a snapshot expires and is deleted. This must" +" be larger than expiration" +msgstr "" + +#: ./doc/common/tables/cinder-hp3par.xml50(td) +msgid "hp3par_snapshot_retention =" +msgstr "" + +#: ./doc/common/tables/cinder-hp3par.xml51(td) +msgid "" +"(StrOpt) The time in hours to retain a snapshot. You can't delete it before " +"this expires." +msgstr "" + +#: ./doc/common/tables/cinder-hp3par.xml54(td) +msgid "hp3par_username =" +msgstr "" + +#: ./doc/common/tables/cinder-hp3par.xml55(td) +msgid "(StrOpt) 3PAR Super user username" +msgstr "" + +#: ./doc/common/tables/cinder-storage_ceph.xml8(caption) +msgid "Description of configuration options for storage_ceph" +msgstr "" + +#: ./doc/common/tables/cinder-storage_ceph.xml22(td) +msgid "rbd_ceph_conf =" +msgstr "" + +#: ./doc/common/tables/cinder-storage_ceph.xml26(td) +msgid "rbd_flatten_volume_from_snapshot = False" +msgstr "" + +#: ./doc/common/tables/cinder-storage_ceph.xml27(td) +msgid "(BoolOpt) flatten volumes created from snapshots to remove dependency" +msgstr "" + +#: ./doc/common/tables/cinder-storage_ceph.xml30(td) +msgid "rbd_max_clone_depth = 5" +msgstr "" + +#: ./doc/common/tables/cinder-storage_ceph.xml31(td) +msgid "" +"(IntOpt) maximum number of nested clones that can be taken of a volume " +"before enforcing a flatten prior to next clone. A value of zero disables " +"cloning" +msgstr "" + +#: ./doc/common/tables/cinder-storage_ceph.xml34(td) +msgid "rbd_pool = rbd" +msgstr "" + +#: ./doc/common/tables/cinder-storage_ceph.xml43(td) +msgid "" +"(StrOpt) the RADOS client name for accessing rbd volumes - only set when " +"using cephx authentication" +msgstr "" + +#: ./doc/common/tables/cinder-storage_ceph.xml46(td) +msgid "volume_tmp_dir = None" +msgstr "" + +#: ./doc/common/tables/cinder-storage_ceph.xml47(td) +msgid "" +"(StrOpt) where to store temporary image files if the volume driver does not " +"write them directly to the volume" +msgstr "" + +#: ./doc/common/tables/nova-livemigration.xml8(caption) +msgid "Description of configuration options for livemigration" +msgstr "" + +#: ./doc/common/tables/nova-livemigration.xml22(td) +msgid "live_migration_retry_count = 30" +msgstr "" + +#: ./doc/common/tables/nova-livemigration.xml23(td) +msgid "(IntOpt) Number of 1 second retries needed in live_migration" +msgstr "" + +#: ./doc/common/tables/nova-livemigration.xml29(td) +msgid "live_migration_bandwidth = 0" +msgstr "" + +#: ./doc/common/tables/nova-livemigration.xml30(td) +msgid "(IntOpt) Maximum bandwidth to be used during migration, in Mbps" +msgstr "" + +#: ./doc/common/tables/nova-livemigration.xml33(td) +msgid "" +"live_migration_flag = VIR_MIGRATE_UNDEFINE_SOURCE, VIR_MIGRATE_PEER2PEER" +msgstr "" + +#: ./doc/common/tables/nova-livemigration.xml34(td) +msgid "(StrOpt) Migration flags to be set for live migration" +msgstr "" + +#: ./doc/common/tables/nova-livemigration.xml37(td) +msgid "live_migration_uri = qemu+tcp://%s/system" +msgstr "" + +#: ./doc/common/tables/nova-livemigration.xml38(td) +msgid "" +"(StrOpt) Migration target URI (any included \"%s\" is replaced with the " +"migration target hostname)" +msgstr "" + +#: ./doc/common/tables/nova-ldap.xml8(caption) +msgid "Description of configuration options for ldap" +msgstr "" + +#: ./doc/common/tables/nova-ldap.xml22(td) +msgid "ldap_dns_base_dn = ou=hosts,dc=example,dc=org" +msgstr "" + +#: ./doc/common/tables/nova-ldap.xml23(td) +msgid "(StrOpt) Base DN for DNS entries in ldap" +msgstr "" + +#: ./doc/common/tables/nova-ldap.xml26(td) +msgid "ldap_dns_password = password" +msgstr "" + +#: ./doc/common/tables/nova-ldap.xml27(td) +msgid "(StrOpt) password for ldap DNS" +msgstr "" + +#: ./doc/common/tables/nova-ldap.xml30(td) +msgid "ldap_dns_servers = ['dns.example.org']" +msgstr "" + +#: ./doc/common/tables/nova-ldap.xml31(td) +msgid "(MultiStrOpt) DNS Servers for ldap dns driver" +msgstr "" + +#: ./doc/common/tables/nova-ldap.xml34(td) +msgid "ldap_dns_soa_expiry = 86400" +msgstr "" + +#: ./doc/common/tables/nova-ldap.xml35(td) +msgid "" +"(StrOpt) Expiry interval (in seconds) for ldap dns driver Statement of " +"Authority" +msgstr "" + +#: ./doc/common/tables/nova-ldap.xml38(td) +msgid "ldap_dns_soa_hostmaster = hostmaster@example.org" +msgstr "" + +#: ./doc/common/tables/nova-ldap.xml39(td) +msgid "(StrOpt) Hostmaster for ldap dns driver Statement of Authority" +msgstr "" + +#: ./doc/common/tables/nova-ldap.xml42(td) +msgid "ldap_dns_soa_minimum = 7200" +msgstr "" + +#: ./doc/common/tables/nova-ldap.xml43(td) +msgid "" +"(StrOpt) Minimum interval (in seconds) for ldap dns driver Statement of " +"Authority" +msgstr "" + +#: ./doc/common/tables/nova-ldap.xml46(td) +msgid "ldap_dns_soa_refresh = 1800" +msgstr "" + +#: ./doc/common/tables/nova-ldap.xml47(td) +msgid "" +"(StrOpt) Refresh interval (in seconds) for ldap dns driver Statement of " +"Authority" +msgstr "" + +#: ./doc/common/tables/nova-ldap.xml50(td) +msgid "ldap_dns_soa_retry = 3600" +msgstr "" + +#: ./doc/common/tables/nova-ldap.xml51(td) +msgid "" +"(StrOpt) Retry interval (in seconds) for ldap dns driver Statement of " +"Authority" +msgstr "" + +#: ./doc/common/tables/nova-ldap.xml54(td) +msgid "ldap_dns_url = ldap://ldap.example.com:389" +msgstr "" + +#: ./doc/common/tables/nova-ldap.xml55(td) +msgid "(StrOpt) URL for ldap server which will store dns entries" +msgstr "" + +#: ./doc/common/tables/nova-ldap.xml58(td) +msgid "ldap_dns_user = uid=admin,ou=people,dc=example,dc=org" +msgstr "" + +#: ./doc/common/tables/nova-ldap.xml59(td) +msgid "(StrOpt) user for ldap DNS" +msgstr "" + +#: ./doc/common/tables/nova-fping.xml8(caption) +msgid "Description of configuration options for fping" +msgstr "" + +#: ./doc/common/tables/nova-fping.xml22(td) +msgid "fping_path = /usr/sbin/fping" +msgstr "" + +#: ./doc/common/tables/nova-fping.xml23(td) +msgid "(StrOpt) Full path to fping." +msgstr "" + +#: ./doc/common/tables/neutron-securitygroups.xml8(caption) +msgid "Description of configuration options for securitygroups" +msgstr "" + +#: ./doc/common/tables/neutron-securitygroups.xml19(td) +msgid "firewall_driver = neutron.agent.firewall.NoopFirewallDriver" +msgstr "" + +#: ./doc/common/tables/neutron-securitygroups.xml20(td) +msgid "(StrOpt) Driver for Security Groups Firewall" +msgstr "" + +#: ./doc/common/tables/cinder-netapp_cdot_iscsi.xml8(caption) +msgid "Description of configuration options for netapp_cdot_iscsi" +msgstr "" + +#: ./doc/common/tables/cinder-netapp_cdot_iscsi.xml54(td) +#: ./doc/common/tables/cinder-netapp_cdot_nfs.xml54(td) +msgid "netapp_vserver = None" +msgstr "" + +#: ./doc/common/tables/cinder-netapp_cdot_iscsi.xml55(td) +#: ./doc/common/tables/cinder-netapp_cdot_nfs.xml55(td) +msgid "" +"(StrOpt) This option specifies the virtual storage server (Vserver) name on " +"the storage cluster on which provisioning of block storage volumes should " +"occur. If using the NFS storage protocol, this parameter is mandatory for " +"storage service catalog support (utilized by Cinder volume type extra_specs " +"support). If this option is specified, the exports belonging to the Vserver " +"will only be used for provisioning in the future. Block storage volumes on " +"exports not belonging to the Vserver specified by this option will continue " +"to function normally." +msgstr "" + +#: ./doc/common/tables/nova-ec2.xml8(caption) +msgid "Description of configuration options for ec2" +msgstr "" + +#: ./doc/common/tables/nova-ec2.xml22(td) +msgid "ec2_dmz_host = $my_ip" +msgstr "" + +#: ./doc/common/tables/nova-ec2.xml23(td) +msgid "(StrOpt) the internal ip of the ec2 api server" +msgstr "" + +#: ./doc/common/tables/nova-ec2.xml26(td) +msgid "ec2_host = $my_ip" +msgstr "" + +#: ./doc/common/tables/nova-ec2.xml27(td) +msgid "(StrOpt) the ip of the ec2 api server" +msgstr "" + +#: ./doc/common/tables/nova-ec2.xml30(td) +msgid "ec2_listen = 0.0.0.0" +msgstr "" + +#: ./doc/common/tables/nova-ec2.xml31(td) +msgid "(StrOpt) The IP address on which the EC2 API will listen." +msgstr "" + +#: ./doc/common/tables/nova-ec2.xml34(td) +msgid "ec2_listen_port = 8773" +msgstr "" + +#: ./doc/common/tables/nova-ec2.xml35(td) +msgid "(IntOpt) The port on which the EC2 API will listen." +msgstr "" + +#: ./doc/common/tables/nova-ec2.xml38(td) +msgid "ec2_path = /services/Cloud" +msgstr "" + +#: ./doc/common/tables/nova-ec2.xml39(td) +msgid "(StrOpt) the path prefix used to call the ec2 api server" +msgstr "" + +#: ./doc/common/tables/nova-ec2.xml42(td) +msgid "ec2_port = 8773" +msgstr "" + +#: ./doc/common/tables/nova-ec2.xml43(td) +msgid "(IntOpt) the port of the ec2 api server" +msgstr "" + +#: ./doc/common/tables/nova-ec2.xml46(td) +msgid "ec2_private_dns_show_ip = False" +msgstr "" + +#: ./doc/common/tables/nova-ec2.xml47(td) +msgid "" +"(BoolOpt) Return the IP address as private dns hostname in describe " +"instances" +msgstr "" + +#: ./doc/common/tables/nova-ec2.xml50(td) +msgid "ec2_scheme = http" +msgstr "" + +#: ./doc/common/tables/nova-ec2.xml51(td) +msgid "" +"(StrOpt) the protocol to use when connecting to the ec2 api server (http, " +"https)" +msgstr "" + +#: ./doc/common/tables/nova-ec2.xml54(td) +msgid "ec2_strict_validation = True" +msgstr "" + +#: ./doc/common/tables/nova-ec2.xml55(td) +msgid "(BoolOpt) Validate security group names according to EC2 specification" +msgstr "" + +#: ./doc/common/tables/nova-ec2.xml58(td) +msgid "ec2_timestamp_expiry = 300" +msgstr "" + +#: ./doc/common/tables/nova-ec2.xml59(td) +msgid "(IntOpt) Time in seconds before ec2 timestamp expires" +msgstr "" + +#: ./doc/common/tables/nova-ec2.xml62(td) +msgid "ec2_workers = None" +msgstr "" + +#: ./doc/common/tables/nova-ec2.xml63(td) +msgid "(IntOpt) Number of workers for EC2 API service" +msgstr "" + +#: ./doc/common/tables/nova-ec2.xml66(td) +msgid "keystone_ec2_url = http://localhost:5000/v2.0/ec2tokens" +msgstr "" + +#: ./doc/common/tables/nova-ec2.xml67(td) +msgid "(StrOpt) URL to get token from ec2 request." +msgstr "" + +#: ./doc/common/tables/nova-ec2.xml70(td) +msgid "lockout_attempts = 5" +msgstr "" + +#: ./doc/common/tables/nova-ec2.xml71(td) +msgid "(IntOpt) Number of failed auths before lockout." +msgstr "" + +#: ./doc/common/tables/nova-ec2.xml74(td) +msgid "lockout_minutes = 15" +msgstr "" + +#: ./doc/common/tables/nova-ec2.xml75(td) +msgid "(IntOpt) Number of minutes to lockout if triggered." +msgstr "" + +#: ./doc/common/tables/nova-ec2.xml78(td) +msgid "lockout_window = 15" +msgstr "" + +#: ./doc/common/tables/nova-ec2.xml79(td) +msgid "(IntOpt) Number of minutes for lockout window." +msgstr "" + +#: ./doc/common/tables/nova-ec2.xml82(td) +msgid "region_list =" +msgstr "" + +#: ./doc/common/tables/nova-ec2.xml83(td) +msgid "(ListOpt) list of region=fqdn pairs separated by commas" +msgstr "" + +#: ./doc/common/tables/swift-account-server-account-auditor.xml7(literal) +msgid "[account-auditor]" +msgstr "" + +#: ./doc/common/tables/swift-account-server-account-auditor.xml18(td) +msgid "log_name = account-auditor" +msgstr "" + +#: ./doc/common/tables/swift-account-server-account-auditor.xml30(td) +#: ./doc/common/tables/swift-container-server-container-auditor.xml30(td) +msgid "interval = 1800" +msgstr "" + +#: ./doc/common/tables/swift-account-server-account-auditor.xml39(td) +msgid "accounts_per_second = 200" +msgstr "" + +#: ./doc/common/tables/swift-account-server-account-auditor.xml39(td) +msgid "" +"Maximum accounts audited per second. Should be tuned according to individual" +" system specs. 0 is unlimited." +msgstr "" + +#: ./doc/common/tables/swift-object-server-DEFAULT.xml21(td) +msgid "bind_port = 6000" +msgstr "" + +#: ./doc/common/tables/swift-object-server-DEFAULT.xml45(td) +#: ./doc/common/tables/swift-proxy-server-DEFAULT.xml55(td) +msgid "expiring_objects_container_divisor = 86400" +msgstr "" + +#: ./doc/common/tables/cinder-nexenta_nfs.xml8(caption) +msgid "Description of configuration options for nexenta_nfs" +msgstr "" + +#: ./doc/common/tables/cinder-nexenta_nfs.xml22(td) +msgid "nexenta_mount_options = None" +msgstr "" + +#: ./doc/common/tables/cinder-nexenta_nfs.xml26(td) +msgid "nexenta_mount_point_base = $state_path/mnt" +msgstr "" + +#: ./doc/common/tables/cinder-nexenta_nfs.xml27(td) +msgid "(StrOpt) Base dir containing mount points for nfs shares" +msgstr "" + +#: ./doc/common/tables/cinder-nexenta_nfs.xml30(td) +msgid "nexenta_nms_cache_volroot = True" +msgstr "" + +#: ./doc/common/tables/cinder-nexenta_nfs.xml31(td) +msgid "" +"(BoolOpt) If set True cache NexentaStor appliance volroot option value." +msgstr "" + +#: ./doc/common/tables/cinder-nexenta_nfs.xml34(td) +msgid "nexenta_oversub_ratio = 1.0" +msgstr "" + +#: ./doc/common/tables/cinder-nexenta_nfs.xml38(td) +msgid "nexenta_shares_config = /etc/cinder/nfs_shares" +msgstr "" + +#: ./doc/common/tables/cinder-nexenta_nfs.xml42(td) +msgid "nexenta_used_ratio = 0.95" +msgstr "" + +#: ./doc/common/tables/cinder-nexenta_nfs.xml46(td) +msgid "nexenta_volume_compression = on" +msgstr "" + +#: ./doc/common/tables/cinder-nexenta_nfs.xml47(td) +msgid "(StrOpt) Default compression value for new ZFS folders." +msgstr "" + +#: ./doc/common/tables/swift-proxy-server-filter-bulk.xml7(literal) +msgid "[filter:bulk]" +msgstr "" + +#: ./doc/common/tables/swift-proxy-server-filter-bulk.xml18(td) +msgid "use = egg:swift#bulk" +msgstr "" + +#: ./doc/common/tables/swift-proxy-server-filter-bulk.xml21(td) +msgid "max_containers_per_extraction = 10000" +msgstr "" + +#: ./doc/common/tables/swift-proxy-server-filter-bulk.xml24(td) +msgid "max_failed_extractions = 1000" +msgstr "" + +#: ./doc/common/tables/swift-proxy-server-filter-bulk.xml27(td) +msgid "max_deletes_per_request = 10000" +msgstr "" + +#: ./doc/common/tables/swift-proxy-server-filter-bulk.xml30(td) +msgid "yield_frequency = 60" +msgstr "" + +#: ./doc/common/tables/nova-policy.xml22(td) +msgid "allow_instance_snapshots = True" +msgstr "" + +#: ./doc/common/tables/nova-policy.xml23(td) +msgid "(BoolOpt) Permit instance snapshot operations." +msgstr "" + +#: ./doc/common/tables/nova-policy.xml26(td) +msgid "allow_migrate_to_same_host = False" +msgstr "" + +#: ./doc/common/tables/nova-policy.xml27(td) +msgid "" +"(BoolOpt) Allow migrate machine to the same host. Useful when testing in " +"single-host environments." +msgstr "" + +#: ./doc/common/tables/nova-policy.xml30(td) +msgid "allow_resize_to_same_host = False" +msgstr "" + +#: ./doc/common/tables/nova-policy.xml31(td) +msgid "" +"(BoolOpt) Allow destination machine to match source for resize. Useful when " +"testing in single-host environments." +msgstr "" + +#: ./doc/common/tables/nova-policy.xml38(td) +msgid "max_local_block_devices = 3" +msgstr "" + +#: ./doc/common/tables/nova-policy.xml39(td) +msgid "" +"(IntOpt) Maximum number of devices that will result in a local image being " +"created on the hypervisor node. Setting this to 0 means nova will allow only" +" boot from volume. A negative number means unlimited." +msgstr "" + +#: ./doc/common/tables/nova-policy.xml42(td) +msgid "osapi_compute_unique_server_name_scope =" +msgstr "" + +#: ./doc/common/tables/nova-policy.xml43(td) +msgid "" +"(StrOpt) When set, compute API will consider duplicate hostnames invalid " +"within the specified scope, regardless of case. Should be empty, \"project\"" +" or \"global\"." +msgstr "" + +#: ./doc/common/tables/nova-policy.xml51(td) +msgid "(IntOpt) the maximum body size per each osapi request(bytes)" +msgstr "" + +#: ./doc/common/tables/nova-policy.xml54(td) +msgid "password_length = 12" +msgstr "" + +#: ./doc/common/tables/nova-policy.xml55(td) +msgid "(IntOpt) Length of generated instance admin passwords" +msgstr "" + +#: ./doc/common/tables/nova-policy.xml59(td) +#: ./doc/common/tables/cinder-common.xml147(td) +msgid "(StrOpt) Rule checked when requested rule is not found" +msgstr "" + +#: ./doc/common/tables/nova-policy.xml63(td) +#: ./doc/common/tables/cinder-common.xml151(td) +msgid "(StrOpt) JSON file representing policy" +msgstr "" + +#: ./doc/common/tables/nova-policy.xml70(td) +msgid "resize_fs_using_block_device = False" +msgstr "" + +#: ./doc/common/tables/nova-policy.xml71(td) +msgid "" +"(BoolOpt) Attempt to resize the filesystem by accessing the image over a " +"block device. This is done by the host and may not be necessary if the image" +" contains a recent version of cloud-init. Possible mechanisms require the " +"nbd driver (for qcow and raw), or loop (for raw)." +msgstr "" + +#: ./doc/common/tables/nova-policy.xml74(td) +#: ./doc/common/tables/cinder-common.xml218(td) +msgid "until_refresh = 0" +msgstr "" + +#: ./doc/common/tables/nova-policy.xml75(td) +#: ./doc/common/tables/cinder-common.xml219(td) +msgid "(IntOpt) count of reservations until usage is refreshed" +msgstr "" + +#: ./doc/common/tables/neutron-logging.xml31(td) +msgid "instance_format = [instance: %(uuid)s]" +msgstr "" + +#: ./doc/common/tables/neutron-logging.xml35(td) +msgid "instance_uuid_format = [instance: %(uuid)s]" +msgstr "" + +#: ./doc/common/tables/neutron-logging.xml39(td) +msgid "log_config_append = None" +msgstr "" + +#: ./doc/common/tables/neutron-logging.xml43(td) +msgid "log_date_format = %Y-%m-%d %H:%M:%S" +msgstr "" + +#: ./doc/common/tables/neutron-logging.xml47(td) +msgid "log_dir = None" +msgstr "" + +#: ./doc/common/tables/neutron-logging.xml51(td) +msgid "log_file = None" +msgstr "" + +#: ./doc/common/tables/neutron-logging.xml55(td) +msgid "log_format = None" +msgstr "" + +#: ./doc/common/tables/neutron-logging.xml79(td) +msgid "syslog_log_facility = LOG_USER" +msgstr "" + +#: ./doc/common/tables/neutron-logging.xml87(td) +msgid "use_syslog = False" +msgstr "" + +#: ./doc/common/tables/glance-rpc.xml22(td) +msgid "" +"allowed_rpc_exception_modules = openstack.common.exception, " +"glance.common.exception, exceptions" +msgstr "" + +#: ./doc/common/tables/nova-authentication.xml8(caption) +msgid "Description of configuration options for authentication" +msgstr "" + +#: ./doc/common/tables/nova-authentication.xml22(td) +msgid "api_rate_limit = False" +msgstr "" + +#: ./doc/common/tables/nova-authentication.xml23(td) +msgid "" +"(BoolOpt) whether to use per-user rate limiting for the api. This option is " +"only used by v2 api. rate limiting is removed from v3 api." +msgstr "" + +#: ./doc/common/tables/nova-authentication.xml26(td) +#: ./doc/common/tables/glance-registry.xml38(td) +#: ./doc/common/tables/cinder-auth.xml22(td) +msgid "auth_strategy = noauth" +msgstr "" + +#: ./doc/common/tables/nova-authentication.xml27(td) +msgid "(StrOpt) The strategy to use for auth: noauth or keystone." +msgstr "" + +#: ./doc/common/tables/cinder-vmware.xml8(caption) +#: ./doc/common/tables/nova-vmware.xml8(caption) +msgid "Description of configuration options for vmware" +msgstr "" + +#: ./doc/common/tables/cinder-vmware.xml22(td) +msgid "vmware_api_retry_count = 10" +msgstr "" + +#: ./doc/common/tables/cinder-vmware.xml23(td) +msgid "" +"(IntOpt) Number of times VMware ESX/VC server API must be retried upon " +"connection related issues." +msgstr "" + +#: ./doc/common/tables/cinder-vmware.xml26(td) +msgid "vmware_host_ip = None" +msgstr "" + +#: ./doc/common/tables/cinder-vmware.xml27(td) +msgid "(StrOpt) IP address for connecting to VMware ESX/VC server." +msgstr "" + +#: ./doc/common/tables/cinder-vmware.xml30(td) +msgid "vmware_host_password = None" +msgstr "" + +#: ./doc/common/tables/cinder-vmware.xml31(td) +msgid "(StrOpt) Password for authenticating with VMware ESX/VC server." +msgstr "" + +#: ./doc/common/tables/cinder-vmware.xml34(td) +msgid "vmware_host_username = None" +msgstr "" + +#: ./doc/common/tables/cinder-vmware.xml35(td) +msgid "(StrOpt) Username for authenticating with VMware ESX/VC server." +msgstr "" + +#: ./doc/common/tables/cinder-vmware.xml38(td) +msgid "vmware_image_transfer_timeout_secs = 7200" +msgstr "" + +#: ./doc/common/tables/cinder-vmware.xml39(td) +msgid "" +"(IntOpt) Timeout in seconds for VMDK volume transfer between Cinder and " +"Glance." +msgstr "" + +#: ./doc/common/tables/cinder-vmware.xml42(td) +msgid "vmware_max_objects_retrieval = 100" +msgstr "" + +#: ./doc/common/tables/cinder-vmware.xml43(td) +msgid "" +"(IntOpt) Max number of objects to be retrieved per batch. Query results will" +" be obtained in batches from the server and not in one shot. Server may " +"still limit the count to something less than the configured value." +msgstr "" + +#: ./doc/common/tables/cinder-vmware.xml46(td) +msgid "vmware_task_poll_interval = 5" +msgstr "" + +#: ./doc/common/tables/cinder-vmware.xml47(td) +msgid "" +"(IntOpt) The interval used for polling remote tasks invoked on VMware ESX/VC" +" server." +msgstr "" + +#: ./doc/common/tables/cinder-vmware.xml50(td) +msgid "vmware_volume_folder = cinder-volumes" +msgstr "" + +#: ./doc/common/tables/cinder-vmware.xml51(td) +msgid "" +"(StrOpt) Name for the folder in the VC datacenter that will contain cinder " +"volumes." +msgstr "" + +#: ./doc/common/tables/cinder-vmware.xml54(td) +msgid "vmware_wsdl_location = None" +msgstr "" + +#: ./doc/common/tables/cinder-vmware.xml55(td) +msgid "" +"(StrOpt) Optional VIM service WSDL Location e.g " +"http://<server>/vimService.wsdl. Optional over-ride to default " +"location for bug work-arounds." +msgstr "" + +#: ./doc/common/tables/glance-sheepdog.xml8(caption) +msgid "Description of configuration options for sheepdog" +msgstr "" + +#: ./doc/common/tables/glance-sheepdog.xml22(td) +msgid "sheepdog_store_address = localhost" +msgstr "" + +#: ./doc/common/tables/glance-sheepdog.xml23(td) +msgid "(StrOpt) IP address of sheep daemon." +msgstr "" + +#: ./doc/common/tables/glance-sheepdog.xml26(td) +msgid "sheepdog_store_chunk_size = 64" +msgstr "" + +#: ./doc/common/tables/glance-sheepdog.xml27(td) +msgid "" +"(IntOpt) Images will be chunked into objects of this size (in megabytes). " +"For best performance, this should be a power of two." +msgstr "" + +#: ./doc/common/tables/glance-sheepdog.xml30(td) +msgid "sheepdog_store_port = 7000" +msgstr "" + +#: ./doc/common/tables/glance-sheepdog.xml31(td) +msgid "(IntOpt) Port of sheep daemon." +msgstr "" + +#: ./doc/common/tables/neutron-hyperv_agent.xml8(caption) +msgid "Description of configuration options for hyperv_agent" +msgstr "" + +#: ./doc/common/tables/neutron-hyperv_agent.xml19(td) +msgid "enable_metrics_collection = False" +msgstr "" + +#: ./doc/common/tables/neutron-hyperv_agent.xml20(td) +msgid "" +"(BoolOpt) Enables metrics collections for switch ports by using Hyper-V's " +"metric APIs. Collected data can by retrieved by other apps and services, " +"e.g.: Ceilometer. Requires Hyper-V / Windows Server 2012 and above" +msgstr "" + +#: ./doc/common/tables/neutron-hyperv_agent.xml23(td) +#: ./doc/common/tables/nova-hyperv.xml30(td) +msgid "force_hyperv_utils_v1 = False" +msgstr "" + +#: ./doc/common/tables/neutron-hyperv_agent.xml24(td) +#: ./doc/common/tables/nova-hyperv.xml31(td) +msgid "(BoolOpt) Force V1 WMI utility classes" +msgstr "" + +#: ./doc/common/tables/neutron-hyperv_agent.xml27(td) +msgid "local_network_vswitch = private" +msgstr "" + +#: ./doc/common/tables/neutron-hyperv_agent.xml28(td) +msgid "(StrOpt) Private vswitch name used for local networks" +msgstr "" + +#: ./doc/common/tables/neutron-hyperv_agent.xml31(td) +msgid "physical_network_vswitch_mappings =" +msgstr "" + +#: ./doc/common/tables/neutron-hyperv_agent.xml32(td) +msgid "" +"(ListOpt) List of <physical_network>:<vswitch> where the " +"physical networks can be expressed with wildcards, e.g.: .\"*:external\"" +msgstr "" + +#: ./doc/common/tables/neutron-hyperv_agent.xml35(td) +msgid "polling_interval = 2" +msgstr "" + +#: ./doc/common/tables/neutron-hyperv_agent.xml36(td) +msgid "" +"(IntOpt) The number of seconds the agent will wait between polling for local" +" device changes." +msgstr "" + +#: ./doc/common/tables/glance-swift.xml8(caption) +msgid "Description of configuration options for swift" +msgstr "" + +#: ./doc/common/tables/glance-swift.xml22(td) +msgid "swift_enable_snet = False" +msgstr "" + +#: ./doc/common/tables/glance-swift.xml23(td) +msgid "" +"(BoolOpt) Whether to use ServiceNET to communicate with the Swift storage " +"servers." +msgstr "" + +#: ./doc/common/tables/glance-swift.xml26(td) +msgid "swift_store_admin_tenants =" +msgstr "" + +#: ./doc/common/tables/glance-swift.xml27(td) +msgid "" +"(ListOpt) A list of tenants that will be granted read/write access on all " +"Swift containers created by Glance in multi-tenant mode." +msgstr "" + +#: ./doc/common/tables/glance-swift.xml30(td) +msgid "swift_store_auth_address = None" +msgstr "" + +#: ./doc/common/tables/glance-swift.xml31(td) +msgid "" +"(StrOpt) The address where the Swift authentication service is listening." +msgstr "" + +#: ./doc/common/tables/glance-swift.xml34(td) +msgid "swift_store_auth_insecure = False" +msgstr "" + +#: ./doc/common/tables/glance-swift.xml35(td) +msgid "" +"(BoolOpt) If True, swiftclient won't check for a valid SSL certificate when " +"authenticating." +msgstr "" + +#: ./doc/common/tables/glance-swift.xml38(td) +msgid "swift_store_auth_version = 2" +msgstr "" + +#: ./doc/common/tables/glance-swift.xml39(td) +msgid "" +"(StrOpt) Version of the authentication service to use. Valid versions are 2 " +"for keystone and 1 for swauth and rackspace" +msgstr "" + +#: ./doc/common/tables/glance-swift.xml42(td) +msgid "swift_store_container = glance" +msgstr "" + +#: ./doc/common/tables/glance-swift.xml43(td) +msgid "" +"(StrOpt) Container within the account that the account should use for " +"storing images in Swift." +msgstr "" + +#: ./doc/common/tables/glance-swift.xml46(td) +msgid "swift_store_create_container_on_put = False" +msgstr "" + +#: ./doc/common/tables/glance-swift.xml47(td) +msgid "" +"(BoolOpt) A boolean value that determines if we create the container if it " +"does not exist." +msgstr "" + +#: ./doc/common/tables/glance-swift.xml50(td) +msgid "swift_store_endpoint_type = publicURL" +msgstr "" + +#: ./doc/common/tables/glance-swift.xml51(td) +msgid "" +"(StrOpt) A string giving the endpoint type of the swift service to use " +"(publicURL, adminURL or internalURL). This setting is only used if " +"swift_store_auth_version is 2." +msgstr "" + +#: ./doc/common/tables/glance-swift.xml54(td) +msgid "swift_store_key = None" +msgstr "" + +#: ./doc/common/tables/glance-swift.xml55(td) +msgid "" +"(StrOpt) Auth key for the user authenticating against the Swift " +"authentication service." +msgstr "" + +#: ./doc/common/tables/glance-swift.xml58(td) +msgid "swift_store_large_object_chunk_size = 200" +msgstr "" + +#: ./doc/common/tables/glance-swift.xml59(td) +msgid "" +"(IntOpt) The amount of data written to a temporary disk buffer during the " +"process of chunking the image file." +msgstr "" + +#: ./doc/common/tables/glance-swift.xml62(td) +msgid "swift_store_large_object_size = 5120" +msgstr "" + +#: ./doc/common/tables/glance-swift.xml63(td) +msgid "" +"(IntOpt) The size, in MB, that Glance will start chunking image files and do" +" a large object manifest in Swift" +msgstr "" + +#: ./doc/common/tables/glance-swift.xml66(td) +msgid "swift_store_multi_tenant = False" +msgstr "" + +#: ./doc/common/tables/glance-swift.xml67(td) +msgid "" +"(BoolOpt) If set to True, enables multi-tenant storage mode which causes " +"Glance images to be stored in tenant specific Swift accounts." +msgstr "" + +#: ./doc/common/tables/glance-swift.xml70(td) +msgid "swift_store_region = None" +msgstr "" + +#: ./doc/common/tables/glance-swift.xml71(td) +msgid "" +"(StrOpt) The region of the swift endpoint to be used for single tenant. This" +" setting is only necessary if the tenant has multiple swift endpoints." +msgstr "" + +#: ./doc/common/tables/glance-swift.xml74(td) +msgid "swift_store_service_type = object-store" +msgstr "" + +#: ./doc/common/tables/glance-swift.xml75(td) +msgid "" +"(StrOpt) A string giving the service type of the swift service to use. This " +"setting is only used if swift_store_auth_version is 2." +msgstr "" + +#: ./doc/common/tables/glance-swift.xml78(td) +msgid "swift_store_ssl_compression = True" +msgstr "" + +#: ./doc/common/tables/glance-swift.xml79(td) +msgid "" +"(BoolOpt) If set to False, disables SSL layer compression of https swift " +"requests. Setting to False may improve performance for images which are " +"already in a compressed format, eg qcow2." +msgstr "" + +#: ./doc/common/tables/glance-swift.xml82(td) +msgid "swift_store_user = None" +msgstr "" + +#: ./doc/common/tables/glance-swift.xml83(td) +msgid "" +"(StrOpt) The user to authenticate against the Swift authentication service" +msgstr "" + +#: ./doc/common/tables/swift-account-server-DEFAULT.xml21(td) +msgid "bind_port = 6002" +msgstr "" + +#: ./doc/common/tables/neutron-bigswitch.xml8(caption) +msgid "Description of configuration options for bigswitch" +msgstr "" + +#: ./doc/common/tables/neutron-bigswitch.xml19(td) +msgid "add_meta_server_route = True" +msgstr "" + +#: ./doc/common/tables/neutron-bigswitch.xml20(td) +msgid "" +"(BoolOpt) Flag to decide if a route to the metadata server should be " +"injected into the VM" +msgstr "" + +#: ./doc/common/tables/neutron-bigswitch.xml23(td) +msgid "max_router_rules = 200" +msgstr "" + +#: ./doc/common/tables/neutron-bigswitch.xml24(td) +msgid "(IntOpt) Maximum number of router rules" +msgstr "" + +#: ./doc/common/tables/neutron-bigswitch.xml27(td) +msgid "neutron_id = neutron-[hostname]" +msgstr "" + +#: ./doc/common/tables/neutron-bigswitch.xml28(td) +msgid "(StrOpt) User defined identifier for this Neutron deployment" +msgstr "" + +#: ./doc/common/tables/neutron-bigswitch.xml31(td) +msgid "node_override_vif_802.1qbg =" +msgstr "" + +#: ./doc/common/tables/neutron-bigswitch.xml32(td) +msgid "(ListOpt) Nova compute nodes to manually set VIF type to 802.1qbg" +msgstr "" + +#: ./doc/common/tables/neutron-bigswitch.xml35(td) +msgid "node_override_vif_802.1qbh =" +msgstr "" + +#: ./doc/common/tables/neutron-bigswitch.xml36(td) +msgid "(ListOpt) Nova compute nodes to manually set VIF type to 802.1qbh" +msgstr "" + +#: ./doc/common/tables/neutron-bigswitch.xml39(td) +msgid "node_override_vif_binding_failed =" +msgstr "" + +#: ./doc/common/tables/neutron-bigswitch.xml40(td) +msgid "" +"(ListOpt) Nova compute nodes to manually set VIF type to binding_failed" +msgstr "" + +#: ./doc/common/tables/neutron-bigswitch.xml43(td) +msgid "node_override_vif_bridge =" +msgstr "" + +#: ./doc/common/tables/neutron-bigswitch.xml44(td) +msgid "(ListOpt) Nova compute nodes to manually set VIF type to bridge" +msgstr "" + +#: ./doc/common/tables/neutron-bigswitch.xml47(td) +msgid "node_override_vif_hyperv =" +msgstr "" + +#: ./doc/common/tables/neutron-bigswitch.xml48(td) +msgid "(ListOpt) Nova compute nodes to manually set VIF type to hyperv" +msgstr "" + +#: ./doc/common/tables/neutron-bigswitch.xml51(td) +msgid "node_override_vif_ivs =" +msgstr "" + +#: ./doc/common/tables/neutron-bigswitch.xml52(td) +msgid "(ListOpt) Nova compute nodes to manually set VIF type to ivs" +msgstr "" + +#: ./doc/common/tables/neutron-bigswitch.xml55(td) +msgid "node_override_vif_midonet =" +msgstr "" + +#: ./doc/common/tables/neutron-bigswitch.xml56(td) +msgid "(ListOpt) Nova compute nodes to manually set VIF type to midonet" +msgstr "" + +#: ./doc/common/tables/neutron-bigswitch.xml59(td) +msgid "node_override_vif_other =" +msgstr "" + +#: ./doc/common/tables/neutron-bigswitch.xml60(td) +msgid "(ListOpt) Nova compute nodes to manually set VIF type to other" +msgstr "" + +#: ./doc/common/tables/neutron-bigswitch.xml63(td) +msgid "node_override_vif_ovs =" +msgstr "" + +#: ./doc/common/tables/neutron-bigswitch.xml64(td) +msgid "(ListOpt) Nova compute nodes to manually set VIF type to ovs" +msgstr "" + +#: ./doc/common/tables/neutron-bigswitch.xml67(td) +msgid "node_override_vif_unbound =" +msgstr "" + +#: ./doc/common/tables/neutron-bigswitch.xml68(td) +msgid "(ListOpt) Nova compute nodes to manually set VIF type to unbound" +msgstr "" + +#: ./doc/common/tables/neutron-bigswitch.xml71(td) +msgid "server_auth = username:password" +msgstr "" + +#: ./doc/common/tables/neutron-bigswitch.xml72(td) +msgid "" +"(StrOpt) The username and password for authenticating against the BigSwitch " +"or Floodlight controller." +msgstr "" + +#: ./doc/common/tables/neutron-bigswitch.xml75(td) +msgid "server_ssl = False" +msgstr "" + +#: ./doc/common/tables/neutron-bigswitch.xml76(td) +msgid "" +"(BoolOpt) If True, Use SSL when connecting to the BigSwitch or Floodlight " +"controller." +msgstr "" + +#: ./doc/common/tables/neutron-bigswitch.xml79(td) +msgid "server_timeout = 10" +msgstr "" + +#: ./doc/common/tables/neutron-bigswitch.xml80(td) +msgid "" +"(IntOpt) Maximum number of seconds to wait for proxy request to connect and " +"complete." +msgstr "" + +#: ./doc/common/tables/neutron-bigswitch.xml83(td) +msgid "servers = localhost:8800" +msgstr "" + +#: ./doc/common/tables/neutron-bigswitch.xml84(td) +msgid "" +"(StrOpt) A comma separated list of BigSwitch or Floodlight servers and port " +"numbers. The plugin proxies the requests to the BigSwitch/Floodlight server," +" which performs the networking configuration. Note that only one server is " +"needed per deployment, but you may wish to deploy multiple servers to " +"support failover." +msgstr "" + +#: ./doc/common/tables/neutron-bigswitch.xml87(td) +msgid "sync_data = False" +msgstr "" + +#: ./doc/common/tables/neutron-bigswitch.xml88(td) +msgid "(BoolOpt) Sync data on connect" +msgstr "" + +#: ./doc/common/tables/neutron-bigswitch.xml91(td) +msgid "tenant_default_router_rule = ['*:any:any:permit']" +msgstr "" + +#: ./doc/common/tables/neutron-bigswitch.xml92(td) +msgid "" +"(MultiStrOpt) The default router rules installed in new tenant routers. " +"Repeat the config option for each rule. Format is " +"<tenant>:<source>:<destination>:<action> Use an * to" +" specify default for all tenants." +msgstr "" + +#: ./doc/common/tables/neutron-bigswitch.xml95(td) +msgid "vif_type = ovs" +msgstr "" + +#: ./doc/common/tables/neutron-bigswitch.xml96(td) +msgid "(StrOpt) Virtual interface type to configure on Nova compute nodes" +msgstr "" + +#: ./doc/common/tables/neutron-bigswitch.xml99(td) +msgid "" +"vif_types = unbound, binding_failed, ovs, ivs, bridge, 802.1qbg, 802.1qbh, " +"hyperv, midonet, other" +msgstr "" + +#: ./doc/common/tables/neutron-bigswitch.xml100(td) +msgid "(ListOpt) List of allowed vif_type values." +msgstr "" + +#: ./doc/common/tables/nova-libvirt.xml8(caption) +msgid "Description of configuration options for libvirt" +msgstr "" + +#: ./doc/common/tables/nova-libvirt.xml22(td) +msgid "remove_unused_base_images = True" +msgstr "" + +#: ./doc/common/tables/nova-libvirt.xml23(td) +msgid "(BoolOpt) Should unused base images be removed?" +msgstr "" + +#: ./doc/common/tables/nova-libvirt.xml26(td) +msgid "remove_unused_original_minimum_age_seconds = 86400" +msgstr "" + +#: ./doc/common/tables/nova-libvirt.xml27(td) +msgid "" +"(IntOpt) Unused unresized base images younger than this will not be removed" +msgstr "" + +#: ./doc/common/tables/nova-libvirt.xml33(td) +msgid "checksum_base_images = False" +msgstr "" + +#: ./doc/common/tables/nova-libvirt.xml34(td) +msgid "(BoolOpt) Write a checksum for files in _base to disk" +msgstr "" + +#: ./doc/common/tables/nova-libvirt.xml37(td) +msgid "checksum_interval_seconds = 3600" +msgstr "" + +#: ./doc/common/tables/nova-libvirt.xml38(td) +msgid "(IntOpt) How frequently to checksum base images" +msgstr "" + +#: ./doc/common/tables/nova-libvirt.xml41(td) +msgid "connection_uri =" +msgstr "" + +#: ./doc/common/tables/nova-libvirt.xml42(td) +msgid "" +"(StrOpt) Override the default libvirt URI (which is dependent on virt_type)" +msgstr "" + +#: ./doc/common/tables/nova-libvirt.xml45(td) +msgid "cpu_mode = None" +msgstr "" + +#: ./doc/common/tables/nova-libvirt.xml46(td) +msgid "" +"(StrOpt) Set to \"host-model\" to clone the host CPU feature flags; to " +"\"host-passthrough\" to use the host CPU model exactly; to \"custom\" to use" +" a named CPU model; to \"none\" to not set any CPU model. If " +"virt_type=\"kvm|qemu\", it will default to \"host-model\", otherwise it will" +" default to \"none\"" +msgstr "" + +#: ./doc/common/tables/nova-libvirt.xml49(td) +msgid "cpu_model = None" +msgstr "" + +#: ./doc/common/tables/nova-libvirt.xml50(td) +msgid "" +"(StrOpt) Set to a named libvirt CPU model (see names listed in " +"/usr/share/libvirt/cpu_map.xml). Only has effect if cpu_mode=\"custom\" and " +"virt_type=\"kvm|qemu\"" +msgstr "" + +#: ./doc/common/tables/nova-libvirt.xml53(td) +msgid "disk_prefix = None" +msgstr "" + +#: ./doc/common/tables/nova-libvirt.xml54(td) +msgid "" +"(StrOpt) Override the default disk prefix for the devices attached to a " +"server, which is dependent on virt_type. (valid options are: sd, xvd, uvd, " +"vd)" +msgstr "" + +#: ./doc/common/tables/nova-libvirt.xml57(td) +msgid "" +"image_info_filename_pattern = " +"$instances_path/$image_cache_subdirectory_name/%(image)s.info" +msgstr "" + +#: ./doc/common/tables/nova-libvirt.xml58(td) +msgid "" +"(StrOpt) Allows image information files to be stored in non-standard " +"locations" +msgstr "" + +#: ./doc/common/tables/nova-libvirt.xml61(td) +msgid "remove_unused_kernels = False" +msgstr "" + +#: ./doc/common/tables/nova-libvirt.xml62(td) +msgid "" +"(BoolOpt) Should unused kernel images be removed? This is only safe to " +"enable if all compute nodes have been updated to support this option. This " +"will be enabled by default in future." +msgstr "" + +#: ./doc/common/tables/nova-libvirt.xml65(td) +msgid "remove_unused_resized_minimum_age_seconds = 3600" +msgstr "" + +#: ./doc/common/tables/nova-libvirt.xml66(td) +msgid "" +"(IntOpt) Unused resized base images younger than this will not be removed" +msgstr "" + +#: ./doc/common/tables/nova-libvirt.xml69(td) +msgid "snapshots_directory = $instances_path/snapshots" +msgstr "" + +#: ./doc/common/tables/nova-libvirt.xml70(td) +msgid "" +"(StrOpt) Location where libvirt driver will store snapshots before uploading" +" them to image service" +msgstr "" + +#: ./doc/common/tables/nova-libvirt.xml73(td) +msgid "vif_driver = nova.virt.libvirt.vif.LibvirtGenericVIFDriver" +msgstr "" + +#: ./doc/common/tables/nova-libvirt.xml74(td) +msgid "(StrOpt) The libvirt VIF driver to configure the VIFs." +msgstr "" + +#: ./doc/common/tables/nova-libvirt.xml77(td) +msgid "virt_type = kvm" +msgstr "" + +#: ./doc/common/tables/nova-libvirt.xml78(td) +msgid "" +"(StrOpt) Libvirt domain type (valid options are: kvm, lxc, qemu, uml, xen)" +msgstr "" + +#: ./doc/common/tables/nova-libvirt.xml81(td) +msgid "" +"volume_drivers = iscsi=nova.virt.libvirt.volume.LibvirtISCSIVolumeDriver, " +"iser=nova.virt.libvirt.volume.LibvirtISERVolumeDriver, " +"local=nova.virt.libvirt.volume.LibvirtVolumeDriver, " +"fake=nova.virt.libvirt.volume.LibvirtFakeVolumeDriver, " +"rbd=nova.virt.libvirt.volume.LibvirtNetVolumeDriver, " +"sheepdog=nova.virt.libvirt.volume.LibvirtNetVolumeDriver, " +"nfs=nova.virt.libvirt.volume.LibvirtNFSVolumeDriver, " +"aoe=nova.virt.libvirt.volume.LibvirtAOEVolumeDriver, " +"glusterfs=nova.virt.libvirt.volume.LibvirtGlusterfsVolumeDriver, " +"fibre_channel=nova.virt.libvirt.volume.LibvirtFibreChannelVolumeDriver, " +"scality=nova.virt.libvirt.volume.LibvirtScalityVolumeDriver" +msgstr "" + +#: ./doc/common/tables/nova-libvirt.xml82(td) +msgid "(ListOpt) Libvirt handlers for remote volumes." +msgstr "" + +#: ./doc/common/tables/nova-libvirt.xml85(td) +msgid "wait_soft_reboot_seconds = 120" +msgstr "" + +#: ./doc/common/tables/nova-libvirt.xml86(td) +msgid "" +"(IntOpt) Number of seconds to wait for instance to shut down after soft " +"reboot request is made. We fall back to hard reboot if instance does not " +"shutdown within this window." +msgstr "" + +#: ./doc/common/tables/neutron-lbaas.xml8(caption) +msgid "Description of configuration options for lbaas" +msgstr "" + +#: ./doc/common/tables/neutron-lbaas.xml19(td) +msgid "actions_to_skip = setup_l2_l3" +msgstr "" + +#: ./doc/common/tables/neutron-lbaas.xml20(td) +msgid "" +"(ListOpt) List of actions that we dont want to push to the completion queue" +msgstr "" + +#: ./doc/common/tables/neutron-lbaas.xml23(td) +msgid "" +"l2_l3_ctor_params = {'ha_ip_pool_name': 'default', 'allocate_ha_vrrp': True," +" 'ha_network_name': 'HA-Network', 'service': '_REPLACE_', 'allocate_ha_ips':" +" True}" +msgstr "" + +#: ./doc/common/tables/neutron-lbaas.xml24(td) +msgid "(DictOpt) l2_l3 workflow constructor params" +msgstr "" + +#: ./doc/common/tables/neutron-lbaas.xml27(td) +msgid "" +"l2_l3_setup_params = {'data_ip_address': '192.168.200.99', 'data_port': 1, " +"'gateway': '192.168.200.1', 'ha_port': 2, 'data_ip_mask': '255.255.255.0'}" +msgstr "" + +#: ./doc/common/tables/neutron-lbaas.xml28(td) +msgid "(DictOpt) l2_l3 workflow setup params" +msgstr "" + +#: ./doc/common/tables/neutron-lbaas.xml31(td) +msgid "l2_l3_workflow_name = openstack_l2_l3" +msgstr "" + +#: ./doc/common/tables/neutron-lbaas.xml32(td) +msgid "(StrOpt) l2_l3 workflow name" +msgstr "" + +#: ./doc/common/tables/neutron-lbaas.xml35(td) +msgid "l4_action_name = BaseCreate" +msgstr "" + +#: ./doc/common/tables/neutron-lbaas.xml36(td) +msgid "(StrOpt) l4 workflow action name" +msgstr "" + +#: ./doc/common/tables/neutron-lbaas.xml39(td) +msgid "l4_workflow_name = openstack_l4" +msgstr "" + +#: ./doc/common/tables/neutron-lbaas.xml40(td) +msgid "(StrOpt) l4 workflow name" +msgstr "" + +#: ./doc/common/tables/neutron-lbaas.xml43(td) +msgid "" +"loadbalancer_pool_scheduler_driver = " +"neutron.services.loadbalancer.agent_scheduler.ChanceScheduler" +msgstr "" + +#: ./doc/common/tables/neutron-lbaas.xml44(td) +msgid "" +"(StrOpt) Driver to use for scheduling pool to a default loadbalancer agent" +msgstr "" + +#: ./doc/common/tables/neutron-lbaas.xml47(td) +msgid "loadbalancer_state_path = $state_path/lbaas" +msgstr "" + +#: ./doc/common/tables/neutron-lbaas.xml48(td) +msgid "(StrOpt) Location to store config and state files" +msgstr "" + +#: ./doc/common/tables/neutron-lbaas.xml51(td) +msgid "service_adc_type = VA" +msgstr "" + +#: ./doc/common/tables/neutron-lbaas.xml52(td) +msgid "(StrOpt) Service ADC type" +msgstr "" + +#: ./doc/common/tables/neutron-lbaas.xml55(td) +msgid "service_adc_version =" +msgstr "" + +#: ./doc/common/tables/neutron-lbaas.xml56(td) +msgid "(StrOpt) Service ADC version" +msgstr "" + +#: ./doc/common/tables/neutron-lbaas.xml59(td) +msgid "service_cache = 20" +msgstr "" + +#: ./doc/common/tables/neutron-lbaas.xml60(td) +msgid "(IntOpt) service cache" +msgstr "" + +#: ./doc/common/tables/neutron-lbaas.xml63(td) +msgid "service_compression_throughput = 100" +msgstr "" + +#: ./doc/common/tables/neutron-lbaas.xml64(td) +msgid "(IntOpt) service compression throughtput" +msgstr "" + +#: ./doc/common/tables/neutron-lbaas.xml67(td) +msgid "service_ha_pair = False" +msgstr "" + +#: ./doc/common/tables/neutron-lbaas.xml68(td) +msgid "(BoolOpt) service HA pair" +msgstr "" + +#: ./doc/common/tables/neutron-lbaas.xml71(td) +msgid "service_isl_vlan = -1" +msgstr "" + +#: ./doc/common/tables/neutron-lbaas.xml72(td) +msgid "(IntOpt) A required VLAN for the interswitch link to use" +msgstr "" + +#: ./doc/common/tables/neutron-lbaas.xml75(td) +msgid "service_resource_pool_ids =" +msgstr "" + +#: ./doc/common/tables/neutron-lbaas.xml76(td) +msgid "(ListOpt) Resource pool ids" +msgstr "" + +#: ./doc/common/tables/neutron-lbaas.xml79(td) +msgid "service_session_mirroring_enabled = False" +msgstr "" + +#: ./doc/common/tables/neutron-lbaas.xml80(td) +msgid "" +"(BoolOpt) Support an Alteon interswitch link for stateful session failover" +msgstr "" + +#: ./doc/common/tables/neutron-lbaas.xml83(td) +msgid "service_ssl_throughput = 100" +msgstr "" + +#: ./doc/common/tables/neutron-lbaas.xml84(td) +msgid "(IntOpt) service ssl throughtput" +msgstr "" + +#: ./doc/common/tables/neutron-lbaas.xml87(td) +msgid "service_throughput = 1000" +msgstr "" + +#: ./doc/common/tables/neutron-lbaas.xml88(td) +msgid "(IntOpt) service throughtput" +msgstr "" + +#: ./doc/common/tables/neutron-lbaas.xml91(td) +msgid "user_group = nogroup" +msgstr "" + +#: ./doc/common/tables/neutron-lbaas.xml92(td) +msgid "(StrOpt) The user group" +msgstr "" + +#: ./doc/common/tables/neutron-lbaas.xml95(td) +msgid "vdirect_address = None" +msgstr "" + +#: ./doc/common/tables/neutron-lbaas.xml96(td) +msgid "(StrOpt) vdirect server IP address" +msgstr "" + +#: ./doc/common/tables/neutron-lbaas.xml99(td) +msgid "vdirect_password = radware" +msgstr "" + +#: ./doc/common/tables/neutron-lbaas.xml100(td) +msgid "(StrOpt) vdirect user password" +msgstr "" + +#: ./doc/common/tables/neutron-lbaas.xml103(td) +msgid "vdirect_user = vDirect" +msgstr "" + +#: ./doc/common/tables/neutron-lbaas.xml104(td) +msgid "(StrOpt) vdirect user name" +msgstr "" + +#: ./doc/common/tables/cinder-backups_swift.xml8(caption) +msgid "Description of configuration options for backups_swift" +msgstr "" + +#: ./doc/common/tables/cinder-backups_swift.xml22(td) +msgid "backup_swift_auth = per_user" +msgstr "" + +#: ./doc/common/tables/cinder-backups_swift.xml23(td) +msgid "(StrOpt) Swift authentication mechanism" +msgstr "" + +#: ./doc/common/tables/cinder-backups_swift.xml26(td) +msgid "backup_swift_container = volumebackups" +msgstr "" + +#: ./doc/common/tables/cinder-backups_swift.xml27(td) +msgid "(StrOpt) The default Swift container to use" +msgstr "" + +#: ./doc/common/tables/cinder-backups_swift.xml30(td) +msgid "backup_swift_key = None" +msgstr "" + +#: ./doc/common/tables/cinder-backups_swift.xml31(td) +msgid "(StrOpt) Swift key for authentication" +msgstr "" + +#: ./doc/common/tables/cinder-backups_swift.xml34(td) +msgid "backup_swift_object_size = 52428800" +msgstr "" + +#: ./doc/common/tables/cinder-backups_swift.xml35(td) +msgid "(IntOpt) The size in bytes of Swift backup objects" +msgstr "" + +#: ./doc/common/tables/cinder-backups_swift.xml38(td) +msgid "backup_swift_retry_attempts = 3" +msgstr "" + +#: ./doc/common/tables/cinder-backups_swift.xml39(td) +msgid "(IntOpt) The number of retries to make for Swift operations" +msgstr "" + +#: ./doc/common/tables/cinder-backups_swift.xml42(td) +msgid "backup_swift_retry_backoff = 2" +msgstr "" + +#: ./doc/common/tables/cinder-backups_swift.xml43(td) +msgid "(IntOpt) The backoff time in seconds between Swift retries" +msgstr "" + +#: ./doc/common/tables/cinder-backups_swift.xml46(td) +msgid "backup_swift_url = http://localhost:8080/v1/AUTH_" +msgstr "" + +#: ./doc/common/tables/cinder-backups_swift.xml47(td) +msgid "(StrOpt) The URL of the Swift endpoint" +msgstr "" + +#: ./doc/common/tables/cinder-backups_swift.xml50(td) +msgid "backup_swift_user = None" +msgstr "" + +#: ./doc/common/tables/cinder-backups_swift.xml51(td) +msgid "(StrOpt) Swift user name" +msgstr "" + +#: ./doc/common/tables/neutron-ml2_cisco.xml8(caption) +msgid "Description of configuration options for ml2_cisco" +msgstr "" + +#: ./doc/common/tables/neutron-ml2_cisco.xml19(td) +msgid "managed_physical_network = None" +msgstr "" + +#: ./doc/common/tables/neutron-ml2_cisco.xml20(td) +msgid "(StrOpt) The physical network managed by the switches." +msgstr "" + +#: ./doc/common/tables/nova-pci.xml8(caption) +msgid "Description of configuration options for pci" +msgstr "" + +#: ./doc/common/tables/nova-pci.xml22(td) +msgid "pci_alias = []" +msgstr "" + +#: ./doc/common/tables/nova-pci.xml23(td) +msgid "" +"(MultiStrOpt) An alias for a PCI passthrough device requirement. This allows" +" users to specify the alias in the extra_spec for a flavor, without needing " +"to repeat all the PCI property requirements. For example: pci_alias = { " +"\"name\": \"QuicAssist\", \"product_id\": \"0443\", \"vendor_id\": \"8086\"," +" \"device_type\": \"ACCEL\" } defines an alias for the Intel QuickAssist " +"card. (multi valued)" +msgstr "" + +#: ./doc/common/tables/nova-pci.xml26(td) +msgid "pci_passthrough_whitelist = []" +msgstr "" + +#: ./doc/common/tables/nova-pci.xml27(td) +msgid "" +"(MultiStrOpt) White list of PCI devices available to VMs. For example: " +"pci_passthrough_whitelist = [{\"vendor_id\": \"8086\", \"product_id\": " +"\"0443\"}]" +msgstr "" + +#: ./doc/common/tables/swift-proxy-server-filter-proxy-logging.xml7(literal) +msgid "[filter:proxy-logging]" +msgstr "" + +#: ./doc/common/tables/swift-proxy-server-filter-proxy-logging.xml18(td) +msgid "use = egg:swift#proxy_logging" +msgstr "" + +#: ./doc/common/tables/swift-proxy-server-filter-proxy-logging.xml21(td) +msgid "access_log_name = swift" +msgstr "" + +#: ./doc/common/tables/swift-proxy-server-filter-proxy-logging.xml24(td) +msgid "access_log_facility = LOG_LOCAL0" +msgstr "" + +#: ./doc/common/tables/swift-proxy-server-filter-proxy-logging.xml27(td) +msgid "access_log_level = INFO" +msgstr "" + +#: ./doc/common/tables/swift-proxy-server-filter-proxy-logging.xml30(td) +msgid "access_log_address = /dev/log" +msgstr "" + +#: ./doc/common/tables/swift-proxy-server-filter-proxy-logging.xml33(td) +msgid "access_log_udp_host =" +msgstr "" + +#: ./doc/common/tables/swift-proxy-server-filter-proxy-logging.xml36(td) +msgid "access_log_udp_port = 514" +msgstr "" + +#: ./doc/common/tables/swift-proxy-server-filter-proxy-logging.xml39(td) +msgid "access_log_statsd_host = localhost" +msgstr "" + +#: ./doc/common/tables/swift-proxy-server-filter-proxy-logging.xml42(td) +msgid "access_log_statsd_port = 8125" +msgstr "" + +#: ./doc/common/tables/swift-proxy-server-filter-proxy-logging.xml45(td) +msgid "access_log_statsd_default_sample_rate = 1.0" +msgstr "" + +#: ./doc/common/tables/swift-proxy-server-filter-proxy-logging.xml48(td) +msgid "access_log_statsd_sample_rate_factor = 1.0" +msgstr "" + +#: ./doc/common/tables/swift-proxy-server-filter-proxy-logging.xml51(td) +msgid "access_log_statsd_metric_prefix =" +msgstr "" + +#: ./doc/common/tables/swift-proxy-server-filter-proxy-logging.xml54(td) +msgid "access_log_headers = false" +msgstr "" + +#: ./doc/common/tables/swift-proxy-server-filter-proxy-logging.xml57(td) +msgid "logged with access_log_headers = True." +msgstr "" + +#: ./doc/common/tables/swift-proxy-server-filter-proxy-logging.xml60(td) +msgid "reveal_sensitive_prefix = 8192" +msgstr "" + +#: ./doc/common/tables/swift-proxy-server-filter-proxy-logging.xml60(td) +msgid "" +"The X-Auth-Token is sensitive data. If revealed to an unauthorised person, " +"they can now make requests against an account until the token expires. Set " +"reveal_sensitive_prefix to the number of characters of the token that are " +"logged. For example reveal_sensitive_prefix = 12 so only first 12 characters" +" of the token are logged. Or, set to 0 to completely remove the token." +msgstr "" + +#: ./doc/common/tables/swift-proxy-server-filter-proxy-logging.xml69(td) +msgid "log_statsd_valid_http_methods = GET,HEAD,POST,PUT,DELETE,COPY,OPTIONS" +msgstr "" + +#: ./doc/common/tables/neutron-varmour.xml8(caption) +msgid "Description of configuration options for varmour" +msgstr "" + +#: ./doc/common/tables/neutron-varmour.xml19(td) +msgid "director = localhost" +msgstr "" + +#: ./doc/common/tables/neutron-varmour.xml20(td) +msgid "(StrOpt) vArmour director ip" +msgstr "" + +#: ./doc/common/tables/neutron-varmour.xml23(td) +msgid "director_port = 443" +msgstr "" + +#: ./doc/common/tables/neutron-varmour.xml24(td) +msgid "(StrOpt) vArmour director port" +msgstr "" + +#: ./doc/common/tables/neutron-varmour.xml27(td) +msgid "password = varmour" +msgstr "" + +#: ./doc/common/tables/neutron-varmour.xml28(td) +msgid "(StrOpt) vArmour director password" +msgstr "" + +#: ./doc/common/tables/glance-imagecache.xml8(caption) +msgid "Description of configuration options for imagecache" +msgstr "" + +#: ./doc/common/tables/glance-imagecache.xml22(td) +msgid "cleanup_scrubber = False" +msgstr "" + +#: ./doc/common/tables/glance-imagecache.xml23(td) +msgid "" +"(BoolOpt) A boolean that determines if the scrubber should clean up the " +"files it uses for taking data. Only one server in your deployment should be " +"designated the cleanup host." +msgstr "" + +#: ./doc/common/tables/glance-imagecache.xml26(td) +msgid "cleanup_scrubber_time = 86400" +msgstr "" + +#: ./doc/common/tables/glance-imagecache.xml27(td) +msgid "" +"(IntOpt) Items must have a modified time that is older than this value in " +"order to be candidates for cleanup." +msgstr "" + +#: ./doc/common/tables/glance-imagecache.xml30(td) +msgid "delayed_delete = False" +msgstr "" + +#: ./doc/common/tables/glance-imagecache.xml31(td) +msgid "(BoolOpt) Turn on/off delayed delete." +msgstr "" + +#: ./doc/common/tables/glance-imagecache.xml34(td) +msgid "image_cache_dir = None" +msgstr "" + +#: ./doc/common/tables/glance-imagecache.xml35(td) +msgid "(StrOpt) Base directory that the Image Cache uses." +msgstr "" + +#: ./doc/common/tables/glance-imagecache.xml38(td) +msgid "image_cache_driver = sqlite" +msgstr "" + +#: ./doc/common/tables/glance-imagecache.xml39(td) +msgid "(StrOpt) The driver to use for image cache management." +msgstr "" + +#: ./doc/common/tables/glance-imagecache.xml42(td) +msgid "image_cache_max_size = 10737418240" +msgstr "" + +#: ./doc/common/tables/glance-imagecache.xml43(td) +msgid "(IntOpt) The maximum size in bytes that the cache can use." +msgstr "" + +#: ./doc/common/tables/glance-imagecache.xml46(td) +msgid "image_cache_sqlite_db = cache.db" +msgstr "" + +#: ./doc/common/tables/glance-imagecache.xml47(td) +msgid "" +"(StrOpt) The path to the sqlite file database that will be used for image " +"cache management." +msgstr "" + +#: ./doc/common/tables/glance-imagecache.xml50(td) +msgid "image_cache_stall_time = 86400" +msgstr "" + +#: ./doc/common/tables/glance-imagecache.xml51(td) +msgid "" +"(IntOpt) The amount of time to let an image remain in the cache without " +"being accessed" +msgstr "" + +#: ./doc/common/tables/glance-imagecache.xml54(td) +msgid "scrub_time = 0" +msgstr "" + +#: ./doc/common/tables/glance-imagecache.xml55(td) +msgid "" +"(IntOpt) The amount of time in seconds to delay before performing a delete." +msgstr "" + +#: ./doc/common/tables/glance-imagecache.xml58(td) +msgid "scrubber_datadir = /var/lib/glance/scrubber" +msgstr "" + +#: ./doc/common/tables/glance-imagecache.xml59(td) +msgid "" +"(StrOpt) Directory that the scrubber will use to track information about " +"what to delete. Make sure this is set in glance-api.conf and glance-" +"scrubber.conf" +msgstr "" + +#: ./doc/common/tables/swift-rsyncd-account.xml7(literal) +msgid "[account]" +msgstr "" + +#: ./doc/common/tables/swift-rsyncd-account.xml18(td) +msgid "max connections = 2" +msgstr "" + +#: ./doc/common/tables/swift-rsyncd-account.xml27(td) +msgid "lock file = /var/lock/account.lock" +msgstr "" + +#: ./doc/common/tables/cinder-storage.xml8(caption) +msgid "Description of configuration options for storage" +msgstr "" + +#: ./doc/common/tables/cinder-storage.xml22(td) +msgid "allocated_capacity_weight_multiplier = -1.0" +msgstr "" + +#: ./doc/common/tables/cinder-storage.xml23(td) +#: ./doc/common/tables/cinder-storage.xml31(td) +msgid "" +"(FloatOpt) Multiplier used for weighing volume capacity. Negative numbers " +"mean to stack vs spread." +msgstr "" + +#: ./doc/common/tables/cinder-storage.xml26(td) +msgid "bindir = $pybasedir/bin" +msgstr "" + +#: ./doc/common/tables/cinder-storage.xml27(td) +msgid "(StrOpt) Directory where cinder binaries are installed" +msgstr "" + +#: ./doc/common/tables/cinder-storage.xml30(td) +msgid "capacity_weight_multiplier = 1.0" +msgstr "" + +#: ./doc/common/tables/cinder-storage.xml34(td) +msgid "enabled_backends = None" +msgstr "" + +#: ./doc/common/tables/cinder-storage.xml35(td) +msgid "" +"(ListOpt) A list of backend names to use. These backend names should be " +"backed by a unique [CONFIG] group with its options" +msgstr "" + +#: ./doc/common/tables/cinder-storage.xml38(td) +msgid "iscsi_helper = tgtadm" +msgstr "" + +#: ./doc/common/tables/cinder-storage.xml39(td) +msgid "(StrOpt) iscsi target user-land tool to use" +msgstr "" + +#: ./doc/common/tables/cinder-storage.xml42(td) +msgid "iscsi_iotype = fileio" +msgstr "" + +#: ./doc/common/tables/cinder-storage.xml43(td) +msgid "" +"(StrOpt) Sets the behavior of the iSCSI target to either perform blockio or " +"fileio optionally, auto can be set and Cinder will autodetect type of " +"backing device" +msgstr "" + +#: ./doc/common/tables/cinder-storage.xml46(td) +msgid "iscsi_ip_address = $my_ip" +msgstr "" + +#: ./doc/common/tables/cinder-storage.xml47(td) +msgid "(StrOpt) The IP address that the iSCSI daemon is listening on" +msgstr "" + +#: ./doc/common/tables/cinder-storage.xml50(td) +msgid "iscsi_num_targets = 100" +msgstr "" + +#: ./doc/common/tables/cinder-storage.xml51(td) +msgid "(IntOpt) The maximum number of iscsi target ids per host" +msgstr "" + +#: ./doc/common/tables/cinder-storage.xml54(td) +msgid "iscsi_port = 3260" +msgstr "" + +#: ./doc/common/tables/cinder-storage.xml55(td) +msgid "(IntOpt) The port that the iSCSI daemon is listening on" +msgstr "" + +#: ./doc/common/tables/cinder-storage.xml58(td) +msgid "iscsi_target_prefix = iqn.2010-10.org.openstack:" +msgstr "" + +#: ./doc/common/tables/cinder-storage.xml59(td) +msgid "(StrOpt) prefix for iscsi volumes" +msgstr "" + +#: ./doc/common/tables/cinder-storage.xml62(td) +msgid "iser_helper = tgtadm" +msgstr "" + +#: ./doc/common/tables/cinder-storage.xml63(td) +msgid "(StrOpt) iser target user-land tool to use" +msgstr "" + +#: ./doc/common/tables/cinder-storage.xml66(td) +msgid "iser_ip_address = $my_ip" +msgstr "" + +#: ./doc/common/tables/cinder-storage.xml67(td) +msgid "(StrOpt) The IP address that the iSER daemon is listening on" +msgstr "" + +#: ./doc/common/tables/cinder-storage.xml70(td) +msgid "iser_num_targets = 100" +msgstr "" + +#: ./doc/common/tables/cinder-storage.xml71(td) +msgid "(IntOpt) The maximum number of iser target ids per host" +msgstr "" + +#: ./doc/common/tables/cinder-storage.xml74(td) +msgid "iser_port = 3260" +msgstr "" + +#: ./doc/common/tables/cinder-storage.xml75(td) +msgid "(IntOpt) The port that the iSER daemon is listening on" +msgstr "" + +#: ./doc/common/tables/cinder-storage.xml78(td) +msgid "iser_target_prefix = iqn.2010-10.org.iser.openstack:" +msgstr "" + +#: ./doc/common/tables/cinder-storage.xml79(td) +msgid "(StrOpt) prefix for iser volumes" +msgstr "" + +#: ./doc/common/tables/cinder-storage.xml82(td) +msgid "max_gigabytes = 10000" +msgstr "" + +#: ./doc/common/tables/cinder-storage.xml83(td) +msgid "" +"(IntOpt) This configure option has been deprecated along with the " +"SimpleScheduler. New scheduler is able to gather capacity information for " +"each host, thus setting the maximum number of volume gigabytes for host is " +"no longer needed. It's safe to remove this configure from cinder.conf." +msgstr "" + +#: ./doc/common/tables/cinder-storage.xml86(td) +msgid "migration_create_volume_timeout_secs = 300" +msgstr "" + +#: ./doc/common/tables/cinder-storage.xml87(td) +msgid "" +"(IntOpt) Timeout for creating the volume to migrate to when performing " +"volume migration (seconds)" +msgstr "" + +#: ./doc/common/tables/cinder-storage.xml91(td) +msgid "" +"(IntOpt) The maximum number of times to rescan iSER targetto find volume" +msgstr "" + +#: ./doc/common/tables/cinder-storage.xml94(td) +msgid "num_volume_device_scan_tries = 3" +msgstr "" + +#: ./doc/common/tables/cinder-storage.xml95(td) +msgid "(IntOpt) The maximum number of times to rescan targets to find volume" +msgstr "" + +#: ./doc/common/tables/cinder-storage.xml98(td) +msgid "volume_backend_name = None" +msgstr "" + +#: ./doc/common/tables/cinder-storage.xml99(td) +msgid "(StrOpt) The backend name for a given driver implementation" +msgstr "" + +#: ./doc/common/tables/cinder-storage.xml102(td) +msgid "volume_clear = zero" +msgstr "" + +#: ./doc/common/tables/cinder-storage.xml103(td) +msgid "" +"(StrOpt) Method used to wipe old voumes (valid options are: none, zero, " +"shred)" +msgstr "" + +#: ./doc/common/tables/cinder-storage.xml106(td) +msgid "volume_clear_size = 0" +msgstr "" + +#: ./doc/common/tables/cinder-storage.xml107(td) +msgid "(IntOpt) Size in MiB to wipe at start of old volumes. 0 => all" +msgstr "" + +#: ./doc/common/tables/cinder-storage.xml110(td) +msgid "volume_dd_blocksize = 1M" +msgstr "" + +#: ./doc/common/tables/cinder-storage.xml111(td) +msgid "(StrOpt) The default block size used when copying/clearing volumes" +msgstr "" + +#: ./doc/common/tables/cinder-storage.xml114(td) +msgid "volume_driver = cinder.volume.drivers.lvm.LVMISCSIDriver" +msgstr "" + +#: ./doc/common/tables/cinder-storage.xml115(td) +msgid "(StrOpt) Driver to use for volume creation" +msgstr "" + +#: ./doc/common/tables/cinder-storage.xml118(td) +msgid "volume_manager = cinder.volume.manager.VolumeManager" +msgstr "" + +#: ./doc/common/tables/cinder-storage.xml119(td) +msgid "(StrOpt) full class name for the Manager for volume" +msgstr "" + +#: ./doc/common/tables/cinder-storage.xml122(td) +msgid "volume_service_inithost_offload = False" +msgstr "" + +#: ./doc/common/tables/cinder-storage.xml123(td) +msgid "(BoolOpt) Offload pending volume delete during volume service startup" +msgstr "" + +#: ./doc/common/tables/cinder-storage.xml126(td) +msgid "volume_usage_audit_period = month" +msgstr "" + +#: ./doc/common/tables/cinder-storage.xml127(td) +msgid "" +"(StrOpt) time period to generate volume usages for. Time period must be " +"hour, day, month or year" +msgstr "" + +#: ./doc/common/tables/cinder-storage.xml130(td) +msgid "volumes_dir = $state_path/volumes" +msgstr "" + +#: ./doc/common/tables/cinder-storage.xml131(td) +msgid "(StrOpt) Volume configuration file storage directory" +msgstr "" + +#: ./doc/common/tables/cinder-storage.xml134(td) +msgid "zadara_default_stripesize = 64" +msgstr "" + +#: ./doc/common/tables/cinder-storage.xml135(td) +msgid "(StrOpt) Default stripe size for volumes" +msgstr "" + +#: ./doc/common/tables/cinder-storage.xml149(td) +msgid "max_pool_size = 5" +msgstr "" + +#: ./doc/common/tables/nova-vpn.xml8(caption) +#: ./doc/common/tables/neutron-vpn.xml8(caption) +msgid "Description of configuration options for vpn" +msgstr "" + +#: ./doc/common/tables/nova-vpn.xml22(td) +msgid "boot_script_template = $pybasedir/nova/cloudpipe/bootscript.template" +msgstr "" + +#: ./doc/common/tables/nova-vpn.xml23(td) +msgid "(StrOpt) Template for cloudpipe instance boot script" +msgstr "" + +#: ./doc/common/tables/nova-vpn.xml26(td) +msgid "dmz_cidr =" +msgstr "" + +#: ./doc/common/tables/nova-vpn.xml27(td) +msgid "(ListOpt) A list of dmz range that should be accepted" +msgstr "" + +#: ./doc/common/tables/nova-vpn.xml30(td) +msgid "dmz_mask = 255.255.255.0" +msgstr "" + +#: ./doc/common/tables/nova-vpn.xml31(td) +msgid "(StrOpt) Netmask to push into openvpn config" +msgstr "" + +#: ./doc/common/tables/nova-vpn.xml34(td) +msgid "dmz_net = 10.0.0.0" +msgstr "" + +#: ./doc/common/tables/nova-vpn.xml35(td) +msgid "(StrOpt) Network to push into openvpn config" +msgstr "" + +#: ./doc/common/tables/nova-vpn.xml38(td) +msgid "vpn_flavor = m1.tiny" +msgstr "" + +#: ./doc/common/tables/nova-vpn.xml39(td) +msgid "(StrOpt) Flavor for vpn instances" +msgstr "" + +#: ./doc/common/tables/nova-vpn.xml42(td) +msgid "vpn_image_id = 0" +msgstr "" + +#: ./doc/common/tables/nova-vpn.xml43(td) +msgid "(StrOpt) image id used when starting up a cloudpipe vpn server" +msgstr "" + +#: ./doc/common/tables/nova-vpn.xml46(td) +msgid "vpn_ip = $my_ip" +msgstr "" + +#: ./doc/common/tables/nova-vpn.xml47(td) +msgid "(StrOpt) Public IP for the cloudpipe VPN servers" +msgstr "" + +#: ./doc/common/tables/nova-vpn.xml50(td) +msgid "vpn_key_suffix = -vpn" +msgstr "" + +#: ./doc/common/tables/nova-vpn.xml51(td) +msgid "(StrOpt) Suffix to add to project name for vpn key and secgroups" +msgstr "" + +#: ./doc/common/tables/nova-vpn.xml54(td) +msgid "vpn_start = 1000" +msgstr "" + +#: ./doc/common/tables/nova-vpn.xml55(td) +msgid "(IntOpt) First Vpn port for private networks" +msgstr "" + +#: ./doc/common/tables/nova-wsgi.xml23(td) +msgid "(StrOpt) File name for the paste.deploy config for nova-api" +msgstr "" + +#: ./doc/common/tables/nova-wsgi.xml26(td) +#: ./doc/common/tables/cinder-common.xml190(td) +#: ./doc/common/tables/neutron-ssl.xml23(td) +msgid "ssl_ca_file = None" +msgstr "" + +#: ./doc/common/tables/nova-wsgi.xml30(td) +#: ./doc/common/tables/cinder-common.xml194(td) +#: ./doc/common/tables/neutron-ssl.xml27(td) +msgid "ssl_cert_file = None" +msgstr "" + +#: ./doc/common/tables/nova-wsgi.xml31(td) +msgid "(StrOpt) SSL certificate of API server" +msgstr "" + +#: ./doc/common/tables/nova-wsgi.xml34(td) +#: ./doc/common/tables/cinder-common.xml198(td) +#: ./doc/common/tables/neutron-ssl.xml31(td) +msgid "ssl_key_file = None" +msgstr "" + +#: ./doc/common/tables/nova-wsgi.xml35(td) +msgid "(StrOpt) SSL private key of API server" +msgstr "" + +#: ./doc/common/tables/nova-wsgi.xml42(td) +msgid "wsgi_default_pool_size = 1000" +msgstr "" + +#: ./doc/common/tables/nova-wsgi.xml43(td) +msgid "(IntOpt) Size of the pool of greenthreads used by wsgi" +msgstr "" + +#: ./doc/common/tables/nova-wsgi.xml46(td) +msgid "" +"wsgi_log_format = %(client_ip)s \"%(request_line)s\" status: %(status_code)s" +" len: %(body_length)s time: %(wall_seconds).7f" +msgstr "" + +#: ./doc/common/tables/nova-wsgi.xml47(td) +msgid "" +"(StrOpt) A python format string that is used as the template to generate log" +" lines. The following values can be formatted into it: client_ip, date_time," +" request_line, status_code, body_length, wall_seconds." +msgstr "" + +#: ./doc/common/tables/cinder-storage_glusterfs.xml8(caption) +msgid "Description of configuration options for storage_glusterfs" +msgstr "" + +#: ./doc/common/tables/cinder-storage_glusterfs.xml23(td) +msgid "(StrOpt) Base dir containing mount points for gluster shares." +msgstr "" + +#: ./doc/common/tables/cinder-storage_glusterfs.xml26(td) +msgid "glusterfs_qcow2_volumes = False" +msgstr "" + +#: ./doc/common/tables/cinder-storage_glusterfs.xml27(td) +msgid "(BoolOpt) Create volumes as QCOW2 files rather than raw files." +msgstr "" + +#: ./doc/common/tables/cinder-storage_glusterfs.xml30(td) +msgid "glusterfs_shares_config = /etc/cinder/glusterfs_shares" +msgstr "" + +#: ./doc/common/tables/cinder-storage_glusterfs.xml31(td) +msgid "(StrOpt) File with the list of available gluster shares" +msgstr "" + +#: ./doc/common/tables/cinder-storage_glusterfs.xml34(td) +msgid "glusterfs_sparsed_volumes = True" +msgstr "" + +#: ./doc/common/tables/nova-availabilityzones.xml8(caption) +msgid "Description of configuration options for availabilityzones" +msgstr "" + +#: ./doc/common/tables/nova-availabilityzones.xml22(td) +msgid "default_availability_zone = nova" +msgstr "" + +#: ./doc/common/tables/nova-availabilityzones.xml23(td) +msgid "(StrOpt) default compute node availability_zone" +msgstr "" + +#: ./doc/common/tables/nova-availabilityzones.xml26(td) +msgid "default_schedule_zone = None" +msgstr "" + +#: ./doc/common/tables/nova-availabilityzones.xml27(td) +msgid "(StrOpt) availability zone to use when user doesn't specify one" +msgstr "" + +#: ./doc/common/tables/nova-availabilityzones.xml30(td) +msgid "internal_service_availability_zone = internal" +msgstr "" + +#: ./doc/common/tables/nova-availabilityzones.xml31(td) +msgid "(StrOpt) availability_zone to show internal services under" +msgstr "" + +#: ./doc/common/tables/nova-vnc.xml8(caption) +msgid "Description of configuration options for vnc" +msgstr "" + +#: ./doc/common/tables/nova-vnc.xml22(td) +msgid "novncproxy_base_url = http://127.0.0.1:6080/vnc_auto.html" +msgstr "" + +#: ./doc/common/tables/nova-vnc.xml23(td) +msgid "" +"(StrOpt) location of vnc console proxy, in the form " +"\"http://127.0.0.1:6080/vnc_auto.html\"" +msgstr "" + +#: ./doc/common/tables/nova-vnc.xml26(td) +msgid "vnc_enabled = True" +msgstr "" + +#: ./doc/common/tables/nova-vnc.xml27(td) +msgid "(BoolOpt) enable vnc related features" +msgstr "" + +#: ./doc/common/tables/nova-vnc.xml30(td) +msgid "vnc_keymap = en-us" +msgstr "" + +#: ./doc/common/tables/nova-vnc.xml31(td) +msgid "(StrOpt) keymap for vnc" +msgstr "" + +#: ./doc/common/tables/nova-vnc.xml34(td) +msgid "vncserver_listen = 127.0.0.1" +msgstr "" + +#: ./doc/common/tables/nova-vnc.xml35(td) +msgid "(StrOpt) IP address on which instance vncservers should listen" +msgstr "" + +#: ./doc/common/tables/nova-vnc.xml38(td) +msgid "vncserver_proxyclient_address = 127.0.0.1" +msgstr "" + +#: ./doc/common/tables/nova-vnc.xml39(td) +msgid "" +"(StrOpt) the address to which proxy clients (like nova-xvpvncproxy) should " +"connect" +msgstr "" + +#: ./doc/common/tables/nova-vnc.xml42(th) +#: ./doc/common/tables/nova-vmware.xml19(th) +#: ./doc/common/tables/nova-network.xml254(th) +msgid "[vmware]" +msgstr "" + +#: ./doc/common/tables/nova-vnc.xml45(td) +msgid "vnc_port = 5900" +msgstr "" + +#: ./doc/common/tables/nova-vnc.xml46(td) +msgid "(IntOpt) VNC starting port" +msgstr "" + +#: ./doc/common/tables/nova-vnc.xml49(td) +msgid "vnc_port_total = 10000" +msgstr "" + +#: ./doc/common/tables/nova-vnc.xml50(td) +msgid "(IntOpt) Total number of VNC ports" +msgstr "" + +#: ./doc/common/tables/swift-swift-swift-constraints.xml7(literal) +msgid "[swift-constraints]" +msgstr "" + +#: ./doc/common/tables/swift-swift-swift-constraints.xml7(literal) +#: ./doc/common/tables/swift-swift-swift-hash.xml7(literal) +msgid "swift.conf-sample" +msgstr "" + +#: ./doc/common/tables/swift-swift-swift-constraints.xml18(td) +msgid "max_file_size = 5368709122" +msgstr "" + +#: ./doc/common/tables/swift-swift-swift-constraints.xml19(td) +msgid "" +"The largest normal object that can be saved in the cluster. This is also the" +" limit on the size of each segment of a large object when using the large " +"object manifest support. This value is set in bytes. Setting it to lower " +"than 1MiB will cause some tests to fail. It is STRONGLY recommended to leave" +" this value at the default (5 * 2**30 + 2)." +msgstr "" + +#: ./doc/common/tables/swift-swift-swift-constraints.xml30(td) +msgid "max_meta_name_length = 128" +msgstr "" + +#: ./doc/common/tables/swift-swift-swift-constraints.xml31(td) +msgid "" +"The maximum number of bytes in the utf8 encoding of the name portion of a " +"metadata header." +msgstr "" + +#: ./doc/common/tables/swift-swift-swift-constraints.xml36(td) +msgid "max_meta_value_length = 256" +msgstr "" + +#: ./doc/common/tables/swift-swift-swift-constraints.xml37(td) +msgid "The max number of bytes in the utf8 encoding of a metadata value." +msgstr "" + +#: ./doc/common/tables/swift-swift-swift-constraints.xml41(td) +msgid "max_meta_count = 90" +msgstr "" + +#: ./doc/common/tables/swift-swift-swift-constraints.xml42(td) +msgid "" +"The maximum number of metadata keys that can be stored on a single account, " +"container, or object." +msgstr "" + +#: ./doc/common/tables/swift-swift-swift-constraints.xml47(td) +msgid "max_meta_overall_size = 4096" +msgstr "" + +#: ./doc/common/tables/swift-swift-swift-constraints.xml48(td) +msgid "" +"The maximum number of bytes in the utf8 encoding of the metadata (keys + " +"values)." +msgstr "" + +#: ./doc/common/tables/swift-swift-swift-constraints.xml53(td) +msgid "max_header_size = 8192" +msgstr "" + +#: ./doc/common/tables/swift-swift-swift-constraints.xml54(td) +msgid "The maximum number of bytes in the utf8 encoding of each header." +msgstr "" + +#: ./doc/common/tables/swift-swift-swift-constraints.xml58(td) +msgid "max_object_name_length = 1024" +msgstr "" + +#: ./doc/common/tables/swift-swift-swift-constraints.xml59(td) +msgid "The maximum number of bytes in the utf8 encoding of an object name." +msgstr "" + +#: ./doc/common/tables/swift-swift-swift-constraints.xml63(td) +msgid "container_listing_limit = 10000" +msgstr "" + +#: ./doc/common/tables/swift-swift-swift-constraints.xml64(td) +msgid "" +"The default (and maximum) number of items returned for a container listing " +"request." +msgstr "" + +#: ./doc/common/tables/swift-swift-swift-constraints.xml69(td) +msgid "account_listing_limit = 10000" +msgstr "" + +#: ./doc/common/tables/swift-swift-swift-constraints.xml70(td) +msgid "" +"The default (and maximum) number of items returned for an account listing " +"request." +msgstr "" + +#: ./doc/common/tables/swift-swift-swift-constraints.xml74(td) +msgid "max_account_name_length = 256" +msgstr "" + +#: ./doc/common/tables/swift-swift-swift-constraints.xml75(td) +msgid "The maximum number of bytes in the utf8 encoding of an account name." +msgstr "" + +#: ./doc/common/tables/swift-swift-swift-constraints.xml79(td) +msgid "max_container_name_length = 256" +msgstr "" + +#: ./doc/common/tables/swift-swift-swift-constraints.xml80(td) +msgid "The maximum number of bytes in the utf8 encoding of a container name." +msgstr "" + +#: ./doc/common/tables/neutron-cisco.xml8(caption) +msgid "Description of configuration options for cisco" +msgstr "" + +#: ./doc/common/tables/neutron-cisco.xml19(td) +msgid "default_network_profile = default_network_profile" +msgstr "" + +#: ./doc/common/tables/neutron-cisco.xml20(td) +msgid "(StrOpt) N1K default network profile" +msgstr "" + +#: ./doc/common/tables/neutron-cisco.xml23(td) +msgid "default_policy_profile = service_profile" +msgstr "" + +#: ./doc/common/tables/neutron-cisco.xml24(td) +msgid "(StrOpt) N1K default policy profile" +msgstr "" + +#: ./doc/common/tables/neutron-cisco.xml27(td) +msgid "" +"model_class = " +"neutron.plugins.cisco.models.virt_phy_sw_v2.VirtualPhysicalSwitchModelV2" +msgstr "" + +#: ./doc/common/tables/neutron-cisco.xml28(td) +msgid "(StrOpt) Model Class" +msgstr "" + +#: ./doc/common/tables/neutron-cisco.xml31(td) +msgid "network_node_policy_profile = dhcp_pp" +msgstr "" + +#: ./doc/common/tables/neutron-cisco.xml32(td) +msgid "(StrOpt) N1K policy profile for network node" +msgstr "" + +#: ./doc/common/tables/neutron-cisco.xml35(td) +msgid "" +"nexus_driver = " +"neutron.plugins.cisco.test.nexus.fake_nexus_driver.CiscoNEXUSFakeDriver" +msgstr "" + +#: ./doc/common/tables/neutron-cisco.xml36(td) +msgid "(StrOpt) Nexus Driver Name" +msgstr "" + +#: ./doc/common/tables/neutron-cisco.xml39(td) +msgid "nexus_l3_enable = False" +msgstr "" + +#: ./doc/common/tables/neutron-cisco.xml40(td) +msgid "(BoolOpt) Enable L3 support on the Nexus switches" +msgstr "" + +#: ./doc/common/tables/neutron-cisco.xml43(td) +msgid "" +"nexus_plugin = neutron.plugins.cisco.nexus.cisco_nexus_plugin_v2.NexusPlugin" +msgstr "" + +#: ./doc/common/tables/neutron-cisco.xml44(td) +msgid "(StrOpt) Nexus Switch to use" +msgstr "" + +#: ./doc/common/tables/neutron-cisco.xml47(td) +msgid "poll_duration = 10" +msgstr "" + +#: ./doc/common/tables/neutron-cisco.xml48(td) +msgid "(StrOpt) N1K Policy profile polling duration in seconds" +msgstr "" + +#: ./doc/common/tables/neutron-cisco.xml51(td) +msgid "provider_vlan_auto_create = True" +msgstr "" + +#: ./doc/common/tables/neutron-cisco.xml52(td) +msgid "" +"(BoolOpt) Provider VLANs are automatically created as needed on the Nexus " +"switch" +msgstr "" + +#: ./doc/common/tables/neutron-cisco.xml55(td) +msgid "provider_vlan_auto_trunk = True" +msgstr "" + +#: ./doc/common/tables/neutron-cisco.xml56(td) +msgid "" +"(BoolOpt) Provider VLANs are automatically trunked as needed on the ports of" +" the Nexus switch" +msgstr "" + +#: ./doc/common/tables/neutron-cisco.xml59(td) +msgid "provider_vlan_name_prefix = p-" +msgstr "" + +#: ./doc/common/tables/neutron-cisco.xml60(td) +msgid "(StrOpt) VLAN Name prefix for provider vlans" +msgstr "" + +#: ./doc/common/tables/neutron-cisco.xml63(td) +#: ./doc/common/tables/neutron-cisco.xml67(td) +msgid "svi_round_robin = False" +msgstr "" + +#: ./doc/common/tables/neutron-cisco.xml64(td) +#: ./doc/common/tables/neutron-cisco.xml68(td) +msgid "(BoolOpt) Distribute SVI interfaces over all switches" +msgstr "" + +#: ./doc/common/tables/neutron-cisco.xml71(td) +#: ./doc/common/tables/neutron-cisco.xml75(td) +msgid "vlan_name_prefix = q-" +msgstr "" + +#: ./doc/common/tables/neutron-cisco.xml72(td) +#: ./doc/common/tables/neutron-cisco.xml76(td) +msgid "(StrOpt) VLAN Name prefix" +msgstr "" + +#: ./doc/common/tables/neutron-cisco.xml79(td) +msgid "" +"vswitch_plugin = " +"neutron.plugins.openvswitch.ovs_neutron_plugin.OVSNeutronPluginV2" +msgstr "" + +#: ./doc/common/tables/neutron-cisco.xml80(td) +msgid "(StrOpt) Virtual Switch to use" +msgstr "" + +#: ./doc/common/tables/neutron-cisco.xml83(td) +msgid "vxlan_id_ranges = 5000:10000" +msgstr "" + +#: ./doc/common/tables/neutron-cisco.xml84(td) +msgid "(StrOpt) N1K VXLAN ID Ranges" +msgstr "" + +#: ./doc/common/tables/nova-hyperv.xml8(caption) +#: ./doc/common/tables/neutron-hyperv.xml8(caption) +msgid "Description of configuration options for hyperv" +msgstr "" + +#: ./doc/common/tables/nova-hyperv.xml22(td) +msgid "dynamic_memory_ratio = 1.0" +msgstr "" + +#: ./doc/common/tables/nova-hyperv.xml23(td) +msgid "" +"(FloatOpt) Enables dynamic memory allocation (ballooning) when set to a " +"value greater than 1. The value expresses the ratio between the total RAM " +"assigned to an instance and its startup RAM amount. For example a ratio of " +"2.0 for an instance with 1024MB of RAM implies 512MB of RAM allocated at " +"startup" +msgstr "" + +#: ./doc/common/tables/nova-hyperv.xml26(td) +msgid "enable_instance_metrics_collection = False" +msgstr "" + +#: ./doc/common/tables/nova-hyperv.xml27(td) +msgid "" +"(BoolOpt) Enables metrics collections for an instance by using Hyper-V's " +"metric APIs. Collected data can by retrieved by other apps and services, " +"e.g.: Ceilometer. Requires Hyper-V / Windows Server 2012 and above" +msgstr "" + +#: ./doc/common/tables/nova-hyperv.xml34(td) +msgid "instances_path_share =" +msgstr "" + +#: ./doc/common/tables/nova-hyperv.xml35(td) +msgid "" +"(StrOpt) The name of a Windows share name mapped to the \"instances_path\" " +"dir and used by the resize feature to copy files to the target host. If left" +" blank, an administrative share will be used, looking for the same " +"\"instances_path\" used locally" +msgstr "" + +#: ./doc/common/tables/nova-hyperv.xml38(td) +msgid "limit_cpu_features = False" +msgstr "" + +#: ./doc/common/tables/nova-hyperv.xml39(td) +msgid "" +"(BoolOpt) Required for live migration among hosts with different CPU " +"features" +msgstr "" + +#: ./doc/common/tables/nova-hyperv.xml42(td) +msgid "qemu_img_cmd = qemu-img.exe" +msgstr "" + +#: ./doc/common/tables/nova-hyperv.xml43(td) +msgid "(StrOpt) qemu-img is used to convert between different image types" +msgstr "" + +#: ./doc/common/tables/nova-hyperv.xml46(td) +msgid "vswitch_name = None" +msgstr "" + +#: ./doc/common/tables/nova-hyperv.xml47(td) +msgid "" +"(StrOpt) External virtual switch Name, if not provided, the first external " +"virtual switch is used" +msgstr "" + +#: ./doc/common/tables/swift-object-server-filter-recon.xml24(td) +msgid "recon_lock_path = /var/lock" +msgstr "" + +#: ./doc/common/tables/cinder-coraid.xml8(caption) +msgid "Description of configuration options for coraid" +msgstr "" + +#: ./doc/common/tables/cinder-coraid.xml22(td) +msgid "coraid_esm_address =" +msgstr "" + +#: ./doc/common/tables/cinder-coraid.xml23(td) +msgid "(StrOpt) IP address of Coraid ESM" +msgstr "" + +#: ./doc/common/tables/cinder-coraid.xml26(td) +msgid "coraid_group = admin" +msgstr "" + +#: ./doc/common/tables/cinder-coraid.xml27(td) +msgid "" +"(StrOpt) Name of group on Coraid ESM to which coraid_user belongs (must have" +" admin privilege)" +msgstr "" + +#: ./doc/common/tables/cinder-coraid.xml30(td) +msgid "coraid_password = password" +msgstr "" + +#: ./doc/common/tables/cinder-coraid.xml31(td) +msgid "(StrOpt) Password to connect to Coraid ESM" +msgstr "" + +#: ./doc/common/tables/cinder-coraid.xml34(td) +msgid "coraid_repository_key = coraid_repository" +msgstr "" + +#: ./doc/common/tables/cinder-coraid.xml35(td) +msgid "(StrOpt) Volume Type key name to store ESM Repository Name" +msgstr "" + +#: ./doc/common/tables/cinder-coraid.xml38(td) +msgid "coraid_user = admin" +msgstr "" + +#: ./doc/common/tables/cinder-coraid.xml39(td) +msgid "(StrOpt) User name to connect to Coraid ESM" +msgstr "" + +#: ./doc/common/tables/swift-container-server-container-auditor.xml7(literal) +msgid "[container-auditor]" +msgstr "" + +#: ./doc/common/tables/swift-container-server-container-auditor.xml18(td) +msgid "log_name = container-auditor" +msgstr "" + +#: ./doc/common/tables/swift-container-server-container-auditor.xml33(td) +msgid "containers_per_second = 200" +msgstr "" + +#: ./doc/common/tables/swift-container-server-container-auditor.xml33(td) +msgid "" +"Maximum containers audited per second. Should be tuned according to " +"individual system specs. 0 is unlimited. mounted to prevent accidentally " +"writing to the root device process simultaneously (it will actually " +"accept(2) N + 1). Setting this to one (1) will only handle one request at a " +"time, without accepting another request concurrently. By increasing the " +"number of workers to a much higher value, one can reduce the impact of slow " +"file system operations in one request from negatively impacting other " +"requests." +msgstr "" + +#: ./doc/common/tables/swift-proxy-server-filter-catch_errors.xml21(td) +msgid "set log_name = catch_errors" +msgstr "" + +#: ./doc/common/tables/nova-vmware.xml22(td) +msgid "api_retry_count = 10" +msgstr "" + +#: ./doc/common/tables/nova-vmware.xml23(td) +msgid "" +"(IntOpt) The number of times we retry on failures, e.g., socket error, etc." +msgstr "" + +#: ./doc/common/tables/nova-vmware.xml26(td) +msgid "cluster_name = None" +msgstr "" + +#: ./doc/common/tables/nova-vmware.xml27(td) +msgid "" +"(MultiStrOpt) Name of a VMware Cluster ComputeResource. Used only if " +"compute_driver is vmwareapi.VMwareVCDriver." +msgstr "" + +#: ./doc/common/tables/nova-vmware.xml30(td) +msgid "datastore_regex = None" +msgstr "" + +#: ./doc/common/tables/nova-vmware.xml31(td) +msgid "" +"(StrOpt) Regex to match the name of a datastore. Used only if compute_driver" +" is vmwareapi.VMwareVCDriver." +msgstr "" + +#: ./doc/common/tables/nova-vmware.xml34(td) +msgid "host_ip = None" +msgstr "" + +#: ./doc/common/tables/nova-vmware.xml35(td) +msgid "(StrOpt) URL for connection to VMware ESX/VC host." +msgstr "" + +#: ./doc/common/tables/nova-vmware.xml38(td) +msgid "host_password = None" +msgstr "" + +#: ./doc/common/tables/nova-vmware.xml39(td) +msgid "(StrOpt) Password for connection to VMware ESX/VC host." +msgstr "" + +#: ./doc/common/tables/nova-vmware.xml42(td) +msgid "host_username = None" +msgstr "" + +#: ./doc/common/tables/nova-vmware.xml43(td) +msgid "(StrOpt) Username for connection to VMware ESX/VC host." +msgstr "" + +#: ./doc/common/tables/nova-vmware.xml47(td) +msgid "(StrOpt) Name of Integration Bridge" +msgstr "" + +#: ./doc/common/tables/nova-vmware.xml50(td) +msgid "maximum_objects = 100" +msgstr "" + +#: ./doc/common/tables/nova-vmware.xml51(td) +msgid "" +"(IntOpt) The maximum number of ObjectContent data objects that should be " +"returned in a single result. A positive value will cause the operation to " +"suspend the retrieval when the count of objects reaches the specified " +"maximum. The server may still limit the count to something less than the " +"configured value. Any remaining objects may be retrieved with additional " +"requests." +msgstr "" + +#: ./doc/common/tables/nova-vmware.xml54(td) +msgid "task_poll_interval = 5.0" +msgstr "" + +#: ./doc/common/tables/nova-vmware.xml55(td) +msgid "(FloatOpt) The interval used for polling of remote tasks." +msgstr "" + +#: ./doc/common/tables/nova-vmware.xml58(td) +msgid "use_linked_clone = True" +msgstr "" + +#: ./doc/common/tables/nova-vmware.xml59(td) +msgid "(BoolOpt) Whether to use linked clone" +msgstr "" + +#: ./doc/common/tables/nova-vmware.xml62(td) +msgid "wsdl_location = None" +msgstr "" + +#: ./doc/common/tables/nova-vmware.xml63(td) +msgid "" +"(StrOpt) Optional VIM Service WSDL Location e.g " +"http://<server>/vimService.wsdl. Optional over-ride to default " +"location for bug work-arounds" +msgstr "" + +#: ./doc/common/tables/nova-logging.xml34(td) +#: ./doc/common/tables/cinder-common.xml62(td) +msgid "fatal_exception_format_errors = False" +msgstr "" + +#: ./doc/common/tables/nova-logging.xml35(td) +#: ./doc/common/tables/cinder-common.xml63(td) +msgid "(BoolOpt) make exception message format errors fatal" +msgstr "" + +#: ./doc/common/tables/nova-xen.xml8(caption) +msgid "Description of configuration options for xen" +msgstr "" + +#: ./doc/common/tables/nova-xen.xml22(td) +msgid "console_driver = nova.console.xvp.XVPConsoleProxy" +msgstr "" + +#: ./doc/common/tables/nova-xen.xml23(td) +msgid "(StrOpt) Driver to use for the console proxy" +msgstr "" + +#: ./doc/common/tables/nova-xen.xml26(td) +msgid "console_vmrc_error_retries = 10" +msgstr "" + +#: ./doc/common/tables/nova-xen.xml27(td) +msgid "(IntOpt) number of retries for retrieving VMRC information" +msgstr "" + +#: ./doc/common/tables/nova-xen.xml30(td) +msgid "console_vmrc_port = 443" +msgstr "" + +#: ./doc/common/tables/nova-xen.xml31(td) +msgid "(IntOpt) port for VMware VMRC connections" +msgstr "" + +#: ./doc/common/tables/nova-xen.xml34(td) +msgid "console_xvp_conf = /etc/xvp.conf" +msgstr "" + +#: ./doc/common/tables/nova-xen.xml35(td) +msgid "(StrOpt) generated XVP conf file" +msgstr "" + +#: ./doc/common/tables/nova-xen.xml38(td) +msgid "console_xvp_conf_template = $pybasedir/nova/console/xvp.conf.template" +msgstr "" + +#: ./doc/common/tables/nova-xen.xml39(td) +msgid "(StrOpt) XVP conf template" +msgstr "" + +#: ./doc/common/tables/nova-xen.xml42(td) +msgid "console_xvp_log = /var/log/xvp.log" +msgstr "" + +#: ./doc/common/tables/nova-xen.xml43(td) +msgid "(StrOpt) XVP log file" +msgstr "" + +#: ./doc/common/tables/nova-xen.xml46(td) +msgid "console_xvp_multiplex_port = 5900" +msgstr "" + +#: ./doc/common/tables/nova-xen.xml47(td) +msgid "(IntOpt) port for XVP to multiplex VNC connections on" +msgstr "" + +#: ./doc/common/tables/nova-xen.xml50(td) +msgid "console_xvp_pid = /var/run/xvp.pid" +msgstr "" + +#: ./doc/common/tables/nova-xen.xml51(td) +msgid "(StrOpt) XVP master process pid file" +msgstr "" + +#: ./doc/common/tables/nova-xen.xml54(td) +msgid "stub_compute = False" +msgstr "" + +#: ./doc/common/tables/nova-xen.xml55(td) +msgid "(BoolOpt) Stub calls to compute worker for tests" +msgstr "" + +#: ./doc/common/tables/nova-xen.xml61(td) +msgid "xen_hvmloader_path = /usr/lib/xen/boot/hvmloader" +msgstr "" + +#: ./doc/common/tables/nova-xen.xml62(td) +msgid "(StrOpt) Location where the Xen hvmloader is kept" +msgstr "" + +#: ./doc/common/tables/nova-xen.xml68(td) +msgid "agent_path = usr/sbin/xe-update-networking" +msgstr "" + +#: ./doc/common/tables/nova-xen.xml69(td) +msgid "" +"(StrOpt) Specifies the path in which the xenapi guest agent should be " +"located. If the agent is present, network configuration is not injected into" +" the image. Used if compute_driver=xenapi.XenAPIDriver and " +"flat_injected=True" +msgstr "" + +#: ./doc/common/tables/nova-xen.xml72(td) +msgid "agent_resetnetwork_timeout = 60" +msgstr "" + +#: ./doc/common/tables/nova-xen.xml73(td) +msgid "" +"(IntOpt) number of seconds to wait for agent reply to resetnetwork request" +msgstr "" + +#: ./doc/common/tables/nova-xen.xml76(td) +msgid "agent_timeout = 30" +msgstr "" + +#: ./doc/common/tables/nova-xen.xml77(td) +msgid "(IntOpt) number of seconds to wait for agent reply" +msgstr "" + +#: ./doc/common/tables/nova-xen.xml80(td) +msgid "agent_version_timeout = 300" +msgstr "" + +#: ./doc/common/tables/nova-xen.xml81(td) +msgid "(IntOpt) number of seconds to wait for agent to be fully operational" +msgstr "" + +#: ./doc/common/tables/nova-xen.xml84(td) +msgid "cache_images = all" +msgstr "" + +#: ./doc/common/tables/nova-xen.xml85(td) +msgid "" +"(StrOpt) Cache glance images locally. `all` will cache all images, `some` " +"will only cache images that have the image_property `cache_in_nova=True`, " +"and `none` turns off caching entirely" +msgstr "" + +#: ./doc/common/tables/nova-xen.xml88(td) +msgid "check_host = True" +msgstr "" + +#: ./doc/common/tables/nova-xen.xml89(td) +msgid "" +"(BoolOpt) Ensure compute service is running on host XenAPI connects to." +msgstr "" + +#: ./doc/common/tables/nova-xen.xml92(td) +msgid "connection_concurrent = 5" +msgstr "" + +#: ./doc/common/tables/nova-xen.xml93(td) +msgid "" +"(IntOpt) Maximum number of concurrent XenAPI connections. Used only if " +"compute_driver=xenapi.XenAPIDriver" +msgstr "" + +#: ./doc/common/tables/nova-xen.xml96(td) +msgid "connection_password = None" +msgstr "" + +#: ./doc/common/tables/nova-xen.xml97(td) +msgid "" +"(StrOpt) Password for connection to XenServer/Xen Cloud Platform. Used only " +"if compute_driver=xenapi.XenAPIDriver" +msgstr "" + +#: ./doc/common/tables/nova-xen.xml100(td) +msgid "connection_url = None" +msgstr "" + +#: ./doc/common/tables/nova-xen.xml101(td) +msgid "" +"(StrOpt) URL for connection to XenServer/Xen Cloud Platform. A special value" +" of unix://local can be used to connect to the local unix socket. Required " +"if compute_driver=xenapi.XenAPIDriver" +msgstr "" + +#: ./doc/common/tables/nova-xen.xml104(td) +msgid "connection_username = root" +msgstr "" + +#: ./doc/common/tables/nova-xen.xml105(td) +msgid "" +"(StrOpt) Username for connection to XenServer/Xen Cloud Platform. Used only " +"if compute_driver=xenapi.XenAPIDriver" +msgstr "" + +#: ./doc/common/tables/nova-xen.xml108(td) +msgid "default_os_type = linux" +msgstr "" + +#: ./doc/common/tables/nova-xen.xml109(td) +msgid "(StrOpt) Default OS type" +msgstr "" + +#: ./doc/common/tables/nova-xen.xml112(td) +msgid "disable_agent = False" +msgstr "" + +#: ./doc/common/tables/nova-xen.xml113(td) +msgid "" +"(BoolOpt) Disables the use of the XenAPI agent in any image regardless of " +"what image properties are present." +msgstr "" + +#: ./doc/common/tables/nova-xen.xml116(td) +msgid "image_compression_level = None" +msgstr "" + +#: ./doc/common/tables/nova-xen.xml117(td) +msgid "" +"(IntOpt) Compression level for images, e.g., 9 for gzip -9. Range is 1-9, 9 " +"being most compressed but most CPU intensive on dom0." +msgstr "" + +#: ./doc/common/tables/nova-xen.xml120(td) +msgid "image_upload_handler = nova.virt.xenapi.image.glance.GlanceStore" +msgstr "" + +#: ./doc/common/tables/nova-xen.xml121(td) +msgid "(StrOpt) Dom0 plugin driver used to handle image uploads." +msgstr "" + +#: ./doc/common/tables/nova-xen.xml124(td) +msgid "ipxe_boot_menu_url = None" +msgstr "" + +#: ./doc/common/tables/nova-xen.xml125(td) +msgid "(StrOpt) URL to the iPXE boot menu" +msgstr "" + +#: ./doc/common/tables/nova-xen.xml128(td) +msgid "ipxe_mkisofs_cmd = mkisofs" +msgstr "" + +#: ./doc/common/tables/nova-xen.xml129(td) +#: ./doc/common/tables/nova-configdrive.xml39(td) +msgid "" +"(StrOpt) Name and optionally path of the tool used for ISO image creation" +msgstr "" + +#: ./doc/common/tables/nova-xen.xml132(td) +msgid "ipxe_network_name = None" +msgstr "" + +#: ./doc/common/tables/nova-xen.xml133(td) +msgid "(StrOpt) Name of network to use for booting iPXE ISOs" +msgstr "" + +#: ./doc/common/tables/nova-xen.xml136(td) +msgid "iqn_prefix = iqn.2010-10.org.openstack" +msgstr "" + +#: ./doc/common/tables/nova-xen.xml137(td) +msgid "(StrOpt) IQN Prefix" +msgstr "" + +#: ./doc/common/tables/nova-xen.xml140(td) +msgid "login_timeout = 10" +msgstr "" + +#: ./doc/common/tables/nova-xen.xml141(td) +msgid "(IntOpt) Timeout in seconds for XenAPI login." +msgstr "" + +#: ./doc/common/tables/nova-xen.xml144(td) +msgid "max_kernel_ramdisk_size = 16777216" +msgstr "" + +#: ./doc/common/tables/nova-xen.xml145(td) +msgid "(IntOpt) Maximum size in bytes of kernel or ramdisk images" +msgstr "" + +#: ./doc/common/tables/nova-xen.xml148(td) +msgid "num_vbd_unplug_retries = 10" +msgstr "" + +#: ./doc/common/tables/nova-xen.xml149(td) +msgid "(IntOpt) Maximum number of retries to unplug VBD" +msgstr "" + +#: ./doc/common/tables/nova-xen.xml152(td) +msgid "ovs_integration_bridge = xapi1" +msgstr "" + +#: ./doc/common/tables/nova-xen.xml156(td) +msgid "remap_vbd_dev = False" +msgstr "" + +#: ./doc/common/tables/nova-xen.xml157(td) +msgid "" +"(BoolOpt) Used to enable the remapping of VBD dev (Works around an issue in " +"Ubuntu Maverick)" +msgstr "" + +#: ./doc/common/tables/nova-xen.xml160(td) +msgid "remap_vbd_dev_prefix = sd" +msgstr "" + +#: ./doc/common/tables/nova-xen.xml161(td) +msgid "" +"(StrOpt) Specify prefix to remap VBD dev to (ex. /dev/xvdb -> /dev/sdb)" +msgstr "" + +#: ./doc/common/tables/nova-xen.xml164(td) +msgid "running_timeout = 60" +msgstr "" + +#: ./doc/common/tables/nova-xen.xml165(td) +msgid "(IntOpt) number of seconds to wait for instance to go to running state" +msgstr "" + +#: ./doc/common/tables/nova-xen.xml168(td) +msgid "sparse_copy = True" +msgstr "" + +#: ./doc/common/tables/nova-xen.xml169(td) +msgid "" +"(BoolOpt) Whether to use sparse_copy for copying data on a resize down " +"(False will use standard dd). This speeds up resizes down considerably since" +" large runs of zeros won't have to be rsynced" +msgstr "" + +#: ./doc/common/tables/nova-xen.xml172(td) +msgid "sr_base_path = /var/run/sr-mount" +msgstr "" + +#: ./doc/common/tables/nova-xen.xml173(td) +#: ./doc/common/tables/cinder-storage_xen.xml43(td) +msgid "(StrOpt) Base path to the storage repository" +msgstr "" + +#: ./doc/common/tables/nova-xen.xml176(td) +msgid "sr_matching_filter = default-sr:true" +msgstr "" + +#: ./doc/common/tables/nova-xen.xml177(td) +msgid "" +"(StrOpt) Filter for finding the SR to be used to install guest instances on." +" To use the Local Storage in default XenServer/XCP installations set this " +"flag to other-config:i18n-key=local-storage. To select an SR with a " +"different matching criteria, you could set it to other-" +"config:my_favorite_sr=true. On the other hand, to fall back on the Default " +"SR, as displayed by XenCenter, set this flag to: default-sr:true" +msgstr "" + +#: ./doc/common/tables/nova-xen.xml180(td) +msgid "target_host = None" +msgstr "" + +#: ./doc/common/tables/nova-xen.xml181(td) +msgid "(StrOpt) iSCSI Target Host" +msgstr "" + +#: ./doc/common/tables/nova-xen.xml184(td) +msgid "target_port = 3260" +msgstr "" + +#: ./doc/common/tables/nova-xen.xml185(td) +msgid "(StrOpt) iSCSI Target Port, 3260 Default" +msgstr "" + +#: ./doc/common/tables/nova-xen.xml188(td) +msgid "torrent_base_url = None" +msgstr "" + +#: ./doc/common/tables/nova-xen.xml189(td) +msgid "(StrOpt) Base URL for torrent files." +msgstr "" + +#: ./doc/common/tables/nova-xen.xml192(td) +msgid "torrent_download_stall_cutoff = 600" +msgstr "" + +#: ./doc/common/tables/nova-xen.xml193(td) +msgid "" +"(IntOpt) Number of seconds a download can remain at the same progress " +"percentage w/o being considered a stall" +msgstr "" + +#: ./doc/common/tables/nova-xen.xml196(td) +msgid "torrent_images = none" +msgstr "" + +#: ./doc/common/tables/nova-xen.xml197(td) +msgid "" +"(StrOpt) Whether or not to download images via Bit Torrent (all|some|none)." +msgstr "" + +#: ./doc/common/tables/nova-xen.xml200(td) +msgid "torrent_listen_port_end = 6891" +msgstr "" + +#: ./doc/common/tables/nova-xen.xml201(td) +msgid "(IntOpt) End of port range to listen on" +msgstr "" + +#: ./doc/common/tables/nova-xen.xml204(td) +msgid "torrent_listen_port_start = 6881" +msgstr "" + +#: ./doc/common/tables/nova-xen.xml205(td) +msgid "(IntOpt) Beginning of port range to listen on" +msgstr "" + +#: ./doc/common/tables/nova-xen.xml208(td) +msgid "torrent_max_last_accessed = 86400" +msgstr "" + +#: ./doc/common/tables/nova-xen.xml209(td) +msgid "" +"(IntOpt) Cached torrent files not accessed within this number of seconds can" +" be reaped" +msgstr "" + +#: ./doc/common/tables/nova-xen.xml212(td) +msgid "torrent_max_seeder_processes_per_host = 1" +msgstr "" + +#: ./doc/common/tables/nova-xen.xml213(td) +msgid "" +"(IntOpt) Maximum number of seeder processes to run concurrently within a " +"given dom0. (-1 = no limit)" +msgstr "" + +#: ./doc/common/tables/nova-xen.xml216(td) +msgid "torrent_seed_chance = 1.0" +msgstr "" + +#: ./doc/common/tables/nova-xen.xml217(td) +msgid "(FloatOpt) Probability that peer will become a seeder. (1.0 = 100%)" +msgstr "" + +#: ./doc/common/tables/nova-xen.xml220(td) +msgid "torrent_seed_duration = 3600" +msgstr "" + +#: ./doc/common/tables/nova-xen.xml221(td) +msgid "" +"(IntOpt) Number of seconds after downloading an image via BitTorrent that it" +" should be seeded for other peers." +msgstr "" + +#: ./doc/common/tables/nova-xen.xml224(td) +msgid "use_agent_default = False" +msgstr "" + +#: ./doc/common/tables/nova-xen.xml225(td) +msgid "" +"(BoolOpt) Determines if the xenapi agent should be used when the image used " +"does not contain a hint to declare if the agent is present or not. The hint " +"is a glance property \"xenapi_use_agent\" that has the value \"true\" or " +"\"false\". Note that waiting for the agent when it is not present will " +"significantly increase server boot times." +msgstr "" + +#: ./doc/common/tables/nova-xen.xml228(td) +msgid "use_join_force = True" +msgstr "" + +#: ./doc/common/tables/nova-xen.xml229(td) +msgid "(BoolOpt) To use for hosts with different CPUs" +msgstr "" + +#: ./doc/common/tables/nova-xen.xml232(td) +msgid "vhd_coalesce_max_attempts = 5" +msgstr "" + +#: ./doc/common/tables/nova-xen.xml233(td) +msgid "" +"(IntOpt) Max number of times to poll for VHD to coalesce. Used only if " +"compute_driver=xenapi.XenAPIDriver" +msgstr "" + +#: ./doc/common/tables/nova-xen.xml236(td) +msgid "vhd_coalesce_poll_interval = 5.0" +msgstr "" + +#: ./doc/common/tables/nova-xen.xml237(td) +msgid "" +"(FloatOpt) The interval used for polling of coalescing vhds. Used only if " +"compute_driver=xenapi.XenAPIDriver" +msgstr "" + +#: ./doc/common/tables/swift-proxy-server-filter-list-endpoints.xml7(literal) +msgid "[filter:list-endpoints]" +msgstr "" + +#: ./doc/common/tables/swift-proxy-server-filter-list-endpoints.xml18(td) +msgid "use = egg:swift#list_endpoints" +msgstr "" + +#: ./doc/common/tables/swift-proxy-server-filter-list-endpoints.xml21(td) +msgid "list_endpoints_path = /endpoints/" +msgstr "" + +#: ./doc/common/tables/neutron-nicira.xml8(caption) +msgid "Description of configuration options for nicira" +msgstr "" + +#: ./doc/common/tables/neutron-nicira.xml19(td) +msgid "agent_mode = agent" +msgstr "" + +#: ./doc/common/tables/neutron-nicira.xml20(td) +msgid "(StrOpt) The mode used to implement DHCP/metadata services." +msgstr "" + +#: ./doc/common/tables/neutron-nicira.xml23(td) +msgid "always_read_status = False" +msgstr "" + +#: ./doc/common/tables/neutron-nicira.xml24(td) +msgid "" +"(BoolOpt) Always read operational status from backend on show operations. " +"Enabling this option might slow down the system." +msgstr "" + +#: ./doc/common/tables/neutron-nicira.xml27(td) +msgid "concurrent_connections = 10" +msgstr "" + +#: ./doc/common/tables/neutron-nicira.xml28(td) +msgid "(IntOpt) Maximum concurrent connections to each NSX controller." +msgstr "" + +#: ./doc/common/tables/neutron-nicira.xml31(td) +msgid "datacenter_moid = None" +msgstr "" + +#: ./doc/common/tables/neutron-nicira.xml32(td) +msgid "" +"(StrOpt) Optional parameter identifying the ID of datacenter to deploy NSX " +"Edges" +msgstr "" + +#: ./doc/common/tables/neutron-nicira.xml35(td) +msgid "datastore_id = None" +msgstr "" + +#: ./doc/common/tables/neutron-nicira.xml36(td) +#: ./doc/common/tables/neutron-nicira.xml64(td) +msgid "" +"(StrOpt) Optional parameter identifying the ID of datastore to deploy NSX " +"Edges" +msgstr "" + +#: ./doc/common/tables/neutron-nicira.xml39(td) +msgid "default_interface_name = breth0" +msgstr "" + +#: ./doc/common/tables/neutron-nicira.xml40(td) +msgid "" +"(StrOpt) Name of the interface on a L2 Gateway transport nodewhich should be" +" used by default when setting up a network connection" +msgstr "" + +#: ./doc/common/tables/neutron-nicira.xml43(td) +msgid "default_l2_gw_service_uuid = None" +msgstr "" + +#: ./doc/common/tables/neutron-nicira.xml44(td) +msgid "" +"(StrOpt) Unique identifier of the NSX L2 Gateway service which will be used " +"by default for network gateways" +msgstr "" + +#: ./doc/common/tables/neutron-nicira.xml47(td) +msgid "default_l3_gw_service_uuid = None" +msgstr "" + +#: ./doc/common/tables/neutron-nicira.xml48(td) +msgid "" +"(StrOpt) Unique identifier of the NSX L3 Gateway service which will be used " +"for implementing routers and floating IPs" +msgstr "" + +#: ./doc/common/tables/neutron-nicira.xml51(td) +msgid "default_service_cluster_uuid = None" +msgstr "" + +#: ./doc/common/tables/neutron-nicira.xml52(td) +msgid "" +"(StrOpt) Unique identifier of the Service Cluster which will be used by " +"logical services like dhcp and metadata" +msgstr "" + +#: ./doc/common/tables/neutron-nicira.xml55(td) +msgid "default_transport_type = stt" +msgstr "" + +#: ./doc/common/tables/neutron-nicira.xml56(td) +msgid "" +"(StrOpt) The default network tranport type to use (stt, gre, bridge, " +"ipsec_gre, or ipsec_stt)" +msgstr "" + +#: ./doc/common/tables/neutron-nicira.xml59(td) +msgid "default_tz_uuid = None" +msgstr "" + +#: ./doc/common/tables/neutron-nicira.xml60(td) +msgid "" +"(StrOpt) This is uuid of the default NSX Transport zone that will be used " +"for creating tunneled isolated \"Neutron\" networks. It needs to be created " +"in NSX before starting Neutron with the nsx plugin." +msgstr "" + +#: ./doc/common/tables/neutron-nicira.xml63(td) +msgid "deployment_container_id = None" +msgstr "" + +#: ./doc/common/tables/neutron-nicira.xml67(td) +msgid "external_network = None" +msgstr "" + +#: ./doc/common/tables/neutron-nicira.xml68(td) +msgid "(StrOpt) Network ID for physical network connectivity" +msgstr "" + +#: ./doc/common/tables/neutron-nicira.xml71(td) +msgid "http_timeout = 10" +msgstr "" + +#: ./doc/common/tables/neutron-nicira.xml72(td) +msgid "(IntOpt) Time before aborting a request" +msgstr "" + +#: ./doc/common/tables/neutron-nicira.xml75(td) +msgid "manager_uri = None" +msgstr "" + +#: ./doc/common/tables/neutron-nicira.xml76(td) +msgid "(StrOpt) uri for vsm" +msgstr "" + +#: ./doc/common/tables/neutron-nicira.xml79(td) +msgid "max_lp_per_bridged_ls = 5000" +msgstr "" + +#: ./doc/common/tables/neutron-nicira.xml80(td) +msgid "" +"(IntOpt) Maximum number of ports of a logical switch on a bridged transport " +"zone (default 5000)" +msgstr "" + +#: ./doc/common/tables/neutron-nicira.xml83(td) +msgid "max_lp_per_overlay_ls = 256" +msgstr "" + +#: ./doc/common/tables/neutron-nicira.xml84(td) +msgid "" +"(IntOpt) Maximum number of ports of a logical switch on an overlay transport" +" zone (default 256)" +msgstr "" + +#: ./doc/common/tables/neutron-nicira.xml87(td) +msgid "max_random_sync_delay = 0" +msgstr "" + +#: ./doc/common/tables/neutron-nicira.xml88(td) +msgid "" +"(IntOpt) Maximum value for the additional random delay in seconds between " +"runs of the state synchronization task" +msgstr "" + +#: ./doc/common/tables/neutron-nicira.xml91(td) +msgid "metadata_mode = access_network" +msgstr "" + +#: ./doc/common/tables/neutron-nicira.xml92(td) +msgid "" +"(StrOpt) If set to access_network this enables a dedicated connection to the" +" metadata proxy for metadata server access via Neutron router. If set to " +"dhcp_host_route this enables host route injection via the dhcp agent. This " +"option is only useful if running on a host that does not support namespaces " +"otherwise access_network should be used." +msgstr "" + +#: ./doc/common/tables/neutron-nicira.xml95(td) +msgid "min_chunk_size = 500" +msgstr "" + +#: ./doc/common/tables/neutron-nicira.xml96(td) +msgid "" +"(IntOpt) Minimum number of resources to be retrieved from NSX during state " +"synchronization" +msgstr "" + +#: ./doc/common/tables/neutron-nicira.xml99(td) +msgid "min_sync_req_delay = 10" +msgstr "" + +#: ./doc/common/tables/neutron-nicira.xml100(td) +msgid "" +"(IntOpt) Minimum delay, in seconds, between two state synchronization " +"queries to NSX. It must not exceed state_sync_interval" +msgstr "" + +#: ./doc/common/tables/neutron-nicira.xml103(td) +msgid "nsx_controllers = None" +msgstr "" + +#: ./doc/common/tables/neutron-nicira.xml104(td) +msgid "(ListOpt) Lists the NSX controllers in this cluster" +msgstr "" + +#: ./doc/common/tables/neutron-nicira.xml107(td) +msgid "nsx_gen_timeout = -1" +msgstr "" + +#: ./doc/common/tables/neutron-nicira.xml108(td) +msgid "" +"(IntOpt) Number of seconds a generation id should be valid for (default -1 " +"meaning do not time out)" +msgstr "" + +#: ./doc/common/tables/neutron-nicira.xml111(td) +msgid "nsx_password = admin" +msgstr "" + +#: ./doc/common/tables/neutron-nicira.xml112(td) +msgid "(StrOpt) Password for NSX controllers in this cluster" +msgstr "" + +#: ./doc/common/tables/neutron-nicira.xml115(td) +msgid "nsx_user = admin" +msgstr "" + +#: ./doc/common/tables/neutron-nicira.xml116(td) +msgid "(StrOpt) User name for NSX controllers in this cluster" +msgstr "" + +#: ./doc/common/tables/neutron-nicira.xml119(td) +msgid "redirects = 2" +msgstr "" + +#: ./doc/common/tables/neutron-nicira.xml120(td) +msgid "(IntOpt) Number of times a redirect should be followed" +msgstr "" + +#: ./doc/common/tables/neutron-nicira.xml123(td) +msgid "req_timeout = 30" +msgstr "" + +#: ./doc/common/tables/neutron-nicira.xml124(td) +msgid "(IntOpt) Total time limit for a cluster request" +msgstr "" + +#: ./doc/common/tables/neutron-nicira.xml127(td) +msgid "resource_pool_id = None" +msgstr "" + +#: ./doc/common/tables/neutron-nicira.xml128(td) +msgid "" +"(StrOpt) Optional parameter identifying the ID of resource to deploy NSX " +"Edges" +msgstr "" + +#: ./doc/common/tables/neutron-nicira.xml131(td) +msgid "retries = 2" +msgstr "" + +#: ./doc/common/tables/neutron-nicira.xml132(td) +msgid "(IntOpt) Number of time a request should be retried" +msgstr "" + +#: ./doc/common/tables/neutron-nicira.xml135(td) +msgid "retries = 3" +msgstr "" + +#: ./doc/common/tables/neutron-nicira.xml136(td) +msgid "" +"(IntOpt) The number of retries the agent will send request to daemon before " +"giving up" +msgstr "" + +#: ./doc/common/tables/neutron-nicira.xml139(td) +msgid "state_sync_interval = 120" +msgstr "" + +#: ./doc/common/tables/neutron-nicira.xml140(td) +msgid "" +"(IntOpt) Interval in seconds between runs of the state synchronization task." +" Set it to 0 to disable it" +msgstr "" + +#: ./doc/common/tables/neutron-nicira.xml143(td) +msgid "task_status_check_interval = 2000" +msgstr "" + +#: ./doc/common/tables/neutron-nicira.xml144(td) +msgid "(IntOpt) Task status check interval" +msgstr "" + +#: ./doc/common/tables/neutron-nicira.xml147(td) +msgid "user = admin" +msgstr "" + +#: ./doc/common/tables/neutron-nicira.xml148(td) +msgid "(StrOpt) User name for vsm" +msgstr "" + +#: ./doc/common/tables/swift-memcache-memcache.xml7(literal) +msgid "[memcache]" +msgstr "" + +#: ./doc/common/tables/swift-memcache-memcache.xml7(literal) +msgid "memcache.conf-sample" +msgstr "" + +#: ./doc/common/tables/swift-proxy-server-filter-keystoneauth.xml7(literal) +msgid "[filter:keystoneauth]" +msgstr "" + +#: ./doc/common/tables/swift-proxy-server-filter-keystoneauth.xml18(td) +msgid "use = egg:swift#keystoneauth" +msgstr "" + +#: ./doc/common/tables/swift-proxy-server-filter-keystoneauth.xml21(td) +msgid "operator_roles = admin, swiftoperator" +msgstr "" + +#: ./doc/common/tables/neutron-ml2.xml8(caption) +msgid "Description of configuration options for ml2" +msgstr "" + +#: ./doc/common/tables/neutron-ml2.xml19(td) +msgid "mechanism_drivers =" +msgstr "" + +#: ./doc/common/tables/neutron-ml2.xml20(td) +msgid "" +"(ListOpt) An ordered list of networking mechanism driver entrypoints to be " +"loaded from the neutron.ml2.mechanism_drivers namespace." +msgstr "" + +#: ./doc/common/tables/neutron-ml2.xml23(td) +msgid "tenant_network_types = local" +msgstr "" + +#: ./doc/common/tables/neutron-ml2.xml24(td) +msgid "" +"(ListOpt) Ordered list of network_types to allocate as tenant networks." +msgstr "" + +#: ./doc/common/tables/neutron-ml2.xml27(td) +msgid "type_drivers = local, flat, vlan, gre, vxlan" +msgstr "" + +#: ./doc/common/tables/neutron-ml2.xml28(td) +msgid "" +"(ListOpt) List of network type driver entrypoints to be loaded from the " +"neutron.ml2.type_drivers namespace." +msgstr "" + +#: ./doc/common/tables/neutron-linuxbridge.xml8(caption) +msgid "Description of configuration options for linuxbridge" +msgstr "" + +#: ./doc/common/tables/neutron-linuxbridge.xml20(td) +msgid "(StrOpt) Network type for tenant networks (local, vlan, or none)" +msgstr "" + +#: ./doc/common/tables/cinder-netapp_7mode_nfs.xml8(caption) +msgid "Description of configuration options for netapp_7mode_nfs" +msgstr "" + +#: ./doc/common/tables/cinder-netapp_7mode_nfs.xml22(td) +#: ./doc/common/tables/cinder-netapp_cdot_nfs.xml22(td) +msgid "expiry_thres_minutes = 720" +msgstr "" + +#: ./doc/common/tables/cinder-netapp_7mode_nfs.xml23(td) +#: ./doc/common/tables/cinder-netapp_cdot_nfs.xml23(td) +msgid "" +"(IntOpt) This option specifies the threshold for last access time for images" +" in the NFS image cache. When a cache cleaning cycle begins, images in the " +"cache that have not been accessed in the last M minutes, where M is the " +"value of this parameter, will be deleted from the cache to create free space" +" on the NFS share." +msgstr "" + +#: ./doc/common/tables/cinder-netapp_7mode_nfs.xml54(td) +#: ./doc/common/tables/cinder-netapp_cdot_nfs.xml58(td) +msgid "thres_avl_size_perc_start = 20" +msgstr "" + +#: ./doc/common/tables/cinder-netapp_7mode_nfs.xml55(td) +#: ./doc/common/tables/cinder-netapp_cdot_nfs.xml59(td) +msgid "" +"(IntOpt) If the percentage of available space for an NFS share has dropped " +"below the value specified by this option, the NFS image cache will be " +"cleaned." +msgstr "" + +#: ./doc/common/tables/cinder-netapp_7mode_nfs.xml58(td) +#: ./doc/common/tables/cinder-netapp_cdot_nfs.xml62(td) +msgid "thres_avl_size_perc_stop = 60" +msgstr "" + +#: ./doc/common/tables/cinder-netapp_7mode_nfs.xml59(td) +#: ./doc/common/tables/cinder-netapp_cdot_nfs.xml63(td) +msgid "" +"(IntOpt) When the percentage of available space on an NFS share has reached " +"the percentage specified by this option, the driver will stop clearing files" +" from the NFS image cache that have not been accessed in the last M minutes," +" where M is the value of the expiry_thres_minutes configuration option." +msgstr "" + +#: ./doc/common/tables/glance-common.xml22(td) +msgid "allow_additional_image_properties = True" +msgstr "" + +#: ./doc/common/tables/glance-common.xml23(td) +msgid "" +"(BoolOpt) Whether to allow users to specify image properties beyond what the" +" image schema provides" +msgstr "" + +#: ./doc/common/tables/glance-common.xml26(td) +msgid "api_limit_max = 1000" +msgstr "" + +#: ./doc/common/tables/glance-common.xml27(td) +msgid "" +"(IntOpt) Maximum permissible number of items that could be returned by a " +"request" +msgstr "" + +#: ./doc/common/tables/glance-common.xml31(td) +msgid "" +"(IntOpt) The backlog value that will be used when creating the TCP listener " +"socket." +msgstr "" + +#: ./doc/common/tables/glance-common.xml35(td) +msgid "" +"(StrOpt) Address to bind the server. Useful when selecting a particular " +"network interface." +msgstr "" + +#: ./doc/common/tables/glance-common.xml38(td) +msgid "bind_port = None" +msgstr "" + +#: ./doc/common/tables/glance-common.xml39(td) +msgid "(IntOpt) The port on which the server will listen." +msgstr "" + +#: ./doc/common/tables/glance-common.xml42(td) +msgid "data_api = glance.db.sqlalchemy.api" +msgstr "" + +#: ./doc/common/tables/glance-common.xml43(td) +msgid "(StrOpt) Python module path of data access API" +msgstr "" + +#: ./doc/common/tables/glance-common.xml50(td) +msgid "image_location_quota = 10" +msgstr "" + +#: ./doc/common/tables/glance-common.xml51(td) +msgid "" +"(IntOpt) Maximum number of locations allowed on an image. Negative values " +"evaluate to unlimited." +msgstr "" + +#: ./doc/common/tables/glance-common.xml54(td) +msgid "image_member_quota = 128" +msgstr "" + +#: ./doc/common/tables/glance-common.xml55(td) +msgid "" +"(IntOpt) Maximum number of image members per image. Negative values evaluate" +" to unlimited." +msgstr "" + +#: ./doc/common/tables/glance-common.xml58(td) +msgid "image_property_quota = 128" +msgstr "" + +#: ./doc/common/tables/glance-common.xml59(td) +msgid "" +"(IntOpt) Maximum number of properties allowed on an image. Negative values " +"evaluate to unlimited." +msgstr "" + +#: ./doc/common/tables/glance-common.xml62(td) +msgid "image_tag_quota = 128" +msgstr "" + +#: ./doc/common/tables/glance-common.xml63(td) +msgid "" +"(IntOpt) Maximum number of tags allowed on an image. Negative values " +"evaluate to unlimited." +msgstr "" + +#: ./doc/common/tables/glance-common.xml66(td) +msgid "limit_param_default = 25" +msgstr "" + +#: ./doc/common/tables/glance-common.xml67(td) +msgid "" +"(IntOpt) Default value for the number of items returned by a request if not " +"specified explicitly in the request" +msgstr "" + +#: ./doc/common/tables/glance-common.xml74(td) +msgid "metadata_encryption_key = None" +msgstr "" + +#: ./doc/common/tables/glance-common.xml75(td) +msgid "" +"(StrOpt) Key used for encrypting sensitive metadata while talking to the " +"registry or database." +msgstr "" + +#: ./doc/common/tables/glance-common.xml78(td) +msgid "notifier_strategy = default" +msgstr "" + +#: ./doc/common/tables/glance-common.xml79(td) +msgid "" +"(StrOpt) Notifications can be sent when images are create, updated or " +"deleted. There are three methods of sending notifications, logging (via the " +"log_file directive), rabbit (via a rabbitmq queue), qpid (via a Qpid message" +" queue), or noop (no notifications sent, the default). (DEPRECATED)" +msgstr "" + +#: ./doc/common/tables/glance-common.xml83(td) +msgid "(StrOpt) Region name of this node" +msgstr "" + +#: ./doc/common/tables/glance-common.xml86(td) +msgid "property_protection_file = None" +msgstr "" + +#: ./doc/common/tables/glance-common.xml87(td) +msgid "(StrOpt) The location of the property protection file." +msgstr "" + +#: ./doc/common/tables/glance-common.xml90(td) +msgid "property_protection_rule_format = roles" +msgstr "" + +#: ./doc/common/tables/glance-common.xml91(td) +msgid "" +"(StrOpt) This config value indicates whether \"roles\" or \"policies\" are " +"used in the property protection file." +msgstr "" + +#: ./doc/common/tables/glance-common.xml94(td) +msgid "show_image_direct_url = False" +msgstr "" + +#: ./doc/common/tables/glance-common.xml95(td) +msgid "" +"(BoolOpt) Whether to include the backend image storage location in image " +"properties. Revealing storage location can be a security risk, so use this " +"setting with caution!" +msgstr "" + +#: ./doc/common/tables/glance-common.xml98(td) +msgid "user_storage_quota = 0" +msgstr "" + +#: ./doc/common/tables/glance-common.xml99(td) +msgid "" +"(IntOpt) Set a system wide quota for every user. This value is the total " +"number of bytes that a user can use across all storage systems. A value of 0" +" means unlimited." +msgstr "" + +#: ./doc/common/tables/glance-common.xml102(td) +msgid "workers = 1" +msgstr "" + +#: ./doc/common/tables/glance-common.xml103(td) +msgid "" +"(IntOpt) The number of child process workers that will be created to service" +" API requests." +msgstr "" + +#: ./doc/common/tables/glance-common.xml109(td) +#: ./doc/common/tables/cinder-common.xml249(td) +#: ./doc/common/tables/neutron-db.xml79(td) +#: ./doc/common/tables/nova-api.xml93(td) +msgid "use_tpool = False" +msgstr "" + +#: ./doc/common/tables/glance-common.xml110(td) +#: ./doc/common/tables/cinder-common.xml250(td) +#: ./doc/common/tables/neutron-db.xml80(td) +#: ./doc/common/tables/nova-api.xml94(td) +msgid "" +"(BoolOpt) Enable the experimental use of thread pooling for all DB API calls" +msgstr "" + +#: ./doc/common/tables/glance-common.xml113(th) +msgid "[image_format]" +msgstr "" + +#: ./doc/common/tables/glance-common.xml116(td) +msgid "container_formats = ami, ari, aki, bare, ovf" +msgstr "" + +#: ./doc/common/tables/glance-common.xml117(td) +msgid "(ListOpt) Supported values for the 'container_format' image attribute" +msgstr "" + +#: ./doc/common/tables/glance-common.xml120(td) +msgid "disk_formats = ami, ari, aki, vhd, vmdk, raw, qcow2, vdi, iso" +msgstr "" + +#: ./doc/common/tables/glance-common.xml121(td) +msgid "(ListOpt) Supported values for the 'disk_format' image attribute" +msgstr "" + +#: ./doc/common/tables/glance-common.xml124(th) +msgid "[task]" +msgstr "" + +#: ./doc/common/tables/glance-common.xml127(td) +msgid "task_time_to_live = 48" +msgstr "" + +#: ./doc/common/tables/glance-common.xml128(td) +msgid "" +"(IntOpt) Time in hours for which a task lives after, either succeeding or " +"failing" +msgstr "" + +#: ./doc/common/tables/nova-network.xml8(caption) +msgid "Description of configuration options for network" +msgstr "" + +#: ./doc/common/tables/nova-network.xml22(td) +msgid "allow_same_net_traffic = True" +msgstr "" + +#: ./doc/common/tables/nova-network.xml23(td) +msgid "(BoolOpt) Whether to allow network traffic from same network" +msgstr "" + +#: ./doc/common/tables/nova-network.xml26(td) +msgid "auto_assign_floating_ip = False" +msgstr "" + +#: ./doc/common/tables/nova-network.xml27(td) +msgid "(BoolOpt) Autoassigning floating ip to VM" +msgstr "" + +#: ./doc/common/tables/nova-network.xml30(td) +msgid "cnt_vpn_clients = 0" +msgstr "" + +#: ./doc/common/tables/nova-network.xml31(td) +msgid "(IntOpt) Number of addresses reserved for vpn clients" +msgstr "" + +#: ./doc/common/tables/nova-network.xml34(td) +msgid "create_unique_mac_address_attempts = 5" +msgstr "" + +#: ./doc/common/tables/nova-network.xml35(td) +msgid "(IntOpt) Number of attempts to create unique mac address" +msgstr "" + +#: ./doc/common/tables/nova-network.xml38(td) +msgid "default_access_ip_network_name = None" +msgstr "" + +#: ./doc/common/tables/nova-network.xml39(td) +msgid "(StrOpt) Name of network to use to set access ips for instances" +msgstr "" + +#: ./doc/common/tables/nova-network.xml42(td) +msgid "default_floating_pool = nova" +msgstr "" + +#: ./doc/common/tables/nova-network.xml43(td) +msgid "(StrOpt) Default pool for floating ips" +msgstr "" + +#: ./doc/common/tables/nova-network.xml46(td) +msgid "defer_iptables_apply = False" +msgstr "" + +#: ./doc/common/tables/nova-network.xml47(td) +msgid "" +"(BoolOpt) Whether to batch up the application of IPTables rules during a " +"host restart and apply all at the end of the init phase" +msgstr "" + +#: ./doc/common/tables/nova-network.xml50(td) +msgid "dhcp_domain = novalocal" +msgstr "" + +#: ./doc/common/tables/nova-network.xml51(td) +msgid "(StrOpt) domain to use for building the hostnames" +msgstr "" + +#: ./doc/common/tables/nova-network.xml54(td) +msgid "dhcp_lease_time = 120" +msgstr "" + +#: ./doc/common/tables/nova-network.xml55(td) +msgid "(IntOpt) Lifetime of a DHCP lease in seconds" +msgstr "" + +#: ./doc/common/tables/nova-network.xml58(td) +msgid "dhcpbridge = $bindir/nova-dhcpbridge" +msgstr "" + +#: ./doc/common/tables/nova-network.xml59(td) +msgid "(StrOpt) location of nova-dhcpbridge" +msgstr "" + +#: ./doc/common/tables/nova-network.xml62(td) +msgid "dhcpbridge_flagfile = ['/etc/nova/nova-dhcpbridge.conf']" +msgstr "" + +#: ./doc/common/tables/nova-network.xml63(td) +msgid "(MultiStrOpt) location of flagfiles for dhcpbridge" +msgstr "" + +#: ./doc/common/tables/nova-network.xml66(td) +msgid "dns_server = []" +msgstr "" + +#: ./doc/common/tables/nova-network.xml67(td) +msgid "" +"(MultiStrOpt) if set, uses specific dns server for dnsmasq. Canbe specified " +"multiple times." +msgstr "" + +#: ./doc/common/tables/nova-network.xml70(td) +msgid "dns_update_periodic_interval = -1" +msgstr "" + +#: ./doc/common/tables/nova-network.xml71(td) +msgid "" +"(IntOpt) Number of seconds to wait between runs of updates to DNS entries." +msgstr "" + +#: ./doc/common/tables/nova-network.xml74(td) +msgid "dnsmasq_config_file =" +msgstr "" + +#: ./doc/common/tables/nova-network.xml75(td) +msgid "(StrOpt) Override the default dnsmasq settings with this file" +msgstr "" + +#: ./doc/common/tables/nova-network.xml78(td) +msgid "firewall_driver = None" +msgstr "" + +#: ./doc/common/tables/nova-network.xml79(td) +msgid "" +"(StrOpt) Firewall driver (defaults to hypervisor specific iptables driver)" +msgstr "" + +#: ./doc/common/tables/nova-network.xml82(td) +msgid "fixed_ip_disassociate_timeout = 600" +msgstr "" + +#: ./doc/common/tables/nova-network.xml83(td) +msgid "(IntOpt) Seconds after which a deallocated ip is disassociated" +msgstr "" + +#: ./doc/common/tables/nova-network.xml86(td) +msgid "flat_injected = False" +msgstr "" + +#: ./doc/common/tables/nova-network.xml87(td) +msgid "(BoolOpt) Whether to attempt to inject network setup into guest" +msgstr "" + +#: ./doc/common/tables/nova-network.xml90(td) +msgid "flat_interface = None" +msgstr "" + +#: ./doc/common/tables/nova-network.xml91(td) +msgid "(StrOpt) FlatDhcp will bridge into this interface if set" +msgstr "" + +#: ./doc/common/tables/nova-network.xml94(td) +msgid "flat_network_bridge = None" +msgstr "" + +#: ./doc/common/tables/nova-network.xml95(td) +msgid "(StrOpt) Bridge for simple network instances" +msgstr "" + +#: ./doc/common/tables/nova-network.xml98(td) +msgid "flat_network_dns = 8.8.4.4" +msgstr "" + +#: ./doc/common/tables/nova-network.xml99(td) +msgid "(StrOpt) Dns for simple network" +msgstr "" + +#: ./doc/common/tables/nova-network.xml102(td) +msgid "floating_ip_dns_manager = nova.network.noop_dns_driver.NoopDNSDriver" +msgstr "" + +#: ./doc/common/tables/nova-network.xml103(td) +msgid "(StrOpt) full class name for the DNS Manager for floating IPs" +msgstr "" + +#: ./doc/common/tables/nova-network.xml106(td) +msgid "force_dhcp_release = True" +msgstr "" + +#: ./doc/common/tables/nova-network.xml107(td) +msgid "(BoolOpt) If True, send a dhcp release on instance termination" +msgstr "" + +#: ./doc/common/tables/nova-network.xml110(td) +msgid "force_snat_range = []" +msgstr "" + +#: ./doc/common/tables/nova-network.xml111(td) +msgid "" +"(MultiStrOpt) Traffic to this range will always be snatted to the fallback " +"ip, even if it would normally be bridged out of the node. Can be specified " +"multiple times." +msgstr "" + +#: ./doc/common/tables/nova-network.xml114(td) +msgid "forward_bridge_interface = ['all']" +msgstr "" + +#: ./doc/common/tables/nova-network.xml115(td) +msgid "" +"(MultiStrOpt) An interface that bridges can forward to. If this is set to " +"all then all traffic will be forwarded. Can be specified multiple times." +msgstr "" + +#: ./doc/common/tables/nova-network.xml118(td) +msgid "gateway = None" +msgstr "" + +#: ./doc/common/tables/nova-network.xml119(td) +msgid "(StrOpt) Default IPv4 gateway" +msgstr "" + +#: ./doc/common/tables/nova-network.xml122(td) +msgid "injected_network_template = $pybasedir/nova/virt/interfaces.template" +msgstr "" + +#: ./doc/common/tables/nova-network.xml123(td) +msgid "(StrOpt) Template file for injected network" +msgstr "" + +#: ./doc/common/tables/nova-network.xml126(td) +msgid "instance_dns_domain =" +msgstr "" + +#: ./doc/common/tables/nova-network.xml127(td) +msgid "(StrOpt) full class name for the DNS Zone for instance IPs" +msgstr "" + +#: ./doc/common/tables/nova-network.xml130(td) +msgid "instance_dns_manager = nova.network.noop_dns_driver.NoopDNSDriver" +msgstr "" + +#: ./doc/common/tables/nova-network.xml131(td) +msgid "(StrOpt) full class name for the DNS Manager for instance IPs" +msgstr "" + +#: ./doc/common/tables/nova-network.xml134(td) +msgid "iptables_bottom_regex =" +msgstr "" + +#: ./doc/common/tables/nova-network.xml135(td) +msgid "" +"(StrOpt) Regular expression to match iptables rule that should always be on " +"the bottom." +msgstr "" + +#: ./doc/common/tables/nova-network.xml138(td) +msgid "iptables_drop_action = DROP" +msgstr "" + +#: ./doc/common/tables/nova-network.xml139(td) +msgid "" +"(StrOpt) The table that iptables to jump to when a packet is to be dropped." +msgstr "" + +#: ./doc/common/tables/nova-network.xml142(td) +msgid "iptables_top_regex =" +msgstr "" + +#: ./doc/common/tables/nova-network.xml143(td) +msgid "" +"(StrOpt) Regular expression to match iptables rule that should always be on " +"the top." +msgstr "" + +#: ./doc/common/tables/nova-network.xml146(td) +msgid "l3_lib = nova.network.l3.LinuxNetL3" +msgstr "" + +#: ./doc/common/tables/nova-network.xml147(td) +msgid "(StrOpt) Indicates underlying L3 management library" +msgstr "" + +#: ./doc/common/tables/nova-network.xml150(td) +msgid "" +"linuxnet_interface_driver = " +"nova.network.linux_net.LinuxBridgeInterfaceDriver" +msgstr "" + +#: ./doc/common/tables/nova-network.xml151(td) +msgid "(StrOpt) Driver used to create ethernet devices." +msgstr "" + +#: ./doc/common/tables/nova-network.xml154(td) +msgid "linuxnet_ovs_integration_bridge = br-int" +msgstr "" + +#: ./doc/common/tables/nova-network.xml155(td) +msgid "(StrOpt) Name of Open vSwitch bridge used with linuxnet" +msgstr "" + +#: ./doc/common/tables/nova-network.xml158(td) +msgid "multi_host = False" +msgstr "" + +#: ./doc/common/tables/nova-network.xml159(td) +msgid "" +"(BoolOpt) Default value for multi_host in networks. Also, if set, some rpc " +"network calls will be sent directly to host." +msgstr "" + +#: ./doc/common/tables/nova-network.xml162(td) +msgid "network_allocate_retries = 0" +msgstr "" + +#: ./doc/common/tables/nova-network.xml163(td) +msgid "(IntOpt) Number of times to retry network allocation on failures" +msgstr "" + +#: ./doc/common/tables/nova-network.xml166(td) +msgid "network_api_class = nova.network.api.API" +msgstr "" + +#: ./doc/common/tables/nova-network.xml167(td) +msgid "(StrOpt) The full class name of the network API class to use" +msgstr "" + +#: ./doc/common/tables/nova-network.xml171(td) +msgid "(IntOpt) MTU setting for network interface" +msgstr "" + +#: ./doc/common/tables/nova-network.xml174(td) +msgid "network_driver = nova.network.linux_net" +msgstr "" + +#: ./doc/common/tables/nova-network.xml175(td) +msgid "(StrOpt) Driver to use for network creation" +msgstr "" + +#: ./doc/common/tables/nova-network.xml178(td) +msgid "network_manager = nova.network.manager.VlanManager" +msgstr "" + +#: ./doc/common/tables/nova-network.xml179(td) +msgid "(StrOpt) full class name for the Manager for network" +msgstr "" + +#: ./doc/common/tables/nova-network.xml182(td) +msgid "network_size = 256" +msgstr "" + +#: ./doc/common/tables/nova-network.xml183(td) +msgid "(IntOpt) Number of addresses in each private subnet" +msgstr "" + +#: ./doc/common/tables/nova-network.xml186(td) +msgid "network_topic = network" +msgstr "" + +#: ./doc/common/tables/nova-network.xml187(td) +msgid "(StrOpt) the topic network nodes listen on" +msgstr "" + +#: ./doc/common/tables/nova-network.xml190(td) +msgid "networks_path = $state_path/networks" +msgstr "" + +#: ./doc/common/tables/nova-network.xml191(td) +msgid "(StrOpt) Location to keep network config files" +msgstr "" + +#: ./doc/common/tables/nova-network.xml194(td) +msgid "num_networks = 1" +msgstr "" + +#: ./doc/common/tables/nova-network.xml195(td) +msgid "(IntOpt) Number of networks to support" +msgstr "" + +#: ./doc/common/tables/nova-network.xml198(td) +msgid "ovs_vsctl_timeout = 120" +msgstr "" + +#: ./doc/common/tables/nova-network.xml199(td) +msgid "" +"(IntOpt) Amount of time, in seconds, that ovs_vsctl should wait for a " +"response from the database. 0 is to wait forever." +msgstr "" + +#: ./doc/common/tables/nova-network.xml202(td) +msgid "public_interface = eth0" +msgstr "" + +#: ./doc/common/tables/nova-network.xml203(td) +msgid "(StrOpt) Interface for public IP addresses" +msgstr "" + +#: ./doc/common/tables/nova-network.xml206(td) +msgid "routing_source_ip = $my_ip" +msgstr "" + +#: ./doc/common/tables/nova-network.xml207(td) +msgid "(StrOpt) Public IP of network host" +msgstr "" + +#: ./doc/common/tables/nova-network.xml210(td) +msgid "security_group_api = nova" +msgstr "" + +#: ./doc/common/tables/nova-network.xml211(td) +msgid "(StrOpt) The full class name of the security API class" +msgstr "" + +#: ./doc/common/tables/nova-network.xml214(td) +msgid "send_arp_for_ha = False" +msgstr "" + +#: ./doc/common/tables/nova-network.xml215(td) +msgid "(BoolOpt) send gratuitous ARPs for HA setup" +msgstr "" + +#: ./doc/common/tables/nova-network.xml218(td) +msgid "send_arp_for_ha_count = 3" +msgstr "" + +#: ./doc/common/tables/nova-network.xml219(td) +msgid "(IntOpt) send this many gratuitous ARPs for HA setup" +msgstr "" + +#: ./doc/common/tables/nova-network.xml222(td) +msgid "share_dhcp_address = False" +msgstr "" + +#: ./doc/common/tables/nova-network.xml223(td) +msgid "" +"(BoolOpt) If True in multi_host mode, all compute hosts share the same dhcp " +"address. The same IP address used for DHCP will be added on each nova-" +"network node which is only visible to the vms on the same host." +msgstr "" + +#: ./doc/common/tables/nova-network.xml226(td) +msgid "teardown_unused_network_gateway = False" +msgstr "" + +#: ./doc/common/tables/nova-network.xml227(td) +msgid "" +"(BoolOpt) If True, unused gateway devices (VLAN and bridge) are deleted in " +"VLAN network mode with multi hosted networks" +msgstr "" + +#: ./doc/common/tables/nova-network.xml230(td) +msgid "update_dns_entries = False" +msgstr "" + +#: ./doc/common/tables/nova-network.xml231(td) +msgid "" +"(BoolOpt) If True, when a DNS entry must be updated, it sends a fanout cast " +"to all network hosts to update their DNS entries in multi host mode" +msgstr "" + +#: ./doc/common/tables/nova-network.xml234(td) +msgid "use_network_dns_servers = False" +msgstr "" + +#: ./doc/common/tables/nova-network.xml235(td) +msgid "" +"(BoolOpt) if set, uses the dns1 and dns2 from the network ref.as dns " +"servers." +msgstr "" + +#: ./doc/common/tables/nova-network.xml238(td) +msgid "use_neutron_default_nets = False" +msgstr "" + +#: ./doc/common/tables/nova-network.xml239(td) +msgid "(StrOpt) Control for checking for default networks" +msgstr "" + +#: ./doc/common/tables/nova-network.xml242(td) +msgid "use_single_default_gateway = False" +msgstr "" + +#: ./doc/common/tables/nova-network.xml243(td) +msgid "" +"(BoolOpt) Use single default gateway. Only first nic of vm will get default " +"gateway from dhcp server" +msgstr "" + +#: ./doc/common/tables/nova-network.xml246(td) +msgid "vlan_interface = None" +msgstr "" + +#: ./doc/common/tables/nova-network.xml247(td) +msgid "(StrOpt) vlans will bridge into this interface if set" +msgstr "" + +#: ./doc/common/tables/nova-network.xml250(td) +msgid "vlan_start = 100" +msgstr "" + +#: ./doc/common/tables/nova-network.xml251(td) +msgid "(IntOpt) First VLAN for private networks" +msgstr "" + +#: ./doc/common/tables/nova-network.xml257(td) +msgid "vlan_interface = vmnic0" +msgstr "" + +#: ./doc/common/tables/nova-network.xml258(td) +msgid "(StrOpt) Physical ethernet adapter name for vlan networking" +msgstr "" + +#: ./doc/common/tables/cinder-scality.xml8(caption) +msgid "Description of configuration options for scality" +msgstr "" + +#: ./doc/common/tables/cinder-scality.xml30(td) +msgid "scality_sofs_volume_dir = cinder/volumes" +msgstr "" + +#: ./doc/common/tables/cinder-scality.xml31(td) +msgid "(StrOpt) Path from Scality SOFS root to volume dir" +msgstr "" + +#: ./doc/common/tables/neutron-notifier.xml8(caption) +msgid "Description of configuration options for notifier" +msgstr "" + +#: ./doc/common/tables/neutron-notifier.xml19(td) +#: ./doc/common/tables/cinder-common.xml38(td) +#: ./doc/common/tables/nova-compute.xml54(td) +msgid "default_notification_level = INFO" +msgstr "" + +#: ./doc/common/tables/neutron-notifier.xml20(td) +#: ./doc/common/tables/cinder-common.xml39(td) +#: ./doc/common/tables/nova-compute.xml55(td) +msgid "(StrOpt) Default notification level for outgoing notifications" +msgstr "" + +#: ./doc/common/tables/neutron-notifier.xml23(td) +msgid "default_publisher_id = $host" +msgstr "" + +#: ./doc/common/tables/neutron-notifier.xml24(td) +#: ./doc/common/tables/cinder-common.xml43(td) +#: ./doc/common/tables/glance-api.xml31(td) +#: ./doc/common/tables/nova-compute.xml59(td) +msgid "(StrOpt) Default publisher_id for outgoing notifications" +msgstr "" + +#: ./doc/common/tables/neutron-notifier.xml32(td) +msgid "(ListOpt) AMQP topic used for openstack notifications" +msgstr "" + +#: ./doc/common/tables/cinder-common.xml22(td) +msgid "compute_api_class = cinder.compute.nova.API" +msgstr "" + +#: ./doc/common/tables/cinder-common.xml23(td) +msgid "(StrOpt) The full class name of the compute API class to use" +msgstr "" + +#: ./doc/common/tables/cinder-common.xml30(td) +msgid "default_availability_zone = None" +msgstr "" + +#: ./doc/common/tables/cinder-common.xml31(td) +msgid "" +"(StrOpt) default availability zone to use when creating a new volume. If " +"this is not set then we use the value from the storage_availability_zone " +"option as the default availability_zone for new volumes." +msgstr "" + +#: ./doc/common/tables/cinder-common.xml42(td) +#: ./doc/common/tables/nova-compute.xml58(td) +msgid "default_publisher_id = None" +msgstr "" + +#: ./doc/common/tables/cinder-common.xml46(td) +msgid "default_volume_type = None" +msgstr "" + +#: ./doc/common/tables/cinder-common.xml47(td) +msgid "(StrOpt) default volume type to use" +msgstr "" + +#: ./doc/common/tables/cinder-common.xml54(td) +#: ./doc/common/tables/nova-api.xml22(td) +msgid "enable_new_services = True" +msgstr "" + +#: ./doc/common/tables/cinder-common.xml55(td) +#: ./doc/common/tables/nova-api.xml23(td) +msgid "(BoolOpt) Services to be added to the available pool on create" +msgstr "" + +#: ./doc/common/tables/cinder-common.xml67(td) +msgid "" +"(StrOpt) Name of this node. This can be an opaque identifier. It is not " +"necessarily a hostname, FQDN, or IP address." +msgstr "" + +#: ./doc/common/tables/cinder-common.xml70(td) +msgid "iet_conf = /etc/iet/ietd.conf" +msgstr "" + +#: ./doc/common/tables/cinder-common.xml71(td) +msgid "(StrOpt) IET configuration file" +msgstr "" + +#: ./doc/common/tables/cinder-common.xml74(td) +msgid "lio_initiator_iqns =" +msgstr "" + +#: ./doc/common/tables/cinder-common.xml75(td) +msgid "" +"(StrOpt) Comma-separated list of initiator IQNs allowed to connect to the " +"iSCSI target. (From Nova compute nodes.)" +msgstr "" + +#: ./doc/common/tables/cinder-common.xml119(td) +msgid "(BoolOpt) Enable monkey patching" +msgstr "" + +#: ./doc/common/tables/cinder-common.xml122(td) +msgid "monkey_patch_modules =" +msgstr "" + +#: ./doc/common/tables/cinder-common.xml130(td) +msgid "no_snapshot_gb_quota = False" +msgstr "" + +#: ./doc/common/tables/cinder-common.xml131(td) +msgid "(BoolOpt) Whether snapshots count against GigaByte quota" +msgstr "" + +#: ./doc/common/tables/cinder-common.xml134(td) +msgid "num_shell_tries = 3" +msgstr "" + +#: ./doc/common/tables/cinder-common.xml135(td) +msgid "(IntOpt) number of times to attempt to run flakey shell commands" +msgstr "" + +#: ./doc/common/tables/cinder-common.xml142(td) +msgid "periodic_interval = 60" +msgstr "" + +#: ./doc/common/tables/cinder-common.xml143(td) +msgid "(IntOpt) seconds between running periodic tasks" +msgstr "" + +#: ./doc/common/tables/cinder-common.xml155(td) +msgid "(StrOpt) Directory where the cinder python module is installed" +msgstr "" + +#: ./doc/common/tables/cinder-common.xml162(td) +msgid "reserved_percentage = 0" +msgstr "" + +#: ./doc/common/tables/cinder-common.xml163(td) +msgid "(IntOpt) The percentage of backend capacity is reserved" +msgstr "" + +#: ./doc/common/tables/cinder-common.xml167(td) +msgid "(StrOpt) Deprecated: command to use for running commands as root" +msgstr "" + +#: ./doc/common/tables/cinder-common.xml170(td) +msgid "rootwrap_config = /etc/cinder/rootwrap.conf" +msgstr "" + +#: ./doc/common/tables/cinder-common.xml182(td) +msgid "sqlite_db = cinder.sqlite" +msgstr "" + +#: ./doc/common/tables/cinder-common.xml203(td) +msgid "(StrOpt) Top-level directory for maintaining cinder's state" +msgstr "" + +#: ./doc/common/tables/cinder-common.xml206(td) +msgid "storage_availability_zone = nova" +msgstr "" + +#: ./doc/common/tables/cinder-common.xml207(td) +msgid "(StrOpt) availability zone of this node" +msgstr "" + +#: ./doc/common/tables/cinder-common.xml226(td) +#: ./doc/common/tables/nova-api.xml86(td) +msgid "use_forwarded_for = False" +msgstr "" + +#: ./doc/common/tables/cinder-common.xml227(td) +#: ./doc/common/tables/nova-api.xml87(td) +msgid "" +"(BoolOpt) Treat X-Forwarded-For as the canonical remote address. Only enable" +" this if you have a sanitizing proxy." +msgstr "" + +#: ./doc/common/tables/cinder-common.xml253(th) +#: ./doc/common/tables/nova-redis.xml19(th) +msgid "[matchmaker_redis]" +msgstr "" + +#: ./doc/common/tables/cinder-common.xml256(td) +#: ./doc/common/tables/neutron-rpc.xml31(td) +#: ./doc/common/tables/neutron-nec.xml39(td) +#: ./doc/common/tables/nova-redis.xml22(td) +msgid "host = 127.0.0.1" +msgstr "" + +#: ./doc/common/tables/cinder-common.xml257(td) +#: ./doc/common/tables/neutron-rpc.xml32(td) +#: ./doc/common/tables/nova-redis.xml23(td) +msgid "(StrOpt) Host to locate redis" +msgstr "" + +#: ./doc/common/tables/cinder-common.xml260(td) +#: ./doc/common/tables/neutron-rpc.xml43(td) +#: ./doc/common/tables/ldap-keystone-conf.xml25(td) +#: ./doc/common/tables/nova-redis.xml26(td) +msgid "password = None" +msgstr "" + +#: ./doc/common/tables/cinder-common.xml261(td) +#: ./doc/common/tables/nova-redis.xml27(td) +msgid "(StrOpt) Password for Redis server. (optional)" +msgstr "" + +#: ./doc/common/tables/cinder-common.xml264(td) +#: ./doc/common/tables/neutron-rpc.xml47(td) +#: ./doc/common/tables/nova-redis.xml30(td) +msgid "port = 6379" +msgstr "" + +#: ./doc/common/tables/cinder-common.xml265(td) +#: ./doc/common/tables/neutron-rpc.xml48(td) +#: ./doc/common/tables/nova-redis.xml31(td) +msgid "(IntOpt) Use this port to connect to redis host." +msgstr "" + +#: ./doc/common/tables/cinder-common.xml268(th) +#: ./doc/common/tables/nova-rpc.xml76(th) +msgid "[rpc_notifier2]" +msgstr "" + +#: ./doc/common/tables/cinder-common.xml271(td) +#: ./doc/common/tables/neutron-rpc.xml79(td) +#: ./doc/common/tables/nova-rpc.xml79(td) +msgid "topics = notifications" +msgstr "" + +#: ./doc/common/tables/cinder-common.xml272(td) +#: ./doc/common/tables/nova-rpc.xml80(td) +msgid "(ListOpt) AMQP topic(s) used for OpenStack notifications" +msgstr "" + +#: ./doc/common/tables/nova-trustedcomputing.xml8(caption) +msgid "Description of configuration options for trustedcomputing" +msgstr "" + +#: ./doc/common/tables/nova-trustedcomputing.xml19(th) +msgid "[trusted_computing]" +msgstr "" + +#: ./doc/common/tables/nova-trustedcomputing.xml22(td) +msgid "attestation_api_url = /OpenAttestationWebServices/V1.0" +msgstr "" + +#: ./doc/common/tables/nova-trustedcomputing.xml23(td) +msgid "(StrOpt) attestation web API URL" +msgstr "" + +#: ./doc/common/tables/nova-trustedcomputing.xml26(td) +msgid "attestation_auth_blob = None" +msgstr "" + +#: ./doc/common/tables/nova-trustedcomputing.xml27(td) +msgid "(StrOpt) attestation authorization blob - must change" +msgstr "" + +#: ./doc/common/tables/nova-trustedcomputing.xml30(td) +msgid "attestation_auth_timeout = 60" +msgstr "" + +#: ./doc/common/tables/nova-trustedcomputing.xml31(td) +msgid "(IntOpt) Attestation status cache valid period length" +msgstr "" + +#: ./doc/common/tables/nova-trustedcomputing.xml34(td) +msgid "attestation_port = 8443" +msgstr "" + +#: ./doc/common/tables/nova-trustedcomputing.xml35(td) +msgid "(StrOpt) attestation server port" +msgstr "" + +#: ./doc/common/tables/nova-trustedcomputing.xml38(td) +msgid "attestation_server = None" +msgstr "" + +#: ./doc/common/tables/nova-trustedcomputing.xml39(td) +msgid "(StrOpt) attestation server http" +msgstr "" + +#: ./doc/common/tables/nova-trustedcomputing.xml42(td) +msgid "attestation_server_ca_file = None" +msgstr "" + +#: ./doc/common/tables/nova-trustedcomputing.xml43(td) +msgid "(StrOpt) attestation server Cert file for Identity verification" +msgstr "" + +#: ./doc/common/tables/neutron-ml2_flat.xml8(caption) +msgid "Description of configuration options for ml2_flat" +msgstr "" + +#: ./doc/common/tables/neutron-ml2_flat.xml19(td) +msgid "flat_networks =" +msgstr "" + +#: ./doc/common/tables/neutron-ml2_flat.xml20(td) +msgid "" +"(ListOpt) List of physical_network names with which flat networks can be " +"created. Use * to allow flat networks with arbitrary physical_network names." +msgstr "" + +#: ./doc/common/tables/nova-configdrive.xml8(caption) +msgid "Description of configuration options for configdrive" +msgstr "" + +#: ./doc/common/tables/nova-configdrive.xml22(td) +msgid "config_drive_format = iso9660" +msgstr "" + +#: ./doc/common/tables/nova-configdrive.xml23(td) +msgid "(StrOpt) Config drive format. One of iso9660 (default) or vfat" +msgstr "" + +#: ./doc/common/tables/nova-configdrive.xml26(td) +msgid "" +"config_drive_skip_versions = 1.0 2007-01-19 2007-03-01 2007-08-29 2007-10-10" +" 2007-12-15 2008-02-01 2008-09-01" +msgstr "" + +#: ./doc/common/tables/nova-configdrive.xml27(td) +msgid "" +"(StrOpt) List of metadata versions to skip placing into the config drive" +msgstr "" + +#: ./doc/common/tables/nova-configdrive.xml30(td) +msgid "config_drive_tempdir = None" +msgstr "" + +#: ./doc/common/tables/nova-configdrive.xml31(td) +msgid "" +"(StrOpt) Where to put temporary files associated with config drive creation" +msgstr "" + +#: ./doc/common/tables/nova-configdrive.xml34(td) +msgid "force_config_drive = None" +msgstr "" + +#: ./doc/common/tables/nova-configdrive.xml35(td) +msgid "" +"(StrOpt) Set to force injection to take place on a config drive (if set, " +"valid options are: always)" +msgstr "" + +#: ./doc/common/tables/nova-configdrive.xml38(td) +msgid "mkisofs_cmd = genisoimage" +msgstr "" + +#: ./doc/common/tables/nova-configdrive.xml45(td) +msgid "config_drive_cdrom = False" +msgstr "" + +#: ./doc/common/tables/nova-configdrive.xml46(td) +msgid "" +"(BoolOpt) Attaches the Config Drive image as a cdrom drive instead of a disk" +" drive" +msgstr "" + +#: ./doc/common/tables/nova-configdrive.xml49(td) +msgid "config_drive_inject_password = False" +msgstr "" + +#: ./doc/common/tables/nova-configdrive.xml50(td) +msgid "(BoolOpt) Sets the admin password in the config drive image" +msgstr "" + +#: ./doc/common/tables/cinder-database.xml8(caption) +msgid "Description of configuration options for database" +msgstr "" + +#: ./doc/common/tables/cinder-database.xml22(td) +#: ./doc/common/tables/nova-baremetal.xml22(td) +msgid "db_backend = sqlalchemy" +msgstr "" + +#: ./doc/common/tables/cinder-database.xml26(td) +msgid "db_driver = cinder.db" +msgstr "" + +#: ./doc/common/tables/neutron-rpc.xml27(td) +msgid "control_exchange = neutron" +msgstr "" + +#: ./doc/common/tables/neutron-rpc.xml44(td) +msgid "(StrOpt) HTTP password for authentication" +msgstr "" + +#: ./doc/common/tables/neutron-rpc.xml55(td) +msgid "rpc_backend = neutron.openstack.common.rpc.impl_kombu" +msgstr "" + +#: ./doc/common/tables/neutron-rpc.xml71(td) +msgid "rpc_support_old_agents = False" +msgstr "" + +#: ./doc/common/tables/neutron-rpc.xml72(td) +msgid "(BoolOpt) Enable server RPC compatibility with old agents" +msgstr "" + +#: ./doc/common/tables/neutron-rpc.xml80(td) +msgid "(ListOpt) AMQP topic(s) used for openstack notifications" +msgstr "" + +#: ./doc/common/tables/nova-zeromq.xml8(caption) +#: ./doc/common/tables/neutron-zeromq.xml8(caption) +msgid "Description of configuration options for zeromq" +msgstr "" + +#: ./doc/common/tables/nova-zeromq.xml38(td) +msgid "" +"rpc_zmq_matchmaker = " +"nova.openstack.common.rpc.matchmaker.MatchMakerLocalhost" +msgstr "" + +#: ./doc/common/tables/glance-testing.xml22(td) +msgid "pydev_worker_debug_host = None" +msgstr "" + +#: ./doc/common/tables/glance-testing.xml23(td) +msgid "" +"(StrOpt) The hostname/IP of the pydev process listening for debug " +"connections" +msgstr "" + +#: ./doc/common/tables/glance-testing.xml26(td) +msgid "pydev_worker_debug_port = 5678" +msgstr "" + +#: ./doc/common/tables/glance-testing.xml27(td) +msgid "" +"(IntOpt) The port on which a pydev process is listening for connections." +msgstr "" + +#: ./doc/common/tables/swift-proxy-server-filter-tempauth.xml7(literal) +msgid "[filter:tempauth]" +msgstr "" + +#: ./doc/common/tables/swift-proxy-server-filter-tempauth.xml18(td) +msgid "use = egg:swift#tempauth" +msgstr "" + +#: ./doc/common/tables/swift-proxy-server-filter-tempauth.xml21(td) +msgid "set log_name = tempauth" +msgstr "" + +#: ./doc/common/tables/swift-proxy-server-filter-tempauth.xml36(td) +msgid "reseller_prefix = AUTH" +msgstr "" + +#: ./doc/common/tables/swift-proxy-server-filter-tempauth.xml36(td) +msgid "The naming scope for the auth service. Swift" +msgstr "" + +#: ./doc/common/tables/swift-proxy-server-filter-tempauth.xml39(td) +msgid "auth_prefix = /auth/" +msgstr "" + +#: ./doc/common/tables/swift-proxy-server-filter-tempauth.xml39(td) +msgid "" +"The HTTP request path prefix for the auth service. Swift itself reserves " +"anything beginning with the letter `v`." +msgstr "" + +#: ./doc/common/tables/swift-proxy-server-filter-tempauth.xml42(td) +msgid "token_life = 86400" +msgstr "" + +#: ./doc/common/tables/swift-proxy-server-filter-tempauth.xml42(td) +msgid "The number of seconds a token is valid." +msgstr "" + +#: ./doc/common/tables/swift-proxy-server-filter-tempauth.xml45(td) +msgid "allow_overrides = true" +msgstr "" + +#: ./doc/common/tables/swift-proxy-server-filter-tempauth.xml48(td) +msgid "storage_url_scheme = default" +msgstr "" + +#: ./doc/common/tables/swift-proxy-server-filter-tempauth.xml48(td) +msgid "" +"Scheme to return with storage urls: http, https, or default (chooses based " +"on what the server is running as) This can be useful with an SSL load " +"balancer in front of a non-SSL server." +msgstr "" + +#: ./doc/common/tables/swift-proxy-server-filter-tempauth.xml51(td) +msgid "user_admin_admin = admin .admin .reseller_admin" +msgstr "" + +#: ./doc/common/tables/swift-proxy-server-filter-tempauth.xml54(td) +msgid "user_test_tester = testing .admin" +msgstr "" + +#: ./doc/common/tables/swift-proxy-server-filter-tempauth.xml57(td) +msgid "user_test2_tester2 = testing2 .admin" +msgstr "" + +#: ./doc/common/tables/swift-proxy-server-filter-tempauth.xml60(td) +msgid "user_test_tester3 = testing3" +msgstr "" + +#: ./doc/common/tables/glance-registry.xml8(caption) +msgid "Description of configuration options for registry" +msgstr "" + +#: ./doc/common/tables/glance-registry.xml23(td) +msgid "(StrOpt) The administrators password." +msgstr "" + +#: ./doc/common/tables/glance-registry.xml27(td) +msgid "(StrOpt) The tenant name of the administrative user." +msgstr "" + +#: ./doc/common/tables/glance-registry.xml31(td) +msgid "(StrOpt) The administrators user name." +msgstr "" + +#: ./doc/common/tables/glance-registry.xml35(td) +msgid "(StrOpt) The region for the authentication service." +msgstr "" + +#: ./doc/common/tables/glance-registry.xml39(td) +msgid "(StrOpt) The strategy to use for authentication." +msgstr "" + +#: ./doc/common/tables/glance-registry.xml43(td) +msgid "(StrOpt) The URL to the keystone service." +msgstr "" + +#: ./doc/common/tables/glance-registry.xml46(td) +msgid "registry_client_ca_file = None" +msgstr "" + +#: ./doc/common/tables/glance-registry.xml47(td) +msgid "" +"(StrOpt) The path to the certifying authority cert file to use in SSL " +"connections to the registry server." +msgstr "" + +#: ./doc/common/tables/glance-registry.xml50(td) +msgid "registry_client_cert_file = None" +msgstr "" + +#: ./doc/common/tables/glance-registry.xml51(td) +msgid "" +"(StrOpt) The path to the cert file to use in SSL connections to the registry" +" server." +msgstr "" + +#: ./doc/common/tables/glance-registry.xml54(td) +msgid "registry_client_insecure = False" +msgstr "" + +#: ./doc/common/tables/glance-registry.xml55(td) +msgid "" +"(BoolOpt) When using SSL in connections to the registry server, do not " +"require validation via a certifying authority." +msgstr "" + +#: ./doc/common/tables/glance-registry.xml58(td) +msgid "registry_client_key_file = None" +msgstr "" + +#: ./doc/common/tables/glance-registry.xml59(td) +msgid "" +"(StrOpt) The path to the key file to use in SSL connections to the registry " +"server." +msgstr "" + +#: ./doc/common/tables/glance-registry.xml62(td) +msgid "registry_client_protocol = http" +msgstr "" + +#: ./doc/common/tables/glance-registry.xml63(td) +msgid "" +"(StrOpt) The protocol to use for communication with the registry server. " +"Either http or https." +msgstr "" + +#: ./doc/common/tables/glance-registry.xml66(td) +msgid "registry_client_timeout = 600" +msgstr "" + +#: ./doc/common/tables/glance-registry.xml67(td) +msgid "" +"(IntOpt) The period of time, in seconds, that the API server will wait for a" +" registry request to complete. A value of 0 implies no timeout." +msgstr "" + +#: ./doc/common/tables/glance-registry.xml70(td) +msgid "registry_host = 0.0.0.0" +msgstr "" + +#: ./doc/common/tables/glance-registry.xml71(td) +msgid "(StrOpt) Address to find the registry server." +msgstr "" + +#: ./doc/common/tables/glance-registry.xml74(td) +msgid "registry_port = 9191" +msgstr "" + +#: ./doc/common/tables/glance-registry.xml75(td) +msgid "(IntOpt) Port the registry server is listening on." +msgstr "" + +#: ./doc/common/tables/ldap-keystone-conf.xml4(caption) +msgid "Description of keystone.conf file configuration options for LDAP" +msgstr "" + +#: ./doc/common/tables/ldap-keystone-conf.xml11(th) +msgid "(Type) Description" +msgstr "" + +#: ./doc/common/tables/ldap-keystone-conf.xml16(td) +msgid "url = ldap://localhost" +msgstr "" + +#: ./doc/common/tables/ldap-keystone-conf.xml17(td) +msgid "The location for the ldap server." +msgstr "" + +#: ./doc/common/tables/ldap-keystone-conf.xml20(td) +msgid "user = dc=Manager,dc=example,dc=com" +msgstr "" + +#: ./doc/common/tables/ldap-keystone-conf.xml22(td) +msgid "(StrOpt) User for the LDAP server to use as default." +msgstr "" + +#: ./doc/common/tables/ldap-keystone-conf.xml26(td) +msgid "(StrOpt) Password for LDAP server to connect to." +msgstr "" + +#: ./doc/common/tables/ldap-keystone-conf.xml29(td) +msgid "suffix = cn=example,cn=com" +msgstr "" + +#: ./doc/common/tables/ldap-keystone-conf.xml31(td) +msgid "(StrOpt) Default suffix for your LDAP server." +msgstr "" + +#: ./doc/common/tables/ldap-keystone-conf.xml33(td) +msgid "use_dumb_member = False" +msgstr "" + +#: ./doc/common/tables/ldap-keystone-conf.xml34(td) +msgid "(Bool) Indicates whether dumb_member settings are in use." +msgstr "" + +#: ./doc/common/tables/ldap-keystone-conf.xml36(td) +msgid "allow_subtree_delete = False" +msgstr "" + +#: ./doc/common/tables/ldap-keystone-conf.xml38(td) +msgid "(Bool) Determine whether to delete LDAP subtrees." +msgstr "" + +#: ./doc/common/tables/ldap-keystone-conf.xml41(td) +msgid "dumb_member = cn=dumb,dc=example,dc=com" +msgstr "" + +#: ./doc/common/tables/ldap-keystone-conf.xml43(td) +msgid "Mockup member as placeholder, for testing purposes." +msgstr "" + +#: ./doc/common/tables/ldap-keystone-conf.xml45(td) +msgid "query_scope = one" +msgstr "" + +#: ./doc/common/tables/ldap-keystone-conf.xml47(td) +msgid "" +"The LDAP scope for queries, this can be either 'one' (onelevel/singleLevel) " +"or 'sub' (subtree/wholeSubtree)" +msgstr "" + +#: ./doc/common/tables/ldap-keystone-conf.xml49(td) +msgid "user_tree_dn = ou=Users,dc=example,dc=com" +msgstr "" + +#: ./doc/common/tables/ldap-keystone-conf.xml53(td) +msgid "user_filter =" +msgstr "" + +#: ./doc/common/tables/ldap-keystone-conf.xml57(td) +msgid "user_objectclass = inetOrgPerson" +msgstr "" + +#: ./doc/common/tables/ldap-keystone-conf.xml61(td) +msgid "user_id_attribute = cn" +msgstr "" + +#: ./doc/common/tables/ldap-keystone-conf.xml65(td) +msgid "user_name_attribute = sn" +msgstr "" + +#: ./doc/common/tables/ldap-keystone-conf.xml69(td) +msgid "user_mail_attribute = email" +msgstr "" + +#: ./doc/common/tables/ldap-keystone-conf.xml73(td) +msgid "user_pass_attribute = userPassword" +msgstr "" + +#: ./doc/common/tables/ldap-keystone-conf.xml77(td) +msgid "user_enabled_attribute = enabled" +msgstr "" + +#: ./doc/common/tables/ldap-keystone-conf.xml79(td) +msgid "" +"Example, userAccountControl. Combines with user_enabled_mask and " +"user_enabled_default settings below to extract the value from an integer " +"attribute like in Active Directory." +msgstr "" + +#: ./doc/common/tables/ldap-keystone-conf.xml82(td) +msgid "user_enabled_mask = 0" +msgstr "" + +#: ./doc/common/tables/ldap-keystone-conf.xml86(td) +msgid "user_enabled_default = True" +msgstr "" + +#: ./doc/common/tables/ldap-keystone-conf.xml90(td) +msgid "user_attribute_ignore = tenant_id,tenants" +msgstr "" + +#: ./doc/common/tables/ldap-keystone-conf.xml94(td) +msgid "user_allow_create = True" +msgstr "" + +#: ./doc/common/tables/ldap-keystone-conf.xml96(td) +msgid "" +"If the users are managed by another tool and you have only read access, you " +"would set this to False." +msgstr "" + +#: ./doc/common/tables/ldap-keystone-conf.xml98(td) +msgid "user_allow_update = True" +msgstr "" + +#: ./doc/common/tables/ldap-keystone-conf.xml102(td) +msgid "user_allow_delete = True" +msgstr "" + +#: ./doc/common/tables/ldap-keystone-conf.xml107(td) +msgid "tenant_tree_dn = ou=Groups,dc=example,dc=com" +msgstr "" + +#: ./doc/common/tables/ldap-keystone-conf.xml112(td) +msgid "tenant_filter =" +msgstr "" + +#: ./doc/common/tables/ldap-keystone-conf.xml114(td) +msgid "" +"If the backend is providing too much output, you can set a filter to blank " +"so tenants are not passed through." +msgstr "" + +#: ./doc/common/tables/ldap-keystone-conf.xml116(td) +msgid "tenant_objectclass = groupOfNames" +msgstr "" + +#: ./doc/common/tables/ldap-keystone-conf.xml120(td) +msgid "tenant_id_attribute = cn" +msgstr "" + +#: ./doc/common/tables/ldap-keystone-conf.xml124(td) +msgid "tenant_member_attribute = member" +msgstr "" + +#: ./doc/common/tables/ldap-keystone-conf.xml128(td) +msgid "tenant_name_attribute = ou" +msgstr "" + +#: ./doc/common/tables/ldap-keystone-conf.xml132(td) +msgid "tenant_desc_attribute = desc" +msgstr "" + +#: ./doc/common/tables/ldap-keystone-conf.xml136(td) +msgid "tenant_enabled_attribute = enabled" +msgstr "" + +#: ./doc/common/tables/ldap-keystone-conf.xml140(td) +msgid "tenant_attribute_ignore =" +msgstr "" + +#: ./doc/common/tables/ldap-keystone-conf.xml144(td) +msgid "tenant_allow_create = True" +msgstr "" + +#: ./doc/common/tables/ldap-keystone-conf.xml148(td) +msgid "tenant_allow_update = True" +msgstr "" + +#: ./doc/common/tables/ldap-keystone-conf.xml153(td) +msgid "tenant_allow_delete = True" +msgstr "" + +#: ./doc/common/tables/ldap-keystone-conf.xml158(td) +msgid "role_tree_dn = ou=Roles,dc=example,dc=com" +msgstr "" + +#: ./doc/common/tables/ldap-keystone-conf.xml163(td) +msgid "role_filter =" +msgstr "" + +#: ./doc/common/tables/ldap-keystone-conf.xml168(td) +msgid "role_objectclass = organizationalRole" +msgstr "" + +#: ./doc/common/tables/ldap-keystone-conf.xml173(td) +msgid "role_id_attribute = cn" +msgstr "" + +#: ./doc/common/tables/ldap-keystone-conf.xml178(td) +msgid "role_name_attribute = ou" +msgstr "" + +#: ./doc/common/tables/ldap-keystone-conf.xml183(td) +msgid "role_member_attribute = roleOccupant" +msgstr "" + +#: ./doc/common/tables/ldap-keystone-conf.xml188(td) +msgid "role_attribute_ignore =" +msgstr "" + +#: ./doc/common/tables/ldap-keystone-conf.xml193(td) +msgid "role_allow_create = True" +msgstr "" + +#: ./doc/common/tables/ldap-keystone-conf.xml198(td) +msgid "role_allow_update = True" +msgstr "" + +#: ./doc/common/tables/ldap-keystone-conf.xml203(td) +msgid "role_allow_delete = True" +msgstr "" + +#: ./doc/common/tables/ldap-keystone-conf.xml208(td) +msgid "group_tree_dn =" +msgstr "" + +#: ./doc/common/tables/ldap-keystone-conf.xml213(td) +msgid "group_filter =" +msgstr "" + +#: ./doc/common/tables/ldap-keystone-conf.xml218(td) +msgid "group_objectclass = groupOfNames" +msgstr "" + +#: ./doc/common/tables/ldap-keystone-conf.xml223(td) +msgid "group_id_attribute = cn" +msgstr "" + +#: ./doc/common/tables/ldap-keystone-conf.xml228(td) +msgid "group_name_attribute = ou" +msgstr "" + +#: ./doc/common/tables/ldap-keystone-conf.xml233(td) +msgid "group_member_attribute = member" +msgstr "" + +#: ./doc/common/tables/ldap-keystone-conf.xml238(td) +msgid "group_desc_attribute = desc" +msgstr "" + +#: ./doc/common/tables/ldap-keystone-conf.xml243(td) +msgid "group_attribute_ignore =" +msgstr "" + +#: ./doc/common/tables/ldap-keystone-conf.xml248(td) +msgid "group_allow_create = True" +msgstr "" + +#: ./doc/common/tables/ldap-keystone-conf.xml253(td) +msgid "group_allow_update = True" +msgstr "" + +#: ./doc/common/tables/ldap-keystone-conf.xml258(td) +msgid "group_allow_delete = True" +msgstr "" + +#: ./doc/common/tables/swift-object-server-object-replicator.xml7(literal) +msgid "[object-replicator]" +msgstr "" + +#: ./doc/common/tables/swift-object-server-object-replicator.xml18(td) +msgid "log_name = object-replicator" +msgstr "" + +#: ./doc/common/tables/swift-object-server-object-replicator.xml33(td) +msgid "daemonize = on" +msgstr "" + +#: ./doc/common/tables/swift-object-server-object-replicator.xml33(td) +msgid "Whether or not to run replication as a daemon" +msgstr "" + +#: ./doc/common/tables/swift-object-server-object-replicator.xml42(td) +msgid "stats_interval = 300" +msgstr "" + +#: ./doc/common/tables/swift-object-server-object-replicator.xml42(td) +msgid "Interval in seconds between logging replication statistics" +msgstr "" + +#: ./doc/common/tables/swift-object-server-object-replicator.xml45(td) +msgid "rsync_timeout = 900" +msgstr "" + +#: ./doc/common/tables/swift-object-server-object-replicator.xml45(td) +msgid "Max duration (seconds) of a partition rsync" +msgstr "" + +#: ./doc/common/tables/swift-object-server-object-replicator.xml48(td) +msgid "rsync_bwlimit = 0" +msgstr "" + +#: ./doc/common/tables/swift-object-server-object-replicator.xml51(td) +msgid "rsync_io_timeout = 30" +msgstr "" + +#: ./doc/common/tables/swift-object-server-object-replicator.xml51(td) +msgid "Passed to rsync for a max duration (seconds) of an I/O op" +msgstr "" + +#: ./doc/common/tables/swift-object-server-object-replicator.xml54(td) +msgid "http_timeout = 60" +msgstr "" + +#: ./doc/common/tables/swift-object-server-object-replicator.xml54(td) +msgid "Maximum duration for an HTTP request" +msgstr "" + +#: ./doc/common/tables/swift-object-server-object-replicator.xml57(td) +msgid "lockup_timeout = 1800" +msgstr "" + +#: ./doc/common/tables/swift-object-server-object-replicator.xml57(td) +msgid "" +"Attempts to kill all workers if nothing replications for lockup_timeout " +"seconds" +msgstr "" + +#: ./doc/common/tables/swift-object-server-object-replicator.xml63(td) +msgid "ring_check_interval = 15" +msgstr "" + +#: ./doc/common/tables/swift-object-server-object-replicator.xml63(td) +msgid "How often (in seconds) to check the ring" +msgstr "" + +#: ./doc/common/tables/swift-object-server-object-replicator.xml69(td) +msgid "rsync_error_log_line_length = 0" +msgstr "" + +#: ./doc/common/tables/swift-dispersion-dispersion.xml7(literal) +msgid "[dispersion]" +msgstr "" + +#: ./doc/common/tables/swift-dispersion-dispersion.xml7(literal) +msgid "dispersion.conf-sample" +msgstr "" + +#: ./doc/common/tables/swift-dispersion-dispersion.xml18(td) +msgid "auth_url = http://localhost:8080/auth/v1.0" +msgstr "" + +#: ./doc/common/tables/swift-dispersion-dispersion.xml18(td) +#: ./doc/common/tables/swift-dispersion-dispersion.xml27(td) +msgid "Endpoint for auth server, such as keystone" +msgstr "" + +#: ./doc/common/tables/swift-dispersion-dispersion.xml21(td) +#: ./doc/common/tables/swift-dispersion-dispersion.xml30(td) +msgid "auth_user = test:tester" +msgstr "" + +#: ./doc/common/tables/swift-dispersion-dispersion.xml21(td) +#: ./doc/common/tables/swift-dispersion-dispersion.xml30(td) +msgid "Default user for dispersion in this context" +msgstr "" + +#: ./doc/common/tables/swift-dispersion-dispersion.xml24(td) +#: ./doc/common/tables/swift-dispersion-dispersion.xml33(td) +msgid "auth_key = testing" +msgstr "" + +#: ./doc/common/tables/swift-dispersion-dispersion.xml27(td) +msgid "auth_url = http://saio:5000/v2.0/" +msgstr "" + +#: ./doc/common/tables/swift-dispersion-dispersion.xml36(td) +msgid "auth_version = 2.0" +msgstr "" + +#: ./doc/common/tables/swift-dispersion-dispersion.xml39(td) +msgid "endpoint_type = publicURL" +msgstr "" + +#: ./doc/common/tables/swift-dispersion-dispersion.xml39(td) +msgid "Indicates whether endpoint for auth is public or internal" +msgstr "" + +#: ./doc/common/tables/swift-dispersion-dispersion.xml42(td) +msgid "keystone_api_insecure = no" +msgstr "" + +#: ./doc/common/tables/swift-dispersion-dispersion.xml48(td) +msgid "dispersion_coverage = 1.0" +msgstr "" + +#: ./doc/common/tables/swift-dispersion-dispersion.xml51(td) +msgid "retries = 5" +msgstr "" + +#: ./doc/common/tables/swift-dispersion-dispersion.xml54(td) +#: ./doc/common/tables/swift-account-server-account-reaper.xml30(td) +msgid "concurrency = 25" +msgstr "" + +#: ./doc/common/tables/swift-dispersion-dispersion.xml57(td) +msgid "container_report = yes" +msgstr "" + +#: ./doc/common/tables/swift-dispersion-dispersion.xml60(td) +msgid "object_report = yes" +msgstr "" + +#: ./doc/common/tables/swift-dispersion-dispersion.xml63(td) +msgid "dump_json = no" +msgstr "" + +#: ./doc/common/tables/swift-account-server-account-replicator.xml7(literal) +msgid "[account-replicator]" +msgstr "" + +#: ./doc/common/tables/swift-account-server-account-replicator.xml18(td) +msgid "log_name = account-replicator" +msgstr "" + +#: ./doc/common/tables/neutron-fwaas.xml8(caption) +msgid "Description of configuration options for fwaas" +msgstr "" + +#: ./doc/common/tables/neutron-fwaas.xml19(td) +#: ./doc/common/tables/nova-spice.xml26(td) +#: ./doc/common/tables/nova-apiv3.xml22(td) +msgid "enabled = False" +msgstr "" + +#: ./doc/common/tables/neutron-fwaas.xml20(td) +msgid "(BoolOpt) Enable FWaaS" +msgstr "" + +#: ./doc/common/tables/glance-rabbitmq.xml8(caption) +#: ./doc/common/tables/neutron-rabbitmq.xml8(caption) +#: ./doc/common/tables/nova-rabbitmq.xml8(caption) +msgid "Description of configuration options for rabbitmq" +msgstr "" + +#: ./doc/common/tables/glance-rabbitmq.xml39(td) +#: ./doc/common/tables/nova-kombu.xml35(td) +msgid "" +"(StrOpt) SSL version to use (valid only if SSL enabled). valid values are " +"TLSv1, SSLv23 and SSLv3. SSLv2 may be available on some distributions" +msgstr "" + +#: ./doc/common/tables/cinder-backups_tsm.xml8(caption) +msgid "Description of configuration options for backups_tsm" +msgstr "" + +#: ./doc/common/tables/cinder-backups_tsm.xml22(td) +msgid "backup_tsm_compression = True" +msgstr "" + +#: ./doc/common/tables/cinder-backups_tsm.xml23(td) +msgid "(BoolOpt) Enable or Disable compression for backups" +msgstr "" + +#: ./doc/common/tables/cinder-backups_tsm.xml26(td) +msgid "backup_tsm_password = password" +msgstr "" + +#: ./doc/common/tables/cinder-backups_tsm.xml27(td) +msgid "(StrOpt) TSM password for the running username" +msgstr "" + +#: ./doc/common/tables/cinder-backups_tsm.xml30(td) +msgid "backup_tsm_volume_prefix = backup" +msgstr "" + +#: ./doc/common/tables/cinder-backups_tsm.xml31(td) +msgid "(StrOpt) Volume prefix for the backup id when backing up to TSM" +msgstr "" + +#: ./doc/common/tables/cinder-connection.xml8(caption) +msgid "Description of configuration options for connection" +msgstr "" + +#: ./doc/common/tables/cinder-connection.xml22(td) +msgid "connection = sqlite:///$state_path/$sqlite_db" +msgstr "" + +#: ./doc/common/tables/swift-proxy-server-filter-authtoken.xml7(literal) +msgid "[filter:authtoken]" +msgstr "" + +#: ./doc/common/tables/swift-proxy-server-filter-authtoken.xml18(td) +msgid "auth_host = keystonehost" +msgstr "" + +#: ./doc/common/tables/swift-proxy-server-filter-authtoken.xml21(td) +msgid "auth_port = 35357" +msgstr "" + +#: ./doc/common/tables/swift-proxy-server-filter-authtoken.xml24(td) +msgid "auth_protocol = http" +msgstr "" + +#: ./doc/common/tables/swift-proxy-server-filter-authtoken.xml27(td) +msgid "auth_uri = http://keystonehost:5000/" +msgstr "" + +#: ./doc/common/tables/swift-proxy-server-filter-authtoken.xml30(td) +msgid "admin_tenant_name = service" +msgstr "" + +#: ./doc/common/tables/swift-proxy-server-filter-authtoken.xml33(td) +msgid "admin_user = swift" +msgstr "" + +#: ./doc/common/tables/swift-proxy-server-filter-authtoken.xml36(td) +msgid "admin_password = password" +msgstr "" + +#: ./doc/common/tables/swift-proxy-server-filter-authtoken.xml39(td) +msgid "delay_auth_decision = 1" +msgstr "" + +#: ./doc/common/tables/swift-proxy-server-filter-authtoken.xml42(td) +msgid "cache = swift.cache" +msgstr "" + +#: ./doc/common/tables/neutron-zeromq.xml27(td) +msgid "rpc_zmq_host = [hostname]" +msgstr "" + +#: ./doc/common/tables/neutron-zeromq.xml35(td) +msgid "" +"rpc_zmq_matchmaker = " +"neutron.openstack.common.rpc.matchmaker.MatchMakerLocalhost" +msgstr "" + +#: ./doc/common/tables/neutron-vpn.xml19(td) +msgid "config_base_dir = $state_path/ipsec" +msgstr "" + +#: ./doc/common/tables/neutron-vpn.xml20(td) +msgid "(StrOpt) Location to store ipsec server config files" +msgstr "" + +#: ./doc/common/tables/neutron-vpn.xml23(td) +msgid "" +"ipsec_config_template = /usr/lib/python2.7/site-" +"packages/neutron/services/vpn/device_drivers/template/openswan/ipsec.conf.template" +msgstr "" + +#: ./doc/common/tables/neutron-vpn.xml24(td) +msgid "(StrOpt) Template file for ipsec configuration" +msgstr "" + +#: ./doc/common/tables/neutron-vpn.xml27(td) +msgid "" +"ipsec_secret_template = /usr/lib/python2.7/site-" +"packages/neutron/services/vpn/device_drivers/template/openswan/ipsec.secret.template" +msgstr "" + +#: ./doc/common/tables/neutron-vpn.xml28(td) +msgid "(StrOpt) Template file for ipsec secret configuration" +msgstr "" + +#: ./doc/common/tables/neutron-vpn.xml31(td) +msgid "ipsec_status_check_interval = 60" +msgstr "" + +#: ./doc/common/tables/neutron-vpn.xml32(td) +msgid "(IntOpt) Interval for checking ipsec status" +msgstr "" + +#: ./doc/common/tables/neutron-vpn.xml35(td) +msgid "" +"vpn_device_driver = " +"['neutron.services.vpn.device_drivers.ipsec.OpenSwanDriver']" +msgstr "" + +#: ./doc/common/tables/neutron-vpn.xml36(td) +msgid "(MultiStrOpt) The vpn device drivers Neutron will use" +msgstr "" + +#: ./doc/common/tables/cinder-log.xml8(caption) +msgid "Description of configuration options for log" +msgstr "" + +#: ./doc/common/tables/neutron-agent.xml8(caption) +msgid "Description of configuration options for agent" +msgstr "" + +#: ./doc/common/tables/neutron-agent.xml19(td) +msgid "agent_down_time = 9" +msgstr "" + +#: ./doc/common/tables/neutron-agent.xml20(td) +msgid "" +"(IntOpt) Seconds to regard the agent is down; should be at least twice " +"report_interval, to be sure the agent is down for good." +msgstr "" + +#: ./doc/common/tables/neutron-agent.xml23(td) +msgid "external_pids = $state_path/external/pids" +msgstr "" + +#: ./doc/common/tables/neutron-agent.xml24(td) +msgid "(StrOpt) Location to store child pid files" +msgstr "" + +#: ./doc/common/tables/neutron-agent.xml27(td) +msgid "interface_driver = None" +msgstr "" + +#: ./doc/common/tables/neutron-agent.xml28(td) +msgid "(StrOpt) The driver used to manage the virtual interface." +msgstr "" + +#: ./doc/common/tables/neutron-agent.xml31(td) +msgid "report_interval = 4" +msgstr "" + +#: ./doc/common/tables/neutron-agent.xml32(td) +msgid "" +"(FloatOpt) Seconds between nodes reporting state to server; should be less " +"than agent_down_time, best if it is half or less than agent_down_time." +msgstr "" + +#: ./doc/common/tables/neutron-agent.xml35(td) +msgid "use_namespaces = True" +msgstr "" + +#: ./doc/common/tables/neutron-agent.xml36(td) +msgid "(BoolOpt) Allow overlapping IP." +msgstr "" + +#: ./doc/common/tables/neutron-ryu.xml8(caption) +msgid "Description of configuration options for ryu" +msgstr "" + +#: ./doc/common/tables/neutron-ryu.xml19(td) +msgid "openflow_rest_api = 127.0.0.1:8080" +msgstr "" + +#: ./doc/common/tables/neutron-ryu.xml20(td) +msgid "(StrOpt) OpenFlow REST API location" +msgstr "" + +#: ./doc/common/tables/neutron-ryu.xml23(td) +msgid "ovsdb_interface = None" +msgstr "" + +#: ./doc/common/tables/neutron-ryu.xml24(td) +msgid "(StrOpt) OVSDB interface to connect to" +msgstr "" + +#: ./doc/common/tables/neutron-ryu.xml27(td) +msgid "ovsdb_ip = None" +msgstr "" + +#: ./doc/common/tables/neutron-ryu.xml28(td) +msgid "(StrOpt) OVSDB IP to connect to" +msgstr "" + +#: ./doc/common/tables/neutron-ryu.xml31(td) +msgid "ovsdb_port = 6634" +msgstr "" + +#: ./doc/common/tables/neutron-ryu.xml32(td) +msgid "(IntOpt) OVSDB port to connect to" +msgstr "" + +#: ./doc/common/tables/neutron-ryu.xml35(td) +msgid "tunnel_interface = None" +msgstr "" + +#: ./doc/common/tables/neutron-ryu.xml36(td) +msgid "(StrOpt) Tunnel interface to use" +msgstr "" + +#: ./doc/common/tables/neutron-ryu.xml39(td) +msgid "tunnel_ip = None" +msgstr "" + +#: ./doc/common/tables/neutron-ryu.xml40(td) +msgid "(StrOpt) Tunnel IP to use" +msgstr "" + +#: ./doc/common/tables/neutron-ryu.xml43(td) +msgid "tunnel_key_max = 16777215" +msgstr "" + +#: ./doc/common/tables/neutron-ryu.xml44(td) +msgid "(IntOpt) Maximum tunnel ID to use" +msgstr "" + +#: ./doc/common/tables/neutron-ryu.xml47(td) +msgid "tunnel_key_min = 1" +msgstr "" + +#: ./doc/common/tables/neutron-ryu.xml48(td) +msgid "(IntOpt) Minimum tunnel ID to use" +msgstr "" + +#: ./doc/common/tables/swift-object-server-app-object-server.xml7(literal) +msgid "[app:object-server]" +msgstr "" + +#: ./doc/common/tables/swift-object-server-app-object-server.xml18(td) +msgid "use = egg:swift#object" +msgstr "" + +#: ./doc/common/tables/swift-object-server-app-object-server.xml21(td) +msgid "set log_name = object-server" +msgstr "" + +#: ./doc/common/tables/swift-object-server-app-object-server.xml42(td) +msgid "network_chunk_size = 65536" +msgstr "" + +#: ./doc/common/tables/swift-object-server-app-object-server.xml42(td) +msgid "Size of chunks to read/write over the network" +msgstr "" + +#: ./doc/common/tables/swift-object-server-app-object-server.xml45(td) +msgid "disk_chunk_size = 65536" +msgstr "" + +#: ./doc/common/tables/swift-object-server-app-object-server.xml45(td) +msgid "Size of chunks to read/write to disk" +msgstr "" + +#: ./doc/common/tables/swift-object-server-app-object-server.xml48(td) +msgid "max_upload_time = 86400" +msgstr "" + +#: ./doc/common/tables/swift-object-server-app-object-server.xml48(td) +msgid "Maximum time allowed to upload an object" +msgstr "" + +#: ./doc/common/tables/swift-object-server-app-object-server.xml51(td) +msgid "slow = 0" +msgstr "" + +#: ./doc/common/tables/swift-object-server-app-object-server.xml51(td) +msgid "" +"If > 0, Minimum time in seconds for a PUT or DELETE request to complete" +msgstr "" + +#: ./doc/common/tables/swift-object-server-app-object-server.xml54(td) +msgid "keep_cache_size = 5424880" +msgstr "" + +#: ./doc/common/tables/swift-object-server-app-object-server.xml54(td) +msgid "Largest object size to keep in buffer cache" +msgstr "" + +#: ./doc/common/tables/swift-object-server-app-object-server.xml57(td) +msgid "keep_cache_private = false" +msgstr "" + +#: ./doc/common/tables/swift-object-server-app-object-server.xml57(td) +msgid "Allow non-public objects to stay in kernel's buffer cache" +msgstr "" + +#: ./doc/common/tables/swift-object-server-app-object-server.xml60(td) +msgid "mb_per_sync = 512" +msgstr "" + +#: ./doc/common/tables/swift-object-server-app-object-server.xml60(td) +msgid "On PUT requests, sync file every n MB" +msgstr "" + +#: ./doc/common/tables/swift-object-server-app-object-server.xml63(td) +msgid "" +"allowed_headers = Content-Disposition, Content-Encoding, X-Delete-At, X" +"-Object-Manifest, X-Static-Large-Object" +msgstr "" + +#: ./doc/common/tables/swift-object-server-app-object-server.xml63(td) +msgid "" +"Comma-separated list of headers that can be set in metadata of an object" +msgstr "" + +#: ./doc/common/tables/swift-object-server-app-object-server.xml72(td) +msgid "threads_per_disk = 0" +msgstr "" + +#: ./doc/common/tables/swift-object-server-app-object-server.xml72(td) +msgid "" +"Size of the per-disk thread pool used for performing disk I/O. The default " +"of 0 means to not use a per-disk thread pool. It is recommended to keep this" +" value small, as large values can result in high read latencies due to large" +" queue depths. A good starting point is 4 threads per disk." +msgstr "" + +#: ./doc/common/tables/neutron-policy.xml19(td) +msgid "allow_overlapping_ips = False" +msgstr "" + +#: ./doc/common/tables/neutron-policy.xml20(td) +msgid "(BoolOpt) Allow overlapping IP support in Neutron" +msgstr "" + +#: ./doc/common/tables/neutron-policy.xml24(td) +msgid "(StrOpt) The policy file to use" +msgstr "" + +#: ./doc/common/tables/swift-proxy-server-DEFAULT.xml21(td) +msgid "bind_port = 80" +msgstr "" + +#: ./doc/common/tables/swift-proxy-server-DEFAULT.xml49(td) +msgid "cert_file = /etc/swift/proxy.crt" +msgstr "" + +#: ./doc/common/tables/swift-proxy-server-DEFAULT.xml49(td) +msgid "to the ssl .crt. This should be enabled for testing purposes only." +msgstr "" + +#: ./doc/common/tables/swift-proxy-server-DEFAULT.xml52(td) +msgid "key_file = /etc/swift/proxy.key" +msgstr "" + +#: ./doc/common/tables/swift-proxy-server-DEFAULT.xml52(td) +msgid "to the ssl .key. This should be enabled for testing purposes only." +msgstr "" + +#: ./doc/common/tables/swift-proxy-server-DEFAULT.xml67(td) +msgid "log_headers = false" +msgstr "" + +#: ./doc/common/tables/swift-proxy-server-DEFAULT.xml73(td) +msgid "trans_id_suffix =" +msgstr "" + +#: ./doc/common/tables/swift-proxy-server-DEFAULT.xml103(td) +msgid "cors_allow_origin =" +msgstr "" + +#: ./doc/common/tables/swift-proxy-server-DEFAULT.xml103(td) +msgid "" +"is a list of hosts that are included with any CORS request by default and " +"returned with the Access-Control-Allow-Origin header in addition to what the" +" container has set. to call to setup custom log handlers. for eventlet the " +"proxy server. For most cases, this should be `egg:swift#proxy`. request " +"whenever it has to failover to a handoff node" +msgstr "" + +#: ./doc/common/tables/swift-proxy-server-DEFAULT.xml106(td) +msgid "client_timeout = 60" +msgstr "" + +#: ./doc/common/tables/swift-proxy-server-DEFAULT.xml106(td) +msgid "Timeout to read one chunk from a client external services" +msgstr "" + +#: ./doc/common/tables/swift-proxy-server-filter-staticweb.xml7(literal) +msgid "[filter:staticweb]" +msgstr "" + +#: ./doc/common/tables/swift-proxy-server-filter-staticweb.xml18(td) +msgid "use = egg:swift#staticweb" +msgstr "" + +#: ./doc/common/tables/neutron-meta.xml8(caption) +msgid "Description of configuration options for meta" +msgstr "" + +#: ./doc/common/tables/neutron-meta.xml19(td) +msgid "default_flavor =" +msgstr "" + +#: ./doc/common/tables/neutron-meta.xml20(td) +msgid "(StrOpt) Default flavor to use" +msgstr "" + +#: ./doc/common/tables/neutron-meta.xml23(td) +msgid "default_l3_flavor =" +msgstr "" + +#: ./doc/common/tables/neutron-meta.xml24(td) +msgid "(StrOpt) Default L3 flavor to use" +msgstr "" + +#: ./doc/common/tables/neutron-meta.xml27(td) +msgid "extension_map =" +msgstr "" + +#: ./doc/common/tables/neutron-meta.xml28(td) +msgid "(StrOpt) A list of extensions, per plugin, to load." +msgstr "" + +#: ./doc/common/tables/neutron-meta.xml31(td) +msgid "l3_plugin_list =" +msgstr "" + +#: ./doc/common/tables/neutron-meta.xml32(td) +msgid "(StrOpt) List of L3 plugins to load" +msgstr "" + +#: ./doc/common/tables/neutron-meta.xml35(td) +msgid "plugin_list =" +msgstr "" + +#: ./doc/common/tables/neutron-meta.xml36(td) +msgid "(StrOpt) List of plugins to load" +msgstr "" + +#: ./doc/common/tables/neutron-meta.xml39(td) +msgid "supported_extension_aliases =" +msgstr "" + +#: ./doc/common/tables/neutron-meta.xml40(td) +msgid "(StrOpt) Supported extension aliases" +msgstr "" + +#: ./doc/common/tables/neutron-ssl.xml8(caption) +#: ./doc/common/tables/glance-ssl.xml8(caption) +msgid "Description of configuration options for ssl" +msgstr "" + +#: ./doc/common/tables/neutron-ssl.xml20(td) +msgid "(StrOpt) Key file" +msgstr "" + +#: ./doc/common/tables/neutron-ssl.xml35(td) +#: ./doc/common/tables/neutron-nec.xml51(td) +msgid "use_ssl = False" +msgstr "" + +#: ./doc/common/tables/neutron-ssl.xml36(td) +msgid "(BoolOpt) Enable SSL on the API server" +msgstr "" + +#: ./doc/common/tables/nova-scheduling.xml8(caption) +msgid "Description of configuration options for scheduling" +msgstr "" + +#: ./doc/common/tables/nova-scheduling.xml22(td) +msgid "aggregate_image_properties_isolation_namespace = None" +msgstr "" + +#: ./doc/common/tables/nova-scheduling.xml23(td) +msgid "" +"(StrOpt) Force the filter to consider only keys matching the given " +"namespace." +msgstr "" + +#: ./doc/common/tables/nova-scheduling.xml26(td) +msgid "aggregate_image_properties_isolation_separator = ." +msgstr "" + +#: ./doc/common/tables/nova-scheduling.xml27(td) +msgid "(StrOpt) The separator used between the namespace and keys" +msgstr "" + +#: ./doc/common/tables/nova-scheduling.xml30(td) +msgid "cpu_allocation_ratio = 16.0" +msgstr "" + +#: ./doc/common/tables/nova-scheduling.xml31(td) +msgid "" +"(FloatOpt) Virtual CPU to physical CPU allocation ratio which affects all " +"CPU filters. This configuration specifies a global ratio for CoreFilter. For" +" AggregateCoreFilter, it will fall back to this configuration value if no " +"per-aggregate setting found." +msgstr "" + +#: ./doc/common/tables/nova-scheduling.xml34(td) +msgid "disk_allocation_ratio = 1.0" +msgstr "" + +#: ./doc/common/tables/nova-scheduling.xml35(td) +msgid "(FloatOpt) virtual disk to physical disk allocation ratio" +msgstr "" + +#: ./doc/common/tables/nova-scheduling.xml38(td) +msgid "isolated_hosts =" +msgstr "" + +#: ./doc/common/tables/nova-scheduling.xml39(td) +msgid "(ListOpt) Host reserved for specific images" +msgstr "" + +#: ./doc/common/tables/nova-scheduling.xml42(td) +msgid "isolated_images =" +msgstr "" + +#: ./doc/common/tables/nova-scheduling.xml43(td) +msgid "(ListOpt) Images to run on isolated host" +msgstr "" + +#: ./doc/common/tables/nova-scheduling.xml46(td) +msgid "max_instances_per_host = 50" +msgstr "" + +#: ./doc/common/tables/nova-scheduling.xml47(td) +msgid "(IntOpt) Ignore hosts that have too many instances" +msgstr "" + +#: ./doc/common/tables/nova-scheduling.xml50(td) +msgid "max_io_ops_per_host = 8" +msgstr "" + +#: ./doc/common/tables/nova-scheduling.xml51(td) +msgid "" +"(IntOpt) Ignore hosts that have too many builds/resizes/snaps/migrations" +msgstr "" + +#: ./doc/common/tables/nova-scheduling.xml54(td) +msgid "ram_allocation_ratio = 1.5" +msgstr "" + +#: ./doc/common/tables/nova-scheduling.xml55(td) +msgid "" +"(FloatOpt) Virtual ram to physical ram allocation ratio which affects all " +"ram filters. This configuration specifies a global ratio for RamFilter. For " +"AggregateRamFilter, it will fall back to this configuration value if no per-" +"aggregate setting found." +msgstr "" + +#: ./doc/common/tables/nova-scheduling.xml58(td) +msgid "ram_weight_multiplier = 1.0" +msgstr "" + +#: ./doc/common/tables/nova-scheduling.xml59(td) +#: ./doc/common/tables/nova-scheduling.xml118(td) +msgid "" +"(FloatOpt) Multiplier used for weighing ram. Negative numbers mean to stack " +"vs spread." +msgstr "" + +#: ./doc/common/tables/nova-scheduling.xml62(td) +msgid "reserved_host_disk_mb = 0" +msgstr "" + +#: ./doc/common/tables/nova-scheduling.xml63(td) +msgid "(IntOpt) Amount of disk in MB to reserve for the host" +msgstr "" + +#: ./doc/common/tables/nova-scheduling.xml66(td) +msgid "reserved_host_memory_mb = 512" +msgstr "" + +#: ./doc/common/tables/nova-scheduling.xml67(td) +msgid "(IntOpt) Amount of memory in MB to reserve for the host" +msgstr "" + +#: ./doc/common/tables/nova-scheduling.xml70(td) +msgid "restrict_isolated_hosts_to_isolated_images = True" +msgstr "" + +#: ./doc/common/tables/nova-scheduling.xml71(td) +msgid "(BoolOpt) Whether to force isolated hosts to run only isolated images" +msgstr "" + +#: ./doc/common/tables/nova-scheduling.xml74(td) +msgid "scheduler_available_filters = ['nova.scheduler.filters.all_filters']" +msgstr "" + +#: ./doc/common/tables/nova-scheduling.xml75(td) +msgid "" +"(MultiStrOpt) Filter classes available to the scheduler which may be " +"specified more than once. An entry of " +"\"nova.scheduler.filters.standard_filters\" maps to all filters included " +"with nova." +msgstr "" + +#: ./doc/common/tables/nova-scheduling.xml78(td) +msgid "" +"scheduler_default_filters = RetryFilter, AvailabilityZoneFilter, RamFilter, " +"ComputeFilter, ComputeCapabilitiesFilter, ImagePropertiesFilter" +msgstr "" + +#: ./doc/common/tables/nova-scheduling.xml79(td) +#: ./doc/common/tables/cinder-scheduler.xml23(td) +msgid "" +"(ListOpt) Which filter class names to use for filtering hosts when not " +"specified in the request." +msgstr "" + +#: ./doc/common/tables/nova-scheduling.xml82(td) +msgid "scheduler_driver = nova.scheduler.filter_scheduler.FilterScheduler" +msgstr "" + +#: ./doc/common/tables/nova-scheduling.xml83(td) +msgid "(StrOpt) Default driver to use for the scheduler" +msgstr "" + +#: ./doc/common/tables/nova-scheduling.xml86(td) +msgid "scheduler_host_manager = nova.scheduler.host_manager.HostManager" +msgstr "" + +#: ./doc/common/tables/nova-scheduling.xml87(td) +#: ./doc/common/tables/cinder-scheduler.xml35(td) +msgid "(StrOpt) The scheduler host manager class to use" +msgstr "" + +#: ./doc/common/tables/nova-scheduling.xml90(td) +msgid "scheduler_host_subset_size = 1" +msgstr "" + +#: ./doc/common/tables/nova-scheduling.xml91(td) +msgid "" +"(IntOpt) New instances will be scheduled on a host chosen randomly from a " +"subset of the N best hosts. This property defines the subset size that a " +"host is chosen from. A value of 1 chooses the first host returned by the " +"weighing functions. This value must be at least 1. Any value less than 1 " +"will be ignored, and 1 will be used instead" +msgstr "" + +#: ./doc/common/tables/nova-scheduling.xml94(td) +#: ./doc/common/tables/cinder-scheduler.xml38(td) +msgid "scheduler_json_config_location =" +msgstr "" + +#: ./doc/common/tables/nova-scheduling.xml95(td) +#: ./doc/common/tables/cinder-scheduler.xml39(td) +msgid "(StrOpt) Absolute path to scheduler configuration JSON file." +msgstr "" + +#: ./doc/common/tables/nova-scheduling.xml98(td) +msgid "scheduler_manager = nova.scheduler.manager.SchedulerManager" +msgstr "" + +#: ./doc/common/tables/nova-scheduling.xml99(td) +#: ./doc/common/tables/cinder-scheduler.xml43(td) +msgid "(StrOpt) full class name for the Manager for scheduler" +msgstr "" + +#: ./doc/common/tables/nova-scheduling.xml102(td) +#: ./doc/common/tables/cinder-scheduler.xml46(td) +msgid "scheduler_max_attempts = 3" +msgstr "" + +#: ./doc/common/tables/nova-scheduling.xml103(td) +msgid "(IntOpt) Maximum number of attempts to schedule an instance" +msgstr "" + +#: ./doc/common/tables/nova-scheduling.xml106(td) +msgid "scheduler_topic = scheduler" +msgstr "" + +#: ./doc/common/tables/nova-scheduling.xml107(td) +#: ./doc/common/tables/cinder-scheduler.xml51(td) +msgid "(StrOpt) the topic scheduler nodes listen on" +msgstr "" + +#: ./doc/common/tables/nova-scheduling.xml110(td) +msgid "scheduler_weight_classes = nova.scheduler.weights.all_weighers" +msgstr "" + +#: ./doc/common/tables/nova-scheduling.xml111(td) +msgid "(ListOpt) Which weight class names to use for weighing hosts" +msgstr "" + +#: ./doc/common/tables/nova-scheduling.xml117(td) +msgid "ram_weight_multiplier = 10.0" +msgstr "" + +#: ./doc/common/tables/nova-scheduling.xml121(td) +msgid "scheduler_filter_classes = nova.cells.filters.all_filters" +msgstr "" + +#: ./doc/common/tables/nova-scheduling.xml122(td) +msgid "" +"(ListOpt) Filter classes the cells scheduler should use. An entry of " +"\"nova.cells.filters.all_filters\"maps to all cells filters included with " +"nova." +msgstr "" + +#: ./doc/common/tables/nova-scheduling.xml125(td) +msgid "scheduler_retries = 10" +msgstr "" + +#: ./doc/common/tables/nova-scheduling.xml126(td) +msgid "(IntOpt) How many retries when no cells are available." +msgstr "" + +#: ./doc/common/tables/nova-scheduling.xml129(td) +msgid "scheduler_retry_delay = 2" +msgstr "" + +#: ./doc/common/tables/nova-scheduling.xml130(td) +msgid "(IntOpt) How often to retry in seconds when no cells are available." +msgstr "" + +#: ./doc/common/tables/nova-scheduling.xml133(td) +msgid "scheduler_weight_classes = nova.cells.weights.all_weighers" +msgstr "" + +#: ./doc/common/tables/nova-scheduling.xml134(td) +msgid "" +"(ListOpt) Weigher classes the cells scheduler should use. An entry of " +"\"nova.cells.weights.all_weighers\"maps to all cell weighers included with " +"nova." +msgstr "" + +#: ./doc/common/tables/nova-scheduling.xml137(th) +msgid "[metrics]" +msgstr "" + +#: ./doc/common/tables/nova-scheduling.xml140(td) +msgid "weight_multiplier = 1.0" +msgstr "" + +#: ./doc/common/tables/nova-scheduling.xml141(td) +msgid "(FloatOpt) Multiplier used for weighing metrics." +msgstr "" + +#: ./doc/common/tables/nova-scheduling.xml144(td) +msgid "weight_setting =" +msgstr "" + +#: ./doc/common/tables/nova-scheduling.xml145(td) +msgid "" +"(ListOpt) How the metrics are going to be weighed. This should be in the " +"form of \"<name1>=<ratio1>, <name2>=<ratio2>, ...\"," +" where <nameX> is one of the metric to be weighed, and <ratioX> " +"is the corresponding ratio. So for \"name1=1.0, name2=-1.0\" The final " +"weight would be name1.value * 1.0 + name2.value * -1.0." +msgstr "" + +#: ./doc/common/tables/swift-drive-audit-drive-audit.xml7(literal) +msgid "[drive-audit]" +msgstr "" + +#: ./doc/common/tables/swift-drive-audit-drive-audit.xml7(literal) +msgid "drive-audit.conf-sample" +msgstr "" + +#: ./doc/common/tables/swift-drive-audit-drive-audit.xml18(td) +msgid "device_dir = /srv/node" +msgstr "" + +#: ./doc/common/tables/swift-drive-audit-drive-audit.xml18(td) +msgid "Directory devices are mounted under" +msgstr "" + +#: ./doc/common/tables/swift-drive-audit-drive-audit.xml30(td) +msgid "minutes = 60" +msgstr "" + +#: ./doc/common/tables/swift-drive-audit-drive-audit.xml30(td) +msgid "Number of minutes to look back in `/var/log/kern.log`" +msgstr "" + +#: ./doc/common/tables/swift-drive-audit-drive-audit.xml33(td) +msgid "error_limit = 1" +msgstr "" + +#: ./doc/common/tables/swift-drive-audit-drive-audit.xml33(td) +msgid "Number of errors to find before a device is unmounted" +msgstr "" + +#: ./doc/common/tables/swift-drive-audit-drive-audit.xml36(td) +msgid "log_file_pattern = /var/log/kern*" +msgstr "" + +#: ./doc/common/tables/swift-drive-audit-drive-audit.xml36(td) +msgid "" +"Location of the log file with globbing pattern to check against device " +"errors locate device blocks with errors in the log file" +msgstr "" + +#: ./doc/common/tables/swift-drive-audit-drive-audit.xml39(td) +msgid "regex_pattern_1 = \\berror\\b.*\\b(dm-[0-9]{1,2}\\d?)\\b" +msgstr "" + +#: ./doc/common/tables/neutron-db.xml23(td) +msgid "connection = sqlite://" +msgstr "" + +#: ./doc/common/tables/neutron-db.xml35(td) +msgid "dhcp_agents_per_network = 1" +msgstr "" + +#: ./doc/common/tables/neutron-db.xml36(td) +msgid "(IntOpt) Number of DHCP agents scheduled to host a network." +msgstr "" + +#: ./doc/common/tables/neutron-db.xml43(td) +msgid "max_overflow = 20" +msgstr "" + +#: ./doc/common/tables/neutron-db.xml47(td) +msgid "max_pool_size = 10" +msgstr "" + +#: ./doc/common/tables/neutron-db.xml59(td) +msgid "pool_timeout = 10" +msgstr "" + +#: ./doc/common/tables/neutron-db.xml71(td) +msgid "sqlite_db =" +msgstr "" + +#: ./doc/common/tables/neutron-brocade.xml8(caption) +msgid "Description of configuration options for brocade" +msgstr "" + +#: ./doc/common/tables/neutron-brocade.xml19(td) +msgid "address =" +msgstr "" + +#: ./doc/common/tables/neutron-brocade.xml20(td) +msgid "(StrOpt) The address of the host to SSH to" +msgstr "" + +#: ./doc/common/tables/neutron-brocade.xml23(td) +msgid "ostype = NOS" +msgstr "" + +#: ./doc/common/tables/neutron-brocade.xml24(td) +msgid "(StrOpt) Currently unused" +msgstr "" + +#: ./doc/common/tables/neutron-brocade.xml27(td) +msgid "password =" +msgstr "" + +#: ./doc/common/tables/neutron-brocade.xml28(td) +msgid "(StrOpt) The SSH password to use" +msgstr "" + +#: ./doc/common/tables/neutron-brocade.xml31(td) +msgid "physical_interface = eth0" +msgstr "" + +#: ./doc/common/tables/neutron-brocade.xml32(td) +msgid "(StrOpt) The network interface to use when creatinga port" +msgstr "" + +#: ./doc/common/tables/neutron-brocade.xml35(td) +msgid "username =" +msgstr "" + +#: ./doc/common/tables/neutron-brocade.xml36(td) +msgid "(StrOpt) The SSH username to use" +msgstr "" + +#: ./doc/common/tables/swift-object-expirer-pipeline-main.xml18(td) +msgid "pipeline = catch_errors cache proxy-server" +msgstr "" + +#: ./doc/common/tables/neutron-linuxbridge_agent.xml8(caption) +msgid "Description of configuration options for linuxbridge_agent" +msgstr "" + +#: ./doc/common/tables/neutron-linuxbridge_agent.xml19(td) +msgid "enable_vxlan = False" +msgstr "" + +#: ./doc/common/tables/neutron-linuxbridge_agent.xml20(td) +msgid "" +"(BoolOpt) Enable VXLAN on the agent. Can be enabled when agent is managed by" +" ml2 plugin using linuxbridge mechanism driver" +msgstr "" + +#: ./doc/common/tables/neutron-linuxbridge_agent.xml24(td) +msgid "" +"(BoolOpt) Extension to use alongside ml2 plugin's l2population mechanism " +"driver. It enables the plugin to populate VXLAN forwarding table." +msgstr "" + +#: ./doc/common/tables/neutron-linuxbridge_agent.xml27(td) +#: ./doc/common/tables/neutron-linuxbridge_agent.xml31(td) +msgid "physical_interface_mappings =" +msgstr "" + +#: ./doc/common/tables/neutron-linuxbridge_agent.xml28(td) +#: ./doc/common/tables/neutron-linuxbridge_agent.xml32(td) +msgid "(ListOpt) List of <physical_network>:<physical_interface>" +msgstr "" + +#: ./doc/common/tables/neutron-linuxbridge_agent.xml35(td) +msgid "tos = None" +msgstr "" + +#: ./doc/common/tables/neutron-linuxbridge_agent.xml36(td) +msgid "(IntOpt) TOS for vxlan interface protocol packets." +msgstr "" + +#: ./doc/common/tables/neutron-linuxbridge_agent.xml39(td) +msgid "ttl = None" +msgstr "" + +#: ./doc/common/tables/neutron-linuxbridge_agent.xml40(td) +msgid "(IntOpt) TTL for vxlan interface protocol packets." +msgstr "" + +#: ./doc/common/tables/neutron-linuxbridge_agent.xml43(td) +msgid "vxlan_group = 224.0.0.1" +msgstr "" + +#: ./doc/common/tables/neutron-linuxbridge_agent.xml44(td) +msgid "(StrOpt) Multicast group for vxlan interface." +msgstr "" + +#: ./doc/common/tables/cinder-xiv.xml8(caption) +msgid "Description of configuration options for xiv" +msgstr "" + +#: ./doc/common/tables/cinder-xiv.xml22(td) +msgid "xiv_ds8k_connection_type = iscsi" +msgstr "" + +#: ./doc/common/tables/cinder-xiv.xml23(td) +msgid "" +"(StrOpt) Connection type to the IBM Storage Array (fibre_channel|iscsi)" +msgstr "" + +#: ./doc/common/tables/cinder-xiv.xml26(td) +msgid "xiv_ds8k_proxy = xiv_ds8k_openstack.nova_proxy.XIVDS8KNovaProxy" +msgstr "" + +#: ./doc/common/tables/cinder-xiv.xml27(td) +msgid "(StrOpt) Proxy driver that connects to the IBM Storage Array" +msgstr "" + +#: ./doc/common/tables/swift-proxy-server-filter-container-quotas.xml7(literal) +msgid "[filter:container-quotas]" +msgstr "" + +#: ./doc/common/tables/swift-proxy-server-filter-container-quotas.xml18(td) +msgid "use = egg:swift#container_quotas" +msgstr "" + +#: ./doc/common/tables/swift-swift-swift-hash.xml7(literal) +msgid "[swift-hash]" +msgstr "" + +#: ./doc/common/tables/swift-swift-swift-hash.xml18(td) +msgid "swift_hash_path_suffix = changeme" +msgstr "" + +#: ./doc/common/tables/swift-swift-swift-hash.xml18(td) +msgid "" +"A suffix used by hash_path to offer a bit more security when generating " +"hashes for paths. It simply appends this value to all paths; if someone " +"knows this suffix, it's easier for them to guess the hash a path will end up" +" with. New installations are advised to set this parameter to a random " +"secret, which would not be disclosed ouside the organization. The same " +"secret needs to be used by all swift servers of the same cluster. Existing " +"installations should set this parameter to an empty string." +msgstr "" + +#: ./doc/common/tables/swift-swift-swift-hash.xml29(td) +msgid "swift_hash_path_prefix = changeme" +msgstr "" + +#: ./doc/common/tables/swift-swift-swift-hash.xml29(td) +msgid "" +"A prefix used by hash_path to offer a bit more security when generating " +"hashes for paths. It simply appends this value to all paths; if someone " +"knows this suffix, it's easier for them to guess the hash a path will end up" +" with. New installations are advised to set this parameter to a random " +"secret, which would not be disclosed ouside the organization. The same " +"secret needs to be used by all swift servers of the same cluster. Existing " +"installations should set this parameter to an empty string." +msgstr "" + +#: ./doc/common/tables/cinder-auth.xml8(caption) +msgid "Description of configuration options for auth" +msgstr "" + +#: ./doc/common/tables/cinder-auth.xml23(td) +msgid "" +"(StrOpt) The strategy to use for auth. Supports noauth, keystone, and " +"deprecated." +msgstr "" + +#: ./doc/common/tables/swift-proxy-server-filter-formpost.xml7(literal) +msgid "[filter:formpost]" +msgstr "" + +#: ./doc/common/tables/swift-proxy-server-filter-formpost.xml18(td) +msgid "use = egg:swift#formpost" +msgstr "" + +#: ./doc/common/tables/cinder-hds.xml8(caption) +msgid "Description of configuration options for hds" +msgstr "" + +#: ./doc/common/tables/cinder-hds.xml22(td) +msgid "hds_cinder_config_file = /opt/hds/hus/cinder_hus_conf.xml" +msgstr "" + +#: ./doc/common/tables/cinder-hds.xml23(td) +msgid "(StrOpt) configuration file for HDS cinder plugin for HUS" +msgstr "" + +#: ./doc/common/tables/nova-spice.xml8(caption) +msgid "Description of configuration options for spice" +msgstr "" + +#: ./doc/common/tables/nova-spice.xml19(th) +msgid "[spice]" +msgstr "" + +#: ./doc/common/tables/nova-spice.xml22(td) +msgid "agent_enabled = True" +msgstr "" + +#: ./doc/common/tables/nova-spice.xml23(td) +msgid "(BoolOpt) enable spice guest agent support" +msgstr "" + +#: ./doc/common/tables/nova-spice.xml27(td) +msgid "(BoolOpt) enable spice related features" +msgstr "" + +#: ./doc/common/tables/nova-spice.xml30(td) +msgid "html5proxy_base_url = http://127.0.0.1:6082/spice_auto.html" +msgstr "" + +#: ./doc/common/tables/nova-spice.xml31(td) +msgid "" +"(StrOpt) location of spice html5 console proxy, in the form " +"\"http://127.0.0.1:6082/spice_auto.html\"" +msgstr "" + +#: ./doc/common/tables/nova-spice.xml34(td) +msgid "keymap = en-us" +msgstr "" + +#: ./doc/common/tables/nova-spice.xml35(td) +msgid "(StrOpt) keymap for spice" +msgstr "" + +#: ./doc/common/tables/nova-spice.xml38(td) +msgid "server_listen = 127.0.0.1" +msgstr "" + +#: ./doc/common/tables/nova-spice.xml39(td) +msgid "(StrOpt) IP address on which instance spice server should listen" +msgstr "" + +#: ./doc/common/tables/nova-spice.xml42(td) +msgid "server_proxyclient_address = 127.0.0.1" +msgstr "" + +#: ./doc/common/tables/nova-spice.xml43(td) +msgid "" +"(StrOpt) the address to which proxy clients (like nova-spicehtml5proxy) " +"should connect" +msgstr "" + +#: ./doc/common/tables/neutron-midonet.xml8(caption) +msgid "Description of configuration options for midonet" +msgstr "" + +#: ./doc/common/tables/neutron-midonet.xml19(td) +msgid "midonet_host_uuid_path = /etc/midolman/host_uuid.properties" +msgstr "" + +#: ./doc/common/tables/neutron-midonet.xml20(td) +msgid "(StrOpt) Path to midonet host uuid file" +msgstr "" + +#: ./doc/common/tables/neutron-midonet.xml23(td) +msgid "midonet_uri = http://localhost:8080/midonet-api" +msgstr "" + +#: ./doc/common/tables/neutron-midonet.xml24(td) +msgid "(StrOpt) MidoNet API server URI." +msgstr "" + +#: ./doc/common/tables/neutron-midonet.xml27(td) +msgid "mode = dev" +msgstr "" + +#: ./doc/common/tables/neutron-midonet.xml28(td) +msgid "(StrOpt) Operational mode. Internal dev use only." +msgstr "" + +#: ./doc/common/tables/neutron-midonet.xml31(td) +msgid "password = passw0rd" +msgstr "" + +#: ./doc/common/tables/neutron-midonet.xml32(td) +msgid "(StrOpt) MidoNet admin password." +msgstr "" + +#: ./doc/common/tables/neutron-midonet.xml35(td) +msgid "project_id = 77777777-7777-7777-7777-777777777777" +msgstr "" + +#: ./doc/common/tables/neutron-midonet.xml36(td) +msgid "(StrOpt) ID of the project that MidoNet admin userbelongs to." +msgstr "" + +#: ./doc/common/tables/neutron-midonet.xml39(td) +msgid "provider_router_id = None" +msgstr "" + +#: ./doc/common/tables/neutron-midonet.xml40(td) +msgid "(StrOpt) Virtual provider router ID." +msgstr "" + +#: ./doc/common/tables/neutron-midonet.xml43(td) +msgid "username = admin" +msgstr "" + +#: ./doc/common/tables/neutron-midonet.xml44(td) +msgid "(StrOpt) MidoNet admin username." +msgstr "" + +#: ./doc/common/tables/cinder-storwize.xml8(caption) +msgid "Description of configuration options for storwize" +msgstr "" + +#: ./doc/common/tables/cinder-storwize.xml22(td) +msgid "storwize_svc_connection_protocol = iSCSI" +msgstr "" + +#: ./doc/common/tables/cinder-storwize.xml23(td) +msgid "(StrOpt) Connection protocol (iSCSI/FC)" +msgstr "" + +#: ./doc/common/tables/cinder-storwize.xml26(td) +msgid "storwize_svc_flashcopy_timeout = 120" +msgstr "" + +#: ./doc/common/tables/cinder-storwize.xml27(td) +msgid "" +"(IntOpt) Maximum number of seconds to wait for FlashCopy to be prepared. " +"Maximum value is 600 seconds (10 minutes)" +msgstr "" + +#: ./doc/common/tables/cinder-storwize.xml30(td) +msgid "storwize_svc_iscsi_chap_enabled = True" +msgstr "" + +#: ./doc/common/tables/cinder-storwize.xml31(td) +msgid "" +"(BoolOpt) Configure CHAP authentication for iSCSI connections (Default: " +"Enabled)" +msgstr "" + +#: ./doc/common/tables/cinder-storwize.xml34(td) +msgid "storwize_svc_multihostmap_enabled = True" +msgstr "" + +#: ./doc/common/tables/cinder-storwize.xml35(td) +msgid "(BoolOpt) Allows vdisk to multi host mapping" +msgstr "" + +#: ./doc/common/tables/cinder-storwize.xml38(td) +msgid "storwize_svc_multipath_enabled = False" +msgstr "" + +#: ./doc/common/tables/cinder-storwize.xml39(td) +msgid "" +"(BoolOpt) Connect with multipath (FC only; iSCSI multipath is controlled by " +"Nova)" +msgstr "" + +#: ./doc/common/tables/cinder-storwize.xml42(td) +msgid "storwize_svc_vol_autoexpand = True" +msgstr "" + +#: ./doc/common/tables/cinder-storwize.xml43(td) +msgid "(BoolOpt) Storage system autoexpand parameter for volumes (True/False)" +msgstr "" + +#: ./doc/common/tables/cinder-storwize.xml46(td) +msgid "storwize_svc_vol_compression = False" +msgstr "" + +#: ./doc/common/tables/cinder-storwize.xml47(td) +msgid "(BoolOpt) Storage system compression option for volumes" +msgstr "" + +#: ./doc/common/tables/cinder-storwize.xml50(td) +msgid "storwize_svc_vol_easytier = True" +msgstr "" + +#: ./doc/common/tables/cinder-storwize.xml51(td) +msgid "(BoolOpt) Enable Easy Tier for volumes" +msgstr "" + +#: ./doc/common/tables/cinder-storwize.xml54(td) +msgid "storwize_svc_vol_grainsize = 256" +msgstr "" + +#: ./doc/common/tables/cinder-storwize.xml55(td) +msgid "" +"(IntOpt) Storage system grain size parameter for volumes (32/64/128/256)" +msgstr "" + +#: ./doc/common/tables/cinder-storwize.xml58(td) +msgid "storwize_svc_vol_iogrp = 0" +msgstr "" + +#: ./doc/common/tables/cinder-storwize.xml59(td) +msgid "(IntOpt) The I/O group in which to allocate volumes" +msgstr "" + +#: ./doc/common/tables/cinder-storwize.xml62(td) +msgid "storwize_svc_vol_rsize = 2" +msgstr "" + +#: ./doc/common/tables/cinder-storwize.xml63(td) +msgid "" +"(IntOpt) Storage system space-efficiency parameter for volumes (percentage)" +msgstr "" + +#: ./doc/common/tables/cinder-storwize.xml66(td) +msgid "storwize_svc_vol_warning = 0" +msgstr "" + +#: ./doc/common/tables/cinder-storwize.xml67(td) +msgid "" +"(IntOpt) Storage system threshold for volume capacity warnings (percentage)" +msgstr "" + +#: ./doc/common/tables/cinder-storwize.xml70(td) +msgid "storwize_svc_volpool_name = volpool" +msgstr "" + +#: ./doc/common/tables/cinder-storwize.xml71(td) +msgid "(StrOpt) Storage system storage pool for volumes" +msgstr "" + +#: ./doc/common/tables/cinder-solidfire.xml8(caption) +msgid "Description of configuration options for solidfire" +msgstr "" + +#: ./doc/common/tables/cinder-solidfire.xml22(td) +msgid "sf_account_prefix = None" +msgstr "" + +#: ./doc/common/tables/cinder-solidfire.xml23(td) +msgid "" +"(StrOpt) Create SolidFire accounts with this prefix. Any string can be used " +"here, but the string \"hostname\" is special and will create a prefix using " +"the cinder node hostsname (previous default behavior). The default is NO " +"prefix." +msgstr "" + +#: ./doc/common/tables/cinder-solidfire.xml26(td) +msgid "sf_allow_tenant_qos = False" +msgstr "" + +#: ./doc/common/tables/cinder-solidfire.xml27(td) +msgid "(BoolOpt) Allow tenants to specify QOS on create" +msgstr "" + +#: ./doc/common/tables/cinder-solidfire.xml30(td) +msgid "sf_api_port = 443" +msgstr "" + +#: ./doc/common/tables/cinder-solidfire.xml31(td) +msgid "" +"(IntOpt) SolidFire API port. Useful if the device api is behind a proxy on a" +" different port." +msgstr "" + +#: ./doc/common/tables/cinder-solidfire.xml34(td) +msgid "sf_emulate_512 = True" +msgstr "" + +#: ./doc/common/tables/cinder-solidfire.xml35(td) +msgid "(BoolOpt) Set 512 byte emulation on volume creation;" +msgstr "" + +#: ./doc/common/tables/glance-ssl.xml23(td) +msgid "(StrOpt) CA certificate file to use to verify connecting clients." +msgstr "" + +#: ./doc/common/tables/glance-ssl.xml27(td) +msgid "(StrOpt) Certificate file to use when starting API server securely." +msgstr "" + +#: ./doc/common/tables/glance-ssl.xml31(td) +msgid "(StrOpt) Private key file to use when starting API server securely." +msgstr "" + +#: ./doc/common/tables/nova-apiv3.xml8(caption) +msgid "Description of configuration options for apiv3" +msgstr "" + +#: ./doc/common/tables/nova-apiv3.xml19(th) +msgid "[osapi_v3]" +msgstr "" + +#: ./doc/common/tables/nova-apiv3.xml23(td) +msgid "(BoolOpt) Whether the V3 API is enabled or not" +msgstr "" + +#: ./doc/common/tables/nova-apiv3.xml26(td) +msgid "extensions_blacklist =" +msgstr "" + +#: ./doc/common/tables/nova-apiv3.xml27(td) +msgid "" +"(ListOpt) A list of v3 API extensions to never load. Specify the extension " +"aliases here." +msgstr "" + +#: ./doc/common/tables/nova-apiv3.xml30(td) +msgid "extensions_whitelist =" +msgstr "" + +#: ./doc/common/tables/nova-apiv3.xml31(td) +msgid "" +"(ListOpt) If the list is not empty then a v3 API extension will only be " +"loaded if it exists in this list. Specify the extension aliases here." +msgstr "" + +#: ./doc/common/tables/glance-db.xml22(td) +msgid "sqlite_db = glance.sqlite" +msgstr "" + +#: ./doc/common/tables/glance-db.xml37(td) +msgid "" +"connection = " +"sqlite:////home/shaunm/Projects/glance/glance/openstack/common/db/$sqlite_db" +msgstr "" + +#: ./doc/common/tables/nova-api.xml26(td) +msgid "enabled_apis = ec2, osapi_compute, metadata" +msgstr "" + +#: ./doc/common/tables/nova-api.xml27(td) +msgid "(ListOpt) a list of APIs to enable by default" +msgstr "" + +#: ./doc/common/tables/nova-api.xml30(td) +msgid "enabled_ssl_apis =" +msgstr "" + +#: ./doc/common/tables/nova-api.xml31(td) +msgid "(ListOpt) a list of APIs with enabled SSL" +msgstr "" + +#: ./doc/common/tables/nova-api.xml34(td) +msgid "instance_name_template = instance-%08x" +msgstr "" + +#: ./doc/common/tables/nova-api.xml35(td) +msgid "(StrOpt) Template string to be used to generate instance names" +msgstr "" + +#: ./doc/common/tables/nova-api.xml38(td) +msgid "multi_instance_display_name_template = %(name)s-%(uuid)s" +msgstr "" + +#: ./doc/common/tables/nova-api.xml39(td) +msgid "" +"(StrOpt) When creating multiple instances with a single request using the " +"os-multiple-create API extension, this template will be used to build the " +"display name for each instance. The benefit is that the instances end up " +"with different hostnames. To restore legacy behavior of every instance " +"having the same name, set this option to \"%(name)s\". Valid keys for the " +"template are: name, uuid, count." +msgstr "" + +#: ./doc/common/tables/nova-api.xml42(td) +msgid "non_inheritable_image_properties = cache_in_nova, bittorrent" +msgstr "" + +#: ./doc/common/tables/nova-api.xml43(td) +msgid "" +"(ListOpt) These are image properties which a snapshot should not inherit " +"from an instance" +msgstr "" + +#: ./doc/common/tables/nova-api.xml46(td) +msgid "null_kernel = nokernel" +msgstr "" + +#: ./doc/common/tables/nova-api.xml47(td) +msgid "" +"(StrOpt) kernel image that indicates not to use a kernel, but to use a raw " +"disk image instead" +msgstr "" + +#: ./doc/common/tables/nova-api.xml50(td) +msgid "osapi_compute_ext_list =" +msgstr "" + +#: ./doc/common/tables/nova-api.xml51(td) +msgid "" +"(ListOpt) Specify list of extensions to load when using " +"osapi_compute_extension option with " +"nova.api.openstack.compute.contrib.select_extensions" +msgstr "" + +#: ./doc/common/tables/nova-api.xml54(td) +msgid "" +"osapi_compute_extension = " +"['nova.api.openstack.compute.contrib.standard_extensions']" +msgstr "" + +#: ./doc/common/tables/nova-api.xml55(td) +msgid "(MultiStrOpt) osapi compute extension to load" +msgstr "" + +#: ./doc/common/tables/nova-api.xml58(td) +msgid "osapi_compute_link_prefix = None" +msgstr "" + +#: ./doc/common/tables/nova-api.xml59(td) +msgid "" +"(StrOpt) Base URL that will be presented to users in links to the OpenStack " +"Compute API" +msgstr "" + +#: ./doc/common/tables/nova-api.xml62(td) +msgid "osapi_compute_listen = 0.0.0.0" +msgstr "" + +#: ./doc/common/tables/nova-api.xml63(td) +msgid "(StrOpt) The IP address on which the OpenStack API will listen." +msgstr "" + +#: ./doc/common/tables/nova-api.xml66(td) +msgid "osapi_compute_listen_port = 8774" +msgstr "" + +#: ./doc/common/tables/nova-api.xml67(td) +msgid "(IntOpt) The port on which the OpenStack API will listen." +msgstr "" + +#: ./doc/common/tables/nova-api.xml70(td) +msgid "osapi_compute_workers = None" +msgstr "" + +#: ./doc/common/tables/nova-api.xml71(td) +msgid "(IntOpt) Number of workers for OpenStack API service" +msgstr "" + +#: ./doc/common/tables/nova-api.xml74(td) +msgid "osapi_hide_server_address_states = building" +msgstr "" + +#: ./doc/common/tables/nova-api.xml75(td) +msgid "(ListOpt) List of instance states that should hide network info" +msgstr "" + +#: ./doc/common/tables/nova-api.xml78(td) +msgid "servicegroup_driver = db" +msgstr "" + +#: ./doc/common/tables/nova-api.xml79(td) +msgid "" +"(StrOpt) The driver for servicegroup service (valid options are: db, zk, mc)" +msgstr "" + +#: ./doc/common/tables/swift-rsyncd-container.xml7(literal) +msgid "[container]" +msgstr "" + +#: ./doc/common/tables/swift-rsyncd-container.xml18(td) +msgid "max connections = 4" +msgstr "" + +#: ./doc/common/tables/swift-rsyncd-container.xml27(td) +msgid "lock file = /var/lock/container.lock" +msgstr "" + +#: ./doc/common/tables/cinder-san-solaris.xml8(caption) +msgid "Description of configuration options for san-solaris" +msgstr "" + +#: ./doc/common/tables/cinder-san-solaris.xml22(td) +msgid "san_zfs_volume_base = rpool/" +msgstr "" + +#: ./doc/common/tables/cinder-san-solaris.xml23(td) +msgid "(StrOpt) The ZFS path under which to create zvols for volumes." +msgstr "" + +#: ./doc/common/tables/cinder-netapp_cdot_nfs.xml8(caption) +msgid "Description of configuration options for netapp_cdot_nfs" +msgstr "" + +#: ./doc/common/tables/glance-paste.xml8(caption) +msgid "Description of configuration options for paste" +msgstr "" + +#: ./doc/common/tables/glance-paste.xml19(th) +msgid "[paste_deploy]" +msgstr "" + +#: ./doc/common/tables/glance-paste.xml22(td) +msgid "config_file = None" +msgstr "" + +#: ./doc/common/tables/glance-paste.xml23(td) +msgid "(StrOpt) Name of the paste configuration file." +msgstr "" + +#: ./doc/common/tables/glance-paste.xml26(td) +msgid "flavor = None" +msgstr "" + +#: ./doc/common/tables/glance-paste.xml27(td) +msgid "" +"(StrOpt) Partial name of a pipeline in your paste configuration file with " +"the service name removed. For example, if your paste section name is " +"[pipeline:glance-api-keystone] use the value \"keystone\"" +msgstr "" + +#: ./doc/common/tables/neutron-quotas.xml8(caption) +msgid "Description of configuration options for quotas" +msgstr "" + +#: ./doc/common/tables/neutron-quotas.xml19(td) +msgid "default_quota = -1" +msgstr "" + +#: ./doc/common/tables/neutron-quotas.xml20(td) +msgid "" +"(IntOpt) Default number of resource allowed per tenant. A negative value " +"means unlimited." +msgstr "" + +#: ./doc/common/tables/neutron-quotas.xml23(td) +msgid "max_routes = 30" +msgstr "" + +#: ./doc/common/tables/neutron-quotas.xml24(td) +msgid "(IntOpt) Maximum number of routes" +msgstr "" + +#: ./doc/common/tables/neutron-quotas.xml27(td) +msgid "quota_driver = neutron.db.quota_db.DbQuotaDriver" +msgstr "" + +#: ./doc/common/tables/neutron-quotas.xml28(td) +msgid "(StrOpt) Default driver to use for quota checks" +msgstr "" + +#: ./doc/common/tables/neutron-quotas.xml31(td) +msgid "quota_firewall = 1" +msgstr "" + +#: ./doc/common/tables/neutron-quotas.xml32(td) +msgid "" +"(IntOpt) Number of firewalls allowed per tenant. A negative value means " +"unlimited." +msgstr "" + +#: ./doc/common/tables/neutron-quotas.xml35(td) +msgid "quota_firewall_policy = 1" +msgstr "" + +#: ./doc/common/tables/neutron-quotas.xml36(td) +msgid "" +"(IntOpt) Number of firewall policies allowed per tenant. A negative value " +"means unlimited." +msgstr "" + +#: ./doc/common/tables/neutron-quotas.xml39(td) +msgid "quota_firewall_rule = -1" +msgstr "" + +#: ./doc/common/tables/neutron-quotas.xml40(td) +msgid "" +"(IntOpt) Number of firewall rules allowed per tenant. A negative value means" +" unlimited." +msgstr "" + +#: ./doc/common/tables/neutron-quotas.xml43(td) +msgid "quota_floatingip = 50" +msgstr "" + +#: ./doc/common/tables/neutron-quotas.xml44(td) +msgid "" +"(IntOpt) Number of floating IPs allowed per tenant. A negative value means " +"unlimited." +msgstr "" + +#: ./doc/common/tables/neutron-quotas.xml47(td) +msgid "quota_items = network, subnet, port" +msgstr "" + +#: ./doc/common/tables/neutron-quotas.xml48(td) +msgid "(ListOpt) Resource name(s) that are supported in quota features" +msgstr "" + +#: ./doc/common/tables/neutron-quotas.xml51(td) +msgid "quota_network = 10" +msgstr "" + +#: ./doc/common/tables/neutron-quotas.xml52(td) +msgid "" +"(IntOpt) Number of networks allowed per tenant.A negative value means " +"unlimited." +msgstr "" + +#: ./doc/common/tables/neutron-quotas.xml55(td) +msgid "quota_network_gateway = 5" +msgstr "" + +#: ./doc/common/tables/neutron-quotas.xml56(td) +msgid "" +"(IntOpt) Number of network gateways allowed per tenant, -1 for unlimited" +msgstr "" + +#: ./doc/common/tables/neutron-quotas.xml59(td) +msgid "quota_packet_filter = 100" +msgstr "" + +#: ./doc/common/tables/neutron-quotas.xml60(td) +msgid "(IntOpt) Number of packet_filters allowed per tenant, -1 for unlimited" +msgstr "" + +#: ./doc/common/tables/neutron-quotas.xml63(td) +msgid "quota_port = 50" +msgstr "" + +#: ./doc/common/tables/neutron-quotas.xml64(td) +msgid "" +"(IntOpt) Number of ports allowed per tenant. A negative value means " +"unlimited." +msgstr "" + +#: ./doc/common/tables/neutron-quotas.xml67(td) +msgid "quota_router = 10" +msgstr "" + +#: ./doc/common/tables/neutron-quotas.xml68(td) +msgid "" +"(IntOpt) Number of routers allowed per tenant. A negative value means " +"unlimited." +msgstr "" + +#: ./doc/common/tables/neutron-quotas.xml71(td) +msgid "quota_security_group = 10" +msgstr "" + +#: ./doc/common/tables/neutron-quotas.xml72(td) +msgid "" +"(IntOpt) Number of security groups allowed per tenant. A negative value " +"means unlimited." +msgstr "" + +#: ./doc/common/tables/neutron-quotas.xml75(td) +msgid "quota_security_group_rule = 100" +msgstr "" + +#: ./doc/common/tables/neutron-quotas.xml76(td) +msgid "" +"(IntOpt) Number of security rules allowed per tenant. A negative value means" +" unlimited." +msgstr "" + +#: ./doc/common/tables/neutron-quotas.xml79(td) +msgid "quota_subnet = 10" +msgstr "" + +#: ./doc/common/tables/neutron-quotas.xml80(td) +msgid "" +"(IntOpt) Number of subnets allowed per tenant, A negative value means " +"unlimited." +msgstr "" + +#: ./doc/common/tables/nova-rpc.xml42(td) +msgid "rpc_backend = nova.openstack.common.rpc.impl_kombu" +msgstr "" + +#: ./doc/common/tables/nova-rpc.xml65(td) +msgid "rpc_driver_queue_base = cells.intercell" +msgstr "" + +#: ./doc/common/tables/nova-rpc.xml66(td) +msgid "" +"(StrOpt) Base queue name to use when communicating between cells. Various " +"topics by message type will be appended to this." +msgstr "" + +#: ./doc/common/tables/nova-rpc.xml83(th) +#: ./doc/common/tables/nova-upgrade_levels.xml26(th) +msgid "[upgrade_levels]" +msgstr "" + +#: ./doc/common/tables/nova-rpc.xml86(td) +msgid "baseapi = None" +msgstr "" + +#: ./doc/common/tables/nova-rpc.xml87(td) +msgid "" +"(StrOpt) Set a version cap for messages sent to the base api in any service" +msgstr "" + +#: ./doc/common/tables/nova-baremetal.xml8(caption) +msgid "Description of configuration options for baremetal" +msgstr "" + +#: ./doc/common/tables/nova-baremetal.xml23(td) +msgid "(StrOpt) The backend to use for bare-metal database" +msgstr "" + +#: ./doc/common/tables/nova-baremetal.xml26(td) +msgid "deploy_kernel = None" +msgstr "" + +#: ./doc/common/tables/nova-baremetal.xml27(td) +msgid "(StrOpt) Default kernel image ID used in deployment phase" +msgstr "" + +#: ./doc/common/tables/nova-baremetal.xml30(td) +msgid "deploy_ramdisk = None" +msgstr "" + +#: ./doc/common/tables/nova-baremetal.xml31(td) +msgid "(StrOpt) Default ramdisk image ID used in deployment phase" +msgstr "" + +#: ./doc/common/tables/nova-baremetal.xml34(td) +msgid "driver = nova.virt.baremetal.pxe.PXE" +msgstr "" + +#: ./doc/common/tables/nova-baremetal.xml35(td) +msgid "(StrOpt) Baremetal driver back-end (pxe or tilera)" +msgstr "" + +#: ./doc/common/tables/nova-baremetal.xml38(td) +msgid "flavor_extra_specs =" +msgstr "" + +#: ./doc/common/tables/nova-baremetal.xml39(td) +msgid "" +"(ListOpt) a list of additional capabilities corresponding to " +"flavor_extra_specs for this compute host to advertise. Valid entries are " +"name=value, pairs For example, \"key1:val1, key2:val2\"" +msgstr "" + +#: ./doc/common/tables/nova-baremetal.xml42(td) +msgid "ipmi_power_retry = 10" +msgstr "" + +#: ./doc/common/tables/nova-baremetal.xml43(td) +msgid "(IntOpt) maximal number of retries for IPMI operations" +msgstr "" + +#: ./doc/common/tables/nova-baremetal.xml46(td) +msgid "" +"net_config_template = $pybasedir/nova/virt/baremetal/net-" +"dhcp.ubuntu.template" +msgstr "" + +#: ./doc/common/tables/nova-baremetal.xml47(td) +msgid "(StrOpt) Template file for injected network config" +msgstr "" + +#: ./doc/common/tables/nova-baremetal.xml50(td) +msgid "power_manager = nova.virt.baremetal.ipmi.IPMI" +msgstr "" + +#: ./doc/common/tables/nova-baremetal.xml51(td) +msgid "(StrOpt) Baremetal power management method" +msgstr "" + +#: ./doc/common/tables/nova-baremetal.xml54(td) +msgid "pxe_append_params = nofb nomodeset vga=normal" +msgstr "" + +#: ./doc/common/tables/nova-baremetal.xml55(td) +msgid "(StrOpt) additional append parameters for baremetal PXE boot" +msgstr "" + +#: ./doc/common/tables/nova-baremetal.xml58(td) +msgid "pxe_bootfile_name = pxelinux.0" +msgstr "" + +#: ./doc/common/tables/nova-baremetal.xml59(td) +msgid "" +"(StrOpt) This gets passed to Neutron as the bootfile dhcp parameter when the" +" dhcp_options_enabled is set." +msgstr "" + +#: ./doc/common/tables/nova-baremetal.xml62(td) +msgid "" +"pxe_config_template = $pybasedir/nova/virt/baremetal/pxe_config.template" +msgstr "" + +#: ./doc/common/tables/nova-baremetal.xml63(td) +msgid "(StrOpt) Template file for PXE configuration" +msgstr "" + +#: ./doc/common/tables/nova-baremetal.xml66(td) +msgid "pxe_deploy_timeout = 0" +msgstr "" + +#: ./doc/common/tables/nova-baremetal.xml67(td) +msgid "(IntOpt) Timeout for PXE deployments. Default: 0 (unlimited)" +msgstr "" + +#: ./doc/common/tables/nova-baremetal.xml70(td) +msgid "pxe_network_config = False" +msgstr "" + +#: ./doc/common/tables/nova-baremetal.xml71(td) +msgid "" +"(BoolOpt) If set, pass the network configuration details to the initramfs " +"via cmdline." +msgstr "" + +#: ./doc/common/tables/nova-baremetal.xml74(td) +msgid "sql_connection = sqlite:///$state_path/baremetal_$sqlite_db" +msgstr "" + +#: ./doc/common/tables/nova-baremetal.xml75(td) +msgid "" +"(StrOpt) The SQLAlchemy connection string used to connect to the bare-metal " +"database" +msgstr "" + +#: ./doc/common/tables/nova-baremetal.xml78(td) +msgid "terminal = shellinaboxd" +msgstr "" + +#: ./doc/common/tables/nova-baremetal.xml79(td) +msgid "(StrOpt) path to baremetal terminal program" +msgstr "" + +#: ./doc/common/tables/nova-baremetal.xml82(td) +msgid "terminal_cert_dir = None" +msgstr "" + +#: ./doc/common/tables/nova-baremetal.xml83(td) +msgid "(StrOpt) path to baremetal terminal SSL cert(PEM)" +msgstr "" + +#: ./doc/common/tables/nova-baremetal.xml86(td) +msgid "terminal_pid_dir = $state_path/baremetal/console" +msgstr "" + +#: ./doc/common/tables/nova-baremetal.xml87(td) +msgid "(StrOpt) path to directory stores pidfiles of baremetal_terminal" +msgstr "" + +#: ./doc/common/tables/nova-baremetal.xml90(td) +msgid "tftp_root = /tftpboot" +msgstr "" + +#: ./doc/common/tables/nova-baremetal.xml91(td) +msgid "(StrOpt) Baremetal compute node's tftp root path" +msgstr "" + +#: ./doc/common/tables/nova-baremetal.xml94(td) +msgid "use_file_injection = True" +msgstr "" + +#: ./doc/common/tables/nova-baremetal.xml95(td) +msgid "" +"(BoolOpt) If True, enable file injection for network info, files and admin " +"password" +msgstr "" + +#: ./doc/common/tables/nova-baremetal.xml98(td) +msgid "use_unsafe_iscsi = False" +msgstr "" + +#: ./doc/common/tables/nova-baremetal.xml99(td) +msgid "" +"(BoolOpt) Do not set this out of dev/test environments. If a node does not " +"have a fixed PXE IP address, volumes are exported with globally opened ACL" +msgstr "" + +#: ./doc/common/tables/nova-baremetal.xml102(td) +msgid "vif_driver = nova.virt.baremetal.vif_driver.BareMetalVIFDriver" +msgstr "" + +#: ./doc/common/tables/nova-baremetal.xml103(td) +msgid "(StrOpt) Baremetal VIF driver." +msgstr "" + +#: ./doc/common/tables/nova-baremetal.xml106(td) +msgid "virtual_power_host_key = None" +msgstr "" + +#: ./doc/common/tables/nova-baremetal.xml107(td) +msgid "(StrOpt) ssh key for virtual power host_user" +msgstr "" + +#: ./doc/common/tables/nova-baremetal.xml110(td) +msgid "virtual_power_host_pass =" +msgstr "" + +#: ./doc/common/tables/nova-baremetal.xml111(td) +msgid "(StrOpt) password for virtual power host_user" +msgstr "" + +#: ./doc/common/tables/nova-baremetal.xml114(td) +msgid "virtual_power_host_user =" +msgstr "" + +#: ./doc/common/tables/nova-baremetal.xml115(td) +msgid "(StrOpt) user to execute virtual power commands as" +msgstr "" + +#: ./doc/common/tables/nova-baremetal.xml118(td) +msgid "virtual_power_ssh_host =" +msgstr "" + +#: ./doc/common/tables/nova-baremetal.xml119(td) +msgid "(StrOpt) ip or name to virtual power host" +msgstr "" + +#: ./doc/common/tables/nova-baremetal.xml122(td) +msgid "virtual_power_ssh_port = 22" +msgstr "" + +#: ./doc/common/tables/nova-baremetal.xml123(td) +msgid "(IntOpt) Port to use for ssh to virtual power host" +msgstr "" + +#: ./doc/common/tables/nova-baremetal.xml126(td) +msgid "virtual_power_type = virsh" +msgstr "" + +#: ./doc/common/tables/nova-baremetal.xml127(td) +msgid "(StrOpt) base command to use for virtual power(vbox,virsh)" +msgstr "" + +#: ./doc/common/tables/nova-baremetal.xml133(td) +msgid "vif_driver = nova.virt.xenapi.vif.XenAPIBridgeDriver" +msgstr "" + +#: ./doc/common/tables/nova-baremetal.xml134(td) +msgid "(StrOpt) The XenAPI VIF driver using XenServer Network APIs." +msgstr "" + +#: ./doc/common/tables/swift-account-server-pipeline-main.xml18(td) +msgid "pipeline = healthcheck recon account-server" +msgstr "" + +#: ./doc/common/tables/glance-api.xml22(td) +msgid "admin_role = admin" +msgstr "" + +#: ./doc/common/tables/glance-api.xml23(td) +msgid "(StrOpt) Role used to identify an authenticated user as administrator." +msgstr "" + +#: ./doc/common/tables/glance-api.xml26(td) +msgid "allow_anonymous_access = False" +msgstr "" + +#: ./doc/common/tables/glance-api.xml27(td) +msgid "" +"(BoolOpt) Allow unauthenticated users to access the API with read-only " +"privileges. This only applies when using ContextMiddleware." +msgstr "" + +#: ./doc/common/tables/glance-api.xml30(td) +msgid "default_publisher_id = image.localhost" +msgstr "" + +#: ./doc/common/tables/glance-api.xml34(td) +msgid "default_store = file" +msgstr "" + +#: ./doc/common/tables/glance-api.xml35(td) +msgid "" +"(StrOpt) Default scheme to use to store image data. The scheme must be " +"registered by one of the stores defined by the 'known_stores' config option." +msgstr "" + +#: ./doc/common/tables/glance-api.xml39(td) +msgid "(BoolOpt) Deploy the v1 OpenStack Images API." +msgstr "" + +#: ./doc/common/tables/glance-api.xml43(td) +msgid "(BoolOpt) Deploy the v2 OpenStack Images API." +msgstr "" + +#: ./doc/common/tables/glance-api.xml46(td) +msgid "image_size_cap = 1099511627776" +msgstr "" + +#: ./doc/common/tables/glance-api.xml47(td) +msgid "" +"(IntOpt) Maximum size of image a user can upload in bytes. Defaults to " +"1099511627776 bytes (1 TB)." +msgstr "" + +#: ./doc/common/tables/glance-api.xml50(td) +msgid "" +"known_stores = glance.store.filesystem.Store, glance.store.http.Store, " +"glance.store.rbd.Store, glance.store.s3.Store, glance.store.swift.Store, " +"glance.store.sheepdog.Store, glance.store.cinder.Store" +msgstr "" + +#: ./doc/common/tables/glance-api.xml51(td) +msgid "" +"(ListOpt) List of which store classes and store class locations are " +"currently known to glance at startup." +msgstr "" + +#: ./doc/common/tables/glance-api.xml54(td) +msgid "owner_is_tenant = True" +msgstr "" + +#: ./doc/common/tables/glance-api.xml55(td) +msgid "" +"(BoolOpt) When true, this option sets the owner of an image to be the " +"tenant. Otherwise, the owner of the image will be the authenticated user " +"issuing the request." +msgstr "" + +#: ./doc/common/tables/glance-api.xml58(td) +msgid "send_identity_headers = False" +msgstr "" + +#: ./doc/common/tables/glance-api.xml59(td) +msgid "" +"(BoolOpt) Whether to pass through headers containing user and tenant " +"information when making requests to the registry. This allows the registry " +"to use the context middleware without the keystoneclients' auth_token " +"middleware, removing calls to the keystone auth service. It is recommended " +"that when using this option, secure communication between glance api and " +"glance registry is ensured by means other than auth_token middleware." +msgstr "" + +#: ./doc/common/tables/glance-api.xml62(td) +msgid "show_multiple_locations = False" +msgstr "" + +#: ./doc/common/tables/glance-api.xml63(td) +msgid "" +"(BoolOpt) Whether to include the backend image locations in image " +"properties. Revealing storage location can be a security risk, so use this " +"setting with caution! The overrides show_image_direct_url." +msgstr "" + +#: ./doc/common/tables/glance-api.xml66(td) +msgid "use_user_token = True" +msgstr "" + +#: ./doc/common/tables/glance-api.xml67(td) +msgid "" +"(BoolOpt) Whether to pass through the user token when making requests to the" +" registry." +msgstr "" + +#: ./doc/common/tables/cinder-scheduler.xml22(td) +msgid "" +"scheduler_default_filters = AvailabilityZoneFilter, CapacityFilter, " +"CapabilitiesFilter" +msgstr "" + +#: ./doc/common/tables/cinder-scheduler.xml26(td) +msgid "scheduler_default_weighers = CapacityWeigher" +msgstr "" + +#: ./doc/common/tables/cinder-scheduler.xml27(td) +msgid "(ListOpt) Which weigher class names to use for weighing hosts." +msgstr "" + +#: ./doc/common/tables/cinder-scheduler.xml30(td) +msgid "scheduler_driver = cinder.scheduler.filter_scheduler.FilterScheduler" +msgstr "" + +#: ./doc/common/tables/cinder-scheduler.xml31(td) +msgid "(StrOpt) Default scheduler driver to use" +msgstr "" + +#: ./doc/common/tables/cinder-scheduler.xml34(td) +msgid "scheduler_host_manager = cinder.scheduler.host_manager.HostManager" +msgstr "" + +#: ./doc/common/tables/cinder-scheduler.xml42(td) +msgid "scheduler_manager = cinder.scheduler.manager.SchedulerManager" +msgstr "" + +#: ./doc/common/tables/cinder-scheduler.xml47(td) +msgid "(IntOpt) Maximum number of attempts to schedule an volume" +msgstr "" + +#: ./doc/common/tables/cinder-scheduler.xml50(td) +msgid "scheduler_topic = cinder-scheduler" +msgstr "" + +#: ./doc/common/tables/neutron-ml2_ncs.xml8(caption) +msgid "Description of configuration options for ml2_ncs" +msgstr "" + +#: ./doc/common/tables/neutron-ml2_ncs.xml20(td) +msgid "(IntOpt) HTTP timeout in seconds." +msgstr "" + +#: ./doc/common/tables/neutron-ml2_ncs.xml23(td) +msgid "url = None" +msgstr "" + +#: ./doc/common/tables/neutron-ml2_ncs.xml24(td) +msgid "(StrOpt) HTTP URL of Tail-f NCS REST interface." +msgstr "" + +#: ./doc/common/tables/neutron-nec.xml8(caption) +msgid "Description of configuration options for nec" +msgstr "" + +#: ./doc/common/tables/neutron-nec.xml20(td) +msgid "(StrOpt) Certificate file" +msgstr "" + +#: ./doc/common/tables/neutron-nec.xml23(td) +msgid "default_router_provider = l3-agent" +msgstr "" + +#: ./doc/common/tables/neutron-nec.xml24(td) +msgid "(StrOpt) Default router provider to use." +msgstr "" + +#: ./doc/common/tables/neutron-nec.xml27(td) +msgid "driver = neutron.services.firewall.drivers.fwaas_base.NoopFwaasDriver" +msgstr "" + +#: ./doc/common/tables/neutron-nec.xml28(td) +msgid "(StrOpt) Name of the FWaaS Driver" +msgstr "" + +#: ./doc/common/tables/neutron-nec.xml31(td) +msgid "driver = trema" +msgstr "" + +#: ./doc/common/tables/neutron-nec.xml32(td) +msgid "(StrOpt) Driver to use" +msgstr "" + +#: ./doc/common/tables/neutron-nec.xml35(td) +msgid "enable_packet_filter = True" +msgstr "" + +#: ./doc/common/tables/neutron-nec.xml36(td) +msgid "(BoolOpt) Enable packet filter" +msgstr "" + +#: ./doc/common/tables/neutron-nec.xml40(td) +msgid "(StrOpt) Host to connect to" +msgstr "" + +#: ./doc/common/tables/neutron-nec.xml43(td) +msgid "port = 8888" +msgstr "" + +#: ./doc/common/tables/neutron-nec.xml44(td) +msgid "(StrOpt) Port to connect to" +msgstr "" + +#: ./doc/common/tables/neutron-nec.xml47(td) +msgid "router_providers = l3-agent, openflow" +msgstr "" + +#: ./doc/common/tables/neutron-nec.xml48(td) +msgid "(ListOpt) List of enabled router providers." +msgstr "" + +#: ./doc/common/tables/neutron-nec.xml52(td) +msgid "(BoolOpt) Use SSL to connect" +msgstr "" + +#: ./doc/common/tables/swift-object-expirer-object-expirer.xml7(literal) +msgid "[object-expirer]" +msgstr "" + +#: ./doc/common/tables/swift-object-expirer-object-expirer.xml24(td) +msgid "report_interval = 300" +msgstr "" + +#: ./doc/common/tables/swift-object-expirer-object-expirer.xml30(td) +msgid "processes = 0" +msgstr "" + +#: ./doc/common/tables/swift-object-expirer-object-expirer.xml33(td) +msgid "process = 0" +msgstr "" + +#: ./doc/common/tables/swift-object-expirer-object-expirer.xml33(td) +msgid "" +"(it will actually accept(2) N + 1). Setting this to one (1) will only handle" +" one request at a time, without accepting another request concurrently." +msgstr "" + +#: ./doc/common/tables/glance-cinder.xml8(caption) +msgid "Description of configuration options for cinder" +msgstr "" + +#: ./doc/common/tables/glance-cinder.xml27(td) +msgid "" +"(StrOpt) Location of ca certicates file to use for cinder client requests." +msgstr "" + +#: ./doc/common/tables/nova-redis.xml8(caption) +msgid "Description of configuration options for redis" +msgstr "" + +#: ./doc/common/tables/nova-redis.xml34(th) +msgid "[remote_debug]" +msgstr "" + +#: ./doc/common/tables/nova-redis.xml37(td) +msgid "host = None" +msgstr "" + +#: ./doc/common/tables/nova-redis.xml38(td) +msgid "" +"(StrOpt) Debug host (ip or name) to connect. Note that using the remote " +"debug option changes how Nova uses the eventlet library to support async IO." +" This could result in failures that do not occur under normal operation. Use" +" at your own risk." +msgstr "" + +#: ./doc/common/tables/nova-redis.xml41(td) +msgid "port = None" +msgstr "" + +#: ./doc/common/tables/nova-redis.xml42(td) +msgid "" +"(IntOpt) Debug port to connect. Note that using the remote debug option " +"changes how Nova uses the eventlet library to support async IO. This could " +"result in failures that do not occur under normal operation. Use at your own" +" risk." +msgstr "" + +#: ./doc/common/tables/neutron-embrane.xml8(caption) +msgid "Description of configuration options for embrane" +msgstr "" + +#: ./doc/common/tables/neutron-embrane.xml19(td) +msgid "admin_username = admin" +msgstr "" + +#: ./doc/common/tables/neutron-embrane.xml20(td) +msgid "(StrOpt) ESM admin username." +msgstr "" + +#: ./doc/common/tables/neutron-embrane.xml23(td) +msgid "async_requests = True" +msgstr "" + +#: ./doc/common/tables/neutron-embrane.xml24(td) +msgid "(BoolOpt) Define if the requests have run asynchronously or not" +msgstr "" + +#: ./doc/common/tables/neutron-embrane.xml27(td) +msgid "dummy_utif_id = None" +msgstr "" + +#: ./doc/common/tables/neutron-embrane.xml28(td) +msgid "(StrOpt) Dummy user traffic Security Zone id" +msgstr "" + +#: ./doc/common/tables/neutron-embrane.xml31(td) +msgid "esm_mgmt = None" +msgstr "" + +#: ./doc/common/tables/neutron-embrane.xml32(td) +msgid "(StrOpt) ESM management root address" +msgstr "" + +#: ./doc/common/tables/neutron-embrane.xml35(td) +msgid "inband_id = None" +msgstr "" + +#: ./doc/common/tables/neutron-embrane.xml36(td) +msgid "(StrOpt) In band Security Zone id" +msgstr "" + +#: ./doc/common/tables/neutron-embrane.xml39(td) +msgid "mgmt_id = None" +msgstr "" + +#: ./doc/common/tables/neutron-embrane.xml40(td) +msgid "(StrOpt) Management Security Zone id" +msgstr "" + +#: ./doc/common/tables/neutron-embrane.xml43(td) +msgid "oob_id = None" +msgstr "" + +#: ./doc/common/tables/neutron-embrane.xml44(td) +msgid "(StrOpt) Out of band Security Zone id" +msgstr "" + +#: ./doc/common/tables/neutron-embrane.xml47(td) +msgid "resource_pool_id = default" +msgstr "" + +#: ./doc/common/tables/neutron-embrane.xml48(td) +msgid "(StrOpt) Shared resource pool id" +msgstr "" + +#: ./doc/common/tables/neutron-embrane.xml51(td) +msgid "router_image = None" +msgstr "" + +#: ./doc/common/tables/neutron-embrane.xml52(td) +msgid "(StrOpt) Router image id (Embrane FW/VPN)" +msgstr "" + +#: ./doc/common/tables/swift-proxy-server-pipeline-main.xml18(td) +msgid "" +"pipeline = catch_errors healthcheck proxy-logging cache bulk slo ratelimit " +"tempauth container-quotas account-quotas proxy-logging proxy-server" +msgstr "" + +#: ./doc/common/tables/nova-upgrade_levels.xml8(caption) +msgid "Description of configuration options for upgrade_levels" +msgstr "" + +#: ./doc/common/tables/nova-upgrade_levels.xml22(td) +msgid "scheduler = nova.cells.scheduler.CellsScheduler" +msgstr "" + +#: ./doc/common/tables/nova-upgrade_levels.xml23(td) +msgid "(StrOpt) Cells scheduler to use" +msgstr "" + +#: ./doc/common/tables/nova-upgrade_levels.xml29(td) +msgid "cells = None" +msgstr "" + +#: ./doc/common/tables/nova-upgrade_levels.xml30(td) +msgid "(StrOpt) Set a version cap for messages sent to local cells services" +msgstr "" + +#: ./doc/common/tables/nova-upgrade_levels.xml33(td) +msgid "cert = None" +msgstr "" + +#: ./doc/common/tables/nova-upgrade_levels.xml34(td) +msgid "(StrOpt) Set a version cap for messages sent to cert services" +msgstr "" + +#: ./doc/common/tables/nova-upgrade_levels.xml37(td) +msgid "compute = None" +msgstr "" + +#: ./doc/common/tables/nova-upgrade_levels.xml38(td) +msgid "(StrOpt) Set a version cap for messages sent to compute services" +msgstr "" + +#: ./doc/common/tables/nova-upgrade_levels.xml41(td) +msgid "conductor = None" +msgstr "" + +#: ./doc/common/tables/nova-upgrade_levels.xml42(td) +msgid "(StrOpt) Set a version cap for messages sent to conductor services" +msgstr "" + +#: ./doc/common/tables/nova-upgrade_levels.xml45(td) +msgid "console = None" +msgstr "" + +#: ./doc/common/tables/nova-upgrade_levels.xml46(td) +msgid "(StrOpt) Set a version cap for messages sent to console services" +msgstr "" + +#: ./doc/common/tables/nova-upgrade_levels.xml49(td) +msgid "consoleauth = None" +msgstr "" + +#: ./doc/common/tables/nova-upgrade_levels.xml50(td) +msgid "(StrOpt) Set a version cap for messages sent to consoleauth services" +msgstr "" + +#: ./doc/common/tables/nova-upgrade_levels.xml53(td) +msgid "intercell = None" +msgstr "" + +#: ./doc/common/tables/nova-upgrade_levels.xml54(td) +msgid "(StrOpt) Set a version cap for messages sent between cells services" +msgstr "" + +#: ./doc/common/tables/nova-upgrade_levels.xml57(td) +msgid "network = None" +msgstr "" + +#: ./doc/common/tables/nova-upgrade_levels.xml58(td) +msgid "(StrOpt) Set a version cap for messages sent to network services" +msgstr "" + +#: ./doc/common/tables/nova-upgrade_levels.xml61(td) +msgid "scheduler = None" +msgstr "" + +#: ./doc/common/tables/nova-upgrade_levels.xml62(td) +msgid "(StrOpt) Set a version cap for messages sent to scheduler services" +msgstr "" + +#: ./doc/common/tables/swift-proxy-server-filter-cname_lookup.xml7(literal) +msgid "[filter:cname_lookup]" +msgstr "" + +#: ./doc/common/tables/swift-proxy-server-filter-cname_lookup.xml18(td) +msgid "use = egg:swift#cname_lookup" +msgstr "" + +#: ./doc/common/tables/swift-proxy-server-filter-cname_lookup.xml21(td) +msgid "set log_name = cname_lookup" +msgstr "" + +#: ./doc/common/tables/swift-proxy-server-filter-cname_lookup.xml36(td) +#: ./doc/common/tables/swift-proxy-server-filter-domain_remap.xml36(td) +msgid "storage_domain = example.com" +msgstr "" + +#: ./doc/common/tables/swift-proxy-server-filter-cname_lookup.xml36(td) +#: ./doc/common/tables/swift-proxy-server-filter-domain_remap.xml36(td) +msgid "Domain to use for remap" +msgstr "" + +#: ./doc/common/tables/swift-proxy-server-filter-cname_lookup.xml39(td) +msgid "lookup_depth = 1" +msgstr "" + +#: ./doc/common/tables/swift-proxy-server-filter-cname_lookup.xml39(td) +msgid "As CNAMES can be recursive, how many levels to search through" +msgstr "" + +#: ./doc/common/tables/cinder-zadara.xml8(caption) +msgid "Description of configuration options for zadara" +msgstr "" + +#: ./doc/common/tables/cinder-zadara.xml22(td) +msgid "zadara_default_striping_mode = simple" +msgstr "" + +#: ./doc/common/tables/cinder-zadara.xml23(td) +msgid "(StrOpt) Default striping mode for volumes" +msgstr "" + +#: ./doc/common/tables/cinder-zadara.xml26(td) +msgid "zadara_password = None" +msgstr "" + +#: ./doc/common/tables/cinder-zadara.xml27(td) +msgid "(StrOpt) Password for the VPSA" +msgstr "" + +#: ./doc/common/tables/cinder-zadara.xml30(td) +msgid "zadara_user = None" +msgstr "" + +#: ./doc/common/tables/cinder-zadara.xml31(td) +msgid "(StrOpt) User name for the VPSA" +msgstr "" + +#: ./doc/common/tables/cinder-zadara.xml34(td) +msgid "zadara_vol_encrypt = False" +msgstr "" + +#: ./doc/common/tables/cinder-zadara.xml35(td) +msgid "(BoolOpt) Default encryption policy for volumes" +msgstr "" + +#: ./doc/common/tables/cinder-zadara.xml38(td) +msgid "zadara_vol_name_template = OS_%s" +msgstr "" + +#: ./doc/common/tables/cinder-zadara.xml39(td) +msgid "(StrOpt) Default template for VPSA volume names" +msgstr "" + +#: ./doc/common/tables/cinder-zadara.xml42(td) +msgid "zadara_vol_thin = True" +msgstr "" + +#: ./doc/common/tables/cinder-zadara.xml43(td) +msgid "(BoolOpt) Default thin provisioning policy for volumes" +msgstr "" + +#: ./doc/common/tables/cinder-zadara.xml46(td) +msgid "zadara_vpsa_allow_nonexistent_delete = True" +msgstr "" + +#: ./doc/common/tables/cinder-zadara.xml47(td) +msgid "(BoolOpt) Don't halt on deletion of non-existing volumes" +msgstr "" + +#: ./doc/common/tables/cinder-zadara.xml50(td) +msgid "zadara_vpsa_auto_detach_on_delete = True" +msgstr "" + +#: ./doc/common/tables/cinder-zadara.xml51(td) +msgid "(BoolOpt) Automatically detach from servers on volume delete" +msgstr "" + +#: ./doc/common/tables/cinder-zadara.xml54(td) +msgid "zadara_vpsa_ip = None" +msgstr "" + +#: ./doc/common/tables/cinder-zadara.xml55(td) +msgid "(StrOpt) Management IP of Zadara VPSA" +msgstr "" + +#: ./doc/common/tables/cinder-zadara.xml58(td) +msgid "zadara_vpsa_poolname = None" +msgstr "" + +#: ./doc/common/tables/cinder-zadara.xml59(td) +msgid "(StrOpt) Name of VPSA storage pool for volumes" +msgstr "" + +#: ./doc/common/tables/cinder-zadara.xml62(td) +msgid "zadara_vpsa_port = None" +msgstr "" + +#: ./doc/common/tables/cinder-zadara.xml63(td) +msgid "(StrOpt) Zadara VPSA port number" +msgstr "" + +#: ./doc/common/tables/cinder-zadara.xml66(td) +msgid "zadara_vpsa_use_ssl = False" +msgstr "" + +#: ./doc/common/tables/cinder-zadara.xml67(td) +msgid "(BoolOpt) Use SSL connection" +msgstr "" + +#: ./doc/common/tables/swift-account-server-account-reaper.xml7(literal) +msgid "[account-reaper]" +msgstr "" + +#: ./doc/common/tables/swift-account-server-account-reaper.xml18(td) +msgid "log_name = account-reaper" +msgstr "" + +#: ./doc/common/tables/swift-account-server-account-reaper.xml33(td) +msgid "interval = 3600" +msgstr "" + +#: ./doc/common/tables/swift-account-server-account-reaper.xml42(td) +msgid "delay_reaping = 0" +msgstr "" + +#: ./doc/common/tables/swift-account-server-account-reaper.xml42(td) +msgid "" +"Normally, the reaper begins deleting account information for deleted " +"accounts immediately; you can set this to delay its work however. The value " +"is in seconds, 2592000 = 30 days, for example. bind to giving up worker can " +"process simultaneously (it will actually accept(2) N + 1). Setting this to " +"one (1) will only handle one request at a time, without accepting another " +"request concurrently. By increasing the number of workers to a much higher " +"value, one can reduce the impact of slow file system operations in one " +"request from negatively impacting other requests." +msgstr "" + +#: ./doc/common/tables/swift-account-server-account-reaper.xml45(td) +msgid "reap_warn_after = 2592000" +msgstr "" + +#: ./doc/common/tables/nova-quota.xml22(td) +msgid "bandwidth_poll_interval = 600" +msgstr "" + +#: ./doc/common/tables/nova-quota.xml23(td) +msgid "(IntOpt) interval to pull bandwidth usage info" +msgstr "" + +#: ./doc/common/tables/nova-quota.xml26(td) +msgid "enable_network_quota = False" +msgstr "" + +#: ./doc/common/tables/nova-quota.xml27(td) +msgid "(BoolOpt) Enables or disables quota checking for tenant networks" +msgstr "" + +#: ./doc/common/tables/nova-quota.xml30(td) +msgid "quota_cores = 20" +msgstr "" + +#: ./doc/common/tables/nova-quota.xml31(td) +msgid "(IntOpt) number of instance cores allowed per project" +msgstr "" + +#: ./doc/common/tables/nova-quota.xml34(td) +msgid "quota_driver = nova.quota.DbQuotaDriver" +msgstr "" + +#: ./doc/common/tables/nova-quota.xml38(td) +msgid "quota_fixed_ips = -1" +msgstr "" + +#: ./doc/common/tables/nova-quota.xml39(td) +msgid "" +"(IntOpt) number of fixed ips allowed per project (this should be at least " +"the number of instances allowed)" +msgstr "" + +#: ./doc/common/tables/nova-quota.xml42(td) +msgid "quota_floating_ips = 10" +msgstr "" + +#: ./doc/common/tables/nova-quota.xml43(td) +msgid "(IntOpt) number of floating ips allowed per project" +msgstr "" + +#: ./doc/common/tables/nova-quota.xml46(td) +msgid "quota_injected_file_content_bytes = 10240" +msgstr "" + +#: ./doc/common/tables/nova-quota.xml47(td) +msgid "(IntOpt) number of bytes allowed per injected file" +msgstr "" + +#: ./doc/common/tables/nova-quota.xml50(td) +msgid "quota_injected_file_path_bytes = 255" +msgstr "" + +#: ./doc/common/tables/nova-quota.xml51(td) +msgid "(IntOpt) number of bytes allowed per injected file path" +msgstr "" + +#: ./doc/common/tables/nova-quota.xml54(td) +msgid "quota_injected_files = 5" +msgstr "" + +#: ./doc/common/tables/nova-quota.xml55(td) +msgid "(IntOpt) number of injected files allowed" +msgstr "" + +#: ./doc/common/tables/nova-quota.xml58(td) +msgid "quota_instances = 10" +msgstr "" + +#: ./doc/common/tables/nova-quota.xml59(td) +msgid "(IntOpt) number of instances allowed per project" +msgstr "" + +#: ./doc/common/tables/nova-quota.xml62(td) +msgid "quota_key_pairs = 100" +msgstr "" + +#: ./doc/common/tables/nova-quota.xml63(td) +msgid "(IntOpt) number of key pairs per user" +msgstr "" + +#: ./doc/common/tables/nova-quota.xml66(td) +msgid "quota_metadata_items = 128" +msgstr "" + +#: ./doc/common/tables/nova-quota.xml67(td) +msgid "(IntOpt) number of metadata items allowed per instance" +msgstr "" + +#: ./doc/common/tables/nova-quota.xml70(td) +msgid "quota_ram = 51200" +msgstr "" + +#: ./doc/common/tables/nova-quota.xml71(td) +msgid "(IntOpt) megabytes of instance ram allowed per project" +msgstr "" + +#: ./doc/common/tables/nova-quota.xml74(td) +msgid "quota_security_group_rules = 20" +msgstr "" + +#: ./doc/common/tables/nova-quota.xml75(td) +msgid "(IntOpt) number of security rules per security group" +msgstr "" + +#: ./doc/common/tables/nova-quota.xml78(td) +msgid "quota_security_groups = 10" +msgstr "" + +#: ./doc/common/tables/nova-quota.xml79(td) +msgid "(IntOpt) number of security groups per project" +msgstr "" + +#: ./doc/common/tables/nova-quota.xml85(td) +msgid "bandwidth_update_interval = 600" +msgstr "" + +#: ./doc/common/tables/nova-quota.xml86(td) +msgid "(IntOpt) Seconds between bandwidth updates for cells." +msgstr "" + +#: ./doc/common/tables/nova-conductor.xml8(caption) +msgid "Description of configuration options for conductor" +msgstr "" + +#: ./doc/common/tables/nova-conductor.xml22(td) +msgid "migrate_max_retries = -1" +msgstr "" + +#: ./doc/common/tables/nova-conductor.xml23(td) +msgid "" +"(IntOpt) Number of times to retry live-migration before failing. If == -1, " +"try until out of hosts. If == 0, only try once, no retries." +msgstr "" + +#: ./doc/common/tables/nova-conductor.xml26(th) +msgid "[conductor]" +msgstr "" + +#: ./doc/common/tables/nova-conductor.xml29(td) +msgid "manager = nova.conductor.manager.ConductorManager" +msgstr "" + +#: ./doc/common/tables/nova-conductor.xml30(td) +msgid "(StrOpt) full class name for the Manager for conductor" +msgstr "" + +#: ./doc/common/tables/nova-conductor.xml33(td) +msgid "topic = conductor" +msgstr "" + +#: ./doc/common/tables/nova-conductor.xml34(td) +msgid "(StrOpt) the topic conductor nodes listen on" +msgstr "" + +#: ./doc/common/tables/nova-conductor.xml37(td) +msgid "use_local = False" +msgstr "" + +#: ./doc/common/tables/nova-conductor.xml38(td) +msgid "(BoolOpt) Perform nova-conductor operations locally" +msgstr "" + +#: ./doc/common/tables/nova-conductor.xml41(td) +msgid "workers = None" +msgstr "" + +#: ./doc/common/tables/nova-conductor.xml42(td) +msgid "(IntOpt) Number of workers for OpenStack Conductor service" +msgstr "" + +#: ./doc/common/tables/nova-compute.xml22(td) +msgid "compute_available_monitors = ['nova.compute.monitors.all_monitors']" +msgstr "" + +#: ./doc/common/tables/nova-compute.xml23(td) +msgid "" +"(MultiStrOpt) Monitor classes available to the compute which may be " +"specified more than once." +msgstr "" + +#: ./doc/common/tables/nova-compute.xml26(td) +msgid "compute_driver = None" +msgstr "" + +#: ./doc/common/tables/nova-compute.xml27(td) +msgid "" +"(StrOpt) Driver to use for controlling virtualization. Options include: " +"libvirt.LibvirtDriver, xenapi.XenAPIDriver, fake.FakeDriver, " +"baremetal.BareMetalDriver, vmwareapi.VMwareESXDriver, " +"vmwareapi.VMwareVCDriver" +msgstr "" + +#: ./doc/common/tables/nova-compute.xml30(td) +msgid "compute_manager = nova.compute.manager.ComputeManager" +msgstr "" + +#: ./doc/common/tables/nova-compute.xml31(td) +msgid "(StrOpt) full class name for the Manager for compute" +msgstr "" + +#: ./doc/common/tables/nova-compute.xml34(td) +msgid "compute_monitors =" +msgstr "" + +#: ./doc/common/tables/nova-compute.xml35(td) +msgid "" +"(ListOpt) A list of monitors that can be used for getting compute metrics." +msgstr "" + +#: ./doc/common/tables/nova-compute.xml38(td) +msgid "compute_stats_class = nova.compute.stats.Stats" +msgstr "" + +#: ./doc/common/tables/nova-compute.xml39(td) +msgid "(StrOpt) Class that will manage stats for the local compute host" +msgstr "" + +#: ./doc/common/tables/nova-compute.xml42(td) +msgid "console_host = oslo" +msgstr "" + +#: ./doc/common/tables/nova-compute.xml43(td) +msgid "" +"(StrOpt) Console proxy host to use to connect to instances on this host." +msgstr "" + +#: ./doc/common/tables/nova-compute.xml46(td) +msgid "console_manager = nova.console.manager.ConsoleProxyManager" +msgstr "" + +#: ./doc/common/tables/nova-compute.xml47(td) +msgid "(StrOpt) full class name for the Manager for console proxy" +msgstr "" + +#: ./doc/common/tables/nova-compute.xml50(td) +msgid "default_flavor = m1.small" +msgstr "" + +#: ./doc/common/tables/nova-compute.xml51(td) +msgid "" +"(StrOpt) default flavor to use for the EC2 API only. The Nova API does not " +"support a default flavor." +msgstr "" + +#: ./doc/common/tables/nova-compute.xml62(td) +msgid "enable_instance_password = True" +msgstr "" + +#: ./doc/common/tables/nova-compute.xml63(td) +msgid "" +"(BoolOpt) Enables returning of the instance password by the relevant server " +"API calls such as create, rebuild or rescue, If the hypervisor does not " +"support password injection then the password returned will not be correct" +msgstr "" + +#: ./doc/common/tables/nova-compute.xml66(td) +msgid "heal_instance_info_cache_interval = 60" +msgstr "" + +#: ./doc/common/tables/nova-compute.xml67(td) +msgid "" +"(IntOpt) Number of seconds between instance info_cache self healing updates" +msgstr "" + +#: ./doc/common/tables/nova-compute.xml70(td) +msgid "host_state_interval = 120" +msgstr "" + +#: ./doc/common/tables/nova-compute.xml71(td) +msgid "(IntOpt) Interval in seconds for querying the host status" +msgstr "" + +#: ./doc/common/tables/nova-compute.xml74(td) +msgid "image_cache_manager_interval = 2400" +msgstr "" + +#: ./doc/common/tables/nova-compute.xml75(td) +msgid "" +"(IntOpt) Number of seconds to wait between runs of the image cache manager" +msgstr "" + +#: ./doc/common/tables/nova-compute.xml78(td) +msgid "image_cache_subdirectory_name = _base" +msgstr "" + +#: ./doc/common/tables/nova-compute.xml79(td) +msgid "" +"(StrOpt) Where cached images are stored under $instances_path. This is NOT " +"the full path - just a folder name. For per-compute-host cached images, set " +"to _base_$my_ip" +msgstr "" + +#: ./doc/common/tables/nova-compute.xml82(td) +msgid "instance_build_timeout = 0" +msgstr "" + +#: ./doc/common/tables/nova-compute.xml83(td) +msgid "" +"(IntOpt) Amount of time in seconds an instance can be in BUILD before going " +"into ERROR status.Set to 0 to disable." +msgstr "" + +#: ./doc/common/tables/nova-compute.xml86(td) +msgid "instance_delete_interval = 300" +msgstr "" + +#: ./doc/common/tables/nova-compute.xml87(td) +msgid "(IntOpt) Interval in seconds for retrying failed instance file deletes" +msgstr "" + +#: ./doc/common/tables/nova-compute.xml90(td) +msgid "instance_usage_audit = False" +msgstr "" + +#: ./doc/common/tables/nova-compute.xml91(td) +msgid "(BoolOpt) Generate periodic compute.instance.exists notifications" +msgstr "" + +#: ./doc/common/tables/nova-compute.xml94(td) +msgid "instance_usage_audit_period = month" +msgstr "" + +#: ./doc/common/tables/nova-compute.xml95(td) +msgid "" +"(StrOpt) time period to generate instance usages for. Time period must be " +"hour, day, month or year" +msgstr "" + +#: ./doc/common/tables/nova-compute.xml98(td) +msgid "instances_path = $state_path/instances" +msgstr "" + +#: ./doc/common/tables/nova-compute.xml99(td) +msgid "(StrOpt) where instances are stored on disk" +msgstr "" + +#: ./doc/common/tables/nova-compute.xml102(td) +msgid "maximum_instance_delete_attempts = 5" +msgstr "" + +#: ./doc/common/tables/nova-compute.xml103(td) +msgid "(IntOpt) The number of times to attempt to reap an instance's files." +msgstr "" + +#: ./doc/common/tables/nova-compute.xml106(td) +msgid "reboot_timeout = 0" +msgstr "" + +#: ./doc/common/tables/nova-compute.xml107(td) +msgid "" +"(IntOpt) Automatically hard reboot an instance if it has been stuck in a " +"rebooting state longer than N seconds. Set to 0 to disable." +msgstr "" + +#: ./doc/common/tables/nova-compute.xml110(td) +msgid "reclaim_instance_interval = 0" +msgstr "" + +#: ./doc/common/tables/nova-compute.xml111(td) +msgid "(IntOpt) Interval in seconds for reclaiming deleted instances" +msgstr "" + +#: ./doc/common/tables/nova-compute.xml114(td) +msgid "resize_confirm_window = 0" +msgstr "" + +#: ./doc/common/tables/nova-compute.xml115(td) +msgid "" +"(IntOpt) Automatically confirm resizes after N seconds. Set to 0 to disable." +msgstr "" + +#: ./doc/common/tables/nova-compute.xml118(td) +msgid "resume_guests_state_on_host_boot = False" +msgstr "" + +#: ./doc/common/tables/nova-compute.xml119(td) +msgid "" +"(BoolOpt) Whether to start guests that were running before the host rebooted" +msgstr "" + +#: ./doc/common/tables/nova-compute.xml122(td) +msgid "running_deleted_instance_action = reap" +msgstr "" + +#: ./doc/common/tables/nova-compute.xml123(td) +msgid "" +"(StrOpt) Action to take if a running deleted instance is detected.Valid " +"options are 'noop', 'log', 'shutdown', or 'reap'. Set to 'noop' to take no " +"action." +msgstr "" + +#: ./doc/common/tables/nova-compute.xml126(td) +msgid "running_deleted_instance_poll_interval = 1800" +msgstr "" + +#: ./doc/common/tables/nova-compute.xml127(td) +msgid "(IntOpt) Number of seconds to wait between runs of the cleanup task." +msgstr "" + +#: ./doc/common/tables/nova-compute.xml130(td) +msgid "running_deleted_instance_timeout = 0" +msgstr "" + +#: ./doc/common/tables/nova-compute.xml131(td) +msgid "" +"(IntOpt) Number of seconds after being deleted when a running instance " +"should be considered eligible for cleanup." +msgstr "" + +#: ./doc/common/tables/nova-compute.xml134(td) +msgid "shelved_offload_time = 0" +msgstr "" + +#: ./doc/common/tables/nova-compute.xml135(td) +msgid "" +"(IntOpt) Time in seconds before a shelved instance is eligible for removing " +"from a host. -1 never offload, 0 offload when shelved" +msgstr "" + +#: ./doc/common/tables/nova-compute.xml138(td) +msgid "shelved_poll_interval = 3600" +msgstr "" + +#: ./doc/common/tables/nova-compute.xml139(td) +msgid "(IntOpt) Interval in seconds for polling shelved instances to offload" +msgstr "" + +#: ./doc/common/tables/nova-compute.xml142(td) +msgid "sync_power_state_interval = 600" +msgstr "" + +#: ./doc/common/tables/nova-compute.xml143(td) +msgid "" +"(IntOpt) interval to sync power states between the database and the " +"hypervisor" +msgstr "" + +#: ./doc/common/tables/swift-proxy-server-filter-domain_remap.xml7(literal) +msgid "[filter:domain_remap]" +msgstr "" + +#: ./doc/common/tables/swift-proxy-server-filter-domain_remap.xml18(td) +msgid "use = egg:swift#domain_remap" +msgstr "" + +#: ./doc/common/tables/swift-proxy-server-filter-domain_remap.xml21(td) +msgid "set log_name = domain_remap" +msgstr "" + +#: ./doc/common/tables/swift-proxy-server-filter-domain_remap.xml39(td) +msgid "path_root = v1" +msgstr "" + +#: ./doc/common/tables/swift-proxy-server-filter-domain_remap.xml39(td) +msgid "Root path" +msgstr "" + +#: ./doc/common/tables/swift-proxy-server-filter-domain_remap.xml42(td) +msgid "reseller_prefixes = AUTH" +msgstr "" + +#: ./doc/common/tables/swift-proxy-server-filter-domain_remap.xml42(td) +msgid "Reseller prefix" +msgstr "" + +#: ./doc/common/tables/neutron-hyperv.xml24(td) +msgid "(StrOpt) Network type for tenant networks (local, flat, vlan or none)" +msgstr "" + +#: ./doc/common/tables/cinder-storage_xen.xml8(caption) +msgid "Description of configuration options for storage_xen" +msgstr "" + +#: ./doc/common/tables/cinder-storage_xen.xml22(td) +msgid "xenapi_connection_password = None" +msgstr "" + +#: ./doc/common/tables/cinder-storage_xen.xml23(td) +msgid "(StrOpt) Password for XenAPI connection" +msgstr "" + +#: ./doc/common/tables/cinder-storage_xen.xml26(td) +msgid "xenapi_connection_url = None" +msgstr "" + +#: ./doc/common/tables/cinder-storage_xen.xml27(td) +msgid "(StrOpt) URL for XenAPI connection" +msgstr "" + +#: ./doc/common/tables/cinder-storage_xen.xml30(td) +msgid "xenapi_connection_username = root" +msgstr "" + +#: ./doc/common/tables/cinder-storage_xen.xml31(td) +msgid "(StrOpt) Username for XenAPI connection" +msgstr "" + +#: ./doc/common/tables/cinder-storage_xen.xml34(td) +msgid "xenapi_nfs_server = None" +msgstr "" + +#: ./doc/common/tables/cinder-storage_xen.xml35(td) +msgid "(StrOpt) NFS server to be used by XenAPINFSDriver" +msgstr "" + +#: ./doc/common/tables/cinder-storage_xen.xml38(td) +msgid "xenapi_nfs_serverpath = None" +msgstr "" + +#: ./doc/common/tables/cinder-storage_xen.xml39(td) +msgid "(StrOpt) Path of exported NFS, used by XenAPINFSDriver" +msgstr "" + +#: ./doc/common/tables/cinder-storage_xen.xml42(td) +msgid "xenapi_sr_base_path = /var/run/sr-mount" +msgstr "" + +#: ./doc/common/tables/nova-xvpnvncproxy.xml8(caption) +msgid "Description of configuration options for xvpnvncproxy" +msgstr "" + +#: ./doc/common/tables/nova-xvpnvncproxy.xml22(td) +msgid "xvpvncproxy_base_url = http://127.0.0.1:6081/console" +msgstr "" + +#: ./doc/common/tables/nova-xvpnvncproxy.xml23(td) +msgid "" +"(StrOpt) location of nova xvp vnc console proxy, in the form " +"\"http://127.0.0.1:6081/console\"" +msgstr "" + +#: ./doc/common/tables/nova-xvpnvncproxy.xml26(td) +msgid "xvpvncproxy_host = 0.0.0.0" +msgstr "" + +#: ./doc/common/tables/nova-xvpnvncproxy.xml27(td) +msgid "(StrOpt) Address that the XCP VNC proxy should bind to" +msgstr "" + +#: ./doc/common/tables/nova-xvpnvncproxy.xml30(td) +msgid "xvpvncproxy_port = 6081" +msgstr "" + +#: ./doc/common/tables/nova-xvpnvncproxy.xml31(td) +msgid "(IntOpt) Port that the XCP VNC proxy should bind to" +msgstr "" + +#. Put one translator per line, in the form of NAME , YEAR1, YEAR2 +#: ./doc/common/tables/nova-xvpnvncproxy.xml0(None) +msgid "translator-credits" +msgstr "" diff --git a/doc/config-reference/locale/config-reference.pot b/doc/config-reference/locale/config-reference.pot new file mode 100644 index 0000000000..71c0620205 --- /dev/null +++ b/doc/config-reference/locale/config-reference.pot @@ -0,0 +1,7292 @@ +msgid "" +msgstr "" +"Project-Id-Version: PACKAGE VERSION\n" +"POT-Creation-Date: 2014-01-30 06:24+0000\n" +"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n" +"Last-Translator: FULL NAME \n" +"Language-Team: LANGUAGE \n" +"MIME-Version: 1.0\n" +"Content-Type: text/plain; charset=UTF-8\n" +"Content-Transfer-Encoding: 8bit\n" + +#: ./doc/config-reference/ch_imageservice.xml:10(title) +msgid "Image Service" +msgstr "" + +#: ./doc/config-reference/ch_imageservice.xml:11(para) +msgid "Compute relies on an external image service to store virtual machine images and maintain a catalog of available images. By default, Compute is configured to use the OpenStack Image Service (Glance), which is currently the only supported image service." +msgstr "" + +#: ./doc/config-reference/ch_imageservice.xml:19(para) +msgid "If your installation requires euca2ools to register new images, you must run the nova-objectstore service. This service provides an Amazon S3 front-end for Glance, which is required by euca2ools." +msgstr "" + +#: ./doc/config-reference/ch_imageservice.xml:26(para) +msgid "You can modify many of the OpenStack Image Catalogue and Delivery Service. The following tables provide a comprehensive list." +msgstr "" + +#: ./doc/config-reference/ch_config-overview.xml:6(title) +msgid "OpenStack configuration overview" +msgstr "" + +#: ./doc/config-reference/ch_config-overview.xml:7(para) +msgid "OpenStack is a collection of open source project components that enable setting up cloud services. Each component uses similar configuration techniques and a common framework for INI file options." +msgstr "" + +#: ./doc/config-reference/ch_config-overview.xml:12(para) +msgid "This guide pulls together multiple references and configuration options for the following OpenStack components:" +msgstr "" + +#: ./doc/config-reference/ch_config-overview.xml:16(para) +msgid "OpenStack Identity" +msgstr "" + +#: ./doc/config-reference/ch_config-overview.xml:17(para) +msgid "OpenStack Compute" +msgstr "" + +#: ./doc/config-reference/ch_config-overview.xml:18(para) +msgid "OpenStack Image Service" +msgstr "" + +#: ./doc/config-reference/ch_config-overview.xml:19(para) +msgid "OpenStack Networking" +msgstr "" + +#: ./doc/config-reference/ch_config-overview.xml:20(para) +msgid "OpenStack Dashboard" +msgstr "" + +#: ./doc/config-reference/ch_config-overview.xml:21(para) +msgid "OpenStack Object Storage" +msgstr "" + +#: ./doc/config-reference/ch_config-overview.xml:22(para) +msgid "OpenStack Block Storage" +msgstr "" + +#: ./doc/config-reference/ch_computeconfigure.xml:6(title) +msgid "Compute" +msgstr "" + +#: ./doc/config-reference/ch_computeconfigure.xml:7(para) +msgid "The OpenStack Compute service is a cloud computing fabric controller, which is the main part of an IaaS system. You can use OpenStack Compute to host and manage cloud computing systems. This section describes the OpenStack Compute configuration options." +msgstr "" + +#: ./doc/config-reference/ch_computeconfigure.xml:12(para) +msgid "To configure your Compute installation, you must define configuration options in these files:" +msgstr "" + +#: ./doc/config-reference/ch_computeconfigure.xml:16(para) +msgid "nova.conf. Contains most of the Compute configuration options. Resides in the /etc/nova directory." +msgstr "" + +#: ./doc/config-reference/ch_computeconfigure.xml:21(para) +msgid "api-paste.ini. Defines Compute limits. Resides in the /etc/nova directory." +msgstr "" + +#: ./doc/config-reference/ch_computeconfigure.xml:26(para) +msgid "Related Image Service and Identity Service management configuration files." +msgstr "" + +#: ./doc/config-reference/ch_computeconfigure.xml:32(title) +msgid "Configure logging" +msgstr "" + +#: ./doc/config-reference/ch_computeconfigure.xml:33(para) +msgid "You can use nova.conf file to configure where Compute logs events, the level of logging, and log formats." +msgstr "" + +#: ./doc/config-reference/ch_computeconfigure.xml:36(para) +msgid "To customize log formats for OpenStack Compute, use these configuration option settings." +msgstr "" + +#: ./doc/config-reference/ch_computeconfigure.xml:41(title) +msgid "Configure authentication and authorization" +msgstr "" + +#: ./doc/config-reference/ch_computeconfigure.xml:42(para) +msgid "There are different methods of authentication for the OpenStack Compute project, including no authentication. The preferred system is the OpenStack Identity Service, code-named Keystone." +msgstr "" + +#: ./doc/config-reference/ch_computeconfigure.xml:46(para) +msgid "To customize authorization settings for Compute, see these configuration settings in nova.conf." +msgstr "" + +#: ./doc/config-reference/ch_computeconfigure.xml:49(para) +msgid "To customize certificate authority settings for Compute, see these configuration settings in nova.conf." +msgstr "" + +#: ./doc/config-reference/ch_computeconfigure.xml:53(para) +msgid "To customize Compute and the Identity service to use LDAP as a backend, refer to these configuration settings in nova.conf." +msgstr "" + +#: ./doc/config-reference/ch_computeconfigure.xml:62(title) +msgid "Configure resize" +msgstr "" + +#: ./doc/config-reference/ch_computeconfigure.xml:63(para) +msgid "Resize (or Server resize) is the ability to change the flavor of a server, thus allowing it to upscale or downscale according to user needs. For this feature to work properly, you might need to configure some underlying virt layers." +msgstr "" + +#: ./doc/config-reference/ch_computeconfigure.xml:68(title) ./doc/config-reference/compute/section_hypervisor_kvm.xml:5(title) +msgid "KVM" +msgstr "" + +#: ./doc/config-reference/ch_computeconfigure.xml:69(para) +msgid "Resize on KVM is implemented currently by transferring the images between compute nodes over ssh. For KVM you need hostnames to resolve properly and passwordless ssh access between your compute hosts. Direct access from one compute host to another is needed to copy the VM file across." +msgstr "" + +#: ./doc/config-reference/ch_computeconfigure.xml:74(para) +msgid "Cloud end users can find out how to resize a server by reading the OpenStack End User Guide." +msgstr "" + +#: ./doc/config-reference/ch_computeconfigure.xml:80(title) ./doc/config-reference/compute/section_compute-configure-migrations.xml:289(title) +msgid "XenServer" +msgstr "" + +#: ./doc/config-reference/ch_computeconfigure.xml:81(para) +msgid "To get resize to work with XenServer (and XCP), you need to establish a root trust between all hypervisor nodes and provide an /image mount point to your hypervisors dom0." +msgstr "" + +#: ./doc/config-reference/bk-config-ref.xml:6(title) ./doc/config-reference/bk-config-ref.xml:8(titleabbrev) +msgid "OpenStack Configuration Reference" +msgstr "" + +#: ./doc/config-reference/bk-config-ref.xml:16(orgname) ./doc/config-reference/bk-config-ref.xml:21(holder) +msgid "OpenStack Foundation" +msgstr "" + +#: ./doc/config-reference/bk-config-ref.xml:20(year) +msgid "2013" +msgstr "" + +#: ./doc/config-reference/bk-config-ref.xml:23(productname) +msgid "OpenStack" +msgstr "" + +#: ./doc/config-reference/bk-config-ref.xml:24(releaseinfo) +msgid "havana" +msgstr "" + +#: ./doc/config-reference/bk-config-ref.xml:28(remark) +msgid "Copyright details are filled in by the template." +msgstr "" + +#: ./doc/config-reference/bk-config-ref.xml:33(para) +msgid "This document is for system administrators who want to look up configuration options. It contains lists of configuration options available with OpenStack and uses auto-generation to generate options and the descriptions from the code for each project. It includes sample configuration files." +msgstr "" + +#: ./doc/config-reference/bk-config-ref.xml:43(date) +msgid "2014-01-09" +msgstr "" + +#: ./doc/config-reference/bk-config-ref.xml:47(para) +msgid "Removes content addressed in installation, merges duplicated content, and revises legacy references." +msgstr "" + +#: ./doc/config-reference/bk-config-ref.xml:55(date) +msgid "2013-10-17" +msgstr "" + +#: ./doc/config-reference/bk-config-ref.xml:59(para) +msgid "Havana release." +msgstr "" + +#: ./doc/config-reference/bk-config-ref.xml:65(date) +msgid "2013-08-16" +msgstr "" + +#: ./doc/config-reference/bk-config-ref.xml:69(para) +msgid "Moves Block Storage driver configuration information from the Block Storage Administration Guide to this reference." +msgstr "" + +#: ./doc/config-reference/bk-config-ref.xml:77(date) +msgid "2013-06-10" +msgstr "" + +#: ./doc/config-reference/bk-config-ref.xml:81(para) +msgid "Initial creation of Configuration Reference." +msgstr "" + +#: ./doc/config-reference/ch_blockstorageconfigure.xml:10(title) +msgid "Block Storage" +msgstr "" + +#: ./doc/config-reference/ch_blockstorageconfigure.xml:11(para) +msgid "The OpenStack Block Storage Service works with many different storage drivers that you can configure by using these instructions." +msgstr "" + +#: ./doc/config-reference/ch_blockstorageconfigure.xml:15(title) ./doc/config-reference/block-storage/drivers/emc-volume-driver.xml:192(title) +msgid "cinder.conf configuration file" +msgstr "" + +#: ./doc/config-reference/ch_blockstorageconfigure.xml:16(para) +msgid "The cinder.conf file is installed in /etc/cinder by default. When you manually install the Block Storage Service, the options in the cinder.conf file are set to default values." +msgstr "" + +#: ./doc/config-reference/ch_blockstorageconfigure.xml:20(para) +msgid "This example shows a typical cinder.conf file:" +msgstr "" + +#: ./doc/config-reference/ch_identityconfigure.xml:10(title) +msgid "Identity Service" +msgstr "" + +#: ./doc/config-reference/ch_identityconfigure.xml:11(para) +msgid "This chapter details the OpenStack Identity Service configuration options. For installation prerequisites and step-by-step walkthroughs, see the OpenStack Installation Guide for your distribution (docs.openstack.org) and Cloud Administrator Guide." +msgstr "" + +#: ./doc/config-reference/ch_objectstorageconfigure.xml:6(title) +msgid "Object Storage" +msgstr "" + +#: ./doc/config-reference/ch_objectstorageconfigure.xml:7(para) +msgid "OpenStack Object Storage uses multiple configuration files for multiple services and background daemons, and to manage server configurations. Default configuration options appear in the [DEFAULT] section. You can override the default values by setting values in the other sections." +msgstr "" + +#: ./doc/config-reference/ch_objectstorageconfigure.xml:17(title) +msgid "Object server configuration" +msgstr "" + +#: ./doc/config-reference/ch_objectstorageconfigure.xml:18(para) +msgid "Find an example object server configuration at etc/object-server.conf-sample in the source code repository." +msgstr "" + +#: ./doc/config-reference/ch_objectstorageconfigure.xml:21(para) ./doc/config-reference/ch_objectstorageconfigure.xml:48(para) ./doc/config-reference/ch_objectstorageconfigure.xml:78(para) ./doc/config-reference/ch_objectstorageconfigure.xml:105(para) +msgid "The available configuration options are:" +msgstr "" + +#: ./doc/config-reference/ch_objectstorageconfigure.xml:39(title) +msgid "Sample object server configuration file" +msgstr "" + +#: ./doc/config-reference/ch_objectstorageconfigure.xml:44(title) +msgid "Container server configuration" +msgstr "" + +#: ./doc/config-reference/ch_objectstorageconfigure.xml:45(para) +msgid "Find an example container server configuration at etc/container-server.conf-sample in the source code repository." +msgstr "" + +#: ./doc/config-reference/ch_objectstorageconfigure.xml:68(title) +msgid "Sample container server configuration file" +msgstr "" + +#: ./doc/config-reference/ch_objectstorageconfigure.xml:74(title) +msgid "Account server configuration" +msgstr "" + +#: ./doc/config-reference/ch_objectstorageconfigure.xml:75(para) +msgid "Find an example account server configuration at etc/account-server.conf-sample in the source code repository." +msgstr "" + +#: ./doc/config-reference/ch_objectstorageconfigure.xml:96(title) +msgid "Sample account server configuration file" +msgstr "" + +#: ./doc/config-reference/ch_objectstorageconfigure.xml:101(title) +msgid "Proxy server configuration" +msgstr "" + +#: ./doc/config-reference/ch_objectstorageconfigure.xml:102(para) +msgid "Find an example proxy server configuration at etc/proxy-server.conf-sample in the source code repository." +msgstr "" + +#: ./doc/config-reference/ch_objectstorageconfigure.xml:131(title) +msgid "Sample proxy server configuration file" +msgstr "" + +#: ./doc/config-reference/ch_dashboardconfigure.xml:6(title) +msgid "Dashboard" +msgstr "" + +#: ./doc/config-reference/ch_dashboardconfigure.xml:7(para) +msgid "This chapter describes how to configure the OpenStack dashboard with Apache web server." +msgstr "" + +#: ./doc/config-reference/ch_networkingconfigure.xml:10(title) +msgid "Networking" +msgstr "" + +#: ./doc/config-reference/ch_networkingconfigure.xml:11(para) +msgid "This chapter explains the OpenStack Networking configuration options. For installation prerequisites, steps, and use cases, see the OpenStack Installation Guide for your distribution (docs.openstack.org) and Cloud Administrator Guide." +msgstr "" + +#: ./doc/config-reference/compute/section_compute-configure-xen.xml:10(title) ./doc/config-reference/compute/section_compute-configure-xen.xml:75(title) +msgid "Xen configuration reference" +msgstr "" + +#: ./doc/config-reference/compute/section_compute-configure-xen.xml:11(para) +msgid "The following section discusses some commonly changed options in XenServer. The table below provides a complete reference of all configuration options available for configuring Xen with OpenStack." +msgstr "" + +#: ./doc/config-reference/compute/section_compute-configure-xen.xml:15(para) +msgid "The recommended way to use Xen with OpenStack is through the XenAPI driver. To enable the XenAPI driver, add the following configuration options /etc/nova/nova.conf and restart the nova-compute service:" +msgstr "" + +#: ./doc/config-reference/compute/section_compute-configure-xen.xml:23(para) +msgid "These connection details are used by the OpenStack Compute service to contact your hypervisor and are the same details you use to connect XenCenter, the XenServer management console, to your XenServer or XCP box." +msgstr "" + +#: ./doc/config-reference/compute/section_compute-configure-xen.xml:27(para) +msgid "The xenapi_connection_url is generally the management network IP address of the XenServer. Though it is possible to use the internal network IP Address (169.250.0.1) to contact XenAPI, this does not allow live migration between hosts, and other functionalities like host aggregates do not work." +msgstr "" + +#: ./doc/config-reference/compute/section_compute-configure-xen.xml:34(para) +msgid "It is possible to manage Xen using libvirt, though this is not well-tested or supported. To experiment using Xen through libvirt add the following configuration options /etc/nova/nova.conf: " +msgstr "" + +#: ./doc/config-reference/compute/section_compute-configure-xen.xml:42(title) ./doc/config-reference/networking/section_networking-options-reference.xml:19(title) +msgid "Agent" +msgstr "" + +#: ./doc/config-reference/compute/section_compute-configure-xen.xml:43(para) +msgid "If you don't have the guest agent on your VMs, it takes a long time for nova to decide the VM has successfully started. Generally a large timeout is required for Windows instances, bug you may want to tweak agent_version_timeout" +msgstr "" + +#: ./doc/config-reference/compute/section_compute-configure-xen.xml:48(title) +msgid "Firewall" +msgstr "" + +#: ./doc/config-reference/compute/section_compute-configure-xen.xml:49(para) +msgid "If using nova-network, IPTables is supported: Alternately, doing the isolation in Dom0: " +msgstr "" + +#: ./doc/config-reference/compute/section_compute-configure-xen.xml:56(title) +msgid "VNC proxy address" +msgstr "" + +#: ./doc/config-reference/compute/section_compute-configure-xen.xml:57(para) +msgid "Assuming you are talking to XenAPI through the host local management network, and XenServer is on the address: 169.254.0.1, you can use the following: vncserver_proxyclient_address=169.254.0.1" +msgstr "" + +#: ./doc/config-reference/compute/section_compute-configure-xen.xml:63(title) +msgid "Storage" +msgstr "" + +#: ./doc/config-reference/compute/section_compute-configure-xen.xml:71(para) +msgid "To use a XenServer pool, you must create the pool by using the Host Aggregates feature." +msgstr "" + +#: ./doc/config-reference/compute/section_compute-configure-xen.xml:64(para) +msgid "You can specify which Storage Repository to use with nova by looking at the following flag. The default is to use the local-storage setup by the default installer: Another good alternative is to use the \"default\" storage (for example if you have attached NFS or any other shared storage): " +msgstr "" + +#. When image changes, this message will be marked fuzzy or untranslated for you. +#. It doesn't matter what you translate it to: it's not used at all. +#: ./doc/config-reference/compute/section_introduction-to-xen.xml:127(None) +msgid "@@image: '../../common/figures/xenserver_architecture.png'; md5=8eb25be1693aa7865967ac7b07d3e563" +msgstr "" + +#: ./doc/config-reference/compute/section_introduction-to-xen.xml:7(title) +msgid "Xen, XenAPI, XenServer, and XCP" +msgstr "" + +#: ./doc/config-reference/compute/section_introduction-to-xen.xml:9(para) +msgid "This section describes Xen, XenAPI, XenServer, and XCP, their differences, and how to use them with OpenStack. After you understand how the Xen and KVM architectures differ, you can determine when to use each architecture in your OpenStack cloud." +msgstr "" + +#: ./doc/config-reference/compute/section_introduction-to-xen.xml:15(title) +msgid "Xen terminology" +msgstr "" + +#: ./doc/config-reference/compute/section_introduction-to-xen.xml:16(para) +msgid "Xen. A hypervisor that provides the fundamental isolation between virtual machines. Xen is open source (GPLv2) and is managed by Xen.org, an cross-industry organization." +msgstr "" + +#: ./doc/config-reference/compute/section_introduction-to-xen.xml:20(para) +msgid "Xen is a component of many different products and projects. The hypervisor itself is very similar across all these projects, but the way that it is managed can be different, which can cause confusion if you're not clear which tool stack you are using. Make sure you know what tool stack you want before you get started." +msgstr "" + +#: ./doc/config-reference/compute/section_introduction-to-xen.xml:26(para) +msgid "Xen Cloud Platform (XCP). An open source (GPLv2) tool stack for Xen. It is designed specifically as a platform for enterprise and cloud computing, and is well integrated with OpenStack. XCP is available both as a binary distribution, installed from an iso, and from Linux distributions, such as xcp-xapi in Ubuntu. The current versions of XCP available in Linux distributions do not yet include all the features available in the binary distribution of XCP." +msgstr "" + +#: ./doc/config-reference/compute/section_introduction-to-xen.xml:38(para) +msgid "Citrix XenServer. A commercial product. It is based on XCP, and exposes the same tool stack and management API. As an analogy, think of XenServer being based on XCP in the way that Red Hat Enterprise Linux is based on Fedora. XenServer has a free version (which is very similar to XCP) and paid-for versions with additional features enabled. Citrix provides support for XenServer, but as of July 2012, they do not provide any support for XCP. For a comparison between these products see the XCP Feature Matrix." +msgstr "" + +#: ./doc/config-reference/compute/section_introduction-to-xen.xml:50(para) +msgid "Both XenServer and XCP include Xen, Linux, and the primary control daemon known as xapi." +msgstr "" + +#: ./doc/config-reference/compute/section_introduction-to-xen.xml:53(para) +msgid "The API shared between XCP and XenServer is called XenAPI. OpenStack usually refers to XenAPI, to indicate that the integration works equally well on XCP and XenServer. Sometimes, a careless person will refer to XenServer specifically, but you can be reasonably confident that anything that works on XenServer will also work on the latest version of XCP. Read the XenAPI Object Model Overview for definitions of XenAPI specific terms such as SR, VDI, VIF and PIF." +msgstr "" + +#: ./doc/config-reference/compute/section_introduction-to-xen.xml:66(title) +msgid "Privileged and unprivileged domains" +msgstr "" + +#: ./doc/config-reference/compute/section_introduction-to-xen.xml:67(para) +msgid "A Xen host runs a number of virtual machines, VMs, or domains (the terms are synonymous on Xen). One of these is in charge of running the rest of the system, and is known as \"domain 0,\" or \"dom0.\" It is the first domain to boot after Xen, and owns the storage and networking hardware, the device drivers, and the primary control software. Any other VM is unprivileged, and are known as a \"domU\" or \"guest\". All customer VMs are unprivileged of course, but you should note that on Xen the OpenStack control software (nova-compute) also runs in a domU. This gives a level of security isolation between the privileged system software and the OpenStack software (much of which is customer-facing). This architecture is described in more detail later." +msgstr "" + +#: ./doc/config-reference/compute/section_introduction-to-xen.xml:83(para) +msgid "There is an ongoing project to split domain 0 into multiple privileged domains known as driver domains and stub domains. This would give even better separation between critical components. This technology is what powers Citrix XenClient RT, and is likely to be added into XCP in the next few years. However, the current architecture just has three levels of separation: dom0, the OpenStack domU, and the completely unprivileged customer VMs." +msgstr "" + +#: ./doc/config-reference/compute/section_introduction-to-xen.xml:96(title) +msgid "Paravirtualized versus hardware virtualized domains" +msgstr "" + +#: ./doc/config-reference/compute/section_introduction-to-xen.xml:98(para) +msgid "A Xen virtual machine can be paravirtualized (PV) or hardware virtualized (HVM). This refers to the interaction between Xen, domain 0, and the guest VM's kernel. PV guests are aware of the fact that they are virtualized and will co-operate with Xen and domain 0; this gives them better performance characteristics. HVM guests are not aware of their environment, and the hardware has to pretend that they are running on an unvirtualized machine. HVM guests do not need to modify the guest operating system, which is essential when running Windows." +msgstr "" + +#: ./doc/config-reference/compute/section_introduction-to-xen.xml:111(para) +msgid "In OpenStack, customer VMs may run in either PV or HVM mode. However, the OpenStack domU (that's the one running nova-compute) must be running in PV mode." +msgstr "" + +#: ./doc/config-reference/compute/section_introduction-to-xen.xml:119(title) +msgid "XenAPI Deployment Architecture" +msgstr "" + +#: ./doc/config-reference/compute/section_introduction-to-xen.xml:121(para) +msgid "When you deploy OpenStack on XCP or XenServer, you get something similar to this: " +msgstr "" + +#: ./doc/config-reference/compute/section_introduction-to-xen.xml:133(para) +msgid "The hypervisor: Xen" +msgstr "" + +#: ./doc/config-reference/compute/section_introduction-to-xen.xml:136(para) +msgid "Domain 0: runs xapi and some small pieces from OpenStack (some xapi plug-ins and network isolation rules). The majority of this is provided by XenServer or XCP (or yourself using Kronos)." +msgstr "" + +#: ./doc/config-reference/compute/section_introduction-to-xen.xml:143(para) +msgid "OpenStack VM: The nova-compute code runs in a paravirtualized virtual machine, running on the host under management. Each host runs a local instance of nova-compute. It will often also be running nova-network (depending on your network mode). In this case, nova-network is managing the addresses given to the tenant VMs through DHCP." +msgstr "" + +#: ./doc/config-reference/compute/section_introduction-to-xen.xml:155(para) +msgid "Nova uses the XenAPI Python library to talk to xapi, and it uses the Management Network to reach from the domU to dom0 without leaving the host." +msgstr "" + +#: ./doc/config-reference/compute/section_introduction-to-xen.xml:131(para) +msgid "Key things to note: " +msgstr "" + +#: ./doc/config-reference/compute/section_introduction-to-xen.xml:163(para) +msgid "The above diagram assumes FlatDHCP networking (the DevStack default)." +msgstr "" + +#: ./doc/config-reference/compute/section_introduction-to-xen.xml:169(para) +msgid "Management network - RabbitMQ, MySQL, etc. Please note that the VM images are downloaded by the XenAPI plug-ins, so make sure that the images can be downloaded through the management network. It usually means binding those services to the management interface." +msgstr "" + +#: ./doc/config-reference/compute/section_introduction-to-xen.xml:179(para) +msgid "Tenant network - controlled by nova-network. The parameters of this network depend on the networking model selected (Flat, Flat DHCP, VLAN)." +msgstr "" + +#: ./doc/config-reference/compute/section_introduction-to-xen.xml:186(para) +msgid "Public network - floating IPs, public API endpoints." +msgstr "" + +#: ./doc/config-reference/compute/section_introduction-to-xen.xml:167(para) +msgid "There are three main OpenStack Networks:" +msgstr "" + +#: ./doc/config-reference/compute/section_introduction-to-xen.xml:192(para) +msgid "The networks shown here must be connected to the corresponding physical networks within the data center. In the simplest case, three individual physical network cards could be used. It is also possible to use VLANs to separate these networks. Please note, that the selected configuration must be in line with the networking model selected for the cloud. (In case of VLAN networking, the physical channels have to be able to forward the tagged traffic.)" +msgstr "" + +#: ./doc/config-reference/compute/section_introduction-to-xen.xml:161(para) +msgid "Some notes on the networking: " +msgstr "" + +#: ./doc/config-reference/compute/section_introduction-to-xen.xml:207(title) +msgid "XenAPI pools" +msgstr "" + +#: ./doc/config-reference/compute/section_introduction-to-xen.xml:208(para) +msgid "The host-aggregates feature enables you to create pools of XenServer hosts to enable live migration when using shared storage. However, you cannot configure shared storage." +msgstr "" + +#: ./doc/config-reference/compute/section_introduction-to-xen.xml:214(title) +msgid "Further reading" +msgstr "" + +#: ./doc/config-reference/compute/section_introduction-to-xen.xml:218(para) +msgid "Citrix XenServer official documentation: http://docs.vmd.citrix.com/XenServer." +msgstr "" + +#: ./doc/config-reference/compute/section_introduction-to-xen.xml:225(para) +msgid "What is Xen? by Xen.org: http://xen.org/files/Marketing/WhatisXen.pdf." +msgstr "" + +#: ./doc/config-reference/compute/section_introduction-to-xen.xml:231(para) +msgid "Xen Hypervisor project: http://xen.org/products/xenhyp.html." +msgstr "" + +#: ./doc/config-reference/compute/section_introduction-to-xen.xml:237(para) +msgid "XCP project: http://xen.org/products/cloudxen.html." +msgstr "" + +#: ./doc/config-reference/compute/section_introduction-to-xen.xml:243(para) +msgid "Further XenServer and OpenStack information: http://wiki.openstack.org/XenServer." +msgstr "" + +#: ./doc/config-reference/compute/section_introduction-to-xen.xml:215(para) +msgid "Here are some of the resources available to learn more about Xen: " +msgstr "" + +#: ./doc/config-reference/compute/section_hypervisor_baremetal.xml:6(title) +msgid "Bare metal driver" +msgstr "" + +#: ./doc/config-reference/compute/section_hypervisor_baremetal.xml:7(para) +msgid "The baremetal driver is a hypervisor driver for OpenStack Nova Compute. Within the OpenStack framework, it has the same role as the drivers for other hypervisors (libvirt, xen, etc), and yet it is presently unique in that the hardware is not virtualized - there is no hypervisor between the tenants and the physical hardware. It exposes hardware through the OpenStack APIs, using pluggable sub-drivers to deliver machine imaging (PXE) and power control (IPMI). With this, provisioning and management of physical hardware is accomplished by using common cloud APIs and tools, such as OpenStack Orchestration or salt-cloud. However, due to this unique situation, using the baremetal driver requires some additional preparation of its environment, the details of which are beyond the scope of this guide." +msgstr "" + +#: ./doc/config-reference/compute/section_hypervisor_baremetal.xml:20(para) +msgid "Some OpenStack Compute features are not implemented by the baremetal hypervisor driver. See the hypervisor support matrix for details." +msgstr "" + +#: ./doc/config-reference/compute/section_hypervisor_baremetal.xml:24(para) +msgid "For the Baremetal driver to be loaded and function properly, ensure that the following options are set in /etc/nova/nova.conf on your nova-compute hosts." +msgstr "" + +#: ./doc/config-reference/compute/section_hypervisor_baremetal.xml:34(para) +msgid "Many configuration options are specific to the Baremetal driver. Also, some additional steps are required, such as building the baremetal deploy ramdisk. See the main wiki page for details and implementation suggestions." +msgstr "" + +#: ./doc/config-reference/compute/section_compute-configure-backing-storage.xml:10(title) +msgid "Configure Compute backing storage" +msgstr "" + +#: ./doc/config-reference/compute/section_compute-configure-backing-storage.xml:11(para) +msgid "Backing Storage is the storage used to provide the expanded operating system image, and any ephemeral storage. Inside the virtual machine, this is normally presented as two virtual hard disks (for example, /dev/vda and /dev/vdb respectively). However, inside OpenStack, this can be derived from one of three methods: LVM, QCOW or RAW, chosen using the libvirt_images_type option in nova.conf on the compute node." +msgstr "" + +#: ./doc/config-reference/compute/section_compute-configure-backing-storage.xml:19(para) +msgid "QCOW is the default backing store. It uses a copy-on-write philosophy to delay allocation of storage until it is actually needed. This means that the space required for the backing of an image can be significantly less on the real disk than what seems available in the virtual machine operating system." +msgstr "" + +#: ./doc/config-reference/compute/section_compute-configure-backing-storage.xml:24(para) +msgid "RAW creates files without any sort of file formatting, effectively creating files with the plain binary one would normally see on a real disk. This can increase performance, but means that the entire size of the virtual disk is reserved on the physical disk." +msgstr "" + +#: ./doc/config-reference/compute/section_compute-configure-backing-storage.xml:29(para) +msgid "Local LVM volumes can also be used. Set libvirt_images_volume_group=nova_local where nova_local is the name of the LVM group you have created." +msgstr "" + +#: ./doc/config-reference/compute/section_compute-hypervisors.xml:10(title) +msgid "Hypervisors" +msgstr "" + +#: ./doc/config-reference/compute/section_compute-hypervisors.xml:11(para) +msgid "OpenStack Compute supports many hypervisors, which might make it difficult for you to choose one. Most installations use only one hypervisor. However you can use and to schedule to different hypervisors within the same installation. The following links help you choose a hypervisor. See http://wiki.openstack.org/HypervisorSupportMatrix for a detailed list of features and support across the hypervisors." +msgstr "" + +#: ./doc/config-reference/compute/section_compute-hypervisors.xml:22(para) +msgid "The following hypervisors are supported:" +msgstr "" + +#: ./doc/config-reference/compute/section_compute-hypervisors.xml:25(para) +msgid "KVM - Kernel-based Virtual Machine. The virtual disk formats that it supports is inherited from QEMU since it uses a modified QEMU program to launch the virtual machine. The supported formats include raw images, the qcow2, and VMware formats." +msgstr "" + +#: ./doc/config-reference/compute/section_compute-hypervisors.xml:34(para) +msgid "LXC - Linux Containers (through libvirt), use to run Linux-based virtual machines." +msgstr "" + +#: ./doc/config-reference/compute/section_compute-hypervisors.xml:39(para) +msgid "QEMU - Quick EMUlator, generally only used for development purposes." +msgstr "" + +#: ./doc/config-reference/compute/section_compute-hypervisors.xml:44(para) +msgid "UML - User Mode Linux, generally only used for development purposes." +msgstr "" + +#: ./doc/config-reference/compute/section_compute-hypervisors.xml:50(para) +msgid "VMWare vSphere 4.1 update 1 and newer, runs VMWare-based Linux and Windows images through a connection with a vCenter server or directly with an ESXi host." +msgstr "" + +#: ./doc/config-reference/compute/section_compute-hypervisors.xml:58(para) +msgid "Xen - XenServer, Xen Cloud Platform (XCP), use to run Linux or Windows virtual machines. You must install the nova-compute service in a para-virtualized VM." +msgstr "" + +#: ./doc/config-reference/compute/section_compute-hypervisors.xml:66(para) +msgid " Hyper-V - Server virtualization with Microsoft's Hyper-V, use to run Windows, Linux, and FreeBSD virtual machines. Runs nova-compute natively on the Windows virtualization platform." +msgstr "" + +#: ./doc/config-reference/compute/section_compute-hypervisors.xml:75(para) +msgid " Bare Metal - Not a hypervisor in the traditional sense, this driver provisions physical hardware through pluggable sub-drivers (for example, PXE for image deployment, and IPMI for power management)." +msgstr "" + +#: ./doc/config-reference/compute/section_compute-hypervisors.xml:83(para) +msgid "Dockeris an open-source engine which automates the deployment of >applications as highly portable, self-sufficient containers which are >independent of hardware, language, framework, packaging system and hosting >provider." +msgstr "" + +#: ./doc/config-reference/compute/section_compute-hypervisors.xml:92(title) +msgid "Hypervisor configuration basics" +msgstr "" + +#: ./doc/config-reference/compute/section_compute-hypervisors.xml:93(para) +msgid "The node where the nova-compute service is installed and running is the machine that runs all the virtual machines, referred to as the compute node in this guide." +msgstr "" + +#: ./doc/config-reference/compute/section_compute-hypervisors.xml:97(para) +msgid "By default, the selected hypervisor is KVM. To change to another hypervisor, change the libvirt_type option in nova.conf and restart the nova-compute service." +msgstr "" + +#: ./doc/config-reference/compute/section_compute-hypervisors.xml:103(para) +msgid "Here are the general nova.conf options that are used to configure the compute node's hypervisor. Specific options for particular hypervisors can be found in following sections." +msgstr "" + +#. When image changes, this message will be marked fuzzy or untranslated for you. +#. It doesn't matter what you translate it to: it's not used at all. +#: ./doc/config-reference/compute/section_compute-config-samples.xml:44(None) +msgid "@@image: '../../common/figures/SCH_5004_V00_NUAC-Network_mode_KVM_Flat_OpenStack.png'; md5=1e883ef27e5912b5c516d153b8844a28" +msgstr "" + +#. When image changes, this message will be marked fuzzy or untranslated for you. +#. It doesn't matter what you translate it to: it's not used at all. +#: ./doc/config-reference/compute/section_compute-config-samples.xml:83(None) +msgid "@@image: '../../common/figures/SCH_5005_V00_NUAC-Network_mode_XEN_Flat_OpenStack.png'; md5=3b151435a0fda3702d4fac5a964fac83" +msgstr "" + +#: ./doc/config-reference/compute/section_compute-config-samples.xml:9(title) +msgid "Example nova.conf configuration files" +msgstr "" + +#: ./doc/config-reference/compute/section_compute-config-samples.xml:11(para) +msgid "The following sections describe the configuration options in the nova.conf file. You must copy the nova.conf file to each compute node. The sample nova.conf files show examples of specific configurations." +msgstr "" + +#: ./doc/config-reference/compute/section_compute-config-samples.xml:17(title) +msgid "Small, private cloud" +msgstr "" + +#: ./doc/config-reference/compute/section_compute-config-samples.xml:18(para) +msgid "This example nova.conf file configures a small private cloud with cloud controller services, database server, and messaging server on the same server. In this case, CONTROLLER_IP represents the IP address of a central server, BRIDGE_INTERFACE represents the bridge such as br100, the NETWORK_INTERFACE represents an interface to your VLAN setup, and passwords are represented as DB_PASSWORD_COMPUTE for your Compute (nova) database password, and RABBIT PASSWORD represents the password to your message queue installation." +msgstr "" + +#: ./doc/config-reference/compute/section_compute-config-samples.xml:31(title) ./doc/config-reference/compute/section_compute-config-samples.xml:38(title) ./doc/config-reference/compute/section_compute-config-samples.xml:77(title) +msgid "KVM, Flat, MySQL, and Glance, OpenStack or EC2 API" +msgstr "" + +#: ./doc/config-reference/compute/section_compute-config-samples.xml:33(para) +msgid "This example nova.conf file, from an internal Rackspace test system, is used for demonstrations." +msgstr "" + +#: ./doc/config-reference/compute/section_compute-config-samples.xml:50(title) +msgid "XenServer, Flat networking, MySQL, and Glance, OpenStack API" +msgstr "" + +#: ./doc/config-reference/compute/section_compute-config-samples.xml:52(para) +msgid "This example nova.conf file is from an internal Rackspace test system." +msgstr "" + +#: ./doc/config-reference/compute/section_hypervisor_lxc.xml:6(title) +msgid "LXC (Linux containers)" +msgstr "" + +#: ./doc/config-reference/compute/section_hypervisor_lxc.xml:7(para) +msgid "LXC (also known as Linux containers) is a virtualization technology that works at the operating system level. This is different from hardware virtualization, the approach used by other hypervisors such as KVM, Xen, and VMWare. LXC (as currently implemented using libvirt in the nova project) is not a secure virtualization technology for multi-tenant environments (specifically, containers may affect resource quotas for other containers hosted on the same machine). Additional containment technologies, such as AppArmor, may be used to provide better isolation between containers, although this is not the case by default. For all these reasons, the choice of this virtualization technology is not recommended in production." +msgstr "" + +#: ./doc/config-reference/compute/section_hypervisor_lxc.xml:19(para) +msgid "If your compute hosts do not have hardware support for virtualization, LXC will likely provide better performance than QEMU. In addition, if your guests must access specialized hardware, such as GPUs, this might be easier to achieve with LXC than other hypervisors." +msgstr "" + +#: ./doc/config-reference/compute/section_hypervisor_lxc.xml:22(para) +msgid "Some OpenStack Compute features might be missing when running with LXC as the hypervisor. See the hypervisor support matrix for details." +msgstr "" + +#: ./doc/config-reference/compute/section_hypervisor_lxc.xml:25(para) +msgid "To enable LXC, ensure the following options are set in /etc/nova/nova.conf on all hosts running the nova-compute service." +msgstr "" + +#: ./doc/config-reference/compute/section_hypervisor_lxc.xml:30(para) +msgid "On Ubuntu 12.04, enable LXC support in OpenStack by installing the nova-compute-lxc package." +msgstr "" + +#: ./doc/config-reference/compute/section_compute-configure-db.xml:9(title) +msgid "Database configuration" +msgstr "" + +#: ./doc/config-reference/compute/section_compute-configure-db.xml:10(para) +msgid "You can configure OpenStack Compute to use any SQLAlchemy-compatible database. The database name is nova. The nova-conductor service is the only service that writes to the database. The other Compute services access the database through the nova-conductor service." +msgstr "" + +#: ./doc/config-reference/compute/section_compute-configure-db.xml:17(para) +msgid "To ensure that the database schema is current, run the following command:" +msgstr "" + +#: ./doc/config-reference/compute/section_compute-configure-db.xml:19(para) +msgid "If nova-conductor is not used, entries to the database are mostly written by the nova-scheduler service, although all services must be able to update entries in the database." +msgstr "" + +#: ./doc/config-reference/compute/section_compute-configure-db.xml:24(para) +msgid "In either case, use these settings to configure the connection string for the nova database." +msgstr "" + +#: ./doc/config-reference/compute/section_compute-options-reference.xml:6(title) ./doc/config-reference/block-storage/drivers/xenapi-nfs.xml:86(title) ./doc/config-reference/block-storage/drivers/hds-volume-driver.xml:309(caption) +msgid "Configuration options" +msgstr "" + +#: ./doc/config-reference/compute/section_compute-options-reference.xml:7(para) +msgid "For a complete list of all available configuration options for each OpenStack Compute service, run bin/nova-<servicename> --help." +msgstr "" + +#: ./doc/config-reference/compute/section_compute-configure-ipv6.xml:9(title) +msgid "Configure Compute to use IPv6 addresses" +msgstr "" + +#: ./doc/config-reference/compute/section_compute-configure-ipv6.xml:10(para) +msgid "You can configure Compute to use both IPv4 and IPv6 addresses for communication by putting it into a IPv4/IPv6 dual stack mode. In IPv4/IPv6 dual stack mode, instances can acquire their IPv6 global unicast address by stateless address auto configuration mechanism [RFC 4862/2462]. IPv4/IPv6 dual stack mode works with VlanManager and FlatDHCPManager networking modes. In VlanManager, different 64bit global routing prefix is used for each project. In FlatDHCPManager, one 64bit global routing prefix is used for all instances." +msgstr "" + +#: ./doc/config-reference/compute/section_compute-configure-ipv6.xml:18(para) +msgid "This configuration has been tested with VM images that have IPv6 stateless address auto configuration capability (must use EUI-64 address for stateless address auto configuration), a requirement for any VM you want to run with an IPv6 address. Each node that executes a nova-* service must have python-netaddr and radvd installed." +msgstr "" + +#: ./doc/config-reference/compute/section_compute-configure-ipv6.xml:24(para) +msgid "On all nova-nodes, install python-netaddr:" +msgstr "" + +#: ./doc/config-reference/compute/section_compute-configure-ipv6.xml:26(para) +msgid "On all nova-network nodes install radvd and configure IPv6 networking:" +msgstr "" + +#: ./doc/config-reference/compute/section_compute-configure-ipv6.xml:31(para) +msgid "Edit the nova.conf file on all nodes to set the use_ipv6 configuration option to True. Restart all nova- services." +msgstr "" + +#: ./doc/config-reference/compute/section_compute-configure-ipv6.xml:34(para) +msgid "When using the command you can add a fixed range for IPv6 addresses. You must specify public or private after the create parameter." +msgstr "" + +#: ./doc/config-reference/compute/section_compute-configure-ipv6.xml:36(replaceable) +msgid "fixed_range_v4" +msgstr "" + +#: ./doc/config-reference/compute/section_compute-configure-ipv6.xml:36(replaceable) +msgid "vlan_id" +msgstr "" + +#: ./doc/config-reference/compute/section_compute-configure-ipv6.xml:36(replaceable) +msgid "vpn_start" +msgstr "" + +#: ./doc/config-reference/compute/section_compute-configure-ipv6.xml:36(replaceable) +msgid "fixed_range_v6" +msgstr "" + +#: ./doc/config-reference/compute/section_compute-configure-ipv6.xml:37(para) +msgid "You can set IPv6 global routing prefix by using the --fixed_range_v6 parameter. The default is: fd00::/48. When you use FlatDHCPManager, the command uses the original value of --fixed_range_v6. When you use VlanManager, the command creates prefixes of subnet by incrementing subnet id. Guest VMs uses this prefix for generating their IPv6 global unicast address." +msgstr "" + +#: ./doc/config-reference/compute/section_compute-configure-ipv6.xml:43(para) +msgid "Here is a usage example for VlanManager:" +msgstr "" + +#: ./doc/config-reference/compute/section_compute-configure-ipv6.xml:45(para) +msgid "Here is a usage example for FlatDHCPManager:" +msgstr "" + +#: ./doc/config-reference/compute/section_compute-configure-console.xml:7(title) +msgid "Configure remote console access" +msgstr "" + +#. +#: ./doc/config-reference/compute/section_compute-configure-console.xml:9(para) +msgid "OpenStack has two main methods for providing a remote console or remote desktop access to guest Virtual Machines. They are VNC, and SPICE HTML5 and can be used either through the OpenStack dashboard and the command line. Best practice is to select one or the other to run." +msgstr "" + +#: ./doc/config-reference/compute/section_hypervisor_kvm.xml:6(para) +msgid "KVM is configured as the default hypervisor for Compute." +msgstr "" + +#: ./doc/config-reference/compute/section_hypervisor_kvm.xml:8(para) +msgid "This document contains several sections about hypervisor selection. If you are reading this document linearly, you do not want to load the KVM module before you install nova-compute. The nova-compute service depends on qemu-kvm, which installs /lib/udev/rules.d/45-qemu-kvm.rules, which sets the correct permissions on the /dev/kvm device node." +msgstr "" + +#: ./doc/config-reference/compute/section_hypervisor_kvm.xml:15(para) +msgid "To enable KVM explicitly, add the following configuration options to the /etc/nova/nova.conf file:" +msgstr "" + +#: ./doc/config-reference/compute/section_hypervisor_kvm.xml:19(para) +msgid "The KVM hypervisor supports the following virtual machine image formats:" +msgstr "" + +#: ./doc/config-reference/compute/section_hypervisor_kvm.xml:22(para) ./doc/config-reference/compute/section_hypervisor_qemu.xml:43(para) +msgid "Raw" +msgstr "" + +#: ./doc/config-reference/compute/section_hypervisor_kvm.xml:25(para) ./doc/config-reference/compute/section_hypervisor_qemu.xml:46(para) +msgid "QEMU Copy-on-write (qcow2)" +msgstr "" + +#: ./doc/config-reference/compute/section_hypervisor_kvm.xml:28(para) +msgid "QED Qemu Enhanced Disk" +msgstr "" + +#: ./doc/config-reference/compute/section_hypervisor_kvm.xml:31(para) ./doc/config-reference/compute/section_hypervisor_qemu.xml:49(para) +msgid "VMWare virtual machine disk format (vmdk)" +msgstr "" + +#: ./doc/config-reference/compute/section_hypervisor_kvm.xml:34(para) +msgid "This section describes how to enable KVM on your system. For more information, see the following distribution-specific documentation:" +msgstr "" + +#: ./doc/config-reference/compute/section_hypervisor_kvm.xml:38(para) +msgid "Fedora: Getting started with virtualization from the Fedora project wiki." +msgstr "" + +#: ./doc/config-reference/compute/section_hypervisor_kvm.xml:44(para) +msgid "Ubuntu: KVM/Installation from the Community Ubuntu documentation." +msgstr "" + +#: ./doc/config-reference/compute/section_hypervisor_kvm.xml:48(para) +msgid "Debian: Virtualization with KVM from the Debian handbook." +msgstr "" + +#: ./doc/config-reference/compute/section_hypervisor_kvm.xml:53(para) +msgid "RHEL: Installing virtualization packages on an existing Red Hat Enterprise Linux system from the Red Hat Enterprise Linux Virtualization Host Configuration and Guest Installation Guide." +msgstr "" + +#: ./doc/config-reference/compute/section_hypervisor_kvm.xml:60(para) +msgid "openSUSE: Installing KVM from the openSUSE Virtualization with KVM manual." +msgstr "" + +#: ./doc/config-reference/compute/section_hypervisor_kvm.xml:66(para) +msgid "SLES: Installing KVM from the SUSE Linux Enterprise Server Virtualization with KVM manual." +msgstr "" + +#: ./doc/config-reference/compute/section_hypervisor_kvm.xml:76(title) +msgid "Specify the CPU model of KVM guests" +msgstr "" + +#: ./doc/config-reference/compute/section_hypervisor_kvm.xml:77(para) +msgid "The Compute service enables you to control the guest CPU model that is exposed to KVM virtual machines. Use cases include:" +msgstr "" + +#: ./doc/config-reference/compute/section_hypervisor_kvm.xml:81(para) +msgid "To maximize performance of virtual machines by exposing new host CPU features to the guest" +msgstr "" + +#: ./doc/config-reference/compute/section_hypervisor_kvm.xml:85(para) +msgid "To ensure a consistent default CPU across all machines, removing reliance of variable QEMU defaults" +msgstr "" + +#: ./doc/config-reference/compute/section_hypervisor_kvm.xml:89(para) +msgid "In libvirt, the CPU is specified by providing a base CPU model name (which is a shorthand for a set of feature flags), a set of additional feature flags, and the topology (sockets/cores/threads). The libvirt KVM driver provides a number of standard CPU model names. These models are defined in the /usr/share/libvirt/cpu_map.xml file. Check this file to determine which models are supported by your local installation." +msgstr "" + +#: ./doc/config-reference/compute/section_hypervisor_kvm.xml:95(para) +msgid "Two Compute configuration options define which type of CPU model is exposed to the hypervisor when using KVM: libvirt_cpu_mode and libvirt_cpu_model." +msgstr "" + +#: ./doc/config-reference/compute/section_hypervisor_kvm.xml:98(para) +msgid "The libvirt_cpu_mode option can take one of the following values: none, host-passthrough, host-model, and custom." +msgstr "" + +#: ./doc/config-reference/compute/section_hypervisor_kvm.xml:102(title) +msgid "Host model (default for KVM & QEMU)" +msgstr "" + +#: ./doc/config-reference/compute/section_hypervisor_kvm.xml:103(para) +msgid "If your nova.conf file contains libvirt_cpu_mode=host-model, libvirt identifies the CPU model in /usr/share/libvirt/cpu_map.xml file that most closely matches the host, and requests additional CPU flags to complete the match. This configuration provides the maximum functionality and performance and maintains good reliability and compatibility if the guest is migrated to another host with slightly different host CPUs." +msgstr "" + +#: ./doc/config-reference/compute/section_hypervisor_kvm.xml:112(title) +msgid "Host pass through" +msgstr "" + +#: ./doc/config-reference/compute/section_hypervisor_kvm.xml:113(para) +msgid "If your nova.conf file contains libvirt_cpu_mode=host-passthrough, libvirt tells KVM to pass through the host CPU with no modifications. The difference to host-model, instead of just matching feature flags, every last detail of the host CPU is matched. This gives absolutely best performance, and can be important to some apps which check low level CPU details, but it comes at a cost with respect to migration: the guest can only be migrated to an exactly matching host CPU." +msgstr "" + +#: ./doc/config-reference/compute/section_hypervisor_kvm.xml:122(title) +msgid "Custom" +msgstr "" + +#: ./doc/config-reference/compute/section_hypervisor_kvm.xml:123(para) +msgid "If your nova.conf file contains libvirt_cpu_mode=custom, you can explicitly specify one of the supported named model using the libvirt_cpu_model configuration option. For example, to configure the KVM guests to expose Nehalem CPUs, your nova.conf file should contain:" +msgstr "" + +#: ./doc/config-reference/compute/section_hypervisor_kvm.xml:132(title) +msgid "None (default for all libvirt-driven hypervisors other than KVM & QEMU)" +msgstr "" + +#: ./doc/config-reference/compute/section_hypervisor_kvm.xml:134(para) +msgid "If your nova.conf file contains libvirt_cpu_mode=none, libvirt does not specify a CPU model. Instead, the hypervisor chooses the default model. This setting is equivalent to the Compute service behavior prior to the Folsom release." +msgstr "" + +#: ./doc/config-reference/compute/section_hypervisor_kvm.xml:141(title) +msgid "Guest agent support" +msgstr "" + +#: ./doc/config-reference/compute/section_hypervisor_kvm.xml:142(para) +msgid "With the Havana release, support for guest agents was added, allowing optional access between compute nods and guests through a socket, using the qmp protocol." +msgstr "" + +#: ./doc/config-reference/compute/section_hypervisor_kvm.xml:144(para) +msgid "To enable this feature, you must set hw_qemu_guest_agent=yes as a metadata parameter on the image you wish to use to create guest-agent-capable instances from. You can explicitly disable the feature by setting hw_qemu_guest_agent=no in the image metadata." +msgstr "" + +#: ./doc/config-reference/compute/section_hypervisor_kvm.xml:150(title) +msgid "KVM performance tweaks" +msgstr "" + +#: ./doc/config-reference/compute/section_hypervisor_kvm.xml:151(para) +msgid "The VHostNet kernel module improves network performance. To load the kernel module, run the following command as root:" +msgstr "" + +#: ./doc/config-reference/compute/section_hypervisor_kvm.xml:157(title) +msgid "Troubleshoot KVM" +msgstr "" + +#: ./doc/config-reference/compute/section_hypervisor_kvm.xml:158(para) +msgid "Trying to launch a new virtual machine instance fails with the ERRORstate, and the following error appears in the /var/log/nova/nova-compute.log file:" +msgstr "" + +#: ./doc/config-reference/compute/section_hypervisor_kvm.xml:162(para) +msgid "This message indicates that the KVM kernel modules were not loaded." +msgstr "" + +#: ./doc/config-reference/compute/section_hypervisor_kvm.xml:163(para) +msgid "If you cannot start VMs after installation without rebooting, the permissions might not be correct. This can happen if you load the KVM module before you install nova-compute. To check whether the group is set to kvm, run:" +msgstr "" + +#: ./doc/config-reference/compute/section_hypervisor_kvm.xml:168(para) +msgid "If it is not set to kvm, run:" +msgstr "" + +#: ./doc/config-reference/compute/section_hypervisor_docker.xml:6(title) +msgid "Docker driver" +msgstr "" + +#: ./doc/config-reference/compute/section_hypervisor_docker.xml:7(para) +msgid "The Docker driver is a hypervisor driver for OpenStack Compute, introduced with the Havana release. Docker is an open-source engine which automates the deployment of applications as highly portable, self-sufficient containers which are independent of hardware, language, framework, packaging system and hosting provider. Docker extends LXC with a high level API providing a lightweight virtualization solution that runs processes in isolation. It provides a way to automate software deployment in a secure and repeatable environment. A standard container in Docker contains a software component along with all of its dependencies - binaries, libraries, configuration files, scripts, virtualenvs, jars, gems and tarballs. Docker can be run on any x86_64 Linux kernel that supports cgroups and aufs. Docker is a way of managing LXC containers on a single machine. However used behind OpenStack Compute makes Docker much more powerful since it is then possible to manage several hosts which will then manage hundreds of containers. The current Docker project aims for full OpenStack compatibility. Containers don't aim to be a replacement for VMs, they are just complementary in the sense that they are better for specific use cases. Compute's support for VMs is currently advanced thanks to the variety of hypervisors running VMs. However it's not the case for containers even though libvirt/LXC is a good starting point. Docker aims to go the second level of integration." +msgstr "" + +#: ./doc/config-reference/compute/section_hypervisor_docker.xml:27(para) +msgid "Some OpenStack Compute features are not implemented by the docker driver. See the hypervisor support matrix for details." +msgstr "" + +#: ./doc/config-reference/compute/section_hypervisor_docker.xml:33(para) +msgid "To enable Docker, ensure the following options are set in /etc/nova/nova-compute.conf on all hosts running the nova-compute service. " +msgstr "" + +#: ./doc/config-reference/compute/section_hypervisor_docker.xml:37(para) +msgid "Glance also needs to be configured to support the Docker container format, in /etc/glance-api.conf: " +msgstr "" + +#: ./doc/config-reference/compute/section_compute-configure-service-groups.xml:15(title) +msgid "Configuring Compute Service Groups" +msgstr "" + +#: ./doc/config-reference/compute/section_compute-configure-service-groups.xml:16(para) +msgid "To effectively manage and utilize compute nodes, the Compute service must know their statuses. For example, when a user launches a new VM, the Compute scheduler should send the request to a live node (with enough capacity too, of course). From the Grizzly release and later, the Compute service queries the ServiceGroup API to get the node liveness information." +msgstr "" + +#: ./doc/config-reference/compute/section_compute-configure-service-groups.xml:21(para) +msgid "When a compute worker (running the nova-compute daemon) starts, it calls the join API to join the compute group, so that every service that is interested in the information (for example, the scheduler) can query the group membership or the status of a particular node. Internally, the ServiceGroup client driver automatically updates the compute worker status." +msgstr "" + +#: ./doc/config-reference/compute/section_compute-configure-service-groups.xml:27(para) +msgid "The following drivers are implemented: database and ZooKeeper. Further drivers are in review or development, such as memcache." +msgstr "" + +#: ./doc/config-reference/compute/section_compute-configure-service-groups.xml:31(title) +msgid "Database ServiceGroup driver" +msgstr "" + +#: ./doc/config-reference/compute/section_compute-configure-service-groups.xml:32(para) +msgid "Compute uses the database driver, which is the default driver, to track node liveness. In a compute worker, this driver periodically sends a command to the database, saying I'm OK with a timestamp. A pre-defined timeout (service_down_time) determines if a node is dead." +msgstr "" + +#: ./doc/config-reference/compute/section_compute-configure-service-groups.xml:38(para) +msgid "The driver has limitations, which may or may not be an issue for you, depending on your setup. The more compute worker nodes that you have, the more pressure you put on the database. By default, the timeout is 60 seconds so it might take some time to detect node failures. You could reduce the timeout value, but you must also make the DB update more frequently, which again increases the DB workload." +msgstr "" + +#: ./doc/config-reference/compute/section_compute-configure-service-groups.xml:44(para) +msgid "Fundamentally, the data that describes whether the node is alive is \"transient\" — After a few seconds, this data is obsolete. Other data in the database is persistent, such as the entries that describe who owns which VMs. However, because this data is stored in the same database, is treated the same way. The ServiceGroup abstraction aims to treat them separately." +msgstr "" + +#: ./doc/config-reference/compute/section_compute-configure-service-groups.xml:53(title) +msgid "ZooKeeper ServiceGroup driver" +msgstr "" + +#: ./doc/config-reference/compute/section_compute-configure-service-groups.xml:54(para) +msgid "The ZooKeeper ServiceGroup driver works by using ZooKeeper ephemeral nodes. ZooKeeper, in contrast to databases, is a distributed system. Its load is divided among several servers. At a compute worker node, after establishing a ZooKeeper session, it creates an ephemeral znode in the group directory. Ephemeral znodes have the same lifespan as the session. If the worker node or the nova-compute daemon crashes, or a network partition is in place between the worker and the ZooKeeper server quorums, the ephemeral znodes are removed automatically. The driver gets the group membership by running the command in the group directory." +msgstr "" + +#: ./doc/config-reference/compute/section_compute-configure-service-groups.xml:64(para) +msgid "To use the ZooKeeper driver, you must install ZooKeeper servers and client libraries. Setting up ZooKeeper servers is outside the scope of this article. For the rest of the article, assume these servers are installed, and their addresses and ports are 192.168.2.1:2181, 192.168.2.2:2181, 192.168.2.3:2181." +msgstr "" + +#: ./doc/config-reference/compute/section_compute-configure-service-groups.xml:71(para) +msgid "To use ZooKeeper, you must install client-side Python libraries on every nova node: python-zookeeper – the official Zookeeper Python binding and evzookeeper – the library to make the binding work with the eventlet threading model." +msgstr "" + +#: ./doc/config-reference/compute/section_compute-configure-service-groups.xml:77(para) +msgid "The relevant configuration snippet in the /etc/nova/nova.conf file on every node is:" +msgstr "" + +#: ./doc/config-reference/compute/section_compute-conductor.xml:7(title) +msgid "Conductor" +msgstr "" + +#: ./doc/config-reference/compute/section_compute-conductor.xml:8(para) +msgid "The nova-conductor service enables OpenStack to function without compute nodes accessing the database. Conceptually, it implements a new layer on top of nova-compute. It should not be deployed on compute nodes, or else the security benefits of removing database access from nova-compute are negated. Just like other nova services such as nova-api or nova-scheduler, it can be scaled horizontally. You can run multiple instances of nova-conductor on different machines as needed for scaling purposes." +msgstr "" + +#: ./doc/config-reference/compute/section_compute-conductor.xml:21(para) +msgid "In the Grizzly release, the methods exposed by nova-conductor are relatively simple methods used by nova-compute to offload its database operations. Places where nova-compute previously performed database access are now talking to nova-conductor. However, we have plans in the medium to long term to move more and more of what is currently in nova-compute up to the nova-conductor layer. The compute service will start to look like a less intelligent slave service to nova-conductor. The conductor service will implement long running complex operations, ensuring forward progress and graceful error handling. This will be especially beneficial for operations that cross multiple compute nodes, such as migrations or resizes." +msgstr "" + +#: ./doc/config-reference/compute/section_nova-conf.xml:6(title) +msgid "Overview of nova.conf" +msgstr "" + +#: ./doc/config-reference/compute/section_nova-conf.xml:7(para) +msgid "The nova.conf configuration file is an INI file format file that specifies options as key=value pairs, which are grouped into sections. The DEFAULT section contains most of the configuration options. For example:" +msgstr "" + +#: ./doc/config-reference/compute/section_nova-conf.xml:19(para) +msgid "You can use a particular configuration option file by using the option (nova.conf) parameter when you run one of the nova-* services. This parameter inserts configuration option definitions from the specified configuration file name, which might be useful for debugging or performance tuning." +msgstr "" + +#: ./doc/config-reference/compute/section_nova-conf.xml:25(para) +msgid "To place comments in the nova.conf file, start a new line that begins with the pound (#) character. For a list of configuration options, see the tables in this guide." +msgstr "" + +#: ./doc/config-reference/compute/section_nova-conf.xml:29(para) +msgid "To learn more about the nova.conf configuration file, review these general purpose configuration options." +msgstr "" + +#: ./doc/config-reference/compute/section_nova-conf.xml:34(title) +msgid "Types of configuration options" +msgstr "" + +#: ./doc/config-reference/compute/section_nova-conf.xml:35(para) +msgid "Each configuration option has an associated data type. The supported data types for configuration options are:" +msgstr "" + +#: ./doc/config-reference/compute/section_nova-conf.xml:40(term) +msgid "BoolOpt" +msgstr "" + +#: ./doc/config-reference/compute/section_nova-conf.xml:42(para) +msgid "Boolean option. Value must be either true or false . Example:" +msgstr "" + +#: ./doc/config-reference/compute/section_nova-conf.xml:49(term) +msgid "StrOpt" +msgstr "" + +#: ./doc/config-reference/compute/section_nova-conf.xml:51(para) +msgid "String option. Value is an arbitrary string. Example:" +msgstr "" + +#: ./doc/config-reference/compute/section_nova-conf.xml:56(term) +msgid "IntOption" +msgstr "" + +#: ./doc/config-reference/compute/section_nova-conf.xml:58(para) +msgid "Integer option. Value must be an integer. Example: " +msgstr "" + +#: ./doc/config-reference/compute/section_nova-conf.xml:64(term) +msgid "MultiStrOpt" +msgstr "" + +#: ./doc/config-reference/compute/section_nova-conf.xml:66(para) +msgid "String option. Same as StrOpt, except that it can be declared multiple times to indicate multiple values. Example:" +msgstr "" + +#: ./doc/config-reference/compute/section_nova-conf.xml:74(term) +msgid "ListOpt" +msgstr "" + +#: ./doc/config-reference/compute/section_nova-conf.xml:76(para) +msgid "List option. Value is a list of arbitrary strings separated by commas. Example:" +msgstr "" + +#: ./doc/config-reference/compute/section_nova-conf.xml:82(term) +msgid "FloatOpt" +msgstr "" + +#: ./doc/config-reference/compute/section_nova-conf.xml:84(para) +msgid "Floating-point option. Value must be a floating-point number. Example:" +msgstr "" + +#: ./doc/config-reference/compute/section_nova-conf.xml:91(para) +msgid "Do not specify quotes around Nova options." +msgstr "" + +#: ./doc/config-reference/compute/section_nova-conf.xml:95(title) +msgid "Sections" +msgstr "" + +#: ./doc/config-reference/compute/section_nova-conf.xml:99(literal) +msgid "[DEFAULT]" +msgstr "" + +#: ./doc/config-reference/compute/section_nova-conf.xml:101(para) +msgid "Contains most configuration options. If the documentation for a configuration option does not specify its section, assume that it appears in this section." +msgstr "" + +#: ./doc/config-reference/compute/section_nova-conf.xml:109(literal) +msgid "[cells]" +msgstr "" + +#: ./doc/config-reference/compute/section_nova-conf.xml:111(para) +msgid "Configures cells functionality. For details, see the Cells section ()." +msgstr "" + +#: ./doc/config-reference/compute/section_nova-conf.xml:119(literal) +msgid "[baremetal]" +msgstr "" + +#: ./doc/config-reference/compute/section_nova-conf.xml:121(para) +msgid "Configures the baremetal hypervisor driver." +msgstr "" + +#: ./doc/config-reference/compute/section_nova-conf.xml:126(literal) +msgid "[conductor]" +msgstr "" + +#: ./doc/config-reference/compute/section_nova-conf.xml:128(para) +msgid "Configures the nova-conductor service." +msgstr "" + +#: ./doc/config-reference/compute/section_nova-conf.xml:135(literal) +msgid "[trusted_computing]" +msgstr "" + +#: ./doc/config-reference/compute/section_nova-conf.xml:137(para) +msgid "Configures the trusted computing pools functionality and how to connect to a remote attestation service." +msgstr "" + +#: ./doc/config-reference/compute/section_nova-conf.xml:96(para) +msgid "Configuration options are grouped by section. The Compute configuration file supports the following sections:" +msgstr "" + +#: ./doc/config-reference/compute/section_nova-conf.xml:146(title) +msgid "Variable substitution" +msgstr "" + +#: ./doc/config-reference/compute/section_nova-conf.xml:147(para) +msgid "The configuration file supports variable substitution. After you set a configuration option, it can be referenced in later configuration values when you precede it with $. This example defines my_ip and then uses $my_ip as a variable:" +msgstr "" + +#: ./doc/config-reference/compute/section_nova-conf.xml:156(para) +msgid "If a value must contain the $ character, escape it with $$. For example, if your LDAP DNS password is $xkj432, specify it, as follows:" +msgstr "" + +#: ./doc/config-reference/compute/section_nova-conf.xml:161(para) +msgid "The Compute code uses the Python string.Template.safe_substitute() method to implement variable substitution. For more details on how variable substitution is resolved, see http://docs.python.org/2/library/string.html#template-strings and http://www.python.org/dev/peps/pep-0292/." +msgstr "" + +#: ./doc/config-reference/compute/section_nova-conf.xml:173(title) +msgid "Whitespace" +msgstr "" + +#: ./doc/config-reference/compute/section_nova-conf.xml:174(para) +msgid "To include whitespace in a configuration value, use a quoted string. For example:" +msgstr "" + +#: ./doc/config-reference/compute/section_nova-conf.xml:179(title) +msgid "Define an alternate location for nova.conf" +msgstr "" + +#: ./doc/config-reference/compute/section_nova-conf.xml:180(para) +msgid "All nova-* services and the command-line client load the configuration file. To define an alternate location for the configuration file, pass the --config-file /path/to/nova.conf parameter when you start a nova-* service or call a command." +msgstr "" + +#: ./doc/config-reference/compute/section_hypervisor_hyper-v.xml:6(title) +msgid "Hyper-V virtualization platform" +msgstr "" + +#: ./doc/config-reference/compute/section_hypervisor_hyper-v.xml:15(emphasis) +msgid "Windows Server 2008r2" +msgstr "" + +#: ./doc/config-reference/compute/section_hypervisor_hyper-v.xml:16(para) +msgid "Both Server and Server Core with the Hyper-V role enabled (Shared Nothing Live migration is not supported using 2008r2)" +msgstr "" + +#: ./doc/config-reference/compute/section_hypervisor_hyper-v.xml:20(emphasis) +msgid "Windows Server 2012" +msgstr "" + +#: ./doc/config-reference/compute/section_hypervisor_hyper-v.xml:21(para) +msgid "Server and Core (with the Hyper-V role enabled), and Hyper-V Server" +msgstr "" + +#: ./doc/config-reference/compute/section_hypervisor_hyper-v.xml:7(para) +msgid "It is possible to use Hyper-V as a compute node within an OpenStack Deployment. The nova-compute service runs as \"openstack-compute,\" a 32-bit service directly upon the Windows platform with the Hyper-V role enabled. The necessary Python components as well as the nova-compute service are installed directly onto the Windows platform. Windows Clustering Services are not needed for functionality within the OpenStack infrastructure. The use of the Windows Server 2012 platform is recommend for the best experience and is the platform for active development. The following Windows platforms have been tested as compute nodes:" +msgstr "" + +#: ./doc/config-reference/compute/section_hypervisor_hyper-v.xml:26(title) +msgid "Hyper-V configuration" +msgstr "" + +#: ./doc/config-reference/compute/section_hypervisor_hyper-v.xml:27(para) +msgid "The following sections discuss how to prepare the Windows Hyper-V node for operation as an OpenStack Compute node. Unless stated otherwise, any configuration information should work for both the Windows 2008r2 and 2012 platforms." +msgstr "" + +#: ./doc/config-reference/compute/section_hypervisor_hyper-v.xml:30(emphasis) +msgid "Local Storage Considerations" +msgstr "" + +#: ./doc/config-reference/compute/section_hypervisor_hyper-v.xml:31(para) +msgid "The Hyper-V compute node needs to have ample storage for storing the virtual machine images running on the compute nodes. You may use a single volume for all, or partition it into an OS volume and VM volume. It is up to the individual deploying to decide." +msgstr "" + +#: ./doc/config-reference/compute/section_hypervisor_hyper-v.xml:37(title) +msgid "Configure NTP" +msgstr "" + +#: ./doc/config-reference/compute/section_hypervisor_hyper-v.xml:38(para) +msgid "Network time services must be configured to ensure proper operation of the Hyper-V compute node. To set network time on your Hyper-V host you must run the following commands:" +msgstr "" + +#: ./doc/config-reference/compute/section_hypervisor_hyper-v.xml:52(title) +msgid "Configure Hyper-V virtual switching" +msgstr "" + +#: ./doc/config-reference/compute/section_hypervisor_hyper-v.xml:53(para) +msgid "Information regarding the Hyper-V virtual Switch can be located here: http://technet.microsoft.com/en-us/library/hh831823.aspx" +msgstr "" + +#: ./doc/config-reference/compute/section_hypervisor_hyper-v.xml:57(para) +msgid "To quickly enable an interface to be used as a Virtual Interface the following PowerShell may be used:" +msgstr "" + +#: ./doc/config-reference/compute/section_hypervisor_hyper-v.xml:67(title) +msgid "Enable iSCSI initiator service" +msgstr "" + +#: ./doc/config-reference/compute/section_hypervisor_hyper-v.xml:68(para) +msgid "To prepare the Hyper-V node to be able to attach to volumes provided by cinder you must first make sure the Windows iSCSI initiator service is running and started automatically." +msgstr "" + +#: ./doc/config-reference/compute/section_hypervisor_hyper-v.xml:79(title) +msgid "Configure shared nothing live migration" +msgstr "" + +#: ./doc/config-reference/compute/section_hypervisor_hyper-v.xml:80(para) +msgid "Detailed information on the configuration of live migration can be found here: http://technet.microsoft.com/en-us/library/jj134199.aspx" +msgstr "" + +#: ./doc/config-reference/compute/section_hypervisor_hyper-v.xml:83(para) +msgid "The following outlines the steps of shared nothing live migration." +msgstr "" + +#: ./doc/config-reference/compute/section_hypervisor_hyper-v.xml:86(para) +msgid "The target hosts ensures that live migration is enabled and properly configured in Hyper-V." +msgstr "" + +#: ./doc/config-reference/compute/section_hypervisor_hyper-v.xml:90(para) +msgid "The target hosts checks if the image to be migrated requires a base VHD and pulls it from Glance if not already available on the target host." +msgstr "" + +#: ./doc/config-reference/compute/section_hypervisor_hyper-v.xml:94(para) +msgid "The source hosts ensures that live migration is enabled and properly configured in Hyper-V." +msgstr "" + +#: ./doc/config-reference/compute/section_hypervisor_hyper-v.xml:98(para) +msgid "The source hosts initiates a Hyper-V live migration." +msgstr "" + +#: ./doc/config-reference/compute/section_hypervisor_hyper-v.xml:101(para) +msgid "The source hosts communicates to the manager the outcome of the operation." +msgstr "" + +#: ./doc/config-reference/compute/section_hypervisor_hyper-v.xml:109(literal) +msgid "instances_shared_storage=False" +msgstr "" + +#: ./doc/config-reference/compute/section_hypervisor_hyper-v.xml:110(para) +msgid "This needed to support \"shared nothing\" Hyper-V live migrations. It is used in nova/compute/manager.py" +msgstr "" + +#: ./doc/config-reference/compute/section_hypervisor_hyper-v.xml:114(literal) +msgid "limit_cpu_features=True" +msgstr "" + +#: ./doc/config-reference/compute/section_hypervisor_hyper-v.xml:115(para) +msgid "This flag is needed to support live migration to hosts with different CPU features. This flag is checked during instance creation in order to limit the CPU features used by the VM." +msgstr "" + +#: ./doc/config-reference/compute/section_hypervisor_hyper-v.xml:121(literal) +msgid "instances_path=DRIVELETTER:\\PATH\\TO\\YOUR\\INSTANCES" +msgstr "" + +#: ./doc/config-reference/compute/section_hypervisor_hyper-v.xml:105(para) +msgid "The following two configuration options/flags are needed in order to support Hyper-V live migration and must be added to your nova.conf on the Hyper-V compute node:" +msgstr "" + +#: ./doc/config-reference/compute/section_hypervisor_hyper-v.xml:125(para) +msgid "Additional Requirements:" +msgstr "" + +#: ./doc/config-reference/compute/section_hypervisor_hyper-v.xml:128(para) +msgid "Hyper-V 2012 RC or Windows Server 2012 RC with Hyper-V role enabled" +msgstr "" + +#: ./doc/config-reference/compute/section_hypervisor_hyper-v.xml:131(para) +msgid "A Windows domain controller with the Hyper-V compute nodes as domain members" +msgstr "" + +#: ./doc/config-reference/compute/section_hypervisor_hyper-v.xml:135(para) +msgid "The instances_path command line option/flag needs to be the same on all hosts" +msgstr "" + +#: ./doc/config-reference/compute/section_hypervisor_hyper-v.xml:139(para) +msgid "The openstack-compute service deployed with the setup must run with domain credentials. You can set the service credentials with:" +msgstr "" + +#: ./doc/config-reference/compute/section_hypervisor_hyper-v.xml:145(emphasis) +msgid "How to setup live migration on Hyper-V" +msgstr "" + +#: ./doc/config-reference/compute/section_hypervisor_hyper-v.xml:146(para) +msgid "To enable shared nothing live migration run the 3 PowerShell instructions below on each Hyper-V host:" +msgstr "" + +#: ./doc/config-reference/compute/section_hypervisor_hyper-v.xml:152(replaceable) ./doc/config-reference/compute/section_hypervisor_hyper-v.xml:337(replaceable) ./doc/config-reference/compute/section_hypervisor_hyper-v.xml:338(replaceable) ./doc/config-reference/compute/section_hypervisor_hyper-v.xml:345(replaceable) +msgid "IP_ADDRESS" +msgstr "" + +#: ./doc/config-reference/compute/section_hypervisor_hyper-v.xml:158(para) +msgid "Please replace the IP_ADDRESS with the address of the interface which will provide the virtual switching for nova-network." +msgstr "" + +#: ./doc/config-reference/compute/section_hypervisor_hyper-v.xml:161(emphasis) +msgid "Additional Reading" +msgstr "" + +#: ./doc/config-reference/compute/section_hypervisor_hyper-v.xml:162(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:166(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:170(title) +msgid "Python Requirements" +msgstr "" + +#: ./doc/config-reference/compute/section_hypervisor_hyper-v.xml:171(emphasis) +msgid "Python" +msgstr "" + +#: ./doc/config-reference/compute/section_hypervisor_hyper-v.xml:177(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:181(para) +msgid "Install the MSI accepting the default options." +msgstr "" + +#: ./doc/config-reference/compute/section_hypervisor_hyper-v.xml:184(para) +msgid "The installation will put python in C:/python27." +msgstr "" + +#: ./doc/config-reference/compute/section_hypervisor_hyper-v.xml:172(para) +msgid "Python 2.7.3 must be installed prior to installing the OpenStack Compute Driver on the Hyper-V server. Download and then install the MSI for windows here:" +msgstr "" + +#: ./doc/config-reference/compute/section_hypervisor_hyper-v.xml:188(emphasis) +msgid "Setuptools" +msgstr "" + +#: ./doc/config-reference/compute/section_hypervisor_hyper-v.xml:189(para) +msgid "You will require pip to install the necessary python module dependencies. The installer will install under the C:\\python27 directory structure. Setuptools for Python 2.7 for Windows can be download from here:" +msgstr "" + +#: ./doc/config-reference/compute/section_hypervisor_hyper-v.xml:194(link) +msgid "http://pypi.python.org/packages/2.7/s/setuptools/setuptools-0.6c11.win32-py2.7.exe" +msgstr "" + +#: ./doc/config-reference/compute/section_hypervisor_hyper-v.xml:197(emphasis) +msgid "Python Dependencies" +msgstr "" + +#: ./doc/config-reference/compute/section_hypervisor_hyper-v.xml:198(para) +msgid "You must download and manually install the following packages on the Compute node:" +msgstr "" + +#: ./doc/config-reference/compute/section_hypervisor_hyper-v.xml:202(emphasis) +msgid "MySQL-python" +msgstr "" + +#: ./doc/config-reference/compute/section_hypervisor_hyper-v.xml:205(link) +msgid "http://codegood.com/download/10/" +msgstr "" + +#: ./doc/config-reference/compute/section_hypervisor_hyper-v.xml:209(emphasis) +msgid "pywin32" +msgstr "" + +#: ./doc/config-reference/compute/section_hypervisor_hyper-v.xml:210(para) +msgid "Download and run the installer from the following location" +msgstr "" + +#: ./doc/config-reference/compute/section_hypervisor_hyper-v.xml:214(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:218(emphasis) +msgid "greenlet" +msgstr "" + +#: ./doc/config-reference/compute/section_hypervisor_hyper-v.xml:219(para) +msgid "Select the link below:" +msgstr "" + +#: ./doc/config-reference/compute/section_hypervisor_hyper-v.xml:221(link) +msgid "http://www.lfd.uci.edu/~gohlke/pythonlibs/" +msgstr "" + +#: ./doc/config-reference/compute/section_hypervisor_hyper-v.xml:222(para) +msgid "You must scroll to the greenlet section for the following file: greenlet-0.4.0.win32-py2.7.‌exe" +msgstr "" + +#: ./doc/config-reference/compute/section_hypervisor_hyper-v.xml:224(para) +msgid "Click on the file, to initiate the download. Once the download is complete, run the installer." +msgstr "" + +#: ./doc/config-reference/compute/section_hypervisor_hyper-v.xml:228(para) +msgid "You must install the following Python packages through or . Run the following replacing PACKAGENAME with the following packages:" +msgstr "" + +#: ./doc/config-reference/compute/section_hypervisor_hyper-v.xml:231(replaceable) +msgid "PACKAGE_NAME" +msgstr "" + +#: ./doc/config-reference/compute/section_hypervisor_hyper-v.xml:235(para) +msgid "amqplib" +msgstr "" + +#: ./doc/config-reference/compute/section_hypervisor_hyper-v.xml:238(para) +msgid "anyjson" +msgstr "" + +#: ./doc/config-reference/compute/section_hypervisor_hyper-v.xml:241(para) +msgid "distribute" +msgstr "" + +#: ./doc/config-reference/compute/section_hypervisor_hyper-v.xml:244(para) +msgid "eventlet" +msgstr "" + +#: ./doc/config-reference/compute/section_hypervisor_hyper-v.xml:247(para) +msgid "httplib2" +msgstr "" + +#: ./doc/config-reference/compute/section_hypervisor_hyper-v.xml:250(para) +msgid "iso8601" +msgstr "" + +#: ./doc/config-reference/compute/section_hypervisor_hyper-v.xml:253(para) +msgid "jsonschema" +msgstr "" + +#: ./doc/config-reference/compute/section_hypervisor_hyper-v.xml:256(para) +msgid "kombu" +msgstr "" + +#: ./doc/config-reference/compute/section_hypervisor_hyper-v.xml:259(para) +msgid "netaddr" +msgstr "" + +#: ./doc/config-reference/compute/section_hypervisor_hyper-v.xml:262(para) +msgid "paste" +msgstr "" + +#: ./doc/config-reference/compute/section_hypervisor_hyper-v.xml:265(para) +msgid "paste-deploy" +msgstr "" + +#: ./doc/config-reference/compute/section_hypervisor_hyper-v.xml:268(para) +msgid "prettytable" +msgstr "" + +#: ./doc/config-reference/compute/section_hypervisor_hyper-v.xml:271(para) +msgid "python-cinderclient" +msgstr "" + +#: ./doc/config-reference/compute/section_hypervisor_hyper-v.xml:274(para) +msgid "python-glanceclient" +msgstr "" + +#: ./doc/config-reference/compute/section_hypervisor_hyper-v.xml:277(para) +msgid "python-keystoneclient" +msgstr "" + +#: ./doc/config-reference/compute/section_hypervisor_hyper-v.xml:280(para) +msgid "repoze.lru" +msgstr "" + +#: ./doc/config-reference/compute/section_hypervisor_hyper-v.xml:283(para) +msgid "routes" +msgstr "" + +#: ./doc/config-reference/compute/section_hypervisor_hyper-v.xml:286(para) +msgid "sqlalchemy" +msgstr "" + +#: ./doc/config-reference/compute/section_hypervisor_hyper-v.xml:289(para) +msgid "simplejson" +msgstr "" + +#: ./doc/config-reference/compute/section_hypervisor_hyper-v.xml:292(para) +msgid "warlock" +msgstr "" + +#: ./doc/config-reference/compute/section_hypervisor_hyper-v.xml:295(para) +msgid "webob" +msgstr "" + +#: ./doc/config-reference/compute/section_hypervisor_hyper-v.xml:298(para) +msgid "wmi" +msgstr "" + +#: ./doc/config-reference/compute/section_hypervisor_hyper-v.xml:303(title) +msgid "Install Nova-compute" +msgstr "" + +#: ./doc/config-reference/compute/section_hypervisor_hyper-v.xml:304(emphasis) +msgid "Using git on Windows to retrieve source" +msgstr "" + +#: ./doc/config-reference/compute/section_hypervisor_hyper-v.xml:305(para) +msgid "Git be used 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:310(link) +msgid "http://code.google.com/p/msysgit/downloads/list?q=full+installer+official+git" +msgstr "" + +#: ./doc/config-reference/compute/section_hypervisor_hyper-v.xml:312(para) +msgid "Download the latest installer. Once the download is complete double click 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:315(para) +msgid "Once installed you may run the following to clone the Nova code." +msgstr "" + +#: ./doc/config-reference/compute/section_hypervisor_hyper-v.xml:321(title) +msgid "Configure Nova.conf" +msgstr "" + +#: ./doc/config-reference/compute/section_hypervisor_hyper-v.xml:322(para) +msgid "The nova.conf file must be placed in C:\\etc\\nova for running OpenStack on Hyper-V. Below is a sample nova.conf for Windows:" +msgstr "" + +#: ./doc/config-reference/compute/section_hypervisor_hyper-v.xml:346(para) +msgid "The following table contains a reference of all options for hyper-v" +msgstr "" + +#: ./doc/config-reference/compute/section_hypervisor_hyper-v.xml:350(title) +msgid "Prepare images for use with Hyper-V" +msgstr "" + +#: ./doc/config-reference/compute/section_hypervisor_hyper-v.xml:351(para) +msgid "Hyper-V currently supports only the VHD 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:355(link) +msgid "http://technet.microsoft.com/en-us/library/cc772480.aspx" +msgstr "" + +#: ./doc/config-reference/compute/section_hypervisor_hyper-v.xml:356(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:359(replaceable) +msgid "VM_IMAGE_NAME" +msgstr "" + +#: ./doc/config-reference/compute/section_hypervisor_hyper-v.xml:363(title) +msgid "Run Compute with Hyper-V" +msgstr "" + +#: ./doc/config-reference/compute/section_hypervisor_hyper-v.xml:364(para) +msgid "To start the nova-compute service, run this command from a console in the Windows server:" +msgstr "" + +#: ./doc/config-reference/compute/section_hypervisor_hyper-v.xml:371(title) +msgid "Troubleshoot Hyper-V configuration" +msgstr "" + +#: ./doc/config-reference/compute/section_hypervisor_hyper-v.xml:374(para) +msgid "I ran the nova-manage service list 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:379(link) +msgid "here" +msgstr "" + +#: ./doc/config-reference/compute/section_hypervisor_hyper-v.xml:377(emphasis) +msgid "Verify that you are synchronized with a network time source. Instructions for configuring NTP on your Hyper-V compute node are located " +msgstr "" + +#. When image changes, this message will be marked fuzzy or untranslated for you. +#. It doesn't matter what you translate it to: it's not used at all. +#: ./doc/config-reference/compute/section_hypervisor_vmware.xml:39(None) +msgid "@@image: '../../common/figures/vmware-nova-driver-architecture.jpg'; md5=d95084ce963cffbe3e86307c87d804c1" +msgstr "" + +#: ./doc/config-reference/compute/section_hypervisor_vmware.xml:6(title) +msgid "VMware vSphere" +msgstr "" + +#: ./doc/config-reference/compute/section_hypervisor_vmware.xml:9(title) +msgid "Introduction" +msgstr "" + +#: ./doc/config-reference/compute/section_hypervisor_vmware.xml:10(para) +msgid "OpenStack Compute supports the VMware vSphere product family and enables access to advanced features such as vMotion, High Availability, and Dynamic Resource Scheduling (DRS). This section describes how to configure VMware-based virtual machine images for launch. vSphere versions 4.1 and newer are supported." +msgstr "" + +#: ./doc/config-reference/compute/section_hypervisor_vmware.xml:16(para) +msgid "The VMware vCenter driver enables the nova-compute service to communicate with a VMware vCenter server that manages one or more ESX host clusters. The driver aggregates the ESX hosts in each cluster to present one large hypervisor entity for each cluster to the Compute scheduler. Because individual ESX hosts are not exposed to the scheduler, Compute schedules to the granularity of clusters and vCenter uses DRS to select the actual ESX host within the cluster. When a virtual machine makes its way into a vCenter cluster, it can use all vSphere features." +msgstr "" + +#: ./doc/config-reference/compute/section_hypervisor_vmware.xml:26(para) +msgid "The following sections describe how to configure the VMware vCenter driver." +msgstr "" + +#: ./doc/config-reference/compute/section_hypervisor_vmware.xml:30(title) +msgid "High-level architecture" +msgstr "" + +#: ./doc/config-reference/compute/section_hypervisor_vmware.xml:31(para) +msgid "The following diagram shows a high-level view of the VMware driver architecture:" +msgstr "" + +#: ./doc/config-reference/compute/section_hypervisor_vmware.xml:34(title) +msgid "VMware driver architecture" +msgstr "" + +#: ./doc/config-reference/compute/section_hypervisor_vmware.xml:43(para) +msgid "As the figure shows, the OpenStack Compute Scheduler sees three hypervisors that each correspond to a cluster in vCenter. Nova-compute contains the VMware driver. You can run with multiple nova-compute services. While Compute schedules at the granularity of a cluster, the VMware driver inside nova-compute interacts with the vCenter APIs to select an appropriate ESX host within the cluster. Internally, vCenter uses DRS for placement." +msgstr "" + +#: ./doc/config-reference/compute/section_hypervisor_vmware.xml:53(para) +msgid "The VMware vCenter driver also interacts with the OpenStack Image Service to copy VMDK images from the Image Service back end store. The dotted line in the figure represents VMDK images being copied from the OpenStack Image Service to the vSphere data store. VMDK images are cached in the data store so the copy operation is only required the first time that the VMDK image is used." +msgstr "" + +#: ./doc/config-reference/compute/section_hypervisor_vmware.xml:60(para) +msgid "After OpenStack boots a VM into a vSphere cluster, the VM becomes visible in vCenter and can access vSphere advanced features. At the same time, the VM is visible in the OpenStack dashboard and you can manage it as you would any other OpenStack VM. You can perform advanced vSphere operations in vCenter while you configure OpenStack resources such as VMs through the OpenStack dashboard." +msgstr "" + +#: ./doc/config-reference/compute/section_hypervisor_vmware.xml:67(para) +msgid "The figure does not show how networking fits into the architecture. Both nova-network and the OpenStack Networking Service are supported. For details, see ." +msgstr "" + +#: ./doc/config-reference/compute/section_hypervisor_vmware.xml:74(title) +msgid "Configuration overview" +msgstr "" + +#: ./doc/config-reference/compute/section_hypervisor_vmware.xml:75(para) +msgid "To get started with the VMware vCenter driver, complete the following high-level steps:" +msgstr "" + +#: ./doc/config-reference/compute/section_hypervisor_vmware.xml:79(para) +msgid "Configure vCenter correctly. See ." +msgstr "" + +#: ./doc/config-reference/compute/section_hypervisor_vmware.xml:83(para) +msgid "Configure nova.conf for the VMware vCenter driver. See ." +msgstr "" + +#: ./doc/config-reference/compute/section_hypervisor_vmware.xml:88(para) +msgid "Load desired VMDK images into the OpenStack Image Service. See ." +msgstr "" + +#: ./doc/config-reference/compute/section_hypervisor_vmware.xml:92(para) +msgid "Configure networking with either nova-network or the OpenStack Networking Service. See ." +msgstr "" + +#: ./doc/config-reference/compute/section_hypervisor_vmware.xml:100(title) +msgid "Prerequisites and limitations" +msgstr "" + +#: ./doc/config-reference/compute/section_hypervisor_vmware.xml:101(para) +msgid "Use the following list to prepare a vSphere environment that runs with the VMware vCenter driver:" +msgstr "" + +#: ./doc/config-reference/compute/section_hypervisor_vmware.xml:105(para) +msgid "vCenter inventory. Make sure that any vCenter used by OpenStack contains a single data center. A future Havana stable release will address this temporary limitation." +msgstr "" + +#: ./doc/config-reference/compute/section_hypervisor_vmware.xml:111(para) +msgid "DRS. For any cluster that contains multiple ESX hosts, enable DRS and enable fully automated placement." +msgstr "" + +#: ./doc/config-reference/compute/section_hypervisor_vmware.xml:116(para) +msgid "Shared storage. Only shared storage is supported and data stores must be shared among all hosts in a cluster. It is recommended to remove data stores not intended for OpenStack from clusters being configured for OpenStack. Currently, a single data store can be used per cluster. A future Havana stable release will address this temporary limitation." +msgstr "" + +#: ./doc/config-reference/compute/section_hypervisor_vmware.xml:125(para) +msgid "Clusters and data stores. Do not use OpenStack clusters and data stores for other purposes. If you do, OpenStack displays incorrect usage information." +msgstr "" + +#: ./doc/config-reference/compute/section_hypervisor_vmware.xml:131(para) +msgid "Networking. The networking configuration depends on the desired networking model. See ." +msgstr "" + +#: ./doc/config-reference/compute/section_hypervisor_vmware.xml:136(para) +msgid "Security groups. If you use the VMware driver with OpenStack Networking and the NSX plug-in, security groups are supported. If you use nova-network, security groups are not supported." +msgstr "" + +#: ./doc/config-reference/compute/section_hypervisor_vmware.xml:141(para) +msgid "The NSX plug-in is the only plug-in that is validated for vSphere." +msgstr "" + +#: ./doc/config-reference/compute/section_hypervisor_vmware.xml:145(para) +msgid "VNC. The port range 5900 - 6105 (inclusive) is automatically enabled for VNC connections on every ESX host in all clusters under OpenStack control. For more information about using a VNC client to connect to virtual machine, see http://kb.vmware.com/selfservice/microsites/search.do?language=en_US&cmd=displayKC&externalId=1246." +msgstr "" + +#: ./doc/config-reference/compute/section_hypervisor_vmware.xml:152(para) +msgid "In addition to the default VNC port numbers (5900 to 6000) specified in the above document, the following ports are also used: 6101, 6102, and 6105." +msgstr "" + +#: ./doc/config-reference/compute/section_hypervisor_vmware.xml:155(para) +msgid "You must modify the ESXi firewall configuration to allow the VNC ports. Additionally, for the firewall modifications to persist after a reboot, you must create a custom vSphere Installation Bundle (VIB) which is then installed onto the running ESXi host or added to a custom image profile used to install ESXi hosts. For details about how to create a VIB for persisting the firewall configuration modifications, see http://kb.vmware.com/selfservice/microsites/search.do?language=en_US&cmd=displayKC&externalId=2007381." +msgstr "" + +#: ./doc/config-reference/compute/section_hypervisor_vmware.xml:168(para) +msgid "Ephemeral Disks. Ephemeral disks are not supported. A future stable release will address this temporary limitation." +msgstr "" + +#: ./doc/config-reference/compute/section_hypervisor_vmware.xml:175(title) +msgid "VMware vCenter driver" +msgstr "" + +#: ./doc/config-reference/compute/section_hypervisor_vmware.xml:176(para) +msgid "Use the VMware vCenter driver (VMwareVCDriver) to connect OpenStack Compute with vCenter. This recommended configuration enables access through vCenter to advanced vSphere features like vMotion, High Availability, and Dynamic Resource Scheduling (DRS)." +msgstr "" + +#: ./doc/config-reference/compute/section_hypervisor_vmware.xml:182(title) +msgid "VMwareVCDriver configuration options" +msgstr "" + +#: ./doc/config-reference/compute/section_hypervisor_vmware.xml:183(para) +msgid "When you use the VMwareVCDriver (vCenter) with OpenStack Compute, add the following VMware-specific configuration options to the nova.conf file:" +msgstr "" + +#: ./doc/config-reference/compute/section_hypervisor_vmware.xml:200(para) +msgid "Clusters: The vCenter driver can support multiple clusters. To use more than one cluster, simply add multiple cluster_name lines in nova.conf with the appropriate cluster name. Clusters and data stores used by the vCenter driver should not contain any VMs other than those created by the driver." +msgstr "" + +#: ./doc/config-reference/compute/section_hypervisor_vmware.xml:209(para) +msgid "Data stores: The datastore_regex field specifies the data stores to use with Compute. For example, datastore_regex=\"nas.*\" selects all the data stores that have a name starting with \"nas\". If this line is omitted, Compute uses the first data store returned by the vSphere API. It is recommended not to use this field and instead remove data stores that are not intended for OpenStack." +msgstr "" + +#: ./doc/config-reference/compute/section_hypervisor_vmware.xml:220(para) +msgid "A nova-compute service can control one or more clusters containing multiple ESX hosts, making nova-compute a critical service from a high availability perspective. Because the host that runs nova-compute can fail while the vCenter and ESX still run, you must protect the nova-compute service against host failures." +msgstr "" + +#: ./doc/config-reference/compute/section_hypervisor_vmware.xml:230(para) ./doc/config-reference/compute/section_hypervisor_vmware.xml:634(para) +msgid "Many nova.conf options are relevant to libvirt but do not apply to this driver." +msgstr "" + +#: ./doc/config-reference/compute/section_hypervisor_vmware.xml:233(para) +msgid "You must complete additional configuration for environments that use vSphere 5.0 and earlier. See ." +msgstr "" + +#: ./doc/config-reference/compute/section_hypervisor_vmware.xml:239(title) +msgid "Images with VMware vSphere" +msgstr "" + +#: ./doc/config-reference/compute/section_hypervisor_vmware.xml:240(para) +msgid "The vCenter driver supports images in the VMDK format. Disks in this format can be obtained from VMware Fusion or from an ESX environment. It is also possible to convert other formats, such as qcow2, to the VMDK format using the qemu-img utility. After a VMDK disk is available, load it into the OpenStack Image Service. Then, you can use it with the VMware vCenter driver. The following sections provide additional details on the supported disks and the commands used for conversion and upload." +msgstr "" + +#: ./doc/config-reference/compute/section_hypervisor_vmware.xml:250(title) +msgid "Supported image types" +msgstr "" + +#: ./doc/config-reference/compute/section_hypervisor_vmware.xml:251(para) +msgid "Upload images to the OpenStack Image Service in VMDK format. The following VMDK disk types are supported:" +msgstr "" + +#: ./doc/config-reference/compute/section_hypervisor_vmware.xml:255(para) +msgid "VMFS Flat Disks (includes thin, thick, zeroedthick, and eagerzeroedthick). Note that once a VMFS thin disk is exported from VMFS to a non-VMFS location, like the OpenStack Image Service, it becomes a preallocated flat disk. This impacts the transfer time from the OpenStack Image Service to the data store when the full preallocated flat disk, rather than the thin disk, must be transferred." +msgstr "" + +#: ./doc/config-reference/compute/section_hypervisor_vmware.xml:265(para) +msgid "Monolithic Sparse disks. Sparse disks get imported from the OpenStack Image Service into ESX as thin provisioned disks. Monolithic Sparse disks can be obtained from VMware Fusion or can be created by converting from other virtual disk formats using the qemu-img utility." +msgstr "" + +#: ./doc/config-reference/compute/section_hypervisor_vmware.xml:274(para) +msgid "The following table shows the vmware_disktype property that applies to each of the supported VMDK disk types:" +msgstr "" + +#: ./doc/config-reference/compute/section_hypervisor_vmware.xml:278(caption) +msgid "OpenStack Image Service disk type settings" +msgstr "" + +#: ./doc/config-reference/compute/section_hypervisor_vmware.xml:281(th) +msgid "vmware_disktype property" +msgstr "" + +#: ./doc/config-reference/compute/section_hypervisor_vmware.xml:282(th) ./doc/config-reference/block-storage/drivers/vmware-vmdk-driver.xml:31(title) +msgid "VMDK disk type" +msgstr "" + +#: ./doc/config-reference/compute/section_hypervisor_vmware.xml:287(td) +msgid "sparse" +msgstr "" + +#: ./doc/config-reference/compute/section_hypervisor_vmware.xml:289(para) +msgid "Monolithic Sparse" +msgstr "" + +#: ./doc/config-reference/compute/section_hypervisor_vmware.xml:293(td) ./doc/config-reference/block-storage/drivers/vmware-vmdk-driver.xml:51(td) ./doc/config-reference/block-storage/drivers/vmware-vmdk-driver.xml:53(td) +msgid "thin" +msgstr "" + +#: ./doc/config-reference/compute/section_hypervisor_vmware.xml:295(para) +msgid "VMFS flat, thin provisioned" +msgstr "" + +#: ./doc/config-reference/compute/section_hypervisor_vmware.xml:299(td) +msgid "preallocated (default)" +msgstr "" + +#: ./doc/config-reference/compute/section_hypervisor_vmware.xml:301(para) +msgid "VMFS flat, thick/zeroedthick/eagerzeroedthick" +msgstr "" + +#: ./doc/config-reference/compute/section_hypervisor_vmware.xml:308(para) +msgid "The vmware_disktype property is set when an image is loaded into the OpenStack Image Service. For example, the following command creates a Monolithic Sparse image by setting vmware_disktype to sparse:" +msgstr "" + +#: ./doc/config-reference/compute/section_hypervisor_vmware.xml:317(para) +msgid "Note that specifying thin does not provide any advantage over preallocated with the current version of the driver. Future versions might restore the thin properties of the disk after it is downloaded to a vSphere data store." +msgstr "" + +#: ./doc/config-reference/compute/section_hypervisor_vmware.xml:324(title) +msgid "Convert and load images" +msgstr "" + +#: ./doc/config-reference/compute/section_hypervisor_vmware.xml:325(para) +msgid "Using the qemu-img utility, disk images in several formats (such as, qcow2) can be converted to the VMDK format." +msgstr "" + +#: ./doc/config-reference/compute/section_hypervisor_vmware.xml:328(para) +msgid "For example, the following command can be used to convert a qcow2 Ubuntu Precise cloud image:" +msgstr "" + +#: ./doc/config-reference/compute/section_hypervisor_vmware.xml:334(para) +msgid "VMDK disks converted through qemu-img are always monolithic sparse VMDK disks with an IDE adapter type. Using the previous example of the Precise Ubuntu image after the qemu-img conversion, the command to upload the VMDK disk should be something like:" +msgstr "" + +#: ./doc/config-reference/compute/section_hypervisor_vmware.xml:345(para) +msgid "Note that the vmware_disktype is set to sparse and the vmware_adaptertype is set to ide in the previous command." +msgstr "" + +#: ./doc/config-reference/compute/section_hypervisor_vmware.xml:349(para) +msgid "If the image did not come from the qemu-img utility, the vmware_disktype and vmware_adaptertype might be different. To determine the image adapter type from an image file, use the following command and look for the ddb.adapterType= line:" +msgstr "" + +#: ./doc/config-reference/compute/section_hypervisor_vmware.xml:356(para) +msgid "Assuming a preallocated disk type and an iSCSI lsiLogic adapter type, the following command uploads the VMDK disk:" +msgstr "" + +#: ./doc/config-reference/compute/section_hypervisor_vmware.xml:364(para) +msgid "Currently, OS boot VMDK disks with an IDE adapter type cannot be attached to a virtual SCSI controller and likewise disks with one of the SCSI adapter types (such as, busLogic, lsiLogic) cannot be attached to the IDE controller. Therefore, as the previous examples show, it is important to set the vmware_adaptertype property correctly. The default adapter type is lsiLogic, which is SCSI, so you can omit the vmware_adaptertype property if you are certain that the image adapter type is lsiLogic." +msgstr "" + +#: ./doc/config-reference/compute/section_hypervisor_vmware.xml:376(title) +msgid "Tag VMware images" +msgstr "" + +#: ./doc/config-reference/compute/section_hypervisor_vmware.xml:377(para) +msgid "In a mixed hypervisor environment, OpenStack Compute uses the hypervisor_type tag to match images to the correct hypervisor type. For VMware images, set the hypervisor type to vmware. Other valid hypervisor types include: xen, qemu, kvm, lxc, uml, and hyperv." +msgstr "" + +#: ./doc/config-reference/compute/section_hypervisor_vmware.xml:390(title) +msgid "Optimize images" +msgstr "" + +#: ./doc/config-reference/compute/section_hypervisor_vmware.xml:391(para) +msgid "Monolithic Sparse disks are considerably faster to download but have the overhead of an additional conversion step. When imported into ESX, sparse disks get converted to VMFS flat thin provisioned disks. The download and conversion steps only affect the first launched instance that uses the sparse disk image. The converted disk image is cached, so subsequent instances that use this disk image can simply use the cached version." +msgstr "" + +#: ./doc/config-reference/compute/section_hypervisor_vmware.xml:399(para) +msgid "To avoid the conversion step (at the cost of longer download times) consider converting sparse disks to thin provisioned or preallocated disks before loading them into the OpenStack Image Service. Below are some tools that can be used to pre-convert sparse disks." +msgstr "" + +#: ./doc/config-reference/compute/section_hypervisor_vmware.xml:406(emphasis) +msgid "Using vSphere CLI (or sometimes called the remote CLI or rCLI) tools" +msgstr "" + +#: ./doc/config-reference/compute/section_hypervisor_vmware.xml:408(para) +msgid "Assuming that the sparse disk is made available on a data store accessible by an ESX host, the following command converts it to preallocated format:" +msgstr "" + +#: ./doc/config-reference/compute/section_hypervisor_vmware.xml:412(para) +msgid "(Note that the vifs tool from the same CLI package can be used to upload the disk to be converted. The vifs tool can also be used to download the converted disk if necessary.)" +msgstr "" + +#: ./doc/config-reference/compute/section_hypervisor_vmware.xml:418(emphasis) +msgid "Using vmkfstools directly on the ESX host" +msgstr "" + +#: ./doc/config-reference/compute/section_hypervisor_vmware.xml:420(para) +msgid "If the SSH service is enabled on an ESX host, the sparse disk can be uploaded to the ESX data store via scp and the vmkfstools local to the ESX host can use used to perform the conversion: (After logging in to the host via ssh)" +msgstr "" + +#: ./doc/config-reference/compute/section_hypervisor_vmware.xml:429(emphasis) +msgid "vmware-vdiskmanager" +msgstr "" + +#: ./doc/config-reference/compute/section_hypervisor_vmware.xml:430(para) +msgid "vmware-vdiskmanager is a utility that comes bundled with VMware Fusion and VMware Workstation. Below is an example of converting a sparse disk to preallocated format:" +msgstr "" + +#: ./doc/config-reference/compute/section_hypervisor_vmware.xml:435(para) +msgid "In all of the above cases, the converted vmdk is actually a pair of files: the descriptor file converted.vmdk and the actual virtual disk data file converted-flat.vmdk. The file to be uploaded to the OpenStack Image Service is converted-flat.vmdk." +msgstr "" + +#: ./doc/config-reference/compute/section_hypervisor_vmware.xml:446(title) +msgid "Image handling" +msgstr "" + +#: ./doc/config-reference/compute/section_hypervisor_vmware.xml:447(para) +msgid "The ESX hypervisor requires a copy of the VMDK file in order to boot up a virtual machine. As a result, the vCenter OpenStack Compute driver must download the VMDK via HTTP from the OpenStack Image Service to a data store that is visible to the hypervisor. To optimize this process, the first time a VMDK file is used, it gets cached in the data store. Subsequent virtual machines that need the VMDK use the cached version and don't have to copy the file again from the OpenStack Image Service." +msgstr "" + +#: ./doc/config-reference/compute/section_hypervisor_vmware.xml:456(para) +msgid "Even with a cached VMDK, there is still a copy operation from the cache location to the hypervisor file directory in the shared data store. To avoid this copy, boot the image in linked_clone mode. To learn how to enable this mode, see . Note also that it is possible to override the linked_clone mode on a per-image basis by using the vmware_linked_clone property in the OpenStack Image Service." +msgstr "" + +#: ./doc/config-reference/compute/section_hypervisor_vmware.xml:467(title) +msgid "Networking with VMware vSphere" +msgstr "" + +#: ./doc/config-reference/compute/section_hypervisor_vmware.xml:468(para) +msgid "The VMware driver supports networking with the nova-network service or the OpenStack Networking Service. Depending on your installation, complete these configuration steps before you provision VMs:" +msgstr "" + +#: ./doc/config-reference/compute/section_hypervisor_vmware.xml:475(para) +msgid "The nova-network service with the FlatManager or FlatDHCPManager. Create a port group with the same name as the flat_network_bridge value in the nova.conf file. The default value is br100." +msgstr "" + +#: ./doc/config-reference/compute/section_hypervisor_vmware.xml:481(para) +msgid "All VM NICs are attached to this port group." +msgstr "" + +#: ./doc/config-reference/compute/section_hypervisor_vmware.xml:482(para) +msgid "Ensure that the flat interface of the node that runs the nova-network service has a path to this network." +msgstr "" + +#: ./doc/config-reference/compute/section_hypervisor_vmware.xml:487(para) +msgid "The nova-network service with the VlanManager. Set the vlan_interface configuration option to match the ESX host interface that handles VLAN-tagged VM traffic." +msgstr "" + +#: ./doc/config-reference/compute/section_hypervisor_vmware.xml:493(para) +msgid "OpenStack Compute automatically creates the corresponding port groups." +msgstr "" + +#: ./doc/config-reference/compute/section_hypervisor_vmware.xml:497(para) +msgid "The OpenStack Networking Service. If you use OVS as the l2 agent, create a port group with the same name as the DEFAULT.neutron_ovs_bridge value in the nova.conf file. Otherwise, create a port group with the same name as the vmware.integration_bridge value in the nova.conf file. In both cases, the default value is br-int." +msgstr "" + +#: ./doc/config-reference/compute/section_hypervisor_vmware.xml:506(para) +msgid "All VM NICs are attached to this port group for management by the OpenStack Networking plug-in." +msgstr "" + +#: ./doc/config-reference/compute/section_hypervisor_vmware.xml:512(title) +msgid "Volumes with VMware vSphere" +msgstr "" + +#: ./doc/config-reference/compute/section_hypervisor_vmware.xml:513(para) +msgid "The VMware driver supports attaching volumes from the OpenStack Block Storage service. The VMware VMDK driver for OpenStack Block Storage is recommended and should be used for managing volumes based on vSphere data stores. More information about the VMware VMDK driver can be found at: VMware VMDK Driver. Also an iscsi volume driver provides limited support and can be used only for attachments." +msgstr "" + +#: ./doc/config-reference/compute/section_hypervisor_vmware.xml:524(title) +msgid "vSphere 5.0 and earlier additional set up" +msgstr "" + +#: ./doc/config-reference/compute/section_hypervisor_vmware.xml:525(para) +msgid "Users of vSphere 5.0 or earlier must host their WSDL files locally. These steps are applicable for vCenter 5.0 or ESXi 5.0 and you can either mirror the WSDL from the vCenter or ESXi server that you intend to use or you can download the SDK directly from VMware. These workaround steps fix a known issue with the WSDL that was resolved in later versions." +msgstr "" + +#: ./doc/config-reference/compute/section_hypervisor_vmware.xml:534(title) +msgid "Mirror WSDL from vCenter (or ESXi)" +msgstr "" + +#: ./doc/config-reference/compute/section_hypervisor_vmware.xml:536(para) +msgid "Set the VMWAREAPI_IP shell variable to the IP address for your vCenter or ESXi host from where you plan to mirror files. For example:" +msgstr "" + +#: ./doc/config-reference/compute/section_hypervisor_vmware.xml:542(para) +msgid "Create a local file system directory to hold the WSDL files:" +msgstr "" + +#: ./doc/config-reference/compute/section_hypervisor_vmware.xml:547(para) +msgid "Change into the new directory. " +msgstr "" + +#: ./doc/config-reference/compute/section_hypervisor_vmware.xml:551(para) +msgid "Use your OS-specific tools to install a command-line tool that can download files like ." +msgstr "" + +#: ./doc/config-reference/compute/section_hypervisor_vmware.xml:556(para) +msgid "Download the files to the local file cache:" +msgstr "" + +#: ./doc/config-reference/compute/section_hypervisor_vmware.xml:566(para) +msgid "Because the reflect-types.xsd and reflect-messagetypes.xsd files do not fetch properly, you must stub out these files. Use the following XML listing to replace the missing file content. The XML parser underneath Python can be very particular and if you put a space in the wrong place, it can break the parser. Copy the following contents and formatting carefully." +msgstr "" + +#: ./doc/config-reference/compute/section_hypervisor_vmware.xml:583(para) +msgid "Now that the files are locally present, tell the driver to look for the SOAP service WSDLs in the local file system and not on the remote vSphere server. Add the following setting to the nova.conf file for your nova-compute node:" +msgstr "" + +#: ./doc/config-reference/compute/section_hypervisor_vmware.xml:593(para) +msgid "Alternatively, download the version appropriate SDK from http://www.vmware.com/support/developer/vc-sdk/ and copy it to the /opt/stack/vmware file. Make sure that the WSDL is available, in for example /opt/stack/vmware/SDK/wsdl/vim25/vimService.wsdl. You must point nova.conf to fetch this WSDL file from the local file system by using a URL." +msgstr "" + +#: ./doc/config-reference/compute/section_hypervisor_vmware.xml:602(para) +msgid "When using the VMwareVCDriver (vCenter) with OpenStack Compute with vSphere version 5.0 or earlier, nova.conf must include the following extra config option:" +msgstr "" + +#: ./doc/config-reference/compute/section_hypervisor_vmware.xml:610(title) +msgid "VMware ESX driver" +msgstr "" + +#: ./doc/config-reference/compute/section_hypervisor_vmware.xml:611(para) +msgid "This section covers details of using the VMwareESXDriver. The ESX Driver has not been extensively tested and is not recommended. To configure the VMware vCenter driver instead, see ." +msgstr "" + +#: ./doc/config-reference/compute/section_hypervisor_vmware.xml:616(title) +msgid "VMwareESXDriver configuration options" +msgstr "" + +#: ./doc/config-reference/compute/section_hypervisor_vmware.xml:617(para) +msgid "When you use the VMwareESXDriver (no vCenter) with OpenStack Compute, add the following VMware-specific configuration options to the nova.conf file:" +msgstr "" + +#: ./doc/config-reference/compute/section_hypervisor_vmware.xml:629(para) +msgid "Remember that you will have one nova-compute service for each ESXi host. It is recommended that this host run as a VM on the same ESXi host that it manages." +msgstr "" + +#: ./doc/config-reference/compute/section_hypervisor_vmware.xml:639(title) +msgid "Requirements and limitations" +msgstr "" + +#: ./doc/config-reference/compute/section_hypervisor_vmware.xml:640(para) +msgid "The ESXDriver cannot use many of the vSphere platform advanced capabilities, namely vMotion, high availability, and DRS." +msgstr "" + +#: ./doc/config-reference/compute/section_hypervisor_vmware.xml:646(title) ./doc/config-reference/compute/section_compute-scheduler.xml:527(title) +msgid "Configuration reference" +msgstr "" + +#. When image changes, this message will be marked fuzzy or untranslated for you. +#. It doesn't matter what you translate it to: it's not used at all. +#: ./doc/config-reference/compute/section_compute-scheduler.xml:75(None) +msgid "@@image: '../../common/figures/filteringWorkflow1.png'; md5=c144af5cbdee1bd17a7bde0bea5b5fe7" +msgstr "" + +#: ./doc/config-reference/compute/section_compute-scheduler.xml:10(title) +msgid "Scheduling" +msgstr "" + +#: ./doc/config-reference/compute/section_compute-scheduler.xml:11(para) +msgid "Compute uses the nova-scheduler service to determine how to dispatch compute and volume requests. For example, the nova-scheduler service determines which host a VM should launch on. The term host in the context of filters means a physical node that has a nova-compute service running on it. You can configure the scheduler through a variety of options." +msgstr "" + +#: ./doc/config-reference/compute/section_compute-scheduler.xml:17(para) +msgid "Compute is configured with the following default scheduler options:" +msgstr "" + +#: ./doc/config-reference/compute/section_compute-scheduler.xml:24(para) +msgid "By default, the compute scheduler is configured as a filter scheduler, as described in the next section. In the default configuration, this scheduler considers hosts that meet all the following criteria:" +msgstr "" + +#: ./doc/config-reference/compute/section_compute-scheduler.xml:30(para) +msgid "Are in the requested availability zone (AvailabilityZoneFilter)." +msgstr "" + +#: ./doc/config-reference/compute/section_compute-scheduler.xml:34(para) +msgid "Have sufficient RAM available (RamFilter)." +msgstr "" + +#: ./doc/config-reference/compute/section_compute-scheduler.xml:38(para) +msgid "Are capable of servicing the request (ComputeFilter)." +msgstr "" + +#: ./doc/config-reference/compute/section_compute-scheduler.xml:42(para) +msgid "For information on the volume scheduler, refer the Block Storage section of OpenStack Cloud Administrator Guide for information." +msgstr "" + +#: ./doc/config-reference/compute/section_compute-scheduler.xml:46(title) +msgid "Filter scheduler" +msgstr "" + +#: ./doc/config-reference/compute/section_compute-scheduler.xml:47(para) +msgid "The Filter Scheduler (nova.scheduler.filter_scheduler.FilterScheduler) is the default scheduler for scheduling virtual machine instances. It supports filtering and weighting to make informed decisions on where a new instance should be created. You can use this scheduler to schedule compute requests but not volume requests. For example, you can use it with only the compute_scheduler_driver configuration option." +msgstr "" + +#: ./doc/config-reference/compute/section_compute-scheduler.xml:60(title) +msgid "Filters" +msgstr "" + +#: ./doc/config-reference/compute/section_compute-scheduler.xml:70(title) +msgid "Filtering" +msgstr "" + +#: ./doc/config-reference/compute/section_compute-scheduler.xml:61(para) +msgid "When the Filter Scheduler receives a request for a resource, it first applies filters to determine which hosts are eligible for consideration when dispatching a resource. Filters are binary: either a host is accepted by the filter, or it is rejected. Hosts that are accepted by the filter are then processed by a different algorithm to decide which hosts to use for that request, described in the Weights section. " +msgstr "" + +#: ./doc/config-reference/compute/section_compute-scheduler.xml:80(para) +msgid "The scheduler_available_filters configuration option in nova.conf provides the Compute service with the list of the filters that are used by the scheduler. The default setting specifies all of the filter that are included with the Compute service:" +msgstr "" + +#: ./doc/config-reference/compute/section_compute-scheduler.xml:87(para) +msgid "This configuration option can be specified multiple times. For example, if you implemented your own custom filter in Python called myfilter.MyFilter and you wanted to use both the built-in filters and your custom filter, your nova.conf file would contain:" +msgstr "" + +#: ./doc/config-reference/compute/section_compute-scheduler.xml:96(para) +msgid "The scheduler_default_filters configuration option in nova.conf defines the list of filters that are applied by the nova-scheduler service. As mentioned, the default filters are:" +msgstr "" + +#: ./doc/config-reference/compute/section_compute-scheduler.xml:102(para) +msgid "The following sections describe the available filters." +msgstr "" + +#: ./doc/config-reference/compute/section_compute-scheduler.xml:105(title) +msgid "AggregateCoreFilter" +msgstr "" + +#: ./doc/config-reference/compute/section_compute-scheduler.xml:106(para) +msgid "Implements blueprint per-aggregate-resource-ratio. AggregateCoreFilter supports per-aggregate cpu_allocation_ratio. If the per-aggregate value is not found, the value falls back to the global setting." +msgstr "" + +#: ./doc/config-reference/compute/section_compute-scheduler.xml:113(title) +msgid "AggregateInstanceExtraSpecsFilter" +msgstr "" + +#: ./doc/config-reference/compute/section_compute-scheduler.xml:114(para) +msgid "Matches properties defined in an instance type's extra specs against admin-defined properties on a host aggregate. Works with specifications that are unscoped, or are scoped with aggregate_instance_extra_specs. See the host aggregates section for documentation on how to use this filter." +msgstr "" + +#: ./doc/config-reference/compute/section_compute-scheduler.xml:123(title) +msgid "AggregateMultiTenancyIsolation" +msgstr "" + +#: ./doc/config-reference/compute/section_compute-scheduler.xml:124(para) +msgid "Isolates tenants to specific host aggregates. If a host is in an aggregate that has the metadata key filter_tenant_id it only creates instances from that tenant (or list of tenants). A host can be in different aggregates. If a host does not belong to an aggregate with the metadata key, it can create instances from all tenants." +msgstr "" + +#: ./doc/config-reference/compute/section_compute-scheduler.xml:134(title) +msgid "AggregateRamFilter" +msgstr "" + +#: ./doc/config-reference/compute/section_compute-scheduler.xml:135(para) +msgid "Implements blueprint per-aggregate-resource-ratio. Supports per-aggregate ram_allocation_ratio. If per-aggregate value is not found, it falls back to the default setting." +msgstr "" + +#: ./doc/config-reference/compute/section_compute-scheduler.xml:143(title) +msgid "AllHostsFilter" +msgstr "" + +#: ./doc/config-reference/compute/section_compute-scheduler.xml:144(para) +msgid "This is a no-op filter, it does not eliminate any of the available hosts." +msgstr "" + +#: ./doc/config-reference/compute/section_compute-scheduler.xml:148(title) +msgid "AvailabilityZoneFilter" +msgstr "" + +#: ./doc/config-reference/compute/section_compute-scheduler.xml:149(para) +msgid "Filters hosts by availability zone. This filter must be enabled for the scheduler to respect availability zones in requests." +msgstr "" + +#: ./doc/config-reference/compute/section_compute-scheduler.xml:154(title) +msgid "ComputeCapabilitiesFilter" +msgstr "" + +#: ./doc/config-reference/compute/section_compute-scheduler.xml:155(para) +msgid "Matches properties defined in an instance type's extra specs against compute capabilities." +msgstr "" + +#: ./doc/config-reference/compute/section_compute-scheduler.xml:157(para) +msgid "If an extra specs key contains a colon \":\", anything before the colon is treated as a namespace, and anything after the colon is treated as the key to be matched. If a namespace is present and is not 'capabilities', it is ignored by this filter." +msgstr "" + +#: ./doc/config-reference/compute/section_compute-scheduler.xml:163(para) +msgid "Disable the ComputeCapabilitiesFilter when using a Bare Metal configuration, due to bug 1129485" +msgstr "" + +#: ./doc/config-reference/compute/section_compute-scheduler.xml:170(title) +msgid "ComputeFilter" +msgstr "" + +#: ./doc/config-reference/compute/section_compute-scheduler.xml:171(para) +msgid "Passes all hosts that are operational and enabled." +msgstr "" + +#: ./doc/config-reference/compute/section_compute-scheduler.xml:173(para) +msgid "In general, this filter should always be enabled." +msgstr "" + +#: ./doc/config-reference/compute/section_compute-scheduler.xml:177(title) +msgid "CoreFilter" +msgstr "" + +#: ./doc/config-reference/compute/section_compute-scheduler.xml:178(para) +msgid "Only schedule instances on hosts if there are sufficient CPU cores available. If this filter is not set, the scheduler may over provision a host based on cores (for example, the virtual cores running on an instance may exceed the physical cores)." +msgstr "" + +#: ./doc/config-reference/compute/section_compute-scheduler.xml:183(para) +msgid "This filter can be configured to allow a fixed amount of vCPU overcommitment by using the cpu_allocation_ratio Configuration option in nova.conf. The default setting is:" +msgstr "" + +#: ./doc/config-reference/compute/section_compute-scheduler.xml:190(para) +msgid "With this setting, if 8 vCPUs are on a node, the scheduler allows instances up to 128 vCPU to be run on that node." +msgstr "" + +#: ./doc/config-reference/compute/section_compute-scheduler.xml:193(para) +msgid "To disallow vCPU overcommitment set:" +msgstr "" + +#: ./doc/config-reference/compute/section_compute-scheduler.xml:197(title) +msgid "DifferentHostFilter" +msgstr "" + +#: ./doc/config-reference/compute/section_compute-scheduler.xml:198(para) +msgid "Schedule the instance on a different host from a set of instances. To take advantage of this filter, the requester must pass a scheduler hint, using different_host as the key and a list of instance uuids as the value. This filter is the opposite of the SameHostFilter. Using the command-line tool, use the --hint flag. For example:" +msgstr "" + +#: ./doc/config-reference/compute/section_compute-scheduler.xml:210(para) +msgid "With the API, use the os:scheduler_hints key. For example:" +msgstr "" + +#: ./doc/config-reference/compute/section_compute-scheduler.xml:227(title) +msgid "DiskFilter" +msgstr "" + +#: ./doc/config-reference/compute/section_compute-scheduler.xml:228(para) +msgid "Only schedule instances on hosts if there is sufficient disk space available for root and ephemeral storage." +msgstr "" + +#: ./doc/config-reference/compute/section_compute-scheduler.xml:231(para) +msgid "This filter can be configured to allow a fixed amount of disk overcommitment by using the disk_allocation_ratio Configuration option in nova.conf. The default setting is:" +msgstr "" + +#: ./doc/config-reference/compute/section_compute-scheduler.xml:238(para) +msgid "Adjusting this value to greater than 1.0 enables scheduling instances while over committing disk resources on the node. This might be desirable if you use an image format that is sparse or copy on write such that each virtual instance does not require a 1:1 allocation of virtual disk to physical storage." +msgstr "" + +#: ./doc/config-reference/compute/section_compute-scheduler.xml:245(title) +msgid "GroupAffinityFilter" +msgstr "" + +#: ./doc/config-reference/compute/section_compute-scheduler.xml:246(para) +msgid "The GroupAffinityFilter ensures that an instance is scheduled on to a host from a set of group hosts. To take advantage of this filter, the requester must pass a scheduler hint, using group as the key and an arbitrary name as the value. Using the command-line tool, use the --hint flag. For example:" +msgstr "" + +#: ./doc/config-reference/compute/section_compute-scheduler.xml:258(title) +msgid "GroupAntiAffinityFilter" +msgstr "" + +#: ./doc/config-reference/compute/section_compute-scheduler.xml:259(para) +msgid "The GroupAntiAffinityFilter ensures that each instance in a group is on a different host. To take advantage of this filter, the requester must pass a scheduler hint, using group as the key and an arbitrary name as the value. Using the command-line tool, use the --hint flag. For example:" +msgstr "" + +#: ./doc/config-reference/compute/section_compute-scheduler.xml:271(title) +msgid "ImagePropertiesFilter" +msgstr "" + +#: ./doc/config-reference/compute/section_compute-scheduler.xml:272(para) +msgid "Filters hosts based on properties defined on the instance's image. It passes hosts that can support the specified image properties contained in the instance. Properties include the architecture, hypervisor type, and virtual machine mode. for example, an instance might require a host that runs an ARM-based processor and QEMU as the hypervisor. An image can be decorated with these properties by using:" +msgstr "" + +#: ./doc/config-reference/compute/section_compute-scheduler.xml:281(para) +msgid "The image properties that the filter checks for are:" +msgstr "" + +#: ./doc/config-reference/compute/section_compute-scheduler.xml:285(para) +msgid "architecture: Architecture describes the machine architecture required by the image. Examples are i686, x86_64, arm, and ppc64." +msgstr "" + +#: ./doc/config-reference/compute/section_compute-scheduler.xml:291(para) +msgid "hypervisor_type: Hypervisor type describes the hypervisor required by the image. Examples are xen, kvm, qemu, and xenapi." +msgstr "" + +#: ./doc/config-reference/compute/section_compute-scheduler.xml:297(para) +msgid "vm_mode: Virtual machine mode describes the hypervisor application binary interface (ABI) required by the image. Examples are 'xen' for Xen 3.0 paravirtual ABI, 'hvm' for native ABI, 'uml' for User Mode Linux paravirtual ABI, exe for container virt executable ABI." +msgstr "" + +#: ./doc/config-reference/compute/section_compute-scheduler.xml:308(title) +msgid "IsolatedHostsFilter" +msgstr "" + +#: ./doc/config-reference/compute/section_compute-scheduler.xml:309(para) +msgid "Allows the admin to define a special (isolated) set of images and a special (isolated) set of hosts, such that the isolated images can only run on the isolated hosts, and the isolated hosts can only run isolated images. The flag restrict_isolated_hosts_to_isolated_images can be used to force isolated hosts to only run isolated images." +msgstr "" + +#: ./doc/config-reference/compute/section_compute-scheduler.xml:315(para) +msgid "The admin must specify the isolated set of images and hosts in the nova.conf file using the isolated_hosts and isolated_images configuration options. For example: " +msgstr "" + +#: ./doc/config-reference/compute/section_compute-scheduler.xml:325(title) +msgid "JsonFilter" +msgstr "" + +#: ./doc/config-reference/compute/section_compute-scheduler.xml:330(para) +msgid "=" +msgstr "" + +#: ./doc/config-reference/compute/section_compute-scheduler.xml:333(para) +msgid "<" +msgstr "" + +#: ./doc/config-reference/compute/section_compute-scheduler.xml:336(para) +msgid ">" +msgstr "" + +#: ./doc/config-reference/compute/section_compute-scheduler.xml:339(para) +msgid "in" +msgstr "" + +#: ./doc/config-reference/compute/section_compute-scheduler.xml:342(para) +msgid "<=" +msgstr "" + +#: ./doc/config-reference/compute/section_compute-scheduler.xml:345(para) +msgid ">=" +msgstr "" + +#: ./doc/config-reference/compute/section_compute-scheduler.xml:348(para) +msgid "not" +msgstr "" + +#: ./doc/config-reference/compute/section_compute-scheduler.xml:351(para) +msgid "or" +msgstr "" + +#: ./doc/config-reference/compute/section_compute-scheduler.xml:354(para) +msgid "and" +msgstr "" + +#: ./doc/config-reference/compute/section_compute-scheduler.xml:358(para) +msgid "$free_ram_mb" +msgstr "" + +#: ./doc/config-reference/compute/section_compute-scheduler.xml:361(para) +msgid "$free_disk_mb" +msgstr "" + +#: ./doc/config-reference/compute/section_compute-scheduler.xml:364(para) +msgid "$total_usable_ram_mb" +msgstr "" + +#: ./doc/config-reference/compute/section_compute-scheduler.xml:367(para) +msgid "$vcpus_total" +msgstr "" + +#: ./doc/config-reference/compute/section_compute-scheduler.xml:370(para) +msgid "$vcpus_used" +msgstr "" + +#: ./doc/config-reference/compute/section_compute-scheduler.xml:326(para) +msgid "The JsonFilter allows a user to construct a custom filter by passing a scheduler hint in JSON format. The following operators are supported:The filter supports the following variables:Using the command-line tool, use the --hint flag:" +msgstr "" + +#: ./doc/config-reference/compute/section_compute-scheduler.xml:377(para) ./doc/config-reference/compute/section_compute-scheduler.xml:436(para) ./doc/config-reference/compute/section_compute-scheduler.xml:482(para) +msgid "With the API, use the os:scheduler_hints key:" +msgstr "" + +#: ./doc/config-reference/compute/section_compute-scheduler.xml:393(title) +msgid "RamFilter" +msgstr "" + +#: ./doc/config-reference/compute/section_compute-scheduler.xml:394(para) +msgid "Only schedule instances on hosts that have sufficient RAM available. If this filter is not set, the scheduler may over provision a host based on RAM (for example, the RAM allocated by virtual machine instances may exceed the physical RAM)." +msgstr "" + +#: ./doc/config-reference/compute/section_compute-scheduler.xml:399(para) +msgid "This filter can be configured to allow a fixed amount of RAM overcommitment by using the ram_allocation_ratio configuration option in nova.conf. The default setting is:" +msgstr "" + +#: ./doc/config-reference/compute/section_compute-scheduler.xml:406(para) +msgid "With this setting, if there is 1GB of free RAM, the scheduler allows instances up to size 1.5GB to be run on that instance." +msgstr "" + +#: ./doc/config-reference/compute/section_compute-scheduler.xml:411(title) +msgid "RetryFilter" +msgstr "" + +#: ./doc/config-reference/compute/section_compute-scheduler.xml:412(para) +msgid "Filter out hosts that have already been attempted for scheduling purposes. If the scheduler selects a host to respond to a service request, and the host fails to respond to the request, this filter prevents the scheduler from retrying that host for the service request." +msgstr "" + +#: ./doc/config-reference/compute/section_compute-scheduler.xml:417(para) +msgid "This filter is only useful if the scheduler_max_attempts configuration option is set to a value greater than zero." +msgstr "" + +#: ./doc/config-reference/compute/section_compute-scheduler.xml:423(title) +msgid "SameHostFilter" +msgstr "" + +#: ./doc/config-reference/compute/section_compute-scheduler.xml:424(para) +msgid "Schedule the instance on the same host as another instance in a set of instances. To take advantage of this filter, the requester must pass a scheduler hint, using same_host as the key and a list of instance uuids as the value. This filter is the opposite of the DifferentHostFilter. Using the command-line tool, use the --hint flag:" +msgstr "" + +#: ./doc/config-reference/compute/section_compute-scheduler.xml:453(title) +msgid "SimpleCIDRAffinityFilter" +msgstr "" + +#: ./doc/config-reference/compute/section_compute-scheduler.xml:454(para) +msgid "Schedule the instance based on host IP subnet range. To take advantage of this filter, the requester must specify a range of valid IP address in CIDR format, by passing two scheduler hints:" +msgstr "" + +#: ./doc/config-reference/compute/section_compute-scheduler.xml:460(literal) +msgid "build_near_host_ip" +msgstr "" + +#: ./doc/config-reference/compute/section_compute-scheduler.xml:462(para) +msgid "The first IP address in the subnet (for example, 192.168.1.1)" +msgstr "" + +#: ./doc/config-reference/compute/section_compute-scheduler.xml:468(literal) +msgid "cidr" +msgstr "" + +#: ./doc/config-reference/compute/section_compute-scheduler.xml:470(para) +msgid "The CIDR that corresponds to the subnet (for example, /24)" +msgstr "" + +#: ./doc/config-reference/compute/section_compute-scheduler.xml:476(para) +msgid "Using the command-line tool, use the --hint flag. For example, to specify the IP subnet 192.168.1.1/24" +msgstr "" + +#: ./doc/config-reference/compute/section_compute-scheduler.xml:499(title) +msgid "Weights" +msgstr "" + +#: ./doc/config-reference/compute/section_compute-scheduler.xml:501(para) +msgid "The Filter Scheduler weighs hosts based on the config option scheduler_weight_classes, this defaults to nova.scheduler.weights.all_weighers, which selects the only weigher available -- the RamWeigher. Hosts are then weighed and sorted with the largest weight winning." +msgstr "" + +#: ./doc/config-reference/compute/section_compute-scheduler.xml:510(para) +msgid "The default is to spread instances across all hosts evenly. Set the ram_weight_multiplier option to a negative number if you prefer stacking instead of spreading." +msgstr "" + +#: ./doc/config-reference/compute/section_compute-scheduler.xml:516(title) +msgid "Chance scheduler" +msgstr "" + +#: ./doc/config-reference/compute/section_compute-scheduler.xml:518(para) +msgid "As an administrator, you work with the Filter Scheduler. However, the Compute service also uses the Chance Scheduler, nova.scheduler.chance.ChanceScheduler, which randomly selects from lists of filtered hosts. It is the default volume scheduler." +msgstr "" + +#: ./doc/config-reference/compute/section_compute-cells.xml:10(title) +msgid "Cells" +msgstr "" + +#: ./doc/config-reference/compute/section_compute-cells.xml:12(para) +msgid "Cells functionality allows you to scale an OpenStack Compute cloud in a more distributed fashion without having to use complicated technologies like database and message queue clustering. It is intended to support very large deployments." +msgstr "" + +#: ./doc/config-reference/compute/section_compute-cells.xml:16(para) +msgid "When this functionality is enabled, the hosts in an OpenStack Compute cloud are partitioned into groups called cells. Cells are configured as a tree. The top-level cell should have a host that runs a nova-api service, but no nova-compute services. Each child cell should run all of the typical nova-* services in a regular Compute cloud except for nova-api. You can think of cells as a normal Compute deployment in that each cell has its own database server and message queue broker." +msgstr "" + +#: ./doc/config-reference/compute/section_compute-cells.xml:24(para) +msgid "The nova-cells service handles communication between cells and selects cells for new instances. This service is required for every cell. Communication between cells is pluggable, and currently the only option is communication through RPC." +msgstr "" + +#: ./doc/config-reference/compute/section_compute-cells.xml:28(para) +msgid "Cells scheduling is separate from host scheduling. nova-cells first picks a cell (now randomly, but future releases plan to add filtering/weighing functionality, and decisions will be based on broadcasts of capacity/capabilities). Once a cell is selected and the new build request reaches its nova-cells service, it is sent over to the host scheduler in that cell and the build proceeds as it would have without cells." +msgstr "" + +#: ./doc/config-reference/compute/section_compute-cells.xml:35(para) +msgid "Cell functionality is currently considered experimental." +msgstr "" + +#: ./doc/config-reference/compute/section_compute-cells.xml:38(title) +msgid "Cell configuration options" +msgstr "" + +#: ./doc/config-reference/compute/section_compute-cells.xml:43(literal) +msgid "enable" +msgstr "" + +#: ./doc/config-reference/compute/section_compute-cells.xml:45(para) +msgid "Set this is True to turn on cell functionality, which is off by default." +msgstr "" + +#: ./doc/config-reference/compute/section_compute-cells.xml:50(literal) +msgid "name" +msgstr "" + +#: ./doc/config-reference/compute/section_compute-cells.xml:52(para) +msgid "Name of the current cell. This must be unique for each cell." +msgstr "" + +#: ./doc/config-reference/compute/section_compute-cells.xml:56(literal) +msgid "capabilities" +msgstr "" + +#: ./doc/config-reference/compute/section_compute-cells.xml:58(para) +msgid "List of arbitrary key=value pairs defining capabilities of the current cell. Values include hypervisor=xenserver;kvm,os=linux;windows." +msgstr "" + +#: ./doc/config-reference/compute/section_compute-cells.xml:66(literal) +msgid "call_timeout" +msgstr "" + +#: ./doc/config-reference/compute/section_compute-cells.xml:68(para) +msgid "How long in seconds to wait for replies from calls between cells." +msgstr "" + +#: ./doc/config-reference/compute/section_compute-cells.xml:73(term) +msgid "scheduler_filter_classes" +msgstr "" + +#: ./doc/config-reference/compute/section_compute-cells.xml:75(para) +msgid "Filter classes that the cells scheduler should use. By default, uses \"nova.cells.filters.all_filters\" to map to all cells filters included with Compute." +msgstr "" + +#: ./doc/config-reference/compute/section_compute-cells.xml:81(term) +msgid "scheduler_weight_classes" +msgstr "" + +#: ./doc/config-reference/compute/section_compute-cells.xml:82(para) +msgid "Weight classes the cells scheduler should use. By default, uses \"nova.cells.weights.all_weighers\" to map to all cells weight algorithms (weighers) included with Compute." +msgstr "" + +#: ./doc/config-reference/compute/section_compute-cells.xml:88(term) +msgid "ram_weight_multiplier" +msgstr "" + +#: ./doc/config-reference/compute/section_compute-cells.xml:90(para) +msgid "Multiplier used for weighing ram. Negative numbers mean you want Compute to stack VMs on one host instead of spreading out new VMs to more hosts in the cell. Default value is 10.0." +msgstr "" + +#: ./doc/config-reference/compute/section_compute-cells.xml:39(para) +msgid "Cells are disabled by default. All cell-related configuration options go under a [cells] section in nova.conf. The following cell-related options are currently supported:" +msgstr "" + +#: ./doc/config-reference/compute/section_compute-cells.xml:99(title) +msgid "Configure the API (top-level) cell" +msgstr "" + +#: ./doc/config-reference/compute/section_compute-cells.xml:100(para) +msgid "The compute API class must be changed in the API cell so that requests can be proxied through nova-cells down to the correct cell properly. Add the following to nova.conf in the API cell:" +msgstr "" + +#: ./doc/config-reference/compute/section_compute-cells.xml:112(title) +msgid "Configure the child cells" +msgstr "" + +#: ./doc/config-reference/compute/section_compute-cells.xml:121(replaceable) +msgid "cell1" +msgstr "" + +#: ./doc/config-reference/compute/section_compute-cells.xml:113(para) +msgid "Add the following to nova.conf in the child cells, replacing cell1 with the name of each cell:" +msgstr "" + +#: ./doc/config-reference/compute/section_compute-cells.xml:124(title) +msgid "Configure the database in each cell" +msgstr "" + +#: ./doc/config-reference/compute/section_compute-cells.xml:125(para) +msgid "Before bringing the services online, the database in each cell needs to be configured with information about related cells. In particular, the API cell needs to know about its immediate children, and the child cells must know about their immediate agents. The information needed is the RabbitMQ server credentials for the particular cell." +msgstr "" + +#: ./doc/config-reference/compute/section_compute-cells.xml:130(para) +msgid "Use the command to add this information to the database in each cell:" +msgstr "" + +#: ./doc/config-reference/compute/section_compute-cells.xml:152(para) +msgid "As an example, assume we have an API cell named api and a child cell named cell1. Within the api cell, we have the following RabbitMQ server info:" +msgstr "" + +#: ./doc/config-reference/compute/section_compute-cells.xml:160(para) +msgid "And in the child cell named cell1 we have the following RabbitMQ server info:" +msgstr "" + +#: ./doc/config-reference/compute/section_compute-cells.xml:167(para) +msgid "We would run this in the API cell, as root." +msgstr "" + +#: ./doc/config-reference/compute/section_compute-cells.xml:169(para) +msgid "Repeat the above for all child cells." +msgstr "" + +#: ./doc/config-reference/compute/section_compute-cells.xml:170(para) +msgid "In the child cell, we would run the following, as root:" +msgstr "" + +#: ./doc/config-reference/compute/section_compute-cells.xml:176(title) +msgid "Cell scheduling configuration" +msgstr "" + +#: ./doc/config-reference/compute/section_compute-cells.xml:177(para) +msgid "To determine the best cell for launching a new instance, Compute uses a set of filters and weights configured in /etc/nova/nova.conf. The following options are available to prioritize cells for scheduling:" +msgstr "" + +#: ./doc/config-reference/compute/section_compute-cells.xml:183(para) +msgid "scheduler_filter_classes - Specifies the list of filter classes. By default nova.cells.weights.all_filters is specified, which maps to all cells filters included with Compute (see ." +msgstr "" + +#: ./doc/config-reference/compute/section_compute-cells.xml:189(para) +msgid "scheduler_weight_classes - Specifies the list of weight classes. By default nova.cells.weights.all_weighers is specified, which maps to all cell weight algorithms (weighers) included with Compute. The following modules are available:" +msgstr "" + +#: ./doc/config-reference/compute/section_compute-cells.xml:194(para) +msgid "mute_child: Downgrades the likelihood of child cells being chosen for scheduling requests, which haven't sent capacity or capability updates in a while. Options include mute_weight_multiplier (multiplier for mute children; value should be negative) and mute_weight_value (assigned to mute children; should be a positive value)." +msgstr "" + +#: ./doc/config-reference/compute/section_compute-cells.xml:203(para) +msgid "ram_by_instance_type: Select cells with the most RAM capacity for the instance type being requested. Because higher weights win, Compute returns the number of available units for the instance type requested. The ram_weight_multiplier option defaults to 10.0 that adds to the weight by a factor of 10. Use a negative number to stack VMs on one host instead of spreading out new VMs to more hosts in the cell." +msgstr "" + +#: ./doc/config-reference/compute/section_compute-cells.xml:211(para) +msgid "weight_offset: Allows modifying the database to weight a particular cell. You can use this when you want to disable a cell (for example, '0'), or to set a default cell by making its weight_offset very high (for example, '999999999999999'). The highest weight will be the first cell to be scheduled for launching an instance." +msgstr "" + +#: ./doc/config-reference/compute/section_compute-cells.xml:219(para) +msgid "Additionally, the following options are available for the cell scheduler:" +msgstr "" + +#: ./doc/config-reference/compute/section_compute-cells.xml:223(para) +msgid "scheduler_retries - Specifies how many times the scheduler tries to launch a new instance when no cells are available (default=10)." +msgstr "" + +#: ./doc/config-reference/compute/section_compute-cells.xml:227(para) +msgid "scheduler_retry_delay - Specifies the delay (in seconds) between retries (default=2)." +msgstr "" + +#: ./doc/config-reference/compute/section_compute-cells.xml:232(para) +msgid "As an admin user, you can also add a filter that directs builds to a particular cell. The policy.json file must have a line with \"cells_scheduler_filter:TargetCellFilter\" : \"is_admin:True\" to let an admin user specify a scheduler hint to direct a build to a particular cell." +msgstr "" + +#: ./doc/config-reference/compute/section_compute-cells.xml:239(title) +msgid "Optional cell configuration" +msgstr "" + +#: ./doc/config-reference/compute/section_compute-cells.xml:240(para) +msgid "Cells currently keeps all inter-cell communication data, including user names and passwords, in the database. This is undesirable and unnecessary since cells data isn't updated very frequently. Instead, create a JSON file to input cells data specified via a [cells]cells_config option. When specified, the database is no longer consulted when reloading cells data. The file will need the columns present in the Cell model (excluding common database fields and the id column). The queue connection information must be specified through a transport_url field, instead of username, password, and so on. The transport_url has the following form:" +msgstr "" + +#: ./doc/config-reference/compute/section_compute-cells.xml:255(para) +msgid "The scheme can be either qpid or rabbit, as shown previously. The following sample shows this optional configuration:" +msgstr "" + +#: ./doc/config-reference/compute/section_compute-security.xml:10(title) +msgid "Security hardening" +msgstr "" + +#: ./doc/config-reference/compute/section_compute-security.xml:11(para) +msgid "OpenStack Compute can be integrated with various third-party technologies to increase security. For more information, see the OpenStack Security Guide." +msgstr "" + +#: ./doc/config-reference/compute/section_hypervisor_qemu.xml:7(title) +msgid "QEMU" +msgstr "" + +#: ./doc/config-reference/compute/section_hypervisor_qemu.xml:8(para) +msgid "From the perspective of the Compute service, the QEMU hypervisor is very similar to the KVM hypervisor. Both are controlled through libvirt, both support the same feature set, and all virtual machine images that are compatible with KVM are also compatible with QEMU. The main difference is that QEMU does not support native virtualization. Consequently, QEMU has worse performance than KVM and is a poor choice for a production deployment." +msgstr "" + +#: ./doc/config-reference/compute/section_hypervisor_qemu.xml:15(para) +msgid "Running on older hardware that lacks virtualization support." +msgstr "" + +#: ./doc/config-reference/compute/section_hypervisor_qemu.xml:19(para) +msgid "Running the Compute service inside of a virtual machine for development or testing purposes, where the hypervisor does not support native virtualization for guests." +msgstr "" + +#: ./doc/config-reference/compute/section_hypervisor_qemu.xml:13(para) +msgid "The typical uses cases for QEMU are" +msgstr "" + +#: ./doc/config-reference/compute/section_hypervisor_qemu.xml:25(para) +msgid "To enable QEMU, add these settings to nova.conf:" +msgstr "" + +#: ./doc/config-reference/compute/section_hypervisor_qemu.xml:29(para) +msgid "For some operations you may also have to install the utility:" +msgstr "" + +#: ./doc/config-reference/compute/section_hypervisor_qemu.xml:31(para) +msgid "On Ubuntu: " +msgstr "" + +#: ./doc/config-reference/compute/section_hypervisor_qemu.xml:34(para) +msgid "On RHEL, Fedora or CentOS: " +msgstr "" + +#: ./doc/config-reference/compute/section_hypervisor_qemu.xml:37(para) +msgid "On openSUSE: " +msgstr "" + +#: ./doc/config-reference/compute/section_hypervisor_qemu.xml:40(para) +msgid "The QEMU hypervisor supports the following virtual machine image formats:" +msgstr "" + +#: ./doc/config-reference/compute/section_hypervisor_qemu.xml:53(title) +msgid "Tips and fixes for QEMU on RHEL" +msgstr "" + +#: ./doc/config-reference/compute/section_hypervisor_qemu.xml:54(para) +msgid "If you are testing OpenStack in a virtual machine, you need to configure nova to use qemu without KVM and hardware virtualization. The second command relaxes SELinux rules to allow this mode of operation ( https://bugzilla.redhat.com/show_bug.cgi?id=753589). The last two commands here work around a libvirt issue fixed in RHEL 6.4. Note nested virtualization will be the much slower TCG variety, and you should provide lots of memory to the top level guest, as the OpenStack-created guests default to 2GM RAM with no overcommit." +msgstr "" + +#: ./doc/config-reference/compute/section_hypervisor_qemu.xml:65(para) +msgid "The second command, , may take a while." +msgstr "" + +#: ./doc/config-reference/compute/section_compute-configure-migrations.xml:10(title) +msgid "Configure migrations" +msgstr "" + +#: ./doc/config-reference/compute/section_compute-configure-migrations.xml:12(para) +msgid "Only cloud administrators can perform live migrations. If your cloud is configured to use cells, you can perform live migration within but not between cells." +msgstr "" + +#: ./doc/config-reference/compute/section_compute-configure-migrations.xml:16(para) +msgid "Migration enables an administrator to move a virtual machine instance from one compute host to another. This feature is useful when a compute host requires maintenance. Migration can also be useful to redistribute the load when many VM instances are running on a specific physical machine." +msgstr "" + +#: ./doc/config-reference/compute/section_compute-configure-migrations.xml:21(para) +msgid "The migration types are:" +msgstr "" + +#: ./doc/config-reference/compute/section_compute-configure-migrations.xml:24(para) +msgid "Migration (or non-live migration). The instance is shut down (and the instance knows that it was rebooted) for a period of time to be moved to another hypervisor." +msgstr "" + +#: ./doc/config-reference/compute/section_compute-configure-migrations.xml:30(para) +msgid "Live migration (or true live migration). Almost no instance downtime. Useful when the instances must be kept running during the migration." +msgstr "" + +#: ./doc/config-reference/compute/section_compute-configure-migrations.xml:35(para) +msgid "The types of live migration are:" +msgstr "" + +#: ./doc/config-reference/compute/section_compute-configure-migrations.xml:38(para) +msgid "Shared storage-based live migration. Both hypervisors have access to shared storage." +msgstr "" + +#: ./doc/config-reference/compute/section_compute-configure-migrations.xml:43(para) +msgid "Block live migration. No shared storage is required." +msgstr "" + +#: ./doc/config-reference/compute/section_compute-configure-migrations.xml:47(para) +msgid "Volume-backed live migration. When instances are backed by volumes rather than ephemeral disk, no shared storage is required, and migration is supported (currently only in libvirt-based hypervisors)." +msgstr "" + +#: ./doc/config-reference/compute/section_compute-configure-migrations.xml:54(para) +msgid "The following sections describe how to configure your hosts and compute nodes for migrations by using the KVM and XenServer hypervisors." +msgstr "" + +#: ./doc/config-reference/compute/section_compute-configure-migrations.xml:58(title) +msgid "KVM-Libvirt" +msgstr "" + +#: ./doc/config-reference/compute/section_compute-configure-migrations.xml:60(title) ./doc/config-reference/compute/section_compute-configure-migrations.xml:293(title) ./doc/config-reference/compute/section_compute-configure-migrations.xml:368(title) ./doc/config-reference/block-storage/drivers/xen-sm-driver.xml:117(title) +msgid "Prerequisites" +msgstr "" + +#: ./doc/config-reference/compute/section_compute-configure-migrations.xml:62(para) +msgid "Hypervisor: KVM with libvirt" +msgstr "" + +#: ./doc/config-reference/compute/section_compute-configure-migrations.xml:66(para) +msgid "Shared storage:NOVA-INST-DIR/instances/ (for example, /var/lib/nova/instances) has to be mounted by shared storage. This guide uses NFS but other options, including the OpenStack Gluster Connector are available." +msgstr "" + +#: ./doc/config-reference/compute/section_compute-configure-migrations.xml:75(para) +msgid "Instances: Instance can be migrated with iSCSI based volumes" +msgstr "" + +#: ./doc/config-reference/compute/section_compute-configure-migrations.xml:80(title) ./doc/config-reference/compute/section_compute-configure-migrations.xml:377(title) +msgid "Notes" +msgstr "" + +#: ./doc/config-reference/compute/section_compute-configure-migrations.xml:83(para) +msgid "Because the Compute service does not use the libvirt live migration functionality by default, guests are suspended before migration and might experience several minutes of downtime. For details, see ." +msgstr "" + +#: ./doc/config-reference/compute/section_compute-configure-migrations.xml:90(para) +msgid "This guide assumes the default value for in your nova.conf file (NOVA-INST-DIR/instances). If you have changed the state_path or instances_path variables, modify accordingly." +msgstr "" + +#: ./doc/config-reference/compute/section_compute-configure-migrations.xml:99(para) +msgid "You must specify vncserver_listen=0.0.0.0 or live migration does not work correctly." +msgstr "" + +#: ./doc/config-reference/compute/section_compute-configure-migrations.xml:106(title) +msgid "Example Compute installation environment" +msgstr "" + +#: ./doc/config-reference/compute/section_compute-configure-migrations.xml:108(para) +msgid "Prepare at least three servers; for example, HostA, HostB, and HostC." +msgstr "" + +#: ./doc/config-reference/compute/section_compute-configure-migrations.xml:113(para) +msgid "HostA is the Cloud Controller, and should run these services: nova-api, nova-scheduler, nova-network, cinder-volume, and nova-objectstore." +msgstr "" + +#: ./doc/config-reference/compute/section_compute-configure-migrations.xml:123(para) +msgid "HostB and HostC are the compute nodes that run nova-compute." +msgstr "" + +#: ./doc/config-reference/compute/section_compute-configure-migrations.xml:129(para) +msgid "Ensure that NOVA-INST-DIR (set with state_path in the nova.conf file) is the same on all hosts." +msgstr "" + +#: ./doc/config-reference/compute/section_compute-configure-migrations.xml:136(para) +msgid "In this example, HostA is the NFSv4 server that exports NOVA-INST-DIR/instances, and HostB and HostC mount it." +msgstr "" + +#: ./doc/config-reference/compute/section_compute-configure-migrations.xml:144(title) +msgid "To configure your system" +msgstr "" + +#: ./doc/config-reference/compute/section_compute-configure-migrations.xml:146(para) +msgid "Configure your DNS or /etc/hosts and ensure it is consistent across all hosts. Make sure that the three hosts can perform name resolution with each other. As a test, use the command to ping each host from one another." +msgstr "" + +#: ./doc/config-reference/compute/section_compute-configure-migrations.xml:156(para) +msgid "Ensure that the UID and GID of your nova and libvirt users are identical between each of your servers. This ensures that the permissions on the NFS mount works correctly." +msgstr "" + +#: ./doc/config-reference/compute/section_compute-configure-migrations.xml:162(para) +msgid "Follow the instructions at the Ubuntu NFS HowTo to setup an NFS server on HostA, and NFS Clients on HostB and HostC." +msgstr "" + +#: ./doc/config-reference/compute/section_compute-configure-migrations.xml:168(para) +msgid "The aim is to export NOVA-INST-DIR/instances from HostA, and have it readable and writable by the nova user on HostB and HostC." +msgstr "" + +#: ./doc/config-reference/compute/section_compute-configure-migrations.xml:175(para) +msgid "Using your knowledge from the Ubuntu documentation, configure the NFS server at HostA by adding this line to the /etc/exports file:" +msgstr "" + +#: ./doc/config-reference/compute/section_compute-configure-migrations.xml:179(replaceable) ./doc/config-reference/compute/section_compute-configure-migrations.xml:194(replaceable) ./doc/config-reference/compute/section_compute-configure-migrations.xml:199(replaceable) ./doc/config-reference/compute/section_compute-configure-migrations.xml:206(replaceable) ./doc/config-reference/compute/section_compute-configure-migrations.xml:211(replaceable) +msgid "NOVA-INST-DIR" +msgstr "" + +#: ./doc/config-reference/compute/section_compute-configure-migrations.xml:180(para) +msgid "Change the subnet mask (255.255.0.0) to the appropriate value to include the IP addresses of HostB and HostC. Then restart the NFS server:" +msgstr "" + +#: ./doc/config-reference/compute/section_compute-configure-migrations.xml:188(para) +msgid "Set the 'execute/search' bit on your shared directory." +msgstr "" + +#: ./doc/config-reference/compute/section_compute-configure-migrations.xml:190(para) +msgid "On both compute nodes, make sure to enable the 'execute/search' bit to allow qemu to be able to use the images within the directories. On all hosts, run the following command:" +msgstr "" + +#: ./doc/config-reference/compute/section_compute-configure-migrations.xml:197(para) +msgid "Configure NFS at HostB and HostC by adding this line to the /etc/fstab file:" +msgstr "" + +#: ./doc/config-reference/compute/section_compute-configure-migrations.xml:200(para) +msgid "Make sure that you can mount the exported directory can be mounted:" +msgstr "" + +#: ./doc/config-reference/compute/section_compute-configure-migrations.xml:203(para) +msgid "Check that HostA can see the \"NOVA-INST-DIR/instances/\" directory:" +msgstr "" + +#: ./doc/config-reference/compute/section_compute-configure-migrations.xml:206(filename) ./doc/config-reference/compute/section_compute-configure-migrations.xml:211(filename) +msgid "/instances/" +msgstr "" + +#: ./doc/config-reference/compute/section_compute-configure-migrations.xml:208(para) +msgid "Perform the same check at HostB and HostC, paying special attention to the permissions (nova should be able to write):" +msgstr "" + +#: ./doc/config-reference/compute/section_compute-configure-migrations.xml:224(para) +msgid "Update the libvirt configurations. Modify the /etc/libvirt/libvirtd.conf file:" +msgstr "" + +#: ./doc/config-reference/compute/section_compute-configure-migrations.xml:234(para) +msgid "Modify the /etc/libvirt/qemu.conf file:" +msgstr "" + +#: ./doc/config-reference/compute/section_compute-configure-migrations.xml:238(para) +msgid "Modify the /etc/init/libvirt-bin.conf file:" +msgstr "" + +#: ./doc/config-reference/compute/section_compute-configure-migrations.xml:243(para) +msgid "Modify the /etc/default/libvirt-bin file:" +msgstr "" + +#: ./doc/config-reference/compute/section_compute-configure-migrations.xml:247(para) +msgid "Restart libvirt. After you run the command, ensure that libvirt is successfully restarted:" +msgstr "" + +#: ./doc/config-reference/compute/section_compute-configure-migrations.xml:254(para) +msgid "Configure your firewall to allow libvirt to communicate between nodes." +msgstr "" + +#: ./doc/config-reference/compute/section_compute-configure-migrations.xml:256(para) +msgid "For information about ports that are used with libvirt, see the libvirt documentation By default, libvirt listens on TCP port 16509 and an ephemeral TCP range from 49152 to 49261 is used for the KVM communications. As this guide has disabled libvirt auth, you should take good care that these ports are only open to hosts within your installation." +msgstr "" + +#: ./doc/config-reference/compute/section_compute-configure-migrations.xml:267(para) +msgid "You can now configure options for live migration. In most cases, you do not need to configure any options. The following chart is for advanced usage only." +msgstr "" + +#: ./doc/config-reference/compute/section_compute-configure-migrations.xml:274(title) +msgid "Enable true live migration" +msgstr "" + +#: ./doc/config-reference/compute/section_compute-configure-migrations.xml:275(para) +msgid "By default, the Compute service does not use the libvirt live migration functionality. To enable this functionality, add the following line to the nova.conf file:" +msgstr "" + +#: ./doc/config-reference/compute/section_compute-configure-migrations.xml:280(para) +msgid "The Compute service does not use libvirt's live migration by default because there is a risk that the migration process never ends. This can happen if the guest operating system dirties blocks on the disk faster than they can migrated." +msgstr "" + +#: ./doc/config-reference/compute/section_compute-configure-migrations.xml:291(title) +msgid "Shared storage" +msgstr "" + +#: ./doc/config-reference/compute/section_compute-configure-migrations.xml:295(para) +msgid "Compatible XenServer hypervisors. For more information, see the Requirements for Creating Resource Pools section of the XenServer Administrator's Guide." +msgstr "" + +#: ./doc/config-reference/compute/section_compute-configure-migrations.xml:304(para) +msgid "Shared storage. An NFS export, visible to all XenServer hosts." +msgstr "" + +#: ./doc/config-reference/compute/section_compute-configure-migrations.xml:307(para) +msgid "For the supported NFS versions, see the NFS VHD section of the XenServer Administrator's Guide." +msgstr "" + +#: ./doc/config-reference/compute/section_compute-configure-migrations.xml:314(para) +msgid "To use shared storage live migration with XenServer hypervisors, the hosts must be joined to a XenServer pool. To create that pool, a host aggregate must be created with special metadata. This metadata is used by the XAPI plug-ins to establish the pool." +msgstr "" + +#: ./doc/config-reference/compute/section_compute-configure-migrations.xml:320(title) +msgid "To use shared storage live migration with XenServer hypervisors" +msgstr "" + +#: ./doc/config-reference/compute/section_compute-configure-migrations.xml:323(para) +msgid "Add an NFS VHD storage to your master XenServer, and set it as default SR. For more information, please refer to the NFS VHD section in the XenServer Administrator's Guide." +msgstr "" + +#: ./doc/config-reference/compute/section_compute-configure-migrations.xml:331(para) +msgid "Configure all the compute nodes to use the default sr for pool operations. Add this line to your nova.conf configuration files across your compute nodes:" +msgstr "" + +#: ./doc/config-reference/compute/section_compute-configure-migrations.xml:338(para) +msgid "Create a host aggregate:" +msgstr "" + +#: ./doc/config-reference/compute/section_compute-configure-migrations.xml:340(para) +msgid "The command displays a table that contains the ID of the newly created aggregate." +msgstr "" + +#: ./doc/config-reference/compute/section_compute-configure-migrations.xml:342(para) +msgid "Now add special metadata to the aggregate, to mark it as a hypervisor pool:" +msgstr "" + +#: ./doc/config-reference/compute/section_compute-configure-migrations.xml:346(para) +msgid "Make the first compute node part of that aggregate:" +msgstr "" + +#: ./doc/config-reference/compute/section_compute-configure-migrations.xml:349(para) +msgid "At this point, the host is part of a XenServer pool." +msgstr "" + +#: ./doc/config-reference/compute/section_compute-configure-migrations.xml:353(para) +msgid "Add additional hosts to the pool:" +msgstr "" + +#: ./doc/config-reference/compute/section_compute-configure-migrations.xml:356(para) +msgid "At this point, the added compute node and the host are shut down, to join the host to the XenServer pool. The operation fails, if any server other than the compute node is running/suspended on your host." +msgstr "" + +#: ./doc/config-reference/compute/section_compute-configure-migrations.xml:366(title) +msgid "Block migration" +msgstr "" + +#: ./doc/config-reference/compute/section_compute-configure-migrations.xml:370(para) +msgid "Compatible XenServer hypervisors. The hypervisors must support the Storage XenMotion feature. See your XenServer manual to make sure your edition has this feature." +msgstr "" + +#: ./doc/config-reference/compute/section_compute-configure-migrations.xml:380(para) +msgid "To use block migration, you must use the --block-migrate parameter with the live migration command." +msgstr "" + +#: ./doc/config-reference/compute/section_compute-configure-migrations.xml:385(para) +msgid "Block migration works only with EXT local storage SRs, and the server must not have any volumes attached." +msgstr "" + +#: ./doc/config-reference/networking/section_networking-plugins.xml:10(title) +msgid "Networking plug-ins" +msgstr "" + +#: ./doc/config-reference/networking/section_networking-plugins.xml:11(para) +msgid "OpenStack Networking introduces the concept of a plug-in, which is a back-end implementation of the OpenStack Networking API. A plug-in can use a variety of technologies to implement the logical API requests. Some OpenStack Networking plug-ins might use basic Linux VLANs and IP tables, while others might use more advanced technologies, such as L2-in-L3 tunneling or OpenFlow. These sections detail the configuration options for the various plug-ins." +msgstr "" + +#: ./doc/config-reference/networking/section_networking-plugins.xml:22(title) +msgid "BigSwitch configuration options" +msgstr "" + +#: ./doc/config-reference/networking/section_networking-plugins.xml:28(title) +msgid "Brocade configuration options" +msgstr "" + +#: ./doc/config-reference/networking/section_networking-plugins.xml:34(title) +msgid "CISCO configuration options" +msgstr "" + +#: ./doc/config-reference/networking/section_networking-plugins.xml:40(title) +msgid "CloudBase Hyper-V plug-in configuration options (deprecated)" +msgstr "" + +#: ./doc/config-reference/networking/section_networking-plugins.xml:47(title) +msgid "CloudBase Hyper-V Agent configuration options" +msgstr "" + +#: ./doc/config-reference/networking/section_networking-plugins.xml:54(title) +msgid "Linux bridge plug-in configuration options (deprecated)" +msgstr "" + +#: ./doc/config-reference/networking/section_networking-plugins.xml:61(title) +msgid "Linux bridge Agent configuration options" +msgstr "" + +#: ./doc/config-reference/networking/section_networking-plugins.xml:68(title) +msgid "Mellanox configuration options" +msgstr "" + +#: ./doc/config-reference/networking/section_networking-plugins.xml:74(title) +msgid "Meta Plug-in configuration options" +msgstr "" + +#: ./doc/config-reference/networking/section_networking-plugins.xml:75(para) +msgid "The Meta Plug-in allows you to use multiple plug-ins at the same time." +msgstr "" + +#: ./doc/config-reference/networking/section_networking-plugins.xml:83(title) +msgid "MidoNet configuration options" +msgstr "" + +#: ./doc/config-reference/networking/section_networking-plugins.xml:89(title) +msgid "NEC configuration options" +msgstr "" + +#: ./doc/config-reference/networking/section_networking-plugins.xml:95(title) +msgid "Nicira NVP configuration options" +msgstr "" + +#: ./doc/config-reference/networking/section_networking-plugins.xml:101(title) +msgid "Open vSwitch plug-in configuration options (deprecated)" +msgstr "" + +#: ./doc/config-reference/networking/section_networking-plugins.xml:108(title) +msgid "Open vSwitch Agent configuration options" +msgstr "" + +#: ./doc/config-reference/networking/section_networking-plugins.xml:115(title) +msgid "PLUMgrid configuration options" +msgstr "" + +#: ./doc/config-reference/networking/section_networking-plugins.xml:121(title) +msgid "Ryu configuration options" +msgstr "" + +#: ./doc/config-reference/networking/section_networking-plugins-ml2.xml:10(title) +msgid "Modular Layer 2 (ml2) configuration options" +msgstr "" + +#: ./doc/config-reference/networking/section_networking-plugins-ml2.xml:11(para) +msgid "The Modular Layer 2 (ml2) plug-in has two components: network types and mechanisms. You can configure these components separately. This section describes these configuration options." +msgstr "" + +#: ./doc/config-reference/networking/section_networking-plugins-ml2.xml:16(title) +msgid "MTU bug with VXLAN tunnelling" +msgstr "" + +#: ./doc/config-reference/networking/section_networking-plugins-ml2.xml:17(para) +msgid "Due to a bug in Linux Bridge software maximum transmission unit (MTU) handling, using VXLAN tunnels does not work by default." +msgstr "" + +#: ./doc/config-reference/networking/section_networking-plugins-ml2.xml:22(para) +msgid "A simple workaround is to increase the MTU value of the physical interface and physical switch fabric by at least 50 bytes. For example, increase the MTU value to 1550. This value enables an automatic 50-byte MTU difference between the physical interface (1500) and the VXLAN interface (automatically 1500-50 = 1450). An MTU value of 1450 causes issues when virtual machine taps are configured at an MTU value of 1500." +msgstr "" + +#: ./doc/config-reference/networking/section_networking-plugins-ml2.xml:33(para) +msgid "Another workaround is to decrease the virtual ethernet devices' MTU. Set the option to 1450 in the neutron.conf file, and set all guest virtual machines' MTU to the same value by using a DHCP option. For information about how to use this option, see Configure OVS plug-in." +msgstr "" + +#: ./doc/config-reference/networking/section_networking-plugins-ml2.xml:48(title) +msgid "Modular Layer 2 (ml2) Flat Type configuration options" +msgstr "" + +#: ./doc/config-reference/networking/section_networking-plugins-ml2.xml:53(title) +msgid "Modular Layer 2 (ml2) VXLAN Type configuration options" +msgstr "" + +#: ./doc/config-reference/networking/section_networking-plugins-ml2.xml:58(title) +msgid "Modular Layer 2 (ml2) Arista Mechanism configuration options" +msgstr "" + +#: ./doc/config-reference/networking/section_networking-plugins-ml2.xml:64(title) +msgid "Modular Layer 2 (ml2) Cisco Mechanism configuration options" +msgstr "" + +#: ./doc/config-reference/networking/section_networking-plugins-ml2.xml:69(title) +msgid "Modular Layer 2 (ml2) L2 Population Mechanism configuration options" +msgstr "" + +#: ./doc/config-reference/networking/section_networking-plugins-ml2.xml:74(title) +msgid "Modular Layer 2 (ml2) Tail-f NCS Mechanism configuration options" +msgstr "" + +#: ./doc/config-reference/networking/section_networking-options-reference.xml:6(title) +msgid "Networking configuration options" +msgstr "" + +#: ./doc/config-reference/networking/section_networking-options-reference.xml:7(para) +msgid "The options and descriptions listed in this introduction are auto generated from the code in the Networking service project, which provides software-defined networking between VMs run in Compute. The list contains common options, while the subsections list the options for the various networking plug-ins." +msgstr "" + +#: ./doc/config-reference/networking/section_networking-options-reference.xml:20(para) +msgid "Use the following options to alter agent-related settings." +msgstr "" + +#: ./doc/config-reference/networking/section_networking-options-reference.xml:25(title) +msgid "API" +msgstr "" + +#: ./doc/config-reference/networking/section_networking-options-reference.xml:26(para) +msgid "Use the following options to alter API-related settings." +msgstr "" + +#: ./doc/config-reference/networking/section_networking-options-reference.xml:31(title) +msgid "Database" +msgstr "" + +#: ./doc/config-reference/networking/section_networking-options-reference.xml:32(para) +msgid "Use the following options to alter Database-related settings." +msgstr "" + +#: ./doc/config-reference/networking/section_networking-options-reference.xml:37(title) +msgid "Logging" +msgstr "" + +#: ./doc/config-reference/networking/section_networking-options-reference.xml:38(para) +msgid "Use the following options to alter logging settings." +msgstr "" + +#: ./doc/config-reference/networking/section_networking-options-reference.xml:43(title) +msgid "Metadata Agent" +msgstr "" + +#: ./doc/config-reference/networking/section_networking-options-reference.xml:44(para) +msgid "Use the following options in the metadata_agent.ini file for the Metadata agent." +msgstr "" + +#: ./doc/config-reference/networking/section_networking-options-reference.xml:50(title) +msgid "Policy" +msgstr "" + +#: ./doc/config-reference/networking/section_networking-options-reference.xml:51(para) +msgid "Use the following options in the neutron.conf file to change policy settings." +msgstr "" + +#: ./doc/config-reference/networking/section_networking-options-reference.xml:57(title) +msgid "Quotas" +msgstr "" + +#: ./doc/config-reference/networking/section_networking-options-reference.xml:58(para) +msgid "Use the following options in the neutron.conf file for the quota system." +msgstr "" + +#: ./doc/config-reference/networking/section_networking-options-reference.xml:64(title) +msgid "Scheduler" +msgstr "" + +#: ./doc/config-reference/networking/section_networking-options-reference.xml:65(para) +msgid "Use the following options in the neutron.conf file to change scheduler settings." +msgstr "" + +#: ./doc/config-reference/networking/section_networking-options-reference.xml:71(title) +msgid "Security Groups" +msgstr "" + +#: ./doc/config-reference/networking/section_networking-options-reference.xml:72(para) +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:78(title) +msgid "SSL" +msgstr "" + +#: ./doc/config-reference/networking/section_networking-options-reference.xml:79(para) +msgid "Use the following options in the neutron.conf file to enable SSL." +msgstr "" + +#: ./doc/config-reference/networking/section_networking-options-reference.xml:85(title) +msgid "Testing" +msgstr "" + +#: ./doc/config-reference/networking/section_networking-options-reference.xml:86(para) +msgid "Use the following options to alter testing-related features." +msgstr "" + +#: ./doc/config-reference/networking/section_networking-options-reference.xml:91(title) +msgid "WSGI" +msgstr "" + +#: ./doc/config-reference/networking/section_networking-options-reference.xml:92(para) +msgid "Use the following options in the neutron.conf file to configure the WSGI layer." +msgstr "" + +#: ./doc/config-reference/block-storage/section_backup-drivers.xml:6(title) +msgid "Backup drivers" +msgstr "" + +#: ./doc/config-reference/block-storage/section_backup-drivers.xml:7(para) +msgid "This section describes how to configure the cinder-backup service and its drivers." +msgstr "" + +#: ./doc/config-reference/block-storage/section_backup-drivers.xml:10(para) +msgid "The volume drivers are included with the Block Storage repository (https://github.com/openstack/cinder). To set a backup driver, use the backup_driver flag. By default there is no backup driver enabled." +msgstr "" + +#: ./doc/config-reference/block-storage/section_volume-drivers.xml:6(title) +msgid "Volume drivers" +msgstr "" + +#: ./doc/config-reference/block-storage/section_volume-drivers.xml:7(para) +msgid "To use different volume drivers for the cinder-volume service, use the parameters described in these sections." +msgstr "" + +#: ./doc/config-reference/block-storage/section_volume-drivers.xml:10(para) +msgid "The volume drivers are included in the Block Storage repository (https://github.com/openstack/cinder). To set a volume driver, use the volume_driver flag. The default is:" +msgstr "" + +#: ./doc/config-reference/block-storage/section_block-storage-overview.xml:6(title) +msgid "Introduction to the Block Storage Service" +msgstr "" + +#: ./doc/config-reference/block-storage/section_block-storage-overview.xml:7(para) +msgid "The Openstack Block Storage Service provides persistent block storage resources that OpenStack Compute instances can consume. This includes secondary attached storage similar to the Amazon Elastic Block Storage (EBS) offering. In addition, you can write images to a Block Storage device for Compute to use as a bootable persistent instance." +msgstr "" + +#: ./doc/config-reference/block-storage/section_block-storage-overview.xml:14(para) +msgid "The Block Storage Service differs slightly from the Amazon EBS offering. The Block Storage Service does not provide a shared storage solution like NFS. With the Block Storage Service, you can attach a device to only one instance." +msgstr "" + +#: ./doc/config-reference/block-storage/section_block-storage-overview.xml:19(para) +msgid "The Block Storage Service provides:" +msgstr "" + +#: ./doc/config-reference/block-storage/section_block-storage-overview.xml:22(para) +msgid "cinder-api. A WSGI app that authenticates and routes requests throughout the Block Storage Service. It supports the OpenStack APIs only, although there is a translation that can be done through Compute's EC2 interface, which calls in to the cinderclient." +msgstr "" + +#: ./doc/config-reference/block-storage/section_block-storage-overview.xml:30(para) +msgid "cinder-scheduler. Schedules and routes requests to the appropriate volume service. As of Grizzly; depending upon your configuration this may be simple round-robin scheduling to the running volume services, or it can be more sophisticated through the use of the Filter Scheduler. The Filter Scheduler is the default in Grizzly and enables filters on things like Capacity, Availability Zone, Volume Types, and Capabilities as well as custom filters." +msgstr "" + +#: ./doc/config-reference/block-storage/section_block-storage-overview.xml:38(para) +msgid "cinder-volume. Manages Block Storage devices, specifically the back-end devices themselves." +msgstr "" + +#: ./doc/config-reference/block-storage/section_block-storage-overview.xml:43(para) +msgid "cinder-backup Provides a means to back up a Block Storage Volume to OpenStack Object Store (SWIFT)." +msgstr "" + +#: ./doc/config-reference/block-storage/section_block-storage-overview.xml:48(para) +msgid "The Block Storage Service contains the following components:" +msgstr "" + +#: ./doc/config-reference/block-storage/section_block-storage-overview.xml:52(para) +msgid "Back-end Storage Devices. The Block Storage Service requires some form of back-end storage that the service is built on. The default implementation is to use LVM on a local volume group named \"cinder-volumes.\" In addition to the base driver implementation, the Block Storage Service also provides the means to add support for other storage devices to be utilized such as external Raid Arrays or other storage appliances. These back-end storage devices may have custom block sizes when using KVM or QEMU as the hypervisor." +msgstr "" + +#: ./doc/config-reference/block-storage/section_block-storage-overview.xml:65(para) +msgid "Users and Tenants (Projects). The Block Storage Service is designed to be used by many different cloud computing consumers or customers, basically tenants on a shared system, using role-based access assignments. Roles control the actions that a user is allowed to perform. In the default configuration, most actions do not require a particular role, but this is configurable by the system administrator editing the appropriate policy.json file that maintains the rules. A user's access to particular volumes is limited by tenant, but the username and password are assigned per user. Key pairs granting access to a volume are enabled per user, but quotas to control resource consumption across available hardware resources are per tenant." +msgstr "" + +#: ./doc/config-reference/block-storage/section_block-storage-overview.xml:81(para) +msgid "For tenants, quota controls are available to limit:" +msgstr "" + +#: ./doc/config-reference/block-storage/section_block-storage-overview.xml:85(para) +msgid "The number of volumes that can be created" +msgstr "" + +#: ./doc/config-reference/block-storage/section_block-storage-overview.xml:89(para) +msgid "The number of snapshots that can be created" +msgstr "" + +#: ./doc/config-reference/block-storage/section_block-storage-overview.xml:93(para) +msgid "The total number of GBs allowed per tenant (shared between snapshots and volumes)" +msgstr "" + +#: ./doc/config-reference/block-storage/section_block-storage-overview.xml:97(para) +msgid "You can revise the default quota values with the cinder CLI, so the limits placed by quotas are editable by admin users." +msgstr "" + +#: ./doc/config-reference/block-storage/section_block-storage-overview.xml:100(para) +msgid "Volumes, Snapshots, and Backups. The basic resources offered by the Block Storage Service are volumes and snapshots, which are derived from volumes, and backups:" +msgstr "" + +#: ./doc/config-reference/block-storage/section_block-storage-overview.xml:107(para) +msgid "Volumes. Allocated block storage resources that can be attached to instances as secondary storage or they can be used as the root store to boot instances. Volumes are persistent R/W block storage devices most commonly attached to the Compute node through iSCSI." +msgstr "" + +#: ./doc/config-reference/block-storage/section_block-storage-overview.xml:116(para) +msgid "Snapshots. A read-only point in time copy of a volume. The snapshot can be created from a volume that is currently in use (through the use of '--force True') or in an available state. The snapshot can then be used to create a new volume through create from snapshot." +msgstr "" + +#: ./doc/config-reference/block-storage/section_block-storage-overview.xml:125(para) +msgid "Backups. An archived copy of a volume currently stored in OpenStack Object Storage (Swift)." +msgstr "" + +#: ./doc/config-reference/block-storage/drivers/vmware-vmdk-driver.xml:6(title) +msgid "VMware VMDK driver" +msgstr "" + +#: ./doc/config-reference/block-storage/drivers/vmware-vmdk-driver.xml:7(para) +msgid "Use the VMware VMDK driver to enable management of the OpenStack Block Storage volumes on vCenter-managed data stores. Volumes are backed by VMDK files on data stores using any VMware-compatible storage technology such as NFS, iSCSI, FiberChannel, and vSAN." +msgstr "" + +#: ./doc/config-reference/block-storage/drivers/vmware-vmdk-driver.xml:13(title) ./doc/config-reference/block-storage/drivers/xen-sm-driver.xml:134(title) ./doc/config-reference/block-storage/drivers/hds-volume-driver.xml:72(title) +msgid "Configuration" +msgstr "" + +#: ./doc/config-reference/block-storage/drivers/vmware-vmdk-driver.xml:14(para) +msgid "The recommended volume driver for OpenStack Block Storage is the VMware vCenter VMDK driver. When you configure the driver, you must match it with the appropriate OpenStack Compute driver from VMware and both drivers must point to the same server." +msgstr "" + +#: ./doc/config-reference/block-storage/drivers/vmware-vmdk-driver.xml:19(para) +msgid "For example, in the nova.conf file, use this option to define the Compute driver:" +msgstr "" + +#: ./doc/config-reference/block-storage/drivers/vmware-vmdk-driver.xml:22(para) +msgid "In the cinder.conf file, use this option to define the volume driver:" +msgstr "" + +#: ./doc/config-reference/block-storage/drivers/vmware-vmdk-driver.xml:25(para) +msgid "The following table lists various options that the drivers support for the OpenStack Block Storage configuration (cinder.conf):" +msgstr "" + +#: ./doc/config-reference/block-storage/drivers/vmware-vmdk-driver.xml:32(para) +msgid "The VMware VMDK drivers support the creation of VMDK disk files of type thin, thick, or eagerZeroedThick. Use the vmware:vmdk_type extra spec key with the appropriate value to specify the VMDK disk file type. The following table captures the mapping between the extra spec entry and the VMDK disk file type:" +msgstr "" + +#: ./doc/config-reference/block-storage/drivers/vmware-vmdk-driver.xml:40(caption) +msgid "Extra spec entry to VMDK disk file type mapping" +msgstr "" + +#: ./doc/config-reference/block-storage/drivers/vmware-vmdk-driver.xml:44(td) +msgid "Disk file type" +msgstr "" + +#: ./doc/config-reference/block-storage/drivers/vmware-vmdk-driver.xml:45(td) ./doc/config-reference/block-storage/drivers/vmware-vmdk-driver.xml:94(td) +msgid "Extra spec key" +msgstr "" + +#: ./doc/config-reference/block-storage/drivers/vmware-vmdk-driver.xml:46(td) ./doc/config-reference/block-storage/drivers/vmware-vmdk-driver.xml:95(td) +msgid "Extra spec value" +msgstr "" + +#: ./doc/config-reference/block-storage/drivers/vmware-vmdk-driver.xml:52(td) ./doc/config-reference/block-storage/drivers/vmware-vmdk-driver.xml:57(td) ./doc/config-reference/block-storage/drivers/vmware-vmdk-driver.xml:62(td) +msgid "vmware:vmdk_type" +msgstr "" + +#: ./doc/config-reference/block-storage/drivers/vmware-vmdk-driver.xml:56(td) ./doc/config-reference/block-storage/drivers/vmware-vmdk-driver.xml:58(td) +msgid "thick" +msgstr "" + +#: ./doc/config-reference/block-storage/drivers/vmware-vmdk-driver.xml:61(td) ./doc/config-reference/block-storage/drivers/vmware-vmdk-driver.xml:63(td) +msgid "eagerZeroedThick" +msgstr "" + +#: ./doc/config-reference/block-storage/drivers/vmware-vmdk-driver.xml:67(para) +msgid "If no vmdk_type extra spec entry is specified, the default disk file type is thin." +msgstr "" + +#: ./doc/config-reference/block-storage/drivers/vmware-vmdk-driver.xml:70(para) +msgid "The example below shows how to create a thick VMDK volume using the appropriate vmdk_type:" +msgstr "" + +#: ./doc/config-reference/block-storage/drivers/vmware-vmdk-driver.xml:80(title) ./doc/config-reference/block-storage/drivers/vmware-vmdk-driver.xml:93(td) +msgid "Clone type" +msgstr "" + +#: ./doc/config-reference/block-storage/drivers/vmware-vmdk-driver.xml:81(para) +msgid "With the VMware VMDK drivers, you can create a volume from another source volume or from a snapshot point. The VMware vCenter VMDK driver supports clone types full and linked/fast. The clone type is specified using the vmware:clone_type extra spec key with the appropriate value. The following table captures the mapping for clone types:" +msgstr "" + +#: ./doc/config-reference/block-storage/drivers/vmware-vmdk-driver.xml:90(caption) +msgid "Extra spec entry to clone type mapping" +msgstr "" + +#: ./doc/config-reference/block-storage/drivers/vmware-vmdk-driver.xml:100(td) ./doc/config-reference/block-storage/drivers/vmware-vmdk-driver.xml:102(td) +msgid "full" +msgstr "" + +#: ./doc/config-reference/block-storage/drivers/vmware-vmdk-driver.xml:101(td) ./doc/config-reference/block-storage/drivers/vmware-vmdk-driver.xml:106(td) +msgid "vmware:clone_type" +msgstr "" + +#: ./doc/config-reference/block-storage/drivers/vmware-vmdk-driver.xml:105(td) +msgid "linked/fast" +msgstr "" + +#: ./doc/config-reference/block-storage/drivers/vmware-vmdk-driver.xml:107(td) +msgid "linked" +msgstr "" + +#: ./doc/config-reference/block-storage/drivers/vmware-vmdk-driver.xml:111(para) +msgid "If not specified, the default clone type is full." +msgstr "" + +#: ./doc/config-reference/block-storage/drivers/vmware-vmdk-driver.xml:113(para) +msgid "The following is an example of linked cloning from another source volume:" +msgstr "" + +#: ./doc/config-reference/block-storage/drivers/vmware-vmdk-driver.xml:120(para) +msgid "Note: The VMware ESX VMDK driver ignores the extra spec entry and always creates a full clone." +msgstr "" + +#: ./doc/config-reference/block-storage/drivers/vmware-vmdk-driver.xml:125(title) ./doc/config-reference/block-storage/drivers/huawei-storage-driver.xml:13(title) ./doc/config-reference/block-storage/drivers/emc-volume-driver.xml:31(title) ./doc/config-reference/block-storage/drivers/hp-3par-driver.xml:42(title) +msgid "Supported operations" +msgstr "" + +#: ./doc/config-reference/block-storage/drivers/vmware-vmdk-driver.xml:126(para) +msgid "The following operations are supported by the VMware vCenter and ESX VMDK drivers:" +msgstr "" + +#: ./doc/config-reference/block-storage/drivers/vmware-vmdk-driver.xml:130(para) ./doc/config-reference/block-storage/drivers/huawei-storage-driver.xml:17(para) ./doc/config-reference/block-storage/drivers/huawei-storage-driver.xml:48(para) ./doc/config-reference/block-storage/drivers/huawei-storage-driver.xml:74(para) ./doc/config-reference/block-storage/drivers/huawei-storage-driver.xml:93(para) ./doc/config-reference/block-storage/drivers/emc-volume-driver.xml:36(para) ./doc/config-reference/block-storage/drivers/hds-volume-driver.xml:30(para) +msgid "Create volume" +msgstr "" + +#: ./doc/config-reference/block-storage/drivers/vmware-vmdk-driver.xml:133(para) +msgid "Create volume from another source volume. (Supported only if source volume is not attached to an instance.)" +msgstr "" + +#: ./doc/config-reference/block-storage/drivers/vmware-vmdk-driver.xml:138(para) ./doc/config-reference/block-storage/drivers/huawei-storage-driver.xml:35(para) ./doc/config-reference/block-storage/drivers/huawei-storage-driver.xml:111(para) ./doc/config-reference/block-storage/drivers/emc-volume-driver.xml:66(para) ./doc/config-reference/block-storage/drivers/hds-volume-driver.xml:60(para) +msgid "Create volume from snapshot" +msgstr "" + +#: ./doc/config-reference/block-storage/drivers/vmware-vmdk-driver.xml:141(para) +msgid "Create volume from glance image" +msgstr "" + +#: ./doc/config-reference/block-storage/drivers/vmware-vmdk-driver.xml:144(para) +msgid "Attach volume (When a volume is attached to an instance, a reconfigure operation is performed on the instance to add the volume's VMDK to it. The user must manually rescan and mount the device from within the guest operating system.)" +msgstr "" + +#: ./doc/config-reference/block-storage/drivers/vmware-vmdk-driver.xml:151(para) ./doc/config-reference/block-storage/drivers/huawei-storage-driver.xml:26(para) ./doc/config-reference/block-storage/drivers/huawei-storage-driver.xml:57(para) ./doc/config-reference/block-storage/drivers/huawei-storage-driver.xml:83(para) ./doc/config-reference/block-storage/drivers/huawei-storage-driver.xml:102(para) ./doc/config-reference/block-storage/drivers/emc-volume-driver.xml:45(para) ./doc/config-reference/block-storage/drivers/hds-volume-driver.xml:39(para) +msgid "Detach volume" +msgstr "" + +#: ./doc/config-reference/block-storage/drivers/vmware-vmdk-driver.xml:154(para) +msgid "Create snapshot (Allowed only if volume is not attached to an instance.)" +msgstr "" + +#: ./doc/config-reference/block-storage/drivers/vmware-vmdk-driver.xml:158(para) +msgid "Delete snapshot (Allowed only if volume is not attached to an instance.)" +msgstr "" + +#: ./doc/config-reference/block-storage/drivers/vmware-vmdk-driver.xml:162(para) +msgid "Upload as image to glance (Allowed only if volume is not attached to an instance.)" +msgstr "" + +#: ./doc/config-reference/block-storage/drivers/vmware-vmdk-driver.xml:167(para) +msgid "Although the VMware ESX VMDK driver supports these operations, it has not been extensively tested." +msgstr "" + +#: ./doc/config-reference/block-storage/drivers/vmware-vmdk-driver.xml:172(title) +msgid "Data store selection" +msgstr "" + +#: ./doc/config-reference/block-storage/drivers/vmware-vmdk-driver.xml:173(para) +msgid "When creating a volume, the driver chooses a data store that has sufficient free space and has the highest freespace/totalspace metric value." +msgstr "" + +#: ./doc/config-reference/block-storage/drivers/vmware-vmdk-driver.xml:177(para) +msgid "When a volume is attached to an instance, the driver attempts to place the volume under the instance's ESX host on a data store that is selected using the strategy above." +msgstr "" + +#: ./doc/config-reference/block-storage/drivers/nexenta-volume-driver.xml:4(title) +msgid "Nexenta drivers" +msgstr "" + +#: ./doc/config-reference/block-storage/drivers/nexenta-volume-driver.xml:5(para) +msgid "NexentaStor Appliance is NAS/SAN software platform designed for building reliable and fast network storage arrays. The Nexenta Storage Appliance uses ZFS as a disk management system. NexentaStor can serve as a storage node for the OpenStack and for the virtual servers through iSCSI and NFS protocols." +msgstr "" + +#: ./doc/config-reference/block-storage/drivers/nexenta-volume-driver.xml:11(para) +msgid "With the NFS option, every Compute volume is represented by a directory designated to be its own file system in the ZFS file system. These file systems are exported using NFS." +msgstr "" + +#: ./doc/config-reference/block-storage/drivers/nexenta-volume-driver.xml:14(para) +msgid "With either option some minimal setup is required to tell OpenStack which NexentaStor servers are being used, whether they are supporting iSCSI and/or NFS and how to access each of the servers." +msgstr "" + +#: ./doc/config-reference/block-storage/drivers/nexenta-volume-driver.xml:18(para) +msgid "Typically the only operation required on the NexentaStor servers is to create the containing directory for the iSCSI or NFS exports. For NFS this containing directory must be explicitly exported via NFS. There is no software that must be installed on the NexentaStor servers; they are controlled using existing management plane interfaces." +msgstr "" + +#: ./doc/config-reference/block-storage/drivers/nexenta-volume-driver.xml:26(title) +msgid "Nexenta iSCSI driver" +msgstr "" + +#: ./doc/config-reference/block-storage/drivers/nexenta-volume-driver.xml:27(para) +msgid "The Nexenta iSCSI driver allows you to use NexentaStor appliance to store Compute volumes. Every Compute volume is represented by a single zvol in a predefined Nexenta namespace. For every new volume the driver creates a iSCSI target and iSCSI target group that are used to access it from compute hosts." +msgstr "" + +#: ./doc/config-reference/block-storage/drivers/nexenta-volume-driver.xml:33(para) +msgid "The Nexenta iSCSI volume driver should work with all versions of NexentaStor. The NexentaStor appliance must be installed and configured according to the relevant Nexenta documentation. A pool and an enclosing namespace must be created for all iSCSI volumes to be accessed through the volume driver. This should be done as specified in the release specific NexentaStor documentation." +msgstr "" + +#: ./doc/config-reference/block-storage/drivers/nexenta-volume-driver.xml:40(para) +msgid "The NexentaStor Appliance iSCSI driver is selected using the normal procedures for one or multiple back-end volume drivers. You must configure these items for each NexentaStor appliance that the iSCSI volume driver controls:" +msgstr "" + +#: ./doc/config-reference/block-storage/drivers/nexenta-volume-driver.xml:46(title) +msgid "Enable the Nexenta iSCSI driver and related options" +msgstr "" + +#: ./doc/config-reference/block-storage/drivers/nexenta-volume-driver.xml:48(para) +msgid "This table contains the options supported by the Nexenta iSCSI driver." +msgstr "" + +#: ./doc/config-reference/block-storage/drivers/nexenta-volume-driver.xml:52(para) +msgid "To use Compute with the Nexenta iSCSI driver, first set the volume_driver:" +msgstr "" + +#: ./doc/config-reference/block-storage/drivers/nexenta-volume-driver.xml:56(para) +msgid "Then, set the nexenta_host parameter and other parameters from the table, if needed." +msgstr "" + +#: ./doc/config-reference/block-storage/drivers/nexenta-volume-driver.xml:63(title) +msgid "Nexenta NFS driver" +msgstr "" + +#: ./doc/config-reference/block-storage/drivers/nexenta-volume-driver.xml:64(para) +msgid "The Nexenta NFS driver allows you to use NexentaStor appliance to store Compute volumes via NFS. Every Compute volume is represented by a single NFS file within a shared directory." +msgstr "" + +#: ./doc/config-reference/block-storage/drivers/nexenta-volume-driver.xml:68(para) +msgid "While the NFS protocols standardize file access for users, they do not standardize administrative actions such as taking snapshots or replicating file systems. The Openstack Volume Drivers bring a common interface to these operations. The Nexenta NFS driver implements these standard actions using the ZFS management plane that already is deployed on NexentaStor appliances." +msgstr "" + +#: ./doc/config-reference/block-storage/drivers/nexenta-volume-driver.xml:75(para) +msgid "The Nexenta NFS volume driver should work with all versions of NexentaStor. The NexentaStor appliance must be installed and configured according to the relevant Nexenta documentation. A single parent file system must be created for all virtual disk directories supported for OpenStack. This directory must be created and exported on each NexentaStor appliance. This should be done as specified in the release specific NexentaStor documentation." +msgstr "" + +#: ./doc/config-reference/block-storage/drivers/nexenta-volume-driver.xml:84(title) +msgid "Enable the Nexenta NFS driver and related options" +msgstr "" + +#: ./doc/config-reference/block-storage/drivers/nexenta-volume-driver.xml:86(para) +msgid "To use Compute with the Nexenta NFS driver, first set the volume_driver:" +msgstr "" + +#: ./doc/config-reference/block-storage/drivers/nexenta-volume-driver.xml:91(para) +msgid "The following table contains the options supported by the Nexenta NFS driver." +msgstr "" + +#: ./doc/config-reference/block-storage/drivers/nexenta-volume-driver.xml:95(para) +msgid "Add your list of Nexenta NFS servers to the file you specified with the nexenta_shares_config option. For example, if the value of this option was set to /etc/cinder/nfs_shares, then:" +msgstr "" + +#: ./doc/config-reference/block-storage/drivers/nexenta-volume-driver.xml:105(para) +msgid "Comments are allowed in this file. They begin with a #." +msgstr "" + +#: ./doc/config-reference/block-storage/drivers/nexenta-volume-driver.xml:107(para) +msgid "Each line in this file represents a NFS share. The first part of the line is the NFS share URL, the second is the connection URL to the NexentaStor Appliance." +msgstr "" + +#: ./doc/config-reference/block-storage/drivers/zadara-volume-driver.xml:6(title) +msgid "Zadara" +msgstr "" + +#: ./doc/config-reference/block-storage/drivers/zadara-volume-driver.xml:7(para) +msgid "There is a volume back-end for Zadara. Set the following in your cinder.conf, and use the following options to configure it." +msgstr "" + +#. When image changes, this message will be marked fuzzy or untranslated for you. +#. It doesn't matter what you translate it to: it's not used at all. +#: ./doc/config-reference/block-storage/drivers/coraid-driver.xml:286(None) +msgid "@@image: '../../../common/figures/coraid/Repository_Creation_Plan_screen.png'; md5=83038804978648c2db4001a46c11f8ba" +msgstr "" + +#: ./doc/config-reference/block-storage/drivers/coraid-driver.xml:6(title) +msgid "Coraid AoE driver configuration" +msgstr "" + +#: ./doc/config-reference/block-storage/drivers/coraid-driver.xml:7(para) +msgid "Coraid storage appliances can provide block-level storage to OpenStack instances. Coraid storage appliances use the low-latency ATA-over-Ethernet (ATA) protocol to provide high-bandwidth data transfer between hosts and data on the network." +msgstr "" + +#: ./doc/config-reference/block-storage/drivers/coraid-driver.xml:11(para) +msgid "Once configured for OpenStack, you can:" +msgstr "" + +#: ./doc/config-reference/block-storage/drivers/coraid-driver.xml:14(para) +msgid "Create, delete, attach, and detach block storage volumes." +msgstr "" + +#: ./doc/config-reference/block-storage/drivers/coraid-driver.xml:18(para) +msgid "Create, list, and delete volume snapshots." +msgstr "" + +#: ./doc/config-reference/block-storage/drivers/coraid-driver.xml:21(para) +msgid "Create a volume from a snapshot, copy an image to a volume, copy a volume to an image, clone a volume, and get volume statistics." +msgstr "" + +#: ./doc/config-reference/block-storage/drivers/coraid-driver.xml:26(para) +msgid "This document describes how to configure the OpenStack Block Storage Service for use with Coraid storage appliances." +msgstr "" + +#: ./doc/config-reference/block-storage/drivers/coraid-driver.xml:29(title) +msgid "Terminology" +msgstr "" + +#: ./doc/config-reference/block-storage/drivers/coraid-driver.xml:30(para) +msgid "These terms are used in this section:" +msgstr "" + +#: ./doc/config-reference/block-storage/drivers/coraid-driver.xml:34(th) +msgid "Term" +msgstr "" + +#: ./doc/config-reference/block-storage/drivers/coraid-driver.xml:35(th) +msgid "Definition" +msgstr "" + +#: ./doc/config-reference/block-storage/drivers/coraid-driver.xml:40(td) +msgid "AoE" +msgstr "" + +#: ./doc/config-reference/block-storage/drivers/coraid-driver.xml:41(td) +msgid "ATA-over-Ethernet protocol" +msgstr "" + +#: ./doc/config-reference/block-storage/drivers/coraid-driver.xml:44(td) +msgid "EtherCloud Storage Manager (ESM)" +msgstr "" + +#: ./doc/config-reference/block-storage/drivers/coraid-driver.xml:45(td) +msgid "ESM provides live monitoring and management of EtherDrive appliances that use the AoE protocol, such as the SRX and VSX." +msgstr "" + +#: ./doc/config-reference/block-storage/drivers/coraid-driver.xml:50(td) +msgid "Fully-Qualified Repository Name (FQRN)" +msgstr "" + +#: ./doc/config-reference/block-storage/drivers/coraid-driver.xml:53(replaceable) +msgid "performance_class" +msgstr "" + +#: ./doc/config-reference/block-storage/drivers/coraid-driver.xml:53(replaceable) +msgid "availability_class" +msgstr "" + +#: ./doc/config-reference/block-storage/drivers/coraid-driver.xml:53(replaceable) +msgid "profile_name" +msgstr "" + +#: ./doc/config-reference/block-storage/drivers/coraid-driver.xml:53(replaceable) +msgid "repository_name" +msgstr "" + +#: ./doc/config-reference/block-storage/drivers/coraid-driver.xml:51(td) +msgid "The FQRN is the full identifier of a storage profile. FQRN syntax is: " +msgstr "" + +#: ./doc/config-reference/block-storage/drivers/coraid-driver.xml:56(td) +msgid "SAN" +msgstr "" + +#: ./doc/config-reference/block-storage/drivers/coraid-driver.xml:57(td) +msgid "Storage Area Network" +msgstr "" + +#: ./doc/config-reference/block-storage/drivers/coraid-driver.xml:60(td) +msgid "SRX" +msgstr "" + +#: ./doc/config-reference/block-storage/drivers/coraid-driver.xml:61(td) +msgid "Coraid EtherDrive SRX block storage appliance" +msgstr "" + +#: ./doc/config-reference/block-storage/drivers/coraid-driver.xml:64(td) +msgid "VSX" +msgstr "" + +#: ./doc/config-reference/block-storage/drivers/coraid-driver.xml:65(td) +msgid "Coraid EtherDrive VSX storage virtualization appliance" +msgstr "" + +#: ./doc/config-reference/block-storage/drivers/coraid-driver.xml:72(title) ./doc/config-reference/block-storage/drivers/xenapi-nfs.xml:14(title) +msgid "Requirements" +msgstr "" + +#: ./doc/config-reference/block-storage/drivers/coraid-driver.xml:73(para) +msgid "To support the OpenStack Block Storage Service, your SAN must include an SRX for physical storage, a VSX running at least CorOS v2.0.6 for snapshot support, and an ESM running at least v2.1.1 for storage repository orchestration. Ensure that all storage appliances are installed and connected to your network before you configure OpenStack volumes." +msgstr "" + +#: ./doc/config-reference/block-storage/drivers/coraid-driver.xml:79(para) +msgid "So that the node can communicate with the SAN, you must install the Coraid AoE Linux driver on each compute node on the network that runs an OpenStack instance." +msgstr "" + +#: ./doc/config-reference/block-storage/drivers/coraid-driver.xml:84(title) +msgid "Overview" +msgstr "" + +#: ./doc/config-reference/block-storage/drivers/coraid-driver.xml:85(para) +msgid "To configure the OpenStack Block Storage for use with Coraid storage appliances, perform the following procedures:" +msgstr "" + +#: ./doc/config-reference/block-storage/drivers/coraid-driver.xml:89(para) +msgid "Download and install the Coraid Linux AoE driver." +msgstr "" + +#: ./doc/config-reference/block-storage/drivers/coraid-driver.xml:93(para) +msgid "Create a storage profile by using the Coraid ESM GUI." +msgstr "" + +#: ./doc/config-reference/block-storage/drivers/coraid-driver.xml:97(para) +msgid "Create a storage repository by using the ESM GUI and record the FQRN." +msgstr "" + +#: ./doc/config-reference/block-storage/drivers/coraid-driver.xml:102(para) +msgid "Configure the cinder.conf file." +msgstr "" + +#: ./doc/config-reference/block-storage/drivers/coraid-driver.xml:106(para) +msgid "Create and associate a block storage volume type." +msgstr "" + +#: ./doc/config-reference/block-storage/drivers/coraid-driver.xml:113(title) +msgid "Install the Coraid AoE driver" +msgstr "" + +#: ./doc/config-reference/block-storage/drivers/coraid-driver.xml:114(para) +msgid "Install the Coraid AoE driver on every compute node that will require access to block storage." +msgstr "" + +#: ./doc/config-reference/block-storage/drivers/coraid-driver.xml:116(para) +msgid "The latest AoE drivers will always be located at http://support.coraid.com/support/linux/." +msgstr "" + +#: ./doc/config-reference/block-storage/drivers/coraid-driver.xml:119(para) +msgid "To download and install the AoE driver, follow the instructions below, replacing “aoeXXX” with the AoE driver file name:" +msgstr "" + +#: ./doc/config-reference/block-storage/drivers/coraid-driver.xml:124(para) +msgid "Download the latest Coraid AoE driver." +msgstr "" + +#: ./doc/config-reference/block-storage/drivers/coraid-driver.xml:130(para) +msgid "Unpack the AoE driver." +msgstr "" + +#: ./doc/config-reference/block-storage/drivers/coraid-driver.xml:133(para) +msgid "Install the AoE driver." +msgstr "" + +#: ./doc/config-reference/block-storage/drivers/coraid-driver.xml:139(para) +msgid "Initialize the AoE driver." +msgstr "" + +#: ./doc/config-reference/block-storage/drivers/coraid-driver.xml:145(para) +msgid "Optionally, specify the Ethernet interfaces that the node can use to communicate with the SAN." +msgstr "" + +#: ./doc/config-reference/block-storage/drivers/coraid-driver.xml:147(para) +msgid "The AoE driver may use every Ethernet interface available to the node unless limited with the aoe_iflist parameter. For more information about the aoe_iflist parameter, see the aoe readme file included with the AoE driver." +msgstr "" + +#: ./doc/config-reference/block-storage/drivers/coraid-driver.xml:154(replaceable) +msgid "eth1 eth2 ..." +msgstr "" + +#: ./doc/config-reference/block-storage/drivers/coraid-driver.xml:160(title) +msgid "Create a storage profile" +msgstr "" + +#: ./doc/config-reference/block-storage/drivers/coraid-driver.xml:161(para) +msgid "To create a storage profile using the ESM GUI:" +msgstr "" + +#: ./doc/config-reference/block-storage/drivers/coraid-driver.xml:164(para) +msgid "Log in to the ESM." +msgstr "" + +#: ./doc/config-reference/block-storage/drivers/coraid-driver.xml:167(para) +msgid "Click Storage Profiles in the SAN Domain pane." +msgstr "" + +#: ./doc/config-reference/block-storage/drivers/coraid-driver.xml:171(para) +msgid "Choose Menu > Create Storage Profile. If the option is unavailable, you might not have appropriate permissions. Make sure you are logged in to the ESM as the SAN administrator." +msgstr "" + +#: ./doc/config-reference/block-storage/drivers/coraid-driver.xml:177(para) +msgid "Use the storage class selector to select a storage class." +msgstr "" + +#: ./doc/config-reference/block-storage/drivers/coraid-driver.xml:179(para) +msgid "Each storage class includes performance and availability criteria (see the Storage Classes topic in the ESM Online Help for information on the different options)." +msgstr "" + +#: ./doc/config-reference/block-storage/drivers/coraid-driver.xml:184(para) +msgid "Select a RAID type (if more than one is available) for the selected profile type." +msgstr "" + +#: ./doc/config-reference/block-storage/drivers/coraid-driver.xml:188(para) +msgid "Type a Storage Profile name." +msgstr "" + +#: ./doc/config-reference/block-storage/drivers/coraid-driver.xml:189(para) +msgid "The name is restricted to alphanumeric characters, underscore (_), and hyphen (-), and cannot exceed 32 characters." +msgstr "" + +#: ./doc/config-reference/block-storage/drivers/coraid-driver.xml:194(para) +msgid "Select the drive size from the drop-down menu." +msgstr "" + +#: ./doc/config-reference/block-storage/drivers/coraid-driver.xml:197(para) +msgid "Select the number of drives to be initialized for each RAID (LUN) from the drop-down menu (if the selected RAID type requires multiple drives)." +msgstr "" + +#: ./doc/config-reference/block-storage/drivers/coraid-driver.xml:202(para) +msgid "Type the number of RAID sets (LUNs) you want to create in the repository by using this profile." +msgstr "" + +#: ./doc/config-reference/block-storage/drivers/coraid-driver.xml:206(para) +msgid "Click Next." +msgstr "" + +#: ./doc/config-reference/block-storage/drivers/coraid-driver.xml:211(title) +msgid "Create a storage repository and get the FQRN" +msgstr "" + +#: ./doc/config-reference/block-storage/drivers/coraid-driver.xml:212(para) +msgid "Create a storage repository and get its fully qualified repository name (FQRN):" +msgstr "" + +#: ./doc/config-reference/block-storage/drivers/coraid-driver.xml:216(para) +msgid "Access the Create Storage Repository dialog box." +msgstr "" + +#: ./doc/config-reference/block-storage/drivers/coraid-driver.xml:220(para) +msgid "Type a Storage Repository name." +msgstr "" + +#: ./doc/config-reference/block-storage/drivers/coraid-driver.xml:221(para) +msgid "The name is restricted to alphanumeric characters, underscore (_), hyphen (-), and cannot exceed 32 characters." +msgstr "" + +#: ./doc/config-reference/block-storage/drivers/coraid-driver.xml:226(para) +msgid "Click Limited or Unlimited to indicate the maximum repository size." +msgstr "" + +#: ./doc/config-reference/block-storage/drivers/coraid-driver.xml:229(para) +msgid "Limited sets the amount of space that can be allocated to the repository. Specify the size in TB, GB, or MB." +msgstr "" + +#: ./doc/config-reference/block-storage/drivers/coraid-driver.xml:232(para) +msgid "When the difference between the reserved space and the space already allocated to LUNs is less than is required by a LUN allocation request, the reserved space is increased until the repository limit is reached." +msgstr "" + +#: ./doc/config-reference/block-storage/drivers/coraid-driver.xml:237(para) +msgid "The reserved space does not include space used for parity or space used for mirrors. If parity and/or mirrors are required, the actual space allocated to the repository from the SAN is greater than that specified in reserved space." +msgstr "" + +#: ./doc/config-reference/block-storage/drivers/coraid-driver.xml:243(para) +msgid "Unlimited—Unlimited means that the amount of space allocated to the repository is unlimited and additional space is allocated to the repository automatically when space is required and available." +msgstr "" + +#: ./doc/config-reference/block-storage/drivers/coraid-driver.xml:249(para) +msgid "Drives specified in the associated Storage Profile must be available on the SAN in order to allocate additional resources." +msgstr "" + +#: ./doc/config-reference/block-storage/drivers/coraid-driver.xml:255(para) +msgid "Check the Resizeable LUN box." +msgstr "" + +#: ./doc/config-reference/block-storage/drivers/coraid-driver.xml:257(para) +msgid "This is required for OpenStack volumes." +msgstr "" + +#: ./doc/config-reference/block-storage/drivers/coraid-driver.xml:259(para) +msgid "If the Storage Profile associated with the repository has platinum availability, the Resizeable LUN box is automatically checked." +msgstr "" + +#: ./doc/config-reference/block-storage/drivers/coraid-driver.xml:265(para) +msgid "Check the Show Allocation Plan API calls box. Click Next." +msgstr "" + +#: ./doc/config-reference/block-storage/drivers/coraid-driver.xml:270(para) +msgid "Record the FQRN and click Finish." +msgstr "" + +#: ./doc/config-reference/block-storage/drivers/coraid-driver.xml:272(para) +msgid "The FQRN is located in the first line of output following the Plan keyword in the Repository Creation Plan window. The FQRN syntax is performance_classavailability_classprofile_namerepository_name." +msgstr "" + +#: ./doc/config-reference/block-storage/drivers/coraid-driver.xml:277(para) +msgid "In this example, the FQRN is Bronze-Platinum:BP1000:OSTest, and is highlighted." +msgstr "" + +#: ./doc/config-reference/block-storage/drivers/coraid-driver.xml:281(title) +msgid "Repository Creation Plan screen" +msgstr "" + +#: ./doc/config-reference/block-storage/drivers/coraid-driver.xml:290(para) +msgid "Record the FQRN; it is a required parameter later in the configuration procedure." +msgstr "" + +#: ./doc/config-reference/block-storage/drivers/coraid-driver.xml:296(title) +msgid "Configure options in the cinder.conf file" +msgstr "" + +#: ./doc/config-reference/block-storage/drivers/coraid-driver.xml:297(para) +msgid "Edit or add the following lines to the file /etc/cinder/cinder.conf:" +msgstr "" + +#: ./doc/config-reference/block-storage/drivers/coraid-driver.xml:300(replaceable) +msgid "ESM_IP_address" +msgstr "" + +#: ./doc/config-reference/block-storage/drivers/coraid-driver.xml:301(replaceable) ./doc/config-reference/block-storage/drivers/hds-volume-driver.xml:340(option) +msgid "username" +msgstr "" + +#: ./doc/config-reference/block-storage/drivers/coraid-driver.xml:302(replaceable) +msgid "Access_Control_Group_name" +msgstr "" + +#: ./doc/config-reference/block-storage/drivers/coraid-driver.xml:303(replaceable) ./doc/config-reference/block-storage/drivers/hds-volume-driver.xml:350(option) +msgid "password" +msgstr "" + +#: ./doc/config-reference/block-storage/drivers/coraid-driver.xml:304(replaceable) ./doc/config-reference/block-storage/drivers/coraid-driver.xml:352(replaceable) ./doc/config-reference/block-storage/drivers/coraid-driver.xml:370(replaceable) +msgid "coraid_repository_key" +msgstr "" + +#: ./doc/config-reference/block-storage/drivers/coraid-driver.xml:306(para) +msgid "Access to storage devices and storage repositories can be controlled using Access Control Groups configured in ESM. Configuring cinder.conf to log on to ESM as the SAN administrator (user name admin), will grant full access to the devices and repositories configured in ESM." +msgstr "" + +#: ./doc/config-reference/block-storage/drivers/coraid-driver.xml:312(para) +msgid "Optionally, you can configure an ESM Access Control Group and user. Then, use the cinder.conf file to configure access to the ESM through that group, and user limits access from the OpenStack instance to devices and storage repositories that are defined in the group." +msgstr "" + +#: ./doc/config-reference/block-storage/drivers/coraid-driver.xml:317(para) +msgid "To manage access to the SAN by using Access Control Groups, you must enable the Use Access Control setting in the ESM System Setup > Security screen." +msgstr "" + +#: ./doc/config-reference/block-storage/drivers/coraid-driver.xml:321(para) +msgid "For more information, see the ESM Online Help." +msgstr "" + +#: ./doc/config-reference/block-storage/drivers/coraid-driver.xml:324(title) +msgid "Create and associate a volume type" +msgstr "" + +#: ./doc/config-reference/block-storage/drivers/coraid-driver.xml:325(para) +msgid "Create and associate a volume with the ESM storage repository." +msgstr "" + +#: ./doc/config-reference/block-storage/drivers/coraid-driver.xml:329(para) +msgid "Restart Cinder." +msgstr "" + +#: ./doc/config-reference/block-storage/drivers/coraid-driver.xml:335(para) +msgid "Create a volume." +msgstr "" + +#: ./doc/config-reference/block-storage/drivers/coraid-driver.xml:336(replaceable) +msgid "volume_type_name" +msgstr "" + +#: ./doc/config-reference/block-storage/drivers/coraid-driver.xml:337(para) +msgid "where volume_type_name is the name you assign the volume. You will see output similar to the following:" +msgstr "" + +#: ./doc/config-reference/block-storage/drivers/coraid-driver.xml:345(para) +msgid "Record the value in the ID field; you use this value in the next step." +msgstr "" + +#: ./doc/config-reference/block-storage/drivers/coraid-driver.xml:349(para) +msgid "Associate the volume type with the Storage Repository." +msgstr "" + +#: ./doc/config-reference/block-storage/drivers/coraid-driver.xml:352(replaceable) ./doc/config-reference/block-storage/drivers/coraid-driver.xml:363(replaceable) +msgid "UUID" +msgstr "" + +#: ./doc/config-reference/block-storage/drivers/coraid-driver.xml:352(replaceable) ./doc/config-reference/block-storage/drivers/coraid-driver.xml:378(replaceable) +msgid "FQRN" +msgstr "" + +#: ./doc/config-reference/block-storage/drivers/coraid-driver.xml:357(th) +msgid "Variable" +msgstr "" + +#: ./doc/config-reference/block-storage/drivers/coraid-driver.xml:358(th) ./doc/config-reference/block-storage/drivers/huawei-storage-driver.xml:311(td) ./doc/config-reference/block-storage/drivers/ibm-storwize-svc-driver.xml:202(td) ./doc/config-reference/block-storage/drivers/hds-volume-driver.xml:319(td) ./doc/config-reference/block-storage/drivers/ibm-gpfs-volume-driver.xml:80(th) +msgid "Description" +msgstr "" + +#: ./doc/config-reference/block-storage/drivers/coraid-driver.xml:364(td) +msgid "The ID returned from the command. You can use the command to recover the ID." +msgstr "" + +#: ./doc/config-reference/block-storage/drivers/coraid-driver.xml:373(filename) +msgid "cinder.conf" +msgstr "" + +#: ./doc/config-reference/block-storage/drivers/coraid-driver.xml:375(literal) +msgid "coraid_repository" +msgstr "" + +#: ./doc/config-reference/block-storage/drivers/coraid-driver.xml:371(td) +msgid "The key name used to associate the Cinder volume type with the ESM in the file. If no key name was defined, this is default value for ." +msgstr "" + +#: ./doc/config-reference/block-storage/drivers/coraid-driver.xml:379(td) +msgid "The FQRN recorded during the Create Storage Repository process." +msgstr "" + +#: ./doc/config-reference/block-storage/drivers/solidfire-volume-driver.xml:5(title) +msgid "SolidFire" +msgstr "" + +#: ./doc/config-reference/block-storage/drivers/solidfire-volume-driver.xml:6(para) +msgid "The SolidFire Cluster is a high performance all SSD iSCSI storage device that provides massive scale out capability and extreme fault tolerance. A key feature of the SolidFire cluster is the ability to set and modify during operation specific QoS levels on a volume for volume basis. The SolidFire cluster offers this along with de-duplication, compression, and an architecture that takes full advantage of SSDs." +msgstr "" + +#: ./doc/config-reference/block-storage/drivers/solidfire-volume-driver.xml:14(para) +msgid "To configure the use of a SolidFire cluster with Block Storage, modify your cinder.conf file as follows:" +msgstr "" + +#: ./doc/config-reference/block-storage/drivers/solidfire-volume-driver.xml:23(para) +msgid "The SolidFire driver creates a unique account prefixed with $cinder-volume-service-hostname-$tenant-id on the SolidFire cluster for each tenant that accesses the cluster through the Volume API. Unfortunately, this account formation results in issues for High Availability (HA) installations and installations where the cinder-volume service can move to a new node. HA installations can return an Account Not Found error because the call to the SolidFire cluster is not always going to be sent from the same node. In installations where the cinder-volume service moves to a new node, the same issue can occur when you perform operations on existing volumes, such as clone, extend, delete, and so on." +msgstr "" + +#: ./doc/config-reference/block-storage/drivers/solidfire-volume-driver.xml:41(para) +msgid "Set the sf_account_prefix option to an empty string ('') in the cinder.conf file. This setting results in unique accounts being created on the SolidFire cluster, but the accounts are prefixed with the tenant-id or any unique identifier that you choose and are independent of the host where the cinder-volume service resides." +msgstr "" + +#: ./doc/config-reference/block-storage/drivers/xen-sm-driver.xml:4(title) +msgid "XenAPI Storage Manager volume driver" +msgstr "" + +#: ./doc/config-reference/block-storage/drivers/xen-sm-driver.xml:5(para) +msgid "The Xen Storage Manager volume driver (xensm) is a XenAPI hypervisor specific volume driver, and can be used to provide basic storage functionality, including volume creation and destruction, on a number of different storage back-ends. It also enables the capability of using more sophisticated storage back-ends for operations like cloning/snapshots, and so on. Some of the storage plug-ins that are already supported in Citrix XenServer and Xen Cloud Platform (XCP) are:" +msgstr "" + +#: ./doc/config-reference/block-storage/drivers/xen-sm-driver.xml:15(para) +msgid "NFS VHD: Storage repository (SR) plug-in that stores disks as Virtual Hard Disk (VHD) files on a remote Network File System (NFS)." +msgstr "" + +#: ./doc/config-reference/block-storage/drivers/xen-sm-driver.xml:20(para) +msgid "Local VHD on LVM: SR plug-in that represents disks as VHD disks on Logical Volumes (LVM) within a locally-attached Volume Group." +msgstr "" + +#: ./doc/config-reference/block-storage/drivers/xen-sm-driver.xml:25(para) +msgid "HBA LUN-per-VDI driver: SR plug-in that represents Logical Units (LUs) as Virtual Disk Images (VDIs) sourced by host bus adapters (HBAs). For example, hardware-based iSCSI or FC support." +msgstr "" + +#: ./doc/config-reference/block-storage/drivers/xen-sm-driver.xml:31(para) +msgid "NetApp: SR driver for mapping of LUNs to VDIs on a NETAPP server, providing use of fast snapshot and clone features on the filer." +msgstr "" + +#: ./doc/config-reference/block-storage/drivers/xen-sm-driver.xml:36(para) +msgid "LVHD over FC: SR plug-in that represents disks as VHDs on Logical Volumes within a Volume Group created on an HBA LUN. For example, hardware-based iSCSI or FC support." +msgstr "" + +#: ./doc/config-reference/block-storage/drivers/xen-sm-driver.xml:42(para) +msgid "iSCSI: Base ISCSI SR driver, provides a LUN-per-VDI. Does not support creation of VDIs but accesses existing LUNs on a target." +msgstr "" + +#: ./doc/config-reference/block-storage/drivers/xen-sm-driver.xml:47(para) +msgid "LVHD over iSCSI: SR plug-in that represents disks as Logical Volumes within a Volume Group created on an iSCSI LUN." +msgstr "" + +#: ./doc/config-reference/block-storage/drivers/xen-sm-driver.xml:52(para) +msgid "EqualLogic: SR driver for mapping of LUNs to VDIs on a EQUALLOGIC array group, providing use of fast snapshot and clone features on the array." +msgstr "" + +#: ./doc/config-reference/block-storage/drivers/xen-sm-driver.xml:58(title) +msgid "Design and operation" +msgstr "" + +#: ./doc/config-reference/block-storage/drivers/xen-sm-driver.xml:60(title) +msgid "Definitions" +msgstr "" + +#: ./doc/config-reference/block-storage/drivers/xen-sm-driver.xml:63(para) +msgid "Back-end: A term for a particular storage back-end. This could be iSCSI, NFS, NetApp, and so on." +msgstr "" + +#: ./doc/config-reference/block-storage/drivers/xen-sm-driver.xml:68(para) +msgid "Back-end-config: All the parameters required to connect to a specific back-end. For example, for NFS, this would be the server, path, and so on." +msgstr "" + +#: ./doc/config-reference/block-storage/drivers/xen-sm-driver.xml:75(para) +msgid "Flavor: This term is equivalent to volume \"types\". A user friendly term to specify some notion of quality of service. For example, \"gold\" might mean that the volumes use a back-end where backups are possible. A flavor can be associated with multiple back-ends. The volume scheduler, with the help of the driver, decides which back-end is used to create a volume of a particular flavor. Currently, the driver uses a simple \"first-fit\" policy, where the first back-end that can successfully create this volume is the one that is used." +msgstr "" + +#: ./doc/config-reference/block-storage/drivers/xen-sm-driver.xml:93(title) +msgid "Operation" +msgstr "" + +#: ./doc/config-reference/block-storage/drivers/xen-sm-driver.xml:94(para) +msgid "The admin uses the nova-manage command detailed below to add flavors and back-ends." +msgstr "" + +#: ./doc/config-reference/block-storage/drivers/xen-sm-driver.xml:96(para) +msgid "One or more cinder-volume service instances are deployed for each availability zone. When an instance is started, it creates storage repositories (SRs) to connect to the back-ends available within that zone. All cinder-volume instances within a zone can see all the available back-ends. These instances are completely symmetric and hence should be able to service any create_volume request within the zone." +msgstr "" + +#: ./doc/config-reference/block-storage/drivers/xen-sm-driver.xml:108(title) +msgid "On XenServer, PV guests required" +msgstr "" + +#: ./doc/config-reference/block-storage/drivers/xen-sm-driver.xml:109(para) +msgid "Note that when using XenServer you can only attach a volume to a PV guest." +msgstr "" + +#: ./doc/config-reference/block-storage/drivers/xen-sm-driver.xml:115(title) +msgid "Configure XenAPI Storage Manager" +msgstr "" + +#: ./doc/config-reference/block-storage/drivers/xen-sm-driver.xml:120(para) +msgid "xensm requires that you use either Citrix XenServer or XCP as the hypervisor. The NetApp and EqualLogic back-ends are not supported on XCP." +msgstr "" + +#: ./doc/config-reference/block-storage/drivers/xen-sm-driver.xml:126(para) +msgid "Ensure all hosts running volume and compute services have connectivity to the storage system." +msgstr "" + +#: ./doc/config-reference/block-storage/drivers/xen-sm-driver.xml:141(systemitem) ./doc/config-reference/block-storage/drivers/xen-sm-driver.xml:181(systemitem) +msgid "nova-compute" +msgstr "" + +#: ./doc/config-reference/block-storage/drivers/xen-sm-driver.xml:138(emphasis) +msgid "Set the following configuration options for the nova volume service: ( also requires the volume_driver configuration option.)" +msgstr "" + +#: ./doc/config-reference/block-storage/drivers/xen-sm-driver.xml:152(emphasis) +msgid "You must create the back-end configurations that the volume driver uses before you start the volume service." +msgstr "" + +#: ./doc/config-reference/block-storage/drivers/xen-sm-driver.xml:161(para) +msgid "SR type and configuration connection parameters are in keeping with the XenAPI Command Line Interface." +msgstr "" + +#: ./doc/config-reference/block-storage/drivers/xen-sm-driver.xml:168(para) +msgid "Example: For the NFS storage manager plug-in, run these commands:" +msgstr "" + +#: ./doc/config-reference/block-storage/drivers/xen-sm-driver.xml:179(systemitem) +msgid "cinder-volume" +msgstr "" + +#: ./doc/config-reference/block-storage/drivers/xen-sm-driver.xml:177(emphasis) +msgid "Start and with the new configuration options." +msgstr "" + +#: ./doc/config-reference/block-storage/drivers/xen-sm-driver.xml:188(title) +msgid "Create and access the volumes from VMs" +msgstr "" + +#: ./doc/config-reference/block-storage/drivers/xen-sm-driver.xml:189(para) +msgid "Currently, the flavors have not been tied to the volume types API. As a result, we simply end up creating volumes in a \"first fit\" order on the given back-ends." +msgstr "" + +#: ./doc/config-reference/block-storage/drivers/xen-sm-driver.xml:193(para) +msgid "Use the standard or OpenStack API commands (such as volume extensions) to create, destroy, attach, or detach volumes." +msgstr "" + +#: ./doc/config-reference/block-storage/drivers/ibm-xiv-volume-driver.xml:5(title) +msgid "IBM XIV/DS8K volume driver" +msgstr "" + +#: ./doc/config-reference/block-storage/drivers/ibm-xiv-volume-driver.xml:6(para) +msgid "There is a unified volume back-end for IBM XIV and DS8K storage. Set the following in your cinder.conf, and use the following options to configure it." +msgstr "" + +#: ./doc/config-reference/block-storage/drivers/netapp-volume-driver.xml:5(title) +msgid "NetApp unified driver" +msgstr "" + +#: ./doc/config-reference/block-storage/drivers/netapp-volume-driver.xml:6(para) +msgid "The NetApp® unified driver is a block storage driver that supports multiple storage families and protocols. A storage family corresponds to storage systems built on different NetApp technologies such as clustered Data ONTAP® and Data ONTAP operating in 7-Mode. The storage protocol refers to the protocol used to initiate data storage and access operations on those storage systems like iSCSI and NFS. The NetApp unified driver can be configured to provision and manage OpenStack volumes on a given storage family using a specified storage protocol. The OpenStack volumes can then be used for accessing and storing data using the storage protocol on the storage family system. The NetApp unified driver is an extensible interface that can support new storage families and protocols." +msgstr "" + +#: ./doc/config-reference/block-storage/drivers/netapp-volume-driver.xml:21(title) +msgid "NetApp clustered Data ONTAP storage family" +msgstr "" + +#: ./doc/config-reference/block-storage/drivers/netapp-volume-driver.xml:22(para) +msgid "The NetApp clustered Data ONTAP storage family represents a configuration group which provides OpenStack compute instances access to clustered Data ONTAP storage systems. At present it can be configured in Cinder to work with iSCSI and NFS storage protocols." +msgstr "" + +#: ./doc/config-reference/block-storage/drivers/netapp-volume-driver.xml:28(title) +msgid "NetApp iSCSI configuration for clustered Data ONTAP" +msgstr "" + +#: ./doc/config-reference/block-storage/drivers/netapp-volume-driver.xml:30(para) +msgid "The NetApp iSCSI configuration for clustered Data ONTAP is an interface from OpenStack to clustered Data ONTAP storage systems for provisioning and managing the SAN block storage entity; that is, a NetApp LUN which can be accessed using the iSCSI protocol." +msgstr "" + +#: ./doc/config-reference/block-storage/drivers/netapp-volume-driver.xml:35(para) +msgid "The iSCSI configuration for clustered Data ONTAP is a direct interface from Cinder to the clustered Data ONTAP instance and as such does not require additional management software to achieve the desired functionality. It uses NetApp APIs to interact with the clustered Data ONTAP instance." +msgstr "" + +#: ./doc/config-reference/block-storage/drivers/netapp-volume-driver.xml:42(title) +msgid "Configuration options for clustered Data ONTAP family with iSCSI protocol" +msgstr "" + +#: ./doc/config-reference/block-storage/drivers/netapp-volume-driver.xml:44(para) +msgid "Configure the volume driver, storage family and storage protocol to the NetApp unified driver, clustered Data ONTAP, and iSCSI respectively by setting the volume_driver, netapp_storage_family and netapp_storage_protocol options in cinder.conf as follows:" +msgstr "" + +#: ./doc/config-reference/block-storage/drivers/netapp-volume-driver.xml:63(para) ./doc/config-reference/block-storage/drivers/netapp-volume-driver.xml:230(para) +msgid "You must override the default value of netapp_storage_protocol with iscsi in order to utilize the iSCSI protocol." +msgstr "" + +#: ./doc/config-reference/block-storage/drivers/netapp-volume-driver.xml:71(para) ./doc/config-reference/block-storage/drivers/netapp-volume-driver.xml:129(para) +msgid "If you specify an account in the netapp_login that only has virtual storage server (Vserver) administration privileges (rather than cluster-wide administration privileges), some advanced features of the NetApp unified driver will not work and you may see warnings in the Cinder logs." +msgstr "" + +#: ./doc/config-reference/block-storage/drivers/netapp-volume-driver.xml:81(para) +msgid "For more information on these options and other deployment and operational scenarios, visit the OpenStack NetApp community." +msgstr "" + +#: ./doc/config-reference/block-storage/drivers/netapp-volume-driver.xml:91(title) +msgid "NetApp NFS configuration for clustered Data ONTAP" +msgstr "" + +#: ./doc/config-reference/block-storage/drivers/netapp-volume-driver.xml:93(para) +msgid "The NetApp NFS configuration for clustered Data ONTAP is an interface from OpenStack to a clustered Data ONTAP system for provisioning and managing OpenStack volumes on NFS exports provided by the clustered Data ONTAP system that are accessed using the NFS protocol." +msgstr "" + +#: ./doc/config-reference/block-storage/drivers/netapp-volume-driver.xml:99(para) +msgid "The NFS configuration for clustered Data ONTAP is a direct interface from Cinder to the clustered Data ONTAP instance and as such does not require any additional management software to achieve the desired functionality. It uses NetApp APIs to interact with the clustered Data ONTAP instance." +msgstr "" + +#: ./doc/config-reference/block-storage/drivers/netapp-volume-driver.xml:106(title) +msgid "Configuration options for the clustered Data ONTAP family with NFS protocol" +msgstr "" + +#: ./doc/config-reference/block-storage/drivers/netapp-volume-driver.xml:108(para) +msgid "Configure the volume driver, storage family and storage protocol to NetApp unified driver, clustered Data ONTAP, and NFS respectively by setting the volume_driver, netapp_storage_family and netapp_storage_protocol options in cinder.conf as follows:" +msgstr "" + +#: ./doc/config-reference/block-storage/drivers/netapp-volume-driver.xml:139(para) ./doc/config-reference/block-storage/drivers/netapp-volume-driver.xml:238(para) ./doc/config-reference/block-storage/drivers/netapp-volume-driver.xml:288(para) +msgid "For more information on these options and other deployment and operational scenarios, visit the OpenStack NetApp community." +msgstr "" + +#: ./doc/config-reference/block-storage/drivers/netapp-volume-driver.xml:148(title) +msgid "NetApp-supported extra specs for clustered Data ONTAP" +msgstr "" + +#: ./doc/config-reference/block-storage/drivers/netapp-volume-driver.xml:150(para) +msgid "Extra specs enable vendors to specify extra filter criteria that the Block Storage scheduler uses when it determines which volume node should fulfill a volume provisioning request. When you use the NetApp unified driver with a clustered Data ONTAP storage system, you can leverage extra specs with Cinder volume types to ensure that Cinder volumes are created on storage back ends that have certain properties. For example, when you configure QoS, mirroring, or compression for a storage back end." +msgstr "" + +#: ./doc/config-reference/block-storage/drivers/netapp-volume-driver.xml:160(para) +msgid "Extra specs are associated with Cinder volume types, so that when users request volumes of a particular volume type, the volumes are created on storage back ends that meet the list of requirements. For example, the back ends have the available space or extra specs. You can use the specs in the following table when you define Cinder volume types by using the command." +msgstr "" + +#: ./doc/config-reference/block-storage/drivers/netapp-volume-driver.xml:171(para) +msgid "It is recommended to only set the value of extra specs to True when combining multiple specs to enforce a certain logic set. If you desire to remove volumes with a certain feature enabled from consideration from the Cinder volume scheduler, be sure to use the negated spec name with a value of True rather than setting the positive spec to a value of False." +msgstr "" + +#: ./doc/config-reference/block-storage/drivers/netapp-volume-driver.xml:184(title) +msgid "NetApp Data ONTAP operating in 7-Mode storage family" +msgstr "" + +#: ./doc/config-reference/block-storage/drivers/netapp-volume-driver.xml:186(para) +msgid "The NetApp Data ONTAP operating in 7-Mode storage family represents a configuration group which provides OpenStack compute instances access to 7-Mode storage systems. At present it can be configured in Cinder to work with iSCSI and NFS storage protocols." +msgstr "" + +#: ./doc/config-reference/block-storage/drivers/netapp-volume-driver.xml:192(title) +msgid "NetApp iSCSI configuration for Data ONTAP operating in 7-Mode" +msgstr "" + +#: ./doc/config-reference/block-storage/drivers/netapp-volume-driver.xml:194(para) +msgid "The NetApp iSCSI configuration for Data ONTAP operating in 7-Mode is an interface from OpenStack to Data ONTAP operating in 7-Mode storage systems for provisioning and managing the SAN block storage entity, that is, a LUN which can be accessed using iSCSI protocol." +msgstr "" + +#: ./doc/config-reference/block-storage/drivers/netapp-volume-driver.xml:200(para) +msgid "The iSCSI configuration for Data ONTAP operating in 7-Mode is a direct interface from OpenStack to Data ONTAP operating in 7-Mode storage system and it does not require additional management software to achieve the desired functionality. It uses NetApp ONTAPI to interact with the Data ONTAP operating in 7-Mode storage system." +msgstr "" + +#: ./doc/config-reference/block-storage/drivers/netapp-volume-driver.xml:208(title) +msgid "Configuration options for the Data ONTAP operating in 7-Mode storage family with iSCSI protocol" +msgstr "" + +#: ./doc/config-reference/block-storage/drivers/netapp-volume-driver.xml:211(para) +msgid "Configure the volume driver, storage family and storage protocol to the NetApp unified driver, Data ONTAP operating in 7-Mode, and iSCSI respectively by setting the volume_driver, netapp_storage_family and netapp_storage_protocol options in cinder.conf as follows:" +msgstr "" + +#: ./doc/config-reference/block-storage/drivers/netapp-volume-driver.xml:247(title) +msgid "NetApp NFS configuration for Data ONTAP operating in 7-Mode" +msgstr "" + +#: ./doc/config-reference/block-storage/drivers/netapp-volume-driver.xml:249(para) +msgid "The NetApp NFS configuration for Data ONTAP operating in 7-Mode is an interface from OpenStack to Data ONTAP operating in 7-Mode storage system for provisioning and managing OpenStack volumes on NFS exports provided by the Data ONTAP operating in 7-Mode storage system which can then be accessed using NFS protocol." +msgstr "" + +#: ./doc/config-reference/block-storage/drivers/netapp-volume-driver.xml:256(para) +msgid "The NFS configuration for Data ONTAP operating in 7-Mode is a direct interface from Cinder to the Data ONTAP operating in 7-Mode instance and as such does not require any additional management software to achieve the desired functionality. It uses NetApp ONTAPI to interact with the Data ONTAP operating in 7-Mode storage system." +msgstr "" + +#: ./doc/config-reference/block-storage/drivers/netapp-volume-driver.xml:264(title) +msgid "Configuration options for the Data ONTAP operating in 7-Mode family with NFS protocol" +msgstr "" + +#: ./doc/config-reference/block-storage/drivers/netapp-volume-driver.xml:267(para) +msgid "Configure the volume driver, storage family and storage protocol to the NetApp unified driver, Data ONTAP operating in 7-Mode, and NFS respectively by setting the volume_driver, netapp_storage_family and netapp_storage_protocol options in cinder.conf as follows:" +msgstr "" + +#: ./doc/config-reference/block-storage/drivers/netapp-volume-driver.xml:298(title) +msgid "Upgrading prior NetApp drivers to the NetApp unified driver" +msgstr "" + +#: ./doc/config-reference/block-storage/drivers/netapp-volume-driver.xml:300(para) +msgid "NetApp introduced a new unified block storage driver in Havana for configuring different storage families and storage protocols. This requires defining upgrade path for NetApp drivers which existed in releases prior to Havana. This section covers the upgrade configuration for NetApp drivers to the new unified configuration and a list of deprecated NetApp drivers." +msgstr "" + +#: ./doc/config-reference/block-storage/drivers/netapp-volume-driver.xml:308(title) +msgid "Upgraded NetApp drivers" +msgstr "" + +#: ./doc/config-reference/block-storage/drivers/netapp-volume-driver.xml:309(para) +msgid "This section describes how to update Cinder configuration from a pre-Havana release to the new unified driver format." +msgstr "" + +#: ./doc/config-reference/block-storage/drivers/netapp-volume-driver.xml:313(title) +msgid "Driver upgrade configuration" +msgstr "" + +#: ./doc/config-reference/block-storage/drivers/netapp-volume-driver.xml:316(para) +msgid "NetApp iSCSI direct driver for Clustered Data ONTAP in Grizzly (or earlier)" +msgstr "" + +#: ./doc/config-reference/block-storage/drivers/netapp-volume-driver.xml:321(para) ./doc/config-reference/block-storage/drivers/netapp-volume-driver.xml:335(para) ./doc/config-reference/block-storage/drivers/netapp-volume-driver.xml:350(para) ./doc/config-reference/block-storage/drivers/netapp-volume-driver.xml:365(para) +msgid "NetApp Unified Driver configuration" +msgstr "" + +#: ./doc/config-reference/block-storage/drivers/netapp-volume-driver.xml:330(para) +msgid "NetApp NFS direct driver for Clustered Data ONTAP in Grizzly (or earlier)" +msgstr "" + +#: ./doc/config-reference/block-storage/drivers/netapp-volume-driver.xml:344(para) +msgid "NetApp iSCSI direct driver for Data ONTAP operating in 7-Mode storage controller in Grizzly (or earlier)" +msgstr "" + +#: ./doc/config-reference/block-storage/drivers/netapp-volume-driver.xml:359(para) +msgid "NetApp NFS direct driver for Data ONTAP operating in 7-Mode storage controller in Grizzly (or earlier)" +msgstr "" + +#: ./doc/config-reference/block-storage/drivers/netapp-volume-driver.xml:378(title) +msgid "Deprecated NetApp drivers" +msgstr "" + +#: ./doc/config-reference/block-storage/drivers/netapp-volume-driver.xml:379(para) +msgid "This section lists the NetApp drivers in previous releases that are deprecated in Havana." +msgstr "" + +#: ./doc/config-reference/block-storage/drivers/netapp-volume-driver.xml:383(para) +msgid "NetApp iSCSI driver for clustered Data ONTAP." +msgstr "" + +#: ./doc/config-reference/block-storage/drivers/netapp-volume-driver.xml:390(para) +msgid "NetApp NFS driver for clustered Data ONTAP." +msgstr "" + +#: ./doc/config-reference/block-storage/drivers/netapp-volume-driver.xml:397(para) +msgid "NetApp iSCSI driver for Data ONTAP operating in 7-Mode storage controller." +msgstr "" + +#: ./doc/config-reference/block-storage/drivers/netapp-volume-driver.xml:404(para) +msgid "NetApp NFS driver for Data ONTAP operating in 7-Mode storage controller." +msgstr "" + +#: ./doc/config-reference/block-storage/drivers/netapp-volume-driver.xml:412(para) +msgid "See the OpenStack NetApp community for support information on deprecated NetApp drivers in the Havana release." +msgstr "" + +#: ./doc/config-reference/block-storage/drivers/huawei-storage-driver.xml:6(title) +msgid "Huawei storage driver" +msgstr "" + +#: ./doc/config-reference/block-storage/drivers/huawei-storage-driver.xml:7(para) +msgid "Huawei driver supports the iSCSI and Fibre Channel connections and enables OceanStor T series unified storage, OceanStor Dorado high-performance storage, and OceanStor HVS high-end storage to provide block storage services for OpenStack." +msgstr "" + +#: ./doc/config-reference/block-storage/drivers/huawei-storage-driver.xml:20(para) ./doc/config-reference/block-storage/drivers/huawei-storage-driver.xml:51(para) ./doc/config-reference/block-storage/drivers/huawei-storage-driver.xml:77(para) ./doc/config-reference/block-storage/drivers/huawei-storage-driver.xml:96(para) ./doc/config-reference/block-storage/drivers/emc-volume-driver.xml:39(para) ./doc/config-reference/block-storage/drivers/hds-volume-driver.xml:33(para) +msgid "Delete volume" +msgstr "" + +#: ./doc/config-reference/block-storage/drivers/huawei-storage-driver.xml:23(para) ./doc/config-reference/block-storage/drivers/huawei-storage-driver.xml:54(para) ./doc/config-reference/block-storage/drivers/huawei-storage-driver.xml:80(para) ./doc/config-reference/block-storage/drivers/huawei-storage-driver.xml:99(para) ./doc/config-reference/block-storage/drivers/emc-volume-driver.xml:42(para) ./doc/config-reference/block-storage/drivers/hds-volume-driver.xml:36(para) +msgid "Attach volume" +msgstr "" + +#: ./doc/config-reference/block-storage/drivers/huawei-storage-driver.xml:29(para) ./doc/config-reference/block-storage/drivers/huawei-storage-driver.xml:60(para) ./doc/config-reference/block-storage/drivers/huawei-storage-driver.xml:105(para) ./doc/config-reference/block-storage/drivers/emc-volume-driver.xml:48(para) ./doc/config-reference/block-storage/drivers/hds-volume-driver.xml:48(para) +msgid "Create snapshot" +msgstr "" + +#: ./doc/config-reference/block-storage/drivers/huawei-storage-driver.xml:32(para) ./doc/config-reference/block-storage/drivers/huawei-storage-driver.xml:63(para) ./doc/config-reference/block-storage/drivers/huawei-storage-driver.xml:108(para) ./doc/config-reference/block-storage/drivers/emc-volume-driver.xml:51(para) ./doc/config-reference/block-storage/drivers/hds-volume-driver.xml:51(para) +msgid "Delete snapshot" +msgstr "" + +#: ./doc/config-reference/block-storage/drivers/huawei-storage-driver.xml:38(para) ./doc/config-reference/block-storage/drivers/huawei-storage-driver.xml:114(para) +msgid "Create clone volume" +msgstr "" + +#: ./doc/config-reference/block-storage/drivers/huawei-storage-driver.xml:41(para) ./doc/config-reference/block-storage/drivers/huawei-storage-driver.xml:66(para) ./doc/config-reference/block-storage/drivers/huawei-storage-driver.xml:86(para) ./doc/config-reference/block-storage/drivers/huawei-storage-driver.xml:117(para) ./doc/config-reference/block-storage/drivers/emc-volume-driver.xml:57(para) ./doc/config-reference/block-storage/drivers/hds-volume-driver.xml:54(para) +msgid "Copy image to volume" +msgstr "" + +#: ./doc/config-reference/block-storage/drivers/huawei-storage-driver.xml:44(para) ./doc/config-reference/block-storage/drivers/huawei-storage-driver.xml:69(para) ./doc/config-reference/block-storage/drivers/huawei-storage-driver.xml:89(para) ./doc/config-reference/block-storage/drivers/huawei-storage-driver.xml:120(para) ./doc/config-reference/block-storage/drivers/emc-volume-driver.xml:60(para) ./doc/config-reference/block-storage/drivers/hds-volume-driver.xml:57(para) +msgid "Copy volume to image" +msgstr "" + +#: ./doc/config-reference/block-storage/drivers/huawei-storage-driver.xml:14(para) +msgid "OceanStor T series unified storage supports the following operations:OceanStor Dorado5100 supports the following operations:OceanStor Dorado2100 G2 supports the following operations:OceanStor HVS supports the following operations:" +msgstr "" + +#: ./doc/config-reference/block-storage/drivers/huawei-storage-driver.xml:125(title) +msgid "Configure Cinder nodes" +msgstr "" + +#: ./doc/config-reference/block-storage/drivers/huawei-storage-driver.xml:126(para) +msgid "In /etc/cinder, create the driver configuration file named cinder_huawei_conf.xml." +msgstr "" + +#: ./doc/config-reference/block-storage/drivers/huawei-storage-driver.xml:129(para) +msgid "You must configure and to specify a storage system and link type. The following uses the iSCSI driver as an example. The driver configuration file of OceanStor T series unified storage is shown as follows:" +msgstr "" + +#: ./doc/config-reference/block-storage/drivers/huawei-storage-driver.xml:160(para) +msgid "The driver configuration file of OceanStor Dorado5100 is shown as follows:" +msgstr "" + +#: ./doc/config-reference/block-storage/drivers/huawei-storage-driver.xml:186(para) +msgid "The driver configuration file of OceanStor Dorado2100 G2 is shown as follows:" +msgstr "" + +#: ./doc/config-reference/block-storage/drivers/huawei-storage-driver.xml:210(para) +msgid "The driver configuration file of OceanStor HVS is shown as follows:" +msgstr "" + +#: ./doc/config-reference/block-storage/drivers/huawei-storage-driver.xml:236(para) +msgid "You do not need to configure the iSCSI target IP address for the Fibre Channel driver. In the prior example, delete the iSCSI configuration:" +msgstr "" + +#: ./doc/config-reference/block-storage/drivers/huawei-storage-driver.xml:246(para) +msgid "To add and items, you can modify the cinder.conf configuration file as follows:" +msgstr "" + +#: ./doc/config-reference/block-storage/drivers/huawei-storage-driver.xml:252(para) +msgid "You can configure multiple Huawei back-end storages as follows:" +msgstr "" + +#: ./doc/config-reference/block-storage/drivers/huawei-storage-driver.xml:263(para) +msgid "OceanStor HVS storage system supports the QoS function. You must create a QoS policy for the HVS storage system and create the volume type to enable QoS as follows:" +msgstr "" + +#: ./doc/config-reference/block-storage/drivers/huawei-storage-driver.xml:272(para) +msgid " is a QoS policy created by a user for the HVS storage system. is the self-defined volume type. Set the option to high, normal, or low." +msgstr "" + +#: ./doc/config-reference/block-storage/drivers/huawei-storage-driver.xml:280(para) +msgid "OceanStor HVS storage system supports the SmartTier function. SmartTier has three tiers. You can create the volume type to enable SmartTier as follows:" +msgstr "" + +#: ./doc/config-reference/block-storage/drivers/huawei-storage-driver.xml:288(para) +msgid " and can only be set to high, normal, or low." +msgstr "" + +#: ./doc/config-reference/block-storage/drivers/huawei-storage-driver.xml:295(title) +msgid "Configuration file details" +msgstr "" + +#: ./doc/config-reference/block-storage/drivers/huawei-storage-driver.xml:296(para) +msgid "This table describes the Huawei storage driver configuration options:" +msgstr "" + +#: ./doc/config-reference/block-storage/drivers/huawei-storage-driver.xml:299(caption) +msgid "Huawei storage driver configuration options" +msgstr "" + +#: ./doc/config-reference/block-storage/drivers/huawei-storage-driver.xml:308(td) ./doc/config-reference/block-storage/drivers/ibm-storwize-svc-driver.xml:199(td) +msgid "Flag name" +msgstr "" + +#: ./doc/config-reference/block-storage/drivers/huawei-storage-driver.xml:309(td) ./doc/config-reference/block-storage/drivers/ibm-storwize-svc-driver.xml:200(td) ./doc/config-reference/block-storage/drivers/hds-volume-driver.xml:317(td) +msgid "Type" +msgstr "" + +#: ./doc/config-reference/block-storage/drivers/huawei-storage-driver.xml:310(td) ./doc/config-reference/block-storage/drivers/ibm-storwize-svc-driver.xml:201(td) ./doc/config-reference/block-storage/drivers/hds-volume-driver.xml:318(td) +msgid "Default" +msgstr "" + +#: ./doc/config-reference/block-storage/drivers/huawei-storage-driver.xml:317(option) +msgid "Product" +msgstr "" + +#: ./doc/config-reference/block-storage/drivers/huawei-storage-driver.xml:320(para) ./doc/config-reference/block-storage/drivers/huawei-storage-driver.xml:334(td) ./doc/config-reference/block-storage/drivers/huawei-storage-driver.xml:345(td) ./doc/config-reference/block-storage/drivers/huawei-storage-driver.xml:357(para) ./doc/config-reference/block-storage/drivers/huawei-storage-driver.xml:369(td) ./doc/config-reference/block-storage/drivers/huawei-storage-driver.xml:381(para) ./doc/config-reference/block-storage/drivers/huawei-storage-driver.xml:396(para) ./doc/config-reference/block-storage/drivers/huawei-storage-driver.xml:501(td) ./doc/config-reference/block-storage/drivers/ibm-storwize-svc-driver.xml:209(para) ./doc/config-reference/block-storage/drivers/ibm-storwize-svc-driver.xml:224(para) ./doc/config-reference/block-storage/drivers/ibm-storwize-svc-driver.xml:262(para) ./doc/config-reference/block-storage/drivers/hds-volume-driver.xml:326(para) ./doc/config-reference/block-storage/drivers/hds-volume-driver.xml:334(para) ./doc/config-reference/block-storage/drivers/hds-volume-driver.xml:379(para) ./doc/config-reference/block-storage/drivers/hds-volume-driver.xml:391(para) ./doc/config-reference/block-storage/drivers/hds-volume-driver.xml:408(para) ./doc/config-reference/block-storage/drivers/hds-volume-driver.xml:419(para) +msgid "Required" +msgstr "" + +#: ./doc/config-reference/block-storage/drivers/huawei-storage-driver.xml:326(para) +msgid "Type of a storage product. Valid values are T, Dorado, or HVS." +msgstr "" + +#: ./doc/config-reference/block-storage/drivers/huawei-storage-driver.xml:333(option) +msgid "Protocol" +msgstr "" + +#: ./doc/config-reference/block-storage/drivers/huawei-storage-driver.xml:339(literal) ./doc/config-reference/block-storage/drivers/ibm-storwize-svc-driver.xml:412(para) +msgid "iSCSI" +msgstr "" + +#: ./doc/config-reference/block-storage/drivers/huawei-storage-driver.xml:340(literal) +msgid "FC" +msgstr "" + +#: ./doc/config-reference/block-storage/drivers/huawei-storage-driver.xml:338(td) +msgid "Type of a protocol. Valid values are or ." +msgstr "" + +#: ./doc/config-reference/block-storage/drivers/huawei-storage-driver.xml:344(option) +msgid "ControllerIP0" +msgstr "" + +#: ./doc/config-reference/block-storage/drivers/huawei-storage-driver.xml:349(td) +msgid "IP address of the primary controller (not required for the HVS)" +msgstr "" + +#: ./doc/config-reference/block-storage/drivers/huawei-storage-driver.xml:354(option) +msgid "ControllerIP1" +msgstr "" + +#: ./doc/config-reference/block-storage/drivers/huawei-storage-driver.xml:363(para) +msgid "IP address of the secondary controller (not required for the HVS)" +msgstr "" + +#: ./doc/config-reference/block-storage/drivers/huawei-storage-driver.xml:368(option) +msgid "HVSURL" +msgstr "" + +#: ./doc/config-reference/block-storage/drivers/huawei-storage-driver.xml:373(td) +msgid "Access address of the Rest port (required only for the HVS)" +msgstr "" + +#: ./doc/config-reference/block-storage/drivers/huawei-storage-driver.xml:378(option) +msgid "UserName" +msgstr "" + +#: ./doc/config-reference/block-storage/drivers/huawei-storage-driver.xml:387(para) +msgid "User name of an administrator" +msgstr "" + +#: ./doc/config-reference/block-storage/drivers/huawei-storage-driver.xml:392(option) +msgid "UserPassword" +msgstr "" + +#: ./doc/config-reference/block-storage/drivers/huawei-storage-driver.xml:402(para) +msgid "Password of an administrator" +msgstr "" + +#: ./doc/config-reference/block-storage/drivers/huawei-storage-driver.xml:407(option) +msgid "LUNType" +msgstr "" + +#: ./doc/config-reference/block-storage/drivers/huawei-storage-driver.xml:410(para) ./doc/config-reference/block-storage/drivers/huawei-storage-driver.xml:427(para) ./doc/config-reference/block-storage/drivers/huawei-storage-driver.xml:445(para) ./doc/config-reference/block-storage/drivers/huawei-storage-driver.xml:463(para) ./doc/config-reference/block-storage/drivers/huawei-storage-driver.xml:476(td) ./doc/config-reference/block-storage/drivers/huawei-storage-driver.xml:491(td) ./doc/config-reference/block-storage/drivers/huawei-storage-driver.xml:513(td) ./doc/config-reference/block-storage/drivers/huawei-storage-driver.xml:524(td) ./doc/config-reference/block-storage/drivers/huawei-storage-driver.xml:534(td) ./doc/config-reference/block-storage/drivers/huawei-storage-driver.xml:545(td) ./doc/config-reference/block-storage/drivers/huawei-storage-driver.xml:553(td) ./doc/config-reference/block-storage/drivers/ibm-storwize-svc-driver.xml:217(para) ./doc/config-reference/block-storage/drivers/ibm-storwize-svc-driver.xml:271(para) ./doc/config-reference/block-storage/drivers/ibm-storwize-svc-driver.xml:295(para) ./doc/config-reference/block-storage/drivers/ibm-storwize-svc-driver.xml:306(para) ./doc/config-reference/block-storage/drivers/ibm-storwize-svc-driver.xml:330(para) ./doc/config-reference/block-storage/drivers/ibm-storwize-svc-driver.xml:341(para) ./doc/config-reference/block-storage/drivers/ibm-storwize-svc-driver.xml:362(para) ./doc/config-reference/block-storage/drivers/ibm-storwize-svc-driver.xml:380(para) ./doc/config-reference/block-storage/drivers/ibm-storwize-svc-driver.xml:390(para) ./doc/config-reference/block-storage/drivers/ibm-storwize-svc-driver.xml:411(para) ./doc/config-reference/block-storage/drivers/ibm-storwize-svc-driver.xml:422(para) ./doc/config-reference/block-storage/drivers/ibm-storwize-svc-driver.xml:432(para) ./doc/config-reference/block-storage/drivers/ibm-storwize-svc-driver.xml:448(para) ./doc/config-reference/block-storage/drivers/hds-volume-driver.xml:342(para) ./doc/config-reference/block-storage/drivers/hds-volume-driver.xml:352(para) ./doc/config-reference/block-storage/drivers/hds-volume-driver.xml:364(para) ./doc/config-reference/block-storage/drivers/hds-volume-driver.xml:430(para) ./doc/config-reference/block-storage/drivers/hds-volume-driver.xml:441(para) +msgid "Optional" +msgstr "" + +#: ./doc/config-reference/block-storage/drivers/huawei-storage-driver.xml:413(para) +msgid "Thin" +msgstr "" + +#: ./doc/config-reference/block-storage/drivers/huawei-storage-driver.xml:416(para) +msgid "Type of a created LUN. Valid values are Thick or Thin." +msgstr "" + +#: ./doc/config-reference/block-storage/drivers/huawei-storage-driver.xml:423(option) +msgid "StripUnitSize" +msgstr "" + +#: ./doc/config-reference/block-storage/drivers/huawei-storage-driver.xml:430(para) +msgid "64" +msgstr "" + +#: ./doc/config-reference/block-storage/drivers/huawei-storage-driver.xml:433(para) +msgid "Stripe depth of a created LUN. The value is expressed in KB." +msgstr "" + +#: ./doc/config-reference/block-storage/drivers/huawei-storage-driver.xml:435(para) +msgid "This flag is not valid for a thin LUN." +msgstr "" + +#: ./doc/config-reference/block-storage/drivers/huawei-storage-driver.xml:441(option) +msgid "WriteType" +msgstr "" + +#: ./doc/config-reference/block-storage/drivers/huawei-storage-driver.xml:448(para) ./doc/config-reference/block-storage/drivers/huawei-storage-driver.xml:466(para) +msgid "1" +msgstr "" + +#: ./doc/config-reference/block-storage/drivers/huawei-storage-driver.xml:451(para) +msgid "Cache write method. The method can be write back, write through, or Required write back. The default value is 1, indicating write back." +msgstr "" + +#: ./doc/config-reference/block-storage/drivers/huawei-storage-driver.xml:460(option) +msgid "MirrorSwitch" +msgstr "" + +#: ./doc/config-reference/block-storage/drivers/huawei-storage-driver.xml:469(para) +msgid "Cache mirroring policy. The default value is 1, indicating that a mirroring policy is used." +msgstr "" + +#: ./doc/config-reference/block-storage/drivers/huawei-storage-driver.xml:475(option) +msgid "Prefetch Type" +msgstr "" + +#: ./doc/config-reference/block-storage/drivers/huawei-storage-driver.xml:478(para) +msgid "3" +msgstr "" + +#: ./doc/config-reference/block-storage/drivers/huawei-storage-driver.xml:481(para) +msgid "Cache prefetch strategy. The strategy can be constant prefetch, variable prefetch, or intelligent prefetch. Default value is 3, which indicates intelligent prefetch and is not required for the HVS." +msgstr "" + +#: ./doc/config-reference/block-storage/drivers/huawei-storage-driver.xml:490(option) +msgid "Prefetch Value" +msgstr "" + +#: ./doc/config-reference/block-storage/drivers/huawei-storage-driver.xml:493(para) ./doc/config-reference/block-storage/drivers/ibm-storwize-svc-driver.xml:381(para) ./doc/config-reference/block-storage/drivers/hds-volume-driver.xml:431(para) +msgid "0" +msgstr "" + +#: ./doc/config-reference/block-storage/drivers/huawei-storage-driver.xml:496(para) +msgid "Cache prefetch value." +msgstr "" + +#: ./doc/config-reference/block-storage/drivers/huawei-storage-driver.xml:500(option) +msgid "StoragePool" +msgstr "" + +#: ./doc/config-reference/block-storage/drivers/huawei-storage-driver.xml:506(para) +msgid "Name of a storage pool that you want to use. Not required for the Dorado2100 G2." +msgstr "" + +#: ./doc/config-reference/block-storage/drivers/huawei-storage-driver.xml:512(option) +msgid "DefaultTargetIP" +msgstr "" + +#: ./doc/config-reference/block-storage/drivers/huawei-storage-driver.xml:518(para) +msgid "Default IP address of the iSCSI port provided for compute nodes." +msgstr "" + +#: ./doc/config-reference/block-storage/drivers/huawei-storage-driver.xml:523(option) +msgid "Initiator Name" +msgstr "" + +#: ./doc/config-reference/block-storage/drivers/huawei-storage-driver.xml:529(para) +msgid "Name of a compute node initiator." +msgstr "" + +#: ./doc/config-reference/block-storage/drivers/huawei-storage-driver.xml:533(option) +msgid "Initiator TargetIP" +msgstr "" + +#: ./doc/config-reference/block-storage/drivers/huawei-storage-driver.xml:539(para) +msgid "IP address of the iSCSI port provided for Compute nodes." +msgstr "" + +#: ./doc/config-reference/block-storage/drivers/huawei-storage-driver.xml:544(option) +msgid "OSType" +msgstr "" + +#: ./doc/config-reference/block-storage/drivers/huawei-storage-driver.xml:547(para) +msgid "Linux" +msgstr "" + +#: ./doc/config-reference/block-storage/drivers/huawei-storage-driver.xml:549(td) +msgid "The OS type for a Compute node." +msgstr "" + +#: ./doc/config-reference/block-storage/drivers/huawei-storage-driver.xml:552(option) +msgid "HostIP" +msgstr "" + +#: ./doc/config-reference/block-storage/drivers/huawei-storage-driver.xml:557(td) +msgid "The IPs for Compute nodes." +msgstr "" + +#: ./doc/config-reference/block-storage/drivers/huawei-storage-driver.xml:564(para) +msgid "You can configure one iSCSI target port for each or all Compute nodes. The driver checks whether a target port IP address is configured for the current Compute node. If not, select ." +msgstr "" + +#: ./doc/config-reference/block-storage/drivers/huawei-storage-driver.xml:571(para) +msgid "You can configure multiple storage pools in one configuration file, which supports the use of multiple storage pools in a storage system. (HVS allows configuration of only one storage pool.)" +msgstr "" + +#: ./doc/config-reference/block-storage/drivers/huawei-storage-driver.xml:578(para) +msgid "For details about LUN configuration information, see the command in the command-line interface (CLI) documentation or run the on the storage system CLI." +msgstr "" + +#: ./doc/config-reference/block-storage/drivers/huawei-storage-driver.xml:587(para) +msgid "After the driver is loaded, the storage system obtains any modification of the driver configuration file in real time and you do not need to restart the cinder-volume service." +msgstr "" + +#: ./doc/config-reference/block-storage/drivers/glusterfs-driver.xml:6(title) +msgid "GlusterFS driver" +msgstr "" + +#: ./doc/config-reference/block-storage/drivers/glusterfs-driver.xml:7(para) +msgid "GlusterFS is an open-source scalable distributed file system that is able to grow to petabytes and beyond in size. More information can be found on Gluster's homepage." +msgstr "" + +#: ./doc/config-reference/block-storage/drivers/glusterfs-driver.xml:12(para) +msgid "This driver enables use of GlusterFS in a similar fashion as the NFS driver. It supports basic volume operations, and like NFS, does not support snapshot/clone." +msgstr "" + +#: ./doc/config-reference/block-storage/drivers/glusterfs-driver.xml:16(para) +msgid "You must use a Linux kernel of version 3.4 or greater (or version 2.6.32 or greater in RHEL/CentOS 6.3+) when working with Gluster-based volumes. See Bug 1177103 for more information." +msgstr "" + +#: ./doc/config-reference/block-storage/drivers/glusterfs-driver.xml:22(para) +msgid "To use Cinder with GlusterFS, first set the volume_driver in cinder.conf:" +msgstr "" + +#: ./doc/config-reference/block-storage/drivers/glusterfs-driver.xml:26(para) +msgid "The following table contains the configuration options supported by the GlusterFS driver." +msgstr "" + +#: ./doc/config-reference/block-storage/drivers/emc-volume-driver.xml:5(title) +msgid "EMC SMI-S iSCSI driver" +msgstr "" + +#: ./doc/config-reference/block-storage/drivers/emc-volume-driver.xml:6(para) +msgid "The EMC SMI-S iSCSI driver, which is based on the iSCSI driver, can create, delete, attach, and detach volumes, create and delete snapshots, and so on." +msgstr "" + +#: ./doc/config-reference/block-storage/drivers/emc-volume-driver.xml:9(para) +msgid "The EMC SMI-S iSCSI driver runs volume operations by communicating with the back-end EMC storage. It uses a CIM client in Python called PyWBEM to perform CIM operations over HTTP." +msgstr "" + +#: ./doc/config-reference/block-storage/drivers/emc-volume-driver.xml:13(para) +msgid "The EMC CIM Object Manager (ECOM) is packaged with the EMC SMI-S provider. It is a CIM server that enables CIM clients to perform CIM operations over HTTP by using SMI-S in the back-end for EMC storage operations." +msgstr "" + +#: ./doc/config-reference/block-storage/drivers/emc-volume-driver.xml:17(para) +msgid "The EMC SMI-S Provider supports the SNIA Storage Management Initiative (SMI), an ANSI standard for storage management. It supports VMAX and VNX storage systems." +msgstr "" + +#: ./doc/config-reference/block-storage/drivers/emc-volume-driver.xml:21(title) ./doc/config-reference/block-storage/drivers/hp-3par-driver.xml:16(title) ./doc/config-reference/block-storage/drivers/hds-volume-driver.xml:17(title) +msgid "System requirements" +msgstr "" + +#: ./doc/config-reference/block-storage/drivers/emc-volume-driver.xml:22(para) +msgid "EMC SMI-S Provider V4.5.1 and higher is required. You can download SMI-S from the EMC Powerlink web site. See the EMC SMI-S Provider release notes for installation instructions." +msgstr "" + +#: ./doc/config-reference/block-storage/drivers/emc-volume-driver.xml:27(para) +msgid "EMC storage VMAX Family and VNX Series are supported." +msgstr "" + +#: ./doc/config-reference/block-storage/drivers/emc-volume-driver.xml:32(para) +msgid "VMAX and VNX arrays support these operations:" +msgstr "" + +#: ./doc/config-reference/block-storage/drivers/emc-volume-driver.xml:54(para) +msgid "Create cloned volume" +msgstr "" + +#: ./doc/config-reference/block-storage/drivers/emc-volume-driver.xml:63(para) +msgid "Only VNX supports these operations:" +msgstr "" + +#: ./doc/config-reference/block-storage/drivers/emc-volume-driver.xml:69(para) +msgid "Only thin provisioning is supported." +msgstr "" + +#: ./doc/config-reference/block-storage/drivers/emc-volume-driver.xml:72(title) +msgid "Task flow" +msgstr "" + +#: ./doc/config-reference/block-storage/drivers/emc-volume-driver.xml:74(title) +msgid "To set up the EMC SMI-S iSCSI driver" +msgstr "" + +#: ./doc/config-reference/block-storage/drivers/emc-volume-driver.xml:76(para) +msgid "Install the python-pywbem package for your distribution. See ." +msgstr "" + +#: ./doc/config-reference/block-storage/drivers/emc-volume-driver.xml:81(para) +msgid "Download SMI-S from PowerLink and install it. Add your VNX/VMAX arrays to SMI-S." +msgstr "" + +#: ./doc/config-reference/block-storage/drivers/emc-volume-driver.xml:83(para) +msgid "For information, see and the SMI-S release notes." +msgstr "" + +#: ./doc/config-reference/block-storage/drivers/emc-volume-driver.xml:87(para) +msgid "Register with VNX. See ." +msgstr "" + +#: ./doc/config-reference/block-storage/drivers/emc-volume-driver.xml:91(para) +msgid "Create a masking view on VMAX. See ." +msgstr "" + +#: ./doc/config-reference/block-storage/drivers/emc-volume-driver.xml:96(title) +msgid "Install the python-pywbem package" +msgstr "" + +#: ./doc/config-reference/block-storage/drivers/emc-volume-driver.xml:99(para) +msgid "Install the python-pywbem package for your distribution:" +msgstr "" + +#: ./doc/config-reference/block-storage/drivers/emc-volume-driver.xml:103(para) +msgid "On Ubuntu:" +msgstr "" + +#: ./doc/config-reference/block-storage/drivers/emc-volume-driver.xml:107(para) +msgid "On openSUSE:" +msgstr "" + +#: ./doc/config-reference/block-storage/drivers/emc-volume-driver.xml:111(para) +msgid "On Fedora:" +msgstr "" + +#: ./doc/config-reference/block-storage/drivers/emc-volume-driver.xml:119(title) +msgid "Set up SMI-S" +msgstr "" + +#: ./doc/config-reference/block-storage/drivers/emc-volume-driver.xml:120(para) +msgid "You can install SMI-S on a non-OpenStack host. Supported platforms include different flavors of Windows, Red Hat, and SUSE Linux. The host can be either a physical server or VM hosted by an ESX server. See the EMC SMI-S Provider release notes for supported platforms and installation instructions." +msgstr "" + +#: ./doc/config-reference/block-storage/drivers/emc-volume-driver.xml:127(para) +msgid "You must discover storage arrays on the SMI-S server before you can use the Cinder driver. Follow instructions in the SMI-S release notes." +msgstr "" + +#: ./doc/config-reference/block-storage/drivers/emc-volume-driver.xml:131(para) +msgid "SMI-S is usually installed at /opt/emc/ECIM/ECOM/bin on Linux and C:\\Program Files\\EMC\\ECIM\\ECOM\\bin on Windows. After you install and configure SMI-S, go to that directory and type ." +msgstr "" + +#: ./doc/config-reference/block-storage/drivers/emc-volume-driver.xml:138(para) +msgid "Use in to add an array. Use and examine the output after the array is added. Make sure that the arrays are recognized by the SMI-S server before using the EMC Cinder driver." +msgstr "" + +#: ./doc/config-reference/block-storage/drivers/emc-volume-driver.xml:146(title) +msgid "Register with VNX" +msgstr "" + +#: ./doc/config-reference/block-storage/drivers/emc-volume-driver.xml:147(para) +msgid "To export a VNX volume to a Compute node, you must register the node with VNX." +msgstr "" + +#: ./doc/config-reference/block-storage/drivers/emc-volume-driver.xml:149(para) +msgid "On the Compute node 1.1.1.1, run these commands (assume 10.10.61.35 is the iscsi target):" +msgstr "" + +#: ./doc/config-reference/block-storage/drivers/emc-volume-driver.xml:152(literal) ./doc/config-reference/block-storage/drivers/emc-volume-driver.xml:158(literal) +msgid "10.10.61.35" +msgstr "" + +#: ./doc/config-reference/block-storage/drivers/emc-volume-driver.xml:156(para) +msgid "Log in to VNX from the Compute node by using the target corresponding to the SPA port:" +msgstr "" + +#: ./doc/config-reference/block-storage/drivers/emc-volume-driver.xml:158(literal) +msgid "iqn.1992-04.com.emc:cx.apm01234567890.a0" +msgstr "" + +#: ./doc/config-reference/block-storage/drivers/emc-volume-driver.xml:159(para) +msgid "Assume iqn.1993-08.org.debian:01:1a2b3c4d5f6g is the initiator name of the Compute node. Log in to Unisphere, go to VNX00000->Hosts->Initiators, refresh and wait until initiator iqn.1993-08.org.debian:01:1a2b3c4d5f6g with SP Port A-8v0 appears." +msgstr "" + +#: ./doc/config-reference/block-storage/drivers/emc-volume-driver.xml:167(para) +msgid "Click Register, select CLARiiON/VNX, and enter the myhost1 host name and myhost1 IP address. Click Register. Now the 1.1.1.1 host appears under HostsHost List as well." +msgstr "" + +#: ./doc/config-reference/block-storage/drivers/emc-volume-driver.xml:172(para) +msgid "Log out of VNX on the Compute node:" +msgstr "" + +#: ./doc/config-reference/block-storage/drivers/emc-volume-driver.xml:174(para) +msgid "Log in to VNX from the Compute node using the target corresponding to the SPB port:" +msgstr "" + +#: ./doc/config-reference/block-storage/drivers/emc-volume-driver.xml:177(para) +msgid "In Unisphere, register the initiator with the SPB port." +msgstr "" + +#: ./doc/config-reference/block-storage/drivers/emc-volume-driver.xml:179(para) +msgid "Log out:" +msgstr "" + +#: ./doc/config-reference/block-storage/drivers/emc-volume-driver.xml:183(title) +msgid "Create a masking view on VMAX" +msgstr "" + +#: ./doc/config-reference/block-storage/drivers/emc-volume-driver.xml:184(para) +msgid "For VMAX, you must set up the Unisphere for VMAX server. On the Unisphere for VMAX server, create initiator group, storage group, and port group and put them in a masking view. Initiator group contains the initiator names of the OpenStack hosts. Storage group must have at least six gatekeepers." +msgstr "" + +#: ./doc/config-reference/block-storage/drivers/emc-volume-driver.xml:194(para) +msgid "Make the following changes in /etc/cinder/cinder.conf." +msgstr "" + +#: ./doc/config-reference/block-storage/drivers/emc-volume-driver.xml:196(para) +msgid "For VMAX, add the following entries, where 10.10.61.45 is the IP address of the VMAX iscsi target:" +msgstr "" + +#: ./doc/config-reference/block-storage/drivers/emc-volume-driver.xml:203(para) +msgid "For VNX, add the following entries, where 10.10.61.35 is the IP address of the VNX iscsi target:" +msgstr "" + +#: ./doc/config-reference/block-storage/drivers/emc-volume-driver.xml:210(para) +msgid "Restart the cinder-volume service." +msgstr "" + +#: ./doc/config-reference/block-storage/drivers/emc-volume-driver.xml:214(title) +msgid "cinder_emc_config.xml configuration file" +msgstr "" + +#: ./doc/config-reference/block-storage/drivers/emc-volume-driver.xml:216(para) +msgid "Create the file /etc/cinder/cinder_emc_config.xml. You do not need to restart the service for this change." +msgstr "" + +#: ./doc/config-reference/block-storage/drivers/emc-volume-driver.xml:220(para) +msgid "For VMAX, add the following lines to the XML file:" +msgstr "" + +#: ./doc/config-reference/block-storage/drivers/emc-volume-driver.xml:231(para) +msgid "For VNX, add the following lines to the XML file:" +msgstr "" + +#: ./doc/config-reference/block-storage/drivers/emc-volume-driver.xml:241(para) +msgid "To attach VMAX volumes to an OpenStack VM, you must create a Masking View by using Unisphere for VMAX. The Masking View must have an Initiator Group that contains the initiator of the OpenStack compute node that hosts the VM." +msgstr "" + +#: ./doc/config-reference/block-storage/drivers/emc-volume-driver.xml:246(para) +msgid "StorageType is the thin pool where user wants to create the volume from. Only thin LUNs are supported by the plug-in. Thin pools can be created using Unisphere for VMAX and VNX." +msgstr "" + +#: ./doc/config-reference/block-storage/drivers/emc-volume-driver.xml:250(para) +msgid "EcomServerIp and EcomServerPort are the IP address and port number of the ECOM server which is packaged with SMI-S. EcomUserName and EcomPassword are credentials for the ECOM server." +msgstr "" + +#: ./doc/config-reference/block-storage/drivers/hp-3par-driver.xml:4(title) +msgid "HP 3PAR Fibre Channel and iSCSI drivers" +msgstr "" + +#: ./doc/config-reference/block-storage/drivers/hp-3par-driver.xml:5(para) +msgid "The HP3PARFCDriver and HP3PARISCSIDriver drivers, which are based on the Block Storage Service (Cinder) plug-in architecture, run volume operations by communicating with the HP 3PAR storage system over HTTP, HTTPS, and SSH connections. The HTTP and HTTPS communications use hp3parclient, which is part of the Python standard library." +msgstr "" + +#: ./doc/config-reference/block-storage/drivers/hp-3par-driver.xml:13(para) +msgid "For information about how to manage HP 3PAR storage systems, see the HP 3PAR user documentation." +msgstr "" + +#: ./doc/config-reference/block-storage/drivers/hp-3par-driver.xml:17(para) +msgid "To use the HP 3PAR drivers, install the following software and components on the HP 3PAR storage system:" +msgstr "" + +#: ./doc/config-reference/block-storage/drivers/hp-3par-driver.xml:22(para) +msgid "HP 3PAR Operating System software version 3.1.2 (MU2) or higher" +msgstr "" + +#: ./doc/config-reference/block-storage/drivers/hp-3par-driver.xml:26(para) +msgid "HP 3PAR Web Services API Server must be enabled and running" +msgstr "" + +#: ./doc/config-reference/block-storage/drivers/hp-3par-driver.xml:30(para) +msgid "One Common Provisioning Group (CPG)" +msgstr "" + +#: ./doc/config-reference/block-storage/drivers/hp-3par-driver.xml:33(para) +msgid "Additionally, you must install the hp3parclient version 2.0 or newer from the Python standard library on the system with the enabled Block Storage Service volume drivers." +msgstr "" + +#: ./doc/config-reference/block-storage/drivers/hp-3par-driver.xml:45(para) +msgid "Create volumes." +msgstr "" + +#: ./doc/config-reference/block-storage/drivers/hp-3par-driver.xml:48(para) +msgid "Delete volumes." +msgstr "" + +#: ./doc/config-reference/block-storage/drivers/hp-3par-driver.xml:51(para) +msgid "Extend volumes." +msgstr "" + +#: ./doc/config-reference/block-storage/drivers/hp-3par-driver.xml:54(para) +msgid "Attach volumes." +msgstr "" + +#: ./doc/config-reference/block-storage/drivers/hp-3par-driver.xml:57(para) +msgid "Detach volumes." +msgstr "" + +#: ./doc/config-reference/block-storage/drivers/hp-3par-driver.xml:60(para) +msgid "Create snapshots." +msgstr "" + +#: ./doc/config-reference/block-storage/drivers/hp-3par-driver.xml:63(para) +msgid "Delete snapshots." +msgstr "" + +#: ./doc/config-reference/block-storage/drivers/hp-3par-driver.xml:66(para) +msgid "Create volumes from snapshots." +msgstr "" + +#: ./doc/config-reference/block-storage/drivers/hp-3par-driver.xml:69(para) +msgid "Create cloned volumes." +msgstr "" + +#: ./doc/config-reference/block-storage/drivers/hp-3par-driver.xml:72(para) +msgid "Copy images to volumes." +msgstr "" + +#: ./doc/config-reference/block-storage/drivers/hp-3par-driver.xml:75(para) +msgid "Copy volumes to images." +msgstr "" + +#: ./doc/config-reference/block-storage/drivers/hp-3par-driver.xml:78(para) +msgid "Volume type support for both HP 3PAR drivers includes the ability to set the following capabilities in the OpenStack Cinder API cinder.api.contrib.types_extra_specs volume type extra specs extension module:" +msgstr "" + +#: ./doc/config-reference/block-storage/drivers/hp-3par-driver.xml:85(literal) +msgid "hp3par:cpg" +msgstr "" + +#: ./doc/config-reference/block-storage/drivers/hp-3par-driver.xml:88(literal) +msgid "hp3par:snap_cpg" +msgstr "" + +#: ./doc/config-reference/block-storage/drivers/hp-3par-driver.xml:91(literal) +msgid "hp3par:provisioning" +msgstr "" + +#: ./doc/config-reference/block-storage/drivers/hp-3par-driver.xml:94(literal) +msgid "hp3par:persona" +msgstr "" + +#: ./doc/config-reference/block-storage/drivers/hp-3par-driver.xml:97(literal) +msgid "hp3par:vvs" +msgstr "" + +#: ./doc/config-reference/block-storage/drivers/hp-3par-driver.xml:100(literal) +msgid "qos:maxBWS" +msgstr "" + +#: ./doc/config-reference/block-storage/drivers/hp-3par-driver.xml:103(literal) +msgid "qos:maxIOPS" +msgstr "" + +#: ./doc/config-reference/block-storage/drivers/hp-3par-driver.xml:106(para) +msgid "To work with the default filter scheduler, the key values are case sensitive and scoped with hp3par: or qos:. For information about how to set the key-value pairs and associate them with a volume type, run the following command: " +msgstr "" + +#: ./doc/config-reference/block-storage/drivers/hp-3par-driver.xml:116(para) +msgid "Volumes that are cloned only support extra specs keys cpg, snap_cpg, provisioning and vvs. The others are ignored. In addition the comments section of the cloned volume in the HP 3PAR StoreServ storage array is not populated." +msgstr "" + +#: ./doc/config-reference/block-storage/drivers/hp-3par-driver.xml:122(para) +msgid "The following keys require that the HP 3PAR StoreServ storage array has a Priority Optimization license installed." +msgstr "" + +#: ./doc/config-reference/block-storage/drivers/hp-3par-driver.xml:127(para) +msgid "hp3par:vvs - The virtual volume set name that has been predefined by the Administrator with Quality of Service (QoS) rules associated to it. If you specify hp3par:vvs, the qos:maxIOPS and qos:maxBWS settings are ignored." +msgstr "" + +#: ./doc/config-reference/block-storage/drivers/hp-3par-driver.xml:137(para) +msgid "qos:maxBWS - The QoS I/O issue count rate limit in MBs. If not set, the I/O issue bandwidth rate has no limit." +msgstr "" + +#: ./doc/config-reference/block-storage/drivers/hp-3par-driver.xml:142(para) +msgid "qos:maxIOPS - The QoS I/O issue count rate limit. If not set, the I/O issue count rate has no limit." +msgstr "" + +#: ./doc/config-reference/block-storage/drivers/hp-3par-driver.xml:147(para) +msgid "If volume types are not used or a particular key is not set for a volume type, the following defaults are used." +msgstr "" + +#: ./doc/config-reference/block-storage/drivers/hp-3par-driver.xml:152(para) +msgid "hp3par:cpg - Defaults to the hp3par_cpg setting in the cinder.conf file." +msgstr "" + +#: ./doc/config-reference/block-storage/drivers/hp-3par-driver.xml:157(para) +msgid "hp3par:snap_cpg - Defaults to the hp3par_snap setting in the cinder.conf file. If hp3par_snap is not set, it defaults to the hp3par_cpg setting." +msgstr "" + +#: ./doc/config-reference/block-storage/drivers/hp-3par-driver.xml:165(para) +msgid "hp3par:provisioning - Defaults to thin provisioning, the valid values are thin and full." +msgstr "" + +#: ./doc/config-reference/block-storage/drivers/hp-3par-driver.xml:171(para) +msgid "hp3par:persona - Defaults to the 1 – Generic persona. The valid values are, 1 – Generic, 2 - Generic-ALUA, 6 - Generic-legacy, 7 - HPUX-legacy, 8 - AIX-legacy, 9 – EGENERA, 10 - ONTAP-legacy, 11 – VMware, and 12 - OpenVMS." +msgstr "" + +#: ./doc/config-reference/block-storage/drivers/hp-3par-driver.xml:186(title) +msgid "Enable the HP 3PAR Fibre Channel and iSCSI drivers" +msgstr "" + +#: ./doc/config-reference/block-storage/drivers/hp-3par-driver.xml:188(para) +msgid "The HP3PARFCDriver and HP3PARISCSIDriver are installed with the OpenStack software." +msgstr "" + +#: ./doc/config-reference/block-storage/drivers/hp-3par-driver.xml:193(para) +msgid "Install the hp3parclient Python package on the OpenStack Block Storage system. " +msgstr "" + +#: ./doc/config-reference/block-storage/drivers/hp-3par-driver.xml:200(para) +msgid "Verify that the HP 3PAR Web Services API server is enabled and running on the HP 3PAR storage system." +msgstr "" + +#: ./doc/config-reference/block-storage/drivers/hp-3par-driver.xml:205(para) +msgid "Log onto the HP 3PAR storage system with administrator access." +msgstr "" + +#: ./doc/config-reference/block-storage/drivers/hp-3par-driver.xml:210(para) +msgid "View the current state of the Web Services API Server. " +msgstr "" + +#: ./doc/config-reference/block-storage/drivers/hp-3par-driver.xml:217(para) +msgid "If the Web Services API Server is disabled, start it." +msgstr "" + +#: ./doc/config-reference/block-storage/drivers/hp-3par-driver.xml:227(para) +msgid "To stop the Web Services API Server, use the stopwsapi command. For other options run the command." +msgstr "" + +#: ./doc/config-reference/block-storage/drivers/hp-3par-driver.xml:224(para) +msgid "If the HTTP or HTTPS state is disabled, enable one of them. or " +msgstr "" + +#: ./doc/config-reference/block-storage/drivers/hp-3par-driver.xml:234(para) +msgid "If you are not using an existing CPG, create a CPG on the HP 3PAR storage system to be used as the default location for creating volumes." +msgstr "" + +#: ./doc/config-reference/block-storage/drivers/hp-3par-driver.xml:239(para) +msgid "Make the following changes in the /etc/cinder/cinder.conf file." +msgstr "" + +#: ./doc/config-reference/block-storage/drivers/hp-3par-driver.xml:243(emphasis) +msgid "## REQUIRED SETTINGS" +msgstr "" + +#: ./doc/config-reference/block-storage/drivers/hp-3par-driver.xml:277(emphasis) +msgid "## OPTIONAL SETTINGS" +msgstr "" + +#: ./doc/config-reference/block-storage/drivers/hp-3par-driver.xml:291(para) +msgid "You can enable only one driver on each cinder instance unless you enable multiple back-end support. See the Cinder multiple back-end support instructions to enable this feature." +msgstr "" + +#: ./doc/config-reference/block-storage/drivers/hp-3par-driver.xml:298(para) +msgid "You can configure one or more iSCSI addresses by using the option. When you configure multiple addresses, the driver selects the iSCSI port with the fewest active volumes at attach time. The IP address might include an IP port by using a colon (:) to separate the address from port. If you do not define an IP port, the default port 3260 is used. Separate IP addresses with a comma (,). The / options might be used as an alternative to for single port iSCSI configuration." +msgstr "" + +#: ./doc/config-reference/block-storage/drivers/hp-3par-driver.xml:317(para) +msgid "Save the changes to the cinder.conf file and restart the cinder-volume service." +msgstr "" + +#: ./doc/config-reference/block-storage/drivers/hp-3par-driver.xml:323(para) +msgid "The HP 3PAR Fibre Channel and iSCSI drivers are now enabled on your OpenStack system. If you experience problems, review the Block Storage Service log files for errors." +msgstr "" + +#: ./doc/config-reference/block-storage/drivers/dell-equallogic-driver.xml:6(title) +msgid "Dell EqualLogic volume driver" +msgstr "" + +#: ./doc/config-reference/block-storage/drivers/dell-equallogic-driver.xml:7(para) +msgid "The Dell EqualLogic volume driver interacts with configured EqualLogic arrays and supports various operations, such as volume creation and deletion, volume attachment and detachment, snapshot creation and deletion, and clone creation." +msgstr "" + +#: ./doc/config-reference/block-storage/drivers/dell-equallogic-driver.xml:12(para) +msgid "To configure and use a Dell EqualLogic array with Block Storage, modify your cinder.conf as follows." +msgstr "" + +#: ./doc/config-reference/block-storage/drivers/dell-equallogic-driver.xml:15(para) +msgid "Set the option to the Dell EqualLogic volume driver:" +msgstr "" + +#: ./doc/config-reference/block-storage/drivers/dell-equallogic-driver.xml:18(para) +msgid "Set the option to the IP address to reach the EqualLogic Group through SSH:" +msgstr "" + +#: ./doc/config-reference/block-storage/drivers/dell-equallogic-driver.xml:21(para) +msgid "Set the option to the user name to login to the Group manager:" +msgstr "" + +#: ./doc/config-reference/block-storage/drivers/dell-equallogic-driver.xml:24(para) +msgid "Set the option to the password to login the Group manager with:" +msgstr "" + +#: ./doc/config-reference/block-storage/drivers/dell-equallogic-driver.xml:27(para) +msgid "Optionally set the option to false to disable creation of thin-provisioned volumes:" +msgstr "" + +#: ./doc/config-reference/block-storage/drivers/dell-equallogic-driver.xml:31(para) +msgid "The following table describes additional options that the driver supports:" +msgstr "" + +#: ./doc/config-reference/block-storage/drivers/ibm-storwize-svc-driver.xml:5(title) +msgid "IBM Storwize family and SVC volume driver" +msgstr "" + +#: ./doc/config-reference/block-storage/drivers/ibm-storwize-svc-driver.xml:6(para) +msgid "The volume management driver for Storwize family and SAN Volume Controller (SVC) provides OpenStack Compute instances with access to IBM Storwize family or SVC storage systems." +msgstr "" + +#: ./doc/config-reference/block-storage/drivers/ibm-storwize-svc-driver.xml:11(title) +msgid "Configure the Storwize family and SVC system" +msgstr "" + +#: ./doc/config-reference/block-storage/drivers/ibm-storwize-svc-driver.xml:13(title) +msgid "Network configuration" +msgstr "" + +#: ./doc/config-reference/block-storage/drivers/ibm-storwize-svc-driver.xml:14(para) +msgid "The Storwize family or SVC system must be configured for iSCSI, Fibre Channel, or both." +msgstr "" + +#: ./doc/config-reference/block-storage/drivers/ibm-storwize-svc-driver.xml:16(para) +msgid "If using iSCSI, each Storwize family or SVC node should have at least one iSCSI IP address. The IBM Storwize/SVC driver uses an iSCSI IP address associated with the volume's preferred node (if available) to attach the volume to the instance, otherwise it uses the first available iSCSI IP address of the system. The driver obtains the iSCSI IP address directly from the storage system; you do not need to provide these iSCSI IP addresses directly to the driver." +msgstr "" + +#: ./doc/config-reference/block-storage/drivers/ibm-storwize-svc-driver.xml:27(para) +msgid "If using iSCSI, ensure that the compute nodes have iSCSI network access to the Storwize family or SVC system." +msgstr "" + +#: ./doc/config-reference/block-storage/drivers/ibm-storwize-svc-driver.xml:32(para) +msgid "OpenStack Nova's Grizzly version supports iSCSI multipath. Once this is configured on the Nova host (outside the scope of this documentation), multipath is enabled." +msgstr "" + +#: ./doc/config-reference/block-storage/drivers/ibm-storwize-svc-driver.xml:37(para) +msgid "If using Fibre Channel (FC), each Storwize family or SVC node should have at least one WWPN port configured. If the storwize_svc_multipath_enabled flag is set to True in the Cinder configuration file, the driver uses all available WWPNs to attach the volume to the instance (details about the configuration flags appear in the next section). If the flag is not set, the driver uses the WWPN associated with the volume's preferred node (if available), otherwise it uses the first available WWPN of the system. The driver obtains the WWPNs directly from the storage system; you do not need to provide these WWPNs directly to the driver." +msgstr "" + +#: ./doc/config-reference/block-storage/drivers/ibm-storwize-svc-driver.xml:53(para) +msgid "If using FC, ensure that the compute nodes have FC connectivity to the Storwize family or SVC system." +msgstr "" + +#: ./doc/config-reference/block-storage/drivers/ibm-storwize-svc-driver.xml:59(title) +msgid "iSCSI CHAP authentication" +msgstr "" + +#: ./doc/config-reference/block-storage/drivers/ibm-storwize-svc-driver.xml:67(para) +msgid "CHAP secrets are added to existing hosts as well as newly-created ones. If the CHAP option is enabled, hosts will not be able to access the storage without the generated secrets." +msgstr "" + +#: ./doc/config-reference/block-storage/drivers/ibm-storwize-svc-driver.xml:74(para) +msgid "Not all OpenStack Compute drivers support CHAP authentication. Please check compatibility before using." +msgstr "" + +#: ./doc/config-reference/block-storage/drivers/ibm-storwize-svc-driver.xml:79(para) +msgid "CHAP secrets are passed from OpenStack Block Storage to Compute in clear text. This communication should be secured to ensure that CHAP secrets are not discovered." +msgstr "" + +#: ./doc/config-reference/block-storage/drivers/ibm-storwize-svc-driver.xml:60(para) +msgid "If using iSCSI for data access and the storwize_svc_iscsi_chap_enabled is set to True, the driver will associate randomly-generated CHAP secrets with all hosts on the Storwize family system. OpenStack compute nodes use these secrets when creating iSCSI connections. " +msgstr "" + +#: ./doc/config-reference/block-storage/drivers/ibm-storwize-svc-driver.xml:86(title) +msgid "Configure storage pools" +msgstr "" + +#: ./doc/config-reference/block-storage/drivers/ibm-storwize-svc-driver.xml:87(para) +msgid "Each instance of the IBM Storwize/SVC driver allocates all volumes in a single pool. The pool should be created in advance and be provided to the driver using the storwize_svc_volpool_name configuration flag. Details about the configuration flags and how to provide the flags to the driver appear in the next section." +msgstr "" + +#: ./doc/config-reference/block-storage/drivers/ibm-storwize-svc-driver.xml:98(title) +msgid "Configure user authentication for the driver" +msgstr "" + +#: ./doc/config-reference/block-storage/drivers/ibm-storwize-svc-driver.xml:100(para) +msgid "The driver requires access to the Storwize family or SVC system management interface. The driver communicates with the management using SSH. The driver should be provided with the Storwize family or SVC management IP using the san_ip flag, and the management port should be provided by the san_ssh_port flag. By default, the port value is configured to be port 22 (SSH)." +msgstr "" + +#: ./doc/config-reference/block-storage/drivers/ibm-storwize-svc-driver.xml:110(para) +msgid "Make sure the compute node running the nova-volume management driver has SSH network access to the storage system." +msgstr "" + +#: ./doc/config-reference/block-storage/drivers/ibm-storwize-svc-driver.xml:114(para) +msgid "To allow the driver to communicate with the Storwize family or SVC system, you must provide the driver with a user on the storage system. The driver has two authentication methods: password-based authentication and SSH key pair authentication. The user should have an Administrator role. It is suggested to create a new user for the management driver. Please consult with your storage and security administrator regarding the preferred authentication method and how passwords or SSH keys should be stored in a secure manner." +msgstr "" + +#: ./doc/config-reference/block-storage/drivers/ibm-storwize-svc-driver.xml:125(para) +msgid "When creating a new user on the Storwize or SVC system, make sure the user belongs to the Administrator group or to another group that has an Administrator role." +msgstr "" + +#: ./doc/config-reference/block-storage/drivers/ibm-storwize-svc-driver.xml:130(para) +msgid "If using password authentication, assign a password to the user on the Storwize or SVC system. The driver configuration flags for the user and password are san_login and san_password, respectively." +msgstr "" + +#: ./doc/config-reference/block-storage/drivers/ibm-storwize-svc-driver.xml:136(para) +msgid "If you are using the SSH key pair authentication, create SSH private and public keys using the instructions below or by any other method. Associate the public key with the user by uploading the public key: select the \"choose file\" option in the Storwize family or SVC management GUI under \"SSH public key\". Alternatively, you may associate the SSH public key using the command line interface; details can be found in the Storwize and SVC documentation. The private key should be provided to the driver using the san_private_key configuration flag." +msgstr "" + +#: ./doc/config-reference/block-storage/drivers/ibm-storwize-svc-driver.xml:150(title) +msgid "Create a SSH key pair with OpenSSH" +msgstr "" + +#: ./doc/config-reference/block-storage/drivers/ibm-storwize-svc-driver.xml:151(para) +msgid "You can create an SSH key pair using OpenSSH, by running:" +msgstr "" + +#: ./doc/config-reference/block-storage/drivers/ibm-storwize-svc-driver.xml:154(para) +msgid "The command prompts for a file to save the key pair. For example, if you select 'key' as the filename, two files are created: key and key.pub. The key file holds the private SSH key and key.pub holds the public SSH key." +msgstr "" + +#: ./doc/config-reference/block-storage/drivers/ibm-storwize-svc-driver.xml:161(para) +msgid "The command also prompts for a pass phrase, which should be empty." +msgstr "" + +#: ./doc/config-reference/block-storage/drivers/ibm-storwize-svc-driver.xml:163(para) +msgid "The private key file should be provided to the driver using the san_private_key configuration flag. The public key should be uploaded to the Storwize family or SVC system using the storage management GUI or command line interface." +msgstr "" + +#: ./doc/config-reference/block-storage/drivers/ibm-storwize-svc-driver.xml:169(para) +msgid "Ensure that Cinder has read permissions on the private key file." +msgstr "" + +#: ./doc/config-reference/block-storage/drivers/ibm-storwize-svc-driver.xml:175(title) +msgid "Configure the Storwize family and SVC driver" +msgstr "" + +#: ./doc/config-reference/block-storage/drivers/ibm-storwize-svc-driver.xml:177(title) +msgid "Enable the Storwize family and SVC driver" +msgstr "" + +#: ./doc/config-reference/block-storage/drivers/ibm-storwize-svc-driver.xml:178(para) +msgid "Set the volume driver to the Storwize family and SVC driver by setting the volume_driver option in cinder.conf as follows:" +msgstr "" + +#: ./doc/config-reference/block-storage/drivers/ibm-storwize-svc-driver.xml:185(title) +msgid "Storwize family and SVC driver options in cinder.conf" +msgstr "" + +#: ./doc/config-reference/block-storage/drivers/ibm-storwize-svc-driver.xml:187(para) +msgid "The following options specify default values for all volumes. Some can be over-ridden using volume types, which are described below." +msgstr "" + +#: ./doc/config-reference/block-storage/drivers/ibm-storwize-svc-driver.xml:191(caption) +msgid "List of configuration flags for Storwize storage and SVC driver" +msgstr "" + +#: ./doc/config-reference/block-storage/drivers/ibm-storwize-svc-driver.xml:207(literal) +msgid "san_ip" +msgstr "" + +#: ./doc/config-reference/block-storage/drivers/ibm-storwize-svc-driver.xml:211(para) +msgid "Management IP or host name" +msgstr "" + +#: ./doc/config-reference/block-storage/drivers/ibm-storwize-svc-driver.xml:215(literal) +msgid "san_ssh_port" +msgstr "" + +#: ./doc/config-reference/block-storage/drivers/ibm-storwize-svc-driver.xml:218(para) +msgid "22" +msgstr "" + +#: ./doc/config-reference/block-storage/drivers/ibm-storwize-svc-driver.xml:219(para) +msgid "Management port" +msgstr "" + +#: ./doc/config-reference/block-storage/drivers/ibm-storwize-svc-driver.xml:222(literal) +msgid "san_login" +msgstr "" + +#: ./doc/config-reference/block-storage/drivers/ibm-storwize-svc-driver.xml:226(para) +msgid "Management login username" +msgstr "" + +#: ./doc/config-reference/block-storage/drivers/ibm-storwize-svc-driver.xml:230(literal) +msgid "san_password" +msgstr "" + +#: ./doc/config-reference/block-storage/drivers/ibm-storwize-svc-driver.xml:234(para) +msgid "The authentication requires either a password (san_password) or SSH private key (san_private_key). One must be specified. If both are specified, the driver uses only the SSH private key." +msgstr "" + +#: ./doc/config-reference/block-storage/drivers/ibm-storwize-svc-driver.xml:232(para) +msgid "Required " +msgstr "" + +#: ./doc/config-reference/block-storage/drivers/ibm-storwize-svc-driver.xml:244(para) +msgid "Management login password" +msgstr "" + +#: ./doc/config-reference/block-storage/drivers/ibm-storwize-svc-driver.xml:248(literal) +msgid "san_private_key" +msgstr "" + +#: ./doc/config-reference/block-storage/drivers/ibm-storwize-svc-driver.xml:250(para) +msgid "Required " +msgstr "" + +#: ./doc/config-reference/block-storage/drivers/ibm-storwize-svc-driver.xml:254(para) +msgid "Management login SSH private key" +msgstr "" + +#: ./doc/config-reference/block-storage/drivers/ibm-storwize-svc-driver.xml:260(literal) +msgid "storwize_svc_volpool_name" +msgstr "" + +#: ./doc/config-reference/block-storage/drivers/ibm-storwize-svc-driver.xml:264(para) +msgid "Default pool name for volumes" +msgstr "" + +#: ./doc/config-reference/block-storage/drivers/ibm-storwize-svc-driver.xml:269(literal) +msgid "storwize_svc_vol_rsize" +msgstr "" + +#: ./doc/config-reference/block-storage/drivers/ibm-storwize-svc-driver.xml:272(para) +msgid "2" +msgstr "" + +#: ./doc/config-reference/block-storage/drivers/ibm-storwize-svc-driver.xml:276(para) +msgid "The driver creates thin-provisioned volumes by default. The storwize_svc_vol_rsize flag defines the initial physical allocation percentage for thin-provisioned volumes, or if set to -1, the driver creates full allocated volumes. More details about the available options are available in the Storwize family and SVC documentation." +msgstr "" + +#: ./doc/config-reference/block-storage/drivers/ibm-storwize-svc-driver.xml:273(para) +msgid "Initial physical allocation (percentage) " +msgstr "" + +#: ./doc/config-reference/block-storage/drivers/ibm-storwize-svc-driver.xml:293(literal) +msgid "storwize_svc_vol_warning" +msgstr "" + +#: ./doc/config-reference/block-storage/drivers/ibm-storwize-svc-driver.xml:296(para) +msgid "0 (disabled)" +msgstr "" + +#: ./doc/config-reference/block-storage/drivers/ibm-storwize-svc-driver.xml:297(para) +msgid "Space allocation warning threshold (percentage) " +msgstr "" + +#: ./doc/config-reference/block-storage/drivers/ibm-storwize-svc-driver.xml:304(literal) +msgid "storwize_svc_vol_autoexpand" +msgstr "" + +#: ./doc/config-reference/block-storage/drivers/ibm-storwize-svc-driver.xml:307(para) ./doc/config-reference/block-storage/drivers/ibm-storwize-svc-driver.xml:363(para) ./doc/config-reference/block-storage/drivers/ibm-storwize-svc-driver.xml:423(para) ./doc/config-reference/block-storage/drivers/ibm-storwize-svc-driver.xml:449(para) +msgid "True" +msgstr "" + +#: ./doc/config-reference/block-storage/drivers/ibm-storwize-svc-driver.xml:310(para) +msgid "Defines whether thin-provisioned volumes can be auto expanded by the storage system, a value of True means that auto expansion is enabled, a value of False disables auto expansion. Details about this option can be found in the –autoexpand flag of the Storwize family and SVC command line interface mkvdisk command." +msgstr "" + +#: ./doc/config-reference/block-storage/drivers/ibm-storwize-svc-driver.xml:308(para) +msgid "Enable or disable volume auto expand " +msgstr "" + +#: ./doc/config-reference/block-storage/drivers/ibm-storwize-svc-driver.xml:328(literal) +msgid "storwize_svc_vol_grainsize" +msgstr "" + +#: ./doc/config-reference/block-storage/drivers/ibm-storwize-svc-driver.xml:331(para) +msgid "256" +msgstr "" + +#: ./doc/config-reference/block-storage/drivers/ibm-storwize-svc-driver.xml:332(para) +msgid "Volume grain size in KB" +msgstr "" + +#: ./doc/config-reference/block-storage/drivers/ibm-storwize-svc-driver.xml:338(literal) +msgid "storwize_svc_vol_compression" +msgstr "" + +#: ./doc/config-reference/block-storage/drivers/ibm-storwize-svc-driver.xml:342(para) ./doc/config-reference/block-storage/drivers/ibm-storwize-svc-driver.xml:433(para) +msgid "False" +msgstr "" + +#: ./doc/config-reference/block-storage/drivers/ibm-storwize-svc-driver.xml:346(para) +msgid "Defines whether Real-time Compression is used for the volumes created with OpenStack. Details on Real-time Compression can be found in the Storwize family and SVC documentation. The Storwize or SVC system must have compression enabled for this feature to work." +msgstr "" + +#: ./doc/config-reference/block-storage/drivers/ibm-storwize-svc-driver.xml:343(para) +msgid "Enable or disable Real-time Compression " +msgstr "" + +#: ./doc/config-reference/block-storage/drivers/ibm-storwize-svc-driver.xml:360(literal) +msgid "storwize_svc_vol_easytier" +msgstr "" + +#: ./doc/config-reference/block-storage/drivers/ibm-storwize-svc-driver.xml:366(para) +msgid "Defines whether Easy Tier is used for the volumes created with OpenStack. Details on EasyTier can be found in the Storwize family and SVC documentation. The Storwize or SVC system must have Easy Tier enabled for this feature to work." +msgstr "" + +#: ./doc/config-reference/block-storage/drivers/ibm-storwize-svc-driver.xml:364(para) +msgid "Enable or disable Easy Tier " +msgstr "" + +#: ./doc/config-reference/block-storage/drivers/ibm-storwize-svc-driver.xml:378(literal) +msgid "storwize_svc_vol_iogrp" +msgstr "" + +#: ./doc/config-reference/block-storage/drivers/ibm-storwize-svc-driver.xml:382(para) +msgid "The I/O group in which to allocate vdisks" +msgstr "" + +#: ./doc/config-reference/block-storage/drivers/ibm-storwize-svc-driver.xml:387(literal) +msgid "storwize_svc_flashcopy_timeout" +msgstr "" + +#: ./doc/config-reference/block-storage/drivers/ibm-storwize-svc-driver.xml:391(para) +msgid "120" +msgstr "" + +#: ./doc/config-reference/block-storage/drivers/ibm-storwize-svc-driver.xml:394(para) +msgid "The driver wait timeout threshold when creating an OpenStack snapshot. This is actually the maximum amount of time that the driver waits for the Storwize family or SVC system to prepare a new FlashCopy mapping. The driver accepts a maximum wait time of 600 seconds (10 minutes)." +msgstr "" + +#: ./doc/config-reference/block-storage/drivers/ibm-storwize-svc-driver.xml:392(para) +msgid "FlashCopy timeout threshold (seconds)" +msgstr "" + +#: ./doc/config-reference/block-storage/drivers/ibm-storwize-svc-driver.xml:408(literal) +msgid "storwize_svc_connection_protocol" +msgstr "" + +#: ./doc/config-reference/block-storage/drivers/ibm-storwize-svc-driver.xml:413(para) +msgid "Connection protocol to use (currently supports 'iSCSI' or 'FC')" +msgstr "" + +#: ./doc/config-reference/block-storage/drivers/ibm-storwize-svc-driver.xml:419(literal) +msgid "storwize_svc_iscsi_chap_enabled" +msgstr "" + +#: ./doc/config-reference/block-storage/drivers/ibm-storwize-svc-driver.xml:424(para) +msgid "Configure CHAP authentication for iSCSI connections" +msgstr "" + +#: ./doc/config-reference/block-storage/drivers/ibm-storwize-svc-driver.xml:429(literal) +msgid "storwize_svc_multipath_enabled" +msgstr "" + +#: ./doc/config-reference/block-storage/drivers/ibm-storwize-svc-driver.xml:436(para) +msgid "Multipath for iSCSI connections requires no storage-side configuration and is enabled if the compute host has multipath configured." +msgstr "" + +#: ./doc/config-reference/block-storage/drivers/ibm-storwize-svc-driver.xml:434(para) +msgid "Enable multipath for FC connections " +msgstr "" + +#: ./doc/config-reference/block-storage/drivers/ibm-storwize-svc-driver.xml:445(literal) +msgid "storwize_svc_multihost_enabled" +msgstr "" + +#: ./doc/config-reference/block-storage/drivers/ibm-storwize-svc-driver.xml:453(para) +msgid "This option allows the driver to map a vdisk to more than one host at a time. This scenario occurs during migration of a virtual machine with an attached volume; the volume is simultaneously mapped to both the source and destination compute hosts. If your deployment does not require attaching vdisks to multiple hosts, setting this flag to False will provide added safety." +msgstr "" + +#: ./doc/config-reference/block-storage/drivers/ibm-storwize-svc-driver.xml:450(para) +msgid "Enable mapping vdisks to multiple hosts " +msgstr "" + +#: ./doc/config-reference/block-storage/drivers/ibm-storwize-svc-driver.xml:474(title) +msgid "Placement with volume types" +msgstr "" + +#: ./doc/config-reference/block-storage/drivers/ibm-storwize-svc-driver.xml:475(para) +msgid "The IBM Storwize/SVC driver exposes capabilities that can be added to the extra specs of volume types, and used by the filter scheduler to determine placement of new volumes. Make sure to prefix these keys with capabilities: to indicate that the scheduler should use them. The following extra specs are supported:" +msgstr "" + +#: ./doc/config-reference/block-storage/drivers/ibm-storwize-svc-driver.xml:486(para) +msgid "capabilities:volume_back-end_name - Specify a specific back-end where the volume should be created. The back-end name is a concatenation of the name of the IBM Storwize/SVC storage system as shown in lssystem, an underscore, and the name of the pool (mdisk group). For example: " +msgstr "" + +#: ./doc/config-reference/block-storage/drivers/ibm-storwize-svc-driver.xml:497(para) +msgid "capabilities:compression_support - Specify a back-end according to compression support. A value of True should be used to request a back-end that supports compression, and a value of False will request a back-end that does not support compression. If you do not have constraints on compression support, do not set this key. Note that specifying True does not enable compression; it only requests that the volume be placed on a back-end that supports compression. Example syntax: " +msgstr "" + +#: ./doc/config-reference/block-storage/drivers/ibm-storwize-svc-driver.xml:513(para) +msgid "capabilities:easytier_support - Similar semantics as the compression_support key, but for specifying according to support of the Easy Tier feature. Example syntax: " +msgstr "" + +#: ./doc/config-reference/block-storage/drivers/ibm-storwize-svc-driver.xml:521(para) +msgid "capabilities:storage_protocol - Specifies the connection protocol used to attach volumes of this type to instances. Legal values are iSCSI and FC. This extra specs value is used for both placement and setting the protocol used for this volume. In the example syntax, note <in> is used as opposed to <is> used in the previous examples. " +msgstr "" + +#: ./doc/config-reference/block-storage/drivers/ibm-storwize-svc-driver.xml:536(title) +msgid "Configure per-volume creation options" +msgstr "" + +#: ./doc/config-reference/block-storage/drivers/ibm-storwize-svc-driver.xml:537(para) +msgid "Volume types can also be used to pass options to the IBM Storwize/SVC driver, which over-ride the default values set in the configuration file. Contrary to the previous examples where the \"capabilities\" scope was used to pass parameters to the Cinder scheduler, options can be passed to the IBM Storwize/SVC driver with the \"drivers\" scope." +msgstr "" + +#: ./doc/config-reference/block-storage/drivers/ibm-storwize-svc-driver.xml:547(para) +msgid "rsize" +msgstr "" + +#: ./doc/config-reference/block-storage/drivers/ibm-storwize-svc-driver.xml:550(para) +msgid "warning" +msgstr "" + +#: ./doc/config-reference/block-storage/drivers/ibm-storwize-svc-driver.xml:553(para) +msgid "autoexpand" +msgstr "" + +#: ./doc/config-reference/block-storage/drivers/ibm-storwize-svc-driver.xml:556(para) +msgid "grainsize" +msgstr "" + +#: ./doc/config-reference/block-storage/drivers/ibm-storwize-svc-driver.xml:559(para) +msgid "compression" +msgstr "" + +#: ./doc/config-reference/block-storage/drivers/ibm-storwize-svc-driver.xml:562(para) +msgid "easytier" +msgstr "" + +#: ./doc/config-reference/block-storage/drivers/ibm-storwize-svc-driver.xml:565(para) +msgid "multipath" +msgstr "" + +#: ./doc/config-reference/block-storage/drivers/ibm-storwize-svc-driver.xml:568(para) +msgid "iogrp" +msgstr "" + +#: ./doc/config-reference/block-storage/drivers/ibm-storwize-svc-driver.xml:544(para) +msgid "The following extra specs keys are supported by the IBM Storwize/SVC driver: These keys have the same semantics as their counterparts in the configuration file. They are set similarly; for example, rsize=2 or compression=False." +msgstr "" + +#: ./doc/config-reference/block-storage/drivers/ibm-storwize-svc-driver.xml:576(title) +msgid "Example: Volume types" +msgstr "" + +#: ./doc/config-reference/block-storage/drivers/ibm-storwize-svc-driver.xml:577(para) +msgid "In the following example, we create a volume type to specify a controller that supports iSCSI and compression, to use iSCSI when attaching the volume, and to enable compression:" +msgstr "" + +#: ./doc/config-reference/block-storage/drivers/ibm-storwize-svc-driver.xml:583(para) +msgid "We can then create a 50GB volume using this type:" +msgstr "" + +#: ./doc/config-reference/block-storage/drivers/ibm-storwize-svc-driver.xml:587(para) +msgid "Volume types can be used, for example, to provide users with different" +msgstr "" + +#: ./doc/config-reference/block-storage/drivers/ibm-storwize-svc-driver.xml:591(para) +msgid "performance levels (such as, allocating entirely on an HDD tier, using Easy Tier for an HDD-SDD mix, or allocating entirely on an SSD tier)" +msgstr "" + +#: ./doc/config-reference/block-storage/drivers/ibm-storwize-svc-driver.xml:597(para) +msgid "resiliency levels (such as, allocating volumes in pools with different RAID levels)" +msgstr "" + +#: ./doc/config-reference/block-storage/drivers/ibm-storwize-svc-driver.xml:602(para) +msgid "features (such as, enabling/disabling Real-time Compression)" +msgstr "" + +#: ./doc/config-reference/block-storage/drivers/ibm-storwize-svc-driver.xml:609(title) +msgid "Operational notes for the Storwize family and SVC driver" +msgstr "" + +#: ./doc/config-reference/block-storage/drivers/ibm-storwize-svc-driver.xml:612(title) +msgid "Migrate volumes" +msgstr "" + +#: ./doc/config-reference/block-storage/drivers/ibm-storwize-svc-driver.xml:613(para) +msgid "In the context of OpenStack Block Storage's volume migration feature, the IBM Storwize/SVC driver enables the storage's virtualization technology. When migrating a volume from one pool to another, the volume will appear in the destination pool almost immediately, while the storage moves the data in the background." +msgstr "" + +#: ./doc/config-reference/block-storage/drivers/ibm-storwize-svc-driver.xml:621(para) +msgid "To enable this feature, both pools involved in a given volume migration must have the same values for extent_size. If the pools have different values for extent_size, the data will still be moved directly between the pools (not host-side copy), but the operation will be synchronous." +msgstr "" + +#: ./doc/config-reference/block-storage/drivers/ibm-storwize-svc-driver.xml:632(title) +msgid "Extend volumes" +msgstr "" + +#: ./doc/config-reference/block-storage/drivers/ibm-storwize-svc-driver.xml:633(para) +msgid "The IBM Storwize/SVC driver allows for extending a volume's size, but only for volumes without snapshots." +msgstr "" + +#: ./doc/config-reference/block-storage/drivers/ibm-storwize-svc-driver.xml:638(title) ./doc/config-reference/block-storage/drivers/ibm-gpfs-volume-driver.xml:173(title) +msgid "Snapshots and clones" +msgstr "" + +#: ./doc/config-reference/block-storage/drivers/ibm-storwize-svc-driver.xml:639(para) +msgid "Snapshots are implemented using FlashCopy with no background copy (space-efficient). Volume clones (volumes created from existing volumes) are implemented with FlashCopy, but with background copy enabled. This means that volume clones are independent, full copies. While this background copy is taking place, attempting to delete or extend the source volume will result in that operation waiting for the copy to complete." +msgstr "" + +#. When image changes, this message will be marked fuzzy or untranslated for you. +#. It doesn't matter what you translate it to: it's not used at all. +#: ./doc/config-reference/block-storage/drivers/xenapi-nfs.xml:62(None) +msgid "@@image: '../../../common/figures/xenapinfs/local_config.png'; md5=16a3864b0ec636518335246360438fd1" +msgstr "" + +#. When image changes, this message will be marked fuzzy or untranslated for you. +#. It doesn't matter what you translate it to: it's not used at all. +#: ./doc/config-reference/block-storage/drivers/xenapi-nfs.xml:78(None) +msgid "@@image: '../../../common/figures/xenapinfs/remote_config.png'; md5=eab22f6aa5413c2043936872ea44e459" +msgstr "" + +#: ./doc/config-reference/block-storage/drivers/xenapi-nfs.xml:4(title) +msgid "XenAPINFS" +msgstr "" + +#: ./doc/config-reference/block-storage/drivers/xenapi-nfs.xml:5(para) +msgid "XenAPINFS is a Block Storage (Cinder) driver that uses an NFS share through the XenAPI Storage Manager to store virtual disk images and expose those virtual disks as volumes." +msgstr "" + +#: ./doc/config-reference/block-storage/drivers/xenapi-nfs.xml:8(para) +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:17(para) +msgid "A XenServer/XCP installation that acts as Storage Controller. This hypervisor is known as the storage controller." +msgstr "" + +#: ./doc/config-reference/block-storage/drivers/xenapi-nfs.xml:22(para) +msgid "Use XenServer/XCP as your hypervisor for Compute nodes." +msgstr "" + +#: ./doc/config-reference/block-storage/drivers/xenapi-nfs.xml:26(para) +msgid "An NFS share that is configured for XenServer/XCP. For specific requirements and export options, see the administration guide for your specific XenServer version. The NFS share must be accessible by all XenServers components within your cloud." +msgstr "" + +#: ./doc/config-reference/block-storage/drivers/xenapi-nfs.xml:34(para) +msgid "To create volumes from XenServer type images (vhd tgz files), XenServer Nova plug-ins are also required on the storage controller." +msgstr "" + +#: ./doc/config-reference/block-storage/drivers/xenapi-nfs.xml:40(para) +msgid "You can use a XenServer as a storage controller and Compute node at the same time. This minimal configuration consists of a XenServer/XCP box and an NFS share." +msgstr "" + +#: ./doc/config-reference/block-storage/drivers/xenapi-nfs.xml:47(title) +msgid "Configuration patterns" +msgstr "" + +#: ./doc/config-reference/block-storage/drivers/xenapi-nfs.xml:50(para) +msgid "Local configuration (Recommended): The driver runs in a virtual machine on top of the storage controller. With this configuration, you can create volumes from qemu-img-supported formats." +msgstr "" + +#: ./doc/config-reference/block-storage/drivers/xenapi-nfs.xml:57(title) +msgid "Local configuration" +msgstr "" + +#: ./doc/config-reference/block-storage/drivers/xenapi-nfs.xml:68(para) +msgid "Remote configuration: The driver is not a guest VM of the storage controller. With this configuration, you can only use XenServer vhd-type images to create volumes." +msgstr "" + +#: ./doc/config-reference/block-storage/drivers/xenapi-nfs.xml:73(title) +msgid "Remote configuration" +msgstr "" + +#: ./doc/config-reference/block-storage/drivers/xenapi-nfs.xml:87(para) +msgid "Assuming the following setup:" +msgstr "" + +#: ./doc/config-reference/block-storage/drivers/xenapi-nfs.xml:90(para) +msgid "XenServer box at 10.2.2.1" +msgstr "" + +#: ./doc/config-reference/block-storage/drivers/xenapi-nfs.xml:94(para) +msgid "XenServer password is r00tme" +msgstr "" + +#: ./doc/config-reference/block-storage/drivers/xenapi-nfs.xml:98(para) +msgid "NFS server is nfs.example.com" +msgstr "" + +#: ./doc/config-reference/block-storage/drivers/xenapi-nfs.xml:102(para) +msgid "NFS export is at /volumes" +msgstr "" + +#: ./doc/config-reference/block-storage/drivers/xenapi-nfs.xml:106(para) +msgid "To use XenAPINFS as your cinder driver, set these configuration options in the cinder.conf file:" +msgstr "" + +#: ./doc/config-reference/block-storage/drivers/xenapi-nfs.xml:115(para) +msgid "The following table shows the configuration options that the XenAPINFS driver supports:" +msgstr "" + +#: ./doc/config-reference/block-storage/drivers/hds-volume-driver.xml:11(title) +msgid "HDS iSCSI volume driver" +msgstr "" + +#: ./doc/config-reference/block-storage/drivers/hds-volume-driver.xml:12(para) +msgid "This Cinder volume driver provides iSCSI support for HUS (Hitachi Unified Storage) arrays such as, HUS-110, HUS-130, and HUS-150." +msgstr "" + +#: ./doc/config-reference/block-storage/drivers/hds-volume-driver.xml:18(para) +msgid "Use the HDS command to communicate with an HUS array. You can download this utility package from the HDS support site (https://HDSSupport.hds.com." +msgstr "" + +#: ./doc/config-reference/block-storage/drivers/hds-volume-driver.xml:23(para) +msgid "Platform: Ubuntu 12.04LTS or newer." +msgstr "" + +#: ./doc/config-reference/block-storage/drivers/hds-volume-driver.xml:26(title) +msgid "Supported Cinder operations" +msgstr "" + +#: ./doc/config-reference/block-storage/drivers/hds-volume-driver.xml:27(para) +msgid "These operations are supported:" +msgstr "" + +#: ./doc/config-reference/block-storage/drivers/hds-volume-driver.xml:42(para) +msgid "Clone volume" +msgstr "" + +#: ./doc/config-reference/block-storage/drivers/hds-volume-driver.xml:45(para) +msgid "Extend volume" +msgstr "" + +#: ./doc/config-reference/block-storage/drivers/hds-volume-driver.xml:63(para) +msgid "get_volume_stats" +msgstr "" + +#: ./doc/config-reference/block-storage/drivers/hds-volume-driver.xml:66(para) +msgid "Thin provisioning, also known as Hitachi Dynamic Pool (HDP), is supported for volume or snapshot creation. Cinder volumes and snapshots do not have to reside in the same pool." +msgstr "" + +#: ./doc/config-reference/block-storage/drivers/hds-volume-driver.xml:78(para) +msgid "Do not confuse differentiated services with the Cinder volume service." +msgstr "" + +#: ./doc/config-reference/block-storage/drivers/hds-volume-driver.xml:73(para) +msgid "The HDS driver supports the concept of differentiated services, where volume type can be associated with the fine-tuned performance characteristics of HDP—the the dynamic pool where volumes shall be created. For instance, an HDP can consist of fast SSDs to provide speed. HDP can provide a certain reliability based on things like its RAID level characteristics. HDS driver maps volume type to the option in its configuration file." +msgstr "" + +#: ./doc/config-reference/block-storage/drivers/hds-volume-driver.xml:86(para) +msgid "Configuration is read from an XML-format file. Examples are shown for single and multi back-end cases." +msgstr "" + +#: ./doc/config-reference/block-storage/drivers/hds-volume-driver.xml:91(para) +msgid "Configuration is read from an XML file. This example shows the configuration for single back-end and for multi-back-end cases." +msgstr "" + +#: ./doc/config-reference/block-storage/drivers/hds-volume-driver.xml:100(para) +msgid "It is okay to manage multiple HUS arrays by using multiple Cinder instances (or servers)." +msgstr "" + +#: ./doc/config-reference/block-storage/drivers/hds-volume-driver.xml:96(para) +msgid "It is not recommended to manage a HUS array simultaneously from multiple Cinder instances or servers. " +msgstr "" + +#: ./doc/config-reference/block-storage/drivers/hds-volume-driver.xml:109(title) +msgid "Single back-end" +msgstr "" + +#: ./doc/config-reference/block-storage/drivers/hds-volume-driver.xml:110(para) +msgid "In a single back-end deployment, only one Cinder instance runs on the Cinder server and controls one HUS array: this setup requires these configuration files:" +msgstr "" + +#: ./doc/config-reference/block-storage/drivers/hds-volume-driver.xml:123(para) +msgid "The configuration file location is not fixed." +msgstr "" + +#: ./doc/config-reference/block-storage/drivers/hds-volume-driver.xml:116(para) +msgid "Set the option in the /etc/cinder/cinder.conf file to use the HDS volume driver. This option points to a configuration file." +msgstr "" + +#: ./doc/config-reference/block-storage/drivers/hds-volume-driver.xml:130(para) +msgid "Configure at the location specified previously. For example, /opt/hds/hus/cinder_hds_conf.xml:" +msgstr "" + +#: ./doc/config-reference/block-storage/drivers/hds-volume-driver.xml:160(title) +msgid "Multi back-end" +msgstr "" + +#: ./doc/config-reference/block-storage/drivers/hds-volume-driver.xml:161(para) +msgid "In a multi back-end deployment, more than one Cinder instance runs on the same server. In this example, two HUS arrays are used, possibly providing different storage performance:" +msgstr "" + +#: ./doc/config-reference/block-storage/drivers/hds-volume-driver.xml:167(para) +msgid "Configure /etc/cinder/cinder.conf: the hus1 configuration blocks are created. Set the option to point to an unique configuration file for each block. Set the option for each back-end to cinder.volume.drivers.hds.hds.HUSDriver" +msgstr "" + +#: ./doc/config-reference/block-storage/drivers/hds-volume-driver.xml:189(para) +msgid "Configure /opt/hds/hus/cinder_hus1_conf.xml:" +msgstr "" + +#: ./doc/config-reference/block-storage/drivers/hds-volume-driver.xml:214(para) +msgid "Configure the /opt/hds/hus/cinder_hus2_conf.xml file:" +msgstr "" + +#: ./doc/config-reference/block-storage/drivers/hds-volume-driver.xml:242(title) +msgid "Type extra specs: and volume type" +msgstr "" + +#: ./doc/config-reference/block-storage/drivers/hds-volume-driver.xml:244(para) +msgid "If you use volume types, you must configure them in the configuration file and set the option to the appropriate back-end. In the previous multi back-end example, the platinum volume type is served by hus-2, and the regular volume type is served by hus-1." +msgstr "" + +#: ./doc/config-reference/block-storage/drivers/hds-volume-driver.xml:255(title) +msgid "Non differentiated deployment of HUS arrays" +msgstr "" + +#: ./doc/config-reference/block-storage/drivers/hds-volume-driver.xml:256(para) +msgid "You can deploy multiple Cinder instances that each control a separate HUS array. Each instance has no volume type associated with it. The Cinder filtering algorithm selects the HUS array with the largest available free space. In each configuration file, you must define the default in the service labels." +msgstr "" + +#: ./doc/config-reference/block-storage/drivers/hds-volume-driver.xml:267(title) +msgid "HDS iSCSI volume driver configuration options" +msgstr "" + +#: ./doc/config-reference/block-storage/drivers/hds-volume-driver.xml:274(para) +msgid "There is no relative precedence or weight among these four labels." +msgstr "" + +#: ./doc/config-reference/block-storage/drivers/hds-volume-driver.xml:268(para) +msgid "These details apply to the XML format configuration file that is read by HDS volume driver. These differentiated service labels are predefined: svc_0, svc_1, svc_2, and svc_3. Each respective service label associates with these parameters and tags:" +msgstr "" + +#: ./doc/config-reference/block-storage/drivers/hds-volume-driver.xml:280(para) +msgid ": A create_volume call with a certain volume type shall be matched up with this tag. default is special in that any service associated with this type is used to create volume when no other labels match. Other labels are case sensitive and should exactly match. If no configured volume_types match the incoming requested type, an error occurs in volume creation." +msgstr "" + +#: ./doc/config-reference/block-storage/drivers/hds-volume-driver.xml:291(para) +msgid ", the pool ID associated with the service." +msgstr "" + +#: ./doc/config-reference/block-storage/drivers/hds-volume-driver.xml:295(para) +msgid "An iSCSI port dedicated to the service." +msgstr "" + +#: ./doc/config-reference/block-storage/drivers/hds-volume-driver.xml:304(para) +msgid "get_volume_stats() always provides the available capacity based on the combined sum of all the HDPs that are used in these services labels." +msgstr "" + +#: ./doc/config-reference/block-storage/drivers/hds-volume-driver.xml:298(para) +msgid "Typically a Cinder volume instance has only one such service label. For example, any svc_0, svc_1, svc_2, or svc_3 can be associated with it. But any mix of these service labels can be used in the same instance ." +msgstr "" + +#: ./doc/config-reference/block-storage/drivers/hds-volume-driver.xml:316(td) +msgid "Option" +msgstr "" + +#: ./doc/config-reference/block-storage/drivers/hds-volume-driver.xml:324(option) +msgid "mgmt_ip0" +msgstr "" + +#: ./doc/config-reference/block-storage/drivers/hds-volume-driver.xml:328(para) +msgid "Management Port 0 IP address" +msgstr "" + +#: ./doc/config-reference/block-storage/drivers/hds-volume-driver.xml:332(option) +msgid "mgmt_ip1" +msgstr "" + +#: ./doc/config-reference/block-storage/drivers/hds-volume-driver.xml:336(para) +msgid "Management Port 1 IP address" +msgstr "" + +#: ./doc/config-reference/block-storage/drivers/hds-volume-driver.xml:345(para) +msgid "Username is required only if secure mode is used" +msgstr "" + +#: ./doc/config-reference/block-storage/drivers/hds-volume-driver.xml:355(para) +msgid "Password is required only if secure mode is used" +msgstr "" + +#: ./doc/config-reference/block-storage/drivers/hds-volume-driver.xml:361(option) +msgid "svc_0, svc_1, svc_2, svc_3" +msgstr "" + +#: ./doc/config-reference/block-storage/drivers/hds-volume-driver.xml:365(para) +msgid "(at least one label has to be defined)" +msgstr "" + +#: ./doc/config-reference/block-storage/drivers/hds-volume-driver.xml:368(para) +msgid "Service labels: these four predefined names help four different sets of configuration options -- each can specify iSCSI port address, HDP and an unique volume type." +msgstr "" + +#: ./doc/config-reference/block-storage/drivers/hds-volume-driver.xml:377(option) +msgid "snapshot" +msgstr "" + +#: ./doc/config-reference/block-storage/drivers/hds-volume-driver.xml:382(para) +msgid "A service label which helps specify configuration for snapshots, such as, HDP." +msgstr "" + +#: ./doc/config-reference/block-storage/drivers/hds-volume-driver.xml:389(option) +msgid "volume_type" +msgstr "" + +#: ./doc/config-reference/block-storage/drivers/hds-volume-driver.xml:394(para) +msgid " tag is used to match volume type. Default meets any type of , or if it is not specified. Any other volume_type is selected if exactly matched during create_volume." +msgstr "" + +#: ./doc/config-reference/block-storage/drivers/hds-volume-driver.xml:406(option) +msgid "iscsi_ip" +msgstr "" + +#: ./doc/config-reference/block-storage/drivers/hds-volume-driver.xml:411(para) +msgid "iSCSI port IP address where volume attaches for this volume type." +msgstr "" + +#: ./doc/config-reference/block-storage/drivers/hds-volume-driver.xml:417(option) +msgid "hdp" +msgstr "" + +#: ./doc/config-reference/block-storage/drivers/hds-volume-driver.xml:422(para) +msgid "HDP, the pool number where volume, or snapshot should be created." +msgstr "" + +#: ./doc/config-reference/block-storage/drivers/hds-volume-driver.xml:428(option) +msgid "lun_start" +msgstr "" + +#: ./doc/config-reference/block-storage/drivers/hds-volume-driver.xml:433(para) +msgid "LUN allocation starts at this number." +msgstr "" + +#: ./doc/config-reference/block-storage/drivers/hds-volume-driver.xml:439(option) +msgid "lun_end" +msgstr "" + +#: ./doc/config-reference/block-storage/drivers/hds-volume-driver.xml:442(para) +msgid "4096" +msgstr "" + +#: ./doc/config-reference/block-storage/drivers/hds-volume-driver.xml:444(para) +msgid "LUN allocation is up to, but not including, this number." +msgstr "" + +#. When image changes, this message will be marked fuzzy or untranslated for you. +#. It doesn't matter what you translate it to: it's not used at all. +#: ./doc/config-reference/block-storage/drivers/ceph-rbd-volume-driver.xml:26(None) +msgid "@@image: '../../../common/figures/ceph/ceph-architecture.png'; md5=f7e854c9dbfb64534c47c3583e774c81" +msgstr "" + +#: ./doc/config-reference/block-storage/drivers/ceph-rbd-volume-driver.xml:4(title) +msgid "Ceph RADOS Block Device (RBD)" +msgstr "" + +#: ./doc/config-reference/block-storage/drivers/ceph-rbd-volume-driver.xml:5(para) +msgid "By Sebastien Han from " +msgstr "" + +#: ./doc/config-reference/block-storage/drivers/ceph-rbd-volume-driver.xml:8(para) +msgid "If you use KVM or QEMU as your hypervisor, you can configure the Compute service to use Ceph RADOS block devices (RBD) for volumes." +msgstr "" + +#: ./doc/config-reference/block-storage/drivers/ceph-rbd-volume-driver.xml:21(title) +msgid "Ceph architecture" +msgstr "" + +#: ./doc/config-reference/block-storage/drivers/ceph-rbd-volume-driver.xml:12(para) +msgid "Ceph is a massively scalable, open source, distributed storage system. It is comprised of an object store, block store, and a POSIX-compliant distributed file system. The platform can auto-scale to the exabyte level and beyond. It runs on commodity hardware, is self-healing and self-managing, and has no single point of failure. Ceph is in the Linux kernel and is integrated with the OpenStack cloud operating system. Due to its open source nature, you can install and use this portable storage platform in public or private clouds. " +msgstr "" + +#: ./doc/config-reference/block-storage/drivers/ceph-rbd-volume-driver.xml:32(title) +msgid "RADOS?" +msgstr "" + +#: ./doc/config-reference/block-storage/drivers/ceph-rbd-volume-driver.xml:33(para) +msgid "You can easily get confused by the naming: Ceph? RADOS?" +msgstr "" + +#: ./doc/config-reference/block-storage/drivers/ceph-rbd-volume-driver.xml:35(para) +msgid "RADOS: Reliable Autonomic Distributed Object Store is an object store. RADOS distributes objects across the storage cluster and replicates objects for fault tolerance. RADOS contains the following major components:" +msgstr "" + +#: ./doc/config-reference/block-storage/drivers/ceph-rbd-volume-driver.xml:42(para) +msgid "Object Storage Device (ODS). The storage daemon - RADOS service, the location of your data. You must run this daemon on each server in your cluster. For each OSD, you can have an associated hard drive disks. For performance purposes, pool your hard drive disk with raid arrays, logical volume management (LVM) or B-tree file system (Btrfs) pooling. By default, the following pools are created: data, metadata, and RBD." +msgstr "" + +#: ./doc/config-reference/block-storage/drivers/ceph-rbd-volume-driver.xml:54(para) +msgid "Meta-Data Server (MDS). Stores metadata. MDSs build a POSIX file system on top of objects for Ceph clients. However, if you do not use the Ceph file system, you do not need a metadata server." +msgstr "" + +#: ./doc/config-reference/block-storage/drivers/ceph-rbd-volume-driver.xml:61(para) +msgid "Monitor (MON). This lightweight daemon handles all communications with external applications and clients. It also provides a consensus for distributed decision making in a Ceph/RADOS cluster. For instance, when you mount a Ceph shared on a client, you point to the address of a MON server. It checks the state and the consistency of the data. In an ideal setup, you must run at least three ceph-mon daemons on separate servers." +msgstr "" + +#: ./doc/config-reference/block-storage/drivers/ceph-rbd-volume-driver.xml:74(para) +msgid "Ceph developers recommend that you use Btrfs as a file system for storage. XFS might be a better alternative for production environments. Neither Ceph nor Btrfs is ready for production and it could be risky to use them in combination. XFS is an excellent alternative to Btrfs. The ext4 file system is also compatible but does not exploit the power of Ceph." +msgstr "" + +#: ./doc/config-reference/block-storage/drivers/ceph-rbd-volume-driver.xml:82(para) +msgid "Currently, configure Ceph to use the XFS file system. Use Btrfs when it is stable enough for production." +msgstr "" + +#: ./doc/config-reference/block-storage/drivers/ceph-rbd-volume-driver.xml:86(para) +msgid "See ceph.com/docs/master/rec/file system/ for more information about usable file systems." +msgstr "" + +#: ./doc/config-reference/block-storage/drivers/ceph-rbd-volume-driver.xml:92(title) +msgid "Ways to store, use, and expose data" +msgstr "" + +#: ./doc/config-reference/block-storage/drivers/ceph-rbd-volume-driver.xml:93(para) +msgid "To store and access your data, you can use the following storage systems:" +msgstr "" + +#: ./doc/config-reference/block-storage/drivers/ceph-rbd-volume-driver.xml:97(para) +msgid "RADOS. Use as an object, default storage mechanism." +msgstr "" + +#: ./doc/config-reference/block-storage/drivers/ceph-rbd-volume-driver.xml:101(para) +msgid "RBD. Use as a block device. The Linux kernel RBD (rados block device) driver allows striping a Linux block device over multiple distributed object store data objects. It is compatible with the kvm RBD image." +msgstr "" + +#: ./doc/config-reference/block-storage/drivers/ceph-rbd-volume-driver.xml:108(para) +msgid "CephFS. Use as a file, POSIX-compliant file system." +msgstr "" + +#: ./doc/config-reference/block-storage/drivers/ceph-rbd-volume-driver.xml:112(para) +msgid "Ceph exposes its distributed object store (RADOS). You can access it through the following interfaces:" +msgstr "" + +#: ./doc/config-reference/block-storage/drivers/ceph-rbd-volume-driver.xml:116(para) +msgid "RADOS Gateway. Swift and Amazon-S3 compatible RESTful interface. See RADOS_Gateway for more information." +msgstr "" + +#: ./doc/config-reference/block-storage/drivers/ceph-rbd-volume-driver.xml:123(para) +msgid "librados, and the related C/C++ bindings." +msgstr "" + +#: ./doc/config-reference/block-storage/drivers/ceph-rbd-volume-driver.xml:127(para) +msgid "rbd and QEMU-RBD. Linux kernel and QEMU block devices that stripe data across multiple objects." +msgstr "" + +#: ./doc/config-reference/block-storage/drivers/ceph-rbd-volume-driver.xml:132(para) +msgid "For detailed installation instructions and benchmarking information, see http://www.sebastien-han.fr/blog/2012/06/10/introducing-ceph-to-openstack/." +msgstr "" + +#: ./doc/config-reference/block-storage/drivers/ceph-rbd-volume-driver.xml:138(title) +msgid "Driver options" +msgstr "" + +#: ./doc/config-reference/block-storage/drivers/ceph-rbd-volume-driver.xml:139(para) +msgid "The following table contains the configuration options supported by the Ceph RADOS Block Device driver." +msgstr "" + +#: ./doc/config-reference/block-storage/drivers/hp-lefthand-driver.xml:4(title) +msgid "HP / LeftHand SAN" +msgstr "" + +#: ./doc/config-reference/block-storage/drivers/hp-lefthand-driver.xml:5(para) +msgid "HP/LeftHand SANs are optimized for virtualized environments with VMware ESX & Microsoft Hyper-V, though the OpenStack integration provides additional support to various other virtualized environments, such as Xen, KVM, and OpenVZ, by exposing the volumes through ISCSI to connect to the instances." +msgstr "" + +#: ./doc/config-reference/block-storage/drivers/hp-lefthand-driver.xml:11(para) +msgid "The HpSanISCSIDriver enables you to use a HP/Lefthand SAN that supports the Cliq interface. Every supported volume operation translates into a cliq call in the back-end." +msgstr "" + +#: ./doc/config-reference/block-storage/drivers/hp-lefthand-driver.xml:14(para) +msgid "To use Cinder with HP/Lefthand SAN, you must set the following parameters in the cinder.conf file:" +msgstr "" + +#: ./doc/config-reference/block-storage/drivers/hp-lefthand-driver.xml:19(para) +msgid "Set volume_driver=cinder.volume.drivers.san.HpSanISCSIDriver." +msgstr "" + +#: ./doc/config-reference/block-storage/drivers/hp-lefthand-driver.xml:23(para) +msgid "Set san_ip flag to the hostname or VIP of your Virtual Storage Appliance (VSA)." +msgstr "" + +#: ./doc/config-reference/block-storage/drivers/hp-lefthand-driver.xml:28(para) +msgid "Set san_login and san_password to the user name and password of the ssh user with all necessary privileges on the appliance." +msgstr "" + +#: ./doc/config-reference/block-storage/drivers/hp-lefthand-driver.xml:34(para) +msgid "Set san_ssh_port=16022. The default is 22. However, the default for the VSA is usually 16022." +msgstr "" + +#: ./doc/config-reference/block-storage/drivers/hp-lefthand-driver.xml:39(para) +msgid "Set san_clustername to the name of the cluster where the associated volumes are created." +msgstr "" + +#: ./doc/config-reference/block-storage/drivers/hp-lefthand-driver.xml:44(para) +msgid "The following optional parameters have the following default values:" +msgstr "" + +#: ./doc/config-reference/block-storage/drivers/hp-lefthand-driver.xml:48(para) +msgid "san_thin_provision=True. To disable thin provisioning, set to False." +msgstr "" + +#: ./doc/config-reference/block-storage/drivers/hp-lefthand-driver.xml:53(para) +msgid "san_is_local=False. Typically, this parameter is set to False for this driver. To configure the cliq commands to run locally instead of over ssh, set this parameter to True." +msgstr "" + +#: ./doc/config-reference/block-storage/drivers/hp-lefthand-driver.xml:60(para) +msgid "In addition to configuring the cinder-volume service, you must configure the VSA to function in an OpenStack environment." +msgstr "" + +#: ./doc/config-reference/block-storage/drivers/hp-lefthand-driver.xml:64(title) +msgid "To configure the VSA" +msgstr "" + +#: ./doc/config-reference/block-storage/drivers/hp-lefthand-driver.xml:66(para) +msgid "Configure Chap on each of the nova-compute nodes." +msgstr "" + +#: ./doc/config-reference/block-storage/drivers/hp-lefthand-driver.xml:71(para) +msgid "Add Server associations on the VSA with the associated Chap and initiator information. The name should correspond to the 'hostname' of the nova-compute node. For Xen, this is the hypervisor host name. To do this, use either Cliq or the Centralized Management Console." +msgstr "" + +#: ./doc/config-reference/block-storage/drivers/windows-volume-driver.xml:6(title) +msgid "Windows" +msgstr "" + +#: ./doc/config-reference/block-storage/drivers/windows-volume-driver.xml:7(para) +msgid "There is a volume back-end for Windows. Set the following in your cinder.conf, and use the options below to configure it." +msgstr "" + +#: ./doc/config-reference/block-storage/drivers/lvm-volume-driver.xml:6(title) +msgid "LVM" +msgstr "" + +#: ./doc/config-reference/block-storage/drivers/lvm-volume-driver.xml:7(para) +msgid "The default volume back-end uses local volumes managed by LVM." +msgstr "" + +#: ./doc/config-reference/block-storage/drivers/lvm-volume-driver.xml:8(para) +msgid "This driver supports different transport protocols to attach volumes, currently ISCSI and ISER." +msgstr "" + +#: ./doc/config-reference/block-storage/drivers/lvm-volume-driver.xml:10(para) +msgid "Set the following in your cinder.conf, and use the following options to configure for ISCSI transport:" +msgstr "" + +#: ./doc/config-reference/block-storage/drivers/lvm-volume-driver.xml:16(para) +msgid "and for the ISER transport:" +msgstr "" + +#: ./doc/config-reference/block-storage/drivers/nfs-volume-driver.xml:4(title) +msgid "NFS driver" +msgstr "" + +#: ./doc/config-reference/block-storage/drivers/nfs-volume-driver.xml:5(para) +msgid "The Network File System (NFS) is a distributed file system protocol originally developed by Sun Microsystems in 1984. An NFS server exports one or more of its file systems, known as shares. An NFS client can mount these exported shares on its own file system. You can perform file actions on this mounted remote file system as if the file system were local." +msgstr "" + +#: ./doc/config-reference/block-storage/drivers/nfs-volume-driver.xml:13(title) +msgid "How the NFS driver works" +msgstr "" + +#: ./doc/config-reference/block-storage/drivers/nfs-volume-driver.xml:14(para) +msgid "The NFS driver, and other drivers based off of it, work quite differently than a traditional block storage driver." +msgstr "" + +#: ./doc/config-reference/block-storage/drivers/nfs-volume-driver.xml:17(para) +msgid "The NFS driver does not actually allow an instance to access a storage device at the block level. Instead, files are created on an NFS share and mapped to instances, which emulates a block device. This works in a similar way to QEMU, which stores instances in the /var/lib/nova/instances directory." +msgstr "" + +#: ./doc/config-reference/block-storage/drivers/nfs-volume-driver.xml:26(title) +msgid "Enable the NFS driver and related options" +msgstr "" + +#: ./doc/config-reference/block-storage/drivers/nfs-volume-driver.xml:27(para) +msgid "To use Cinder with the NFS driver, first set the volume_driver in cinder.conf:" +msgstr "" + +#: ./doc/config-reference/block-storage/drivers/nfs-volume-driver.xml:31(para) +msgid "The following table contains the options supported by the NFS driver." +msgstr "" + +#: ./doc/config-reference/block-storage/drivers/nfs-volume-driver.xml:37(title) +msgid "How to use the NFS driver" +msgstr "" + +#: ./doc/config-reference/block-storage/drivers/nfs-volume-driver.xml:40(para) +msgid "Access to one or more NFS servers. Creating an NFS server is outside the scope of this document. This example assumes access to the following NFS servers and mount points:" +msgstr "" + +#: ./doc/config-reference/block-storage/drivers/nfs-volume-driver.xml:46(literal) +msgid "192.168.1.200:/storage" +msgstr "" + +#: ./doc/config-reference/block-storage/drivers/nfs-volume-driver.xml:49(literal) +msgid "192.168.1.201:/storage" +msgstr "" + +#: ./doc/config-reference/block-storage/drivers/nfs-volume-driver.xml:52(literal) +msgid "192.168.1.202:/storage" +msgstr "" + +#: ./doc/config-reference/block-storage/drivers/nfs-volume-driver.xml:55(para) +msgid "This example demonstrates the use of with this driver with multiple NFS servers. Multiple servers are not required. One is usually enough." +msgstr "" + +#: ./doc/config-reference/block-storage/drivers/nfs-volume-driver.xml:60(para) +msgid "Add your list of NFS servers to the file you specified with the nfs_shares_config option. For example, if the value of this option was set to /etc/cinder/shares.txt, then:" +msgstr "" + +#: ./doc/config-reference/block-storage/drivers/nfs-volume-driver.xml:70(para) +msgid "Comments are allowed in this file. They begin with a #." +msgstr "" + +#: ./doc/config-reference/block-storage/drivers/nfs-volume-driver.xml:74(para) +msgid "Configure the nfs_mount_point_base option. This is a directory where cinder-volume mounts all NFS shares stored in shares.txt. For this example, /var/lib/cinder/nfs is used. You can, of course, use the default value of $state_path/mnt." +msgstr "" + +#: ./doc/config-reference/block-storage/drivers/nfs-volume-driver.xml:85(para) +msgid "Start the cinder-volume service. /var/lib/cinder/nfs should now contain a directory for each NFS share specified in shares.txt. The name of each directory is a hashed name:" +msgstr "" + +#: ./doc/config-reference/block-storage/drivers/nfs-volume-driver.xml:97(para) +msgid "You can now create volumes as you normally would:" +msgstr "" + +#: ./doc/config-reference/block-storage/drivers/nfs-volume-driver.xml:102(para) +msgid "This volume can also be attached and deleted just like other volumes. However, snapshotting is not supported." +msgstr "" + +#: ./doc/config-reference/block-storage/drivers/nfs-volume-driver.xml:109(title) +msgid "NFS driver notes" +msgstr "" + +#: ./doc/config-reference/block-storage/drivers/nfs-volume-driver.xml:112(para) +msgid "cinder-volume manages the mounting of the NFS shares as well as volume creation on the shares. Keep this in mind when planning your OpenStack architecture. If you have one master NFS server, it might make sense to only have one cinder-volume service to handle all requests to that NFS server. However, if that single server is unable to handle all requests, more than one cinder-volume service is needed as well as potentially more than one NFS server." +msgstr "" + +#: ./doc/config-reference/block-storage/drivers/nfs-volume-driver.xml:128(para) +msgid "Because data is stored in a file and not actually on a block storage device, you might not see the same IO performance as you would with a traditional block storage driver. Please test accordingly." +msgstr "" + +#: ./doc/config-reference/block-storage/drivers/nfs-volume-driver.xml:135(para) +msgid "Despite possible IO performance loss, having volume data stored in a file might be beneficial. For example, backing up volumes can be as easy as copying the volume files." +msgstr "" + +#: ./doc/config-reference/block-storage/drivers/nfs-volume-driver.xml:140(para) +msgid "Regular IO flushing and syncing still stands." +msgstr "" + +#: ./doc/config-reference/block-storage/drivers/ibm-gpfs-volume-driver.xml:4(title) +msgid "IBM GPFS volume driver" +msgstr "" + +#: ./doc/config-reference/block-storage/drivers/ibm-gpfs-volume-driver.xml:5(para) +msgid "IBM General Parallel File System (GPFS) is a cluster file system that provides concurrent access to file systems from multiple nodes. The storage provided by these nodes can be direct attached, network attached, SAN attached, or a combination of these methods. GPFS provides many features beyond common data access, including data replication, policy based storage management, and space efficient file snapshot and clone operations." +msgstr "" + +#: ./doc/config-reference/block-storage/drivers/ibm-gpfs-volume-driver.xml:14(title) +msgid "How the GPFS driver works" +msgstr "" + +#: ./doc/config-reference/block-storage/drivers/ibm-gpfs-volume-driver.xml:15(para) +msgid "The GPFS driver enables the use of GPFS in a fashion similar to that of the NFS driver. With the GPFS driver, instances do not actually access a storage device at the block level. Instead, volume backing files are created in a GPFS file system and mapped to instances, which emulate a block device." +msgstr "" + +#: ./doc/config-reference/block-storage/drivers/ibm-gpfs-volume-driver.xml:23(para) +msgid "GPFS software must be installed and running on nodes where Block Storage and Compute services run in the OpenStack environment. A GPFS file system must also be created and mounted on these nodes before starting the cinder-volume service. The details of these GPFS specific steps are covered in GPFS: Concepts, Planning, and Installation Guide and GPFS: Administration and Programming Reference." +msgstr "" + +#: ./doc/config-reference/block-storage/drivers/ibm-gpfs-volume-driver.xml:35(para) +msgid "Optionally, the Image Service can be configured to store images on a GPFS file system. When a Block Storage volume is created from an image, if both image data and volume data reside in the same GPFS file system, the data from image file is moved efficiently to the volume file using copy-on-write optimization strategy." +msgstr "" + +#: ./doc/config-reference/block-storage/drivers/ibm-gpfs-volume-driver.xml:43(title) +msgid "Enable the GPFS driver" +msgstr "" + +#: ./doc/config-reference/block-storage/drivers/ibm-gpfs-volume-driver.xml:44(para) +msgid "To use the Block Storage Service with the GPFS driver, first set the volume_driver in cinder.conf:" +msgstr "" + +#: ./doc/config-reference/block-storage/drivers/ibm-gpfs-volume-driver.xml:48(para) +msgid "The following table contains the configuration options supported by the GPFS driver." +msgstr "" + +#: ./doc/config-reference/block-storage/drivers/ibm-gpfs-volume-driver.xml:53(para) +msgid "The gpfs_images_share_mode flag is only valid if the Image Service is configured to use GPFS with the gpfs_images_dir flag. When the value of this flag is copy_on_write, the paths specified by the gpfs_mount_point_base and gpfs_images_dir flags must both reside in the same GPFS file system and in the same GPFS file set." +msgstr "" + +#: ./doc/config-reference/block-storage/drivers/ibm-gpfs-volume-driver.xml:66(title) +msgid "Volume creation options" +msgstr "" + +#: ./doc/config-reference/block-storage/drivers/ibm-gpfs-volume-driver.xml:67(para) +msgid "It is possible to specify additional volume configuration options on a per-volume basis by specifying volume metadata. The volume is created using the specified options. Changing the metadata after the volume is created has no effect. The following table lists the volume creation options supported by the GPFS volume driver." +msgstr "" + +#: ./doc/config-reference/block-storage/drivers/ibm-gpfs-volume-driver.xml:75(caption) +msgid "Volume Create Options for GPFS Volume Drive" +msgstr "" + +#: ./doc/config-reference/block-storage/drivers/ibm-gpfs-volume-driver.xml:79(th) +msgid "Metadata Item Name" +msgstr "" + +#: ./doc/config-reference/block-storage/drivers/ibm-gpfs-volume-driver.xml:85(literal) ./doc/config-reference/block-storage/drivers/ibm-gpfs-volume-driver.xml:98(literal) ./doc/config-reference/block-storage/drivers/ibm-gpfs-volume-driver.xml:99(literal) +msgid "fstype" +msgstr "" + +#: ./doc/config-reference/block-storage/drivers/ibm-gpfs-volume-driver.xml:88(literal) +msgid "fstype=swap" +msgstr "" + +#: ./doc/config-reference/block-storage/drivers/ibm-gpfs-volume-driver.xml:86(td) +msgid "Specifies whether to create a file system or a swap area on the new volume. If is specified, the mkswap command is used to create a swap area. Otherwise the mkfs command is passed the specified file system type, for example ext3, ext4 or ntfs." +msgstr "" + +#: ./doc/config-reference/block-storage/drivers/ibm-gpfs-volume-driver.xml:96(literal) +msgid "fslabel" +msgstr "" + +#: ./doc/config-reference/block-storage/drivers/ibm-gpfs-volume-driver.xml:97(td) +msgid "Sets the file system label for the file system specified by option. This value is only used if is specified." +msgstr "" + +#: ./doc/config-reference/block-storage/drivers/ibm-gpfs-volume-driver.xml:103(literal) +msgid "data_pool_name" +msgstr "" + +#: ./doc/config-reference/block-storage/drivers/ibm-gpfs-volume-driver.xml:105(para) +msgid "Specifies the GPFS storage pool to which the volume is to be assigned. Note: The GPFS storage pool must already have been created." +msgstr "" + +#: ./doc/config-reference/block-storage/drivers/ibm-gpfs-volume-driver.xml:111(literal) +msgid "replicas" +msgstr "" + +#: ./doc/config-reference/block-storage/drivers/ibm-gpfs-volume-driver.xml:113(para) +msgid "Specifies how many copies of the volume file to create. Valid values are 1, 2, and, for GPFS V3.5.0.7 and later, 3. This value cannot be greater than the value of the MaxDataReplicas attribute of the file system." +msgstr "" + +#: ./doc/config-reference/block-storage/drivers/ibm-gpfs-volume-driver.xml:122(literal) +msgid "dio" +msgstr "" + +#: ./doc/config-reference/block-storage/drivers/ibm-gpfs-volume-driver.xml:124(para) +msgid "Enables or disables the Direct I/O caching policy for the volume file. Valid values are yes and no." +msgstr "" + +#: ./doc/config-reference/block-storage/drivers/ibm-gpfs-volume-driver.xml:130(literal) +msgid "write_affinity_depth" +msgstr "" + +#: ./doc/config-reference/block-storage/drivers/ibm-gpfs-volume-driver.xml:132(para) +msgid "Specifies the allocation policy to be used for the volume file. Note: This option only works if allow-write-affinity is set for the GPFS data pool." +msgstr "" + +#: ./doc/config-reference/block-storage/drivers/ibm-gpfs-volume-driver.xml:139(literal) +msgid "block_group_factor" +msgstr "" + +#: ./doc/config-reference/block-storage/drivers/ibm-gpfs-volume-driver.xml:141(para) +msgid "Specifies how many blocks are laid out sequentially in the volume file to behave as a single large block. Note: This option only works if allow-write-affinity is set for the GPFS data pool." +msgstr "" + +#: ./doc/config-reference/block-storage/drivers/ibm-gpfs-volume-driver.xml:149(literal) +msgid "write_affinity_failure_group" +msgstr "" + +#: ./doc/config-reference/block-storage/drivers/ibm-gpfs-volume-driver.xml:151(para) +msgid "Specifies the range of nodes (in GPFS shared nothing architecture) where replicas of blocks in the volume file are to be written. See GPFS: Administration and Programming Reference for more details on this option." +msgstr "" + +#: ./doc/config-reference/block-storage/drivers/ibm-gpfs-volume-driver.xml:162(title) +msgid "Example: Volume creation options" +msgstr "" + +#: ./doc/config-reference/block-storage/drivers/ibm-gpfs-volume-driver.xml:163(para) +msgid "This example shows the creation of a 50GB volume with an ext4 file system labeled newfsand direct IO enabled:" +msgstr "" + +#: ./doc/config-reference/block-storage/drivers/ibm-gpfs-volume-driver.xml:171(title) +msgid "Operational notes for GPFS driver" +msgstr "" + +#: ./doc/config-reference/block-storage/drivers/ibm-gpfs-volume-driver.xml:174(para) +msgid "Volume snapshots are implemented using the GPFS file clone feature. Whenever a new snapshot is created, the snapshot file is efficiently created as a read-only clone parent of the volume, and the volume file uses copy-on-write optimization strategy to minimize data movement." +msgstr "" + +#: ./doc/config-reference/block-storage/drivers/ibm-gpfs-volume-driver.xml:180(para) +msgid "Similarly when a new volume is created from a snapshot or from an existing volume, the same approach is taken. The same approach is also used when a new volume is created from a Glance image, if the source image is in raw format, and gpfs_images_share_mode is set to copy_on_write." +msgstr "" + +#: ./doc/config-reference/block-storage/backup/tsm-backup-driver.xml:6(title) +msgid "IBM Tivoli Storage Manager backup driver" +msgstr "" + +#: ./doc/config-reference/block-storage/backup/tsm-backup-driver.xml:7(para) +msgid "The IBM Tivoli Storage Manager (TSM) backup driver enables performing volume backups to a TSM server." +msgstr "" + +#: ./doc/config-reference/block-storage/backup/tsm-backup-driver.xml:10(para) +msgid "The TSM client should be installed and configured on the machine running the cinder-backup service. See the IBM Tivoli Storage Manager Backup-Archive Client Installation and User's Guide for details on installing the TSM client." +msgstr "" + +#: ./doc/config-reference/block-storage/backup/tsm-backup-driver.xml:17(para) +msgid "To enable the IBM TSM backup driver, include the following option in cinder.conf:" +msgstr "" + +#: ./doc/config-reference/block-storage/backup/tsm-backup-driver.xml:20(para) +msgid "The following configuration options are available for the TSM backup driver." +msgstr "" + +#: ./doc/config-reference/block-storage/backup/tsm-backup-driver.xml:23(para) +msgid "This example shows the default options for the TSM backup driver." +msgstr "" + +#: ./doc/config-reference/block-storage/backup/ceph-backup-driver.xml:11(title) +msgid "Ceph backup driver" +msgstr "" + +#: ./doc/config-reference/block-storage/backup/ceph-backup-driver.xml:12(para) +msgid "The Ceph backup driver backs up volumes of any type to a Ceph back-end store. The driver can also detect whether the volume to be backed up is a Ceph RBD volume, and if so, it tries to perform incremental and differential backups." +msgstr "" + +#: ./doc/config-reference/block-storage/backup/ceph-backup-driver.xml:17(para) +msgid "For source Ceph RBD volumes, you can perform backups within the same Ceph pool (not recommended) and backups between different Ceph pools and between different Ceph clusters." +msgstr "" + +#: ./doc/config-reference/block-storage/backup/ceph-backup-driver.xml:21(para) +msgid "At the time of writing, differential backup support in Ceph/librbd was quite new. This driver attempts a differential backup in the first instance. If the differential backup fails, the driver falls back to full backup/copy." +msgstr "" + +#: ./doc/config-reference/block-storage/backup/ceph-backup-driver.xml:26(para) +msgid "If incremental backups are used, multiple backups of the same volume are stored as snapshots so that minimal space is consumed in the backup store. It takes far less time to restore a volume than to take a full copy." +msgstr "" + +#: ./doc/config-reference/block-storage/backup/ceph-backup-driver.xml:32(para) +msgid "Block Storage Service enables you to:" +msgstr "" + +#: ./doc/config-reference/block-storage/backup/ceph-backup-driver.xml:35(para) +msgid "Restore to a new volume, which is the default and recommended action." +msgstr "" + +#: ./doc/config-reference/block-storage/backup/ceph-backup-driver.xml:40(para) +msgid "Restore to the original volume from which the backup was taken. The restore action takes a full copy because this is the safest action." +msgstr "" + +#: ./doc/config-reference/block-storage/backup/ceph-backup-driver.xml:48(para) +msgid "To enable the Ceph backup driver, include the following option in the cinder.conf file:" +msgstr "" + +#: ./doc/config-reference/block-storage/backup/ceph-backup-driver.xml:52(para) +msgid "The following configuration options are available for the Ceph backup driver." +msgstr "" + +#: ./doc/config-reference/block-storage/backup/ceph-backup-driver.xml:56(para) +msgid "This example shows the default options for the Ceph backup driver." +msgstr "" + +#: ./doc/config-reference/block-storage/backup/swift-backup-driver.xml:5(title) +msgid "Swift backup driver" +msgstr "" + +#: ./doc/config-reference/block-storage/backup/swift-backup-driver.xml:6(para) +msgid "The backup driver for Swift back-end performs a volume backup to a Swift object storage system." +msgstr "" + +#: ./doc/config-reference/block-storage/backup/swift-backup-driver.xml:8(para) +msgid "To enable the Swift backup driver, include the following option in the cinder.conf file:" +msgstr "" + +#: ./doc/config-reference/block-storage/backup/swift-backup-driver.xml:12(para) +msgid "The following configuration options are available for the Swift back-end backup driver." +msgstr "" + +#: ./doc/config-reference/block-storage/backup/swift-backup-driver.xml:16(para) +msgid "This example shows the default options for the Swift back-end backup driver." +msgstr "" + +#: ./doc/config-reference/image/section_glance-property-protection.xml:6(title) +msgid "Image property protection" +msgstr "" + +#: ./doc/config-reference/image/section_glance-property-protection.xml:7(para) +msgid "There are currently two types of properties in the Image Service: \"core properties,\" which are defined by the system, and \"additional properties,\" which are arbitrary key/value pairs that can be set on an image." +msgstr "" + +#: ./doc/config-reference/image/section_glance-property-protection.xml:11(para) +msgid "With the Havana release, any such property can be protected through configuration. When you put protections on a property, it limits the users who can perform CRUD operations on the property based on their user role. The use case is to enable the cloud provider to maintain extra properties on images so typically this would be an administrator who has access to protected properties, managed with policy.json. The extra property could be licensing information or billing information, for example." +msgstr "" + +#: ./doc/config-reference/image/section_glance-property-protection.xml:20(para) +msgid "Properties that don't have protections defined for them will act as they do now: the administrator can control core properties, with the image owner having control over additional properties." +msgstr "" + +#: ./doc/config-reference/image/section_glance-property-protection.xml:23(para) +msgid "Property protection can be set in /etc/glance/property-protections.conf, using roles found in policy.json." +msgstr "" + +#: ./doc/config-reference/object-storage/section_object-storage-listendpoints.xml:6(title) +msgid "Endpoint listing middleware" +msgstr "" + +#: ./doc/config-reference/object-storage/section_object-storage-listendpoints.xml:7(para) +msgid "The endpoint listing middleware enables third-party services that use data locality information to integrate with swift. This middleware reduces network overhead and is designed for third-party services that run inside the firewall. Deploy this middleware on a proxy server because usage of this middleware is not authenticated." +msgstr "" + +#: ./doc/config-reference/object-storage/section_object-storage-listendpoints.xml:13(para) +msgid "Format requests for endpoints, as follows:" +msgstr "" + +#: ./doc/config-reference/object-storage/section_object-storage-listendpoints.xml:14(replaceable) ./doc/config-reference/object-storage/section_object-storage-listendpoints.xml:15(replaceable) ./doc/config-reference/object-storage/section_object-storage-listendpoints.xml:16(replaceable) +msgid "{account}" +msgstr "" + +#: ./doc/config-reference/object-storage/section_object-storage-listendpoints.xml:14(replaceable) ./doc/config-reference/object-storage/section_object-storage-listendpoints.xml:15(replaceable) +msgid "{container}" +msgstr "" + +#: ./doc/config-reference/object-storage/section_object-storage-listendpoints.xml:14(replaceable) +msgid "{object}" +msgstr "" + +#: ./doc/config-reference/object-storage/section_object-storage-listendpoints.xml:17(para) +msgid "Use the configuration option in the proxy_server.conf file to customize the /endpoints/ path." +msgstr "" + +#: ./doc/config-reference/object-storage/section_object-storage-listendpoints.xml:20(para) +msgid "Responses are JSON-encoded lists of endpoints, as follows:" +msgstr "" + +#: ./doc/config-reference/object-storage/section_object-storage-listendpoints.xml:22(replaceable) ./doc/config-reference/object-storage/section_object-storage-listendpoints.xml:23(replaceable) ./doc/config-reference/object-storage/section_object-storage-listendpoints.xml:24(replaceable) +msgid "{server}" +msgstr "" + +#: ./doc/config-reference/object-storage/section_object-storage-listendpoints.xml:22(replaceable) ./doc/config-reference/object-storage/section_object-storage-listendpoints.xml:23(replaceable) ./doc/config-reference/object-storage/section_object-storage-listendpoints.xml:24(replaceable) +msgid "{port}" +msgstr "" + +#: ./doc/config-reference/object-storage/section_object-storage-listendpoints.xml:22(replaceable) ./doc/config-reference/object-storage/section_object-storage-listendpoints.xml:23(replaceable) ./doc/config-reference/object-storage/section_object-storage-listendpoints.xml:24(replaceable) +msgid "{dev}" +msgstr "" + +#: ./doc/config-reference/object-storage/section_object-storage-listendpoints.xml:22(replaceable) ./doc/config-reference/object-storage/section_object-storage-listendpoints.xml:23(replaceable) ./doc/config-reference/object-storage/section_object-storage-listendpoints.xml:24(replaceable) +msgid "{part}" +msgstr "" + +#: ./doc/config-reference/object-storage/section_object-storage-listendpoints.xml:22(replaceable) ./doc/config-reference/object-storage/section_object-storage-listendpoints.xml:23(replaceable) ./doc/config-reference/object-storage/section_object-storage-listendpoints.xml:24(replaceable) +msgid "{acc}" +msgstr "" + +#: ./doc/config-reference/object-storage/section_object-storage-listendpoints.xml:22(replaceable) ./doc/config-reference/object-storage/section_object-storage-listendpoints.xml:23(replaceable) +msgid "{cont}" +msgstr "" + +#: ./doc/config-reference/object-storage/section_object-storage-listendpoints.xml:22(replaceable) +msgid "{obj}" +msgstr "" + +#: ./doc/config-reference/object-storage/section_object-storage-listendpoints.xml:25(para) +msgid "An example response is:" +msgstr "" + +#: ./doc/config-reference/object-storage/section_configure_s3.xml:6(title) +msgid "Configure Object Storage with the S3 API" +msgstr "" + +#: ./doc/config-reference/object-storage/section_configure_s3.xml:7(para) +msgid "The Swift3 middleware emulates the S3 REST API on top of Object Storage." +msgstr "" + +#: ./doc/config-reference/object-storage/section_configure_s3.xml:9(para) +msgid "The following operations are currently supported:" +msgstr "" + +#: ./doc/config-reference/object-storage/section_configure_s3.xml:12(para) +msgid "GET Service" +msgstr "" + +#: ./doc/config-reference/object-storage/section_configure_s3.xml:15(para) +msgid "DELETE Bucket" +msgstr "" + +#: ./doc/config-reference/object-storage/section_configure_s3.xml:18(para) +msgid "GET Bucket (List Objects)" +msgstr "" + +#: ./doc/config-reference/object-storage/section_configure_s3.xml:21(para) +msgid "PUT Bucket" +msgstr "" + +#: ./doc/config-reference/object-storage/section_configure_s3.xml:24(para) +msgid "DELETE Object" +msgstr "" + +#: ./doc/config-reference/object-storage/section_configure_s3.xml:27(para) +msgid "GET Object" +msgstr "" + +#: ./doc/config-reference/object-storage/section_configure_s3.xml:30(para) +msgid "HEAD Object" +msgstr "" + +#: ./doc/config-reference/object-storage/section_configure_s3.xml:33(para) +msgid "PUT Object" +msgstr "" + +#: ./doc/config-reference/object-storage/section_configure_s3.xml:36(para) +msgid "PUT Object (Copy)" +msgstr "" + +#: ./doc/config-reference/object-storage/section_configure_s3.xml:39(para) +msgid "To use this middleware, first download the latest version from its repository to your proxy server(s)." +msgstr "" + +#: ./doc/config-reference/object-storage/section_configure_s3.xml:43(para) +msgid "Optional: To use this middleware with Swift 1.7.0 and previous versions, you must use the v1.7 tag of the fujita/swift3 repository. Clone the repository, as shown previously, and run this command:" +msgstr "" + +#: ./doc/config-reference/object-storage/section_configure_s3.xml:48(para) +msgid "Then, install it using standard python mechanisms, such as:" +msgstr "" + +#: ./doc/config-reference/object-storage/section_configure_s3.xml:51(para) +msgid "Alternatively, if you have configured the Ubuntu Cloud Archive, you may use: " +msgstr "" + +#: ./doc/config-reference/object-storage/section_configure_s3.xml:54(para) +msgid "To add this middleware to your configuration, add the swift3 middleware in front of the auth middleware, and before any other middleware that look at swift requests (like rate limiting)." +msgstr "" + +#: ./doc/config-reference/object-storage/section_configure_s3.xml:58(para) +msgid "Ensure that your proxy-server.conf file contains swift3 in the pipeline and the [filter:swift3] section, as shown below:" +msgstr "" + +#: ./doc/config-reference/object-storage/section_configure_s3.xml:68(para) +msgid "Next, configure the tool that you use to connect to the S3 API. For S3curl, for example, you must add your host IP information by adding your host IP to the @endpoints array (line 33 in s3curl.pl):" +msgstr "" + +#: ./doc/config-reference/object-storage/section_configure_s3.xml:73(para) +msgid "Now you can send commands to the endpoint, such as:" +msgstr "" + +#: ./doc/config-reference/object-storage/section_configure_s3.xml:77(para) +msgid "To set up your client, the access key will be the concatenation of the account and user strings that should look like test:tester, and the secret access key is the account password. The host should also point to the Swift storage node's hostname. It also will have to use the old-style calling format, and not the hostname-based container format. Here is an example client setup using the Python boto library on a locally installed all-in-one Swift installation." +msgstr "" + +#: ./doc/config-reference/object-storage/section_object-storage-features.xml:6(title) +msgid "Configure Object Storage features" +msgstr "" + +#: ./doc/config-reference/object-storage/section_object-storage-features.xml:8(title) +msgid "Object Storage zones" +msgstr "" + +#: ./doc/config-reference/object-storage/section_object-storage-features.xml:9(para) +msgid "In OpenStack Object Storage, data is placed across different tiers of failure domains. First, data is spread across regions, then zones, then servers, and finally across drives. Data is placed to get the highest failure domain isolation. If you deploy multiple regions, the Object Storage service places the data across the regions. Within a region, each replica of the data should be stored in unique zones, if possible. If there is only one zone, data should be placed on different servers. And if there is only one server, data should be placed on different drives." +msgstr "" + +#: ./doc/config-reference/object-storage/section_object-storage-features.xml:20(para) +msgid "Regions are widely separated installations with a high-latency or otherwise constrained network link between them. Zones are arbitrarily assigned, and it is up to the administrator of the Object Storage cluster to choose an isolation level and attempt to maintain the isolation level through appropriate zone assignment. For example, a zone may be defined as a rack with a single power source. Or a zone may be a DC room with a common utility provider. Servers are identified by a unique IP/port. Drives are locally attached storage volumes identified by mount point." +msgstr "" + +#: ./doc/config-reference/object-storage/section_object-storage-features.xml:31(para) +msgid "In small clusters (five nodes or fewer), everything is normally in a single zone. Larger Object Storage deployments may assign zone designations differently; for example, an entire cabinet or rack of servers may be designated as a single zone to maintain replica availability if the cabinet becomes unavailable (for example, due to failure of the top of rack switches or a dedicated circuit). In very large deployments, such as service provider level deployments, each zone might have an entirely autonomous switching and power infrastructure, so that even the loss of an electrical circuit or switching aggregator would result in the loss of a single replica at most." +msgstr "" + +#: ./doc/config-reference/object-storage/section_object-storage-features.xml:45(title) +msgid "Rackspace zone recommendations" +msgstr "" + +#: ./doc/config-reference/object-storage/section_object-storage-features.xml:46(para) +msgid "For ease of maintenance on OpenStack Object Storage, Rackspace recommends that you set up at least five nodes. Each node is assigned its own zone (for a total of five zones), which gives you host level redundancy. This enables you to take down a single zone for maintenance and still guarantee object availability in the event that another zone fails during your maintenance." +msgstr "" + +#: ./doc/config-reference/object-storage/section_object-storage-features.xml:54(para) +msgid "You could keep each server in its own cabinet to achieve cabinet level isolation, but you may wish to wait until your swift service is better established before developing cabinet-level isolation. OpenStack Object Storage is flexible; if you later decide to change the isolation level, you can take down one zone at a time and move them to appropriate new homes." +msgstr "" + +#: ./doc/config-reference/object-storage/section_object-storage-features.xml:65(title) +msgid "RAID controller configuration" +msgstr "" + +#: ./doc/config-reference/object-storage/section_object-storage-features.xml:66(para) +msgid "OpenStack Object Storage does not require RAID. In fact, most RAID configurations cause significant performance degradation. The main reason for using a RAID controller is the battery-backed cache. It is very important for data integrity reasons that when the operating system confirms a write has been committed that the write has actually been committed to a persistent location. Most disks lie about hardware commits by default, instead writing to a faster write cache for performance reasons. In most cases, that write cache exists only in non-persistent memory. In the case of a loss of power, this data may never actually get committed to disk, resulting in discrepancies that the underlying file system must handle." +msgstr "" + +#: ./doc/config-reference/object-storage/section_object-storage-features.xml:79(para) +msgid "OpenStack Object Storage works best on the XFS file system, and this document assumes that the hardware being used is configured appropriately to be mounted with the option.   For more information, refer to the XFS FAQ: http://xfs.org/index.php/XFS_FAQ" +msgstr "" + +#: ./doc/config-reference/object-storage/section_object-storage-features.xml:87(para) +msgid "To get the most out of your hardware, it is essential that every disk used in OpenStack Object Storage is configured as a standalone, individual RAID 0 disk; in the case of 6 disks, you would have six RAID 0s or one JBOD. Some RAID controllers do not support JBOD or do not support battery backed cache with JBOD. To ensure the integrity of your data, you must ensure that the individual drive caches are disabled and the battery backed cache in your RAID card is configured and used. Failure to configure the controller properly in this case puts data at risk in the case of sudden loss of power." +msgstr "" + +#: ./doc/config-reference/object-storage/section_object-storage-features.xml:99(para) +msgid "You can also use hybrid drives or similar options for battery backed up cache configurations without a RAID controller." +msgstr "" + +#: ./doc/config-reference/object-storage/section_object-storage-features.xml:105(title) +msgid "Throttle resources through rate limits" +msgstr "" + +#: ./doc/config-reference/object-storage/section_object-storage-features.xml:106(para) +msgid "Rate limiting in OpenStack Object Storage is implemented as a pluggable middleware that you configure on the proxy server. Rate limiting is performed on requests that result in database writes to the account and container SQLite databases. It uses memcached and is dependent on the proxy servers having highly synchronized time. The rate limits are limited by the accuracy of the proxy server clocks." +msgstr "" + +#: ./doc/config-reference/object-storage/section_object-storage-features.xml:115(title) +msgid "Configure rate limiting" +msgstr "" + +#: ./doc/config-reference/object-storage/section_object-storage-features.xml:116(para) +msgid "All configuration is optional. If no account or container limits are provided, no rate limiting occurs. Available configuration options include:" +msgstr "" + +#: ./doc/config-reference/object-storage/section_object-storage-features.xml:122(para) +msgid "The container rate limits are linearly interpolated from the values given. A sample container rate limiting could be:" +msgstr "" + +#: ./doc/config-reference/object-storage/section_object-storage-features.xml:125(para) +msgid "container_ratelimit_100 = 100" +msgstr "" + +#: ./doc/config-reference/object-storage/section_object-storage-features.xml:126(para) +msgid "container_ratelimit_200 = 50" +msgstr "" + +#: ./doc/config-reference/object-storage/section_object-storage-features.xml:127(para) +msgid "container_ratelimit_500 = 20" +msgstr "" + +#: ./doc/config-reference/object-storage/section_object-storage-features.xml:128(para) +msgid "This would result in:" +msgstr "" + +#: ./doc/config-reference/object-storage/section_object-storage-features.xml:130(caption) +msgid "Values for Rate Limiting with Sample Configuration Settings" +msgstr "" + +#: ./doc/config-reference/object-storage/section_object-storage-features.xml:134(td) +msgid "Container Size" +msgstr "" + +#: ./doc/config-reference/object-storage/section_object-storage-features.xml:135(td) +msgid "Rate Limit" +msgstr "" + +#: ./doc/config-reference/object-storage/section_object-storage-features.xml:138(td) +msgid "0-99" +msgstr "" + +#: ./doc/config-reference/object-storage/section_object-storage-features.xml:139(td) +msgid "No limiting" +msgstr "" + +#: ./doc/config-reference/object-storage/section_object-storage-features.xml:142(td) ./doc/config-reference/object-storage/section_object-storage-features.xml:143(td) +msgid "100" +msgstr "" + +#: ./doc/config-reference/object-storage/section_object-storage-features.xml:147(td) +msgid "150" +msgstr "" + +#: ./doc/config-reference/object-storage/section_object-storage-features.xml:148(td) +msgid "75" +msgstr "" + +#: ./doc/config-reference/object-storage/section_object-storage-features.xml:151(td) +msgid "500" +msgstr "" + +#: ./doc/config-reference/object-storage/section_object-storage-features.xml:152(td) ./doc/config-reference/object-storage/section_object-storage-features.xml:156(td) +msgid "20" +msgstr "" + +#: ./doc/config-reference/object-storage/section_object-storage-features.xml:155(td) +msgid "1000" +msgstr "" + +#: ./doc/config-reference/object-storage/section_object-storage-features.xml:163(title) +msgid "Health check" +msgstr "" + +#: ./doc/config-reference/object-storage/section_object-storage-features.xml:164(para) +msgid "Provides an easy way to monitor whether the swift proxy server is alive. If you access the proxy with the path /healthcheck, it respond OK in the response body, which monitoring tools can use." +msgstr "" + +#: ./doc/config-reference/object-storage/section_object-storage-features.xml:174(title) +msgid "Domain remap" +msgstr "" + +#: ./doc/config-reference/object-storage/section_object-storage-features.xml:175(para) +msgid "Middleware that translates container and account parts of a domain to path parameters that the proxy server understands." +msgstr "" + +#: ./doc/config-reference/object-storage/section_object-storage-features.xml:183(title) +msgid "CNAME lookup" +msgstr "" + +#: ./doc/config-reference/object-storage/section_object-storage-features.xml:184(para) +msgid "Middleware that translates an unknown domain in the host header to something that ends with the configured storage_domain by looking up the given domain's CNAME record in DNS." +msgstr "" + +#: ./doc/config-reference/object-storage/section_object-storage-features.xml:194(title) +msgid "Temporary URL" +msgstr "" + +#: ./doc/config-reference/object-storage/section_object-storage-features.xml:195(para) +msgid "Allows the creation of URLs to provide temporary access to objects. For example, a website may wish to provide a link to download a large object in Swift, but the Swift account has no public access. The website can generate a URL that provides GET access for a limited time to the resource. When the web browser user clicks on the link, the browser downloads the object directly from Swift, eliminating the need for the website to act as a proxy for the request. If the user shares the link with all his friends, or accidentally posts it on a forum, the direct access is limited to the expiration time set when the website created the link." +msgstr "" + +#: ./doc/config-reference/object-storage/section_object-storage-features.xml:210(literal) +msgid "temp_url_sig" +msgstr "" + +#: ./doc/config-reference/object-storage/section_object-storage-features.xml:212(para) +msgid "A cryptographic signature" +msgstr "" + +#: ./doc/config-reference/object-storage/section_object-storage-features.xml:216(literal) +msgid "temp_url_expires" +msgstr "" + +#: ./doc/config-reference/object-storage/section_object-storage-features.xml:218(para) +msgid "An expiration date, in Unix time." +msgstr "" + +#: ./doc/config-reference/object-storage/section_object-storage-features.xml:207(para) +msgid "A temporary URL is the typical URL associated with an object, with two additional query parameters:" +msgstr "" + +#: ./doc/config-reference/object-storage/section_object-storage-features.xml:222(para) +msgid "An example of a temporary URL:" +msgstr "" + +#: ./doc/config-reference/object-storage/section_object-storage-features.xml:228(para) +msgid "To create temporary URLs, first set the X-Account-Meta-Temp-URL-Key header on your Swift account to an arbitrary string. This string serves as a secret key. For example, to set a key of b3968d0207b54ece87cccc06515a89d4 using the command-line tool:" +msgstr "" + +#: ./doc/config-reference/object-storage/section_object-storage-features.xml:235(replaceable) +msgid "b3968d0207b54ece87cccc06515a89d4" +msgstr "" + +#: ./doc/config-reference/object-storage/section_object-storage-features.xml:236(para) +msgid "Next, generate an HMAC-SHA1 (RFC 2104) signature to specify:" +msgstr "" + +#: ./doc/config-reference/object-storage/section_object-storage-features.xml:240(para) +msgid "Which HTTP method to allow (typically GET or PUT)" +msgstr "" + +#: ./doc/config-reference/object-storage/section_object-storage-features.xml:245(para) +msgid "The expiry date as a Unix timestamp" +msgstr "" + +#: ./doc/config-reference/object-storage/section_object-storage-features.xml:248(para) +msgid "the full path to the object" +msgstr "" + +#: ./doc/config-reference/object-storage/section_object-storage-features.xml:251(para) +msgid "The secret key set as the X-Account-Meta-Temp-URL-Key" +msgstr "" + +#: ./doc/config-reference/object-storage/section_object-storage-features.xml:255(para) +msgid "Here is code generating the signature for a GET for 24 hours on /v1/AUTH_account/container/object:" +msgstr "" + +#: ./doc/config-reference/object-storage/section_object-storage-features.xml:279(para) +msgid "Changing the X-Account-Meta-Temp-URL-Key invalidates any previously generated temporary URLs within 60 seconds (the memcache time for the key). Swift supports up to two keys, specified by X-Account-Meta-Temp-URL-Key and X-Account-Meta-Temp-URL-Key-2. Signatures are checked against both keys, if present. This is to allow for key rotation without invalidating all existing temporary URLs." +msgstr "" + +#: ./doc/config-reference/object-storage/section_object-storage-features.xml:270(para) +msgid "Any alteration of the resource path or query arguments results in a 401Unauthorized error. Similarly, a PUT where GET was the allowed method returns a 401. HEAD is allowed if GET or PUT is allowed. Using this in combination with browser form post translation middleware could also allow direct-from-browser uploads to specific locations in Swift. Note that " +msgstr "" + +#: ./doc/config-reference/object-storage/section_object-storage-features.xml:291(para) +msgid "Swift includes a script called that generates the query parameters automatically:" +msgstr "" + +#: ./doc/config-reference/object-storage/section_object-storage-features.xml:298(para) +msgid "Because this command only returns the path, you must prefix the Swift storage host name (for example, https://swift-cluster.example.com)." +msgstr "" + +#: ./doc/config-reference/object-storage/section_object-storage-features.xml:301(para) +msgid "With GET Temporary URLs, a Content-Disposition header is set on the response so that browsers interpret this as a file attachment to be saved. The file name chosen is based on the object name, but you can override this with a filename query parameter. The following example specifies a filename of My Test File.pdf:" +msgstr "" + +#: ./doc/config-reference/object-storage/section_object-storage-features.xml:324(emphasis) +msgid "tempurl" +msgstr "" + +#: ./doc/config-reference/object-storage/section_object-storage-features.xml:313(para) +msgid "To enable Temporary URL functionality, edit /etc/swift/proxy-server.conf to add tempurl to the pipeline variable defined in the [pipeline:main] section. The tempurl entry should appear immediately before the authentication filters in the pipeline, such as authtoken, tempauth or keystoneauth. For example:" +msgstr "" + +#: ./doc/config-reference/object-storage/section_object-storage-features.xml:331(title) +msgid "Name check filter" +msgstr "" + +#: ./doc/config-reference/object-storage/section_object-storage-features.xml:332(para) +msgid "Name Check is a filter that disallows any paths that contain defined forbidden characters or that exceed a defined length." +msgstr "" + +#: ./doc/config-reference/object-storage/section_object-storage-features.xml:340(title) +msgid "Constraints" +msgstr "" + +#: ./doc/config-reference/object-storage/section_object-storage-features.xml:341(para) +msgid "To change the OpenStack Object Storage internal limits, update the values in the swift-constraints section in the swift.conf file. Use caution when you update these values because they affect the performance in the entire cluster." +msgstr "" + +#: ./doc/config-reference/object-storage/section_object-storage-features.xml:352(title) +msgid "Cluster health" +msgstr "" + +#: ./doc/config-reference/object-storage/section_object-storage-features.xml:353(para) +msgid "Use the tool to measure overall cluster health. This tool checks if a set of deliberately distributed containers and objects are currently in their proper places within the cluster. For instance, a common deployment has three replicas of each object. The health of that object can be measured by checking if each replica is in its proper place. If only 2 of the 3 is in place the object’s health can be said to be at 66.66%, where 100% would be perfect. A single object’s health, especially an older object, usually reflects the health of that entire partition the object is in. If you make enough objects on a distinct percentage of the partitions in the cluster,you get a good estimate of the overall cluster health. In practice, about 1% partition coverage seems to balance well between accuracy and the amount of time it takes to gather results. The first thing that needs to be done to provide this health value is create a new account solely for this usage. Next, you need to place the containers and objects throughout the system so that they are on distinct partitions. The swift-dispersion-populate tool does this by making up random container and object names until they fall on distinct partitions. Last, and repeatedly for the life of the cluster, you must run the tool to check the health of each of these containers and objects. These tools need direct access to the entire cluster and to the ring files (installing them on a proxy server suffices). The and commands both use the same configuration file, /etc/swift/dispersion.conf. Example dispersion.conf file:" +msgstr "" + +#: ./doc/config-reference/object-storage/section_object-storage-features.xml:393(para) +msgid "There are also configuration options for specifying the dispersion coverage, which defaults to 1%, retries, concurrency, and so on. However, the defaults are usually fine. Once the configuration is in place, run to populate the containers and objects throughout the cluster. Now that those containers and objects are in place, you can run to get a dispersion report, or the overall health of the cluster. Here is an example of a cluster in perfect health:" +msgstr "" + +#: ./doc/config-reference/object-storage/section_object-storage-features.xml:413(para) +msgid "Now, deliberately double the weight of a device in the object ring (with replication turned off) and re-run the dispersion report to show what impact that has:" +msgstr "" + +#: ./doc/config-reference/object-storage/section_object-storage-features.xml:429(para) +msgid "You can see the health of the objects in the cluster has gone down significantly. Of course, this test environment has just four devices, in a production environment with many devices the impact of one device change is much less. Next, run the replicators to get everything put back into place and then rerun the dispersion report:" +msgstr "" + +#: ./doc/config-reference/object-storage/section_object-storage-features.xml:446(para) +msgid "Alternatively, the dispersion report can also be output in json format. This allows it to be more easily consumed by third party utilities:" +msgstr "" + +#. Usage documented in http://docs.openstack.org/developer/swift/overview_large_objects.html +#: ./doc/config-reference/object-storage/section_object-storage-features.xml:460(title) +msgid "Static Large Object (SLO) support" +msgstr "" + +#: ./doc/config-reference/object-storage/section_object-storage-features.xml:461(para) +msgid "This feature is very similar to Dynamic Large Object (DLO) support in that it enables the user to upload many objects concurrently and afterwards download them as a single object. It is different in that it does not rely on eventually consistent container listings to do so. Instead, a user defined manifest of the object segments is used." +msgstr "" + +#: ./doc/config-reference/object-storage/section_object-storage-features.xml:473(title) +msgid "Container quotas" +msgstr "" + +#: ./doc/config-reference/object-storage/section_object-storage-features.xml:474(para) +msgid "The container_quotas middleware implements simple quotas that can be imposed on swift containers by a user with the ability to set container metadata, most likely the account administrator. This can be useful for limiting the scope of containers that are delegated to non-admin users, exposed to formpost uploads, or just as a self-imposed sanity check." +msgstr "" + +#: ./doc/config-reference/object-storage/section_object-storage-features.xml:481(para) +msgid "Any object PUT operations that exceed these quotas return a 413 response (request entity too large) with a descriptive body." +msgstr "" + +#: ./doc/config-reference/object-storage/section_object-storage-features.xml:484(para) +msgid "Quotas are subject to several limitations: eventual consistency, the timeliness of the cached container_info (60 second ttl by default), and it is unable to reject chunked transfer uploads that exceed the quota (though once the quota is exceeded, new chunked transfers are refused)." +msgstr "" + +#: ./doc/config-reference/object-storage/section_object-storage-features.xml:490(para) +msgid "Set quotas by adding meta values to the container. These values are validated when you set them:" +msgstr "" + +#: ./doc/config-reference/object-storage/section_object-storage-features.xml:494(para) +msgid "X-Container-Meta-Quota-Bytes: Maximum size of the container, in bytes." +msgstr "" + +#: ./doc/config-reference/object-storage/section_object-storage-features.xml:498(para) +msgid "X-Container-Meta-Quota-Count: Maximum object count of the container." +msgstr "" + +#: ./doc/config-reference/object-storage/section_object-storage-features.xml:507(title) +msgid "Account quotas" +msgstr "" + +#: ./doc/config-reference/object-storage/section_object-storage-features.xml:508(para) +msgid "The x-account-meta-quota-bytes metadata entry must be requests (PUT, POST) if a given account quota (in bytes) is exceeded while DELETE requests are still allowed." +msgstr "" + +#: ./doc/config-reference/object-storage/section_object-storage-features.xml:512(para) +msgid "The x-account-meta-quota-bytes metadata entry must be set to store and enable the quota. Write requests to this metadata entry are only permitted for resellers. There is no account quota limitation on a reseller account even if x-account-meta-quota-bytes is set." +msgstr "" + +#: ./doc/config-reference/object-storage/section_object-storage-features.xml:517(para) +msgid "Any object PUT operations that exceed the quota return a 413 response (request entity too large) with a descriptive body." +msgstr "" + +#: ./doc/config-reference/object-storage/section_object-storage-features.xml:520(para) +msgid "The following command uses an admin account that own the Reseller role to set a quota on the test account:" +msgstr "" + +#: ./doc/config-reference/object-storage/section_object-storage-features.xml:524(para) +msgid "Here is the stat listing of an account where quota has been set:" +msgstr "" + +#: ./doc/config-reference/object-storage/section_object-storage-features.xml:534(para) +msgid "This command removes the account quota:" +msgstr "" + +#: ./doc/config-reference/object-storage/section_object-storage-features.xml:538(title) +msgid "Bulk delete" +msgstr "" + +#: ./doc/config-reference/object-storage/section_object-storage-features.xml:539(para) +msgid "Use bulk-delete to delete multiple files from an account with a single request. Responds to DELETE requests with a header 'X-Bulk-Delete: true_value'. The body of the DELETE request is a new line separated list of files to delete. The files listed must be URL encoded and in the form:" +msgstr "" + +#: ./doc/config-reference/object-storage/section_object-storage-features.xml:548(para) +msgid "If all files are successfully deleted (or did not exist), the operation returns HTTPOk. If any files failed to delete, the operation returns HTTPBadGateway. In both cases the response body is a JSON dictionary that shows the number of files that were successfully deleted or not found. The files that failed are listed." +msgstr "" + +#: ./doc/config-reference/object-storage/section_object-storage-features.xml:560(title) +msgid "Drive audit" +msgstr "" + +#: ./doc/config-reference/object-storage/section_object-storage-features.xml:561(para) +msgid "The configuration items reference a script that can be run by using to watch for bad drives. If errors are detected, it unmounts the bad drive, so that OpenStack Object Storage can work around it. It takes the following options:" +msgstr "" + +#: ./doc/config-reference/object-storage/section_object-storage-features.xml:572(title) +msgid "Form post" +msgstr "" + +#: ./doc/config-reference/object-storage/section_object-storage-features.xml:573(para) +msgid "Middleware that provides the ability to upload objects to a cluster using an HTML form POST. The format of the form is:" +msgstr "" + +#: ./doc/config-reference/object-storage/section_object-storage-features.xml:588(para) +msgid "The swift-url is the URL to the Swift destination, such as: https://swift-cluster.example.com/v1/AUTH_account/container/object_prefix The name of each file uploaded is appended to the specified swift-url. So, you can upload directly to the root of container with a url like: https://swift-cluster.example.com/v1/AUTH_account/container/ Optionally, you can include an object prefix to better separate different users’ uploads, such as: https://swift-cluster.example.com/v1/AUTH_account/container/object_prefix" +msgstr "" + +#: ./doc/config-reference/object-storage/section_object-storage-features.xml:600(para) +msgid "The form method must be POST and the enctype must be set as multipart/form-data." +msgstr "" + +#: ./doc/config-reference/object-storage/section_object-storage-features.xml:603(para) +msgid "The redirect attribute is the URL to redirect the browser to after the upload completes. The URL has status and message query parameters added to it, indicating the HTTP status code for the upload (2xx is success) and a possible message for further information if there was an error (such as “max_file_size exceeded”)." +msgstr "" + +#: ./doc/config-reference/object-storage/section_object-storage-features.xml:610(para) +msgid "The max_file_size attribute must be included and indicates the largest single file upload that can be done, in bytes." +msgstr "" + +#: ./doc/config-reference/object-storage/section_object-storage-features.xml:613(para) +msgid "The max_file_count attribute must be included and indicates the maximum number of files that can be uploaded with the form. Include additional <![CDATA[<input type=\"file\" name=\"filexx\"/>]]> attributes if desired." +msgstr "" + +#: ./doc/config-reference/object-storage/section_object-storage-features.xml:619(para) +msgid "The expires attribute is the Unix timestamp before which the form must be submitted before it is invalidated." +msgstr "" + +#: ./doc/config-reference/object-storage/section_object-storage-features.xml:622(para) +msgid "The signature attribute is the HMAC-SHA1 signature of the form. This sample Python code shows how to compute the signature:" +msgstr "" + +#: ./doc/config-reference/object-storage/section_object-storage-features.xml:639(para) +msgid "The key is the value of the X-Account-Meta-Temp-URL-Key header on the account." +msgstr "" + +#: ./doc/config-reference/object-storage/section_object-storage-features.xml:642(para) +msgid "Be certain to use the full path, from the /v1/ onward." +msgstr "" + +#: ./doc/config-reference/object-storage/section_object-storage-features.xml:644(para) +msgid "The command line tool may be used (mostly just when testing) to compute expires and signature." +msgstr "" + +#: ./doc/config-reference/object-storage/section_object-storage-features.xml:648(para) +msgid "The file attributes must appear after the other attributes to be processed correctly. If attributes come after the file, they are not sent with the sub-request because on the server side, all attributes in the file cannot be parsed unless the whole file is read into memory and the server does not have enough memory to service these requests. So, attributes that follow the file are ignored." +msgstr "" + +#: ./doc/config-reference/object-storage/section_object-storage-features.xml:661(title) +msgid "Static web sites" +msgstr "" + +#: ./doc/config-reference/object-storage/section_object-storage-features.xml:662(para) +msgid "When configured, this middleware serves container data as a static web site with index file and error file resolution and optional file listings. This mode is normally only active for anonymous requests." +msgstr "" + +#: ./doc/config-reference/object-storage/section_object-storage-cors.xml:6(title) +msgid "Cross-origin resource sharing" +msgstr "" + +#: ./doc/config-reference/object-storage/section_object-storage-cors.xml:7(para) +msgid "Cross-Origin Resource Sharing (CORS) is a mechanism to allow code running in a browser (JavaScript for example) to make requests to a domain other then the one from where it originated. Swift supports CORS requests to containers and objects within the containers using metadata held on the container." +msgstr "" + +#: ./doc/config-reference/object-storage/section_object-storage-cors.xml:13(para) +msgid "In addition to the metadata on containers, you can use the option in the proxy-server.conf file to set a list of hosts that are included with any CORS request by default." +msgstr "" + +#: ./doc/config-reference/object-storage/section_object-storage-general-service-conf.xml:6(title) +msgid "Object Storage general service configuration" +msgstr "" + +#: ./doc/config-reference/object-storage/section_object-storage-general-service-conf.xml:7(para) +msgid "Most Object Storage services fall into two categories, Object Storage's wsgi servers and background daemons." +msgstr "" + +#: ./doc/config-reference/object-storage/section_object-storage-general-service-conf.xml:11(para) +msgid "Object Storage uses paste.deploy to manage server configurations. Read more at http://pythonpaste.org/deploy/." +msgstr "" + +#: ./doc/config-reference/object-storage/section_object-storage-general-service-conf.xml:14(para) +msgid "Default configuration options are set in the `[DEFAULT]` section, and any options specified there can be overridden in any of the other sections when the syntax set option_name = value is in place." +msgstr "" + +#: ./doc/config-reference/object-storage/section_object-storage-general-service-conf.xml:19(para) +msgid "Configuration for servers and daemons can be expressed together in the same file for each type of server, or separately. If a required section for the service trying to start is missing there will be an error. The sections not used by the service are ignored." +msgstr "" + +#: ./doc/config-reference/object-storage/section_object-storage-general-service-conf.xml:25(para) +msgid "Consider the example of an object storage node. By convention configuration for the object-server, object-updater, object-replicator, and object-auditor exist in a single file /etc/swift/object-server.conf:" +msgstr "" + +#: ./doc/config-reference/object-storage/section_object-storage-general-service-conf.xml:47(para) +msgid "Object Storage services expect a configuration path as the first argument:" +msgstr "" + +#: ./doc/config-reference/object-storage/section_object-storage-general-service-conf.xml:55(para) +msgid "If you omit the object-auditor section this file can not be used as the configuration path when starting the daemon:" +msgstr "" + +#: ./doc/config-reference/object-storage/section_object-storage-general-service-conf.xml:63(para) +msgid "If the configuration path is a directory instead of a file all of the files in the directory with the file extension \".conf\" will be combined to generate the configuration object which is delivered to the Object Storage service. This is referred to generally as \"directory based configuration\"." +msgstr "" + +#: ./doc/config-reference/object-storage/section_object-storage-general-service-conf.xml:70(para) +msgid "Directory based configuration leverages ConfigParser's native multi-file support. Files ending in \".conf\" in the given directory are parsed in lexicographical order. File names starting with '.' are ignored. A mixture of file and directory configuration paths is not supported - if the configuration path is a file, only that file will be parsed." +msgstr "" + +#: ./doc/config-reference/object-storage/section_object-storage-general-service-conf.xml:78(para) +msgid "The Object Storage service management tool swift-init has adopted the convention of looking for /etc/swift/{type}-server.conf.d/ if the file /etc/swift/{type}-server.conf file does not exist." +msgstr "" + +#: ./doc/config-reference/object-storage/section_object-storage-general-service-conf.xml:86(para) +msgid "When using directory based configuration, if the same option under the same section appears more than once in different files, the last value parsed is said to override previous occurrences. You can ensure proper override precedence by prefixing the files in the configuration directory with numerical values, as in the following example file layout:" +msgstr "" + +#: ./doc/config-reference/object-storage/section_object-storage-general-service-conf.xml:105(para) +msgid "You can inspect the resulting combined configuration object using the command line tool." +msgstr "" + +#. Put one translator per line, in the form of NAME , YEAR1, YEAR2 +#: ./doc/config-reference/object-storage/section_object-storage-general-service-conf.xml:0(None) +msgid "translator-credits" +msgstr "" + diff --git a/doc/config-reference/locale/he_IL.po b/doc/config-reference/locale/he_IL.po new file mode 100644 index 0000000000..e725132c91 --- /dev/null +++ b/doc/config-reference/locale/he_IL.po @@ -0,0 +1,10848 @@ +# +# Translators: +msgid "" +msgstr "" +"Project-Id-Version: OpenStack Manuals\n" +"POT-Creation-Date: 2014-01-30 06:24+0000\n" +"PO-Revision-Date: 2014-01-29 22:14+0000\n" +"Last-Translator: openstackjenkins \n" +"Language-Team: Hebrew (Israel) (http://www.transifex.com/projects/p/openstack/language/he_IL/)\n" +"MIME-Version: 1.0\n" +"Content-Type: text/plain; charset=UTF-8\n" +"Content-Transfer-Encoding: 8bit\n" +"Language: he_IL\n" +"Plural-Forms: nplurals=2; plural=(n != 1);\n" + +#: ./doc/config-reference/ch_imageservice.xml10(title) +msgid "Image Service" +msgstr "" + +#: ./doc/config-reference/ch_imageservice.xml11(para) +msgid "" +"Compute relies on an external image service to store virtual machine images " +"and maintain a catalog of available images. By default, Compute is " +"configured to use the OpenStack Image Service (Glance), which is currently " +"the only supported image service." +msgstr "" + +#: ./doc/config-reference/ch_imageservice.xml19(para) +msgid "" +"If your installation requires euca2ools to register new images, you must run" +" the nova-objectstore service. " +"This service provides an Amazon S3 front-end for Glance, which is required " +"by euca2ools." +msgstr "" + +#: ./doc/config-reference/ch_imageservice.xml26(para) +msgid "" +"You can modify many of the OpenStack Image Catalogue and Delivery Service. " +"The following tables provide a comprehensive list." +msgstr "" + +#: ./doc/config-reference/ch_config-overview.xml6(title) +msgid "OpenStack configuration overview" +msgstr "" + +#: ./doc/config-reference/ch_config-overview.xml7(para) +msgid "" +"OpenStack is a collection of open source project components that enable " +"setting up cloud services. Each component uses similar configuration " +"techniques and a common framework for INI file options." +msgstr "" + +#: ./doc/config-reference/ch_config-overview.xml12(para) +msgid "" +"This guide pulls together multiple references and configuration options for " +"the following OpenStack components:" +msgstr "" + +#: ./doc/config-reference/ch_config-overview.xml16(para) +msgid "OpenStack Identity" +msgstr "" + +#: ./doc/config-reference/ch_config-overview.xml17(para) +msgid "OpenStack Compute" +msgstr "" + +#: ./doc/config-reference/ch_config-overview.xml18(para) +msgid "OpenStack Image Service" +msgstr "" + +#: ./doc/config-reference/ch_config-overview.xml19(para) +msgid "OpenStack Networking" +msgstr "" + +#: ./doc/config-reference/ch_config-overview.xml20(para) +msgid "OpenStack Dashboard" +msgstr "" + +#: ./doc/config-reference/ch_config-overview.xml21(para) +msgid "OpenStack Object Storage" +msgstr "" + +#: ./doc/config-reference/ch_config-overview.xml22(para) +msgid "OpenStack Block Storage" +msgstr "" + +#: ./doc/config-reference/ch_computeconfigure.xml6(title) +msgid "Compute" +msgstr "" + +#: ./doc/config-reference/ch_computeconfigure.xml7(para) +msgid "" +"The OpenStack Compute service is a cloud computing fabric controller, which " +"is the main part of an IaaS system. You can use OpenStack Compute to host " +"and manage cloud computing systems. This section describes the OpenStack " +"Compute configuration options." +msgstr "" + +#: ./doc/config-reference/ch_computeconfigure.xml12(para) +msgid "" +"To configure your Compute installation, you must define configuration " +"options in these files:" +msgstr "" + +#: ./doc/config-reference/ch_computeconfigure.xml16(para) +msgid "" +"nova.conf. Contains most of the Compute configuration " +"options. Resides in the /etc/nova directory." +msgstr "" + +#: ./doc/config-reference/ch_computeconfigure.xml21(para) +msgid "" +"api-paste.ini. Defines Compute limits. Resides in the " +"/etc/nova directory." +msgstr "" + +#: ./doc/config-reference/ch_computeconfigure.xml26(para) +msgid "" +"Related Image Service and Identity Service management configuration files." +msgstr "" + +#: ./doc/config-reference/ch_computeconfigure.xml32(title) +msgid "Configure logging" +msgstr "" + +#: ./doc/config-reference/ch_computeconfigure.xml33(para) +msgid "" +"You can use nova.conf file to configure where Compute " +"logs events, the level of logging, and log formats." +msgstr "" + +#: ./doc/config-reference/ch_computeconfigure.xml36(para) +msgid "" +"To customize log formats for OpenStack Compute, use these configuration " +"option settings." +msgstr "" + +#: ./doc/config-reference/ch_computeconfigure.xml41(title) +msgid "Configure authentication and authorization" +msgstr "" + +#: ./doc/config-reference/ch_computeconfigure.xml42(para) +msgid "" +"There are different methods of authentication for the OpenStack Compute " +"project, including no authentication. The preferred system is the OpenStack " +"Identity Service, code-named Keystone." +msgstr "" + +#: ./doc/config-reference/ch_computeconfigure.xml46(para) +msgid "" +"To customize authorization settings for Compute, see these configuration " +"settings in nova.conf." +msgstr "" + +#: ./doc/config-reference/ch_computeconfigure.xml49(para) +msgid "" +"To customize certificate authority settings for Compute, see these " +"configuration settings in nova.conf." +msgstr "" + +#: ./doc/config-reference/ch_computeconfigure.xml53(para) +msgid "" +"To customize Compute and the Identity service to use LDAP as a backend, " +"refer to these configuration settings in nova.conf." +msgstr "" + +#: ./doc/config-reference/ch_computeconfigure.xml62(title) +msgid "Configure resize" +msgstr "" + +#: ./doc/config-reference/ch_computeconfigure.xml63(para) +msgid "" +"Resize (or Server resize) is the ability to change the flavor of a server, " +"thus allowing it to upscale or downscale according to user needs. For this " +"feature to work properly, you might need to configure some underlying virt " +"layers." +msgstr "" + +#: ./doc/config-reference/ch_computeconfigure.xml68(title) +#: ./doc/config-reference/compute/section_hypervisor_kvm.xml5(title) +msgid "KVM" +msgstr "" + +#: ./doc/config-reference/ch_computeconfigure.xml69(para) +msgid "" +"Resize on KVM is implemented currently by transferring the images between " +"compute nodes over ssh. For KVM you need hostnames to resolve properly and " +"passwordless ssh access between your compute hosts. Direct access from one " +"compute host to another is needed to copy the VM file across." +msgstr "" + +#: ./doc/config-reference/ch_computeconfigure.xml74(para) +msgid "" +"Cloud end users can find out how to resize a server by reading the OpenStack End User Guide." +msgstr "" + +#: ./doc/config-reference/ch_computeconfigure.xml80(title) +#: ./doc/config-reference/compute/section_compute-configure-migrations.xml289(title) +msgid "XenServer" +msgstr "" + +#: ./doc/config-reference/ch_computeconfigure.xml81(para) +msgid "" +"To get resize to work with XenServer (and XCP), you need to establish a root" +" trust between all hypervisor nodes and provide an /image mount point to " +"your hypervisors dom0." +msgstr "" + +#: ./doc/config-reference/bk-config-ref.xml6(title) +#: ./doc/config-reference/bk-config-ref.xml8(titleabbrev) +msgid "OpenStack Configuration Reference" +msgstr "" + +#: ./doc/config-reference/bk-config-ref.xml16(orgname) +#: ./doc/config-reference/bk-config-ref.xml21(holder) +msgid "OpenStack Foundation" +msgstr "" + +#: ./doc/config-reference/bk-config-ref.xml20(year) +msgid "2013" +msgstr "" + +#: ./doc/config-reference/bk-config-ref.xml23(productname) +msgid "OpenStack" +msgstr "" + +#: ./doc/config-reference/bk-config-ref.xml24(releaseinfo) +msgid "havana" +msgstr "" + +#: ./doc/config-reference/bk-config-ref.xml28(remark) +msgid "Copyright details are filled in by the template." +msgstr "" + +#: ./doc/config-reference/bk-config-ref.xml33(para) +msgid "" +"This document is for system administrators who want to look up configuration" +" options. It contains lists of configuration options available with " +"OpenStack and uses auto-generation to generate options and the descriptions " +"from the code for each project. It includes sample configuration files." +msgstr "" + +#: ./doc/config-reference/bk-config-ref.xml43(date) +msgid "2014-01-09" +msgstr "" + +#: ./doc/config-reference/bk-config-ref.xml47(para) +msgid "" +"Removes content addressed in installation, merges duplicated content, and " +"revises legacy references." +msgstr "" + +#: ./doc/config-reference/bk-config-ref.xml55(date) +msgid "2013-10-17" +msgstr "" + +#: ./doc/config-reference/bk-config-ref.xml59(para) +msgid "Havana release." +msgstr "" + +#: ./doc/config-reference/bk-config-ref.xml65(date) +msgid "2013-08-16" +msgstr "" + +#: ./doc/config-reference/bk-config-ref.xml69(para) +msgid "" +"Moves Block Storage driver configuration information from the " +"Block Storage Administration Guide to this reference." +msgstr "" + +#: ./doc/config-reference/bk-config-ref.xml77(date) +msgid "2013-06-10" +msgstr "" + +#: ./doc/config-reference/bk-config-ref.xml81(para) +msgid "Initial creation of Configuration Reference." +msgstr "" + +#: ./doc/config-reference/ch_blockstorageconfigure.xml10(title) +msgid "Block Storage" +msgstr "" + +#: ./doc/config-reference/ch_blockstorageconfigure.xml11(para) +msgid "" +"The OpenStack Block Storage Service works with many different storage " +"drivers that you can configure by using these instructions." +msgstr "" + +#: ./doc/config-reference/ch_blockstorageconfigure.xml15(title) +#: ./doc/config-reference/block-storage/drivers/emc-volume-driver.xml192(title) +msgid "cinder.conf configuration file" +msgstr "" + +#: ./doc/config-reference/ch_blockstorageconfigure.xml16(para) +msgid "" +"The cinder.conf file is installed in " +"/etc/cinder by default. When you manually install the " +"Block Storage Service, the options in the cinder.conf " +"file are set to default values." +msgstr "" + +#: ./doc/config-reference/ch_blockstorageconfigure.xml20(para) +msgid "This example shows a typical cinder.conf file:" +msgstr "" + +#: ./doc/config-reference/ch_identityconfigure.xml10(title) +msgid "Identity Service" +msgstr "" + +#: ./doc/config-reference/ch_identityconfigure.xml11(para) +msgid "" +"This chapter details the OpenStack Identity Service configuration options. " +"For installation prerequisites and step-by-step walkthroughs, see the " +"OpenStack Installation Guide for your distribution " +"(docs.openstack.org) and " +"Cloud Administrator Guide." +msgstr "" + +#: ./doc/config-reference/ch_objectstorageconfigure.xml6(title) +msgid "Object Storage" +msgstr "" + +#: ./doc/config-reference/ch_objectstorageconfigure.xml7(para) +msgid "" +"OpenStack Object Storage uses multiple configuration files for multiple " +"services and background daemons, and to manage server " +"configurations. Default configuration options appear in the " +"[DEFAULT] section. You can override the default values by " +"setting values in the other sections." +msgstr "" + +#: ./doc/config-reference/ch_objectstorageconfigure.xml17(title) +msgid "Object server configuration" +msgstr "" + +#: ./doc/config-reference/ch_objectstorageconfigure.xml18(para) +msgid "" +"Find an example object server configuration at etc/object-server" +".conf-sample in the source code repository." +msgstr "" + +#: ./doc/config-reference/ch_objectstorageconfigure.xml21(para) +#: ./doc/config-reference/ch_objectstorageconfigure.xml48(para) +#: ./doc/config-reference/ch_objectstorageconfigure.xml78(para) +#: ./doc/config-reference/ch_objectstorageconfigure.xml105(para) +msgid "The available configuration options are:" +msgstr "" + +#: ./doc/config-reference/ch_objectstorageconfigure.xml39(title) +msgid "Sample object server configuration file" +msgstr "" + +#: ./doc/config-reference/ch_objectstorageconfigure.xml44(title) +msgid "Container server configuration" +msgstr "" + +#: ./doc/config-reference/ch_objectstorageconfigure.xml45(para) +msgid "" +"Find an example container server configuration at etc/container-" +"server.conf-sample in the source code repository." +msgstr "" + +#: ./doc/config-reference/ch_objectstorageconfigure.xml68(title) +msgid "Sample container server configuration file" +msgstr "" + +#: ./doc/config-reference/ch_objectstorageconfigure.xml74(title) +msgid "Account server configuration" +msgstr "" + +#: ./doc/config-reference/ch_objectstorageconfigure.xml75(para) +msgid "" +"Find an example account server configuration at etc/account-server" +".conf-sample in the source code repository." +msgstr "" + +#: ./doc/config-reference/ch_objectstorageconfigure.xml96(title) +msgid "Sample account server configuration file" +msgstr "" + +#: ./doc/config-reference/ch_objectstorageconfigure.xml101(title) +msgid "Proxy server configuration" +msgstr "" + +#: ./doc/config-reference/ch_objectstorageconfigure.xml102(para) +msgid "" +"Find an example proxy server configuration at etc/proxy-server" +".conf-sample in the source code repository." +msgstr "" + +#: ./doc/config-reference/ch_objectstorageconfigure.xml131(title) +msgid "Sample proxy server configuration file" +msgstr "" + +#: ./doc/config-reference/ch_dashboardconfigure.xml6(title) +msgid "Dashboard" +msgstr "" + +#: ./doc/config-reference/ch_dashboardconfigure.xml7(para) +msgid "" +"This chapter describes how to configure the OpenStack dashboard with Apache " +"web server." +msgstr "" + +#: ./doc/config-reference/ch_networkingconfigure.xml10(title) +msgid "Networking" +msgstr "" + +#: ./doc/config-reference/ch_networkingconfigure.xml11(para) +msgid "" +"This chapter explains the OpenStack Networking configuration options. For " +"installation prerequisites, steps, and use cases, see the " +"OpenStack Installation Guide for your distribution " +"(docs.openstack.org) and " +"Cloud Administrator Guide." +msgstr "" + +#: ./doc/config-reference/compute/section_compute-configure-xen.xml10(title) +#: ./doc/config-reference/compute/section_compute-configure-xen.xml75(title) +msgid "Xen configuration reference" +msgstr "" + +#: ./doc/config-reference/compute/section_compute-configure-xen.xml11(para) +msgid "" +"The following section discusses some commonly changed options in XenServer. " +"The table below provides a complete reference of all configuration options " +"available for configuring Xen with OpenStack." +msgstr "" + +#: ./doc/config-reference/compute/section_compute-configure-xen.xml15(para) +msgid "" +"The recommended way to use Xen with OpenStack is through the XenAPI driver. " +"To enable the XenAPI driver, add the following configuration options " +"/etc/nova/nova.conf and restart the nova-compute service:" +msgstr "" + +#: ./doc/config-reference/compute/section_compute-configure-xen.xml23(para) +msgid "" +"These connection details are used by the OpenStack Compute service to " +"contact your hypervisor and are the same details you use to connect " +"XenCenter, the XenServer management console, to your XenServer or XCP box." +msgstr "" + +#: ./doc/config-reference/compute/section_compute-configure-xen.xml27(para) +msgid "" +"The xenapi_connection_url is generally the management " +"network IP address of the XenServer. Though it is possible to use the " +"internal network IP Address (169.250.0.1) to contact XenAPI, this does not " +"allow live migration between hosts, and other functionalities like host " +"aggregates do not work." +msgstr "" + +#: ./doc/config-reference/compute/section_compute-configure-xen.xml34(para) +msgid "" +"It is possible to manage Xen using libvirt, though this is not well-tested " +"or supported. To experiment using Xen through libvirt add the following " +"configuration options /etc/nova/nova.conf: " +"" +msgstr "" + +#: ./doc/config-reference/compute/section_compute-configure-xen.xml42(title) +#: ./doc/config-reference/networking/section_networking-options-reference.xml19(title) +msgid "Agent" +msgstr "" + +#: ./doc/config-reference/compute/section_compute-configure-xen.xml43(para) +msgid "" +"If you don't have the guest agent on your VMs, it takes a long time for nova" +" to decide the VM has successfully started. Generally a large timeout is " +"required for Windows instances, bug you may want to tweak " +"agent_version_timeout" +msgstr "" + +#: ./doc/config-reference/compute/section_compute-configure-xen.xml48(title) +msgid "Firewall" +msgstr "" + +#: ./doc/config-reference/compute/section_compute-configure-xen.xml49(para) +msgid "" +"If using nova-network, IPTables is supported: Alternately, " +"doing the isolation in Dom0: " +msgstr "" + +#: ./doc/config-reference/compute/section_compute-configure-xen.xml56(title) +msgid "VNC proxy address" +msgstr "" + +#: ./doc/config-reference/compute/section_compute-configure-xen.xml57(para) +msgid "" +"Assuming you are talking to XenAPI through the host local management " +"network, and XenServer is on the address: 169.254.0.1, you can use the " +"following: vncserver_proxyclient_address=169.254.0.1" +msgstr "" + +#: ./doc/config-reference/compute/section_compute-configure-xen.xml63(title) +msgid "Storage" +msgstr "" + +#: ./doc/config-reference/compute/section_compute-configure-xen.xml71(para) +msgid "" +"To use a XenServer pool, you must create the pool by using the Host " +"Aggregates feature." +msgstr "" + +#: ./doc/config-reference/compute/section_compute-configure-xen.xml64(para) +msgid "" +"You can specify which Storage Repository to use with nova by looking at the " +"following flag. The default is to use the local-storage setup by the default" +" installer: Another good alternative is to use the " +"\"default\" storage (for example if you have attached NFS or any other " +"shared storage): " +msgstr "" + +#. When image changes, this message will be marked fuzzy or untranslated for +#. you. +#. It doesn't matter what you translate it to: it's not used at all. +#: ./doc/config-reference/compute/section_introduction-to-xen.xml127(None) +msgid "" +"@@image: '../../common/figures/xenserver_architecture.png'; " +"md5=8eb25be1693aa7865967ac7b07d3e563" +msgstr "" + +#: ./doc/config-reference/compute/section_introduction-to-xen.xml7(title) +msgid "Xen, XenAPI, XenServer, and XCP" +msgstr "" + +#: ./doc/config-reference/compute/section_introduction-to-xen.xml9(para) +msgid "" +"This section describes Xen, XenAPI, XenServer, and XCP, their differences, " +"and how to use them with OpenStack. After you understand how the Xen and KVM" +" architectures differ, you can determine when to use each architecture in " +"your OpenStack cloud." +msgstr "" + +#: ./doc/config-reference/compute/section_introduction-to-xen.xml15(title) +msgid "Xen terminology" +msgstr "" + +#: ./doc/config-reference/compute/section_introduction-to-xen.xml16(para) +msgid "" +"Xen. A hypervisor that provides the " +"fundamental isolation between virtual machines. Xen is open source (GPLv2) " +"and is managed by Xen.org, an cross-industry organization." +msgstr "" + +#: ./doc/config-reference/compute/section_introduction-to-xen.xml20(para) +msgid "" +"Xen is a component of many different products and projects. The hypervisor " +"itself is very similar across all these projects, but the way that it is " +"managed can be different, which can cause confusion if you're not clear " +"which tool stack you are using. Make sure you know what tool stack you want " +"before you get started." +msgstr "" + +#: ./doc/config-reference/compute/section_introduction-to-xen.xml26(para) +msgid "" +"Xen Cloud Platform (XCP). An open source " +"(GPLv2) tool stack for Xen. It is designed specifically as a platform for " +"enterprise and cloud computing, and is well integrated with OpenStack. XCP " +"is available both as a binary distribution, installed from an iso, and from " +"Linux distributions, such as xcp-xapi in Ubuntu. The current versions of XCP available" +" in Linux distributions do not yet include all the features available in the" +" binary distribution of XCP." +msgstr "" + +#: ./doc/config-reference/compute/section_introduction-to-xen.xml38(para) +msgid "" +"Citrix XenServer. A commercial product. " +"It is based on XCP, and exposes the same tool stack and management API. As " +"an analogy, think of XenServer being based on XCP in the way that Red Hat " +"Enterprise Linux is based on Fedora. XenServer has a free version (which is " +"very similar to XCP) and paid-for versions with additional features enabled." +" Citrix provides support for XenServer, but as of July 2012, they do not " +"provide any support for XCP. For a comparison between these products see the" +" XCP " +"Feature Matrix." +msgstr "" + +#: ./doc/config-reference/compute/section_introduction-to-xen.xml50(para) +msgid "" +"Both XenServer and XCP include Xen, Linux, and the primary control daemon " +"known as xapi." +msgstr "" + +#: ./doc/config-reference/compute/section_introduction-to-xen.xml53(para) +msgid "" +"The API shared between XCP and XenServer is called XenAPI. OpenStack usually refers to XenAPI, to " +"indicate that the integration works equally well on XCP and XenServer. " +"Sometimes, a careless person will refer to XenServer specifically, but you " +"can be reasonably confident that anything that works on XenServer will also " +"work on the latest version of XCP. Read the " +" XenAPI Object Model Overview for definitions of XenAPI specific " +"terms such as SR, VDI, VIF and PIF." +msgstr "" + +#: ./doc/config-reference/compute/section_introduction-to-xen.xml66(title) +msgid "Privileged and unprivileged domains" +msgstr "" + +#: ./doc/config-reference/compute/section_introduction-to-xen.xml67(para) +msgid "" +"A Xen host runs a number of virtual machines, VMs, or domains (the terms are" +" synonymous on Xen). One of these is in charge of running the rest of the " +"system, and is known as \"domain 0,\" or \"dom0.\" It is the first domain to" +" boot after Xen, and owns the storage and networking hardware, the device " +"drivers, and the primary control software. Any other VM is unprivileged, and" +" are known as a \"domU\" or \"guest\". All customer VMs are unprivileged of " +"course, but you should note that on Xen the OpenStack control software " +"(nova-compute) also runs in a " +"domU. This gives a level of security isolation between the privileged system" +" software and the OpenStack software (much of which is customer-facing). " +"This architecture is described in more detail later." +msgstr "" + +#: ./doc/config-reference/compute/section_introduction-to-xen.xml83(para) +msgid "" +"There is an ongoing project to split domain 0 into multiple privileged " +"domains known as driver domains and " +"stub domains. This would give even better" +" separation between critical components. This technology is what powers " +"Citrix XenClient RT, and is likely to be added into XCP in the next few " +"years. However, the current architecture just has three levels of " +"separation: dom0, the OpenStack domU, and the completely unprivileged " +"customer VMs." +msgstr "" + +#: ./doc/config-reference/compute/section_introduction-to-xen.xml96(title) +msgid "Paravirtualized versus hardware virtualized domains" +msgstr "" + +#: ./doc/config-reference/compute/section_introduction-to-xen.xml98(para) +msgid "" +"A Xen virtual machine can be paravirtualized " +"(PV) or hardware virtualized " +"(HVM). This refers to the interaction between Xen, domain 0, and " +"the guest VM's kernel. PV guests are aware of the fact that they are " +"virtualized and will co-operate with Xen and domain 0; this gives them " +"better performance characteristics. HVM guests are not aware of their " +"environment, and the hardware has to pretend that they are running on an " +"unvirtualized machine. HVM guests do not need to modify the guest operating " +"system, which is essential when running Windows." +msgstr "" + +#: ./doc/config-reference/compute/section_introduction-to-xen.xml111(para) +msgid "" +"In OpenStack, customer VMs may run in either PV or HVM mode. However, the " +"OpenStack domU (that's the one running nova-" +"compute) must be running in " +"PV mode." +msgstr "" + +#: ./doc/config-reference/compute/section_introduction-to-xen.xml119(title) +msgid "XenAPI Deployment Architecture" +msgstr "" + +#: ./doc/config-reference/compute/section_introduction-to-xen.xml121(para) +msgid "" +"When you deploy OpenStack on XCP or XenServer, you get something similar to " +"this: " +msgstr "" + +#: ./doc/config-reference/compute/section_introduction-to-xen.xml133(para) +msgid "The hypervisor: Xen" +msgstr "" + +#: ./doc/config-reference/compute/section_introduction-to-xen.xml136(para) +msgid "" +"Domain 0: runs xapi and some small pieces from OpenStack (some xapi plug-ins" +" and network isolation rules). The majority of this is provided by XenServer" +" or XCP (or yourself using Kronos)." +msgstr "" + +#: ./doc/config-reference/compute/section_introduction-to-xen.xml143(para) +msgid "" +"OpenStack VM: The nova-compute " +"code runs in a paravirtualized virtual machine, running on the host under " +"management. Each host runs a local instance of nova-compute. It will often also be running nova-network " +"(depending on your network mode). In this case, nova-network is managing the" +" addresses given to the tenant VMs through DHCP." +msgstr "" + +#: ./doc/config-reference/compute/section_introduction-to-xen.xml155(para) +msgid "" +"Nova uses the XenAPI Python library to talk to xapi, and it uses the " +"Management Network to reach from the domU to dom0 without leaving the host." +msgstr "" + +#: ./doc/config-reference/compute/section_introduction-to-xen.xml131(para) +msgid "Key things to note: " +msgstr "" + +#: ./doc/config-reference/compute/section_introduction-to-xen.xml163(para) +msgid "The above diagram assumes FlatDHCP networking (the DevStack default)." +msgstr "" + +#: ./doc/config-reference/compute/section_introduction-to-xen.xml169(para) +msgid "" +"Management network - RabbitMQ, MySQL, etc. Please note that the VM images " +"are downloaded by the XenAPI plug-ins, so make sure that the images can be " +"downloaded through the management network. It usually means binding those " +"services to the management interface." +msgstr "" + +#: ./doc/config-reference/compute/section_introduction-to-xen.xml179(para) +msgid "" +"Tenant network - controlled by nova-network. The parameters of this network " +"depend on the networking model selected (Flat, Flat DHCP, VLAN)." +msgstr "" + +#: ./doc/config-reference/compute/section_introduction-to-xen.xml186(para) +msgid "Public network - floating IPs, public API endpoints." +msgstr "" + +#: ./doc/config-reference/compute/section_introduction-to-xen.xml167(para) +msgid "There are three main OpenStack Networks:" +msgstr "" + +#: ./doc/config-reference/compute/section_introduction-to-xen.xml192(para) +msgid "" +"The networks shown here must be connected to the corresponding physical " +"networks within the data center. In the simplest case, three individual " +"physical network cards could be used. It is also possible to use VLANs to " +"separate these networks. Please note, that the selected configuration must " +"be in line with the networking model selected for the cloud. (In case of " +"VLAN networking, the physical channels have to be able to forward the tagged" +" traffic.)" +msgstr "" + +#: ./doc/config-reference/compute/section_introduction-to-xen.xml161(para) +msgid "Some notes on the networking: " +msgstr "" + +#: ./doc/config-reference/compute/section_introduction-to-xen.xml207(title) +msgid "XenAPI pools" +msgstr "" + +#: ./doc/config-reference/compute/section_introduction-to-xen.xml208(para) +msgid "" +"The host-aggregates feature enables you to create pools of XenServer hosts " +"to enable live migration when using shared storage. However, you cannot " +"configure shared storage." +msgstr "" + +#: ./doc/config-reference/compute/section_introduction-to-xen.xml214(title) +msgid "Further reading" +msgstr "" + +#: ./doc/config-reference/compute/section_introduction-to-xen.xml218(para) +msgid "" +"Citrix XenServer official documentation: " +"http://docs.vmd.citrix.com/XenServer." +msgstr "" + +#: ./doc/config-reference/compute/section_introduction-to-xen.xml225(para) +msgid "" +"What is Xen? by Xen.org: " +"http://xen.org/files/Marketing/WhatisXen.pdf." +msgstr "" + +#: ./doc/config-reference/compute/section_introduction-to-xen.xml231(para) +msgid "" +"Xen Hypervisor project: " +"http://xen.org/products/xenhyp.html." +msgstr "" + +#: ./doc/config-reference/compute/section_introduction-to-xen.xml237(para) +msgid "" +"XCP project: " +"http://xen.org/products/cloudxen.html." +msgstr "" + +#: ./doc/config-reference/compute/section_introduction-to-xen.xml243(para) +msgid "" +"Further XenServer and OpenStack information: " +"http://wiki.openstack.org/XenServer." +msgstr "" + +#: ./doc/config-reference/compute/section_introduction-to-xen.xml215(para) +msgid "" +"Here are some of the resources available to learn more about Xen: " +"" +msgstr "" + +#: ./doc/config-reference/compute/section_hypervisor_baremetal.xml6(title) +msgid "Bare metal driver" +msgstr "" + +#: ./doc/config-reference/compute/section_hypervisor_baremetal.xml7(para) +msgid "" +"The baremetal driver is a hypervisor driver for OpenStack Nova Compute. " +"Within the OpenStack framework, it has the same role as the drivers for " +"other hypervisors (libvirt, xen, etc), and yet it is presently unique in " +"that the hardware is not virtualized - there is no hypervisor between the " +"tenants and the physical hardware. It exposes hardware through the OpenStack" +" APIs, using pluggable sub-drivers to deliver machine imaging (PXE) and " +"power control (IPMI). With this, provisioning and management of physical " +"hardware is accomplished by using common cloud APIs and tools, such as " +"OpenStack Orchestration or salt-cloud. However, due to this unique " +"situation, using the baremetal driver requires some additional preparation " +"of its environment, the details of which are beyond the scope of this guide." +msgstr "" + +#: ./doc/config-reference/compute/section_hypervisor_baremetal.xml20(para) +msgid "" +"Some OpenStack Compute features are not implemented by the baremetal " +"hypervisor driver. See the hypervisor " +"support matrix for details." +msgstr "" + +#: ./doc/config-reference/compute/section_hypervisor_baremetal.xml24(para) +msgid "" +"For the Baremetal driver to be loaded and function properly, ensure that the" +" following options are set in /etc/nova/nova.conf on " +"your nova-compute hosts." +msgstr "" + +#: ./doc/config-reference/compute/section_hypervisor_baremetal.xml34(para) +msgid "" +"Many configuration options are specific to the Baremetal driver. Also, some " +"additional steps are required, such as building the baremetal deploy " +"ramdisk. See the main wiki page for" +" details and implementation suggestions." +msgstr "" + +#: ./doc/config-reference/compute/section_compute-configure-backing-storage.xml10(title) +msgid "Configure Compute backing storage" +msgstr "" + +#: ./doc/config-reference/compute/section_compute-configure-backing-storage.xml11(para) +msgid "" +"Backing Storage is the storage used to provide the expanded operating system" +" image, and any ephemeral storage. Inside the virtual machine, this is " +"normally presented as two virtual hard disks (for example, /dev/vda and " +"/dev/vdb respectively). However, inside OpenStack, this can be derived from " +"one of three methods: LVM, QCOW or RAW, chosen using the " +"libvirt_images_type option in " +"nova.conf on the compute node." +msgstr "" + +#: ./doc/config-reference/compute/section_compute-configure-backing-storage.xml19(para) +msgid "" +"QCOW is the default backing store. It uses a copy-on-write philosophy to " +"delay allocation of storage until it is actually needed. This means that the" +" space required for the backing of an image can be significantly less on the" +" real disk than what seems available in the virtual machine operating " +"system." +msgstr "" + +#: ./doc/config-reference/compute/section_compute-configure-backing-storage.xml24(para) +msgid "" +"RAW creates files without any sort of file formatting, effectively creating " +"files with the plain binary one would normally see on a real disk. This can " +"increase performance, but means that the entire size of the virtual disk is " +"reserved on the physical disk." +msgstr "" + +#: ./doc/config-reference/compute/section_compute-configure-backing-storage.xml29(para) +msgid "" +"Local LVM" +" volumes can also be used. Set " +"libvirt_images_volume_group=nova_local where " +"nova_local is the name of the LVM group you have created." +msgstr "" + +#: ./doc/config-reference/compute/section_compute-hypervisors.xml10(title) +msgid "Hypervisors" +msgstr "" + +#: ./doc/config-reference/compute/section_compute-hypervisors.xml11(para) +msgid "" +"OpenStack Compute supports many hypervisors, which might make it difficult " +"for you to choose one. Most installations use only one hypervisor. However " +"you can use and to schedule to different hypervisors " +"within the same installation. The following links help you choose a " +"hypervisor. See http://wiki.openstack.org/HypervisorSupportMatrix" +" for a detailed list of features and support across the hypervisors." +msgstr "" + +#: ./doc/config-reference/compute/section_compute-hypervisors.xml22(para) +msgid "The following hypervisors are supported:" +msgstr "" + +#: ./doc/config-reference/compute/section_compute-hypervisors.xml25(para) +msgid "" +"KVM - Kernel-" +"based Virtual Machine. The virtual disk formats that it supports is " +"inherited from QEMU since it uses a modified QEMU program to launch the " +"virtual machine. The supported formats include raw images, the qcow2, and " +"VMware formats." +msgstr "" + +#: ./doc/config-reference/compute/section_compute-hypervisors.xml34(para) +msgid "" +"LXC - Linux Containers " +"(through libvirt), use to run Linux-based virtual machines." +msgstr "" + +#: ./doc/config-reference/compute/section_compute-hypervisors.xml39(para) +msgid "" +"QEMU - Quick EMUlator, " +"generally only used for development purposes." +msgstr "" + +#: ./doc/config-reference/compute/section_compute-hypervisors.xml44(para) +msgid "" +"UML - User " +"Mode Linux, generally only used for development purposes." +msgstr "" + +#: ./doc/config-reference/compute/section_compute-hypervisors.xml50(para) +msgid "" +"VMWare vSphere 4.1 update 1 and newer, runs" +" VMWare-based Linux and Windows images through a connection with a vCenter " +"server or directly with an ESXi host." +msgstr "" + +#: ./doc/config-reference/compute/section_compute-hypervisors.xml58(para) +msgid "" +"Xen - XenServer, Xen Cloud Platform" +" (XCP), use to run Linux or Windows virtual machines. You must install the " +"nova-compute service in a para-" +"virtualized VM." +msgstr "" + +#: ./doc/config-reference/compute/section_compute-hypervisors.xml66(para) +msgid "" +" Hyper-V - Server " +"virtualization with Microsoft's Hyper-V, use to run Windows, Linux, and " +"FreeBSD virtual machines. Runs nova-" +"compute natively on the Windows virtualization platform." +msgstr "" + +#: ./doc/config-reference/compute/section_compute-hypervisors.xml75(para) +msgid "" +" Bare Metal " +"- Not a hypervisor in the traditional sense, this driver provisions physical" +" hardware through pluggable sub-drivers (for example, PXE for image " +"deployment, and IPMI for power management)." +msgstr "" + +#: ./doc/config-reference/compute/section_compute-hypervisors.xml83(para) +msgid "" +"Dockeris an open-source engine " +"which automates the deployment of >applications as highly portable, self-" +"sufficient containers which are >independent of hardware, language, " +"framework, packaging system and hosting >provider." +msgstr "" + +#: ./doc/config-reference/compute/section_compute-hypervisors.xml92(title) +msgid "Hypervisor configuration basics" +msgstr "" + +#: ./doc/config-reference/compute/section_compute-hypervisors.xml93(para) +msgid "" +"The node where the nova-compute " +"service is installed and running is the machine that runs all the virtual " +"machines, referred to as the compute node in this guide." +msgstr "" + +#: ./doc/config-reference/compute/section_compute-hypervisors.xml97(para) +msgid "" +"By default, the selected hypervisor is KVM. To change to another hypervisor," +" change the libvirt_type option in " +"nova.conf and restart the nova-compute service." +msgstr "" + +#: ./doc/config-reference/compute/section_compute-hypervisors.xml103(para) +msgid "" +"Here are the general nova.conf options that are used to" +" configure the compute node's hypervisor. Specific options for particular " +"hypervisors can be found in following sections." +msgstr "" + +#. When image changes, this message will be marked fuzzy or untranslated for +#. you. +#. It doesn't matter what you translate it to: it's not used at all. +#: ./doc/config-reference/compute/section_compute-config-samples.xml44(None) +msgid "" +"@@image: '../../common/figures/SCH_5004_V00_NUAC-" +"Network_mode_KVM_Flat_OpenStack.png'; md5=1e883ef27e5912b5c516d153b8844a28" +msgstr "" + +#. When image changes, this message will be marked fuzzy or untranslated for +#. you. +#. It doesn't matter what you translate it to: it's not used at all. +#: ./doc/config-reference/compute/section_compute-config-samples.xml83(None) +msgid "" +"@@image: '../../common/figures/SCH_5005_V00_NUAC-" +"Network_mode_XEN_Flat_OpenStack.png'; md5=3b151435a0fda3702d4fac5a964fac83" +msgstr "" + +#: ./doc/config-reference/compute/section_compute-config-samples.xml9(title) +msgid "Example nova.conf configuration files" +msgstr "" + +#: ./doc/config-reference/compute/section_compute-config-samples.xml11(para) +msgid "" +"The following sections describe the configuration options in the " +"nova.conf file. You must copy the " +"nova.conf file to each compute node. The sample " +"nova.conf files show examples of specific " +"configurations." +msgstr "" + +#: ./doc/config-reference/compute/section_compute-config-samples.xml17(title) +msgid "Small, private cloud" +msgstr "" + +#: ./doc/config-reference/compute/section_compute-config-samples.xml18(para) +msgid "" +"This example nova.conf file configures a small private " +"cloud with cloud controller services, database server, and messaging server " +"on the same server. In this case, CONTROLLER_IP represents the IP address of" +" a central server, BRIDGE_INTERFACE represents the bridge such as br100, the" +" NETWORK_INTERFACE represents an interface to your VLAN setup, and passwords" +" are represented as DB_PASSWORD_COMPUTE for your Compute (nova) database " +"password, and RABBIT PASSWORD represents the password to your message queue " +"installation." +msgstr "" + +#: ./doc/config-reference/compute/section_compute-config-samples.xml31(title) +#: ./doc/config-reference/compute/section_compute-config-samples.xml38(title) +#: ./doc/config-reference/compute/section_compute-config-samples.xml77(title) +msgid "KVM, Flat, MySQL, and Glance, OpenStack or EC2 API" +msgstr "" + +#: ./doc/config-reference/compute/section_compute-config-samples.xml33(para) +msgid "" +"This example nova.conf file, from an internal Rackspace" +" test system, is used for demonstrations." +msgstr "" + +#: ./doc/config-reference/compute/section_compute-config-samples.xml50(title) +msgid "XenServer, Flat networking, MySQL, and Glance, OpenStack API" +msgstr "" + +#: ./doc/config-reference/compute/section_compute-config-samples.xml52(para) +msgid "" +"This example nova.conf file is from an internal " +"Rackspace test system." +msgstr "" + +#: ./doc/config-reference/compute/section_hypervisor_lxc.xml6(title) +msgid "LXC (Linux containers)" +msgstr "" + +#: ./doc/config-reference/compute/section_hypervisor_lxc.xml7(para) +msgid "" +"LXC (also known as Linux containers) is a virtualization technology that " +"works at the operating system level. This is different from hardware " +"virtualization, the approach used by other hypervisors such as KVM, Xen, and" +" VMWare. LXC (as currently implemented using libvirt in the nova project) is" +" not a secure virtualization technology for multi-tenant environments " +"(specifically, containers may affect resource quotas for other containers " +"hosted on the same machine). Additional containment technologies, such as " +"AppArmor, may be used to provide better isolation between containers, " +"although this is not the case by default. For all these reasons, the choice " +"of this virtualization technology is not recommended in production." +msgstr "" + +#: ./doc/config-reference/compute/section_hypervisor_lxc.xml19(para) +msgid "" +"If your compute hosts do not have hardware support for virtualization, LXC " +"will likely provide better performance than QEMU. In addition, if your " +"guests must access specialized hardware, such as GPUs, this might be easier " +"to achieve with LXC than other hypervisors." +msgstr "" + +#: ./doc/config-reference/compute/section_hypervisor_lxc.xml22(para) +msgid "" +"Some OpenStack Compute features might be missing when running with LXC as " +"the hypervisor. See the hypervisor " +"support matrix for details." +msgstr "" + +#: ./doc/config-reference/compute/section_hypervisor_lxc.xml25(para) +msgid "" +"To enable LXC, ensure the following options are set in " +"/etc/nova/nova.conf on all hosts running the " +"nova-compute " +"service." +msgstr "" + +#: ./doc/config-reference/compute/section_hypervisor_lxc.xml30(para) +msgid "" +"On Ubuntu 12.04, enable LXC support in OpenStack by installing the nova-compute-lxc package." +msgstr "" + +#: ./doc/config-reference/compute/section_compute-configure-db.xml9(title) +msgid "Database configuration" +msgstr "" + +#: ./doc/config-reference/compute/section_compute-configure-db.xml10(para) +msgid "" +"You can configure OpenStack Compute to use any SQLAlchemy-compatible " +"database. The database name is nova. The nova-conductor service is the only service " +"that writes to the database. The other Compute services access the database " +"through the nova-conductor " +"service." +msgstr "" + +#: ./doc/config-reference/compute/section_compute-configure-db.xml17(para) +msgid "" +"To ensure that the database schema is current, run the following command:" +msgstr "" + +#: ./doc/config-reference/compute/section_compute-configure-db.xml19(para) +msgid "" +"If nova-conductor is not used, " +"entries to the database are mostly written by the nova-scheduler service, although all services" +" must be able to update entries in the database." +msgstr "" + +#: ./doc/config-reference/compute/section_compute-configure-db.xml24(para) +msgid "" +"In either case, use these settings to configure the connection string for " +"the nova database." +msgstr "" + +#: ./doc/config-reference/compute/section_compute-options-reference.xml6(title) +#: ./doc/config-reference/block-storage/drivers/xenapi-nfs.xml86(title) +#: ./doc/config-reference/block-storage/drivers/hds-volume-driver.xml309(caption) +msgid "Configuration options" +msgstr "" + +#: ./doc/config-reference/compute/section_compute-options-reference.xml7(para) +msgid "" +"For a complete list of all available configuration options for each " +"OpenStack Compute service, run bin/nova-<servicename> --help." +msgstr "" + +#: ./doc/config-reference/compute/section_compute-configure-ipv6.xml9(title) +msgid "Configure Compute to use IPv6 addresses" +msgstr "" + +#: ./doc/config-reference/compute/section_compute-configure-ipv6.xml10(para) +msgid "" +"You can configure Compute to use both IPv4 and IPv6 addresses for " +"communication by putting it into a IPv4/IPv6 dual stack mode. In IPv4/IPv6 " +"dual stack mode, instances can acquire their IPv6 global unicast address by " +"stateless address auto configuration mechanism [RFC 4862/2462]. IPv4/IPv6 " +"dual stack mode works with VlanManager and " +"FlatDHCPManager networking modes. In " +"VlanManager, different 64bit global routing prefix is " +"used for each project. In FlatDHCPManager, one 64bit " +"global routing prefix is used for all instances." +msgstr "" + +#: ./doc/config-reference/compute/section_compute-configure-ipv6.xml18(para) +msgid "" +"This configuration has been tested with VM images that have IPv6 stateless " +"address auto configuration capability (must use EUI-64 address for stateless" +" address auto configuration), a requirement for any VM you want to run with " +"an IPv6 address. Each node that executes a nova-* service" +" must have python-netaddr and radvd " +"installed." +msgstr "" + +#: ./doc/config-reference/compute/section_compute-configure-ipv6.xml24(para) +msgid "On all nova-nodes, install python-netaddr:" +msgstr "" + +#: ./doc/config-reference/compute/section_compute-configure-ipv6.xml26(para) +msgid "" +"On all nova-network nodes install " +"radvd and configure IPv6 networking:" +msgstr "" + +#: ./doc/config-reference/compute/section_compute-configure-ipv6.xml31(para) +msgid "" +"Edit the nova.conf file on all nodes to set the " +"use_ipv6 configuration option to True. Restart all nova- services." +msgstr "" + +#: ./doc/config-reference/compute/section_compute-configure-ipv6.xml34(para) +msgid "" +"When using the command you can add a fixed range for IPv6 " +"addresses. You must specify public or private after the create parameter." +msgstr "" + +#: ./doc/config-reference/compute/section_compute-configure-ipv6.xml36(replaceable) +msgid "fixed_range_v4" +msgstr "" + +#: ./doc/config-reference/compute/section_compute-configure-ipv6.xml36(replaceable) +msgid "vlan_id" +msgstr "" + +#: ./doc/config-reference/compute/section_compute-configure-ipv6.xml36(replaceable) +msgid "vpn_start" +msgstr "" + +#: ./doc/config-reference/compute/section_compute-configure-ipv6.xml36(replaceable) +msgid "fixed_range_v6" +msgstr "" + +#: ./doc/config-reference/compute/section_compute-configure-ipv6.xml37(para) +msgid "" +"You can set IPv6 global routing prefix by using the " +"--fixed_range_v6 parameter. The default is: " +"fd00::/48. When you use " +"FlatDHCPManager, the command uses the original value of " +"--fixed_range_v6. When you use " +"VlanManager, the command creates prefixes of subnet by " +"incrementing subnet id. Guest VMs uses this prefix for generating their IPv6" +" global unicast address." +msgstr "" + +#: ./doc/config-reference/compute/section_compute-configure-ipv6.xml43(para) +msgid "Here is a usage example for VlanManager:" +msgstr "" + +#: ./doc/config-reference/compute/section_compute-configure-ipv6.xml45(para) +msgid "Here is a usage example for FlatDHCPManager:" +msgstr "" + +#: ./doc/config-reference/compute/section_compute-configure-console.xml7(title) +msgid "Configure remote console access" +msgstr "" + +#. +#: ./doc/config-reference/compute/section_compute-configure-console.xml9(para) +msgid "" +"OpenStack has two main methods for providing a remote console or remote " +"desktop access to guest Virtual Machines. They are VNC, and SPICE HTML5 and " +"can be used either through the OpenStack dashboard and the command line. " +"Best practice is to select one or the other to run." +msgstr "" + +#: ./doc/config-reference/compute/section_hypervisor_kvm.xml6(para) +msgid "KVM is configured as the default hypervisor for Compute." +msgstr "" + +#: ./doc/config-reference/compute/section_hypervisor_kvm.xml8(para) +msgid "" +"This document contains several sections about hypervisor selection. If you " +"are reading this document linearly, you do not want to load the KVM module " +"before you install nova-compute. " +"The nova-compute service depends " +"on qemu-kvm, which installs /lib/udev/rules.d/45-qemu-" +"kvm.rules, which sets the correct permissions on the /dev/kvm " +"device node." +msgstr "" + +#: ./doc/config-reference/compute/section_hypervisor_kvm.xml15(para) +msgid "" +"To enable KVM explicitly, add the following configuration options to the " +"/etc/nova/nova.conf file:" +msgstr "" + +#: ./doc/config-reference/compute/section_hypervisor_kvm.xml19(para) +msgid "" +"The KVM hypervisor supports the following virtual machine image formats:" +msgstr "" + +#: ./doc/config-reference/compute/section_hypervisor_kvm.xml22(para) +#: ./doc/config-reference/compute/section_hypervisor_qemu.xml43(para) +msgid "Raw" +msgstr "" + +#: ./doc/config-reference/compute/section_hypervisor_kvm.xml25(para) +#: ./doc/config-reference/compute/section_hypervisor_qemu.xml46(para) +msgid "QEMU Copy-on-write (qcow2)" +msgstr "" + +#: ./doc/config-reference/compute/section_hypervisor_kvm.xml28(para) +msgid "QED Qemu Enhanced Disk" +msgstr "" + +#: ./doc/config-reference/compute/section_hypervisor_kvm.xml31(para) +#: ./doc/config-reference/compute/section_hypervisor_qemu.xml49(para) +msgid "VMWare virtual machine disk format (vmdk)" +msgstr "" + +#: ./doc/config-reference/compute/section_hypervisor_kvm.xml34(para) +msgid "" +"This section describes how to enable KVM on your system. For more " +"information, see the following distribution-specific documentation:" +msgstr "" + +#: ./doc/config-reference/compute/section_hypervisor_kvm.xml38(para) +msgid "" +"Fedora:" +" Getting started with virtualization from the Fedora project wiki." +msgstr "" + +#: ./doc/config-reference/compute/section_hypervisor_kvm.xml44(para) +msgid "" +"Ubuntu: " +"KVM/Installation from the Community Ubuntu documentation." +msgstr "" + +#: ./doc/config-reference/compute/section_hypervisor_kvm.xml48(para) +msgid "" +"Debian: " +"Virtualization with KVM from the Debian handbook." +msgstr "" + +#: ./doc/config-reference/compute/section_hypervisor_kvm.xml53(para) +msgid "" +"RHEL:" +" Installing virtualization packages on an existing Red Hat Enterprise Linux " +"system from the Red Hat Enterprise Linux Virtualization " +"Host Configuration and Guest Installation Guide." +msgstr "" + +#: ./doc/config-reference/compute/section_hypervisor_kvm.xml60(para) +msgid "" +"openSUSE: Installing " +"KVM from the openSUSE Virtualization with KVM manual." +msgstr "" + +#: ./doc/config-reference/compute/section_hypervisor_kvm.xml66(para) +msgid "" +"SLES: " +"Installing KVM from the SUSE Linux Enterprise Server Virtualization " +"with KVM manual." +msgstr "" + +#: ./doc/config-reference/compute/section_hypervisor_kvm.xml76(title) +msgid "Specify the CPU model of KVM guests" +msgstr "" + +#: ./doc/config-reference/compute/section_hypervisor_kvm.xml77(para) +msgid "" +"The Compute service enables you to control the guest CPU model that is " +"exposed to KVM virtual machines. Use cases include:" +msgstr "" + +#: ./doc/config-reference/compute/section_hypervisor_kvm.xml81(para) +msgid "" +"To maximize performance of virtual machines by exposing new host CPU " +"features to the guest" +msgstr "" + +#: ./doc/config-reference/compute/section_hypervisor_kvm.xml85(para) +msgid "" +"To ensure a consistent default CPU across all machines, removing reliance of" +" variable QEMU defaults" +msgstr "" + +#: ./doc/config-reference/compute/section_hypervisor_kvm.xml89(para) +msgid "" +"In libvirt, the CPU is specified by providing a base CPU model name (which " +"is a shorthand for a set of feature flags), a set of additional feature " +"flags, and the topology (sockets/cores/threads). The libvirt KVM driver " +"provides a number of standard CPU model names. These models are defined in " +"the /usr/share/libvirt/cpu_map.xml file. Check this " +"file to determine which models are supported by your local installation." +msgstr "" + +#: ./doc/config-reference/compute/section_hypervisor_kvm.xml95(para) +msgid "" +"Two Compute configuration options define which type of CPU model is exposed " +"to the hypervisor when using KVM: libvirt_cpu_mode and " +"libvirt_cpu_model." +msgstr "" + +#: ./doc/config-reference/compute/section_hypervisor_kvm.xml98(para) +msgid "" +"The libvirt_cpu_mode option can take one of the following" +" values: none, host-passthrough, " +"host-model, and custom." +msgstr "" + +#: ./doc/config-reference/compute/section_hypervisor_kvm.xml102(title) +msgid "Host model (default for KVM & QEMU)" +msgstr "" + +#: ./doc/config-reference/compute/section_hypervisor_kvm.xml103(para) +msgid "" +"If your nova.conf file contains " +"libvirt_cpu_mode=host-model, libvirt identifies the CPU " +"model in /usr/share/libvirt/cpu_map.xml file that most " +"closely matches the host, and requests additional CPU flags to complete the " +"match. This configuration provides the maximum functionality and performance" +" and maintains good reliability and compatibility if the guest is migrated " +"to another host with slightly different host CPUs." +msgstr "" + +#: ./doc/config-reference/compute/section_hypervisor_kvm.xml112(title) +msgid "Host pass through" +msgstr "" + +#: ./doc/config-reference/compute/section_hypervisor_kvm.xml113(para) +msgid "" +"If your nova.conf file contains " +"libvirt_cpu_mode=host-passthrough, libvirt tells KVM to " +"pass through the host CPU with no modifications. The difference to host-" +"model, instead of just matching feature flags, every last detail of the host" +" CPU is matched. This gives absolutely best performance, and can be " +"important to some apps which check low level CPU details, but it comes at a " +"cost with respect to migration: the guest can only be migrated to an exactly" +" matching host CPU." +msgstr "" + +#: ./doc/config-reference/compute/section_hypervisor_kvm.xml122(title) +msgid "Custom" +msgstr "" + +#: ./doc/config-reference/compute/section_hypervisor_kvm.xml123(para) +msgid "" +"If your nova.conf file contains " +"libvirt_cpu_mode=custom, you can explicitly specify one " +"of the supported named model using the libvirt_cpu_model configuration " +"option. For example, to configure the KVM guests to expose Nehalem CPUs, " +"your nova.conf file should contain:" +msgstr "" + +#: ./doc/config-reference/compute/section_hypervisor_kvm.xml132(title) +msgid "" +"None (default for all libvirt-driven hypervisors other than KVM & QEMU)" +msgstr "" + +#: ./doc/config-reference/compute/section_hypervisor_kvm.xml134(para) +msgid "" +"If your nova.conf file contains " +"libvirt_cpu_mode=none, libvirt does not specify a CPU " +"model. Instead, the hypervisor chooses the default model. This setting is " +"equivalent to the Compute service behavior prior to the Folsom release." +msgstr "" + +#: ./doc/config-reference/compute/section_hypervisor_kvm.xml141(title) +msgid "Guest agent support" +msgstr "" + +#: ./doc/config-reference/compute/section_hypervisor_kvm.xml142(para) +msgid "" +"With the Havana release, support for guest agents was added, allowing " +"optional access between compute nods and guests through a socket, using the " +"qmp protocol." +msgstr "" + +#: ./doc/config-reference/compute/section_hypervisor_kvm.xml144(para) +msgid "" +"To enable this feature, you must set " +"hw_qemu_guest_agent=yes as a metadata parameter on the " +"image you wish to use to create guest-agent-capable instances from. You can " +"explicitly disable the feature by setting " +"hw_qemu_guest_agent=no in the image metadata." +msgstr "" + +#: ./doc/config-reference/compute/section_hypervisor_kvm.xml150(title) +msgid "KVM performance tweaks" +msgstr "" + +#: ./doc/config-reference/compute/section_hypervisor_kvm.xml151(para) +msgid "" +"The VHostNet " +"kernel module improves network performance. To load the kernel module, run " +"the following command as root:" +msgstr "" + +#: ./doc/config-reference/compute/section_hypervisor_kvm.xml157(title) +msgid "Troubleshoot KVM" +msgstr "" + +#: ./doc/config-reference/compute/section_hypervisor_kvm.xml158(para) +msgid "" +"Trying to launch a new virtual machine instance fails with the " +"ERRORstate, and the following error appears in the " +"/var/log/nova/nova-compute.log file:" +msgstr "" + +#: ./doc/config-reference/compute/section_hypervisor_kvm.xml162(para) +msgid "This message indicates that the KVM kernel modules were not loaded." +msgstr "" + +#: ./doc/config-reference/compute/section_hypervisor_kvm.xml163(para) +msgid "" +"If you cannot start VMs after installation without rebooting, the " +"permissions might not be correct. This can happen if you load the KVM module" +" before you install nova-compute." +" To check whether the group is set to kvm, run:" +msgstr "" + +#: ./doc/config-reference/compute/section_hypervisor_kvm.xml168(para) +msgid "If it is not set to kvm, run:" +msgstr "" + +#: ./doc/config-reference/compute/section_hypervisor_docker.xml6(title) +msgid "Docker driver" +msgstr "" + +#: ./doc/config-reference/compute/section_hypervisor_docker.xml7(para) +msgid "" +"The Docker driver is a hypervisor driver for OpenStack Compute, introduced " +"with the Havana release. Docker is an open-source engine which automates the" +" deployment of applications as highly portable, self-sufficient containers " +"which are independent of hardware, language, framework, packaging system and" +" hosting provider. Docker extends LXC with a high level API providing a " +"lightweight virtualization solution that runs processes in isolation. It " +"provides a way to automate software deployment in a secure and repeatable " +"environment. A standard container in Docker contains a software component " +"along with all of its dependencies - binaries, libraries, configuration " +"files, scripts, virtualenvs, jars, gems and tarballs. Docker can be run on " +"any x86_64 Linux kernel that supports cgroups and aufs. Docker is a way of " +"managing LXC containers on a single machine. However used behind OpenStack " +"Compute makes Docker much more powerful since it is then possible to manage " +"several hosts which will then manage hundreds of containers. The current " +"Docker project aims for full OpenStack compatibility. Containers don't aim " +"to be a replacement for VMs, they are just complementary in the sense that " +"they are better for specific use cases. Compute's support for VMs is " +"currently advanced thanks to the variety of hypervisors running VMs. However" +" it's not the case for containers even though libvirt/LXC is a good starting" +" point. Docker aims to go the second level of integration." +msgstr "" + +#: ./doc/config-reference/compute/section_hypervisor_docker.xml27(para) +msgid "" +"Some OpenStack Compute features are not implemented by the docker driver. " +"See the " +"hypervisor support matrix for details." +msgstr "" + +#: ./doc/config-reference/compute/section_hypervisor_docker.xml33(para) +msgid "" +"To enable Docker, ensure the following options are set in " +"/etc/nova/nova-compute.conf on all hosts running the " +"nova-compute service. " +"" +msgstr "" + +#: ./doc/config-reference/compute/section_hypervisor_docker.xml37(para) +msgid "" +"Glance also needs to be configured to support the Docker container format, " +"in /etc/glance-api.conf: " +msgstr "" + +#: ./doc/config-reference/compute/section_compute-configure-service-groups.xml15(title) +msgid "Configuring Compute Service Groups" +msgstr "" + +#: ./doc/config-reference/compute/section_compute-configure-service-groups.xml16(para) +msgid "" +"To effectively manage and utilize compute nodes, the Compute service must " +"know their statuses. For example, when a user launches a new VM, the Compute" +" scheduler should send the request to a live node (with enough capacity too," +" of course). From the Grizzly release and later, the Compute service queries" +" the ServiceGroup API to get the node liveness information." +msgstr "" + +#: ./doc/config-reference/compute/section_compute-configure-service-groups.xml21(para) +msgid "" +"When a compute worker (running the nova-" +"compute daemon) starts, it calls the join API to join the " +"compute group, so that every service that is interested in the information " +"(for example, the scheduler) can query the group membership or the status of" +" a particular node. Internally, the ServiceGroup client driver automatically" +" updates the compute worker status." +msgstr "" + +#: ./doc/config-reference/compute/section_compute-configure-service-groups.xml27(para) +msgid "" +"The following drivers are implemented: database and ZooKeeper. Further " +"drivers are in review or development, such as memcache." +msgstr "" + +#: ./doc/config-reference/compute/section_compute-configure-service-groups.xml31(title) +msgid "Database ServiceGroup driver" +msgstr "" + +#: ./doc/config-reference/compute/section_compute-configure-service-groups.xml32(para) +msgid "" +"Compute uses the database driver, which is the default driver, to track node" +" liveness. In a compute worker, this driver periodically sends a " +" command to the database, saying I'm OK with " +"a timestamp. A pre-defined timeout (service_down_time) " +"determines if a node is dead." +msgstr "" + +#: ./doc/config-reference/compute/section_compute-configure-service-groups.xml38(para) +msgid "" +"The driver has limitations, which may or may not be an issue for you, " +"depending on your setup. The more compute worker nodes that you have, the " +"more pressure you put on the database. By default, the timeout is 60 seconds" +" so it might take some time to detect node failures. You could reduce the " +"timeout value, but you must also make the DB update more frequently, which " +"again increases the DB workload." +msgstr "" + +#: ./doc/config-reference/compute/section_compute-configure-service-groups.xml44(para) +msgid "" +"Fundamentally, the data that describes whether the node is alive is " +"\"transient\" — After a few seconds, this data is obsolete. Other data in " +"the database is persistent, such as the entries that describe who owns which" +" VMs. However, because this data is stored in the same database, is treated " +"the same way. The ServiceGroup abstraction aims to treat them separately." +msgstr "" + +#: ./doc/config-reference/compute/section_compute-configure-service-groups.xml53(title) +msgid "ZooKeeper ServiceGroup driver" +msgstr "" + +#: ./doc/config-reference/compute/section_compute-configure-service-groups.xml54(para) +msgid "" +"The ZooKeeper ServiceGroup driver works by using ZooKeeper ephemeral nodes. " +"ZooKeeper, in contrast to databases, is a distributed system. Its load is " +"divided among several servers. At a compute worker node, after establishing " +"a ZooKeeper session, it creates an ephemeral znode in the group directory. " +"Ephemeral znodes have the same lifespan as the session. If the worker node " +"or the nova-compute daemon " +"crashes, or a network partition is in place between the worker and the " +"ZooKeeper server quorums, the ephemeral znodes are removed automatically. " +"The driver gets the group membership by running the command" +" in the group directory." +msgstr "" + +#: ./doc/config-reference/compute/section_compute-configure-service-groups.xml64(para) +msgid "" +"To use the ZooKeeper driver, you must install ZooKeeper servers and client " +"libraries. Setting up ZooKeeper servers is outside the scope of this " +"article. For the rest of the article, assume these servers are installed, " +"and their addresses and ports are 192.168.2.1:2181, " +"192.168.2.2:2181, 192.168.2.3:2181." +msgstr "" + +#: ./doc/config-reference/compute/section_compute-configure-service-groups.xml71(para) +msgid "" +"To use ZooKeeper, you must install client-side Python libraries on every " +"nova node: python-zookeeper – the official Zookeeper " +"Python binding and evzookeeper – the library to make the " +"binding work with the eventlet threading model." +msgstr "" + +#: ./doc/config-reference/compute/section_compute-configure-service-groups.xml77(para) +msgid "" +"The relevant configuration snippet in the " +"/etc/nova/nova.conf file on every node is:" +msgstr "" + +#: ./doc/config-reference/compute/section_compute-conductor.xml7(title) +msgid "Conductor" +msgstr "" + +#: ./doc/config-reference/compute/section_compute-conductor.xml8(para) +msgid "" +"The nova-conductor service " +"enables OpenStack to function without compute nodes accessing the database. " +"Conceptually, it implements a new layer on top of nova-compute. It should not be deployed on " +"compute nodes, or else the security benefits of removing database access " +"from nova-compute are negated. " +"Just like other nova services such as nova-" +"api or nova-scheduler, it can be scaled horizontally. You can " +"run multiple instances of nova-" +"conductor on different machines as needed for scaling purposes." +msgstr "" + +#: ./doc/config-reference/compute/section_compute-conductor.xml21(para) +msgid "" +"In the Grizzly release, the methods exposed by nova-conductor are relatively simple methods used by " +"nova-compute to offload its " +"database operations. Places where nova-" +"compute previously performed database access are now talking to" +" nova-conductor. However, we have" +" plans in the medium to long term to move more and more of what is currently" +" in nova-compute up to the " +"nova-conductor layer. The compute" +" service will start to look like a less intelligent slave service to " +"nova-conductor. The conductor " +"service will implement long running complex operations, ensuring forward " +"progress and graceful error handling. This will be especially beneficial for" +" operations that cross multiple compute nodes, such as migrations or " +"resizes." +msgstr "" + +#: ./doc/config-reference/compute/section_nova-conf.xml6(title) +msgid "Overview of nova.conf" +msgstr "" + +#: ./doc/config-reference/compute/section_nova-conf.xml7(para) +msgid "" +"The nova.conf configuration file is an INI file format file " +"that specifies options as key=value pairs, which are " +"grouped into sections. The DEFAULT section contains most " +"of the configuration options. For example:" +msgstr "" + +#: ./doc/config-reference/compute/section_nova-conf.xml19(para) +msgid "" +"You can use a particular configuration option file by using the " +"option (nova.conf) parameter when " +"you run one of the nova-* services. This parameter " +"inserts configuration option definitions from the specified configuration " +"file name, which might be useful for debugging or performance tuning." +msgstr "" + +#: ./doc/config-reference/compute/section_nova-conf.xml25(para) +msgid "" +"To place comments in the nova.conf file, start a new " +"line that begins with the pound (#) character. For a list" +" of configuration options, see the tables in this guide." +msgstr "" + +#: ./doc/config-reference/compute/section_nova-conf.xml29(para) +msgid "" +"To learn more about the nova.conf configuration file, " +"review these general purpose configuration options." +msgstr "" + +#: ./doc/config-reference/compute/section_nova-conf.xml34(title) +msgid "Types of configuration options" +msgstr "" + +#: ./doc/config-reference/compute/section_nova-conf.xml35(para) +msgid "" +"Each configuration option has an associated data type. The supported data " +"types for configuration options are:" +msgstr "" + +#: ./doc/config-reference/compute/section_nova-conf.xml40(term) +msgid "BoolOpt" +msgstr "" + +#: ./doc/config-reference/compute/section_nova-conf.xml42(para) +msgid "" +"Boolean option. Value must be either true or " +"false . Example:" +msgstr "" + +#: ./doc/config-reference/compute/section_nova-conf.xml49(term) +msgid "StrOpt" +msgstr "" + +#: ./doc/config-reference/compute/section_nova-conf.xml51(para) +msgid "String option. Value is an arbitrary string. Example:" +msgstr "" + +#: ./doc/config-reference/compute/section_nova-conf.xml56(term) +msgid "IntOption" +msgstr "" + +#: ./doc/config-reference/compute/section_nova-conf.xml58(para) +msgid "Integer option. Value must be an integer. Example: " +msgstr "" + +#: ./doc/config-reference/compute/section_nova-conf.xml64(term) +msgid "MultiStrOpt" +msgstr "" + +#: ./doc/config-reference/compute/section_nova-conf.xml66(para) +msgid "" +"String option. Same as StrOpt, except that it can be declared multiple times" +" to indicate multiple values. Example:" +msgstr "" + +#: ./doc/config-reference/compute/section_nova-conf.xml74(term) +msgid "ListOpt" +msgstr "" + +#: ./doc/config-reference/compute/section_nova-conf.xml76(para) +msgid "" +"List option. Value is a list of arbitrary strings separated by commas. " +"Example:" +msgstr "" + +#: ./doc/config-reference/compute/section_nova-conf.xml82(term) +msgid "FloatOpt" +msgstr "" + +#: ./doc/config-reference/compute/section_nova-conf.xml84(para) +msgid "Floating-point option. Value must be a floating-point number. Example:" +msgstr "" + +#: ./doc/config-reference/compute/section_nova-conf.xml91(para) +msgid "Do not specify quotes around Nova options." +msgstr "" + +#: ./doc/config-reference/compute/section_nova-conf.xml95(title) +msgid "Sections" +msgstr "" + +#: ./doc/config-reference/compute/section_nova-conf.xml99(literal) +msgid "[DEFAULT]" +msgstr "" + +#: ./doc/config-reference/compute/section_nova-conf.xml101(para) +msgid "" +"Contains most configuration options. If the documentation for a " +"configuration option does not specify its section, assume that it appears in" +" this section." +msgstr "" + +#: ./doc/config-reference/compute/section_nova-conf.xml109(literal) +msgid "[cells]" +msgstr "" + +#: ./doc/config-reference/compute/section_nova-conf.xml111(para) +msgid "" +"Configures cells functionality. For details, see the Cells section ()." +msgstr "" + +#: ./doc/config-reference/compute/section_nova-conf.xml119(literal) +msgid "[baremetal]" +msgstr "" + +#: ./doc/config-reference/compute/section_nova-conf.xml121(para) +msgid "Configures the baremetal hypervisor driver." +msgstr "" + +#: ./doc/config-reference/compute/section_nova-conf.xml126(literal) +msgid "[conductor]" +msgstr "" + +#: ./doc/config-reference/compute/section_nova-conf.xml128(para) +msgid "" +"Configures the nova-conductor " +"service." +msgstr "" + +#: ./doc/config-reference/compute/section_nova-conf.xml135(literal) +msgid "[trusted_computing]" +msgstr "" + +#: ./doc/config-reference/compute/section_nova-conf.xml137(para) +msgid "" +"Configures the trusted computing pools functionality and how to connect to a" +" remote attestation service." +msgstr "" + +#: ./doc/config-reference/compute/section_nova-conf.xml96(para) +msgid "" +"Configuration options are grouped by section. The Compute configuration file" +" supports the following sections:" +msgstr "" + +#: ./doc/config-reference/compute/section_nova-conf.xml146(title) +msgid "Variable substitution" +msgstr "" + +#: ./doc/config-reference/compute/section_nova-conf.xml147(para) +msgid "" +"The configuration file supports variable substitution. After you set a " +"configuration option, it can be referenced in later configuration values " +"when you precede it with $. This example defines " +"my_ip and then uses $my_ip as a " +"variable:" +msgstr "" + +#: ./doc/config-reference/compute/section_nova-conf.xml156(para) +msgid "" +"If a value must contain the $ character, escape it with " +"$$. For example, if your LDAP DNS password is " +"$xkj432, specify it, as follows:" +msgstr "" + +#: ./doc/config-reference/compute/section_nova-conf.xml161(para) +msgid "" +"The Compute code uses the Python " +"string.Template.safe_substitute() method to implement " +"variable substitution. For more details on how variable substitution is " +"resolved, see http://docs.python.org/2/library/string.html#template-" +"strings and http://www.python.org/dev/peps/pep-0292/." +msgstr "" + +#: ./doc/config-reference/compute/section_nova-conf.xml173(title) +msgid "Whitespace" +msgstr "" + +#: ./doc/config-reference/compute/section_nova-conf.xml174(para) +msgid "" +"To include whitespace in a configuration value, use a quoted string. For " +"example:" +msgstr "" + +#: ./doc/config-reference/compute/section_nova-conf.xml179(title) +msgid "Define an alternate location for nova.conf" +msgstr "" + +#: ./doc/config-reference/compute/section_nova-conf.xml180(para) +msgid "" +"All nova-* services and the " +" command-line client load the configuration file. To define " +"an alternate location for the configuration file, pass the --config-file /path/to/nova.conf " +"parameter when you start a nova-*" +" service or call a command." +msgstr "" + +#: ./doc/config-reference/compute/section_hypervisor_hyper-v.xml6(title) +msgid "Hyper-V virtualization platform" +msgstr "" + +#: ./doc/config-reference/compute/section_hypervisor_hyper-v.xml15(emphasis) +msgid "Windows Server 2008r2" +msgstr "" + +#: ./doc/config-reference/compute/section_hypervisor_hyper-v.xml16(para) +msgid "" +"Both Server and Server Core with the Hyper-V role enabled (Shared Nothing " +"Live migration is not supported using 2008r2)" +msgstr "" + +#: ./doc/config-reference/compute/section_hypervisor_hyper-v.xml20(emphasis) +msgid "Windows Server 2012" +msgstr "" + +#: ./doc/config-reference/compute/section_hypervisor_hyper-v.xml21(para) +msgid "Server and Core (with the Hyper-V role enabled), and Hyper-V Server" +msgstr "" + +#: ./doc/config-reference/compute/section_hypervisor_hyper-v.xml7(para) +msgid "" +"It is possible to use Hyper-V as a compute node within an OpenStack " +"Deployment. The nova-compute " +"service runs as \"openstack-compute,\" a 32-bit service directly upon the " +"Windows platform with the Hyper-V role enabled. The necessary Python " +"components as well as the nova-" +"compute service are installed directly onto the Windows " +"platform. Windows Clustering Services are not needed for functionality " +"within the OpenStack infrastructure. The use of the Windows Server 2012 " +"platform is recommend for the best experience and is the platform for active" +" development. The following Windows platforms have been tested as compute " +"nodes:" +msgstr "" + +#: ./doc/config-reference/compute/section_hypervisor_hyper-v.xml26(title) +msgid "Hyper-V configuration" +msgstr "" + +#: ./doc/config-reference/compute/section_hypervisor_hyper-v.xml27(para) +msgid "" +"The following sections discuss how to prepare the Windows Hyper-V node for " +"operation as an OpenStack Compute node. Unless stated otherwise, any " +"configuration information should work for both the Windows 2008r2 and 2012 " +"platforms." +msgstr "" + +#: ./doc/config-reference/compute/section_hypervisor_hyper-v.xml30(emphasis) +msgid "Local Storage Considerations" +msgstr "" + +#: ./doc/config-reference/compute/section_hypervisor_hyper-v.xml31(para) +msgid "" +"The Hyper-V compute node needs to have ample storage for storing the virtual" +" machine images running on the compute nodes. You may use a single volume " +"for all, or partition it into an OS volume and VM volume. It is up to the " +"individual deploying to decide." +msgstr "" + +#: ./doc/config-reference/compute/section_hypervisor_hyper-v.xml37(title) +msgid "Configure NTP" +msgstr "" + +#: ./doc/config-reference/compute/section_hypervisor_hyper-v.xml38(para) +msgid "" +"Network time services must be configured to ensure proper operation of the " +"Hyper-V compute node. To set network time on your Hyper-V host you must run " +"the following commands:" +msgstr "" + +#: ./doc/config-reference/compute/section_hypervisor_hyper-v.xml52(title) +msgid "Configure Hyper-V virtual switching" +msgstr "" + +#: ./doc/config-reference/compute/section_hypervisor_hyper-v.xml53(para) +msgid "" +"Information regarding the Hyper-V virtual Switch can be located here: http://technet.microsoft.com/en-" +"us/library/hh831823.aspx" +msgstr "" + +#: ./doc/config-reference/compute/section_hypervisor_hyper-v.xml57(para) +msgid "" +"To quickly enable an interface to be used as a Virtual Interface the " +"following PowerShell may be used:" +msgstr "" + +#: ./doc/config-reference/compute/section_hypervisor_hyper-v.xml67(title) +msgid "Enable iSCSI initiator service" +msgstr "" + +#: ./doc/config-reference/compute/section_hypervisor_hyper-v.xml68(para) +msgid "" +"To prepare the Hyper-V node to be able to attach to volumes provided by " +"cinder you must first make sure the Windows iSCSI initiator service is " +"running and started automatically." +msgstr "" + +#: ./doc/config-reference/compute/section_hypervisor_hyper-v.xml79(title) +msgid "Configure shared nothing live migration" +msgstr "" + +#: ./doc/config-reference/compute/section_hypervisor_hyper-v.xml80(para) +msgid "" +"Detailed information on the configuration of live migration can be found " +"here: http://technet.microsoft.com/en-" +"us/library/jj134199.aspx" +msgstr "" + +#: ./doc/config-reference/compute/section_hypervisor_hyper-v.xml83(para) +msgid "The following outlines the steps of shared nothing live migration." +msgstr "" + +#: ./doc/config-reference/compute/section_hypervisor_hyper-v.xml86(para) +msgid "" +"The target hosts ensures that live migration is enabled and properly " +"configured in Hyper-V." +msgstr "" + +#: ./doc/config-reference/compute/section_hypervisor_hyper-v.xml90(para) +msgid "" +"The target hosts checks if the image to be migrated requires a base VHD and " +"pulls it from Glance if not already available on the target host." +msgstr "" + +#: ./doc/config-reference/compute/section_hypervisor_hyper-v.xml94(para) +msgid "" +"The source hosts ensures that live migration is enabled and properly " +"configured in Hyper-V." +msgstr "" + +#: ./doc/config-reference/compute/section_hypervisor_hyper-v.xml98(para) +msgid "The source hosts initiates a Hyper-V live migration." +msgstr "" + +#: ./doc/config-reference/compute/section_hypervisor_hyper-v.xml101(para) +msgid "" +"The source hosts communicates to the manager the outcome of the operation." +msgstr "" + +#: ./doc/config-reference/compute/section_hypervisor_hyper-v.xml109(literal) +msgid "instances_shared_storage=False" +msgstr "" + +#: ./doc/config-reference/compute/section_hypervisor_hyper-v.xml110(para) +msgid "" +"This needed to support \"shared nothing\" Hyper-V live migrations. It is " +"used in nova/compute/manager.py" +msgstr "" + +#: ./doc/config-reference/compute/section_hypervisor_hyper-v.xml114(literal) +msgid "limit_cpu_features=True" +msgstr "" + +#: ./doc/config-reference/compute/section_hypervisor_hyper-v.xml115(para) +msgid "" +"This flag is needed to support live migration to hosts with different CPU " +"features. This flag is checked during instance creation in order to limit " +"the CPU features used by the VM." +msgstr "" + +#: ./doc/config-reference/compute/section_hypervisor_hyper-v.xml121(literal) +msgid "instances_path=DRIVELETTER:\\PATH\\TO\\YOUR\\INSTANCES" +msgstr "" + +#: ./doc/config-reference/compute/section_hypervisor_hyper-v.xml105(para) +msgid "" +"The following two configuration options/flags are needed in order to support" +" Hyper-V live migration and must be added to your " +"nova.conf on the Hyper-V compute node:" +msgstr "" + +#: ./doc/config-reference/compute/section_hypervisor_hyper-v.xml125(para) +msgid "Additional Requirements:" +msgstr "" + +#: ./doc/config-reference/compute/section_hypervisor_hyper-v.xml128(para) +msgid "Hyper-V 2012 RC or Windows Server 2012 RC with Hyper-V role enabled" +msgstr "" + +#: ./doc/config-reference/compute/section_hypervisor_hyper-v.xml131(para) +msgid "" +"A Windows domain controller with the Hyper-V compute nodes as domain members" +msgstr "" + +#: ./doc/config-reference/compute/section_hypervisor_hyper-v.xml135(para) +msgid "" +"The instances_path command line option/flag needs to be the same on all " +"hosts" +msgstr "" + +#: ./doc/config-reference/compute/section_hypervisor_hyper-v.xml139(para) +msgid "" +"The openstack-compute service deployed with the setup must run with domain " +"credentials. You can set the service credentials with:" +msgstr "" + +#: ./doc/config-reference/compute/section_hypervisor_hyper-v.xml145(emphasis) +msgid "How to setup live migration on Hyper-V" +msgstr "" + +#: ./doc/config-reference/compute/section_hypervisor_hyper-v.xml146(para) +msgid "" +"To enable shared nothing live migration run the 3 PowerShell instructions " +"below on each Hyper-V host:" +msgstr "" + +#: ./doc/config-reference/compute/section_hypervisor_hyper-v.xml152(replaceable) +#: ./doc/config-reference/compute/section_hypervisor_hyper-v.xml337(replaceable) +#: ./doc/config-reference/compute/section_hypervisor_hyper-v.xml338(replaceable) +#: ./doc/config-reference/compute/section_hypervisor_hyper-v.xml345(replaceable) +msgid "IP_ADDRESS" +msgstr "" + +#: ./doc/config-reference/compute/section_hypervisor_hyper-v.xml158(para) +msgid "" +"Please replace the IP_ADDRESS with the address of the interface which will " +"provide the virtual switching for nova-network." +msgstr "" + +#: ./doc/config-reference/compute/section_hypervisor_hyper-v.xml161(emphasis) +msgid "Additional Reading" +msgstr "" + +#: ./doc/config-reference/compute/section_hypervisor_hyper-v.xml162(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.xml166(link) +msgid "" +"http://ariessysadmin.blogspot.ro/2012/04/hyper-v-live-migration-of-" +"windows.html" +msgstr "" + +#: ./doc/config-reference/compute/section_hypervisor_hyper-v.xml170(title) +msgid "Python Requirements" +msgstr "" + +#: ./doc/config-reference/compute/section_hypervisor_hyper-v.xml171(emphasis) +msgid "Python" +msgstr "" + +#: ./doc/config-reference/compute/section_hypervisor_hyper-v.xml177(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.xml181(para) +msgid "Install the MSI accepting the default options." +msgstr "" + +#: ./doc/config-reference/compute/section_hypervisor_hyper-v.xml184(para) +msgid "The installation will put python in C:/python27." +msgstr "" + +#: ./doc/config-reference/compute/section_hypervisor_hyper-v.xml172(para) +msgid "" +"Python 2.7.3 must be installed prior to installing the OpenStack Compute " +"Driver on the Hyper-V server. Download and then install the MSI for windows " +"here:" +msgstr "" + +#: ./doc/config-reference/compute/section_hypervisor_hyper-v.xml188(emphasis) +msgid "Setuptools" +msgstr "" + +#: ./doc/config-reference/compute/section_hypervisor_hyper-v.xml189(para) +msgid "" +"You will require pip to install the necessary python module dependencies. " +"The installer will install under the C:\\python27 directory structure. " +"Setuptools for Python 2.7 for Windows can be download from here:" +msgstr "" + +#: ./doc/config-reference/compute/section_hypervisor_hyper-v.xml194(link) +msgid "" +"http://pypi.python.org/packages/2.7/s/setuptools/setuptools-0.6c11.win32-py2.7.exe" +msgstr "" + +#: ./doc/config-reference/compute/section_hypervisor_hyper-v.xml197(emphasis) +msgid "Python Dependencies" +msgstr "" + +#: ./doc/config-reference/compute/section_hypervisor_hyper-v.xml198(para) +msgid "" +"You must download and manually install the following packages on the Compute" +" node:" +msgstr "" + +#: ./doc/config-reference/compute/section_hypervisor_hyper-v.xml202(emphasis) +msgid "MySQL-python" +msgstr "" + +#: ./doc/config-reference/compute/section_hypervisor_hyper-v.xml205(link) +msgid "http://codegood.com/download/10/" +msgstr "" + +#: ./doc/config-reference/compute/section_hypervisor_hyper-v.xml209(emphasis) +msgid "pywin32" +msgstr "" + +#: ./doc/config-reference/compute/section_hypervisor_hyper-v.xml210(para) +msgid "Download and run the installer from the following location" +msgstr "" + +#: ./doc/config-reference/compute/section_hypervisor_hyper-v.xml214(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.xml218(emphasis) +msgid "greenlet" +msgstr "" + +#: ./doc/config-reference/compute/section_hypervisor_hyper-v.xml219(para) +msgid "Select the link below:" +msgstr "" + +#: ./doc/config-reference/compute/section_hypervisor_hyper-v.xml221(link) +msgid "http://www.lfd.uci.edu/~gohlke/pythonlibs/" +msgstr "" + +#: ./doc/config-reference/compute/section_hypervisor_hyper-v.xml222(para) +msgid "" +"You must scroll to the greenlet section for the following file: " +"greenlet-0.4.0.win32-py2.7.‌exe" +msgstr "" + +#: ./doc/config-reference/compute/section_hypervisor_hyper-v.xml224(para) +msgid "" +"Click on the file, to initiate the download. Once the download is complete, " +"run the installer." +msgstr "" + +#: ./doc/config-reference/compute/section_hypervisor_hyper-v.xml228(para) +msgid "" +"You must install the following Python packages through or " +". Run the following replacing PACKAGENAME with the following" +" packages:" +msgstr "" + +#: ./doc/config-reference/compute/section_hypervisor_hyper-v.xml231(replaceable) +msgid "PACKAGE_NAME" +msgstr "" + +#: ./doc/config-reference/compute/section_hypervisor_hyper-v.xml235(para) +msgid "amqplib" +msgstr "" + +#: ./doc/config-reference/compute/section_hypervisor_hyper-v.xml238(para) +msgid "anyjson" +msgstr "" + +#: ./doc/config-reference/compute/section_hypervisor_hyper-v.xml241(para) +msgid "distribute" +msgstr "" + +#: ./doc/config-reference/compute/section_hypervisor_hyper-v.xml244(para) +msgid "eventlet" +msgstr "" + +#: ./doc/config-reference/compute/section_hypervisor_hyper-v.xml247(para) +msgid "httplib2" +msgstr "" + +#: ./doc/config-reference/compute/section_hypervisor_hyper-v.xml250(para) +msgid "iso8601" +msgstr "" + +#: ./doc/config-reference/compute/section_hypervisor_hyper-v.xml253(para) +msgid "jsonschema" +msgstr "" + +#: ./doc/config-reference/compute/section_hypervisor_hyper-v.xml256(para) +msgid "kombu" +msgstr "" + +#: ./doc/config-reference/compute/section_hypervisor_hyper-v.xml259(para) +msgid "netaddr" +msgstr "" + +#: ./doc/config-reference/compute/section_hypervisor_hyper-v.xml262(para) +msgid "paste" +msgstr "" + +#: ./doc/config-reference/compute/section_hypervisor_hyper-v.xml265(para) +msgid "paste-deploy" +msgstr "" + +#: ./doc/config-reference/compute/section_hypervisor_hyper-v.xml268(para) +msgid "prettytable" +msgstr "" + +#: ./doc/config-reference/compute/section_hypervisor_hyper-v.xml271(para) +msgid "python-cinderclient" +msgstr "" + +#: ./doc/config-reference/compute/section_hypervisor_hyper-v.xml274(para) +msgid "python-glanceclient" +msgstr "" + +#: ./doc/config-reference/compute/section_hypervisor_hyper-v.xml277(para) +msgid "python-keystoneclient" +msgstr "" + +#: ./doc/config-reference/compute/section_hypervisor_hyper-v.xml280(para) +msgid "repoze.lru" +msgstr "" + +#: ./doc/config-reference/compute/section_hypervisor_hyper-v.xml283(para) +msgid "routes" +msgstr "" + +#: ./doc/config-reference/compute/section_hypervisor_hyper-v.xml286(para) +msgid "sqlalchemy" +msgstr "" + +#: ./doc/config-reference/compute/section_hypervisor_hyper-v.xml289(para) +msgid "simplejson" +msgstr "" + +#: ./doc/config-reference/compute/section_hypervisor_hyper-v.xml292(para) +msgid "warlock" +msgstr "" + +#: ./doc/config-reference/compute/section_hypervisor_hyper-v.xml295(para) +msgid "webob" +msgstr "" + +#: ./doc/config-reference/compute/section_hypervisor_hyper-v.xml298(para) +msgid "wmi" +msgstr "" + +#: ./doc/config-reference/compute/section_hypervisor_hyper-v.xml303(title) +msgid "Install Nova-compute" +msgstr "" + +#: ./doc/config-reference/compute/section_hypervisor_hyper-v.xml304(emphasis) +msgid "Using git on Windows to retrieve source" +msgstr "" + +#: ./doc/config-reference/compute/section_hypervisor_hyper-v.xml305(para) +msgid "" +"Git be used 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.xml310(link) +msgid "" +"http://code.google.com/p/msysgit/downloads/list?q=full+installer+official+git" +msgstr "" + +#: ./doc/config-reference/compute/section_hypervisor_hyper-v.xml312(para) +msgid "" +"Download the latest installer. Once the download is complete double click " +"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.xml315(para) +msgid "Once installed you may run the following to clone the Nova code." +msgstr "" + +#: ./doc/config-reference/compute/section_hypervisor_hyper-v.xml321(title) +msgid "Configure Nova.conf" +msgstr "" + +#: ./doc/config-reference/compute/section_hypervisor_hyper-v.xml322(para) +msgid "" +"The nova.conf file must be placed in " +"C:\\etc\\nova for running OpenStack on Hyper-V. Below is " +"a sample nova.conf for Windows:" +msgstr "" + +#: ./doc/config-reference/compute/section_hypervisor_hyper-v.xml346(para) +msgid "The following table contains a reference of all options for hyper-v" +msgstr "" + +#: ./doc/config-reference/compute/section_hypervisor_hyper-v.xml350(title) +msgid "Prepare images for use with Hyper-V" +msgstr "" + +#: ./doc/config-reference/compute/section_hypervisor_hyper-v.xml351(para) +msgid "" +"Hyper-V currently supports only the VHD 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.xml355(link) +msgid "http://technet.microsoft.com/en-us/library/cc772480.aspx" +msgstr "" + +#: ./doc/config-reference/compute/section_hypervisor_hyper-v.xml356(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.xml359(replaceable) +msgid "VM_IMAGE_NAME" +msgstr "" + +#: ./doc/config-reference/compute/section_hypervisor_hyper-v.xml363(title) +msgid "Run Compute with Hyper-V" +msgstr "" + +#: ./doc/config-reference/compute/section_hypervisor_hyper-v.xml364(para) +msgid "" +"To start the nova-compute " +"service, run this command from a console in the Windows server:" +msgstr "" + +#: ./doc/config-reference/compute/section_hypervisor_hyper-v.xml371(title) +msgid "Troubleshoot Hyper-V configuration" +msgstr "" + +#: ./doc/config-reference/compute/section_hypervisor_hyper-v.xml374(para) +msgid "" +"I ran the nova-manage service list 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.xml379(link) +msgid "here" +msgstr "" + +#: ./doc/config-reference/compute/section_hypervisor_hyper-v.xml377(emphasis) +msgid "" +"Verify that you are synchronized with a network time source. Instructions " +"for configuring NTP on your Hyper-V compute node are located " +"" +msgstr "" + +#. When image changes, this message will be marked fuzzy or untranslated for +#. you. +#. It doesn't matter what you translate it to: it's not used at all. +#: ./doc/config-reference/compute/section_hypervisor_vmware.xml39(None) +msgid "" +"@@image: '../../common/figures/vmware-nova-driver-architecture.jpg'; " +"md5=d95084ce963cffbe3e86307c87d804c1" +msgstr "" + +#: ./doc/config-reference/compute/section_hypervisor_vmware.xml6(title) +msgid "VMware vSphere" +msgstr "" + +#: ./doc/config-reference/compute/section_hypervisor_vmware.xml9(title) +msgid "Introduction" +msgstr "" + +#: ./doc/config-reference/compute/section_hypervisor_vmware.xml10(para) +msgid "" +"OpenStack Compute supports the VMware vSphere product family and enables " +"access to advanced features such as vMotion, High Availability, and Dynamic " +"Resource Scheduling (DRS). This section describes how to configure VMware-" +"based virtual machine images for launch. vSphere versions 4.1 and newer are " +"supported." +msgstr "" + +#: ./doc/config-reference/compute/section_hypervisor_vmware.xml16(para) +msgid "" +"The VMware vCenter driver enables the nova-" +"compute service to communicate with a VMware vCenter server " +"that manages one or more ESX host clusters. The driver aggregates the ESX " +"hosts in each cluster to present one large hypervisor entity for each " +"cluster to the Compute scheduler. Because individual ESX hosts are not " +"exposed to the scheduler, Compute schedules to the granularity of clusters " +"and vCenter uses DRS to select the actual ESX host within the cluster. When " +"a virtual machine makes its way into a vCenter cluster, it can use all " +"vSphere features." +msgstr "" + +#: ./doc/config-reference/compute/section_hypervisor_vmware.xml26(para) +msgid "" +"The following sections describe how to configure the VMware vCenter driver." +msgstr "" + +#: ./doc/config-reference/compute/section_hypervisor_vmware.xml30(title) +msgid "High-level architecture" +msgstr "" + +#: ./doc/config-reference/compute/section_hypervisor_vmware.xml31(para) +msgid "" +"The following diagram shows a high-level view of the VMware driver " +"architecture:" +msgstr "" + +#: ./doc/config-reference/compute/section_hypervisor_vmware.xml34(title) +msgid "VMware driver architecture" +msgstr "" + +#: ./doc/config-reference/compute/section_hypervisor_vmware.xml43(para) +msgid "" +"As the figure shows, the OpenStack Compute Scheduler sees three hypervisors " +"that each correspond to a cluster in vCenter. Nova-compute contains the VMware driver. You can run with " +"multiple nova-compute services. " +"While Compute schedules at the granularity of a cluster, the VMware driver " +"inside nova-compute interacts " +"with the vCenter APIs to select an appropriate ESX host within the cluster. " +"Internally, vCenter uses DRS for placement." +msgstr "" + +#: ./doc/config-reference/compute/section_hypervisor_vmware.xml53(para) +msgid "" +"The VMware vCenter driver also interacts with the OpenStack Image Service to" +" copy VMDK images from the Image Service back end store. The dotted line in " +"the figure represents VMDK images being copied from the OpenStack Image " +"Service to the vSphere data store. VMDK images are cached in the data store " +"so the copy operation is only required the first time that the VMDK image is" +" used." +msgstr "" + +#: ./doc/config-reference/compute/section_hypervisor_vmware.xml60(para) +msgid "" +"After OpenStack boots a VM into a vSphere cluster, the VM becomes visible in" +" vCenter and can access vSphere advanced features. At the same time, the VM " +"is visible in the OpenStack dashboard and you can manage it as you would any" +" other OpenStack VM. You can perform advanced vSphere operations in vCenter " +"while you configure OpenStack resources such as VMs through the OpenStack " +"dashboard." +msgstr "" + +#: ./doc/config-reference/compute/section_hypervisor_vmware.xml67(para) +msgid "" +"The figure does not show how networking fits into the architecture. Both " +"nova-network and the OpenStack " +"Networking Service are supported. For details, see ." +msgstr "" + +#: ./doc/config-reference/compute/section_hypervisor_vmware.xml74(title) +msgid "Configuration overview" +msgstr "" + +#: ./doc/config-reference/compute/section_hypervisor_vmware.xml75(para) +msgid "" +"To get started with the VMware vCenter driver, complete the following high-" +"level steps:" +msgstr "" + +#: ./doc/config-reference/compute/section_hypervisor_vmware.xml79(para) +msgid "Configure vCenter correctly. See ." +msgstr "" + +#: ./doc/config-reference/compute/section_hypervisor_vmware.xml83(para) +msgid "" +"Configure nova.conf for the VMware vCenter driver. See " +"." +msgstr "" + +#: ./doc/config-reference/compute/section_hypervisor_vmware.xml88(para) +msgid "" +"Load desired VMDK images into the OpenStack Image Service. See ." +msgstr "" + +#: ./doc/config-reference/compute/section_hypervisor_vmware.xml92(para) +msgid "" +"Configure networking with either nova-" +"network or the OpenStack Networking Service. See ." +msgstr "" + +#: ./doc/config-reference/compute/section_hypervisor_vmware.xml100(title) +msgid "Prerequisites and limitations" +msgstr "" + +#: ./doc/config-reference/compute/section_hypervisor_vmware.xml101(para) +msgid "" +"Use the following list to prepare a vSphere environment that runs with the " +"VMware vCenter driver:" +msgstr "" + +#: ./doc/config-reference/compute/section_hypervisor_vmware.xml105(para) +msgid "" +"vCenter inventory. Make sure that any " +"vCenter used by OpenStack contains a single data center. A future Havana " +"stable release will address this temporary limitation." +msgstr "" + +#: ./doc/config-reference/compute/section_hypervisor_vmware.xml111(para) +msgid "" +"DRS. For any cluster that contains " +"multiple ESX hosts, enable DRS and enable fully automated placement." +msgstr "" + +#: ./doc/config-reference/compute/section_hypervisor_vmware.xml116(para) +msgid "" +"Shared storage. Only shared storage is " +"supported and data stores must be shared among all hosts in a cluster. It is" +" recommended to remove data stores not intended for OpenStack from clusters " +"being configured for OpenStack. Currently, a single data store can be used " +"per cluster. A future Havana stable release will address this temporary " +"limitation." +msgstr "" + +#: ./doc/config-reference/compute/section_hypervisor_vmware.xml125(para) +msgid "" +"Clusters and data stores. Do not use " +"OpenStack clusters and data stores for other purposes. If you do, OpenStack " +"displays incorrect usage information." +msgstr "" + +#: ./doc/config-reference/compute/section_hypervisor_vmware.xml131(para) +msgid "" +"Networking. The networking configuration " +"depends on the desired networking model. See ." +msgstr "" + +#: ./doc/config-reference/compute/section_hypervisor_vmware.xml136(para) +msgid "" +"Security groups. If you use the VMware " +"driver with OpenStack Networking and the NSX plug-in, security groups are " +"supported. If you use nova-" +"network, security groups are not supported." +msgstr "" + +#: ./doc/config-reference/compute/section_hypervisor_vmware.xml141(para) +msgid "The NSX plug-in is the only plug-in that is validated for vSphere." +msgstr "" + +#: ./doc/config-reference/compute/section_hypervisor_vmware.xml145(para) +msgid "" +"VNC. The port range 5900 - 6105 " +"(inclusive) is automatically enabled for VNC connections on every ESX host " +"in all clusters under OpenStack control. For more information about using a " +"VNC client to connect to virtual machine, see http://kb.vmware.com/selfservice/microsites/search.do?language=en_US&cmd=displayKC&externalId=1246." +msgstr "" + +#: ./doc/config-reference/compute/section_hypervisor_vmware.xml152(para) +msgid "" +"In addition to the default VNC port numbers (5900 to 6000) specified in the " +"above document, the following ports are also used: 6101, 6102, and 6105." +msgstr "" + +#: ./doc/config-reference/compute/section_hypervisor_vmware.xml155(para) +msgid "" +"You must modify the ESXi firewall configuration to allow the VNC ports. " +"Additionally, for the firewall modifications to persist after a reboot, you " +"must create a custom vSphere Installation Bundle (VIB) which is then " +"installed onto the running ESXi host or added to a custom image profile used" +" to install ESXi hosts. For details about how to create a VIB for persisting" +" the firewall configuration modifications, see " +" " +"http://kb.vmware.com/selfservice/microsites/search.do?language=en_US&cmd=displayKC&externalId=2007381." +msgstr "" + +#: ./doc/config-reference/compute/section_hypervisor_vmware.xml168(para) +msgid "" +"Ephemeral Disks. Ephemeral disks are not " +"supported. A future stable release will address this temporary limitation." +msgstr "" + +#: ./doc/config-reference/compute/section_hypervisor_vmware.xml175(title) +msgid "VMware vCenter driver" +msgstr "" + +#: ./doc/config-reference/compute/section_hypervisor_vmware.xml176(para) +msgid "" +"Use the VMware vCenter driver (VMwareVCDriver) to connect OpenStack Compute " +"with vCenter. This recommended configuration enables access through vCenter " +"to advanced vSphere features like vMotion, High Availability, and Dynamic " +"Resource Scheduling (DRS)." +msgstr "" + +#: ./doc/config-reference/compute/section_hypervisor_vmware.xml182(title) +msgid "VMwareVCDriver configuration options" +msgstr "" + +#: ./doc/config-reference/compute/section_hypervisor_vmware.xml183(para) +msgid "" +"When you use the VMwareVCDriver (vCenter) with OpenStack Compute, add the " +"following VMware-specific configuration options to the " +"nova.conf file:" +msgstr "" + +#: ./doc/config-reference/compute/section_hypervisor_vmware.xml200(para) +msgid "" +"Clusters: The vCenter driver can support multiple clusters. To use more than" +" one cluster, simply add multiple cluster_name lines in " +"nova.conf with the appropriate cluster name. Clusters " +"and data stores used by the vCenter driver should not contain any VMs other " +"than those created by the driver." +msgstr "" + +#: ./doc/config-reference/compute/section_hypervisor_vmware.xml209(para) +msgid "" +"Data stores: The datastore_regex field specifies the data " +"stores to use with Compute. For example, " +"datastore_regex=\"nas.*\" selects all the data stores that have" +" a name starting with \"nas\". If this line is omitted, Compute uses the " +"first data store returned by the vSphere API. It is recommended not to use " +"this field and instead remove data stores that are not intended for " +"OpenStack." +msgstr "" + +#: ./doc/config-reference/compute/section_hypervisor_vmware.xml220(para) +msgid "" +"A nova-compute service can " +"control one or more clusters containing multiple ESX hosts, making " +"nova-compute a critical service " +"from a high availability perspective. Because the host that runs nova-compute can fail while the vCenter and " +"ESX still run, you must protect the nova-" +"compute service against host failures." +msgstr "" + +#: ./doc/config-reference/compute/section_hypervisor_vmware.xml230(para) +#: ./doc/config-reference/compute/section_hypervisor_vmware.xml634(para) +msgid "" +"Many nova.conf options are relevant to libvirt but do " +"not apply to this driver." +msgstr "" + +#: ./doc/config-reference/compute/section_hypervisor_vmware.xml233(para) +msgid "" +"You must complete additional configuration for environments that use vSphere" +" 5.0 and earlier. See ." +msgstr "" + +#: ./doc/config-reference/compute/section_hypervisor_vmware.xml239(title) +msgid "Images with VMware vSphere" +msgstr "" + +#: ./doc/config-reference/compute/section_hypervisor_vmware.xml240(para) +msgid "" +"The vCenter driver supports images in the VMDK format. Disks in this format " +"can be obtained from VMware Fusion or from an ESX environment. It is also " +"possible to convert other formats, such as qcow2, to the VMDK format using " +"the qemu-img utility. After a VMDK disk is available, load it " +"into the OpenStack Image Service. Then, you can use it with the VMware " +"vCenter driver. The following sections provide additional details on the " +"supported disks and the commands used for conversion and upload." +msgstr "" + +#: ./doc/config-reference/compute/section_hypervisor_vmware.xml250(title) +msgid "Supported image types" +msgstr "" + +#: ./doc/config-reference/compute/section_hypervisor_vmware.xml251(para) +msgid "" +"Upload images to the OpenStack Image Service in VMDK format. The following " +"VMDK disk types are supported:" +msgstr "" + +#: ./doc/config-reference/compute/section_hypervisor_vmware.xml255(para) +msgid "" +"VMFS Flat Disks (includes thin, thick, " +"zeroedthick, and eagerzeroedthick). Note that once a VMFS thin disk is " +"exported from VMFS to a non-VMFS location, like the OpenStack Image Service," +" it becomes a preallocated flat disk. This impacts the transfer time from " +"the OpenStack Image Service to the data store when the full preallocated " +"flat disk, rather than the thin disk, must be transferred." +msgstr "" + +#: ./doc/config-reference/compute/section_hypervisor_vmware.xml265(para) +msgid "" +"Monolithic Sparse disks. Sparse disks " +"get imported from the OpenStack Image Service into ESX as thin provisioned " +"disks. Monolithic Sparse disks can be obtained from VMware Fusion or can be " +"created by converting from other virtual disk formats using the qemu-" +"img utility." +msgstr "" + +#: ./doc/config-reference/compute/section_hypervisor_vmware.xml274(para) +msgid "" +"The following table shows the vmware_disktype property that " +"applies to each of the supported VMDK disk types:" +msgstr "" + +#: ./doc/config-reference/compute/section_hypervisor_vmware.xml278(caption) +msgid "OpenStack Image Service disk type settings" +msgstr "" + +#: ./doc/config-reference/compute/section_hypervisor_vmware.xml281(th) +msgid "vmware_disktype property" +msgstr "" + +#: ./doc/config-reference/compute/section_hypervisor_vmware.xml282(th) +#: ./doc/config-reference/block-storage/drivers/vmware-vmdk-driver.xml31(title) +msgid "VMDK disk type" +msgstr "" + +#: ./doc/config-reference/compute/section_hypervisor_vmware.xml287(td) +msgid "sparse" +msgstr "" + +#: ./doc/config-reference/compute/section_hypervisor_vmware.xml289(para) +msgid "Monolithic Sparse" +msgstr "" + +#: ./doc/config-reference/compute/section_hypervisor_vmware.xml293(td) +#: ./doc/config-reference/block-storage/drivers/vmware-vmdk-driver.xml51(td) +#: ./doc/config-reference/block-storage/drivers/vmware-vmdk-driver.xml53(td) +msgid "thin" +msgstr "" + +#: ./doc/config-reference/compute/section_hypervisor_vmware.xml295(para) +msgid "VMFS flat, thin provisioned" +msgstr "" + +#: ./doc/config-reference/compute/section_hypervisor_vmware.xml299(td) +msgid "preallocated (default)" +msgstr "" + +#: ./doc/config-reference/compute/section_hypervisor_vmware.xml301(para) +msgid "VMFS flat, thick/zeroedthick/eagerzeroedthick" +msgstr "" + +#: ./doc/config-reference/compute/section_hypervisor_vmware.xml308(para) +msgid "" +"The vmware_disktype property is set when an image is loaded " +"into the OpenStack Image Service. For example, the following command creates" +" a Monolithic Sparse image by setting vmware_disktype to " +"sparse:" +msgstr "" + +#: ./doc/config-reference/compute/section_hypervisor_vmware.xml317(para) +msgid "" +"Note that specifying thin does not provide any advantage " +"over preallocated with the current version of the driver." +" Future versions might restore the thin properties of the disk after it is " +"downloaded to a vSphere data store." +msgstr "" + +#: ./doc/config-reference/compute/section_hypervisor_vmware.xml324(title) +msgid "Convert and load images" +msgstr "" + +#: ./doc/config-reference/compute/section_hypervisor_vmware.xml325(para) +msgid "" +"Using the qemu-img utility, disk images in several formats " +"(such as, qcow2) can be converted to the VMDK format." +msgstr "" + +#: ./doc/config-reference/compute/section_hypervisor_vmware.xml328(para) +msgid "" +"For example, the following command can be used to convert a qcow2 Ubuntu Precise cloud image:" +msgstr "" + +#: ./doc/config-reference/compute/section_hypervisor_vmware.xml334(para) +msgid "" +"VMDK disks converted through qemu-img are always monolithic sparse VMDK disks with an IDE " +"adapter type. Using the previous example of the Precise Ubuntu image after " +"the qemu-img conversion, the command to upload the VMDK disk " +"should be something like:" +msgstr "" + +#: ./doc/config-reference/compute/section_hypervisor_vmware.xml345(para) +msgid "" +"Note that the vmware_disktype is set to sparse and the vmware_adaptertype is" +" set to ide in the previous command." +msgstr "" + +#: ./doc/config-reference/compute/section_hypervisor_vmware.xml349(para) +msgid "" +"If the image did not come from the qemu-img utility, the " +"vmware_disktype and vmware_adaptertype might be " +"different. To determine the image adapter type from an image file, use the " +"following command and look for the ddb.adapterType= line:" +msgstr "" + +#: ./doc/config-reference/compute/section_hypervisor_vmware.xml356(para) +msgid "" +"Assuming a preallocated disk type and an iSCSI lsiLogic adapter type, the " +"following command uploads the VMDK disk:" +msgstr "" + +#: ./doc/config-reference/compute/section_hypervisor_vmware.xml364(para) +msgid "" +"Currently, OS boot VMDK disks with an IDE adapter type cannot be attached to" +" a virtual SCSI controller and likewise disks with one of the SCSI adapter " +"types (such as, busLogic, lsiLogic) cannot be attached to the IDE " +"controller. Therefore, as the previous examples show, it is important to set" +" the vmware_adaptertype property correctly. The default adapter" +" type is lsiLogic, which is SCSI, so you can omit the " +"vmware_adaptertype property if you are certain that " +"the image adapter type is lsiLogic." +msgstr "" + +#: ./doc/config-reference/compute/section_hypervisor_vmware.xml376(title) +msgid "Tag VMware images" +msgstr "" + +#: ./doc/config-reference/compute/section_hypervisor_vmware.xml377(para) +msgid "" +"In a mixed hypervisor environment, OpenStack Compute uses the " +"hypervisor_type tag to match images to the correct hypervisor " +"type. For VMware images, set the hypervisor type to " +"vmware. Other valid hypervisor types include: xen, qemu, " +"kvm, lxc, uml, and hyperv." +msgstr "" + +#: ./doc/config-reference/compute/section_hypervisor_vmware.xml390(title) +msgid "Optimize images" +msgstr "" + +#: ./doc/config-reference/compute/section_hypervisor_vmware.xml391(para) +msgid "" +"Monolithic Sparse disks are considerably faster to download but have the " +"overhead of an additional conversion step. When imported into ESX, sparse " +"disks get converted to VMFS flat thin provisioned disks. The download and " +"conversion steps only affect the first launched instance that uses the " +"sparse disk image. The converted disk image is cached, so subsequent " +"instances that use this disk image can simply use the cached version." +msgstr "" + +#: ./doc/config-reference/compute/section_hypervisor_vmware.xml399(para) +msgid "" +"To avoid the conversion step (at the cost of longer download times) consider" +" converting sparse disks to thin provisioned or preallocated disks before " +"loading them into the OpenStack Image Service. Below are some tools that can" +" be used to pre-convert sparse disks." +msgstr "" + +#: ./doc/config-reference/compute/section_hypervisor_vmware.xml406(emphasis) +msgid "Using vSphere CLI (or sometimes called the remote CLI or rCLI) tools" +msgstr "" + +#: ./doc/config-reference/compute/section_hypervisor_vmware.xml408(para) +msgid "" +"Assuming that the sparse disk is made available on a data store accessible " +"by an ESX host, the following command converts it to preallocated format:" +msgstr "" + +#: ./doc/config-reference/compute/section_hypervisor_vmware.xml412(para) +msgid "" +"(Note that the vifs tool from the same CLI package can be used to upload the" +" disk to be converted. The vifs tool can also be used to download the " +"converted disk if necessary.)" +msgstr "" + +#: ./doc/config-reference/compute/section_hypervisor_vmware.xml418(emphasis) +msgid "Using vmkfstools directly on the ESX host" +msgstr "" + +#: ./doc/config-reference/compute/section_hypervisor_vmware.xml420(para) +msgid "" +"If the SSH service is enabled on an ESX host, the sparse disk can be " +"uploaded to the ESX data store via scp and the vmkfstools local to the ESX " +"host can use used to perform the conversion: (After logging in to the host " +"via ssh)" +msgstr "" + +#: ./doc/config-reference/compute/section_hypervisor_vmware.xml429(emphasis) +msgid "vmware-vdiskmanager" +msgstr "" + +#: ./doc/config-reference/compute/section_hypervisor_vmware.xml430(para) +msgid "" +"vmware-vdiskmanager is a utility that comes bundled with VMware" +" Fusion and VMware Workstation. Below is an example of converting a sparse " +"disk to preallocated format:" +msgstr "" + +#: ./doc/config-reference/compute/section_hypervisor_vmware.xml435(para) +msgid "" +"In all of the above cases, the converted vmdk is actually a pair of files: " +"the descriptor file converted.vmdk and " +"the actual virtual disk data file converted-" +"flat.vmdk. The file to be uploaded to the OpenStack Image Service" +" is converted-flat.vmdk." +msgstr "" + +#: ./doc/config-reference/compute/section_hypervisor_vmware.xml446(title) +msgid "Image handling" +msgstr "" + +#: ./doc/config-reference/compute/section_hypervisor_vmware.xml447(para) +msgid "" +"The ESX hypervisor requires a copy of the VMDK file in order to boot up a " +"virtual machine. As a result, the vCenter OpenStack Compute driver must " +"download the VMDK via HTTP from the OpenStack Image Service to a data store " +"that is visible to the hypervisor. To optimize this process, the first time " +"a VMDK file is used, it gets cached in the data store. Subsequent virtual " +"machines that need the VMDK use the cached version and don't have to copy " +"the file again from the OpenStack Image Service." +msgstr "" + +#: ./doc/config-reference/compute/section_hypervisor_vmware.xml456(para) +msgid "" +"Even with a cached VMDK, there is still a copy operation from the cache " +"location to the hypervisor file directory in the shared data store. To avoid" +" this copy, boot the image in linked_clone mode. To learn how to enable this" +" mode, see . Note also that it is possible " +"to override the linked_clone mode on a per-image basis by using the " +"vmware_linked_clone property in the OpenStack Image Service." +msgstr "" + +#: ./doc/config-reference/compute/section_hypervisor_vmware.xml467(title) +msgid "Networking with VMware vSphere" +msgstr "" + +#: ./doc/config-reference/compute/section_hypervisor_vmware.xml468(para) +msgid "" +"The VMware driver supports networking with the nova-network service or the OpenStack Networking Service. " +"Depending on your installation, complete these configuration steps before " +"you provision VMs:" +msgstr "" + +#: ./doc/config-reference/compute/section_hypervisor_vmware.xml475(para) +msgid "" +"The nova-" +"network service with the FlatManager or " +"FlatDHCPManager. Create a port group with the same name as the " +"flat_network_bridge value in the " +"nova.conf file. The default value is " +"br100." +msgstr "" + +#: ./doc/config-reference/compute/section_hypervisor_vmware.xml481(para) +msgid "All VM NICs are attached to this port group." +msgstr "" + +#: ./doc/config-reference/compute/section_hypervisor_vmware.xml482(para) +msgid "" +"Ensure that the flat interface of the node that runs the nova-network service has a path to this " +"network." +msgstr "" + +#: ./doc/config-reference/compute/section_hypervisor_vmware.xml487(para) +msgid "" +"The nova-" +"network service with the VlanManager. Set the " +"vlan_interface configuration option to match the ESX host" +" interface that handles VLAN-tagged VM traffic." +msgstr "" + +#: ./doc/config-reference/compute/section_hypervisor_vmware.xml493(para) +msgid "OpenStack Compute automatically creates the corresponding port groups." +msgstr "" + +#: ./doc/config-reference/compute/section_hypervisor_vmware.xml497(para) +msgid "" +"The OpenStack Networking Service. If you " +"use OVS as the l2 agent, create a port group with the " +"same name as the DEFAULT.neutron_ovs_bridge value in the " +"nova.conf file. Otherwise, create a port group with the" +" same name as the vmware.integration_bridge value in the " +"nova.conf file. In both cases, the default value is " +"br-int." +msgstr "" + +#: ./doc/config-reference/compute/section_hypervisor_vmware.xml506(para) +msgid "" +"All VM NICs are attached to this port group for management by the OpenStack " +"Networking plug-in." +msgstr "" + +#: ./doc/config-reference/compute/section_hypervisor_vmware.xml512(title) +msgid "Volumes with VMware vSphere" +msgstr "" + +#: ./doc/config-reference/compute/section_hypervisor_vmware.xml513(para) +msgid "" +"The VMware driver supports attaching volumes from the OpenStack Block " +"Storage service. The VMware VMDK driver for OpenStack Block Storage is " +"recommended and should be used for managing volumes based on vSphere data " +"stores. More information about the VMware VMDK driver can be found at: VMware VMDK Driver. Also an iscsi volume driver " +"provides limited support and can be used only for attachments." +msgstr "" + +#: ./doc/config-reference/compute/section_hypervisor_vmware.xml524(title) +msgid "vSphere 5.0 and earlier additional set up" +msgstr "" + +#: ./doc/config-reference/compute/section_hypervisor_vmware.xml525(para) +msgid "" +"Users of vSphere 5.0 or earlier must host their WSDL files locally. These " +"steps are applicable for vCenter 5.0 or ESXi 5.0 and you can either mirror " +"the WSDL from the vCenter or ESXi server that you intend to use or you can " +"download the SDK directly from VMware. These workaround steps fix a known" +" issue with the WSDL that was resolved in later versions." +msgstr "" + +#: ./doc/config-reference/compute/section_hypervisor_vmware.xml534(title) +msgid "Mirror WSDL from vCenter (or ESXi)" +msgstr "" + +#: ./doc/config-reference/compute/section_hypervisor_vmware.xml536(para) +msgid "" +"Set the VMWAREAPI_IP shell variable to the IP address for your " +"vCenter or ESXi host from where you plan to mirror files. For example:" +msgstr "" + +#: ./doc/config-reference/compute/section_hypervisor_vmware.xml542(para) +msgid "Create a local file system directory to hold the WSDL files:" +msgstr "" + +#: ./doc/config-reference/compute/section_hypervisor_vmware.xml547(para) +msgid "Change into the new directory. " +msgstr "" + +#: ./doc/config-reference/compute/section_hypervisor_vmware.xml551(para) +msgid "" +"Use your OS-specific tools to install a command-line tool that can download " +"files like ." +msgstr "" + +#: ./doc/config-reference/compute/section_hypervisor_vmware.xml556(para) +msgid "Download the files to the local file cache:" +msgstr "" + +#: ./doc/config-reference/compute/section_hypervisor_vmware.xml566(para) +msgid "" +"Because the reflect-types.xsd and reflect-" +"messagetypes.xsd files do not fetch properly, you must stub out " +"these files. Use the following XML listing to replace the missing file " +"content. The XML parser underneath Python can be very particular and if you " +"put a space in the wrong place, it can break the parser. Copy the following " +"contents and formatting carefully." +msgstr "" + +#: ./doc/config-reference/compute/section_hypervisor_vmware.xml583(para) +msgid "" +"Now that the files are locally present, tell the driver to look for the SOAP" +" service WSDLs in the local file system and not on the remote vSphere " +"server. Add the following setting to the nova.conf file" +" for your nova-compute node:" +msgstr "" + +#: ./doc/config-reference/compute/section_hypervisor_vmware.xml593(para) +msgid "" +"Alternatively, download the version appropriate SDK from http://www.vmware.com/support/developer/vc-sdk/ and copy it to" +" the /opt/stack/vmware file. Make sure that the WSDL is" +" available, in for example " +"/opt/stack/vmware/SDK/wsdl/vim25/vimService.wsdl. You " +"must point nova.conf to fetch this WSDL file from the " +"local file system by using a URL." +msgstr "" + +#: ./doc/config-reference/compute/section_hypervisor_vmware.xml602(para) +msgid "" +"When using the VMwareVCDriver (vCenter) with OpenStack Compute with vSphere " +"version 5.0 or earlier, nova.conf must include the " +"following extra config option:" +msgstr "" + +#: ./doc/config-reference/compute/section_hypervisor_vmware.xml610(title) +msgid "VMware ESX driver" +msgstr "" + +#: ./doc/config-reference/compute/section_hypervisor_vmware.xml611(para) +msgid "" +"This section covers details of using the VMwareESXDriver. The ESX Driver has" +" not been extensively tested and is not recommended. To configure the VMware" +" vCenter driver instead, see ." +msgstr "" + +#: ./doc/config-reference/compute/section_hypervisor_vmware.xml616(title) +msgid "VMwareESXDriver configuration options" +msgstr "" + +#: ./doc/config-reference/compute/section_hypervisor_vmware.xml617(para) +msgid "" +"When you use the VMwareESXDriver (no vCenter) with OpenStack Compute, add " +"the following VMware-specific configuration options to the " +"nova.conf file:" +msgstr "" + +#: ./doc/config-reference/compute/section_hypervisor_vmware.xml629(para) +msgid "" +"Remember that you will have one nova-" +"compute service for each ESXi host. It is recommended that this" +" host run as a VM on the same ESXi host that it manages." +msgstr "" + +#: ./doc/config-reference/compute/section_hypervisor_vmware.xml639(title) +msgid "Requirements and limitations" +msgstr "" + +#: ./doc/config-reference/compute/section_hypervisor_vmware.xml640(para) +msgid "" +"The ESXDriver cannot use many of the vSphere platform advanced capabilities," +" namely vMotion, high availability, and DRS." +msgstr "" + +#: ./doc/config-reference/compute/section_hypervisor_vmware.xml646(title) +#: ./doc/config-reference/compute/section_compute-scheduler.xml527(title) +msgid "Configuration reference" +msgstr "" + +#. When image changes, this message will be marked fuzzy or untranslated for +#. you. +#. It doesn't matter what you translate it to: it's not used at all. +#: ./doc/config-reference/compute/section_compute-scheduler.xml75(None) +msgid "" +"@@image: '../../common/figures/filteringWorkflow1.png'; " +"md5=c144af5cbdee1bd17a7bde0bea5b5fe7" +msgstr "" + +#: ./doc/config-reference/compute/section_compute-scheduler.xml10(title) +msgid "Scheduling" +msgstr "" + +#: ./doc/config-reference/compute/section_compute-scheduler.xml11(para) +msgid "" +"Compute uses the nova-scheduler " +"service to determine how to dispatch compute and volume requests. For " +"example, the nova-scheduler " +"service determines which host a VM should launch on. The term " +"host in the context of filters means a physical node " +"that has a nova-compute service " +"running on it. You can configure the scheduler through a variety of options." +msgstr "" + +#: ./doc/config-reference/compute/section_compute-scheduler.xml17(para) +msgid "Compute is configured with the following default scheduler options:" +msgstr "" + +#: ./doc/config-reference/compute/section_compute-scheduler.xml24(para) +msgid "" +"By default, the compute scheduler is configured as a filter scheduler, as " +"described in the next section. In the default configuration, this scheduler " +"considers hosts that meet all the following criteria:" +msgstr "" + +#: ./doc/config-reference/compute/section_compute-scheduler.xml30(para) +msgid "" +"Are in the requested availability zone " +"(AvailabilityZoneFilter)." +msgstr "" + +#: ./doc/config-reference/compute/section_compute-scheduler.xml34(para) +msgid "Have sufficient RAM available (RamFilter)." +msgstr "" + +#: ./doc/config-reference/compute/section_compute-scheduler.xml38(para) +msgid "" +"Are capable of servicing the request (ComputeFilter)." +msgstr "" + +#: ./doc/config-reference/compute/section_compute-scheduler.xml42(para) +msgid "" +"For information on the volume scheduler, refer the Block Storage section of " +"OpenStack Cloud Administrator " +"Guide for information." +msgstr "" + +#: ./doc/config-reference/compute/section_compute-scheduler.xml46(title) +msgid "Filter scheduler" +msgstr "" + +#: ./doc/config-reference/compute/section_compute-scheduler.xml47(para) +msgid "" +"The Filter Scheduler " +"(nova.scheduler.filter_scheduler.FilterScheduler) is the " +"default scheduler for scheduling virtual machine instances. It supports " +"filtering and weighting to make informed decisions on where a new instance " +"should be created. You can use this scheduler to schedule compute requests " +"but not volume requests. For example, you can use it with only the " +"compute_scheduler_driver configuration option." +msgstr "" + +#: ./doc/config-reference/compute/section_compute-scheduler.xml60(title) +msgid "Filters" +msgstr "" + +#: ./doc/config-reference/compute/section_compute-scheduler.xml70(title) +msgid "Filtering" +msgstr "" + +#: ./doc/config-reference/compute/section_compute-scheduler.xml61(para) +msgid "" +"When the Filter Scheduler receives a request for a resource, it first " +"applies filters to determine which hosts are eligible for consideration when" +" dispatching a resource. Filters are binary: either a host is accepted by " +"the filter, or it is rejected. Hosts that are accepted by the filter are " +"then processed by a different algorithm to decide which hosts to use for " +"that request, described in the Weights " +"section. " +msgstr "" + +#: ./doc/config-reference/compute/section_compute-scheduler.xml80(para) +msgid "" +"The scheduler_available_filters configuration option in " +"nova.conf provides the Compute service with the list of" +" the filters that are used by the scheduler. The default setting specifies " +"all of the filter that are included with the Compute service:" +msgstr "" + +#: ./doc/config-reference/compute/section_compute-scheduler.xml87(para) +msgid "" +"This configuration option can be specified multiple times. For example, if " +"you implemented your own custom filter in Python called " +"myfilter.MyFilter and you wanted to use both the built-in" +" filters and your custom filter, your nova.conf file " +"would contain:" +msgstr "" + +#: ./doc/config-reference/compute/section_compute-scheduler.xml96(para) +msgid "" +"The scheduler_default_filters configuration option in " +"nova.conf defines the list of filters that are applied " +"by the nova-scheduler service. As" +" mentioned, the default filters are:" +msgstr "" + +#: ./doc/config-reference/compute/section_compute-scheduler.xml102(para) +msgid "The following sections describe the available filters." +msgstr "" + +#: ./doc/config-reference/compute/section_compute-scheduler.xml105(title) +msgid "AggregateCoreFilter" +msgstr "" + +#: ./doc/config-reference/compute/section_compute-scheduler.xml106(para) +msgid "" +"Implements blueprint per-aggregate-resource-ratio. AggregateCoreFilter " +"supports per-aggregate cpu_allocation_ratio. If the per-" +"aggregate value is not found, the value falls back to the global setting." +msgstr "" + +#: ./doc/config-reference/compute/section_compute-scheduler.xml113(title) +msgid "AggregateInstanceExtraSpecsFilter" +msgstr "" + +#: ./doc/config-reference/compute/section_compute-scheduler.xml114(para) +msgid "" +"Matches properties defined in an instance type's extra specs against admin-" +"defined properties on a host aggregate. Works with specifications that are " +"unscoped, or are scoped with " +"aggregate_instance_extra_specs. See the host aggregates section for documentation on how" +" to use this filter." +msgstr "" + +#: ./doc/config-reference/compute/section_compute-scheduler.xml123(title) +msgid "AggregateMultiTenancyIsolation" +msgstr "" + +#: ./doc/config-reference/compute/section_compute-scheduler.xml124(para) +msgid "" +"Isolates tenants to specific host " +"aggregates. If a host is in an aggregate that has the metadata key " +"filter_tenant_id it only creates instances from that " +"tenant (or list of tenants). A host can be in different aggregates. If a " +"host does not belong to an aggregate with the metadata key, it can create " +"instances from all tenants." +msgstr "" + +#: ./doc/config-reference/compute/section_compute-scheduler.xml134(title) +msgid "AggregateRamFilter" +msgstr "" + +#: ./doc/config-reference/compute/section_compute-scheduler.xml135(para) +msgid "" +"Implements blueprint per-aggregate-resource-ratio. " +"Supports per-aggregate ram_allocation_ratio. If per-" +"aggregate value is not found, it falls back to the default setting." +msgstr "" + +#: ./doc/config-reference/compute/section_compute-scheduler.xml143(title) +msgid "AllHostsFilter" +msgstr "" + +#: ./doc/config-reference/compute/section_compute-scheduler.xml144(para) +msgid "" +"This is a no-op filter, it does not eliminate any of the available hosts." +msgstr "" + +#: ./doc/config-reference/compute/section_compute-scheduler.xml148(title) +msgid "AvailabilityZoneFilter" +msgstr "" + +#: ./doc/config-reference/compute/section_compute-scheduler.xml149(para) +msgid "" +"Filters hosts by availability zone. This filter must be enabled for the " +"scheduler to respect availability zones in requests." +msgstr "" + +#: ./doc/config-reference/compute/section_compute-scheduler.xml154(title) +msgid "ComputeCapabilitiesFilter" +msgstr "" + +#: ./doc/config-reference/compute/section_compute-scheduler.xml155(para) +msgid "" +"Matches properties defined in an instance type's extra specs against compute" +" capabilities." +msgstr "" + +#: ./doc/config-reference/compute/section_compute-scheduler.xml157(para) +msgid "" +"If an extra specs key contains a colon \":\", anything before the colon is " +"treated as a namespace, and anything after the colon is treated as the key " +"to be matched. If a namespace is present and is not 'capabilities', it is " +"ignored by this filter." +msgstr "" + +#: ./doc/config-reference/compute/section_compute-scheduler.xml163(para) +msgid "" +"Disable the ComputeCapabilitiesFilter when using a Bare Metal configuration," +" due to bug " +"1129485" +msgstr "" + +#: ./doc/config-reference/compute/section_compute-scheduler.xml170(title) +msgid "ComputeFilter" +msgstr "" + +#: ./doc/config-reference/compute/section_compute-scheduler.xml171(para) +msgid "Passes all hosts that are operational and enabled." +msgstr "" + +#: ./doc/config-reference/compute/section_compute-scheduler.xml173(para) +msgid "In general, this filter should always be enabled." +msgstr "" + +#: ./doc/config-reference/compute/section_compute-scheduler.xml177(title) +msgid "CoreFilter" +msgstr "" + +#: ./doc/config-reference/compute/section_compute-scheduler.xml178(para) +msgid "" +"Only schedule instances on hosts if there are sufficient CPU cores " +"available. If this filter is not set, the scheduler may over provision a " +"host based on cores (for example, the virtual cores running on an instance " +"may exceed the physical cores)." +msgstr "" + +#: ./doc/config-reference/compute/section_compute-scheduler.xml183(para) +msgid "" +"This filter can be configured to allow a fixed amount of vCPU overcommitment" +" by using the cpu_allocation_ratio Configuration option " +"in nova.conf. The default setting is:" +msgstr "" + +#: ./doc/config-reference/compute/section_compute-scheduler.xml190(para) +msgid "" +"With this setting, if 8 vCPUs are on a node, the scheduler allows instances " +"up to 128 vCPU to be run on that node." +msgstr "" + +#: ./doc/config-reference/compute/section_compute-scheduler.xml193(para) +msgid "To disallow vCPU overcommitment set:" +msgstr "" + +#: ./doc/config-reference/compute/section_compute-scheduler.xml197(title) +msgid "DifferentHostFilter" +msgstr "" + +#: ./doc/config-reference/compute/section_compute-scheduler.xml198(para) +msgid "" +"Schedule the instance on a different host from a set of instances. To take " +"advantage of this filter, the requester must pass a scheduler hint, using " +"different_host as the key and a list of instance uuids as" +" the value. This filter is the opposite of the " +"SameHostFilter. Using the command-line " +"tool, use the --hint flag. For example:" +msgstr "" + +#: ./doc/config-reference/compute/section_compute-scheduler.xml210(para) +msgid "" +"With the API, use the os:scheduler_hints key. For " +"example:" +msgstr "" + +#: ./doc/config-reference/compute/section_compute-scheduler.xml227(title) +msgid "DiskFilter" +msgstr "" + +#: ./doc/config-reference/compute/section_compute-scheduler.xml228(para) +msgid "" +"Only schedule instances on hosts if there is sufficient disk space available" +" for root and ephemeral storage." +msgstr "" + +#: ./doc/config-reference/compute/section_compute-scheduler.xml231(para) +msgid "" +"This filter can be configured to allow a fixed amount of disk overcommitment" +" by using the disk_allocation_ratio Configuration option " +"in nova.conf. The default setting is:" +msgstr "" + +#: ./doc/config-reference/compute/section_compute-scheduler.xml238(para) +msgid "" +"Adjusting this value to greater than 1.0 enables scheduling instances while " +"over committing disk resources on the node. This might be desirable if you " +"use an image format that is sparse or copy on write such that each virtual " +"instance does not require a 1:1 allocation of virtual disk to physical " +"storage." +msgstr "" + +#: ./doc/config-reference/compute/section_compute-scheduler.xml245(title) +msgid "GroupAffinityFilter" +msgstr "" + +#: ./doc/config-reference/compute/section_compute-scheduler.xml246(para) +msgid "" +"The GroupAffinityFilter ensures that an instance is scheduled on to a host " +"from a set of group hosts. To take advantage of this filter, the requester " +"must pass a scheduler hint, using group as the key and an" +" arbitrary name as the value. Using the command-line tool, " +"use the --hint flag. For example:" +msgstr "" + +#: ./doc/config-reference/compute/section_compute-scheduler.xml258(title) +msgid "GroupAntiAffinityFilter" +msgstr "" + +#: ./doc/config-reference/compute/section_compute-scheduler.xml259(para) +msgid "" +"The GroupAntiAffinityFilter ensures that each instance in a group is on a " +"different host. To take advantage of this filter, the requester must pass a " +"scheduler hint, using group as the key and an arbitrary " +"name as the value. Using the command-line tool, use the " +"--hint flag. For example:" +msgstr "" + +#: ./doc/config-reference/compute/section_compute-scheduler.xml271(title) +msgid "ImagePropertiesFilter" +msgstr "" + +#: ./doc/config-reference/compute/section_compute-scheduler.xml272(para) +msgid "" +"Filters hosts based on properties defined on the instance's image. It passes" +" hosts that can support the specified image properties contained in the " +"instance. Properties include the architecture, hypervisor type, and virtual " +"machine mode. for example, an instance might require a host that runs an " +"ARM-based processor and QEMU as the hypervisor. An image can be decorated " +"with these properties by using:" +msgstr "" + +#: ./doc/config-reference/compute/section_compute-scheduler.xml281(para) +msgid "The image properties that the filter checks for are:" +msgstr "" + +#: ./doc/config-reference/compute/section_compute-scheduler.xml285(para) +msgid "" +"architecture: Architecture describes the machine " +"architecture required by the image. Examples are i686, x86_64, arm, and " +"ppc64." +msgstr "" + +#: ./doc/config-reference/compute/section_compute-scheduler.xml291(para) +msgid "" +"hypervisor_type: Hypervisor type describes the hypervisor" +" required by the image. Examples are xen, kvm, qemu, and xenapi." +msgstr "" + +#: ./doc/config-reference/compute/section_compute-scheduler.xml297(para) +msgid "" +"vm_mode: Virtual machine mode describes the hypervisor " +"application binary interface (ABI) required by the image. Examples are 'xen'" +" for Xen 3.0 paravirtual ABI, 'hvm' for native ABI, 'uml' for User Mode " +"Linux paravirtual ABI, exe for container virt executable ABI." +msgstr "" + +#: ./doc/config-reference/compute/section_compute-scheduler.xml308(title) +msgid "IsolatedHostsFilter" +msgstr "" + +#: ./doc/config-reference/compute/section_compute-scheduler.xml309(para) +msgid "" +"Allows the admin to define a special (isolated) set of images and a special " +"(isolated) set of hosts, such that the isolated images can only run on the " +"isolated hosts, and the isolated hosts can only run isolated images. The " +"flag restrict_isolated_hosts_to_isolated_images can be " +"used to force isolated hosts to only run isolated images." +msgstr "" + +#: ./doc/config-reference/compute/section_compute-scheduler.xml315(para) +msgid "" +"The admin must specify the isolated set of images and hosts in the " +"nova.conf file using the " +"isolated_hosts and isolated_images " +"configuration options. For example: " +msgstr "" + +#: ./doc/config-reference/compute/section_compute-scheduler.xml325(title) +msgid "JsonFilter" +msgstr "" + +#: ./doc/config-reference/compute/section_compute-scheduler.xml330(para) +msgid "=" +msgstr "" + +#: ./doc/config-reference/compute/section_compute-scheduler.xml333(para) +msgid "<" +msgstr "" + +#: ./doc/config-reference/compute/section_compute-scheduler.xml336(para) +msgid ">" +msgstr "" + +#: ./doc/config-reference/compute/section_compute-scheduler.xml339(para) +msgid "in" +msgstr "" + +#: ./doc/config-reference/compute/section_compute-scheduler.xml342(para) +msgid "<=" +msgstr "" + +#: ./doc/config-reference/compute/section_compute-scheduler.xml345(para) +msgid ">=" +msgstr "" + +#: ./doc/config-reference/compute/section_compute-scheduler.xml348(para) +msgid "not" +msgstr "" + +#: ./doc/config-reference/compute/section_compute-scheduler.xml351(para) +msgid "or" +msgstr "" + +#: ./doc/config-reference/compute/section_compute-scheduler.xml354(para) +msgid "and" +msgstr "" + +#: ./doc/config-reference/compute/section_compute-scheduler.xml358(para) +msgid "$free_ram_mb" +msgstr "" + +#: ./doc/config-reference/compute/section_compute-scheduler.xml361(para) +msgid "$free_disk_mb" +msgstr "" + +#: ./doc/config-reference/compute/section_compute-scheduler.xml364(para) +msgid "$total_usable_ram_mb" +msgstr "" + +#: ./doc/config-reference/compute/section_compute-scheduler.xml367(para) +msgid "$vcpus_total" +msgstr "" + +#: ./doc/config-reference/compute/section_compute-scheduler.xml370(para) +msgid "$vcpus_used" +msgstr "" + +#: ./doc/config-reference/compute/section_compute-scheduler.xml326(para) +msgid "" +"The JsonFilter allows a user to construct a custom filter by passing a " +"scheduler hint in JSON format. The following operators are " +"supported:The filter supports the following " +"variables:Using the command-line tool, use " +"the --hint flag:" +msgstr "" + +#: ./doc/config-reference/compute/section_compute-scheduler.xml377(para) +#: ./doc/config-reference/compute/section_compute-scheduler.xml436(para) +#: ./doc/config-reference/compute/section_compute-scheduler.xml482(para) +msgid "With the API, use the os:scheduler_hints key:" +msgstr "" + +#: ./doc/config-reference/compute/section_compute-scheduler.xml393(title) +msgid "RamFilter" +msgstr "" + +#: ./doc/config-reference/compute/section_compute-scheduler.xml394(para) +msgid "" +"Only schedule instances on hosts that have sufficient RAM available. If this" +" filter is not set, the scheduler may over provision a host based on RAM " +"(for example, the RAM allocated by virtual machine instances may exceed the " +"physical RAM)." +msgstr "" + +#: ./doc/config-reference/compute/section_compute-scheduler.xml399(para) +msgid "" +"This filter can be configured to allow a fixed amount of RAM overcommitment " +"by using the ram_allocation_ratio configuration option in" +" nova.conf. The default setting is:" +msgstr "" + +#: ./doc/config-reference/compute/section_compute-scheduler.xml406(para) +msgid "" +"With this setting, if there is 1GB of free RAM, the scheduler allows " +"instances up to size 1.5GB to be run on that instance." +msgstr "" + +#: ./doc/config-reference/compute/section_compute-scheduler.xml411(title) +msgid "RetryFilter" +msgstr "" + +#: ./doc/config-reference/compute/section_compute-scheduler.xml412(para) +msgid "" +"Filter out hosts that have already been attempted for scheduling purposes. " +"If the scheduler selects a host to respond to a service request, and the " +"host fails to respond to the request, this filter prevents the scheduler " +"from retrying that host for the service request." +msgstr "" + +#: ./doc/config-reference/compute/section_compute-scheduler.xml417(para) +msgid "" +"This filter is only useful if the scheduler_max_attempts " +"configuration option is set to a value greater than zero." +msgstr "" + +#: ./doc/config-reference/compute/section_compute-scheduler.xml423(title) +msgid "SameHostFilter" +msgstr "" + +#: ./doc/config-reference/compute/section_compute-scheduler.xml424(para) +msgid "" +"Schedule the instance on the same host as another instance in a set of " +"instances. To take advantage of this filter, the requester must pass a " +"scheduler hint, using same_host as the key and a list of " +"instance uuids as the value. This filter is the opposite of the " +"DifferentHostFilter. Using the command-" +"line tool, use the --hint flag:" +msgstr "" + +#: ./doc/config-reference/compute/section_compute-scheduler.xml453(title) +msgid "SimpleCIDRAffinityFilter" +msgstr "" + +#: ./doc/config-reference/compute/section_compute-scheduler.xml454(para) +msgid "" +"Schedule the instance based on host IP subnet range. To take advantage of " +"this filter, the requester must specify a range of valid IP address in CIDR " +"format, by passing two scheduler hints:" +msgstr "" + +#: ./doc/config-reference/compute/section_compute-scheduler.xml460(literal) +msgid "build_near_host_ip" +msgstr "" + +#: ./doc/config-reference/compute/section_compute-scheduler.xml462(para) +msgid "" +"The first IP address in the subnet (for example, " +"192.168.1.1)" +msgstr "" + +#: ./doc/config-reference/compute/section_compute-scheduler.xml468(literal) +msgid "cidr" +msgstr "" + +#: ./doc/config-reference/compute/section_compute-scheduler.xml470(para) +msgid "" +"The CIDR that corresponds to the subnet (for example, " +"/24)" +msgstr "" + +#: ./doc/config-reference/compute/section_compute-scheduler.xml476(para) +msgid "" +"Using the command-line tool, use the " +"--hint flag. For example, to specify the IP subnet " +"192.168.1.1/24" +msgstr "" + +#: ./doc/config-reference/compute/section_compute-scheduler.xml499(title) +msgid "Weights" +msgstr "" + +#: ./doc/config-reference/compute/section_compute-scheduler.xml501(para) +msgid "" +"The Filter Scheduler weighs hosts based on the config option " +"scheduler_weight_classes, this defaults to " +"nova.scheduler.weights.all_weighers, which selects the " +"only weigher available -- the RamWeigher. Hosts are then weighed and sorted " +"with the largest weight winning." +msgstr "" + +#: ./doc/config-reference/compute/section_compute-scheduler.xml510(para) +msgid "" +"The default is to spread instances across all hosts evenly. Set the " +"ram_weight_multiplier option to a negative number if you " +"prefer stacking instead of spreading." +msgstr "" + +#: ./doc/config-reference/compute/section_compute-scheduler.xml516(title) +msgid "Chance scheduler" +msgstr "" + +#: ./doc/config-reference/compute/section_compute-scheduler.xml518(para) +msgid "" +"As an administrator, you work with the Filter Scheduler. However, the " +"Compute service also uses the Chance Scheduler, " +"nova.scheduler.chance.ChanceScheduler, which randomly " +"selects from lists of filtered hosts. It is the default volume scheduler." +msgstr "" + +#: ./doc/config-reference/compute/section_compute-cells.xml10(title) +msgid "Cells" +msgstr "" + +#: ./doc/config-reference/compute/section_compute-cells.xml12(para) +msgid "" +"Cells functionality allows you to scale" +" an OpenStack Compute cloud in a more distributed fashion without having to " +"use complicated technologies like database and message queue clustering. It " +"is intended to support very large deployments." +msgstr "" + +#: ./doc/config-reference/compute/section_compute-cells.xml16(para) +msgid "" +"When this functionality is enabled, the hosts in an OpenStack Compute cloud " +"are partitioned into groups called cells. Cells are configured as a tree. " +"The top-level cell should have a host that runs a nova-api service, but no nova-compute services. Each child cell should" +" run all of the typical nova-* " +"services in a regular Compute cloud except for nova-api. You can think of cells as a normal Compute " +"deployment in that each cell has its own database server and message queue " +"broker." +msgstr "" + +#: ./doc/config-reference/compute/section_compute-cells.xml24(para) +msgid "" +"The nova-cells service handles " +"communication between cells and selects cells for new instances. This " +"service is required for every cell. Communication between cells is " +"pluggable, and currently the only option is communication through RPC." +msgstr "" + +#: ./doc/config-reference/compute/section_compute-cells.xml28(para) +msgid "" +"Cells scheduling is separate from host scheduling. nova-cells first picks a cell (now randomly, " +"but future releases plan to add filtering/weighing functionality, and " +"decisions will be based on broadcasts of capacity/capabilities). Once a cell" +" is selected and the new build request reaches its nova-cells service, it is sent over to the " +"host scheduler in that cell and the build proceeds as it would have without " +"cells." +msgstr "" + +#: ./doc/config-reference/compute/section_compute-cells.xml35(para) +msgid "Cell functionality is currently considered experimental." +msgstr "" + +#: ./doc/config-reference/compute/section_compute-cells.xml38(title) +msgid "Cell configuration options" +msgstr "" + +#: ./doc/config-reference/compute/section_compute-cells.xml43(literal) +msgid "enable" +msgstr "" + +#: ./doc/config-reference/compute/section_compute-cells.xml45(para) +msgid "" +"Set this is True to turn on cell functionality, which is " +"off by default." +msgstr "" + +#: ./doc/config-reference/compute/section_compute-cells.xml50(literal) +msgid "name" +msgstr "" + +#: ./doc/config-reference/compute/section_compute-cells.xml52(para) +msgid "Name of the current cell. This must be unique for each cell." +msgstr "" + +#: ./doc/config-reference/compute/section_compute-cells.xml56(literal) +msgid "capabilities" +msgstr "" + +#: ./doc/config-reference/compute/section_compute-cells.xml58(para) +msgid "" +"List of arbitrary " +"key=value" +" pairs defining capabilities of the current cell. Values include " +"hypervisor=xenserver;kvm,os=linux;windows." +msgstr "" + +#: ./doc/config-reference/compute/section_compute-cells.xml66(literal) +msgid "call_timeout" +msgstr "" + +#: ./doc/config-reference/compute/section_compute-cells.xml68(para) +msgid "How long in seconds to wait for replies from calls between cells." +msgstr "" + +#: ./doc/config-reference/compute/section_compute-cells.xml73(term) +msgid "scheduler_filter_classes" +msgstr "" + +#: ./doc/config-reference/compute/section_compute-cells.xml75(para) +msgid "" +"Filter classes that the cells scheduler should use. By default, uses " +"\"nova.cells.filters.all_filters\" to map to all cells " +"filters included with Compute." +msgstr "" + +#: ./doc/config-reference/compute/section_compute-cells.xml81(term) +msgid "scheduler_weight_classes" +msgstr "" + +#: ./doc/config-reference/compute/section_compute-cells.xml82(para) +msgid "" +"Weight classes the cells scheduler should use. By default, uses " +"\"nova.cells.weights.all_weighers\" to map to all cells " +"weight algorithms (weighers) included with Compute." +msgstr "" + +#: ./doc/config-reference/compute/section_compute-cells.xml88(term) +msgid "ram_weight_multiplier" +msgstr "" + +#: ./doc/config-reference/compute/section_compute-cells.xml90(para) +msgid "" +"Multiplier used for weighing ram. Negative numbers mean you want Compute to " +"stack VMs on one host instead of spreading out new VMs to more hosts in the " +"cell. Default value is 10.0." +msgstr "" + +#: ./doc/config-reference/compute/section_compute-cells.xml39(para) +msgid "" +"Cells are disabled by default. All cell-related configuration options go " +"under a [cells] section in " +"nova.conf. The following cell-related options are " +"currently supported:" +msgstr "" + +#: ./doc/config-reference/compute/section_compute-cells.xml99(title) +msgid "Configure the API (top-level) cell" +msgstr "" + +#: ./doc/config-reference/compute/section_compute-cells.xml100(para) +msgid "" +"The compute API class must be changed in the API cell so that requests can " +"be proxied through nova-cells down to the correct cell properly. Add the " +"following to nova.conf in the API cell:" +msgstr "" + +#: ./doc/config-reference/compute/section_compute-cells.xml112(title) +msgid "Configure the child cells" +msgstr "" + +#: ./doc/config-reference/compute/section_compute-cells.xml121(replaceable) +msgid "cell1" +msgstr "" + +#: ./doc/config-reference/compute/section_compute-cells.xml113(para) +msgid "" +"Add the following to nova.conf in the child cells, " +"replacing cell1 with the name of each " +"cell:" +msgstr "" + +#: ./doc/config-reference/compute/section_compute-cells.xml124(title) +msgid "Configure the database in each cell" +msgstr "" + +#: ./doc/config-reference/compute/section_compute-cells.xml125(para) +msgid "" +"Before bringing the services online, the database in each cell needs to be " +"configured with information about related cells. In particular, the API cell" +" needs to know about its immediate children, and the child cells must know " +"about their immediate agents. The information needed is the " +"RabbitMQ server credentials for the particular " +"cell." +msgstr "" + +#: ./doc/config-reference/compute/section_compute-cells.xml130(para) +msgid "" +"Use the command to add this information to the database in " +"each cell:" +msgstr "" + +#: ./doc/config-reference/compute/section_compute-cells.xml152(para) +msgid "" +"As an example, assume we have an API cell named api and a" +" child cell named cell1. Within the api cell, we have the" +" following RabbitMQ server info:" +msgstr "" + +#: ./doc/config-reference/compute/section_compute-cells.xml160(para) +msgid "" +"And in the child cell named cell1 we have the following " +"RabbitMQ server info:" +msgstr "" + +#: ./doc/config-reference/compute/section_compute-cells.xml167(para) +msgid "We would run this in the API cell, as root." +msgstr "" + +#: ./doc/config-reference/compute/section_compute-cells.xml169(para) +msgid "Repeat the above for all child cells." +msgstr "" + +#: ./doc/config-reference/compute/section_compute-cells.xml170(para) +msgid "" +"In the child cell, we would run the following, as root:" +msgstr "" + +#: ./doc/config-reference/compute/section_compute-cells.xml176(title) +msgid "Cell scheduling configuration" +msgstr "" + +#: ./doc/config-reference/compute/section_compute-cells.xml177(para) +msgid "" +"To determine the best cell for launching a new instance, Compute uses a set " +"of filters and weights configured in " +"/etc/nova/nova.conf. The following options are " +"available to prioritize cells for scheduling:" +msgstr "" + +#: ./doc/config-reference/compute/section_compute-cells.xml183(para) +msgid "" +"scheduler_filter_classes - Specifies the list of filter " +"classes. By default nova.cells.weights.all_filters is " +"specified, which maps to all cells filters included with Compute (see ." +msgstr "" + +#: ./doc/config-reference/compute/section_compute-cells.xml189(para) +msgid "" +"scheduler_weight_classes - Specifies the list of weight " +"classes. By default nova.cells.weights.all_weighers is " +"specified, which maps to all cell weight algorithms (weighers) included with" +" Compute. The following modules are available:" +msgstr "" + +#: ./doc/config-reference/compute/section_compute-cells.xml194(para) +msgid "" +"mute_child: Downgrades the likelihood of child cells being " +"chosen for scheduling requests, which haven't sent capacity or capability " +"updates in a while. Options include mute_weight_multiplier " +"(multiplier for mute children; value should be negative) and " +"mute_weight_value (assigned to mute children; should be a " +"positive value)." +msgstr "" + +#: ./doc/config-reference/compute/section_compute-cells.xml203(para) +msgid "" +"ram_by_instance_type: Select cells with the most RAM capacity " +"for the instance type being requested. Because higher weights win, Compute " +"returns the number of available units for the instance type requested. The " +"ram_weight_multiplier option defaults to 10.0 that adds to the " +"weight by a factor of 10. Use a negative number to stack VMs on one host " +"instead of spreading out new VMs to more hosts in the cell." +msgstr "" + +#: ./doc/config-reference/compute/section_compute-cells.xml211(para) +msgid "" +"weight_offset: Allows modifying the database to weight a " +"particular cell. You can use this when you want to disable a cell (for " +"example, '0'), or to set a default cell by making its weight_offset very " +"high (for example, '999999999999999'). The highest weight will be the first " +"cell to be scheduled for launching an instance." +msgstr "" + +#: ./doc/config-reference/compute/section_compute-cells.xml219(para) +msgid "" +"Additionally, the following options are available for the cell scheduler:" +msgstr "" + +#: ./doc/config-reference/compute/section_compute-cells.xml223(para) +msgid "" +"scheduler_retries - Specifies how many times the scheduler " +"tries to launch a new instance when no cells are available (default=10)." +msgstr "" + +#: ./doc/config-reference/compute/section_compute-cells.xml227(para) +msgid "" +"scheduler_retry_delay - Specifies the delay (in seconds) " +"between retries (default=2)." +msgstr "" + +#: ./doc/config-reference/compute/section_compute-cells.xml232(para) +msgid "" +"As an admin user, you can also add a filter that directs builds to a " +"particular cell. The policy.json file must have a line " +"with \"cells_scheduler_filter:TargetCellFilter\" : " +"\"is_admin:True\" to let an admin user specify a scheduler hint to" +" direct a build to a particular cell." +msgstr "" + +#: ./doc/config-reference/compute/section_compute-cells.xml239(title) +msgid "Optional cell configuration" +msgstr "" + +#: ./doc/config-reference/compute/section_compute-cells.xml240(para) +msgid "" +"Cells currently keeps all inter-cell communication data, including user " +"names and passwords, in the database. This is undesirable and unnecessary " +"since cells data isn't updated very frequently. Instead, create a JSON file " +"to input cells data specified via a [cells]cells_config option." +" When specified, the database is no longer consulted when reloading cells " +"data. The file will need the columns present in the Cell model (excluding " +"common database fields and the id column). The queue connection" +" information must be specified through a transport_url field, " +"instead of username, password, and so on. The " +"transport_url has the following form:" +msgstr "" + +#: ./doc/config-reference/compute/section_compute-cells.xml255(para) +msgid "" +"The scheme can be either qpid or " +"rabbit, as shown previously. The following sample shows " +"this optional configuration:" +msgstr "" + +#: ./doc/config-reference/compute/section_compute-security.xml10(title) +msgid "Security hardening" +msgstr "" + +#: ./doc/config-reference/compute/section_compute-security.xml11(para) +msgid "" +"OpenStack Compute can be integrated with various third-party technologies to" +" increase security. For more information, see the OpenStack Security " +"Guide." +msgstr "" + +#: ./doc/config-reference/compute/section_hypervisor_qemu.xml7(title) +msgid "QEMU" +msgstr "" + +#: ./doc/config-reference/compute/section_hypervisor_qemu.xml8(para) +msgid "" +"From the perspective of the Compute service, the QEMU hypervisor is very " +"similar to the KVM hypervisor. Both are controlled through libvirt, both " +"support the same feature set, and all virtual machine images that are " +"compatible with KVM are also compatible with QEMU. The main difference is " +"that QEMU does not support native virtualization. Consequently, QEMU has " +"worse performance than KVM and is a poor choice for a production deployment." +msgstr "" + +#: ./doc/config-reference/compute/section_hypervisor_qemu.xml15(para) +msgid "Running on older hardware that lacks virtualization support." +msgstr "" + +#: ./doc/config-reference/compute/section_hypervisor_qemu.xml19(para) +msgid "" +"Running the Compute service inside of a virtual machine for development or " +"testing purposes, where the hypervisor does not support native " +"virtualization for guests." +msgstr "" + +#: ./doc/config-reference/compute/section_hypervisor_qemu.xml13(para) +msgid "The typical uses cases for QEMU are" +msgstr "" + +#: ./doc/config-reference/compute/section_hypervisor_qemu.xml25(para) +msgid "" +"To enable QEMU, add these settings to " +"nova.conf:" +msgstr "" + +#: ./doc/config-reference/compute/section_hypervisor_qemu.xml29(para) +msgid "" +"For some operations you may also have to install the " +"utility:" +msgstr "" + +#: ./doc/config-reference/compute/section_hypervisor_qemu.xml31(para) +msgid "On Ubuntu: " +msgstr "" + +#: ./doc/config-reference/compute/section_hypervisor_qemu.xml34(para) +msgid "On RHEL, Fedora or CentOS: " +msgstr "" + +#: ./doc/config-reference/compute/section_hypervisor_qemu.xml37(para) +msgid "On openSUSE: " +msgstr "" + +#: ./doc/config-reference/compute/section_hypervisor_qemu.xml40(para) +msgid "" +"The QEMU hypervisor supports the following virtual machine image formats:" +msgstr "" + +#: ./doc/config-reference/compute/section_hypervisor_qemu.xml53(title) +msgid "Tips and fixes for QEMU on RHEL" +msgstr "" + +#: ./doc/config-reference/compute/section_hypervisor_qemu.xml54(para) +msgid "" +"If you are testing OpenStack in a virtual machine, you need to configure " +"nova to use qemu without KVM and hardware virtualization. The second command" +" relaxes SELinux rules to allow this mode of operation ( " +"https://bugzilla.redhat.com/show_bug.cgi?id=753589). The last two " +"commands here work around a libvirt issue fixed in RHEL 6.4. Note nested " +"virtualization will be the much slower TCG variety, and you should provide " +"lots of memory to the top level guest, as the OpenStack-created guests " +"default to 2GM RAM with no overcommit." +msgstr "" + +#: ./doc/config-reference/compute/section_hypervisor_qemu.xml65(para) +msgid "The second command, , may take a while." +msgstr "" + +#: ./doc/config-reference/compute/section_compute-configure-migrations.xml10(title) +msgid "Configure migrations" +msgstr "" + +#: ./doc/config-reference/compute/section_compute-configure-migrations.xml12(para) +msgid "" +"Only cloud administrators can perform live migrations. If your cloud is " +"configured to use cells, you can perform live migration within but not " +"between cells." +msgstr "" + +#: ./doc/config-reference/compute/section_compute-configure-migrations.xml16(para) +msgid "" +"Migration enables an administrator to move a virtual machine instance from " +"one compute host to another. This feature is useful when a compute host " +"requires maintenance. Migration can also be useful to redistribute the load " +"when many VM instances are running on a specific physical machine." +msgstr "" + +#: ./doc/config-reference/compute/section_compute-configure-migrations.xml21(para) +msgid "The migration types are:" +msgstr "" + +#: ./doc/config-reference/compute/section_compute-configure-migrations.xml24(para) +msgid "" +"Migration (or non-live migration). The " +"instance is shut down (and the instance knows that it was rebooted) for a " +"period of time to be moved to another hypervisor." +msgstr "" + +#: ./doc/config-reference/compute/section_compute-configure-migrations.xml30(para) +msgid "" +"Live migration (or true live migration). " +"Almost no instance downtime. Useful when the instances must be kept running " +"during the migration." +msgstr "" + +#: ./doc/config-reference/compute/section_compute-configure-migrations.xml35(para) +msgid "The types of live migration are:" +msgstr "" + +#: ./doc/config-reference/compute/section_compute-configure-migrations.xml38(para) +msgid "" +"Shared storage-based live migration. Both" +" hypervisors have access to shared storage." +msgstr "" + +#: ./doc/config-reference/compute/section_compute-configure-migrations.xml43(para) +msgid "" +"Block live migration. No shared storage " +"is required." +msgstr "" + +#: ./doc/config-reference/compute/section_compute-configure-migrations.xml47(para) +msgid "" +"Volume-backed live migration. When " +"instances are backed by volumes rather than ephemeral disk, no shared " +"storage is required, and migration is supported (currently only in libvirt-" +"based hypervisors)." +msgstr "" + +#: ./doc/config-reference/compute/section_compute-configure-migrations.xml54(para) +msgid "" +"The following sections describe how to configure your hosts and compute " +"nodes for migrations by using the KVM and XenServer hypervisors." +msgstr "" + +#: ./doc/config-reference/compute/section_compute-configure-migrations.xml58(title) +msgid "KVM-Libvirt" +msgstr "" + +#: ./doc/config-reference/compute/section_compute-configure-migrations.xml60(title) +#: ./doc/config-reference/compute/section_compute-configure-migrations.xml293(title) +#: ./doc/config-reference/compute/section_compute-configure-migrations.xml368(title) +#: ./doc/config-reference/block-storage/drivers/xen-sm-driver.xml117(title) +msgid "Prerequisites" +msgstr "" + +#: ./doc/config-reference/compute/section_compute-configure-migrations.xml62(para) +msgid "Hypervisor: KVM with libvirt" +msgstr "" + +#: ./doc/config-reference/compute/section_compute-configure-migrations.xml66(para) +msgid "" +"Shared storage:NOVA-INST-DIR/instances/ (for example, " +"/var/lib/nova/instances) has to be mounted by shared " +"storage. This guide uses NFS but other options, including the OpenStack" +" Gluster Connector are available." +msgstr "" + +#: ./doc/config-reference/compute/section_compute-configure-migrations.xml75(para) +msgid "" +"Instances: Instance can be migrated with " +"iSCSI based volumes" +msgstr "" + +#: ./doc/config-reference/compute/section_compute-configure-migrations.xml80(title) +#: ./doc/config-reference/compute/section_compute-configure-migrations.xml377(title) +msgid "Notes" +msgstr "" + +#: ./doc/config-reference/compute/section_compute-configure-migrations.xml83(para) +msgid "" +"Because the Compute service does not use the libvirt live migration " +"functionality by default, guests are suspended before migration and might " +"experience several minutes of downtime. For details, see ." +msgstr "" + +#: ./doc/config-reference/compute/section_compute-configure-migrations.xml90(para) +msgid "" +"This guide assumes the default value for in " +"your nova.conf file (NOVA-INST-" +"DIR/instances). If you have changed the " +"state_path or instances_path " +"variables, modify accordingly." +msgstr "" + +#: ./doc/config-reference/compute/section_compute-configure-migrations.xml99(para) +msgid "" +"You must specify vncserver_listen=0.0.0.0 or live " +"migration does not work correctly." +msgstr "" + +#: ./doc/config-reference/compute/section_compute-configure-migrations.xml106(title) +msgid "Example Compute installation environment" +msgstr "" + +#: ./doc/config-reference/compute/section_compute-configure-migrations.xml108(para) +msgid "" +"Prepare at least three servers; for example, HostA, " +"HostB, and HostC." +msgstr "" + +#: ./doc/config-reference/compute/section_compute-configure-migrations.xml113(para) +msgid "" +"HostA is the Cloud Controller, and should run these services: " +"nova-api, nova-scheduler, nova-" +"network, cinder-volume," +" and nova-objectstore." +msgstr "" + +#: ./doc/config-reference/compute/section_compute-configure-migrations.xml123(para) +msgid "" +"HostB and HostC are the compute nodes that run nova-compute." +msgstr "" + +#: ./doc/config-reference/compute/section_compute-configure-migrations.xml129(para) +msgid "" +"Ensure that NOVA-INST-DIR (set" +" with state_path in the nova.conf " +"file) is the same on all hosts." +msgstr "" + +#: ./doc/config-reference/compute/section_compute-configure-migrations.xml136(para) +msgid "" +"In this example, HostA is the NFSv4 server that exports " +"NOVA-INST-DIR/instances, and" +" HostB and HostC mount it." +msgstr "" + +#: ./doc/config-reference/compute/section_compute-configure-migrations.xml144(title) +msgid "To configure your system" +msgstr "" + +#: ./doc/config-reference/compute/section_compute-configure-migrations.xml146(para) +msgid "" +"Configure your DNS or /etc/hosts and ensure it is " +"consistent across all hosts. Make sure that the three hosts can perform name" +" resolution with each other. As a test, use the command to " +"ping each host from one another." +msgstr "" + +#: ./doc/config-reference/compute/section_compute-configure-migrations.xml156(para) +msgid "" +"Ensure that the UID and GID of your nova and libvirt users are identical " +"between each of your servers. This ensures that the permissions on the NFS " +"mount works correctly." +msgstr "" + +#: ./doc/config-reference/compute/section_compute-configure-migrations.xml162(para) +msgid "" +"Follow the instructions at the Ubuntu NFS " +"HowTo to setup an NFS server on HostA, and NFS Clients on" +" HostB and HostC." +msgstr "" + +#: ./doc/config-reference/compute/section_compute-configure-migrations.xml168(para) +msgid "" +"The aim is to export NOVA-INST-" +"DIR/instances from HostA, and " +"have it readable and writable by the nova user on HostB " +"and HostC." +msgstr "" + +#: ./doc/config-reference/compute/section_compute-configure-migrations.xml175(para) +msgid "" +"Using your knowledge from the Ubuntu documentation, configure the NFS server" +" at HostA by adding this line to the " +"/etc/exports file:" +msgstr "" + +#: ./doc/config-reference/compute/section_compute-configure-migrations.xml179(replaceable) +#: ./doc/config-reference/compute/section_compute-configure-migrations.xml194(replaceable) +#: ./doc/config-reference/compute/section_compute-configure-migrations.xml199(replaceable) +#: ./doc/config-reference/compute/section_compute-configure-migrations.xml206(replaceable) +#: ./doc/config-reference/compute/section_compute-configure-migrations.xml211(replaceable) +msgid "NOVA-INST-DIR" +msgstr "" + +#: ./doc/config-reference/compute/section_compute-configure-migrations.xml180(para) +msgid "" +"Change the subnet mask (255.255.0.0) to the appropriate " +"value to include the IP addresses of HostB and " +"HostC. Then restart the NFS server:" +msgstr "" + +#: ./doc/config-reference/compute/section_compute-configure-migrations.xml188(para) +msgid "Set the 'execute/search' bit on your shared directory." +msgstr "" + +#: ./doc/config-reference/compute/section_compute-configure-migrations.xml190(para) +msgid "" +"On both compute nodes, make sure to enable the 'execute/search' bit to allow" +" qemu to be able to use the images within the directories. On all hosts, run" +" the following command:" +msgstr "" + +#: ./doc/config-reference/compute/section_compute-configure-migrations.xml197(para) +msgid "" +"Configure NFS at HostB and HostC by adding this line to the " +"/etc/fstab file:" +msgstr "" + +#: ./doc/config-reference/compute/section_compute-configure-migrations.xml200(para) +msgid "Make sure that you can mount the exported directory can be mounted:" +msgstr "" + +#: ./doc/config-reference/compute/section_compute-configure-migrations.xml203(para) +msgid "" +"Check that HostA can see the \"NOVA-INST-" +"DIR/instances/\" directory:" +msgstr "" + +#: ./doc/config-reference/compute/section_compute-configure-migrations.xml206(filename) +#: ./doc/config-reference/compute/section_compute-configure-migrations.xml211(filename) +msgid "/instances/" +msgstr "" + +#: ./doc/config-reference/compute/section_compute-configure-migrations.xml208(para) +msgid "" +"Perform the same check at HostB and HostC, paying special attention to the " +"permissions (nova should be able to write):" +msgstr "" + +#: ./doc/config-reference/compute/section_compute-configure-migrations.xml224(para) +msgid "" +"Update the libvirt configurations. Modify the " +"/etc/libvirt/libvirtd.conf file:" +msgstr "" + +#: ./doc/config-reference/compute/section_compute-configure-migrations.xml234(para) +msgid "Modify the /etc/libvirt/qemu.conf file:" +msgstr "" + +#: ./doc/config-reference/compute/section_compute-configure-migrations.xml238(para) +msgid "Modify the /etc/init/libvirt-bin.conf file:" +msgstr "" + +#: ./doc/config-reference/compute/section_compute-configure-migrations.xml243(para) +msgid "Modify the /etc/default/libvirt-bin file:" +msgstr "" + +#: ./doc/config-reference/compute/section_compute-configure-migrations.xml247(para) +msgid "" +"Restart libvirt. After you run the command, ensure that libvirt is " +"successfully restarted:" +msgstr "" + +#: ./doc/config-reference/compute/section_compute-configure-migrations.xml254(para) +msgid "Configure your firewall to allow libvirt to communicate between nodes." +msgstr "" + +#: ./doc/config-reference/compute/section_compute-configure-migrations.xml256(para) +msgid "" +"For information about ports that are used with libvirt, see the " +"libvirt documentation By default, libvirt listens on TCP port 16509 " +"and an ephemeral TCP range from 49152 to 49261 is used for the KVM " +"communications. As this guide has disabled libvirt auth, you should take " +"good care that these ports are only open to hosts within your installation." +msgstr "" + +#: ./doc/config-reference/compute/section_compute-configure-migrations.xml267(para) +msgid "" +"You can now configure options for live migration. In most cases, you do not " +"need to configure any options. The following chart is for advanced usage " +"only." +msgstr "" + +#: ./doc/config-reference/compute/section_compute-configure-migrations.xml274(title) +msgid "Enable true live migration" +msgstr "" + +#: ./doc/config-reference/compute/section_compute-configure-migrations.xml275(para) +msgid "" +"By default, the Compute service does not use the libvirt live migration " +"functionality. To enable this functionality, add the following line to the " +"nova.conf file:" +msgstr "" + +#: ./doc/config-reference/compute/section_compute-configure-migrations.xml280(para) +msgid "" +"The Compute service does not use libvirt's live migration by default because" +" there is a risk that the migration process never ends. This can happen if " +"the guest operating system dirties blocks on the disk faster than they can " +"migrated." +msgstr "" + +#: ./doc/config-reference/compute/section_compute-configure-migrations.xml291(title) +msgid "Shared storage" +msgstr "" + +#: ./doc/config-reference/compute/section_compute-configure-migrations.xml295(para) +msgid "" +"Compatible XenServer hypervisors. For " +"more information, see the Requirements" +" for Creating Resource Pools section of the XenServer " +"Administrator's Guide." +msgstr "" + +#: ./doc/config-reference/compute/section_compute-configure-migrations.xml304(para) +msgid "" +"Shared storage. An NFS export, visible to" +" all XenServer hosts." +msgstr "" + +#: ./doc/config-reference/compute/section_compute-configure-migrations.xml307(para) +msgid "" +"For the supported NFS versions, see the NFS" +" VHD section of the XenServer Administrator's " +"Guide." +msgstr "" + +#: ./doc/config-reference/compute/section_compute-configure-migrations.xml314(para) +msgid "" +"To use shared storage live migration with XenServer hypervisors, the hosts " +"must be joined to a XenServer pool. To create that pool, a host aggregate " +"must be created with special metadata. This metadata is used by the XAPI " +"plug-ins to establish the pool." +msgstr "" + +#: ./doc/config-reference/compute/section_compute-configure-migrations.xml320(title) +msgid "To use shared storage live migration with XenServer hypervisors" +msgstr "" + +#: ./doc/config-reference/compute/section_compute-configure-migrations.xml323(para) +msgid "" +"Add an NFS VHD storage to your master XenServer, and set it as default SR. " +"For more information, please refer to the NFS" +" VHD section in the XenServer Administrator's " +"Guide." +msgstr "" + +#: ./doc/config-reference/compute/section_compute-configure-migrations.xml331(para) +msgid "" +"Configure all the compute nodes to use the default sr for pool operations. " +"Add this line to your nova.conf configuration files " +"across your compute nodes:" +msgstr "" + +#: ./doc/config-reference/compute/section_compute-configure-migrations.xml338(para) +msgid "Create a host aggregate:" +msgstr "" + +#: ./doc/config-reference/compute/section_compute-configure-migrations.xml340(para) +msgid "" +"The command displays a table that contains the ID of the newly created " +"aggregate." +msgstr "" + +#: ./doc/config-reference/compute/section_compute-configure-migrations.xml342(para) +msgid "" +"Now add special metadata to the aggregate, to mark it as a hypervisor pool:" +msgstr "" + +#: ./doc/config-reference/compute/section_compute-configure-migrations.xml346(para) +msgid "Make the first compute node part of that aggregate:" +msgstr "" + +#: ./doc/config-reference/compute/section_compute-configure-migrations.xml349(para) +msgid "At this point, the host is part of a XenServer pool." +msgstr "" + +#: ./doc/config-reference/compute/section_compute-configure-migrations.xml353(para) +msgid "Add additional hosts to the pool:" +msgstr "" + +#: ./doc/config-reference/compute/section_compute-configure-migrations.xml356(para) +msgid "" +"At this point, the added compute node and the host are shut down, to join " +"the host to the XenServer pool. The operation fails, if any server other " +"than the compute node is running/suspended on your host." +msgstr "" + +#: ./doc/config-reference/compute/section_compute-configure-migrations.xml366(title) +msgid "Block migration" +msgstr "" + +#: ./doc/config-reference/compute/section_compute-configure-migrations.xml370(para) +msgid "" +"Compatible XenServer hypervisors. The " +"hypervisors must support the Storage XenMotion feature. See your XenServer " +"manual to make sure your edition has this feature." +msgstr "" + +#: ./doc/config-reference/compute/section_compute-configure-migrations.xml380(para) +msgid "" +"To use block migration, you must use the --block-" +"migrate parameter with the live migration command." +msgstr "" + +#: ./doc/config-reference/compute/section_compute-configure-migrations.xml385(para) +msgid "" +"Block migration works only with EXT local storage SRs, and the server must " +"not have any volumes attached." +msgstr "" + +#: ./doc/config-reference/networking/section_networking-plugins.xml10(title) +msgid "Networking plug-ins" +msgstr "" + +#: ./doc/config-reference/networking/section_networking-plugins.xml11(para) +msgid "" +"OpenStack Networking introduces the concept of a plug-in, which is a back-" +"end implementation of the OpenStack Networking API. A plug-in can use a " +"variety of technologies to implement the logical API requests. Some " +"OpenStack Networking plug-ins might use basic Linux VLANs and IP tables, " +"while others might use more advanced technologies, such as L2-in-L3 " +"tunneling or OpenFlow. These sections detail the configuration options for " +"the various plug-ins." +msgstr "" + +#: ./doc/config-reference/networking/section_networking-plugins.xml22(title) +msgid "BigSwitch configuration options" +msgstr "" + +#: ./doc/config-reference/networking/section_networking-plugins.xml28(title) +msgid "Brocade configuration options" +msgstr "" + +#: ./doc/config-reference/networking/section_networking-plugins.xml34(title) +msgid "CISCO configuration options" +msgstr "" + +#: ./doc/config-reference/networking/section_networking-plugins.xml40(title) +msgid "CloudBase Hyper-V plug-in configuration options (deprecated)" +msgstr "" + +#: ./doc/config-reference/networking/section_networking-plugins.xml47(title) +msgid "CloudBase Hyper-V Agent configuration options" +msgstr "" + +#: ./doc/config-reference/networking/section_networking-plugins.xml54(title) +msgid "Linux bridge plug-in configuration options (deprecated)" +msgstr "" + +#: ./doc/config-reference/networking/section_networking-plugins.xml61(title) +msgid "Linux bridge Agent configuration options" +msgstr "" + +#: ./doc/config-reference/networking/section_networking-plugins.xml68(title) +msgid "Mellanox configuration options" +msgstr "" + +#: ./doc/config-reference/networking/section_networking-plugins.xml74(title) +msgid "Meta Plug-in configuration options" +msgstr "" + +#: ./doc/config-reference/networking/section_networking-plugins.xml75(para) +msgid "The Meta Plug-in allows you to use multiple plug-ins at the same time." +msgstr "" + +#: ./doc/config-reference/networking/section_networking-plugins.xml83(title) +msgid "MidoNet configuration options" +msgstr "" + +#: ./doc/config-reference/networking/section_networking-plugins.xml89(title) +msgid "NEC configuration options" +msgstr "" + +#: ./doc/config-reference/networking/section_networking-plugins.xml95(title) +msgid "Nicira NVP configuration options" +msgstr "" + +#: ./doc/config-reference/networking/section_networking-plugins.xml101(title) +msgid "Open vSwitch plug-in configuration options (deprecated)" +msgstr "" + +#: ./doc/config-reference/networking/section_networking-plugins.xml108(title) +msgid "Open vSwitch Agent configuration options" +msgstr "" + +#: ./doc/config-reference/networking/section_networking-plugins.xml115(title) +msgid "PLUMgrid configuration options" +msgstr "" + +#: ./doc/config-reference/networking/section_networking-plugins.xml121(title) +msgid "Ryu configuration options" +msgstr "" + +#: ./doc/config-reference/networking/section_networking-plugins-ml2.xml10(title) +msgid "Modular Layer 2 (ml2) configuration options" +msgstr "" + +#: ./doc/config-reference/networking/section_networking-plugins-ml2.xml11(para) +msgid "" +"The Modular Layer 2 (ml2) plug-in has two components: network types and " +"mechanisms. You can configure these components separately. This section " +"describes these configuration options." +msgstr "" + +#: ./doc/config-reference/networking/section_networking-plugins-ml2.xml16(title) +msgid "MTU bug with VXLAN tunnelling" +msgstr "" + +#: ./doc/config-reference/networking/section_networking-plugins-ml2.xml17(para) +msgid "" +"Due to a bug in Linux Bridge software maximum transmission unit (MTU) " +"handling, using VXLAN tunnels does not work by default." +msgstr "" + +#: ./doc/config-reference/networking/section_networking-plugins-ml2.xml22(para) +msgid "" +"A simple workaround is to increase the MTU value of the physical interface " +"and physical switch fabric by at least 50 bytes. For example, increase the " +"MTU value to 1550. This value enables an automatic 50-byte MTU difference " +"between the physical interface (1500) and the VXLAN interface (automatically" +" 1500-50 = 1450). An MTU value of 1450 causes issues when virtual machine " +"taps are configured at an MTU value of 1500." +msgstr "" + +#: ./doc/config-reference/networking/section_networking-plugins-ml2.xml33(para) +msgid "" +"Another workaround is to decrease the virtual ethernet devices' MTU. Set the" +" option to 1450 in the " +"neutron.conf file, and set all guest virtual machines' " +"MTU to the same value by using a DHCP option. For information about how to " +"use this option, see Configure OVS plug-" +"in." +msgstr "" + +#: ./doc/config-reference/networking/section_networking-plugins-ml2.xml48(title) +msgid "Modular Layer 2 (ml2) Flat Type configuration options" +msgstr "" + +#: ./doc/config-reference/networking/section_networking-plugins-ml2.xml53(title) +msgid "Modular Layer 2 (ml2) VXLAN Type configuration options" +msgstr "" + +#: ./doc/config-reference/networking/section_networking-plugins-ml2.xml58(title) +msgid "Modular Layer 2 (ml2) Arista Mechanism configuration options" +msgstr "" + +#: ./doc/config-reference/networking/section_networking-plugins-ml2.xml64(title) +msgid "Modular Layer 2 (ml2) Cisco Mechanism configuration options" +msgstr "" + +#: ./doc/config-reference/networking/section_networking-plugins-ml2.xml69(title) +msgid "Modular Layer 2 (ml2) L2 Population Mechanism configuration options" +msgstr "" + +#: ./doc/config-reference/networking/section_networking-plugins-ml2.xml74(title) +msgid "Modular Layer 2 (ml2) Tail-f NCS Mechanism configuration options" +msgstr "" + +#: ./doc/config-reference/networking/section_networking-options-reference.xml6(title) +msgid "Networking configuration options" +msgstr "" + +#: ./doc/config-reference/networking/section_networking-options-reference.xml7(para) +msgid "" +"The options and descriptions listed in this introduction are auto generated " +"from the code in the Networking service project, which provides software-" +"defined networking between VMs run in Compute. The list contains common " +"options, while the subsections list the options for the various networking " +"plug-ins." +msgstr "" + +#: ./doc/config-reference/networking/section_networking-options-reference.xml20(para) +msgid "Use the following options to alter agent-related settings." +msgstr "" + +#: ./doc/config-reference/networking/section_networking-options-reference.xml25(title) +msgid "API" +msgstr "" + +#: ./doc/config-reference/networking/section_networking-options-reference.xml26(para) +msgid "Use the following options to alter API-related settings." +msgstr "" + +#: ./doc/config-reference/networking/section_networking-options-reference.xml31(title) +msgid "Database" +msgstr "" + +#: ./doc/config-reference/networking/section_networking-options-reference.xml32(para) +msgid "Use the following options to alter Database-related settings." +msgstr "" + +#: ./doc/config-reference/networking/section_networking-options-reference.xml37(title) +msgid "Logging" +msgstr "" + +#: ./doc/config-reference/networking/section_networking-options-reference.xml38(para) +msgid "Use the following options to alter logging settings." +msgstr "" + +#: ./doc/config-reference/networking/section_networking-options-reference.xml43(title) +msgid "Metadata Agent" +msgstr "" + +#: ./doc/config-reference/networking/section_networking-options-reference.xml44(para) +msgid "" +"Use the following options in the metadata_agent.ini " +"file for the Metadata agent." +msgstr "" + +#: ./doc/config-reference/networking/section_networking-options-reference.xml50(title) +msgid "Policy" +msgstr "" + +#: ./doc/config-reference/networking/section_networking-options-reference.xml51(para) +msgid "" +"Use the following options in the neutron.conf file to " +"change policy settings." +msgstr "" + +#: ./doc/config-reference/networking/section_networking-options-reference.xml57(title) +msgid "Quotas" +msgstr "" + +#: ./doc/config-reference/networking/section_networking-options-reference.xml58(para) +msgid "" +"Use the following options in the neutron.conf file for " +"the quota system." +msgstr "" + +#: ./doc/config-reference/networking/section_networking-options-reference.xml64(title) +msgid "Scheduler" +msgstr "" + +#: ./doc/config-reference/networking/section_networking-options-reference.xml65(para) +msgid "" +"Use the following options in the neutron.conf file to " +"change scheduler settings." +msgstr "" + +#: ./doc/config-reference/networking/section_networking-options-reference.xml71(title) +msgid "Security Groups" +msgstr "" + +#: ./doc/config-reference/networking/section_networking-options-reference.xml72(para) +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.xml78(title) +msgid "SSL" +msgstr "" + +#: ./doc/config-reference/networking/section_networking-options-reference.xml79(para) +msgid "" +"Use the following options in the neutron.conf file to " +"enable SSL." +msgstr "" + +#: ./doc/config-reference/networking/section_networking-options-reference.xml85(title) +msgid "Testing" +msgstr "" + +#: ./doc/config-reference/networking/section_networking-options-reference.xml86(para) +msgid "Use the following options to alter testing-related features." +msgstr "" + +#: ./doc/config-reference/networking/section_networking-options-reference.xml91(title) +msgid "WSGI" +msgstr "" + +#: ./doc/config-reference/networking/section_networking-options-reference.xml92(para) +msgid "" +"Use the following options in the neutron.conf file to " +"configure the WSGI layer." +msgstr "" + +#: ./doc/config-reference/block-storage/section_backup-drivers.xml6(title) +msgid "Backup drivers" +msgstr "" + +#: ./doc/config-reference/block-storage/section_backup-drivers.xml7(para) +msgid "" +"This section describes how to configure the cinder-backup service and its drivers." +msgstr "" + +#: ./doc/config-reference/block-storage/section_backup-drivers.xml10(para) +msgid "" +"The volume drivers are included with the Block Storage repository (https://github.com/openstack/cinder)." +" To set a backup driver, use the backup_driver flag. By " +"default there is no backup driver enabled." +msgstr "" + +#: ./doc/config-reference/block-storage/section_volume-drivers.xml6(title) +msgid "Volume drivers" +msgstr "" + +#: ./doc/config-reference/block-storage/section_volume-drivers.xml7(para) +msgid "" +"To use different volume drivers for the cinder-volume service, use the parameters described in these" +" sections." +msgstr "" + +#: ./doc/config-reference/block-storage/section_volume-drivers.xml10(para) +msgid "" +"The volume drivers are included in the Block Storage repository (https://github.com/openstack/cinder)." +" To set a volume driver, use the volume_driver flag. The " +"default is:" +msgstr "" + +#: ./doc/config-reference/block-storage/section_block-storage-overview.xml6(title) +msgid "Introduction to the Block Storage Service" +msgstr "" + +#: ./doc/config-reference/block-storage/section_block-storage-overview.xml7(para) +msgid "" +"The Openstack Block Storage Service provides persistent block storage " +"resources that OpenStack Compute instances can consume. This includes " +"secondary attached storage similar to the Amazon Elastic Block Storage (EBS)" +" offering. In addition, you can write images to a Block Storage device for " +"Compute to use as a bootable persistent instance." +msgstr "" + +#: ./doc/config-reference/block-storage/section_block-storage-overview.xml14(para) +msgid "" +"The Block Storage Service differs slightly from the Amazon EBS offering. The" +" Block Storage Service does not provide a shared storage solution like NFS. " +"With the Block Storage Service, you can attach a device to only one " +"instance." +msgstr "" + +#: ./doc/config-reference/block-storage/section_block-storage-overview.xml19(para) +msgid "The Block Storage Service provides:" +msgstr "" + +#: ./doc/config-reference/block-storage/section_block-storage-overview.xml22(para) +msgid "" +"cinder-api. A WSGI app that " +"authenticates and routes requests throughout the Block Storage Service. It " +"supports the OpenStack APIs only, although there is a translation that can " +"be done through Compute's EC2 interface, which calls in to the cinderclient." +msgstr "" + +#: ./doc/config-reference/block-storage/section_block-storage-overview.xml30(para) +msgid "" +"cinder-scheduler. Schedules and " +"routes requests to the appropriate volume service. As of Grizzly; depending " +"upon your configuration this may be simple round-robin scheduling to the " +"running volume services, or it can be more sophisticated through the use of " +"the Filter Scheduler. The Filter Scheduler is the default in Grizzly and " +"enables filters on things like Capacity, Availability Zone, Volume Types, " +"and Capabilities as well as custom filters." +msgstr "" + +#: ./doc/config-reference/block-storage/section_block-storage-overview.xml38(para) +msgid "" +"cinder-volume. Manages Block " +"Storage devices, specifically the back-end devices themselves." +msgstr "" + +#: ./doc/config-reference/block-storage/section_block-storage-overview.xml43(para) +msgid "" +"cinder-backup Provides a means to" +" back up a Block Storage Volume to OpenStack Object Store (SWIFT)." +msgstr "" + +#: ./doc/config-reference/block-storage/section_block-storage-overview.xml48(para) +msgid "The Block Storage Service contains the following components:" +msgstr "" + +#: ./doc/config-reference/block-storage/section_block-storage-overview.xml52(para) +msgid "" +"Back-end Storage Devices. The Block " +"Storage Service requires some form of back-end storage that the service is " +"built on. The default implementation is to use LVM on a local volume group " +"named \"cinder-volumes.\" In addition to the base driver implementation, the" +" Block Storage Service also provides the means to add support for other " +"storage devices to be utilized such as external Raid Arrays or other storage" +" appliances. These back-end storage devices may have custom block sizes when" +" using KVM or QEMU as the hypervisor." +msgstr "" + +#: ./doc/config-reference/block-storage/section_block-storage-overview.xml65(para) +msgid "" +"Users and Tenants (Projects). The Block " +"Storage Service is designed to be used by many different cloud computing " +"consumers or customers, basically tenants on a shared system, using role-" +"based access assignments. Roles control the actions that a user is allowed " +"to perform. In the default configuration, most actions do not require a " +"particular role, but this is configurable by the system administrator " +"editing the appropriate policy.json file that maintains" +" the rules. A user's access to particular volumes is limited by tenant, but " +"the username and password are assigned per user. Key pairs granting access " +"to a volume are enabled per user, but quotas to control resource consumption" +" across available hardware resources are per tenant." +msgstr "" + +#: ./doc/config-reference/block-storage/section_block-storage-overview.xml81(para) +msgid "For tenants, quota controls are available to limit:" +msgstr "" + +#: ./doc/config-reference/block-storage/section_block-storage-overview.xml85(para) +msgid "The number of volumes that can be created" +msgstr "" + +#: ./doc/config-reference/block-storage/section_block-storage-overview.xml89(para) +msgid "The number of snapshots that can be created" +msgstr "" + +#: ./doc/config-reference/block-storage/section_block-storage-overview.xml93(para) +msgid "" +"The total number of GBs allowed per tenant (shared between snapshots and " +"volumes)" +msgstr "" + +#: ./doc/config-reference/block-storage/section_block-storage-overview.xml97(para) +msgid "" +"You can revise the default quota values with the cinder CLI, so the limits " +"placed by quotas are editable by admin users." +msgstr "" + +#: ./doc/config-reference/block-storage/section_block-storage-overview.xml100(para) +msgid "" +"Volumes, Snapshots, and Backups. The " +"basic resources offered by the Block Storage Service are volumes and " +"snapshots, which are derived from volumes, and backups:" +msgstr "" + +#: ./doc/config-reference/block-storage/section_block-storage-overview.xml107(para) +msgid "" +"Volumes. Allocated block storage " +"resources that can be attached to instances as secondary storage or they can" +" be used as the root store to boot instances. Volumes are persistent R/W " +"block storage devices most commonly attached to the Compute node through " +"iSCSI." +msgstr "" + +#: ./doc/config-reference/block-storage/section_block-storage-overview.xml116(para) +msgid "" +"Snapshots. A read-only point in time copy" +" of a volume. The snapshot can be created from a volume that is currently in" +" use (through the use of '--force True') or in an available state. The " +"snapshot can then be used to create a new volume through create from " +"snapshot." +msgstr "" + +#: ./doc/config-reference/block-storage/section_block-storage-overview.xml125(para) +msgid "" +"Backups. An archived copy of a volume " +"currently stored in OpenStack Object Storage (Swift)." +msgstr "" + +#: ./doc/config-reference/block-storage/drivers/vmware-vmdk-driver.xml6(title) +msgid "VMware VMDK driver" +msgstr "" + +#: ./doc/config-reference/block-storage/drivers/vmware-vmdk-driver.xml7(para) +msgid "" +"Use the VMware VMDK driver to enable management of the OpenStack Block " +"Storage volumes on vCenter-managed data stores. Volumes are backed by VMDK " +"files on data stores using any VMware-compatible storage technology such as " +"NFS, iSCSI, FiberChannel, and vSAN." +msgstr "" + +#: ./doc/config-reference/block-storage/drivers/vmware-vmdk-driver.xml13(title) +#: ./doc/config-reference/block-storage/drivers/xen-sm-driver.xml134(title) +#: ./doc/config-reference/block-storage/drivers/hds-volume-driver.xml72(title) +msgid "Configuration" +msgstr "" + +#: ./doc/config-reference/block-storage/drivers/vmware-vmdk-driver.xml14(para) +msgid "" +"The recommended volume driver for OpenStack Block Storage is the VMware " +"vCenter VMDK driver. When you configure the driver, you must match it with " +"the appropriate OpenStack Compute driver from VMware and both drivers must " +"point to the same server." +msgstr "" + +#: ./doc/config-reference/block-storage/drivers/vmware-vmdk-driver.xml19(para) +msgid "" +"For example, in the nova.conf file, use this option to " +"define the Compute driver:" +msgstr "" + +#: ./doc/config-reference/block-storage/drivers/vmware-vmdk-driver.xml22(para) +msgid "" +"In the cinder.conf file, use this option to define the " +"volume driver:" +msgstr "" + +#: ./doc/config-reference/block-storage/drivers/vmware-vmdk-driver.xml25(para) +msgid "" +"The following table lists various options that the drivers support for the " +"OpenStack Block Storage configuration (cinder.conf):" +msgstr "" + +#: ./doc/config-reference/block-storage/drivers/vmware-vmdk-driver.xml32(para) +msgid "" +"The VMware VMDK drivers support the creation of VMDK disk files of type " +"thin, thick, or " +"eagerZeroedThick. Use the vmware:vmdk_type " +"extra spec key with the appropriate value to specify the VMDK disk file " +"type. The following table captures the mapping between the extra spec entry " +"and the VMDK disk file type:" +msgstr "" + +#: ./doc/config-reference/block-storage/drivers/vmware-vmdk-driver.xml40(caption) +msgid "Extra spec entry to VMDK disk file type mapping" +msgstr "" + +#: ./doc/config-reference/block-storage/drivers/vmware-vmdk-driver.xml44(td) +msgid "Disk file type" +msgstr "" + +#: ./doc/config-reference/block-storage/drivers/vmware-vmdk-driver.xml45(td) +#: ./doc/config-reference/block-storage/drivers/vmware-vmdk-driver.xml94(td) +msgid "Extra spec key" +msgstr "" + +#: ./doc/config-reference/block-storage/drivers/vmware-vmdk-driver.xml46(td) +#: ./doc/config-reference/block-storage/drivers/vmware-vmdk-driver.xml95(td) +msgid "Extra spec value" +msgstr "" + +#: ./doc/config-reference/block-storage/drivers/vmware-vmdk-driver.xml52(td) +#: ./doc/config-reference/block-storage/drivers/vmware-vmdk-driver.xml57(td) +#: ./doc/config-reference/block-storage/drivers/vmware-vmdk-driver.xml62(td) +msgid "vmware:vmdk_type" +msgstr "" + +#: ./doc/config-reference/block-storage/drivers/vmware-vmdk-driver.xml56(td) +#: ./doc/config-reference/block-storage/drivers/vmware-vmdk-driver.xml58(td) +msgid "thick" +msgstr "" + +#: ./doc/config-reference/block-storage/drivers/vmware-vmdk-driver.xml61(td) +#: ./doc/config-reference/block-storage/drivers/vmware-vmdk-driver.xml63(td) +msgid "eagerZeroedThick" +msgstr "" + +#: ./doc/config-reference/block-storage/drivers/vmware-vmdk-driver.xml67(para) +msgid "" +"If no vmdk_type extra spec entry is specified, the default disk" +" file type is thin." +msgstr "" + +#: ./doc/config-reference/block-storage/drivers/vmware-vmdk-driver.xml70(para) +msgid "" +"The example below shows how to create a thick VMDK volume using" +" the appropriate vmdk_type:" +msgstr "" + +#: ./doc/config-reference/block-storage/drivers/vmware-vmdk-driver.xml80(title) +#: ./doc/config-reference/block-storage/drivers/vmware-vmdk-driver.xml93(td) +msgid "Clone type" +msgstr "" + +#: ./doc/config-reference/block-storage/drivers/vmware-vmdk-driver.xml81(para) +msgid "" +"With the VMware VMDK drivers, you can create a volume from another source " +"volume or from a snapshot point. The VMware vCenter VMDK driver supports " +"clone types full and linked/fast. The " +"clone type is specified using the vmware:clone_type extra spec " +"key with the appropriate value. The following table captures the mapping for" +" clone types:" +msgstr "" + +#: ./doc/config-reference/block-storage/drivers/vmware-vmdk-driver.xml90(caption) +msgid "Extra spec entry to clone type mapping" +msgstr "" + +#: ./doc/config-reference/block-storage/drivers/vmware-vmdk-driver.xml100(td) +#: ./doc/config-reference/block-storage/drivers/vmware-vmdk-driver.xml102(td) +msgid "full" +msgstr "" + +#: ./doc/config-reference/block-storage/drivers/vmware-vmdk-driver.xml101(td) +#: ./doc/config-reference/block-storage/drivers/vmware-vmdk-driver.xml106(td) +msgid "vmware:clone_type" +msgstr "" + +#: ./doc/config-reference/block-storage/drivers/vmware-vmdk-driver.xml105(td) +msgid "linked/fast" +msgstr "" + +#: ./doc/config-reference/block-storage/drivers/vmware-vmdk-driver.xml107(td) +msgid "linked" +msgstr "" + +#: ./doc/config-reference/block-storage/drivers/vmware-vmdk-driver.xml111(para) +msgid "If not specified, the default clone type is full." +msgstr "" + +#: ./doc/config-reference/block-storage/drivers/vmware-vmdk-driver.xml113(para) +msgid "" +"The following is an example of linked cloning from another source volume:" +msgstr "" + +#: ./doc/config-reference/block-storage/drivers/vmware-vmdk-driver.xml120(para) +msgid "" +"Note: The VMware ESX VMDK driver ignores the extra spec entry and always " +"creates a full clone." +msgstr "" + +#: ./doc/config-reference/block-storage/drivers/vmware-vmdk-driver.xml125(title) +#: ./doc/config-reference/block-storage/drivers/huawei-storage-driver.xml13(title) +#: ./doc/config-reference/block-storage/drivers/emc-volume-driver.xml31(title) +#: ./doc/config-reference/block-storage/drivers/hp-3par-driver.xml42(title) +msgid "Supported operations" +msgstr "" + +#: ./doc/config-reference/block-storage/drivers/vmware-vmdk-driver.xml126(para) +msgid "" +"The following operations are supported by the VMware vCenter and ESX VMDK " +"drivers:" +msgstr "" + +#: ./doc/config-reference/block-storage/drivers/vmware-vmdk-driver.xml130(para) +#: ./doc/config-reference/block-storage/drivers/huawei-storage-driver.xml17(para) +#: ./doc/config-reference/block-storage/drivers/huawei-storage-driver.xml48(para) +#: ./doc/config-reference/block-storage/drivers/huawei-storage-driver.xml74(para) +#: ./doc/config-reference/block-storage/drivers/huawei-storage-driver.xml93(para) +#: ./doc/config-reference/block-storage/drivers/emc-volume-driver.xml36(para) +#: ./doc/config-reference/block-storage/drivers/hds-volume-driver.xml30(para) +msgid "Create volume" +msgstr "" + +#: ./doc/config-reference/block-storage/drivers/vmware-vmdk-driver.xml133(para) +msgid "" +"Create volume from another source volume. (Supported only if source volume " +"is not attached to an instance.)" +msgstr "" + +#: ./doc/config-reference/block-storage/drivers/vmware-vmdk-driver.xml138(para) +#: ./doc/config-reference/block-storage/drivers/huawei-storage-driver.xml35(para) +#: ./doc/config-reference/block-storage/drivers/huawei-storage-driver.xml111(para) +#: ./doc/config-reference/block-storage/drivers/emc-volume-driver.xml66(para) +#: ./doc/config-reference/block-storage/drivers/hds-volume-driver.xml60(para) +msgid "Create volume from snapshot" +msgstr "" + +#: ./doc/config-reference/block-storage/drivers/vmware-vmdk-driver.xml141(para) +msgid "Create volume from glance image" +msgstr "" + +#: ./doc/config-reference/block-storage/drivers/vmware-vmdk-driver.xml144(para) +msgid "" +"Attach volume (When a volume is attached to an instance, a reconfigure " +"operation is performed on the instance to add the volume's VMDK to it. The " +"user must manually rescan and mount the device from within the guest " +"operating system.)" +msgstr "" + +#: ./doc/config-reference/block-storage/drivers/vmware-vmdk-driver.xml151(para) +#: ./doc/config-reference/block-storage/drivers/huawei-storage-driver.xml26(para) +#: ./doc/config-reference/block-storage/drivers/huawei-storage-driver.xml57(para) +#: ./doc/config-reference/block-storage/drivers/huawei-storage-driver.xml83(para) +#: ./doc/config-reference/block-storage/drivers/huawei-storage-driver.xml102(para) +#: ./doc/config-reference/block-storage/drivers/emc-volume-driver.xml45(para) +#: ./doc/config-reference/block-storage/drivers/hds-volume-driver.xml39(para) +msgid "Detach volume" +msgstr "" + +#: ./doc/config-reference/block-storage/drivers/vmware-vmdk-driver.xml154(para) +msgid "" +"Create snapshot (Allowed only if volume is not attached to an instance.)" +msgstr "" + +#: ./doc/config-reference/block-storage/drivers/vmware-vmdk-driver.xml158(para) +msgid "" +"Delete snapshot (Allowed only if volume is not attached to an instance.)" +msgstr "" + +#: ./doc/config-reference/block-storage/drivers/vmware-vmdk-driver.xml162(para) +msgid "" +"Upload as image to glance (Allowed only if volume is not attached to an " +"instance.)" +msgstr "" + +#: ./doc/config-reference/block-storage/drivers/vmware-vmdk-driver.xml167(para) +msgid "" +"Although the VMware ESX VMDK driver supports these operations, it has not " +"been extensively tested." +msgstr "" + +#: ./doc/config-reference/block-storage/drivers/vmware-vmdk-driver.xml172(title) +msgid "Data store selection" +msgstr "" + +#: ./doc/config-reference/block-storage/drivers/vmware-vmdk-driver.xml173(para) +msgid "" +"When creating a volume, the driver chooses a data store that has sufficient " +"free space and has the highest freespace/totalspace " +"metric value." +msgstr "" + +#: ./doc/config-reference/block-storage/drivers/vmware-vmdk-driver.xml177(para) +msgid "" +"When a volume is attached to an instance, the driver attempts to place the " +"volume under the instance's ESX host on a data store that is selected using " +"the strategy above." +msgstr "" + +#: ./doc/config-reference/block-storage/drivers/nexenta-volume-driver.xml4(title) +msgid "Nexenta drivers" +msgstr "" + +#: ./doc/config-reference/block-storage/drivers/nexenta-volume-driver.xml5(para) +msgid "" +"NexentaStor Appliance is NAS/SAN software platform designed for building " +"reliable and fast network storage arrays. The Nexenta Storage Appliance uses" +" ZFS as a disk management system. NexentaStor can serve as a storage node " +"for the OpenStack and for the virtual servers through iSCSI and NFS " +"protocols." +msgstr "" + +#: ./doc/config-reference/block-storage/drivers/nexenta-volume-driver.xml11(para) +msgid "" +"With the NFS option, every Compute volume is represented by a directory " +"designated to be its own file system in the ZFS file system. These file " +"systems are exported using NFS." +msgstr "" + +#: ./doc/config-reference/block-storage/drivers/nexenta-volume-driver.xml14(para) +msgid "" +"With either option some minimal setup is required to tell OpenStack which " +"NexentaStor servers are being used, whether they are supporting iSCSI and/or" +" NFS and how to access each of the servers." +msgstr "" + +#: ./doc/config-reference/block-storage/drivers/nexenta-volume-driver.xml18(para) +msgid "" +"Typically the only operation required on the NexentaStor servers is to " +"create the containing directory for the iSCSI or NFS exports. For NFS this " +"containing directory must be explicitly exported via NFS. There is no " +"software that must be installed on the NexentaStor servers; they are " +"controlled using existing management plane interfaces." +msgstr "" + +#: ./doc/config-reference/block-storage/drivers/nexenta-volume-driver.xml26(title) +msgid "Nexenta iSCSI driver" +msgstr "" + +#: ./doc/config-reference/block-storage/drivers/nexenta-volume-driver.xml27(para) +msgid "" +"The Nexenta iSCSI driver allows you to use NexentaStor appliance to store " +"Compute volumes. Every Compute volume is represented by a single zvol in a " +"predefined Nexenta namespace. For every new volume the driver creates a " +"iSCSI target and iSCSI target group that are used to access it from compute " +"hosts." +msgstr "" + +#: ./doc/config-reference/block-storage/drivers/nexenta-volume-driver.xml33(para) +msgid "" +"The Nexenta iSCSI volume driver should work with all versions of " +"NexentaStor. The NexentaStor appliance must be installed and configured " +"according to the relevant Nexenta documentation. A pool and an enclosing " +"namespace must be created for all iSCSI volumes to be accessed through the " +"volume driver. This should be done as specified in the release specific " +"NexentaStor documentation." +msgstr "" + +#: ./doc/config-reference/block-storage/drivers/nexenta-volume-driver.xml40(para) +msgid "" +"The NexentaStor Appliance iSCSI driver is selected using the normal " +"procedures for one or multiple back-end volume drivers. You must configure " +"these items for each NexentaStor appliance that the iSCSI volume driver " +"controls:" +msgstr "" + +#: ./doc/config-reference/block-storage/drivers/nexenta-volume-driver.xml46(title) +msgid "Enable the Nexenta iSCSI driver and related options" +msgstr "" + +#: ./doc/config-reference/block-storage/drivers/nexenta-volume-driver.xml48(para) +msgid "This table contains the options supported by the Nexenta iSCSI driver." +msgstr "" + +#: ./doc/config-reference/block-storage/drivers/nexenta-volume-driver.xml52(para) +msgid "" +"To use Compute with the Nexenta iSCSI driver, first set the " +"volume_driver:" +msgstr "" + +#: ./doc/config-reference/block-storage/drivers/nexenta-volume-driver.xml56(para) +msgid "" +"Then, set the nexenta_host parameter and other parameters from " +"the table, if needed." +msgstr "" + +#: ./doc/config-reference/block-storage/drivers/nexenta-volume-driver.xml63(title) +msgid "Nexenta NFS driver" +msgstr "" + +#: ./doc/config-reference/block-storage/drivers/nexenta-volume-driver.xml64(para) +msgid "" +"The Nexenta NFS driver allows you to use NexentaStor appliance to store " +"Compute volumes via NFS. Every Compute volume is represented by a single NFS" +" file within a shared directory." +msgstr "" + +#: ./doc/config-reference/block-storage/drivers/nexenta-volume-driver.xml68(para) +msgid "" +"While the NFS protocols standardize file access for users, they do not " +"standardize administrative actions such as taking snapshots or replicating " +"file systems. The Openstack Volume Drivers bring a common interface to these" +" operations. The Nexenta NFS driver implements these standard actions using " +"the ZFS management plane that already is deployed on NexentaStor appliances." +msgstr "" + +#: ./doc/config-reference/block-storage/drivers/nexenta-volume-driver.xml75(para) +msgid "" +"The Nexenta NFS volume driver should work with all versions of NexentaStor. " +"The NexentaStor appliance must be installed and configured according to the " +"relevant Nexenta documentation. A single parent file system must be created " +"for all virtual disk directories supported for OpenStack. This directory " +"must be created and exported on each NexentaStor appliance. This should be " +"done as specified in the release specific NexentaStor documentation." +msgstr "" + +#: ./doc/config-reference/block-storage/drivers/nexenta-volume-driver.xml84(title) +msgid "Enable the Nexenta NFS driver and related options" +msgstr "" + +#: ./doc/config-reference/block-storage/drivers/nexenta-volume-driver.xml86(para) +msgid "" +"To use Compute with the Nexenta NFS driver, first set the " +"volume_driver:" +msgstr "" + +#: ./doc/config-reference/block-storage/drivers/nexenta-volume-driver.xml91(para) +msgid "" +"The following table contains the options supported by the Nexenta NFS " +"driver." +msgstr "" + +#: ./doc/config-reference/block-storage/drivers/nexenta-volume-driver.xml95(para) +msgid "" +"Add your list of Nexenta NFS servers to the file you specified with the " +"nexenta_shares_config option. For example, if the value of this" +" option was set to /etc/cinder/nfs_shares, then:" +msgstr "" + +#: ./doc/config-reference/block-storage/drivers/nexenta-volume-driver.xml105(para) +msgid "Comments are allowed in this file. They begin with a #." +msgstr "" + +#: ./doc/config-reference/block-storage/drivers/nexenta-volume-driver.xml107(para) +msgid "" +"Each line in this file represents a NFS share. The first part of the line is" +" the NFS share URL, the second is the connection URL to the NexentaStor " +"Appliance." +msgstr "" + +#: ./doc/config-reference/block-storage/drivers/zadara-volume-driver.xml6(title) +msgid "Zadara" +msgstr "" + +#: ./doc/config-reference/block-storage/drivers/zadara-volume-driver.xml7(para) +msgid "" +"There is a volume back-end for Zadara. Set the following in your " +"cinder.conf, and use the following options to configure" +" it." +msgstr "" + +#. When image changes, this message will be marked fuzzy or untranslated for +#. you. +#. It doesn't matter what you translate it to: it's not used at all. +#: ./doc/config-reference/block-storage/drivers/coraid-driver.xml286(None) +msgid "" +"@@image: " +"'../../../common/figures/coraid/Repository_Creation_Plan_screen.png'; " +"md5=83038804978648c2db4001a46c11f8ba" +msgstr "" + +#: ./doc/config-reference/block-storage/drivers/coraid-driver.xml6(title) +msgid "Coraid AoE driver configuration" +msgstr "" + +#: ./doc/config-reference/block-storage/drivers/coraid-driver.xml7(para) +msgid "" +"Coraid storage appliances can provide block-level storage to OpenStack " +"instances. Coraid storage appliances use the low-latency ATA-over-Ethernet " +"(ATA) protocol to provide high-bandwidth data transfer between hosts and " +"data on the network." +msgstr "" + +#: ./doc/config-reference/block-storage/drivers/coraid-driver.xml11(para) +msgid "Once configured for OpenStack, you can:" +msgstr "" + +#: ./doc/config-reference/block-storage/drivers/coraid-driver.xml14(para) +msgid "Create, delete, attach, and detach block storage volumes." +msgstr "" + +#: ./doc/config-reference/block-storage/drivers/coraid-driver.xml18(para) +msgid "Create, list, and delete volume snapshots." +msgstr "" + +#: ./doc/config-reference/block-storage/drivers/coraid-driver.xml21(para) +msgid "" +"Create a volume from a snapshot, copy an image to a volume, copy a volume to" +" an image, clone a volume, and get volume statistics." +msgstr "" + +#: ./doc/config-reference/block-storage/drivers/coraid-driver.xml26(para) +msgid "" +"This document describes how to configure the OpenStack Block Storage Service" +" for use with Coraid storage appliances." +msgstr "" + +#: ./doc/config-reference/block-storage/drivers/coraid-driver.xml29(title) +msgid "Terminology" +msgstr "" + +#: ./doc/config-reference/block-storage/drivers/coraid-driver.xml30(para) +msgid "These terms are used in this section:" +msgstr "" + +#: ./doc/config-reference/block-storage/drivers/coraid-driver.xml34(th) +msgid "Term" +msgstr "" + +#: ./doc/config-reference/block-storage/drivers/coraid-driver.xml35(th) +msgid "Definition" +msgstr "" + +#: ./doc/config-reference/block-storage/drivers/coraid-driver.xml40(td) +msgid "AoE" +msgstr "" + +#: ./doc/config-reference/block-storage/drivers/coraid-driver.xml41(td) +msgid "ATA-over-Ethernet protocol" +msgstr "" + +#: ./doc/config-reference/block-storage/drivers/coraid-driver.xml44(td) +msgid "EtherCloud Storage Manager (ESM)" +msgstr "" + +#: ./doc/config-reference/block-storage/drivers/coraid-driver.xml45(td) +msgid "" +"ESM provides live monitoring and management of EtherDrive appliances that " +"use the AoE protocol, such as the SRX and VSX." +msgstr "" + +#: ./doc/config-reference/block-storage/drivers/coraid-driver.xml50(td) +msgid "Fully-Qualified Repository Name (FQRN)" +msgstr "" + +#: ./doc/config-reference/block-storage/drivers/coraid-driver.xml53(replaceable) +msgid "performance_class" +msgstr "" + +#: ./doc/config-reference/block-storage/drivers/coraid-driver.xml53(replaceable) +msgid "availability_class" +msgstr "" + +#: ./doc/config-reference/block-storage/drivers/coraid-driver.xml53(replaceable) +msgid "profile_name" +msgstr "" + +#: ./doc/config-reference/block-storage/drivers/coraid-driver.xml53(replaceable) +msgid "repository_name" +msgstr "" + +#: ./doc/config-reference/block-storage/drivers/coraid-driver.xml51(td) +msgid "" +"The FQRN is the full identifier of a storage profile. FQRN syntax is: " +"" +msgstr "" + +#: ./doc/config-reference/block-storage/drivers/coraid-driver.xml56(td) +msgid "SAN" +msgstr "" + +#: ./doc/config-reference/block-storage/drivers/coraid-driver.xml57(td) +msgid "Storage Area Network" +msgstr "" + +#: ./doc/config-reference/block-storage/drivers/coraid-driver.xml60(td) +msgid "SRX" +msgstr "" + +#: ./doc/config-reference/block-storage/drivers/coraid-driver.xml61(td) +msgid "Coraid EtherDrive SRX block storage appliance" +msgstr "" + +#: ./doc/config-reference/block-storage/drivers/coraid-driver.xml64(td) +msgid "VSX" +msgstr "" + +#: ./doc/config-reference/block-storage/drivers/coraid-driver.xml65(td) +msgid "Coraid EtherDrive VSX storage virtualization appliance" +msgstr "" + +#: ./doc/config-reference/block-storage/drivers/coraid-driver.xml72(title) +#: ./doc/config-reference/block-storage/drivers/xenapi-nfs.xml14(title) +msgid "Requirements" +msgstr "" + +#: ./doc/config-reference/block-storage/drivers/coraid-driver.xml73(para) +msgid "" +"To support the OpenStack Block Storage Service, your SAN must include an SRX" +" for physical storage, a VSX running at least CorOS v2.0.6 for snapshot " +"support, and an ESM running at least v2.1.1 for storage repository " +"orchestration. Ensure that all storage appliances are installed and " +"connected to your network before you configure OpenStack volumes." +msgstr "" + +#: ./doc/config-reference/block-storage/drivers/coraid-driver.xml79(para) +msgid "" +"So that the node can communicate with the SAN, you must install the Coraid " +"AoE Linux driver on each compute node on the network that runs an OpenStack " +"instance." +msgstr "" + +#: ./doc/config-reference/block-storage/drivers/coraid-driver.xml84(title) +msgid "Overview" +msgstr "" + +#: ./doc/config-reference/block-storage/drivers/coraid-driver.xml85(para) +msgid "" +"To configure the OpenStack Block Storage for use with Coraid storage " +"appliances, perform the following procedures:" +msgstr "" + +#: ./doc/config-reference/block-storage/drivers/coraid-driver.xml89(para) +msgid "" +"Download and install the " +"Coraid Linux AoE driver." +msgstr "" + +#: ./doc/config-reference/block-storage/drivers/coraid-driver.xml93(para) +msgid "" +"Create a storage profile " +"by using the Coraid ESM GUI." +msgstr "" + +#: ./doc/config-reference/block-storage/drivers/coraid-driver.xml97(para) +msgid "" +"Create a storage " +"repository by using the ESM GUI and record the FQRN." +msgstr "" + +#: ./doc/config-reference/block-storage/drivers/coraid-driver.xml102(para) +msgid "" +"Configure the " +"cinder.conf file." +msgstr "" + +#: ./doc/config-reference/block-storage/drivers/coraid-driver.xml106(para) +msgid "" +"Create and " +"associate a block storage volume type." +msgstr "" + +#: ./doc/config-reference/block-storage/drivers/coraid-driver.xml113(title) +msgid "Install the Coraid AoE driver" +msgstr "" + +#: ./doc/config-reference/block-storage/drivers/coraid-driver.xml114(para) +msgid "" +"Install the Coraid AoE driver on every compute node that will require access" +" to block storage." +msgstr "" + +#: ./doc/config-reference/block-storage/drivers/coraid-driver.xml116(para) +msgid "" +"The latest AoE drivers will always be located at http://support.coraid.com/support/linux/." +msgstr "" + +#: ./doc/config-reference/block-storage/drivers/coraid-driver.xml119(para) +msgid "" +"To download and install the AoE driver, follow the instructions below, " +"replacing “aoeXXX” with the AoE driver file name:" +msgstr "" + +#: ./doc/config-reference/block-storage/drivers/coraid-driver.xml124(para) +msgid "Download the latest Coraid AoE driver." +msgstr "" + +#: ./doc/config-reference/block-storage/drivers/coraid-driver.xml130(para) +msgid "Unpack the AoE driver." +msgstr "" + +#: ./doc/config-reference/block-storage/drivers/coraid-driver.xml133(para) +msgid "Install the AoE driver." +msgstr "" + +#: ./doc/config-reference/block-storage/drivers/coraid-driver.xml139(para) +msgid "Initialize the AoE driver." +msgstr "" + +#: ./doc/config-reference/block-storage/drivers/coraid-driver.xml145(para) +msgid "" +"Optionally, specify the Ethernet interfaces that the node can use to " +"communicate with the SAN." +msgstr "" + +#: ./doc/config-reference/block-storage/drivers/coraid-driver.xml147(para) +msgid "" +"The AoE driver may use every Ethernet interface available to the node unless" +" limited with the aoe_iflist parameter. For more " +"information about the aoe_iflist parameter, see the " +"aoe readme file included with the AoE driver." +msgstr "" + +#: ./doc/config-reference/block-storage/drivers/coraid-driver.xml154(replaceable) +msgid "eth1 eth2 ..." +msgstr "" + +#: ./doc/config-reference/block-storage/drivers/coraid-driver.xml160(title) +msgid "Create a storage profile" +msgstr "" + +#: ./doc/config-reference/block-storage/drivers/coraid-driver.xml161(para) +msgid "To create a storage profile using the ESM GUI:" +msgstr "" + +#: ./doc/config-reference/block-storage/drivers/coraid-driver.xml164(para) +msgid "Log in to the ESM." +msgstr "" + +#: ./doc/config-reference/block-storage/drivers/coraid-driver.xml167(para) +msgid "" +"Click Storage Profiles in the SAN " +"Domain pane." +msgstr "" + +#: ./doc/config-reference/block-storage/drivers/coraid-driver.xml171(para) +msgid "" +"Choose Menu > Create Storage Profile. If the " +"option is unavailable, you might not have appropriate permissions. Make sure" +" you are logged in to the ESM as the SAN administrator." +msgstr "" + +#: ./doc/config-reference/block-storage/drivers/coraid-driver.xml177(para) +msgid "Use the storage class selector to select a storage class." +msgstr "" + +#: ./doc/config-reference/block-storage/drivers/coraid-driver.xml179(para) +msgid "" +"Each storage class includes performance and availability criteria (see the " +"Storage Classes topic in the ESM Online Help for information on the " +"different options)." +msgstr "" + +#: ./doc/config-reference/block-storage/drivers/coraid-driver.xml184(para) +msgid "" +"Select a RAID type (if more than one is available) for the selected profile " +"type." +msgstr "" + +#: ./doc/config-reference/block-storage/drivers/coraid-driver.xml188(para) +msgid "Type a Storage Profile name." +msgstr "" + +#: ./doc/config-reference/block-storage/drivers/coraid-driver.xml189(para) +msgid "" +"The name is restricted to alphanumeric characters, underscore (_), and " +"hyphen (-), and cannot exceed 32 characters." +msgstr "" + +#: ./doc/config-reference/block-storage/drivers/coraid-driver.xml194(para) +msgid "Select the drive size from the drop-down menu." +msgstr "" + +#: ./doc/config-reference/block-storage/drivers/coraid-driver.xml197(para) +msgid "" +"Select the number of drives to be initialized for each RAID (LUN) from the " +"drop-down menu (if the selected RAID type requires multiple drives)." +msgstr "" + +#: ./doc/config-reference/block-storage/drivers/coraid-driver.xml202(para) +msgid "" +"Type the number of RAID sets (LUNs) you want to create in the repository by " +"using this profile." +msgstr "" + +#: ./doc/config-reference/block-storage/drivers/coraid-driver.xml206(para) +msgid "Click Next." +msgstr "" + +#: ./doc/config-reference/block-storage/drivers/coraid-driver.xml211(title) +msgid "Create a storage repository and get the FQRN" +msgstr "" + +#: ./doc/config-reference/block-storage/drivers/coraid-driver.xml212(para) +msgid "" +"Create a storage repository and get its fully qualified repository name " +"(FQRN):" +msgstr "" + +#: ./doc/config-reference/block-storage/drivers/coraid-driver.xml216(para) +msgid "Access the Create Storage Repository dialog box." +msgstr "" + +#: ./doc/config-reference/block-storage/drivers/coraid-driver.xml220(para) +msgid "Type a Storage Repository name." +msgstr "" + +#: ./doc/config-reference/block-storage/drivers/coraid-driver.xml221(para) +msgid "" +"The name is restricted to alphanumeric characters, underscore (_), hyphen " +"(-), and cannot exceed 32 characters." +msgstr "" + +#: ./doc/config-reference/block-storage/drivers/coraid-driver.xml226(para) +msgid "" +"Click Limited or Unlimited to " +"indicate the maximum repository size." +msgstr "" + +#: ./doc/config-reference/block-storage/drivers/coraid-driver.xml229(para) +msgid "" +"Limited sets the amount of space that can be " +"allocated to the repository. Specify the size in TB, GB, or MB." +msgstr "" + +#: ./doc/config-reference/block-storage/drivers/coraid-driver.xml232(para) +msgid "" +"When the difference between the reserved space and the space already " +"allocated to LUNs is less than is required by a LUN allocation request, the " +"reserved space is increased until the repository limit is reached." +msgstr "" + +#: ./doc/config-reference/block-storage/drivers/coraid-driver.xml237(para) +msgid "" +"The reserved space does not include space used for parity or space used for " +"mirrors. If parity and/or mirrors are required, the actual space allocated " +"to the repository from the SAN is greater than that specified in reserved " +"space." +msgstr "" + +#: ./doc/config-reference/block-storage/drivers/coraid-driver.xml243(para) +msgid "" +"Unlimited—Unlimited means that the amount" +" of space allocated to the repository is unlimited and additional space is " +"allocated to the repository automatically when space is required and " +"available." +msgstr "" + +#: ./doc/config-reference/block-storage/drivers/coraid-driver.xml249(para) +msgid "" +"Drives specified in the associated Storage Profile must be available on the " +"SAN in order to allocate additional resources." +msgstr "" + +#: ./doc/config-reference/block-storage/drivers/coraid-driver.xml255(para) +msgid "Check the Resizeable LUN box." +msgstr "" + +#: ./doc/config-reference/block-storage/drivers/coraid-driver.xml257(para) +msgid "This is required for OpenStack volumes." +msgstr "" + +#: ./doc/config-reference/block-storage/drivers/coraid-driver.xml259(para) +msgid "" +"If the Storage Profile associated with the repository has platinum " +"availability, the Resizeable LUN box is automatically checked." +msgstr "" + +#: ./doc/config-reference/block-storage/drivers/coraid-driver.xml265(para) +msgid "" +"Check the Show Allocation Plan API calls box. Click " +"Next." +msgstr "" + +#: ./doc/config-reference/block-storage/drivers/coraid-driver.xml270(para) +msgid "Record the FQRN and click Finish." +msgstr "" + +#: ./doc/config-reference/block-storage/drivers/coraid-driver.xml272(para) +msgid "" +"The FQRN is located in the first line of output following the " +"Plan keyword in the Repository Creation " +"Plan window. The FQRN syntax is " +"performance_classavailability_classprofile_namerepository_name." +msgstr "" + +#: ./doc/config-reference/block-storage/drivers/coraid-driver.xml277(para) +msgid "" +"In this example, the FQRN is Bronze-" +"Platinum:BP1000:OSTest, and is highlighted." +msgstr "" + +#: ./doc/config-reference/block-storage/drivers/coraid-driver.xml281(title) +msgid "Repository Creation Plan screen" +msgstr "" + +#: ./doc/config-reference/block-storage/drivers/coraid-driver.xml290(para) +msgid "" +"Record the FQRN; it is a required parameter later in the configuration " +"procedure." +msgstr "" + +#: ./doc/config-reference/block-storage/drivers/coraid-driver.xml296(title) +msgid "Configure options in the cinder.conf file" +msgstr "" + +#: ./doc/config-reference/block-storage/drivers/coraid-driver.xml297(para) +msgid "" +"Edit or add the following lines to the file " +"/etc/cinder/cinder.conf:" +msgstr "" + +#: ./doc/config-reference/block-storage/drivers/coraid-driver.xml300(replaceable) +msgid "ESM_IP_address" +msgstr "" + +#: ./doc/config-reference/block-storage/drivers/coraid-driver.xml301(replaceable) +#: ./doc/config-reference/block-storage/drivers/hds-volume-driver.xml340(option) +msgid "username" +msgstr "" + +#: ./doc/config-reference/block-storage/drivers/coraid-driver.xml302(replaceable) +msgid "Access_Control_Group_name" +msgstr "" + +#: ./doc/config-reference/block-storage/drivers/coraid-driver.xml303(replaceable) +#: ./doc/config-reference/block-storage/drivers/hds-volume-driver.xml350(option) +msgid "password" +msgstr "" + +#: ./doc/config-reference/block-storage/drivers/coraid-driver.xml304(replaceable) +#: ./doc/config-reference/block-storage/drivers/coraid-driver.xml352(replaceable) +#: ./doc/config-reference/block-storage/drivers/coraid-driver.xml370(replaceable) +msgid "coraid_repository_key" +msgstr "" + +#: ./doc/config-reference/block-storage/drivers/coraid-driver.xml306(para) +msgid "" +"Access to storage devices and storage repositories can be controlled using " +"Access Control Groups configured in ESM. Configuring " +"cinder.conf to log on to ESM as the SAN administrator " +"(user name admin), will grant full access to the devices " +"and repositories configured in ESM." +msgstr "" + +#: ./doc/config-reference/block-storage/drivers/coraid-driver.xml312(para) +msgid "" +"Optionally, you can configure an ESM Access Control Group and user. Then, " +"use the cinder.conf file to configure access to the ESM" +" through that group, and user limits access from the OpenStack instance to " +"devices and storage repositories that are defined in the group." +msgstr "" + +#: ./doc/config-reference/block-storage/drivers/coraid-driver.xml317(para) +msgid "" +"To manage access to the SAN by using Access Control Groups, you must enable " +"the Use Access Control setting in the ESM System " +"Setup > Security screen." +msgstr "" + +#: ./doc/config-reference/block-storage/drivers/coraid-driver.xml321(para) +msgid "For more information, see the ESM Online Help." +msgstr "" + +#: ./doc/config-reference/block-storage/drivers/coraid-driver.xml324(title) +msgid "Create and associate a volume type" +msgstr "" + +#: ./doc/config-reference/block-storage/drivers/coraid-driver.xml325(para) +msgid "Create and associate a volume with the ESM storage repository." +msgstr "" + +#: ./doc/config-reference/block-storage/drivers/coraid-driver.xml329(para) +msgid "Restart Cinder." +msgstr "" + +#: ./doc/config-reference/block-storage/drivers/coraid-driver.xml335(para) +msgid "Create a volume." +msgstr "" + +#: ./doc/config-reference/block-storage/drivers/coraid-driver.xml336(replaceable) +msgid "volume_type_name" +msgstr "" + +#: ./doc/config-reference/block-storage/drivers/coraid-driver.xml337(para) +msgid "" +"where volume_type_name is the name you assign the" +" volume. You will see output similar to the following:" +msgstr "" + +#: ./doc/config-reference/block-storage/drivers/coraid-driver.xml345(para) +msgid "Record the value in the ID field; you use this value in the next step." +msgstr "" + +#: ./doc/config-reference/block-storage/drivers/coraid-driver.xml349(para) +msgid "Associate the volume type with the Storage Repository." +msgstr "" + +#: ./doc/config-reference/block-storage/drivers/coraid-driver.xml352(replaceable) +#: ./doc/config-reference/block-storage/drivers/coraid-driver.xml363(replaceable) +msgid "UUID" +msgstr "" + +#: ./doc/config-reference/block-storage/drivers/coraid-driver.xml352(replaceable) +#: ./doc/config-reference/block-storage/drivers/coraid-driver.xml378(replaceable) +msgid "FQRN" +msgstr "" + +#: ./doc/config-reference/block-storage/drivers/coraid-driver.xml357(th) +msgid "Variable" +msgstr "" + +#: ./doc/config-reference/block-storage/drivers/coraid-driver.xml358(th) +#: ./doc/config-reference/block-storage/drivers/huawei-storage-driver.xml311(td) +#: ./doc/config-reference/block-storage/drivers/ibm-storwize-svc-driver.xml202(td) +#: ./doc/config-reference/block-storage/drivers/hds-volume-driver.xml319(td) +#: ./doc/config-reference/block-storage/drivers/ibm-gpfs-volume-driver.xml80(th) +msgid "Description" +msgstr "" + +#: ./doc/config-reference/block-storage/drivers/coraid-driver.xml364(td) +msgid "" +"The ID returned from the command. You can use the " +" command to recover the ID." +msgstr "" + +#: ./doc/config-reference/block-storage/drivers/coraid-driver.xml373(filename) +msgid "cinder.conf" +msgstr "" + +#: ./doc/config-reference/block-storage/drivers/coraid-driver.xml375(literal) +msgid "coraid_repository" +msgstr "" + +#: ./doc/config-reference/block-storage/drivers/coraid-driver.xml371(td) +msgid "" +"The key name used to associate the Cinder volume type with the ESM in the " +" file. If no key name was defined, this is default value for" +" ." +msgstr "" + +#: ./doc/config-reference/block-storage/drivers/coraid-driver.xml379(td) +msgid "The FQRN recorded during the Create Storage Repository process." +msgstr "" + +#: ./doc/config-reference/block-storage/drivers/solidfire-volume-driver.xml5(title) +msgid "SolidFire" +msgstr "" + +#: ./doc/config-reference/block-storage/drivers/solidfire-volume-driver.xml6(para) +msgid "" +"The SolidFire Cluster is a high performance all SSD iSCSI storage device " +"that provides massive scale out capability and extreme fault tolerance. A " +"key feature of the SolidFire cluster is the ability to set and modify during" +" operation specific QoS levels on a volume for volume basis. The SolidFire " +"cluster offers this along with de-duplication, compression, and an " +"architecture that takes full advantage of SSDs." +msgstr "" + +#: ./doc/config-reference/block-storage/drivers/solidfire-volume-driver.xml14(para) +msgid "" +"To configure the use of a SolidFire cluster with Block Storage, modify your " +"cinder.conf file as follows:" +msgstr "" + +#: ./doc/config-reference/block-storage/drivers/solidfire-volume-driver.xml23(para) +msgid "" +"The SolidFire driver creates a unique account prefixed with $cinder-volume-service-hostname-$tenant-id on the SolidFire " +"cluster for each tenant that accesses the cluster through the Volume API. " +"Unfortunately, this account formation results in issues for High " +"Availability (HA) installations and installations where the cinder-volume service can move to a new node." +" HA installations can return an Account Not Found " +"error because the call to the SolidFire cluster is not always going to be " +"sent from the same node. In installations where the cinder-volume service moves to a new node, " +"the same issue can occur when you perform operations on existing volumes, " +"such as clone, extend, delete, and so on." +msgstr "" + +#: ./doc/config-reference/block-storage/drivers/solidfire-volume-driver.xml41(para) +msgid "" +"Set the sf_account_prefix option to an empty string ('') " +"in the cinder.conf file. This setting results in unique" +" accounts being created on the SolidFire cluster, but the accounts are " +"prefixed with the tenant-id or any unique identifier that you choose and are" +" independent of the host where the cinder-" +"volume service resides." +msgstr "" + +#: ./doc/config-reference/block-storage/drivers/xen-sm-driver.xml4(title) +msgid "XenAPI Storage Manager volume driver" +msgstr "" + +#: ./doc/config-reference/block-storage/drivers/xen-sm-driver.xml5(para) +msgid "" +"The Xen Storage Manager volume driver (xensm) is a XenAPI hypervisor " +"specific volume driver, and can be used to provide basic storage " +"functionality, including volume creation and destruction, on a number of " +"different storage back-ends. It also enables the capability of using more " +"sophisticated storage back-ends for operations like cloning/snapshots, and " +"so on. Some of the storage plug-ins that are already supported in Citrix " +"XenServer and Xen Cloud Platform (XCP) are:" +msgstr "" + +#: ./doc/config-reference/block-storage/drivers/xen-sm-driver.xml15(para) +msgid "" +"NFS VHD: Storage repository (SR) plug-in that stores disks as Virtual Hard " +"Disk (VHD) files on a remote Network File System (NFS)." +msgstr "" + +#: ./doc/config-reference/block-storage/drivers/xen-sm-driver.xml20(para) +msgid "" +"Local VHD on LVM: SR plug-in that represents disks as VHD disks on Logical " +"Volumes (LVM) within a locally-attached Volume Group." +msgstr "" + +#: ./doc/config-reference/block-storage/drivers/xen-sm-driver.xml25(para) +msgid "" +"HBA LUN-per-VDI driver: SR plug-in that represents Logical Units (LUs) as " +"Virtual Disk Images (VDIs) sourced by host bus adapters (HBAs). For example," +" hardware-based iSCSI or FC support." +msgstr "" + +#: ./doc/config-reference/block-storage/drivers/xen-sm-driver.xml31(para) +msgid "" +"NetApp: SR driver for mapping of LUNs to VDIs on a NETAPP server, providing " +"use of fast snapshot and clone features on the filer." +msgstr "" + +#: ./doc/config-reference/block-storage/drivers/xen-sm-driver.xml36(para) +msgid "" +"LVHD over FC: SR plug-in that represents disks as VHDs on Logical Volumes " +"within a Volume Group created on an HBA LUN. For example, hardware-based " +"iSCSI or FC support." +msgstr "" + +#: ./doc/config-reference/block-storage/drivers/xen-sm-driver.xml42(para) +msgid "" +"iSCSI: Base ISCSI SR driver, provides a LUN-per-VDI. Does not support " +"creation of VDIs but accesses existing LUNs on a target." +msgstr "" + +#: ./doc/config-reference/block-storage/drivers/xen-sm-driver.xml47(para) +msgid "" +"LVHD over iSCSI: SR plug-in that represents disks as Logical Volumes within " +"a Volume Group created on an iSCSI LUN." +msgstr "" + +#: ./doc/config-reference/block-storage/drivers/xen-sm-driver.xml52(para) +msgid "" +"EqualLogic: SR driver for mapping of LUNs to VDIs on a EQUALLOGIC array " +"group, providing use of fast snapshot and clone features on the array." +msgstr "" + +#: ./doc/config-reference/block-storage/drivers/xen-sm-driver.xml58(title) +msgid "Design and operation" +msgstr "" + +#: ./doc/config-reference/block-storage/drivers/xen-sm-driver.xml60(title) +msgid "Definitions" +msgstr "" + +#: ./doc/config-reference/block-storage/drivers/xen-sm-driver.xml63(para) +msgid "" +"Back-end: A term for a particular storage" +" back-end. This could be iSCSI, NFS, NetApp, and so on." +msgstr "" + +#: ./doc/config-reference/block-storage/drivers/xen-sm-driver.xml68(para) +msgid "" +"Back-end-config: All the parameters " +"required to connect to a specific back-end. For example, for NFS, this would" +" be the server, path, and so on." +msgstr "" + +#: ./doc/config-reference/block-storage/drivers/xen-sm-driver.xml75(para) +msgid "" +"Flavor: This term is equivalent to volume" +" \"types\". A user friendly term to specify some notion of quality of " +"service. For example, \"gold\" might mean that the volumes use a back-end " +"where backups are possible. A flavor can be associated with multiple back-" +"ends. The volume scheduler, with the help of the driver, decides which back-" +"end is used to create a volume of a particular flavor. Currently, the driver" +" uses a simple \"first-fit\" policy, where the first back-end that can " +"successfully create this volume is the one that is used." +msgstr "" + +#: ./doc/config-reference/block-storage/drivers/xen-sm-driver.xml93(title) +msgid "Operation" +msgstr "" + +#: ./doc/config-reference/block-storage/drivers/xen-sm-driver.xml94(para) +msgid "" +"The admin uses the nova-manage command detailed below to add flavors and " +"back-ends." +msgstr "" + +#: ./doc/config-reference/block-storage/drivers/xen-sm-driver.xml96(para) +msgid "" +"One or more cinder-volume service" +" instances are deployed for each availability zone. When an instance is " +"started, it creates storage repositories (SRs) to connect to the back-ends " +"available within that zone. All cinder-" +"volume instances within a zone can see all the available back-" +"ends. These instances are completely symmetric and hence should be able to " +"service any create_volume request within the zone." +msgstr "" + +#: ./doc/config-reference/block-storage/drivers/xen-sm-driver.xml108(title) +msgid "On XenServer, PV guests required" +msgstr "" + +#: ./doc/config-reference/block-storage/drivers/xen-sm-driver.xml109(para) +msgid "" +"Note that when using XenServer you can only attach a volume to a PV guest." +msgstr "" + +#: ./doc/config-reference/block-storage/drivers/xen-sm-driver.xml115(title) +msgid "Configure XenAPI Storage Manager" +msgstr "" + +#: ./doc/config-reference/block-storage/drivers/xen-sm-driver.xml120(para) +msgid "" +"xensm requires that you use either Citrix XenServer or XCP as the " +"hypervisor. The NetApp and EqualLogic back-ends are not supported on XCP." +msgstr "" + +#: ./doc/config-reference/block-storage/drivers/xen-sm-driver.xml126(para) +msgid "" +"Ensure all hosts running volume and " +"compute services have connectivity to the storage system." +msgstr "" + +#: ./doc/config-reference/block-storage/drivers/xen-sm-driver.xml141(systemitem) +#: ./doc/config-reference/block-storage/drivers/xen-sm-driver.xml181(systemitem) +msgid "nova-compute" +msgstr "" + +#: ./doc/config-reference/block-storage/drivers/xen-sm-driver.xml138(emphasis) +msgid "" +"Set the following configuration options for the nova volume service: " +"( also requires the volume_driver configuration option.)" +msgstr "" + +#: ./doc/config-reference/block-storage/drivers/xen-sm-driver.xml152(emphasis) +msgid "" +"You must create the back-end configurations that the volume driver uses " +"before you start the volume service." +msgstr "" + +#: ./doc/config-reference/block-storage/drivers/xen-sm-driver.xml161(para) +msgid "" +"SR type and configuration connection parameters are in keeping with the " +"XenAPI Command " +"Line Interface." +msgstr "" + +#: ./doc/config-reference/block-storage/drivers/xen-sm-driver.xml168(para) +msgid "Example: For the NFS storage manager plug-in, run these commands:" +msgstr "" + +#: ./doc/config-reference/block-storage/drivers/xen-sm-driver.xml179(systemitem) +msgid "cinder-volume" +msgstr "" + +#: ./doc/config-reference/block-storage/drivers/xen-sm-driver.xml177(emphasis) +msgid "" +"Start and with the new configuration " +"options." +msgstr "" + +#: ./doc/config-reference/block-storage/drivers/xen-sm-driver.xml188(title) +msgid "Create and access the volumes from VMs" +msgstr "" + +#: ./doc/config-reference/block-storage/drivers/xen-sm-driver.xml189(para) +msgid "" +"Currently, the flavors have not been tied to the volume types API. As a " +"result, we simply end up creating volumes in a \"first fit\" order on the " +"given back-ends." +msgstr "" + +#: ./doc/config-reference/block-storage/drivers/xen-sm-driver.xml193(para) +msgid "" +"Use the standard or OpenStack API commands (such as volume " +"extensions) to create, destroy, attach, or detach volumes." +msgstr "" + +#: ./doc/config-reference/block-storage/drivers/ibm-xiv-volume-driver.xml5(title) +msgid "IBM XIV/DS8K volume driver" +msgstr "" + +#: ./doc/config-reference/block-storage/drivers/ibm-xiv-volume-driver.xml6(para) +msgid "" +"There is a unified volume back-end for IBM XIV and DS8K storage. Set the " +"following in your cinder.conf, and use the following " +"options to configure it." +msgstr "" + +#: ./doc/config-reference/block-storage/drivers/netapp-volume-driver.xml5(title) +msgid "NetApp unified driver" +msgstr "" + +#: ./doc/config-reference/block-storage/drivers/netapp-volume-driver.xml6(para) +msgid "" +"The NetApp® unified driver is a block storage driver that supports multiple " +"storage families and protocols. A storage family corresponds to storage " +"systems built on different NetApp technologies such as clustered Data ONTAP®" +" and Data ONTAP operating in 7-Mode. The storage protocol refers to the " +"protocol used to initiate data storage and access operations on those " +"storage systems like iSCSI and NFS. The NetApp unified driver can be " +"configured to provision and manage OpenStack volumes on a given storage " +"family using a specified storage protocol. The OpenStack volumes can then be" +" used for accessing and storing data using the storage protocol on the " +"storage family system. The NetApp unified driver is an extensible interface " +"that can support new storage families and protocols." +msgstr "" + +#: ./doc/config-reference/block-storage/drivers/netapp-volume-driver.xml21(title) +msgid "NetApp clustered Data ONTAP storage family" +msgstr "" + +#: ./doc/config-reference/block-storage/drivers/netapp-volume-driver.xml22(para) +msgid "" +"The NetApp clustered Data ONTAP storage family represents a configuration " +"group which provides OpenStack compute instances access to clustered Data " +"ONTAP storage systems. At present it can be configured in Cinder to work " +"with iSCSI and NFS storage protocols." +msgstr "" + +#: ./doc/config-reference/block-storage/drivers/netapp-volume-driver.xml28(title) +msgid "NetApp iSCSI configuration for clustered Data ONTAP" +msgstr "" + +#: ./doc/config-reference/block-storage/drivers/netapp-volume-driver.xml30(para) +msgid "" +"The NetApp iSCSI configuration for clustered Data ONTAP is an interface from" +" OpenStack to clustered Data ONTAP storage systems for provisioning and " +"managing the SAN block storage entity; that is, a NetApp LUN which can be " +"accessed using the iSCSI protocol." +msgstr "" + +#: ./doc/config-reference/block-storage/drivers/netapp-volume-driver.xml35(para) +msgid "" +"The iSCSI configuration for clustered Data ONTAP is a direct interface from " +"Cinder to the clustered Data ONTAP instance and as such does not require " +"additional management software to achieve the desired functionality. It uses" +" NetApp APIs to interact with the clustered Data ONTAP instance." +msgstr "" + +#: ./doc/config-reference/block-storage/drivers/netapp-volume-driver.xml42(title) +msgid "" +"Configuration options for clustered Data ONTAP family with iSCSI protocol" +msgstr "" + +#: ./doc/config-reference/block-storage/drivers/netapp-volume-driver.xml44(para) +msgid "" +"Configure the volume driver, storage family and storage protocol to the " +"NetApp unified driver, clustered Data ONTAP, and iSCSI respectively by " +"setting the volume_driver, " +"netapp_storage_family and " +"netapp_storage_protocol options in " +"cinder.conf as follows:" +msgstr "" + +#: ./doc/config-reference/block-storage/drivers/netapp-volume-driver.xml63(para) +#: ./doc/config-reference/block-storage/drivers/netapp-volume-driver.xml230(para) +msgid "" +"You must override the default value of " +"netapp_storage_protocol with iscsi in " +"order to utilize the iSCSI protocol." +msgstr "" + +#: ./doc/config-reference/block-storage/drivers/netapp-volume-driver.xml71(para) +#: ./doc/config-reference/block-storage/drivers/netapp-volume-driver.xml129(para) +msgid "" +"If you specify an account in the netapp_login that only " +"has virtual storage server (Vserver) administration privileges (rather than " +"cluster-wide administration privileges), some advanced features of the " +"NetApp unified driver will not work and you may see warnings in the Cinder " +"logs." +msgstr "" + +#: ./doc/config-reference/block-storage/drivers/netapp-volume-driver.xml81(para) +msgid "" +"For more information on these options and other deployment and operational " +"scenarios, visit the OpenStack NetApp " +"community." +msgstr "" + +#: ./doc/config-reference/block-storage/drivers/netapp-volume-driver.xml91(title) +msgid "NetApp NFS configuration for clustered Data ONTAP" +msgstr "" + +#: ./doc/config-reference/block-storage/drivers/netapp-volume-driver.xml93(para) +msgid "" +"The NetApp NFS configuration for clustered Data ONTAP is an interface from " +"OpenStack to a clustered Data ONTAP system for provisioning and managing " +"OpenStack volumes on NFS exports provided by the clustered Data ONTAP system" +" that are accessed using the NFS protocol." +msgstr "" + +#: ./doc/config-reference/block-storage/drivers/netapp-volume-driver.xml99(para) +msgid "" +"The NFS configuration for clustered Data ONTAP is a direct interface from " +"Cinder to the clustered Data ONTAP instance and as such does not require any" +" additional management software to achieve the desired functionality. It " +"uses NetApp APIs to interact with the clustered Data ONTAP instance." +msgstr "" + +#: ./doc/config-reference/block-storage/drivers/netapp-volume-driver.xml106(title) +msgid "" +"Configuration options for the clustered Data ONTAP family with NFS protocol" +msgstr "" + +#: ./doc/config-reference/block-storage/drivers/netapp-volume-driver.xml108(para) +msgid "" +"Configure the volume driver, storage family and storage protocol to NetApp " +"unified driver, clustered Data ONTAP, and NFS respectively by setting the " +"volume_driver, netapp_storage_family " +"and netapp_storage_protocol options in " +"cinder.conf as follows:" +msgstr "" + +#: ./doc/config-reference/block-storage/drivers/netapp-volume-driver.xml139(para) +#: ./doc/config-reference/block-storage/drivers/netapp-volume-driver.xml238(para) +#: ./doc/config-reference/block-storage/drivers/netapp-volume-driver.xml288(para) +msgid "" +"For more information on these options and other deployment and operational " +"scenarios, visit the OpenStack NetApp " +"community." +msgstr "" + +#: ./doc/config-reference/block-storage/drivers/netapp-volume-driver.xml148(title) +msgid "NetApp-supported extra specs for clustered Data ONTAP" +msgstr "" + +#: ./doc/config-reference/block-storage/drivers/netapp-volume-driver.xml150(para) +msgid "" +"Extra specs enable vendors to specify extra filter criteria that the Block " +"Storage scheduler uses when it determines which volume node should fulfill a" +" volume provisioning request. When you use the NetApp unified driver with a " +"clustered Data ONTAP storage system, you can leverage extra specs with " +"Cinder volume types to ensure that Cinder volumes are created on storage " +"back ends that have certain properties. For example, when you configure QoS," +" mirroring, or compression for a storage back end." +msgstr "" + +#: ./doc/config-reference/block-storage/drivers/netapp-volume-driver.xml160(para) +msgid "" +"Extra specs are associated with Cinder volume types, so that when users " +"request volumes of a particular volume type, the volumes are created on " +"storage back ends that meet the list of requirements. For example, the back " +"ends have the available space or extra specs. You can use the specs in the " +"following table when you define Cinder volume types by using the " +" command." +msgstr "" + +#: ./doc/config-reference/block-storage/drivers/netapp-volume-driver.xml171(para) +msgid "" +"It is recommended to only set the value of extra specs to " +"True when combining multiple specs to enforce a certain " +"logic set. If you desire to remove volumes with a certain feature enabled " +"from consideration from the Cinder volume scheduler, be sure to use the " +"negated spec name with a value of True rather than " +"setting the positive spec to a value of False." +msgstr "" + +#: ./doc/config-reference/block-storage/drivers/netapp-volume-driver.xml184(title) +msgid "NetApp Data ONTAP operating in 7-Mode storage family" +msgstr "" + +#: ./doc/config-reference/block-storage/drivers/netapp-volume-driver.xml186(para) +msgid "" +"The NetApp Data ONTAP operating in 7-Mode storage family represents a " +"configuration group which provides OpenStack compute instances access to " +"7-Mode storage systems. At present it can be configured in Cinder to work " +"with iSCSI and NFS storage protocols." +msgstr "" + +#: ./doc/config-reference/block-storage/drivers/netapp-volume-driver.xml192(title) +msgid "NetApp iSCSI configuration for Data ONTAP operating in 7-Mode" +msgstr "" + +#: ./doc/config-reference/block-storage/drivers/netapp-volume-driver.xml194(para) +msgid "" +"The NetApp iSCSI configuration for Data ONTAP operating in 7-Mode is an " +"interface from OpenStack to Data ONTAP operating in 7-Mode storage systems " +"for provisioning and managing the SAN block storage entity, that is, a LUN " +"which can be accessed using iSCSI protocol." +msgstr "" + +#: ./doc/config-reference/block-storage/drivers/netapp-volume-driver.xml200(para) +msgid "" +"The iSCSI configuration for Data ONTAP operating in 7-Mode is a direct " +"interface from OpenStack to Data ONTAP operating in 7-Mode storage system " +"and it does not require additional management software to achieve the " +"desired functionality. It uses NetApp ONTAPI to interact with the Data ONTAP" +" operating in 7-Mode storage system." +msgstr "" + +#: ./doc/config-reference/block-storage/drivers/netapp-volume-driver.xml208(title) +msgid "" +"Configuration options for the Data ONTAP operating in 7-Mode storage family " +"with iSCSI protocol" +msgstr "" + +#: ./doc/config-reference/block-storage/drivers/netapp-volume-driver.xml211(para) +msgid "" +"Configure the volume driver, storage family and storage protocol to the " +"NetApp unified driver, Data ONTAP operating in 7-Mode, and iSCSI " +"respectively by setting the volume_driver, " +"netapp_storage_family and " +"netapp_storage_protocol options in " +"cinder.conf as follows:" +msgstr "" + +#: ./doc/config-reference/block-storage/drivers/netapp-volume-driver.xml247(title) +msgid "NetApp NFS configuration for Data ONTAP operating in 7-Mode" +msgstr "" + +#: ./doc/config-reference/block-storage/drivers/netapp-volume-driver.xml249(para) +msgid "" +"The NetApp NFS configuration for Data ONTAP operating in 7-Mode is an " +"interface from OpenStack to Data ONTAP operating in 7-Mode storage system " +"for provisioning and managing OpenStack volumes on NFS exports provided by " +"the Data ONTAP operating in 7-Mode storage system which can then be accessed" +" using NFS protocol." +msgstr "" + +#: ./doc/config-reference/block-storage/drivers/netapp-volume-driver.xml256(para) +msgid "" +"The NFS configuration for Data ONTAP operating in 7-Mode is a direct " +"interface from Cinder to the Data ONTAP operating in 7-Mode instance and as " +"such does not require any additional management software to achieve the " +"desired functionality. It uses NetApp ONTAPI to interact with the Data ONTAP" +" operating in 7-Mode storage system." +msgstr "" + +#: ./doc/config-reference/block-storage/drivers/netapp-volume-driver.xml264(title) +msgid "" +"Configuration options for the Data ONTAP operating in 7-Mode family with NFS" +" protocol" +msgstr "" + +#: ./doc/config-reference/block-storage/drivers/netapp-volume-driver.xml267(para) +msgid "" +"Configure the volume driver, storage family and storage protocol to the " +"NetApp unified driver, Data ONTAP operating in 7-Mode, and NFS respectively " +"by setting the volume_driver, " +"netapp_storage_family and " +"netapp_storage_protocol options in " +"cinder.conf as follows:" +msgstr "" + +#: ./doc/config-reference/block-storage/drivers/netapp-volume-driver.xml298(title) +msgid "Upgrading prior NetApp drivers to the NetApp unified driver" +msgstr "" + +#: ./doc/config-reference/block-storage/drivers/netapp-volume-driver.xml300(para) +msgid "" +"NetApp introduced a new unified block storage driver in Havana for " +"configuring different storage families and storage protocols. This requires " +"defining upgrade path for NetApp drivers which existed in releases prior to " +"Havana. This section covers the upgrade configuration for NetApp drivers to " +"the new unified configuration and a list of deprecated NetApp drivers." +msgstr "" + +#: ./doc/config-reference/block-storage/drivers/netapp-volume-driver.xml308(title) +msgid "Upgraded NetApp drivers" +msgstr "" + +#: ./doc/config-reference/block-storage/drivers/netapp-volume-driver.xml309(para) +msgid "" +"This section describes how to update Cinder configuration from a pre-Havana " +"release to the new unified driver format." +msgstr "" + +#: ./doc/config-reference/block-storage/drivers/netapp-volume-driver.xml313(title) +msgid "Driver upgrade configuration" +msgstr "" + +#: ./doc/config-reference/block-storage/drivers/netapp-volume-driver.xml316(para) +msgid "" +"NetApp iSCSI direct driver for Clustered Data ONTAP in Grizzly (or earlier)" +msgstr "" + +#: ./doc/config-reference/block-storage/drivers/netapp-volume-driver.xml321(para) +#: ./doc/config-reference/block-storage/drivers/netapp-volume-driver.xml335(para) +#: ./doc/config-reference/block-storage/drivers/netapp-volume-driver.xml350(para) +#: ./doc/config-reference/block-storage/drivers/netapp-volume-driver.xml365(para) +msgid "NetApp Unified Driver configuration" +msgstr "" + +#: ./doc/config-reference/block-storage/drivers/netapp-volume-driver.xml330(para) +msgid "" +"NetApp NFS direct driver for Clustered Data ONTAP in Grizzly (or earlier)" +msgstr "" + +#: ./doc/config-reference/block-storage/drivers/netapp-volume-driver.xml344(para) +msgid "" +"NetApp iSCSI direct driver for Data ONTAP operating in 7-Mode storage " +"controller in Grizzly (or earlier)" +msgstr "" + +#: ./doc/config-reference/block-storage/drivers/netapp-volume-driver.xml359(para) +msgid "" +"NetApp NFS direct driver for Data ONTAP operating in 7-Mode storage " +"controller in Grizzly (or earlier)" +msgstr "" + +#: ./doc/config-reference/block-storage/drivers/netapp-volume-driver.xml378(title) +msgid "Deprecated NetApp drivers" +msgstr "" + +#: ./doc/config-reference/block-storage/drivers/netapp-volume-driver.xml379(para) +msgid "" +"This section lists the NetApp drivers in previous releases that are " +"deprecated in Havana." +msgstr "" + +#: ./doc/config-reference/block-storage/drivers/netapp-volume-driver.xml383(para) +msgid "NetApp iSCSI driver for clustered Data ONTAP." +msgstr "" + +#: ./doc/config-reference/block-storage/drivers/netapp-volume-driver.xml390(para) +msgid "NetApp NFS driver for clustered Data ONTAP." +msgstr "" + +#: ./doc/config-reference/block-storage/drivers/netapp-volume-driver.xml397(para) +msgid "" +"NetApp iSCSI driver for Data ONTAP operating in 7-Mode storage controller." +msgstr "" + +#: ./doc/config-reference/block-storage/drivers/netapp-volume-driver.xml404(para) +msgid "" +"NetApp NFS driver for Data ONTAP operating in 7-Mode storage controller." +msgstr "" + +#: ./doc/config-reference/block-storage/drivers/netapp-volume-driver.xml412(para) +msgid "" +"See the OpenStack NetApp " +"community for support information on deprecated NetApp drivers in the" +" Havana release." +msgstr "" + +#: ./doc/config-reference/block-storage/drivers/huawei-storage-driver.xml6(title) +msgid "Huawei storage driver" +msgstr "" + +#: ./doc/config-reference/block-storage/drivers/huawei-storage-driver.xml7(para) +msgid "" +"Huawei driver supports the iSCSI and Fibre Channel connections and enables " +"OceanStor T series unified storage, OceanStor Dorado high-performance " +"storage, and OceanStor HVS high-end storage to provide block storage " +"services for OpenStack." +msgstr "" + +#: ./doc/config-reference/block-storage/drivers/huawei-storage-driver.xml20(para) +#: ./doc/config-reference/block-storage/drivers/huawei-storage-driver.xml51(para) +#: ./doc/config-reference/block-storage/drivers/huawei-storage-driver.xml77(para) +#: ./doc/config-reference/block-storage/drivers/huawei-storage-driver.xml96(para) +#: ./doc/config-reference/block-storage/drivers/emc-volume-driver.xml39(para) +#: ./doc/config-reference/block-storage/drivers/hds-volume-driver.xml33(para) +msgid "Delete volume" +msgstr "" + +#: ./doc/config-reference/block-storage/drivers/huawei-storage-driver.xml23(para) +#: ./doc/config-reference/block-storage/drivers/huawei-storage-driver.xml54(para) +#: ./doc/config-reference/block-storage/drivers/huawei-storage-driver.xml80(para) +#: ./doc/config-reference/block-storage/drivers/huawei-storage-driver.xml99(para) +#: ./doc/config-reference/block-storage/drivers/emc-volume-driver.xml42(para) +#: ./doc/config-reference/block-storage/drivers/hds-volume-driver.xml36(para) +msgid "Attach volume" +msgstr "" + +#: ./doc/config-reference/block-storage/drivers/huawei-storage-driver.xml29(para) +#: ./doc/config-reference/block-storage/drivers/huawei-storage-driver.xml60(para) +#: ./doc/config-reference/block-storage/drivers/huawei-storage-driver.xml105(para) +#: ./doc/config-reference/block-storage/drivers/emc-volume-driver.xml48(para) +#: ./doc/config-reference/block-storage/drivers/hds-volume-driver.xml48(para) +msgid "Create snapshot" +msgstr "" + +#: ./doc/config-reference/block-storage/drivers/huawei-storage-driver.xml32(para) +#: ./doc/config-reference/block-storage/drivers/huawei-storage-driver.xml63(para) +#: ./doc/config-reference/block-storage/drivers/huawei-storage-driver.xml108(para) +#: ./doc/config-reference/block-storage/drivers/emc-volume-driver.xml51(para) +#: ./doc/config-reference/block-storage/drivers/hds-volume-driver.xml51(para) +msgid "Delete snapshot" +msgstr "" + +#: ./doc/config-reference/block-storage/drivers/huawei-storage-driver.xml38(para) +#: ./doc/config-reference/block-storage/drivers/huawei-storage-driver.xml114(para) +msgid "Create clone volume" +msgstr "" + +#: ./doc/config-reference/block-storage/drivers/huawei-storage-driver.xml41(para) +#: ./doc/config-reference/block-storage/drivers/huawei-storage-driver.xml66(para) +#: ./doc/config-reference/block-storage/drivers/huawei-storage-driver.xml86(para) +#: ./doc/config-reference/block-storage/drivers/huawei-storage-driver.xml117(para) +#: ./doc/config-reference/block-storage/drivers/emc-volume-driver.xml57(para) +#: ./doc/config-reference/block-storage/drivers/hds-volume-driver.xml54(para) +msgid "Copy image to volume" +msgstr "" + +#: ./doc/config-reference/block-storage/drivers/huawei-storage-driver.xml44(para) +#: ./doc/config-reference/block-storage/drivers/huawei-storage-driver.xml69(para) +#: ./doc/config-reference/block-storage/drivers/huawei-storage-driver.xml89(para) +#: ./doc/config-reference/block-storage/drivers/huawei-storage-driver.xml120(para) +#: ./doc/config-reference/block-storage/drivers/emc-volume-driver.xml60(para) +#: ./doc/config-reference/block-storage/drivers/hds-volume-driver.xml57(para) +msgid "Copy volume to image" +msgstr "" + +#: ./doc/config-reference/block-storage/drivers/huawei-storage-driver.xml14(para) +msgid "" +"OceanStor T series unified storage supports the following " +"operations:OceanStor Dorado5100 supports the following " +"operations:OceanStor Dorado2100 G2 supports the following " +"operations:OceanStor HVS supports the following " +"operations:" +msgstr "" + +#: ./doc/config-reference/block-storage/drivers/huawei-storage-driver.xml125(title) +msgid "Configure Cinder nodes" +msgstr "" + +#: ./doc/config-reference/block-storage/drivers/huawei-storage-driver.xml126(para) +msgid "" +"In /etc/cinder, create the driver configuration file " +"named cinder_huawei_conf.xml." +msgstr "" + +#: ./doc/config-reference/block-storage/drivers/huawei-storage-driver.xml129(para) +msgid "" +"You must configure and to" +" specify a storage system and link type. The following uses the iSCSI driver" +" as an example. The driver configuration file of OceanStor T series unified " +"storage is shown as follows:" +msgstr "" + +#: ./doc/config-reference/block-storage/drivers/huawei-storage-driver.xml160(para) +msgid "" +"The driver configuration file of OceanStor Dorado5100 is shown as follows:" +msgstr "" + +#: ./doc/config-reference/block-storage/drivers/huawei-storage-driver.xml186(para) +msgid "" +"The driver configuration file of OceanStor Dorado2100 G2 is shown as " +"follows:" +msgstr "" + +#: ./doc/config-reference/block-storage/drivers/huawei-storage-driver.xml210(para) +msgid "The driver configuration file of OceanStor HVS is shown as follows:" +msgstr "" + +#: ./doc/config-reference/block-storage/drivers/huawei-storage-driver.xml236(para) +msgid "" +"You do not need to configure the iSCSI target IP address for the Fibre " +"Channel driver. In the prior example, delete the iSCSI configuration:" +msgstr "" + +#: ./doc/config-reference/block-storage/drivers/huawei-storage-driver.xml246(para) +msgid "" +"To add and " +" items, you can modify the " +"cinder.conf configuration file as follows:" +msgstr "" + +#: ./doc/config-reference/block-storage/drivers/huawei-storage-driver.xml252(para) +msgid "You can configure multiple Huawei back-end storages as follows:" +msgstr "" + +#: ./doc/config-reference/block-storage/drivers/huawei-storage-driver.xml263(para) +msgid "" +"OceanStor HVS storage system supports the QoS function. You must create a " +"QoS policy for the HVS storage system and create the volume type to enable " +"QoS as follows:" +msgstr "" + +#: ./doc/config-reference/block-storage/drivers/huawei-storage-driver.xml272(para) +msgid "" +" is a QoS policy created by a user for " +"the HVS storage system. is the self-defined volume" +" type. Set the option to " +"high, normal, or " +"low." +msgstr "" + +#: ./doc/config-reference/block-storage/drivers/huawei-storage-driver.xml280(para) +msgid "" +"OceanStor HVS storage system supports the SmartTier function. SmartTier has " +"three tiers. You can create the volume type to enable SmartTier as follows:" +msgstr "" + +#: ./doc/config-reference/block-storage/drivers/huawei-storage-driver.xml288(para) +msgid "" +" and " +"can only be set to high, normal, or " +"low." +msgstr "" + +#: ./doc/config-reference/block-storage/drivers/huawei-storage-driver.xml295(title) +msgid "Configuration file details" +msgstr "" + +#: ./doc/config-reference/block-storage/drivers/huawei-storage-driver.xml296(para) +msgid "This table describes the Huawei storage driver configuration options:" +msgstr "" + +#: ./doc/config-reference/block-storage/drivers/huawei-storage-driver.xml299(caption) +msgid "Huawei storage driver configuration options" +msgstr "" + +#: ./doc/config-reference/block-storage/drivers/huawei-storage-driver.xml308(td) +#: ./doc/config-reference/block-storage/drivers/ibm-storwize-svc-driver.xml199(td) +msgid "Flag name" +msgstr "" + +#: ./doc/config-reference/block-storage/drivers/huawei-storage-driver.xml309(td) +#: ./doc/config-reference/block-storage/drivers/ibm-storwize-svc-driver.xml200(td) +#: ./doc/config-reference/block-storage/drivers/hds-volume-driver.xml317(td) +msgid "Type" +msgstr "" + +#: ./doc/config-reference/block-storage/drivers/huawei-storage-driver.xml310(td) +#: ./doc/config-reference/block-storage/drivers/ibm-storwize-svc-driver.xml201(td) +#: ./doc/config-reference/block-storage/drivers/hds-volume-driver.xml318(td) +msgid "Default" +msgstr "" + +#: ./doc/config-reference/block-storage/drivers/huawei-storage-driver.xml317(option) +msgid "Product" +msgstr "" + +#: ./doc/config-reference/block-storage/drivers/huawei-storage-driver.xml320(para) +#: ./doc/config-reference/block-storage/drivers/huawei-storage-driver.xml334(td) +#: ./doc/config-reference/block-storage/drivers/huawei-storage-driver.xml345(td) +#: ./doc/config-reference/block-storage/drivers/huawei-storage-driver.xml357(para) +#: ./doc/config-reference/block-storage/drivers/huawei-storage-driver.xml369(td) +#: ./doc/config-reference/block-storage/drivers/huawei-storage-driver.xml381(para) +#: ./doc/config-reference/block-storage/drivers/huawei-storage-driver.xml396(para) +#: ./doc/config-reference/block-storage/drivers/huawei-storage-driver.xml501(td) +#: ./doc/config-reference/block-storage/drivers/ibm-storwize-svc-driver.xml209(para) +#: ./doc/config-reference/block-storage/drivers/ibm-storwize-svc-driver.xml224(para) +#: ./doc/config-reference/block-storage/drivers/ibm-storwize-svc-driver.xml262(para) +#: ./doc/config-reference/block-storage/drivers/hds-volume-driver.xml326(para) +#: ./doc/config-reference/block-storage/drivers/hds-volume-driver.xml334(para) +#: ./doc/config-reference/block-storage/drivers/hds-volume-driver.xml379(para) +#: ./doc/config-reference/block-storage/drivers/hds-volume-driver.xml391(para) +#: ./doc/config-reference/block-storage/drivers/hds-volume-driver.xml408(para) +#: ./doc/config-reference/block-storage/drivers/hds-volume-driver.xml419(para) +msgid "Required" +msgstr "" + +#: ./doc/config-reference/block-storage/drivers/huawei-storage-driver.xml326(para) +msgid "" +"Type of a storage product. Valid values are T, " +"Dorado, or HVS." +msgstr "" + +#: ./doc/config-reference/block-storage/drivers/huawei-storage-driver.xml333(option) +msgid "Protocol" +msgstr "" + +#: ./doc/config-reference/block-storage/drivers/huawei-storage-driver.xml339(literal) +#: ./doc/config-reference/block-storage/drivers/ibm-storwize-svc-driver.xml412(para) +msgid "iSCSI" +msgstr "" + +#: ./doc/config-reference/block-storage/drivers/huawei-storage-driver.xml340(literal) +msgid "FC" +msgstr "" + +#: ./doc/config-reference/block-storage/drivers/huawei-storage-driver.xml338(td) +msgid "" +"Type of a protocol. Valid values are or ." +msgstr "" + +#: ./doc/config-reference/block-storage/drivers/huawei-storage-driver.xml344(option) +msgid "ControllerIP0" +msgstr "" + +#: ./doc/config-reference/block-storage/drivers/huawei-storage-driver.xml349(td) +msgid "IP address of the primary controller (not required for the HVS)" +msgstr "" + +#: ./doc/config-reference/block-storage/drivers/huawei-storage-driver.xml354(option) +msgid "ControllerIP1" +msgstr "" + +#: ./doc/config-reference/block-storage/drivers/huawei-storage-driver.xml363(para) +msgid "IP address of the secondary controller (not required for the HVS)" +msgstr "" + +#: ./doc/config-reference/block-storage/drivers/huawei-storage-driver.xml368(option) +msgid "HVSURL" +msgstr "" + +#: ./doc/config-reference/block-storage/drivers/huawei-storage-driver.xml373(td) +msgid "Access address of the Rest port (required only for the HVS)" +msgstr "" + +#: ./doc/config-reference/block-storage/drivers/huawei-storage-driver.xml378(option) +msgid "UserName" +msgstr "" + +#: ./doc/config-reference/block-storage/drivers/huawei-storage-driver.xml387(para) +msgid "User name of an administrator" +msgstr "" + +#: ./doc/config-reference/block-storage/drivers/huawei-storage-driver.xml392(option) +msgid "UserPassword" +msgstr "" + +#: ./doc/config-reference/block-storage/drivers/huawei-storage-driver.xml402(para) +msgid "Password of an administrator" +msgstr "" + +#: ./doc/config-reference/block-storage/drivers/huawei-storage-driver.xml407(option) +msgid "LUNType" +msgstr "" + +#: ./doc/config-reference/block-storage/drivers/huawei-storage-driver.xml410(para) +#: ./doc/config-reference/block-storage/drivers/huawei-storage-driver.xml427(para) +#: ./doc/config-reference/block-storage/drivers/huawei-storage-driver.xml445(para) +#: ./doc/config-reference/block-storage/drivers/huawei-storage-driver.xml463(para) +#: ./doc/config-reference/block-storage/drivers/huawei-storage-driver.xml476(td) +#: ./doc/config-reference/block-storage/drivers/huawei-storage-driver.xml491(td) +#: ./doc/config-reference/block-storage/drivers/huawei-storage-driver.xml513(td) +#: ./doc/config-reference/block-storage/drivers/huawei-storage-driver.xml524(td) +#: ./doc/config-reference/block-storage/drivers/huawei-storage-driver.xml534(td) +#: ./doc/config-reference/block-storage/drivers/huawei-storage-driver.xml545(td) +#: ./doc/config-reference/block-storage/drivers/huawei-storage-driver.xml553(td) +#: ./doc/config-reference/block-storage/drivers/ibm-storwize-svc-driver.xml217(para) +#: ./doc/config-reference/block-storage/drivers/ibm-storwize-svc-driver.xml271(para) +#: ./doc/config-reference/block-storage/drivers/ibm-storwize-svc-driver.xml295(para) +#: ./doc/config-reference/block-storage/drivers/ibm-storwize-svc-driver.xml306(para) +#: ./doc/config-reference/block-storage/drivers/ibm-storwize-svc-driver.xml330(para) +#: ./doc/config-reference/block-storage/drivers/ibm-storwize-svc-driver.xml341(para) +#: ./doc/config-reference/block-storage/drivers/ibm-storwize-svc-driver.xml362(para) +#: ./doc/config-reference/block-storage/drivers/ibm-storwize-svc-driver.xml380(para) +#: ./doc/config-reference/block-storage/drivers/ibm-storwize-svc-driver.xml390(para) +#: ./doc/config-reference/block-storage/drivers/ibm-storwize-svc-driver.xml411(para) +#: ./doc/config-reference/block-storage/drivers/ibm-storwize-svc-driver.xml422(para) +#: ./doc/config-reference/block-storage/drivers/ibm-storwize-svc-driver.xml432(para) +#: ./doc/config-reference/block-storage/drivers/ibm-storwize-svc-driver.xml448(para) +#: ./doc/config-reference/block-storage/drivers/hds-volume-driver.xml342(para) +#: ./doc/config-reference/block-storage/drivers/hds-volume-driver.xml352(para) +#: ./doc/config-reference/block-storage/drivers/hds-volume-driver.xml364(para) +#: ./doc/config-reference/block-storage/drivers/hds-volume-driver.xml430(para) +#: ./doc/config-reference/block-storage/drivers/hds-volume-driver.xml441(para) +msgid "Optional" +msgstr "" + +#: ./doc/config-reference/block-storage/drivers/huawei-storage-driver.xml413(para) +msgid "Thin" +msgstr "" + +#: ./doc/config-reference/block-storage/drivers/huawei-storage-driver.xml416(para) +msgid "" +"Type of a created LUN. Valid values are Thick or " +"Thin." +msgstr "" + +#: ./doc/config-reference/block-storage/drivers/huawei-storage-driver.xml423(option) +msgid "StripUnitSize" +msgstr "" + +#: ./doc/config-reference/block-storage/drivers/huawei-storage-driver.xml430(para) +msgid "64" +msgstr "" + +#: ./doc/config-reference/block-storage/drivers/huawei-storage-driver.xml433(para) +msgid "Stripe depth of a created LUN. The value is expressed in KB." +msgstr "" + +#: ./doc/config-reference/block-storage/drivers/huawei-storage-driver.xml435(para) +msgid "This flag is not valid for a thin LUN." +msgstr "" + +#: ./doc/config-reference/block-storage/drivers/huawei-storage-driver.xml441(option) +msgid "WriteType" +msgstr "" + +#: ./doc/config-reference/block-storage/drivers/huawei-storage-driver.xml448(para) +#: ./doc/config-reference/block-storage/drivers/huawei-storage-driver.xml466(para) +msgid "1" +msgstr "" + +#: ./doc/config-reference/block-storage/drivers/huawei-storage-driver.xml451(para) +msgid "" +"Cache write method. The method can be write back, write through, or Required" +" write back. The default value is 1, indicating write " +"back." +msgstr "" + +#: ./doc/config-reference/block-storage/drivers/huawei-storage-driver.xml460(option) +msgid "MirrorSwitch" +msgstr "" + +#: ./doc/config-reference/block-storage/drivers/huawei-storage-driver.xml469(para) +msgid "" +"Cache mirroring policy. The default value is 1, " +"indicating that a mirroring policy is used." +msgstr "" + +#: ./doc/config-reference/block-storage/drivers/huawei-storage-driver.xml475(option) +msgid "Prefetch Type" +msgstr "" + +#: ./doc/config-reference/block-storage/drivers/huawei-storage-driver.xml478(para) +msgid "3" +msgstr "" + +#: ./doc/config-reference/block-storage/drivers/huawei-storage-driver.xml481(para) +msgid "" +"Cache prefetch strategy. The strategy can be constant prefetch, variable " +"prefetch, or intelligent prefetch. Default value is 3, " +"which indicates intelligent prefetch and is not required for the HVS." +msgstr "" + +#: ./doc/config-reference/block-storage/drivers/huawei-storage-driver.xml490(option) +msgid "Prefetch Value" +msgstr "" + +#: ./doc/config-reference/block-storage/drivers/huawei-storage-driver.xml493(para) +#: ./doc/config-reference/block-storage/drivers/ibm-storwize-svc-driver.xml381(para) +#: ./doc/config-reference/block-storage/drivers/hds-volume-driver.xml431(para) +msgid "0" +msgstr "" + +#: ./doc/config-reference/block-storage/drivers/huawei-storage-driver.xml496(para) +msgid "Cache prefetch value." +msgstr "" + +#: ./doc/config-reference/block-storage/drivers/huawei-storage-driver.xml500(option) +msgid "StoragePool" +msgstr "" + +#: ./doc/config-reference/block-storage/drivers/huawei-storage-driver.xml506(para) +msgid "" +"Name of a storage pool that you want to use. Not required for the Dorado2100" +" G2." +msgstr "" + +#: ./doc/config-reference/block-storage/drivers/huawei-storage-driver.xml512(option) +msgid "DefaultTargetIP" +msgstr "" + +#: ./doc/config-reference/block-storage/drivers/huawei-storage-driver.xml518(para) +msgid "Default IP address of the iSCSI port provided for compute nodes." +msgstr "" + +#: ./doc/config-reference/block-storage/drivers/huawei-storage-driver.xml523(option) +msgid "Initiator Name" +msgstr "" + +#: ./doc/config-reference/block-storage/drivers/huawei-storage-driver.xml529(para) +msgid "Name of a compute node initiator." +msgstr "" + +#: ./doc/config-reference/block-storage/drivers/huawei-storage-driver.xml533(option) +msgid "Initiator TargetIP" +msgstr "" + +#: ./doc/config-reference/block-storage/drivers/huawei-storage-driver.xml539(para) +msgid "IP address of the iSCSI port provided for Compute nodes." +msgstr "" + +#: ./doc/config-reference/block-storage/drivers/huawei-storage-driver.xml544(option) +msgid "OSType" +msgstr "" + +#: ./doc/config-reference/block-storage/drivers/huawei-storage-driver.xml547(para) +msgid "Linux" +msgstr "" + +#: ./doc/config-reference/block-storage/drivers/huawei-storage-driver.xml549(td) +msgid "The OS type for a Compute node." +msgstr "" + +#: ./doc/config-reference/block-storage/drivers/huawei-storage-driver.xml552(option) +msgid "HostIP" +msgstr "" + +#: ./doc/config-reference/block-storage/drivers/huawei-storage-driver.xml557(td) +msgid "The IPs for Compute nodes." +msgstr "" + +#: ./doc/config-reference/block-storage/drivers/huawei-storage-driver.xml564(para) +msgid "" +"You can configure one iSCSI target port for each or all Compute nodes. The " +"driver checks whether a target port IP address is configured for the current" +" Compute node. If not, select ." +msgstr "" + +#: ./doc/config-reference/block-storage/drivers/huawei-storage-driver.xml571(para) +msgid "" +"You can configure multiple storage pools in one configuration file, which " +"supports the use of multiple storage pools in a storage system. (HVS allows " +"configuration of only one storage pool.)" +msgstr "" + +#: ./doc/config-reference/block-storage/drivers/huawei-storage-driver.xml578(para) +msgid "" +"For details about LUN configuration information, see the " +"command in the command-line interface (CLI) documentation or run the " +" on the storage system CLI." +msgstr "" + +#: ./doc/config-reference/block-storage/drivers/huawei-storage-driver.xml587(para) +msgid "" +"After the driver is loaded, the storage system obtains any modification of " +"the driver configuration file in real time and you do not need to restart " +"the cinder-volume service." +msgstr "" + +#: ./doc/config-reference/block-storage/drivers/glusterfs-driver.xml6(title) +msgid "GlusterFS driver" +msgstr "" + +#: ./doc/config-reference/block-storage/drivers/glusterfs-driver.xml7(para) +msgid "" +"GlusterFS is an open-source scalable distributed file system that is able to" +" grow to petabytes and beyond in size. More information can be found on " +"Gluster's homepage." +msgstr "" + +#: ./doc/config-reference/block-storage/drivers/glusterfs-driver.xml12(para) +msgid "" +"This driver enables use of GlusterFS in a similar fashion as the NFS driver." +" It supports basic volume operations, and like NFS, does not support " +"snapshot/clone." +msgstr "" + +#: ./doc/config-reference/block-storage/drivers/glusterfs-driver.xml16(para) +msgid "" +"You must use a Linux kernel of version 3.4 or greater (or version 2.6.32 or " +"greater in RHEL/CentOS 6.3+) when working with Gluster-based volumes. See " +"Bug " +"1177103 for more information." +msgstr "" + +#: ./doc/config-reference/block-storage/drivers/glusterfs-driver.xml22(para) +msgid "" +"To use Cinder with GlusterFS, first set the volume_driver" +" in cinder.conf:" +msgstr "" + +#: ./doc/config-reference/block-storage/drivers/glusterfs-driver.xml26(para) +msgid "" +"The following table contains the configuration options supported by the " +"GlusterFS driver." +msgstr "" + +#: ./doc/config-reference/block-storage/drivers/emc-volume-driver.xml5(title) +msgid "EMC SMI-S iSCSI driver" +msgstr "" + +#: ./doc/config-reference/block-storage/drivers/emc-volume-driver.xml6(para) +msgid "" +"The EMC SMI-S iSCSI driver, which is based on the iSCSI driver, can create, " +"delete, attach, and detach volumes, create and delete snapshots, and so on." +msgstr "" + +#: ./doc/config-reference/block-storage/drivers/emc-volume-driver.xml9(para) +msgid "" +"The EMC SMI-S iSCSI driver runs volume operations by communicating with the " +"back-end EMC storage. It uses a CIM client in Python called PyWBEM to " +"perform CIM operations over HTTP." +msgstr "" + +#: ./doc/config-reference/block-storage/drivers/emc-volume-driver.xml13(para) +msgid "" +"The EMC CIM Object Manager (ECOM) is packaged with the EMC SMI-S provider. " +"It is a CIM server that enables CIM clients to perform CIM operations over " +"HTTP by using SMI-S in the back-end for EMC storage operations." +msgstr "" + +#: ./doc/config-reference/block-storage/drivers/emc-volume-driver.xml17(para) +msgid "" +"The EMC SMI-S Provider supports the SNIA Storage Management Initiative " +"(SMI), an ANSI standard for storage management. It supports VMAX and VNX " +"storage systems." +msgstr "" + +#: ./doc/config-reference/block-storage/drivers/emc-volume-driver.xml21(title) +#: ./doc/config-reference/block-storage/drivers/hp-3par-driver.xml16(title) +#: ./doc/config-reference/block-storage/drivers/hds-volume-driver.xml17(title) +msgid "System requirements" +msgstr "" + +#: ./doc/config-reference/block-storage/drivers/emc-volume-driver.xml22(para) +msgid "" +"EMC SMI-S Provider V4.5.1 and higher is required. You can download SMI-S " +"from the EMC Powerlink web " +"site. See the EMC SMI-S Provider release notes for installation " +"instructions." +msgstr "" + +#: ./doc/config-reference/block-storage/drivers/emc-volume-driver.xml27(para) +msgid "EMC storage VMAX Family and VNX Series are supported." +msgstr "" + +#: ./doc/config-reference/block-storage/drivers/emc-volume-driver.xml32(para) +msgid "VMAX and VNX arrays support these operations:" +msgstr "" + +#: ./doc/config-reference/block-storage/drivers/emc-volume-driver.xml54(para) +msgid "Create cloned volume" +msgstr "" + +#: ./doc/config-reference/block-storage/drivers/emc-volume-driver.xml63(para) +msgid "Only VNX supports these operations:" +msgstr "" + +#: ./doc/config-reference/block-storage/drivers/emc-volume-driver.xml69(para) +msgid "Only thin provisioning is supported." +msgstr "" + +#: ./doc/config-reference/block-storage/drivers/emc-volume-driver.xml72(title) +msgid "Task flow" +msgstr "" + +#: ./doc/config-reference/block-storage/drivers/emc-volume-driver.xml74(title) +msgid "To set up the EMC SMI-S iSCSI driver" +msgstr "" + +#: ./doc/config-reference/block-storage/drivers/emc-volume-driver.xml76(para) +msgid "" +"Install the python-pywbem package for your distribution. " +"See ." +msgstr "" + +#: ./doc/config-reference/block-storage/drivers/emc-volume-driver.xml81(para) +msgid "" +"Download SMI-S from PowerLink and install it. Add your VNX/VMAX arrays to " +"SMI-S." +msgstr "" + +#: ./doc/config-reference/block-storage/drivers/emc-volume-driver.xml83(para) +msgid "" +"For information, see and the SMI-S release " +"notes." +msgstr "" + +#: ./doc/config-reference/block-storage/drivers/emc-volume-driver.xml87(para) +msgid "Register with VNX. See ." +msgstr "" + +#: ./doc/config-reference/block-storage/drivers/emc-volume-driver.xml91(para) +msgid "Create a masking view on VMAX. See ." +msgstr "" + +#: ./doc/config-reference/block-storage/drivers/emc-volume-driver.xml96(title) +msgid "Install the python-pywbem package" +msgstr "" + +#: ./doc/config-reference/block-storage/drivers/emc-volume-driver.xml99(para) +msgid "" +"Install the python-pywbem package for your distribution:" +msgstr "" + +#: ./doc/config-reference/block-storage/drivers/emc-volume-driver.xml103(para) +msgid "On Ubuntu:" +msgstr "" + +#: ./doc/config-reference/block-storage/drivers/emc-volume-driver.xml107(para) +msgid "On openSUSE:" +msgstr "" + +#: ./doc/config-reference/block-storage/drivers/emc-volume-driver.xml111(para) +msgid "On Fedora:" +msgstr "" + +#: ./doc/config-reference/block-storage/drivers/emc-volume-driver.xml119(title) +msgid "Set up SMI-S" +msgstr "" + +#: ./doc/config-reference/block-storage/drivers/emc-volume-driver.xml120(para) +msgid "" +"You can install SMI-S on a non-OpenStack host. Supported platforms include " +"different flavors of Windows, Red Hat, and SUSE Linux. The host can be " +"either a physical server or VM hosted by an ESX server. See the EMC SMI-S " +"Provider release notes for supported platforms and installation " +"instructions." +msgstr "" + +#: ./doc/config-reference/block-storage/drivers/emc-volume-driver.xml127(para) +msgid "" +"You must discover storage arrays on the SMI-S server before you can use the " +"Cinder driver. Follow instructions in the SMI-S release notes." +msgstr "" + +#: ./doc/config-reference/block-storage/drivers/emc-volume-driver.xml131(para) +msgid "" +"SMI-S is usually installed at /opt/emc/ECIM/ECOM/bin on" +" Linux and C:\\Program Files\\EMC\\ECIM\\ECOM\\bin on " +"Windows. After you install and configure SMI-S, go to that directory and " +"type ." +msgstr "" + +#: ./doc/config-reference/block-storage/drivers/emc-volume-driver.xml138(para) +msgid "" +"Use in to add an array. Use " +" and examine the output after the array is added. Make sure " +"that the arrays are recognized by the SMI-S server before using the EMC " +"Cinder driver." +msgstr "" + +#: ./doc/config-reference/block-storage/drivers/emc-volume-driver.xml146(title) +msgid "Register with VNX" +msgstr "" + +#: ./doc/config-reference/block-storage/drivers/emc-volume-driver.xml147(para) +msgid "" +"To export a VNX volume to a Compute node, you must register the node with " +"VNX." +msgstr "" + +#: ./doc/config-reference/block-storage/drivers/emc-volume-driver.xml149(para) +msgid "" +"On the Compute node 1.1.1.1, run these commands (assume " +"10.10.61.35 is the iscsi target):" +msgstr "" + +#: ./doc/config-reference/block-storage/drivers/emc-volume-driver.xml152(literal) +#: ./doc/config-reference/block-storage/drivers/emc-volume-driver.xml158(literal) +msgid "10.10.61.35" +msgstr "" + +#: ./doc/config-reference/block-storage/drivers/emc-volume-driver.xml156(para) +msgid "" +"Log in to VNX from the Compute node by using the target corresponding to the" +" SPA port:" +msgstr "" + +#: ./doc/config-reference/block-storage/drivers/emc-volume-driver.xml158(literal) +msgid "iqn.1992-04.com.emc:cx.apm01234567890.a0" +msgstr "" + +#: ./doc/config-reference/block-storage/drivers/emc-volume-driver.xml159(para) +msgid "" +"Assume iqn.1993-08.org.debian:01:1a2b3c4d5f6g is the " +"initiator name of the Compute node. Log in to Unisphere, go to " +"VNX00000->Hosts->Initiators, refresh and wait until" +" initiator iqn.1993-08.org.debian:01:1a2b3c4d5f6g with SP" +" Port A-8v0 appears." +msgstr "" + +#: ./doc/config-reference/block-storage/drivers/emc-volume-driver.xml167(para) +msgid "" +"Click Register, select " +"CLARiiON/VNX, and enter the myhost1 " +"host name and myhost1 IP address. Click " +"Register. Now the 1.1.1.1 host " +"appears under HostsHost List " +"as well." +msgstr "" + +#: ./doc/config-reference/block-storage/drivers/emc-volume-driver.xml172(para) +msgid "Log out of VNX on the Compute node:" +msgstr "" + +#: ./doc/config-reference/block-storage/drivers/emc-volume-driver.xml174(para) +msgid "" +"Log in to VNX from the Compute node using the target corresponding to the " +"SPB port:" +msgstr "" + +#: ./doc/config-reference/block-storage/drivers/emc-volume-driver.xml177(para) +msgid "In Unisphere, register the initiator with the SPB port." +msgstr "" + +#: ./doc/config-reference/block-storage/drivers/emc-volume-driver.xml179(para) +msgid "Log out:" +msgstr "" + +#: ./doc/config-reference/block-storage/drivers/emc-volume-driver.xml183(title) +msgid "Create a masking view on VMAX" +msgstr "" + +#: ./doc/config-reference/block-storage/drivers/emc-volume-driver.xml184(para) +msgid "" +"For VMAX, you must set up the Unisphere for VMAX server. On the Unisphere " +"for VMAX server, create initiator group, storage group, and port group and " +"put them in a masking view. Initiator group contains the initiator names of " +"the OpenStack hosts. Storage group must have at least six gatekeepers." +msgstr "" + +#: ./doc/config-reference/block-storage/drivers/emc-volume-driver.xml194(para) +msgid "" +"Make the following changes in /etc/cinder/cinder.conf." +msgstr "" + +#: ./doc/config-reference/block-storage/drivers/emc-volume-driver.xml196(para) +msgid "" +"For VMAX, add the following entries, where 10.10.61.45 is" +" the IP address of the VMAX iscsi target:" +msgstr "" + +#: ./doc/config-reference/block-storage/drivers/emc-volume-driver.xml203(para) +msgid "" +"For VNX, add the following entries, where 10.10.61.35 is " +"the IP address of the VNX iscsi target:" +msgstr "" + +#: ./doc/config-reference/block-storage/drivers/emc-volume-driver.xml210(para) +msgid "" +"Restart the cinder-volume " +"service." +msgstr "" + +#: ./doc/config-reference/block-storage/drivers/emc-volume-driver.xml214(title) +msgid "cinder_emc_config.xml configuration file" +msgstr "" + +#: ./doc/config-reference/block-storage/drivers/emc-volume-driver.xml216(para) +msgid "" +"Create the file /etc/cinder/cinder_emc_config.xml. You " +"do not need to restart the service for this change." +msgstr "" + +#: ./doc/config-reference/block-storage/drivers/emc-volume-driver.xml220(para) +msgid "For VMAX, add the following lines to the XML file:" +msgstr "" + +#: ./doc/config-reference/block-storage/drivers/emc-volume-driver.xml231(para) +msgid "For VNX, add the following lines to the XML file:" +msgstr "" + +#: ./doc/config-reference/block-storage/drivers/emc-volume-driver.xml241(para) +msgid "" +"To attach VMAX volumes to an OpenStack VM, you must create a Masking View by" +" using Unisphere for VMAX. The Masking View must have an Initiator Group " +"that contains the initiator of the OpenStack compute node that hosts the VM." +msgstr "" + +#: ./doc/config-reference/block-storage/drivers/emc-volume-driver.xml246(para) +msgid "" +"StorageType is the thin pool where user wants to create the volume from. " +"Only thin LUNs are supported by the plug-in. Thin pools can be created using" +" Unisphere for VMAX and VNX." +msgstr "" + +#: ./doc/config-reference/block-storage/drivers/emc-volume-driver.xml250(para) +msgid "" +"EcomServerIp and EcomServerPort are the IP address and port number of the " +"ECOM server which is packaged with SMI-S. EcomUserName and EcomPassword are " +"credentials for the ECOM server." +msgstr "" + +#: ./doc/config-reference/block-storage/drivers/hp-3par-driver.xml4(title) +msgid "HP 3PAR Fibre Channel and iSCSI drivers" +msgstr "" + +#: ./doc/config-reference/block-storage/drivers/hp-3par-driver.xml5(para) +msgid "" +"The HP3PARFCDriver and " +"HP3PARISCSIDriver drivers, which are based on the Block" +" Storage Service (Cinder) plug-in architecture, run volume operations by " +"communicating with the HP 3PAR storage system over HTTP, HTTPS, and SSH " +"connections. The HTTP and HTTPS communications use " +"hp3parclient, which is part of the Python standard " +"library." +msgstr "" + +#: ./doc/config-reference/block-storage/drivers/hp-3par-driver.xml13(para) +msgid "" +"For information about how to manage HP 3PAR storage systems, see the HP 3PAR" +" user documentation." +msgstr "" + +#: ./doc/config-reference/block-storage/drivers/hp-3par-driver.xml17(para) +msgid "" +"To use the HP 3PAR drivers, install the following software and components on" +" the HP 3PAR storage system:" +msgstr "" + +#: ./doc/config-reference/block-storage/drivers/hp-3par-driver.xml22(para) +msgid "HP 3PAR Operating System software version 3.1.2 (MU2) or higher" +msgstr "" + +#: ./doc/config-reference/block-storage/drivers/hp-3par-driver.xml26(para) +msgid "HP 3PAR Web Services API Server must be enabled and running" +msgstr "" + +#: ./doc/config-reference/block-storage/drivers/hp-3par-driver.xml30(para) +msgid "One Common Provisioning Group (CPG)" +msgstr "" + +#: ./doc/config-reference/block-storage/drivers/hp-3par-driver.xml33(para) +msgid "" +"Additionally, you must install the hp3parclient version " +"2.0 or newer from the Python standard library on the system with the enabled" +" Block Storage Service volume drivers." +msgstr "" + +#: ./doc/config-reference/block-storage/drivers/hp-3par-driver.xml45(para) +msgid "Create volumes." +msgstr "" + +#: ./doc/config-reference/block-storage/drivers/hp-3par-driver.xml48(para) +msgid "Delete volumes." +msgstr "" + +#: ./doc/config-reference/block-storage/drivers/hp-3par-driver.xml51(para) +msgid "Extend volumes." +msgstr "" + +#: ./doc/config-reference/block-storage/drivers/hp-3par-driver.xml54(para) +msgid "Attach volumes." +msgstr "" + +#: ./doc/config-reference/block-storage/drivers/hp-3par-driver.xml57(para) +msgid "Detach volumes." +msgstr "" + +#: ./doc/config-reference/block-storage/drivers/hp-3par-driver.xml60(para) +msgid "Create snapshots." +msgstr "" + +#: ./doc/config-reference/block-storage/drivers/hp-3par-driver.xml63(para) +msgid "Delete snapshots." +msgstr "" + +#: ./doc/config-reference/block-storage/drivers/hp-3par-driver.xml66(para) +msgid "Create volumes from snapshots." +msgstr "" + +#: ./doc/config-reference/block-storage/drivers/hp-3par-driver.xml69(para) +msgid "Create cloned volumes." +msgstr "" + +#: ./doc/config-reference/block-storage/drivers/hp-3par-driver.xml72(para) +msgid "Copy images to volumes." +msgstr "" + +#: ./doc/config-reference/block-storage/drivers/hp-3par-driver.xml75(para) +msgid "Copy volumes to images." +msgstr "" + +#: ./doc/config-reference/block-storage/drivers/hp-3par-driver.xml78(para) +msgid "" +"Volume type support for both HP 3PAR drivers includes the ability to set the" +" following capabilities in the OpenStack Cinder API " +"cinder.api.contrib.types_extra_specs volume type extra " +"specs extension module:" +msgstr "" + +#: ./doc/config-reference/block-storage/drivers/hp-3par-driver.xml85(literal) +msgid "hp3par:cpg" +msgstr "" + +#: ./doc/config-reference/block-storage/drivers/hp-3par-driver.xml88(literal) +msgid "hp3par:snap_cpg" +msgstr "" + +#: ./doc/config-reference/block-storage/drivers/hp-3par-driver.xml91(literal) +msgid "hp3par:provisioning" +msgstr "" + +#: ./doc/config-reference/block-storage/drivers/hp-3par-driver.xml94(literal) +msgid "hp3par:persona" +msgstr "" + +#: ./doc/config-reference/block-storage/drivers/hp-3par-driver.xml97(literal) +msgid "hp3par:vvs" +msgstr "" + +#: ./doc/config-reference/block-storage/drivers/hp-3par-driver.xml100(literal) +msgid "qos:maxBWS" +msgstr "" + +#: ./doc/config-reference/block-storage/drivers/hp-3par-driver.xml103(literal) +msgid "qos:maxIOPS" +msgstr "" + +#: ./doc/config-reference/block-storage/drivers/hp-3par-driver.xml106(para) +msgid "" +"To work with the default filter scheduler, the key values are case sensitive" +" and scoped with hp3par: or qos:. For " +"information about how to set the key-value pairs and associate them with a " +"volume type, run the following command: " +msgstr "" + +#: ./doc/config-reference/block-storage/drivers/hp-3par-driver.xml116(para) +msgid "" +"Volumes that are cloned only support extra specs keys cpg, snap_cpg, " +"provisioning and vvs. The others are ignored. In addition the comments " +"section of the cloned volume in the HP 3PAR StoreServ storage array is not " +"populated." +msgstr "" + +#: ./doc/config-reference/block-storage/drivers/hp-3par-driver.xml122(para) +msgid "" +"The following keys require that the HP 3PAR StoreServ storage array has a " +"Priority Optimization license installed." +msgstr "" + +#: ./doc/config-reference/block-storage/drivers/hp-3par-driver.xml127(para) +msgid "" +"hp3par:vvs - The virtual volume set name that has been " +"predefined by the Administrator with Quality of Service (QoS) rules " +"associated to it. If you specify hp3par:vvs, the " +"qos:maxIOPS and qos:maxBWS settings " +"are ignored." +msgstr "" + +#: ./doc/config-reference/block-storage/drivers/hp-3par-driver.xml137(para) +msgid "" +"qos:maxBWS - The QoS I/O issue count rate limit in MBs. " +"If not set, the I/O issue bandwidth rate has no limit." +msgstr "" + +#: ./doc/config-reference/block-storage/drivers/hp-3par-driver.xml142(para) +msgid "" +"qos:maxIOPS - The QoS I/O issue count rate limit. If not " +"set, the I/O issue count rate has no limit." +msgstr "" + +#: ./doc/config-reference/block-storage/drivers/hp-3par-driver.xml147(para) +msgid "" +"If volume types are not used or a particular key is not set for a volume " +"type, the following defaults are used." +msgstr "" + +#: ./doc/config-reference/block-storage/drivers/hp-3par-driver.xml152(para) +msgid "" +"hp3par:cpg - Defaults to the " +"hp3par_cpg setting in the " +"cinder.conf file." +msgstr "" + +#: ./doc/config-reference/block-storage/drivers/hp-3par-driver.xml157(para) +msgid "" +"hp3par:snap_cpg - Defaults to the " +"hp3par_snap setting in the " +"cinder.conf file. If hp3par_snap is " +"not set, it defaults to the hp3par_cpg setting." +msgstr "" + +#: ./doc/config-reference/block-storage/drivers/hp-3par-driver.xml165(para) +msgid "" +"hp3par:provisioning - Defaults to thin provisioning, the " +"valid values are thin and full." +msgstr "" + +#: ./doc/config-reference/block-storage/drivers/hp-3par-driver.xml171(para) +msgid "" +"hp3par:persona - Defaults to the 1 – " +"Generic persona. The valid values are, 1 – " +"Generic, 2 - Generic-ALUA, 6 - " +"Generic-legacy, 7 - HPUX-legacy, 8 - " +"AIX-legacy, 9 – EGENERA, 10 - ONTAP-" +"legacy, 11 – VMware, and 12 - " +"OpenVMS." +msgstr "" + +#: ./doc/config-reference/block-storage/drivers/hp-3par-driver.xml186(title) +msgid "Enable the HP 3PAR Fibre Channel and iSCSI drivers" +msgstr "" + +#: ./doc/config-reference/block-storage/drivers/hp-3par-driver.xml188(para) +msgid "" +"The HP3PARFCDriver and " +"HP3PARISCSIDriver are installed with the OpenStack " +"software." +msgstr "" + +#: ./doc/config-reference/block-storage/drivers/hp-3par-driver.xml193(para) +msgid "" +"Install the hp3parclient Python package on the " +"OpenStack Block Storage system. " +msgstr "" + +#: ./doc/config-reference/block-storage/drivers/hp-3par-driver.xml200(para) +msgid "" +"Verify that the HP 3PAR Web Services API server is enabled and running on " +"the HP 3PAR storage system." +msgstr "" + +#: ./doc/config-reference/block-storage/drivers/hp-3par-driver.xml205(para) +msgid "" +"Log onto the HP 3PAR storage system with administrator " +"access." +msgstr "" + +#: ./doc/config-reference/block-storage/drivers/hp-3par-driver.xml210(para) +msgid "" +"View the current state of the Web Services API Server. " +"" +msgstr "" + +#: ./doc/config-reference/block-storage/drivers/hp-3par-driver.xml217(para) +msgid "If the Web Services API Server is disabled, start it." +msgstr "" + +#: ./doc/config-reference/block-storage/drivers/hp-3par-driver.xml227(para) +msgid "" +"To stop the Web Services API Server, use the stopwsapi command. For other " +"options run the command." +msgstr "" + +#: ./doc/config-reference/block-storage/drivers/hp-3par-driver.xml224(para) +msgid "" +"If the HTTP or HTTPS state is disabled, enable one of them. " +"or " +msgstr "" + +#: ./doc/config-reference/block-storage/drivers/hp-3par-driver.xml234(para) +msgid "" +"If you are not using an existing CPG, create a CPG on the HP 3PAR storage " +"system to be used as the default location for creating volumes." +msgstr "" + +#: ./doc/config-reference/block-storage/drivers/hp-3par-driver.xml239(para) +msgid "" +"Make the following changes in the " +"/etc/cinder/cinder.conf file." +msgstr "" + +#: ./doc/config-reference/block-storage/drivers/hp-3par-driver.xml243(emphasis) +msgid "## REQUIRED SETTINGS" +msgstr "" + +#: ./doc/config-reference/block-storage/drivers/hp-3par-driver.xml277(emphasis) +msgid "## OPTIONAL SETTINGS" +msgstr "" + +#: ./doc/config-reference/block-storage/drivers/hp-3par-driver.xml291(para) +msgid "" +"You can enable only one driver on each cinder instance unless you enable " +"multiple back-end support. See the Cinder multiple back-end support " +"instructions to enable this feature." +msgstr "" + +#: ./doc/config-reference/block-storage/drivers/hp-3par-driver.xml298(para) +msgid "" +"You can configure one or more iSCSI addresses by using the " +" option. When you configure multiple " +"addresses, the driver selects the iSCSI port with the fewest active volumes " +"at attach time. The IP address might include an IP port by using a colon " +"(:) to separate the address from port. If you do not " +"define an IP port, the default port 3260 is used. Separate IP addresses with" +" a comma (,). The " +"/ options might " +"be used as an alternative to for single " +"port iSCSI configuration." +msgstr "" + +#: ./doc/config-reference/block-storage/drivers/hp-3par-driver.xml317(para) +msgid "" +"Save the changes to the cinder.conf file and restart " +"the cinder-volume service." +msgstr "" + +#: ./doc/config-reference/block-storage/drivers/hp-3par-driver.xml323(para) +msgid "" +"The HP 3PAR Fibre Channel and iSCSI drivers are now enabled on your " +"OpenStack system. If you experience problems, review the Block Storage " +"Service log files for errors." +msgstr "" + +#: ./doc/config-reference/block-storage/drivers/dell-equallogic-driver.xml6(title) +msgid "Dell EqualLogic volume driver" +msgstr "" + +#: ./doc/config-reference/block-storage/drivers/dell-equallogic-driver.xml7(para) +msgid "" +"The Dell EqualLogic volume driver interacts with configured EqualLogic " +"arrays and supports various operations, such as volume creation and " +"deletion, volume attachment and detachment, snapshot creation and deletion, " +"and clone creation." +msgstr "" + +#: ./doc/config-reference/block-storage/drivers/dell-equallogic-driver.xml12(para) +msgid "" +"To configure and use a Dell EqualLogic array with Block Storage, modify your" +" cinder.conf as follows." +msgstr "" + +#: ./doc/config-reference/block-storage/drivers/dell-equallogic-driver.xml15(para) +msgid "" +"Set the option to the Dell EqualLogic volume " +"driver:" +msgstr "" + +#: ./doc/config-reference/block-storage/drivers/dell-equallogic-driver.xml18(para) +msgid "" +"Set the option to the IP address to reach the " +"EqualLogic Group through SSH:" +msgstr "" + +#: ./doc/config-reference/block-storage/drivers/dell-equallogic-driver.xml21(para) +msgid "" +"Set the option to the user name to login to the " +"Group manager:" +msgstr "" + +#: ./doc/config-reference/block-storage/drivers/dell-equallogic-driver.xml24(para) +msgid "" +"Set the option to the password to login the " +"Group manager with:" +msgstr "" + +#: ./doc/config-reference/block-storage/drivers/dell-equallogic-driver.xml27(para) +msgid "" +"Optionally set the option to false to " +"disable creation of thin-provisioned volumes:" +msgstr "" + +#: ./doc/config-reference/block-storage/drivers/dell-equallogic-driver.xml31(para) +msgid "" +"The following table describes additional options that the driver supports:" +msgstr "" + +#: ./doc/config-reference/block-storage/drivers/ibm-storwize-svc-driver.xml5(title) +msgid "IBM Storwize family and SVC volume driver" +msgstr "" + +#: ./doc/config-reference/block-storage/drivers/ibm-storwize-svc-driver.xml6(para) +msgid "" +"The volume management driver for Storwize family and SAN Volume Controller " +"(SVC) provides OpenStack Compute instances with access to IBM Storwize " +"family or SVC storage systems." +msgstr "" + +#: ./doc/config-reference/block-storage/drivers/ibm-storwize-svc-driver.xml11(title) +msgid "Configure the Storwize family and SVC system" +msgstr "" + +#: ./doc/config-reference/block-storage/drivers/ibm-storwize-svc-driver.xml13(title) +msgid "Network configuration" +msgstr "" + +#: ./doc/config-reference/block-storage/drivers/ibm-storwize-svc-driver.xml14(para) +msgid "" +"The Storwize family or SVC system must be configured for iSCSI, Fibre " +"Channel, or both." +msgstr "" + +#: ./doc/config-reference/block-storage/drivers/ibm-storwize-svc-driver.xml16(para) +msgid "" +"If using iSCSI, each Storwize family or SVC node should have at least one " +"iSCSI IP address. The IBM Storwize/SVC driver uses an iSCSI IP address " +"associated with the volume's preferred node (if available) to attach the " +"volume to the instance, otherwise it uses the first available iSCSI IP " +"address of the system. The driver obtains the iSCSI IP address directly from" +" the storage system; you do not need to provide these iSCSI IP addresses " +"directly to the driver." +msgstr "" + +#: ./doc/config-reference/block-storage/drivers/ibm-storwize-svc-driver.xml27(para) +msgid "" +"If using iSCSI, ensure that the compute nodes have iSCSI network access to " +"the Storwize family or SVC system." +msgstr "" + +#: ./doc/config-reference/block-storage/drivers/ibm-storwize-svc-driver.xml32(para) +msgid "" +"OpenStack Nova's Grizzly version supports iSCSI multipath. Once this is " +"configured on the Nova host (outside the scope of this documentation), " +"multipath is enabled." +msgstr "" + +#: ./doc/config-reference/block-storage/drivers/ibm-storwize-svc-driver.xml37(para) +msgid "" +"If using Fibre Channel (FC), each Storwize family or SVC node should have at" +" least one WWPN port configured. If the " +"storwize_svc_multipath_enabled flag is set to True in the" +" Cinder configuration file, the driver uses all available WWPNs to attach " +"the volume to the instance (details about the configuration flags appear in " +"the next section). If the" +" flag is not set, the driver uses the WWPN associated with the volume's " +"preferred node (if available), otherwise it uses the first available WWPN of" +" the system. The driver obtains the WWPNs directly from the storage system; " +"you do not need to provide these WWPNs directly to the driver." +msgstr "" + +#: ./doc/config-reference/block-storage/drivers/ibm-storwize-svc-driver.xml53(para) +msgid "" +"If using FC, ensure that the compute nodes have FC connectivity to the " +"Storwize family or SVC system." +msgstr "" + +#: ./doc/config-reference/block-storage/drivers/ibm-storwize-svc-driver.xml59(title) +msgid "iSCSI CHAP authentication" +msgstr "" + +#: ./doc/config-reference/block-storage/drivers/ibm-storwize-svc-driver.xml67(para) +msgid "" +"CHAP secrets are added to existing hosts as well as newly-created ones. If " +"the CHAP option is enabled, hosts will not be able to access the storage " +"without the generated secrets." +msgstr "" + +#: ./doc/config-reference/block-storage/drivers/ibm-storwize-svc-driver.xml74(para) +msgid "" +"Not all OpenStack Compute drivers support CHAP authentication. Please check " +"compatibility before using." +msgstr "" + +#: ./doc/config-reference/block-storage/drivers/ibm-storwize-svc-driver.xml79(para) +msgid "" +"CHAP secrets are passed from OpenStack Block Storage to Compute in clear " +"text. This communication should be secured to ensure that CHAP secrets are " +"not discovered." +msgstr "" + +#: ./doc/config-reference/block-storage/drivers/ibm-storwize-svc-driver.xml60(para) +msgid "" +"If using iSCSI for data access and the " +"storwize_svc_iscsi_chap_enabled is set to " +"True, the driver will associate randomly-generated CHAP " +"secrets with all hosts on the Storwize family system. OpenStack compute " +"nodes use these secrets when creating iSCSI connections. " +"" +msgstr "" + +#: ./doc/config-reference/block-storage/drivers/ibm-storwize-svc-driver.xml86(title) +msgid "Configure storage pools" +msgstr "" + +#: ./doc/config-reference/block-storage/drivers/ibm-storwize-svc-driver.xml87(para) +msgid "" +"Each instance of the IBM Storwize/SVC driver allocates all volumes in a " +"single pool. The pool should be created in advance and be provided to the " +"driver using the storwize_svc_volpool_name configuration " +"flag. Details about the configuration flags and how to provide the flags to " +"the driver appear in the next " +"section." +msgstr "" + +#: ./doc/config-reference/block-storage/drivers/ibm-storwize-svc-driver.xml98(title) +msgid "Configure user authentication for the driver" +msgstr "" + +#: ./doc/config-reference/block-storage/drivers/ibm-storwize-svc-driver.xml100(para) +msgid "" +"The driver requires access to the Storwize family or SVC system management " +"interface. The driver communicates with the management using SSH. The driver" +" should be provided with the Storwize family or SVC management IP using the " +"san_ip flag, and the management port should be provided " +"by the san_ssh_port flag. By default, the port value is " +"configured to be port 22 (SSH)." +msgstr "" + +#: ./doc/config-reference/block-storage/drivers/ibm-storwize-svc-driver.xml110(para) +msgid "" +"Make sure the compute node running the nova-volume management driver has SSH" +" network access to the storage system." +msgstr "" + +#: ./doc/config-reference/block-storage/drivers/ibm-storwize-svc-driver.xml114(para) +msgid "" +"To allow the driver to communicate with the Storwize family or SVC system, " +"you must provide the driver with a user on the storage system. The driver " +"has two authentication methods: password-based authentication and SSH key " +"pair authentication. The user should have an Administrator role. It is " +"suggested to create a new user for the management driver. Please consult " +"with your storage and security administrator regarding the preferred " +"authentication method and how passwords or SSH keys should be stored in a " +"secure manner." +msgstr "" + +#: ./doc/config-reference/block-storage/drivers/ibm-storwize-svc-driver.xml125(para) +msgid "" +"When creating a new user on the Storwize or SVC system, make sure the user " +"belongs to the Administrator group or to another group that has an " +"Administrator role." +msgstr "" + +#: ./doc/config-reference/block-storage/drivers/ibm-storwize-svc-driver.xml130(para) +msgid "" +"If using password authentication, assign a password to the user on the " +"Storwize or SVC system. The driver configuration flags for the user and " +"password are san_login and " +"san_password, respectively." +msgstr "" + +#: ./doc/config-reference/block-storage/drivers/ibm-storwize-svc-driver.xml136(para) +msgid "" +"If you are using the SSH key pair authentication, create SSH private and " +"public keys using the instructions below or by any other method. Associate " +"the public key with the user by uploading the public key: select the " +"\"choose file\" option in the Storwize family or SVC management GUI under " +"\"SSH public key\". Alternatively, you may associate the SSH public key " +"using the command line interface; details can be found in the Storwize and " +"SVC documentation. The private key should be provided to the driver using " +"the san_private_key configuration flag." +msgstr "" + +#: ./doc/config-reference/block-storage/drivers/ibm-storwize-svc-driver.xml150(title) +msgid "Create a SSH key pair with OpenSSH" +msgstr "" + +#: ./doc/config-reference/block-storage/drivers/ibm-storwize-svc-driver.xml151(para) +msgid "You can create an SSH key pair using OpenSSH, by running:" +msgstr "" + +#: ./doc/config-reference/block-storage/drivers/ibm-storwize-svc-driver.xml154(para) +msgid "" +"The command prompts for a file to save the key pair. For example, if you " +"select 'key' as the filename, two files are created: key " +"and key.pub. The key file holds the " +"private SSH key and key.pub holds the public SSH key." +msgstr "" + +#: ./doc/config-reference/block-storage/drivers/ibm-storwize-svc-driver.xml161(para) +msgid "The command also prompts for a pass phrase, which should be empty." +msgstr "" + +#: ./doc/config-reference/block-storage/drivers/ibm-storwize-svc-driver.xml163(para) +msgid "" +"The private key file should be provided to the driver using the " +"san_private_key configuration flag. The public key should" +" be uploaded to the Storwize family or SVC system using the storage " +"management GUI or command line interface." +msgstr "" + +#: ./doc/config-reference/block-storage/drivers/ibm-storwize-svc-driver.xml169(para) +msgid "Ensure that Cinder has read permissions on the private key file." +msgstr "" + +#: ./doc/config-reference/block-storage/drivers/ibm-storwize-svc-driver.xml175(title) +msgid "Configure the Storwize family and SVC driver" +msgstr "" + +#: ./doc/config-reference/block-storage/drivers/ibm-storwize-svc-driver.xml177(title) +msgid "Enable the Storwize family and SVC driver" +msgstr "" + +#: ./doc/config-reference/block-storage/drivers/ibm-storwize-svc-driver.xml178(para) +msgid "" +"Set the volume driver to the Storwize family and SVC driver by setting the " +"volume_driver option in cinder.conf " +"as follows:" +msgstr "" + +#: ./doc/config-reference/block-storage/drivers/ibm-storwize-svc-driver.xml185(title) +msgid "Storwize family and SVC driver options in cinder.conf" +msgstr "" + +#: ./doc/config-reference/block-storage/drivers/ibm-storwize-svc-driver.xml187(para) +msgid "" +"The following options specify default values for all volumes. Some can be " +"over-ridden using volume types, which are described below." +msgstr "" + +#: ./doc/config-reference/block-storage/drivers/ibm-storwize-svc-driver.xml191(caption) +msgid "List of configuration flags for Storwize storage and SVC driver" +msgstr "" + +#: ./doc/config-reference/block-storage/drivers/ibm-storwize-svc-driver.xml207(literal) +msgid "san_ip" +msgstr "" + +#: ./doc/config-reference/block-storage/drivers/ibm-storwize-svc-driver.xml211(para) +msgid "Management IP or host name" +msgstr "" + +#: ./doc/config-reference/block-storage/drivers/ibm-storwize-svc-driver.xml215(literal) +msgid "san_ssh_port" +msgstr "" + +#: ./doc/config-reference/block-storage/drivers/ibm-storwize-svc-driver.xml218(para) +msgid "22" +msgstr "" + +#: ./doc/config-reference/block-storage/drivers/ibm-storwize-svc-driver.xml219(para) +msgid "Management port" +msgstr "" + +#: ./doc/config-reference/block-storage/drivers/ibm-storwize-svc-driver.xml222(literal) +msgid "san_login" +msgstr "" + +#: ./doc/config-reference/block-storage/drivers/ibm-storwize-svc-driver.xml226(para) +msgid "Management login username" +msgstr "" + +#: ./doc/config-reference/block-storage/drivers/ibm-storwize-svc-driver.xml230(literal) +msgid "san_password" +msgstr "" + +#: ./doc/config-reference/block-storage/drivers/ibm-storwize-svc-driver.xml234(para) +msgid "" +"The authentication requires either a password " +"(san_password) or SSH private key " +"(san_private_key). One must be specified. If both are " +"specified, the driver uses only the SSH private key." +msgstr "" + +#: ./doc/config-reference/block-storage/drivers/ibm-storwize-svc-driver.xml232(para) +msgid "Required " +msgstr "" + +#: ./doc/config-reference/block-storage/drivers/ibm-storwize-svc-driver.xml244(para) +msgid "Management login password" +msgstr "" + +#: ./doc/config-reference/block-storage/drivers/ibm-storwize-svc-driver.xml248(literal) +msgid "san_private_key" +msgstr "" + +#: ./doc/config-reference/block-storage/drivers/ibm-storwize-svc-driver.xml250(para) +msgid "Required " +msgstr "" + +#: ./doc/config-reference/block-storage/drivers/ibm-storwize-svc-driver.xml254(para) +msgid "Management login SSH private key" +msgstr "" + +#: ./doc/config-reference/block-storage/drivers/ibm-storwize-svc-driver.xml260(literal) +msgid "storwize_svc_volpool_name" +msgstr "" + +#: ./doc/config-reference/block-storage/drivers/ibm-storwize-svc-driver.xml264(para) +msgid "Default pool name for volumes" +msgstr "" + +#: ./doc/config-reference/block-storage/drivers/ibm-storwize-svc-driver.xml269(literal) +msgid "storwize_svc_vol_rsize" +msgstr "" + +#: ./doc/config-reference/block-storage/drivers/ibm-storwize-svc-driver.xml272(para) +msgid "2" +msgstr "" + +#: ./doc/config-reference/block-storage/drivers/ibm-storwize-svc-driver.xml276(para) +msgid "" +"The driver creates thin-provisioned volumes by default. The " +"storwize_svc_vol_rsize flag defines the initial physical " +"allocation percentage for thin-provisioned volumes, or if set to " +"-1, the driver creates full allocated volumes. More " +"details about the available options are available in the Storwize family and" +" SVC documentation." +msgstr "" + +#: ./doc/config-reference/block-storage/drivers/ibm-storwize-svc-driver.xml273(para) +msgid "Initial physical allocation (percentage) " +msgstr "" + +#: ./doc/config-reference/block-storage/drivers/ibm-storwize-svc-driver.xml293(literal) +msgid "storwize_svc_vol_warning" +msgstr "" + +#: ./doc/config-reference/block-storage/drivers/ibm-storwize-svc-driver.xml296(para) +msgid "0 (disabled)" +msgstr "" + +#: ./doc/config-reference/block-storage/drivers/ibm-storwize-svc-driver.xml297(para) +msgid "" +"Space allocation warning threshold (percentage) " +msgstr "" + +#: ./doc/config-reference/block-storage/drivers/ibm-storwize-svc-driver.xml304(literal) +msgid "storwize_svc_vol_autoexpand" +msgstr "" + +#: ./doc/config-reference/block-storage/drivers/ibm-storwize-svc-driver.xml307(para) +#: ./doc/config-reference/block-storage/drivers/ibm-storwize-svc-driver.xml363(para) +#: ./doc/config-reference/block-storage/drivers/ibm-storwize-svc-driver.xml423(para) +#: ./doc/config-reference/block-storage/drivers/ibm-storwize-svc-driver.xml449(para) +msgid "True" +msgstr "" + +#: ./doc/config-reference/block-storage/drivers/ibm-storwize-svc-driver.xml310(para) +msgid "" +"Defines whether thin-provisioned volumes can be auto expanded by the storage" +" system, a value of True means that auto expansion is " +"enabled, a value of False disables auto expansion. " +"Details about this option can be found in the –autoexpand" +" flag of the Storwize family and SVC command line interface " +"mkvdisk command." +msgstr "" + +#: ./doc/config-reference/block-storage/drivers/ibm-storwize-svc-driver.xml308(para) +msgid "Enable or disable volume auto expand " +msgstr "" + +#: ./doc/config-reference/block-storage/drivers/ibm-storwize-svc-driver.xml328(literal) +msgid "storwize_svc_vol_grainsize" +msgstr "" + +#: ./doc/config-reference/block-storage/drivers/ibm-storwize-svc-driver.xml331(para) +msgid "256" +msgstr "" + +#: ./doc/config-reference/block-storage/drivers/ibm-storwize-svc-driver.xml332(para) +msgid "Volume grain size in KB" +msgstr "" + +#: ./doc/config-reference/block-storage/drivers/ibm-storwize-svc-driver.xml338(literal) +msgid "storwize_svc_vol_compression" +msgstr "" + +#: ./doc/config-reference/block-storage/drivers/ibm-storwize-svc-driver.xml342(para) +#: ./doc/config-reference/block-storage/drivers/ibm-storwize-svc-driver.xml433(para) +msgid "False" +msgstr "" + +#: ./doc/config-reference/block-storage/drivers/ibm-storwize-svc-driver.xml346(para) +msgid "" +"Defines whether Real-time Compression is used for the volumes created with " +"OpenStack. Details on Real-time Compression can be found in the Storwize " +"family and SVC documentation. The Storwize or SVC system must have " +"compression enabled for this feature to work." +msgstr "" + +#: ./doc/config-reference/block-storage/drivers/ibm-storwize-svc-driver.xml343(para) +msgid "Enable or disable Real-time Compression " +msgstr "" + +#: ./doc/config-reference/block-storage/drivers/ibm-storwize-svc-driver.xml360(literal) +msgid "storwize_svc_vol_easytier" +msgstr "" + +#: ./doc/config-reference/block-storage/drivers/ibm-storwize-svc-driver.xml366(para) +msgid "" +"Defines whether Easy Tier is used for the volumes created with OpenStack. " +"Details on EasyTier can be found in the Storwize family and SVC " +"documentation. The Storwize or SVC system must have Easy Tier enabled for " +"this feature to work." +msgstr "" + +#: ./doc/config-reference/block-storage/drivers/ibm-storwize-svc-driver.xml364(para) +msgid "Enable or disable Easy Tier " +msgstr "" + +#: ./doc/config-reference/block-storage/drivers/ibm-storwize-svc-driver.xml378(literal) +msgid "storwize_svc_vol_iogrp" +msgstr "" + +#: ./doc/config-reference/block-storage/drivers/ibm-storwize-svc-driver.xml382(para) +msgid "The I/O group in which to allocate vdisks" +msgstr "" + +#: ./doc/config-reference/block-storage/drivers/ibm-storwize-svc-driver.xml387(literal) +msgid "storwize_svc_flashcopy_timeout" +msgstr "" + +#: ./doc/config-reference/block-storage/drivers/ibm-storwize-svc-driver.xml391(para) +msgid "120" +msgstr "" + +#: ./doc/config-reference/block-storage/drivers/ibm-storwize-svc-driver.xml394(para) +msgid "" +"The driver wait timeout threshold when creating an OpenStack snapshot. This " +"is actually the maximum amount of time that the driver waits for the " +"Storwize family or SVC system to prepare a new FlashCopy mapping. The driver" +" accepts a maximum wait time of 600 seconds (10 minutes)." +msgstr "" + +#: ./doc/config-reference/block-storage/drivers/ibm-storwize-svc-driver.xml392(para) +msgid "FlashCopy timeout threshold (seconds)" +msgstr "" + +#: ./doc/config-reference/block-storage/drivers/ibm-storwize-svc-driver.xml408(literal) +msgid "storwize_svc_connection_protocol" +msgstr "" + +#: ./doc/config-reference/block-storage/drivers/ibm-storwize-svc-driver.xml413(para) +msgid "Connection protocol to use (currently supports 'iSCSI' or 'FC')" +msgstr "" + +#: ./doc/config-reference/block-storage/drivers/ibm-storwize-svc-driver.xml419(literal) +msgid "storwize_svc_iscsi_chap_enabled" +msgstr "" + +#: ./doc/config-reference/block-storage/drivers/ibm-storwize-svc-driver.xml424(para) +msgid "Configure CHAP authentication for iSCSI connections" +msgstr "" + +#: ./doc/config-reference/block-storage/drivers/ibm-storwize-svc-driver.xml429(literal) +msgid "storwize_svc_multipath_enabled" +msgstr "" + +#: ./doc/config-reference/block-storage/drivers/ibm-storwize-svc-driver.xml436(para) +msgid "" +"Multipath for iSCSI connections requires no storage-side configuration and " +"is enabled if the compute host has multipath configured." +msgstr "" + +#: ./doc/config-reference/block-storage/drivers/ibm-storwize-svc-driver.xml434(para) +msgid "Enable multipath for FC connections " +msgstr "" + +#: ./doc/config-reference/block-storage/drivers/ibm-storwize-svc-driver.xml445(literal) +msgid "storwize_svc_multihost_enabled" +msgstr "" + +#: ./doc/config-reference/block-storage/drivers/ibm-storwize-svc-driver.xml453(para) +msgid "" +"This option allows the driver to map a vdisk to more than one host at a " +"time. This scenario occurs during migration of a virtual machine with an " +"attached volume; the volume is simultaneously mapped to both the source and " +"destination compute hosts. If your deployment does not require attaching " +"vdisks to multiple hosts, setting this flag to False will provide added " +"safety." +msgstr "" + +#: ./doc/config-reference/block-storage/drivers/ibm-storwize-svc-driver.xml450(para) +msgid "Enable mapping vdisks to multiple hosts " +msgstr "" + +#: ./doc/config-reference/block-storage/drivers/ibm-storwize-svc-driver.xml474(title) +msgid "Placement with volume types" +msgstr "" + +#: ./doc/config-reference/block-storage/drivers/ibm-storwize-svc-driver.xml475(para) +msgid "" +"The IBM Storwize/SVC driver exposes capabilities that can be added to the " +"extra specs of volume types, and used by the filter " +"scheduler to determine placement of new volumes. Make sure to prefix these " +"keys with capabilities: to indicate that the scheduler " +"should use them. The following extra specs are supported:" +msgstr "" + +#: ./doc/config-reference/block-storage/drivers/ibm-storwize-svc-driver.xml486(para) +msgid "" +"capabilities:volume_back-end_name - Specify a specific back-end where the " +"volume should be created. The back-end name is a concatenation of the name " +"of the IBM Storwize/SVC storage system as shown in " +"lssystem, an underscore, and the name of the pool (mdisk " +"group). For example: " +msgstr "" + +#: ./doc/config-reference/block-storage/drivers/ibm-storwize-svc-driver.xml497(para) +msgid "" +"capabilities:compression_support - Specify a back-end according to " +"compression support. A value of True should be used to " +"request a back-end that supports compression, and a value of " +"False will request a back-end that does not support " +"compression. If you do not have constraints on compression support, do not " +"set this key. Note that specifying True does not enable " +"compression; it only requests that the volume be placed on a back-end that " +"supports compression. Example syntax: " +msgstr "" + +#: ./doc/config-reference/block-storage/drivers/ibm-storwize-svc-driver.xml513(para) +msgid "" +"capabilities:easytier_support - Similar semantics as the " +"compression_support key, but for specifying according to " +"support of the Easy Tier feature. Example syntax: " +msgstr "" + +#: ./doc/config-reference/block-storage/drivers/ibm-storwize-svc-driver.xml521(para) +msgid "" +"capabilities:storage_protocol - Specifies the connection protocol used to " +"attach volumes of this type to instances. Legal values are " +"iSCSI and FC. This extra " +"specs value is used for both placement and setting the protocol " +"used for this volume. In the example syntax, note <in> is used as " +"opposed to <is> used in the previous examples. " +msgstr "" + +#: ./doc/config-reference/block-storage/drivers/ibm-storwize-svc-driver.xml536(title) +msgid "Configure per-volume creation options" +msgstr "" + +#: ./doc/config-reference/block-storage/drivers/ibm-storwize-svc-driver.xml537(para) +msgid "" +"Volume types can also be used to pass options to the IBM Storwize/SVC " +"driver, which over-ride the default values set in the configuration file. " +"Contrary to the previous examples where the \"capabilities\" scope was used " +"to pass parameters to the Cinder scheduler, options can be passed to the IBM" +" Storwize/SVC driver with the \"drivers\" scope." +msgstr "" + +#: ./doc/config-reference/block-storage/drivers/ibm-storwize-svc-driver.xml547(para) +msgid "rsize" +msgstr "" + +#: ./doc/config-reference/block-storage/drivers/ibm-storwize-svc-driver.xml550(para) +msgid "warning" +msgstr "" + +#: ./doc/config-reference/block-storage/drivers/ibm-storwize-svc-driver.xml553(para) +msgid "autoexpand" +msgstr "" + +#: ./doc/config-reference/block-storage/drivers/ibm-storwize-svc-driver.xml556(para) +msgid "grainsize" +msgstr "" + +#: ./doc/config-reference/block-storage/drivers/ibm-storwize-svc-driver.xml559(para) +msgid "compression" +msgstr "" + +#: ./doc/config-reference/block-storage/drivers/ibm-storwize-svc-driver.xml562(para) +msgid "easytier" +msgstr "" + +#: ./doc/config-reference/block-storage/drivers/ibm-storwize-svc-driver.xml565(para) +msgid "multipath" +msgstr "" + +#: ./doc/config-reference/block-storage/drivers/ibm-storwize-svc-driver.xml568(para) +msgid "iogrp" +msgstr "" + +#: ./doc/config-reference/block-storage/drivers/ibm-storwize-svc-driver.xml544(para) +msgid "" +"The following extra specs keys are supported by the IBM " +"Storwize/SVC driver: These keys have the same semantics as " +"their counterparts in the configuration file. They are set similarly; for " +"example, rsize=2 or compression=False." +msgstr "" + +#: ./doc/config-reference/block-storage/drivers/ibm-storwize-svc-driver.xml576(title) +msgid "Example: Volume types" +msgstr "" + +#: ./doc/config-reference/block-storage/drivers/ibm-storwize-svc-driver.xml577(para) +msgid "" +"In the following example, we create a volume type to specify a controller " +"that supports iSCSI and compression, to use iSCSI when attaching the volume," +" and to enable compression:" +msgstr "" + +#: ./doc/config-reference/block-storage/drivers/ibm-storwize-svc-driver.xml583(para) +msgid "We can then create a 50GB volume using this type:" +msgstr "" + +#: ./doc/config-reference/block-storage/drivers/ibm-storwize-svc-driver.xml587(para) +msgid "Volume types can be used, for example, to provide users with different" +msgstr "" + +#: ./doc/config-reference/block-storage/drivers/ibm-storwize-svc-driver.xml591(para) +msgid "" +"performance levels (such as, allocating entirely on an HDD tier, using Easy " +"Tier for an HDD-SDD mix, or allocating entirely on an SSD tier)" +msgstr "" + +#: ./doc/config-reference/block-storage/drivers/ibm-storwize-svc-driver.xml597(para) +msgid "" +"resiliency levels (such as, allocating volumes in pools with different RAID " +"levels)" +msgstr "" + +#: ./doc/config-reference/block-storage/drivers/ibm-storwize-svc-driver.xml602(para) +msgid "features (such as, enabling/disabling Real-time Compression)" +msgstr "" + +#: ./doc/config-reference/block-storage/drivers/ibm-storwize-svc-driver.xml609(title) +msgid "Operational notes for the Storwize family and SVC driver" +msgstr "" + +#: ./doc/config-reference/block-storage/drivers/ibm-storwize-svc-driver.xml612(title) +msgid "Migrate volumes" +msgstr "" + +#: ./doc/config-reference/block-storage/drivers/ibm-storwize-svc-driver.xml613(para) +msgid "" +"In the context of OpenStack Block Storage's volume migration feature, the " +"IBM Storwize/SVC driver enables the storage's virtualization technology. " +"When migrating a volume from one pool to another, the volume will appear in " +"the destination pool almost immediately, while the storage moves the data in" +" the background." +msgstr "" + +#: ./doc/config-reference/block-storage/drivers/ibm-storwize-svc-driver.xml621(para) +msgid "" +"To enable this feature, both pools involved in a given volume migration must" +" have the same values for extent_size. If the pools have " +"different values for extent_size, the data will still be " +"moved directly between the pools (not host-side copy), but the operation " +"will be synchronous." +msgstr "" + +#: ./doc/config-reference/block-storage/drivers/ibm-storwize-svc-driver.xml632(title) +msgid "Extend volumes" +msgstr "" + +#: ./doc/config-reference/block-storage/drivers/ibm-storwize-svc-driver.xml633(para) +msgid "" +"The IBM Storwize/SVC driver allows for extending a volume's size, but only " +"for volumes without snapshots." +msgstr "" + +#: ./doc/config-reference/block-storage/drivers/ibm-storwize-svc-driver.xml638(title) +#: ./doc/config-reference/block-storage/drivers/ibm-gpfs-volume-driver.xml173(title) +msgid "Snapshots and clones" +msgstr "" + +#: ./doc/config-reference/block-storage/drivers/ibm-storwize-svc-driver.xml639(para) +msgid "" +"Snapshots are implemented using FlashCopy with no background copy (space-" +"efficient). Volume clones (volumes created from existing volumes) are " +"implemented with FlashCopy, but with background copy enabled. This means " +"that volume clones are independent, full copies. While this background copy " +"is taking place, attempting to delete or extend the source volume will " +"result in that operation waiting for the copy to complete." +msgstr "" + +#. When image changes, this message will be marked fuzzy or untranslated for +#. you. +#. It doesn't matter what you translate it to: it's not used at all. +#: ./doc/config-reference/block-storage/drivers/xenapi-nfs.xml62(None) +msgid "" +"@@image: '../../../common/figures/xenapinfs/local_config.png'; " +"md5=16a3864b0ec636518335246360438fd1" +msgstr "" + +#. When image changes, this message will be marked fuzzy or untranslated for +#. you. +#. It doesn't matter what you translate it to: it's not used at all. +#: ./doc/config-reference/block-storage/drivers/xenapi-nfs.xml78(None) +msgid "" +"@@image: '../../../common/figures/xenapinfs/remote_config.png'; " +"md5=eab22f6aa5413c2043936872ea44e459" +msgstr "" + +#: ./doc/config-reference/block-storage/drivers/xenapi-nfs.xml4(title) +msgid "XenAPINFS" +msgstr "" + +#: ./doc/config-reference/block-storage/drivers/xenapi-nfs.xml5(para) +msgid "" +"XenAPINFS is a Block Storage (Cinder) driver that uses an NFS share through " +"the XenAPI Storage Manager to store virtual disk images and expose those " +"virtual disks as volumes." +msgstr "" + +#: ./doc/config-reference/block-storage/drivers/xenapi-nfs.xml8(para) +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.xml17(para) +msgid "" +"A XenServer/XCP installation that acts as Storage Controller. This " +"hypervisor is known as the storage controller." +msgstr "" + +#: ./doc/config-reference/block-storage/drivers/xenapi-nfs.xml22(para) +msgid "Use XenServer/XCP as your hypervisor for Compute nodes." +msgstr "" + +#: ./doc/config-reference/block-storage/drivers/xenapi-nfs.xml26(para) +msgid "" +"An NFS share that is configured for XenServer/XCP. For specific requirements" +" and export options, see the administration guide for your specific " +"XenServer version. The NFS share must be accessible by all XenServers " +"components within your cloud." +msgstr "" + +#: ./doc/config-reference/block-storage/drivers/xenapi-nfs.xml34(para) +msgid "" +"To create volumes from XenServer type images (vhd tgz files), XenServer Nova" +" plug-ins are also required on the storage controller." +msgstr "" + +#: ./doc/config-reference/block-storage/drivers/xenapi-nfs.xml40(para) +msgid "" +"You can use a XenServer as a storage controller and Compute node at the same" +" time. This minimal configuration consists of a XenServer/XCP box and an NFS" +" share." +msgstr "" + +#: ./doc/config-reference/block-storage/drivers/xenapi-nfs.xml47(title) +msgid "Configuration patterns" +msgstr "" + +#: ./doc/config-reference/block-storage/drivers/xenapi-nfs.xml50(para) +msgid "" +"Local configuration (Recommended): The driver runs in a virtual machine on " +"top of the storage controller. With this configuration, you can create " +"volumes from qemu-img-supported formats." +msgstr "" + +#: ./doc/config-reference/block-storage/drivers/xenapi-nfs.xml57(title) +msgid "Local configuration" +msgstr "" + +#: ./doc/config-reference/block-storage/drivers/xenapi-nfs.xml68(para) +msgid "" +"Remote configuration: The driver is not a guest VM of the storage " +"controller. With this configuration, you can only use XenServer vhd-type " +"images to create volumes." +msgstr "" + +#: ./doc/config-reference/block-storage/drivers/xenapi-nfs.xml73(title) +msgid "Remote configuration" +msgstr "" + +#: ./doc/config-reference/block-storage/drivers/xenapi-nfs.xml87(para) +msgid "Assuming the following setup:" +msgstr "" + +#: ./doc/config-reference/block-storage/drivers/xenapi-nfs.xml90(para) +msgid "XenServer box at 10.2.2.1" +msgstr "" + +#: ./doc/config-reference/block-storage/drivers/xenapi-nfs.xml94(para) +msgid "XenServer password is r00tme" +msgstr "" + +#: ./doc/config-reference/block-storage/drivers/xenapi-nfs.xml98(para) +msgid "NFS server is nfs.example.com" +msgstr "" + +#: ./doc/config-reference/block-storage/drivers/xenapi-nfs.xml102(para) +msgid "NFS export is at /volumes" +msgstr "" + +#: ./doc/config-reference/block-storage/drivers/xenapi-nfs.xml106(para) +msgid "" +"To use XenAPINFS as your cinder driver, set these configuration options in " +"the cinder.conf file:" +msgstr "" + +#: ./doc/config-reference/block-storage/drivers/xenapi-nfs.xml115(para) +msgid "" +"The following table shows the configuration options that the XenAPINFS " +"driver supports:" +msgstr "" + +#: ./doc/config-reference/block-storage/drivers/hds-volume-driver.xml11(title) +msgid "HDS iSCSI volume driver" +msgstr "" + +#: ./doc/config-reference/block-storage/drivers/hds-volume-driver.xml12(para) +msgid "" +"This Cinder volume driver provides iSCSI support for HUS (Hitachi Unified Storage) arrays such " +"as, HUS-110, HUS-130, and HUS-150." +msgstr "" + +#: ./doc/config-reference/block-storage/drivers/hds-volume-driver.xml18(para) +msgid "" +"Use the HDS command to communicate with an HUS array. You " +"can download this utility package from the HDS support site (https://HDSSupport.hds.com." +msgstr "" + +#: ./doc/config-reference/block-storage/drivers/hds-volume-driver.xml23(para) +msgid "Platform: Ubuntu 12.04LTS or newer." +msgstr "" + +#: ./doc/config-reference/block-storage/drivers/hds-volume-driver.xml26(title) +msgid "Supported Cinder operations" +msgstr "" + +#: ./doc/config-reference/block-storage/drivers/hds-volume-driver.xml27(para) +msgid "These operations are supported:" +msgstr "" + +#: ./doc/config-reference/block-storage/drivers/hds-volume-driver.xml42(para) +msgid "Clone volume" +msgstr "" + +#: ./doc/config-reference/block-storage/drivers/hds-volume-driver.xml45(para) +msgid "Extend volume" +msgstr "" + +#: ./doc/config-reference/block-storage/drivers/hds-volume-driver.xml63(para) +msgid "get_volume_stats" +msgstr "" + +#: ./doc/config-reference/block-storage/drivers/hds-volume-driver.xml66(para) +msgid "" +"Thin provisioning, also known as Hitachi Dynamic Pool (HDP), is supported " +"for volume or snapshot creation. Cinder volumes and snapshots do not have to" +" reside in the same pool." +msgstr "" + +#: ./doc/config-reference/block-storage/drivers/hds-volume-driver.xml78(para) +msgid "Do not confuse differentiated services with the Cinder volume service." +msgstr "" + +#: ./doc/config-reference/block-storage/drivers/hds-volume-driver.xml73(para) +msgid "" +"The HDS driver supports the concept of differentiated services, where volume" +" type can be associated with the fine-tuned performance characteristics of " +"HDP—the the dynamic pool where volumes shall be created. For" +" instance, an HDP can consist of fast SSDs to provide speed. HDP can provide" +" a certain reliability based on things like its RAID level characteristics. " +"HDS driver maps volume type to the option in " +"its configuration file." +msgstr "" + +#: ./doc/config-reference/block-storage/drivers/hds-volume-driver.xml86(para) +msgid "" +"Configuration is read from an XML-format file. Examples are shown for single" +" and multi back-end cases." +msgstr "" + +#: ./doc/config-reference/block-storage/drivers/hds-volume-driver.xml91(para) +msgid "" +"Configuration is read from an XML file. This example shows the configuration" +" for single back-end and for multi-back-end cases." +msgstr "" + +#: ./doc/config-reference/block-storage/drivers/hds-volume-driver.xml100(para) +msgid "" +"It is okay to manage multiple HUS arrays by using multiple Cinder instances " +"(or servers)." +msgstr "" + +#: ./doc/config-reference/block-storage/drivers/hds-volume-driver.xml96(para) +msgid "" +"It is not recommended to manage a HUS array simultaneously from multiple " +"Cinder instances or servers. " +msgstr "" + +#: ./doc/config-reference/block-storage/drivers/hds-volume-driver.xml109(title) +msgid "Single back-end" +msgstr "" + +#: ./doc/config-reference/block-storage/drivers/hds-volume-driver.xml110(para) +msgid "" +"In a single back-end deployment, only one Cinder instance runs on the Cinder" +" server and controls one HUS array: this setup requires these configuration " +"files:" +msgstr "" + +#: ./doc/config-reference/block-storage/drivers/hds-volume-driver.xml123(para) +msgid "The configuration file location is not fixed." +msgstr "" + +#: ./doc/config-reference/block-storage/drivers/hds-volume-driver.xml116(para) +msgid "" +"Set the option in the " +"/etc/cinder/cinder.conf file to use the HDS volume " +"driver. This option points to a configuration file." +msgstr "" + +#: ./doc/config-reference/block-storage/drivers/hds-volume-driver.xml130(para) +msgid "" +"Configure at the location specified " +"previously. For example, " +"/opt/hds/hus/cinder_hds_conf.xml:" +msgstr "" + +#: ./doc/config-reference/block-storage/drivers/hds-volume-driver.xml160(title) +msgid "Multi back-end" +msgstr "" + +#: ./doc/config-reference/block-storage/drivers/hds-volume-driver.xml161(para) +msgid "" +"In a multi back-end deployment, more than one Cinder instance runs on the " +"same server. In this example, two HUS arrays are used, possibly providing " +"different storage performance:" +msgstr "" + +#: ./doc/config-reference/block-storage/drivers/hds-volume-driver.xml167(para) +msgid "" +"Configure /etc/cinder/cinder.conf: the " +"hus1 configuration blocks are " +"created. Set the option to point to " +"an unique configuration file for each block. Set the " +" option for each back-end to " +"cinder.volume.drivers.hds.hds.HUSDriver" +msgstr "" + +#: ./doc/config-reference/block-storage/drivers/hds-volume-driver.xml189(para) +msgid "Configure /opt/hds/hus/cinder_hus1_conf.xml:" +msgstr "" + +#: ./doc/config-reference/block-storage/drivers/hds-volume-driver.xml214(para) +msgid "" +"Configure the /opt/hds/hus/cinder_hus2_conf.xml file:" +msgstr "" + +#: ./doc/config-reference/block-storage/drivers/hds-volume-driver.xml242(title) +msgid "Type extra specs: and volume type" +msgstr "" + +#: ./doc/config-reference/block-storage/drivers/hds-volume-driver.xml244(para) +msgid "" +"If you use volume types, you must configure them in the configuration file " +"and set the option to the appropriate " +"back-end. In the previous multi back-end example, the " +"platinum volume type is served by hus-2, and the " +"regular volume type is served by hus-1." +msgstr "" + +#: ./doc/config-reference/block-storage/drivers/hds-volume-driver.xml255(title) +msgid "Non differentiated deployment of HUS arrays" +msgstr "" + +#: ./doc/config-reference/block-storage/drivers/hds-volume-driver.xml256(para) +msgid "" +"You can deploy multiple Cinder instances that each control a separate HUS " +"array. Each instance has no volume type associated with it. The Cinder " +"filtering algorithm selects the HUS array with the largest available free " +"space. In each configuration file, you must define the " +"default in the service " +"labels." +msgstr "" + +#: ./doc/config-reference/block-storage/drivers/hds-volume-driver.xml267(title) +msgid "HDS iSCSI volume driver configuration options" +msgstr "" + +#: ./doc/config-reference/block-storage/drivers/hds-volume-driver.xml274(para) +msgid "There is no relative precedence or weight among these four labels." +msgstr "" + +#: ./doc/config-reference/block-storage/drivers/hds-volume-driver.xml268(para) +msgid "" +"These details apply to the XML format configuration file that is read by HDS" +" volume driver. These differentiated service labels are predefined: " +"svc_0, svc_1, " +"svc_2, and svc_3. Each" +" respective service label associates with these parameters and tags:" +msgstr "" + +#: ./doc/config-reference/block-storage/drivers/hds-volume-driver.xml280(para) +msgid "" +": A create_volume call with a certain volume " +"type shall be matched up with this tag. default is " +"special in that any service associated with this type is used to create " +"volume when no other labels match. Other labels are case sensitive and " +"should exactly match. If no configured volume_types match the incoming " +"requested type, an error occurs in volume creation." +msgstr "" + +#: ./doc/config-reference/block-storage/drivers/hds-volume-driver.xml291(para) +msgid ", the pool ID associated with the service." +msgstr "" + +#: ./doc/config-reference/block-storage/drivers/hds-volume-driver.xml295(para) +msgid "An iSCSI port dedicated to the service." +msgstr "" + +#: ./doc/config-reference/block-storage/drivers/hds-volume-driver.xml304(para) +msgid "" +"get_volume_stats() always provides the available capacity based on the " +"combined sum of all the HDPs that are used in these services labels." +msgstr "" + +#: ./doc/config-reference/block-storage/drivers/hds-volume-driver.xml298(para) +msgid "" +"Typically a Cinder volume instance has only one such service label. For " +"example, any svc_0, svc_1, " +"svc_2, or svc_3 can be associated with" +" it. But any mix of these service labels can be used in the same instance " +"." +msgstr "" + +#: ./doc/config-reference/block-storage/drivers/hds-volume-driver.xml316(td) +msgid "Option" +msgstr "" + +#: ./doc/config-reference/block-storage/drivers/hds-volume-driver.xml324(option) +msgid "mgmt_ip0" +msgstr "" + +#: ./doc/config-reference/block-storage/drivers/hds-volume-driver.xml328(para) +msgid "Management Port 0 IP address" +msgstr "" + +#: ./doc/config-reference/block-storage/drivers/hds-volume-driver.xml332(option) +msgid "mgmt_ip1" +msgstr "" + +#: ./doc/config-reference/block-storage/drivers/hds-volume-driver.xml336(para) +msgid "Management Port 1 IP address" +msgstr "" + +#: ./doc/config-reference/block-storage/drivers/hds-volume-driver.xml345(para) +msgid "Username is required only if secure mode is used" +msgstr "" + +#: ./doc/config-reference/block-storage/drivers/hds-volume-driver.xml355(para) +msgid "Password is required only if secure mode is used" +msgstr "" + +#: ./doc/config-reference/block-storage/drivers/hds-volume-driver.xml361(option) +msgid "svc_0, svc_1, svc_2, svc_3" +msgstr "" + +#: ./doc/config-reference/block-storage/drivers/hds-volume-driver.xml365(para) +msgid "(at least one label has to be defined)" +msgstr "" + +#: ./doc/config-reference/block-storage/drivers/hds-volume-driver.xml368(para) +msgid "" +"Service labels: these four predefined names help four different sets of " +"configuration options -- each can specify iSCSI port address, HDP and an " +"unique volume type." +msgstr "" + +#: ./doc/config-reference/block-storage/drivers/hds-volume-driver.xml377(option) +msgid "snapshot" +msgstr "" + +#: ./doc/config-reference/block-storage/drivers/hds-volume-driver.xml382(para) +msgid "" +"A service label which helps specify configuration for snapshots, such as, " +"HDP." +msgstr "" + +#: ./doc/config-reference/block-storage/drivers/hds-volume-driver.xml389(option) +msgid "volume_type" +msgstr "" + +#: ./doc/config-reference/block-storage/drivers/hds-volume-driver.xml394(para) +msgid "" +" tag is used to match volume type. " +"Default meets any type of , " +"or if it is not specified. Any other volume_type is selected if exactly " +"matched during create_volume." +msgstr "" + +#: ./doc/config-reference/block-storage/drivers/hds-volume-driver.xml406(option) +msgid "iscsi_ip" +msgstr "" + +#: ./doc/config-reference/block-storage/drivers/hds-volume-driver.xml411(para) +msgid "iSCSI port IP address where volume attaches for this volume type." +msgstr "" + +#: ./doc/config-reference/block-storage/drivers/hds-volume-driver.xml417(option) +msgid "hdp" +msgstr "" + +#: ./doc/config-reference/block-storage/drivers/hds-volume-driver.xml422(para) +msgid "HDP, the pool number where volume, or snapshot should be created." +msgstr "" + +#: ./doc/config-reference/block-storage/drivers/hds-volume-driver.xml428(option) +msgid "lun_start" +msgstr "" + +#: ./doc/config-reference/block-storage/drivers/hds-volume-driver.xml433(para) +msgid "LUN allocation starts at this number." +msgstr "" + +#: ./doc/config-reference/block-storage/drivers/hds-volume-driver.xml439(option) +msgid "lun_end" +msgstr "" + +#: ./doc/config-reference/block-storage/drivers/hds-volume-driver.xml442(para) +msgid "4096" +msgstr "" + +#: ./doc/config-reference/block-storage/drivers/hds-volume-driver.xml444(para) +msgid "LUN allocation is up to, but not including, this number." +msgstr "" + +#. When image changes, this message will be marked fuzzy or untranslated for +#. you. +#. It doesn't matter what you translate it to: it's not used at all. +#: ./doc/config-reference/block-storage/drivers/ceph-rbd-volume-driver.xml26(None) +msgid "" +"@@image: '../../../common/figures/ceph/ceph-architecture.png'; " +"md5=f7e854c9dbfb64534c47c3583e774c81" +msgstr "" + +#: ./doc/config-reference/block-storage/drivers/ceph-rbd-volume-driver.xml4(title) +msgid "Ceph RADOS Block Device (RBD)" +msgstr "" + +#: ./doc/config-reference/block-storage/drivers/ceph-rbd-volume-driver.xml5(para) +msgid "" +"By Sebastien Han from " +msgstr "" + +#: ./doc/config-reference/block-storage/drivers/ceph-rbd-volume-driver.xml8(para) +msgid "" +"If you use KVM or QEMU as your hypervisor, you can configure the Compute " +"service to use " +"Ceph RADOS block devices (RBD) for volumes." +msgstr "" + +#: ./doc/config-reference/block-storage/drivers/ceph-rbd-volume-driver.xml21(title) +msgid "Ceph architecture" +msgstr "" + +#: ./doc/config-reference/block-storage/drivers/ceph-rbd-volume-driver.xml12(para) +msgid "" +"Ceph is a massively scalable, open source, distributed storage system. It is" +" comprised of an object store, block store, and a POSIX-compliant " +"distributed file system. The platform can auto-scale to the exabyte level " +"and beyond. It runs on commodity hardware, is self-healing and self-" +"managing, and has no single point of failure. Ceph is in the Linux kernel " +"and is integrated with the OpenStack cloud operating system. Due to its open" +" source nature, you can install and use this portable storage platform in " +"public or private clouds. " +msgstr "" + +#: ./doc/config-reference/block-storage/drivers/ceph-rbd-volume-driver.xml32(title) +msgid "RADOS?" +msgstr "" + +#: ./doc/config-reference/block-storage/drivers/ceph-rbd-volume-driver.xml33(para) +msgid "You can easily get confused by the naming: Ceph? RADOS?" +msgstr "" + +#: ./doc/config-reference/block-storage/drivers/ceph-rbd-volume-driver.xml35(para) +msgid "" +"RADOS: Reliable Autonomic Distributed Object Store is " +"an object store. RADOS distributes objects across the storage cluster and " +"replicates objects for fault tolerance. RADOS contains the following major " +"components:" +msgstr "" + +#: ./doc/config-reference/block-storage/drivers/ceph-rbd-volume-driver.xml42(para) +msgid "" +"Object Storage Device (ODS). The storage daemon - RADOS" +" service, the location of your data. You must run this daemon on each server" +" in your cluster. For each OSD, you can have an associated hard drive disks." +" For performance purposes, pool your hard drive disk with raid arrays, " +"logical volume management (LVM) or B-tree file system (Btrfs) pooling. By " +"default, the following pools are created: data, metadata, and RBD." +msgstr "" + +#: ./doc/config-reference/block-storage/drivers/ceph-rbd-volume-driver.xml54(para) +msgid "" +"Meta-Data Server (MDS). Stores metadata. MDSs build a " +"POSIX file system on top of objects for Ceph clients. However, if you do not" +" use the Ceph file system, you do not need a metadata server." +msgstr "" + +#: ./doc/config-reference/block-storage/drivers/ceph-rbd-volume-driver.xml61(para) +msgid "" +"Monitor (MON). This lightweight daemon handles all " +"communications with external applications and clients. It also provides a " +"consensus for distributed decision making in a Ceph/RADOS cluster. For " +"instance, when you mount a Ceph shared on a client, you point to the address" +" of a MON server. It checks the state and the consistency of the data. In an" +" ideal setup, you must run at least three ceph-mon daemons on " +"separate servers." +msgstr "" + +#: ./doc/config-reference/block-storage/drivers/ceph-rbd-volume-driver.xml74(para) +msgid "" +"Ceph developers recommend that you use Btrfs as a file system for storage. " +"XFS might be a better alternative for production environments. Neither Ceph " +"nor Btrfs is ready for production and it could be risky to use them in " +"combination. XFS is an excellent alternative to Btrfs. The ext4 file system " +"is also compatible but does not exploit the power of Ceph." +msgstr "" + +#: ./doc/config-reference/block-storage/drivers/ceph-rbd-volume-driver.xml82(para) +msgid "" +"Currently, configure Ceph to use the XFS file system. Use Btrfs when it is " +"stable enough for production." +msgstr "" + +#: ./doc/config-reference/block-storage/drivers/ceph-rbd-volume-driver.xml86(para) +msgid "" +"See ceph.com/docs/master/rec/file" +" system/ for more information about usable file systems." +msgstr "" + +#: ./doc/config-reference/block-storage/drivers/ceph-rbd-volume-driver.xml92(title) +msgid "Ways to store, use, and expose data" +msgstr "" + +#: ./doc/config-reference/block-storage/drivers/ceph-rbd-volume-driver.xml93(para) +msgid "" +"To store and access your data, you can use the following storage systems:" +msgstr "" + +#: ./doc/config-reference/block-storage/drivers/ceph-rbd-volume-driver.xml97(para) +msgid "" +"RADOS. Use as an object, default storage mechanism." +msgstr "" + +#: ./doc/config-reference/block-storage/drivers/ceph-rbd-volume-driver.xml101(para) +msgid "" +"RBD. Use as a block device. The Linux kernel RBD (rados" +" block device) driver allows striping a Linux block device over multiple " +"distributed object store data objects. It is compatible with the kvm RBD " +"image." +msgstr "" + +#: ./doc/config-reference/block-storage/drivers/ceph-rbd-volume-driver.xml108(para) +msgid "" +"CephFS. Use as a file, POSIX-compliant file system." +msgstr "" + +#: ./doc/config-reference/block-storage/drivers/ceph-rbd-volume-driver.xml112(para) +msgid "" +"Ceph exposes its distributed object store (RADOS). You can access it through" +" the following interfaces:" +msgstr "" + +#: ./doc/config-reference/block-storage/drivers/ceph-rbd-volume-driver.xml116(para) +msgid "" +"RADOS Gateway. Swift and Amazon-S3 compatible RESTful " +"interface. See RADOS_Gateway for more " +"information." +msgstr "" + +#: ./doc/config-reference/block-storage/drivers/ceph-rbd-volume-driver.xml123(para) +msgid "librados, and the related C/C++ bindings." +msgstr "" + +#: ./doc/config-reference/block-storage/drivers/ceph-rbd-volume-driver.xml127(para) +msgid "" +"rbd and QEMU-RBD. Linux kernel and QEMU block devices " +"that stripe data across multiple objects." +msgstr "" + +#: ./doc/config-reference/block-storage/drivers/ceph-rbd-volume-driver.xml132(para) +msgid "" +"For detailed installation instructions and benchmarking information, see " +"http://www.sebastien-han.fr/blog/2012/06/10/introducing-" +"ceph-to-openstack/." +msgstr "" + +#: ./doc/config-reference/block-storage/drivers/ceph-rbd-volume-driver.xml138(title) +msgid "Driver options" +msgstr "" + +#: ./doc/config-reference/block-storage/drivers/ceph-rbd-volume-driver.xml139(para) +msgid "" +"The following table contains the configuration options supported by the Ceph" +" RADOS Block Device driver." +msgstr "" + +#: ./doc/config-reference/block-storage/drivers/hp-lefthand-driver.xml4(title) +msgid "HP / LeftHand SAN" +msgstr "" + +#: ./doc/config-reference/block-storage/drivers/hp-lefthand-driver.xml5(para) +msgid "" +"HP/LeftHand SANs are optimized for virtualized environments with VMware ESX " +"& Microsoft Hyper-V, though the OpenStack integration provides " +"additional support to various other virtualized environments, such as Xen, " +"KVM, and OpenVZ, by exposing the volumes through ISCSI to connect to the " +"instances." +msgstr "" + +#: ./doc/config-reference/block-storage/drivers/hp-lefthand-driver.xml11(para) +msgid "" +"The HpSanISCSIDriver enables you to use a HP/Lefthand SAN that supports the " +"Cliq interface. Every supported volume operation translates into a cliq call" +" in the back-end." +msgstr "" + +#: ./doc/config-reference/block-storage/drivers/hp-lefthand-driver.xml14(para) +msgid "" +"To use Cinder with HP/Lefthand SAN, you must set the following parameters in" +" the cinder.conf file:" +msgstr "" + +#: ./doc/config-reference/block-storage/drivers/hp-lefthand-driver.xml19(para) +msgid "" +"Set " +"volume_driver=cinder.volume.drivers.san.HpSanISCSIDriver." +msgstr "" + +#: ./doc/config-reference/block-storage/drivers/hp-lefthand-driver.xml23(para) +msgid "" +"Set san_ip flag to the hostname or VIP of your " +"Virtual Storage Appliance (VSA)." +msgstr "" + +#: ./doc/config-reference/block-storage/drivers/hp-lefthand-driver.xml28(para) +msgid "" +"Set san_login and san_password" +" to the user name and password of the ssh user with all necessary privileges" +" on the appliance." +msgstr "" + +#: ./doc/config-reference/block-storage/drivers/hp-lefthand-driver.xml34(para) +msgid "" +"Set san_ssh_port=16022. The default is 22. However, the default" +" for the VSA is usually 16022." +msgstr "" + +#: ./doc/config-reference/block-storage/drivers/hp-lefthand-driver.xml39(para) +msgid "" +"Set san_clustername to the name of the cluster where the " +"associated volumes are created." +msgstr "" + +#: ./doc/config-reference/block-storage/drivers/hp-lefthand-driver.xml44(para) +msgid "The following optional parameters have the following default values:" +msgstr "" + +#: ./doc/config-reference/block-storage/drivers/hp-lefthand-driver.xml48(para) +msgid "" +"san_thin_provision=True. To disable thin provisioning, set to " +"False." +msgstr "" + +#: ./doc/config-reference/block-storage/drivers/hp-lefthand-driver.xml53(para) +msgid "" +"san_is_local=False. Typically, this parameter is set to " +"False for this driver. To configure the cliq commands to " +"run locally instead of over ssh, set this parameter to " +"True." +msgstr "" + +#: ./doc/config-reference/block-storage/drivers/hp-lefthand-driver.xml60(para) +msgid "" +"In addition to configuring the cinder-" +"volume service, you must configure the VSA to function in an " +"OpenStack environment." +msgstr "" + +#: ./doc/config-reference/block-storage/drivers/hp-lefthand-driver.xml64(title) +msgid "To configure the VSA" +msgstr "" + +#: ./doc/config-reference/block-storage/drivers/hp-lefthand-driver.xml66(para) +msgid "" +"Configure Chap on each of the nova-" +"compute nodes." +msgstr "" + +#: ./doc/config-reference/block-storage/drivers/hp-lefthand-driver.xml71(para) +msgid "" +"Add Server associations on the VSA with the associated Chap and initiator " +"information. The name should correspond to the 'hostname' of the nova-compute node. For Xen, this is the hypervisor host " +"name. To do this, use either Cliq or the Centralized Management Console." +msgstr "" + +#: ./doc/config-reference/block-storage/drivers/windows-volume-driver.xml6(title) +msgid "Windows" +msgstr "" + +#: ./doc/config-reference/block-storage/drivers/windows-volume-driver.xml7(para) +msgid "" +"There is a volume back-end for Windows. Set the following in your " +"cinder.conf, and use the options below to configure it." +msgstr "" + +#: ./doc/config-reference/block-storage/drivers/lvm-volume-driver.xml6(title) +msgid "LVM" +msgstr "" + +#: ./doc/config-reference/block-storage/drivers/lvm-volume-driver.xml7(para) +msgid "The default volume back-end uses local volumes managed by LVM." +msgstr "" + +#: ./doc/config-reference/block-storage/drivers/lvm-volume-driver.xml8(para) +msgid "" +"This driver supports different transport protocols to attach volumes, " +"currently ISCSI and ISER." +msgstr "" + +#: ./doc/config-reference/block-storage/drivers/lvm-volume-driver.xml10(para) +msgid "" +"Set the following in your cinder.conf, and use the " +"following options to configure for ISCSI transport:" +msgstr "" + +#: ./doc/config-reference/block-storage/drivers/lvm-volume-driver.xml16(para) +msgid "and for the ISER transport:" +msgstr "" + +#: ./doc/config-reference/block-storage/drivers/nfs-volume-driver.xml4(title) +msgid "NFS driver" +msgstr "" + +#: ./doc/config-reference/block-storage/drivers/nfs-volume-driver.xml5(para) +msgid "" +"The Network File System (NFS) is a distributed file system protocol " +"originally developed by Sun Microsystems in 1984. An NFS server " +"exports one or more of its file systems, known as " +"shares. An NFS client can mount these exported shares " +"on its own file system. You can perform file actions on this mounted remote " +"file system as if the file system were local." +msgstr "" + +#: ./doc/config-reference/block-storage/drivers/nfs-volume-driver.xml13(title) +msgid "How the NFS driver works" +msgstr "" + +#: ./doc/config-reference/block-storage/drivers/nfs-volume-driver.xml14(para) +msgid "" +"The NFS driver, and other drivers based off of it, work quite differently " +"than a traditional block storage driver." +msgstr "" + +#: ./doc/config-reference/block-storage/drivers/nfs-volume-driver.xml17(para) +msgid "" +"The NFS driver does not actually allow an instance to access a storage " +"device at the block level. Instead, files are created on an NFS share and " +"mapped to instances, which emulates a block device. This works in a similar " +"way to QEMU, which stores instances in the " +"/var/lib/nova/instances directory." +msgstr "" + +#: ./doc/config-reference/block-storage/drivers/nfs-volume-driver.xml26(title) +msgid "Enable the NFS driver and related options" +msgstr "" + +#: ./doc/config-reference/block-storage/drivers/nfs-volume-driver.xml27(para) +msgid "" +"To use Cinder with the NFS driver, first set the " +"volume_driver in cinder.conf:" +msgstr "" + +#: ./doc/config-reference/block-storage/drivers/nfs-volume-driver.xml31(para) +msgid "The following table contains the options supported by the NFS driver." +msgstr "" + +#: ./doc/config-reference/block-storage/drivers/nfs-volume-driver.xml37(title) +msgid "How to use the NFS driver" +msgstr "" + +#: ./doc/config-reference/block-storage/drivers/nfs-volume-driver.xml40(para) +msgid "" +"Access to one or more NFS servers. Creating an NFS server is outside the " +"scope of this document. This example assumes access to the following NFS " +"servers and mount points:" +msgstr "" + +#: ./doc/config-reference/block-storage/drivers/nfs-volume-driver.xml46(literal) +msgid "192.168.1.200:/storage" +msgstr "" + +#: ./doc/config-reference/block-storage/drivers/nfs-volume-driver.xml49(literal) +msgid "192.168.1.201:/storage" +msgstr "" + +#: ./doc/config-reference/block-storage/drivers/nfs-volume-driver.xml52(literal) +msgid "192.168.1.202:/storage" +msgstr "" + +#: ./doc/config-reference/block-storage/drivers/nfs-volume-driver.xml55(para) +msgid "" +"This example demonstrates the use of with this driver with multiple NFS " +"servers. Multiple servers are not required. One is usually enough." +msgstr "" + +#: ./doc/config-reference/block-storage/drivers/nfs-volume-driver.xml60(para) +msgid "" +"Add your list of NFS servers to the file you specified with the " +"nfs_shares_config option. For example, if the value of " +"this option was set to /etc/cinder/shares.txt, then:" +msgstr "" + +#: ./doc/config-reference/block-storage/drivers/nfs-volume-driver.xml70(para) +msgid "" +"Comments are allowed in this file. They begin with a #." +msgstr "" + +#: ./doc/config-reference/block-storage/drivers/nfs-volume-driver.xml74(para) +msgid "" +"Configure the nfs_mount_point_base option. This is a " +"directory where cinder-volume " +"mounts all NFS shares stored in shares.txt. For this " +"example, /var/lib/cinder/nfs is used. You can, of course," +" use the default value of $state_path/mnt." +msgstr "" + +#: ./doc/config-reference/block-storage/drivers/nfs-volume-driver.xml85(para) +msgid "" +"Start the cinder-volume service. " +"/var/lib/cinder/nfs should now contain a directory for " +"each NFS share specified in shares.txt. The name of each " +"directory is a hashed name:" +msgstr "" + +#: ./doc/config-reference/block-storage/drivers/nfs-volume-driver.xml97(para) +msgid "You can now create volumes as you normally would:" +msgstr "" + +#: ./doc/config-reference/block-storage/drivers/nfs-volume-driver.xml102(para) +msgid "" +"This volume can also be attached and deleted just like other volumes. " +"However, snapshotting is not supported." +msgstr "" + +#: ./doc/config-reference/block-storage/drivers/nfs-volume-driver.xml109(title) +msgid "NFS driver notes" +msgstr "" + +#: ./doc/config-reference/block-storage/drivers/nfs-volume-driver.xml112(para) +msgid "" +"cinder-volume manages the " +"mounting of the NFS shares as well as volume creation on the shares. Keep " +"this in mind when planning your OpenStack architecture. If you have one " +"master NFS server, it might make sense to only have one cinder-volume service to handle all requests " +"to that NFS server. However, if that single server is unable to handle all " +"requests, more than one cinder-" +"volume service is needed as well as potentially more than one " +"NFS server." +msgstr "" + +#: ./doc/config-reference/block-storage/drivers/nfs-volume-driver.xml128(para) +msgid "" +"Because data is stored in a file and not actually on a block storage device," +" you might not see the same IO performance as you would with a traditional " +"block storage driver. Please test accordingly." +msgstr "" + +#: ./doc/config-reference/block-storage/drivers/nfs-volume-driver.xml135(para) +msgid "" +"Despite possible IO performance loss, having volume data stored in a file " +"might be beneficial. For example, backing up volumes can be as easy as " +"copying the volume files." +msgstr "" + +#: ./doc/config-reference/block-storage/drivers/nfs-volume-driver.xml140(para) +msgid "Regular IO flushing and syncing still stands." +msgstr "" + +#: ./doc/config-reference/block-storage/drivers/ibm-gpfs-volume-driver.xml4(title) +msgid "IBM GPFS volume driver" +msgstr "" + +#: ./doc/config-reference/block-storage/drivers/ibm-gpfs-volume-driver.xml5(para) +msgid "" +"IBM General Parallel File System (GPFS) is a cluster file system that " +"provides concurrent access to file systems from multiple nodes. The storage " +"provided by these nodes can be direct attached, network attached, SAN " +"attached, or a combination of these methods. GPFS provides many features " +"beyond common data access, including data replication, policy based storage " +"management, and space efficient file snapshot and clone operations." +msgstr "" + +#: ./doc/config-reference/block-storage/drivers/ibm-gpfs-volume-driver.xml14(title) +msgid "How the GPFS driver works" +msgstr "" + +#: ./doc/config-reference/block-storage/drivers/ibm-gpfs-volume-driver.xml15(para) +msgid "" +"The GPFS driver enables the use of GPFS in a fashion similar to that of the " +"NFS driver. With the GPFS driver, instances do not actually access a storage" +" device at the block level. Instead, volume backing files are created in a " +"GPFS file system and mapped to instances, which emulate a block device." +msgstr "" + +#: ./doc/config-reference/block-storage/drivers/ibm-gpfs-volume-driver.xml23(para) +msgid "" +"GPFS software must be installed and running on nodes where Block Storage and" +" Compute services run in the OpenStack environment. A GPFS file system must " +"also be created and mounted on these nodes before starting the cinder-volume service. The details of these GPFS specific steps " +"are covered in GPFS: Concepts, Planning, and Installation " +"Guide and GPFS: Administration and Programming " +"Reference." +msgstr "" + +#: ./doc/config-reference/block-storage/drivers/ibm-gpfs-volume-driver.xml35(para) +msgid "" +"Optionally, the Image Service can be configured to store images on a GPFS " +"file system. When a Block Storage volume is created from an image, if both " +"image data and volume data reside in the same GPFS file system, the data " +"from image file is moved efficiently to the volume file using copy-on-write " +"optimization strategy." +msgstr "" + +#: ./doc/config-reference/block-storage/drivers/ibm-gpfs-volume-driver.xml43(title) +msgid "Enable the GPFS driver" +msgstr "" + +#: ./doc/config-reference/block-storage/drivers/ibm-gpfs-volume-driver.xml44(para) +msgid "" +"To use the Block Storage Service with the GPFS driver, first set the " +"volume_driver in cinder.conf:" +msgstr "" + +#: ./doc/config-reference/block-storage/drivers/ibm-gpfs-volume-driver.xml48(para) +msgid "" +"The following table contains the configuration options supported by the GPFS" +" driver." +msgstr "" + +#: ./doc/config-reference/block-storage/drivers/ibm-gpfs-volume-driver.xml53(para) +msgid "" +"The gpfs_images_share_mode flag is only valid if the " +"Image Service is configured to use GPFS with the " +"gpfs_images_dir flag. When the value of this flag is " +"copy_on_write, the paths specified by the " +"gpfs_mount_point_base and " +"gpfs_images_dir flags must both reside in the same GPFS " +"file system and in the same GPFS file set." +msgstr "" + +#: ./doc/config-reference/block-storage/drivers/ibm-gpfs-volume-driver.xml66(title) +msgid "Volume creation options" +msgstr "" + +#: ./doc/config-reference/block-storage/drivers/ibm-gpfs-volume-driver.xml67(para) +msgid "" +"It is possible to specify additional volume configuration options on a per-" +"volume basis by specifying volume metadata. The volume is created using the " +"specified options. Changing the metadata after the volume is created has no " +"effect. The following table lists the volume creation options supported by " +"the GPFS volume driver." +msgstr "" + +#: ./doc/config-reference/block-storage/drivers/ibm-gpfs-volume-driver.xml75(caption) +msgid "Volume Create Options for GPFS Volume Drive" +msgstr "" + +#: ./doc/config-reference/block-storage/drivers/ibm-gpfs-volume-driver.xml79(th) +msgid "Metadata Item Name" +msgstr "" + +#: ./doc/config-reference/block-storage/drivers/ibm-gpfs-volume-driver.xml85(literal) +#: ./doc/config-reference/block-storage/drivers/ibm-gpfs-volume-driver.xml98(literal) +#: ./doc/config-reference/block-storage/drivers/ibm-gpfs-volume-driver.xml99(literal) +msgid "fstype" +msgstr "" + +#: ./doc/config-reference/block-storage/drivers/ibm-gpfs-volume-driver.xml88(literal) +msgid "fstype=swap" +msgstr "" + +#: ./doc/config-reference/block-storage/drivers/ibm-gpfs-volume-driver.xml86(td) +msgid "" +"Specifies whether to create a file system or a swap area on the new volume. " +"If is specified, the mkswap command is used to create a " +"swap area. Otherwise the mkfs command is passed the specified file system " +"type, for example ext3, ext4 or ntfs." +msgstr "" + +#: ./doc/config-reference/block-storage/drivers/ibm-gpfs-volume-driver.xml96(literal) +msgid "fslabel" +msgstr "" + +#: ./doc/config-reference/block-storage/drivers/ibm-gpfs-volume-driver.xml97(td) +msgid "" +"Sets the file system label for the file system specified by " +" option. This value is only used if is specified." +msgstr "" + +#: ./doc/config-reference/block-storage/drivers/ibm-gpfs-volume-driver.xml103(literal) +msgid "data_pool_name" +msgstr "" + +#: ./doc/config-reference/block-storage/drivers/ibm-gpfs-volume-driver.xml105(para) +msgid "" +"Specifies the GPFS storage pool to which the volume is to be assigned. Note:" +" The GPFS storage pool must already have been created." +msgstr "" + +#: ./doc/config-reference/block-storage/drivers/ibm-gpfs-volume-driver.xml111(literal) +msgid "replicas" +msgstr "" + +#: ./doc/config-reference/block-storage/drivers/ibm-gpfs-volume-driver.xml113(para) +msgid "" +"Specifies how many copies of the volume file to create. Valid values are 1, " +"2, and, for GPFS V3.5.0.7 and later, 3. This value cannot be greater than " +"the value of the MaxDataReplicas attribute of the file " +"system." +msgstr "" + +#: ./doc/config-reference/block-storage/drivers/ibm-gpfs-volume-driver.xml122(literal) +msgid "dio" +msgstr "" + +#: ./doc/config-reference/block-storage/drivers/ibm-gpfs-volume-driver.xml124(para) +msgid "" +"Enables or disables the Direct I/O caching policy for the volume file. Valid" +" values are yes and no." +msgstr "" + +#: ./doc/config-reference/block-storage/drivers/ibm-gpfs-volume-driver.xml130(literal) +msgid "write_affinity_depth" +msgstr "" + +#: ./doc/config-reference/block-storage/drivers/ibm-gpfs-volume-driver.xml132(para) +msgid "" +"Specifies the allocation policy to be used for the volume file. Note: This " +"option only works if allow-write-affinity is set for the " +"GPFS data pool." +msgstr "" + +#: ./doc/config-reference/block-storage/drivers/ibm-gpfs-volume-driver.xml139(literal) +msgid "block_group_factor" +msgstr "" + +#: ./doc/config-reference/block-storage/drivers/ibm-gpfs-volume-driver.xml141(para) +msgid "" +"Specifies how many blocks are laid out sequentially in the volume file to " +"behave as a single large block. Note: This option only works if allow-write-affinity is set for the GPFS data pool." +msgstr "" + +#: ./doc/config-reference/block-storage/drivers/ibm-gpfs-volume-driver.xml149(literal) +msgid "write_affinity_failure_group" +msgstr "" + +#: ./doc/config-reference/block-storage/drivers/ibm-gpfs-volume-driver.xml151(para) +msgid "" +"Specifies the range of nodes (in GPFS shared nothing architecture) where " +"replicas of blocks in the volume file are to be written. See " +"GPFS: Administration and Programming Reference for " +"more details on this option." +msgstr "" + +#: ./doc/config-reference/block-storage/drivers/ibm-gpfs-volume-driver.xml162(title) +msgid "Example: Volume creation options" +msgstr "" + +#: ./doc/config-reference/block-storage/drivers/ibm-gpfs-volume-driver.xml163(para) +msgid "" +"This example shows the creation of a 50GB volume with an ext4 file system " +"labeled newfsand direct IO enabled:" +msgstr "" + +#: ./doc/config-reference/block-storage/drivers/ibm-gpfs-volume-driver.xml171(title) +msgid "Operational notes for GPFS driver" +msgstr "" + +#: ./doc/config-reference/block-storage/drivers/ibm-gpfs-volume-driver.xml174(para) +msgid "" +"Volume snapshots are implemented using the GPFS file clone feature. Whenever" +" a new snapshot is created, the snapshot file is efficiently created as a " +"read-only clone parent of the volume, and the volume file uses copy-on-write" +" optimization strategy to minimize data movement." +msgstr "" + +#: ./doc/config-reference/block-storage/drivers/ibm-gpfs-volume-driver.xml180(para) +msgid "" +"Similarly when a new volume is created from a snapshot or from an existing " +"volume, the same approach is taken. The same approach is also used when a " +"new volume is created from a Glance image, if the source image is in raw " +"format, and gpfs_images_share_mode is set to " +"copy_on_write." +msgstr "" + +#: ./doc/config-reference/block-storage/backup/tsm-backup-driver.xml6(title) +msgid "IBM Tivoli Storage Manager backup driver" +msgstr "" + +#: ./doc/config-reference/block-storage/backup/tsm-backup-driver.xml7(para) +msgid "" +"The IBM Tivoli Storage Manager (TSM) backup driver enables performing volume" +" backups to a TSM server." +msgstr "" + +#: ./doc/config-reference/block-storage/backup/tsm-backup-driver.xml10(para) +msgid "" +"The TSM client should be installed and configured on the machine running the" +" cinder-backup service. See the " +"IBM Tivoli Storage Manager Backup-Archive Client Installation and" +" User's Guide for details on installing the TSM client." +msgstr "" + +#: ./doc/config-reference/block-storage/backup/tsm-backup-driver.xml17(para) +msgid "" +"To enable the IBM TSM backup driver, include the following option in " +"cinder.conf:" +msgstr "" + +#: ./doc/config-reference/block-storage/backup/tsm-backup-driver.xml20(para) +msgid "" +"The following configuration options are available for the TSM backup driver." +msgstr "" + +#: ./doc/config-reference/block-storage/backup/tsm-backup-driver.xml23(para) +msgid "This example shows the default options for the TSM backup driver." +msgstr "" + +#: ./doc/config-reference/block-storage/backup/ceph-backup-driver.xml11(title) +msgid "Ceph backup driver" +msgstr "" + +#: ./doc/config-reference/block-storage/backup/ceph-backup-driver.xml12(para) +msgid "" +"The Ceph backup driver backs up volumes of any type to a Ceph back-end " +"store. The driver can also detect whether the volume to be backed up is a " +"Ceph RBD volume, and if so, it tries to perform incremental and differential" +" backups." +msgstr "" + +#: ./doc/config-reference/block-storage/backup/ceph-backup-driver.xml17(para) +msgid "" +"For source Ceph RBD volumes, you can perform backups within the same Ceph " +"pool (not recommended) and backups between different Ceph pools and between " +"different Ceph clusters." +msgstr "" + +#: ./doc/config-reference/block-storage/backup/ceph-backup-driver.xml21(para) +msgid "" +"At the time of writing, differential backup support in Ceph/librbd was quite" +" new. This driver attempts a differential backup in the first instance. If " +"the differential backup fails, the driver falls back to full backup/copy." +msgstr "" + +#: ./doc/config-reference/block-storage/backup/ceph-backup-driver.xml26(para) +msgid "" +"If incremental backups are used, multiple backups of the same volume are " +"stored as snapshots so that minimal space is consumed in the backup store. " +"It takes far less time to restore a volume than to take a full copy." +msgstr "" + +#: ./doc/config-reference/block-storage/backup/ceph-backup-driver.xml32(para) +msgid "Block Storage Service enables you to:" +msgstr "" + +#: ./doc/config-reference/block-storage/backup/ceph-backup-driver.xml35(para) +msgid "Restore to a new volume, which is the default and recommended action." +msgstr "" + +#: ./doc/config-reference/block-storage/backup/ceph-backup-driver.xml40(para) +msgid "" +"Restore to the original volume from which the backup was taken. The restore " +"action takes a full copy because this is the safest action." +msgstr "" + +#: ./doc/config-reference/block-storage/backup/ceph-backup-driver.xml48(para) +msgid "" +"To enable the Ceph backup driver, include the following option in the " +"cinder.conf file:" +msgstr "" + +#: ./doc/config-reference/block-storage/backup/ceph-backup-driver.xml52(para) +msgid "" +"The following configuration options are available for the Ceph backup " +"driver." +msgstr "" + +#: ./doc/config-reference/block-storage/backup/ceph-backup-driver.xml56(para) +msgid "This example shows the default options for the Ceph backup driver." +msgstr "" + +#: ./doc/config-reference/block-storage/backup/swift-backup-driver.xml5(title) +msgid "Swift backup driver" +msgstr "" + +#: ./doc/config-reference/block-storage/backup/swift-backup-driver.xml6(para) +msgid "" +"The backup driver for Swift back-end performs a volume backup to a Swift " +"object storage system." +msgstr "" + +#: ./doc/config-reference/block-storage/backup/swift-backup-driver.xml8(para) +msgid "" +"To enable the Swift backup driver, include the following option in the " +"cinder.conf file:" +msgstr "" + +#: ./doc/config-reference/block-storage/backup/swift-backup-driver.xml12(para) +msgid "" +"The following configuration options are available for the Swift back-end " +"backup driver." +msgstr "" + +#: ./doc/config-reference/block-storage/backup/swift-backup-driver.xml16(para) +msgid "" +"This example shows the default options for the Swift back-end backup driver." +msgstr "" + +#: ./doc/config-reference/image/section_glance-property-protection.xml6(title) +msgid "Image property protection" +msgstr "" + +#: ./doc/config-reference/image/section_glance-property-protection.xml7(para) +msgid "" +"There are currently two types of properties in the Image Service: \"core " +"properties,\" which are defined by the system, and \"additional " +"properties,\" which are arbitrary key/value pairs that can be set on an " +"image." +msgstr "" + +#: ./doc/config-reference/image/section_glance-property-protection.xml11(para) +msgid "" +"With the Havana release, any such property can be protected through " +"configuration. When you put protections on a property, it limits the users " +"who can perform CRUD operations on the property based on their user role. " +"The use case is to enable the cloud provider to maintain extra properties on" +" images so typically this would be an administrator who has access to " +"protected properties, managed with policy.json. The " +"extra property could be licensing information or billing information, for " +"example." +msgstr "" + +#: ./doc/config-reference/image/section_glance-property-protection.xml20(para) +msgid "" +"Properties that don't have protections defined for them will act as they do " +"now: the administrator can control core properties, with the image owner " +"having control over additional properties." +msgstr "" + +#: ./doc/config-reference/image/section_glance-property-protection.xml23(para) +msgid "" +"Property protection can be set in /etc/glance/property-" +"protections.conf, using roles found in " +"policy.json." +msgstr "" + +#: ./doc/config-reference/object-storage/section_object-storage-listendpoints.xml6(title) +msgid "Endpoint listing middleware" +msgstr "" + +#: ./doc/config-reference/object-storage/section_object-storage-listendpoints.xml7(para) +msgid "" +"The endpoint listing middleware enables third-party services that use data " +"locality information to integrate with swift. This middleware reduces " +"network overhead and is designed for third-party services that run inside " +"the firewall. Deploy this middleware on a proxy server because usage of this" +" middleware is not authenticated." +msgstr "" + +#: ./doc/config-reference/object-storage/section_object-storage-listendpoints.xml13(para) +msgid "Format requests for endpoints, as follows:" +msgstr "" + +#: ./doc/config-reference/object-storage/section_object-storage-listendpoints.xml14(replaceable) +#: ./doc/config-reference/object-storage/section_object-storage-listendpoints.xml15(replaceable) +#: ./doc/config-reference/object-storage/section_object-storage-listendpoints.xml16(replaceable) +msgid "{account}" +msgstr "" + +#: ./doc/config-reference/object-storage/section_object-storage-listendpoints.xml14(replaceable) +#: ./doc/config-reference/object-storage/section_object-storage-listendpoints.xml15(replaceable) +msgid "{container}" +msgstr "" + +#: ./doc/config-reference/object-storage/section_object-storage-listendpoints.xml14(replaceable) +msgid "{object}" +msgstr "" + +#: ./doc/config-reference/object-storage/section_object-storage-listendpoints.xml17(para) +msgid "" +"Use the configuration option in the " +"proxy_server.conf file to customize the " +"/endpoints/ path." +msgstr "" + +#: ./doc/config-reference/object-storage/section_object-storage-listendpoints.xml20(para) +msgid "Responses are JSON-encoded lists of endpoints, as follows:" +msgstr "" + +#: ./doc/config-reference/object-storage/section_object-storage-listendpoints.xml22(replaceable) +#: ./doc/config-reference/object-storage/section_object-storage-listendpoints.xml23(replaceable) +#: ./doc/config-reference/object-storage/section_object-storage-listendpoints.xml24(replaceable) +msgid "{server}" +msgstr "" + +#: ./doc/config-reference/object-storage/section_object-storage-listendpoints.xml22(replaceable) +#: ./doc/config-reference/object-storage/section_object-storage-listendpoints.xml23(replaceable) +#: ./doc/config-reference/object-storage/section_object-storage-listendpoints.xml24(replaceable) +msgid "{port}" +msgstr "" + +#: ./doc/config-reference/object-storage/section_object-storage-listendpoints.xml22(replaceable) +#: ./doc/config-reference/object-storage/section_object-storage-listendpoints.xml23(replaceable) +#: ./doc/config-reference/object-storage/section_object-storage-listendpoints.xml24(replaceable) +msgid "{dev}" +msgstr "" + +#: ./doc/config-reference/object-storage/section_object-storage-listendpoints.xml22(replaceable) +#: ./doc/config-reference/object-storage/section_object-storage-listendpoints.xml23(replaceable) +#: ./doc/config-reference/object-storage/section_object-storage-listendpoints.xml24(replaceable) +msgid "{part}" +msgstr "" + +#: ./doc/config-reference/object-storage/section_object-storage-listendpoints.xml22(replaceable) +#: ./doc/config-reference/object-storage/section_object-storage-listendpoints.xml23(replaceable) +#: ./doc/config-reference/object-storage/section_object-storage-listendpoints.xml24(replaceable) +msgid "{acc}" +msgstr "" + +#: ./doc/config-reference/object-storage/section_object-storage-listendpoints.xml22(replaceable) +#: ./doc/config-reference/object-storage/section_object-storage-listendpoints.xml23(replaceable) +msgid "{cont}" +msgstr "" + +#: ./doc/config-reference/object-storage/section_object-storage-listendpoints.xml22(replaceable) +msgid "{obj}" +msgstr "" + +#: ./doc/config-reference/object-storage/section_object-storage-listendpoints.xml25(para) +msgid "An example response is:" +msgstr "" + +#: ./doc/config-reference/object-storage/section_configure_s3.xml6(title) +msgid "Configure Object Storage with the S3 API" +msgstr "" + +#: ./doc/config-reference/object-storage/section_configure_s3.xml7(para) +msgid "" +"The Swift3 middleware emulates the S3 REST API on top of Object Storage." +msgstr "" + +#: ./doc/config-reference/object-storage/section_configure_s3.xml9(para) +msgid "The following operations are currently supported:" +msgstr "" + +#: ./doc/config-reference/object-storage/section_configure_s3.xml12(para) +msgid "GET Service" +msgstr "" + +#: ./doc/config-reference/object-storage/section_configure_s3.xml15(para) +msgid "DELETE Bucket" +msgstr "" + +#: ./doc/config-reference/object-storage/section_configure_s3.xml18(para) +msgid "GET Bucket (List Objects)" +msgstr "" + +#: ./doc/config-reference/object-storage/section_configure_s3.xml21(para) +msgid "PUT Bucket" +msgstr "" + +#: ./doc/config-reference/object-storage/section_configure_s3.xml24(para) +msgid "DELETE Object" +msgstr "" + +#: ./doc/config-reference/object-storage/section_configure_s3.xml27(para) +msgid "GET Object" +msgstr "" + +#: ./doc/config-reference/object-storage/section_configure_s3.xml30(para) +msgid "HEAD Object" +msgstr "" + +#: ./doc/config-reference/object-storage/section_configure_s3.xml33(para) +msgid "PUT Object" +msgstr "" + +#: ./doc/config-reference/object-storage/section_configure_s3.xml36(para) +msgid "PUT Object (Copy)" +msgstr "" + +#: ./doc/config-reference/object-storage/section_configure_s3.xml39(para) +msgid "" +"To use this middleware, first download the latest version from its " +"repository to your proxy server(s)." +msgstr "" + +#: ./doc/config-reference/object-storage/section_configure_s3.xml43(para) +msgid "" +"Optional: To use this middleware with Swift 1.7.0 and previous versions, you" +" must use the v1.7 tag of the fujita/swift3 repository. Clone the " +"repository, as shown previously, and run this command:" +msgstr "" + +#: ./doc/config-reference/object-storage/section_configure_s3.xml48(para) +msgid "Then, install it using standard python mechanisms, such as:" +msgstr "" + +#: ./doc/config-reference/object-storage/section_configure_s3.xml51(para) +msgid "" +"Alternatively, if you have configured the Ubuntu Cloud Archive, you may use:" +" " +msgstr "" + +#: ./doc/config-reference/object-storage/section_configure_s3.xml54(para) +msgid "" +"To add this middleware to your configuration, add the swift3 middleware in " +"front of the auth middleware, and before any other middleware that look at " +"swift requests (like rate limiting)." +msgstr "" + +#: ./doc/config-reference/object-storage/section_configure_s3.xml58(para) +msgid "" +"Ensure that your proxy-server.conf file contains swift3 in the pipeline and " +"the [filter:swift3] section, as shown below:" +msgstr "" + +#: ./doc/config-reference/object-storage/section_configure_s3.xml68(para) +msgid "" +"Next, configure the tool that you use to connect to the S3 API. For S3curl, " +"for example, you must add your host IP information by adding your host IP to" +" the @endpoints array (line 33 in s3curl.pl):" +msgstr "" + +#: ./doc/config-reference/object-storage/section_configure_s3.xml73(para) +msgid "Now you can send commands to the endpoint, such as:" +msgstr "" + +#: ./doc/config-reference/object-storage/section_configure_s3.xml77(para) +msgid "" +"To set up your client, the access key will be the concatenation of the " +"account and user strings that should look like test:tester, and the secret " +"access key is the account password. The host should also point to the Swift " +"storage node's hostname. It also will have to use the old-style calling " +"format, and not the hostname-based container format. Here is an example " +"client setup using the Python boto library on a locally installed all-in-one" +" Swift installation." +msgstr "" + +#: ./doc/config-reference/object-storage/section_object-storage-features.xml6(title) +msgid "Configure Object Storage features" +msgstr "" + +#: ./doc/config-reference/object-storage/section_object-storage-features.xml8(title) +msgid "Object Storage zones" +msgstr "" + +#: ./doc/config-reference/object-storage/section_object-storage-features.xml9(para) +msgid "" +"In OpenStack Object Storage, data is placed across different tiers of " +"failure domains. First, data is spread across regions, then zones, then " +"servers, and finally across drives. Data is placed to get the highest " +"failure domain isolation. If you deploy multiple regions, the Object Storage" +" service places the data across the regions. Within a region, each replica " +"of the data should be stored in unique zones, if possible. If there is only " +"one zone, data should be placed on different servers. And if there is only " +"one server, data should be placed on different drives." +msgstr "" + +#: ./doc/config-reference/object-storage/section_object-storage-features.xml20(para) +msgid "" +"Regions are widely separated installations with a high-latency or otherwise " +"constrained network link between them. Zones are arbitrarily assigned, and " +"it is up to the administrator of the Object Storage cluster to choose an " +"isolation level and attempt to maintain the isolation level through " +"appropriate zone assignment. For example, a zone may be defined as a rack " +"with a single power source. Or a zone may be a DC room with a common utility" +" provider. Servers are identified by a unique IP/port. Drives are locally " +"attached storage volumes identified by mount point." +msgstr "" + +#: ./doc/config-reference/object-storage/section_object-storage-features.xml31(para) +msgid "" +"In small clusters (five nodes or fewer), everything is normally in a single " +"zone. Larger Object Storage deployments may assign zone designations " +"differently; for example, an entire cabinet or rack of servers may be " +"designated as a single zone to maintain replica availability if the cabinet " +"becomes unavailable (for example, due to failure of the top of rack switches" +" or a dedicated circuit). In very large deployments, such as service " +"provider level deployments, each zone might have an entirely autonomous " +"switching and power infrastructure, so that even the loss of an electrical " +"circuit or switching aggregator would result in the loss of a single replica" +" at most." +msgstr "" + +#: ./doc/config-reference/object-storage/section_object-storage-features.xml45(title) +msgid "Rackspace zone recommendations" +msgstr "" + +#: ./doc/config-reference/object-storage/section_object-storage-features.xml46(para) +msgid "" +"For ease of maintenance on OpenStack Object Storage, Rackspace recommends " +"that you set up at least five nodes. Each node is assigned its own zone (for" +" a total of five zones), which gives you host level redundancy. This enables" +" you to take down a single zone for maintenance and still guarantee object " +"availability in the event that another zone fails during your maintenance." +msgstr "" + +#: ./doc/config-reference/object-storage/section_object-storage-features.xml54(para) +msgid "" +"You could keep each server in its own cabinet to achieve cabinet level " +"isolation, but you may wish to wait until your swift service is better " +"established before developing cabinet-level isolation. OpenStack Object " +"Storage is flexible; if you later decide to change the isolation level, you " +"can take down one zone at a time and move them to appropriate new homes." +msgstr "" + +#: ./doc/config-reference/object-storage/section_object-storage-features.xml65(title) +msgid "RAID controller configuration" +msgstr "" + +#: ./doc/config-reference/object-storage/section_object-storage-features.xml66(para) +msgid "" +"OpenStack Object Storage does not require RAID. In fact, most RAID " +"configurations cause significant performance degradation. The main reason " +"for using a RAID controller is the battery-backed cache. It is very " +"important for data integrity reasons that when the operating system confirms" +" a write has been committed that the write has actually been committed to a " +"persistent location. Most disks lie about hardware commits by default, " +"instead writing to a faster write cache for performance reasons. In most " +"cases, that write cache exists only in non-persistent memory. In the case of" +" a loss of power, this data may never actually get committed to disk, " +"resulting in discrepancies that the underlying file system must handle." +msgstr "" + +#: ./doc/config-reference/object-storage/section_object-storage-features.xml79(para) +msgid "" +"OpenStack Object Storage works best on the XFS file system, and this " +"document assumes that the hardware being used is configured appropriately to" +" be mounted with the option.   For more information, refer " +"to the XFS FAQ: http://xfs.org/index.php/XFS_FAQ" +msgstr "" + +#: ./doc/config-reference/object-storage/section_object-storage-features.xml87(para) +msgid "" +"To get the most out of your hardware, it is essential that every disk used " +"in OpenStack Object Storage is configured as a standalone, individual RAID 0" +" disk; in the case of 6 disks, you would have six RAID 0s or one JBOD. Some " +"RAID controllers do not support JBOD or do not support battery backed cache " +"with JBOD. To ensure the integrity of your data, you must ensure that the " +"individual drive caches are disabled and the battery backed cache in your " +"RAID card is configured and used. Failure to configure the controller " +"properly in this case puts data at risk in the case of sudden loss of power." +msgstr "" + +#: ./doc/config-reference/object-storage/section_object-storage-features.xml99(para) +msgid "" +"You can also use hybrid drives or similar options for battery backed up " +"cache configurations without a RAID controller." +msgstr "" + +#: ./doc/config-reference/object-storage/section_object-storage-features.xml105(title) +msgid "Throttle resources through rate limits" +msgstr "" + +#: ./doc/config-reference/object-storage/section_object-storage-features.xml106(para) +msgid "" +"Rate limiting in OpenStack Object Storage is implemented as a pluggable " +"middleware that you configure on the proxy server. Rate limiting is " +"performed on requests that result in database writes to the account and " +"container SQLite databases. It uses memcached and is dependent on the proxy " +"servers having highly synchronized time. The rate limits are limited by the " +"accuracy of the proxy server clocks." +msgstr "" + +#: ./doc/config-reference/object-storage/section_object-storage-features.xml115(title) +msgid "Configure rate limiting" +msgstr "" + +#: ./doc/config-reference/object-storage/section_object-storage-features.xml116(para) +msgid "" +"All configuration is optional. If no account or container limits are " +"provided, no rate limiting occurs. Available configuration options include:" +msgstr "" + +#: ./doc/config-reference/object-storage/section_object-storage-features.xml122(para) +msgid "" +"The container rate limits are linearly interpolated from the values given. A" +" sample container rate limiting could be:" +msgstr "" + +#: ./doc/config-reference/object-storage/section_object-storage-features.xml125(para) +msgid "container_ratelimit_100 = 100" +msgstr "" + +#: ./doc/config-reference/object-storage/section_object-storage-features.xml126(para) +msgid "container_ratelimit_200 = 50" +msgstr "" + +#: ./doc/config-reference/object-storage/section_object-storage-features.xml127(para) +msgid "container_ratelimit_500 = 20" +msgstr "" + +#: ./doc/config-reference/object-storage/section_object-storage-features.xml128(para) +msgid "This would result in:" +msgstr "" + +#: ./doc/config-reference/object-storage/section_object-storage-features.xml130(caption) +msgid "Values for Rate Limiting with Sample Configuration Settings" +msgstr "" + +#: ./doc/config-reference/object-storage/section_object-storage-features.xml134(td) +msgid "Container Size" +msgstr "" + +#: ./doc/config-reference/object-storage/section_object-storage-features.xml135(td) +msgid "Rate Limit" +msgstr "" + +#: ./doc/config-reference/object-storage/section_object-storage-features.xml138(td) +msgid "0-99" +msgstr "" + +#: ./doc/config-reference/object-storage/section_object-storage-features.xml139(td) +msgid "No limiting" +msgstr "" + +#: ./doc/config-reference/object-storage/section_object-storage-features.xml142(td) +#: ./doc/config-reference/object-storage/section_object-storage-features.xml143(td) +msgid "100" +msgstr "" + +#: ./doc/config-reference/object-storage/section_object-storage-features.xml147(td) +msgid "150" +msgstr "" + +#: ./doc/config-reference/object-storage/section_object-storage-features.xml148(td) +msgid "75" +msgstr "" + +#: ./doc/config-reference/object-storage/section_object-storage-features.xml151(td) +msgid "500" +msgstr "" + +#: ./doc/config-reference/object-storage/section_object-storage-features.xml152(td) +#: ./doc/config-reference/object-storage/section_object-storage-features.xml156(td) +msgid "20" +msgstr "" + +#: ./doc/config-reference/object-storage/section_object-storage-features.xml155(td) +msgid "1000" +msgstr "" + +#: ./doc/config-reference/object-storage/section_object-storage-features.xml163(title) +msgid "Health check" +msgstr "" + +#: ./doc/config-reference/object-storage/section_object-storage-features.xml164(para) +msgid "" +"Provides an easy way to monitor whether the swift proxy server is alive. If " +"you access the proxy with the path /healthcheck, it " +"respond OK in the response body, which monitoring tools " +"can use." +msgstr "" + +#: ./doc/config-reference/object-storage/section_object-storage-features.xml174(title) +msgid "Domain remap" +msgstr "" + +#: ./doc/config-reference/object-storage/section_object-storage-features.xml175(para) +msgid "" +"Middleware that translates container and account parts of a domain to path " +"parameters that the proxy server understands." +msgstr "" + +#: ./doc/config-reference/object-storage/section_object-storage-features.xml183(title) +msgid "CNAME lookup" +msgstr "" + +#: ./doc/config-reference/object-storage/section_object-storage-features.xml184(para) +msgid "" +"Middleware that translates an unknown domain in the host header to something" +" that ends with the configured storage_domain by looking up the given " +"domain's CNAME record in DNS." +msgstr "" + +#: ./doc/config-reference/object-storage/section_object-storage-features.xml194(title) +msgid "Temporary URL" +msgstr "" + +#: ./doc/config-reference/object-storage/section_object-storage-features.xml195(para) +msgid "" +"Allows the creation of URLs to provide temporary access to objects. For " +"example, a website may wish to provide a link to download a large object in " +"Swift, but the Swift account has no public access. The website can generate " +"a URL that provides GET access for a limited time to the resource. When the " +"web browser user clicks on the link, the browser downloads the object " +"directly from Swift, eliminating the need for the website to act as a proxy " +"for the request. If the user shares the link with all his friends, or " +"accidentally posts it on a forum, the direct access is limited to the " +"expiration time set when the website created the link." +msgstr "" + +#: ./doc/config-reference/object-storage/section_object-storage-features.xml210(literal) +msgid "temp_url_sig" +msgstr "" + +#: ./doc/config-reference/object-storage/section_object-storage-features.xml212(para) +msgid "A cryptographic signature" +msgstr "" + +#: ./doc/config-reference/object-storage/section_object-storage-features.xml216(literal) +msgid "temp_url_expires" +msgstr "" + +#: ./doc/config-reference/object-storage/section_object-storage-features.xml218(para) +msgid "An expiration date, in Unix time." +msgstr "" + +#: ./doc/config-reference/object-storage/section_object-storage-features.xml207(para) +msgid "" +"A temporary URL is the typical URL associated with an object, with two " +"additional query parameters:" +msgstr "" + +#: ./doc/config-reference/object-storage/section_object-storage-features.xml222(para) +msgid "An example of a temporary URL:" +msgstr "" + +#: ./doc/config-reference/object-storage/section_object-storage-features.xml228(para) +msgid "" +"To create temporary URLs, first set the X-Account-Meta-Temp-URL-" +"Key header on your Swift account to an arbitrary string. This " +"string serves as a secret key. For example, to set a key of " +"b3968d0207b54ece87cccc06515a89d4 using the " +" command-line tool:" +msgstr "" + +#: ./doc/config-reference/object-storage/section_object-storage-features.xml235(replaceable) +msgid "b3968d0207b54ece87cccc06515a89d4" +msgstr "" + +#: ./doc/config-reference/object-storage/section_object-storage-features.xml236(para) +msgid "Next, generate an HMAC-SHA1 (RFC 2104) signature to specify:" +msgstr "" + +#: ./doc/config-reference/object-storage/section_object-storage-features.xml240(para) +msgid "" +"Which HTTP method to allow (typically GET or " +"PUT)" +msgstr "" + +#: ./doc/config-reference/object-storage/section_object-storage-features.xml245(para) +msgid "The expiry date as a Unix timestamp" +msgstr "" + +#: ./doc/config-reference/object-storage/section_object-storage-features.xml248(para) +msgid "the full path to the object" +msgstr "" + +#: ./doc/config-reference/object-storage/section_object-storage-features.xml251(para) +msgid "" +"The secret key set as the X-Account-Meta-Temp-URL-Key" +msgstr "" + +#: ./doc/config-reference/object-storage/section_object-storage-features.xml255(para) +msgid "" +"Here is code generating the signature for a GET for 24 hours on " +"/v1/AUTH_account/container/object:" +msgstr "" + +#: ./doc/config-reference/object-storage/section_object-storage-features.xml279(para) +msgid "" +"Changing the X-Account-Meta-Temp-URL-Key invalidates any " +"previously generated temporary URLs within 60 seconds (the memcache time for" +" the key). Swift supports up to two keys, specified by X-Account-" +"Meta-Temp-URL-Key and X-Account-Meta-Temp-URL-" +"Key-2. Signatures are checked against both keys, if present. This " +"is to allow for key rotation without invalidating all existing temporary " +"URLs." +msgstr "" + +#: ./doc/config-reference/object-storage/section_object-storage-features.xml270(para) +msgid "" +"Any alteration of the resource path or query arguments results in a " +"401Unauthorized error. " +"Similarly, a PUT where GET was the allowed method returns a " +"401. HEAD is allowed if GET or PUT is allowed. Using " +"this in combination with browser form post translation middleware could also" +" allow direct-from-browser uploads to specific locations in Swift. Note that" +" " +msgstr "" + +#: ./doc/config-reference/object-storage/section_object-storage-features.xml291(para) +msgid "" +"Swift includes a script called that generates the query " +"parameters automatically:" +msgstr "" + +#: ./doc/config-reference/object-storage/section_object-storage-features.xml298(para) +msgid "" +"Because this command only returns the path, you must prefix the Swift " +"storage host name (for example, https://swift-" +"cluster.example.com)." +msgstr "" + +#: ./doc/config-reference/object-storage/section_object-storage-features.xml301(para) +msgid "" +"With GET Temporary URLs, a Content-Disposition header is " +"set on the response so that browsers interpret this as a file attachment to " +"be saved. The file name chosen is based on the object name, but you can " +"override this with a filename query parameter. The " +"following example specifies a filename of My Test " +"File.pdf:" +msgstr "" + +#: ./doc/config-reference/object-storage/section_object-storage-features.xml324(emphasis) +msgid "tempurl" +msgstr "" + +#: ./doc/config-reference/object-storage/section_object-storage-features.xml313(para) +msgid "" +"To enable Temporary URL functionality, edit /etc/swift/proxy-" +"server.conf to add tempurl to the " +"pipeline variable defined in the " +"[pipeline:main] section. The tempurl " +"entry should appear immediately before the authentication filters in the " +"pipeline, such as authtoken, tempauth " +"or keystoneauth. For example:" +msgstr "" + +#: ./doc/config-reference/object-storage/section_object-storage-features.xml331(title) +msgid "Name check filter" +msgstr "" + +#: ./doc/config-reference/object-storage/section_object-storage-features.xml332(para) +msgid "" +"Name Check is a filter that disallows any paths that contain defined " +"forbidden characters or that exceed a defined length." +msgstr "" + +#: ./doc/config-reference/object-storage/section_object-storage-features.xml340(title) +msgid "Constraints" +msgstr "" + +#: ./doc/config-reference/object-storage/section_object-storage-features.xml341(para) +msgid "" +"To change the OpenStack Object Storage internal limits, update the values in" +" the swift-constraints section in the " +"swift.conf file. Use caution when you update these " +"values because they affect the performance in the entire cluster." +msgstr "" + +#: ./doc/config-reference/object-storage/section_object-storage-features.xml352(title) +msgid "Cluster health" +msgstr "" + +#: ./doc/config-reference/object-storage/section_object-storage-features.xml353(para) +msgid "" +"Use the tool to measure overall cluster health. This tool " +"checks if a set of deliberately distributed containers and objects are " +"currently in their proper places within the cluster. For instance, a common " +"deployment has three replicas of each object. The health of that object can " +"be measured by checking if each replica is in its proper place. If only 2 of" +" the 3 is in place the object’s health can be said to be at 66.66%, where " +"100% would be perfect. A single object’s health, especially an older object," +" usually reflects the health of that entire partition the object is in. If " +"you make enough objects on a distinct percentage of the partitions in the " +"cluster,you get a good estimate of the overall cluster health. In practice, " +"about 1% partition coverage seems to balance well between accuracy and the " +"amount of time it takes to gather results. The first thing that needs to be " +"done to provide this health value is create a new account solely for this " +"usage. Next, you need to place the containers and objects throughout the " +"system so that they are on distinct partitions. The swift-dispersion-" +"populate tool does this by making up random container and object names until" +" they fall on distinct partitions. Last, and repeatedly for the life of the " +"cluster, you must run the tool to check the health of each " +"of these containers and objects. These tools need direct access to the " +"entire cluster and to the ring files (installing them on a proxy server " +"suffices). The and commands both use the " +"same configuration file, /etc/swift/dispersion.conf. " +"Example dispersion.conf file:" +msgstr "" + +#: ./doc/config-reference/object-storage/section_object-storage-features.xml393(para) +msgid "" +"There are also configuration options for specifying the dispersion coverage," +" which defaults to 1%, retries, concurrency, and so on. However, the " +"defaults are usually fine. Once the configuration is in place, run " +" to populate the containers and objects throughout the " +"cluster. Now that those containers and objects are in place, you can run " +" to get a dispersion report, or the overall health of the " +"cluster. Here is an example of a cluster in perfect health:" +msgstr "" + +#: ./doc/config-reference/object-storage/section_object-storage-features.xml413(para) +msgid "" +"Now, deliberately double the weight of a device in the object ring (with " +"replication turned off) and re-run the dispersion report to show what impact" +" that has:" +msgstr "" + +#: ./doc/config-reference/object-storage/section_object-storage-features.xml429(para) +msgid "" +"You can see the health of the objects in the cluster has gone down " +"significantly. Of course, this test environment has just four devices, in a " +"production environment with many devices the impact of one device change is " +"much less. Next, run the replicators to get everything put back into place " +"and then rerun the dispersion report:" +msgstr "" + +#: ./doc/config-reference/object-storage/section_object-storage-features.xml446(para) +msgid "" +"Alternatively, the dispersion report can also be output in json format. This" +" allows it to be more easily consumed by third party utilities:" +msgstr "" + +#. Usage documented in +#. http://docs.openstack.org/developer/swift/overview_large_objects.html +#: ./doc/config-reference/object-storage/section_object-storage-features.xml460(title) +msgid "Static Large Object (SLO) support" +msgstr "" + +#: ./doc/config-reference/object-storage/section_object-storage-features.xml461(para) +msgid "" +"This feature is very similar to Dynamic Large Object (DLO) support in that " +"it enables the user to upload many objects concurrently and afterwards " +"download them as a single object. It is different in that it does not rely " +"on eventually consistent container listings to do so. Instead, a user " +"defined manifest of the object segments is used." +msgstr "" + +#: ./doc/config-reference/object-storage/section_object-storage-features.xml473(title) +msgid "Container quotas" +msgstr "" + +#: ./doc/config-reference/object-storage/section_object-storage-features.xml474(para) +msgid "" +"The container_quotas middleware implements simple quotas that can be imposed" +" on swift containers by a user with the ability to set container metadata, " +"most likely the account administrator. This can be useful for limiting the " +"scope of containers that are delegated to non-admin users, exposed to " +"formpost uploads, or just as a self-imposed sanity check." +msgstr "" + +#: ./doc/config-reference/object-storage/section_object-storage-features.xml481(para) +msgid "" +"Any object PUT operations that exceed these quotas return a 413 response " +"(request entity too large) with a descriptive body." +msgstr "" + +#: ./doc/config-reference/object-storage/section_object-storage-features.xml484(para) +msgid "" +"Quotas are subject to several limitations: eventual consistency, the " +"timeliness of the cached container_info (60 second ttl by default), and it " +"is unable to reject chunked transfer uploads that exceed the quota (though " +"once the quota is exceeded, new chunked transfers are refused)." +msgstr "" + +#: ./doc/config-reference/object-storage/section_object-storage-features.xml490(para) +msgid "" +"Set quotas by adding meta values to the container. These values are " +"validated when you set them:" +msgstr "" + +#: ./doc/config-reference/object-storage/section_object-storage-features.xml494(para) +msgid "X-Container-Meta-Quota-Bytes: Maximum size of the container, in bytes." +msgstr "" + +#: ./doc/config-reference/object-storage/section_object-storage-features.xml498(para) +msgid "X-Container-Meta-Quota-Count: Maximum object count of the container." +msgstr "" + +#: ./doc/config-reference/object-storage/section_object-storage-features.xml507(title) +msgid "Account quotas" +msgstr "" + +#: ./doc/config-reference/object-storage/section_object-storage-features.xml508(para) +msgid "" +"The x-account-meta-quota-bytes metadata entry must be" +" requests (PUT, POST) if a given account quota (in bytes) is exceeded while " +"DELETE requests are still allowed." +msgstr "" + +#: ./doc/config-reference/object-storage/section_object-storage-features.xml512(para) +msgid "" +"The x-account-meta-quota-bytes metadata entry must be set to store and " +"enable the quota. Write requests to this metadata entry are only permitted " +"for resellers. There is no account quota limitation on a reseller account " +"even if x-account-meta-quota-bytes is set." +msgstr "" + +#: ./doc/config-reference/object-storage/section_object-storage-features.xml517(para) +msgid "" +"Any object PUT operations that exceed the quota return a 413 response " +"(request entity too large) with a descriptive body." +msgstr "" + +#: ./doc/config-reference/object-storage/section_object-storage-features.xml520(para) +msgid "" +"The following command uses an admin account that own the Reseller role to " +"set a quota on the test account:" +msgstr "" + +#: ./doc/config-reference/object-storage/section_object-storage-features.xml524(para) +msgid "Here is the stat listing of an account where quota has been set:" +msgstr "" + +#: ./doc/config-reference/object-storage/section_object-storage-features.xml534(para) +msgid "This command removes the account quota:" +msgstr "" + +#: ./doc/config-reference/object-storage/section_object-storage-features.xml538(title) +msgid "Bulk delete" +msgstr "" + +#: ./doc/config-reference/object-storage/section_object-storage-features.xml539(para) +msgid "" +"Use bulk-delete to delete multiple files from an account with a single " +"request. Responds to DELETE requests with a header 'X-Bulk-Delete: " +"true_value'. The body of the DELETE request is a new line separated list of " +"files to delete. The files listed must be URL encoded and in the form:" +msgstr "" + +#: ./doc/config-reference/object-storage/section_object-storage-features.xml548(para) +msgid "" +"If all files are successfully deleted (or did not exist), the operation " +"returns HTTPOk. If any files failed to delete, the operation returns " +"HTTPBadGateway. In both cases the response body is a JSON dictionary that " +"shows the number of files that were successfully deleted or not found. The " +"files that failed are listed." +msgstr "" + +#: ./doc/config-reference/object-storage/section_object-storage-features.xml560(title) +msgid "Drive audit" +msgstr "" + +#: ./doc/config-reference/object-storage/section_object-storage-features.xml561(para) +msgid "" +"The configuration items reference a " +"script that can be run by using to watch for bad drives. If" +" errors are detected, it unmounts the bad drive, so that OpenStack Object " +"Storage can work around it. It takes the following options:" +msgstr "" + +#: ./doc/config-reference/object-storage/section_object-storage-features.xml572(title) +msgid "Form post" +msgstr "" + +#: ./doc/config-reference/object-storage/section_object-storage-features.xml573(para) +msgid "" +"Middleware that provides the ability to upload objects to a cluster using an" +" HTML form POST. The format of the form is:" +msgstr "" + +#: ./doc/config-reference/object-storage/section_object-storage-features.xml588(para) +msgid "" +"The swift-url is the URL to the Swift destination, such " +"as: https://swift-" +"cluster.example.com/v1/AUTH_account/container/object_prefix The name " +"of each file uploaded is appended to the specified swift-" +"url. So, you can upload directly to the root of container with a " +"url like: https://swift-" +"cluster.example.com/v1/AUTH_account/container/ Optionally, you can " +"include an object prefix to better separate different users’ uploads, such " +"as: https://swift-" +"cluster.example.com/v1/AUTH_account/container/object_prefix" +msgstr "" + +#: ./doc/config-reference/object-storage/section_object-storage-features.xml600(para) +msgid "" +"The form method must be POST and the enctype must be set as " +"multipart/form-data." +msgstr "" + +#: ./doc/config-reference/object-storage/section_object-storage-features.xml603(para) +msgid "" +"The redirect attribute is the URL to redirect the browser to after the " +"upload completes. The URL has status and message query parameters added to " +"it, indicating the HTTP status code for the upload (2xx is success) and a " +"possible message for further information if there was an error (such as " +"“max_file_size exceeded”)." +msgstr "" + +#: ./doc/config-reference/object-storage/section_object-storage-features.xml610(para) +msgid "" +"The max_file_size attribute must be included and " +"indicates the largest single file upload that can be done, in bytes." +msgstr "" + +#: ./doc/config-reference/object-storage/section_object-storage-features.xml613(para) +msgid "" +"The max_file_count attribute must be included and " +"indicates the maximum number of files that can be uploaded with the form. " +"Include additional <![CDATA[<input type=\"file\" " +"name=\"filexx\"/>]]> attributes if desired." +msgstr "" + +#: ./doc/config-reference/object-storage/section_object-storage-features.xml619(para) +msgid "" +"The expires attribute is the Unix timestamp before which the form must be " +"submitted before it is invalidated." +msgstr "" + +#: ./doc/config-reference/object-storage/section_object-storage-features.xml622(para) +msgid "" +"The signature attribute is the HMAC-SHA1 signature of the form. This sample " +"Python code shows how to compute the signature:" +msgstr "" + +#: ./doc/config-reference/object-storage/section_object-storage-features.xml639(para) +msgid "" +"The key is the value of the X-Account-Meta-Temp-URL-Key " +"header on the account." +msgstr "" + +#: ./doc/config-reference/object-storage/section_object-storage-features.xml642(para) +msgid "" +"Be certain to use the full path, from the /v1/ onward." +msgstr "" + +#: ./doc/config-reference/object-storage/section_object-storage-features.xml644(para) +msgid "" +"The command line tool may be used (mostly just when " +"testing) to compute expires and signature." +msgstr "" + +#: ./doc/config-reference/object-storage/section_object-storage-features.xml648(para) +msgid "" +"The file attributes must appear after the other attributes to be processed " +"correctly. If attributes come after the file, they are not sent with the " +"sub-request because on the server side, all attributes in the file cannot be" +" parsed unless the whole file is read into memory and the server does not " +"have enough memory to service these requests. So, attributes that follow the" +" file are ignored." +msgstr "" + +#: ./doc/config-reference/object-storage/section_object-storage-features.xml661(title) +msgid "Static web sites" +msgstr "" + +#: ./doc/config-reference/object-storage/section_object-storage-features.xml662(para) +msgid "" +"When configured, this middleware serves container data as a static web site " +"with index file and error file resolution and optional file listings. This " +"mode is normally only active for anonymous requests." +msgstr "" + +#: ./doc/config-reference/object-storage/section_object-storage-cors.xml6(title) +msgid "Cross-origin resource sharing" +msgstr "" + +#: ./doc/config-reference/object-storage/section_object-storage-cors.xml7(para) +msgid "" +"Cross-Origin Resource Sharing (CORS) is a mechanism to allow code running in" +" a browser (JavaScript for example) to make requests to a domain other then " +"the one from where it originated. Swift supports CORS requests to containers" +" and objects within the containers using metadata held on the container." +msgstr "" + +#: ./doc/config-reference/object-storage/section_object-storage-cors.xml13(para) +msgid "" +"In addition to the metadata on containers, you can use the " +" option in the proxy-" +"server.conf file to set a list of hosts that are included with " +"any CORS request by default." +msgstr "" + +#: ./doc/config-reference/object-storage/section_object-storage-general-service-conf.xml6(title) +msgid "Object Storage general service configuration" +msgstr "" + +#: ./doc/config-reference/object-storage/section_object-storage-general-service-conf.xml7(para) +msgid "" +"Most Object Storage services fall into two categories, Object Storage's wsgi" +" servers and background daemons." +msgstr "" + +#: ./doc/config-reference/object-storage/section_object-storage-general-service-conf.xml11(para) +msgid "" +"Object Storage uses paste.deploy to manage server configurations. Read more " +"at http://pythonpaste.org/deploy/." +msgstr "" + +#: ./doc/config-reference/object-storage/section_object-storage-general-service-conf.xml14(para) +msgid "" +"Default configuration options are set in the `[DEFAULT]` section, and any " +"options specified there can be overridden in any of the other sections when " +"the syntax set option_name = value is in place." +msgstr "" + +#: ./doc/config-reference/object-storage/section_object-storage-general-service-conf.xml19(para) +msgid "" +"Configuration for servers and daemons can be expressed together in the same " +"file for each type of server, or separately. If a required section for the " +"service trying to start is missing there will be an error. The sections not " +"used by the service are ignored." +msgstr "" + +#: ./doc/config-reference/object-storage/section_object-storage-general-service-conf.xml25(para) +msgid "" +"Consider the example of an object storage node. By convention configuration " +"for the object-server, object-updater, object-replicator, and object-auditor" +" exist in a single file /etc/swift/object-server.conf:" +msgstr "" + +#: ./doc/config-reference/object-storage/section_object-storage-general-service-conf.xml47(para) +msgid "" +"Object Storage services expect a configuration path as the first argument:" +msgstr "" + +#: ./doc/config-reference/object-storage/section_object-storage-general-service-conf.xml55(para) +msgid "" +"If you omit the object-auditor section this file can not be used as the " +"configuration path when starting the daemon:" +msgstr "" + +#: ./doc/config-reference/object-storage/section_object-storage-general-service-conf.xml63(para) +msgid "" +"If the configuration path is a directory instead of a file all of the files " +"in the directory with the file extension \".conf\" will be combined to " +"generate the configuration object which is delivered to the Object Storage " +"service. This is referred to generally as \"directory based configuration\"." +msgstr "" + +#: ./doc/config-reference/object-storage/section_object-storage-general-service-conf.xml70(para) +msgid "" +"Directory based configuration leverages ConfigParser's native multi-file " +"support. Files ending in \".conf\" in the given directory are parsed in " +"lexicographical order. File names starting with '.' are ignored. A mixture " +"of file and directory configuration paths is not supported - if the " +"configuration path is a file, only that file will be parsed." +msgstr "" + +#: ./doc/config-reference/object-storage/section_object-storage-general-service-conf.xml78(para) +msgid "" +"The Object Storage service management tool swift-init " +"has adopted the convention of looking for " +"/etc/swift/{type}-server.conf.d/ if the file " +"/etc/swift/{type}-server.conf file does not exist." +msgstr "" + +#: ./doc/config-reference/object-storage/section_object-storage-general-service-conf.xml86(para) +msgid "" +"When using directory based configuration, if the same option under the same " +"section appears more than once in different files, the last value parsed is " +"said to override previous occurrences. You can ensure proper override " +"precedence by prefixing the files in the configuration directory with " +"numerical values, as in the following example file layout:" +msgstr "" + +#: ./doc/config-reference/object-storage/section_object-storage-general-service-conf.xml105(para) +msgid "" +"You can inspect the resulting combined configuration object using the " +" command line tool." +msgstr "" + +#. Put one translator per line, in the form of NAME , YEAR1, YEAR2 +#: ./doc/config-reference/object-storage/section_object-storage-general-service-conf.xml0(None) +msgid "translator-credits" +msgstr "" diff --git a/doc/glossary/locale/glossary.pot b/doc/glossary/locale/glossary.pot new file mode 100644 index 0000000000..29e113ceff --- /dev/null +++ b/doc/glossary/locale/glossary.pot @@ -0,0 +1,4792 @@ +msgid "" +msgstr "" +"Project-Id-Version: PACKAGE VERSION\n" +"POT-Creation-Date: 2014-01-30 06:24+0000\n" +"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n" +"Last-Translator: FULL NAME \n" +"Language-Team: LANGUAGE \n" +"MIME-Version: 1.0\n" +"Content-Type: text/plain; charset=UTF-8\n" +"Content-Transfer-Encoding: 8bit\n" + +#: ./doc/glossary/glossary-terms.xml:5(title) +msgid "Glossary" +msgstr "" + +#: ./doc/glossary/glossary-terms.xml:8(para) +msgid "Licensed under the Apache License, Version 2.0 (the \"License\"); you may not use this file except in compliance with the License. You may obtain a copy of the License at" +msgstr "" + +#: ./doc/glossary/glossary-terms.xml:15(link) +msgid "http://www.apache.org/licenses/LICENSE-2.0" +msgstr "" + +#: ./doc/glossary/glossary-terms.xml:17(para) +msgid "Unless required by applicable law or agreed to in writing, software distributed under the License is distributed on an \"AS IS\" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. See the License for the specific language governing permissions and limitations under the License." +msgstr "" + +#: ./doc/glossary/glossary-terms.xml:27(title) +msgid "A" +msgstr "" + +#: ./doc/glossary/glossary-terms.xml:29(glossterm) +msgid "absolute limit" +msgstr "" + +#: ./doc/glossary/glossary-terms.xml:31(para) +msgid "Impassable limits for nova VMs. Settings include total RAM size, maximum number of vCPUs, and maximum disk size." +msgstr "" + +#: ./doc/glossary/glossary-terms.xml:37(glossterm) +msgid "access control list" +msgstr "" + +#: ./doc/glossary/glossary-terms.xml:39(para) +msgid "A list of permissions attached to an object. An ACL specifies which users or system processes have access to objects. It also defines which operations can be performed on specified objects. Each entry in a typical ACL specifies a subject and an operation. For instance, ACL entry, (Alice, delete), for a file gives Alice permission to delete the file." +msgstr "" + +#: ./doc/glossary/glossary-terms.xml:45(glossterm) +msgid "access key" +msgstr "" + +#: ./doc/glossary/glossary-terms.xml:47(para) +msgid "Alternative term for an Amazon EC2 access key. See EC2 Access key." +msgstr "" + +#: ./doc/glossary/glossary-terms.xml:52(glossterm) +msgid "account" +msgstr "" + +#: ./doc/glossary/glossary-terms.xml:54(para) +msgid "The swift context of an account. Do not confuse with a user account from an identity service such as Active Directory, /etc/passwd, OpenLDAP, keystone, and so on." +msgstr "" + +#: ./doc/glossary/glossary-terms.xml:61(glossterm) +msgid "account auditor" +msgstr "" + +#: ./doc/glossary/glossary-terms.xml:63(para) +msgid "Checks for missing replicas, incorrect, and corrupted objects in a specified swift account by running queries against the back-end SQLite database." +msgstr "" + +#: ./doc/glossary/glossary-terms.xml:70(glossterm) +msgid "account database" +msgstr "" + +#: ./doc/glossary/glossary-terms.xml:72(para) +msgid "A SQLite database that contains swift accounts and related metadata and is accessed by the accounts server." +msgstr "" + +#: ./doc/glossary/glossary-terms.xml:78(glossterm) +msgid "account reaper" +msgstr "" + +#: ./doc/glossary/glossary-terms.xml:80(para) +msgid "A swift worker that scans for and deletes account databases that are marked for deletion on an account server." +msgstr "" + +#: ./doc/glossary/glossary-terms.xml:86(glossterm) +msgid "account server" +msgstr "" + +#: ./doc/glossary/glossary-terms.xml:88(para) +msgid "Lists containers in swift and stores container information in the account database." +msgstr "" + +#: ./doc/glossary/glossary-terms.xml:93(glossterm) +msgid "account service" +msgstr "" + +#: ./doc/glossary/glossary-terms.xml:95(para) +msgid "A swift component that provides account services such as list, create, modify, and audit. Do not confuse with keystone, OpenLDAP, or similar user account services." +msgstr "" + +#: ./doc/glossary/glossary-terms.xml:102(glossterm) +msgid "accounting" +msgstr "" + +#: ./doc/glossary/glossary-terms.xml:104(para) +msgid "The Compute Service provides accounting information through the event notification and system usage data facilities." +msgstr "" + +#: ./doc/glossary/glossary-terms.xml:110(glossterm) +msgid "ACL" +msgstr "" + +#: ./doc/glossary/glossary-terms.xml:112(para) +msgid "See access control list." +msgstr "" + +#: ./doc/glossary/glossary-terms.xml:116(glossterm) +msgid "Active Directory" +msgstr "" + +#: ./doc/glossary/glossary-terms.xml:118(para) +msgid "Authentication and Identity Service by Microsoft, based on LDAP. Supported in OpenStack." +msgstr "" + +#: ./doc/glossary/glossary-terms.xml:124(glossterm) +msgid "address pool" +msgstr "" + +#: ./doc/glossary/glossary-terms.xml:126(para) +msgid "A group of fixed and/or floating IP addresses that are assigned to a nova project and can be used by or assigned to the VM instances in a project." +msgstr "" + +#: ./doc/glossary/glossary-terms.xml:133(glossterm) +msgid "admin API" +msgstr "" + +#: ./doc/glossary/glossary-terms.xml:135(para) +msgid "A subset of API calls that are accessible to authorized administrators and are generally not accessible to end users or the public internet, can exist as a separate service (keystone) or can be a subset of another API (nova)." +msgstr "" + +#: ./doc/glossary/glossary-terms.xml:143(glossterm) +msgid "admin server" +msgstr "" + +#: ./doc/glossary/glossary-terms.xml:145(para) +msgid "In the context of keystone, the worker process that provides access to the admin API." +msgstr "" + +#: ./doc/glossary/glossary-terms.xml:150(glossterm) +msgid "Advanced Message Queuing Protocol (AMQP)" +msgstr "" + +#: ./doc/glossary/glossary-terms.xml:153(para) +msgid "The open standard messaging protocol used by nova for intra-service communications, provided by RabbitMQ (the default), Qpid, or ZeroMQ." +msgstr "" + +#: ./doc/glossary/glossary-terms.xml:159(glossterm) +msgid "Advanced RISC Machine (ARM)" +msgstr "" + +#: ./doc/glossary/glossary-terms.xml:161(para) +msgid "Lower power consumption CPU often found in mobile and embedded devices. Supported by OpenStack." +msgstr "" + +#: ./doc/glossary/glossary-terms.xml:167(glossterm) +msgid "alert" +msgstr "" + +#: ./doc/glossary/glossary-terms.xml:169(para) +msgid "The Compute Service can send alerts through its notification system, which includes a facility to create custom notification drivers. Alerts can be sent to and displayed on the horizon dashboard." +msgstr "" + +#: ./doc/glossary/glossary-terms.xml:176(glossterm) +msgid "allocate" +msgstr "" + +#: ./doc/glossary/glossary-terms.xml:178(para) +msgid "The process of taking floating IP address from the address pool so it can be associated with a fixed IP on a nova VM instance." +msgstr "" + +#: ./doc/glossary/glossary-terms.xml:184(glossterm) +msgid "Amazon Kernel Image (AKI)" +msgstr "" + +#: ./doc/glossary/glossary-terms.xml:186(para) ./doc/glossary/glossary-terms.xml:193(para) ./doc/glossary/glossary-terms.xml:200(para) +msgid "Both a VM container format and disk format. Supported by glance." +msgstr "" + +#: ./doc/glossary/glossary-terms.xml:191(glossterm) +msgid "Amazon Machine Image (AMI)" +msgstr "" + +#: ./doc/glossary/glossary-terms.xml:198(glossterm) +msgid "Amazon Ramdisk Image (ARI)" +msgstr "" + +#: ./doc/glossary/glossary-terms.xml:205(glossterm) +msgid "AMQP" +msgstr "" + +#: ./doc/glossary/glossary-terms.xml:207(para) +msgid "Advanced Message Queue Protocol. An open Internet protocol for reliably sending and receiving messages. It enables building a diverse, coherent messaging ecosystem." +msgstr "" + +#: ./doc/glossary/glossary-terms.xml:214(glossterm) +msgid "Anvil" +msgstr "" + +#: ./doc/glossary/glossary-terms.xml:216(para) +msgid "A project that ports the shell script-based project named devstack to Python." +msgstr "" + +#: ./doc/glossary/glossary-terms.xml:221(glossterm) +msgid "Apache" +msgstr "" + +#: ./doc/glossary/glossary-terms.xml:223(para) +msgid "The Apache Software Foundation supports the Apache community of open-source software projects. These projects provide software products for the public good." +msgstr "" + +#: ./doc/glossary/glossary-terms.xml:230(glossterm) +msgid "Apache License 2.0" +msgstr "" + +#: ./doc/glossary/glossary-terms.xml:232(para) +msgid "All OpenStack core projects are provided under the terms of the Apache License 2.0 license." +msgstr "" + +#: ./doc/glossary/glossary-terms.xml:238(glossterm) +msgid "Apache Web Server" +msgstr "" + +#: ./doc/glossary/glossary-terms.xml:240(para) +msgid "The most common web server software currently used on the Internet." +msgstr "" + +#: ./doc/glossary/glossary-terms.xml:245(glossterm) +msgid "API" +msgstr "" + +#: ./doc/glossary/glossary-terms.xml:247(para) +msgid "Application programming interface." +msgstr "" + +#: ./doc/glossary/glossary-terms.xml:251(glossterm) +msgid "API endpoint" +msgstr "" + +#: ./doc/glossary/glossary-terms.xml:253(para) +msgid "The daemon, worker, or service that a client communicates with to access an API. API endpoints can provide any number of services such as keystone authentication, sales data, performance metrics, nova VM commands, census data, and so on." +msgstr "" + +#: ./doc/glossary/glossary-terms.xml:262(glossterm) +msgid "API extension" +msgstr "" + +#: ./doc/glossary/glossary-terms.xml:264(para) +msgid "A nova and neutron feature that enables custom modules to extend the core APIs." +msgstr "" + +#: ./doc/glossary/glossary-terms.xml:269(glossterm) +msgid "API extension plug-in" +msgstr "" + +#: ./doc/glossary/glossary-terms.xml:271(para) +msgid "Alternative term for a neutron plug-in or neutron API extension." +msgstr "" + +#: ./doc/glossary/glossary-terms.xml:276(glossterm) +msgid "API key" +msgstr "" + +#: ./doc/glossary/glossary-terms.xml:278(para) +msgid "Alternative term for an API token." +msgstr "" + +#: ./doc/glossary/glossary-terms.xml:282(glossterm) +msgid "API server" +msgstr "" + +#: ./doc/glossary/glossary-terms.xml:284(para) +msgid "Any node running a daemon or worker that provides an API endpoint." +msgstr "" + +#: ./doc/glossary/glossary-terms.xml:289(glossterm) +msgid "API token" +msgstr "" + +#: ./doc/glossary/glossary-terms.xml:291(para) +msgid "Passed to API requests and used by OpenStack to verify that the client is authorized to run the requested operation." +msgstr "" + +#: ./doc/glossary/glossary-terms.xml:297(glossterm) +msgid "API version" +msgstr "" + +#: ./doc/glossary/glossary-terms.xml:299(para) +msgid "In OpenStack, a the API version for a project is part of the URL. For example, example.com/nova/v1/foobar." +msgstr "" + +#: ./doc/glossary/glossary-terms.xml:305(glossterm) +msgid "applet" +msgstr "" + +#: ./doc/glossary/glossary-terms.xml:307(para) +msgid "A Java program that can be embedded into a web page." +msgstr "" + +#: ./doc/glossary/glossary-terms.xml:312(glossterm) +msgid "Application Programming Interface (API)" +msgstr "" + +#: ./doc/glossary/glossary-terms.xml:315(para) +msgid "A collection of specifications used to access a service, application, or program. Includes service calls, required parameters for each call, and the expected return values." +msgstr "" + +#: ./doc/glossary/glossary-terms.xml:322(glossterm) +msgid "application server" +msgstr "" + +#: ./doc/glossary/glossary-terms.xml:324(para) +msgid "A piece of software that makes available another piece of software over a network." +msgstr "" + +#: ./doc/glossary/glossary-terms.xml:329(glossterm) +msgid "Application Service Provider (ASP)" +msgstr "" + +#: ./doc/glossary/glossary-terms.xml:331(para) +msgid "Companies that rent specialized applications that help businesses and organizations provide additional services with less cost." +msgstr "" + +#: ./doc/glossary/glossary-terms.xml:337(glossterm) +msgid "arptables" +msgstr "" + +#: ./doc/glossary/glossary-terms.xml:339(para) +msgid "Used along with iptables, ebtables, and ip6tables in nova to provide firewall services." +msgstr "" + +#: ./doc/glossary/glossary-terms.xml:345(glossterm) +msgid "associate" +msgstr "" + +#: ./doc/glossary/glossary-terms.xml:347(para) +msgid "The process associating a nova floating IP address to a fixed IP address." +msgstr "" + +#: ./doc/glossary/glossary-terms.xml:352(glossterm) +msgid "Asynchronous JavaScript and XML (AJAX)" +msgstr "" + +#: ./doc/glossary/glossary-terms.xml:355(para) +msgid "A group of interrelated web development techniques used on the client-side to create asynchronous web applications. Used extensively in horizon." +msgstr "" + +#: ./doc/glossary/glossary-terms.xml:362(glossterm) +msgid "ATA over Ethernet (AoE)" +msgstr "" + +#: ./doc/glossary/glossary-terms.xml:364(para) +msgid "A disk storage protocol tunneled within Ethernet. Currently not supported in nova." +msgstr "" + +#: ./doc/glossary/glossary-terms.xml:369(glossterm) +msgid "attach" +msgstr "" + +#: ./doc/glossary/glossary-terms.xml:371(para) +msgid "The process of connecting a VIF or vNIC to a L2 network in neutron. In the context of nova, this process connects a storage volume to an instance." +msgstr "" + +#: ./doc/glossary/glossary-terms.xml:378(glossterm) +msgid "attachment (network)" +msgstr "" + +#: ./doc/glossary/glossary-terms.xml:380(para) +msgid "Association of an interface ID to a logical port. Plugs an interface into a port." +msgstr "" + +#: ./doc/glossary/glossary-terms.xml:385(glossterm) +msgid "auditing" +msgstr "" + +#: ./doc/glossary/glossary-terms.xml:387(para) +msgid "Provided in nova through the system usage data facility." +msgstr "" + +#: ./doc/glossary/glossary-terms.xml:392(glossterm) +msgid "auditor" +msgstr "" + +#: ./doc/glossary/glossary-terms.xml:394(para) +msgid "A worker processes that verifies the integrity of swift objects, containers, and accounts. Auditors is the collective term for the swift account auditor, container auditor, and object auditor." +msgstr "" + +#: ./doc/glossary/glossary-terms.xml:402(glossterm) +msgid "Austin" +msgstr "" + +#: ./doc/glossary/glossary-terms.xml:404(para) +msgid "Project name for the initial release of OpenStack." +msgstr "" + +#: ./doc/glossary/glossary-terms.xml:409(glossterm) +msgid "auth node" +msgstr "" + +#: ./doc/glossary/glossary-terms.xml:411(para) +msgid "Alternative term for a swift authorization node." +msgstr "" + +#: ./doc/glossary/glossary-terms.xml:416(glossterm) +msgid "authentication" +msgstr "" + +#: ./doc/glossary/glossary-terms.xml:418(para) +msgid "The process that confirms that the user, process, or client is really who they say they are through private key, secret token, password, fingerprint, or similar method." +msgstr "" + +#: ./doc/glossary/glossary-terms.xml:425(glossterm) +msgid "authentication token" +msgstr "" + +#: ./doc/glossary/glossary-terms.xml:427(para) +msgid "A string of text provided to the client after authentication. Must be provided by the user or process in subsequent requests to the API endpoint." +msgstr "" + +#: ./doc/glossary/glossary-terms.xml:434(glossterm) +msgid "AuthN" +msgstr "" + +#: ./doc/glossary/glossary-terms.xml:436(para) +msgid "The keystone component that provides authentication services." +msgstr "" + +#: ./doc/glossary/glossary-terms.xml:441(glossterm) +msgid "authorization" +msgstr "" + +#: ./doc/glossary/glossary-terms.xml:443(para) +msgid "The act of verifying that a user, process, or client is authorized to perform an action, such as delete a swift object, list a swift container, start a nova VM, reset a password, and so on." +msgstr "" + +#: ./doc/glossary/glossary-terms.xml:451(glossterm) +msgid "authorization node" +msgstr "" + +#: ./doc/glossary/glossary-terms.xml:453(para) +msgid "A swift node that provides authorization services." +msgstr "" + +#: ./doc/glossary/glossary-terms.xml:458(glossterm) +msgid "AuthZ" +msgstr "" + +#: ./doc/glossary/glossary-terms.xml:460(para) +msgid "The keystone component that provides high-level authorization services." +msgstr "" + +#: ./doc/glossary/glossary-terms.xml:465(glossterm) +msgid "Auto ACK" +msgstr "" + +#: ./doc/glossary/glossary-terms.xml:467(para) +msgid "Configuration setting within RabbitMQ that enables or disables message acknowledgment. Enabled by default." +msgstr "" + +#: ./doc/glossary/glossary-terms.xml:473(glossterm) +msgid "auto declare" +msgstr "" + +#: ./doc/glossary/glossary-terms.xml:475(para) +msgid "A nova RabbitMQ setting that determines if a message exchange is automatically created when the program starts." +msgstr "" + +#: ./doc/glossary/glossary-terms.xml:481(glossterm) +msgid "availability zone" +msgstr "" + +#: ./doc/glossary/glossary-terms.xml:483(para) +msgid "An Amazon EC2 concept of an isolated area that is used for fault tolerance. Do not confuse with an OpenStack nova zone or cell." +msgstr "" + +#: ./doc/glossary/glossary-terms.xml:489(glossterm) +msgid "AWS" +msgstr "" + +#: ./doc/glossary/glossary-terms.xml:491(para) +msgid "Amazon Web Services." +msgstr "" + +#: ./doc/glossary/glossary-terms.xml:497(title) +msgid "B" +msgstr "" + +#: ./doc/glossary/glossary-terms.xml:499(glossterm) +msgid "back-end" +msgstr "" + +#: ./doc/glossary/glossary-terms.xml:501(para) +msgid "Interactions and processes that are obfuscated from the user, such as nova mounting a volume, a daemon sending data to an iSCSI target, or swift checking the integrity of an object." +msgstr "" + +#: ./doc/glossary/glossary-terms.xml:508(glossterm) +msgid "back-end catalog" +msgstr "" + +#: ./doc/glossary/glossary-terms.xml:510(para) +msgid "The storage method used by the keystone catalog service to store and retrieve information about API endpoints that are available to the client. Examples include a SQL database, LDAP database, or KVS back-end." +msgstr "" + +#: ./doc/glossary/glossary-terms.xml:518(glossterm) +msgid "back-end store" +msgstr "" + +#: ./doc/glossary/glossary-terms.xml:520(para) +msgid "The persistent data store used to save and retrieve a information for a service, such as a listing of swift objects, the current state of a nova VM, a list of user names, and so on. Method that glance uses to retrieve and store VM images. Options include swift, local file system, S3, and HTTP." +msgstr "" + +#: ./doc/glossary/glossary-terms.xml:530(glossterm) +msgid "bandwidth" +msgstr "" + +#: ./doc/glossary/glossary-terms.xml:532(para) +msgid "The amount of available data used by communication resources such as the Internet. Represents the amount of data that is used to download things or the amount of data available to download." +msgstr "" + +#: ./doc/glossary/glossary-terms.xml:540(glossterm) +msgid "bare" +msgstr "" + +#: ./doc/glossary/glossary-terms.xml:542(para) +msgid "A glance container format that indicates that no container exists for the VM image." +msgstr "" + +#: ./doc/glossary/glossary-terms.xml:547(glossterm) +msgid "base image" +msgstr "" + +#: ./doc/glossary/glossary-terms.xml:549(para) +msgid "An OpenStack-provided image." +msgstr "" + +#: ./doc/glossary/glossary-terms.xml:553(glossterm) +msgid "Bexar" +msgstr "" + +#: ./doc/glossary/glossary-terms.xml:555(para) +msgid "A grouped release of projects related to OpenStack that came out in February of 2011. It included Compute (nova) and Object Storage (swift) only." +msgstr "" + +#: ./doc/glossary/glossary-terms.xml:562(glossterm) +msgid "binary" +msgstr "" + +#: ./doc/glossary/glossary-terms.xml:564(para) +msgid "Information that consists solely of ones and zeroes, which is the language of computers." +msgstr "" + +#: ./doc/glossary/glossary-terms.xml:569(glossterm) +msgid "bit" +msgstr "" + +#: ./doc/glossary/glossary-terms.xml:571(para) +msgid "A bit is a single digit number that is in base of 2 (either a zero or one). Bandwidth usage is measured in bits-per-second." +msgstr "" + +#: ./doc/glossary/glossary-terms.xml:577(glossterm) +msgid "bit-per-second (BPS)" +msgstr "" + +#: ./doc/glossary/glossary-terms.xml:579(para) +msgid "The universal measurement of how quickly data is transferred from place to place." +msgstr "" + +#: ./doc/glossary/glossary-terms.xml:584(glossterm) +msgid "block device" +msgstr "" + +#: ./doc/glossary/glossary-terms.xml:586(para) +msgid "A device that moves data in the form of blocks. These device nodes interface the devices, such as hard disks, CD-ROM drives, flash drives, and other addressable regions of memory." +msgstr "" + +#: ./doc/glossary/glossary-terms.xml:593(glossterm) +msgid "block migration" +msgstr "" + +#: ./doc/glossary/glossary-terms.xml:595(para) +msgid "A method of VM live migration used by KVM to evacuate instances from one host to another with very little downtime during a user-initiated switch-over. Does not require shared storage. Supported by nova." +msgstr "" + +#: ./doc/glossary/glossary-terms.xml:603(glossterm) +msgid "BMC" +msgstr "" + +#: ./doc/glossary/glossary-terms.xml:605(para) +msgid "Baseboard Management Controller. The intelligence in the IPMI architecture, which is a specialized micro-controller that is embedded on the motherboard of a computer and acts as a server. Manages the interface between system management software and platform hardware." +msgstr "" + +#: ./doc/glossary/glossary-terms.xml:614(glossterm) +msgid "bootable disk image" +msgstr "" + +#: ./doc/glossary/glossary-terms.xml:616(para) +msgid "A type of VM image that exists as a single, bootable file." +msgstr "" + +#: ./doc/glossary/glossary-terms.xml:621(glossterm) +msgid "Bootstrap Protocol (BOOTP)" +msgstr "" + +#: ./doc/glossary/glossary-terms.xml:623(para) +msgid "A network protocol used by a network client to obtain an IP address from a configuration server. Provided in nova through the dnsmasq daemon when using either the FlatDHCP manager or VLAN manager network manager." +msgstr "" + +#: ./doc/glossary/glossary-terms.xml:631(glossterm) +msgid "browser" +msgstr "" + +#: ./doc/glossary/glossary-terms.xml:633(para) +msgid "Any client software that enables a computer or device to access the Internet." +msgstr "" + +#: ./doc/glossary/glossary-terms.xml:638(glossterm) +msgid "builder file" +msgstr "" + +#: ./doc/glossary/glossary-terms.xml:640(para) +msgid "Contains configuration information for a swift ring, and is used to re-configure the ring or to recreate it from scratch after a serious failure." +msgstr "" + +#: ./doc/glossary/glossary-terms.xml:647(glossterm) +msgid "button class" +msgstr "" + +#: ./doc/glossary/glossary-terms.xml:649(para) +msgid "A group of related button types within horizon. Buttons to start, stop, and suspend VMs are in one class. Buttons to associate and disassociate floating IP addresses are in another class, and so on." +msgstr "" + +#: ./doc/glossary/glossary-terms.xml:657(glossterm) +msgid "byte" +msgstr "" + +#: ./doc/glossary/glossary-terms.xml:659(para) +msgid "Set of bits that make up a single character; there are usually 8 bits to a byte." +msgstr "" + +#: ./doc/glossary/glossary-terms.xml:672(title) +msgid "C" +msgstr "" + +#: ./doc/glossary/glossary-terms.xml:674(glossterm) +msgid "CA" +msgstr "" + +#: ./doc/glossary/glossary-terms.xml:676(para) +msgid "Certificate Authority or Certification Authority. In cryptography, an entity that issues digital certificates. The digital certificate certifies the ownership of a public key by the named subject of the certificate. This enables others (relying parties) to rely upon signatures or assertions made by the private key that corresponds to the certified public key. In this model of trust relationships, a CA is a trusted third party for both the subject (owner) of the certificate and the party relying upon the certificate. CAs are characteristic of many public key infrastructure (PKI) schemes." +msgstr "" + +#: ./doc/glossary/glossary-terms.xml:692(glossterm) +msgid "cache pruner" +msgstr "" + +#: ./doc/glossary/glossary-terms.xml:694(para) +msgid "An executable program that is used to keep a glance VM image cache at or below its configured maximum size." +msgstr "" + +#: ./doc/glossary/glossary-terms.xml:700(glossterm) +msgid "Cactus" +msgstr "" + +#: ./doc/glossary/glossary-terms.xml:702(para) +msgid "An OpenStack grouped release of projects that came out in the spring of 2011. It included Compute (nova), Object Storage (swift), and the Image service (glance)." +msgstr "" + +#: ./doc/glossary/glossary-terms.xml:709(glossterm) +msgid "CALL" +msgstr "" + +#: ./doc/glossary/glossary-terms.xml:711(para) +msgid "One of the RPC primitives used by the OpenStack message queue software. Sends a message and waits for a response." +msgstr "" + +#: ./doc/glossary/glossary-terms.xml:717(glossterm) +msgid "capability" +msgstr "" + +#: ./doc/glossary/glossary-terms.xml:719(para) +msgid "Defines resources for a cell, including CPU, storage, and networking. Can apply to the specific services within a cell or a whole cell." +msgstr "" + +#: ./doc/glossary/glossary-terms.xml:725(glossterm) +msgid "capacity cache" +msgstr "" + +#: ./doc/glossary/glossary-terms.xml:727(para) +msgid "A table within the nova back-end database that contains the current workload, amount of free RAM, number of VMs running on each host. Used to determine on which VM a host starts." +msgstr "" + +#: ./doc/glossary/glossary-terms.xml:734(glossterm) +msgid "capacity updater" +msgstr "" + +#: ./doc/glossary/glossary-terms.xml:736(para) +msgid "A notification driver that monitors VM instances and updates the capacity cache as needed." +msgstr "" + +#: ./doc/glossary/glossary-terms.xml:741(glossterm) +msgid "CAST" +msgstr "" + +#: ./doc/glossary/glossary-terms.xml:743(para) +msgid "One of the RPC primitives used by the OpenStack message queue software. Sends a message and does not wait for a response." +msgstr "" + +#: ./doc/glossary/glossary-terms.xml:749(glossterm) +msgid "catalog" +msgstr "" + +#: ./doc/glossary/glossary-terms.xml:751(para) +msgid "Contains a list of available API endpoints to a user after they authenticate to keystone." +msgstr "" + +#: ./doc/glossary/glossary-terms.xml:756(glossterm) +msgid "catalog service" +msgstr "" + +#: ./doc/glossary/glossary-terms.xml:758(para) +msgid "A keystone service that provides a list of available API endpoints to a user after they authenticate to keystone." +msgstr "" + +#: ./doc/glossary/glossary-terms.xml:764(glossterm) +msgid "Ceilometer" +msgstr "" + +#: ./doc/glossary/glossary-terms.xml:766(para) +msgid "An incubated project that provides metering and billing facilities for OpenStack." +msgstr "" + +#: ./doc/glossary/glossary-terms.xml:771(glossterm) +msgid "cell" +msgstr "" + +#: ./doc/glossary/glossary-terms.xml:773(para) +msgid "Provides logical partitioning of nova resources in a child and parent relationship. Requests are passed from parent cells to child cells if the parent cannot provide the requested resource." +msgstr "" + +#: ./doc/glossary/glossary-terms.xml:781(glossterm) +msgid "cell forwarding" +msgstr "" + +#: ./doc/glossary/glossary-terms.xml:783(para) +msgid "A nova option that enables parent cells to pass resource requests to child cells if the parent cannot provide the requested resource." +msgstr "" + +#: ./doc/glossary/glossary-terms.xml:789(glossterm) +msgid "cell manager" +msgstr "" + +#: ./doc/glossary/glossary-terms.xml:791(para) +msgid "The nova component that contains a list of the current capabilities of each host within the cell and routes requests as appropriate." +msgstr "" + +#: ./doc/glossary/glossary-terms.xml:797(glossterm) +msgid "CentOS" +msgstr "" + +#: ./doc/glossary/glossary-terms.xml:799(para) ./doc/glossary/glossary-terms.xml:1288(para) ./doc/glossary/glossary-terms.xml:3242(para) ./doc/glossary/glossary-terms.xml:3669(para) ./doc/glossary/glossary-terms.xml:4232(para) +msgid "A Linux distribution that is compatible with OpenStack." +msgstr "" + +#: ./doc/glossary/glossary-terms.xml:804(glossterm) +msgid "Ceph" +msgstr "" + +#: ./doc/glossary/glossary-terms.xml:806(para) +msgid "Massively scalable distributed storage system that consists of an object store, block store, and POSIX-compatible distributed file system. Compatible with OpenStack." +msgstr "" + +#: ./doc/glossary/glossary-terms.xml:813(glossterm) +msgid "CephFS" +msgstr "" + +#: ./doc/glossary/glossary-terms.xml:815(para) +msgid "The POSIX-compliant file system provided by Ceph." +msgstr "" + +#: ./doc/glossary/glossary-terms.xml:820(glossterm) +msgid "certificate authority" +msgstr "" + +#: ./doc/glossary/glossary-terms.xml:822(para) +msgid "A simple certificate authority provided by nova for cloudpipe VPNs and VM image decryption." +msgstr "" + +#: ./doc/glossary/glossary-terms.xml:827(glossterm) +msgid "Challenge-Handshake Authentication Protocol (CHAP)" +msgstr "" + +#: ./doc/glossary/glossary-terms.xml:830(para) +msgid "An iSCSI authentication method supported by nova." +msgstr "" + +#: ./doc/glossary/glossary-terms.xml:835(glossterm) +msgid "chance scheduler" +msgstr "" + +#: ./doc/glossary/glossary-terms.xml:837(para) +msgid "A scheduling method used by nova that randomly chooses an available host from the pool." +msgstr "" + +#: ./doc/glossary/glossary-terms.xml:842(glossterm) +msgid "changes since" +msgstr "" + +#: ./doc/glossary/glossary-terms.xml:844(para) +msgid "A nova API parameter that downloads changes to the requested item since your last request, instead of downloading a new, fresh set of data and comparing it against the old data." +msgstr "" + +#: ./doc/glossary/glossary-terms.xml:852(glossterm) +msgid "Chef" +msgstr "" + +#: ./doc/glossary/glossary-terms.xml:854(para) +msgid "An operating system configuration management tool supporting OpenStack deployments." +msgstr "" + +#: ./doc/glossary/glossary-terms.xml:859(glossterm) +msgid "child cell" +msgstr "" + +#: ./doc/glossary/glossary-terms.xml:861(para) +msgid "If a requested resource such as CPU time, disk storage, or memory is not available in the parent cell, the request is forwarded to its associated child cells. If the child cell can fulfill the request, it does. Otherwise, it attempts to pass the request to any of its children." +msgstr "" + +#: ./doc/glossary/glossary-terms.xml:870(glossterm) +msgid "Cinder" +msgstr "" + +#: ./doc/glossary/glossary-terms.xml:872(para) +msgid "A core OpenStack project that maintains the object storage services for VMs." +msgstr "" + +#: ./doc/glossary/glossary-terms.xml:877(glossterm) +msgid "Cisco neutron plug-in" +msgstr "" + +#: ./doc/glossary/glossary-terms.xml:879(para) +msgid "A neutron plug-in for Cisco devices and technologies including UCS and Nexus." +msgstr "" + +#: ./doc/glossary/glossary-terms.xml:884(glossterm) +msgid "cloud architect" +msgstr "" + +#: ./doc/glossary/glossary-terms.xml:886(para) +msgid "A person who plans, designs, and oversees the creation of clouds." +msgstr "" + +#: ./doc/glossary/glossary-terms.xml:891(glossterm) +msgid "cloud computing" +msgstr "" + +#: ./doc/glossary/glossary-terms.xml:893(para) +msgid "A model that enables access to a shared pool of configurable computing resources, such as networks, servers, storage, applications, and services, that can be rapidly provisioned and released with minimal management effort or service provider interaction." +msgstr "" + +#: ./doc/glossary/glossary-terms.xml:902(glossterm) +msgid "cloud controller" +msgstr "" + +#: ./doc/glossary/glossary-terms.xml:904(para) +msgid "Collection of nova components that represent the global state of the cloud, talks to services such as keystone authentication, swift object storage, and node/storage workers through a queue." +msgstr "" + +#: ./doc/glossary/glossary-terms.xml:911(glossterm) +msgid "cloud controller node" +msgstr "" + +#: ./doc/glossary/glossary-terms.xml:913(para) +msgid "A node that runs network, volume, API, scheduler and image services. Each service may be broken out into separate nodes for scalability or availability." +msgstr "" + +#: ./doc/glossary/glossary-terms.xml:920(glossterm) +msgid "Cloud Data Management Interface (CDMI)" +msgstr "" + +#: ./doc/glossary/glossary-terms.xml:923(para) +msgid "SINA standard that defines a RESTful API for managing objects in the cloud, currently unsupported in OpenStack." +msgstr "" + +#: ./doc/glossary/glossary-terms.xml:929(glossterm) +msgid "Cloud Infrastructure Management Interface (CIMI)" +msgstr "" + +#: ./doc/glossary/glossary-terms.xml:932(para) +msgid "An in-progress specification for cloud management. Currently unsupported in OpenStack." +msgstr "" + +#: ./doc/glossary/glossary-terms.xml:938(glossterm) +msgid "cloud-init" +msgstr "" + +#: ./doc/glossary/glossary-terms.xml:940(para) +msgid "A package commonly installed in VM images that performs initialization of an instance after boot using information that it retrieves from the metadata service such as the SSH public key and user data." +msgstr "" + +#: ./doc/glossary/glossary-terms.xml:948(glossterm) +msgid "cloudadmin" +msgstr "" + +#: ./doc/glossary/glossary-terms.xml:950(para) +msgid "One of the default roles in the nova RBAC system. Grants complete system access." +msgstr "" + +#: ./doc/glossary/glossary-terms.xml:955(glossterm) +msgid "cloudpipe" +msgstr "" + +#: ./doc/glossary/glossary-terms.xml:957(para) +msgid "A service in nova used to create VPNs on a per-project basis." +msgstr "" + +#: ./doc/glossary/glossary-terms.xml:962(glossterm) +msgid "cloudpipe image" +msgstr "" + +#: ./doc/glossary/glossary-terms.xml:964(para) +msgid "A pre-made VM image that serves as a cloudpipe server. Essentially, OpenVPN running on Linux." +msgstr "" + +#: ./doc/glossary/glossary-terms.xml:970(glossterm) +msgid "CMDB" +msgstr "" + +#: ./doc/glossary/glossary-terms.xml:972(para) +msgid "Configuration Management Database." +msgstr "" + +#: ./doc/glossary/glossary-terms.xml:976(glossterm) +msgid "command filter" +msgstr "" + +#: ./doc/glossary/glossary-terms.xml:978(para) +msgid "Lists allowed commands within the nova rootwrap facility." +msgstr "" + +#: ./doc/glossary/glossary-terms.xml:983(glossterm) +msgid "community project" +msgstr "" + +#: ./doc/glossary/glossary-terms.xml:985(para) +msgid "A project that is not officially endorsed by the OpenStack Foundation. If the project is successful enough, it might be elevated to an incubated project and then to a core project, or it might be merged with the main code trunk." +msgstr "" + +#: ./doc/glossary/glossary-terms.xml:993(glossterm) +msgid "compression" +msgstr "" + +#: ./doc/glossary/glossary-terms.xml:995(para) +msgid "OpenStack supports compression at the Linux file system level but does not support compression for things such as swift objects or glance VM images." +msgstr "" + +#: ./doc/glossary/glossary-terms.xml:1002(glossterm) +msgid "Compute API" +msgstr "" + +#: ./doc/glossary/glossary-terms.xml:1004(para) +msgid "The nova-api daemon that provides access to nova services. Can communicate with other APIs, such as the Amazon EC2 API." +msgstr "" + +#: ./doc/glossary/glossary-terms.xml:1011(glossterm) +msgid "Compute API extension" +msgstr "" + +#: ./doc/glossary/glossary-terms.xml:1013(para) +msgid "Alternative term for a nova API extension." +msgstr "" + +#: ./doc/glossary/glossary-terms.xml:1018(glossterm) +msgid "compute controller" +msgstr "" + +#: ./doc/glossary/glossary-terms.xml:1020(para) +msgid "The nova component that chooses suitable hosts on which to start VM instances." +msgstr "" + +#: ./doc/glossary/glossary-terms.xml:1025(glossterm) +msgid "compute host" +msgstr "" + +#: ./doc/glossary/glossary-terms.xml:1027(para) +msgid "Physical host dedicated to running compute nodes." +msgstr "" + +#: ./doc/glossary/glossary-terms.xml:1032(glossterm) +msgid "compute node" +msgstr "" + +#: ./doc/glossary/glossary-terms.xml:1034(para) +msgid "A node that runs the nova-compute daemon, a VM instance that provides a wide range of services such as a web services and analytics." +msgstr "" + +#: ./doc/glossary/glossary-terms.xml:1040(glossterm) +msgid "compute service" +msgstr "" + +#: ./doc/glossary/glossary-terms.xml:1042(para) +msgid "Alternative term for the nova component that manages VMs." +msgstr "" + +#: ./doc/glossary/glossary-terms.xml:1047(glossterm) +msgid "compute worker" +msgstr "" + +#: ./doc/glossary/glossary-terms.xml:1049(para) +msgid "The nova component that runs on each compute node and manages the VM instance life cycle, including run, reboot, terminate, attach/detach volumes, and so on. Provided by the nova-compute daemon." +msgstr "" + +#: ./doc/glossary/glossary-terms.xml:1057(glossterm) +msgid "concatenated object" +msgstr "" + +#: ./doc/glossary/glossary-terms.xml:1059(para) +msgid "A segmented large object within swift that is put back together again and then sent to the client." +msgstr "" + +#: ./doc/glossary/glossary-terms.xml:1065(glossterm) +msgid "conductor" +msgstr "" + +#: ./doc/glossary/glossary-terms.xml:1067(para) +msgid "In nova, conductor is the process that proxies database requests from the compute process. Using conductor improves security as compute nodes don't need direct access to the database." +msgstr "" + +#: ./doc/glossary/glossary-terms.xml:1074(glossterm) +msgid "consistency window" +msgstr "" + +#: ./doc/glossary/glossary-terms.xml:1076(para) +msgid "The amount of time it takes for a new swift object to become accessible to all clients." +msgstr "" + +#: ./doc/glossary/glossary-terms.xml:1081(glossterm) +msgid "console log" +msgstr "" + +#: ./doc/glossary/glossary-terms.xml:1083(para) +msgid "Contains the output from a Linux VM console in nova." +msgstr "" + +#: ./doc/glossary/glossary-terms.xml:1088(glossterm) +msgid "container" +msgstr "" + +#: ./doc/glossary/glossary-terms.xml:1090(para) +msgid "Used to organize and store objects within swift, similar to the concept as a Linux directory but cannot be nested. Alternative term for a glance container format." +msgstr "" + +#: ./doc/glossary/glossary-terms.xml:1097(glossterm) +msgid "container auditor" +msgstr "" + +#: ./doc/glossary/glossary-terms.xml:1099(para) +msgid "Checks for missing replicas or incorrect objects in the specified swift containers through queries to the SQLite back-end database." +msgstr "" + +#: ./doc/glossary/glossary-terms.xml:1105(glossterm) +msgid "container database" +msgstr "" + +#: ./doc/glossary/glossary-terms.xml:1107(para) +msgid "A SQLite database that contains swift containers and related metadata and is accessed by the container server" +msgstr "" + +#: ./doc/glossary/glossary-terms.xml:1113(glossterm) +msgid "container format" +msgstr "" + +#: ./doc/glossary/glossary-terms.xml:1115(para) +msgid "The \"envelope\" used by glance to store a VM image and its associated metadata, such as machine state, OS disk size, and so on." +msgstr "" + +#: ./doc/glossary/glossary-terms.xml:1121(glossterm) +msgid "container server" +msgstr "" + +#: ./doc/glossary/glossary-terms.xml:1123(para) +msgid "A swift that manages containers." +msgstr "" + +#: ./doc/glossary/glossary-terms.xml:1127(glossterm) +msgid "container service" +msgstr "" + +#: ./doc/glossary/glossary-terms.xml:1129(para) +msgid "The swift component that provides container services, such as create, delete, list, and so on." +msgstr "" + +#: ./doc/glossary/glossary-terms.xml:1135(glossterm) +msgid "controller node" +msgstr "" + +#: ./doc/glossary/glossary-terms.xml:1137(para) +msgid "Alternative term for a cloud controller node." +msgstr "" + +#: ./doc/glossary/glossary-terms.xml:1142(glossterm) +msgid "core API" +msgstr "" + +#: ./doc/glossary/glossary-terms.xml:1144(para) +msgid "Depending on context, the core API is either the OpenStack API or the main API of a specific core project, such as nova, neutron, glance, and so on." +msgstr "" + +#: ./doc/glossary/glossary-terms.xml:1151(glossterm) +msgid "core project" +msgstr "" + +#: ./doc/glossary/glossary-terms.xml:1153(para) +msgid "An official OpenStack project. Currently consists of Compute (nova), Object Storage (swift), Image Service (glance), Identity (keystone), Dashboard (horizon), Networking (neutron), Block Storage (cinder), Telemetry Service (ceilometer) and Orchestration Service (heat)." +msgstr "" + +#: ./doc/glossary/glossary-terms.xml:1163(glossterm) +msgid "cost" +msgstr "" + +#: ./doc/glossary/glossary-terms.xml:1165(para) +msgid "Under the nova distributed scheduler this is calculated by looking at the capabilities of each host relative to the flavor of the VM instance being requested." +msgstr "" + +#: ./doc/glossary/glossary-terms.xml:1172(glossterm) +msgid "credentials" +msgstr "" + +#: ./doc/glossary/glossary-terms.xml:1174(para) +msgid "Data that is only known to or accessible by a user that is used to verify the user is who they say they are and presented to the server during authentication. Examples include a password, secret key, digital certificate, fingerprint, and so on." +msgstr "" + +#: ./doc/glossary/glossary-terms.xml:1183(glossterm) +msgid "Crowbar" +msgstr "" + +#: ./doc/glossary/glossary-terms.xml:1185(para) +msgid "An open source community project by Dell that aims to provide all necessary services to quickly deploy clouds." +msgstr "" + +#: ./doc/glossary/glossary-terms.xml:1191(glossterm) +msgid "current workload" +msgstr "" + +#: ./doc/glossary/glossary-terms.xml:1193(para) +msgid "An element of the nova capacity cache that is calculated based on the number of build, snapshot, migrate, and resize operations currently in progress on a given host." +msgstr "" + +#: ./doc/glossary/glossary-terms.xml:1200(glossterm) +msgid "customer" +msgstr "" + +#: ./doc/glossary/glossary-terms.xml:1202(para) +msgid "Alternative term for tenant." +msgstr "" + +#: ./doc/glossary/glossary-terms.xml:1206(glossterm) +msgid "customization module" +msgstr "" + +#: ./doc/glossary/glossary-terms.xml:1208(para) +msgid "A user-created Python module that is loaded by horizon to change the look and feel of the dashboard." +msgstr "" + +#: ./doc/glossary/glossary-terms.xml:1222(title) +msgid "D" +msgstr "" + +#: ./doc/glossary/glossary-terms.xml:1224(glossterm) +msgid "daemon" +msgstr "" + +#: ./doc/glossary/glossary-terms.xml:1226(para) +msgid "A process that runs in the background and waits for requests. May or may not listen on a TCP or UDP port. Do not confuse with a worker." +msgstr "" + +#: ./doc/glossary/glossary-terms.xml:1232(glossterm) +msgid "DAC" +msgstr "" + +#: ./doc/glossary/glossary-terms.xml:1234(para) +msgid "Discretionary access control. Governs the ability of subjects to access objects, while enabling users to make policy decisions and assign security attributes. The traditional UNIX system of users, groups, and read-write-execute permissions is an example of DAC." +msgstr "" + +#: ./doc/glossary/glossary-terms.xml:1243(glossterm) +msgid "dashboard" +msgstr "" + +#: ./doc/glossary/glossary-terms.xml:1245(para) +msgid "The web-based management interface for OpenStack. An alternative name for horizon." +msgstr "" + +#: ./doc/glossary/glossary-terms.xml:1250(glossterm) +msgid "data encryption" +msgstr "" + +#: ./doc/glossary/glossary-terms.xml:1252(para) +msgid "Both glance and nova support encrypted virtual machine (VM) images (but not instances). In-transit data encryption is supported in OpenStack using technologies such as HTTPS, SSL, TLS, SSH. swift does not support object encryption at the application level but may support storage that uses disk encryption." +msgstr "" + +#: ./doc/glossary/glossary-terms.xml:1262(glossterm) +msgid "database ID" +msgstr "" + +#: ./doc/glossary/glossary-terms.xml:1264(para) +msgid "A unique ID given to each replica of a swift database." +msgstr "" + +#: ./doc/glossary/glossary-terms.xml:1269(glossterm) +msgid "database replicator" +msgstr "" + +#: ./doc/glossary/glossary-terms.xml:1271(para) +msgid "A swift component that copies changes in the account, container, and object databases to other nodes." +msgstr "" + +#: ./doc/glossary/glossary-terms.xml:1277(glossterm) +msgid "deallocate" +msgstr "" + +#: ./doc/glossary/glossary-terms.xml:1279(para) +msgid "The process of removing the association between a floating IP address and a fixed IP address thus returning the floating IP to the address pool." +msgstr "" + +#: ./doc/glossary/glossary-terms.xml:1286(glossterm) +msgid "Debian" +msgstr "" + +#: ./doc/glossary/glossary-terms.xml:1293(glossterm) +msgid "deduplication" +msgstr "" + +#: ./doc/glossary/glossary-terms.xml:1295(para) +msgid "The process of finding duplicate data at the disk block, file, and/or object level to minimize storage use, currently unsupported within OpenStack." +msgstr "" + +#: ./doc/glossary/glossary-terms.xml:1302(glossterm) +msgid "default panel" +msgstr "" + +#: ./doc/glossary/glossary-terms.xml:1304(para) +msgid "The default panel that is displayed when a user accesses the horizon dashboard." +msgstr "" + +#: ./doc/glossary/glossary-terms.xml:1309(glossterm) +msgid "default tenant" +msgstr "" + +#: ./doc/glossary/glossary-terms.xml:1311(para) +msgid "New users are assigned to this keystone tenant if no tenant is specified when a user is created." +msgstr "" + +#: ./doc/glossary/glossary-terms.xml:1317(glossterm) +msgid "default token" +msgstr "" + +#: ./doc/glossary/glossary-terms.xml:1319(para) +msgid "A keystone token that is not associated with a specific tenant and is exchanged for a scoped token." +msgstr "" + +#: ./doc/glossary/glossary-terms.xml:1325(glossterm) +msgid "delayed delete" +msgstr "" + +#: ./doc/glossary/glossary-terms.xml:1327(para) +msgid "An option within glance so that rather than immediately delete an image, it is deleted after a pre-defined number of seconds." +msgstr "" + +#: ./doc/glossary/glossary-terms.xml:1333(glossterm) +msgid "delivery mode" +msgstr "" + +#: ./doc/glossary/glossary-terms.xml:1335(para) +msgid "Setting for the nova RabbitMQ message delivery mode, can be set to either transient or persistent." +msgstr "" + +#: ./doc/glossary/glossary-terms.xml:1341(glossterm) +msgid "deprecated auth" +msgstr "" + +#: ./doc/glossary/glossary-terms.xml:1343(para) +msgid "An option within nova that enables administrators to create and manage users through the nova-manage command as opposed to using keystone." +msgstr "" + +#: ./doc/glossary/glossary-terms.xml:1349(glossterm) +msgid "developer" +msgstr "" + +#: ./doc/glossary/glossary-terms.xml:1351(para) +msgid "One of the default roles in the nova RBAC system and is the default role assigned to a new user." +msgstr "" + +#: ./doc/glossary/glossary-terms.xml:1357(glossterm) +msgid "device" +msgstr "" + +#: ./doc/glossary/glossary-terms.xml:1359(para) +msgid "In the context of swift this refers to the underlying storage device." +msgstr "" + +#: ./doc/glossary/glossary-terms.xml:1364(glossterm) +msgid "device ID" +msgstr "" + +#: ./doc/glossary/glossary-terms.xml:1366(para) +msgid "Maps swift partitions to physical storage devices." +msgstr "" + +#: ./doc/glossary/glossary-terms.xml:1371(glossterm) +msgid "device weight" +msgstr "" + +#: ./doc/glossary/glossary-terms.xml:1373(para) +msgid "Used to distribute the partitions among swift devices. The distribution is usually proportional to the storage capacity of the device." +msgstr "" + +#: ./doc/glossary/glossary-terms.xml:1379(glossterm) +msgid "DevStack" +msgstr "" + +#: ./doc/glossary/glossary-terms.xml:1381(para) +msgid "Community project that uses shell scripts to quickly build complete OpenStack development environments." +msgstr "" + +#: ./doc/glossary/glossary-terms.xml:1387(glossterm) +msgid "DHCP" +msgstr "" + +#: ./doc/glossary/glossary-terms.xml:1389(para) +msgid "Dynamic Host Configuration Protocol. A network protocol that configures devices that are connected to a network so they can communicate on that network by using the Internet Protocol (IP). The protocol is implemented in a client-server model where DHCP clients request configuration data such as, an IP address, a default route, and one or more DNS server addresses from a DHCP server." +msgstr "" + +#: ./doc/glossary/glossary-terms.xml:1401(glossterm) +msgid "Diablo" +msgstr "" + +#: ./doc/glossary/glossary-terms.xml:1403(para) +msgid "A grouped release of projects related to OpenStack that came out in the fall of 2011, the fourth release of OpenStack. It included Compute (nova 2011.3), Object Storage (swift 1.4.3), and the Image service (glance)." +msgstr "" + +#: ./doc/glossary/glossary-terms.xml:1411(glossterm) +msgid "direct consumer" +msgstr "" + +#: ./doc/glossary/glossary-terms.xml:1413(para) +msgid "An element of the nova RabbitMQ that comes to life when a RPC call is executed. It connects to a direct exchange through a unique exclusive queue, sends the message, and terminates." +msgstr "" + +#: ./doc/glossary/glossary-terms.xml:1420(glossterm) +msgid "direct exchange" +msgstr "" + +#: ./doc/glossary/glossary-terms.xml:1422(para) +msgid "A routing table that is created within the nova RabbitMQ during RPC calls, one is created for each RPC call that is invoked." +msgstr "" + +#: ./doc/glossary/glossary-terms.xml:1428(glossterm) +msgid "direct publisher" +msgstr "" + +#: ./doc/glossary/glossary-terms.xml:1430(para) +msgid "Element of RabbitMQ that provides a response to an incoming MQ message." +msgstr "" + +#: ./doc/glossary/glossary-terms.xml:1435(glossterm) +msgid "disassociate" +msgstr "" + +#: ./doc/glossary/glossary-terms.xml:1437(para) +msgid "The process of removing the association between a floating IP address and fixed IP and thus returning the floating IP address to the address pool." +msgstr "" + +#: ./doc/glossary/glossary-terms.xml:1444(glossterm) +msgid "disk encryption" +msgstr "" + +#: ./doc/glossary/glossary-terms.xml:1446(para) +msgid "The ability to encrypt data at the file system, disk partition or whole disk level. Supported within nova VMs." +msgstr "" + +#: ./doc/glossary/glossary-terms.xml:1452(glossterm) +msgid "disk format" +msgstr "" + +#: ./doc/glossary/glossary-terms.xml:1454(para) +msgid "The underlying format that a disk image for a VM is stored as within the glance back-end store. For example, AMI, ISO, QCOW2, VMDK, and so on." +msgstr "" + +#: ./doc/glossary/glossary-terms.xml:1460(glossterm) +msgid "dispersion" +msgstr "" + +#: ./doc/glossary/glossary-terms.xml:1462(para) +msgid "In swift, tools to test and ensure dispersion of objects and containers to ensure fault tolerance." +msgstr "" + +#: ./doc/glossary/glossary-terms.xml:1468(glossterm) +msgid "Django" +msgstr "" + +#: ./doc/glossary/glossary-terms.xml:1470(para) +msgid "A web framework used extensively in horizon." +msgstr "" + +#: ./doc/glossary/glossary-terms.xml:1475(glossterm) +msgid "DNS" +msgstr "" + +#: ./doc/glossary/glossary-terms.xml:1477(para) +msgid "Domain Name Server. A hierarchical and distributed naming system for computers, services, and resources connected to the Internet or a private network. Associates a human-friendly names to IP addresses." +msgstr "" + +#: ./doc/glossary/glossary-terms.xml:1485(glossterm) +msgid "DNS record" +msgstr "" + +#: ./doc/glossary/glossary-terms.xml:1487(para) +msgid "A record that specifies information about a particular domain and belongs to the domain." +msgstr "" + +#: ./doc/glossary/glossary-terms.xml:1493(glossterm) +msgid "dnsmasq" +msgstr "" + +#: ./doc/glossary/glossary-terms.xml:1495(para) +msgid "Daemon that provides DNS, DHCP, BOOTP, and TFTP services, used by the nova VLAN manager and FlatDHCP manager." +msgstr "" + +#: ./doc/glossary/glossary-terms.xml:1501(glossterm) +msgid "domain" +msgstr "" + +#: ./doc/glossary/glossary-terms.xml:1503(para) +msgid "Separates a web site from other sites. Often, the domain name has two or more parts that are separated by dots. For example, yahoo.com, usa.gov, Harvard.edu, or mail.yahoo.com." +msgstr "" + +#: ./doc/glossary/glossary-terms.xml:1507(para) +msgid "A domain is an entity or container of all DNS-related information containing one or more records." +msgstr "" + +#: ./doc/glossary/glossary-terms.xml:1513(glossterm) +msgid "Domain Name Service (DNS)" +msgstr "" + +#: ./doc/glossary/glossary-terms.xml:1515(para) +msgid "In nova, the support that enables associating DNS entries with floating IP addresses, nodes, or cells so host names are consistent across reboots." +msgstr "" + +#: ./doc/glossary/glossary-terms.xml:1522(glossterm) +msgid "Domain Name System (DNS)" +msgstr "" + +#: ./doc/glossary/glossary-terms.xml:1524(para) +msgid "A system by which Internet domain name-to-address and address-to-name resolutions are determined." +msgstr "" + +#: ./doc/glossary/glossary-terms.xml:1527(para) +msgid "DNS helps navigate the Internet by translating the IP address into an address that is easier to remember For example, translating 111.111.111.1 into www.yahoo.com." +msgstr "" + +#: ./doc/glossary/glossary-terms.xml:1531(para) +msgid "All domains and their components, such as mail servers, utilize DNS to resolve to the appropriate locations. DNS servers are usually set up in a master-slave relationship such that failure of the master invokes the slave. DNS servers might also be clustered or replicated such that changes made to one DNS server are automatically propagated to other active servers." +msgstr "" + +#: ./doc/glossary/glossary-terms.xml:1542(glossterm) +msgid "download" +msgstr "" + +#: ./doc/glossary/glossary-terms.xml:1544(para) +msgid "The transfer of data, usually in the form of files, from one computer to another." +msgstr "" + +#: ./doc/glossary/glossary-terms.xml:1549(glossterm) +msgid "DRTM" +msgstr "" + +#: ./doc/glossary/glossary-terms.xml:1551(para) +msgid "Dynamic root of trust measurement." +msgstr "" + +#: ./doc/glossary/glossary-terms.xml:1555(glossterm) +msgid "durable exchange" +msgstr "" + +#: ./doc/glossary/glossary-terms.xml:1557(para) +msgid "The nova RabbitMQ message exchange that remains active when the server restarts." +msgstr "" + +#: ./doc/glossary/glossary-terms.xml:1562(glossterm) +msgid "durable queue" +msgstr "" + +#: ./doc/glossary/glossary-terms.xml:1564(para) +msgid "A nova RabbitMQ message queue that remains active when the server restarts." +msgstr "" + +#: ./doc/glossary/glossary-terms.xml:1569(glossterm) +msgid "Dynamic Host Configuration Protocol (DHCP)" +msgstr "" + +#: ./doc/glossary/glossary-terms.xml:1572(para) +msgid "A method to automatically configure networking for a host at boot time. Provided by both neutron and nova." +msgstr "" + +#: ./doc/glossary/glossary-terms.xml:1578(glossterm) +msgid "Dynamic HyperText Markup Language (DHTML)" +msgstr "" + +#: ./doc/glossary/glossary-terms.xml:1581(para) +msgid "Pages that use HTML, JavaScript, and CCS to enable users to interact with a web page or show simple animation." +msgstr "" + +#: ./doc/glossary/glossary-terms.xml:1589(title) +msgid "E" +msgstr "" + +#: ./doc/glossary/glossary-terms.xml:1591(glossterm) +msgid "EBS boot volume" +msgstr "" + +#: ./doc/glossary/glossary-terms.xml:1593(para) +msgid "An Amazon EBS storage volume that contains a bootable VM image, currently unsupported in OpenStack." +msgstr "" + +#: ./doc/glossary/glossary-terms.xml:1599(glossterm) +msgid "ebtables" +msgstr "" + +#: ./doc/glossary/glossary-terms.xml:1601(para) +msgid "Used in nova along with arptables, iptables, and ip6tables to create firewalls and to ensure isolation of network communications." +msgstr "" + +#: ./doc/glossary/glossary-terms.xml:1607(glossterm) +msgid "EC2" +msgstr "" + +#: ./doc/glossary/glossary-terms.xml:1609(para) +msgid "The Amazon commercial compute product, similar to nova." +msgstr "" + +#: ./doc/glossary/glossary-terms.xml:1614(glossterm) +msgid "EC2 access key" +msgstr "" + +#: ./doc/glossary/glossary-terms.xml:1616(para) +msgid "Used along with an EC2 secret key to access the nova EC2 API." +msgstr "" + +#: ./doc/glossary/glossary-terms.xml:1621(glossterm) +msgid "EC2 API" +msgstr "" + +#: ./doc/glossary/glossary-terms.xml:1623(para) +msgid "OpenStack supports accessing the Amazon EC2 API through nova." +msgstr "" + +#: ./doc/glossary/glossary-terms.xml:1628(glossterm) +msgid "EC2 Compatibility API" +msgstr "" + +#: ./doc/glossary/glossary-terms.xml:1630(para) +msgid "A nova component that enables OpenStack to communicate with Amazon EC2." +msgstr "" + +#: ./doc/glossary/glossary-terms.xml:1635(glossterm) +msgid "EC2 secret key" +msgstr "" + +#: ./doc/glossary/glossary-terms.xml:1637(para) +msgid "Used along with an EC2 access key when communicating with the nova EC2 API, is used to digitally sign each request." +msgstr "" + +#: ./doc/glossary/glossary-terms.xml:1643(glossterm) +msgid "Elastic Block Storage (EBS)" +msgstr "" + +#: ./doc/glossary/glossary-terms.xml:1645(para) +msgid "The Amazon commercial block storage product." +msgstr "" + +#: ./doc/glossary/glossary-terms.xml:1650(glossterm) +msgid "encryption" +msgstr "" + +#: ./doc/glossary/glossary-terms.xml:1652(para) +msgid "OpenStack supports encryption technologies such as HTTPS, SSH, SSL, TLS, digital certificates, and data encryption." +msgstr "" + +#: ./doc/glossary/glossary-terms.xml:1658(glossterm) +msgid "endpoint" +msgstr "" + +#: ./doc/glossary/glossary-terms.xml:1660(para) +msgid "See API endpoint." +msgstr "" + +#: ./doc/glossary/glossary-terms.xml:1664(glossterm) +msgid "endpoint registry" +msgstr "" + +#: ./doc/glossary/glossary-terms.xml:1666(para) +msgid "Alternative term for a keystone catalog." +msgstr "" + +#: ./doc/glossary/glossary-terms.xml:1670(glossterm) +msgid "endpoint template" +msgstr "" + +#: ./doc/glossary/glossary-terms.xml:1672(para) +msgid "A list of URL and port number endpoints that indicate where a service, such as object storage, compute, identity, and so on, can be accessed." +msgstr "" + +#: ./doc/glossary/glossary-terms.xml:1679(glossterm) +msgid "entity" +msgstr "" + +#: ./doc/glossary/glossary-terms.xml:1681(para) +msgid "Any piece of hardware or software that wants to connect to the network services provided by neutron, the Network Connectivity service. An entity can make use of neutron by implementing a VIF." +msgstr "" + +#: ./doc/glossary/glossary-terms.xml:1689(glossterm) +msgid "ephemeral image" +msgstr "" + +#: ./doc/glossary/glossary-terms.xml:1691(para) +msgid "A VM image that does not save changes made to its volumes and reverts them to their original state after the instance is terminated." +msgstr "" + +#: ./doc/glossary/glossary-terms.xml:1697(glossterm) +msgid "ephemeral volume" +msgstr "" + +#: ./doc/glossary/glossary-terms.xml:1699(para) +msgid "Volume that does not save the changes made to it and reverts to its original state when the current user relinquishes control." +msgstr "" + +#: ./doc/glossary/glossary-terms.xml:1705(glossterm) +msgid "Essex" +msgstr "" + +#: ./doc/glossary/glossary-terms.xml:1707(para) +msgid "A grouped release of projects related to OpenStack that came out in April 2012, the fifth release of OpenStack. It included Compute (nova 2012.1), Object Storage (swift 1.4.8), Image (glance), Identity (keystone), and Dashboard (horizon)." +msgstr "" + +#: ./doc/glossary/glossary-terms.xml:1716(glossterm) +msgid "ESX" +msgstr "" + +#: ./doc/glossary/glossary-terms.xml:1718(para) ./doc/glossary/glossary-terms.xml:1724(para) ./doc/glossary/glossary-terms.xml:2614(para) ./doc/glossary/glossary-terms.xml:2682(para) ./doc/glossary/glossary-terms.xml:4508(para) ./doc/glossary/glossary-terms.xml:4627(para) ./doc/glossary/glossary-terms.xml:4762(para) ./doc/glossary/glossary-terms.xml:4827(para) ./doc/glossary/glossary-terms.xml:4841(para) +msgid "An OpenStack-supported hypervisor." +msgstr "" + +#: ./doc/glossary/glossary-terms.xml:1722(glossterm) +msgid "ESXi" +msgstr "" + +#: ./doc/glossary/glossary-terms.xml:1728(glossterm) +msgid "ETag" +msgstr "" + +#: ./doc/glossary/glossary-terms.xml:1730(para) +msgid "MD5 hash of an object within swift, used to ensure data integrity." +msgstr "" + +#: ./doc/glossary/glossary-terms.xml:1735(glossterm) +msgid "euca2ools" +msgstr "" + +#: ./doc/glossary/glossary-terms.xml:1737(para) +msgid "A collection of command line tools for administering VMs, most are compatible with OpenStack." +msgstr "" + +#: ./doc/glossary/glossary-terms.xml:1743(glossterm) +msgid "Eucalyptus Kernel Image (EKI)" +msgstr "" + +#: ./doc/glossary/glossary-terms.xml:1745(para) +msgid "Used along with an ERI to create an EMI." +msgstr "" + +#: ./doc/glossary/glossary-terms.xml:1749(glossterm) +msgid "Eucalyptus Machine Image (EMI)" +msgstr "" + +#: ./doc/glossary/glossary-terms.xml:1751(para) +msgid "VM image container format supported by glance." +msgstr "" + +#: ./doc/glossary/glossary-terms.xml:1756(glossterm) +msgid "Eucalyptus Ramdisk Image (ERI)" +msgstr "" + +#: ./doc/glossary/glossary-terms.xml:1758(para) +msgid "Used along with an EKI to create an EMI." +msgstr "" + +#: ./doc/glossary/glossary-terms.xml:1762(glossterm) +msgid "evacuate" +msgstr "" + +#: ./doc/glossary/glossary-terms.xml:1764(para) +msgid "The process of migrating one or all virtual machine (VM) instances from one host to another, compatible with both shared storage live migration and block migration." +msgstr "" + +#: ./doc/glossary/glossary-terms.xml:1771(glossterm) +msgid "exchange" +msgstr "" + +#: ./doc/glossary/glossary-terms.xml:1773(para) +msgid "Alternative term for a RabbitMQ message exchange." +msgstr "" + +#: ./doc/glossary/glossary-terms.xml:1778(glossterm) +msgid "exchange type" +msgstr "" + +#: ./doc/glossary/glossary-terms.xml:1780(para) +msgid "A routing algorithm in the nova RabbitMQ." +msgstr "" + +#: ./doc/glossary/glossary-terms.xml:1784(glossterm) +msgid "exclusive queue" +msgstr "" + +#: ./doc/glossary/glossary-terms.xml:1786(para) +msgid "Connected to by a direct consumer in RabbitMQ / nova, the message can only be consumed by the current connection." +msgstr "" + +#: ./doc/glossary/glossary-terms.xml:1792(glossterm) +msgid "extended attributes (xattrs)" +msgstr "" + +#: ./doc/glossary/glossary-terms.xml:1794(para) +msgid "File system option that enables storage of additional information beyond owner, group, permissions, modification time, and so on. The underlying swift file system must support extended attributes." +msgstr "" + +#: ./doc/glossary/glossary-terms.xml:1802(glossterm) +msgid "extension" +msgstr "" + +#: ./doc/glossary/glossary-terms.xml:1804(para) +msgid "Alternative term for a nova API extension or plug-in. In the context of keystone this is a call that is specific to the implementation, such as adding support for OpenID." +msgstr "" + +#: ./doc/glossary/glossary-terms.xml:1811(glossterm) +msgid "extra specs" +msgstr "" + +#: ./doc/glossary/glossary-terms.xml:1813(para) +msgid "Specifies additional requirements when nova determines where to start a new instance. Examples include a minimum amount of network bandwidth or a GPU." +msgstr "" + +#: ./doc/glossary/glossary-terms.xml:1822(title) +msgid "F" +msgstr "" + +#: ./doc/glossary/glossary-terms.xml:1824(glossterm) +msgid "FakeLDAP" +msgstr "" + +#: ./doc/glossary/glossary-terms.xml:1826(para) +msgid "An easy method to create a local LDAP directory for testing keystone and nova. Requires Redis." +msgstr "" + +#: ./doc/glossary/glossary-terms.xml:1832(glossterm) +msgid "fan-out exchange" +msgstr "" + +#: ./doc/glossary/glossary-terms.xml:1834(para) +msgid "Within RabbitMQ and nova it is the messaging interface that is used by the scheduler service to receive capability messages from the compute, volume, and network nodes." +msgstr "" + +#: ./doc/glossary/glossary-terms.xml:1841(glossterm) +msgid "Fedora" +msgstr "" + +#: ./doc/glossary/glossary-terms.xml:1843(para) +msgid "A Linux distribution compatible with OpenStack." +msgstr "" + +#: ./doc/glossary/glossary-terms.xml:1848(glossterm) +msgid "Fibre Channel" +msgstr "" + +#: ./doc/glossary/glossary-terms.xml:1850(para) +msgid "Storage protocol similar in concept to TCP/IP, encapsulates SCSI commands and data." +msgstr "" + +#: ./doc/glossary/glossary-terms.xml:1855(glossterm) +msgid "Fibre Channel over Ethernet (FCoE)" +msgstr "" + +#: ./doc/glossary/glossary-terms.xml:1857(para) +msgid "The fibre channel protocol tunneled within Ethernet." +msgstr "" + +#: ./doc/glossary/glossary-terms.xml:1862(glossterm) +msgid "fill-first scheduler" +msgstr "" + +#: ./doc/glossary/glossary-terms.xml:1864(para) +msgid "The nova scheduling method that attempts to fill a host with VMs rather than starting new VMs on a variety of hosts." +msgstr "" + +#: ./doc/glossary/glossary-terms.xml:1870(glossterm) +msgid "filter" +msgstr "" + +#: ./doc/glossary/glossary-terms.xml:1872(para) +msgid "The step in the nova scheduling process when hosts that cannot run VMs are eliminated and not chosen." +msgstr "" + +#: ./doc/glossary/glossary-terms.xml:1878(glossterm) +msgid "firewall" +msgstr "" + +#: ./doc/glossary/glossary-terms.xml:1880(para) +msgid "Used to restrict communications between hosts and/or nodes, implemented in nova using iptables, arptables, ip6tables and etables." +msgstr "" + +#: ./doc/glossary/glossary-terms.xml:1886(glossterm) +msgid "fixed IP address" +msgstr "" + +#: ./doc/glossary/glossary-terms.xml:1888(para) +msgid "An IP address that is associated with the same instance each time that instance boots, generally not accessible to end users or the public internet, used for management of the instance." +msgstr "" + +#: ./doc/glossary/glossary-terms.xml:1896(glossterm) +msgid "Flat Manager" +msgstr "" + +#: ./doc/glossary/glossary-terms.xml:1898(para) +msgid "The nova component that gives IP addresses to authorized nodes and assumes DHCP, DNS, and routing configuration and services are provided by something else." +msgstr "" + +#: ./doc/glossary/glossary-terms.xml:1905(glossterm) +msgid "flat mode injection" +msgstr "" + +#: ./doc/glossary/glossary-terms.xml:1907(para) +msgid "A nova networking method where the OS network configuration information is injected into the VM image before the instance starts." +msgstr "" + +#: ./doc/glossary/glossary-terms.xml:1913(glossterm) +msgid "flat network" +msgstr "" + +#: ./doc/glossary/glossary-terms.xml:1915(para) +msgid "The Network Controller provides virtual networks to enable compute servers to interact with each other and with the public network. All machines must have a public and private network interface. A flat network is a private network interface, which is controlled by the flat_interface option with flat managers." +msgstr "" + +#: ./doc/glossary/glossary-terms.xml:1925(glossterm) +msgid "FlatDHCP Manager" +msgstr "" + +#: ./doc/glossary/glossary-terms.xml:1927(para) +msgid "The nova component that provides dnsmasq (DHCP, DNS, BOOTP, TFTP) and radvd (routing) services." +msgstr "" + +#: ./doc/glossary/glossary-terms.xml:1933(glossterm) +msgid "flavor" +msgstr "" + +#: ./doc/glossary/glossary-terms.xml:1935(para) +msgid "Alternative term for a VM instance type." +msgstr "" + +#: ./doc/glossary/glossary-terms.xml:1939(glossterm) +msgid "flavor ID" +msgstr "" + +#: ./doc/glossary/glossary-terms.xml:1941(para) +msgid "UUID for each nova or glance VM flavor or instance type." +msgstr "" + +#: ./doc/glossary/glossary-terms.xml:1946(glossterm) +msgid "floating IP address" +msgstr "" + +#: ./doc/glossary/glossary-terms.xml:1948(para) +msgid "An IP address that a nova project can associate with a VM so the instance has the same public IP address each time that it boots. You create a pool of floating IP addresses and assign them to instances as they are launched to maintain a consistent IP address for maintaining DNS assignment." +msgstr "" + +#: ./doc/glossary/glossary-terms.xml:1958(glossterm) +msgid "Folsom" +msgstr "" + +#: ./doc/glossary/glossary-terms.xml:1960(para) +msgid "A grouped release of projects related to OpenStack that came out in the fall of 2012, the sixth release of OpenStack. It includes Compute (nova), Object Storage (swift), Identity (keystone), Networking (neutron), Image service (glance) and Volumes or Block Storage (cinder)." +msgstr "" + +#: ./doc/glossary/glossary-terms.xml:1970(glossterm) +msgid "FormPost" +msgstr "" + +#: ./doc/glossary/glossary-terms.xml:1972(para) +msgid "swift middleware that uploads (posts) an image through a form on a web page." +msgstr "" + +#: ./doc/glossary/glossary-terms.xml:1978(glossterm) +msgid "front-end" +msgstr "" + +#: ./doc/glossary/glossary-terms.xml:1980(para) +msgid "The point where a user interacts with a service, can be an API endpoint, the horizon dashboard, or a command line tool." +msgstr "" + +#: ./doc/glossary/glossary-terms.xml:1994(title) +msgid "G" +msgstr "" + +#: ./doc/glossary/glossary-terms.xml:1996(glossterm) +msgid "gateway" +msgstr "" + +#: ./doc/glossary/glossary-terms.xml:1998(para) +msgid "Hardware or software that translates between two different protocols." +msgstr "" + +#: ./doc/glossary/glossary-terms.xml:2003(glossterm) +msgid "Glance" +msgstr "" + +#: ./doc/glossary/glossary-terms.xml:2005(para) +msgid "A core project that provides the OpenStack Image Service." +msgstr "" + +#: ./doc/glossary/glossary-terms.xml:2010(glossterm) +msgid "glance API server" +msgstr "" + +#: ./doc/glossary/glossary-terms.xml:2012(para) +msgid "Processes client requests for VMs, updates glance metadata on the registry server, and communicates with the store adapter to upload VM images from the back-end store." +msgstr "" + +#: ./doc/glossary/glossary-terms.xml:2019(glossterm) +msgid "glance registry" +msgstr "" + +#: ./doc/glossary/glossary-terms.xml:2021(para) ./doc/glossary/glossary-terms.xml:3691(para) +msgid "Alternative term for the glance image registry." +msgstr "" + +#: ./doc/glossary/glossary-terms.xml:2026(glossterm) +msgid "global endpoint template" +msgstr "" + +#: ./doc/glossary/glossary-terms.xml:2028(para) +msgid "The keystone endpoint template that contains services available to all tenants." +msgstr "" + +#: ./doc/glossary/glossary-terms.xml:2033(glossterm) +msgid "GlusterFS" +msgstr "" + +#: ./doc/glossary/glossary-terms.xml:2035(para) +msgid "A file system designed to aggregate NAS hosts, compatible with OpenStack." +msgstr "" + +#: ./doc/glossary/glossary-terms.xml:2040(glossterm) +msgid "golden image" +msgstr "" + +#: ./doc/glossary/glossary-terms.xml:2042(para) +msgid "A method of operating system installation where a finalized disk image is created and then used by all nodes without modification." +msgstr "" + +#: ./doc/glossary/glossary-terms.xml:2048(glossterm) +msgid "Graphic Interchange Format (GIF)" +msgstr "" + +#: ./doc/glossary/glossary-terms.xml:2050(para) +msgid "A type of image file that is commonly used for animated images on web pages." +msgstr "" + +#: ./doc/glossary/glossary-terms.xml:2055(glossterm) +msgid "Graphics Processing Unit (GPU)" +msgstr "" + +#: ./doc/glossary/glossary-terms.xml:2057(para) +msgid "Choosing a host based on the existence of a GPU is currently unsupported in OpenStack." +msgstr "" + +#: ./doc/glossary/glossary-terms.xml:2062(glossterm) +msgid "Green Threads" +msgstr "" + +#: ./doc/glossary/glossary-terms.xml:2064(para) +msgid "The cooperative threading model used by Python, reduces race conditions, and only context switches when specific library calls are made. Each OpenStack service is its own thread." +msgstr "" + +#: ./doc/glossary/glossary-terms.xml:2071(glossterm) +msgid "Grizzly" +msgstr "" + +#: ./doc/glossary/glossary-terms.xml:2073(para) +msgid "Project name for the seventh release of OpenStack." +msgstr "" + +#: ./doc/glossary/glossary-terms.xml:2078(glossterm) +msgid "guest OS" +msgstr "" + +#: ./doc/glossary/glossary-terms.xml:2080(para) +msgid "An operating system instance running under the control of a hypervisor." +msgstr "" + +#: ./doc/glossary/glossary-terms.xml:2087(title) +msgid "H" +msgstr "" + +#: ./doc/glossary/glossary-terms.xml:2089(glossterm) +msgid "Hadoop" +msgstr "" + +#: ./doc/glossary/glossary-terms.xml:2091(para) +msgid "Apache Hadoop is an open-source software framework that supports data-intensive distributed applications." +msgstr "" + +#: ./doc/glossary/glossary-terms.xml:2097(glossterm) +msgid "handover" +msgstr "" + +#: ./doc/glossary/glossary-terms.xml:2099(para) +msgid "An object state in swift where a new replica of the object is automatically created due to a drive failure." +msgstr "" + +#: ./doc/glossary/glossary-terms.xml:2105(glossterm) +msgid "hard reboot" +msgstr "" + +#: ./doc/glossary/glossary-terms.xml:2107(para) +msgid "A type of reboot where a physical or virtual power button is pressed as opposed to a graceful, proper shutdown of the operating system." +msgstr "" + +#: ./doc/glossary/glossary-terms.xml:2113(glossterm) +msgid "Havana" +msgstr "" + +#: ./doc/glossary/glossary-terms.xml:2115(para) +msgid "Project name for the eighth release of OpenStack." +msgstr "" + +#: ./doc/glossary/glossary-terms.xml:2120(glossterm) +msgid "Heat" +msgstr "" + +#: ./doc/glossary/glossary-terms.xml:2122(para) +msgid "An integrated project that aims to orchestrate multiple cloud applications for OpenStack." +msgstr "" + +#: ./doc/glossary/glossary-terms.xml:2127(glossterm) +msgid "Horizon" +msgstr "" + +#: ./doc/glossary/glossary-terms.xml:2129(para) +msgid "OpenStack project that provides a dashboard, which is a web interface." +msgstr "" + +#: ./doc/glossary/glossary-terms.xml:2134(glossterm) +msgid "horizon plug-in" +msgstr "" + +#: ./doc/glossary/glossary-terms.xml:2136(para) +msgid "A plug-in for the OpenStack dashboard (horizon)." +msgstr "" + +#: ./doc/glossary/glossary-terms.xml:2141(glossterm) +msgid "host" +msgstr "" + +#: ./doc/glossary/glossary-terms.xml:2143(para) +msgid "A physical computer, not a VM instance (node)." +msgstr "" + +#: ./doc/glossary/glossary-terms.xml:2148(glossterm) +msgid "host aggregate" +msgstr "" + +#: ./doc/glossary/glossary-terms.xml:2150(para) +msgid "A method to further subdivide availability zones into hypervisor pools, a collection of common hosts." +msgstr "" + +#: ./doc/glossary/glossary-terms.xml:2156(glossterm) +msgid "Host Bus Adapter (HBA)" +msgstr "" + +#: ./doc/glossary/glossary-terms.xml:2158(para) +msgid "Device plugged into a PCI slot such as a fibre channel or network card." +msgstr "" + +#: ./doc/glossary/glossary-terms.xml:2163(glossterm) +msgid "HTTP" +msgstr "" + +#: ./doc/glossary/glossary-terms.xml:2165(para) +msgid "Hypertext Transfer Protocol. HTTP is an application protocol for distributed, collaborative, hypermedia information systems. It is the foundation of data communication for the World Wide Web. Hypertext is structured text that uses logical links (hyper links) between nodes containing text. HTTP is the protocol to exchange or transfer hypertext." +msgstr "" + +#: ./doc/glossary/glossary-terms.xml:2176(glossterm) +msgid "HTTPS" +msgstr "" + +#: ./doc/glossary/glossary-terms.xml:2178(para) +msgid "Hypertext Transfer Protocol Secure (HTTPS) is a communications protocol for secure communication over a computer network, with especially wide deployment on the Internet. Technically, it is not a protocol in and of itself; rather, it is the result of simply layering the Hypertext Transfer Protocol (HTTP) on top of the SSL/TLS protocol, thus adding the security capabilities of SSL/TLS to standard HTTP communications." +msgstr "" + +#: ./doc/glossary/glossary-terms.xml:2191(glossterm) +msgid "Hyper-V" +msgstr "" + +#: ./doc/glossary/glossary-terms.xml:2193(para) +msgid "One of the hypervisors supported by OpenStack." +msgstr "" + +#: ./doc/glossary/glossary-terms.xml:2198(glossterm) +msgid "hyper link" +msgstr "" + +#: ./doc/glossary/glossary-terms.xml:2200(para) +msgid "Any kind of text that contains a link to some other site, commonly found in documents where clicking on a word or words opens up a different web site." +msgstr "" + +#: ./doc/glossary/glossary-terms.xml:2207(glossterm) +msgid "HyperText Transfer Protocol (HTTP)" +msgstr "" + +#: ./doc/glossary/glossary-terms.xml:2209(para) +msgid "The protocol that tells browsers where to go to find information." +msgstr "" + +#: ./doc/glossary/glossary-terms.xml:2214(glossterm) +msgid "Hypertext Transfer Protocol Secure (HTTPS)" +msgstr "" + +#: ./doc/glossary/glossary-terms.xml:2217(para) +msgid "Encrypted HTTP communications using SSL or TLS, most OpenStack API endpoints and many inter-component communications support HTTPS communication." +msgstr "" + +#: ./doc/glossary/glossary-terms.xml:2224(glossterm) +msgid "hypervisor" +msgstr "" + +#: ./doc/glossary/glossary-terms.xml:2226(para) +msgid "Software that arbitrates and controls VM access to the actual underlying hardware." +msgstr "" + +#: ./doc/glossary/glossary-terms.xml:2231(glossterm) +msgid "hypervisor pool" +msgstr "" + +#: ./doc/glossary/glossary-terms.xml:2233(para) +msgid "A collection of hypervisors grouped together through host aggregates." +msgstr "" + +#: ./doc/glossary/glossary-terms.xml:2246(title) +msgid "I" +msgstr "" + +#: ./doc/glossary/glossary-terms.xml:2248(glossterm) +msgid "IaaS" +msgstr "" + +#: ./doc/glossary/glossary-terms.xml:2250(para) +msgid "Infrastructure as a Service. IaaS is a provision model in which an organization outsources the equipment used to support operations, including storage, hardware, servers and networking components. The service provider owns the equipment and is responsible for housing, running and maintaining it. The client typically pays on a per-use basis. IaaS is a model for providing cloud services." +msgstr "" + +#: ./doc/glossary/glossary-terms.xml:2262(glossterm) +msgid "Icehouse" +msgstr "" + +#: ./doc/glossary/glossary-terms.xml:2264(para) +msgid "Project name for the ninth release of OpenStack." +msgstr "" + +#: ./doc/glossary/glossary-terms.xml:2268(glossterm) +msgid "ID number" +msgstr "" + +#: ./doc/glossary/glossary-terms.xml:2270(para) +msgid "Unique numeric ID associated with each user in keystone, conceptually similar to a Linux or LDAP UID." +msgstr "" + +#: ./doc/glossary/glossary-terms.xml:2276(glossterm) +msgid "Identity API" +msgstr "" + +#: ./doc/glossary/glossary-terms.xml:2278(para) +msgid "Alternative term for the Identity Service API." +msgstr "" + +#: ./doc/glossary/glossary-terms.xml:2283(glossterm) +msgid "Identity back-end" +msgstr "" + +#: ./doc/glossary/glossary-terms.xml:2285(para) +msgid "The source used by keystone to retrieve user information an OpenLDAP server for example." +msgstr "" + +#: ./doc/glossary/glossary-terms.xml:2290(glossterm) +msgid "Identity Service" +msgstr "" + +#: ./doc/glossary/glossary-terms.xml:2292(para) +msgid "The identity service provided by the keystone project." +msgstr "" + +#: ./doc/glossary/glossary-terms.xml:2297(glossterm) +msgid "Identity Service API" +msgstr "" + +#: ./doc/glossary/glossary-terms.xml:2299(para) +msgid "The API used to access the OpenStack Identity Service provided through keystone." +msgstr "" + +#: ./doc/glossary/glossary-terms.xml:2304(glossterm) +msgid "IDS" +msgstr "" + +#: ./doc/glossary/glossary-terms.xml:2306(para) +msgid "Intrusion Detection System" +msgstr "" + +#: ./doc/glossary/glossary-terms.xml:2311(glossterm) +msgid "image" +msgstr "" + +#: ./doc/glossary/glossary-terms.xml:2313(para) +msgid "A collection of files for a specific operating system (OS) that you use to create or rebuild a server. OpenStack provides pre-built images. You can also create custom images, or snapshots, from servers that you have launched. Custom images can be used for data backups or as \"gold\" images for additional servers." +msgstr "" + +#: ./doc/glossary/glossary-terms.xml:2323(glossterm) +msgid "Image API" +msgstr "" + +#: ./doc/glossary/glossary-terms.xml:2325(para) +msgid "The glance API endpoint for management of VM images." +msgstr "" + +#: ./doc/glossary/glossary-terms.xml:2330(glossterm) +msgid "image cache" +msgstr "" + +#: ./doc/glossary/glossary-terms.xml:2332(para) +msgid "Used by glance to obtain images on the local host rather than re-downloading them from the image server each time one is requested." +msgstr "" + +#: ./doc/glossary/glossary-terms.xml:2339(glossterm) +msgid "image ID" +msgstr "" + +#: ./doc/glossary/glossary-terms.xml:2341(para) +msgid "Combination of URI and UUID used to access glance VM images through the image API." +msgstr "" + +#: ./doc/glossary/glossary-terms.xml:2346(glossterm) +msgid "image membership" +msgstr "" + +#: ./doc/glossary/glossary-terms.xml:2348(para) ./doc/glossary/glossary-terms.xml:2781(para) +msgid "A list of tenants that can access a given VM image within glance." +msgstr "" + +#: ./doc/glossary/glossary-terms.xml:2353(glossterm) +msgid "image owner" +msgstr "" + +#: ./doc/glossary/glossary-terms.xml:2355(para) +msgid "The keystone tenant who owns a glance virtual machine image." +msgstr "" + +#: ./doc/glossary/glossary-terms.xml:2360(glossterm) +msgid "image registry" +msgstr "" + +#: ./doc/glossary/glossary-terms.xml:2362(para) +msgid "A list of VM images that are available through glance." +msgstr "" + +#: ./doc/glossary/glossary-terms.xml:2367(glossterm) +msgid "Image Service API" +msgstr "" + +#: ./doc/glossary/glossary-terms.xml:2369(para) +msgid "Alternative name for the glance image API." +msgstr "" + +#: ./doc/glossary/glossary-terms.xml:2374(glossterm) +msgid "image status" +msgstr "" + +#: ./doc/glossary/glossary-terms.xml:2376(para) +msgid "The current status of a VM image in glance, not to be confused with the status of a running instance." +msgstr "" + +#: ./doc/glossary/glossary-terms.xml:2382(glossterm) +msgid "image store" +msgstr "" + +#: ./doc/glossary/glossary-terms.xml:2384(para) +msgid "The back-end store used by glance to store VM images, options include swift, local file system, S3, or HTTP." +msgstr "" + +#: ./doc/glossary/glossary-terms.xml:2390(glossterm) +msgid "image UUID" +msgstr "" + +#: ./doc/glossary/glossary-terms.xml:2392(para) +msgid "UUID used by glance to uniquely identify each VM image." +msgstr "" + +#: ./doc/glossary/glossary-terms.xml:2397(glossterm) +msgid "incubated project" +msgstr "" + +#: ./doc/glossary/glossary-terms.xml:2399(para) +msgid "A community project may be elevated to this status and is then promoted to a core project." +msgstr "" + +#: ./doc/glossary/glossary-terms.xml:2405(glossterm) +msgid "ingress filtering" +msgstr "" + +#: ./doc/glossary/glossary-terms.xml:2407(para) +msgid "The process of filtering incoming network traffic. Supported by nova." +msgstr "" + +#: ./doc/glossary/glossary-terms.xml:2412(glossterm) +msgid "injection" +msgstr "" + +#: ./doc/glossary/glossary-terms.xml:2414(para) +msgid "The process of putting a file into a virtual machine image before the instance is started." +msgstr "" + +#: ./doc/glossary/glossary-terms.xml:2420(glossterm) +msgid "instance" +msgstr "" + +#: ./doc/glossary/glossary-terms.xml:2422(para) +msgid "A running VM, or a VM in a known state such as suspended that can be used like a hardware server." +msgstr "" + +#: ./doc/glossary/glossary-terms.xml:2428(glossterm) +msgid "instance ID" +msgstr "" + +#: ./doc/glossary/glossary-terms.xml:2430(para) +msgid "Alternative term for instance UUID." +msgstr "" + +#: ./doc/glossary/glossary-terms.xml:2434(glossterm) +msgid "instance state" +msgstr "" + +#: ./doc/glossary/glossary-terms.xml:2436(para) +msgid "The current state of a nova VM image." +msgstr "" + +#: ./doc/glossary/glossary-terms.xml:2440(glossterm) +msgid "instance type" +msgstr "" + +#: ./doc/glossary/glossary-terms.xml:2442(para) +msgid "Describes the parameters of the various virtual machine images that are available to users, includes parameters such as CPU, storage, and memory. Alternative term for flavor." +msgstr "" + +#: ./doc/glossary/glossary-terms.xml:2449(glossterm) +msgid "instance type ID" +msgstr "" + +#: ./doc/glossary/glossary-terms.xml:2451(para) +msgid "Alternative term for a flavor ID." +msgstr "" + +#: ./doc/glossary/glossary-terms.xml:2455(glossterm) +msgid "instance UUID" +msgstr "" + +#: ./doc/glossary/glossary-terms.xml:2457(para) ./doc/glossary/glossary-terms.xml:3969(para) +msgid "Unique ID assigned to each nova VM instance." +msgstr "" + +#: ./doc/glossary/glossary-terms.xml:2462(glossterm) +msgid "interface ID" +msgstr "" + +#: ./doc/glossary/glossary-terms.xml:2464(para) +msgid "Unique ID for a neutron VIF or vNIC in the form of a UUID." +msgstr "" + +#: ./doc/glossary/glossary-terms.xml:2469(glossterm) +msgid "Internet Service Provider (ISP)" +msgstr "" + +#: ./doc/glossary/glossary-terms.xml:2471(para) +msgid "Any business that provides Internet access to individuals or businesses." +msgstr "" + +#: ./doc/glossary/glossary-terms.xml:2476(glossterm) +msgid "Ironic" +msgstr "" + +#: ./doc/glossary/glossary-terms.xml:2478(para) +msgid "OpenStack project that provisions bare metal, as opposed to virtual, machines." +msgstr "" + +#: ./doc/glossary/glossary-terms.xml:2483(glossterm) +msgid "IP address" +msgstr "" + +#: ./doc/glossary/glossary-terms.xml:2485(para) +msgid "Number that is unique to every computer system on the Internet. Two versions of the Internet Protocol (IP) are in use for addresses: IPv4 and IPv6." +msgstr "" + +#: ./doc/glossary/glossary-terms.xml:2492(glossterm) +msgid "IP Address Management (IPAM)" +msgstr "" + +#: ./doc/glossary/glossary-terms.xml:2494(para) +msgid "The process of automating IP address allocation, deallocation, and management. Currently provided by nova, melange, and neutron." +msgstr "" + +#: ./doc/glossary/glossary-terms.xml:2500(glossterm) +msgid "IPL" +msgstr "" + +#: ./doc/glossary/glossary-terms.xml:2502(para) +msgid "Initial Program Loader." +msgstr "" + +#: ./doc/glossary/glossary-terms.xml:2506(glossterm) +msgid "IPMI" +msgstr "" + +#: ./doc/glossary/glossary-terms.xml:2508(para) +msgid "Intelligent Platform Management Interface. IPMI is a standardized computer system interface used by system administrators for out-of-band management of computer systems and monitoring of their operation. In layman's terms, it is a way to manage a computer using a direct network connection, whether it is turned on or not; connecting to the hardware rather than an operating system or login shell." +msgstr "" + +#: ./doc/glossary/glossary-terms.xml:2520(glossterm) +msgid "iptables" +msgstr "" + +#: ./doc/glossary/glossary-terms.xml:2522(para) +msgid "Used along with arptables and ebtables, iptables create firewalls in nova. iptables are the tables provided by the Linux kernel firewall (implemented as different Netfilter modules) and the chains and rules it stores. Different kernel modules and programs are currently used for different protocols; iptables applies to IPv4, ip6tables to IPv6, arptables to ARP, and ebtables to Ethernet frames. Requires root privilege to manipulate." +msgstr "" + +#: ./doc/glossary/glossary-terms.xml:2535(glossterm) +msgid "iSCSI" +msgstr "" + +#: ./doc/glossary/glossary-terms.xml:2537(para) +msgid "The SCSI disk protocol tunneled within Ethernet, supported by nova, swift, and glance." +msgstr "" + +#: ./doc/glossary/glossary-terms.xml:2542(glossterm) +msgid "ISO9960" +msgstr "" + +#: ./doc/glossary/glossary-terms.xml:2544(para) ./doc/glossary/glossary-terms.xml:3498(para) ./doc/glossary/glossary-terms.xml:4538(para) ./doc/glossary/glossary-terms.xml:4545(para) ./doc/glossary/glossary-terms.xml:4653(para) +msgid "One of the VM image disk formats supported by glance." +msgstr "" + +#: ./doc/glossary/glossary-terms.xml:2549(glossterm) +msgid "itsec" +msgstr "" + +#: ./doc/glossary/glossary-terms.xml:2551(para) +msgid "A default role in the nova RBAC system that can quarantine an instance in any project." +msgstr "" + +#: ./doc/glossary/glossary-terms.xml:2565(title) +msgid "J" +msgstr "" + +#: ./doc/glossary/glossary-terms.xml:2567(glossterm) +msgid "Java" +msgstr "" + +#: ./doc/glossary/glossary-terms.xml:2569(para) +msgid "A programming language that is used to create systems that involve more than one computer by way of a network." +msgstr "" + +#: ./doc/glossary/glossary-terms.xml:2575(glossterm) +msgid "JavaScript" +msgstr "" + +#: ./doc/glossary/glossary-terms.xml:2577(para) +msgid "A scripting language that is used to build web pages." +msgstr "" + +#: ./doc/glossary/glossary-terms.xml:2582(glossterm) +msgid "JavaScript Object Notation (JSON)" +msgstr "" + +#: ./doc/glossary/glossary-terms.xml:2584(para) +msgid "One of the supported response formats in OpenStack." +msgstr "" + +#: ./doc/glossary/glossary-terms.xml:2589(glossterm) +msgid "Jenkins" +msgstr "" + +#: ./doc/glossary/glossary-terms.xml:2591(para) +msgid "Tool used to run jobs automatically for OpenStack development." +msgstr "" + +#: ./doc/glossary/glossary-terms.xml:2596(glossterm) +msgid "Juno" +msgstr "" + +#: ./doc/glossary/glossary-terms.xml:2598(para) +msgid "Project name for the tenth release of OpenStack." +msgstr "" + +#: ./doc/glossary/glossary-terms.xml:2610(title) +msgid "K" +msgstr "" + +#: ./doc/glossary/glossary-terms.xml:2612(glossterm) +msgid "kernel-based VM (KVM)" +msgstr "" + +#: ./doc/glossary/glossary-terms.xml:2618(glossterm) +msgid "Keystone" +msgstr "" + +#: ./doc/glossary/glossary-terms.xml:2620(para) +msgid "The project that provides OpenStack Identity services." +msgstr "" + +#: ./doc/glossary/glossary-terms.xml:2625(glossterm) +msgid "Kickstart" +msgstr "" + +#: ./doc/glossary/glossary-terms.xml:2627(para) +msgid "A tool to automate system configuration and installation on Red Hat, Fedora, and CentOS based Linux distributions." +msgstr "" + +#: ./doc/glossary/glossary-terms.xml:2635(title) +msgid "L" +msgstr "" + +#: ./doc/glossary/glossary-terms.xml:2637(glossterm) +msgid "large object" +msgstr "" + +#: ./doc/glossary/glossary-terms.xml:2639(para) +msgid "An object within swift that is larger than 5 GBs." +msgstr "" + +#: ./doc/glossary/glossary-terms.xml:2644(glossterm) +msgid "Launchpad" +msgstr "" + +#: ./doc/glossary/glossary-terms.xml:2646(para) +msgid "The collaboration site for OpenStack." +msgstr "" + +#: ./doc/glossary/glossary-terms.xml:2650(glossterm) +msgid "Layer-2 network" +msgstr "" + +#: ./doc/glossary/glossary-terms.xml:2652(para) +msgid "Term used for OSI network architecture for the data link layer." +msgstr "" + +#: ./doc/glossary/glossary-terms.xml:2657(glossterm) +msgid "libvirt" +msgstr "" + +#: ./doc/glossary/glossary-terms.xml:2659(para) +msgid "Virtualization API library used by OpenStack to interact with many of its supported hypervisors." +msgstr "" + +#: ./doc/glossary/glossary-terms.xml:2665(glossterm) +msgid "Linux bridge" +msgstr "" + +#: ./doc/glossary/glossary-terms.xml:2667(para) +msgid "Software that enables multiple VMs to share a single physical NIC within nova." +msgstr "" + +#: ./doc/glossary/glossary-terms.xml:2672(glossterm) +msgid "Linux Bridge neutron plug-in" +msgstr "" + +#: ./doc/glossary/glossary-terms.xml:2674(para) +msgid "Enables a Linux bridge to understand a neutron port, interface attachment, and other abstractions." +msgstr "" + +#: ./doc/glossary/glossary-terms.xml:2680(glossterm) +msgid "Linux containers (LXC)" +msgstr "" + +#: ./doc/glossary/glossary-terms.xml:2686(glossterm) +msgid "live migration" +msgstr "" + +#: ./doc/glossary/glossary-terms.xml:2688(para) +msgid "The ability within nova to move running virtual machine instances from one host to another with only a small service interruption during switch-over." +msgstr "" + +#: ./doc/glossary/glossary-terms.xml:2695(glossterm) +msgid "load balancer" +msgstr "" + +#: ./doc/glossary/glossary-terms.xml:2697(para) +msgid "A load balancer is a logical device which belongs to a cloud account. It is used to distribute workloads between multiple back-end systems or services, based on the criteria defined as part of its configuration." +msgstr "" + +#: ./doc/glossary/glossary-terms.xml:2705(glossterm) +msgid "load balancing" +msgstr "" + +#: ./doc/glossary/glossary-terms.xml:2707(para) +msgid "The process of spreading client requests between two or more nodes to improve performance and availability." +msgstr "" + +#: ./doc/glossary/glossary-terms.xml:2721(title) +msgid "M" +msgstr "" + +#: ./doc/glossary/glossary-terms.xml:2723(glossterm) +msgid "management API" +msgstr "" + +#: ./doc/glossary/glossary-terms.xml:2725(para) +msgid "Alternative term for an admin API." +msgstr "" + +#: ./doc/glossary/glossary-terms.xml:2729(glossterm) +msgid "management network" +msgstr "" + +#: ./doc/glossary/glossary-terms.xml:2731(para) +msgid "A network segment used for administration, not accessible to the public internet." +msgstr "" + +#: ./doc/glossary/glossary-terms.xml:2736(glossterm) +msgid "manager" +msgstr "" + +#: ./doc/glossary/glossary-terms.xml:2738(para) +msgid "Logical groupings of related code such as the nova volume manager or network manager." +msgstr "" + +#: ./doc/glossary/glossary-terms.xml:2743(glossterm) +msgid "manifest" +msgstr "" + +#: ./doc/glossary/glossary-terms.xml:2745(para) +msgid "Used to track segments of a large object within swift." +msgstr "" + +#: ./doc/glossary/glossary-terms.xml:2750(glossterm) +msgid "manifest object" +msgstr "" + +#: ./doc/glossary/glossary-terms.xml:2752(para) +msgid "A special swift object that contains the manifest for a large object." +msgstr "" + +#: ./doc/glossary/glossary-terms.xml:2757(glossterm) +msgid "Marconi" +msgstr "" + +#: ./doc/glossary/glossary-terms.xml:2759(para) +msgid "OpenStack project that provides a queue service to applications." +msgstr "" + +#: ./doc/glossary/glossary-terms.xml:2764(glossterm) +msgid "Melange" +msgstr "" + +#: ./doc/glossary/glossary-terms.xml:2766(para) +msgid "Project name for OpenStack Network Information Service. To be merged with neutron." +msgstr "" + +#: ./doc/glossary/glossary-terms.xml:2771(glossterm) +msgid "membership" +msgstr "" + +#: ./doc/glossary/glossary-terms.xml:2773(para) +msgid "The association between a glance VM image and a tenant. Enables images to be shared with specified tenants." +msgstr "" + +#: ./doc/glossary/glossary-terms.xml:2779(glossterm) +msgid "membership list" +msgstr "" + +#: ./doc/glossary/glossary-terms.xml:2786(glossterm) +msgid "memcached" +msgstr "" + +#: ./doc/glossary/glossary-terms.xml:2788(para) +msgid "A distributed memory object caching system that is used by swift for caching." +msgstr "" + +#: ./doc/glossary/glossary-terms.xml:2793(glossterm) +msgid "memory overcommit" +msgstr "" + +#: ./doc/glossary/glossary-terms.xml:2795(para) +msgid "The ability to start new VM instances based on the actual memory usage of a host, as opposed to basing the decision on the amount of RAM each running instance thinks it has available. Also known as RAM overcommit." +msgstr "" + +#: ./doc/glossary/glossary-terms.xml:2803(glossterm) +msgid "message broker" +msgstr "" + +#: ./doc/glossary/glossary-terms.xml:2805(para) +msgid "The software package used to provide AMQP messaging capabilities within nova. Default package is RabbitMQ." +msgstr "" + +#: ./doc/glossary/glossary-terms.xml:2811(glossterm) +msgid "message bus" +msgstr "" + +#: ./doc/glossary/glossary-terms.xml:2813(para) +msgid "The main virtual communication line used by all AMQP messages for inter-cloud communications within nova." +msgstr "" + +#: ./doc/glossary/glossary-terms.xml:2819(glossterm) +msgid "message queue" +msgstr "" + +#: ./doc/glossary/glossary-terms.xml:2821(para) +msgid "Passes requests from clients to the appropriate workers and returns the output to the client after the job completes." +msgstr "" + +#: ./doc/glossary/glossary-terms.xml:2827(glossterm) +msgid "Meta-Data Server (MDS)" +msgstr "" + +#: ./doc/glossary/glossary-terms.xml:2829(para) +msgid "Stores CephFS metadata." +msgstr "" + +#: ./doc/glossary/glossary-terms.xml:2833(glossterm) +msgid "migration" +msgstr "" + +#: ./doc/glossary/glossary-terms.xml:2835(para) +msgid "The process of moving a VM instance from one host to another." +msgstr "" + +#: ./doc/glossary/glossary-terms.xml:2840(glossterm) +msgid "Modular Layer 2 (ML2) neutron plug-in" +msgstr "" + +#: ./doc/glossary/glossary-terms.xml:2842(para) +msgid "Can concurrently use multiple layer 2 networking technologies, such as 802.1Q and VXLAN, in neutron." +msgstr "" + +#: ./doc/glossary/glossary-terms.xml:2848(glossterm) +msgid "Monitor (Mon)" +msgstr "" + +#: ./doc/glossary/glossary-terms.xml:2850(para) +msgid "A Ceph component that communicates with external clients, checks data state and consistency, and performs quorum functions." +msgstr "" + +#: ./doc/glossary/glossary-terms.xml:2856(glossterm) +msgid "multi-factor authentication" +msgstr "" + +#: ./doc/glossary/glossary-terms.xml:2858(para) +msgid "Authentication method that uses two or more credentials, such as a password and a private key. Currently not supported in keystone." +msgstr "" + +#: ./doc/glossary/glossary-terms.xml:2864(glossterm) +msgid "MultiNic" +msgstr "" + +#: ./doc/glossary/glossary-terms.xml:2866(para) +msgid "Facility in nova that enables a virtual machine instance to have more than one VIF connected to it." +msgstr "" + +#: ./doc/glossary/glossary-terms.xml:2880(title) +msgid "N" +msgstr "" + +#: ./doc/glossary/glossary-terms.xml:2882(glossterm) +msgid "Nebula" +msgstr "" + +#: ./doc/glossary/glossary-terms.xml:2884(para) +msgid "Released as open source by NASA in 2010 and is the basis for nova." +msgstr "" + +#: ./doc/glossary/glossary-terms.xml:2889(glossterm) +msgid "netadmin" +msgstr "" + +#: ./doc/glossary/glossary-terms.xml:2891(para) +msgid "One of the default roles in the nova RBAC system. Enables the user to allocate publicly accessible IP addresses to instances and change firewall rules." +msgstr "" + +#: ./doc/glossary/glossary-terms.xml:2898(glossterm) +msgid "NetApp volume driver" +msgstr "" + +#: ./doc/glossary/glossary-terms.xml:2900(para) +msgid "Enables nova to communicate with NetApp storage devices through the NetApp OnCommand Provisioning Manager." +msgstr "" + +#: ./doc/glossary/glossary-terms.xml:2906(glossterm) +msgid "network" +msgstr "" + +#: ./doc/glossary/glossary-terms.xml:2908(para) +msgid "A virtual network that provides connectivity between entities. For example, a collection of virtual ports that share network connectivity. In neutron terminology, a network is always a Layer-2 network." +msgstr "" + +#: ./doc/glossary/glossary-terms.xml:2916(glossterm) +msgid "Network Address Translation (NAT)" +msgstr "" + +#: ./doc/glossary/glossary-terms.xml:2918(para) +msgid "The process of modifying IP address information while in-transit. Supported by nova and neutron." +msgstr "" + +#: ./doc/glossary/glossary-terms.xml:2924(glossterm) +msgid "network controller" +msgstr "" + +#: ./doc/glossary/glossary-terms.xml:2926(para) +msgid "A nova daemon that orchestrates the network configuration of nodes including includes IP addresses, VLANs, bridging, and manages routing for both public and private networks." +msgstr "" + +#: ./doc/glossary/glossary-terms.xml:2933(glossterm) +msgid "Network File System (NFS)" +msgstr "" + +#: ./doc/glossary/glossary-terms.xml:2935(para) +msgid "A method for making file systems available over the network. Supported by OpenStack." +msgstr "" + +#: ./doc/glossary/glossary-terms.xml:2940(glossterm) +msgid "network ID" +msgstr "" + +#: ./doc/glossary/glossary-terms.xml:2942(para) +msgid "Unique ID assigned to each network segment within neutron. Same as network UUID" +msgstr "" + +#: ./doc/glossary/glossary-terms.xml:2947(glossterm) +msgid "network manager" +msgstr "" + +#: ./doc/glossary/glossary-terms.xml:2949(para) +msgid "The nova component that manages various network components, such as firewall rules, IP address allocation, and so on." +msgstr "" + +#: ./doc/glossary/glossary-terms.xml:2955(glossterm) +msgid "network node" +msgstr "" + +#: ./doc/glossary/glossary-terms.xml:2957(para) +msgid "Any nova node that runs the network worker daemon." +msgstr "" + +#: ./doc/glossary/glossary-terms.xml:2962(glossterm) +msgid "network segment" +msgstr "" + +#: ./doc/glossary/glossary-terms.xml:2964(para) +msgid "Represents a virtual, isolated OSI layer 2 subnet in neutron." +msgstr "" + +#: ./doc/glossary/glossary-terms.xml:2969(glossterm) +msgid "Network Time Protocol (NTP)" +msgstr "" + +#: ./doc/glossary/glossary-terms.xml:2971(para) +msgid "A method of keeping a clock for a host or node correct through communications with a trusted, accurate time source." +msgstr "" + +#: ./doc/glossary/glossary-terms.xml:2977(glossterm) +msgid "network UUID" +msgstr "" + +#: ./doc/glossary/glossary-terms.xml:2979(para) +msgid "Unique ID for a neutron network segment." +msgstr "" + +#: ./doc/glossary/glossary-terms.xml:2983(glossterm) +msgid "network worker" +msgstr "" + +#: ./doc/glossary/glossary-terms.xml:2985(para) +msgid "The nova-network worker daemon, provides services such as giving an IP address to a booting nova instance." +msgstr "" + +#: ./doc/glossary/glossary-terms.xml:2991(glossterm) +msgid "Neutron" +msgstr "" + +#: ./doc/glossary/glossary-terms.xml:2993(para) +msgid "A core OpenStack project that provides a network connectivity abstraction layer to OpenStack Compute." +msgstr "" + +#: ./doc/glossary/glossary-terms.xml:2999(glossterm) +msgid "neutron API" +msgstr "" + +#: ./doc/glossary/glossary-terms.xml:3001(para) +msgid "API used to access neutron. Provides an extensible architecture to enable custom plug-in creation." +msgstr "" + +#: ./doc/glossary/glossary-terms.xml:3007(glossterm) +msgid "neutron manager" +msgstr "" + +#: ./doc/glossary/glossary-terms.xml:3009(para) +msgid "Enables nova and neutron integration, which enables neutron to perform network management for nova VMs." +msgstr "" + +#: ./doc/glossary/glossary-terms.xml:3015(glossterm) +msgid "neutron plug-in" +msgstr "" + +#: ./doc/glossary/glossary-terms.xml:3017(para) +msgid "Interface within neutron that enables organizations to create custom plug-ins for advanced features such as QoS, ACLs, or IDS." +msgstr "" + +#: ./doc/glossary/glossary-terms.xml:3024(glossterm) +msgid "Nexenta volume driver" +msgstr "" + +#: ./doc/glossary/glossary-terms.xml:3026(para) +msgid "Provides support for NexentaStor devices in nova." +msgstr "" + +#: ./doc/glossary/glossary-terms.xml:3031(glossterm) +msgid "Nicira NVP neutron plug-in" +msgstr "" + +#: ./doc/glossary/glossary-terms.xml:3033(para) +msgid "Provides support for the Nicira Network Virtualization Platform (NVP) in neutron." +msgstr "" + +#: ./doc/glossary/glossary-terms.xml:3038(glossterm) +msgid "No ACK" +msgstr "" + +#: ./doc/glossary/glossary-terms.xml:3040(para) +msgid "Disables server-side message acknowledgment in the nova RabbitMQ. Increases performance but decreases reliability." +msgstr "" + +#: ./doc/glossary/glossary-terms.xml:3046(glossterm) +msgid "node" +msgstr "" + +#: ./doc/glossary/glossary-terms.xml:3048(para) +msgid "A VM instance that runs on a host." +msgstr "" + +#: ./doc/glossary/glossary-terms.xml:3052(glossterm) +msgid "non-durable exchange" +msgstr "" + +#: ./doc/glossary/glossary-terms.xml:3054(para) +msgid "Message exchange that is cleared when the service restarts. Its data is not written to persistent storage." +msgstr "" + +#: ./doc/glossary/glossary-terms.xml:3060(glossterm) +msgid "non-durable queue" +msgstr "" + +#: ./doc/glossary/glossary-terms.xml:3062(para) +msgid "Message queue that is cleared when the service restarts. Its data is not written to persistent storage." +msgstr "" + +#: ./doc/glossary/glossary-terms.xml:3068(glossterm) +msgid "non-persistent volume" +msgstr "" + +#: ./doc/glossary/glossary-terms.xml:3070(para) +msgid "Alternative term for an ephemeral volume." +msgstr "" + +#: ./doc/glossary/glossary-terms.xml:3074(glossterm) +msgid "nova" +msgstr "" + +#: ./doc/glossary/glossary-terms.xml:3076(para) +msgid "OpenStack project that provides compute services." +msgstr "" + +#: ./doc/glossary/glossary-terms.xml:3081(glossterm) +msgid "nova API" +msgstr "" + +#: ./doc/glossary/glossary-terms.xml:3083(para) +msgid "Alternative term for the nova Compute API." +msgstr "" + +#: ./doc/glossary/glossary-terms.xml:3088(glossterm) +msgid "nova network" +msgstr "" + +#: ./doc/glossary/glossary-terms.xml:3090(para) +msgid "A nova component that manages IP address allocation, firewalls, and other network-related tasks." +msgstr "" + +#: ./doc/glossary/glossary-terms.xml:3096(glossterm) +msgid "nova volume" +msgstr "" + +#: ./doc/glossary/glossary-terms.xml:3098(para) +msgid "The nova component that manages storage volumes, currently being split off into a separate project named cinder." +msgstr "" + +#: ./doc/glossary/glossary-terms.xml:3106(title) +msgid "O" +msgstr "" + +#: ./doc/glossary/glossary-terms.xml:3108(glossterm) +msgid "object" +msgstr "" + +#: ./doc/glossary/glossary-terms.xml:3110(para) +msgid "A BLOB of data held by swift, can be in any format." +msgstr "" + +#: ./doc/glossary/glossary-terms.xml:3115(glossterm) +msgid "Object API" +msgstr "" + +#: ./doc/glossary/glossary-terms.xml:3117(para) ./doc/glossary/glossary-terms.xml:3169(para) +msgid "Alternative term for the swift object API." +msgstr "" + +#: ./doc/glossary/glossary-terms.xml:3122(glossterm) +msgid "object auditor" +msgstr "" + +#: ./doc/glossary/glossary-terms.xml:3124(para) +msgid "Opens all objects for an object server and verifies the MD5 hash, size, and metadata for each object." +msgstr "" + +#: ./doc/glossary/glossary-terms.xml:3130(glossterm) +msgid "object expiration" +msgstr "" + +#: ./doc/glossary/glossary-terms.xml:3132(para) +msgid "A configurable option within swift to automatically delete objects after a specified amount of time has passed or a certain date is reached." +msgstr "" + +#: ./doc/glossary/glossary-terms.xml:3139(glossterm) +msgid "object hash" +msgstr "" + +#: ./doc/glossary/glossary-terms.xml:3141(para) +msgid "Uniquely ID for a swift object." +msgstr "" + +#: ./doc/glossary/glossary-terms.xml:3145(glossterm) +msgid "object path hash" +msgstr "" + +#: ./doc/glossary/glossary-terms.xml:3147(para) +msgid "Used by swift to determine the location of an object in the ring. Maps objects to partitions." +msgstr "" + +#: ./doc/glossary/glossary-terms.xml:3153(glossterm) +msgid "object replicator" +msgstr "" + +#: ./doc/glossary/glossary-terms.xml:3155(para) +msgid "A swift component that copies and object to remote partitions for fault tolerance." +msgstr "" + +#: ./doc/glossary/glossary-terms.xml:3160(glossterm) +msgid "object server" +msgstr "" + +#: ./doc/glossary/glossary-terms.xml:3162(para) +msgid "A swift component that is responsible for managing objects." +msgstr "" + +#: ./doc/glossary/glossary-terms.xml:3167(glossterm) +msgid "Object Service API" +msgstr "" + +#: ./doc/glossary/glossary-terms.xml:3174(glossterm) +msgid "object storage" +msgstr "" + +#: ./doc/glossary/glossary-terms.xml:3176(para) +msgid "Provides eventually consistent and redundant storage and retrieval of fixed digital content." +msgstr "" + +#: ./doc/glossary/glossary-terms.xml:3182(glossterm) +msgid "Object Storage Device (OSD)" +msgstr "" + +#: ./doc/glossary/glossary-terms.xml:3184(para) +msgid "The Ceph storage daemon." +msgstr "" + +#: ./doc/glossary/glossary-terms.xml:3188(glossterm) +msgid "object versioning" +msgstr "" + +#: ./doc/glossary/glossary-terms.xml:3190(para) +msgid "Allows a user to set a flag on a swift container so all objects within the container are versioned." +msgstr "" + +#: ./doc/glossary/glossary-terms.xml:3196(glossterm) +msgid "Oldie" +msgstr "" + +#: ./doc/glossary/glossary-terms.xml:3198(para) +msgid "Term for a swift process that runs for a long time. Can indicate a hung process." +msgstr "" + +#: ./doc/glossary/glossary-terms.xml:3204(glossterm) +msgid "Open Cloud Computing Interface (OCCI)" +msgstr "" + +#: ./doc/glossary/glossary-terms.xml:3207(para) +msgid "A standardized interface for managing compute, data, and network resources, currently unsupported in OpenStack." +msgstr "" + +#: ./doc/glossary/glossary-terms.xml:3213(glossterm) +msgid "Open Virtualization Format (OVF)" +msgstr "" + +#: ./doc/glossary/glossary-terms.xml:3215(para) +msgid "Standard for packaging VM images. Supported in OpenStack." +msgstr "" + +#: ./doc/glossary/glossary-terms.xml:3220(glossterm) +msgid "Open vSwitch neutron plug-in" +msgstr "" + +#: ./doc/glossary/glossary-terms.xml:3222(para) +msgid "Provides support for Open vSwitch in neutron." +msgstr "" + +#: ./doc/glossary/glossary-terms.xml:3227(glossterm) +msgid "OpenLDAP" +msgstr "" + +#: ./doc/glossary/glossary-terms.xml:3229(para) +msgid "An open source LDAP server. Supported by both nova and keystone." +msgstr "" + +#: ./doc/glossary/glossary-terms.xml:3234(glossterm) +msgid "OpenStack API (OSAPI)" +msgstr "" + +#: ./doc/glossary/glossary-terms.xml:3236(para) +msgid "The core OpenStack API." +msgstr "" + +#: ./doc/glossary/glossary-terms.xml:3240(glossterm) +msgid "openSUSE" +msgstr "" + +#: ./doc/glossary/glossary-terms.xml:3247(glossterm) +msgid "operator" +msgstr "" + +#: ./doc/glossary/glossary-terms.xml:3249(para) +msgid "The person responsible for planning and maintaining an OpenStack installation." +msgstr "" + +#: ./doc/glossary/glossary-terms.xml:3254(glossterm) +msgid "orphan" +msgstr "" + +#: ./doc/glossary/glossary-terms.xml:3256(para) +msgid "In the context of swift this is a process that is not terminated after an upgrade, restart, or reload of the service." +msgstr "" + +#: ./doc/glossary/glossary-terms.xml:3264(title) +msgid "P" +msgstr "" + +#: ./doc/glossary/glossary-terms.xml:3266(glossterm) +msgid "parent cell" +msgstr "" + +#: ./doc/glossary/glossary-terms.xml:3268(para) +msgid "If a requested resource, such as CPU time, disk storage, or memory, is not available in the parent cell, the request is forwarded to associated child cells." +msgstr "" + +#: ./doc/glossary/glossary-terms.xml:3275(glossterm) +msgid "partition" +msgstr "" + +#: ./doc/glossary/glossary-terms.xml:3277(para) +msgid "A unit of storage within swift used to store objects, exists on top of devices, replicated for fault tolerance." +msgstr "" + +#: ./doc/glossary/glossary-terms.xml:3283(glossterm) +msgid "partition index" +msgstr "" + +#: ./doc/glossary/glossary-terms.xml:3285(para) +msgid "Contains the locations of all swift partitions within the ring." +msgstr "" + +#: ./doc/glossary/glossary-terms.xml:3290(glossterm) +msgid "partition shift value" +msgstr "" + +#: ./doc/glossary/glossary-terms.xml:3292(para) +msgid "Used by swift to determine which partition data should reside on." +msgstr "" + +#: ./doc/glossary/glossary-terms.xml:3297(glossterm) +msgid "pause" +msgstr "" + +#: ./doc/glossary/glossary-terms.xml:3299(para) +msgid "A VM state where no changes occur (no changes in memory, network communications stop, etc), the VM is frozen but not shut down." +msgstr "" + +#: ./doc/glossary/glossary-terms.xml:3305(glossterm) +msgid "PCI passthrough" +msgstr "" + +#: ./doc/glossary/glossary-terms.xml:3307(para) +msgid "Gives guest VMs exclusive access to a PCI device. Currently supported in OpenStack Havana and later releases." +msgstr "" + +#: ./doc/glossary/glossary-terms.xml:3313(glossterm) +msgid "persistent message" +msgstr "" + +#: ./doc/glossary/glossary-terms.xml:3315(para) +msgid "A message that is stored both in memory and on disk, the message is not lost after a failure or restart." +msgstr "" + +#: ./doc/glossary/glossary-terms.xml:3321(glossterm) +msgid "persistent volume" +msgstr "" + +#: ./doc/glossary/glossary-terms.xml:3323(para) +msgid "Changes to these types of disk volumes are saved." +msgstr "" + +#: ./doc/glossary/glossary-terms.xml:3328(glossterm) +msgid "personality file" +msgstr "" + +#: ./doc/glossary/glossary-terms.xml:3330(para) +msgid "A file used to customize a nova instance, can be used to inject SSH keys or a specific network configuration." +msgstr "" + +#: ./doc/glossary/glossary-terms.xml:3336(glossterm) +msgid "plug-in" +msgstr "" + +#: ./doc/glossary/glossary-terms.xml:3338(para) +msgid "Software component providing the actual implementation for neutron APIs, or for Compute APIs, depending on the context." +msgstr "" + +#: ./doc/glossary/glossary-terms.xml:3344(glossterm) +msgid "policy service" +msgstr "" + +#: ./doc/glossary/glossary-terms.xml:3346(para) +msgid "Component of keystone that provides a rule management interface and a rule based authorization engine." +msgstr "" + +#: ./doc/glossary/glossary-terms.xml:3352(glossterm) +msgid "port" +msgstr "" + +#: ./doc/glossary/glossary-terms.xml:3354(para) +msgid "A virtual network port within neutron, VIFs / vNICs are connected to a port." +msgstr "" + +#: ./doc/glossary/glossary-terms.xml:3359(glossterm) +msgid "port UUID" +msgstr "" + +#: ./doc/glossary/glossary-terms.xml:3361(para) +msgid "Unique ID for a neutron port." +msgstr "" + +#: ./doc/glossary/glossary-terms.xml:3365(glossterm) +msgid "preseed" +msgstr "" + +#: ./doc/glossary/glossary-terms.xml:3367(para) +msgid "A tool to automate system configuration and installation on Debian-based Linux distributions." +msgstr "" + +#: ./doc/glossary/glossary-terms.xml:3373(glossterm) +msgid "private image" +msgstr "" + +#: ./doc/glossary/glossary-terms.xml:3375(para) +msgid "A glance VM image that is only available to specified tenants." +msgstr "" + +#: ./doc/glossary/glossary-terms.xml:3380(glossterm) +msgid "private IP address" +msgstr "" + +#: ./doc/glossary/glossary-terms.xml:3382(para) +msgid "An IP address used for management and administration, not available to the public internet." +msgstr "" + +#: ./doc/glossary/glossary-terms.xml:3388(glossterm) +msgid "private network" +msgstr "" + +#: ./doc/glossary/glossary-terms.xml:3390(para) +msgid "The Network Controller provides virtual networks to enable compute servers to interact with each other and with the public network. All machines must have a public and private network interface. A private network interface can be a flat or VLAN network interface. A flat network interface is controlled by the flat_interface with flat managers. A VLAN network interface is controlled by the vlan_interface option with VLAN managers." +msgstr "" + +#: ./doc/glossary/glossary-terms.xml:3403(glossterm) +msgid "project" +msgstr "" + +#: ./doc/glossary/glossary-terms.xml:3405(para) +msgid "A logical grouping of users within nova, used to define quotas and access to VM images." +msgstr "" + +#: ./doc/glossary/glossary-terms.xml:3410(glossterm) +msgid "project ID" +msgstr "" + +#: ./doc/glossary/glossary-terms.xml:3412(para) +msgid "User defined alpha-numeric string in nova, the name of a project." +msgstr "" + +#: ./doc/glossary/glossary-terms.xml:3417(glossterm) +msgid "project VPN" +msgstr "" + +#: ./doc/glossary/glossary-terms.xml:3419(para) +msgid "Alternative term for a cloudpipe." +msgstr "" + +#: ./doc/glossary/glossary-terms.xml:3423(glossterm) +msgid "provider" +msgstr "" + +#: ./doc/glossary/glossary-terms.xml:3425(para) +msgid "An administrator who has access to all hosts and instances." +msgstr "" + +#: ./doc/glossary/glossary-terms.xml:3430(glossterm) +msgid "proxy node" +msgstr "" + +#: ./doc/glossary/glossary-terms.xml:3432(para) +msgid "A node that provides the swift proxy service." +msgstr "" + +#: ./doc/glossary/glossary-terms.xml:3437(glossterm) +msgid "proxy server" +msgstr "" + +#: ./doc/glossary/glossary-terms.xml:3439(para) +msgid "Users of swift interact with the service through the proxy server which in-turn looks up the location of the requested data within the ring and returns the results to the user." +msgstr "" + +#: ./doc/glossary/glossary-terms.xml:3446(glossterm) +msgid "public API" +msgstr "" + +#: ./doc/glossary/glossary-terms.xml:3448(para) +msgid "An API endpoint used for both service to service communication and end user interactions." +msgstr "" + +#: ./doc/glossary/glossary-terms.xml:3453(glossterm) +msgid "public image" +msgstr "" + +#: ./doc/glossary/glossary-terms.xml:3455(para) +msgid "A glance VM image that is available to all tenants." +msgstr "" + +#: ./doc/glossary/glossary-terms.xml:3460(glossterm) +msgid "public IP address" +msgstr "" + +#: ./doc/glossary/glossary-terms.xml:3462(para) +msgid "An IP address that is accessible to end-users." +msgstr "" + +#: ./doc/glossary/glossary-terms.xml:3467(glossterm) +msgid "public network" +msgstr "" + +#: ./doc/glossary/glossary-terms.xml:3469(para) +msgid "The Network Controller provides virtual networks to enable compute servers to interact with each other and with the public network. All machines must have a public and private network interface. The public network interface is controlled by the public_interface option." +msgstr "" + +#: ./doc/glossary/glossary-terms.xml:3478(glossterm) +msgid "Puppet" +msgstr "" + +#: ./doc/glossary/glossary-terms.xml:3480(para) +msgid "An operating system configuration management tool supported by OpenStack." +msgstr "" + +#: ./doc/glossary/glossary-terms.xml:3485(glossterm) +msgid "Python" +msgstr "" + +#: ./doc/glossary/glossary-terms.xml:3487(para) +msgid "Programming language used extensively in OpenStack." +msgstr "" + +#: ./doc/glossary/glossary-terms.xml:3494(title) +msgid "Q" +msgstr "" + +#: ./doc/glossary/glossary-terms.xml:3496(glossterm) +msgid "QEMU Copy On Write 2 (QCOW2)" +msgstr "" + +#: ./doc/glossary/glossary-terms.xml:3503(glossterm) +msgid "Qpid" +msgstr "" + +#: ./doc/glossary/glossary-terms.xml:3505(para) +msgid "Message queue software supported by OpenStack, an alternative to RabbitMQ." +msgstr "" + +#: ./doc/glossary/glossary-terms.xml:3510(glossterm) +msgid "quarantine" +msgstr "" + +#: ./doc/glossary/glossary-terms.xml:3512(para) +msgid "If swift finds objects, containers, or accounts that are corrupt they are placed in this state, are not replicated, cannot be read by clients, and a correct copy is re-replicated." +msgstr "" + +#: ./doc/glossary/glossary-terms.xml:3519(glossterm) +msgid "Quick EMUlator (QEMU)" +msgstr "" + +#: ./doc/glossary/glossary-terms.xml:3521(para) +msgid "QEMU is a generic and open source machine emulator and virtualizer." +msgstr "" + +#: ./doc/glossary/glossary-terms.xml:3523(para) +msgid "One of the hypervisors supported by OpenStack, generally used for development purposes." +msgstr "" + +#: ./doc/glossary/glossary-terms.xml:3528(glossterm) +msgid "quota" +msgstr "" + +#: ./doc/glossary/glossary-terms.xml:3530(para) +msgid "In nova, the ability to set resource limits on a per-project basis." +msgstr "" + +#: ./doc/glossary/glossary-terms.xml:3537(title) +msgid "R" +msgstr "" + +#: ./doc/glossary/glossary-terms.xml:3539(glossterm) +msgid "RabbitMQ" +msgstr "" + +#: ./doc/glossary/glossary-terms.xml:3541(para) +msgid "The default message queue software used by OpenStack." +msgstr "" + +#: ./doc/glossary/glossary-terms.xml:3546(glossterm) +msgid "Rackspace Cloud Files" +msgstr "" + +#: ./doc/glossary/glossary-terms.xml:3548(para) +msgid "Released as open source by Rackspace in 2010, the basis for swift." +msgstr "" + +#: ./doc/glossary/glossary-terms.xml:3553(glossterm) +msgid "RADOS Block Device (RBD)" +msgstr "" + +#: ./doc/glossary/glossary-terms.xml:3555(para) +msgid "Ceph component that enables a Linux block device to be striped over multiple distributed data stores." +msgstr "" + +#: ./doc/glossary/glossary-terms.xml:3561(glossterm) +msgid "radvd" +msgstr "" + +#: ./doc/glossary/glossary-terms.xml:3563(para) +msgid "The router advertisement daemon, used by the nova VLAN manager and FlatDHCP manager to provide routing services for VM instances." +msgstr "" + +#: ./doc/glossary/glossary-terms.xml:3569(glossterm) +msgid "RAM filter" +msgstr "" + +#: ./doc/glossary/glossary-terms.xml:3571(para) +msgid "The nova setting that enables or disables RAM overcommitment." +msgstr "" + +#: ./doc/glossary/glossary-terms.xml:3576(glossterm) +msgid "RAM overcommit" +msgstr "" + +#: ./doc/glossary/glossary-terms.xml:3578(para) +msgid "The ability to start new VM instances based on the actual memory usage of a host, as opposed to basing the decision on the amount of RAM each running instance thinks it has available. Also known as memory overcommit." +msgstr "" + +#: ./doc/glossary/glossary-terms.xml:3586(glossterm) +msgid "rate limit" +msgstr "" + +#: ./doc/glossary/glossary-terms.xml:3588(para) +msgid "Configurable option within swift to limit database writes on a per-account and/or per-container basis." +msgstr "" + +#: ./doc/glossary/glossary-terms.xml:3594(glossterm) +msgid "raw" +msgstr "" + +#: ./doc/glossary/glossary-terms.xml:3596(para) +msgid "One of the VM image disk formats supported by glance, an unstructured disk image." +msgstr "" + +#: ./doc/glossary/glossary-terms.xml:3601(glossterm) +msgid "rebalance" +msgstr "" + +#: ./doc/glossary/glossary-terms.xml:3603(para) +msgid "The process of distributing swift partitions across all drives in the ring, used during initial ring creation and after ring reconfiguration." +msgstr "" + +#: ./doc/glossary/glossary-terms.xml:3610(glossterm) +msgid "reboot" +msgstr "" + +#: ./doc/glossary/glossary-terms.xml:3612(para) +msgid "Either a soft or hard reboot of a server. With a soft reboot, the operating system is signaled to restart, which enables a graceful shutdown of all processes. A hard reboot is the equivalent of power cycling the server. The virtualization platform should ensure that the reboot action has completed successfully even in cases in which the underlying domain/vm is paused or halted/stopped." +msgstr "" + +#: ./doc/glossary/glossary-terms.xml:3624(glossterm) +msgid "rebuild" +msgstr "" + +#: ./doc/glossary/glossary-terms.xml:3626(para) +msgid "Removes all data on the server and replaces it with the specified image. Server ID and IP addresses remain the same." +msgstr "" + +#: ./doc/glossary/glossary-terms.xml:3632(glossterm) +msgid "Recon" +msgstr "" + +#: ./doc/glossary/glossary-terms.xml:3634(para) +msgid "A swift component that collects metrics." +msgstr "" + +#: ./doc/glossary/glossary-terms.xml:3638(glossterm) +msgid "record" +msgstr "" + +#: ./doc/glossary/glossary-terms.xml:3640(para) +msgid "Belongs to a particular domain and is used to specify information about the domain. There are several types of DNS records. Each record type contains particular information used to describe the purpose of that record. Examples include mail exchange (MX) records, which specify the mail server for a particular domain, and name server (NS) records, which specify the authoritative name servers for a domain." +msgstr "" + +#: ./doc/glossary/glossary-terms.xml:3652(glossterm) +msgid "record ID" +msgstr "" + +#: ./doc/glossary/glossary-terms.xml:3654(para) +msgid "A number within a database that is incremented each time a change is made. Used by swift when replicating." +msgstr "" + +#: ./doc/glossary/glossary-terms.xml:3660(glossterm) +msgid "Red Dwarf Lite" +msgstr "" + +#: ./doc/glossary/glossary-terms.xml:3662(para) +msgid "Community project that aims to provide database as a service." +msgstr "" + +#: ./doc/glossary/glossary-terms.xml:3667(glossterm) +msgid "Red Hat Enterprise Linux (RHEL)" +msgstr "" + +#: ./doc/glossary/glossary-terms.xml:3674(glossterm) +msgid "reference architecture" +msgstr "" + +#: ./doc/glossary/glossary-terms.xml:3676(para) +msgid "A recommended architecture for an OpenStack cloud." +msgstr "" + +#: ./doc/glossary/glossary-terms.xml:3681(glossterm) +msgid "region" +msgstr "" + +#: ./doc/glossary/glossary-terms.xml:3683(para) +msgid "A Discrete OpenStack environment with dedicated API endpoints that typically shares only the Identity Service (keystone) with other regions." +msgstr "" + +#: ./doc/glossary/glossary-terms.xml:3689(glossterm) +msgid "registry" +msgstr "" + +#: ./doc/glossary/glossary-terms.xml:3696(glossterm) +msgid "registry server" +msgstr "" + +#: ./doc/glossary/glossary-terms.xml:3698(para) +msgid "A glance service that provides VM image metadata information to clients." +msgstr "" + +#: ./doc/glossary/glossary-terms.xml:3703(glossterm) +msgid "Reliable, Autonomic Distributed Object Store (RADOS)" +msgstr "" + +#: ./doc/glossary/glossary-terms.xml:3706(para) +msgid "A collection of components that provides object storage within Ceph. Similar to swift." +msgstr "" + +#: ./doc/glossary/glossary-terms.xml:3711(glossterm) +msgid "Remote Procedure Call (RPC)" +msgstr "" + +#: ./doc/glossary/glossary-terms.xml:3713(para) +msgid "The method used by the nova RabbitMQ for intra-service communications." +msgstr "" + +#: ./doc/glossary/glossary-terms.xml:3718(glossterm) +msgid "replica" +msgstr "" + +#: ./doc/glossary/glossary-terms.xml:3720(para) +msgid "Provides data redundancy and fault tolerance by creating copies of swift objects, accounts, and containers so they are not lost when the underlying storage fails." +msgstr "" + +#: ./doc/glossary/glossary-terms.xml:3727(glossterm) +msgid "replica count" +msgstr "" + +#: ./doc/glossary/glossary-terms.xml:3729(para) +msgid "The number of replicas of the data in a swift ring." +msgstr "" + +#: ./doc/glossary/glossary-terms.xml:3734(glossterm) +msgid "replication" +msgstr "" + +#: ./doc/glossary/glossary-terms.xml:3736(para) +msgid "The process of copying data to a separate physical device for fault tolerance and performance." +msgstr "" + +#: ./doc/glossary/glossary-terms.xml:3742(glossterm) +msgid "replicator" +msgstr "" + +#: ./doc/glossary/glossary-terms.xml:3744(para) +msgid "The swift back-end process that creates and manages object replicas." +msgstr "" + +#: ./doc/glossary/glossary-terms.xml:3749(glossterm) +msgid "request ID" +msgstr "" + +#: ./doc/glossary/glossary-terms.xml:3751(para) +msgid "Unique ID assigned to each request sent to nova." +msgstr "" + +#: ./doc/glossary/glossary-terms.xml:3756(glossterm) +msgid "rescue image" +msgstr "" + +#: ./doc/glossary/glossary-terms.xml:3758(para) +msgid "A special type of VM image that is booted when an instance is placed into rescue mode. Allows an administrator to mount the file systems for an instance to correct the problem." +msgstr "" + +#: ./doc/glossary/glossary-terms.xml:3765(glossterm) +msgid "resize" +msgstr "" + +#: ./doc/glossary/glossary-terms.xml:3767(para) +msgid "Converts an existing server to a different flavor, which scales the server up or down. The original server is saved to enable rollback if a problem occurs. All resizes must be tested and explicitly confirmed, at which time the original server is removed." +msgstr "" + +#: ./doc/glossary/glossary-terms.xml:3776(glossterm) +msgid "RESTful" +msgstr "" + +#: ./doc/glossary/glossary-terms.xml:3778(para) +msgid "A kind of web service API that uses REST, or Representational State Transfer. REST is the style of architecture for hypermedia systems that is used for the World Wide Web." +msgstr "" + +#: ./doc/glossary/glossary-terms.xml:3785(glossterm) +msgid "ring" +msgstr "" + +#: ./doc/glossary/glossary-terms.xml:3787(para) +msgid "An entity that maps swift data to partitions. A separate ring exists for each service, such as account, object, and container." +msgstr "" + +#: ./doc/glossary/glossary-terms.xml:3793(glossterm) +msgid "ring builder" +msgstr "" + +#: ./doc/glossary/glossary-terms.xml:3795(para) +msgid "Builds and manages rings within swift, assigns partitions to devices, and pushes the configuration to other storage nodes." +msgstr "" + +#: ./doc/glossary/glossary-terms.xml:3801(glossterm) +msgid "Role Based Access Control (RBAC)" +msgstr "" + +#: ./doc/glossary/glossary-terms.xml:3803(para) +msgid "Provides a predefined list of actions that the user can perform such as start or stop VMs, reset passwords, and so on. Supported in both keystone and nova and can be configured using the horizon dashboard." +msgstr "" + +#: ./doc/glossary/glossary-terms.xml:3811(glossterm) +msgid "role ID" +msgstr "" + +#: ./doc/glossary/glossary-terms.xml:3813(para) +msgid "Alpha-numeric ID assigned to each keystone role." +msgstr "" + +#: ./doc/glossary/glossary-terms.xml:3818(glossterm) +msgid "rootwrap" +msgstr "" + +#: ./doc/glossary/glossary-terms.xml:3820(para) +msgid "A feature of nova that allows the unprivileged \"nova\" user to run a specified list of commands as the Linux root user." +msgstr "" + +#: ./doc/glossary/glossary-terms.xml:3826(glossterm) +msgid "round-robin scheduler" +msgstr "" + +#: ./doc/glossary/glossary-terms.xml:3828(para) +msgid "Type of nova scheduler that evenly distributes instances among available hosts." +msgstr "" + +#: ./doc/glossary/glossary-terms.xml:3833(glossterm) +msgid "routing key" +msgstr "" + +#: ./doc/glossary/glossary-terms.xml:3835(para) +msgid "the nova direct exchanges, fanout exchanges, and topic exchanges use this to determine how to process a message, processing varies depending on exchange type." +msgstr "" + +#: ./doc/glossary/glossary-terms.xml:3842(glossterm) +msgid "RPC driver" +msgstr "" + +#: ./doc/glossary/glossary-terms.xml:3844(para) +msgid "Modular system that allows the nova underlying message queue software to be changed. For example, from RabbitMQ to ZeroMQ or Qpid." +msgstr "" + +#: ./doc/glossary/glossary-terms.xml:3850(glossterm) +msgid "rsync" +msgstr "" + +#: ./doc/glossary/glossary-terms.xml:3852(para) +msgid "Used by swift to push object replicas." +msgstr "" + +#: ./doc/glossary/glossary-terms.xml:3856(glossterm) +msgid "RXTX cap" +msgstr "" + +#: ./doc/glossary/glossary-terms.xml:3858(para) +msgid "Absolute limit on the amount of network traffic a nova VM instance can send and receive." +msgstr "" + +#: ./doc/glossary/glossary-terms.xml:3863(glossterm) +msgid "RXTX quota" +msgstr "" + +#: ./doc/glossary/glossary-terms.xml:3865(para) +msgid "Soft limit on the amount of network traffic a nova VM instance can send and receive." +msgstr "" + +#: ./doc/glossary/glossary-terms.xml:3870(glossterm) +msgid "Ryu neutron plug-in" +msgstr "" + +#: ./doc/glossary/glossary-terms.xml:3872(para) +msgid "Enables the Ryu network operating system to function as a neutron OpenFlow controller." +msgstr "" + +#: ./doc/glossary/glossary-terms.xml:3879(title) +msgid "S" +msgstr "" + +#: ./doc/glossary/glossary-terms.xml:3881(glossterm) +msgid "S3" +msgstr "" + +#: ./doc/glossary/glossary-terms.xml:3883(para) +msgid "Object storage service by Amazon, similar in function to swift, can act as a back-end store for glance VM images." +msgstr "" + +#: ./doc/glossary/glossary-terms.xml:3889(glossterm) +msgid "Savanna" +msgstr "" + +#: ./doc/glossary/glossary-terms.xml:3891(para) +msgid "OpenStack project that provisions Hadoop on top of OpenStack to provide a data processing service." +msgstr "" + +#: ./doc/glossary/glossary-terms.xml:3897(glossterm) +msgid "scheduler manager" +msgstr "" + +#: ./doc/glossary/glossary-terms.xml:3899(para) +msgid "A nova component that determines where VM instances should start. Uses modular design to support a variety of scheduler types." +msgstr "" + +#: ./doc/glossary/glossary-terms.xml:3905(glossterm) +msgid "scoped token" +msgstr "" + +#: ./doc/glossary/glossary-terms.xml:3907(para) +msgid "A keystone API access token that is associated with a specific tenant." +msgstr "" + +#: ./doc/glossary/glossary-terms.xml:3912(glossterm) +msgid "scrubber" +msgstr "" + +#: ./doc/glossary/glossary-terms.xml:3914(para) +msgid "Checks for and deletes unused VM, the component of glance that implements delayed delete." +msgstr "" + +#: ./doc/glossary/glossary-terms.xml:3919(glossterm) +msgid "secret key" +msgstr "" + +#: ./doc/glossary/glossary-terms.xml:3921(para) +msgid "String of text only known by the user, used along with an access key to make requests to the nova API." +msgstr "" + +#: ./doc/glossary/glossary-terms.xml:3927(glossterm) +msgid "secure shell (SSH)" +msgstr "" + +#: ./doc/glossary/glossary-terms.xml:3929(para) +msgid "Open source tool used to access remote hosts through an encrypted communications channel, SSH key injection is supported by nova." +msgstr "" + +#: ./doc/glossary/glossary-terms.xml:3935(glossterm) +msgid "security group" +msgstr "" + +#: ./doc/glossary/glossary-terms.xml:3937(para) +msgid "A set of network traffic filtering rules that are applied to a nova instance." +msgstr "" + +#: ./doc/glossary/glossary-terms.xml:3942(glossterm) +msgid "segmented object" +msgstr "" + +#: ./doc/glossary/glossary-terms.xml:3944(para) +msgid "A swift large object that has been broken up into pieces, the re-assembled object is called a concatenated object." +msgstr "" + +#: ./doc/glossary/glossary-terms.xml:3950(glossterm) +msgid "server" +msgstr "" + +#: ./doc/glossary/glossary-terms.xml:3952(para) +msgid "Computer that provides explicit services to the client software running on that system, often managing a variety of computer operations." +msgstr "" + +#: ./doc/glossary/glossary-terms.xml:3955(para) +msgid "A server is a VM instance in the compute system. Flavor and image are requisite elements when creating a server." +msgstr "" + +#: ./doc/glossary/glossary-terms.xml:3961(glossterm) +msgid "server image" +msgstr "" + +#: ./doc/glossary/glossary-terms.xml:3963(para) +msgid "Alternative term for a VM image." +msgstr "" + +#: ./doc/glossary/glossary-terms.xml:3967(glossterm) +msgid "server UUID" +msgstr "" + +#: ./doc/glossary/glossary-terms.xml:3974(glossterm) +msgid "service catalog" +msgstr "" + +#: ./doc/glossary/glossary-terms.xml:3976(para) +msgid "Alternative term for the keystone catalog." +msgstr "" + +#: ./doc/glossary/glossary-terms.xml:3981(glossterm) +msgid "service ID" +msgstr "" + +#: ./doc/glossary/glossary-terms.xml:3983(para) +msgid "Unique ID assigned to each service that is available in the keystone catalog." +msgstr "" + +#: ./doc/glossary/glossary-terms.xml:3988(glossterm) +msgid "service registration" +msgstr "" + +#: ./doc/glossary/glossary-terms.xml:3990(para) +msgid "A keystone feature that enables services, such as nova, to automatically register with the catalog." +msgstr "" + +#: ./doc/glossary/glossary-terms.xml:3995(glossterm) +msgid "service tenant" +msgstr "" + +#: ./doc/glossary/glossary-terms.xml:3997(para) +msgid "Special keystone tenant that contains all services that are listed in the catalog." +msgstr "" + +#: ./doc/glossary/glossary-terms.xml:4002(glossterm) +msgid "service token" +msgstr "" + +#: ./doc/glossary/glossary-terms.xml:4004(para) +msgid "An administrator defined token used by nova to communicate securely with keystone." +msgstr "" + +#: ./doc/glossary/glossary-terms.xml:4009(glossterm) +msgid "session back-end" +msgstr "" + +#: ./doc/glossary/glossary-terms.xml:4011(para) +msgid "The method of storage used by horizon to track client sessions such as local memory, cookies, a database, or memcached." +msgstr "" + +#: ./doc/glossary/glossary-terms.xml:4017(glossterm) +msgid "session persistence" +msgstr "" + +#: ./doc/glossary/glossary-terms.xml:4019(para) +msgid "A feature of the load balancing service. It attempts to force subsequent connections to a service to be redirected to the same node as long as it is online." +msgstr "" + +#: ./doc/glossary/glossary-terms.xml:4026(glossterm) +msgid "session storage" +msgstr "" + +#: ./doc/glossary/glossary-terms.xml:4028(para) +msgid "A horizon component that stores and tracks client session information. Implemented through the Django sessions framework." +msgstr "" + +#: ./doc/glossary/glossary-terms.xml:4034(glossterm) +msgid "shared IP address" +msgstr "" + +#: ./doc/glossary/glossary-terms.xml:4036(para) +msgid "An IP address that can be assigned to a VM instance within the shared IP group. Public IP addresses can be shared across multiple servers for use in various high availability scenarios. When an IP address is shared to another server, the cloud network restrictions are modified to enable each server to listen to and respond on that IP address. You can optionally specify that the target server network configuration be modified. Shared IP addresses can be used with many standard heartbeat facilities, such as keepalive, that monitor for failure and manage IP failover." +msgstr "" + +#: ./doc/glossary/glossary-terms.xml:4052(glossterm) +msgid "shared IP group" +msgstr "" + +#: ./doc/glossary/glossary-terms.xml:4054(para) +msgid "A collection of servers that can share IPs with other members of the group. Any server in a group can share one or more public IPs with any other server in the group. With the exception of the first server in a shared IP group, servers must be launched into shared IP groups. A server may only be a member of one shared IP group." +msgstr "" + +#: ./doc/glossary/glossary-terms.xml:4064(glossterm) +msgid "shared storage" +msgstr "" + +#: ./doc/glossary/glossary-terms.xml:4066(para) +msgid "Block storage that is simultaneously accessible by multiple clients. For example, NFS." +msgstr "" + +#: ./doc/glossary/glossary-terms.xml:4071(glossterm) +msgid "Sheepdog" +msgstr "" + +#: ./doc/glossary/glossary-terms.xml:4073(para) +msgid "Distributed block storage system for QEMU, supported by OpenStack." +msgstr "" + +#: ./doc/glossary/glossary-terms.xml:4078(glossterm) +msgid "Simple Cloud Identity Management (SCIM)" +msgstr "" + +#: ./doc/glossary/glossary-terms.xml:4081(para) +msgid "Specification for managing identity in the cloud, currently unsupported by OpenStack." +msgstr "" + +#: ./doc/glossary/glossary-terms.xml:4086(glossterm) +msgid "Single-root I/O Virtualization (SR-IOV)" +msgstr "" + +#: ./doc/glossary/glossary-terms.xml:4089(para) +msgid "A specification that when implemented by a physical PCIe device enables it to appear as multiple separate PCIe devices. This enables multiple virtualized guests to share direct access to the physical device, offering improved performance over an equivalent virtual device. Currently supported in OpenStack Havana and later releases." +msgstr "" + +#: ./doc/glossary/glossary-terms.xml:4099(glossterm) +msgid "SmokeStack" +msgstr "" + +#: ./doc/glossary/glossary-terms.xml:4101(para) +msgid "Runs automated tests against the core OpenStack API, written in Rails." +msgstr "" + +#: ./doc/glossary/glossary-terms.xml:4106(glossterm) +msgid "snapshot" +msgstr "" + +#: ./doc/glossary/glossary-terms.xml:4108(para) +msgid "A point-in-time copy of an OpenStack storage volume or image. Use storage volume snapshots to back up volumes. Use image snapshots to back up data, or as \"gold\" images for additional servers." +msgstr "" + +#: ./doc/glossary/glossary-terms.xml:4116(glossterm) +msgid "soft reboot" +msgstr "" + +#: ./doc/glossary/glossary-terms.xml:4118(para) +msgid "A controlled reboot where a VM instance is properly restarted through operating system commands." +msgstr "" + +#: ./doc/glossary/glossary-terms.xml:4124(glossterm) +msgid "SolidFire Volume Driver" +msgstr "" + +#: ./doc/glossary/glossary-terms.xml:4126(para) +msgid "The nova volume driver for the SolidFire iSCSI storage appliance." +msgstr "" + +#: ./doc/glossary/glossary-terms.xml:4131(glossterm) +msgid "spread-first scheduler" +msgstr "" + +#: ./doc/glossary/glossary-terms.xml:4133(para) +msgid "The nova VM scheduling algorithm that attempts to start new VM on the host with the least amount of load." +msgstr "" + +#: ./doc/glossary/glossary-terms.xml:4139(glossterm) +msgid "SQL-Alchemy" +msgstr "" + +#: ./doc/glossary/glossary-terms.xml:4141(para) +msgid "An open source SQL toolkit for Python, used in OpenStack." +msgstr "" + +#: ./doc/glossary/glossary-terms.xml:4146(glossterm) +msgid "SQLite" +msgstr "" + +#: ./doc/glossary/glossary-terms.xml:4148(para) +msgid "A lightweight SQL database, used as the default persistent storage method in many OpenStack services." +msgstr "" + +#: ./doc/glossary/glossary-terms.xml:4154(glossterm) +msgid "StackTach" +msgstr "" + +#: ./doc/glossary/glossary-terms.xml:4156(para) +msgid "Community project that captures nova AMQP communications, useful for debugging." +msgstr "" + +#: ./doc/glossary/glossary-terms.xml:4161(glossterm) +msgid "static IP address" +msgstr "" + +#: ./doc/glossary/glossary-terms.xml:4163(para) +msgid "Alternative term for a fixed IP address." +msgstr "" + +#: ./doc/glossary/glossary-terms.xml:4167(glossterm) +msgid "StaticWeb" +msgstr "" + +#: ./doc/glossary/glossary-terms.xml:4169(para) +msgid "WSGI middleware component of swift that serves container data as a static web page." +msgstr "" + +#: ./doc/glossary/glossary-terms.xml:4174(glossterm) +msgid "storage back-end" +msgstr "" + +#: ./doc/glossary/glossary-terms.xml:4176(para) +msgid "The method that a service uses for persistent storage such as iSCSI, NFS, or local disk." +msgstr "" + +#: ./doc/glossary/glossary-terms.xml:4181(glossterm) +msgid "storage node" +msgstr "" + +#: ./doc/glossary/glossary-terms.xml:4183(para) +msgid "A swift node that provides container services, account services, and object services, controls the account databases, container databases, and object storage." +msgstr "" + +#: ./doc/glossary/glossary-terms.xml:4190(glossterm) +msgid "storage manager" +msgstr "" + +#: ./doc/glossary/glossary-terms.xml:4192(para) +msgid "A XenAPI component that provides a pluggable interface to support a wide variety of persistent storage back-ends." +msgstr "" + +#: ./doc/glossary/glossary-terms.xml:4198(glossterm) +msgid "storage manager back-end" +msgstr "" + +#: ./doc/glossary/glossary-terms.xml:4200(para) +msgid "A persistent storage method supported by XenAPI such as iSCSI or NFS." +msgstr "" + +#: ./doc/glossary/glossary-terms.xml:4205(glossterm) +msgid "storage services" +msgstr "" + +#: ./doc/glossary/glossary-terms.xml:4207(para) +msgid "Collective name for the swift object services, container services, and account services." +msgstr "" + +#: ./doc/glossary/glossary-terms.xml:4212(glossterm) +msgid "strategy" +msgstr "" + +#: ./doc/glossary/glossary-terms.xml:4214(para) +msgid "Specifies the authentication source used by glance or keystone." +msgstr "" + +#: ./doc/glossary/glossary-terms.xml:4219(glossterm) +msgid "subdomain" +msgstr "" + +#: ./doc/glossary/glossary-terms.xml:4221(para) +msgid "A domain within a parent domain. Subdomains cannot be registered. Subdomains enable you to delegate domains. Subdomains can themselves have subdomains, so third-level, fourth-level, fifth-level, and deeper levels of nesting are possible." +msgstr "" + +#: ./doc/glossary/glossary-terms.xml:4230(glossterm) +msgid "SUSE Linux Enterprise Server (SLES)" +msgstr "" + +#: ./doc/glossary/glossary-terms.xml:4237(glossterm) +msgid "suspend" +msgstr "" + +#: ./doc/glossary/glossary-terms.xml:4239(para) +msgid "Alternative term for a paused VM instance." +msgstr "" + +#: ./doc/glossary/glossary-terms.xml:4244(glossterm) +msgid "swap" +msgstr "" + +#: ./doc/glossary/glossary-terms.xml:4246(para) +msgid "Disk-based virtual memory, used by operating systems to provide more memory than is actually available on the system." +msgstr "" + +#: ./doc/glossary/glossary-terms.xml:4252(glossterm) +msgid "swawth" +msgstr "" + +#: ./doc/glossary/glossary-terms.xml:4254(para) +msgid "An authentication and authorization service for swift, implemented through WSGI middleware, uses swift itself as the persistent backing store." +msgstr "" + +#: ./doc/glossary/glossary-terms.xml:4261(glossterm) +msgid "Swift" +msgstr "" + +#: ./doc/glossary/glossary-terms.xml:4263(para) +msgid "An OpenStack core project that provides object storage services." +msgstr "" + +#: ./doc/glossary/glossary-terms.xml:4268(glossterm) +msgid "swift All in One (SAIO)" +msgstr "" + +#: ./doc/glossary/glossary-terms.xml:4270(para) +msgid "Creates a full swift development environment within a single VM." +msgstr "" + +#: ./doc/glossary/glossary-terms.xml:4275(glossterm) +msgid "swift middleware" +msgstr "" + +#: ./doc/glossary/glossary-terms.xml:4277(para) +msgid "Collective term for swift components that provide additional functionality." +msgstr "" + +#: ./doc/glossary/glossary-terms.xml:4282(glossterm) +msgid "swift proxy server" +msgstr "" + +#: ./doc/glossary/glossary-terms.xml:4284(para) +msgid "Acts as the gatekeeper to swift and is responsible for authenticating the user." +msgstr "" + +#: ./doc/glossary/glossary-terms.xml:4289(glossterm) +msgid "swift storage node" +msgstr "" + +#: ./doc/glossary/glossary-terms.xml:4291(para) +msgid "A node that runs swift account, container, and object services." +msgstr "" + +#: ./doc/glossary/glossary-terms.xml:4296(glossterm) +msgid "sync point" +msgstr "" + +#: ./doc/glossary/glossary-terms.xml:4298(para) +msgid "Point in time since the last container and accounts database sync among nodes within swift." +msgstr "" + +#: ./doc/glossary/glossary-terms.xml:4304(glossterm) +msgid "sysadmin" +msgstr "" + +#: ./doc/glossary/glossary-terms.xml:4306(para) +msgid "One of the default roles in the nova RBAC system. Enables a user to add other users to a project, interact with VM images that are associated with the project, and start and stop VM (VM) instances." +msgstr "" + +#: ./doc/glossary/glossary-terms.xml:4313(glossterm) +msgid "system usage" +msgstr "" + +#: ./doc/glossary/glossary-terms.xml:4315(para) +msgid "A nova component that, along with the notification system, collects metrics and usage information. Can be used for billing." +msgstr "" + +#: ./doc/glossary/glossary-terms.xml:4323(title) +msgid "T" +msgstr "" + +#: ./doc/glossary/glossary-terms.xml:4325(glossterm) +msgid "TempAuth" +msgstr "" + +#: ./doc/glossary/glossary-terms.xml:4327(para) +msgid "An authentication facility within swift that enables swift itself to perform authentication and authorization. Frequently used in testing and development." +msgstr "" + +#: ./doc/glossary/glossary-terms.xml:4334(glossterm) +msgid "Tempest" +msgstr "" + +#: ./doc/glossary/glossary-terms.xml:4336(para) +msgid "Automated software test suite designed to run against the trunk of the OpenStack core project." +msgstr "" + +#: ./doc/glossary/glossary-terms.xml:4342(glossterm) +msgid "TempURL" +msgstr "" + +#: ./doc/glossary/glossary-terms.xml:4344(para) +msgid "A swift middleware component that enables creation of URLs for temporary object access." +msgstr "" + +#: ./doc/glossary/glossary-terms.xml:4348(glossterm) +msgid "tenant" +msgstr "" + +#: ./doc/glossary/glossary-terms.xml:4350(para) +msgid "A group of users, used to isolate access to nova resources. An alternative term for a nova project." +msgstr "" + +#: ./doc/glossary/glossary-terms.xml:4356(glossterm) +msgid "Tenant API" +msgstr "" + +#: ./doc/glossary/glossary-terms.xml:4358(para) +msgid "An API that is accessible to tenants." +msgstr "" + +#: ./doc/glossary/glossary-terms.xml:4362(glossterm) +msgid "tenant endpoint" +msgstr "" + +#: ./doc/glossary/glossary-terms.xml:4364(para) +msgid "A keystone API endpoint that is associated with one or more tenants." +msgstr "" + +#: ./doc/glossary/glossary-terms.xml:4369(glossterm) +msgid "tenant ID" +msgstr "" + +#: ./doc/glossary/glossary-terms.xml:4371(para) +msgid "Unique ID assigned to each tenant within keystone, the nova project IDs map to the keystone tenant IDs." +msgstr "" + +#: ./doc/glossary/glossary-terms.xml:4377(glossterm) +msgid "token" +msgstr "" + +#: ./doc/glossary/glossary-terms.xml:4379(para) +msgid "An alpha-numeric string of text used to access OpenStack APIs and resources." +msgstr "" + +#: ./doc/glossary/glossary-terms.xml:4384(glossterm) +msgid "token services" +msgstr "" + +#: ./doc/glossary/glossary-terms.xml:4386(para) +msgid "A keystone component that manages and validates tokens after a user or tenant has been authenticated." +msgstr "" + +#: ./doc/glossary/glossary-terms.xml:4392(glossterm) +msgid "tombstone" +msgstr "" + +#: ./doc/glossary/glossary-terms.xml:4394(para) +msgid "Used to mark swift objects that have been deleted, ensures the object is not updated on another node after it has been deleted." +msgstr "" + +#: ./doc/glossary/glossary-terms.xml:4400(glossterm) +msgid "topic publisher" +msgstr "" + +#: ./doc/glossary/glossary-terms.xml:4402(para) +msgid "A process that is created when a RPC call is executed, used to push the message to the topic exchange." +msgstr "" + +#: ./doc/glossary/glossary-terms.xml:4408(glossterm) +msgid "Torpedo" +msgstr "" + +#: ./doc/glossary/glossary-terms.xml:4410(para) +msgid "Community project used to run automated tests against the OpenStack API." +msgstr "" + +#: ./doc/glossary/glossary-terms.xml:4415(glossterm) +msgid "transaction ID" +msgstr "" + +#: ./doc/glossary/glossary-terms.xml:4417(para) +msgid "Unique ID assigned to each swift request, used for debugging and tracing." +msgstr "" + +#: ./doc/glossary/glossary-terms.xml:4422(glossterm) +msgid "transient" +msgstr "" + +#: ./doc/glossary/glossary-terms.xml:4424(para) +msgid "Alternative term for non-durable." +msgstr "" + +#: ./doc/glossary/glossary-terms.xml:4428(glossterm) +msgid "transient exchange" +msgstr "" + +#: ./doc/glossary/glossary-terms.xml:4430(para) +msgid "Alternative term for a non-durable exchange." +msgstr "" + +#: ./doc/glossary/glossary-terms.xml:4435(glossterm) +msgid "transient message" +msgstr "" + +#: ./doc/glossary/glossary-terms.xml:4437(para) +msgid "A message that is stored in memory and is lost after the server is restarted." +msgstr "" + +#: ./doc/glossary/glossary-terms.xml:4442(glossterm) +msgid "transient queue" +msgstr "" + +#: ./doc/glossary/glossary-terms.xml:4444(para) +msgid "Alternative term for a non-durable queue." +msgstr "" + +#: ./doc/glossary/glossary-terms.xml:4448(glossterm) +msgid "Trove" +msgstr "" + +#: ./doc/glossary/glossary-terms.xml:4450(para) +msgid "OpenStack project that provides database services to applications." +msgstr "" + +#: ./doc/glossary/glossary-terms.xml:4464(title) +msgid "U" +msgstr "" + +#: ./doc/glossary/glossary-terms.xml:4466(glossterm) +msgid "Ubuntu" +msgstr "" + +#: ./doc/glossary/glossary-terms.xml:4468(para) +msgid "A Debian-based Linux distribution." +msgstr "" + +#: ./doc/glossary/glossary-terms.xml:4472(glossterm) +msgid "unscoped token" +msgstr "" + +#: ./doc/glossary/glossary-terms.xml:4474(para) +msgid "Alternative term for a keystone default token." +msgstr "" + +#: ./doc/glossary/glossary-terms.xml:4479(glossterm) +msgid "updater" +msgstr "" + +#: ./doc/glossary/glossary-terms.xml:4481(para) +msgid "Collective term for a group of swift components that processes queued and failed updates for containers and objects." +msgstr "" + +#: ./doc/glossary/glossary-terms.xml:4487(glossterm) +msgid "user" +msgstr "" + +#: ./doc/glossary/glossary-terms.xml:4489(para) +msgid "In keystone each user is associated with one or more tenants, and in nova they can be associated with roles, projects, or both." +msgstr "" + +#: ./doc/glossary/glossary-terms.xml:4495(glossterm) +msgid "user data" +msgstr "" + +#: ./doc/glossary/glossary-terms.xml:4497(para) +msgid "A blob of data that can be specified by the user when launching an instance. This data can be accessed by the instance through the metadata service or config drive. Commonly used for passing a shell script that is executed by the instance on boot." +msgstr "" + +#: ./doc/glossary/glossary-terms.xml:4506(glossterm) +msgid "User Mode Linux (UML)" +msgstr "" + +#: ./doc/glossary/glossary-terms.xml:4520(title) +msgid "V" +msgstr "" + +#: ./doc/glossary/glossary-terms.xml:4522(glossterm) +msgid "VIF UUID" +msgstr "" + +#: ./doc/glossary/glossary-terms.xml:4524(para) +msgid "Unique ID assigned to each neutron VIF." +msgstr "" + +#: ./doc/glossary/glossary-terms.xml:4528(glossterm) +msgid "Virtual Central Processing Unit (vCPU)" +msgstr "" + +#: ./doc/glossary/glossary-terms.xml:4531(para) +msgid "Sub-divides physical CPUs. Instances can then use those divisions." +msgstr "" + +#: ./doc/glossary/glossary-terms.xml:4536(glossterm) +msgid "Virtual Disk Image (VDI)" +msgstr "" + +#: ./doc/glossary/glossary-terms.xml:4543(glossterm) +msgid "Virtual Hard Disk (VHD)" +msgstr "" + +#: ./doc/glossary/glossary-terms.xml:4550(glossterm) +msgid "virtual IP" +msgstr "" + +#: ./doc/glossary/glossary-terms.xml:4552(para) +msgid "An Internet Protocol (IP) address configured on the load balancer for use by clients connecting to a service that is load balanced. Incoming connections are distributed to back-end nodes based on the configuration of the load balancer." +msgstr "" + +#: ./doc/glossary/glossary-terms.xml:4561(glossterm) +msgid "virtual machine (VM)" +msgstr "" + +#: ./doc/glossary/glossary-terms.xml:4563(para) +msgid "An operating system instance that runs on top of a hypervisor. Multiple VMs can run at the same time on the same physical host." +msgstr "" + +#: ./doc/glossary/glossary-terms.xml:4569(glossterm) +msgid "virtual network" +msgstr "" + +#: ./doc/glossary/glossary-terms.xml:4571(para) +msgid "An L2 network segment within neutron." +msgstr "" + +#: ./doc/glossary/glossary-terms.xml:4575(glossterm) +msgid "Virtual Network Computing (VNC)" +msgstr "" + +#: ./doc/glossary/glossary-terms.xml:4577(para) +msgid "Open source GUI and CLI tools used for remote console access to VMs. Supported by nova." +msgstr "" + +#: ./doc/glossary/glossary-terms.xml:4582(glossterm) +msgid "Virtual Network InterFace (VIF)" +msgstr "" + +#: ./doc/glossary/glossary-terms.xml:4584(para) +msgid "An interface that is plugged into a port in a neutron network. Typically a virtual network interface belonging to a VM." +msgstr "" + +#: ./doc/glossary/glossary-terms.xml:4590(glossterm) +msgid "virtual port" +msgstr "" + +#: ./doc/glossary/glossary-terms.xml:4592(para) +msgid "Attachment point where a virtual interface connects to a virtual network." +msgstr "" + +#: ./doc/glossary/glossary-terms.xml:4597(glossterm) +msgid "virtual private network (VPN)" +msgstr "" + +#: ./doc/glossary/glossary-terms.xml:4599(para) +msgid "Provided by nova in the form of cloudpipes, specialized instances that are used to create VPNs on a per-project basis." +msgstr "" + +#: ./doc/glossary/glossary-terms.xml:4605(glossterm) +msgid "virtual server" +msgstr "" + +#: ./doc/glossary/glossary-terms.xml:4607(para) +msgid "Alternative term for a VM or guest." +msgstr "" + +#: ./doc/glossary/glossary-terms.xml:4611(glossterm) +msgid "virtual switch (vSwitch)" +msgstr "" + +#: ./doc/glossary/glossary-terms.xml:4613(para) +msgid "Software that runs on a host or node and provides the features and functions of a hardware based network switch." +msgstr "" + +#: ./doc/glossary/glossary-terms.xml:4619(glossterm) +msgid "virtual VLAN" +msgstr "" + +#: ./doc/glossary/glossary-terms.xml:4621(para) +msgid "Alternative term for a virtual network." +msgstr "" + +#: ./doc/glossary/glossary-terms.xml:4625(glossterm) +msgid "VirtualBox" +msgstr "" + +#: ./doc/glossary/glossary-terms.xml:4631(glossterm) +msgid "VLAN manager" +msgstr "" + +#: ./doc/glossary/glossary-terms.xml:4633(para) +msgid "A nova component that provides dnsmasq, radvd, and sets up forwarding to and from cloudpipe instances." +msgstr "" + +#: ./doc/glossary/glossary-terms.xml:4639(glossterm) +msgid "VLAN network" +msgstr "" + +#: ./doc/glossary/glossary-terms.xml:4641(para) +msgid "The Network Controller provides virtual networks to enable compute servers to interact with each other and with the public network. All machines must have a public and private network interface. A VLAN network is a private network interface, which is controlled by the vlan_interface option with VLAN managers." +msgstr "" + +#: ./doc/glossary/glossary-terms.xml:4651(glossterm) +msgid "VM disk (VMDK)" +msgstr "" + +#: ./doc/glossary/glossary-terms.xml:4658(glossterm) +msgid "VM image" +msgstr "" + +#: ./doc/glossary/glossary-terms.xml:4660(para) +msgid "Alternative term for an image." +msgstr "" + +#: ./doc/glossary/glossary-terms.xml:4664(glossterm) +msgid "VM Remote Control (VMRC)" +msgstr "" + +#: ./doc/glossary/glossary-terms.xml:4666(para) +msgid "Method to access VM instance consoles using a web browser. Supported by nova." +msgstr "" + +#: ./doc/glossary/glossary-terms.xml:4671(glossterm) +msgid "VMware API" +msgstr "" + +#: ./doc/glossary/glossary-terms.xml:4673(para) +msgid "Supports interaction with VMware products in nova." +msgstr "" + +#: ./doc/glossary/glossary-terms.xml:4678(glossterm) +msgid "VNC proxy" +msgstr "" + +#: ./doc/glossary/glossary-terms.xml:4680(para) +msgid "A nova component that provides users access to the consoles of their VM instances through VNC or VMRC." +msgstr "" + +#: ./doc/glossary/glossary-terms.xml:4686(glossterm) +msgid "volume" +msgstr "" + +#: ./doc/glossary/glossary-terms.xml:4688(para) +msgid "Disk-based data storage generally represented as an iSCSI target with a file system that supports extended attributes, can be persistent or ephemeral." +msgstr "" + +#: ./doc/glossary/glossary-terms.xml:4695(glossterm) +msgid "Volume API" +msgstr "" + +#: ./doc/glossary/glossary-terms.xml:4697(para) +msgid "An API on a separate endpoint for attaching, detaching, and creating block storage for compute VMs." +msgstr "" + +#: ./doc/glossary/glossary-terms.xml:4703(glossterm) +msgid "volume controller" +msgstr "" + +#: ./doc/glossary/glossary-terms.xml:4705(para) +msgid "A nova component that oversees and coordinates storage volume actions." +msgstr "" + +#: ./doc/glossary/glossary-terms.xml:4710(glossterm) +msgid "volume driver" +msgstr "" + +#: ./doc/glossary/glossary-terms.xml:4712(para) +msgid "Alternative term for a volume plug-in." +msgstr "" + +#: ./doc/glossary/glossary-terms.xml:4716(glossterm) +msgid "volume ID" +msgstr "" + +#: ./doc/glossary/glossary-terms.xml:4718(para) +msgid "Unique ID applied to each storage volume under the nova control." +msgstr "" + +#: ./doc/glossary/glossary-terms.xml:4723(glossterm) +msgid "volume manager" +msgstr "" + +#: ./doc/glossary/glossary-terms.xml:4725(para) +msgid "A nova component that creates, attaches, and detaches persistent storage volumes." +msgstr "" + +#: ./doc/glossary/glossary-terms.xml:4730(glossterm) +msgid "volume node" +msgstr "" + +#: ./doc/glossary/glossary-terms.xml:4732(para) +msgid "A nova node that runs the cinder-volume daemon." +msgstr "" + +#: ./doc/glossary/glossary-terms.xml:4737(glossterm) +msgid "volume plug-in" +msgstr "" + +#: ./doc/glossary/glossary-terms.xml:4739(para) +msgid "Provides support for new and specialized types of back-end storage for the nova volume manager." +msgstr "" + +#: ./doc/glossary/glossary-terms.xml:4745(glossterm) +msgid "Volume Service API" +msgstr "" + +#: ./doc/glossary/glossary-terms.xml:4747(para) +msgid "Alternative term for the nova volume API." +msgstr "" + +#: ./doc/glossary/glossary-terms.xml:4751(glossterm) +msgid "volume worker" +msgstr "" + +#: ./doc/glossary/glossary-terms.xml:4753(para) +msgid "A cinder component that interacts with back-end storage to manage the creation and deletion of volumes and the creation of compute volumes, provided by the cinder-volume daemon." +msgstr "" + +#: ./doc/glossary/glossary-terms.xml:4760(glossterm) +msgid "vSphere" +msgstr "" + +#: ./doc/glossary/glossary-terms.xml:4774(title) +msgid "W" +msgstr "" + +#: ./doc/glossary/glossary-terms.xml:4776(glossterm) +msgid "weighing" +msgstr "" + +#: ./doc/glossary/glossary-terms.xml:4778(para) +msgid "A nova process that determines the suitability of the VM instances for a job for a particular host. For example, not enough RAM on the host, too many CPUs on the host, and so on." +msgstr "" + +#: ./doc/glossary/glossary-terms.xml:4785(glossterm) +msgid "weight" +msgstr "" + +#: ./doc/glossary/glossary-terms.xml:4787(para) +msgid "Used by swift storage devices to determine which storage devices are suitable for the job. Devices are weighted by size." +msgstr "" + +#: ./doc/glossary/glossary-terms.xml:4793(glossterm) +msgid "weighted cost" +msgstr "" + +#: ./doc/glossary/glossary-terms.xml:4795(para) +msgid "The sum of each cost used when deciding where to start a new VM instance in nova." +msgstr "" + +#: ./doc/glossary/glossary-terms.xml:4800(glossterm) +msgid "worker" +msgstr "" + +#: ./doc/glossary/glossary-terms.xml:4802(para) +msgid "A daemon that listens to a queue and carries out tasks in response to messages. For example, the cinder-volume worker attaches storage to instances." +msgstr "" + +#: ./doc/glossary/glossary-terms.xml:4816(title) +msgid "X" +msgstr "" + +#: ./doc/glossary/glossary-terms.xml:4818(glossterm) +msgid "Xen API" +msgstr "" + +#: ./doc/glossary/glossary-terms.xml:4820(para) +msgid "The Xen administrative API, which is supported by nova." +msgstr "" + +#: ./doc/glossary/glossary-terms.xml:4825(glossterm) +msgid "Xen Cloud Platform (XCP)" +msgstr "" + +#: ./doc/glossary/glossary-terms.xml:4831(glossterm) +msgid "Xen Storage Manager Volume Driver" +msgstr "" + +#: ./doc/glossary/glossary-terms.xml:4833(para) +msgid "A nova volume plug-in that enables communication with the Xen Storage Manager API." +msgstr "" + +#: ./doc/glossary/glossary-terms.xml:4839(glossterm) +msgid "XenServer" +msgstr "" + +#: ./doc/glossary/glossary-terms.xml:4853(title) +msgid "Y" +msgstr "" + +#: ./doc/glossary/glossary-terms.xml:4863(title) +msgid "Z" +msgstr "" + +#: ./doc/glossary/glossary-terms.xml:4865(glossterm) +msgid "ZeroMQ" +msgstr "" + +#: ./doc/glossary/glossary-terms.xml:4867(para) +msgid "Message queue software supported by OpenStack. An alternative to RabbitMQ. Also spelled 0MQ." +msgstr "" + +#: ./doc/glossary/glossary-terms.xml:4873(glossterm) +msgid "Zuul" +msgstr "" + +#: ./doc/glossary/glossary-terms.xml:4875(para) +msgid "Tool used in OpenStack development to ensure correctly ordered testing of changes in parallel." +msgstr "" + +#: ./doc/glossary/openstack-glossary.xml:9(title) ./doc/glossary/openstack-glossary.xml:12(title) +msgid "OpenStack Glossary" +msgstr "" + +#: ./doc/glossary/openstack-glossary.xml:13(para) +msgid "Use this glossary to get definitions of OpenStack-related words and phrases." +msgstr "" + +#: ./doc/glossary/openstack-glossary.xml:15(para) +msgid "To add to this glossary, fork the openstack-manuals repository on github.com and update the source files through the OpenStack contribution process." +msgstr "" + +#. Put one translator per line, in the form of NAME , YEAR1, YEAR2 +#: ./doc/glossary/openstack-glossary.xml:0(None) +msgid "translator-credits" +msgstr "" + diff --git a/doc/glossary/locale/he_IL.po b/doc/glossary/locale/he_IL.po new file mode 100644 index 0000000000..5dbc1a8b3c --- /dev/null +++ b/doc/glossary/locale/he_IL.po @@ -0,0 +1,5782 @@ +# +# Translators: +msgid "" +msgstr "" +"Project-Id-Version: OpenStack Manuals\n" +"POT-Creation-Date: 2014-01-30 06:24+0000\n" +"PO-Revision-Date: 2014-01-21 01:25+0000\n" +"Last-Translator: daisy.ycguo \n" +"Language-Team: Hebrew (Israel) (http://www.transifex.com/projects/p/openstack/language/he_IL/)\n" +"MIME-Version: 1.0\n" +"Content-Type: text/plain; charset=UTF-8\n" +"Content-Transfer-Encoding: 8bit\n" +"Language: he_IL\n" +"Plural-Forms: nplurals=2; plural=(n != 1);\n" + +#: ./doc/glossary/glossary-terms.xml5(title) +msgid "Glossary" +msgstr "" + +#: ./doc/glossary/glossary-terms.xml8(para) +msgid "" +"Licensed under the Apache License, Version 2.0 (the \"License\"); you may " +"not use this file except in compliance with the License. You may obtain a " +"copy of the License at" +msgstr "" + +#: ./doc/glossary/glossary-terms.xml15(link) +msgid "http://www.apache.org/licenses/LICENSE-2.0" +msgstr "" + +#: ./doc/glossary/glossary-terms.xml17(para) +msgid "" +"Unless required by applicable law or agreed to in writing, software " +"distributed under the License is distributed on an \"AS IS\" BASIS, WITHOUT " +"WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. See the " +"License for the specific language governing permissions and limitations " +"under the License." +msgstr "" + +#: ./doc/glossary/glossary-terms.xml27(title) +msgid "A" +msgstr "" + +#: ./doc/glossary/glossary-terms.xml29(glossterm) +msgid "absolute limit" +msgstr "" + +#: ./doc/glossary/glossary-terms.xml31(para) +msgid "" +"Impassable limits for nova VMs. Settings include total RAM size, maximum " +"number of vCPUs, and maximum disk size." +msgstr "" + +#: ./doc/glossary/glossary-terms.xml37(glossterm) +msgid "access control list" +msgstr "" + +#: ./doc/glossary/glossary-terms.xml39(para) +msgid "" +"A list of permissions attached to an object. An ACL specifies which users or" +" system processes have access to objects. It also defines which operations " +"can be performed on specified objects. Each entry in a typical ACL specifies" +" a subject and an operation. For instance, ACL entry, (Alice, " +"delete), for a file gives Alice permission to delete the file." +msgstr "" + +#: ./doc/glossary/glossary-terms.xml45(glossterm) +msgid "access key" +msgstr "" + +#: ./doc/glossary/glossary-terms.xml47(para) +msgid "Alternative term for an Amazon EC2 access key. See EC2 Access key." +msgstr "" + +#: ./doc/glossary/glossary-terms.xml52(glossterm) +msgid "account" +msgstr "" + +#: ./doc/glossary/glossary-terms.xml54(para) +msgid "" +"The swift context of an account. Do not confuse with a user account from an " +"identity service such as Active Directory, /etc/passwd, OpenLDAP, keystone, " +"and so on." +msgstr "" + +#: ./doc/glossary/glossary-terms.xml61(glossterm) +msgid "account auditor" +msgstr "" + +#: ./doc/glossary/glossary-terms.xml63(para) +msgid "" +"Checks for missing replicas, incorrect, and corrupted objects in a specified" +" swift account by running queries against the back-end SQLite database." +msgstr "" + +#: ./doc/glossary/glossary-terms.xml70(glossterm) +msgid "account database" +msgstr "" + +#: ./doc/glossary/glossary-terms.xml72(para) +msgid "" +"A SQLite database that contains swift accounts and related metadata and is " +"accessed by the accounts server." +msgstr "" + +#: ./doc/glossary/glossary-terms.xml78(glossterm) +msgid "account reaper" +msgstr "" + +#: ./doc/glossary/glossary-terms.xml80(para) +msgid "" +"A swift worker that scans for and deletes account databases that are marked " +"for deletion on an account server." +msgstr "" + +#: ./doc/glossary/glossary-terms.xml86(glossterm) +msgid "account server" +msgstr "" + +#: ./doc/glossary/glossary-terms.xml88(para) +msgid "" +"Lists containers in swift and stores container information in the account " +"database." +msgstr "" + +#: ./doc/glossary/glossary-terms.xml93(glossterm) +msgid "account service" +msgstr "" + +#: ./doc/glossary/glossary-terms.xml95(para) +msgid "" +"A swift component that provides account services such as list, create, " +"modify, and audit. Do not confuse with keystone, OpenLDAP, or similar user " +"account services." +msgstr "" + +#: ./doc/glossary/glossary-terms.xml102(glossterm) +msgid "accounting" +msgstr "" + +#: ./doc/glossary/glossary-terms.xml104(para) +msgid "" +"The Compute Service provides accounting information through the event " +"notification and system usage data facilities." +msgstr "" + +#: ./doc/glossary/glossary-terms.xml110(glossterm) +msgid "ACL" +msgstr "" + +#: ./doc/glossary/glossary-terms.xml112(para) +msgid "See access control list." +msgstr "" + +#: ./doc/glossary/glossary-terms.xml116(glossterm) +msgid "Active Directory" +msgstr "" + +#: ./doc/glossary/glossary-terms.xml118(para) +msgid "" +"Authentication and Identity Service by Microsoft, based on LDAP. Supported " +"in OpenStack." +msgstr "" + +#: ./doc/glossary/glossary-terms.xml124(glossterm) +msgid "address pool" +msgstr "" + +#: ./doc/glossary/glossary-terms.xml126(para) +msgid "" +"A group of fixed and/or floating IP addresses that are assigned to a nova " +"project and can be used by or assigned to the VM instances in a project." +msgstr "" + +#: ./doc/glossary/glossary-terms.xml133(glossterm) +msgid "admin API" +msgstr "" + +#: ./doc/glossary/glossary-terms.xml135(para) +msgid "" +"A subset of API calls that are accessible to authorized administrators and " +"are generally not accessible to end users or the public internet, can exist " +"as a separate service (keystone) or can be a subset of another API (nova)." +msgstr "" + +#: ./doc/glossary/glossary-terms.xml143(glossterm) +msgid "admin server" +msgstr "" + +#: ./doc/glossary/glossary-terms.xml145(para) +msgid "" +"In the context of keystone, the worker process that provides access to the " +"admin API." +msgstr "" + +#: ./doc/glossary/glossary-terms.xml150(glossterm) +msgid "Advanced Message Queuing Protocol (AMQP)" +msgstr "" + +#: ./doc/glossary/glossary-terms.xml153(para) +msgid "" +"The open standard messaging protocol used by nova for intra-service " +"communications, provided by RabbitMQ (the default), Qpid, or ZeroMQ." +msgstr "" + +#: ./doc/glossary/glossary-terms.xml159(glossterm) +msgid "Advanced RISC Machine (ARM)" +msgstr "" + +#: ./doc/glossary/glossary-terms.xml161(para) +msgid "" +"Lower power consumption CPU often found in mobile and embedded devices. " +"Supported by OpenStack." +msgstr "" + +#: ./doc/glossary/glossary-terms.xml167(glossterm) +msgid "alert" +msgstr "" + +#: ./doc/glossary/glossary-terms.xml169(para) +msgid "" +"The Compute Service can send alerts through its notification system, which " +"includes a facility to create custom notification drivers. Alerts can be " +"sent to and displayed on the horizon dashboard." +msgstr "" + +#: ./doc/glossary/glossary-terms.xml176(glossterm) +msgid "allocate" +msgstr "" + +#: ./doc/glossary/glossary-terms.xml178(para) +msgid "" +"The process of taking floating IP address from the address pool so it can be" +" associated with a fixed IP on a nova VM instance." +msgstr "" + +#: ./doc/glossary/glossary-terms.xml184(glossterm) +msgid "Amazon Kernel Image (AKI)" +msgstr "" + +#: ./doc/glossary/glossary-terms.xml186(para) +#: ./doc/glossary/glossary-terms.xml193(para) +#: ./doc/glossary/glossary-terms.xml200(para) +msgid "Both a VM container format and disk format. Supported by glance." +msgstr "" + +#: ./doc/glossary/glossary-terms.xml191(glossterm) +msgid "Amazon Machine Image (AMI)" +msgstr "" + +#: ./doc/glossary/glossary-terms.xml198(glossterm) +msgid "Amazon Ramdisk Image (ARI)" +msgstr "" + +#: ./doc/glossary/glossary-terms.xml205(glossterm) +msgid "AMQP" +msgstr "" + +#: ./doc/glossary/glossary-terms.xml207(para) +msgid "" +"Advanced Message Queue Protocol. An open Internet protocol for reliably " +"sending and receiving messages. It enables building a diverse, coherent " +"messaging ecosystem." +msgstr "" + +#: ./doc/glossary/glossary-terms.xml214(glossterm) +msgid "Anvil" +msgstr "" + +#: ./doc/glossary/glossary-terms.xml216(para) +msgid "" +"A project that ports the shell script-based project named devstack to " +"Python." +msgstr "" + +#: ./doc/glossary/glossary-terms.xml221(glossterm) +msgid "Apache" +msgstr "" + +#: ./doc/glossary/glossary-terms.xml223(para) +msgid "" +"The Apache Software Foundation supports the Apache community of open-source " +"software projects. These projects provide software products for the public " +"good." +msgstr "" + +#: ./doc/glossary/glossary-terms.xml230(glossterm) +msgid "Apache License 2.0" +msgstr "" + +#: ./doc/glossary/glossary-terms.xml232(para) +msgid "" +"All OpenStack core projects are provided under the terms of the Apache " +"License 2.0 license." +msgstr "" + +#: ./doc/glossary/glossary-terms.xml238(glossterm) +msgid "Apache Web Server" +msgstr "" + +#: ./doc/glossary/glossary-terms.xml240(para) +msgid "The most common web server software currently used on the Internet." +msgstr "" + +#: ./doc/glossary/glossary-terms.xml245(glossterm) +msgid "API" +msgstr "" + +#: ./doc/glossary/glossary-terms.xml247(para) +msgid "Application programming interface." +msgstr "" + +#: ./doc/glossary/glossary-terms.xml251(glossterm) +msgid "API endpoint" +msgstr "" + +#: ./doc/glossary/glossary-terms.xml253(para) +msgid "" +"The daemon, worker, or service that a client communicates with to access an " +"API. API endpoints can provide any number of services such as keystone " +"authentication, sales data, performance metrics, nova VM commands, census " +"data, and so on." +msgstr "" + +#: ./doc/glossary/glossary-terms.xml262(glossterm) +msgid "API extension" +msgstr "" + +#: ./doc/glossary/glossary-terms.xml264(para) +msgid "" +"A nova and neutron feature that enables custom modules to extend the core " +"APIs." +msgstr "" + +#: ./doc/glossary/glossary-terms.xml269(glossterm) +msgid "API extension plug-in" +msgstr "" + +#: ./doc/glossary/glossary-terms.xml271(para) +msgid "Alternative term for a neutron plug-in or neutron API extension." +msgstr "" + +#: ./doc/glossary/glossary-terms.xml276(glossterm) +msgid "API key" +msgstr "" + +#: ./doc/glossary/glossary-terms.xml278(para) +msgid "Alternative term for an API token." +msgstr "" + +#: ./doc/glossary/glossary-terms.xml282(glossterm) +msgid "API server" +msgstr "" + +#: ./doc/glossary/glossary-terms.xml284(para) +msgid "Any node running a daemon or worker that provides an API endpoint." +msgstr "" + +#: ./doc/glossary/glossary-terms.xml289(glossterm) +msgid "API token" +msgstr "" + +#: ./doc/glossary/glossary-terms.xml291(para) +msgid "" +"Passed to API requests and used by OpenStack to verify that the client is " +"authorized to run the requested operation." +msgstr "" + +#: ./doc/glossary/glossary-terms.xml297(glossterm) +msgid "API version" +msgstr "" + +#: ./doc/glossary/glossary-terms.xml299(para) +msgid "" +"In OpenStack, a the API version for a project is part of the URL. For " +"example, example.com/nova/v1/foobar." +msgstr "" + +#: ./doc/glossary/glossary-terms.xml305(glossterm) +msgid "applet" +msgstr "" + +#: ./doc/glossary/glossary-terms.xml307(para) +msgid "A Java program that can be embedded into a web page." +msgstr "" + +#: ./doc/glossary/glossary-terms.xml312(glossterm) +msgid "Application Programming Interface (API)" +msgstr "" + +#: ./doc/glossary/glossary-terms.xml315(para) +msgid "" +"A collection of specifications used to access a service, application, or " +"program. Includes service calls, required parameters for each call, and the " +"expected return values." +msgstr "" + +#: ./doc/glossary/glossary-terms.xml322(glossterm) +msgid "application server" +msgstr "" + +#: ./doc/glossary/glossary-terms.xml324(para) +msgid "" +"A piece of software that makes available another piece of software over a " +"network." +msgstr "" + +#: ./doc/glossary/glossary-terms.xml329(glossterm) +msgid "Application Service Provider (ASP)" +msgstr "" + +#: ./doc/glossary/glossary-terms.xml331(para) +msgid "" +"Companies that rent specialized applications that help businesses and " +"organizations provide additional services with less cost." +msgstr "" + +#: ./doc/glossary/glossary-terms.xml337(glossterm) +msgid "arptables" +msgstr "" + +#: ./doc/glossary/glossary-terms.xml339(para) +msgid "" +"Used along with iptables, ebtables, and ip6tables in nova to provide " +"firewall services." +msgstr "" + +#: ./doc/glossary/glossary-terms.xml345(glossterm) +msgid "associate" +msgstr "" + +#: ./doc/glossary/glossary-terms.xml347(para) +msgid "" +"The process associating a nova floating IP address to a fixed IP address." +msgstr "" + +#: ./doc/glossary/glossary-terms.xml352(glossterm) +msgid "Asynchronous JavaScript and XML (AJAX)" +msgstr "" + +#: ./doc/glossary/glossary-terms.xml355(para) +msgid "" +"A group of interrelated web development techniques used on the client-side " +"to create asynchronous web applications. Used extensively in horizon." +msgstr "" + +#: ./doc/glossary/glossary-terms.xml362(glossterm) +msgid "ATA over Ethernet (AoE)" +msgstr "" + +#: ./doc/glossary/glossary-terms.xml364(para) +msgid "" +"A disk storage protocol tunneled within Ethernet. Currently not supported in" +" nova." +msgstr "" + +#: ./doc/glossary/glossary-terms.xml369(glossterm) +msgid "attach" +msgstr "" + +#: ./doc/glossary/glossary-terms.xml371(para) +msgid "" +"The process of connecting a VIF or vNIC to a L2 network in neutron. In the " +"context of nova, this process connects a storage volume to an instance." +msgstr "" + +#: ./doc/glossary/glossary-terms.xml378(glossterm) +msgid "attachment (network)" +msgstr "" + +#: ./doc/glossary/glossary-terms.xml380(para) +msgid "" +"Association of an interface ID to a logical port. Plugs an interface into a " +"port." +msgstr "" + +#: ./doc/glossary/glossary-terms.xml385(glossterm) +msgid "auditing" +msgstr "" + +#: ./doc/glossary/glossary-terms.xml387(para) +msgid "Provided in nova through the system usage data facility." +msgstr "" + +#: ./doc/glossary/glossary-terms.xml392(glossterm) +msgid "auditor" +msgstr "" + +#: ./doc/glossary/glossary-terms.xml394(para) +msgid "" +"A worker processes that verifies the integrity of swift objects, containers," +" and accounts. Auditors is the collective term for the swift account " +"auditor, container auditor, and object auditor." +msgstr "" + +#: ./doc/glossary/glossary-terms.xml402(glossterm) +msgid "Austin" +msgstr "" + +#: ./doc/glossary/glossary-terms.xml404(para) +msgid "Project name for the initial release of OpenStack." +msgstr "" + +#: ./doc/glossary/glossary-terms.xml409(glossterm) +msgid "auth node" +msgstr "" + +#: ./doc/glossary/glossary-terms.xml411(para) +msgid "Alternative term for a swift authorization node." +msgstr "" + +#: ./doc/glossary/glossary-terms.xml416(glossterm) +msgid "authentication" +msgstr "" + +#: ./doc/glossary/glossary-terms.xml418(para) +msgid "" +"The process that confirms that the user, process, or client is really who " +"they say they are through private key, secret token, password, fingerprint, " +"or similar method." +msgstr "" + +#: ./doc/glossary/glossary-terms.xml425(glossterm) +msgid "authentication token" +msgstr "" + +#: ./doc/glossary/glossary-terms.xml427(para) +msgid "" +"A string of text provided to the client after authentication. Must be " +"provided by the user or process in subsequent requests to the API endpoint." +msgstr "" + +#: ./doc/glossary/glossary-terms.xml434(glossterm) +msgid "AuthN" +msgstr "" + +#: ./doc/glossary/glossary-terms.xml436(para) +msgid "The keystone component that provides authentication services." +msgstr "" + +#: ./doc/glossary/glossary-terms.xml441(glossterm) +msgid "authorization" +msgstr "" + +#: ./doc/glossary/glossary-terms.xml443(para) +msgid "" +"The act of verifying that a user, process, or client is authorized to " +"perform an action, such as delete a swift object, list a swift container, " +"start a nova VM, reset a password, and so on." +msgstr "" + +#: ./doc/glossary/glossary-terms.xml451(glossterm) +msgid "authorization node" +msgstr "" + +#: ./doc/glossary/glossary-terms.xml453(para) +msgid "A swift node that provides authorization services." +msgstr "" + +#: ./doc/glossary/glossary-terms.xml458(glossterm) +msgid "AuthZ" +msgstr "" + +#: ./doc/glossary/glossary-terms.xml460(para) +msgid "" +"The keystone component that provides high-level authorization services." +msgstr "" + +#: ./doc/glossary/glossary-terms.xml465(glossterm) +msgid "Auto ACK" +msgstr "" + +#: ./doc/glossary/glossary-terms.xml467(para) +msgid "" +"Configuration setting within RabbitMQ that enables or disables message " +"acknowledgment. Enabled by default." +msgstr "" + +#: ./doc/glossary/glossary-terms.xml473(glossterm) +msgid "auto declare" +msgstr "" + +#: ./doc/glossary/glossary-terms.xml475(para) +msgid "" +"A nova RabbitMQ setting that determines if a message exchange is " +"automatically created when the program starts." +msgstr "" + +#: ./doc/glossary/glossary-terms.xml481(glossterm) +msgid "availability zone" +msgstr "" + +#: ./doc/glossary/glossary-terms.xml483(para) +msgid "" +"An Amazon EC2 concept of an isolated area that is used for fault tolerance. " +"Do not confuse with an OpenStack nova zone or cell." +msgstr "" + +#: ./doc/glossary/glossary-terms.xml489(glossterm) +msgid "AWS" +msgstr "" + +#: ./doc/glossary/glossary-terms.xml491(para) +msgid "Amazon Web Services." +msgstr "" + +#: ./doc/glossary/glossary-terms.xml497(title) +msgid "B" +msgstr "" + +#: ./doc/glossary/glossary-terms.xml499(glossterm) +msgid "back-end" +msgstr "" + +#: ./doc/glossary/glossary-terms.xml501(para) +msgid "" +"Interactions and processes that are obfuscated from the user, such as nova " +"mounting a volume, a daemon sending data to an iSCSI target, or swift " +"checking the integrity of an object." +msgstr "" + +#: ./doc/glossary/glossary-terms.xml508(glossterm) +msgid "back-end catalog" +msgstr "" + +#: ./doc/glossary/glossary-terms.xml510(para) +msgid "" +"The storage method used by the keystone catalog service to store and " +"retrieve information about API endpoints that are available to the client. " +"Examples include a SQL database, LDAP database, or KVS back-end." +msgstr "" + +#: ./doc/glossary/glossary-terms.xml518(glossterm) +msgid "back-end store" +msgstr "" + +#: ./doc/glossary/glossary-terms.xml520(para) +msgid "" +"The persistent data store used to save and retrieve a information for a " +"service, such as a listing of swift objects, the current state of a nova VM," +" a list of user names, and so on. Method that glance uses to retrieve and " +"store VM images. Options include swift, local file system, S3, and HTTP." +msgstr "" + +#: ./doc/glossary/glossary-terms.xml530(glossterm) +msgid "bandwidth" +msgstr "" + +#: ./doc/glossary/glossary-terms.xml532(para) +msgid "" +"The amount of available data used by communication resources such as the " +"Internet. Represents the amount of data that is used to download things or " +"the amount of data available to download." +msgstr "" + +#: ./doc/glossary/glossary-terms.xml540(glossterm) +msgid "bare" +msgstr "" + +#: ./doc/glossary/glossary-terms.xml542(para) +msgid "" +"A glance container format that indicates that no container exists for the VM" +" image." +msgstr "" + +#: ./doc/glossary/glossary-terms.xml547(glossterm) +msgid "base image" +msgstr "" + +#: ./doc/glossary/glossary-terms.xml549(para) +msgid "An OpenStack-provided image." +msgstr "" + +#: ./doc/glossary/glossary-terms.xml553(glossterm) +msgid "Bexar" +msgstr "" + +#: ./doc/glossary/glossary-terms.xml555(para) +msgid "" +"A grouped release of projects related to OpenStack that came out in February" +" of 2011. It included Compute (nova) and Object Storage (swift) only." +msgstr "" + +#: ./doc/glossary/glossary-terms.xml562(glossterm) +msgid "binary" +msgstr "" + +#: ./doc/glossary/glossary-terms.xml564(para) +msgid "" +"Information that consists solely of ones and zeroes, which is the language " +"of computers." +msgstr "" + +#: ./doc/glossary/glossary-terms.xml569(glossterm) +msgid "bit" +msgstr "" + +#: ./doc/glossary/glossary-terms.xml571(para) +msgid "" +"A bit is a single digit number that is in base of 2 (either a zero or one). " +"Bandwidth usage is measured in bits-per-second." +msgstr "" + +#: ./doc/glossary/glossary-terms.xml577(glossterm) +msgid "bit-per-second (BPS)" +msgstr "" + +#: ./doc/glossary/glossary-terms.xml579(para) +msgid "" +"The universal measurement of how quickly data is transferred from place to " +"place." +msgstr "" + +#: ./doc/glossary/glossary-terms.xml584(glossterm) +msgid "block device" +msgstr "" + +#: ./doc/glossary/glossary-terms.xml586(para) +msgid "" +"A device that moves data in the form of blocks. These device nodes interface" +" the devices, such as hard disks, CD-ROM drives, flash drives, and other " +"addressable regions of memory." +msgstr "" + +#: ./doc/glossary/glossary-terms.xml593(glossterm) +msgid "block migration" +msgstr "" + +#: ./doc/glossary/glossary-terms.xml595(para) +msgid "" +"A method of VM live migration used by KVM to evacuate instances from one " +"host to another with very little downtime during a user-initiated switch-" +"over. Does not require shared storage. Supported by nova." +msgstr "" + +#: ./doc/glossary/glossary-terms.xml603(glossterm) +msgid "BMC" +msgstr "" + +#: ./doc/glossary/glossary-terms.xml605(para) +msgid "" +"Baseboard Management Controller. The intelligence in the IPMI architecture, " +"which is a specialized micro-controller that is embedded on the motherboard " +"of a computer and acts as a server. Manages the interface between system " +"management software and platform hardware." +msgstr "" + +#: ./doc/glossary/glossary-terms.xml614(glossterm) +msgid "bootable disk image" +msgstr "" + +#: ./doc/glossary/glossary-terms.xml616(para) +msgid "A type of VM image that exists as a single, bootable file." +msgstr "" + +#: ./doc/glossary/glossary-terms.xml621(glossterm) +msgid "Bootstrap Protocol (BOOTP)" +msgstr "" + +#: ./doc/glossary/glossary-terms.xml623(para) +msgid "" +"A network protocol used by a network client to obtain an IP address from a " +"configuration server. Provided in nova through the dnsmasq daemon when using" +" either the FlatDHCP manager or VLAN manager network manager." +msgstr "" + +#: ./doc/glossary/glossary-terms.xml631(glossterm) +msgid "browser" +msgstr "" + +#: ./doc/glossary/glossary-terms.xml633(para) +msgid "" +"Any client software that enables a computer or device to access the " +"Internet." +msgstr "" + +#: ./doc/glossary/glossary-terms.xml638(glossterm) +msgid "builder file" +msgstr "" + +#: ./doc/glossary/glossary-terms.xml640(para) +msgid "" +"Contains configuration information for a swift ring, and is used to re-" +"configure the ring or to recreate it from scratch after a serious failure." +msgstr "" + +#: ./doc/glossary/glossary-terms.xml647(glossterm) +msgid "button class" +msgstr "" + +#: ./doc/glossary/glossary-terms.xml649(para) +msgid "" +"A group of related button types within horizon. Buttons to start, stop, and " +"suspend VMs are in one class. Buttons to associate and disassociate floating" +" IP addresses are in another class, and so on." +msgstr "" + +#: ./doc/glossary/glossary-terms.xml657(glossterm) +msgid "byte" +msgstr "" + +#: ./doc/glossary/glossary-terms.xml659(para) +msgid "" +"Set of bits that make up a single character; there are usually 8 bits to a " +"byte." +msgstr "" + +#: ./doc/glossary/glossary-terms.xml672(title) +msgid "C" +msgstr "" + +#: ./doc/glossary/glossary-terms.xml674(glossterm) +msgid "CA" +msgstr "" + +#: ./doc/glossary/glossary-terms.xml676(para) +msgid "" +"Certificate Authority or Certification Authority. In cryptography, an entity" +" that issues digital certificates. The digital certificate certifies the " +"ownership of a public key by the named subject of the certificate. This " +"enables others (relying parties) to rely upon signatures or assertions made " +"by the private key that corresponds to the certified public key. In this " +"model of trust relationships, a CA is a trusted third party for both the " +"subject (owner) of the certificate and the party relying upon the " +"certificate. CAs are characteristic of many public key infrastructure (PKI) " +"schemes." +msgstr "" + +#: ./doc/glossary/glossary-terms.xml692(glossterm) +msgid "cache pruner" +msgstr "" + +#: ./doc/glossary/glossary-terms.xml694(para) +msgid "" +"An executable program that is used to keep a glance VM image cache at or " +"below its configured maximum size." +msgstr "" + +#: ./doc/glossary/glossary-terms.xml700(glossterm) +msgid "Cactus" +msgstr "" + +#: ./doc/glossary/glossary-terms.xml702(para) +msgid "" +"An OpenStack grouped release of projects that came out in the spring of " +"2011. It included Compute (nova), Object Storage (swift), and the Image " +"service (glance)." +msgstr "" + +#: ./doc/glossary/glossary-terms.xml709(glossterm) +msgid "CALL" +msgstr "" + +#: ./doc/glossary/glossary-terms.xml711(para) +msgid "" +"One of the RPC primitives used by the OpenStack message queue software. " +"Sends a message and waits for a response." +msgstr "" + +#: ./doc/glossary/glossary-terms.xml717(glossterm) +msgid "capability" +msgstr "" + +#: ./doc/glossary/glossary-terms.xml719(para) +msgid "" +"Defines resources for a cell, including CPU, storage, and networking. Can " +"apply to the specific services within a cell or a whole cell." +msgstr "" + +#: ./doc/glossary/glossary-terms.xml725(glossterm) +msgid "capacity cache" +msgstr "" + +#: ./doc/glossary/glossary-terms.xml727(para) +msgid "" +"A table within the nova back-end database that contains the current " +"workload, amount of free RAM, number of VMs running on each host. Used to " +"determine on which VM a host starts." +msgstr "" + +#: ./doc/glossary/glossary-terms.xml734(glossterm) +msgid "capacity updater" +msgstr "" + +#: ./doc/glossary/glossary-terms.xml736(para) +msgid "" +"A notification driver that monitors VM instances and updates the capacity " +"cache as needed." +msgstr "" + +#: ./doc/glossary/glossary-terms.xml741(glossterm) +msgid "CAST" +msgstr "" + +#: ./doc/glossary/glossary-terms.xml743(para) +msgid "" +"One of the RPC primitives used by the OpenStack message queue software. " +"Sends a message and does not wait for a response." +msgstr "" + +#: ./doc/glossary/glossary-terms.xml749(glossterm) +msgid "catalog" +msgstr "" + +#: ./doc/glossary/glossary-terms.xml751(para) +msgid "" +"Contains a list of available API endpoints to a user after they authenticate" +" to keystone." +msgstr "" + +#: ./doc/glossary/glossary-terms.xml756(glossterm) +msgid "catalog service" +msgstr "" + +#: ./doc/glossary/glossary-terms.xml758(para) +msgid "" +"A keystone service that provides a list of available API endpoints to a user" +" after they authenticate to keystone." +msgstr "" + +#: ./doc/glossary/glossary-terms.xml764(glossterm) +msgid "Ceilometer" +msgstr "" + +#: ./doc/glossary/glossary-terms.xml766(para) +msgid "" +"An incubated project that provides metering and billing facilities for " +"OpenStack." +msgstr "" + +#: ./doc/glossary/glossary-terms.xml771(glossterm) +msgid "cell" +msgstr "" + +#: ./doc/glossary/glossary-terms.xml773(para) +msgid "" +"Provides logical partitioning of nova resources in a child and parent " +"relationship. Requests are passed from parent cells to child cells if the " +"parent cannot provide the requested resource." +msgstr "" + +#: ./doc/glossary/glossary-terms.xml781(glossterm) +msgid "cell forwarding" +msgstr "" + +#: ./doc/glossary/glossary-terms.xml783(para) +msgid "" +"A nova option that enables parent cells to pass resource requests to child " +"cells if the parent cannot provide the requested resource." +msgstr "" + +#: ./doc/glossary/glossary-terms.xml789(glossterm) +msgid "cell manager" +msgstr "" + +#: ./doc/glossary/glossary-terms.xml791(para) +msgid "" +"The nova component that contains a list of the current capabilities of each " +"host within the cell and routes requests as appropriate." +msgstr "" + +#: ./doc/glossary/glossary-terms.xml797(glossterm) +msgid "CentOS" +msgstr "" + +#: ./doc/glossary/glossary-terms.xml799(para) +#: ./doc/glossary/glossary-terms.xml1288(para) +#: ./doc/glossary/glossary-terms.xml3242(para) +#: ./doc/glossary/glossary-terms.xml3669(para) +#: ./doc/glossary/glossary-terms.xml4232(para) +msgid "A Linux distribution that is compatible with OpenStack." +msgstr "" + +#: ./doc/glossary/glossary-terms.xml804(glossterm) +msgid "Ceph" +msgstr "" + +#: ./doc/glossary/glossary-terms.xml806(para) +msgid "" +"Massively scalable distributed storage system that consists of an object " +"store, block store, and POSIX-compatible distributed file system. Compatible" +" with OpenStack." +msgstr "" + +#: ./doc/glossary/glossary-terms.xml813(glossterm) +msgid "CephFS" +msgstr "" + +#: ./doc/glossary/glossary-terms.xml815(para) +msgid "The POSIX-compliant file system provided by Ceph." +msgstr "" + +#: ./doc/glossary/glossary-terms.xml820(glossterm) +msgid "certificate authority" +msgstr "" + +#: ./doc/glossary/glossary-terms.xml822(para) +msgid "" +"A simple certificate authority provided by nova for cloudpipe VPNs and VM " +"image decryption." +msgstr "" + +#: ./doc/glossary/glossary-terms.xml827(glossterm) +msgid "Challenge-Handshake Authentication Protocol (CHAP)" +msgstr "" + +#: ./doc/glossary/glossary-terms.xml830(para) +msgid "An iSCSI authentication method supported by nova." +msgstr "" + +#: ./doc/glossary/glossary-terms.xml835(glossterm) +msgid "chance scheduler" +msgstr "" + +#: ./doc/glossary/glossary-terms.xml837(para) +msgid "" +"A scheduling method used by nova that randomly chooses an available host " +"from the pool." +msgstr "" + +#: ./doc/glossary/glossary-terms.xml842(glossterm) +msgid "changes since" +msgstr "" + +#: ./doc/glossary/glossary-terms.xml844(para) +msgid "" +"A nova API parameter that downloads changes to the requested item since your" +" last request, instead of downloading a new, fresh set of data and comparing" +" it against the old data." +msgstr "" + +#: ./doc/glossary/glossary-terms.xml852(glossterm) +msgid "Chef" +msgstr "" + +#: ./doc/glossary/glossary-terms.xml854(para) +msgid "" +"An operating system configuration management tool supporting OpenStack " +"deployments." +msgstr "" + +#: ./doc/glossary/glossary-terms.xml859(glossterm) +msgid "child cell" +msgstr "" + +#: ./doc/glossary/glossary-terms.xml861(para) +msgid "" +"If a requested resource such as CPU time, disk storage, or memory is not " +"available in the parent cell, the request is forwarded to its associated " +"child cells. If the child cell can fulfill the request, it does. Otherwise, " +"it attempts to pass the request to any of its children." +msgstr "" + +#: ./doc/glossary/glossary-terms.xml870(glossterm) +msgid "Cinder" +msgstr "" + +#: ./doc/glossary/glossary-terms.xml872(para) +msgid "" +"A core OpenStack project that maintains the object storage services for VMs." +msgstr "" + +#: ./doc/glossary/glossary-terms.xml877(glossterm) +msgid "Cisco neutron plug-in" +msgstr "" + +#: ./doc/glossary/glossary-terms.xml879(para) +msgid "" +"A neutron plug-in for Cisco devices and technologies including UCS and " +"Nexus." +msgstr "" + +#: ./doc/glossary/glossary-terms.xml884(glossterm) +msgid "cloud architect" +msgstr "" + +#: ./doc/glossary/glossary-terms.xml886(para) +msgid "A person who plans, designs, and oversees the creation of clouds." +msgstr "" + +#: ./doc/glossary/glossary-terms.xml891(glossterm) +msgid "cloud computing" +msgstr "" + +#: ./doc/glossary/glossary-terms.xml893(para) +msgid "" +"A model that enables access to a shared pool of configurable computing " +"resources, such as networks, servers, storage, applications, and services, " +"that can be rapidly provisioned and released with minimal management effort " +"or service provider interaction." +msgstr "" + +#: ./doc/glossary/glossary-terms.xml902(glossterm) +msgid "cloud controller" +msgstr "" + +#: ./doc/glossary/glossary-terms.xml904(para) +msgid "" +"Collection of nova components that represent the global state of the cloud, " +"talks to services such as keystone authentication, swift object storage, and" +" node/storage workers through a queue." +msgstr "" + +#: ./doc/glossary/glossary-terms.xml911(glossterm) +msgid "cloud controller node" +msgstr "" + +#: ./doc/glossary/glossary-terms.xml913(para) +msgid "" +"A node that runs network, volume, API, scheduler and image services. Each " +"service may be broken out into separate nodes for scalability or " +"availability." +msgstr "" + +#: ./doc/glossary/glossary-terms.xml920(glossterm) +msgid "Cloud Data Management Interface (CDMI)" +msgstr "" + +#: ./doc/glossary/glossary-terms.xml923(para) +msgid "" +"SINA standard that defines a RESTful API for managing objects in the cloud, " +"currently unsupported in OpenStack." +msgstr "" + +#: ./doc/glossary/glossary-terms.xml929(glossterm) +msgid "Cloud Infrastructure Management Interface (CIMI)" +msgstr "" + +#: ./doc/glossary/glossary-terms.xml932(para) +msgid "" +"An in-progress specification for cloud management. Currently unsupported in " +"OpenStack." +msgstr "" + +#: ./doc/glossary/glossary-terms.xml938(glossterm) +msgid "cloud-init" +msgstr "" + +#: ./doc/glossary/glossary-terms.xml940(para) +msgid "" +"A package commonly installed in VM images that performs initialization of an" +" instance after boot using information that it retrieves from the metadata " +"service such as the SSH public key and user data." +msgstr "" + +#: ./doc/glossary/glossary-terms.xml948(glossterm) +msgid "cloudadmin" +msgstr "" + +#: ./doc/glossary/glossary-terms.xml950(para) +msgid "" +"One of the default roles in the nova RBAC system. Grants complete system " +"access." +msgstr "" + +#: ./doc/glossary/glossary-terms.xml955(glossterm) +msgid "cloudpipe" +msgstr "" + +#: ./doc/glossary/glossary-terms.xml957(para) +msgid "A service in nova used to create VPNs on a per-project basis." +msgstr "" + +#: ./doc/glossary/glossary-terms.xml962(glossterm) +msgid "cloudpipe image" +msgstr "" + +#: ./doc/glossary/glossary-terms.xml964(para) +msgid "" +"A pre-made VM image that serves as a cloudpipe server. Essentially, OpenVPN " +"running on Linux." +msgstr "" + +#: ./doc/glossary/glossary-terms.xml970(glossterm) +msgid "CMDB" +msgstr "" + +#: ./doc/glossary/glossary-terms.xml972(para) +msgid "Configuration Management Database." +msgstr "" + +#: ./doc/glossary/glossary-terms.xml976(glossterm) +msgid "command filter" +msgstr "" + +#: ./doc/glossary/glossary-terms.xml978(para) +msgid "Lists allowed commands within the nova rootwrap facility." +msgstr "" + +#: ./doc/glossary/glossary-terms.xml983(glossterm) +msgid "community project" +msgstr "" + +#: ./doc/glossary/glossary-terms.xml985(para) +msgid "" +"A project that is not officially endorsed by the OpenStack Foundation. If " +"the project is successful enough, it might be elevated to an incubated " +"project and then to a core project, or it might be merged with the main code" +" trunk." +msgstr "" + +#: ./doc/glossary/glossary-terms.xml993(glossterm) +msgid "compression" +msgstr "" + +#: ./doc/glossary/glossary-terms.xml995(para) +msgid "" +"OpenStack supports compression at the Linux file system level but does not " +"support compression for things such as swift objects or glance VM images." +msgstr "" + +#: ./doc/glossary/glossary-terms.xml1002(glossterm) +msgid "Compute API" +msgstr "" + +#: ./doc/glossary/glossary-terms.xml1004(para) +msgid "" +"The nova-api daemon that provides" +" access to nova services. Can communicate with other APIs, such as the " +"Amazon EC2 API." +msgstr "" + +#: ./doc/glossary/glossary-terms.xml1011(glossterm) +msgid "Compute API extension" +msgstr "" + +#: ./doc/glossary/glossary-terms.xml1013(para) +msgid "Alternative term for a nova API extension." +msgstr "" + +#: ./doc/glossary/glossary-terms.xml1018(glossterm) +msgid "compute controller" +msgstr "" + +#: ./doc/glossary/glossary-terms.xml1020(para) +msgid "" +"The nova component that chooses suitable hosts on which to start VM " +"instances." +msgstr "" + +#: ./doc/glossary/glossary-terms.xml1025(glossterm) +msgid "compute host" +msgstr "" + +#: ./doc/glossary/glossary-terms.xml1027(para) +msgid "Physical host dedicated to running compute nodes." +msgstr "" + +#: ./doc/glossary/glossary-terms.xml1032(glossterm) +msgid "compute node" +msgstr "" + +#: ./doc/glossary/glossary-terms.xml1034(para) +msgid "" +"A node that runs the nova-compute" +" daemon, a VM instance that provides a wide range of services such as a web " +"services and analytics." +msgstr "" + +#: ./doc/glossary/glossary-terms.xml1040(glossterm) +msgid "compute service" +msgstr "" + +#: ./doc/glossary/glossary-terms.xml1042(para) +msgid "Alternative term for the nova component that manages VMs." +msgstr "" + +#: ./doc/glossary/glossary-terms.xml1047(glossterm) +msgid "compute worker" +msgstr "" + +#: ./doc/glossary/glossary-terms.xml1049(para) +msgid "" +"The nova component that runs on each compute node and manages the VM " +"instance life cycle, including run, reboot, terminate, attach/detach " +"volumes, and so on. Provided by the nova-" +"compute daemon." +msgstr "" + +#: ./doc/glossary/glossary-terms.xml1057(glossterm) +msgid "concatenated object" +msgstr "" + +#: ./doc/glossary/glossary-terms.xml1059(para) +msgid "" +"A segmented large object within swift that is put back together again and " +"then sent to the client." +msgstr "" + +#: ./doc/glossary/glossary-terms.xml1065(glossterm) +msgid "conductor" +msgstr "" + +#: ./doc/glossary/glossary-terms.xml1067(para) +msgid "" +"In nova, conductor is the process that proxies database requests from the " +"compute process. Using conductor improves security as compute nodes don't " +"need direct access to the database." +msgstr "" + +#: ./doc/glossary/glossary-terms.xml1074(glossterm) +msgid "consistency window" +msgstr "" + +#: ./doc/glossary/glossary-terms.xml1076(para) +msgid "" +"The amount of time it takes for a new swift object to become accessible to " +"all clients." +msgstr "" + +#: ./doc/glossary/glossary-terms.xml1081(glossterm) +msgid "console log" +msgstr "" + +#: ./doc/glossary/glossary-terms.xml1083(para) +msgid "Contains the output from a Linux VM console in nova." +msgstr "" + +#: ./doc/glossary/glossary-terms.xml1088(glossterm) +msgid "container" +msgstr "" + +#: ./doc/glossary/glossary-terms.xml1090(para) +msgid "" +"Used to organize and store objects within swift, similar to the concept as a" +" Linux directory but cannot be nested. Alternative term for a glance " +"container format." +msgstr "" + +#: ./doc/glossary/glossary-terms.xml1097(glossterm) +msgid "container auditor" +msgstr "" + +#: ./doc/glossary/glossary-terms.xml1099(para) +msgid "" +"Checks for missing replicas or incorrect objects in the specified swift " +"containers through queries to the SQLite back-end database." +msgstr "" + +#: ./doc/glossary/glossary-terms.xml1105(glossterm) +msgid "container database" +msgstr "" + +#: ./doc/glossary/glossary-terms.xml1107(para) +msgid "" +"A SQLite database that contains swift containers and related metadata and is" +" accessed by the container server" +msgstr "" + +#: ./doc/glossary/glossary-terms.xml1113(glossterm) +msgid "container format" +msgstr "" + +#: ./doc/glossary/glossary-terms.xml1115(para) +msgid "" +"The \"envelope\" used by glance to store a VM image and its associated " +"metadata, such as machine state, OS disk size, and so on." +msgstr "" + +#: ./doc/glossary/glossary-terms.xml1121(glossterm) +msgid "container server" +msgstr "" + +#: ./doc/glossary/glossary-terms.xml1123(para) +msgid "A swift that manages containers." +msgstr "" + +#: ./doc/glossary/glossary-terms.xml1127(glossterm) +msgid "container service" +msgstr "" + +#: ./doc/glossary/glossary-terms.xml1129(para) +msgid "" +"The swift component that provides container services, such as create, " +"delete, list, and so on." +msgstr "" + +#: ./doc/glossary/glossary-terms.xml1135(glossterm) +msgid "controller node" +msgstr "" + +#: ./doc/glossary/glossary-terms.xml1137(para) +msgid "Alternative term for a cloud controller node." +msgstr "" + +#: ./doc/glossary/glossary-terms.xml1142(glossterm) +msgid "core API" +msgstr "" + +#: ./doc/glossary/glossary-terms.xml1144(para) +msgid "" +"Depending on context, the core API is either the OpenStack API or the main " +"API of a specific core project, such as nova, neutron, glance, and so on." +msgstr "" + +#: ./doc/glossary/glossary-terms.xml1151(glossterm) +msgid "core project" +msgstr "" + +#: ./doc/glossary/glossary-terms.xml1153(para) +msgid "" +"An official OpenStack project. Currently consists of Compute (nova), Object " +"Storage (swift), Image Service (glance), Identity (keystone), Dashboard " +"(horizon), Networking (neutron), Block Storage (cinder), Telemetry Service " +"(ceilometer) and Orchestration Service (heat)." +msgstr "" + +#: ./doc/glossary/glossary-terms.xml1163(glossterm) +msgid "cost" +msgstr "" + +#: ./doc/glossary/glossary-terms.xml1165(para) +msgid "" +"Under the nova distributed scheduler this is calculated by looking at the " +"capabilities of each host relative to the flavor of the VM instance being " +"requested." +msgstr "" + +#: ./doc/glossary/glossary-terms.xml1172(glossterm) +msgid "credentials" +msgstr "" + +#: ./doc/glossary/glossary-terms.xml1174(para) +msgid "" +"Data that is only known to or accessible by a user that is used to verify " +"the user is who they say they are and presented to the server during " +"authentication. Examples include a password, secret key, digital " +"certificate, fingerprint, and so on." +msgstr "" + +#: ./doc/glossary/glossary-terms.xml1183(glossterm) +msgid "Crowbar" +msgstr "" + +#: ./doc/glossary/glossary-terms.xml1185(para) +msgid "" +"An open source community project by Dell that aims to provide all necessary " +"services to quickly deploy clouds." +msgstr "" + +#: ./doc/glossary/glossary-terms.xml1191(glossterm) +msgid "current workload" +msgstr "" + +#: ./doc/glossary/glossary-terms.xml1193(para) +msgid "" +"An element of the nova capacity cache that is calculated based on the number" +" of build, snapshot, migrate, and resize operations currently in progress on" +" a given host." +msgstr "" + +#: ./doc/glossary/glossary-terms.xml1200(glossterm) +msgid "customer" +msgstr "" + +#: ./doc/glossary/glossary-terms.xml1202(para) +msgid "Alternative term for tenant." +msgstr "" + +#: ./doc/glossary/glossary-terms.xml1206(glossterm) +msgid "customization module" +msgstr "" + +#: ./doc/glossary/glossary-terms.xml1208(para) +msgid "" +"A user-created Python module that is loaded by horizon to change the look " +"and feel of the dashboard." +msgstr "" + +#: ./doc/glossary/glossary-terms.xml1222(title) +msgid "D" +msgstr "" + +#: ./doc/glossary/glossary-terms.xml1224(glossterm) +msgid "daemon" +msgstr "" + +#: ./doc/glossary/glossary-terms.xml1226(para) +msgid "" +"A process that runs in the background and waits for requests. May or may not" +" listen on a TCP or UDP port. Do not confuse with a worker." +msgstr "" + +#: ./doc/glossary/glossary-terms.xml1232(glossterm) +msgid "DAC" +msgstr "" + +#: ./doc/glossary/glossary-terms.xml1234(para) +msgid "" +"Discretionary access control. Governs the ability of subjects to access " +"objects, while enabling users to make policy decisions and assign security " +"attributes. The traditional UNIX system of users, groups, and read-write-" +"execute permissions is an example of DAC." +msgstr "" + +#: ./doc/glossary/glossary-terms.xml1243(glossterm) +msgid "dashboard" +msgstr "" + +#: ./doc/glossary/glossary-terms.xml1245(para) +msgid "" +"The web-based management interface for OpenStack. An alternative name for " +"horizon." +msgstr "" + +#: ./doc/glossary/glossary-terms.xml1250(glossterm) +msgid "data encryption" +msgstr "" + +#: ./doc/glossary/glossary-terms.xml1252(para) +msgid "" +"Both glance and nova support encrypted virtual machine (VM) images (but not " +"instances). In-transit data encryption is supported in OpenStack using " +"technologies such as HTTPS, SSL, TLS, SSH. swift does not support object " +"encryption at the application level but may support storage that uses disk " +"encryption." +msgstr "" + +#: ./doc/glossary/glossary-terms.xml1262(glossterm) +msgid "database ID" +msgstr "" + +#: ./doc/glossary/glossary-terms.xml1264(para) +msgid "A unique ID given to each replica of a swift database." +msgstr "" + +#: ./doc/glossary/glossary-terms.xml1269(glossterm) +msgid "database replicator" +msgstr "" + +#: ./doc/glossary/glossary-terms.xml1271(para) +msgid "" +"A swift component that copies changes in the account, container, and object " +"databases to other nodes." +msgstr "" + +#: ./doc/glossary/glossary-terms.xml1277(glossterm) +msgid "deallocate" +msgstr "" + +#: ./doc/glossary/glossary-terms.xml1279(para) +msgid "" +"The process of removing the association between a floating IP address and a " +"fixed IP address thus returning the floating IP to the address pool." +msgstr "" + +#: ./doc/glossary/glossary-terms.xml1286(glossterm) +msgid "Debian" +msgstr "" + +#: ./doc/glossary/glossary-terms.xml1293(glossterm) +msgid "deduplication" +msgstr "" + +#: ./doc/glossary/glossary-terms.xml1295(para) +msgid "" +"The process of finding duplicate data at the disk block, file, and/or object" +" level to minimize storage use, currently unsupported within OpenStack." +msgstr "" + +#: ./doc/glossary/glossary-terms.xml1302(glossterm) +msgid "default panel" +msgstr "" + +#: ./doc/glossary/glossary-terms.xml1304(para) +msgid "" +"The default panel that is displayed when a user accesses the horizon " +"dashboard." +msgstr "" + +#: ./doc/glossary/glossary-terms.xml1309(glossterm) +msgid "default tenant" +msgstr "" + +#: ./doc/glossary/glossary-terms.xml1311(para) +msgid "" +"New users are assigned to this keystone tenant if no tenant is specified " +"when a user is created." +msgstr "" + +#: ./doc/glossary/glossary-terms.xml1317(glossterm) +msgid "default token" +msgstr "" + +#: ./doc/glossary/glossary-terms.xml1319(para) +msgid "" +"A keystone token that is not associated with a specific tenant and is " +"exchanged for a scoped token." +msgstr "" + +#: ./doc/glossary/glossary-terms.xml1325(glossterm) +msgid "delayed delete" +msgstr "" + +#: ./doc/glossary/glossary-terms.xml1327(para) +msgid "" +"An option within glance so that rather than immediately delete an image, it " +"is deleted after a pre-defined number of seconds." +msgstr "" + +#: ./doc/glossary/glossary-terms.xml1333(glossterm) +msgid "delivery mode" +msgstr "" + +#: ./doc/glossary/glossary-terms.xml1335(para) +msgid "" +"Setting for the nova RabbitMQ message delivery mode, can be set to either " +"transient or persistent." +msgstr "" + +#: ./doc/glossary/glossary-terms.xml1341(glossterm) +msgid "deprecated auth" +msgstr "" + +#: ./doc/glossary/glossary-terms.xml1343(para) +msgid "" +"An option within nova that enables administrators to create and manage users" +" through the nova-manage command as opposed to using keystone." +msgstr "" + +#: ./doc/glossary/glossary-terms.xml1349(glossterm) +msgid "developer" +msgstr "" + +#: ./doc/glossary/glossary-terms.xml1351(para) +msgid "" +"One of the default roles in the nova RBAC system and is the default role " +"assigned to a new user." +msgstr "" + +#: ./doc/glossary/glossary-terms.xml1357(glossterm) +msgid "device" +msgstr "" + +#: ./doc/glossary/glossary-terms.xml1359(para) +msgid "In the context of swift this refers to the underlying storage device." +msgstr "" + +#: ./doc/glossary/glossary-terms.xml1364(glossterm) +msgid "device ID" +msgstr "" + +#: ./doc/glossary/glossary-terms.xml1366(para) +msgid "Maps swift partitions to physical storage devices." +msgstr "" + +#: ./doc/glossary/glossary-terms.xml1371(glossterm) +msgid "device weight" +msgstr "" + +#: ./doc/glossary/glossary-terms.xml1373(para) +msgid "" +"Used to distribute the partitions among swift devices. The distribution is " +"usually proportional to the storage capacity of the device." +msgstr "" + +#: ./doc/glossary/glossary-terms.xml1379(glossterm) +msgid "DevStack" +msgstr "" + +#: ./doc/glossary/glossary-terms.xml1381(para) +msgid "" +"Community project that uses shell scripts to quickly build complete " +"OpenStack development environments." +msgstr "" + +#: ./doc/glossary/glossary-terms.xml1387(glossterm) +msgid "DHCP" +msgstr "" + +#: ./doc/glossary/glossary-terms.xml1389(para) +msgid "" +"Dynamic Host Configuration Protocol. A network protocol that configures " +"devices that are connected to a network so they can communicate on that " +"network by using the Internet Protocol (IP). The protocol is implemented in " +"a client-server model where DHCP clients request configuration data such as," +" an IP address, a default route, and one or more DNS server addresses from a" +" DHCP server." +msgstr "" + +#: ./doc/glossary/glossary-terms.xml1401(glossterm) +msgid "Diablo" +msgstr "" + +#: ./doc/glossary/glossary-terms.xml1403(para) +msgid "" +"A grouped release of projects related to OpenStack that came out in the fall" +" of 2011, the fourth release of OpenStack. It included Compute (nova " +"2011.3), Object Storage (swift 1.4.3), and the Image service (glance)." +msgstr "" + +#: ./doc/glossary/glossary-terms.xml1411(glossterm) +msgid "direct consumer" +msgstr "" + +#: ./doc/glossary/glossary-terms.xml1413(para) +msgid "" +"An element of the nova RabbitMQ that comes to life when a RPC call is " +"executed. It connects to a direct exchange through a unique exclusive queue," +" sends the message, and terminates." +msgstr "" + +#: ./doc/glossary/glossary-terms.xml1420(glossterm) +msgid "direct exchange" +msgstr "" + +#: ./doc/glossary/glossary-terms.xml1422(para) +msgid "" +"A routing table that is created within the nova RabbitMQ during RPC calls, " +"one is created for each RPC call that is invoked." +msgstr "" + +#: ./doc/glossary/glossary-terms.xml1428(glossterm) +msgid "direct publisher" +msgstr "" + +#: ./doc/glossary/glossary-terms.xml1430(para) +msgid "" +"Element of RabbitMQ that provides a response to an incoming MQ message." +msgstr "" + +#: ./doc/glossary/glossary-terms.xml1435(glossterm) +msgid "disassociate" +msgstr "" + +#: ./doc/glossary/glossary-terms.xml1437(para) +msgid "" +"The process of removing the association between a floating IP address and " +"fixed IP and thus returning the floating IP address to the address pool." +msgstr "" + +#: ./doc/glossary/glossary-terms.xml1444(glossterm) +msgid "disk encryption" +msgstr "" + +#: ./doc/glossary/glossary-terms.xml1446(para) +msgid "" +"The ability to encrypt data at the file system, disk partition or whole disk" +" level. Supported within nova VMs." +msgstr "" + +#: ./doc/glossary/glossary-terms.xml1452(glossterm) +msgid "disk format" +msgstr "" + +#: ./doc/glossary/glossary-terms.xml1454(para) +msgid "" +"The underlying format that a disk image for a VM is stored as within the " +"glance back-end store. For example, AMI, ISO, QCOW2, VMDK, and so on." +msgstr "" + +#: ./doc/glossary/glossary-terms.xml1460(glossterm) +msgid "dispersion" +msgstr "" + +#: ./doc/glossary/glossary-terms.xml1462(para) +msgid "" +"In swift, tools to test and ensure dispersion of objects and containers to " +"ensure fault tolerance." +msgstr "" + +#: ./doc/glossary/glossary-terms.xml1468(glossterm) +msgid "Django" +msgstr "" + +#: ./doc/glossary/glossary-terms.xml1470(para) +msgid "A web framework used extensively in horizon." +msgstr "" + +#: ./doc/glossary/glossary-terms.xml1475(glossterm) +msgid "DNS" +msgstr "" + +#: ./doc/glossary/glossary-terms.xml1477(para) +msgid "" +"Domain Name Server. A hierarchical and distributed naming system for " +"computers, services, and resources connected to the Internet or a private " +"network. Associates a human-friendly names to IP addresses." +msgstr "" + +#: ./doc/glossary/glossary-terms.xml1485(glossterm) +msgid "DNS record" +msgstr "" + +#: ./doc/glossary/glossary-terms.xml1487(para) +msgid "" +"A record that specifies information about a particular domain and belongs to" +" the domain." +msgstr "" + +#: ./doc/glossary/glossary-terms.xml1493(glossterm) +msgid "dnsmasq" +msgstr "" + +#: ./doc/glossary/glossary-terms.xml1495(para) +msgid "" +"Daemon that provides DNS, DHCP, BOOTP, and TFTP services, used by the nova " +"VLAN manager and FlatDHCP manager." +msgstr "" + +#: ./doc/glossary/glossary-terms.xml1501(glossterm) +msgid "domain" +msgstr "" + +#: ./doc/glossary/glossary-terms.xml1503(para) +msgid "" +"Separates a web site from other sites. Often, the domain name has two or " +"more parts that are separated by dots. For example, yahoo.com, usa.gov, " +"Harvard.edu, or mail.yahoo.com." +msgstr "" + +#: ./doc/glossary/glossary-terms.xml1507(para) +msgid "" +"A domain is an entity or container of all DNS-related information containing" +" one or more records." +msgstr "" + +#: ./doc/glossary/glossary-terms.xml1513(glossterm) +msgid "Domain Name Service (DNS)" +msgstr "" + +#: ./doc/glossary/glossary-terms.xml1515(para) +msgid "" +"In nova, the support that enables associating DNS entries with floating IP " +"addresses, nodes, or cells so host names are consistent across reboots." +msgstr "" + +#: ./doc/glossary/glossary-terms.xml1522(glossterm) +msgid "Domain Name System (DNS)" +msgstr "" + +#: ./doc/glossary/glossary-terms.xml1524(para) +msgid "" +"A system by which Internet domain name-to-address and address-to-name " +"resolutions are determined." +msgstr "" + +#: ./doc/glossary/glossary-terms.xml1527(para) +msgid "" +"DNS helps navigate the Internet by translating the IP address into an " +"address that is easier to remember For example, translating 111.111.111.1 " +"into www.yahoo.com." +msgstr "" + +#: ./doc/glossary/glossary-terms.xml1531(para) +msgid "" +"All domains and their components, such as mail servers, utilize DNS to " +"resolve to the appropriate locations. DNS servers are usually set up in a " +"master-slave relationship such that failure of the master invokes the slave." +" DNS servers might also be clustered or replicated such that changes made to" +" one DNS server are automatically propagated to other active servers." +msgstr "" + +#: ./doc/glossary/glossary-terms.xml1542(glossterm) +msgid "download" +msgstr "" + +#: ./doc/glossary/glossary-terms.xml1544(para) +msgid "" +"The transfer of data, usually in the form of files, from one computer to " +"another." +msgstr "" + +#: ./doc/glossary/glossary-terms.xml1549(glossterm) +msgid "DRTM" +msgstr "" + +#: ./doc/glossary/glossary-terms.xml1551(para) +msgid "Dynamic root of trust measurement." +msgstr "" + +#: ./doc/glossary/glossary-terms.xml1555(glossterm) +msgid "durable exchange" +msgstr "" + +#: ./doc/glossary/glossary-terms.xml1557(para) +msgid "" +"The nova RabbitMQ message exchange that remains active when the server " +"restarts." +msgstr "" + +#: ./doc/glossary/glossary-terms.xml1562(glossterm) +msgid "durable queue" +msgstr "" + +#: ./doc/glossary/glossary-terms.xml1564(para) +msgid "" +"A nova RabbitMQ message queue that remains active when the server restarts." +msgstr "" + +#: ./doc/glossary/glossary-terms.xml1569(glossterm) +msgid "Dynamic Host Configuration Protocol (DHCP)" +msgstr "" + +#: ./doc/glossary/glossary-terms.xml1572(para) +msgid "" +"A method to automatically configure networking for a host at boot time. " +"Provided by both neutron and nova." +msgstr "" + +#: ./doc/glossary/glossary-terms.xml1578(glossterm) +msgid "Dynamic HyperText Markup Language (DHTML)" +msgstr "" + +#: ./doc/glossary/glossary-terms.xml1581(para) +msgid "" +"Pages that use HTML, JavaScript, and CCS to enable users to interact with a " +"web page or show simple animation." +msgstr "" + +#: ./doc/glossary/glossary-terms.xml1589(title) +msgid "E" +msgstr "" + +#: ./doc/glossary/glossary-terms.xml1591(glossterm) +msgid "EBS boot volume" +msgstr "" + +#: ./doc/glossary/glossary-terms.xml1593(para) +msgid "" +"An Amazon EBS storage volume that contains a bootable VM image, currently " +"unsupported in OpenStack." +msgstr "" + +#: ./doc/glossary/glossary-terms.xml1599(glossterm) +msgid "ebtables" +msgstr "" + +#: ./doc/glossary/glossary-terms.xml1601(para) +msgid "" +"Used in nova along with arptables, iptables, and ip6tables to create " +"firewalls and to ensure isolation of network communications." +msgstr "" + +#: ./doc/glossary/glossary-terms.xml1607(glossterm) +msgid "EC2" +msgstr "" + +#: ./doc/glossary/glossary-terms.xml1609(para) +msgid "The Amazon commercial compute product, similar to nova." +msgstr "" + +#: ./doc/glossary/glossary-terms.xml1614(glossterm) +msgid "EC2 access key" +msgstr "" + +#: ./doc/glossary/glossary-terms.xml1616(para) +msgid "Used along with an EC2 secret key to access the nova EC2 API." +msgstr "" + +#: ./doc/glossary/glossary-terms.xml1621(glossterm) +msgid "EC2 API" +msgstr "" + +#: ./doc/glossary/glossary-terms.xml1623(para) +msgid "OpenStack supports accessing the Amazon EC2 API through nova." +msgstr "" + +#: ./doc/glossary/glossary-terms.xml1628(glossterm) +msgid "EC2 Compatibility API" +msgstr "" + +#: ./doc/glossary/glossary-terms.xml1630(para) +msgid "" +"A nova component that enables OpenStack to communicate with Amazon EC2." +msgstr "" + +#: ./doc/glossary/glossary-terms.xml1635(glossterm) +msgid "EC2 secret key" +msgstr "" + +#: ./doc/glossary/glossary-terms.xml1637(para) +msgid "" +"Used along with an EC2 access key when communicating with the nova EC2 API, " +"is used to digitally sign each request." +msgstr "" + +#: ./doc/glossary/glossary-terms.xml1643(glossterm) +msgid "Elastic Block Storage (EBS)" +msgstr "" + +#: ./doc/glossary/glossary-terms.xml1645(para) +msgid "The Amazon commercial block storage product." +msgstr "" + +#: ./doc/glossary/glossary-terms.xml1650(glossterm) +msgid "encryption" +msgstr "" + +#: ./doc/glossary/glossary-terms.xml1652(para) +msgid "" +"OpenStack supports encryption technologies such as HTTPS, SSH, SSL, TLS, " +"digital certificates, and data encryption." +msgstr "" + +#: ./doc/glossary/glossary-terms.xml1658(glossterm) +msgid "endpoint" +msgstr "" + +#: ./doc/glossary/glossary-terms.xml1660(para) +msgid "See API endpoint." +msgstr "" + +#: ./doc/glossary/glossary-terms.xml1664(glossterm) +msgid "endpoint registry" +msgstr "" + +#: ./doc/glossary/glossary-terms.xml1666(para) +msgid "Alternative term for a keystone catalog." +msgstr "" + +#: ./doc/glossary/glossary-terms.xml1670(glossterm) +msgid "endpoint template" +msgstr "" + +#: ./doc/glossary/glossary-terms.xml1672(para) +msgid "" +"A list of URL and port number endpoints that indicate where a service, such " +"as object storage, compute, identity, and so on, can be accessed." +msgstr "" + +#: ./doc/glossary/glossary-terms.xml1679(glossterm) +msgid "entity" +msgstr "" + +#: ./doc/glossary/glossary-terms.xml1681(para) +msgid "" +"Any piece of hardware or software that wants to connect to the network " +"services provided by neutron, the Network Connectivity service. An entity " +"can make use of neutron by implementing a VIF." +msgstr "" + +#: ./doc/glossary/glossary-terms.xml1689(glossterm) +msgid "ephemeral image" +msgstr "" + +#: ./doc/glossary/glossary-terms.xml1691(para) +msgid "" +"A VM image that does not save changes made to its volumes and reverts them " +"to their original state after the instance is terminated." +msgstr "" + +#: ./doc/glossary/glossary-terms.xml1697(glossterm) +msgid "ephemeral volume" +msgstr "" + +#: ./doc/glossary/glossary-terms.xml1699(para) +msgid "" +"Volume that does not save the changes made to it and reverts to its original" +" state when the current user relinquishes control." +msgstr "" + +#: ./doc/glossary/glossary-terms.xml1705(glossterm) +msgid "Essex" +msgstr "" + +#: ./doc/glossary/glossary-terms.xml1707(para) +msgid "" +"A grouped release of projects related to OpenStack that came out in April " +"2012, the fifth release of OpenStack. It included Compute (nova 2012.1), " +"Object Storage (swift 1.4.8), Image (glance), Identity (keystone), and " +"Dashboard (horizon)." +msgstr "" + +#: ./doc/glossary/glossary-terms.xml1716(glossterm) +msgid "ESX" +msgstr "" + +#: ./doc/glossary/glossary-terms.xml1718(para) +#: ./doc/glossary/glossary-terms.xml1724(para) +#: ./doc/glossary/glossary-terms.xml2614(para) +#: ./doc/glossary/glossary-terms.xml2682(para) +#: ./doc/glossary/glossary-terms.xml4508(para) +#: ./doc/glossary/glossary-terms.xml4627(para) +#: ./doc/glossary/glossary-terms.xml4762(para) +#: ./doc/glossary/glossary-terms.xml4827(para) +#: ./doc/glossary/glossary-terms.xml4841(para) +msgid "An OpenStack-supported hypervisor." +msgstr "" + +#: ./doc/glossary/glossary-terms.xml1722(glossterm) +msgid "ESXi" +msgstr "" + +#: ./doc/glossary/glossary-terms.xml1728(glossterm) +msgid "ETag" +msgstr "" + +#: ./doc/glossary/glossary-terms.xml1730(para) +msgid "MD5 hash of an object within swift, used to ensure data integrity." +msgstr "" + +#: ./doc/glossary/glossary-terms.xml1735(glossterm) +msgid "euca2ools" +msgstr "" + +#: ./doc/glossary/glossary-terms.xml1737(para) +msgid "" +"A collection of command line tools for administering VMs, most are " +"compatible with OpenStack." +msgstr "" + +#: ./doc/glossary/glossary-terms.xml1743(glossterm) +msgid "Eucalyptus Kernel Image (EKI)" +msgstr "" + +#: ./doc/glossary/glossary-terms.xml1745(para) +msgid "Used along with an ERI to create an EMI." +msgstr "" + +#: ./doc/glossary/glossary-terms.xml1749(glossterm) +msgid "Eucalyptus Machine Image (EMI)" +msgstr "" + +#: ./doc/glossary/glossary-terms.xml1751(para) +msgid "VM image container format supported by glance." +msgstr "" + +#: ./doc/glossary/glossary-terms.xml1756(glossterm) +msgid "Eucalyptus Ramdisk Image (ERI)" +msgstr "" + +#: ./doc/glossary/glossary-terms.xml1758(para) +msgid "Used along with an EKI to create an EMI." +msgstr "" + +#: ./doc/glossary/glossary-terms.xml1762(glossterm) +msgid "evacuate" +msgstr "" + +#: ./doc/glossary/glossary-terms.xml1764(para) +msgid "" +"The process of migrating one or all virtual machine (VM) instances from one " +"host to another, compatible with both shared storage live migration and " +"block migration." +msgstr "" + +#: ./doc/glossary/glossary-terms.xml1771(glossterm) +msgid "exchange" +msgstr "" + +#: ./doc/glossary/glossary-terms.xml1773(para) +msgid "Alternative term for a RabbitMQ message exchange." +msgstr "" + +#: ./doc/glossary/glossary-terms.xml1778(glossterm) +msgid "exchange type" +msgstr "" + +#: ./doc/glossary/glossary-terms.xml1780(para) +msgid "A routing algorithm in the nova RabbitMQ." +msgstr "" + +#: ./doc/glossary/glossary-terms.xml1784(glossterm) +msgid "exclusive queue" +msgstr "" + +#: ./doc/glossary/glossary-terms.xml1786(para) +msgid "" +"Connected to by a direct consumer in RabbitMQ / nova, the message can only " +"be consumed by the current connection." +msgstr "" + +#: ./doc/glossary/glossary-terms.xml1792(glossterm) +msgid "extended attributes (xattrs)" +msgstr "" + +#: ./doc/glossary/glossary-terms.xml1794(para) +msgid "" +"File system option that enables storage of additional information beyond " +"owner, group, permissions, modification time, and so on. The underlying " +"swift file system must support extended attributes." +msgstr "" + +#: ./doc/glossary/glossary-terms.xml1802(glossterm) +msgid "extension" +msgstr "" + +#: ./doc/glossary/glossary-terms.xml1804(para) +msgid "" +"Alternative term for a nova API extension or plug-in. In the context of " +"keystone this is a call that is specific to the implementation, such as " +"adding support for OpenID." +msgstr "" + +#: ./doc/glossary/glossary-terms.xml1811(glossterm) +msgid "extra specs" +msgstr "" + +#: ./doc/glossary/glossary-terms.xml1813(para) +msgid "" +"Specifies additional requirements when nova determines where to start a new " +"instance. Examples include a minimum amount of network bandwidth or a GPU." +msgstr "" + +#: ./doc/glossary/glossary-terms.xml1822(title) +msgid "F" +msgstr "" + +#: ./doc/glossary/glossary-terms.xml1824(glossterm) +msgid "FakeLDAP" +msgstr "" + +#: ./doc/glossary/glossary-terms.xml1826(para) +msgid "" +"An easy method to create a local LDAP directory for testing keystone and " +"nova. Requires Redis." +msgstr "" + +#: ./doc/glossary/glossary-terms.xml1832(glossterm) +msgid "fan-out exchange" +msgstr "" + +#: ./doc/glossary/glossary-terms.xml1834(para) +msgid "" +"Within RabbitMQ and nova it is the messaging interface that is used by the " +"scheduler service to receive capability messages from the compute, volume, " +"and network nodes." +msgstr "" + +#: ./doc/glossary/glossary-terms.xml1841(glossterm) +msgid "Fedora" +msgstr "" + +#: ./doc/glossary/glossary-terms.xml1843(para) +msgid "A Linux distribution compatible with OpenStack." +msgstr "" + +#: ./doc/glossary/glossary-terms.xml1848(glossterm) +msgid "Fibre Channel" +msgstr "" + +#: ./doc/glossary/glossary-terms.xml1850(para) +msgid "" +"Storage protocol similar in concept to TCP/IP, encapsulates SCSI commands " +"and data." +msgstr "" + +#: ./doc/glossary/glossary-terms.xml1855(glossterm) +msgid "Fibre Channel over Ethernet (FCoE)" +msgstr "" + +#: ./doc/glossary/glossary-terms.xml1857(para) +msgid "The fibre channel protocol tunneled within Ethernet." +msgstr "" + +#: ./doc/glossary/glossary-terms.xml1862(glossterm) +msgid "fill-first scheduler" +msgstr "" + +#: ./doc/glossary/glossary-terms.xml1864(para) +msgid "" +"The nova scheduling method that attempts to fill a host with VMs rather than" +" starting new VMs on a variety of hosts." +msgstr "" + +#: ./doc/glossary/glossary-terms.xml1870(glossterm) +msgid "filter" +msgstr "" + +#: ./doc/glossary/glossary-terms.xml1872(para) +msgid "" +"The step in the nova scheduling process when hosts that cannot run VMs are " +"eliminated and not chosen." +msgstr "" + +#: ./doc/glossary/glossary-terms.xml1878(glossterm) +msgid "firewall" +msgstr "" + +#: ./doc/glossary/glossary-terms.xml1880(para) +msgid "" +"Used to restrict communications between hosts and/or nodes, implemented in " +"nova using iptables, arptables, ip6tables and etables." +msgstr "" + +#: ./doc/glossary/glossary-terms.xml1886(glossterm) +msgid "fixed IP address" +msgstr "" + +#: ./doc/glossary/glossary-terms.xml1888(para) +msgid "" +"An IP address that is associated with the same instance each time that " +"instance boots, generally not accessible to end users or the public " +"internet, used for management of the instance." +msgstr "" + +#: ./doc/glossary/glossary-terms.xml1896(glossterm) +msgid "Flat Manager" +msgstr "" + +#: ./doc/glossary/glossary-terms.xml1898(para) +msgid "" +"The nova component that gives IP addresses to authorized nodes and assumes " +"DHCP, DNS, and routing configuration and services are provided by something " +"else." +msgstr "" + +#: ./doc/glossary/glossary-terms.xml1905(glossterm) +msgid "flat mode injection" +msgstr "" + +#: ./doc/glossary/glossary-terms.xml1907(para) +msgid "" +"A nova networking method where the OS network configuration information is " +"injected into the VM image before the instance starts." +msgstr "" + +#: ./doc/glossary/glossary-terms.xml1913(glossterm) +msgid "flat network" +msgstr "" + +#: ./doc/glossary/glossary-terms.xml1915(para) +msgid "" +"The Network Controller provides virtual networks to enable compute servers " +"to interact with each other and with the public network. All machines must " +"have a public and private network interface. A flat network is a private " +"network interface, which is controlled by the flat_interface option with " +"flat managers." +msgstr "" + +#: ./doc/glossary/glossary-terms.xml1925(glossterm) +msgid "FlatDHCP Manager" +msgstr "" + +#: ./doc/glossary/glossary-terms.xml1927(para) +msgid "" +"The nova component that provides dnsmasq (DHCP, DNS, BOOTP, TFTP) and radvd " +"(routing) services." +msgstr "" + +#: ./doc/glossary/glossary-terms.xml1933(glossterm) +msgid "flavor" +msgstr "" + +#: ./doc/glossary/glossary-terms.xml1935(para) +msgid "Alternative term for a VM instance type." +msgstr "" + +#: ./doc/glossary/glossary-terms.xml1939(glossterm) +msgid "flavor ID" +msgstr "" + +#: ./doc/glossary/glossary-terms.xml1941(para) +msgid "UUID for each nova or glance VM flavor or instance type." +msgstr "" + +#: ./doc/glossary/glossary-terms.xml1946(glossterm) +msgid "floating IP address" +msgstr "" + +#: ./doc/glossary/glossary-terms.xml1948(para) +msgid "" +"An IP address that a nova project can associate with a VM so the instance " +"has the same public IP address each time that it boots. You create a pool of" +" floating IP addresses and assign them to instances as they are launched to " +"maintain a consistent IP address for maintaining DNS assignment." +msgstr "" + +#: ./doc/glossary/glossary-terms.xml1958(glossterm) +msgid "Folsom" +msgstr "" + +#: ./doc/glossary/glossary-terms.xml1960(para) +msgid "" +"A grouped release of projects related to OpenStack that came out in the fall" +" of 2012, the sixth release of OpenStack. It includes Compute (nova), Object" +" Storage (swift), Identity (keystone), Networking (neutron), Image service " +"(glance) and Volumes or Block Storage (cinder)." +msgstr "" + +#: ./doc/glossary/glossary-terms.xml1970(glossterm) +msgid "FormPost" +msgstr "" + +#: ./doc/glossary/glossary-terms.xml1972(para) +msgid "" +"swift middleware that uploads (posts) an image through a form on a web page." +msgstr "" + +#: ./doc/glossary/glossary-terms.xml1978(glossterm) +msgid "front-end" +msgstr "" + +#: ./doc/glossary/glossary-terms.xml1980(para) +msgid "" +"The point where a user interacts with a service, can be an API endpoint, the" +" horizon dashboard, or a command line tool." +msgstr "" + +#: ./doc/glossary/glossary-terms.xml1994(title) +msgid "G" +msgstr "" + +#: ./doc/glossary/glossary-terms.xml1996(glossterm) +msgid "gateway" +msgstr "" + +#: ./doc/glossary/glossary-terms.xml1998(para) +msgid "Hardware or software that translates between two different protocols." +msgstr "" + +#: ./doc/glossary/glossary-terms.xml2003(glossterm) +msgid "Glance" +msgstr "" + +#: ./doc/glossary/glossary-terms.xml2005(para) +msgid "A core project that provides the OpenStack Image Service." +msgstr "" + +#: ./doc/glossary/glossary-terms.xml2010(glossterm) +msgid "glance API server" +msgstr "" + +#: ./doc/glossary/glossary-terms.xml2012(para) +msgid "" +"Processes client requests for VMs, updates glance metadata on the registry " +"server, and communicates with the store adapter to upload VM images from the" +" back-end store." +msgstr "" + +#: ./doc/glossary/glossary-terms.xml2019(glossterm) +msgid "glance registry" +msgstr "" + +#: ./doc/glossary/glossary-terms.xml2021(para) +#: ./doc/glossary/glossary-terms.xml3691(para) +msgid "Alternative term for the glance image registry." +msgstr "" + +#: ./doc/glossary/glossary-terms.xml2026(glossterm) +msgid "global endpoint template" +msgstr "" + +#: ./doc/glossary/glossary-terms.xml2028(para) +msgid "" +"The keystone endpoint template that contains services available to all " +"tenants." +msgstr "" + +#: ./doc/glossary/glossary-terms.xml2033(glossterm) +msgid "GlusterFS" +msgstr "" + +#: ./doc/glossary/glossary-terms.xml2035(para) +msgid "" +"A file system designed to aggregate NAS hosts, compatible with OpenStack." +msgstr "" + +#: ./doc/glossary/glossary-terms.xml2040(glossterm) +msgid "golden image" +msgstr "" + +#: ./doc/glossary/glossary-terms.xml2042(para) +msgid "" +"A method of operating system installation where a finalized disk image is " +"created and then used by all nodes without modification." +msgstr "" + +#: ./doc/glossary/glossary-terms.xml2048(glossterm) +msgid "Graphic Interchange Format (GIF)" +msgstr "" + +#: ./doc/glossary/glossary-terms.xml2050(para) +msgid "" +"A type of image file that is commonly used for animated images on web pages." +msgstr "" + +#: ./doc/glossary/glossary-terms.xml2055(glossterm) +msgid "Graphics Processing Unit (GPU)" +msgstr "" + +#: ./doc/glossary/glossary-terms.xml2057(para) +msgid "" +"Choosing a host based on the existence of a GPU is currently unsupported in " +"OpenStack." +msgstr "" + +#: ./doc/glossary/glossary-terms.xml2062(glossterm) +msgid "Green Threads" +msgstr "" + +#: ./doc/glossary/glossary-terms.xml2064(para) +msgid "" +"The cooperative threading model used by Python, reduces race conditions, and" +" only context switches when specific library calls are made. Each OpenStack " +"service is its own thread." +msgstr "" + +#: ./doc/glossary/glossary-terms.xml2071(glossterm) +msgid "Grizzly" +msgstr "" + +#: ./doc/glossary/glossary-terms.xml2073(para) +msgid "Project name for the seventh release of OpenStack." +msgstr "" + +#: ./doc/glossary/glossary-terms.xml2078(glossterm) +msgid "guest OS" +msgstr "" + +#: ./doc/glossary/glossary-terms.xml2080(para) +msgid "" +"An operating system instance running under the control of a hypervisor." +msgstr "" + +#: ./doc/glossary/glossary-terms.xml2087(title) +msgid "H" +msgstr "" + +#: ./doc/glossary/glossary-terms.xml2089(glossterm) +msgid "Hadoop" +msgstr "" + +#: ./doc/glossary/glossary-terms.xml2091(para) +msgid "" +"Apache Hadoop is an open-source software framework that supports data-" +"intensive distributed applications." +msgstr "" + +#: ./doc/glossary/glossary-terms.xml2097(glossterm) +msgid "handover" +msgstr "" + +#: ./doc/glossary/glossary-terms.xml2099(para) +msgid "" +"An object state in swift where a new replica of the object is automatically " +"created due to a drive failure." +msgstr "" + +#: ./doc/glossary/glossary-terms.xml2105(glossterm) +msgid "hard reboot" +msgstr "" + +#: ./doc/glossary/glossary-terms.xml2107(para) +msgid "" +"A type of reboot where a physical or virtual power button is pressed as " +"opposed to a graceful, proper shutdown of the operating system." +msgstr "" + +#: ./doc/glossary/glossary-terms.xml2113(glossterm) +msgid "Havana" +msgstr "" + +#: ./doc/glossary/glossary-terms.xml2115(para) +msgid "Project name for the eighth release of OpenStack." +msgstr "" + +#: ./doc/glossary/glossary-terms.xml2120(glossterm) +msgid "Heat" +msgstr "" + +#: ./doc/glossary/glossary-terms.xml2122(para) +msgid "" +"An integrated project that aims to orchestrate multiple cloud applications " +"for OpenStack." +msgstr "" + +#: ./doc/glossary/glossary-terms.xml2127(glossterm) +msgid "Horizon" +msgstr "" + +#: ./doc/glossary/glossary-terms.xml2129(para) +msgid "OpenStack project that provides a dashboard, which is a web interface." +msgstr "" + +#: ./doc/glossary/glossary-terms.xml2134(glossterm) +msgid "horizon plug-in" +msgstr "" + +#: ./doc/glossary/glossary-terms.xml2136(para) +msgid "A plug-in for the OpenStack dashboard (horizon)." +msgstr "" + +#: ./doc/glossary/glossary-terms.xml2141(glossterm) +msgid "host" +msgstr "" + +#: ./doc/glossary/glossary-terms.xml2143(para) +msgid "A physical computer, not a VM instance (node)." +msgstr "" + +#: ./doc/glossary/glossary-terms.xml2148(glossterm) +msgid "host aggregate" +msgstr "" + +#: ./doc/glossary/glossary-terms.xml2150(para) +msgid "" +"A method to further subdivide availability zones into hypervisor pools, a " +"collection of common hosts." +msgstr "" + +#: ./doc/glossary/glossary-terms.xml2156(glossterm) +msgid "Host Bus Adapter (HBA)" +msgstr "" + +#: ./doc/glossary/glossary-terms.xml2158(para) +msgid "" +"Device plugged into a PCI slot such as a fibre channel or network card." +msgstr "" + +#: ./doc/glossary/glossary-terms.xml2163(glossterm) +msgid "HTTP" +msgstr "" + +#: ./doc/glossary/glossary-terms.xml2165(para) +msgid "" +"Hypertext Transfer Protocol. HTTP is an application protocol for " +"distributed, collaborative, hypermedia information systems. It is the " +"foundation of data communication for the World Wide Web. Hypertext is " +"structured text that uses logical links (hyper links) between nodes " +"containing text. HTTP is the protocol to exchange or transfer hypertext." +msgstr "" + +#: ./doc/glossary/glossary-terms.xml2176(glossterm) +msgid "HTTPS" +msgstr "" + +#: ./doc/glossary/glossary-terms.xml2178(para) +msgid "" +"Hypertext Transfer Protocol Secure (HTTPS) is a communications protocol for " +"secure communication over a computer network, with especially wide " +"deployment on the Internet. Technically, it is not a protocol in and of " +"itself; rather, it is the result of simply layering the Hypertext Transfer " +"Protocol (HTTP) on top of the SSL/TLS protocol, thus adding the security " +"capabilities of SSL/TLS to standard HTTP communications." +msgstr "" + +#: ./doc/glossary/glossary-terms.xml2191(glossterm) +msgid "Hyper-V" +msgstr "" + +#: ./doc/glossary/glossary-terms.xml2193(para) +msgid "One of the hypervisors supported by OpenStack." +msgstr "" + +#: ./doc/glossary/glossary-terms.xml2198(glossterm) +msgid "hyper link" +msgstr "" + +#: ./doc/glossary/glossary-terms.xml2200(para) +msgid "" +"Any kind of text that contains a link to some other site, commonly found in " +"documents where clicking on a word or words opens up a different web site." +msgstr "" + +#: ./doc/glossary/glossary-terms.xml2207(glossterm) +msgid "HyperText Transfer Protocol (HTTP)" +msgstr "" + +#: ./doc/glossary/glossary-terms.xml2209(para) +msgid "The protocol that tells browsers where to go to find information." +msgstr "" + +#: ./doc/glossary/glossary-terms.xml2214(glossterm) +msgid "Hypertext Transfer Protocol Secure (HTTPS)" +msgstr "" + +#: ./doc/glossary/glossary-terms.xml2217(para) +msgid "" +"Encrypted HTTP communications using SSL or TLS, most OpenStack API endpoints" +" and many inter-component communications support HTTPS communication." +msgstr "" + +#: ./doc/glossary/glossary-terms.xml2224(glossterm) +msgid "hypervisor" +msgstr "" + +#: ./doc/glossary/glossary-terms.xml2226(para) +msgid "" +"Software that arbitrates and controls VM access to the actual underlying " +"hardware." +msgstr "" + +#: ./doc/glossary/glossary-terms.xml2231(glossterm) +msgid "hypervisor pool" +msgstr "" + +#: ./doc/glossary/glossary-terms.xml2233(para) +msgid "A collection of hypervisors grouped together through host aggregates." +msgstr "" + +#: ./doc/glossary/glossary-terms.xml2246(title) +msgid "I" +msgstr "" + +#: ./doc/glossary/glossary-terms.xml2248(glossterm) +msgid "IaaS" +msgstr "" + +#: ./doc/glossary/glossary-terms.xml2250(para) +msgid "" +"Infrastructure as a Service. IaaS is a provision model in which an " +"organization outsources the equipment used to support operations, including " +"storage, hardware, servers and networking components. The service provider " +"owns the equipment and is responsible for housing, running and maintaining " +"it. The client typically pays on a per-use basis. IaaS is a model for " +"providing cloud services." +msgstr "" + +#: ./doc/glossary/glossary-terms.xml2262(glossterm) +msgid "Icehouse" +msgstr "" + +#: ./doc/glossary/glossary-terms.xml2264(para) +msgid "Project name for the ninth release of OpenStack." +msgstr "" + +#: ./doc/glossary/glossary-terms.xml2268(glossterm) +msgid "ID number" +msgstr "" + +#: ./doc/glossary/glossary-terms.xml2270(para) +msgid "" +"Unique numeric ID associated with each user in keystone, conceptually " +"similar to a Linux or LDAP UID." +msgstr "" + +#: ./doc/glossary/glossary-terms.xml2276(glossterm) +msgid "Identity API" +msgstr "" + +#: ./doc/glossary/glossary-terms.xml2278(para) +msgid "Alternative term for the Identity Service API." +msgstr "" + +#: ./doc/glossary/glossary-terms.xml2283(glossterm) +msgid "Identity back-end" +msgstr "" + +#: ./doc/glossary/glossary-terms.xml2285(para) +msgid "" +"The source used by keystone to retrieve user information an OpenLDAP server " +"for example." +msgstr "" + +#: ./doc/glossary/glossary-terms.xml2290(glossterm) +msgid "Identity Service" +msgstr "" + +#: ./doc/glossary/glossary-terms.xml2292(para) +msgid "The identity service provided by the keystone project." +msgstr "" + +#: ./doc/glossary/glossary-terms.xml2297(glossterm) +msgid "Identity Service API" +msgstr "" + +#: ./doc/glossary/glossary-terms.xml2299(para) +msgid "" +"The API used to access the OpenStack Identity Service provided through " +"keystone." +msgstr "" + +#: ./doc/glossary/glossary-terms.xml2304(glossterm) +msgid "IDS" +msgstr "" + +#: ./doc/glossary/glossary-terms.xml2306(para) +msgid "Intrusion Detection System" +msgstr "" + +#: ./doc/glossary/glossary-terms.xml2311(glossterm) +msgid "image" +msgstr "" + +#: ./doc/glossary/glossary-terms.xml2313(para) +msgid "" +"A collection of files for a specific operating system (OS) that you use to " +"create or rebuild a server. OpenStack provides pre-built images. You can " +"also create custom images, or snapshots, from servers that you have " +"launched. Custom images can be used for data backups or as \"gold\" images " +"for additional servers." +msgstr "" + +#: ./doc/glossary/glossary-terms.xml2323(glossterm) +msgid "Image API" +msgstr "" + +#: ./doc/glossary/glossary-terms.xml2325(para) +msgid "The glance API endpoint for management of VM images." +msgstr "" + +#: ./doc/glossary/glossary-terms.xml2330(glossterm) +msgid "image cache" +msgstr "" + +#: ./doc/glossary/glossary-terms.xml2332(para) +msgid "" +"Used by glance to obtain images on the local host rather than re-downloading" +" them from the image server each time one is requested." +msgstr "" + +#: ./doc/glossary/glossary-terms.xml2339(glossterm) +msgid "image ID" +msgstr "" + +#: ./doc/glossary/glossary-terms.xml2341(para) +msgid "" +"Combination of URI and UUID used to access glance VM images through the " +"image API." +msgstr "" + +#: ./doc/glossary/glossary-terms.xml2346(glossterm) +msgid "image membership" +msgstr "" + +#: ./doc/glossary/glossary-terms.xml2348(para) +#: ./doc/glossary/glossary-terms.xml2781(para) +msgid "A list of tenants that can access a given VM image within glance." +msgstr "" + +#: ./doc/glossary/glossary-terms.xml2353(glossterm) +msgid "image owner" +msgstr "" + +#: ./doc/glossary/glossary-terms.xml2355(para) +msgid "The keystone tenant who owns a glance virtual machine image." +msgstr "" + +#: ./doc/glossary/glossary-terms.xml2360(glossterm) +msgid "image registry" +msgstr "" + +#: ./doc/glossary/glossary-terms.xml2362(para) +msgid "A list of VM images that are available through glance." +msgstr "" + +#: ./doc/glossary/glossary-terms.xml2367(glossterm) +msgid "Image Service API" +msgstr "" + +#: ./doc/glossary/glossary-terms.xml2369(para) +msgid "Alternative name for the glance image API." +msgstr "" + +#: ./doc/glossary/glossary-terms.xml2374(glossterm) +msgid "image status" +msgstr "" + +#: ./doc/glossary/glossary-terms.xml2376(para) +msgid "" +"The current status of a VM image in glance, not to be confused with the " +"status of a running instance." +msgstr "" + +#: ./doc/glossary/glossary-terms.xml2382(glossterm) +msgid "image store" +msgstr "" + +#: ./doc/glossary/glossary-terms.xml2384(para) +msgid "" +"The back-end store used by glance to store VM images, options include swift," +" local file system, S3, or HTTP." +msgstr "" + +#: ./doc/glossary/glossary-terms.xml2390(glossterm) +msgid "image UUID" +msgstr "" + +#: ./doc/glossary/glossary-terms.xml2392(para) +msgid "UUID used by glance to uniquely identify each VM image." +msgstr "" + +#: ./doc/glossary/glossary-terms.xml2397(glossterm) +msgid "incubated project" +msgstr "" + +#: ./doc/glossary/glossary-terms.xml2399(para) +msgid "" +"A community project may be elevated to this status and is then promoted to a" +" core project." +msgstr "" + +#: ./doc/glossary/glossary-terms.xml2405(glossterm) +msgid "ingress filtering" +msgstr "" + +#: ./doc/glossary/glossary-terms.xml2407(para) +msgid "The process of filtering incoming network traffic. Supported by nova." +msgstr "" + +#: ./doc/glossary/glossary-terms.xml2412(glossterm) +msgid "injection" +msgstr "" + +#: ./doc/glossary/glossary-terms.xml2414(para) +msgid "" +"The process of putting a file into a virtual machine image before the " +"instance is started." +msgstr "" + +#: ./doc/glossary/glossary-terms.xml2420(glossterm) +msgid "instance" +msgstr "" + +#: ./doc/glossary/glossary-terms.xml2422(para) +msgid "" +"A running VM, or a VM in a known state such as suspended that can be used " +"like a hardware server." +msgstr "" + +#: ./doc/glossary/glossary-terms.xml2428(glossterm) +msgid "instance ID" +msgstr "" + +#: ./doc/glossary/glossary-terms.xml2430(para) +msgid "Alternative term for instance UUID." +msgstr "" + +#: ./doc/glossary/glossary-terms.xml2434(glossterm) +msgid "instance state" +msgstr "" + +#: ./doc/glossary/glossary-terms.xml2436(para) +msgid "The current state of a nova VM image." +msgstr "" + +#: ./doc/glossary/glossary-terms.xml2440(glossterm) +msgid "instance type" +msgstr "" + +#: ./doc/glossary/glossary-terms.xml2442(para) +msgid "" +"Describes the parameters of the various virtual machine images that are " +"available to users, includes parameters such as CPU, storage, and memory. " +"Alternative term for flavor." +msgstr "" + +#: ./doc/glossary/glossary-terms.xml2449(glossterm) +msgid "instance type ID" +msgstr "" + +#: ./doc/glossary/glossary-terms.xml2451(para) +msgid "Alternative term for a flavor ID." +msgstr "" + +#: ./doc/glossary/glossary-terms.xml2455(glossterm) +msgid "instance UUID" +msgstr "" + +#: ./doc/glossary/glossary-terms.xml2457(para) +#: ./doc/glossary/glossary-terms.xml3969(para) +msgid "Unique ID assigned to each nova VM instance." +msgstr "" + +#: ./doc/glossary/glossary-terms.xml2462(glossterm) +msgid "interface ID" +msgstr "" + +#: ./doc/glossary/glossary-terms.xml2464(para) +msgid "Unique ID for a neutron VIF or vNIC in the form of a UUID." +msgstr "" + +#: ./doc/glossary/glossary-terms.xml2469(glossterm) +msgid "Internet Service Provider (ISP)" +msgstr "" + +#: ./doc/glossary/glossary-terms.xml2471(para) +msgid "" +"Any business that provides Internet access to individuals or businesses." +msgstr "" + +#: ./doc/glossary/glossary-terms.xml2476(glossterm) +msgid "Ironic" +msgstr "" + +#: ./doc/glossary/glossary-terms.xml2478(para) +msgid "" +"OpenStack project that provisions bare metal, as opposed to virtual, " +"machines." +msgstr "" + +#: ./doc/glossary/glossary-terms.xml2483(glossterm) +msgid "IP address" +msgstr "" + +#: ./doc/glossary/glossary-terms.xml2485(para) +msgid "" +"Number that is unique to every computer system on the Internet. Two versions" +" of the Internet Protocol (IP) are in use for addresses: IPv4 and IPv6." +msgstr "" + +#: ./doc/glossary/glossary-terms.xml2492(glossterm) +msgid "IP Address Management (IPAM)" +msgstr "" + +#: ./doc/glossary/glossary-terms.xml2494(para) +msgid "" +"The process of automating IP address allocation, deallocation, and " +"management. Currently provided by nova, melange, and neutron." +msgstr "" + +#: ./doc/glossary/glossary-terms.xml2500(glossterm) +msgid "IPL" +msgstr "" + +#: ./doc/glossary/glossary-terms.xml2502(para) +msgid "Initial Program Loader." +msgstr "" + +#: ./doc/glossary/glossary-terms.xml2506(glossterm) +msgid "IPMI" +msgstr "" + +#: ./doc/glossary/glossary-terms.xml2508(para) +msgid "" +"Intelligent Platform Management Interface. IPMI is a standardized computer " +"system interface used by system administrators for out-of-band management of" +" computer systems and monitoring of their operation. In layman's terms, it " +"is a way to manage a computer using a direct network connection, whether it " +"is turned on or not; connecting to the hardware rather than an operating " +"system or login shell." +msgstr "" + +#: ./doc/glossary/glossary-terms.xml2520(glossterm) +msgid "iptables" +msgstr "" + +#: ./doc/glossary/glossary-terms.xml2522(para) +msgid "" +"Used along with arptables and ebtables, iptables create firewalls in nova. " +"iptables are the tables provided by the Linux kernel firewall (implemented " +"as different Netfilter modules) and the chains and rules it stores. " +"Different kernel modules and programs are currently used for different " +"protocols; iptables applies to IPv4, ip6tables to IPv6, arptables to ARP, " +"and ebtables to Ethernet frames. Requires root privilege to manipulate." +msgstr "" + +#: ./doc/glossary/glossary-terms.xml2535(glossterm) +msgid "iSCSI" +msgstr "" + +#: ./doc/glossary/glossary-terms.xml2537(para) +msgid "" +"The SCSI disk protocol tunneled within Ethernet, supported by nova, swift, " +"and glance." +msgstr "" + +#: ./doc/glossary/glossary-terms.xml2542(glossterm) +msgid "ISO9960" +msgstr "" + +#: ./doc/glossary/glossary-terms.xml2544(para) +#: ./doc/glossary/glossary-terms.xml3498(para) +#: ./doc/glossary/glossary-terms.xml4538(para) +#: ./doc/glossary/glossary-terms.xml4545(para) +#: ./doc/glossary/glossary-terms.xml4653(para) +msgid "One of the VM image disk formats supported by glance." +msgstr "" + +#: ./doc/glossary/glossary-terms.xml2549(glossterm) +msgid "itsec" +msgstr "" + +#: ./doc/glossary/glossary-terms.xml2551(para) +msgid "" +"A default role in the nova RBAC system that can quarantine an instance in " +"any project." +msgstr "" + +#: ./doc/glossary/glossary-terms.xml2565(title) +msgid "J" +msgstr "" + +#: ./doc/glossary/glossary-terms.xml2567(glossterm) +msgid "Java" +msgstr "" + +#: ./doc/glossary/glossary-terms.xml2569(para) +msgid "" +"A programming language that is used to create systems that involve more than" +" one computer by way of a network." +msgstr "" + +#: ./doc/glossary/glossary-terms.xml2575(glossterm) +msgid "JavaScript" +msgstr "" + +#: ./doc/glossary/glossary-terms.xml2577(para) +msgid "A scripting language that is used to build web pages." +msgstr "" + +#: ./doc/glossary/glossary-terms.xml2582(glossterm) +msgid "JavaScript Object Notation (JSON)" +msgstr "" + +#: ./doc/glossary/glossary-terms.xml2584(para) +msgid "One of the supported response formats in OpenStack." +msgstr "" + +#: ./doc/glossary/glossary-terms.xml2589(glossterm) +msgid "Jenkins" +msgstr "" + +#: ./doc/glossary/glossary-terms.xml2591(para) +msgid "Tool used to run jobs automatically for OpenStack development." +msgstr "" + +#: ./doc/glossary/glossary-terms.xml2596(glossterm) +msgid "Juno" +msgstr "" + +#: ./doc/glossary/glossary-terms.xml2598(para) +msgid "Project name for the tenth release of OpenStack." +msgstr "" + +#: ./doc/glossary/glossary-terms.xml2610(title) +msgid "K" +msgstr "" + +#: ./doc/glossary/glossary-terms.xml2612(glossterm) +msgid "kernel-based VM (KVM)" +msgstr "" + +#: ./doc/glossary/glossary-terms.xml2618(glossterm) +msgid "Keystone" +msgstr "" + +#: ./doc/glossary/glossary-terms.xml2620(para) +msgid "The project that provides OpenStack Identity services." +msgstr "" + +#: ./doc/glossary/glossary-terms.xml2625(glossterm) +msgid "Kickstart" +msgstr "" + +#: ./doc/glossary/glossary-terms.xml2627(para) +msgid "" +"A tool to automate system configuration and installation on Red Hat, Fedora," +" and CentOS based Linux distributions." +msgstr "" + +#: ./doc/glossary/glossary-terms.xml2635(title) +msgid "L" +msgstr "" + +#: ./doc/glossary/glossary-terms.xml2637(glossterm) +msgid "large object" +msgstr "" + +#: ./doc/glossary/glossary-terms.xml2639(para) +msgid "An object within swift that is larger than 5 GBs." +msgstr "" + +#: ./doc/glossary/glossary-terms.xml2644(glossterm) +msgid "Launchpad" +msgstr "" + +#: ./doc/glossary/glossary-terms.xml2646(para) +msgid "The collaboration site for OpenStack." +msgstr "" + +#: ./doc/glossary/glossary-terms.xml2650(glossterm) +msgid "Layer-2 network" +msgstr "" + +#: ./doc/glossary/glossary-terms.xml2652(para) +msgid "Term used for OSI network architecture for the data link layer." +msgstr "" + +#: ./doc/glossary/glossary-terms.xml2657(glossterm) +msgid "libvirt" +msgstr "" + +#: ./doc/glossary/glossary-terms.xml2659(para) +msgid "" +"Virtualization API library used by OpenStack to interact with many of its " +"supported hypervisors." +msgstr "" + +#: ./doc/glossary/glossary-terms.xml2665(glossterm) +msgid "Linux bridge" +msgstr "" + +#: ./doc/glossary/glossary-terms.xml2667(para) +msgid "" +"Software that enables multiple VMs to share a single physical NIC within " +"nova." +msgstr "" + +#: ./doc/glossary/glossary-terms.xml2672(glossterm) +msgid "Linux Bridge neutron plug-in" +msgstr "" + +#: ./doc/glossary/glossary-terms.xml2674(para) +msgid "" +"Enables a Linux bridge to understand a neutron port, interface attachment, " +"and other abstractions." +msgstr "" + +#: ./doc/glossary/glossary-terms.xml2680(glossterm) +msgid "Linux containers (LXC)" +msgstr "" + +#: ./doc/glossary/glossary-terms.xml2686(glossterm) +msgid "live migration" +msgstr "" + +#: ./doc/glossary/glossary-terms.xml2688(para) +msgid "" +"The ability within nova to move running virtual machine instances from one " +"host to another with only a small service interruption during switch-over." +msgstr "" + +#: ./doc/glossary/glossary-terms.xml2695(glossterm) +msgid "load balancer" +msgstr "" + +#: ./doc/glossary/glossary-terms.xml2697(para) +msgid "" +"A load balancer is a logical device which belongs to a cloud account. It is " +"used to distribute workloads between multiple back-end systems or services, " +"based on the criteria defined as part of its configuration." +msgstr "" + +#: ./doc/glossary/glossary-terms.xml2705(glossterm) +msgid "load balancing" +msgstr "" + +#: ./doc/glossary/glossary-terms.xml2707(para) +msgid "" +"The process of spreading client requests between two or more nodes to " +"improve performance and availability." +msgstr "" + +#: ./doc/glossary/glossary-terms.xml2721(title) +msgid "M" +msgstr "" + +#: ./doc/glossary/glossary-terms.xml2723(glossterm) +msgid "management API" +msgstr "" + +#: ./doc/glossary/glossary-terms.xml2725(para) +msgid "Alternative term for an admin API." +msgstr "" + +#: ./doc/glossary/glossary-terms.xml2729(glossterm) +msgid "management network" +msgstr "" + +#: ./doc/glossary/glossary-terms.xml2731(para) +msgid "" +"A network segment used for administration, not accessible to the public " +"internet." +msgstr "" + +#: ./doc/glossary/glossary-terms.xml2736(glossterm) +msgid "manager" +msgstr "" + +#: ./doc/glossary/glossary-terms.xml2738(para) +msgid "" +"Logical groupings of related code such as the nova volume manager or network" +" manager." +msgstr "" + +#: ./doc/glossary/glossary-terms.xml2743(glossterm) +msgid "manifest" +msgstr "" + +#: ./doc/glossary/glossary-terms.xml2745(para) +msgid "Used to track segments of a large object within swift." +msgstr "" + +#: ./doc/glossary/glossary-terms.xml2750(glossterm) +msgid "manifest object" +msgstr "" + +#: ./doc/glossary/glossary-terms.xml2752(para) +msgid "A special swift object that contains the manifest for a large object." +msgstr "" + +#: ./doc/glossary/glossary-terms.xml2757(glossterm) +msgid "Marconi" +msgstr "" + +#: ./doc/glossary/glossary-terms.xml2759(para) +msgid "OpenStack project that provides a queue service to applications." +msgstr "" + +#: ./doc/glossary/glossary-terms.xml2764(glossterm) +msgid "Melange" +msgstr "" + +#: ./doc/glossary/glossary-terms.xml2766(para) +msgid "" +"Project name for OpenStack Network Information Service. To be merged with " +"neutron." +msgstr "" + +#: ./doc/glossary/glossary-terms.xml2771(glossterm) +msgid "membership" +msgstr "" + +#: ./doc/glossary/glossary-terms.xml2773(para) +msgid "" +"The association between a glance VM image and a tenant. Enables images to be" +" shared with specified tenants." +msgstr "" + +#: ./doc/glossary/glossary-terms.xml2779(glossterm) +msgid "membership list" +msgstr "" + +#: ./doc/glossary/glossary-terms.xml2786(glossterm) +msgid "memcached" +msgstr "" + +#: ./doc/glossary/glossary-terms.xml2788(para) +msgid "" +"A distributed memory object caching system that is used by swift for " +"caching." +msgstr "" + +#: ./doc/glossary/glossary-terms.xml2793(glossterm) +msgid "memory overcommit" +msgstr "" + +#: ./doc/glossary/glossary-terms.xml2795(para) +msgid "" +"The ability to start new VM instances based on the actual memory usage of a " +"host, as opposed to basing the decision on the amount of RAM each running " +"instance thinks it has available. Also known as RAM overcommit." +msgstr "" + +#: ./doc/glossary/glossary-terms.xml2803(glossterm) +msgid "message broker" +msgstr "" + +#: ./doc/glossary/glossary-terms.xml2805(para) +msgid "" +"The software package used to provide AMQP messaging capabilities within " +"nova. Default package is RabbitMQ." +msgstr "" + +#: ./doc/glossary/glossary-terms.xml2811(glossterm) +msgid "message bus" +msgstr "" + +#: ./doc/glossary/glossary-terms.xml2813(para) +msgid "" +"The main virtual communication line used by all AMQP messages for inter-" +"cloud communications within nova." +msgstr "" + +#: ./doc/glossary/glossary-terms.xml2819(glossterm) +msgid "message queue" +msgstr "" + +#: ./doc/glossary/glossary-terms.xml2821(para) +msgid "" +"Passes requests from clients to the appropriate workers and returns the " +"output to the client after the job completes." +msgstr "" + +#: ./doc/glossary/glossary-terms.xml2827(glossterm) +msgid "Meta-Data Server (MDS)" +msgstr "" + +#: ./doc/glossary/glossary-terms.xml2829(para) +msgid "Stores CephFS metadata." +msgstr "" + +#: ./doc/glossary/glossary-terms.xml2833(glossterm) +msgid "migration" +msgstr "" + +#: ./doc/glossary/glossary-terms.xml2835(para) +msgid "The process of moving a VM instance from one host to another." +msgstr "" + +#: ./doc/glossary/glossary-terms.xml2840(glossterm) +msgid "Modular Layer 2 (ML2) neutron plug-in" +msgstr "" + +#: ./doc/glossary/glossary-terms.xml2842(para) +msgid "" +"Can concurrently use multiple layer 2 networking technologies, such as " +"802.1Q and VXLAN, in neutron." +msgstr "" + +#: ./doc/glossary/glossary-terms.xml2848(glossterm) +msgid "Monitor (Mon)" +msgstr "" + +#: ./doc/glossary/glossary-terms.xml2850(para) +msgid "" +"A Ceph component that communicates with external clients, checks data state " +"and consistency, and performs quorum functions." +msgstr "" + +#: ./doc/glossary/glossary-terms.xml2856(glossterm) +msgid "multi-factor authentication" +msgstr "" + +#: ./doc/glossary/glossary-terms.xml2858(para) +msgid "" +"Authentication method that uses two or more credentials, such as a password " +"and a private key. Currently not supported in keystone." +msgstr "" + +#: ./doc/glossary/glossary-terms.xml2864(glossterm) +msgid "MultiNic" +msgstr "" + +#: ./doc/glossary/glossary-terms.xml2866(para) +msgid "" +"Facility in nova that enables a virtual machine instance to have more than " +"one VIF connected to it." +msgstr "" + +#: ./doc/glossary/glossary-terms.xml2880(title) +msgid "N" +msgstr "" + +#: ./doc/glossary/glossary-terms.xml2882(glossterm) +msgid "Nebula" +msgstr "" + +#: ./doc/glossary/glossary-terms.xml2884(para) +msgid "Released as open source by NASA in 2010 and is the basis for nova." +msgstr "" + +#: ./doc/glossary/glossary-terms.xml2889(glossterm) +msgid "netadmin" +msgstr "" + +#: ./doc/glossary/glossary-terms.xml2891(para) +msgid "" +"One of the default roles in the nova RBAC system. Enables the user to " +"allocate publicly accessible IP addresses to instances and change firewall " +"rules." +msgstr "" + +#: ./doc/glossary/glossary-terms.xml2898(glossterm) +msgid "NetApp volume driver" +msgstr "" + +#: ./doc/glossary/glossary-terms.xml2900(para) +msgid "" +"Enables nova to communicate with NetApp storage devices through the NetApp " +"OnCommand Provisioning Manager." +msgstr "" + +#: ./doc/glossary/glossary-terms.xml2906(glossterm) +msgid "network" +msgstr "" + +#: ./doc/glossary/glossary-terms.xml2908(para) +msgid "" +"A virtual network that provides connectivity between entities. For example, " +"a collection of virtual ports that share network connectivity. In neutron " +"terminology, a network is always a Layer-2 network." +msgstr "" + +#: ./doc/glossary/glossary-terms.xml2916(glossterm) +msgid "Network Address Translation (NAT)" +msgstr "" + +#: ./doc/glossary/glossary-terms.xml2918(para) +msgid "" +"The process of modifying IP address information while in-transit. Supported " +"by nova and neutron." +msgstr "" + +#: ./doc/glossary/glossary-terms.xml2924(glossterm) +msgid "network controller" +msgstr "" + +#: ./doc/glossary/glossary-terms.xml2926(para) +msgid "" +"A nova daemon that orchestrates the network configuration of nodes including" +" includes IP addresses, VLANs, bridging, and manages routing for both public" +" and private networks." +msgstr "" + +#: ./doc/glossary/glossary-terms.xml2933(glossterm) +msgid "Network File System (NFS)" +msgstr "" + +#: ./doc/glossary/glossary-terms.xml2935(para) +msgid "" +"A method for making file systems available over the network. Supported by " +"OpenStack." +msgstr "" + +#: ./doc/glossary/glossary-terms.xml2940(glossterm) +msgid "network ID" +msgstr "" + +#: ./doc/glossary/glossary-terms.xml2942(para) +msgid "" +"Unique ID assigned to each network segment within neutron. Same as network " +"UUID" +msgstr "" + +#: ./doc/glossary/glossary-terms.xml2947(glossterm) +msgid "network manager" +msgstr "" + +#: ./doc/glossary/glossary-terms.xml2949(para) +msgid "" +"The nova component that manages various network components, such as firewall" +" rules, IP address allocation, and so on." +msgstr "" + +#: ./doc/glossary/glossary-terms.xml2955(glossterm) +msgid "network node" +msgstr "" + +#: ./doc/glossary/glossary-terms.xml2957(para) +msgid "Any nova node that runs the network worker daemon." +msgstr "" + +#: ./doc/glossary/glossary-terms.xml2962(glossterm) +msgid "network segment" +msgstr "" + +#: ./doc/glossary/glossary-terms.xml2964(para) +msgid "Represents a virtual, isolated OSI layer 2 subnet in neutron." +msgstr "" + +#: ./doc/glossary/glossary-terms.xml2969(glossterm) +msgid "Network Time Protocol (NTP)" +msgstr "" + +#: ./doc/glossary/glossary-terms.xml2971(para) +msgid "" +"A method of keeping a clock for a host or node correct through " +"communications with a trusted, accurate time source." +msgstr "" + +#: ./doc/glossary/glossary-terms.xml2977(glossterm) +msgid "network UUID" +msgstr "" + +#: ./doc/glossary/glossary-terms.xml2979(para) +msgid "Unique ID for a neutron network segment." +msgstr "" + +#: ./doc/glossary/glossary-terms.xml2983(glossterm) +msgid "network worker" +msgstr "" + +#: ./doc/glossary/glossary-terms.xml2985(para) +msgid "" +"The nova-network worker daemon, provides services such as giving an IP " +"address to a booting nova instance." +msgstr "" + +#: ./doc/glossary/glossary-terms.xml2991(glossterm) +msgid "Neutron" +msgstr "" + +#: ./doc/glossary/glossary-terms.xml2993(para) +msgid "" +"A core OpenStack project that provides a network connectivity abstraction " +"layer to OpenStack Compute." +msgstr "" + +#: ./doc/glossary/glossary-terms.xml2999(glossterm) +msgid "neutron API" +msgstr "" + +#: ./doc/glossary/glossary-terms.xml3001(para) +msgid "" +"API used to access neutron. Provides an extensible architecture to enable " +"custom plug-in creation." +msgstr "" + +#: ./doc/glossary/glossary-terms.xml3007(glossterm) +msgid "neutron manager" +msgstr "" + +#: ./doc/glossary/glossary-terms.xml3009(para) +msgid "" +"Enables nova and neutron integration, which enables neutron to perform " +"network management for nova VMs." +msgstr "" + +#: ./doc/glossary/glossary-terms.xml3015(glossterm) +msgid "neutron plug-in" +msgstr "" + +#: ./doc/glossary/glossary-terms.xml3017(para) +msgid "" +"Interface within neutron that enables organizations to create custom plug-" +"ins for advanced features such as QoS, ACLs, or IDS." +msgstr "" + +#: ./doc/glossary/glossary-terms.xml3024(glossterm) +msgid "Nexenta volume driver" +msgstr "" + +#: ./doc/glossary/glossary-terms.xml3026(para) +msgid "Provides support for NexentaStor devices in nova." +msgstr "" + +#: ./doc/glossary/glossary-terms.xml3031(glossterm) +msgid "Nicira NVP neutron plug-in" +msgstr "" + +#: ./doc/glossary/glossary-terms.xml3033(para) +msgid "" +"Provides support for the Nicira Network Virtualization Platform (NVP) in " +"neutron." +msgstr "" + +#: ./doc/glossary/glossary-terms.xml3038(glossterm) +msgid "No ACK" +msgstr "" + +#: ./doc/glossary/glossary-terms.xml3040(para) +msgid "" +"Disables server-side message acknowledgment in the nova RabbitMQ. Increases " +"performance but decreases reliability." +msgstr "" + +#: ./doc/glossary/glossary-terms.xml3046(glossterm) +msgid "node" +msgstr "" + +#: ./doc/glossary/glossary-terms.xml3048(para) +msgid "A VM instance that runs on a host." +msgstr "" + +#: ./doc/glossary/glossary-terms.xml3052(glossterm) +msgid "non-durable exchange" +msgstr "" + +#: ./doc/glossary/glossary-terms.xml3054(para) +msgid "" +"Message exchange that is cleared when the service restarts. Its data is not " +"written to persistent storage." +msgstr "" + +#: ./doc/glossary/glossary-terms.xml3060(glossterm) +msgid "non-durable queue" +msgstr "" + +#: ./doc/glossary/glossary-terms.xml3062(para) +msgid "" +"Message queue that is cleared when the service restarts. Its data is not " +"written to persistent storage." +msgstr "" + +#: ./doc/glossary/glossary-terms.xml3068(glossterm) +msgid "non-persistent volume" +msgstr "" + +#: ./doc/glossary/glossary-terms.xml3070(para) +msgid "Alternative term for an ephemeral volume." +msgstr "" + +#: ./doc/glossary/glossary-terms.xml3074(glossterm) +msgid "nova" +msgstr "" + +#: ./doc/glossary/glossary-terms.xml3076(para) +msgid "OpenStack project that provides compute services." +msgstr "" + +#: ./doc/glossary/glossary-terms.xml3081(glossterm) +msgid "nova API" +msgstr "" + +#: ./doc/glossary/glossary-terms.xml3083(para) +msgid "Alternative term for the nova Compute API." +msgstr "" + +#: ./doc/glossary/glossary-terms.xml3088(glossterm) +msgid "nova network" +msgstr "" + +#: ./doc/glossary/glossary-terms.xml3090(para) +msgid "" +"A nova component that manages IP address allocation, firewalls, and other " +"network-related tasks." +msgstr "" + +#: ./doc/glossary/glossary-terms.xml3096(glossterm) +msgid "nova volume" +msgstr "" + +#: ./doc/glossary/glossary-terms.xml3098(para) +msgid "" +"The nova component that manages storage volumes, currently being split off " +"into a separate project named cinder." +msgstr "" + +#: ./doc/glossary/glossary-terms.xml3106(title) +msgid "O" +msgstr "" + +#: ./doc/glossary/glossary-terms.xml3108(glossterm) +msgid "object" +msgstr "" + +#: ./doc/glossary/glossary-terms.xml3110(para) +msgid "A BLOB of data held by swift, can be in any format." +msgstr "" + +#: ./doc/glossary/glossary-terms.xml3115(glossterm) +msgid "Object API" +msgstr "" + +#: ./doc/glossary/glossary-terms.xml3117(para) +#: ./doc/glossary/glossary-terms.xml3169(para) +msgid "Alternative term for the swift object API." +msgstr "" + +#: ./doc/glossary/glossary-terms.xml3122(glossterm) +msgid "object auditor" +msgstr "" + +#: ./doc/glossary/glossary-terms.xml3124(para) +msgid "" +"Opens all objects for an object server and verifies the MD5 hash, size, and " +"metadata for each object." +msgstr "" + +#: ./doc/glossary/glossary-terms.xml3130(glossterm) +msgid "object expiration" +msgstr "" + +#: ./doc/glossary/glossary-terms.xml3132(para) +msgid "" +"A configurable option within swift to automatically delete objects after a " +"specified amount of time has passed or a certain date is reached." +msgstr "" + +#: ./doc/glossary/glossary-terms.xml3139(glossterm) +msgid "object hash" +msgstr "" + +#: ./doc/glossary/glossary-terms.xml3141(para) +msgid "Uniquely ID for a swift object." +msgstr "" + +#: ./doc/glossary/glossary-terms.xml3145(glossterm) +msgid "object path hash" +msgstr "" + +#: ./doc/glossary/glossary-terms.xml3147(para) +msgid "" +"Used by swift to determine the location of an object in the ring. Maps " +"objects to partitions." +msgstr "" + +#: ./doc/glossary/glossary-terms.xml3153(glossterm) +msgid "object replicator" +msgstr "" + +#: ./doc/glossary/glossary-terms.xml3155(para) +msgid "" +"A swift component that copies and object to remote partitions for fault " +"tolerance." +msgstr "" + +#: ./doc/glossary/glossary-terms.xml3160(glossterm) +msgid "object server" +msgstr "" + +#: ./doc/glossary/glossary-terms.xml3162(para) +msgid "A swift component that is responsible for managing objects." +msgstr "" + +#: ./doc/glossary/glossary-terms.xml3167(glossterm) +msgid "Object Service API" +msgstr "" + +#: ./doc/glossary/glossary-terms.xml3174(glossterm) +msgid "object storage" +msgstr "" + +#: ./doc/glossary/glossary-terms.xml3176(para) +msgid "" +"Provides eventually consistent and redundant storage and retrieval of fixed " +"digital content." +msgstr "" + +#: ./doc/glossary/glossary-terms.xml3182(glossterm) +msgid "Object Storage Device (OSD)" +msgstr "" + +#: ./doc/glossary/glossary-terms.xml3184(para) +msgid "The Ceph storage daemon." +msgstr "" + +#: ./doc/glossary/glossary-terms.xml3188(glossterm) +msgid "object versioning" +msgstr "" + +#: ./doc/glossary/glossary-terms.xml3190(para) +msgid "" +"Allows a user to set a flag on a swift container so all objects within the " +"container are versioned." +msgstr "" + +#: ./doc/glossary/glossary-terms.xml3196(glossterm) +msgid "Oldie" +msgstr "" + +#: ./doc/glossary/glossary-terms.xml3198(para) +msgid "" +"Term for a swift process that runs for a long time. Can indicate a hung " +"process." +msgstr "" + +#: ./doc/glossary/glossary-terms.xml3204(glossterm) +msgid "Open Cloud Computing Interface (OCCI)" +msgstr "" + +#: ./doc/glossary/glossary-terms.xml3207(para) +msgid "" +"A standardized interface for managing compute, data, and network resources, " +"currently unsupported in OpenStack." +msgstr "" + +#: ./doc/glossary/glossary-terms.xml3213(glossterm) +msgid "Open Virtualization Format (OVF)" +msgstr "" + +#: ./doc/glossary/glossary-terms.xml3215(para) +msgid "Standard for packaging VM images. Supported in OpenStack." +msgstr "" + +#: ./doc/glossary/glossary-terms.xml3220(glossterm) +msgid "Open vSwitch neutron plug-in" +msgstr "" + +#: ./doc/glossary/glossary-terms.xml3222(para) +msgid "Provides support for Open vSwitch in neutron." +msgstr "" + +#: ./doc/glossary/glossary-terms.xml3227(glossterm) +msgid "OpenLDAP" +msgstr "" + +#: ./doc/glossary/glossary-terms.xml3229(para) +msgid "An open source LDAP server. Supported by both nova and keystone." +msgstr "" + +#: ./doc/glossary/glossary-terms.xml3234(glossterm) +msgid "OpenStack API (OSAPI)" +msgstr "" + +#: ./doc/glossary/glossary-terms.xml3236(para) +msgid "The core OpenStack API." +msgstr "" + +#: ./doc/glossary/glossary-terms.xml3240(glossterm) +msgid "openSUSE" +msgstr "" + +#: ./doc/glossary/glossary-terms.xml3247(glossterm) +msgid "operator" +msgstr "" + +#: ./doc/glossary/glossary-terms.xml3249(para) +msgid "" +"The person responsible for planning and maintaining an OpenStack " +"installation." +msgstr "" + +#: ./doc/glossary/glossary-terms.xml3254(glossterm) +msgid "orphan" +msgstr "" + +#: ./doc/glossary/glossary-terms.xml3256(para) +msgid "" +"In the context of swift this is a process that is not terminated after an " +"upgrade, restart, or reload of the service." +msgstr "" + +#: ./doc/glossary/glossary-terms.xml3264(title) +msgid "P" +msgstr "" + +#: ./doc/glossary/glossary-terms.xml3266(glossterm) +msgid "parent cell" +msgstr "" + +#: ./doc/glossary/glossary-terms.xml3268(para) +msgid "" +"If a requested resource, such as CPU time, disk storage, or memory, is not " +"available in the parent cell, the request is forwarded to associated child " +"cells." +msgstr "" + +#: ./doc/glossary/glossary-terms.xml3275(glossterm) +msgid "partition" +msgstr "" + +#: ./doc/glossary/glossary-terms.xml3277(para) +msgid "" +"A unit of storage within swift used to store objects, exists on top of " +"devices, replicated for fault tolerance." +msgstr "" + +#: ./doc/glossary/glossary-terms.xml3283(glossterm) +msgid "partition index" +msgstr "" + +#: ./doc/glossary/glossary-terms.xml3285(para) +msgid "Contains the locations of all swift partitions within the ring." +msgstr "" + +#: ./doc/glossary/glossary-terms.xml3290(glossterm) +msgid "partition shift value" +msgstr "" + +#: ./doc/glossary/glossary-terms.xml3292(para) +msgid "Used by swift to determine which partition data should reside on." +msgstr "" + +#: ./doc/glossary/glossary-terms.xml3297(glossterm) +msgid "pause" +msgstr "" + +#: ./doc/glossary/glossary-terms.xml3299(para) +msgid "" +"A VM state where no changes occur (no changes in memory, network " +"communications stop, etc), the VM is frozen but not shut down." +msgstr "" + +#: ./doc/glossary/glossary-terms.xml3305(glossterm) +msgid "PCI passthrough" +msgstr "" + +#: ./doc/glossary/glossary-terms.xml3307(para) +msgid "" +"Gives guest VMs exclusive access to a PCI device. Currently supported in " +"OpenStack Havana and later releases." +msgstr "" + +#: ./doc/glossary/glossary-terms.xml3313(glossterm) +msgid "persistent message" +msgstr "" + +#: ./doc/glossary/glossary-terms.xml3315(para) +msgid "" +"A message that is stored both in memory and on disk, the message is not lost" +" after a failure or restart." +msgstr "" + +#: ./doc/glossary/glossary-terms.xml3321(glossterm) +msgid "persistent volume" +msgstr "" + +#: ./doc/glossary/glossary-terms.xml3323(para) +msgid "Changes to these types of disk volumes are saved." +msgstr "" + +#: ./doc/glossary/glossary-terms.xml3328(glossterm) +msgid "personality file" +msgstr "" + +#: ./doc/glossary/glossary-terms.xml3330(para) +msgid "" +"A file used to customize a nova instance, can be used to inject SSH keys or " +"a specific network configuration." +msgstr "" + +#: ./doc/glossary/glossary-terms.xml3336(glossterm) +msgid "plug-in" +msgstr "" + +#: ./doc/glossary/glossary-terms.xml3338(para) +msgid "" +"Software component providing the actual implementation for neutron APIs, or " +"for Compute APIs, depending on the context." +msgstr "" + +#: ./doc/glossary/glossary-terms.xml3344(glossterm) +msgid "policy service" +msgstr "" + +#: ./doc/glossary/glossary-terms.xml3346(para) +msgid "" +"Component of keystone that provides a rule management interface and a rule " +"based authorization engine." +msgstr "" + +#: ./doc/glossary/glossary-terms.xml3352(glossterm) +msgid "port" +msgstr "" + +#: ./doc/glossary/glossary-terms.xml3354(para) +msgid "" +"A virtual network port within neutron, VIFs / vNICs are connected to a port." +msgstr "" + +#: ./doc/glossary/glossary-terms.xml3359(glossterm) +msgid "port UUID" +msgstr "" + +#: ./doc/glossary/glossary-terms.xml3361(para) +msgid "Unique ID for a neutron port." +msgstr "" + +#: ./doc/glossary/glossary-terms.xml3365(glossterm) +msgid "preseed" +msgstr "" + +#: ./doc/glossary/glossary-terms.xml3367(para) +msgid "" +"A tool to automate system configuration and installation on Debian-based " +"Linux distributions." +msgstr "" + +#: ./doc/glossary/glossary-terms.xml3373(glossterm) +msgid "private image" +msgstr "" + +#: ./doc/glossary/glossary-terms.xml3375(para) +msgid "A glance VM image that is only available to specified tenants." +msgstr "" + +#: ./doc/glossary/glossary-terms.xml3380(glossterm) +msgid "private IP address" +msgstr "" + +#: ./doc/glossary/glossary-terms.xml3382(para) +msgid "" +"An IP address used for management and administration, not available to the " +"public internet." +msgstr "" + +#: ./doc/glossary/glossary-terms.xml3388(glossterm) +msgid "private network" +msgstr "" + +#: ./doc/glossary/glossary-terms.xml3390(para) +msgid "" +"The Network Controller provides virtual networks to enable compute servers " +"to interact with each other and with the public network. All machines must " +"have a public and private network interface. A private network interface can" +" be a flat or VLAN network interface. A flat network interface is controlled" +" by the flat_interface with flat managers. A VLAN network interface is " +"controlled by the vlan_interface option with VLAN managers." +msgstr "" + +#: ./doc/glossary/glossary-terms.xml3403(glossterm) +msgid "project" +msgstr "" + +#: ./doc/glossary/glossary-terms.xml3405(para) +msgid "" +"A logical grouping of users within nova, used to define quotas and access to" +" VM images." +msgstr "" + +#: ./doc/glossary/glossary-terms.xml3410(glossterm) +msgid "project ID" +msgstr "" + +#: ./doc/glossary/glossary-terms.xml3412(para) +msgid "User defined alpha-numeric string in nova, the name of a project." +msgstr "" + +#: ./doc/glossary/glossary-terms.xml3417(glossterm) +msgid "project VPN" +msgstr "" + +#: ./doc/glossary/glossary-terms.xml3419(para) +msgid "Alternative term for a cloudpipe." +msgstr "" + +#: ./doc/glossary/glossary-terms.xml3423(glossterm) +msgid "provider" +msgstr "" + +#: ./doc/glossary/glossary-terms.xml3425(para) +msgid "An administrator who has access to all hosts and instances." +msgstr "" + +#: ./doc/glossary/glossary-terms.xml3430(glossterm) +msgid "proxy node" +msgstr "" + +#: ./doc/glossary/glossary-terms.xml3432(para) +msgid "A node that provides the swift proxy service." +msgstr "" + +#: ./doc/glossary/glossary-terms.xml3437(glossterm) +msgid "proxy server" +msgstr "" + +#: ./doc/glossary/glossary-terms.xml3439(para) +msgid "" +"Users of swift interact with the service through the proxy server which in-" +"turn looks up the location of the requested data within the ring and returns" +" the results to the user." +msgstr "" + +#: ./doc/glossary/glossary-terms.xml3446(glossterm) +msgid "public API" +msgstr "" + +#: ./doc/glossary/glossary-terms.xml3448(para) +msgid "" +"An API endpoint used for both service to service communication and end user " +"interactions." +msgstr "" + +#: ./doc/glossary/glossary-terms.xml3453(glossterm) +msgid "public image" +msgstr "" + +#: ./doc/glossary/glossary-terms.xml3455(para) +msgid "A glance VM image that is available to all tenants." +msgstr "" + +#: ./doc/glossary/glossary-terms.xml3460(glossterm) +msgid "public IP address" +msgstr "" + +#: ./doc/glossary/glossary-terms.xml3462(para) +msgid "An IP address that is accessible to end-users." +msgstr "" + +#: ./doc/glossary/glossary-terms.xml3467(glossterm) +msgid "public network" +msgstr "" + +#: ./doc/glossary/glossary-terms.xml3469(para) +msgid "" +"The Network Controller provides virtual networks to enable compute servers " +"to interact with each other and with the public network. All machines must " +"have a public and private network interface. The public network interface is" +" controlled by the public_interface option." +msgstr "" + +#: ./doc/glossary/glossary-terms.xml3478(glossterm) +msgid "Puppet" +msgstr "" + +#: ./doc/glossary/glossary-terms.xml3480(para) +msgid "" +"An operating system configuration management tool supported by OpenStack." +msgstr "" + +#: ./doc/glossary/glossary-terms.xml3485(glossterm) +msgid "Python" +msgstr "" + +#: ./doc/glossary/glossary-terms.xml3487(para) +msgid "Programming language used extensively in OpenStack." +msgstr "" + +#: ./doc/glossary/glossary-terms.xml3494(title) +msgid "Q" +msgstr "" + +#: ./doc/glossary/glossary-terms.xml3496(glossterm) +msgid "QEMU Copy On Write 2 (QCOW2)" +msgstr "" + +#: ./doc/glossary/glossary-terms.xml3503(glossterm) +msgid "Qpid" +msgstr "" + +#: ./doc/glossary/glossary-terms.xml3505(para) +msgid "" +"Message queue software supported by OpenStack, an alternative to RabbitMQ." +msgstr "" + +#: ./doc/glossary/glossary-terms.xml3510(glossterm) +msgid "quarantine" +msgstr "" + +#: ./doc/glossary/glossary-terms.xml3512(para) +msgid "" +"If swift finds objects, containers, or accounts that are corrupt they are " +"placed in this state, are not replicated, cannot be read by clients, and a " +"correct copy is re-replicated." +msgstr "" + +#: ./doc/glossary/glossary-terms.xml3519(glossterm) +msgid "Quick EMUlator (QEMU)" +msgstr "" + +#: ./doc/glossary/glossary-terms.xml3521(para) +msgid "QEMU is a generic and open source machine emulator and virtualizer." +msgstr "" + +#: ./doc/glossary/glossary-terms.xml3523(para) +msgid "" +"One of the hypervisors supported by OpenStack, generally used for " +"development purposes." +msgstr "" + +#: ./doc/glossary/glossary-terms.xml3528(glossterm) +msgid "quota" +msgstr "" + +#: ./doc/glossary/glossary-terms.xml3530(para) +msgid "In nova, the ability to set resource limits on a per-project basis." +msgstr "" + +#: ./doc/glossary/glossary-terms.xml3537(title) +msgid "R" +msgstr "" + +#: ./doc/glossary/glossary-terms.xml3539(glossterm) +msgid "RabbitMQ" +msgstr "" + +#: ./doc/glossary/glossary-terms.xml3541(para) +msgid "The default message queue software used by OpenStack." +msgstr "" + +#: ./doc/glossary/glossary-terms.xml3546(glossterm) +msgid "Rackspace Cloud Files" +msgstr "" + +#: ./doc/glossary/glossary-terms.xml3548(para) +msgid "Released as open source by Rackspace in 2010, the basis for swift." +msgstr "" + +#: ./doc/glossary/glossary-terms.xml3553(glossterm) +msgid "RADOS Block Device (RBD)" +msgstr "" + +#: ./doc/glossary/glossary-terms.xml3555(para) +msgid "" +"Ceph component that enables a Linux block device to be striped over multiple" +" distributed data stores." +msgstr "" + +#: ./doc/glossary/glossary-terms.xml3561(glossterm) +msgid "radvd" +msgstr "" + +#: ./doc/glossary/glossary-terms.xml3563(para) +msgid "" +"The router advertisement daemon, used by the nova VLAN manager and FlatDHCP " +"manager to provide routing services for VM instances." +msgstr "" + +#: ./doc/glossary/glossary-terms.xml3569(glossterm) +msgid "RAM filter" +msgstr "" + +#: ./doc/glossary/glossary-terms.xml3571(para) +msgid "The nova setting that enables or disables RAM overcommitment." +msgstr "" + +#: ./doc/glossary/glossary-terms.xml3576(glossterm) +msgid "RAM overcommit" +msgstr "" + +#: ./doc/glossary/glossary-terms.xml3578(para) +msgid "" +"The ability to start new VM instances based on the actual memory usage of a " +"host, as opposed to basing the decision on the amount of RAM each running " +"instance thinks it has available. Also known as memory overcommit." +msgstr "" + +#: ./doc/glossary/glossary-terms.xml3586(glossterm) +msgid "rate limit" +msgstr "" + +#: ./doc/glossary/glossary-terms.xml3588(para) +msgid "" +"Configurable option within swift to limit database writes on a per-account " +"and/or per-container basis." +msgstr "" + +#: ./doc/glossary/glossary-terms.xml3594(glossterm) +msgid "raw" +msgstr "" + +#: ./doc/glossary/glossary-terms.xml3596(para) +msgid "" +"One of the VM image disk formats supported by glance, an unstructured disk " +"image." +msgstr "" + +#: ./doc/glossary/glossary-terms.xml3601(glossterm) +msgid "rebalance" +msgstr "" + +#: ./doc/glossary/glossary-terms.xml3603(para) +msgid "" +"The process of distributing swift partitions across all drives in the ring, " +"used during initial ring creation and after ring reconfiguration." +msgstr "" + +#: ./doc/glossary/glossary-terms.xml3610(glossterm) +msgid "reboot" +msgstr "" + +#: ./doc/glossary/glossary-terms.xml3612(para) +msgid "" +"Either a soft or hard reboot of a server. With a soft reboot, the operating " +"system is signaled to restart, which enables a graceful shutdown of all " +"processes. A hard reboot is the equivalent of power cycling the server. The " +"virtualization platform should ensure that the reboot action has completed " +"successfully even in cases in which the underlying domain/vm is paused or " +"halted/stopped." +msgstr "" + +#: ./doc/glossary/glossary-terms.xml3624(glossterm) +msgid "rebuild" +msgstr "" + +#: ./doc/glossary/glossary-terms.xml3626(para) +msgid "" +"Removes all data on the server and replaces it with the specified image. " +"Server ID and IP addresses remain the same." +msgstr "" + +#: ./doc/glossary/glossary-terms.xml3632(glossterm) +msgid "Recon" +msgstr "" + +#: ./doc/glossary/glossary-terms.xml3634(para) +msgid "A swift component that collects metrics." +msgstr "" + +#: ./doc/glossary/glossary-terms.xml3638(glossterm) +msgid "record" +msgstr "" + +#: ./doc/glossary/glossary-terms.xml3640(para) +msgid "" +"Belongs to a particular domain and is used to specify information about the " +"domain. There are several types of DNS records. Each record type contains " +"particular information used to describe the purpose of that record. Examples" +" include mail exchange (MX) records, which specify the mail server for a " +"particular domain, and name server (NS) records, which specify the " +"authoritative name servers for a domain." +msgstr "" + +#: ./doc/glossary/glossary-terms.xml3652(glossterm) +msgid "record ID" +msgstr "" + +#: ./doc/glossary/glossary-terms.xml3654(para) +msgid "" +"A number within a database that is incremented each time a change is made. " +"Used by swift when replicating." +msgstr "" + +#: ./doc/glossary/glossary-terms.xml3660(glossterm) +msgid "Red Dwarf Lite" +msgstr "" + +#: ./doc/glossary/glossary-terms.xml3662(para) +msgid "Community project that aims to provide database as a service." +msgstr "" + +#: ./doc/glossary/glossary-terms.xml3667(glossterm) +msgid "Red Hat Enterprise Linux (RHEL)" +msgstr "" + +#: ./doc/glossary/glossary-terms.xml3674(glossterm) +msgid "reference architecture" +msgstr "" + +#: ./doc/glossary/glossary-terms.xml3676(para) +msgid "A recommended architecture for an OpenStack cloud." +msgstr "" + +#: ./doc/glossary/glossary-terms.xml3681(glossterm) +msgid "region" +msgstr "" + +#: ./doc/glossary/glossary-terms.xml3683(para) +msgid "" +"A Discrete OpenStack environment with dedicated API endpoints that typically" +" shares only the Identity Service (keystone) with other regions." +msgstr "" + +#: ./doc/glossary/glossary-terms.xml3689(glossterm) +msgid "registry" +msgstr "" + +#: ./doc/glossary/glossary-terms.xml3696(glossterm) +msgid "registry server" +msgstr "" + +#: ./doc/glossary/glossary-terms.xml3698(para) +msgid "" +"A glance service that provides VM image metadata information to clients." +msgstr "" + +#: ./doc/glossary/glossary-terms.xml3703(glossterm) +msgid "Reliable, Autonomic Distributed Object Store (RADOS)" +msgstr "" + +#: ./doc/glossary/glossary-terms.xml3706(para) +msgid "" +"A collection of components that provides object storage within Ceph. Similar" +" to swift." +msgstr "" + +#: ./doc/glossary/glossary-terms.xml3711(glossterm) +msgid "Remote Procedure Call (RPC)" +msgstr "" + +#: ./doc/glossary/glossary-terms.xml3713(para) +msgid "The method used by the nova RabbitMQ for intra-service communications." +msgstr "" + +#: ./doc/glossary/glossary-terms.xml3718(glossterm) +msgid "replica" +msgstr "" + +#: ./doc/glossary/glossary-terms.xml3720(para) +msgid "" +"Provides data redundancy and fault tolerance by creating copies of swift " +"objects, accounts, and containers so they are not lost when the underlying " +"storage fails." +msgstr "" + +#: ./doc/glossary/glossary-terms.xml3727(glossterm) +msgid "replica count" +msgstr "" + +#: ./doc/glossary/glossary-terms.xml3729(para) +msgid "The number of replicas of the data in a swift ring." +msgstr "" + +#: ./doc/glossary/glossary-terms.xml3734(glossterm) +msgid "replication" +msgstr "" + +#: ./doc/glossary/glossary-terms.xml3736(para) +msgid "" +"The process of copying data to a separate physical device for fault " +"tolerance and performance." +msgstr "" + +#: ./doc/glossary/glossary-terms.xml3742(glossterm) +msgid "replicator" +msgstr "" + +#: ./doc/glossary/glossary-terms.xml3744(para) +msgid "The swift back-end process that creates and manages object replicas." +msgstr "" + +#: ./doc/glossary/glossary-terms.xml3749(glossterm) +msgid "request ID" +msgstr "" + +#: ./doc/glossary/glossary-terms.xml3751(para) +msgid "Unique ID assigned to each request sent to nova." +msgstr "" + +#: ./doc/glossary/glossary-terms.xml3756(glossterm) +msgid "rescue image" +msgstr "" + +#: ./doc/glossary/glossary-terms.xml3758(para) +msgid "" +"A special type of VM image that is booted when an instance is placed into " +"rescue mode. Allows an administrator to mount the file systems for an " +"instance to correct the problem." +msgstr "" + +#: ./doc/glossary/glossary-terms.xml3765(glossterm) +msgid "resize" +msgstr "" + +#: ./doc/glossary/glossary-terms.xml3767(para) +msgid "" +"Converts an existing server to a different flavor, which scales the server " +"up or down. The original server is saved to enable rollback if a problem " +"occurs. All resizes must be tested and explicitly confirmed, at which time " +"the original server is removed." +msgstr "" + +#: ./doc/glossary/glossary-terms.xml3776(glossterm) +msgid "RESTful" +msgstr "" + +#: ./doc/glossary/glossary-terms.xml3778(para) +msgid "" +"A kind of web service API that uses REST, or Representational State " +"Transfer. REST is the style of architecture for hypermedia systems that is " +"used for the World Wide Web." +msgstr "" + +#: ./doc/glossary/glossary-terms.xml3785(glossterm) +msgid "ring" +msgstr "" + +#: ./doc/glossary/glossary-terms.xml3787(para) +msgid "" +"An entity that maps swift data to partitions. A separate ring exists for " +"each service, such as account, object, and container." +msgstr "" + +#: ./doc/glossary/glossary-terms.xml3793(glossterm) +msgid "ring builder" +msgstr "" + +#: ./doc/glossary/glossary-terms.xml3795(para) +msgid "" +"Builds and manages rings within swift, assigns partitions to devices, and " +"pushes the configuration to other storage nodes." +msgstr "" + +#: ./doc/glossary/glossary-terms.xml3801(glossterm) +msgid "Role Based Access Control (RBAC)" +msgstr "" + +#: ./doc/glossary/glossary-terms.xml3803(para) +msgid "" +"Provides a predefined list of actions that the user can perform such as " +"start or stop VMs, reset passwords, and so on. Supported in both keystone " +"and nova and can be configured using the horizon dashboard." +msgstr "" + +#: ./doc/glossary/glossary-terms.xml3811(glossterm) +msgid "role ID" +msgstr "" + +#: ./doc/glossary/glossary-terms.xml3813(para) +msgid "Alpha-numeric ID assigned to each keystone role." +msgstr "" + +#: ./doc/glossary/glossary-terms.xml3818(glossterm) +msgid "rootwrap" +msgstr "" + +#: ./doc/glossary/glossary-terms.xml3820(para) +msgid "" +"A feature of nova that allows the unprivileged \"nova\" user to run a " +"specified list of commands as the Linux root user." +msgstr "" + +#: ./doc/glossary/glossary-terms.xml3826(glossterm) +msgid "round-robin scheduler" +msgstr "" + +#: ./doc/glossary/glossary-terms.xml3828(para) +msgid "" +"Type of nova scheduler that evenly distributes instances among available " +"hosts." +msgstr "" + +#: ./doc/glossary/glossary-terms.xml3833(glossterm) +msgid "routing key" +msgstr "" + +#: ./doc/glossary/glossary-terms.xml3835(para) +msgid "" +"the nova direct exchanges, fanout exchanges, and topic exchanges use this to" +" determine how to process a message, processing varies depending on exchange" +" type." +msgstr "" + +#: ./doc/glossary/glossary-terms.xml3842(glossterm) +msgid "RPC driver" +msgstr "" + +#: ./doc/glossary/glossary-terms.xml3844(para) +msgid "" +"Modular system that allows the nova underlying message queue software to be " +"changed. For example, from RabbitMQ to ZeroMQ or Qpid." +msgstr "" + +#: ./doc/glossary/glossary-terms.xml3850(glossterm) +msgid "rsync" +msgstr "" + +#: ./doc/glossary/glossary-terms.xml3852(para) +msgid "Used by swift to push object replicas." +msgstr "" + +#: ./doc/glossary/glossary-terms.xml3856(glossterm) +msgid "RXTX cap" +msgstr "" + +#: ./doc/glossary/glossary-terms.xml3858(para) +msgid "" +"Absolute limit on the amount of network traffic a nova VM instance can send " +"and receive." +msgstr "" + +#: ./doc/glossary/glossary-terms.xml3863(glossterm) +msgid "RXTX quota" +msgstr "" + +#: ./doc/glossary/glossary-terms.xml3865(para) +msgid "" +"Soft limit on the amount of network traffic a nova VM instance can send and " +"receive." +msgstr "" + +#: ./doc/glossary/glossary-terms.xml3870(glossterm) +msgid "Ryu neutron plug-in" +msgstr "" + +#: ./doc/glossary/glossary-terms.xml3872(para) +msgid "" +"Enables the Ryu network operating system to function as a neutron OpenFlow " +"controller." +msgstr "" + +#: ./doc/glossary/glossary-terms.xml3879(title) +msgid "S" +msgstr "" + +#: ./doc/glossary/glossary-terms.xml3881(glossterm) +msgid "S3" +msgstr "" + +#: ./doc/glossary/glossary-terms.xml3883(para) +msgid "" +"Object storage service by Amazon, similar in function to swift, can act as a" +" back-end store for glance VM images." +msgstr "" + +#: ./doc/glossary/glossary-terms.xml3889(glossterm) +msgid "Savanna" +msgstr "" + +#: ./doc/glossary/glossary-terms.xml3891(para) +msgid "" +"OpenStack project that provisions Hadoop on top of OpenStack to provide a " +"data processing service." +msgstr "" + +#: ./doc/glossary/glossary-terms.xml3897(glossterm) +msgid "scheduler manager" +msgstr "" + +#: ./doc/glossary/glossary-terms.xml3899(para) +msgid "" +"A nova component that determines where VM instances should start. Uses " +"modular design to support a variety of scheduler types." +msgstr "" + +#: ./doc/glossary/glossary-terms.xml3905(glossterm) +msgid "scoped token" +msgstr "" + +#: ./doc/glossary/glossary-terms.xml3907(para) +msgid "A keystone API access token that is associated with a specific tenant." +msgstr "" + +#: ./doc/glossary/glossary-terms.xml3912(glossterm) +msgid "scrubber" +msgstr "" + +#: ./doc/glossary/glossary-terms.xml3914(para) +msgid "" +"Checks for and deletes unused VM, the component of glance that implements " +"delayed delete." +msgstr "" + +#: ./doc/glossary/glossary-terms.xml3919(glossterm) +msgid "secret key" +msgstr "" + +#: ./doc/glossary/glossary-terms.xml3921(para) +msgid "" +"String of text only known by the user, used along with an access key to make" +" requests to the nova API." +msgstr "" + +#: ./doc/glossary/glossary-terms.xml3927(glossterm) +msgid "secure shell (SSH)" +msgstr "" + +#: ./doc/glossary/glossary-terms.xml3929(para) +msgid "" +"Open source tool used to access remote hosts through an encrypted " +"communications channel, SSH key injection is supported by nova." +msgstr "" + +#: ./doc/glossary/glossary-terms.xml3935(glossterm) +msgid "security group" +msgstr "" + +#: ./doc/glossary/glossary-terms.xml3937(para) +msgid "" +"A set of network traffic filtering rules that are applied to a nova " +"instance." +msgstr "" + +#: ./doc/glossary/glossary-terms.xml3942(glossterm) +msgid "segmented object" +msgstr "" + +#: ./doc/glossary/glossary-terms.xml3944(para) +msgid "" +"A swift large object that has been broken up into pieces, the re-assembled " +"object is called a concatenated object." +msgstr "" + +#: ./doc/glossary/glossary-terms.xml3950(glossterm) +msgid "server" +msgstr "" + +#: ./doc/glossary/glossary-terms.xml3952(para) +msgid "" +"Computer that provides explicit services to the client software running on " +"that system, often managing a variety of computer operations." +msgstr "" + +#: ./doc/glossary/glossary-terms.xml3955(para) +msgid "" +"A server is a VM instance in the compute system. Flavor and image are " +"requisite elements when creating a server." +msgstr "" + +#: ./doc/glossary/glossary-terms.xml3961(glossterm) +msgid "server image" +msgstr "" + +#: ./doc/glossary/glossary-terms.xml3963(para) +msgid "Alternative term for a VM image." +msgstr "" + +#: ./doc/glossary/glossary-terms.xml3967(glossterm) +msgid "server UUID" +msgstr "" + +#: ./doc/glossary/glossary-terms.xml3974(glossterm) +msgid "service catalog" +msgstr "" + +#: ./doc/glossary/glossary-terms.xml3976(para) +msgid "Alternative term for the keystone catalog." +msgstr "" + +#: ./doc/glossary/glossary-terms.xml3981(glossterm) +msgid "service ID" +msgstr "" + +#: ./doc/glossary/glossary-terms.xml3983(para) +msgid "" +"Unique ID assigned to each service that is available in the keystone " +"catalog." +msgstr "" + +#: ./doc/glossary/glossary-terms.xml3988(glossterm) +msgid "service registration" +msgstr "" + +#: ./doc/glossary/glossary-terms.xml3990(para) +msgid "" +"A keystone feature that enables services, such as nova, to automatically " +"register with the catalog." +msgstr "" + +#: ./doc/glossary/glossary-terms.xml3995(glossterm) +msgid "service tenant" +msgstr "" + +#: ./doc/glossary/glossary-terms.xml3997(para) +msgid "" +"Special keystone tenant that contains all services that are listed in the " +"catalog." +msgstr "" + +#: ./doc/glossary/glossary-terms.xml4002(glossterm) +msgid "service token" +msgstr "" + +#: ./doc/glossary/glossary-terms.xml4004(para) +msgid "" +"An administrator defined token used by nova to communicate securely with " +"keystone." +msgstr "" + +#: ./doc/glossary/glossary-terms.xml4009(glossterm) +msgid "session back-end" +msgstr "" + +#: ./doc/glossary/glossary-terms.xml4011(para) +msgid "" +"The method of storage used by horizon to track client sessions such as local" +" memory, cookies, a database, or memcached." +msgstr "" + +#: ./doc/glossary/glossary-terms.xml4017(glossterm) +msgid "session persistence" +msgstr "" + +#: ./doc/glossary/glossary-terms.xml4019(para) +msgid "" +"A feature of the load balancing service. It attempts to force subsequent " +"connections to a service to be redirected to the same node as long as it is " +"online." +msgstr "" + +#: ./doc/glossary/glossary-terms.xml4026(glossterm) +msgid "session storage" +msgstr "" + +#: ./doc/glossary/glossary-terms.xml4028(para) +msgid "" +"A horizon component that stores and tracks client session information. " +"Implemented through the Django sessions framework." +msgstr "" + +#: ./doc/glossary/glossary-terms.xml4034(glossterm) +msgid "shared IP address" +msgstr "" + +#: ./doc/glossary/glossary-terms.xml4036(para) +msgid "" +"An IP address that can be assigned to a VM instance within the shared IP " +"group. Public IP addresses can be shared across multiple servers for use in " +"various high availability scenarios. When an IP address is shared to another" +" server, the cloud network restrictions are modified to enable each server " +"to listen to and respond on that IP address. You can optionally specify that" +" the target server network configuration be modified. Shared IP addresses " +"can be used with many standard heartbeat facilities, such as keepalive, that" +" monitor for failure and manage IP failover." +msgstr "" + +#: ./doc/glossary/glossary-terms.xml4052(glossterm) +msgid "shared IP group" +msgstr "" + +#: ./doc/glossary/glossary-terms.xml4054(para) +msgid "" +"A collection of servers that can share IPs with other members of the group. " +"Any server in a group can share one or more public IPs with any other server" +" in the group. With the exception of the first server in a shared IP group, " +"servers must be launched into shared IP groups. A server may only be a " +"member of one shared IP group." +msgstr "" + +#: ./doc/glossary/glossary-terms.xml4064(glossterm) +msgid "shared storage" +msgstr "" + +#: ./doc/glossary/glossary-terms.xml4066(para) +msgid "" +"Block storage that is simultaneously accessible by multiple clients. For " +"example, NFS." +msgstr "" + +#: ./doc/glossary/glossary-terms.xml4071(glossterm) +msgid "Sheepdog" +msgstr "" + +#: ./doc/glossary/glossary-terms.xml4073(para) +msgid "Distributed block storage system for QEMU, supported by OpenStack." +msgstr "" + +#: ./doc/glossary/glossary-terms.xml4078(glossterm) +msgid "Simple Cloud Identity Management (SCIM)" +msgstr "" + +#: ./doc/glossary/glossary-terms.xml4081(para) +msgid "" +"Specification for managing identity in the cloud, currently unsupported by " +"OpenStack." +msgstr "" + +#: ./doc/glossary/glossary-terms.xml4086(glossterm) +msgid "Single-root I/O Virtualization (SR-IOV)" +msgstr "" + +#: ./doc/glossary/glossary-terms.xml4089(para) +msgid "" +"A specification that when implemented by a physical PCIe device enables it " +"to appear as multiple separate PCIe devices. This enables multiple " +"virtualized guests to share direct access to the physical device, offering " +"improved performance over an equivalent virtual device. Currently supported " +"in OpenStack Havana and later releases." +msgstr "" + +#: ./doc/glossary/glossary-terms.xml4099(glossterm) +msgid "SmokeStack" +msgstr "" + +#: ./doc/glossary/glossary-terms.xml4101(para) +msgid "Runs automated tests against the core OpenStack API, written in Rails." +msgstr "" + +#: ./doc/glossary/glossary-terms.xml4106(glossterm) +msgid "snapshot" +msgstr "" + +#: ./doc/glossary/glossary-terms.xml4108(para) +msgid "" +"A point-in-time copy of an OpenStack storage volume or image. Use storage " +"volume snapshots to back up volumes. Use image snapshots to back up data, or" +" as \"gold\" images for additional servers." +msgstr "" + +#: ./doc/glossary/glossary-terms.xml4116(glossterm) +msgid "soft reboot" +msgstr "" + +#: ./doc/glossary/glossary-terms.xml4118(para) +msgid "" +"A controlled reboot where a VM instance is properly restarted through " +"operating system commands." +msgstr "" + +#: ./doc/glossary/glossary-terms.xml4124(glossterm) +msgid "SolidFire Volume Driver" +msgstr "" + +#: ./doc/glossary/glossary-terms.xml4126(para) +msgid "The nova volume driver for the SolidFire iSCSI storage appliance." +msgstr "" + +#: ./doc/glossary/glossary-terms.xml4131(glossterm) +msgid "spread-first scheduler" +msgstr "" + +#: ./doc/glossary/glossary-terms.xml4133(para) +msgid "" +"The nova VM scheduling algorithm that attempts to start new VM on the host " +"with the least amount of load." +msgstr "" + +#: ./doc/glossary/glossary-terms.xml4139(glossterm) +msgid "SQL-Alchemy" +msgstr "" + +#: ./doc/glossary/glossary-terms.xml4141(para) +msgid "An open source SQL toolkit for Python, used in OpenStack." +msgstr "" + +#: ./doc/glossary/glossary-terms.xml4146(glossterm) +msgid "SQLite" +msgstr "" + +#: ./doc/glossary/glossary-terms.xml4148(para) +msgid "" +"A lightweight SQL database, used as the default persistent storage method in" +" many OpenStack services." +msgstr "" + +#: ./doc/glossary/glossary-terms.xml4154(glossterm) +msgid "StackTach" +msgstr "" + +#: ./doc/glossary/glossary-terms.xml4156(para) +msgid "" +"Community project that captures nova AMQP communications, useful for " +"debugging." +msgstr "" + +#: ./doc/glossary/glossary-terms.xml4161(glossterm) +msgid "static IP address" +msgstr "" + +#: ./doc/glossary/glossary-terms.xml4163(para) +msgid "Alternative term for a fixed IP address." +msgstr "" + +#: ./doc/glossary/glossary-terms.xml4167(glossterm) +msgid "StaticWeb" +msgstr "" + +#: ./doc/glossary/glossary-terms.xml4169(para) +msgid "" +"WSGI middleware component of swift that serves container data as a static " +"web page." +msgstr "" + +#: ./doc/glossary/glossary-terms.xml4174(glossterm) +msgid "storage back-end" +msgstr "" + +#: ./doc/glossary/glossary-terms.xml4176(para) +msgid "" +"The method that a service uses for persistent storage such as iSCSI, NFS, or" +" local disk." +msgstr "" + +#: ./doc/glossary/glossary-terms.xml4181(glossterm) +msgid "storage node" +msgstr "" + +#: ./doc/glossary/glossary-terms.xml4183(para) +msgid "" +"A swift node that provides container services, account services, and object " +"services, controls the account databases, container databases, and object " +"storage." +msgstr "" + +#: ./doc/glossary/glossary-terms.xml4190(glossterm) +msgid "storage manager" +msgstr "" + +#: ./doc/glossary/glossary-terms.xml4192(para) +msgid "" +"A XenAPI component that provides a pluggable interface to support a wide " +"variety of persistent storage back-ends." +msgstr "" + +#: ./doc/glossary/glossary-terms.xml4198(glossterm) +msgid "storage manager back-end" +msgstr "" + +#: ./doc/glossary/glossary-terms.xml4200(para) +msgid "A persistent storage method supported by XenAPI such as iSCSI or NFS." +msgstr "" + +#: ./doc/glossary/glossary-terms.xml4205(glossterm) +msgid "storage services" +msgstr "" + +#: ./doc/glossary/glossary-terms.xml4207(para) +msgid "" +"Collective name for the swift object services, container services, and " +"account services." +msgstr "" + +#: ./doc/glossary/glossary-terms.xml4212(glossterm) +msgid "strategy" +msgstr "" + +#: ./doc/glossary/glossary-terms.xml4214(para) +msgid "Specifies the authentication source used by glance or keystone." +msgstr "" + +#: ./doc/glossary/glossary-terms.xml4219(glossterm) +msgid "subdomain" +msgstr "" + +#: ./doc/glossary/glossary-terms.xml4221(para) +msgid "" +"A domain within a parent domain. Subdomains cannot be registered. Subdomains" +" enable you to delegate domains. Subdomains can themselves have subdomains, " +"so third-level, fourth-level, fifth-level, and deeper levels of nesting are " +"possible." +msgstr "" + +#: ./doc/glossary/glossary-terms.xml4230(glossterm) +msgid "SUSE Linux Enterprise Server (SLES)" +msgstr "" + +#: ./doc/glossary/glossary-terms.xml4237(glossterm) +msgid "suspend" +msgstr "" + +#: ./doc/glossary/glossary-terms.xml4239(para) +msgid "Alternative term for a paused VM instance." +msgstr "" + +#: ./doc/glossary/glossary-terms.xml4244(glossterm) +msgid "swap" +msgstr "" + +#: ./doc/glossary/glossary-terms.xml4246(para) +msgid "" +"Disk-based virtual memory, used by operating systems to provide more memory " +"than is actually available on the system." +msgstr "" + +#: ./doc/glossary/glossary-terms.xml4252(glossterm) +msgid "swawth" +msgstr "" + +#: ./doc/glossary/glossary-terms.xml4254(para) +msgid "" +"An authentication and authorization service for swift, implemented through " +"WSGI middleware, uses swift itself as the persistent backing store." +msgstr "" + +#: ./doc/glossary/glossary-terms.xml4261(glossterm) +msgid "Swift" +msgstr "" + +#: ./doc/glossary/glossary-terms.xml4263(para) +msgid "An OpenStack core project that provides object storage services." +msgstr "" + +#: ./doc/glossary/glossary-terms.xml4268(glossterm) +msgid "swift All in One (SAIO)" +msgstr "" + +#: ./doc/glossary/glossary-terms.xml4270(para) +msgid "Creates a full swift development environment within a single VM." +msgstr "" + +#: ./doc/glossary/glossary-terms.xml4275(glossterm) +msgid "swift middleware" +msgstr "" + +#: ./doc/glossary/glossary-terms.xml4277(para) +msgid "" +"Collective term for swift components that provide additional functionality." +msgstr "" + +#: ./doc/glossary/glossary-terms.xml4282(glossterm) +msgid "swift proxy server" +msgstr "" + +#: ./doc/glossary/glossary-terms.xml4284(para) +msgid "" +"Acts as the gatekeeper to swift and is responsible for authenticating the " +"user." +msgstr "" + +#: ./doc/glossary/glossary-terms.xml4289(glossterm) +msgid "swift storage node" +msgstr "" + +#: ./doc/glossary/glossary-terms.xml4291(para) +msgid "A node that runs swift account, container, and object services." +msgstr "" + +#: ./doc/glossary/glossary-terms.xml4296(glossterm) +msgid "sync point" +msgstr "" + +#: ./doc/glossary/glossary-terms.xml4298(para) +msgid "" +"Point in time since the last container and accounts database sync among " +"nodes within swift." +msgstr "" + +#: ./doc/glossary/glossary-terms.xml4304(glossterm) +msgid "sysadmin" +msgstr "" + +#: ./doc/glossary/glossary-terms.xml4306(para) +msgid "" +"One of the default roles in the nova RBAC system. Enables a user to add " +"other users to a project, interact with VM images that are associated with " +"the project, and start and stop VM (VM) instances." +msgstr "" + +#: ./doc/glossary/glossary-terms.xml4313(glossterm) +msgid "system usage" +msgstr "" + +#: ./doc/glossary/glossary-terms.xml4315(para) +msgid "" +"A nova component that, along with the notification system, collects metrics " +"and usage information. Can be used for billing." +msgstr "" + +#: ./doc/glossary/glossary-terms.xml4323(title) +msgid "T" +msgstr "" + +#: ./doc/glossary/glossary-terms.xml4325(glossterm) +msgid "TempAuth" +msgstr "" + +#: ./doc/glossary/glossary-terms.xml4327(para) +msgid "" +"An authentication facility within swift that enables swift itself to perform" +" authentication and authorization. Frequently used in testing and " +"development." +msgstr "" + +#: ./doc/glossary/glossary-terms.xml4334(glossterm) +msgid "Tempest" +msgstr "" + +#: ./doc/glossary/glossary-terms.xml4336(para) +msgid "" +"Automated software test suite designed to run against the trunk of the " +"OpenStack core project." +msgstr "" + +#: ./doc/glossary/glossary-terms.xml4342(glossterm) +msgid "TempURL" +msgstr "" + +#: ./doc/glossary/glossary-terms.xml4344(para) +msgid "" +"A swift middleware component that enables creation of URLs for temporary " +"object access." +msgstr "" + +#: ./doc/glossary/glossary-terms.xml4348(glossterm) +msgid "tenant" +msgstr "" + +#: ./doc/glossary/glossary-terms.xml4350(para) +msgid "" +"A group of users, used to isolate access to nova resources. An alternative " +"term for a nova project." +msgstr "" + +#: ./doc/glossary/glossary-terms.xml4356(glossterm) +msgid "Tenant API" +msgstr "" + +#: ./doc/glossary/glossary-terms.xml4358(para) +msgid "An API that is accessible to tenants." +msgstr "" + +#: ./doc/glossary/glossary-terms.xml4362(glossterm) +msgid "tenant endpoint" +msgstr "" + +#: ./doc/glossary/glossary-terms.xml4364(para) +msgid "A keystone API endpoint that is associated with one or more tenants." +msgstr "" + +#: ./doc/glossary/glossary-terms.xml4369(glossterm) +msgid "tenant ID" +msgstr "" + +#: ./doc/glossary/glossary-terms.xml4371(para) +msgid "" +"Unique ID assigned to each tenant within keystone, the nova project IDs map " +"to the keystone tenant IDs." +msgstr "" + +#: ./doc/glossary/glossary-terms.xml4377(glossterm) +msgid "token" +msgstr "" + +#: ./doc/glossary/glossary-terms.xml4379(para) +msgid "" +"An alpha-numeric string of text used to access OpenStack APIs and resources." +msgstr "" + +#: ./doc/glossary/glossary-terms.xml4384(glossterm) +msgid "token services" +msgstr "" + +#: ./doc/glossary/glossary-terms.xml4386(para) +msgid "" +"A keystone component that manages and validates tokens after a user or " +"tenant has been authenticated." +msgstr "" + +#: ./doc/glossary/glossary-terms.xml4392(glossterm) +msgid "tombstone" +msgstr "" + +#: ./doc/glossary/glossary-terms.xml4394(para) +msgid "" +"Used to mark swift objects that have been deleted, ensures the object is not" +" updated on another node after it has been deleted." +msgstr "" + +#: ./doc/glossary/glossary-terms.xml4400(glossterm) +msgid "topic publisher" +msgstr "" + +#: ./doc/glossary/glossary-terms.xml4402(para) +msgid "" +"A process that is created when a RPC call is executed, used to push the " +"message to the topic exchange." +msgstr "" + +#: ./doc/glossary/glossary-terms.xml4408(glossterm) +msgid "Torpedo" +msgstr "" + +#: ./doc/glossary/glossary-terms.xml4410(para) +msgid "" +"Community project used to run automated tests against the OpenStack API." +msgstr "" + +#: ./doc/glossary/glossary-terms.xml4415(glossterm) +msgid "transaction ID" +msgstr "" + +#: ./doc/glossary/glossary-terms.xml4417(para) +msgid "" +"Unique ID assigned to each swift request, used for debugging and tracing." +msgstr "" + +#: ./doc/glossary/glossary-terms.xml4422(glossterm) +msgid "transient" +msgstr "" + +#: ./doc/glossary/glossary-terms.xml4424(para) +msgid "Alternative term for non-durable." +msgstr "" + +#: ./doc/glossary/glossary-terms.xml4428(glossterm) +msgid "transient exchange" +msgstr "" + +#: ./doc/glossary/glossary-terms.xml4430(para) +msgid "Alternative term for a non-durable exchange." +msgstr "" + +#: ./doc/glossary/glossary-terms.xml4435(glossterm) +msgid "transient message" +msgstr "" + +#: ./doc/glossary/glossary-terms.xml4437(para) +msgid "" +"A message that is stored in memory and is lost after the server is " +"restarted." +msgstr "" + +#: ./doc/glossary/glossary-terms.xml4442(glossterm) +msgid "transient queue" +msgstr "" + +#: ./doc/glossary/glossary-terms.xml4444(para) +msgid "Alternative term for a non-durable queue." +msgstr "" + +#: ./doc/glossary/glossary-terms.xml4448(glossterm) +msgid "Trove" +msgstr "" + +#: ./doc/glossary/glossary-terms.xml4450(para) +msgid "OpenStack project that provides database services to applications." +msgstr "" + +#: ./doc/glossary/glossary-terms.xml4464(title) +msgid "U" +msgstr "" + +#: ./doc/glossary/glossary-terms.xml4466(glossterm) +msgid "Ubuntu" +msgstr "" + +#: ./doc/glossary/glossary-terms.xml4468(para) +msgid "A Debian-based Linux distribution." +msgstr "" + +#: ./doc/glossary/glossary-terms.xml4472(glossterm) +msgid "unscoped token" +msgstr "" + +#: ./doc/glossary/glossary-terms.xml4474(para) +msgid "Alternative term for a keystone default token." +msgstr "" + +#: ./doc/glossary/glossary-terms.xml4479(glossterm) +msgid "updater" +msgstr "" + +#: ./doc/glossary/glossary-terms.xml4481(para) +msgid "" +"Collective term for a group of swift components that processes queued and " +"failed updates for containers and objects." +msgstr "" + +#: ./doc/glossary/glossary-terms.xml4487(glossterm) +msgid "user" +msgstr "" + +#: ./doc/glossary/glossary-terms.xml4489(para) +msgid "" +"In keystone each user is associated with one or more tenants, and in nova " +"they can be associated with roles, projects, or both." +msgstr "" + +#: ./doc/glossary/glossary-terms.xml4495(glossterm) +msgid "user data" +msgstr "" + +#: ./doc/glossary/glossary-terms.xml4497(para) +msgid "" +"A blob of data that can be specified by the user when launching an instance." +" This data can be accessed by the instance through the metadata service or " +"config drive. Commonly used for passing a shell script that is executed by " +"the instance on boot." +msgstr "" + +#: ./doc/glossary/glossary-terms.xml4506(glossterm) +msgid "User Mode Linux (UML)" +msgstr "" + +#: ./doc/glossary/glossary-terms.xml4520(title) +msgid "V" +msgstr "" + +#: ./doc/glossary/glossary-terms.xml4522(glossterm) +msgid "VIF UUID" +msgstr "" + +#: ./doc/glossary/glossary-terms.xml4524(para) +msgid "Unique ID assigned to each neutron VIF." +msgstr "" + +#: ./doc/glossary/glossary-terms.xml4528(glossterm) +msgid "Virtual Central Processing Unit (vCPU)" +msgstr "" + +#: ./doc/glossary/glossary-terms.xml4531(para) +msgid "Sub-divides physical CPUs. Instances can then use those divisions." +msgstr "" + +#: ./doc/glossary/glossary-terms.xml4536(glossterm) +msgid "Virtual Disk Image (VDI)" +msgstr "" + +#: ./doc/glossary/glossary-terms.xml4543(glossterm) +msgid "Virtual Hard Disk (VHD)" +msgstr "" + +#: ./doc/glossary/glossary-terms.xml4550(glossterm) +msgid "virtual IP" +msgstr "" + +#: ./doc/glossary/glossary-terms.xml4552(para) +msgid "" +"An Internet Protocol (IP) address configured on the load balancer for use by" +" clients connecting to a service that is load balanced. Incoming connections" +" are distributed to back-end nodes based on the configuration of the load " +"balancer." +msgstr "" + +#: ./doc/glossary/glossary-terms.xml4561(glossterm) +msgid "virtual machine (VM)" +msgstr "" + +#: ./doc/glossary/glossary-terms.xml4563(para) +msgid "" +"An operating system instance that runs on top of a hypervisor. Multiple VMs " +"can run at the same time on the same physical host." +msgstr "" + +#: ./doc/glossary/glossary-terms.xml4569(glossterm) +msgid "virtual network" +msgstr "" + +#: ./doc/glossary/glossary-terms.xml4571(para) +msgid "An L2 network segment within neutron." +msgstr "" + +#: ./doc/glossary/glossary-terms.xml4575(glossterm) +msgid "Virtual Network Computing (VNC)" +msgstr "" + +#: ./doc/glossary/glossary-terms.xml4577(para) +msgid "" +"Open source GUI and CLI tools used for remote console access to VMs. " +"Supported by nova." +msgstr "" + +#: ./doc/glossary/glossary-terms.xml4582(glossterm) +msgid "Virtual Network InterFace (VIF)" +msgstr "" + +#: ./doc/glossary/glossary-terms.xml4584(para) +msgid "" +"An interface that is plugged into a port in a neutron network. Typically a " +"virtual network interface belonging to a VM." +msgstr "" + +#: ./doc/glossary/glossary-terms.xml4590(glossterm) +msgid "virtual port" +msgstr "" + +#: ./doc/glossary/glossary-terms.xml4592(para) +msgid "" +"Attachment point where a virtual interface connects to a virtual network." +msgstr "" + +#: ./doc/glossary/glossary-terms.xml4597(glossterm) +msgid "virtual private network (VPN)" +msgstr "" + +#: ./doc/glossary/glossary-terms.xml4599(para) +msgid "" +"Provided by nova in the form of cloudpipes, specialized instances that are " +"used to create VPNs on a per-project basis." +msgstr "" + +#: ./doc/glossary/glossary-terms.xml4605(glossterm) +msgid "virtual server" +msgstr "" + +#: ./doc/glossary/glossary-terms.xml4607(para) +msgid "Alternative term for a VM or guest." +msgstr "" + +#: ./doc/glossary/glossary-terms.xml4611(glossterm) +msgid "virtual switch (vSwitch)" +msgstr "" + +#: ./doc/glossary/glossary-terms.xml4613(para) +msgid "" +"Software that runs on a host or node and provides the features and functions" +" of a hardware based network switch." +msgstr "" + +#: ./doc/glossary/glossary-terms.xml4619(glossterm) +msgid "virtual VLAN" +msgstr "" + +#: ./doc/glossary/glossary-terms.xml4621(para) +msgid "Alternative term for a virtual network." +msgstr "" + +#: ./doc/glossary/glossary-terms.xml4625(glossterm) +msgid "VirtualBox" +msgstr "" + +#: ./doc/glossary/glossary-terms.xml4631(glossterm) +msgid "VLAN manager" +msgstr "" + +#: ./doc/glossary/glossary-terms.xml4633(para) +msgid "" +"A nova component that provides dnsmasq, radvd, and sets up forwarding to and" +" from cloudpipe instances." +msgstr "" + +#: ./doc/glossary/glossary-terms.xml4639(glossterm) +msgid "VLAN network" +msgstr "" + +#: ./doc/glossary/glossary-terms.xml4641(para) +msgid "" +"The Network Controller provides virtual networks to enable compute servers " +"to interact with each other and with the public network. All machines must " +"have a public and private network interface. A VLAN network is a private " +"network interface, which is controlled by the vlan_interface option with " +"VLAN managers." +msgstr "" + +#: ./doc/glossary/glossary-terms.xml4651(glossterm) +msgid "VM disk (VMDK)" +msgstr "" + +#: ./doc/glossary/glossary-terms.xml4658(glossterm) +msgid "VM image" +msgstr "" + +#: ./doc/glossary/glossary-terms.xml4660(para) +msgid "Alternative term for an image." +msgstr "" + +#: ./doc/glossary/glossary-terms.xml4664(glossterm) +msgid "VM Remote Control (VMRC)" +msgstr "" + +#: ./doc/glossary/glossary-terms.xml4666(para) +msgid "" +"Method to access VM instance consoles using a web browser. Supported by " +"nova." +msgstr "" + +#: ./doc/glossary/glossary-terms.xml4671(glossterm) +msgid "VMware API" +msgstr "" + +#: ./doc/glossary/glossary-terms.xml4673(para) +msgid "Supports interaction with VMware products in nova." +msgstr "" + +#: ./doc/glossary/glossary-terms.xml4678(glossterm) +msgid "VNC proxy" +msgstr "" + +#: ./doc/glossary/glossary-terms.xml4680(para) +msgid "" +"A nova component that provides users access to the consoles of their VM " +"instances through VNC or VMRC." +msgstr "" + +#: ./doc/glossary/glossary-terms.xml4686(glossterm) +msgid "volume" +msgstr "" + +#: ./doc/glossary/glossary-terms.xml4688(para) +msgid "" +"Disk-based data storage generally represented as an iSCSI target with a file" +" system that supports extended attributes, can be persistent or ephemeral." +msgstr "" + +#: ./doc/glossary/glossary-terms.xml4695(glossterm) +msgid "Volume API" +msgstr "" + +#: ./doc/glossary/glossary-terms.xml4697(para) +msgid "" +"An API on a separate endpoint for attaching, detaching, and creating block " +"storage for compute VMs." +msgstr "" + +#: ./doc/glossary/glossary-terms.xml4703(glossterm) +msgid "volume controller" +msgstr "" + +#: ./doc/glossary/glossary-terms.xml4705(para) +msgid "A nova component that oversees and coordinates storage volume actions." +msgstr "" + +#: ./doc/glossary/glossary-terms.xml4710(glossterm) +msgid "volume driver" +msgstr "" + +#: ./doc/glossary/glossary-terms.xml4712(para) +msgid "Alternative term for a volume plug-in." +msgstr "" + +#: ./doc/glossary/glossary-terms.xml4716(glossterm) +msgid "volume ID" +msgstr "" + +#: ./doc/glossary/glossary-terms.xml4718(para) +msgid "Unique ID applied to each storage volume under the nova control." +msgstr "" + +#: ./doc/glossary/glossary-terms.xml4723(glossterm) +msgid "volume manager" +msgstr "" + +#: ./doc/glossary/glossary-terms.xml4725(para) +msgid "" +"A nova component that creates, attaches, and detaches persistent storage " +"volumes." +msgstr "" + +#: ./doc/glossary/glossary-terms.xml4730(glossterm) +msgid "volume node" +msgstr "" + +#: ./doc/glossary/glossary-terms.xml4732(para) +msgid "" +"A nova node that runs the cinder-" +"volume daemon." +msgstr "" + +#: ./doc/glossary/glossary-terms.xml4737(glossterm) +msgid "volume plug-in" +msgstr "" + +#: ./doc/glossary/glossary-terms.xml4739(para) +msgid "" +"Provides support for new and specialized types of back-end storage for the " +"nova volume manager." +msgstr "" + +#: ./doc/glossary/glossary-terms.xml4745(glossterm) +msgid "Volume Service API" +msgstr "" + +#: ./doc/glossary/glossary-terms.xml4747(para) +msgid "Alternative term for the nova volume API." +msgstr "" + +#: ./doc/glossary/glossary-terms.xml4751(glossterm) +msgid "volume worker" +msgstr "" + +#: ./doc/glossary/glossary-terms.xml4753(para) +msgid "" +"A cinder component that interacts with back-end storage to manage the " +"creation and deletion of volumes and the creation of compute volumes, " +"provided by the cinder-volume " +"daemon." +msgstr "" + +#: ./doc/glossary/glossary-terms.xml4760(glossterm) +msgid "vSphere" +msgstr "" + +#: ./doc/glossary/glossary-terms.xml4774(title) +msgid "W" +msgstr "" + +#: ./doc/glossary/glossary-terms.xml4776(glossterm) +msgid "weighing" +msgstr "" + +#: ./doc/glossary/glossary-terms.xml4778(para) +msgid "" +"A nova process that determines the suitability of the VM instances for a job" +" for a particular host. For example, not enough RAM on the host, too many " +"CPUs on the host, and so on." +msgstr "" + +#: ./doc/glossary/glossary-terms.xml4785(glossterm) +msgid "weight" +msgstr "" + +#: ./doc/glossary/glossary-terms.xml4787(para) +msgid "" +"Used by swift storage devices to determine which storage devices are " +"suitable for the job. Devices are weighted by size." +msgstr "" + +#: ./doc/glossary/glossary-terms.xml4793(glossterm) +msgid "weighted cost" +msgstr "" + +#: ./doc/glossary/glossary-terms.xml4795(para) +msgid "" +"The sum of each cost used when deciding where to start a new VM instance in " +"nova." +msgstr "" + +#: ./doc/glossary/glossary-terms.xml4800(glossterm) +msgid "worker" +msgstr "" + +#: ./doc/glossary/glossary-terms.xml4802(para) +msgid "" +"A daemon that listens to a queue and carries out tasks in response to " +"messages. For example, the cinder-" +"volume worker attaches storage to instances." +msgstr "" + +#: ./doc/glossary/glossary-terms.xml4816(title) +msgid "X" +msgstr "" + +#: ./doc/glossary/glossary-terms.xml4818(glossterm) +msgid "Xen API" +msgstr "" + +#: ./doc/glossary/glossary-terms.xml4820(para) +msgid "The Xen administrative API, which is supported by nova." +msgstr "" + +#: ./doc/glossary/glossary-terms.xml4825(glossterm) +msgid "Xen Cloud Platform (XCP)" +msgstr "" + +#: ./doc/glossary/glossary-terms.xml4831(glossterm) +msgid "Xen Storage Manager Volume Driver" +msgstr "" + +#: ./doc/glossary/glossary-terms.xml4833(para) +msgid "" +"A nova volume plug-in that enables communication with the Xen Storage " +"Manager API." +msgstr "" + +#: ./doc/glossary/glossary-terms.xml4839(glossterm) +msgid "XenServer" +msgstr "" + +#: ./doc/glossary/glossary-terms.xml4853(title) +msgid "Y" +msgstr "" + +#: ./doc/glossary/glossary-terms.xml4863(title) +msgid "Z" +msgstr "" + +#: ./doc/glossary/glossary-terms.xml4865(glossterm) +msgid "ZeroMQ" +msgstr "" + +#: ./doc/glossary/glossary-terms.xml4867(para) +msgid "" +"Message queue software supported by OpenStack. An alternative to RabbitMQ. " +"Also spelled 0MQ." +msgstr "" + +#: ./doc/glossary/glossary-terms.xml4873(glossterm) +msgid "Zuul" +msgstr "" + +#: ./doc/glossary/glossary-terms.xml4875(para) +msgid "" +"Tool used in OpenStack development to ensure correctly ordered testing of " +"changes in parallel." +msgstr "" + +#: ./doc/glossary/openstack-glossary.xml9(title) +#: ./doc/glossary/openstack-glossary.xml12(title) +msgid "OpenStack Glossary" +msgstr "" + +#: ./doc/glossary/openstack-glossary.xml13(para) +msgid "" +"Use this glossary to get definitions of OpenStack-related words and phrases." +msgstr "" + +#: ./doc/glossary/openstack-glossary.xml15(para) +msgid "" +"To add to this glossary, fork the openstack-manuals " +"repository on github.com and update the source files through the OpenStack " +"contribution process." +msgstr "" + +#. Put one translator per line, in the form of NAME , YEAR1, YEAR2 +#: ./doc/glossary/openstack-glossary.xml0(None) +msgid "translator-credits" +msgstr "" diff --git a/doc/high-availability-guide/locale/he_IL.po b/doc/high-availability-guide/locale/he_IL.po new file mode 100644 index 0000000000..faca0b1f70 --- /dev/null +++ b/doc/high-availability-guide/locale/he_IL.po @@ -0,0 +1,2304 @@ +# +# Translators: +msgid "" +msgstr "" +"Project-Id-Version: OpenStack Manuals\n" +"POT-Creation-Date: 2014-01-30 06:24+0000\n" +"PO-Revision-Date: 2014-01-22 06:47+0000\n" +"Last-Translator: openstackjenkins \n" +"Language-Team: Hebrew (Israel) (http://www.transifex.com/projects/p/openstack/language/he_IL/)\n" +"MIME-Version: 1.0\n" +"Content-Type: text/plain; charset=UTF-8\n" +"Content-Transfer-Encoding: 8bit\n" +"Language: he_IL\n" +"Plural-Forms: nplurals=2; plural=(n != 1);\n" + +#: ./doc/high-availability-guide/ha-guide-docinfo.xml4(firstname) +#: ./doc/high-availability-guide/bk-ha-guide.xml8(firstname) +msgid "Florian" +msgstr "" + +#: ./doc/high-availability-guide/ha-guide-docinfo.xml5(surname) +#: ./doc/high-availability-guide/bk-ha-guide.xml9(surname) +msgid "Haas" +msgstr "" + +#: ./doc/high-availability-guide/ha-guide-docinfo.xml7(email) +#: ./doc/high-availability-guide/bk-ha-guide.xml11(email) +msgid "florian@hastexo.com" +msgstr "" + +#: ./doc/high-availability-guide/ha-guide-docinfo.xml9(orgname) +#: ./doc/high-availability-guide/bk-ha-guide.xml13(orgname) +msgid "hastexo" +msgstr "" + +#: ./doc/high-availability-guide/bk-ha-guide.xml5(title) +msgid "OpenStack High Availability Guide" +msgstr "" + +#: ./doc/high-availability-guide/bk-ha-guide.xml17(year) +msgid "2012" +msgstr "" + +#: ./doc/high-availability-guide/bk-ha-guide.xml18(year) +msgid "2013" +msgstr "" + +#: ./doc/high-availability-guide/bk-ha-guide.xml19(holder) +msgid "OpenStack Contributors" +msgstr "" + +#: ./doc/high-availability-guide/bk-ha-guide.xml21(releaseinfo) +msgid "master" +msgstr "" + +#: ./doc/high-availability-guide/bk-ha-guide.xml22(productname) +msgid "OpenStack" +msgstr "" + +#: ./doc/high-availability-guide/bk-ha-guide.xml26(remark) +msgid "Copyright details are filled in by the template." +msgstr "" + +#: ./doc/high-availability-guide/bk-ha-guide.xml31(date) +msgid "2012-01-16" +msgstr "" + +#: ./doc/high-availability-guide/bk-ha-guide.xml35(para) +msgid "Organizes guide based on cloud controller and compute nodes." +msgstr "" + +#: ./doc/high-availability-guide/bk-ha-guide.xml41(date) +msgid "2012-05-24" +msgstr "" + +#: ./doc/high-availability-guide/bk-ha-guide.xml45(para) +msgid "Begin trunk designation." +msgstr "" + +#: ./doc/high-availability-guide/bk-ha-guide.xml54(title) +msgid "Introduction to OpenStack High Availability" +msgstr "" + +#: ./doc/high-availability-guide/bk-ha-guide.xml56(simpara) +msgid "High Availability systems seek to minimize two things:" +msgstr "" + +#: ./doc/high-availability-guide/bk-ha-guide.xml59(simpara) +msgid "" +"System downtime — occurs when a " +"user-facing service is unavailable beyond a specified " +"maximum amount of time, and" +msgstr "" + +#: ./doc/high-availability-guide/bk-ha-guide.xml63(simpara) +msgid "" +"Data loss — accidental deletion or " +"destruction of data." +msgstr "" + +#: ./doc/high-availability-guide/bk-ha-guide.xml67(simpara) +msgid "" +"Most high availability systems guarantee protection against system downtime " +"and data loss only in the event of a single failure. However, they are also " +"expected to protect against cascading failures, where a single failure " +"deteriorates into a series of consequential failures." +msgstr "" + +#: ./doc/high-availability-guide/bk-ha-guide.xml68(simpara) +msgid "" +"A crucial aspect of high availability is the elimination of single points of" +" failure (SPOFs). A SPOF is an individual piece of equipment or software " +"which will cause system downtime or data loss if it fails. In order to " +"eliminate SPOFs, check that mechanisms exist for redundancy of:" +msgstr "" + +#: ./doc/high-availability-guide/bk-ha-guide.xml71(simpara) +msgid "Network components, such as switches and routers" +msgstr "" + +#: ./doc/high-availability-guide/bk-ha-guide.xml76(simpara) +msgid "Applications and automatic service migration" +msgstr "" + +#: ./doc/high-availability-guide/bk-ha-guide.xml81(simpara) +msgid "Storage components" +msgstr "" + +#: ./doc/high-availability-guide/bk-ha-guide.xml86(simpara) +msgid "Facility services such as power, air conditioning, and fire protection" +msgstr "" + +#: ./doc/high-availability-guide/bk-ha-guide.xml91(simpara) +msgid "" +"Most high availability systems will fail in the event of multiple " +"independent (non-consequential) failures. In this case, most systems will " +"protect data over maintaining availability." +msgstr "" + +#: ./doc/high-availability-guide/bk-ha-guide.xml92(simpara) +msgid "" +"High-availability systems typically achieve uptime of 99.99% or more, which " +"roughly equates to less than an hour of cumulative downtime per year. In " +"order to achieve this, high availability systems should keep recovery times " +"after a failure to about one to two minutes, sometimes significantly less." +msgstr "" + +#: ./doc/high-availability-guide/bk-ha-guide.xml93(simpara) +msgid "" +"OpenStack currently meets such availability requirements for its own " +"infrastructure services, meaning that an uptime of 99.99% is feasible for " +"the OpenStack infrastructure proper. However, OpenStack " +"doesnot guarantee 99.99% " +"availability for individual guest instances." +msgstr "" + +#: ./doc/high-availability-guide/bk-ha-guide.xml94(simpara) +msgid "" +"Preventing single points of failure can depend on whether or not a service " +"is stateless." +msgstr "" + +#: ./doc/high-availability-guide/bk-ha-guide.xml97(title) +msgid "Stateless vs. Stateful services" +msgstr "" + +#: ./doc/high-availability-guide/bk-ha-guide.xml99(simpara) +msgid "" +"A stateless service is one that provides a response after your request, and " +"then requires no further attention. To make a stateless service highly " +"available, you need to provide redundant instances and load balance them. " +"OpenStack services that are stateless include nova-api, nova-conductor, " +"glance-api, keystone-api, neutron-api and nova-scheduler." +msgstr "" + +#: ./doc/high-availability-guide/bk-ha-guide.xml100(simpara) +msgid "" +"A stateful service is one where subsequent requests to the service depend on" +" the results of the first request. Stateful services are more difficult to " +"manage because a single action typically involves more than one request, so " +"simply providing additional instances and load balancing will not solve the " +"problem. For example, if the Horizon user interface reset itself every time " +"you went to a new page, it wouldn’t be very useful. OpenStack services that " +"are stateful include the OpenStack database and message queue." +msgstr "" + +#: ./doc/high-availability-guide/bk-ha-guide.xml101(simpara) +msgid "" +"Making stateful services highly available can depend on whether you choose " +"an active/passive or active/active configuration." +msgstr "" + +#: ./doc/high-availability-guide/bk-ha-guide.xml105(title) +msgid "Active/Passive" +msgstr "" + +#: ./doc/high-availability-guide/bk-ha-guide.xml107(simpara) +msgid "" +"In an active/passive configuration, systems are set up to bring additional " +"resources online to replace those that have failed. For example, OpenStack " +"would write to the main database while maintaining a disaster recovery " +"database that can be brought online in the event that the main database " +"fails." +msgstr "" + +#: ./doc/high-availability-guide/bk-ha-guide.xml108(simpara) +msgid "" +"Typically, an active/passive installation for a stateless service would " +"maintain a redundant instance that can be brought online when required. " +"Requests are load balanced using a virtual IP address and a load balancer " +"such as HAProxy." +msgstr "" + +#: ./doc/high-availability-guide/bk-ha-guide.xml109(simpara) +msgid "" +"A typical active/passive installation for a stateful service maintains a " +"replacement resource that can be brought online when required. A separate " +"application (such as Pacemaker or Corosync) monitors these services, " +"bringing the backup online as necessary." +msgstr "" + +#: ./doc/high-availability-guide/bk-ha-guide.xml113(title) +msgid "Active/Active" +msgstr "" + +#: ./doc/high-availability-guide/bk-ha-guide.xml115(simpara) +msgid "" +"In an active/active configuration, systems also use a backup but will manage" +" both the main and redundant systems concurrently. This way, if there is a " +"failure the user is unlikely to notice. The backup system is already online," +" and takes on increased load while the main system is fixed and brought back" +" online." +msgstr "" + +#: ./doc/high-availability-guide/bk-ha-guide.xml116(simpara) +msgid "" +"Typically, an active/active installation for a stateless service would " +"maintain a redundant instance, and requests are load balanced using a " +"virtual IP address and a load balancer such as HAProxy." +msgstr "" + +#: ./doc/high-availability-guide/bk-ha-guide.xml117(simpara) +msgid "" +"A typical active/active installation for a stateful service would include " +"redundant services with all instances having an identical state. For " +"example, updates to one instance of a database would also update all other " +"instances. This way a request to one instance is the same as a request to " +"any other. A load balancer manages the traffic to these systems, ensuring " +"that operational systems always handle the request." +msgstr "" + +#: ./doc/high-availability-guide/bk-ha-guide.xml118(simpara) +msgid "" +"These are some of the more common ways to implement these high availability " +"architectures, but they are by no means the only ways to do it. The " +"important thing is to make sure that your services are redundant, and " +"available; how you achieve that is up to you. This document will cover some " +"of the more common options for highly available systems." +msgstr "" + +#: ./doc/high-availability-guide/bk-ha-guide.xml123(title) +msgid "HA Using Active/Passive" +msgstr "" + +#: ./doc/high-availability-guide/bk-ha-guide.xml127(title) +msgid "The Pacemaker Cluster Stack" +msgstr "" + +#: ./doc/high-availability-guide/bk-ha-guide.xml129(simpara) +msgid "" +"OpenStack infrastructure high availability relies on the Pacemaker cluster stack, the " +"state-of-the-art high availability and load balancing stack for the Linux " +"platform. Pacemaker is storage- and application-agnostic, and is in no way " +"specific to OpenStack." +msgstr "" + +#: ./doc/high-availability-guide/bk-ha-guide.xml134(simpara) +msgid "" +"Pacemaker relies on the Corosync messaging layer for " +"reliable cluster communications. Corosync implements the Totem single-ring " +"ordering and membership protocol and provides UDP and InfiniBand based " +"messaging, quorum, and cluster membership to Pacemaker." +msgstr "" + +#: ./doc/high-availability-guide/bk-ha-guide.xml139(simpara) +msgid "" +"Pacemaker interacts with applications through resource " +"agents (RAs), of which it supports over 70 natively. Pacemaker " +"can also easily use third-party RAs. An OpenStack high-availability " +"configuration uses existing native Pacemaker RAs (such as those managing " +"MySQL databases or virtual IP addresses), existing third-party RAs (such as " +"for RabbitMQ), and native OpenStack RAs (such as those managing the " +"OpenStack Identity and Image Services)." +msgstr "" + +#: ./doc/high-availability-guide/bk-ha-guide.xml148(title) +msgid "Installing Packages" +msgstr "" + +#: ./doc/high-availability-guide/bk-ha-guide.xml150(simpara) +msgid "" +"On any host that is meant to be part of a Pacemaker cluster, you must first " +"establish cluster communications through the Corosync messaging layer. This " +"involves installing the following packages (and their dependencies, which " +"your package manager will normally install automatically):" +msgstr "" + +#: ./doc/high-availability-guide/bk-ha-guide.xml158(literal) +msgid "pacemaker" +msgstr "" + +#: ./doc/high-availability-guide/bk-ha-guide.xml163(literal) +msgid "corosync" +msgstr "" + +#: ./doc/high-availability-guide/bk-ha-guide.xml168(literal) +msgid "cluster-glue" +msgstr "" + +#: ./doc/high-availability-guide/bk-ha-guide.xml172(simpara) +msgid "" +"fence-agents (Fedora only; all other distributions use " +"fencing agents from cluster-glue)" +msgstr "" + +#: ./doc/high-availability-guide/bk-ha-guide.xml178(literal) +msgid "resource-agents" +msgstr "" + +#: ./doc/high-availability-guide/bk-ha-guide.xml185(title) +msgid "Setting up Corosync" +msgstr "" + +#: ./doc/high-availability-guide/bk-ha-guide.xml187(simpara) +msgid "" +"Besides installing the corosync package, you will also " +"have to create a configuration file, stored in " +"/etc/corosync/corosync.conf. Most distributions ship an " +"example configuration file (corosync.conf.example) as " +"part of the documentation bundled with the corosync " +"package. An example Corosync configuration file is shown below:" +msgstr "" + +#: ./doc/high-availability-guide/bk-ha-guide.xml195(title) +msgid "Corosync configuration file (corosync.conf)" +msgstr "" + +#: ./doc/high-availability-guide/bk-ha-guide.xml269(para) +msgid "" +"The token value specifies the time, in milliseconds, " +"during which the Corosync token is expected to be transmitted around the " +"ring. When this timeout expires, the token is declared lost, and after " +"token_retransmits_before_loss_const lost tokens the non-" +"responding processor (cluster node) is declared dead. " +"In other words, token × " +"token_retransmits_before_loss_const is the maximum time a" +" node is allowed to not respond to cluster messages before being considered " +"dead. The default for token is 1000 (1 second), with 4 " +"allowed retransmits. These defaults are intended to minimize failover times," +" but can cause frequent \"false alarms\" and unintended failovers in case of" +" short network interruptions. The values used here are safer, albeit with " +"slightly extended failover times." +msgstr "" + +#: ./doc/high-availability-guide/bk-ha-guide.xml285(para) +msgid "" +"With secauth enabled, Corosync nodes mutually " +"authenticate using a 128-byte shared secret stored in " +"/etc/corosync/authkey, which may be generated with the " +"corosync-keygen utility. When using " +"secauth, cluster communications are also encrypted." +msgstr "" + +#: ./doc/high-availability-guide/bk-ha-guide.xml293(para) +msgid "" +"In Corosync configurations using redundant networking (with more than one " +"interface), you must select a Redundant Ring Protocol " +"(RRP) mode other than none. active is " +"the recommended RRP mode." +msgstr "" + +#: ./doc/high-availability-guide/bk-ha-guide.xml300(para) +msgid "" +"There are several things to note about the recommended interface " +"configuration:" +msgstr "" + +#: ./doc/high-availability-guide/bk-ha-guide.xml306(simpara) +msgid "" +"The ringnumber must differ between all configured " +"interfaces, starting with 0." +msgstr "" + +#: ./doc/high-availability-guide/bk-ha-guide.xml312(simpara) +msgid "" +"The bindnetaddr is the network " +"address of the interfaces to bind to. The example uses two network addresses" +" of /24 IPv4 subnets." +msgstr "" + +#: ./doc/high-availability-guide/bk-ha-guide.xml318(simpara) +msgid "" +"Multicast groups (mcastaddr) must " +"not be reused across cluster boundaries. In other words, no two " +"distinct clusters should ever use the same multicast group. Be sure to " +"select multicast addresses compliant with RFC 2365, \"Administratively " +"Scoped IP Multicast\"." +msgstr "" + +#: ./doc/high-availability-guide/bk-ha-guide.xml327(simpara) +msgid "" +"For firewall configurations, note that Corosync communicates over UDP only, " +"and uses mcastport (for receives) and " +"mcastport-1 (for sends)." +msgstr "" + +#: ./doc/high-availability-guide/bk-ha-guide.xml336(para) +msgid "" +"The service declaration for the " +"pacemaker service may be placed in the " +"corosync.conf file directly, or in its own separate file," +" /etc/corosync/service.d/pacemaker." +msgstr "" + +#: ./doc/high-availability-guide/bk-ha-guide.xml343(simpara) +msgid "" +"Once created, the corosync.conf file (and the " +"authkey file if the secauth option is " +"enabled) must be synchronized across all cluster nodes." +msgstr "" + +#: ./doc/high-availability-guide/bk-ha-guide.xml349(title) +msgid "Starting Corosync" +msgstr "" + +#: ./doc/high-availability-guide/bk-ha-guide.xml351(simpara) +msgid "" +"Corosync is started as a regular system service. Depending on your " +"distribution, it may ship with a LSB (System V style) init script, an " +"upstart job, or a systemd unit file. Either way, the service is usually " +"named corosync:" +msgstr "" + +#: ./doc/high-availability-guide/bk-ha-guide.xml357(simpara) +msgid "/etc/init.d/corosync start (LSB)" +msgstr "" + +#: ./doc/high-availability-guide/bk-ha-guide.xml361(simpara) +msgid "service corosync start (LSB, alternate)" +msgstr "" + +#: ./doc/high-availability-guide/bk-ha-guide.xml365(simpara) +msgid "start corosync (upstart)" +msgstr "" + +#: ./doc/high-availability-guide/bk-ha-guide.xml369(simpara) +msgid "systemctl start corosync (systemd)" +msgstr "" + +#: ./doc/high-availability-guide/bk-ha-guide.xml373(simpara) +msgid "You can now check Corosync connectivity with two tools." +msgstr "" + +#: ./doc/high-availability-guide/bk-ha-guide.xml374(simpara) +msgid "" +"The corosync-cfgtool utility, when invoked with the " +"-s option, gives a summary of the health of the " +"communication rings:" +msgstr "" + +#: ./doc/high-availability-guide/bk-ha-guide.xml385(simpara) +msgid "" +"The corosync-objctl utility can be used to dump the " +"Corosync cluster member list:" +msgstr "" + +#: ./doc/high-availability-guide/bk-ha-guide.xml394(simpara) +msgid "" +"You should see a status=joined entry for each of your " +"constituent cluster nodes." +msgstr "" + +#: ./doc/high-availability-guide/bk-ha-guide.xml399(title) +msgid "Starting Pacemaker" +msgstr "" + +#: ./doc/high-availability-guide/bk-ha-guide.xml401(simpara) +msgid "" +"Once the Corosync services have been started, and you have established that " +"the cluster is communicating properly, it is safe to start " +"pacemakerd, the Pacemaker master control process:" +msgstr "" + +#: ./doc/high-availability-guide/bk-ha-guide.xml406(simpara) +msgid "/etc/init.d/pacemaker start (LSB)" +msgstr "" + +#: ./doc/high-availability-guide/bk-ha-guide.xml410(simpara) +msgid "service pacemaker start (LSB, alternate)" +msgstr "" + +#: ./doc/high-availability-guide/bk-ha-guide.xml414(simpara) +msgid "start pacemaker (upstart)" +msgstr "" + +#: ./doc/high-availability-guide/bk-ha-guide.xml418(simpara) +msgid "systemctl start pacemaker (systemd)" +msgstr "" + +#: ./doc/high-availability-guide/bk-ha-guide.xml422(simpara) +msgid "" +"Once Pacemaker services have started, Pacemaker will create an default empty" +" cluster configuration with no resources. You may observe Pacemaker’s status" +" with the crm_mon utility:" +msgstr "" + +#: ./doc/high-availability-guide/bk-ha-guide.xml439(title) +msgid "Setting basic cluster properties" +msgstr "" + +#: ./doc/high-availability-guide/bk-ha-guide.xml441(simpara) +msgid "" +"Once your Pacemaker cluster is set up, it is recommended to set a few basic " +"cluster properties. To do so, start the crm shell and " +"change into the configuration menu by entering configure." +" Alternatively. you may jump straight into the Pacemaker configuration menu " +"by typing crm configure directly from a shell prompt." +msgstr "" + +#: ./doc/high-availability-guide/bk-ha-guide.xml447(simpara) +msgid "Then, set the following properties:" +msgstr "" + +#: ./doc/high-availability-guide/bk-ha-guide.xml455(para) +msgid "" +"Setting no-quorum-policy=\"ignore\" is required in 2-node" +" Pacemaker clusters for the following reason: if quorum enforcement is " +"enabled, and one of the two nodes fails, then the remaining node can not " +"establish a majority of quorum votes necessary to run " +"services, and thus it is unable to take over any resources. The appropriate " +"workaround is to ignore loss of quorum in the cluster. This is safe and " +"necessary only in 2-node clusters. Do not set this " +"property in Pacemaker clusters with more than two nodes." +msgstr "" + +#: ./doc/high-availability-guide/bk-ha-guide.xml467(para) +msgid "" +"Setting pe-warn-series-max, pe-input-series-" +"max and pe-error-series-max to 1000 instructs " +"Pacemaker to keep a longer history of the inputs processed, and errors and " +"warnings generated, by its Policy Engine. This history is typically useful " +"in case cluster troubleshooting becomes necessary." +msgstr "" + +#: ./doc/high-availability-guide/bk-ha-guide.xml476(para) +msgid "" +"Pacemaker uses an event-driven approach to cluster state processing. " +"However, certain Pacemaker actions occur at a configurable interval, " +"cluster-recheck-interval, which defaults to 15 minutes. " +"It is usually prudent to reduce this to a shorter interval, such as 5 or 3 " +"minutes." +msgstr "" + +#: ./doc/high-availability-guide/bk-ha-guide.xml485(simpara) +msgid "" +"Once you have made these changes, you may commit the " +"updated configuration." +msgstr "" + +#: ./doc/high-availability-guide/bk-ha-guide.xml491(title) +msgid "Cloud Controller Cluster Stack" +msgstr "" + +#: ./doc/high-availability-guide/bk-ha-guide.xml493(simpara) +msgid "" +"The Cloud Controller sits on the management network and needs to talk to all" +" other services." +msgstr "" + +#: ./doc/high-availability-guide/bk-ha-guide.xml496(title) +msgid "Highly available MySQL" +msgstr "" + +#: ./doc/high-availability-guide/bk-ha-guide.xml498(simpara) +msgid "" +"MySQL is the default database server used by many OpenStack services. Making" +" the MySQL service highly available involves" +msgstr "" + +#: ./doc/high-availability-guide/bk-ha-guide.xml502(simpara) +msgid "configuring a DRBD device for use by MySQL," +msgstr "" + +#: ./doc/high-availability-guide/bk-ha-guide.xml507(simpara) +msgid "" +"configuring MySQL to use a data directory residing on that DRBD device," +msgstr "" + +#: ./doc/high-availability-guide/bk-ha-guide.xml513(simpara) +#: ./doc/high-availability-guide/bk-ha-guide.xml759(simpara) +msgid "" +"selecting and assigning a virtual IP address (VIP) that can freely float " +"between cluster nodes," +msgstr "" + +#: ./doc/high-availability-guide/bk-ha-guide.xml519(simpara) +msgid "configuring MySQL to listen on that IP address," +msgstr "" + +#: ./doc/high-availability-guide/bk-ha-guide.xml524(simpara) +msgid "" +"managing all resources, including the MySQL daemon itself, with the " +"Pacemaker cluster manager." +msgstr "" + +#: ./doc/high-availability-guide/bk-ha-guide.xml531(simpara) +msgid "" +"MySQL/Galera is " +"an alternative method of configuring MySQL for high availability. It is " +"likely to become the preferred method of achieving MySQL high availability " +"once it has sufficiently matured. At the time of writing, however, the " +"Pacemaker/DRBD based approach remains the recommended one for OpenStack " +"environments." +msgstr "" + +#: ./doc/high-availability-guide/bk-ha-guide.xml540(title) +#: ./doc/high-availability-guide/bk-ha-guide.xml789(title) +msgid "Configuring DRBD" +msgstr "" + +#: ./doc/high-availability-guide/bk-ha-guide.xml542(simpara) +msgid "" +"The Pacemaker based MySQL server requires a DRBD resource from which it " +"mounts the /var/lib/mysql directory. In this example, the" +" DRBD resource is simply named mysql:" +msgstr "" + +#: ./doc/high-availability-guide/bk-ha-guide.xml547(title) +msgid "" +"mysql DRBD resource configuration " +"(/etc/drbd.d/mysql.res)" +msgstr "" + +#: ./doc/high-availability-guide/bk-ha-guide.xml563(simpara) +msgid "" +"This resource uses an underlying local disk (in DRBD terminology, a " +"backing device) named " +"/dev/data/mysql on both cluster nodes, " +"node1 and node2. Normally, this would " +"be an LVM Logical Volume specifically set aside for this purpose. The DRBD " +"meta-disk is internal, meaning DRBD-" +"specific metadata is being stored at the end of the disk " +"device itself. The device is configured to communicate between IPv4 " +"addresses 10.0.42.100 and 10.0.42.254, using TCP port 7700. Once enabled, it" +" will map to a local DRBD block device with the device minor number 0, that " +"is, /dev/drbd0." +msgstr "" + +#: ./doc/high-availability-guide/bk-ha-guide.xml572(simpara) +#: ./doc/high-availability-guide/bk-ha-guide.xml821(simpara) +msgid "" +"Enabling a DRBD resource is explained in detail in the DRBD " +"User’s Guide. In brief, the proper sequence of commands is this:" +msgstr "" + +#: ./doc/high-availability-guide/bk-ha-guide.xml580(para) +msgid "" +"Initializes DRBD metadata and writes the initial set of metadata to " +"/dev/data/mysql. Must be completed on both nodes." +msgstr "" + +#: ./doc/high-availability-guide/bk-ha-guide.xml586(para) +msgid "" +"Creates the /dev/drbd0 device node, " +"attaches the DRBD device to its backing store, and " +"connects the DRBD node to its peer. Must be completed " +"on both nodes." +msgstr "" + +#: ./doc/high-availability-guide/bk-ha-guide.xml593(para) +#: ./doc/high-availability-guide/bk-ha-guide.xml842(para) +msgid "" +"Kicks off the initial device synchronization, and puts the device into the " +"primary (readable and writable) role. See Resource " +"roles (from the DRBD User’s Guide) for a more detailed description of" +" the primary and secondary roles in DRBD. Must be completed on one" +" node only, namely the one where you are about to continue with " +"creating your filesystem." +msgstr "" + +#: ./doc/high-availability-guide/bk-ha-guide.xml607(title) +#: ./doc/high-availability-guide/bk-ha-guide.xml856(title) +msgid "Creating a file system" +msgstr "" + +#: ./doc/high-availability-guide/bk-ha-guide.xml609(simpara) +msgid "" +"Once the DRBD resource is running and in the primary role (and potentially " +"still in the process of running the initial device synchronization), you may" +" proceed with creating the filesystem for MySQL data. XFS is the generally " +"recommended filesystem:" +msgstr "" + +#: ./doc/high-availability-guide/bk-ha-guide.xml614(simpara) +#: ./doc/high-availability-guide/bk-ha-guide.xml863(simpara) +msgid "" +"You may also use the alternate device path for the DRBD device, which may be" +" easier to remember as it includes the self-explanatory resource name:" +msgstr "" + +#: ./doc/high-availability-guide/bk-ha-guide.xml618(simpara) +#: ./doc/high-availability-guide/bk-ha-guide.xml867(simpara) +msgid "" +"Once completed, you may safely return the device to the secondary role. Any " +"ongoing device synchronization will continue in the background:" +msgstr "" + +#: ./doc/high-availability-guide/bk-ha-guide.xml625(title) +msgid "Preparing MySQL for Pacemaker high availability" +msgstr "" + +#: ./doc/high-availability-guide/bk-ha-guide.xml627(simpara) +msgid "" +"In order for Pacemaker monitoring to function properly, you must ensure that" +" MySQL’s database files reside on the DRBD device. If you already have an " +"existing MySQL database, the simplest approach is to just move the contents " +"of the existing /var/lib/mysql directory into the newly " +"created filesystem on the DRBD device." +msgstr "" + +#: ./doc/high-availability-guide/bk-ha-guide.xml633(simpara) +msgid "" +"You must complete the next step while the MySQL database server is shut " +"down." +msgstr "" + +#: ./doc/high-availability-guide/bk-ha-guide.xml639(simpara) +msgid "" +"For a new MySQL installation with no existing data, you may also run the " +"mysql_install_db command:" +msgstr "" + +#: ./doc/high-availability-guide/bk-ha-guide.xml644(simpara) +msgid "" +"Regardless of the approach, the steps outlined here must be completed on " +"only one cluster node." +msgstr "" + +#: ./doc/high-availability-guide/bk-ha-guide.xml649(title) +msgid "Adding MySQL resources to Pacemaker" +msgstr "" + +#: ./doc/high-availability-guide/bk-ha-guide.xml651(simpara) +msgid "" +"You may now proceed with adding the Pacemaker configuration for MySQL " +"resources. Connect to the Pacemaker cluster with crm " +"configure, and add the following cluster resources:" +msgstr "" + +#: ./doc/high-availability-guide/bk-ha-guide.xml687(simpara) +#: ./doc/high-availability-guide/bk-ha-guide.xml921(simpara) +#: ./doc/high-availability-guide/bk-ha-guide.xml1120(simpara) +#: ./doc/high-availability-guide/bk-ha-guide.xml1211(simpara) +#: ./doc/high-availability-guide/bk-ha-guide.xml1370(simpara) +#: ./doc/high-availability-guide/bk-ha-guide.xml1444(simpara) +#: ./doc/high-availability-guide/bk-ha-guide.xml1488(simpara) +#: ./doc/high-availability-guide/bk-ha-guide.xml1529(simpara) +msgid "This configuration creates" +msgstr "" + +#: ./doc/high-availability-guide/bk-ha-guide.xml690(simpara) +msgid "" +"p_ip_mysql, a virtual IP address for use by MySQL " +"(192.168.42.101)," +msgstr "" + +#: ./doc/high-availability-guide/bk-ha-guide.xml695(simpara) +msgid "" +"p_fs_mysql, a Pacemaker managed filesystem mounted to " +"/var/lib/mysql on whatever node currently runs the MySQL " +"service," +msgstr "" + +#: ./doc/high-availability-guide/bk-ha-guide.xml701(simpara) +msgid "" +"ms_drbd_mysql, the master/slave set " +"managing the mysql DRBD resource," +msgstr "" + +#: ./doc/high-availability-guide/bk-ha-guide.xml706(simpara) +#: ./doc/high-availability-guide/bk-ha-guide.xml940(simpara) +msgid "" +"a service group and order and " +"colocation constraints to ensure resources are started on" +" the correct nodes, and in the correct sequence." +msgstr "" + +#: ./doc/high-availability-guide/bk-ha-guide.xml712(simpara) +msgid "" +"crm configure supports batch input, so you may copy and " +"paste the above into your live pacemaker configuration, and then make " +"changes as required. For example, you may enter edit " +"p_ip_mysql from the crm configure menu and edit" +" the resource to match your preferred virtual IP address." +msgstr "" + +#: ./doc/high-availability-guide/bk-ha-guide.xml717(simpara) +msgid "" +"Once completed, commit your configuration changes by entering " +"commit from the crm configure menu. " +"Pacemaker will then start the MySQL service, and its dependent resources, on" +" one of your nodes." +msgstr "" + +#: ./doc/high-availability-guide/bk-ha-guide.xml723(title) +msgid "Configuring OpenStack services for highly available MySQL" +msgstr "" + +#: ./doc/high-availability-guide/bk-ha-guide.xml725(simpara) +msgid "" +"Your OpenStack services must now point their MySQL configuration to the " +"highly available, virtual cluster IP address — rather than a MySQL server’s " +"physical IP address as you normally would." +msgstr "" + +#: ./doc/high-availability-guide/bk-ha-guide.xml728(simpara) +msgid "" +"For OpenStack Image, for example, if your MySQL service IP address is " +"192.168.42.101 as in the configuration explained here, you would use the " +"following line in your OpenStack Image registry configuration file (glance-registry.conf):" +msgstr "" + +#: ./doc/high-availability-guide/bk-ha-guide.xml733(simpara) +msgid "" +"No other changes are necessary to your OpenStack configuration. If the node " +"currently hosting your database experiences a problem necessitating service " +"failover, your OpenStack services may experience a brief MySQL interruption," +" as they would in the event of a network hiccup, and then continue to run " +"normally." +msgstr "" + +#: ./doc/high-availability-guide/bk-ha-guide.xml742(title) +msgid "Highly available RabbitMQ" +msgstr "" + +#: ./doc/high-availability-guide/bk-ha-guide.xml744(simpara) +msgid "" +"RabbitMQ is the default AMQP server used by many OpenStack services. Making " +"the RabbitMQ service highly available involves" +msgstr "" + +#: ./doc/high-availability-guide/bk-ha-guide.xml748(simpara) +msgid "configuring a DRBD device for use by RabbitMQ," +msgstr "" + +#: ./doc/high-availability-guide/bk-ha-guide.xml753(simpara) +msgid "" +"configuring RabbitMQ to use a data directory residing on that DRBD device," +msgstr "" + +#: ./doc/high-availability-guide/bk-ha-guide.xml765(simpara) +msgid "configuring RabbitMQ to listen on that IP address," +msgstr "" + +#: ./doc/high-availability-guide/bk-ha-guide.xml770(simpara) +msgid "" +"managing all resources, including the RabbitMQ daemon itself, with the " +"Pacemaker cluster manager." +msgstr "" + +#: ./doc/high-availability-guide/bk-ha-guide.xml777(simpara) +msgid "" +"There is an alternative method of configuring RabbitMQ for high " +"availability. That approach, known as active-active mirrored " +"queues, happens to be the one preferred by the RabbitMQ developers — " +"however it has shown less than ideal consistency and reliability in " +"OpenStack clusters. Thus, at the time of writing, the Pacemaker/DRBD based " +"approach remains the recommended one for OpenStack environments, although " +"this may change in the near future as RabbitMQ active-active mirrored queues" +" mature." +msgstr "" + +#: ./doc/high-availability-guide/bk-ha-guide.xml791(simpara) +msgid "" +"The Pacemaker based RabbitMQ server requires a DRBD resource from which it " +"mounts the /var/lib/rabbitmq directory. In this example, " +"the DRBD resource is simply named rabbitmq:" +msgstr "" + +#: ./doc/high-availability-guide/bk-ha-guide.xml796(title) +msgid "" +"rabbitmq DRBD resource configuration " +"(/etc/drbd.d/rabbitmq.res)" +msgstr "" + +#: ./doc/high-availability-guide/bk-ha-guide.xml812(simpara) +msgid "" +"This resource uses an underlying local disk (in DRBD terminology, a " +"backing device) named " +"/dev/data/rabbitmq on both cluster nodes, " +"node1 and node2. Normally, this would " +"be an LVM Logical Volume specifically set aside for this purpose. The DRBD " +"meta-disk is internal, meaning DRBD-" +"specific metadata is being stored at the end of the disk " +"device itself. The device is configured to communicate between IPv4 " +"addresses 10.0.42.100 and 10.0.42.254, using TCP port 7701. Once enabled, it" +" will map to a local DRBD block device with the device minor number 1, that " +"is, /dev/drbd1." +msgstr "" + +#: ./doc/high-availability-guide/bk-ha-guide.xml829(para) +msgid "" +"Initializes DRBD metadata and writes the initial set of metadata to " +"/dev/data/rabbitmq. Must be completed on both nodes." +msgstr "" + +#: ./doc/high-availability-guide/bk-ha-guide.xml835(para) +msgid "" +"Creates the /dev/drbd1 device node, " +"attaches the DRBD device to its backing store, and " +"connects the DRBD node to its peer. Must be completed " +"on both nodes." +msgstr "" + +#: ./doc/high-availability-guide/bk-ha-guide.xml858(simpara) +msgid "" +"Once the DRBD resource is running and in the primary role (and potentially " +"still in the process of running the initial device synchronization), you may" +" proceed with creating the filesystem for RabbitMQ data. XFS is the " +"generally recommended filesystem:" +msgstr "" + +#: ./doc/high-availability-guide/bk-ha-guide.xml874(title) +msgid "Preparing RabbitMQ for Pacemaker high availability" +msgstr "" + +#: ./doc/high-availability-guide/bk-ha-guide.xml876(simpara) +msgid "" +"In order for Pacemaker monitoring to function properly, you must ensure that" +" RabbitMQ’s .erlang.cookie files are identical on all " +"nodes, regardless of whether DRBD is mounted there or not. The simplest way " +"of doing so is to take an existing .erlang.cookie from " +"one of your nodes, copying it to the RabbitMQ data directory on the other " +"node, and also copying it to the DRBD-backed filesystem." +msgstr "" + +#: ./doc/high-availability-guide/bk-ha-guide.xml889(title) +msgid "Adding RabbitMQ resources to Pacemaker" +msgstr "" + +#: ./doc/high-availability-guide/bk-ha-guide.xml891(simpara) +msgid "" +"You may now proceed with adding the Pacemaker configuration for RabbitMQ " +"resources. Connect to the Pacemaker cluster with crm " +"configure, and add the following cluster resources:" +msgstr "" + +#: ./doc/high-availability-guide/bk-ha-guide.xml924(simpara) +msgid "" +"p_ip_rabbitmp, a virtual IP address for use by RabbitMQ " +"(192.168.42.100)," +msgstr "" + +#: ./doc/high-availability-guide/bk-ha-guide.xml929(simpara) +msgid "" +"p_fs_rabbitmq, a Pacemaker managed filesystem mounted to " +"/var/lib/rabbitmq on whatever node currently runs the " +"RabbitMQ service," +msgstr "" + +#: ./doc/high-availability-guide/bk-ha-guide.xml935(simpara) +msgid "" +"ms_drbd_rabbitmq, the master/slave " +"set managing the rabbitmq DRBD resource," +msgstr "" + +#: ./doc/high-availability-guide/bk-ha-guide.xml946(simpara) +msgid "" +"crm configure supports batch input, so you may copy and " +"paste the above into your live pacemaker configuration, and then make " +"changes as required. For example, you may enter edit " +"p_ip_rabbitmq from the crm configure menu and " +"edit the resource to match your preferred virtual IP address." +msgstr "" + +#: ./doc/high-availability-guide/bk-ha-guide.xml951(simpara) +msgid "" +"Once completed, commit your configuration changes by entering " +"commit from the crm configure menu. " +"Pacemaker will then start the RabbitMQ service, and its dependent resources," +" on one of your nodes." +msgstr "" + +#: ./doc/high-availability-guide/bk-ha-guide.xml957(title) +msgid "Configuring OpenStack services for highly available RabbitMQ" +msgstr "" + +#: ./doc/high-availability-guide/bk-ha-guide.xml959(simpara) +msgid "" +"Your OpenStack services must now point their RabbitMQ configuration to the " +"highly available, virtual cluster IP address — rather than a RabbitMQ " +"server’s physical IP address as you normally would." +msgstr "" + +#: ./doc/high-availability-guide/bk-ha-guide.xml962(simpara) +msgid "" +"For OpenStack Image, for example, if your RabbitMQ service IP address is " +"192.168.42.100 as in the configuration explained here, you would use the " +"following line in your OpenStack Image API configuration file (glance-api.conf):" +msgstr "" + +#: ./doc/high-availability-guide/bk-ha-guide.xml967(simpara) +msgid "" +"No other changes are necessary to your OpenStack configuration. If the node " +"currently hosting your RabbitMQ experiences a problem necessitating service " +"failover, your OpenStack services may experience a brief RabbitMQ " +"interruption, as they would in the event of a network hiccup, and then " +"continue to run normally." +msgstr "" + +#: ./doc/high-availability-guide/bk-ha-guide.xml977(title) +msgid "API Node Cluster Stack" +msgstr "" + +#: ./doc/high-availability-guide/bk-ha-guide.xml979(simpara) +msgid "" +"The API node exposes OpenStack API endpoints onto external network " +"(Internet). It needs to talk to the Cloud Controller on the management " +"network." +msgstr "" + +#: ./doc/high-availability-guide/bk-ha-guide.xml983(title) +msgid "Configure the VIP" +msgstr "" + +#: ./doc/high-availability-guide/bk-ha-guide.xml985(simpara) +msgid "" +"First of all, we need to select and assign a virtual IP address (VIP) that " +"can freely float between cluster nodes." +msgstr "" + +#: ./doc/high-availability-guide/bk-ha-guide.xml986(simpara) +msgid "" +"This configuration creates p_ip_api, a virtual IP address" +" for use by the API node (192.168.42.103) :" +msgstr "" + +#: ./doc/high-availability-guide/bk-ha-guide.xml993(title) +msgid "Highly available OpenStack Identity" +msgstr "" + +#: ./doc/high-availability-guide/bk-ha-guide.xml995(simpara) +msgid "" +"OpenStack Identity is the Identity Service in OpenStack and used by many " +"services. Making the OpenStack Identity service highly available in active /" +" passive mode involves" +msgstr "" + +#: ./doc/high-availability-guide/bk-ha-guide.xml999(simpara) +msgid "configuring OpenStack Identity to listen on the VIP address," +msgstr "" + +#: ./doc/high-availability-guide/bk-ha-guide.xml1004(simpara) +msgid "managing OpenStack Identity daemon with the Pacemaker cluster manager," +msgstr "" + +#: ./doc/high-availability-guide/bk-ha-guide.xml1009(simpara) +#: ./doc/high-availability-guide/bk-ha-guide.xml1098(simpara) +#: ./doc/high-availability-guide/bk-ha-guide.xml1188(simpara) +#: ./doc/high-availability-guide/bk-ha-guide.xml1272(simpara) +msgid "configuring OpenStack services to use this IP address." +msgstr "" + +#: ./doc/high-availability-guide/bk-ha-guide.xml1015(simpara) +msgid "" +"Here is the documentation for installing OpenStack Identity " +"service." +msgstr "" + +#: ./doc/high-availability-guide/bk-ha-guide.xml1019(title) +msgid "Adding OpenStack Identity resource to Pacemaker" +msgstr "" + +#: ./doc/high-availability-guide/bk-ha-guide.xml1021(simpara) +#: ./doc/high-availability-guide/bk-ha-guide.xml1110(simpara) +#: ./doc/high-availability-guide/bk-ha-guide.xml1200(simpara) +#: ./doc/high-availability-guide/bk-ha-guide.xml1284(simpara) +#: ./doc/high-availability-guide/bk-ha-guide.xml1360(simpara) +#: ./doc/high-availability-guide/bk-ha-guide.xml1477(simpara) +msgid "First of all, you need to download the resource agent to your system :" +msgstr "" + +#: ./doc/high-availability-guide/bk-ha-guide.xml1027(simpara) +msgid "" +"You may now proceed with adding the Pacemaker configuration for OpenStack " +"Identity resource. Connect to the Pacemaker cluster with crm " +"configure, and add the following cluster resources:" +msgstr "" + +#: ./doc/high-availability-guide/bk-ha-guide.xml1033(simpara) +msgid "" +"This configuration creates p_keystone, a resource for " +"manage OpenStack Identity service." +msgstr "" + +#: ./doc/high-availability-guide/bk-ha-guide.xml1034(simpara) +msgid "" +"crm configure supports batch input, so you may copy and " +"paste the above into your live pacemaker configuration, and then make " +"changes as required. For example, you may enter edit " +"p_ip_keystone from the crm configure menu and " +"edit the resource to match your preferred virtual IP address." +msgstr "" + +#: ./doc/high-availability-guide/bk-ha-guide.xml1039(simpara) +msgid "" +"Once completed, commit your configuration changes by entering " +"commit from the crm configure menu. " +"Pacemaker will then start the OpenStack Identity service, and its dependent " +"resources, on one of your nodes." +msgstr "" + +#: ./doc/high-availability-guide/bk-ha-guide.xml1045(title) +msgid "Configuring OpenStack Identity service" +msgstr "" + +#: ./doc/high-availability-guide/bk-ha-guide.xml1047(simpara) +msgid "" +"You need to edit your OpenStack Identity configuration file " +"(keystone.conf) and change the bind parameters :" +msgstr "" + +#: ./doc/high-availability-guide/bk-ha-guide.xml1048(simpara) +msgid "On Havana:" +msgstr "" + +#: ./doc/high-availability-guide/bk-ha-guide.xml1050(simpara) +msgid "" +"On Icehouse, the admin_bind_host option lets you use a " +"private network for the admin access." +msgstr "" + +#: ./doc/high-availability-guide/bk-ha-guide.xml1053(simpara) +msgid "" +"To be sure all data will be high available, you should be sure that you " +"store everything in the MySQL database (which is also high available) :" +msgstr "" + +#: ./doc/high-availability-guide/bk-ha-guide.xml1063(title) +msgid "" +"Configuring OpenStack Services to use High Available OpenStack Identity" +msgstr "" + +#: ./doc/high-availability-guide/bk-ha-guide.xml1065(simpara) +msgid "" +"Your OpenStack services must now point their OpenStack Identity " +"configuration to the highly available, virtual cluster IP address — rather " +"than a OpenStack Identity server’s physical IP address as you normally " +"would." +msgstr "" + +#: ./doc/high-availability-guide/bk-ha-guide.xml1068(simpara) +msgid "" +"For example with OpenStack Compute, if your OpenStack Identity service IP " +"address is 192.168.42.103 as in the configuration explained here, you would " +"use the following line in your API configuration file (api-" +"paste.ini):" +msgstr "" + +#: ./doc/high-availability-guide/bk-ha-guide.xml1073(simpara) +msgid "You need also to create the OpenStack Identity Endpoint with this IP." +msgstr "" + +#: ./doc/high-availability-guide/bk-ha-guide.xml1074(simpara) +msgid "" +"NOTE : If you are using both private and public IP addresses, you should " +"create two Virtual IP addresses and define your endpoint like this :" +msgstr "" + +#: ./doc/high-availability-guide/bk-ha-guide.xml1076(simpara) +msgid "" +"If you are using the Horizon Dashboard, you should edit " +"local_settings.py file :" +msgstr "" + +#: ./doc/high-availability-guide/bk-ha-guide.xml1082(title) +msgid "Highly available OpenStack Image API" +msgstr "" + +#: ./doc/high-availability-guide/bk-ha-guide.xml1084(simpara) +msgid "" +"OpenStack Image Service offers a service for discovering, registering, and " +"retrieving virtual machine images. Making the OpenStack Image API service " +"highly available in active / passive mode involves" +msgstr "" + +#: ./doc/high-availability-guide/bk-ha-guide.xml1088(simpara) +msgid "configuring OpenStack Image to listen on the VIP address," +msgstr "" + +#: ./doc/high-availability-guide/bk-ha-guide.xml1093(simpara) +msgid "" +"managing OpenStack Image API daemon with the Pacemaker cluster manager," +msgstr "" + +#: ./doc/high-availability-guide/bk-ha-guide.xml1104(simpara) +msgid "" +"Here is the documentation for installing OpenStack Image API " +"service." +msgstr "" + +#: ./doc/high-availability-guide/bk-ha-guide.xml1108(title) +msgid "Adding OpenStack Image API resource to Pacemaker" +msgstr "" + +#: ./doc/high-availability-guide/bk-ha-guide.xml1114(simpara) +msgid "" +"You may now proceed with adding the Pacemaker configuration for OpenStack " +"Image API resource. Connect to the Pacemaker cluster with crm " +"configure, and add the following cluster resources:" +msgstr "" + +#: ./doc/high-availability-guide/bk-ha-guide.xml1123(simpara) +msgid "" +"p_glance-api, a resource for manage OpenStack Image API " +"service" +msgstr "" + +#: ./doc/high-availability-guide/bk-ha-guide.xml1127(simpara) +msgid "" +"crm configure supports batch input, so you may copy and " +"paste the above into your live pacemaker configuration, and then make " +"changes as required. For example, you may enter edit p_ip_glance-" +"api from the crm configure menu and edit the " +"resource to match your preferred virtual IP address." +msgstr "" + +#: ./doc/high-availability-guide/bk-ha-guide.xml1132(simpara) +msgid "" +"Once completed, commit your configuration changes by entering " +"commit from the crm configure menu. " +"Pacemaker will then start the OpenStack Image API service, and its dependent" +" resources, on one of your nodes." +msgstr "" + +#: ./doc/high-availability-guide/bk-ha-guide.xml1138(title) +msgid "Configuring OpenStack Image API service" +msgstr "" + +#: ./doc/high-availability-guide/bk-ha-guide.xml1140(simpara) +msgid "Edit /etc/glance/glance-api.conf :" +msgstr "" + +#: ./doc/high-availability-guide/bk-ha-guide.xml1156(title) +msgid "" +"Configuring OpenStack Services to use High Available OpenStack Image API" +msgstr "" + +#: ./doc/high-availability-guide/bk-ha-guide.xml1158(simpara) +msgid "" +"Your OpenStack services must now point their OpenStack Image API " +"configuration to the highly available, virtual cluster IP address — rather " +"than a OpenStack Image API server’s physical IP address as you normally " +"would." +msgstr "" + +#: ./doc/high-availability-guide/bk-ha-guide.xml1161(simpara) +msgid "" +"For OpenStack Compute, for example, if your OpenStack Image API service IP " +"address is 192.168.42.104 as in the configuration explained here, you would " +"use the following line in your nova.conf file :" +msgstr "" + +#: ./doc/high-availability-guide/bk-ha-guide.xml1165(simpara) +msgid "You need also to create the OpenStack Image API Endpoint with this IP." +msgstr "" + +#: ./doc/high-availability-guide/bk-ha-guide.xml1166(simpara) +#: ./doc/high-availability-guide/bk-ha-guide.xml1334(simpara) +msgid "" +"NOTE : If you are using both private and public IP addresses, you should " +"create two Virtual IP addresses and define your endpoint like this:" +msgstr "" + +#: ./doc/high-availability-guide/bk-ha-guide.xml1172(title) +msgid "Highly available Cinder API" +msgstr "" + +#: ./doc/high-availability-guide/bk-ha-guide.xml1174(simpara) +msgid "" +"Cinder is the block storage service in OpenStack. Making the Cinder API " +"service highly available in active / passive mode involves" +msgstr "" + +#: ./doc/high-availability-guide/bk-ha-guide.xml1178(simpara) +msgid "configuring Cinder to listen on the VIP address," +msgstr "" + +#: ./doc/high-availability-guide/bk-ha-guide.xml1183(simpara) +msgid "managing Cinder API daemon with the Pacemaker cluster manager," +msgstr "" + +#: ./doc/high-availability-guide/bk-ha-guide.xml1194(simpara) +msgid "" +"Here is the documentation for " +"installing Cinder service." +msgstr "" + +#: ./doc/high-availability-guide/bk-ha-guide.xml1198(title) +msgid "Adding Cinder API resource to Pacemaker" +msgstr "" + +#: ./doc/high-availability-guide/bk-ha-guide.xml1204(simpara) +msgid "" +"You may now proceed with adding the Pacemaker configuration for Cinder API " +"resource. Connect to the Pacemaker cluster with crm " +"configure, and add the following cluster resources:" +msgstr "" + +#: ./doc/high-availability-guide/bk-ha-guide.xml1214(simpara) +msgid "" +"p_cinder-api, a resource for manage Cinder API service" +msgstr "" + +#: ./doc/high-availability-guide/bk-ha-guide.xml1218(simpara) +msgid "" +"crm configure supports batch input, so you may copy and " +"paste the above into your live pacemaker configuration, and then make " +"changes as required. For example, you may enter edit p_ip_cinder-" +"api from the crm configure menu and edit the " +"resource to match your preferred virtual IP address." +msgstr "" + +#: ./doc/high-availability-guide/bk-ha-guide.xml1223(simpara) +msgid "" +"Once completed, commit your configuration changes by entering " +"commit from the crm configure menu. " +"Pacemaker will then start the Cinder API service, and its dependent " +"resources, on one of your nodes." +msgstr "" + +#: ./doc/high-availability-guide/bk-ha-guide.xml1229(title) +msgid "Configuring Cinder API service" +msgstr "" + +#: ./doc/high-availability-guide/bk-ha-guide.xml1231(simpara) +msgid "Edit /etc/cinder/cinder.conf :" +msgstr "" + +#: ./doc/high-availability-guide/bk-ha-guide.xml1244(title) +msgid "Configuring OpenStack Services to use High Available Cinder API" +msgstr "" + +#: ./doc/high-availability-guide/bk-ha-guide.xml1246(simpara) +msgid "" +"Your OpenStack services must now point their Cinder API configuration to the" +" highly available, virtual cluster IP address — rather than a Cinder API " +"server’s physical IP address as you normally would." +msgstr "" + +#: ./doc/high-availability-guide/bk-ha-guide.xml1249(simpara) +msgid "You need to create the Cinder API Endpoint with this IP." +msgstr "" + +#: ./doc/high-availability-guide/bk-ha-guide.xml1250(simpara) +msgid "" +"NOTE : If you are using both private and public IP, you should create two " +"Virtual IP and define your endpoint like this :" +msgstr "" + +#: ./doc/high-availability-guide/bk-ha-guide.xml1256(title) +msgid "Highly available OpenStack Networking Server" +msgstr "" + +#: ./doc/high-availability-guide/bk-ha-guide.xml1258(simpara) +msgid "" +"OpenStack Networking is the network connectivity service in OpenStack. " +"Making the OpenStack Networking Server service highly available in active / " +"passive mode involves" +msgstr "" + +#: ./doc/high-availability-guide/bk-ha-guide.xml1262(simpara) +msgid "configuring OpenStack Networking to listen on the VIP address," +msgstr "" + +#: ./doc/high-availability-guide/bk-ha-guide.xml1267(simpara) +msgid "" +"managing OpenStack Networking API Server daemon with the Pacemaker cluster " +"manager," +msgstr "" + +#: ./doc/high-availability-guide/bk-ha-guide.xml1278(simpara) +msgid "" +"Here is the documentation for installing OpenStack Networking " +"service." +msgstr "" + +#: ./doc/high-availability-guide/bk-ha-guide.xml1282(title) +msgid "Adding OpenStack Networking Server resource to Pacemaker" +msgstr "" + +#: ./doc/high-availability-guide/bk-ha-guide.xml1288(simpara) +msgid "" +"You may now proceed with adding the Pacemaker configuration for OpenStack " +"Networking Server resource. Connect to the Pacemaker cluster with " +"crm configure, and add the following cluster resources:" +msgstr "" + +#: ./doc/high-availability-guide/bk-ha-guide.xml1295(simpara) +msgid "" +"This configuration creates p_neutron-server, a resource " +"for manage OpenStack Networking Server service" +msgstr "" + +#: ./doc/high-availability-guide/bk-ha-guide.xml1296(simpara) +msgid "" +"crm configure supports batch input, so you may copy and " +"paste the above into your live pacemaker configuration, and then make " +"changes as required. For example, you may enter edit p_neutron-" +"server from the crm configure menu and edit the" +" resource to match your preferred virtual IP address." +msgstr "" + +#: ./doc/high-availability-guide/bk-ha-guide.xml1301(simpara) +msgid "" +"Once completed, commit your configuration changes by entering " +"commit from the crm configure menu. " +"Pacemaker will then start the OpenStack Networking API service, and its " +"dependent resources, on one of your nodes." +msgstr "" + +#: ./doc/high-availability-guide/bk-ha-guide.xml1307(title) +msgid "Configuring OpenStack Networking Server" +msgstr "" + +#: ./doc/high-availability-guide/bk-ha-guide.xml1309(simpara) +msgid "Edit /etc/neutron/neutron.conf :" +msgstr "" + +#: ./doc/high-availability-guide/bk-ha-guide.xml1326(title) +msgid "" +"Configuring OpenStack Services to use Highly available OpenStack Networking " +"Server" +msgstr "" + +#: ./doc/high-availability-guide/bk-ha-guide.xml1328(simpara) +msgid "" +"Your OpenStack services must now point their OpenStack Networking Server " +"configuration to the highly available, virtual cluster IP address — rather " +"than an OpenStack Networking server’s physical IP address as you normally " +"would." +msgstr "" + +#: ./doc/high-availability-guide/bk-ha-guide.xml1331(simpara) +msgid "" +"For example, you should configure OpenStack Compute for using Highly " +"Available OpenStack Networking Server in editing " +"nova.conf file :" +msgstr "" + +#: ./doc/high-availability-guide/bk-ha-guide.xml1333(simpara) +msgid "" +"You need to create the OpenStack Networking Server Endpoint with this IP." +msgstr "" + +#: ./doc/high-availability-guide/bk-ha-guide.xml1340(title) +msgid "Highly available Ceilometer Central Agent" +msgstr "" + +#: ./doc/high-availability-guide/bk-ha-guide.xml1342(simpara) +msgid "" +"Ceilometer is the metering service in OpenStack. Central Agent polls for " +"resource utilization statistics for resources not tied to instances or " +"compute nodes." +msgstr "" + +#: ./doc/high-availability-guide/bk-ha-guide.xml1346(simpara) +msgid "" +"Due to limitations of a polling model, a single instance of this agent can " +"be polling a given list of meters. In this setup, we install this service on" +" the API nodes also in the active / passive mode." +msgstr "" + +#: ./doc/high-availability-guide/bk-ha-guide.xml1350(simpara) +msgid "" +"Making the Ceilometer Central Agent service highly available in active / " +"passive mode involves managing its daemon with the Pacemaker cluster " +"manager," +msgstr "" + +#: ./doc/high-availability-guide/bk-ha-guide.xml1353(simpara) +msgid "" +"You will find at this page the process to install " +"Ceilometer Central Agent." +msgstr "" + +#: ./doc/high-availability-guide/bk-ha-guide.xml1358(title) +msgid "Adding Ceilometer Central Agent resource to Pacemaker" +msgstr "" + +#: ./doc/high-availability-guide/bk-ha-guide.xml1364(simpara) +msgid "" +"You may then proceed with adding the Pacemaker configuration for Ceilometer " +"Central Agent resource. Connect to the Pacemaker cluster with crm " +"configure, and add the following cluster resources:" +msgstr "" + +#: ./doc/high-availability-guide/bk-ha-guide.xml1373(simpara) +msgid "" +"p_ceilometer-agent-central, a resource for manage " +"Ceilometer Central Agent service" +msgstr "" + +#: ./doc/high-availability-guide/bk-ha-guide.xml1377(simpara) +#: ./doc/high-availability-guide/bk-ha-guide.xml1451(simpara) +#: ./doc/high-availability-guide/bk-ha-guide.xml1496(simpara) +#: ./doc/high-availability-guide/bk-ha-guide.xml1537(simpara) +msgid "" +"crm configure supports batch input, so you may copy and " +"paste the above into your live pacemaker configuration, and then make " +"changes as required." +msgstr "" + +#: ./doc/high-availability-guide/bk-ha-guide.xml1380(simpara) +msgid "" +"Once completed, commit your configuration changes by entering " +"commit from the crm configure menu. " +"Pacemaker will then start the Ceilometer Central Agent service, and its " +"dependent resources, on one of your nodes." +msgstr "" + +#: ./doc/high-availability-guide/bk-ha-guide.xml1386(title) +msgid "Configuring Ceilometer Central Agent service" +msgstr "" + +#: ./doc/high-availability-guide/bk-ha-guide.xml1388(simpara) +msgid "Edit /etc/ceilometer/ceilometer.conf :" +msgstr "" + +#: ./doc/high-availability-guide/bk-ha-guide.xml1403(title) +msgid "Configure Pacemaker Group" +msgstr "" + +#: ./doc/high-availability-guide/bk-ha-guide.xml1405(simpara) +msgid "" +"Finally, we need to create a service group to ensure that" +" virtual IP is linked to the API services resources :" +msgstr "" + +#: ./doc/high-availability-guide/bk-ha-guide.xml1412(title) +msgid "Network Controller Cluster Stack" +msgstr "" + +#: ./doc/high-availability-guide/bk-ha-guide.xml1414(simpara) +msgid "" +"The Network controller sits on the management and data network, and needs to" +" be connected to the Internet if a VM needs access to it." +msgstr "" + +#: ./doc/high-availability-guide/bk-ha-guide.xml1416(simpara) +msgid "" +"Both nodes should have the same hostname since the Neutron scheduler will be" +" aware of one node, for example a virtual router attached to a single L3 " +"node." +msgstr "" + +#: ./doc/high-availability-guide/bk-ha-guide.xml1421(title) +msgid "Highly available Neutron L3 Agent" +msgstr "" + +#: ./doc/high-availability-guide/bk-ha-guide.xml1423(simpara) +msgid "" +"The Neutron L3 agent provides L3/NAT forwarding to ensure external network " +"access for VMs on tenant networks. High Availability for the L3 agent is " +"achieved by adopting Pacemaker." +msgstr "" + +#: ./doc/high-availability-guide/bk-ha-guide.xml1427(simpara) +msgid "" +"Here is the documentation for " +"installing Neutron L3 Agent." +msgstr "" + +#: ./doc/high-availability-guide/bk-ha-guide.xml1431(title) +msgid "Adding Neutron L3 Agent resource to Pacemaker" +msgstr "" + +#: ./doc/high-availability-guide/bk-ha-guide.xml1433(simpara) +#: ./doc/high-availability-guide/bk-ha-guide.xml1518(simpara) +msgid "First of all, you need to download the resource agent to your system:" +msgstr "" + +#: ./doc/high-availability-guide/bk-ha-guide.xml1437(simpara) +msgid "" +"You may now proceed with adding the Pacemaker configuration for Neutron L3 " +"Agent resource. Connect to the Pacemaker cluster with crm " +"configure, and add the following cluster resources:" +msgstr "" + +#: ./doc/high-availability-guide/bk-ha-guide.xml1447(simpara) +msgid "" +"p_neutron-l3-agent, a resource for manage Neutron L3 " +"Agent service" +msgstr "" + +#: ./doc/high-availability-guide/bk-ha-guide.xml1454(simpara) +msgid "" +"Once completed, commit your configuration changes by entering " +"commit from the crm configure menu. " +"Pacemaker will then start the Neutron L3 Agent service, and its dependent " +"resources, on one of your nodes." +msgstr "" + +#: ./doc/high-availability-guide/bk-ha-guide.xml1458(simpara) +msgid "" +"This method does not ensure a zero downtime since it has to recreate all the" +" namespaces and virtual routers on the node." +msgstr "" + +#: ./doc/high-availability-guide/bk-ha-guide.xml1465(title) +msgid "Highly available Neutron DHCP Agent" +msgstr "" + +#: ./doc/high-availability-guide/bk-ha-guide.xml1467(simpara) +msgid "" +"Neutron DHCP agent distributes IP addresses to the VMs with dnsmasq (by " +"default). High Availability for the DHCP agent is achieved by adopting " +"Pacemaker." +msgstr "" + +#: ./doc/high-availability-guide/bk-ha-guide.xml1471(simpara) +msgid "" +"Here is the documentation for" +" installing Neutron DHCP Agent." +msgstr "" + +#: ./doc/high-availability-guide/bk-ha-guide.xml1475(title) +msgid "Adding Neutron DHCP Agent resource to Pacemaker" +msgstr "" + +#: ./doc/high-availability-guide/bk-ha-guide.xml1481(simpara) +msgid "" +"You may now proceed with adding the Pacemaker configuration for Neutron DHCP" +" Agent resource. Connect to the Pacemaker cluster with crm " +"configure, and add the following cluster resources:" +msgstr "" + +#: ./doc/high-availability-guide/bk-ha-guide.xml1491(simpara) +msgid "" +"p_neutron-dhcp-agent, a resource for manage Neutron DHCP " +"Agent service" +msgstr "" + +#: ./doc/high-availability-guide/bk-ha-guide.xml1499(simpara) +msgid "" +"Once completed, commit your configuration changes by entering " +"commit from the crm configure menu. " +"Pacemaker will then start the Neutron DHCP Agent service, and its dependent " +"resources, on one of your nodes." +msgstr "" + +#: ./doc/high-availability-guide/bk-ha-guide.xml1506(title) +msgid "Highly available Neutron Metadata Agent" +msgstr "" + +#: ./doc/high-availability-guide/bk-ha-guide.xml1508(simpara) +msgid "" +"Neutron Metadata agent allows Nova API Metadata to be reachable by VMs on " +"tenant networks. High Availability for the Metadata agent is achieved by " +"adopting Pacemaker." +msgstr "" + +#: ./doc/high-availability-guide/bk-ha-guide.xml1512(simpara) +msgid "" +"Here is the documentation " +"for installing Neutron Metadata Agent." +msgstr "" + +#: ./doc/high-availability-guide/bk-ha-guide.xml1516(title) +msgid "Adding Neutron Metadata Agent resource to Pacemaker" +msgstr "" + +#: ./doc/high-availability-guide/bk-ha-guide.xml1522(simpara) +msgid "" +"You may now proceed with adding the Pacemaker configuration for Neutron " +"Metadata Agent resource. Connect to the Pacemaker cluster with crm " +"configure, and add the following cluster resources:" +msgstr "" + +#: ./doc/high-availability-guide/bk-ha-guide.xml1532(simpara) +msgid "" +"p_neutron-metadata-agent, a resource for manage Neutron " +"Metadata Agent service" +msgstr "" + +#: ./doc/high-availability-guide/bk-ha-guide.xml1540(simpara) +msgid "" +"Once completed, commit your configuration changes by entering " +"commit from the crm configure menu. " +"Pacemaker will then start the Neutron Metadata Agent service, and its " +"dependent resources, on one of your nodes." +msgstr "" + +#: ./doc/high-availability-guide/bk-ha-guide.xml1547(title) +msgid "Manage network resources" +msgstr "" + +#: ./doc/high-availability-guide/bk-ha-guide.xml1549(simpara) +msgid "" +"You may now proceed with adding the Pacemaker configuration for managing all" +" network resources together with a group. Connect to the Pacemaker cluster " +"with crm configure, and add the following cluster " +"resources:" +msgstr "" + +#: ./doc/high-availability-guide/bk-ha-guide.xml1560(title) +msgid "HA Using Active/Active" +msgstr "" + +#: ./doc/high-availability-guide/bk-ha-guide.xml1564(title) +msgid "Database" +msgstr "" + +#: ./doc/high-availability-guide/bk-ha-guide.xml1566(simpara) +msgid "" +"The first step is installing the database that sits at the heart of the " +"cluster. When we’re talking about High Availability, however, we’re talking " +"about not just one database, but several (for redundancy) and a means to " +"keep them synchronized. In this case, we’re going to choose the MySQL " +"database, along with Galera for synchronous multi-master replication." +msgstr "" + +#: ./doc/high-availability-guide/bk-ha-guide.xml1571(simpara) +msgid "" +"The choice of database isn’t a foregone conclusion; you’re not required to " +"use MySQL. It is, however, a fairly common choice in OpenStack " +"installations, so we’ll cover it here." +msgstr "" + +#: ./doc/high-availability-guide/bk-ha-guide.xml1576(title) +msgid "MySQL with Galera" +msgstr "" + +#: ./doc/high-availability-guide/bk-ha-guide.xml1578(simpara) +msgid "" +"Rather than starting with a vanilla version of MySQL and then adding Galera " +"to it, you will want to install a version of MySQL patched for wsrep (Write " +"Set REPlication) from https://launchpad.net/codership-mysql/0.7. Note that the " +"installation requirements are a bit touchy; you will want to make sure to " +"read the README file so you don’t miss any steps." +msgstr "" + +#: ./doc/high-availability-guide/bk-ha-guide.xml1583(simpara) +msgid "" +"Next, download Galera itself from https://launchpad.net/galera/+download." +" Go ahead and install the *.rpms or *.debs, taking care of any dependencies " +"that your system doesn’t already have installed." +msgstr "" + +#: ./doc/high-availability-guide/bk-ha-guide.xml1586(simpara) +msgid "" +"Once you’ve completed the installation, you’ll need to make a few " +"configuration changes:" +msgstr "" + +#: ./doc/high-availability-guide/bk-ha-guide.xml1587(simpara) +msgid "" +"In the system-wide my.conf file, make sure mysqld isn’t " +"bound to 127.0.0.1, and that /etc/mysql/conf.d/ is " +"included. Typically you can find this file at " +"/etc/my.cnf:" +msgstr "" + +#: ./doc/high-availability-guide/bk-ha-guide.xml1594(simpara) +msgid "" +"When adding a new node, you must configure it with a MySQL account that can " +"access the other nodes so that it can request a state snapshot from one of " +"those existing nodes. First specify that account information in " +"/etc/mysql/conf.d/wsrep.cnf:" +msgstr "" + +#: ./doc/high-availability-guide/bk-ha-guide.xml1598(simpara) +msgid "Next connect as root and grant privileges to that user:" +msgstr "" + +#: ./doc/high-availability-guide/bk-ha-guide.xml1600(simpara) +msgid "" +"You’ll also need to remove user accounts with empty usernames, as they cause" +" problems:" +msgstr "" + +#: ./doc/high-availability-guide/bk-ha-guide.xml1602(simpara) +msgid "" +"You’ll also need to set certain mandatory configuration options within MySQL" +" itself. These include:" +msgstr "" + +#: ./doc/high-availability-guide/bk-ha-guide.xml1608(simpara) +msgid "" +"Finally, make sure that the nodes can access each other through the " +"firewall. This might mean adjusting iptables, as in:" +msgstr "" + +#: ./doc/high-availability-guide/bk-ha-guide.xml1612(simpara) +msgid "" +"It might also mean configuring any NAT firewall between nodes to allow " +"direct connections, or disabling SELinux or configuring it to allow mysqld " +"to listen to sockets at unprivileged ports." +msgstr "" + +#: ./doc/high-availability-guide/bk-ha-guide.xml1615(simpara) +msgid "Now you’re ready to actually create the cluster." +msgstr "" + +#: ./doc/high-availability-guide/bk-ha-guide.xml1618(title) +msgid "Creating the cluster" +msgstr "" + +#: ./doc/high-availability-guide/bk-ha-guide.xml1620(simpara) +msgid "" +"In creating a cluster, you first start a single instance, which creates the " +"cluster. The rest of the MySQL instances then connect to that cluster. For " +"example, if you started on 10.0.0.10 by executing the " +"command:" +msgstr "" + +#: ./doc/high-availability-guide/bk-ha-guide.xml1622(simpara) +msgid "" +"you could then connect to that cluster on the rest of the nodes by " +"referencing the address of that node, as in:" +msgstr "" + +#: ./doc/high-availability-guide/bk-ha-guide.xml1624(simpara) +msgid "" +"You also have the option to set the wsrep_cluster_address" +" in the /etc/mysql/conf.d/wsrep.cnf file, or within the " +"client itself. (In fact, for some systems, such as MariaDB or Percona, this " +"may be your only option.) For example, to check the status of the cluster, " +"open the MySQL client and check the status of the various parameters:" +msgstr "" + +#: ./doc/high-availability-guide/bk-ha-guide.xml1631(simpara) +msgid "You should see a status that looks something like this:" +msgstr "" + +#: ./doc/high-availability-guide/bk-ha-guide.xml1680(title) +msgid "Galera Monitoring Scripts" +msgstr "" + +#: ./doc/high-availability-guide/bk-ha-guide.xml1682(simpara) +msgid "(Coming soon)" +msgstr "" + +#: ./doc/high-availability-guide/bk-ha-guide.xml1686(title) +msgid "Other ways to provide a Highly Available database" +msgstr "" + +#: ./doc/high-availability-guide/bk-ha-guide.xml1688(simpara) +msgid "" +"MySQL with Galera is by no means the only way to achieve database HA. " +"MariaDB (https://mariadb.org/) " +"and Percona (http://www.percona.com/) also work " +"with Galera. You also have the option to use Postgres, which has its own " +"replication, or some other database HA option." +msgstr "" + +#: ./doc/high-availability-guide/bk-ha-guide.xml1696(title) +msgid "RabbitMQ" +msgstr "" + +#: ./doc/high-availability-guide/bk-ha-guide.xml1698(simpara) +msgid "" +"RabbitMQ is the default AMQP server used by many OpenStack services. Making " +"the RabbitMQ service highly available involves:" +msgstr "" + +#: ./doc/high-availability-guide/bk-ha-guide.xml1702(simpara) +#: ./doc/high-availability-guide/bk-ha-guide.xml1719(title) +msgid "Install RabbitMQ" +msgstr "" + +#: ./doc/high-availability-guide/bk-ha-guide.xml1707(simpara) +msgid "Configure RabbitMQ for HA queues" +msgstr "" + +#: ./doc/high-availability-guide/bk-ha-guide.xml1712(simpara) +msgid "Configure OpenStack services to use Rabbit HA queues" +msgstr "" + +#: ./doc/high-availability-guide/bk-ha-guide.xml1721(simpara) +msgid "This setup has been tested with RabbitMQ 2.7.1." +msgstr "" + +#: ./doc/high-availability-guide/bk-ha-guide.xml1724(title) +msgid "On Ubuntu / Debian" +msgstr "" + +#: ./doc/high-availability-guide/bk-ha-guide.xml1726(simpara) +#: ./doc/high-availability-guide/bk-ha-guide.xml1736(simpara) +msgid "RabbitMQ is packaged on both distros:" +msgstr "" + +#: ./doc/high-availability-guide/bk-ha-guide.xml1729(link) +msgid "Official manual for installing RabbitMQ on Ubuntu / Debian" +msgstr "" + +#: ./doc/high-availability-guide/bk-ha-guide.xml1734(title) +msgid "On Fedora / RHEL" +msgstr "" + +#: ./doc/high-availability-guide/bk-ha-guide.xml1739(link) +msgid "Official manual for installing RabbitMQ on Fedora / RHEL" +msgstr "" + +#: ./doc/high-availability-guide/bk-ha-guide.xml1745(title) +msgid "Configure RabbitMQ" +msgstr "" + +#: ./doc/high-availability-guide/bk-ha-guide.xml1747(simpara) +msgid "" +"Here we are building a cluster of RabbitMQ nodes to construct a RabbitMQ " +"broker. Mirrored queues in RabbitMQ improve the availability of service " +"since it will be resilient to failures, but we have to consider that while " +"exchanges and bindings will survive the loss of individual nodes, queues and" +" their messages will no because a queue and its contents is located on one " +"node. So if we lose this node, we also lose the queue." +msgstr "" + +#: ./doc/high-availability-guide/bk-ha-guide.xml1752(simpara) +msgid "" +"We consider that we run (at least) two RabbitMQ servers. To build a broker, " +"we need to ensure that all nodes have the same erlang cookie file. To do so," +" stop RabbitMQ everywhere and copy the cookie from rabbit1 server to other " +"server(s):" +msgstr "" + +#: ./doc/high-availability-guide/bk-ha-guide.xml1757(simpara) +msgid "" +"Then, start RabbitMQ on nodes. If RabbitMQ fails to start, you can’t " +"continue to the next step." +msgstr "" + +#: ./doc/high-availability-guide/bk-ha-guide.xml1759(simpara) +msgid "Now, we are building the HA cluster. From rabbit2, run these commands:" +msgstr "" + +#: ./doc/high-availability-guide/bk-ha-guide.xml1763(simpara) +msgid "To verify the cluster status :" +msgstr "" + +#: ./doc/high-availability-guide/bk-ha-guide.xml1768(simpara) +msgid "" +"If the cluster is working, you can now proceed to creating users and " +"password for queues." +msgstr "" + +#: ./doc/high-availability-guide/bk-ha-guide.xml1770(emphasis) +msgid "Note for RabbitMQ version 3" +msgstr "" + +#: ./doc/high-availability-guide/bk-ha-guide.xml1772(simpara) +msgid "" +"Queue mirroring is no longer controlled by the x-ha-" +"policy argument when declaring a queue. OpenStack can continue to" +" declare this argument, but it won’t cause queues to be mirrored. We need to" +" make sure that all queues (except those with auto-generated names) are " +"mirrored across all nodes in running:" +msgstr "" + +#: ./doc/high-availability-guide/bk-ha-guide.xml1777(link) +msgid "More informations about High availability in RabbitMQ" +msgstr "" + +#: ./doc/high-availability-guide/bk-ha-guide.xml1782(title) +msgid "Configure OpenStack Services to use RabbitMQ" +msgstr "" + +#: ./doc/high-availability-guide/bk-ha-guide.xml1784(simpara) +msgid "" +"Since Grizzly Release, most of OpenStack components using queuing has been " +"supported the feature, we have to configure them to use at least two " +"RabbitMQ nodes." +msgstr "" + +#: ./doc/high-availability-guide/bk-ha-guide.xml1786(simpara) +msgid "Do this configuration on all services using RabbitMQ:" +msgstr "" + +#: ./doc/high-availability-guide/bk-ha-guide.xml1787(simpara) +msgid "RabbitMQ HA cluster host:port pairs:" +msgstr "" + +#: ./doc/high-availability-guide/bk-ha-guide.xml1789(simpara) +msgid "How frequently to retry connecting with RabbitMQ:" +msgstr "" + +#: ./doc/high-availability-guide/bk-ha-guide.xml1791(simpara) +msgid "How long to backoff for between retries when connecting to RabbitMQ:" +msgstr "" + +#: ./doc/high-availability-guide/bk-ha-guide.xml1793(simpara) +msgid "" +"Maximum retries with trying to connect to RabbitMQ (infinite by default):" +msgstr "" + +#: ./doc/high-availability-guide/bk-ha-guide.xml1795(simpara) +msgid "Use durable queues in RabbitMQ:" +msgstr "" + +#: ./doc/high-availability-guide/bk-ha-guide.xml1797(simpara) +msgid "Use H/A queues in RabbitMQ (x-ha-policy: all):" +msgstr "" + +#: ./doc/high-availability-guide/bk-ha-guide.xml1799(simpara) +msgid "" +"If you change the configuration from an old setup which did not use HA " +"queues, you should interrupt the service :" +msgstr "" + +#: ./doc/high-availability-guide/bk-ha-guide.xml1803(simpara) +msgid "" +"Services currently working with HA queues : OpenStack Compute, Cinder, " +"OpenStack Networking, Ceilometer." +msgstr "" + +#: ./doc/high-availability-guide/bk-ha-guide.xml1808(title) +msgid "HAproxy Nodes" +msgstr "" + +#: ./doc/high-availability-guide/bk-ha-guide.xml1810(simpara) +msgid "" +"HAProxy is a very fast and reliable solution offering high availability, " +"load balancing, and proxying for TCP and HTTP-based applications. It is " +"particularly suited for web sites crawling under very high loads while " +"needing persistence or Layer 7 processing. Supporting tens of thousands of " +"connections is clearly realistic with today’s hardware." +msgstr "" + +#: ./doc/high-availability-guide/bk-ha-guide.xml1814(simpara) +msgid "" +"For installing HAproxy on your nodes, you should consider its official documentation. Also, " +"you have to consider that this service should not be a single point of " +"failure, so you need at least two nodes running HAproxy." +msgstr "" + +#: ./doc/high-availability-guide/bk-ha-guide.xml1817(simpara) +msgid "Here is an example for HAproxy configuration file:" +msgstr "" + +#: ./doc/high-availability-guide/bk-ha-guide.xml1957(simpara) +msgid "After each change of this file, you should restart HAproxy." +msgstr "" + +#: ./doc/high-availability-guide/bk-ha-guide.xml1961(title) +msgid "OpenStack Controller Nodes" +msgstr "" + +#: ./doc/high-availability-guide/bk-ha-guide.xml1963(simpara) +msgid "OpenStack Controller Nodes contains:" +msgstr "" + +#: ./doc/high-availability-guide/bk-ha-guide.xml1966(simpara) +msgid "All OpenStack API services" +msgstr "" + +#: ./doc/high-availability-guide/bk-ha-guide.xml1971(simpara) +msgid "All OpenStack schedulers" +msgstr "" + +#: ./doc/high-availability-guide/bk-ha-guide.xml1976(simpara) +msgid "Memcached service" +msgstr "" + +#: ./doc/high-availability-guide/bk-ha-guide.xml1983(title) +msgid "Running OpenStack API & schedulers" +msgstr "" + +#: ./doc/high-availability-guide/bk-ha-guide.xml1987(title) +msgid "API Services" +msgstr "" + +#: ./doc/high-availability-guide/bk-ha-guide.xml1989(simpara) +msgid "" +"All OpenStack projects have an API service for controlling all the resources" +" in the Cloud. In Active / Active mode, the most common setup is to scale-" +"out these services on at least two nodes and use load-balancing and virtual " +"IP (with HAproxy & Keepalived in this setup)." +msgstr "" + +#: ./doc/high-availability-guide/bk-ha-guide.xml1993(emphasis) +msgid "Configuring API OpenStack services" +msgstr "" + +#: ./doc/high-availability-guide/bk-ha-guide.xml1995(simpara) +msgid "" +"To configure our Cloud using Highly available and scalable API services, we " +"need to ensure that:" +msgstr "" + +#: ./doc/high-availability-guide/bk-ha-guide.xml1998(simpara) +msgid "Using Virtual IP when configuring OpenStack Identity Endpoints." +msgstr "" + +#: ./doc/high-availability-guide/bk-ha-guide.xml2003(simpara) +msgid "All OpenStack configuration files should refer to Virtual IP." +msgstr "" + +#: ./doc/high-availability-guide/bk-ha-guide.xml2009(emphasis) +msgid "In case of failure" +msgstr "" + +#: ./doc/high-availability-guide/bk-ha-guide.xml2011(simpara) +msgid "" +"The monitor check is quite simple since it just establishes a TCP connection" +" to the API port. Comparing to the Active / Passive mode using Corosync " +"& Resources Agents, we don’t check if the service is actually running). " +"That’s why all OpenStack API should be monitored by another tool (i.e. " +"Nagios) with the goal to detect failures in the Cloud Framework " +"infrastructure." +msgstr "" + +#: ./doc/high-availability-guide/bk-ha-guide.xml2018(title) +msgid "Schedulers" +msgstr "" + +#: ./doc/high-availability-guide/bk-ha-guide.xml2020(simpara) +msgid "" +"OpenStack schedulers are used to determine how to dispatch compute, network " +"and volume requests. The most common setup is to use RabbitMQ as messaging " +"system already documented in this guide. Those services are connected to the" +" messaging backend and can scale-out :" +msgstr "" + +#: ./doc/high-availability-guide/bk-ha-guide.xml2025(simpara) +msgid "nova-scheduler" +msgstr "" + +#: ./doc/high-availability-guide/bk-ha-guide.xml2030(simpara) +msgid "nova-conductor" +msgstr "" + +#: ./doc/high-availability-guide/bk-ha-guide.xml2035(simpara) +msgid "cinder-scheduler" +msgstr "" + +#: ./doc/high-availability-guide/bk-ha-guide.xml2040(simpara) +msgid "neutron-server" +msgstr "" + +#: ./doc/high-availability-guide/bk-ha-guide.xml2045(simpara) +msgid "ceilometer-collector" +msgstr "" + +#: ./doc/high-availability-guide/bk-ha-guide.xml2050(simpara) +msgid "heat-engine" +msgstr "" + +#: ./doc/high-availability-guide/bk-ha-guide.xml2055(simpara) +msgid "" +"Please refer to the RabbitMQ section for configure these services with " +"multiple messaging servers." +msgstr "" + +#: ./doc/high-availability-guide/bk-ha-guide.xml2060(title) +msgid "Memcached" +msgstr "" + +#: ./doc/high-availability-guide/bk-ha-guide.xml2062(simpara) +msgid "" +"Most of OpenStack services use an application to offer persistence and store" +" ephemeral datas (like tokens). Memcached is one of them and can scale-out " +"easily without specific trick." +msgstr "" + +#: ./doc/high-availability-guide/bk-ha-guide.xml2064(simpara) +msgid "" +"To install and configure it, you can read the official " +"documentation." +msgstr "" + +#: ./doc/high-availability-guide/bk-ha-guide.xml2065(simpara) +msgid "" +"Memory caching is managed by Oslo-incubator for so the way to use multiple " +"memcached servers is the same for all projects." +msgstr "" + +#: ./doc/high-availability-guide/bk-ha-guide.xml2066(simpara) +msgid "Example with two hosts:" +msgstr "" + +#: ./doc/high-availability-guide/bk-ha-guide.xml2068(simpara) +msgid "" +"By default, controller1 will handle the caching service but if the host goes" +" down, controller2 will do the job. More informations about memcached " +"installation are in the OpenStack Compute Manual." +msgstr "" + +#: ./doc/high-availability-guide/bk-ha-guide.xml2074(title) +msgid "OpenStack Network Nodes" +msgstr "" + +#: ./doc/high-availability-guide/bk-ha-guide.xml2076(simpara) +msgid "OpenStack Network Nodes contains:" +msgstr "" + +#: ./doc/high-availability-guide/bk-ha-guide.xml2079(simpara) +msgid "Neutron DHCP Agent" +msgstr "" + +#: ./doc/high-availability-guide/bk-ha-guide.xml2084(simpara) +msgid "Neutron L2 Agent" +msgstr "" + +#: ./doc/high-availability-guide/bk-ha-guide.xml2089(simpara) +msgid "Neutron L3 Agent" +msgstr "" + +#: ./doc/high-availability-guide/bk-ha-guide.xml2094(simpara) +msgid "Neutron Metadata Agent" +msgstr "" + +#: ./doc/high-availability-guide/bk-ha-guide.xml2099(simpara) +msgid "Neutron LBaaS Agent" +msgstr "" + +#: ./doc/high-availability-guide/bk-ha-guide.xml2105(simpara) +msgid "" +"The Neutron L2 Agent does not need to be highly available. It has to be " +"installed on each Data Forwarding Node and controls the virtual networking " +"drivers as Open-vSwitch or Linux Bridge. One L2 agent runs per node and " +"controls its virtual interfaces. That’s why it cannot be distributed and " +"highly available." +msgstr "" + +#: ./doc/high-availability-guide/bk-ha-guide.xml2113(title) +msgid "Running Neutron DHCP Agent" +msgstr "" + +#: ./doc/high-availability-guide/bk-ha-guide.xml2115(simpara) +msgid "" +"Since the Grizzly release, OpenStack Networking service has a scheduler that" +" lets you run multiple agents across nodes. Also, the DHCP agent can be " +"natively highly available. For details, see OpenStack Configuration " +"Reference." +msgstr "" + +#: ./doc/high-availability-guide/bk-ha-guide.xml2121(title) +msgid "Running Neutron L3 Agent" +msgstr "" + +#: ./doc/high-availability-guide/bk-ha-guide.xml2123(simpara) +msgid "" +"Since the Grizzly release, the Neutron L3 Agent is scalable thanks to the " +"scheduler that allows distribution of virtual routers across multiple nodes." +" But there is no native feature to make these routers highly available. At " +"this time, the Active / Passive solution exists to run the Neutron L3 agent " +"in failover mode with Pacemaker. See the Active / Passive section of this " +"guide." +msgstr "" + +#: ./doc/high-availability-guide/bk-ha-guide.xml2132(title) +msgid "Running Neutron Metadata Agent" +msgstr "" + +#: ./doc/high-availability-guide/bk-ha-guide.xml2134(simpara) +msgid "" +"There is no native feature to make this service highly available. At this " +"time, the Active / Passive solution exists to run the Neutron Metadata agent" +" in failover mode with Pacemaker. See the Active / Passive section of this " +"guide." +msgstr "" + +#. Put one translator per line, in the form of NAME , YEAR1, YEAR2 +#: ./doc/high-availability-guide/bk-ha-guide.xml0(None) +msgid "translator-credits" +msgstr "" diff --git a/doc/high-availability-guide/locale/high-availability-guide.pot b/doc/high-availability-guide/locale/high-availability-guide.pot new file mode 100644 index 0000000000..bdc6d75ed5 --- /dev/null +++ b/doc/high-availability-guide/locale/high-availability-guide.pot @@ -0,0 +1,1540 @@ +msgid "" +msgstr "" +"Project-Id-Version: PACKAGE VERSION\n" +"POT-Creation-Date: 2014-01-30 06:24+0000\n" +"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n" +"Last-Translator: FULL NAME \n" +"Language-Team: LANGUAGE \n" +"MIME-Version: 1.0\n" +"Content-Type: text/plain; charset=UTF-8\n" +"Content-Transfer-Encoding: 8bit\n" + +#: ./doc/high-availability-guide/ha-guide-docinfo.xml:4(firstname) ./doc/high-availability-guide/bk-ha-guide.xml:8(firstname) +msgid "Florian" +msgstr "" + +#: ./doc/high-availability-guide/ha-guide-docinfo.xml:5(surname) ./doc/high-availability-guide/bk-ha-guide.xml:9(surname) +msgid "Haas" +msgstr "" + +#: ./doc/high-availability-guide/ha-guide-docinfo.xml:7(email) ./doc/high-availability-guide/bk-ha-guide.xml:11(email) +msgid "florian@hastexo.com" +msgstr "" + +#: ./doc/high-availability-guide/ha-guide-docinfo.xml:9(orgname) ./doc/high-availability-guide/bk-ha-guide.xml:13(orgname) +msgid "hastexo" +msgstr "" + +#: ./doc/high-availability-guide/bk-ha-guide.xml:5(title) +msgid "OpenStack High Availability Guide" +msgstr "" + +#: ./doc/high-availability-guide/bk-ha-guide.xml:17(year) +msgid "2012" +msgstr "" + +#: ./doc/high-availability-guide/bk-ha-guide.xml:18(year) +msgid "2013" +msgstr "" + +#: ./doc/high-availability-guide/bk-ha-guide.xml:19(holder) +msgid "OpenStack Contributors" +msgstr "" + +#: ./doc/high-availability-guide/bk-ha-guide.xml:21(releaseinfo) +msgid "master" +msgstr "" + +#: ./doc/high-availability-guide/bk-ha-guide.xml:22(productname) +msgid "OpenStack" +msgstr "" + +#: ./doc/high-availability-guide/bk-ha-guide.xml:26(remark) +msgid "Copyright details are filled in by the template." +msgstr "" + +#: ./doc/high-availability-guide/bk-ha-guide.xml:31(date) +msgid "2012-01-16" +msgstr "" + +#: ./doc/high-availability-guide/bk-ha-guide.xml:35(para) +msgid "Organizes guide based on cloud controller and compute nodes." +msgstr "" + +#: ./doc/high-availability-guide/bk-ha-guide.xml:41(date) +msgid "2012-05-24" +msgstr "" + +#: ./doc/high-availability-guide/bk-ha-guide.xml:45(para) +msgid "Begin trunk designation." +msgstr "" + +#: ./doc/high-availability-guide/bk-ha-guide.xml:54(title) +msgid "Introduction to OpenStack High Availability" +msgstr "" + +#: ./doc/high-availability-guide/bk-ha-guide.xml:56(simpara) +msgid "High Availability systems seek to minimize two things:" +msgstr "" + +#: ./doc/high-availability-guide/bk-ha-guide.xml:59(simpara) +msgid "System downtime — occurs when a user-facing service is unavailable beyond a specified maximum amount of time, and" +msgstr "" + +#: ./doc/high-availability-guide/bk-ha-guide.xml:63(simpara) +msgid "Data loss — accidental deletion or destruction of data." +msgstr "" + +#: ./doc/high-availability-guide/bk-ha-guide.xml:67(simpara) +msgid "Most high availability systems guarantee protection against system downtime and data loss only in the event of a single failure. However, they are also expected to protect against cascading failures, where a single failure deteriorates into a series of consequential failures." +msgstr "" + +#: ./doc/high-availability-guide/bk-ha-guide.xml:68(simpara) +msgid "A crucial aspect of high availability is the elimination of single points of failure (SPOFs). A SPOF is an individual piece of equipment or software which will cause system downtime or data loss if it fails. In order to eliminate SPOFs, check that mechanisms exist for redundancy of:" +msgstr "" + +#: ./doc/high-availability-guide/bk-ha-guide.xml:71(simpara) +msgid "Network components, such as switches and routers" +msgstr "" + +#: ./doc/high-availability-guide/bk-ha-guide.xml:76(simpara) +msgid "Applications and automatic service migration" +msgstr "" + +#: ./doc/high-availability-guide/bk-ha-guide.xml:81(simpara) +msgid "Storage components" +msgstr "" + +#: ./doc/high-availability-guide/bk-ha-guide.xml:86(simpara) +msgid "Facility services such as power, air conditioning, and fire protection" +msgstr "" + +#: ./doc/high-availability-guide/bk-ha-guide.xml:91(simpara) +msgid "Most high availability systems will fail in the event of multiple independent (non-consequential) failures. In this case, most systems will protect data over maintaining availability." +msgstr "" + +#: ./doc/high-availability-guide/bk-ha-guide.xml:92(simpara) +msgid "High-availability systems typically achieve uptime of 99.99% or more, which roughly equates to less than an hour of cumulative downtime per year. In order to achieve this, high availability systems should keep recovery times after a failure to about one to two minutes, sometimes significantly less." +msgstr "" + +#: ./doc/high-availability-guide/bk-ha-guide.xml:93(simpara) +msgid "OpenStack currently meets such availability requirements for its own infrastructure services, meaning that an uptime of 99.99% is feasible for the OpenStack infrastructure proper. However, OpenStack doesnot guarantee 99.99% availability for individual guest instances." +msgstr "" + +#: ./doc/high-availability-guide/bk-ha-guide.xml:94(simpara) +msgid "Preventing single points of failure can depend on whether or not a service is stateless." +msgstr "" + +#: ./doc/high-availability-guide/bk-ha-guide.xml:97(title) +msgid "Stateless vs. Stateful services" +msgstr "" + +#: ./doc/high-availability-guide/bk-ha-guide.xml:99(simpara) +msgid "A stateless service is one that provides a response after your request, and then requires no further attention. To make a stateless service highly available, you need to provide redundant instances and load balance them. OpenStack services that are stateless include nova-api, nova-conductor, glance-api, keystone-api, neutron-api and nova-scheduler." +msgstr "" + +#: ./doc/high-availability-guide/bk-ha-guide.xml:100(simpara) +msgid "A stateful service is one where subsequent requests to the service depend on the results of the first request. Stateful services are more difficult to manage because a single action typically involves more than one request, so simply providing additional instances and load balancing will not solve the problem. For example, if the Horizon user interface reset itself every time you went to a new page, it wouldn’t be very useful. OpenStack services that are stateful include the OpenStack database and message queue." +msgstr "" + +#: ./doc/high-availability-guide/bk-ha-guide.xml:101(simpara) +msgid "Making stateful services highly available can depend on whether you choose an active/passive or active/active configuration." +msgstr "" + +#: ./doc/high-availability-guide/bk-ha-guide.xml:105(title) +msgid "Active/Passive" +msgstr "" + +#: ./doc/high-availability-guide/bk-ha-guide.xml:107(simpara) +msgid "In an active/passive configuration, systems are set up to bring additional resources online to replace those that have failed. For example, OpenStack would write to the main database while maintaining a disaster recovery database that can be brought online in the event that the main database fails." +msgstr "" + +#: ./doc/high-availability-guide/bk-ha-guide.xml:108(simpara) +msgid "Typically, an active/passive installation for a stateless service would maintain a redundant instance that can be brought online when required. Requests are load balanced using a virtual IP address and a load balancer such as HAProxy." +msgstr "" + +#: ./doc/high-availability-guide/bk-ha-guide.xml:109(simpara) +msgid "A typical active/passive installation for a stateful service maintains a replacement resource that can be brought online when required. A separate application (such as Pacemaker or Corosync) monitors these services, bringing the backup online as necessary." +msgstr "" + +#: ./doc/high-availability-guide/bk-ha-guide.xml:113(title) +msgid "Active/Active" +msgstr "" + +#: ./doc/high-availability-guide/bk-ha-guide.xml:115(simpara) +msgid "In an active/active configuration, systems also use a backup but will manage both the main and redundant systems concurrently. This way, if there is a failure the user is unlikely to notice. The backup system is already online, and takes on increased load while the main system is fixed and brought back online." +msgstr "" + +#: ./doc/high-availability-guide/bk-ha-guide.xml:116(simpara) +msgid "Typically, an active/active installation for a stateless service would maintain a redundant instance, and requests are load balanced using a virtual IP address and a load balancer such as HAProxy." +msgstr "" + +#: ./doc/high-availability-guide/bk-ha-guide.xml:117(simpara) +msgid "A typical active/active installation for a stateful service would include redundant services with all instances having an identical state. For example, updates to one instance of a database would also update all other instances. This way a request to one instance is the same as a request to any other. A load balancer manages the traffic to these systems, ensuring that operational systems always handle the request." +msgstr "" + +#: ./doc/high-availability-guide/bk-ha-guide.xml:118(simpara) +msgid "These are some of the more common ways to implement these high availability architectures, but they are by no means the only ways to do it. The important thing is to make sure that your services are redundant, and available; how you achieve that is up to you. This document will cover some of the more common options for highly available systems." +msgstr "" + +#: ./doc/high-availability-guide/bk-ha-guide.xml:123(title) +msgid "HA Using Active/Passive" +msgstr "" + +#: ./doc/high-availability-guide/bk-ha-guide.xml:127(title) +msgid "The Pacemaker Cluster Stack" +msgstr "" + +#: ./doc/high-availability-guide/bk-ha-guide.xml:129(simpara) +msgid "OpenStack infrastructure high availability relies on the Pacemaker cluster stack, the state-of-the-art high availability and load balancing stack for the Linux platform. Pacemaker is storage- and application-agnostic, and is in no way specific to OpenStack." +msgstr "" + +#: ./doc/high-availability-guide/bk-ha-guide.xml:134(simpara) +msgid "Pacemaker relies on the Corosync messaging layer for reliable cluster communications. Corosync implements the Totem single-ring ordering and membership protocol and provides UDP and InfiniBand based messaging, quorum, and cluster membership to Pacemaker." +msgstr "" + +#: ./doc/high-availability-guide/bk-ha-guide.xml:139(simpara) +msgid "Pacemaker interacts with applications through resource agents (RAs), of which it supports over 70 natively. Pacemaker can also easily use third-party RAs. An OpenStack high-availability configuration uses existing native Pacemaker RAs (such as those managing MySQL databases or virtual IP addresses), existing third-party RAs (such as for RabbitMQ), and native OpenStack RAs (such as those managing the OpenStack Identity and Image Services)." +msgstr "" + +#: ./doc/high-availability-guide/bk-ha-guide.xml:148(title) +msgid "Installing Packages" +msgstr "" + +#: ./doc/high-availability-guide/bk-ha-guide.xml:150(simpara) +msgid "On any host that is meant to be part of a Pacemaker cluster, you must first establish cluster communications through the Corosync messaging layer. This involves installing the following packages (and their dependencies, which your package manager will normally install automatically):" +msgstr "" + +#: ./doc/high-availability-guide/bk-ha-guide.xml:158(literal) +msgid "pacemaker" +msgstr "" + +#: ./doc/high-availability-guide/bk-ha-guide.xml:163(literal) +msgid "corosync" +msgstr "" + +#: ./doc/high-availability-guide/bk-ha-guide.xml:168(literal) +msgid "cluster-glue" +msgstr "" + +#: ./doc/high-availability-guide/bk-ha-guide.xml:172(simpara) +msgid "fence-agents (Fedora only; all other distributions use fencing agents from cluster-glue)" +msgstr "" + +#: ./doc/high-availability-guide/bk-ha-guide.xml:178(literal) +msgid "resource-agents" +msgstr "" + +#: ./doc/high-availability-guide/bk-ha-guide.xml:185(title) +msgid "Setting up Corosync" +msgstr "" + +#: ./doc/high-availability-guide/bk-ha-guide.xml:187(simpara) +msgid "Besides installing the corosync package, you will also have to create a configuration file, stored in /etc/corosync/corosync.conf. Most distributions ship an example configuration file (corosync.conf.example) as part of the documentation bundled with the corosync package. An example Corosync configuration file is shown below:" +msgstr "" + +#: ./doc/high-availability-guide/bk-ha-guide.xml:195(title) +msgid "Corosync configuration file (corosync.conf)" +msgstr "" + +#: ./doc/high-availability-guide/bk-ha-guide.xml:269(para) +msgid "The token value specifies the time, in milliseconds, during which the Corosync token is expected to be transmitted around the ring. When this timeout expires, the token is declared lost, and after token_retransmits_before_loss_const lost tokens the non-responding processor (cluster node) is declared dead. In other words, token × token_retransmits_before_loss_const is the maximum time a node is allowed to not respond to cluster messages before being considered dead. The default for token is 1000 (1 second), with 4 allowed retransmits. These defaults are intended to minimize failover times, but can cause frequent \"false alarms\" and unintended failovers in case of short network interruptions. The values used here are safer, albeit with slightly extended failover times." +msgstr "" + +#: ./doc/high-availability-guide/bk-ha-guide.xml:285(para) +msgid "With secauth enabled, Corosync nodes mutually authenticate using a 128-byte shared secret stored in /etc/corosync/authkey, which may be generated with the corosync-keygen utility. When using secauth, cluster communications are also encrypted." +msgstr "" + +#: ./doc/high-availability-guide/bk-ha-guide.xml:293(para) +msgid "In Corosync configurations using redundant networking (with more than one interface), you must select a Redundant Ring Protocol (RRP) mode other than none. active is the recommended RRP mode." +msgstr "" + +#: ./doc/high-availability-guide/bk-ha-guide.xml:300(para) +msgid "There are several things to note about the recommended interface configuration:" +msgstr "" + +#: ./doc/high-availability-guide/bk-ha-guide.xml:306(simpara) +msgid "The ringnumber must differ between all configured interfaces, starting with 0." +msgstr "" + +#: ./doc/high-availability-guide/bk-ha-guide.xml:312(simpara) +msgid "The bindnetaddr is the network address of the interfaces to bind to. The example uses two network addresses of /24 IPv4 subnets." +msgstr "" + +#: ./doc/high-availability-guide/bk-ha-guide.xml:318(simpara) +msgid "Multicast groups (mcastaddr) must not be reused across cluster boundaries. In other words, no two distinct clusters should ever use the same multicast group. Be sure to select multicast addresses compliant with RFC 2365, \"Administratively Scoped IP Multicast\"." +msgstr "" + +#: ./doc/high-availability-guide/bk-ha-guide.xml:327(simpara) +msgid "For firewall configurations, note that Corosync communicates over UDP only, and uses mcastport (for receives) and mcastport-1 (for sends)." +msgstr "" + +#: ./doc/high-availability-guide/bk-ha-guide.xml:336(para) +msgid "The service declaration for the pacemaker service may be placed in the corosync.conf file directly, or in its own separate file, /etc/corosync/service.d/pacemaker." +msgstr "" + +#: ./doc/high-availability-guide/bk-ha-guide.xml:343(simpara) +msgid "Once created, the corosync.conf file (and the authkey file if the secauth option is enabled) must be synchronized across all cluster nodes." +msgstr "" + +#: ./doc/high-availability-guide/bk-ha-guide.xml:349(title) +msgid "Starting Corosync" +msgstr "" + +#: ./doc/high-availability-guide/bk-ha-guide.xml:351(simpara) +msgid "Corosync is started as a regular system service. Depending on your distribution, it may ship with a LSB (System V style) init script, an upstart job, or a systemd unit file. Either way, the service is usually named corosync:" +msgstr "" + +#: ./doc/high-availability-guide/bk-ha-guide.xml:357(simpara) +msgid "/etc/init.d/corosync start (LSB)" +msgstr "" + +#: ./doc/high-availability-guide/bk-ha-guide.xml:361(simpara) +msgid "service corosync start (LSB, alternate)" +msgstr "" + +#: ./doc/high-availability-guide/bk-ha-guide.xml:365(simpara) +msgid "start corosync (upstart)" +msgstr "" + +#: ./doc/high-availability-guide/bk-ha-guide.xml:369(simpara) +msgid "systemctl start corosync (systemd)" +msgstr "" + +#: ./doc/high-availability-guide/bk-ha-guide.xml:373(simpara) +msgid "You can now check Corosync connectivity with two tools." +msgstr "" + +#: ./doc/high-availability-guide/bk-ha-guide.xml:374(simpara) +msgid "The corosync-cfgtool utility, when invoked with the -s option, gives a summary of the health of the communication rings:" +msgstr "" + +#: ./doc/high-availability-guide/bk-ha-guide.xml:385(simpara) +msgid "The corosync-objctl utility can be used to dump the Corosync cluster member list:" +msgstr "" + +#: ./doc/high-availability-guide/bk-ha-guide.xml:394(simpara) +msgid "You should see a status=joined entry for each of your constituent cluster nodes." +msgstr "" + +#: ./doc/high-availability-guide/bk-ha-guide.xml:399(title) +msgid "Starting Pacemaker" +msgstr "" + +#: ./doc/high-availability-guide/bk-ha-guide.xml:401(simpara) +msgid "Once the Corosync services have been started, and you have established that the cluster is communicating properly, it is safe to start pacemakerd, the Pacemaker master control process:" +msgstr "" + +#: ./doc/high-availability-guide/bk-ha-guide.xml:406(simpara) +msgid "/etc/init.d/pacemaker start (LSB)" +msgstr "" + +#: ./doc/high-availability-guide/bk-ha-guide.xml:410(simpara) +msgid "service pacemaker start (LSB, alternate)" +msgstr "" + +#: ./doc/high-availability-guide/bk-ha-guide.xml:414(simpara) +msgid "start pacemaker (upstart)" +msgstr "" + +#: ./doc/high-availability-guide/bk-ha-guide.xml:418(simpara) +msgid "systemctl start pacemaker (systemd)" +msgstr "" + +#: ./doc/high-availability-guide/bk-ha-guide.xml:422(simpara) +msgid "Once Pacemaker services have started, Pacemaker will create an default empty cluster configuration with no resources. You may observe Pacemaker’s status with the crm_mon utility:" +msgstr "" + +#: ./doc/high-availability-guide/bk-ha-guide.xml:439(title) +msgid "Setting basic cluster properties" +msgstr "" + +#: ./doc/high-availability-guide/bk-ha-guide.xml:441(simpara) +msgid "Once your Pacemaker cluster is set up, it is recommended to set a few basic cluster properties. To do so, start the crm shell and change into the configuration menu by entering configure. Alternatively. you may jump straight into the Pacemaker configuration menu by typing crm configure directly from a shell prompt." +msgstr "" + +#: ./doc/high-availability-guide/bk-ha-guide.xml:447(simpara) +msgid "Then, set the following properties:" +msgstr "" + +#: ./doc/high-availability-guide/bk-ha-guide.xml:455(para) +msgid "Setting no-quorum-policy=\"ignore\" is required in 2-node Pacemaker clusters for the following reason: if quorum enforcement is enabled, and one of the two nodes fails, then the remaining node can not establish a majority of quorum votes necessary to run services, and thus it is unable to take over any resources. The appropriate workaround is to ignore loss of quorum in the cluster. This is safe and necessary only in 2-node clusters. Do not set this property in Pacemaker clusters with more than two nodes." +msgstr "" + +#: ./doc/high-availability-guide/bk-ha-guide.xml:467(para) +msgid "Setting pe-warn-series-max, pe-input-series-max and pe-error-series-max to 1000 instructs Pacemaker to keep a longer history of the inputs processed, and errors and warnings generated, by its Policy Engine. This history is typically useful in case cluster troubleshooting becomes necessary." +msgstr "" + +#: ./doc/high-availability-guide/bk-ha-guide.xml:476(para) +msgid "Pacemaker uses an event-driven approach to cluster state processing. However, certain Pacemaker actions occur at a configurable interval, cluster-recheck-interval, which defaults to 15 minutes. It is usually prudent to reduce this to a shorter interval, such as 5 or 3 minutes." +msgstr "" + +#: ./doc/high-availability-guide/bk-ha-guide.xml:485(simpara) +msgid "Once you have made these changes, you may commit the updated configuration." +msgstr "" + +#: ./doc/high-availability-guide/bk-ha-guide.xml:491(title) +msgid "Cloud Controller Cluster Stack" +msgstr "" + +#: ./doc/high-availability-guide/bk-ha-guide.xml:493(simpara) +msgid "The Cloud Controller sits on the management network and needs to talk to all other services." +msgstr "" + +#: ./doc/high-availability-guide/bk-ha-guide.xml:496(title) +msgid "Highly available MySQL" +msgstr "" + +#: ./doc/high-availability-guide/bk-ha-guide.xml:498(simpara) +msgid "MySQL is the default database server used by many OpenStack services. Making the MySQL service highly available involves" +msgstr "" + +#: ./doc/high-availability-guide/bk-ha-guide.xml:502(simpara) +msgid "configuring a DRBD device for use by MySQL," +msgstr "" + +#: ./doc/high-availability-guide/bk-ha-guide.xml:507(simpara) +msgid "configuring MySQL to use a data directory residing on that DRBD device," +msgstr "" + +#: ./doc/high-availability-guide/bk-ha-guide.xml:513(simpara) ./doc/high-availability-guide/bk-ha-guide.xml:759(simpara) +msgid "selecting and assigning a virtual IP address (VIP) that can freely float between cluster nodes," +msgstr "" + +#: ./doc/high-availability-guide/bk-ha-guide.xml:519(simpara) +msgid "configuring MySQL to listen on that IP address," +msgstr "" + +#: ./doc/high-availability-guide/bk-ha-guide.xml:524(simpara) +msgid "managing all resources, including the MySQL daemon itself, with the Pacemaker cluster manager." +msgstr "" + +#: ./doc/high-availability-guide/bk-ha-guide.xml:531(simpara) +msgid "MySQL/Galera is an alternative method of configuring MySQL for high availability. It is likely to become the preferred method of achieving MySQL high availability once it has sufficiently matured. At the time of writing, however, the Pacemaker/DRBD based approach remains the recommended one for OpenStack environments." +msgstr "" + +#: ./doc/high-availability-guide/bk-ha-guide.xml:540(title) ./doc/high-availability-guide/bk-ha-guide.xml:789(title) +msgid "Configuring DRBD" +msgstr "" + +#: ./doc/high-availability-guide/bk-ha-guide.xml:542(simpara) +msgid "The Pacemaker based MySQL server requires a DRBD resource from which it mounts the /var/lib/mysql directory. In this example, the DRBD resource is simply named mysql:" +msgstr "" + +#: ./doc/high-availability-guide/bk-ha-guide.xml:547(title) +msgid "mysql DRBD resource configuration (/etc/drbd.d/mysql.res)" +msgstr "" + +#: ./doc/high-availability-guide/bk-ha-guide.xml:563(simpara) +msgid "This resource uses an underlying local disk (in DRBD terminology, a backing device) named /dev/data/mysql on both cluster nodes, node1 and node2. Normally, this would be an LVM Logical Volume specifically set aside for this purpose. The DRBD meta-disk is internal, meaning DRBD-specific metadata is being stored at the end of the disk device itself. The device is configured to communicate between IPv4 addresses 10.0.42.100 and 10.0.42.254, using TCP port 7700. Once enabled, it will map to a local DRBD block device with the device minor number 0, that is, /dev/drbd0." +msgstr "" + +#: ./doc/high-availability-guide/bk-ha-guide.xml:572(simpara) ./doc/high-availability-guide/bk-ha-guide.xml:821(simpara) +msgid "Enabling a DRBD resource is explained in detail in the DRBD User’s Guide. In brief, the proper sequence of commands is this:" +msgstr "" + +#: ./doc/high-availability-guide/bk-ha-guide.xml:580(para) +msgid "Initializes DRBD metadata and writes the initial set of metadata to /dev/data/mysql. Must be completed on both nodes." +msgstr "" + +#: ./doc/high-availability-guide/bk-ha-guide.xml:586(para) +msgid "Creates the /dev/drbd0 device node, attaches the DRBD device to its backing store, and connects the DRBD node to its peer. Must be completed on both nodes." +msgstr "" + +#: ./doc/high-availability-guide/bk-ha-guide.xml:593(para) ./doc/high-availability-guide/bk-ha-guide.xml:842(para) +msgid "Kicks off the initial device synchronization, and puts the device into the primary (readable and writable) role. See Resource roles (from the DRBD User’s Guide) for a more detailed description of the primary and secondary roles in DRBD. Must be completed on one node only, namely the one where you are about to continue with creating your filesystem." +msgstr "" + +#: ./doc/high-availability-guide/bk-ha-guide.xml:607(title) ./doc/high-availability-guide/bk-ha-guide.xml:856(title) +msgid "Creating a file system" +msgstr "" + +#: ./doc/high-availability-guide/bk-ha-guide.xml:609(simpara) +msgid "Once the DRBD resource is running and in the primary role (and potentially still in the process of running the initial device synchronization), you may proceed with creating the filesystem for MySQL data. XFS is the generally recommended filesystem:" +msgstr "" + +#: ./doc/high-availability-guide/bk-ha-guide.xml:614(simpara) ./doc/high-availability-guide/bk-ha-guide.xml:863(simpara) +msgid "You may also use the alternate device path for the DRBD device, which may be easier to remember as it includes the self-explanatory resource name:" +msgstr "" + +#: ./doc/high-availability-guide/bk-ha-guide.xml:618(simpara) ./doc/high-availability-guide/bk-ha-guide.xml:867(simpara) +msgid "Once completed, you may safely return the device to the secondary role. Any ongoing device synchronization will continue in the background:" +msgstr "" + +#: ./doc/high-availability-guide/bk-ha-guide.xml:625(title) +msgid "Preparing MySQL for Pacemaker high availability" +msgstr "" + +#: ./doc/high-availability-guide/bk-ha-guide.xml:627(simpara) +msgid "In order for Pacemaker monitoring to function properly, you must ensure that MySQL’s database files reside on the DRBD device. If you already have an existing MySQL database, the simplest approach is to just move the contents of the existing /var/lib/mysql directory into the newly created filesystem on the DRBD device." +msgstr "" + +#: ./doc/high-availability-guide/bk-ha-guide.xml:633(simpara) +msgid "You must complete the next step while the MySQL database server is shut down." +msgstr "" + +#: ./doc/high-availability-guide/bk-ha-guide.xml:639(simpara) +msgid "For a new MySQL installation with no existing data, you may also run the mysql_install_db command:" +msgstr "" + +#: ./doc/high-availability-guide/bk-ha-guide.xml:644(simpara) +msgid "Regardless of the approach, the steps outlined here must be completed on only one cluster node." +msgstr "" + +#: ./doc/high-availability-guide/bk-ha-guide.xml:649(title) +msgid "Adding MySQL resources to Pacemaker" +msgstr "" + +#: ./doc/high-availability-guide/bk-ha-guide.xml:651(simpara) +msgid "You may now proceed with adding the Pacemaker configuration for MySQL resources. Connect to the Pacemaker cluster with crm configure, and add the following cluster resources:" +msgstr "" + +#: ./doc/high-availability-guide/bk-ha-guide.xml:687(simpara) ./doc/high-availability-guide/bk-ha-guide.xml:921(simpara) ./doc/high-availability-guide/bk-ha-guide.xml:1120(simpara) ./doc/high-availability-guide/bk-ha-guide.xml:1211(simpara) ./doc/high-availability-guide/bk-ha-guide.xml:1370(simpara) ./doc/high-availability-guide/bk-ha-guide.xml:1444(simpara) ./doc/high-availability-guide/bk-ha-guide.xml:1488(simpara) ./doc/high-availability-guide/bk-ha-guide.xml:1529(simpara) +msgid "This configuration creates" +msgstr "" + +#: ./doc/high-availability-guide/bk-ha-guide.xml:690(simpara) +msgid "p_ip_mysql, a virtual IP address for use by MySQL (192.168.42.101)," +msgstr "" + +#: ./doc/high-availability-guide/bk-ha-guide.xml:695(simpara) +msgid "p_fs_mysql, a Pacemaker managed filesystem mounted to /var/lib/mysql on whatever node currently runs the MySQL service," +msgstr "" + +#: ./doc/high-availability-guide/bk-ha-guide.xml:701(simpara) +msgid "ms_drbd_mysql, the master/slave set managing the mysql DRBD resource," +msgstr "" + +#: ./doc/high-availability-guide/bk-ha-guide.xml:706(simpara) ./doc/high-availability-guide/bk-ha-guide.xml:940(simpara) +msgid "a service group and order and colocation constraints to ensure resources are started on the correct nodes, and in the correct sequence." +msgstr "" + +#: ./doc/high-availability-guide/bk-ha-guide.xml:712(simpara) +msgid "crm configure supports batch input, so you may copy and paste the above into your live pacemaker configuration, and then make changes as required. For example, you may enter edit p_ip_mysql from the crm configure menu and edit the resource to match your preferred virtual IP address." +msgstr "" + +#: ./doc/high-availability-guide/bk-ha-guide.xml:717(simpara) +msgid "Once completed, commit your configuration changes by entering commit from the crm configure menu. Pacemaker will then start the MySQL service, and its dependent resources, on one of your nodes." +msgstr "" + +#: ./doc/high-availability-guide/bk-ha-guide.xml:723(title) +msgid "Configuring OpenStack services for highly available MySQL" +msgstr "" + +#: ./doc/high-availability-guide/bk-ha-guide.xml:725(simpara) +msgid "Your OpenStack services must now point their MySQL configuration to the highly available, virtual cluster IP address — rather than a MySQL server’s physical IP address as you normally would." +msgstr "" + +#: ./doc/high-availability-guide/bk-ha-guide.xml:728(simpara) +msgid "For OpenStack Image, for example, if your MySQL service IP address is 192.168.42.101 as in the configuration explained here, you would use the following line in your OpenStack Image registry configuration file (glance-registry.conf):" +msgstr "" + +#: ./doc/high-availability-guide/bk-ha-guide.xml:733(simpara) +msgid "No other changes are necessary to your OpenStack configuration. If the node currently hosting your database experiences a problem necessitating service failover, your OpenStack services may experience a brief MySQL interruption, as they would in the event of a network hiccup, and then continue to run normally." +msgstr "" + +#: ./doc/high-availability-guide/bk-ha-guide.xml:742(title) +msgid "Highly available RabbitMQ" +msgstr "" + +#: ./doc/high-availability-guide/bk-ha-guide.xml:744(simpara) +msgid "RabbitMQ is the default AMQP server used by many OpenStack services. Making the RabbitMQ service highly available involves" +msgstr "" + +#: ./doc/high-availability-guide/bk-ha-guide.xml:748(simpara) +msgid "configuring a DRBD device for use by RabbitMQ," +msgstr "" + +#: ./doc/high-availability-guide/bk-ha-guide.xml:753(simpara) +msgid "configuring RabbitMQ to use a data directory residing on that DRBD device," +msgstr "" + +#: ./doc/high-availability-guide/bk-ha-guide.xml:765(simpara) +msgid "configuring RabbitMQ to listen on that IP address," +msgstr "" + +#: ./doc/high-availability-guide/bk-ha-guide.xml:770(simpara) +msgid "managing all resources, including the RabbitMQ daemon itself, with the Pacemaker cluster manager." +msgstr "" + +#: ./doc/high-availability-guide/bk-ha-guide.xml:777(simpara) +msgid "There is an alternative method of configuring RabbitMQ for high availability. That approach, known as active-active mirrored queues, happens to be the one preferred by the RabbitMQ developers — however it has shown less than ideal consistency and reliability in OpenStack clusters. Thus, at the time of writing, the Pacemaker/DRBD based approach remains the recommended one for OpenStack environments, although this may change in the near future as RabbitMQ active-active mirrored queues mature." +msgstr "" + +#: ./doc/high-availability-guide/bk-ha-guide.xml:791(simpara) +msgid "The Pacemaker based RabbitMQ server requires a DRBD resource from which it mounts the /var/lib/rabbitmq directory. In this example, the DRBD resource is simply named rabbitmq:" +msgstr "" + +#: ./doc/high-availability-guide/bk-ha-guide.xml:796(title) +msgid "rabbitmq DRBD resource configuration (/etc/drbd.d/rabbitmq.res)" +msgstr "" + +#: ./doc/high-availability-guide/bk-ha-guide.xml:812(simpara) +msgid "This resource uses an underlying local disk (in DRBD terminology, a backing device) named /dev/data/rabbitmq on both cluster nodes, node1 and node2. Normally, this would be an LVM Logical Volume specifically set aside for this purpose. The DRBD meta-disk is internal, meaning DRBD-specific metadata is being stored at the end of the disk device itself. The device is configured to communicate between IPv4 addresses 10.0.42.100 and 10.0.42.254, using TCP port 7701. Once enabled, it will map to a local DRBD block device with the device minor number 1, that is, /dev/drbd1." +msgstr "" + +#: ./doc/high-availability-guide/bk-ha-guide.xml:829(para) +msgid "Initializes DRBD metadata and writes the initial set of metadata to /dev/data/rabbitmq. Must be completed on both nodes." +msgstr "" + +#: ./doc/high-availability-guide/bk-ha-guide.xml:835(para) +msgid "Creates the /dev/drbd1 device node, attaches the DRBD device to its backing store, and connects the DRBD node to its peer. Must be completed on both nodes." +msgstr "" + +#: ./doc/high-availability-guide/bk-ha-guide.xml:858(simpara) +msgid "Once the DRBD resource is running and in the primary role (and potentially still in the process of running the initial device synchronization), you may proceed with creating the filesystem for RabbitMQ data. XFS is the generally recommended filesystem:" +msgstr "" + +#: ./doc/high-availability-guide/bk-ha-guide.xml:874(title) +msgid "Preparing RabbitMQ for Pacemaker high availability" +msgstr "" + +#: ./doc/high-availability-guide/bk-ha-guide.xml:876(simpara) +msgid "In order for Pacemaker monitoring to function properly, you must ensure that RabbitMQ’s .erlang.cookie files are identical on all nodes, regardless of whether DRBD is mounted there or not. The simplest way of doing so is to take an existing .erlang.cookie from one of your nodes, copying it to the RabbitMQ data directory on the other node, and also copying it to the DRBD-backed filesystem." +msgstr "" + +#: ./doc/high-availability-guide/bk-ha-guide.xml:889(title) +msgid "Adding RabbitMQ resources to Pacemaker" +msgstr "" + +#: ./doc/high-availability-guide/bk-ha-guide.xml:891(simpara) +msgid "You may now proceed with adding the Pacemaker configuration for RabbitMQ resources. Connect to the Pacemaker cluster with crm configure, and add the following cluster resources:" +msgstr "" + +#: ./doc/high-availability-guide/bk-ha-guide.xml:924(simpara) +msgid "p_ip_rabbitmp, a virtual IP address for use by RabbitMQ (192.168.42.100)," +msgstr "" + +#: ./doc/high-availability-guide/bk-ha-guide.xml:929(simpara) +msgid "p_fs_rabbitmq, a Pacemaker managed filesystem mounted to /var/lib/rabbitmq on whatever node currently runs the RabbitMQ service," +msgstr "" + +#: ./doc/high-availability-guide/bk-ha-guide.xml:935(simpara) +msgid "ms_drbd_rabbitmq, the master/slave set managing the rabbitmq DRBD resource," +msgstr "" + +#: ./doc/high-availability-guide/bk-ha-guide.xml:946(simpara) +msgid "crm configure supports batch input, so you may copy and paste the above into your live pacemaker configuration, and then make changes as required. For example, you may enter edit p_ip_rabbitmq from the crm configure menu and edit the resource to match your preferred virtual IP address." +msgstr "" + +#: ./doc/high-availability-guide/bk-ha-guide.xml:951(simpara) +msgid "Once completed, commit your configuration changes by entering commit from the crm configure menu. Pacemaker will then start the RabbitMQ service, and its dependent resources, on one of your nodes." +msgstr "" + +#: ./doc/high-availability-guide/bk-ha-guide.xml:957(title) +msgid "Configuring OpenStack services for highly available RabbitMQ" +msgstr "" + +#: ./doc/high-availability-guide/bk-ha-guide.xml:959(simpara) +msgid "Your OpenStack services must now point their RabbitMQ configuration to the highly available, virtual cluster IP address — rather than a RabbitMQ server’s physical IP address as you normally would." +msgstr "" + +#: ./doc/high-availability-guide/bk-ha-guide.xml:962(simpara) +msgid "For OpenStack Image, for example, if your RabbitMQ service IP address is 192.168.42.100 as in the configuration explained here, you would use the following line in your OpenStack Image API configuration file (glance-api.conf):" +msgstr "" + +#: ./doc/high-availability-guide/bk-ha-guide.xml:967(simpara) +msgid "No other changes are necessary to your OpenStack configuration. If the node currently hosting your RabbitMQ experiences a problem necessitating service failover, your OpenStack services may experience a brief RabbitMQ interruption, as they would in the event of a network hiccup, and then continue to run normally." +msgstr "" + +#: ./doc/high-availability-guide/bk-ha-guide.xml:977(title) +msgid "API Node Cluster Stack" +msgstr "" + +#: ./doc/high-availability-guide/bk-ha-guide.xml:979(simpara) +msgid "The API node exposes OpenStack API endpoints onto external network (Internet). It needs to talk to the Cloud Controller on the management network." +msgstr "" + +#: ./doc/high-availability-guide/bk-ha-guide.xml:983(title) +msgid "Configure the VIP" +msgstr "" + +#: ./doc/high-availability-guide/bk-ha-guide.xml:985(simpara) +msgid "First of all, we need to select and assign a virtual IP address (VIP) that can freely float between cluster nodes." +msgstr "" + +#: ./doc/high-availability-guide/bk-ha-guide.xml:986(simpara) +msgid "This configuration creates p_ip_api, a virtual IP address for use by the API node (192.168.42.103) :" +msgstr "" + +#: ./doc/high-availability-guide/bk-ha-guide.xml:993(title) +msgid "Highly available OpenStack Identity" +msgstr "" + +#: ./doc/high-availability-guide/bk-ha-guide.xml:995(simpara) +msgid "OpenStack Identity is the Identity Service in OpenStack and used by many services. Making the OpenStack Identity service highly available in active / passive mode involves" +msgstr "" + +#: ./doc/high-availability-guide/bk-ha-guide.xml:999(simpara) +msgid "configuring OpenStack Identity to listen on the VIP address," +msgstr "" + +#: ./doc/high-availability-guide/bk-ha-guide.xml:1004(simpara) +msgid "managing OpenStack Identity daemon with the Pacemaker cluster manager," +msgstr "" + +#: ./doc/high-availability-guide/bk-ha-guide.xml:1009(simpara) ./doc/high-availability-guide/bk-ha-guide.xml:1098(simpara) ./doc/high-availability-guide/bk-ha-guide.xml:1188(simpara) ./doc/high-availability-guide/bk-ha-guide.xml:1272(simpara) +msgid "configuring OpenStack services to use this IP address." +msgstr "" + +#: ./doc/high-availability-guide/bk-ha-guide.xml:1015(simpara) +msgid "Here is the documentation for installing OpenStack Identity service." +msgstr "" + +#: ./doc/high-availability-guide/bk-ha-guide.xml:1019(title) +msgid "Adding OpenStack Identity resource to Pacemaker" +msgstr "" + +#: ./doc/high-availability-guide/bk-ha-guide.xml:1021(simpara) ./doc/high-availability-guide/bk-ha-guide.xml:1110(simpara) ./doc/high-availability-guide/bk-ha-guide.xml:1200(simpara) ./doc/high-availability-guide/bk-ha-guide.xml:1284(simpara) ./doc/high-availability-guide/bk-ha-guide.xml:1360(simpara) ./doc/high-availability-guide/bk-ha-guide.xml:1477(simpara) +msgid "First of all, you need to download the resource agent to your system :" +msgstr "" + +#: ./doc/high-availability-guide/bk-ha-guide.xml:1027(simpara) +msgid "You may now proceed with adding the Pacemaker configuration for OpenStack Identity resource. Connect to the Pacemaker cluster with crm configure, and add the following cluster resources:" +msgstr "" + +#: ./doc/high-availability-guide/bk-ha-guide.xml:1033(simpara) +msgid "This configuration creates p_keystone, a resource for manage OpenStack Identity service." +msgstr "" + +#: ./doc/high-availability-guide/bk-ha-guide.xml:1034(simpara) +msgid "crm configure supports batch input, so you may copy and paste the above into your live pacemaker configuration, and then make changes as required. For example, you may enter edit p_ip_keystone from the crm configure menu and edit the resource to match your preferred virtual IP address." +msgstr "" + +#: ./doc/high-availability-guide/bk-ha-guide.xml:1039(simpara) +msgid "Once completed, commit your configuration changes by entering commit from the crm configure menu. Pacemaker will then start the OpenStack Identity service, and its dependent resources, on one of your nodes." +msgstr "" + +#: ./doc/high-availability-guide/bk-ha-guide.xml:1045(title) +msgid "Configuring OpenStack Identity service" +msgstr "" + +#: ./doc/high-availability-guide/bk-ha-guide.xml:1047(simpara) +msgid "You need to edit your OpenStack Identity configuration file (keystone.conf) and change the bind parameters :" +msgstr "" + +#: ./doc/high-availability-guide/bk-ha-guide.xml:1048(simpara) +msgid "On Havana:" +msgstr "" + +#: ./doc/high-availability-guide/bk-ha-guide.xml:1050(simpara) +msgid "On Icehouse, the admin_bind_host option lets you use a private network for the admin access." +msgstr "" + +#: ./doc/high-availability-guide/bk-ha-guide.xml:1053(simpara) +msgid "To be sure all data will be high available, you should be sure that you store everything in the MySQL database (which is also high available) :" +msgstr "" + +#: ./doc/high-availability-guide/bk-ha-guide.xml:1063(title) +msgid "Configuring OpenStack Services to use High Available OpenStack Identity" +msgstr "" + +#: ./doc/high-availability-guide/bk-ha-guide.xml:1065(simpara) +msgid "Your OpenStack services must now point their OpenStack Identity configuration to the highly available, virtual cluster IP address — rather than a OpenStack Identity server’s physical IP address as you normally would." +msgstr "" + +#: ./doc/high-availability-guide/bk-ha-guide.xml:1068(simpara) +msgid "For example with OpenStack Compute, if your OpenStack Identity service IP address is 192.168.42.103 as in the configuration explained here, you would use the following line in your API configuration file (api-paste.ini):" +msgstr "" + +#: ./doc/high-availability-guide/bk-ha-guide.xml:1073(simpara) +msgid "You need also to create the OpenStack Identity Endpoint with this IP." +msgstr "" + +#: ./doc/high-availability-guide/bk-ha-guide.xml:1074(simpara) +msgid "NOTE : If you are using both private and public IP addresses, you should create two Virtual IP addresses and define your endpoint like this :" +msgstr "" + +#: ./doc/high-availability-guide/bk-ha-guide.xml:1076(simpara) +msgid "If you are using the Horizon Dashboard, you should edit local_settings.py file :" +msgstr "" + +#: ./doc/high-availability-guide/bk-ha-guide.xml:1082(title) +msgid "Highly available OpenStack Image API" +msgstr "" + +#: ./doc/high-availability-guide/bk-ha-guide.xml:1084(simpara) +msgid "OpenStack Image Service offers a service for discovering, registering, and retrieving virtual machine images. Making the OpenStack Image API service highly available in active / passive mode involves" +msgstr "" + +#: ./doc/high-availability-guide/bk-ha-guide.xml:1088(simpara) +msgid "configuring OpenStack Image to listen on the VIP address," +msgstr "" + +#: ./doc/high-availability-guide/bk-ha-guide.xml:1093(simpara) +msgid "managing OpenStack Image API daemon with the Pacemaker cluster manager," +msgstr "" + +#: ./doc/high-availability-guide/bk-ha-guide.xml:1104(simpara) +msgid "Here is the documentation for installing OpenStack Image API service." +msgstr "" + +#: ./doc/high-availability-guide/bk-ha-guide.xml:1108(title) +msgid "Adding OpenStack Image API resource to Pacemaker" +msgstr "" + +#: ./doc/high-availability-guide/bk-ha-guide.xml:1114(simpara) +msgid "You may now proceed with adding the Pacemaker configuration for OpenStack Image API resource. Connect to the Pacemaker cluster with crm configure, and add the following cluster resources:" +msgstr "" + +#: ./doc/high-availability-guide/bk-ha-guide.xml:1123(simpara) +msgid "p_glance-api, a resource for manage OpenStack Image API service" +msgstr "" + +#: ./doc/high-availability-guide/bk-ha-guide.xml:1127(simpara) +msgid "crm configure supports batch input, so you may copy and paste the above into your live pacemaker configuration, and then make changes as required. For example, you may enter edit p_ip_glance-api from the crm configure menu and edit the resource to match your preferred virtual IP address." +msgstr "" + +#: ./doc/high-availability-guide/bk-ha-guide.xml:1132(simpara) +msgid "Once completed, commit your configuration changes by entering commit from the crm configure menu. Pacemaker will then start the OpenStack Image API service, and its dependent resources, on one of your nodes." +msgstr "" + +#: ./doc/high-availability-guide/bk-ha-guide.xml:1138(title) +msgid "Configuring OpenStack Image API service" +msgstr "" + +#: ./doc/high-availability-guide/bk-ha-guide.xml:1140(simpara) +msgid "Edit /etc/glance/glance-api.conf :" +msgstr "" + +#: ./doc/high-availability-guide/bk-ha-guide.xml:1156(title) +msgid "Configuring OpenStack Services to use High Available OpenStack Image API" +msgstr "" + +#: ./doc/high-availability-guide/bk-ha-guide.xml:1158(simpara) +msgid "Your OpenStack services must now point their OpenStack Image API configuration to the highly available, virtual cluster IP address — rather than a OpenStack Image API server’s physical IP address as you normally would." +msgstr "" + +#: ./doc/high-availability-guide/bk-ha-guide.xml:1161(simpara) +msgid "For OpenStack Compute, for example, if your OpenStack Image API service IP address is 192.168.42.104 as in the configuration explained here, you would use the following line in your nova.conf file :" +msgstr "" + +#: ./doc/high-availability-guide/bk-ha-guide.xml:1165(simpara) +msgid "You need also to create the OpenStack Image API Endpoint with this IP." +msgstr "" + +#: ./doc/high-availability-guide/bk-ha-guide.xml:1166(simpara) ./doc/high-availability-guide/bk-ha-guide.xml:1334(simpara) +msgid "NOTE : If you are using both private and public IP addresses, you should create two Virtual IP addresses and define your endpoint like this:" +msgstr "" + +#: ./doc/high-availability-guide/bk-ha-guide.xml:1172(title) +msgid "Highly available Cinder API" +msgstr "" + +#: ./doc/high-availability-guide/bk-ha-guide.xml:1174(simpara) +msgid "Cinder is the block storage service in OpenStack. Making the Cinder API service highly available in active / passive mode involves" +msgstr "" + +#: ./doc/high-availability-guide/bk-ha-guide.xml:1178(simpara) +msgid "configuring Cinder to listen on the VIP address," +msgstr "" + +#: ./doc/high-availability-guide/bk-ha-guide.xml:1183(simpara) +msgid "managing Cinder API daemon with the Pacemaker cluster manager," +msgstr "" + +#: ./doc/high-availability-guide/bk-ha-guide.xml:1194(simpara) +msgid "Here is the documentation for installing Cinder service." +msgstr "" + +#: ./doc/high-availability-guide/bk-ha-guide.xml:1198(title) +msgid "Adding Cinder API resource to Pacemaker" +msgstr "" + +#: ./doc/high-availability-guide/bk-ha-guide.xml:1204(simpara) +msgid "You may now proceed with adding the Pacemaker configuration for Cinder API resource. Connect to the Pacemaker cluster with crm configure, and add the following cluster resources:" +msgstr "" + +#: ./doc/high-availability-guide/bk-ha-guide.xml:1214(simpara) +msgid "p_cinder-api, a resource for manage Cinder API service" +msgstr "" + +#: ./doc/high-availability-guide/bk-ha-guide.xml:1218(simpara) +msgid "crm configure supports batch input, so you may copy and paste the above into your live pacemaker configuration, and then make changes as required. For example, you may enter edit p_ip_cinder-api from the crm configure menu and edit the resource to match your preferred virtual IP address." +msgstr "" + +#: ./doc/high-availability-guide/bk-ha-guide.xml:1223(simpara) +msgid "Once completed, commit your configuration changes by entering commit from the crm configure menu. Pacemaker will then start the Cinder API service, and its dependent resources, on one of your nodes." +msgstr "" + +#: ./doc/high-availability-guide/bk-ha-guide.xml:1229(title) +msgid "Configuring Cinder API service" +msgstr "" + +#: ./doc/high-availability-guide/bk-ha-guide.xml:1231(simpara) +msgid "Edit /etc/cinder/cinder.conf :" +msgstr "" + +#: ./doc/high-availability-guide/bk-ha-guide.xml:1244(title) +msgid "Configuring OpenStack Services to use High Available Cinder API" +msgstr "" + +#: ./doc/high-availability-guide/bk-ha-guide.xml:1246(simpara) +msgid "Your OpenStack services must now point their Cinder API configuration to the highly available, virtual cluster IP address — rather than a Cinder API server’s physical IP address as you normally would." +msgstr "" + +#: ./doc/high-availability-guide/bk-ha-guide.xml:1249(simpara) +msgid "You need to create the Cinder API Endpoint with this IP." +msgstr "" + +#: ./doc/high-availability-guide/bk-ha-guide.xml:1250(simpara) +msgid "NOTE : If you are using both private and public IP, you should create two Virtual IP and define your endpoint like this :" +msgstr "" + +#: ./doc/high-availability-guide/bk-ha-guide.xml:1256(title) +msgid "Highly available OpenStack Networking Server" +msgstr "" + +#: ./doc/high-availability-guide/bk-ha-guide.xml:1258(simpara) +msgid "OpenStack Networking is the network connectivity service in OpenStack. Making the OpenStack Networking Server service highly available in active / passive mode involves" +msgstr "" + +#: ./doc/high-availability-guide/bk-ha-guide.xml:1262(simpara) +msgid "configuring OpenStack Networking to listen on the VIP address," +msgstr "" + +#: ./doc/high-availability-guide/bk-ha-guide.xml:1267(simpara) +msgid "managing OpenStack Networking API Server daemon with the Pacemaker cluster manager," +msgstr "" + +#: ./doc/high-availability-guide/bk-ha-guide.xml:1278(simpara) +msgid "Here is the documentation for installing OpenStack Networking service." +msgstr "" + +#: ./doc/high-availability-guide/bk-ha-guide.xml:1282(title) +msgid "Adding OpenStack Networking Server resource to Pacemaker" +msgstr "" + +#: ./doc/high-availability-guide/bk-ha-guide.xml:1288(simpara) +msgid "You may now proceed with adding the Pacemaker configuration for OpenStack Networking Server resource. Connect to the Pacemaker cluster with crm configure, and add the following cluster resources:" +msgstr "" + +#: ./doc/high-availability-guide/bk-ha-guide.xml:1295(simpara) +msgid "This configuration creates p_neutron-server, a resource for manage OpenStack Networking Server service" +msgstr "" + +#: ./doc/high-availability-guide/bk-ha-guide.xml:1296(simpara) +msgid "crm configure supports batch input, so you may copy and paste the above into your live pacemaker configuration, and then make changes as required. For example, you may enter edit p_neutron-server from the crm configure menu and edit the resource to match your preferred virtual IP address." +msgstr "" + +#: ./doc/high-availability-guide/bk-ha-guide.xml:1301(simpara) +msgid "Once completed, commit your configuration changes by entering commit from the crm configure menu. Pacemaker will then start the OpenStack Networking API service, and its dependent resources, on one of your nodes." +msgstr "" + +#: ./doc/high-availability-guide/bk-ha-guide.xml:1307(title) +msgid "Configuring OpenStack Networking Server" +msgstr "" + +#: ./doc/high-availability-guide/bk-ha-guide.xml:1309(simpara) +msgid "Edit /etc/neutron/neutron.conf :" +msgstr "" + +#: ./doc/high-availability-guide/bk-ha-guide.xml:1326(title) +msgid "Configuring OpenStack Services to use Highly available OpenStack Networking Server" +msgstr "" + +#: ./doc/high-availability-guide/bk-ha-guide.xml:1328(simpara) +msgid "Your OpenStack services must now point their OpenStack Networking Server configuration to the highly available, virtual cluster IP address — rather than an OpenStack Networking server’s physical IP address as you normally would." +msgstr "" + +#: ./doc/high-availability-guide/bk-ha-guide.xml:1331(simpara) +msgid "For example, you should configure OpenStack Compute for using Highly Available OpenStack Networking Server in editing nova.conf file :" +msgstr "" + +#: ./doc/high-availability-guide/bk-ha-guide.xml:1333(simpara) +msgid "You need to create the OpenStack Networking Server Endpoint with this IP." +msgstr "" + +#: ./doc/high-availability-guide/bk-ha-guide.xml:1340(title) +msgid "Highly available Ceilometer Central Agent" +msgstr "" + +#: ./doc/high-availability-guide/bk-ha-guide.xml:1342(simpara) +msgid "Ceilometer is the metering service in OpenStack. Central Agent polls for resource utilization statistics for resources not tied to instances or compute nodes." +msgstr "" + +#: ./doc/high-availability-guide/bk-ha-guide.xml:1346(simpara) +msgid "Due to limitations of a polling model, a single instance of this agent can be polling a given list of meters. In this setup, we install this service on the API nodes also in the active / passive mode." +msgstr "" + +#: ./doc/high-availability-guide/bk-ha-guide.xml:1350(simpara) +msgid "Making the Ceilometer Central Agent service highly available in active / passive mode involves managing its daemon with the Pacemaker cluster manager," +msgstr "" + +#: ./doc/high-availability-guide/bk-ha-guide.xml:1353(simpara) +msgid "You will find at this page the process to install Ceilometer Central Agent." +msgstr "" + +#: ./doc/high-availability-guide/bk-ha-guide.xml:1358(title) +msgid "Adding Ceilometer Central Agent resource to Pacemaker" +msgstr "" + +#: ./doc/high-availability-guide/bk-ha-guide.xml:1364(simpara) +msgid "You may then proceed with adding the Pacemaker configuration for Ceilometer Central Agent resource. Connect to the Pacemaker cluster with crm configure, and add the following cluster resources:" +msgstr "" + +#: ./doc/high-availability-guide/bk-ha-guide.xml:1373(simpara) +msgid "p_ceilometer-agent-central, a resource for manage Ceilometer Central Agent service" +msgstr "" + +#: ./doc/high-availability-guide/bk-ha-guide.xml:1377(simpara) ./doc/high-availability-guide/bk-ha-guide.xml:1451(simpara) ./doc/high-availability-guide/bk-ha-guide.xml:1496(simpara) ./doc/high-availability-guide/bk-ha-guide.xml:1537(simpara) +msgid "crm configure supports batch input, so you may copy and paste the above into your live pacemaker configuration, and then make changes as required." +msgstr "" + +#: ./doc/high-availability-guide/bk-ha-guide.xml:1380(simpara) +msgid "Once completed, commit your configuration changes by entering commit from the crm configure menu. Pacemaker will then start the Ceilometer Central Agent service, and its dependent resources, on one of your nodes." +msgstr "" + +#: ./doc/high-availability-guide/bk-ha-guide.xml:1386(title) +msgid "Configuring Ceilometer Central Agent service" +msgstr "" + +#: ./doc/high-availability-guide/bk-ha-guide.xml:1388(simpara) +msgid "Edit /etc/ceilometer/ceilometer.conf :" +msgstr "" + +#: ./doc/high-availability-guide/bk-ha-guide.xml:1403(title) +msgid "Configure Pacemaker Group" +msgstr "" + +#: ./doc/high-availability-guide/bk-ha-guide.xml:1405(simpara) +msgid "Finally, we need to create a service group to ensure that virtual IP is linked to the API services resources :" +msgstr "" + +#: ./doc/high-availability-guide/bk-ha-guide.xml:1412(title) +msgid "Network Controller Cluster Stack" +msgstr "" + +#: ./doc/high-availability-guide/bk-ha-guide.xml:1414(simpara) +msgid "The Network controller sits on the management and data network, and needs to be connected to the Internet if a VM needs access to it." +msgstr "" + +#: ./doc/high-availability-guide/bk-ha-guide.xml:1416(simpara) +msgid "Both nodes should have the same hostname since the Neutron scheduler will be aware of one node, for example a virtual router attached to a single L3 node." +msgstr "" + +#: ./doc/high-availability-guide/bk-ha-guide.xml:1421(title) +msgid "Highly available Neutron L3 Agent" +msgstr "" + +#: ./doc/high-availability-guide/bk-ha-guide.xml:1423(simpara) +msgid "The Neutron L3 agent provides L3/NAT forwarding to ensure external network access for VMs on tenant networks. High Availability for the L3 agent is achieved by adopting Pacemaker." +msgstr "" + +#: ./doc/high-availability-guide/bk-ha-guide.xml:1427(simpara) +msgid "Here is the documentation for installing Neutron L3 Agent." +msgstr "" + +#: ./doc/high-availability-guide/bk-ha-guide.xml:1431(title) +msgid "Adding Neutron L3 Agent resource to Pacemaker" +msgstr "" + +#: ./doc/high-availability-guide/bk-ha-guide.xml:1433(simpara) ./doc/high-availability-guide/bk-ha-guide.xml:1518(simpara) +msgid "First of all, you need to download the resource agent to your system:" +msgstr "" + +#: ./doc/high-availability-guide/bk-ha-guide.xml:1437(simpara) +msgid "You may now proceed with adding the Pacemaker configuration for Neutron L3 Agent resource. Connect to the Pacemaker cluster with crm configure, and add the following cluster resources:" +msgstr "" + +#: ./doc/high-availability-guide/bk-ha-guide.xml:1447(simpara) +msgid "p_neutron-l3-agent, a resource for manage Neutron L3 Agent service" +msgstr "" + +#: ./doc/high-availability-guide/bk-ha-guide.xml:1454(simpara) +msgid "Once completed, commit your configuration changes by entering commit from the crm configure menu. Pacemaker will then start the Neutron L3 Agent service, and its dependent resources, on one of your nodes." +msgstr "" + +#: ./doc/high-availability-guide/bk-ha-guide.xml:1458(simpara) +msgid "This method does not ensure a zero downtime since it has to recreate all the namespaces and virtual routers on the node." +msgstr "" + +#: ./doc/high-availability-guide/bk-ha-guide.xml:1465(title) +msgid "Highly available Neutron DHCP Agent" +msgstr "" + +#: ./doc/high-availability-guide/bk-ha-guide.xml:1467(simpara) +msgid "Neutron DHCP agent distributes IP addresses to the VMs with dnsmasq (by default). High Availability for the DHCP agent is achieved by adopting Pacemaker." +msgstr "" + +#: ./doc/high-availability-guide/bk-ha-guide.xml:1471(simpara) +msgid "Here is the documentation for installing Neutron DHCP Agent." +msgstr "" + +#: ./doc/high-availability-guide/bk-ha-guide.xml:1475(title) +msgid "Adding Neutron DHCP Agent resource to Pacemaker" +msgstr "" + +#: ./doc/high-availability-guide/bk-ha-guide.xml:1481(simpara) +msgid "You may now proceed with adding the Pacemaker configuration for Neutron DHCP Agent resource. Connect to the Pacemaker cluster with crm configure, and add the following cluster resources:" +msgstr "" + +#: ./doc/high-availability-guide/bk-ha-guide.xml:1491(simpara) +msgid "p_neutron-dhcp-agent, a resource for manage Neutron DHCP Agent service" +msgstr "" + +#: ./doc/high-availability-guide/bk-ha-guide.xml:1499(simpara) +msgid "Once completed, commit your configuration changes by entering commit from the crm configure menu. Pacemaker will then start the Neutron DHCP Agent service, and its dependent resources, on one of your nodes." +msgstr "" + +#: ./doc/high-availability-guide/bk-ha-guide.xml:1506(title) +msgid "Highly available Neutron Metadata Agent" +msgstr "" + +#: ./doc/high-availability-guide/bk-ha-guide.xml:1508(simpara) +msgid "Neutron Metadata agent allows Nova API Metadata to be reachable by VMs on tenant networks. High Availability for the Metadata agent is achieved by adopting Pacemaker." +msgstr "" + +#: ./doc/high-availability-guide/bk-ha-guide.xml:1512(simpara) +msgid "Here is the documentation for installing Neutron Metadata Agent." +msgstr "" + +#: ./doc/high-availability-guide/bk-ha-guide.xml:1516(title) +msgid "Adding Neutron Metadata Agent resource to Pacemaker" +msgstr "" + +#: ./doc/high-availability-guide/bk-ha-guide.xml:1522(simpara) +msgid "You may now proceed with adding the Pacemaker configuration for Neutron Metadata Agent resource. Connect to the Pacemaker cluster with crm configure, and add the following cluster resources:" +msgstr "" + +#: ./doc/high-availability-guide/bk-ha-guide.xml:1532(simpara) +msgid "p_neutron-metadata-agent, a resource for manage Neutron Metadata Agent service" +msgstr "" + +#: ./doc/high-availability-guide/bk-ha-guide.xml:1540(simpara) +msgid "Once completed, commit your configuration changes by entering commit from the crm configure menu. Pacemaker will then start the Neutron Metadata Agent service, and its dependent resources, on one of your nodes." +msgstr "" + +#: ./doc/high-availability-guide/bk-ha-guide.xml:1547(title) +msgid "Manage network resources" +msgstr "" + +#: ./doc/high-availability-guide/bk-ha-guide.xml:1549(simpara) +msgid "You may now proceed with adding the Pacemaker configuration for managing all network resources together with a group. Connect to the Pacemaker cluster with crm configure, and add the following cluster resources:" +msgstr "" + +#: ./doc/high-availability-guide/bk-ha-guide.xml:1560(title) +msgid "HA Using Active/Active" +msgstr "" + +#: ./doc/high-availability-guide/bk-ha-guide.xml:1564(title) +msgid "Database" +msgstr "" + +#: ./doc/high-availability-guide/bk-ha-guide.xml:1566(simpara) +msgid "The first step is installing the database that sits at the heart of the cluster. When we’re talking about High Availability, however, we’re talking about not just one database, but several (for redundancy) and a means to keep them synchronized. In this case, we’re going to choose the MySQL database, along with Galera for synchronous multi-master replication." +msgstr "" + +#: ./doc/high-availability-guide/bk-ha-guide.xml:1571(simpara) +msgid "The choice of database isn’t a foregone conclusion; you’re not required to use MySQL. It is, however, a fairly common choice in OpenStack installations, so we’ll cover it here." +msgstr "" + +#: ./doc/high-availability-guide/bk-ha-guide.xml:1576(title) +msgid "MySQL with Galera" +msgstr "" + +#: ./doc/high-availability-guide/bk-ha-guide.xml:1578(simpara) +msgid "Rather than starting with a vanilla version of MySQL and then adding Galera to it, you will want to install a version of MySQL patched for wsrep (Write Set REPlication) from https://launchpad.net/codership-mysql/0.7. Note that the installation requirements are a bit touchy; you will want to make sure to read the README file so you don’t miss any steps." +msgstr "" + +#: ./doc/high-availability-guide/bk-ha-guide.xml:1583(simpara) +msgid "Next, download Galera itself from https://launchpad.net/galera/+download. Go ahead and install the *.rpms or *.debs, taking care of any dependencies that your system doesn’t already have installed." +msgstr "" + +#: ./doc/high-availability-guide/bk-ha-guide.xml:1586(simpara) +msgid "Once you’ve completed the installation, you’ll need to make a few configuration changes:" +msgstr "" + +#: ./doc/high-availability-guide/bk-ha-guide.xml:1587(simpara) +msgid "In the system-wide my.conf file, make sure mysqld isn’t bound to 127.0.0.1, and that /etc/mysql/conf.d/ is included. Typically you can find this file at /etc/my.cnf:" +msgstr "" + +#: ./doc/high-availability-guide/bk-ha-guide.xml:1594(simpara) +msgid "When adding a new node, you must configure it with a MySQL account that can access the other nodes so that it can request a state snapshot from one of those existing nodes. First specify that account information in /etc/mysql/conf.d/wsrep.cnf:" +msgstr "" + +#: ./doc/high-availability-guide/bk-ha-guide.xml:1598(simpara) +msgid "Next connect as root and grant privileges to that user:" +msgstr "" + +#: ./doc/high-availability-guide/bk-ha-guide.xml:1600(simpara) +msgid "You’ll also need to remove user accounts with empty usernames, as they cause problems:" +msgstr "" + +#: ./doc/high-availability-guide/bk-ha-guide.xml:1602(simpara) +msgid "You’ll also need to set certain mandatory configuration options within MySQL itself. These include:" +msgstr "" + +#: ./doc/high-availability-guide/bk-ha-guide.xml:1608(simpara) +msgid "Finally, make sure that the nodes can access each other through the firewall. This might mean adjusting iptables, as in:" +msgstr "" + +#: ./doc/high-availability-guide/bk-ha-guide.xml:1612(simpara) +msgid "It might also mean configuring any NAT firewall between nodes to allow direct connections, or disabling SELinux or configuring it to allow mysqld to listen to sockets at unprivileged ports." +msgstr "" + +#: ./doc/high-availability-guide/bk-ha-guide.xml:1615(simpara) +msgid "Now you’re ready to actually create the cluster." +msgstr "" + +#: ./doc/high-availability-guide/bk-ha-guide.xml:1618(title) +msgid "Creating the cluster" +msgstr "" + +#: ./doc/high-availability-guide/bk-ha-guide.xml:1620(simpara) +msgid "In creating a cluster, you first start a single instance, which creates the cluster. The rest of the MySQL instances then connect to that cluster. For example, if you started on 10.0.0.10 by executing the command:" +msgstr "" + +#: ./doc/high-availability-guide/bk-ha-guide.xml:1622(simpara) +msgid "you could then connect to that cluster on the rest of the nodes by referencing the address of that node, as in:" +msgstr "" + +#: ./doc/high-availability-guide/bk-ha-guide.xml:1624(simpara) +msgid "You also have the option to set the wsrep_cluster_address in the /etc/mysql/conf.d/wsrep.cnf file, or within the client itself. (In fact, for some systems, such as MariaDB or Percona, this may be your only option.) For example, to check the status of the cluster, open the MySQL client and check the status of the various parameters:" +msgstr "" + +#: ./doc/high-availability-guide/bk-ha-guide.xml:1631(simpara) +msgid "You should see a status that looks something like this:" +msgstr "" + +#: ./doc/high-availability-guide/bk-ha-guide.xml:1680(title) +msgid "Galera Monitoring Scripts" +msgstr "" + +#: ./doc/high-availability-guide/bk-ha-guide.xml:1682(simpara) +msgid "(Coming soon)" +msgstr "" + +#: ./doc/high-availability-guide/bk-ha-guide.xml:1686(title) +msgid "Other ways to provide a Highly Available database" +msgstr "" + +#: ./doc/high-availability-guide/bk-ha-guide.xml:1688(simpara) +msgid "MySQL with Galera is by no means the only way to achieve database HA. MariaDB (https://mariadb.org/) and Percona (http://www.percona.com/) also work with Galera. You also have the option to use Postgres, which has its own replication, or some other database HA option." +msgstr "" + +#: ./doc/high-availability-guide/bk-ha-guide.xml:1696(title) +msgid "RabbitMQ" +msgstr "" + +#: ./doc/high-availability-guide/bk-ha-guide.xml:1698(simpara) +msgid "RabbitMQ is the default AMQP server used by many OpenStack services. Making the RabbitMQ service highly available involves:" +msgstr "" + +#: ./doc/high-availability-guide/bk-ha-guide.xml:1702(simpara) ./doc/high-availability-guide/bk-ha-guide.xml:1719(title) +msgid "Install RabbitMQ" +msgstr "" + +#: ./doc/high-availability-guide/bk-ha-guide.xml:1707(simpara) +msgid "Configure RabbitMQ for HA queues" +msgstr "" + +#: ./doc/high-availability-guide/bk-ha-guide.xml:1712(simpara) +msgid "Configure OpenStack services to use Rabbit HA queues" +msgstr "" + +#: ./doc/high-availability-guide/bk-ha-guide.xml:1721(simpara) +msgid "This setup has been tested with RabbitMQ 2.7.1." +msgstr "" + +#: ./doc/high-availability-guide/bk-ha-guide.xml:1724(title) +msgid "On Ubuntu / Debian" +msgstr "" + +#: ./doc/high-availability-guide/bk-ha-guide.xml:1726(simpara) ./doc/high-availability-guide/bk-ha-guide.xml:1736(simpara) +msgid "RabbitMQ is packaged on both distros:" +msgstr "" + +#: ./doc/high-availability-guide/bk-ha-guide.xml:1729(link) +msgid "Official manual for installing RabbitMQ on Ubuntu / Debian" +msgstr "" + +#: ./doc/high-availability-guide/bk-ha-guide.xml:1734(title) +msgid "On Fedora / RHEL" +msgstr "" + +#: ./doc/high-availability-guide/bk-ha-guide.xml:1739(link) +msgid "Official manual for installing RabbitMQ on Fedora / RHEL" +msgstr "" + +#: ./doc/high-availability-guide/bk-ha-guide.xml:1745(title) +msgid "Configure RabbitMQ" +msgstr "" + +#: ./doc/high-availability-guide/bk-ha-guide.xml:1747(simpara) +msgid "Here we are building a cluster of RabbitMQ nodes to construct a RabbitMQ broker. Mirrored queues in RabbitMQ improve the availability of service since it will be resilient to failures, but we have to consider that while exchanges and bindings will survive the loss of individual nodes, queues and their messages will no because a queue and its contents is located on one node. So if we lose this node, we also lose the queue." +msgstr "" + +#: ./doc/high-availability-guide/bk-ha-guide.xml:1752(simpara) +msgid "We consider that we run (at least) two RabbitMQ servers. To build a broker, we need to ensure that all nodes have the same erlang cookie file. To do so, stop RabbitMQ everywhere and copy the cookie from rabbit1 server to other server(s):" +msgstr "" + +#: ./doc/high-availability-guide/bk-ha-guide.xml:1757(simpara) +msgid "Then, start RabbitMQ on nodes. If RabbitMQ fails to start, you can’t continue to the next step." +msgstr "" + +#: ./doc/high-availability-guide/bk-ha-guide.xml:1759(simpara) +msgid "Now, we are building the HA cluster. From rabbit2, run these commands:" +msgstr "" + +#: ./doc/high-availability-guide/bk-ha-guide.xml:1763(simpara) +msgid "To verify the cluster status :" +msgstr "" + +#: ./doc/high-availability-guide/bk-ha-guide.xml:1768(simpara) +msgid "If the cluster is working, you can now proceed to creating users and password for queues." +msgstr "" + +#: ./doc/high-availability-guide/bk-ha-guide.xml:1770(emphasis) +msgid "Note for RabbitMQ version 3" +msgstr "" + +#: ./doc/high-availability-guide/bk-ha-guide.xml:1772(simpara) +msgid "Queue mirroring is no longer controlled by the x-ha-policy argument when declaring a queue. OpenStack can continue to declare this argument, but it won’t cause queues to be mirrored. We need to make sure that all queues (except those with auto-generated names) are mirrored across all nodes in running:" +msgstr "" + +#: ./doc/high-availability-guide/bk-ha-guide.xml:1777(link) +msgid "More informations about High availability in RabbitMQ" +msgstr "" + +#: ./doc/high-availability-guide/bk-ha-guide.xml:1782(title) +msgid "Configure OpenStack Services to use RabbitMQ" +msgstr "" + +#: ./doc/high-availability-guide/bk-ha-guide.xml:1784(simpara) +msgid "Since Grizzly Release, most of OpenStack components using queuing has been supported the feature, we have to configure them to use at least two RabbitMQ nodes." +msgstr "" + +#: ./doc/high-availability-guide/bk-ha-guide.xml:1786(simpara) +msgid "Do this configuration on all services using RabbitMQ:" +msgstr "" + +#: ./doc/high-availability-guide/bk-ha-guide.xml:1787(simpara) +msgid "RabbitMQ HA cluster host:port pairs:" +msgstr "" + +#: ./doc/high-availability-guide/bk-ha-guide.xml:1789(simpara) +msgid "How frequently to retry connecting with RabbitMQ:" +msgstr "" + +#: ./doc/high-availability-guide/bk-ha-guide.xml:1791(simpara) +msgid "How long to backoff for between retries when connecting to RabbitMQ:" +msgstr "" + +#: ./doc/high-availability-guide/bk-ha-guide.xml:1793(simpara) +msgid "Maximum retries with trying to connect to RabbitMQ (infinite by default):" +msgstr "" + +#: ./doc/high-availability-guide/bk-ha-guide.xml:1795(simpara) +msgid "Use durable queues in RabbitMQ:" +msgstr "" + +#: ./doc/high-availability-guide/bk-ha-guide.xml:1797(simpara) +msgid "Use H/A queues in RabbitMQ (x-ha-policy: all):" +msgstr "" + +#: ./doc/high-availability-guide/bk-ha-guide.xml:1799(simpara) +msgid "If you change the configuration from an old setup which did not use HA queues, you should interrupt the service :" +msgstr "" + +#: ./doc/high-availability-guide/bk-ha-guide.xml:1803(simpara) +msgid "Services currently working with HA queues : OpenStack Compute, Cinder, OpenStack Networking, Ceilometer." +msgstr "" + +#: ./doc/high-availability-guide/bk-ha-guide.xml:1808(title) +msgid "HAproxy Nodes" +msgstr "" + +#: ./doc/high-availability-guide/bk-ha-guide.xml:1810(simpara) +msgid "HAProxy is a very fast and reliable solution offering high availability, load balancing, and proxying for TCP and HTTP-based applications. It is particularly suited for web sites crawling under very high loads while needing persistence or Layer 7 processing. Supporting tens of thousands of connections is clearly realistic with today’s hardware." +msgstr "" + +#: ./doc/high-availability-guide/bk-ha-guide.xml:1814(simpara) +msgid "For installing HAproxy on your nodes, you should consider its official documentation. Also, you have to consider that this service should not be a single point of failure, so you need at least two nodes running HAproxy." +msgstr "" + +#: ./doc/high-availability-guide/bk-ha-guide.xml:1817(simpara) +msgid "Here is an example for HAproxy configuration file:" +msgstr "" + +#: ./doc/high-availability-guide/bk-ha-guide.xml:1957(simpara) +msgid "After each change of this file, you should restart HAproxy." +msgstr "" + +#: ./doc/high-availability-guide/bk-ha-guide.xml:1961(title) +msgid "OpenStack Controller Nodes" +msgstr "" + +#: ./doc/high-availability-guide/bk-ha-guide.xml:1963(simpara) +msgid "OpenStack Controller Nodes contains:" +msgstr "" + +#: ./doc/high-availability-guide/bk-ha-guide.xml:1966(simpara) +msgid "All OpenStack API services" +msgstr "" + +#: ./doc/high-availability-guide/bk-ha-guide.xml:1971(simpara) +msgid "All OpenStack schedulers" +msgstr "" + +#: ./doc/high-availability-guide/bk-ha-guide.xml:1976(simpara) +msgid "Memcached service" +msgstr "" + +#: ./doc/high-availability-guide/bk-ha-guide.xml:1983(title) +msgid "Running OpenStack API & schedulers" +msgstr "" + +#: ./doc/high-availability-guide/bk-ha-guide.xml:1987(title) +msgid "API Services" +msgstr "" + +#: ./doc/high-availability-guide/bk-ha-guide.xml:1989(simpara) +msgid "All OpenStack projects have an API service for controlling all the resources in the Cloud. In Active / Active mode, the most common setup is to scale-out these services on at least two nodes and use load-balancing and virtual IP (with HAproxy & Keepalived in this setup)." +msgstr "" + +#: ./doc/high-availability-guide/bk-ha-guide.xml:1993(emphasis) +msgid "Configuring API OpenStack services" +msgstr "" + +#: ./doc/high-availability-guide/bk-ha-guide.xml:1995(simpara) +msgid "To configure our Cloud using Highly available and scalable API services, we need to ensure that:" +msgstr "" + +#: ./doc/high-availability-guide/bk-ha-guide.xml:1998(simpara) +msgid "Using Virtual IP when configuring OpenStack Identity Endpoints." +msgstr "" + +#: ./doc/high-availability-guide/bk-ha-guide.xml:2003(simpara) +msgid "All OpenStack configuration files should refer to Virtual IP." +msgstr "" + +#: ./doc/high-availability-guide/bk-ha-guide.xml:2009(emphasis) +msgid "In case of failure" +msgstr "" + +#: ./doc/high-availability-guide/bk-ha-guide.xml:2011(simpara) +msgid "The monitor check is quite simple since it just establishes a TCP connection to the API port. Comparing to the Active / Passive mode using Corosync & Resources Agents, we don’t check if the service is actually running). That’s why all OpenStack API should be monitored by another tool (i.e. Nagios) with the goal to detect failures in the Cloud Framework infrastructure." +msgstr "" + +#: ./doc/high-availability-guide/bk-ha-guide.xml:2018(title) +msgid "Schedulers" +msgstr "" + +#: ./doc/high-availability-guide/bk-ha-guide.xml:2020(simpara) +msgid "OpenStack schedulers are used to determine how to dispatch compute, network and volume requests. The most common setup is to use RabbitMQ as messaging system already documented in this guide. Those services are connected to the messaging backend and can scale-out :" +msgstr "" + +#: ./doc/high-availability-guide/bk-ha-guide.xml:2025(simpara) +msgid "nova-scheduler" +msgstr "" + +#: ./doc/high-availability-guide/bk-ha-guide.xml:2030(simpara) +msgid "nova-conductor" +msgstr "" + +#: ./doc/high-availability-guide/bk-ha-guide.xml:2035(simpara) +msgid "cinder-scheduler" +msgstr "" + +#: ./doc/high-availability-guide/bk-ha-guide.xml:2040(simpara) +msgid "neutron-server" +msgstr "" + +#: ./doc/high-availability-guide/bk-ha-guide.xml:2045(simpara) +msgid "ceilometer-collector" +msgstr "" + +#: ./doc/high-availability-guide/bk-ha-guide.xml:2050(simpara) +msgid "heat-engine" +msgstr "" + +#: ./doc/high-availability-guide/bk-ha-guide.xml:2055(simpara) +msgid "Please refer to the RabbitMQ section for configure these services with multiple messaging servers." +msgstr "" + +#: ./doc/high-availability-guide/bk-ha-guide.xml:2060(title) +msgid "Memcached" +msgstr "" + +#: ./doc/high-availability-guide/bk-ha-guide.xml:2062(simpara) +msgid "Most of OpenStack services use an application to offer persistence and store ephemeral datas (like tokens). Memcached is one of them and can scale-out easily without specific trick." +msgstr "" + +#: ./doc/high-availability-guide/bk-ha-guide.xml:2064(simpara) +msgid "To install and configure it, you can read the official documentation." +msgstr "" + +#: ./doc/high-availability-guide/bk-ha-guide.xml:2065(simpara) +msgid "Memory caching is managed by Oslo-incubator for so the way to use multiple memcached servers is the same for all projects." +msgstr "" + +#: ./doc/high-availability-guide/bk-ha-guide.xml:2066(simpara) +msgid "Example with two hosts:" +msgstr "" + +#: ./doc/high-availability-guide/bk-ha-guide.xml:2068(simpara) +msgid "By default, controller1 will handle the caching service but if the host goes down, controller2 will do the job. More informations about memcached installation are in the OpenStack Compute Manual." +msgstr "" + +#: ./doc/high-availability-guide/bk-ha-guide.xml:2074(title) +msgid "OpenStack Network Nodes" +msgstr "" + +#: ./doc/high-availability-guide/bk-ha-guide.xml:2076(simpara) +msgid "OpenStack Network Nodes contains:" +msgstr "" + +#: ./doc/high-availability-guide/bk-ha-guide.xml:2079(simpara) +msgid "Neutron DHCP Agent" +msgstr "" + +#: ./doc/high-availability-guide/bk-ha-guide.xml:2084(simpara) +msgid "Neutron L2 Agent" +msgstr "" + +#: ./doc/high-availability-guide/bk-ha-guide.xml:2089(simpara) +msgid "Neutron L3 Agent" +msgstr "" + +#: ./doc/high-availability-guide/bk-ha-guide.xml:2094(simpara) +msgid "Neutron Metadata Agent" +msgstr "" + +#: ./doc/high-availability-guide/bk-ha-guide.xml:2099(simpara) +msgid "Neutron LBaaS Agent" +msgstr "" + +#: ./doc/high-availability-guide/bk-ha-guide.xml:2105(simpara) +msgid "The Neutron L2 Agent does not need to be highly available. It has to be installed on each Data Forwarding Node and controls the virtual networking drivers as Open-vSwitch or Linux Bridge. One L2 agent runs per node and controls its virtual interfaces. That’s why it cannot be distributed and highly available." +msgstr "" + +#: ./doc/high-availability-guide/bk-ha-guide.xml:2113(title) +msgid "Running Neutron DHCP Agent" +msgstr "" + +#: ./doc/high-availability-guide/bk-ha-guide.xml:2115(simpara) +msgid "Since the Grizzly release, OpenStack Networking service has a scheduler that lets you run multiple agents across nodes. Also, the DHCP agent can be natively highly available. For details, see OpenStack Configuration Reference." +msgstr "" + +#: ./doc/high-availability-guide/bk-ha-guide.xml:2121(title) +msgid "Running Neutron L3 Agent" +msgstr "" + +#: ./doc/high-availability-guide/bk-ha-guide.xml:2123(simpara) +msgid "Since the Grizzly release, the Neutron L3 Agent is scalable thanks to the scheduler that allows distribution of virtual routers across multiple nodes. But there is no native feature to make these routers highly available. At this time, the Active / Passive solution exists to run the Neutron L3 agent in failover mode with Pacemaker. See the Active / Passive section of this guide." +msgstr "" + +#: ./doc/high-availability-guide/bk-ha-guide.xml:2132(title) +msgid "Running Neutron Metadata Agent" +msgstr "" + +#: ./doc/high-availability-guide/bk-ha-guide.xml:2134(simpara) +msgid "There is no native feature to make this service highly available. At this time, the Active / Passive solution exists to run the Neutron Metadata agent in failover mode with Pacemaker. See the Active / Passive section of this guide." +msgstr "" + +#. Put one translator per line, in the form of NAME , YEAR1, YEAR2 +#: ./doc/high-availability-guide/bk-ha-guide.xml:0(None) +msgid "translator-credits" +msgstr "" + diff --git a/doc/image-guide/locale/he_IL.po b/doc/image-guide/locale/he_IL.po new file mode 100644 index 0000000000..288fe7f9ee --- /dev/null +++ b/doc/image-guide/locale/he_IL.po @@ -0,0 +1,3458 @@ +# +# Translators: +msgid "" +msgstr "" +"Project-Id-Version: OpenStack Manuals\n" +"POT-Creation-Date: 2014-01-30 06:24+0000\n" +"PO-Revision-Date: 2014-01-27 17:39+0000\n" +"Last-Translator: openstackjenkins \n" +"Language-Team: Hebrew (Israel) (http://www.transifex.com/projects/p/openstack/language/he_IL/)\n" +"MIME-Version: 1.0\n" +"Content-Type: text/plain; charset=UTF-8\n" +"Content-Transfer-Encoding: 8bit\n" +"Language: he_IL\n" +"Plural-Forms: nplurals=2; plural=(n != 1);\n" + +#: ./doc/image-guide/ch_modifying_images.xml6(title) +msgid "Modify images" +msgstr "" + +#: ./doc/image-guide/ch_modifying_images.xml12(para) +msgid "" +"Do not attempt to use these tools to modify an image that is attached to a " +"running virtual machine. These tools are designed to only modify images that" +" are not currently running." +msgstr "" + +#: ./doc/image-guide/ch_modifying_images.xml8(para) +msgid "" +"Once you have obtained a virtual machine image, you may want to make some " +"changes to it before uploading it to the OpenStack Image service. Here we " +"describe several tools available that allow you to modify " +"images." +msgstr "" + +#: ./doc/image-guide/ch_modifying_images.xml18(title) +msgid "guestfish" +msgstr "" + +#: ./doc/image-guide/ch_modifying_images.xml19(para) +msgid "" +"The program is a tool from the libguestfs project that allows you to" +" modify the files inside of a virtual machine image." +msgstr "" + +#: ./doc/image-guide/ch_modifying_images.xml24(para) +msgid "" +" does not mount the image directly into the local file " +"system. Instead, it provides you with a shell interface that enables you to " +"view, edit, and delete files. Many of commands, such as " +", , and , resemble " +"traditional bash commands." +msgstr "" + +#: ./doc/image-guide/ch_modifying_images.xml34(title) +msgid "Example guestfish session" +msgstr "" + +#: ./doc/image-guide/ch_modifying_images.xml35(para) +msgid "" +"Sometimes, you must modify a virtual machine image to remove any traces of " +"the MAC address that was assigned to the virtual network interface card when" +" the image was first created, because the MAC address will be different when" +" it boots the next time. This example shows how to use guestfish to remove " +"references to the old MAC address by deleting the " +"/etc/udev/rules.d/70-persistent-net.rules file and " +"removing the HWADDR line from the " +"/etc/sysconfig/network-scripts/ifcfg-eth0 file." +msgstr "" + +#: ./doc/image-guide/ch_modifying_images.xml47(para) +msgid "" +"Assume that you have a CentOS qcow2 image called " +"centos63_desktop.img. Mount the image in read-write " +"mode as root, as follows:" +msgstr "" + +#: ./doc/image-guide/ch_modifying_images.xml61(para) +msgid "" +"This starts a guestfish session. Note that the guestfish prompt looks like a" +" fish: > <fs>." +msgstr "" + +#: ./doc/image-guide/ch_modifying_images.xml64(para) +msgid "" +"We must first use the command at the guestfish prompt " +"before we can do anything else. This will launch a virtual machine, which " +"will be used to perform all of the file manipulations. We " +"can now view the file systems in the image using the " +"command:We need to mount the logical volume that contains " +"the root partition: " +msgstr "" + +#: ./doc/image-guide/ch_modifying_images.xml78(para) +msgid "" +"Next, we want to delete a file. We can use the guestfish " +"command, which works the same way it does in a traditional shell." +msgstr "" + +#: ./doc/image-guide/ch_modifying_images.xml82(para) +msgid "" +"We want to edit the ifcfg-eth0 file to " +"remove the HWADDR line. The command will" +" copy the file to the host, invoke your editor, and then copy the file back." +" " +msgstr "" + +#: ./doc/image-guide/ch_modifying_images.xml89(para) +msgid "" +"If you want to modify this image to load the 8021q kernel at boot time, you " +"must create an executable script in the " +"/etc/sysconfig/modules/ directory. You can use the " +" guestfish command to create an empty file, the " +" command to edit it, and the command to " +"make it executable. We add the following line to the file " +"and save it:Then we set to executable: " +msgstr "" + +#: ./doc/image-guide/ch_modifying_images.xml103(para) +msgid "" +"We're done, so we can exit using the " +"command:" +msgstr "" + +#: ./doc/image-guide/ch_modifying_images.xml108(title) +msgid "Go further with guestfish" +msgstr "" + +#: ./doc/image-guide/ch_modifying_images.xml109(para) +msgid "" +"There is an enormous amount of functionality in guestfish and a full " +"treatment is beyond the scope of this document. Instead, we recommend that " +"you read the guestfs-recipes documentation page for a sense of what is possible" +" with these tools." +msgstr "" + +#: ./doc/image-guide/ch_modifying_images.xml119(title) +msgid "guestmount" +msgstr "" + +#: ./doc/image-guide/ch_modifying_images.xml120(para) +msgid "" +"For some types of changes, you may find it easier to mount the image's file " +"system directly in the guest. The program, also from the " +"libguestfs project, allows you to do so." +msgstr "" + +#: ./doc/image-guide/ch_modifying_images.xml124(para) +msgid "" +"For example, to mount the root partition from our " +"centos63_desktop.qcow2 image to " +"/mnt, we can do:" +msgstr "" + +#: ./doc/image-guide/ch_modifying_images.xml130(para) +msgid "" +"If we didn't know in advance what the mount point is in the guest, we could " +"use the -i(inspect) flag to tell guestmount to " +"automatically determine what mount point to use:Once " +"mounted, we could do things like list the installed packages using " +"rpm: Once done, we unmount:" +msgstr "" + +#: ./doc/image-guide/ch_modifying_images.xml142(title) +msgid "virt-* tools" +msgstr "" + +#: ./doc/image-guide/ch_modifying_images.xml147(para) +msgid "" +"virt-edit for " +"editing a file inside of an image." +msgstr "" + +#: ./doc/image-guide/ch_modifying_images.xml153(para) +msgid "" +"virt-df for " +"displaying free space inside of an image." +msgstr "" + +#: ./doc/image-guide/ch_modifying_images.xml159(para) +msgid "" +"virt-resize " +"for resizing an image." +msgstr "" + +#: ./doc/image-guide/ch_modifying_images.xml165(para) +msgid "" +"virt-sysprep" +" for preparing an image for distribution (for example, delete SSH host keys," +" remove MAC address info, or remove user accounts)." +msgstr "" + +#: ./doc/image-guide/ch_modifying_images.xml173(para) +msgid "" +"virt-" +"sparsify for making an image sparse" +msgstr "" + +#: ./doc/image-guide/ch_modifying_images.xml179(para) +msgid "" +"virt-p2v for " +"converting a physical machine to an image that runs on KVM" +msgstr "" + +#: ./doc/image-guide/ch_modifying_images.xml185(para) +msgid "" +"virt-v2v for " +"converting Xen and VMWare images to KVM images" +msgstr "" + +#: ./doc/image-guide/ch_modifying_images.xml143(para) +msgid "" +"The libguestfs project has a " +"number of other useful tools, including:" +msgstr "" + +#: ./doc/image-guide/ch_modifying_images.xml192(title) +msgid "Modify a single file inside of an image" +msgstr "" + +#: ./doc/image-guide/ch_modifying_images.xml193(para) +msgid "" +"This example shows how to use to modify a file. The command" +" can take either a filename as an argument with the -a " +"flag, or a domain name as an argument with the -d flag. " +"The following examples shows how to use this to modify the " +"/etc/shadow file in instance with libvirt domain name " +"instance-000000e1 that is currently running:" +msgstr "" + +#: ./doc/image-guide/ch_modifying_images.xml210(title) +msgid "Resize an image" +msgstr "" + +#: ./doc/image-guide/ch_modifying_images.xml211(para) +msgid "" +"Here's a simple of example of how to use to resize an " +"image. Assume we have a 16GB Windows image in qcow2 format that we want to " +"resize to 50GB. First, we use to identify the " +"partitions:" +msgstr "" + +#: ./doc/image-guide/ch_modifying_images.xml223(para) +msgid "" +"In this case, it's the /dev/sda2 partition that we want" +" to resize. We create a new qcow2 image and use the command" +" to write a resized copy of the original into the new image: " +"" +msgstr "" + +#: ./doc/image-guide/ch_modifying_images.xml257(title) +msgid "Loop devices, kpartx, network block devices" +msgstr "" + +#: ./doc/image-guide/ch_modifying_images.xml261(para) +msgid "" +"Mounting untrusted guest images using the tools described in this section is" +" a security risk, always use libguestfs tools such as guestfish and " +"guestmount if you have access to them. See A reminder why you should " +"never mount guest disk images on the host OS by Daniel Berrangé for " +"more details." +msgstr "" + +#: ./doc/image-guide/ch_modifying_images.xml258(para) +msgid "" +"If you don't have access to libguestfs, you can mount image file systems " +"directly in the host using loop devices, kpartx, and network block " +"devices." +msgstr "" + +#: ./doc/image-guide/ch_modifying_images.xml271(title) +msgid "Mount a raw image (without LVM)" +msgstr "" + +#: ./doc/image-guide/ch_modifying_images.xml272(para) +msgid "" +"If you have a raw virtual machine image that is not using LVM to manage its " +"partitions. First, use the command to find an unused loop " +"device. " +msgstr "" + +#: ./doc/image-guide/ch_modifying_images.xml278(para) +msgid "" +"In this example, /dev/loop0 is free. Associate a loop " +"device with the raw image:" +msgstr "" + +#: ./doc/image-guide/ch_modifying_images.xml281(para) +msgid "" +"If the image only has a single partition, you can mount the loop device " +"directly:" +msgstr "" + +#: ./doc/image-guide/ch_modifying_images.xml284(para) +msgid "" +"If the image has multiple partitions, use to expose the " +"partitions as separate devices (for example, " +"/dev/mapper/loop0p1), then mount the partition that " +"corresponds to the root file system:" +msgstr "" + +#: ./doc/image-guide/ch_modifying_images.xml290(para) +msgid "" +"If the image has, say three partitions (/boot, /, /swap), there should be " +"one new device created per partition:To mount the second " +"partition, as root:Once you're done, to clean " +"up:" +msgstr "" + +#: ./doc/image-guide/ch_modifying_images.xml305(title) +msgid "Mount a raw image (with LVM)" +msgstr "" + +#: ./doc/image-guide/ch_modifying_images.xml306(para) +msgid "" +"If your partitions are managed with LVM, use losetup and kpartx as in the " +"previous example to expose the partitions to the host:" +msgstr "" + +#: ./doc/image-guide/ch_modifying_images.xml313(para) +msgid "" +"Next, you need to use the command to identify the LVM " +"volume groups and then to expose the volumes as devices:" +msgstr "" + +#: ./doc/image-guide/ch_modifying_images.xml323(para) +msgid "Clean up when you're done:" +msgstr "" + +#: ./doc/image-guide/ch_modifying_images.xml330(title) +msgid "Mount a qcow2 image (without LVM)" +msgstr "" + +#: ./doc/image-guide/ch_modifying_images.xml331(para) +msgid "" +"You need the nbd (network block device) kernel module " +"loaded to mount qcow2 images. This will load it with support for 16 block " +"devices, which is fine for our purposes. As root:" +msgstr "" + +#: ./doc/image-guide/ch_modifying_images.xml336(para) +msgid "" +"Assuming the first block device (/dev/nbd0) is not " +"currently in use, we can expose the disk partitions using the " +" and commands. As root:" +msgstr "" + +#: ./doc/image-guide/ch_modifying_images.xml343(para) +msgid "" +"If the image has, say three partitions (/boot, /, /swap), there should be " +"one new device created for each partition:" +msgstr "" + +#: ./doc/image-guide/ch_modifying_images.xml352(para) +msgid "" +"If the network block device you selected was already in use, the initial " +" command will fail silently, and the " +"/dev/nbd3p{1,2,3} device files will not be created." +msgstr "" + +#: ./doc/image-guide/ch_modifying_images.xml359(para) +msgid "" +"If the image partitions are not managed with LVM, they can be mounted " +"directly:" +msgstr "" + +#: ./doc/image-guide/ch_modifying_images.xml363(para) +msgid "When you're done, clean up:" +msgstr "" + +#: ./doc/image-guide/ch_modifying_images.xml368(title) +msgid "Mount a qcow2 image (with LVM)" +msgstr "" + +#: ./doc/image-guide/ch_modifying_images.xml369(para) +msgid "" +"If the image partitions are managed with LVM, after you use " +" and , you must use and in" +" order to expose the LVM partitions as devices that can be " +"mounted:" +msgstr "" + +#: ./doc/image-guide/ch_modifying_images.xml383(para) +msgid "When you're done, clean up:" +msgstr "" + +#. When image changes, this message will be marked fuzzy or untranslated for +#. you. +#. It doesn't matter what you translate it to: it's not used at all. +#: ./doc/image-guide/section_centos-example.xml80(None) +#: ./doc/image-guide/section_centos-example.xml84(None) +msgid "" +"@@image: 'figures/centos-install.png'; md5=013b5be9e167ee27e674859ba4869d89" +msgstr "" + +#. When image changes, this message will be marked fuzzy or untranslated for +#. you. +#. It doesn't matter what you translate it to: it's not used at all. +#: ./doc/image-guide/section_centos-example.xml96(None) +msgid "" +"@@image: 'figures/centos-tcpip.png'; md5=fe0324d0d74368d1920c243fd72747fd" +msgstr "" + +#. When image changes, this message will be marked fuzzy or untranslated for +#. you. +#. It doesn't matter what you translate it to: it's not used at all. +#: ./doc/image-guide/section_centos-example.xml107(None) +msgid "" +"@@image: 'figures/install-method.png'; md5=1d60286d52f6b385a5d15ae042858893" +msgstr "" + +#. When image changes, this message will be marked fuzzy or untranslated for +#. you. +#. It doesn't matter what you translate it to: it's not used at all. +#: ./doc/image-guide/section_centos-example.xml122(None) +msgid "@@image: 'figures/url-setup.png'; md5=b2f3b4a3552ad175575f5eb78e63dfd8" +msgstr "" + +#. When image changes, this message will be marked fuzzy or untranslated for +#. you. +#. It doesn't matter what you translate it to: it's not used at all. +#: ./doc/image-guide/section_centos-example.xml188(None) +msgid "" +"@@image: 'figures/centos-complete.png'; md5=1b2c6a2e45a9ae52a5f6338ae74b1e54" +msgstr "" + +#: ./doc/image-guide/section_centos-example.xml6(title) +msgid "Example: CentOS image" +msgstr "" + +#: ./doc/image-guide/section_centos-example.xml7(para) +msgid "" +"We'll run through an example of installing a CentOS image. This will focus " +"mainly on CentOS 6.4. Because the CentOS installation process may change " +"across versions, if you are using a different version of CentOS the " +"installer steps may differ." +msgstr "" + +#: ./doc/image-guide/section_centos-example.xml13(title) +msgid "Download a CentOS install ISO" +msgstr "" + +#: ./doc/image-guide/section_centos-example.xml17(para) +msgid "" +"Navigate to the CentOS " +"mirrors page." +msgstr "" + +#: ./doc/image-guide/section_centos-example.xml22(para) +msgid "" +"Click one of the HTTP links in the right-hand column next" +" to one of the mirrors." +msgstr "" + +#: ./doc/image-guide/section_centos-example.xml27(para) +msgid "" +"Click the folder link of the CentOS version you want to use. For example, " +"6.4/." +msgstr "" + +#: ./doc/image-guide/section_centos-example.xml32(para) +msgid "Click the isos/ folder link." +msgstr "" + +#: ./doc/image-guide/section_centos-example.xml36(para) +msgid "Click the x86_64/ folder link for 64-bit images." +msgstr "" + +#: ./doc/image-guide/section_centos-example.xml40(para) +msgid "" +"Click the ISO image you want to download. The netinstall ISO. For example, " +"CentOS-6.4-x86_64-netinstall.iso is a good choice since" +" it's a smaller image that will download missing packages from the Internet " +"during the install process." +msgstr "" + +#: ./doc/image-guide/section_centos-example.xml51(title) +#: ./doc/image-guide/section_ubuntu-example.xml21(title) +msgid "Start the install process" +msgstr "" + +#: ./doc/image-guide/section_centos-example.xml52(para) +#: ./doc/image-guide/section_ubuntu-example.xml22(para) +msgid "" +"Start the installation process using either or " +" as described in the previous section. If using " +", don't forget to connect your VNC client to the virtual " +"machine." +msgstr "" + +#: ./doc/image-guide/section_centos-example.xml58(para) +msgid "" +"We will assume the name of your virtual machine image is " +"centos-6.4, which we need to know when using " +" commands to manipulate the state of the image." +msgstr "" + +#: ./doc/image-guide/section_centos-example.xml62(para) +#: ./doc/image-guide/section_ubuntu-example.xml32(para) +msgid "" +"If you're using virt-manager, the commands should look something like " +"this:" +msgstr "" + +#: ./doc/image-guide/section_centos-example.xml73(title) +#: ./doc/image-guide/section_centos-example.xml174(title) +#: ./doc/image-guide/section_ubuntu-example.xml43(title) +#: ./doc/image-guide/section_ubuntu-example.xml69(title) +msgid "Step through the install" +msgstr "" + +#: ./doc/image-guide/section_centos-example.xml74(para) +msgid "" +"At the initial Installer boot menu, choose the \"Install or upgrade an " +"existing system\" option. Step through the install prompts, the defaults " +"should be fine." +msgstr "" + +#: ./doc/image-guide/section_centos-example.xml89(title) +msgid "Configure TCP/IP" +msgstr "" + +#: ./doc/image-guide/section_centos-example.xml90(para) +msgid "" +"The default TCP/IP settings are fine. In particular, ensure that Enable IPv4" +" support is enabled with DHCP, which is the default." +msgstr "" + +#: ./doc/image-guide/section_centos-example.xml102(title) +msgid "Point the installer to a CentOS web server" +msgstr "" + +#: ./doc/image-guide/section_centos-example.xml103(para) +msgid "Choose URL as the installation method." +msgstr "" + +#: ./doc/image-guide/section_centos-example.xml116(para) +msgid "Consider using other mirrors as an alternative to mirror.umd.edu." +msgstr "" + +#: ./doc/image-guide/section_centos-example.xml110(para) +msgid "" +"Depending on the version of CentOS, the net installer requires that the user" +" specify either a URL, or the web site and a CentOS directory that " +"corresponds to one of the CentOS mirrors. If the installer asks for a single" +" URL, an example of a valid URL would be: " +"http://mirror.umd/centos/6/os/x86_64." +msgstr "" + +#: ./doc/image-guide/section_centos-example.xml126(para) +msgid "" +"If the installer asks for web site name and CentOS directory separately, an " +"example would be:" +msgstr "" + +#: ./doc/image-guide/section_centos-example.xml131(para) +msgid "Web site name: mirror.umd.edu" +msgstr "" + +#: ./doc/image-guide/section_centos-example.xml136(para) +msgid "CentOS directory: centos/6/os/x86_64" +msgstr "" + +#: ./doc/image-guide/section_centos-example.xml141(para) +msgid "" +"See CentOS " +"mirror page to get a full list of mirrors, click on the \"HTTP\" link" +" of a mirror to retrieve the web site name of a mirror." +msgstr "" + +#: ./doc/image-guide/section_centos-example.xml148(title) +msgid "Storage devices" +msgstr "" + +#: ./doc/image-guide/section_centos-example.xml149(para) +msgid "" +"If asked about what type of devices your installation involves, choose " +"\"Basic Storage Devices\"." +msgstr "" + +#: ./doc/image-guide/section_centos-example.xml153(title) +#: ./doc/image-guide/section_ubuntu-example.xml55(title) +msgid "Hostname" +msgstr "" + +#: ./doc/image-guide/section_centos-example.xml154(para) +msgid "" +"The installer may ask you to choose a hostname. The default " +"(localhost.localdomain) is fine. We will install the " +"cloud-init packge later, which will set the hostname on boot when a new " +"instance is provisioned using this image." +msgstr "" + +#: ./doc/image-guide/section_centos-example.xml161(title) +#: ./doc/image-guide/section_ubuntu-example.xml75(title) +msgid "Partition the disks" +msgstr "" + +#: ./doc/image-guide/section_centos-example.xml162(para) +#: ./doc/image-guide/section_ubuntu-example.xml76(para) +msgid "" +"There are different options for partitioning the disks. The default " +"installation will use LVM partitions, and will create three partitions " +"(/boot, /, swap), and this will " +"work fine. Alternatively, you may wish to create a single ext4 partition, " +"mounted to \"/\", should also work fine." +msgstr "" + +#: ./doc/image-guide/section_centos-example.xml169(para) +#: ./doc/image-guide/section_ubuntu-example.xml83(para) +msgid "" +"If unsure, we recommend you use the installer's default partition scheme, " +"since there is no clear advantage to one scheme of another." +msgstr "" + +#: ./doc/image-guide/section_centos-example.xml175(para) +msgid "" +"Step through the install, using the default options. The simplest thing to " +"do is to choose the \"Basic Server\" install (may be called \"Server\" " +"install on older versions of CentOS), which will install an SSH server." +msgstr "" + +#: ./doc/image-guide/section_centos-example.xml181(title) +#: ./doc/image-guide/section_ubuntu-example.xml120(title) +msgid "Detach the CD-ROM and reboot" +msgstr "" + +#: ./doc/image-guide/section_centos-example.xml182(para) +msgid "" +"Once the install completes, you will see the screen \"Congratulations, your " +"CentOS installation is complete\"." +msgstr "" + +#: ./doc/image-guide/section_centos-example.xml197(replaceable) +#: ./doc/image-guide/section_centos-example.xml368(replaceable) +#: ./doc/image-guide/section_ubuntu-example.xml144(replaceable) +#: ./doc/image-guide/section_ubuntu-example.xml238(replaceable) +msgid "vm-image" +msgstr "" + +#: ./doc/image-guide/section_centos-example.xml192(para) +#: ./doc/image-guide/section_ubuntu-example.xml139(para) +msgid "" +"To eject a disk using , libvirt requires that you attach an " +"empty disk at the same target that the CDROM was previously attached, which " +"should be hdc. You can confirm the appropriate target " +"using the command." +msgstr "" + +#: ./doc/image-guide/section_centos-example.xml212(para) +msgid "" +"Run the following commands from the host to eject the disk and reboot using " +"virsh, as root. If you are using virt-manager, the commands below will work," +" but you can also use the GUI to the detach and reboot it by manually " +"stopping and starting." +msgstr "" + +#: ./doc/image-guide/section_centos-example.xml221(para) +msgid "" +"In theory, the command can be used instead of using destroy" +" and start commands. However, in our testing we were unable to reboot " +"successfully using the command." +msgstr "" + +#: ./doc/image-guide/section_centos-example.xml230(title) +#: ./doc/image-guide/section_ubuntu-example.xml176(title) +msgid "Log in to newly created image" +msgstr "" + +#: ./doc/image-guide/section_centos-example.xml231(para) +msgid "" +"When you boot the first time after install, it may ask you about " +"authentication tools, you can just choose \"Exit\". Then, log in as root " +"using the root password you specified." +msgstr "" + +#: ./doc/image-guide/section_centos-example.xml237(title) +msgid "Configure to fetch metadata" +msgstr "" + +#: ./doc/image-guide/section_centos-example.xml243(para) +msgid "" +"Install a cloud-init RPM, which is a port of the Ubuntu cloud-init package. This is" +" the recommended approach." +msgstr "" + +#: ./doc/image-guide/section_centos-example.xml250(para) +msgid "" +"Modify /etc/rc.local to fetch desired information from " +"the metadata service, as described below." +msgstr "" + +#: ./doc/image-guide/section_centos-example.xml238(para) +msgid "" +"An instance must perform several steps on start up by interacting with the " +"metadata service. For example, retrieve ssh public key and execute user data" +" script. There are several ways to implement this functionality, " +"including:" +msgstr "" + +#: ./doc/image-guide/section_centos-example.xml257(title) +#: ./doc/image-guide/ch_openstack_images.xml284(title) +msgid "Use cloud-init to fetch the public key" +msgstr "" + +#: ./doc/image-guide/section_centos-example.xml258(para) +msgid "" +"The cloud-init package will automatically fetch the public key from the " +"metadata server and place the key in an account. You can install cloud-init " +"inside the CentOS guest by adding the EPEL repo:" +msgstr "" + +#: ./doc/image-guide/section_centos-example.xml264(para) +#: ./doc/image-guide/section_ubuntu-example.xml201(para) +msgid "" +"The account varies by distribution. On Ubuntu-based virtual machines, the " +"account is called \"ubuntu\". On Fedora-based virtual machines, the account " +"is called \"ec2-user\"." +msgstr "" + +#: ./doc/image-guide/section_centos-example.xml268(para) +#: ./doc/image-guide/ch_openstack_images.xml291(para) +msgid "" +"You can change the name of the account used by cloud-init by editing the " +"/etc/cloud/cloud.cfg file and adding a line with a " +"different user. For example, to configure cloud-init to put the key in an " +"account named admin, edit the configuration file so it " +"has the line:" +msgstr "" + +#: ./doc/image-guide/section_centos-example.xml278(title) +msgid "Write a script to fetch the public key (if no cloud-init)" +msgstr "" + +#: ./doc/image-guide/section_centos-example.xml280(para) +msgid "" +"If you are not able to install the cloud-init package in your image, to " +"fetch the ssh public key and add it to the root account, edit the " +"/etc/rc.local file and add the following lines before " +"the line “touch /var/lock/subsys/local”" +msgstr "" + +#: ./doc/image-guide/section_centos-example.xml310(para) +msgid "" +"Some VNC clients replace : (colon) with ; (semicolon) and _ (underscore) " +"with - (hyphen). Make sure it's http: not http; and authorized_keys not " +"authorized-keys." +msgstr "" + +#: ./doc/image-guide/section_centos-example.xml316(para) +msgid "" +"The above script only retrieves the ssh public key from the metadata server." +" It does not retrieve user data, which " +"is optional data that can be passed by the user when requesting a new " +"instance. User data is often used for running a custom script when an " +"instance comes up." +msgstr "" + +#: ./doc/image-guide/section_centos-example.xml323(para) +msgid "" +"As the OpenStack metadata service is compatible with version 2009-04-04 of " +"the Amazon EC2 metadata service, consult the Amazon EC2 documentation on " +"Using Instance Metadata for " +"details on how to retrieve user data." +msgstr "" + +#: ./doc/image-guide/section_centos-example.xml332(title) +msgid "Configure console" +msgstr "" + +#: ./doc/image-guide/section_centos-example.xml339(replaceable) +msgid "..." +msgstr "" + +#: ./doc/image-guide/section_centos-example.xml333(para) +msgid "" +"In order for to work properly on CentOS 6.x, guests you may" +" need to add the following lines to " +"/boot/grub/menu.lst" +msgstr "" + +#: ./doc/image-guide/section_centos-example.xml342(title) +#: ./doc/image-guide/section_ubuntu-example.xml214(title) +msgid "Shut down the instance" +msgstr "" + +#: ./doc/image-guide/section_centos-example.xml343(para) +#: ./doc/image-guide/section_ubuntu-example.xml215(para) +msgid "From inside the instance, as root:" +msgstr "" + +#: ./doc/image-guide/section_centos-example.xml347(title) +#: ./doc/image-guide/section_ubuntu-example.xml219(title) +msgid "Clean up (remove MAC address details)" +msgstr "" + +#: ./doc/image-guide/section_centos-example.xml348(para) +msgid "" +"The operating system records the MAC address of the virtual ethernet card in" +" locations such as /etc/sysconfig/network-scripts/ifcfg-" +"eth0 and /etc/udev/rules.d/70-persistent-" +"net.rules during the instance process. However, each time the " +"image boots up, the virtual ethernet card will have a different MAC address," +" so this information must be deleted from the configuration file." +msgstr "" + +#: ./doc/image-guide/section_centos-example.xml357(para) +#: ./doc/image-guide/section_ubuntu-example.xml227(para) +msgid "" +"There is a utility called , that performs various cleanup " +"tasks such as removing the MAC address references. It will clean up a " +"virtual machine image in place:" +msgstr "" + +#: ./doc/image-guide/section_centos-example.xml364(title) +#: ./doc/image-guide/section_ubuntu-example.xml234(title) +msgid "Undefine the libvirt domain" +msgstr "" + +#: ./doc/image-guide/section_centos-example.xml365(para) +msgid "" +"Now that the image is ready to be uploaded to the Image service, you no " +"longer need to have this virtual machine image managed by libvirt. Use the " +" command to inform libvirt." +msgstr "" + +#: ./doc/image-guide/section_centos-example.xml373(title) +#: ./doc/image-guide/section_ubuntu-example.xml243(title) +msgid "Image is complete" +msgstr "" + +#: ./doc/image-guide/section_centos-example.xml374(para) +msgid "" +"The underlying image file you created with . For example, " +"/tmp/centos-6.4.qcow2 is now ready for uploading to the" +" OpenStack Image service." +msgstr "" + +#: ./doc/image-guide/bk-imageguide.xml10(title) +msgid "OpenStack Virtual Machine Image Guide" +msgstr "" + +#: ./doc/image-guide/bk-imageguide.xml12(titleabbrev) +msgid "VM Image Guide" +msgstr "" + +#: ./doc/image-guide/bk-imageguide.xml20(orgname) +#: ./doc/image-guide/bk-imageguide.xml25(holder) +msgid "OpenStack Foundation" +msgstr "" + +#: ./doc/image-guide/bk-imageguide.xml24(year) +msgid "2013" +msgstr "" + +#: ./doc/image-guide/bk-imageguide.xml27(releaseinfo) +msgid "havana" +msgstr "" + +#: ./doc/image-guide/bk-imageguide.xml28(productname) +msgid "OpenStack" +msgstr "" + +#: ./doc/image-guide/bk-imageguide.xml32(remark) +msgid "Remaining licensing details are filled in by the template." +msgstr "" + +#: ./doc/image-guide/bk-imageguide.xml37(para) +msgid "" +"This guide describes how to obtain, create, and modify virtual machine " +"images that are compatible with OpenStack." +msgstr "" + +#: ./doc/image-guide/bk-imageguide.xml44(date) +msgid "2013-10-25" +msgstr "" + +#: ./doc/image-guide/bk-imageguide.xml48(para) +msgid "Adds information about image formats, properties." +msgstr "" + +#: ./doc/image-guide/bk-imageguide.xml54(date) +msgid "2013-10-17" +msgstr "" + +#: ./doc/image-guide/bk-imageguide.xml58(para) +msgid "Havana release." +msgstr "" + +#: ./doc/image-guide/bk-imageguide.xml64(date) +msgid "2013-06-04" +msgstr "" + +#: ./doc/image-guide/bk-imageguide.xml68(para) +msgid "Updated title for consistency." +msgstr "" + +#: ./doc/image-guide/bk-imageguide.xml74(date) +msgid "2013-05-28" +msgstr "" + +#: ./doc/image-guide/bk-imageguide.xml78(para) +msgid "Initial release of this guide." +msgstr "" + +#. When image changes, this message will be marked fuzzy or untranslated for +#. you. +#. It doesn't matter what you translate it to: it's not used at all. +#: ./doc/image-guide/section_ubuntu-example.xml50(None) +msgid "" +"@@image: 'figures/ubuntu-install.png'; md5=a1f2ab707b7bc3122e20e6e0e4580887" +msgstr "" + +#. When image changes, this message will be marked fuzzy or untranslated for +#. you. +#. It doesn't matter what you translate it to: it's not used at all. +#: ./doc/image-guide/section_ubuntu-example.xml104(None) +msgid "" +"@@image: 'figures/ubuntu-software-selection.png'; " +"md5=423be828f701345f7d20551a39f24271" +msgstr "" + +#. When image changes, this message will be marked fuzzy or untranslated for +#. you. +#. It doesn't matter what you translate it to: it's not used at all. +#: ./doc/image-guide/section_ubuntu-example.xml115(None) +msgid "" +"@@image: 'figures/ubuntu-grub.png'; md5=e46a46bd4044483da7cd07de2ff1ddbc" +msgstr "" + +#. When image changes, this message will be marked fuzzy or untranslated for +#. you. +#. It doesn't matter what you translate it to: it's not used at all. +#: ./doc/image-guide/section_ubuntu-example.xml128(None) +msgid "" +"@@image: 'figures/ubuntu-finished.png'; md5=750be1d6a71b4186be563c049043e3a4" +msgstr "" + +#: ./doc/image-guide/section_ubuntu-example.xml6(title) +msgid "Example: Ubuntu image" +msgstr "" + +#: ./doc/image-guide/section_ubuntu-example.xml7(para) +msgid "" +"We'll run through an example of installing an Ubuntu image. This will focus " +"mainly on Ubuntu 12.04 (Precise Pangolin) server. Because the Ubuntu " +"installation process may change across versions, if you are using a " +"different version of Ubuntu the installer steps may differ." +msgstr "" + +#: ./doc/image-guide/section_ubuntu-example.xml13(title) +msgid "Download an Ubuntu install ISO" +msgstr "" + +#: ./doc/image-guide/section_ubuntu-example.xml14(para) +msgid "" +"In this example, we'll use the network installation ISO, since it's a " +"smaller image. The 64-bit 12.04 network installer ISO is at http://archive.ubuntu.com/ubuntu/dists/precise/main" +"/installer-amd64/current/images/netboot/mini.iso" +msgstr "" + +#: ./doc/image-guide/section_ubuntu-example.xml28(para) +msgid "" +"We will assume the name of your virtual machine image is " +"ubuntu-12.04, which we need to know when using " +" commands to manipulate the state of the image." +msgstr "" + +#: ./doc/image-guide/section_ubuntu-example.xml44(para) +msgid "" +"At the initial Installer boot menu, choose the \"Install\" option. Step " +"through the install prompts, the defaults should be fine." +msgstr "" + +#: ./doc/image-guide/section_ubuntu-example.xml56(para) +msgid "" +"The installer may ask you to choose a hostname. The default " +"(ubuntu) is fine. We will install the cloud-init package " +"later, which will set the hostname on boot when a new instance is " +"provisioned using this image." +msgstr "" + +#: ./doc/image-guide/section_ubuntu-example.xml64(title) +msgid "Select a mirror" +msgstr "" + +#: ./doc/image-guide/section_ubuntu-example.xml65(para) +msgid "The default mirror proposed by the installer should be fine." +msgstr "" + +#: ./doc/image-guide/section_ubuntu-example.xml70(para) +msgid "" +"Step through the install, using the default options. When prompted for a " +"username, the default (ubuntu) is fine." +msgstr "" + +#: ./doc/image-guide/section_ubuntu-example.xml88(title) +msgid "Automatic updates" +msgstr "" + +#: ./doc/image-guide/section_ubuntu-example.xml89(para) +msgid "" +"The Ubuntu installer will ask how you want to manage upgrades on your " +"system. This option depends upon your specific use case. If your virtual " +"machine instances will be able to connect to the internet, we recommend " +"\"Install security updates automatically\"." +msgstr "" + +#: ./doc/image-guide/section_ubuntu-example.xml96(title) +msgid "Software selection: OpenSSH server" +msgstr "" + +#: ./doc/image-guide/section_ubuntu-example.xml97(para) +msgid "" +"Choose \"OpenSSH server\"so that you will be able to SSH into the virtual " +"machine when it launches inside of an OpenStack cloud." +msgstr "" + +#: ./doc/image-guide/section_ubuntu-example.xml109(title) +msgid "Install GRUB boot loader" +msgstr "" + +#: ./doc/image-guide/section_ubuntu-example.xml110(para) +msgid "" +"Select \"Yes\" when asked about installing the GRUB boot loader to the " +"master boot record." +msgstr "" + +#: ./doc/image-guide/section_ubuntu-example.xml121(para) +msgid "" +"Select the defaults for all of the remaining options. When the installation " +"is complete, you will be prompted to remove the CD-ROM." +msgstr "" + +#: ./doc/image-guide/section_ubuntu-example.xml133(para) +msgid "" +"When you hit \"Continue\" the virtual machine will shut down, even though it" +" says it will reboot." +msgstr "" + +#: ./doc/image-guide/section_ubuntu-example.xml160(para) +msgid "" +"Run the following commands in the host as root to start up the machine again" +" as paused, eject the disk and resume. If you are using virt-manager, you " +"may instead use the GUI." +msgstr "" + +#: ./doc/image-guide/section_ubuntu-example.xml167(para) +msgid "" +"In the example above, we start the instance paused, eject the disk, and then" +" unpause. In theory, we could have ejected the disk at the \"Installation " +"complete\" screen. However, our testing indicates that the Ubuntu installer " +"locks the drive so that it cannot be ejected at that point." +msgstr "" + +#: ./doc/image-guide/section_ubuntu-example.xml177(para) +msgid "" +"When you boot the first time after install, it may ask you about " +"authentication tools, you can just choose 'Exit'. Then, log in as root using" +" the root password you specified." +msgstr "" + +#: ./doc/image-guide/section_ubuntu-example.xml183(title) +msgid "Install cloud-init" +msgstr "" + +#: ./doc/image-guide/section_ubuntu-example.xml184(para) +msgid "" +"The script starts on instance boot and will search for a " +"metadata provider to fetch a public key from. The public key will be placed " +"in the default user account for the image." +msgstr "" + +#: ./doc/image-guide/section_ubuntu-example.xml188(para) +msgid "Install the cloud-init package:" +msgstr "" + +#: ./doc/image-guide/section_ubuntu-example.xml190(para) +msgid "" +"When building Ubuntu images must be explicitly configured " +"for the metadata source in use. The OpenStack metadata server emulates the " +"EC2 metadata service used by images in Amazon EC2." +msgstr "" + +#: ./doc/image-guide/section_ubuntu-example.xml195(para) +msgid "" +"To set the metadata source to be used by the image run the " +"command against the cloud-init package. When prompted " +"select the EC2 data source: " +msgstr "" + +#: ./doc/image-guide/section_ubuntu-example.xml205(para) +msgid "" +"You can change the name of the account used by cloud-init by editing the " +"/etc/cloud/cloud.cfg file and adding a line with a " +"different user. For example, to configure cloud-init to put the key in an " +"account named \"admin\", edit the config file so it has the " +"line:" +msgstr "" + +#: ./doc/image-guide/section_ubuntu-example.xml220(para) +msgid "" +"The operating system records the MAC address of the virtual ethernet card in" +" locations such as /etc/udev/rules.d/70-persistent-" +"net.rules during the instance process. However, each time the " +"image boots up, the virtual ethernet card will have a different MAC address," +" so this information must be deleted from the configuration file." +msgstr "" + +#: ./doc/image-guide/section_ubuntu-example.xml235(para) +msgid "" +"Now that the image is ready to be uploaded to the Image service, we know " +"longer need to have this virtual machine image managed by libvirt. Use the " +" command to inform libvirt" +msgstr "" + +#: ./doc/image-guide/section_ubuntu-example.xml244(para) +msgid "" +"The underlying image file that you created with , such as " +"/tmp/precise.qcow2, is now ready for uploading to the " +"OpenStack Image service." +msgstr "" + +#: ./doc/image-guide/ch_introduction.xml6(title) +msgid "Introduction" +msgstr "" + +#: ./doc/image-guide/ch_introduction.xml7(para) +msgid "" +"An OpenStack Compute cloud is not very useful unless you have virtual " +"machine images (which some people call \"virtual appliances\"). This guide " +"describes how to obtain, create, and modify virtual machine images that are " +"compatible with OpenStack." +msgstr "" + +#: ./doc/image-guide/ch_introduction.xml10(para) +msgid "" +"To keep things brief, we'll sometimes use the term \"image\" instead of " +"\"virtual machine image\"." +msgstr "" + +#: ./doc/image-guide/ch_introduction.xml12(para) +msgid "What is a virtual machine image?" +msgstr "" + +#: ./doc/image-guide/ch_introduction.xml13(para) +msgid "" +"A virtual machine image is a single file which contains a virtual disk that " +"has a bootable operating system installed on it." +msgstr "" + +#: ./doc/image-guide/ch_introduction.xml15(para) +msgid "" +"Virtual machine images come in different formats, some of which are " +"described below. In a later chapter, we'll describe how to convert between " +"formats." +msgstr "" + +#: ./doc/image-guide/ch_introduction.xml19(term) +msgid "Raw" +msgstr "" + +#: ./doc/image-guide/ch_introduction.xml26(para) +msgid "" +"We don't recommend creating raw images by dd'ing block device files, we " +"discuss how to create raw images later." +msgstr "" + +#: ./doc/image-guide/ch_introduction.xml20(para) +msgid "" +"The \"raw\" image format is the simplest one, and is natively supported by " +"both KVM and Xen hypervisors. You can think of a raw image as being the bit-" +"equivalent of a block device file, created as if somebody had copied, say, " +"/dev/sda to a file using the command. " +"" +msgstr "" + +#: ./doc/image-guide/ch_introduction.xml32(term) +#: ./doc/image-guide/ch_converting.xml26(td) +#: ./doc/image-guide/ch_converting.xml27(literal) +msgid "qcow2" +msgstr "" + +#: ./doc/image-guide/ch_introduction.xml37(para) +msgid "Using sparse representation, so the image size is smaller" +msgstr "" + +#: ./doc/image-guide/ch_introduction.xml40(para) +msgid "Support for snapshots" +msgstr "" + +#: ./doc/image-guide/ch_introduction.xml33(para) +msgid "" +"The qcow2 " +"(QEMU copy-on-write version 2) format is commonly used with the KVM " +"hypervisor. It has some additional features over the raw format, such " +"as:" +msgstr "" + +#: ./doc/image-guide/ch_introduction.xml43(para) +msgid "" +"Because qcow2 is sparse, it's often faster to convert a raw image to qcow2 " +"and upload it then to upload the raw file." +msgstr "" + +#: ./doc/image-guide/ch_introduction.xml47(para) +msgid "" +"Because raw images don't support snapshots, OpenStack Compute will " +"automatically convert raw image files to qcow2 as needed." +msgstr "" + +#: ./doc/image-guide/ch_introduction.xml53(term) +msgid "AMI/AKI/ARI" +msgstr "" + +#: ./doc/image-guide/ch_introduction.xml59(para) +msgid "AMI (Amazon Machine Image):" +msgstr "" + +#: ./doc/image-guide/ch_introduction.xml60(para) +msgid "This is a virtual machine image in raw format, as described above." +msgstr "" + +#: ./doc/image-guide/ch_introduction.xml64(para) +msgid "AKI (Amazon Kernel Image)" +msgstr "" + +#: ./doc/image-guide/ch_introduction.xml65(para) +msgid "" +"A kernel file that the hypervisor will load initially to boot the image. For" +" a Linux machine, this would be a vmlinuz file." +msgstr "" + +#: ./doc/image-guide/ch_introduction.xml72(para) +msgid "ARI (Amazon Ramdisk Image)" +msgstr "" + +#: ./doc/image-guide/ch_introduction.xml73(para) +msgid "" +"An optional ramdisk file mounted at boot time. For a Linux machine, this " +"would be an initrd file." +msgstr "" + +#: ./doc/image-guide/ch_introduction.xml54(para) +msgid "" +"The AMI/AKI/ARI" +" format was the initial image format supported by Amazon EC2. The " +"image consists of three files:" +msgstr "" + +#: ./doc/image-guide/ch_introduction.xml81(term) +msgid "UEC tarball" +msgstr "" + +#: ./doc/image-guide/ch_introduction.xml84(para) +msgid "" +"Ubuntu Enterprise Cloud refers to a discontinued Eucalyptus-based Ubuntu " +"cloud solution that has been replaced by the OpenStack-based Ubuntu Cloud " +"Infrastructure." +msgstr "" + +#: ./doc/image-guide/ch_introduction.xml82(para) +msgid "" +"A UEC (Ubuntu Enterprise Cloud) tarball is a gzipped tarfile that contains " +"an AMI file, AKI file, and ARI file." +msgstr "" + +#: ./doc/image-guide/ch_introduction.xml90(term) +msgid "VMDK" +msgstr "" + +#: ./doc/image-guide/ch_introduction.xml91(para) +msgid "" +"VMWare's ESXi hypervisor uses the VMDK (Virtual Machine " +"Disk) format for images." +msgstr "" + +#: ./doc/image-guide/ch_introduction.xml96(term) +msgid "VDI" +msgstr "" + +#: ./doc/image-guide/ch_introduction.xml97(para) +msgid "" +"VirtualBox uses the VDI " +"(Virtual Disk Image) format for image files. None of the OpenStack Compute " +"hypervisors support VDI directly, so you will need to convert these files to" +" a different format to use them with OpenStack." +msgstr "" + +#: ./doc/image-guide/ch_introduction.xml104(term) +msgid "VHD" +msgstr "" + +#: ./doc/image-guide/ch_introduction.xml105(para) +msgid "Microsoft Hyper-V uses the VHD (Virtual Hard Disk) format for images." +msgstr "" + +#: ./doc/image-guide/ch_introduction.xml108(term) +msgid "VHDX" +msgstr "" + +#: ./doc/image-guide/ch_introduction.xml109(para) +msgid "" +"The version of Hyper-V that ships with Microsoft Server 2012 uses the newer " +"VHDX format, which has some additional " +"features over VHD such as support for larger disk sizes and protection " +"against data corruption during power failures." +msgstr "" + +#: ./doc/image-guide/ch_introduction.xml115(term) +msgid "OVF" +msgstr "" + +#: ./doc/image-guide/ch_introduction.xml116(para) +msgid "" +"OVF (Open " +"Virtualization Format) is a packaging format for virtual machines, defined " +"by the Distributed Management Task Force (DMTF) standards group. An OVF " +"package contains one or more image files, a .ovf XML metadata file that " +"contains information about the virtual machine, and possibly other files as " +"well." +msgstr "" + +#: ./doc/image-guide/ch_introduction.xml121(para) +msgid "" +"An OVF package can be distributed in different ways. For example, it could " +"be distributed as a set of discrete files, or as a tar archive file with an " +".ova (open virtual appliance/application) extension." +msgstr "" + +#: ./doc/image-guide/ch_introduction.xml124(para) +msgid "" +"OpenStack Compute does not currently have support for OVF packages, so you " +"will need to extract the image file(s) from an OVF package if you wish to " +"use it with OpenStack." +msgstr "" + +#: ./doc/image-guide/ch_introduction.xml129(term) +msgid "ISO" +msgstr "" + +#: ./doc/image-guide/ch_introduction.xml130(para) +msgid "" +"The ISO format is" +" a disk image formatted with the read-only ISO 9660 (also known as ECMA-119)" +" filesystem commonly used for CDs and DVDs. While we don't normally think of" +" ISO a virtual machine image format, since ISOs contain bootable filesystems" +" with an installed operating system, you can treat them the same you treat " +"other virtual machine image files." +msgstr "" + +#: ./doc/image-guide/ch_creating_images_automatically.xml6(title) +msgid "Tool support for image creation" +msgstr "" + +#: ./doc/image-guide/ch_creating_images_automatically.xml8(para) +msgid "There are several tools that are designed to automate image creation." +msgstr "" + +#: ./doc/image-guide/ch_creating_images_automatically.xml11(title) +msgid "Oz" +msgstr "" + +#: ./doc/image-guide/ch_creating_images_automatically.xml22(para) +msgid "" +"As of this writing, there are no Oz packages for Ubuntu, so you will need to" +" either install from source or build your own .deb file." +msgstr "" + +#: ./doc/image-guide/ch_creating_images_automatically.xml12(para) +msgid "" +"Oz is a " +"command-line tool that automates the process of creating a virtual machine " +"image file. Oz is a Python app that interacts with KVM to step through the " +"process of installing a virtual machine. It uses a predefined set of " +"kickstart (Red Hat-based systems) and preseed files (Debian-based systems) " +"for operating systems that it supports, and it can also be used to create " +"Microsoft Windows images. On Fedora, install Oz with " +"yum:" +msgstr "" + +#: ./doc/image-guide/ch_creating_images_automatically.xml26(para) +msgid "" +"A full treatment of Oz is beyond the scope of this document, but we will " +"provide an example. You can find additional examples of Oz template files on" +" github at rackerjoe/oz-image-build/templates. " +"Here's how you would create a CentOS 6.4 image with Oz." +msgstr "" + +#: ./doc/image-guide/ch_creating_images_automatically.xml33(para) +msgid "" +"Create a template file (we'll call it centos64.tdl) " +"with the following contents. The only entry you will need to change is the " +"<rootpw> contents." +msgstr "" + +#: ./doc/image-guide/ch_creating_images_automatically.xml71(para) +msgid "" +"This Oz template specifies where to download the Centos 6.4 install ISO. Oz " +"will use the version information to identify which kickstart file to use. In" +" this case, it will be RHEL6.auto." +" It adds EPEL as a repository and install the epel-" +"release, cloud-utils, and cloud-" +"init packages, as specified in the packages " +"section of the file." +msgstr "" + +#: ./doc/image-guide/ch_creating_images_automatically.xml82(para) +msgid "" +"After Oz does the initial OS install using the kickstart file, it customizes" +" the image by doing an update. It also removes any reference to the eth0 " +"device that libvirt creates while Oz does the customizing, as specified in " +"the command section of the XML file." +msgstr "" + +#: ./doc/image-guide/ch_creating_images_automatically.xml88(para) +msgid "To run this, do, as root:" +msgstr "" + +#: ./doc/image-guide/ch_creating_images_automatically.xml91(para) +msgid "" +"The -d3 flag tells Oz to show status information as it " +"runs." +msgstr "" + +#: ./doc/image-guide/ch_creating_images_automatically.xml95(para) +msgid "" +"The -u tells Oz to do the customization (install extra " +"packages, run the commands) once it does the initial install." +msgstr "" + +#: ./doc/image-guide/ch_creating_images_automatically.xml101(para) +msgid "" +"The -x <filename> flag tells Oz what filename to " +"use to write out a libvirt XML file (otherwise it will default to something " +"like centos64Apr_03_2013-12:39:42." +msgstr "" + +#: ./doc/image-guide/ch_creating_images_automatically.xml89(para) +msgid "" +"If you leave out the -u " +"flag, or you want to edit the file to do additional customizations, you can " +"use the command, using the libvirt XML file that " +" creates. For example: Oz will invoke " +"libvirt to boot the image inside of KVM, then Oz will ssh into the instance " +"and perform the customizations." +msgstr "" + +#: ./doc/image-guide/ch_creating_images_automatically.xml119(title) +msgid "VMBuilder" +msgstr "" + +#: ./doc/image-guide/ch_creating_images_automatically.xml120(para) +msgid "" +"VMBuilder (Virtual " +"Machine Builder) is a command-line tool that creates virtual machine images " +"for different hypervisors. The version of VMBuilder that ships with Ubuntu " +"can only create Ubuntu virtual machine guests. The version of VMBuilder that" +" ships with Debian can create Ubuntu and Debian virtual machine guests." +msgstr "" + +#: ./doc/image-guide/ch_creating_images_automatically.xml127(para) +msgid "" +"The Ubuntu Server Guide has " +"documentation on how to use VMBuilder to create an Ubuntu image." +msgstr "" + +#: ./doc/image-guide/ch_creating_images_automatically.xml134(title) +msgid "BoxGrinder" +msgstr "" + +#: ./doc/image-guide/ch_creating_images_automatically.xml135(para) +msgid "" +"BoxGrinder  is another tool for" +" creating virtual machine images, which it calls appliances. BoxGrinder can " +"create Fedora, Red Hat Enterprise Linux, or CentOS images. BoxGrinder is " +"currently only supported on Fedora." +msgstr "" + +#: ./doc/image-guide/ch_creating_images_automatically.xml144(title) +msgid "VeeWee" +msgstr "" + +#: ./doc/image-guide/ch_creating_images_automatically.xml145(para) +msgid "" +" VeeWee is often " +"used to build Vagrant boxes, but " +"it can also be used to build KVM images." +msgstr "" + +#: ./doc/image-guide/ch_creating_images_automatically.xml151(title) +msgid "imagefactory" +msgstr "" + +#: ./doc/image-guide/ch_creating_images_automatically.xml152(para) +msgid "" +"imagefactory is a newer tool " +"designed to automate the building, converting, and uploading images to " +"different cloud providers. It uses Oz as its back-end and includes support " +"for OpenStack-based clouds." +msgstr "" + +#: ./doc/image-guide/ch_creating_images_automatically.xml159(title) +msgid "SUSE Studio" +msgstr "" + +#: ./doc/image-guide/ch_creating_images_automatically.xml160(para) +msgid "" +"SUSE Studio is a web application" +" for building and testing software applications in a web browser. It " +"supports the creation of physical, virtual or cloud-based applications and " +"includes support for building images for OpenStack based clouds using SUSE " +"Linux Enterprise and openSUSE as distributions." +msgstr "" + +#: ./doc/image-guide/ch_openstack_images.xml6(title) +msgid "OpenStack Linux image requirements" +msgstr "" + +#: ./doc/image-guide/ch_openstack_images.xml17(para) +#: ./doc/image-guide/ch_openstack_images.xml44(title) +msgid "Disk partitions and resize root partition on boot (cloud-init)" +msgstr "" + +#: ./doc/image-guide/ch_openstack_images.xml21(para) +#: ./doc/image-guide/ch_openstack_images.xml221(title) +msgid "No hard-coded MAC address information" +msgstr "" + +#: ./doc/image-guide/ch_openstack_images.xml24(para) +msgid "SSH server running" +msgstr "" + +#: ./doc/image-guide/ch_openstack_images.xml27(para) +#: ./doc/image-guide/ch_openstack_images.xml266(title) +msgid "Disable firewall" +msgstr "" + +#: ./doc/image-guide/ch_openstack_images.xml30(para) +#: ./doc/image-guide/ch_openstack_images.xml275(title) +msgid "Access instance using ssh public key (cloud-init)" +msgstr "" + +#: ./doc/image-guide/ch_openstack_images.xml34(para) +#: ./doc/image-guide/ch_openstack_images.xml358(title) +msgid "Process user data and other metadata (cloud-init)" +msgstr "" + +#: ./doc/image-guide/ch_openstack_images.xml38(para) +msgid "" +"Paravirtualized Xen support in Linux kernel (Xen hypervisor only with Linux " +"kernel version < 3.0)" +msgstr "" + +#: ./doc/image-guide/ch_openstack_images.xml8(para) +msgid "" +"For a Linux-based image to have full functionality in an OpenStack Compute " +"cloud, there are a few requirements. For some of these, the requirement can " +"be fulfilled by installing the cloud-init " +"package. You should read this section before creating your own image to be " +"sure that the image supports the OpenStack features you plan on " +"using." +msgstr "" + +#: ./doc/image-guide/ch_openstack_images.xml46(para) +msgid "" +"When you create a new Linux image, the first decision you will need to make " +"is how to partition the disks. The choice of partition method can affect the" +" resizing functionality, as described below." +msgstr "" + +#: ./doc/image-guide/ch_openstack_images.xml50(para) +msgid "" +"The size of the disk in a virtual machine image is determined when you " +"initially create the image. However, OpenStack lets you launch instances " +"with different size drives by specifying different flavors. For example, if " +"your image was created with a 5 GB disk, and you launch an instance with a " +"flavor of m1.small. The resulting virtual machine " +"instance has, by default, a primary disk size of 10 GB. When an instance's " +"disk is resized up, zeros are just added to the end." +msgstr "" + +#: ./doc/image-guide/ch_openstack_images.xml59(para) +msgid "" +"Your image needs to be able to resize its partitions on boot to match the " +"size requested by the user. Otherwise, after the instance boots, you will " +"need to manually resize the partitions if you want to access the additional " +"storage you have access to when the disk size associated with the flavor " +"exceeds the disk size your image was created with." +msgstr "" + +#: ./doc/image-guide/ch_openstack_images.xml67(title) +msgid "Xen: 1 ext3/ext4 partition (no LVM, no /boot, no swap)" +msgstr "" + +#: ./doc/image-guide/ch_openstack_images.xml74(para) +msgid "" +"auto_disk_config=True is set as a property on the image " +"in the Image Registry." +msgstr "" + +#: ./doc/image-guide/ch_openstack_images.xml79(para) +msgid "The disk on the image has only one partition." +msgstr "" + +#: ./doc/image-guide/ch_openstack_images.xml83(para) +msgid "The file system on the one partition is ext3 or ext4." +msgstr "" + +#: ./doc/image-guide/ch_openstack_images.xml69(para) +msgid "" +"If you are using the OpenStack XenAPI driver, the Compute service will " +"automatically adjust the partition and filesystem for your instance on boot." +" Automatic resize will occur if the following are all true:" +msgstr "" + +#: ./doc/image-guide/ch_openstack_images.xml87(para) +msgid "" +"Therefore, if you are using Xen, we recommend that when you create your " +"images, you create a single ext3 or ext4 partition (not managed by LVM). " +"Otherwise, read on." +msgstr "" + +#: ./doc/image-guide/ch_openstack_images.xml93(title) +msgid "" +"Non-Xen with cloud-init/cloud-tools: 1 ext3/ext4 partition (no LVM, no " +"/boot, no swap)" +msgstr "" + +#: ./doc/image-guide/ch_openstack_images.xml97(para) +msgid "The image's partition table describes the original size of the image" +msgstr "" + +#: ./doc/image-guide/ch_openstack_images.xml101(para) +msgid "The image's filesystem fills the original size of the image" +msgstr "" + +#: ./doc/image-guide/ch_openstack_images.xml95(para) +msgid "Your image must be configured to deal with two issues:" +msgstr "" + +#: ./doc/image-guide/ch_openstack_images.xml110(para) +msgid "" +"If you are not using LVM, you must modify the table to extend the existing " +"root partition to encompass this additional space" +msgstr "" + +#: ./doc/image-guide/ch_openstack_images.xml117(para) +msgid "" +"If you are using LVM, you can create add a new LVM entry to the partition " +"table, create a new LVM physical volume, add it to the volume group, and " +"extend the logical partition with the root volume" +msgstr "" + +#: ./doc/image-guide/ch_openstack_images.xml107(para) +msgid "" +"the partition table must be modified to be made aware of the additional " +"space" +msgstr "" + +#: ./doc/image-guide/ch_openstack_images.xml128(para) +msgid "the root volume filesystem must be resized" +msgstr "" + +#: ./doc/image-guide/ch_openstack_images.xml105(para) +msgid "Then, during the boot process:" +msgstr "" + +#: ./doc/image-guide/ch_openstack_images.xml132(para) +msgid "" +"The simplest way to support this in your image is to install the cloud-utils package " +"(contains the tool for extending partitions), the cloud-initramfs-" +"tools package (which will support resizing root partition on the " +"first boot), and the cloud-" +"init package into your image. With these installed, the image will " +"perform the root partition resize on boot. For example, in the " +"/etc/rc.local file. These packages are in the Ubuntu " +"and Debian package repository, as well as the EPEL repository (for " +"Fedora/RHEL/CentOS/Scientific Linux guests)." +msgstr "" + +#: ./doc/image-guide/ch_openstack_images.xml150(para) +msgid "" +"If you are not able to install cloud-initramfs-tools, " +"Robert Plestenjak has a github project called linux-rootfs-" +"resize that contains scripts that will update a ramdisk using " +" so that the image will resize properly on boot." +msgstr "" + +#: ./doc/image-guide/ch_openstack_images.xml158(para) +msgid "" +"If you are able to install the cloud-utils and cloud-init packages, we " +"recommend that when you create your images, you create a single ext3 or ext4" +" partition (not managed by LVM)." +msgstr "" + +#: ./doc/image-guide/ch_openstack_images.xml164(title) +msgid "Non-Xen without cloud-init/cloud-tools: LVM" +msgstr "" + +#: ./doc/image-guide/ch_openstack_images.xml165(para) +msgid "" +"If you cannot install cloud-init and cloud-tools inside of your guest, and " +"you want to support resize, you will need to write a script that your image " +"will run on boot to modify the partition table. In this case, we recommend " +"using LVM to manage your partitions. Due to a limitation in the Linux kernel" +" (as of this writing), you cannot modify a partition table of a raw disk " +"that has partition currently mounted, but you can do this for LVM." +msgstr "" + +#: ./doc/image-guide/ch_openstack_images.xml176(para) +msgid "" +"Detect if any additional space is available on the disk. For example, parse " +"the output of ." +msgstr "" + +#: ./doc/image-guide/ch_openstack_images.xml183(para) +msgid "" +"Create a new LVM partition with the additional space. For example, " +"." +msgstr "" + +#: ./doc/image-guide/ch_openstack_images.xml191(replaceable) +#: ./doc/image-guide/ch_openstack_images.xml198(replaceable) +#: ./doc/image-guide/ch_openstack_images.xml205(replaceable) +msgid "sda6" +msgstr "" + +#: ./doc/image-guide/ch_openstack_images.xml189(para) +msgid "Create a new physical volume. For example, ." +msgstr "" + +#: ./doc/image-guide/ch_openstack_images.xml197(replaceable) +msgid "vg00" +msgstr "" + +#: ./doc/image-guide/ch_openstack_images.xml194(para) +msgid "" +"Extend the volume group with this physical partition. For example, " +".)" +msgstr "" + +#: ./doc/image-guide/ch_openstack_images.xml204(replaceable) +#: ./doc/image-guide/ch_openstack_images.xml210(replaceable) +msgid "node-root" +msgstr "" + +#: ./doc/image-guide/ch_openstack_images.xml201(para) +msgid "" +"Extend the logical volume contained the root partition by the amount of " +"space. For example, ." +msgstr "" + +#: ./doc/image-guide/ch_openstack_images.xml208(para) +msgid "Resize the root file system. For example, ." +msgstr "" + +#: ./doc/image-guide/ch_openstack_images.xml174(para) +msgid "" +"Your script will need to do something like the following:" +msgstr "" + +#: ./doc/image-guide/ch_openstack_images.xml213(para) +msgid "" +"You do not need to have a /boot partition, unless your " +"image is an older Linux distribution that requires that " +"/boot is not managed by LVM. You may elect to use a " +"swap per" +msgstr "" + +#: ./doc/image-guide/ch_openstack_images.xml231(para) +msgid "" +"Replace /etc/udev/rules.d/70-persistent-net.rules with " +"an empty file (contains network persistence rules, including MAC address)" +msgstr "" + +#: ./doc/image-guide/ch_openstack_images.xml238(para) +msgid "" +"Replace /lib/udev/rules.d/75-persistent-net-" +"generator.rules with an empty file (this generates the file " +"above)" +msgstr "" + +#: ./doc/image-guide/ch_openstack_images.xml244(para) +msgid "" +"Remove the HWADDR line from /etc/sysconfig/network-scripts/ifcfg-" +"eth0 on Fedora-based images" +msgstr "" + +#: ./doc/image-guide/ch_openstack_images.xml249(para) +msgid "" +"If you delete the network persistent rules files, you may get a udev kernel " +"warning at boot time, which is why we recommend replacing them with empty " +"files instead." +msgstr "" + +#: ./doc/image-guide/ch_openstack_images.xml222(para) +msgid "" +"You must remove the network persistence rules in the image as their presence" +" will result in the network interface in the instance coming up as an " +"interface other than eth0. This is because your image has a record of the " +"MAC address of the network interface card when it was first installed, and " +"this MAC address will be different each time the instance boots up. You " +"should alter the following files:" +msgstr "" + +#: ./doc/image-guide/ch_openstack_images.xml257(title) +msgid "Ensure ssh server runs" +msgstr "" + +#: ./doc/image-guide/ch_openstack_images.xml258(para) +msgid "" +"You must install an ssh server into the image and ensure that it starts up " +"on boot, or you will not be able to connect to your instance using ssh when " +"it boots inside of OpenStack. This package is typically called openssh-server." +msgstr "" + +#: ./doc/image-guide/ch_openstack_images.xml267(para) +msgid "" +"In general, we recommend that you disable any firewalls inside of your image" +" and use OpenStack security groups to restrict access to instances. The " +"reason is that having a firewall installed on your instance can make it more" +" difficult to troubleshoot networking issues if you cannot connect to your " +"instance." +msgstr "" + +#: ./doc/image-guide/ch_openstack_images.xml277(para) +msgid "" +"The typical way that users access virtual machines running on OpenStack is " +"to ssh using public key authentication. For this to work, your virtual " +"machine image must be configured to download the ssh public key from the " +"OpenStack metadata service or config drive, at boot time." +msgstr "" + +#: ./doc/image-guide/ch_openstack_images.xml285(para) +msgid "" +"The cloud-init package will automatically fetch the public key from the " +"metadata server and place the key in an account. The account varies by " +"distribution. On Ubuntu-based virtual machines, the account is called " +"\"ubuntu\". On Fedora-based virtual machines, the account is called " +"\"ec2-user\"." +msgstr "" + +#: ./doc/image-guide/ch_openstack_images.xml301(title) +msgid "Write a custom script to fetch the public key" +msgstr "" + +#: ./doc/image-guide/ch_openstack_images.xml303(para) +msgid "" +"If you are unable or unwilling to install cloud-init inside the guest, you " +"can write a custom script to fetch the public and add it to a user account." +msgstr "" + +#: ./doc/image-guide/ch_openstack_images.xml306(para) +msgid "" +"To fetch the ssh public key and add it to the root account, edit the " +"/etc/rc.local file and add the following lines before " +"the line “touch /var/lock/subsys/local”. This code fragment is taken from " +"the rackerjoe oz-image-build " +"CentOS 6 template." +msgstr "" + +#: ./doc/image-guide/ch_openstack_images.xml346(para) +msgid "" +"Some VNC clients replace : (colon) with ; (semicolon) and _ (underscore) " +"with - (hyphen). If editing a file over a VNC session, make sure it's http: " +"not http; and authorized_keys not authorized-keys." +msgstr "" + +#: ./doc/image-guide/ch_openstack_images.xml360(para) +msgid "" +"In additional the ssh public key, an image may need to retrieve additional " +"information from OpenStack, such as user data that the user " +"submitted when requesting the image. For example, you might want to set the " +"host name of the instance to name given to the instance when it is booted. " +"Or, you might wish to configure your image so that it executes user data " +"content as a script on boot." +msgstr "" + +#: ./doc/image-guide/ch_openstack_images.xml370(para) +msgid "" +"This information is accessible through the metadata service or the config drive. As the OpenStack metadata service is " +"compatible with version 2009-04-04 of the Amazon EC2 metadata service, " +"consult the Amazon EC2 documentation on Using Instance Metadata for details on " +"how to retrieve user data." +msgstr "" + +#: ./doc/image-guide/ch_openstack_images.xml381(para) +msgid "" +"The easiest way to support this type of functionality is to install the " +"cloud-init package into your image, which is configured by default to treat " +"user data as an executable script, and will set the host name." +msgstr "" + +#: ./doc/image-guide/ch_openstack_images.xml387(title) +msgid "Ensure image writes boot log to console" +msgstr "" + +#: ./doc/image-guide/ch_openstack_images.xml388(para) +msgid "" +"You must configure the image so that the kernel writes the boot log to the " +"ttyS0 device. In particular, the " +"console=ttyS0 argument must be passed to the kernel on " +"boot." +msgstr "" + +#: ./doc/image-guide/ch_openstack_images.xml392(para) +msgid "" +"If your image uses grub2 as the boot loader, there should be a line in the " +"grub configuration file. For example, " +"/boot/grub/grub.cfg, which looks something like this:" +msgstr "" + +#: ./doc/image-guide/ch_openstack_images.xml397(para) +msgid "" +"If console=ttyS0 does not appear, you will need to modify" +" your grub configuration. In general, you should not update the grub.cfg " +"directly, since it is automatically generated. Instead, you should edit " +"/etc/default/grub and modify the value of the " +"GRUB_CMDLINE_LINUX_DEFAULT variable: " +msgstr "" + +#: ./doc/image-guide/ch_openstack_images.xml405(para) +msgid "" +"Next, update the grub configuration. On Debian-based operating-systems such " +"as Ubuntu, do:" +msgstr "" + +#: ./doc/image-guide/ch_openstack_images.xml408(para) +msgid "On Fedora-based systems such as RHEL and CentOS, do:" +msgstr "" + +#: ./doc/image-guide/ch_openstack_images.xml413(title) +msgid "Paravirtualized Xen support in the kernel (Xen hypervisor only)" +msgstr "" + +#: ./doc/image-guide/ch_openstack_images.xml415(para) +msgid "" +"Prior to Linux kernel version 3.0, the mainline branch of the Linux kernel " +"did not have support paravirtualized Xen virtual machine instances (what Xen" +" calls DomU guests). If you are running the Xen hypervisor with " +"paravirtualization, and you want to create an image for an older Linux " +"distribution that has a pre 3.0 kernel, you will need to ensure that the " +"image boots a kernel that has been compiled with Xen support." +msgstr "" + +#: ./doc/image-guide/ch_openstack_images.xml425(title) +msgid "Manage the image cache" +msgstr "" + +#: ./doc/image-guide/ch_openstack_images.xml426(para) +msgid "" +"Use options in nova.conf to control whether, and for " +"how long, unused base images are stored in " +"/var/lib/nova/instances/_base/. If you have configured " +"live migration of instances, all your compute nodes share one common " +"/var/lib/nova/instances/ directory." +msgstr "" + +#: ./doc/image-guide/ch_openstack_images.xml433(para) +msgid "" +"For information about libvirt images in OpenStack, refer to The life of" +" an OpenStack libvirt image from Pádraig Brady." +msgstr "" + +#: ./doc/image-guide/ch_openstack_images.xml439(caption) +msgid "Image cache management configuration options" +msgstr "" + +#: ./doc/image-guide/ch_openstack_images.xml445(td) +msgid "Configuration option=Default value" +msgstr "" + +#: ./doc/image-guide/ch_openstack_images.xml446(td) +msgid "(Type) Description" +msgstr "" + +#: ./doc/image-guide/ch_openstack_images.xml451(td) +msgid "preallocate_images=none" +msgstr "" + +#: ./doc/image-guide/ch_openstack_images.xml459(link) +msgid "fallocate" +msgstr "" + +#: ./doc/image-guide/ch_openstack_images.xml452(td) +msgid "" +"(StrOpt) VM image preallocation mode: \"none\" => no storage provisioning" +" is done up front, \"space\" => storage is fully allocated at instance " +"start. If this is set to 'space', the $instance_dir/ images will be  " +"d to immediately determine if enough space is available, and" +" to possibly improve VM I/O performance due to ongoing allocation avoidance," +" and better locality of block allocations." +msgstr "" + +#: ./doc/image-guide/ch_openstack_images.xml466(td) +msgid "remove_unused_base_images=True" +msgstr "" + +#: ./doc/image-guide/ch_openstack_images.xml467(td) +msgid "" +"(BoolOpt) Should unused base images be removed? When set to True, the " +"interval at which base images are removed are set with the following two " +"settings. If set to False base images are never removed by Compute." +msgstr "" + +#: ./doc/image-guide/ch_openstack_images.xml474(td) +msgid "remove_unused_original_minimum_age_seconds=86400" +msgstr "" + +#: ./doc/image-guide/ch_openstack_images.xml475(td) +msgid "" +"(IntOpt) Unused unresized base images younger than this will not be removed." +" Default is 86400 seconds, or 24 hours." +msgstr "" + +#: ./doc/image-guide/ch_openstack_images.xml480(td) +msgid "remove_unused_resized_minimum_age_seconds=3600" +msgstr "" + +#: ./doc/image-guide/ch_openstack_images.xml481(td) +msgid "" +"(IntOpt) Unused resized base images younger than this will not be removed. " +"Default is 3600 seconds, or one hour." +msgstr "" + +#: ./doc/image-guide/ch_openstack_images.xml487(para) +msgid "" +"To see how the settings affect the deletion of a running instance, check the" +" directory where the images are stored:" +msgstr "" + +#: ./doc/image-guide/ch_openstack_images.xml491(para) +msgid "" +"Then look for the identifier in " +"/var/log/compute/compute.log:" +msgstr "" + +#: ./doc/image-guide/ch_openstack_images.xml498(para) +msgid "" +"Since 86400 seconds (24 hours) is the default time for " +"remove_unused_original_minimum_age_seconds, you can " +"either wait for that time interval to see the base image removed, or set the" +" value to a shorter time period in nova.conf. Restart " +"all nova services after changing a setting in " +"nova.conf." +msgstr "" + +#: ./doc/image-guide/section_windows-example.xml8(title) +msgid "Example: Microsoft Windows image" +msgstr "" + +#: ./doc/image-guide/section_windows-example.xml9(para) +msgid "" +"We do not yet have a fully documented example of how to create a Microsoft " +"Windows image. You can use libvirt to install Windows from an installation " +"DVD using the same approach as with the CentOS and Ubuntu examples. Once the" +" initial install is done, you will need to perform some Windows-specific " +"customizations." +msgstr "" + +#: ./doc/image-guide/section_windows-example.xml14(title) +msgid "Install VirtIO drivers" +msgstr "" + +#: ./doc/image-guide/section_windows-example.xml15(para) +msgid "" +"Installing the VirtIO paravirtualizaion" +" drivers for Windows will improve virtual machine performance when " +"using KVM as the hypervisor to run Windows." +msgstr "" + +#: ./doc/image-guide/section_windows-example.xml20(title) +msgid "Sysprep" +msgstr "" + +#: ./doc/image-guide/section_windows-example.xml21(para) +msgid "" +"Microsoft has a special tool called Sysprep that must be run inside " +"of a Windows guest to prepare it for use as a virtual machine image. On " +"Windows 2012 server, invoke sysprep, as follows: " +msgstr "" + +#: ./doc/image-guide/section_windows-example.xml28(title) +msgid "cloudbase-init" +msgstr "" + +#: ./doc/image-guide/section_windows-example.xml29(para) +msgid "" +"cloudbase-init is a Windows port of cloud-init that should be " +"installed inside of the guest. The source code is available on github." +msgstr "" + +#: ./doc/image-guide/section_windows-example.xml35(title) +msgid "Jordan Rinke's OpenStack Windows resources" +msgstr "" + +#: ./doc/image-guide/section_windows-example.xml36(para) +msgid "" +"Jordan Rinke maintains a collection of " +"resources for managing OpenStack Windows virtual machine guests." +msgstr "" + +#: ./doc/image-guide/section_windows-example.xml41(title) +msgid "Windows instances require the timezone to be \"localtime\"" +msgstr "" + +#: ./doc/image-guide/section_windows-example.xml42(para) +msgid "" +"When uploading Windows images, you must set the os_type " +"parameter to windows, which causes instances to use the " +"local time zone. Failing to set this will cause the clock timezone to be " +"UTC, which has unexpected side effects in Windows." +msgstr "" + +#: ./doc/image-guide/section_freebsd-example.xml8(title) +msgid "Example: FreeBSD image" +msgstr "" + +#: ./doc/image-guide/section_freebsd-example.xml9(para) +msgid "" +"We do not yet have a fully documented example of how to create a FreeBSD " +"image." +msgstr "" + +#: ./doc/image-guide/section_freebsd-example.xml11(para) +msgid "" +"See the bsd-" +"cloudinit project for information on how to build a FreeBSD VM image " +"that works with OpenStack." +msgstr "" + +#. When image changes, this message will be marked fuzzy or untranslated for +#. you. +#. It doesn't matter what you translate it to: it's not used at all. +#: ./doc/image-guide/ch_creating_images_manually.xml78(None) +msgid "" +"@@image: 'figures/virt-manager-new.png'; " +"md5=3528ebfc1b945b7dd80a34897b8fe98e" +msgstr "" + +#: ./doc/image-guide/ch_creating_images_manually.xml6(title) +msgid "Create images manually" +msgstr "" + +#: ./doc/image-guide/ch_creating_images_manually.xml7(para) +msgid "" +"Creating a new image is a step done outside of your OpenStack installation. " +"You create the new image manually on your own system and then upload the " +"image to your cloud." +msgstr "" + +#: ./doc/image-guide/ch_creating_images_manually.xml11(para) +msgid "" +"To create a new image, you will need the installation CD or DVD ISO file for" +" the guest operating system. You'll also need access to a virtualization " +"tool. You can use KVM for this. Or, if you have a GUI desktop virtualization" +" tool (such as, VMWare Fusion and VirtualBox), you can use that instead and " +"just convert the file to raw once you're done." +msgstr "" + +#: ./doc/image-guide/ch_creating_images_manually.xml17(para) +msgid "" +"When you create a new virtual machine image, you will need to connect to the" +" graphical console of the hypervisor, which acts as the virtual machine's " +"display and allows you to interact with the guest operating system's " +"installer using your keyboard and mouse. KVM can expose the graphical " +"console using the VNC " +"(Virtual Network Computing) protocol or the newer SPICE protocol. We'll use the VNC protocol here, since " +"you're more likely to be able to find a VNC client that works on your local " +"desktop." +msgstr "" + +#: ./doc/image-guide/ch_creating_images_manually.xml30(title) +msgid "Verify the libvirt default network is running" +msgstr "" + +#: ./doc/image-guide/ch_creating_images_manually.xml31(para) +msgid "" +"Before starting a virtual machine with libvirt, verify that the libvirt " +"\"default\" network has been started. This network must be active for your " +"virtual machine to be able to connect out to the network. Starting this " +"network will create a Linux bridge (usually called " +"virbr0), iptables rules, and a dnsmasq process that will " +"serve as a DHCP server." +msgstr "" + +#: ./doc/image-guide/ch_creating_images_manually.xml38(para) +msgid "" +"To verify that the libvirt \"default\" network is enabled, use the " +" command and verify that the \"default\" network is active:" +msgstr "" + +#: ./doc/image-guide/ch_creating_images_manually.xml45(para) +msgid "If the network is not active, start it by doing:" +msgstr "" + +#: ./doc/image-guide/ch_creating_images_manually.xml49(title) +msgid "Use the virt-manager X11 GUI" +msgstr "" + +#: ./doc/image-guide/ch_creating_images_manually.xml50(para) +msgid "" +"If you plan to create a virtual machine image on a machine that can run X11 " +"applications, the simplest way to do so is to use the GUI, " +"which is installable as the virt-manager package on both " +"Fedora-based and Debian-based systems. This GUI has an embedded VNC client " +"in it that will let you view and interact with the guest's graphical " +"console." +msgstr "" + +#: ./doc/image-guide/ch_creating_images_manually.xml58(para) +msgid "" +"If you are building the image on a headless server, and you have an X server" +" on your local machine, you can launch  using ssh X11 " +"forwarding to access the GUI. Since virt-manager interacts directly with " +"libvirt, you typically need to be root to access it. If you can ssh directly" +" in as root (or with a user that has permissions to interact with libvirt), " +"do:" +msgstr "" + +#: ./doc/image-guide/ch_creating_images_manually.xml69(para) +msgid "" +"The -X flag passed to ssh will enable X11 forwarding over" +" ssh. If this does not work, try replacing it with the -Y" +" flag." +msgstr "" + +#: ./doc/image-guide/ch_creating_images_manually.xml66(para) +msgid "" +"If the account you use to ssh into your server does not have permissions to " +"run libvirt, but has sudo privileges, do:" +msgstr "" + +#: ./doc/image-guide/ch_creating_images_manually.xml74(para) +msgid "" +"Click the \"New\" button at the top-left and step through the instructions. " +"You will be shown a series of dialog boxes that will allow " +"you to specify information about the virtual machine." +msgstr "" + +#: ./doc/image-guide/ch_creating_images_manually.xml83(para) +msgid "" +"When using qcow2 format images you should check the option 'customize before" +" install', go to disk properties and explicitly select the qcow2 format. The" +" ensures the virtual machine disk size will be correct." +msgstr "" + +#: ./doc/image-guide/ch_creating_images_manually.xml91(title) +msgid "Use virt-install and connect by using a local VNC client" +msgstr "" + +#: ./doc/image-guide/ch_creating_images_manually.xml93(para) +msgid "" +"If you do not wish to use virt-manager (for example, you do not want to " +"install the dependencies on your server, you don't have an X server running " +"locally, the X11 forwarding over SSH isn't working), you can use the " +" tool to boot the virtual machine through libvirt and " +"connect to the graphical console from a VNC client installed on your local " +"machine." +msgstr "" + +#: ./doc/image-guide/ch_creating_images_manually.xml101(para) +msgid "" +"Because VNC is a standard protocol, there are multiple clients available " +"that implement the VNC spec, including TigerVNC" +" (multiple platforms), TightVNC " +"(multiple platforms), RealVNC " +"(multiple platforms), Chicken (Mac OS X)," +" Krde (KDE), and Vinagre (GNOME)." +msgstr "" + +#: ./doc/image-guide/ch_creating_images_manually.xml116(para) +msgid "" +"The following example shows how to use the command to " +"create an empty image file command to start up a virtual " +"machine using that image file. As root:" +msgstr "" + +#: ./doc/image-guide/ch_creating_images_manually.xml148(para) +msgid "" +"When using the libvirt default network, libvirt will " +"connect the virtual machine's interface to a bridge called " +"virbr0. There is a dnsmasq process managed by libvirt " +"that will hand out an IP address on the 192.168.122.0/24 subnet, and libvirt" +" has iptables rules for doing NAT for IP addresses on this subnet." +msgstr "" + +#: ./doc/image-guide/ch_creating_images_manually.xml133(para) +msgid "" +"This uses the KVM hypervisor to start up a virtual machine with the libvirt " +"name of centos-6.4 with 1024MB of RAM, with a virtual CD-" +"ROM drive associated with the " +"/data/CentOS-6.4-x86_64-netinstall.iso file, and a " +"local hard disk which is stored in the host at " +"/data/centos-6.4.qcow2 that is 10GB in size in qcow2 " +"format. It configures networking to use libvirt's default network. There is " +"a VNC server that is listening on all interfaces, and libvirt will not " +"attempt to launch a VNC client automatically nor try to display the text " +"console (--no-autoconsole). Finally, libvirt will attempt" +" to optimize the configuration for a Linux guest running a RHEL 6.x " +"distribution." +msgstr "" + +#: ./doc/image-guide/ch_creating_images_manually.xml157(para) +msgid "" +"Run the command to see a range of allowed --os-" +"variant options." +msgstr "" + +#: ./doc/image-guide/ch_creating_images_manually.xml161(replaceable) +msgid "vm-name" +msgstr "" + +#: ./doc/image-guide/ch_creating_images_manually.xml160(para) +msgid "Use the command to get the VNC port number." +msgstr "" + +#: ./doc/image-guide/ch_creating_images_manually.xml165(para) +msgid "" +"In the example above, the guest centos-6.4 uses VNC " +"display :1, which corresponds to tcp port " +"5901. You should be able to connect to a VNC client " +"running on your local machine to display :1 on the remote machine and step " +"through the installation process." +msgstr "" + +#: ./doc/image-guide/ch_preface.xml10(title) +msgid "Preface" +msgstr "" + +#: ./doc/image-guide/section_glance_image-formats.xml6(title) +msgid "Disk and container formats for images" +msgstr "" + +#: ./doc/image-guide/section_glance_image-formats.xml8(para) +msgid "" +"When you add an image to the Image Service, you can specify its disk and " +"container formats." +msgstr "" + +#: ./doc/image-guide/section_glance_image-formats.xml11(title) +msgid "Disk formats" +msgstr "" + +#: ./doc/image-guide/section_glance_image-formats.xml12(para) +msgid "" +"The disk format of a virtual machine image is the format of the underlying " +"disk image. Virtual appliance vendors have different formats for laying out " +"the information contained in a virtual machine disk image." +msgstr "" + +#: ./doc/image-guide/section_glance_image-formats.xml16(para) +msgid "Set the disk format for your image to one of the following values:" +msgstr "" + +#: ./doc/image-guide/section_glance_image-formats.xml20(para) +msgid "" +"raw. An unstructured disk image format; if you have a " +"file without an extension it is possibly a raw format" +msgstr "" + +#: ./doc/image-guide/section_glance_image-formats.xml25(para) +msgid "" +"vhd. The VHD disk format, a common disk format used by " +"virtual machine monitors from VMWare, Xen, Microsoft, VirtualBox, and others" +msgstr "" + +#: ./doc/image-guide/section_glance_image-formats.xml31(para) +msgid "" +"vmdk. Common disk format supported by many common virtual" +" machine monitors" +msgstr "" + +#: ./doc/image-guide/section_glance_image-formats.xml36(para) +msgid "" +"vdi. Supported by VirtualBox virtual machine monitor and " +"the QEMU emulator" +msgstr "" + +#: ./doc/image-guide/section_glance_image-formats.xml41(para) +msgid "" +"iso. An archive format for the data contents of an " +"optical disc, such as CD-ROM." +msgstr "" + +#: ./doc/image-guide/section_glance_image-formats.xml46(para) +msgid "" +"qcow2. Supported by the QEMU emulator that can expand " +"dynamically and supports Copy on Write" +msgstr "" + +#: ./doc/image-guide/section_glance_image-formats.xml51(para) +#: ./doc/image-guide/section_glance_image-formats.xml87(para) +msgid "aki. An Amazon kernel image." +msgstr "" + +#: ./doc/image-guide/section_glance_image-formats.xml55(para) +#: ./doc/image-guide/section_glance_image-formats.xml91(para) +msgid "ari. An Amazon ramdisk image." +msgstr "" + +#: ./doc/image-guide/section_glance_image-formats.xml59(para) +#: ./doc/image-guide/section_glance_image-formats.xml95(para) +msgid "ami. An Amazon machine image." +msgstr "" + +#: ./doc/image-guide/section_glance_image-formats.xml65(title) +msgid "Container formats" +msgstr "" + +#: ./doc/image-guide/section_glance_image-formats.xml66(para) +msgid "" +"The container format indicates whether the virtual machine image is in a " +"file format that also contains metadata about the actual virtual machine." +msgstr "" + +#: ./doc/image-guide/section_glance_image-formats.xml70(para) +msgid "" +"The Image Service and other OpenStack projects do not currently support the " +"container format. It is safe to specify bare as the " +"container format if you are unsure." +msgstr "" + +#: ./doc/image-guide/section_glance_image-formats.xml75(para) +msgid "" +"You can set the container format for your image to one of the following " +"values:" +msgstr "" + +#: ./doc/image-guide/section_glance_image-formats.xml79(para) +msgid "" +"bare. The image does not have a container or metadata " +"envelope." +msgstr "" + +#: ./doc/image-guide/section_glance_image-formats.xml83(para) +msgid "ovf. The OVF container format." +msgstr "" + +#: ./doc/image-guide/section_glance-image-metadata.xml7(title) +msgid "Image metadata" +msgstr "" + +#: ./doc/image-guide/section_glance-image-metadata.xml9(para) +msgid "" +"You can associate metadata with an image using the --property " +"key=value " +"argument to or . For example:" +msgstr "" + +#: ./doc/image-guide/section_glance-image-metadata.xml14(replaceable) +msgid "img-uuid" +msgstr "" + +#: ./doc/image-guide/section_glance-image-metadata.xml15(para) +msgid "" +"If the following properties are set on an image, and the " +"ImagePropertiesFilter scheduler filter is enabled (which it is by default), " +"then the scheduler will only consider compute hosts that satisfy these " +"properties:" +msgstr "" + +#: ./doc/image-guide/section_glance-image-metadata.xml20(term) +msgid "architecture" +msgstr "" + +#: ./doc/image-guide/section_glance-image-metadata.xml31(literal) +msgid "alpha" +msgstr "" + +#: ./doc/image-guide/section_glance-image-metadata.xml35(link) +msgid "DEC 64-bit RISC" +msgstr "" + +#: ./doc/image-guide/section_glance-image-metadata.xml40(literal) +msgid "armv7l" +msgstr "" + +#: ./doc/image-guide/section_glance-image-metadata.xml44(link) +msgid "ARM Cortex-A7 MPCore" +msgstr "" + +#: ./doc/image-guide/section_glance-image-metadata.xml49(literal) +msgid "cris" +msgstr "" + +#: ./doc/image-guide/section_glance-image-metadata.xml53(link) +msgid "Ethernet, Token Ring, AXis - Code Reduced Instruction Set" +msgstr "" + +#: ./doc/image-guide/section_glance-image-metadata.xml58(literal) +msgid "i686" +msgstr "" + +#: ./doc/image-guide/section_glance-image-metadata.xml60(para) +msgid "" +"Intel sixth-generation " +"x86 (P6 micro architecture)" +msgstr "" + +#: ./doc/image-guide/section_glance-image-metadata.xml68(literal) +msgid "ia64" +msgstr "" + +#: ./doc/image-guide/section_glance-image-metadata.xml72(link) +msgid "Itanium" +msgstr "" + +#: ./doc/image-guide/section_glance-image-metadata.xml77(literal) +msgid "lm32" +msgstr "" + +#: ./doc/image-guide/section_glance-image-metadata.xml81(link) +msgid "Lattice Micro32" +msgstr "" + +#: ./doc/image-guide/section_glance-image-metadata.xml86(literal) +msgid "m68k" +msgstr "" + +#: ./doc/image-guide/section_glance-image-metadata.xml90(link) +msgid "Motorola 68000" +msgstr "" + +#: ./doc/image-guide/section_glance-image-metadata.xml95(literal) +msgid "microblaze" +msgstr "" + +#: ./doc/image-guide/section_glance-image-metadata.xml99(link) +msgid "Xilinx 32-bit FPGA (Big Endian)" +msgstr "" + +#: ./doc/image-guide/section_glance-image-metadata.xml104(literal) +msgid "microblazeel" +msgstr "" + +#: ./doc/image-guide/section_glance-image-metadata.xml108(link) +msgid "Xilinx 32-bit FPGA (Little Endian)" +msgstr "" + +#: ./doc/image-guide/section_glance-image-metadata.xml113(literal) +msgid "mips" +msgstr "" + +#: ./doc/image-guide/section_glance-image-metadata.xml117(link) +msgid "MIPS 32-bit RISC (Big Endian)" +msgstr "" + +#: ./doc/image-guide/section_glance-image-metadata.xml122(literal) +msgid "mipsel" +msgstr "" + +#: ./doc/image-guide/section_glance-image-metadata.xml126(link) +msgid "MIPS 32-bit RISC (Little Endian)" +msgstr "" + +#: ./doc/image-guide/section_glance-image-metadata.xml131(literal) +msgid "mips64" +msgstr "" + +#: ./doc/image-guide/section_glance-image-metadata.xml135(link) +msgid "MIPS 64-bit RISC (Big Endian)" +msgstr "" + +#: ./doc/image-guide/section_glance-image-metadata.xml140(literal) +msgid "mips64el" +msgstr "" + +#: ./doc/image-guide/section_glance-image-metadata.xml144(link) +msgid "MIPS 64-bit RISC (Little Endian)" +msgstr "" + +#: ./doc/image-guide/section_glance-image-metadata.xml149(literal) +msgid "openrisc" +msgstr "" + +#: ./doc/image-guide/section_glance-image-metadata.xml153(link) +msgid "OpenCores RISC" +msgstr "" + +#: ./doc/image-guide/section_glance-image-metadata.xml158(literal) +msgid "parisc" +msgstr "" + +#: ./doc/image-guide/section_glance-image-metadata.xml162(link) +msgid "HP Precision Architecture RISC" +msgstr "" + +#: ./doc/image-guide/section_glance-image-metadata.xml167(literal) +msgid "parisc64" +msgstr "" + +#: ./doc/image-guide/section_glance-image-metadata.xml171(link) +msgid "HP Precision Architecture 64-bit RISC" +msgstr "" + +#: ./doc/image-guide/section_glance-image-metadata.xml176(literal) +msgid "ppc" +msgstr "" + +#: ./doc/image-guide/section_glance-image-metadata.xml180(link) +msgid "PowerPC 32-bit" +msgstr "" + +#: ./doc/image-guide/section_glance-image-metadata.xml185(literal) +msgid "ppc64" +msgstr "" + +#: ./doc/image-guide/section_glance-image-metadata.xml189(link) +msgid "PowerPC 64-bit" +msgstr "" + +#: ./doc/image-guide/section_glance-image-metadata.xml194(literal) +msgid "ppcemb" +msgstr "" + +#: ./doc/image-guide/section_glance-image-metadata.xml198(link) +msgid "PowerPC (Embedded 32-bit)" +msgstr "" + +#: ./doc/image-guide/section_glance-image-metadata.xml203(literal) +msgid "s390" +msgstr "" + +#: ./doc/image-guide/section_glance-image-metadata.xml207(link) +msgid "IBM Enterprise Systems Architecture/390" +msgstr "" + +#: ./doc/image-guide/section_glance-image-metadata.xml212(literal) +msgid "s390x" +msgstr "" + +#: ./doc/image-guide/section_glance-image-metadata.xml216(link) +msgid "S/390 64-bit" +msgstr "" + +#: ./doc/image-guide/section_glance-image-metadata.xml221(literal) +msgid "sh4" +msgstr "" + +#: ./doc/image-guide/section_glance-image-metadata.xml225(link) +msgid "SuperH SH-4 (Little Endian)" +msgstr "" + +#: ./doc/image-guide/section_glance-image-metadata.xml230(literal) +msgid "sh4eb" +msgstr "" + +#: ./doc/image-guide/section_glance-image-metadata.xml234(link) +msgid "SuperH SH-4 (Big Endian)" +msgstr "" + +#: ./doc/image-guide/section_glance-image-metadata.xml239(literal) +msgid "sparc" +msgstr "" + +#: ./doc/image-guide/section_glance-image-metadata.xml243(link) +msgid "Scalable Processor Architecture, 32-bit" +msgstr "" + +#: ./doc/image-guide/section_glance-image-metadata.xml248(literal) +msgid "sparc64" +msgstr "" + +#: ./doc/image-guide/section_glance-image-metadata.xml252(link) +msgid "Scalable Processor Architecture, 64-bit" +msgstr "" + +#: ./doc/image-guide/section_glance-image-metadata.xml257(literal) +msgid "unicore32" +msgstr "" + +#: ./doc/image-guide/section_glance-image-metadata.xml261(link) +msgid "Microprocessor Research and Development Center RISC Unicore32" +msgstr "" + +#: ./doc/image-guide/section_glance-image-metadata.xml267(literal) +msgid "x86_64" +msgstr "" + +#: ./doc/image-guide/section_glance-image-metadata.xml271(link) +msgid "64-bit extension of IA-32" +msgstr "" + +#: ./doc/image-guide/section_glance-image-metadata.xml276(literal) +msgid "xtensa" +msgstr "" + +#: ./doc/image-guide/section_glance-image-metadata.xml280(link) +msgid "Tensilica Xtensa configurable microprocessor core" +msgstr "" + +#: ./doc/image-guide/section_glance-image-metadata.xml285(literal) +msgid "xtensaeb" +msgstr "" + +#: ./doc/image-guide/section_glance-image-metadata.xml289(link) +msgid "Tensilica Xtensa configurable microprocessor core (Big Endian)" +msgstr "" + +#: ./doc/image-guide/section_glance-image-metadata.xml22(para) +msgid "" +"The CPU architecture that must be supported by the hypervisor. For example, " +"x86_64, arm, or " +"ppc64. Run to get the architecture of a " +"machine. We strongly recommend using the architecture data vocabulary " +"defined by the libosinfo project " +"for this purpose. Recognized values for this field are: " +msgstr "" + +#: ./doc/image-guide/section_glance-image-metadata.xml299(term) +msgid "hypervisor_type" +msgstr "" + +#: ./doc/image-guide/section_glance-image-metadata.xml301(para) +msgid "" +"The hypervisor type. Allowed values include: xen, " +"qemu, kvm, lxc, " +"uml, vmware, " +"hyperv." +msgstr "" + +#: ./doc/image-guide/section_glance-image-metadata.xml308(term) +msgid "vm_mode" +msgstr "" + +#: ./doc/image-guide/section_glance-image-metadata.xml314(literal) +msgid "hvm" +msgstr "" + +#: ./doc/image-guide/section_glance-image-metadata.xml316(para) +msgid "Fully virtualized. This is the mode used by QEMU and KVM." +msgstr "" + +#: ./doc/image-guide/section_glance-image-metadata.xml321(literal) +msgid "xen" +msgstr "" + +#: ./doc/image-guide/section_glance-image-metadata.xml323(para) +msgid "Xen 3.0 paravirtualized." +msgstr "" + +#: ./doc/image-guide/section_glance-image-metadata.xml327(literal) +msgid "uml" +msgstr "" + +#: ./doc/image-guide/section_glance-image-metadata.xml329(para) +msgid "User Mode Linux paravirtualized." +msgstr "" + +#: ./doc/image-guide/section_glance-image-metadata.xml333(literal) +msgid "exe" +msgstr "" + +#: ./doc/image-guide/section_glance-image-metadata.xml335(para) +msgid "Executables in containers. This is the mode used by LXC." +msgstr "" + +#: ./doc/image-guide/section_glance-image-metadata.xml310(para) +msgid "" +"The virtual machine mode. This represents the host/guest ABI (application " +"binary interface) used for the virtual machine. Allowed values " +"are:" +msgstr "" + +#: ./doc/image-guide/section_glance-image-metadata.xml342(para) +msgid "The following metadata properties are specific to the XenAPI driver:" +msgstr "" + +#: ./doc/image-guide/section_glance-image-metadata.xml344(term) +msgid "auto_disk_config" +msgstr "" + +#: ./doc/image-guide/section_glance-image-metadata.xml346(para) +msgid "" +"A boolean option. If true, the root partition on the disk will be " +"automatically resized before the instance boots. This value is only taken " +"into account by the Compute service when using a Xen-based hypervisor with " +"the XenAPI driver. The Compute service will only attempt to resize if there " +"is a single partition on the image, and only if the partition is in ext3 or " +"ext4 format." +msgstr "" + +#: ./doc/image-guide/section_glance-image-metadata.xml355(term) +msgid "os_type" +msgstr "" + +#: ./doc/image-guide/section_glance-image-metadata.xml357(para) +msgid "" +"The operating system installed on the image. For example, " +"linux or windows. The XenAPI driver " +"contains logic that will take different actions depending on the value of " +"the os_type parameter of the image. For example, for images where " +"os_type=windows, it creates a FAT32-based swap partition " +"instead of a Linux swap partition, and it limits the injected host name to " +"less than 16 characters." +msgstr "" + +#: ./doc/image-guide/section_glance-image-metadata.xml373(term) +msgid "hw_video_model" +msgstr "" + +#: ./doc/image-guide/section_glance-image-metadata.xml375(para) +msgid "" +"The video image driver used. Allowed values include: vga," +" cirrus, vmvga, xen" +" and qxl." +msgstr "" + +#: ./doc/image-guide/section_glance-image-metadata.xml369(para) +msgid "" +"The following metadata properties are specific to the libvirt API driver: " +"" +msgstr "" + +#: ./doc/image-guide/section_glance-image-metadata.xml384(para) +msgid "" +"The following metadata properties are specific to the VMware API driver:" +msgstr "" + +#: ./doc/image-guide/section_glance-image-metadata.xml387(term) +msgid "vmware_adaptertype" +msgstr "" + +#: ./doc/image-guide/section_glance-image-metadata.xml389(para) +msgid "" +"Indicates the virtual SCSI or IDE controller used by the hypervisor. Allowed" +" values: lsiLogic, busLogic, " +"ide" +msgstr "" + +#: ./doc/image-guide/section_glance-image-metadata.xml395(term) +msgid "vmware_ostype" +msgstr "" + +#: ./doc/image-guide/section_glance-image-metadata.xml397(para) +msgid "" +"A VMware GuestID which describes the operating system installed in the " +"image. This will be passed to the hypervisor when creating a virtual " +"machine. See thinkvirt.com for a " +"list of valid values. If this is not specified, it will default to " +"otherGuest." +msgstr "" + +#: ./doc/image-guide/section_glance-image-metadata.xml406(term) +msgid "vmware_image_version" +msgstr "" + +#: ./doc/image-guide/section_glance-image-metadata.xml408(para) +msgid "Currently unused, set it to 1." +msgstr "" + +#: ./doc/image-guide/section_glance-image-metadata.xml412(para) +msgid "" +"To assist end-users in utilizing images, you may wish to put additional " +"common metadata on Glance images. By community agreement, the following " +"metadata keys may be used across Glance installations for the purposes " +"described, as follows." +msgstr "" + +#: ./doc/image-guide/section_glance-image-metadata.xml417(term) +msgid "instance_uuid" +msgstr "" + +#: ./doc/image-guide/section_glance-image-metadata.xml419(para) +msgid "" +"For snapshot images, this is the UUID of the server used to create this " +"image." +msgstr "" + +#: ./doc/image-guide/section_glance-image-metadata.xml425(term) +msgid "kernel_id" +msgstr "" + +#: ./doc/image-guide/section_glance-image-metadata.xml427(para) +msgid "" +"The ID of image stored in Glance that should be used as the kernel when " +"booting an AMI-style image." +msgstr "" + +#: ./doc/image-guide/section_glance-image-metadata.xml434(term) +msgid "ramdisk_id" +msgstr "" + +#: ./doc/image-guide/section_glance-image-metadata.xml436(para) +msgid "" +"The ID of image stored in Glance that should be used as the ramdisk when " +"booting an AMI-style image." +msgstr "" + +#: ./doc/image-guide/section_glance-image-metadata.xml443(term) +msgid "os_version" +msgstr "" + +#: ./doc/image-guide/section_glance-image-metadata.xml445(para) +msgid "The operating system version as specified by the distributor." +msgstr "" + +#: ./doc/image-guide/section_glance-image-metadata.xml451(term) +msgid "os_distro" +msgstr "" + +#: ./doc/image-guide/section_glance-image-metadata.xml464(literal) +msgid "arch" +msgstr "" + +#: ./doc/image-guide/section_glance-image-metadata.xml466(para) +msgid "This is: Arch Linux" +msgstr "" + +#: ./doc/image-guide/section_glance-image-metadata.xml469(para) +msgid "" +"Do not use: archlinux, or " +"org.archlinux" +msgstr "" + +#: ./doc/image-guide/section_glance-image-metadata.xml477(literal) +msgid "centos" +msgstr "" + +#: ./doc/image-guide/section_glance-image-metadata.xml479(para) +msgid "This is: Community Enterprise Operating System" +msgstr "" + +#: ./doc/image-guide/section_glance-image-metadata.xml482(para) +msgid "" +"Do not use: org.centos, or CentOS" +msgstr "" + +#: ./doc/image-guide/section_glance-image-metadata.xml490(literal) +msgid "debian" +msgstr "" + +#: ./doc/image-guide/section_glance-image-metadata.xml492(para) +msgid "This is: Debian" +msgstr "" + +#: ./doc/image-guide/section_glance-image-metadata.xml495(para) +msgid "" +"Do not use: Debian, or org.debian" +msgstr "" + +#: ./doc/image-guide/section_glance-image-metadata.xml503(literal) +msgid "fedora" +msgstr "" + +#: ./doc/image-guide/section_glance-image-metadata.xml505(para) +msgid "This is: Fedora" +msgstr "" + +#: ./doc/image-guide/section_glance-image-metadata.xml508(para) +msgid "" +"Do not use: Fedora, org.fedora, or " +"org.fedoraproject" +msgstr "" + +#: ./doc/image-guide/section_glance-image-metadata.xml517(literal) +msgid "freebsd" +msgstr "" + +#: ./doc/image-guide/section_glance-image-metadata.xml519(para) +msgid "This is: FreeBSD" +msgstr "" + +#: ./doc/image-guide/section_glance-image-metadata.xml522(para) +msgid "" +"Do not use: org.freebsd, freeBSD, or " +"FreeBSD" +msgstr "" + +#: ./doc/image-guide/section_glance-image-metadata.xml531(literal) +msgid "gentoo" +msgstr "" + +#: ./doc/image-guide/section_glance-image-metadata.xml533(para) +msgid "This is: Gentoo Linux" +msgstr "" + +#: ./doc/image-guide/section_glance-image-metadata.xml536(para) +msgid "" +"Do not use: Gentoo, or org.gentoo" +msgstr "" + +#: ./doc/image-guide/section_glance-image-metadata.xml544(literal) +msgid "mandrake" +msgstr "" + +#: ./doc/image-guide/section_glance-image-metadata.xml546(para) +msgid "This is: Mandrakelinux (MandrakeSoft)" +msgstr "" + +#: ./doc/image-guide/section_glance-image-metadata.xml549(para) +msgid "" +"Do not use: mandrakelinux, or " +"MandrakeLinux" +msgstr "" + +#: ./doc/image-guide/section_glance-image-metadata.xml557(literal) +msgid "mandriva" +msgstr "" + +#: ./doc/image-guide/section_glance-image-metadata.xml559(para) +msgid "This is: Mandriva Linux" +msgstr "" + +#: ./doc/image-guide/section_glance-image-metadata.xml562(para) +msgid "Do not use: mandrivalinux" +msgstr "" + +#: ./doc/image-guide/section_glance-image-metadata.xml569(literal) +msgid "mes" +msgstr "" + +#: ./doc/image-guide/section_glance-image-metadata.xml571(para) +msgid "This is: Mandriva Enterprise Server" +msgstr "" + +#: ./doc/image-guide/section_glance-image-metadata.xml574(para) +msgid "" +"Do not use: mandrivaent, or mandrivaES" +msgstr "" + +#: ./doc/image-guide/section_glance-image-metadata.xml582(literal) +msgid "msdos" +msgstr "" + +#: ./doc/image-guide/section_glance-image-metadata.xml584(para) +msgid "This is: Microsoft Disc Operating System" +msgstr "" + +#: ./doc/image-guide/section_glance-image-metadata.xml587(para) +msgid "Do not use: ms-dos" +msgstr "" + +#: ./doc/image-guide/section_glance-image-metadata.xml594(literal) +msgid "netbsd" +msgstr "" + +#: ./doc/image-guide/section_glance-image-metadata.xml596(para) +msgid "This is: NetBSD" +msgstr "" + +#: ./doc/image-guide/section_glance-image-metadata.xml599(para) +msgid "" +"Do not use: NetBSD, or org.netbsd" +msgstr "" + +#: ./doc/image-guide/section_glance-image-metadata.xml607(literal) +msgid "netware" +msgstr "" + +#: ./doc/image-guide/section_glance-image-metadata.xml609(para) +msgid "This is: Novell NetWare" +msgstr "" + +#: ./doc/image-guide/section_glance-image-metadata.xml612(para) +msgid "Do not use: novell, or NetWare" +msgstr "" + +#: ./doc/image-guide/section_glance-image-metadata.xml620(literal) +msgid "openbsd" +msgstr "" + +#: ./doc/image-guide/section_glance-image-metadata.xml622(para) +msgid "This is: OpenBSD" +msgstr "" + +#: ./doc/image-guide/section_glance-image-metadata.xml625(para) +msgid "" +"Do not use: OpenBSD, or org.openbsd" +msgstr "" + +#: ./doc/image-guide/section_glance-image-metadata.xml633(literal) +msgid "opensolaris" +msgstr "" + +#: ./doc/image-guide/section_glance-image-metadata.xml635(para) +msgid "" +"Do not use: OpenSolaris,or " +"org.opensolaris" +msgstr "" + +#: ./doc/image-guide/section_glance-image-metadata.xml643(literal) +msgid "opensuse" +msgstr "" + +#: ./doc/image-guide/section_glance-image-metadata.xml645(para) +msgid "This is: openSUSE" +msgstr "" + +#: ./doc/image-guide/section_glance-image-metadata.xml648(para) +msgid "" +"Do not use: suse, SuSE, or " +"org.opensuse" +msgstr "" + +#: ./doc/image-guide/section_glance-image-metadata.xml657(literal) +msgid "rhel" +msgstr "" + +#: ./doc/image-guide/section_glance-image-metadata.xml659(para) +msgid "This is: Red Hat Enterprise Linux" +msgstr "" + +#: ./doc/image-guide/section_glance-image-metadata.xml662(para) +msgid "" +"Do not use: redhat, RedHat, or " +"com.redhat" +msgstr "" + +#: ./doc/image-guide/section_glance-image-metadata.xml671(literal) +msgid "sled" +msgstr "" + +#: ./doc/image-guide/section_glance-image-metadata.xml673(para) +msgid "This is: SUSE Linux Enterprise Desktop" +msgstr "" + +#: ./doc/image-guide/section_glance-image-metadata.xml676(para) +msgid "Do not use: com.suse" +msgstr "" + +#: ./doc/image-guide/section_glance-image-metadata.xml683(literal) +msgid "ubuntu" +msgstr "" + +#: ./doc/image-guide/section_glance-image-metadata.xml685(para) +msgid "This is: Ubuntu" +msgstr "" + +#: ./doc/image-guide/section_glance-image-metadata.xml688(para) +msgid "" +"Do not use: Ubuntu, com.ubuntu, " +"org.ubuntu, or canonical" +msgstr "" + +#: ./doc/image-guide/section_glance-image-metadata.xml698(literal) +msgid "windows" +msgstr "" + +#: ./doc/image-guide/section_glance-image-metadata.xml700(para) +msgid "This is: Microsoft Windows" +msgstr "" + +#: ./doc/image-guide/section_glance-image-metadata.xml703(para) +msgid "" +"Do not use: com.microsoft.server, or " +"windoze" +msgstr "" + +#: ./doc/image-guide/section_glance-image-metadata.xml453(para) +msgid "" +"The value of this property is the common name of the operating system " +"distribution in all-lowercase. For this purpose, we use the same data " +"vocabulary as the libosinfo " +"project. Following are the recognized values for this property. In " +"the interest of interoperability, please use only a recognized value for " +"this field. The deprecated values are listed to assist you in searching for " +"the recognized value. Allowed values are: " +msgstr "" + +#: ./doc/image-guide/ch_converting.xml4(title) +msgid "Converting between image formats" +msgstr "" + +#: ./doc/image-guide/ch_converting.xml5(para) +msgid "" +"Converting images from one format to another is generally straightforward." +msgstr "" + +#: ./doc/image-guide/ch_converting.xml7(title) +msgid "qemu-img convert: raw, qcow2, VDI, VMDK" +msgstr "" + +#: ./doc/image-guide/ch_converting.xml8(para) +msgid "" +"The command can do conversion between multiple formats, " +"including raw, qcow2, VDI (VirtualBox), VMDK (VMWare) and VHD (Hyper-V)." +msgstr "" + +#: ./doc/image-guide/ch_converting.xml12(caption) +msgid "qemu-img format strings" +msgstr "" + +#: ./doc/image-guide/ch_converting.xml16(th) +msgid "Image format" +msgstr "" + +#: ./doc/image-guide/ch_converting.xml17(th) +msgid "Argument to qemu-img" +msgstr "" + +#: ./doc/image-guide/ch_converting.xml22(td) +#: ./doc/image-guide/ch_converting.xml23(literal) +msgid "raw" +msgstr "" + +#: ./doc/image-guide/ch_converting.xml30(td) +msgid "VDI (VirtualBox)" +msgstr "" + +#: ./doc/image-guide/ch_converting.xml31(literal) +msgid "vdi" +msgstr "" + +#: ./doc/image-guide/ch_converting.xml34(td) +msgid "VMDK (VMWare)" +msgstr "" + +#: ./doc/image-guide/ch_converting.xml35(literal) +msgid "vmdk" +msgstr "" + +#: ./doc/image-guide/ch_converting.xml38(td) +msgid "VHD (Hyper-V)" +msgstr "" + +#: ./doc/image-guide/ch_converting.xml39(literal) +msgid "vpc" +msgstr "" + +#: ./doc/image-guide/ch_converting.xml43(para) +msgid "" +"This example will convert a raw image file named centos63.dsk to a qcow2 " +"image file." +msgstr "" + +#: ./doc/image-guide/ch_converting.xml47(para) +msgid "To convert from vmdk to raw, you would do: " +msgstr "" + +#: ./doc/image-guide/ch_converting.xml51(para) +msgid "" +"The -f format flag is " +"optional. If omitted, qemu-img will try to infer the image format." +msgstr "" + +#: ./doc/image-guide/ch_converting.xml57(title) +msgid "VBoxManage: VDI (VirtualBox) to raw" +msgstr "" + +#: ./doc/image-guide/ch_converting.xml58(para) +msgid "" +"If you've created a VDI image using VirtualBox, you can convert it to raw " +"format using the command-line tool that ships with " +"VirtualBox. On Mac OS X, VirtualBox stores images by default in the " +"~/VirtualBox VMs/ directory. The following example " +"creates a raw image in the current directory from a VirtualBox VDI " +"image." +msgstr "" + +#: ./doc/image-guide/ch_obtaining_images.xml6(title) +msgid "Get images" +msgstr "" + +#: ./doc/image-guide/ch_obtaining_images.xml8(para) +msgid "" +"The simplest way to obtain a virtual machine image that works with OpenStack" +" is to download one that someone else has already created." +msgstr "" + +#: ./doc/image-guide/ch_obtaining_images.xml11(title) +msgid "CirrOS (test) images" +msgstr "" + +#: ./doc/image-guide/ch_obtaining_images.xml12(para) +msgid "" +"CirrOS is a minimal Linux distribution that was designed for use as a test " +"image on clouds such as OpenStack Compute. You can download a CirrOS image " +"in various formats from the CirrOS Launchpad download " +"page." +msgstr "" + +#: ./doc/image-guide/ch_obtaining_images.xml21(para) +msgid "" +"In a CirrOS image, the login account is cirros. The " +"password is cubswin:)" +msgstr "" + +#: ./doc/image-guide/ch_obtaining_images.xml16(para) +msgid "" +"If your deployment uses QEMU or KVM, we recommend using the images in qcow2 " +"format. The most recent 64-bit qcow2 image as of this writing is cirros-0.3.1-x86_64-disk.img" +msgstr "" + +#: ./doc/image-guide/ch_obtaining_images.xml27(title) +msgid "Official Ubuntu images" +msgstr "" + +#: ./doc/image-guide/ch_obtaining_images.xml28(para) +msgid "" +"Canonical maintains an official set of Ubuntu-based images." +msgstr "" + +#: ./doc/image-guide/ch_obtaining_images.xml30(para) +msgid "" +"Images are arranged by Ubuntu release, and by image release date, with " +"\"current\" being the most recent. For example, the page that contains the " +"most recently built image for Ubuntu 12.04 \"Precise Pangolin\" is http://cloud-" +"images.ubuntu.com/precise/current/. Scroll to the bottom of the page " +"for links to images that can be downloaded directly." +msgstr "" + +#: ./doc/image-guide/ch_obtaining_images.xml40(para) +msgid "" +"In an Ubuntu cloud image, the login account is ubuntu." +msgstr "" + +#: ./doc/image-guide/ch_obtaining_images.xml36(para) +msgid "" +"If your deployment uses QEMU or KVM, we recommend using the images in qcow2 " +"format. The most recent version of the 64-bit QCOW2 image for Ubuntu 12.04 " +"is precise-server-cloudimg-" +"amd64-disk1.img." +msgstr "" + +#: ./doc/image-guide/ch_obtaining_images.xml45(title) +msgid "Official Red Hat Enterprise Linux images" +msgstr "" + +#: ./doc/image-guide/ch_obtaining_images.xml46(para) +msgid "" +"Red Hat maintains an official Red Hat Enterprise Linux 6 cloud image. A " +"valid Red Hat Enterprise Linux 6 subscription is required to download the " +"KVM" +" Guest Image." +msgstr "" + +#: ./doc/image-guide/ch_obtaining_images.xml53(para) +msgid "" +"A boot.iso" +" image is also available. This is the same as the " +"boot.iso file provided on the Red Hat Enterprise Linux " +"installation DVD. It is a minimal image suitable for kickstarting operating " +"system installation over a network." +msgstr "" + +#: ./doc/image-guide/ch_obtaining_images.xml63(title) +msgid "Official Fedora images" +msgstr "" + +#: ./doc/image-guide/ch_obtaining_images.xml64(para) +msgid "" +"The Fedora project maintains a list of official cloud images at . The images include the " +"cloud-init utility to support key" +" and user data injection. The default user name is fedora." +msgstr "" + +#: ./doc/image-guide/ch_obtaining_images.xml72(title) +msgid "Official openSUSE and SLES images" +msgstr "" + +#: ./doc/image-guide/ch_obtaining_images.xml73(para) +msgid "" +"SUSE does not provide openSUSE or SUSE Linux Enterprise Server (SLES) images" +" for direct download. Instead, they provide a web-based tool called SUSE Studio that you can use to build " +"openSUSE and SLES images." +msgstr "" + +#: ./doc/image-guide/ch_obtaining_images.xml79(para) +msgid "" +"For example, Christian Berendt used openSUSE to create a test openSUSE 12.3 image." +msgstr "" + +#: ./doc/image-guide/ch_obtaining_images.xml84(title) +msgid "Official images from other Linux distributions" +msgstr "" + +#: ./doc/image-guide/ch_obtaining_images.xml85(para) +msgid "" +"As of this writing, we are not aware of other distributions that provide " +"images for download." +msgstr "" + +#: ./doc/image-guide/ch_obtaining_images.xml88(title) +msgid "Rackspace Cloud Builders (multiple distros) images" +msgstr "" + +#: ./doc/image-guide/ch_obtaining_images.xml90(para) +msgid "" +"Rackspace Cloud Builders maintains a list of pre-built images from various " +"distributions (Red Hat, CentOS, Fedora, Ubuntu). Links to these images can " +"be found at rackerjoe/oz-image-build on Github." +msgstr "" + +#: ./doc/image-guide/ch_obtaining_images.xml96(title) +msgid "Microsoft Windows images" +msgstr "" + +#: ./doc/image-guide/ch_obtaining_images.xml97(para) +msgid "" +"Cloudbase Solutions hosts an OpenStack Windows Server 2012 " +"Standard Evaluation image that runs on Hyper-V, KVM, and " +"XenServer/XCP." +msgstr "" + +#. Put one translator per line, in the form of NAME , YEAR1, YEAR2 +#: ./doc/image-guide/ch_obtaining_images.xml0(None) +msgid "translator-credits" +msgstr "" diff --git a/doc/image-guide/locale/image-guide.pot b/doc/image-guide/locale/image-guide.pot new file mode 100644 index 0000000000..02e3df1420 --- /dev/null +++ b/doc/image-guide/locale/image-guide.pot @@ -0,0 +1,2412 @@ +msgid "" +msgstr "" +"Project-Id-Version: PACKAGE VERSION\n" +"POT-Creation-Date: 2014-01-30 06:24+0000\n" +"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n" +"Last-Translator: FULL NAME \n" +"Language-Team: LANGUAGE \n" +"MIME-Version: 1.0\n" +"Content-Type: text/plain; charset=UTF-8\n" +"Content-Transfer-Encoding: 8bit\n" + +#: ./doc/image-guide/ch_modifying_images.xml:6(title) +msgid "Modify images" +msgstr "" + +#: ./doc/image-guide/ch_modifying_images.xml:12(para) +msgid "Do not attempt to use these tools to modify an image that is attached to a running virtual machine. These tools are designed to only modify images that are not currently running." +msgstr "" + +#: ./doc/image-guide/ch_modifying_images.xml:8(para) +msgid "Once you have obtained a virtual machine image, you may want to make some changes to it before uploading it to the OpenStack Image service. Here we describe several tools available that allow you to modify images." +msgstr "" + +#: ./doc/image-guide/ch_modifying_images.xml:18(title) +msgid "guestfish" +msgstr "" + +#: ./doc/image-guide/ch_modifying_images.xml:19(para) +msgid "The program is a tool from the libguestfs project that allows you to modify the files inside of a virtual machine image." +msgstr "" + +#: ./doc/image-guide/ch_modifying_images.xml:24(para) +msgid " does not mount the image directly into the local file system. Instead, it provides you with a shell interface that enables you to view, edit, and delete files. Many of commands, such as , , and , resemble traditional bash commands." +msgstr "" + +#: ./doc/image-guide/ch_modifying_images.xml:34(title) +msgid "Example guestfish session" +msgstr "" + +#: ./doc/image-guide/ch_modifying_images.xml:35(para) +msgid "Sometimes, you must modify a virtual machine image to remove any traces of the MAC address that was assigned to the virtual network interface card when the image was first created, because the MAC address will be different when it boots the next time. This example shows how to use guestfish to remove references to the old MAC address by deleting the /etc/udev/rules.d/70-persistent-net.rules file and removing the HWADDR line from the /etc/sysconfig/network-scripts/ifcfg-eth0 file." +msgstr "" + +#: ./doc/image-guide/ch_modifying_images.xml:47(para) +msgid "Assume that you have a CentOS qcow2 image called centos63_desktop.img. Mount the image in read-write mode as root, as follows:" +msgstr "" + +#: ./doc/image-guide/ch_modifying_images.xml:61(para) +msgid "This starts a guestfish session. Note that the guestfish prompt looks like a fish: > <fs>." +msgstr "" + +#: ./doc/image-guide/ch_modifying_images.xml:64(para) +msgid "We must first use the command at the guestfish prompt before we can do anything else. This will launch a virtual machine, which will be used to perform all of the file manipulations. We can now view the file systems in the image using the command:We need to mount the logical volume that contains the root partition: " +msgstr "" + +#: ./doc/image-guide/ch_modifying_images.xml:78(para) +msgid "Next, we want to delete a file. We can use the guestfish command, which works the same way it does in a traditional shell." +msgstr "" + +#: ./doc/image-guide/ch_modifying_images.xml:82(para) +msgid "We want to edit the ifcfg-eth0 file to remove the HWADDR line. The command will copy the file to the host, invoke your editor, and then copy the file back. " +msgstr "" + +#: ./doc/image-guide/ch_modifying_images.xml:89(para) +msgid "If you want to modify this image to load the 8021q kernel at boot time, you must create an executable script in the /etc/sysconfig/modules/ directory. You can use the guestfish command to create an empty file, the command to edit it, and the command to make it executable. We add the following line to the file and save it:Then we set to executable: " +msgstr "" + +#: ./doc/image-guide/ch_modifying_images.xml:103(para) +msgid "We're done, so we can exit using the command:" +msgstr "" + +#: ./doc/image-guide/ch_modifying_images.xml:108(title) +msgid "Go further with guestfish" +msgstr "" + +#: ./doc/image-guide/ch_modifying_images.xml:109(para) +msgid "There is an enormous amount of functionality in guestfish and a full treatment is beyond the scope of this document. Instead, we recommend that you read the guestfs-recipes documentation page for a sense of what is possible with these tools." +msgstr "" + +#: ./doc/image-guide/ch_modifying_images.xml:119(title) +msgid "guestmount" +msgstr "" + +#: ./doc/image-guide/ch_modifying_images.xml:120(para) +msgid "For some types of changes, you may find it easier to mount the image's file system directly in the guest. The program, also from the libguestfs project, allows you to do so." +msgstr "" + +#: ./doc/image-guide/ch_modifying_images.xml:124(para) +msgid "For example, to mount the root partition from our centos63_desktop.qcow2 image to /mnt, we can do:" +msgstr "" + +#: ./doc/image-guide/ch_modifying_images.xml:130(para) +msgid "If we didn't know in advance what the mount point is in the guest, we could use the -i(inspect) flag to tell guestmount to automatically determine what mount point to use:Once mounted, we could do things like list the installed packages using rpm: Once done, we unmount:" +msgstr "" + +#: ./doc/image-guide/ch_modifying_images.xml:142(title) +msgid "virt-* tools" +msgstr "" + +#: ./doc/image-guide/ch_modifying_images.xml:147(para) +msgid "virt-edit for editing a file inside of an image." +msgstr "" + +#: ./doc/image-guide/ch_modifying_images.xml:153(para) +msgid "virt-df for displaying free space inside of an image." +msgstr "" + +#: ./doc/image-guide/ch_modifying_images.xml:159(para) +msgid "virt-resize for resizing an image." +msgstr "" + +#: ./doc/image-guide/ch_modifying_images.xml:165(para) +msgid "virt-sysprep for preparing an image for distribution (for example, delete SSH host keys, remove MAC address info, or remove user accounts)." +msgstr "" + +#: ./doc/image-guide/ch_modifying_images.xml:173(para) +msgid "virt-sparsify for making an image sparse" +msgstr "" + +#: ./doc/image-guide/ch_modifying_images.xml:179(para) +msgid "virt-p2v for converting a physical machine to an image that runs on KVM" +msgstr "" + +#: ./doc/image-guide/ch_modifying_images.xml:185(para) +msgid "virt-v2v for converting Xen and VMWare images to KVM images" +msgstr "" + +#: ./doc/image-guide/ch_modifying_images.xml:143(para) +msgid "The libguestfs project has a number of other useful tools, including:" +msgstr "" + +#: ./doc/image-guide/ch_modifying_images.xml:192(title) +msgid "Modify a single file inside of an image" +msgstr "" + +#: ./doc/image-guide/ch_modifying_images.xml:193(para) +msgid "This example shows how to use to modify a file. The command can take either a filename as an argument with the -a flag, or a domain name as an argument with the -d flag. The following examples shows how to use this to modify the /etc/shadow file in instance with libvirt domain name instance-000000e1 that is currently running:" +msgstr "" + +#: ./doc/image-guide/ch_modifying_images.xml:210(title) +msgid "Resize an image" +msgstr "" + +#: ./doc/image-guide/ch_modifying_images.xml:211(para) +msgid "Here's a simple of example of how to use to resize an image. Assume we have a 16GB Windows image in qcow2 format that we want to resize to 50GB. First, we use to identify the partitions:" +msgstr "" + +#: ./doc/image-guide/ch_modifying_images.xml:223(para) +msgid "In this case, it's the /dev/sda2 partition that we want to resize. We create a new qcow2 image and use the command to write a resized copy of the original into the new image: " +msgstr "" + +#: ./doc/image-guide/ch_modifying_images.xml:257(title) +msgid "Loop devices, kpartx, network block devices" +msgstr "" + +#: ./doc/image-guide/ch_modifying_images.xml:261(para) +msgid "Mounting untrusted guest images using the tools described in this section is a security risk, always use libguestfs tools such as guestfish and guestmount if you have access to them. See A reminder why you should never mount guest disk images on the host OS by Daniel Berrangé for more details." +msgstr "" + +#: ./doc/image-guide/ch_modifying_images.xml:258(para) +msgid "If you don't have access to libguestfs, you can mount image file systems directly in the host using loop devices, kpartx, and network block devices." +msgstr "" + +#: ./doc/image-guide/ch_modifying_images.xml:271(title) +msgid "Mount a raw image (without LVM)" +msgstr "" + +#: ./doc/image-guide/ch_modifying_images.xml:272(para) +msgid "If you have a raw virtual machine image that is not using LVM to manage its partitions. First, use the command to find an unused loop device. " +msgstr "" + +#: ./doc/image-guide/ch_modifying_images.xml:278(para) +msgid "In this example, /dev/loop0 is free. Associate a loop device with the raw image:" +msgstr "" + +#: ./doc/image-guide/ch_modifying_images.xml:281(para) +msgid "If the image only has a single partition, you can mount the loop device directly:" +msgstr "" + +#: ./doc/image-guide/ch_modifying_images.xml:284(para) +msgid "If the image has multiple partitions, use to expose the partitions as separate devices (for example, /dev/mapper/loop0p1), then mount the partition that corresponds to the root file system:" +msgstr "" + +#: ./doc/image-guide/ch_modifying_images.xml:290(para) +msgid "If the image has, say three partitions (/boot, /, /swap), there should be one new device created per partition:To mount the second partition, as root:Once you're done, to clean up:" +msgstr "" + +#: ./doc/image-guide/ch_modifying_images.xml:305(title) +msgid "Mount a raw image (with LVM)" +msgstr "" + +#: ./doc/image-guide/ch_modifying_images.xml:306(para) +msgid "If your partitions are managed with LVM, use losetup and kpartx as in the previous example to expose the partitions to the host:" +msgstr "" + +#: ./doc/image-guide/ch_modifying_images.xml:313(para) +msgid "Next, you need to use the command to identify the LVM volume groups and then to expose the volumes as devices:" +msgstr "" + +#: ./doc/image-guide/ch_modifying_images.xml:323(para) +msgid "Clean up when you're done:" +msgstr "" + +#: ./doc/image-guide/ch_modifying_images.xml:330(title) +msgid "Mount a qcow2 image (without LVM)" +msgstr "" + +#: ./doc/image-guide/ch_modifying_images.xml:331(para) +msgid "You need the nbd (network block device) kernel module loaded to mount qcow2 images. This will load it with support for 16 block devices, which is fine for our purposes. As root:" +msgstr "" + +#: ./doc/image-guide/ch_modifying_images.xml:336(para) +msgid "Assuming the first block device (/dev/nbd0) is not currently in use, we can expose the disk partitions using the and commands. As root:" +msgstr "" + +#: ./doc/image-guide/ch_modifying_images.xml:343(para) +msgid "If the image has, say three partitions (/boot, /, /swap), there should be one new device created for each partition:" +msgstr "" + +#: ./doc/image-guide/ch_modifying_images.xml:352(para) +msgid "If the network block device you selected was already in use, the initial command will fail silently, and the /dev/nbd3p{1,2,3} device files will not be created." +msgstr "" + +#: ./doc/image-guide/ch_modifying_images.xml:359(para) +msgid "If the image partitions are not managed with LVM, they can be mounted directly:" +msgstr "" + +#: ./doc/image-guide/ch_modifying_images.xml:363(para) +msgid "When you're done, clean up:" +msgstr "" + +#: ./doc/image-guide/ch_modifying_images.xml:368(title) +msgid "Mount a qcow2 image (with LVM)" +msgstr "" + +#: ./doc/image-guide/ch_modifying_images.xml:369(para) +msgid "If the image partitions are managed with LVM, after you use and , you must use and in order to expose the LVM partitions as devices that can be mounted:" +msgstr "" + +#: ./doc/image-guide/ch_modifying_images.xml:383(para) +msgid "When you're done, clean up:" +msgstr "" + +#. When image changes, this message will be marked fuzzy or untranslated for you. +#. It doesn't matter what you translate it to: it's not used at all. +#: ./doc/image-guide/section_centos-example.xml:80(None) ./doc/image-guide/section_centos-example.xml:84(None) +msgid "@@image: 'figures/centos-install.png'; md5=013b5be9e167ee27e674859ba4869d89" +msgstr "" + +#. When image changes, this message will be marked fuzzy or untranslated for you. +#. It doesn't matter what you translate it to: it's not used at all. +#: ./doc/image-guide/section_centos-example.xml:96(None) +msgid "@@image: 'figures/centos-tcpip.png'; md5=fe0324d0d74368d1920c243fd72747fd" +msgstr "" + +#. When image changes, this message will be marked fuzzy or untranslated for you. +#. It doesn't matter what you translate it to: it's not used at all. +#: ./doc/image-guide/section_centos-example.xml:107(None) +msgid "@@image: 'figures/install-method.png'; md5=1d60286d52f6b385a5d15ae042858893" +msgstr "" + +#. When image changes, this message will be marked fuzzy or untranslated for you. +#. It doesn't matter what you translate it to: it's not used at all. +#: ./doc/image-guide/section_centos-example.xml:122(None) +msgid "@@image: 'figures/url-setup.png'; md5=b2f3b4a3552ad175575f5eb78e63dfd8" +msgstr "" + +#. When image changes, this message will be marked fuzzy or untranslated for you. +#. It doesn't matter what you translate it to: it's not used at all. +#: ./doc/image-guide/section_centos-example.xml:188(None) +msgid "@@image: 'figures/centos-complete.png'; md5=1b2c6a2e45a9ae52a5f6338ae74b1e54" +msgstr "" + +#: ./doc/image-guide/section_centos-example.xml:6(title) +msgid "Example: CentOS image" +msgstr "" + +#: ./doc/image-guide/section_centos-example.xml:7(para) +msgid "We'll run through an example of installing a CentOS image. This will focus mainly on CentOS 6.4. Because the CentOS installation process may change across versions, if you are using a different version of CentOS the installer steps may differ." +msgstr "" + +#: ./doc/image-guide/section_centos-example.xml:13(title) +msgid "Download a CentOS install ISO" +msgstr "" + +#: ./doc/image-guide/section_centos-example.xml:17(para) +msgid "Navigate to the CentOS mirrors page." +msgstr "" + +#: ./doc/image-guide/section_centos-example.xml:22(para) +msgid "Click one of the HTTP links in the right-hand column next to one of the mirrors." +msgstr "" + +#: ./doc/image-guide/section_centos-example.xml:27(para) +msgid "Click the folder link of the CentOS version you want to use. For example, 6.4/." +msgstr "" + +#: ./doc/image-guide/section_centos-example.xml:32(para) +msgid "Click the isos/ folder link." +msgstr "" + +#: ./doc/image-guide/section_centos-example.xml:36(para) +msgid "Click the x86_64/ folder link for 64-bit images." +msgstr "" + +#: ./doc/image-guide/section_centos-example.xml:40(para) +msgid "Click the ISO image you want to download. The netinstall ISO. For example, CentOS-6.4-x86_64-netinstall.iso is a good choice since it's a smaller image that will download missing packages from the Internet during the install process." +msgstr "" + +#: ./doc/image-guide/section_centos-example.xml:51(title) ./doc/image-guide/section_ubuntu-example.xml:21(title) +msgid "Start the install process" +msgstr "" + +#: ./doc/image-guide/section_centos-example.xml:52(para) ./doc/image-guide/section_ubuntu-example.xml:22(para) +msgid "Start the installation process using either or as described in the previous section. If using , don't forget to connect your VNC client to the virtual machine." +msgstr "" + +#: ./doc/image-guide/section_centos-example.xml:58(para) +msgid "We will assume the name of your virtual machine image is centos-6.4, which we need to know when using commands to manipulate the state of the image." +msgstr "" + +#: ./doc/image-guide/section_centos-example.xml:62(para) ./doc/image-guide/section_ubuntu-example.xml:32(para) +msgid "If you're using virt-manager, the commands should look something like this:" +msgstr "" + +#: ./doc/image-guide/section_centos-example.xml:73(title) ./doc/image-guide/section_centos-example.xml:174(title) ./doc/image-guide/section_ubuntu-example.xml:43(title) ./doc/image-guide/section_ubuntu-example.xml:69(title) +msgid "Step through the install" +msgstr "" + +#: ./doc/image-guide/section_centos-example.xml:74(para) +msgid "At the initial Installer boot menu, choose the \"Install or upgrade an existing system\" option. Step through the install prompts, the defaults should be fine." +msgstr "" + +#: ./doc/image-guide/section_centos-example.xml:89(title) +msgid "Configure TCP/IP" +msgstr "" + +#: ./doc/image-guide/section_centos-example.xml:90(para) +msgid "The default TCP/IP settings are fine. In particular, ensure that Enable IPv4 support is enabled with DHCP, which is the default." +msgstr "" + +#: ./doc/image-guide/section_centos-example.xml:102(title) +msgid "Point the installer to a CentOS web server" +msgstr "" + +#: ./doc/image-guide/section_centos-example.xml:103(para) +msgid "Choose URL as the installation method." +msgstr "" + +#: ./doc/image-guide/section_centos-example.xml:116(para) +msgid "Consider using other mirrors as an alternative to mirror.umd.edu." +msgstr "" + +#: ./doc/image-guide/section_centos-example.xml:110(para) +msgid "Depending on the version of CentOS, the net installer requires that the user specify either a URL, or the web site and a CentOS directory that corresponds to one of the CentOS mirrors. If the installer asks for a single URL, an example of a valid URL would be: http://mirror.umd/centos/6/os/x86_64." +msgstr "" + +#: ./doc/image-guide/section_centos-example.xml:126(para) +msgid "If the installer asks for web site name and CentOS directory separately, an example would be:" +msgstr "" + +#: ./doc/image-guide/section_centos-example.xml:131(para) +msgid "Web site name: mirror.umd.edu" +msgstr "" + +#: ./doc/image-guide/section_centos-example.xml:136(para) +msgid "CentOS directory: centos/6/os/x86_64" +msgstr "" + +#: ./doc/image-guide/section_centos-example.xml:141(para) +msgid "See CentOS mirror page to get a full list of mirrors, click on the \"HTTP\" link of a mirror to retrieve the web site name of a mirror." +msgstr "" + +#: ./doc/image-guide/section_centos-example.xml:148(title) +msgid "Storage devices" +msgstr "" + +#: ./doc/image-guide/section_centos-example.xml:149(para) +msgid "If asked about what type of devices your installation involves, choose \"Basic Storage Devices\"." +msgstr "" + +#: ./doc/image-guide/section_centos-example.xml:153(title) ./doc/image-guide/section_ubuntu-example.xml:55(title) +msgid "Hostname" +msgstr "" + +#: ./doc/image-guide/section_centos-example.xml:154(para) +msgid "The installer may ask you to choose a hostname. The default (localhost.localdomain) is fine. We will install the cloud-init packge later, which will set the hostname on boot when a new instance is provisioned using this image." +msgstr "" + +#: ./doc/image-guide/section_centos-example.xml:161(title) ./doc/image-guide/section_ubuntu-example.xml:75(title) +msgid "Partition the disks" +msgstr "" + +#: ./doc/image-guide/section_centos-example.xml:162(para) ./doc/image-guide/section_ubuntu-example.xml:76(para) +msgid "There are different options for partitioning the disks. The default installation will use LVM partitions, and will create three partitions (/boot, /, swap), and this will work fine. Alternatively, you may wish to create a single ext4 partition, mounted to \"/\", should also work fine." +msgstr "" + +#: ./doc/image-guide/section_centos-example.xml:169(para) ./doc/image-guide/section_ubuntu-example.xml:83(para) +msgid "If unsure, we recommend you use the installer's default partition scheme, since there is no clear advantage to one scheme of another." +msgstr "" + +#: ./doc/image-guide/section_centos-example.xml:175(para) +msgid "Step through the install, using the default options. The simplest thing to do is to choose the \"Basic Server\" install (may be called \"Server\" install on older versions of CentOS), which will install an SSH server." +msgstr "" + +#: ./doc/image-guide/section_centos-example.xml:181(title) ./doc/image-guide/section_ubuntu-example.xml:120(title) +msgid "Detach the CD-ROM and reboot" +msgstr "" + +#: ./doc/image-guide/section_centos-example.xml:182(para) +msgid "Once the install completes, you will see the screen \"Congratulations, your CentOS installation is complete\"." +msgstr "" + +#: ./doc/image-guide/section_centos-example.xml:197(replaceable) ./doc/image-guide/section_centos-example.xml:368(replaceable) ./doc/image-guide/section_ubuntu-example.xml:144(replaceable) ./doc/image-guide/section_ubuntu-example.xml:238(replaceable) +msgid "vm-image" +msgstr "" + +#: ./doc/image-guide/section_centos-example.xml:192(para) ./doc/image-guide/section_ubuntu-example.xml:139(para) +msgid "To eject a disk using , libvirt requires that you attach an empty disk at the same target that the CDROM was previously attached, which should be hdc. You can confirm the appropriate target using the command." +msgstr "" + +#: ./doc/image-guide/section_centos-example.xml:212(para) +msgid "Run the following commands from the host to eject the disk and reboot using virsh, as root. If you are using virt-manager, the commands below will work, but you can also use the GUI to the detach and reboot it by manually stopping and starting." +msgstr "" + +#: ./doc/image-guide/section_centos-example.xml:221(para) +msgid "In theory, the command can be used instead of using destroy and start commands. However, in our testing we were unable to reboot successfully using the command." +msgstr "" + +#: ./doc/image-guide/section_centos-example.xml:230(title) ./doc/image-guide/section_ubuntu-example.xml:176(title) +msgid "Log in to newly created image" +msgstr "" + +#: ./doc/image-guide/section_centos-example.xml:231(para) +msgid "When you boot the first time after install, it may ask you about authentication tools, you can just choose \"Exit\". Then, log in as root using the root password you specified." +msgstr "" + +#: ./doc/image-guide/section_centos-example.xml:237(title) +msgid "Configure to fetch metadata" +msgstr "" + +#: ./doc/image-guide/section_centos-example.xml:243(para) +msgid "Install a cloud-init RPM, which is a port of the Ubuntu cloud-init package. This is the recommended approach." +msgstr "" + +#: ./doc/image-guide/section_centos-example.xml:250(para) +msgid "Modify /etc/rc.local to fetch desired information from the metadata service, as described below." +msgstr "" + +#: ./doc/image-guide/section_centos-example.xml:238(para) +msgid "An instance must perform several steps on start up by interacting with the metadata service. For example, retrieve ssh public key and execute user data script. There are several ways to implement this functionality, including:" +msgstr "" + +#: ./doc/image-guide/section_centos-example.xml:257(title) ./doc/image-guide/ch_openstack_images.xml:284(title) +msgid "Use cloud-init to fetch the public key" +msgstr "" + +#: ./doc/image-guide/section_centos-example.xml:258(para) +msgid "The cloud-init package will automatically fetch the public key from the metadata server and place the key in an account. You can install cloud-init inside the CentOS guest by adding the EPEL repo:" +msgstr "" + +#: ./doc/image-guide/section_centos-example.xml:264(para) ./doc/image-guide/section_ubuntu-example.xml:201(para) +msgid "The account varies by distribution. On Ubuntu-based virtual machines, the account is called \"ubuntu\". On Fedora-based virtual machines, the account is called \"ec2-user\"." +msgstr "" + +#: ./doc/image-guide/section_centos-example.xml:268(para) ./doc/image-guide/ch_openstack_images.xml:291(para) +msgid "You can change the name of the account used by cloud-init by editing the /etc/cloud/cloud.cfg file and adding a line with a different user. For example, to configure cloud-init to put the key in an account named admin, edit the configuration file so it has the line:" +msgstr "" + +#: ./doc/image-guide/section_centos-example.xml:278(title) +msgid "Write a script to fetch the public key (if no cloud-init)" +msgstr "" + +#: ./doc/image-guide/section_centos-example.xml:280(para) +msgid "If you are not able to install the cloud-init package in your image, to fetch the ssh public key and add it to the root account, edit the /etc/rc.local file and add the following lines before the line “touch /var/lock/subsys/local”" +msgstr "" + +#: ./doc/image-guide/section_centos-example.xml:310(para) +msgid "Some VNC clients replace : (colon) with ; (semicolon) and _ (underscore) with - (hyphen). Make sure it's http: not http; and authorized_keys not authorized-keys." +msgstr "" + +#: ./doc/image-guide/section_centos-example.xml:316(para) +msgid "The above script only retrieves the ssh public key from the metadata server. It does not retrieve user data, which is optional data that can be passed by the user when requesting a new instance. User data is often used for running a custom script when an instance comes up." +msgstr "" + +#: ./doc/image-guide/section_centos-example.xml:323(para) +msgid "As the OpenStack metadata service is compatible with version 2009-04-04 of the Amazon EC2 metadata service, consult the Amazon EC2 documentation on Using Instance Metadata for details on how to retrieve user data." +msgstr "" + +#: ./doc/image-guide/section_centos-example.xml:332(title) +msgid "Configure console" +msgstr "" + +#: ./doc/image-guide/section_centos-example.xml:339(replaceable) +msgid "..." +msgstr "" + +#: ./doc/image-guide/section_centos-example.xml:333(para) +msgid "In order for to work properly on CentOS 6.x, guests you may need to add the following lines to /boot/grub/menu.lst" +msgstr "" + +#: ./doc/image-guide/section_centos-example.xml:342(title) ./doc/image-guide/section_ubuntu-example.xml:214(title) +msgid "Shut down the instance" +msgstr "" + +#: ./doc/image-guide/section_centos-example.xml:343(para) ./doc/image-guide/section_ubuntu-example.xml:215(para) +msgid "From inside the instance, as root:" +msgstr "" + +#: ./doc/image-guide/section_centos-example.xml:347(title) ./doc/image-guide/section_ubuntu-example.xml:219(title) +msgid "Clean up (remove MAC address details)" +msgstr "" + +#: ./doc/image-guide/section_centos-example.xml:348(para) +msgid "The operating system records the MAC address of the virtual ethernet card in locations such as /etc/sysconfig/network-scripts/ifcfg-eth0 and /etc/udev/rules.d/70-persistent-net.rules during the instance process. However, each time the image boots up, the virtual ethernet card will have a different MAC address, so this information must be deleted from the configuration file." +msgstr "" + +#: ./doc/image-guide/section_centos-example.xml:357(para) ./doc/image-guide/section_ubuntu-example.xml:227(para) +msgid "There is a utility called , that performs various cleanup tasks such as removing the MAC address references. It will clean up a virtual machine image in place:" +msgstr "" + +#: ./doc/image-guide/section_centos-example.xml:364(title) ./doc/image-guide/section_ubuntu-example.xml:234(title) +msgid "Undefine the libvirt domain" +msgstr "" + +#: ./doc/image-guide/section_centos-example.xml:365(para) +msgid "Now that the image is ready to be uploaded to the Image service, you no longer need to have this virtual machine image managed by libvirt. Use the command to inform libvirt." +msgstr "" + +#: ./doc/image-guide/section_centos-example.xml:373(title) ./doc/image-guide/section_ubuntu-example.xml:243(title) +msgid "Image is complete" +msgstr "" + +#: ./doc/image-guide/section_centos-example.xml:374(para) +msgid "The underlying image file you created with . For example, /tmp/centos-6.4.qcow2 is now ready for uploading to the OpenStack Image service." +msgstr "" + +#: ./doc/image-guide/bk-imageguide.xml:10(title) +msgid "OpenStack Virtual Machine Image Guide" +msgstr "" + +#: ./doc/image-guide/bk-imageguide.xml:12(titleabbrev) +msgid "VM Image Guide" +msgstr "" + +#: ./doc/image-guide/bk-imageguide.xml:20(orgname) ./doc/image-guide/bk-imageguide.xml:25(holder) +msgid "OpenStack Foundation" +msgstr "" + +#: ./doc/image-guide/bk-imageguide.xml:24(year) +msgid "2013" +msgstr "" + +#: ./doc/image-guide/bk-imageguide.xml:27(releaseinfo) +msgid "havana" +msgstr "" + +#: ./doc/image-guide/bk-imageguide.xml:28(productname) +msgid "OpenStack" +msgstr "" + +#: ./doc/image-guide/bk-imageguide.xml:32(remark) +msgid "Remaining licensing details are filled in by the template." +msgstr "" + +#: ./doc/image-guide/bk-imageguide.xml:37(para) +msgid "This guide describes how to obtain, create, and modify virtual machine images that are compatible with OpenStack." +msgstr "" + +#: ./doc/image-guide/bk-imageguide.xml:44(date) +msgid "2013-10-25" +msgstr "" + +#: ./doc/image-guide/bk-imageguide.xml:48(para) +msgid "Adds information about image formats, properties." +msgstr "" + +#: ./doc/image-guide/bk-imageguide.xml:54(date) +msgid "2013-10-17" +msgstr "" + +#: ./doc/image-guide/bk-imageguide.xml:58(para) +msgid "Havana release." +msgstr "" + +#: ./doc/image-guide/bk-imageguide.xml:64(date) +msgid "2013-06-04" +msgstr "" + +#: ./doc/image-guide/bk-imageguide.xml:68(para) +msgid "Updated title for consistency." +msgstr "" + +#: ./doc/image-guide/bk-imageguide.xml:74(date) +msgid "2013-05-28" +msgstr "" + +#: ./doc/image-guide/bk-imageguide.xml:78(para) +msgid "Initial release of this guide." +msgstr "" + +#. When image changes, this message will be marked fuzzy or untranslated for you. +#. It doesn't matter what you translate it to: it's not used at all. +#: ./doc/image-guide/section_ubuntu-example.xml:50(None) +msgid "@@image: 'figures/ubuntu-install.png'; md5=a1f2ab707b7bc3122e20e6e0e4580887" +msgstr "" + +#. When image changes, this message will be marked fuzzy or untranslated for you. +#. It doesn't matter what you translate it to: it's not used at all. +#: ./doc/image-guide/section_ubuntu-example.xml:104(None) +msgid "@@image: 'figures/ubuntu-software-selection.png'; md5=423be828f701345f7d20551a39f24271" +msgstr "" + +#. When image changes, this message will be marked fuzzy or untranslated for you. +#. It doesn't matter what you translate it to: it's not used at all. +#: ./doc/image-guide/section_ubuntu-example.xml:115(None) +msgid "@@image: 'figures/ubuntu-grub.png'; md5=e46a46bd4044483da7cd07de2ff1ddbc" +msgstr "" + +#. When image changes, this message will be marked fuzzy or untranslated for you. +#. It doesn't matter what you translate it to: it's not used at all. +#: ./doc/image-guide/section_ubuntu-example.xml:128(None) +msgid "@@image: 'figures/ubuntu-finished.png'; md5=750be1d6a71b4186be563c049043e3a4" +msgstr "" + +#: ./doc/image-guide/section_ubuntu-example.xml:6(title) +msgid "Example: Ubuntu image" +msgstr "" + +#: ./doc/image-guide/section_ubuntu-example.xml:7(para) +msgid "We'll run through an example of installing an Ubuntu image. This will focus mainly on Ubuntu 12.04 (Precise Pangolin) server. Because the Ubuntu installation process may change across versions, if you are using a different version of Ubuntu the installer steps may differ." +msgstr "" + +#: ./doc/image-guide/section_ubuntu-example.xml:13(title) +msgid "Download an Ubuntu install ISO" +msgstr "" + +#: ./doc/image-guide/section_ubuntu-example.xml:14(para) +msgid "In this example, we'll use the network installation ISO, since it's a smaller image. The 64-bit 12.04 network installer ISO is at http://archive.ubuntu.com/ubuntu/dists/precise/main/installer-amd64/current/images/netboot/mini.iso" +msgstr "" + +#: ./doc/image-guide/section_ubuntu-example.xml:28(para) +msgid "We will assume the name of your virtual machine image is ubuntu-12.04, which we need to know when using commands to manipulate the state of the image." +msgstr "" + +#: ./doc/image-guide/section_ubuntu-example.xml:44(para) +msgid "At the initial Installer boot menu, choose the \"Install\" option. Step through the install prompts, the defaults should be fine." +msgstr "" + +#: ./doc/image-guide/section_ubuntu-example.xml:56(para) +msgid "The installer may ask you to choose a hostname. The default (ubuntu) is fine. We will install the cloud-init package later, which will set the hostname on boot when a new instance is provisioned using this image." +msgstr "" + +#: ./doc/image-guide/section_ubuntu-example.xml:64(title) +msgid "Select a mirror" +msgstr "" + +#: ./doc/image-guide/section_ubuntu-example.xml:65(para) +msgid "The default mirror proposed by the installer should be fine." +msgstr "" + +#: ./doc/image-guide/section_ubuntu-example.xml:70(para) +msgid "Step through the install, using the default options. When prompted for a username, the default (ubuntu) is fine." +msgstr "" + +#: ./doc/image-guide/section_ubuntu-example.xml:88(title) +msgid "Automatic updates" +msgstr "" + +#: ./doc/image-guide/section_ubuntu-example.xml:89(para) +msgid "The Ubuntu installer will ask how you want to manage upgrades on your system. This option depends upon your specific use case. If your virtual machine instances will be able to connect to the internet, we recommend \"Install security updates automatically\"." +msgstr "" + +#: ./doc/image-guide/section_ubuntu-example.xml:96(title) +msgid "Software selection: OpenSSH server" +msgstr "" + +#: ./doc/image-guide/section_ubuntu-example.xml:97(para) +msgid "Choose \"OpenSSH server\"so that you will be able to SSH into the virtual machine when it launches inside of an OpenStack cloud." +msgstr "" + +#: ./doc/image-guide/section_ubuntu-example.xml:109(title) +msgid "Install GRUB boot loader" +msgstr "" + +#: ./doc/image-guide/section_ubuntu-example.xml:110(para) +msgid "Select \"Yes\" when asked about installing the GRUB boot loader to the master boot record." +msgstr "" + +#: ./doc/image-guide/section_ubuntu-example.xml:121(para) +msgid "Select the defaults for all of the remaining options. When the installation is complete, you will be prompted to remove the CD-ROM." +msgstr "" + +#: ./doc/image-guide/section_ubuntu-example.xml:133(para) +msgid "When you hit \"Continue\" the virtual machine will shut down, even though it says it will reboot." +msgstr "" + +#: ./doc/image-guide/section_ubuntu-example.xml:160(para) +msgid "Run the following commands in the host as root to start up the machine again as paused, eject the disk and resume. If you are using virt-manager, you may instead use the GUI." +msgstr "" + +#: ./doc/image-guide/section_ubuntu-example.xml:167(para) +msgid "In the example above, we start the instance paused, eject the disk, and then unpause. In theory, we could have ejected the disk at the \"Installation complete\" screen. However, our testing indicates that the Ubuntu installer locks the drive so that it cannot be ejected at that point." +msgstr "" + +#: ./doc/image-guide/section_ubuntu-example.xml:177(para) +msgid "When you boot the first time after install, it may ask you about authentication tools, you can just choose 'Exit'. Then, log in as root using the root password you specified." +msgstr "" + +#: ./doc/image-guide/section_ubuntu-example.xml:183(title) +msgid "Install cloud-init" +msgstr "" + +#: ./doc/image-guide/section_ubuntu-example.xml:184(para) +msgid "The script starts on instance boot and will search for a metadata provider to fetch a public key from. The public key will be placed in the default user account for the image." +msgstr "" + +#: ./doc/image-guide/section_ubuntu-example.xml:188(para) +msgid "Install the cloud-init package:" +msgstr "" + +#: ./doc/image-guide/section_ubuntu-example.xml:190(para) +msgid "When building Ubuntu images must be explicitly configured for the metadata source in use. The OpenStack metadata server emulates the EC2 metadata service used by images in Amazon EC2." +msgstr "" + +#: ./doc/image-guide/section_ubuntu-example.xml:195(para) +msgid "To set the metadata source to be used by the image run the command against the cloud-init package. When prompted select the EC2 data source: " +msgstr "" + +#: ./doc/image-guide/section_ubuntu-example.xml:205(para) +msgid "You can change the name of the account used by cloud-init by editing the /etc/cloud/cloud.cfg file and adding a line with a different user. For example, to configure cloud-init to put the key in an account named \"admin\", edit the config file so it has the line:" +msgstr "" + +#: ./doc/image-guide/section_ubuntu-example.xml:220(para) +msgid "The operating system records the MAC address of the virtual ethernet card in locations such as /etc/udev/rules.d/70-persistent-net.rules during the instance process. However, each time the image boots up, the virtual ethernet card will have a different MAC address, so this information must be deleted from the configuration file." +msgstr "" + +#: ./doc/image-guide/section_ubuntu-example.xml:235(para) +msgid "Now that the image is ready to be uploaded to the Image service, we know longer need to have this virtual machine image managed by libvirt. Use the command to inform libvirt" +msgstr "" + +#: ./doc/image-guide/section_ubuntu-example.xml:244(para) +msgid "The underlying image file that you created with , such as /tmp/precise.qcow2, is now ready for uploading to the OpenStack Image service." +msgstr "" + +#: ./doc/image-guide/ch_introduction.xml:6(title) +msgid "Introduction" +msgstr "" + +#: ./doc/image-guide/ch_introduction.xml:7(para) +msgid "An OpenStack Compute cloud is not very useful unless you have virtual machine images (which some people call \"virtual appliances\"). This guide describes how to obtain, create, and modify virtual machine images that are compatible with OpenStack." +msgstr "" + +#: ./doc/image-guide/ch_introduction.xml:10(para) +msgid "To keep things brief, we'll sometimes use the term \"image\" instead of \"virtual machine image\"." +msgstr "" + +#: ./doc/image-guide/ch_introduction.xml:12(para) +msgid "What is a virtual machine image?" +msgstr "" + +#: ./doc/image-guide/ch_introduction.xml:13(para) +msgid "A virtual machine image is a single file which contains a virtual disk that has a bootable operating system installed on it." +msgstr "" + +#: ./doc/image-guide/ch_introduction.xml:15(para) +msgid "Virtual machine images come in different formats, some of which are described below. In a later chapter, we'll describe how to convert between formats." +msgstr "" + +#: ./doc/image-guide/ch_introduction.xml:19(term) +msgid "Raw" +msgstr "" + +#: ./doc/image-guide/ch_introduction.xml:26(para) +msgid "We don't recommend creating raw images by dd'ing block device files, we discuss how to create raw images later." +msgstr "" + +#: ./doc/image-guide/ch_introduction.xml:20(para) +msgid "The \"raw\" image format is the simplest one, and is natively supported by both KVM and Xen hypervisors. You can think of a raw image as being the bit-equivalent of a block device file, created as if somebody had copied, say, /dev/sda to a file using the command. " +msgstr "" + +#: ./doc/image-guide/ch_introduction.xml:32(term) ./doc/image-guide/ch_converting.xml:26(td) ./doc/image-guide/ch_converting.xml:27(literal) +msgid "qcow2" +msgstr "" + +#: ./doc/image-guide/ch_introduction.xml:37(para) +msgid "Using sparse representation, so the image size is smaller" +msgstr "" + +#: ./doc/image-guide/ch_introduction.xml:40(para) +msgid "Support for snapshots" +msgstr "" + +#: ./doc/image-guide/ch_introduction.xml:33(para) +msgid "The qcow2 (QEMU copy-on-write version 2) format is commonly used with the KVM hypervisor. It has some additional features over the raw format, such as:" +msgstr "" + +#: ./doc/image-guide/ch_introduction.xml:43(para) +msgid "Because qcow2 is sparse, it's often faster to convert a raw image to qcow2 and upload it then to upload the raw file." +msgstr "" + +#: ./doc/image-guide/ch_introduction.xml:47(para) +msgid "Because raw images don't support snapshots, OpenStack Compute will automatically convert raw image files to qcow2 as needed." +msgstr "" + +#: ./doc/image-guide/ch_introduction.xml:53(term) +msgid "AMI/AKI/ARI" +msgstr "" + +#: ./doc/image-guide/ch_introduction.xml:59(para) +msgid "AMI (Amazon Machine Image):" +msgstr "" + +#: ./doc/image-guide/ch_introduction.xml:60(para) +msgid "This is a virtual machine image in raw format, as described above." +msgstr "" + +#: ./doc/image-guide/ch_introduction.xml:64(para) +msgid "AKI (Amazon Kernel Image)" +msgstr "" + +#: ./doc/image-guide/ch_introduction.xml:65(para) +msgid "A kernel file that the hypervisor will load initially to boot the image. For a Linux machine, this would be a vmlinuz file." +msgstr "" + +#: ./doc/image-guide/ch_introduction.xml:72(para) +msgid "ARI (Amazon Ramdisk Image)" +msgstr "" + +#: ./doc/image-guide/ch_introduction.xml:73(para) +msgid "An optional ramdisk file mounted at boot time. For a Linux machine, this would be an initrd file." +msgstr "" + +#: ./doc/image-guide/ch_introduction.xml:54(para) +msgid "The AMI/AKI/ARI format was the initial image format supported by Amazon EC2. The image consists of three files:" +msgstr "" + +#: ./doc/image-guide/ch_introduction.xml:81(term) +msgid "UEC tarball" +msgstr "" + +#: ./doc/image-guide/ch_introduction.xml:84(para) +msgid "Ubuntu Enterprise Cloud refers to a discontinued Eucalyptus-based Ubuntu cloud solution that has been replaced by the OpenStack-based Ubuntu Cloud Infrastructure." +msgstr "" + +#: ./doc/image-guide/ch_introduction.xml:82(para) +msgid "A UEC (Ubuntu Enterprise Cloud) tarball is a gzipped tarfile that contains an AMI file, AKI file, and ARI file." +msgstr "" + +#: ./doc/image-guide/ch_introduction.xml:90(term) +msgid "VMDK" +msgstr "" + +#: ./doc/image-guide/ch_introduction.xml:91(para) +msgid "VMWare's ESXi hypervisor uses the VMDK (Virtual Machine Disk) format for images." +msgstr "" + +#: ./doc/image-guide/ch_introduction.xml:96(term) +msgid "VDI" +msgstr "" + +#: ./doc/image-guide/ch_introduction.xml:97(para) +msgid "VirtualBox uses the VDI (Virtual Disk Image) format for image files. None of the OpenStack Compute hypervisors support VDI directly, so you will need to convert these files to a different format to use them with OpenStack." +msgstr "" + +#: ./doc/image-guide/ch_introduction.xml:104(term) +msgid "VHD" +msgstr "" + +#: ./doc/image-guide/ch_introduction.xml:105(para) +msgid "Microsoft Hyper-V uses the VHD (Virtual Hard Disk) format for images." +msgstr "" + +#: ./doc/image-guide/ch_introduction.xml:108(term) +msgid "VHDX" +msgstr "" + +#: ./doc/image-guide/ch_introduction.xml:109(para) +msgid "The version of Hyper-V that ships with Microsoft Server 2012 uses the newer VHDX format, which has some additional features over VHD such as support for larger disk sizes and protection against data corruption during power failures." +msgstr "" + +#: ./doc/image-guide/ch_introduction.xml:115(term) +msgid "OVF" +msgstr "" + +#: ./doc/image-guide/ch_introduction.xml:116(para) +msgid "OVF (Open Virtualization Format) is a packaging format for virtual machines, defined by the Distributed Management Task Force (DMTF) standards group. An OVF package contains one or more image files, a .ovf XML metadata file that contains information about the virtual machine, and possibly other files as well." +msgstr "" + +#: ./doc/image-guide/ch_introduction.xml:121(para) +msgid "An OVF package can be distributed in different ways. For example, it could be distributed as a set of discrete files, or as a tar archive file with an .ova (open virtual appliance/application) extension." +msgstr "" + +#: ./doc/image-guide/ch_introduction.xml:124(para) +msgid "OpenStack Compute does not currently have support for OVF packages, so you will need to extract the image file(s) from an OVF package if you wish to use it with OpenStack." +msgstr "" + +#: ./doc/image-guide/ch_introduction.xml:129(term) +msgid "ISO" +msgstr "" + +#: ./doc/image-guide/ch_introduction.xml:130(para) +msgid "The ISO format is a disk image formatted with the read-only ISO 9660 (also known as ECMA-119) filesystem commonly used for CDs and DVDs. While we don't normally think of ISO a virtual machine image format, since ISOs contain bootable filesystems with an installed operating system, you can treat them the same you treat other virtual machine image files." +msgstr "" + +#: ./doc/image-guide/ch_creating_images_automatically.xml:6(title) +msgid "Tool support for image creation" +msgstr "" + +#: ./doc/image-guide/ch_creating_images_automatically.xml:8(para) +msgid "There are several tools that are designed to automate image creation." +msgstr "" + +#: ./doc/image-guide/ch_creating_images_automatically.xml:11(title) +msgid "Oz" +msgstr "" + +#: ./doc/image-guide/ch_creating_images_automatically.xml:22(para) +msgid "As of this writing, there are no Oz packages for Ubuntu, so you will need to either install from source or build your own .deb file." +msgstr "" + +#: ./doc/image-guide/ch_creating_images_automatically.xml:12(para) +msgid "Oz is a command-line tool that automates the process of creating a virtual machine image file. Oz is a Python app that interacts with KVM to step through the process of installing a virtual machine. It uses a predefined set of kickstart (Red Hat-based systems) and preseed files (Debian-based systems) for operating systems that it supports, and it can also be used to create Microsoft Windows images. On Fedora, install Oz with yum:" +msgstr "" + +#: ./doc/image-guide/ch_creating_images_automatically.xml:26(para) +msgid "A full treatment of Oz is beyond the scope of this document, but we will provide an example. You can find additional examples of Oz template files on github at rackerjoe/oz-image-build/templates. Here's how you would create a CentOS 6.4 image with Oz." +msgstr "" + +#: ./doc/image-guide/ch_creating_images_automatically.xml:33(para) +msgid "Create a template file (we'll call it centos64.tdl) with the following contents. The only entry you will need to change is the <rootpw> contents." +msgstr "" + +#: ./doc/image-guide/ch_creating_images_automatically.xml:71(para) +msgid "This Oz template specifies where to download the Centos 6.4 install ISO. Oz will use the version information to identify which kickstart file to use. In this case, it will be RHEL6.auto. It adds EPEL as a repository and install the epel-release, cloud-utils, and cloud-init packages, as specified in the packages section of the file." +msgstr "" + +#: ./doc/image-guide/ch_creating_images_automatically.xml:82(para) +msgid "After Oz does the initial OS install using the kickstart file, it customizes the image by doing an update. It also removes any reference to the eth0 device that libvirt creates while Oz does the customizing, as specified in the command section of the XML file." +msgstr "" + +#: ./doc/image-guide/ch_creating_images_automatically.xml:88(para) +msgid "To run this, do, as root:" +msgstr "" + +#: ./doc/image-guide/ch_creating_images_automatically.xml:91(para) +msgid "The -d3 flag tells Oz to show status information as it runs." +msgstr "" + +#: ./doc/image-guide/ch_creating_images_automatically.xml:95(para) +msgid "The -u tells Oz to do the customization (install extra packages, run the commands) once it does the initial install." +msgstr "" + +#: ./doc/image-guide/ch_creating_images_automatically.xml:101(para) +msgid "The -x <filename> flag tells Oz what filename to use to write out a libvirt XML file (otherwise it will default to something like centos64Apr_03_2013-12:39:42." +msgstr "" + +#: ./doc/image-guide/ch_creating_images_automatically.xml:89(para) +msgid "If you leave out the -u flag, or you want to edit the file to do additional customizations, you can use the command, using the libvirt XML file that creates. For example: Oz will invoke libvirt to boot the image inside of KVM, then Oz will ssh into the instance and perform the customizations." +msgstr "" + +#: ./doc/image-guide/ch_creating_images_automatically.xml:119(title) +msgid "VMBuilder" +msgstr "" + +#: ./doc/image-guide/ch_creating_images_automatically.xml:120(para) +msgid "VMBuilder (Virtual Machine Builder) is a command-line tool that creates virtual machine images for different hypervisors. The version of VMBuilder that ships with Ubuntu can only create Ubuntu virtual machine guests. The version of VMBuilder that ships with Debian can create Ubuntu and Debian virtual machine guests." +msgstr "" + +#: ./doc/image-guide/ch_creating_images_automatically.xml:127(para) +msgid "The Ubuntu Server Guide has documentation on how to use VMBuilder to create an Ubuntu image." +msgstr "" + +#: ./doc/image-guide/ch_creating_images_automatically.xml:134(title) +msgid "BoxGrinder" +msgstr "" + +#: ./doc/image-guide/ch_creating_images_automatically.xml:135(para) +msgid "BoxGrinder  is another tool for creating virtual machine images, which it calls appliances. BoxGrinder can create Fedora, Red Hat Enterprise Linux, or CentOS images. BoxGrinder is currently only supported on Fedora." +msgstr "" + +#: ./doc/image-guide/ch_creating_images_automatically.xml:144(title) +msgid "VeeWee" +msgstr "" + +#: ./doc/image-guide/ch_creating_images_automatically.xml:145(para) +msgid " VeeWee is often used to build Vagrant boxes, but it can also be used to build KVM images." +msgstr "" + +#: ./doc/image-guide/ch_creating_images_automatically.xml:151(title) +msgid "imagefactory" +msgstr "" + +#: ./doc/image-guide/ch_creating_images_automatically.xml:152(para) +msgid "imagefactory is a newer tool designed to automate the building, converting, and uploading images to different cloud providers. It uses Oz as its back-end and includes support for OpenStack-based clouds." +msgstr "" + +#: ./doc/image-guide/ch_creating_images_automatically.xml:159(title) +msgid "SUSE Studio" +msgstr "" + +#: ./doc/image-guide/ch_creating_images_automatically.xml:160(para) +msgid "SUSE Studio is a web application for building and testing software applications in a web browser. It supports the creation of physical, virtual or cloud-based applications and includes support for building images for OpenStack based clouds using SUSE Linux Enterprise and openSUSE as distributions." +msgstr "" + +#: ./doc/image-guide/ch_openstack_images.xml:6(title) +msgid "OpenStack Linux image requirements" +msgstr "" + +#: ./doc/image-guide/ch_openstack_images.xml:17(para) ./doc/image-guide/ch_openstack_images.xml:44(title) +msgid "Disk partitions and resize root partition on boot (cloud-init)" +msgstr "" + +#: ./doc/image-guide/ch_openstack_images.xml:21(para) ./doc/image-guide/ch_openstack_images.xml:221(title) +msgid "No hard-coded MAC address information" +msgstr "" + +#: ./doc/image-guide/ch_openstack_images.xml:24(para) +msgid "SSH server running" +msgstr "" + +#: ./doc/image-guide/ch_openstack_images.xml:27(para) ./doc/image-guide/ch_openstack_images.xml:266(title) +msgid "Disable firewall" +msgstr "" + +#: ./doc/image-guide/ch_openstack_images.xml:30(para) ./doc/image-guide/ch_openstack_images.xml:275(title) +msgid "Access instance using ssh public key (cloud-init)" +msgstr "" + +#: ./doc/image-guide/ch_openstack_images.xml:34(para) ./doc/image-guide/ch_openstack_images.xml:358(title) +msgid "Process user data and other metadata (cloud-init)" +msgstr "" + +#: ./doc/image-guide/ch_openstack_images.xml:38(para) +msgid "Paravirtualized Xen support in Linux kernel (Xen hypervisor only with Linux kernel version < 3.0)" +msgstr "" + +#: ./doc/image-guide/ch_openstack_images.xml:8(para) +msgid "For a Linux-based image to have full functionality in an OpenStack Compute cloud, there are a few requirements. For some of these, the requirement can be fulfilled by installing the cloud-init package. You should read this section before creating your own image to be sure that the image supports the OpenStack features you plan on using." +msgstr "" + +#: ./doc/image-guide/ch_openstack_images.xml:46(para) +msgid "When you create a new Linux image, the first decision you will need to make is how to partition the disks. The choice of partition method can affect the resizing functionality, as described below." +msgstr "" + +#: ./doc/image-guide/ch_openstack_images.xml:50(para) +msgid "The size of the disk in a virtual machine image is determined when you initially create the image. However, OpenStack lets you launch instances with different size drives by specifying different flavors. For example, if your image was created with a 5 GB disk, and you launch an instance with a flavor of m1.small. The resulting virtual machine instance has, by default, a primary disk size of 10 GB. When an instance's disk is resized up, zeros are just added to the end." +msgstr "" + +#: ./doc/image-guide/ch_openstack_images.xml:59(para) +msgid "Your image needs to be able to resize its partitions on boot to match the size requested by the user. Otherwise, after the instance boots, you will need to manually resize the partitions if you want to access the additional storage you have access to when the disk size associated with the flavor exceeds the disk size your image was created with." +msgstr "" + +#: ./doc/image-guide/ch_openstack_images.xml:67(title) +msgid "Xen: 1 ext3/ext4 partition (no LVM, no /boot, no swap)" +msgstr "" + +#: ./doc/image-guide/ch_openstack_images.xml:74(para) +msgid "auto_disk_config=True is set as a property on the image in the Image Registry." +msgstr "" + +#: ./doc/image-guide/ch_openstack_images.xml:79(para) +msgid "The disk on the image has only one partition." +msgstr "" + +#: ./doc/image-guide/ch_openstack_images.xml:83(para) +msgid "The file system on the one partition is ext3 or ext4." +msgstr "" + +#: ./doc/image-guide/ch_openstack_images.xml:69(para) +msgid "If you are using the OpenStack XenAPI driver, the Compute service will automatically adjust the partition and filesystem for your instance on boot. Automatic resize will occur if the following are all true:" +msgstr "" + +#: ./doc/image-guide/ch_openstack_images.xml:87(para) +msgid "Therefore, if you are using Xen, we recommend that when you create your images, you create a single ext3 or ext4 partition (not managed by LVM). Otherwise, read on." +msgstr "" + +#: ./doc/image-guide/ch_openstack_images.xml:93(title) +msgid "Non-Xen with cloud-init/cloud-tools: 1 ext3/ext4 partition (no LVM, no /boot, no swap)" +msgstr "" + +#: ./doc/image-guide/ch_openstack_images.xml:97(para) +msgid "The image's partition table describes the original size of the image" +msgstr "" + +#: ./doc/image-guide/ch_openstack_images.xml:101(para) +msgid "The image's filesystem fills the original size of the image" +msgstr "" + +#: ./doc/image-guide/ch_openstack_images.xml:95(para) +msgid "Your image must be configured to deal with two issues:" +msgstr "" + +#: ./doc/image-guide/ch_openstack_images.xml:110(para) +msgid "If you are not using LVM, you must modify the table to extend the existing root partition to encompass this additional space" +msgstr "" + +#: ./doc/image-guide/ch_openstack_images.xml:117(para) +msgid "If you are using LVM, you can create add a new LVM entry to the partition table, create a new LVM physical volume, add it to the volume group, and extend the logical partition with the root volume" +msgstr "" + +#: ./doc/image-guide/ch_openstack_images.xml:107(para) +msgid "the partition table must be modified to be made aware of the additional space" +msgstr "" + +#: ./doc/image-guide/ch_openstack_images.xml:128(para) +msgid "the root volume filesystem must be resized" +msgstr "" + +#: ./doc/image-guide/ch_openstack_images.xml:105(para) +msgid "Then, during the boot process:" +msgstr "" + +#: ./doc/image-guide/ch_openstack_images.xml:132(para) +msgid "The simplest way to support this in your image is to install the cloud-utils package (contains the tool for extending partitions), the cloud-initramfs-tools package (which will support resizing root partition on the first boot), and the cloud-init package into your image. With these installed, the image will perform the root partition resize on boot. For example, in the /etc/rc.local file. These packages are in the Ubuntu and Debian package repository, as well as the EPEL repository (for Fedora/RHEL/CentOS/Scientific Linux guests)." +msgstr "" + +#: ./doc/image-guide/ch_openstack_images.xml:150(para) +msgid "If you are not able to install cloud-initramfs-tools, Robert Plestenjak has a github project called linux-rootfs-resize that contains scripts that will update a ramdisk using so that the image will resize properly on boot." +msgstr "" + +#: ./doc/image-guide/ch_openstack_images.xml:158(para) +msgid "If you are able to install the cloud-utils and cloud-init packages, we recommend that when you create your images, you create a single ext3 or ext4 partition (not managed by LVM)." +msgstr "" + +#: ./doc/image-guide/ch_openstack_images.xml:164(title) +msgid "Non-Xen without cloud-init/cloud-tools: LVM" +msgstr "" + +#: ./doc/image-guide/ch_openstack_images.xml:165(para) +msgid "If you cannot install cloud-init and cloud-tools inside of your guest, and you want to support resize, you will need to write a script that your image will run on boot to modify the partition table. In this case, we recommend using LVM to manage your partitions. Due to a limitation in the Linux kernel (as of this writing), you cannot modify a partition table of a raw disk that has partition currently mounted, but you can do this for LVM." +msgstr "" + +#: ./doc/image-guide/ch_openstack_images.xml:176(para) +msgid "Detect if any additional space is available on the disk. For example, parse the output of ." +msgstr "" + +#: ./doc/image-guide/ch_openstack_images.xml:183(para) +msgid "Create a new LVM partition with the additional space. For example, ." +msgstr "" + +#: ./doc/image-guide/ch_openstack_images.xml:191(replaceable) ./doc/image-guide/ch_openstack_images.xml:198(replaceable) ./doc/image-guide/ch_openstack_images.xml:205(replaceable) +msgid "sda6" +msgstr "" + +#: ./doc/image-guide/ch_openstack_images.xml:189(para) +msgid "Create a new physical volume. For example, ." +msgstr "" + +#: ./doc/image-guide/ch_openstack_images.xml:197(replaceable) +msgid "vg00" +msgstr "" + +#: ./doc/image-guide/ch_openstack_images.xml:194(para) +msgid "Extend the volume group with this physical partition. For example, .)" +msgstr "" + +#: ./doc/image-guide/ch_openstack_images.xml:204(replaceable) ./doc/image-guide/ch_openstack_images.xml:210(replaceable) +msgid "node-root" +msgstr "" + +#: ./doc/image-guide/ch_openstack_images.xml:201(para) +msgid "Extend the logical volume contained the root partition by the amount of space. For example, ." +msgstr "" + +#: ./doc/image-guide/ch_openstack_images.xml:208(para) +msgid "Resize the root file system. For example, ." +msgstr "" + +#: ./doc/image-guide/ch_openstack_images.xml:174(para) +msgid "Your script will need to do something like the following:" +msgstr "" + +#: ./doc/image-guide/ch_openstack_images.xml:213(para) +msgid "You do not need to have a /boot partition, unless your image is an older Linux distribution that requires that /boot is not managed by LVM. You may elect to use a swap per" +msgstr "" + +#: ./doc/image-guide/ch_openstack_images.xml:231(para) +msgid "Replace /etc/udev/rules.d/70-persistent-net.rules with an empty file (contains network persistence rules, including MAC address)" +msgstr "" + +#: ./doc/image-guide/ch_openstack_images.xml:238(para) +msgid "Replace /lib/udev/rules.d/75-persistent-net-generator.rules with an empty file (this generates the file above)" +msgstr "" + +#: ./doc/image-guide/ch_openstack_images.xml:244(para) +msgid "Remove the HWADDR line from /etc/sysconfig/network-scripts/ifcfg-eth0 on Fedora-based images" +msgstr "" + +#: ./doc/image-guide/ch_openstack_images.xml:249(para) +msgid "If you delete the network persistent rules files, you may get a udev kernel warning at boot time, which is why we recommend replacing them with empty files instead." +msgstr "" + +#: ./doc/image-guide/ch_openstack_images.xml:222(para) +msgid "You must remove the network persistence rules in the image as their presence will result in the network interface in the instance coming up as an interface other than eth0. This is because your image has a record of the MAC address of the network interface card when it was first installed, and this MAC address will be different each time the instance boots up. You should alter the following files:" +msgstr "" + +#: ./doc/image-guide/ch_openstack_images.xml:257(title) +msgid "Ensure ssh server runs" +msgstr "" + +#: ./doc/image-guide/ch_openstack_images.xml:258(para) +msgid "You must install an ssh server into the image and ensure that it starts up on boot, or you will not be able to connect to your instance using ssh when it boots inside of OpenStack. This package is typically called openssh-server." +msgstr "" + +#: ./doc/image-guide/ch_openstack_images.xml:267(para) +msgid "In general, we recommend that you disable any firewalls inside of your image and use OpenStack security groups to restrict access to instances. The reason is that having a firewall installed on your instance can make it more difficult to troubleshoot networking issues if you cannot connect to your instance." +msgstr "" + +#: ./doc/image-guide/ch_openstack_images.xml:277(para) +msgid "The typical way that users access virtual machines running on OpenStack is to ssh using public key authentication. For this to work, your virtual machine image must be configured to download the ssh public key from the OpenStack metadata service or config drive, at boot time." +msgstr "" + +#: ./doc/image-guide/ch_openstack_images.xml:285(para) +msgid "The cloud-init package will automatically fetch the public key from the metadata server and place the key in an account. The account varies by distribution. On Ubuntu-based virtual machines, the account is called \"ubuntu\". On Fedora-based virtual machines, the account is called \"ec2-user\"." +msgstr "" + +#: ./doc/image-guide/ch_openstack_images.xml:301(title) +msgid "Write a custom script to fetch the public key" +msgstr "" + +#: ./doc/image-guide/ch_openstack_images.xml:303(para) +msgid "If you are unable or unwilling to install cloud-init inside the guest, you can write a custom script to fetch the public and add it to a user account." +msgstr "" + +#: ./doc/image-guide/ch_openstack_images.xml:306(para) +msgid "To fetch the ssh public key and add it to the root account, edit the /etc/rc.local file and add the following lines before the line “touch /var/lock/subsys/local”. This code fragment is taken from the rackerjoe oz-image-build CentOS 6 template." +msgstr "" + +#: ./doc/image-guide/ch_openstack_images.xml:346(para) +msgid "Some VNC clients replace : (colon) with ; (semicolon) and _ (underscore) with - (hyphen). If editing a file over a VNC session, make sure it's http: not http; and authorized_keys not authorized-keys." +msgstr "" + +#: ./doc/image-guide/ch_openstack_images.xml:360(para) +msgid "In additional the ssh public key, an image may need to retrieve additional information from OpenStack, such as user data that the user submitted when requesting the image. For example, you might want to set the host name of the instance to name given to the instance when it is booted. Or, you might wish to configure your image so that it executes user data content as a script on boot." +msgstr "" + +#: ./doc/image-guide/ch_openstack_images.xml:370(para) +msgid "This information is accessible through the metadata service or the config drive. As the OpenStack metadata service is compatible with version 2009-04-04 of the Amazon EC2 metadata service, consult the Amazon EC2 documentation on Using Instance Metadata for details on how to retrieve user data." +msgstr "" + +#: ./doc/image-guide/ch_openstack_images.xml:381(para) +msgid "The easiest way to support this type of functionality is to install the cloud-init package into your image, which is configured by default to treat user data as an executable script, and will set the host name." +msgstr "" + +#: ./doc/image-guide/ch_openstack_images.xml:387(title) +msgid "Ensure image writes boot log to console" +msgstr "" + +#: ./doc/image-guide/ch_openstack_images.xml:388(para) +msgid "You must configure the image so that the kernel writes the boot log to the ttyS0 device. In particular, the console=ttyS0 argument must be passed to the kernel on boot." +msgstr "" + +#: ./doc/image-guide/ch_openstack_images.xml:392(para) +msgid "If your image uses grub2 as the boot loader, there should be a line in the grub configuration file. For example, /boot/grub/grub.cfg, which looks something like this:" +msgstr "" + +#: ./doc/image-guide/ch_openstack_images.xml:397(para) +msgid "If console=ttyS0 does not appear, you will need to modify your grub configuration. In general, you should not update the grub.cfg directly, since it is automatically generated. Instead, you should edit /etc/default/grub and modify the value of the GRUB_CMDLINE_LINUX_DEFAULT variable: " +msgstr "" + +#: ./doc/image-guide/ch_openstack_images.xml:405(para) +msgid "Next, update the grub configuration. On Debian-based operating-systems such as Ubuntu, do:" +msgstr "" + +#: ./doc/image-guide/ch_openstack_images.xml:408(para) +msgid "On Fedora-based systems such as RHEL and CentOS, do:" +msgstr "" + +#: ./doc/image-guide/ch_openstack_images.xml:413(title) +msgid "Paravirtualized Xen support in the kernel (Xen hypervisor only)" +msgstr "" + +#: ./doc/image-guide/ch_openstack_images.xml:415(para) +msgid "Prior to Linux kernel version 3.0, the mainline branch of the Linux kernel did not have support paravirtualized Xen virtual machine instances (what Xen calls DomU guests). If you are running the Xen hypervisor with paravirtualization, and you want to create an image for an older Linux distribution that has a pre 3.0 kernel, you will need to ensure that the image boots a kernel that has been compiled with Xen support." +msgstr "" + +#: ./doc/image-guide/ch_openstack_images.xml:425(title) +msgid "Manage the image cache" +msgstr "" + +#: ./doc/image-guide/ch_openstack_images.xml:426(para) +msgid "Use options in nova.conf to control whether, and for how long, unused base images are stored in /var/lib/nova/instances/_base/. If you have configured live migration of instances, all your compute nodes share one common /var/lib/nova/instances/ directory." +msgstr "" + +#: ./doc/image-guide/ch_openstack_images.xml:433(para) +msgid "For information about libvirt images in OpenStack, refer to The life of an OpenStack libvirt image from Pádraig Brady." +msgstr "" + +#: ./doc/image-guide/ch_openstack_images.xml:439(caption) +msgid "Image cache management configuration options" +msgstr "" + +#: ./doc/image-guide/ch_openstack_images.xml:445(td) +msgid "Configuration option=Default value" +msgstr "" + +#: ./doc/image-guide/ch_openstack_images.xml:446(td) +msgid "(Type) Description" +msgstr "" + +#: ./doc/image-guide/ch_openstack_images.xml:451(td) +msgid "preallocate_images=none" +msgstr "" + +#: ./doc/image-guide/ch_openstack_images.xml:459(link) +msgid "fallocate" +msgstr "" + +#: ./doc/image-guide/ch_openstack_images.xml:452(td) +msgid "(StrOpt) VM image preallocation mode: \"none\" => no storage provisioning is done up front, \"space\" => storage is fully allocated at instance start. If this is set to 'space', the $instance_dir/ images will be  d to immediately determine if enough space is available, and to possibly improve VM I/O performance due to ongoing allocation avoidance, and better locality of block allocations." +msgstr "" + +#: ./doc/image-guide/ch_openstack_images.xml:466(td) +msgid "remove_unused_base_images=True" +msgstr "" + +#: ./doc/image-guide/ch_openstack_images.xml:467(td) +msgid "(BoolOpt) Should unused base images be removed? When set to True, the interval at which base images are removed are set with the following two settings. If set to False base images are never removed by Compute." +msgstr "" + +#: ./doc/image-guide/ch_openstack_images.xml:474(td) +msgid "remove_unused_original_minimum_age_seconds=86400" +msgstr "" + +#: ./doc/image-guide/ch_openstack_images.xml:475(td) +msgid "(IntOpt) Unused unresized base images younger than this will not be removed. Default is 86400 seconds, or 24 hours." +msgstr "" + +#: ./doc/image-guide/ch_openstack_images.xml:480(td) +msgid "remove_unused_resized_minimum_age_seconds=3600" +msgstr "" + +#: ./doc/image-guide/ch_openstack_images.xml:481(td) +msgid "(IntOpt) Unused resized base images younger than this will not be removed. Default is 3600 seconds, or one hour." +msgstr "" + +#: ./doc/image-guide/ch_openstack_images.xml:487(para) +msgid "To see how the settings affect the deletion of a running instance, check the directory where the images are stored:" +msgstr "" + +#: ./doc/image-guide/ch_openstack_images.xml:491(para) +msgid "Then look for the identifier in /var/log/compute/compute.log:" +msgstr "" + +#: ./doc/image-guide/ch_openstack_images.xml:498(para) +msgid "Since 86400 seconds (24 hours) is the default time for remove_unused_original_minimum_age_seconds, you can either wait for that time interval to see the base image removed, or set the value to a shorter time period in nova.conf. Restart all nova services after changing a setting in nova.conf." +msgstr "" + +#: ./doc/image-guide/section_windows-example.xml:8(title) +msgid "Example: Microsoft Windows image" +msgstr "" + +#: ./doc/image-guide/section_windows-example.xml:9(para) +msgid "We do not yet have a fully documented example of how to create a Microsoft Windows image. You can use libvirt to install Windows from an installation DVD using the same approach as with the CentOS and Ubuntu examples. Once the initial install is done, you will need to perform some Windows-specific customizations." +msgstr "" + +#: ./doc/image-guide/section_windows-example.xml:14(title) +msgid "Install VirtIO drivers" +msgstr "" + +#: ./doc/image-guide/section_windows-example.xml:15(para) +msgid "Installing the VirtIO paravirtualizaion drivers for Windows will improve virtual machine performance when using KVM as the hypervisor to run Windows." +msgstr "" + +#: ./doc/image-guide/section_windows-example.xml:20(title) +msgid "Sysprep" +msgstr "" + +#: ./doc/image-guide/section_windows-example.xml:21(para) +msgid "Microsoft has a special tool called Sysprep that must be run inside of a Windows guest to prepare it for use as a virtual machine image. On Windows 2012 server, invoke sysprep, as follows: " +msgstr "" + +#: ./doc/image-guide/section_windows-example.xml:28(title) +msgid "cloudbase-init" +msgstr "" + +#: ./doc/image-guide/section_windows-example.xml:29(para) +msgid "cloudbase-init is a Windows port of cloud-init that should be installed inside of the guest. The source code is available on github." +msgstr "" + +#: ./doc/image-guide/section_windows-example.xml:35(title) +msgid "Jordan Rinke's OpenStack Windows resources" +msgstr "" + +#: ./doc/image-guide/section_windows-example.xml:36(para) +msgid "Jordan Rinke maintains a collection of resources for managing OpenStack Windows virtual machine guests." +msgstr "" + +#: ./doc/image-guide/section_windows-example.xml:41(title) +msgid "Windows instances require the timezone to be \"localtime\"" +msgstr "" + +#: ./doc/image-guide/section_windows-example.xml:42(para) +msgid "When uploading Windows images, you must set the os_type parameter to windows, which causes instances to use the local time zone. Failing to set this will cause the clock timezone to be UTC, which has unexpected side effects in Windows." +msgstr "" + +#: ./doc/image-guide/section_freebsd-example.xml:8(title) +msgid "Example: FreeBSD image" +msgstr "" + +#: ./doc/image-guide/section_freebsd-example.xml:9(para) +msgid "We do not yet have a fully documented example of how to create a FreeBSD image." +msgstr "" + +#: ./doc/image-guide/section_freebsd-example.xml:11(para) +msgid "See the bsd-cloudinit project for information on how to build a FreeBSD VM image that works with OpenStack." +msgstr "" + +#. When image changes, this message will be marked fuzzy or untranslated for you. +#. It doesn't matter what you translate it to: it's not used at all. +#: ./doc/image-guide/ch_creating_images_manually.xml:78(None) +msgid "@@image: 'figures/virt-manager-new.png'; md5=3528ebfc1b945b7dd80a34897b8fe98e" +msgstr "" + +#: ./doc/image-guide/ch_creating_images_manually.xml:6(title) +msgid "Create images manually" +msgstr "" + +#: ./doc/image-guide/ch_creating_images_manually.xml:7(para) +msgid "Creating a new image is a step done outside of your OpenStack installation. You create the new image manually on your own system and then upload the image to your cloud." +msgstr "" + +#: ./doc/image-guide/ch_creating_images_manually.xml:11(para) +msgid "To create a new image, you will need the installation CD or DVD ISO file for the guest operating system. You'll also need access to a virtualization tool. You can use KVM for this. Or, if you have a GUI desktop virtualization tool (such as, VMWare Fusion and VirtualBox), you can use that instead and just convert the file to raw once you're done." +msgstr "" + +#: ./doc/image-guide/ch_creating_images_manually.xml:17(para) +msgid "When you create a new virtual machine image, you will need to connect to the graphical console of the hypervisor, which acts as the virtual machine's display and allows you to interact with the guest operating system's installer using your keyboard and mouse. KVM can expose the graphical console using the VNC (Virtual Network Computing) protocol or the newer SPICE protocol. We'll use the VNC protocol here, since you're more likely to be able to find a VNC client that works on your local desktop." +msgstr "" + +#: ./doc/image-guide/ch_creating_images_manually.xml:30(title) +msgid "Verify the libvirt default network is running" +msgstr "" + +#: ./doc/image-guide/ch_creating_images_manually.xml:31(para) +msgid "Before starting a virtual machine with libvirt, verify that the libvirt \"default\" network has been started. This network must be active for your virtual machine to be able to connect out to the network. Starting this network will create a Linux bridge (usually called virbr0), iptables rules, and a dnsmasq process that will serve as a DHCP server." +msgstr "" + +#: ./doc/image-guide/ch_creating_images_manually.xml:38(para) +msgid "To verify that the libvirt \"default\" network is enabled, use the command and verify that the \"default\" network is active:" +msgstr "" + +#: ./doc/image-guide/ch_creating_images_manually.xml:45(para) +msgid "If the network is not active, start it by doing:" +msgstr "" + +#: ./doc/image-guide/ch_creating_images_manually.xml:49(title) +msgid "Use the virt-manager X11 GUI" +msgstr "" + +#: ./doc/image-guide/ch_creating_images_manually.xml:50(para) +msgid "If you plan to create a virtual machine image on a machine that can run X11 applications, the simplest way to do so is to use the GUI, which is installable as the virt-manager package on both Fedora-based and Debian-based systems. This GUI has an embedded VNC client in it that will let you view and interact with the guest's graphical console." +msgstr "" + +#: ./doc/image-guide/ch_creating_images_manually.xml:58(para) +msgid "If you are building the image on a headless server, and you have an X server on your local machine, you can launch  using ssh X11 forwarding to access the GUI. Since virt-manager interacts directly with libvirt, you typically need to be root to access it. If you can ssh directly in as root (or with a user that has permissions to interact with libvirt), do:" +msgstr "" + +#: ./doc/image-guide/ch_creating_images_manually.xml:69(para) +msgid "The -X flag passed to ssh will enable X11 forwarding over ssh. If this does not work, try replacing it with the -Y flag." +msgstr "" + +#: ./doc/image-guide/ch_creating_images_manually.xml:66(para) +msgid "If the account you use to ssh into your server does not have permissions to run libvirt, but has sudo privileges, do:" +msgstr "" + +#: ./doc/image-guide/ch_creating_images_manually.xml:74(para) +msgid "Click the \"New\" button at the top-left and step through the instructions. You will be shown a series of dialog boxes that will allow you to specify information about the virtual machine." +msgstr "" + +#: ./doc/image-guide/ch_creating_images_manually.xml:83(para) +msgid "When using qcow2 format images you should check the option 'customize before install', go to disk properties and explicitly select the qcow2 format. The ensures the virtual machine disk size will be correct." +msgstr "" + +#: ./doc/image-guide/ch_creating_images_manually.xml:91(title) +msgid "Use virt-install and connect by using a local VNC client" +msgstr "" + +#: ./doc/image-guide/ch_creating_images_manually.xml:93(para) +msgid "If you do not wish to use virt-manager (for example, you do not want to install the dependencies on your server, you don't have an X server running locally, the X11 forwarding over SSH isn't working), you can use the tool to boot the virtual machine through libvirt and connect to the graphical console from a VNC client installed on your local machine." +msgstr "" + +#: ./doc/image-guide/ch_creating_images_manually.xml:101(para) +msgid "Because VNC is a standard protocol, there are multiple clients available that implement the VNC spec, including TigerVNC (multiple platforms), TightVNC (multiple platforms), RealVNC (multiple platforms), Chicken (Mac OS X), Krde (KDE), and Vinagre (GNOME)." +msgstr "" + +#: ./doc/image-guide/ch_creating_images_manually.xml:116(para) +msgid "The following example shows how to use the command to create an empty image file command to start up a virtual machine using that image file. As root:" +msgstr "" + +#: ./doc/image-guide/ch_creating_images_manually.xml:148(para) +msgid "When using the libvirt default network, libvirt will connect the virtual machine's interface to a bridge called virbr0. There is a dnsmasq process managed by libvirt that will hand out an IP address on the 192.168.122.0/24 subnet, and libvirt has iptables rules for doing NAT for IP addresses on this subnet." +msgstr "" + +#: ./doc/image-guide/ch_creating_images_manually.xml:133(para) +msgid "This uses the KVM hypervisor to start up a virtual machine with the libvirt name of centos-6.4 with 1024MB of RAM, with a virtual CD-ROM drive associated with the /data/CentOS-6.4-x86_64-netinstall.iso file, and a local hard disk which is stored in the host at /data/centos-6.4.qcow2 that is 10GB in size in qcow2 format. It configures networking to use libvirt's default network. There is a VNC server that is listening on all interfaces, and libvirt will not attempt to launch a VNC client automatically nor try to display the text console (--no-autoconsole). Finally, libvirt will attempt to optimize the configuration for a Linux guest running a RHEL 6.x distribution." +msgstr "" + +#: ./doc/image-guide/ch_creating_images_manually.xml:157(para) +msgid "Run the command to see a range of allowed --os-variant options." +msgstr "" + +#: ./doc/image-guide/ch_creating_images_manually.xml:161(replaceable) +msgid "vm-name" +msgstr "" + +#: ./doc/image-guide/ch_creating_images_manually.xml:160(para) +msgid "Use the command to get the VNC port number." +msgstr "" + +#: ./doc/image-guide/ch_creating_images_manually.xml:165(para) +msgid "In the example above, the guest centos-6.4 uses VNC display :1, which corresponds to tcp port 5901. You should be able to connect to a VNC client running on your local machine to display :1 on the remote machine and step through the installation process." +msgstr "" + +#: ./doc/image-guide/ch_preface.xml:10(title) +msgid "Preface" +msgstr "" + +#: ./doc/image-guide/section_glance_image-formats.xml:6(title) +msgid "Disk and container formats for images" +msgstr "" + +#: ./doc/image-guide/section_glance_image-formats.xml:8(para) +msgid "When you add an image to the Image Service, you can specify its disk and container formats." +msgstr "" + +#: ./doc/image-guide/section_glance_image-formats.xml:11(title) +msgid "Disk formats" +msgstr "" + +#: ./doc/image-guide/section_glance_image-formats.xml:12(para) +msgid "The disk format of a virtual machine image is the format of the underlying disk image. Virtual appliance vendors have different formats for laying out the information contained in a virtual machine disk image." +msgstr "" + +#: ./doc/image-guide/section_glance_image-formats.xml:16(para) +msgid "Set the disk format for your image to one of the following values:" +msgstr "" + +#: ./doc/image-guide/section_glance_image-formats.xml:20(para) +msgid "raw. An unstructured disk image format; if you have a file without an extension it is possibly a raw format" +msgstr "" + +#: ./doc/image-guide/section_glance_image-formats.xml:25(para) +msgid "vhd. The VHD disk format, a common disk format used by virtual machine monitors from VMWare, Xen, Microsoft, VirtualBox, and others" +msgstr "" + +#: ./doc/image-guide/section_glance_image-formats.xml:31(para) +msgid "vmdk. Common disk format supported by many common virtual machine monitors" +msgstr "" + +#: ./doc/image-guide/section_glance_image-formats.xml:36(para) +msgid "vdi. Supported by VirtualBox virtual machine monitor and the QEMU emulator" +msgstr "" + +#: ./doc/image-guide/section_glance_image-formats.xml:41(para) +msgid "iso. An archive format for the data contents of an optical disc, such as CD-ROM." +msgstr "" + +#: ./doc/image-guide/section_glance_image-formats.xml:46(para) +msgid "qcow2. Supported by the QEMU emulator that can expand dynamically and supports Copy on Write" +msgstr "" + +#: ./doc/image-guide/section_glance_image-formats.xml:51(para) ./doc/image-guide/section_glance_image-formats.xml:87(para) +msgid "aki. An Amazon kernel image." +msgstr "" + +#: ./doc/image-guide/section_glance_image-formats.xml:55(para) ./doc/image-guide/section_glance_image-formats.xml:91(para) +msgid "ari. An Amazon ramdisk image." +msgstr "" + +#: ./doc/image-guide/section_glance_image-formats.xml:59(para) ./doc/image-guide/section_glance_image-formats.xml:95(para) +msgid "ami. An Amazon machine image." +msgstr "" + +#: ./doc/image-guide/section_glance_image-formats.xml:65(title) +msgid "Container formats" +msgstr "" + +#: ./doc/image-guide/section_glance_image-formats.xml:66(para) +msgid "The container format indicates whether the virtual machine image is in a file format that also contains metadata about the actual virtual machine." +msgstr "" + +#: ./doc/image-guide/section_glance_image-formats.xml:70(para) +msgid "The Image Service and other OpenStack projects do not currently support the container format. It is safe to specify bare as the container format if you are unsure." +msgstr "" + +#: ./doc/image-guide/section_glance_image-formats.xml:75(para) +msgid "You can set the container format for your image to one of the following values:" +msgstr "" + +#: ./doc/image-guide/section_glance_image-formats.xml:79(para) +msgid "bare. The image does not have a container or metadata envelope." +msgstr "" + +#: ./doc/image-guide/section_glance_image-formats.xml:83(para) +msgid "ovf. The OVF container format." +msgstr "" + +#: ./doc/image-guide/section_glance-image-metadata.xml:7(title) +msgid "Image metadata" +msgstr "" + +#: ./doc/image-guide/section_glance-image-metadata.xml:9(para) +msgid "You can associate metadata with an image using the --property key=value argument to or . For example:" +msgstr "" + +#: ./doc/image-guide/section_glance-image-metadata.xml:14(replaceable) +msgid "img-uuid" +msgstr "" + +#: ./doc/image-guide/section_glance-image-metadata.xml:15(para) +msgid "If the following properties are set on an image, and the ImagePropertiesFilter scheduler filter is enabled (which it is by default), then the scheduler will only consider compute hosts that satisfy these properties:" +msgstr "" + +#: ./doc/image-guide/section_glance-image-metadata.xml:20(term) +msgid "architecture" +msgstr "" + +#: ./doc/image-guide/section_glance-image-metadata.xml:31(literal) +msgid "alpha" +msgstr "" + +#: ./doc/image-guide/section_glance-image-metadata.xml:35(link) +msgid "DEC 64-bit RISC" +msgstr "" + +#: ./doc/image-guide/section_glance-image-metadata.xml:40(literal) +msgid "armv7l" +msgstr "" + +#: ./doc/image-guide/section_glance-image-metadata.xml:44(link) +msgid "ARM Cortex-A7 MPCore" +msgstr "" + +#: ./doc/image-guide/section_glance-image-metadata.xml:49(literal) +msgid "cris" +msgstr "" + +#: ./doc/image-guide/section_glance-image-metadata.xml:53(link) +msgid "Ethernet, Token Ring, AXis - Code Reduced Instruction Set" +msgstr "" + +#: ./doc/image-guide/section_glance-image-metadata.xml:58(literal) +msgid "i686" +msgstr "" + +#: ./doc/image-guide/section_glance-image-metadata.xml:60(para) +msgid "Intel sixth-generation x86 (P6 micro architecture)" +msgstr "" + +#: ./doc/image-guide/section_glance-image-metadata.xml:68(literal) +msgid "ia64" +msgstr "" + +#: ./doc/image-guide/section_glance-image-metadata.xml:72(link) +msgid "Itanium" +msgstr "" + +#: ./doc/image-guide/section_glance-image-metadata.xml:77(literal) +msgid "lm32" +msgstr "" + +#: ./doc/image-guide/section_glance-image-metadata.xml:81(link) +msgid "Lattice Micro32" +msgstr "" + +#: ./doc/image-guide/section_glance-image-metadata.xml:86(literal) +msgid "m68k" +msgstr "" + +#: ./doc/image-guide/section_glance-image-metadata.xml:90(link) +msgid "Motorola 68000" +msgstr "" + +#: ./doc/image-guide/section_glance-image-metadata.xml:95(literal) +msgid "microblaze" +msgstr "" + +#: ./doc/image-guide/section_glance-image-metadata.xml:99(link) +msgid "Xilinx 32-bit FPGA (Big Endian)" +msgstr "" + +#: ./doc/image-guide/section_glance-image-metadata.xml:104(literal) +msgid "microblazeel" +msgstr "" + +#: ./doc/image-guide/section_glance-image-metadata.xml:108(link) +msgid "Xilinx 32-bit FPGA (Little Endian)" +msgstr "" + +#: ./doc/image-guide/section_glance-image-metadata.xml:113(literal) +msgid "mips" +msgstr "" + +#: ./doc/image-guide/section_glance-image-metadata.xml:117(link) +msgid "MIPS 32-bit RISC (Big Endian)" +msgstr "" + +#: ./doc/image-guide/section_glance-image-metadata.xml:122(literal) +msgid "mipsel" +msgstr "" + +#: ./doc/image-guide/section_glance-image-metadata.xml:126(link) +msgid "MIPS 32-bit RISC (Little Endian)" +msgstr "" + +#: ./doc/image-guide/section_glance-image-metadata.xml:131(literal) +msgid "mips64" +msgstr "" + +#: ./doc/image-guide/section_glance-image-metadata.xml:135(link) +msgid "MIPS 64-bit RISC (Big Endian)" +msgstr "" + +#: ./doc/image-guide/section_glance-image-metadata.xml:140(literal) +msgid "mips64el" +msgstr "" + +#: ./doc/image-guide/section_glance-image-metadata.xml:144(link) +msgid "MIPS 64-bit RISC (Little Endian)" +msgstr "" + +#: ./doc/image-guide/section_glance-image-metadata.xml:149(literal) +msgid "openrisc" +msgstr "" + +#: ./doc/image-guide/section_glance-image-metadata.xml:153(link) +msgid "OpenCores RISC" +msgstr "" + +#: ./doc/image-guide/section_glance-image-metadata.xml:158(literal) +msgid "parisc" +msgstr "" + +#: ./doc/image-guide/section_glance-image-metadata.xml:162(link) +msgid "HP Precision Architecture RISC" +msgstr "" + +#: ./doc/image-guide/section_glance-image-metadata.xml:167(literal) +msgid "parisc64" +msgstr "" + +#: ./doc/image-guide/section_glance-image-metadata.xml:171(link) +msgid "HP Precision Architecture 64-bit RISC" +msgstr "" + +#: ./doc/image-guide/section_glance-image-metadata.xml:176(literal) +msgid "ppc" +msgstr "" + +#: ./doc/image-guide/section_glance-image-metadata.xml:180(link) +msgid "PowerPC 32-bit" +msgstr "" + +#: ./doc/image-guide/section_glance-image-metadata.xml:185(literal) +msgid "ppc64" +msgstr "" + +#: ./doc/image-guide/section_glance-image-metadata.xml:189(link) +msgid "PowerPC 64-bit" +msgstr "" + +#: ./doc/image-guide/section_glance-image-metadata.xml:194(literal) +msgid "ppcemb" +msgstr "" + +#: ./doc/image-guide/section_glance-image-metadata.xml:198(link) +msgid "PowerPC (Embedded 32-bit)" +msgstr "" + +#: ./doc/image-guide/section_glance-image-metadata.xml:203(literal) +msgid "s390" +msgstr "" + +#: ./doc/image-guide/section_glance-image-metadata.xml:207(link) +msgid "IBM Enterprise Systems Architecture/390" +msgstr "" + +#: ./doc/image-guide/section_glance-image-metadata.xml:212(literal) +msgid "s390x" +msgstr "" + +#: ./doc/image-guide/section_glance-image-metadata.xml:216(link) +msgid "S/390 64-bit" +msgstr "" + +#: ./doc/image-guide/section_glance-image-metadata.xml:221(literal) +msgid "sh4" +msgstr "" + +#: ./doc/image-guide/section_glance-image-metadata.xml:225(link) +msgid "SuperH SH-4 (Little Endian)" +msgstr "" + +#: ./doc/image-guide/section_glance-image-metadata.xml:230(literal) +msgid "sh4eb" +msgstr "" + +#: ./doc/image-guide/section_glance-image-metadata.xml:234(link) +msgid "SuperH SH-4 (Big Endian)" +msgstr "" + +#: ./doc/image-guide/section_glance-image-metadata.xml:239(literal) +msgid "sparc" +msgstr "" + +#: ./doc/image-guide/section_glance-image-metadata.xml:243(link) +msgid "Scalable Processor Architecture, 32-bit" +msgstr "" + +#: ./doc/image-guide/section_glance-image-metadata.xml:248(literal) +msgid "sparc64" +msgstr "" + +#: ./doc/image-guide/section_glance-image-metadata.xml:252(link) +msgid "Scalable Processor Architecture, 64-bit" +msgstr "" + +#: ./doc/image-guide/section_glance-image-metadata.xml:257(literal) +msgid "unicore32" +msgstr "" + +#: ./doc/image-guide/section_glance-image-metadata.xml:261(link) +msgid "Microprocessor Research and Development Center RISC Unicore32" +msgstr "" + +#: ./doc/image-guide/section_glance-image-metadata.xml:267(literal) +msgid "x86_64" +msgstr "" + +#: ./doc/image-guide/section_glance-image-metadata.xml:271(link) +msgid "64-bit extension of IA-32" +msgstr "" + +#: ./doc/image-guide/section_glance-image-metadata.xml:276(literal) +msgid "xtensa" +msgstr "" + +#: ./doc/image-guide/section_glance-image-metadata.xml:280(link) +msgid "Tensilica Xtensa configurable microprocessor core" +msgstr "" + +#: ./doc/image-guide/section_glance-image-metadata.xml:285(literal) +msgid "xtensaeb" +msgstr "" + +#: ./doc/image-guide/section_glance-image-metadata.xml:289(link) +msgid "Tensilica Xtensa configurable microprocessor core (Big Endian)" +msgstr "" + +#: ./doc/image-guide/section_glance-image-metadata.xml:22(para) +msgid "The CPU architecture that must be supported by the hypervisor. For example, x86_64, arm, or ppc64. Run to get the architecture of a machine. We strongly recommend using the architecture data vocabulary defined by the libosinfo project for this purpose. Recognized values for this field are: " +msgstr "" + +#: ./doc/image-guide/section_glance-image-metadata.xml:299(term) +msgid "hypervisor_type" +msgstr "" + +#: ./doc/image-guide/section_glance-image-metadata.xml:301(para) +msgid "The hypervisor type. Allowed values include: xen, qemu, kvm, lxc, uml, vmware, hyperv." +msgstr "" + +#: ./doc/image-guide/section_glance-image-metadata.xml:308(term) +msgid "vm_mode" +msgstr "" + +#: ./doc/image-guide/section_glance-image-metadata.xml:314(literal) +msgid "hvm" +msgstr "" + +#: ./doc/image-guide/section_glance-image-metadata.xml:316(para) +msgid "Fully virtualized. This is the mode used by QEMU and KVM." +msgstr "" + +#: ./doc/image-guide/section_glance-image-metadata.xml:321(literal) +msgid "xen" +msgstr "" + +#: ./doc/image-guide/section_glance-image-metadata.xml:323(para) +msgid "Xen 3.0 paravirtualized." +msgstr "" + +#: ./doc/image-guide/section_glance-image-metadata.xml:327(literal) +msgid "uml" +msgstr "" + +#: ./doc/image-guide/section_glance-image-metadata.xml:329(para) +msgid "User Mode Linux paravirtualized." +msgstr "" + +#: ./doc/image-guide/section_glance-image-metadata.xml:333(literal) +msgid "exe" +msgstr "" + +#: ./doc/image-guide/section_glance-image-metadata.xml:335(para) +msgid "Executables in containers. This is the mode used by LXC." +msgstr "" + +#: ./doc/image-guide/section_glance-image-metadata.xml:310(para) +msgid "The virtual machine mode. This represents the host/guest ABI (application binary interface) used for the virtual machine. Allowed values are:" +msgstr "" + +#: ./doc/image-guide/section_glance-image-metadata.xml:342(para) +msgid "The following metadata properties are specific to the XenAPI driver:" +msgstr "" + +#: ./doc/image-guide/section_glance-image-metadata.xml:344(term) +msgid "auto_disk_config" +msgstr "" + +#: ./doc/image-guide/section_glance-image-metadata.xml:346(para) +msgid "A boolean option. If true, the root partition on the disk will be automatically resized before the instance boots. This value is only taken into account by the Compute service when using a Xen-based hypervisor with the XenAPI driver. The Compute service will only attempt to resize if there is a single partition on the image, and only if the partition is in ext3 or ext4 format." +msgstr "" + +#: ./doc/image-guide/section_glance-image-metadata.xml:355(term) +msgid "os_type" +msgstr "" + +#: ./doc/image-guide/section_glance-image-metadata.xml:357(para) +msgid "The operating system installed on the image. For example, linux or windows. The XenAPI driver contains logic that will take different actions depending on the value of the os_type parameter of the image. For example, for images where os_type=windows, it creates a FAT32-based swap partition instead of a Linux swap partition, and it limits the injected host name to less than 16 characters." +msgstr "" + +#: ./doc/image-guide/section_glance-image-metadata.xml:373(term) +msgid "hw_video_model" +msgstr "" + +#: ./doc/image-guide/section_glance-image-metadata.xml:375(para) +msgid "The video image driver used. Allowed values include: vga, cirrus, vmvga, xen and qxl." +msgstr "" + +#: ./doc/image-guide/section_glance-image-metadata.xml:369(para) +msgid "The following metadata properties are specific to the libvirt API driver: " +msgstr "" + +#: ./doc/image-guide/section_glance-image-metadata.xml:384(para) +msgid "The following metadata properties are specific to the VMware API driver:" +msgstr "" + +#: ./doc/image-guide/section_glance-image-metadata.xml:387(term) +msgid "vmware_adaptertype" +msgstr "" + +#: ./doc/image-guide/section_glance-image-metadata.xml:389(para) +msgid "Indicates the virtual SCSI or IDE controller used by the hypervisor. Allowed values: lsiLogic, busLogic, ide" +msgstr "" + +#: ./doc/image-guide/section_glance-image-metadata.xml:395(term) +msgid "vmware_ostype" +msgstr "" + +#: ./doc/image-guide/section_glance-image-metadata.xml:397(para) +msgid "A VMware GuestID which describes the operating system installed in the image. This will be passed to the hypervisor when creating a virtual machine. See thinkvirt.com for a list of valid values. If this is not specified, it will default to otherGuest." +msgstr "" + +#: ./doc/image-guide/section_glance-image-metadata.xml:406(term) +msgid "vmware_image_version" +msgstr "" + +#: ./doc/image-guide/section_glance-image-metadata.xml:408(para) +msgid "Currently unused, set it to 1." +msgstr "" + +#: ./doc/image-guide/section_glance-image-metadata.xml:412(para) +msgid "To assist end-users in utilizing images, you may wish to put additional common metadata on Glance images. By community agreement, the following metadata keys may be used across Glance installations for the purposes described, as follows." +msgstr "" + +#: ./doc/image-guide/section_glance-image-metadata.xml:417(term) +msgid "instance_uuid" +msgstr "" + +#: ./doc/image-guide/section_glance-image-metadata.xml:419(para) +msgid "For snapshot images, this is the UUID of the server used to create this image." +msgstr "" + +#: ./doc/image-guide/section_glance-image-metadata.xml:425(term) +msgid "kernel_id" +msgstr "" + +#: ./doc/image-guide/section_glance-image-metadata.xml:427(para) +msgid "The ID of image stored in Glance that should be used as the kernel when booting an AMI-style image." +msgstr "" + +#: ./doc/image-guide/section_glance-image-metadata.xml:434(term) +msgid "ramdisk_id" +msgstr "" + +#: ./doc/image-guide/section_glance-image-metadata.xml:436(para) +msgid "The ID of image stored in Glance that should be used as the ramdisk when booting an AMI-style image." +msgstr "" + +#: ./doc/image-guide/section_glance-image-metadata.xml:443(term) +msgid "os_version" +msgstr "" + +#: ./doc/image-guide/section_glance-image-metadata.xml:445(para) +msgid "The operating system version as specified by the distributor." +msgstr "" + +#: ./doc/image-guide/section_glance-image-metadata.xml:451(term) +msgid "os_distro" +msgstr "" + +#: ./doc/image-guide/section_glance-image-metadata.xml:464(literal) +msgid "arch" +msgstr "" + +#: ./doc/image-guide/section_glance-image-metadata.xml:466(para) +msgid "This is: Arch Linux" +msgstr "" + +#: ./doc/image-guide/section_glance-image-metadata.xml:469(para) +msgid "Do not use: archlinux, or org.archlinux" +msgstr "" + +#: ./doc/image-guide/section_glance-image-metadata.xml:477(literal) +msgid "centos" +msgstr "" + +#: ./doc/image-guide/section_glance-image-metadata.xml:479(para) +msgid "This is: Community Enterprise Operating System" +msgstr "" + +#: ./doc/image-guide/section_glance-image-metadata.xml:482(para) +msgid "Do not use: org.centos, or CentOS" +msgstr "" + +#: ./doc/image-guide/section_glance-image-metadata.xml:490(literal) +msgid "debian" +msgstr "" + +#: ./doc/image-guide/section_glance-image-metadata.xml:492(para) +msgid "This is: Debian" +msgstr "" + +#: ./doc/image-guide/section_glance-image-metadata.xml:495(para) +msgid "Do not use: Debian, or org.debian" +msgstr "" + +#: ./doc/image-guide/section_glance-image-metadata.xml:503(literal) +msgid "fedora" +msgstr "" + +#: ./doc/image-guide/section_glance-image-metadata.xml:505(para) +msgid "This is: Fedora" +msgstr "" + +#: ./doc/image-guide/section_glance-image-metadata.xml:508(para) +msgid "Do not use: Fedora, org.fedora, or org.fedoraproject" +msgstr "" + +#: ./doc/image-guide/section_glance-image-metadata.xml:517(literal) +msgid "freebsd" +msgstr "" + +#: ./doc/image-guide/section_glance-image-metadata.xml:519(para) +msgid "This is: FreeBSD" +msgstr "" + +#: ./doc/image-guide/section_glance-image-metadata.xml:522(para) +msgid "Do not use: org.freebsd, freeBSD, or FreeBSD" +msgstr "" + +#: ./doc/image-guide/section_glance-image-metadata.xml:531(literal) +msgid "gentoo" +msgstr "" + +#: ./doc/image-guide/section_glance-image-metadata.xml:533(para) +msgid "This is: Gentoo Linux" +msgstr "" + +#: ./doc/image-guide/section_glance-image-metadata.xml:536(para) +msgid "Do not use: Gentoo, or org.gentoo" +msgstr "" + +#: ./doc/image-guide/section_glance-image-metadata.xml:544(literal) +msgid "mandrake" +msgstr "" + +#: ./doc/image-guide/section_glance-image-metadata.xml:546(para) +msgid "This is: Mandrakelinux (MandrakeSoft)" +msgstr "" + +#: ./doc/image-guide/section_glance-image-metadata.xml:549(para) +msgid "Do not use: mandrakelinux, or MandrakeLinux" +msgstr "" + +#: ./doc/image-guide/section_glance-image-metadata.xml:557(literal) +msgid "mandriva" +msgstr "" + +#: ./doc/image-guide/section_glance-image-metadata.xml:559(para) +msgid "This is: Mandriva Linux" +msgstr "" + +#: ./doc/image-guide/section_glance-image-metadata.xml:562(para) +msgid "Do not use: mandrivalinux" +msgstr "" + +#: ./doc/image-guide/section_glance-image-metadata.xml:569(literal) +msgid "mes" +msgstr "" + +#: ./doc/image-guide/section_glance-image-metadata.xml:571(para) +msgid "This is: Mandriva Enterprise Server" +msgstr "" + +#: ./doc/image-guide/section_glance-image-metadata.xml:574(para) +msgid "Do not use: mandrivaent, or mandrivaES" +msgstr "" + +#: ./doc/image-guide/section_glance-image-metadata.xml:582(literal) +msgid "msdos" +msgstr "" + +#: ./doc/image-guide/section_glance-image-metadata.xml:584(para) +msgid "This is: Microsoft Disc Operating System" +msgstr "" + +#: ./doc/image-guide/section_glance-image-metadata.xml:587(para) +msgid "Do not use: ms-dos" +msgstr "" + +#: ./doc/image-guide/section_glance-image-metadata.xml:594(literal) +msgid "netbsd" +msgstr "" + +#: ./doc/image-guide/section_glance-image-metadata.xml:596(para) +msgid "This is: NetBSD" +msgstr "" + +#: ./doc/image-guide/section_glance-image-metadata.xml:599(para) +msgid "Do not use: NetBSD, or org.netbsd" +msgstr "" + +#: ./doc/image-guide/section_glance-image-metadata.xml:607(literal) +msgid "netware" +msgstr "" + +#: ./doc/image-guide/section_glance-image-metadata.xml:609(para) +msgid "This is: Novell NetWare" +msgstr "" + +#: ./doc/image-guide/section_glance-image-metadata.xml:612(para) +msgid "Do not use: novell, or NetWare" +msgstr "" + +#: ./doc/image-guide/section_glance-image-metadata.xml:620(literal) +msgid "openbsd" +msgstr "" + +#: ./doc/image-guide/section_glance-image-metadata.xml:622(para) +msgid "This is: OpenBSD" +msgstr "" + +#: ./doc/image-guide/section_glance-image-metadata.xml:625(para) +msgid "Do not use: OpenBSD, or org.openbsd" +msgstr "" + +#: ./doc/image-guide/section_glance-image-metadata.xml:633(literal) +msgid "opensolaris" +msgstr "" + +#: ./doc/image-guide/section_glance-image-metadata.xml:635(para) +msgid "Do not use: OpenSolaris,or org.opensolaris" +msgstr "" + +#: ./doc/image-guide/section_glance-image-metadata.xml:643(literal) +msgid "opensuse" +msgstr "" + +#: ./doc/image-guide/section_glance-image-metadata.xml:645(para) +msgid "This is: openSUSE" +msgstr "" + +#: ./doc/image-guide/section_glance-image-metadata.xml:648(para) +msgid "Do not use: suse, SuSE, or org.opensuse" +msgstr "" + +#: ./doc/image-guide/section_glance-image-metadata.xml:657(literal) +msgid "rhel" +msgstr "" + +#: ./doc/image-guide/section_glance-image-metadata.xml:659(para) +msgid "This is: Red Hat Enterprise Linux" +msgstr "" + +#: ./doc/image-guide/section_glance-image-metadata.xml:662(para) +msgid "Do not use: redhat, RedHat, or com.redhat" +msgstr "" + +#: ./doc/image-guide/section_glance-image-metadata.xml:671(literal) +msgid "sled" +msgstr "" + +#: ./doc/image-guide/section_glance-image-metadata.xml:673(para) +msgid "This is: SUSE Linux Enterprise Desktop" +msgstr "" + +#: ./doc/image-guide/section_glance-image-metadata.xml:676(para) +msgid "Do not use: com.suse" +msgstr "" + +#: ./doc/image-guide/section_glance-image-metadata.xml:683(literal) +msgid "ubuntu" +msgstr "" + +#: ./doc/image-guide/section_glance-image-metadata.xml:685(para) +msgid "This is: Ubuntu" +msgstr "" + +#: ./doc/image-guide/section_glance-image-metadata.xml:688(para) +msgid "Do not use: Ubuntu, com.ubuntu, org.ubuntu, or canonical" +msgstr "" + +#: ./doc/image-guide/section_glance-image-metadata.xml:698(literal) +msgid "windows" +msgstr "" + +#: ./doc/image-guide/section_glance-image-metadata.xml:700(para) +msgid "This is: Microsoft Windows" +msgstr "" + +#: ./doc/image-guide/section_glance-image-metadata.xml:703(para) +msgid "Do not use: com.microsoft.server, or windoze" +msgstr "" + +#: ./doc/image-guide/section_glance-image-metadata.xml:453(para) +msgid "The value of this property is the common name of the operating system distribution in all-lowercase. For this purpose, we use the same data vocabulary as the libosinfo project. Following are the recognized values for this property. In the interest of interoperability, please use only a recognized value for this field. The deprecated values are listed to assist you in searching for the recognized value. Allowed values are: " +msgstr "" + +#: ./doc/image-guide/ch_converting.xml:4(title) +msgid "Converting between image formats" +msgstr "" + +#: ./doc/image-guide/ch_converting.xml:5(para) +msgid "Converting images from one format to another is generally straightforward." +msgstr "" + +#: ./doc/image-guide/ch_converting.xml:7(title) +msgid "qemu-img convert: raw, qcow2, VDI, VMDK" +msgstr "" + +#: ./doc/image-guide/ch_converting.xml:8(para) +msgid "The command can do conversion between multiple formats, including raw, qcow2, VDI (VirtualBox), VMDK (VMWare) and VHD (Hyper-V)." +msgstr "" + +#: ./doc/image-guide/ch_converting.xml:12(caption) +msgid "qemu-img format strings" +msgstr "" + +#: ./doc/image-guide/ch_converting.xml:16(th) +msgid "Image format" +msgstr "" + +#: ./doc/image-guide/ch_converting.xml:17(th) +msgid "Argument to qemu-img" +msgstr "" + +#: ./doc/image-guide/ch_converting.xml:22(td) ./doc/image-guide/ch_converting.xml:23(literal) +msgid "raw" +msgstr "" + +#: ./doc/image-guide/ch_converting.xml:30(td) +msgid "VDI (VirtualBox)" +msgstr "" + +#: ./doc/image-guide/ch_converting.xml:31(literal) +msgid "vdi" +msgstr "" + +#: ./doc/image-guide/ch_converting.xml:34(td) +msgid "VMDK (VMWare)" +msgstr "" + +#: ./doc/image-guide/ch_converting.xml:35(literal) +msgid "vmdk" +msgstr "" + +#: ./doc/image-guide/ch_converting.xml:38(td) +msgid "VHD (Hyper-V)" +msgstr "" + +#: ./doc/image-guide/ch_converting.xml:39(literal) +msgid "vpc" +msgstr "" + +#: ./doc/image-guide/ch_converting.xml:43(para) +msgid "This example will convert a raw image file named centos63.dsk to a qcow2 image file." +msgstr "" + +#: ./doc/image-guide/ch_converting.xml:47(para) +msgid "To convert from vmdk to raw, you would do: " +msgstr "" + +#: ./doc/image-guide/ch_converting.xml:51(para) +msgid "The -f format flag is optional. If omitted, qemu-img will try to infer the image format." +msgstr "" + +#: ./doc/image-guide/ch_converting.xml:57(title) +msgid "VBoxManage: VDI (VirtualBox) to raw" +msgstr "" + +#: ./doc/image-guide/ch_converting.xml:58(para) +msgid "If you've created a VDI image using VirtualBox, you can convert it to raw format using the command-line tool that ships with VirtualBox. On Mac OS X, VirtualBox stores images by default in the ~/VirtualBox VMs/ directory. The following example creates a raw image in the current directory from a VirtualBox VDI image." +msgstr "" + +#: ./doc/image-guide/ch_obtaining_images.xml:6(title) +msgid "Get images" +msgstr "" + +#: ./doc/image-guide/ch_obtaining_images.xml:8(para) +msgid "The simplest way to obtain a virtual machine image that works with OpenStack is to download one that someone else has already created." +msgstr "" + +#: ./doc/image-guide/ch_obtaining_images.xml:11(title) +msgid "CirrOS (test) images" +msgstr "" + +#: ./doc/image-guide/ch_obtaining_images.xml:12(para) +msgid "CirrOS is a minimal Linux distribution that was designed for use as a test image on clouds such as OpenStack Compute. You can download a CirrOS image in various formats from the CirrOS Launchpad download page." +msgstr "" + +#: ./doc/image-guide/ch_obtaining_images.xml:21(para) +msgid "In a CirrOS image, the login account is cirros. The password is cubswin:)" +msgstr "" + +#: ./doc/image-guide/ch_obtaining_images.xml:16(para) +msgid "If your deployment uses QEMU or KVM, we recommend using the images in qcow2 format. The most recent 64-bit qcow2 image as of this writing is cirros-0.3.1-x86_64-disk.img" +msgstr "" + +#: ./doc/image-guide/ch_obtaining_images.xml:27(title) +msgid "Official Ubuntu images" +msgstr "" + +#: ./doc/image-guide/ch_obtaining_images.xml:28(para) +msgid "Canonical maintains an official set of Ubuntu-based images." +msgstr "" + +#: ./doc/image-guide/ch_obtaining_images.xml:30(para) +msgid "Images are arranged by Ubuntu release, and by image release date, with \"current\" being the most recent. For example, the page that contains the most recently built image for Ubuntu 12.04 \"Precise Pangolin\" is http://cloud-images.ubuntu.com/precise/current/. Scroll to the bottom of the page for links to images that can be downloaded directly." +msgstr "" + +#: ./doc/image-guide/ch_obtaining_images.xml:40(para) +msgid "In an Ubuntu cloud image, the login account is ubuntu." +msgstr "" + +#: ./doc/image-guide/ch_obtaining_images.xml:36(para) +msgid "If your deployment uses QEMU or KVM, we recommend using the images in qcow2 format. The most recent version of the 64-bit QCOW2 image for Ubuntu 12.04 is precise-server-cloudimg-amd64-disk1.img." +msgstr "" + +#: ./doc/image-guide/ch_obtaining_images.xml:45(title) +msgid "Official Red Hat Enterprise Linux images" +msgstr "" + +#: ./doc/image-guide/ch_obtaining_images.xml:46(para) +msgid "Red Hat maintains an official Red Hat Enterprise Linux 6 cloud image. A valid Red Hat Enterprise Linux 6 subscription is required to download the KVM Guest Image." +msgstr "" + +#: ./doc/image-guide/ch_obtaining_images.xml:53(para) +msgid "A boot.iso image is also available. This is the same as the boot.iso file provided on the Red Hat Enterprise Linux installation DVD. It is a minimal image suitable for kickstarting operating system installation over a network." +msgstr "" + +#: ./doc/image-guide/ch_obtaining_images.xml:63(title) +msgid "Official Fedora images" +msgstr "" + +#: ./doc/image-guide/ch_obtaining_images.xml:64(para) +msgid "The Fedora project maintains a list of official cloud images at . The images include the cloud-init utility to support key and user data injection. The default user name is fedora." +msgstr "" + +#: ./doc/image-guide/ch_obtaining_images.xml:72(title) +msgid "Official openSUSE and SLES images" +msgstr "" + +#: ./doc/image-guide/ch_obtaining_images.xml:73(para) +msgid "SUSE does not provide openSUSE or SUSE Linux Enterprise Server (SLES) images for direct download. Instead, they provide a web-based tool called SUSE Studio that you can use to build openSUSE and SLES images." +msgstr "" + +#: ./doc/image-guide/ch_obtaining_images.xml:79(para) +msgid "For example, Christian Berendt used openSUSE to create a test openSUSE 12.3 image." +msgstr "" + +#: ./doc/image-guide/ch_obtaining_images.xml:84(title) +msgid "Official images from other Linux distributions" +msgstr "" + +#: ./doc/image-guide/ch_obtaining_images.xml:85(para) +msgid "As of this writing, we are not aware of other distributions that provide images for download." +msgstr "" + +#: ./doc/image-guide/ch_obtaining_images.xml:88(title) +msgid "Rackspace Cloud Builders (multiple distros) images" +msgstr "" + +#: ./doc/image-guide/ch_obtaining_images.xml:90(para) +msgid "Rackspace Cloud Builders maintains a list of pre-built images from various distributions (Red Hat, CentOS, Fedora, Ubuntu). Links to these images can be found at rackerjoe/oz-image-build on Github." +msgstr "" + +#: ./doc/image-guide/ch_obtaining_images.xml:96(title) +msgid "Microsoft Windows images" +msgstr "" + +#: ./doc/image-guide/ch_obtaining_images.xml:97(para) +msgid "Cloudbase Solutions hosts an OpenStack Windows Server 2012 Standard Evaluation image that runs on Hyper-V, KVM, and XenServer/XCP." +msgstr "" + +#. Put one translator per line, in the form of NAME , YEAR1, YEAR2 +#: ./doc/image-guide/ch_obtaining_images.xml:0(None) +msgid "translator-credits" +msgstr "" + diff --git a/doc/install-guide/locale/he_IL.po b/doc/install-guide/locale/he_IL.po new file mode 100644 index 0000000000..2cd3249f2b --- /dev/null +++ b/doc/install-guide/locale/he_IL.po @@ -0,0 +1,8775 @@ +# +# Translators: +msgid "" +msgstr "" +"Project-Id-Version: OpenStack Manuals\n" +"POT-Creation-Date: 2014-01-30 06:24+0000\n" +"PO-Revision-Date: 2014-01-28 20:09+0000\n" +"Last-Translator: openstackjenkins \n" +"Language-Team: Hebrew (Israel) (http://www.transifex.com/projects/p/openstack/language/he_IL/)\n" +"MIME-Version: 1.0\n" +"Content-Type: text/plain; charset=UTF-8\n" +"Content-Transfer-Encoding: 8bit\n" +"Language: he_IL\n" +"Plural-Forms: nplurals=2; plural=(n != 1);\n" + +#: ./doc/install-guide/section_keystone-users.xml5(title) +msgid "Define users, tenants, and roles" +msgstr "" + +#: ./doc/install-guide/section_keystone-users.xml7(para) +msgid "" +"After you install the Identity Service, set up users, tenants, and roles to authenticate against. " +"These are used to allow access to services and endpoints, described in the next section." +msgstr "" + +#: ./doc/install-guide/section_keystone-users.xml24(replaceable) +#: ./doc/install-guide/section_keystone-users.xml27(replaceable) +msgid "FCAF3E..." +msgstr "" + +#: ./doc/install-guide/section_keystone-users.xml14(para) +msgid "" +"Typically, you would indicate a user and password to authenticate with the " +"Identity Service. At this point, however, we have not created any users, so " +"we have to use the authorization token created in the previous section. You " +"can pass this with the option to the " +" command or set the OS_SERVICE_TOKEN " +"environment variable. We'll set OS_SERVICE_TOKEN, as well as " +"OS_SERVICE_ENDPOINT to specify where the Identity Service is " +"running. Replace with your authorization token." +msgstr "" + +#: ./doc/install-guide/section_keystone-users.xml30(para) +msgid "" +"First, create a tenant for an administrative user and a tenant for other " +"OpenStack services to use." +msgstr "" + +#: ./doc/install-guide/section_keystone-users.xml36(para) +msgid "" +"Next, create an administrative user called admin. Choose " +"a password for the admin user and specify an email " +"address for the account." +msgstr "" + +#: ./doc/install-guide/section_keystone-users.xml40(replaceable) +#: ./doc/install-guide/section_keystone-verify.xml25(replaceable) +#: ./doc/install-guide/section_keystone-verify.xml35(replaceable) +#: ./doc/install-guide/section_keystone-verify.xml49(replaceable) +#: ./doc/install-guide/section_neutron-per-tenant-routers-with-private-networks.xml408(replaceable) +#: ./doc/install-guide/section_neutron-provider-router-with-private_networks.xml376(replaceable) +#: ./doc/install-guide/section_neutron-single-flat.xml483(replaceable) +msgid "ADMIN_PASS" +msgstr "" + +#: ./doc/install-guide/section_keystone-users.xml41(replaceable) +msgid "admin@example.com" +msgstr "" + +#: ./doc/install-guide/section_keystone-users.xml43(para) +msgid "" +"Create a role for administrative tasks called admin. Any " +"roles you create should map to roles specified in the " +"policy.json files of the various OpenStack services. " +"The default policy files use the admin role to allow " +"access to most services." +msgstr "" + +#: ./doc/install-guide/section_keystone-users.xml51(para) +msgid "" +"Finally, you have to add roles to users. Users always log in with a tenant, " +"and roles are assigned to users within tenants. Add the " +"admin role to the admin user when " +"logging in with the admin tenant." +msgstr "" + +#. When image changes, this message will be marked fuzzy or untranslated for +#. you. +#. It doesn't matter what you translate it to: it's not used at all. +#: ./doc/install-guide/section_debconf-api-endpoints.xml29(None) +msgid "" +"@@image: 'figures/debconf-screenshots/api-endpoint_1_register_endpoint.png';" +" md5=d534be231be4f725820a1050fbf44231" +msgstr "" + +#. When image changes, this message will be marked fuzzy or untranslated for +#. you. +#. It doesn't matter what you translate it to: it's not used at all. +#: ./doc/install-guide/section_debconf-api-endpoints.xml40(None) +msgid "" +"@@image: 'figures/debconf-screenshots/api-" +"endpoint_2_keystone_server_ip.png'; md5=d2c5a5b82dd433fcf9cde6f5ac34c30e" +msgstr "" + +#. When image changes, this message will be marked fuzzy or untranslated for +#. you. +#. It doesn't matter what you translate it to: it's not used at all. +#: ./doc/install-guide/section_debconf-api-endpoints.xml54(None) +msgid "" +"@@image: 'figures/debconf-screenshots/api-" +"endpoint_3_keystone_authtoken.png'; md5=1f3b05ebe671f64d672ac70d246e4f39" +msgstr "" + +#. When image changes, this message will be marked fuzzy or untranslated for +#. you. +#. It doesn't matter what you translate it to: it's not used at all. +#: ./doc/install-guide/section_debconf-api-endpoints.xml69(None) +msgid "" +"@@image: 'figures/debconf-screenshots/api-" +"endpoint_4_service_endpoint_ip_address.png'; " +"md5=6853f0ae2ef8d5fddb22c466d465de15" +msgstr "" + +#. When image changes, this message will be marked fuzzy or untranslated for +#. you. +#. It doesn't matter what you translate it to: it's not used at all. +#: ./doc/install-guide/section_debconf-api-endpoints.xml81(None) +msgid "" +"@@image: 'figures/debconf-screenshots/api-endpoint_5_region_name.png'; " +"md5=a6bce0acf5a1cb85f161290f0cf30733" +msgstr "" + +#: ./doc/install-guide/section_debconf-api-endpoints.xml6(title) +msgid "Register API endpoints" +msgstr "" + +#: ./doc/install-guide/section_debconf-api-endpoints.xml7(para) +msgid "" +"All Debian packages for API services, except the heat-api" +" package, register the service in the Identity Service catalog. This feature" +" is helpful because API endpoints are difficult to remember." +msgstr "" + +#: ./doc/install-guide/section_debconf-api-endpoints.xml12(para) +msgid "" +"The heat-common package and not the heat-" +"api package configures the Orchestration service." +msgstr "" + +#: ./doc/install-guide/section_debconf-api-endpoints.xml16(para) +msgid "" +"When you install a package for an API service, you are prompted to register " +"that service. However, after you install or upgrade the package for an API " +"service, Debian immediately removes your response to this prompt from the " +"debconf database. Consequently, you are prompted to re-" +"register the service with the Identity Service. If you already registered " +"the API service, respond no when you upgrade." +msgstr "" + +#: ./doc/install-guide/section_debconf-api-endpoints.xml33(para) +msgid "This screen registers packages in the Identity Service catalog:" +msgstr "" + +#: ./doc/install-guide/section_debconf-api-endpoints.xml44(para) +msgid "" +"You are prompted for the Identity Service admin_token " +"value. The Identity Service uses this value to register the API service. " +"When you set up the keystone package, this value is " +"configured automatically." +msgstr "" + +#: ./doc/install-guide/section_debconf-api-endpoints.xml58(para) +msgid "" +"This screen configures the IP addresses for the service. The configuration " +"script automatically detects the IP address used by the interface that is " +"connected to the default route (/sbin/route and " +"/sbin/ip)." +msgstr "" + +#: ./doc/install-guide/section_debconf-api-endpoints.xml62(para) +msgid "" +"Unless you have a unique set up for your network, press " +"ENTER." +msgstr "" + +#: ./doc/install-guide/section_debconf-api-endpoints.xml73(para) +msgid "" +"This screen configures the region name for the service. For example, us-east-coast or europe-paris." +msgstr "" + +#: ./doc/install-guide/ch_glance.xml6(title) +msgid "Configure the Image Service" +msgstr "" + +#: ./doc/install-guide/ch_glance.xml7(para) +msgid "" +"The OpenStack Image Service enables users to discover, register, and " +"retrieve virtual machine images. Also known as the glance project, the Image" +" Service offers a REST API that enables you to query virtual machine image " +"metadata and retrieve an actual image. Virtual machine images made available" +" through the Image Service can be stored in a variety of locations from " +"simple file systems to object-storage systems like OpenStack Object Storage." +msgstr "" + +#: ./doc/install-guide/ch_glance.xml16(para) +msgid "" +"For simplicity this guide configures the Image Service to use the " +"file backend. This means that images uploaded to the " +"Image Service will be stored in a directory on the same system that hosts " +"the service. By default this directory is " +"/var/lib/glance/images/." +msgstr "" + +#: ./doc/install-guide/ch_glance.xml23(para) +msgid "" +"Ensure that the system has sufficient space available under this directory " +"to store virtual machine images and snapshots before proceeding. At an " +"absolute minimum several gigabytes of space should be available for use by " +"the Image Service in a proof of concept deployment." +msgstr "" + +#: ./doc/install-guide/ch_cinder.xml6(title) +msgid "Add the Block Storage Service" +msgstr "" + +#: ./doc/install-guide/ch_cinder.xml7(para) +msgid "" +"The OpenStack Block Storage Service works through the interaction of a " +"series of daemon processes named cinder-* that reside persistently on the host " +"machine or machines. You can run the binaries from a single node or across " +"multiple nodes. You can also run them on the same node as other OpenStack " +"services. The following sections introduce Block Storage Service components " +"and concepts and show you how to configure and install the Block Storage " +"Service." +msgstr "" + +#: ./doc/install-guide/section_nova-kvm.xml5(title) +msgid "Enable KVM on the Compute node" +msgstr "" + +#: ./doc/install-guide/section_nova-kvm.xml7(para) +msgid "" +"OpenStack Compute requires hardware virtualization support and certain " +"kernel modules. Use the following procedure to determine whether your system" +" has this support and the correct kernel modules and to enable KVM. In many " +"cases, your distribution completes this installation and you do not need to " +"perform any additional action." +msgstr "" + +#: ./doc/install-guide/section_glance-verify.xml5(title) +msgid "Verify the Image Service installation" +msgstr "" + +#: ./doc/install-guide/section_glance-verify.xml6(para) +msgid "" +"To test the Image Service installation, download at least one virtual " +"machine image that is known to work with OpenStack. For example, CirrOS is a" +" small test image that is often used for testing OpenStack deployments " +"(CirrOS downloads). " +"This walk through uses the 64-bit CirrOS QCOW2 image." +msgstr "" + +#: ./doc/install-guide/section_glance-verify.xml13(para) +msgid "" +"For more information about how to download and build images, see OpenStack Virtual Machine Image " +"Guide. For information about how to manage images, see " +"the OpenStack User " +"Guide." +msgstr "" + +#: ./doc/install-guide/section_glance-verify.xml24(para) +msgid "" +"Download the image into a dedicated directory using or " +":" +msgstr "" + +#: ./doc/install-guide/section_glance-verify.xml32(para) +msgid "Upload the image to the Image Service:" +msgstr "" + +#: ./doc/install-guide/section_glance-verify.xml33(replaceable) +#: ./doc/install-guide/section_glance-verify.xml38(replaceable) +msgid "imageLabel" +msgstr "" + +#: ./doc/install-guide/section_glance-verify.xml33(replaceable) +#: ./doc/install-guide/section_glance-verify.xml45(replaceable) +msgid "fileFormat" +msgstr "" + +#: ./doc/install-guide/section_glance-verify.xml34(replaceable) +#: ./doc/install-guide/section_glance-verify.xml65(replaceable) +msgid "containerFormat" +msgstr "" + +#: ./doc/install-guide/section_glance-verify.xml34(replaceable) +#: ./doc/install-guide/section_glance-verify.xml86(replaceable) +msgid "accessValue" +msgstr "" + +#: ./doc/install-guide/section_glance-verify.xml34(replaceable) +#: ./doc/install-guide/section_glance-verify.xml101(replaceable) +msgid "imageFile" +msgstr "" + +#: ./doc/install-guide/section_glance-verify.xml35(para) +msgid "Where:" +msgstr "" + +#: ./doc/install-guide/section_glance-verify.xml40(para) +msgid "Arbitrary label. The name by which users refer to the image." +msgstr "" + +#: ./doc/install-guide/section_glance-verify.xml47(para) +msgid "" +"Specifies the format of the image file. Valid formats include " +"qcow2, raw, vhd, " +"vmdk, vdi, iso, " +"aki, ari, and ami." +msgstr "" + +#: ./doc/install-guide/section_glance-verify.xml58(para) +msgid "" +"You can verify the format using the command: " +"" +msgstr "" + +#: ./doc/install-guide/section_glance-verify.xml67(para) +msgid "" +"Specifies the container format. Valid formats include: " +"bare, ovf, aki, " +"ari and ami." +msgstr "" + +#: ./doc/install-guide/section_glance-verify.xml73(para) +msgid "" +"Specify bare to indicate that the image file is not in a " +"file format that contains metadata about the virtual machine. Although this " +"field is currently required, it is not actually used by any of the OpenStack" +" services and has no effect on system behavior. Because the value is not " +"used anywhere, it safe to always specify bare as the " +"container format." +msgstr "" + +#: ./doc/install-guide/section_glance-verify.xml90(para) +msgid "true - All users can view and use the image." +msgstr "" + +#: ./doc/install-guide/section_glance-verify.xml94(para) +msgid "false - Only administrators can view and use the image." +msgstr "" + +#: ./doc/install-guide/section_glance-verify.xml88(para) +msgid "Specifies image access: " +msgstr "" + +#: ./doc/install-guide/section_glance-verify.xml103(para) +msgid "Specifies the name of your downloaded image file." +msgstr "" + +#: ./doc/install-guide/section_glance-verify.xml108(para) +msgid "For example:" +msgstr "" + +#: ./doc/install-guide/section_glance-verify.xml132(para) +msgid "" +"Because the returned image ID is generated dynamically, your deployment " +"generates a different ID than the one shown in this example." +msgstr "" + +#: ./doc/install-guide/section_glance-verify.xml138(para) +msgid "Confirm that the image was uploaded and display its attributes:" +msgstr "" + +#: ./doc/install-guide/ch_clients.xml6(title) +msgid "Install and configure the OpenStack clients" +msgstr "" + +#. When image changes, this message will be marked fuzzy or untranslated for +#. you. +#. It doesn't matter what you translate it to: it's not used at all. +#: ./doc/install-guide/section_debconf-keystone_authtoken.xml30(None) +msgid "" +"@@image: 'figures/debconf-" +"screenshots/service_keystone_authtoken_server_hostname.png'; " +"md5=aafd53894e1d960531d4901123952117" +msgstr "" + +#. When image changes, this message will be marked fuzzy or untranslated for +#. you. +#. It doesn't matter what you translate it to: it's not used at all. +#: ./doc/install-guide/section_debconf-keystone_authtoken.xml37(None) +msgid "" +"@@image: 'figures/debconf-" +"screenshots/service_keystone_authtoken_admin_tenant_name.png'; " +"md5=a935563e4fba9b00040e35cdcfffc732" +msgstr "" + +#. When image changes, this message will be marked fuzzy or untranslated for +#. you. +#. It doesn't matter what you translate it to: it's not used at all. +#: ./doc/install-guide/section_debconf-keystone_authtoken.xml44(None) +msgid "" +"@@image: 'figures/debconf-" +"screenshots/service_keystone_authtoken_tenant_admin_user.png'; " +"md5=fe3dc93c591b3e9783d4d05556efcf25" +msgstr "" + +#. When image changes, this message will be marked fuzzy or untranslated for +#. you. +#. It doesn't matter what you translate it to: it's not used at all. +#: ./doc/install-guide/section_debconf-keystone_authtoken.xml51(None) +msgid "" +"@@image: 'figures/debconf-" +"screenshots/service_keystone_authtoken_admin_password.png'; " +"md5=0c30c80315d5e636dbe93a938fc2822b" +msgstr "" + +#: ./doc/install-guide/section_debconf-keystone_authtoken.xml6(title) +msgid "Services and the [keystone_authtoken]" +msgstr "" + +#: ./doc/install-guide/section_debconf-keystone_authtoken.xml7(para) +msgid "" +"Because most OpenStack services must access the Identity Service, you must " +"configure the IP address of the keystone server to be able to " +"access it. You must also configure the admin_tenant_name, " +"admin_user, and admin_password options for each " +"service to work." +msgstr "" + +#: ./doc/install-guide/section_debconf-keystone_authtoken.xml13(para) +msgid "Generally, this section looks like this:" +msgstr "" + +#: ./doc/install-guide/section_debconf-keystone_authtoken.xml21(para) +msgid "" +"The debconf system helps users configure the auth_host, " +"admin_tenant_name, admin_user and " +"admin_password options." +msgstr "" + +#: ./doc/install-guide/section_debconf-keystone_authtoken.xml25(para) +msgid "The following screens show an example Image Service configuration:" +msgstr "" + +#: ./doc/install-guide/section_debconf-keystone_authtoken.xml55(para) +msgid "" +"This information is stored in the configuration file for each service. For " +"example:" +msgstr "" + +#: ./doc/install-guide/section_debconf-keystone_authtoken.xml63(para) +msgid "" +"The Debian OpenStack packages offer automation for this, so OpenStack users " +"do not have to manually edit the configuration files." +msgstr "" + +#: ./doc/install-guide/ch_swift.xml6(title) +msgid "Add Object Storage" +msgstr "" + +#: ./doc/install-guide/ch_swift.xml8(para) +msgid "" +"The OpenStack Object Storage services work together to provide object " +"storage and retrieval through a REST API. For this example architecture, you" +" must have already installed the Identity Service, also known as Keystone." +msgstr "" + +#: ./doc/install-guide/section_neutron-concepts.xml8(title) +msgid "Neutron concepts" +msgstr "" + +#: ./doc/install-guide/section_neutron-concepts.xml9(para) +msgid "" +"Like Nova Networking, Neutron manages software-defined networking for your " +"OpenStack installation. However, unlike Nova Networking, you can configure " +"Neutron for advanced virtual network topologies, such as per-tenant private " +"networks and more." +msgstr "" + +#: ./doc/install-guide/section_neutron-concepts.xml13(para) +msgid "" +"Neutron has the following object abstractions: networks, subnets, and " +"routers. Each has functionality that mimics its physical counterpart: " +"networks contain subnets, and routers route traffic between different subnet" +" and networks." +msgstr "" + +#: ./doc/install-guide/section_neutron-concepts.xml17(para) +msgid "" +"Any given Neutron set up has at least one external network. This network, " +"unlike the other networks, is not merely a virtually defined network. " +"Instead, it represents the view into a slice of the external network that is" +" accessible outside the OpenStack installation. IP addresses on the Neutron " +"external network are accessible by anybody physically on the outside " +"network. Because this network merely represents a slice of the outside " +"network, DHCP is disabled on this network." +msgstr "" + +#: ./doc/install-guide/section_neutron-concepts.xml25(para) +msgid "" +"In addition to external networks, any Neutron set up has one or more " +"internal networks. These software-defined networks connect directly to the " +"VMs. Only the VMs on any given internal network, or those on subnets " +"connected through interfaces to a similar router, can access VMs connected " +"to that network directly." +msgstr "" + +#: ./doc/install-guide/section_neutron-concepts.xml30(para) +msgid "" +"For the outside network to access VMs, and vice versa, routers between the " +"networks are needed. Each router has one gateway that is connected to a " +"network and many interfaces that are connected to subnets. Like a physical " +"router, subnets can access machines on other subnets that are connected to " +"the same router, and machines can access the outside network through the " +"gateway for the router." +msgstr "" + +#: ./doc/install-guide/section_neutron-concepts.xml37(para) +msgid "" +"Additionally, you can allocate IP addresses on an external networks to ports" +" on the internal network. Whenever something is connected to a subnet, that " +"connection is called a port. You can associate external network IP addresses" +" with ports to VMs. This way, entities on the outside network can access " +"VMs." +msgstr "" + +#: ./doc/install-guide/section_neutron-concepts.xml42(para) +msgid "" +"Neutron also supports security groups. " +"Security groups enable administrators to define firewall rules in groups. A " +"VM can belong to one or more security groups, and Neutron applies the rules " +"in those security groups to block or unblock ports, port ranges, or traffic " +"types for that VM." +msgstr "" + +#: ./doc/install-guide/section_neutron-concepts.xml48(para) +msgid "" +"Each plug-in that Neutron uses has its own concepts. While not vital to " +"operating Neutron, understanding these concepts can help you set up Neutron." +" All Neutron installations use a core plug-in and a security group plug-in " +"(or just the No-Op security group plug-in). Additionally, Firewall-" +"as-a-service (FWaaS) and Load-balancing-as-a-service (LBaaS) plug-ins are " +"available." +msgstr "" + +#: ./doc/install-guide/section_neutron-concepts.xml55(title) +msgid "Open vSwitch concepts" +msgstr "" + +#: ./doc/install-guide/section_neutron-concepts.xml56(para) +msgid "" +"The Open vSwitch plug-in is one of the most popular core plug-ins. Open " +"vSwitch configurations consists of bridges and ports. Ports represent " +"connections to other things, such as physical interfaces and patch cables. " +"Packets from any given port on a bridge are shared with all other ports on " +"that bridge. Bridges can be connected through Open vSwitch virtual patch " +"cables or through Linux virtual Ethernet cables (veth). " +"Additionally, bridges appear as network interfaces to Linux, so you can " +"assign IP addresses to them." +msgstr "" + +#: ./doc/install-guide/section_neutron-concepts.xml66(para) +msgid "" +"In Neutron, the integration bridge, called br-int, " +"connects directly to the VMs and associated services. The external bridge, " +"called br-ex, connects to the external network. Finally, " +"the VLAN configuration of the Open vSwitch plug-in uses bridges associated " +"with each physical network." +msgstr "" + +#: ./doc/install-guide/section_neutron-concepts.xml72(para) +msgid "" +"In addition to defining bridges, Open vSwitch has OpenFlow, which enables " +"you to define networking flow rules. Certain configurations use these rules " +"to transfer packets between VLANs." +msgstr "" + +#: ./doc/install-guide/section_neutron-concepts.xml76(para) +msgid "" +"Finally, some configurations of Open vSwitch use network namespaces that " +"enable Linux to group adapters into unique namespaces that are not visible " +"to other namespaces, which allows the same network node to manage multiple " +"Neutron routers." +msgstr "" + +#: ./doc/install-guide/section_neutron-concepts.xml81(para) +msgid "" +"With Open vSwitch, you can use two different technologies to create the " +"virtual networks: GRE or VLANs." +msgstr "" + +#: ./doc/install-guide/section_neutron-concepts.xml83(para) +msgid "" +"Generic Routing Encapsulation (GRE) is the technology used in many VPNs. It " +"wraps IP packets to create entirely new packets with different routing " +"information. When the new packet reaches its destination, it is unwrapped, " +"and the underlying packet is routed. To use GRE with Open vSwitch, Neutron " +"creates GRE tunnels. These tunnels are ports on a bridge and enable bridges " +"on different systems to act as though they were one bridge, which allows the" +" compute and network nodes to act as one for the purposes of routing." +msgstr "" + +#: ./doc/install-guide/section_neutron-concepts.xml92(para) +msgid "" +"Virtual LANs (VLANs), on the other hand, use a special modification to the " +"Ethernet header. They add a 4-byte VLAN tag that ranges from 1 to 4094 (the " +"0 tag is special, and the 4095 tag, made of all ones, is equivalent to an " +"untagged packet). Special NICs, switches, and routers know how to interpret " +"the VLAN tags, as does Open vSwitch. Packets tagged for one VLAN are only " +"shared with other devices configured to be on that VLAN, even through all " +"devices are on the same physical network." +msgstr "" + +#: ./doc/install-guide/section_neutron-concepts.xml101(para) +msgid "" +"The most common security group driver used with Open vSwitch is the Hybrid " +"IPTables/Open vSwitch plug-in. It uses a combination for IPTables and " +"OpenFlow rules. Use the IPTables tool to create firewalls and set up NATs on" +" Linux. This tool uses a complex rule system and chains of rules to " +"accommodate the complex rules required by Neutron security groups." +msgstr "" + +#: ./doc/install-guide/section_ceilometer-install.xml6(title) +msgid "Install the Telemetry service" +msgstr "" + +#: ./doc/install-guide/section_ceilometer-install.xml8(para) +msgid "" +"OpenStack Telemetry is an API service that provides a collector and a range " +"of disparate agents. Before you can install these agents on nodes such as " +"the compute node, you must use this procedure to install the core components" +" on the controller node." +msgstr "" + +#: ./doc/install-guide/section_ceilometer-install.xml14(para) +msgid "Install the Telemetry service on the controller node:" +msgstr "" + +#: ./doc/install-guide/section_ceilometer-install.xml21(para) +msgid "" +"Respond to the prompts for [keystone_authtoken] " +"settings, RabbitMQ " +"credentials and API " +"endpoint registration." +msgstr "" + +#: ./doc/install-guide/section_ceilometer-install.xml29(para) +msgid "" +"The Telemetry service uses a database to store information. Specify the " +"location of the database in the configuration file. The examples use a " +"MongoDB database on the controller node:" +msgstr "" + +#: ./doc/install-guide/section_ceilometer-install.xml37(para) +msgid "" +"By default MongoDB is configured to create several 1 GB files in the " +"/var/lib/mongodb/journal/ directory to support database" +" journaling." +msgstr "" + +#: ./doc/install-guide/section_ceilometer-install.xml42(para) +msgid "" +"If you need to minimize the space allocated to support database journaling " +"then set the configuration key to " +"true in the /etc/mongodb.conf " +"configuration file. This will reduce the size of each journaling file to 512" +" MB." +msgstr "" + +#: ./doc/install-guide/section_ceilometer-install.xml49(para) +msgid "" +"As the files are created the first time the MongoDB service starts you must " +"stop the service and remove the files for this change to take effect:" +msgstr "" + +#: ./doc/install-guide/section_ceilometer-install.xml59(para) +msgid "" +"For more information on the configuration key " +"refer to the MongoDB documentation at ." +msgstr "" + +#: ./doc/install-guide/section_ceilometer-install.xml64(para) +msgid "" +"For instructions detailing the steps to disable database journaling entirely" +" refer to ." +msgstr "" + +#: ./doc/install-guide/section_ceilometer-install.xml72(para) +msgid "" +"Configure MongoDB to make it listen on the controller public IP address. " +"Edit the /etc/mongodb.conf file and modify the " +"bind_ip key:" +msgstr "" + +#: ./doc/install-guide/section_ceilometer-install.xml78(para) +msgid "Restart the MongoDB service to apply the configuration change:" +msgstr "" + +#: ./doc/install-guide/section_ceilometer-install.xml82(para) +msgid "" +"Start the MongoDB server and configure it to start when the system boots:" +msgstr "" + +#: ./doc/install-guide/section_ceilometer-install.xml92(para) +msgid "Create the database and a ceilometer database user:" +msgstr "" + +#: ./doc/install-guide/section_ceilometer-install.xml94(replaceable) +#: ./doc/install-guide/section_ceilometer-install.xml104(replaceable) +#: ./doc/install-guide/section_ceilometer-install.xml111(replaceable) +#: ./doc/install-guide/section_ceilometer-install.xml138(replaceable) +#: ./doc/install-guide/section_ceilometer-install.xml141(replaceable) +#: ./doc/install-guide/section_ceilometer-install.xml171(replaceable) +#: ./doc/install-guide/section_ceilometer-install.xml213(replaceable) +#: ./doc/install-guide/section_ceilometer-install.xml214(replaceable) +#: ./doc/install-guide/section_ceilometer-install.xml215(replaceable) +#: ./doc/install-guide/section_nova-controller.xml55(replaceable) +#: ./doc/install-guide/section_nova-controller.xml69(replaceable) +#: ./doc/install-guide/section_nova-controller.xml154(replaceable) +#: ./doc/install-guide/section_nova-controller.xml194(replaceable) +#: ./doc/install-guide/section_nova-controller.xml197(replaceable) +#: ./doc/install-guide/section_nova-controller.xml217(replaceable) +#: ./doc/install-guide/section_nova-controller.xml218(replaceable) +#: ./doc/install-guide/section_nova-controller.xml219(replaceable) +#: ./doc/install-guide/section_keystone-services.xml47(replaceable) +#: ./doc/install-guide/section_keystone-services.xml48(replaceable) +#: ./doc/install-guide/section_keystone-services.xml49(replaceable) +#: ./doc/install-guide/section_neutron-per-tenant-routers-with-private-networks.xml181(replaceable) +#: ./doc/install-guide/section_neutron-per-tenant-routers-with-private-networks.xml186(replaceable) +#: ./doc/install-guide/section_neutron-per-tenant-routers-with-private-networks.xml194(replaceable) +#: ./doc/install-guide/section_neutron-per-tenant-routers-with-private-networks.xml199(replaceable) +#: ./doc/install-guide/section_neutron-per-tenant-routers-with-private-networks.xml271(replaceable) +#: ./doc/install-guide/section_neutron-per-tenant-routers-with-private-networks.xml276(replaceable) +#: ./doc/install-guide/section_neutron-per-tenant-routers-with-private-networks.xml326(replaceable) +#: ./doc/install-guide/section_neutron-per-tenant-routers-with-private-networks.xml410(replaceable) +#: ./doc/install-guide/section_neutron-provider-router-with-private_networks.xml116(replaceable) +#: ./doc/install-guide/section_neutron-provider-router-with-private_networks.xml177(replaceable) +#: ./doc/install-guide/section_neutron-provider-router-with-private_networks.xml181(replaceable) +#: ./doc/install-guide/section_neutron-provider-router-with-private_networks.xml185(replaceable) +#: ./doc/install-guide/section_neutron-provider-router-with-private_networks.xml191(replaceable) +#: ./doc/install-guide/section_neutron-provider-router-with-private_networks.xml222(replaceable) +#: ./doc/install-guide/section_neutron-provider-router-with-private_networks.xml226(replaceable) +#: ./doc/install-guide/section_neutron-provider-router-with-private_networks.xml234(replaceable) +#: ./doc/install-guide/section_neutron-provider-router-with-private_networks.xml321(replaceable) +#: ./doc/install-guide/section_neutron-provider-router-with-private_networks.xml325(replaceable) +#: ./doc/install-guide/section_neutron-provider-router-with-private_networks.xml329(replaceable) +#: ./doc/install-guide/section_neutron-provider-router-with-private_networks.xml335(replaceable) +#: ./doc/install-guide/section_neutron-provider-router-with-private_networks.xml377(replaceable) +#: ./doc/install-guide/section_ceilometer-glance.xml17(replaceable) +#: ./doc/install-guide/section_ceilometer-glance.xml23(replaceable) +#: ./doc/install-guide/section_neutron-single-flat.xml193(replaceable) +#: ./doc/install-guide/section_neutron-single-flat.xml212(replaceable) +#: ./doc/install-guide/section_neutron-single-flat.xml229(replaceable) +#: ./doc/install-guide/section_neutron-single-flat.xml234(replaceable) +#: ./doc/install-guide/section_neutron-single-flat.xml284(replaceable) +#: ./doc/install-guide/section_neutron-single-flat.xml287(replaceable) +#: ./doc/install-guide/section_neutron-single-flat.xml291(replaceable) +#: ./doc/install-guide/section_neutron-single-flat.xml301(replaceable) +#: ./doc/install-guide/section_neutron-single-flat.xml332(replaceable) +#: ./doc/install-guide/section_neutron-single-flat.xml337(replaceable) +#: ./doc/install-guide/section_neutron-single-flat.xml346(replaceable) +#: ./doc/install-guide/section_neutron-single-flat.xml365(replaceable) +#: ./doc/install-guide/section_neutron-single-flat.xml424(replaceable) +#: ./doc/install-guide/section_neutron-single-flat.xml449(replaceable) +#: ./doc/install-guide/section_neutron-single-flat.xml485(replaceable) +#: ./doc/install-guide/section_cinder-node.xml110(replaceable) +#: ./doc/install-guide/section_cinder-node.xml127(replaceable) +#: ./doc/install-guide/section_cinder-node.xml164(replaceable) +#: ./doc/install-guide/section_cinder-node.xml167(replaceable) +#: ./doc/install-guide/section_cinder-controller.xml47(replaceable) +#: ./doc/install-guide/section_cinder-controller.xml50(replaceable) +#: ./doc/install-guide/section_cinder-controller.xml89(replaceable) +#: ./doc/install-guide/section_cinder-controller.xml107(replaceable) +#: ./doc/install-guide/section_cinder-controller.xml142(replaceable) +#: ./doc/install-guide/section_cinder-controller.xml143(replaceable) +#: ./doc/install-guide/section_cinder-controller.xml144(replaceable) +#: ./doc/install-guide/section_cinder-controller.xml153(replaceable) +#: ./doc/install-guide/section_cinder-controller.xml154(replaceable) +#: ./doc/install-guide/section_cinder-controller.xml155(replaceable) +#: ./doc/install-guide/section_neutron-install.xml158(replaceable) +#: ./doc/install-guide/section_neutron-install.xml159(replaceable) +#: ./doc/install-guide/section_neutron-install.xml160(replaceable) +#: ./doc/install-guide/section_neutron-install.xml283(replaceable) +#: ./doc/install-guide/section_neutron-install.xml323(replaceable) +#: ./doc/install-guide/section_neutron-install.xml341(replaceable) +#: ./doc/install-guide/section_neutron-install.xml349(replaceable) +#: ./doc/install-guide/section_neutron-install.xml351(replaceable) +#: ./doc/install-guide/section_neutron-install.xml365(replaceable) +#: ./doc/install-guide/section_neutron-install.xml366(replaceable) +#: ./doc/install-guide/section_neutron-install.xml851(replaceable) +#: ./doc/install-guide/section_neutron-install.xml853(replaceable) +#: ./doc/install-guide/section_neutron-install.xml878(replaceable) +#: ./doc/install-guide/section_neutron-install.xml890(replaceable) +#: ./doc/install-guide/section_neutron-install.xml919(replaceable) +#: ./doc/install-guide/section_neutron-install.xml927(replaceable) +#: ./doc/install-guide/section_neutron-install.xml938(replaceable) +#: ./doc/install-guide/section_neutron-install.xml953(replaceable) +#: ./doc/install-guide/section_neutron-install.xml963(replaceable) +#: ./doc/install-guide/section_neutron-install.xml974(replaceable) +#: ./doc/install-guide/section_neutron-install.xml979(replaceable) +#: ./doc/install-guide/section_neutron-install.xml1080(replaceable) +#: ./doc/install-guide/section_neutron-install.xml1230(replaceable) +#: ./doc/install-guide/section_neutron-install.xml1245(replaceable) +#: ./doc/install-guide/section_neutron-install.xml1247(replaceable) +#: ./doc/install-guide/section_neutron-install.xml1274(replaceable) +#: ./doc/install-guide/section_neutron-install.xml1280(replaceable) +#: ./doc/install-guide/section_neutron-install.xml1281(replaceable) +#: ./doc/install-guide/section_neutron-install.xml1305(replaceable) +#: ./doc/install-guide/section_neutron-install.xml1329(replaceable) +#: ./doc/install-guide/section_neutron-install.xml1348(replaceable) +#: ./doc/install-guide/section_neutron-install.xml1372(replaceable) +#: ./doc/install-guide/section_neutron-install.xml1382(replaceable) +#: ./doc/install-guide/section_neutron-install.xml1393(replaceable) +#: ./doc/install-guide/section_neutron-install.xml1398(replaceable) +#: ./doc/install-guide/section_heat-install.xml116(replaceable) +#: ./doc/install-guide/section_heat-install.xml121(replaceable) +#: ./doc/install-guide/section_heat-install.xml122(replaceable) +#: ./doc/install-guide/section_heat-install.xml133(replaceable) +#: ./doc/install-guide/section_heat-install.xml134(replaceable) +#: ./doc/install-guide/section_heat-install.xml135(replaceable) +#: ./doc/install-guide/section_heat-install.xml140(replaceable) +#: ./doc/install-guide/section_heat-install.xml141(replaceable) +#: ./doc/install-guide/section_heat-install.xml142(replaceable) +#: ./doc/install-guide/section_ceilometer-nova.xml78(replaceable) +#: ./doc/install-guide/section_ceilometer-nova.xml84(replaceable) +#: ./doc/install-guide/section_ceilometer-nova.xml90(replaceable) +#: ./doc/install-guide/section_ceilometer-nova.xml106(replaceable) +#: ./doc/install-guide/section_ceilometer-nova.xml121(replaceable) +#: ./doc/install-guide/section_nova-compute.xml112(replaceable) +#: ./doc/install-guide/section_nova-compute.xml135(replaceable) +#: ./doc/install-guide/section_nova-compute.xml158(replaceable) +#: ./doc/install-guide/section_nova-compute.xml170(replaceable) +#: ./doc/install-guide/section_nova-compute.xml178(replaceable) +#: ./doc/install-guide/section_nova-compute.xml181(replaceable) +#: ./doc/install-guide/section_nova-compute.xml221(replaceable) +#: ./doc/install-guide/section_glance-install.xml57(replaceable) +#: ./doc/install-guide/section_glance-install.xml59(replaceable) +#: ./doc/install-guide/section_glance-install.xml70(replaceable) +#: ./doc/install-guide/section_glance-install.xml118(replaceable) +#: ./doc/install-guide/section_glance-install.xml120(replaceable) +#: ./doc/install-guide/section_glance-install.xml130(replaceable) +#: ./doc/install-guide/section_glance-install.xml132(replaceable) +#: ./doc/install-guide/section_glance-install.xml152(replaceable) +#: ./doc/install-guide/section_glance-install.xml153(replaceable) +#: ./doc/install-guide/section_glance-install.xml198(replaceable) +#: ./doc/install-guide/section_glance-install.xml199(replaceable) +#: ./doc/install-guide/section_glance-install.xml200(replaceable) +#: ./doc/install-guide/object-storage/section_object-storage-install-config-proxy-node.xml99(replaceable) +#: ./doc/install-guide/object-storage/section_object-storage-install.xml102(replaceable) +#: ./doc/install-guide/object-storage/section_object-storage-install.xml103(replaceable) +#: ./doc/install-guide/object-storage/section_object-storage-install.xml104(replaceable) +msgid "controller" +msgstr "" + +#: ./doc/install-guide/section_ceilometer-install.xml97(replaceable) +#: ./doc/install-guide/section_ceilometer-install.xml104(replaceable) +#: ./doc/install-guide/section_ceilometer-install.xml111(replaceable) +msgid "CEILOMETER_DBPASS" +msgstr "" + +#: ./doc/install-guide/section_ceilometer-install.xml102(para) +msgid "Configure the Telemetry service to use the database:" +msgstr "" + +#: ./doc/install-guide/section_ceilometer-install.xml105(para) +msgid "" +"Edit the /etc/ceilometer/ceilometer.conf file and " +"change the [database] section:" +msgstr "" + +#: ./doc/install-guide/section_ceilometer-install.xml115(para) +msgid "" +"You must define an secret key that is used as a shared secret among " +"Telemetry service nodes. Use to generate a random token and" +" store it in the configuration file:" +msgstr "" + +#: ./doc/install-guide/section_ceilometer-install.xml122(para) +msgid "For SUSE Linux Enterprise, run the following command:" +msgstr "" + +#: ./doc/install-guide/section_ceilometer-install.xml126(para) +msgid "" +"Edit the /etc/ceilometer/ceilometer.conf file and " +"change the [publisher_rpc] section. Replace " +"CEILOMETER_TOKEN with the results of the " +"openssl command:" +msgstr "" + +#: ./doc/install-guide/section_ceilometer-install.xml133(replaceable) +#: ./doc/install-guide/section_ceilometer-nova.xml69(replaceable) +msgid "CEILOMETER_TOKEN" +msgstr "" + +#: ./doc/install-guide/section_ceilometer-install.xml137(para) +#: ./doc/install-guide/section_ceilometer-nova.xml73(para) +msgid "Configure the RabbitMQ access:" +msgstr "" + +#: ./doc/install-guide/section_ceilometer-install.xml139(replaceable) +#: ./doc/install-guide/section_ceilometer-install.xml142(replaceable) +#: ./doc/install-guide/section_nova-controller.xml78(replaceable) +#: ./doc/install-guide/section_nova-controller.xml86(replaceable) +#: ./doc/install-guide/section_neutron-per-tenant-routers-with-private-networks.xml182(replaceable) +#: ./doc/install-guide/section_neutron-per-tenant-routers-with-private-networks.xml195(replaceable) +#: ./doc/install-guide/section_neutron-per-tenant-routers-with-private-networks.xml272(replaceable) +#: ./doc/install-guide/section_neutron-per-tenant-routers-with-private-networks.xml327(replaceable) +#: ./doc/install-guide/section_neutron-provider-router-with-private_networks.xml113(replaceable) +#: ./doc/install-guide/section_neutron-provider-router-with-private_networks.xml178(replaceable) +#: ./doc/install-guide/section_neutron-provider-router-with-private_networks.xml189(replaceable) +#: ./doc/install-guide/section_neutron-provider-router-with-private_networks.xml322(replaceable) +#: ./doc/install-guide/section_neutron-provider-router-with-private_networks.xml333(replaceable) +#: ./doc/install-guide/section_ceilometer-glance.xml18(replaceable) +#: ./doc/install-guide/section_ceilometer-glance.xml24(replaceable) +#: ./doc/install-guide/section_neutron-single-flat.xml207(replaceable) +#: ./doc/install-guide/section_neutron-single-flat.xml230(replaceable) +#: ./doc/install-guide/section_neutron-single-flat.xml333(replaceable) +#: ./doc/install-guide/section_neutron-single-flat.xml360(replaceable) +#: ./doc/install-guide/section_neutron-single-flat.xml425(replaceable) +#: ./doc/install-guide/section_neutron-single-flat.xml444(replaceable) +#: ./doc/install-guide/ch_basics.xml640(replaceable) +#: ./doc/install-guide/section_cinder-node.xml130(replaceable) +#: ./doc/install-guide/section_cinder-node.xml150(replaceable) +#: ./doc/install-guide/section_cinder-controller.xml110(replaceable) +#: ./doc/install-guide/section_cinder-controller.xml130(replaceable) +#: ./doc/install-guide/section_neutron-install.xml307(replaceable) +#: ./doc/install-guide/section_neutron-install.xml316(replaceable) +#: ./doc/install-guide/section_neutron-install.xml871(replaceable) +#: ./doc/install-guide/section_neutron-install.xml901(replaceable) +#: ./doc/install-guide/section_neutron-install.xml1322(replaceable) +#: ./doc/install-guide/section_neutron-install.xml1349(replaceable) +#: ./doc/install-guide/section_heat-install.xml93(replaceable) +#: ./doc/install-guide/section_heat-install.xml96(replaceable) +#: ./doc/install-guide/section_ceilometer-nova.xml75(replaceable) +#: ./doc/install-guide/section_ceilometer-nova.xml79(replaceable) +#: ./doc/install-guide/section_nova-compute.xml142(replaceable) +#: ./doc/install-guide/section_nova-compute.xml148(replaceable) +msgid "RABBIT_PASS" +msgstr "" + +#: ./doc/install-guide/section_ceilometer-install.xml140(para) +#: ./doc/install-guide/section_ceilometer-install.xml153(para) +#: ./doc/install-guide/section_ceilometer-nova.xml76(para) +#: ./doc/install-guide/section_ceilometer-nova.xml129(para) +msgid "" +"Edit the /etc/ceilometer/ceilometer.conf file and " +"update the [DEFAULT] section:" +msgstr "" + +#: ./doc/install-guide/section_ceilometer-install.xml146(para) +msgid "Configure collector dispatcher:" +msgstr "" + +#: ./doc/install-guide/section_ceilometer-install.xml152(para) +#: ./doc/install-guide/section_ceilometer-nova.xml128(para) +msgid "Configure the log directory." +msgstr "" + +#: ./doc/install-guide/section_ceilometer-install.xml160(para) +msgid "" +"Create a ceilometer user that the Telemetry service uses " +"to authenticate with the Identity Service. Use the " +"service tenant and give the user the " +"admin role:" +msgstr "" + +#: ./doc/install-guide/section_ceilometer-install.xml164(replaceable) +#: ./doc/install-guide/section_ceilometer-install.xml179(replaceable) +#: ./doc/install-guide/section_ceilometer-install.xml185(replaceable) +#: ./doc/install-guide/section_ceilometer-install.xml196(replaceable) +#: ./doc/install-guide/section_ceilometer-install.xml202(replaceable) +#: ./doc/install-guide/section_ceilometer-nova.xml98(replaceable) +#: ./doc/install-guide/section_ceilometer-nova.xml104(replaceable) +#: ./doc/install-guide/section_ceilometer-nova.xml117(replaceable) +#: ./doc/install-guide/section_ceilometer-nova.xml124(replaceable) +msgid "CEILOMETER_PASS" +msgstr "" + +#: ./doc/install-guide/section_ceilometer-install.xml164(replaceable) +msgid "ceilometer@example.com" +msgstr "" + +#: ./doc/install-guide/section_ceilometer-install.xml168(para) +msgid "" +"Add the credentials to the configuration files for the Telemetry service:" +msgstr "" + +#: ./doc/install-guide/section_ceilometer-install.xml186(para) +#: ./doc/install-guide/section_ceilometer-nova.xml107(para) +msgid "" +"Edit the /etc/ceilometer/ceilometer.conf file and " +"change the [keystone_authtoken] section:" +msgstr "" + +#: ./doc/install-guide/section_ceilometer-install.xml197(para) +#: ./doc/install-guide/section_ceilometer-nova.xml118(para) +msgid "Also set the [service_credentials] section:" +msgstr "" + +#: ./doc/install-guide/section_ceilometer-install.xml205(para) +msgid "" +"Register the Telemetry service with the Identity Service so that other " +"OpenStack services can locate it. Use the command to " +"register the service and specify the endpoint:" +msgstr "" + +#: ./doc/install-guide/section_ceilometer-install.xml218(para) +msgid "Restart the services with their new settings:" +msgstr "" + +#: ./doc/install-guide/section_ceilometer-install.xml224(para) +msgid "" +"Start the openstack-ceilometer-" +"api, openstack-ceilometer-agent-centralopenstack-ceilometer-" +"central and openstack-ceilometer-" +"collector services and configure them to start when the system " +"boots:" +msgstr "" + +#: ./doc/install-guide/section_ceilometer-verify.xml5(title) +msgid "Verify the Telemetry Service installation" +msgstr "" + +#: ./doc/install-guide/section_ceilometer-verify.xml6(para) +msgid "" +"To test the Telemetry Service installation, download an image from the Image" +" Service, and use the Telemetry Service to display usage statistics." +msgstr "" + +#: ./doc/install-guide/section_ceilometer-verify.xml11(para) +msgid "" +"Use the ceilometer meter-list command to test the access " +"to the Telemetry Service:" +msgstr "" + +#: ./doc/install-guide/section_ceilometer-verify.xml22(para) +msgid "Download an image from the Image Service:" +msgstr "" + +#: ./doc/install-guide/section_ceilometer-verify.xml26(para) +msgid "" +"Call the ceilometer meter-list command again to validate " +"that the download has been detected and stored by the Telemetry Service:" +msgstr "" + +#: ./doc/install-guide/section_ceilometer-verify.xml40(para) +msgid "You can now get usage statistics for the various meters:" +msgstr "" + +#: ./doc/install-guide/section_nova-controller.xml5(title) +msgid "Install Compute controller services" +msgstr "" + +#: ./doc/install-guide/section_nova-controller.xml6(para) +msgid "" +"Compute is a collection of services that enable you to launch virtual " +"machine instances. You can configure these services to run on separate nodes" +" or the same node. In this guide, most services run on the controller node " +"and the service that launches virtual machines runs on a dedicated compute " +"node. This section shows you how to install and configure these services on " +"the controller node." +msgstr "" + +#: ./doc/install-guide/section_nova-controller.xml15(para) +msgid "" +"Install the openstack-nova meta-package, which installs " +"various Compute packages that are used on the controller node." +msgstr "" + +#: ./doc/install-guide/section_nova-controller.xml20(para) +msgid "" +"Install these Compute packages, which provide the Compute services that run " +"on the controller node." +msgstr "" + +#: ./doc/install-guide/section_nova-controller.xml38(para) +msgid "" +"Respond to the prompts for database management, [keystone_authtoken] " +"settings, RabbitMQ " +"credentials, and API " +"endpoint registration. The command runs " +"automatically." +msgstr "" + +#: ./doc/install-guide/section_nova-controller.xml49(para) +msgid "" +"Compute stores information in a database. In this guide, we use a MySQL " +"database on the controller node. Configure Compute with the database " +"location and credentials. Replace NOVA_DBPASS " +"with the password for the database that you will create in a later step." +msgstr "" + +#: ./doc/install-guide/section_nova-controller.xml55(replaceable) +#: ./doc/install-guide/section_nova-controller.xml61(replaceable) +#: ./doc/install-guide/section_nova-controller.xml93(replaceable) +#: ./doc/install-guide/section_nova-controller.xml107(replaceable) +#: ./doc/install-guide/section_nova-controller.xml109(replaceable) +#: ./doc/install-guide/section_nova-compute.xml110(replaceable) +msgid "NOVA_DBPASS" +msgstr "" + +#: ./doc/install-guide/section_nova-controller.xml56(para) +msgid "" +"Edit the [database] section in the " +"/etc/nova/nova.conf file to modify this key:" +msgstr "" + +#: ./doc/install-guide/section_nova-controller.xml65(para) +msgid "" +"Set these configuration keys to configure Compute to use the Qpid message " +"broker:" +msgstr "" + +#: ./doc/install-guide/section_nova-controller.xml72(para) +#: ./doc/install-guide/section_nova-compute.xml136(para) +msgid "" +"Configure the Compute Service to use the RabbitMQ message broker by setting " +"these configuration keys in the [DEFAULT] configuration " +"group of the /etc/nova/nova.conf file:" +msgstr "" + +#: ./doc/install-guide/section_nova-controller.xml81(para) +msgid "" +"Set these configuration keys to configure Compute to use the RabbitMQ " +"message broker:" +msgstr "" + +#: ./doc/install-guide/section_nova-controller.xml90(para) +msgid "" +"Run the command to create the Compute service database and " +"tables and a nova database user." +msgstr "" + +#: ./doc/install-guide/section_nova-controller.xml96(para) +msgid "" +"By default, the Ubuntu packages create an SQLite database. Delete the " +"nova.sqlite file created in the " +"/var/lib/nova/ directory so that it does not get used " +"by mistake." +msgstr "" + +#: ./doc/install-guide/section_nova-controller.xml102(para) +msgid "" +"Use the password you created previously to log in as root. Create a " +"nova database user:" +msgstr "" + +#: ./doc/install-guide/section_nova-controller.xml112(para) +msgid "Create the Compute service tables:" +msgstr "" + +#: ./doc/install-guide/section_nova-controller.xml116(para) +msgid "" +"Set the , , and " +" configuration options to the " +"internal IP address of the controller node:" +msgstr "" + +#: ./doc/install-guide/section_nova-controller.xml124(para) +#: ./doc/install-guide/section_nova-network.xml62(para) +msgid "" +"Edit the /etc/nova/nova.conf file and add these lines " +"to the [DEFAULT] section:" +msgstr "" + +#: ./doc/install-guide/section_nova-controller.xml127(para) +msgid "" +"In Debian, the debconf package automatically sets up " +"my_ip parameter but you must edit the " +"/etc/nova/nova.conf file to configure the " +" and " +" options, which appear at the " +"end of the file:" +msgstr "" + +#: ./doc/install-guide/section_nova-controller.xml142(para) +msgid "" +"Create a nova user that Compute uses to authenticate with" +" the Identity Service. Use the service tenant and give " +"the user the admin role:" +msgstr "" + +#: ./doc/install-guide/section_nova-controller.xml146(replaceable) +#: ./doc/install-guide/section_nova-controller.xml159(replaceable) +#: ./doc/install-guide/section_nova-controller.xml178(replaceable) +#: ./doc/install-guide/section_nova-controller.xml200(replaceable) +#: ./doc/install-guide/section_nova-compute.xml117(replaceable) +#: ./doc/install-guide/section_nova-compute.xml226(replaceable) +msgid "NOVA_PASS" +msgstr "" + +#: ./doc/install-guide/section_nova-controller.xml146(replaceable) +msgid "nova@example.com" +msgstr "" + +#: ./doc/install-guide/section_nova-controller.xml150(para) +msgid "" +"Configure Compute to use these credentials with the Identity Service running" +" on the controller. Replace NOVA_PASS with your " +"Compute password." +msgstr "" + +#: ./doc/install-guide/section_nova-controller.xml160(para) +msgid "" +"Edit the [DEFAULT] section in the " +"/etc/nova/nova.conf file to add this key:" +msgstr "" + +#: ./doc/install-guide/section_nova-controller.xml168(para) +msgid "Add these keys to the [keystone_authtoken] section:" +msgstr "" + +#: ./doc/install-guide/section_nova-controller.xml182(para) +msgid "" +"Add the credentials to the /etc/nova/api-paste.ini " +"file. Add these options to the [filter:authtoken] " +"section:" +msgstr "" + +#: ./doc/install-guide/section_nova-controller.xml187(title) +#: ./doc/install-guide/section_nova-compute.xml214(title) +msgid "Use of .ini files" +msgstr "" + +#: ./doc/install-guide/section_nova-controller.xml188(para) +msgid "" +"You might sometimes have to edit .ini files during " +"initial setup. However, do not edit these files for general configuration " +"tasks." +msgstr "" + +#: ./doc/install-guide/section_nova-controller.xml202(para) +msgid "" +"Ensure that the " +"option is set in the /etc/nova/nova.conf file." +msgstr "" + +#: ./doc/install-guide/section_nova-controller.xml209(para) +msgid "" +"You must register Compute with the Identity Service so that other OpenStack " +"services can locate it. Register the service and specify the endpoint:" +msgstr "" + +#: ./doc/install-guide/section_nova-controller.xml222(para) +msgid "" +"Start Compute services and configure them to start when the system boots:" +msgstr "" + +#: ./doc/install-guide/section_nova-controller.xml225(para) +msgid "Restart Compute services:" +msgstr "" + +#: ./doc/install-guide/section_nova-controller.xml246(para) +msgid "To verify your configuration, list available images:" +msgstr "" + +#: ./doc/install-guide/section_dashboard-system-reqs.xml6(title) +#: ./doc/install-guide/object-storage/section_object-storage-sys-requirements.xml7(title) +msgid "System requirements" +msgstr "" + +#: ./doc/install-guide/section_dashboard-system-reqs.xml7(para) +msgid "" +"Before you install the OpenStack dashboard, you must meet the following " +"system requirements:" +msgstr "" + +#: ./doc/install-guide/section_dashboard-system-reqs.xml11(para) +msgid "" +"OpenStack Compute installation. Enable the Identity Service for user and " +"project management." +msgstr "" + +#: ./doc/install-guide/section_dashboard-system-reqs.xml13(para) +msgid "Note the URLs of the Identity Service and Compute endpoints." +msgstr "" + +#: ./doc/install-guide/section_dashboard-system-reqs.xml17(para) +msgid "" +"Identity Service user with sudo privileges. Because Apache does not serve " +"content from a root user, users must run the dashboard as an Identity " +"Service user with sudo privileges." +msgstr "" + +#: ./doc/install-guide/section_dashboard-system-reqs.xml23(para) +msgid "" +"Python 2.6 or 2.7. The Python version must support Django. The Python " +"version should run on any system, including Mac OS X. Installation " +"prerequisites might differ by platform." +msgstr "" + +#: ./doc/install-guide/section_dashboard-system-reqs.xml29(para) +msgid "" +"Then, install and configure the dashboard on a node that can contact the " +"Identity Service." +msgstr "" + +#: ./doc/install-guide/section_dashboard-system-reqs.xml31(para) +msgid "" +"Provide users with the following information so that they can access the " +"dashboard through a web browser on their local machine:" +msgstr "" + +#: ./doc/install-guide/section_dashboard-system-reqs.xml36(para) +msgid "The public IP address from which they can access the dashboard" +msgstr "" + +#: ./doc/install-guide/section_dashboard-system-reqs.xml40(para) +msgid "The user name and password with which they can access the dashboard" +msgstr "" + +#: ./doc/install-guide/section_dashboard-system-reqs.xml44(para) +msgid "" +"Your web browser, and that of your users, must support HTML5 and have " +"cookies and JavaScript enabled." +msgstr "" + +#: ./doc/install-guide/section_dashboard-system-reqs.xml48(para) +msgid "" +"To use the VNC client with the dashboard, the browser must support HTML5 " +"Canvas and HTML5 WebSockets." +msgstr "" + +#: ./doc/install-guide/section_dashboard-system-reqs.xml50(para) +msgid "" +"For details about browsers that support noVNC, see https://github.com/kanaka/noVNC/blob/master/README.md," +" and https://github.com/kanaka/noVNC/wiki/Browser-support, " +"respectively." +msgstr "" + +#: ./doc/install-guide/section_nova-boot.xml5(title) +msgid "Launch an instance" +msgstr "" + +#: ./doc/install-guide/section_nova-boot.xml6(para) +msgid "" +"After you configure the Compute services, you can launch an instance. An " +"instance is a virtual machine that OpenStack provisions on a Compute server." +" This example shows you how to launch a low-resource instance by using a " +"downloaded image." +msgstr "" + +#: ./doc/install-guide/section_nova-boot.xml12(para) +msgid "This procedure assumes you have:" +msgstr "" + +#: ./doc/install-guide/section_nova-boot.xml15(para) +msgid "" +"Installed the nova client library on the machine on which you will run the " +"commands (log on the controller if you are not sure)." +msgstr "" + +#: ./doc/install-guide/section_nova-boot.xml20(para) +msgid "" +"Set environment variables to specify your credentials. See ." +msgstr "" + +#: ./doc/install-guide/section_nova-boot.xml24(para) +msgid "Downloaded an image. See ." +msgstr "" + +#: ./doc/install-guide/section_nova-boot.xml28(para) +msgid "Configured networking. See ." +msgstr "" + +#: ./doc/install-guide/section_nova-boot.xml35(para) +msgid "" +"Generate a keypair that consists of a private and public key to be able to " +"launch instances on OpenStack. These keys are injected into the instances to" +" make password-less SSH access to the instance. This depends on the way the " +"necessary tools are bundled into the images. For more details, see the OpenStack Admin User " +"Guide." +msgstr "" + +#: ./doc/install-guide/section_nova-boot.xml47(para) +msgid "" +"You have just created the mykey keypair. The " +"id_rsa private key is saved locally in " +"~/.ssh, which you can use to connect to an instance " +"launched by using mykey as the keypair. To view available keypairs:" +msgstr "" + +#: ./doc/install-guide/section_nova-boot.xml60(para) +msgid "" +"To launch an instance, you must specify the ID for the flavor you want to " +"use for the instance. A flavor is a resource allocation profile. For " +"example, it specifies how many virtual CPUs and how much RAM your instance " +"gets. To see a list of the available profiles:" +msgstr "" + +#: ./doc/install-guide/section_nova-boot.xml77(para) +msgid "Get the ID of the image to use for the instance:" +msgstr "" + +#: ./doc/install-guide/section_nova-boot.xml86(para) +msgid "" +"To use SSH and ping, you must configure security group rules. See the OpenStack " +"User Guide." +msgstr "" + +#: ./doc/install-guide/section_nova-boot.xml91(replaceable) +#: ./doc/install-guide/section_nova-boot.xml92(replaceable) +msgid "default" +msgstr "" + +#: ./doc/install-guide/section_nova-boot.xml95(para) +msgid "Launch the instance:" +msgstr "" + +#: ./doc/install-guide/section_nova-boot.xml96(replaceable) +msgid "flavorType" +msgstr "" + +#: ./doc/install-guide/section_nova-boot.xml96(replaceable) +msgid "keypairName" +msgstr "" + +#: ./doc/install-guide/section_nova-boot.xml96(replaceable) +#: ./doc/install-guide/app_reserved_uids.xml29(th) +msgid "ID" +msgstr "" + +#: ./doc/install-guide/section_nova-boot.xml96(replaceable) +msgid "newInstanceName" +msgstr "" + +#: ./doc/install-guide/section_nova-boot.xml97(para) +msgid "Create an instance by using flavor 1 or 2. For example:" +msgstr "" + +#: ./doc/install-guide/section_nova-boot.xml134(para) +msgid "" +"If sufficient RAM is not available for the instance, Compute creates, but " +"does not start, the instance and sets the status for the instance to " +"ERROR." +msgstr "" + +#: ./doc/install-guide/section_nova-boot.xml141(para) +msgid "" +"After the instance launches, use the to view its status. " +"The status changes from BUILD to " +"ACTIVE:" +msgstr "" + +#: ./doc/install-guide/section_nova-boot.xml159(para) +msgid "To show details for a specified instance:" +msgstr "" + +#: ./doc/install-guide/section_nova-boot.xml197(para) +msgid "" +"After the instance boots and initializes and you have configured security " +"groups, you can into the instance without a password by " +"using the keypair you specified in the command. Use the " +" command to get the IP address for the instance. You do not " +"need to specify the private key because it was stored in the default " +"location, ~/.ssh/.id_rsa, for the " +"client." +msgstr "" + +#: ./doc/install-guide/section_nova-boot.xml207(para) +msgid "" +"If using a CirrOS image to spawn an instance you must log in as the " +"cirros, and not the root, user." +msgstr "" + +#: ./doc/install-guide/section_nova-boot.xml210(para) +msgid "" +"You can also log in to the cirros account without an ssh " +"key by using the cubswin:) password:" +msgstr "" + +#: ./doc/install-guide/section_keystone-services.xml4(title) +msgid "Define services and API endpoints" +msgstr "" + +#: ./doc/install-guide/section_keystone-services.xml5(para) +msgid "" +"So that the Identity Service can track which OpenStack services are " +"installed and where they are located on the network, you must register each " +"service in your OpenStack installation. To register a service, run these " +"commands:" +msgstr "" + +#: ./doc/install-guide/section_keystone-services.xml11(para) +msgid ". Describes the service." +msgstr "" + +#: ./doc/install-guide/section_keystone-services.xml15(para) +msgid "" +". Associates API " +"endpoints with the service." +msgstr "" + +#: ./doc/install-guide/section_keystone-services.xml20(para) +msgid "" +"You must also register the Identity Service itself. Use the " +"OS_SERVICE_TOKEN environment variable, as set previously, for " +"authentication." +msgstr "" + +#: ./doc/install-guide/section_keystone-services.xml25(para) +msgid "Create a service entry for the Identity Service:" +msgstr "" + +#: ./doc/install-guide/section_keystone-services.xml36(para) +#: ./doc/install-guide/object-storage/section_object-storage-install.xml91(para) +msgid "" +"The service ID is randomly generated and is different from the one shown " +"here." +msgstr "" + +#: ./doc/install-guide/section_keystone-services.xml40(para) +msgid "" +"Specify an API endpoint for the Identity Service by using the returned " +"service ID. When you specify an endpoint, you provide URLs for the public " +"API, internal API, and admin API. In this guide, the " +"controller host name is used. Note that the Identity " +"Service uses a different port for the admin API." +msgstr "" + +#: ./doc/install-guide/section_keystone-services.xml63(para) +msgid "" +"You will need to create an additional endpoint for each service added to " +"your OpenStack environment. The sections of this guide associated with the " +"installation of each service include the endpoint creation step specific to " +"the service." +msgstr "" + +#: ./doc/install-guide/section_keystone-verify.xml6(title) +msgid "Verify the Identity Service installation" +msgstr "" + +#: ./doc/install-guide/section_keystone-verify.xml9(para) +msgid "" +"To verify that the Identity Service is installed and configured correctly, " +"clear the values in the OS_SERVICE_TOKEN and " +"OS_SERVICE_ENDPOINT environment variables:" +msgstr "" + +#: ./doc/install-guide/section_keystone-verify.xml15(para) +msgid "" +"These variables, which were used to bootstrap the administrative user and " +"register the Identity Service, are no longer needed." +msgstr "" + +#: ./doc/install-guide/section_keystone-verify.xml20(para) +msgid "You can now use regular user name-based authentication." +msgstr "" + +#: ./doc/install-guide/section_keystone-verify.xml22(para) +msgid "" +"Request a authentication token by using the admin user " +"and the password you chose for that user:" +msgstr "" + +#: ./doc/install-guide/section_keystone-verify.xml27(para) +msgid "" +"In response, you receive a token paired with your user ID. This verifies " +"that the Identity Service is running on the expected endpoint and that your " +"user account is established with the expected credentials." +msgstr "" + +#: ./doc/install-guide/section_keystone-verify.xml33(para) +msgid "" +"Verify that authorization behaves as expected. To do so, request " +"authorization on a tenant:" +msgstr "" + +#: ./doc/install-guide/section_keystone-verify.xml38(para) +msgid "" +"In response, you receive a token that includes the ID of the tenant that you" +" specified. This verifies that your user account has an explicitly defined " +"role on the specified tenant and the tenant exists as expected." +msgstr "" + +#: ./doc/install-guide/section_keystone-verify.xml44(para) +msgid "" +"You can also set your --os-* variables in your " +"environment to simplify command-line usage. Set up a " +"openrc.sh file with the admin credentials and admin " +"endpoint:" +msgstr "" + +#: ./doc/install-guide/section_keystone-verify.xml54(para) +msgid "Source this file to read in the environment variables:" +msgstr "" + +#: ./doc/install-guide/section_keystone-verify.xml59(para) +msgid "" +"Verify that your openrc.sh file is configured " +"correctly. Run the same command without the --os-* " +"arguments:" +msgstr "" + +#: ./doc/install-guide/section_keystone-verify.xml63(para) +msgid "" +"The command returns a token and the ID of the specified tenant. This " +"verifies that you have configured your environment variables correctly." +msgstr "" + +#: ./doc/install-guide/section_keystone-verify.xml68(para) +msgid "" +"Verify that your admin account has authorization to perform administrative " +"commands:" +msgstr "" + +#: ./doc/install-guide/section_keystone-verify.xml76(para) +msgid "" +"This verifies that your user account has the admin role, " +"which matches the role used in the Identity Service " +"policy.json file." +msgstr "" + +#: ./doc/install-guide/section_keystone-verify.xml81(para) +msgid "" +"As long as you define your credentials and the Identity Service endpoint " +"through the command line or environment variables, you can run all OpenStack" +" client commands from any machine. For details, see ." +msgstr "" + +#. When image changes, this message will be marked fuzzy or untranslated for +#. you. +#. It doesn't matter what you translate it to: it's not used at all. +#: ./doc/install-guide/section_neutron-per-tenant-routers-with-private-networks.xml15(None) +#: ./doc/install-guide/section_neutron-per-tenant-routers-with-private-networks.xml863(None) +msgid "" +"@@image: '../common/figures/UseCase-MultiRouter.png'; " +"md5=5695d4b003e2f8442eab135cbcd1f842" +msgstr "" + +#. When image changes, this message will be marked fuzzy or untranslated for +#. you. +#. It doesn't matter what you translate it to: it's not used at all. +#: ./doc/install-guide/section_neutron-per-tenant-routers-with-private-networks.xml25(None) +msgid "" +"@@image: '../common/figures/demo_routers_with_private_networks.png'; " +"md5=985b8cacfd7161ce50ee13106b27f854" +msgstr "" + +#: ./doc/install-guide/section_neutron-per-tenant-routers-with-private-networks.xml6(title) +msgid "Per-tenant routers with private networks" +msgstr "" + +#: ./doc/install-guide/section_neutron-per-tenant-routers-with-private-networks.xml7(para) +msgid "" +"This section describes how to install the OpenStack Networking service and " +"its components for a use case that has per-tenant routers with private " +"networks." +msgstr "" + +#: ./doc/install-guide/section_neutron-per-tenant-routers-with-private-networks.xml19(para) +msgid "The following figure shows the setup:" +msgstr "" + +#: ./doc/install-guide/section_neutron-per-tenant-routers-with-private-networks.xml29(para) +msgid "As shown in the figure, the setup includes:" +msgstr "" + +#: ./doc/install-guide/section_neutron-per-tenant-routers-with-private-networks.xml32(para) +msgid "An interface for management traffic on each node." +msgstr "" + +#: ./doc/install-guide/section_neutron-per-tenant-routers-with-private-networks.xml36(para) +msgid "Use of the Open vSwitch plug-in." +msgstr "" + +#: ./doc/install-guide/section_neutron-per-tenant-routers-with-private-networks.xml39(para) +msgid "GRE tunnels for data transport on all agents." +msgstr "" + +#: ./doc/install-guide/section_neutron-per-tenant-routers-with-private-networks.xml42(para) +msgid "" +"Floating IPs and router gateway ports that are configured in an external " +"network, and a physical router that connects the floating IPs and router " +"gateway ports to the outside world." +msgstr "" + +#: ./doc/install-guide/section_neutron-per-tenant-routers-with-private-networks.xml49(para) +msgid "" +"Because this example runs a DHCP agent and L3 agent on one node, you must " +"set the use_namespace option to True " +"in the configuration file for each agent. The default is " +"True." +msgstr "" + +#: ./doc/install-guide/section_neutron-per-tenant-routers-with-private-networks.xml55(para) +msgid "This table describes the nodes:" +msgstr "" + +#: ./doc/install-guide/section_neutron-per-tenant-routers-with-private-networks.xml61(th) +#: ./doc/install-guide/section_neutron-provider-router-with-private_networks.xml31(th) +#: ./doc/install-guide/section_neutron-single-flat.xml32(th) +msgid "Node" +msgstr "" + +#: ./doc/install-guide/section_neutron-per-tenant-routers-with-private-networks.xml62(th) +#: ./doc/install-guide/section_neutron-provider-router-with-private_networks.xml32(th) +#: ./doc/install-guide/app_reserved_uids.xml28(th) +#: ./doc/install-guide/section_neutron-single-flat.xml33(th) +msgid "Description" +msgstr "" + +#: ./doc/install-guide/section_neutron-per-tenant-routers-with-private-networks.xml67(td) +#: ./doc/install-guide/section_neutron-single-flat.xml38(td) +msgid "Controller Node" +msgstr "" + +#: ./doc/install-guide/section_neutron-per-tenant-routers-with-private-networks.xml68(para) +msgid "" +"Runs Networking, Identity Service, and all Compute services that are " +"required to deploy VMs (nova-api," +" nova-scheduler, for example). " +"The node must have at least one network interface, which connects to the " +"Management Network. The host name is controlnode, which " +"other nodes resolve to the IP of the controller node." +msgstr "" + +#: ./doc/install-guide/section_neutron-per-tenant-routers-with-private-networks.xml80(para) +msgid "" +"The nova-network service should " +"not be running. This is replaced by Networking." +msgstr "" + +#: ./doc/install-guide/section_neutron-per-tenant-routers-with-private-networks.xml87(td) +#: ./doc/install-guide/section_neutron-provider-router-with-private_networks.xml281(title) +#: ./doc/install-guide/section_neutron-single-flat.xml70(td) +msgid "Compute Node" +msgstr "" + +#: ./doc/install-guide/section_neutron-per-tenant-routers-with-private-networks.xml90(systemitem) +#: ./doc/install-guide/section_neutron-single-flat.xml73(systemitem) +msgid "nova-compute" +msgstr "" + +#: ./doc/install-guide/section_neutron-per-tenant-routers-with-private-networks.xml92(systemitem) +msgid "nova-*" +msgstr "" + +#: ./doc/install-guide/section_neutron-per-tenant-routers-with-private-networks.xml88(td) +msgid "" +"Runs the Networking L2 agent and the Compute services that run VMs " +"( specifically, and optionally other " +"services depending on configuration). The node must have at least two " +"network interfaces. One interface communicates with the controller node " +"through the management network. The other node is used for the VM traffic on" +" the data network. The VM receives its IP address from the DHCP agent on " +"this network." +msgstr "" + +#: ./doc/install-guide/section_neutron-per-tenant-routers-with-private-networks.xml101(td) +#: ./doc/install-guide/section_neutron-single-flat.xml84(td) +msgid "Network Node" +msgstr "" + +#: ./doc/install-guide/section_neutron-per-tenant-routers-with-private-networks.xml102(td) +msgid "" +"Runs Networking L2 agent, DHCP agent and L3 agent. This node has access to " +"the external network. The DHCP agent allocates IP addresses to the VMs on " +"data network. (Technically, the addresses are allocated by the Networking " +"server, and distributed by the dhcp agent.) The node must have at least two " +"network interfaces. One interface communicates with the controller node " +"through the management network. The other interface is used as external " +"network. GRE tunnels are set up as data networks." +msgstr "" + +#: ./doc/install-guide/section_neutron-per-tenant-routers-with-private-networks.xml115(td) +#: ./doc/install-guide/section_neutron-single-flat.xml94(td) +msgid "Router" +msgstr "" + +#: ./doc/install-guide/section_neutron-per-tenant-routers-with-private-networks.xml116(td) +#: ./doc/install-guide/section_neutron-single-flat.xml95(td) +msgid "" +"Router has IP 30.0.0.1, which is the default gateway for all VMs. The router" +" must be able to access public networks." +msgstr "" + +#: ./doc/install-guide/section_neutron-per-tenant-routers-with-private-networks.xml122(para) +msgid "The use case assumes the following:" +msgstr "" + +#: ./doc/install-guide/section_neutron-per-tenant-routers-with-private-networks.xml123(emphasis) +#: ./doc/install-guide/section_neutron-single-flat.xml102(emphasis) +msgid "Controller node" +msgstr "" + +#: ./doc/install-guide/section_neutron-per-tenant-routers-with-private-networks.xml126(para) +#: ./doc/install-guide/section_neutron-single-flat.xml105(para) +msgid "Relevant Compute services are installed, configured, and running." +msgstr "" + +#: ./doc/install-guide/section_neutron-per-tenant-routers-with-private-networks.xml130(para) +msgid "" +"Glance is installed, configured, and running. In addition, an image named " +"tty must be present." +msgstr "" + +#: ./doc/install-guide/section_neutron-per-tenant-routers-with-private-networks.xml135(para) +msgid "" +"Identity is installed, configured, and running. A Networking user named " +"neutron should be created on tenant " +"service with password " +"NEUTRON_PASS." +msgstr "" + +#: ./doc/install-guide/section_neutron-per-tenant-routers-with-private-networks.xml145(para) +msgid "" +"RabbitMQ is running with default guest and password " +"RABBIT_PASS." +msgstr "" + +#: ./doc/install-guide/section_neutron-per-tenant-routers-with-private-networks.xml150(para) +#: ./doc/install-guide/section_neutron-single-flat.xml133(para) +msgid "MySQL server (user is root)." +msgstr "" + +#: ./doc/install-guide/section_neutron-per-tenant-routers-with-private-networks.xml143(para) +msgid "Additional services: " +msgstr "" + +#: ./doc/install-guide/section_neutron-per-tenant-routers-with-private-networks.xml156(emphasis) +#: ./doc/install-guide/section_neutron-single-flat.xml139(emphasis) +msgid "Compute node" +msgstr "" + +#: ./doc/install-guide/section_neutron-per-tenant-routers-with-private-networks.xml157(para) +msgid "Install and configure Compute." +msgstr "" + +#: ./doc/install-guide/section_neutron-per-tenant-routers-with-private-networks.xml159(title) +#: ./doc/install-guide/section_neutron-provider-router-with-private_networks.xml91(title) +#: ./doc/install-guide/section_neutron-single-flat.xml146(title) +msgid "Install" +msgstr "" + +#: ./doc/install-guide/section_neutron-per-tenant-routers-with-private-networks.xml162(emphasis) +#: ./doc/install-guide/section_neutron-single-flat.xml149(emphasis) +msgid "Controller node - Networking server" +msgstr "" + +#: ./doc/install-guide/section_neutron-per-tenant-routers-with-private-networks.xml166(para) +#: ./doc/install-guide/section_neutron-single-flat.xml154(para) +msgid "Install the Networking server." +msgstr "" + +#: ./doc/install-guide/section_neutron-per-tenant-routers-with-private-networks.xml169(para) +#: ./doc/install-guide/section_neutron-single-flat.xml168(para) +msgid "Create database ovs_neutron." +msgstr "" + +#: ./doc/install-guide/section_neutron-per-tenant-routers-with-private-networks.xml173(para) +msgid "" +"Update the Networking configuration file, " +"/etc/neutron/neutron.conf, with plug-in choice and Identity " +"Service user as necessary:" +msgstr "" + +#: ./doc/install-guide/section_neutron-per-tenant-routers-with-private-networks.xml186(replaceable) +#: ./doc/install-guide/section_neutron-per-tenant-routers-with-private-networks.xml199(replaceable) +#: ./doc/install-guide/section_neutron-per-tenant-routers-with-private-networks.xml276(replaceable) +#: ./doc/install-guide/section_neutron-provider-router-with-private_networks.xml116(replaceable) +#: ./doc/install-guide/section_neutron-provider-router-with-private_networks.xml181(replaceable) +#: ./doc/install-guide/section_neutron-provider-router-with-private_networks.xml185(replaceable) +#: ./doc/install-guide/section_neutron-provider-router-with-private_networks.xml191(replaceable) +#: ./doc/install-guide/section_neutron-provider-router-with-private_networks.xml325(replaceable) +#: ./doc/install-guide/section_neutron-provider-router-with-private_networks.xml329(replaceable) +#: ./doc/install-guide/section_neutron-provider-router-with-private_networks.xml335(replaceable) +#: ./doc/install-guide/section_neutron-single-flat.xml193(replaceable) +#: ./doc/install-guide/section_neutron-single-flat.xml234(replaceable) +#: ./doc/install-guide/section_neutron-single-flat.xml337(replaceable) +#: ./doc/install-guide/section_neutron-single-flat.xml346(replaceable) +#: ./doc/install-guide/section_neutron-install.xml141(replaceable) +#: ./doc/install-guide/section_neutron-install.xml143(replaceable) +#: ./doc/install-guide/section_neutron-install.xml334(replaceable) +#: ./doc/install-guide/section_neutron-install.xml341(replaceable) +#: ./doc/install-guide/section_neutron-install.xml912(replaceable) +#: ./doc/install-guide/section_neutron-install.xml919(replaceable) +#: ./doc/install-guide/section_neutron-install.xml1220(replaceable) +#: ./doc/install-guide/section_neutron-install.xml1230(replaceable) +msgid "NEUTRON_DBPASS" +msgstr "" + +#: ./doc/install-guide/section_neutron-per-tenant-routers-with-private-networks.xml191(replaceable) +#: ./doc/install-guide/section_neutron-per-tenant-routers-with-private-networks.xml236(replaceable) +#: ./doc/install-guide/section_neutron-provider-router-with-private_networks.xml132(replaceable) +#: ./doc/install-guide/section_neutron-provider-router-with-private_networks.xml225(replaceable) +#: ./doc/install-guide/section_neutron-provider-router-with-private_networks.xml237(replaceable) +#: ./doc/install-guide/section_neutron-single-flat.xml190(replaceable) +#: ./doc/install-guide/section_neutron-single-flat.xml239(replaceable) +#: ./doc/install-guide/section_neutron-single-flat.xml283(replaceable) +#: ./doc/install-guide/section_neutron-single-flat.xml299(replaceable) +#: ./doc/install-guide/section_neutron-install.xml149(replaceable) +#: ./doc/install-guide/section_neutron-install.xml266(replaceable) +#: ./doc/install-guide/section_neutron-install.xml288(replaceable) +#: ./doc/install-guide/section_neutron-install.xml357(replaceable) +#: ./doc/install-guide/section_neutron-install.xml369(replaceable) +#: ./doc/install-guide/section_neutron-install.xml439(replaceable) +#: ./doc/install-guide/section_neutron-install.xml453(replaceable) +#: ./doc/install-guide/section_neutron-install.xml859(replaceable) +#: ./doc/install-guide/section_neutron-install.xml893(replaceable) +#: ./doc/install-guide/section_neutron-install.xml930(replaceable) +#: ./doc/install-guide/section_neutron-install.xml944(replaceable) +#: ./doc/install-guide/section_neutron-install.xml961(replaceable) +#: ./doc/install-guide/section_neutron-install.xml978(replaceable) +#: ./doc/install-guide/section_neutron-install.xml1253(replaceable) +#: ./doc/install-guide/section_neutron-install.xml1279(replaceable) +#: ./doc/install-guide/section_neutron-install.xml1295(replaceable) +#: ./doc/install-guide/section_neutron-install.xml1311(replaceable) +#: ./doc/install-guide/section_neutron-install.xml1380(replaceable) +#: ./doc/install-guide/section_neutron-install.xml1397(replaceable) +msgid "NEUTRON_PASS" +msgstr "" + +#: ./doc/install-guide/section_neutron-per-tenant-routers-with-private-networks.xml202(para) +msgid "" +"Update the plug-in configuration file, " +"/etc/neutron/plugins/openvswitch/ovs_neutron_plugin.ini:" +msgstr "" + +#: ./doc/install-guide/section_neutron-per-tenant-routers-with-private-networks.xml210(para) +msgid "Start the Networking server." +msgstr "" + +#: ./doc/install-guide/section_neutron-per-tenant-routers-with-private-networks.xml211(para) +msgid "" +"The Networking server can be a service of the operating system. The command " +"to start the service depends on your operating system. The following command" +" runs the Networking server directly:" +msgstr "" + +#: ./doc/install-guide/section_neutron-per-tenant-routers-with-private-networks.xml223(emphasis) +msgid "Compute node—Compute" +msgstr "" + +#: ./doc/install-guide/section_neutron-per-tenant-routers-with-private-networks.xml225(para) +msgid "Install Compute services." +msgstr "" + +#: ./doc/install-guide/section_neutron-per-tenant-routers-with-private-networks.xml228(para) +msgid "" +"Update the Compute /etc/nova/nova.conf configuration " +"file. Make sure the following line appears at the end of this file:" +msgstr "" + +#: ./doc/install-guide/section_neutron-per-tenant-routers-with-private-networks.xml243(para) +msgid "Restart relevant Compute services." +msgstr "" + +#: ./doc/install-guide/section_neutron-per-tenant-routers-with-private-networks.xml249(emphasis) +msgid "Compute and Networking node—L2 agent" +msgstr "" + +#: ./doc/install-guide/section_neutron-per-tenant-routers-with-private-networks.xml253(para) +msgid "Install and start Open vSwitch." +msgstr "" + +#: ./doc/install-guide/section_neutron-per-tenant-routers-with-private-networks.xml256(para) +msgid "Install the L2 agent (Neutron Open vSwitch agent)." +msgstr "" + +#: ./doc/install-guide/section_neutron-per-tenant-routers-with-private-networks.xml260(para) +#: ./doc/install-guide/section_neutron-provider-router-with-private_networks.xml168(para) +msgid "Add the integration bridge to the Open vSwitch:" +msgstr "" + +#: ./doc/install-guide/section_neutron-per-tenant-routers-with-private-networks.xml265(para) +msgid "" +"Update the Networking configuration file, " +"/etc/neutron/neutron.conf:" +msgstr "" + +#: ./doc/install-guide/section_neutron-per-tenant-routers-with-private-networks.xml279(para) +msgid "" +"Update the plug-in configuration file, " +"/etc/neutron/plugins/openvswitch/ovs_neutron_plugin.ini." +msgstr "" + +#: ./doc/install-guide/section_neutron-per-tenant-routers-with-private-networks.xml282(para) +msgid "Compute node:" +msgstr "" + +#: ./doc/install-guide/section_neutron-per-tenant-routers-with-private-networks.xml288(para) +msgid "Network node:" +msgstr "" + +#: ./doc/install-guide/section_neutron-per-tenant-routers-with-private-networks.xml296(para) +msgid "Create the integration bridge br-int:" +msgstr "" + +#: ./doc/install-guide/section_neutron-per-tenant-routers-with-private-networks.xml301(para) +msgid "Start the Networking L2 agent" +msgstr "" + +#: ./doc/install-guide/section_neutron-per-tenant-routers-with-private-networks.xml302(para) +msgid "" +"The Networking Open vSwitch L2 agent can be a service of operating system. " +"The command to start depends on your operating systems. The following " +"command runs the service directly:" +msgstr "" + +#: ./doc/install-guide/section_neutron-per-tenant-routers-with-private-networks.xml313(emphasis) +msgid "Network node—DHCP agent" +msgstr "" + +#: ./doc/install-guide/section_neutron-per-tenant-routers-with-private-networks.xml317(para) +#: ./doc/install-guide/section_neutron-single-flat.xml412(para) +msgid "Install the DHCP agent." +msgstr "" + +#: ./doc/install-guide/section_neutron-per-tenant-routers-with-private-networks.xml320(para) +msgid "" +"Update the Networking configuration file, " +"/etc/neutron/neutron.conf" +msgstr "" + +#: ./doc/install-guide/section_neutron-per-tenant-routers-with-private-networks.xml331(literal) +msgid "allow_overlapping_ips" +msgstr "" + +#: ./doc/install-guide/section_neutron-per-tenant-routers-with-private-networks.xml330(emphasis) +msgid "" +"Set because TenantA and TenantC use overlapping subnets." +msgstr "" + +#: ./doc/install-guide/section_neutron-per-tenant-routers-with-private-networks.xml336(para) +msgid "" +"Update the DHCP /etc/neutron/dhcp_agent.ini " +"configuration file:" +msgstr "" + +#: ./doc/install-guide/section_neutron-per-tenant-routers-with-private-networks.xml342(para) +msgid "Start the DHCP agent." +msgstr "" + +#: ./doc/install-guide/section_neutron-per-tenant-routers-with-private-networks.xml343(para) +msgid "" +"The Networking DHCP agent can be a service of operating system. The command " +"to start the service depends on your operating system. The following command" +" runs the service directly:" +msgstr "" + +#: ./doc/install-guide/section_neutron-per-tenant-routers-with-private-networks.xml354(emphasis) +msgid "Network node—L3 agent" +msgstr "" + +#: ./doc/install-guide/section_neutron-per-tenant-routers-with-private-networks.xml358(para) +msgid "Install the L3 agent." +msgstr "" + +#: ./doc/install-guide/section_neutron-per-tenant-routers-with-private-networks.xml361(para) +msgid "Add the external network bridge" +msgstr "" + +#: ./doc/install-guide/section_neutron-per-tenant-routers-with-private-networks.xml365(para) +msgid "" +"Add the physical interface, for example eth0, that is connected to the " +"outside network to this bridge:" +msgstr "" + +#: ./doc/install-guide/section_neutron-per-tenant-routers-with-private-networks.xml371(para) +msgid "" +"Update the L3 configuration file " +"/etc/neutron/l3_agent.ini:" +msgstr "" + +#: ./doc/install-guide/section_neutron-per-tenant-routers-with-private-networks.xml378(literal) +msgid "use_namespaces" +msgstr "" + +#: ./doc/install-guide/section_neutron-per-tenant-routers-with-private-networks.xml377(emphasis) +msgid "" +"Set the option (it is True by default) because TenantA and " +"TenantC have overlapping subnets, and the routers are hosted on one l3 agent" +" network node." +msgstr "" + +#: ./doc/install-guide/section_neutron-per-tenant-routers-with-private-networks.xml386(para) +msgid "Start the L3 agent" +msgstr "" + +#: ./doc/install-guide/section_neutron-per-tenant-routers-with-private-networks.xml387(para) +msgid "" +"The Networking L3 agent can be a service of operating system. The command to" +" start the service depends on your operating system. The following command " +"starts the agent directly:" +msgstr "" + +#: ./doc/install-guide/section_neutron-per-tenant-routers-with-private-networks.xml401(title) +#: ./doc/install-guide/section_neutron-single-flat.xml475(title) +msgid "Configure logical network" +msgstr "" + +#: ./doc/install-guide/section_neutron-per-tenant-routers-with-private-networks.xml402(para) +msgid "You can run these commands on the network node." +msgstr "" + +#: ./doc/install-guide/section_neutron-per-tenant-routers-with-private-networks.xml404(para) +msgid "" +"Ensure that the following environment variables are set. Various clients use" +" these to access the Identity Service." +msgstr "" + +#: ./doc/install-guide/section_neutron-per-tenant-routers-with-private-networks.xml414(para) +#: ./doc/install-guide/section_neutron-single-flat.xml488(para) +msgid "Get the tenant ID (Used as $TENANT_ID later):" +msgstr "" + +#: ./doc/install-guide/section_neutron-per-tenant-routers-with-private-networks.xml428(para) +msgid "Get user information:" +msgstr "" + +#: ./doc/install-guide/section_neutron-per-tenant-routers-with-private-networks.xml441(para) +msgid "Create the external network and its subnet by admin user:" +msgstr "" + +#: ./doc/install-guide/section_neutron-per-tenant-routers-with-private-networks.xml479(literal) +msgid "provider:network_type local" +msgstr "" + +#: ./doc/install-guide/section_neutron-per-tenant-routers-with-private-networks.xml482(literal) +msgid "router:external true" +msgstr "" + +#: ./doc/install-guide/section_neutron-per-tenant-routers-with-private-networks.xml478(emphasis) +msgid "" +" means that Networking does not have to realize this network" +" through provider network. means that an external network " +"is created where you can create floating IP and router gateway port." +msgstr "" + +#: ./doc/install-guide/section_neutron-per-tenant-routers-with-private-networks.xml488(para) +msgid "Add an IP on external network to br-ex." +msgstr "" + +#: ./doc/install-guide/section_neutron-per-tenant-routers-with-private-networks.xml489(para) +msgid "" +"Because br-ex is the external network bridge, add an IP 30.0.0.100/24 to br-" +"ex and ping the floating IP of the VM from our network node." +msgstr "" + +#: ./doc/install-guide/section_neutron-per-tenant-routers-with-private-networks.xml497(para) +msgid "Serve TenantA." +msgstr "" + +#: ./doc/install-guide/section_neutron-per-tenant-routers-with-private-networks.xml498(para) +msgid "" +"For TenantA, create a private network, subnet, server, router, and floating " +"IP." +msgstr "" + +#: ./doc/install-guide/section_neutron-per-tenant-routers-with-private-networks.xml502(para) +msgid "Create a network for TenantA:" +msgstr "" + +#: ./doc/install-guide/section_neutron-per-tenant-routers-with-private-networks.xml518(para) +msgid "" +"After that, you can use admin user to query the provider network " +"information:" +msgstr "" + +#: ./doc/install-guide/section_neutron-per-tenant-routers-with-private-networks.xml537(para) +msgid "" +"The network has GRE tunnel ID (for example, provider:segmentation_id) 1." +msgstr "" + +#: ./doc/install-guide/section_neutron-per-tenant-routers-with-private-networks.xml542(para) +msgid "Create a subnet on the network TenantA-Net:" +msgstr "" + +#: ./doc/install-guide/section_neutron-per-tenant-routers-with-private-networks.xml564(para) +msgid "Create a server for TenantA:" +msgstr "" + +#: ./doc/install-guide/section_neutron-per-tenant-routers-with-private-networks.xml576(para) +msgid "" +"It is important to understand that you should not attach the instance to " +"Ext-Net directly. Instead, you must use a floating IP to make it accessible " +"from the external network." +msgstr "" + +#: ./doc/install-guide/section_neutron-per-tenant-routers-with-private-networks.xml585(para) +msgid "Create and configure a router for TenantA:" +msgstr "" + +#: ./doc/install-guide/section_neutron-per-tenant-routers-with-private-networks.xml603(para) +msgid "Added interface to router TenantA-R1" +msgstr "" + +#: ./doc/install-guide/section_neutron-per-tenant-routers-with-private-networks.xml612(para) +msgid "Associate a floating IP for TenantA_VM1." +msgstr "" + +#: ./doc/install-guide/section_neutron-per-tenant-routers-with-private-networks.xml616(para) +msgid "Create a floating IP:" +msgstr "" + +#: ./doc/install-guide/section_neutron-per-tenant-routers-with-private-networks.xml633(para) +msgid "" +"Get the port ID of the VM with ID 7c5e6499-7ef7-4e36-8216-62c2941d21ff:" +msgstr "" + +#: ./doc/install-guide/section_neutron-per-tenant-routers-with-private-networks.xml645(para) +msgid "Associate the floating IP with the VM port:" +msgstr "" + +#: ./doc/install-guide/section_neutron-per-tenant-routers-with-private-networks.xml663(para) +msgid "Ping the public network from the server of TenantA." +msgstr "" + +#: ./doc/install-guide/section_neutron-per-tenant-routers-with-private-networks.xml665(para) +msgid "" +"In my environment, 192.168.1.0/24 is my public network connected with my " +"physical router, which also connects to the external network 30.0.0.0/24. " +"With the floating IP and virtual router, you can ping the public network " +"within the server of tenant A:" +msgstr "" + +#: ./doc/install-guide/section_neutron-per-tenant-routers-with-private-networks.xml683(para) +msgid "Ping floating IP of the TenantA's server:" +msgstr "" + +#: ./doc/install-guide/section_neutron-per-tenant-routers-with-private-networks.xml696(para) +msgid "Create other servers for TenantA." +msgstr "" + +#: ./doc/install-guide/section_neutron-per-tenant-routers-with-private-networks.xml697(para) +msgid "You can create more servers for TenantA and add floating IPs for them." +msgstr "" + +#: ./doc/install-guide/section_neutron-per-tenant-routers-with-private-networks.xml701(para) +msgid "Serve TenantC." +msgstr "" + +#: ./doc/install-guide/section_neutron-per-tenant-routers-with-private-networks.xml702(para) +msgid "" +"For TenantC, you create two private networks with subnet 10.0.0.0/24 and " +"subnet 10.0.1.0/24, some servers, one router to connect to these two subnets" +" and some floating IPs." +msgstr "" + +#: ./doc/install-guide/section_neutron-per-tenant-routers-with-private-networks.xml708(para) +msgid "Create networks and subnets for TenantC:" +msgstr "" + +#: ./doc/install-guide/section_neutron-per-tenant-routers-with-private-networks.xml721(para) +msgid "" +"After that you can use admin user to query the network's provider network " +"information:" +msgstr "" + +#: ./doc/install-guide/section_neutron-per-tenant-routers-with-private-networks.xml757(para) +msgid "" +"You can see GRE tunnel IDs (such as, provider:segmentation_id) 2 and 3. And " +"also note the network IDs and subnet IDs because you use them to create VMs " +"and router." +msgstr "" + +#: ./doc/install-guide/section_neutron-per-tenant-routers-with-private-networks.xml764(para) +msgid "Create a server TenantC-VM1 for TenantC on TenantC-Net1." +msgstr "" + +#: ./doc/install-guide/section_neutron-per-tenant-routers-with-private-networks.xml771(para) +msgid "Create a server TenantC-VM3 for TenantC on TenantC-Net2." +msgstr "" + +#: ./doc/install-guide/section_neutron-per-tenant-routers-with-private-networks.xml778(para) +msgid "List servers of TenantC." +msgstr "" + +#: ./doc/install-guide/section_neutron-per-tenant-routers-with-private-networks.xml787(para) +msgid "Note the server IDs because you use them later." +msgstr "" + +#: ./doc/install-guide/section_neutron-per-tenant-routers-with-private-networks.xml791(para) +msgid "Make sure servers get their IPs." +msgstr "" + +#: ./doc/install-guide/section_neutron-per-tenant-routers-with-private-networks.xml792(para) +msgid "" +"You can use VNC to log on the VMs to check if they get IPs. If not, you must" +" make sure that the Networking components are running correctly and the GRE " +"tunnels work." +msgstr "" + +#: ./doc/install-guide/section_neutron-per-tenant-routers-with-private-networks.xml799(para) +msgid "Create and configure a router for TenantC:" +msgstr "" + +#: ./doc/install-guide/section_neutron-per-tenant-routers-with-private-networks.xml814(para) +msgid "Checkpoint: ping from within TenantC's servers." +msgstr "" + +#: ./doc/install-guide/section_neutron-per-tenant-routers-with-private-networks.xml816(para) +msgid "" +"Because a router connects to two subnets, the VMs on these subnets can ping " +"each other. And because the gateway for the router is set, TenantC's servers" +" can ping external network IPs, such as 192.168.1.1, 30.0.0.1, and so on." +msgstr "" + +#: ./doc/install-guide/section_neutron-per-tenant-routers-with-private-networks.xml824(para) +#: ./doc/install-guide/section_neutron-per-tenant-routers-with-private-networks.xml835(para) +msgid "Associate floating IPs for TenantC's servers." +msgstr "" + +#: ./doc/install-guide/section_neutron-per-tenant-routers-with-private-networks.xml826(para) +msgid "" +"Because a router connects to two subnets, the VMs on these subnets can ping " +"each other. And because the gateway interface for the router is set, " +"TenantC's servers can ping external network IPs, such as 192.168.1.1, " +"30.0.0.1, and so on." +msgstr "" + +#: ./doc/install-guide/section_neutron-per-tenant-routers-with-private-networks.xml837(para) +msgid "" +"You can use similar commands to the ones used in the section for TenantA." +msgstr "" + +#: ./doc/install-guide/section_neutron-per-tenant-routers-with-private-networks.xml845(title) +msgid "Use case: per-tenant routers with private networks" +msgstr "" + +#: ./doc/install-guide/section_neutron-per-tenant-routers-with-private-networks.xml847(para) +msgid "" +"This use case represents a more advanced router scenario in which each " +"tenant gets at least one router, and potentially has access to the " +"Networking API to create additional routers. The tenant can create their own" +" networks, potentially uplinking those networks to a router. This model " +"enables tenant-defined, multi-tier applications, with each tier being a " +"separate network behind the router. Because there are multiple routers, " +"tenant subnets can overlap without conflicting, because access to external " +"networks all happens through SNAT or floating IPs. Each router uplink and " +"floating IP is allocated from the external network subnet." +msgstr "" + +#: ./doc/install-guide/ch_horizon.xml6(title) +msgid "Add the dashboard" +msgstr "" + +#: ./doc/install-guide/ch_horizon.xml7(para) +msgid "" +"The OpenStack dashboard, also known as Horizon, is a Web " +"interface that enables cloud administrators and users to manage various " +"OpenStack resources and services." +msgstr "" + +#: ./doc/install-guide/ch_horizon.xml12(para) +msgid "" +"The dashboard enables web-based interactions with the OpenStack Compute " +"cloud controller through the OpenStack APIs." +msgstr "" + +#: ./doc/install-guide/ch_horizon.xml15(para) +msgid "" +"These instructions show an example deployment configured with an Apache web " +"server." +msgstr "" + +#: ./doc/install-guide/ch_horizon.xml17(para) +msgid "" +"After you install and configure the " +"dashboard, you can complete the following tasks:" +msgstr "" + +#: ./doc/install-guide/ch_horizon.xml22(para) +msgid "" +"Customize your dashboard. See section Customize the dashboard in the OpenStack Cloud Administrator " +"Guide." +msgstr "" + +#: ./doc/install-guide/ch_horizon.xml30(para) +msgid "" +"Set up session storage for the dashboard. See ." +msgstr "" + +#: ./doc/install-guide/section_heat-verify.xml6(title) +msgid "Verify the Orchestration service installation" +msgstr "" + +#: ./doc/install-guide/section_heat-verify.xml8(para) +msgid "" +"To verify that the Orchestration service is installed and configured " +"correctly, make sure that your credentials are set up correctly in the " +"openrc.sh file. Source the file, as follows:" +msgstr "" + +#: ./doc/install-guide/section_heat-verify.xml14(para) +msgid "Next, create some stacks by using the samples." +msgstr "" + +#: ./doc/install-guide/ch_ceilometer.xml6(title) +msgid "Add the Telemetry service" +msgstr "" + +#: ./doc/install-guide/ch_ceilometer.xml8(para) +msgid "" +"The OpenStack Telemetry service provides a framework for monitoring and " +"metering the OpenStack cloud. It is also known as the Ceilometer project." +msgstr "" + +#: ./doc/install-guide/ch_keystone.xml6(title) +msgid "Configure the Identity Service" +msgstr "" + +#: ./doc/install-guide/ch_heat.xml6(title) +msgid "Add the Orchestration service" +msgstr "" + +#: ./doc/install-guide/ch_heat.xml7(para) +msgid "" +"Use the OpenStack Orchestration service to create cloud resources using a " +"template language called HOT. The integrated project name is Heat." +msgstr "" + +#. When image changes, this message will be marked fuzzy or untranslated for +#. you. +#. It doesn't matter what you translate it to: it's not used at all. +#: ./doc/install-guide/section_debconf-rabbitqm.xml15(None) +msgid "" +"@@image: 'figures/debconf-screenshots/rabbitmq-host.png'; " +"md5=5353ad857884a2d31847cf82efbdc6b6" +msgstr "" + +#. When image changes, this message will be marked fuzzy or untranslated for +#. you. +#. It doesn't matter what you translate it to: it's not used at all. +#: ./doc/install-guide/section_debconf-rabbitqm.xml22(None) +msgid "" +"@@image: 'figures/debconf-screenshots/rabbitmq-user.png'; " +"md5=33a3c1182e79ed65f1b1b63f2156792c" +msgstr "" + +#. When image changes, this message will be marked fuzzy or untranslated for +#. you. +#. It doesn't matter what you translate it to: it's not used at all. +#: ./doc/install-guide/section_debconf-rabbitqm.xml29(None) +msgid "" +"@@image: 'figures/debconf-screenshots/rabbitmq-password.png'; " +"md5=6385185200d20e96b6316ae15ae1255d" +msgstr "" + +#: ./doc/install-guide/section_debconf-rabbitqm.xml6(title) +msgid "RabbitMQ credentials parameters" +msgstr "" + +#: ./doc/install-guide/section_debconf-rabbitqm.xml7(para) +msgid "" +"For every package that must connect to a Messaging Server, the Debian " +"package enables you to configure the IP address for that server and the user" +" name and password that is used to connect. The following example shows " +"configuration with the ceilometer-" +"common package:" +msgstr "" + +#: ./doc/install-guide/section_debconf-rabbitqm.xml33(para) +msgid "" +"These debconf screens appear in: ceilometer-" +"common, cinder-" +"common, glance-" +"common, heat-common," +" neutron-common and nova-common." +msgstr "" + +#. When image changes, this message will be marked fuzzy or untranslated for +#. you. +#. It doesn't matter what you translate it to: it's not used at all. +#: ./doc/install-guide/section_neutron-provider-router-with-private_networks.xml16(None) +#: ./doc/install-guide/ch_overview.xml101(None) +msgid "" +"@@image: '../common/figures/Neutron-PhysNet-Diagram.png'; " +"md5=ac17dba8837f9d7ba714a692c60e68ab" +msgstr "" + +#. When image changes, this message will be marked fuzzy or untranslated for +#. you. +#. It doesn't matter what you translate it to: it's not used at all. +#: ./doc/install-guide/section_neutron-provider-router-with-private_networks.xml660(None) +msgid "" +"@@image: '../common/figures/UseCase-SingleRouter.png'; " +"md5=63d21d52d32ed7fa1c1dad1a1fd88eb5" +msgstr "" + +#: ./doc/install-guide/section_neutron-provider-router-with-private_networks.xml6(title) +msgid "Provider router with private networks" +msgstr "" + +#: ./doc/install-guide/section_neutron-provider-router-with-private_networks.xml7(para) +msgid "" +"This section describes how to install the OpenStack Networking service and " +"its components for a single router use case: a provider router with private " +"networks." +msgstr "" + +#: ./doc/install-guide/section_neutron-provider-router-with-private_networks.xml10(para) +msgid "This figure shows the set up:" +msgstr "" + +#: ./doc/install-guide/section_neutron-provider-router-with-private_networks.xml21(para) +msgid "" +"Because you run the DHCP agent and L3 agent on one node, you must set " +"use_namespaces to True (which is the " +"default) in the configuration files for both agents." +msgstr "" + +#: ./doc/install-guide/section_neutron-provider-router-with-private_networks.xml26(para) +msgid "The configuration includes these nodes:" +msgstr "" + +#: ./doc/install-guide/section_neutron-provider-router-with-private_networks.xml28(caption) +msgid "Nodes for use case" +msgstr "" + +#: ./doc/install-guide/section_neutron-provider-router-with-private_networks.xml37(para) +#: ./doc/install-guide/section_neutron-provider-router-with-private_networks.xml93(title) +msgid "Controller" +msgstr "" + +#: ./doc/install-guide/section_neutron-provider-router-with-private_networks.xml38(para) +msgid "" +"Runs the Networking service, Identity Service, and all Compute services that" +" are required to deploy a VM." +msgstr "" + +#: ./doc/install-guide/section_neutron-provider-router-with-private_networks.xml41(para) +msgid "" +"The service must have at least two network interfaces. The first should be " +"connected to the Management Network to communicate with the compute and " +"network nodes. The second interface should be connected to the API/public " +"network." +msgstr "" + +#: ./doc/install-guide/section_neutron-provider-router-with-private_networks.xml49(para) +msgid "Compute" +msgstr "" + +#: ./doc/install-guide/section_neutron-provider-router-with-private_networks.xml50(para) +msgid "Runs Compute and the Networking L2 agent." +msgstr "" + +#: ./doc/install-guide/section_neutron-provider-router-with-private_networks.xml52(para) +msgid "This node does not have access the public network." +msgstr "" + +#: ./doc/install-guide/section_neutron-provider-router-with-private_networks.xml54(para) +msgid "" +"The node must have a network interface that communicates with the controller" +" node through the management network. The VM receives its IP address from " +"the DHCP agent on this network." +msgstr "" + +#: ./doc/install-guide/section_neutron-provider-router-with-private_networks.xml61(para) +msgid "Network" +msgstr "" + +#: ./doc/install-guide/section_neutron-provider-router-with-private_networks.xml62(para) +msgid "Runs Networking L2 agent, DHCP agent, and L3 agent." +msgstr "" + +#: ./doc/install-guide/section_neutron-provider-router-with-private_networks.xml64(para) +msgid "" +"This node has access to the public network. The DHCP agent allocates IP " +"addresses to the VMs on the network. The L3 agent performs NAT and enables " +"the VMs to access the public network." +msgstr "" + +#: ./doc/install-guide/section_neutron-provider-router-with-private_networks.xml71(para) +msgid "" +"A network interface that communicates with the controller node through the " +"management network" +msgstr "" + +#: ./doc/install-guide/section_neutron-provider-router-with-private_networks.xml77(para) +msgid "A network interface on the data network that manages VM traffic" +msgstr "" + +#: ./doc/install-guide/section_neutron-provider-router-with-private_networks.xml82(para) +msgid "" +"A network interface that connects to the external gateway on the network" +msgstr "" + +#: ./doc/install-guide/section_neutron-provider-router-with-private_networks.xml69(para) +msgid "The node must have:" +msgstr "" + +#: ./doc/install-guide/section_neutron-provider-router-with-private_networks.xml95(title) +msgid "To install and configure the controller node" +msgstr "" + +#: ./doc/install-guide/section_neutron-provider-router-with-private_networks.xml98(para) +#: ./doc/install-guide/section_nova-compute.xml56(para) +msgid "Run this command:" +msgstr "" + +#: ./doc/install-guide/section_neutron-provider-router-with-private_networks.xml104(para) +msgid "Configure Networking services:" +msgstr "" + +#: ./doc/install-guide/section_neutron-provider-router-with-private_networks.xml107(para) +msgid "" +"Edit the /etc/neutron/neutron.conf file and add these " +"lines:" +msgstr "" + +#: ./doc/install-guide/section_neutron-provider-router-with-private_networks.xml119(para) +#: ./doc/install-guide/section_neutron-provider-router-with-private_networks.xml338(para) +msgid "" +"Edit the " +"/etc/neutron/plugins/openvswitch/ovs_neutron_plugin.ini file and " +"add these lines:" +msgstr "" + +#: ./doc/install-guide/section_neutron-provider-router-with-private_networks.xml127(para) +msgid "" +"Edit the /etc/neutron/api-paste.ini file and add these" +" lines:" +msgstr "" + +#: ./doc/install-guide/section_neutron-provider-router-with-private_networks.xml137(para) +msgid "Start the services:" +msgstr "" + +#: ./doc/install-guide/section_neutron-provider-router-with-private_networks.xml144(title) +msgid "Network node" +msgstr "" + +#: ./doc/install-guide/section_neutron-provider-router-with-private_networks.xml146(title) +msgid "Install and configure the network node" +msgstr "" + +#. FIXME Review Fedora instructions +#: ./doc/install-guide/section_neutron-provider-router-with-private_networks.xml148(para) +#: ./doc/install-guide/section_neutron-provider-router-with-private_networks.xml287(para) +msgid "Install the packages:" +msgstr "" + +#: ./doc/install-guide/section_neutron-provider-router-with-private_networks.xml157(para) +msgid "" +"Start Open vSwitch and " +"configure it to start when the system boots:" +msgstr "" + +#: ./doc/install-guide/section_neutron-provider-router-with-private_networks.xml173(para) +msgid "" +"Update the OpenStack Networking " +"/etc/neutron/neutron.conf configuration file:" +msgstr "" + +#: ./doc/install-guide/section_neutron-provider-router-with-private_networks.xml194(para) +msgid "" +"Update the plug-in " +"/etc/neutron/plugins/openvswitch/ovs_neutron_plugin.ini" +" configuration file:" +msgstr "" + +#: ./doc/install-guide/section_neutron-provider-router-with-private_networks.xml203(para) +#: ./doc/install-guide/section_neutron-provider-router-with-private_networks.xml308(para) +msgid "" +"All VM communication between the nodes occurs through the br-" +"eth1 bridge." +msgstr "" + +#: ./doc/install-guide/section_neutron-provider-router-with-private_networks.xml206(para) +#: ./doc/install-guide/section_neutron-provider-router-with-private_networks.xml311(para) +msgid "Create the br-eth1 network bridge:" +msgstr "" + +#: ./doc/install-guide/section_neutron-provider-router-with-private_networks.xml212(para) +msgid "Create the external network bridge to the Open vSwitch:" +msgstr "" + +#: ./doc/install-guide/section_neutron-provider-router-with-private_networks.xml218(para) +msgid "" +"Edit the /etc/neutron/l3_agent.ini file and add these " +"lines:" +msgstr "" + +#: ./doc/install-guide/section_neutron-provider-router-with-private_networks.xml230(para) +msgid "" +"Edit the /etc/neutron/api-paste.ini file and add these " +"lines:" +msgstr "" + +#: ./doc/install-guide/section_neutron-provider-router-with-private_networks.xml240(para) +msgid "" +"Edit the /etc/neutron/dhcp_agent.ini file and add this " +"line:" +msgstr "" + +#: ./doc/install-guide/section_neutron-provider-router-with-private_networks.xml246(para) +msgid "Restart networking services:" +msgstr "" + +#: ./doc/install-guide/section_neutron-provider-router-with-private_networks.xml252(para) +#: ./doc/install-guide/section_neutron-provider-router-with-private_networks.xml352(para) +msgid "Start and permanently enable networking services:" +msgstr "" + +#. FIXME: Required on Debian/Ubuntu? +#: ./doc/install-guide/section_neutron-provider-router-with-private_networks.xml269(para) +msgid "" +"Enable the neutron-ovs-cleanup " +"service. This service starts on boot and ensures that Networking has full " +"control over the creation and management of tap devices." +msgstr "" + +#: ./doc/install-guide/section_neutron-provider-router-with-private_networks.xml284(title) +msgid "Install and configure the compute node" +msgstr "" + +#: ./doc/install-guide/section_neutron-provider-router-with-private_networks.xml293(para) +msgid "" +"Start the OpenvSwitch service and configure it to start when the " +"system boots:" +msgstr "" + +#: ./doc/install-guide/section_neutron-provider-router-with-private_networks.xml304(para) +msgid "Create the integration bridge:" +msgstr "" + +#: ./doc/install-guide/section_neutron-provider-router-with-private_networks.xml317(para) +msgid "" +"Edit the OpenStack Networking /etc/neutron/neutron.conf" +" configuration file and add this line:" +msgstr "" + +#: ./doc/install-guide/section_neutron-provider-router-with-private_networks.xml347(para) +msgid "Restart the OpenvSwitch Neutron plug-in agent:" +msgstr "" + +#: ./doc/install-guide/section_neutron-provider-router-with-private_networks.xml363(title) +msgid "Logical network configuration" +msgstr "" + +#: ./doc/install-guide/section_neutron-provider-router-with-private_networks.xml365(para) +msgid "Run these commands on the network node." +msgstr "" + +#: ./doc/install-guide/section_neutron-provider-router-with-private_networks.xml366(para) +#: ./doc/install-guide/section_neutron-single-flat.xml478(para) +msgid "" +"Ensure that the following environment variables are set. Various clients use" +" these variables to access the Identity Service." +msgstr "" + +#: ./doc/install-guide/section_neutron-provider-router-with-private_networks.xml372(para) +msgid "Create an adminrc file that contains these lines:" +msgstr "" + +#: ./doc/install-guide/section_neutron-provider-router-with-private_networks.xml381(para) +msgid "" +"Export the environment variables in the adminrc file:" +msgstr "" + +#: ./doc/install-guide/section_neutron-provider-router-with-private_networks.xml386(para) +msgid "" +"The admin tenant can define resources that other tenants " +"can use but cannot modify. These resources are a provider network and its " +"associated router." +msgstr "" + +#: ./doc/install-guide/section_neutron-provider-router-with-private_networks.xml390(para) +msgid "" +"The admin user creates a network and subnet on behalf of " +"tenant_A." +msgstr "" + +#: ./doc/install-guide/section_neutron-provider-router-with-private_networks.xml392(para) +msgid "A tenant_A user can also complete these steps." +msgstr "" + +#: ./doc/install-guide/section_neutron-provider-router-with-private_networks.xml395(title) +msgid "Configure internal networking" +msgstr "" + +#: ./doc/install-guide/section_neutron-provider-router-with-private_networks.xml397(para) +msgid "Get the tenant_A tenant ID:" +msgstr "" + +#: ./doc/install-guide/section_neutron-provider-router-with-private_networks.xml402(para) +msgid "" +"Create the net1 internal network for the " +"tenant_A tenant:" +msgstr "" + +#: ./doc/install-guide/section_neutron-provider-router-with-private_networks.xml423(para) +msgid "" +"Create a subnet on the net1 network and store its ID in a" +" variable:" +msgstr "" + +#: ./doc/install-guide/section_neutron-provider-router-with-private_networks.xml443(replaceable) +msgid "c395cb5d-ba03-41ee-8a12-7e792d51a167" +msgstr "" + +#: ./doc/install-guide/section_neutron-provider-router-with-private_networks.xml445(para) +#: ./doc/install-guide/section_neutron-provider-router-with-private_networks.xml473(para) +msgid "The id value will be different on your system." +msgstr "" + +#: ./doc/install-guide/section_neutron-provider-router-with-private_networks.xml450(para) +msgid "" +"A user with the admin role in the " +"admin tenant must complete these steps." +msgstr "" + +#: ./doc/install-guide/section_neutron-provider-router-with-private_networks.xml454(title) +msgid "Configure the router and external networking" +msgstr "" + +#: ./doc/install-guide/section_neutron-provider-router-with-private_networks.xml457(para) +msgid "" +"Create a router1 router and store its ID in the " +"ROUTER_ID variable:" +msgstr "" + +#: ./doc/install-guide/section_neutron-provider-router-with-private_networks.xml471(replaceable) +msgid "685f64e7-a020-4fdf-a8ad-e41194ae124b" +msgstr "" + +#: ./doc/install-guide/section_neutron-provider-router-with-private_networks.xml477(para) +msgid "" +"The --tenant-id parameter is not specified, so this " +"router is assigned to the admin tenant." +msgstr "" + +#: ./doc/install-guide/section_neutron-provider-router-with-private_networks.xml484(para) +msgid "" +"Add an interface to the router1 router and attach it to " +"the subnet from net1:" +msgstr "" + +#: ./doc/install-guide/section_neutron-provider-router-with-private_networks.xml491(para) +msgid "" +"You can repeat this step to add interfaces for networks that belong to other" +" tenants." +msgstr "" + +#: ./doc/install-guide/section_neutron-provider-router-with-private_networks.xml497(para) +msgid "" +"Create the ext_net external network and store its ID in a" +" the EXTERNAL_NETWORK_ID variable:" +msgstr "" + +#: ./doc/install-guide/section_neutron-provider-router-with-private_networks.xml519(replaceable) +msgid "8858732b-0400-41f6-8e5c-25590e67ffeb" +msgstr "" + +#: ./doc/install-guide/section_neutron-provider-router-with-private_networks.xml522(para) +msgid "Create the subnet for floating IPs." +msgstr "" + +#: ./doc/install-guide/section_neutron-provider-router-with-private_networks.xml524(para) +msgid "The DHCP service is disabled for this subnet." +msgstr "" + +#: ./doc/install-guide/section_neutron-provider-router-with-private_networks.xml547(para) +msgid "Set the gateway for the router to the external network:" +msgstr "" + +#: ./doc/install-guide/section_neutron-provider-router-with-private_networks.xml553(para) +msgid "" +"A user from tenant_A completes these steps, so the " +"credentials in the environment variables are different than those in the " +"previous procedure." +msgstr "" + +#: ./doc/install-guide/section_neutron-provider-router-with-private_networks.xml557(title) +msgid "Allocate floating IP addresses" +msgstr "" + +#: ./doc/install-guide/section_neutron-provider-router-with-private_networks.xml559(para) +msgid "" +"You can associate a floating IP address with a VM after it starts. Store the" +" port ID that was allocated for the VM in the PORT_ID " +"variable:" +msgstr "" + +#: ./doc/install-guide/section_neutron-provider-router-with-private_networks.xml569(replaceable) +msgid "1cdc671d-a296-4476-9a75-f9ca1d92fd26" +msgstr "" + +#: ./doc/install-guide/section_neutron-provider-router-with-private_networks.xml575(replaceable) +msgid "9aa47099-b87b-488c-8c1d-32f993626a30" +msgstr "" + +#: ./doc/install-guide/section_neutron-provider-router-with-private_networks.xml578(para) +msgid "" +"Allocate a floating IP and store its ID in the " +"FLOATING_ID variable:" +msgstr "" + +#: ./doc/install-guide/section_neutron-provider-router-with-private_networks.xml593(replaceable) +msgid "7.7.7.131" +msgstr "" + +#: ./doc/install-guide/section_neutron-provider-router-with-private_networks.xml596(para) +msgid "Associate the floating IP with the port for the VM:" +msgstr "" + +#: ./doc/install-guide/section_neutron-provider-router-with-private_networks.xml602(para) +msgid "Show the floating IP:" +msgstr "" + +#: ./doc/install-guide/section_neutron-provider-router-with-private_networks.xml617(para) +msgid "Test the floating IP:" +msgstr "" + +#: ./doc/install-guide/section_neutron-provider-router-with-private_networks.xml626(title) +msgid "Use case: provider router with private networks" +msgstr "" + +#: ./doc/install-guide/section_neutron-provider-router-with-private_networks.xml627(para) +msgid "" +"This use case provides each tenant with one or more private networks that " +"connect to the outside world through an OpenStack Networking router. When " +"each tenant gets exactly one network, this architecture maps to the same " +"logical topology as the VlanManager in Compute (although of course, " +"Networking does not require VLANs). Using the Networking API, the tenant can" +" only see a network for each private network assigned to that tenant. The " +"router object in the API is created and owned by the cloud administrator." +msgstr "" + +#: ./doc/install-guide/section_neutron-provider-router-with-private_networks.xml637(para) +msgid "" +"This model supports assigning public addresses to VMs by using floating IPs; the router maps public " +"addresses from the external network to fixed IPs on private networks. Hosts " +"without floating IPs can still create outbound connections to the external " +"network because the provider router performs SNAT to the router's external " +"IP. The IP address of the physical router is used as the " +"gateway_ip of the external network subnet, so the " +"provider has a default router for Internet traffic." +msgstr "" + +#: ./doc/install-guide/section_neutron-provider-router-with-private_networks.xml648(para) +msgid "" +"The router provides L3 connectivity among private networks. Tenants can " +"reach instances for other tenants unless you use additional filtering, such " +"as, security groups). With a single router, tenant networks cannot use " +"overlapping IPs. To resolve this issue, the administrator can create private" +" networks on behalf of the tenants." +msgstr "" + +#: ./doc/install-guide/ch_nova.xml7(title) +msgid "Configure Compute services" +msgstr "" + +#: ./doc/install-guide/section_ceilometer-cinder.xml7(title) +msgid "Add the Block Storage Service agent for the Telemetry service" +msgstr "" + +#: ./doc/install-guide/section_ceilometer-cinder.xml11(para) +msgid "" +"To retrieve volume samples, you must configure the Block Storage Service to " +"send notifications to the bus." +msgstr "" + +#: ./doc/install-guide/section_ceilometer-cinder.xml14(para) +msgid "" +"Edit /etc/cinder/cinder.conf and add in the " +"[DEFAULT] section:" +msgstr "" + +#: ./doc/install-guide/section_ceilometer-cinder.xml19(para) +#: ./doc/install-guide/section_ceilometer-glance.xml20(para) +#: ./doc/install-guide/section_heat-install.xml94(para) +msgid "Run the following commands:" +msgstr "" + +#: ./doc/install-guide/section_ceilometer-cinder.xml25(para) +msgid "Restart the Block Storage services with their new settings:" +msgstr "" + +#: ./doc/install-guide/section_nova-network.xml5(title) +msgid "Configure networking" +msgstr "" + +#: ./doc/install-guide/section_nova-network.xml6(para) +msgid "" +"Configuring networking in OpenStack can be a bewildering experience. The " +"following example shows the simplest production-ready configuration that is " +"available: the legacy networking in OpenStack Compute, with a flat network, " +"that takes care of DHCP." +msgstr "" + +#: ./doc/install-guide/section_nova-network.xml11(para) +msgid "" +"This set up uses multi-host functionality. Networking is configured to be " +"highly available by distributing networking functionality across multiple " +"hosts. As a result, no single network controller acts as a single point of " +"failure. This process configures each compute node for networking." +msgstr "" + +#: ./doc/install-guide/section_nova-network.xml17(para) +msgid "Choose one of these options to configure networking in OpenStack:" +msgstr "" + +#: ./doc/install-guide/section_nova-network.xml20(para) +msgid "Legacy networking in OpenStack Compute, which is described here." +msgstr "" + +#: ./doc/install-guide/section_nova-network.xml24(para) +msgid "" +"The full software-defined networking stack. See ." +msgstr "" + +#: ./doc/install-guide/section_nova-network.xml31(para) +msgid "" +"Install the appropriate packages for compute networking on the compute node " +"only. These packages are not required on the controller node." +msgstr "" + +#: ./doc/install-guide/section_nova-network.xml34(para) +msgid "" +"So that the nova-network service " +"can forward metadata requests on each compute node, each compute node must " +"install the nova-api-metadata " +"service, as follows:" +msgstr "" + +#: ./doc/install-guide/section_nova-network.xml44(para) +msgid "" +"Edit the nova.conf file to define the networking mode:" +msgstr "" + +#: ./doc/install-guide/section_nova-network.xml81(para) +msgid "" +"Provide a local metadata service that is reachable from instances on this " +"compute node. Perform this step only on compute nodes that do not run the " +"nova-api service." +msgstr "" + +#: ./doc/install-guide/section_nova-network.xml90(para) +msgid "Restart the network service:" +msgstr "" + +#: ./doc/install-guide/section_nova-network.xml92(para) +msgid "" +"Start the network service and configure it to start when the system boots:" +msgstr "" + +#: ./doc/install-guide/section_nova-network.xml99(para) +msgid "" +"Create a network that virtual machines can use. Do this once for the entire " +"installation and not on each compute node. Run the command " +"on the controller:" +msgstr "" + +#: ./doc/install-guide/app_reserved_uids.xml6(title) +#: ./doc/install-guide/app_reserved_uids.xml24(caption) +msgid "Reserved user IDs" +msgstr "" + +#: ./doc/install-guide/app_reserved_uids.xml8(para) +msgid "" +"In OpenStack, certain user IDs are reserved and used to run specific " +"OpenStack services and own specific OpenStack files. These users are set up " +"according to the distribution packages. The following table gives an " +"overview." +msgstr "" + +#: ./doc/install-guide/app_reserved_uids.xml16(para) +msgid "" +"Some OpenStack packages generate and assign user IDs automatically during " +"package installation. In these cases, the user ID value is not important. " +"The existence of the user ID is what matters." +msgstr "" + +#: ./doc/install-guide/app_reserved_uids.xml27(th) +msgid "Name" +msgstr "" + +#: ./doc/install-guide/app_reserved_uids.xml35(td) +msgid "ceilometer" +msgstr "" + +#: ./doc/install-guide/app_reserved_uids.xml36(td) +msgid "openstack-ceilometer" +msgstr "" + +#: ./doc/install-guide/app_reserved_uids.xml37(td) +msgid "OpenStack Ceilometer Daemons" +msgstr "" + +#: ./doc/install-guide/app_reserved_uids.xml38(td) +msgid "166" +msgstr "" + +#: ./doc/install-guide/app_reserved_uids.xml39(td) +#: ./doc/install-guide/app_reserved_uids.xml46(td) +#: ./doc/install-guide/app_reserved_uids.xml53(td) +#: ./doc/install-guide/app_reserved_uids.xml60(td) +#: ./doc/install-guide/app_reserved_uids.xml67(td) +#: ./doc/install-guide/app_reserved_uids.xml74(td) +#: ./doc/install-guide/app_reserved_uids.xml82(td) +#: ./doc/install-guide/app_reserved_uids.xml89(td) +msgid "Assigned during package installation" +msgstr "" + +#: ./doc/install-guide/app_reserved_uids.xml42(td) +msgid "cinder" +msgstr "" + +#: ./doc/install-guide/app_reserved_uids.xml43(td) +msgid "openstack-cinder" +msgstr "" + +#: ./doc/install-guide/app_reserved_uids.xml44(td) +msgid "OpenStack Cinder Daemons" +msgstr "" + +#: ./doc/install-guide/app_reserved_uids.xml45(td) +msgid "165" +msgstr "" + +#: ./doc/install-guide/app_reserved_uids.xml49(td) +msgid "glance" +msgstr "" + +#: ./doc/install-guide/app_reserved_uids.xml50(td) +msgid "openstack-glance" +msgstr "" + +#: ./doc/install-guide/app_reserved_uids.xml51(td) +msgid "OpenStack Glance Daemons" +msgstr "" + +#: ./doc/install-guide/app_reserved_uids.xml52(td) +msgid "161" +msgstr "" + +#: ./doc/install-guide/app_reserved_uids.xml56(td) +msgid "heat" +msgstr "" + +#: ./doc/install-guide/app_reserved_uids.xml57(td) +msgid "openstack-heat" +msgstr "" + +#: ./doc/install-guide/app_reserved_uids.xml58(td) +msgid "OpenStack Heat Daemons" +msgstr "" + +#: ./doc/install-guide/app_reserved_uids.xml59(td) +msgid "187" +msgstr "" + +#: ./doc/install-guide/app_reserved_uids.xml63(td) +msgid "keystone" +msgstr "" + +#: ./doc/install-guide/app_reserved_uids.xml64(td) +msgid "openstack-keystone" +msgstr "" + +#: ./doc/install-guide/app_reserved_uids.xml65(td) +msgid "OpenStack Keystone Daemons" +msgstr "" + +#: ./doc/install-guide/app_reserved_uids.xml66(td) +msgid "163" +msgstr "" + +#: ./doc/install-guide/app_reserved_uids.xml70(td) +msgid "neutron" +msgstr "" + +#: ./doc/install-guide/app_reserved_uids.xml71(td) +msgid "openstack-neutron" +msgstr "" + +#: ./doc/install-guide/app_reserved_uids.xml72(td) +msgid "OpenStack Neutron Daemons" +msgstr "" + +#: ./doc/install-guide/app_reserved_uids.xml73(td) +msgid "164" +msgstr "" + +#: ./doc/install-guide/app_reserved_uids.xml77(td) +msgid "nova" +msgstr "" + +#: ./doc/install-guide/app_reserved_uids.xml78(td) +msgid "openstack-nova" +msgstr "" + +#: ./doc/install-guide/app_reserved_uids.xml79(td) +msgid "OpenStack Nova Daemons" +msgstr "" + +#: ./doc/install-guide/app_reserved_uids.xml80(td) +msgid "162" +msgstr "" + +#: ./doc/install-guide/app_reserved_uids.xml81(td) +msgid "96" +msgstr "" + +#: ./doc/install-guide/app_reserved_uids.xml85(td) +msgid "swift" +msgstr "" + +#: ./doc/install-guide/app_reserved_uids.xml86(td) +msgid "openstack-swift" +msgstr "" + +#: ./doc/install-guide/app_reserved_uids.xml87(td) +msgid "OpenStack Swift Daemons" +msgstr "" + +#: ./doc/install-guide/app_reserved_uids.xml88(td) +msgid "160" +msgstr "" + +#: ./doc/install-guide/app_reserved_uids.xml93(para) +msgid "Each user belongs to a user group with the same name as the user." +msgstr "" + +#: ./doc/install-guide/ch_preface.xml10(title) +msgid "Preface" +msgstr "" + +#: ./doc/install-guide/section_ceilometer-glance.xml6(title) +msgid "Add the Image Service agent for the Telemetry service" +msgstr "" + +#: ./doc/install-guide/section_ceilometer-glance.xml9(para) +msgid "" +"To retrieve image samples, you must configure the Image Service to send " +"notifications to the bus." +msgstr "" + +#: ./doc/install-guide/section_ceilometer-glance.xml12(para) +msgid "" +"Edit /etc/glance/glance-api.conf and modify the " +"[DEFAULT] section:" +msgstr "" + +#: ./doc/install-guide/section_ceilometer-glance.xml31(para) +msgid "Restart the Image services with their new settings:" +msgstr "" + +#: ./doc/install-guide/section_debconf-concepts.xml7(title) +msgid "debconf concepts" +msgstr "" + +#: ./doc/install-guide/section_debconf-concepts.xml8(para) +msgid "" +"This chapter explains how to use the Debian debconf and dbconfig-common packages to configure OpenStack services. " +"These packages enable users to perform configuration tasks. When users " +"install OpenStack packages, debconf prompts the user for " +"responses, which seed the contents of configuration files associated with " +"that package. After package installation, users can update the configuration" +" of a package by using the program." +msgstr "" + +#: ./doc/install-guide/section_debconf-concepts.xml18(para) +msgid "" +"If you are familiar with these packages and pre-seeding, you can proceed to " +"." +msgstr "" + +#: ./doc/install-guide/section_debconf-concepts.xml21(title) +msgid "The Debian packages" +msgstr "" + +#: ./doc/install-guide/section_debconf-concepts.xml22(para) +msgid "" +"The rules described here are from the Debian Policy Manual. If any" +" rule described in this chapter is not respected, you have found a serious " +"bug that must be fixed." +msgstr "" + +#: ./doc/install-guide/section_debconf-concepts.xml27(para) +msgid "" +"When you install or upgrade a Debian package, all configuration file values " +"are preserved. Using the debconf " +"database as a registry is considered a bug in Debian. If you edit something " +"in any OpenStack configuration file, the debconf package reads that value when it " +"prepares to prompt the user. For example, to change the log in name for the " +"RabbitMQ messaging queue for a service, you can edit its value in the " +"corresponding configuration file." +msgstr "" + +#: ./doc/install-guide/section_debconf-concepts.xml36(para) +msgid "" +"To opt out of using the debconf " +"package, run the command and select non-interactive mode:" +msgstr "" + +#: ./doc/install-guide/section_debconf-concepts.xml41(para) +msgid "" +"Then, debconf does not prompt " +"you." +msgstr "" + +#: ./doc/install-guide/section_debconf-concepts.xml43(para) +msgid "" +"Another way to disable the debconf package is to prefix the " +" command with " +"DEBIAN_FRONTEND=noninteractive, as follows:" +msgstr "" + +#: ./doc/install-guide/section_debconf-concepts.xml49(para) +msgid "" +"If you configure a package with debconf incorrectly, you can re-configure it," +" as follows:" +msgstr "" + +#: ./doc/install-guide/section_debconf-concepts.xml52(replaceable) +msgid "PACKAGE-NAME" +msgstr "" + +#: ./doc/install-guide/section_debconf-concepts.xml53(para) +msgid "" +"This calls the post-installation script for the PACKAGE-" +"NAME package after the user responds to all prompts. If you " +"cannot install a Debian package in a non-interactive way, you have found a " +"release-critical bug in Debian. Report it to the Debian bug tracking system." +msgstr "" + +#: ./doc/install-guide/section_debconf-concepts.xml58(para) +msgid "" +"Generally, the -common packages " +"install the configuration files. For example, the glance-" +"common package installs the glance-api.conf " +"and glance-registry.conf files. So, for the Image " +"Service, you must re-configure the glance-common package." +" The same applies for cinder-common, nova-" +"common, and heat-common packages." +msgstr "" + +#: ./doc/install-guide/section_debconf-concepts.xml68(para) +msgid "" +"In debconf, the higher the " +"priority for a screen, the greater the chance that the user sees that " +"screen. If a debconf screen has " +"medium priority and you configure the Debian system to " +"show only critical prompts, which is the default in " +"Debian, the user does not see that debconf screen. Instead, the default for the " +"related package is used. In the Debian OpenStack packages, a number of " +"debconf screens are set with " +"medium priority. Consequently, if you want to respond to " +"all debconf screens from the " +"Debian OpenStack packages, you must run the following command and select the" +" medium priority before you install any packages:" +msgstr "" + +#: ./doc/install-guide/section_debconf-concepts.xml87(para) +msgid "" +"The packages do not require pre-depends. If dbconfig-common is already installed on the system, the user" +" sees all prompts. However, you cannot define the order in which the " +"debconf screens appear. The user " +"must make sense of it even if the prompts appear in an illogical order." +msgstr "" + +#: ./doc/install-guide/section_ceilometer-swift.xml6(title) +msgid "Add the Object Storage agent for the Telemetry service" +msgstr "" + +#: ./doc/install-guide/section_ceilometer-swift.xml9(para) +msgid "" +"To retrieve object store statistics, the Telemetry service needs access to " +"Object Storage with the ResellerAdmin role. Give this " +"role to your os_username user for the " +"os_tenant_name tenant:" +msgstr "" + +#: ./doc/install-guide/section_ceilometer-swift.xml23(replaceable) +msgid "462fa46c13fd4798a95a3bfbe27b5e54" +msgstr "" + +#: ./doc/install-guide/section_ceilometer-swift.xml26(para) +msgid "" +"You must also add the Telemetry middleware to Object Storage to handle " +"incoming and outgoing traffic. Add these lines to the /etc/swift" +"/proxy-server.conf file:" +msgstr "" + +#: ./doc/install-guide/section_ceilometer-swift.xml35(para) +msgid "" +"Add ceilometer to the pipeline " +"parameter of that same file:" +msgstr "" + +#: ./doc/install-guide/section_ceilometer-swift.xml41(para) +#: ./doc/install-guide/section_heat-install.xml145(para) +#: ./doc/install-guide/section_ceilometer-nova.xml136(para) +msgid "Restart the service with its new settings:" +msgstr "" + +#: ./doc/install-guide/section_debconf-preseeding.xml6(title) +msgid "Pre-seed debconf prompts" +msgstr "" + +#: ./doc/install-guide/section_debconf-preseeding.xml7(para) +msgid "" +"You can pre-seed all debconf " +"prompts. To pre-seed means to store responses in the " +"debconf database so that debconf does " +"not prompt the user for responses. Pre-seeding enables a hands-free " +"installation for users. The package maintainer creates scripts that " +"automatically configure the services." +msgstr "" + +#: ./doc/install-guide/section_debconf-preseeding.xml14(para) +msgid "" +"The following example shows how to pre-seed an automated MySQL Server " +"installation:" +msgstr "" + +#: ./doc/install-guide/section_debconf-preseeding.xml16(replaceable) +#: ./doc/install-guide/section_debconf-preseeding.xml17(replaceable) +#: ./doc/install-guide/section_debconf-preseeding.xml19(replaceable) +msgid "MYSQL_PASSWORD" +msgstr "" + +#: ./doc/install-guide/section_debconf-preseeding.xml23(para) +msgid "" +"The seen true option tells debconf that a " +"specified screen was already seen by the user so do not show it again. This " +"option is useful for upgrades." +msgstr "" + +#. When image changes, this message will be marked fuzzy or untranslated for +#. you. +#. It doesn't matter what you translate it to: it's not used at all. +#: ./doc/install-guide/section_neutron-single-flat.xml22(None) +msgid "" +"@@image: '../common/figures/demo_flat_install.png'; " +"md5=27b45d5871859ff4951c92df7c8763d8" +msgstr "" + +#. When image changes, this message will be marked fuzzy or untranslated for +#. you. +#. It doesn't matter what you translate it to: it's not used at all. +#: ./doc/install-guide/section_neutron-single-flat.xml621(None) +msgid "" +"@@image: '../common/figures/UseCase-SingleFlat.png'; " +"md5=bdd61f2967fb1a55e4f50d766db7b113" +msgstr "" + +#. When image changes, this message will be marked fuzzy or untranslated for +#. you. +#. It doesn't matter what you translate it to: it's not used at all. +#: ./doc/install-guide/section_neutron-single-flat.xml637(None) +msgid "" +"@@image: '../common/figures/UseCase-MultiFlat.png'; " +"md5=289e38a7a13a2a4413e5a1e62ce55b3e" +msgstr "" + +#. When image changes, this message will be marked fuzzy or untranslated for +#. you. +#. It doesn't matter what you translate it to: it's not used at all. +#: ./doc/install-guide/section_neutron-single-flat.xml659(None) +msgid "" +"@@image: '../common/figures/UseCase-MixedFlatPrivate.png'; " +"md5=8da4ceb5a1e5a2357394478645af7449" +msgstr "" + +#: ./doc/install-guide/section_neutron-single-flat.xml6(title) +msgid "Single flat network" +msgstr "" + +#: ./doc/install-guide/section_neutron-single-flat.xml7(para) +msgid "" +"This section describes how to install the OpenStack Networking service and " +"its components for a single flat network use case." +msgstr "" + +#: ./doc/install-guide/section_neutron-single-flat.xml10(para) +msgid "" +"The following diagram shows the set up. For simplicity, all nodes should " +"have one interface for management traffic and one or more interfaces for " +"traffic to and from VMs. The management network is 100.1.1.0/24 with " +"controller node at 100.1.1.2. The example uses the Open vSwitch plugin and " +"agent." +msgstr "" + +#: ./doc/install-guide/section_neutron-single-flat.xml16(para) +msgid "" +"You can modify this set up to make use of another supported plug-in and its " +"agent." +msgstr "" + +#: ./doc/install-guide/section_neutron-single-flat.xml25(para) +msgid "The following table describes some nodes in the set up:" +msgstr "" + +#: ./doc/install-guide/section_neutron-single-flat.xml39(para) +msgid "" +"Runs the Networking service, Identity Service, and Compute services that are" +" required to deploy VMs (nova-" +"api, nova-scheduler," +" for example). The node must have at least one network interface, which is " +"connected to the Management Network. The host name is " +"controller, which every other node resolves to the IP of " +"the controller node." +msgstr "" + +#: ./doc/install-guide/section_neutron-single-flat.xml52(para) +msgid "" +"The nova-network service should " +"not be running. This is replaced by the OpenStack Networking component, " +"neutron. To delete a network, run" +" this command:" +msgstr "" + +#: ./doc/install-guide/section_neutron-single-flat.xml64(para) +msgid "" +"Note that a network must first be disassociated from a project using the " +"nova network-disassociate command before it can be deleted." +msgstr "" + +#: ./doc/install-guide/section_neutron-single-flat.xml71(td) +msgid "" +"Runs the Networking L2 agent and the Compute services that run VMs " +"( specifically, and optionally other nova-* services " +"depending on configuration). The node must have at least two network " +"interfaces. The first communicates with the controller node through the " +"management network. The second interface handles the VM traffic on the data " +"network. The VM can receive its IP address from the DHCP agent on this " +"network." +msgstr "" + +#: ./doc/install-guide/section_neutron-single-flat.xml85(td) +msgid "" +"Runs Networking L2 agent and the DHCP agent. The DHCP agent allocates IP " +"addresses to the VMs on the network. The node must have at least two network" +" interfaces. The first communicates with the controller node through the " +"management network. The second interface handles the VM traffic on the data " +"network." +msgstr "" + +#: ./doc/install-guide/section_neutron-single-flat.xml101(para) +msgid "The demo assumes the following prerequisites:" +msgstr "" + +#: ./doc/install-guide/section_neutron-single-flat.xml109(para) +msgid "" +"Glance is installed, configured, and running. Additionally, an image must be" +" available." +msgstr "" + +#: ./doc/install-guide/section_neutron-single-flat.xml113(para) +msgid "" +"OpenStack Identity is installed, configured, and running. A Networking user " +"neutron is in place on tenant service with password " +"NEUTRON_PASS." +msgstr "" + +#: ./doc/install-guide/section_neutron-single-flat.xml121(para) +msgid "Additional services:" +msgstr "" + +#: ./doc/install-guide/section_neutron-single-flat.xml124(para) +msgid "" +"RabbitMQ is running with the default guest user and password " +"RABBIT_PASS." +msgstr "" + +#: ./doc/install-guide/section_neutron-single-flat.xml129(para) +msgid "Qpid is running with the default guest user and password." +msgstr "" + +#: ./doc/install-guide/section_neutron-single-flat.xml142(para) +msgid "Compute is installed and configured." +msgstr "" + +#: ./doc/install-guide/section_neutron-single-flat.xml155(para) +msgid "" +"Install the Networking server and respond to debconf prompts to configure the database, " +"the keystone_authtoken, and the RabbitMQ credentials." +msgstr "" + +#: ./doc/install-guide/section_neutron-single-flat.xml162(para) +msgid "" +"See for " +"installation instructions." +msgstr "" + +#: ./doc/install-guide/section_neutron-single-flat.xml171(para) +msgid "" +"See for database creation " +"details." +msgstr "" + +#: ./doc/install-guide/section_neutron-single-flat.xml177(para) +msgid "" +"If not already configured, update the Networking " +"/etc/neutron/neutron.conf configuration file to use the Identity " +"Service, the plug-in, and database configuration:" +msgstr "" + +#: ./doc/install-guide/section_neutron-single-flat.xml191(para) +#: ./doc/install-guide/section_neutron-install.xml332(para) +#: ./doc/install-guide/section_neutron-install.xml910(para) +#: ./doc/install-guide/section_neutron-install.xml1218(para) +msgid "Configure Networking to connect to the database:" +msgstr "" + +#: ./doc/install-guide/section_neutron-single-flat.xml194(para) +#: ./doc/install-guide/section_neutron-single-flat.xml347(para) +msgid "Configure Networking to use your chosen plug-in:" +msgstr "" + +#: ./doc/install-guide/section_neutron-single-flat.xml199(para) +#: ./doc/install-guide/section_neutron-single-flat.xml352(para) +#: ./doc/install-guide/section_neutron-single-flat.xml436(para) +#: ./doc/install-guide/section_neutron-install.xml299(para) +#: ./doc/install-guide/section_neutron-install.xml863(para) +#: ./doc/install-guide/section_neutron-install.xml1314(para) +msgid "Configure access to the RabbitMQ service:" +msgstr "" + +#: ./doc/install-guide/section_neutron-single-flat.xml208(para) +#: ./doc/install-guide/section_neutron-single-flat.xml361(para) +#: ./doc/install-guide/section_neutron-single-flat.xml445(para) +#: ./doc/install-guide/section_neutron-install.xml319(para) +#: ./doc/install-guide/section_neutron-install.xml874(para) +#: ./doc/install-guide/section_neutron-install.xml1325(para) +msgid "Configure access to the Qpid message queue:" +msgstr "" + +#: ./doc/install-guide/section_neutron-single-flat.xml216(replaceable) +#: ./doc/install-guide/section_neutron-single-flat.xml218(replaceable) +#: ./doc/install-guide/section_neutron-single-flat.xml369(replaceable) +#: ./doc/install-guide/section_neutron-single-flat.xml371(replaceable) +#: ./doc/install-guide/section_neutron-single-flat.xml453(replaceable) +#: ./doc/install-guide/section_neutron-single-flat.xml455(replaceable) +#: ./doc/install-guide/section_neutron-install.xml327(replaceable) +#: ./doc/install-guide/section_neutron-install.xml329(replaceable) +#: ./doc/install-guide/section_neutron-install.xml882(replaceable) +#: ./doc/install-guide/section_neutron-install.xml884(replaceable) +#: ./doc/install-guide/section_neutron-install.xml1333(replaceable) +#: ./doc/install-guide/section_neutron-install.xml1335(replaceable) +msgid "guest" +msgstr "" + +#: ./doc/install-guide/section_neutron-single-flat.xml221(para) +msgid "" +"If not already configured, update the Networking " +"/etc/neutron/neutron.conf configuration file to choose a plug-in " +"and Identity Service user as necessary:" +msgstr "" + +#: ./doc/install-guide/section_neutron-single-flat.xml243(para) +msgid "" +"Update the plug-in " +"/etc/neutron/plugins/openvswitch/ovs_neutron_plugin.ini " +"configuration file with the bridge mappings:" +msgstr "" + +#: ./doc/install-guide/section_neutron-single-flat.xml258(para) +msgid "Restart the Networking service:" +msgstr "" + +#: ./doc/install-guide/section_neutron-single-flat.xml265(emphasis) +msgid "Compute node - Compute" +msgstr "" + +#: ./doc/install-guide/section_neutron-single-flat.xml267(para) +msgid "" +"Install the nova-compute service." +msgstr "" + +#: ./doc/install-guide/section_neutron-single-flat.xml271(para) +msgid "See for installation instructions." +msgstr "" + +#: ./doc/install-guide/section_neutron-single-flat.xml276(para) +msgid "" +"Update the Compute /etc/nova/nova.conf configuration " +"file to make use of OpenStack Networking:" +msgstr "" + +#: ./doc/install-guide/section_neutron-single-flat.xml304(para) +msgid "Restart the Compute services" +msgstr "" + +#: ./doc/install-guide/section_neutron-single-flat.xml311(emphasis) +msgid "Compute and Network node - L2 agent" +msgstr "" + +#: ./doc/install-guide/section_neutron-single-flat.xml314(para) +msgid "" +"Install and start Open vSwitch. Then, configure neutron accordingly." +msgstr "" + +#: ./doc/install-guide/section_neutron-single-flat.xml316(para) +msgid "" +"See for detailed " +"instructions." +msgstr "" + +#: ./doc/install-guide/section_neutron-single-flat.xml321(para) +msgid "Add the integration bridge to Open vSwitch:" +msgstr "" + +#: ./doc/install-guide/section_neutron-single-flat.xml326(para) +#: ./doc/install-guide/section_neutron-single-flat.xml418(para) +msgid "" +"Update the Networking /etc/neutron/neutron.conf " +"configuration file:" +msgstr "" + +#: ./doc/install-guide/section_neutron-single-flat.xml341(para) +msgid "" +"If not already configured, update the Networking " +"/etc/neutron/neutron.conf configuration file to use the plug-in, " +"message queue, and database configuration:" +msgstr "" + +#: ./doc/install-guide/section_neutron-single-flat.xml374(para) +msgid "" +"Update the plug-in " +"/etc/neutron/plugins/openvswitch/ovs_neutron_plugin.ini " +"configuration file:" +msgstr "" + +#: ./doc/install-guide/section_neutron-single-flat.xml388(para) +msgid "" +"Create a symbolic link from /etc/neutron/plugin.ini to " +"/etc/neutron/plugins/openvswitch/ovs_neutron_plugin.ini" +" or neutron-server will not run:" +msgstr "" + +#: ./doc/install-guide/section_neutron-single-flat.xml393(para) +msgid "" +"Create the br-eth0 network bridge to " +"handle communication between nodes using eth0:" +msgstr "" + +#: ./doc/install-guide/section_neutron-single-flat.xml401(para) +msgid "Restart the OpenStack Networking L2 agent:" +msgstr "" + +#: ./doc/install-guide/section_neutron-single-flat.xml409(emphasis) +msgid "Network node - DHCP agent" +msgstr "" + +#: ./doc/install-guide/section_neutron-single-flat.xml413(para) +msgid "" +"See for generic installation instructions." +msgstr "" + +#: ./doc/install-guide/section_neutron-single-flat.xml429(para) +msgid "" +"If not already configured, update the Networking " +"/etc/neutron/neutron.conf configuration file to use the plug-in " +"and message queue." +msgstr "" + +#: ./doc/install-guide/section_neutron-single-flat.xml458(para) +msgid "" +"Ensure that the DHCP agent is using the correct plug-in my changing the " +"configuration in /etc/neutron/dhcp_agent.ini:" +msgstr "" + +#: ./doc/install-guide/section_neutron-single-flat.xml466(para) +msgid "Restart the DHCP agent:" +msgstr "" + +#: ./doc/install-guide/section_neutron-single-flat.xml476(para) +msgid "Use the following commands on the network node." +msgstr "" + +#: ./doc/install-guide/section_neutron-single-flat.xml502(para) +msgid "Get the user information:" +msgstr "" + +#: ./doc/install-guide/section_neutron-single-flat.xml515(para) +msgid "" +"Create a internal shared network on the demo tenant ($TENANT_ID is " +"b7445f221cda4f4a8ac7db6b218b1339):" +msgstr "" + +#: ./doc/install-guide/section_neutron-single-flat.xml538(para) +msgid "Create a subnet on the network:" +msgstr "" + +#: ./doc/install-guide/section_neutron-single-flat.xml558(para) +msgid "Create a server for tenant A:" +msgstr "" + +#: ./doc/install-guide/section_neutron-single-flat.xml571(para) +msgid "Ping the server of tenant A:" +msgstr "" + +#: ./doc/install-guide/section_neutron-single-flat.xml577(para) +msgid "Ping the public network within the server of tenant A:" +msgstr "" + +#: ./doc/install-guide/section_neutron-single-flat.xml589(para) +msgid "" +"The 192.168.1.1 is an IP on public network to which the router connects." +msgstr "" + +#: ./doc/install-guide/section_neutron-single-flat.xml594(para) +msgid "" +"Create servers for other tenants with similar commands. Because all VMs " +"share the same subnet, they can access each other." +msgstr "" + +#: ./doc/install-guide/section_neutron-single-flat.xml601(title) +msgid "Use case: single flat network" +msgstr "" + +#: ./doc/install-guide/section_neutron-single-flat.xml602(para) +msgid "" +"The simplest use case is a single network. This is a \"shared\" network, " +"meaning it is visible to all tenants via the Networking API. Tenant VMs have" +" a single NIC, and receive a fixed IP address from the subnet(s) associated " +"with that network. This use case essentially maps to the FlatManager and " +"FlatDHCPManager models provided by Compute. Floating IPs are not supported." +msgstr "" + +#: ./doc/install-guide/section_neutron-single-flat.xml609(para) +msgid "" +"This network type is often created by the OpenStack administrator to map " +"directly to an existing physical network in the data center (called a " +"\"provider network\"). This allows the provider to use a physical router on " +"that data center network as the gateway for VMs to reach the outside world. " +"For each subnet on an external network, the gateway configuration on the " +"physical router must be manually configured outside of OpenStack." +msgstr "" + +#: ./doc/install-guide/section_neutron-single-flat.xml628(title) +msgid "Use case: multiple flat network" +msgstr "" + +#: ./doc/install-guide/section_neutron-single-flat.xml629(para) +msgid "" +"This use case is similar to the above single flat network use case, except " +"that tenants can see multiple shared networks via the Networking API and can" +" choose which network (or networks) to plug into." +msgstr "" + +#: ./doc/install-guide/section_neutron-single-flat.xml643(title) +msgid "Use case: mixed flat and private network" +msgstr "" + +#: ./doc/install-guide/section_neutron-single-flat.xml644(para) +msgid "" +"This use case is an extension of the above Flat Network use cases. In " +"addition to being able to see one or more shared networks via the OpenStack " +"Networking API, tenants can also have access to private per-tenant networks " +"(only visible to tenant users)." +msgstr "" + +#: ./doc/install-guide/section_neutron-single-flat.xml649(para) +msgid "" +"Created VMs can have NICs on any of the shared or private networks that the " +"tenant owns. This enables the creation of multi-tier topologies that use VMs" +" with multiple NICs. It also enables a VM to act as a gateway so that it can" +" provide services such as routing, NAT, and load balancing." +msgstr "" + +#: ./doc/install-guide/ch_neutron.xml6(title) +msgid "Install the Networking service" +msgstr "" + +#: ./doc/install-guide/ch_neutron.xml9(para) +msgid "" +"This chapter is a bit more adventurous than we would like. We are working on" +" cleanup and improvements to it. Like for the rest of the Installation " +"Guide, feedback through bug reports and patches to improve it are welcome." +msgstr "" + +#: ./doc/install-guide/ch_neutron.xml16(title) +msgid "Networking considerations" +msgstr "" + +#: ./doc/install-guide/ch_neutron.xml17(para) +msgid "" +"OpenStack Networking drivers range from software bridges to full control of " +"certain switching hardware. This guide focuses on the Open vSwitch driver. " +"However, the theories presented here are mostly applicable to other " +"mechanisms, and the Networking chapter of the OpenStack " +"Configuration Reference offers additional information." +msgstr "" + +#: ./doc/install-guide/ch_neutron.xml26(para) +msgid "To prepare for installation, see ." +msgstr "" + +#: ./doc/install-guide/ch_neutron.xml29(para) +msgid "" +"If you previously set up networking for your compute node by using " +"nova-network, this configuration " +"overrides those settings." +msgstr "" + +#. When image changes, this message will be marked fuzzy or untranslated for +#. you. +#. It doesn't matter what you translate it to: it's not used at all. +#: ./doc/install-guide/ch_basics.xml123(None) +msgid "" +"@@image: 'figures/basic-architecture-networking.svg'; " +"md5=1a9454b8cdb45af98a43fbff5dd58fe9" +msgstr "" + +#: ./doc/install-guide/ch_basics.xml6(title) +msgid "Basic operating system configuration" +msgstr "" + +#: ./doc/install-guide/ch_basics.xml8(para) +msgid "" +"This guide shows you how to create a controller node to host most services " +"and a compute node to run virtual machine instances. Subsequent chapters " +"create additional nodes to run more services. OpenStack is flexible about " +"how and where you run each service, so other configurations are possible. " +"However, you must configure certain operating system settings on each node." +msgstr "" + +#: ./doc/install-guide/ch_basics.xml14(para) +msgid "" +"This chapter details a sample configuration for the controller node and any " +"additional nodes. You can configure the operating system in other ways, but " +"this guide assumes that your configuration is compatible with the one " +"described here." +msgstr "" + +#: ./doc/install-guide/ch_basics.xml18(para) +msgid "" +"All example commands assume you have administrative privileges. Either run " +"the commands as the root user or prefix them with the " +"command." +msgstr "" + +#: ./doc/install-guide/ch_basics.xml24(title) +#: ./doc/install-guide/object-storage/section_object-storage-install.xml23(title) +msgid "Before you begin" +msgstr "" + +#: ./doc/install-guide/ch_basics.xml26(para) +msgid "" +"We strongly recommend that you install a 64-bit operating system on your " +"compute nodes. If you use a 32-bit operating system, attempting a start a " +"virtual machine using a 64-bit image will fail with an error." +msgstr "" + +#: ./doc/install-guide/ch_basics.xml31(para) +msgid "" +"For more information about system requirements, see the OpenStack Operations Guide." +msgstr "" + +#: ./doc/install-guide/ch_basics.xml38(title) +msgid "Networking" +msgstr "" + +#: ./doc/install-guide/ch_basics.xml40(para) +msgid "" +"For an OpenStack production deployment, most nodes must have these network " +"interface cards:" +msgstr "" + +#: ./doc/install-guide/ch_basics.xml44(para) +msgid "One network interface card for external network traffic" +msgstr "" + +#: ./doc/install-guide/ch_basics.xml48(para) +msgid "Another card to communicate with other OpenStack nodes." +msgstr "" + +#: ./doc/install-guide/ch_basics.xml52(para) +msgid "" +"For simple test cases, you can use machines with a single network interface " +"card." +msgstr "" + +#: ./doc/install-guide/ch_basics.xml54(para) +msgid "" +"The following example configures Networking on two networks with static IP addresses and manually " +"manages a list of host names on each machine. If you manage a large network," +" you might already have systems in place to manage this. If so, you can skip" +" this section but note that the rest of this guide assumes that each node " +"can reach the other nodes on the internal network by using the " +"controller and compute1 host names." +msgstr "" + +#. these fedora only paragraphs are confirmed not needed in centos +#: ./doc/install-guide/ch_basics.xml64(para) +msgid "" +"Disable the NetworkManager " +"service and enable the network " +"service. The network service is " +"more suitable for the static network configuration done in this guide." +msgstr "" + +#: ./doc/install-guide/ch_basics.xml76(para) +msgid "" +"Since Fedora 19, firewalld replaces " +"iptables as the default firewall system." +msgstr "" + +#: ./doc/install-guide/ch_basics.xml79(para) +msgid "" +"You can use firewalld successfully, but this guide " +"recommends and demonstrates the use of the default " +"iptables." +msgstr "" + +#: ./doc/install-guide/ch_basics.xml82(para) +msgid "" +"For Fedora 19 systems, run the following commands to disable " +"firewalld and enable iptables:" +msgstr "" + +#: ./doc/install-guide/ch_basics.xml90(para) +msgid "" +"RHEL and derivatives including CentOS and Scientific Linux enable a " +"restrictive firewall by default. During this " +"installation, certain steps will fail unless you alter this setting or " +"disable the firewall. For further information about securing your " +"installation, refer to the OpenStack Security Guide." +msgstr "" + +#: ./doc/install-guide/ch_basics.xml98(para) +msgid "" +"When you set up your system, use the traditional network scripts and do not " +"use NetworkManager. You can " +"change the settings after installation with the YaST network module:" +msgstr "" + +#: ./doc/install-guide/ch_basics.xml104(para) +msgid "" +"Configure both eth0 and eth1. The " +"examples in this guide use the " +"192.168.0.x IP addresses for " +"the internal network and the " +"10.0.0.x IP addresses for the " +"external network. Make sure to connect your network devices to the correct " +"network." +msgstr "" + +#: ./doc/install-guide/ch_basics.xml111(para) +msgid "" +"In this guide, the controller node uses the 192.168.0.10 " +"and 10.0.0.10 IP addresses. When you create the compute " +"node, use the 192.168.0.11 and " +"10.0.0.11 addresses instead. Additional nodes that you " +"add in subsequent chapters also follow this pattern." +msgstr "" + +#: ./doc/install-guide/ch_basics.xml119(title) +msgid "Basic architecture" +msgstr "" + +#: ./doc/install-guide/ch_basics.xml128(filename) +msgid "/etc/sysconfig/network-scripts/ifcfg-eth0" +msgstr "" + +#: ./doc/install-guide/ch_basics.xml139(filename) +msgid "/etc/sysconfig/network-scripts/ifcfg-eth1" +msgstr "" + +#: ./doc/install-guide/ch_basics.xml149(para) +msgid "" +"To configure the network interfaces, start the YaST network module, as " +"follows:" +msgstr "" + +#: ./doc/install-guide/ch_basics.xml154(para) +msgid "" +"Use these parameters to set up the eth0 ethernet card for" +" the internal network:" +msgstr "" + +#: ./doc/install-guide/ch_basics.xml162(para) +msgid "" +"Use these parameters to set up the eth1 ethernet card for" +" the external network:" +msgstr "" + +#: ./doc/install-guide/ch_basics.xml170(para) +msgid "Set up a default route on the external network." +msgstr "" + +#: ./doc/install-guide/ch_basics.xml175(filename) +msgid "/etc/network/interfaces" +msgstr "" + +#: ./doc/install-guide/ch_basics.xml189(para) +msgid "" +"After you configure the network, restart the daemon for changes to take " +"effect:" +msgstr "" + +#: ./doc/install-guide/ch_basics.xml195(para) +msgid "" +"Set the host name of each machine. Name the controller node " +"controller and the first compute node " +"compute1. The examples in this guide use these host " +"names." +msgstr "" + +#: ./doc/install-guide/ch_basics.xml199(para) +msgid "" +"Use the command to set the host name: " +msgstr "" + +#: ./doc/install-guide/ch_basics.xml202(para) +msgid "Use to set the host name with YaST." +msgstr "" + +#: ./doc/install-guide/ch_basics.xml204(para) +msgid "" +"To have the host name change persist when the system reboots, you must " +"specify it in the proper configuration file. In Red Hat Enterprise Linux, " +"CentOS, and older versions of Fedora, you set this in the file " +"/etc/sysconfig/network. Change the line starting with " +"HOSTNAME=." +msgstr "" + +#: ./doc/install-guide/ch_basics.xml211(para) +msgid "" +"As of Fedora 18, Fedora uses the /etc/hostname file, " +"which contains a single line with the host name." +msgstr "" + +#: ./doc/install-guide/ch_basics.xml214(para) +msgid "" +"To configure this host name to be available when the system reboots, you " +"must specify it in the /etc/hostname file, which " +"contains a single line with the host name." +msgstr "" + +#: ./doc/install-guide/ch_basics.xml218(para) +msgid "" +"Finally, ensure that each node can reach the other nodes by using host " +"names. You must manually edit the /etc/hosts file on " +"each system. For large-scale deployments, use DNS or a configuration " +"management system like Puppet." +msgstr "" + +#: ./doc/install-guide/ch_basics.xml228(title) +msgid "Network Time Protocol (NTP)" +msgstr "" + +#: ./doc/install-guide/ch_basics.xml229(para) +msgid "" +"To synchronize services across multiple machines, you must install " +"NTP. The " +"examples in this guide configure the controller node as the reference server" +" and any additional nodes to set their time from the controller node." +msgstr "" + +#: ./doc/install-guide/ch_basics.xml234(para) +msgid "" +"Install the ntp package on each system running OpenStack " +"services." +msgstr "" + +#: ./doc/install-guide/ch_basics.xml239(para) +msgid "" +"Set up the NTP server on your controller node so that it receives data by " +"modifying the ntp.conf file and restarting the service." +msgstr "" + +#: ./doc/install-guide/ch_basics.xml247(para) +msgid "" +"On additional nodes, it is advised that you configure the other nodes to " +"synchronize their time from the controller node rather than from outside of " +"your LAN. To do so, install the ntp daemon as above, then edit " +"/etc/ntp.conf and change the server " +"directive to use the controller node as internet time source." +msgstr "" + +#: ./doc/install-guide/ch_basics.xml256(title) +msgid "Passwords" +msgstr "" + +#: ./doc/install-guide/ch_basics.xml258(para) +msgid "" +"The various OpenStack services and the required software like the database " +"and the Messaging server have to be password protected. These passwords are " +"needed when configuring a service and then again to access the service. You " +"have to choose a random password while configuring the service and later " +"remember to use the same password when accessing it. To generate a list of " +"passwords, you can use the pwgen program to " +"generate a list of passwords or take the output of: " +msgstr "" + +#: ./doc/install-guide/ch_basics.xml269(para) +msgid "" +"This guide uses the convention that " +"SERVICE_PASS is password to " +"access the service SERVICE and " +"SERVICE_DBPASS is the database" +" password used by the service SERVICE to access the database." +msgstr "" + +#: ./doc/install-guide/ch_basics.xml277(para) +msgid "" +"The complete list of passwords you need to define in this guide are:
Passwords
Password " +"nameDescription
Database password " +"(no variable used)Root password for the database
RABBIT_PASSPassword" +" of user guest of " +"RabbitMQ
KEYSTONE_DBPASSDatabase" +" password of Identity " +"service
ADMIN_PASSPassword" +" of user " +"admin
GLANCE_DBPASSDatabase" +" password for Image " +"Service
GLANCE_PASSPassword" +" of Image Service user " +"glance
NOVA_DBPASSDatabase" +" password for Compute " +"service
NOVA_PASSPassword" +" of Compute service user " +"nova
DASH_DBPASSDatabase" +" password for the " +"dashboard
CINDER_DBPASSDatabase" +" password for the Block Storage " +"Service
CINDER_PASSPassword" +" of Block Storage Service user " +"cinder
NEUTRON_DBPASSDatabase" +" password for the Networking " +"service
NEUTRON_PASSPassword" +" of Networking service user " +"neutron
HEAT_DBPASSDatabase" +" password for the Orchestration " +"service
HEAT_PASSPassword" +" of Orchestration service user " +"heat
CEILOMETER_DBPASSDatabase" +" password for the Telemetry " +"service
CEILOMETER_PASSPassword" +" of Telemetry service user " +"ceilometer
" +msgstr "" + +#: ./doc/install-guide/ch_basics.xml361(title) +msgid "MySQL database" +msgstr "" + +#: ./doc/install-guide/ch_basics.xml362(para) +msgid "" +"Most OpenStack services require a database to store information. These " +"examples use a MySQL database that runs on the controller node. You must " +"install the MySQL database on the controller node. You must install MySQL " +"client software on any additional nodes that access MySQL." +msgstr "" + +#: ./doc/install-guide/ch_basics.xml368(para) +msgid "" +"Most OpenStack services require a database to store information. This guide " +"uses a MySQL database on SUSE Linux Enterprise Server and a compatible " +"database on openSUSE running on the controller node. This compatible " +"database for openSUSE is MariaDB. You must install the MariaDB database on " +"the controller node. You must install the MariaDB client software on any " +"nodes that access the MariaDB database." +msgstr "" + +#: ./doc/install-guide/ch_basics.xml378(title) +msgid "Controller setup" +msgstr "" + +#: ./doc/install-guide/ch_basics.xml379(para) +msgid "" +"For SUSE Linux Enterprise Server: On the " +"controller node, install the MySQL client and server packages, and the " +"Python library." +msgstr "" + +#: ./doc/install-guide/ch_basics.xml383(para) +msgid "" +"For openSUSE: On the controller node, install the MariaDB client and " +"database server packages, and the MySQL Python library." +msgstr "" + +#: ./doc/install-guide/ch_basics.xml390(para) +msgid "" +"When you install the server package, you are prompted for the root password " +"for the database. Choose a strong password and remember it." +msgstr "" + +#: ./doc/install-guide/ch_basics.xml394(para) +msgid "" +"Edit /etc/mysql/my.cnf/etc/my.cnf and set the " +"bind-address to the internal IP address of the " +"controller, to enable access from outside the controller node." +msgstr "" + +#: ./doc/install-guide/ch_basics.xml404(para) +msgid "Restart the MySQL service to apply the changes:" +msgstr "" + +#: ./doc/install-guide/ch_basics.xml407(para) +msgid "" +"Start the MySQLMariaDB or MySQL database server and set it to" +" start automatically when the system boots." +msgstr "" + +#: ./doc/install-guide/ch_basics.xml416(para) +msgid "" +"Finally, you should set a root password for your MySQLMariaDB" +" or MySQL database. The OpenStack programs that set up databases " +"and tables prompt you for this password if it is set." +msgstr "" + +#: ./doc/install-guide/ch_basics.xml422(para) +msgid "" +"You must delete the anonymous users that are created when the database is " +"first started. Otherwise, database connection problems occur when you follow" +" the instructions in this guide. To do this, use the " +"command. Note that if fails you might need to use " +" first:" +msgstr "" + +#: ./doc/install-guide/ch_basics.xml431(para) +msgid "" +"If you have not already set " +"a root database password, press ENTER when you are prompted" +" for the password. This command presents a number of options for " +"you to secure your database installation. Respond to all " +"prompts unless you have a good reason to do otherwise." +msgstr "" + +#: ./doc/install-guide/ch_basics.xml441(title) +msgid "Node setup" +msgstr "" + +#: ./doc/install-guide/ch_basics.xml442(para) +msgid "" +"On all nodes other than the controller node, install the MySQLMariaDB (on openSUSE) client and the MySQL Python " +"library on any system that does not host a MySQL database:" +msgstr "" + +#: ./doc/install-guide/ch_basics.xml451(para) +msgid "For SUSE Linux Enterprise, install MySQL:" +msgstr "" + +#: ./doc/install-guide/ch_basics.xml458(title) +msgid "OpenStack packages" +msgstr "" + +#: ./doc/install-guide/ch_basics.xml459(para) +msgid "" +"Distributions might release OpenStack packages as part of their distribution" +" or through other methods because the OpenStack and distribution release " +"times are independent of each other." +msgstr "" + +#: ./doc/install-guide/ch_basics.xml463(para) +msgid "" +"This section describes the configuration you must complete after you " +"configure machines to install the latest OpenStack packages." +msgstr "" + +#: ./doc/install-guide/ch_basics.xml466(para) +msgid "" +"The examples in this guide use the OpenStack packages from the RDO " +"repository. These packages work on Red Hat Enterprise Linux 6, compatible " +"versions of CentOS, and Fedora 19. To enable the RDO repository, download " +"and install the rdo-release-havana package." +msgstr "" + +#: ./doc/install-guide/ch_basics.xml473(para) +msgid "" +"The EPEL package includes GPG keys for package signing and repository " +"information. This should only be installed on Red Hat Enterprise Linux and " +"CentOS, not Fedora. Install the latest epel-release " +"package (see http://download.fedoraproject.org/pub/epel/6/x86_64/repoview" +"/epel-release.html). For example:" +msgstr "" + +#: ./doc/install-guide/ch_basics.xml482(para) +msgid "" +"The openstack-utils package contains utility programs " +"that make installation and configuration easier. These programs are used " +"throughout this guide. Install openstack-utils. This " +"verifies that you can access the RDO repository." +msgstr "" + +#: ./doc/install-guide/ch_basics.xml489(para) +msgid "" +"Use the Open Build Service repositories for Havana " +"based on your openSUSE or SUSE Linux Enterprise Server version, for example " +"if you run openSUSE 12.3 use:" +msgstr "" + +#: ./doc/install-guide/ch_basics.xml494(para) +msgid "If you use SUSE Linux Enterprise Server 11 SP3, use:" +msgstr "" + +#: ./doc/install-guide/ch_basics.xml497(para) +msgid "" +"For openSUSE 13.1, nothing needs to be done because OpenStack Havana " +"packages are part of the distribution itself." +msgstr "" + +#: ./doc/install-guide/ch_basics.xml500(para) +msgid "" +"The openstack-utils package contains utility programs " +"that make installation and configuration easier. These programs are used " +"throughout this guide. Install openstack-utils. This " +"verifies that you can access the Open Build Service repository:" +msgstr "" + +#: ./doc/install-guide/ch_basics.xml507(para) +msgid "" +"The openstack-config program in the openstack-utils package uses crudini " +"to manipulate configuration files. However, " +"crudini version 0.3 does not support multi valued" +" options. See https://bugs.launchpad.net/openstack-" +"manuals/+bug/1269271. As a work around, you must manually set any " +"multi valued options or the new value overwrites the previous value instead " +"of creating a new option." +msgstr "" + +#: ./doc/install-guide/ch_basics.xml519(para) +msgid "" +"The openstack-selinux package includes the policy files " +"that are required to configure SELinux during OpenStack installation. " +"Install openstack-selinux." +msgstr "" + +#: ./doc/install-guide/ch_basics.xml525(para) +msgid "Upgrade your system packages:" +msgstr "" + +#: ./doc/install-guide/ch_basics.xml529(para) +msgid "" +"If the upgrade included a new kernel package, reboot the system to ensure " +"the new kernel is running:" +msgstr "" + +#: ./doc/install-guide/ch_basics.xml533(title) +msgid "To use the Ubuntu Cloud Archive for Havana" +msgstr "" + +#: ./doc/install-guide/ch_basics.xml534(para) +msgid "" +"The Ubuntu " +"Cloud Archive is a special repository that allows you to install " +"newer releases of OpenStack on the stable supported version of Ubuntu." +msgstr "" + +#: ./doc/install-guide/ch_basics.xml540(para) +msgid "" +"Install the Ubuntu Cloud Archive for Havana: " +"" +msgstr "" + +#: ./doc/install-guide/ch_basics.xml546(para) +msgid "" +"Update the package database, upgrade your system, and reboot for all changes" +" to take effect: " +msgstr "" + +#: ./doc/install-guide/ch_basics.xml553(title) +msgid "To use the Debian Wheezy backports archive for Havana" +msgstr "" + +#: ./doc/install-guide/ch_basics.xml555(para) +msgid "" +"The Havana release is available only in Debian Sid " +"(otherwise called Unstable). However, the Debian maintainers of OpenStack " +"also maintain a non-official Debian repository for OpenStack containing " +"Wheezy backports." +msgstr "" + +#: ./doc/install-guide/ch_basics.xml561(para) +msgid "Install the Debian Wheezy backport repository Havana:" +msgstr "" + +#: ./doc/install-guide/ch_basics.xml566(para) +msgid "Install the Debian Wheezy OpenStack repository for Havana:" +msgstr "" + +#: ./doc/install-guide/ch_basics.xml571(para) +msgid "Update the repository database and install the key:" +msgstr "" + +#: ./doc/install-guide/ch_basics.xml575(para) +msgid "" +"Update the package database, upgrade your system, and reboot for all changes" +" to take effect:" +msgstr "" + +#: ./doc/install-guide/ch_basics.xml581(para) +msgid "" +"Numerous archive.gplhost.com mirrors are available around the world. All are" +" available with both FTP and HTTP protocols (you should use the closest " +"mirror). The list of mirrors is available at http://archive.gplhost.com/readme.mirrors." +msgstr "" + +#: ./doc/install-guide/ch_basics.xml589(title) +msgid "Manually install python-argparse" +msgstr "" + +#: ./doc/install-guide/ch_basics.xml590(para) +msgid "" +"The Debian OpenStack packages are maintained on Debian Sid (also known as " +"Debian Unstable) - the current development version. Backported packages run " +"correctly on Debian Wheezy with one caveat:" +msgstr "" + +#: ./doc/install-guide/ch_basics.xml594(para) +msgid "" +"All OpenStack packages are written in Python. Wheezy uses Python 2.6 and " +"2.7, with Python 2.6 as the default interpreter; Sid has only Python 2.7. " +"There is one packaging change between these two. In Python 2.6, you " +"installed the python-argparse package separately. In " +"Python 2.7, this package is installed by default. Unfortunately, in Python " +"2.7, this package does not include Provides: python-argparse " +"directive." +msgstr "" + +#: ./doc/install-guide/ch_basics.xml602(para) +msgid "" +"Because the packages are maintained in Sid where the Provides: python-" +"argparse directive causes an error, and the Debian OpenStack " +"maintainer wants to maintain one version of the OpenStack packages, you must" +" manually install the python-argparse on each OpenStack " +"system that runs Debian Wheezy before you install the other OpenStack " +"packages. Use the following command to install the package:" +msgstr "" + +#: ./doc/install-guide/ch_basics.xml611(para) +msgid "This caveat applies to most OpenStack packages in Wheezy." +msgstr "" + +#: ./doc/install-guide/ch_basics.xml615(title) +msgid "Messaging server" +msgstr "" + +#: ./doc/install-guide/ch_basics.xml616(para) +msgid "" +"On the controller node, install the messaging queue server. Typically this " +"is RabbitMQQpid but QpidRabbitMQ and " +"ZeroMQ (0MQ) are also available." +msgstr "" + +#: ./doc/install-guide/ch_basics.xml628(title) +msgid "Important security consideration" +msgstr "" + +#: ./doc/install-guide/ch_basics.xml629(para) +msgid "" +"The rabbitmq-server package configures the RabbitMQ " +"service to start automatically and creates a guest user " +"with a default guest password. The RabbitMQ examples in " +"this guide use the guest account, though it is strongly " +"advised to change its default password, especially if you have IPv6 " +"available: by default the RabbitMQ server enables anyone to connect to it by" +" using guest as login and password, and with IPv6, it is reachable from the " +"outside." +msgstr "" + +#: ./doc/install-guide/ch_basics.xml639(para) +msgid "To change the default guest password of RabbitMQ:" +msgstr "" + +#: ./doc/install-guide/ch_basics.xml642(para) +msgid "" +"Disable Qpid authentication by editing /etc/qpidd.conf " +"file and changing the auth option to " +"no." +msgstr "" + +#: ./doc/install-guide/ch_basics.xml648(para) +msgid "" +"To simplify configuration, the Qpid examples in this guide do not use " +"authentication. However, we strongly advise enabling authentication for " +"production deployments. For more information on securing Qpid refer to the " +"Qpid " +"Documentation." +msgstr "" + +#: ./doc/install-guide/ch_basics.xml657(para) +msgid "" +"After you enable Qpid authentication, you must update the configuration file" +" of each OpenStack service to ensure that the " +"qpid_username and qpid_password " +"configuration keys refer to a valid Qpid username and password, " +"respectively." +msgstr "" + +#: ./doc/install-guide/ch_basics.xml665(para) +msgid "Start Qpid and set it to start automatically when the system boots." +msgstr "" + +#: ./doc/install-guide/ch_basics.xml669(para) +msgid "" +"Start the messaging service and set it to start automatically when the " +"system boots:" +msgstr "" + +#: ./doc/install-guide/ch_basics.xml673(para) +msgid "Congratulations, now you are ready to install OpenStack services!" +msgstr "" + +#: ./doc/install-guide/section_cinder-node.xml6(title) +msgid "Configure a Block Storage Service node" +msgstr "" + +#: ./doc/install-guide/section_cinder-node.xml7(para) +msgid "" +"After you configure the services on the controller node, configure a second " +"system to be a Block Storage Service node. This node contains the disk that " +"serves volumes." +msgstr "" + +#: ./doc/install-guide/section_cinder-node.xml10(para) +#: ./doc/install-guide/section_cinder-controller.xml15(para) +msgid "" +"You can configure OpenStack to use various storage systems. The examples in " +"this guide show you how to configure LVM." +msgstr "" + +#: ./doc/install-guide/section_cinder-node.xml14(para) +msgid "" +"Use the instructions in to configure the " +"system. Note the following differences from the installation instructions " +"for the controller node:" +msgstr "" + +#: ./doc/install-guide/section_cinder-node.xml19(para) +msgid "" +"Set the host name to block1. Ensure that the IP addresses" +" and host names for both nodes are listed in the " +"/etc/hosts file on each system." +msgstr "" + +#: ./doc/install-guide/section_cinder-node.xml25(para) +msgid "" +"Follow the instructions in to synchronize " +"from the controller node." +msgstr "" + +#: ./doc/install-guide/section_cinder-node.xml31(para) +msgid "" +"Install the required LVM packages, if they are not already installed: " +"" +msgstr "" + +#: ./doc/install-guide/section_cinder-node.xml37(para) +msgid "" +"Create the LVM physical and logical volumes. This guide assumes a second " +"disk /dev/sdb that is used for this purpose:" +msgstr "" + +#: ./doc/install-guide/section_cinder-node.xml45(para) +msgid "" +"Add a filter entry to the devices section " +"/etc/lvm/lvm.conf to keep LVM from scanning devices " +"used by virtual machines:" +msgstr "" + +#: ./doc/install-guide/section_cinder-node.xml49(para) +msgid "" +"You must add required physical volumes for LVM on the Block Storage host. " +"Run the command to get a list or required volumes." +msgstr "" + +#: ./doc/install-guide/section_cinder-node.xml53(para) +msgid "" +"Each item in the filter array starts with either an a for" +" accept, or an r for reject. The physical volumes that " +"are required on the Block Storage host have names that begin with " +"a. The array must end with \"r/.*/\" " +"to reject any device not listed." +msgstr "" + +#: ./doc/install-guide/section_cinder-node.xml59(para) +msgid "" +"In this example, /dev/sda1 is the volume where the " +"volumes for the operating system for the node reside, while " +"/dev/sdb is the volume reserved for cinder-" +"volumes." +msgstr "" + +#: ./doc/install-guide/section_cinder-node.xml70(para) +msgid "" +"After you configure the operating system, install the appropriate packages " +"for the Block Storage Service:" +msgstr "" + +#: ./doc/install-guide/section_cinder-node.xml77(para) +msgid "" +"Respond to the debconf prompts " +"about the database " +"management, [keystone_authtoken] " +"settings, and RabbitMQ " +"credentials. Make sure to enter the same details as your Block " +"Storage Service controller node." +msgstr "" + +#: ./doc/install-guide/section_cinder-node.xml85(para) +msgid "" +"Another screen prompts you for the volume-" +"group to use. The Debian package configuration script detects " +"every active volume group, provided that the lvm2 package is installed before Block " +"Storage (this should be the case if you configured the volume group first, " +"as this guide recommends), and tries to use the first one it sees. If you " +"have only one active volume group on your Block Storage Service node, you do" +" not need to manually enter its name in when you install the cinder-volume package because it is detected " +"automatically. If no volume-group" +" is available when you install cinder-" +"common, you must manually configure or re-configure cinder-common by using ." +msgstr "" + +#: ./doc/install-guide/section_cinder-node.xml104(para) +msgid "" +"Copy the /etc/cinder/api-paste.ini file from the " +"controller, or open the file in a text editor and locate the section " +"[filter:authtoken]. Make sure the following options are " +"set:" +msgstr "" + +#: ./doc/install-guide/section_cinder-node.xml115(replaceable) +#: ./doc/install-guide/section_cinder-controller.xml78(replaceable) +#: ./doc/install-guide/section_cinder-controller.xml94(replaceable) +msgid "CINDER_PASS" +msgstr "" + +#: ./doc/install-guide/section_cinder-node.xml118(para) +#: ./doc/install-guide/section_cinder-controller.xml98(para) +msgid "" +"Configure Block Storage to use the RabbitMQ message broker by setting these " +"configuration keys in the [DEFAULT] configuration group " +"of the /etc/cinder/cinder.conf file. Replace " +"RABBIT_PASS with the password you chose for " +"RabbitMQ." +msgstr "" + +#: ./doc/install-guide/section_cinder-node.xml133(para) +#: ./doc/install-guide/section_cinder-controller.xml113(para) +msgid "Configure Block Storage to use the Qpid message broker." +msgstr "" + +#: ./doc/install-guide/section_cinder-node.xml140(para) +#: ./doc/install-guide/section_cinder-controller.xml120(para) +msgid "" +"Configure Block Storage to use the RabbitMQ message broker. Replace " +"RABBIT_PASS with the password you chose for " +"RabbitMQ." +msgstr "" + +#: ./doc/install-guide/section_cinder-node.xml153(para) +msgid "" +"Configure Block Storage to use your MySQL database. Edit the " +"/etc/cinder/cinder.conf file and add the following key " +"under the [database] section. Replace " +"CINDER_DBPASS with the password you chose for the" +" Block Storage database." +msgstr "" + +#: ./doc/install-guide/section_cinder-node.xml158(para) +#: ./doc/install-guide/section_cinder-controller.xml41(para) +msgid "" +"The /etc/cinder/cinder.conf file packaged with some " +"distributions does not include the [database] section " +"header. You must add this section header to the end of the file before " +"proceeding further." +msgstr "" + +#: ./doc/install-guide/section_cinder-node.xml164(replaceable) +#: ./doc/install-guide/section_cinder-node.xml167(replaceable) +#: ./doc/install-guide/section_cinder-controller.xml47(replaceable) +#: ./doc/install-guide/section_cinder-controller.xml50(replaceable) +#: ./doc/install-guide/section_cinder-controller.xml56(replaceable) +#: ./doc/install-guide/section_cinder-controller.xml64(replaceable) +#: ./doc/install-guide/section_cinder-controller.xml66(replaceable) +msgid "CINDER_DBPASS" +msgstr "" + +#: ./doc/install-guide/section_cinder-node.xml173(para) +#: ./doc/install-guide/section_cinder-controller.xml158(para) +msgid "Restart the cinder service with its new settings:" +msgstr "" + +#: ./doc/install-guide/section_cinder-node.xml180(para) +msgid "" +"Configure the ISCI target service to discover cinder volumes. Add the " +"following line to the beginning of the " +"/etc/tgt/targets.conf file, if it is not already " +"present:" +msgstr "" + +#: ./doc/install-guide/section_cinder-node.xml188(para) +msgid "" +"Start the cinder services and configure them to start when the system boots:" +msgstr "" + +#: ./doc/install-guide/section_cinder-controller.xml5(title) +msgid "Configure a Block Storage Service controller" +msgstr "" + +#: ./doc/install-guide/section_cinder-controller.xml7(para) +msgid "" +"This section describes how to configure OpenStack Block Storage services on " +"the Controller node and " +"assumes that a second node provides storage through the cinder-volume service. For instructions on " +"how to configure the second node, see ." +msgstr "" + +#: ./doc/install-guide/section_cinder-controller.xml19(para) +msgid "Install the appropriate packages for the Block Storage Service:" +msgstr "" + +#: ./doc/install-guide/section_cinder-controller.xml26(para) +msgid "" +"Respond to the prompts for database management, [keystone_authtoken] " +"settings, RabbitMQ " +"credentials and API " +"endpoint registration." +msgstr "" + +#: ./doc/install-guide/section_cinder-controller.xml35(para) +msgid "" +"Configure Block Storage to use your MySQL database. Edit the " +"/etc/cinder/cinder.conf file and add the following key " +"under the [database] section. Replace " +"CINDER_DBPASS with the password for the Block " +"Storage database that you will create in a later step." +msgstr "" + +#: ./doc/install-guide/section_cinder-controller.xml53(para) +msgid "" +"To create the Block Storage Service database and tables and a " +"cinder database user, run the command." +msgstr "" + +#: ./doc/install-guide/section_cinder-controller.xml59(para) +msgid "" +"Use the password that you set to log in as root to create a " +"cinder database." +msgstr "" + +#: ./doc/install-guide/section_cinder-controller.xml69(para) +msgid "Create the database tables for the Block Storage Service." +msgstr "" + +#: ./doc/install-guide/section_cinder-controller.xml74(para) +msgid "" +"Create a cinder user. The Block Storage Service uses this" +" user to authenticate with the Identity Service. Use the " +"service tenant and give the user the " +"admin role." +msgstr "" + +#: ./doc/install-guide/section_cinder-controller.xml78(replaceable) +msgid "cinder@example.com" +msgstr "" + +#: ./doc/install-guide/section_cinder-controller.xml82(para) +msgid "" +"Add the credentials to the file /etc/cinder/api-" +"paste.ini. Open the file in a text editor and locate the section " +"[filter:authtoken]. Set the following options:" +msgstr "" + +#: ./doc/install-guide/section_cinder-controller.xml134(para) +msgid "" +"Register the Block Storage Service with the Identity Service so that other " +"OpenStack services can locate it. Register the service and specify the " +"endpoint using the command." +msgstr "" + +#: ./doc/install-guide/section_cinder-controller.xml147(para) +msgid "" +"Also register a service and endpoint for version 2 of the Block Storage " +"Service API." +msgstr "" + +#: ./doc/install-guide/section_cinder-controller.xml163(para) +msgid "" +"Start the cinder services and configure them to start when the system boots." +msgstr "" + +#: ./doc/install-guide/bk_openstackinstallguide.xml8(title) +msgid "" +"OpenStack Installation Guide for Red Hat " +"Enterprise Linux, CentOS, and Fedora for " +"Ubuntu 12.04 (LTS) for Debian 7.0 " +"(Wheezy) for openSUSE and SUSE Linux " +"Enterprise Server" +msgstr "" + +#: ./doc/install-guide/bk_openstackinstallguide.xml18(phrase) +msgid "for Red Hat Enterprise Linux, CentOS, and Fedora" +msgstr "" + +#: ./doc/install-guide/bk_openstackinstallguide.xml20(phrase) +msgid "for Ubuntu 12.04 (LTS)" +msgstr "" + +#: ./doc/install-guide/bk_openstackinstallguide.xml21(phrase) +msgid "for openSUSE and SUSE Linux Enterprise Server" +msgstr "" + +#: ./doc/install-guide/bk_openstackinstallguide.xml23(phrase) +msgid "for Debian 7.0 (Wheezy)" +msgstr "" + +#: ./doc/install-guide/bk_openstackinstallguide.xml17(titleabbrev) +msgid "" +"OpenStack Installation " +"Guide" +msgstr "" + +#: ./doc/install-guide/bk_openstackinstallguide.xml32(orgname) +msgid "OpenStack" +msgstr "" + +#: ./doc/install-guide/bk_openstackinstallguide.xml36(year) +msgid "2012" +msgstr "" + +#: ./doc/install-guide/bk_openstackinstallguide.xml37(year) +msgid "2013" +msgstr "" + +#: ./doc/install-guide/bk_openstackinstallguide.xml38(holder) +msgid "OpenStack Foundation" +msgstr "" + +#: ./doc/install-guide/bk_openstackinstallguide.xml40(releaseinfo) +msgid "havana" +msgstr "" + +#: ./doc/install-guide/bk_openstackinstallguide.xml41(productname) +msgid "OpenStack Installation Guide" +msgstr "" + +#: ./doc/install-guide/bk_openstackinstallguide.xml45(remark) +msgid "Copyright details are filled in by the template." +msgstr "" + +#: ./doc/install-guide/bk_openstackinstallguide.xml50(para) +msgid "" +"The OpenStack® system consists of several key projects that you install " +"separately but that work together depending on your cloud needs. These " +"projects include Compute, Identity Service, Networking, Image Service, Block" +" Storage Service, Object Storage, Telemetry, and Orchestration. You can " +"install any of these projects separately and configure them standalone or as" +" connected entities. This guide walks through an " +"installation by using packages available through Debian 7.0 (code name: " +"Wheezy).This guide walks through an " +"installation by using packages available through Ubuntu 12.04 " +"(LTS).This guide shows you how to" +" install OpenStack by using packages available through Fedora 19 as well as " +"on Red Hat Enterprise Linux and its derivatives through the EPEL " +"repository.This guide shows you how to " +"install OpenStack by using packages on openSUSE through the Open Build " +"Service Cloud repository. Explanations of configuration options and" +" sample configuration files are included." +msgstr "" + +#: ./doc/install-guide/bk_openstackinstallguide.xml78(date) +msgid "2013-10-25" +msgstr "" + +#: ./doc/install-guide/bk_openstackinstallguide.xml82(para) +msgid "Added initial Debian support." +msgstr "" + +#: ./doc/install-guide/bk_openstackinstallguide.xml88(date) +msgid "2013-10-17" +msgstr "" + +#: ./doc/install-guide/bk_openstackinstallguide.xml92(para) +msgid "Havana release." +msgstr "" + +#: ./doc/install-guide/bk_openstackinstallguide.xml98(date) +msgid "2013-10-16" +msgstr "" + +#: ./doc/install-guide/bk_openstackinstallguide.xml102(para) +msgid "Add support for SUSE Linux Enterprise." +msgstr "" + +#: ./doc/install-guide/bk_openstackinstallguide.xml109(date) +msgid "2013-10-08" +msgstr "" + +#: ./doc/install-guide/bk_openstackinstallguide.xml113(para) +msgid "Complete reorganization for Havana." +msgstr "" + +#: ./doc/install-guide/bk_openstackinstallguide.xml120(date) +msgid "2013-09-09" +msgstr "" + +#: ./doc/install-guide/bk_openstackinstallguide.xml124(para) +msgid "Build also for openSUSE." +msgstr "" + +#: ./doc/install-guide/bk_openstackinstallguide.xml130(date) +msgid "2013-08-01" +msgstr "" + +#: ./doc/install-guide/bk_openstackinstallguide.xml134(para) +msgid "" +"Fixes to Object Storage verification steps. Fix bug 1207347." +msgstr "" + +#: ./doc/install-guide/bk_openstackinstallguide.xml143(date) +msgid "2013-07-25" +msgstr "" + +#: ./doc/install-guide/bk_openstackinstallguide.xml147(para) +msgid "" +"Adds creation of cinder user and addition to the service tenant. Fix bug " +"1205057." +msgstr "" + +#: ./doc/install-guide/bk_openstackinstallguide.xml157(date) +msgid "2013-05-08" +msgstr "" + +#: ./doc/install-guide/bk_openstackinstallguide.xml161(para) +msgid "Updated the book title for consistency." +msgstr "" + +#: ./doc/install-guide/bk_openstackinstallguide.xml168(date) +msgid "2013-05-02" +msgstr "" + +#: ./doc/install-guide/bk_openstackinstallguide.xml172(para) +msgid "Updated cover and fixed small errors in appendix." +msgstr "" + +#: ./doc/install-guide/bk_openstackinstallguide.xml179(date) +msgid "2013-04-30" +msgstr "" + +#: ./doc/install-guide/bk_openstackinstallguide.xml183(para) +msgid "Grizzly release." +msgstr "" + +#: ./doc/install-guide/bk_openstackinstallguide.xml189(date) +msgid "2013-04-18" +msgstr "" + +#: ./doc/install-guide/bk_openstackinstallguide.xml193(para) +msgid "Updates and clean up on the Object Storage installation." +msgstr "" + +#: ./doc/install-guide/bk_openstackinstallguide.xml200(date) +msgid "2013-04-08" +msgstr "" + +#: ./doc/install-guide/bk_openstackinstallguide.xml204(para) +msgid "" +"Adds a note about availability of Grizzly packages on Ubuntu and Debian." +msgstr "" + +#: ./doc/install-guide/bk_openstackinstallguide.xml212(date) +msgid "2013-04-03" +msgstr "" + +#: ./doc/install-guide/bk_openstackinstallguide.xml216(para) +msgid "Updates RHEL/CentOS/Fedora information for Grizzly release." +msgstr "" + +#: ./doc/install-guide/bk_openstackinstallguide.xml224(date) +msgid "2013-03-26" +msgstr "" + +#: ./doc/install-guide/bk_openstackinstallguide.xml228(para) +msgid "Updates Dashboard (Horizon) information for Grizzly release." +msgstr "" + +#: ./doc/install-guide/bk_openstackinstallguide.xml236(date) +msgid "2013-02-12" +msgstr "" + +#: ./doc/install-guide/bk_openstackinstallguide.xml240(para) +msgid "" +"Adds chapter about Essex to Folsom upgrade for Compute and related services " +"(excludes OpenStack Object Storage (Swift) and OpenStack Networking " +"(Quantum))." +msgstr "" + +#: ./doc/install-guide/bk_openstackinstallguide.xml250(date) +msgid "2013-01-16" +msgstr "" + +#: ./doc/install-guide/bk_openstackinstallguide.xml254(para) +msgid "Fix file copy issue for figures in the /common/ directory." +msgstr "" + +#: ./doc/install-guide/bk_openstackinstallguide.xml261(date) +msgid "2012-11-09" +msgstr "" + +#: ./doc/install-guide/bk_openstackinstallguide.xml265(para) +msgid "Folsom release of this document." +msgstr "" + +#: ./doc/install-guide/bk_openstackinstallguide.xml272(date) +msgid "2012-10-10" +msgstr "" + +#: ./doc/install-guide/bk_openstackinstallguide.xml276(para) +msgid "" +"Doc bug fixes: 10544591064745" +msgstr "" + +#: ./doc/install-guide/bk_openstackinstallguide.xml286(date) +msgid "2012-09-26" +msgstr "" + +#: ./doc/install-guide/bk_openstackinstallguide.xml290(para) +msgid "Adds an all-in-one install section." +msgstr "" + +#: ./doc/install-guide/bk_openstackinstallguide.xml297(date) +msgid "2012-07-23" +msgstr "" + +#: ./doc/install-guide/bk_openstackinstallguide.xml301(para) +msgid "Adds additional detail about installing and configuring nova-volumes." +msgstr "" + +#: ./doc/install-guide/bk_openstackinstallguide.xml306(para) +msgid "" +"Doc bug fixes: 9785101027230" +msgstr "" + +#: ./doc/install-guide/bk_openstackinstallguide.xml317(date) +msgid "2012-07-17" +msgstr "" + +#: ./doc/install-guide/bk_openstackinstallguide.xml321(para) +msgid "Update build process so two uniquely-named PDF files are output." +msgstr "" + +#: ./doc/install-guide/bk_openstackinstallguide.xml329(date) +msgid "2012-07-13" +msgstr "" + +#: ./doc/install-guide/bk_openstackinstallguide.xml333(para) +msgid "" +"Doc bug fixes: 10258401025847" +msgstr "" + +#: ./doc/install-guide/bk_openstackinstallguide.xml344(date) +msgid "2012-06-19" +msgstr "" + +#: ./doc/install-guide/bk_openstackinstallguide.xml348(para) +msgid "Fix PDF links." +msgstr "" + +#: ./doc/install-guide/bk_openstackinstallguide.xml351(para) +msgid "" +"Doc bug fixes: 967778984959, 1002294, 1010163." +msgstr "" + +#: ./doc/install-guide/bk_openstackinstallguide.xml367(date) +msgid "2012-05-31" +msgstr "" + +#: ./doc/install-guide/bk_openstackinstallguide.xml371(para) +msgid "Revise install guide to encompass more Linux distros." +msgstr "" + +#: ./doc/install-guide/bk_openstackinstallguide.xml375(para) +msgid "" +"Doc bug fixes: 996988, 998116, 999005." +msgstr "" + +#: ./doc/install-guide/bk_openstackinstallguide.xml387(date) +msgid "2012-05-03" +msgstr "" + +#: ./doc/install-guide/bk_openstackinstallguide.xml391(para) +msgid "" +"Fixes problems with glance-api-paste.ini and glance-registry-paste.ini samples and instructions." +msgstr "" + +#: ./doc/install-guide/bk_openstackinstallguide.xml398(para) +msgid "Removes \"DRAFT\" designation." +msgstr "" + +#: ./doc/install-guide/bk_openstackinstallguide.xml404(date) +msgid "2012-05-02" +msgstr "" + +#: ./doc/install-guide/bk_openstackinstallguide.xml408(para) +msgid "Essex release." +msgstr "" + +#: ./doc/install-guide/bk_openstackinstallguide.xml414(date) +msgid "2012-05-01" +msgstr "" + +#: ./doc/install-guide/bk_openstackinstallguide.xml418(para) +msgid "Updates the Object Storage and Identity (Keystone) configuration." +msgstr "" + +#: ./doc/install-guide/bk_openstackinstallguide.xml426(date) +msgid "2012-04-25" +msgstr "" + +#: ./doc/install-guide/bk_openstackinstallguide.xml430(para) +msgid "" +"Changes service_id copy/paste error for the EC2 service-create command." +msgstr "" + +#: ./doc/install-guide/bk_openstackinstallguide.xml433(para) +msgid "Adds verification steps for Object Storage installation." +msgstr "" + +#: ./doc/install-guide/bk_openstackinstallguide.xml435(para) +msgid "" +"Fixes proxy-server.conf file so it points to keystone " +"not tempauth." +msgstr "" + +#: ./doc/install-guide/bk_openstackinstallguide.xml444(date) +msgid "2012-04-23" +msgstr "" + +#: ./doc/install-guide/bk_openstackinstallguide.xml448(para) +msgid "" +"Adds installation and configuration for multi-node Object Storage service." +msgstr "" + +#: ./doc/install-guide/bk_openstackinstallguide.xml456(date) +msgid "2012-04-17" +msgstr "" + +#: ./doc/install-guide/bk_openstackinstallguide.xml460(para) +msgid "" +"Doc bug fixes: 983417, 984106, 984034" +msgstr "" + +#: ./doc/install-guide/bk_openstackinstallguide.xml472(date) +msgid "2012-04-13" +msgstr "" + +#: ./doc/install-guide/bk_openstackinstallguide.xml476(para) +msgid "" +"Doc bug fixes: 977905, 980882, 977823, adds additional Glance database " +"preparation steps" +msgstr "" + +#: ./doc/install-guide/bk_openstackinstallguide.xml490(date) +msgid "2012-04-10" +msgstr "" + +#: ./doc/install-guide/bk_openstackinstallguide.xml494(para) +msgid "" +"Doc bug fixes: 977831" +msgstr "" + +#: ./doc/install-guide/bk_openstackinstallguide.xml502(date) +msgid "2012-03-23" +msgstr "" + +#: ./doc/install-guide/bk_openstackinstallguide.xml506(para) +msgid "Updates for Xen hypervisor." +msgstr "" + +#: ./doc/install-guide/bk_openstackinstallguide.xml512(date) +msgid "2012-03-09" +msgstr "" + +#: ./doc/install-guide/bk_openstackinstallguide.xml516(para) +msgid "" +"Updates for Essex release, includes new Glance config files, new Keystone " +"configuration." +msgstr "" + +#: ./doc/install-guide/bk_openstackinstallguide.xml524(date) +msgid "2012-01-24" +msgstr "" + +#: ./doc/install-guide/bk_openstackinstallguide.xml528(para) +msgid "Initial draft for Essex." +msgstr "" + +#: ./doc/install-guide/bk_openstackinstallguide.xml531(para) +msgid "Assumes use of Ubuntu 12.04 repository." +msgstr "" + +#: ./doc/install-guide/bk_openstackinstallguide.xml540(date) +msgid "2011-01-24" +msgstr "" + +#: ./doc/install-guide/bk_openstackinstallguide.xml544(para) +msgid "Initial draft for Diablo." +msgstr "" + +#. When image changes, this message will be marked fuzzy or untranslated for +#. you. +#. It doesn't matter what you translate it to: it's not used at all. +#: ./doc/install-guide/section_neutron-install.xml21(None) +msgid "" +"@@image: 'figures/debconf-screenshots/neutron_1_plugin_selection.png'; " +"md5=adf41c33778a691a560b7098908792db" +msgstr "" + +#. When image changes, this message will be marked fuzzy or untranslated for +#. you. +#. It doesn't matter what you translate it to: it's not used at all. +#: ./doc/install-guide/section_neutron-install.xml113(None) +msgid "" +"@@image: 'figures/debconf-screenshots/neutron_2_networking_type.png'; " +"md5=0d4d788a44ae0a716a503dca20b82f22" +msgstr "" + +#. When image changes, this message will be marked fuzzy or untranslated for +#. you. +#. It doesn't matter what you translate it to: it's not used at all. +#: ./doc/install-guide/section_neutron-install.xml122(None) +msgid "" +"@@image: 'figures/debconf-screenshots/neutron_3_hypervisor_ip.png'; " +"md5=2beb543a6334f641d7b69ac5dcbcb3a8" +msgstr "" + +#: ./doc/install-guide/section_neutron-install.xml8(title) +msgid "Install Networking services" +msgstr "" + +#: ./doc/install-guide/section_neutron-install.xml9(para) +msgid "" +"When you install a Networking node, you must configure it for API endpoints," +" RabbitMQ, keystone_authtoken, and the database. Use " +"debconf to configure these values." +msgstr "" + +#: ./doc/install-guide/section_neutron-install.xml13(para) +msgid "" +"When you install a Networking package, debconf prompts " +"you to choose configuration options including which plug-in to use, as " +"follows:" +msgstr "" + +#: ./doc/install-guide/section_neutron-install.xml25(para) +msgid "" +"This parameter sets the core_plugin option value in " +"the /etc/neutron/neutron.conf file." +msgstr "" + +#: ./doc/install-guide/section_neutron-install.xml29(para) +msgid "" +"When you install the neutron-common package, all plug-ins" +" are installed by default." +msgstr "" + +#: ./doc/install-guide/section_neutron-install.xml32(para) +msgid "" +"This table lists the values for the core_plugin " +"option. These values depend on your response to the " +"debconf prompt." +msgstr "" + +#: ./doc/install-guide/section_neutron-install.xml36(caption) +msgid "Plug-ins and the core_plugin option" +msgstr "" + +#: ./doc/install-guide/section_neutron-install.xml39(th) +msgid "Plug-in" +msgstr "" + +#: ./doc/install-guide/section_neutron-install.xml41(filename) +msgid "neutron.conf" +msgstr "" + +#: ./doc/install-guide/section_neutron-install.xml40(th) +msgid "core_plugin value in " +msgstr "" + +#: ./doc/install-guide/section_neutron-install.xml46(para) +msgid "BigSwitch" +msgstr "" + +#: ./doc/install-guide/section_neutron-install.xml47(para) +msgid "neutron.plugins.bigswitch.plugin.NeutronRestProxyV2" +msgstr "" + +#: ./doc/install-guide/section_neutron-install.xml50(para) +msgid "Brocade" +msgstr "" + +#: ./doc/install-guide/section_neutron-install.xml51(para) +msgid "neutron.plugins.brocade.NeutronPlugin.BrocadePluginV2" +msgstr "" + +#: ./doc/install-guide/section_neutron-install.xml54(para) +msgid "Cisco" +msgstr "" + +#: ./doc/install-guide/section_neutron-install.xml55(para) +msgid "neutron.plugins.cisco.network_plugin.PluginV2" +msgstr "" + +#: ./doc/install-guide/section_neutron-install.xml58(para) +msgid "Hyper-V" +msgstr "" + +#: ./doc/install-guide/section_neutron-install.xml59(para) +msgid "neutron.plugins.hyperv.hyperv_neutron_plugin.HyperVNeutronPlugin" +msgstr "" + +#: ./doc/install-guide/section_neutron-install.xml62(para) +msgid "LinuxBridge" +msgstr "" + +#: ./doc/install-guide/section_neutron-install.xml63(para) +msgid "neutron.plugins.linuxbridge.lb_neutron_plugin.LinuxBridgePluginV2" +msgstr "" + +#: ./doc/install-guide/section_neutron-install.xml66(para) +msgid "Mellanox" +msgstr "" + +#: ./doc/install-guide/section_neutron-install.xml67(para) +msgid "neutron.plugins.mlnx.mlnx_plugin.MellanoxEswitchPlugin" +msgstr "" + +#: ./doc/install-guide/section_neutron-install.xml70(para) +msgid "MetaPlugin" +msgstr "" + +#: ./doc/install-guide/section_neutron-install.xml71(para) +msgid "neutron.plugins.metaplugin.meta_neutron_plugin.MetaPluginV2" +msgstr "" + +#: ./doc/install-guide/section_neutron-install.xml74(para) +msgid "Midonet" +msgstr "" + +#: ./doc/install-guide/section_neutron-install.xml75(para) +msgid "neutron.plugins.midonet.plugin.MidonetPluginV2" +msgstr "" + +#: ./doc/install-guide/section_neutron-install.xml78(para) +msgid "ml2" +msgstr "" + +#: ./doc/install-guide/section_neutron-install.xml79(para) +msgid "neutron.plugins.ml2.plugin.Ml2Plugin" +msgstr "" + +#: ./doc/install-guide/section_neutron-install.xml82(para) +msgid "Nec" +msgstr "" + +#: ./doc/install-guide/section_neutron-install.xml83(para) +msgid "neutron.plugins.nec.nec_plugin.NECPluginV2" +msgstr "" + +#: ./doc/install-guide/section_neutron-install.xml86(para) +msgid "OpenVSwitch" +msgstr "" + +#: ./doc/install-guide/section_neutron-install.xml87(para) +msgid "neutron.plugins.openvswitch.ovs_neutron_plugin.OVSNeutronPluginV2" +msgstr "" + +#: ./doc/install-guide/section_neutron-install.xml90(para) +msgid "PLUMgrid" +msgstr "" + +#: ./doc/install-guide/section_neutron-install.xml91(para) +msgid "" +"neutron.plugins.plumgrid.plumgrid_nos_plugin.plumgrid_plugin.NeutronPluginPLUMgridV2" +msgstr "" + +#: ./doc/install-guide/section_neutron-install.xml94(para) +msgid "RYU" +msgstr "" + +#: ./doc/install-guide/section_neutron-install.xml95(para) +msgid "neutron.plugins.ryu.ryu_neutron_plugin.RyuNeutronPluginV2" +msgstr "" + +#: ./doc/install-guide/section_neutron-install.xml99(para) +msgid "" +"Depending on the value of core_plugin, the start-up " +"scripts start the daemons by using the corresponding plug-in configuration " +"file directly. For example, if you selected the Open vSwitch plug-in, neutron-server automatically launches with --config-file " +"/etc/neutron/plugins/openvswitch/ovs_neutron_plugin.ini." +msgstr "" + +#: ./doc/install-guide/section_neutron-install.xml106(para) +msgid "" +"The neutron-common package also prompts you for the " +"default network configuration:" +msgstr "" + +#: ./doc/install-guide/section_neutron-install.xml126(para) +msgid "" +"Before you configure individual nodes for Networking, you must create the " +"required OpenStack components: user, service, database, and one or more " +"endpoints. After you complete these steps on the controller node, follow the" +" instructions in this guide to set up OpenStack Networking nodes." +msgstr "" + +#. TODO(sross): move this into its own section +#: ./doc/install-guide/section_neutron-install.xml136(para) +msgid "" +"Use the password that you set previously to log in as root and create a " +"neutron database:" +msgstr "" + +#: ./doc/install-guide/section_neutron-install.xml146(para) +msgid "" +"Create the required user, service, and endpoint so that Networking can " +"interface with the Identity Service." +msgstr "" + +#: ./doc/install-guide/section_neutron-install.xml148(para) +msgid "Create a neutron user:" +msgstr "" + +#: ./doc/install-guide/section_neutron-install.xml149(replaceable) +msgid "neutron@example.com" +msgstr "" + +#: ./doc/install-guide/section_neutron-install.xml150(para) +msgid "Add the user role to the neutron user:" +msgstr "" + +#: ./doc/install-guide/section_neutron-install.xml152(para) +msgid "Create the neutron service:" +msgstr "" + +#: ./doc/install-guide/section_neutron-install.xml155(para) +msgid "Create a Networking endpoint:" +msgstr "" + +#: ./doc/install-guide/section_neutron-install.xml164(title) +msgid "Install Networking services on a dedicated network node" +msgstr "" + +#: ./doc/install-guide/section_neutron-install.xml167(para) +msgid "" +"Before you start, set up a machine as a dedicated network node. Dedicated " +"network nodes have a MGMT_INTERFACE NIC, a " +"DATA_INTERFACE NIC, and a " +"EXTERNAL_INTERFACE NIC." +msgstr "" + +#: ./doc/install-guide/section_neutron-install.xml172(para) +msgid "" +"The management network handles communication among nodes. The data network " +"handles communication coming to and from VMs. The external NIC connects the " +"network node, and optionally to the controller node, so your VMs can connect" +" to the outside world." +msgstr "" + +#: ./doc/install-guide/section_neutron-install.xml177(para) +msgid "" +"All NICs must have static IPs. However, the data and external NICs have a " +"special set up. For details about Networking plug-ins, see ." +msgstr "" + +#: ./doc/install-guide/section_neutron-install.xml183(para) +msgid "" +"By default, the system-config-firewall automated firewall" +" configuration tool is in place on RHEL. This graphical interface (and a " +"curses-style interface with -tui on the end of the name) " +"enables you to configure IP tables as a basic firewall. You should disable " +"it when you work with Networking unless you are familiar with the underlying" +" network technologies, as, by default, it blocks various types of network " +"traffic that are important to Networking. To disable it, simply launch the " +"program and clear the Enabled check box." +msgstr "" + +#: ./doc/install-guide/section_neutron-install.xml193(para) +msgid "" +"After you successfully set up OpenStack Networking, you can re-enable and " +"configure the tool. However, during Networking set up, disable the tool to " +"make it easier to debug network issues." +msgstr "" + +#: ./doc/install-guide/section_neutron-install.xml200(para) +msgid "Install the Networking packages and any dependencies." +msgstr "" + +#: ./doc/install-guide/section_neutron-install.xml208(para) +msgid "" +"Respond to prompts for database " +"management, [keystone_authtoken] " +"settings, RabbitMQ " +"credentials and API " +"endpoint registration." +msgstr "" + +#: ./doc/install-guide/section_neutron-install.xml219(para) +msgid "Configure basic Networking-related services to start at boot time:" +msgstr "" + +#: ./doc/install-guide/section_neutron-install.xml225(para) +msgid "" +"Enable packet forwarding and disable packet destination filtering so that " +"the network node can coordinate traffic for the VMs. Edit the " +"/etc/sysctl.conf file, as follows:" +msgstr "" + +#: ./doc/install-guide/section_neutron-install.xml232(para) +msgid "" +"Use the command to ensure the changes made to the " +"/etc/sysctl.conf file take effect:" +msgstr "" + +#: ./doc/install-guide/section_neutron-install.xml237(para) +msgid "" +"It is recommended that the networking service is restarted after changing " +"values related to the networking configuration. This ensures that all " +"modified values take effect immediately:" +msgstr "" + +#: ./doc/install-guide/section_neutron-install.xml246(para) +#: ./doc/install-guide/section_neutron-install.xml839(para) +#: ./doc/install-guide/section_neutron-install.xml1233(para) +msgid "" +"Configure Networking to use keystone for authentication:" +msgstr "" + +#: ./doc/install-guide/section_neutron-install.xml249(para) +#: ./doc/install-guide/section_neutron-install.xml274(para) +#: ./doc/install-guide/section_neutron-install.xml842(para) +#: ./doc/install-guide/section_neutron-install.xml1236(para) +msgid "" +"Set the auth_strategy configuration key to " +"keystone in the DEFAULT section of the" +" file:" +msgstr "" + +#: ./doc/install-guide/section_neutron-install.xml255(para) +#: ./doc/install-guide/section_neutron-install.xml848(para) +#: ./doc/install-guide/section_neutron-install.xml1242(para) +msgid "" +"Set the neutron configuration for" +" keystone authentication:" +msgstr "" + +#: ./doc/install-guide/section_neutron-install.xml270(para) +msgid "" +"To configure neutron to use " +"keystone for authentication, edit" +" the /etc/neutron/neutron.conffile." +msgstr "" + +#: ./doc/install-guide/section_neutron-install.xml280(para) +msgid "" +"Add these lines to the keystone_authtoken section of the " +"file:" +msgstr "" + +#: ./doc/install-guide/section_neutron-install.xml293(para) +#: ./doc/install-guide/section_neutron-install.xml904(para) +#: ./doc/install-guide/section_neutron-install.xml1352(para) +msgid "" +"Set the root_helper configuration in the " +"[agent] section of " +"/etc/neutron/neutron.conf:" +msgstr "" + +#: ./doc/install-guide/section_neutron-install.xml310(para) +msgid "" +"Configure the RabbitMQ access. Edit the " +"/etc/neutron/neutron.conf file to modify the following " +"parameters in the DEFAULT section." +msgstr "" + +#: ./doc/install-guide/section_neutron-install.xml337(para) +#: ./doc/install-guide/section_neutron-install.xml915(para) +msgid "" +"Configure Networking to connect to the database. Edit the " +"[database] section in the same file, as follows:" +msgstr "" + +#: ./doc/install-guide/section_neutron-install.xml344(para) +#: ./doc/install-guide/section_neutron-install.xml933(para) +#: ./doc/install-guide/section_neutron-install.xml1300(para) +msgid "" +"Configure the /etc/neutron/api-paste.ini file for " +"keystone authentication:" +msgstr "" + +#: ./doc/install-guide/section_neutron-install.xml360(para) +#: ./doc/install-guide/section_neutron-install.xml922(para) +msgid "" +"Edit the /etc/neutron/api-paste.ini file and add these " +"lines to the [filter:authtoken] section:" +msgstr "" + +#: ./doc/install-guide/section_neutron-install.xml371(para) +msgid "" +"keystoneclient.middleware.auth_token: You must configure " +"auth_uri to point to the public identity endpoint. " +"Otherwise, clients might not be able to authenticate against an admin " +"endpoint." +msgstr "" + +#: ./doc/install-guide/section_neutron-install.xml378(para) +msgid "" +"Configure your network plug-in. For instructions, see instructions. Then, return here." +msgstr "" + +#: ./doc/install-guide/section_neutron-install.xml383(para) +msgid "" +"Install and configure a networking plug-in. OpenStack Networking uses this " +"plug-in to perform software-defined networking. See for further details. Then, return here when " +"finished." +msgstr "" + +#: ./doc/install-guide/section_neutron-install.xml389(para) +msgid "" +"Now that you've installed and configured a plug-in, it is time to configure " +"the remaining parts of OpenStack Networking." +msgstr "" + +#: ./doc/install-guide/section_neutron-install.xml393(para) +msgid "" +"To perform DHCP on the software-defined networks, Networking supports " +"several different plug-ins. However, in general, you use the " +"dnsmasq plug-in." +msgstr "" + +#: ./doc/install-guide/section_neutron-install.xml396(para) +msgid "Configure the /etc/neutron/dhcp_agent.ini file:" +msgstr "" + +#: ./doc/install-guide/section_neutron-install.xml405(para) +msgid "" +"To allow virtual machines to access the Compute metadata information, the " +"Networking metadata agent must be enabled and configured. The agent will act" +" as a proxy for the Compute metadata service." +msgstr "" + +#: ./doc/install-guide/section_neutron-install.xml409(para) +msgid "" +"On the controller, edit the /etc/nova/nova.conf file to" +" define a secret key that will be shared between the Compute Service and the" +" Networking metadata agent." +msgstr "" + +#: ./doc/install-guide/section_neutron-install.xml413(para) +msgid "Add to the [DEFAULT] section:" +msgstr "" + +#: ./doc/install-guide/section_neutron-install.xml416(replaceable) +#: ./doc/install-guide/section_neutron-install.xml422(replaceable) +#: ./doc/install-guide/section_neutron-install.xml441(replaceable) +#: ./doc/install-guide/section_neutron-install.xml457(replaceable) +msgid "METADATA_PASS" +msgstr "" + +#: ./doc/install-guide/section_neutron-install.xml418(para) +msgid "Set the neutron_metadata_proxy_shared_secret key:" +msgstr "" + +#: ./doc/install-guide/section_neutron-install.xml425(para) +msgid "Restart the nova-api service:" +msgstr "" + +#: ./doc/install-guide/section_neutron-install.xml429(para) +msgid "On the network node, modify the metadata agent configuration." +msgstr "" + +#: ./doc/install-guide/section_neutron-install.xml431(para) +msgid "" +"Edit the /etc/neutron/metadata_agent.ini file and " +"modify the [DEFAULT] section:" +msgstr "" + +#: ./doc/install-guide/section_neutron-install.xml442(para) +#: ./doc/install-guide/section_neutron-install.xml472(para) +msgid "Set the required keys:" +msgstr "" + +#: ./doc/install-guide/section_neutron-install.xml459(para) +msgid "" +"The value of auth_region is case-sensitive and must match" +" the endpoint region defined in Keystone." +msgstr "" + +#: ./doc/install-guide/section_neutron-install.xml464(para) +msgid "" +"If you serve the OpenStack Networking API over HTTPS with self-signed " +"certificates, you must perform additional configuration for the metadata " +"agent because Networking cannot validate the SSL certificates from the " +"service catalog." +msgstr "" + +#: ./doc/install-guide/section_neutron-install.xml468(para) +msgid "Add this statement to the [DEFAULT] section:" +msgstr "" + +#: ./doc/install-guide/section_neutron-install.xml477(para) +#: ./doc/install-guide/section_neutron-install.xml1441(para) +msgid "" +"The neutron-server initialization" +" script expects a symbolic link /etc/neutron/plugin.ini" +" pointing to the configuration file associated with your chosen plug-in. " +"Using Open vSwitch, for example, the symbolic link must point to " +"/etc/neutron/plugins/openvswitch/ovs_neutron_plugin.ini." +" If this symbolic link does not exist, create it using the following " +"commands:" +msgstr "" + +#: ./doc/install-guide/section_neutron-install.xml489(para) +#: ./doc/install-guide/section_neutron-install.xml1453(para) +msgid "" +"The openstack-neutron " +"initialization script expects the variable " +"NEUTRON_PLUGIN_CONF in file " +"/etc/sysconfig/neutron to reference the configuration " +"file associated with your chosen plug-in. Using Open vSwitch, for example, " +"edit the /etc/sysconfig/neutron file and add the " +"following:" +msgstr "" + +#: ./doc/install-guide/section_neutron-install.xml500(para) +msgid "Restart Networking services." +msgstr "" + +#: ./doc/install-guide/section_neutron-install.xml510(para) +#: ./doc/install-guide/section_neutron-install.xml1033(para) +msgid "" +"Also restart your chosen Networking plug-in agent, for example, Open " +"vSwitch." +msgstr "" + +#: ./doc/install-guide/section_neutron-install.xml516(para) +msgid "" +"After you configure the compute and controller nodes, configure the base networks." +msgstr "" + +#: ./doc/install-guide/section_neutron-install.xml526(title) +msgid "Install and configure the Networking plug-ins" +msgstr "" + +#: ./doc/install-guide/section_neutron-install.xml528(title) +msgid "Install the Open vSwitch (OVS) plug-in" +msgstr "" + +#: ./doc/install-guide/section_neutron-install.xml531(para) +#: ./doc/install-guide/section_neutron-install.xml1047(para) +msgid "Install the Open vSwitch plug-in and its dependencies:" +msgstr "" + +#: ./doc/install-guide/section_neutron-install.xml537(para) +msgid "" +"On Ubuntu 12.04 LTS with GRE you must install openvswitch-datapath-dkms and " +"restart the service to enable the GRE flow so that OVS 1.10 and higher is " +"used. Make sure you are running the OVS 1.10 kernel module in addition to " +"the OVS 1.10 user space. Both the kernel module and user space are required " +"for VXLAN support. The error you see in the /var/log" +"/openvswitchovs-vswitchd.log log file is \"Stderr: 'ovs-ofctl: " +"-1: negative values not supported for in_port\\n'\". If you see this error, " +"make sure shows the right version. Also check the output " +"from for the version of the OVS module being loaded." +msgstr "" + +#: ./doc/install-guide/section_neutron-install.xml554(para) +msgid "Start Open vSwitch:" +msgstr "" + +#: ./doc/install-guide/section_neutron-install.xml558(para) +msgid "And configure it to start when the system boots:" +msgstr "" + +#: ./doc/install-guide/section_neutron-install.xml564(para) +msgid "" +"No matter which networking technology you use, you must add the br-" +"int integration bridge, which connects to the VMs, and the " +"br-ex external bridge, which connects to the outside " +"world." +msgstr "" + +#: ./doc/install-guide/section_neutron-install.xml573(para) +msgid "" +"Add a port (connection) from the " +"EXTERNAL_INTERFACE interface to br-" +"ex interface:" +msgstr "" + +#: ./doc/install-guide/section_neutron-install.xml576(replaceable) +#: ./doc/install-guide/section_neutron-install.xml583(replaceable) +msgid "EXTERNAL_INTERFACE" +msgstr "" + +#: ./doc/install-guide/section_neutron-install.xml578(para) +msgid "" +"The host must have an IP address associated with an interface other than " +"EXTERNAL_INTERFACE, and your remote terminal " +"session must be associated with this other IP address." +msgstr "" + +#: ./doc/install-guide/section_neutron-install.xml582(para) +msgid "" +"If you associate an IP address with " +"EXTERNAL_INTERFACE, that IP address stops working" +" after you issue the command. If you associate a remote " +"terminal session with that IP address, you lose connectivity with the host." +msgstr "" + +#: ./doc/install-guide/section_neutron-install.xml586(para) +msgid "" +"For more details about this behavior, see the Configuration " +"Problems section of the Open vSwitch " +"FAQ." +msgstr "" + +#: ./doc/install-guide/section_neutron-install.xml593(para) +msgid "" +"Configure the EXTERNAL_INTERFACE without an IP " +"address and in promiscuous mode. Additionally, you must set the newly " +"created br-ex interface to have the IP address that " +"formerly belonged to EXTERNAL_INTERFACE." +msgstr "" + +#: ./doc/install-guide/section_neutron-install.xml600(para) +msgid "" +"Generic Receive Offload (GRO) should not be enabled on this interface as it " +"can cause severe performance problems. It can be disabled with the ethtool " +"utility." +msgstr "" + +#: ./doc/install-guide/section_neutron-install.xml605(para) +msgid "" +"Edit the /etc/sysconfig/network-scripts/ifcfg-" +"EXTERNAL_INTERFACE file:" +msgstr "" + +#: ./doc/install-guide/section_neutron-install.xml614(para) +msgid "" +"Create and edit the /etc/sysconfig/network-scripts/ifcfg-br-" +"ex file:" +msgstr "" + +#: ./doc/install-guide/section_neutron-install.xml627(para) +msgid "" +"You must set some common configuration options no matter which networking " +"technology you choose to use with Open vSwitch. Configure the L3 and DHCP " +"agents to use OVS and namespaces. Edit the " +"/etc/neutron/l3_agent.ini and " +"/etc/neutron/dhcp_agent.ini files, respectively:" +msgstr "" + +#: ./doc/install-guide/section_neutron-install.xml636(para) +msgid "" +"You must enable veth support if you use certain kernels. Some kernels, such " +"as recent versions of RHEL (not RHOS) and CentOS, only partially support " +"namespaces. Edit the previous files, as follows:" +msgstr "" + +#: ./doc/install-guide/section_neutron-install.xml644(para) +msgid "" +"Similarly, you must also tell Neutron core to use OVS. " +"Edit the /etc/neutron/neutron.conf file:" +msgstr "" + +#: ./doc/install-guide/section_neutron-install.xml651(para) +msgid "" +"Choose a networking technology to create the virtual networks. Neutron " +"supports GRE tunneling, VLANs, and VXLANs. This guide shows how to configure" +" GRE tunneling and VLANs." +msgstr "" + +#: ./doc/install-guide/section_neutron-install.xml655(para) +msgid "" +"GRE " +"tunneling is simpler to set up because it does not require any " +"special configuration from any physical network hardware. However, its " +"protocol makes it difficult to filter traffic on the physical network. " +"Additionally, this configuration does not use namespaces. You can have only " +"one router for each network node. However, you can enable namespacing, and " +"potentially veth, as described in the section detailing how to use VLANs " +"with OVS)." +msgstr "" + +#: ./doc/install-guide/section_neutron-install.xml666(para) +msgid "" +"On the other hand, VLAN tagging modifies the ethernet header of packets. " +"You can filter packets on the physical network through normal methods. " +"However, not all NICs handle the increased packet size of VLAN-tagged " +"packets well, and you might need to complete additional configuration on " +"physical network hardware to ensure that your Neutron VLANs do not interfere" +" with any other VLANs on your network and that any physical network hardware" +" between nodes does not strip VLAN tags." +msgstr "" + +#: ./doc/install-guide/section_neutron-install.xml678(para) +msgid "" +"While the examples in this guide enable network namespaces by default, you " +"can disable them if issues occur or your kernel does not support them. Edit " +"the /etc/neutron/l3_agent.ini and " +"/etc/neutron/dhcp_agent.ini files, respectively:" +msgstr "" + +#: ./doc/install-guide/section_neutron-install.xml685(para) +msgid "" +"Edit the /etc/neutron/neutron.conf file to disable " +"overlapping IP addresses:" +msgstr "" + +#: ./doc/install-guide/section_neutron-install.xml689(para) +msgid "" +"Note that when network namespaces are disabled, you can have only one router" +" for each network node and overlapping IP addresses are not supported." +msgstr "" + +#: ./doc/install-guide/section_neutron-install.xml692(para) +msgid "" +"You must complete additional steps after you create the initial Neutron " +"virtual networks and router." +msgstr "" + +#: ./doc/install-guide/section_neutron-install.xml699(para) +msgid "" +"Configure a firewall plug-in. If you do not wish to enforce firewall rules, " +"called security groups by" +" OpenStack, you can use " +"neutron.agent.firewall.NoopFirewall. Otherwise, you can " +"choose one of the Networking firewall plug-ins. The most common choice is " +"the Hybrid OVS-IPTables driver, but you can also use the Firewall-" +"as-a-Service driver. Edit the " +"/etc/neutron/plugins/openvswitch/ovs_neutron_plugin.ini" +" file:" +msgstr "" + +#: ./doc/install-guide/section_neutron-install.xml714(para) +#: ./doc/install-guide/section_neutron-install.xml1108(para) +msgid "" +"You must use at least the No-Op firewall. Otherwise, Horizon and other " +"OpenStack services cannot get and set required VM boot options." +msgstr "" + +#: ./doc/install-guide/section_neutron-install.xml721(para) +#: ./doc/install-guide/section_neutron-install.xml1114(para) +msgid "Configure the OVS plug-in to start on boot." +msgstr "" + +#: ./doc/install-guide/section_neutron-install.xml727(para) +#: ./doc/install-guide/section_neutron-install.xml1120(para) +#: ./doc/install-guide/section_neutron-install.xml1147(para) +#: ./doc/install-guide/section_neutron-install.xml1522(para) +#: ./doc/install-guide/section_neutron-install.xml1685(para) +msgid "Now, return to the general OVS instructions." +msgstr "" + +#: ./doc/install-guide/section_neutron-install.xml732(title) +msgid "Configure the Neutron OVS plug-in for GRE tunneling" +msgstr "" + +#: ./doc/install-guide/section_neutron-install.xml736(para) +msgid "" +"Configure the OVS plug-in to use GRE tunneling, the " +"br-int integration bridge, the br-tun " +"tunneling bridge, and a local IP for the " +"DATA_INTERFACE tunnel IP. Edit the " +"/etc/neutron/plugins/openvswitch/ovs_neutron_plugin.ini" +" file:" +msgstr "" + +#: ./doc/install-guide/section_neutron-install.xml753(para) +#: ./doc/install-guide/section_neutron-install.xml1175(para) +#: ./doc/install-guide/section_neutron-install.xml1542(para) +#: ./doc/install-guide/section_neutron-install.xml1561(para) +msgid "Return to the general OVS instructions." +msgstr "" + +#: ./doc/install-guide/section_neutron-install.xml759(title) +msgid "Configure the Neutron OVS plug-in for VLANs" +msgstr "" + +#: ./doc/install-guide/section_neutron-install.xml763(para) +msgid "" +"Configure OVS to use VLANS. Edit the " +"/etc/neutron/plugins/openvswitch/ovs_neutron_plugin.ini" +" file:" +msgstr "" + +#: ./doc/install-guide/section_neutron-install.xml773(para) +msgid "" +"Create the bridge for DATA_INTERFACE and add " +"DATA_INTERFACE to it:" +msgstr "" + +#: ./doc/install-guide/section_neutron-install.xml781(para) +msgid "" +"Transfer the IP address for DATA_INTERFACE to the" +" bridge in the same way that you transferred the " +"EXTERNAL_INTERFACE IP address to br-" +"ex. However, do not turn on promiscuous mode." +msgstr "" + +#: ./doc/install-guide/section_neutron-install.xml789(para) +msgid "Return to the OVS general instruction." +msgstr "" + +#: ./doc/install-guide/section_neutron-install.xml798(title) +msgid "Install networking support on a dedicated compute node" +msgstr "" + +#: ./doc/install-guide/section_neutron-install.xml801(para) +msgid "" +"This section details set up for any node that runs the nova-" +"compute component but does not run the full network stack." +msgstr "" + +#: ./doc/install-guide/section_neutron-install.xml806(para) +#: ./doc/install-guide/section_neutron-install.xml1195(para) +msgid "" +"By default, the system-config-firewall automated firewall" +" configuration tool is in place on RHEL. This graphical interface (and a " +"curses-style interface with -tui on the end of the name) " +"enables you to configure IP tables as a basic firewall. You should disable " +"it when you work with Neutron unless you are familiar with the underlying " +"network technologies, as, by default, it blocks various types of network " +"traffic that are important to Neutron. To disable it, simple launch the " +"program and clear the Enabled check box." +msgstr "" + +#: ./doc/install-guide/section_neutron-install.xml816(para) +#: ./doc/install-guide/section_neutron-install.xml1205(para) +msgid "" +"After you successfully set up OpenStack with Neutron, you can re-enable and " +"configure the tool. However, during Neutron set up, disable the tool to make" +" it easier to debug network issues." +msgstr "" + +#: ./doc/install-guide/section_neutron-install.xml823(para) +msgid "" +"Disable packet destination filtering (route verification) to let the " +"networking services route traffic to the VMs. Edit the " +"/etc/sysctl.conf file and run the following command to " +"activate changes:" +msgstr "" + +#: ./doc/install-guide/section_neutron-install.xml833(para) +msgid "" +"Install and configure your networking plug-in components. To install and " +"configure the network plug-in that you chose when you set up your network " +"node, see ." +msgstr "" + +#: ./doc/install-guide/section_neutron-install.xml887(para) +msgid "" +"Configure the core components of Neutron. Edit the " +"/etc/neutron/neutron.conf file:" +msgstr "" + +#: ./doc/install-guide/section_neutron-install.xml947(para) +#: ./doc/install-guide/section_neutron-install.xml1366(para) +msgid "" +"Configure OpenStack Compute to use OpenStack Networking services. Configure " +"the /etc/nova/nova.conf file as per instructions below:" +msgstr "" + +#: ./doc/install-guide/section_neutron-install.xml970(para) +#: ./doc/install-guide/section_neutron-install.xml1389(para) +msgid "" +"Configure OpenStack Compute to use OpenStack Networking services. Edit the " +"/etc/nova/nova.conf file:" +msgstr "" + +#: ./doc/install-guide/section_neutron-install.xml986(para) +msgid "" +"No matter which firewall driver you chose when you configured the network " +"and compute nodes, you must edit the " +"/etc/nova/nova.conf file to set the firewall driver to " +"nova.virt.firewall.NoopFirewallDriver. Because OpenStack " +"Networking handles the firewall, this statement instructs Compute to not use" +" a firewall." +msgstr "" + +#: ./doc/install-guide/section_neutron-install.xml996(para) +msgid "" +"If you want Networking to handle the firewall, edit the " +"/etc/neutron/plugins/openvswitch/ovs_neutron_plugin.ini" +" file to set the firewall_driver option to the firewall for the" +" plug-in. For example, with OVS, edit the file as " +"follows:" +msgstr "" + +#: ./doc/install-guide/section_neutron-install.xml1011(para) +msgid "" +"If you do not want to use a firewall in Compute or Networking, edit both " +"configuration files and set " +"firewall_driver=nova.virt.firewall.NoopFirewallDriver. Also, " +"edit the /etc/nova/nova.conf file and comment out or " +"remove the security_group_api=neutron statement." +msgstr "" + +#: ./doc/install-guide/section_neutron-install.xml1019(para) +msgid "" +"Otherwise, when you issue commands, the ERROR: " +"The server has either erred or is incapable of performing the requested " +"operation. (HTTP 500) error might be returned." +msgstr "" + +#: ./doc/install-guide/section_neutron-install.xml1029(para) +#: ./doc/install-guide/section_nova-compute.xml239(para) +msgid "Restart the Compute service." +msgstr "" + +#: ./doc/install-guide/section_neutron-install.xml1040(title) +msgid "Install and configure Neutron plug-ins on a dedicated compute node" +msgstr "" + +#: ./doc/install-guide/section_neutron-install.xml1043(title) +msgid "Install the Open vSwitch (OVS) plug-in on a dedicated compute node" +msgstr "" + +#: ./doc/install-guide/section_neutron-install.xml1054(para) +msgid "Restart Open vSwitch:" +msgstr "" + +#: ./doc/install-guide/section_neutron-install.xml1058(para) +msgid "Start Open vSwitch and configure it to start when the system boots:" +msgstr "" + +#: ./doc/install-guide/section_neutron-install.xml1066(para) +msgid "" +"You must set some common configuration options no matter which networking " +"technology you choose to use with Open vSwitch. You must add the br-int integration bridge, which connects to the VMs." +msgstr "" + +#: ./doc/install-guide/section_neutron-install.xml1074(para) +msgid "" +"You must set some common configuration options. You must configure " +"Networking core to use OVS. Edit the " +"/etc/neutron/neutron.conf file:" +msgstr "" + +#: ./doc/install-guide/section_neutron-install.xml1086(para) +msgid "" +"Configure the networking type that you chose when you set up the network " +"node: either GRE tunneling or VLANs." +msgstr "" + +#: ./doc/install-guide/section_neutron-install.xml1095(para) +msgid "" +"You must configure a firewall as well. You should use the same firewall " +"plug-in that you chose to use when you set up the network node. To do this, " +"edit " +"/etc/neutron/plugins/openvswitch/ovs_neutron_plugin.ini" +" file and set the firewall_driver value under the " +"securitygroup to the same value used on the network node." +" For instance, if you chose to use the Hybrid OVS-IPTables plug-in, your " +"configuration looks like this:" +msgstr "" + +#: ./doc/install-guide/section_neutron-install.xml1126(title) +msgid "" +"Configure the Neutron OVS plug-in for GRE tunneling on a " +"dedicated compute node" +msgstr "" + +#: ./doc/install-guide/section_neutron-install.xml1130(para) +msgid "" +"Tell the OVS plug-in to use GRE tunneling with a br-int integration bridge, a br-tun tunneling " +"bridge, and a local IP for the tunnel of " +"DATA_INTERFACE's IP Edit the " +"/etc/neutron/plugins/openvswitch/ovs_neutron_plugin.ini" +" file:" +msgstr "" + +#: ./doc/install-guide/section_neutron-install.xml1144(replaceable) +msgid "DATA_INTERFACE_IP" +msgstr "" + +#: ./doc/install-guide/section_neutron-install.xml1154(title) +msgid "" +"Configure the Neutron OVS plug-in for VLANs on a " +"dedicated compute node" +msgstr "" + +#: ./doc/install-guide/section_neutron-install.xml1158(para) +msgid "" +"Tell OVS to use VLANs. Edit the " +"/etc/neutron/plugins/openvswitch/ovs_neutron_plugin.ini" +" file:" +msgstr "" + +#: ./doc/install-guide/section_neutron-install.xml1164(replaceable) +msgid "DATA_INTERFACE" +msgstr "" + +#: ./doc/install-guide/section_neutron-install.xml1167(para) +msgid "" +"Create the bridge for the DATA_INTERFACE and add " +"DATA_INTERFACE to it, the same way you did on the" +" network node:" +msgstr "" + +#: ./doc/install-guide/section_neutron-install.xml1184(title) +msgid "Install networking support on a dedicated controller node" +msgstr "" + +#: ./doc/install-guide/section_neutron-install.xml1187(para) +msgid "" +"This is for a node which runs the control components of Neutron, but does " +"not run any of the components that provide the underlying functionality " +"(such as the plug-in agent or the L3 agent). If you wish to have a combined " +"controller/compute node follow these instructions, and then those for the " +"compute node." +msgstr "" + +#: ./doc/install-guide/section_neutron-install.xml1212(para) +msgid "Install the server component of Networking and any dependencies." +msgstr "" + +#: ./doc/install-guide/section_neutron-install.xml1223(para) +msgid "" +"Configure Networking to use your MySQL database. Edit the " +"/etc/neutron/neutron.conf file and add the following " +"key under the [database] section. Replace " +"NEUTRON_DBPASS with the password you chose for " +"the Neutron database." +msgstr "" + +#: ./doc/install-guide/section_neutron-install.xml1257(para) +msgid "" +"Configure Networking to use keystone as the Identity Service for " +"authentication." +msgstr "" + +#: ./doc/install-guide/section_neutron-install.xml1261(para) +msgid "" +"Edit the /etc/neutron/neutron.conf file and add the " +"following key under the [DEFAULT] section." +msgstr "" + +#: ./doc/install-guide/section_neutron-install.xml1268(para) +msgid "" +"Add the following keys under the [keystone_authtoken] " +"section. Replace NEUTRON_PASS with the password " +"you chose for the Neutron user in Keystone." +msgstr "" + +#: ./doc/install-guide/section_neutron-install.xml1285(para) +msgid "" +"Edit the /etc/neutron/api-paste.ini file and add the " +"following keys under the [filter:authtoken] section. " +"Replace NEUTRON_PASS with the password you chose " +"for the Neutron user in Keystone." +msgstr "" + +#: ./doc/install-guide/section_neutron-install.xml1338(para) +msgid "" +"Configure Networking to use your message broker. Edit the " +"/etc/neutron/neutron.conf file and add the following " +"keys under the [DEFAULT] section." +msgstr "" + +#: ./doc/install-guide/section_neutron-install.xml1342(para) +msgid "" +"Replace RABBIT_PASS with the password you chose " +"for RabbitMQ." +msgstr "" + +#: ./doc/install-guide/section_neutron-install.xml1358(para) +msgid "" +"Although the controller node does not run any Networking agents, you must " +"install and configure the same plug-in that you configured on the network " +"node." +msgstr "" + +#: ./doc/install-guide/section_neutron-install.xml1361(link) +msgid "" +"Install and configure the Networking plug-ins on a dedicated controller node" +msgstr "" + +#: ./doc/install-guide/section_neutron-install.xml1405(para) +msgid "" +"Regardless of which firewall driver you chose when you configured the " +"network and compute nodes, set this driver as the No-Op firewall. This " +"firewall is a nova firewall, and " +"because neutron handles the " +"Firewall, you must tell nova not " +"to use one." +msgstr "" + +#: ./doc/install-guide/section_neutron-install.xml1412(para) +msgid "" +"When Networking handles the firewall, the option " +"firewall_driver should be set according to the specified plug-" +"in. For example with OVS, edit the " +"/etc/neutron/plugins/openvswitch/ovs_neutron_plugin.ini" +" file:" +msgstr "" + +#: ./doc/install-guide/section_neutron-install.xml1426(para) +msgid "" +"If you do not want to use a firewall in Compute or Networking, set " +"firewall_driver=nova.virt.firewall.NoopFirewallDriver in both " +"config files, and comment out or remove " +"security_group_api=neutron in the " +"/etc/nova/nova.conf file, otherwise you may encounter " +"ERROR: The server has either erred or is incapable of performing " +"the requested operation. (HTTP 500) when issuing " +" commands." +msgstr "" + +#: ./doc/install-guide/section_neutron-install.xml1464(para) +msgid "Restart the Compute and Networking services:" +msgstr "" + +#: ./doc/install-guide/section_neutron-install.xml1471(para) +msgid "Restart the Compute services:" +msgstr "" + +#: ./doc/install-guide/section_neutron-install.xml1477(para) +msgid "" +"Start the Networking service and configure it to start when the system " +"boots:" +msgstr "" + +#: ./doc/install-guide/section_neutron-install.xml1486(title) +msgid "" +"Install and configure the Neutron plug-ins on a dedicated controller node" +msgstr "" + +#: ./doc/install-guide/section_neutron-install.xml1489(title) +msgid "Install the Open vSwitch (OVS) plug-in on a dedicated controller node" +msgstr "" + +#: ./doc/install-guide/section_neutron-install.xml1493(para) +msgid "Install the Open vSwitch plug-in:" +msgstr "" + +#: ./doc/install-guide/section_neutron-install.xml1499(para) +msgid "" +"You must set some common configuration options no matter which networking " +"technology you choose to use with Open vSwitch. You must configure " +"Networking core to use OVS. Edit the " +"/etc/neutron/neutron.conf file:" +msgstr "" + +#: ./doc/install-guide/section_neutron-install.xml1508(para) +msgid "" +"Configure the OVS plug-in for the networking type that " +"you chose when you configured the network node: GRE tunneling or VLANs." +msgstr "" + +#: ./doc/install-guide/section_neutron-install.xml1517(para) +msgid "" +"The dedicated controller node does not need to run Open vSwitch or the Open " +"vSwitch agent." +msgstr "" + +#: ./doc/install-guide/section_neutron-install.xml1528(title) +msgid "" +"Configure the Neutron OVS plug-in for GRE tunneling on a " +"dedicated controller node" +msgstr "" + +#: ./doc/install-guide/section_neutron-install.xml1532(para) +msgid "" +"Tell the OVS plug-in to use GRE tunneling. Edit the " +"/etc/neutron/plugins/openvswitch/ovs_neutron_plugin.ini" +" file:" +msgstr "" + +#: ./doc/install-guide/section_neutron-install.xml1549(title) +msgid "" +"Configure the Neutron OVS plug-in for VLANs on a " +"dedicated controller node" +msgstr "" + +#: ./doc/install-guide/section_neutron-install.xml1553(para) +msgid "" +"Tell OVS to use VLANS. Edit the " +"/etc/neutron/plugins/openvswitch/ovs_neutron_plugin.ini" +" file, as follows:" +msgstr "" + +#: ./doc/install-guide/section_neutron-install.xml1570(title) +msgid "Create the base Neutron networks" +msgstr "" + +#: ./doc/install-guide/section_neutron-install.xml1572(para) +msgid "" +"In these sections, replace SPECIAL_OPTIONS with " +"any options specific to your Networking plug-in choices. See here to " +"check if your plug-in requires any special options." +msgstr "" + +#: ./doc/install-guide/section_neutron-install.xml1581(para) +msgid "" +"Create the ext-net external network. This network " +"represents a slice of the outside world. VMs are not directly linked to this" +" network; instead, they connect to internal networks. Outgoing traffic is " +"routed by Neutron to the external network. Additionally, floating IP " +"addresses from the subnet for ext-net might be assigned " +"to VMs so that the external network can contact them. Neutron routes the " +"traffic appropriately." +msgstr "" + +#: ./doc/install-guide/section_neutron-install.xml1590(replaceable) +#: ./doc/install-guide/section_neutron-install.xml1635(replaceable) +msgid "SPECIAL_OPTIONS" +msgstr "" + +#: ./doc/install-guide/section_neutron-install.xml1593(para) +msgid "" +"Create the associated subnet with the same gateway and CIDR as " +"EXTERNAL_INTERFACE. It does not have DHCP because" +" it represents a slice of the external world:" +msgstr "" + +#: ./doc/install-guide/section_neutron-install.xml1598(replaceable) +msgid "FLOATING_IP_START" +msgstr "" + +#: ./doc/install-guide/section_neutron-install.xml1598(replaceable) +msgid "FLOATING_IP_END" +msgstr "" + +#: ./doc/install-guide/section_neutron-install.xml1599(replaceable) +msgid "EXTERNAL_INTERFACE_GATEWAY" +msgstr "" + +#: ./doc/install-guide/section_neutron-install.xml1600(replaceable) +msgid "EXTERNAL_INTERFACE_CIDR" +msgstr "" + +#: ./doc/install-guide/section_neutron-install.xml1603(para) +msgid "Create one or more initial tenants, for example:" +msgstr "" + +#: ./doc/install-guide/section_neutron-install.xml1604(replaceable) +#: ./doc/install-guide/section_neutron-install.xml1619(replaceable) +msgid "DEMO_TENANT" +msgstr "" + +#: ./doc/install-guide/section_neutron-install.xml1605(para) +msgid "See for further details." +msgstr "" + +#: ./doc/install-guide/section_neutron-install.xml1607(para) +msgid "See for further details." +msgstr "" + +#: ./doc/install-guide/section_neutron-install.xml1611(para) +msgid "" +"Create the router attached to the external network. This router routes " +"traffic to the internal subnets as appropriate. You can create it under a " +"given tenant: Append --tenant-id option with a value of " +"DEMO_TENANT_ID to the command." +msgstr "" + +#: ./doc/install-guide/section_neutron-install.xml1617(para) +msgid "" +"Use the following to quickly get the DEMO_TENANT " +"tenant-id:" +msgstr "" + +#: ./doc/install-guide/section_neutron-install.xml1620(para) +msgid "Then create the router:" +msgstr "" + +#: ./doc/install-guide/section_neutron-install.xml1621(replaceable) +#: ./doc/install-guide/section_neutron-install.xml1635(replaceable) +#: ./doc/install-guide/section_neutron-install.xml1636(replaceable) +msgid "DEMO_TENANT_ID" +msgstr "" + +#: ./doc/install-guide/section_neutron-install.xml1624(para) +msgid "" +"Connect the router to ext-net by setting the gateway for " +"the router as ext-net:" +msgstr "" + +#: ./doc/install-guide/section_neutron-install.xml1627(replaceable) +#: ./doc/install-guide/section_neutron-install.xml1637(replaceable) +#: ./doc/install-guide/section_neutron-install.xml1668(replaceable) +msgid "EXT_TO_INT_ID" +msgstr "" + +#: ./doc/install-guide/section_neutron-install.xml1627(replaceable) +#: ./doc/install-guide/section_neutron-install.xml1667(replaceable) +msgid "EXT_NET_ID" +msgstr "" + +#: ./doc/install-guide/section_neutron-install.xml1630(para) +msgid "" +"Create an internal network for DEMO_TENANT (and " +"associated subnet over an arbitrary internal IP range, such as, " +"10.5.5.0/24), and connect it to the router by setting it " +"as a port:" +msgstr "" + +#: ./doc/install-guide/section_neutron-install.xml1637(replaceable) +msgid "DEMO_NET_SUBNET_ID" +msgstr "" + +#: ./doc/install-guide/section_neutron-install.xml1640(para) +msgid "" +"Check the special options page for your plug-in for remaining steps. Now, " +"return to the general OVS instructions." +msgstr "" + +#: ./doc/install-guide/section_neutron-install.xml1647(title) +msgid "Plug-in-specific Neutron network options" +msgstr "" + +#: ./doc/install-guide/section_neutron-install.xml1650(title) +msgid "Open vSwitch Network configuration options" +msgstr "" + +#: ./doc/install-guide/section_neutron-install.xml1653(title) +msgid "GRE tunneling network options" +msgstr "" + +#: ./doc/install-guide/section_neutron-install.xml1655(para) +msgid "" +"While this guide currently enables network namespaces by default, you can " +"disable them if you have issues or your kernel does not support them. If you" +" disabled namespaces, you must perform some additional configuration for the" +" L3 agent." +msgstr "" + +#: ./doc/install-guide/section_neutron-install.xml1660(para) +msgid "" +"After you create all the networks, tell the L3 agent what the external " +"network ID is, as well as the ID of the router associated with this machine " +"(because you are not using namespaces, there can be only one router for each" +" machine). To do this, edit the " +"/etc/neutron/l3_agent.ini file:" +msgstr "" + +#: ./doc/install-guide/section_neutron-install.xml1669(para) +msgid "Then, restart the L3 agent:" +msgstr "" + +#: ./doc/install-guide/section_neutron-install.xml1672(para) +msgid "When creating networks, you should use the options:" +msgstr "" + +#: ./doc/install-guide/section_neutron-install.xml1675(para) +msgid "" +"SEG_ID should be 2 for the " +"external network, and just any unique number inside the tunnel range " +"specified before for any other network." +msgstr "" + +#: ./doc/install-guide/section_neutron-install.xml1680(para) +msgid "" +"These options are not needed beyond the first network, as Neutron " +"automatically increments the segmentation id and copy the network type " +"option for any additional networks." +msgstr "" + +#: ./doc/install-guide/section_neutron-install.xml1690(title) +msgid "VLAN network options" +msgstr "" + +#: ./doc/install-guide/section_neutron-install.xml1691(para) +msgid "When creating networks, use these options:" +msgstr "" + +#: ./doc/install-guide/section_neutron-install.xml1693(para) +msgid "" +"SEG_ID should be 2 for the " +"external network, and just any unique number inside the vlan range specified" +" above for any other network." +msgstr "" + +#: ./doc/install-guide/section_neutron-install.xml1698(para) +msgid "" +"These options are not needed beyond the first network, as Neutron " +"automatically increments the segmentation ID and copies the network type and" +" physical network options for any additional networks. They are only needed " +"if you wish to modify those values in any way." +msgstr "" + +#: ./doc/install-guide/section_neutron-install.xml1706(para) +msgid "" +"Some NICs have Linux drivers that do not handle VLANs properly. See the " +"ovs-vlan-bug-workaround and ovs-vlan-" +"test man pages for more information. Additionally, you might try " +"turning off rx-vlan-offload and tx-vlan-" +"offload by using ethtool on the " +"DATA_INTERFACE. Another potential caveat to VLAN " +"functionality is that VLAN tags add an additional 4 bytes to the packet " +"size. If your NICs cannot handle large packets, make sure to set the MTU to " +"a value that is 4 bytes less than the normal value on the " +"DATA_INTERFACE." +msgstr "" + +#: ./doc/install-guide/section_neutron-install.xml1721(para) +msgid "" +"If you run OpenStack inside a virtualized environment (for testing " +"purposes), switching to the virtio NIC type (or a similar" +" technology if you are not using KVM/QEMU to run your host VMs) might solve " +"the issue." +msgstr "" + +#: ./doc/install-guide/ch_debconf.xml6(title) +msgid "Configure OpenStack with debconf" +msgstr "" + +#. When image changes, this message will be marked fuzzy or untranslated for +#. you. +#. It doesn't matter what you translate it to: it's not used at all. +#: ./doc/install-guide/ch_overview.xml61(None) +msgid "" +"@@image: 'figures/basic-architecture.svg'; " +"md5=33d7a8c99d42020ff657f85d80cc06bd" +msgstr "" + +#: ./doc/install-guide/ch_overview.xml6(title) +msgid "Architecture" +msgstr "" + +#: ./doc/install-guide/ch_overview.xml7(para) +msgid "" +"This install guide offers a few of the many ways to install OpenStack " +"components and have them work together. It is meant as a \"choose your own " +"adventure\" guide, not a comprehensive guide. The OpenStack " +"Configuration Reference lists every option in all OpenStack " +"services. Before you begin an installation adventure, here are some things " +"you should know about OpenStack concepts." +msgstr "" + +#: ./doc/install-guide/ch_overview.xml25(title) +msgid "Example architectures" +msgstr "" + +#: ./doc/install-guide/ch_overview.xml26(para) +msgid "" +"This guide enables you to choose your own OpenStack adventure. OpenStack is " +"highly configurable to meet different needs with various compute, " +"networking, and storage options." +msgstr "" + +#: ./doc/install-guide/ch_overview.xml29(para) +msgid "This guide uses the following example architectures:" +msgstr "" + +#: ./doc/install-guide/ch_overview.xml32(para) +#: ./doc/install-guide/ch_overview.xml57(title) +msgid "Basic architecture with legacy networking" +msgstr "" + +#: ./doc/install-guide/ch_overview.xml35(para) +msgid "" +"The controller node runs the Identity Service, Image Service, dashboard, and" +" management portion of Compute. It also contains the associated API " +"services, MySQL databases, and messaging system." +msgstr "" + +#: ./doc/install-guide/ch_overview.xml41(para) +msgid "" +"The compute node runs the hypervisor portion of Compute, which operates " +"tenant virtual machines. By default, Compute uses " +"KVM as the " +"hypervisor. Compute also provisions and operates " +"tenant networks and implements security groups. You can run more than one compute node." +msgstr "" + +#: ./doc/install-guide/ch_overview.xml52(para) +msgid "When implementing this architecture, skip ." +msgstr "" + +#: ./doc/install-guide/ch_overview.xml67(para) +#: ./doc/install-guide/ch_overview.xml97(title) +msgid "Basic architecture with OpenStack Networking (Neutron)" +msgstr "" + +#: ./doc/install-guide/ch_overview.xml70(para) +msgid "" +"The controller node runs the Identity Service, Image Service, dashboard, and" +" management portions of Compute and Networking. It also contains the " +"associated API services, MySQL databases, and messaging system." +msgstr "" + +#: ./doc/install-guide/ch_overview.xml76(para) +msgid "" +"The network node runs the Networking plug-in agent and several layer 3 " +"agents that provision tenant networks and provide services to them, " +"including routing, NAT, and DHCP. It also handles " +"external (internet) connectivity for tenant virtual machines." +msgstr "" + +#: ./doc/install-guide/ch_overview.xml85(para) +msgid "" +"The compute node runs the hypervisor portion of Compute, which operates " +"tenant virtual machines. By default, Compute uses KVM as the hypervisor. The" +" compute node also runs the Networking plug-in agent, which operates tenant " +"networks and implements security groups. You can run more than one compute " +"node." +msgstr "" + +#: ./doc/install-guide/ch_overview.xml92(para) +msgid "" +"When implementing this architecture, skip ." +msgstr "" + +#: ./doc/install-guide/ch_overview.xml107(para) +msgid "" +"You can add nodes that run Block Storage or Object Storage to either of " +"these architectures." +msgstr "" + +#: ./doc/install-guide/section_dashboard-install.xml13(title) +msgid "Install the dashboard" +msgstr "" + +#: ./doc/install-guide/section_dashboard-install.xml14(para) +msgid "" +"Before you can install and configure the dashboard, meet the requirements in" +" ." +msgstr "" + +#: ./doc/install-guide/section_dashboard-install.xml18(para) +msgid "" +"When you install only Object Storage and the Identity Service, even if you " +"install the dashboard, it does not pull up projects and is unusable." +msgstr "" + +#: ./doc/install-guide/section_dashboard-install.xml22(para) +msgid "" +"For more information about how to deploy the dashboard, see deployment" +" topics in the developer documentation." +msgstr "" + +#: ./doc/install-guide/section_dashboard-install.xml28(para) +msgid "" +"Install the dashboard on the node that can contact the Identity Service as " +"root:" +msgstr "" + +#: ./doc/install-guide/section_dashboard-install.xml34(title) +msgid "Note for Ubuntu users" +msgstr "" + +#: ./doc/install-guide/section_dashboard-install.xml36(para) +msgid "" +"Remove the openstack-dashboard-ubuntu-theme package. This" +" theme prevents translations, several menus as well as the network map from " +"rendering correctly: " +msgstr "" + +#: ./doc/install-guide/section_dashboard-install.xml45(title) +msgid "Note for Debian users" +msgstr "" + +#: ./doc/install-guide/section_dashboard-install.xml46(para) +msgid "To install the Apache package:" +msgstr "" + +#: ./doc/install-guide/section_dashboard-install.xml48(para) +msgid "" +"This command installs and configures Apache correctly, provided that the " +"user asks for it during the debconf prompts. The default " +"SSL certificate is self-signed, and it is probably wise to have it signed by" +" a root Certificate Authority (CA)." +msgstr "" + +#: ./doc/install-guide/section_dashboard-install.xml57(para) +msgid "" +"Modify the value of CACHES['default']['LOCATION'] in " +"/etc/openstack-" +"dashboard/local_settings.py/etc/openstack-" +"dashboard/local_settings/usr/share" +"/openstack-dashboard/openstack_dashboard/local/local_settings.py " +"to match the ones set in /etc/memcached.conf/etc/sysconfig/memcached." +msgstr "" + +#: ./doc/install-guide/section_dashboard-install.xml69(para) +msgid "" +"Open /etc/openstack-" +"dashboard/local_settings.py/etc/openstack-dashboard/local_settings" +" and look for this line:" +msgstr "" + +#: ./doc/install-guide/section_dashboard-install.xml82(title) +#: ./doc/install-guide/object-storage/section_object-storage-sys-requirements.xml25(td) +msgid "Notes" +msgstr "" + +#: ./doc/install-guide/section_dashboard-install.xml85(para) +msgid "" +"The address and port must match the ones set in /etc/memcached.conf/etc/sysconfig/memcached." +msgstr "" + +#: ./doc/install-guide/section_dashboard-install.xml90(para) +msgid "" +"If you change the memcached settings, you must restart the Apache web server" +" for the changes to take effect." +msgstr "" + +#: ./doc/install-guide/section_dashboard-install.xml95(para) +msgid "" +"You can use options other than memcached option for session storage. Set the" +" session back-end through the SESSION_ENGINE option." +msgstr "" + +#: ./doc/install-guide/section_dashboard-install.xml102(para) +msgid "" +"To change the timezone, use the dashboard or edit the /etc/openstack-" +"dashboard/local_settings/etc" +"/openstack-dashboard/local_settings.py/usr/share/openstack-" +"dashboard/openstack_dashboard/local/local_settings.py file." +msgstr "" + +#: ./doc/install-guide/section_dashboard-install.xml111(para) +msgid "Change the following parameter: TIME_ZONE = \"UTC\"" +msgstr "" + +#: ./doc/install-guide/section_dashboard-install.xml118(para) +msgid "" +"Update the ALLOWED_HOSTS in " +"local_settings.py to include the addresses you wish to " +"access the dashboard from." +msgstr "" + +#: ./doc/install-guide/section_dashboard-install.xml122(para) +msgid "" +"Edit /etc/openstack-" +"dashboard/local_settings/etc" +"/openstack-dashboard/local_settings.py/usr/share/openstack-" +"dashboard/openstack_dashboard/local/local_settings.py:" +msgstr "" + +#: ./doc/install-guide/section_dashboard-install.xml132(para) +msgid "" +"This guide assumes that you are running the Dashboard on the controller " +"node. You can easily run the dashboard on a separate server, by changing the" +" appropriate settings in local_settings.py." +msgstr "" + +#: ./doc/install-guide/section_dashboard-install.xml137(para) +msgid "" +"Edit /etc/openstack-" +"dashboard/local_settings/etc" +"/openstack-dashboard/local_settings.py/usr/share/openstack-" +"dashboard/openstack_dashboard/local/local_settings.py and change " +"OPENSTACK_HOST to the hostname of your Identity Service:" +msgstr "" + +#: ./doc/install-guide/section_dashboard-install.xml149(para) +msgid "Setup Apache configuration: " +msgstr "" + +#: ./doc/install-guide/section_dashboard-install.xml156(para) +msgid "" +"By default, the openstack-dashboard package enables" +" a database as session store. Before you continue, either change the session" +" store set up as described in or " +"finish the setup of the database session store as explained in ." +msgstr "" + +#: ./doc/install-guide/section_dashboard-install.xml166(para) +msgid "Start the Apache web server and memcached:" +msgstr "" + +#: ./doc/install-guide/section_dashboard-install.xml179(para) +msgid "" +"You can now access the dashboard at http://controller/horizonhttps://controller/http://controller/dashboardhttp://controller." +msgstr "" + +#: ./doc/install-guide/section_dashboard-install.xml186(para) +msgid "" +"Login with credentials for any user that you created with the OpenStack " +"Identity Service." +msgstr "" + +#: ./doc/install-guide/section_heat-install.xml5(title) +msgid "Install the Orchestration service" +msgstr "" + +#: ./doc/install-guide/section_heat-install.xml8(para) +#: ./doc/install-guide/section_heat-install.xml24(para) +msgid "Install the OpenStack Orchestration service on the controller node:" +msgstr "" + +#: ./doc/install-guide/section_heat-install.xml13(para) +msgid "" +"Respond to prompts for database " +"management, [keystone_authtoken] " +"settings, RabbitMQ " +"credentials and API " +"endpoint registration." +msgstr "" + +#: ./doc/install-guide/section_heat-install.xml33(para) +msgid "" +"In the configuration file, specify the location of the database where the " +"Orchestration service stores data. These examples use a MySQL database with " +"a heat user on the controller node. Replace " +"HEAT_DBPASS with the password for the database " +"user:" +msgstr "" + +#: ./doc/install-guide/section_heat-install.xml40(replaceable) +#: ./doc/install-guide/section_heat-install.xml46(replaceable) +#: ./doc/install-guide/section_heat-install.xml61(replaceable) +#: ./doc/install-guide/section_heat-install.xml63(replaceable) +msgid "HEAT_DBPASS" +msgstr "" + +#: ./doc/install-guide/section_heat-install.xml41(para) +msgid "" +"Edit /etc/heat/heat.conf and change the " +"[DEFAULT] section." +msgstr "" + +#: ./doc/install-guide/section_heat-install.xml50(para) +msgid "" +"By default, the Ubuntu packages create an SQLite database. Delete the " +"heat.sqlite file that was created in the " +"/var/lib/heat/ directory so that it does not get used " +"by mistake." +msgstr "" + +#: ./doc/install-guide/section_heat-install.xml56(para) +msgid "" +"Use the password that you set previously to log in as " +"root and create a heat database user:" +msgstr "" + +#: ./doc/install-guide/section_heat-install.xml66(para) +msgid "Create the heat service tables:" +msgstr "" + +#: ./doc/install-guide/section_heat-install.xml69(para) +msgid "Ignore DeprecationWarning errors." +msgstr "" + +#: ./doc/install-guide/section_heat-install.xml74(para) +msgid "" +"The Ubuntu packages do not correctly set up logging. Edit the " +"/etc/heat/heat.conf file and change the " +"[DEFAULT] section:" +msgstr "" + +#: ./doc/install-guide/section_heat-install.xml88(para) +msgid "" +"Configure the Orchestration Service to use the RabbitMQ message broker." +msgstr "" + +#: ./doc/install-guide/section_heat-install.xml90(para) +msgid "" +"Edit /etc/heat/heat.conf and modify the " +"[DEFAULT] section:" +msgstr "" + +#: ./doc/install-guide/section_heat-install.xml99(para) +msgid "" +"Create a heat user that the Orchestration service can use" +" to authenticate with the Identity Service. Use the " +"service tenant and give the user the " +"admin role:" +msgstr "" + +#: ./doc/install-guide/section_heat-install.xml103(replaceable) +#: ./doc/install-guide/section_heat-install.xml119(replaceable) +msgid "HEAT_PASS" +msgstr "" + +#: ./doc/install-guide/section_heat-install.xml104(replaceable) +msgid "heat@example.com" +msgstr "" + +#: ./doc/install-guide/section_heat-install.xml108(para) +msgid "" +"Edit the /etc/heat/heat.conf file to change the " +"[keystone_authtoken] and " +"[ec2_authtoken] sections to add credentials to the " +"Orchestration Service:" +msgstr "" + +#: ./doc/install-guide/section_heat-install.xml125(para) +msgid "" +"Register the Heat and CloudFormation APIs with the Identity Service so that " +"other OpenStack services can locate these APIs. Register the service and " +"specify the endpoint:" +msgstr "" + +#: ./doc/install-guide/section_heat-install.xml151(para) +msgid "" +"Start the heat-api, heat-api-cfn and heat-engine services and configure them to start when the " +"system boots:" +msgstr "" + +#: ./doc/install-guide/section_ceilometer-nova.xml7(title) +msgid "Install the Compute agent for the Telemetry service" +msgstr "" + +#: ./doc/install-guide/section_ceilometer-nova.xml9(para) +msgid "" +"OpenStack Telemetry is an API service that provides a collector and a range " +"of disparate agents. This procedure details how to install the agent that " +"runs on the compute node." +msgstr "" + +#: ./doc/install-guide/section_ceilometer-nova.xml14(para) +msgid "Install the Telemetry service on the Compute node:" +msgstr "" + +#: ./doc/install-guide/section_ceilometer-nova.xml20(para) +msgid "" +"Set the following options in the /etc/nova/nova.conf " +"file:" +msgstr "" + +#: ./doc/install-guide/section_ceilometer-nova.xml30(para) +msgid "" +"The option is a multi valued option, " +"which openstack-config cannot set properly. See " +"." +msgstr "" + +#: ./doc/install-guide/section_ceilometer-nova.xml36(para) +msgid "" +"Edit the /etc/nova/nova.conf file and add the following" +" lines to the [DEFAULT] section:" +msgstr "" + +#: ./doc/install-guide/section_ceilometer-nova.xml53(para) +msgid "Restart the Compute service:" +msgstr "" + +#: ./doc/install-guide/section_ceilometer-nova.xml58(para) +msgid "" +"You must set the secret key that you defined previously. The Telemetry " +"service nodes share this key as a shared secret:" +msgstr "" + +#: ./doc/install-guide/section_ceilometer-nova.xml62(para) +msgid "" +"Edit the /etc/ceilometer/ceilometer.conf file and " +"change these lines in the [DEFAULT] section. Replace " +"CEILOMETER_TOKEN with the ceilometer token that " +"you created previously:" +msgstr "" + +#: ./doc/install-guide/section_ceilometer-nova.xml83(para) +msgid "Configure the QPid access:" +msgstr "" + +#: ./doc/install-guide/section_ceilometer-nova.xml88(para) +msgid "Add the Identity service credentials:" +msgstr "" + +#: ./doc/install-guide/section_ceilometer-nova.xml140(para) +msgid "Start the service and configure it to start when the system boots:" +msgstr "" + +#: ./doc/install-guide/section_neutron-deploy-use-cases.xml6(title) +msgid "Neutron deployment use cases" +msgstr "" + +#: ./doc/install-guide/section_neutron-deploy-use-cases.xml7(para) +msgid "" +"This section describes how to configure the Networking service and its " +"components for some typical use cases." +msgstr "" + +#: ./doc/install-guide/section_nova-compute.xml5(title) +msgid "Configure a Compute node" +msgstr "" + +#: ./doc/install-guide/section_nova-compute.xml6(para) +msgid "" +"After you configure the Compute service on the controller node, you must " +"configure another system as a Compute node. The Compute node receives " +"requests from the controller node and hosts virtual machine instances. You " +"can run all services on a single node, but the examples in this guide use " +"separate systems. This makes it easy to scale horizontally by adding " +"additional Compute nodes following the instructions in this section." +msgstr "" + +#: ./doc/install-guide/section_nova-compute.xml13(para) +msgid "" +"The Compute service relies on a hypervisor to run virtual machine instances." +" OpenStack can use various hypervisors, but this guide uses KVM." +msgstr "" + +#: ./doc/install-guide/section_nova-compute.xml18(para) +msgid "" +"Configure the system. Use the instructions in ," +" but note the following differences from the controller node:" +msgstr "" + +#: ./doc/install-guide/section_nova-compute.xml23(para) +msgid "" +"Use different IP addresses when you configure eth0. " +"This guide uses 192.168.0.11 for the internal network. Do" +" not configure eth1 with a static IP address. The " +"networking component of OpenStack assigns and configures an IP address." +msgstr "" + +#: ./doc/install-guide/section_nova-compute.xml31(para) +msgid "" +"Set the host name to compute1. To verify, use the " +"uname -n parameter. Ensure that the IP addresses and host names" +" for both nodes are listed in the /etc/hosts file on " +"each system." +msgstr "" + +#: ./doc/install-guide/section_nova-compute.xml38(para) +msgid "" +"Synchronize from the controller node. Follow the instructions in ." +msgstr "" + +#: ./doc/install-guide/section_nova-compute.xml42(para) +msgid "" +"Install the MySQL client libraries. You do not need to install the MySQL " +"database server or start the MySQL service." +msgstr "" + +#: ./doc/install-guide/section_nova-compute.xml47(para) +msgid "" +"Enable the OpenStack packages for the distribution that you are using. See " +"." +msgstr "" + +#: ./doc/install-guide/section_nova-compute.xml54(para) +msgid "" +"After you configure the operating system, install the appropriate packages " +"for the Compute service." +msgstr "" + +#: ./doc/install-guide/section_nova-compute.xml58(para) +msgid "" +"When prompted to create a supermin appliance, respond " +"." +msgstr "" + +#: ./doc/install-guide/section_nova-compute.xml63(para) +msgid "" +"To use the meta-packages and install other components on your compute node, " +"such as OVS Networking and Ceilometer agents, run this command:" +msgstr "" + +#: ./doc/install-guide/section_nova-compute.xml67(para) +msgid "" +"The controller node has the openstack-proxy-node and " +"openstack-toaster meta-packages that install openstack-proxy-node and openstack-toaster at " +"the same time." +msgstr "" + +#: ./doc/install-guide/section_nova-compute.xml79(para) +msgid "" +"Respond to the prompts for database management, [keystone_authtoken] " +"settings, RabbitMQ " +"credentials, and API " +"endpoint registration." +msgstr "" + +#: ./doc/install-guide/section_nova-compute.xml88(para) +msgid "" +"For security reasons, the Linux kernel is not readable by normal users which" +" restricts hypervisor services such as qemu and libguestfs. For details, see" +" this " +"bug. To make the current kernel readable, run: To " +"also enable this override for all future kernel updates, create the file " +"/etc/kernel/postinst.d/statoverride " +"containing: Remember to make the file executable: " +"" +msgstr "" + +#: ./doc/install-guide/section_nova-compute.xml107(para) +msgid "Edit the /etc/nova/nova.conf configuration file:" +msgstr "" + +#: ./doc/install-guide/section_nova-compute.xml118(para) +msgid "" +"Edit the /etc/nova/nova.conf configuration file and add" +" these lines to the appropriate sections:" +msgstr "" + +#: ./doc/install-guide/section_nova-compute.xml131(para) +msgid "" +"Configure the Compute Service to use the Qpid message broker by setting " +"these configuration keys:" +msgstr "" + +#: ./doc/install-guide/section_nova-compute.xml143(para) +msgid "" +"Configure the Compute Service to use the RabbitMQ message broker by setting " +"these configuration keys:" +msgstr "" + +#: ./doc/install-guide/section_nova-compute.xml152(para) +msgid "Configure Compute to provide remote console access to instances." +msgstr "" + +#: ./doc/install-guide/section_nova-compute.xml159(para) +msgid "" +"Edit /etc/nova/nova.conf and add the following keys " +"under the [DEFAULT] section:" +msgstr "" + +#: ./doc/install-guide/section_nova-compute.xml173(para) +msgid "" +"Specify the host that runs the Image Service. " +"Edit /etc/nova/nova.conf file and add these lines to " +"the [DEFAULT] section:" +msgstr "" + +#: ./doc/install-guide/section_nova-compute.xml184(para) +msgid "" +"If you install Compute on a virtual machine for testing purposes, you must " +"determine whether your hypervisor and/or CPU support nested hardware " +"acceleration using the following command:" +msgstr "" + +#: ./doc/install-guide/section_nova-compute.xml189(para) +msgid "" +"If this command returns a value of one or greater, your" +" hypervisor and/or CPU support nested hardware acceleration which requires " +"no additional configuration." +msgstr "" + +#: ./doc/install-guide/section_nova-compute.xml193(para) +msgid "" +"If this command returns a value of zero, your " +"hypervisor and/or CPU do not support nested hardware acceleration and " +"libvirt must use QEMU instead of KVM. Edit the " +"[DEFAULT] section in the /etc/nova/nova-" +"compute.conf file to modify this key:" +msgstr "" + +#: ./doc/install-guide/section_nova-compute.xml203(para) +msgid "" +"If this command returns a value of zero, your " +"hypervisor and/or CPU do not support nested hardware acceleration and " +"libvirt must use QEMU instead of KVM. Configure " +"libvirt to use QEMU:" +msgstr "" + +#: ./doc/install-guide/section_nova-compute.xml211(para) +msgid "" +"Edit the /etc/nova/api-paste.ini file to add the " +"credentials to the [filter:authtoken] section:" +msgstr "" + +#: ./doc/install-guide/section_nova-compute.xml215(para) +msgid "" +"Files with the extension .ini sometimes need to be " +"edited during initial setup. However, they should not be used for general " +"configuration tasks." +msgstr "" + +#: ./doc/install-guide/section_nova-compute.xml229(para) +msgid "" +"Ensure that the " +"option is set in /etc/nova/nova.conf file." +msgstr "" + +#: ./doc/install-guide/section_nova-compute.xml236(para) +msgid "" +"Start the Compute service and configure it to start when the system boots." +msgstr "" + +#: ./doc/install-guide/section_nova-compute.xml253(para) +msgid "Remove the SQLite database created by the packages:" +msgstr "" + +#. When image changes, this message will be marked fuzzy or untranslated for +#. you. +#. It doesn't matter what you translate it to: it's not used at all. +#: ./doc/install-guide/section_glance-install.xml40(None) +msgid "" +"@@image: 'figures/debconf-screenshots/glance-common_pipeline_flavor.png'; " +"md5=78bef92c36a140ad042074f6345d8917" +msgstr "" + +#: ./doc/install-guide/section_glance-install.xml7(title) +msgid "Install the Image Service" +msgstr "" + +#: ./doc/install-guide/section_glance-install.xml8(para) +msgid "" +"The OpenStack Image Service acts as a registry for virtual disk images. " +"Users can add new images or take a snapshot of an image from an existing " +"server for immediate storage. Use snapshots for back up and as templates to " +"launch new servers. You can store registered images in Object Storage or in " +"other locations. For example, you can store images in simple file systems or" +" external web servers." +msgstr "" + +#: ./doc/install-guide/section_glance-install.xml16(para) +msgid "" +"This procedure assumes you set the appropriate environment variables to your" +" credentials as described in ." +msgstr "" + +#: ./doc/install-guide/section_glance-install.xml22(para) +msgid "Install the Image Service on the controller node:" +msgstr "" + +#: ./doc/install-guide/section_glance-install.xml29(para) +msgid "" +"Respond to prompts for database " +"management, [keystone_authtoken] " +"settings, RabbitMQ " +"credentials and API " +"endpoint registration. You must also select the caching type:" +msgstr "" + +#: ./doc/install-guide/section_glance-install.xml45(para) +msgid "" +"The Image Service stores information about images in a database. The " +"examples in this guide use the MySQL database that is used by other " +"OpenStack services." +msgstr "" + +#: ./doc/install-guide/section_glance-install.xml48(para) +msgid "" +"Configure the location of the database. The Image Service provides the " +"glance-api and glance-registry services, each with its own " +"configuration file. You must update both configuration files throughout this" +" section. Replace GLANCE_DBPASS with your Image " +"Service database password." +msgstr "" + +#: ./doc/install-guide/section_glance-install.xml57(replaceable) +#: ./doc/install-guide/section_glance-install.xml59(replaceable) +#: ./doc/install-guide/section_glance-install.xml77(replaceable) +#: ./doc/install-guide/section_glance-install.xml91(replaceable) +#: ./doc/install-guide/section_glance-install.xml93(replaceable) +msgid "GLANCE_DBPASS" +msgstr "" + +#: ./doc/install-guide/section_glance-install.xml60(para) +msgid "" +"Edit /etc/glance/glance-api.conf and " +"/etc/glance/glance-registry.conf and change the " +"[DEFAULT] section." +msgstr "" + +#: ./doc/install-guide/section_glance-install.xml74(para) +msgid "" +"Use the command to create the Image Service database and " +"tables and a glance database user:" +msgstr "" + +#: ./doc/install-guide/section_glance-install.xml80(para) +msgid "" +"By default, the Ubuntu packages create an SQLite database. Delete the " +"glance.sqlite file created in the " +"/var/lib/glance/ directory so that it does not get used" +" by mistake." +msgstr "" + +#: ./doc/install-guide/section_glance-install.xml86(para) +msgid "" +"Use the password you created to log in as root and create a " +"glance database user:" +msgstr "" + +#: ./doc/install-guide/section_glance-install.xml96(para) +msgid "Create the database tables for the Image Service:" +msgstr "" + +#: ./doc/install-guide/section_glance-install.xml100(para) +msgid "" +"Create a glance user that the Image Service can use to " +"authenticate with the Identity Service. Choose a password and specify an " +"email address for the glance user. Use the " +"service tenant and give the user the " +"admin role." +msgstr "" + +#: ./doc/install-guide/section_glance-install.xml106(replaceable) +#: ./doc/install-guide/section_glance-install.xml126(replaceable) +#: ./doc/install-guide/section_glance-install.xml138(replaceable) +#: ./doc/install-guide/section_glance-install.xml158(replaceable) +#: ./doc/install-guide/section_glance-install.xml188(replaceable) +msgid "GLANCE_PASS" +msgstr "" + +#: ./doc/install-guide/section_glance-install.xml107(replaceable) +msgid "glance@example.com" +msgstr "" + +#: ./doc/install-guide/section_glance-install.xml111(para) +msgid "" +"Configure the Image Service to use the Identity Service for authentication." +msgstr "" + +#: ./doc/install-guide/section_glance-install.xml113(para) +msgid "" +"Run the following commands and replace " +"GLANCE_PASS with the password you chose for the " +"glance user in the Identity Service:" +msgstr "" + +#: ./doc/install-guide/section_glance-install.xml141(para) +msgid "" +"Edit the /etc/glance/glance-api.conf and " +"/etc/glance/glance-registry.conf files. Replace " +"GLANCE_PASS with the password you chose for the " +"glance user in the Identity Service." +msgstr "" + +#: ./doc/install-guide/section_glance-install.xml148(para) +msgid "" +"Add the following keys under the [keystone_authtoken] " +"section:" +msgstr "" + +#: ./doc/install-guide/section_glance-install.xml161(para) +msgid "" +"Add the following key under the [paste_deploy] section:" +msgstr "" + +#: ./doc/install-guide/section_glance-install.xml170(para) +msgid "" +"Add the credentials to the /etc/glance/glance-api-" +"paste.ini and /etc/glance/glance-registry-" +"paste.ini files." +msgstr "" + +#: ./doc/install-guide/section_glance-install.xml174(para) +msgid "On CentOS, you may need to copy these files to the correct location." +msgstr "" + +#: ./doc/install-guide/section_glance-install.xml180(para) +msgid "" +"Edit each file to set the following options in the " +"[filter:authtoken] section and leave any other existing " +"option as it is." +msgstr "" + +#: ./doc/install-guide/section_glance-install.xml191(para) +msgid "" +"Register the Image Service with the Identity Service so that other OpenStack" +" services can locate it. Register the service and create the endpoint:" +msgstr "" + +#: ./doc/install-guide/section_glance-install.xml203(para) +msgid "" +"Restart the glance service with " +"its new settings." +msgstr "" + +#: ./doc/install-guide/section_glance-install.xml209(para) +msgid "" +"Start the glance-api and " +"glance-registry services and " +"configure them to start when the system boots:" +msgstr "" + +#. When image changes, this message will be marked fuzzy or untranslated for +#. you. +#. It doesn't matter what you translate it to: it's not used at all. +#: ./doc/install-guide/section_debconf-dbconfig-common.xml30(None) +msgid "" +"@@image: 'figures/debconf-screenshots/dbconfig-common_keep_admin_pass.png'; " +"md5=01af4867c16e458306b8abd78a1fccc9" +msgstr "" + +#. When image changes, this message will be marked fuzzy or untranslated for +#. you. +#. It doesn't matter what you translate it to: it's not used at all. +#: ./doc/install-guide/section_debconf-dbconfig-common.xml39(None) +msgid "" +"@@image: 'figures/debconf-screenshots/dbconfig-" +"common_used_for_remote_db.png'; md5=c6ec966bbfdee18ad87456cf4d44a56f" +msgstr "" + +#. When image changes, this message will be marked fuzzy or untranslated for +#. you. +#. It doesn't matter what you translate it to: it's not used at all. +#: ./doc/install-guide/section_debconf-dbconfig-common.xml78(None) +msgid "" +"@@image: 'figures/debconf-screenshots/dbconfig-common_1_configure-with-" +"dbconfig-yes-no.png'; md5=4e9d7bce27cc6c7bd68ce8622c80b60f" +msgstr "" + +#. When image changes, this message will be marked fuzzy or untranslated for +#. you. +#. It doesn't matter what you translate it to: it's not used at all. +#: ./doc/install-guide/section_debconf-dbconfig-common.xml87(None) +msgid "" +"@@image: 'figures/debconf-screenshots/dbconfig-common_2_db-types.png'; " +"md5=a77beb7e13b487cf79716c2140f258c2" +msgstr "" + +#. When image changes, this message will be marked fuzzy or untranslated for +#. you. +#. It doesn't matter what you translate it to: it's not used at all. +#: ./doc/install-guide/section_debconf-dbconfig-common.xml96(None) +msgid "" +"@@image: 'figures/debconf-screenshots/dbconfig-" +"common_3_connection_method.png'; md5=6cc592e5dd5ea404ad7aad98b37a71f6" +msgstr "" + +#. When image changes, this message will be marked fuzzy or untranslated for +#. you. +#. It doesn't matter what you translate it to: it's not used at all. +#: ./doc/install-guide/section_debconf-dbconfig-common.xml105(None) +msgid "" +"@@image: 'figures/debconf-screenshots/dbconfig-" +"common_4_mysql_root_password.png'; md5=873ec338742e37305583e9e692bcfdc6" +msgstr "" + +#. When image changes, this message will be marked fuzzy or untranslated for +#. you. +#. It doesn't matter what you translate it to: it's not used at all. +#: ./doc/install-guide/section_debconf-dbconfig-common.xml114(None) +msgid "" +"@@image: 'figures/debconf-screenshots/dbconfig-" +"common_5_mysql_app_password.png'; md5=3651970770d05892f21d1b5741afbee6" +msgstr "" + +#. When image changes, this message will be marked fuzzy or untranslated for +#. you. +#. It doesn't matter what you translate it to: it's not used at all. +#: ./doc/install-guide/section_debconf-dbconfig-common.xml123(None) +msgid "" +"@@image: 'figures/debconf-screenshots/dbconfig-" +"common_6_mysql_app_password_confirm.png'; " +"md5=060cc90aaf6f6fd5cea718064829c1b1" +msgstr "" + +#: ./doc/install-guide/section_debconf-dbconfig-common.xml6(title) +msgid "Configure the database with dbconfig-common" +msgstr "" + +#: ./doc/install-guide/section_debconf-dbconfig-common.xml7(para) +msgid "" +"The dbconfig-common package provides a standard Debian " +"interface that enables you to configure Debian database parameters. It " +"includes localized prompts for many languages and it supports the OpenStack " +"database back ends: SQLite, MySQL, and PostgreSQL." +msgstr "" + +#: ./doc/install-guide/section_debconf-dbconfig-common.xml12(para) +msgid "" +"By default, the dbconfig-common package configures the " +"OpenStack services to use SQLite3. So if you use debconf " +"in non-interactive mode and without pre-seeding, the OpenStack services that" +" you install use SQLite3." +msgstr "" + +#: ./doc/install-guide/section_debconf-dbconfig-common.xml17(para) +msgid "" +"By default, dbconfig-common does not provide access to " +"database servers over a network. If you want the dbconfig-" +"common package to prompt for remote database servers that are " +"accessed over a network and not through a UNIX socket file, reconfigure it, " +"as follows:" +msgstr "" + +#: ./doc/install-guide/section_debconf-dbconfig-common.xml23(para) +msgid "" +"These screens appear when you re-configure the dbconfig-" +"common package:" +msgstr "" + +#: ./doc/install-guide/section_debconf-dbconfig-common.xml43(para) +msgid "" +"Unlike other debconf prompts, you cannot pre-seed the " +"responses for the dbconfig-common prompts by using " +". Instead, you must create a file in /etc" +"/dbconfig-common. For example, you might create a keystone " +"configuration file for dbconfig-common that is located in" +" /etc/dbconfig-common/keystone.conf, as follows:" +msgstr "" + +#: ./doc/install-guide/section_debconf-dbconfig-common.xml66(para) +msgid "After you create this file, run this command:" +msgstr "" + +#: ./doc/install-guide/section_debconf-dbconfig-common.xml68(para) +msgid "" +"The Identity Service is installed with MySQL as the database back end, " +"keystonedb as database name, and the localhost socket " +"file." +msgstr "" + +#: ./doc/install-guide/section_debconf-dbconfig-common.xml71(para) +msgid "The cinder-common package displays these screens:" +msgstr "" + +#: ./doc/install-guide/section_debconf-dbconfig-common.xml127(para) +msgid "" +"To access a MySQL server remotely, you must make it accessible as root from " +"a remote server. To do so, run the openstack-proxy-node " +"package command:" +msgstr "" + +#: ./doc/install-guide/section_debconf-dbconfig-common.xml131(para) +msgid "" +"Alternatively, if you do not want to install this package, run this script " +"to enable remote root access:" +msgstr "" + +#: ./doc/install-guide/section_debconf-dbconfig-common.xml154(para) +msgid "You must enable remote access before you install OpenStack services." +msgstr "" + +#. When image changes, this message will be marked fuzzy or untranslated for +#. you. +#. It doesn't matter what you translate it to: it's not used at all. +#: ./doc/install-guide/section_keystone-install.xml87(None) +msgid "" +"@@image: 'figures/debconf-screenshots/keystone_1_admin_token.png'; " +"md5=29a51caaf09c3d6e3f0fda73c256a17a" +msgstr "" + +#. When image changes, this message will be marked fuzzy or untranslated for +#. you. +#. It doesn't matter what you translate it to: it's not used at all. +#: ./doc/install-guide/section_keystone-install.xml112(None) +msgid "" +"@@image: 'figures/debconf-" +"screenshots/keystone_2_register_admin_tenant_yes_no.png'; " +"md5=25c9a90b1df2d979aae6ce9975c7285b" +msgstr "" + +#. When image changes, this message will be marked fuzzy or untranslated for +#. you. +#. It doesn't matter what you translate it to: it's not used at all. +#: ./doc/install-guide/section_keystone-install.xml121(None) +msgid "" +"@@image: 'figures/debconf-screenshots/keystone_3_admin_user_name.png'; " +"md5=173cf7ed13252df1425109be588b2ad6" +msgstr "" + +#. When image changes, this message will be marked fuzzy or untranslated for +#. you. +#. It doesn't matter what you translate it to: it's not used at all. +#: ./doc/install-guide/section_keystone-install.xml130(None) +msgid "" +"@@image: 'figures/debconf-screenshots/keystone_4_admin_user_email.png'; " +"md5=b7f0d34350ccc0aa9ae4e766b7ac80c1" +msgstr "" + +#. When image changes, this message will be marked fuzzy or untranslated for +#. you. +#. It doesn't matter what you translate it to: it's not used at all. +#: ./doc/install-guide/section_keystone-install.xml139(None) +msgid "" +"@@image: 'figures/debconf-screenshots/keystone_5_admin_user_pass.png'; " +"md5=e6b32d8d80af90f07a66abc8fb256c84" +msgstr "" + +#. When image changes, this message will be marked fuzzy or untranslated for +#. you. +#. It doesn't matter what you translate it to: it's not used at all. +#: ./doc/install-guide/section_keystone-install.xml148(None) +msgid "" +"@@image: 'figures/debconf-" +"screenshots/keystone_6_admin_user_pass_confirm.png'; " +"md5=1fbf9223e4923c93030d53278d1771cc" +msgstr "" + +#. When image changes, this message will be marked fuzzy or untranslated for +#. you. +#. It doesn't matter what you translate it to: it's not used at all. +#: ./doc/install-guide/section_keystone-install.xml162(None) +msgid "" +"@@image: 'figures/debconf-screenshots/keystone_7_register_endpoint.png'; " +"md5=d24d84133bfee936267e79631a2666e6" +msgstr "" + +#: ./doc/install-guide/section_keystone-install.xml6(title) +msgid "Install the Identity Service" +msgstr "" + +#: ./doc/install-guide/section_keystone-install.xml9(para) +msgid "" +"Install the OpenStack Identity Service on the controller node, together with" +" python-keystoneclient (which is a dependency):" +msgstr "" + +#: ./doc/install-guide/section_keystone-install.xml17(para) +msgid "" +"Answer to the debconf and " +"dbconfig-common questions for " +"setting-up the database." +msgstr "" + +#: ./doc/install-guide/section_keystone-install.xml23(para) +msgid "" +"The Identity Service uses a database to store information. Specify the " +"location of the database in the configuration file. In this guide, we use a " +"MySQL database on the controller node with the username " +"keystone. Replace " +"KEYSTONE_DBPASS with a " +"suitable password for the database user." +msgstr "" + +#: ./doc/install-guide/section_keystone-install.xml30(replaceable) +#: ./doc/install-guide/section_keystone-install.xml50(replaceable) +#: ./doc/install-guide/section_keystone-install.xml65(replaceable) +#: ./doc/install-guide/section_keystone-install.xml67(replaceable) +msgid "KEYSTONE_DBPASS" +msgstr "" + +#: ./doc/install-guide/section_keystone-install.xml31(para) +msgid "" +"Edit /etc/keystone/keystone.conf and change the " +"[sql] section." +msgstr "" + +#: ./doc/install-guide/section_keystone-install.xml44(para) +msgid "" +"Use the command to create the database and tables, as well " +"as a database user called keystone to connect to the " +"database. Replace " +"KEYSTONE_DBPASS with the same " +"password used in the previous step." +msgstr "" + +#: ./doc/install-guide/section_keystone-install.xml53(para) +msgid "" +"By default, the Ubuntu packages create an SQLite database. Delete the " +"keystone.db file created in the " +"/var/lib/keystone/ directory so that it does not get " +"used by mistake." +msgstr "" + +#: ./doc/install-guide/section_keystone-install.xml59(para) +msgid "" +"Use the password that you set previously to log in as root. Create a " +"keystone database user:" +msgstr "" + +#: ./doc/install-guide/section_keystone-install.xml70(para) +msgid "Create the database tables for the Identity Service:" +msgstr "" + +#: ./doc/install-guide/section_keystone-install.xml75(para) +msgid "" +"Define an authorization token to use as a shared secret between the Identity" +" Service and other OpenStack services. Respond to the " +"debconf prompt with the value in the " +"admin_token directive in the keystone.conf" +" file. Use the command to generate this password." +msgstr "" + +#: ./doc/install-guide/section_keystone-install.xml91(para) +msgid "" +"Later, you can verify that the " +"/etc/keystone/keystone.conf file contains the password " +"you have set using debconf: " +msgstr "" + +#: ./doc/install-guide/section_keystone-install.xml99(para) +msgid "" +"If you omit a password (for example by pressing Enter at the " +"debconf prompt, or installing Keystone using the Debconf " +"non-interactive mode) the package generates a random " +"ADMIN_TOKEN value." +msgstr "" + +#: ./doc/install-guide/section_keystone-install.xml105(para) +msgid "Respond to the prompts to create an administrative tenant:" +msgstr "" + +#: ./doc/install-guide/section_keystone-install.xml154(para) +msgid "" +"If this is the first time you have installed the Identity Service, register " +"the Identity Service in the service catalog:" +msgstr "" + +#: ./doc/install-guide/section_keystone-install.xml168(para) +msgid "" +"Define an authorization token to use as a shared secret between the Identity" +" Service and other OpenStack services. Use to generate a " +"random token and store it in the configuration file:" +msgstr "" + +#: ./doc/install-guide/section_keystone-install.xml177(para) +msgid "For SUSE Linux Enterprise use instead as first command:" +msgstr "" + +#: ./doc/install-guide/section_keystone-install.xml180(para) +msgid "" +"Edit /etc/keystone/keystone.conf and change the " +"[DEFAULT] section, replacing ADMIN_TOKEN with the results" +" of the command." +msgstr "" + +#: ./doc/install-guide/section_keystone-install.xml190(para) +msgid "" +"By default, Keystone uses PKI tokens. Create the signing keys and " +"certificates:" +msgstr "" + +#: ./doc/install-guide/section_keystone-install.xml201(para) +msgid "Restart the Identity Service:" +msgstr "" + +#: ./doc/install-guide/section_keystone-install.xml205(para) +msgid "" +"Start the Identity Service and enable it to start when the system boots:" +msgstr "" + +#: ./doc/install-guide/object-storage/section_object-storage-post-install.xml6(title) +msgid "Object Storage post-installation tasks" +msgstr "" + +#: ./doc/install-guide/object-storage/section_object-storage-post-install.xml10(title) +msgid "Add a proxy server" +msgstr "" + +#: ./doc/install-guide/object-storage/section_object-storage-post-install.xml11(para) +msgid "" +"For reliability, you add proxy servers. You can set up an additional proxy " +"node the same way that you set up the first proxy node but with additional " +"configuration steps." +msgstr "" + +#: ./doc/install-guide/object-storage/section_object-storage-post-install.xml15(para) +msgid "" +"After you have more than two proxies, you must load balance them; your " +"storage endpoint (what clients use to connect to your storage) also changes." +" You can select from different strategies for load balancing. For example, " +"you could use round-robin DNS, or a software or hardware load balancer (like" +" pound) in front of the two proxies, and point your storage URL to the load " +"balancer." +msgstr "" + +#: ./doc/install-guide/object-storage/section_object-storage-post-install.xml24(para) +msgid "" +"Configure an initial proxy node. Then, complete these steps to add proxy " +"servers." +msgstr "" + +#: ./doc/install-guide/object-storage/section_object-storage-post-install.xml28(para) +msgid "" +"Update the list of memcache servers in the /etc/swift/proxy-" +"server.conf file for added proxy servers. If you run multiple " +"memcache servers, use this pattern for the multiple IP:port listings in each" +" proxy server configuration file:" +msgstr "" + +#: ./doc/install-guide/object-storage/section_object-storage-post-install.xml42(para) +msgid "" +"Copy ring information to all nodes, including new proxy nodes. Also, ensure " +"that the ring information gets to all storage nodes." +msgstr "" + +#: ./doc/install-guide/object-storage/section_object-storage-post-install.xml49(para) +msgid "" +"After you sync all nodes, make sure that the admin has keys in " +"/etc/swift and the ownership for the ring file is " +"correct." +msgstr "" + +#: ./doc/install-guide/object-storage/section_object-storage-verifying-install.xml6(title) +msgid "Verify the installation" +msgstr "" + +#: ./doc/install-guide/object-storage/section_object-storage-verifying-install.xml7(para) +msgid "" +"You can run these commands from the proxy server or any server that has " +"access to the Identity Service." +msgstr "" + +#: ./doc/install-guide/object-storage/section_object-storage-verifying-install.xml11(para) +msgid "" +"Make sure that your credentials are set up correctly in the " +"openrc.sh file and source it:" +msgstr "" + +#: ./doc/install-guide/object-storage/section_object-storage-verifying-install.xml15(para) +msgid "Run the following command:" +msgstr "" + +#: ./doc/install-guide/object-storage/section_object-storage-verifying-install.xml27(para) +msgid "" +"Run the following commands to upload files to a container. " +"Create the test.txt and test2.txt " +"test files locally if needed." +msgstr "" + +#: ./doc/install-guide/object-storage/section_object-storage-verifying-install.xml34(para) +msgid "" +"Run the following command to download all files from the " +"myfiles container:" +msgstr "" + +#: ./doc/install-guide/object-storage/section_object-storage-install-config-proxy-node.xml6(title) +msgid "Install and configure the proxy node" +msgstr "" + +#: ./doc/install-guide/object-storage/section_object-storage-install-config-proxy-node.xml7(para) +msgid "" +"The proxy server takes each request and looks up locations for the account, " +"container, or object and routes the requests correctly. The proxy server " +"also handles API requests. You enable account management by configuring it " +"in the proxy-server.conf file." +msgstr "" + +#: ./doc/install-guide/object-storage/section_object-storage-install-config-proxy-node.xml13(para) +msgid "" +"The Object Storage processes run under a separate user and group, set by " +"configuration options, and referred to as swift:swiftopenstack-swift:openstack-swift. The default " +"user is swift, which may not" +" exist on your system.openstack-" +"swift." +msgstr "" + +#: ./doc/install-guide/object-storage/section_object-storage-install-config-proxy-node.xml25(para) +msgid "Install swift-proxy service:" +msgstr "" + +#: ./doc/install-guide/object-storage/section_object-storage-install-config-proxy-node.xml31(para) +msgid "Create self-signed cert for SSL:" +msgstr "" + +#: ./doc/install-guide/object-storage/section_object-storage-install-config-proxy-node.xml36(para) +msgid "" +"Modify memcached to listen on the default interfaces on a local, non-public " +"network. Edit this line in the /etc/memcached.conf " +"file:" +msgstr "" + +#: ./doc/install-guide/object-storage/section_object-storage-install-config-proxy-node.xml40(para) +msgid "Change it to:" +msgstr "" + +#: ./doc/install-guide/object-storage/section_object-storage-install-config-proxy-node.xml44(para) +msgid "Restart the memcached server:" +msgstr "" + +#: ./doc/install-guide/object-storage/section_object-storage-install-config-proxy-node.xml48(para) +msgid "" +"RHEL/CentOS/Fedora only: To set up Object Storage to authenticate tokens, " +"set the Identity Service Admin token in the swift proxy file with the " +" command." +msgstr "" + +#: ./doc/install-guide/object-storage/section_object-storage-install-config-proxy-node.xml58(para) +msgid "" +"Ubuntu only: Because the distribution packages do not include a copy of the " +"keystoneauth middleware, ensure that the proxy server includes them:" +msgstr "" + +#: ./doc/install-guide/object-storage/section_object-storage-install-config-proxy-node.xml68(para) +msgid "Create /etc/swift/proxy-server.conf:" +msgstr "" + +#: ./doc/install-guide/object-storage/section_object-storage-install-config-proxy-node.xml72(phrase) +msgid "user = swift" +msgstr "" + +#: ./doc/install-guide/object-storage/section_object-storage-install-config-proxy-node.xml73(phrase) +msgid "user = openstack-swift" +msgstr "" + +#: ./doc/install-guide/object-storage/section_object-storage-install-config-proxy-node.xml120(para) +msgid "" +"If you run multiple memcache servers, put the multiple IP:port listings in " +"the [filter:cache] section of the proxy-server.conf " +"file:" +msgstr "" + +#: ./doc/install-guide/object-storage/section_object-storage-install-config-proxy-node.xml125(para) +msgid "Only the proxy server uses memcache." +msgstr "" + +#: ./doc/install-guide/object-storage/section_object-storage-install-config-proxy-node.xml129(para) +msgid "" +"Create the signing_dir and set its " +"permissions accordingly." +msgstr "" + +#: ./doc/install-guide/object-storage/section_object-storage-install-config-proxy-node.xml138(para) +msgid "" +"Create the account, container, and object rings. The builder command creates" +" a builder file with a few parameters. The parameter with the value of 18 " +"represents 2 ^ 18th, the value that the partition is sized to. Set this " +"“partition power” value based on the total amount of storage you expect your" +" entire ring to use. The value 3 represents the number of replicas of each " +"object, with the last value being the number of hours to restrict moving a " +"partition more than once." +msgstr "" + +#: ./doc/install-guide/object-storage/section_object-storage-install-config-proxy-node.xml154(para) +msgid "For every storage device on each node add entries to each ring:" +msgstr "" + +#: ./doc/install-guide/object-storage/section_object-storage-install-config-proxy-node.xml160(para) +msgid "" +"You must omit the optional STORAGE_REPLICATION_NET_IP" +" parameter if you do not want to use dedicated network for replication." +msgstr "" + +#: ./doc/install-guide/object-storage/section_object-storage-install-config-proxy-node.xml164(para) +msgid "" +"For example, if a storage node has a partition in Zone 1 on IP 10.0.0.1, the" +" storage node has address 10.0.1.1 from replication network. The mount point" +" of this partition is /srv/node/sdb1, and the path in " +"rsyncd.conf is /srv/node/, the DEVICE would be sdb1 and" +" the commands are:" +msgstr "" + +#: ./doc/install-guide/object-storage/section_object-storage-install-config-proxy-node.xml175(para) +msgid "" +"If you assume five zones with one node for each zone, start ZONE at 1. For " +"each additional node, increment ZONE by 1." +msgstr "" + +#: ./doc/install-guide/object-storage/section_object-storage-install-config-proxy-node.xml181(para) +msgid "Verify the ring contents for each ring:" +msgstr "" + +#: ./doc/install-guide/object-storage/section_object-storage-install-config-proxy-node.xml187(para) +msgid "Rebalance the rings:" +msgstr "" + +#: ./doc/install-guide/object-storage/section_object-storage-install-config-proxy-node.xml192(para) +msgid "Rebalancing rings can take some time." +msgstr "" + +#: ./doc/install-guide/object-storage/section_object-storage-install-config-proxy-node.xml196(para) +msgid "" +"Copy the account.ring.gz, " +"container.ring.gz, and " +"object.ring.gz files to each of the Proxy and Storage " +"nodes in /etc/swift." +msgstr "" + +#: ./doc/install-guide/object-storage/section_object-storage-install-config-proxy-node.xml202(para) +msgid "Make sure the swift user owns all configuration files:" +msgstr "" + +#: ./doc/install-guide/object-storage/section_object-storage-install-config-proxy-node.xml207(para) +msgid "Start Proxy services:" +msgstr "" + +#: ./doc/install-guide/object-storage/section_object-storage-network-planning.xml6(title) +msgid "Plan networking for Object Storage" +msgstr "" + +#: ./doc/install-guide/object-storage/section_object-storage-network-planning.xml7(para) +msgid "" +"For both conserving network resources and ensuring that network " +"administrators understand the needs for networks and public IP addresses for" +" providing access to the APIs and storage network as necessary, this section" +" offers recommendations and required minimum sizes. Throughput of at least " +"1000 Mbps is suggested." +msgstr "" + +#: ./doc/install-guide/object-storage/section_object-storage-network-planning.xml15(para) +msgid "A mandatory public network. Connects to the Proxy server." +msgstr "" + +#: ./doc/install-guide/object-storage/section_object-storage-network-planning.xml19(para) +msgid "" +"A mandatory storage network. Not accessible from outside the cluster. All " +"nodes connect to this network." +msgstr "" + +#: ./doc/install-guide/object-storage/section_object-storage-network-planning.xml23(para) +msgid "" +"An optional replication network. Not accessible from outside the cluster. " +"Dedicated to replication traffic among Storage nodes. Must be configured in " +"the Ring." +msgstr "" + +#: ./doc/install-guide/object-storage/section_object-storage-network-planning.xml13(para) +msgid "This guide describes the following networks:" +msgstr "" + +#: ./doc/install-guide/object-storage/section_object-storage-network-planning.xml28(para) +msgid "" +"By default, all of the OpenStack Object Storage services, as well as the " +"rsync daemon on the Storage nodes, are configured to listen on their " +"STORAGE_LOCAL_NET IP addresses." +msgstr "" + +#: ./doc/install-guide/object-storage/section_object-storage-network-planning.xml32(para) +msgid "" +"If you configure a replication network in the Ring, the Account, Container " +"and Object servers listen on both the STORAGE_LOCAL_NET " +"and STORAGE_REPLICATION_NET IP addresses. The rsync " +"daemon only listens on the STORAGE_REPLICATION_NET IP " +"address." +msgstr "" + +#: ./doc/install-guide/object-storage/section_object-storage-network-planning.xml40(term) +msgid "Public Network (Publicly routable IP range)" +msgstr "" + +#: ./doc/install-guide/object-storage/section_object-storage-network-planning.xml42(para) +msgid "" +"Provides public IP accessibility to the API endpoints within the cloud " +"infrastructure." +msgstr "" + +#: ./doc/install-guide/object-storage/section_object-storage-network-planning.xml44(para) +msgid "Minimum size: one IP address for each proxy server." +msgstr "" + +#: ./doc/install-guide/object-storage/section_object-storage-network-planning.xml49(term) +msgid "Storage Network (RFC1918 IP Range, not publicly routable)" +msgstr "" + +#: ./doc/install-guide/object-storage/section_object-storage-network-planning.xml52(para) +msgid "" +"Manages all inter-server communications within the Object Storage " +"infrastructure." +msgstr "" + +#: ./doc/install-guide/object-storage/section_object-storage-network-planning.xml54(para) +msgid "Minimum size: one IP address for each storage node and proxy server." +msgstr "" + +#: ./doc/install-guide/object-storage/section_object-storage-network-planning.xml56(para) +msgid "" +"Recommended size: as above, with room for expansion to the largest your " +"cluster size. For example, 255 or CIDR /24." +msgstr "" + +#: ./doc/install-guide/object-storage/section_object-storage-network-planning.xml62(term) +msgid "Replication Network (RFC1918 IP Range, not publicly routable)" +msgstr "" + +#: ./doc/install-guide/object-storage/section_object-storage-network-planning.xml65(para) +msgid "" +"Manages replication-related communications among storage servers within the " +"Object Storage infrastructure." +msgstr "" + +#: ./doc/install-guide/object-storage/section_object-storage-network-planning.xml67(para) +msgid "Recommended size: as for STORAGE_LOCAL_NET." +msgstr "" + +#. When image changes, this message will be marked fuzzy or untranslated for +#. you. +#. It doesn't matter what you translate it to: it's not used at all. +#: ./doc/install-guide/object-storage/section_object-storage-example-install-arch.xml45(None) +msgid "" +"@@image: '../figures/swift_install_arch.png'; " +"md5=c6519fb969c1184afa22e024de9bd2a6" +msgstr "" + +#: ./doc/install-guide/object-storage/section_object-storage-example-install-arch.xml6(title) +msgid "Example Object Storage installation architecture" +msgstr "" + +#: ./doc/install-guide/object-storage/section_object-storage-example-install-arch.xml9(para) +msgid "" +"node. A host machine that runs one or more OpenStack Object Storage " +"services." +msgstr "" + +#: ./doc/install-guide/object-storage/section_object-storage-example-install-arch.xml13(para) +msgid "Proxy node. Runs Proxy services." +msgstr "" + +#: ./doc/install-guide/object-storage/section_object-storage-example-install-arch.xml16(para) +msgid "Storage node. Runs Account, Container, and Object services." +msgstr "" + +#: ./doc/install-guide/object-storage/section_object-storage-example-install-arch.xml20(para) +msgid "" +"Ring. A set of mappings between OpenStack Object Storage data to physical " +"devices." +msgstr "" + +#: ./doc/install-guide/object-storage/section_object-storage-example-install-arch.xml24(para) +msgid "" +"Replica. A copy of an object. By default, three copies are maintained in the" +" cluster." +msgstr "" + +#: ./doc/install-guide/object-storage/section_object-storage-example-install-arch.xml28(para) +msgid "" +"Zone. A logically separate section of the cluster, related to independent " +"failure characteristics." +msgstr "" + +#: ./doc/install-guide/object-storage/section_object-storage-example-install-arch.xml32(para) +msgid "" +"To increase reliability and performance, you can add additional proxy " +"servers." +msgstr "" + +#: ./doc/install-guide/object-storage/section_object-storage-example-install-arch.xml34(para) +msgid "" +"This document describes each storage node as a separate zone in the ring. At" +" a minimum, five zones are recommended. A zone is a group of nodes that is " +"as isolated as possible from other nodes (separate servers, network, power, " +"even geography). The ring guarantees that every replica is stored in a " +"separate zone. This diagram shows one possible configuration for a minimal " +"installation:" +msgstr "" + +#: ./doc/install-guide/object-storage/section_object-storage-install.xml6(title) +msgid "Install Object Storage" +msgstr "" + +#: ./doc/install-guide/object-storage/section_object-storage-install.xml7(para) +msgid "" +"Though you can install OpenStack Object Storage for development or testing " +"purposes on one server, a multiple-server installation enables the high " +"availability and redundancy you want in a production distributed object " +"storage system." +msgstr "" + +#: ./doc/install-guide/object-storage/section_object-storage-install.xml12(para) +msgid "" +"To perform a single-node installation for development purposes from source " +"code, use the Swift All In One instructions (Ubuntu) or DevStack (multiple " +"distros). See http://swift.openstack.org/development_saio.html" +" for manual instructions or http://devstack.org for all-in-one " +"including authentication with the Identity Service (keystone)." +msgstr "" + +#: ./doc/install-guide/object-storage/section_object-storage-install.xml24(para) +msgid "" +"Have a copy of the operating system installation media available if you are " +"installing on a new server." +msgstr "" + +#: ./doc/install-guide/object-storage/section_object-storage-install.xml26(para) +msgid "" +"These steps assume you have set up repositories for packages for your " +"operating system as shown in OpenStack " +"Packages." +msgstr "" + +#: ./doc/install-guide/object-storage/section_object-storage-install.xml30(para) +msgid "" +"This document demonstrates how to install a cluster by using the following " +"types of nodes:" +msgstr "" + +#: ./doc/install-guide/object-storage/section_object-storage-install.xml34(para) +msgid "" +"One proxy node which runs the swift-proxy-server processes. The proxy server" +" proxies requests to the appropriate storage nodes." +msgstr "" + +#: ./doc/install-guide/object-storage/section_object-storage-install.xml39(para) +msgid "" +"Five storage nodes that run the swift-account-server, swift-container-" +"server, and swift-object-server processes which control storage of the " +"account databases, the container databases, as well as the actual stored " +"objects." +msgstr "" + +#: ./doc/install-guide/object-storage/section_object-storage-install.xml48(para) +msgid "" +"Fewer storage nodes can be used initially, but a minimum of five is " +"recommended for a production cluster." +msgstr "" + +#: ./doc/install-guide/object-storage/section_object-storage-install.xml54(title) +msgid "General installation steps" +msgstr "" + +#: ./doc/install-guide/object-storage/section_object-storage-install.xml57(para) +msgid "Install core Swift files and openSSH." +msgstr "" + +#: ./doc/install-guide/object-storage/section_object-storage-install.xml68(para) +msgid "" +"Create a swift user that the Object Storage Service can " +"use to authenticate with the Identity Service. Choose a password and specify" +" an email address for the swift user. Use the " +"service tenant and give the user the " +"admin role." +msgstr "" + +#: ./doc/install-guide/object-storage/section_object-storage-install.xml75(replaceable) +msgid "SWIFT_PASS" +msgstr "" + +#: ./doc/install-guide/object-storage/section_object-storage-install.xml76(replaceable) +msgid "swift@example.com" +msgstr "" + +#: ./doc/install-guide/object-storage/section_object-storage-install.xml80(para) +msgid "Create a service entry for the Object Storage Service:" +msgstr "" + +#: ./doc/install-guide/object-storage/section_object-storage-install.xml95(para) +msgid "" +"Specify an API endpoint for the Object Storage Service by using the returned" +" service ID. When you specify an endpoint, you provide URLs for the public " +"API, internal API, and admin API. In this guide, the " +"controller host name is used." +msgstr "" + +#: ./doc/install-guide/object-storage/section_object-storage-install.xml117(para) +msgid "Create and populate configuration directories on all nodes:" +msgstr "" + +#: ./doc/install-guide/object-storage/section_object-storage-install.xml125(para) +msgid "Create /etc/swift/swift.conf on all nodes:" +msgstr "" + +#: ./doc/install-guide/object-storage/section_object-storage-install.xml132(para) +msgid "" +"The suffix value in /etc/swift/swift.conf should be set" +" to some random string of text to be used as a salt when hashing to " +"determine mappings in the ring. This file should be the same on every node " +"in the cluster!" +msgstr "" + +#: ./doc/install-guide/object-storage/section_object-storage-install.xml139(para) +msgid "" +"Next, set up your storage nodes and proxy node. This example uses the " +"Identity Service for the common authentication piece." +msgstr "" + +#: ./doc/install-guide/object-storage/section_start-storage-node-services.xml7(title) +msgid "Start services on the storage nodes" +msgstr "" + +#: ./doc/install-guide/object-storage/section_start-storage-node-services.xml8(para) +msgid "" +"Now that the ring files are on each storage node, you can start the " +"services. On each storage node, run the following commands:" +msgstr "" + +#: ./doc/install-guide/object-storage/section_start-storage-node-services.xml36(para) +msgid "To start all swift services at once, run the command:" +msgstr "" + +#: ./doc/install-guide/object-storage/section_start-storage-node-services.xml38(para) +msgid "To know more about swift-init command, run:" +msgstr "" + +#: ./doc/install-guide/object-storage/section_start-storage-node-services.xml45(replaceable) +msgid "service" +msgstr "" + +#: ./doc/install-guide/object-storage/section_start-storage-node-services.xml44(para) +msgid "On Fedora, you might need to use ." +msgstr "" + +#: ./doc/install-guide/object-storage/section_object-storage-install-config-storage-nodes.xml6(title) +msgid "Install and configure storage nodes" +msgstr "" + +#: ./doc/install-guide/object-storage/section_object-storage-install-config-storage-nodes.xml8(para) +msgid "" +"Object Storage works on any file system that supports Extended Attributes " +"(XATTRS). XFS shows the best overall performance for the swift use case " +"after considerable testing and benchmarking at Rackspace. It is also the " +"only file system that has been thoroughly tested. See the OpenStack Configuration " +"Reference for additional recommendations." +msgstr "" + +#: ./doc/install-guide/object-storage/section_object-storage-install-config-storage-nodes.xml20(para) +msgid "Install Storage node packages:" +msgstr "" + +#: ./doc/install-guide/object-storage/section_object-storage-install-config-storage-nodes.xml29(para) +msgid "" +"For each device on the node that you want to use for storage, set up the XFS" +" volume (/dev/sdb is used as an example). Use a single " +"partition per drive. For example, in a server with 12 disks you may use one " +"or two disks for the operating system which should not be touched in this " +"step. The other 10 or 11 disks should be partitioned with a single " +"partition, then formatted in XFS." +msgstr "" + +#: ./doc/install-guide/object-storage/section_object-storage-install-config-storage-nodes.xml52(para) +msgid "Create /etc/rsyncd.conf:" +msgstr "" + +#: ./doc/install-guide/object-storage/section_object-storage-install-config-storage-nodes.xml101(para) +msgid "" +"(Optional) If you want to separate rsync and replication traffic to " +"replication network, set STORAGE_REPLICATION_NET_IP " +"instead of STORAGE_LOCAL_NET_IP:" +msgstr "" + +#: ./doc/install-guide/object-storage/section_object-storage-install-config-storage-nodes.xml109(para) +msgid "Edit the following line in /etc/default/rsync:" +msgstr "" + +#: ./doc/install-guide/object-storage/section_object-storage-install-config-storage-nodes.xml114(para) +msgid "Start rsync daemon:" +msgstr "" + +#: ./doc/install-guide/object-storage/section_object-storage-install-config-storage-nodes.xml117(para) +msgid "" +"The rsync daemon requires no authentication, so run it on a local, private " +"network." +msgstr "" + +#: ./doc/install-guide/object-storage/section_object-storage-install-config-storage-nodes.xml122(para) +msgid "Create the swift recon cache directory and set its permissions." +msgstr "" + +#: ./doc/install-guide/object-storage/section_object-storage-sys-requirements.xml8(para) +msgid "" +"Hardware: OpenStack Object Storage is " +"designed to run on commodity hardware." +msgstr "" + +#: ./doc/install-guide/object-storage/section_object-storage-sys-requirements.xml11(para) +msgid "" +"When you install only the Object Storage and Identity Service, you cannot " +"use the dashboard unless you also install Compute and the Image Service." +msgstr "" + +#: ./doc/install-guide/object-storage/section_object-storage-sys-requirements.xml16(caption) +msgid "Hardware recommendations" +msgstr "" + +#: ./doc/install-guide/object-storage/section_object-storage-sys-requirements.xml23(td) +msgid "Server" +msgstr "" + +#: ./doc/install-guide/object-storage/section_object-storage-sys-requirements.xml24(td) +msgid "Recommended Hardware" +msgstr "" + +#: ./doc/install-guide/object-storage/section_object-storage-sys-requirements.xml30(para) +msgid "Object Storage object servers" +msgstr "" + +#: ./doc/install-guide/object-storage/section_object-storage-sys-requirements.xml32(para) +#: ./doc/install-guide/object-storage/section_object-storage-sys-requirements.xml61(para) +#: ./doc/install-guide/object-storage/section_object-storage-sys-requirements.xml71(para) +msgid "Processor: dual quad core" +msgstr "" + +#: ./doc/install-guide/object-storage/section_object-storage-sys-requirements.xml33(para) +#: ./doc/install-guide/object-storage/section_object-storage-sys-requirements.xml62(para) +msgid "Memory: 8 or 12 GB RAM" +msgstr "" + +#: ./doc/install-guide/object-storage/section_object-storage-sys-requirements.xml34(para) +msgid "Disk space: optimized for cost per GB" +msgstr "" + +#: ./doc/install-guide/object-storage/section_object-storage-sys-requirements.xml35(para) +#: ./doc/install-guide/object-storage/section_object-storage-sys-requirements.xml63(para) +#: ./doc/install-guide/object-storage/section_object-storage-sys-requirements.xml72(para) +msgid "Network: one 1 GB Network Interface Card (NIC)" +msgstr "" + +#: ./doc/install-guide/object-storage/section_object-storage-sys-requirements.xml37(para) +msgid "" +"The amount of disk space depends on how much you can fit into the rack " +"efficiently. You want to optimize these for best cost per GB while still " +"getting industry-standard failure rates. At Rackspace, our storage servers " +"are currently running fairly generic 4U servers with 24 2T SATA drives and 8" +" cores of processing power. RAID on the storage drives is not required and " +"not recommended. Swift's disk usage pattern is the worst case possible for " +"RAID, and performance degrades very quickly using RAID 5 or 6." +msgstr "" + +#: ./doc/install-guide/object-storage/section_object-storage-sys-requirements.xml49(para) +msgid "" +"As an example, Rackspace runs Cloud Files storage servers with 24 2T SATA " +"drives and 8 cores of processing power. Most services support either a " +"worker or concurrency value in the settings. This allows the services to " +"make effective use of the cores available." +msgstr "" + +#: ./doc/install-guide/object-storage/section_object-storage-sys-requirements.xml58(para) +msgid "Object Storage container/account servers" +msgstr "" + +#: ./doc/install-guide/object-storage/section_object-storage-sys-requirements.xml65(para) +msgid "Optimized for IOPS due to tracking with SQLite databases." +msgstr "" + +#: ./doc/install-guide/object-storage/section_object-storage-sys-requirements.xml69(para) +msgid "Object Storage proxy server" +msgstr "" + +#: ./doc/install-guide/object-storage/section_object-storage-sys-requirements.xml74(para) +msgid "" +"Higher network throughput offers better performance for supporting many API " +"requests." +msgstr "" + +#: ./doc/install-guide/object-storage/section_object-storage-sys-requirements.xml77(para) +msgid "" +"Optimize your proxy servers for best CPU performance. The Proxy Services are" +" more CPU and network I/O intensive. If you are using 10 GB networking to " +"the proxy, or are terminating SSL traffic at the proxy, greater CPU power is" +" required." +msgstr "" + +#: ./doc/install-guide/object-storage/section_object-storage-sys-requirements.xml86(para) +msgid "" +"Operating system: OpenStack Object " +"Storage currently runs on Ubuntu, RHEL, CentOS, Fedora, openSUSE, or SLES." +msgstr "" + +#: ./doc/install-guide/object-storage/section_object-storage-sys-requirements.xml89(para) +msgid "" +"Networking: 1Gpbs or 10 Gbps is suggested" +" internally. For OpenStack Object Storage, an external network should " +"connect the outside world to the proxy servers, and the storage network is " +"intended to be isolated on a private network or multiple private networks." +msgstr "" + +#: ./doc/install-guide/object-storage/section_object-storage-sys-requirements.xml94(para) +msgid "" +"Database: For OpenStack Object Storage, a" +" SQLite database is part of the OpenStack Object Storage container and " +"account management process." +msgstr "" + +#: ./doc/install-guide/object-storage/section_object-storage-sys-requirements.xml98(para) +msgid "" +"Permissions: You can install OpenStack " +"Object Storage either as root or as a user with sudo permissions if you " +"configure the sudoers file to enable all the permissions." +msgstr "" + +#. Put one translator per line, in the form of NAME , YEAR1, YEAR2 +#: ./doc/install-guide/object-storage/section_object-storage-sys-requirements.xml0(None) +msgid "translator-credits" +msgstr "" diff --git a/doc/install-guide/locale/install-guide.pot b/doc/install-guide/locale/install-guide.pot new file mode 100644 index 0000000000..61926f410e --- /dev/null +++ b/doc/install-guide/locale/install-guide.pot @@ -0,0 +1,5696 @@ +msgid "" +msgstr "" +"Project-Id-Version: PACKAGE VERSION\n" +"POT-Creation-Date: 2014-01-30 06:24+0000\n" +"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n" +"Last-Translator: FULL NAME \n" +"Language-Team: LANGUAGE \n" +"MIME-Version: 1.0\n" +"Content-Type: text/plain; charset=UTF-8\n" +"Content-Transfer-Encoding: 8bit\n" + +#: ./doc/install-guide/section_keystone-users.xml:5(title) +msgid "Define users, tenants, and roles" +msgstr "" + +#: ./doc/install-guide/section_keystone-users.xml:7(para) +msgid "After you install the Identity Service, set up users, tenants, and roles to authenticate against. These are used to allow access to services and endpoints, described in the next section." +msgstr "" + +#: ./doc/install-guide/section_keystone-users.xml:24(replaceable) ./doc/install-guide/section_keystone-users.xml:27(replaceable) +msgid "FCAF3E..." +msgstr "" + +#: ./doc/install-guide/section_keystone-users.xml:14(para) +msgid "Typically, you would indicate a user and password to authenticate with the Identity Service. At this point, however, we have not created any users, so we have to use the authorization token created in the previous section. You can pass this with the option to the command or set the OS_SERVICE_TOKEN environment variable. We'll set OS_SERVICE_TOKEN, as well as OS_SERVICE_ENDPOINT to specify where the Identity Service is running. Replace with your authorization token." +msgstr "" + +#: ./doc/install-guide/section_keystone-users.xml:30(para) +msgid "First, create a tenant for an administrative user and a tenant for other OpenStack services to use." +msgstr "" + +#: ./doc/install-guide/section_keystone-users.xml:36(para) +msgid "Next, create an administrative user called admin. Choose a password for the admin user and specify an email address for the account." +msgstr "" + +#: ./doc/install-guide/section_keystone-users.xml:40(replaceable) ./doc/install-guide/section_keystone-verify.xml:25(replaceable) ./doc/install-guide/section_keystone-verify.xml:35(replaceable) ./doc/install-guide/section_keystone-verify.xml:49(replaceable) ./doc/install-guide/section_neutron-per-tenant-routers-with-private-networks.xml:408(replaceable) ./doc/install-guide/section_neutron-provider-router-with-private_networks.xml:376(replaceable) ./doc/install-guide/section_neutron-single-flat.xml:483(replaceable) +msgid "ADMIN_PASS" +msgstr "" + +#: ./doc/install-guide/section_keystone-users.xml:41(replaceable) +msgid "admin@example.com" +msgstr "" + +#: ./doc/install-guide/section_keystone-users.xml:43(para) +msgid "Create a role for administrative tasks called admin. Any roles you create should map to roles specified in the policy.json files of the various OpenStack services. The default policy files use the admin role to allow access to most services." +msgstr "" + +#: ./doc/install-guide/section_keystone-users.xml:51(para) +msgid "Finally, you have to add roles to users. Users always log in with a tenant, and roles are assigned to users within tenants. Add the admin role to the admin user when logging in with the admin tenant." +msgstr "" + +#. When image changes, this message will be marked fuzzy or untranslated for you. +#. It doesn't matter what you translate it to: it's not used at all. +#: ./doc/install-guide/section_debconf-api-endpoints.xml:29(None) +msgid "@@image: 'figures/debconf-screenshots/api-endpoint_1_register_endpoint.png'; md5=d534be231be4f725820a1050fbf44231" +msgstr "" + +#. When image changes, this message will be marked fuzzy or untranslated for you. +#. It doesn't matter what you translate it to: it's not used at all. +#: ./doc/install-guide/section_debconf-api-endpoints.xml:40(None) +msgid "@@image: 'figures/debconf-screenshots/api-endpoint_2_keystone_server_ip.png'; md5=d2c5a5b82dd433fcf9cde6f5ac34c30e" +msgstr "" + +#. When image changes, this message will be marked fuzzy or untranslated for you. +#. It doesn't matter what you translate it to: it's not used at all. +#: ./doc/install-guide/section_debconf-api-endpoints.xml:54(None) +msgid "@@image: 'figures/debconf-screenshots/api-endpoint_3_keystone_authtoken.png'; md5=1f3b05ebe671f64d672ac70d246e4f39" +msgstr "" + +#. When image changes, this message will be marked fuzzy or untranslated for you. +#. It doesn't matter what you translate it to: it's not used at all. +#: ./doc/install-guide/section_debconf-api-endpoints.xml:69(None) +msgid "@@image: 'figures/debconf-screenshots/api-endpoint_4_service_endpoint_ip_address.png'; md5=6853f0ae2ef8d5fddb22c466d465de15" +msgstr "" + +#. When image changes, this message will be marked fuzzy or untranslated for you. +#. It doesn't matter what you translate it to: it's not used at all. +#: ./doc/install-guide/section_debconf-api-endpoints.xml:81(None) +msgid "@@image: 'figures/debconf-screenshots/api-endpoint_5_region_name.png'; md5=a6bce0acf5a1cb85f161290f0cf30733" +msgstr "" + +#: ./doc/install-guide/section_debconf-api-endpoints.xml:6(title) +msgid "Register API endpoints" +msgstr "" + +#: ./doc/install-guide/section_debconf-api-endpoints.xml:7(para) +msgid "All Debian packages for API services, except the heat-api package, register the service in the Identity Service catalog. This feature is helpful because API endpoints are difficult to remember." +msgstr "" + +#: ./doc/install-guide/section_debconf-api-endpoints.xml:12(para) +msgid "The heat-common package and not the heat-api package configures the Orchestration service." +msgstr "" + +#: ./doc/install-guide/section_debconf-api-endpoints.xml:16(para) +msgid "When you install a package for an API service, you are prompted to register that service. However, after you install or upgrade the package for an API service, Debian immediately removes your response to this prompt from the debconf database. Consequently, you are prompted to re-register the service with the Identity Service. If you already registered the API service, respond no when you upgrade." +msgstr "" + +#: ./doc/install-guide/section_debconf-api-endpoints.xml:33(para) +msgid "This screen registers packages in the Identity Service catalog:" +msgstr "" + +#: ./doc/install-guide/section_debconf-api-endpoints.xml:44(para) +msgid "You are prompted for the Identity Service admin_token value. The Identity Service uses this value to register the API service. When you set up the keystone package, this value is configured automatically." +msgstr "" + +#: ./doc/install-guide/section_debconf-api-endpoints.xml:58(para) +msgid "This screen configures the IP addresses for the service. The configuration script automatically detects the IP address used by the interface that is connected to the default route (/sbin/route and /sbin/ip)." +msgstr "" + +#: ./doc/install-guide/section_debconf-api-endpoints.xml:62(para) +msgid "Unless you have a unique set up for your network, press ENTER." +msgstr "" + +#: ./doc/install-guide/section_debconf-api-endpoints.xml:73(para) +msgid "This screen configures the region name for the service. For example, us-east-coast or europe-paris." +msgstr "" + +#: ./doc/install-guide/ch_glance.xml:6(title) +msgid "Configure the Image Service" +msgstr "" + +#: ./doc/install-guide/ch_glance.xml:7(para) +msgid "The OpenStack Image Service enables users to discover, register, and retrieve virtual machine images. Also known as the glance project, the Image Service offers a REST API that enables you to query virtual machine image metadata and retrieve an actual image. Virtual machine images made available through the Image Service can be stored in a variety of locations from simple file systems to object-storage systems like OpenStack Object Storage." +msgstr "" + +#: ./doc/install-guide/ch_glance.xml:16(para) +msgid "For simplicity this guide configures the Image Service to use the file backend. This means that images uploaded to the Image Service will be stored in a directory on the same system that hosts the service. By default this directory is /var/lib/glance/images/." +msgstr "" + +#: ./doc/install-guide/ch_glance.xml:23(para) +msgid "Ensure that the system has sufficient space available under this directory to store virtual machine images and snapshots before proceeding. At an absolute minimum several gigabytes of space should be available for use by the Image Service in a proof of concept deployment." +msgstr "" + +#: ./doc/install-guide/ch_cinder.xml:6(title) +msgid "Add the Block Storage Service" +msgstr "" + +#: ./doc/install-guide/ch_cinder.xml:7(para) +msgid "The OpenStack Block Storage Service works through the interaction of a series of daemon processes named cinder-* that reside persistently on the host machine or machines. You can run the binaries from a single node or across multiple nodes. You can also run them on the same node as other OpenStack services. The following sections introduce Block Storage Service components and concepts and show you how to configure and install the Block Storage Service." +msgstr "" + +#: ./doc/install-guide/section_nova-kvm.xml:5(title) +msgid "Enable KVM on the Compute node" +msgstr "" + +#: ./doc/install-guide/section_nova-kvm.xml:7(para) +msgid "OpenStack Compute requires hardware virtualization support and certain kernel modules. Use the following procedure to determine whether your system has this support and the correct kernel modules and to enable KVM. In many cases, your distribution completes this installation and you do not need to perform any additional action." +msgstr "" + +#: ./doc/install-guide/section_glance-verify.xml:5(title) +msgid "Verify the Image Service installation" +msgstr "" + +#: ./doc/install-guide/section_glance-verify.xml:6(para) +msgid "To test the Image Service installation, download at least one virtual machine image that is known to work with OpenStack. For example, CirrOS is a small test image that is often used for testing OpenStack deployments (CirrOS downloads). This walk through uses the 64-bit CirrOS QCOW2 image." +msgstr "" + +#: ./doc/install-guide/section_glance-verify.xml:13(para) +msgid "For more information about how to download and build images, see OpenStack Virtual Machine Image Guide. For information about how to manage images, see the OpenStack User Guide." +msgstr "" + +#: ./doc/install-guide/section_glance-verify.xml:24(para) +msgid "Download the image into a dedicated directory using or :" +msgstr "" + +#: ./doc/install-guide/section_glance-verify.xml:32(para) +msgid "Upload the image to the Image Service:" +msgstr "" + +#: ./doc/install-guide/section_glance-verify.xml:33(replaceable) ./doc/install-guide/section_glance-verify.xml:38(replaceable) +msgid "imageLabel" +msgstr "" + +#: ./doc/install-guide/section_glance-verify.xml:33(replaceable) ./doc/install-guide/section_glance-verify.xml:45(replaceable) +msgid "fileFormat" +msgstr "" + +#: ./doc/install-guide/section_glance-verify.xml:34(replaceable) ./doc/install-guide/section_glance-verify.xml:65(replaceable) +msgid "containerFormat" +msgstr "" + +#: ./doc/install-guide/section_glance-verify.xml:34(replaceable) ./doc/install-guide/section_glance-verify.xml:86(replaceable) +msgid "accessValue" +msgstr "" + +#: ./doc/install-guide/section_glance-verify.xml:34(replaceable) ./doc/install-guide/section_glance-verify.xml:101(replaceable) +msgid "imageFile" +msgstr "" + +#: ./doc/install-guide/section_glance-verify.xml:35(para) +msgid "Where:" +msgstr "" + +#: ./doc/install-guide/section_glance-verify.xml:40(para) +msgid "Arbitrary label. The name by which users refer to the image." +msgstr "" + +#: ./doc/install-guide/section_glance-verify.xml:47(para) +msgid "Specifies the format of the image file. Valid formats include qcow2, raw, vhd, vmdk, vdi, iso, aki, ari, and ami." +msgstr "" + +#: ./doc/install-guide/section_glance-verify.xml:58(para) +msgid "You can verify the format using the command: " +msgstr "" + +#: ./doc/install-guide/section_glance-verify.xml:67(para) +msgid "Specifies the container format. Valid formats include: bare, ovf, aki, ari and ami." +msgstr "" + +#: ./doc/install-guide/section_glance-verify.xml:73(para) +msgid "Specify bare to indicate that the image file is not in a file format that contains metadata about the virtual machine. Although this field is currently required, it is not actually used by any of the OpenStack services and has no effect on system behavior. Because the value is not used anywhere, it safe to always specify bare as the container format." +msgstr "" + +#: ./doc/install-guide/section_glance-verify.xml:90(para) +msgid "true - All users can view and use the image." +msgstr "" + +#: ./doc/install-guide/section_glance-verify.xml:94(para) +msgid "false - Only administrators can view and use the image." +msgstr "" + +#: ./doc/install-guide/section_glance-verify.xml:88(para) +msgid "Specifies image access: " +msgstr "" + +#: ./doc/install-guide/section_glance-verify.xml:103(para) +msgid "Specifies the name of your downloaded image file." +msgstr "" + +#: ./doc/install-guide/section_glance-verify.xml:108(para) +msgid "For example:" +msgstr "" + +#: ./doc/install-guide/section_glance-verify.xml:132(para) +msgid "Because the returned image ID is generated dynamically, your deployment generates a different ID than the one shown in this example." +msgstr "" + +#: ./doc/install-guide/section_glance-verify.xml:138(para) +msgid "Confirm that the image was uploaded and display its attributes:" +msgstr "" + +#: ./doc/install-guide/ch_clients.xml:6(title) +msgid "Install and configure the OpenStack clients" +msgstr "" + +#. When image changes, this message will be marked fuzzy or untranslated for you. +#. It doesn't matter what you translate it to: it's not used at all. +#: ./doc/install-guide/section_debconf-keystone_authtoken.xml:30(None) +msgid "@@image: 'figures/debconf-screenshots/service_keystone_authtoken_server_hostname.png'; md5=aafd53894e1d960531d4901123952117" +msgstr "" + +#. When image changes, this message will be marked fuzzy or untranslated for you. +#. It doesn't matter what you translate it to: it's not used at all. +#: ./doc/install-guide/section_debconf-keystone_authtoken.xml:37(None) +msgid "@@image: 'figures/debconf-screenshots/service_keystone_authtoken_admin_tenant_name.png'; md5=a935563e4fba9b00040e35cdcfffc732" +msgstr "" + +#. When image changes, this message will be marked fuzzy or untranslated for you. +#. It doesn't matter what you translate it to: it's not used at all. +#: ./doc/install-guide/section_debconf-keystone_authtoken.xml:44(None) +msgid "@@image: 'figures/debconf-screenshots/service_keystone_authtoken_tenant_admin_user.png'; md5=fe3dc93c591b3e9783d4d05556efcf25" +msgstr "" + +#. When image changes, this message will be marked fuzzy or untranslated for you. +#. It doesn't matter what you translate it to: it's not used at all. +#: ./doc/install-guide/section_debconf-keystone_authtoken.xml:51(None) +msgid "@@image: 'figures/debconf-screenshots/service_keystone_authtoken_admin_password.png'; md5=0c30c80315d5e636dbe93a938fc2822b" +msgstr "" + +#: ./doc/install-guide/section_debconf-keystone_authtoken.xml:6(title) +msgid "Services and the [keystone_authtoken]" +msgstr "" + +#: ./doc/install-guide/section_debconf-keystone_authtoken.xml:7(para) +msgid "Because most OpenStack services must access the Identity Service, you must configure the IP address of the keystone server to be able to access it. You must also configure the admin_tenant_name, admin_user, and admin_password options for each service to work." +msgstr "" + +#: ./doc/install-guide/section_debconf-keystone_authtoken.xml:13(para) +msgid "Generally, this section looks like this:" +msgstr "" + +#: ./doc/install-guide/section_debconf-keystone_authtoken.xml:21(para) +msgid "The debconf system helps users configure the auth_host, admin_tenant_name, admin_user and admin_password options." +msgstr "" + +#: ./doc/install-guide/section_debconf-keystone_authtoken.xml:25(para) +msgid "The following screens show an example Image Service configuration:" +msgstr "" + +#: ./doc/install-guide/section_debconf-keystone_authtoken.xml:55(para) +msgid "This information is stored in the configuration file for each service. For example:" +msgstr "" + +#: ./doc/install-guide/section_debconf-keystone_authtoken.xml:63(para) +msgid "The Debian OpenStack packages offer automation for this, so OpenStack users do not have to manually edit the configuration files." +msgstr "" + +#: ./doc/install-guide/ch_swift.xml:6(title) +msgid "Add Object Storage" +msgstr "" + +#: ./doc/install-guide/ch_swift.xml:8(para) +msgid "The OpenStack Object Storage services work together to provide object storage and retrieval through a REST API. For this example architecture, you must have already installed the Identity Service, also known as Keystone." +msgstr "" + +#: ./doc/install-guide/section_neutron-concepts.xml:8(title) +msgid "Neutron concepts" +msgstr "" + +#: ./doc/install-guide/section_neutron-concepts.xml:9(para) +msgid "Like Nova Networking, Neutron manages software-defined networking for your OpenStack installation. However, unlike Nova Networking, you can configure Neutron for advanced virtual network topologies, such as per-tenant private networks and more." +msgstr "" + +#: ./doc/install-guide/section_neutron-concepts.xml:13(para) +msgid "Neutron has the following object abstractions: networks, subnets, and routers. Each has functionality that mimics its physical counterpart: networks contain subnets, and routers route traffic between different subnet and networks." +msgstr "" + +#: ./doc/install-guide/section_neutron-concepts.xml:17(para) +msgid "Any given Neutron set up has at least one external network. This network, unlike the other networks, is not merely a virtually defined network. Instead, it represents the view into a slice of the external network that is accessible outside the OpenStack installation. IP addresses on the Neutron external network are accessible by anybody physically on the outside network. Because this network merely represents a slice of the outside network, DHCP is disabled on this network." +msgstr "" + +#: ./doc/install-guide/section_neutron-concepts.xml:25(para) +msgid "In addition to external networks, any Neutron set up has one or more internal networks. These software-defined networks connect directly to the VMs. Only the VMs on any given internal network, or those on subnets connected through interfaces to a similar router, can access VMs connected to that network directly." +msgstr "" + +#: ./doc/install-guide/section_neutron-concepts.xml:30(para) +msgid "For the outside network to access VMs, and vice versa, routers between the networks are needed. Each router has one gateway that is connected to a network and many interfaces that are connected to subnets. Like a physical router, subnets can access machines on other subnets that are connected to the same router, and machines can access the outside network through the gateway for the router." +msgstr "" + +#: ./doc/install-guide/section_neutron-concepts.xml:37(para) +msgid "Additionally, you can allocate IP addresses on an external networks to ports on the internal network. Whenever something is connected to a subnet, that connection is called a port. You can associate external network IP addresses with ports to VMs. This way, entities on the outside network can access VMs." +msgstr "" + +#: ./doc/install-guide/section_neutron-concepts.xml:42(para) +msgid "Neutron also supports security groups. Security groups enable administrators to define firewall rules in groups. A VM can belong to one or more security groups, and Neutron applies the rules in those security groups to block or unblock ports, port ranges, or traffic types for that VM." +msgstr "" + +#: ./doc/install-guide/section_neutron-concepts.xml:48(para) +msgid "Each plug-in that Neutron uses has its own concepts. While not vital to operating Neutron, understanding these concepts can help you set up Neutron. All Neutron installations use a core plug-in and a security group plug-in (or just the No-Op security group plug-in). Additionally, Firewall-as-a-service (FWaaS) and Load-balancing-as-a-service (LBaaS) plug-ins are available." +msgstr "" + +#: ./doc/install-guide/section_neutron-concepts.xml:55(title) +msgid "Open vSwitch concepts" +msgstr "" + +#: ./doc/install-guide/section_neutron-concepts.xml:56(para) +msgid "The Open vSwitch plug-in is one of the most popular core plug-ins. Open vSwitch configurations consists of bridges and ports. Ports represent connections to other things, such as physical interfaces and patch cables. Packets from any given port on a bridge are shared with all other ports on that bridge. Bridges can be connected through Open vSwitch virtual patch cables or through Linux virtual Ethernet cables (veth). Additionally, bridges appear as network interfaces to Linux, so you can assign IP addresses to them." +msgstr "" + +#: ./doc/install-guide/section_neutron-concepts.xml:66(para) +msgid "In Neutron, the integration bridge, called br-int, connects directly to the VMs and associated services. The external bridge, called br-ex, connects to the external network. Finally, the VLAN configuration of the Open vSwitch plug-in uses bridges associated with each physical network." +msgstr "" + +#: ./doc/install-guide/section_neutron-concepts.xml:72(para) +msgid "In addition to defining bridges, Open vSwitch has OpenFlow, which enables you to define networking flow rules. Certain configurations use these rules to transfer packets between VLANs." +msgstr "" + +#: ./doc/install-guide/section_neutron-concepts.xml:76(para) +msgid "Finally, some configurations of Open vSwitch use network namespaces that enable Linux to group adapters into unique namespaces that are not visible to other namespaces, which allows the same network node to manage multiple Neutron routers." +msgstr "" + +#: ./doc/install-guide/section_neutron-concepts.xml:81(para) +msgid "With Open vSwitch, you can use two different technologies to create the virtual networks: GRE or VLANs." +msgstr "" + +#: ./doc/install-guide/section_neutron-concepts.xml:83(para) +msgid "Generic Routing Encapsulation (GRE) is the technology used in many VPNs. It wraps IP packets to create entirely new packets with different routing information. When the new packet reaches its destination, it is unwrapped, and the underlying packet is routed. To use GRE with Open vSwitch, Neutron creates GRE tunnels. These tunnels are ports on a bridge and enable bridges on different systems to act as though they were one bridge, which allows the compute and network nodes to act as one for the purposes of routing." +msgstr "" + +#: ./doc/install-guide/section_neutron-concepts.xml:92(para) +msgid "Virtual LANs (VLANs), on the other hand, use a special modification to the Ethernet header. They add a 4-byte VLAN tag that ranges from 1 to 4094 (the 0 tag is special, and the 4095 tag, made of all ones, is equivalent to an untagged packet). Special NICs, switches, and routers know how to interpret the VLAN tags, as does Open vSwitch. Packets tagged for one VLAN are only shared with other devices configured to be on that VLAN, even through all devices are on the same physical network." +msgstr "" + +#: ./doc/install-guide/section_neutron-concepts.xml:101(para) +msgid "The most common security group driver used with Open vSwitch is the Hybrid IPTables/Open vSwitch plug-in. It uses a combination for IPTables and OpenFlow rules. Use the IPTables tool to create firewalls and set up NATs on Linux. This tool uses a complex rule system and chains of rules to accommodate the complex rules required by Neutron security groups." +msgstr "" + +#: ./doc/install-guide/section_ceilometer-install.xml:6(title) +msgid "Install the Telemetry service" +msgstr "" + +#: ./doc/install-guide/section_ceilometer-install.xml:8(para) +msgid "OpenStack Telemetry is an API service that provides a collector and a range of disparate agents. Before you can install these agents on nodes such as the compute node, you must use this procedure to install the core components on the controller node." +msgstr "" + +#: ./doc/install-guide/section_ceilometer-install.xml:14(para) +msgid "Install the Telemetry service on the controller node:" +msgstr "" + +#: ./doc/install-guide/section_ceilometer-install.xml:21(para) +msgid "Respond to the prompts for [keystone_authtoken] settings, RabbitMQ credentials and API endpoint registration." +msgstr "" + +#: ./doc/install-guide/section_ceilometer-install.xml:29(para) +msgid "The Telemetry service uses a database to store information. Specify the location of the database in the configuration file. The examples use a MongoDB database on the controller node:" +msgstr "" + +#: ./doc/install-guide/section_ceilometer-install.xml:37(para) +msgid "By default MongoDB is configured to create several 1 GB files in the /var/lib/mongodb/journal/ directory to support database journaling." +msgstr "" + +#: ./doc/install-guide/section_ceilometer-install.xml:42(para) +msgid "If you need to minimize the space allocated to support database journaling then set the configuration key to true in the /etc/mongodb.conf configuration file. This will reduce the size of each journaling file to 512 MB." +msgstr "" + +#: ./doc/install-guide/section_ceilometer-install.xml:49(para) +msgid "As the files are created the first time the MongoDB service starts you must stop the service and remove the files for this change to take effect:" +msgstr "" + +#: ./doc/install-guide/section_ceilometer-install.xml:59(para) +msgid "For more information on the configuration key refer to the MongoDB documentation at ." +msgstr "" + +#: ./doc/install-guide/section_ceilometer-install.xml:64(para) +msgid "For instructions detailing the steps to disable database journaling entirely refer to ." +msgstr "" + +#: ./doc/install-guide/section_ceilometer-install.xml:72(para) +msgid "Configure MongoDB to make it listen on the controller public IP address. Edit the /etc/mongodb.conf file and modify the bind_ip key:" +msgstr "" + +#: ./doc/install-guide/section_ceilometer-install.xml:78(para) +msgid "Restart the MongoDB service to apply the configuration change:" +msgstr "" + +#: ./doc/install-guide/section_ceilometer-install.xml:82(para) +msgid "Start the MongoDB server and configure it to start when the system boots:" +msgstr "" + +#: ./doc/install-guide/section_ceilometer-install.xml:92(para) +msgid "Create the database and a ceilometer database user:" +msgstr "" + +#: ./doc/install-guide/section_ceilometer-install.xml:94(replaceable) ./doc/install-guide/section_ceilometer-install.xml:104(replaceable) ./doc/install-guide/section_ceilometer-install.xml:111(replaceable) ./doc/install-guide/section_ceilometer-install.xml:138(replaceable) ./doc/install-guide/section_ceilometer-install.xml:141(replaceable) ./doc/install-guide/section_ceilometer-install.xml:171(replaceable) ./doc/install-guide/section_ceilometer-install.xml:213(replaceable) ./doc/install-guide/section_ceilometer-install.xml:214(replaceable) ./doc/install-guide/section_ceilometer-install.xml:215(replaceable) ./doc/install-guide/section_nova-controller.xml:55(replaceable) ./doc/install-guide/section_nova-controller.xml:69(replaceable) ./doc/install-guide/section_nova-controller.xml:154(replaceable) ./doc/install-guide/section_nova-controller.xml:194(replaceable) ./doc/install-guide/section_nova-controller.xml:197(replaceable) ./doc/install-guide/section_nova-controller.xml:217(replaceable) ./doc/install-guide/section_nova-controller.xml:218(replaceable) ./doc/install-guide/section_nova-controller.xml:219(replaceable) ./doc/install-guide/section_keystone-services.xml:47(replaceable) ./doc/install-guide/section_keystone-services.xml:48(replaceable) ./doc/install-guide/section_keystone-services.xml:49(replaceable) ./doc/install-guide/section_neutron-per-tenant-routers-with-private-networks.xml:181(replaceable) ./doc/install-guide/section_neutron-per-tenant-routers-with-private-networks.xml:186(replaceable) ./doc/install-guide/section_neutron-per-tenant-routers-with-private-networks.xml:194(replaceable) ./doc/install-guide/section_neutron-per-tenant-routers-with-private-networks.xml:199(replaceable) ./doc/install-guide/section_neutron-per-tenant-routers-with-private-networks.xml:271(replaceable) ./doc/install-guide/section_neutron-per-tenant-routers-with-private-networks.xml:276(replaceable) ./doc/install-guide/section_neutron-per-tenant-routers-with-private-networks.xml:326(replaceable) ./doc/install-guide/section_neutron-per-tenant-routers-with-private-networks.xml:410(replaceable) ./doc/install-guide/section_neutron-provider-router-with-private_networks.xml:116(replaceable) ./doc/install-guide/section_neutron-provider-router-with-private_networks.xml:177(replaceable) ./doc/install-guide/section_neutron-provider-router-with-private_networks.xml:181(replaceable) ./doc/install-guide/section_neutron-provider-router-with-private_networks.xml:185(replaceable) ./doc/install-guide/section_neutron-provider-router-with-private_networks.xml:191(replaceable) ./doc/install-guide/section_neutron-provider-router-with-private_networks.xml:222(replaceable) ./doc/install-guide/section_neutron-provider-router-with-private_networks.xml:226(replaceable) ./doc/install-guide/section_neutron-provider-router-with-private_networks.xml:234(replaceable) ./doc/install-guide/section_neutron-provider-router-with-private_networks.xml:321(replaceable) ./doc/install-guide/section_neutron-provider-router-with-private_networks.xml:325(replaceable) ./doc/install-guide/section_neutron-provider-router-with-private_networks.xml:329(replaceable) ./doc/install-guide/section_neutron-provider-router-with-private_networks.xml:335(replaceable) ./doc/install-guide/section_neutron-provider-router-with-private_networks.xml:377(replaceable) ./doc/install-guide/section_ceilometer-glance.xml:17(replaceable) ./doc/install-guide/section_ceilometer-glance.xml:23(replaceable) ./doc/install-guide/section_neutron-single-flat.xml:193(replaceable) ./doc/install-guide/section_neutron-single-flat.xml:212(replaceable) ./doc/install-guide/section_neutron-single-flat.xml:229(replaceable) ./doc/install-guide/section_neutron-single-flat.xml:234(replaceable) ./doc/install-guide/section_neutron-single-flat.xml:284(replaceable) ./doc/install-guide/section_neutron-single-flat.xml:287(replaceable) ./doc/install-guide/section_neutron-single-flat.xml:291(replaceable) ./doc/install-guide/section_neutron-single-flat.xml:301(replaceable) ./doc/install-guide/section_neutron-single-flat.xml:332(replaceable) ./doc/install-guide/section_neutron-single-flat.xml:337(replaceable) ./doc/install-guide/section_neutron-single-flat.xml:346(replaceable) ./doc/install-guide/section_neutron-single-flat.xml:365(replaceable) ./doc/install-guide/section_neutron-single-flat.xml:424(replaceable) ./doc/install-guide/section_neutron-single-flat.xml:449(replaceable) ./doc/install-guide/section_neutron-single-flat.xml:485(replaceable) ./doc/install-guide/section_cinder-node.xml:110(replaceable) ./doc/install-guide/section_cinder-node.xml:127(replaceable) ./doc/install-guide/section_cinder-node.xml:164(replaceable) ./doc/install-guide/section_cinder-node.xml:167(replaceable) ./doc/install-guide/section_cinder-controller.xml:47(replaceable) ./doc/install-guide/section_cinder-controller.xml:50(replaceable) ./doc/install-guide/section_cinder-controller.xml:89(replaceable) ./doc/install-guide/section_cinder-controller.xml:107(replaceable) ./doc/install-guide/section_cinder-controller.xml:142(replaceable) ./doc/install-guide/section_cinder-controller.xml:143(replaceable) ./doc/install-guide/section_cinder-controller.xml:144(replaceable) ./doc/install-guide/section_cinder-controller.xml:153(replaceable) ./doc/install-guide/section_cinder-controller.xml:154(replaceable) ./doc/install-guide/section_cinder-controller.xml:155(replaceable) ./doc/install-guide/section_neutron-install.xml:158(replaceable) ./doc/install-guide/section_neutron-install.xml:159(replaceable) ./doc/install-guide/section_neutron-install.xml:160(replaceable) ./doc/install-guide/section_neutron-install.xml:283(replaceable) ./doc/install-guide/section_neutron-install.xml:323(replaceable) ./doc/install-guide/section_neutron-install.xml:341(replaceable) ./doc/install-guide/section_neutron-install.xml:349(replaceable) ./doc/install-guide/section_neutron-install.xml:351(replaceable) ./doc/install-guide/section_neutron-install.xml:365(replaceable) ./doc/install-guide/section_neutron-install.xml:366(replaceable) ./doc/install-guide/section_neutron-install.xml:851(replaceable) ./doc/install-guide/section_neutron-install.xml:853(replaceable) ./doc/install-guide/section_neutron-install.xml:878(replaceable) ./doc/install-guide/section_neutron-install.xml:890(replaceable) ./doc/install-guide/section_neutron-install.xml:919(replaceable) ./doc/install-guide/section_neutron-install.xml:927(replaceable) ./doc/install-guide/section_neutron-install.xml:938(replaceable) ./doc/install-guide/section_neutron-install.xml:953(replaceable) ./doc/install-guide/section_neutron-install.xml:963(replaceable) ./doc/install-guide/section_neutron-install.xml:974(replaceable) ./doc/install-guide/section_neutron-install.xml:979(replaceable) ./doc/install-guide/section_neutron-install.xml:1080(replaceable) ./doc/install-guide/section_neutron-install.xml:1230(replaceable) ./doc/install-guide/section_neutron-install.xml:1245(replaceable) ./doc/install-guide/section_neutron-install.xml:1247(replaceable) ./doc/install-guide/section_neutron-install.xml:1274(replaceable) ./doc/install-guide/section_neutron-install.xml:1280(replaceable) ./doc/install-guide/section_neutron-install.xml:1281(replaceable) ./doc/install-guide/section_neutron-install.xml:1305(replaceable) ./doc/install-guide/section_neutron-install.xml:1329(replaceable) ./doc/install-guide/section_neutron-install.xml:1348(replaceable) ./doc/install-guide/section_neutron-install.xml:1372(replaceable) ./doc/install-guide/section_neutron-install.xml:1382(replaceable) ./doc/install-guide/section_neutron-install.xml:1393(replaceable) ./doc/install-guide/section_neutron-install.xml:1398(replaceable) ./doc/install-guide/section_heat-install.xml:116(replaceable) ./doc/install-guide/section_heat-install.xml:121(replaceable) ./doc/install-guide/section_heat-install.xml:122(replaceable) ./doc/install-guide/section_heat-install.xml:133(replaceable) ./doc/install-guide/section_heat-install.xml:134(replaceable) ./doc/install-guide/section_heat-install.xml:135(replaceable) ./doc/install-guide/section_heat-install.xml:140(replaceable) ./doc/install-guide/section_heat-install.xml:141(replaceable) ./doc/install-guide/section_heat-install.xml:142(replaceable) ./doc/install-guide/section_ceilometer-nova.xml:78(replaceable) ./doc/install-guide/section_ceilometer-nova.xml:84(replaceable) ./doc/install-guide/section_ceilometer-nova.xml:90(replaceable) ./doc/install-guide/section_ceilometer-nova.xml:106(replaceable) ./doc/install-guide/section_ceilometer-nova.xml:121(replaceable) ./doc/install-guide/section_nova-compute.xml:112(replaceable) ./doc/install-guide/section_nova-compute.xml:135(replaceable) ./doc/install-guide/section_nova-compute.xml:158(replaceable) ./doc/install-guide/section_nova-compute.xml:170(replaceable) ./doc/install-guide/section_nova-compute.xml:178(replaceable) ./doc/install-guide/section_nova-compute.xml:181(replaceable) ./doc/install-guide/section_nova-compute.xml:221(replaceable) ./doc/install-guide/section_glance-install.xml:57(replaceable) ./doc/install-guide/section_glance-install.xml:59(replaceable) ./doc/install-guide/section_glance-install.xml:70(replaceable) ./doc/install-guide/section_glance-install.xml:118(replaceable) ./doc/install-guide/section_glance-install.xml:120(replaceable) ./doc/install-guide/section_glance-install.xml:130(replaceable) ./doc/install-guide/section_glance-install.xml:132(replaceable) ./doc/install-guide/section_glance-install.xml:152(replaceable) ./doc/install-guide/section_glance-install.xml:153(replaceable) ./doc/install-guide/section_glance-install.xml:198(replaceable) ./doc/install-guide/section_glance-install.xml:199(replaceable) ./doc/install-guide/section_glance-install.xml:200(replaceable) ./doc/install-guide/object-storage/section_object-storage-install-config-proxy-node.xml:99(replaceable) ./doc/install-guide/object-storage/section_object-storage-install.xml:102(replaceable) ./doc/install-guide/object-storage/section_object-storage-install.xml:103(replaceable) ./doc/install-guide/object-storage/section_object-storage-install.xml:104(replaceable) +msgid "controller" +msgstr "" + +#: ./doc/install-guide/section_ceilometer-install.xml:97(replaceable) ./doc/install-guide/section_ceilometer-install.xml:104(replaceable) ./doc/install-guide/section_ceilometer-install.xml:111(replaceable) +msgid "CEILOMETER_DBPASS" +msgstr "" + +#: ./doc/install-guide/section_ceilometer-install.xml:102(para) +msgid "Configure the Telemetry service to use the database:" +msgstr "" + +#: ./doc/install-guide/section_ceilometer-install.xml:105(para) +msgid "Edit the /etc/ceilometer/ceilometer.conf file and change the [database] section:" +msgstr "" + +#: ./doc/install-guide/section_ceilometer-install.xml:115(para) +msgid "You must define an secret key that is used as a shared secret among Telemetry service nodes. Use to generate a random token and store it in the configuration file:" +msgstr "" + +#: ./doc/install-guide/section_ceilometer-install.xml:122(para) +msgid "For SUSE Linux Enterprise, run the following command:" +msgstr "" + +#: ./doc/install-guide/section_ceilometer-install.xml:126(para) +msgid "Edit the /etc/ceilometer/ceilometer.conf file and change the [publisher_rpc] section. Replace CEILOMETER_TOKEN with the results of the openssl command:" +msgstr "" + +#: ./doc/install-guide/section_ceilometer-install.xml:133(replaceable) ./doc/install-guide/section_ceilometer-nova.xml:69(replaceable) +msgid "CEILOMETER_TOKEN" +msgstr "" + +#: ./doc/install-guide/section_ceilometer-install.xml:137(para) ./doc/install-guide/section_ceilometer-nova.xml:73(para) +msgid "Configure the RabbitMQ access:" +msgstr "" + +#: ./doc/install-guide/section_ceilometer-install.xml:139(replaceable) ./doc/install-guide/section_ceilometer-install.xml:142(replaceable) ./doc/install-guide/section_nova-controller.xml:78(replaceable) ./doc/install-guide/section_nova-controller.xml:86(replaceable) ./doc/install-guide/section_neutron-per-tenant-routers-with-private-networks.xml:182(replaceable) ./doc/install-guide/section_neutron-per-tenant-routers-with-private-networks.xml:195(replaceable) ./doc/install-guide/section_neutron-per-tenant-routers-with-private-networks.xml:272(replaceable) ./doc/install-guide/section_neutron-per-tenant-routers-with-private-networks.xml:327(replaceable) ./doc/install-guide/section_neutron-provider-router-with-private_networks.xml:113(replaceable) ./doc/install-guide/section_neutron-provider-router-with-private_networks.xml:178(replaceable) ./doc/install-guide/section_neutron-provider-router-with-private_networks.xml:189(replaceable) ./doc/install-guide/section_neutron-provider-router-with-private_networks.xml:322(replaceable) ./doc/install-guide/section_neutron-provider-router-with-private_networks.xml:333(replaceable) ./doc/install-guide/section_ceilometer-glance.xml:18(replaceable) ./doc/install-guide/section_ceilometer-glance.xml:24(replaceable) ./doc/install-guide/section_neutron-single-flat.xml:207(replaceable) ./doc/install-guide/section_neutron-single-flat.xml:230(replaceable) ./doc/install-guide/section_neutron-single-flat.xml:333(replaceable) ./doc/install-guide/section_neutron-single-flat.xml:360(replaceable) ./doc/install-guide/section_neutron-single-flat.xml:425(replaceable) ./doc/install-guide/section_neutron-single-flat.xml:444(replaceable) ./doc/install-guide/ch_basics.xml:640(replaceable) ./doc/install-guide/section_cinder-node.xml:130(replaceable) ./doc/install-guide/section_cinder-node.xml:150(replaceable) ./doc/install-guide/section_cinder-controller.xml:110(replaceable) ./doc/install-guide/section_cinder-controller.xml:130(replaceable) ./doc/install-guide/section_neutron-install.xml:307(replaceable) ./doc/install-guide/section_neutron-install.xml:316(replaceable) ./doc/install-guide/section_neutron-install.xml:871(replaceable) ./doc/install-guide/section_neutron-install.xml:901(replaceable) ./doc/install-guide/section_neutron-install.xml:1322(replaceable) ./doc/install-guide/section_neutron-install.xml:1349(replaceable) ./doc/install-guide/section_heat-install.xml:93(replaceable) ./doc/install-guide/section_heat-install.xml:96(replaceable) ./doc/install-guide/section_ceilometer-nova.xml:75(replaceable) ./doc/install-guide/section_ceilometer-nova.xml:79(replaceable) ./doc/install-guide/section_nova-compute.xml:142(replaceable) ./doc/install-guide/section_nova-compute.xml:148(replaceable) +msgid "RABBIT_PASS" +msgstr "" + +#: ./doc/install-guide/section_ceilometer-install.xml:140(para) ./doc/install-guide/section_ceilometer-install.xml:153(para) ./doc/install-guide/section_ceilometer-nova.xml:76(para) ./doc/install-guide/section_ceilometer-nova.xml:129(para) +msgid "Edit the /etc/ceilometer/ceilometer.conf file and update the [DEFAULT] section:" +msgstr "" + +#: ./doc/install-guide/section_ceilometer-install.xml:146(para) +msgid "Configure collector dispatcher:" +msgstr "" + +#: ./doc/install-guide/section_ceilometer-install.xml:152(para) ./doc/install-guide/section_ceilometer-nova.xml:128(para) +msgid "Configure the log directory." +msgstr "" + +#: ./doc/install-guide/section_ceilometer-install.xml:160(para) +msgid "Create a ceilometer user that the Telemetry service uses to authenticate with the Identity Service. Use the service tenant and give the user the admin role:" +msgstr "" + +#: ./doc/install-guide/section_ceilometer-install.xml:164(replaceable) ./doc/install-guide/section_ceilometer-install.xml:179(replaceable) ./doc/install-guide/section_ceilometer-install.xml:185(replaceable) ./doc/install-guide/section_ceilometer-install.xml:196(replaceable) ./doc/install-guide/section_ceilometer-install.xml:202(replaceable) ./doc/install-guide/section_ceilometer-nova.xml:98(replaceable) ./doc/install-guide/section_ceilometer-nova.xml:104(replaceable) ./doc/install-guide/section_ceilometer-nova.xml:117(replaceable) ./doc/install-guide/section_ceilometer-nova.xml:124(replaceable) +msgid "CEILOMETER_PASS" +msgstr "" + +#: ./doc/install-guide/section_ceilometer-install.xml:164(replaceable) +msgid "ceilometer@example.com" +msgstr "" + +#: ./doc/install-guide/section_ceilometer-install.xml:168(para) +msgid "Add the credentials to the configuration files for the Telemetry service:" +msgstr "" + +#: ./doc/install-guide/section_ceilometer-install.xml:186(para) ./doc/install-guide/section_ceilometer-nova.xml:107(para) +msgid "Edit the /etc/ceilometer/ceilometer.conf file and change the [keystone_authtoken] section:" +msgstr "" + +#: ./doc/install-guide/section_ceilometer-install.xml:197(para) ./doc/install-guide/section_ceilometer-nova.xml:118(para) +msgid "Also set the [service_credentials] section:" +msgstr "" + +#: ./doc/install-guide/section_ceilometer-install.xml:205(para) +msgid "Register the Telemetry service with the Identity Service so that other OpenStack services can locate it. Use the command to register the service and specify the endpoint:" +msgstr "" + +#: ./doc/install-guide/section_ceilometer-install.xml:218(para) +msgid "Restart the services with their new settings:" +msgstr "" + +#: ./doc/install-guide/section_ceilometer-install.xml:224(para) +msgid "Start the openstack-ceilometer-api, openstack-ceilometer-agent-centralopenstack-ceilometer-central and openstack-ceilometer-collector services and configure them to start when the system boots:" +msgstr "" + +#: ./doc/install-guide/section_ceilometer-verify.xml:5(title) +msgid "Verify the Telemetry Service installation" +msgstr "" + +#: ./doc/install-guide/section_ceilometer-verify.xml:6(para) +msgid "To test the Telemetry Service installation, download an image from the Image Service, and use the Telemetry Service to display usage statistics." +msgstr "" + +#: ./doc/install-guide/section_ceilometer-verify.xml:11(para) +msgid "Use the ceilometer meter-list command to test the access to the Telemetry Service:" +msgstr "" + +#: ./doc/install-guide/section_ceilometer-verify.xml:22(para) +msgid "Download an image from the Image Service:" +msgstr "" + +#: ./doc/install-guide/section_ceilometer-verify.xml:26(para) +msgid "Call the ceilometer meter-list command again to validate that the download has been detected and stored by the Telemetry Service:" +msgstr "" + +#: ./doc/install-guide/section_ceilometer-verify.xml:40(para) +msgid "You can now get usage statistics for the various meters:" +msgstr "" + +#: ./doc/install-guide/section_nova-controller.xml:5(title) +msgid "Install Compute controller services" +msgstr "" + +#: ./doc/install-guide/section_nova-controller.xml:6(para) +msgid "Compute is a collection of services that enable you to launch virtual machine instances. You can configure these services to run on separate nodes or the same node. In this guide, most services run on the controller node and the service that launches virtual machines runs on a dedicated compute node. This section shows you how to install and configure these services on the controller node." +msgstr "" + +#: ./doc/install-guide/section_nova-controller.xml:15(para) +msgid "Install the openstack-nova meta-package, which installs various Compute packages that are used on the controller node." +msgstr "" + +#: ./doc/install-guide/section_nova-controller.xml:20(para) +msgid "Install these Compute packages, which provide the Compute services that run on the controller node." +msgstr "" + +#: ./doc/install-guide/section_nova-controller.xml:38(para) +msgid "Respond to the prompts for database management, [keystone_authtoken] settings, RabbitMQ credentials, and API endpoint registration. The command runs automatically." +msgstr "" + +#: ./doc/install-guide/section_nova-controller.xml:49(para) +msgid "Compute stores information in a database. In this guide, we use a MySQL database on the controller node. Configure Compute with the database location and credentials. Replace NOVA_DBPASS with the password for the database that you will create in a later step." +msgstr "" + +#: ./doc/install-guide/section_nova-controller.xml:55(replaceable) ./doc/install-guide/section_nova-controller.xml:61(replaceable) ./doc/install-guide/section_nova-controller.xml:93(replaceable) ./doc/install-guide/section_nova-controller.xml:107(replaceable) ./doc/install-guide/section_nova-controller.xml:109(replaceable) ./doc/install-guide/section_nova-compute.xml:110(replaceable) +msgid "NOVA_DBPASS" +msgstr "" + +#: ./doc/install-guide/section_nova-controller.xml:56(para) +msgid "Edit the [database] section in the /etc/nova/nova.conf file to modify this key:" +msgstr "" + +#: ./doc/install-guide/section_nova-controller.xml:65(para) +msgid "Set these configuration keys to configure Compute to use the Qpid message broker:" +msgstr "" + +#: ./doc/install-guide/section_nova-controller.xml:72(para) ./doc/install-guide/section_nova-compute.xml:136(para) +msgid "Configure the Compute Service to use the RabbitMQ message broker by setting these configuration keys in the [DEFAULT] configuration group of the /etc/nova/nova.conf file:" +msgstr "" + +#: ./doc/install-guide/section_nova-controller.xml:81(para) +msgid "Set these configuration keys to configure Compute to use the RabbitMQ message broker:" +msgstr "" + +#: ./doc/install-guide/section_nova-controller.xml:90(para) +msgid "Run the command to create the Compute service database and tables and a nova database user." +msgstr "" + +#: ./doc/install-guide/section_nova-controller.xml:96(para) +msgid "By default, the Ubuntu packages create an SQLite database. Delete the nova.sqlite file created in the /var/lib/nova/ directory so that it does not get used by mistake." +msgstr "" + +#: ./doc/install-guide/section_nova-controller.xml:102(para) +msgid "Use the password you created previously to log in as root. Create a nova database user:" +msgstr "" + +#: ./doc/install-guide/section_nova-controller.xml:112(para) +msgid "Create the Compute service tables:" +msgstr "" + +#: ./doc/install-guide/section_nova-controller.xml:116(para) +msgid "Set the , , and configuration options to the internal IP address of the controller node:" +msgstr "" + +#: ./doc/install-guide/section_nova-controller.xml:124(para) ./doc/install-guide/section_nova-network.xml:62(para) +msgid "Edit the /etc/nova/nova.conf file and add these lines to the [DEFAULT] section:" +msgstr "" + +#: ./doc/install-guide/section_nova-controller.xml:127(para) +msgid "In Debian, the debconf package automatically sets up my_ip parameter but you must edit the /etc/nova/nova.conf file to configure the and options, which appear at the end of the file:" +msgstr "" + +#: ./doc/install-guide/section_nova-controller.xml:142(para) +msgid "Create a nova user that Compute uses to authenticate with the Identity Service. Use the service tenant and give the user the admin role:" +msgstr "" + +#: ./doc/install-guide/section_nova-controller.xml:146(replaceable) ./doc/install-guide/section_nova-controller.xml:159(replaceable) ./doc/install-guide/section_nova-controller.xml:178(replaceable) ./doc/install-guide/section_nova-controller.xml:200(replaceable) ./doc/install-guide/section_nova-compute.xml:117(replaceable) ./doc/install-guide/section_nova-compute.xml:226(replaceable) +msgid "NOVA_PASS" +msgstr "" + +#: ./doc/install-guide/section_nova-controller.xml:146(replaceable) +msgid "nova@example.com" +msgstr "" + +#: ./doc/install-guide/section_nova-controller.xml:150(para) +msgid "Configure Compute to use these credentials with the Identity Service running on the controller. Replace NOVA_PASS with your Compute password." +msgstr "" + +#: ./doc/install-guide/section_nova-controller.xml:160(para) +msgid "Edit the [DEFAULT] section in the /etc/nova/nova.conf file to add this key:" +msgstr "" + +#: ./doc/install-guide/section_nova-controller.xml:168(para) +msgid "Add these keys to the [keystone_authtoken] section:" +msgstr "" + +#: ./doc/install-guide/section_nova-controller.xml:182(para) +msgid "Add the credentials to the /etc/nova/api-paste.ini file. Add these options to the [filter:authtoken] section:" +msgstr "" + +#: ./doc/install-guide/section_nova-controller.xml:187(title) ./doc/install-guide/section_nova-compute.xml:214(title) +msgid "Use of .ini files" +msgstr "" + +#: ./doc/install-guide/section_nova-controller.xml:188(para) +msgid "You might sometimes have to edit .ini files during initial setup. However, do not edit these files for general configuration tasks." +msgstr "" + +#: ./doc/install-guide/section_nova-controller.xml:202(para) +msgid "Ensure that the option is set in the /etc/nova/nova.conf file." +msgstr "" + +#: ./doc/install-guide/section_nova-controller.xml:209(para) +msgid "You must register Compute with the Identity Service so that other OpenStack services can locate it. Register the service and specify the endpoint:" +msgstr "" + +#: ./doc/install-guide/section_nova-controller.xml:222(para) +msgid "Start Compute services and configure them to start when the system boots:" +msgstr "" + +#: ./doc/install-guide/section_nova-controller.xml:225(para) +msgid "Restart Compute services:" +msgstr "" + +#: ./doc/install-guide/section_nova-controller.xml:246(para) +msgid "To verify your configuration, list available images:" +msgstr "" + +#: ./doc/install-guide/section_dashboard-system-reqs.xml:6(title) ./doc/install-guide/object-storage/section_object-storage-sys-requirements.xml:7(title) +msgid "System requirements" +msgstr "" + +#: ./doc/install-guide/section_dashboard-system-reqs.xml:7(para) +msgid "Before you install the OpenStack dashboard, you must meet the following system requirements:" +msgstr "" + +#: ./doc/install-guide/section_dashboard-system-reqs.xml:11(para) +msgid "OpenStack Compute installation. Enable the Identity Service for user and project management." +msgstr "" + +#: ./doc/install-guide/section_dashboard-system-reqs.xml:13(para) +msgid "Note the URLs of the Identity Service and Compute endpoints." +msgstr "" + +#: ./doc/install-guide/section_dashboard-system-reqs.xml:17(para) +msgid "Identity Service user with sudo privileges. Because Apache does not serve content from a root user, users must run the dashboard as an Identity Service user with sudo privileges." +msgstr "" + +#: ./doc/install-guide/section_dashboard-system-reqs.xml:23(para) +msgid "Python 2.6 or 2.7. The Python version must support Django. The Python version should run on any system, including Mac OS X. Installation prerequisites might differ by platform." +msgstr "" + +#: ./doc/install-guide/section_dashboard-system-reqs.xml:29(para) +msgid "Then, install and configure the dashboard on a node that can contact the Identity Service." +msgstr "" + +#: ./doc/install-guide/section_dashboard-system-reqs.xml:31(para) +msgid "Provide users with the following information so that they can access the dashboard through a web browser on their local machine:" +msgstr "" + +#: ./doc/install-guide/section_dashboard-system-reqs.xml:36(para) +msgid "The public IP address from which they can access the dashboard" +msgstr "" + +#: ./doc/install-guide/section_dashboard-system-reqs.xml:40(para) +msgid "The user name and password with which they can access the dashboard" +msgstr "" + +#: ./doc/install-guide/section_dashboard-system-reqs.xml:44(para) +msgid "Your web browser, and that of your users, must support HTML5 and have cookies and JavaScript enabled." +msgstr "" + +#: ./doc/install-guide/section_dashboard-system-reqs.xml:48(para) +msgid "To use the VNC client with the dashboard, the browser must support HTML5 Canvas and HTML5 WebSockets." +msgstr "" + +#: ./doc/install-guide/section_dashboard-system-reqs.xml:50(para) +msgid "For details about browsers that support noVNC, see https://github.com/kanaka/noVNC/blob/master/README.md, and https://github.com/kanaka/noVNC/wiki/Browser-support, respectively." +msgstr "" + +#: ./doc/install-guide/section_nova-boot.xml:5(title) +msgid "Launch an instance" +msgstr "" + +#: ./doc/install-guide/section_nova-boot.xml:6(para) +msgid "After you configure the Compute services, you can launch an instance. An instance is a virtual machine that OpenStack provisions on a Compute server. This example shows you how to launch a low-resource instance by using a downloaded image." +msgstr "" + +#: ./doc/install-guide/section_nova-boot.xml:12(para) +msgid "This procedure assumes you have:" +msgstr "" + +#: ./doc/install-guide/section_nova-boot.xml:15(para) +msgid "Installed the nova client library on the machine on which you will run the commands (log on the controller if you are not sure)." +msgstr "" + +#: ./doc/install-guide/section_nova-boot.xml:20(para) +msgid "Set environment variables to specify your credentials. See ." +msgstr "" + +#: ./doc/install-guide/section_nova-boot.xml:24(para) +msgid "Downloaded an image. See ." +msgstr "" + +#: ./doc/install-guide/section_nova-boot.xml:28(para) +msgid "Configured networking. See ." +msgstr "" + +#: ./doc/install-guide/section_nova-boot.xml:35(para) +msgid "Generate a keypair that consists of a private and public key to be able to launch instances on OpenStack. These keys are injected into the instances to make password-less SSH access to the instance. This depends on the way the necessary tools are bundled into the images. For more details, see the OpenStack Admin User Guide." +msgstr "" + +#: ./doc/install-guide/section_nova-boot.xml:47(para) +msgid "You have just created the mykey keypair. The id_rsa private key is saved locally in ~/.ssh, which you can use to connect to an instance launched by using mykey as the keypair. To view available keypairs:" +msgstr "" + +#: ./doc/install-guide/section_nova-boot.xml:60(para) +msgid "To launch an instance, you must specify the ID for the flavor you want to use for the instance. A flavor is a resource allocation profile. For example, it specifies how many virtual CPUs and how much RAM your instance gets. To see a list of the available profiles:" +msgstr "" + +#: ./doc/install-guide/section_nova-boot.xml:77(para) +msgid "Get the ID of the image to use for the instance:" +msgstr "" + +#: ./doc/install-guide/section_nova-boot.xml:86(para) +msgid "To use SSH and ping, you must configure security group rules. See the OpenStack User Guide." +msgstr "" + +#: ./doc/install-guide/section_nova-boot.xml:91(replaceable) ./doc/install-guide/section_nova-boot.xml:92(replaceable) +msgid "default" +msgstr "" + +#: ./doc/install-guide/section_nova-boot.xml:95(para) +msgid "Launch the instance:" +msgstr "" + +#: ./doc/install-guide/section_nova-boot.xml:96(replaceable) +msgid "flavorType" +msgstr "" + +#: ./doc/install-guide/section_nova-boot.xml:96(replaceable) +msgid "keypairName" +msgstr "" + +#: ./doc/install-guide/section_nova-boot.xml:96(replaceable) ./doc/install-guide/app_reserved_uids.xml:29(th) +msgid "ID" +msgstr "" + +#: ./doc/install-guide/section_nova-boot.xml:96(replaceable) +msgid "newInstanceName" +msgstr "" + +#: ./doc/install-guide/section_nova-boot.xml:97(para) +msgid "Create an instance by using flavor 1 or 2. For example:" +msgstr "" + +#: ./doc/install-guide/section_nova-boot.xml:134(para) +msgid "If sufficient RAM is not available for the instance, Compute creates, but does not start, the instance and sets the status for the instance to ERROR." +msgstr "" + +#: ./doc/install-guide/section_nova-boot.xml:141(para) +msgid "After the instance launches, use the to view its status. The status changes from BUILD to ACTIVE:" +msgstr "" + +#: ./doc/install-guide/section_nova-boot.xml:159(para) +msgid "To show details for a specified instance:" +msgstr "" + +#: ./doc/install-guide/section_nova-boot.xml:197(para) +msgid "After the instance boots and initializes and you have configured security groups, you can into the instance without a password by using the keypair you specified in the command. Use the command to get the IP address for the instance. You do not need to specify the private key because it was stored in the default location, ~/.ssh/.id_rsa, for the client." +msgstr "" + +#: ./doc/install-guide/section_nova-boot.xml:207(para) +msgid "If using a CirrOS image to spawn an instance you must log in as the cirros, and not the root, user." +msgstr "" + +#: ./doc/install-guide/section_nova-boot.xml:210(para) +msgid "You can also log in to the cirros account without an ssh key by using the cubswin:) password:" +msgstr "" + +#: ./doc/install-guide/section_keystone-services.xml:4(title) +msgid "Define services and API endpoints" +msgstr "" + +#: ./doc/install-guide/section_keystone-services.xml:5(para) +msgid "So that the Identity Service can track which OpenStack services are installed and where they are located on the network, you must register each service in your OpenStack installation. To register a service, run these commands:" +msgstr "" + +#: ./doc/install-guide/section_keystone-services.xml:11(para) +msgid ". Describes the service." +msgstr "" + +#: ./doc/install-guide/section_keystone-services.xml:15(para) +msgid ". Associates API endpoints with the service." +msgstr "" + +#: ./doc/install-guide/section_keystone-services.xml:20(para) +msgid "You must also register the Identity Service itself. Use the OS_SERVICE_TOKEN environment variable, as set previously, for authentication." +msgstr "" + +#: ./doc/install-guide/section_keystone-services.xml:25(para) +msgid "Create a service entry for the Identity Service:" +msgstr "" + +#: ./doc/install-guide/section_keystone-services.xml:36(para) ./doc/install-guide/object-storage/section_object-storage-install.xml:91(para) +msgid "The service ID is randomly generated and is different from the one shown here." +msgstr "" + +#: ./doc/install-guide/section_keystone-services.xml:40(para) +msgid "Specify an API endpoint for the Identity Service by using the returned service ID. When you specify an endpoint, you provide URLs for the public API, internal API, and admin API. In this guide, the controller host name is used. Note that the Identity Service uses a different port for the admin API." +msgstr "" + +#: ./doc/install-guide/section_keystone-services.xml:63(para) +msgid "You will need to create an additional endpoint for each service added to your OpenStack environment. The sections of this guide associated with the installation of each service include the endpoint creation step specific to the service." +msgstr "" + +#: ./doc/install-guide/section_keystone-verify.xml:6(title) +msgid "Verify the Identity Service installation" +msgstr "" + +#: ./doc/install-guide/section_keystone-verify.xml:9(para) +msgid "To verify that the Identity Service is installed and configured correctly, clear the values in the OS_SERVICE_TOKEN and OS_SERVICE_ENDPOINT environment variables:" +msgstr "" + +#: ./doc/install-guide/section_keystone-verify.xml:15(para) +msgid "These variables, which were used to bootstrap the administrative user and register the Identity Service, are no longer needed." +msgstr "" + +#: ./doc/install-guide/section_keystone-verify.xml:20(para) +msgid "You can now use regular user name-based authentication." +msgstr "" + +#: ./doc/install-guide/section_keystone-verify.xml:22(para) +msgid "Request a authentication token by using the admin user and the password you chose for that user:" +msgstr "" + +#: ./doc/install-guide/section_keystone-verify.xml:27(para) +msgid "In response, you receive a token paired with your user ID. This verifies that the Identity Service is running on the expected endpoint and that your user account is established with the expected credentials." +msgstr "" + +#: ./doc/install-guide/section_keystone-verify.xml:33(para) +msgid "Verify that authorization behaves as expected. To do so, request authorization on a tenant:" +msgstr "" + +#: ./doc/install-guide/section_keystone-verify.xml:38(para) +msgid "In response, you receive a token that includes the ID of the tenant that you specified. This verifies that your user account has an explicitly defined role on the specified tenant and the tenant exists as expected." +msgstr "" + +#: ./doc/install-guide/section_keystone-verify.xml:44(para) +msgid "You can also set your --os-* variables in your environment to simplify command-line usage. Set up a openrc.sh file with the admin credentials and admin endpoint:" +msgstr "" + +#: ./doc/install-guide/section_keystone-verify.xml:54(para) +msgid "Source this file to read in the environment variables:" +msgstr "" + +#: ./doc/install-guide/section_keystone-verify.xml:59(para) +msgid "Verify that your openrc.sh file is configured correctly. Run the same command without the --os-* arguments:" +msgstr "" + +#: ./doc/install-guide/section_keystone-verify.xml:63(para) +msgid "The command returns a token and the ID of the specified tenant. This verifies that you have configured your environment variables correctly." +msgstr "" + +#: ./doc/install-guide/section_keystone-verify.xml:68(para) +msgid "Verify that your admin account has authorization to perform administrative commands:" +msgstr "" + +#: ./doc/install-guide/section_keystone-verify.xml:76(para) +msgid "This verifies that your user account has the admin role, which matches the role used in the Identity Service policy.json file." +msgstr "" + +#: ./doc/install-guide/section_keystone-verify.xml:81(para) +msgid "As long as you define your credentials and the Identity Service endpoint through the command line or environment variables, you can run all OpenStack client commands from any machine. For details, see ." +msgstr "" + +#. When image changes, this message will be marked fuzzy or untranslated for you. +#. It doesn't matter what you translate it to: it's not used at all. +#: ./doc/install-guide/section_neutron-per-tenant-routers-with-private-networks.xml:15(None) ./doc/install-guide/section_neutron-per-tenant-routers-with-private-networks.xml:863(None) +msgid "@@image: '../common/figures/UseCase-MultiRouter.png'; md5=5695d4b003e2f8442eab135cbcd1f842" +msgstr "" + +#. When image changes, this message will be marked fuzzy or untranslated for you. +#. It doesn't matter what you translate it to: it's not used at all. +#: ./doc/install-guide/section_neutron-per-tenant-routers-with-private-networks.xml:25(None) +msgid "@@image: '../common/figures/demo_routers_with_private_networks.png'; md5=985b8cacfd7161ce50ee13106b27f854" +msgstr "" + +#: ./doc/install-guide/section_neutron-per-tenant-routers-with-private-networks.xml:6(title) +msgid "Per-tenant routers with private networks" +msgstr "" + +#: ./doc/install-guide/section_neutron-per-tenant-routers-with-private-networks.xml:7(para) +msgid "This section describes how to install the OpenStack Networking service and its components for a use case that has per-tenant routers with private networks." +msgstr "" + +#: ./doc/install-guide/section_neutron-per-tenant-routers-with-private-networks.xml:19(para) +msgid "The following figure shows the setup:" +msgstr "" + +#: ./doc/install-guide/section_neutron-per-tenant-routers-with-private-networks.xml:29(para) +msgid "As shown in the figure, the setup includes:" +msgstr "" + +#: ./doc/install-guide/section_neutron-per-tenant-routers-with-private-networks.xml:32(para) +msgid "An interface for management traffic on each node." +msgstr "" + +#: ./doc/install-guide/section_neutron-per-tenant-routers-with-private-networks.xml:36(para) +msgid "Use of the Open vSwitch plug-in." +msgstr "" + +#: ./doc/install-guide/section_neutron-per-tenant-routers-with-private-networks.xml:39(para) +msgid "GRE tunnels for data transport on all agents." +msgstr "" + +#: ./doc/install-guide/section_neutron-per-tenant-routers-with-private-networks.xml:42(para) +msgid "Floating IPs and router gateway ports that are configured in an external network, and a physical router that connects the floating IPs and router gateway ports to the outside world." +msgstr "" + +#: ./doc/install-guide/section_neutron-per-tenant-routers-with-private-networks.xml:49(para) +msgid "Because this example runs a DHCP agent and L3 agent on one node, you must set the use_namespace option to True in the configuration file for each agent. The default is True." +msgstr "" + +#: ./doc/install-guide/section_neutron-per-tenant-routers-with-private-networks.xml:55(para) +msgid "This table describes the nodes:" +msgstr "" + +#: ./doc/install-guide/section_neutron-per-tenant-routers-with-private-networks.xml:61(th) ./doc/install-guide/section_neutron-provider-router-with-private_networks.xml:31(th) ./doc/install-guide/section_neutron-single-flat.xml:32(th) +msgid "Node" +msgstr "" + +#: ./doc/install-guide/section_neutron-per-tenant-routers-with-private-networks.xml:62(th) ./doc/install-guide/section_neutron-provider-router-with-private_networks.xml:32(th) ./doc/install-guide/app_reserved_uids.xml:28(th) ./doc/install-guide/section_neutron-single-flat.xml:33(th) +msgid "Description" +msgstr "" + +#: ./doc/install-guide/section_neutron-per-tenant-routers-with-private-networks.xml:67(td) ./doc/install-guide/section_neutron-single-flat.xml:38(td) +msgid "Controller Node" +msgstr "" + +#: ./doc/install-guide/section_neutron-per-tenant-routers-with-private-networks.xml:68(para) +msgid "Runs Networking, Identity Service, and all Compute services that are required to deploy VMs (nova-api, nova-scheduler, for example). The node must have at least one network interface, which connects to the Management Network. The host name is controlnode, which other nodes resolve to the IP of the controller node." +msgstr "" + +#: ./doc/install-guide/section_neutron-per-tenant-routers-with-private-networks.xml:80(para) +msgid "The nova-network service should not be running. This is replaced by Networking." +msgstr "" + +#: ./doc/install-guide/section_neutron-per-tenant-routers-with-private-networks.xml:87(td) ./doc/install-guide/section_neutron-provider-router-with-private_networks.xml:281(title) ./doc/install-guide/section_neutron-single-flat.xml:70(td) +msgid "Compute Node" +msgstr "" + +#: ./doc/install-guide/section_neutron-per-tenant-routers-with-private-networks.xml:90(systemitem) ./doc/install-guide/section_neutron-single-flat.xml:73(systemitem) +msgid "nova-compute" +msgstr "" + +#: ./doc/install-guide/section_neutron-per-tenant-routers-with-private-networks.xml:92(systemitem) +msgid "nova-*" +msgstr "" + +#: ./doc/install-guide/section_neutron-per-tenant-routers-with-private-networks.xml:88(td) +msgid "Runs the Networking L2 agent and the Compute services that run VMs ( specifically, and optionally other services depending on configuration). The node must have at least two network interfaces. One interface communicates with the controller node through the management network. The other node is used for the VM traffic on the data network. The VM receives its IP address from the DHCP agent on this network." +msgstr "" + +#: ./doc/install-guide/section_neutron-per-tenant-routers-with-private-networks.xml:101(td) ./doc/install-guide/section_neutron-single-flat.xml:84(td) +msgid "Network Node" +msgstr "" + +#: ./doc/install-guide/section_neutron-per-tenant-routers-with-private-networks.xml:102(td) +msgid "Runs Networking L2 agent, DHCP agent and L3 agent. This node has access to the external network. The DHCP agent allocates IP addresses to the VMs on data network. (Technically, the addresses are allocated by the Networking server, and distributed by the dhcp agent.) The node must have at least two network interfaces. One interface communicates with the controller node through the management network. The other interface is used as external network. GRE tunnels are set up as data networks." +msgstr "" + +#: ./doc/install-guide/section_neutron-per-tenant-routers-with-private-networks.xml:115(td) ./doc/install-guide/section_neutron-single-flat.xml:94(td) +msgid "Router" +msgstr "" + +#: ./doc/install-guide/section_neutron-per-tenant-routers-with-private-networks.xml:116(td) ./doc/install-guide/section_neutron-single-flat.xml:95(td) +msgid "Router has IP 30.0.0.1, which is the default gateway for all VMs. The router must be able to access public networks." +msgstr "" + +#: ./doc/install-guide/section_neutron-per-tenant-routers-with-private-networks.xml:122(para) +msgid "The use case assumes the following:" +msgstr "" + +#: ./doc/install-guide/section_neutron-per-tenant-routers-with-private-networks.xml:123(emphasis) ./doc/install-guide/section_neutron-single-flat.xml:102(emphasis) +msgid "Controller node" +msgstr "" + +#: ./doc/install-guide/section_neutron-per-tenant-routers-with-private-networks.xml:126(para) ./doc/install-guide/section_neutron-single-flat.xml:105(para) +msgid "Relevant Compute services are installed, configured, and running." +msgstr "" + +#: ./doc/install-guide/section_neutron-per-tenant-routers-with-private-networks.xml:130(para) +msgid "Glance is installed, configured, and running. In addition, an image named tty must be present." +msgstr "" + +#: ./doc/install-guide/section_neutron-per-tenant-routers-with-private-networks.xml:135(para) +msgid "Identity is installed, configured, and running. A Networking user named neutron should be created on tenant service with password NEUTRON_PASS." +msgstr "" + +#: ./doc/install-guide/section_neutron-per-tenant-routers-with-private-networks.xml:145(para) +msgid "RabbitMQ is running with default guest and password RABBIT_PASS." +msgstr "" + +#: ./doc/install-guide/section_neutron-per-tenant-routers-with-private-networks.xml:150(para) ./doc/install-guide/section_neutron-single-flat.xml:133(para) +msgid "MySQL server (user is root)." +msgstr "" + +#: ./doc/install-guide/section_neutron-per-tenant-routers-with-private-networks.xml:143(para) +msgid "Additional services: " +msgstr "" + +#: ./doc/install-guide/section_neutron-per-tenant-routers-with-private-networks.xml:156(emphasis) ./doc/install-guide/section_neutron-single-flat.xml:139(emphasis) +msgid "Compute node" +msgstr "" + +#: ./doc/install-guide/section_neutron-per-tenant-routers-with-private-networks.xml:157(para) +msgid "Install and configure Compute." +msgstr "" + +#: ./doc/install-guide/section_neutron-per-tenant-routers-with-private-networks.xml:159(title) ./doc/install-guide/section_neutron-provider-router-with-private_networks.xml:91(title) ./doc/install-guide/section_neutron-single-flat.xml:146(title) +msgid "Install" +msgstr "" + +#: ./doc/install-guide/section_neutron-per-tenant-routers-with-private-networks.xml:162(emphasis) ./doc/install-guide/section_neutron-single-flat.xml:149(emphasis) +msgid "Controller node - Networking server" +msgstr "" + +#: ./doc/install-guide/section_neutron-per-tenant-routers-with-private-networks.xml:166(para) ./doc/install-guide/section_neutron-single-flat.xml:154(para) +msgid "Install the Networking server." +msgstr "" + +#: ./doc/install-guide/section_neutron-per-tenant-routers-with-private-networks.xml:169(para) ./doc/install-guide/section_neutron-single-flat.xml:168(para) +msgid "Create database ovs_neutron." +msgstr "" + +#: ./doc/install-guide/section_neutron-per-tenant-routers-with-private-networks.xml:173(para) +msgid "Update the Networking configuration file, /etc/neutron/neutron.conf, with plug-in choice and Identity Service user as necessary:" +msgstr "" + +#: ./doc/install-guide/section_neutron-per-tenant-routers-with-private-networks.xml:186(replaceable) ./doc/install-guide/section_neutron-per-tenant-routers-with-private-networks.xml:199(replaceable) ./doc/install-guide/section_neutron-per-tenant-routers-with-private-networks.xml:276(replaceable) ./doc/install-guide/section_neutron-provider-router-with-private_networks.xml:116(replaceable) ./doc/install-guide/section_neutron-provider-router-with-private_networks.xml:181(replaceable) ./doc/install-guide/section_neutron-provider-router-with-private_networks.xml:185(replaceable) ./doc/install-guide/section_neutron-provider-router-with-private_networks.xml:191(replaceable) ./doc/install-guide/section_neutron-provider-router-with-private_networks.xml:325(replaceable) ./doc/install-guide/section_neutron-provider-router-with-private_networks.xml:329(replaceable) ./doc/install-guide/section_neutron-provider-router-with-private_networks.xml:335(replaceable) ./doc/install-guide/section_neutron-single-flat.xml:193(replaceable) ./doc/install-guide/section_neutron-single-flat.xml:234(replaceable) ./doc/install-guide/section_neutron-single-flat.xml:337(replaceable) ./doc/install-guide/section_neutron-single-flat.xml:346(replaceable) ./doc/install-guide/section_neutron-install.xml:141(replaceable) ./doc/install-guide/section_neutron-install.xml:143(replaceable) ./doc/install-guide/section_neutron-install.xml:334(replaceable) ./doc/install-guide/section_neutron-install.xml:341(replaceable) ./doc/install-guide/section_neutron-install.xml:912(replaceable) ./doc/install-guide/section_neutron-install.xml:919(replaceable) ./doc/install-guide/section_neutron-install.xml:1220(replaceable) ./doc/install-guide/section_neutron-install.xml:1230(replaceable) +msgid "NEUTRON_DBPASS" +msgstr "" + +#: ./doc/install-guide/section_neutron-per-tenant-routers-with-private-networks.xml:191(replaceable) ./doc/install-guide/section_neutron-per-tenant-routers-with-private-networks.xml:236(replaceable) ./doc/install-guide/section_neutron-provider-router-with-private_networks.xml:132(replaceable) ./doc/install-guide/section_neutron-provider-router-with-private_networks.xml:225(replaceable) ./doc/install-guide/section_neutron-provider-router-with-private_networks.xml:237(replaceable) ./doc/install-guide/section_neutron-single-flat.xml:190(replaceable) ./doc/install-guide/section_neutron-single-flat.xml:239(replaceable) ./doc/install-guide/section_neutron-single-flat.xml:283(replaceable) ./doc/install-guide/section_neutron-single-flat.xml:299(replaceable) ./doc/install-guide/section_neutron-install.xml:149(replaceable) ./doc/install-guide/section_neutron-install.xml:266(replaceable) ./doc/install-guide/section_neutron-install.xml:288(replaceable) ./doc/install-guide/section_neutron-install.xml:357(replaceable) ./doc/install-guide/section_neutron-install.xml:369(replaceable) ./doc/install-guide/section_neutron-install.xml:439(replaceable) ./doc/install-guide/section_neutron-install.xml:453(replaceable) ./doc/install-guide/section_neutron-install.xml:859(replaceable) ./doc/install-guide/section_neutron-install.xml:893(replaceable) ./doc/install-guide/section_neutron-install.xml:930(replaceable) ./doc/install-guide/section_neutron-install.xml:944(replaceable) ./doc/install-guide/section_neutron-install.xml:961(replaceable) ./doc/install-guide/section_neutron-install.xml:978(replaceable) ./doc/install-guide/section_neutron-install.xml:1253(replaceable) ./doc/install-guide/section_neutron-install.xml:1279(replaceable) ./doc/install-guide/section_neutron-install.xml:1295(replaceable) ./doc/install-guide/section_neutron-install.xml:1311(replaceable) ./doc/install-guide/section_neutron-install.xml:1380(replaceable) ./doc/install-guide/section_neutron-install.xml:1397(replaceable) +msgid "NEUTRON_PASS" +msgstr "" + +#: ./doc/install-guide/section_neutron-per-tenant-routers-with-private-networks.xml:202(para) +msgid "Update the plug-in configuration file, /etc/neutron/plugins/openvswitch/ovs_neutron_plugin.ini:" +msgstr "" + +#: ./doc/install-guide/section_neutron-per-tenant-routers-with-private-networks.xml:210(para) +msgid "Start the Networking server." +msgstr "" + +#: ./doc/install-guide/section_neutron-per-tenant-routers-with-private-networks.xml:211(para) +msgid "The Networking server can be a service of the operating system. The command to start the service depends on your operating system. The following command runs the Networking server directly:" +msgstr "" + +#: ./doc/install-guide/section_neutron-per-tenant-routers-with-private-networks.xml:223(emphasis) +msgid "Compute node—Compute" +msgstr "" + +#: ./doc/install-guide/section_neutron-per-tenant-routers-with-private-networks.xml:225(para) +msgid "Install Compute services." +msgstr "" + +#: ./doc/install-guide/section_neutron-per-tenant-routers-with-private-networks.xml:228(para) +msgid "Update the Compute /etc/nova/nova.conf configuration file. Make sure the following line appears at the end of this file:" +msgstr "" + +#: ./doc/install-guide/section_neutron-per-tenant-routers-with-private-networks.xml:243(para) +msgid "Restart relevant Compute services." +msgstr "" + +#: ./doc/install-guide/section_neutron-per-tenant-routers-with-private-networks.xml:249(emphasis) +msgid "Compute and Networking node—L2 agent" +msgstr "" + +#: ./doc/install-guide/section_neutron-per-tenant-routers-with-private-networks.xml:253(para) +msgid "Install and start Open vSwitch." +msgstr "" + +#: ./doc/install-guide/section_neutron-per-tenant-routers-with-private-networks.xml:256(para) +msgid "Install the L2 agent (Neutron Open vSwitch agent)." +msgstr "" + +#: ./doc/install-guide/section_neutron-per-tenant-routers-with-private-networks.xml:260(para) ./doc/install-guide/section_neutron-provider-router-with-private_networks.xml:168(para) +msgid "Add the integration bridge to the Open vSwitch:" +msgstr "" + +#: ./doc/install-guide/section_neutron-per-tenant-routers-with-private-networks.xml:265(para) +msgid "Update the Networking configuration file, /etc/neutron/neutron.conf:" +msgstr "" + +#: ./doc/install-guide/section_neutron-per-tenant-routers-with-private-networks.xml:279(para) +msgid "Update the plug-in configuration file, /etc/neutron/plugins/openvswitch/ovs_neutron_plugin.ini." +msgstr "" + +#: ./doc/install-guide/section_neutron-per-tenant-routers-with-private-networks.xml:282(para) +msgid "Compute node:" +msgstr "" + +#: ./doc/install-guide/section_neutron-per-tenant-routers-with-private-networks.xml:288(para) +msgid "Network node:" +msgstr "" + +#: ./doc/install-guide/section_neutron-per-tenant-routers-with-private-networks.xml:296(para) +msgid "Create the integration bridge br-int:" +msgstr "" + +#: ./doc/install-guide/section_neutron-per-tenant-routers-with-private-networks.xml:301(para) +msgid "Start the Networking L2 agent" +msgstr "" + +#: ./doc/install-guide/section_neutron-per-tenant-routers-with-private-networks.xml:302(para) +msgid "The Networking Open vSwitch L2 agent can be a service of operating system. The command to start depends on your operating systems. The following command runs the service directly:" +msgstr "" + +#: ./doc/install-guide/section_neutron-per-tenant-routers-with-private-networks.xml:313(emphasis) +msgid "Network node—DHCP agent" +msgstr "" + +#: ./doc/install-guide/section_neutron-per-tenant-routers-with-private-networks.xml:317(para) ./doc/install-guide/section_neutron-single-flat.xml:412(para) +msgid "Install the DHCP agent." +msgstr "" + +#: ./doc/install-guide/section_neutron-per-tenant-routers-with-private-networks.xml:320(para) +msgid "Update the Networking configuration file, /etc/neutron/neutron.conf" +msgstr "" + +#: ./doc/install-guide/section_neutron-per-tenant-routers-with-private-networks.xml:331(literal) +msgid "allow_overlapping_ips" +msgstr "" + +#: ./doc/install-guide/section_neutron-per-tenant-routers-with-private-networks.xml:330(emphasis) +msgid "Set because TenantA and TenantC use overlapping subnets." +msgstr "" + +#: ./doc/install-guide/section_neutron-per-tenant-routers-with-private-networks.xml:336(para) +msgid "Update the DHCP /etc/neutron/dhcp_agent.ini configuration file:" +msgstr "" + +#: ./doc/install-guide/section_neutron-per-tenant-routers-with-private-networks.xml:342(para) +msgid "Start the DHCP agent." +msgstr "" + +#: ./doc/install-guide/section_neutron-per-tenant-routers-with-private-networks.xml:343(para) +msgid "The Networking DHCP agent can be a service of operating system. The command to start the service depends on your operating system. The following command runs the service directly:" +msgstr "" + +#: ./doc/install-guide/section_neutron-per-tenant-routers-with-private-networks.xml:354(emphasis) +msgid "Network node—L3 agent" +msgstr "" + +#: ./doc/install-guide/section_neutron-per-tenant-routers-with-private-networks.xml:358(para) +msgid "Install the L3 agent." +msgstr "" + +#: ./doc/install-guide/section_neutron-per-tenant-routers-with-private-networks.xml:361(para) +msgid "Add the external network bridge" +msgstr "" + +#: ./doc/install-guide/section_neutron-per-tenant-routers-with-private-networks.xml:365(para) +msgid "Add the physical interface, for example eth0, that is connected to the outside network to this bridge:" +msgstr "" + +#: ./doc/install-guide/section_neutron-per-tenant-routers-with-private-networks.xml:371(para) +msgid "Update the L3 configuration file /etc/neutron/l3_agent.ini:" +msgstr "" + +#: ./doc/install-guide/section_neutron-per-tenant-routers-with-private-networks.xml:378(literal) +msgid "use_namespaces" +msgstr "" + +#: ./doc/install-guide/section_neutron-per-tenant-routers-with-private-networks.xml:377(emphasis) +msgid "Set the option (it is True by default) because TenantA and TenantC have overlapping subnets, and the routers are hosted on one l3 agent network node." +msgstr "" + +#: ./doc/install-guide/section_neutron-per-tenant-routers-with-private-networks.xml:386(para) +msgid "Start the L3 agent" +msgstr "" + +#: ./doc/install-guide/section_neutron-per-tenant-routers-with-private-networks.xml:387(para) +msgid "The Networking L3 agent can be a service of operating system. The command to start the service depends on your operating system. The following command starts the agent directly:" +msgstr "" + +#: ./doc/install-guide/section_neutron-per-tenant-routers-with-private-networks.xml:401(title) ./doc/install-guide/section_neutron-single-flat.xml:475(title) +msgid "Configure logical network" +msgstr "" + +#: ./doc/install-guide/section_neutron-per-tenant-routers-with-private-networks.xml:402(para) +msgid "You can run these commands on the network node." +msgstr "" + +#: ./doc/install-guide/section_neutron-per-tenant-routers-with-private-networks.xml:404(para) +msgid "Ensure that the following environment variables are set. Various clients use these to access the Identity Service." +msgstr "" + +#: ./doc/install-guide/section_neutron-per-tenant-routers-with-private-networks.xml:414(para) ./doc/install-guide/section_neutron-single-flat.xml:488(para) +msgid "Get the tenant ID (Used as $TENANT_ID later):" +msgstr "" + +#: ./doc/install-guide/section_neutron-per-tenant-routers-with-private-networks.xml:428(para) +msgid "Get user information:" +msgstr "" + +#: ./doc/install-guide/section_neutron-per-tenant-routers-with-private-networks.xml:441(para) +msgid "Create the external network and its subnet by admin user:" +msgstr "" + +#: ./doc/install-guide/section_neutron-per-tenant-routers-with-private-networks.xml:479(literal) +msgid "provider:network_type local" +msgstr "" + +#: ./doc/install-guide/section_neutron-per-tenant-routers-with-private-networks.xml:482(literal) +msgid "router:external true" +msgstr "" + +#: ./doc/install-guide/section_neutron-per-tenant-routers-with-private-networks.xml:478(emphasis) +msgid " means that Networking does not have to realize this network through provider network. means that an external network is created where you can create floating IP and router gateway port." +msgstr "" + +#: ./doc/install-guide/section_neutron-per-tenant-routers-with-private-networks.xml:488(para) +msgid "Add an IP on external network to br-ex." +msgstr "" + +#: ./doc/install-guide/section_neutron-per-tenant-routers-with-private-networks.xml:489(para) +msgid "Because br-ex is the external network bridge, add an IP 30.0.0.100/24 to br-ex and ping the floating IP of the VM from our network node." +msgstr "" + +#: ./doc/install-guide/section_neutron-per-tenant-routers-with-private-networks.xml:497(para) +msgid "Serve TenantA." +msgstr "" + +#: ./doc/install-guide/section_neutron-per-tenant-routers-with-private-networks.xml:498(para) +msgid "For TenantA, create a private network, subnet, server, router, and floating IP." +msgstr "" + +#: ./doc/install-guide/section_neutron-per-tenant-routers-with-private-networks.xml:502(para) +msgid "Create a network for TenantA:" +msgstr "" + +#: ./doc/install-guide/section_neutron-per-tenant-routers-with-private-networks.xml:518(para) +msgid "After that, you can use admin user to query the provider network information:" +msgstr "" + +#: ./doc/install-guide/section_neutron-per-tenant-routers-with-private-networks.xml:537(para) +msgid "The network has GRE tunnel ID (for example, provider:segmentation_id) 1." +msgstr "" + +#: ./doc/install-guide/section_neutron-per-tenant-routers-with-private-networks.xml:542(para) +msgid "Create a subnet on the network TenantA-Net:" +msgstr "" + +#: ./doc/install-guide/section_neutron-per-tenant-routers-with-private-networks.xml:564(para) +msgid "Create a server for TenantA:" +msgstr "" + +#: ./doc/install-guide/section_neutron-per-tenant-routers-with-private-networks.xml:576(para) +msgid "It is important to understand that you should not attach the instance to Ext-Net directly. Instead, you must use a floating IP to make it accessible from the external network." +msgstr "" + +#: ./doc/install-guide/section_neutron-per-tenant-routers-with-private-networks.xml:585(para) +msgid "Create and configure a router for TenantA:" +msgstr "" + +#: ./doc/install-guide/section_neutron-per-tenant-routers-with-private-networks.xml:603(para) +msgid "Added interface to router TenantA-R1" +msgstr "" + +#: ./doc/install-guide/section_neutron-per-tenant-routers-with-private-networks.xml:612(para) +msgid "Associate a floating IP for TenantA_VM1." +msgstr "" + +#: ./doc/install-guide/section_neutron-per-tenant-routers-with-private-networks.xml:616(para) +msgid "Create a floating IP:" +msgstr "" + +#: ./doc/install-guide/section_neutron-per-tenant-routers-with-private-networks.xml:633(para) +msgid "Get the port ID of the VM with ID 7c5e6499-7ef7-4e36-8216-62c2941d21ff:" +msgstr "" + +#: ./doc/install-guide/section_neutron-per-tenant-routers-with-private-networks.xml:645(para) +msgid "Associate the floating IP with the VM port:" +msgstr "" + +#: ./doc/install-guide/section_neutron-per-tenant-routers-with-private-networks.xml:663(para) +msgid "Ping the public network from the server of TenantA." +msgstr "" + +#: ./doc/install-guide/section_neutron-per-tenant-routers-with-private-networks.xml:665(para) +msgid "In my environment, 192.168.1.0/24 is my public network connected with my physical router, which also connects to the external network 30.0.0.0/24. With the floating IP and virtual router, you can ping the public network within the server of tenant A:" +msgstr "" + +#: ./doc/install-guide/section_neutron-per-tenant-routers-with-private-networks.xml:683(para) +msgid "Ping floating IP of the TenantA's server:" +msgstr "" + +#: ./doc/install-guide/section_neutron-per-tenant-routers-with-private-networks.xml:696(para) +msgid "Create other servers for TenantA." +msgstr "" + +#: ./doc/install-guide/section_neutron-per-tenant-routers-with-private-networks.xml:697(para) +msgid "You can create more servers for TenantA and add floating IPs for them." +msgstr "" + +#: ./doc/install-guide/section_neutron-per-tenant-routers-with-private-networks.xml:701(para) +msgid "Serve TenantC." +msgstr "" + +#: ./doc/install-guide/section_neutron-per-tenant-routers-with-private-networks.xml:702(para) +msgid "For TenantC, you create two private networks with subnet 10.0.0.0/24 and subnet 10.0.1.0/24, some servers, one router to connect to these two subnets and some floating IPs." +msgstr "" + +#: ./doc/install-guide/section_neutron-per-tenant-routers-with-private-networks.xml:708(para) +msgid "Create networks and subnets for TenantC:" +msgstr "" + +#: ./doc/install-guide/section_neutron-per-tenant-routers-with-private-networks.xml:721(para) +msgid "After that you can use admin user to query the network's provider network information:" +msgstr "" + +#: ./doc/install-guide/section_neutron-per-tenant-routers-with-private-networks.xml:757(para) +msgid "You can see GRE tunnel IDs (such as, provider:segmentation_id) 2 and 3. And also note the network IDs and subnet IDs because you use them to create VMs and router." +msgstr "" + +#: ./doc/install-guide/section_neutron-per-tenant-routers-with-private-networks.xml:764(para) +msgid "Create a server TenantC-VM1 for TenantC on TenantC-Net1." +msgstr "" + +#: ./doc/install-guide/section_neutron-per-tenant-routers-with-private-networks.xml:771(para) +msgid "Create a server TenantC-VM3 for TenantC on TenantC-Net2." +msgstr "" + +#: ./doc/install-guide/section_neutron-per-tenant-routers-with-private-networks.xml:778(para) +msgid "List servers of TenantC." +msgstr "" + +#: ./doc/install-guide/section_neutron-per-tenant-routers-with-private-networks.xml:787(para) +msgid "Note the server IDs because you use them later." +msgstr "" + +#: ./doc/install-guide/section_neutron-per-tenant-routers-with-private-networks.xml:791(para) +msgid "Make sure servers get their IPs." +msgstr "" + +#: ./doc/install-guide/section_neutron-per-tenant-routers-with-private-networks.xml:792(para) +msgid "You can use VNC to log on the VMs to check if they get IPs. If not, you must make sure that the Networking components are running correctly and the GRE tunnels work." +msgstr "" + +#: ./doc/install-guide/section_neutron-per-tenant-routers-with-private-networks.xml:799(para) +msgid "Create and configure a router for TenantC:" +msgstr "" + +#: ./doc/install-guide/section_neutron-per-tenant-routers-with-private-networks.xml:814(para) +msgid "Checkpoint: ping from within TenantC's servers." +msgstr "" + +#: ./doc/install-guide/section_neutron-per-tenant-routers-with-private-networks.xml:816(para) +msgid "Because a router connects to two subnets, the VMs on these subnets can ping each other. And because the gateway for the router is set, TenantC's servers can ping external network IPs, such as 192.168.1.1, 30.0.0.1, and so on." +msgstr "" + +#: ./doc/install-guide/section_neutron-per-tenant-routers-with-private-networks.xml:824(para) ./doc/install-guide/section_neutron-per-tenant-routers-with-private-networks.xml:835(para) +msgid "Associate floating IPs for TenantC's servers." +msgstr "" + +#: ./doc/install-guide/section_neutron-per-tenant-routers-with-private-networks.xml:826(para) +msgid "Because a router connects to two subnets, the VMs on these subnets can ping each other. And because the gateway interface for the router is set, TenantC's servers can ping external network IPs, such as 192.168.1.1, 30.0.0.1, and so on." +msgstr "" + +#: ./doc/install-guide/section_neutron-per-tenant-routers-with-private-networks.xml:837(para) +msgid "You can use similar commands to the ones used in the section for TenantA." +msgstr "" + +#: ./doc/install-guide/section_neutron-per-tenant-routers-with-private-networks.xml:845(title) +msgid "Use case: per-tenant routers with private networks" +msgstr "" + +#: ./doc/install-guide/section_neutron-per-tenant-routers-with-private-networks.xml:847(para) +msgid "This use case represents a more advanced router scenario in which each tenant gets at least one router, and potentially has access to the Networking API to create additional routers. The tenant can create their own networks, potentially uplinking those networks to a router. This model enables tenant-defined, multi-tier applications, with each tier being a separate network behind the router. Because there are multiple routers, tenant subnets can overlap without conflicting, because access to external networks all happens through SNAT or floating IPs. Each router uplink and floating IP is allocated from the external network subnet." +msgstr "" + +#: ./doc/install-guide/ch_horizon.xml:6(title) +msgid "Add the dashboard" +msgstr "" + +#: ./doc/install-guide/ch_horizon.xml:7(para) +msgid "The OpenStack dashboard, also known as Horizon, is a Web interface that enables cloud administrators and users to manage various OpenStack resources and services." +msgstr "" + +#: ./doc/install-guide/ch_horizon.xml:12(para) +msgid "The dashboard enables web-based interactions with the OpenStack Compute cloud controller through the OpenStack APIs." +msgstr "" + +#: ./doc/install-guide/ch_horizon.xml:15(para) +msgid "These instructions show an example deployment configured with an Apache web server." +msgstr "" + +#: ./doc/install-guide/ch_horizon.xml:17(para) +msgid "After you install and configure the dashboard, you can complete the following tasks:" +msgstr "" + +#: ./doc/install-guide/ch_horizon.xml:22(para) +msgid "Customize your dashboard. See section Customize the dashboard in the OpenStack Cloud Administrator Guide." +msgstr "" + +#: ./doc/install-guide/ch_horizon.xml:30(para) +msgid "Set up session storage for the dashboard. See ." +msgstr "" + +#: ./doc/install-guide/section_heat-verify.xml:6(title) +msgid "Verify the Orchestration service installation" +msgstr "" + +#: ./doc/install-guide/section_heat-verify.xml:8(para) +msgid "To verify that the Orchestration service is installed and configured correctly, make sure that your credentials are set up correctly in the openrc.sh file. Source the file, as follows:" +msgstr "" + +#: ./doc/install-guide/section_heat-verify.xml:14(para) +msgid "Next, create some stacks by using the samples." +msgstr "" + +#: ./doc/install-guide/ch_ceilometer.xml:6(title) +msgid "Add the Telemetry service" +msgstr "" + +#: ./doc/install-guide/ch_ceilometer.xml:8(para) +msgid "The OpenStack Telemetry service provides a framework for monitoring and metering the OpenStack cloud. It is also known as the Ceilometer project." +msgstr "" + +#: ./doc/install-guide/ch_keystone.xml:6(title) +msgid "Configure the Identity Service" +msgstr "" + +#: ./doc/install-guide/ch_heat.xml:6(title) +msgid "Add the Orchestration service" +msgstr "" + +#: ./doc/install-guide/ch_heat.xml:7(para) +msgid "Use the OpenStack Orchestration service to create cloud resources using a template language called HOT. The integrated project name is Heat." +msgstr "" + +#. When image changes, this message will be marked fuzzy or untranslated for you. +#. It doesn't matter what you translate it to: it's not used at all. +#: ./doc/install-guide/section_debconf-rabbitqm.xml:15(None) +msgid "@@image: 'figures/debconf-screenshots/rabbitmq-host.png'; md5=5353ad857884a2d31847cf82efbdc6b6" +msgstr "" + +#. When image changes, this message will be marked fuzzy or untranslated for you. +#. It doesn't matter what you translate it to: it's not used at all. +#: ./doc/install-guide/section_debconf-rabbitqm.xml:22(None) +msgid "@@image: 'figures/debconf-screenshots/rabbitmq-user.png'; md5=33a3c1182e79ed65f1b1b63f2156792c" +msgstr "" + +#. When image changes, this message will be marked fuzzy or untranslated for you. +#. It doesn't matter what you translate it to: it's not used at all. +#: ./doc/install-guide/section_debconf-rabbitqm.xml:29(None) +msgid "@@image: 'figures/debconf-screenshots/rabbitmq-password.png'; md5=6385185200d20e96b6316ae15ae1255d" +msgstr "" + +#: ./doc/install-guide/section_debconf-rabbitqm.xml:6(title) +msgid "RabbitMQ credentials parameters" +msgstr "" + +#: ./doc/install-guide/section_debconf-rabbitqm.xml:7(para) +msgid "For every package that must connect to a Messaging Server, the Debian package enables you to configure the IP address for that server and the user name and password that is used to connect. The following example shows configuration with the ceilometer-common package:" +msgstr "" + +#: ./doc/install-guide/section_debconf-rabbitqm.xml:33(para) +msgid "These debconf screens appear in: ceilometer-common, cinder-common, glance-common, heat-common, neutron-common and nova-common." +msgstr "" + +#. When image changes, this message will be marked fuzzy or untranslated for you. +#. It doesn't matter what you translate it to: it's not used at all. +#: ./doc/install-guide/section_neutron-provider-router-with-private_networks.xml:16(None) ./doc/install-guide/ch_overview.xml:101(None) +msgid "@@image: '../common/figures/Neutron-PhysNet-Diagram.png'; md5=ac17dba8837f9d7ba714a692c60e68ab" +msgstr "" + +#. When image changes, this message will be marked fuzzy or untranslated for you. +#. It doesn't matter what you translate it to: it's not used at all. +#: ./doc/install-guide/section_neutron-provider-router-with-private_networks.xml:660(None) +msgid "@@image: '../common/figures/UseCase-SingleRouter.png'; md5=63d21d52d32ed7fa1c1dad1a1fd88eb5" +msgstr "" + +#: ./doc/install-guide/section_neutron-provider-router-with-private_networks.xml:6(title) +msgid "Provider router with private networks" +msgstr "" + +#: ./doc/install-guide/section_neutron-provider-router-with-private_networks.xml:7(para) +msgid "This section describes how to install the OpenStack Networking service and its components for a single router use case: a provider router with private networks." +msgstr "" + +#: ./doc/install-guide/section_neutron-provider-router-with-private_networks.xml:10(para) +msgid "This figure shows the set up:" +msgstr "" + +#: ./doc/install-guide/section_neutron-provider-router-with-private_networks.xml:21(para) +msgid "Because you run the DHCP agent and L3 agent on one node, you must set use_namespaces to True (which is the default) in the configuration files for both agents." +msgstr "" + +#: ./doc/install-guide/section_neutron-provider-router-with-private_networks.xml:26(para) +msgid "The configuration includes these nodes:" +msgstr "" + +#: ./doc/install-guide/section_neutron-provider-router-with-private_networks.xml:28(caption) +msgid "Nodes for use case" +msgstr "" + +#: ./doc/install-guide/section_neutron-provider-router-with-private_networks.xml:37(para) ./doc/install-guide/section_neutron-provider-router-with-private_networks.xml:93(title) +msgid "Controller" +msgstr "" + +#: ./doc/install-guide/section_neutron-provider-router-with-private_networks.xml:38(para) +msgid "Runs the Networking service, Identity Service, and all Compute services that are required to deploy a VM." +msgstr "" + +#: ./doc/install-guide/section_neutron-provider-router-with-private_networks.xml:41(para) +msgid "The service must have at least two network interfaces. The first should be connected to the Management Network to communicate with the compute and network nodes. The second interface should be connected to the API/public network." +msgstr "" + +#: ./doc/install-guide/section_neutron-provider-router-with-private_networks.xml:49(para) +msgid "Compute" +msgstr "" + +#: ./doc/install-guide/section_neutron-provider-router-with-private_networks.xml:50(para) +msgid "Runs Compute and the Networking L2 agent." +msgstr "" + +#: ./doc/install-guide/section_neutron-provider-router-with-private_networks.xml:52(para) +msgid "This node does not have access the public network." +msgstr "" + +#: ./doc/install-guide/section_neutron-provider-router-with-private_networks.xml:54(para) +msgid "The node must have a network interface that communicates with the controller node through the management network. The VM receives its IP address from the DHCP agent on this network." +msgstr "" + +#: ./doc/install-guide/section_neutron-provider-router-with-private_networks.xml:61(para) +msgid "Network" +msgstr "" + +#: ./doc/install-guide/section_neutron-provider-router-with-private_networks.xml:62(para) +msgid "Runs Networking L2 agent, DHCP agent, and L3 agent." +msgstr "" + +#: ./doc/install-guide/section_neutron-provider-router-with-private_networks.xml:64(para) +msgid "This node has access to the public network. The DHCP agent allocates IP addresses to the VMs on the network. The L3 agent performs NAT and enables the VMs to access the public network." +msgstr "" + +#: ./doc/install-guide/section_neutron-provider-router-with-private_networks.xml:71(para) +msgid "A network interface that communicates with the controller node through the management network" +msgstr "" + +#: ./doc/install-guide/section_neutron-provider-router-with-private_networks.xml:77(para) +msgid "A network interface on the data network that manages VM traffic" +msgstr "" + +#: ./doc/install-guide/section_neutron-provider-router-with-private_networks.xml:82(para) +msgid "A network interface that connects to the external gateway on the network" +msgstr "" + +#: ./doc/install-guide/section_neutron-provider-router-with-private_networks.xml:69(para) +msgid "The node must have:" +msgstr "" + +#: ./doc/install-guide/section_neutron-provider-router-with-private_networks.xml:95(title) +msgid "To install and configure the controller node" +msgstr "" + +#: ./doc/install-guide/section_neutron-provider-router-with-private_networks.xml:98(para) ./doc/install-guide/section_nova-compute.xml:56(para) +msgid "Run this command:" +msgstr "" + +#: ./doc/install-guide/section_neutron-provider-router-with-private_networks.xml:104(para) +msgid "Configure Networking services:" +msgstr "" + +#: ./doc/install-guide/section_neutron-provider-router-with-private_networks.xml:107(para) +msgid "Edit the /etc/neutron/neutron.conf file and add these lines:" +msgstr "" + +#: ./doc/install-guide/section_neutron-provider-router-with-private_networks.xml:119(para) ./doc/install-guide/section_neutron-provider-router-with-private_networks.xml:338(para) +msgid "Edit the /etc/neutron/plugins/openvswitch/ovs_neutron_plugin.ini file and add these lines:" +msgstr "" + +#: ./doc/install-guide/section_neutron-provider-router-with-private_networks.xml:127(para) +msgid "Edit the /etc/neutron/api-paste.ini file and add these lines:" +msgstr "" + +#: ./doc/install-guide/section_neutron-provider-router-with-private_networks.xml:137(para) +msgid "Start the services:" +msgstr "" + +#: ./doc/install-guide/section_neutron-provider-router-with-private_networks.xml:144(title) +msgid "Network node" +msgstr "" + +#: ./doc/install-guide/section_neutron-provider-router-with-private_networks.xml:146(title) +msgid "Install and configure the network node" +msgstr "" + +#. FIXME Review Fedora instructions +#: ./doc/install-guide/section_neutron-provider-router-with-private_networks.xml:148(para) ./doc/install-guide/section_neutron-provider-router-with-private_networks.xml:287(para) +msgid "Install the packages:" +msgstr "" + +#: ./doc/install-guide/section_neutron-provider-router-with-private_networks.xml:157(para) +msgid "Start Open vSwitch and configure it to start when the system boots:" +msgstr "" + +#: ./doc/install-guide/section_neutron-provider-router-with-private_networks.xml:173(para) +msgid "Update the OpenStack Networking /etc/neutron/neutron.conf configuration file:" +msgstr "" + +#: ./doc/install-guide/section_neutron-provider-router-with-private_networks.xml:194(para) +msgid "Update the plug-in /etc/neutron/plugins/openvswitch/ovs_neutron_plugin.ini configuration file:" +msgstr "" + +#: ./doc/install-guide/section_neutron-provider-router-with-private_networks.xml:203(para) ./doc/install-guide/section_neutron-provider-router-with-private_networks.xml:308(para) +msgid "All VM communication between the nodes occurs through the br-eth1 bridge." +msgstr "" + +#: ./doc/install-guide/section_neutron-provider-router-with-private_networks.xml:206(para) ./doc/install-guide/section_neutron-provider-router-with-private_networks.xml:311(para) +msgid "Create the br-eth1 network bridge:" +msgstr "" + +#: ./doc/install-guide/section_neutron-provider-router-with-private_networks.xml:212(para) +msgid "Create the external network bridge to the Open vSwitch:" +msgstr "" + +#: ./doc/install-guide/section_neutron-provider-router-with-private_networks.xml:218(para) +msgid "Edit the /etc/neutron/l3_agent.ini file and add these lines:" +msgstr "" + +#: ./doc/install-guide/section_neutron-provider-router-with-private_networks.xml:230(para) +msgid "Edit the /etc/neutron/api-paste.ini file and add these lines:" +msgstr "" + +#: ./doc/install-guide/section_neutron-provider-router-with-private_networks.xml:240(para) +msgid "Edit the /etc/neutron/dhcp_agent.ini file and add this line:" +msgstr "" + +#: ./doc/install-guide/section_neutron-provider-router-with-private_networks.xml:246(para) +msgid "Restart networking services:" +msgstr "" + +#: ./doc/install-guide/section_neutron-provider-router-with-private_networks.xml:252(para) ./doc/install-guide/section_neutron-provider-router-with-private_networks.xml:352(para) +msgid "Start and permanently enable networking services:" +msgstr "" + +#. FIXME: Required on Debian/Ubuntu? +#: ./doc/install-guide/section_neutron-provider-router-with-private_networks.xml:269(para) +msgid "Enable the neutron-ovs-cleanup service. This service starts on boot and ensures that Networking has full control over the creation and management of tap devices." +msgstr "" + +#: ./doc/install-guide/section_neutron-provider-router-with-private_networks.xml:284(title) +msgid "Install and configure the compute node" +msgstr "" + +#: ./doc/install-guide/section_neutron-provider-router-with-private_networks.xml:293(para) +msgid "Start the OpenvSwitch service and configure it to start when the system boots:" +msgstr "" + +#: ./doc/install-guide/section_neutron-provider-router-with-private_networks.xml:304(para) +msgid "Create the integration bridge:" +msgstr "" + +#: ./doc/install-guide/section_neutron-provider-router-with-private_networks.xml:317(para) +msgid "Edit the OpenStack Networking /etc/neutron/neutron.conf configuration file and add this line:" +msgstr "" + +#: ./doc/install-guide/section_neutron-provider-router-with-private_networks.xml:347(para) +msgid "Restart the OpenvSwitch Neutron plug-in agent:" +msgstr "" + +#: ./doc/install-guide/section_neutron-provider-router-with-private_networks.xml:363(title) +msgid "Logical network configuration" +msgstr "" + +#: ./doc/install-guide/section_neutron-provider-router-with-private_networks.xml:365(para) +msgid "Run these commands on the network node." +msgstr "" + +#: ./doc/install-guide/section_neutron-provider-router-with-private_networks.xml:366(para) ./doc/install-guide/section_neutron-single-flat.xml:478(para) +msgid "Ensure that the following environment variables are set. Various clients use these variables to access the Identity Service." +msgstr "" + +#: ./doc/install-guide/section_neutron-provider-router-with-private_networks.xml:372(para) +msgid "Create an adminrc file that contains these lines:" +msgstr "" + +#: ./doc/install-guide/section_neutron-provider-router-with-private_networks.xml:381(para) +msgid "Export the environment variables in the adminrc file:" +msgstr "" + +#: ./doc/install-guide/section_neutron-provider-router-with-private_networks.xml:386(para) +msgid "The admin tenant can define resources that other tenants can use but cannot modify. These resources are a provider network and its associated router." +msgstr "" + +#: ./doc/install-guide/section_neutron-provider-router-with-private_networks.xml:390(para) +msgid "The admin user creates a network and subnet on behalf of tenant_A." +msgstr "" + +#: ./doc/install-guide/section_neutron-provider-router-with-private_networks.xml:392(para) +msgid "A tenant_A user can also complete these steps." +msgstr "" + +#: ./doc/install-guide/section_neutron-provider-router-with-private_networks.xml:395(title) +msgid "Configure internal networking" +msgstr "" + +#: ./doc/install-guide/section_neutron-provider-router-with-private_networks.xml:397(para) +msgid "Get the tenant_A tenant ID:" +msgstr "" + +#: ./doc/install-guide/section_neutron-provider-router-with-private_networks.xml:402(para) +msgid "Create the net1 internal network for the tenant_A tenant:" +msgstr "" + +#: ./doc/install-guide/section_neutron-provider-router-with-private_networks.xml:423(para) +msgid "Create a subnet on the net1 network and store its ID in a variable:" +msgstr "" + +#: ./doc/install-guide/section_neutron-provider-router-with-private_networks.xml:443(replaceable) +msgid "c395cb5d-ba03-41ee-8a12-7e792d51a167" +msgstr "" + +#: ./doc/install-guide/section_neutron-provider-router-with-private_networks.xml:445(para) ./doc/install-guide/section_neutron-provider-router-with-private_networks.xml:473(para) +msgid "The id value will be different on your system." +msgstr "" + +#: ./doc/install-guide/section_neutron-provider-router-with-private_networks.xml:450(para) +msgid "A user with the admin role in the admin tenant must complete these steps." +msgstr "" + +#: ./doc/install-guide/section_neutron-provider-router-with-private_networks.xml:454(title) +msgid "Configure the router and external networking" +msgstr "" + +#: ./doc/install-guide/section_neutron-provider-router-with-private_networks.xml:457(para) +msgid "Create a router1 router and store its ID in the ROUTER_ID variable:" +msgstr "" + +#: ./doc/install-guide/section_neutron-provider-router-with-private_networks.xml:471(replaceable) +msgid "685f64e7-a020-4fdf-a8ad-e41194ae124b" +msgstr "" + +#: ./doc/install-guide/section_neutron-provider-router-with-private_networks.xml:477(para) +msgid "The --tenant-id parameter is not specified, so this router is assigned to the admin tenant." +msgstr "" + +#: ./doc/install-guide/section_neutron-provider-router-with-private_networks.xml:484(para) +msgid "Add an interface to the router1 router and attach it to the subnet from net1:" +msgstr "" + +#: ./doc/install-guide/section_neutron-provider-router-with-private_networks.xml:491(para) +msgid "You can repeat this step to add interfaces for networks that belong to other tenants." +msgstr "" + +#: ./doc/install-guide/section_neutron-provider-router-with-private_networks.xml:497(para) +msgid "Create the ext_net external network and store its ID in a the EXTERNAL_NETWORK_ID variable:" +msgstr "" + +#: ./doc/install-guide/section_neutron-provider-router-with-private_networks.xml:519(replaceable) +msgid "8858732b-0400-41f6-8e5c-25590e67ffeb" +msgstr "" + +#: ./doc/install-guide/section_neutron-provider-router-with-private_networks.xml:522(para) +msgid "Create the subnet for floating IPs." +msgstr "" + +#: ./doc/install-guide/section_neutron-provider-router-with-private_networks.xml:524(para) +msgid "The DHCP service is disabled for this subnet." +msgstr "" + +#: ./doc/install-guide/section_neutron-provider-router-with-private_networks.xml:547(para) +msgid "Set the gateway for the router to the external network:" +msgstr "" + +#: ./doc/install-guide/section_neutron-provider-router-with-private_networks.xml:553(para) +msgid "A user from tenant_A completes these steps, so the credentials in the environment variables are different than those in the previous procedure." +msgstr "" + +#: ./doc/install-guide/section_neutron-provider-router-with-private_networks.xml:557(title) +msgid "Allocate floating IP addresses" +msgstr "" + +#: ./doc/install-guide/section_neutron-provider-router-with-private_networks.xml:559(para) +msgid "You can associate a floating IP address with a VM after it starts. Store the port ID that was allocated for the VM in the PORT_ID variable:" +msgstr "" + +#: ./doc/install-guide/section_neutron-provider-router-with-private_networks.xml:569(replaceable) +msgid "1cdc671d-a296-4476-9a75-f9ca1d92fd26" +msgstr "" + +#: ./doc/install-guide/section_neutron-provider-router-with-private_networks.xml:575(replaceable) +msgid "9aa47099-b87b-488c-8c1d-32f993626a30" +msgstr "" + +#: ./doc/install-guide/section_neutron-provider-router-with-private_networks.xml:578(para) +msgid "Allocate a floating IP and store its ID in the FLOATING_ID variable:" +msgstr "" + +#: ./doc/install-guide/section_neutron-provider-router-with-private_networks.xml:593(replaceable) +msgid "7.7.7.131" +msgstr "" + +#: ./doc/install-guide/section_neutron-provider-router-with-private_networks.xml:596(para) +msgid "Associate the floating IP with the port for the VM:" +msgstr "" + +#: ./doc/install-guide/section_neutron-provider-router-with-private_networks.xml:602(para) +msgid "Show the floating IP:" +msgstr "" + +#: ./doc/install-guide/section_neutron-provider-router-with-private_networks.xml:617(para) +msgid "Test the floating IP:" +msgstr "" + +#: ./doc/install-guide/section_neutron-provider-router-with-private_networks.xml:626(title) +msgid "Use case: provider router with private networks" +msgstr "" + +#: ./doc/install-guide/section_neutron-provider-router-with-private_networks.xml:627(para) +msgid "This use case provides each tenant with one or more private networks that connect to the outside world through an OpenStack Networking router. When each tenant gets exactly one network, this architecture maps to the same logical topology as the VlanManager in Compute (although of course, Networking does not require VLANs). Using the Networking API, the tenant can only see a network for each private network assigned to that tenant. The router object in the API is created and owned by the cloud administrator." +msgstr "" + +#: ./doc/install-guide/section_neutron-provider-router-with-private_networks.xml:637(para) +msgid "This model supports assigning public addresses to VMs by using floating IPs; the router maps public addresses from the external network to fixed IPs on private networks. Hosts without floating IPs can still create outbound connections to the external network because the provider router performs SNAT to the router's external IP. The IP address of the physical router is used as the gateway_ip of the external network subnet, so the provider has a default router for Internet traffic." +msgstr "" + +#: ./doc/install-guide/section_neutron-provider-router-with-private_networks.xml:648(para) +msgid "The router provides L3 connectivity among private networks. Tenants can reach instances for other tenants unless you use additional filtering, such as, security groups). With a single router, tenant networks cannot use overlapping IPs. To resolve this issue, the administrator can create private networks on behalf of the tenants." +msgstr "" + +#: ./doc/install-guide/ch_nova.xml:7(title) +msgid "Configure Compute services" +msgstr "" + +#: ./doc/install-guide/section_ceilometer-cinder.xml:7(title) +msgid "Add the Block Storage Service agent for the Telemetry service" +msgstr "" + +#: ./doc/install-guide/section_ceilometer-cinder.xml:11(para) +msgid "To retrieve volume samples, you must configure the Block Storage Service to send notifications to the bus." +msgstr "" + +#: ./doc/install-guide/section_ceilometer-cinder.xml:14(para) +msgid "Edit /etc/cinder/cinder.conf and add in the [DEFAULT] section:" +msgstr "" + +#: ./doc/install-guide/section_ceilometer-cinder.xml:19(para) ./doc/install-guide/section_ceilometer-glance.xml:20(para) ./doc/install-guide/section_heat-install.xml:94(para) +msgid "Run the following commands:" +msgstr "" + +#: ./doc/install-guide/section_ceilometer-cinder.xml:25(para) +msgid "Restart the Block Storage services with their new settings:" +msgstr "" + +#: ./doc/install-guide/section_nova-network.xml:5(title) +msgid "Configure networking" +msgstr "" + +#: ./doc/install-guide/section_nova-network.xml:6(para) +msgid "Configuring networking in OpenStack can be a bewildering experience. The following example shows the simplest production-ready configuration that is available: the legacy networking in OpenStack Compute, with a flat network, that takes care of DHCP." +msgstr "" + +#: ./doc/install-guide/section_nova-network.xml:11(para) +msgid "This set up uses multi-host functionality. Networking is configured to be highly available by distributing networking functionality across multiple hosts. As a result, no single network controller acts as a single point of failure. This process configures each compute node for networking." +msgstr "" + +#: ./doc/install-guide/section_nova-network.xml:17(para) +msgid "Choose one of these options to configure networking in OpenStack:" +msgstr "" + +#: ./doc/install-guide/section_nova-network.xml:20(para) +msgid "Legacy networking in OpenStack Compute, which is described here." +msgstr "" + +#: ./doc/install-guide/section_nova-network.xml:24(para) +msgid "The full software-defined networking stack. See ." +msgstr "" + +#: ./doc/install-guide/section_nova-network.xml:31(para) +msgid "Install the appropriate packages for compute networking on the compute node only. These packages are not required on the controller node." +msgstr "" + +#: ./doc/install-guide/section_nova-network.xml:34(para) +msgid "So that the nova-network service can forward metadata requests on each compute node, each compute node must install the nova-api-metadata service, as follows:" +msgstr "" + +#: ./doc/install-guide/section_nova-network.xml:44(para) +msgid "Edit the nova.conf file to define the networking mode:" +msgstr "" + +#: ./doc/install-guide/section_nova-network.xml:81(para) +msgid "Provide a local metadata service that is reachable from instances on this compute node. Perform this step only on compute nodes that do not run the nova-api service." +msgstr "" + +#: ./doc/install-guide/section_nova-network.xml:90(para) +msgid "Restart the network service:" +msgstr "" + +#: ./doc/install-guide/section_nova-network.xml:92(para) +msgid "Start the network service and configure it to start when the system boots:" +msgstr "" + +#: ./doc/install-guide/section_nova-network.xml:99(para) +msgid "Create a network that virtual machines can use. Do this once for the entire installation and not on each compute node. Run the command on the controller:" +msgstr "" + +#: ./doc/install-guide/app_reserved_uids.xml:6(title) ./doc/install-guide/app_reserved_uids.xml:24(caption) +msgid "Reserved user IDs" +msgstr "" + +#: ./doc/install-guide/app_reserved_uids.xml:8(para) +msgid "In OpenStack, certain user IDs are reserved and used to run specific OpenStack services and own specific OpenStack files. These users are set up according to the distribution packages. The following table gives an overview." +msgstr "" + +#: ./doc/install-guide/app_reserved_uids.xml:16(para) +msgid "Some OpenStack packages generate and assign user IDs automatically during package installation. In these cases, the user ID value is not important. The existence of the user ID is what matters." +msgstr "" + +#: ./doc/install-guide/app_reserved_uids.xml:27(th) +msgid "Name" +msgstr "" + +#: ./doc/install-guide/app_reserved_uids.xml:35(td) +msgid "ceilometer" +msgstr "" + +#: ./doc/install-guide/app_reserved_uids.xml:36(td) +msgid "openstack-ceilometer" +msgstr "" + +#: ./doc/install-guide/app_reserved_uids.xml:37(td) +msgid "OpenStack Ceilometer Daemons" +msgstr "" + +#: ./doc/install-guide/app_reserved_uids.xml:38(td) +msgid "166" +msgstr "" + +#: ./doc/install-guide/app_reserved_uids.xml:39(td) ./doc/install-guide/app_reserved_uids.xml:46(td) ./doc/install-guide/app_reserved_uids.xml:53(td) ./doc/install-guide/app_reserved_uids.xml:60(td) ./doc/install-guide/app_reserved_uids.xml:67(td) ./doc/install-guide/app_reserved_uids.xml:74(td) ./doc/install-guide/app_reserved_uids.xml:82(td) ./doc/install-guide/app_reserved_uids.xml:89(td) +msgid "Assigned during package installation" +msgstr "" + +#: ./doc/install-guide/app_reserved_uids.xml:42(td) +msgid "cinder" +msgstr "" + +#: ./doc/install-guide/app_reserved_uids.xml:43(td) +msgid "openstack-cinder" +msgstr "" + +#: ./doc/install-guide/app_reserved_uids.xml:44(td) +msgid "OpenStack Cinder Daemons" +msgstr "" + +#: ./doc/install-guide/app_reserved_uids.xml:45(td) +msgid "165" +msgstr "" + +#: ./doc/install-guide/app_reserved_uids.xml:49(td) +msgid "glance" +msgstr "" + +#: ./doc/install-guide/app_reserved_uids.xml:50(td) +msgid "openstack-glance" +msgstr "" + +#: ./doc/install-guide/app_reserved_uids.xml:51(td) +msgid "OpenStack Glance Daemons" +msgstr "" + +#: ./doc/install-guide/app_reserved_uids.xml:52(td) +msgid "161" +msgstr "" + +#: ./doc/install-guide/app_reserved_uids.xml:56(td) +msgid "heat" +msgstr "" + +#: ./doc/install-guide/app_reserved_uids.xml:57(td) +msgid "openstack-heat" +msgstr "" + +#: ./doc/install-guide/app_reserved_uids.xml:58(td) +msgid "OpenStack Heat Daemons" +msgstr "" + +#: ./doc/install-guide/app_reserved_uids.xml:59(td) +msgid "187" +msgstr "" + +#: ./doc/install-guide/app_reserved_uids.xml:63(td) +msgid "keystone" +msgstr "" + +#: ./doc/install-guide/app_reserved_uids.xml:64(td) +msgid "openstack-keystone" +msgstr "" + +#: ./doc/install-guide/app_reserved_uids.xml:65(td) +msgid "OpenStack Keystone Daemons" +msgstr "" + +#: ./doc/install-guide/app_reserved_uids.xml:66(td) +msgid "163" +msgstr "" + +#: ./doc/install-guide/app_reserved_uids.xml:70(td) +msgid "neutron" +msgstr "" + +#: ./doc/install-guide/app_reserved_uids.xml:71(td) +msgid "openstack-neutron" +msgstr "" + +#: ./doc/install-guide/app_reserved_uids.xml:72(td) +msgid "OpenStack Neutron Daemons" +msgstr "" + +#: ./doc/install-guide/app_reserved_uids.xml:73(td) +msgid "164" +msgstr "" + +#: ./doc/install-guide/app_reserved_uids.xml:77(td) +msgid "nova" +msgstr "" + +#: ./doc/install-guide/app_reserved_uids.xml:78(td) +msgid "openstack-nova" +msgstr "" + +#: ./doc/install-guide/app_reserved_uids.xml:79(td) +msgid "OpenStack Nova Daemons" +msgstr "" + +#: ./doc/install-guide/app_reserved_uids.xml:80(td) +msgid "162" +msgstr "" + +#: ./doc/install-guide/app_reserved_uids.xml:81(td) +msgid "96" +msgstr "" + +#: ./doc/install-guide/app_reserved_uids.xml:85(td) +msgid "swift" +msgstr "" + +#: ./doc/install-guide/app_reserved_uids.xml:86(td) +msgid "openstack-swift" +msgstr "" + +#: ./doc/install-guide/app_reserved_uids.xml:87(td) +msgid "OpenStack Swift Daemons" +msgstr "" + +#: ./doc/install-guide/app_reserved_uids.xml:88(td) +msgid "160" +msgstr "" + +#: ./doc/install-guide/app_reserved_uids.xml:93(para) +msgid "Each user belongs to a user group with the same name as the user." +msgstr "" + +#: ./doc/install-guide/ch_preface.xml:10(title) +msgid "Preface" +msgstr "" + +#: ./doc/install-guide/section_ceilometer-glance.xml:6(title) +msgid "Add the Image Service agent for the Telemetry service" +msgstr "" + +#: ./doc/install-guide/section_ceilometer-glance.xml:9(para) +msgid "To retrieve image samples, you must configure the Image Service to send notifications to the bus." +msgstr "" + +#: ./doc/install-guide/section_ceilometer-glance.xml:12(para) +msgid "Edit /etc/glance/glance-api.conf and modify the [DEFAULT] section:" +msgstr "" + +#: ./doc/install-guide/section_ceilometer-glance.xml:31(para) +msgid "Restart the Image services with their new settings:" +msgstr "" + +#: ./doc/install-guide/section_debconf-concepts.xml:7(title) +msgid "debconf concepts" +msgstr "" + +#: ./doc/install-guide/section_debconf-concepts.xml:8(para) +msgid "This chapter explains how to use the Debian debconf and dbconfig-common packages to configure OpenStack services. These packages enable users to perform configuration tasks. When users install OpenStack packages, debconf prompts the user for responses, which seed the contents of configuration files associated with that package. After package installation, users can update the configuration of a package by using the program." +msgstr "" + +#: ./doc/install-guide/section_debconf-concepts.xml:18(para) +msgid "If you are familiar with these packages and pre-seeding, you can proceed to ." +msgstr "" + +#: ./doc/install-guide/section_debconf-concepts.xml:21(title) +msgid "The Debian packages" +msgstr "" + +#: ./doc/install-guide/section_debconf-concepts.xml:22(para) +msgid "The rules described here are from the Debian Policy Manual. If any rule described in this chapter is not respected, you have found a serious bug that must be fixed." +msgstr "" + +#: ./doc/install-guide/section_debconf-concepts.xml:27(para) +msgid "When you install or upgrade a Debian package, all configuration file values are preserved. Using the debconf database as a registry is considered a bug in Debian. If you edit something in any OpenStack configuration file, the debconf package reads that value when it prepares to prompt the user. For example, to change the log in name for the RabbitMQ messaging queue for a service, you can edit its value in the corresponding configuration file." +msgstr "" + +#: ./doc/install-guide/section_debconf-concepts.xml:36(para) +msgid "To opt out of using the debconf package, run the command and select non-interactive mode:" +msgstr "" + +#: ./doc/install-guide/section_debconf-concepts.xml:41(para) +msgid "Then, debconf does not prompt you." +msgstr "" + +#: ./doc/install-guide/section_debconf-concepts.xml:43(para) +msgid "Another way to disable the debconf package is to prefix the command with DEBIAN_FRONTEND=noninteractive, as follows:" +msgstr "" + +#: ./doc/install-guide/section_debconf-concepts.xml:49(para) +msgid "If you configure a package with debconf incorrectly, you can re-configure it, as follows:" +msgstr "" + +#: ./doc/install-guide/section_debconf-concepts.xml:52(replaceable) +msgid "PACKAGE-NAME" +msgstr "" + +#: ./doc/install-guide/section_debconf-concepts.xml:53(para) +msgid "This calls the post-installation script for the PACKAGE-NAME package after the user responds to all prompts. If you cannot install a Debian package in a non-interactive way, you have found a release-critical bug in Debian. Report it to the Debian bug tracking system." +msgstr "" + +#: ./doc/install-guide/section_debconf-concepts.xml:58(para) +msgid "Generally, the -common packages install the configuration files. For example, the glance-common package installs the glance-api.conf and glance-registry.conf files. So, for the Image Service, you must re-configure the glance-common package. The same applies for cinder-common, nova-common, and heat-common packages." +msgstr "" + +#: ./doc/install-guide/section_debconf-concepts.xml:68(para) +msgid "In debconf, the higher the priority for a screen, the greater the chance that the user sees that screen. If a debconf screen has medium priority and you configure the Debian system to show only critical prompts, which is the default in Debian, the user does not see that debconf screen. Instead, the default for the related package is used. In the Debian OpenStack packages, a number of debconf screens are set with medium priority. Consequently, if you want to respond to all debconf screens from the Debian OpenStack packages, you must run the following command and select the medium priority before you install any packages:" +msgstr "" + +#: ./doc/install-guide/section_debconf-concepts.xml:87(para) +msgid "The packages do not require pre-depends. If dbconfig-common is already installed on the system, the user sees all prompts. However, you cannot define the order in which the debconf screens appear. The user must make sense of it even if the prompts appear in an illogical order." +msgstr "" + +#: ./doc/install-guide/section_ceilometer-swift.xml:6(title) +msgid "Add the Object Storage agent for the Telemetry service" +msgstr "" + +#: ./doc/install-guide/section_ceilometer-swift.xml:9(para) +msgid "To retrieve object store statistics, the Telemetry service needs access to Object Storage with the ResellerAdmin role. Give this role to your os_username user for the os_tenant_name tenant:" +msgstr "" + +#: ./doc/install-guide/section_ceilometer-swift.xml:23(replaceable) +msgid "462fa46c13fd4798a95a3bfbe27b5e54" +msgstr "" + +#: ./doc/install-guide/section_ceilometer-swift.xml:26(para) +msgid "You must also add the Telemetry middleware to Object Storage to handle incoming and outgoing traffic. Add these lines to the /etc/swift/proxy-server.conf file:" +msgstr "" + +#: ./doc/install-guide/section_ceilometer-swift.xml:35(para) +msgid "Add ceilometer to the pipeline parameter of that same file:" +msgstr "" + +#: ./doc/install-guide/section_ceilometer-swift.xml:41(para) ./doc/install-guide/section_heat-install.xml:145(para) ./doc/install-guide/section_ceilometer-nova.xml:136(para) +msgid "Restart the service with its new settings:" +msgstr "" + +#: ./doc/install-guide/section_debconf-preseeding.xml:6(title) +msgid "Pre-seed debconf prompts" +msgstr "" + +#: ./doc/install-guide/section_debconf-preseeding.xml:7(para) +msgid "You can pre-seed all debconf prompts. To pre-seed means to store responses in the debconf database so that debconf does not prompt the user for responses. Pre-seeding enables a hands-free installation for users. The package maintainer creates scripts that automatically configure the services." +msgstr "" + +#: ./doc/install-guide/section_debconf-preseeding.xml:14(para) +msgid "The following example shows how to pre-seed an automated MySQL Server installation:" +msgstr "" + +#: ./doc/install-guide/section_debconf-preseeding.xml:16(replaceable) ./doc/install-guide/section_debconf-preseeding.xml:17(replaceable) ./doc/install-guide/section_debconf-preseeding.xml:19(replaceable) +msgid "MYSQL_PASSWORD" +msgstr "" + +#: ./doc/install-guide/section_debconf-preseeding.xml:23(para) +msgid "The seen true option tells debconf that a specified screen was already seen by the user so do not show it again. This option is useful for upgrades." +msgstr "" + +#. When image changes, this message will be marked fuzzy or untranslated for you. +#. It doesn't matter what you translate it to: it's not used at all. +#: ./doc/install-guide/section_neutron-single-flat.xml:22(None) +msgid "@@image: '../common/figures/demo_flat_install.png'; md5=27b45d5871859ff4951c92df7c8763d8" +msgstr "" + +#. When image changes, this message will be marked fuzzy or untranslated for you. +#. It doesn't matter what you translate it to: it's not used at all. +#: ./doc/install-guide/section_neutron-single-flat.xml:621(None) +msgid "@@image: '../common/figures/UseCase-SingleFlat.png'; md5=bdd61f2967fb1a55e4f50d766db7b113" +msgstr "" + +#. When image changes, this message will be marked fuzzy or untranslated for you. +#. It doesn't matter what you translate it to: it's not used at all. +#: ./doc/install-guide/section_neutron-single-flat.xml:637(None) +msgid "@@image: '../common/figures/UseCase-MultiFlat.png'; md5=289e38a7a13a2a4413e5a1e62ce55b3e" +msgstr "" + +#. When image changes, this message will be marked fuzzy or untranslated for you. +#. It doesn't matter what you translate it to: it's not used at all. +#: ./doc/install-guide/section_neutron-single-flat.xml:659(None) +msgid "@@image: '../common/figures/UseCase-MixedFlatPrivate.png'; md5=8da4ceb5a1e5a2357394478645af7449" +msgstr "" + +#: ./doc/install-guide/section_neutron-single-flat.xml:6(title) +msgid "Single flat network" +msgstr "" + +#: ./doc/install-guide/section_neutron-single-flat.xml:7(para) +msgid "This section describes how to install the OpenStack Networking service and its components for a single flat network use case." +msgstr "" + +#: ./doc/install-guide/section_neutron-single-flat.xml:10(para) +msgid "The following diagram shows the set up. For simplicity, all nodes should have one interface for management traffic and one or more interfaces for traffic to and from VMs. The management network is 100.1.1.0/24 with controller node at 100.1.1.2. The example uses the Open vSwitch plugin and agent." +msgstr "" + +#: ./doc/install-guide/section_neutron-single-flat.xml:16(para) +msgid "You can modify this set up to make use of another supported plug-in and its agent." +msgstr "" + +#: ./doc/install-guide/section_neutron-single-flat.xml:25(para) +msgid "The following table describes some nodes in the set up:" +msgstr "" + +#: ./doc/install-guide/section_neutron-single-flat.xml:39(para) +msgid "Runs the Networking service, Identity Service, and Compute services that are required to deploy VMs (nova-api, nova-scheduler, for example). The node must have at least one network interface, which is connected to the Management Network. The host name is controller, which every other node resolves to the IP of the controller node." +msgstr "" + +#: ./doc/install-guide/section_neutron-single-flat.xml:52(para) +msgid "The nova-network service should not be running. This is replaced by the OpenStack Networking component, neutron. To delete a network, run this command:" +msgstr "" + +#: ./doc/install-guide/section_neutron-single-flat.xml:64(para) +msgid "Note that a network must first be disassociated from a project using the nova network-disassociate command before it can be deleted." +msgstr "" + +#: ./doc/install-guide/section_neutron-single-flat.xml:71(td) +msgid "Runs the Networking L2 agent and the Compute services that run VMs ( specifically, and optionally other nova-* services depending on configuration). The node must have at least two network interfaces. The first communicates with the controller node through the management network. The second interface handles the VM traffic on the data network. The VM can receive its IP address from the DHCP agent on this network." +msgstr "" + +#: ./doc/install-guide/section_neutron-single-flat.xml:85(td) +msgid "Runs Networking L2 agent and the DHCP agent. The DHCP agent allocates IP addresses to the VMs on the network. The node must have at least two network interfaces. The first communicates with the controller node through the management network. The second interface handles the VM traffic on the data network." +msgstr "" + +#: ./doc/install-guide/section_neutron-single-flat.xml:101(para) +msgid "The demo assumes the following prerequisites:" +msgstr "" + +#: ./doc/install-guide/section_neutron-single-flat.xml:109(para) +msgid "Glance is installed, configured, and running. Additionally, an image must be available." +msgstr "" + +#: ./doc/install-guide/section_neutron-single-flat.xml:113(para) +msgid "OpenStack Identity is installed, configured, and running. A Networking user neutron is in place on tenant service with password NEUTRON_PASS." +msgstr "" + +#: ./doc/install-guide/section_neutron-single-flat.xml:121(para) +msgid "Additional services:" +msgstr "" + +#: ./doc/install-guide/section_neutron-single-flat.xml:124(para) +msgid "RabbitMQ is running with the default guest user and password RABBIT_PASS." +msgstr "" + +#: ./doc/install-guide/section_neutron-single-flat.xml:129(para) +msgid "Qpid is running with the default guest user and password." +msgstr "" + +#: ./doc/install-guide/section_neutron-single-flat.xml:142(para) +msgid "Compute is installed and configured." +msgstr "" + +#: ./doc/install-guide/section_neutron-single-flat.xml:155(para) +msgid "Install the Networking server and respond to debconf prompts to configure the database, the keystone_authtoken, and the RabbitMQ credentials." +msgstr "" + +#: ./doc/install-guide/section_neutron-single-flat.xml:162(para) +msgid "See for installation instructions." +msgstr "" + +#: ./doc/install-guide/section_neutron-single-flat.xml:171(para) +msgid "See for database creation details." +msgstr "" + +#: ./doc/install-guide/section_neutron-single-flat.xml:177(para) +msgid "If not already configured, update the Networking /etc/neutron/neutron.conf configuration file to use the Identity Service, the plug-in, and database configuration:" +msgstr "" + +#: ./doc/install-guide/section_neutron-single-flat.xml:191(para) ./doc/install-guide/section_neutron-install.xml:332(para) ./doc/install-guide/section_neutron-install.xml:910(para) ./doc/install-guide/section_neutron-install.xml:1218(para) +msgid "Configure Networking to connect to the database:" +msgstr "" + +#: ./doc/install-guide/section_neutron-single-flat.xml:194(para) ./doc/install-guide/section_neutron-single-flat.xml:347(para) +msgid "Configure Networking to use your chosen plug-in:" +msgstr "" + +#: ./doc/install-guide/section_neutron-single-flat.xml:199(para) ./doc/install-guide/section_neutron-single-flat.xml:352(para) ./doc/install-guide/section_neutron-single-flat.xml:436(para) ./doc/install-guide/section_neutron-install.xml:299(para) ./doc/install-guide/section_neutron-install.xml:863(para) ./doc/install-guide/section_neutron-install.xml:1314(para) +msgid "Configure access to the RabbitMQ service:" +msgstr "" + +#: ./doc/install-guide/section_neutron-single-flat.xml:208(para) ./doc/install-guide/section_neutron-single-flat.xml:361(para) ./doc/install-guide/section_neutron-single-flat.xml:445(para) ./doc/install-guide/section_neutron-install.xml:319(para) ./doc/install-guide/section_neutron-install.xml:874(para) ./doc/install-guide/section_neutron-install.xml:1325(para) +msgid "Configure access to the Qpid message queue:" +msgstr "" + +#: ./doc/install-guide/section_neutron-single-flat.xml:216(replaceable) ./doc/install-guide/section_neutron-single-flat.xml:218(replaceable) ./doc/install-guide/section_neutron-single-flat.xml:369(replaceable) ./doc/install-guide/section_neutron-single-flat.xml:371(replaceable) ./doc/install-guide/section_neutron-single-flat.xml:453(replaceable) ./doc/install-guide/section_neutron-single-flat.xml:455(replaceable) ./doc/install-guide/section_neutron-install.xml:327(replaceable) ./doc/install-guide/section_neutron-install.xml:329(replaceable) ./doc/install-guide/section_neutron-install.xml:882(replaceable) ./doc/install-guide/section_neutron-install.xml:884(replaceable) ./doc/install-guide/section_neutron-install.xml:1333(replaceable) ./doc/install-guide/section_neutron-install.xml:1335(replaceable) +msgid "guest" +msgstr "" + +#: ./doc/install-guide/section_neutron-single-flat.xml:221(para) +msgid "If not already configured, update the Networking /etc/neutron/neutron.conf configuration file to choose a plug-in and Identity Service user as necessary:" +msgstr "" + +#: ./doc/install-guide/section_neutron-single-flat.xml:243(para) +msgid "Update the plug-in /etc/neutron/plugins/openvswitch/ovs_neutron_plugin.ini configuration file with the bridge mappings:" +msgstr "" + +#: ./doc/install-guide/section_neutron-single-flat.xml:258(para) +msgid "Restart the Networking service:" +msgstr "" + +#: ./doc/install-guide/section_neutron-single-flat.xml:265(emphasis) +msgid "Compute node - Compute" +msgstr "" + +#: ./doc/install-guide/section_neutron-single-flat.xml:267(para) +msgid "Install the nova-compute service." +msgstr "" + +#: ./doc/install-guide/section_neutron-single-flat.xml:271(para) +msgid "See for installation instructions." +msgstr "" + +#: ./doc/install-guide/section_neutron-single-flat.xml:276(para) +msgid "Update the Compute /etc/nova/nova.conf configuration file to make use of OpenStack Networking:" +msgstr "" + +#: ./doc/install-guide/section_neutron-single-flat.xml:304(para) +msgid "Restart the Compute services" +msgstr "" + +#: ./doc/install-guide/section_neutron-single-flat.xml:311(emphasis) +msgid "Compute and Network node - L2 agent" +msgstr "" + +#: ./doc/install-guide/section_neutron-single-flat.xml:314(para) +msgid "Install and start Open vSwitch. Then, configure neutron accordingly." +msgstr "" + +#: ./doc/install-guide/section_neutron-single-flat.xml:316(para) +msgid "See for detailed instructions." +msgstr "" + +#: ./doc/install-guide/section_neutron-single-flat.xml:321(para) +msgid "Add the integration bridge to Open vSwitch:" +msgstr "" + +#: ./doc/install-guide/section_neutron-single-flat.xml:326(para) ./doc/install-guide/section_neutron-single-flat.xml:418(para) +msgid "Update the Networking /etc/neutron/neutron.conf configuration file:" +msgstr "" + +#: ./doc/install-guide/section_neutron-single-flat.xml:341(para) +msgid "If not already configured, update the Networking /etc/neutron/neutron.conf configuration file to use the plug-in, message queue, and database configuration:" +msgstr "" + +#: ./doc/install-guide/section_neutron-single-flat.xml:374(para) +msgid "Update the plug-in /etc/neutron/plugins/openvswitch/ovs_neutron_plugin.ini configuration file:" +msgstr "" + +#: ./doc/install-guide/section_neutron-single-flat.xml:388(para) +msgid "Create a symbolic link from /etc/neutron/plugin.ini to /etc/neutron/plugins/openvswitch/ovs_neutron_plugin.ini or neutron-server will not run:" +msgstr "" + +#: ./doc/install-guide/section_neutron-single-flat.xml:393(para) +msgid "Create the br-eth0 network bridge to handle communication between nodes using eth0:" +msgstr "" + +#: ./doc/install-guide/section_neutron-single-flat.xml:401(para) +msgid "Restart the OpenStack Networking L2 agent:" +msgstr "" + +#: ./doc/install-guide/section_neutron-single-flat.xml:409(emphasis) +msgid "Network node - DHCP agent" +msgstr "" + +#: ./doc/install-guide/section_neutron-single-flat.xml:413(para) +msgid "See for generic installation instructions." +msgstr "" + +#: ./doc/install-guide/section_neutron-single-flat.xml:429(para) +msgid "If not already configured, update the Networking /etc/neutron/neutron.conf configuration file to use the plug-in and message queue." +msgstr "" + +#: ./doc/install-guide/section_neutron-single-flat.xml:458(para) +msgid "Ensure that the DHCP agent is using the correct plug-in my changing the configuration in /etc/neutron/dhcp_agent.ini:" +msgstr "" + +#: ./doc/install-guide/section_neutron-single-flat.xml:466(para) +msgid "Restart the DHCP agent:" +msgstr "" + +#: ./doc/install-guide/section_neutron-single-flat.xml:476(para) +msgid "Use the following commands on the network node." +msgstr "" + +#: ./doc/install-guide/section_neutron-single-flat.xml:502(para) +msgid "Get the user information:" +msgstr "" + +#: ./doc/install-guide/section_neutron-single-flat.xml:515(para) +msgid "Create a internal shared network on the demo tenant ($TENANT_ID is b7445f221cda4f4a8ac7db6b218b1339):" +msgstr "" + +#: ./doc/install-guide/section_neutron-single-flat.xml:538(para) +msgid "Create a subnet on the network:" +msgstr "" + +#: ./doc/install-guide/section_neutron-single-flat.xml:558(para) +msgid "Create a server for tenant A:" +msgstr "" + +#: ./doc/install-guide/section_neutron-single-flat.xml:571(para) +msgid "Ping the server of tenant A:" +msgstr "" + +#: ./doc/install-guide/section_neutron-single-flat.xml:577(para) +msgid "Ping the public network within the server of tenant A:" +msgstr "" + +#: ./doc/install-guide/section_neutron-single-flat.xml:589(para) +msgid "The 192.168.1.1 is an IP on public network to which the router connects." +msgstr "" + +#: ./doc/install-guide/section_neutron-single-flat.xml:594(para) +msgid "Create servers for other tenants with similar commands. Because all VMs share the same subnet, they can access each other." +msgstr "" + +#: ./doc/install-guide/section_neutron-single-flat.xml:601(title) +msgid "Use case: single flat network" +msgstr "" + +#: ./doc/install-guide/section_neutron-single-flat.xml:602(para) +msgid "The simplest use case is a single network. This is a \"shared\" network, meaning it is visible to all tenants via the Networking API. Tenant VMs have a single NIC, and receive a fixed IP address from the subnet(s) associated with that network. This use case essentially maps to the FlatManager and FlatDHCPManager models provided by Compute. Floating IPs are not supported." +msgstr "" + +#: ./doc/install-guide/section_neutron-single-flat.xml:609(para) +msgid "This network type is often created by the OpenStack administrator to map directly to an existing physical network in the data center (called a \"provider network\"). This allows the provider to use a physical router on that data center network as the gateway for VMs to reach the outside world. For each subnet on an external network, the gateway configuration on the physical router must be manually configured outside of OpenStack." +msgstr "" + +#: ./doc/install-guide/section_neutron-single-flat.xml:628(title) +msgid "Use case: multiple flat network" +msgstr "" + +#: ./doc/install-guide/section_neutron-single-flat.xml:629(para) +msgid "This use case is similar to the above single flat network use case, except that tenants can see multiple shared networks via the Networking API and can choose which network (or networks) to plug into." +msgstr "" + +#: ./doc/install-guide/section_neutron-single-flat.xml:643(title) +msgid "Use case: mixed flat and private network" +msgstr "" + +#: ./doc/install-guide/section_neutron-single-flat.xml:644(para) +msgid "This use case is an extension of the above Flat Network use cases. In addition to being able to see one or more shared networks via the OpenStack Networking API, tenants can also have access to private per-tenant networks (only visible to tenant users)." +msgstr "" + +#: ./doc/install-guide/section_neutron-single-flat.xml:649(para) +msgid "Created VMs can have NICs on any of the shared or private networks that the tenant owns. This enables the creation of multi-tier topologies that use VMs with multiple NICs. It also enables a VM to act as a gateway so that it can provide services such as routing, NAT, and load balancing." +msgstr "" + +#: ./doc/install-guide/ch_neutron.xml:6(title) +msgid "Install the Networking service" +msgstr "" + +#: ./doc/install-guide/ch_neutron.xml:9(para) +msgid "This chapter is a bit more adventurous than we would like. We are working on cleanup and improvements to it. Like for the rest of the Installation Guide, feedback through bug reports and patches to improve it are welcome." +msgstr "" + +#: ./doc/install-guide/ch_neutron.xml:16(title) +msgid "Networking considerations" +msgstr "" + +#: ./doc/install-guide/ch_neutron.xml:17(para) +msgid "OpenStack Networking drivers range from software bridges to full control of certain switching hardware. This guide focuses on the Open vSwitch driver. However, the theories presented here are mostly applicable to other mechanisms, and the Networking chapter of the OpenStack Configuration Reference offers additional information." +msgstr "" + +#: ./doc/install-guide/ch_neutron.xml:26(para) +msgid "To prepare for installation, see ." +msgstr "" + +#: ./doc/install-guide/ch_neutron.xml:29(para) +msgid "If you previously set up networking for your compute node by using nova-network, this configuration overrides those settings." +msgstr "" + +#. When image changes, this message will be marked fuzzy or untranslated for you. +#. It doesn't matter what you translate it to: it's not used at all. +#: ./doc/install-guide/ch_basics.xml:123(None) +msgid "@@image: 'figures/basic-architecture-networking.svg'; md5=1a9454b8cdb45af98a43fbff5dd58fe9" +msgstr "" + +#: ./doc/install-guide/ch_basics.xml:6(title) +msgid "Basic operating system configuration" +msgstr "" + +#: ./doc/install-guide/ch_basics.xml:8(para) +msgid "This guide shows you how to create a controller node to host most services and a compute node to run virtual machine instances. Subsequent chapters create additional nodes to run more services. OpenStack is flexible about how and where you run each service, so other configurations are possible. However, you must configure certain operating system settings on each node." +msgstr "" + +#: ./doc/install-guide/ch_basics.xml:14(para) +msgid "This chapter details a sample configuration for the controller node and any additional nodes. You can configure the operating system in other ways, but this guide assumes that your configuration is compatible with the one described here." +msgstr "" + +#: ./doc/install-guide/ch_basics.xml:18(para) +msgid "All example commands assume you have administrative privileges. Either run the commands as the root user or prefix them with the command." +msgstr "" + +#: ./doc/install-guide/ch_basics.xml:24(title) ./doc/install-guide/object-storage/section_object-storage-install.xml:23(title) +msgid "Before you begin" +msgstr "" + +#: ./doc/install-guide/ch_basics.xml:26(para) +msgid "We strongly recommend that you install a 64-bit operating system on your compute nodes. If you use a 32-bit operating system, attempting a start a virtual machine using a 64-bit image will fail with an error." +msgstr "" + +#: ./doc/install-guide/ch_basics.xml:31(para) +msgid "For more information about system requirements, see the OpenStack Operations Guide." +msgstr "" + +#: ./doc/install-guide/ch_basics.xml:38(title) +msgid "Networking" +msgstr "" + +#: ./doc/install-guide/ch_basics.xml:40(para) +msgid "For an OpenStack production deployment, most nodes must have these network interface cards:" +msgstr "" + +#: ./doc/install-guide/ch_basics.xml:44(para) +msgid "One network interface card for external network traffic" +msgstr "" + +#: ./doc/install-guide/ch_basics.xml:48(para) +msgid "Another card to communicate with other OpenStack nodes." +msgstr "" + +#: ./doc/install-guide/ch_basics.xml:52(para) +msgid "For simple test cases, you can use machines with a single network interface card." +msgstr "" + +#: ./doc/install-guide/ch_basics.xml:54(para) +msgid "The following example configures Networking on two networks with static IP addresses and manually manages a list of host names on each machine. If you manage a large network, you might already have systems in place to manage this. If so, you can skip this section but note that the rest of this guide assumes that each node can reach the other nodes on the internal network by using the controller and compute1 host names." +msgstr "" + +#. these fedora only paragraphs are confirmed not needed in centos +#: ./doc/install-guide/ch_basics.xml:64(para) +msgid "Disable the NetworkManager service and enable the network service. The network service is more suitable for the static network configuration done in this guide." +msgstr "" + +#: ./doc/install-guide/ch_basics.xml:76(para) +msgid "Since Fedora 19, firewalld replaces iptables as the default firewall system." +msgstr "" + +#: ./doc/install-guide/ch_basics.xml:79(para) +msgid "You can use firewalld successfully, but this guide recommends and demonstrates the use of the default iptables." +msgstr "" + +#: ./doc/install-guide/ch_basics.xml:82(para) +msgid "For Fedora 19 systems, run the following commands to disable firewalld and enable iptables:" +msgstr "" + +#: ./doc/install-guide/ch_basics.xml:90(para) +msgid "RHEL and derivatives including CentOS and Scientific Linux enable a restrictive firewall by default. During this installation, certain steps will fail unless you alter this setting or disable the firewall. For further information about securing your installation, refer to the OpenStack Security Guide." +msgstr "" + +#: ./doc/install-guide/ch_basics.xml:98(para) +msgid "When you set up your system, use the traditional network scripts and do not use NetworkManager. You can change the settings after installation with the YaST network module:" +msgstr "" + +#: ./doc/install-guide/ch_basics.xml:104(para) +msgid "Configure both eth0 and eth1. The examples in this guide use the 192.168.0.x IP addresses for the internal network and the 10.0.0.x IP addresses for the external network. Make sure to connect your network devices to the correct network." +msgstr "" + +#: ./doc/install-guide/ch_basics.xml:111(para) +msgid "In this guide, the controller node uses the 192.168.0.10 and 10.0.0.10 IP addresses. When you create the compute node, use the 192.168.0.11 and 10.0.0.11 addresses instead. Additional nodes that you add in subsequent chapters also follow this pattern." +msgstr "" + +#: ./doc/install-guide/ch_basics.xml:119(title) +msgid "Basic architecture" +msgstr "" + +#: ./doc/install-guide/ch_basics.xml:128(filename) +msgid "/etc/sysconfig/network-scripts/ifcfg-eth0" +msgstr "" + +#: ./doc/install-guide/ch_basics.xml:139(filename) +msgid "/etc/sysconfig/network-scripts/ifcfg-eth1" +msgstr "" + +#: ./doc/install-guide/ch_basics.xml:149(para) +msgid "To configure the network interfaces, start the YaST network module, as follows:" +msgstr "" + +#: ./doc/install-guide/ch_basics.xml:154(para) +msgid "Use these parameters to set up the eth0 ethernet card for the internal network:" +msgstr "" + +#: ./doc/install-guide/ch_basics.xml:162(para) +msgid "Use these parameters to set up the eth1 ethernet card for the external network:" +msgstr "" + +#: ./doc/install-guide/ch_basics.xml:170(para) +msgid "Set up a default route on the external network." +msgstr "" + +#: ./doc/install-guide/ch_basics.xml:175(filename) +msgid "/etc/network/interfaces" +msgstr "" + +#: ./doc/install-guide/ch_basics.xml:189(para) +msgid "After you configure the network, restart the daemon for changes to take effect:" +msgstr "" + +#: ./doc/install-guide/ch_basics.xml:195(para) +msgid "Set the host name of each machine. Name the controller node controller and the first compute node compute1. The examples in this guide use these host names." +msgstr "" + +#: ./doc/install-guide/ch_basics.xml:199(para) +msgid "Use the command to set the host name: " +msgstr "" + +#: ./doc/install-guide/ch_basics.xml:202(para) +msgid "Use to set the host name with YaST." +msgstr "" + +#: ./doc/install-guide/ch_basics.xml:204(para) +msgid "To have the host name change persist when the system reboots, you must specify it in the proper configuration file. In Red Hat Enterprise Linux, CentOS, and older versions of Fedora, you set this in the file /etc/sysconfig/network. Change the line starting with HOSTNAME=." +msgstr "" + +#: ./doc/install-guide/ch_basics.xml:211(para) +msgid "As of Fedora 18, Fedora uses the /etc/hostname file, which contains a single line with the host name." +msgstr "" + +#: ./doc/install-guide/ch_basics.xml:214(para) +msgid "To configure this host name to be available when the system reboots, you must specify it in the /etc/hostname file, which contains a single line with the host name." +msgstr "" + +#: ./doc/install-guide/ch_basics.xml:218(para) +msgid "Finally, ensure that each node can reach the other nodes by using host names. You must manually edit the /etc/hosts file on each system. For large-scale deployments, use DNS or a configuration management system like Puppet." +msgstr "" + +#: ./doc/install-guide/ch_basics.xml:228(title) +msgid "Network Time Protocol (NTP)" +msgstr "" + +#: ./doc/install-guide/ch_basics.xml:229(para) +msgid "To synchronize services across multiple machines, you must install NTP. The examples in this guide configure the controller node as the reference server and any additional nodes to set their time from the controller node." +msgstr "" + +#: ./doc/install-guide/ch_basics.xml:234(para) +msgid "Install the ntp package on each system running OpenStack services." +msgstr "" + +#: ./doc/install-guide/ch_basics.xml:239(para) +msgid "Set up the NTP server on your controller node so that it receives data by modifying the ntp.conf file and restarting the service." +msgstr "" + +#: ./doc/install-guide/ch_basics.xml:247(para) +msgid "On additional nodes, it is advised that you configure the other nodes to synchronize their time from the controller node rather than from outside of your LAN. To do so, install the ntp daemon as above, then edit /etc/ntp.conf and change the server directive to use the controller node as internet time source." +msgstr "" + +#: ./doc/install-guide/ch_basics.xml:256(title) +msgid "Passwords" +msgstr "" + +#: ./doc/install-guide/ch_basics.xml:258(para) +msgid "The various OpenStack services and the required software like the database and the Messaging server have to be password protected. These passwords are needed when configuring a service and then again to access the service. You have to choose a random password while configuring the service and later remember to use the same password when accessing it. To generate a list of passwords, you can use the pwgen program to generate a list of passwords or take the output of: " +msgstr "" + +#: ./doc/install-guide/ch_basics.xml:269(para) +msgid "This guide uses the convention that SERVICE_PASS is password to access the service SERVICE and SERVICE_DBPASS is the database password used by the service SERVICE to access the database." +msgstr "" + +#: ./doc/install-guide/ch_basics.xml:277(para) +msgid "The complete list of passwords you need to define in this guide are:
Passwords
Password nameDescription
Database password (no variable used)Root password for the database
RABBIT_PASSPassword of user guest of RabbitMQ
KEYSTONE_DBPASSDatabase password of Identity service
ADMIN_PASSPassword of user admin
GLANCE_DBPASSDatabase password for Image Service
GLANCE_PASSPassword of Image Service user glance
NOVA_DBPASSDatabase password for Compute service
NOVA_PASSPassword of Compute service user nova
DASH_DBPASSDatabase password for the dashboard
CINDER_DBPASSDatabase password for the Block Storage Service
CINDER_PASSPassword of Block Storage Service user cinder
NEUTRON_DBPASSDatabase password for the Networking service
NEUTRON_PASSPassword of Networking service user neutron
HEAT_DBPASSDatabase password for the Orchestration service
HEAT_PASSPassword of Orchestration service user heat
CEILOMETER_DBPASSDatabase password for the Telemetry service
CEILOMETER_PASSPassword of Telemetry service user ceilometer
" +msgstr "" + +#: ./doc/install-guide/ch_basics.xml:361(title) +msgid "MySQL database" +msgstr "" + +#: ./doc/install-guide/ch_basics.xml:362(para) +msgid "Most OpenStack services require a database to store information. These examples use a MySQL database that runs on the controller node. You must install the MySQL database on the controller node. You must install MySQL client software on any additional nodes that access MySQL." +msgstr "" + +#: ./doc/install-guide/ch_basics.xml:368(para) +msgid "Most OpenStack services require a database to store information. This guide uses a MySQL database on SUSE Linux Enterprise Server and a compatible database on openSUSE running on the controller node. This compatible database for openSUSE is MariaDB. You must install the MariaDB database on the controller node. You must install the MariaDB client software on any nodes that access the MariaDB database." +msgstr "" + +#: ./doc/install-guide/ch_basics.xml:378(title) +msgid "Controller setup" +msgstr "" + +#: ./doc/install-guide/ch_basics.xml:379(para) +msgid "For SUSE Linux Enterprise Server: On the controller node, install the MySQL client and server packages, and the Python library." +msgstr "" + +#: ./doc/install-guide/ch_basics.xml:383(para) +msgid "For openSUSE: On the controller node, install the MariaDB client and database server packages, and the MySQL Python library." +msgstr "" + +#: ./doc/install-guide/ch_basics.xml:390(para) +msgid "When you install the server package, you are prompted for the root password for the database. Choose a strong password and remember it." +msgstr "" + +#: ./doc/install-guide/ch_basics.xml:394(para) +msgid "Edit /etc/mysql/my.cnf/etc/my.cnf and set the bind-address to the internal IP address of the controller, to enable access from outside the controller node." +msgstr "" + +#: ./doc/install-guide/ch_basics.xml:404(para) +msgid "Restart the MySQL service to apply the changes:" +msgstr "" + +#: ./doc/install-guide/ch_basics.xml:407(para) +msgid "Start the MySQLMariaDB or MySQL database server and set it to start automatically when the system boots." +msgstr "" + +#: ./doc/install-guide/ch_basics.xml:416(para) +msgid "Finally, you should set a root password for your MySQLMariaDB or MySQL database. The OpenStack programs that set up databases and tables prompt you for this password if it is set." +msgstr "" + +#: ./doc/install-guide/ch_basics.xml:422(para) +msgid "You must delete the anonymous users that are created when the database is first started. Otherwise, database connection problems occur when you follow the instructions in this guide. To do this, use the command. Note that if fails you might need to use first:" +msgstr "" + +#: ./doc/install-guide/ch_basics.xml:431(para) +msgid "If you have not already set a root database password, press ENTER when you are prompted for the password. This command presents a number of options for you to secure your database installation. Respond to all prompts unless you have a good reason to do otherwise." +msgstr "" + +#: ./doc/install-guide/ch_basics.xml:441(title) +msgid "Node setup" +msgstr "" + +#: ./doc/install-guide/ch_basics.xml:442(para) +msgid "On all nodes other than the controller node, install the MySQLMariaDB (on openSUSE) client and the MySQL Python library on any system that does not host a MySQL database:" +msgstr "" + +#: ./doc/install-guide/ch_basics.xml:451(para) +msgid "For SUSE Linux Enterprise, install MySQL:" +msgstr "" + +#: ./doc/install-guide/ch_basics.xml:458(title) +msgid "OpenStack packages" +msgstr "" + +#: ./doc/install-guide/ch_basics.xml:459(para) +msgid "Distributions might release OpenStack packages as part of their distribution or through other methods because the OpenStack and distribution release times are independent of each other." +msgstr "" + +#: ./doc/install-guide/ch_basics.xml:463(para) +msgid "This section describes the configuration you must complete after you configure machines to install the latest OpenStack packages." +msgstr "" + +#: ./doc/install-guide/ch_basics.xml:466(para) +msgid "The examples in this guide use the OpenStack packages from the RDO repository. These packages work on Red Hat Enterprise Linux 6, compatible versions of CentOS, and Fedora 19. To enable the RDO repository, download and install the rdo-release-havana package." +msgstr "" + +#: ./doc/install-guide/ch_basics.xml:473(para) +msgid "The EPEL package includes GPG keys for package signing and repository information. This should only be installed on Red Hat Enterprise Linux and CentOS, not Fedora. Install the latest epel-release package (see http://download.fedoraproject.org/pub/epel/6/x86_64/repoview/epel-release.html). For example:" +msgstr "" + +#: ./doc/install-guide/ch_basics.xml:482(para) +msgid "The openstack-utils package contains utility programs that make installation and configuration easier. These programs are used throughout this guide. Install openstack-utils. This verifies that you can access the RDO repository." +msgstr "" + +#: ./doc/install-guide/ch_basics.xml:489(para) +msgid "Use the Open Build Service repositories for Havana based on your openSUSE or SUSE Linux Enterprise Server version, for example if you run openSUSE 12.3 use:" +msgstr "" + +#: ./doc/install-guide/ch_basics.xml:494(para) +msgid "If you use SUSE Linux Enterprise Server 11 SP3, use:" +msgstr "" + +#: ./doc/install-guide/ch_basics.xml:497(para) +msgid "For openSUSE 13.1, nothing needs to be done because OpenStack Havana packages are part of the distribution itself." +msgstr "" + +#: ./doc/install-guide/ch_basics.xml:500(para) +msgid "The openstack-utils package contains utility programs that make installation and configuration easier. These programs are used throughout this guide. Install openstack-utils. This verifies that you can access the Open Build Service repository:" +msgstr "" + +#: ./doc/install-guide/ch_basics.xml:507(para) +msgid "The openstack-config program in the openstack-utils package uses crudini to manipulate configuration files. However, crudini version 0.3 does not support multi valued options. See https://bugs.launchpad.net/openstack-manuals/+bug/1269271. As a work around, you must manually set any multi valued options or the new value overwrites the previous value instead of creating a new option." +msgstr "" + +#: ./doc/install-guide/ch_basics.xml:519(para) +msgid "The openstack-selinux package includes the policy files that are required to configure SELinux during OpenStack installation. Install openstack-selinux." +msgstr "" + +#: ./doc/install-guide/ch_basics.xml:525(para) +msgid "Upgrade your system packages:" +msgstr "" + +#: ./doc/install-guide/ch_basics.xml:529(para) +msgid "If the upgrade included a new kernel package, reboot the system to ensure the new kernel is running:" +msgstr "" + +#: ./doc/install-guide/ch_basics.xml:533(title) +msgid "To use the Ubuntu Cloud Archive for Havana" +msgstr "" + +#: ./doc/install-guide/ch_basics.xml:534(para) +msgid "The Ubuntu Cloud Archive is a special repository that allows you to install newer releases of OpenStack on the stable supported version of Ubuntu." +msgstr "" + +#: ./doc/install-guide/ch_basics.xml:540(para) +msgid "Install the Ubuntu Cloud Archive for Havana: " +msgstr "" + +#: ./doc/install-guide/ch_basics.xml:546(para) +msgid "Update the package database, upgrade your system, and reboot for all changes to take effect: " +msgstr "" + +#: ./doc/install-guide/ch_basics.xml:553(title) +msgid "To use the Debian Wheezy backports archive for Havana" +msgstr "" + +#: ./doc/install-guide/ch_basics.xml:555(para) +msgid "The Havana release is available only in Debian Sid (otherwise called Unstable). However, the Debian maintainers of OpenStack also maintain a non-official Debian repository for OpenStack containing Wheezy backports." +msgstr "" + +#: ./doc/install-guide/ch_basics.xml:561(para) +msgid "Install the Debian Wheezy backport repository Havana:" +msgstr "" + +#: ./doc/install-guide/ch_basics.xml:566(para) +msgid "Install the Debian Wheezy OpenStack repository for Havana:" +msgstr "" + +#: ./doc/install-guide/ch_basics.xml:571(para) +msgid "Update the repository database and install the key:" +msgstr "" + +#: ./doc/install-guide/ch_basics.xml:575(para) +msgid "Update the package database, upgrade your system, and reboot for all changes to take effect:" +msgstr "" + +#: ./doc/install-guide/ch_basics.xml:581(para) +msgid "Numerous archive.gplhost.com mirrors are available around the world. All are available with both FTP and HTTP protocols (you should use the closest mirror). The list of mirrors is available at http://archive.gplhost.com/readme.mirrors." +msgstr "" + +#: ./doc/install-guide/ch_basics.xml:589(title) +msgid "Manually install python-argparse" +msgstr "" + +#: ./doc/install-guide/ch_basics.xml:590(para) +msgid "The Debian OpenStack packages are maintained on Debian Sid (also known as Debian Unstable) - the current development version. Backported packages run correctly on Debian Wheezy with one caveat:" +msgstr "" + +#: ./doc/install-guide/ch_basics.xml:594(para) +msgid "All OpenStack packages are written in Python. Wheezy uses Python 2.6 and 2.7, with Python 2.6 as the default interpreter; Sid has only Python 2.7. There is one packaging change between these two. In Python 2.6, you installed the python-argparse package separately. In Python 2.7, this package is installed by default. Unfortunately, in Python 2.7, this package does not include Provides: python-argparse directive." +msgstr "" + +#: ./doc/install-guide/ch_basics.xml:602(para) +msgid "Because the packages are maintained in Sid where the Provides: python-argparse directive causes an error, and the Debian OpenStack maintainer wants to maintain one version of the OpenStack packages, you must manually install the python-argparse on each OpenStack system that runs Debian Wheezy before you install the other OpenStack packages. Use the following command to install the package:" +msgstr "" + +#: ./doc/install-guide/ch_basics.xml:611(para) +msgid "This caveat applies to most OpenStack packages in Wheezy." +msgstr "" + +#: ./doc/install-guide/ch_basics.xml:615(title) +msgid "Messaging server" +msgstr "" + +#: ./doc/install-guide/ch_basics.xml:616(para) +msgid "On the controller node, install the messaging queue server. Typically this is RabbitMQQpid but QpidRabbitMQ and ZeroMQ (0MQ) are also available." +msgstr "" + +#: ./doc/install-guide/ch_basics.xml:628(title) +msgid "Important security consideration" +msgstr "" + +#: ./doc/install-guide/ch_basics.xml:629(para) +msgid "The rabbitmq-server package configures the RabbitMQ service to start automatically and creates a guest user with a default guest password. The RabbitMQ examples in this guide use the guest account, though it is strongly advised to change its default password, especially if you have IPv6 available: by default the RabbitMQ server enables anyone to connect to it by using guest as login and password, and with IPv6, it is reachable from the outside." +msgstr "" + +#: ./doc/install-guide/ch_basics.xml:639(para) +msgid "To change the default guest password of RabbitMQ:" +msgstr "" + +#: ./doc/install-guide/ch_basics.xml:642(para) +msgid "Disable Qpid authentication by editing /etc/qpidd.conf file and changing the auth option to no." +msgstr "" + +#: ./doc/install-guide/ch_basics.xml:648(para) +msgid "To simplify configuration, the Qpid examples in this guide do not use authentication. However, we strongly advise enabling authentication for production deployments. For more information on securing Qpid refer to the Qpid Documentation." +msgstr "" + +#: ./doc/install-guide/ch_basics.xml:657(para) +msgid "After you enable Qpid authentication, you must update the configuration file of each OpenStack service to ensure that the qpid_username and qpid_password configuration keys refer to a valid Qpid username and password, respectively." +msgstr "" + +#: ./doc/install-guide/ch_basics.xml:665(para) +msgid "Start Qpid and set it to start automatically when the system boots." +msgstr "" + +#: ./doc/install-guide/ch_basics.xml:669(para) +msgid "Start the messaging service and set it to start automatically when the system boots:" +msgstr "" + +#: ./doc/install-guide/ch_basics.xml:673(para) +msgid "Congratulations, now you are ready to install OpenStack services!" +msgstr "" + +#: ./doc/install-guide/section_cinder-node.xml:6(title) +msgid "Configure a Block Storage Service node" +msgstr "" + +#: ./doc/install-guide/section_cinder-node.xml:7(para) +msgid "After you configure the services on the controller node, configure a second system to be a Block Storage Service node. This node contains the disk that serves volumes." +msgstr "" + +#: ./doc/install-guide/section_cinder-node.xml:10(para) ./doc/install-guide/section_cinder-controller.xml:15(para) +msgid "You can configure OpenStack to use various storage systems. The examples in this guide show you how to configure LVM." +msgstr "" + +#: ./doc/install-guide/section_cinder-node.xml:14(para) +msgid "Use the instructions in to configure the system. Note the following differences from the installation instructions for the controller node:" +msgstr "" + +#: ./doc/install-guide/section_cinder-node.xml:19(para) +msgid "Set the host name to block1. Ensure that the IP addresses and host names for both nodes are listed in the /etc/hosts file on each system." +msgstr "" + +#: ./doc/install-guide/section_cinder-node.xml:25(para) +msgid "Follow the instructions in to synchronize from the controller node." +msgstr "" + +#: ./doc/install-guide/section_cinder-node.xml:31(para) +msgid "Install the required LVM packages, if they are not already installed: " +msgstr "" + +#: ./doc/install-guide/section_cinder-node.xml:37(para) +msgid "Create the LVM physical and logical volumes. This guide assumes a second disk /dev/sdb that is used for this purpose:" +msgstr "" + +#: ./doc/install-guide/section_cinder-node.xml:45(para) +msgid "Add a filter entry to the devices section /etc/lvm/lvm.conf to keep LVM from scanning devices used by virtual machines:" +msgstr "" + +#: ./doc/install-guide/section_cinder-node.xml:49(para) +msgid "You must add required physical volumes for LVM on the Block Storage host. Run the command to get a list or required volumes." +msgstr "" + +#: ./doc/install-guide/section_cinder-node.xml:53(para) +msgid "Each item in the filter array starts with either an a for accept, or an r for reject. The physical volumes that are required on the Block Storage host have names that begin with a. The array must end with \"r/.*/\" to reject any device not listed." +msgstr "" + +#: ./doc/install-guide/section_cinder-node.xml:59(para) +msgid "In this example, /dev/sda1 is the volume where the volumes for the operating system for the node reside, while /dev/sdb is the volume reserved for cinder-volumes." +msgstr "" + +#: ./doc/install-guide/section_cinder-node.xml:70(para) +msgid "After you configure the operating system, install the appropriate packages for the Block Storage Service:" +msgstr "" + +#: ./doc/install-guide/section_cinder-node.xml:77(para) +msgid "Respond to the debconf prompts about the database management, [keystone_authtoken] settings, and RabbitMQ credentials. Make sure to enter the same details as your Block Storage Service controller node." +msgstr "" + +#: ./doc/install-guide/section_cinder-node.xml:85(para) +msgid "Another screen prompts you for the volume-group to use. The Debian package configuration script detects every active volume group, provided that the lvm2 package is installed before Block Storage (this should be the case if you configured the volume group first, as this guide recommends), and tries to use the first one it sees. If you have only one active volume group on your Block Storage Service node, you do not need to manually enter its name in when you install the cinder-volume package because it is detected automatically. If no volume-group is available when you install cinder-common, you must manually configure or re-configure cinder-common by using ." +msgstr "" + +#: ./doc/install-guide/section_cinder-node.xml:104(para) +msgid "Copy the /etc/cinder/api-paste.ini file from the controller, or open the file in a text editor and locate the section [filter:authtoken]. Make sure the following options are set:" +msgstr "" + +#: ./doc/install-guide/section_cinder-node.xml:115(replaceable) ./doc/install-guide/section_cinder-controller.xml:78(replaceable) ./doc/install-guide/section_cinder-controller.xml:94(replaceable) +msgid "CINDER_PASS" +msgstr "" + +#: ./doc/install-guide/section_cinder-node.xml:118(para) ./doc/install-guide/section_cinder-controller.xml:98(para) +msgid "Configure Block Storage to use the RabbitMQ message broker by setting these configuration keys in the [DEFAULT] configuration group of the /etc/cinder/cinder.conf file. Replace RABBIT_PASS with the password you chose for RabbitMQ." +msgstr "" + +#: ./doc/install-guide/section_cinder-node.xml:133(para) ./doc/install-guide/section_cinder-controller.xml:113(para) +msgid "Configure Block Storage to use the Qpid message broker." +msgstr "" + +#: ./doc/install-guide/section_cinder-node.xml:140(para) ./doc/install-guide/section_cinder-controller.xml:120(para) +msgid "Configure Block Storage to use the RabbitMQ message broker. Replace RABBIT_PASS with the password you chose for RabbitMQ." +msgstr "" + +#: ./doc/install-guide/section_cinder-node.xml:153(para) +msgid "Configure Block Storage to use your MySQL database. Edit the /etc/cinder/cinder.conf file and add the following key under the [database] section. Replace CINDER_DBPASS with the password you chose for the Block Storage database." +msgstr "" + +#: ./doc/install-guide/section_cinder-node.xml:158(para) ./doc/install-guide/section_cinder-controller.xml:41(para) +msgid "The /etc/cinder/cinder.conf file packaged with some distributions does not include the [database] section header. You must add this section header to the end of the file before proceeding further." +msgstr "" + +#: ./doc/install-guide/section_cinder-node.xml:164(replaceable) ./doc/install-guide/section_cinder-node.xml:167(replaceable) ./doc/install-guide/section_cinder-controller.xml:47(replaceable) ./doc/install-guide/section_cinder-controller.xml:50(replaceable) ./doc/install-guide/section_cinder-controller.xml:56(replaceable) ./doc/install-guide/section_cinder-controller.xml:64(replaceable) ./doc/install-guide/section_cinder-controller.xml:66(replaceable) +msgid "CINDER_DBPASS" +msgstr "" + +#: ./doc/install-guide/section_cinder-node.xml:173(para) ./doc/install-guide/section_cinder-controller.xml:158(para) +msgid "Restart the cinder service with its new settings:" +msgstr "" + +#: ./doc/install-guide/section_cinder-node.xml:180(para) +msgid "Configure the ISCI target service to discover cinder volumes. Add the following line to the beginning of the /etc/tgt/targets.conf file, if it is not already present:" +msgstr "" + +#: ./doc/install-guide/section_cinder-node.xml:188(para) +msgid "Start the cinder services and configure them to start when the system boots:" +msgstr "" + +#: ./doc/install-guide/section_cinder-controller.xml:5(title) +msgid "Configure a Block Storage Service controller" +msgstr "" + +#: ./doc/install-guide/section_cinder-controller.xml:7(para) +msgid "This section describes how to configure OpenStack Block Storage services on the Controller node and assumes that a second node provides storage through the cinder-volume service. For instructions on how to configure the second node, see ." +msgstr "" + +#: ./doc/install-guide/section_cinder-controller.xml:19(para) +msgid "Install the appropriate packages for the Block Storage Service:" +msgstr "" + +#: ./doc/install-guide/section_cinder-controller.xml:26(para) +msgid "Respond to the prompts for database management, [keystone_authtoken] settings, RabbitMQ credentials and API endpoint registration." +msgstr "" + +#: ./doc/install-guide/section_cinder-controller.xml:35(para) +msgid "Configure Block Storage to use your MySQL database. Edit the /etc/cinder/cinder.conf file and add the following key under the [database] section. Replace CINDER_DBPASS with the password for the Block Storage database that you will create in a later step." +msgstr "" + +#: ./doc/install-guide/section_cinder-controller.xml:53(para) +msgid "To create the Block Storage Service database and tables and a cinder database user, run the command." +msgstr "" + +#: ./doc/install-guide/section_cinder-controller.xml:59(para) +msgid "Use the password that you set to log in as root to create a cinder database." +msgstr "" + +#: ./doc/install-guide/section_cinder-controller.xml:69(para) +msgid "Create the database tables for the Block Storage Service." +msgstr "" + +#: ./doc/install-guide/section_cinder-controller.xml:74(para) +msgid "Create a cinder user. The Block Storage Service uses this user to authenticate with the Identity Service. Use the service tenant and give the user the admin role." +msgstr "" + +#: ./doc/install-guide/section_cinder-controller.xml:78(replaceable) +msgid "cinder@example.com" +msgstr "" + +#: ./doc/install-guide/section_cinder-controller.xml:82(para) +msgid "Add the credentials to the file /etc/cinder/api-paste.ini. Open the file in a text editor and locate the section [filter:authtoken]. Set the following options:" +msgstr "" + +#: ./doc/install-guide/section_cinder-controller.xml:134(para) +msgid "Register the Block Storage Service with the Identity Service so that other OpenStack services can locate it. Register the service and specify the endpoint using the command." +msgstr "" + +#: ./doc/install-guide/section_cinder-controller.xml:147(para) +msgid "Also register a service and endpoint for version 2 of the Block Storage Service API." +msgstr "" + +#: ./doc/install-guide/section_cinder-controller.xml:163(para) +msgid "Start the cinder services and configure them to start when the system boots." +msgstr "" + +#: ./doc/install-guide/bk_openstackinstallguide.xml:8(title) +msgid "OpenStack Installation Guide for Red Hat Enterprise Linux, CentOS, and Fedora for Ubuntu 12.04 (LTS) for Debian 7.0 (Wheezy) for openSUSE and SUSE Linux Enterprise Server" +msgstr "" + +#: ./doc/install-guide/bk_openstackinstallguide.xml:18(phrase) +msgid "for Red Hat Enterprise Linux, CentOS, and Fedora" +msgstr "" + +#: ./doc/install-guide/bk_openstackinstallguide.xml:20(phrase) +msgid "for Ubuntu 12.04 (LTS)" +msgstr "" + +#: ./doc/install-guide/bk_openstackinstallguide.xml:21(phrase) +msgid "for openSUSE and SUSE Linux Enterprise Server" +msgstr "" + +#: ./doc/install-guide/bk_openstackinstallguide.xml:23(phrase) +msgid "for Debian 7.0 (Wheezy)" +msgstr "" + +#: ./doc/install-guide/bk_openstackinstallguide.xml:17(titleabbrev) +msgid "OpenStack Installation Guide" +msgstr "" + +#: ./doc/install-guide/bk_openstackinstallguide.xml:32(orgname) +msgid "OpenStack" +msgstr "" + +#: ./doc/install-guide/bk_openstackinstallguide.xml:36(year) +msgid "2012" +msgstr "" + +#: ./doc/install-guide/bk_openstackinstallguide.xml:37(year) +msgid "2013" +msgstr "" + +#: ./doc/install-guide/bk_openstackinstallguide.xml:38(holder) +msgid "OpenStack Foundation" +msgstr "" + +#: ./doc/install-guide/bk_openstackinstallguide.xml:40(releaseinfo) +msgid "havana" +msgstr "" + +#: ./doc/install-guide/bk_openstackinstallguide.xml:41(productname) +msgid "OpenStack Installation Guide" +msgstr "" + +#: ./doc/install-guide/bk_openstackinstallguide.xml:45(remark) +msgid "Copyright details are filled in by the template." +msgstr "" + +#: ./doc/install-guide/bk_openstackinstallguide.xml:50(para) +msgid "The OpenStack® system consists of several key projects that you install separately but that work together depending on your cloud needs. These projects include Compute, Identity Service, Networking, Image Service, Block Storage Service, Object Storage, Telemetry, and Orchestration. You can install any of these projects separately and configure them standalone or as connected entities. This guide walks through an installation by using packages available through Debian 7.0 (code name: Wheezy).This guide walks through an installation by using packages available through Ubuntu 12.04 (LTS).This guide shows you how to install OpenStack by using packages available through Fedora 19 as well as on Red Hat Enterprise Linux and its derivatives through the EPEL repository.This guide shows you how to install OpenStack by using packages on openSUSE through the Open Build Service Cloud repository. Explanations of configuration options and sample configuration files are included." +msgstr "" + +#: ./doc/install-guide/bk_openstackinstallguide.xml:78(date) +msgid "2013-10-25" +msgstr "" + +#: ./doc/install-guide/bk_openstackinstallguide.xml:82(para) +msgid "Added initial Debian support." +msgstr "" + +#: ./doc/install-guide/bk_openstackinstallguide.xml:88(date) +msgid "2013-10-17" +msgstr "" + +#: ./doc/install-guide/bk_openstackinstallguide.xml:92(para) +msgid "Havana release." +msgstr "" + +#: ./doc/install-guide/bk_openstackinstallguide.xml:98(date) +msgid "2013-10-16" +msgstr "" + +#: ./doc/install-guide/bk_openstackinstallguide.xml:102(para) +msgid "Add support for SUSE Linux Enterprise." +msgstr "" + +#: ./doc/install-guide/bk_openstackinstallguide.xml:109(date) +msgid "2013-10-08" +msgstr "" + +#: ./doc/install-guide/bk_openstackinstallguide.xml:113(para) +msgid "Complete reorganization for Havana." +msgstr "" + +#: ./doc/install-guide/bk_openstackinstallguide.xml:120(date) +msgid "2013-09-09" +msgstr "" + +#: ./doc/install-guide/bk_openstackinstallguide.xml:124(para) +msgid "Build also for openSUSE." +msgstr "" + +#: ./doc/install-guide/bk_openstackinstallguide.xml:130(date) +msgid "2013-08-01" +msgstr "" + +#: ./doc/install-guide/bk_openstackinstallguide.xml:134(para) +msgid "Fixes to Object Storage verification steps. Fix bug 1207347." +msgstr "" + +#: ./doc/install-guide/bk_openstackinstallguide.xml:143(date) +msgid "2013-07-25" +msgstr "" + +#: ./doc/install-guide/bk_openstackinstallguide.xml:147(para) +msgid "Adds creation of cinder user and addition to the service tenant. Fix bug 1205057." +msgstr "" + +#: ./doc/install-guide/bk_openstackinstallguide.xml:157(date) +msgid "2013-05-08" +msgstr "" + +#: ./doc/install-guide/bk_openstackinstallguide.xml:161(para) +msgid "Updated the book title for consistency." +msgstr "" + +#: ./doc/install-guide/bk_openstackinstallguide.xml:168(date) +msgid "2013-05-02" +msgstr "" + +#: ./doc/install-guide/bk_openstackinstallguide.xml:172(para) +msgid "Updated cover and fixed small errors in appendix." +msgstr "" + +#: ./doc/install-guide/bk_openstackinstallguide.xml:179(date) +msgid "2013-04-30" +msgstr "" + +#: ./doc/install-guide/bk_openstackinstallguide.xml:183(para) +msgid "Grizzly release." +msgstr "" + +#: ./doc/install-guide/bk_openstackinstallguide.xml:189(date) +msgid "2013-04-18" +msgstr "" + +#: ./doc/install-guide/bk_openstackinstallguide.xml:193(para) +msgid "Updates and clean up on the Object Storage installation." +msgstr "" + +#: ./doc/install-guide/bk_openstackinstallguide.xml:200(date) +msgid "2013-04-08" +msgstr "" + +#: ./doc/install-guide/bk_openstackinstallguide.xml:204(para) +msgid "Adds a note about availability of Grizzly packages on Ubuntu and Debian." +msgstr "" + +#: ./doc/install-guide/bk_openstackinstallguide.xml:212(date) +msgid "2013-04-03" +msgstr "" + +#: ./doc/install-guide/bk_openstackinstallguide.xml:216(para) +msgid "Updates RHEL/CentOS/Fedora information for Grizzly release." +msgstr "" + +#: ./doc/install-guide/bk_openstackinstallguide.xml:224(date) +msgid "2013-03-26" +msgstr "" + +#: ./doc/install-guide/bk_openstackinstallguide.xml:228(para) +msgid "Updates Dashboard (Horizon) information for Grizzly release." +msgstr "" + +#: ./doc/install-guide/bk_openstackinstallguide.xml:236(date) +msgid "2013-02-12" +msgstr "" + +#: ./doc/install-guide/bk_openstackinstallguide.xml:240(para) +msgid "Adds chapter about Essex to Folsom upgrade for Compute and related services (excludes OpenStack Object Storage (Swift) and OpenStack Networking (Quantum))." +msgstr "" + +#: ./doc/install-guide/bk_openstackinstallguide.xml:250(date) +msgid "2013-01-16" +msgstr "" + +#: ./doc/install-guide/bk_openstackinstallguide.xml:254(para) +msgid "Fix file copy issue for figures in the /common/ directory." +msgstr "" + +#: ./doc/install-guide/bk_openstackinstallguide.xml:261(date) +msgid "2012-11-09" +msgstr "" + +#: ./doc/install-guide/bk_openstackinstallguide.xml:265(para) +msgid "Folsom release of this document." +msgstr "" + +#: ./doc/install-guide/bk_openstackinstallguide.xml:272(date) +msgid "2012-10-10" +msgstr "" + +#: ./doc/install-guide/bk_openstackinstallguide.xml:276(para) +msgid "Doc bug fixes: 10544591064745" +msgstr "" + +#: ./doc/install-guide/bk_openstackinstallguide.xml:286(date) +msgid "2012-09-26" +msgstr "" + +#: ./doc/install-guide/bk_openstackinstallguide.xml:290(para) +msgid "Adds an all-in-one install section." +msgstr "" + +#: ./doc/install-guide/bk_openstackinstallguide.xml:297(date) +msgid "2012-07-23" +msgstr "" + +#: ./doc/install-guide/bk_openstackinstallguide.xml:301(para) +msgid "Adds additional detail about installing and configuring nova-volumes." +msgstr "" + +#: ./doc/install-guide/bk_openstackinstallguide.xml:306(para) +msgid "Doc bug fixes: 9785101027230" +msgstr "" + +#: ./doc/install-guide/bk_openstackinstallguide.xml:317(date) +msgid "2012-07-17" +msgstr "" + +#: ./doc/install-guide/bk_openstackinstallguide.xml:321(para) +msgid "Update build process so two uniquely-named PDF files are output." +msgstr "" + +#: ./doc/install-guide/bk_openstackinstallguide.xml:329(date) +msgid "2012-07-13" +msgstr "" + +#: ./doc/install-guide/bk_openstackinstallguide.xml:333(para) +msgid "Doc bug fixes: 10258401025847" +msgstr "" + +#: ./doc/install-guide/bk_openstackinstallguide.xml:344(date) +msgid "2012-06-19" +msgstr "" + +#: ./doc/install-guide/bk_openstackinstallguide.xml:348(para) +msgid "Fix PDF links." +msgstr "" + +#: ./doc/install-guide/bk_openstackinstallguide.xml:351(para) +msgid "Doc bug fixes: 967778984959, 1002294, 1010163." +msgstr "" + +#: ./doc/install-guide/bk_openstackinstallguide.xml:367(date) +msgid "2012-05-31" +msgstr "" + +#: ./doc/install-guide/bk_openstackinstallguide.xml:371(para) +msgid "Revise install guide to encompass more Linux distros." +msgstr "" + +#: ./doc/install-guide/bk_openstackinstallguide.xml:375(para) +msgid "Doc bug fixes: 996988, 998116, 999005." +msgstr "" + +#: ./doc/install-guide/bk_openstackinstallguide.xml:387(date) +msgid "2012-05-03" +msgstr "" + +#: ./doc/install-guide/bk_openstackinstallguide.xml:391(para) +msgid "Fixes problems with glance-api-paste.ini and glance-registry-paste.ini samples and instructions." +msgstr "" + +#: ./doc/install-guide/bk_openstackinstallguide.xml:398(para) +msgid "Removes \"DRAFT\" designation." +msgstr "" + +#: ./doc/install-guide/bk_openstackinstallguide.xml:404(date) +msgid "2012-05-02" +msgstr "" + +#: ./doc/install-guide/bk_openstackinstallguide.xml:408(para) +msgid "Essex release." +msgstr "" + +#: ./doc/install-guide/bk_openstackinstallguide.xml:414(date) +msgid "2012-05-01" +msgstr "" + +#: ./doc/install-guide/bk_openstackinstallguide.xml:418(para) +msgid "Updates the Object Storage and Identity (Keystone) configuration." +msgstr "" + +#: ./doc/install-guide/bk_openstackinstallguide.xml:426(date) +msgid "2012-04-25" +msgstr "" + +#: ./doc/install-guide/bk_openstackinstallguide.xml:430(para) +msgid "Changes service_id copy/paste error for the EC2 service-create command." +msgstr "" + +#: ./doc/install-guide/bk_openstackinstallguide.xml:433(para) +msgid "Adds verification steps for Object Storage installation." +msgstr "" + +#: ./doc/install-guide/bk_openstackinstallguide.xml:435(para) +msgid "Fixes proxy-server.conf file so it points to keystone not tempauth." +msgstr "" + +#: ./doc/install-guide/bk_openstackinstallguide.xml:444(date) +msgid "2012-04-23" +msgstr "" + +#: ./doc/install-guide/bk_openstackinstallguide.xml:448(para) +msgid "Adds installation and configuration for multi-node Object Storage service." +msgstr "" + +#: ./doc/install-guide/bk_openstackinstallguide.xml:456(date) +msgid "2012-04-17" +msgstr "" + +#: ./doc/install-guide/bk_openstackinstallguide.xml:460(para) +msgid "Doc bug fixes: 983417, 984106, 984034" +msgstr "" + +#: ./doc/install-guide/bk_openstackinstallguide.xml:472(date) +msgid "2012-04-13" +msgstr "" + +#: ./doc/install-guide/bk_openstackinstallguide.xml:476(para) +msgid "Doc bug fixes: 977905, 980882, 977823, adds additional Glance database preparation steps" +msgstr "" + +#: ./doc/install-guide/bk_openstackinstallguide.xml:490(date) +msgid "2012-04-10" +msgstr "" + +#: ./doc/install-guide/bk_openstackinstallguide.xml:494(para) +msgid "Doc bug fixes: 977831" +msgstr "" + +#: ./doc/install-guide/bk_openstackinstallguide.xml:502(date) +msgid "2012-03-23" +msgstr "" + +#: ./doc/install-guide/bk_openstackinstallguide.xml:506(para) +msgid "Updates for Xen hypervisor." +msgstr "" + +#: ./doc/install-guide/bk_openstackinstallguide.xml:512(date) +msgid "2012-03-09" +msgstr "" + +#: ./doc/install-guide/bk_openstackinstallguide.xml:516(para) +msgid "Updates for Essex release, includes new Glance config files, new Keystone configuration." +msgstr "" + +#: ./doc/install-guide/bk_openstackinstallguide.xml:524(date) +msgid "2012-01-24" +msgstr "" + +#: ./doc/install-guide/bk_openstackinstallguide.xml:528(para) +msgid "Initial draft for Essex." +msgstr "" + +#: ./doc/install-guide/bk_openstackinstallguide.xml:531(para) +msgid "Assumes use of Ubuntu 12.04 repository." +msgstr "" + +#: ./doc/install-guide/bk_openstackinstallguide.xml:540(date) +msgid "2011-01-24" +msgstr "" + +#: ./doc/install-guide/bk_openstackinstallguide.xml:544(para) +msgid "Initial draft for Diablo." +msgstr "" + +#. When image changes, this message will be marked fuzzy or untranslated for you. +#. It doesn't matter what you translate it to: it's not used at all. +#: ./doc/install-guide/section_neutron-install.xml:21(None) +msgid "@@image: 'figures/debconf-screenshots/neutron_1_plugin_selection.png'; md5=adf41c33778a691a560b7098908792db" +msgstr "" + +#. When image changes, this message will be marked fuzzy or untranslated for you. +#. It doesn't matter what you translate it to: it's not used at all. +#: ./doc/install-guide/section_neutron-install.xml:113(None) +msgid "@@image: 'figures/debconf-screenshots/neutron_2_networking_type.png'; md5=0d4d788a44ae0a716a503dca20b82f22" +msgstr "" + +#. When image changes, this message will be marked fuzzy or untranslated for you. +#. It doesn't matter what you translate it to: it's not used at all. +#: ./doc/install-guide/section_neutron-install.xml:122(None) +msgid "@@image: 'figures/debconf-screenshots/neutron_3_hypervisor_ip.png'; md5=2beb543a6334f641d7b69ac5dcbcb3a8" +msgstr "" + +#: ./doc/install-guide/section_neutron-install.xml:8(title) +msgid "Install Networking services" +msgstr "" + +#: ./doc/install-guide/section_neutron-install.xml:9(para) +msgid "When you install a Networking node, you must configure it for API endpoints, RabbitMQ, keystone_authtoken, and the database. Use debconf to configure these values." +msgstr "" + +#: ./doc/install-guide/section_neutron-install.xml:13(para) +msgid "When you install a Networking package, debconf prompts you to choose configuration options including which plug-in to use, as follows:" +msgstr "" + +#: ./doc/install-guide/section_neutron-install.xml:25(para) +msgid "This parameter sets the core_plugin option value in the /etc/neutron/neutron.conf file." +msgstr "" + +#: ./doc/install-guide/section_neutron-install.xml:29(para) +msgid "When you install the neutron-common package, all plug-ins are installed by default." +msgstr "" + +#: ./doc/install-guide/section_neutron-install.xml:32(para) +msgid "This table lists the values for the core_plugin option. These values depend on your response to the debconf prompt." +msgstr "" + +#: ./doc/install-guide/section_neutron-install.xml:36(caption) +msgid "Plug-ins and the core_plugin option" +msgstr "" + +#: ./doc/install-guide/section_neutron-install.xml:39(th) +msgid "Plug-in" +msgstr "" + +#: ./doc/install-guide/section_neutron-install.xml:41(filename) +msgid "neutron.conf" +msgstr "" + +#: ./doc/install-guide/section_neutron-install.xml:40(th) +msgid "core_plugin value in " +msgstr "" + +#: ./doc/install-guide/section_neutron-install.xml:46(para) +msgid "BigSwitch" +msgstr "" + +#: ./doc/install-guide/section_neutron-install.xml:47(para) +msgid "neutron.plugins.bigswitch.plugin.NeutronRestProxyV2" +msgstr "" + +#: ./doc/install-guide/section_neutron-install.xml:50(para) +msgid "Brocade" +msgstr "" + +#: ./doc/install-guide/section_neutron-install.xml:51(para) +msgid "neutron.plugins.brocade.NeutronPlugin.BrocadePluginV2" +msgstr "" + +#: ./doc/install-guide/section_neutron-install.xml:54(para) +msgid "Cisco" +msgstr "" + +#: ./doc/install-guide/section_neutron-install.xml:55(para) +msgid "neutron.plugins.cisco.network_plugin.PluginV2" +msgstr "" + +#: ./doc/install-guide/section_neutron-install.xml:58(para) +msgid "Hyper-V" +msgstr "" + +#: ./doc/install-guide/section_neutron-install.xml:59(para) +msgid "neutron.plugins.hyperv.hyperv_neutron_plugin.HyperVNeutronPlugin" +msgstr "" + +#: ./doc/install-guide/section_neutron-install.xml:62(para) +msgid "LinuxBridge" +msgstr "" + +#: ./doc/install-guide/section_neutron-install.xml:63(para) +msgid "neutron.plugins.linuxbridge.lb_neutron_plugin.LinuxBridgePluginV2" +msgstr "" + +#: ./doc/install-guide/section_neutron-install.xml:66(para) +msgid "Mellanox" +msgstr "" + +#: ./doc/install-guide/section_neutron-install.xml:67(para) +msgid "neutron.plugins.mlnx.mlnx_plugin.MellanoxEswitchPlugin" +msgstr "" + +#: ./doc/install-guide/section_neutron-install.xml:70(para) +msgid "MetaPlugin" +msgstr "" + +#: ./doc/install-guide/section_neutron-install.xml:71(para) +msgid "neutron.plugins.metaplugin.meta_neutron_plugin.MetaPluginV2" +msgstr "" + +#: ./doc/install-guide/section_neutron-install.xml:74(para) +msgid "Midonet" +msgstr "" + +#: ./doc/install-guide/section_neutron-install.xml:75(para) +msgid "neutron.plugins.midonet.plugin.MidonetPluginV2" +msgstr "" + +#: ./doc/install-guide/section_neutron-install.xml:78(para) +msgid "ml2" +msgstr "" + +#: ./doc/install-guide/section_neutron-install.xml:79(para) +msgid "neutron.plugins.ml2.plugin.Ml2Plugin" +msgstr "" + +#: ./doc/install-guide/section_neutron-install.xml:82(para) +msgid "Nec" +msgstr "" + +#: ./doc/install-guide/section_neutron-install.xml:83(para) +msgid "neutron.plugins.nec.nec_plugin.NECPluginV2" +msgstr "" + +#: ./doc/install-guide/section_neutron-install.xml:86(para) +msgid "OpenVSwitch" +msgstr "" + +#: ./doc/install-guide/section_neutron-install.xml:87(para) +msgid "neutron.plugins.openvswitch.ovs_neutron_plugin.OVSNeutronPluginV2" +msgstr "" + +#: ./doc/install-guide/section_neutron-install.xml:90(para) +msgid "PLUMgrid" +msgstr "" + +#: ./doc/install-guide/section_neutron-install.xml:91(para) +msgid "neutron.plugins.plumgrid.plumgrid_nos_plugin.plumgrid_plugin.NeutronPluginPLUMgridV2" +msgstr "" + +#: ./doc/install-guide/section_neutron-install.xml:94(para) +msgid "RYU" +msgstr "" + +#: ./doc/install-guide/section_neutron-install.xml:95(para) +msgid "neutron.plugins.ryu.ryu_neutron_plugin.RyuNeutronPluginV2" +msgstr "" + +#: ./doc/install-guide/section_neutron-install.xml:99(para) +msgid "Depending on the value of core_plugin, the start-up scripts start the daemons by using the corresponding plug-in configuration file directly. For example, if you selected the Open vSwitch plug-in, neutron-server automatically launches with --config-file /etc/neutron/plugins/openvswitch/ovs_neutron_plugin.ini." +msgstr "" + +#: ./doc/install-guide/section_neutron-install.xml:106(para) +msgid "The neutron-common package also prompts you for the default network configuration:" +msgstr "" + +#: ./doc/install-guide/section_neutron-install.xml:126(para) +msgid "Before you configure individual nodes for Networking, you must create the required OpenStack components: user, service, database, and one or more endpoints. After you complete these steps on the controller node, follow the instructions in this guide to set up OpenStack Networking nodes." +msgstr "" + +#. TODO(sross): move this into its own section +#: ./doc/install-guide/section_neutron-install.xml:136(para) +msgid "Use the password that you set previously to log in as root and create a neutron database:" +msgstr "" + +#: ./doc/install-guide/section_neutron-install.xml:146(para) +msgid "Create the required user, service, and endpoint so that Networking can interface with the Identity Service." +msgstr "" + +#: ./doc/install-guide/section_neutron-install.xml:148(para) +msgid "Create a neutron user:" +msgstr "" + +#: ./doc/install-guide/section_neutron-install.xml:149(replaceable) +msgid "neutron@example.com" +msgstr "" + +#: ./doc/install-guide/section_neutron-install.xml:150(para) +msgid "Add the user role to the neutron user:" +msgstr "" + +#: ./doc/install-guide/section_neutron-install.xml:152(para) +msgid "Create the neutron service:" +msgstr "" + +#: ./doc/install-guide/section_neutron-install.xml:155(para) +msgid "Create a Networking endpoint:" +msgstr "" + +#: ./doc/install-guide/section_neutron-install.xml:164(title) +msgid "Install Networking services on a dedicated network node" +msgstr "" + +#: ./doc/install-guide/section_neutron-install.xml:167(para) +msgid "Before you start, set up a machine as a dedicated network node. Dedicated network nodes have a MGMT_INTERFACE NIC, a DATA_INTERFACE NIC, and a EXTERNAL_INTERFACE NIC." +msgstr "" + +#: ./doc/install-guide/section_neutron-install.xml:172(para) +msgid "The management network handles communication among nodes. The data network handles communication coming to and from VMs. The external NIC connects the network node, and optionally to the controller node, so your VMs can connect to the outside world." +msgstr "" + +#: ./doc/install-guide/section_neutron-install.xml:177(para) +msgid "All NICs must have static IPs. However, the data and external NICs have a special set up. For details about Networking plug-ins, see ." +msgstr "" + +#: ./doc/install-guide/section_neutron-install.xml:183(para) +msgid "By default, the system-config-firewall automated firewall configuration tool is in place on RHEL. This graphical interface (and a curses-style interface with -tui on the end of the name) enables you to configure IP tables as a basic firewall. You should disable it when you work with Networking unless you are familiar with the underlying network technologies, as, by default, it blocks various types of network traffic that are important to Networking. To disable it, simply launch the program and clear the Enabled check box." +msgstr "" + +#: ./doc/install-guide/section_neutron-install.xml:193(para) +msgid "After you successfully set up OpenStack Networking, you can re-enable and configure the tool. However, during Networking set up, disable the tool to make it easier to debug network issues." +msgstr "" + +#: ./doc/install-guide/section_neutron-install.xml:200(para) +msgid "Install the Networking packages and any dependencies." +msgstr "" + +#: ./doc/install-guide/section_neutron-install.xml:208(para) +msgid "Respond to prompts for database management, [keystone_authtoken] settings, RabbitMQ credentials and API endpoint registration." +msgstr "" + +#: ./doc/install-guide/section_neutron-install.xml:219(para) +msgid "Configure basic Networking-related services to start at boot time:" +msgstr "" + +#: ./doc/install-guide/section_neutron-install.xml:225(para) +msgid "Enable packet forwarding and disable packet destination filtering so that the network node can coordinate traffic for the VMs. Edit the /etc/sysctl.conf file, as follows:" +msgstr "" + +#: ./doc/install-guide/section_neutron-install.xml:232(para) +msgid "Use the command to ensure the changes made to the /etc/sysctl.conf file take effect:" +msgstr "" + +#: ./doc/install-guide/section_neutron-install.xml:237(para) +msgid "It is recommended that the networking service is restarted after changing values related to the networking configuration. This ensures that all modified values take effect immediately:" +msgstr "" + +#: ./doc/install-guide/section_neutron-install.xml:246(para) ./doc/install-guide/section_neutron-install.xml:839(para) ./doc/install-guide/section_neutron-install.xml:1233(para) +msgid "Configure Networking to use keystone for authentication:" +msgstr "" + +#: ./doc/install-guide/section_neutron-install.xml:249(para) ./doc/install-guide/section_neutron-install.xml:274(para) ./doc/install-guide/section_neutron-install.xml:842(para) ./doc/install-guide/section_neutron-install.xml:1236(para) +msgid "Set the auth_strategy configuration key to keystone in the DEFAULT section of the file:" +msgstr "" + +#: ./doc/install-guide/section_neutron-install.xml:255(para) ./doc/install-guide/section_neutron-install.xml:848(para) ./doc/install-guide/section_neutron-install.xml:1242(para) +msgid "Set the neutron configuration for keystone authentication:" +msgstr "" + +#: ./doc/install-guide/section_neutron-install.xml:270(para) +msgid "To configure neutron to use keystone for authentication, edit the /etc/neutron/neutron.conffile." +msgstr "" + +#: ./doc/install-guide/section_neutron-install.xml:280(para) +msgid "Add these lines to the keystone_authtoken section of the file:" +msgstr "" + +#: ./doc/install-guide/section_neutron-install.xml:293(para) ./doc/install-guide/section_neutron-install.xml:904(para) ./doc/install-guide/section_neutron-install.xml:1352(para) +msgid "Set the root_helper configuration in the [agent] section of /etc/neutron/neutron.conf:" +msgstr "" + +#: ./doc/install-guide/section_neutron-install.xml:310(para) +msgid "Configure the RabbitMQ access. Edit the /etc/neutron/neutron.conf file to modify the following parameters in the DEFAULT section." +msgstr "" + +#: ./doc/install-guide/section_neutron-install.xml:337(para) ./doc/install-guide/section_neutron-install.xml:915(para) +msgid "Configure Networking to connect to the database. Edit the [database] section in the same file, as follows:" +msgstr "" + +#: ./doc/install-guide/section_neutron-install.xml:344(para) ./doc/install-guide/section_neutron-install.xml:933(para) ./doc/install-guide/section_neutron-install.xml:1300(para) +msgid "Configure the /etc/neutron/api-paste.ini file for keystone authentication:" +msgstr "" + +#: ./doc/install-guide/section_neutron-install.xml:360(para) ./doc/install-guide/section_neutron-install.xml:922(para) +msgid "Edit the /etc/neutron/api-paste.ini file and add these lines to the [filter:authtoken] section:" +msgstr "" + +#: ./doc/install-guide/section_neutron-install.xml:371(para) +msgid "keystoneclient.middleware.auth_token: You must configure auth_uri to point to the public identity endpoint. Otherwise, clients might not be able to authenticate against an admin endpoint." +msgstr "" + +#: ./doc/install-guide/section_neutron-install.xml:378(para) +msgid "Configure your network plug-in. For instructions, see instructions. Then, return here." +msgstr "" + +#: ./doc/install-guide/section_neutron-install.xml:383(para) +msgid "Install and configure a networking plug-in. OpenStack Networking uses this plug-in to perform software-defined networking. See for further details. Then, return here when finished." +msgstr "" + +#: ./doc/install-guide/section_neutron-install.xml:389(para) +msgid "Now that you've installed and configured a plug-in, it is time to configure the remaining parts of OpenStack Networking." +msgstr "" + +#: ./doc/install-guide/section_neutron-install.xml:393(para) +msgid "To perform DHCP on the software-defined networks, Networking supports several different plug-ins. However, in general, you use the dnsmasq plug-in." +msgstr "" + +#: ./doc/install-guide/section_neutron-install.xml:396(para) +msgid "Configure the /etc/neutron/dhcp_agent.ini file:" +msgstr "" + +#: ./doc/install-guide/section_neutron-install.xml:405(para) +msgid "To allow virtual machines to access the Compute metadata information, the Networking metadata agent must be enabled and configured. The agent will act as a proxy for the Compute metadata service." +msgstr "" + +#: ./doc/install-guide/section_neutron-install.xml:409(para) +msgid "On the controller, edit the /etc/nova/nova.conf file to define a secret key that will be shared between the Compute Service and the Networking metadata agent." +msgstr "" + +#: ./doc/install-guide/section_neutron-install.xml:413(para) +msgid "Add to the [DEFAULT] section:" +msgstr "" + +#: ./doc/install-guide/section_neutron-install.xml:416(replaceable) ./doc/install-guide/section_neutron-install.xml:422(replaceable) ./doc/install-guide/section_neutron-install.xml:441(replaceable) ./doc/install-guide/section_neutron-install.xml:457(replaceable) +msgid "METADATA_PASS" +msgstr "" + +#: ./doc/install-guide/section_neutron-install.xml:418(para) +msgid "Set the neutron_metadata_proxy_shared_secret key:" +msgstr "" + +#: ./doc/install-guide/section_neutron-install.xml:425(para) +msgid "Restart the nova-api service:" +msgstr "" + +#: ./doc/install-guide/section_neutron-install.xml:429(para) +msgid "On the network node, modify the metadata agent configuration." +msgstr "" + +#: ./doc/install-guide/section_neutron-install.xml:431(para) +msgid "Edit the /etc/neutron/metadata_agent.ini file and modify the [DEFAULT] section:" +msgstr "" + +#: ./doc/install-guide/section_neutron-install.xml:442(para) ./doc/install-guide/section_neutron-install.xml:472(para) +msgid "Set the required keys:" +msgstr "" + +#: ./doc/install-guide/section_neutron-install.xml:459(para) +msgid "The value of auth_region is case-sensitive and must match the endpoint region defined in Keystone." +msgstr "" + +#: ./doc/install-guide/section_neutron-install.xml:464(para) +msgid "If you serve the OpenStack Networking API over HTTPS with self-signed certificates, you must perform additional configuration for the metadata agent because Networking cannot validate the SSL certificates from the service catalog." +msgstr "" + +#: ./doc/install-guide/section_neutron-install.xml:468(para) +msgid "Add this statement to the [DEFAULT] section:" +msgstr "" + +#: ./doc/install-guide/section_neutron-install.xml:477(para) ./doc/install-guide/section_neutron-install.xml:1441(para) +msgid "The neutron-server initialization script expects a symbolic link /etc/neutron/plugin.ini pointing to the configuration file associated with your chosen plug-in. Using Open vSwitch, for example, the symbolic link must point to /etc/neutron/plugins/openvswitch/ovs_neutron_plugin.ini. If this symbolic link does not exist, create it using the following commands:" +msgstr "" + +#: ./doc/install-guide/section_neutron-install.xml:489(para) ./doc/install-guide/section_neutron-install.xml:1453(para) +msgid "The openstack-neutron initialization script expects the variable NEUTRON_PLUGIN_CONF in file /etc/sysconfig/neutron to reference the configuration file associated with your chosen plug-in. Using Open vSwitch, for example, edit the /etc/sysconfig/neutron file and add the following:" +msgstr "" + +#: ./doc/install-guide/section_neutron-install.xml:500(para) +msgid "Restart Networking services." +msgstr "" + +#: ./doc/install-guide/section_neutron-install.xml:510(para) ./doc/install-guide/section_neutron-install.xml:1033(para) +msgid "Also restart your chosen Networking plug-in agent, for example, Open vSwitch." +msgstr "" + +#: ./doc/install-guide/section_neutron-install.xml:516(para) +msgid "After you configure the compute and controller nodes, configure the base networks." +msgstr "" + +#: ./doc/install-guide/section_neutron-install.xml:526(title) +msgid "Install and configure the Networking plug-ins" +msgstr "" + +#: ./doc/install-guide/section_neutron-install.xml:528(title) +msgid "Install the Open vSwitch (OVS) plug-in" +msgstr "" + +#: ./doc/install-guide/section_neutron-install.xml:531(para) ./doc/install-guide/section_neutron-install.xml:1047(para) +msgid "Install the Open vSwitch plug-in and its dependencies:" +msgstr "" + +#: ./doc/install-guide/section_neutron-install.xml:537(para) +msgid "On Ubuntu 12.04 LTS with GRE you must install openvswitch-datapath-dkms and restart the service to enable the GRE flow so that OVS 1.10 and higher is used. Make sure you are running the OVS 1.10 kernel module in addition to the OVS 1.10 user space. Both the kernel module and user space are required for VXLAN support. The error you see in the /var/log/openvswitchovs-vswitchd.log log file is \"Stderr: 'ovs-ofctl: -1: negative values not supported for in_port\\n'\". If you see this error, make sure shows the right version. Also check the output from for the version of the OVS module being loaded." +msgstr "" + +#: ./doc/install-guide/section_neutron-install.xml:554(para) +msgid "Start Open vSwitch:" +msgstr "" + +#: ./doc/install-guide/section_neutron-install.xml:558(para) +msgid "And configure it to start when the system boots:" +msgstr "" + +#: ./doc/install-guide/section_neutron-install.xml:564(para) +msgid "No matter which networking technology you use, you must add the br-int integration bridge, which connects to the VMs, and the br-ex external bridge, which connects to the outside world." +msgstr "" + +#: ./doc/install-guide/section_neutron-install.xml:573(para) +msgid "Add a port (connection) from the EXTERNAL_INTERFACE interface to br-ex interface:" +msgstr "" + +#: ./doc/install-guide/section_neutron-install.xml:576(replaceable) ./doc/install-guide/section_neutron-install.xml:583(replaceable) +msgid "EXTERNAL_INTERFACE" +msgstr "" + +#: ./doc/install-guide/section_neutron-install.xml:578(para) +msgid "The host must have an IP address associated with an interface other than EXTERNAL_INTERFACE, and your remote terminal session must be associated with this other IP address." +msgstr "" + +#: ./doc/install-guide/section_neutron-install.xml:582(para) +msgid "If you associate an IP address with EXTERNAL_INTERFACE, that IP address stops working after you issue the command. If you associate a remote terminal session with that IP address, you lose connectivity with the host." +msgstr "" + +#: ./doc/install-guide/section_neutron-install.xml:586(para) +msgid "For more details about this behavior, see the Configuration Problems section of the Open vSwitch FAQ." +msgstr "" + +#: ./doc/install-guide/section_neutron-install.xml:593(para) +msgid "Configure the EXTERNAL_INTERFACE without an IP address and in promiscuous mode. Additionally, you must set the newly created br-ex interface to have the IP address that formerly belonged to EXTERNAL_INTERFACE." +msgstr "" + +#: ./doc/install-guide/section_neutron-install.xml:600(para) +msgid "Generic Receive Offload (GRO) should not be enabled on this interface as it can cause severe performance problems. It can be disabled with the ethtool utility." +msgstr "" + +#: ./doc/install-guide/section_neutron-install.xml:605(para) +msgid "Edit the /etc/sysconfig/network-scripts/ifcfg-EXTERNAL_INTERFACE file:" +msgstr "" + +#: ./doc/install-guide/section_neutron-install.xml:614(para) +msgid "Create and edit the /etc/sysconfig/network-scripts/ifcfg-br-ex file:" +msgstr "" + +#: ./doc/install-guide/section_neutron-install.xml:627(para) +msgid "You must set some common configuration options no matter which networking technology you choose to use with Open vSwitch. Configure the L3 and DHCP agents to use OVS and namespaces. Edit the /etc/neutron/l3_agent.ini and /etc/neutron/dhcp_agent.ini files, respectively:" +msgstr "" + +#: ./doc/install-guide/section_neutron-install.xml:636(para) +msgid "You must enable veth support if you use certain kernels. Some kernels, such as recent versions of RHEL (not RHOS) and CentOS, only partially support namespaces. Edit the previous files, as follows:" +msgstr "" + +#: ./doc/install-guide/section_neutron-install.xml:644(para) +msgid "Similarly, you must also tell Neutron core to use OVS. Edit the /etc/neutron/neutron.conf file:" +msgstr "" + +#: ./doc/install-guide/section_neutron-install.xml:651(para) +msgid "Choose a networking technology to create the virtual networks. Neutron supports GRE tunneling, VLANs, and VXLANs. This guide shows how to configure GRE tunneling and VLANs." +msgstr "" + +#: ./doc/install-guide/section_neutron-install.xml:655(para) +msgid "GRE tunneling is simpler to set up because it does not require any special configuration from any physical network hardware. However, its protocol makes it difficult to filter traffic on the physical network. Additionally, this configuration does not use namespaces. You can have only one router for each network node. However, you can enable namespacing, and potentially veth, as described in the section detailing how to use VLANs with OVS)." +msgstr "" + +#: ./doc/install-guide/section_neutron-install.xml:666(para) +msgid "On the other hand, VLAN tagging modifies the ethernet header of packets. You can filter packets on the physical network through normal methods. However, not all NICs handle the increased packet size of VLAN-tagged packets well, and you might need to complete additional configuration on physical network hardware to ensure that your Neutron VLANs do not interfere with any other VLANs on your network and that any physical network hardware between nodes does not strip VLAN tags." +msgstr "" + +#: ./doc/install-guide/section_neutron-install.xml:678(para) +msgid "While the examples in this guide enable network namespaces by default, you can disable them if issues occur or your kernel does not support them. Edit the /etc/neutron/l3_agent.ini and /etc/neutron/dhcp_agent.ini files, respectively:" +msgstr "" + +#: ./doc/install-guide/section_neutron-install.xml:685(para) +msgid "Edit the /etc/neutron/neutron.conf file to disable overlapping IP addresses:" +msgstr "" + +#: ./doc/install-guide/section_neutron-install.xml:689(para) +msgid "Note that when network namespaces are disabled, you can have only one router for each network node and overlapping IP addresses are not supported." +msgstr "" + +#: ./doc/install-guide/section_neutron-install.xml:692(para) +msgid "You must complete additional steps after you create the initial Neutron virtual networks and router." +msgstr "" + +#: ./doc/install-guide/section_neutron-install.xml:699(para) +msgid "Configure a firewall plug-in. If you do not wish to enforce firewall rules, called security groups by OpenStack, you can use neutron.agent.firewall.NoopFirewall. Otherwise, you can choose one of the Networking firewall plug-ins. The most common choice is the Hybrid OVS-IPTables driver, but you can also use the Firewall-as-a-Service driver. Edit the /etc/neutron/plugins/openvswitch/ovs_neutron_plugin.ini file:" +msgstr "" + +#: ./doc/install-guide/section_neutron-install.xml:714(para) ./doc/install-guide/section_neutron-install.xml:1108(para) +msgid "You must use at least the No-Op firewall. Otherwise, Horizon and other OpenStack services cannot get and set required VM boot options." +msgstr "" + +#: ./doc/install-guide/section_neutron-install.xml:721(para) ./doc/install-guide/section_neutron-install.xml:1114(para) +msgid "Configure the OVS plug-in to start on boot." +msgstr "" + +#: ./doc/install-guide/section_neutron-install.xml:727(para) ./doc/install-guide/section_neutron-install.xml:1120(para) ./doc/install-guide/section_neutron-install.xml:1147(para) ./doc/install-guide/section_neutron-install.xml:1522(para) ./doc/install-guide/section_neutron-install.xml:1685(para) +msgid "Now, return to the general OVS instructions." +msgstr "" + +#: ./doc/install-guide/section_neutron-install.xml:732(title) +msgid "Configure the Neutron OVS plug-in for GRE tunneling" +msgstr "" + +#: ./doc/install-guide/section_neutron-install.xml:736(para) +msgid "Configure the OVS plug-in to use GRE tunneling, the br-int integration bridge, the br-tun tunneling bridge, and a local IP for the DATA_INTERFACE tunnel IP. Edit the /etc/neutron/plugins/openvswitch/ovs_neutron_plugin.ini file:" +msgstr "" + +#: ./doc/install-guide/section_neutron-install.xml:753(para) ./doc/install-guide/section_neutron-install.xml:1175(para) ./doc/install-guide/section_neutron-install.xml:1542(para) ./doc/install-guide/section_neutron-install.xml:1561(para) +msgid "Return to the general OVS instructions." +msgstr "" + +#: ./doc/install-guide/section_neutron-install.xml:759(title) +msgid "Configure the Neutron OVS plug-in for VLANs" +msgstr "" + +#: ./doc/install-guide/section_neutron-install.xml:763(para) +msgid "Configure OVS to use VLANS. Edit the /etc/neutron/plugins/openvswitch/ovs_neutron_plugin.ini file:" +msgstr "" + +#: ./doc/install-guide/section_neutron-install.xml:773(para) +msgid "Create the bridge for DATA_INTERFACE and add DATA_INTERFACE to it:" +msgstr "" + +#: ./doc/install-guide/section_neutron-install.xml:781(para) +msgid "Transfer the IP address for DATA_INTERFACE to the bridge in the same way that you transferred the EXTERNAL_INTERFACE IP address to br-ex. However, do not turn on promiscuous mode." +msgstr "" + +#: ./doc/install-guide/section_neutron-install.xml:789(para) +msgid "Return to the OVS general instruction." +msgstr "" + +#: ./doc/install-guide/section_neutron-install.xml:798(title) +msgid "Install networking support on a dedicated compute node" +msgstr "" + +#: ./doc/install-guide/section_neutron-install.xml:801(para) +msgid "This section details set up for any node that runs the nova-compute component but does not run the full network stack." +msgstr "" + +#: ./doc/install-guide/section_neutron-install.xml:806(para) ./doc/install-guide/section_neutron-install.xml:1195(para) +msgid "By default, the system-config-firewall automated firewall configuration tool is in place on RHEL. This graphical interface (and a curses-style interface with -tui on the end of the name) enables you to configure IP tables as a basic firewall. You should disable it when you work with Neutron unless you are familiar with the underlying network technologies, as, by default, it blocks various types of network traffic that are important to Neutron. To disable it, simple launch the program and clear the Enabled check box." +msgstr "" + +#: ./doc/install-guide/section_neutron-install.xml:816(para) ./doc/install-guide/section_neutron-install.xml:1205(para) +msgid "After you successfully set up OpenStack with Neutron, you can re-enable and configure the tool. However, during Neutron set up, disable the tool to make it easier to debug network issues." +msgstr "" + +#: ./doc/install-guide/section_neutron-install.xml:823(para) +msgid "Disable packet destination filtering (route verification) to let the networking services route traffic to the VMs. Edit the /etc/sysctl.conf file and run the following command to activate changes:" +msgstr "" + +#: ./doc/install-guide/section_neutron-install.xml:833(para) +msgid "Install and configure your networking plug-in components. To install and configure the network plug-in that you chose when you set up your network node, see ." +msgstr "" + +#: ./doc/install-guide/section_neutron-install.xml:887(para) +msgid "Configure the core components of Neutron. Edit the /etc/neutron/neutron.conf file:" +msgstr "" + +#: ./doc/install-guide/section_neutron-install.xml:947(para) ./doc/install-guide/section_neutron-install.xml:1366(para) +msgid "Configure OpenStack Compute to use OpenStack Networking services. Configure the /etc/nova/nova.conf file as per instructions below:" +msgstr "" + +#: ./doc/install-guide/section_neutron-install.xml:970(para) ./doc/install-guide/section_neutron-install.xml:1389(para) +msgid "Configure OpenStack Compute to use OpenStack Networking services. Edit the /etc/nova/nova.conf file:" +msgstr "" + +#: ./doc/install-guide/section_neutron-install.xml:986(para) +msgid "No matter which firewall driver you chose when you configured the network and compute nodes, you must edit the /etc/nova/nova.conf file to set the firewall driver to nova.virt.firewall.NoopFirewallDriver. Because OpenStack Networking handles the firewall, this statement instructs Compute to not use a firewall." +msgstr "" + +#: ./doc/install-guide/section_neutron-install.xml:996(para) +msgid "If you want Networking to handle the firewall, edit the /etc/neutron/plugins/openvswitch/ovs_neutron_plugin.ini file to set the firewall_driver option to the firewall for the plug-in. For example, with OVS, edit the file as follows:" +msgstr "" + +#: ./doc/install-guide/section_neutron-install.xml:1011(para) +msgid "If you do not want to use a firewall in Compute or Networking, edit both configuration files and set firewall_driver=nova.virt.firewall.NoopFirewallDriver. Also, edit the /etc/nova/nova.conf file and comment out or remove the security_group_api=neutron statement." +msgstr "" + +#: ./doc/install-guide/section_neutron-install.xml:1019(para) +msgid "Otherwise, when you issue commands, the ERROR: The server has either erred or is incapable of performing the requested operation. (HTTP 500) error might be returned." +msgstr "" + +#: ./doc/install-guide/section_neutron-install.xml:1029(para) ./doc/install-guide/section_nova-compute.xml:239(para) +msgid "Restart the Compute service." +msgstr "" + +#: ./doc/install-guide/section_neutron-install.xml:1040(title) +msgid "Install and configure Neutron plug-ins on a dedicated compute node" +msgstr "" + +#: ./doc/install-guide/section_neutron-install.xml:1043(title) +msgid "Install the Open vSwitch (OVS) plug-in on a dedicated compute node" +msgstr "" + +#: ./doc/install-guide/section_neutron-install.xml:1054(para) +msgid "Restart Open vSwitch:" +msgstr "" + +#: ./doc/install-guide/section_neutron-install.xml:1058(para) +msgid "Start Open vSwitch and configure it to start when the system boots:" +msgstr "" + +#: ./doc/install-guide/section_neutron-install.xml:1066(para) +msgid "You must set some common configuration options no matter which networking technology you choose to use with Open vSwitch. You must add the br-int integration bridge, which connects to the VMs." +msgstr "" + +#: ./doc/install-guide/section_neutron-install.xml:1074(para) +msgid "You must set some common configuration options. You must configure Networking core to use OVS. Edit the /etc/neutron/neutron.conf file:" +msgstr "" + +#: ./doc/install-guide/section_neutron-install.xml:1086(para) +msgid "Configure the networking type that you chose when you set up the network node: either GRE tunneling or VLANs." +msgstr "" + +#: ./doc/install-guide/section_neutron-install.xml:1095(para) +msgid "You must configure a firewall as well. You should use the same firewall plug-in that you chose to use when you set up the network node. To do this, edit /etc/neutron/plugins/openvswitch/ovs_neutron_plugin.ini file and set the firewall_driver value under the securitygroup to the same value used on the network node. For instance, if you chose to use the Hybrid OVS-IPTables plug-in, your configuration looks like this:" +msgstr "" + +#: ./doc/install-guide/section_neutron-install.xml:1126(title) +msgid "Configure the Neutron OVS plug-in for GRE tunneling on a dedicated compute node" +msgstr "" + +#: ./doc/install-guide/section_neutron-install.xml:1130(para) +msgid "Tell the OVS plug-in to use GRE tunneling with a br-int integration bridge, a br-tun tunneling bridge, and a local IP for the tunnel of DATA_INTERFACE's IP Edit the /etc/neutron/plugins/openvswitch/ovs_neutron_plugin.ini file:" +msgstr "" + +#: ./doc/install-guide/section_neutron-install.xml:1144(replaceable) +msgid "DATA_INTERFACE_IP" +msgstr "" + +#: ./doc/install-guide/section_neutron-install.xml:1154(title) +msgid "Configure the Neutron OVS plug-in for VLANs on a dedicated compute node" +msgstr "" + +#: ./doc/install-guide/section_neutron-install.xml:1158(para) +msgid "Tell OVS to use VLANs. Edit the /etc/neutron/plugins/openvswitch/ovs_neutron_plugin.ini file:" +msgstr "" + +#: ./doc/install-guide/section_neutron-install.xml:1164(replaceable) +msgid "DATA_INTERFACE" +msgstr "" + +#: ./doc/install-guide/section_neutron-install.xml:1167(para) +msgid "Create the bridge for the DATA_INTERFACE and add DATA_INTERFACE to it, the same way you did on the network node:" +msgstr "" + +#: ./doc/install-guide/section_neutron-install.xml:1184(title) +msgid "Install networking support on a dedicated controller node" +msgstr "" + +#: ./doc/install-guide/section_neutron-install.xml:1187(para) +msgid "This is for a node which runs the control components of Neutron, but does not run any of the components that provide the underlying functionality (such as the plug-in agent or the L3 agent). If you wish to have a combined controller/compute node follow these instructions, and then those for the compute node." +msgstr "" + +#: ./doc/install-guide/section_neutron-install.xml:1212(para) +msgid "Install the server component of Networking and any dependencies." +msgstr "" + +#: ./doc/install-guide/section_neutron-install.xml:1223(para) +msgid "Configure Networking to use your MySQL database. Edit the /etc/neutron/neutron.conf file and add the following key under the [database] section. Replace NEUTRON_DBPASS with the password you chose for the Neutron database." +msgstr "" + +#: ./doc/install-guide/section_neutron-install.xml:1257(para) +msgid "Configure Networking to use keystone as the Identity Service for authentication." +msgstr "" + +#: ./doc/install-guide/section_neutron-install.xml:1261(para) +msgid "Edit the /etc/neutron/neutron.conf file and add the following key under the [DEFAULT] section." +msgstr "" + +#: ./doc/install-guide/section_neutron-install.xml:1268(para) +msgid "Add the following keys under the [keystone_authtoken] section. Replace NEUTRON_PASS with the password you chose for the Neutron user in Keystone." +msgstr "" + +#: ./doc/install-guide/section_neutron-install.xml:1285(para) +msgid "Edit the /etc/neutron/api-paste.ini file and add the following keys under the [filter:authtoken] section. Replace NEUTRON_PASS with the password you chose for the Neutron user in Keystone." +msgstr "" + +#: ./doc/install-guide/section_neutron-install.xml:1338(para) +msgid "Configure Networking to use your message broker. Edit the /etc/neutron/neutron.conf file and add the following keys under the [DEFAULT] section." +msgstr "" + +#: ./doc/install-guide/section_neutron-install.xml:1342(para) +msgid "Replace RABBIT_PASS with the password you chose for RabbitMQ." +msgstr "" + +#: ./doc/install-guide/section_neutron-install.xml:1358(para) +msgid "Although the controller node does not run any Networking agents, you must install and configure the same plug-in that you configured on the network node." +msgstr "" + +#: ./doc/install-guide/section_neutron-install.xml:1361(link) +msgid "Install and configure the Networking plug-ins on a dedicated controller node" +msgstr "" + +#: ./doc/install-guide/section_neutron-install.xml:1405(para) +msgid "Regardless of which firewall driver you chose when you configured the network and compute nodes, set this driver as the No-Op firewall. This firewall is a nova firewall, and because neutron handles the Firewall, you must tell nova not to use one." +msgstr "" + +#: ./doc/install-guide/section_neutron-install.xml:1412(para) +msgid "When Networking handles the firewall, the option firewall_driver should be set according to the specified plug-in. For example with OVS, edit the /etc/neutron/plugins/openvswitch/ovs_neutron_plugin.ini file:" +msgstr "" + +#: ./doc/install-guide/section_neutron-install.xml:1426(para) +msgid "If you do not want to use a firewall in Compute or Networking, set firewall_driver=nova.virt.firewall.NoopFirewallDriver in both config files, and comment out or remove security_group_api=neutron in the /etc/nova/nova.conf file, otherwise you may encounter ERROR: The server has either erred or is incapable of performing the requested operation. (HTTP 500) when issuing commands." +msgstr "" + +#: ./doc/install-guide/section_neutron-install.xml:1464(para) +msgid "Restart the Compute and Networking services:" +msgstr "" + +#: ./doc/install-guide/section_neutron-install.xml:1471(para) +msgid "Restart the Compute services:" +msgstr "" + +#: ./doc/install-guide/section_neutron-install.xml:1477(para) +msgid "Start the Networking service and configure it to start when the system boots:" +msgstr "" + +#: ./doc/install-guide/section_neutron-install.xml:1486(title) +msgid "Install and configure the Neutron plug-ins on a dedicated controller node" +msgstr "" + +#: ./doc/install-guide/section_neutron-install.xml:1489(title) +msgid "Install the Open vSwitch (OVS) plug-in on a dedicated controller node" +msgstr "" + +#: ./doc/install-guide/section_neutron-install.xml:1493(para) +msgid "Install the Open vSwitch plug-in:" +msgstr "" + +#: ./doc/install-guide/section_neutron-install.xml:1499(para) +msgid "You must set some common configuration options no matter which networking technology you choose to use with Open vSwitch. You must configure Networking core to use OVS. Edit the /etc/neutron/neutron.conf file:" +msgstr "" + +#: ./doc/install-guide/section_neutron-install.xml:1508(para) +msgid "Configure the OVS plug-in for the networking type that you chose when you configured the network node: GRE tunneling or VLANs." +msgstr "" + +#: ./doc/install-guide/section_neutron-install.xml:1517(para) +msgid "The dedicated controller node does not need to run Open vSwitch or the Open vSwitch agent." +msgstr "" + +#: ./doc/install-guide/section_neutron-install.xml:1528(title) +msgid "Configure the Neutron OVS plug-in for GRE tunneling on a dedicated controller node" +msgstr "" + +#: ./doc/install-guide/section_neutron-install.xml:1532(para) +msgid "Tell the OVS plug-in to use GRE tunneling. Edit the /etc/neutron/plugins/openvswitch/ovs_neutron_plugin.ini file:" +msgstr "" + +#: ./doc/install-guide/section_neutron-install.xml:1549(title) +msgid "Configure the Neutron OVS plug-in for VLANs on a dedicated controller node" +msgstr "" + +#: ./doc/install-guide/section_neutron-install.xml:1553(para) +msgid "Tell OVS to use VLANS. Edit the /etc/neutron/plugins/openvswitch/ovs_neutron_plugin.ini file, as follows:" +msgstr "" + +#: ./doc/install-guide/section_neutron-install.xml:1570(title) +msgid "Create the base Neutron networks" +msgstr "" + +#: ./doc/install-guide/section_neutron-install.xml:1572(para) +msgid "In these sections, replace SPECIAL_OPTIONS with any options specific to your Networking plug-in choices. See here to check if your plug-in requires any special options." +msgstr "" + +#: ./doc/install-guide/section_neutron-install.xml:1581(para) +msgid "Create the ext-net external network. This network represents a slice of the outside world. VMs are not directly linked to this network; instead, they connect to internal networks. Outgoing traffic is routed by Neutron to the external network. Additionally, floating IP addresses from the subnet for ext-net might be assigned to VMs so that the external network can contact them. Neutron routes the traffic appropriately." +msgstr "" + +#: ./doc/install-guide/section_neutron-install.xml:1590(replaceable) ./doc/install-guide/section_neutron-install.xml:1635(replaceable) +msgid "SPECIAL_OPTIONS" +msgstr "" + +#: ./doc/install-guide/section_neutron-install.xml:1593(para) +msgid "Create the associated subnet with the same gateway and CIDR as EXTERNAL_INTERFACE. It does not have DHCP because it represents a slice of the external world:" +msgstr "" + +#: ./doc/install-guide/section_neutron-install.xml:1598(replaceable) +msgid "FLOATING_IP_START" +msgstr "" + +#: ./doc/install-guide/section_neutron-install.xml:1598(replaceable) +msgid "FLOATING_IP_END" +msgstr "" + +#: ./doc/install-guide/section_neutron-install.xml:1599(replaceable) +msgid "EXTERNAL_INTERFACE_GATEWAY" +msgstr "" + +#: ./doc/install-guide/section_neutron-install.xml:1600(replaceable) +msgid "EXTERNAL_INTERFACE_CIDR" +msgstr "" + +#: ./doc/install-guide/section_neutron-install.xml:1603(para) +msgid "Create one or more initial tenants, for example:" +msgstr "" + +#: ./doc/install-guide/section_neutron-install.xml:1604(replaceable) ./doc/install-guide/section_neutron-install.xml:1619(replaceable) +msgid "DEMO_TENANT" +msgstr "" + +#: ./doc/install-guide/section_neutron-install.xml:1605(para) +msgid "See for further details." +msgstr "" + +#: ./doc/install-guide/section_neutron-install.xml:1607(para) +msgid "See for further details." +msgstr "" + +#: ./doc/install-guide/section_neutron-install.xml:1611(para) +msgid "Create the router attached to the external network. This router routes traffic to the internal subnets as appropriate. You can create it under a given tenant: Append --tenant-id option with a value of DEMO_TENANT_ID to the command." +msgstr "" + +#: ./doc/install-guide/section_neutron-install.xml:1617(para) +msgid "Use the following to quickly get the DEMO_TENANT tenant-id:" +msgstr "" + +#: ./doc/install-guide/section_neutron-install.xml:1620(para) +msgid "Then create the router:" +msgstr "" + +#: ./doc/install-guide/section_neutron-install.xml:1621(replaceable) ./doc/install-guide/section_neutron-install.xml:1635(replaceable) ./doc/install-guide/section_neutron-install.xml:1636(replaceable) +msgid "DEMO_TENANT_ID" +msgstr "" + +#: ./doc/install-guide/section_neutron-install.xml:1624(para) +msgid "Connect the router to ext-net by setting the gateway for the router as ext-net:" +msgstr "" + +#: ./doc/install-guide/section_neutron-install.xml:1627(replaceable) ./doc/install-guide/section_neutron-install.xml:1637(replaceable) ./doc/install-guide/section_neutron-install.xml:1668(replaceable) +msgid "EXT_TO_INT_ID" +msgstr "" + +#: ./doc/install-guide/section_neutron-install.xml:1627(replaceable) ./doc/install-guide/section_neutron-install.xml:1667(replaceable) +msgid "EXT_NET_ID" +msgstr "" + +#: ./doc/install-guide/section_neutron-install.xml:1630(para) +msgid "Create an internal network for DEMO_TENANT (and associated subnet over an arbitrary internal IP range, such as, 10.5.5.0/24), and connect it to the router by setting it as a port:" +msgstr "" + +#: ./doc/install-guide/section_neutron-install.xml:1637(replaceable) +msgid "DEMO_NET_SUBNET_ID" +msgstr "" + +#: ./doc/install-guide/section_neutron-install.xml:1640(para) +msgid "Check the special options page for your plug-in for remaining steps. Now, return to the general OVS instructions." +msgstr "" + +#: ./doc/install-guide/section_neutron-install.xml:1647(title) +msgid "Plug-in-specific Neutron network options" +msgstr "" + +#: ./doc/install-guide/section_neutron-install.xml:1650(title) +msgid "Open vSwitch Network configuration options" +msgstr "" + +#: ./doc/install-guide/section_neutron-install.xml:1653(title) +msgid "GRE tunneling network options" +msgstr "" + +#: ./doc/install-guide/section_neutron-install.xml:1655(para) +msgid "While this guide currently enables network namespaces by default, you can disable them if you have issues or your kernel does not support them. If you disabled namespaces, you must perform some additional configuration for the L3 agent." +msgstr "" + +#: ./doc/install-guide/section_neutron-install.xml:1660(para) +msgid "After you create all the networks, tell the L3 agent what the external network ID is, as well as the ID of the router associated with this machine (because you are not using namespaces, there can be only one router for each machine). To do this, edit the /etc/neutron/l3_agent.ini file:" +msgstr "" + +#: ./doc/install-guide/section_neutron-install.xml:1669(para) +msgid "Then, restart the L3 agent:" +msgstr "" + +#: ./doc/install-guide/section_neutron-install.xml:1672(para) +msgid "When creating networks, you should use the options:" +msgstr "" + +#: ./doc/install-guide/section_neutron-install.xml:1675(para) +msgid "SEG_ID should be 2 for the external network, and just any unique number inside the tunnel range specified before for any other network." +msgstr "" + +#: ./doc/install-guide/section_neutron-install.xml:1680(para) +msgid "These options are not needed beyond the first network, as Neutron automatically increments the segmentation id and copy the network type option for any additional networks." +msgstr "" + +#: ./doc/install-guide/section_neutron-install.xml:1690(title) +msgid "VLAN network options" +msgstr "" + +#: ./doc/install-guide/section_neutron-install.xml:1691(para) +msgid "When creating networks, use these options:" +msgstr "" + +#: ./doc/install-guide/section_neutron-install.xml:1693(para) +msgid "SEG_ID should be 2 for the external network, and just any unique number inside the vlan range specified above for any other network." +msgstr "" + +#: ./doc/install-guide/section_neutron-install.xml:1698(para) +msgid "These options are not needed beyond the first network, as Neutron automatically increments the segmentation ID and copies the network type and physical network options for any additional networks. They are only needed if you wish to modify those values in any way." +msgstr "" + +#: ./doc/install-guide/section_neutron-install.xml:1706(para) +msgid "Some NICs have Linux drivers that do not handle VLANs properly. See the ovs-vlan-bug-workaround and ovs-vlan-test man pages for more information. Additionally, you might try turning off rx-vlan-offload and tx-vlan-offload by using ethtool on the DATA_INTERFACE. Another potential caveat to VLAN functionality is that VLAN tags add an additional 4 bytes to the packet size. If your NICs cannot handle large packets, make sure to set the MTU to a value that is 4 bytes less than the normal value on the DATA_INTERFACE." +msgstr "" + +#: ./doc/install-guide/section_neutron-install.xml:1721(para) +msgid "If you run OpenStack inside a virtualized environment (for testing purposes), switching to the virtio NIC type (or a similar technology if you are not using KVM/QEMU to run your host VMs) might solve the issue." +msgstr "" + +#: ./doc/install-guide/ch_debconf.xml:6(title) +msgid "Configure OpenStack with debconf" +msgstr "" + +#. When image changes, this message will be marked fuzzy or untranslated for you. +#. It doesn't matter what you translate it to: it's not used at all. +#: ./doc/install-guide/ch_overview.xml:61(None) +msgid "@@image: 'figures/basic-architecture.svg'; md5=33d7a8c99d42020ff657f85d80cc06bd" +msgstr "" + +#: ./doc/install-guide/ch_overview.xml:6(title) +msgid "Architecture" +msgstr "" + +#: ./doc/install-guide/ch_overview.xml:7(para) +msgid "This install guide offers a few of the many ways to install OpenStack components and have them work together. It is meant as a \"choose your own adventure\" guide, not a comprehensive guide. The OpenStack Configuration Reference lists every option in all OpenStack services. Before you begin an installation adventure, here are some things you should know about OpenStack concepts." +msgstr "" + +#: ./doc/install-guide/ch_overview.xml:25(title) +msgid "Example architectures" +msgstr "" + +#: ./doc/install-guide/ch_overview.xml:26(para) +msgid "This guide enables you to choose your own OpenStack adventure. OpenStack is highly configurable to meet different needs with various compute, networking, and storage options." +msgstr "" + +#: ./doc/install-guide/ch_overview.xml:29(para) +msgid "This guide uses the following example architectures:" +msgstr "" + +#: ./doc/install-guide/ch_overview.xml:32(para) ./doc/install-guide/ch_overview.xml:57(title) +msgid "Basic architecture with legacy networking" +msgstr "" + +#: ./doc/install-guide/ch_overview.xml:35(para) +msgid "The controller node runs the Identity Service, Image Service, dashboard, and management portion of Compute. It also contains the associated API services, MySQL databases, and messaging system." +msgstr "" + +#: ./doc/install-guide/ch_overview.xml:41(para) +msgid "The compute node runs the hypervisor portion of Compute, which operates tenant virtual machines. By default, Compute uses KVM as the hypervisor. Compute also provisions and operates tenant networks and implements security groups. You can run more than one compute node." +msgstr "" + +#: ./doc/install-guide/ch_overview.xml:52(para) +msgid "When implementing this architecture, skip ." +msgstr "" + +#: ./doc/install-guide/ch_overview.xml:67(para) ./doc/install-guide/ch_overview.xml:97(title) +msgid "Basic architecture with OpenStack Networking (Neutron)" +msgstr "" + +#: ./doc/install-guide/ch_overview.xml:70(para) +msgid "The controller node runs the Identity Service, Image Service, dashboard, and management portions of Compute and Networking. It also contains the associated API services, MySQL databases, and messaging system." +msgstr "" + +#: ./doc/install-guide/ch_overview.xml:76(para) +msgid "The network node runs the Networking plug-in agent and several layer 3 agents that provision tenant networks and provide services to them, including routing, NAT, and DHCP. It also handles external (internet) connectivity for tenant virtual machines." +msgstr "" + +#: ./doc/install-guide/ch_overview.xml:85(para) +msgid "The compute node runs the hypervisor portion of Compute, which operates tenant virtual machines. By default, Compute uses KVM as the hypervisor. The compute node also runs the Networking plug-in agent, which operates tenant networks and implements security groups. You can run more than one compute node." +msgstr "" + +#: ./doc/install-guide/ch_overview.xml:92(para) +msgid "When implementing this architecture, skip ." +msgstr "" + +#: ./doc/install-guide/ch_overview.xml:107(para) +msgid "You can add nodes that run Block Storage or Object Storage to either of these architectures." +msgstr "" + +#: ./doc/install-guide/section_dashboard-install.xml:13(title) +msgid "Install the dashboard" +msgstr "" + +#: ./doc/install-guide/section_dashboard-install.xml:14(para) +msgid "Before you can install and configure the dashboard, meet the requirements in ." +msgstr "" + +#: ./doc/install-guide/section_dashboard-install.xml:18(para) +msgid "When you install only Object Storage and the Identity Service, even if you install the dashboard, it does not pull up projects and is unusable." +msgstr "" + +#: ./doc/install-guide/section_dashboard-install.xml:22(para) +msgid "For more information about how to deploy the dashboard, see deployment topics in the developer documentation." +msgstr "" + +#: ./doc/install-guide/section_dashboard-install.xml:28(para) +msgid "Install the dashboard on the node that can contact the Identity Service as root:" +msgstr "" + +#: ./doc/install-guide/section_dashboard-install.xml:34(title) +msgid "Note for Ubuntu users" +msgstr "" + +#: ./doc/install-guide/section_dashboard-install.xml:36(para) +msgid "Remove the openstack-dashboard-ubuntu-theme package. This theme prevents translations, several menus as well as the network map from rendering correctly: " +msgstr "" + +#: ./doc/install-guide/section_dashboard-install.xml:45(title) +msgid "Note for Debian users" +msgstr "" + +#: ./doc/install-guide/section_dashboard-install.xml:46(para) +msgid "To install the Apache package:" +msgstr "" + +#: ./doc/install-guide/section_dashboard-install.xml:48(para) +msgid "This command installs and configures Apache correctly, provided that the user asks for it during the debconf prompts. The default SSL certificate is self-signed, and it is probably wise to have it signed by a root Certificate Authority (CA)." +msgstr "" + +#: ./doc/install-guide/section_dashboard-install.xml:57(para) +msgid "Modify the value of CACHES['default']['LOCATION'] in /etc/openstack-dashboard/local_settings.py/etc/openstack-dashboard/local_settings/usr/share/openstack-dashboard/openstack_dashboard/local/local_settings.py to match the ones set in /etc/memcached.conf/etc/sysconfig/memcached." +msgstr "" + +#: ./doc/install-guide/section_dashboard-install.xml:69(para) +msgid "Open /etc/openstack-dashboard/local_settings.py/etc/openstack-dashboard/local_settings and look for this line:" +msgstr "" + +#: ./doc/install-guide/section_dashboard-install.xml:82(title) ./doc/install-guide/object-storage/section_object-storage-sys-requirements.xml:25(td) +msgid "Notes" +msgstr "" + +#: ./doc/install-guide/section_dashboard-install.xml:85(para) +msgid "The address and port must match the ones set in /etc/memcached.conf/etc/sysconfig/memcached." +msgstr "" + +#: ./doc/install-guide/section_dashboard-install.xml:90(para) +msgid "If you change the memcached settings, you must restart the Apache web server for the changes to take effect." +msgstr "" + +#: ./doc/install-guide/section_dashboard-install.xml:95(para) +msgid "You can use options other than memcached option for session storage. Set the session back-end through the SESSION_ENGINE option." +msgstr "" + +#: ./doc/install-guide/section_dashboard-install.xml:102(para) +msgid "To change the timezone, use the dashboard or edit the /etc/openstack-dashboard/local_settings/etc/openstack-dashboard/local_settings.py/usr/share/openstack-dashboard/openstack_dashboard/local/local_settings.py file." +msgstr "" + +#: ./doc/install-guide/section_dashboard-install.xml:111(para) +msgid "Change the following parameter: TIME_ZONE = \"UTC\"" +msgstr "" + +#: ./doc/install-guide/section_dashboard-install.xml:118(para) +msgid "Update the ALLOWED_HOSTS in local_settings.py to include the addresses you wish to access the dashboard from." +msgstr "" + +#: ./doc/install-guide/section_dashboard-install.xml:122(para) +msgid "Edit /etc/openstack-dashboard/local_settings/etc/openstack-dashboard/local_settings.py/usr/share/openstack-dashboard/openstack_dashboard/local/local_settings.py:" +msgstr "" + +#: ./doc/install-guide/section_dashboard-install.xml:132(para) +msgid "This guide assumes that you are running the Dashboard on the controller node. You can easily run the dashboard on a separate server, by changing the appropriate settings in local_settings.py." +msgstr "" + +#: ./doc/install-guide/section_dashboard-install.xml:137(para) +msgid "Edit /etc/openstack-dashboard/local_settings/etc/openstack-dashboard/local_settings.py/usr/share/openstack-dashboard/openstack_dashboard/local/local_settings.py and change OPENSTACK_HOST to the hostname of your Identity Service:" +msgstr "" + +#: ./doc/install-guide/section_dashboard-install.xml:149(para) +msgid "Setup Apache configuration: " +msgstr "" + +#: ./doc/install-guide/section_dashboard-install.xml:156(para) +msgid "By default, the openstack-dashboard package enables a database as session store. Before you continue, either change the session store set up as described in or finish the setup of the database session store as explained in ." +msgstr "" + +#: ./doc/install-guide/section_dashboard-install.xml:166(para) +msgid "Start the Apache web server and memcached:" +msgstr "" + +#: ./doc/install-guide/section_dashboard-install.xml:179(para) +msgid "You can now access the dashboard at http://controller/horizonhttps://controller/http://controller/dashboardhttp://controller." +msgstr "" + +#: ./doc/install-guide/section_dashboard-install.xml:186(para) +msgid "Login with credentials for any user that you created with the OpenStack Identity Service." +msgstr "" + +#: ./doc/install-guide/section_heat-install.xml:5(title) +msgid "Install the Orchestration service" +msgstr "" + +#: ./doc/install-guide/section_heat-install.xml:8(para) ./doc/install-guide/section_heat-install.xml:24(para) +msgid "Install the OpenStack Orchestration service on the controller node:" +msgstr "" + +#: ./doc/install-guide/section_heat-install.xml:13(para) +msgid "Respond to prompts for database management, [keystone_authtoken] settings, RabbitMQ credentials and API endpoint registration." +msgstr "" + +#: ./doc/install-guide/section_heat-install.xml:33(para) +msgid "In the configuration file, specify the location of the database where the Orchestration service stores data. These examples use a MySQL database with a heat user on the controller node. Replace HEAT_DBPASS with the password for the database user:" +msgstr "" + +#: ./doc/install-guide/section_heat-install.xml:40(replaceable) ./doc/install-guide/section_heat-install.xml:46(replaceable) ./doc/install-guide/section_heat-install.xml:61(replaceable) ./doc/install-guide/section_heat-install.xml:63(replaceable) +msgid "HEAT_DBPASS" +msgstr "" + +#: ./doc/install-guide/section_heat-install.xml:41(para) +msgid "Edit /etc/heat/heat.conf and change the [DEFAULT] section." +msgstr "" + +#: ./doc/install-guide/section_heat-install.xml:50(para) +msgid "By default, the Ubuntu packages create an SQLite database. Delete the heat.sqlite file that was created in the /var/lib/heat/ directory so that it does not get used by mistake." +msgstr "" + +#: ./doc/install-guide/section_heat-install.xml:56(para) +msgid "Use the password that you set previously to log in as root and create a heat database user:" +msgstr "" + +#: ./doc/install-guide/section_heat-install.xml:66(para) +msgid "Create the heat service tables:" +msgstr "" + +#: ./doc/install-guide/section_heat-install.xml:69(para) +msgid "Ignore DeprecationWarning errors." +msgstr "" + +#: ./doc/install-guide/section_heat-install.xml:74(para) +msgid "The Ubuntu packages do not correctly set up logging. Edit the /etc/heat/heat.conf file and change the [DEFAULT] section:" +msgstr "" + +#: ./doc/install-guide/section_heat-install.xml:88(para) +msgid "Configure the Orchestration Service to use the RabbitMQ message broker." +msgstr "" + +#: ./doc/install-guide/section_heat-install.xml:90(para) +msgid "Edit /etc/heat/heat.conf and modify the [DEFAULT] section:" +msgstr "" + +#: ./doc/install-guide/section_heat-install.xml:99(para) +msgid "Create a heat user that the Orchestration service can use to authenticate with the Identity Service. Use the service tenant and give the user the admin role:" +msgstr "" + +#: ./doc/install-guide/section_heat-install.xml:103(replaceable) ./doc/install-guide/section_heat-install.xml:119(replaceable) +msgid "HEAT_PASS" +msgstr "" + +#: ./doc/install-guide/section_heat-install.xml:104(replaceable) +msgid "heat@example.com" +msgstr "" + +#: ./doc/install-guide/section_heat-install.xml:108(para) +msgid "Edit the /etc/heat/heat.conf file to change the [keystone_authtoken] and [ec2_authtoken] sections to add credentials to the Orchestration Service:" +msgstr "" + +#: ./doc/install-guide/section_heat-install.xml:125(para) +msgid "Register the Heat and CloudFormation APIs with the Identity Service so that other OpenStack services can locate these APIs. Register the service and specify the endpoint:" +msgstr "" + +#: ./doc/install-guide/section_heat-install.xml:151(para) +msgid "Start the heat-api, heat-api-cfn and heat-engine services and configure them to start when the system boots:" +msgstr "" + +#: ./doc/install-guide/section_ceilometer-nova.xml:7(title) +msgid "Install the Compute agent for the Telemetry service" +msgstr "" + +#: ./doc/install-guide/section_ceilometer-nova.xml:9(para) +msgid "OpenStack Telemetry is an API service that provides a collector and a range of disparate agents. This procedure details how to install the agent that runs on the compute node." +msgstr "" + +#: ./doc/install-guide/section_ceilometer-nova.xml:14(para) +msgid "Install the Telemetry service on the Compute node:" +msgstr "" + +#: ./doc/install-guide/section_ceilometer-nova.xml:20(para) +msgid "Set the following options in the /etc/nova/nova.conf file:" +msgstr "" + +#: ./doc/install-guide/section_ceilometer-nova.xml:30(para) +msgid "The option is a multi valued option, which openstack-config cannot set properly. See ." +msgstr "" + +#: ./doc/install-guide/section_ceilometer-nova.xml:36(para) +msgid "Edit the /etc/nova/nova.conf file and add the following lines to the [DEFAULT] section:" +msgstr "" + +#: ./doc/install-guide/section_ceilometer-nova.xml:53(para) +msgid "Restart the Compute service:" +msgstr "" + +#: ./doc/install-guide/section_ceilometer-nova.xml:58(para) +msgid "You must set the secret key that you defined previously. The Telemetry service nodes share this key as a shared secret:" +msgstr "" + +#: ./doc/install-guide/section_ceilometer-nova.xml:62(para) +msgid "Edit the /etc/ceilometer/ceilometer.conf file and change these lines in the [DEFAULT] section. Replace CEILOMETER_TOKEN with the ceilometer token that you created previously:" +msgstr "" + +#: ./doc/install-guide/section_ceilometer-nova.xml:83(para) +msgid "Configure the QPid access:" +msgstr "" + +#: ./doc/install-guide/section_ceilometer-nova.xml:88(para) +msgid "Add the Identity service credentials:" +msgstr "" + +#: ./doc/install-guide/section_ceilometer-nova.xml:140(para) +msgid "Start the service and configure it to start when the system boots:" +msgstr "" + +#: ./doc/install-guide/section_neutron-deploy-use-cases.xml:6(title) +msgid "Neutron deployment use cases" +msgstr "" + +#: ./doc/install-guide/section_neutron-deploy-use-cases.xml:7(para) +msgid "This section describes how to configure the Networking service and its components for some typical use cases." +msgstr "" + +#: ./doc/install-guide/section_nova-compute.xml:5(title) +msgid "Configure a Compute node" +msgstr "" + +#: ./doc/install-guide/section_nova-compute.xml:6(para) +msgid "After you configure the Compute service on the controller node, you must configure another system as a Compute node. The Compute node receives requests from the controller node and hosts virtual machine instances. You can run all services on a single node, but the examples in this guide use separate systems. This makes it easy to scale horizontally by adding additional Compute nodes following the instructions in this section." +msgstr "" + +#: ./doc/install-guide/section_nova-compute.xml:13(para) +msgid "The Compute service relies on a hypervisor to run virtual machine instances. OpenStack can use various hypervisors, but this guide uses KVM." +msgstr "" + +#: ./doc/install-guide/section_nova-compute.xml:18(para) +msgid "Configure the system. Use the instructions in , but note the following differences from the controller node:" +msgstr "" + +#: ./doc/install-guide/section_nova-compute.xml:23(para) +msgid "Use different IP addresses when you configure eth0. This guide uses 192.168.0.11 for the internal network. Do not configure eth1 with a static IP address. The networking component of OpenStack assigns and configures an IP address." +msgstr "" + +#: ./doc/install-guide/section_nova-compute.xml:31(para) +msgid "Set the host name to compute1. To verify, use the uname -n parameter. Ensure that the IP addresses and host names for both nodes are listed in the /etc/hosts file on each system." +msgstr "" + +#: ./doc/install-guide/section_nova-compute.xml:38(para) +msgid "Synchronize from the controller node. Follow the instructions in ." +msgstr "" + +#: ./doc/install-guide/section_nova-compute.xml:42(para) +msgid "Install the MySQL client libraries. You do not need to install the MySQL database server or start the MySQL service." +msgstr "" + +#: ./doc/install-guide/section_nova-compute.xml:47(para) +msgid "Enable the OpenStack packages for the distribution that you are using. See ." +msgstr "" + +#: ./doc/install-guide/section_nova-compute.xml:54(para) +msgid "After you configure the operating system, install the appropriate packages for the Compute service." +msgstr "" + +#: ./doc/install-guide/section_nova-compute.xml:58(para) +msgid "When prompted to create a supermin appliance, respond ." +msgstr "" + +#: ./doc/install-guide/section_nova-compute.xml:63(para) +msgid "To use the meta-packages and install other components on your compute node, such as OVS Networking and Ceilometer agents, run this command:" +msgstr "" + +#: ./doc/install-guide/section_nova-compute.xml:67(para) +msgid "The controller node has the openstack-proxy-node and openstack-toaster meta-packages that install openstack-proxy-node and openstack-toaster at the same time." +msgstr "" + +#: ./doc/install-guide/section_nova-compute.xml:79(para) +msgid "Respond to the prompts for database management, [keystone_authtoken] settings, RabbitMQ credentials, and API endpoint registration." +msgstr "" + +#: ./doc/install-guide/section_nova-compute.xml:88(para) +msgid "For security reasons, the Linux kernel is not readable by normal users which restricts hypervisor services such as qemu and libguestfs. For details, see this bug. To make the current kernel readable, run: To also enable this override for all future kernel updates, create the file /etc/kernel/postinst.d/statoverride containing: Remember to make the file executable: " +msgstr "" + +#: ./doc/install-guide/section_nova-compute.xml:107(para) +msgid "Edit the /etc/nova/nova.conf configuration file:" +msgstr "" + +#: ./doc/install-guide/section_nova-compute.xml:118(para) +msgid "Edit the /etc/nova/nova.conf configuration file and add these lines to the appropriate sections:" +msgstr "" + +#: ./doc/install-guide/section_nova-compute.xml:131(para) +msgid "Configure the Compute Service to use the Qpid message broker by setting these configuration keys:" +msgstr "" + +#: ./doc/install-guide/section_nova-compute.xml:143(para) +msgid "Configure the Compute Service to use the RabbitMQ message broker by setting these configuration keys:" +msgstr "" + +#: ./doc/install-guide/section_nova-compute.xml:152(para) +msgid "Configure Compute to provide remote console access to instances." +msgstr "" + +#: ./doc/install-guide/section_nova-compute.xml:159(para) +msgid "Edit /etc/nova/nova.conf and add the following keys under the [DEFAULT] section:" +msgstr "" + +#: ./doc/install-guide/section_nova-compute.xml:173(para) +msgid "Specify the host that runs the Image Service. Edit /etc/nova/nova.conf file and add these lines to the [DEFAULT] section:" +msgstr "" + +#: ./doc/install-guide/section_nova-compute.xml:184(para) +msgid "If you install Compute on a virtual machine for testing purposes, you must determine whether your hypervisor and/or CPU support nested hardware acceleration using the following command:" +msgstr "" + +#: ./doc/install-guide/section_nova-compute.xml:189(para) +msgid "If this command returns a value of one or greater, your hypervisor and/or CPU support nested hardware acceleration which requires no additional configuration." +msgstr "" + +#: ./doc/install-guide/section_nova-compute.xml:193(para) +msgid "If this command returns a value of zero, your hypervisor and/or CPU do not support nested hardware acceleration and libvirt must use QEMU instead of KVM. Edit the [DEFAULT] section in the /etc/nova/nova-compute.conf file to modify this key:" +msgstr "" + +#: ./doc/install-guide/section_nova-compute.xml:203(para) +msgid "If this command returns a value of zero, your hypervisor and/or CPU do not support nested hardware acceleration and libvirt must use QEMU instead of KVM. Configure libvirt to use QEMU:" +msgstr "" + +#: ./doc/install-guide/section_nova-compute.xml:211(para) +msgid "Edit the /etc/nova/api-paste.ini file to add the credentials to the [filter:authtoken] section:" +msgstr "" + +#: ./doc/install-guide/section_nova-compute.xml:215(para) +msgid "Files with the extension .ini sometimes need to be edited during initial setup. However, they should not be used for general configuration tasks." +msgstr "" + +#: ./doc/install-guide/section_nova-compute.xml:229(para) +msgid "Ensure that the option is set in /etc/nova/nova.conf file." +msgstr "" + +#: ./doc/install-guide/section_nova-compute.xml:236(para) +msgid "Start the Compute service and configure it to start when the system boots." +msgstr "" + +#: ./doc/install-guide/section_nova-compute.xml:253(para) +msgid "Remove the SQLite database created by the packages:" +msgstr "" + +#. When image changes, this message will be marked fuzzy or untranslated for you. +#. It doesn't matter what you translate it to: it's not used at all. +#: ./doc/install-guide/section_glance-install.xml:40(None) +msgid "@@image: 'figures/debconf-screenshots/glance-common_pipeline_flavor.png'; md5=78bef92c36a140ad042074f6345d8917" +msgstr "" + +#: ./doc/install-guide/section_glance-install.xml:7(title) +msgid "Install the Image Service" +msgstr "" + +#: ./doc/install-guide/section_glance-install.xml:8(para) +msgid "The OpenStack Image Service acts as a registry for virtual disk images. Users can add new images or take a snapshot of an image from an existing server for immediate storage. Use snapshots for back up and as templates to launch new servers. You can store registered images in Object Storage or in other locations. For example, you can store images in simple file systems or external web servers." +msgstr "" + +#: ./doc/install-guide/section_glance-install.xml:16(para) +msgid "This procedure assumes you set the appropriate environment variables to your credentials as described in ." +msgstr "" + +#: ./doc/install-guide/section_glance-install.xml:22(para) +msgid "Install the Image Service on the controller node:" +msgstr "" + +#: ./doc/install-guide/section_glance-install.xml:29(para) +msgid "Respond to prompts for database management, [keystone_authtoken] settings, RabbitMQ credentials and API endpoint registration. You must also select the caching type:" +msgstr "" + +#: ./doc/install-guide/section_glance-install.xml:45(para) +msgid "The Image Service stores information about images in a database. The examples in this guide use the MySQL database that is used by other OpenStack services." +msgstr "" + +#: ./doc/install-guide/section_glance-install.xml:48(para) +msgid "Configure the location of the database. The Image Service provides the glance-api and glance-registry services, each with its own configuration file. You must update both configuration files throughout this section. Replace GLANCE_DBPASS with your Image Service database password." +msgstr "" + +#: ./doc/install-guide/section_glance-install.xml:57(replaceable) ./doc/install-guide/section_glance-install.xml:59(replaceable) ./doc/install-guide/section_glance-install.xml:77(replaceable) ./doc/install-guide/section_glance-install.xml:91(replaceable) ./doc/install-guide/section_glance-install.xml:93(replaceable) +msgid "GLANCE_DBPASS" +msgstr "" + +#: ./doc/install-guide/section_glance-install.xml:60(para) +msgid "Edit /etc/glance/glance-api.conf and /etc/glance/glance-registry.conf and change the [DEFAULT] section." +msgstr "" + +#: ./doc/install-guide/section_glance-install.xml:74(para) +msgid "Use the command to create the Image Service database and tables and a glance database user:" +msgstr "" + +#: ./doc/install-guide/section_glance-install.xml:80(para) +msgid "By default, the Ubuntu packages create an SQLite database. Delete the glance.sqlite file created in the /var/lib/glance/ directory so that it does not get used by mistake." +msgstr "" + +#: ./doc/install-guide/section_glance-install.xml:86(para) +msgid "Use the password you created to log in as root and create a glance database user:" +msgstr "" + +#: ./doc/install-guide/section_glance-install.xml:96(para) +msgid "Create the database tables for the Image Service:" +msgstr "" + +#: ./doc/install-guide/section_glance-install.xml:100(para) +msgid "Create a glance user that the Image Service can use to authenticate with the Identity Service. Choose a password and specify an email address for the glance user. Use the service tenant and give the user the admin role." +msgstr "" + +#: ./doc/install-guide/section_glance-install.xml:106(replaceable) ./doc/install-guide/section_glance-install.xml:126(replaceable) ./doc/install-guide/section_glance-install.xml:138(replaceable) ./doc/install-guide/section_glance-install.xml:158(replaceable) ./doc/install-guide/section_glance-install.xml:188(replaceable) +msgid "GLANCE_PASS" +msgstr "" + +#: ./doc/install-guide/section_glance-install.xml:107(replaceable) +msgid "glance@example.com" +msgstr "" + +#: ./doc/install-guide/section_glance-install.xml:111(para) +msgid "Configure the Image Service to use the Identity Service for authentication." +msgstr "" + +#: ./doc/install-guide/section_glance-install.xml:113(para) +msgid "Run the following commands and replace GLANCE_PASS with the password you chose for the glance user in the Identity Service:" +msgstr "" + +#: ./doc/install-guide/section_glance-install.xml:141(para) +msgid "Edit the /etc/glance/glance-api.conf and /etc/glance/glance-registry.conf files. Replace GLANCE_PASS with the password you chose for the glance user in the Identity Service." +msgstr "" + +#: ./doc/install-guide/section_glance-install.xml:148(para) +msgid "Add the following keys under the [keystone_authtoken] section:" +msgstr "" + +#: ./doc/install-guide/section_glance-install.xml:161(para) +msgid "Add the following key under the [paste_deploy] section:" +msgstr "" + +#: ./doc/install-guide/section_glance-install.xml:170(para) +msgid "Add the credentials to the /etc/glance/glance-api-paste.ini and /etc/glance/glance-registry-paste.ini files." +msgstr "" + +#: ./doc/install-guide/section_glance-install.xml:174(para) +msgid "On CentOS, you may need to copy these files to the correct location." +msgstr "" + +#: ./doc/install-guide/section_glance-install.xml:180(para) +msgid "Edit each file to set the following options in the [filter:authtoken] section and leave any other existing option as it is." +msgstr "" + +#: ./doc/install-guide/section_glance-install.xml:191(para) +msgid "Register the Image Service with the Identity Service so that other OpenStack services can locate it. Register the service and create the endpoint:" +msgstr "" + +#: ./doc/install-guide/section_glance-install.xml:203(para) +msgid "Restart the glance service with its new settings." +msgstr "" + +#: ./doc/install-guide/section_glance-install.xml:209(para) +msgid "Start the glance-api and glance-registry services and configure them to start when the system boots:" +msgstr "" + +#. When image changes, this message will be marked fuzzy or untranslated for you. +#. It doesn't matter what you translate it to: it's not used at all. +#: ./doc/install-guide/section_debconf-dbconfig-common.xml:30(None) +msgid "@@image: 'figures/debconf-screenshots/dbconfig-common_keep_admin_pass.png'; md5=01af4867c16e458306b8abd78a1fccc9" +msgstr "" + +#. When image changes, this message will be marked fuzzy or untranslated for you. +#. It doesn't matter what you translate it to: it's not used at all. +#: ./doc/install-guide/section_debconf-dbconfig-common.xml:39(None) +msgid "@@image: 'figures/debconf-screenshots/dbconfig-common_used_for_remote_db.png'; md5=c6ec966bbfdee18ad87456cf4d44a56f" +msgstr "" + +#. When image changes, this message will be marked fuzzy or untranslated for you. +#. It doesn't matter what you translate it to: it's not used at all. +#: ./doc/install-guide/section_debconf-dbconfig-common.xml:78(None) +msgid "@@image: 'figures/debconf-screenshots/dbconfig-common_1_configure-with-dbconfig-yes-no.png'; md5=4e9d7bce27cc6c7bd68ce8622c80b60f" +msgstr "" + +#. When image changes, this message will be marked fuzzy or untranslated for you. +#. It doesn't matter what you translate it to: it's not used at all. +#: ./doc/install-guide/section_debconf-dbconfig-common.xml:87(None) +msgid "@@image: 'figures/debconf-screenshots/dbconfig-common_2_db-types.png'; md5=a77beb7e13b487cf79716c2140f258c2" +msgstr "" + +#. When image changes, this message will be marked fuzzy or untranslated for you. +#. It doesn't matter what you translate it to: it's not used at all. +#: ./doc/install-guide/section_debconf-dbconfig-common.xml:96(None) +msgid "@@image: 'figures/debconf-screenshots/dbconfig-common_3_connection_method.png'; md5=6cc592e5dd5ea404ad7aad98b37a71f6" +msgstr "" + +#. When image changes, this message will be marked fuzzy or untranslated for you. +#. It doesn't matter what you translate it to: it's not used at all. +#: ./doc/install-guide/section_debconf-dbconfig-common.xml:105(None) +msgid "@@image: 'figures/debconf-screenshots/dbconfig-common_4_mysql_root_password.png'; md5=873ec338742e37305583e9e692bcfdc6" +msgstr "" + +#. When image changes, this message will be marked fuzzy or untranslated for you. +#. It doesn't matter what you translate it to: it's not used at all. +#: ./doc/install-guide/section_debconf-dbconfig-common.xml:114(None) +msgid "@@image: 'figures/debconf-screenshots/dbconfig-common_5_mysql_app_password.png'; md5=3651970770d05892f21d1b5741afbee6" +msgstr "" + +#. When image changes, this message will be marked fuzzy or untranslated for you. +#. It doesn't matter what you translate it to: it's not used at all. +#: ./doc/install-guide/section_debconf-dbconfig-common.xml:123(None) +msgid "@@image: 'figures/debconf-screenshots/dbconfig-common_6_mysql_app_password_confirm.png'; md5=060cc90aaf6f6fd5cea718064829c1b1" +msgstr "" + +#: ./doc/install-guide/section_debconf-dbconfig-common.xml:6(title) +msgid "Configure the database with dbconfig-common" +msgstr "" + +#: ./doc/install-guide/section_debconf-dbconfig-common.xml:7(para) +msgid "The dbconfig-common package provides a standard Debian interface that enables you to configure Debian database parameters. It includes localized prompts for many languages and it supports the OpenStack database back ends: SQLite, MySQL, and PostgreSQL." +msgstr "" + +#: ./doc/install-guide/section_debconf-dbconfig-common.xml:12(para) +msgid "By default, the dbconfig-common package configures the OpenStack services to use SQLite3. So if you use debconf in non-interactive mode and without pre-seeding, the OpenStack services that you install use SQLite3." +msgstr "" + +#: ./doc/install-guide/section_debconf-dbconfig-common.xml:17(para) +msgid "By default, dbconfig-common does not provide access to database servers over a network. If you want the dbconfig-common package to prompt for remote database servers that are accessed over a network and not through a UNIX socket file, reconfigure it, as follows:" +msgstr "" + +#: ./doc/install-guide/section_debconf-dbconfig-common.xml:23(para) +msgid "These screens appear when you re-configure the dbconfig-common package:" +msgstr "" + +#: ./doc/install-guide/section_debconf-dbconfig-common.xml:43(para) +msgid "Unlike other debconf prompts, you cannot pre-seed the responses for the dbconfig-common prompts by using . Instead, you must create a file in /etc/dbconfig-common. For example, you might create a keystone configuration file for dbconfig-common that is located in /etc/dbconfig-common/keystone.conf, as follows:" +msgstr "" + +#: ./doc/install-guide/section_debconf-dbconfig-common.xml:66(para) +msgid "After you create this file, run this command:" +msgstr "" + +#: ./doc/install-guide/section_debconf-dbconfig-common.xml:68(para) +msgid "The Identity Service is installed with MySQL as the database back end, keystonedb as database name, and the localhost socket file." +msgstr "" + +#: ./doc/install-guide/section_debconf-dbconfig-common.xml:71(para) +msgid "The cinder-common package displays these screens:" +msgstr "" + +#: ./doc/install-guide/section_debconf-dbconfig-common.xml:127(para) +msgid "To access a MySQL server remotely, you must make it accessible as root from a remote server. To do so, run the openstack-proxy-node package command:" +msgstr "" + +#: ./doc/install-guide/section_debconf-dbconfig-common.xml:131(para) +msgid "Alternatively, if you do not want to install this package, run this script to enable remote root access:" +msgstr "" + +#: ./doc/install-guide/section_debconf-dbconfig-common.xml:154(para) +msgid "You must enable remote access before you install OpenStack services." +msgstr "" + +#. When image changes, this message will be marked fuzzy or untranslated for you. +#. It doesn't matter what you translate it to: it's not used at all. +#: ./doc/install-guide/section_keystone-install.xml:87(None) +msgid "@@image: 'figures/debconf-screenshots/keystone_1_admin_token.png'; md5=29a51caaf09c3d6e3f0fda73c256a17a" +msgstr "" + +#. When image changes, this message will be marked fuzzy or untranslated for you. +#. It doesn't matter what you translate it to: it's not used at all. +#: ./doc/install-guide/section_keystone-install.xml:112(None) +msgid "@@image: 'figures/debconf-screenshots/keystone_2_register_admin_tenant_yes_no.png'; md5=25c9a90b1df2d979aae6ce9975c7285b" +msgstr "" + +#. When image changes, this message will be marked fuzzy or untranslated for you. +#. It doesn't matter what you translate it to: it's not used at all. +#: ./doc/install-guide/section_keystone-install.xml:121(None) +msgid "@@image: 'figures/debconf-screenshots/keystone_3_admin_user_name.png'; md5=173cf7ed13252df1425109be588b2ad6" +msgstr "" + +#. When image changes, this message will be marked fuzzy or untranslated for you. +#. It doesn't matter what you translate it to: it's not used at all. +#: ./doc/install-guide/section_keystone-install.xml:130(None) +msgid "@@image: 'figures/debconf-screenshots/keystone_4_admin_user_email.png'; md5=b7f0d34350ccc0aa9ae4e766b7ac80c1" +msgstr "" + +#. When image changes, this message will be marked fuzzy or untranslated for you. +#. It doesn't matter what you translate it to: it's not used at all. +#: ./doc/install-guide/section_keystone-install.xml:139(None) +msgid "@@image: 'figures/debconf-screenshots/keystone_5_admin_user_pass.png'; md5=e6b32d8d80af90f07a66abc8fb256c84" +msgstr "" + +#. When image changes, this message will be marked fuzzy or untranslated for you. +#. It doesn't matter what you translate it to: it's not used at all. +#: ./doc/install-guide/section_keystone-install.xml:148(None) +msgid "@@image: 'figures/debconf-screenshots/keystone_6_admin_user_pass_confirm.png'; md5=1fbf9223e4923c93030d53278d1771cc" +msgstr "" + +#. When image changes, this message will be marked fuzzy or untranslated for you. +#. It doesn't matter what you translate it to: it's not used at all. +#: ./doc/install-guide/section_keystone-install.xml:162(None) +msgid "@@image: 'figures/debconf-screenshots/keystone_7_register_endpoint.png'; md5=d24d84133bfee936267e79631a2666e6" +msgstr "" + +#: ./doc/install-guide/section_keystone-install.xml:6(title) +msgid "Install the Identity Service" +msgstr "" + +#: ./doc/install-guide/section_keystone-install.xml:9(para) +msgid "Install the OpenStack Identity Service on the controller node, together with python-keystoneclient (which is a dependency):" +msgstr "" + +#: ./doc/install-guide/section_keystone-install.xml:17(para) +msgid "Answer to the debconf and dbconfig-common questions for setting-up the database." +msgstr "" + +#: ./doc/install-guide/section_keystone-install.xml:23(para) +msgid "The Identity Service uses a database to store information. Specify the location of the database in the configuration file. In this guide, we use a MySQL database on the controller node with the username keystone. Replace KEYSTONE_DBPASS with a suitable password for the database user." +msgstr "" + +#: ./doc/install-guide/section_keystone-install.xml:30(replaceable) ./doc/install-guide/section_keystone-install.xml:50(replaceable) ./doc/install-guide/section_keystone-install.xml:65(replaceable) ./doc/install-guide/section_keystone-install.xml:67(replaceable) +msgid "KEYSTONE_DBPASS" +msgstr "" + +#: ./doc/install-guide/section_keystone-install.xml:31(para) +msgid "Edit /etc/keystone/keystone.conf and change the [sql] section." +msgstr "" + +#: ./doc/install-guide/section_keystone-install.xml:44(para) +msgid "Use the command to create the database and tables, as well as a database user called keystone to connect to the database. Replace KEYSTONE_DBPASS with the same password used in the previous step." +msgstr "" + +#: ./doc/install-guide/section_keystone-install.xml:53(para) +msgid "By default, the Ubuntu packages create an SQLite database. Delete the keystone.db file created in the /var/lib/keystone/ directory so that it does not get used by mistake." +msgstr "" + +#: ./doc/install-guide/section_keystone-install.xml:59(para) +msgid "Use the password that you set previously to log in as root. Create a keystone database user:" +msgstr "" + +#: ./doc/install-guide/section_keystone-install.xml:70(para) +msgid "Create the database tables for the Identity Service:" +msgstr "" + +#: ./doc/install-guide/section_keystone-install.xml:75(para) +msgid "Define an authorization token to use as a shared secret between the Identity Service and other OpenStack services. Respond to the debconf prompt with the value in the admin_token directive in the keystone.conf file. Use the command to generate this password." +msgstr "" + +#: ./doc/install-guide/section_keystone-install.xml:91(para) +msgid "Later, you can verify that the /etc/keystone/keystone.conf file contains the password you have set using debconf: " +msgstr "" + +#: ./doc/install-guide/section_keystone-install.xml:99(para) +msgid "If you omit a password (for example by pressing Enter at the debconf prompt, or installing Keystone using the Debconf non-interactive mode) the package generates a random ADMIN_TOKEN value." +msgstr "" + +#: ./doc/install-guide/section_keystone-install.xml:105(para) +msgid "Respond to the prompts to create an administrative tenant:" +msgstr "" + +#: ./doc/install-guide/section_keystone-install.xml:154(para) +msgid "If this is the first time you have installed the Identity Service, register the Identity Service in the service catalog:" +msgstr "" + +#: ./doc/install-guide/section_keystone-install.xml:168(para) +msgid "Define an authorization token to use as a shared secret between the Identity Service and other OpenStack services. Use to generate a random token and store it in the configuration file:" +msgstr "" + +#: ./doc/install-guide/section_keystone-install.xml:177(para) +msgid "For SUSE Linux Enterprise use instead as first command:" +msgstr "" + +#: ./doc/install-guide/section_keystone-install.xml:180(para) +msgid "Edit /etc/keystone/keystone.conf and change the [DEFAULT] section, replacing ADMIN_TOKEN with the results of the command." +msgstr "" + +#: ./doc/install-guide/section_keystone-install.xml:190(para) +msgid "By default, Keystone uses PKI tokens. Create the signing keys and certificates:" +msgstr "" + +#: ./doc/install-guide/section_keystone-install.xml:201(para) +msgid "Restart the Identity Service:" +msgstr "" + +#: ./doc/install-guide/section_keystone-install.xml:205(para) +msgid "Start the Identity Service and enable it to start when the system boots:" +msgstr "" + +#: ./doc/install-guide/object-storage/section_object-storage-post-install.xml:6(title) +msgid "Object Storage post-installation tasks" +msgstr "" + +#: ./doc/install-guide/object-storage/section_object-storage-post-install.xml:10(title) +msgid "Add a proxy server" +msgstr "" + +#: ./doc/install-guide/object-storage/section_object-storage-post-install.xml:11(para) +msgid "For reliability, you add proxy servers. You can set up an additional proxy node the same way that you set up the first proxy node but with additional configuration steps." +msgstr "" + +#: ./doc/install-guide/object-storage/section_object-storage-post-install.xml:15(para) +msgid "After you have more than two proxies, you must load balance them; your storage endpoint (what clients use to connect to your storage) also changes. You can select from different strategies for load balancing. For example, you could use round-robin DNS, or a software or hardware load balancer (like pound) in front of the two proxies, and point your storage URL to the load balancer." +msgstr "" + +#: ./doc/install-guide/object-storage/section_object-storage-post-install.xml:24(para) +msgid "Configure an initial proxy node. Then, complete these steps to add proxy servers." +msgstr "" + +#: ./doc/install-guide/object-storage/section_object-storage-post-install.xml:28(para) +msgid "Update the list of memcache servers in the /etc/swift/proxy-server.conf file for added proxy servers. If you run multiple memcache servers, use this pattern for the multiple IP:port listings in each proxy server configuration file:" +msgstr "" + +#: ./doc/install-guide/object-storage/section_object-storage-post-install.xml:42(para) +msgid "Copy ring information to all nodes, including new proxy nodes. Also, ensure that the ring information gets to all storage nodes." +msgstr "" + +#: ./doc/install-guide/object-storage/section_object-storage-post-install.xml:49(para) +msgid "After you sync all nodes, make sure that the admin has keys in /etc/swift and the ownership for the ring file is correct." +msgstr "" + +#: ./doc/install-guide/object-storage/section_object-storage-verifying-install.xml:6(title) +msgid "Verify the installation" +msgstr "" + +#: ./doc/install-guide/object-storage/section_object-storage-verifying-install.xml:7(para) +msgid "You can run these commands from the proxy server or any server that has access to the Identity Service." +msgstr "" + +#: ./doc/install-guide/object-storage/section_object-storage-verifying-install.xml:11(para) +msgid "Make sure that your credentials are set up correctly in the openrc.sh file and source it:" +msgstr "" + +#: ./doc/install-guide/object-storage/section_object-storage-verifying-install.xml:15(para) +msgid "Run the following command:" +msgstr "" + +#: ./doc/install-guide/object-storage/section_object-storage-verifying-install.xml:27(para) +msgid "Run the following commands to upload files to a container. Create the test.txt and test2.txt test files locally if needed." +msgstr "" + +#: ./doc/install-guide/object-storage/section_object-storage-verifying-install.xml:34(para) +msgid "Run the following command to download all files from the myfiles container:" +msgstr "" + +#: ./doc/install-guide/object-storage/section_object-storage-install-config-proxy-node.xml:6(title) +msgid "Install and configure the proxy node" +msgstr "" + +#: ./doc/install-guide/object-storage/section_object-storage-install-config-proxy-node.xml:7(para) +msgid "The proxy server takes each request and looks up locations for the account, container, or object and routes the requests correctly. The proxy server also handles API requests. You enable account management by configuring it in the proxy-server.conf file." +msgstr "" + +#: ./doc/install-guide/object-storage/section_object-storage-install-config-proxy-node.xml:13(para) +msgid "The Object Storage processes run under a separate user and group, set by configuration options, and referred to as swift:swiftopenstack-swift:openstack-swift. The default user is swift, which may not exist on your system.openstack-swift." +msgstr "" + +#: ./doc/install-guide/object-storage/section_object-storage-install-config-proxy-node.xml:25(para) +msgid "Install swift-proxy service:" +msgstr "" + +#: ./doc/install-guide/object-storage/section_object-storage-install-config-proxy-node.xml:31(para) +msgid "Create self-signed cert for SSL:" +msgstr "" + +#: ./doc/install-guide/object-storage/section_object-storage-install-config-proxy-node.xml:36(para) +msgid "Modify memcached to listen on the default interfaces on a local, non-public network. Edit this line in the /etc/memcached.conf file:" +msgstr "" + +#: ./doc/install-guide/object-storage/section_object-storage-install-config-proxy-node.xml:40(para) +msgid "Change it to:" +msgstr "" + +#: ./doc/install-guide/object-storage/section_object-storage-install-config-proxy-node.xml:44(para) +msgid "Restart the memcached server:" +msgstr "" + +#: ./doc/install-guide/object-storage/section_object-storage-install-config-proxy-node.xml:48(para) +msgid "RHEL/CentOS/Fedora only: To set up Object Storage to authenticate tokens, set the Identity Service Admin token in the swift proxy file with the command." +msgstr "" + +#: ./doc/install-guide/object-storage/section_object-storage-install-config-proxy-node.xml:58(para) +msgid "Ubuntu only: Because the distribution packages do not include a copy of the keystoneauth middleware, ensure that the proxy server includes them:" +msgstr "" + +#: ./doc/install-guide/object-storage/section_object-storage-install-config-proxy-node.xml:68(para) +msgid "Create /etc/swift/proxy-server.conf:" +msgstr "" + +#: ./doc/install-guide/object-storage/section_object-storage-install-config-proxy-node.xml:72(phrase) +msgid "user = swift" +msgstr "" + +#: ./doc/install-guide/object-storage/section_object-storage-install-config-proxy-node.xml:73(phrase) +msgid "user = openstack-swift" +msgstr "" + +#: ./doc/install-guide/object-storage/section_object-storage-install-config-proxy-node.xml:120(para) +msgid "If you run multiple memcache servers, put the multiple IP:port listings in the [filter:cache] section of the proxy-server.conf file:" +msgstr "" + +#: ./doc/install-guide/object-storage/section_object-storage-install-config-proxy-node.xml:125(para) +msgid "Only the proxy server uses memcache." +msgstr "" + +#: ./doc/install-guide/object-storage/section_object-storage-install-config-proxy-node.xml:129(para) +msgid "Create the signing_dir and set its permissions accordingly." +msgstr "" + +#: ./doc/install-guide/object-storage/section_object-storage-install-config-proxy-node.xml:138(para) +msgid "Create the account, container, and object rings. The builder command creates a builder file with a few parameters. The parameter with the value of 18 represents 2 ^ 18th, the value that the partition is sized to. Set this “partition power” value based on the total amount of storage you expect your entire ring to use. The value 3 represents the number of replicas of each object, with the last value being the number of hours to restrict moving a partition more than once." +msgstr "" + +#: ./doc/install-guide/object-storage/section_object-storage-install-config-proxy-node.xml:154(para) +msgid "For every storage device on each node add entries to each ring:" +msgstr "" + +#: ./doc/install-guide/object-storage/section_object-storage-install-config-proxy-node.xml:160(para) +msgid "You must omit the optional STORAGE_REPLICATION_NET_IP parameter if you do not want to use dedicated network for replication." +msgstr "" + +#: ./doc/install-guide/object-storage/section_object-storage-install-config-proxy-node.xml:164(para) +msgid "For example, if a storage node has a partition in Zone 1 on IP 10.0.0.1, the storage node has address 10.0.1.1 from replication network. The mount point of this partition is /srv/node/sdb1, and the path in rsyncd.conf is /srv/node/, the DEVICE would be sdb1 and the commands are:" +msgstr "" + +#: ./doc/install-guide/object-storage/section_object-storage-install-config-proxy-node.xml:175(para) +msgid "If you assume five zones with one node for each zone, start ZONE at 1. For each additional node, increment ZONE by 1." +msgstr "" + +#: ./doc/install-guide/object-storage/section_object-storage-install-config-proxy-node.xml:181(para) +msgid "Verify the ring contents for each ring:" +msgstr "" + +#: ./doc/install-guide/object-storage/section_object-storage-install-config-proxy-node.xml:187(para) +msgid "Rebalance the rings:" +msgstr "" + +#: ./doc/install-guide/object-storage/section_object-storage-install-config-proxy-node.xml:192(para) +msgid "Rebalancing rings can take some time." +msgstr "" + +#: ./doc/install-guide/object-storage/section_object-storage-install-config-proxy-node.xml:196(para) +msgid "Copy the account.ring.gz, container.ring.gz, and object.ring.gz files to each of the Proxy and Storage nodes in /etc/swift." +msgstr "" + +#: ./doc/install-guide/object-storage/section_object-storage-install-config-proxy-node.xml:202(para) +msgid "Make sure the swift user owns all configuration files:" +msgstr "" + +#: ./doc/install-guide/object-storage/section_object-storage-install-config-proxy-node.xml:207(para) +msgid "Start Proxy services:" +msgstr "" + +#: ./doc/install-guide/object-storage/section_object-storage-network-planning.xml:6(title) +msgid "Plan networking for Object Storage" +msgstr "" + +#: ./doc/install-guide/object-storage/section_object-storage-network-planning.xml:7(para) +msgid "For both conserving network resources and ensuring that network administrators understand the needs for networks and public IP addresses for providing access to the APIs and storage network as necessary, this section offers recommendations and required minimum sizes. Throughput of at least 1000 Mbps is suggested." +msgstr "" + +#: ./doc/install-guide/object-storage/section_object-storage-network-planning.xml:15(para) +msgid "A mandatory public network. Connects to the Proxy server." +msgstr "" + +#: ./doc/install-guide/object-storage/section_object-storage-network-planning.xml:19(para) +msgid "A mandatory storage network. Not accessible from outside the cluster. All nodes connect to this network." +msgstr "" + +#: ./doc/install-guide/object-storage/section_object-storage-network-planning.xml:23(para) +msgid "An optional replication network. Not accessible from outside the cluster. Dedicated to replication traffic among Storage nodes. Must be configured in the Ring." +msgstr "" + +#: ./doc/install-guide/object-storage/section_object-storage-network-planning.xml:13(para) +msgid "This guide describes the following networks:" +msgstr "" + +#: ./doc/install-guide/object-storage/section_object-storage-network-planning.xml:28(para) +msgid "By default, all of the OpenStack Object Storage services, as well as the rsync daemon on the Storage nodes, are configured to listen on their STORAGE_LOCAL_NET IP addresses." +msgstr "" + +#: ./doc/install-guide/object-storage/section_object-storage-network-planning.xml:32(para) +msgid "If you configure a replication network in the Ring, the Account, Container and Object servers listen on both the STORAGE_LOCAL_NET and STORAGE_REPLICATION_NET IP addresses. The rsync daemon only listens on the STORAGE_REPLICATION_NET IP address." +msgstr "" + +#: ./doc/install-guide/object-storage/section_object-storage-network-planning.xml:40(term) +msgid "Public Network (Publicly routable IP range)" +msgstr "" + +#: ./doc/install-guide/object-storage/section_object-storage-network-planning.xml:42(para) +msgid "Provides public IP accessibility to the API endpoints within the cloud infrastructure." +msgstr "" + +#: ./doc/install-guide/object-storage/section_object-storage-network-planning.xml:44(para) +msgid "Minimum size: one IP address for each proxy server." +msgstr "" + +#: ./doc/install-guide/object-storage/section_object-storage-network-planning.xml:49(term) +msgid "Storage Network (RFC1918 IP Range, not publicly routable)" +msgstr "" + +#: ./doc/install-guide/object-storage/section_object-storage-network-planning.xml:52(para) +msgid "Manages all inter-server communications within the Object Storage infrastructure." +msgstr "" + +#: ./doc/install-guide/object-storage/section_object-storage-network-planning.xml:54(para) +msgid "Minimum size: one IP address for each storage node and proxy server." +msgstr "" + +#: ./doc/install-guide/object-storage/section_object-storage-network-planning.xml:56(para) +msgid "Recommended size: as above, with room for expansion to the largest your cluster size. For example, 255 or CIDR /24." +msgstr "" + +#: ./doc/install-guide/object-storage/section_object-storage-network-planning.xml:62(term) +msgid "Replication Network (RFC1918 IP Range, not publicly routable)" +msgstr "" + +#: ./doc/install-guide/object-storage/section_object-storage-network-planning.xml:65(para) +msgid "Manages replication-related communications among storage servers within the Object Storage infrastructure." +msgstr "" + +#: ./doc/install-guide/object-storage/section_object-storage-network-planning.xml:67(para) +msgid "Recommended size: as for STORAGE_LOCAL_NET." +msgstr "" + +#. When image changes, this message will be marked fuzzy or untranslated for you. +#. It doesn't matter what you translate it to: it's not used at all. +#: ./doc/install-guide/object-storage/section_object-storage-example-install-arch.xml:45(None) +msgid "@@image: '../figures/swift_install_arch.png'; md5=c6519fb969c1184afa22e024de9bd2a6" +msgstr "" + +#: ./doc/install-guide/object-storage/section_object-storage-example-install-arch.xml:6(title) +msgid "Example Object Storage installation architecture" +msgstr "" + +#: ./doc/install-guide/object-storage/section_object-storage-example-install-arch.xml:9(para) +msgid "node. A host machine that runs one or more OpenStack Object Storage services." +msgstr "" + +#: ./doc/install-guide/object-storage/section_object-storage-example-install-arch.xml:13(para) +msgid "Proxy node. Runs Proxy services." +msgstr "" + +#: ./doc/install-guide/object-storage/section_object-storage-example-install-arch.xml:16(para) +msgid "Storage node. Runs Account, Container, and Object services." +msgstr "" + +#: ./doc/install-guide/object-storage/section_object-storage-example-install-arch.xml:20(para) +msgid "Ring. A set of mappings between OpenStack Object Storage data to physical devices." +msgstr "" + +#: ./doc/install-guide/object-storage/section_object-storage-example-install-arch.xml:24(para) +msgid "Replica. A copy of an object. By default, three copies are maintained in the cluster." +msgstr "" + +#: ./doc/install-guide/object-storage/section_object-storage-example-install-arch.xml:28(para) +msgid "Zone. A logically separate section of the cluster, related to independent failure characteristics." +msgstr "" + +#: ./doc/install-guide/object-storage/section_object-storage-example-install-arch.xml:32(para) +msgid "To increase reliability and performance, you can add additional proxy servers." +msgstr "" + +#: ./doc/install-guide/object-storage/section_object-storage-example-install-arch.xml:34(para) +msgid "This document describes each storage node as a separate zone in the ring. At a minimum, five zones are recommended. A zone is a group of nodes that is as isolated as possible from other nodes (separate servers, network, power, even geography). The ring guarantees that every replica is stored in a separate zone. This diagram shows one possible configuration for a minimal installation:" +msgstr "" + +#: ./doc/install-guide/object-storage/section_object-storage-install.xml:6(title) +msgid "Install Object Storage" +msgstr "" + +#: ./doc/install-guide/object-storage/section_object-storage-install.xml:7(para) +msgid "Though you can install OpenStack Object Storage for development or testing purposes on one server, a multiple-server installation enables the high availability and redundancy you want in a production distributed object storage system." +msgstr "" + +#: ./doc/install-guide/object-storage/section_object-storage-install.xml:12(para) +msgid "To perform a single-node installation for development purposes from source code, use the Swift All In One instructions (Ubuntu) or DevStack (multiple distros). See http://swift.openstack.org/development_saio.html for manual instructions or http://devstack.org for all-in-one including authentication with the Identity Service (keystone)." +msgstr "" + +#: ./doc/install-guide/object-storage/section_object-storage-install.xml:24(para) +msgid "Have a copy of the operating system installation media available if you are installing on a new server." +msgstr "" + +#: ./doc/install-guide/object-storage/section_object-storage-install.xml:26(para) +msgid "These steps assume you have set up repositories for packages for your operating system as shown in OpenStack Packages." +msgstr "" + +#: ./doc/install-guide/object-storage/section_object-storage-install.xml:30(para) +msgid "This document demonstrates how to install a cluster by using the following types of nodes:" +msgstr "" + +#: ./doc/install-guide/object-storage/section_object-storage-install.xml:34(para) +msgid "One proxy node which runs the swift-proxy-server processes. The proxy server proxies requests to the appropriate storage nodes." +msgstr "" + +#: ./doc/install-guide/object-storage/section_object-storage-install.xml:39(para) +msgid "Five storage nodes that run the swift-account-server, swift-container-server, and swift-object-server processes which control storage of the account databases, the container databases, as well as the actual stored objects." +msgstr "" + +#: ./doc/install-guide/object-storage/section_object-storage-install.xml:48(para) +msgid "Fewer storage nodes can be used initially, but a minimum of five is recommended for a production cluster." +msgstr "" + +#: ./doc/install-guide/object-storage/section_object-storage-install.xml:54(title) +msgid "General installation steps" +msgstr "" + +#: ./doc/install-guide/object-storage/section_object-storage-install.xml:57(para) +msgid "Install core Swift files and openSSH." +msgstr "" + +#: ./doc/install-guide/object-storage/section_object-storage-install.xml:68(para) +msgid "Create a swift user that the Object Storage Service can use to authenticate with the Identity Service. Choose a password and specify an email address for the swift user. Use the service tenant and give the user the admin role." +msgstr "" + +#: ./doc/install-guide/object-storage/section_object-storage-install.xml:75(replaceable) +msgid "SWIFT_PASS" +msgstr "" + +#: ./doc/install-guide/object-storage/section_object-storage-install.xml:76(replaceable) +msgid "swift@example.com" +msgstr "" + +#: ./doc/install-guide/object-storage/section_object-storage-install.xml:80(para) +msgid "Create a service entry for the Object Storage Service:" +msgstr "" + +#: ./doc/install-guide/object-storage/section_object-storage-install.xml:95(para) +msgid "Specify an API endpoint for the Object Storage Service by using the returned service ID. When you specify an endpoint, you provide URLs for the public API, internal API, and admin API. In this guide, the controller host name is used." +msgstr "" + +#: ./doc/install-guide/object-storage/section_object-storage-install.xml:117(para) +msgid "Create and populate configuration directories on all nodes:" +msgstr "" + +#: ./doc/install-guide/object-storage/section_object-storage-install.xml:125(para) +msgid "Create /etc/swift/swift.conf on all nodes:" +msgstr "" + +#: ./doc/install-guide/object-storage/section_object-storage-install.xml:132(para) +msgid "The suffix value in /etc/swift/swift.conf should be set to some random string of text to be used as a salt when hashing to determine mappings in the ring. This file should be the same on every node in the cluster!" +msgstr "" + +#: ./doc/install-guide/object-storage/section_object-storage-install.xml:139(para) +msgid "Next, set up your storage nodes and proxy node. This example uses the Identity Service for the common authentication piece." +msgstr "" + +#: ./doc/install-guide/object-storage/section_start-storage-node-services.xml:7(title) +msgid "Start services on the storage nodes" +msgstr "" + +#: ./doc/install-guide/object-storage/section_start-storage-node-services.xml:8(para) +msgid "Now that the ring files are on each storage node, you can start the services. On each storage node, run the following commands:" +msgstr "" + +#: ./doc/install-guide/object-storage/section_start-storage-node-services.xml:36(para) +msgid "To start all swift services at once, run the command:" +msgstr "" + +#: ./doc/install-guide/object-storage/section_start-storage-node-services.xml:38(para) +msgid "To know more about swift-init command, run:" +msgstr "" + +#: ./doc/install-guide/object-storage/section_start-storage-node-services.xml:45(replaceable) +msgid "service" +msgstr "" + +#: ./doc/install-guide/object-storage/section_start-storage-node-services.xml:44(para) +msgid "On Fedora, you might need to use ." +msgstr "" + +#: ./doc/install-guide/object-storage/section_object-storage-install-config-storage-nodes.xml:6(title) +msgid "Install and configure storage nodes" +msgstr "" + +#: ./doc/install-guide/object-storage/section_object-storage-install-config-storage-nodes.xml:8(para) +msgid "Object Storage works on any file system that supports Extended Attributes (XATTRS). XFS shows the best overall performance for the swift use case after considerable testing and benchmarking at Rackspace. It is also the only file system that has been thoroughly tested. See the OpenStack Configuration Reference for additional recommendations." +msgstr "" + +#: ./doc/install-guide/object-storage/section_object-storage-install-config-storage-nodes.xml:20(para) +msgid "Install Storage node packages:" +msgstr "" + +#: ./doc/install-guide/object-storage/section_object-storage-install-config-storage-nodes.xml:29(para) +msgid "For each device on the node that you want to use for storage, set up the XFS volume (/dev/sdb is used as an example). Use a single partition per drive. For example, in a server with 12 disks you may use one or two disks for the operating system which should not be touched in this step. The other 10 or 11 disks should be partitioned with a single partition, then formatted in XFS." +msgstr "" + +#: ./doc/install-guide/object-storage/section_object-storage-install-config-storage-nodes.xml:52(para) +msgid "Create /etc/rsyncd.conf:" +msgstr "" + +#: ./doc/install-guide/object-storage/section_object-storage-install-config-storage-nodes.xml:101(para) +msgid "(Optional) If you want to separate rsync and replication traffic to replication network, set STORAGE_REPLICATION_NET_IP instead of STORAGE_LOCAL_NET_IP:" +msgstr "" + +#: ./doc/install-guide/object-storage/section_object-storage-install-config-storage-nodes.xml:109(para) +msgid "Edit the following line in /etc/default/rsync:" +msgstr "" + +#: ./doc/install-guide/object-storage/section_object-storage-install-config-storage-nodes.xml:114(para) +msgid "Start rsync daemon:" +msgstr "" + +#: ./doc/install-guide/object-storage/section_object-storage-install-config-storage-nodes.xml:117(para) +msgid "The rsync daemon requires no authentication, so run it on a local, private network." +msgstr "" + +#: ./doc/install-guide/object-storage/section_object-storage-install-config-storage-nodes.xml:122(para) +msgid "Create the swift recon cache directory and set its permissions." +msgstr "" + +#: ./doc/install-guide/object-storage/section_object-storage-sys-requirements.xml:8(para) +msgid "Hardware: OpenStack Object Storage is designed to run on commodity hardware." +msgstr "" + +#: ./doc/install-guide/object-storage/section_object-storage-sys-requirements.xml:11(para) +msgid "When you install only the Object Storage and Identity Service, you cannot use the dashboard unless you also install Compute and the Image Service." +msgstr "" + +#: ./doc/install-guide/object-storage/section_object-storage-sys-requirements.xml:16(caption) +msgid "Hardware recommendations" +msgstr "" + +#: ./doc/install-guide/object-storage/section_object-storage-sys-requirements.xml:23(td) +msgid "Server" +msgstr "" + +#: ./doc/install-guide/object-storage/section_object-storage-sys-requirements.xml:24(td) +msgid "Recommended Hardware" +msgstr "" + +#: ./doc/install-guide/object-storage/section_object-storage-sys-requirements.xml:30(para) +msgid "Object Storage object servers" +msgstr "" + +#: ./doc/install-guide/object-storage/section_object-storage-sys-requirements.xml:32(para) ./doc/install-guide/object-storage/section_object-storage-sys-requirements.xml:61(para) ./doc/install-guide/object-storage/section_object-storage-sys-requirements.xml:71(para) +msgid "Processor: dual quad core" +msgstr "" + +#: ./doc/install-guide/object-storage/section_object-storage-sys-requirements.xml:33(para) ./doc/install-guide/object-storage/section_object-storage-sys-requirements.xml:62(para) +msgid "Memory: 8 or 12 GB RAM" +msgstr "" + +#: ./doc/install-guide/object-storage/section_object-storage-sys-requirements.xml:34(para) +msgid "Disk space: optimized for cost per GB" +msgstr "" + +#: ./doc/install-guide/object-storage/section_object-storage-sys-requirements.xml:35(para) ./doc/install-guide/object-storage/section_object-storage-sys-requirements.xml:63(para) ./doc/install-guide/object-storage/section_object-storage-sys-requirements.xml:72(para) +msgid "Network: one 1 GB Network Interface Card (NIC)" +msgstr "" + +#: ./doc/install-guide/object-storage/section_object-storage-sys-requirements.xml:37(para) +msgid "The amount of disk space depends on how much you can fit into the rack efficiently. You want to optimize these for best cost per GB while still getting industry-standard failure rates. At Rackspace, our storage servers are currently running fairly generic 4U servers with 24 2T SATA drives and 8 cores of processing power. RAID on the storage drives is not required and not recommended. Swift's disk usage pattern is the worst case possible for RAID, and performance degrades very quickly using RAID 5 or 6." +msgstr "" + +#: ./doc/install-guide/object-storage/section_object-storage-sys-requirements.xml:49(para) +msgid "As an example, Rackspace runs Cloud Files storage servers with 24 2T SATA drives and 8 cores of processing power. Most services support either a worker or concurrency value in the settings. This allows the services to make effective use of the cores available." +msgstr "" + +#: ./doc/install-guide/object-storage/section_object-storage-sys-requirements.xml:58(para) +msgid "Object Storage container/account servers" +msgstr "" + +#: ./doc/install-guide/object-storage/section_object-storage-sys-requirements.xml:65(para) +msgid "Optimized for IOPS due to tracking with SQLite databases." +msgstr "" + +#: ./doc/install-guide/object-storage/section_object-storage-sys-requirements.xml:69(para) +msgid "Object Storage proxy server" +msgstr "" + +#: ./doc/install-guide/object-storage/section_object-storage-sys-requirements.xml:74(para) +msgid "Higher network throughput offers better performance for supporting many API requests." +msgstr "" + +#: ./doc/install-guide/object-storage/section_object-storage-sys-requirements.xml:77(para) +msgid "Optimize your proxy servers for best CPU performance. The Proxy Services are more CPU and network I/O intensive. If you are using 10 GB networking to the proxy, or are terminating SSL traffic at the proxy, greater CPU power is required." +msgstr "" + +#: ./doc/install-guide/object-storage/section_object-storage-sys-requirements.xml:86(para) +msgid "Operating system: OpenStack Object Storage currently runs on Ubuntu, RHEL, CentOS, Fedora, openSUSE, or SLES." +msgstr "" + +#: ./doc/install-guide/object-storage/section_object-storage-sys-requirements.xml:89(para) +msgid "Networking: 1Gpbs or 10 Gbps is suggested internally. For OpenStack Object Storage, an external network should connect the outside world to the proxy servers, and the storage network is intended to be isolated on a private network or multiple private networks." +msgstr "" + +#: ./doc/install-guide/object-storage/section_object-storage-sys-requirements.xml:94(para) +msgid "Database: For OpenStack Object Storage, a SQLite database is part of the OpenStack Object Storage container and account management process." +msgstr "" + +#: ./doc/install-guide/object-storage/section_object-storage-sys-requirements.xml:98(para) +msgid "Permissions: You can install OpenStack Object Storage either as root or as a user with sudo permissions if you configure the sudoers file to enable all the permissions." +msgstr "" + +#. Put one translator per line, in the form of NAME , YEAR1, YEAR2 +#: ./doc/install-guide/object-storage/section_object-storage-sys-requirements.xml:0(None) +msgid "translator-credits" +msgstr "" + diff --git a/doc/security-guide/locale/he_IL.po b/doc/security-guide/locale/he_IL.po new file mode 100644 index 0000000000..49701de2a8 --- /dev/null +++ b/doc/security-guide/locale/he_IL.po @@ -0,0 +1,9996 @@ +# +# Translators: +msgid "" +msgstr "" +"Project-Id-Version: OpenStack Manuals\n" +"POT-Creation-Date: 2014-01-30 06:24+0000\n" +"PO-Revision-Date: 2014-01-29 18:42+0000\n" +"Last-Translator: openstackjenkins \n" +"Language-Team: Hebrew (Israel) (http://www.transifex.com/projects/p/openstack/language/he_IL/)\n" +"MIME-Version: 1.0\n" +"Content-Type: text/plain; charset=UTF-8\n" +"Content-Transfer-Encoding: 8bit\n" +"Language: he_IL\n" +"Plural-Forms: nplurals=2; plural=(n != 1);\n" + +#. When image changes, this message will be marked fuzzy or untranslated for +#. you. +#. It doesn't matter what you translate it to: it's not used at all. +#: ./doc/security-guide/ch002_why-and-how-we-wrote-this-book.xml30(None) +#: ./doc/security-guide/ch002_why-and-how-we-wrote-this-book.xml33(None) +msgid "@@image: 'static/group.png'; md5=aec1f0af66d29c1a5d1f174df1f12812" +msgstr "" + +#: ./doc/security-guide/ch002_why-and-how-we-wrote-this-book.xml3(title) +msgid "Why and how we wrote this book" +msgstr "" + +#: ./doc/security-guide/ch002_why-and-how-we-wrote-this-book.xml4(para) +msgid "" +"As OpenStack adoption continues to grow and the product matures, security " +"has become a priority. The OpenStack Security Group has recognized the need " +"for a comprehensive and authoritative security guide. The OpenStack Security Guide has been written to " +"provide an overview of security best practices, guidelines, and " +"recommendations for increasing the security of an OpenStack deployment. The " +"authors bring their expertise from deploying and securing OpenStack in a " +"variety of environments." +msgstr "" + +#: ./doc/security-guide/ch002_why-and-how-we-wrote-this-book.xml5(para) +msgid "" +"The guide augments the OpenStack Operations " +"Guide and can be referenced to harden existing OpenStack " +"deployments or to evaluate the security controls of OpenStack cloud " +"providers." +msgstr "" + +#: ./doc/security-guide/ch002_why-and-how-we-wrote-this-book.xml7(title) +msgid "Objectives" +msgstr "" + +#: ./doc/security-guide/ch002_why-and-how-we-wrote-this-book.xml9(para) +msgid "Identify the security domains in OpenStack" +msgstr "" + +#: ./doc/security-guide/ch002_why-and-how-we-wrote-this-book.xml12(para) +msgid "Provide guidance to secure your OpenStack deployment" +msgstr "" + +#: ./doc/security-guide/ch002_why-and-how-we-wrote-this-book.xml15(para) +msgid "" +"Highlight security concerns and potential mitigations in present day " +"OpenStack" +msgstr "" + +#: ./doc/security-guide/ch002_why-and-how-we-wrote-this-book.xml18(para) +msgid "Discuss upcoming security features" +msgstr "" + +#: ./doc/security-guide/ch002_why-and-how-we-wrote-this-book.xml21(para) +msgid "" +"To provide a community driven facility for knowledge capture and " +"dissemination" +msgstr "" + +#: ./doc/security-guide/ch002_why-and-how-we-wrote-this-book.xml26(title) +msgid "How" +msgstr "" + +#: ./doc/security-guide/ch002_why-and-how-we-wrote-this-book.xml27(para) +msgid "" +"As with the OpenStack Operations Guide, we followed the book sprint " +"methodology. The book sprint process allows for rapid development and " +"production of large bodies of written work. Coordinators from the OpenStack " +"Security Group re-enlisted the services of Adam Hyde as facilitator. " +"Corporate support was obtained and the project was formally announced during" +" the OpenStack summit in Portland, Oregon." +msgstr "" + +#: ./doc/security-guide/ch002_why-and-how-we-wrote-this-book.xml28(para) +msgid "" +"The team converged in Annapolis, MD due to the close proximity of some key " +"members of the group. This was a remarkable collaboration between public " +"sector intelligence community members, silicon valley startups and some " +"large, well-known technology companies. The book sprint ran during the last " +"week in June 2013 and the first edition was created in five days." +msgstr "" + +#: ./doc/security-guide/ch002_why-and-how-we-wrote-this-book.xml36(para) +msgid "The team included:" +msgstr "" + +#: ./doc/security-guide/ch002_why-and-how-we-wrote-this-book.xml39(para) +msgid "Bryan D. Payne, Nebula" +msgstr "" + +#: ./doc/security-guide/ch002_why-and-how-we-wrote-this-book.xml40(para) +msgid "" +"Dr. Bryan D. Payne is the Director of Security Research at Nebula and co-" +"founder of the OpenStack Security Group (OSSG). Prior to joining Nebula, he " +"worked at Sandia National Labs, the National Security Agency, BAE Systems, " +"and IBM Research. He graduated with a Ph.D. in Computer Science from the " +"Georgia Tech College of Computing, specializing in systems security." +msgstr "" + +#: ./doc/security-guide/ch002_why-and-how-we-wrote-this-book.xml43(para) +msgid "Robert Clark, HP" +msgstr "" + +#: ./doc/security-guide/ch002_why-and-how-we-wrote-this-book.xml44(para) +msgid "" +"Robert Clark is the Lead Security Architect for HP Cloud Services and co-" +"founder of the OpenStack Security Group (OSSG). Prior to being recruited by " +"HP, he worked in the UK Intelligence Community. Robert has a strong " +"background in threat modeling, security architecture and virtualization " +"technology. Robert has a master's degree in Software Engineering from the " +"University of Wales." +msgstr "" + +#: ./doc/security-guide/ch002_why-and-how-we-wrote-this-book.xml47(para) +msgid "Keith Basil, Red Hat" +msgstr "" + +#: ./doc/security-guide/ch002_why-and-how-we-wrote-this-book.xml48(para) +msgid "" +"Keith Basil is a Principal Product Manager for Red Hat OpenStack and is " +"focused on Red Hat's OpenStack product management, development and strategy." +" Within the US public sector, Basil brings previous experience from the " +"design of an authorized, secure, high-performance cloud architecture for " +"Federal civilian agencies and contractors." +msgstr "" + +#: ./doc/security-guide/ch002_why-and-how-we-wrote-this-book.xml51(para) +msgid "Cody Bunch, Rackspace" +msgstr "" + +#: ./doc/security-guide/ch002_why-and-how-we-wrote-this-book.xml52(para) +msgid "" +"Cody Bunch is a Private Cloud architect with Rackspace. Cody has co-authored" +" an update to \"The OpenStack Cookbook\" as well as books on VMware " +"automation." +msgstr "" + +#: ./doc/security-guide/ch002_why-and-how-we-wrote-this-book.xml55(para) +msgid "Malini Bhandaru, Intel" +msgstr "" + +#: ./doc/security-guide/ch002_why-and-how-we-wrote-this-book.xml56(para) +msgid "" +"Malini Bhandaru is a security architect at Intel. She has a varied " +"background, having worked on platform power and performance at Intel, speech" +" products at Nuance, remote monitoring and management at ComBrio, and web " +"commerce at Verizon. She has a Ph.D. in Artificial Intelligence from the " +"University of Massachusetts, Amherst." +msgstr "" + +#: ./doc/security-guide/ch002_why-and-how-we-wrote-this-book.xml59(para) +msgid "" +"Gregg Tally, Johns Hopkins University " +"Applied Physics Laboratory" +msgstr "" + +#: ./doc/security-guide/ch002_why-and-how-we-wrote-this-book.xml60(para) +msgid "" +"Gregg Tally is the Chief Engineer at JHU/APL's Cyber Systems Group within " +"the Asymmetric Operations Department. He works primarily in systems security" +" engineering. Previously, he has worked at SPARTA, McAfee, and Trusted " +"Information Systems where he was involved in cyber security research " +"projects." +msgstr "" + +#: ./doc/security-guide/ch002_why-and-how-we-wrote-this-book.xml63(para) +msgid "Eric Lopez, Nicira / VMware" +msgstr "" + +#: ./doc/security-guide/ch002_why-and-how-we-wrote-this-book.xml64(para) +msgid "" +"Eric Lopez is Senior Solution Architect at VMware's Networking and Security " +"Business Unit where he helps customer implement OpenStack and Nicira's " +"Network Virtualization Platform. Prior to joining Nicira, he worked for Q1 " +"Labs, Symantec, Vontu, and Brightmail. He has a B.S in Electrical " +"Engineering/Computer Science and Nuclear Engineering from U.C. Berkeley and " +"MBA from the University of San Francisco." +msgstr "" + +#: ./doc/security-guide/ch002_why-and-how-we-wrote-this-book.xml67(para) +msgid "Shawn Wells, Red Hat" +msgstr "" + +#: ./doc/security-guide/ch002_why-and-how-we-wrote-this-book.xml68(para) +msgid "" +"Shawn Wells is the Director, Innovation Programs at Red Hat, focused on " +"improving the process of adopting, contributing to, and managing open source" +" technologies within the U.S. Government. Additionally, Shawn is an upstream" +" maintainer of the SCAP Security Guide project which forms virtualization " +"and operating system hardening policy with the U.S. Military, NSA, and DISA." +" Formerly an NSA civilian, Shawn developed SIGINT collection systems " +"utilizing large distributed computing infrastructures." +msgstr "" + +#: ./doc/security-guide/ch002_why-and-how-we-wrote-this-book.xml71(para) +msgid "Ben de Bont, HP" +msgstr "" + +#: ./doc/security-guide/ch002_why-and-how-we-wrote-this-book.xml72(para) +msgid "" +"Ben de Bont is the CSO for HP Cloud Services. Prior to his current role Ben " +"led the information security group at MySpace and the incident response team" +" at MSN Security. Ben holds a master's degree in Computer Science from the " +"Queensland University of Technology." +msgstr "" + +#: ./doc/security-guide/ch002_why-and-how-we-wrote-this-book.xml75(para) +msgid "" +"Nathanael Burton, National Security " +"Agency" +msgstr "" + +#: ./doc/security-guide/ch002_why-and-how-we-wrote-this-book.xml76(para) +msgid "" +"Nathanael Burton is a Computer Scientist at the National Security Agency. He" +" has worked for the Agency for over 10 years working on distributed systems," +" large-scale hosting, open source initiatives, operating systems, security, " +"storage, and virtualization technology. He has a B.S. in Computer Science " +"from Virginia Tech." +msgstr "" + +#: ./doc/security-guide/ch002_why-and-how-we-wrote-this-book.xml79(emphasis) +msgid "Vibha Fauver" +msgstr "" + +#: ./doc/security-guide/ch002_why-and-how-we-wrote-this-book.xml80(para) +msgid "" +"Vibha Fauver, GWEB, CISSP, PMP, has over fifteen years of experience in " +"Information Technology. Her areas of specialization include software " +"engineering, project management and information security. She has a B.S. in " +"Computer & Information Science and a M.S. in Engineering Management with" +" specialization and a certificate in Systems Engineering." +msgstr "" + +#: ./doc/security-guide/ch002_why-and-how-we-wrote-this-book.xml83(para) +msgid "Eric Windisch, Cloudscaling" +msgstr "" + +#: ./doc/security-guide/ch002_why-and-how-we-wrote-this-book.xml84(para) +msgid "" +"Eric Windisch is a Principal Engineer at Cloudscaling where he has been " +"contributing to OpenStack for over two years. Eric has been in the trenches " +"of hostile environments, building tenant isolation and infrastructure " +"security through more than a decade of experience in the web hosting " +"industry. He has been building cloud computing infrastructure and automation" +" since 2007." +msgstr "" + +#: ./doc/security-guide/ch002_why-and-how-we-wrote-this-book.xml87(para) +msgid "Andrew Hay, CloudPassage" +msgstr "" + +#: ./doc/security-guide/ch002_why-and-how-we-wrote-this-book.xml88(para) +msgid "" +"Andrew Hay is the Director of Applied Security Research at CloudPassage, " +"Inc. where he leads the security research efforts for the company and its " +"server security products purpose-built for dynamic public, private, and " +"hybrid cloud hosting environments." +msgstr "" + +#: ./doc/security-guide/ch002_why-and-how-we-wrote-this-book.xml91(emphasis) +msgid "Adam Hyde" +msgstr "" + +#: ./doc/security-guide/ch002_why-and-how-we-wrote-this-book.xml92(para) +msgid "" +"Adam facilitated this Book Sprint. He also founded the Book Sprint " +"methodology and is the most experienced Book Sprint facilitator around. Adam" +" founded FLOSS Manuals—a community of some 3,000 individuals developing Free" +" Manuals about Free Software. He is also the founder and project manager for" +" Booktype, an open source project for writing, editing, and publishing books" +" online and in print." +msgstr "" + +#: ./doc/security-guide/ch002_why-and-how-we-wrote-this-book.xml95(para) +msgid "" +"During the sprint we also had help from Anne Gentle, Warren Wang, Paul " +"McMillan, Brian Schott and Lorin Hochstein." +msgstr "" + +#: ./doc/security-guide/ch002_why-and-how-we-wrote-this-book.xml96(para) +msgid "" +"This Book was produced in a 5 day book sprint. A book sprint is an intensely" +" collaborative, facilitated process which brings together a group to produce" +" a book in 3-5 days. It is a strongly facilitated process with a specific " +"methodology founded and developed by Adam Hyde. For more information visit " +"the book sprint web page at http://www.booksprints.net." +msgstr "" + +#: ./doc/security-guide/ch002_why-and-how-we-wrote-this-book.xml104(para) +msgid "After initial publication, the following added new content:" +msgstr "" + +#: ./doc/security-guide/ch002_why-and-how-we-wrote-this-book.xml107(para) +msgid "Rodney D. Beede, Seagate Technology" +msgstr "" + +#: ./doc/security-guide/ch002_why-and-how-we-wrote-this-book.xml110(para) +msgid "" +"Rodney D. Beede is the Cloud Security Engineer for Seagate Technology. He " +"contributed the missing chapter on securing OpenStack Object Storage " +"(Swift). He holds a M.S. in Computer Science from the University of " +"Colorado." +msgstr "" + +#: ./doc/security-guide/ch002_why-and-how-we-wrote-this-book.xml119(title) +msgid "How to contribute to this book" +msgstr "" + +#: ./doc/security-guide/ch002_why-and-how-we-wrote-this-book.xml120(para) +msgid "" +"The initial work on this book was conducted in an overly air-conditioned " +"room that served as our group office for the entirety of the documentation " +"sprint." +msgstr "" + +#: ./doc/security-guide/ch002_why-and-how-we-wrote-this-book.xml123(para) +msgid "" +"Learn more about how to contribute to the OpenStack docs: http://wiki.openstack.org/Documentation/HowTo." +msgstr "" + +#: ./doc/security-guide/ch051_vss-intro.xml3(title) +msgid "Hypervisor Selection" +msgstr "" + +#: ./doc/security-guide/ch051_vss-intro.xml4(para) +msgid "" +"Virtualization provides flexibility and other key benefits that enable cloud" +" building. However, a virtualization stack also needs to be secured " +"appropriately to reduce the risks associated with hypervisor breakout " +"attacks. That is, while a virtualization stack can provide isolation between" +" instances, or guest virtual machines, there are situations where that " +"isolation can be less than perfect. Making intelligent selections for " +"virtualization stack as well as following the best practices outlined in " +"this chapter can be included in a layered approach to cloud security. " +"Finally, securing your virtualization stack is critical in order to deliver " +"on the promise of multi-tenant, either between customers in a public cloud, " +"between business units in a private cloud, or some mixture of the two in a " +"hybrid cloud." +msgstr "" + +#: ./doc/security-guide/ch051_vss-intro.xml17(para) +msgid "" +"In this chapter, we discuss the hypervisor selection process.  In the " +"chapters that follow, we provide the foundational information needed for " +"securing a virtualization stack." +msgstr "" + +#: ./doc/security-guide/ch051_vss-intro.xml19(title) +msgid "Hypervisors in OpenStack" +msgstr "" + +#: ./doc/security-guide/ch051_vss-intro.xml20(para) +msgid "" +"Whether OpenStack is deployed within private data centers or as a public " +"cloud service, the underlying virtualization technology provides enterprise-" +"level capabilities in the realms of scalability, resource efficiency, and " +"uptime. While such high-level benefits are generally available across many " +"OpenStack-supported hypervisor technologies, there are significant " +"differences in each hypervisor's security architecture and features, " +"particularly when considering the security threat vectors which are unique " +"to elastic OpenStack environments. As applications consolidate into single " +"Infrastructure as a Service (IaaS) platforms, instance isolation at the " +"hypervisor level becomes paramount. The requirement for secure isolation " +"holds true across commercial, government, and military communities." +msgstr "" + +#: ./doc/security-guide/ch051_vss-intro.xml21(para) +msgid "" +"Within the framework of OpenStack you can choose from any number of " +"hypervisor platforms and corresponding OpenStack plugins to optimize your " +"cloud environment. In the context of the OpenStack Security guide, we will " +"be highlighting hypervisor selection considerations as they pertain to " +"feature sets that are critical to security. However, these considerations " +"are not meant to be an exhaustive investigation into the pros and cons of " +"particular hypervisors. NIST provides additional guidance in Special " +"Publication 800-125, \"Guide to Security for Full Virtualization " +"Technologies\"." +msgstr "" + +#: ./doc/security-guide/ch051_vss-intro.xml24(title) +msgid "Selection Criteria" +msgstr "" + +#: ./doc/security-guide/ch051_vss-intro.xml25(para) +msgid "" +"As part of your hypervisor selection process, you will need to consider a " +"number of important factors to help increase your security posture. " +"Specifically, we will be looking into the following areas:" +msgstr "" + +#: ./doc/security-guide/ch051_vss-intro.xml27(para) +msgid "Team Expertise" +msgstr "" + +#: ./doc/security-guide/ch051_vss-intro.xml30(para) +msgid "Product or Project maturity" +msgstr "" + +#: ./doc/security-guide/ch051_vss-intro.xml33(para) +msgid "Certifications, Attestations" +msgstr "" + +#: ./doc/security-guide/ch051_vss-intro.xml36(para) +#: ./doc/security-guide/ch051_vss-intro.xml300(title) +msgid "Additional Security Features" +msgstr "" + +#: ./doc/security-guide/ch051_vss-intro.xml39(para) +#: ./doc/security-guide/ch051_vss-intro.xml293(title) +msgid "Hypervisor vs. Baremetal" +msgstr "" + +#: ./doc/security-guide/ch051_vss-intro.xml42(para) +#: ./doc/security-guide/ch051_vss-intro.xml255(title) +msgid "Hardware Concerns" +msgstr "" + +#: ./doc/security-guide/ch051_vss-intro.xml45(para) +#: ./doc/security-guide/ch051_vss-intro.xml79(title) +msgid "Common Criteria" +msgstr "" + +#: ./doc/security-guide/ch051_vss-intro.xml49(para) +msgid "" +"Has the hypervisor undergone Common Criteria certification? If so, to what " +"levels?" +msgstr "" + +#: ./doc/security-guide/ch051_vss-intro.xml52(para) +msgid "Is the underlying cryptography certified by a third-party?" +msgstr "" + +#: ./doc/security-guide/ch051_vss-intro.xml48(para) +msgid "" +"Additionally, the following security-related criteria are highly encouraged " +"to be evaluated when selecting a hypervisor for OpenStack " +"deployments:Team Expertise Most " +"likely, the most important aspect in hypervisor selection is the expertise " +"of your staff in managing and maintaining a particular hypervisor platform. " +"The more familiar your team is with a given product, its configuration, and " +"its eccentricities, the less likely will there be configuration mistakes. " +"Additionally, having staff expertise spread across an organization on a " +"given hypervisor will increase availability of your systems, allow for " +"developing a segregation of duties, and mitigate problems in the event that " +"a team member is unavailable." +msgstr "" + +#: ./doc/security-guide/ch051_vss-intro.xml56(title) +msgid "Product or Project Maturity" +msgstr "" + +#: ./doc/security-guide/ch051_vss-intro.xml57(para) +msgid "" +"The maturity of a given hypervisor product or project is critical to your " +"security posture as well. Product maturity will have a number of effects " +"once you have deployed your cloud, in the context of this security guide we " +"are interested in the following:" +msgstr "" + +#: ./doc/security-guide/ch051_vss-intro.xml59(para) +msgid "Availability of expertise" +msgstr "" + +#: ./doc/security-guide/ch051_vss-intro.xml62(para) +msgid "Active developer and user communities" +msgstr "" + +#: ./doc/security-guide/ch051_vss-intro.xml65(para) +msgid "Timeliness and Availability of updates" +msgstr "" + +#: ./doc/security-guide/ch051_vss-intro.xml68(para) +msgid "Incidence response" +msgstr "" + +#: ./doc/security-guide/ch051_vss-intro.xml71(para) +msgid "" +"One of the biggest indicators of a hypervisor's maturity is the size and " +"vibrancy of the community that surrounds it. As this concerns security, the " +"quality of the community will affect the availability of expertise should " +"you need additional cloud operators. It is also a sign of how widely " +"deployed the hypervisor is, in turn leading to the battle readiness of any " +"reference architectures and best practices." +msgstr "" + +#: ./doc/security-guide/ch051_vss-intro.xml72(para) +msgid "" +"Further, the quality of community, as it surrounds an open source hypervisor" +" like KVM or Xen, will have a direct impact on the timeliness of bug fixes " +"and security updates. When investigating both commercial and open source " +"hypervisors, you will want to look into their release and support cycles as " +"well as the time delta between the announcement of a bug or security issue " +"and a patch or response. Lastly, the supported capabilities of OpenStack " +"compute vary depending on the hypervisor chosen. Refer to the OpenStack " +"Hypervisor Support Matrix for OpenStack compute feature support by " +"hypervisor." +msgstr "" + +#: ./doc/security-guide/ch051_vss-intro.xml75(title) +msgid "Certifications and Attestations" +msgstr "" + +#: ./doc/security-guide/ch051_vss-intro.xml76(para) +msgid "" +"One additional consideration when selecting a hypervisor is the availability" +" of various formal certifications and attestations. While they may not be " +"requirements for your specific organization, these certifications and " +"attestations speak to the maturity, production readiness, and thoroughness " +"of the testing a particular hypervisor platform has been subjected to." +msgstr "" + +#: ./doc/security-guide/ch051_vss-intro.xml80(para) +msgid "" +"Common Criteria is an internationally standardized software evaluation " +"process, used by governments and commercial companies to validate software " +"technologies perform as advertised. In the government sector, NSTISSP No. 11" +" mandates that U.S. Government agencies only procure software which has been" +" Common Criteria certified, a policy which has been in place since July " +"2002. It should be specifically noted that OpenStack has not undergone " +"Common Criteria certification, however many of the available hypervisors " +"have." +msgstr "" + +#: ./doc/security-guide/ch051_vss-intro.xml81(para) +msgid "" +"In addition to validating a technologies capabilities, the Common Criteria " +"process evaluates how technologies are developed." +msgstr "" + +#: ./doc/security-guide/ch051_vss-intro.xml83(para) +msgid "How is source code management performed?" +msgstr "" + +#: ./doc/security-guide/ch051_vss-intro.xml86(para) +msgid "How are users granted access to build systems?" +msgstr "" + +#: ./doc/security-guide/ch051_vss-intro.xml89(para) +msgid "Is the technology cryptographically signed before distribution?" +msgstr "" + +#: ./doc/security-guide/ch051_vss-intro.xml92(para) +msgid "" +"The KVM hypervisor has been Common Criteria certified through the U.S. " +"Government and commercial distributions, which have been validated to " +"separate the runtime environment of virtual machines from each other, " +"providing foundational technology to enforce instance isolation. In addition" +" to virtual machine isolation, KVM has been Common Criteria certified to" +msgstr "" + +#: ./doc/security-guide/ch051_vss-intro.xml94(para) +msgid "" +"\"provide system-inherent separation mechanisms to the resources " +"of virtual machines. This separation ensures that large software component " +"used for virtualizing and simulating devices executing for each virtual " +"machine cannot interfere with each other. Using the SELinux multi-category " +"mechanism, the virtualization and simulation software instances are " +"isolated. The virtual machine management framework configures SELinux multi-" +"category settings transparently to the administrator\"" +msgstr "" + +#: ./doc/security-guide/ch051_vss-intro.xml96(para) +msgid "" +"While many hypervisor vendors, such as Red Hat, Microsoft, and VMWare have " +"achieved Common Criteria Certification their underlying certified feature " +"set differs. It is recommended to evaluate vendor claims to ensure they " +"minimally satisfy the following requirements:" +msgstr "" + +#: ./doc/security-guide/ch051_vss-intro.xml103(para) +msgid "Identification and Authentication" +msgstr "" + +#: ./doc/security-guide/ch051_vss-intro.xml104(para) +msgid "" +"Identification and authentication using pluggable authentication modules " +"(PAM) based upon user passwords. The quality of the passwords used can be " +"enforced through configuration options." +msgstr "" + +#: ./doc/security-guide/ch051_vss-intro.xml107(para) +msgid "Audit" +msgstr "" + +#: ./doc/security-guide/ch051_vss-intro.xml108(para) +msgid "" +"The system provides the capability to audit a large number of events " +"including individual system calls as well as events generated by trusted " +"processes. Audit data is collected in regular files in ASCII format. The " +"system provides a program for the purpose of searching the audit records." +msgstr "" + +#: ./doc/security-guide/ch051_vss-intro.xml108(para) +msgid "" +"The system administrator can define a rule base to restrict auditing to the " +"events they are interested in. This includes the ability to restrict " +"auditing to specific events, specific users, specific objects or a " +"combination of all of this. " +msgstr "" + +#: ./doc/security-guide/ch051_vss-intro.xml108(para) +msgid "Audit records can be transferred to a remote audit daemon." +msgstr "" + +#: ./doc/security-guide/ch051_vss-intro.xml111(para) +msgid "Discretionary Access Control" +msgstr "" + +#: ./doc/security-guide/ch051_vss-intro.xml113(para) +msgid "" +"Discretionary Access Control (DAC) restricts access " +"to file system objects based on Access Control Lists (ACLs) that include the standard " +"UNIX permissions for user, group and others. Access control mechanisms also " +"protect IPC objects from unauthorized access." +msgstr "" + +#: ./doc/security-guide/ch051_vss-intro.xml122(para) +msgid "" +"The system includes the ext4 file system, which supports POSIX ACLs. This " +"allows defining access rights to files within this type of file system down " +"to the granularity of a single user." +msgstr "" + +#: ./doc/security-guide/ch051_vss-intro.xml130(para) +msgid "Mandatory Access Control" +msgstr "" + +#: ./doc/security-guide/ch051_vss-intro.xml131(para) +msgid "" +"Mandatory Access Control (MAC) restricts access to objects based on labels " +"assigned to subjects and objects. Sensitivity labels are automatically " +"attached to processes and objects. The access control policy enforced using " +"these labels is derived from the BellLaPadula access control model." +msgstr "" + +#: ./doc/security-guide/ch051_vss-intro.xml131(para) +msgid "" +"SELinux categories are attached to virtual machines and its resources. The " +"access control policy enforced using these categories grant virtual machines" +" access to resources if the category of the virtual machine is identical to " +"the category of the accessed resource." +msgstr "" + +#: ./doc/security-guide/ch051_vss-intro.xml131(para) +msgid "" +"The TOE implements non-hierarchical categories to control access to virtual " +"machines." +msgstr "" + +#: ./doc/security-guide/ch051_vss-intro.xml134(para) +msgid "Role-Based Access Control" +msgstr "" + +#: ./doc/security-guide/ch051_vss-intro.xml135(para) +msgid "" +"Role-based access control (RBAC) allows separation of roles to eliminate the" +" need for an all-powerful system administrator." +msgstr "" + +#: ./doc/security-guide/ch051_vss-intro.xml138(para) +msgid "Object Reuse" +msgstr "" + +#: ./doc/security-guide/ch051_vss-intro.xml139(para) +msgid "" +"File system objects as well as memory and IPC objects will be cleared before" +" they can be reused by a process belonging to a different user." +msgstr "" + +#: ./doc/security-guide/ch051_vss-intro.xml142(para) +msgid "Security Management" +msgstr "" + +#: ./doc/security-guide/ch051_vss-intro.xml143(para) +msgid "" +"The management of the security critical parameters of the system is " +"performed by administrative users. A set of commands that require root " +"privileges (or specific roles when RBAC is used) are used for system " +"management. Security parameters are stored in specific files that are " +"protected by the access control mechanisms of the system against " +"unauthorized access by users that are not administrative users." +msgstr "" + +#: ./doc/security-guide/ch051_vss-intro.xml146(para) +msgid "Secure Communication" +msgstr "" + +#: ./doc/security-guide/ch051_vss-intro.xml147(para) +msgid "" +"The system supports the definition of trusted channels using SSH. Password " +"based authentication is supported. Only a restricted number of cipher suites" +" are supported for those protocols in the evaluated configuration." +msgstr "" + +#: ./doc/security-guide/ch051_vss-intro.xml150(para) +msgid "Storage Encryption" +msgstr "" + +#: ./doc/security-guide/ch051_vss-intro.xml151(para) +msgid "" +"The system supports encrypted block devices to provide storage " +"confidentiality via dm_crypt." +msgstr "" + +#: ./doc/security-guide/ch051_vss-intro.xml154(para) +msgid "TSF Protection" +msgstr "" + +#: ./doc/security-guide/ch051_vss-intro.xml155(para) +msgid "" +"While in operation, the kernel software and data are protected by the " +"hardware memory protection mechanisms. The memory and process management " +"components of the kernel ensure a user process cannot access kernel storage " +"or storage belonging to other processes." +msgstr "" + +#: ./doc/security-guide/ch051_vss-intro.xml155(para) +msgid "" +"Non-kernel TSF software and data are protected by DAC and process isolation" +"  mechanisms. In the evaluated configuration, the reserved user ID root owns" +" the directories and files that define the TSF configuration. In general, " +"files and directories containing internal TSF data, such as configuration " +"files and batch job queues, are also protected from reading by DAC " +"permissions." +msgstr "" + +#: ./doc/security-guide/ch051_vss-intro.xml162(para) +msgid "" +"The system and the hardware and firmware components are required to be " +"physically protected from unauthorized access. The system kernel mediates " +"all access to the hardware mechanisms themselves, other than program visible" +" CPU instruction functions." +msgstr "" + +#: ./doc/security-guide/ch051_vss-intro.xml162(para) +msgid "" +"In addition, mechanisms for protection against stack overflow attacks are " +"provided." +msgstr "" + +#: ./doc/security-guide/ch051_vss-intro.xml169(title) +msgid "Cryptography Standards" +msgstr "" + +#: ./doc/security-guide/ch051_vss-intro.xml170(para) +msgid "" +"Several cryptography algorithms are available within OpenStack for " +"identification and authorization, data transfer and protection of data at " +"rest. When selecting a hypervisor, the following are recommended algorithms " +"and implementation standards to ensure the virtualization layer supports:" +msgstr "" + +#: ./doc/security-guide/ch051_vss-intro.xml180(emphasis) +msgid "Algorithm" +msgstr "" + +#: ./doc/security-guide/ch051_vss-intro.xml181(emphasis) +msgid "Key Length" +msgstr "" + +#: ./doc/security-guide/ch051_vss-intro.xml182(emphasis) +msgid "Intended Purpose" +msgstr "" + +#: ./doc/security-guide/ch051_vss-intro.xml183(emphasis) +msgid "Security Function" +msgstr "" + +#: ./doc/security-guide/ch051_vss-intro.xml184(emphasis) +msgid "Implementation Standard" +msgstr "" + +#: ./doc/security-guide/ch051_vss-intro.xml187(para) +msgid "AES" +msgstr "" + +#: ./doc/security-guide/ch051_vss-intro.xml188(para) +msgid "128 bits,192 bits," +msgstr "" + +#: ./doc/security-guide/ch051_vss-intro.xml188(para) +msgid "256 bits" +msgstr "" + +#: ./doc/security-guide/ch051_vss-intro.xml189(para) +#: ./doc/security-guide/ch051_vss-intro.xml196(para) +msgid "Encryption / Decryption" +msgstr "" + +#: ./doc/security-guide/ch051_vss-intro.xml190(para) +msgid "Protected Data Transfer, Protection for Data at Rest" +msgstr "" + +#: ./doc/security-guide/ch051_vss-intro.xml191(para) +#: ./doc/security-guide/ch051_vss-intro.xml198(para) +msgid "RFC 4253" +msgstr "" + +#: ./doc/security-guide/ch051_vss-intro.xml194(para) +msgid "TDES" +msgstr "" + +#: ./doc/security-guide/ch051_vss-intro.xml195(para) +msgid "168 bits" +msgstr "" + +#: ./doc/security-guide/ch051_vss-intro.xml197(para) +msgid "Protected Data Transfer" +msgstr "" + +#: ./doc/security-guide/ch051_vss-intro.xml201(para) +msgid "RSA" +msgstr "" + +#: ./doc/security-guide/ch051_vss-intro.xml202(para) +msgid "1024 bits,2048 bits," +msgstr "" + +#: ./doc/security-guide/ch051_vss-intro.xml202(para) +msgid "3072 bits " +msgstr "" + +#: ./doc/security-guide/ch051_vss-intro.xml203(para) +#: ./doc/security-guide/ch051_vss-intro.xml210(para) +msgid "Authentication,Key Exchange " +msgstr "" + +#: ./doc/security-guide/ch051_vss-intro.xml204(para) +#: ./doc/security-guide/ch051_vss-intro.xml211(para) +msgid "Identification and Authentication, Protected Data Transfer" +msgstr "" + +#: ./doc/security-guide/ch051_vss-intro.xml205(para) +#: ./doc/security-guide/ch051_vss-intro.xml212(para) +msgid "U.S. NIST FIPS PUB 186-3" +msgstr "" + +#: ./doc/security-guide/ch051_vss-intro.xml208(para) +msgid "DSA" +msgstr "" + +#: ./doc/security-guide/ch051_vss-intro.xml209(para) +msgid "L=1024,N=160 bits " +msgstr "" + +#: ./doc/security-guide/ch051_vss-intro.xml215(para) +msgid "Serpent" +msgstr "" + +#: ./doc/security-guide/ch051_vss-intro.xml216(para) +#: ./doc/security-guide/ch051_vss-intro.xml223(para) +msgid "128, 196, or256 bit " +msgstr "" + +#: ./doc/security-guide/ch051_vss-intro.xml217(para) +#: ./doc/security-guide/ch051_vss-intro.xml224(para) +msgid "Encryption /Decryption " +msgstr "" + +#: ./doc/security-guide/ch051_vss-intro.xml218(para) +#: ./doc/security-guide/ch051_vss-intro.xml225(para) +msgid "Protection of Data at Rest" +msgstr "" + +#: ./doc/security-guide/ch051_vss-intro.xml219(link) +msgid "http://www.cl.cam.ac.uk/~rja14/Papers/serpent.pdf" +msgstr "" + +#: ./doc/security-guide/ch051_vss-intro.xml222(para) +msgid "Twofish" +msgstr "" + +#: ./doc/security-guide/ch051_vss-intro.xml226(link) +msgid "http://www.schneier.com/paper-twofish-paper.html" +msgstr "" + +#: ./doc/security-guide/ch051_vss-intro.xml229(para) +msgid "SHA-1" +msgstr "" + +#: ./doc/security-guide/ch051_vss-intro.xml230(para) +#: ./doc/security-guide/ch051_vss-intro.xml237(para) +msgid "-" +msgstr "" + +#: ./doc/security-guide/ch051_vss-intro.xml231(para) +#: ./doc/security-guide/ch051_vss-intro.xml238(para) +msgid "MessageDigest " +msgstr "" + +#: ./doc/security-guide/ch051_vss-intro.xml232(para) +msgid "Protection of Data at Rest,Protected Data Transfer" +msgstr "" + +#: ./doc/security-guide/ch051_vss-intro.xml233(para) +#: ./doc/security-guide/ch051_vss-intro.xml240(para) +msgid "U.S. NIST FIPS 180-3" +msgstr "" + +#: ./doc/security-guide/ch051_vss-intro.xml236(para) +msgid "SHA-2(224-, 256-," +msgstr "" + +#: ./doc/security-guide/ch051_vss-intro.xml236(para) +msgid "384-, 512 bit)" +msgstr "" + +#: ./doc/security-guide/ch051_vss-intro.xml239(para) +msgid "Protection for Data at Rest,Identification and Authentication " +msgstr "" + +#: ./doc/security-guide/ch051_vss-intro.xml246(title) +msgid "FIPS 140-2" +msgstr "" + +#: ./doc/security-guide/ch051_vss-intro.xml247(para) +msgid "" +"In the United States the National Institute of Science and Technology (NIST)" +" certifies cryptographic algorithms through a process known the " +"Cryptographic Module Validation Program. NIST certifies algorithms for " +"conformance against Federal Information Processing Standard 140-2 (FIPS " +"140-2), which ensures:" +msgstr "" + +#: ./doc/security-guide/ch051_vss-intro.xml249(emphasis) +msgid "" +"Products validated as conforming to FIPS 140-2 are accepted by the Federal " +"agencies of both countries [United States and Canada] for the protection of " +"sensitive information (United States) or Designated Information (Canada). " +"The goal of the CMVP is to promote the use of validated cryptographic " +"modules and provide Federal agencies with a security metric to use in " +"procuring equipment containing validated cryptographic modules." +msgstr "" + +#: ./doc/security-guide/ch051_vss-intro.xml251(para) +msgid "" +"When evaluating base hypervisor technologies, consider if the hypervisor has" +" been certified against FIPS 140-2. Not only is conformance against FIPS " +"140-2 mandated per U.S. Government policy, formal certification indicates " +"that a given implementation of a cryptographic algorithm has been reviewed " +"for conformance against module specification, cryptographic module ports and" +" interfaces; roles, services, and authentication; finite state model; " +"physical security; operational environment; cryptographic key management; " +"electromagnetic interference/electromagnetic compatibility (EMI/EMC); self-" +"tests; design assurance; and mitigation of other attacks." +msgstr "" + +#: ./doc/security-guide/ch051_vss-intro.xml256(para) +msgid "" +"Further, when evaluating a hypervisor platform the supportability of the " +"hardware the hypervisor will run on should be considered. Additionally, " +"consider the additional features available in the hardware and how those " +"features are supported by the hypervisor you chose as part of the OpenStack " +"deployment. To that end, hypervisors will each have their own hardware " +"compatibility lists (HCLs). When selecting compatible hardware it is " +"important to know in advance which hardware-based virtualization " +"technologies are important from a security perspective." +msgstr "" + +#: ./doc/security-guide/ch051_vss-intro.xml264(emphasis) +msgid "Description" +msgstr "" + +#: ./doc/security-guide/ch051_vss-intro.xml265(emphasis) +msgid "Technology" +msgstr "" + +#: ./doc/security-guide/ch051_vss-intro.xml266(emphasis) +msgid "Explanation" +msgstr "" + +#: ./doc/security-guide/ch051_vss-intro.xml269(para) +msgid "I/O MMU" +msgstr "" + +#: ./doc/security-guide/ch051_vss-intro.xml270(para) +msgid "VT-d / AMD-Vi" +msgstr "" + +#: ./doc/security-guide/ch051_vss-intro.xml271(para) +msgid "Required for protecting PCI-passthrough" +msgstr "" + +#: ./doc/security-guide/ch051_vss-intro.xml274(para) +msgid "Intel Trusted Execution Technology" +msgstr "" + +#: ./doc/security-guide/ch051_vss-intro.xml275(para) +msgid "Intel TXT / SEM" +msgstr "" + +#: ./doc/security-guide/ch051_vss-intro.xml276(para) +msgid "Required for dynamic attestation services" +msgstr "" + +#: ./doc/security-guide/ch051_vss-intro.xml279(para) +msgid "" +"PCI-SIG I/O " +"virtualization" +msgstr "" + +#: ./doc/security-guide/ch051_vss-intro.xml280(para) +msgid "SR-IOV, MR-IOV, ATS" +msgstr "" + +#: ./doc/security-guide/ch051_vss-intro.xml281(para) +msgid "Required to allow secure sharing of PCI Express devices" +msgstr "" + +#: ./doc/security-guide/ch051_vss-intro.xml284(para) +msgid "Network virtualization" +msgstr "" + +#: ./doc/security-guide/ch051_vss-intro.xml285(para) +msgid "VT-c" +msgstr "" + +#: ./doc/security-guide/ch051_vss-intro.xml286(para) +msgid "Improves performance of network I/O on hypervisors" +msgstr "" + +#: ./doc/security-guide/ch051_vss-intro.xml294(para) +msgid "" +"To wrap up our discussion around hypervisor selection, it is important to " +"call out the differences between using LXC (Linux Containers) or Baremetal " +"systems vs using a hypervisor like KVM. Specifically, the focus of this " +"security guide will be largely based on having a hypervisor and " +"virtualization platform. However, should your implementation require the use" +" of a baremetal or LXC environment, you will want to pay attention to the " +"particular differences in regard to deployment of that environment. In " +"particular, you will need to provide your end users with assurances that the" +" node has been properly sanitized of their data prior to re-provisioning. " +"Additionally, prior to reusing a node, you will need to provide assurances " +"that the hardware has not been tampered or otherwise compromised." +msgstr "" + +#: ./doc/security-guide/ch051_vss-intro.xml295(para) +msgid "" +"It should be noted that while OpenStack has a baremetal project, a " +"discussion of the particular security implications of running baremetal is " +"beyond the scope of this book." +msgstr "" + +#: ./doc/security-guide/ch051_vss-intro.xml296(para) +msgid "" +"Finally, due to the time constraints around a book sprint, the team chose to" +" use KVM as the hypervisor in our example implementations and architectures." +msgstr "" + +#: ./doc/security-guide/ch051_vss-intro.xml297(para) +msgid "" +"There is an OpenStack Security Note pertaining to the use of LXC in " +"Nova." +msgstr "" + +#: ./doc/security-guide/ch051_vss-intro.xml301(para) +msgid "" +"Another thing to look into when selecting a hypervisor platform is the " +"availability of specific security features. In particular, we are referring " +"to features like Xen Server's XSM or Xen Security Modules, sVirt, Intel TXT," +" and AppArmor. The presence of these features will help increase your " +"security profile as well as provide a good foundation." +msgstr "" + +#: ./doc/security-guide/ch051_vss-intro.xml302(para) +msgid "" +"The following table calls out these features by common hypervisor platforms." +" " +msgstr "" + +#: ./doc/security-guide/ch051_vss-intro.xml315(para) +#: ./doc/security-guide/ch051_vss-intro.xml327(para) +#: ./doc/security-guide/ch051_vss-intro.xml336(para) +#: ./doc/security-guide/ch051_vss-intro.xml338(para) +#: ./doc/security-guide/ch051_vss-intro.xml340(para) +#: ./doc/security-guide/ch051_vss-intro.xml341(para) +#: ./doc/security-guide/ch051_vss-intro.xml346(para) +#: ./doc/security-guide/ch051_vss-intro.xml347(para) +#: ./doc/security-guide/ch051_vss-intro.xml348(para) +#: ./doc/security-guide/ch051_vss-intro.xml350(para) +#: ./doc/security-guide/ch051_vss-intro.xml351(para) +#: ./doc/security-guide/ch051_vss-intro.xml352(para) +#: ./doc/security-guide/ch051_vss-intro.xml356(para) +#: ./doc/security-guide/ch051_vss-intro.xml357(para) +#: ./doc/security-guide/ch051_vss-intro.xml358(para) +#: ./doc/security-guide/ch051_vss-intro.xml359(para) +#: ./doc/security-guide/ch051_vss-intro.xml360(para) +#: ./doc/security-guide/ch051_vss-intro.xml361(para) +#: ./doc/security-guide/ch051_vss-intro.xml362(para) +#: ./doc/security-guide/ch012_configuration-management.xml95(para) +#: ./doc/security-guide/ch012_configuration-management.xml100(emphasis) +msgid " " +msgstr "" + +#: ./doc/security-guide/ch051_vss-intro.xml316(para) +msgid "KSM" +msgstr "" + +#: ./doc/security-guide/ch051_vss-intro.xml317(para) +msgid "XSM" +msgstr "" + +#: ./doc/security-guide/ch051_vss-intro.xml318(para) +msgid "sVirt" +msgstr "" + +#: ./doc/security-guide/ch051_vss-intro.xml319(para) +msgid "TXT" +msgstr "" + +#: ./doc/security-guide/ch051_vss-intro.xml320(para) +msgid "AppArmor" +msgstr "" + +#: ./doc/security-guide/ch051_vss-intro.xml321(para) +msgid "cGroups" +msgstr "" + +#: ./doc/security-guide/ch051_vss-intro.xml322(para) +msgid "MAC Policy" +msgstr "" + +#: ./doc/security-guide/ch051_vss-intro.xml325(para) +msgid "KVM" +msgstr "" + +#: ./doc/security-guide/ch051_vss-intro.xml326(para) +#: ./doc/security-guide/ch051_vss-intro.xml328(para) +#: ./doc/security-guide/ch051_vss-intro.xml329(para) +#: ./doc/security-guide/ch051_vss-intro.xml337(para) +msgid "X" +msgstr "" + +#: ./doc/security-guide/ch051_vss-intro.xml330(address) +#: ./doc/security-guide/ch051_vss-intro.xml331(para) +#: ./doc/security-guide/ch051_vss-intro.xml332(para) +#: ./doc/security-guide/ch051_vss-intro.xml342(para) +msgid "x" +msgstr "" + +#: ./doc/security-guide/ch051_vss-intro.xml335(para) +msgid "Xen" +msgstr "" + +#: ./doc/security-guide/ch051_vss-intro.xml339(para) +#: ./doc/security-guide/ch051_vss-intro.xml349(para) +msgid " X" +msgstr "" + +#: ./doc/security-guide/ch051_vss-intro.xml345(para) +msgid "ESXi" +msgstr "" + +#: ./doc/security-guide/ch051_vss-intro.xml355(para) +msgid "Hyper-V" +msgstr "" + +#: ./doc/security-guide/ch051_vss-intro.xml367(link) +msgid "KSM: Kernel Samepage Merging" +msgstr "" + +#: ./doc/security-guide/ch051_vss-intro.xml368(link) +msgid "XSM: Xen Security Modules" +msgstr "" + +#: ./doc/security-guide/ch051_vss-intro.xml369(link) +msgid "xVirt: Mandatory Access Control for Linux-based virtualization" +msgstr "" + +#: ./doc/security-guide/ch051_vss-intro.xml370(link) +msgid "TXT: Intel Trusted Execution Technology" +msgstr "" + +#: ./doc/security-guide/ch051_vss-intro.xml371(link) +msgid "AppArmor: Linux security module implementing MAC" +msgstr "" + +#: ./doc/security-guide/ch051_vss-intro.xml372(link) +msgid "cgroups: Linux kernel feature to control resource usage" +msgstr "" + +#: ./doc/security-guide/ch051_vss-intro.xml373(para) +msgid "" +"MAC Policy: Mandatory Access Control; may be implemented with SELinux or " +"other operating systems" +msgstr "" + +#: ./doc/security-guide/ch051_vss-intro.xml374(para) +msgid "" +"* Features in this table may not be applicable to all hypervisors or " +"directly mappable between hypervisors." +msgstr "" + +#: ./doc/security-guide/ch017_threat-models-confidence-and-confidentiality.xml3(title) +msgid "Introduction to SSL/TLS" +msgstr "" + +#: ./doc/security-guide/ch017_threat-models-confidence-and-confidentiality.xml4(para) +msgid "" +"OpenStack services receive requests on behalf of users on public networks as" +" well as from other internal services over management networks. Inter-" +"service communications can also occur over public networks depending on " +"deployment and architecture choices." +msgstr "" + +#: ./doc/security-guide/ch017_threat-models-confidence-and-confidentiality.xml5(para) +msgid "" +"While it is commonly accepted that data over public networks should be " +"secured using cryptographic measures, such as Secure Sockets Layer or " +"Transport Layer Security (SSL/TLS) protocols, it is insufficient to rely on " +"security domain separation to protect internal traffic. Using a security-in-" +"depth approach, we recommend securing all domains with SSL/TLS, including " +"the management domain services. It is important that should a tenant escape " +"their VM isolation and gain access to the hypervisor or host resources, " +"compromise an API endpoint, or any other service, they must not be able to " +"easily inject or capture messages, commands, or otherwise affect or control " +"management capabilities of the cloud. SSL/TLS provides the mechanisms to " +"ensure authentication, non-repudiation, confidentiality, and integrity of " +"user communications to the OpenStack services and between the OpenStack " +"services themselves." +msgstr "" + +#: ./doc/security-guide/ch017_threat-models-confidence-and-confidentiality.xml6(para) +msgid "" +"Public Key Infrastructure (PKI) is the set of hardware, software, and " +"policies to operate a secure system which provides authentication, non-" +"repudiation, confidentiality, and integrity. The core components of PKI are:" +msgstr "" + +#: ./doc/security-guide/ch017_threat-models-confidence-and-confidentiality.xml8(para) +msgid "" +"End Entity - user, process, or system that is the subject of a certificate" +msgstr "" + +#: ./doc/security-guide/ch017_threat-models-confidence-and-confidentiality.xml11(para) +msgid "" +"Certification Authority (CA) - defines certificate " +"policies, management, and issuance of certificates" +msgstr "" + +#: ./doc/security-guide/ch017_threat-models-confidence-and-confidentiality.xml14(para) +msgid "" +"Registration Authority (RA) - an optional system to which a CA delegates " +"certain management functions" +msgstr "" + +#: ./doc/security-guide/ch017_threat-models-confidence-and-confidentiality.xml17(para) +msgid "" +"Repository - Where the end entity certificates and certificate revocation " +"lists are stored and looked up - sometimes referred to as the \"certificate " +"bundle\"" +msgstr "" + +#: ./doc/security-guide/ch017_threat-models-confidence-and-confidentiality.xml20(para) +msgid "Relying Party - The end point that is trusting that the CA is valid." +msgstr "" + +#: ./doc/security-guide/ch017_threat-models-confidence-and-confidentiality.xml23(para) +msgid "" +"PKI builds the framework on which to provide encryption algorithms, cipher " +"modes, and protocols for securing data and authentication. We strongly " +"recommend securing all services with Public Key Infrastructure (PKI), " +"including the use of SSL/TLS for API endpoints. It is impossible for the " +"encryption or signing of transports or messages alone to solve all these " +"problems. Hosts themselves must be secure and implement policy, namespaces, " +"and other controls to protect their private credentials and keys. However, " +"the challenges of key management and protection do not reduce the necessity " +"of these controls, or lessen their importance." +msgstr "" + +#: ./doc/security-guide/ch017_threat-models-confidence-and-confidentiality.xml25(title) +msgid "Certification Authorities" +msgstr "" + +#: ./doc/security-guide/ch017_threat-models-confidence-and-confidentiality.xml26(para) +msgid "" +"Many organizations have an established Public Key Infrastructure with their " +"own certification authority (CA), certificate policies, and management for " +"which they should use to issue certificates for internal OpenStack users or " +"services. Organizations in which the public security domain is Internet " +"facing will additionally need certificates signed by a widely recognized " +"public CA. For cryptographic communications over the management network, it " +"is recommended one not use a public CA. Instead, we expect and recommend " +"most deployments deploy their own internal CA." +msgstr "" + +#: ./doc/security-guide/ch017_threat-models-confidence-and-confidentiality.xml27(para) +msgid "" +"It is recommended that the OpenStack cloud architect consider using separate" +" PKI deployments for internal systems and customer facing services. This " +"allows the cloud deployer to maintain control of their PKI infrastructure " +"and among other things makes requesting, signing and deploying certificates " +"for internal systems easier. Advanced configurations may use separate PKI " +"deployments for different security domains. This allows deployers to " +"maintain cryptographic separation of environments, ensuring that " +"certificates issued to one are not recognised by another." +msgstr "" + +#: ./doc/security-guide/ch017_threat-models-confidence-and-confidentiality.xml28(para) +msgid "" +"Certificates used to support SSL/TLS on internet facing cloud endpoints (or " +"customer interfaces where the customer is not expected to have installed " +"anything other than standard operating system provided certificate bundles) " +"should be provisioned using Certificate Authorities that are installed in " +"the operating system certificate bundle. Typical well known vendors include " +"Verisign and Thawte but many others exist." +msgstr "" + +#: ./doc/security-guide/ch017_threat-models-confidence-and-confidentiality.xml29(para) +msgid "" +"There are many management, policy, and technical challenges around creating " +"and signing certificates as such is an area where cloud architects or " +"operators may wish to seek the advice of industry leaders and vendors in " +"addition to the guidance recommended here." +msgstr "" + +#: ./doc/security-guide/ch017_threat-models-confidence-and-confidentiality.xml32(title) +msgid "SSL/TLS Libraries" +msgstr "" + +#: ./doc/security-guide/ch017_threat-models-confidence-and-confidentiality.xml33(para) +msgid "" +"Various components, services, and applications within the OpenStack " +"ecosystem or dependencies of OpenStack are implemented and can be configured" +" to use SSL/TLS libraries. The SSL/TLS and HTTP services within OpenStack " +"are typically implemented using OpenSSL which has been proven to be fairly " +"secure and has a module that has been validated for FIPS 140-2. However, " +"keep in mind that each application or service can still introduce weaknesses" +" in how they use the OpenSSL libraries." +msgstr "" + +#: ./doc/security-guide/ch017_threat-models-confidence-and-confidentiality.xml36(title) +msgid "Cryptographic Algorithms, Cipher Modes, and Protocols" +msgstr "" + +#: ./doc/security-guide/ch017_threat-models-confidence-and-confidentiality.xml37(para) +msgid "" +"We recommend only using TLS v1.1 or v1.2. SSLv3 and TLSv1.0 may be used for " +"compatibility but we recommend using caution and only enabling these " +"protocols if you have a strong requirement to do so. Other SSL/TLS versions," +" explicitly older versions, should not be used. These older versions include" +" SSLv1 and SSLv2. As this book does not intend to be a thorough reference on" +" cryptography we do not wish to be prescriptive about what specific " +"algorithms or cipher modes you should enable or disable in your OpenStack " +"services. However, there are some authoritative references we would like to " +"recommend for further information:" +msgstr "" + +#: ./doc/security-guide/ch017_threat-models-confidence-and-confidentiality.xml39(link) +msgid "National Security Agency, Suite B Cryptography" +msgstr "" + +#: ./doc/security-guide/ch017_threat-models-confidence-and-confidentiality.xml42(link) +msgid "OWASP Guide to Cryptography" +msgstr "" + +#: ./doc/security-guide/ch017_threat-models-confidence-and-confidentiality.xml45(link) +msgid "OWASP Transport Layer Protection Cheat Sheet" +msgstr "" + +#: ./doc/security-guide/ch017_threat-models-confidence-and-confidentiality.xml48(link) +msgid "" +"SoK: SSL and HTTPS: Revisiting past challenges and evaluating certificate " +"trust model enhancements" +msgstr "" + +#: ./doc/security-guide/ch017_threat-models-confidence-and-confidentiality.xml51(link) +msgid "" +"The Most Dangerous Code in the World: Validating SSL Certificates in Non-" +"Browser Software" +msgstr "" + +#: ./doc/security-guide/ch017_threat-models-confidence-and-confidentiality.xml54(link) +msgid "OpenSSL and FIPS 140-2" +msgstr "" + +#: ./doc/security-guide/ch017_threat-models-confidence-and-confidentiality.xml59(title) +msgid "Summary" +msgstr "" + +#: ./doc/security-guide/ch017_threat-models-confidence-and-confidentiality.xml60(para) +msgid "" +"Given the complexity of the OpenStack components and the number of " +"deployment possibilities, you must take care to ensure that each component " +"gets the appropriate configuration of SSL certificates, keys, and CAs. The " +"following services will be discussed in later sections of this book where " +"SSL and PKI is available (either natively or possible via SSL proxy):" +msgstr "" + +#: ./doc/security-guide/ch017_threat-models-confidence-and-confidentiality.xml62(para) +msgid "Compute API endpoints" +msgstr "" + +#: ./doc/security-guide/ch017_threat-models-confidence-and-confidentiality.xml65(para) +msgid "Identity API endpoints" +msgstr "" + +#: ./doc/security-guide/ch017_threat-models-confidence-and-confidentiality.xml68(para) +msgid "Networking API endpoints" +msgstr "" + +#: ./doc/security-guide/ch017_threat-models-confidence-and-confidentiality.xml71(para) +msgid "Storage API endpoints" +msgstr "" + +#: ./doc/security-guide/ch017_threat-models-confidence-and-confidentiality.xml74(para) +msgid "Messaging server" +msgstr "" + +#: ./doc/security-guide/ch017_threat-models-confidence-and-confidentiality.xml77(para) +msgid "Database server" +msgstr "" + +#: ./doc/security-guide/ch017_threat-models-confidence-and-confidentiality.xml80(para) +#: ./doc/security-guide/ch014_best-practices-for-operator-mode-access.xml23(title) +#: ./doc/security-guide/ch004_book-introduction.xml186(title) +#: ./doc/security-guide/ch025_web-dashboard.xml8(title) +msgid "Dashboard" +msgstr "" + +#: ./doc/security-guide/ch017_threat-models-confidence-and-confidentiality.xml83(para) +msgid "" +"Throughout this book we will use SSL as shorthand to refer to these " +"recommendations for SSL/TLS protocols." +msgstr "" + +#: ./doc/security-guide/ch012_configuration-management.xml8(title) +msgid "Continuous Systems Management" +msgstr "" + +#: ./doc/security-guide/ch012_configuration-management.xml9(para) +msgid "" +"A cloud will always have bugs. Some of these will be security problems. For " +"this reason, it is critically important to be prepared to apply security " +"updates and general software updates. This involves smart use of " +"configuration management tools, which are discussed below. This also " +"involves knowing when an upgrade is necessary." +msgstr "" + +#: ./doc/security-guide/ch012_configuration-management.xml16(title) +#: ./doc/security-guide/ch063_compliance-activities.xml43(title) +msgid "Vulnerability Management" +msgstr "" + +#: ./doc/security-guide/ch012_configuration-management.xml17(para) +msgid "" +"For announcements regarding security relevant changes, subscribe to the " +"OpenStack Announce mailing list. The security " +"notifications are also posted through the downstream packages for example " +"through Linux distributions that you may be subscribed to as part of the " +"package updates." +msgstr "" + +#: ./doc/security-guide/ch012_configuration-management.xml24(para) +msgid "" +"The OpenStack components are only a small fraction of the software in a " +"cloud. It is important to keep up to date with all of these other " +"components, too. While the specific data sources will be deployment " +"specific, the key idea is to ensure that a cloud administrator subscribes to" +" the necessary mailing lists for receiving notification of any related " +"security updates. Often this is as simple as tracking an upstream Linux " +"distribution." +msgstr "" + +#: ./doc/security-guide/ch012_configuration-management.xml36(para) +msgid "" +"OpenStack Security Advisories (OSSA) are created by the OpenStack " +"Vulnerability Management Team (VMT). They pertain to security holes in core " +"OpenStack services. More information on the VMT can be found here: https://wiki.openstack.org/wiki/Vulnerability_Management" +msgstr "" + +#: ./doc/security-guide/ch012_configuration-management.xml44(para) +msgid "" +"OpenStack Security Notes (OSSN) were created by the OpenStack Security Group" +" (OSSG) to support the work of the VMT. OSSN address issues in supporting " +"software and common deployment configurations. They're referenced throughout" +" this guide. Security Notes are archived at https://launchpad.net/ossn/" +msgstr "" + +#: ./doc/security-guide/ch012_configuration-management.xml33(para) +msgid "" +"OpenStack releases security information through two channels. " +"" +msgstr "" + +#: ./doc/security-guide/ch012_configuration-management.xml56(title) +msgid "Triage" +msgstr "" + +#: ./doc/security-guide/ch012_configuration-management.xml57(para) +msgid "" +"After you are notified of a security update, the next step is to determine " +"how critical this update is to a given cloud deployment. In this case, it is" +" useful to have a pre-defined policy. Existing vulnerability rating systems " +"such as the common vulnerability scoring system (CVSS) v2 do not properly " +"account for cloud deployments." +msgstr "" + +#: ./doc/security-guide/ch012_configuration-management.xml63(para) +msgid "" +"In this example we introduce a scoring matrix that places vulnerabilities in" +" three categories: Privilege Escalation, Denial of Service and Information " +"Disclosure. Understanding the type of vulnerability and where it occurs in " +"your infrastructure will enable you to make reasoned response decisions." +msgstr "" + +#: ./doc/security-guide/ch012_configuration-management.xml69(para) +msgid "" +"Privilege Escalation describes the ability of a user to act with the " +"privileges of some other user in a system, bypassing appropriate " +"authorization checks. For example, a standard Linux user running code or " +"performing an operation that allows them to conduct further operations with " +"the privileges of the root users on the system." +msgstr "" + +#: ./doc/security-guide/ch012_configuration-management.xml75(para) +msgid "" +"Denial of Service refers to an exploited vulnerability that may cause " +"service or system disruption. This includes both distributed attacks to " +"overwhelm network resources, and single-user attacks that are typically " +"caused through resource allocation bugs or input induced system failure " +"flaws." +msgstr "" + +#: ./doc/security-guide/ch012_configuration-management.xml80(para) +msgid "" +"Information Disclosure vulnerabilities reveal information about your system " +"or operations. These vulnerabilities range from debugging information " +"disclosure, to exposure of critical security data, such as authentication " +"credentials and passwords." +msgstr "" + +#: ./doc/security-guide/ch012_configuration-management.xml96(emphasis) +msgid "Attacker Position / Privilege Level" +msgstr "" + +#: ./doc/security-guide/ch012_configuration-management.xml102(emphasis) +msgid "External" +msgstr "" + +#: ./doc/security-guide/ch012_configuration-management.xml103(emphasis) +msgid "Cloud User" +msgstr "" + +#: ./doc/security-guide/ch012_configuration-management.xml105(emphasis) +msgid "Cloud Admin" +msgstr "" + +#: ./doc/security-guide/ch012_configuration-management.xml107(emphasis) +msgid "Control Plane" +msgstr "" + +#: ./doc/security-guide/ch012_configuration-management.xml111(emphasis) +msgid "Privilege Elevation (3 levels)" +msgstr "" + +#: ./doc/security-guide/ch012_configuration-management.xml113(para) +#: ./doc/security-guide/ch012_configuration-management.xml121(para) +#: ./doc/security-guide/ch012_configuration-management.xml122(para) +#: ./doc/security-guide/ch012_configuration-management.xml129(para) +#: ./doc/security-guide/ch012_configuration-management.xml130(para) +#: ./doc/security-guide/ch012_configuration-management.xml131(para) +msgid "Critical" +msgstr "" + +#: ./doc/security-guide/ch012_configuration-management.xml114(para) +#: ./doc/security-guide/ch012_configuration-management.xml115(para) +#: ./doc/security-guide/ch012_configuration-management.xml116(para) +#: ./doc/security-guide/ch012_configuration-management.xml123(para) +#: ./doc/security-guide/ch012_configuration-management.xml124(para) +#: ./doc/security-guide/ch012_configuration-management.xml132(para) +msgid "n/a" +msgstr "" + +#: ./doc/security-guide/ch012_configuration-management.xml119(emphasis) +msgid "Privilege Elevation (2 levels)" +msgstr "" + +#: ./doc/security-guide/ch012_configuration-management.xml127(emphasis) +msgid "Privilege Elevation (1 level)" +msgstr "" + +#: ./doc/security-guide/ch012_configuration-management.xml135(emphasis) +msgid "Denial of Service" +msgstr "" + +#: ./doc/security-guide/ch012_configuration-management.xml137(para) +msgid "High" +msgstr "" + +#: ./doc/security-guide/ch012_configuration-management.xml138(para) +msgid "Medium" +msgstr "" + +#: ./doc/security-guide/ch012_configuration-management.xml139(para) +#: ./doc/security-guide/ch012_configuration-management.xml140(para) +#: ./doc/security-guide/ch012_configuration-management.xml148(para) +msgid "Low" +msgstr "" + +#: ./doc/security-guide/ch012_configuration-management.xml143(emphasis) +msgid "Information Disclosure" +msgstr "" + +#: ./doc/security-guide/ch012_configuration-management.xml145(para) +#: ./doc/security-guide/ch012_configuration-management.xml146(para) +msgid "Critical / High" +msgstr "" + +#: ./doc/security-guide/ch012_configuration-management.xml147(para) +msgid "Medium / Low" +msgstr "" + +#: ./doc/security-guide/ch012_configuration-management.xml152(para) +msgid "" +"This table illustrates a generic approach to measuring the impact of a " +"vulnerability based on where it occurs in your deployment and the effect. " +"For example, a single level privilege escalation on a Compute API node " +"potentially allows a standard user of the API to escalate to have the same " +"privileges as the root user on the node." +msgstr "" + +#: ./doc/security-guide/ch012_configuration-management.xml158(para) +msgid "" +"We suggest that cloud administrators use this table as a model to help " +"define which actions to take for the various security levels. For example, a" +" critical-level security update might require the cloud to be upgraded on a " +"specified time line, whereas a low-level update might be more relaxed." +msgstr "" + +#: ./doc/security-guide/ch012_configuration-management.xml165(title) +msgid "Testing the Updates" +msgstr "" + +#: ./doc/security-guide/ch012_configuration-management.xml166(para) +msgid "" +"You should test any update before you deploy it in a production environment." +" Typically this requires having a separate test cloud setup that first " +"receives the update. This cloud should be as close to the production cloud " +"as possible, in terms of software and hardware. Updates should be tested " +"thoroughly in terms of performance impact, stability, application impact, " +"and more. Especially important is to verify that the problem theoretically " +"addressed by the update, such as a specific vulnerability, is actually " +"fixed." +msgstr "" + +#: ./doc/security-guide/ch012_configuration-management.xml177(title) +msgid "Deploying the Updates" +msgstr "" + +#: ./doc/security-guide/ch012_configuration-management.xml178(para) +msgid "" +"Once the updates are fully tested, they can be deployed to the production " +"environment. This deployment should be fully automated using the " +"configuration management tools described below." +msgstr "" + +#: ./doc/security-guide/ch012_configuration-management.xml185(title) +msgid "Configuration Management" +msgstr "" + +#: ./doc/security-guide/ch012_configuration-management.xml186(para) +msgid "" +"A production quality cloud should always use tools to automate configuration" +" and deployment. This eliminates human error, and allows the cloud to scale " +"much more rapidly. Automation also helps with continuous integration and " +"testing." +msgstr "" + +#: ./doc/security-guide/ch012_configuration-management.xml191(para) +msgid "" +"When building an OpenStack cloud it is strongly recommended to approach your" +" design and implementation with a configuration management tool or framework" +" in mind. Configuration management allows you to avoid the many pitfalls " +"inherent in building, managing, and maintaining an infrastructure as complex" +" as OpenStack. By producing the manifests, cookbooks, or templates required " +"for a configuration management utility, you are able to satisfy a number of " +"documentation and regulatory reporting requirements. Further, configuration " +"management can also function as part of your BCP and DR plans wherein you " +"can rebuild a node or service back to a known state in a DR event or given a" +" compromise." +msgstr "" + +#: ./doc/security-guide/ch012_configuration-management.xml203(para) +msgid "" +"Additionally, when combined with a version control system such as Git or " +"SVN, you can track changes to your environment over time and re-mediate " +"unauthorized changes that may occur. For example, a " +"nova.conf file or other configuration file falls out of" +" compliance with your standard, your configuration management tool can " +"revert or replace the file and bring your configuration back into a known " +"state. Finally a configuration management tool can also be used to deploy " +"updates; simplifying the security patch process. These tools have a broad " +"range of capabilities that are useful in this space. The key point for " +"securing your cloud is to choose a tool for configuration management and use" +" it." +msgstr "" + +#: ./doc/security-guide/ch012_configuration-management.xml215(para) +msgid "" +"There are many configuration management solutions; at the time of this " +"writing there are two in the marketplace that are robust in their support of" +" OpenStack environments: Chef and " +"Puppet. A non-exhaustive listing of tools in this " +"space is provided below:" +msgstr "" + +#: ./doc/security-guide/ch012_configuration-management.xml223(para) +msgid "Chef" +msgstr "" + +#: ./doc/security-guide/ch012_configuration-management.xml226(para) +msgid "Puppet" +msgstr "" + +#: ./doc/security-guide/ch012_configuration-management.xml229(para) +msgid "Salt Stack" +msgstr "" + +#: ./doc/security-guide/ch012_configuration-management.xml232(para) +msgid "Ansible" +msgstr "" + +#: ./doc/security-guide/ch012_configuration-management.xml236(title) +msgid "Policy Changes" +msgstr "" + +#: ./doc/security-guide/ch012_configuration-management.xml237(para) +msgid "" +"Whenever a policy or configuration management is changed, it is good " +"practice to log the activity, and backup a copy of the new set. Often, such " +"policies and configurations are stored in a version controlled repository " +"such as git." +msgstr "" + +#: ./doc/security-guide/ch012_configuration-management.xml244(title) +msgid "Secure Backup and Recovery" +msgstr "" + +#: ./doc/security-guide/ch012_configuration-management.xml245(para) +msgid "" +"It is important to include Backup procedures and policies in the overall " +"System Security Plan. For a good overview of OpenStack's Backup and Recovery" +" capabilities and procedures, please refer to the OpenStack Operations " +"Guide." +msgstr "" + +#: ./doc/security-guide/ch012_configuration-management.xml250(title) +#: ./doc/security-guide/ch014_best-practices-for-operator-mode-access.xml45(title) +#: ./doc/security-guide/ch014_best-practices-for-operator-mode-access.xml82(title) +#: ./doc/security-guide/ch014_best-practices-for-operator-mode-access.xml113(title) +#: ./doc/security-guide/ch014_best-practices-for-operator-mode-access.xml132(title) +#: ./doc/security-guide/ch026_compute.xml23(title) +#: ./doc/security-guide/ch026_compute.xml57(title) +msgid "Security Considerations" +msgstr "" + +#: ./doc/security-guide/ch012_configuration-management.xml253(para) +msgid "" +"Ensure only authenticated users and backup clients have access to the backup" +" server." +msgstr "" + +#: ./doc/security-guide/ch012_configuration-management.xml257(para) +msgid "Use data encryption options for storage and transmission of backups." +msgstr "" + +#: ./doc/security-guide/ch012_configuration-management.xml261(para) +msgid "" +"Use a dedicated and hardened backup servers. The logs for the backup server " +"must be monitored daily and accessible by only few individuals." +msgstr "" + +#: ./doc/security-guide/ch012_configuration-management.xml266(para) +msgid "" +"Test data recovery options regularly. One of the things that can be restored" +" from secured backups is the images. In case of a compromise, the best " +"practice would be to terminate running instances immediately and then " +"relaunch the instances from the images in the secured backup repository." +msgstr "" + +#: ./doc/security-guide/ch012_configuration-management.xml276(title) +#: ./doc/security-guide/ch014_best-practices-for-operator-mode-access.xml64(title) +#: ./doc/security-guide/ch014_best-practices-for-operator-mode-access.xml123(title) +#: ./doc/security-guide/ch014_best-practices-for-operator-mode-access.xml157(title) +#: ./doc/security-guide/ch026_compute.xml33(title) +#: ./doc/security-guide/ch026_compute.xml70(title) +#: ./doc/security-guide/ch058_forensicsincident-response.xml43(title) +msgid "References" +msgstr "" + +#: ./doc/security-guide/ch012_configuration-management.xml279(para) +msgid "" +"OpenStack Operations Guide on backup and recovery" +msgstr "" + +#: ./doc/security-guide/ch012_configuration-management.xml287(link) +msgid "" +"http://www.sans.org/reading_room/whitepapers/backup/security-considerations-" +"enterprise-level-backups_515" +msgstr "" + +#: ./doc/security-guide/ch012_configuration-management.xml291(link) +msgid "OpenStack Security Primer" +msgstr "" + +#: ./doc/security-guide/ch012_configuration-management.xml297(title) +msgid "Security Auditing Tools" +msgstr "" + +#: ./doc/security-guide/ch012_configuration-management.xml298(para) +msgid "" +"Security auditing tools can complement the configuration management tools.  " +"Security auditing tools automate the process of verifying that a large " +"number of security controls are satisfied for a given system configuration. " +"These tools help to bridge the gap from security configuration guidance " +"documentation (for example, the STIG and NSA Guides) to a specific system " +"installation. For example, SCAP can compare a running system to a pre-defined " +"profile. SCAP outputs a report detailing which controls in the profile were " +"satisfied, which ones failed, and which ones were not checked." +msgstr "" + +#: ./doc/security-guide/ch012_configuration-management.xml310(para) +msgid "" +"Combining configuration management and security auditing tools creates a " +"powerful combination. The auditing tools will highlight deployment concerns." +" And the configuration management tools simplify the process of changing " +"each system to address the audit concerns. Used together in this fashion, " +"these tools help to maintain a cloud that satisfies security requirements " +"ranging from basic hardening to compliance validation." +msgstr "" + +#: ./doc/security-guide/ch012_configuration-management.xml317(para) +msgid "" +"Configuration management and security auditing tools will introduce another " +"layer of complexity into the cloud.  This complexity brings additional " +"security concerns with it. We view this as an acceptable risk trade-off, " +"given their security benefits. Securing the operational use of these tools " +"is beyond the scope of this guide." +msgstr "" + +#: ./doc/security-guide/ch059_case-studies-monitoring-logging.xml3(title) +msgid "Case Studies: Monitoring and Logging" +msgstr "" + +#: ./doc/security-guide/ch059_case-studies-monitoring-logging.xml4(para) +msgid "" +"In this case study we discuss how Alice and Bob would address monitoring and" +" logging in the public vs a private cloud. In both instances, time " +"synchronization and a centralized store of logs become extremely important " +"for performing proper assessments and troubleshooting of anomalies. Just " +"collecting logs is not very useful, a robust monitoring system must be built" +" to generate actionable events." +msgstr "" + +#: ./doc/security-guide/ch059_case-studies-monitoring-logging.xml6(title) +#: ./doc/security-guide/ch039_case-studies-messaging.xml6(title) +#: ./doc/security-guide/ch066_case-studies-compliance.xml6(title) +#: ./doc/security-guide/ch028_case-studies-identity-management.xml6(title) +#: ./doc/security-guide/ch044_case-studies-database.xml6(title) +#: ./doc/security-guide/ch009_case-studies.xml6(title) +#: ./doc/security-guide/ch056_case-studies-instance-management.xml6(title) +#: ./doc/security-guide/ch022_case-studies-api-endpoints.xml6(title) +#: ./doc/security-guide/ch015_case-studies-management.xml29(title) +#: ./doc/security-guide/ch018_case-studies-pkissl.xml6(title) +#: ./doc/security-guide/ch035_case-studies-networking.xml6(title) +#: ./doc/security-guide/ch049_case-studies-tenant-data.xml6(title) +#: ./doc/security-guide/ch053_case-studies-instance-isolation.xml6(title) +msgid "Alice's Private Cloud" +msgstr "" + +#: ./doc/security-guide/ch059_case-studies-monitoring-logging.xml7(para) +msgid "" +"In the private cloud, Alice has a better understanding of the tenants " +"requirements and accordingly can add appropriate oversight and compliance on" +" monitoring and logging. Alice should identify critical services and data " +"and ensure that logging is turned at least on those services and is being " +"aggregated to a central log server. She should start with simple and known " +"use cases and implement correlation and alerting to limit the number of " +"false positives. To implement correlation and alerting, she sends the log " +"data to her organization's existing SIEM tool. Security monitoring should be" +" an ongoing process and she should continue to define use cases and alerts " +"as she has better understanding of the network traffic activity and usage " +"over time." +msgstr "" + +#: ./doc/security-guide/ch059_case-studies-monitoring-logging.xml10(title) +#: ./doc/security-guide/ch039_case-studies-messaging.xml10(title) +#: ./doc/security-guide/ch066_case-studies-compliance.xml13(title) +#: ./doc/security-guide/ch028_case-studies-identity-management.xml12(title) +#: ./doc/security-guide/ch044_case-studies-database.xml10(title) +#: ./doc/security-guide/ch009_case-studies.xml11(title) +#: ./doc/security-guide/ch056_case-studies-instance-management.xml12(title) +#: ./doc/security-guide/ch022_case-studies-api-endpoints.xml10(title) +#: ./doc/security-guide/ch015_case-studies-management.xml34(title) +#: ./doc/security-guide/ch018_case-studies-pkissl.xml10(title) +#: ./doc/security-guide/ch035_case-studies-networking.xml24(title) +#: ./doc/security-guide/ch049_case-studies-tenant-data.xml23(title) +#: ./doc/security-guide/ch053_case-studies-instance-isolation.xml12(title) +msgid "Bob's Public Cloud" +msgstr "" + +#: ./doc/security-guide/ch059_case-studies-monitoring-logging.xml11(para) +msgid "" +"When it comes to logging, as a public cloud provider, Bob is interested in " +"logging both for situational awareness as well as compliance. That is, " +"compliance that Bob as a provider is subject to as well as his ability to " +"provide timely and relevant logs or reports on the behalf of his customers " +"for their compliance audits. With that in mind, Bob configures all of his " +"instances, nodes, and infrastructure devices to perform time synchronization" +" with an external, known good time device. Additionally, Bob's team has " +"built a Django based web applications for his customers to perform self-" +"service log retrieval from Bob's SIEM tool. Bob also uses this SIEM tool " +"along with a robust set of alerts and integration with his CMDB to provide " +"operational awareness to both customers and cloud administrators." +msgstr "" + +#: ./doc/security-guide/bk_openstack-sec-guide.xml6(title) +msgid "OpenStack Security Guide" +msgstr "" + +#: ./doc/security-guide/bk_openstack-sec-guide.xml14(orgname) +#: ./doc/security-guide/bk_openstack-sec-guide.xml19(holder) +msgid "OpenStack Foundation" +msgstr "" + +#: ./doc/security-guide/bk_openstack-sec-guide.xml18(year) +msgid "2013" +msgstr "" + +#: ./doc/security-guide/bk_openstack-sec-guide.xml21(releaseinfo) +msgid "havana" +msgstr "" + +#: ./doc/security-guide/bk_openstack-sec-guide.xml22(productname) +msgid "OpenStack" +msgstr "" + +#: ./doc/security-guide/bk_openstack-sec-guide.xml26(remark) +msgid "Copyright details are filled in by the template." +msgstr "" + +#: ./doc/security-guide/bk_openstack-sec-guide.xml31(para) +msgid "" +"This book provides best practices and conceptual information about securing " +"an OpenStack cloud." +msgstr "" + +#: ./doc/security-guide/bk_openstack-sec-guide.xml38(date) +msgid "2013-12-02" +msgstr "" + +#: ./doc/security-guide/bk_openstack-sec-guide.xml42(para) +msgid "Chapter on Object Storage added." +msgstr "" + +#: ./doc/security-guide/bk_openstack-sec-guide.xml48(date) +msgid "2013-10-17" +msgstr "" + +#: ./doc/security-guide/bk_openstack-sec-guide.xml52(para) +msgid "Havana release." +msgstr "" + +#: ./doc/security-guide/bk_openstack-sec-guide.xml58(date) +msgid "2013-07-02" +msgstr "" + +#: ./doc/security-guide/bk_openstack-sec-guide.xml62(para) +msgid "Initial creation..." +msgstr "" + +#: ./doc/security-guide/ch065_privacy.xml3(title) +msgid "Privacy" +msgstr "" + +#: ./doc/security-guide/ch065_privacy.xml4(para) +msgid "" +"Privacy is an increasingly important element of a compliance program. " +"Businesses are being held to a higher standard by their customers, who have " +"increased interest in understanding how their data is treated from a privacy" +" perspective." +msgstr "" + +#: ./doc/security-guide/ch065_privacy.xml5(para) +msgid "" +"An OpenStack deployment will likely need to demonstrate compliance with an " +"organization’s Privacy Policy, with the U.S. – E.U. Safe Harbor framework, " +"the ISO/IEC 29100:2011 privacy framework or with other privacy-specific " +"guidelines. In the U.S. the AICPA has defined" +" 10 privacy areas of focus, OpenStack deployments within a commercial" +" environment may desire to attest to some or all of these principles." +msgstr "" + +#: ./doc/security-guide/ch065_privacy.xml6(para) +msgid "" +"To aid OpenStack architects in the protection of personal data, it is " +"recommended that OpenStack architects review the NIST publication 800-122, " +"titled \"Guide to Protecting the Confidentiality of Personally " +"Identifiable Information (PII).\" This guide steps through the " +"process of protecting:" +msgstr "" + +#: ./doc/security-guide/ch065_privacy.xml8(para) +msgid "" +"\"any information about an individual maintained by an agency, " +"including (1) any information that can be used to distinguish or trace an " +"individual‘s identity, such as name, social security number, date and place " +"of birth, mother‘s maiden name, or biometric records; and (2) any other " +"information that is linked or linkable to an individual, such as medical, " +"educational, financial, and employment information\"" +msgstr "" + +#: ./doc/security-guide/ch065_privacy.xml10(para) +msgid "" +"Comprehensive privacy management requires significant preparation, thought " +"and investment. Additional complications are introduced when building global" +" OpenStack clouds, for example navigating the differences between U.S. and " +"more restrictive E.U. privacy laws. In addition, extra care needs to be " +"taken when dealing with sensitive PII that may include information such as " +"credit card numbers or medical records. This sensitive data is not only " +"subject to privacy laws but also regulatory and governmental regulations. By" +" deferring to established best practices, including those published by " +"governments, a holistic privacy management policy may be created and " +"practiced for OpenStack deployments." +msgstr "" + +#: ./doc/security-guide/ch032_networking-best-practices.xml3(title) +msgid "Networking Services" +msgstr "" + +#: ./doc/security-guide/ch032_networking-best-practices.xml4(para) +msgid "" +"In the initial architectural phases of designing your OpenStack Network " +"infrastructure it is important to ensure appropriate expertise is available " +"to assist with the design of the physical networking infrastructure, to " +"identify proper security controls and auditing mechanisms." +msgstr "" + +#: ./doc/security-guide/ch032_networking-best-practices.xml5(para) +msgid "" +"OpenStack Networking adds a layer of virtualized network services - giving " +"tenants the capability to architect their own, virtual networks. These " +"virtualized services are not as currently as mature as their traditional " +"networking counterparts. It is important to be aware of the current state of" +" these virtualized services and what controls may need to be implemented at " +"the virtualized and traditional network boundary." +msgstr "" + +#: ./doc/security-guide/ch032_networking-best-practices.xml7(title) +msgid "L2 Isolation using VLANs and Tunneling" +msgstr "" + +#: ./doc/security-guide/ch032_networking-best-practices.xml8(para) +msgid "" +"OpenStack networking can employ two different mechanisms for traffic " +"segregation on a per tenant/network combination: VLANs (IEEE 802.1Q tagging)" +" or L2 tunnels using GRE encapsulation. Which method you choose for traffic " +"segregation and isolation is determined by the scope and scale of your " +"OpenStack deployment." +msgstr "" + +#: ./doc/security-guide/ch032_networking-best-practices.xml10(title) +msgid "VLANs" +msgstr "" + +#: ./doc/security-guide/ch032_networking-best-practices.xml11(para) +msgid "" +"VLANs are realized as packets on a specific physical network containing IEEE" +" 802.1Q headers with a specific VLAN ID (VID) field value. VLAN networks " +"sharing the same physical network are isolated from each other at L2, and " +"can even have overlapping IP address spaces. Each distinct physical network " +"supporting VLAN networks is treated as a separate VLAN trunk, with a " +"distinct space of VID values. Valid VID values are 1 through 4094." +msgstr "" + +#: ./doc/security-guide/ch032_networking-best-practices.xml12(para) +msgid "" +"VLAN configuration complexity depends on your OpenStack design requirements." +" In order to allow OpenStack Networking to efficiently use VLANs, you must " +"allocate a VLAN range (one for each tenant) and turn each compute node " +"physical switch port into a VLAN trunk port." +msgstr "" + +#: ./doc/security-guide/ch032_networking-best-practices.xml14(para) +msgid "" +"NOTE: If you intend for your network to support more than 4094 tenants VLAN " +"is probably not the correct option for you as multiple 'hacks' are required " +"to extend the VLAN tags to more than 4094 tenants." +msgstr "" + +#: ./doc/security-guide/ch032_networking-best-practices.xml18(title) +msgid "L2 Tunneling" +msgstr "" + +#: ./doc/security-guide/ch032_networking-best-practices.xml19(para) +msgid "" +"Network tunneling encapsulates each tenant/network combination with a unique" +" \"tunnel-id\" that is used to identify the network traffic belonging to " +"that combination. The tenant's L2 network connectivity is independent of " +"physical locality or underlying network design. By encapsulating traffic " +"inside IP packets, that traffic can cross Layer-3 boundaries, removing the " +"need for preconfigured VLANs and VLAN trunking. Tunneling adds a layer of " +"obfuscation to network data traffic, reducing the visibility of individual " +"tenant traffic from a monitoring point of view." +msgstr "" + +#: ./doc/security-guide/ch032_networking-best-practices.xml20(para) +msgid "" +"OpenStack Networking currently only supports GRE encapsulation with planned " +"future support of VXLAN due in the Havana release." +msgstr "" + +#: ./doc/security-guide/ch032_networking-best-practices.xml21(para) +msgid "" +"The choice of technology to provide L2 isolation is dependent upon the scope" +" and size of tenant networks that will be created in your deployment. If " +"your environment has limited VLAN ID availability or will have a large " +"number of L2 networks, it is our recommendation that you utilize tunneling." +msgstr "" + +#: ./doc/security-guide/ch032_networking-best-practices.xml25(title) +msgid "Network Services" +msgstr "" + +#: ./doc/security-guide/ch032_networking-best-practices.xml26(para) +msgid "" +"The choice of tenant network isolation affects how the network security and " +"control boundary is implemented for tenant services. The following " +"additional network services are either available or currently under " +"development to enhance the security posture of the OpenStack network " +"architecture." +msgstr "" + +#: ./doc/security-guide/ch032_networking-best-practices.xml28(title) +msgid "Access Control Lists" +msgstr "" + +#: ./doc/security-guide/ch032_networking-best-practices.xml29(para) +msgid "" +"OpenStack Compute supports tenant network traffic access controls directly " +"when deployed with the legacy nova-network service, or may defer access " +"control to the OpenStack Networking service." +msgstr "" + +#: ./doc/security-guide/ch032_networking-best-practices.xml30(para) +msgid "" +"Note, legacy nova-network security groups are applied to all virtual " +"interface ports on an instance using IPTables." +msgstr "" + +#: ./doc/security-guide/ch032_networking-best-practices.xml31(para) +msgid "" +"Security groups allow administrators and tenants the ability to specify the " +"type of traffic, and direction (ingress/egress) that is allowed to pass " +"through a virtual interface port. Security groups rules are stateful L2-L4 " +"traffic filters." +msgstr "" + +#: ./doc/security-guide/ch032_networking-best-practices.xml32(para) +msgid "" +"It is our recommendation that you enable security groups via OpenStack " +"Networking." +msgstr "" + +#: ./doc/security-guide/ch032_networking-best-practices.xml35(title) +msgid "L3 Routing and NAT" +msgstr "" + +#: ./doc/security-guide/ch032_networking-best-practices.xml36(para) +msgid "" +"OpenStack Networking routers can connect multiple L2 networks, and can also " +"provide a gateway that connects one or more private L2 " +"networks to a shared external network, such as a public" +" network for access to the Internet." +msgstr "" + +#: ./doc/security-guide/ch032_networking-best-practices.xml37(para) +msgid "" +"The L3 router provides basic Network Address Translation (NAT) capabilities " +"on gateway ports that uplink the router to external " +"networks. This router SNATs (Static NAT) all traffic by default, and " +"supports floating IPs, which creates a static one-to-one mapping from a " +"public IP on the external network to a private IP on one of the other " +"subnets attached to the router." +msgstr "" + +#: ./doc/security-guide/ch032_networking-best-practices.xml38(para) +msgid "" +"It is our recommendation to leverage per tenant L3 routing and Floating IPs " +"for more granular connectivity of tenant VMs." +msgstr "" + +#: ./doc/security-guide/ch032_networking-best-practices.xml41(title) +msgid "Quality of Service (QoS)" +msgstr "" + +#: ./doc/security-guide/ch032_networking-best-practices.xml42(para) +msgid "" +"The ability to set QoS on the virtual interface ports of tenant instances is" +" a current deficiency for OpenStack Networking. The application of QoS for " +"traffic shaping and rate-limiting at the physical network edge device is " +"insufficient due to the dynamic nature of workloads in an OpenStack " +"deployment and can not be leveraged in the traditional way.  QoS-" +"as-a-Service (QoSaaS) is currently in development for the OpenStack " +"Networking Havana release as an experimental feature. QoSaaS is planning to " +"provide the following services:" +msgstr "" + +#: ./doc/security-guide/ch032_networking-best-practices.xml44(para) +msgid "Traffic shaping via DSCP markings" +msgstr "" + +#: ./doc/security-guide/ch032_networking-best-practices.xml47(para) +msgid "Rate-limiting on a per port/network/tenant basis." +msgstr "" + +#: ./doc/security-guide/ch032_networking-best-practices.xml50(para) +msgid "Port mirroring (via open source or third-party plugins)" +msgstr "" + +#: ./doc/security-guide/ch032_networking-best-practices.xml53(para) +msgid "Flow analysis (via open source or third-party plugins)" +msgstr "" + +#: ./doc/security-guide/ch032_networking-best-practices.xml56(para) +msgid "" +"Tenant traffic port mirroring or Network Flow monitoring is currently not an" +" exposed feature in OpenStack Networking. There are third-party plugin " +"extensions that do provide Port Mirroring on a per port/network/tenant " +"basis. If Open vSwitch is used on the networking hypervisor, it is possible " +"to enable sFlow and port mirroring, however it will require some operational" +" effort to implement." +msgstr "" + +#: ./doc/security-guide/ch032_networking-best-practices.xml59(title) +msgid "Load Balancing" +msgstr "" + +#: ./doc/security-guide/ch032_networking-best-practices.xml60(para) +msgid "" +"An experimental feature in the Grizzly release of OpenStack Networking is " +"Load-Balancer-as-a-service (LBaaS). The LBaaS API gives early adopters and " +"vendors a chance to build implementations of the technology. The reference " +"implementation however, is still experimental and should likely not be run " +"in a production environment. The current reference implementation is based " +"on HA-Proxy. There are third-party plugins in development for extensions in " +"OpenStack Networking to provide extensive L4-L7 functionality for virtual " +"interface ports." +msgstr "" + +#: ./doc/security-guide/ch032_networking-best-practices.xml63(title) +msgid "Firewalls" +msgstr "" + +#: ./doc/security-guide/ch032_networking-best-practices.xml64(para) +msgid "" +"FW-as-a-Service (FWaaS) is currently in development for the OpenStack " +"Networking Havana release as an experimental feature. FWaaS will address the" +" need to manage and leverage the rich set of security features provided by " +"typical firewall products which are typically far more comprehensive than " +"what is currently provided by security groups. There are third-party plugins" +" in development for extensions in OpenStack Networking to support this." +msgstr "" + +#: ./doc/security-guide/ch032_networking-best-practices.xml65(para) +msgid "" +"It is critical during the design of an OpenStack Networking infrastructure " +"to understand the current features and limitations of network services that " +"are available. Understanding where the boundaries of your virtual and " +"physical networks will help you add the required security controls in your " +"environment." +msgstr "" + +#: ./doc/security-guide/ch032_networking-best-practices.xml69(title) +msgid "Network Services Extensions" +msgstr "" + +#: ./doc/security-guide/ch032_networking-best-practices.xml70(para) +msgid "" +"Here is a list of known plugins provided by the open source community or by " +"SDN companies that work with OpenStack Networking:" +msgstr "" + +#: ./doc/security-guide/ch032_networking-best-practices.xml71(para) +msgid "" +"Big Switch Controller Plugin, Brocade Neutron Plugin Brocade Neutron Plugin," +" Cisco UCS/Nexus Plugin, Cloudbase Hyper-V Plugin, Extreme Networks Plugin, " +"Juniper Networks Neutron Plugin, Linux Bridge Plugin, Mellanox Neutron " +"Plugin, MidoNet Plugin, NEC OpenFlow Plugin, Nicira Network Virtualization " +"Platform (NVP) Plugin, Open vSwitch Plugin, PLUMgrid Plugin, Ruijie Networks" +" Plugin, Ryu OpenFlow Controller Plugin" +msgstr "" + +#: ./doc/security-guide/ch032_networking-best-practices.xml72(para) +msgid "" +"For a more detailed comparison of all features provided by plugins as of the" +" Folsom release, see Sebastien Han's " +"comparison." +msgstr "" + +#: ./doc/security-guide/ch032_networking-best-practices.xml75(title) +msgid "Networking Services Limitations" +msgstr "" + +#: ./doc/security-guide/ch032_networking-best-practices.xml76(para) +msgid "OpenStack Networking has the following known limitations:" +msgstr "" + +#: ./doc/security-guide/ch032_networking-best-practices.xml78(para) +msgid "" +"Overlapping IP addresses — If nodes that " +"run either neutron-l3-agent or neutron-dhcp-" +"agent use overlapping IP addresses, those nodes must use Linux " +"network namespaces. By default, the DHCP and L3 agents use Linux network " +"namespaces. However, if the host does not support these namespaces, run the " +"DHCP and L3 agents on different hosts." +msgstr "" + +#: ./doc/security-guide/ch032_networking-best-practices.xml79(para) +msgid "" +"If network namespace support is not present, a further limitation of the L3 " +"Agent is that only a single logical router is supported." +msgstr "" + +#: ./doc/security-guide/ch032_networking-best-practices.xml82(para) +msgid "" +"Multi-Host DHCP-agent — OpenStack " +"Networking supports multiple l3-agent and dhcp-agents with load balancing. " +"However, tight coupling of the location of the virtual machine is not " +"supported." +msgstr "" + +#: ./doc/security-guide/ch032_networking-best-practices.xml85(para) +msgid "" +"No IPv6 Support for L3 agents — The " +"neutron-l3-agent, used by many plugins to implement L3 forwarding, supports " +"only IPv4 forwarding." +msgstr "" + +#. When image changes, this message will be marked fuzzy or untranslated for +#. you. +#. It doesn't matter what you translate it to: it's not used at all. +#: ./doc/security-guide/ch055_security-services-for-instances.xml47(None) +#: ./doc/security-guide/ch055_security-services-for-instances.xml50(None) +msgid "" +"@@image: 'static/filteringWorkflow1.png'; " +"md5=c144af5cbdee1bd17a7bde0bea5b5fe7" +msgstr "" + +#: ./doc/security-guide/ch055_security-services-for-instances.xml3(title) +msgid "Security Services for Instances" +msgstr "" + +#: ./doc/security-guide/ch055_security-services-for-instances.xml4(para) +msgid "" +"One of the virtues of running instances in a virtualized environment is that" +" it opens up new opportunities for security controls that are not typically " +"available when deploying onto bare metal. There are several technologies " +"that can be applied to the virtualization stack that bring improved " +"information assurance for cloud tenants." +msgstr "" + +#: ./doc/security-guide/ch055_security-services-for-instances.xml5(para) +msgid "" +"Deployers or users of OpenStack with strong security requirements may want " +"to consider deploying these technologies. Not all are applicable in every " +"situation, indeed in some cases technologies may be ruled out for use in a " +"cloud because of prescriptive business requirements. Similarly some " +"technologies inspect instance data such as run state which may be " +"undesirable to the users of the system." +msgstr "" + +#: ./doc/security-guide/ch055_security-services-for-instances.xml6(para) +msgid "" +"In this chapter we explore these technologies and describe the situations " +"where they can be used to enhance security for instances or underlying " +"instances. We also seek to highlight where privacy concerns may exist. These" +" include data pass through, introspection, or providing a source of entropy." +" In this section we highlight the following additional security services:" +msgstr "" + +#: ./doc/security-guide/ch055_security-services-for-instances.xml8(para) +msgid "Entropy to Instances" +msgstr "" + +#: ./doc/security-guide/ch055_security-services-for-instances.xml11(para) +#: ./doc/security-guide/ch055_security-services-for-instances.xml28(title) +msgid "Scheduling Instances to Nodes" +msgstr "" + +#: ./doc/security-guide/ch055_security-services-for-instances.xml14(para) +#: ./doc/security-guide/ch055_security-services-for-instances.xml88(title) +msgid "Trusted Images" +msgstr "" + +#: ./doc/security-guide/ch055_security-services-for-instances.xml17(para) +#: ./doc/security-guide/ch055_security-services-for-instances.xml153(title) +msgid "Instance Migrations" +msgstr "" + +#: ./doc/security-guide/ch055_security-services-for-instances.xml21(title) +msgid "Entropy To Instances" +msgstr "" + +#: ./doc/security-guide/ch055_security-services-for-instances.xml22(para) +msgid "" +"We consider entropy to refer to the quality and source of random data that " +"is available to an instance. Cryptographic technologies typically rely " +"heavily on randomness, requiring a high quality pool of entropy to draw " +"from. It is typically hard for a virtual machine to get enough entropy to " +"support these operations. Entropy starvation can manifest in instances as " +"something seemingly unrelated for example, slow boot times because the " +"instance is waiting for ssh key generation. Entropy starvation may also " +"motivate users to employ poor quality entropy sources from within the " +"instance, making applications running in the cloud less secure overall." +msgstr "" + +#: ./doc/security-guide/ch055_security-services-for-instances.xml23(para) +msgid "" +"Fortunately, a cloud architect may address these issues by providing a high " +"quality source of entropy to the cloud instances. This can be done by having" +" enough hardware random number generators (HRNG) in the cloud to support the" +" instances. In this case, \"enough\" is somewhat domain specific. For " +"everyday operations, a modern HRNG is likely to produce enough entropy to " +"support 50-100 compute nodes. High bandwidth HRNGs, such as the RdRand " +"instruction available with Intel Ivy Bridge and newer processors could " +"potentially handle more nodes. For a given cloud, an architect needs to " +"understand the application requirements to ensure that sufficient entropy is" +" available." +msgstr "" + +#: ./doc/security-guide/ch055_security-services-for-instances.xml24(para) +msgid "" +"Once the entropy is available in the cloud, the next step is getting that " +"entropy into the instances. Tools such as the entropy gathering daemon " +"(EGD) provide a way to " +"fairly and securely distribute entropy through a distributed system. Support" +" exists for using the EGD as an entropy source for LibVirt." +msgstr "" + +#: ./doc/security-guide/ch055_security-services-for-instances.xml25(para) +msgid "" +"Compute support for these features is not generally available, but it would " +"only require a moderate amount of work for implementors to integrate this " +"functionality." +msgstr "" + +#: ./doc/security-guide/ch055_security-services-for-instances.xml29(para) +msgid "" +"Before an instance is created, a host for the image instantiation must be " +"selected. This selection is performed by the nova-scheduler which determines how to dispatch compute and " +"volume requests." +msgstr "" + +#: ./doc/security-guide/ch055_security-services-for-instances.xml30(para) +msgid "" +"The default nova scheduler in Grizzly is the Filter Scheduler, although " +"other schedulers exist (see the section Scheduling in the " +"OpenStack Configuration Reference). The filter " +"scheduler works in collaboration with 'filters' to decide where an instance " +"should be started. This process of host selection allows administrators to " +"fulfill many different security requirements. Depending on the cloud " +"deployment type for example, one could choose to have tenant instances " +"reside on the same hosts whenever possible if data isolation was a primary " +"concern, conversely one could attempt to have instances for a tenant reside " +"on as many different hosts as possible for availability or fault tolerance " +"reasons. The following diagram demonstrates how the filter scheduler works:" +msgstr "" + +#: ./doc/security-guide/ch055_security-services-for-instances.xml53(para) +msgid "" +"The use of scheduler filters may be used to segregate customers, data, or " +"even discard machines of the cloud that cannot be attested as secure. This " +"generally applies to all OpenStack projects offering a scheduler. When " +"building a cloud, you may choose to implement scheduling filters for a " +"variety of security-related purposes." +msgstr "" + +#: ./doc/security-guide/ch055_security-services-for-instances.xml54(para) +msgid "" +"Below we highlight a few of the filters that may be useful in a security " +"context, depending on your requirements, the full set of filter " +"documentation is documented in the Filter Scheduler section of the OpenStack" +" Configuration Reference." +msgstr "" + +#: ./doc/security-guide/ch055_security-services-for-instances.xml55(emphasis) +msgid "Tenant Driven Whole Host Reservation" +msgstr "" + +#: ./doc/security-guide/ch055_security-services-for-instances.xml56(para) +msgid "" +"There currently exists a blueprint for whole host reservation - This would allow " +"a tenant to exclusively reserve hosts for only it's instances, incurring " +"extra costs." +msgstr "" + +#: ./doc/security-guide/ch055_security-services-for-instances.xml58(title) +msgid "Host Aggregates" +msgstr "" + +#: ./doc/security-guide/ch055_security-services-for-instances.xml59(para) +msgid "" +"While not a filter in themselves, host aggregates allow administrators to " +"assign key-value pairs to groups of machines. This allows cloud " +"administrators, not users, to partition up their compute host resources. " +"Each node can have multiple aggregates (see the Host Aggregates section of the OpenStack" +" Configuration Reference for more information on creating and " +"managing aggregates)." +msgstr "" + +#: ./doc/security-guide/ch055_security-services-for-instances.xml70(title) +msgid "AggregateMultiTenancyIsolation" +msgstr "" + +#: ./doc/security-guide/ch055_security-services-for-instances.xml71(para) +msgid "" +"Isolates tenants to specific host aggregates. If a host is in an aggregate " +"that has the metadata key filter_tenant_id it will only " +"create instances from that tenant (or list of tenants). A host can be in " +"multiple aggregates. If a host does not belong to an aggregate with the " +"metadata key, it can create instances from all tenants." +msgstr "" + +#: ./doc/security-guide/ch055_security-services-for-instances.xml74(title) +msgid "DifferentHostFilter" +msgstr "" + +#: ./doc/security-guide/ch055_security-services-for-instances.xml75(para) +msgid "" +"Schedule the instance on a different host from a set of instances. To take " +"advantage of this filter, the requester must pass a scheduler hint, using " +"different_host as the key and a list of instance uuids as" +" the value. This filter is the opposite of the " +"SameHostFilter." +msgstr "" + +#: ./doc/security-guide/ch055_security-services-for-instances.xml78(title) +msgid "GroupAntiAffinityFilter" +msgstr "" + +#: ./doc/security-guide/ch055_security-services-for-instances.xml79(para) +msgid "" +"The GroupAntiAffinityFilter ensures that each instance in a group is on a " +"different host. To take advantage of this filter, the requester must pass a " +"scheduler hint, using group as the key and a list of " +"instance uuids as the value." +msgstr "" + +#: ./doc/security-guide/ch055_security-services-for-instances.xml82(title) +msgid "Trusted Compute Pools" +msgstr "" + +#: ./doc/security-guide/ch055_security-services-for-instances.xml83(para) +msgid "" +"There exists a scheduler filter which integrates with the Open Attestation" +" Project (OATS) to define scheduler behavior according to the " +"attestation of PCRs received from a system using Intel TXT." +msgstr "" + +#: ./doc/security-guide/ch055_security-services-for-instances.xml84(para) +msgid "" +"It is unclear if this feature is compatible with AMD's similar SEM, although" +" the OpenAttestation agent relies on the vendor-agnostic TrouSerS library." +msgstr "" + +#: ./doc/security-guide/ch055_security-services-for-instances.xml89(para) +msgid "" +"With regards to images, users will be working with pre-installed images or " +"images that they upload themselves. In both cases, users will want to ensure" +" that the image they are ultimately running has not been tampered with. This" +" requires some source of truth such as a checksum for the known good version" +" of an image as well as verification of the running image. This section " +"describes the current best practices around image handling, while also " +"calling out some of the existing gaps in this space." +msgstr "" + +#: ./doc/security-guide/ch055_security-services-for-instances.xml91(title) +msgid "Image Creation Process" +msgstr "" + +#: ./doc/security-guide/ch055_security-services-for-instances.xml92(para) +msgid "" +"The OpenStack Documentation provides guidance on how to create and upload an" +" image to Glance. Additionally it is assumed that you have a process by " +"which you install and harden operating systems. Thus, the following items " +"will provide additional guidance on how to ensure your images are built " +"securely prior to upload. There are a variety of options for obtaining " +"images. Each has specific steps that help validate the image's provenance." +msgstr "" + +#: ./doc/security-guide/ch055_security-services-for-instances.xml93(para) +msgid "The first option is to obtain boot media from a trusted source." +msgstr "" + +#: ./doc/security-guide/ch055_security-services-for-instances.xml103(para) +msgid "" +"The second option is to use the OpenStack Virtual Machine Image " +"Guide. In this case, you will want to follow your " +"organizations OS hardening guidelines or those provided by a trusted third-" +"party such as the RHEL6 STIG." +msgstr "" + +#: ./doc/security-guide/ch055_security-services-for-instances.xml104(para) +msgid "" +"The final option is to use an automated image builder. The following example" +" uses the Oz image builder. The OpenStack community has recently created a " +"newer tool worth investigating: disk-image-builder. We have not evaluated " +"this tool from a security perspective." +msgstr "" + +#: ./doc/security-guide/ch055_security-services-for-instances.xml105(para) +msgid "" +"Example of RHEL 6 CCE-26976-1 which will help implement NIST 800-53 Section " +"AC-19(d) in Oz." +msgstr "" + +#: ./doc/security-guide/ch055_security-services-for-instances.xml142(para) +msgid "" +"Note, it is the recommendation of this guide to shy away from the manual " +"image building process as it is complex and prone to error. Further, using " +"an automated system like Oz or disk-image-builder for image building, or a " +"configuration management utility like Chef or Puppet for post boot image " +"hardening gives you the ability to produce a consistent image as well as " +"track compliance of your base image to its respective hardening guidelines " +"over time." +msgstr "" + +#: ./doc/security-guide/ch055_security-services-for-instances.xml143(para) +msgid "" +"If subscribing to a public cloud service, you should check with the cloud " +"provider for an outline of the process used to produce their default images." +" If the provider allows you to upload your own images, you will want to " +"ensure that you are able to verify that your image was not modified before " +"you spin it up. To do this, refer to the following section on Image " +"Provenance." +msgstr "" + +#: ./doc/security-guide/ch055_security-services-for-instances.xml146(title) +msgid "Image Provenance and Validation" +msgstr "" + +#: ./doc/security-guide/ch055_security-services-for-instances.xml147(para) +msgid "" +"Unfortunately, it is not currently possible to force Compute to validate an " +"image hash immediately prior to starting an instance. To understand the " +"situation, we begin with a brief overview of how images are handled around " +"the time of image launch." +msgstr "" + +#: ./doc/security-guide/ch055_security-services-for-instances.xml148(para) +msgid "" +"Images come from the glance service to the nova service on a node. This " +"transfer should be protected by running over SSL. Once the image is on the " +"node, it is verified with a basic checksum and then it's disk is expanded " +"based on the size of the instance being launched. If, at a later time, the " +"same image is launched with the same instance size on this node, it will be " +"launched from the same expanded image. Since this expanded image is not re-" +"verified before launching, it could be tampered with and the user would not " +"have any way of knowing, beyond a manual inspection of the files in the " +"resulting image." +msgstr "" + +#: ./doc/security-guide/ch055_security-services-for-instances.xml149(para) +msgid "" +"We hope that future versions of Compute and/or the Image Service will offer " +"support for validating the image hash before each instance launch. An " +"alternative option that would be even more powerful would be allow users to " +"sign an image and then have the signature validated when the instance is " +"launched." +msgstr "" + +#: ./doc/security-guide/ch055_security-services-for-instances.xml154(para) +msgid "" +"OpenStack and the underlying virtualization layers provide for the Live " +"Migration of images between OpenStack nodes allowing you to seamlessly " +"perform rolling upgrades of your OpenStack Compute nodes without instance " +"downtime. However, Live Migrations also come with their fair share of risk. " +"To understand the risks involved, it is important to first understand how a " +"live migration works. The following are the high level steps preformed " +"during a live migration." +msgstr "" + +#: ./doc/security-guide/ch055_security-services-for-instances.xml156(para) +msgid "Start instance on destination host" +msgstr "" + +#: ./doc/security-guide/ch055_security-services-for-instances.xml157(para) +msgid "Transfer memory" +msgstr "" + +#: ./doc/security-guide/ch055_security-services-for-instances.xml158(para) +msgid "Stop the guest & sync disks" +msgstr "" + +#: ./doc/security-guide/ch055_security-services-for-instances.xml159(para) +msgid "Transfer state" +msgstr "" + +#: ./doc/security-guide/ch055_security-services-for-instances.xml160(para) +msgid "Start the guest" +msgstr "" + +#: ./doc/security-guide/ch055_security-services-for-instances.xml163(title) +msgid "Live Migration Risks" +msgstr "" + +#: ./doc/security-guide/ch055_security-services-for-instances.xml164(para) +msgid "" +"At various stages of the live migration process the contents of an instances" +" run time memory and disk are transmitted over the network in plain text. " +"Thus there are several risks that need to be addressed when using live " +"migration. The following in-exhaustive list details some of these risks:" +msgstr "" + +#: ./doc/security-guide/ch055_security-services-for-instances.xml166(para) +msgid "" +"Denial of Service (DoS) : If something fails during the" +" migration process, the instance could be lost." +msgstr "" + +#: ./doc/security-guide/ch055_security-services-for-instances.xml169(para) +msgid "" +"Data Exposure : Memory or disk transfers must be " +"handled securely." +msgstr "" + +#: ./doc/security-guide/ch055_security-services-for-instances.xml172(para) +msgid "" +"Data Manipulation : If memory or disk transfers are not" +" handled securely, then an attacker could manipulate user data during the " +"migration." +msgstr "" + +#: ./doc/security-guide/ch055_security-services-for-instances.xml175(para) +msgid "" +"Code Injection : If memory or disk transfers are not " +"handled securely, then an attacker could manipulate executables, either on " +"disk or in memory, during the migration." +msgstr "" + +#: ./doc/security-guide/ch055_security-services-for-instances.xml180(title) +msgid "Live Migration Mitigations" +msgstr "" + +#: ./doc/security-guide/ch055_security-services-for-instances.xml181(para) +msgid "" +"There are several methods to mitigate some of the risk associated with live " +"migrations, the following list details some of these:" +msgstr "" + +#: ./doc/security-guide/ch055_security-services-for-instances.xml183(para) +#: ./doc/security-guide/ch055_security-services-for-instances.xml193(title) +msgid "Disable Live Migration" +msgstr "" + +#: ./doc/security-guide/ch055_security-services-for-instances.xml186(para) +msgid "Isolated Migration Network" +msgstr "" + +#: ./doc/security-guide/ch055_security-services-for-instances.xml189(para) +#: ./doc/security-guide/ch055_security-services-for-instances.xml204(title) +msgid "Encrypted Live Migration" +msgstr "" + +#: ./doc/security-guide/ch055_security-services-for-instances.xml194(para) +msgid "" +"At this time, live migration is enabled in OpenStack by default. Live " +"migrations can be disabled by adding the following lines to the nova " +"policy.json file:" +msgstr "" + +#: ./doc/security-guide/ch055_security-services-for-instances.xml200(title) +msgid "Migration Network" +msgstr "" + +#: ./doc/security-guide/ch055_security-services-for-instances.xml201(para) +msgid "" +"As a general practice, live migration traffic should be restricted to the " +"management security domain. Indeed live migration traffic, due to its plain " +"text nature and the fact that you are transferring the contents of disk and " +"memory of a running instance, it is recommended you further separate live " +"migration traffic onto a dedicated network. Isolating the traffic to a " +"dedicated network can reduce the risk of exposure." +msgstr "" + +#: ./doc/security-guide/ch055_security-services-for-instances.xml205(para) +msgid "" +"If your use case involves keeping live migration enabled, then libvirtd can " +"provide tunneled, encrypted live migrations. That said, this feature is not " +"currently exposed in OpenStack Dashboard, nor the nova-client commands and " +"can only be accessed through manual configuration of libvritd. Encrypted " +"live migration modifies the live migration process by first copying the " +"instance data from the running hypervisor to libvirtd. From there an " +"encrypted tunnel is created between the libvirtd processes on both hosts. " +"Finally, the destination libvirtd process copies the instance back to the " +"underlying hypervisor." +msgstr "" + +#: ./doc/security-guide/ch061_compliance-overview.xml3(title) +msgid "Compliance Overview" +msgstr "" + +#: ./doc/security-guide/ch061_compliance-overview.xml4(para) +msgid "" +"An OpenStack deployment may require compliance activities for many purposes," +" such as regulatory and legal requirements, customer need, privacy " +"considerations, and security best practices. Compliance, when done " +"correctly, unifies and strengthens the other security topics discussed in " +"this guide. This chapter has several objectives:" +msgstr "" + +#: ./doc/security-guide/ch061_compliance-overview.xml6(para) +msgid "Review common security principles." +msgstr "" + +#: ./doc/security-guide/ch061_compliance-overview.xml9(para) +msgid "" +"Discuss common control frameworks and certification resources to achieve " +"industry certifications or regulator attestations." +msgstr "" + +#: ./doc/security-guide/ch061_compliance-overview.xml12(para) +msgid "Act as a reference for auditors when evaluating OpenStack deployments." +msgstr "" + +#: ./doc/security-guide/ch061_compliance-overview.xml15(para) +msgid "" +"Introduce privacy considerations specific to OpenStack and cloud " +"environments." +msgstr "" + +#: ./doc/security-guide/ch061_compliance-overview.xml19(title) +msgid "Security Principles" +msgstr "" + +#: ./doc/security-guide/ch061_compliance-overview.xml20(para) +msgid "" +"Industry standard security principles provide a baseline for compliance " +"certifications and attestations. If these principles are considered and " +"referenced throughout an OpenStack deployment, certification activities may " +"be simplified." +msgstr "" + +#: ./doc/security-guide/ch061_compliance-overview.xml22(para) +msgid "" +"Layered Defenses: Identify where risks exist in a cloud" +" architecture and apply controls to mitigate the risks. In areas of " +"significant concern, layered defences provide multiple complementary " +"controls to further mitigate risk. For example, to ensure adequate isolation" +" between cloud tenants, we recommend hardening QEMU, using a hypervisor with" +" SELinux support, enforcing mandatory access control policies, and reducing " +"the overall attack surface. The foundational principle is to harden an area " +"of concern with multiple layers of defense such that if any one layer is " +"compromised, other layers will exist to offer protection and minimize " +"exposure." +msgstr "" + +#: ./doc/security-guide/ch061_compliance-overview.xml25(para) +msgid "" +"Fail Securely: In the case of failure, systems should " +"be configured to fail into a closed secure state. For example, SSL " +"certificate verification should fail closed by severing the network " +"connection if the CNAME doesn't match the server's DNS name. Software often " +"fails open in this situation, allowing the connection to proceed without a " +"CNAME match, which is less secure and not recommended." +msgstr "" + +#: ./doc/security-guide/ch061_compliance-overview.xml28(para) +msgid "" +"Least Privilege: Only the minimum level of access for " +"users and system services is granted. This access is based upon role, " +"responsibility and job function. This security principal of least privilege " +"is written into several international government security policies, such as " +"NIST 800-53 Section AC-6 within the United States. " +msgstr "" + +#: ./doc/security-guide/ch061_compliance-overview.xml31(para) +msgid "" +"Compartmentalize: Systems should be segregated in a " +"such way that if one machine, or system-level service, is compromised the " +"security of the other systems will remain intact. Practically, the " +"enablement and proper usage of SELinux helps accomplish this goal." +msgstr "" + +#: ./doc/security-guide/ch061_compliance-overview.xml34(para) +msgid "" +"Promote Privacy: The amount of information that can be " +"gathered about a system and its users should be minimized." +msgstr "" + +#: ./doc/security-guide/ch061_compliance-overview.xml37(para) +msgid "" +"Logging Capability: Appropriate logging is implemented " +"to monitor for unauthorized use, incident response and forensics. It is " +"highly recommended that selected audit subsystems be Common Criteria " +"certified, which provides non-attestable event records in most countries." +msgstr "" + +#: ./doc/security-guide/ch064_certifications-compliance-statements.xml8(title) +msgid "Certification & Compliance Statements" +msgstr "" + +#: ./doc/security-guide/ch064_certifications-compliance-statements.xml9(para) +msgid "" +"Compliance and security are not exclusive, and must be addressed together. " +"OpenStack deployments are unlikely to satisfy compliance requirements " +"without security hardening. The listing below provides an OpenStack " +"architect foundational knowledge and guidance to achieve compliance against " +"commercial and government certifications and standards." +msgstr "" + +#: ./doc/security-guide/ch064_certifications-compliance-statements.xml17(title) +msgid "Commercial Standards" +msgstr "" + +#: ./doc/security-guide/ch064_certifications-compliance-statements.xml18(para) +msgid "" +"For commercial deployments of OpenStack, it is recommended that SOC 1/2 " +"combined with ISO 2700 1/2 be considered as a starting point for OpenStack " +"certification activities. The required security activities mandated by these" +" certifications facilitate a foundation of security best practices and " +"common control criteria that can assist in achieving more stringent " +"compliance activities, including government attestations and certifications." +msgstr "" + +#: ./doc/security-guide/ch064_certifications-compliance-statements.xml26(para) +msgid "" +"After completing these initial certifications, the remaining certifications " +"are more deployment specific. For example, clouds processing credit card " +"transactions will need PCI-DSS, clouds storing health care information " +"require HIPAA, and clouds within the federal government may require " +"FedRAMP/FISMA, and ITAR, certifications. " +msgstr "" + +#: ./doc/security-guide/ch064_certifications-compliance-statements.xml34(title) +msgid "SOC 1 (SSAE 16) / ISAE 3402" +msgstr "" + +#: ./doc/security-guide/ch064_certifications-compliance-statements.xml35(para) +msgid "" +"Service Organization Controls (SOC) criteria are defined by the American Institute of Certified Public " +"Accountants (AICPA). SOC controls assess relevant financial " +"statements and assertions of a service provider, such as compliance with the" +" Sarbanes-Oxley Act. SOC 1 is a replacement for Statement on Auditing " +"Standards No. 70 (SAS 70) Type II report. These controls commonly include " +"physical data centers in scope." +msgstr "" + +#: ./doc/security-guide/ch064_certifications-compliance-statements.xml44(para) +msgid "There are two types of SOC 1 reports:" +msgstr "" + +#: ./doc/security-guide/ch064_certifications-compliance-statements.xml47(para) +#: ./doc/security-guide/ch064_certifications-compliance-statements.xml84(para) +msgid "" +"Type 1 – report on the fairness of the presentation of management's " +"description of the service organization's system and the suitability of the " +"design of the controls to achieve the related control objectives included in" +" the description as of a specified date." +msgstr "" + +#: ./doc/security-guide/ch064_certifications-compliance-statements.xml54(para) +msgid "" +"Type 2 – report on the fairness of the presentation of management's " +"description of the service organization's system and the suitability of the " +"design and operating effectiveness of the controls to achieve the related " +"control objectives included in the description throughout a specified period" +msgstr "" + +#: ./doc/security-guide/ch064_certifications-compliance-statements.xml62(para) +msgid "" +"For more details see the AICPA" +" Report on Controls at a Service Organization Relevant to User Entities’ " +"Internal Control over Financial Reporting." +msgstr "" + +#: ./doc/security-guide/ch064_certifications-compliance-statements.xml70(title) +msgid "SOC 2" +msgstr "" + +#: ./doc/security-guide/ch064_certifications-compliance-statements.xml71(para) +msgid "" +"Service Organization Controls (SOC) 2 is a self attestation of controls that" +" affect the security, availability, and processing integrity of the systems " +"a service organization uses to process users' data and the confidentiality " +"and privacy of information processed by these system. Examples of users are " +"those responsible for governance of the service organization; customers of " +"the service organization; regulators; business partners; suppliers and " +"others who have an understanding of the service organization and its " +"controls." +msgstr "" + +#: ./doc/security-guide/ch064_certifications-compliance-statements.xml81(para) +msgid "There are two types of SOC 2 reports:" +msgstr "" + +#: ./doc/security-guide/ch064_certifications-compliance-statements.xml91(para) +msgid "" +"Type 2 – report on the fairness of the presentation of management's " +"description of the service organization's system and the suitability of the " +"design and operating effectiveness of the controls to achieve the related " +"control objectives included in the description throughout a specified " +"period." +msgstr "" + +#: ./doc/security-guide/ch064_certifications-compliance-statements.xml99(para) +msgid "" +"For more details see the AICPA" +" Report on Controls at a Service Organization Relevant to Security, " +"Availability, Processing Integrity, Confidentiality or Privacy." +msgstr "" + +#: ./doc/security-guide/ch064_certifications-compliance-statements.xml108(title) +msgid "SOC 3" +msgstr "" + +#: ./doc/security-guide/ch064_certifications-compliance-statements.xml109(para) +msgid "" +"Service Organization Controls (SOC) 3 is a trust services report for service" +" organizations. These reports are designed to meet the needs of users who " +"want assurance on the controls at a service organization related to " +"security, availability, processing integrity, confidentiality, or privacy " +"but do not have the need for or the knowledge necessary to make effective " +"use of a SOC 2 Report. These reports are prepared using the AICPA/Canadian " +"Institute of Chartered Accountants (CICA) Trust Services Principles, " +"Criteria, and Illustrations for Security, Availability, Processing " +"Integrity, Confidentiality, and Privacy. Because they are general use " +"reports, SOC 3 Reports can be freely distributed or posted on a website as a" +" seal." +msgstr "" + +#: ./doc/security-guide/ch064_certifications-compliance-statements.xml121(para) +msgid "" +"For more details see the AICPA" +" Trust Services Report for Service Organizations." +msgstr "" + +#: ./doc/security-guide/ch064_certifications-compliance-statements.xml128(title) +msgid "ISO 27001/2" +msgstr "" + +#: ./doc/security-guide/ch064_certifications-compliance-statements.xml129(para) +msgid "" +"The ISO/IEC 27001/2 standards replace BS7799-2, and are specifications for " +"an Information Security Management System (ISMS). An ISMS is a comprehensive" +" set of policies and processes that an organization creates and maintains to" +" manage risk to information assets.  These risks are based upon the " +"confidentiality, integrity, and availability (CIA) of user information. The " +"CIA security triad has been used as a foundation for much of the chapters in" +" this book." +msgstr "" + +#: ./doc/security-guide/ch064_certifications-compliance-statements.xml137(para) +msgid "" +"For more details see ISO " +"27001." +msgstr "" + +#: ./doc/security-guide/ch064_certifications-compliance-statements.xml143(title) +msgid "HIPAA / HITECH" +msgstr "" + +#: ./doc/security-guide/ch064_certifications-compliance-statements.xml144(para) +msgid "" +"The Health Insurance Portability and Accountability Act (HIPAA) is a United " +"States congressional act that governs the collection, storage, use and " +"destruction of patient health records. The act states that Protected Health " +"Information (PHI) must be rendered \"unusable, unreadable, or " +"indecipherable\" to unauthorized persons and that encryption for data 'at-" +"rest' and 'inflight' should be addressed." +msgstr "" + +#: ./doc/security-guide/ch064_certifications-compliance-statements.xml151(para) +msgid "" +"HIPAA is not a certification, rather a guide for protecting healthcare data." +"  Similar to the PCI-DSS, the most important issues with both PCI and HIPPA " +"is that a breach of credit card information, and health data, does not " +"occur. In the instance of a breach the cloud provider will be scrutinized " +"for compliance with PCI and HIPPA controls. If proven compliant, the " +"provider can be expected to immediately implement remedial controls, breach " +"notification responsibilities, and significant expenditure on additional " +"compliance activities.  If not compliant, the cloud provider can expect on-" +"site audit teams, fines, potential loss of merchant ID (PCI), and massive " +"reputation impact." +msgstr "" + +#: ./doc/security-guide/ch064_certifications-compliance-statements.xml163(para) +msgid "" +"Users or organizations that possess PHI must support HIPAA requirements and " +"are HIPAA covered entities. If an entity intends to use a service, or in " +"this case, an OpenStack cloud that might use, store or have access to that " +"PHI, then a Business Associate Agreement must be signed. The BAA is a " +"contract between the HIPAA covered entity and the OpenStack service provider" +" that requires the provider to handle that PHI in accordance with HIPAA " +"requirements. If the service provider does not handle the PHI, such as with " +"security controls and hardening, then they are subject to HIPAA fines and " +"penalties." +msgstr "" + +#: ./doc/security-guide/ch064_certifications-compliance-statements.xml174(para) +msgid "" +"OpenStack architects interpret and respond to HIPAA statements, with data " +"encryption remaining a core practice. Currently this would require any " +"protected health information contained within an OpenStack deployment to be " +"encrypted with industry standard encryption algorithms. Potential future " +"OpenStack projects such as object encryption will facilitate HIPAA " +"guidelines for compliance with the act." +msgstr "" + +#: ./doc/security-guide/ch064_certifications-compliance-statements.xml181(para) +msgid "" +"For more details see the Health Insurance " +"Portability And Accountability Act." +msgstr "" + +#: ./doc/security-guide/ch064_certifications-compliance-statements.xml187(title) +msgid "PCI-DSS" +msgstr "" + +#: ./doc/security-guide/ch064_certifications-compliance-statements.xml188(para) +msgid "" +"The Payment Card Industry Data Security Standard (PCI DSS) is defined by the" +" Payment Card Industry Standards Council, and created to increase controls " +"around card holder data to reduce credit card fraud. Annual compliance " +"validation is assessed by an external Qualified Security Assessor (QSA) who " +"creates a Report on Compliance (ROC), or by a Self-Assessment Questionnaire " +"(SAQ) dependent on volume of card-holder transactions.  " +msgstr "" + +#: ./doc/security-guide/ch064_certifications-compliance-statements.xml196(para) +msgid "" +"OpenStack deployments which stores, processes, or transmits payment card " +"details are in scope for the PCI-DSS. All OpenStack components that are not " +"properly segmented from systems or networks that handle payment data fall " +"under the guidelines of the PCI-DSS. Segmentation in the context of PCI-DSS " +"does not support multi-tenancy, but rather physical separation " +"(host/network). " +msgstr "" + +#: ./doc/security-guide/ch064_certifications-compliance-statements.xml203(para) +msgid "" +"For more details see PCI " +"security standards." +msgstr "" + +#: ./doc/security-guide/ch064_certifications-compliance-statements.xml209(title) +msgid "Government Standards" +msgstr "" + +#: ./doc/security-guide/ch064_certifications-compliance-statements.xml212(title) +msgid "FedRAMP" +msgstr "" + +#: ./doc/security-guide/ch064_certifications-compliance-statements.xml213(para) +msgid "" +"\"The Federal Risk and Authorization " +"Management Program (FedRAMP) is a government-wide program that " +"provides a standardized approach to security assessment, authorization, and " +"continuous monitoring for cloud products and services\". NIST 800-53 is the " +"basis for both FISMA and FedRAMP which mandates security controls " +"specifically selected to provide protection in cloud environments. FedRAMP " +"can be extremely intensive from specificity around security controls, and " +"the volume of documentation required to meet government standards." +msgstr "" + +#: ./doc/security-guide/ch064_certifications-compliance-statements.xml223(para) +msgid "" +"For more details see http://www.gsa.gov/portal/category/102371." +msgstr "" + +#: ./doc/security-guide/ch064_certifications-compliance-statements.xml229(title) +msgid "ITAR" +msgstr "" + +#: ./doc/security-guide/ch064_certifications-compliance-statements.xml230(para) +msgid "" +"The International Traffic in Arms Regulations (ITAR) is a set of United " +"States government regulations that control the export and import of defense-" +"related articles and services on the United States Munitions List (USML) and" +" related technical data. ITAR is often approached by cloud providers as an " +"\"operational alignment\" rather than a formal certification. This typically" +" involves implementing a segregated cloud environment following practices " +"based on the NIST 800-53 framework, as per FISMA requirements, complemented " +"with additional controls restricting access to \"U.S. Persons\" only and " +"background screening." +msgstr "" + +#: ./doc/security-guide/ch064_certifications-compliance-statements.xml241(para) +msgid "" +"For more details see http://pmddtc.state.gov/regulations_laws/itar_official.html." +msgstr "" + +#: ./doc/security-guide/ch064_certifications-compliance-statements.xml247(title) +msgid "FISMA" +msgstr "" + +#: ./doc/security-guide/ch064_certifications-compliance-statements.xml248(para) +msgid "" +"The Federal Information Security Management Act requires that government " +"agencies create a comprehensive plan to implement numerous government " +"security standards, and was enacted within the E-Government Act of 2002. " +"FISMA outlines a process, which utilizing multiple NIST publications, " +"prepares an information system to store and process government data." +msgstr "" + +#: ./doc/security-guide/ch064_certifications-compliance-statements.xml255(para) +msgid "This process is broken apart into three primary categories:" +msgstr "" + +#: ./doc/security-guide/ch064_certifications-compliance-statements.xml259(para) +msgid "" +"System CategorizationThe information " +"system will receive a security category as defined in Federal Information " +"Processing Standards Publication 199 (FIPS 199). These categories reflect " +"the potential impact of system compromise." +msgstr "" + +#: ./doc/security-guide/ch064_certifications-compliance-statements.xml267(para) +msgid "" +"Control SelectionBased upon system " +"security category as defined in FIPS 199, an organization utilizes FIPS 200 " +"to identify specific security control requirements for the information " +"system. For example, if a system is categorized as “moderate” a requirement " +"may be introduced to mandate “secure passwords.”" +msgstr "" + +#: ./doc/security-guide/ch064_certifications-compliance-statements.xml276(para) +msgid "" +"Control TailoringOnce system security " +"controls are identified, an OpenStack architect will utilize NIST 800-53 to " +"extract tailored control selection. For example, specification of what " +"constitutes a “secure password.”" +msgstr "" + +#: ./doc/security-guide/ch039_case-studies-messaging.xml3(title) +msgid "Case Studies: Messaging" +msgstr "" + +#: ./doc/security-guide/ch039_case-studies-messaging.xml4(para) +msgid "" +"The message queue is a critical piece of infrastructure that supports a " +"number of OpenStack services but is most strongly associated with the " +"Compute service. Due to the nature of the message queue service, Alice and " +"Bob have similar security concerns. One of the larger concerns that remains " +"is that many systems have access to this queue and there is no way for a " +"consumer of the queue messages to verify which host or service placed the " +"messages on the queue. An attacker who is able to successfully place " +"messages on the queue is able to create and delete VM instances, attach the " +"block storage of any tenant and a myriad of other malicious actions. There " +"are a number of solutions on the horizon to fix this, with several proposals" +" for message signing and encryption making their way through the OpenStack " +"development process." +msgstr "" + +#: ./doc/security-guide/ch039_case-studies-messaging.xml7(para) +msgid "" +"In this case Alice's controls mimic those Bob has deployed for the public " +"cloud." +msgstr "" + +#: ./doc/security-guide/ch039_case-studies-messaging.xml11(para) +msgid "" +"Bob assumes that at some point infrastructure or networks underpinning the " +"Compute service may become compromised. Due to this, he recognizes the " +"importance of locking down access to the message queue. To do this Bob " +"deploys his RabbitMQ servers with SSL and X.509 client auth for access " +"control. This in turn limits the capabilities of an attacker who has " +"compromised a system that does not have queue access." +msgstr "" + +#: ./doc/security-guide/ch039_case-studies-messaging.xml12(para) +msgid "" +"Additionally, Bob adds strong network ACL rulesets to enforce which " +"endpoints can communicate with the message servers. This second control " +"provides some additional assurance should the other protections fail." +msgstr "" + +#: ./doc/security-guide/ch066_case-studies-compliance.xml3(title) +msgid "Case Studies: Compliance" +msgstr "" + +#: ./doc/security-guide/ch066_case-studies-compliance.xml4(para) +msgid "" +"In this case study we discuss how Alice and Bob would address common " +"compliance requirements. The preceding chapter refers to a wide variety of " +"compliance certifications and standards. Alice will address compliance in a " +"private cloud, while Bob will be focused on compliance for a public cloud." +msgstr "" + +#: ./doc/security-guide/ch066_case-studies-compliance.xml7(para) +msgid "" +"Alice is building an OpenStack private cloud for the United States " +"government, specifically to provide elastic compute environments for signal " +"processing. Alice has researched government compliance requirements, and has" +" identified that her private cloud will be required to certify against FISMA" +" and follow the FedRAMP accreditation process, which is required for all " +"federal agencies, departments and contractors to become a Certified Cloud " +"Provider (CCP). In this particular scenario for signal processing, the FISMA" +" controls required will most likely be FISMA High, which indicates possible " +"\"severe or catastrophic adverse effects\" should the information system " +"become compromised. In addition to FISMA Moderate controls Alice must ensure" +" her private cloud is FedRAMP certified, as this is a requirement for all " +"agencies that currently utilize, or host federal information within a cloud " +"environment." +msgstr "" + +#: ./doc/security-guide/ch066_case-studies-compliance.xml8(para) +msgid "" +"To meet these strict government regulations Alice undertakes a number of " +"activities. Scoping of requirements is particularly important due to the " +"volume of controls that must be implemented, which will be defined in NIST " +"Publication 800-53." +msgstr "" + +#: ./doc/security-guide/ch066_case-studies-compliance.xml9(para) +msgid "" +"All technology within her private cloud must be FIPS certified technology, " +"as mandated within NIST 800-53 and FedRAMP. As the U.S. Department of " +"Defense is involved, Security Technical Implementation Guides (STIGs) will " +"come into play, which are the configuration standards for DOD IA and IA-" +"enabled devices / systems. Alice notices a number of complications here as " +"there is no STIG for OpenStack, so she must address several underlying " +"requirements for each OpenStack service; for example, the networking SRG and" +" Application SRG will both be applicable (list of SRGs). Other " +"critical controls include ensuring that all identities in the cloud use PKI," +" that SELinux is enabled, that encryption exists for all wire-level " +"communications, and that continuous monitoring is in place and clearly " +"documented. Alice is not concerned with object encryption, as this will be " +"the tenants responsibility rather than the provider." +msgstr "" + +#: ./doc/security-guide/ch066_case-studies-compliance.xml10(para) +msgid "" +"If Alice has adequately scoped and executed these compliance activities, she" +" may begin the process to become FedRAMP compliant by hiring an approved " +"third-party auditor. Typically this process takes up to 6 months, after " +"which she will receive an Authority to Operate and can offer OpenStack cloud" +" services to the government." +msgstr "" + +#: ./doc/security-guide/ch066_case-studies-compliance.xml14(para) +msgid "" +"Bob is tasked with compliance for a new OpenStack public cloud deployment, " +"that is focused on providing cloud services to both small developers and " +"startups, as well as large enterprises. Bob recognizes that individual " +"developers are not necessarily concerned with compliance certifications, but" +" to larger enterprises certifications are critical. Specifically Bob desires" +" to achieve SOC 1, SOC 2 Security, as well as ISO 27001/2 as quickly as " +"possible. Bob references the Cloud Security Alliance Cloud Control Matrix " +"(CCM) to assist in identifying common controls across these three " +"certifications (such as periodic access reviews, auditable logging and " +"monitoring services, risk assessment activities, security reviews, etc). Bob" +" then engages an experienced audit team to conduct a gap analysis on the " +"public cloud deployment, reviews the results and fills any gaps identified. " +"Bob works with other team members to ensure that these security controls and" +" activities are regularly conducted for a typical audit period (~6-12 " +"months)." +msgstr "" + +#: ./doc/security-guide/ch066_case-studies-compliance.xml31(para) +msgid "" +"At the end of the audit period Bob has arranged for an external audit team " +"to review in-scope security controls at randomly sampled points of time over" +" a 6 month period. The audit team provides Bob with an official report for " +"SOC 1 and SOC 2, and separately for ISO 27001/2. As Bob has been diligent in" +" ensuring security controls are in place for his OpenStack public cloud, " +"there are no additional gaps exposed on the report. Bob can now provide " +"these official reports to his customers under NDA, and advertise that he is " +"SOC 1, SOC 2 and ISO 27001/2 compliant on his website." +msgstr "" + +#: ./doc/security-guide/ch021_paste-and-middleware.xml3(title) +msgid "API Endpoint Configuration Recommendations" +msgstr "" + +#: ./doc/security-guide/ch021_paste-and-middleware.xml4(para) +msgid "" +"This chapter provides recommendations for improving the security of both " +"public and internal endpoints." +msgstr "" + +#: ./doc/security-guide/ch021_paste-and-middleware.xml6(title) +msgid "Internal API Communications" +msgstr "" + +#: ./doc/security-guide/ch021_paste-and-middleware.xml7(para) +msgid "" +"OpenStack provides both public facing and private API endpoints. By default," +" OpenStack components use the publicly defined endpoints. The recommendation" +" is to configure these components to use the API endpoint within the proper " +"security domain." +msgstr "" + +#: ./doc/security-guide/ch021_paste-and-middleware.xml8(para) +msgid "" +"Services select their respective API endpoints based on the OpenStack " +"service catalog.  The issue here is these services may not obey the listed " +"public or internal API end point values. This can lead to internal " +"management traffic being routed to external API endpoints." +msgstr "" + +#: ./doc/security-guide/ch021_paste-and-middleware.xml10(title) +msgid "Configure Internal URLs in Identity Service Catalog" +msgstr "" + +#: ./doc/security-guide/ch021_paste-and-middleware.xml11(para) +msgid "" +"The Identity Service catalog should be aware of your internal URLs. While " +"this feature is not utilized by default, it may be leveraged through " +"configuration. Additionally, it should be forward-compatible with expectant " +"changes once this behavior becomes the default." +msgstr "" + +#: ./doc/security-guide/ch021_paste-and-middleware.xml12(para) +msgid "To register an internal URL for an endpoint:" +msgstr "" + +#: ./doc/security-guide/ch021_paste-and-middleware.xml22(title) +msgid "Configure Applications for Internal URLs" +msgstr "" + +#: ./doc/security-guide/ch021_paste-and-middleware.xml23(para) +msgid "" +"Some services can be forced to use specific API endpoints.  Therefore, it is" +" recommended that each OpenStack service communicating to the API of another" +" service must be explicitly configured to access the proper internal API " +"endpoint." +msgstr "" + +#: ./doc/security-guide/ch021_paste-and-middleware.xml24(para) +msgid "" +"Each project may present an inconsistent way of defining target API " +"endpoints. Future releases of OpenStack seek to resolve these " +"inconsistencies through consistent use of the Identity Service catalog." +msgstr "" + +#: ./doc/security-guide/ch021_paste-and-middleware.xml26(title) +msgid "Configuration Example #1: Nova" +msgstr "" + +#: ./doc/security-guide/ch021_paste-and-middleware.xml37(title) +msgid "Configuration Example #2: Cinder" +msgstr "" + +#: ./doc/security-guide/ch021_paste-and-middleware.xml44(title) +msgid "Paste and Middleware" +msgstr "" + +#: ./doc/security-guide/ch021_paste-and-middleware.xml45(para) +msgid "" +"Most API endpoints and other HTTP services in OpenStack utilize the Python " +"Paste Deploy library. This is important to understand from a security " +"perspective as it allows for manipulation of the request filter pipeline " +"through the application's configuration. Each element in this chain is " +"referred to as middleware. Changing the order of " +"filters in the pipeline or adding additional middleware may have " +"unpredictable security impact." +msgstr "" + +#: ./doc/security-guide/ch021_paste-and-middleware.xml46(para) +msgid "" +"It is not uncommon that implementors will choose to add additional " +"middleware to extend OpenStack's base functionality. We recommend " +"implementors make careful consideration of the potential exposure introduced" +" by the addition of non-standard software components to their HTTP request " +"pipeline." +msgstr "" + +#: ./doc/security-guide/ch021_paste-and-middleware.xml47(para) +msgid "" +"Additional information on Paste Deploy may be found at http://pythonpaste.org/deploy/." +msgstr "" + +#: ./doc/security-guide/ch021_paste-and-middleware.xml51(title) +msgid "API Endpoint Process Isolation & Policy" +msgstr "" + +#: ./doc/security-guide/ch021_paste-and-middleware.xml52(para) +msgid "" +"API endpoint processes, especially those that reside within the public " +"security domain should be isolated as much as possible. Where deployments " +"allow, API endpoints should be deployed on separate hosts for increased " +"isolation." +msgstr "" + +#: ./doc/security-guide/ch021_paste-and-middleware.xml54(title) +#: ./doc/security-guide/ch038_transport-security.xml119(title) +msgid "Namespaces" +msgstr "" + +#: ./doc/security-guide/ch021_paste-and-middleware.xml55(para) +msgid "" +"Many operating systems now provide compartmentalization support. Linux " +"supports namespaces to assign processes into independent domains. System " +"compartmentalization is covered in more detail in other parts of the guide." +msgstr "" + +#: ./doc/security-guide/ch021_paste-and-middleware.xml58(title) +#: ./doc/security-guide/ch038_transport-security.xml124(title) +msgid "Network Policy" +msgstr "" + +#: ./doc/security-guide/ch021_paste-and-middleware.xml59(para) +msgid "" +"API endpoints typically bridge multiple security domains, as such particular" +" attention should be paid to the compartmentalization of the API processes." +"  See the Security Domain Bridging section for " +"additional information in this area." +msgstr "" + +#: ./doc/security-guide/ch021_paste-and-middleware.xml60(para) +msgid "" +"With careful modeling, network ACLs and IDS technologies can be use to " +"enforce explicit point to point communication between network services. As " +"critical cross domain service, this type of explicit enforcement works well " +"for OpenStack's message queue service." +msgstr "" + +#: ./doc/security-guide/ch021_paste-and-middleware.xml61(para) +msgid "" +"Policy enforcement can be implemented through the configuration of services," +" host-based firewalls (such as IPTables), local policy (SELinux or " +"AppArmor), and optionally enforced through global network policy." +msgstr "" + +#: ./doc/security-guide/ch021_paste-and-middleware.xml64(title) +#: ./doc/security-guide/ch038_transport-security.xml129(title) +#: ./doc/security-guide/ch052_devices.xml90(title) +msgid "Mandatory Access Controls" +msgstr "" + +#: ./doc/security-guide/ch021_paste-and-middleware.xml65(para) +msgid "" +"API endpoint processes should be isolated from each other and other " +"processes on a machine. The configuration for those processes should be " +"restricted to those processes not only by Discretionary Access Controls, but" +" through Mandatory Access Controls. The goal of these enhanced access " +"control is to aid in the containment and escalation of API endpoint security" +" breaches.  With mandatory access controls, such breaches will severely " +"limit access to resources and provide earlier alerting on such events." +msgstr "" + +#: ./doc/security-guide/ch041_database-backend-considerations.xml3(title) +msgid "Database Backend Considerations" +msgstr "" + +#: ./doc/security-guide/ch041_database-backend-considerations.xml4(para) +msgid "" +"The choice of database server is an important consideration in the security " +"of an OpenStack deployment. While security considerations are not the only " +"basis on which a database server must be chosen, security considerations are" +" the only ones within the scope of this book. In practice, OpenStack only " +"supports two database types: PostgreSQL and MySQL." +msgstr "" + +#: ./doc/security-guide/ch041_database-backend-considerations.xml5(para) +msgid "" +"PostgreSQL has a number of desirable security features such as Kerberos " +"authentication, object-level security, and encryption support. The " +"PostgreSQL community has done well to provide solid guidance, documentation," +" and tooling to promote positive security practices." +msgstr "" + +#: ./doc/security-guide/ch041_database-backend-considerations.xml6(para) +msgid "" +"MySQL has a large community, wide-spread adoption, and provides high " +"availability options. MySQL also has the ability to provide enhanced client " +"authentication by way of plug-in authentication mechanisms. Forked " +"distributions in the MySQL community provide many options for consideration." +" It is important to choose a specific implementation of MySQL based on a " +"thorough evaluation of the security posture and the level of support " +"provided for the given distribution." +msgstr "" + +#: ./doc/security-guide/ch041_database-backend-considerations.xml8(title) +msgid "Security References for Database Backends" +msgstr "" + +#: ./doc/security-guide/ch041_database-backend-considerations.xml9(para) +msgid "" +"Those deploying MySQL or PostgreSQL are advised to refer to existing " +"security guidance. Some references are listed below:" +msgstr "" + +#: ./doc/security-guide/ch041_database-backend-considerations.xml10(para) +msgid "MySQL:" +msgstr "" + +#: ./doc/security-guide/ch041_database-backend-considerations.xml12(link) +msgid "OWASP MySQL Hardening" +msgstr "" + +#: ./doc/security-guide/ch041_database-backend-considerations.xml15(link) +msgid "MySQL Pluggable Authentication" +msgstr "" + +#: ./doc/security-guide/ch041_database-backend-considerations.xml18(link) +msgid "Security in MySQL" +msgstr "" + +#: ./doc/security-guide/ch041_database-backend-considerations.xml21(para) +msgid "PostgreSQL:" +msgstr "" + +#: ./doc/security-guide/ch041_database-backend-considerations.xml23(link) +msgid "OWASP PostgreSQL Hardening" +msgstr "" + +#: ./doc/security-guide/ch041_database-backend-considerations.xml26(link) +msgid "Total security in a PostgreSQL database" +msgstr "" + +#: ./doc/security-guide/ch014_best-practices-for-operator-mode-access.xml3(title) +msgid "Management Interfaces" +msgstr "" + +#: ./doc/security-guide/ch014_best-practices-for-operator-mode-access.xml4(para) +msgid "" +"It is necessary for administrators to perform command and control over the " +"cloud for various operational functions. It is important these command and " +"control facilities are understood and secured." +msgstr "" + +#: ./doc/security-guide/ch014_best-practices-for-operator-mode-access.xml5(para) +msgid "" +"OpenStack provides several management interfaces for operators and tenants:" +msgstr "" + +#: ./doc/security-guide/ch014_best-practices-for-operator-mode-access.xml7(para) +msgid "OpenStack Dashboard (Horizon)" +msgstr "" + +#: ./doc/security-guide/ch014_best-practices-for-operator-mode-access.xml10(para) +#: ./doc/security-guide/ch014_best-practices-for-operator-mode-access.xml69(title) +msgid "OpenStack API" +msgstr "" + +#: ./doc/security-guide/ch014_best-practices-for-operator-mode-access.xml13(para) +#: ./doc/security-guide/ch014_best-practices-for-operator-mode-access.xml93(title) +msgid "Secure Shell (SSH)" +msgstr "" + +#: ./doc/security-guide/ch014_best-practices-for-operator-mode-access.xml16(para) +msgid "OpenStack Management Utilities (nova-manage, glance-manage, etc.)" +msgstr "" + +#: ./doc/security-guide/ch014_best-practices-for-operator-mode-access.xml19(para) +msgid "Out-of-Band Management Interfaces (IPMI, etc.)" +msgstr "" + +#: ./doc/security-guide/ch014_best-practices-for-operator-mode-access.xml24(para) +msgid "" +"The OpenStack Dashboard (Horizon) provides administrators and tenants a web-" +"based graphical interface to provision and access cloud-based resources. The" +" dashboard communicates with the back-end services via calls to the " +"OpenStack API (discussed above)." +msgstr "" + +#: ./doc/security-guide/ch014_best-practices-for-operator-mode-access.xml26(title) +#: ./doc/security-guide/ch014_best-practices-for-operator-mode-access.xml72(title) +#: ./doc/security-guide/ch026_compute.xml13(title) +#: ./doc/security-guide/ch026_compute.xml40(title) +msgid "Capabilities" +msgstr "" + +#: ./doc/security-guide/ch014_best-practices-for-operator-mode-access.xml28(para) +msgid "" +"As a cloud administrator, the dashboard provides an overall view of the size" +" and state of your cloud. You can create users and tenants/projects, assign " +"users to tenant/projects and set limits on the resources available for them." +msgstr "" + +#: ./doc/security-guide/ch014_best-practices-for-operator-mode-access.xml31(para) +msgid "" +"The dashboard provides tenant-users a self-service portal to provision their" +" own resources within the limits set by administrators." +msgstr "" + +#: ./doc/security-guide/ch014_best-practices-for-operator-mode-access.xml34(para) +msgid "" +"The dashboard provides GUI support for routers and load-balancers. For " +"example, the dashboard now implements all of the main Networking features." +msgstr "" + +#: ./doc/security-guide/ch014_best-practices-for-operator-mode-access.xml37(para) +msgid "" +"It is an extensible Django web application that " +"allows easy plug-in of third-party products and services, such as billing, " +"monitoring, and additional management tools." +msgstr "" + +#: ./doc/security-guide/ch014_best-practices-for-operator-mode-access.xml40(para) +msgid "" +"The dashboard can also be branded for service providers and other commercial" +" vendors." +msgstr "" + +#: ./doc/security-guide/ch014_best-practices-for-operator-mode-access.xml47(para) +msgid "" +"The dashboard requires cookies and JavaScript to be enabled in the web " +"browser." +msgstr "" + +#: ./doc/security-guide/ch014_best-practices-for-operator-mode-access.xml50(para) +msgid "" +"The web server that hosts dashboard should be configured for SSL to ensure " +"data is encrypted." +msgstr "" + +#: ./doc/security-guide/ch014_best-practices-for-operator-mode-access.xml53(para) +msgid "" +"Both the Horizon web service and the OpenStack API it uses to communicate " +"with the back-end are susceptible to web attack vectors such as denial of " +"service and must be monitored." +msgstr "" + +#: ./doc/security-guide/ch014_best-practices-for-operator-mode-access.xml56(para) +msgid "" +"It is now possible (though there are numerous deployment/security " +"implications) to upload an image file directly from a user’s hard disk to " +"Glance through Horizon. For multi-GB images it is still strongly recommended" +" that the upload be done using the Glance CLI" +msgstr "" + +#: ./doc/security-guide/ch014_best-practices-for-operator-mode-access.xml59(para) +msgid "" +"Create and manage security groups through dashboard. The security groups " +"allows L3-L4 packet filtering for security policies to protect virtual " +"machines" +msgstr "" + +#: ./doc/security-guide/ch014_best-practices-for-operator-mode-access.xml65(citetitle) +msgid "Grizzly Release Notes" +msgstr "" + +#: ./doc/security-guide/ch014_best-practices-for-operator-mode-access.xml70(para) +msgid "" +"The OpenStack API is a RESTful web service endpoint to access, provision and" +" automate cloud-based resources.  Operators and users typically access the " +"API through command-line utilities (i.e. Nova, Glance, etc.), language-" +"specific libraries, or third-party tools." +msgstr "" + +#: ./doc/security-guide/ch014_best-practices-for-operator-mode-access.xml74(para) +msgid "" +"To the cloud administrator the API provides an overall view of the size and " +"state of the cloud deployment and allows the creation of users, " +"tenants/projects, assigning users to tenants/projects and specifying " +"resource quotas on a per tenant/project basis." +msgstr "" + +#: ./doc/security-guide/ch014_best-practices-for-operator-mode-access.xml77(para) +msgid "" +"The API provides a tenant interface for provisioning, managing, and " +"accessing their resources." +msgstr "" + +#: ./doc/security-guide/ch014_best-practices-for-operator-mode-access.xml84(para) +msgid "" +"The API service should be configured for SSL to ensure data is encrypted." +msgstr "" + +#: ./doc/security-guide/ch014_best-practices-for-operator-mode-access.xml87(para) +msgid "" +"As a web service, OpenStack API is susceptible to familiar web site attack " +"vectors such as denial of service attacks." +msgstr "" + +#: ./doc/security-guide/ch014_best-practices-for-operator-mode-access.xml94(para) +msgid "" +"It has become industry practice to use secure shell (SSH) access for the " +"management of Linux and Unix systems. SSH uses secure cryptographic " +"primitives for communication. With the scope and importance of SSH in " +"typical OpenStack deployments, it is important to understand best practices " +"for deploying SSH." +msgstr "" + +#: ./doc/security-guide/ch014_best-practices-for-operator-mode-access.xml96(title) +msgid "Host Key Fingerprints" +msgstr "" + +#: ./doc/security-guide/ch014_best-practices-for-operator-mode-access.xml97(para) +msgid "" +"Often overlooked is the need for key management for SSH hosts. As most or " +"all hosts in an OpenStack deployment will provide an SSH service, it is " +"important to have confidence in connections to these hosts. It cannot be " +"understated that failing to provide a reasonably secure and accessible " +"method to verify SSH host key fingerprints is ripe for abuse and " +"exploitation." +msgstr "" + +#: ./doc/security-guide/ch014_best-practices-for-operator-mode-access.xml98(para) +msgid "" +"All SSH daemons have private host keys and, upon connection, offer a host " +"key fingerprint. This host key fingerprint is the hash of an unsigned public" +" key. It is important these host key fingerprints are known in advance of " +"making SSH connections to those hosts. Verification of host key fingerprints" +" is instrumental in detecting man-in-the-middle attacks." +msgstr "" + +#: ./doc/security-guide/ch014_best-practices-for-operator-mode-access.xml99(para) +msgid "" +"Typically, when an SSH daemon is installed, host keys will be generated. It " +"is necessary that the hosts have sufficient entropy during host key " +"generation. Insufficient entropy during host key generation can result in " +"the possibility to eavesdrop on SSH sessions." +msgstr "" + +#: ./doc/security-guide/ch014_best-practices-for-operator-mode-access.xml100(para) +msgid "" +"Once the SSH host key is generated, the host key fingerprint should be " +"stored in a secure and queriable location. One particularly convenient " +"solution is DNS using SSHFP resource records as defined in RFC-4255. For " +"this to be secure, it is necessary that DNSSEC be deployed." +msgstr "" + +#: ./doc/security-guide/ch014_best-practices-for-operator-mode-access.xml104(title) +msgid "Management Utilities" +msgstr "" + +#: ./doc/security-guide/ch014_best-practices-for-operator-mode-access.xml105(para) +msgid "" +"The OpenStack Management Utilities are open-source Python command-line " +"clients that make API calls. There is a client for each OpenStack service " +"(nova, glance, etc.). In addition to the standard CLI client, most of the " +"services have a management command line which makes direct calls to the " +"database. These dedicated management utilities are slowly being deprecated." +msgstr "" + +#: ./doc/security-guide/ch014_best-practices-for-operator-mode-access.xml115(para) +msgid "" +"The dedicated management utilities (*-manage) in some cases use the direct " +"database connection." +msgstr "" + +#: ./doc/security-guide/ch014_best-practices-for-operator-mode-access.xml118(para) +msgid "" +"Ensure that the .rc file which has your credential information is secured." +msgstr "" + +#: ./doc/security-guide/ch014_best-practices-for-operator-mode-access.xml124(para) +msgid "" +"OpenStack End User Guide section command line clients " +"overview" +msgstr "" + +#: ./doc/security-guide/ch014_best-practices-for-operator-mode-access.xml125(para) +msgid "" +"OpenStack End User Guide section Download and source the OpenStack RC " +"file" +msgstr "" + +#: ./doc/security-guide/ch014_best-practices-for-operator-mode-access.xml129(title) +msgid "Out-of-Band Management Interface" +msgstr "" + +#: ./doc/security-guide/ch014_best-practices-for-operator-mode-access.xml130(para) +msgid "" +"OpenStack management relies on out-of-band management interfaces such as the" +" IPMI protocol to access into nodes running OpenStack components. IPMI is a " +"very popular specification to remotely manage, diagnose and reboot servers " +"whether the operating system is running or the system has crashed." +msgstr "" + +#: ./doc/security-guide/ch014_best-practices-for-operator-mode-access.xml134(para) +msgid "" +"Use strong passwords and safeguard them, or use client-side SSL " +"authentication." +msgstr "" + +#: ./doc/security-guide/ch014_best-practices-for-operator-mode-access.xml137(para) +msgid "" +"Ensure that the network interfaces are on their own private(management or a " +"separate) network. Segregate management domains with firewalls or other " +"network gear." +msgstr "" + +#: ./doc/security-guide/ch014_best-practices-for-operator-mode-access.xml140(para) +msgid "" +"If you use a web interface to interact with the " +"BMC/IPMI, always use the SSL interface, such as https" +" or port 443. This SSL interface should NOT use self-signed certificates, as is often " +"default, but should have trusted certificates using the correctly defined " +"fully qualified domain names (FQDNs)." +msgstr "" + +#: ./doc/security-guide/ch014_best-practices-for-operator-mode-access.xml149(para) +msgid "" +"Monitor the traffic on the management network. The anomalies might be easier" +" to track than on the busier compute nodes." +msgstr "" + +#: ./doc/security-guide/ch014_best-practices-for-operator-mode-access.xml154(para) +msgid "" +"Out of band management interfaces also often include graphical machine " +"console access. It is often possible, although not necessarily default, that" +" these interfaces are encrypted. Consult with your system software " +"documentation for encrypting these interfaces." +msgstr "" + +#: ./doc/security-guide/ch014_best-practices-for-operator-mode-access.xml158(link) +msgid "Hacking servers that are turned off" +msgstr "" + +#: ./doc/security-guide/ch028_case-studies-identity-management.xml3(title) +msgid "Case Studies: Identity Management" +msgstr "" + +#: ./doc/security-guide/ch028_case-studies-identity-management.xml4(para) +msgid "" +"In this case study we discuss how Alice and Bob would address configuration " +"of OpenStack core services. These include the Keystone Identity service, " +"Dashboard, and Compute services. Alice will be concerned with integration " +"into the existing government directory services, while Bob will need to " +"provide access to the public." +msgstr "" + +#: ./doc/security-guide/ch028_case-studies-identity-management.xml7(para) +msgid "" +"Alice's enterprise has a well-established directory service with two-factor " +"authentication for all users. She configures Keystone to support an external" +" authentication service supporting authentication with government-issued " +"access cards. She also uses an external LDAP server to provide role " +"information for the users that is integrated with the access control policy." +" Due to FedRAMP compliance requirements, Alice implements two-factor " +"authentication on the Management network for all administrator access." +msgstr "" + +#: ./doc/security-guide/ch028_case-studies-identity-management.xml8(para) +msgid "" +"Alice also deploys the Dashboard to manage many aspects of the cloud.  She " +"deploys the Dashboard with HSTS to ensure that only HTTPS is used.  The " +"Dashboard resides within an internal subdomain of the private network domain" +" name system." +msgstr "" + +#: ./doc/security-guide/ch028_case-studies-identity-management.xml9(para) +msgid "" +"Alice decides to use SPICE instead of VNC for the virtual console.  She " +"wants to take advantage of the emerging capabilities in SPICE." +msgstr "" + +#: ./doc/security-guide/ch028_case-studies-identity-management.xml13(para) +msgid "" +"Bob must support authentication by the general public, so he elects to use " +"provide for username / password authentication. He has concerns about brute " +"force attacks attempting to crack user passwords, so he also uses an " +"external authentication extension that throttles the number of failed login " +"attempts. Bob's Management network is separate from the other networks " +"within his cloud, but can be reached from his corporate network via ssh. As " +"recommended earlier, Bob requires administrators to use two-factor " +"authentication on the Management network to reduce the risk from compromised" +" administrator passwords." +msgstr "" + +#: ./doc/security-guide/ch028_case-studies-identity-management.xml14(para) +msgid "" +"Bob also deploys the Dashboard to manage many aspects of the cloud.  He " +"deploys the Dashboard with HSTS to ensure that only HTTPS is used.  He has " +"ensured that the Dashboard is deployed on a second-level domain due to the " +"limitations of the same-origin policy. He also disables " +"HORIZON_IMAGES_ALLOW_UPLOAD to prevent resource exhaustion." +msgstr "" + +#: ./doc/security-guide/ch028_case-studies-identity-management.xml15(para) +msgid "" +"Bob decides to use VNC for his virtual console for its maturity and security" +" features." +msgstr "" + +#: ./doc/security-guide/ch037_risks.xml3(title) +msgid "Message Queuing Architecture" +msgstr "" + +#: ./doc/security-guide/ch037_risks.xml4(para) +msgid "" +"Inter-process communication within OpenStack is facilitated via message " +"queueing services. Today, three messaging service backends are supported:" +msgstr "" + +#: ./doc/security-guide/ch037_risks.xml6(para) +msgid "RabbitMQ" +msgstr "" + +#: ./doc/security-guide/ch037_risks.xml9(para) +msgid "Qpid" +msgstr "" + +#: ./doc/security-guide/ch037_risks.xml12(para) +msgid "ZeroMQ" +msgstr "" + +#: ./doc/security-guide/ch037_risks.xml15(para) +msgid "" +"Both RabbitMQ and Qpid are Advanced Message Queuing Protocol (AMQP) " +"frameworks which provide message queues for peer-to-peer communication. " +"Queue implementations are typically deployed as centralized or decentralized" +" pool of queue servers. ZeroMQ differs by communicating directly using TCP " +"sockets between peers." +msgstr "" + +#: ./doc/security-guide/ch037_risks.xml16(para) +msgid "" +"Message queues effectively facilitate command and control functions across " +"OpenStack deployments. Once access to the queue is permitted no further " +"authorization checks are performed. Services accessible via the queue do " +"validate the contexts and tokens within the actual message payload. However," +" awareness of the token's expiration value should be noted as these tokens " +"are potentially replayable and may provide authorization for other services " +"within the infrastructure." +msgstr "" + +#: ./doc/security-guide/ch037_risks.xml17(para) +msgid "" +"OpenStack does not support message-level confidence (i.e., message signing)." +" Because of this, the message transport itself must be secured and " +"authentication to the queue server must be performed. For HA configurations," +" queue to queue authentication and encryption should to be performed as " +"well." +msgstr "" + +#: ./doc/security-guide/ch037_risks.xml18(para) +msgid "" +"With ZeroMQ messaging, IPC sockets are used on individual machines. These " +"sockets may be vulnerable to attack for local message injection and snooping" +" unless secured by an operator." +msgstr "" + +#: ./doc/security-guide/ch026_compute.xml3(title) +#: ./doc/security-guide/ch004_book-introduction.xml122(title) +msgid "Compute" +msgstr "" + +#: ./doc/security-guide/ch026_compute.xml4(para) +msgid "" +"The Compute Service (Nova) is one of the more complex OpenStack services.  " +"It runs in many locations throughout the cloud and interacts with a variety " +"of internal services.  For this reason, most of our recommendations " +"regarding best practices for Compute Service configuration are distributed " +"throughout this book. We provide specific details in the sections on " +"Management, API Endpoints, Messaging, and Database." +msgstr "" + +#: ./doc/security-guide/ch026_compute.xml6(title) +msgid "Virtual Console Selection" +msgstr "" + +#: ./doc/security-guide/ch026_compute.xml7(para) +msgid "" +"One decision a cloud architect will need to make regarding Compute Service " +"configuration is whether to use VNC or SPICE. Below we provide some details " +"on the differences between these options." +msgstr "" + +#: ./doc/security-guide/ch026_compute.xml9(title) +msgid "Virtual Network Computer (VNC)" +msgstr "" + +#: ./doc/security-guide/ch026_compute.xml10(para) +msgid "" +"OpenStack can be configured to provide remote desktop console access to " +"instances for tenants and/or administrators using the Virtual Network " +"Computer (VNC) protocol.  " +msgstr "" + +#: ./doc/security-guide/ch026_compute.xml15(para) +msgid "" +"The OpenStack Dashboard (Horizon) can provide a VNC console for instances " +"directly on the web page using the HTML5 noVNC client.  This requires the " +"nova-novncproxy service to bridge" +" from the public network to the management network." +msgstr "" + +#: ./doc/security-guide/ch026_compute.xml18(para) +msgid "" +"The nova command line utility can return a URL for the VNC console for " +"access by the nova Java VNC client. This requires the nova-xvpvncproxy " +"service to bridge from the public network to the management network." +msgstr "" + +#: ./doc/security-guide/ch026_compute.xml25(para) +msgid "" +"The nova-novncproxyand nova-" +"xvpvncproxy services by default open public-facing ports that are token " +"authenticated." +msgstr "" + +#: ./doc/security-guide/ch026_compute.xml28(para) +msgid "" +"By default, the remote desktop traffic is not encrypted. Havana is expected " +"to have VNC connections secured by Kerberos." +msgstr "" + +#: ./doc/security-guide/ch026_compute.xml34(link) +msgid "Secure Connections to VNC ports" +msgstr "" + +#: ./doc/security-guide/ch026_compute.xml37(title) +msgid "Simple Protocol for Independent Computing Environments (SPICE)" +msgstr "" + +#: ./doc/security-guide/ch026_compute.xml38(para) +msgid "" +"As an alternative to VNC, OpenStack provides remote desktop access to guest " +"virtual machines using the Simple Protocol for Independent Computing " +"Environments (SPICE) protocol." +msgstr "" + +#: ./doc/security-guide/ch026_compute.xml42(para) +msgid "" +"SPICE is supported by the OpenStack Dashboard (Horizon) directly on the " +"instance web page.  This requires the nova-spicehtml5proxy service." +msgstr "" + +#: ./doc/security-guide/ch026_compute.xml45(para) +msgid "" +"The nova command line utility can return a URL for SPICE console for access " +"by a SPICE-html client." +msgstr "" + +#: ./doc/security-guide/ch026_compute.xml50(title) +msgid "Limitations" +msgstr "" + +#: ./doc/security-guide/ch026_compute.xml52(para) +msgid "" +"Although SPICE has many advantages over VNC, the spice-html5 browser " +"integration currently doesn't really allow admins to take advantage of any " +"of the benefits. To take advantage of SPICE features like multi-monitor, USB" +" pass through, etc. admins are recommended to use a standalone SPICE client " +"within the Management Network." +msgstr "" + +#: ./doc/security-guide/ch026_compute.xml59(para) +msgid "" +"The nova-spicehtml5proxy service by default opens public-facing ports that " +"are token authenticated." +msgstr "" + +#: ./doc/security-guide/ch026_compute.xml62(para) +msgid "" +"The functionality and integration are still evolving. We will access the " +"features in the next release and make recommendations." +msgstr "" + +#: ./doc/security-guide/ch026_compute.xml65(para) +msgid "" +"As is the case for VNC, at this time we recommend using SPICE from the " +"management network in addition to limiting use to few individuals." +msgstr "" + +#: ./doc/security-guide/ch026_compute.xml71(link) +msgid "SPICE Console" +msgstr "" + +#: ./doc/security-guide/ch026_compute.xml72(link) +msgid "Red Hat bug 913607" +msgstr "" + +#: ./doc/security-guide/ch026_compute.xml73(link) +msgid "SPICE support in RDO Grizzly" +msgstr "" + +#. When image changes, this message will be marked fuzzy or untranslated for +#. you. +#. It doesn't matter what you translate it to: it's not used at all. +#: ./doc/security-guide/ch013_node-bootstrapping.xml60(None) +#: ./doc/security-guide/ch013_node-bootstrapping.xml65(None) +msgid "" +"@@image: 'static/node-provisioning-pxe.png'; " +"md5=51b76c5aced74f935490b37ba921dc43" +msgstr "" + +#: ./doc/security-guide/ch013_node-bootstrapping.xml8(title) +msgid "Integrity Life-cycle" +msgstr "" + +#: ./doc/security-guide/ch013_node-bootstrapping.xml9(para) +msgid "" +"We define integrity life cycle as a deliberate process that provides " +"assurance that we are always running the expected software with the expected" +" configurations throughout the cloud. This process begins with secure " +"bootstrapping and is maintained through configuration management and " +"security monitoring. This chapter provides recommendations on how to " +"approach the integrity life-cycle process." +msgstr "" + +#: ./doc/security-guide/ch013_node-bootstrapping.xml17(title) +msgid "Secure Bootstrapping" +msgstr "" + +#: ./doc/security-guide/ch013_node-bootstrapping.xml18(para) +msgid "" +"Nodes in the cloud -- including compute, storage, network, service, and " +"hybrid nodes -- should have an automated provisioning process. This ensures " +"that nodes are provisioned consistently and correctly. This also facilitates" +" security patching, upgrading, bug fixing, and other critical changes. Since" +" this process installs new software that runs at the highest privilege " +"levels in the cloud, it is important to verify that the correct software is " +"installed. This includes the earliest stages of the boot process." +msgstr "" + +#: ./doc/security-guide/ch013_node-bootstrapping.xml27(para) +msgid "" +"There are a variety of technologies that enable verification of these early " +"boot stages. These typically require hardware support such as the trusted " +"platform module (TPM), Intel Trusted Execution Technology (TXT), dynamic " +"root of trust measurement (DRTM), and Unified Extensible Firmware Interface " +"(UEFI) secure boot. In this book, we will refer to all of these collectively" +" as secure boot technologies. We recommend using secure" +" boot, while acknowledging that many of the pieces necessary to deploy this " +"require advanced technical skills in order to customize the tools for each " +"environment. Utilizing secure boot will require deeper integration and " +"customization than many of the other recommendations in this guide. TPM " +"technology, while common in most business class laptops and desktops for " +"several years, and is now becoming available in servers together with " +"supporting BIOS. Proper planning is essential to a successful secure boot " +"deployment." +msgstr "" + +#: ./doc/security-guide/ch013_node-bootstrapping.xml43(para) +msgid "" +"A complete tutorial on secure boot deployment is beyond the scope of this " +"book. Instead, here we provide a framework for how to integrate secure boot " +"technologies with the typical node provisioning process. For additional " +"details, cloud architects should refer to the related specifications and " +"software configuration manuals." +msgstr "" + +#: ./doc/security-guide/ch013_node-bootstrapping.xml50(title) +msgid "Node Provisioning" +msgstr "" + +#: ./doc/security-guide/ch013_node-bootstrapping.xml51(para) +msgid "" +"Nodes should use Preboot eXecution Environment (PXE) for provisioning. This " +"significantly reduces the effort required for redeploying nodes. The typical" +" process involves the node receiving various boot stages (i.e., " +"progressively more complex software to execute) from a server." +msgstr "" + +#: ./doc/security-guide/ch013_node-bootstrapping.xml68(para) +msgid "" +"We recommend using a separate, isolated network within the management " +"security domain for provisioning. This network will handle all PXE traffic, " +"along with the subsequent boot stage downloads depicted above. Note that the" +" node boot process begins with two insecure operations: DHCP and TFTP. Then " +"the boot process downloads over SSL the remaining information required to " +"deploy the node. This information might include an initramfs and a kernel. " +"This concludes by downloading the remaining information needed to deploy the" +" node. This may be an operating system installer, a basic install managed by" +" Chef or Puppet, or even a complete file " +"system image that is written directly to disk." +msgstr "" + +#: ./doc/security-guide/ch013_node-bootstrapping.xml82(para) +msgid "" +"While utilizing SSL during the PXE boot process is somewhat more " +"challenging, common PXE firmware projects, such as iPXE, provide this " +"support. Typically this involves building the PXE firmware with knowledge of" +" the allowed SSL certificate chain(s) so that it can properly validate the " +"server certificate.  This raises the bar for an attacker by limiting the " +"number of insecure, plain text network operations." +msgstr "" + +#: ./doc/security-guide/ch013_node-bootstrapping.xml92(title) +msgid "Verified Boot" +msgstr "" + +#: ./doc/security-guide/ch013_node-bootstrapping.xml93(para) +msgid "" +"In general, there are two different strategies for verifying the boot " +"process. Traditional secure boot will validate the code" +" run at each step in the process, and stop the boot if code is incorrect. " +"Boot attestation will record which code is run at each " +"step, and provide this information to another machine as proof that the boot" +" process completed as expected. In both cases, the first step is to measure " +"each piece of code before it is run. In this context, a measurement is " +"effectively a SHA-1 hash of the code, taken before it is executed.  The hash" +" is stored in a platform configuration register (PCR) in the TPM." +msgstr "" + +#: ./doc/security-guide/ch013_node-bootstrapping.xml105(para) +msgid "Note: SHA-1 is used here because this is what the TPM chips support." +msgstr "" + +#: ./doc/security-guide/ch013_node-bootstrapping.xml107(para) +msgid "" +"Each TPM has at least 24 PCRs. The TCG Generic Server Specification, v1.0, " +"March 2005, defines the PCR assignments for boot-time integrity " +"measurements. The table below shows a typical PCR configuration. The context" +" indicates if the values are determined based on the node hardware " +"(firmware) or the software provisioned onto the node. Some values are " +"influenced by firmware versions, disk sizes, and other low-level " +"information. Therefore, it is important to have good practices in place " +"around configuration management to ensure that each system deployed is " +"configured exactly as desired." +msgstr "" + +#: ./doc/security-guide/ch013_node-bootstrapping.xml127(emphasis) +msgid "Register" +msgstr "" + +#: ./doc/security-guide/ch013_node-bootstrapping.xml128(emphasis) +msgid "What Is Measured" +msgstr "" + +#: ./doc/security-guide/ch013_node-bootstrapping.xml131(emphasis) +msgid "Context" +msgstr "" + +#: ./doc/security-guide/ch013_node-bootstrapping.xml134(para) +msgid "PCR-00" +msgstr "" + +#: ./doc/security-guide/ch013_node-bootstrapping.xml135(para) +msgid "" +"Core Root of Trust Measurement (CRTM), Bios code, Host platform extensions" +msgstr "" + +#: ./doc/security-guide/ch013_node-bootstrapping.xml137(para) +#: ./doc/security-guide/ch013_node-bootstrapping.xml142(para) +#: ./doc/security-guide/ch013_node-bootstrapping.xml147(para) +msgid "Hardware" +msgstr "" + +#: ./doc/security-guide/ch013_node-bootstrapping.xml140(para) +msgid "PCR-01" +msgstr "" + +#: ./doc/security-guide/ch013_node-bootstrapping.xml141(para) +msgid "Host Platform Configuration" +msgstr "" + +#: ./doc/security-guide/ch013_node-bootstrapping.xml145(para) +msgid "PCR-02" +msgstr "" + +#: ./doc/security-guide/ch013_node-bootstrapping.xml146(para) +msgid "Option ROM Code " +msgstr "" + +#: ./doc/security-guide/ch013_node-bootstrapping.xml150(para) +msgid "PCR-03" +msgstr "" + +#: ./doc/security-guide/ch013_node-bootstrapping.xml151(para) +msgid "Option ROM Configuration and Data " +msgstr "" + +#: ./doc/security-guide/ch013_node-bootstrapping.xml152(para) +msgid "Hardware " +msgstr "" + +#: ./doc/security-guide/ch013_node-bootstrapping.xml155(para) +msgid "PCR-04" +msgstr "" + +#: ./doc/security-guide/ch013_node-bootstrapping.xml156(para) +msgid "Initial Program Loader (IPL) Code. For example, master boot record." +msgstr "" + +#: ./doc/security-guide/ch013_node-bootstrapping.xml158(para) +#: ./doc/security-guide/ch013_node-bootstrapping.xml163(para) +#: ./doc/security-guide/ch013_node-bootstrapping.xml168(para) +#: ./doc/security-guide/ch013_node-bootstrapping.xml173(para) +#: ./doc/security-guide/ch013_node-bootstrapping.xml179(para) +#: ./doc/security-guide/ch013_node-bootstrapping.xml184(para) +#: ./doc/security-guide/ch013_node-bootstrapping.xml189(para) +msgid "Software " +msgstr "" + +#: ./doc/security-guide/ch013_node-bootstrapping.xml161(para) +msgid "PCR-05" +msgstr "" + +#: ./doc/security-guide/ch013_node-bootstrapping.xml162(para) +msgid "IPL Code Configuration and Data " +msgstr "" + +#: ./doc/security-guide/ch013_node-bootstrapping.xml166(para) +msgid "PCR-06" +msgstr "" + +#: ./doc/security-guide/ch013_node-bootstrapping.xml167(para) +msgid "State Transition and Wake Events " +msgstr "" + +#: ./doc/security-guide/ch013_node-bootstrapping.xml171(para) +msgid "PCR-07" +msgstr "" + +#: ./doc/security-guide/ch013_node-bootstrapping.xml172(para) +msgid "Host Platform Manufacturer Control " +msgstr "" + +#: ./doc/security-guide/ch013_node-bootstrapping.xml176(para) +msgid "PCR-08" +msgstr "" + +#: ./doc/security-guide/ch013_node-bootstrapping.xml177(para) +msgid "Platform specific, often Kernel, Kernel Extensions, and Drivers" +msgstr "" + +#: ./doc/security-guide/ch013_node-bootstrapping.xml182(para) +msgid "PCR-09" +msgstr "" + +#: ./doc/security-guide/ch013_node-bootstrapping.xml183(para) +msgid "Platform specific, often Initramfs" +msgstr "" + +#: ./doc/security-guide/ch013_node-bootstrapping.xml187(para) +msgid "PCR-10 to PCR-23" +msgstr "" + +#: ./doc/security-guide/ch013_node-bootstrapping.xml188(para) +msgid "Platform specific " +msgstr "" + +#: ./doc/security-guide/ch013_node-bootstrapping.xml194(para) +msgid "" +"At the time of this writing, very few clouds are using secure boot " +"technologies in a production environment. As a result, these technologies " +"are still somewhat immature. We recommend planning carefully in terms of " +"hardware selection. For example, ensure that you have a TPM and Intel TXT " +"support. Then verify how the node hardware vendor populates the PCR values. " +"For example, which values will be available for validation. Typically the " +"PCR values listed under the software context in the table above are the ones" +" that a cloud architect has direct control over. But even these may change " +"as the software in the cloud is upgraded.  Configuration management should " +"be linked into the PCR policy engine to ensure that the validation is always" +" up to date." +msgstr "" + +#: ./doc/security-guide/ch013_node-bootstrapping.xml207(para) +msgid "" +"Each manufacturer must provide the BIOS and firmware code for their servers." +" Different servers, hypervisors, and operating systems will choose to " +"populate different PCRs.  In most real world deployments, it will be " +"impossible to validate every PCR against a known good quantity (\"golden " +"measurement\"). Experience has shown that, even within a single vendor's " +"product line, the measurement process for a given PCR may not be consistent." +" We recommend establishing a baseline for each server and monitoring the PCR" +" values for unexpected changes. Third-party software may be available to " +"assist in the TPM provisioning and monitoring process, depending upon your " +"chosen hypervisor solution." +msgstr "" + +#: ./doc/security-guide/ch013_node-bootstrapping.xml219(para) +msgid "" +"The initial program loader (IPL) code will most likely be the PXE firmware, " +"assuming the node deployment strategy outlined above. Therefore, the secure " +"boot or boot attestation process can measure all of the early stage boot " +"code, such as, bios, firmware, and the like, the PXE firmware, and the node " +"kernel. Ensuring that each node has the correct versions of these pieces " +"installed provides a solid foundation on which to build the rest of the node" +" software stack." +msgstr "" + +#: ./doc/security-guide/ch013_node-bootstrapping.xml227(para) +msgid "" +"Depending on the strategy selected, in the event of a failure the node will " +"either fail to boot or it can report the failure back to another entity in " +"the cloud. For secure boot, the node will fail to boot and a provisioning " +"service within the management security domain must recognize this and log " +"the event. For boot attestation, the node will already be running when the " +"failure is detected. In this case the node should be immediately quarantined" +" by disabling its network access. Then the event should be analyzed for the " +"root cause. In either case, policy should dictate how to proceed after a " +"failure. A cloud may automatically attempt to re-provision a node a certain " +"number of times. Or it may immediately notify a cloud administrator to " +"investigate the problem. The right policy here will be deployment and " +"failure mode specific." +msgstr "" + +#: ./doc/security-guide/ch013_node-bootstrapping.xml243(title) +msgid "Node Hardening" +msgstr "" + +#: ./doc/security-guide/ch013_node-bootstrapping.xml244(para) +msgid "" +"At this point we know that the node has booted with the correct kernel and " +"underlying components. There are many paths for hardening a given operating " +"system deployment. The specifics on these steps are outside of the scope of " +"this book.  We recommend following the guidance from a hardening guide " +"specific to your operating system.  For example, the security technical implementation " +"guides (STIG) and the NSA" +" guides are useful starting places." +msgstr "" + +#: ./doc/security-guide/ch013_node-bootstrapping.xml254(para) +msgid "" +"The nature of the nodes makes additional hardening possible. We recommend " +"the following additional steps for production nodes:" +msgstr "" + +#: ./doc/security-guide/ch013_node-bootstrapping.xml259(para) +msgid "" +"Use a read-only file system where possible. Ensure that writeable file " +"systems do not permit execution.  This can be handled through the mount " +"options provided in /etc/fstab." +msgstr "" + +#: ./doc/security-guide/ch013_node-bootstrapping.xml265(para) +msgid "" +"Use a mandatory access control policy to contain the instances, the node " +"services, and any other critical processes and data on the node.  See the " +"discussions on sVirt / SELinux and AppArmor below." +msgstr "" + +#: ./doc/security-guide/ch013_node-bootstrapping.xml271(para) +msgid "" +"Remove any unnecessary software packages. This should result in a very " +"stripped down installation because a compute node has a relatively small " +"number of dependencies." +msgstr "" + +#: ./doc/security-guide/ch013_node-bootstrapping.xml277(para) +msgid "" +"Finally, the node kernel should have a mechanism to validate that the rest " +"of the node starts in a known good state. This provides the necessary link " +"from the boot validation process to validating the entire system. The steps " +"for doing this will be deployment specific. As an example, a kernel module " +"could verify a hash over the blocks comprising the file system before " +"mounting it using dm-" +"verity." +msgstr "" + +#: ./doc/security-guide/ch013_node-bootstrapping.xml289(title) +msgid "Runtime Verification" +msgstr "" + +#: ./doc/security-guide/ch013_node-bootstrapping.xml290(para) +msgid "" +"Once the node is running, we need to ensure that it remains in a good state " +"over time. Broadly speaking, this includes both configuration management and" +" security monitoring. The goals for each of these areas are different. By " +"checking both, we achieve higher assurance that the system is operating as " +"desired. We discuss configuration management in the management section, and " +"security monitoring below." +msgstr "" + +#: ./doc/security-guide/ch013_node-bootstrapping.xml298(title) +msgid "Intrusion Detection System" +msgstr "" + +#: ./doc/security-guide/ch013_node-bootstrapping.xml299(para) +msgid "" +"Host-based intrusion detection tools are also useful for automated " +"validation of the cloud internals. There are a wide variety of host-based " +"intrusion detection tools available. Some are open source projects that are " +"freely available, while others are commercial. Typically these tools analyze" +" data from a variety of sources and produce security alerts based on rule " +"sets and/or training. Typical capabilities include log analysis, file " +"integrity checking, policy monitoring, and rootkit detection. More advanced " +"-- often custom -- tools can validate that in-memory process images match " +"the on-disk executable and validate the execution state of a running " +"process." +msgstr "" + +#: ./doc/security-guide/ch013_node-bootstrapping.xml311(para) +msgid "" +"One critical policy decision for a cloud architect is what to do with the " +"output from a security monitoring tool. There are effectively two options. " +"The first is to alert a human to investigate and/or take corrective action. " +"This could be done by including the security alert in a log or events feed " +"for cloud administrators. The second option is to have the cloud take some " +"form of remedial action automatically, in addition to logging the event. " +"Remedial actions could include anything from re-installing a node to " +"performing a minor service configuration. However, automated remedial action" +" can be challenging due to the possibility of false positives." +msgstr "" + +#: ./doc/security-guide/ch013_node-bootstrapping.xml322(para) +msgid "" +"False positives occur when the security monitoring tool produces a security " +"alert for a benign event. Due to the nature of security monitoring tools, " +"false positives will most certainly occur from time to time. Typically a " +"cloud administrator can tune security monitoring tools to reduce the false " +"positives, but this may also reduce the overall detection rate at the same " +"time. These classic trade-offs must be understood and accounted for when " +"setting up a security monitoring system in the cloud." +msgstr "" + +#: ./doc/security-guide/ch013_node-bootstrapping.xml331(para) +msgid "" +"The selection and configuration of a host-based intrusion detection tool is " +"highly deployment specific. We recommend starting by exploring the following" +" open source projects which implement a variety of host-based intrusion " +"detection and file monitoring features." +msgstr "" + +#: ./doc/security-guide/ch013_node-bootstrapping.xml339(link) +msgid "OSSEC" +msgstr "" + +#: ./doc/security-guide/ch013_node-bootstrapping.xml343(link) +msgid "Samhain" +msgstr "" + +#: ./doc/security-guide/ch013_node-bootstrapping.xml348(link) +msgid "Tripwire" +msgstr "" + +#: ./doc/security-guide/ch013_node-bootstrapping.xml352(link) +msgid "AIDE" +msgstr "" + +#: ./doc/security-guide/ch013_node-bootstrapping.xml355(para) +msgid "" +"Network intrusion detection tools complement the host-based tools. OpenStack" +" doesn't have a specific network IDS built-in, but OpenStack's networking " +"component, Neutron, provides a plugin mechanism to enable different " +"technologies via the Neutron API. This plugin architecture will allow " +"tenants to develop API extensions to insert and configure their own advanced" +" networking services like a firewall, an intrusion detection system, or a " +"VPN between the VMs." +msgstr "" + +#: ./doc/security-guide/ch013_node-bootstrapping.xml363(para) +msgid "" +"Similar to host-based tools, the selection and configuration of a network-" +"based intrusion detection tool is deployment specific. Snort is the leading open source " +"networking intrusion detection tool, and a good starting place to learn " +"more." +msgstr "" + +#: ./doc/security-guide/ch013_node-bootstrapping.xml369(para) +msgid "" +"There are a few important security considerations for network and host-based" +" intrusion detection systems." +msgstr "" + +#: ./doc/security-guide/ch013_node-bootstrapping.xml373(para) +msgid "" +"It is important to consider the placement of the Network IDS on the cloud " +"(for example, adding it to the network boundary and/or around sensitive " +"networks). The placement depends on your network environment but make sure " +"to monitor the impact the IDS may have on your services depending on where " +"you choose to add it. Encrypted traffic, such as SSL, cannot generally be " +"inspected for content by a Network IDS. However, the Network IDS may still " +"provide some benefit in identifying anomalous unencrypted traffic on the " +"network." +msgstr "" + +#: ./doc/security-guide/ch013_node-bootstrapping.xml385(para) +msgid "" +"In some deployments it may be required to add host-based IDS on sensitive " +"components on security domain bridges.  A host-based IDS may detect " +"anomalous activity by compromised or unauthorized processes on the " +"component. The IDS should transmit alert and log information on the " +"Management network." +msgstr "" + +#: ./doc/security-guide/ch038_transport-security.xml3(title) +msgid "Messaging Security" +msgstr "" + +#: ./doc/security-guide/ch038_transport-security.xml4(para) +msgid "" +"This chapter discusses security hardening approaches for the three most " +"common message queuing solutions use in OpenStack: RabbitMQ, Qpid, and " +"ZeroMQ." +msgstr "" + +#: ./doc/security-guide/ch038_transport-security.xml6(title) +msgid "Messaging Transport Security" +msgstr "" + +#: ./doc/security-guide/ch038_transport-security.xml7(para) +msgid "" +"AMQP based solutions (Qpid and RabbitMQ) support transport-level security " +"using SSL. ZeroMQ messaging does not natively support SSL, but transport-" +"level security is possible using labelled IPSec or CIPSO network labels." +msgstr "" + +#: ./doc/security-guide/ch038_transport-security.xml8(para) +msgid "" +"We highly recommend enabling transport-level cryptography for your message " +"queue. Using SSL for the messaging client connections provides protection of" +" the communications from tampering and eavesdropping in-transit to the " +"messaging server. Below is guidance on how SSL is typically configured for " +"the two popular messaging servers Qpid and RabbitMQ. When configuring the " +"trusted certificate authority (CA) bundle that your messaging server uses to" +" verify client connections, it is recommended that this be limited to only " +"the CA used for your nodes, preferably an internally managed CA. The bundle " +"of trusted CAs will determine which client certificates will be authorized " +"and pass the client-server verification step of the setting up the SSL " +"connection. Note, when installing the certificate and key files, ensure that" +" the file permissions are restricted, for example chmod 0600, and the " +"ownership is restricted to the messaging server daemon user to prevent " +"unauthorized access by other processes and users on the messaging server." +msgstr "" + +#: ./doc/security-guide/ch038_transport-security.xml10(title) +msgid "RabbitMQ Server SSL Configuration" +msgstr "" + +#: ./doc/security-guide/ch038_transport-security.xml11(para) +msgid "" +"The following lines should be added to the system-wide RabbitMQ " +"configuration file, typically /etc/rabbitmq/rabbitmq.config:" +msgstr "" + +#: ./doc/security-guide/ch038_transport-security.xml24(para) +msgid "" +"Note, the 'tcp_listeners' option is set to '[]' to prevent it from listening" +" an on non-SSL port. 'ssl_listeners' option should be restricted to only " +"listen on the management network for the services." +msgstr "" + +#: ./doc/security-guide/ch038_transport-security.xml25(para) +msgid "For more information on RabbitMQ SSL configuration see:" +msgstr "" + +#: ./doc/security-guide/ch038_transport-security.xml27(link) +msgid "RabbitMQ Configuration" +msgstr "" + +#: ./doc/security-guide/ch038_transport-security.xml30(link) +msgid "RabbitMQ SSL" +msgstr "" + +#: ./doc/security-guide/ch038_transport-security.xml35(title) +msgid "Qpid Server SSL Configuration" +msgstr "" + +#: ./doc/security-guide/ch038_transport-security.xml36(para) +msgid "The Apache Foundation has a messaging security guide for Qpid. See:" +msgstr "" + +#: ./doc/security-guide/ch038_transport-security.xml38(link) +msgid "Apache Qpid SSL" +msgstr "" + +#: ./doc/security-guide/ch038_transport-security.xml44(title) +msgid "Queue Authentication and Access Control" +msgstr "" + +#: ./doc/security-guide/ch038_transport-security.xml45(para) +msgid "" +"RabbitMQ and Qpid offer authentication and access control mechanisms for " +"controlling access to queues. ZeroMQ offers no such mechanisms." +msgstr "" + +#: ./doc/security-guide/ch038_transport-security.xml46(para) +msgid "" +"Simple Authentication and Security Layer (SASL) is a framework for " +"authentication and data security in Internet protocols. Both RabbitMQ and " +"Qpid offer SASL and other pluggable authentication mechanisms beyond simple " +"usernames and passwords that allow for increased authentication security. " +"While RabbitMQ supports SASL, support in OpenStack does not currently allow " +"for requesting a specific SASL authentication mechanism. RabbitMQ support in" +" OpenStack allows for either username and password authentication over an " +"unencrypted connection or username and password in conjunction with X.509 " +"client certificates to establish the secure SSL connection." +msgstr "" + +#: ./doc/security-guide/ch038_transport-security.xml47(para) +msgid "" +"We recommend configuring X.509 client certificates on all the OpenStack " +"service nodes for client connections to the messaging queue and where " +"possible (currently only Qpid) perform authentication with X.509 client " +"certificates. When using usernames and passwords, accounts should be created" +" per-service and node for finer grained auditability of access to the queue." +msgstr "" + +#: ./doc/security-guide/ch038_transport-security.xml48(para) +msgid "" +"The SSL libraries in use by these queuing servers should also be considered " +"prior to deployment. Qpid uses Mozilla's NSS library, whereas RabbitMQ uses " +"Erlang's SSL module which uses OpenSSL." +msgstr "" + +#: ./doc/security-guide/ch038_transport-security.xml50(title) +msgid "Authentication Configuration Example - RabbitMQ" +msgstr "" + +#: ./doc/security-guide/ch038_transport-security.xml51(para) +msgid "On the RabbitMQ server, delete the default 'guest' user:" +msgstr "" + +#: ./doc/security-guide/ch038_transport-security.xml54(para) +msgid "" +"On the RabbitMQ server, for each OpenStack service or node that communicates" +" with the message queue set up user accounts and privileges:" +msgstr "" + +#: ./doc/security-guide/ch038_transport-security.xml58(para) +msgid "For additional configuration information see:" +msgstr "" + +#: ./doc/security-guide/ch038_transport-security.xml60(link) +msgid "RabbitMQ Access Control" +msgstr "" + +#: ./doc/security-guide/ch038_transport-security.xml63(link) +msgid "RabbitMQ Authentication" +msgstr "" + +#: ./doc/security-guide/ch038_transport-security.xml66(link) +msgid "RabbitMQ Plugins" +msgstr "" + +#: ./doc/security-guide/ch038_transport-security.xml69(link) +msgid "RabbitMQ SASL External Auth" +msgstr "" + +#: ./doc/security-guide/ch038_transport-security.xml74(title) +msgid "OpenStack Service Configuration - RabbitMQ" +msgstr "" + +#: ./doc/security-guide/ch038_transport-security.xml86(para) +msgid "" +"NOTE: A bug exists in the current version of OpenStack Grizzly where if " +"'kombu_ssl_version' is currently specified in the configuration file for any" +" of the OpenStack services it will cause the following python traceback " +"error: 'TypeError: an integer is required'. The current workaround is to " +"remove 'kombu_ssl_version' from the configuration file. Refer to bug report " +"1195431 for current status." +msgstr "" + +#: ./doc/security-guide/ch038_transport-security.xml89(title) +msgid "Authentication Configuration Example - Qpid" +msgstr "" + +#: ./doc/security-guide/ch038_transport-security.xml90(para) +msgid "For configuration information see:" +msgstr "" + +#: ./doc/security-guide/ch038_transport-security.xml92(link) +msgid "Apache Qpid Authentication" +msgstr "" + +#: ./doc/security-guide/ch038_transport-security.xml95(link) +msgid "Apache Qpid Authorization" +msgstr "" + +#: ./doc/security-guide/ch038_transport-security.xml100(title) +msgid "OpenStack Service Configuration - Qpid" +msgstr "" + +#: ./doc/security-guide/ch038_transport-security.xml109(para) +msgid "" +"Optionally, if using SASL with Qpid specify the SASL mechanisms in use by " +"adding:" +msgstr "" + +#: ./doc/security-guide/ch038_transport-security.xml115(title) +msgid "Message Queue Process Isolation & Policy" +msgstr "" + +#: ./doc/security-guide/ch038_transport-security.xml116(para) +msgid "" +"Each project provides a number of services which send and consume messages. " +"Each binary which sends a message is expected to consume messages, if only " +"replies, from the queue." +msgstr "" + +#: ./doc/security-guide/ch038_transport-security.xml117(para) +msgid "" +"Message queue service processes should be isolated from each other and other" +" processes on a machine." +msgstr "" + +#: ./doc/security-guide/ch038_transport-security.xml120(para) +msgid "" +"Network namespaces are highly recommended for all services running on " +"OpenStack Compute Hypervisors. This will help prevent against the bridging " +"of network traffic between VM guests and the management network." +msgstr "" + +#: ./doc/security-guide/ch038_transport-security.xml121(para) +msgid "" +"When using ZeroMQ messaging, each host must run at least one ZeroMQ message " +"receiver to receive messages from the network and forward messages to local " +"processes via IPC. It is possible and advisable to run an independent " +"message receiver per project within an IPC namespace, along with other " +"services within the same project." +msgstr "" + +#: ./doc/security-guide/ch038_transport-security.xml125(para) +msgid "" +"Queue servers should only accept connections from the management network. " +"This applies to all implementations. This should be implemented through " +"configuration of services and optionally enforced through global network " +"policy." +msgstr "" + +#: ./doc/security-guide/ch038_transport-security.xml126(para) +msgid "" +"When using ZeroMQ messaging, each project should run a separate ZeroMQ " +"receiver process on a port dedicated to services belonging to that project. " +"This is equivalent to the AMQP concept of control exchanges." +msgstr "" + +#: ./doc/security-guide/ch038_transport-security.xml130(para) +msgid "" +"The configuration for these processes should be restricted to those " +"processes, not only by Directory Access Controls, but through Mandatory " +"Access Controls. The goal of such restrictions is to prevent isolation from " +"other processes running on the same machine(s)." +msgstr "" + +#: ./doc/security-guide/ch044_case-studies-database.xml3(title) +msgid "Case Studies: Database" +msgstr "" + +#: ./doc/security-guide/ch044_case-studies-database.xml4(para) +msgid "" +"In this case study we discuss how Alice and Bob would address database " +"selection and configuration for their respective private and public clouds." +msgstr "" + +#: ./doc/security-guide/ch044_case-studies-database.xml7(para) +msgid "" +"Alice's organization has high availability concerns, so she has elected to " +"use MySQL for the database. She further places the database on the " +"Management network and uses SSL with mutual authentication among the " +"services to ensure secure access. Given there will be no external access of " +"the database, she uses certificates signed with the organization's self-" +"signed root certificate on the database and its access endpoints. Alice " +"creates separate user accounts for each database user, and configures the " +"database to use both passwords and X.509 certificates for authentication. " +"She elects not to use the nova-" +"conductor sub-service due to the desire for fine-grained access" +" control policies and audit support." +msgstr "" + +#: ./doc/security-guide/ch044_case-studies-database.xml11(para) +msgid "" +"Bob is concerned about strong separation of his tenants' data, so he has " +"elected to use the Postgres database , known for its stronger security " +"features.  The database resides on the Management network and uses SSL with " +"mutual authentication with the services. Since the database is on the " +"Management network, the database uses certificates signed with the company's" +" self-signed root certificate. Bob creates separate user accounts for each " +"database user, and configures the database to use both passwords and X.509 " +"certificates for authentication. He elects not to use the nova-conductor sub-service due to a desire " +"for fine-grained access control." +msgstr "" + +#. When image changes, this message will be marked fuzzy or untranslated for +#. you. +#. It doesn't matter what you translate it to: it's not used at all. +#: ./doc/security-guide/ch001_acknowledgements.xml8(None) +#: ./doc/security-guide/ch001_acknowledgements.xml11(None) +msgid "" +"@@image: 'static/book-sprint-all-logos.png'; " +"md5=f2d97c3130c32f31412f5af41ad72d39" +msgstr "" + +#: ./doc/security-guide/ch001_acknowledgements.xml3(title) +msgid "Acknowledgments" +msgstr "" + +#: ./doc/security-guide/ch001_acknowledgements.xml4(para) +msgid "" +"The OpenStack Security Group would like to acknowledge contributions from " +"the following organizations who were instrumental in making this book " +"possible. These are:" +msgstr "" + +#. When image changes, this message will be marked fuzzy or untranslated for +#. you. +#. It doesn't matter what you translate it to: it's not used at all. +#: ./doc/security-guide/ch033_securing-neutron-services.xml24(None) +#: ./doc/security-guide/ch033_securing-neutron-services.xml27(None) +msgid "" +"@@image: 'static/1aa-logical-neutron-flow.png'; " +"md5=63bd2e81863b9b381adb1c6951517498" +msgstr "" + +#: ./doc/security-guide/ch033_securing-neutron-services.xml3(title) +msgid "Securing OpenStack Networking Services" +msgstr "" + +#: ./doc/security-guide/ch033_securing-neutron-services.xml4(para) +msgid "" +"In order to secure OpenStack Networking, an understanding of the workflow " +"process for tenant instance creation needs to be mapped to security domains." +" " +msgstr "" + +#: ./doc/security-guide/ch033_securing-neutron-services.xml5(para) +msgid "" +"There are four main services that interact with OpenStack Networking. In a " +"typical OpenStack deployment these services map to the following security " +"domains:" +msgstr "" + +#: ./doc/security-guide/ch033_securing-neutron-services.xml7(para) +msgid "OpenStack Dashboard: Public and Management" +msgstr "" + +#: ./doc/security-guide/ch033_securing-neutron-services.xml10(para) +msgid "OpenStack Identity: Management" +msgstr "" + +#: ./doc/security-guide/ch033_securing-neutron-services.xml13(para) +msgid "OpenStack Compute Node: Management and Guest" +msgstr "" + +#: ./doc/security-guide/ch033_securing-neutron-services.xml16(para) +msgid "" +"OpenStack Network Node: Management, Guest, and possibly Public depending " +"upon neutron-plugin in use." +msgstr "" + +#: ./doc/security-guide/ch033_securing-neutron-services.xml19(para) +msgid "" +"SDN Services Node: Management, Guest and possibly Public depending upon " +"product used." +msgstr "" + +#: ./doc/security-guide/ch033_securing-neutron-services.xml30(para) +msgid "" +"In order to isolate sensitive data communication between the OpenStack " +"Networking services and other OpenStack core services, we strongly recommend" +" that these communication channels be configured to only allow " +"communications over an isolated management network." +msgstr "" + +#: ./doc/security-guide/ch033_securing-neutron-services.xml32(title) +msgid "OpenStack Networking Service Configuration" +msgstr "" + +#: ./doc/security-guide/ch033_securing-neutron-services.xml34(title) +msgid "Restrict Bind Address of the API server: neutron-server" +msgstr "" + +#: ./doc/security-guide/ch033_securing-neutron-services.xml35(para) +msgid "" +"To restrict the interface or IP address on which the OpenStack Networking " +"API service binds a network socket for incoming client connections, specify " +"the bind_host and bind_port in the neutron.conf file as shown:" +msgstr "" + +#: ./doc/security-guide/ch033_securing-neutron-services.xml44(title) +msgid "" +"Restrict DB and RPC communication of the OpenStack Networking services:" +msgstr "" + +#: ./doc/security-guide/ch033_securing-neutron-services.xml45(para) +msgid "" +"Various components of the OpenStack Networking services use either the " +"messaging queue or database connections to communicate with other components" +" in OpenStack Networking." +msgstr "" + +#: ./doc/security-guide/ch033_securing-neutron-services.xml46(para) +msgid "" +"It is recommended that you follow the guidelines provided in the Database " +"Authentication and Access Control chapter in the Database section for all " +"components that require direct DB connections." +msgstr "" + +#: ./doc/security-guide/ch033_securing-neutron-services.xml47(para) +msgid "" +"It is recommended that you follow the guidelines provided in the Queue " +"Authentication and Access Control chapter in the Messaging section for all " +"components that require RPC communication." +msgstr "" + +#. When image changes, this message will be marked fuzzy or untranslated for +#. you. +#. It doesn't matter what you translate it to: it's not used at all. +#: ./doc/security-guide/ch004_book-introduction.xml113(None) +#: ./doc/security-guide/ch004_book-introduction.xml118(None) +msgid "" +"@@image: 'static/marketecture-diagram.png'; " +"md5=4ab13a64f80c210be3120abc5c7aee8a" +msgstr "" + +#: ./doc/security-guide/ch004_book-introduction.xml8(title) +msgid "Introduction to OpenStack" +msgstr "" + +#: ./doc/security-guide/ch004_book-introduction.xml9(para) +msgid "" +"This guide provides security insight into OpenStack deployments. The " +"intended audience is cloud architects, deployers, and administrators. In " +"addition, cloud users will find the guide both educational and helpful in " +"provider selection, while auditors will find it useful as a reference " +"document to support their compliance certification efforts. This guide is " +"also recommended for anyone interested in cloud security." +msgstr "" + +#: ./doc/security-guide/ch004_book-introduction.xml16(para) +msgid "" +"Each OpenStack deployment embraces a wide variety of technologies, spanning " +"Linux distributions, database systems, messaging queues, OpenStack " +"components themselves, access control policies, logging services, security " +"monitoring tools, and much more. It should come as no surprise that the " +"security issues involved are equally diverse, and their in-depth analysis " +"would require several guides. We strive to find a balance, providing enough " +"context to understand OpenStack security issues and their handling, and " +"provide external references for further information. The guide could be read" +" from start to finish or sampled as necessary like a reference." +msgstr "" + +#: ./doc/security-guide/ch004_book-introduction.xml27(para) +msgid "" +"We briefly introduce the kinds of clouds: private, public, and hybrid before" +" presenting an overview of the OpenStack components and their related " +"security concerns in the remainder of the chapter." +msgstr "" + +#: ./doc/security-guide/ch004_book-introduction.xml32(title) +msgid "Cloud types" +msgstr "" + +#: ./doc/security-guide/ch004_book-introduction.xml33(para) +msgid "" +"OpenStack is a key enabler in adoption of cloud technology and has several " +"common deployment use cases. These are commonly known as Public, Private, " +"and Hybrid models. The following sections use the National Institute of " +"Standards and Technology (NIST) definition" +" of cloud to introduce these different types of cloud as they apply " +"to OpenStack." +msgstr "" + +#: ./doc/security-guide/ch004_book-introduction.xml42(title) +msgid "Public cloud" +msgstr "" + +#: ./doc/security-guide/ch004_book-introduction.xml43(para) +msgid "" +"According to NIST, a public cloud is one in which the infrastructure is open" +" to the general public for consumption. OpenStack public clouds are " +"typically run by a service provider and can be consumed by individuals, " +"corporations, or any paying customer. A public cloud provider may expose a " +"full set of features such as software defined networking, block storage, in " +"addition to multiple instance types. Due to the nature of public clouds, " +"they are exposed to a higher degree of risk. As a consumer of a public cloud" +" you should validate that your selected provider has the necessary " +"certifications, attestations, and other regulatory considerations. As a " +"public cloud provider, depending on your target customers, you may be " +"subject to one or more regulations. Additionally, even if not required to " +"meet regulatory requirements, a provider should ensure tenant isolation as " +"well as protecting management infrastructure from external attacks." +msgstr "" + +#: ./doc/security-guide/ch004_book-introduction.xml61(title) +msgid "Private cloud" +msgstr "" + +#: ./doc/security-guide/ch004_book-introduction.xml62(para) +msgid "" +"At the opposite end of the spectrum is the private cloud. As NIST defines " +"it, a private cloud is provisioned for exclusive use by a single " +"organization comprising multiple consumers, such as business units. It may " +"be owned, managed, and operated by the organization, a third-party, or some " +"combination of them, and it may exist on or off premises. Private cloud use " +"cases are diverse, as such, their individual security concerns vary." +msgstr "" + +#: ./doc/security-guide/ch004_book-introduction.xml72(title) +msgid "Community cloud" +msgstr "" + +#: ./doc/security-guide/ch004_book-introduction.xml73(para) +msgid "" +"NIST defines a community cloud as one whose  infrastructure is provisioned " +"for the exclusive use by a specific community of consumers from " +"organizations that have shared concerns. For example, mission, security " +"requirements, policy, and compliance considerations. It may be owned, " +"managed, and operated by one or more of the organizations in the community, " +"a third-party, or some combination of them, and it may exist on or off " +"premises." +msgstr "" + +#: ./doc/security-guide/ch004_book-introduction.xml83(title) +msgid "Hybrid cloud" +msgstr "" + +#: ./doc/security-guide/ch004_book-introduction.xml84(para) +msgid "" +"A hybrid cloud is defined by NIST as a composition of two or more distinct " +"cloud infrastructures, such as private, community, or public, that remain " +"unique entities, but are bound together by standardized or proprietary " +"technology that enables data and application portability, such as cloud " +"bursting for load balancing between clouds. For example an online retailer " +"may have their advertising and catalogue presented on a public cloud that " +"allows for elastic provisioning. This would enable them to handle seasonal " +"loads in a flexible, cost-effective fashion. Once a customer begins to " +"process their order, they are transferred to the more secure private cloud " +"backend that is PCI compliant." +msgstr "" + +#: ./doc/security-guide/ch004_book-introduction.xml96(para) +msgid "" +"For the purposes of this document, we treat Community and Hybrid similarly, " +"dealing explicitly only with the extremes of Public and Private clouds from " +"a security perspective. Your security measures depend where your deployment " +"falls upon the private public continuum." +msgstr "" + +#: ./doc/security-guide/ch004_book-introduction.xml104(title) +msgid "OpenStack service overview" +msgstr "" + +#: ./doc/security-guide/ch004_book-introduction.xml105(para) +msgid "" +"OpenStack embraces a modular architecture to provide a set of core services " +"that facilitates scalability and elasticity as core design tenets. This " +"chapter briefly reviews OpenStack components, their use cases and security " +"considerations." +msgstr "" + +#: ./doc/security-guide/ch004_book-introduction.xml123(para) +msgid "" +"OpenStack Compute Service (Nova) provides services to support the management" +" of virtual machine instances at scale, instances that host multi-tiered " +"applications, dev/test environments, \"Big Data\" crunching Hadoop clusters," +" and/or high performance computing." +msgstr "" + +#: ./doc/security-guide/ch004_book-introduction.xml128(para) +msgid "" +"The Compute Service facilitates this management through an abstraction layer" +" that interfaces with supported hypervisors, which we address later on in " +"more detail." +msgstr "" + +#: ./doc/security-guide/ch004_book-introduction.xml131(para) +msgid "" +"Later in the guide, we focus generically on the virtualization stack as it " +"relates to hypervisors." +msgstr "" + +#: ./doc/security-guide/ch004_book-introduction.xml133(para) +msgid "" +"For information about the current state of feature support, see OpenStack " +"Hypervisor Support Matrix." +msgstr "" + +#: ./doc/security-guide/ch004_book-introduction.xml137(para) +msgid "" +"The security of Compute is critical for an OpenStack deployment. Hardening " +"techniques should include support for strong instance isolation, secure " +"communication between Compute sub-components, and resiliency of public-" +"facing API endpoints." +msgstr "" + +#: ./doc/security-guide/ch004_book-introduction.xml144(title) +#: ./doc/security-guide/ch027_storage.xml8(title) +msgid "Object Storage" +msgstr "" + +#: ./doc/security-guide/ch004_book-introduction.xml145(para) +msgid "" +"The OpenStack Object Storage Service (Swift) provides support for storing " +"and retrieving arbitrary data in the cloud. The Object Storage Service " +"provides both a native API and an Amazon Web Services S3 compatible API. The" +" service provides a high degree of resiliency through data replication and " +"can handle petabytes of data." +msgstr "" + +#: ./doc/security-guide/ch004_book-introduction.xml151(para) +msgid "" +"It is important to understand that object storage differs from traditional " +"file system storage. It is best used for static data such as media files " +"(MP3s, images, videos), virtual machine images, and backup files." +msgstr "" + +#: ./doc/security-guide/ch004_book-introduction.xml155(para) +msgid "" +"Object security should focus on access control and encryption of data in " +"transit and at rest. Other concerns may relate to system abuse, illegal or " +"malicious content storage, and cross authentication attack vectors." +msgstr "" + +#: ./doc/security-guide/ch004_book-introduction.xml161(title) +msgid "Block Storage" +msgstr "" + +#: ./doc/security-guide/ch004_book-introduction.xml162(para) +msgid "" +"The OpenStack Block Storage service (Cinder) provides persistent block " +"storage for compute instances. The Block Storage Service is responsible for " +"managing the life-cycle of block devices, from the creation and attachment " +"of volumes to instances, to their release." +msgstr "" + +#: ./doc/security-guide/ch004_book-introduction.xml167(para) +msgid "" +"Security considerations for block storage are similar to that of object " +"storage." +msgstr "" + +#: ./doc/security-guide/ch004_book-introduction.xml171(title) +msgid "OpenStack Networking" +msgstr "" + +#: ./doc/security-guide/ch004_book-introduction.xml172(para) +msgid "" +"The OpenStack Networking Service (Neutron, previously called Quantum) " +"provides various networking services to cloud users (tenants) such as IP " +"address management, DNS, DHCP," +" load balancing, and security groups (network access rules, like firewall " +"policies). It provides a framework for software defined networking (SDN) " +"that allows for pluggable integration with various networking solutions." +msgstr "" + +#: ./doc/security-guide/ch004_book-introduction.xml180(para) +msgid "" +"OpenStack Networking allows cloud tenants to manage their guest network " +"configurations. Security concerns with the networking service include " +"network traffic isolation, availability, integrity and confidentiality." +msgstr "" + +#: ./doc/security-guide/ch004_book-introduction.xml187(para) +msgid "" +"The OpenStack Dashboard Service (Horizon) provides a web-based interface for" +" both cloud administrators and cloud tenants. Through this interface " +"administrators and tenants can provision, manage, and monitor cloud " +"resources. Horizon is commonly deployed in a public facing manner with all " +"the usual security concerns of public web portals." +msgstr "" + +#: ./doc/security-guide/ch004_book-introduction.xml195(title) +msgid "Identity Service" +msgstr "" + +#: ./doc/security-guide/ch004_book-introduction.xml196(para) +msgid "" +"The OpenStack Identity Service (Keystone) is a shared service that provides authentication and " +"authorization services throughout the entire cloud infrastructure. The " +"Identity Service has pluggable support for multiple forms of authentication." +msgstr "" + +#: ./doc/security-guide/ch004_book-introduction.xml201(para) +msgid "" +"Security concerns here pertain to trust in authentication, management of " +"authorization tokens, and secure communication." +msgstr "" + +#: ./doc/security-guide/ch004_book-introduction.xml206(title) +msgid "Image Service" +msgstr "" + +#: ./doc/security-guide/ch004_book-introduction.xml207(para) +msgid "" +"The OpenStack Image Service (Glance) provides disk image management " +"services. The Image Service provides image discovery, registration, and " +"delivery services to Compute, the compute service, as needed." +msgstr "" + +#: ./doc/security-guide/ch004_book-introduction.xml211(para) +msgid "" +"Trusted processes for managing the life cycle of disk images are required, " +"as are all the previously mentioned issues with respect to data security." +msgstr "" + +#: ./doc/security-guide/ch004_book-introduction.xml216(title) +msgid "Other supporting technology" +msgstr "" + +#: ./doc/security-guide/ch004_book-introduction.xml217(para) +msgid "" +"OpenStack relies on messaging for internal communication between several of " +"its services. By default, OpenStack uses message queues based on the " +"Advanced Message Queue Protocol (AMQP). Similar to " +"most OpenStack services, it supports pluggable components. Today the " +"implementation backend could be RabbitMQ, " +"Qpid, or ZeroMQ." +msgstr "" + +#: ./doc/security-guide/ch004_book-introduction.xml226(para) +msgid "" +"As most management commands flow through the message queueing system, it is " +"a primary security concern for any OpenStack deployment. Message queueing " +"security is discussed in detail later in this guide." +msgstr "" + +#: ./doc/security-guide/ch004_book-introduction.xml230(para) +msgid "" +"Several of the components use databases though it is not explicitly called " +"out. Securing the access to the databases and their contents is yet another " +"security concern, and consequently discussed in more detail later in this " +"guide." +msgstr "" + +#: ./doc/security-guide/ch063_compliance-activities.xml3(title) +msgid "Compliance Activities" +msgstr "" + +#: ./doc/security-guide/ch063_compliance-activities.xml4(para) +msgid "" +"There are a number of standard activities that will greatly assist with the " +"compliance process. In this chapter we outline some of the most common " +"compliance activities. These are not specific to OpenStack, however we " +"provide references to relevant sections in this book as useful context." +msgstr "" + +#: ./doc/security-guide/ch063_compliance-activities.xml6(title) +msgid "Information Security Management System (ISMS)" +msgstr "" + +#: ./doc/security-guide/ch063_compliance-activities.xml7(para) +msgid "" +"An Information Security Management System (ISMS) is a comprehensive set of " +"policies and processes that an organization creates and maintains to manage " +"risk to information assets. The most common ISMS for cloud deployments is " +"ISO/IEC 27001/2, " +"which creates a solid foundation of security controls and practices for " +"achieving more stringent compliance certifications." +msgstr "" + +#: ./doc/security-guide/ch063_compliance-activities.xml10(title) +msgid "Risk Assessment" +msgstr "" + +#: ./doc/security-guide/ch063_compliance-activities.xml11(para) +msgid "" +"A Risk Assessment framework identifies risks within an organization or " +"service, and specifies ownership of these risks, along with implementation " +"and mitigation strategies. Risks apply to all areas of the service, from " +"technical controls to environmental disaster scenarios and human elements, " +"for example a malicious insider (or rogue employee). Risks can be rated " +"using a variety of mechanisms, for example likelihood vs impact. An " +"OpenStack deployment risk assessment can include control gaps that are " +"described in this book." +msgstr "" + +#: ./doc/security-guide/ch063_compliance-activities.xml14(title) +msgid "Access & Log Reviews" +msgstr "" + +#: ./doc/security-guide/ch063_compliance-activities.xml15(para) +msgid "" +"Periodic access and log reviews are required to ensure authentication, " +"authorization, and accountability in a service deployment. Specific guidance" +" for OpenStack on these topics are discussed in-depth in the logging " +"section." +msgstr "" + +#: ./doc/security-guide/ch063_compliance-activities.xml18(title) +msgid "Backup and Disaster Recovery" +msgstr "" + +#: ./doc/security-guide/ch063_compliance-activities.xml19(para) +msgid "" +"Disaster Recovery (DR) and Business Continuity Planning (BCP) plans are " +"common requirements for ISMS and compliance activities. These plans must be " +"periodically tested as well as documented. In OpenStack key areas are found " +"in the management security domain, and anywhere that single points of " +"failure (SPOFs) can be identified. See the section on secure backup and " +"recovery for additional details." +msgstr "" + +#: ./doc/security-guide/ch063_compliance-activities.xml22(title) +msgid "Security Training" +msgstr "" + +#: ./doc/security-guide/ch063_compliance-activities.xml23(para) +msgid "" +"Annual, role-specific, security training is a mandatory requirement for " +"almost all compliance certifications and attestations. To optimise the " +"effectiveness of security training, a common method is to provide role " +"specific training, for example to developers, operational personnel, and " +"non-technical employees. Additional cloud security or OpenStack security " +"training based on this hardening guide would be ideal." +msgstr "" + +#: ./doc/security-guide/ch063_compliance-activities.xml26(title) +msgid "Security Reviews" +msgstr "" + +#: ./doc/security-guide/ch063_compliance-activities.xml27(para) +msgid "" +"As OpenStack is a popular open source project, much of the codebase and " +"architecture has been scrutinized by individual contributors, organizations " +"and enterprises. This can be advantageous from a security perspective, " +"however the need for security reviews is still a critical consideration for " +"service providers, as deployments vary, and security is not always the " +"primary concern for contributors. A comprehensive security review process " +"may include architectural review, threat modelling, source code analysis and" +" penetration testing. There are many techniques and recommendations for " +"conducting security reviews that can be found publicly posted. A well-tested" +" example is the Microsoft" +" SDL, created as part of the Microsoft Trustworthy Computing " +"Initiative." +msgstr "" + +#: ./doc/security-guide/ch063_compliance-activities.xml44(para) +msgid "" +"Security updates are critical to any IaaS deployment, whether private or " +"public. Vulnerable systems expand attack surfaces, and are obvious targets " +"for attackers. Common scanning technologies and vulnerability notification " +"services can help mitigate this threat. It is important that scans are " +"authenticated and that mitigation strategies extend beyond simple perimeter " +"hardening. Multi-tenant architectures such as OpenStack are particularly " +"prone to hypervisor vulnerabilities, making this a critical part of the " +"system for vulnerability management. See the section on instance isolation " +"for additional details." +msgstr "" + +#: ./doc/security-guide/ch063_compliance-activities.xml47(title) +msgid "Data Classification" +msgstr "" + +#: ./doc/security-guide/ch063_compliance-activities.xml48(para) +msgid "" +"Data Classification defines a method for classifying and handling " +"information, often to protect customer information from accidental or " +"deliberate theft, loss, or inappropriate disclosure. Most commonly this " +"involves classifying information as sensitive or non-sensitive, or as " +"personally identifiable information (PII). Depending on the context of the " +"deployment various other classifying criteria may be used (government, " +"health-care etc). The underlying principle is that data classifications are " +"clearly defined and in-use. The most common protective mechanisms include " +"industry standard encryption technologies. See the data security section for" +" additional details." +msgstr "" + +#: ./doc/security-guide/ch063_compliance-activities.xml51(title) +msgid "Exception Process" +msgstr "" + +#: ./doc/security-guide/ch063_compliance-activities.xml52(para) +msgid "" +"An exception process is an important component of an ISMS. When certain " +"actions are not compliant with security policies that an organization has " +"defined, they must be logged. Appropriate justification, description and " +"mitigation details need to be included, and signed off by appropriate " +"authorities. OpenStack default configurations may vary in meeting various " +"compliance criteria, areas that fail to meet compliance requirements should " +"be logged, with potential fixes considered for contribution to the " +"community." +msgstr "" + +#. When image changes, this message will be marked fuzzy or untranslated for +#. you. +#. It doesn't matter what you translate it to: it's not used at all. +#: ./doc/security-guide/ch027_storage.xml53(None) +msgid "" +"@@image: 'static/swift_network_diagram-1.png'; " +"md5=83c094bb051cbe5e6161d3f7442f6136" +msgstr "" + +#. When image changes, this message will be marked fuzzy or untranslated for +#. you. +#. It doesn't matter what you translate it to: it's not used at all. +#: ./doc/security-guide/ch027_storage.xml108(None) +#: ./doc/security-guide/ch027_storage.xml113(None) +msgid "" +"@@image: 'static/swift_network_diagram-2.png'; " +"md5=69f8effe3f5d0f3cbccfb8c5a5dd299e" +msgstr "" + +#: ./doc/security-guide/ch027_storage.xml9(para) +msgid "" +"OpenStack Object Storage (Swift) is a service that provides storage and " +"retrieval of data over HTTP. Objects (blobs of data) are stored in an " +"organizational hierarchy that offers anonymous read-only access or ACL " +"defined access based on the authentication mechanism." +msgstr "" + +#: ./doc/security-guide/ch027_storage.xml14(para) +msgid "" +"A consumer can store objects, modify them, or access them using the HTTP " +"protocol and REST APIs. Backend components of Object Storage use different " +"protocols for keeping the information synchronized in a redundant cluster of" +" services. For more details on the API and the backend components see the " +"OpenStack Storage documentation." +msgstr "" + +#: ./doc/security-guide/ch027_storage.xml22(para) +msgid "" +"For this document the components will be grouped into the following primary " +"groups:" +msgstr "" + +#: ./doc/security-guide/ch027_storage.xml26(para) +msgid "Proxy services" +msgstr "" + +#: ./doc/security-guide/ch027_storage.xml29(para) +msgid "Auth services" +msgstr "" + +#: ./doc/security-guide/ch027_storage.xml32(para) +msgid "Storage services" +msgstr "" + +#: ./doc/security-guide/ch027_storage.xml35(para) +#: ./doc/security-guide/ch027_storage.xml159(td) +msgid "Account service" +msgstr "" + +#: ./doc/security-guide/ch027_storage.xml38(para) +#: ./doc/security-guide/ch027_storage.xml164(td) +msgid "Container service" +msgstr "" + +#: ./doc/security-guide/ch027_storage.xml41(para) +#: ./doc/security-guide/ch027_storage.xml169(td) +msgid "Object service" +msgstr "" + +#: ./doc/security-guide/ch027_storage.xml47(title) +msgid "" +"An example diagram from the OpenStack Object Storage Administration Guide " +"(2013)" +msgstr "" + +#: ./doc/security-guide/ch027_storage.xml58(para) +msgid "" +"An Object Storage environment does not have to necessarily be on the " +"Internet and could also be a private cloud with the \"Public Switch\" being " +"part of the organization's internal network infrastructure." +msgstr "" + +#: ./doc/security-guide/ch027_storage.xml64(title) +msgid "First thing to secure – the network" +msgstr "" + +#: ./doc/security-guide/ch027_storage.xml65(para) +msgid "" +"The first aspect of a secure architecture design for Object Storage is in " +"the networking component. The Storage service nodes use rsync between each " +"other for copying data to provide replication and high availability. In " +"addition, the proxy service communicates with the Storage service when " +"relaying data back and forth between the end-point client and the cloud " +"environment." +msgstr "" + +#: ./doc/security-guide/ch027_storage.xml73(para) +msgid "" +"None of these use any type of encryption or authentication at this " +"layer/tier." +msgstr "" + +#: ./doc/security-guide/ch027_storage.xml76(para) +msgid "" +"This is why you see a \"Private Switch\" or private network ([V]LAN) in " +"architecture diagrams. This data domain should be separate from other " +"OpenStack data networks as well. For further discussion on security domains " +"please see ." +msgstr "" + +#: ./doc/security-guide/ch027_storage.xml83(para) +msgid "" +"Rule: Use a private (V)LAN network segment for your " +"Storage services in the data domain." +msgstr "" + +#: ./doc/security-guide/ch027_storage.xml87(para) +msgid "" +"This necessitates that the Proxy service nodes have dual interfaces " +"(physical or virtual):" +msgstr "" + +#: ./doc/security-guide/ch027_storage.xml91(para) +msgid "One as a \"public\" interface for consumers to reach" +msgstr "" + +#: ./doc/security-guide/ch027_storage.xml95(para) +msgid "Another as a \"private\" interface with access to the storage nodes" +msgstr "" + +#: ./doc/security-guide/ch027_storage.xml99(para) +msgid "The following figure demonstrates one possible network architecture." +msgstr "" + +#: ./doc/security-guide/ch027_storage.xml102(title) +msgid "Object storage network architecture with a management node (OSAM)" +msgstr "" + +#: ./doc/security-guide/ch027_storage.xml120(title) +msgid "Securing services – general" +msgstr "" + +#: ./doc/security-guide/ch027_storage.xml122(title) +msgid "Service runas user" +msgstr "" + +#: ./doc/security-guide/ch027_storage.xml123(para) +msgid "" +"It is recommended that you configure each service to run under a non-root " +"(UID 0) service account. One recommendation is the username \"swift\" with " +"primary group \"swift.\"" +msgstr "" + +#: ./doc/security-guide/ch027_storage.xml129(title) +msgid "File permissions" +msgstr "" + +#: ./doc/security-guide/ch027_storage.xml130(para) +msgid "" +"/etc/swift contains information about the ring topology and environment " +"configuration. The following permissions are recommended:" +msgstr "" + +#: ./doc/security-guide/ch027_storage.xml138(para) +msgid "" +"This restricts only root to be able to modify configuration files while " +"allowing the services to read them via their group membership in \"swift.\"" +msgstr "" + +#: ./doc/security-guide/ch027_storage.xml146(title) +msgid "Securing storage services" +msgstr "" + +#: ./doc/security-guide/ch027_storage.xml147(para) +msgid "" +"The following are the default listening ports for the various storage " +"services:" +msgstr "" + +#: ./doc/security-guide/ch027_storage.xml152(td) +msgid "Service Name" +msgstr "" + +#: ./doc/security-guide/ch027_storage.xml153(td) +msgid "Port" +msgstr "" + +#: ./doc/security-guide/ch027_storage.xml154(td) +msgid "Type" +msgstr "" + +#: ./doc/security-guide/ch027_storage.xml160(td) +msgid "6002" +msgstr "" + +#: ./doc/security-guide/ch027_storage.xml161(td) +#: ./doc/security-guide/ch027_storage.xml166(td) +#: ./doc/security-guide/ch027_storage.xml171(td) +#: ./doc/security-guide/ch027_storage.xml176(td) +msgid "TCP" +msgstr "" + +#: ./doc/security-guide/ch027_storage.xml165(td) +msgid "6001" +msgstr "" + +#: ./doc/security-guide/ch027_storage.xml170(td) +msgid "6000" +msgstr "" + +#: ./doc/security-guide/ch027_storage.xml174(td) +msgid "Rsync" +msgstr "" + +#: ./doc/security-guide/ch027_storage.xml175(td) +msgid "873" +msgstr "" + +#: ./doc/security-guide/ch027_storage.xml180(para) +msgid "" +"Authentication does not happen at this level in Object Storage. If someone " +"was able to connect to a Storage service node on one of these ports they " +"could access or modify data without authentication. In order to secure " +"against this issue you should follow the recommendations given previously " +"about using a private storage network." +msgstr "" + +#: ./doc/security-guide/ch027_storage.xml188(title) +msgid "Object storage \"account\" terminology" +msgstr "" + +#: ./doc/security-guide/ch027_storage.xml189(para) +msgid "" +"An Object Storage \"Account\" is not a user account or credential. The " +"following explains the relations:" +msgstr "" + +#: ./doc/security-guide/ch027_storage.xml195(td) +msgid "OpenStack Object Storage Account" +msgstr "" + +#: ./doc/security-guide/ch027_storage.xml196(td) +msgid "" +"Collection of containers; not user accounts or authentication. Which users " +"are associated with the account and how they may access it depends on the " +"authentication system used. See authentication systems later. Referred to in" +" this document as OSSAccount." +msgstr "" + +#: ./doc/security-guide/ch027_storage.xml205(td) +msgid "OpenStack Object Storage Containers" +msgstr "" + +#: ./doc/security-guide/ch027_storage.xml206(td) +msgid "" +"Collection of objects. Metadata on the container is available for ACLs. The " +"meaning of ACLs is dependent on the authentication system used." +msgstr "" + +#: ./doc/security-guide/ch027_storage.xml212(td) +msgid "OpenStack Object Storage Objects" +msgstr "" + +#: ./doc/security-guide/ch027_storage.xml213(td) +msgid "" +"The actual data objects. ACLs at the object level are also possible with " +"metadata. It is dependent on the authentication system used." +msgstr "" + +#: ./doc/security-guide/ch027_storage.xml221(para) +msgid "" +" Another way of " +"thinking about the above would be: A single shelf (Account) holds zero or " +"more -> buckets (Containers) which each hold zero or more -> objects. " +"A garage (Object Storage cloud environment) may have multiple shelves " +"(Accounts) with each shelf belonging to zero or more users." +msgstr "" + +#: ./doc/security-guide/ch027_storage.xml231(para) +msgid "" +"At each level you may have ACLs that dictate who has what type of access. " +"ACLs are interpreted based on what authentication system is in use. The two " +"most common types of authentication providers used are Keystone and SWAuth. " +"Custom authentication providers are also possible. Please see the Object " +"Storage Authentication section for more information." +msgstr "" + +#: ./doc/security-guide/ch027_storage.xml242(title) +msgid "Securing proxy services" +msgstr "" + +#: ./doc/security-guide/ch027_storage.xml243(para) +msgid "" +"A Proxy service node should have at least two interfaces (physical or " +"virtual): one public and one private. The public interface may be protected " +"via firewalls or service binding. The public facing service is an HTTP web " +"server that processes end-point client requests, authenticates them, and " +"performs the appropriate action. The private interface does not require any " +"listening services but is instead used to establish outgoing connections to " +"storage service nodes on the private storage network." +msgstr "" + +#: ./doc/security-guide/ch027_storage.xml253(title) +msgid "Use SSL/TLS" +msgstr "" + +#: ./doc/security-guide/ch027_storage.xml254(para) +msgid "" +"The built-in or included web server that comes with Swift supports SSL, but " +"it does not support transmission of the entire SSL certificate chain. This " +"causes issues when you use a third party trusted and signed certificate, " +"such as Verisign, for your cloud. The current work around is to not use the " +"built-in web server but an alternative web server instead that supports " +"sending both the public server certificate as well as the CA signing " +"authorities intermediate certificate(s). This allows for end-point clients " +"that have the CA root certificate in their trust store to be able to " +"successfully validate your cloud environment's SSL certificate and chain. An" +" example of how to do this with mod_wsgi and Apache is given below. Also " +"consult the Apache" +" Deployment Guide" +msgstr "" + +#: ./doc/security-guide/ch027_storage.xml272(para) +msgid "Modify file /etc/apache2/envvars with" +msgstr "" + +#: ./doc/security-guide/ch027_storage.xml279(para) +msgid "An alternative is to modify your Apache conf file with" +msgstr "" + +#: ./doc/security-guide/ch027_storage.xml285(para) +msgid "Create a \"swift\" directory in your Apache document root:" +msgstr "" + +#: ./doc/security-guide/ch027_storage.xml288(para) +msgid "" +"Create the file $YOUR_APACHE_DOC_ROOT/swift/proxy-" +"server.wsgi:" +msgstr "" + +#: ./doc/security-guide/ch027_storage.xml294(title) +msgid "HTTP listening port" +msgstr "" + +#: ./doc/security-guide/ch027_storage.xml295(para) +msgid "" +"You should run your Proxy service web server as a non-root (no UID 0) user " +"such as \"swift\" mentioned before. The use of a port greater than 1024 is " +"required to make this easy and avoid running any part of the web container " +"as root. Doing so is not a burden as end-point clients are not typically " +"going to type in the URL manually into a web browser to browse around in the" +" object storage. Additionally, for clients using the HTTP REST API and " +"performing authentication they will normally automatically grab the full " +"REST API URL they are to use as provided by the authentication response. " +"OpenStack’s REST API allows for a client to authenticate to one URL and then" +" be told to use a completely different URL for the actual service. Example: " +"Client authenticates to " +"https://identity.cloud.example.org:55443/v1/auth and gets a " +"response with their authentication key and Storage URL (the URL of the proxy" +" nodes or load balancer) of " +"https://swift.cloud.example.org:44443/v1/AUTH_8980." +msgstr "" + +#: ./doc/security-guide/ch027_storage.xml315(para) +msgid "" +"The method for configuring your web server to start and run as a non-root " +"user varies by web server and OS." +msgstr "" + +#: ./doc/security-guide/ch027_storage.xml320(title) +msgid "Load balancer" +msgstr "" + +#: ./doc/security-guide/ch027_storage.xml321(para) +msgid "" +"If the option of using Apache is not feasible or for performance you wish to" +" offload your SSL work you may employ a dedicated network device load " +"balancer. This is also the common way to provide redundancy and load " +"balancing when using multiple proxy nodes." +msgstr "" + +#: ./doc/security-guide/ch027_storage.xml326(para) +msgid "" +"If you choose to offload your SSL ensure that the network link between the " +"load balancer and your proxy nodes is on a private (V)LAN segment such that " +"other nodes on the network (possibly compromised) cannot wiretap (sniff) the" +" unencrypted traffic. If such a breach were to occur the attacker could gain" +" access to end-point client or cloud administrator credentials and access " +"the cloud data." +msgstr "" + +#: ./doc/security-guide/ch027_storage.xml334(para) +msgid "" +"The authentication service you use, such as Keystone or SWAuth, will " +"determine how you configure a different URL in the responses to end-clients " +"so they use your load balancer instead of an individual Proxy service node." +msgstr "" + +#: ./doc/security-guide/ch027_storage.xml343(title) +msgid "Object storage authentication" +msgstr "" + +#: ./doc/security-guide/ch027_storage.xml344(para) +msgid "" +"Object Storage uses wsgi to provide a middleware for authentication of end-" +"point clients. The authentication provider defines what roles and user types" +" exist. Some use traditional username and password credentials while others " +"may leverage API key tokens or even client-side x.509 SSL certificates. " +"Custom providers can be integrated in using the wsgi model." +msgstr "" + +#: ./doc/security-guide/ch027_storage.xml352(title) +msgid "Keystone" +msgstr "" + +#: ./doc/security-guide/ch027_storage.xml353(para) +msgid "" +"Keystone is the commonly used Identity provider in OpenStack. It may also be" +" used for authentication in Object Storage. Coverage of securing Keystone is" +" already provided in ." +msgstr "" + +#: ./doc/security-guide/ch027_storage.xml360(title) +msgid "SWAuth" +msgstr "" + +#: ./doc/security-guide/ch027_storage.xml361(para) +msgid "" +"SWAuth is another alternative to Keystone. In contrast to Keystone it stores" +" the user accounts, credentials, and metadata in object storage itself. More" +" information can be found on the SWAuth website at http://gholt.github.io/swauth/." +msgstr "" + +#: ./doc/security-guide/ch027_storage.xml371(title) +msgid "Other notable items" +msgstr "" + +#: ./doc/security-guide/ch027_storage.xml372(para) +msgid "" +"In /etc/swift/swift.conf on every service node there is a " +"\"swift_hash_path_suffix\" setting. This is provided to reduce the chance of" +" hash collisions for objects being stored and avert one user overwriting the" +" data of another user." +msgstr "" + +#: ./doc/security-guide/ch027_storage.xml377(para) +msgid "" +"This value should be initially set with a cryptographically secure random " +"number generator and consistent across all service nodes. Ensure that it is " +"protected with proper ACLs and that you have a backup copy to avoid data " +"loss." +msgstr "" + +#: ./doc/security-guide/ch006_introduction-to-case-studies.xml8(title) +msgid "Introduction to Case Studies" +msgstr "" + +#: ./doc/security-guide/ch006_introduction-to-case-studies.xml9(para) +msgid "" +"This guide refers to two running case studies, which are introduced here and" +" referred to at the end of each chapter." +msgstr "" + +#: ./doc/security-guide/ch006_introduction-to-case-studies.xml12(title) +msgid "Case Study : Alice the private cloud builder" +msgstr "" + +#: ./doc/security-guide/ch006_introduction-to-case-studies.xml13(para) +msgid "" +"Alice deploys a private cloud for use by a government department in the US. " +"The cloud must comply with relevant standards, such as FedRAMP. The security" +" paperwork requirements for this cloud are very high. It must have no direct" +" access to the internet: its API endpoints, compute instances, and other " +"resources must be exposed to only systems within the department's network, " +"which is entirely air-gapped from all other networks. The cloud can access " +"other network services on the Organization's Intranet. For example, the " +"authentication and logging services." +msgstr "" + +#: ./doc/security-guide/ch006_introduction-to-case-studies.xml25(title) +msgid "Case Study : Bob the public cloud provider" +msgstr "" + +#: ./doc/security-guide/ch006_introduction-to-case-studies.xml26(para) +msgid "" +"Bob is a lead architect for a company that deploys a large greenfield public" +" cloud. This cloud provides IaaS for the masses and enables any consumer " +"with a valid credit card access to utility computing and storage, but the " +"primary focus is enterprise customers. Data privacy concerns are a big " +"priority for Bob as they are seen as a major barrier to large-scale adoption" +" of the cloud by organizations." +msgstr "" + +#: ./doc/security-guide/ch030_state-of-networking.xml3(title) +msgid "State of Networking" +msgstr "" + +#: ./doc/security-guide/ch030_state-of-networking.xml4(para) +msgid "" +"OpenStack Networking in the Grizzly release enables the end-user or tenant " +"to define, utilize, and consume networking resources in new ways that had " +"not been possible in previous OpenStack Networking releases. OpenStack " +"Networking provides a tenant-facing API for defining network connectivity " +"and IP addressing for instances in the cloud in addition to orchestrating " +"the network configuration. With the transition to an API-centric networking " +"service, cloud architects and administrators should take into consideration " +"best practices to secure physical and virtual network infrastructure and " +"services." +msgstr "" + +#: ./doc/security-guide/ch030_state-of-networking.xml5(para) +msgid "" +"OpenStack Networking was designed with a plug-in architecture that provides " +"extensibility of the API via open source community or third-party services. " +"As you evaluate your architectural design requirements, it is important to " +"determine what features are available in OpenStack Networking core services," +" any additional services that are provided by third-party products, and what" +" supplemental services are required to be implemented in the physical " +"infrastructure." +msgstr "" + +#: ./doc/security-guide/ch030_state-of-networking.xml6(para) +msgid "" +"This section is a high-level overview of what processes and best practices " +"should be considered when implementing OpenStack Networking. We will talk " +"about the current state of services that are available, what future services" +" will be implemented, and the current limitations in this project." +msgstr "" + +#: ./doc/security-guide/ch043_database-transport-security.xml3(title) +msgid "Database Transport Security" +msgstr "" + +#: ./doc/security-guide/ch043_database-transport-security.xml4(para) +msgid "" +"This chapter covers issues related to network communications to and from the" +" database server. This includes IP address bindings and encrypting network " +"traffic with SSL." +msgstr "" + +#: ./doc/security-guide/ch043_database-transport-security.xml6(title) +msgid "Database Server IP Address Binding" +msgstr "" + +#: ./doc/security-guide/ch043_database-transport-security.xml7(para) +msgid "" +"To isolate sensitive database communications between the services and the " +"database, we strongly recommend that the database server(s) be configured to" +" only allow communications to and from the database over an isolated " +"management network. This is achieved by restricting the interface or IP " +"address on which the database server binds a network socket for incoming " +"client connections." +msgstr "" + +#: ./doc/security-guide/ch043_database-transport-security.xml9(title) +msgid "Restricting Bind Address for MySQL" +msgstr "" + +#: ./doc/security-guide/ch043_database-transport-security.xml10(para) +#: ./doc/security-guide/ch043_database-transport-security.xml33(para) +msgid "In my.cnf:" +msgstr "" + +#: ./doc/security-guide/ch043_database-transport-security.xml17(title) +msgid "Restricting Listen Address for PostgreSQL" +msgstr "" + +#: ./doc/security-guide/ch043_database-transport-security.xml18(para) +msgid "In postgresql.conf:" +msgstr "" + +#: ./doc/security-guide/ch043_database-transport-security.xml24(title) +msgid "Database Transport" +msgstr "" + +#: ./doc/security-guide/ch043_database-transport-security.xml25(para) +msgid "" +"In addition to restricting database communications to the management " +"network, we also strongly recommend that the cloud administrator configure " +"their database backend to require SSL. Using SSL for the database client " +"connections  protects the communications from tampering and eavesdropping. " +"As will be discussed in the next section, using SSL also provides the " +"framework for doing database user authentication via X.509 certificates " +"(commonly referred to as PKI). Below is guidance on how SSL is typically " +"configured for the two popular database backends MySQL and PostgreSQL." +msgstr "" + +#: ./doc/security-guide/ch043_database-transport-security.xml27(para) +msgid "" +"NOTE: When installing the certificate and key files, ensure that the file " +"permissions are restricted, for example chmod 0600, and " +"the ownership is restricted to the database daemon user to prevent " +"unauthorized access by other processes and users on the database server." +msgstr "" + +#: ./doc/security-guide/ch043_database-transport-security.xml31(title) +msgid "MySQL SSL Configuration" +msgstr "" + +#: ./doc/security-guide/ch043_database-transport-security.xml32(para) +msgid "" +"The following lines should be added in the system-wide MySQL configuration " +"file:" +msgstr "" + +#: ./doc/security-guide/ch043_database-transport-security.xml40(para) +#: ./doc/security-guide/ch043_database-transport-security.xml50(para) +msgid "" +"Optionally, if you wish to restrict the set of SSL ciphers used for the " +"encrypted connection. See http://www.openssl.org/docs/apps/ciphers.html" +" for a list of ciphers and the syntax for specifying the cipher string:" +msgstr "" + +#: ./doc/security-guide/ch043_database-transport-security.xml46(title) +msgid "PostgreSQL SSL Configuration" +msgstr "" + +#: ./doc/security-guide/ch043_database-transport-security.xml47(para) +msgid "" +"The following lines should be added in the system-wide PostgreSQL " +"configuration file, postgresql.conf." +msgstr "" + +#: ./doc/security-guide/ch043_database-transport-security.xml53(para) +msgid "" +"The server certificate, key, and certificate authority (CA) files should be " +"placed in the $PGDATA directory in the following files:" +msgstr "" + +#: ./doc/security-guide/ch043_database-transport-security.xml55(para) +msgid "$PGDATA/server.crt - Server certificate" +msgstr "" + +#: ./doc/security-guide/ch043_database-transport-security.xml58(para) +msgid "$PGDATA/server.key - Private key corresponding to server.crt" +msgstr "" + +#: ./doc/security-guide/ch043_database-transport-security.xml61(para) +msgid "$PGDATA/root.crt - Trusted certificate authorities" +msgstr "" + +#: ./doc/security-guide/ch043_database-transport-security.xml64(para) +msgid "$PGDATA/root.crl - Certificate revocation list" +msgstr "" + +#: ./doc/security-guide/ch048_key-management.xml3(title) +msgid "Key Management" +msgstr "" + +#: ./doc/security-guide/ch048_key-management.xml4(para) +msgid "" +"To address the often mentioned concern of tenant data privacy and limiting " +"cloud provider liability, there is greater interest within the OpenStack " +"community to make data encryption more ubiquitous. It is relatively easy for" +" an end-user to encrypt their data prior to saving it to the cloud, and this" +" is a viable path for tenant objects such as media files, database archives " +"among others. However, when client side encryption is used for virtual " +"machine images, block storage etc, client intervention is necessary in the " +"form of presenting keys to unlock the data for further use. To seamlessly " +"secure the data and yet have it accessible without burdening the client with" +" having to manage their keys and interactively provide them calls for a key " +"management service within OpenStack. Providing encryption and key management" +" services as part of OpenStack eases data-at-rest security adoption, " +"addresses customer concerns about the privacy and misuse of their data with " +"the added advantage of limiting cloud provider liability. Provider liability" +" is of concern in multi-tenant public clouds with respect to handing over " +"tenant data during a misuse investigation." +msgstr "" + +#: ./doc/security-guide/ch048_key-management.xml5(para) +msgid "" +"A key management service is in the early stages of being developed and has a" +" way to go before becoming an official component of OpenStack. Refer to " +"https://github.com/cloudkeep/barbican/wiki/_pages" +" for details." +msgstr "" + +#: ./doc/security-guide/ch048_key-management.xml6(para) +msgid "" +"It shall support the creation of keys, and their secure saving (with a " +"service master-key). Some of the design questions still being debated are " +"how much of the Key Management Interchange Protocol (KMIP) to support, key " +"formats, and certificate management.  The key manager will be pluggable to " +"facilitate deployments that need a third-party Hardware Security Module " +"(HSM)." +msgstr "" + +#: ./doc/security-guide/ch048_key-management.xml7(para) +msgid "" +"OpenStack Block Storage, Cinder, is the first service looking to integrate " +"with the key manager to provide volume encryption." +msgstr "" + +#: ./doc/security-guide/ch048_key-management.xml9(title) +msgid "References:" +msgstr "" + +#: ./doc/security-guide/ch048_key-management.xml11(link) +msgid "Barbican" +msgstr "" + +#: ./doc/security-guide/ch048_key-management.xml14(link) +msgid "KMIP" +msgstr "" + +#: ./doc/security-guide/ch009_case-studies.xml3(title) +msgid "Case Studies: System Documentation" +msgstr "" + +#: ./doc/security-guide/ch009_case-studies.xml4(para) +msgid "" +"In this case study we discuss how Alice and Bob would address their system " +"documentation requirements. The documentation suggested above includes " +"hardware and software records, network diagrams, and system configuration " +"details." +msgstr "" + +#: ./doc/security-guide/ch009_case-studies.xml7(para) +msgid "" +"Alice needs detailed documentation to satisfy FedRamp requirements.  She " +"sets up a configuration management database (CMDB) to store information " +"regarding all of the hardware, firmware, and software versions used " +"throughout the cloud. She also creates a network diagram detailing the cloud" +" architecture, paying careful attention to the security domains and the " +"services that span multiple security domains." +msgstr "" + +#: ./doc/security-guide/ch009_case-studies.xml8(para) +msgid "" +"Alice also needs to record each network service running in the cloud, what " +"interfaces and ports it binds to, the security domains for each service, and" +" why the service is needed. Alice decides to build automated tools to log " +"into each system in the cloud over secure shell (SSH) using the Python Fabric library. The tools collect " +"and store the information in the CMDB, which simplifies the audit process." +msgstr "" + +#: ./doc/security-guide/ch009_case-studies.xml12(para) +msgid "In this case, Bob will approach these steps the same as Alice." +msgstr "" + +#: ./doc/security-guide/ch056_case-studies-instance-management.xml3(title) +msgid "Case Studies: Instance Management" +msgstr "" + +#: ./doc/security-guide/ch056_case-studies-instance-management.xml4(para) +msgid "" +"In this case study we discuss how Alice and Bob would architect their clouds" +" with respect to instance entropy, scheduling instances, trusted images, and" +" instance migrations." +msgstr "" + +#: ./doc/security-guide/ch056_case-studies-instance-management.xml7(para) +msgid "" +"Alice has a need for lots of high quality entropy in the instances. For this" +" reason, she decides to purchase hardware with Intel Ivy Bridge chip sets " +"that support the RdRand instruction on each compute node. Using the entropy " +"gathering daemon (EGD) and LibVirt's EGD support, Alice ensures that this " +"entropy pool is distributed to the instances on each compute node." +msgstr "" + +#: ./doc/security-guide/ch056_case-studies-instance-management.xml8(para) +msgid "" +"For instance scheduling, Alice uses the trusted compute pools to ensure that" +" all cloud workloads are deployed to nodes that presented a proper boot time" +" attestation. Alice decides to disable user permissions for image uploading " +"to help ensure that the images used in the cloud are generated in a known " +"and trusted manner by the cloud administrators." +msgstr "" + +#: ./doc/security-guide/ch056_case-studies-instance-management.xml9(para) +msgid "" +"Finally, Alice disables instance migrations as this feature is less critical" +" for the high performance application workloads expected to run in this " +"cloud. This helps avoid the various security concerns related to instance " +"migrations." +msgstr "" + +#: ./doc/security-guide/ch056_case-studies-instance-management.xml13(para) +msgid "" +"Bob is aware that entropy will be a concern for some of his customers, such " +"as those in the financial industry. However, due to the added cost and " +"complexity, Bob has decided to forgo integrating hardware entropy into the " +"first iteration of his cloud. He adds hardware entropy as a fast-follow to " +"do for a later improvement for the second generation of his cloud " +"architecture." +msgstr "" + +#: ./doc/security-guide/ch056_case-studies-instance-management.xml14(para) +msgid "" +"Bob is interested in ensuring that customers receive a high quality of " +"service. He is concerned that providing too much explicit user control over " +"instance scheduling could negatively impact the quality of service. So he " +"disables this feature. Bob provides images in the cloud from a known trusted" +" source for users to use. Additionally, he also allows users to upload their" +" own images. However, users cannot generally share their images. This helps " +"prevent a user from sharing a malicious image, which could negatively impact" +" the security of other users in the cloud." +msgstr "" + +#: ./doc/security-guide/ch056_case-studies-instance-management.xml15(para) +msgid "" +"For migrations, Bob wants to enable secure instance migrations in order to " +"support rolling upgrades with minimal user downtime. Bob ensures that all " +"migrations occur on an isolated VLAN. He plans to defer implementing " +"encrypted migrations until this is better supported in Nova client tools. " +"However, he makes a note to track this carefully and switch to encrypted " +"migrations as soon as possible." +msgstr "" + +#: ./doc/security-guide/ch_preface.xml10(title) +msgid "Preface" +msgstr "" + +#. When image changes, this message will be marked fuzzy or untranslated for +#. you. +#. It doesn't matter what you translate it to: it's not used at all. +#: ./doc/security-guide/ch008_system-roles-types.xml101(None) +#: ./doc/security-guide/ch008_system-roles-types.xml106(None) +msgid "" +"@@image: 'static/services-protocols-ports.png'; " +"md5=fb1e9f47d969127b7a5ca683d38cfe20" +msgstr "" + +#: ./doc/security-guide/ch008_system-roles-types.xml8(title) +msgid "System Documentation Requirements" +msgstr "" + +#: ./doc/security-guide/ch008_system-roles-types.xml9(para) +msgid "" +"The system documentation for an OpenStack cloud deployment should follow the" +" templates and best practices for the Enterprise Information Technology " +"System in your organization. Organizations often have compliance " +"requirements which may require an overall System Security Plan to inventory " +"and document the architecture of a given system. There are common challenges" +" across the industry related to documenting the dynamic cloud infrastructure" +" and keeping the information up-to-date." +msgstr "" + +#: ./doc/security-guide/ch008_system-roles-types.xml18(title) +msgid "System Roles & Types" +msgstr "" + +#: ./doc/security-guide/ch008_system-roles-types.xml19(para) +msgid "" +"The two broadly defined types of nodes that generally make up an OpenStack " +"installation are:" +msgstr "" + +#: ./doc/security-guide/ch008_system-roles-types.xml23(para) +msgid "" +"Infrastructure nodes. The nodes that run the cloud related services such as " +"the OpenStack Identity Service, the message queuing service, storage, " +"networking, and other services required to support the operation of the " +"cloud." +msgstr "" + +#: ./doc/security-guide/ch008_system-roles-types.xml30(para) +msgid "" +"Compute, storage, or other resource nodes. Provide storage capacity or " +"virtual machines for your cloud." +msgstr "" + +#: ./doc/security-guide/ch008_system-roles-types.xml37(title) +msgid "System Inventory" +msgstr "" + +#: ./doc/security-guide/ch008_system-roles-types.xml38(para) +msgid "" +"Documentation should provide a general description of the OpenStack " +"environment and cover all systems used (production, development, test, " +"etc.). Documenting system components, networks, services, and software often" +" provides the bird's-eye view needed to thoroughly cover and consider " +"security concerns, attack vectors and possible security domain bridging " +"points. A system inventory may need to capture ephemeral resources such as " +"virtual machines or virtual disk volumes that would otherwise be persistent " +"resources in a traditional IT system." +msgstr "" + +#: ./doc/security-guide/ch008_system-roles-types.xml48(title) +msgid "Hardware Inventory" +msgstr "" + +#: ./doc/security-guide/ch008_system-roles-types.xml49(para) +msgid "" +"Clouds without stringent compliance requirements for written documentation " +"might benefit from having a Configuration Management Database " +"(CMDB). CMDBs are normally used for hardware asset " +"tracking and overall life-cycle management. By leveraging a CMDB, an " +"organization can quickly identify cloud infrastructure hardware. For " +"example, compute nodes, storage nodes, and network devices that exist on the" +" network but that might not be adequately protected and/or forgotten. " +"OpenStack provisioning system might provide some CMDB-like functions " +"especially if auto-discovery features of hardware attributes are available." +msgstr "" + +#: ./doc/security-guide/ch008_system-roles-types.xml63(title) +msgid "Software Inventory" +msgstr "" + +#: ./doc/security-guide/ch008_system-roles-types.xml64(para) +msgid "" +"Just as with hardware, all software components within the OpenStack " +"deployment should be documented. Components here should include system " +"databases; OpenStack software components and supporting sub-components; and," +" supporting infrastructure software such as load-balancers, reverse proxies," +" and network address translators. Having an authoritative list like this may" +" be critical toward understanding total system impact due to a compromise or" +" vulnerability of a specific class of software." +msgstr "" + +#: ./doc/security-guide/ch008_system-roles-types.xml76(title) +msgid "Network Topology" +msgstr "" + +#: ./doc/security-guide/ch008_system-roles-types.xml77(para) +msgid "" +"A Network Topology should be provided with highlights specifically calling " +"out the data flows and bridging points between the security domains. Network" +" ingress and egress points should be identified along with any OpenStack " +"logical system boundaries. Multiple diagrams may be needed to provide " +"complete visual coverage of the system.  A network topology document should " +"include virtual networks created on behalf of tenants by the system along " +"with virtual machine instances and gateways created by OpenStack." +msgstr "" + +#: ./doc/security-guide/ch008_system-roles-types.xml88(title) +msgid "Services, Protocols and Ports" +msgstr "" + +#: ./doc/security-guide/ch008_system-roles-types.xml89(para) +msgid "" +"The Service, Protocols and Ports table provides important additional detail " +"of an OpenStack deployment. A table view of all services running within the " +"cloud infrastructure can immediately inform, guide, and help check security " +"procedures. Firewall configuration, service port conflicts, security " +"remediation areas, and compliance requirements become easier to manage when " +"you have concise information available. Consider the following table:" +msgstr "" + +#: ./doc/security-guide/ch008_system-roles-types.xml109(para) +msgid "" +"Referencing a table of services, protocols and ports can help in " +"understanding the relationship between OpenStack components. It is highly " +"recommended that OpenStack deployments have information similar to this on " +"record." +msgstr "" + +#: ./doc/security-guide/ch025_web-dashboard.xml9(para) +msgid "" +"Horizon is the OpenStack dashboard that provides users a self-service portal" +" to provision their own resources within the limits set by administrators. " +"These include provisioning users, defining instance flavors, uploading VM " +"images, managing networks, setting up security groups, starting instances, " +"and accessing the instances via a console." +msgstr "" + +#: ./doc/security-guide/ch025_web-dashboard.xml14(para) +msgid "" +"The dashboard is based on the Django web framework, therefore secure " +"deployment practices for Django apply directly to Horizon. This guide " +"provides a popular set of Django security recommendations, further " +"information can be found by reading the Django deployment " +"and security documentation." +msgstr "" + +#: ./doc/security-guide/ch025_web-dashboard.xml21(para) +msgid "" +"The dashboard ships with reasonable default security settings, and has good " +"deployment" +" and configuration documentation." +msgstr "" + +#: ./doc/security-guide/ch025_web-dashboard.xml26(title) +msgid "Basic Web Server Configuration" +msgstr "" + +#: ./doc/security-guide/ch025_web-dashboard.xml27(para) +msgid "" +"The dashboard should be deployed as a Web Services Gateway Interface (WSGI) " +"application behind an HTTPS proxy such as Apache or nginx. If Apache is not " +"already in use, we recommend nginx since it is lighter weight and easier to " +"configure correctly." +msgstr "" + +#: ./doc/security-guide/ch025_web-dashboard.xml32(para) +msgid "" +"When using nginx, we recommend gunicorn as " +"the wsgi host with an appropriate number of synchronous workers. We strongly" +" advise against deployments using fastcgi, scgi, or uWSGI. We strongly " +"advise against the use of synthetic performance benchmarks when choosing a " +"wsgi server." +msgstr "" + +#: ./doc/security-guide/ch025_web-dashboard.xml39(para) +msgid "" +"When using Apache, we recommend mod_wsgi" +" to host dashboard." +msgstr "" + +#: ./doc/security-guide/ch025_web-dashboard.xml44(title) +msgid "HTTPS" +msgstr "" + +#: ./doc/security-guide/ch025_web-dashboard.xml45(para) +msgid "" +"The dashboard should be deployed behind a secure HTTPS server using a valid," +" trusted certificate from a recognized certificate authority (CA). Private " +"organization-issued certificates are only appropriate when the root of trust" +" is pre-installed in all user browsers." +msgstr "" + +#: ./doc/security-guide/ch025_web-dashboard.xml50(para) +msgid "" +"HTTP requests to the dashboard domain should be configured to redirect to " +"the fully qualified HTTPS URL." +msgstr "" + +#: ./doc/security-guide/ch025_web-dashboard.xml54(title) +msgid "HTTP Strict Transport Security (HSTS)" +msgstr "" + +#: ./doc/security-guide/ch025_web-dashboard.xml55(para) +msgid "It is highly recommended to use HTTP Strict Transport Security (HSTS)." +msgstr "" + +#: ./doc/security-guide/ch025_web-dashboard.xml57(para) +msgid "" +"NOTE: If you are using an HTTPS proxy in front of your web server, rather " +"than using an HTTP server with HTTPS functionality, follow the Django documentation on modifying the SECURE_PROXY_SSL_HEADER " +"variable." +msgstr "" + +#: ./doc/security-guide/ch025_web-dashboard.xml63(para) +msgid "" +"See the chapter on PKI/SSL Everywhere for more specific recommendations and " +"server configurations for HTTPS configurations, including the configuration " +"of HSTS." +msgstr "" + +#: ./doc/security-guide/ch025_web-dashboard.xml68(title) +msgid "Front end Caching" +msgstr "" + +#: ./doc/security-guide/ch025_web-dashboard.xml69(para) +msgid "" +"Since dashboard is rendering dynamic content passed directly from OpenStack " +"API requests, we do not recommend front end caching layers such as varnish. " +"In Django, static media is directly served from Apache or nginx and already " +"benefits from web host caching." +msgstr "" + +#: ./doc/security-guide/ch025_web-dashboard.xml76(title) +msgid "Domain Names" +msgstr "" + +#: ./doc/security-guide/ch025_web-dashboard.xml77(para) +msgid "" +"Many organizations typically deploy web applications at subdomains of an " +"overarching organization domain. It is natural for users to expect a domain " +"of the form openstack.example.org. In this context, there are " +"often many other applications deployed in the same second-level namespace, " +"often serving user-controlled content. This name structure is convenient and" +" simplifies name server maintenance." +msgstr "" + +#: ./doc/security-guide/ch025_web-dashboard.xml85(para) +msgid "" +"We strongly recommend deploying horizon to a second-level " +"domain, such as https://example.com, and advise " +"against deploying horizon on a shared subdomain of any " +"level, for example https://openstack.example.org or " +"https://horizon.openstack.example.org. We also advise against " +"deploying to bare internal domains like https://horizon/." +msgstr "" + +#: ./doc/security-guide/ch025_web-dashboard.xml93(para) +msgid "" +"This recommendation is based on the limitations browser same-origin-policy. " +"The recommendations in this guide cannot effectively protect users against " +"known attacks if dashboard is deployed on a domain which also hosts user-" +"generated content, such as scripts, images, or uploads of any kind, even if " +"the user-generated content is on a different subdomain. This approach is " +"used by most major web presences, such as googleusercontent.com, fbcdn.com, " +"github.io, and twimg.com, to ensure that user generated content stays " +"separate from cookies and security tokens." +msgstr "" + +#: ./doc/security-guide/ch025_web-dashboard.xml103(para) +msgid "" +"Additionally, if you decline to follow this recommendation above about " +"second-level domains, it is vital that you avoid the cookie backed session " +"store and employ HTTP Strict Transport Security (HSTS). When deployed on a " +"subdomain, dashboard's security is only as strong as the weakest application" +" deployed on the same second-level domain." +msgstr "" + +#: ./doc/security-guide/ch025_web-dashboard.xml111(title) +msgid "Static Media" +msgstr "" + +#: ./doc/security-guide/ch025_web-dashboard.xml112(para) +msgid "" +"Dashboard's static media should be deployed to a subdomain of the dashboard " +"domain and served by the web server. The use of an external content delivery" +" network (CDN) is also acceptable. This subdomain should not set cookies or " +"serve user-provided content. The media should also be served with HTTPS." +msgstr "" + +#: ./doc/security-guide/ch025_web-dashboard.xml117(para) +msgid "" +"Django media settings are documented at https://docs.djangoproject.com/en/1.5/ref/settings/#static-" +"root." +msgstr "" + +#: ./doc/security-guide/ch025_web-dashboard.xml120(para) +msgid "" +"Dashboard's default configuration uses django_compressor to compress and " +"minify css and JavaScript content before serving it. This process should be " +"statically done before deploying dashboard, rather than using the default " +"in-request dynamic compression and copying the resulting files along with " +"deployed code or to the CDN server. Compression should be done in a non-" +"production build environment. If this is not practical, we recommend " +"disabling resource compression entirely. Online compression dependencies " +"(less, nodejs) should not be installed on production machines." +msgstr "" + +#: ./doc/security-guide/ch025_web-dashboard.xml134(title) +msgid "Secret Key" +msgstr "" + +#: ./doc/security-guide/ch025_web-dashboard.xml135(para) +msgid "" +"Dashboard depends on a shared SECRET_KEY setting for some security " +"functions. It should be a randomly generated string at least 64 characters " +"long. It must be shared across all active Horizon instances. Compromise of " +"this key may allow a remote attacker to execute arbitrary code. Rotating " +"this key invalidates existing user sessions and caching. Do not commit this " +"key to public repositories." +msgstr "" + +#: ./doc/security-guide/ch025_web-dashboard.xml144(title) +msgid "Session Backend" +msgstr "" + +#: ./doc/security-guide/ch025_web-dashboard.xml145(para) +msgid "" +"Horizon's default session backend " +"(django.contrib.sessions.backends.signed_cookies) " +"stores user data in signed but unencrypted " +"cookies stored in the browser. This approach allows the most " +"simple session backend scaling since each Horizon instance is stateless, but" +" it comes at the cost of storing sensitive access tokens in the " +"client browser and transmitting them with every request. This " +"backend ensures that session data has not been tampered with, but the data " +"itself is not encrypted other than the encryption provided by HTTPS." +msgstr "" + +#: ./doc/security-guide/ch025_web-dashboard.xml156(para) +msgid "" +"If your architecture allows it, we recommend using " +"django.contrib.sessions.backends.cache as your session " +"backend with memcache as the cache. Memcache must not be exposed publicly, " +"and should communicate over a secured private channel. If you choose to use " +"the signed cookies backend, refer to the Django documentation understand the" +" security trade-offs." +msgstr "" + +#: ./doc/security-guide/ch025_web-dashboard.xml163(para) +msgid "" +"For further details, consult the Django session backend " +"documentation." +msgstr "" + +#: ./doc/security-guide/ch025_web-dashboard.xml168(title) +msgid "Allowed Hosts" +msgstr "" + +#: ./doc/security-guide/ch025_web-dashboard.xml169(para) +msgid "" +"Configure the ALLOWED_HOSTS setting with the domain or domains where Horizon" +" is available. Failure to configure this setting (especially if not " +"following the recommendation above regarding second level domains) opens " +"Horizon to a number of serious attacks. Wild card domains should be avoided." +msgstr "" + +#: ./doc/security-guide/ch025_web-dashboard.xml174(para) +msgid "" +"For further details, see the Django documentation on settings." +msgstr "" + +#: ./doc/security-guide/ch025_web-dashboard.xml179(title) +msgid "Cookies" +msgstr "" + +#: ./doc/security-guide/ch025_web-dashboard.xml180(para) +msgid "Session Cookies should be set to HTTPONLY:" +msgstr "" + +#: ./doc/security-guide/ch025_web-dashboard.xml183(para) +msgid "" +"Never configure CSRF or session cookies to have a wild card domain with a " +"leading dot. Horizon's session and CSRF cookie should be secured when " +"deployed with HTTPS:" +msgstr "" + +#: ./doc/security-guide/ch025_web-dashboard.xml191(title) +msgid "Password Auto Complete" +msgstr "" + +#: ./doc/security-guide/ch025_web-dashboard.xml192(para) +msgid "" +"We recommend that implementers do not change the default password auto " +"complete behavior. Users choose stronger passwords in environments that " +"allow them to use the secure browser password manager. Organizations which " +"forbid the browser password manager should enforce this policy at the " +"desktop level." +msgstr "" + +#: ./doc/security-guide/ch025_web-dashboard.xml200(title) +msgid "Cross Site Request Forgery (CSRF)" +msgstr "" + +#: ./doc/security-guide/ch025_web-dashboard.xml201(para) +msgid "" +"Django has a dedicated middleware for cross-site request forgery (CSRF)." +msgstr "" + +#: ./doc/security-guide/ch025_web-dashboard.xml204(para) +msgid "" +"Dashboard is designed to discourage developers from introducing cross-site " +"scripting vulnerabilities with custom dashboards. However, it is important " +"to audit custom dashboards, especially ones that are javascript-heavy for " +"inappropriate use of the @csrf_exempt decorator. Dashboards which do not " +"follow these recommended security settings should be carefully evaluated " +"before restrictions are relaxed." +msgstr "" + +#: ./doc/security-guide/ch025_web-dashboard.xml213(title) +msgid "Cross Site Scripting (XSS)" +msgstr "" + +#: ./doc/security-guide/ch025_web-dashboard.xml214(para) +msgid "" +"Unlike many similar systems, OpenStack dashboard allows the entire Unicode " +"character set in most fields. This means developers have less latitude to " +"make escaping mistakes that open attack vectors for cross-site scripting " +"(XSS)." +msgstr "" + +#: ./doc/security-guide/ch025_web-dashboard.xml218(para) +msgid "" +"Dashboard provides tools for developers to avoid creating XSS " +"vulnerabilities, but they only work if developers use them correctly. Audit " +"any custom dashboards, paying particular attention to use of the mark_safe " +"function, use of is_safe with custom template tags, the safe template tag, " +"anywhere auto escape is turned off, and any JavaScript which might evaluate " +"improperly escaped data." +msgstr "" + +#: ./doc/security-guide/ch025_web-dashboard.xml227(title) +msgid "Cross Origin Resource Sharing (CORS)" +msgstr "" + +#: ./doc/security-guide/ch025_web-dashboard.xml228(para) +msgid "" +"Configure your web server to send a restrictive CORS header with each " +"response, allowing only the Horizon domain and protocol:" +msgstr "" + +#: ./doc/security-guide/ch025_web-dashboard.xml233(para) +msgid "Never allow the wild card origin." +msgstr "" + +#: ./doc/security-guide/ch025_web-dashboard.xml236(title) +msgid "Horizon Image Upload" +msgstr "" + +#: ./doc/security-guide/ch025_web-dashboard.xml237(para) +msgid "" +"We recommend that implementers disable HORIZON_IMAGES_ALLOW_UPLOAD unless they have " +"implemented a plan to prevent resource exhaustion and denial of service." +msgstr "" + +#: ./doc/security-guide/ch025_web-dashboard.xml244(title) +msgid "Upgrading" +msgstr "" + +#: ./doc/security-guide/ch025_web-dashboard.xml245(para) +msgid "" +"Django security releases are generally well tested and aggressively " +"backwards compatible. In almost all cases, new major releases of Django are " +"also fully backwards compatible with previous releases. Dashboard " +"implementers are strongly encouraged to run the latest stable release of " +"Django with up-to-date security releases." +msgstr "" + +#: ./doc/security-guide/ch025_web-dashboard.xml253(title) +msgid "Debug" +msgstr "" + +#: ./doc/security-guide/ch025_web-dashboard.xml254(para) +msgid "" +"Make sure DEBUG is set to False in production. In Django, DEBUG displays " +"stack traces and sensitive web server state information on any exception." +msgstr "" + +#: ./doc/security-guide/ch022_case-studies-api-endpoints.xml3(title) +msgid "Case Studies: API Endpoints" +msgstr "" + +#: ./doc/security-guide/ch022_case-studies-api-endpoints.xml4(para) +msgid "" +"In this case study we discuss how Alice and Bob would address endpoint " +"configuration to secure their private and public clouds. Alice's cloud is " +"not publicly accessible, but she is still concerned about securing the " +"endpoints against improper use.  Bob's cloud, being public, must take " +"measures to reduce the risk of attacks by external adversaries." +msgstr "" + +#: ./doc/security-guide/ch022_case-studies-api-endpoints.xml7(para) +msgid "" +"Alice's organization requires that the security architecture protect the " +"access to the public and private endpoints, so she elects to use the Apache " +"SSL proxy on both public and internal services. Alice's organization has " +"implemented its own certificate authority. Alice contacts the PKI office in " +"her agency that manages her PKI and certificate issuance. Alice obtains " +"certificates issued by this CA and configures the services within both the " +"public and management security domains to use these certificates. Since " +"Alice's OpenStack deployment exists entirely on a disconnected from the " +"Internet network, she makes sure to remove all default CA bundles that " +"contain external public CA providers to ensure the OpenStack services only " +"accept client certificates issued by her agency's CA. Alice has registered " +"all of the services in the Keystone Services Catalog, using the internal " +"URLs for access by internal services. She has installed host-based intrusion" +" detection on all of the API endpoints." +msgstr "" + +#: ./doc/security-guide/ch022_case-studies-api-endpoints.xml11(para) +msgid "" +"Bob must also protect the access to the public and private endpoints, so he " +"elects to use the Apache SSL proxy on both public and internal services. On " +"the public services, he has configured the certificate key files with " +"certificates signed by a well-known Certificate Authority. He has used his " +"organization's self-signed CA to sign certificates in the internal services " +"on the Management network. Bob has registered his services in the Keystone " +"Services Catalog, using the internal URLs for access by internal services. " +"Bob's public cloud runs services on SELinux, which he has configured with a " +"mandatory access control policy to reduce the impact of any publicly " +"accessible services that may be compromised. He has also configured the " +"endpoints with a host-based IDS." +msgstr "" + +#: ./doc/security-guide/ch046_data-residency.xml3(title) +msgid "Data Privacy Concerns" +msgstr "" + +#: ./doc/security-guide/ch046_data-residency.xml4(para) +msgid "" +"OpenStack is designed to support multitenancy and those tenants will most " +"probably have different data requirements. As a cloud builder and operator " +"you need to ensure your OpenStack environment can address various data " +"privacy concerns and regulations. In this chapter we will address the " +"following topics around Data Privacy as it pertains to OpenStack " +"implementations:" +msgstr "" + +#: ./doc/security-guide/ch046_data-residency.xml6(para) +#: ./doc/security-guide/ch046_data-residency.xml13(title) +msgid "Data Residency" +msgstr "" + +#: ./doc/security-guide/ch046_data-residency.xml9(para) +#: ./doc/security-guide/ch046_data-residency.xml64(title) +msgid "Data Disposal" +msgstr "" + +#: ./doc/security-guide/ch046_data-residency.xml14(para) +msgid "" +"The privacy and isolation of data has consistently been cited as the primary" +" barrier to cloud adoption over the past few years. Concerns over who owns " +"data in the cloud and whether the cloud operator can be ultimately trusted " +"as a custodian of this data have been significant issues in the past." +msgstr "" + +#: ./doc/security-guide/ch046_data-residency.xml15(para) +msgid "" +"Numerous OpenStack services maintain data and metadata belonging to tenants " +"or reference tenant information." +msgstr "" + +#: ./doc/security-guide/ch046_data-residency.xml16(para) +msgid "" +"Tenant data stored in an OpenStack cloud may include the following items:" +msgstr "" + +#: ./doc/security-guide/ch046_data-residency.xml18(para) +msgid "Swift objects" +msgstr "" + +#: ./doc/security-guide/ch046_data-residency.xml21(para) +msgid "Compute instance ephemeral filesystem storage" +msgstr "" + +#: ./doc/security-guide/ch046_data-residency.xml24(para) +msgid "Compute instance memory" +msgstr "" + +#: ./doc/security-guide/ch046_data-residency.xml27(para) +#: ./doc/security-guide/ch046_data-residency.xml113(title) +msgid "Cinder volume data" +msgstr "" + +#: ./doc/security-guide/ch046_data-residency.xml30(para) +msgid "Public keys for Compute Access" +msgstr "" + +#: ./doc/security-guide/ch046_data-residency.xml33(para) +msgid "Virtual Machine Images in Glance" +msgstr "" + +#: ./doc/security-guide/ch046_data-residency.xml36(para) +msgid "Machine snapshots" +msgstr "" + +#: ./doc/security-guide/ch046_data-residency.xml39(para) +msgid "Data passed to OpenStack Compute's configuration-drive extension" +msgstr "" + +#: ./doc/security-guide/ch046_data-residency.xml42(para) +msgid "" +"Metadata stored by an OpenStack cloud includes the following non-exhaustive " +"items:" +msgstr "" + +#: ./doc/security-guide/ch046_data-residency.xml44(para) +msgid "Organization name" +msgstr "" + +#: ./doc/security-guide/ch046_data-residency.xml47(para) +msgid "User's \"Real Name\"" +msgstr "" + +#: ./doc/security-guide/ch046_data-residency.xml50(para) +msgid "" +"Number or size of running instances, buckets, objects, volumes, and other " +"quota-related items" +msgstr "" + +#: ./doc/security-guide/ch046_data-residency.xml53(para) +msgid "Number of hours running instances or storing data" +msgstr "" + +#: ./doc/security-guide/ch046_data-residency.xml56(para) +msgid "IP addresses of users" +msgstr "" + +#: ./doc/security-guide/ch046_data-residency.xml59(para) +msgid "Internally generated private keys for compute image bundling" +msgstr "" + +#: ./doc/security-guide/ch046_data-residency.xml65(para) +msgid "" +"OpenStack operators should strive to provide a certain level of tenant data " +"disposal assurance. Best practices suggest that the operator sanitize cloud " +"system media (digital and non-digital) prior to disposal, release out of " +"organization control or release for reuse. Sanitization methods should " +"implement an appropriate level of strength and integrity given the specific " +"security domain and sensitivity of the information." +msgstr "" + +#: ./doc/security-guide/ch046_data-residency.xml67(para) +msgid "" +"\"Sanitization is the process used to remove information from system media " +"such that there is reasonable assurance that the information cannot be " +"retrieved or reconstructed. Sanitization techniques, including clearing, " +"purging, and destroying media information, prevent the disclosure of " +"organizational information to unauthorized individuals when such media is " +"reused or released for disposal.\" [NIST Special Publication 800-53 Revision" +" 3]" +msgstr "" + +#: ./doc/security-guide/ch046_data-residency.xml69(para) +msgid "" +"General data disposal and sanitization guidelines as adopted from NIST " +"recommended security controls. Cloud Operators should:" +msgstr "" + +#: ./doc/security-guide/ch046_data-residency.xml71(para) +msgid "Track, document and verify media sanitization and disposal actions." +msgstr "" + +#: ./doc/security-guide/ch046_data-residency.xml74(para) +msgid "Test sanitation equipment and procedures to verify proper performance." +msgstr "" + +#: ./doc/security-guide/ch046_data-residency.xml78(para) +msgid "" +"Sanitize portable, removable storage devices prior to connecting such " +"devices to the cloud infrastructure." +msgstr "" + +#: ./doc/security-guide/ch046_data-residency.xml81(para) +msgid "Destroy cloud system media that cannot be sanitized." +msgstr "" + +#: ./doc/security-guide/ch046_data-residency.xml84(para) +msgid "In an OpenStack deployment you will need to address the following:" +msgstr "" + +#: ./doc/security-guide/ch046_data-residency.xml86(para) +msgid "Secure data erasure" +msgstr "" + +#: ./doc/security-guide/ch046_data-residency.xml89(para) +#: ./doc/security-guide/ch046_data-residency.xml106(title) +msgid "Instance memory scrubbing" +msgstr "" + +#: ./doc/security-guide/ch046_data-residency.xml92(para) +msgid "Block Storage volume data" +msgstr "" + +#: ./doc/security-guide/ch046_data-residency.xml95(para) +#: ./doc/security-guide/ch046_data-residency.xml119(title) +msgid "Compute instance ephemeral storage" +msgstr "" + +#: ./doc/security-guide/ch046_data-residency.xml98(para) +#: ./doc/security-guide/ch046_data-residency.xml126(title) +msgid "Bare metal server sanitization" +msgstr "" + +#: ./doc/security-guide/ch046_data-residency.xml102(title) +msgid "Data not securely erased" +msgstr "" + +#: ./doc/security-guide/ch046_data-residency.xml103(para) +msgid "" +"Within OpenStack some data may be deleted, but not securely erased in the " +"context of the NIST standards outlined above. This is generally applicable " +"to most or all of the above-defined metadata and information stored in the " +"database. This may be remediated with database and/or system configuration " +"for auto vacuuming and periodic free-space wiping." +msgstr "" + +#: ./doc/security-guide/ch046_data-residency.xml107(para) +msgid "" +"Specific to various hypervisors is the treatment of instance memory. This " +"behavior is not defined in OpenStack Compute, although it is generally " +"expected of hypervisors that they will make a best effort to scrub memory " +"either upon deletion of an instance, upon creation of an instance, or both." +msgstr "" + +#: ./doc/security-guide/ch046_data-residency.xml108(para) +msgid "" +"Xen explicitly assigns dedicated memory regions to instances and scrubs data" +" upon the destruction of instances (or domains in Xen parlance). KVM depends" +" more greatly on Linux page management; A complex set of rules related to " +"KVM paging is defined in the KVM documentation." +msgstr "" + +#: ./doc/security-guide/ch046_data-residency.xml109(para) +msgid "" +"It is important to note that use of the Xen memory balloon feature is likely" +" to result in information disclosure. We strongly recommended to avoid use " +"of this feature." +msgstr "" + +#: ./doc/security-guide/ch046_data-residency.xml110(para) +msgid "" +"For these and other hypervisors, we recommend referring to hypervisor-" +"specific documentation." +msgstr "" + +#: ./doc/security-guide/ch046_data-residency.xml114(para) +msgid "" +"Plugins to OpenStack Block Storage will store data in a variety of ways. " +"Many plugins are specific to a vendor or technology, whereas others are more" +" DIY solutions around filesystems such as LVM or ZFS. Methods to securely " +"destroy data will vary from one plugin to another, from one vendor's " +"solution to another, and from one filesystem to another." +msgstr "" + +#: ./doc/security-guide/ch046_data-residency.xml115(para) +msgid "" +"Some backends such as ZFS will support copy-on-write to prevent data " +"exposure. In these cases, reads from unwritten blocks will always return " +"zero. Other backends such as LVM may not natively support this, thus the " +"Cinder plugin takes the responsibility to override previously written blocks" +" before handing them to users. It is important to review what assurances " +"your chosen volume backend provides and to see what mediations may be " +"available for those assurances not provided." +msgstr "" + +#: ./doc/security-guide/ch046_data-residency.xml116(para) +msgid "" +"Finally, while not a feature of OpenStack, vendors and implementors may " +"choose to add or support encryption of volumes. In this case, destruction of" +" data is as simple as throwing away the key." +msgstr "" + +#: ./doc/security-guide/ch046_data-residency.xml120(para) +msgid "" +"The creation and destruction of ephemeral storage will be somewhat dependent" +" on the chosen hypervisor and the OpenStack Compute plugin." +msgstr "" + +#: ./doc/security-guide/ch046_data-residency.xml121(para) +msgid "" +"The libvirt plugin for compute may maintain ephemeral storage directly on a " +"filesystem, or in LVM. Filesystem storage generally will not overwrite data " +"when it is removed, although there is a guarantee that dirty extents are not" +" provisioned to users." +msgstr "" + +#: ./doc/security-guide/ch046_data-residency.xml122(para) +msgid "" +"When using LVM backed ephemeral storage, which is block-based, it is " +"necessary that the OpenStack Compute software securely erases blocks to " +"prevent information disclosure. There have in the past been information " +"disclosure vulnerabilities related to improperly erased ephemeral block " +"storage devices." +msgstr "" + +#: ./doc/security-guide/ch046_data-residency.xml123(para) +msgid "" +"Filesystem storage is a more secure solution for ephemeral block storage " +"devices than LVM as dirty extents cannot be provisioned to users. However, " +"it is important to be mindful that user data is not destroyed, so it is " +"suggested to encrypt the backing filesystem." +msgstr "" + +#: ./doc/security-guide/ch046_data-residency.xml127(para) +msgid "" +"A bare metal server driver for Nova was under development and has since " +"moved into a separate project called Ironic. At the time " +"of this writing, Ironic does not appear to address sanitization of tenant " +"data resident the physical hardware." +msgstr "" + +#: ./doc/security-guide/ch046_data-residency.xml128(para) +msgid "" +"Additionally, it is possible for tenants of a bare metal system to modify " +"system firmware. TPM technology, described in ##link:Management/Node " +"Bootstrapping##, provides a solution for detecting unauthorized firmware " +"changes." +msgstr "" + +#: ./doc/security-guide/ch062_audit-guidance.xml3(title) +msgid "Understanding the Audit Process" +msgstr "" + +#: ./doc/security-guide/ch062_audit-guidance.xml4(para) +msgid "" +"Information system security compliance is reliant on the completion of two " +"foundational processes:" +msgstr "" + +#: ./doc/security-guide/ch062_audit-guidance.xml6(para) +msgid "" +"Implementation and Operation of Security " +"ControlsAligning the information system with in-scope standards " +"and regulations involves internal tasks which must be conducted before a " +"formal assessment. Auditors may be involved at this state to conduct gap " +"analysis, provide guidance, and increase the likelihood of successful " +"certification." +msgstr "" + +#: ./doc/security-guide/ch062_audit-guidance.xml9(para) +msgid "" +"Independent Verification and " +"ValidationDemonstration to a neutral third-party that system " +"security controls are implemented and operating effectively, in compliance " +"with in-scope standards and regulations, is required before many information" +" systems achieve certified status. Many certifications require periodic " +"audits to ensure continued certification, considered part of an overarching " +"continuous monitoring practice.  " +msgstr "" + +#: ./doc/security-guide/ch062_audit-guidance.xml13(title) +msgid "Determining Audit Scope" +msgstr "" + +#: ./doc/security-guide/ch062_audit-guidance.xml14(para) +msgid "" +"Determining audit scope, specifically what controls are needed and how to " +"design or modify an OpenStack deployment to satisfy them, should be the " +"initial planning step." +msgstr "" + +#: ./doc/security-guide/ch062_audit-guidance.xml15(para) +msgid "" +"When scoping OpenStack deployments for compliance purposes, consider " +"prioritizing controls around sensitive services, such as command and control" +" functions and the base virtualization technology. Compromises of these " +"facilities may impact an OpenStack environment in its entirety." +msgstr "" + +#: ./doc/security-guide/ch062_audit-guidance.xml16(para) +msgid "" +"Scope reduction helps ensure OpenStack architects establish high quality " +"security controls which are tailored to a particular deployment, however it " +"is paramount to ensure these practices do not omit areas or features from " +"security hardening. A common example is applicable to PCI-DSS guidelines, " +"where payment related infrastructure may be scrutinized for security issues," +" but supporting services are left ignored, and vulnerable to attack." +msgstr "" + +#: ./doc/security-guide/ch062_audit-guidance.xml17(para) +msgid "" +"When addressing compliance, you can increase efficiency and reduce work " +"effort by identifying common areas and criteria that apply across multiple " +"certifications. Much of the audit principles and guidelines discussed in " +"this book will assist in identifying these controls, additionally a number " +"of external entities provide comprehensive lists. The following are some " +"examples:" +msgstr "" + +#: ./doc/security-guide/ch062_audit-guidance.xml18(para) +msgid "" +"The Cloud " +"Security Alliance Cloud Controls Matrix (CCM) assists both cloud " +"providers and consumers in assessing the overall security of a cloud " +"provider. The CSA CMM provides a controls framework that map to many " +"industry-accepted standards and regulations including the ISO 27001/2, " +"ISACA, COBIT, PCI, NIST, Jericho Forum and NERC CIP." +msgstr "" + +#: ./doc/security-guide/ch062_audit-guidance.xml19(para) +msgid "" +"The SCAP " +"Security Guide is another useful reference. This is still an emerging" +" source, but we anticipate that this will grow into a tool with controls " +"mappings that are more focused on the US federal government certifications " +"and recommendations. For example, the SCAP Security Guide currently has some" +" mappings for security technical implementation guides (STIGs) and " +"NIST-800-53." +msgstr "" + +#: ./doc/security-guide/ch062_audit-guidance.xml20(para) +msgid "" +"These control mappings will help identify common control criteria across " +"certifications, and provide visibility to both auditors and auditees on " +"problem areas within control sets for particular compliance certifications " +"and attestations." +msgstr "" + +#: ./doc/security-guide/ch062_audit-guidance.xml23(title) +msgid "Internal Audit" +msgstr "" + +#: ./doc/security-guide/ch062_audit-guidance.xml24(para) +msgid "" +"Once a cloud is deployed, it is time for an internal audit. This is the time" +" compare the controls you identified above with the design, features, and " +"deployment strategies utilized in your cloud. The goal is to understand how " +"each control is handled and where gaps exist. Document all of the findings " +"for future reference." +msgstr "" + +#: ./doc/security-guide/ch062_audit-guidance.xml25(para) +msgid "" +"When auditing an OpenStack cloud it is important to appreciate the multi-" +"tenant environment inherent in the OpenStack architecture. Some critical " +"areas for concern include data disposal, hypervisor security, node " +"hardening, and authentication mechanisms." +msgstr "" + +#: ./doc/security-guide/ch062_audit-guidance.xml28(title) +msgid "Prepare for External Audit" +msgstr "" + +#: ./doc/security-guide/ch062_audit-guidance.xml29(para) +msgid "" +"Once the internal audit results look good, it is time to prepare for an " +"external audit. There are several key actions to take at this stage, these " +"are outlined below:" +msgstr "" + +#: ./doc/security-guide/ch062_audit-guidance.xml31(para) +msgid "" +"Maintain good records from your internal audit. These will prove useful " +"during the external audit so you can be prepared to answer questions about " +"mapping the compliance controls to a particular deployment." +msgstr "" + +#: ./doc/security-guide/ch062_audit-guidance.xml34(para) +msgid "" +"Deploy automated testing tools to ensure that the cloud remains compliant " +"over time." +msgstr "" + +#: ./doc/security-guide/ch062_audit-guidance.xml37(para) +msgid "Select an auditor." +msgstr "" + +#: ./doc/security-guide/ch062_audit-guidance.xml40(para) +msgid "" +"Selecting an auditor can be challenging. Ideally, you are looking for " +"someone with experience in cloud compliance audits. OpenStack experience is " +"another big plus. Often it is best to consult with people who have been " +"through this process for referrals. Cost can vary greatly depending on the " +"scope of the engagement and the audit firm considered." +msgstr "" + +#: ./doc/security-guide/ch062_audit-guidance.xml43(title) +msgid "External Audit" +msgstr "" + +#: ./doc/security-guide/ch062_audit-guidance.xml44(para) +msgid "" +"This is the formal audit process. Auditors will test security controls in " +"scope for a specific certification, and demand evidentiary requirements to " +"prove that these controls were also in place for the audit window (for " +"example SOC 2 audits generally evaluate security controls over a 6-12 months" +" period).  Any control failures are logged, and will be documented in the " +"external auditors final report.  Dependent on the type of OpenStack " +"deployment, these reports may be viewed by customers, so it is important to " +"avoid control failures. This is why audit preparation is so important." +msgstr "" + +#: ./doc/security-guide/ch062_audit-guidance.xml47(title) +msgid "Compliance Maintenance" +msgstr "" + +#: ./doc/security-guide/ch062_audit-guidance.xml48(para) +msgid "" +"The process doesn't end with a single external audit. Most certifications " +"require continual compliance activities which means repeating the audit " +"process periodically.  We recommend integrating automated compliance " +"verification tools into a cloud to ensure that it is compliant at all times." +" This should be in done in addition to other security monitoring tools. " +"Remember that the goal is both security and compliance." +" Failing on either of these fronts will significantly complicate future " +"audits." +msgstr "" + +#. When image changes, this message will be marked fuzzy or untranslated for +#. you. +#. It doesn't matter what you translate it to: it's not used at all. +#: ./doc/security-guide/ch042_database-overview.xml13(None) +#: ./doc/security-guide/ch042_database-overview.xml16(None) +msgid "" +"@@image: 'static/databaseusername.png'; md5=a6a5dadedbc1517069ca388c7ac5940a" +msgstr "" + +#. When image changes, this message will be marked fuzzy or untranslated for +#. you. +#. It doesn't matter what you translate it to: it's not used at all. +#: ./doc/security-guide/ch042_database-overview.xml37(None) +#: ./doc/security-guide/ch042_database-overview.xml40(None) +msgid "" +"@@image: 'static/databaseusernamessl.png'; " +"md5=9c43242c47eb159b6f61ac41f3d8bced" +msgstr "" + +#. When image changes, this message will be marked fuzzy or untranslated for +#. you. +#. It doesn't matter what you translate it to: it's not used at all. +#: ./doc/security-guide/ch042_database-overview.xml101(None) +#: ./doc/security-guide/ch042_database-overview.xml104(None) +msgid "" +"@@image: 'static/novaconductor.png'; md5=dbc1ba139bd1af333f0415bb48704843" +msgstr "" + +#: ./doc/security-guide/ch042_database-overview.xml3(title) +msgid "Database Access Control" +msgstr "" + +#: ./doc/security-guide/ch042_database-overview.xml4(para) +msgid "" +"Each of the core OpenStack services (Compute, Identity, Networking, Block " +"Storage) store state and configuration information in databases. In this " +"chapter, we discuss how databases are used currently in OpenStack. We also " +"explore security concerns, and the security ramifications of database " +"backend choices." +msgstr "" + +#: ./doc/security-guide/ch042_database-overview.xml6(title) +msgid "OpenStack Database Access Model" +msgstr "" + +#: ./doc/security-guide/ch042_database-overview.xml7(para) +msgid "" +"All of the services within an OpenStack project access a single database. " +"There are presently no reference policies for creating table or row based " +"access restrictions to the database." +msgstr "" + +#: ./doc/security-guide/ch042_database-overview.xml8(para) +msgid "" +"There are no general provisions for granular control of database operations " +"in OpenStack. Access and privileges are granted simply based on whether a " +"node has access to the database or not.  In this scenario, nodes with access" +" to the database may have full privileges to DROP, INSERT, or UPDATE " +"functions." +msgstr "" + +#: ./doc/security-guide/ch042_database-overview.xml10(title) +msgid "Granular Access Control" +msgstr "" + +#: ./doc/security-guide/ch042_database-overview.xml11(para) +msgid "" +"By default, each of the OpenStack services and their processes access the " +"database using a shared set of credentials. This makes auditing database " +"operations and revoking access privileges from a service and its processes " +"to the database particularly difficult." +msgstr "" + +#: ./doc/security-guide/ch042_database-overview.xml21(title) +#: ./doc/security-guide/ch042_database-overview.xml96(title) +msgid "Nova Conductor" +msgstr "" + +#: ./doc/security-guide/ch042_database-overview.xml22(para) +msgid "" +"The compute nodes are the least trusted of the services in OpenStack because" +" they host tenant instances. The nova-" +"conductor service has been introduced to serve as a database " +"proxy, acting as an intermediary between the compute nodes and the database." +" We discuss its ramifications later in this chapter." +msgstr "" + +#: ./doc/security-guide/ch042_database-overview.xml23(para) +msgid "We strongly recommend:" +msgstr "" + +#: ./doc/security-guide/ch042_database-overview.xml25(para) +msgid "All database communications be isolated to a management network" +msgstr "" + +#: ./doc/security-guide/ch042_database-overview.xml28(para) +msgid "Securing communications using SSL" +msgstr "" + +#: ./doc/security-guide/ch042_database-overview.xml31(para) +msgid "" +"Creating unique database user accounts per OpenStack service endpoint " +"(illustrated below)" +msgstr "" + +#: ./doc/security-guide/ch042_database-overview.xml47(title) +msgid "Database Authentication and Access Control" +msgstr "" + +#: ./doc/security-guide/ch042_database-overview.xml48(para) +msgid "" +"Given the risks around access to the database, we strongly recommend that " +"unique database user accounts be created per node needing access to the " +"database. Doing this facilitates better analysis and auditing for ensuring " +"compliance or in the event of a compromise of a node allows you to isolate " +"the compromised host by removing access for that node to the database upon " +"detection. When creating these per service endpoint database user accounts, " +"care should be taken to ensure that they are configured to require SSL.  " +"Alternatively, for increased security it is recommended that the database " +"accounts be configured using X.509 certificate authentication in addition to" +" usernames and passwords." +msgstr "" + +#: ./doc/security-guide/ch042_database-overview.xml50(title) +msgid "Privileges" +msgstr "" + +#: ./doc/security-guide/ch042_database-overview.xml51(para) +msgid "" +"A separate database administrator (DBA) account should be created and " +"protected that has full privileges to create/drop databases, create user " +"accounts, and update user privileges. This simple means of separation of " +"responsibility helps prevent accidental misconfiguration, lowers risk and " +"lowers scope of compromise." +msgstr "" + +#: ./doc/security-guide/ch042_database-overview.xml52(para) +msgid "" +"The database user accounts created for the OpenStack services and for each " +"node should have privileges limited to just the database relevant to the " +"service where the node is a member." +msgstr "" + +#: ./doc/security-guide/ch042_database-overview.xml56(title) +msgid "Require User Accounts to Require SSL Transport" +msgstr "" + +#: ./doc/security-guide/ch042_database-overview.xml58(title) +#: ./doc/security-guide/ch042_database-overview.xml75(title) +msgid "Configuration Example #1: (MySQL)" +msgstr "" + +#: ./doc/security-guide/ch042_database-overview.xml63(title) +#: ./doc/security-guide/ch042_database-overview.xml82(title) +msgid "Configuration Example #2: (PostgreSQL)" +msgstr "" + +#: ./doc/security-guide/ch042_database-overview.xml64(para) +msgid "In file pg_hba.conf:" +msgstr "" + +#: ./doc/security-guide/ch042_database-overview.xml67(para) +msgid "" +"Note this command only adds the ability to communicate over SSL and is non-" +"exclusive. Other access methods that may allow unencrypted transport should " +"be disabled so that SSL is the sole access method." +msgstr "" + +#: ./doc/security-guide/ch042_database-overview.xml68(para) +msgid "" +"The 'md5' parameter defines the authentication method as a hashed password. " +"We provide a secure authentication example in the section below." +msgstr "" + +#: ./doc/security-guide/ch042_database-overview.xml72(title) +msgid "Authentication with X.509 Certificates" +msgstr "" + +#: ./doc/security-guide/ch042_database-overview.xml73(para) +msgid "" +"Security may be enhanced by requiring X.509 client certificates for " +"authentication.  Authenticating to the database in this manner provides " +"greater identity assurance of the client making the connection to the " +"database and ensures that the communications are encrypted." +msgstr "" + +#: ./doc/security-guide/ch042_database-overview.xml88(title) +msgid "OpenStack Service Database Configuration" +msgstr "" + +#: ./doc/security-guide/ch042_database-overview.xml89(para) +msgid "" +"If your database server is configured to require X.509 certificates for " +"authentication you will need to specify the appropriate SQLAlchemy query " +"parameters for the database backend. These parameters specify the " +"certificate, private key, and certificate authority information for use with" +" the initial connection string." +msgstr "" + +#: ./doc/security-guide/ch042_database-overview.xml90(para) +msgid "" +"Example of an :sql_connection string for X.509 " +"certificate authentication to MySQL:" +msgstr "" + +#: ./doc/security-guide/ch042_database-overview.xml97(para) +msgid "" +"OpenStack Compute offers a sub-service called nova-conductor which proxies database connections, with the " +"primary purpose of having the nova compute nodes interfacing with " +"nova-conductor to meet data " +"persistence needs as opposed to directly communicating with the database." +msgstr "" + +#: ./doc/security-guide/ch042_database-overview.xml98(para) +msgid "" +"Nova-conductor receives requests over RPC and performs actions on behalf of " +"the calling service without granting granular access to the database, its " +"tables, or data within. Nova-conductor essentially abstracts direct database" +" access away from compute nodes." +msgstr "" + +#: ./doc/security-guide/ch042_database-overview.xml99(para) +msgid "" +"This abstraction offers the advantage of restricting services to executing " +"methods with parameters, similar to stored procedures, preventing a large " +"number of systems from directly accessing or modifying database data. This " +"is accomplished without having these procedures stored or executed within " +"the context or scope of the database itself, a frequent criticism of typical" +" stored procedures." +msgstr "" + +#: ./doc/security-guide/ch042_database-overview.xml107(para) +msgid "" +"Unfortunately, this solution complicates the task of more fine-grained " +"access control and the ability to audit data access. Because the nova-conductor service receives requests " +"over RPC, it highlights the importance of improving the security of " +"messaging. Any node with access to the message queue may execute these " +"methods provided by the nova-" +"conductor and effectively modifying the database." +msgstr "" + +#: ./doc/security-guide/ch042_database-overview.xml108(para) +msgid "" +"Finally, it should be noted that as of the Grizzly release, gaps exist where" +" nova-conductor is not used " +"throughout OpenStack Compute. Depending on one's configuration, the use of " +"nova-conductor may not allow " +"deployers to avoid the necessity of providing database GRANTs to individual " +"compute host systems." +msgstr "" + +#: ./doc/security-guide/ch042_database-overview.xml109(para) +msgid "" +"Note, as nova-conductor only " +"applies to OpenStack Compute, direct database access from compute hosts may " +"still be necessary for the operation of other OpenStack components such as " +"Telemetry (Ceilometer), Networking, and Block Storage." +msgstr "" + +#: ./doc/security-guide/ch042_database-overview.xml110(para) +msgid "" +"Implementors should weigh the benefits and risks of both configurations " +"before enabling or disabling the nova-" +"conductor service. We are not yet prepared to recommend the use" +" of nova-conductor in the Grizzly" +" release. However, we do believe that this recommendation will change as " +"additional features are added into OpenStack." +msgstr "" + +#: ./doc/security-guide/ch042_database-overview.xml111(para) +msgid "" +"To disable the nova-conductor, " +"place the following into your nova.conf file (on your " +"compute hosts):" +msgstr "" + +#: ./doc/security-guide/ch024_authentication.xml3(title) +msgid "Identity" +msgstr "" + +#: ./doc/security-guide/ch024_authentication.xml4(para) +msgid "" +"The OpenStack Identity Service (Keystone) supports multiple methods of " +"authentication, including username & password, LDAP, and external " +"authentication methods.  Upon successful authentication, The Identity " +"Service provides the user with an authorization token used for subsequent " +"service requests." +msgstr "" + +#: ./doc/security-guide/ch024_authentication.xml5(para) +msgid "" +"Transport Layer Security TLS/SSL provides authentication between services " +"and persons using X.509 certificates.  Although the default mode for SSL is " +"server-side only authentication, certificates may also be used for client " +"authentication." +msgstr "" + +#: ./doc/security-guide/ch024_authentication.xml7(title) +msgid "Authentication" +msgstr "" + +#: ./doc/security-guide/ch024_authentication.xml9(title) +msgid "Invalid Login Attempts" +msgstr "" + +#: ./doc/security-guide/ch024_authentication.xml10(para) +msgid "" +"The Identity Service does not provide a method to limit access to accounts " +"after repeated unsuccessful login attempts. Repeated failed login attempts " +"are likely brute-force attacks (Refer figure Attack-types). This is a more " +"significant issue in Public clouds." +msgstr "" + +#: ./doc/security-guide/ch024_authentication.xml11(para) +msgid "" +"Prevention is possible by using an external authentication system that " +"blocks out an account after some configured number of failed login attempts." +" The account then may only be unlocked with further side-channel " +"intervention." +msgstr "" + +#: ./doc/security-guide/ch024_authentication.xml12(para) +msgid "" +"If prevention is not an option, detection can be used to mitigate " +"damage.Detection involves frequent review of access control logs to identify" +" unauthorized attempts to access accounts. Possible remediation would " +"include reviewing the strength of the user password, or blocking the network" +" source of the attack via firewall rules. Firewall rules on the keystone " +"server that restrict the number of connections could be used to reduce the " +"attack effectiveness, and thus dissuade the attacker." +msgstr "" + +#: ./doc/security-guide/ch024_authentication.xml13(para) +msgid "" +"In addition, it is useful to examine account activity for unusual login " +"times and suspicious actions, with possibly disable the account. Often times" +" this approach is taken by credit card providers for fraud detection and " +"alert." +msgstr "" + +#: ./doc/security-guide/ch024_authentication.xml16(title) +msgid "Multi-factor Authentication" +msgstr "" + +#: ./doc/security-guide/ch024_authentication.xml17(para) +msgid "" +"Employ multi-factor authentication for network access to privileged user " +"accounts. The Identity Service supports external authentication services " +"through the Apache web server that can provide this functionality. Servers " +"may also enforce client-side authentication using certificates." +msgstr "" + +#: ./doc/security-guide/ch024_authentication.xml18(para) +msgid "" +"This recommendation provides insulation from brute force, social " +"engineering, and both spear and mass phishing attacks that may compromise " +"administrator passwords." +msgstr "" + +#: ./doc/security-guide/ch024_authentication.xml22(title) +msgid "Authentication Methods" +msgstr "" + +#: ./doc/security-guide/ch024_authentication.xml24(title) +msgid "Internally Implemented Authentication Methods" +msgstr "" + +#: ./doc/security-guide/ch024_authentication.xml25(para) +msgid "" +"The Identity Service can store user credentials in an SQL Database, or may " +"use an LDAP-compliant directory server. The Identity database may be " +"separate from databases used by other OpenStack services to reduce the risk " +"of a compromise of the stored credentials." +msgstr "" + +#: ./doc/security-guide/ch024_authentication.xml26(para) +msgid "" +"When authentication is provided via username and password, the Identity " +"Service does not enforce policies on password strength, expiration, or " +"failed authentication attempts as recommended by NIST Special Publication " +"800-118 (draft). Organizations that desire to enforce stronger password " +"policies should consider using Keystone Identity Service Extensions or " +"external authentication services." +msgstr "" + +#: ./doc/security-guide/ch024_authentication.xml27(para) +msgid "" +"LDAP simplifies integration of Identity authentication into an " +"organization's existing directory service and user account management " +"processes." +msgstr "" + +#: ./doc/security-guide/ch024_authentication.xml28(para) +msgid "" +"Authentication and authorization policy in OpenStack may be delegated to an " +"external LDAP server. A typical use case is an organization that seeks to " +"deploy a private cloud and already has a database of employees, the users. " +"This may be in an LDAP system. Using LDAP as a source of authority " +"authentication, requests to Identity Service are delegated to the LDAP " +"service, which will authorize or deny requests based on locally set " +"policies. A token is generated on successful authentication." +msgstr "" + +#: ./doc/security-guide/ch024_authentication.xml29(para) +msgid "" +"Note that if the LDAP system has attributes defined for the user such as " +"admin, finance, HR etc, these must be mapped into roles and groups within " +"Identity for use by the various OpenStack services. The " +"etc/keystone.conf file provides the mapping from the " +"LDAP attributes to Identity attributes." +msgstr "" + +#: ./doc/security-guide/ch024_authentication.xml30(para) +msgid "" +"The Identity Service MUST NOT be allowed " +"to write to LDAP services used for authentication outside of the OpenStack " +"deployment as this would allow a sufficiently privileged keystone user to " +"make changes to the LDAP directory. This would allow privilege escalation " +"within the wider organization or facilitate unauthorized access to other " +"information and resources. In such a deployment, user provisioning would be " +"out of the realm of the OpenStack deployment." +msgstr "" + +#: ./doc/security-guide/ch024_authentication.xml32(para) +msgid "" +"There is an OpenStack Security " +"Note (OSSN) regarding keystone.conf permissions." +msgstr "" + +#: ./doc/security-guide/ch024_authentication.xml33(para) +msgid "" +"There is an OpenStack Security " +"Note (OSSN) regarding potential DoS attacks." +msgstr "" + +#: ./doc/security-guide/ch024_authentication.xml37(title) +msgid "External Authentication Methods" +msgstr "" + +#: ./doc/security-guide/ch024_authentication.xml38(para) +msgid "" +"Organizations may desire to implement external authentication for " +"compatibility with existing authentication services or to enforce stronger " +"authentication policy requirements. Although passwords are the most common " +"form of authentication, they can be compromised through numerous methods, " +"including keystroke logging and password compromise. External authentication" +" services can provide alternative forms of authentication that minimize the " +"risk from weak passwords." +msgstr "" + +#: ./doc/security-guide/ch024_authentication.xml39(para) +msgid "These include:" +msgstr "" + +#: ./doc/security-guide/ch024_authentication.xml41(para) +msgid "" +"Password Policy Enforcement: Requires user passwords to conform to minimum " +"standards for length, diversity of characters, expiration, or failed login " +"attempts." +msgstr "" + +#: ./doc/security-guide/ch024_authentication.xml44(para) +msgid "" +"Multi-factor authentication: The authentication service requires the user to" +" provide information based on something they have, such as a one-time " +"password token or X.509 certificate, and something they know, such as a " +"password." +msgstr "" + +#: ./doc/security-guide/ch024_authentication.xml51(para) +msgid "Kerberos" +msgstr "" + +#: ./doc/security-guide/ch024_authentication.xml57(title) +msgid "Authorization" +msgstr "" + +#: ./doc/security-guide/ch024_authentication.xml58(para) +msgid "" +"The Identity Service supports the notion of groups and roles. Users belong " +"to groups. A group has a list of roles. OpenStack services reference the " +"roles of the user attempting to access the service. The OpenStack policy " +"enforcer middleware takes into consideration the policy rule associated with" +" each resource and the user's group/roles and tenant association to " +"determine if he/she has access to the requested resource." +msgstr "" + +#: ./doc/security-guide/ch024_authentication.xml59(para) +msgid "" +"The Policy enforcement middleware enables fine-grained access control to " +"OpenStack resources. Only admin users can provision new users and have " +"access to various management functionality. The cloud tenant would be able " +"to only spin up instances, attach volumes, etc." +msgstr "" + +#: ./doc/security-guide/ch024_authentication.xml61(title) +msgid "Establish Formal Access Control Policies" +msgstr "" + +#: ./doc/security-guide/ch024_authentication.xml62(para) +msgid "" +"Prior to configuring roles, groups, and users, document your required access" +" control policies for the OpenStack installation. The policies should be " +"consistent with any regulatory or legal requirements for the organization. " +"Future modifications to access control configuration should be done " +"consistently with the formal policies. The policies should include the " +"conditions and processes for creating, deleting, disabling, and enabling " +"accounts, and for assigning privileges to the accounts. Periodically review " +"the policies and ensure that configuration is in compliance with approved " +"policies." +msgstr "" + +#: ./doc/security-guide/ch024_authentication.xml65(title) +msgid "Service Authorization" +msgstr "" + +#: ./doc/security-guide/ch024_authentication.xml66(para) +msgid "" +"As described in the OpenStack Cloud Administrator " +"Guide, cloud administrators must define a user for each " +"service, with a role of Admin. This service user account provides the " +"service with the authorization to authenticate users." +msgstr "" + +#: ./doc/security-guide/ch024_authentication.xml67(para) +msgid "" +"The Compute and Object Storage services can be configured to use either the " +"\"tempAuth\" file or Identity Service to store authentication information. " +"The \"tempAuth\" solution MUST NOT be deployed in a production environment " +"since it stores passwords in plain text." +msgstr "" + +#: ./doc/security-guide/ch024_authentication.xml68(para) +msgid "" +"The Identity Service supports client authentication for SSL which may be " +"enabled. SSL client authentication provides an additional authentication " +"factor, in addition to the username / password, that provides greater " +"reliability on user identification. It reduces the risk of unauthorized " +"access when user names and passwords may be compromised.  However, there is " +"additional administrative overhead and cost to issue certificates to users " +"that may not be feasible in every deployment." +msgstr "" + +#: ./doc/security-guide/ch024_authentication.xml78(para) +msgid "" +"We recommend that you use client authentication with SSL for the " +"authentication of services to the Identity Service." +msgstr "" + +#: ./doc/security-guide/ch024_authentication.xml80(para) +msgid "" +"The cloud administrator should protect sensitive configuration files for " +"unauthorized modification. This can be achieved with mandatory access " +"control frameworks such as SELinux, including " +"/etc/keystone.conf and X.509 certificates." +msgstr "" + +#: ./doc/security-guide/ch024_authentication.xml82(para) +msgid "" +"For client authentication with SSL, you need to issue certificates. These " +"certificates can be signed by an external authority or by the cloud " +"administrator. OpenStack services by default check the signatures of " +"certificates and connections fail if the signature cannot be checked. If the" +" administrator uses self-signed certificates, the check might need to be " +"disabled. To disable these certificates, set insecure=False in " +"the [filter:authtoken] section in the " +"/etc/nova/api.paste.ini file. This setting also " +"disables certificates for other components." +msgstr "" + +#: ./doc/security-guide/ch024_authentication.xml96(title) +msgid "Administrative Users" +msgstr "" + +#: ./doc/security-guide/ch024_authentication.xml97(para) +msgid "" +"We recommend that admin users authenticate using Identity Service and an " +"external authentication service that supports 2-factor authentication, such " +"as a certificate.  This reduces the risk from passwords that may be " +"compromised. This recommendation is in compliance with NIST 800-53 IA-2(1) " +"guidance in the use of multi factor authentication for network access to " +"privileged accounts." +msgstr "" + +#: ./doc/security-guide/ch024_authentication.xml106(title) +msgid "End Users" +msgstr "" + +#: ./doc/security-guide/ch024_authentication.xml107(para) +msgid "" +"The Identity Service can directly provide end-user authentication, or can be" +" configured to use external authentication methods to conform to an " +"organization's security policies and requirements." +msgstr "" + +#: ./doc/security-guide/ch024_authentication.xml111(title) +msgid "Policies" +msgstr "" + +#: ./doc/security-guide/ch024_authentication.xml112(para) +msgid "" +"Each OpenStack service has a policy file in json format, called policy.json. The policy file specifies rules, and " +"the rule that governs each resource. A resource could be API access, the " +"ability to attach to a volume, or to fire up instances." +msgstr "" + +#: ./doc/security-guide/ch024_authentication.xml113(para) +msgid "" +"The policies can be updated by the cloud administrator to further control " +"access to the various resources. The middleware could also be further " +"customized. Note that your users must be assigned to groups/roles that you " +"refer to in your policies." +msgstr "" + +#: ./doc/security-guide/ch024_authentication.xml114(para) +msgid "Below is a snippet of the Block Storage service policy.json file." +msgstr "" + +#: ./doc/security-guide/ch024_authentication.xml133(para) +msgid "" +"Note the default rule specifies that the " +"user must be either an admin or the owner of the volume. It essentially says" +" only the owner of a volume or the admin may create/delete/update volumes. " +"Certain other operations such as managing volume types are accessible only " +"to admin users." +msgstr "" + +#: ./doc/security-guide/ch024_authentication.xml136(title) +msgid "Tokens" +msgstr "" + +#: ./doc/security-guide/ch024_authentication.xml137(para) +msgid "" +"Once a user is authenticated, a token is generated and used internally in " +"OpenStack for authorization and access. The default token lifespan is 24 " +"hours. It is recommended that this value be set lower but caution" +" needs to be taken as some internal services will need sufficient time to " +"complete their work. The cloud may not provide services if tokens expire too" +" early. An example of this would be the time needed by the Compute Service " +"to transfer a disk image onto the hypervisor for local caching." +msgstr "" + +#: ./doc/security-guide/ch024_authentication.xml138(para) +msgid "" +"The following example shows a PKI token. Note that, in practice, the token " +"id value is about 3500 bytes. We shorten it in this example." +msgstr "" + +#: ./doc/security-guide/ch024_authentication.xml153(para) +msgid "" +"Note that the token is often passed within the structure of a larger context" +" of an Identity Service response. These responses also provide a catalog of " +"the various OpenStack services. Each service is listed with its name, access" +" endpoints for internal, admin, and public access." +msgstr "" + +#: ./doc/security-guide/ch024_authentication.xml154(para) +msgid "" +"The Identity Service supports token revocation. This manifests as an API to " +"revoke a token, to list revoked tokens and individual OpenStack services " +"that cache tokens to query for the revoked tokens and remove them from their" +" cache and append the same to their list of cached revoked tokens." +msgstr "" + +#: ./doc/security-guide/ch024_authentication.xml157(title) +msgid "Future" +msgstr "" + +#: ./doc/security-guide/ch024_authentication.xml158(para) +msgid "" +"Domains are high-level containers for projects, users and groups. As such, " +"they can be used to centrally manage all Keystone-based identity components." +" With the introduction of account Domains, server, storage and other " +"resources can now be logically grouped into multiple Projects (previously " +"called Tenants) which can themselves be grouped under a master account-like " +"container. In addition, multiple users can be managed within an account " +"Domain and assigned roles that vary for each Project." +msgstr "" + +#: ./doc/security-guide/ch024_authentication.xml159(para) +msgid "" +"Keystone's V3 API supports multiple domains. Users of different domains may " +"be represented in different authentication backends and even have different " +"attributes that must be mapped to a single set of roles and privileges, that" +" are used in the policy definitions to access the various service resources." +msgstr "" + +#: ./doc/security-guide/ch024_authentication.xml160(para) +msgid "" +"Where a rule may specify access to only admin users and users belonging to " +"the tenant, the mapping may be trivial. In other scenarios the cloud " +"administrator may need to approve the mapping routines per tenant." +msgstr "" + +#: ./doc/security-guide/ch015_case-studies-management.xml9(title) +msgid "Case Studies: Management Interfaces" +msgstr "" + +#: ./doc/security-guide/ch015_case-studies-management.xml10(para) +msgid "" +"Previously we discussed typical OpenStack management interfaces and " +"associated backplane issues. We will now approach these issues by returning " +"to our Alice and Bob case study. Specifically, we will look into how both " +"Alice and Bob will address:" +msgstr "" + +#: ./doc/security-guide/ch015_case-studies-management.xml16(para) +msgid "Cloud Administration" +msgstr "" + +#: ./doc/security-guide/ch015_case-studies-management.xml19(para) +msgid "Self Service" +msgstr "" + +#: ./doc/security-guide/ch015_case-studies-management.xml22(para) +msgid "Data Replication & Recovery" +msgstr "" + +#: ./doc/security-guide/ch015_case-studies-management.xml25(para) +msgid "SLA & Security Monitoring." +msgstr "" + +#: ./doc/security-guide/ch015_case-studies-management.xml30(para) +msgid "" +"When building her private cloud, while air-gapped, Alice still needs to " +"consider her service management interfaces. Before deploying her private " +"cloud, Alice has completed her system documentation. Specifically she has " +"identified which OpenStack services will exist in each security domain. From" +" there Alice has further restricted access to management interfaces by " +"deploying a combination of IDS, SSL encryption, and physical network " +"isolation. Additionally, Alice requires high availability and redundant " +"services. Thus, Alice sets up redundant infrastructure for various OpenStack" +" API services." +msgstr "" + +#: ./doc/security-guide/ch015_case-studies-management.xml31(para) +msgid "" +"Alice also needs to provide assurances that the physical servers and " +"hypervisors have been built from a known secure state into a well-defined " +"configuration. To enable this, Alice uses a combination of a Configuration " +"Management platform to configure each machine according to the standards and" +" regulations she must comply with. It will also enable Alice to report " +"periodically on the state of her cloud and perform remediation to a known " +"state should anything be out of the ordinary. Additionally, Alice provides " +"hardware assurances by using a PXE system to build her nodes from a known " +"set of base images. During the boot process, Alice provides further " +"assurances by enabling Intel TXT and related trusted boot technologies " +"provided by the hardware." +msgstr "" + +#: ./doc/security-guide/ch015_case-studies-management.xml35(para) +msgid "" +"As a public cloud provider, Bob is concerned with both the continuous " +"availability of management interfaces and the security of transactions to " +"the management interfaces. To that end Bob implements multiple redundant " +"OpenStack API endpoints for the services his cloud will run. Additionally on" +" the public network Bob uses SSL to encrypt all transactions between his " +"customers and his cloud interfaces. To isolate his cloud operations Bob has " +"physically isolated his management, instance migration, and storage " +"networks." +msgstr "" + +#: ./doc/security-guide/ch015_case-studies-management.xml36(para) +msgid "" +"To ease scaling and reduce management overhead Bob implements a " +"configuration management system. For customer data assurances, Bob offers a " +"backup as a service product as requirements will vary between customers. " +"Finally, Bob does not provide a \"baremetal\" or the ability to schedule an " +"entire node, so to reduce management overhead and increase operational " +"efficiency Bob does not implement any node boot time security." +msgstr "" + +#: ./doc/security-guide/ch018_case-studies-pkissl.xml3(title) +msgid "Case Studies: PKI and Certificate Management" +msgstr "" + +#: ./doc/security-guide/ch018_case-studies-pkissl.xml4(para) +msgid "" +"In this case study we discuss how Alice and Bob would address deployment of " +"PKI certification authorities (CA) and certificate management." +msgstr "" + +#: ./doc/security-guide/ch018_case-studies-pkissl.xml7(para) +msgid "" +"Alice as a cloud architect within a government agency knows that her agency " +"operates its own certification authority. Alice contacts the PKI office in " +"her agency that manages her PKI and certificate issuance. Alice obtains " +"certificates issued by this CA and configures the services within both the " +"public and management security domains to use these certificates. Since " +"Alice's OpenStack deployment exists entirely on a disconnected from the " +"Internet network, she makes sure to remove all default CA bundles that " +"contain external public CA providers to ensure the OpenStack services only " +"accept client certificates issued by her agency's CA." +msgstr "" + +#: ./doc/security-guide/ch018_case-studies-pkissl.xml11(para) +msgid "" +"Bob is architecting a public cloud and needs to ensure that the publicly " +"facing OpenStack services are using certificates issued by a major public " +"CA. Bob acquires certificates for his public OpenStack services and " +"configures the services to use PKI and SSL and includes the public CAs in " +"his trust bundle for the services. Additionally, Bob also wants to further " +"isolate the internal communications amongst the services within the " +"management security domain. Bob contacts the team within his organization " +"that is responsible for managing his organizations PKI and issuance of " +"certificates using their own internal CA. Bob obtains certificates issued by" +" this internal CA and configures the services that communicate within the " +"management security domain to use these certificates and configures the " +"services to only accept client certificates issued by his internal CA." +msgstr "" + +#. When image changes, this message will be marked fuzzy or untranslated for +#. you. +#. It doesn't matter what you translate it to: it's not used at all. +#: ./doc/security-guide/ch031_neutron-architecture.xml24(None) +#: ./doc/security-guide/ch031_neutron-architecture.xml27(None) +msgid "" +"@@image: 'static/sdn-connections.png'; md5=3fb0f3e2bea0784fea8832526d2b2832" +msgstr "" + +#. When image changes, this message will be marked fuzzy or untranslated for +#. you. +#. It doesn't matter what you translate it to: it's not used at all. +#: ./doc/security-guide/ch031_neutron-architecture.xml36(None) +#: ./doc/security-guide/ch031_neutron-architecture.xml39(None) +msgid "" +"@@image: 'static/1aa-network-domains-diagram.png'; " +"md5=57ae4448b05a3852180f75f3995711b9" +msgstr "" + +#: ./doc/security-guide/ch031_neutron-architecture.xml3(title) +msgid "Networking Architecture" +msgstr "" + +#: ./doc/security-guide/ch031_neutron-architecture.xml4(para) +msgid "" +"OpenStack Networking is a standalone service that often involves deploying " +"several processes across a number of nodes. These processes interact with " +"each other and with other OpenStack services. The main process of the " +"OpenStack Networking service is neutron-server, a Python daemon that exposes" +" the OpenStack Networking API and passes tenant requests to a suite of " +"plugins for additional processing." +msgstr "" + +#: ./doc/security-guide/ch031_neutron-architecture.xml5(para) +msgid "OpenStack Networking components encompasses the following elements:" +msgstr "" + +#: ./doc/security-guide/ch031_neutron-architecture.xml7(para) +msgid "" +"neutron server (neutron-" +"server and neutron-*-plugin): This service runs" +" on the network node to service the Networking API and its extensions. It " +"also enforces the network model and IP addressing of each port. The neutron-" +"server and plugin agents require access to a database for persistent storage" +" and access to a message queue for inter-communication." +msgstr "" + +#: ./doc/security-guide/ch031_neutron-architecture.xml10(para) +msgid "" +"plugin agent " +"(neutron-*-agent): Runs on each compute node to manage " +"local virtual switch (vswitch) configuration. The agents to be run will " +"depend on which plugin you are using. This service requires message queue " +"access. Optional depending on plugin." +msgstr "" + +#: ./doc/security-guide/ch031_neutron-architecture.xml13(para) +msgid "" +"DHCP agent (neutron-dhcp-" +"agent): Provides DHCP services to tenant networks. This agent is " +"the same across all plugins and is responsible for maintaining DHCP " +"configuration. The neutron-dhcp-agent requires message queue access." +msgstr "" + +#: ./doc/security-guide/ch031_neutron-architecture.xml16(para) +msgid "" +"l3 agent " +"(neutron-l3-agent): Provides L3/NAT forwarding for " +"external network access of VMs on tenant networks. Requires message queue " +"access. Optional depending on plugin." +msgstr "" + +#: ./doc/security-guide/ch031_neutron-architecture.xml19(para) +msgid "" +"network provider services (SDN " +"server/services). Provide additional networking services that are provided " +"to tenant networks. These SDN services may interact with the neutron-server," +" neutron-plugin, and/or plugin-agents via REST APIs or other communication " +"channels." +msgstr "" + +#: ./doc/security-guide/ch031_neutron-architecture.xml22(para) +msgid "" +"The figure that follows provides an architectural and networking flow " +"diagram of the OpenStack Networking components:" +msgstr "" + +#: ./doc/security-guide/ch031_neutron-architecture.xml31(title) +msgid "OS Networking Service placement on Physical Servers" +msgstr "" + +#: ./doc/security-guide/ch031_neutron-architecture.xml32(para) +msgid "" +"In this guide, we focus primarily on a standard architecture that includes a" +" cloud controller host, a network " +"host, and a set of compute hypervisors for running VMs." +msgstr "" + +#: ./doc/security-guide/ch031_neutron-architecture.xml34(title) +msgid "Network Connectivity of Physical Servers" +msgstr "" + +#: ./doc/security-guide/ch031_neutron-architecture.xml42(para) +msgid "" +"A standard OpenStack Networking setup has up to four distinct physical data " +"center networks:" +msgstr "" + +#: ./doc/security-guide/ch031_neutron-architecture.xml44(para) +msgid "" +"Management network Used for internal " +"communication between OpenStack Components. The IP addresses on this network" +" should be reachable only within the data center and is considered the " +"Management Security Domain." +msgstr "" + +#: ./doc/security-guide/ch031_neutron-architecture.xml47(para) +msgid "" +"Guest network Used for VM data " +"communication within the cloud deployment. The IP addressing requirements of" +" this network depend on the OpenStack Networking plugin in use and the " +"network configuration choices of the virtual networks made by the tenant. " +"This network is considered the Guest Security Domain." +msgstr "" + +#: ./doc/security-guide/ch031_neutron-architecture.xml50(para) +msgid "" +"External network Used to provide VMs with" +" Internet access in some deployment scenarios. The IP addresses on this " +"network should be reachable by anyone on the Internet and is considered to " +"be in the Public Security Domain." +msgstr "" + +#: ./doc/security-guide/ch031_neutron-architecture.xml53(para) +msgid "" +"API network Exposes all OpenStack APIs, " +"including the OpenStack Networking API, to tenants. The IP addresses on this" +" network should be reachable by anyone on the Internet. This may be the same" +" network as the external network, as it is possible to create a subnet for " +"the external network that uses IP allocation ranges to use only less than " +"the full range of IP addresses in an IP block. This network is considered " +"the Public Security Domain." +msgstr "" + +#: ./doc/security-guide/ch031_neutron-architecture.xml56(para) +msgid "" +"For additional information see the Networking chapter in" +" the OpenStack Cloud Administrator Guide." +msgstr "" + +#: ./doc/security-guide/ch047_data-encryption.xml3(title) +msgid "Data Encryption" +msgstr "" + +#: ./doc/security-guide/ch047_data-encryption.xml4(para) +msgid "" +"The option exists for implementors to encrypt tenant data wherever it is " +"stored on disk or transported over a network. This is above and beyond the " +"general recommendation that users encrypt their own data before sending it " +"to their provider." +msgstr "" + +#: ./doc/security-guide/ch047_data-encryption.xml5(para) +msgid "" +"The importance of encrypting data on behalf of tenants is largely related to" +" the risk assumed by a provider that an attacker could access tenant data. " +"There may be requirements here in government, as well as requirements per-" +"policy, in private contract, or even in case law in regard to private " +"contracts for public cloud providers. It is recommended that a risk " +"assessment and legal consul advised before choosing tenant encryption " +"policies." +msgstr "" + +#: ./doc/security-guide/ch047_data-encryption.xml6(para) +msgid "" +"Per-instance or per-object encryption is preferable over, in descending " +"order, over per-project, per-tenant, per-host, and per-cloud aggregations. " +"This recommendation is inverse to the complexity and difficulty of " +"implementation. Presently, in some projects it is difficult or impossible to" +" implement encryption as loosely granular as even per-tenant. We recommend " +"implementors make a best-effort in encrypting tenant data." +msgstr "" + +#: ./doc/security-guide/ch047_data-encryption.xml7(para) +msgid "" +"Often, data encryption relates positively to the ability to reliably destroy" +" tenant and per-instance data, simply by throwing away the keys. It should " +"be noted that in doing so, it becomes of great importance to destroy those " +"keys in a reliable and secure manner." +msgstr "" + +#: ./doc/security-guide/ch047_data-encryption.xml8(para) +msgid "Opportunities to encrypt data for users are present:" +msgstr "" + +#: ./doc/security-guide/ch047_data-encryption.xml10(para) +msgid "Object Storage objects" +msgstr "" + +#: ./doc/security-guide/ch047_data-encryption.xml13(para) +msgid "Block Storage volumes & Instance Ephemeral Filesystems" +msgstr "" + +#: ./doc/security-guide/ch047_data-encryption.xml16(para) +msgid "Network data" +msgstr "" + +#: ./doc/security-guide/ch047_data-encryption.xml20(title) +msgid "Object Storage Objects" +msgstr "" + +#: ./doc/security-guide/ch047_data-encryption.xml21(para) +msgid "" +"The ability to encrypt objects in Object Storage is presently limited to " +"disk-level encryption per node. However, there does exist third-party " +"extensions and modules for per-object encryption. These modules have been " +"proposed upstream, but have not per this writing been formally accepted. " +"Below are some pointers: " +msgstr "" + +#: ./doc/security-guide/ch047_data-encryption.xml22(link) +msgid "https://github.com/Mirantis/swift-encrypt" +msgstr "" + +#: ./doc/security-guide/ch047_data-encryption.xml23(link) +msgid "" +"http://www.mirantis.com/blog/on-disk-encryption-prototype-for-openstack-" +"swift/" +msgstr "" + +#: ./doc/security-guide/ch047_data-encryption.xml26(title) +msgid "Block Storage Volumes & Instance Ephemeral Filesystems" +msgstr "" + +#: ./doc/security-guide/ch047_data-encryption.xml27(para) +msgid "" +"The ability to encrypt volumes depends on the service backends chosen. Some " +"backends may not support this at all." +msgstr "" + +#: ./doc/security-guide/ch047_data-encryption.xml28(para) +msgid "" +"As both block storage and compute support LVM backed storage, we can easily " +"provide an example applicable to both systems. In deployments using LVM, " +"encryption may be performed against the backing physical volumes. An " +"encrypted block device would be created using the standard Linux tools, with" +" the LVM physical volume (PV) created on top of the decrypted block device " +"using pvcreate. Then, the vgcreate or vgmodify tool may be used to add the " +"encrypted physical volume to an LVM volume group (VG)." +msgstr "" + +#: ./doc/security-guide/ch047_data-encryption.xml29(para) +msgid "" +"A feature aimed for the Havana release provides encryption of the VM's data " +"before it is written to disk. This allows the privacy of data to be " +"maintained while residing on the storage device. The idea is similar to how " +"self-encrypting drives work. This feature presents a normal block storage " +"device to the VM but encrypts the bytes in the virtualization host before " +"writing them to the disk. The block server operates exactly as it does when " +"reading and writing unencrypted blocks, except special handling will be " +"required for Block Storage features such as snapshots and live migration.  " +"Note that this feature uses an independent key manager." +msgstr "" + +#: ./doc/security-guide/ch047_data-encryption.xml32(title) +msgid "Network Data" +msgstr "" + +#: ./doc/security-guide/ch047_data-encryption.xml33(para) +msgid "" +"Tenant data for compute could be encrypted over IPSec or other tunnels. This" +" is not functionality common or standard in OpenStack, but is an option " +"available to motivated and interested implementors." +msgstr "" + +#: ./doc/security-guide/ch047_data-encryption.xml37(para) +msgid "" +"Block storage supports a variety of mechanisms for supplying mountable " +"volumes. It is outside the scope of this guide to specify recommendations " +"for each Block Storage backend driver. For the purpose of performance, many " +"storage protocols are unencrypted. Some protocols such as iSCSI can provide " +"authentication and encrypted sessions, it is our recommendation to enable " +"these features." +msgstr "" + +#. When image changes, this message will be marked fuzzy or untranslated for +#. you. +#. It doesn't matter what you translate it to: it's not used at all. +#: ./doc/security-guide/ch005_security-domains.xml24(None) +#: ./doc/security-guide/ch005_security-domains.xml27(None) +msgid "" +"@@image: 'static/untrusted_trusted.png'; " +"md5=a582dac2ad0b3f439fd4b08386853056" +msgstr "" + +#. When image changes, this message will be marked fuzzy or untranslated for +#. you. +#. It doesn't matter what you translate it to: it's not used at all. +#: ./doc/security-guide/ch005_security-domains.xml55(None) +#: ./doc/security-guide/ch005_security-domains.xml58(None) +msgid "" +"@@image: 'static/bridging_security_domains_1.png'; " +"md5=0d5ca26c51882ce3253405e91a597715" +msgstr "" + +#. When image changes, this message will be marked fuzzy or untranslated for +#. you. +#. It doesn't matter what you translate it to: it's not used at all. +#: ./doc/security-guide/ch005_security-domains.xml63(None) +#: ./doc/security-guide/ch005_security-domains.xml66(None) +msgid "" +"@@image: 'static/bridging_domains_clouduser.png'; " +"md5=17c8a233ee7de17d2f600c7f6f6afe24" +msgstr "" + +#. When image changes, this message will be marked fuzzy or untranslated for +#. you. +#. It doesn't matter what you translate it to: it's not used at all. +#: ./doc/security-guide/ch005_security-domains.xml95(None) +#: ./doc/security-guide/ch005_security-domains.xml98(None) +msgid "" +"@@image: 'static/threat_actors.png'; md5=114c2f9bd9d0319bdd83f9e229d44649" +msgstr "" + +#. When image changes, this message will be marked fuzzy or untranslated for +#. you. +#. It doesn't matter what you translate it to: it's not used at all. +#: ./doc/security-guide/ch005_security-domains.xml116(None) +#: ./doc/security-guide/ch005_security-domains.xml119(None) +msgid "" +"@@image: 'static/high-capability.png'; md5=b7ab599c8b40558a52c0ca86aad89741" +msgstr "" + +#: ./doc/security-guide/ch005_security-domains.xml3(title) +msgid "Security Boundaries and Threats" +msgstr "" + +#: ./doc/security-guide/ch005_security-domains.xml4(para) +msgid "" +"A cloud can be abstracted as a collection of logical components by virtue of" +" their function, users, and shared security concerns, which we call security" +" domains. Threat actors and vectors are classified based on their motivation" +" and access to resources. Our goal is to provide you a sense of the security" +" concerns with respect to each domain depending on your risk/vulnerability " +"protection objectives." +msgstr "" + +#: ./doc/security-guide/ch005_security-domains.xml6(title) +msgid "Security Domains" +msgstr "" + +#: ./doc/security-guide/ch005_security-domains.xml7(para) +msgid "" +"A security domain comprises users, applications, servers or networks that " +"share common trust requirements and expectations within a system. Typically " +"they have the same authentication and authorization (AuthN/Z) requirements " +"and users." +msgstr "" + +#: ./doc/security-guide/ch005_security-domains.xml8(para) +msgid "" +"Although you may desire to break these domains down further (we later " +"discuss where this may be appropriate), we generally refer to four distinct " +"security domains which form the bare minimum that is required to deploy any " +"OpenStack cloud securely. These security domains are:" +msgstr "" + +#: ./doc/security-guide/ch005_security-domains.xml10(para) +#: ./doc/security-guide/ch005_security-domains.xml31(title) +msgid "Public" +msgstr "" + +#: ./doc/security-guide/ch005_security-domains.xml13(para) +#: ./doc/security-guide/ch005_security-domains.xml36(title) +msgid "Guest" +msgstr "" + +#: ./doc/security-guide/ch005_security-domains.xml16(para) +#: ./doc/security-guide/ch005_security-domains.xml41(title) +msgid "Management" +msgstr "" + +#: ./doc/security-guide/ch005_security-domains.xml19(para) +#: ./doc/security-guide/ch005_security-domains.xml46(title) +msgid "Data" +msgstr "" + +#: ./doc/security-guide/ch005_security-domains.xml22(para) +msgid "" +"We selected these security domains because they can be mapped independently " +"or combined to represent the majority of the possible areas of trust within " +"a given OpenStack deployment. For example, some deployment topologies " +"combine both guest and data domains onto one physical network versus others," +" which have these networks physically separated. In each case, the cloud " +"operator should be aware of the appropriate security concerns. Security " +"domains should be mapped out against your specific OpenStack deployment " +"topology. The domains and their trust requirements depend upon whether the " +"cloud instance is public, private, or hybrid." +msgstr "" + +#: ./doc/security-guide/ch005_security-domains.xml32(para) +msgid "" +"The public security domain is an entirely untrusted area of the cloud " +"infrastructure. It can refer to the Internet as a whole or simply to " +"networks over which you have no authority. Any data that transits this " +"domain with confidentiality or integrity requirements should be protected " +"using compensating controls." +msgstr "" + +#: ./doc/security-guide/ch005_security-domains.xml33(para) +msgid "" +"This domain should always be considered untrusted." +msgstr "" + +#: ./doc/security-guide/ch005_security-domains.xml37(para) +msgid "" +"Typically used for compute instance-to-instance traffic, the guest security " +"domain handles compute data generated by instances on the cloud but not " +"services that support the operation of the cloud, such as API calls." +msgstr "" + +#: ./doc/security-guide/ch005_security-domains.xml38(para) +msgid "" +"Public cloud providers and private cloud providers who do not have stringent" +" controls on instance use or who allow unrestricted internet access to VMs " +"should consider this domain to be untrusted. Private " +"cloud providers may want to consider this network as internal and therefore " +"trusted only if they have controls in place to assert " +"that they trust instances and all their tenants." +msgstr "" + +#: ./doc/security-guide/ch005_security-domains.xml42(para) +msgid "" +"The management security domain is where services interact. Sometimes " +"referred to as the \"control plane\", the networks in this domain transport " +"confidential data such as configuration parameters, usernames, and " +"passwords. Command and Control traffic typically resides in this domain, " +"which necessitates strong integrity requirements. Access to this domain " +"should be highly restricted and monitored. At the same time, this domain " +"should still employ all of the security best practices described in this " +"guide." +msgstr "" + +#: ./doc/security-guide/ch005_security-domains.xml43(para) +msgid "" +"In most deployments this domain is considered trusted. " +"However, when considering an OpenStack deployment, there are many systems " +"that bridge this domain with others, potentially reducing the level of trust" +" you can place on this domain. See for more information." +msgstr "" + +#: ./doc/security-guide/ch005_security-domains.xml47(para) +msgid "" +"The data security domain is concerned primarily with information pertaining " +"to the storage services within OpenStack. Much of the data that crosses this" +" network has high integrity and confidentiality requirements and depending " +"on the type of deployment there may also be strong availability " +"requirements." +msgstr "" + +#: ./doc/security-guide/ch005_security-domains.xml48(para) +msgid "" +"The trust level of this network is heavily dependent on deployment decisions" +" and as such we do not assign this any default level of trust." +msgstr "" + +#: ./doc/security-guide/ch005_security-domains.xml52(title) +msgid "Bridging Security Domains" +msgstr "" + +#: ./doc/security-guide/ch005_security-domains.xml53(para) +msgid "" +"A bridge is a component that exists inside more than " +"one security domain. Any component that bridges security domains with " +"different trust levels or authentication requirements must be carefully " +"configured. These bridges are often the weak points in network architecture." +" A bridge should always be configured to meet the security requirements of " +"the highest trust level of any of the domains it is bridging. In many cases " +"the security controls for bridges should be a primary concern due to the " +"likelihood of attack." +msgstr "" + +#: ./doc/security-guide/ch005_security-domains.xml61(para) +msgid "" +"The diagram above shows a compute node bridging the data and management " +"domains, as such the compute node should be configured to meet the security " +"requirements of the management domain. Similarly the API Endpoint in this " +"diagram is bridging the untrusted public domain and the management domain, " +"and should be configured to protect against attacks from the public domain " +"propagating through to the management domain." +msgstr "" + +#: ./doc/security-guide/ch005_security-domains.xml69(para) +msgid "" +"In some cases deployers may want to consider securing a bridge to a higher " +"standard than any of the domains in which it resides. Given the above " +"example of an API endpoint, an adversary could potentially target the API " +"endpoint from the public domain, leveraging it in the hopes of compromising " +"or gaining access to the management domain." +msgstr "" + +#: ./doc/security-guide/ch005_security-domains.xml70(para) +msgid "" +"The design of OpenStack is such that separation of security domains is " +"difficult - as core services will usually bridge at least two domains, " +"special consideration must be given when applying security controls to them." +msgstr "" + +#: ./doc/security-guide/ch005_security-domains.xml73(title) +msgid "Threat Classification, Actors and Attack Vectors" +msgstr "" + +#: ./doc/security-guide/ch005_security-domains.xml74(para) +msgid "" +"Most types of cloud deployment, public or private, are exposed to some form " +"of attack. In this chapter we categorize attackers and summarize potential " +"types of attacks in each security domain." +msgstr "" + +#: ./doc/security-guide/ch005_security-domains.xml76(title) +msgid "Threat Actors" +msgstr "" + +#: ./doc/security-guide/ch005_security-domains.xml77(para) +msgid "" +"A threat actor is an abstract way to refer to a class of adversary that you " +"may attempt to defend against. The more capable the actor, the more " +"expensive the security controls that are required for successful attack " +"mitigation and prevention. Security is a tradeoff between cost, usability " +"and defense. In some cases it will not be possible to secure a cloud " +"deployment against all of the threat actors we describe here. Those " +"deploying an OpenStack cloud will have to decide where the balance lies for " +"their deployment / usage." +msgstr "" + +#: ./doc/security-guide/ch005_security-domains.xml79(para) +msgid "" +"Intelligence Services — Considered by " +"this guide as the most capable adversary. Intelligence Services and other " +"state actors can bring tremendous resources to bear on a target. They have " +"capabilities beyond that of any other actor. It is very difficult to defend " +"against these actors without incredibly stringent controls in place, both " +"human and technical." +msgstr "" + +#: ./doc/security-guide/ch005_security-domains.xml82(para) +msgid "" +"Serious Organized Crime — Highly capable " +"and financially driven groups of attackers. Able to fund in-house exploit " +"development and target research. In recent years the rise of organizations " +"such as the Russian Business Network, a massive cyber-criminal enterprise " +"has demonstrated how cyber attacks have become a commodity. Industrial " +"espionage falls within the SOC group." +msgstr "" + +#: ./doc/security-guide/ch005_security-domains.xml85(para) +msgid "" +"Highly Capable Groups — This refers to " +"'Hacktivist' type organizations who are not typically commercially funded " +"but can pose a serious threat to service providers and cloud operators." +msgstr "" + +#: ./doc/security-guide/ch005_security-domains.xml88(para) +msgid "" +"Motivated Individuals — Acting alone, " +"these attackers come in many guises, such as rogue or malicious employees, " +"disaffected customers, or small-scale industrial espionage." +msgstr "" + +#: ./doc/security-guide/ch005_security-domains.xml91(para) +msgid "" +"Script Kiddies — Automated vulnerability " +"scanning/exploitation. Non-targeted attacks. Often only a nuisance, " +"compromise by one of these actors presents a major risk to an organization's" +" reputation." +msgstr "" + +#: ./doc/security-guide/ch005_security-domains.xml103(title) +msgid "Public / Private Considerations" +msgstr "" + +#: ./doc/security-guide/ch005_security-domains.xml104(para) +msgid "" +"Private clouds are typically deployed by enterprises or institutions inside " +"their networks and behind their firewalls. Enterprises will have strict " +"policies on what data is allowed to exit their network and may even have " +"different clouds for specific purposes. Users of a private cloud are " +"typically employees of the organization that owns the cloud and are able to " +"be held accountable for their actions. Employees often attend training " +"sessions before accessing the cloud and will likely take part in regular " +"scheduled security awareness training. Public clouds by contrast cannot make" +" any assertions about their users, cloud use-cases or user motivations. This" +" immediately pushes the guest security domain into a completely " +"untrusted state for public cloud providers." +msgstr "" + +#: ./doc/security-guide/ch005_security-domains.xml105(para) +msgid "" +"A notable difference in the attack surface of public clouds is that they " +"must provide internet access to their services. Instance connectivity, " +"access to files over the internet and the ability to interact with the cloud" +" controlling fabric such as the API endpoints and dashboard are must-haves " +"for the public cloud." +msgstr "" + +#: ./doc/security-guide/ch005_security-domains.xml106(para) +msgid "" +"Privacy concerns for public and private cloud users are typically " +"diametrically opposed. The data generated and stored in private clouds is " +"normally owned by the operator of the cloud, who is able to deploy " +"technologies such as data loss prevention (DLP) protection, file inspection," +" deep packet inspection and prescriptive firewalling. In contrast, privacy " +"is one of the primary barriers to adoption for the public cloud, as many of " +"these controls do not exist." +msgstr "" + +#: ./doc/security-guide/ch005_security-domains.xml109(title) +msgid "Outbound attacks and reputational risk" +msgstr "" + +#: ./doc/security-guide/ch005_security-domains.xml110(para) +msgid "" +"Careful consideration should be given to potential outbound abuse from a " +"cloud deployment.  Whether public or private, clouds tend to have lots of " +"resource available. An attacker who has established a point of presence " +"within the cloud, either through hacking in or via entitled access (rogue " +"employee), can bring these resources to bear against the internet at large. " +"Clouds with compute services make for ideal DDoS and brute force engines. " +"This is perhaps a more pressing issue for public clouds as their users are " +"largely unaccountable, and can quickly spin up numerous disposable instances" +" for outbound attacks.  Major damage can be inflicted upon a company's " +"reputation if it becomes known for hosting malicious software or launching " +"attacks on other networks. Methods of prevention include egress security " +"groups, outbound traffic inspection, customer education and awareness, and " +"fraud and abuse mitigation strategies." +msgstr "" + +#: ./doc/security-guide/ch005_security-domains.xml113(title) +msgid "Attack Types" +msgstr "" + +#: ./doc/security-guide/ch005_security-domains.xml114(para) +msgid "" +"The diagram shows the types of attacks that may be expected from the actors " +"described in the previous section. Note that there will always be exceptions" +" to this diagram but in general, this describes the sorts of attack that " +"could be typical for each actor." +msgstr "" + +#: ./doc/security-guide/ch005_security-domains.xml122(para) +msgid "" +"The prescriptive defense for each form of attack is beyond the scope of this" +" document. The above diagram can assist you in making an informed decision " +"about which types of threats, and threat actors, should be protected " +"against. For commercial public cloud deployments this might include " +"prevention against serious crime. For those deploying private clouds for " +"government use, more stringent protective mechanisms should be in place, " +"including carefully protected facilities and supply chains. In contrast " +"those standing up basic development or test environments will likely require" +" less restrictive controls (middle of the spectrum)." +msgstr "" + +#: ./doc/security-guide/ch035_case-studies-networking.xml3(title) +msgid "Case Studies: Networking" +msgstr "" + +#: ./doc/security-guide/ch035_case-studies-networking.xml4(para) +msgid "" +"In this case study we discuss how Alice and Bob would address providing " +"networking services to the user." +msgstr "" + +#: ./doc/security-guide/ch035_case-studies-networking.xml7(para) +msgid "" +"A key objective of Alice's cloud is to integrate with the existing auth " +"services and security resources. The key design parameters for this private " +"cloud are a limited scope of tenants, networks and workload type. This " +"environment can be designed to limit what available network resources are " +"available to the tenant and what are the various default quotas and security" +" policies are available. The network policy engine can be modified to " +"restrict creation and changes to network resources. In this environment, " +"Alice might want to leverage nova-network in the application of security " +"group polices on a per instance basis vs. Neutron's application of security " +"group polices on a per port basis. L2 isolation in this environment would " +"leverage VLAN tagging. The use of VLAN tags will allow great visibility of " +"tenant traffic by leveraging existing features and tools of the physical " +"infrastructure." +msgstr "" + +#: ./doc/security-guide/ch035_case-studies-networking.xml25(para) +msgid "" +"A major business driver for Bob is to provide an advanced networking " +"services to his customers. Bob's customers would like to deploy multi-tiered" +" application stacks. This multi-tiered application are either existing " +"enterprise application or newly deployed applications. Since Bob's public " +"cloud is a multi-tenancy enterprise service, the choice to use for L2 " +"isolation in this environment is to use overlay networking. Another aspect " +"of Bob's cloud is the self-service aspect where the customer can provision " +"available networking services as needed. These networking services encompass" +" L2 networks, L3 Routing, Network ACL and NAT. It is " +"important that per-tenant quota's be implemented in this environment." +msgstr "" + +#: ./doc/security-guide/ch035_case-studies-networking.xml38(para) +msgid "" +"An added benefit with utilizing OpenStack Networking is when new advanced " +"networking services become available, these new features can be easily " +"provided to the end customers." +msgstr "" + +#: ./doc/security-guide/ch011_management-introduction.xml3(title) +msgid "Management Introduction" +msgstr "" + +#: ./doc/security-guide/ch011_management-introduction.xml4(para) +msgid "" +"A cloud deployment is a living system. Machines age and fail, software " +"becomes outdated, vulnerabilities are discovered. When errors or omissions " +"are made in configuration, or when software fixes must be applied, these " +"changes must be made in a secure, but convenient, fashion. These changes are" +" typically solved through configuration management." +msgstr "" + +#: ./doc/security-guide/ch011_management-introduction.xml5(para) +msgid "" +"Likewise, it is important to protect the cloud deployment from being " +"configured or manipulated by malicious entities. With many systems in a " +"cloud employing compute and networking virtualization, there are distinct " +"challenges applicable to OpenStack which must be addressed through integrity" +" lifecycle management." +msgstr "" + +#: ./doc/security-guide/ch011_management-introduction.xml6(para) +msgid "" +"Finally, administrators must perform command and control over the cloud for " +"various operational functions. It is important these command and control " +"facilities are understood and secured." +msgstr "" + +#: ./doc/security-guide/ch049_case-studies-tenant-data.xml3(title) +msgid "Case Studies: Tenant Data" +msgstr "" + +#: ./doc/security-guide/ch049_case-studies-tenant-data.xml4(para) +msgid "" +"Returning to Alice and Bob, we will use this section to dive into their " +"particular tenant data privacy requirements. Specifically, we will look into" +" how Alice and Bob both handle tenant data, data destruction, and data " +"encryption." +msgstr "" + +#: ./doc/security-guide/ch049_case-studies-tenant-data.xml7(para) +msgid "" +"As stated during the introduction to Alice's case study, data protection is " +"of an extremely high priority. She needs to ensure that a compromise of one " +"tenant's data does not cause loss of other tenant data. She also has strong " +"regulator requirements that require documentation of data destruction " +"activities. Alice does this using the following:" +msgstr "" + +#: ./doc/security-guide/ch049_case-studies-tenant-data.xml15(para) +msgid "" +"Establishing procedures to sanitize tenant data when a program or project " +"ends" +msgstr "" + +#: ./doc/security-guide/ch049_case-studies-tenant-data.xml16(para) +msgid "" +"Track the destruction of both the tenant data and metadata via ticketing in " +"a CMDB" +msgstr "" + +#: ./doc/security-guide/ch049_case-studies-tenant-data.xml17(para) +#: ./doc/security-guide/ch049_case-studies-tenant-data.xml28(para) +msgid "For Volume storage:" +msgstr "" + +#: ./doc/security-guide/ch049_case-studies-tenant-data.xml18(para) +#: ./doc/security-guide/ch049_case-studies-tenant-data.xml29(para) +msgid "Physical Server Issues" +msgstr "" + +#: ./doc/security-guide/ch049_case-studies-tenant-data.xml19(para) +msgid "" +"To provide secure ephemeral instance storage, Alice implements qcow2 files " +"on an encrypted filesystem." +msgstr "" + +#: ./doc/security-guide/ch049_case-studies-tenant-data.xml24(para) +msgid "" +"As stated during the introduction to Bob's case study, tenant privacy is of " +"an extremely high priority. In addition to the requirements and actions Bob " +"will take to isolate tenants from one another at the infrastructure layer, " +"Bob also needs to provide assurances for tenant data privacy. Bob does this " +"using the following:" +msgstr "" + +#: ./doc/security-guide/ch049_case-studies-tenant-data.xml26(para) +msgid "" +"Establishing procedures to sanitize customer data when a customer churns" +msgstr "" + +#: ./doc/security-guide/ch049_case-studies-tenant-data.xml27(para) +msgid "" +"Track the destruction of both the customer data and metadata via ticketing " +"in a CMDB" +msgstr "" + +#: ./doc/security-guide/ch049_case-studies-tenant-data.xml30(para) +msgid "" +"To provide secure ephemeral instance storage, Bob implements qcow2 files on " +"an encrypted filesystems." +msgstr "" + +#: ./doc/security-guide/ch053_case-studies-instance-isolation.xml3(title) +msgid "Case Studies: Instance Isolation" +msgstr "" + +#: ./doc/security-guide/ch053_case-studies-instance-isolation.xml4(para) +msgid "" +"In this case study we discuss how Alice and Bob would ensure that  their " +"instances are properly isolated. First we consider hypervisor selection, and" +" then techniques for hardening QEMU and applying mandatory access controls." +msgstr "" + +#: ./doc/security-guide/ch053_case-studies-instance-isolation.xml7(para) +msgid "" +"Alice chooses Xen for the hypervisor in her cloud due to a strong internal " +"knowledge base and a desire to use the Xen security modules (XSM) for fine-" +"grained policy enforcement." +msgstr "" + +#: ./doc/security-guide/ch053_case-studies-instance-isolation.xml8(para) +msgid "" +"Alice is willing to apply a relatively large amount of resources to software" +" packaging and maintenance. She will use these resources to build a highly " +"customized version of QEMU that has many components removed, thereby " +"reducing the attack surface. She will also ensure that all compiler " +"hardening options are enabled for QEMU. Alice accepts that these decisions " +"will increase long-term maintenance costs." +msgstr "" + +#: ./doc/security-guide/ch053_case-studies-instance-isolation.xml9(para) +msgid "" +"Alice writes XSM policies (for Xen) and SELinux policies (for Linux domain " +"0, and device domains) to provide stronger isolation between the instances. " +"Alice also uses the Intel TXT support in Xen to measure the hypervisor " +"launch in the TPM." +msgstr "" + +#: ./doc/security-guide/ch053_case-studies-instance-isolation.xml13(para) +msgid "" +"Bob is very concerned about instance isolation since the users in a public " +"cloud represent anyone with a credit card, meaning they are inherently " +"untrusted. Bob has just started hiring the team that will deploy the cloud, " +"so he can tailor his candidate search for specific areas of expertise. With " +"this in mind, Bob chooses a hypervisor based on its technical features, " +"certifications, and community support. KVM has an EAL 4+ common criteria " +"rating, with a layered security protection profile (LSPP) to provide added " +"assurance for instance isolation. This, combined with the strong support for" +" KVM within the OpenStack community drives Bob's decision to use KVM." +msgstr "" + +#: ./doc/security-guide/ch053_case-studies-instance-isolation.xml14(para) +msgid "" +"Bob weighs the added cost of repackaging QEMU and decides that he cannot " +"commit those resources to the project. Fortunately, his Linux distribution " +"has already enabled the compiler hardening options. So he decides to use " +"this QEMU package. Finally, Bob leverages sVirt to manage the SELinux " +"polices associated with the virtualization stack." +msgstr "" + +#: ./doc/security-guide/ch034_tenant-secure-networking-best-practices.xml3(title) +msgid "Networking Services Security Best Practices" +msgstr "" + +#: ./doc/security-guide/ch034_tenant-secure-networking-best-practices.xml4(para) +msgid "" +"This section discusses OpenStack Networking configuration best practices as " +"they apply to tenant network security within your OpenStack deployment." +msgstr "" + +#: ./doc/security-guide/ch034_tenant-secure-networking-best-practices.xml6(title) +msgid "Tenant Network Services Workflow" +msgstr "" + +#: ./doc/security-guide/ch034_tenant-secure-networking-best-practices.xml7(para) +msgid "" +"OpenStack Networking provides users real self services of network resources " +"and configurations. It is important that Cloud Architects and Operators " +"evaluate their design use cases in providing users the ability to create, " +"update, and destroy available network resources." +msgstr "" + +#: ./doc/security-guide/ch034_tenant-secure-networking-best-practices.xml10(title) +msgid "Networking Resource Policy Engine" +msgstr "" + +#: ./doc/security-guide/ch034_tenant-secure-networking-best-practices.xml11(para) +msgid "" +"A policy engine and its configuration file, " +"policy.json, within OpenStack Networking provides a " +"method to provide finer grained authorization of users on tenant networking " +"methods and objects. It is important that cloud architects and operators " +"evaluate their design and use cases in providing users and tenants the " +"ability to create, update, and destroy available network resources as it has" +" a tangible effect on tenant network availability, network security, and " +"overall OpenStack security. For a more detailed explanation of OpenStack " +"Networking policy definition, please refer to the Authentication and authorization " +"section in the OpenStack Cloud Administrator " +"Guide." +msgstr "" + +#: ./doc/security-guide/ch034_tenant-secure-networking-best-practices.xml25(address) +msgid "" +"It is important to review the default networking resource policy and modify " +"the policy appropriately for your security posture." +msgstr "" + +#: ./doc/security-guide/ch034_tenant-secure-networking-best-practices.xml26(para) +msgid "" +"If your deployment of OpenStack provides multiple external access points " +"into different security domains it is important that you limit the tenant's " +"ability to attach multiple vNICs to multiple external access points -- this " +"would bridge these security domains and could lead to unforeseen security " +"compromise. It is possible mitigate this risk by utilizing the host " +"aggregates functionality provided by OpenStack Compute or through splitting " +"the tenant VMs into multiple tenant projects with different virtual network " +"configurations." +msgstr "" + +#: ./doc/security-guide/ch034_tenant-secure-networking-best-practices.xml29(title) +msgid "Security Groups" +msgstr "" + +#: ./doc/security-guide/ch034_tenant-secure-networking-best-practices.xml30(para) +msgid "" +"The OpenStack Networking Service provides security group functionality using" +" a mechanism that is more flexible and powerful than the security group " +"capabilities built into OpenStack Compute. Thus, when using OpenStack " +"Networking, nova.conf should always disable built-in " +"security groups and proxy all security group calls to the OpenStack " +"Networking API. Failure to do so will result in conflicting security " +"policies being simultaneously applied by both services. To proxy security " +"groups to OpenStack Networking, use the following configuration values:" +msgstr "" + +#: ./doc/security-guide/ch034_tenant-secure-networking-best-practices.xml32(para) +msgid "" +"firewall_driver : must be set to 'nova.virt.firewall.NoopFirewallDriver' so " +"that nova-compute does not " +"perform iptables-based filtering itself." +msgstr "" + +#: ./doc/security-guide/ch034_tenant-secure-networking-best-practices.xml35(para) +msgid "" +"security_group_api : must be set to 'neutron' so that all security group " +"requests are proxied to the OpenStack Network Service." +msgstr "" + +#: ./doc/security-guide/ch034_tenant-secure-networking-best-practices.xml38(para) +msgid "" +"Security groups and security group rules allow administrators and tenants " +"the ability to specify the type of traffic and direction (ingress/egress) " +"that is allowed to pass through a virtual interface port. A security group " +"is a container for security group rules. When a virtual interface port is " +"created in OpenStack Networking it is associated with a security group. If a" +" security group is not specified, the port will be associated with a " +"'default' security group. By default this group will drop all ingress " +"traffic and allow all egress. Rules can be added to this group in order to " +"change the behaviour." +msgstr "" + +#: ./doc/security-guide/ch034_tenant-secure-networking-best-practices.xml39(para) +msgid "" +"When using the security group API through OpenStack Compute, security groups" +" are applied to all virtual interface ports on an instance. The reason for " +"this is that OpenStack Compute security group APIs are instance based and " +"not virtual interface port based as OpenStack Networking." +msgstr "" + +#: ./doc/security-guide/ch034_tenant-secure-networking-best-practices.xml42(title) +msgid "Quotas" +msgstr "" + +#: ./doc/security-guide/ch034_tenant-secure-networking-best-practices.xml43(para) +msgid "" +"Quotas provide the ability to limit the number of network resources " +"available to tenants. You can enforce default quotas for all tenants." +msgstr "" + +#: ./doc/security-guide/ch034_tenant-secure-networking-best-practices.xml70(para) +msgid "" +"OpenStack Networking also supports per-tenant quotas limit via a quota " +"extension API. To enable per-tenant quotas, you need to set " +"quota_driver in neutron.conf." +msgstr "" + +#. When image changes, this message will be marked fuzzy or untranslated for +#. you. +#. It doesn't matter what you translate it to: it's not used at all. +#: ./doc/security-guide/ch052_devices.xml131(None) +#: ./doc/security-guide/ch052_devices.xml134(None) +msgid "" +"@@image: 'static/sVirt Diagram 1.png'; md5=ffcdbb45d9054670ad4c270a7c7d3925" +msgstr "" + +#: ./doc/security-guide/ch052_devices.xml3(title) +msgid "Hardening the Virtualization Layers" +msgstr "" + +#: ./doc/security-guide/ch052_devices.xml4(para) +msgid "" +"In the beginning of this chapter we discuss the use of both physical and " +"virtual hardware by instances, the associated security risks, and some " +"recommendations for mitigating those risks. We conclude the chapter with a " +"discussion of sVirt, an open source project for integrating SELinux " +"mandatory access controls with the virtualization components." +msgstr "" + +#: ./doc/security-guide/ch052_devices.xml6(title) +msgid "Physical Hardware (PCI Passthrough)" +msgstr "" + +#: ./doc/security-guide/ch052_devices.xml7(para) +msgid "" +"Many hypervisors offer a functionality known as PCI passthrough. This allows" +" an instance to have direct access to a piece of hardware on the node. For " +"example, this could be used to allow instances to access video cards " +"offering the compute unified device architecture (CUDA) for high performance" +" computation. This feature carries two types of security risks: direct " +"memory access and hardware infection." +msgstr "" + +#: ./doc/security-guide/ch052_devices.xml8(para) +msgid "" +"Direct memory access (DMA) is a feature that permits certain hardware " +"devices to access arbitrary physical memory addresses in the host computer. " +"Often video cards have this capability. However, an instance should not be " +"given arbitrary physical memory access because this would give it full view " +"of both the host system and other instances running on the same node. " +"Hardware vendors use an input/output memory management unit (IOMMU) to " +"manage DMA access in these situations. Therefore, cloud architects should " +"ensure that the hypervisor is configured to utilize this hardware feature." +msgstr "" + +#: ./doc/security-guide/ch052_devices.xml10(para) +msgid "" +"KVM: How to assign devices with VT-d in" +" KVM" +msgstr "" + +#: ./doc/security-guide/ch052_devices.xml13(para) +msgid "Xen: VTd Howto" +msgstr "" + +#: ./doc/security-guide/ch052_devices.xml17(para) +msgid "The IOMMU feature is marketed as VT-d by Intel and AMD-Vi by AMD." +msgstr "" + +#: ./doc/security-guide/ch052_devices.xml19(para) +msgid "" +"A hardware infection occurs when an instance makes a malicious modification " +"to the firmware or some other part of a device. As this device is used by " +"other instances, or even the host OS, the malicious code can spread into " +"these systems. The end result is that one instance can run code outside of " +"its security domain. This is a potential problem in any hardware sharing " +"scenario. The problem is specific to this scenario because it is harder to " +"reset the state of physical hardware than virtual hardware." +msgstr "" + +#: ./doc/security-guide/ch052_devices.xml20(para) +msgid "" +"Solutions to the hardware infection problem are domain specific. The " +"strategy is to identify how an instance can modify hardware state then " +"determine how to reset any modifications when the instance is done using the" +" hardware. For example, one option could be to re-flash the firmware after " +"use. Clearly there is a need to balance hardware longevity with security as " +"some firmwares will fail after a large number of writes. TPM technology, " +"described in link:Management/Node Bootstrapping, provides" +" a solution for detecting unauthorized firmware changes. Regardless of the " +"strategy selected, it is important to understand the risks associated with " +"this kind of hardware sharing so that they can be properly mitigated for a " +"given deployment scenario." +msgstr "" + +#: ./doc/security-guide/ch052_devices.xml21(para) +msgid "" +"Additionally, due to the risk and complexities associated with PCI " +"passthrough, it should be disabled by default. If enabled for a specific " +"need, you will need to have appropriate processes in place to ensure the " +"hardware is clean before re-issue." +msgstr "" + +#: ./doc/security-guide/ch052_devices.xml24(title) +msgid "Virtual Hardware (QEMU)" +msgstr "" + +#: ./doc/security-guide/ch052_devices.xml25(para) +msgid "" +"When running a virtual machine, virtual hardware is a software layer that " +"provides the hardware interface for the virtual machine. Instances use this " +"functionality to provide network, storage, video, and other devices that may" +" be needed. With this in mind, most instances in your environment will " +"exclusively use virtual hardware, with a minority that will require direct " +"hardware access. The major open source hypervisors use QEMU for this " +"functionality. While QEMU fills an important need for virtualization " +"platforms, it has proven to be a very challenging software project to write " +"and maintain. Much of the functionality in QEMU is implemented with low-" +"level code that is difficult for most developers to comprehend. Furthermore," +" the hardware virtualized by QEMU includes many legacy devices that have " +"their own set of quirks. Putting all of this together, QEMU has been the " +"source of many security problems, including hypervisor breakout attacks." +msgstr "" + +#: ./doc/security-guide/ch052_devices.xml41(para) +msgid "" +"For the reasons stated above, it is important to take proactive steps to " +"harden QEMU. We recommend three specific steps: minimizing the code base, " +"using compiler hardening, and using mandatory access controls, such as " +"sVirt, SELinux, or AppArmor." +msgstr "" + +#: ./doc/security-guide/ch052_devices.xml47(title) +msgid "Minimizing the Qemu Code base" +msgstr "" + +#: ./doc/security-guide/ch052_devices.xml48(para) +msgid "" +"One classic security principle is to remove any unused components from your " +"system. QEMU provides support for many different virtual hardware devices. " +"However, only a small number of devices are needed for a given instance. " +"Most instances will use the virtio devices. However, some legacy instances " +"will need access to specific hardware, which can be specified using glance " +"metadata:" +msgstr "" + +#: ./doc/security-guide/ch052_devices.xml54(para) +msgid "" +"A cloud architect should decide what devices to make available to cloud " +"users. Anything that is not needed should be removed from QEMU. This step " +"requires recompiling QEMU after modifying the options passed to the QEMU " +"configure script. For a complete list of up-to-date options simply run " +"./configure --help from within the QEMU source directory." +" Decide what is needed for your deployment, and disable the remaining " +"options." +msgstr "" + +#: ./doc/security-guide/ch052_devices.xml57(title) +msgid "Compiler Hardening" +msgstr "" + +#: ./doc/security-guide/ch052_devices.xml58(para) +msgid "" +"The next step is to harden QEMU using compiler hardening options. Modern " +"compilers provide a variety of compile time options to improve the security " +"of the resulting binaries. These features, which we will describe in more " +"detail below, include relocation read-only (RELRO), stack canaries, never " +"execute (NX), position independent executable (PIE), and address space " +"layout randomization (ASLR)." +msgstr "" + +#: ./doc/security-guide/ch052_devices.xml59(para) +msgid "" +"Many modern linux distributions already build QEMU with compiler hardening " +"enabled, so you may want to verify your existing executable before " +"proceeding with the information below. One tool that can assist you with " +"this verification is called checksec.sh." +msgstr "" + +#: ./doc/security-guide/ch052_devices.xml61(para) +msgid "" +"RELocation Read-Only (RELRO): Hardens the data sections" +" of an executable. Both full and partial RELRO modes are supported by gcc. " +"For QEMU full RELRO is your best choice. This will make the global offset " +"table read-only and place various internal data sections before the program " +"data section in the resulting executable." +msgstr "" + +#: ./doc/security-guide/ch052_devices.xml64(para) +msgid "" +"Stack Canaries: Places values on the stack and verifies" +" their presence to help prevent buffer overflow attacks." +msgstr "" + +#: ./doc/security-guide/ch052_devices.xml67(para) +msgid "" +"Never eXecute (NX): Also known as Data Execution " +"Prevention (DEP), ensures that data sections of the executable can not be " +"executed." +msgstr "" + +#: ./doc/security-guide/ch052_devices.xml70(para) +msgid "" +"Position Independent Executable (PIE): Produces a " +"position independent executable, which is necessary for ASLR.  " +msgstr "" + +#: ./doc/security-guide/ch052_devices.xml73(para) +msgid "" +"Address Space Layout Randomization (ASLR) : This " +"ensures that both code and data regions will be randomized. Enabled by the " +"kernel (all modern linux kernels support ASLR), when the executable is built" +" with PIE." +msgstr "" + +#: ./doc/security-guide/ch052_devices.xml76(para) +msgid "" +"Putting this all together, and adding in some additional useful protections," +" we recommend the following compiler options for gcc when compiling QEMU:" +msgstr "" + +#: ./doc/security-guide/ch052_devices.xml79(para) +msgid "" +"We recommend testing your QEMU executable file after it is compiled to " +"ensure that the compiler hardening worked properly." +msgstr "" + +#: ./doc/security-guide/ch052_devices.xml80(para) +msgid "" +"Most cloud deployments will not want to build software such as QEMU by hand." +" It is better to use packaging to ensure that the process is repeatable and " +"to ensure that the end result can be easily deployed throughout the cloud. " +"The references below provide some additional details on applying compiler " +"hardening options to existing packages." +msgstr "" + +#: ./doc/security-guide/ch052_devices.xml82(para) +msgid "" +"DEB packages: Hardening " +"Walkthrough" +msgstr "" + +#: ./doc/security-guide/ch052_devices.xml85(para) +msgid "" +"RPM packages: How to " +"create an RPM package" +msgstr "" + +#: ./doc/security-guide/ch052_devices.xml91(para) +msgid "" +"Compiler hardening makes it more difficult to attack the QEMU process. " +"However, if an attacker does succeed, we would like to limit the impact of " +"the attack. Mandatory access controls accomplish this by restricting the " +"privileges on QEMU process to only what is needed. This can be accomplished " +"using sVirt / SELinux or AppArmor. When using sVirt, SELinux is configured " +"to run every QEMU process under a different security context. AppArmor can " +"be configured to provide similar functionality. We provide more details on " +"sVirt in the instance isolation section below." +msgstr "" + +#: ./doc/security-guide/ch052_devices.xml95(title) +msgid "sVirt: SELinux + Virtualization" +msgstr "" + +#: ./doc/security-guide/ch052_devices.xml96(para) +msgid "" +"With unique kernel-level architecture and National Security Agency (NSA) " +"developed security mechanisms, KVM provides foundational isolation " +"technologies for multi tenancy. With developmental origins dating back to " +"2002, the Secure Virtualization (sVirt) technology is the application of " +"SELinux against modern day virtualization. SELinux, which was designed to " +"apply separation control based upon labels, has been extended to provide " +"isolation between virtual machine processes, devices, data files and system " +"processes acting upon their behalf." +msgstr "" + +#: ./doc/security-guide/ch052_devices.xml105(para) +msgid "" +"OpenStack's sVirt implementation aspires to protect hypervisor hosts and " +"virtual machines against two primary threat vectors:" +msgstr "" + +#: ./doc/security-guide/ch052_devices.xml107(para) +msgid "" +"Hypervisor threats A compromised " +"application running within a virtual machine attacks the hypervisor to " +"access underlying resources. For example, the host OS, applications, or " +"devices within the physical machine. This is a threat vector unique to " +"virtualization and represents considerable risk as the underlying real " +"machine can be compromised due to vulnerability in a single virtual " +"application." +msgstr "" + +#: ./doc/security-guide/ch052_devices.xml117(para) +msgid "" +"Virtual Machine (multi-tenant) threats A " +"compromised application running within a VM attacks the hypervisor to " +"access/control another virtual machine and its resources. This is a threat " +"vector unique to virtualization and represents considerable risk as a " +"multitude of virtual machine file images could be compromised due to " +"vulnerability in a single application. This virtual network attack is a " +"major concern as the administrative techniques for protecting real networks " +"do not directly apply to the virtual environment." +msgstr "" + +#: ./doc/security-guide/ch052_devices.xml129(para) +msgid "" +"Each KVM-based virtual machine is a process which is labeled by SELinux, " +"effectively establishing a security boundary around each virtual machine. " +"This security boundary is monitored and enforced by the Linux kernel, " +"restricting the virtual machine's access to resources outside of its " +"boundary such as host machine data files or other VMs." +msgstr "" + +#: ./doc/security-guide/ch052_devices.xml137(para) +msgid "" +"As shown above, sVirt isolation is provided regardless of the guest " +"Operating System running inside the virtual machine -- Linux or Windows VMs " +"can be used. Additionally, many Linux distributions provide SELinux within " +"the operating system, allowing the virtual machine to protect internal " +"virtual resources from threats. " +msgstr "" + +#: ./doc/security-guide/ch052_devices.xml139(title) +msgid "Labels and Categories" +msgstr "" + +#: ./doc/security-guide/ch052_devices.xml140(para) +msgid "" +"KVM-based virtual machine instances are labelled with their own SELinux data" +" type, known as svirt_image_t. Kernel level protections prevent unauthorized" +" system processes, such as malware, from manipulating the virtual machine " +"image files on disk. When virtual machines are powered off, images are " +"stored as svirt_image_t as shown below:" +msgstr "" + +#: ./doc/security-guide/ch052_devices.xml146(para) +msgid "" +"The svirt_image_t label uniquely identifies image files on disk, allowing " +"for the SELinux policy to restrict access. When a KVM-based Compute image is" +" powered on, sVirt appends a random numerical identifier to the image. sVirt" +" is technically capable of assigning numerical identifiers to 524,288 " +"virtual machines per hypervisor node, however OpenStack deployments are " +"highly unlikely to encounter this limitation." +msgstr "" + +#: ./doc/security-guide/ch052_devices.xml147(para) +msgid "This example shows the sVirt category identifier:" +msgstr "" + +#: ./doc/security-guide/ch052_devices.xml152(title) +msgid "Booleans" +msgstr "" + +#: ./doc/security-guide/ch052_devices.xml153(para) +msgid "" +"To ease the administrative burden of managing SELinux, many enterprise Linux" +" platforms utilize SELinux Booleans to quickly change the security posture " +"of sVirt." +msgstr "" + +#: ./doc/security-guide/ch052_devices.xml154(para) +msgid "" +"Red Hat Enterprise Linux-based KVM deployments utilize the following sVirt " +"booleans:" +msgstr "" + +#: ./doc/security-guide/ch052_devices.xml161(emphasis) +msgid "sVirt SELinux Boolean" +msgstr "" + +#: ./doc/security-guide/ch052_devices.xml162(emphasis) +msgid " Description" +msgstr "" + +#: ./doc/security-guide/ch052_devices.xml165(para) +msgid "virt_use_common" +msgstr "" + +#: ./doc/security-guide/ch052_devices.xml166(para) +msgid "Allow virt to use serial/parallel communication ports." +msgstr "" + +#: ./doc/security-guide/ch052_devices.xml169(para) +msgid "virt_use_fusefs" +msgstr "" + +#: ./doc/security-guide/ch052_devices.xml170(para) +msgid "Allow virt to read FUSE mounted files." +msgstr "" + +#: ./doc/security-guide/ch052_devices.xml173(para) +msgid "virt_use_nfs" +msgstr "" + +#: ./doc/security-guide/ch052_devices.xml174(para) +msgid "Allow virt to manage NFS mounted files." +msgstr "" + +#: ./doc/security-guide/ch052_devices.xml177(para) +msgid "virt_use_samba" +msgstr "" + +#: ./doc/security-guide/ch052_devices.xml178(para) +msgid "Allow virt to manage CIFS mounted files." +msgstr "" + +#: ./doc/security-guide/ch052_devices.xml181(para) +msgid "virt_use_sanlock" +msgstr "" + +#: ./doc/security-guide/ch052_devices.xml182(para) +msgid "Allow confined virtual guests to interact with the sanlock." +msgstr "" + +#: ./doc/security-guide/ch052_devices.xml185(para) +msgid "virt_use_sysfs" +msgstr "" + +#: ./doc/security-guide/ch052_devices.xml186(para) +msgid "Allow virt to manage device configuration (PCI)." +msgstr "" + +#: ./doc/security-guide/ch052_devices.xml189(para) +msgid "virt_use_usb" +msgstr "" + +#: ./doc/security-guide/ch052_devices.xml190(para) +msgid "Allow virt to use USB devices." +msgstr "" + +#: ./doc/security-guide/ch052_devices.xml193(para) +msgid "virt_use_xserver" +msgstr "" + +#: ./doc/security-guide/ch052_devices.xml194(para) +msgid "Allow virtual machine to interact with the X Window System." +msgstr "" + +#: ./doc/security-guide/ch020_ssl-everywhere.xml3(title) +msgid "SSL Proxies and HTTP Services" +msgstr "" + +#: ./doc/security-guide/ch020_ssl-everywhere.xml4(para) +msgid "" +"OpenStack endpoints are HTTP services providing APIs to both end-users on " +"public networks and to other OpenStack services within the same deployment " +"operating over the management network. It is highly recommended these " +"requests, both those internal and external, operate over SSL." +msgstr "" + +#: ./doc/security-guide/ch020_ssl-everywhere.xml5(para) +msgid "" +"In order for API requests to be encrypted by SSL it's necessary to position " +"the API services behind a proxy that will establish and terminate SSL " +"sessions. The following table offers a non-exhaustive list of software " +"services that can proxy SSL traffic for API requests:" +msgstr "" + +#: ./doc/security-guide/ch020_ssl-everywhere.xml7(link) +msgid "Pound" +msgstr "" + +#: ./doc/security-guide/ch020_ssl-everywhere.xml10(link) +#: ./doc/security-guide/ch020_ssl-everywhere.xml80(title) +msgid "Stud" +msgstr "" + +#: ./doc/security-guide/ch020_ssl-everywhere.xml13(link) +#: ./doc/security-guide/ch020_ssl-everywhere.xml119(title) +msgid "nginx" +msgstr "" + +#: ./doc/security-guide/ch020_ssl-everywhere.xml16(link) +msgid "Apache httpd" +msgstr "" + +#: ./doc/security-guide/ch020_ssl-everywhere.xml19(para) +msgid "Hardware appliance SSL acceleration proxies" +msgstr "" + +#: ./doc/security-guide/ch020_ssl-everywhere.xml22(para) +msgid "" +"It is important to be mindful of the size of requests that will be processed" +" by any chosen SSL proxy." +msgstr "" + +#: ./doc/security-guide/ch020_ssl-everywhere.xml24(title) +msgid "Examples" +msgstr "" + +#: ./doc/security-guide/ch020_ssl-everywhere.xml25(para) +msgid "" +"Below we provide some sample configuration setting for enabling SSL in some " +"of the most popular web servers/SSL terminators with recommended " +"configurations. Note that we have SSL v3 enabled in some of these examples " +"as this will be required in many deployments for client compatibility." +msgstr "" + +#: ./doc/security-guide/ch020_ssl-everywhere.xml27(title) +msgid "Pound - with AES-NI acceleration" +msgstr "" + +#: ./doc/security-guide/ch020_ssl-everywhere.xml81(para) +msgid "" +"This stud example enables SSL v3 for client compatibility.  The ciphers line" +" can be tweaked based on your needs, however this is a reasonable starting " +"place." +msgstr "" + +#: ./doc/security-guide/ch020_ssl-everywhere.xml120(para) +msgid "" +"This nginx example requires TLS v1.1 or v1.2 for maximum security. The " +"ssl_ciphers line can be tweaked based on your needs, however this is a " +"reasonable starting place." +msgstr "" + +#: ./doc/security-guide/ch020_ssl-everywhere.xml137(title) +msgid "Apache" +msgstr "" + +#: ./doc/security-guide/ch020_ssl-everywhere.xml163(para) +msgid "" +"Compute API SSL endpoint in Apache2, which needs to be paired with a short " +"WSGI script." +msgstr "" + +#: ./doc/security-guide/ch020_ssl-everywhere.xml188(title) +msgid "HTTP Strict Transport Security" +msgstr "" + +#: ./doc/security-guide/ch020_ssl-everywhere.xml189(para) +msgid "" +"We recommend that all production deployments use HSTS. This header prevents " +"browsers from making insecure connections after they have made a single " +"secure one. If you have deployed your HTTP services on a public or an " +"untrusted domain, HSTS is especially important. To enable HSTS, configure " +"your web server to send a header like this with all requests:" +msgstr "" + +#: ./doc/security-guide/ch020_ssl-everywhere.xml192(para) +msgid "" +"Start with a short timeout of 1 day during testing, and raise it to one year" +" after testing has shown that you haven't introduced problems for users. " +"Note that once this header is set to a large timeout, it is (by design) very" +" difficult to disable." +msgstr "" + +#: ./doc/security-guide/ch058_forensicsincident-response.xml3(title) +msgid "Forensics and Incident Response" +msgstr "" + +#: ./doc/security-guide/ch058_forensicsincident-response.xml4(para) +msgid "" +"A lot of activity goes on within a cloud environment. It is a mix of " +"hardware, operating systems, virtual machine managers, the OpenStack " +"services, cloud-user activity such as creating instances and attaching " +"storage, the network underlying the whole, and finally end-users using the " +"applications running on the various instances." +msgstr "" + +#: ./doc/security-guide/ch058_forensicsincident-response.xml5(para) +msgid "" +"The generation and collection of logs is an important component of securely " +"monitoring an OpenStack infrastructure. Logs provide visibility into the " +"day-to-day actions of administrators, tenants, and guests, in addition to " +"the activity in the compute, networking, and storage and other components " +"that comprise your OpenStack deployment." +msgstr "" + +#: ./doc/security-guide/ch058_forensicsincident-response.xml6(para) +msgid "" +"The basics of logging: configuration, setting log level, location of the log" +" files, and how to use and customize logs, as well as how to do centralized " +"collections of logs is well covered in the OpenStack Operations " +"Guide." +msgstr "" + +#: ./doc/security-guide/ch058_forensicsincident-response.xml7(para) +msgid "" +"Logs are not only valuable for proactive security and continuous compliance " +"activities, but they are also a valuable information  source for " +"investigating and responding to incidents." +msgstr "" + +#: ./doc/security-guide/ch058_forensicsincident-response.xml8(para) +msgid "" +"For instance, analyzing the access logs of Identity Service or its " +"replacement authentication system would alert us to failed logins, their " +"frequency, origin IP, whether the events are restricted to select accounts " +"etc. Log analysis supports detection." +msgstr "" + +#: ./doc/security-guide/ch058_forensicsincident-response.xml9(para) +msgid "" +"On detection, further action may be to black list an IP, or recommend " +"strengthening user passwords, or even de-activating a user account if it is " +"deemed dormant." +msgstr "" + +#: ./doc/security-guide/ch058_forensicsincident-response.xml11(title) +msgid "Monitoring Use Cases" +msgstr "" + +#: ./doc/security-guide/ch058_forensicsincident-response.xml12(para) +msgid "" +"Monitoring events is more pro-active and provides real-time detection and " +"response.  There are several tools to aid in monitoring." +msgstr "" + +#: ./doc/security-guide/ch058_forensicsincident-response.xml13(para) +msgid "" +"In the case of an OpenStack cloud instance, we need to monitor the hardware," +" the OpenStack services, and the cloud resource usage. The last stems from " +"wanting to be elastic, to scale to the dynamic needs of the users." +msgstr "" + +#: ./doc/security-guide/ch058_forensicsincident-response.xml14(para) +msgid "" +"Here are a few important use cases to consider when implementing log " +"aggregation, analysis and monitoring. These use cases can be implemented and" +" monitored through various commercial and open source tools, homegrown " +"scripts, etc. These tools and scripts can generate events that can then be " +"sent to the administrators through email or integrated dashboard. It is " +"important to consider additional use cases that may apply to your specific " +"network and what you may consider anomalous behavior." +msgstr "" + +#: ./doc/security-guide/ch058_forensicsincident-response.xml16(para) +msgid "" +"Detecting the absence of log generation is an event of high value. Such an " +"event would indicate a service failure or even an intruder who has " +"temporarily switched off logging or modified the log level to hide their " +"tracks." +msgstr "" + +#: ./doc/security-guide/ch058_forensicsincident-response.xml20(para) +msgid "" +"Application events such as start and/or stop that were unscheduled would " +"also be events to monitor and examine for possible security implications." +msgstr "" + +#: ./doc/security-guide/ch058_forensicsincident-response.xml24(para) +msgid "" +"OS events on the OpenStack service machines such as user logins, restarts " +"also provide valuable insight into use/misuse" +msgstr "" + +#: ./doc/security-guide/ch058_forensicsincident-response.xml28(para) +msgid "" +"Being able to detect the load on the OpenStack servers also enables " +"responding by way of introducing additional servers for load balancing to " +"ensure high availability." +msgstr "" + +#: ./doc/security-guide/ch058_forensicsincident-response.xml32(para) +msgid "" +"Other events that are actionable are networking bridges going down, ip " +"tables being flushed on compute nodes and consequential loss of access to " +"instances resulting in unhappy customers. " +msgstr "" + +#: ./doc/security-guide/ch058_forensicsincident-response.xml36(para) +msgid "" +"To reduce security risks from orphan instances on a user/tenant/domain " +"deletion in the Identity service there is discussion to generate " +"notifications in the system and have OpenStack components respond to these " +"events as appropriate such as terminating instances, disconnecting attached " +"volumes, reclaiming CPU and storage resources etc. " +msgstr "" + +#: ./doc/security-guide/ch058_forensicsincident-response.xml39(para) +msgid "" +"A cloud will host many virtual instances, and monitoring these instances " +"goes beyond hardware monitoring and log files which may just contain CRUD " +"events." +msgstr "" + +#: ./doc/security-guide/ch058_forensicsincident-response.xml40(para) +msgid "" +"Security monitoring controls such as intrusion detection software, antivirus" +" software, and spyware detection and removal utilities can generate logs " +"that show when and how an attack or intrusion took place. Deploying these " +"tools on the cloud machines provides value and protection. Cloud users, " +"those running instances on the cloud may also want to run such tools on " +"their instances." +msgstr "" + +#: ./doc/security-guide/ch058_forensicsincident-response.xml44(link) +msgid "http://www.mirantis.com/blog/openstack-monitoring/" +msgstr "" + +#: ./doc/security-guide/ch058_forensicsincident-response.xml45(link) +msgid "http://blog.sflow.com/2012/01/host-sflow-distributed-agent.html" +msgstr "" + +#: ./doc/security-guide/ch058_forensicsincident-response.xml46(link) +msgid "http://blog.sflow.com/2009/09/lan-and-wan.html" +msgstr "" + +#: ./doc/security-guide/ch058_forensicsincident-response.xml47(link) +msgid "" +"http://blog.sflow.com/2013/01/rapidly-detecting-large-flows-sflow-vs.html" +msgstr "" + +#. Put one translator per line, in the form of NAME , YEAR1, YEAR2 +#: ./doc/security-guide/ch058_forensicsincident-response.xml0(None) +msgid "translator-credits" +msgstr "" diff --git a/doc/security-guide/locale/security-guide.pot b/doc/security-guide/locale/security-guide.pot new file mode 100644 index 0000000000..7459078e57 --- /dev/null +++ b/doc/security-guide/locale/security-guide.pot @@ -0,0 +1,5904 @@ +msgid "" +msgstr "" +"Project-Id-Version: PACKAGE VERSION\n" +"POT-Creation-Date: 2014-01-30 06:24+0000\n" +"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n" +"Last-Translator: FULL NAME \n" +"Language-Team: LANGUAGE \n" +"MIME-Version: 1.0\n" +"Content-Type: text/plain; charset=UTF-8\n" +"Content-Transfer-Encoding: 8bit\n" + +#. When image changes, this message will be marked fuzzy or untranslated for you. +#. It doesn't matter what you translate it to: it's not used at all. +#: ./doc/security-guide/ch002_why-and-how-we-wrote-this-book.xml:30(None) ./doc/security-guide/ch002_why-and-how-we-wrote-this-book.xml:33(None) +msgid "@@image: 'static/group.png'; md5=aec1f0af66d29c1a5d1f174df1f12812" +msgstr "" + +#: ./doc/security-guide/ch002_why-and-how-we-wrote-this-book.xml:3(title) +msgid "Why and how we wrote this book" +msgstr "" + +#: ./doc/security-guide/ch002_why-and-how-we-wrote-this-book.xml:4(para) +msgid "As OpenStack adoption continues to grow and the product matures, security has become a priority. The OpenStack Security Group has recognized the need for a comprehensive and authoritative security guide. The OpenStack Security Guide has been written to provide an overview of security best practices, guidelines, and recommendations for increasing the security of an OpenStack deployment. The authors bring their expertise from deploying and securing OpenStack in a variety of environments." +msgstr "" + +#: ./doc/security-guide/ch002_why-and-how-we-wrote-this-book.xml:5(para) +msgid "The guide augments the OpenStack Operations Guide and can be referenced to harden existing OpenStack deployments or to evaluate the security controls of OpenStack cloud providers." +msgstr "" + +#: ./doc/security-guide/ch002_why-and-how-we-wrote-this-book.xml:7(title) +msgid "Objectives" +msgstr "" + +#: ./doc/security-guide/ch002_why-and-how-we-wrote-this-book.xml:9(para) +msgid "Identify the security domains in OpenStack" +msgstr "" + +#: ./doc/security-guide/ch002_why-and-how-we-wrote-this-book.xml:12(para) +msgid "Provide guidance to secure your OpenStack deployment" +msgstr "" + +#: ./doc/security-guide/ch002_why-and-how-we-wrote-this-book.xml:15(para) +msgid "Highlight security concerns and potential mitigations in present day OpenStack" +msgstr "" + +#: ./doc/security-guide/ch002_why-and-how-we-wrote-this-book.xml:18(para) +msgid "Discuss upcoming security features" +msgstr "" + +#: ./doc/security-guide/ch002_why-and-how-we-wrote-this-book.xml:21(para) +msgid "To provide a community driven facility for knowledge capture and dissemination" +msgstr "" + +#: ./doc/security-guide/ch002_why-and-how-we-wrote-this-book.xml:26(title) +msgid "How" +msgstr "" + +#: ./doc/security-guide/ch002_why-and-how-we-wrote-this-book.xml:27(para) +msgid "As with the OpenStack Operations Guide, we followed the book sprint methodology. The book sprint process allows for rapid development and production of large bodies of written work. Coordinators from the OpenStack Security Group re-enlisted the services of Adam Hyde as facilitator. Corporate support was obtained and the project was formally announced during the OpenStack summit in Portland, Oregon." +msgstr "" + +#: ./doc/security-guide/ch002_why-and-how-we-wrote-this-book.xml:28(para) +msgid "The team converged in Annapolis, MD due to the close proximity of some key members of the group. This was a remarkable collaboration between public sector intelligence community members, silicon valley startups and some large, well-known technology companies. The book sprint ran during the last week in June 2013 and the first edition was created in five days." +msgstr "" + +#: ./doc/security-guide/ch002_why-and-how-we-wrote-this-book.xml:36(para) +msgid "The team included:" +msgstr "" + +#: ./doc/security-guide/ch002_why-and-how-we-wrote-this-book.xml:39(para) +msgid "Bryan D. Payne, Nebula" +msgstr "" + +#: ./doc/security-guide/ch002_why-and-how-we-wrote-this-book.xml:40(para) +msgid "Dr. Bryan D. Payne is the Director of Security Research at Nebula and co-founder of the OpenStack Security Group (OSSG). Prior to joining Nebula, he worked at Sandia National Labs, the National Security Agency, BAE Systems, and IBM Research. He graduated with a Ph.D. in Computer Science from the Georgia Tech College of Computing, specializing in systems security." +msgstr "" + +#: ./doc/security-guide/ch002_why-and-how-we-wrote-this-book.xml:43(para) +msgid "Robert Clark, HP" +msgstr "" + +#: ./doc/security-guide/ch002_why-and-how-we-wrote-this-book.xml:44(para) +msgid "Robert Clark is the Lead Security Architect for HP Cloud Services and co-founder of the OpenStack Security Group (OSSG). Prior to being recruited by HP, he worked in the UK Intelligence Community. Robert has a strong background in threat modeling, security architecture and virtualization technology. Robert has a master's degree in Software Engineering from the University of Wales." +msgstr "" + +#: ./doc/security-guide/ch002_why-and-how-we-wrote-this-book.xml:47(para) +msgid "Keith Basil, Red Hat" +msgstr "" + +#: ./doc/security-guide/ch002_why-and-how-we-wrote-this-book.xml:48(para) +msgid "Keith Basil is a Principal Product Manager for Red Hat OpenStack and is focused on Red Hat's OpenStack product management, development and strategy. Within the US public sector, Basil brings previous experience from the design of an authorized, secure, high-performance cloud architecture for Federal civilian agencies and contractors." +msgstr "" + +#: ./doc/security-guide/ch002_why-and-how-we-wrote-this-book.xml:51(para) +msgid "Cody Bunch, Rackspace" +msgstr "" + +#: ./doc/security-guide/ch002_why-and-how-we-wrote-this-book.xml:52(para) +msgid "Cody Bunch is a Private Cloud architect with Rackspace. Cody has co-authored an update to \"The OpenStack Cookbook\" as well as books on VMware automation." +msgstr "" + +#: ./doc/security-guide/ch002_why-and-how-we-wrote-this-book.xml:55(para) +msgid "Malini Bhandaru, Intel" +msgstr "" + +#: ./doc/security-guide/ch002_why-and-how-we-wrote-this-book.xml:56(para) +msgid "Malini Bhandaru is a security architect at Intel. She has a varied background, having worked on platform power and performance at Intel, speech products at Nuance, remote monitoring and management at ComBrio, and web commerce at Verizon. She has a Ph.D. in Artificial Intelligence from the University of Massachusetts, Amherst." +msgstr "" + +#: ./doc/security-guide/ch002_why-and-how-we-wrote-this-book.xml:59(para) +msgid "Gregg Tally, Johns Hopkins University Applied Physics Laboratory" +msgstr "" + +#: ./doc/security-guide/ch002_why-and-how-we-wrote-this-book.xml:60(para) +msgid "Gregg Tally is the Chief Engineer at JHU/APL's Cyber Systems Group within the Asymmetric Operations Department. He works primarily in systems security engineering. Previously, he has worked at SPARTA, McAfee, and Trusted Information Systems where he was involved in cyber security research projects." +msgstr "" + +#: ./doc/security-guide/ch002_why-and-how-we-wrote-this-book.xml:63(para) +msgid "Eric Lopez, Nicira / VMware" +msgstr "" + +#: ./doc/security-guide/ch002_why-and-how-we-wrote-this-book.xml:64(para) +msgid "Eric Lopez is Senior Solution Architect at VMware's Networking and Security Business Unit where he helps customer implement OpenStack and Nicira's Network Virtualization Platform. Prior to joining Nicira, he worked for Q1 Labs, Symantec, Vontu, and Brightmail. He has a B.S in Electrical Engineering/Computer Science and Nuclear Engineering from U.C. Berkeley and MBA from the University of San Francisco." +msgstr "" + +#: ./doc/security-guide/ch002_why-and-how-we-wrote-this-book.xml:67(para) +msgid "Shawn Wells, Red Hat" +msgstr "" + +#: ./doc/security-guide/ch002_why-and-how-we-wrote-this-book.xml:68(para) +msgid "Shawn Wells is the Director, Innovation Programs at Red Hat, focused on improving the process of adopting, contributing to, and managing open source technologies within the U.S. Government. Additionally, Shawn is an upstream maintainer of the SCAP Security Guide project which forms virtualization and operating system hardening policy with the U.S. Military, NSA, and DISA. Formerly an NSA civilian, Shawn developed SIGINT collection systems utilizing large distributed computing infrastructures." +msgstr "" + +#: ./doc/security-guide/ch002_why-and-how-we-wrote-this-book.xml:71(para) +msgid "Ben de Bont, HP" +msgstr "" + +#: ./doc/security-guide/ch002_why-and-how-we-wrote-this-book.xml:72(para) +msgid "Ben de Bont is the CSO for HP Cloud Services. Prior to his current role Ben led the information security group at MySpace and the incident response team at MSN Security. Ben holds a master's degree in Computer Science from the Queensland University of Technology." +msgstr "" + +#: ./doc/security-guide/ch002_why-and-how-we-wrote-this-book.xml:75(para) +msgid "Nathanael Burton, National Security Agency" +msgstr "" + +#: ./doc/security-guide/ch002_why-and-how-we-wrote-this-book.xml:76(para) +msgid "Nathanael Burton is a Computer Scientist at the National Security Agency. He has worked for the Agency for over 10 years working on distributed systems, large-scale hosting, open source initiatives, operating systems, security, storage, and virtualization technology. He has a B.S. in Computer Science from Virginia Tech." +msgstr "" + +#: ./doc/security-guide/ch002_why-and-how-we-wrote-this-book.xml:79(emphasis) +msgid "Vibha Fauver" +msgstr "" + +#: ./doc/security-guide/ch002_why-and-how-we-wrote-this-book.xml:80(para) +msgid "Vibha Fauver, GWEB, CISSP, PMP, has over fifteen years of experience in Information Technology. Her areas of specialization include software engineering, project management and information security. She has a B.S. in Computer & Information Science and a M.S. in Engineering Management with specialization and a certificate in Systems Engineering." +msgstr "" + +#: ./doc/security-guide/ch002_why-and-how-we-wrote-this-book.xml:83(para) +msgid "Eric Windisch, Cloudscaling" +msgstr "" + +#: ./doc/security-guide/ch002_why-and-how-we-wrote-this-book.xml:84(para) +msgid "Eric Windisch is a Principal Engineer at Cloudscaling where he has been contributing to OpenStack for over two years. Eric has been in the trenches of hostile environments, building tenant isolation and infrastructure security through more than a decade of experience in the web hosting industry. He has been building cloud computing infrastructure and automation since 2007." +msgstr "" + +#: ./doc/security-guide/ch002_why-and-how-we-wrote-this-book.xml:87(para) +msgid "Andrew Hay, CloudPassage" +msgstr "" + +#: ./doc/security-guide/ch002_why-and-how-we-wrote-this-book.xml:88(para) +msgid "Andrew Hay is the Director of Applied Security Research at CloudPassage, Inc. where he leads the security research efforts for the company and its server security products purpose-built for dynamic public, private, and hybrid cloud hosting environments." +msgstr "" + +#: ./doc/security-guide/ch002_why-and-how-we-wrote-this-book.xml:91(emphasis) +msgid "Adam Hyde" +msgstr "" + +#: ./doc/security-guide/ch002_why-and-how-we-wrote-this-book.xml:92(para) +msgid "Adam facilitated this Book Sprint. He also founded the Book Sprint methodology and is the most experienced Book Sprint facilitator around. Adam founded FLOSS Manuals—a community of some 3,000 individuals developing Free Manuals about Free Software. He is also the founder and project manager for Booktype, an open source project for writing, editing, and publishing books online and in print." +msgstr "" + +#: ./doc/security-guide/ch002_why-and-how-we-wrote-this-book.xml:95(para) +msgid "During the sprint we also had help from Anne Gentle, Warren Wang, Paul McMillan, Brian Schott and Lorin Hochstein." +msgstr "" + +#: ./doc/security-guide/ch002_why-and-how-we-wrote-this-book.xml:96(para) +msgid "This Book was produced in a 5 day book sprint. A book sprint is an intensely collaborative, facilitated process which brings together a group to produce a book in 3-5 days. It is a strongly facilitated process with a specific methodology founded and developed by Adam Hyde. For more information visit the book sprint web page at http://www.booksprints.net." +msgstr "" + +#: ./doc/security-guide/ch002_why-and-how-we-wrote-this-book.xml:104(para) +msgid "After initial publication, the following added new content:" +msgstr "" + +#: ./doc/security-guide/ch002_why-and-how-we-wrote-this-book.xml:107(para) +msgid "Rodney D. Beede, Seagate Technology" +msgstr "" + +#: ./doc/security-guide/ch002_why-and-how-we-wrote-this-book.xml:110(para) +msgid "Rodney D. Beede is the Cloud Security Engineer for Seagate Technology. He contributed the missing chapter on securing OpenStack Object Storage (Swift). He holds a M.S. in Computer Science from the University of Colorado." +msgstr "" + +#: ./doc/security-guide/ch002_why-and-how-we-wrote-this-book.xml:119(title) +msgid "How to contribute to this book" +msgstr "" + +#: ./doc/security-guide/ch002_why-and-how-we-wrote-this-book.xml:120(para) +msgid "The initial work on this book was conducted in an overly air-conditioned room that served as our group office for the entirety of the documentation sprint." +msgstr "" + +#: ./doc/security-guide/ch002_why-and-how-we-wrote-this-book.xml:123(para) +msgid "Learn more about how to contribute to the OpenStack docs: http://wiki.openstack.org/Documentation/HowTo." +msgstr "" + +#: ./doc/security-guide/ch051_vss-intro.xml:3(title) +msgid "Hypervisor Selection" +msgstr "" + +#: ./doc/security-guide/ch051_vss-intro.xml:4(para) +msgid "Virtualization provides flexibility and other key benefits that enable cloud building. However, a virtualization stack also needs to be secured appropriately to reduce the risks associated with hypervisor breakout attacks. That is, while a virtualization stack can provide isolation between instances, or guest virtual machines, there are situations where that isolation can be less than perfect. Making intelligent selections for virtualization stack as well as following the best practices outlined in this chapter can be included in a layered approach to cloud security. Finally, securing your virtualization stack is critical in order to deliver on the promise of multi-tenant, either between customers in a public cloud, between business units in a private cloud, or some mixture of the two in a hybrid cloud." +msgstr "" + +#: ./doc/security-guide/ch051_vss-intro.xml:17(para) +msgid "In this chapter, we discuss the hypervisor selection process.  In the chapters that follow, we provide the foundational information needed for securing a virtualization stack." +msgstr "" + +#: ./doc/security-guide/ch051_vss-intro.xml:19(title) +msgid "Hypervisors in OpenStack" +msgstr "" + +#: ./doc/security-guide/ch051_vss-intro.xml:20(para) +msgid "Whether OpenStack is deployed within private data centers or as a public cloud service, the underlying virtualization technology provides enterprise-level capabilities in the realms of scalability, resource efficiency, and uptime. While such high-level benefits are generally available across many OpenStack-supported hypervisor technologies, there are significant differences in each hypervisor's security architecture and features, particularly when considering the security threat vectors which are unique to elastic OpenStack environments. As applications consolidate into single Infrastructure as a Service (IaaS) platforms, instance isolation at the hypervisor level becomes paramount. The requirement for secure isolation holds true across commercial, government, and military communities." +msgstr "" + +#: ./doc/security-guide/ch051_vss-intro.xml:21(para) +msgid "Within the framework of OpenStack you can choose from any number of hypervisor platforms and corresponding OpenStack plugins to optimize your cloud environment. In the context of the OpenStack Security guide, we will be highlighting hypervisor selection considerations as they pertain to feature sets that are critical to security. However, these considerations are not meant to be an exhaustive investigation into the pros and cons of particular hypervisors. NIST provides additional guidance in Special Publication 800-125, \"Guide to Security for Full Virtualization Technologies\"." +msgstr "" + +#: ./doc/security-guide/ch051_vss-intro.xml:24(title) +msgid "Selection Criteria" +msgstr "" + +#: ./doc/security-guide/ch051_vss-intro.xml:25(para) +msgid "As part of your hypervisor selection process, you will need to consider a number of important factors to help increase your security posture. Specifically, we will be looking into the following areas:" +msgstr "" + +#: ./doc/security-guide/ch051_vss-intro.xml:27(para) +msgid "Team Expertise" +msgstr "" + +#: ./doc/security-guide/ch051_vss-intro.xml:30(para) +msgid "Product or Project maturity" +msgstr "" + +#: ./doc/security-guide/ch051_vss-intro.xml:33(para) +msgid "Certifications, Attestations" +msgstr "" + +#: ./doc/security-guide/ch051_vss-intro.xml:36(para) ./doc/security-guide/ch051_vss-intro.xml:300(title) +msgid "Additional Security Features" +msgstr "" + +#: ./doc/security-guide/ch051_vss-intro.xml:39(para) ./doc/security-guide/ch051_vss-intro.xml:293(title) +msgid "Hypervisor vs. Baremetal" +msgstr "" + +#: ./doc/security-guide/ch051_vss-intro.xml:42(para) ./doc/security-guide/ch051_vss-intro.xml:255(title) +msgid "Hardware Concerns" +msgstr "" + +#: ./doc/security-guide/ch051_vss-intro.xml:45(para) ./doc/security-guide/ch051_vss-intro.xml:79(title) +msgid "Common Criteria" +msgstr "" + +#: ./doc/security-guide/ch051_vss-intro.xml:49(para) +msgid "Has the hypervisor undergone Common Criteria certification? If so, to what levels?" +msgstr "" + +#: ./doc/security-guide/ch051_vss-intro.xml:52(para) +msgid "Is the underlying cryptography certified by a third-party?" +msgstr "" + +#: ./doc/security-guide/ch051_vss-intro.xml:48(para) +msgid "Additionally, the following security-related criteria are highly encouraged to be evaluated when selecting a hypervisor for OpenStack deployments:Team Expertise Most likely, the most important aspect in hypervisor selection is the expertise of your staff in managing and maintaining a particular hypervisor platform. The more familiar your team is with a given product, its configuration, and its eccentricities, the less likely will there be configuration mistakes. Additionally, having staff expertise spread across an organization on a given hypervisor will increase availability of your systems, allow for developing a segregation of duties, and mitigate problems in the event that a team member is unavailable." +msgstr "" + +#: ./doc/security-guide/ch051_vss-intro.xml:56(title) +msgid "Product or Project Maturity" +msgstr "" + +#: ./doc/security-guide/ch051_vss-intro.xml:57(para) +msgid "The maturity of a given hypervisor product or project is critical to your security posture as well. Product maturity will have a number of effects once you have deployed your cloud, in the context of this security guide we are interested in the following:" +msgstr "" + +#: ./doc/security-guide/ch051_vss-intro.xml:59(para) +msgid "Availability of expertise" +msgstr "" + +#: ./doc/security-guide/ch051_vss-intro.xml:62(para) +msgid "Active developer and user communities" +msgstr "" + +#: ./doc/security-guide/ch051_vss-intro.xml:65(para) +msgid "Timeliness and Availability of updates" +msgstr "" + +#: ./doc/security-guide/ch051_vss-intro.xml:68(para) +msgid "Incidence response" +msgstr "" + +#: ./doc/security-guide/ch051_vss-intro.xml:71(para) +msgid "One of the biggest indicators of a hypervisor's maturity is the size and vibrancy of the community that surrounds it. As this concerns security, the quality of the community will affect the availability of expertise should you need additional cloud operators. It is also a sign of how widely deployed the hypervisor is, in turn leading to the battle readiness of any reference architectures and best practices." +msgstr "" + +#: ./doc/security-guide/ch051_vss-intro.xml:72(para) +msgid "Further, the quality of community, as it surrounds an open source hypervisor like KVM or Xen, will have a direct impact on the timeliness of bug fixes and security updates. When investigating both commercial and open source hypervisors, you will want to look into their release and support cycles as well as the time delta between the announcement of a bug or security issue and a patch or response. Lastly, the supported capabilities of OpenStack compute vary depending on the hypervisor chosen. Refer to the OpenStack Hypervisor Support Matrix for OpenStack compute feature support by hypervisor." +msgstr "" + +#: ./doc/security-guide/ch051_vss-intro.xml:75(title) +msgid "Certifications and Attestations" +msgstr "" + +#: ./doc/security-guide/ch051_vss-intro.xml:76(para) +msgid "One additional consideration when selecting a hypervisor is the availability of various formal certifications and attestations. While they may not be requirements for your specific organization, these certifications and attestations speak to the maturity, production readiness, and thoroughness of the testing a particular hypervisor platform has been subjected to." +msgstr "" + +#: ./doc/security-guide/ch051_vss-intro.xml:80(para) +msgid "Common Criteria is an internationally standardized software evaluation process, used by governments and commercial companies to validate software technologies perform as advertised. In the government sector, NSTISSP No. 11 mandates that U.S. Government agencies only procure software which has been Common Criteria certified, a policy which has been in place since July 2002. It should be specifically noted that OpenStack has not undergone Common Criteria certification, however many of the available hypervisors have." +msgstr "" + +#: ./doc/security-guide/ch051_vss-intro.xml:81(para) +msgid "In addition to validating a technologies capabilities, the Common Criteria process evaluates how technologies are developed." +msgstr "" + +#: ./doc/security-guide/ch051_vss-intro.xml:83(para) +msgid "How is source code management performed?" +msgstr "" + +#: ./doc/security-guide/ch051_vss-intro.xml:86(para) +msgid "How are users granted access to build systems?" +msgstr "" + +#: ./doc/security-guide/ch051_vss-intro.xml:89(para) +msgid "Is the technology cryptographically signed before distribution?" +msgstr "" + +#: ./doc/security-guide/ch051_vss-intro.xml:92(para) +msgid "The KVM hypervisor has been Common Criteria certified through the U.S. Government and commercial distributions, which have been validated to separate the runtime environment of virtual machines from each other, providing foundational technology to enforce instance isolation. In addition to virtual machine isolation, KVM has been Common Criteria certified to" +msgstr "" + +#: ./doc/security-guide/ch051_vss-intro.xml:94(para) +msgid "\"provide system-inherent separation mechanisms to the resources of virtual machines. This separation ensures that large software component used for virtualizing and simulating devices executing for each virtual machine cannot interfere with each other. Using the SELinux multi-category mechanism, the virtualization and simulation software instances are isolated. The virtual machine management framework configures SELinux multi-category settings transparently to the administrator\"" +msgstr "" + +#: ./doc/security-guide/ch051_vss-intro.xml:96(para) +msgid "While many hypervisor vendors, such as Red Hat, Microsoft, and VMWare have achieved Common Criteria Certification their underlying certified feature set differs. It is recommended to evaluate vendor claims to ensure they minimally satisfy the following requirements:" +msgstr "" + +#: ./doc/security-guide/ch051_vss-intro.xml:103(para) +msgid "Identification and Authentication" +msgstr "" + +#: ./doc/security-guide/ch051_vss-intro.xml:104(para) +msgid "Identification and authentication using pluggable authentication modules (PAM) based upon user passwords. The quality of the passwords used can be enforced through configuration options." +msgstr "" + +#: ./doc/security-guide/ch051_vss-intro.xml:107(para) +msgid "Audit" +msgstr "" + +#: ./doc/security-guide/ch051_vss-intro.xml:108(para) +msgid "The system provides the capability to audit a large number of events including individual system calls as well as events generated by trusted processes. Audit data is collected in regular files in ASCII format. The system provides a program for the purpose of searching the audit records." +msgstr "" + +#: ./doc/security-guide/ch051_vss-intro.xml:108(para) +msgid "The system administrator can define a rule base to restrict auditing to the events they are interested in. This includes the ability to restrict auditing to specific events, specific users, specific objects or a combination of all of this. " +msgstr "" + +#: ./doc/security-guide/ch051_vss-intro.xml:108(para) +msgid "Audit records can be transferred to a remote audit daemon." +msgstr "" + +#: ./doc/security-guide/ch051_vss-intro.xml:111(para) +msgid "Discretionary Access Control" +msgstr "" + +#: ./doc/security-guide/ch051_vss-intro.xml:113(para) +msgid "Discretionary Access Control (DAC) restricts access to file system objects based on Access Control Lists (ACLs) that include the standard UNIX permissions for user, group and others. Access control mechanisms also protect IPC objects from unauthorized access." +msgstr "" + +#: ./doc/security-guide/ch051_vss-intro.xml:122(para) +msgid "The system includes the ext4 file system, which supports POSIX ACLs. This allows defining access rights to files within this type of file system down to the granularity of a single user." +msgstr "" + +#: ./doc/security-guide/ch051_vss-intro.xml:130(para) +msgid "Mandatory Access Control" +msgstr "" + +#: ./doc/security-guide/ch051_vss-intro.xml:131(para) +msgid "Mandatory Access Control (MAC) restricts access to objects based on labels assigned to subjects and objects. Sensitivity labels are automatically attached to processes and objects. The access control policy enforced using these labels is derived from the BellLaPadula access control model." +msgstr "" + +#: ./doc/security-guide/ch051_vss-intro.xml:131(para) +msgid "SELinux categories are attached to virtual machines and its resources. The access control policy enforced using these categories grant virtual machines access to resources if the category of the virtual machine is identical to the category of the accessed resource." +msgstr "" + +#: ./doc/security-guide/ch051_vss-intro.xml:131(para) +msgid "The TOE implements non-hierarchical categories to control access to virtual machines." +msgstr "" + +#: ./doc/security-guide/ch051_vss-intro.xml:134(para) +msgid "Role-Based Access Control" +msgstr "" + +#: ./doc/security-guide/ch051_vss-intro.xml:135(para) +msgid "Role-based access control (RBAC) allows separation of roles to eliminate the need for an all-powerful system administrator." +msgstr "" + +#: ./doc/security-guide/ch051_vss-intro.xml:138(para) +msgid "Object Reuse" +msgstr "" + +#: ./doc/security-guide/ch051_vss-intro.xml:139(para) +msgid "File system objects as well as memory and IPC objects will be cleared before they can be reused by a process belonging to a different user." +msgstr "" + +#: ./doc/security-guide/ch051_vss-intro.xml:142(para) +msgid "Security Management" +msgstr "" + +#: ./doc/security-guide/ch051_vss-intro.xml:143(para) +msgid "The management of the security critical parameters of the system is performed by administrative users. A set of commands that require root privileges (or specific roles when RBAC is used) are used for system management. Security parameters are stored in specific files that are protected by the access control mechanisms of the system against unauthorized access by users that are not administrative users." +msgstr "" + +#: ./doc/security-guide/ch051_vss-intro.xml:146(para) +msgid "Secure Communication" +msgstr "" + +#: ./doc/security-guide/ch051_vss-intro.xml:147(para) +msgid "The system supports the definition of trusted channels using SSH. Password based authentication is supported. Only a restricted number of cipher suites are supported for those protocols in the evaluated configuration." +msgstr "" + +#: ./doc/security-guide/ch051_vss-intro.xml:150(para) +msgid "Storage Encryption" +msgstr "" + +#: ./doc/security-guide/ch051_vss-intro.xml:151(para) +msgid "The system supports encrypted block devices to provide storage confidentiality via dm_crypt." +msgstr "" + +#: ./doc/security-guide/ch051_vss-intro.xml:154(para) +msgid "TSF Protection" +msgstr "" + +#: ./doc/security-guide/ch051_vss-intro.xml:155(para) +msgid "While in operation, the kernel software and data are protected by the hardware memory protection mechanisms. The memory and process management components of the kernel ensure a user process cannot access kernel storage or storage belonging to other processes." +msgstr "" + +#: ./doc/security-guide/ch051_vss-intro.xml:155(para) +msgid "Non-kernel TSF software and data are protected by DAC and process isolation  mechanisms. In the evaluated configuration, the reserved user ID root owns the directories and files that define the TSF configuration. In general, files and directories containing internal TSF data, such as configuration files and batch job queues, are also protected from reading by DAC permissions." +msgstr "" + +#: ./doc/security-guide/ch051_vss-intro.xml:162(para) +msgid "The system and the hardware and firmware components are required to be physically protected from unauthorized access. The system kernel mediates all access to the hardware mechanisms themselves, other than program visible CPU instruction functions." +msgstr "" + +#: ./doc/security-guide/ch051_vss-intro.xml:162(para) +msgid "In addition, mechanisms for protection against stack overflow attacks are provided." +msgstr "" + +#: ./doc/security-guide/ch051_vss-intro.xml:169(title) +msgid "Cryptography Standards" +msgstr "" + +#: ./doc/security-guide/ch051_vss-intro.xml:170(para) +msgid "Several cryptography algorithms are available within OpenStack for identification and authorization, data transfer and protection of data at rest. When selecting a hypervisor, the following are recommended algorithms and implementation standards to ensure the virtualization layer supports:" +msgstr "" + +#: ./doc/security-guide/ch051_vss-intro.xml:180(emphasis) +msgid "Algorithm" +msgstr "" + +#: ./doc/security-guide/ch051_vss-intro.xml:181(emphasis) +msgid "Key Length" +msgstr "" + +#: ./doc/security-guide/ch051_vss-intro.xml:182(emphasis) +msgid "Intended Purpose" +msgstr "" + +#: ./doc/security-guide/ch051_vss-intro.xml:183(emphasis) +msgid "Security Function" +msgstr "" + +#: ./doc/security-guide/ch051_vss-intro.xml:184(emphasis) +msgid "Implementation Standard" +msgstr "" + +#: ./doc/security-guide/ch051_vss-intro.xml:187(para) +msgid "AES" +msgstr "" + +#: ./doc/security-guide/ch051_vss-intro.xml:188(para) +msgid "128 bits,192 bits," +msgstr "" + +#: ./doc/security-guide/ch051_vss-intro.xml:188(para) +msgid "256 bits" +msgstr "" + +#: ./doc/security-guide/ch051_vss-intro.xml:189(para) ./doc/security-guide/ch051_vss-intro.xml:196(para) +msgid "Encryption / Decryption" +msgstr "" + +#: ./doc/security-guide/ch051_vss-intro.xml:190(para) +msgid "Protected Data Transfer, Protection for Data at Rest" +msgstr "" + +#: ./doc/security-guide/ch051_vss-intro.xml:191(para) ./doc/security-guide/ch051_vss-intro.xml:198(para) +msgid "RFC 4253" +msgstr "" + +#: ./doc/security-guide/ch051_vss-intro.xml:194(para) +msgid "TDES" +msgstr "" + +#: ./doc/security-guide/ch051_vss-intro.xml:195(para) +msgid "168 bits" +msgstr "" + +#: ./doc/security-guide/ch051_vss-intro.xml:197(para) +msgid "Protected Data Transfer" +msgstr "" + +#: ./doc/security-guide/ch051_vss-intro.xml:201(para) +msgid "RSA" +msgstr "" + +#: ./doc/security-guide/ch051_vss-intro.xml:202(para) +msgid "1024 bits,2048 bits," +msgstr "" + +#: ./doc/security-guide/ch051_vss-intro.xml:202(para) +msgid "3072 bits " +msgstr "" + +#: ./doc/security-guide/ch051_vss-intro.xml:203(para) ./doc/security-guide/ch051_vss-intro.xml:210(para) +msgid "Authentication,Key Exchange " +msgstr "" + +#: ./doc/security-guide/ch051_vss-intro.xml:204(para) ./doc/security-guide/ch051_vss-intro.xml:211(para) +msgid "Identification and Authentication, Protected Data Transfer" +msgstr "" + +#: ./doc/security-guide/ch051_vss-intro.xml:205(para) ./doc/security-guide/ch051_vss-intro.xml:212(para) +msgid "U.S. NIST FIPS PUB 186-3" +msgstr "" + +#: ./doc/security-guide/ch051_vss-intro.xml:208(para) +msgid "DSA" +msgstr "" + +#: ./doc/security-guide/ch051_vss-intro.xml:209(para) +msgid "L=1024,N=160 bits " +msgstr "" + +#: ./doc/security-guide/ch051_vss-intro.xml:215(para) +msgid "Serpent" +msgstr "" + +#: ./doc/security-guide/ch051_vss-intro.xml:216(para) ./doc/security-guide/ch051_vss-intro.xml:223(para) +msgid "128, 196, or256 bit " +msgstr "" + +#: ./doc/security-guide/ch051_vss-intro.xml:217(para) ./doc/security-guide/ch051_vss-intro.xml:224(para) +msgid "Encryption /Decryption " +msgstr "" + +#: ./doc/security-guide/ch051_vss-intro.xml:218(para) ./doc/security-guide/ch051_vss-intro.xml:225(para) +msgid "Protection of Data at Rest" +msgstr "" + +#: ./doc/security-guide/ch051_vss-intro.xml:219(link) +msgid "http://www.cl.cam.ac.uk/~rja14/Papers/serpent.pdf" +msgstr "" + +#: ./doc/security-guide/ch051_vss-intro.xml:222(para) +msgid "Twofish" +msgstr "" + +#: ./doc/security-guide/ch051_vss-intro.xml:226(link) +msgid "http://www.schneier.com/paper-twofish-paper.html" +msgstr "" + +#: ./doc/security-guide/ch051_vss-intro.xml:229(para) +msgid "SHA-1" +msgstr "" + +#: ./doc/security-guide/ch051_vss-intro.xml:230(para) ./doc/security-guide/ch051_vss-intro.xml:237(para) +msgid "-" +msgstr "" + +#: ./doc/security-guide/ch051_vss-intro.xml:231(para) ./doc/security-guide/ch051_vss-intro.xml:238(para) +msgid "MessageDigest " +msgstr "" + +#: ./doc/security-guide/ch051_vss-intro.xml:232(para) +msgid "Protection of Data at Rest,Protected Data Transfer" +msgstr "" + +#: ./doc/security-guide/ch051_vss-intro.xml:233(para) ./doc/security-guide/ch051_vss-intro.xml:240(para) +msgid "U.S. NIST FIPS 180-3" +msgstr "" + +#: ./doc/security-guide/ch051_vss-intro.xml:236(para) +msgid "SHA-2(224-, 256-," +msgstr "" + +#: ./doc/security-guide/ch051_vss-intro.xml:236(para) +msgid "384-, 512 bit)" +msgstr "" + +#: ./doc/security-guide/ch051_vss-intro.xml:239(para) +msgid "Protection for Data at Rest,Identification and Authentication " +msgstr "" + +#: ./doc/security-guide/ch051_vss-intro.xml:246(title) +msgid "FIPS 140-2" +msgstr "" + +#: ./doc/security-guide/ch051_vss-intro.xml:247(para) +msgid "In the United States the National Institute of Science and Technology (NIST) certifies cryptographic algorithms through a process known the Cryptographic Module Validation Program. NIST certifies algorithms for conformance against Federal Information Processing Standard 140-2 (FIPS 140-2), which ensures:" +msgstr "" + +#: ./doc/security-guide/ch051_vss-intro.xml:249(emphasis) +msgid "Products validated as conforming to FIPS 140-2 are accepted by the Federal agencies of both countries [United States and Canada] for the protection of sensitive information (United States) or Designated Information (Canada). The goal of the CMVP is to promote the use of validated cryptographic modules and provide Federal agencies with a security metric to use in procuring equipment containing validated cryptographic modules." +msgstr "" + +#: ./doc/security-guide/ch051_vss-intro.xml:251(para) +msgid "When evaluating base hypervisor technologies, consider if the hypervisor has been certified against FIPS 140-2. Not only is conformance against FIPS 140-2 mandated per U.S. Government policy, formal certification indicates that a given implementation of a cryptographic algorithm has been reviewed for conformance against module specification, cryptographic module ports and interfaces; roles, services, and authentication; finite state model; physical security; operational environment; cryptographic key management; electromagnetic interference/electromagnetic compatibility (EMI/EMC); self-tests; design assurance; and mitigation of other attacks." +msgstr "" + +#: ./doc/security-guide/ch051_vss-intro.xml:256(para) +msgid "Further, when evaluating a hypervisor platform the supportability of the hardware the hypervisor will run on should be considered. Additionally, consider the additional features available in the hardware and how those features are supported by the hypervisor you chose as part of the OpenStack deployment. To that end, hypervisors will each have their own hardware compatibility lists (HCLs). When selecting compatible hardware it is important to know in advance which hardware-based virtualization technologies are important from a security perspective." +msgstr "" + +#: ./doc/security-guide/ch051_vss-intro.xml:264(emphasis) +msgid "Description" +msgstr "" + +#: ./doc/security-guide/ch051_vss-intro.xml:265(emphasis) +msgid "Technology" +msgstr "" + +#: ./doc/security-guide/ch051_vss-intro.xml:266(emphasis) +msgid "Explanation" +msgstr "" + +#: ./doc/security-guide/ch051_vss-intro.xml:269(para) +msgid "I/O MMU" +msgstr "" + +#: ./doc/security-guide/ch051_vss-intro.xml:270(para) +msgid "VT-d / AMD-Vi" +msgstr "" + +#: ./doc/security-guide/ch051_vss-intro.xml:271(para) +msgid "Required for protecting PCI-passthrough" +msgstr "" + +#: ./doc/security-guide/ch051_vss-intro.xml:274(para) +msgid "Intel Trusted Execution Technology" +msgstr "" + +#: ./doc/security-guide/ch051_vss-intro.xml:275(para) +msgid "Intel TXT / SEM" +msgstr "" + +#: ./doc/security-guide/ch051_vss-intro.xml:276(para) +msgid "Required for dynamic attestation services" +msgstr "" + +#: ./doc/security-guide/ch051_vss-intro.xml:279(para) +msgid "PCI-SIG I/O virtualization" +msgstr "" + +#: ./doc/security-guide/ch051_vss-intro.xml:280(para) +msgid "SR-IOV, MR-IOV, ATS" +msgstr "" + +#: ./doc/security-guide/ch051_vss-intro.xml:281(para) +msgid "Required to allow secure sharing of PCI Express devices" +msgstr "" + +#: ./doc/security-guide/ch051_vss-intro.xml:284(para) +msgid "Network virtualization" +msgstr "" + +#: ./doc/security-guide/ch051_vss-intro.xml:285(para) +msgid "VT-c" +msgstr "" + +#: ./doc/security-guide/ch051_vss-intro.xml:286(para) +msgid "Improves performance of network I/O on hypervisors" +msgstr "" + +#: ./doc/security-guide/ch051_vss-intro.xml:294(para) +msgid "To wrap up our discussion around hypervisor selection, it is important to call out the differences between using LXC (Linux Containers) or Baremetal systems vs using a hypervisor like KVM. Specifically, the focus of this security guide will be largely based on having a hypervisor and virtualization platform. However, should your implementation require the use of a baremetal or LXC environment, you will want to pay attention to the particular differences in regard to deployment of that environment. In particular, you will need to provide your end users with assurances that the node has been properly sanitized of their data prior to re-provisioning. Additionally, prior to reusing a node, you will need to provide assurances that the hardware has not been tampered or otherwise compromised." +msgstr "" + +#: ./doc/security-guide/ch051_vss-intro.xml:295(para) +msgid "It should be noted that while OpenStack has a baremetal project, a discussion of the particular security implications of running baremetal is beyond the scope of this book." +msgstr "" + +#: ./doc/security-guide/ch051_vss-intro.xml:296(para) +msgid "Finally, due to the time constraints around a book sprint, the team chose to use KVM as the hypervisor in our example implementations and architectures." +msgstr "" + +#: ./doc/security-guide/ch051_vss-intro.xml:297(para) +msgid "There is an OpenStack Security Note pertaining to the use of LXC in Nova." +msgstr "" + +#: ./doc/security-guide/ch051_vss-intro.xml:301(para) +msgid "Another thing to look into when selecting a hypervisor platform is the availability of specific security features. In particular, we are referring to features like Xen Server's XSM or Xen Security Modules, sVirt, Intel TXT, and AppArmor. The presence of these features will help increase your security profile as well as provide a good foundation." +msgstr "" + +#: ./doc/security-guide/ch051_vss-intro.xml:302(para) +msgid "The following table calls out these features by common hypervisor platforms. " +msgstr "" + +#: ./doc/security-guide/ch051_vss-intro.xml:315(para) ./doc/security-guide/ch051_vss-intro.xml:327(para) ./doc/security-guide/ch051_vss-intro.xml:336(para) ./doc/security-guide/ch051_vss-intro.xml:338(para) ./doc/security-guide/ch051_vss-intro.xml:340(para) ./doc/security-guide/ch051_vss-intro.xml:341(para) ./doc/security-guide/ch051_vss-intro.xml:346(para) ./doc/security-guide/ch051_vss-intro.xml:347(para) ./doc/security-guide/ch051_vss-intro.xml:348(para) ./doc/security-guide/ch051_vss-intro.xml:350(para) ./doc/security-guide/ch051_vss-intro.xml:351(para) ./doc/security-guide/ch051_vss-intro.xml:352(para) ./doc/security-guide/ch051_vss-intro.xml:356(para) ./doc/security-guide/ch051_vss-intro.xml:357(para) ./doc/security-guide/ch051_vss-intro.xml:358(para) ./doc/security-guide/ch051_vss-intro.xml:359(para) ./doc/security-guide/ch051_vss-intro.xml:360(para) ./doc/security-guide/ch051_vss-intro.xml:361(para) ./doc/security-guide/ch051_vss-intro.xml:362(para) ./doc/security-guide/ch012_configuration-management.xml:95(para) ./doc/security-guide/ch012_configuration-management.xml:100(emphasis) +msgid " " +msgstr "" + +#: ./doc/security-guide/ch051_vss-intro.xml:316(para) +msgid "KSM" +msgstr "" + +#: ./doc/security-guide/ch051_vss-intro.xml:317(para) +msgid "XSM" +msgstr "" + +#: ./doc/security-guide/ch051_vss-intro.xml:318(para) +msgid "sVirt" +msgstr "" + +#: ./doc/security-guide/ch051_vss-intro.xml:319(para) +msgid "TXT" +msgstr "" + +#: ./doc/security-guide/ch051_vss-intro.xml:320(para) +msgid "AppArmor" +msgstr "" + +#: ./doc/security-guide/ch051_vss-intro.xml:321(para) +msgid "cGroups" +msgstr "" + +#: ./doc/security-guide/ch051_vss-intro.xml:322(para) +msgid "MAC Policy" +msgstr "" + +#: ./doc/security-guide/ch051_vss-intro.xml:325(para) +msgid "KVM" +msgstr "" + +#: ./doc/security-guide/ch051_vss-intro.xml:326(para) ./doc/security-guide/ch051_vss-intro.xml:328(para) ./doc/security-guide/ch051_vss-intro.xml:329(para) ./doc/security-guide/ch051_vss-intro.xml:337(para) +msgid "X" +msgstr "" + +#: ./doc/security-guide/ch051_vss-intro.xml:330(address) ./doc/security-guide/ch051_vss-intro.xml:331(para) ./doc/security-guide/ch051_vss-intro.xml:332(para) ./doc/security-guide/ch051_vss-intro.xml:342(para) +msgid "x" +msgstr "" + +#: ./doc/security-guide/ch051_vss-intro.xml:335(para) +msgid "Xen" +msgstr "" + +#: ./doc/security-guide/ch051_vss-intro.xml:339(para) ./doc/security-guide/ch051_vss-intro.xml:349(para) +msgid " X" +msgstr "" + +#: ./doc/security-guide/ch051_vss-intro.xml:345(para) +msgid "ESXi" +msgstr "" + +#: ./doc/security-guide/ch051_vss-intro.xml:355(para) +msgid "Hyper-V" +msgstr "" + +#: ./doc/security-guide/ch051_vss-intro.xml:367(link) +msgid "KSM: Kernel Samepage Merging" +msgstr "" + +#: ./doc/security-guide/ch051_vss-intro.xml:368(link) +msgid "XSM: Xen Security Modules" +msgstr "" + +#: ./doc/security-guide/ch051_vss-intro.xml:369(link) +msgid "xVirt: Mandatory Access Control for Linux-based virtualization" +msgstr "" + +#: ./doc/security-guide/ch051_vss-intro.xml:370(link) +msgid "TXT: Intel Trusted Execution Technology" +msgstr "" + +#: ./doc/security-guide/ch051_vss-intro.xml:371(link) +msgid "AppArmor: Linux security module implementing MAC" +msgstr "" + +#: ./doc/security-guide/ch051_vss-intro.xml:372(link) +msgid "cgroups: Linux kernel feature to control resource usage" +msgstr "" + +#: ./doc/security-guide/ch051_vss-intro.xml:373(para) +msgid "MAC Policy: Mandatory Access Control; may be implemented with SELinux or other operating systems" +msgstr "" + +#: ./doc/security-guide/ch051_vss-intro.xml:374(para) +msgid "* Features in this table may not be applicable to all hypervisors or directly mappable between hypervisors." +msgstr "" + +#: ./doc/security-guide/ch017_threat-models-confidence-and-confidentiality.xml:3(title) +msgid "Introduction to SSL/TLS" +msgstr "" + +#: ./doc/security-guide/ch017_threat-models-confidence-and-confidentiality.xml:4(para) +msgid "OpenStack services receive requests on behalf of users on public networks as well as from other internal services over management networks. Inter-service communications can also occur over public networks depending on deployment and architecture choices." +msgstr "" + +#: ./doc/security-guide/ch017_threat-models-confidence-and-confidentiality.xml:5(para) +msgid "While it is commonly accepted that data over public networks should be secured using cryptographic measures, such as Secure Sockets Layer or Transport Layer Security (SSL/TLS) protocols, it is insufficient to rely on security domain separation to protect internal traffic. Using a security-in-depth approach, we recommend securing all domains with SSL/TLS, including the management domain services. It is important that should a tenant escape their VM isolation and gain access to the hypervisor or host resources, compromise an API endpoint, or any other service, they must not be able to easily inject or capture messages, commands, or otherwise affect or control management capabilities of the cloud. SSL/TLS provides the mechanisms to ensure authentication, non-repudiation, confidentiality, and integrity of user communications to the OpenStack services and between the OpenStack services themselves." +msgstr "" + +#: ./doc/security-guide/ch017_threat-models-confidence-and-confidentiality.xml:6(para) +msgid "Public Key Infrastructure (PKI) is the set of hardware, software, and policies to operate a secure system which provides authentication, non-repudiation, confidentiality, and integrity. The core components of PKI are:" +msgstr "" + +#: ./doc/security-guide/ch017_threat-models-confidence-and-confidentiality.xml:8(para) +msgid "End Entity - user, process, or system that is the subject of a certificate" +msgstr "" + +#: ./doc/security-guide/ch017_threat-models-confidence-and-confidentiality.xml:11(para) +msgid "Certification Authority (CA) - defines certificate policies, management, and issuance of certificates" +msgstr "" + +#: ./doc/security-guide/ch017_threat-models-confidence-and-confidentiality.xml:14(para) +msgid "Registration Authority (RA) - an optional system to which a CA delegates certain management functions" +msgstr "" + +#: ./doc/security-guide/ch017_threat-models-confidence-and-confidentiality.xml:17(para) +msgid "Repository - Where the end entity certificates and certificate revocation lists are stored and looked up - sometimes referred to as the \"certificate bundle\"" +msgstr "" + +#: ./doc/security-guide/ch017_threat-models-confidence-and-confidentiality.xml:20(para) +msgid "Relying Party - The end point that is trusting that the CA is valid." +msgstr "" + +#: ./doc/security-guide/ch017_threat-models-confidence-and-confidentiality.xml:23(para) +msgid "PKI builds the framework on which to provide encryption algorithms, cipher modes, and protocols for securing data and authentication. We strongly recommend securing all services with Public Key Infrastructure (PKI), including the use of SSL/TLS for API endpoints. It is impossible for the encryption or signing of transports or messages alone to solve all these problems. Hosts themselves must be secure and implement policy, namespaces, and other controls to protect their private credentials and keys. However, the challenges of key management and protection do not reduce the necessity of these controls, or lessen their importance." +msgstr "" + +#: ./doc/security-guide/ch017_threat-models-confidence-and-confidentiality.xml:25(title) +msgid "Certification Authorities" +msgstr "" + +#: ./doc/security-guide/ch017_threat-models-confidence-and-confidentiality.xml:26(para) +msgid "Many organizations have an established Public Key Infrastructure with their own certification authority (CA), certificate policies, and management for which they should use to issue certificates for internal OpenStack users or services. Organizations in which the public security domain is Internet facing will additionally need certificates signed by a widely recognized public CA. For cryptographic communications over the management network, it is recommended one not use a public CA. Instead, we expect and recommend most deployments deploy their own internal CA." +msgstr "" + +#: ./doc/security-guide/ch017_threat-models-confidence-and-confidentiality.xml:27(para) +msgid "It is recommended that the OpenStack cloud architect consider using separate PKI deployments for internal systems and customer facing services. This allows the cloud deployer to maintain control of their PKI infrastructure and among other things makes requesting, signing and deploying certificates for internal systems easier. Advanced configurations may use separate PKI deployments for different security domains. This allows deployers to maintain cryptographic separation of environments, ensuring that certificates issued to one are not recognised by another." +msgstr "" + +#: ./doc/security-guide/ch017_threat-models-confidence-and-confidentiality.xml:28(para) +msgid "Certificates used to support SSL/TLS on internet facing cloud endpoints (or customer interfaces where the customer is not expected to have installed anything other than standard operating system provided certificate bundles) should be provisioned using Certificate Authorities that are installed in the operating system certificate bundle. Typical well known vendors include Verisign and Thawte but many others exist." +msgstr "" + +#: ./doc/security-guide/ch017_threat-models-confidence-and-confidentiality.xml:29(para) +msgid "There are many management, policy, and technical challenges around creating and signing certificates as such is an area where cloud architects or operators may wish to seek the advice of industry leaders and vendors in addition to the guidance recommended here." +msgstr "" + +#: ./doc/security-guide/ch017_threat-models-confidence-and-confidentiality.xml:32(title) +msgid "SSL/TLS Libraries" +msgstr "" + +#: ./doc/security-guide/ch017_threat-models-confidence-and-confidentiality.xml:33(para) +msgid "Various components, services, and applications within the OpenStack ecosystem or dependencies of OpenStack are implemented and can be configured to use SSL/TLS libraries. The SSL/TLS and HTTP services within OpenStack are typically implemented using OpenSSL which has been proven to be fairly secure and has a module that has been validated for FIPS 140-2. However, keep in mind that each application or service can still introduce weaknesses in how they use the OpenSSL libraries." +msgstr "" + +#: ./doc/security-guide/ch017_threat-models-confidence-and-confidentiality.xml:36(title) +msgid "Cryptographic Algorithms, Cipher Modes, and Protocols" +msgstr "" + +#: ./doc/security-guide/ch017_threat-models-confidence-and-confidentiality.xml:37(para) +msgid "We recommend only using TLS v1.1 or v1.2. SSLv3 and TLSv1.0 may be used for compatibility but we recommend using caution and only enabling these protocols if you have a strong requirement to do so. Other SSL/TLS versions, explicitly older versions, should not be used. These older versions include SSLv1 and SSLv2. As this book does not intend to be a thorough reference on cryptography we do not wish to be prescriptive about what specific algorithms or cipher modes you should enable or disable in your OpenStack services. However, there are some authoritative references we would like to recommend for further information:" +msgstr "" + +#: ./doc/security-guide/ch017_threat-models-confidence-and-confidentiality.xml:39(link) +msgid "National Security Agency, Suite B Cryptography" +msgstr "" + +#: ./doc/security-guide/ch017_threat-models-confidence-and-confidentiality.xml:42(link) +msgid "OWASP Guide to Cryptography" +msgstr "" + +#: ./doc/security-guide/ch017_threat-models-confidence-and-confidentiality.xml:45(link) +msgid "OWASP Transport Layer Protection Cheat Sheet" +msgstr "" + +#: ./doc/security-guide/ch017_threat-models-confidence-and-confidentiality.xml:48(link) +msgid "SoK: SSL and HTTPS: Revisiting past challenges and evaluating certificate trust model enhancements" +msgstr "" + +#: ./doc/security-guide/ch017_threat-models-confidence-and-confidentiality.xml:51(link) +msgid "The Most Dangerous Code in the World: Validating SSL Certificates in Non-Browser Software" +msgstr "" + +#: ./doc/security-guide/ch017_threat-models-confidence-and-confidentiality.xml:54(link) +msgid "OpenSSL and FIPS 140-2" +msgstr "" + +#: ./doc/security-guide/ch017_threat-models-confidence-and-confidentiality.xml:59(title) +msgid "Summary" +msgstr "" + +#: ./doc/security-guide/ch017_threat-models-confidence-and-confidentiality.xml:60(para) +msgid "Given the complexity of the OpenStack components and the number of deployment possibilities, you must take care to ensure that each component gets the appropriate configuration of SSL certificates, keys, and CAs. The following services will be discussed in later sections of this book where SSL and PKI is available (either natively or possible via SSL proxy):" +msgstr "" + +#: ./doc/security-guide/ch017_threat-models-confidence-and-confidentiality.xml:62(para) +msgid "Compute API endpoints" +msgstr "" + +#: ./doc/security-guide/ch017_threat-models-confidence-and-confidentiality.xml:65(para) +msgid "Identity API endpoints" +msgstr "" + +#: ./doc/security-guide/ch017_threat-models-confidence-and-confidentiality.xml:68(para) +msgid "Networking API endpoints" +msgstr "" + +#: ./doc/security-guide/ch017_threat-models-confidence-and-confidentiality.xml:71(para) +msgid "Storage API endpoints" +msgstr "" + +#: ./doc/security-guide/ch017_threat-models-confidence-and-confidentiality.xml:74(para) +msgid "Messaging server" +msgstr "" + +#: ./doc/security-guide/ch017_threat-models-confidence-and-confidentiality.xml:77(para) +msgid "Database server" +msgstr "" + +#: ./doc/security-guide/ch017_threat-models-confidence-and-confidentiality.xml:80(para) ./doc/security-guide/ch014_best-practices-for-operator-mode-access.xml:23(title) ./doc/security-guide/ch004_book-introduction.xml:186(title) ./doc/security-guide/ch025_web-dashboard.xml:8(title) +msgid "Dashboard" +msgstr "" + +#: ./doc/security-guide/ch017_threat-models-confidence-and-confidentiality.xml:83(para) +msgid "Throughout this book we will use SSL as shorthand to refer to these recommendations for SSL/TLS protocols." +msgstr "" + +#: ./doc/security-guide/ch012_configuration-management.xml:8(title) +msgid "Continuous Systems Management" +msgstr "" + +#: ./doc/security-guide/ch012_configuration-management.xml:9(para) +msgid "A cloud will always have bugs. Some of these will be security problems. For this reason, it is critically important to be prepared to apply security updates and general software updates. This involves smart use of configuration management tools, which are discussed below. This also involves knowing when an upgrade is necessary." +msgstr "" + +#: ./doc/security-guide/ch012_configuration-management.xml:16(title) ./doc/security-guide/ch063_compliance-activities.xml:43(title) +msgid "Vulnerability Management" +msgstr "" + +#: ./doc/security-guide/ch012_configuration-management.xml:17(para) +msgid "For announcements regarding security relevant changes, subscribe to the OpenStack Announce mailing list. The security notifications are also posted through the downstream packages for example through Linux distributions that you may be subscribed to as part of the package updates." +msgstr "" + +#: ./doc/security-guide/ch012_configuration-management.xml:24(para) +msgid "The OpenStack components are only a small fraction of the software in a cloud. It is important to keep up to date with all of these other components, too. While the specific data sources will be deployment specific, the key idea is to ensure that a cloud administrator subscribes to the necessary mailing lists for receiving notification of any related security updates. Often this is as simple as tracking an upstream Linux distribution." +msgstr "" + +#: ./doc/security-guide/ch012_configuration-management.xml:36(para) +msgid "OpenStack Security Advisories (OSSA) are created by the OpenStack Vulnerability Management Team (VMT). They pertain to security holes in core OpenStack services. More information on the VMT can be found here: https://wiki.openstack.org/wiki/Vulnerability_Management" +msgstr "" + +#: ./doc/security-guide/ch012_configuration-management.xml:44(para) +msgid "OpenStack Security Notes (OSSN) were created by the OpenStack Security Group (OSSG) to support the work of the VMT. OSSN address issues in supporting software and common deployment configurations. They're referenced throughout this guide. Security Notes are archived at https://launchpad.net/ossn/" +msgstr "" + +#: ./doc/security-guide/ch012_configuration-management.xml:33(para) +msgid "OpenStack releases security information through two channels. " +msgstr "" + +#: ./doc/security-guide/ch012_configuration-management.xml:56(title) +msgid "Triage" +msgstr "" + +#: ./doc/security-guide/ch012_configuration-management.xml:57(para) +msgid "After you are notified of a security update, the next step is to determine how critical this update is to a given cloud deployment. In this case, it is useful to have a pre-defined policy. Existing vulnerability rating systems such as the common vulnerability scoring system (CVSS) v2 do not properly account for cloud deployments." +msgstr "" + +#: ./doc/security-guide/ch012_configuration-management.xml:63(para) +msgid "In this example we introduce a scoring matrix that places vulnerabilities in three categories: Privilege Escalation, Denial of Service and Information Disclosure. Understanding the type of vulnerability and where it occurs in your infrastructure will enable you to make reasoned response decisions." +msgstr "" + +#: ./doc/security-guide/ch012_configuration-management.xml:69(para) +msgid "Privilege Escalation describes the ability of a user to act with the privileges of some other user in a system, bypassing appropriate authorization checks. For example, a standard Linux user running code or performing an operation that allows them to conduct further operations with the privileges of the root users on the system." +msgstr "" + +#: ./doc/security-guide/ch012_configuration-management.xml:75(para) +msgid "Denial of Service refers to an exploited vulnerability that may cause service or system disruption. This includes both distributed attacks to overwhelm network resources, and single-user attacks that are typically caused through resource allocation bugs or input induced system failure flaws." +msgstr "" + +#: ./doc/security-guide/ch012_configuration-management.xml:80(para) +msgid "Information Disclosure vulnerabilities reveal information about your system or operations. These vulnerabilities range from debugging information disclosure, to exposure of critical security data, such as authentication credentials and passwords." +msgstr "" + +#: ./doc/security-guide/ch012_configuration-management.xml:96(emphasis) +msgid "Attacker Position / Privilege Level" +msgstr "" + +#: ./doc/security-guide/ch012_configuration-management.xml:102(emphasis) +msgid "External" +msgstr "" + +#: ./doc/security-guide/ch012_configuration-management.xml:103(emphasis) +msgid "Cloud User" +msgstr "" + +#: ./doc/security-guide/ch012_configuration-management.xml:105(emphasis) +msgid "Cloud Admin" +msgstr "" + +#: ./doc/security-guide/ch012_configuration-management.xml:107(emphasis) +msgid "Control Plane" +msgstr "" + +#: ./doc/security-guide/ch012_configuration-management.xml:111(emphasis) +msgid "Privilege Elevation (3 levels)" +msgstr "" + +#: ./doc/security-guide/ch012_configuration-management.xml:113(para) ./doc/security-guide/ch012_configuration-management.xml:121(para) ./doc/security-guide/ch012_configuration-management.xml:122(para) ./doc/security-guide/ch012_configuration-management.xml:129(para) ./doc/security-guide/ch012_configuration-management.xml:130(para) ./doc/security-guide/ch012_configuration-management.xml:131(para) +msgid "Critical" +msgstr "" + +#: ./doc/security-guide/ch012_configuration-management.xml:114(para) ./doc/security-guide/ch012_configuration-management.xml:115(para) ./doc/security-guide/ch012_configuration-management.xml:116(para) ./doc/security-guide/ch012_configuration-management.xml:123(para) ./doc/security-guide/ch012_configuration-management.xml:124(para) ./doc/security-guide/ch012_configuration-management.xml:132(para) +msgid "n/a" +msgstr "" + +#: ./doc/security-guide/ch012_configuration-management.xml:119(emphasis) +msgid "Privilege Elevation (2 levels)" +msgstr "" + +#: ./doc/security-guide/ch012_configuration-management.xml:127(emphasis) +msgid "Privilege Elevation (1 level)" +msgstr "" + +#: ./doc/security-guide/ch012_configuration-management.xml:135(emphasis) +msgid "Denial of Service" +msgstr "" + +#: ./doc/security-guide/ch012_configuration-management.xml:137(para) +msgid "High" +msgstr "" + +#: ./doc/security-guide/ch012_configuration-management.xml:138(para) +msgid "Medium" +msgstr "" + +#: ./doc/security-guide/ch012_configuration-management.xml:139(para) ./doc/security-guide/ch012_configuration-management.xml:140(para) ./doc/security-guide/ch012_configuration-management.xml:148(para) +msgid "Low" +msgstr "" + +#: ./doc/security-guide/ch012_configuration-management.xml:143(emphasis) +msgid "Information Disclosure" +msgstr "" + +#: ./doc/security-guide/ch012_configuration-management.xml:145(para) ./doc/security-guide/ch012_configuration-management.xml:146(para) +msgid "Critical / High" +msgstr "" + +#: ./doc/security-guide/ch012_configuration-management.xml:147(para) +msgid "Medium / Low" +msgstr "" + +#: ./doc/security-guide/ch012_configuration-management.xml:152(para) +msgid "This table illustrates a generic approach to measuring the impact of a vulnerability based on where it occurs in your deployment and the effect. For example, a single level privilege escalation on a Compute API node potentially allows a standard user of the API to escalate to have the same privileges as the root user on the node." +msgstr "" + +#: ./doc/security-guide/ch012_configuration-management.xml:158(para) +msgid "We suggest that cloud administrators use this table as a model to help define which actions to take for the various security levels. For example, a critical-level security update might require the cloud to be upgraded on a specified time line, whereas a low-level update might be more relaxed." +msgstr "" + +#: ./doc/security-guide/ch012_configuration-management.xml:165(title) +msgid "Testing the Updates" +msgstr "" + +#: ./doc/security-guide/ch012_configuration-management.xml:166(para) +msgid "You should test any update before you deploy it in a production environment. Typically this requires having a separate test cloud setup that first receives the update. This cloud should be as close to the production cloud as possible, in terms of software and hardware. Updates should be tested thoroughly in terms of performance impact, stability, application impact, and more. Especially important is to verify that the problem theoretically addressed by the update, such as a specific vulnerability, is actually fixed." +msgstr "" + +#: ./doc/security-guide/ch012_configuration-management.xml:177(title) +msgid "Deploying the Updates" +msgstr "" + +#: ./doc/security-guide/ch012_configuration-management.xml:178(para) +msgid "Once the updates are fully tested, they can be deployed to the production environment. This deployment should be fully automated using the configuration management tools described below." +msgstr "" + +#: ./doc/security-guide/ch012_configuration-management.xml:185(title) +msgid "Configuration Management" +msgstr "" + +#: ./doc/security-guide/ch012_configuration-management.xml:186(para) +msgid "A production quality cloud should always use tools to automate configuration and deployment. This eliminates human error, and allows the cloud to scale much more rapidly. Automation also helps with continuous integration and testing." +msgstr "" + +#: ./doc/security-guide/ch012_configuration-management.xml:191(para) +msgid "When building an OpenStack cloud it is strongly recommended to approach your design and implementation with a configuration management tool or framework in mind. Configuration management allows you to avoid the many pitfalls inherent in building, managing, and maintaining an infrastructure as complex as OpenStack. By producing the manifests, cookbooks, or templates required for a configuration management utility, you are able to satisfy a number of documentation and regulatory reporting requirements. Further, configuration management can also function as part of your BCP and DR plans wherein you can rebuild a node or service back to a known state in a DR event or given a compromise." +msgstr "" + +#: ./doc/security-guide/ch012_configuration-management.xml:203(para) +msgid "Additionally, when combined with a version control system such as Git or SVN, you can track changes to your environment over time and re-mediate unauthorized changes that may occur. For example, a nova.conf file or other configuration file falls out of compliance with your standard, your configuration management tool can revert or replace the file and bring your configuration back into a known state. Finally a configuration management tool can also be used to deploy updates; simplifying the security patch process. These tools have a broad range of capabilities that are useful in this space. The key point for securing your cloud is to choose a tool for configuration management and use it." +msgstr "" + +#: ./doc/security-guide/ch012_configuration-management.xml:215(para) +msgid "There are many configuration management solutions; at the time of this writing there are two in the marketplace that are robust in their support of OpenStack environments: Chef and Puppet. A non-exhaustive listing of tools in this space is provided below:" +msgstr "" + +#: ./doc/security-guide/ch012_configuration-management.xml:223(para) +msgid "Chef" +msgstr "" + +#: ./doc/security-guide/ch012_configuration-management.xml:226(para) +msgid "Puppet" +msgstr "" + +#: ./doc/security-guide/ch012_configuration-management.xml:229(para) +msgid "Salt Stack" +msgstr "" + +#: ./doc/security-guide/ch012_configuration-management.xml:232(para) +msgid "Ansible" +msgstr "" + +#: ./doc/security-guide/ch012_configuration-management.xml:236(title) +msgid "Policy Changes" +msgstr "" + +#: ./doc/security-guide/ch012_configuration-management.xml:237(para) +msgid "Whenever a policy or configuration management is changed, it is good practice to log the activity, and backup a copy of the new set. Often, such policies and configurations are stored in a version controlled repository such as git." +msgstr "" + +#: ./doc/security-guide/ch012_configuration-management.xml:244(title) +msgid "Secure Backup and Recovery" +msgstr "" + +#: ./doc/security-guide/ch012_configuration-management.xml:245(para) +msgid "It is important to include Backup procedures and policies in the overall System Security Plan. For a good overview of OpenStack's Backup and Recovery capabilities and procedures, please refer to the OpenStack Operations Guide." +msgstr "" + +#: ./doc/security-guide/ch012_configuration-management.xml:250(title) ./doc/security-guide/ch014_best-practices-for-operator-mode-access.xml:45(title) ./doc/security-guide/ch014_best-practices-for-operator-mode-access.xml:82(title) ./doc/security-guide/ch014_best-practices-for-operator-mode-access.xml:113(title) ./doc/security-guide/ch014_best-practices-for-operator-mode-access.xml:132(title) ./doc/security-guide/ch026_compute.xml:23(title) ./doc/security-guide/ch026_compute.xml:57(title) +msgid "Security Considerations" +msgstr "" + +#: ./doc/security-guide/ch012_configuration-management.xml:253(para) +msgid "Ensure only authenticated users and backup clients have access to the backup server." +msgstr "" + +#: ./doc/security-guide/ch012_configuration-management.xml:257(para) +msgid "Use data encryption options for storage and transmission of backups." +msgstr "" + +#: ./doc/security-guide/ch012_configuration-management.xml:261(para) +msgid "Use a dedicated and hardened backup servers. The logs for the backup server must be monitored daily and accessible by only few individuals." +msgstr "" + +#: ./doc/security-guide/ch012_configuration-management.xml:266(para) +msgid "Test data recovery options regularly. One of the things that can be restored from secured backups is the images. In case of a compromise, the best practice would be to terminate running instances immediately and then relaunch the instances from the images in the secured backup repository." +msgstr "" + +#: ./doc/security-guide/ch012_configuration-management.xml:276(title) ./doc/security-guide/ch014_best-practices-for-operator-mode-access.xml:64(title) ./doc/security-guide/ch014_best-practices-for-operator-mode-access.xml:123(title) ./doc/security-guide/ch014_best-practices-for-operator-mode-access.xml:157(title) ./doc/security-guide/ch026_compute.xml:33(title) ./doc/security-guide/ch026_compute.xml:70(title) ./doc/security-guide/ch058_forensicsincident-response.xml:43(title) +msgid "References" +msgstr "" + +#: ./doc/security-guide/ch012_configuration-management.xml:279(para) +msgid "OpenStack Operations Guide on backup and recovery" +msgstr "" + +#: ./doc/security-guide/ch012_configuration-management.xml:287(link) +msgid "http://www.sans.org/reading_room/whitepapers/backup/security-considerations-enterprise-level-backups_515" +msgstr "" + +#: ./doc/security-guide/ch012_configuration-management.xml:291(link) +msgid "OpenStack Security Primer" +msgstr "" + +#: ./doc/security-guide/ch012_configuration-management.xml:297(title) +msgid "Security Auditing Tools" +msgstr "" + +#: ./doc/security-guide/ch012_configuration-management.xml:298(para) +msgid "Security auditing tools can complement the configuration management tools.  Security auditing tools automate the process of verifying that a large number of security controls are satisfied for a given system configuration. These tools help to bridge the gap from security configuration guidance documentation (for example, the STIG and NSA Guides) to a specific system installation. For example, SCAP can compare a running system to a pre-defined profile. SCAP outputs a report detailing which controls in the profile were satisfied, which ones failed, and which ones were not checked." +msgstr "" + +#: ./doc/security-guide/ch012_configuration-management.xml:310(para) +msgid "Combining configuration management and security auditing tools creates a powerful combination. The auditing tools will highlight deployment concerns. And the configuration management tools simplify the process of changing each system to address the audit concerns. Used together in this fashion, these tools help to maintain a cloud that satisfies security requirements ranging from basic hardening to compliance validation." +msgstr "" + +#: ./doc/security-guide/ch012_configuration-management.xml:317(para) +msgid "Configuration management and security auditing tools will introduce another layer of complexity into the cloud.  This complexity brings additional security concerns with it. We view this as an acceptable risk trade-off, given their security benefits. Securing the operational use of these tools is beyond the scope of this guide." +msgstr "" + +#: ./doc/security-guide/ch059_case-studies-monitoring-logging.xml:3(title) +msgid "Case Studies: Monitoring and Logging" +msgstr "" + +#: ./doc/security-guide/ch059_case-studies-monitoring-logging.xml:4(para) +msgid "In this case study we discuss how Alice and Bob would address monitoring and logging in the public vs a private cloud. In both instances, time synchronization and a centralized store of logs become extremely important for performing proper assessments and troubleshooting of anomalies. Just collecting logs is not very useful, a robust monitoring system must be built to generate actionable events." +msgstr "" + +#: ./doc/security-guide/ch059_case-studies-monitoring-logging.xml:6(title) ./doc/security-guide/ch039_case-studies-messaging.xml:6(title) ./doc/security-guide/ch066_case-studies-compliance.xml:6(title) ./doc/security-guide/ch028_case-studies-identity-management.xml:6(title) ./doc/security-guide/ch044_case-studies-database.xml:6(title) ./doc/security-guide/ch009_case-studies.xml:6(title) ./doc/security-guide/ch056_case-studies-instance-management.xml:6(title) ./doc/security-guide/ch022_case-studies-api-endpoints.xml:6(title) ./doc/security-guide/ch015_case-studies-management.xml:29(title) ./doc/security-guide/ch018_case-studies-pkissl.xml:6(title) ./doc/security-guide/ch035_case-studies-networking.xml:6(title) ./doc/security-guide/ch049_case-studies-tenant-data.xml:6(title) ./doc/security-guide/ch053_case-studies-instance-isolation.xml:6(title) +msgid "Alice's Private Cloud" +msgstr "" + +#: ./doc/security-guide/ch059_case-studies-monitoring-logging.xml:7(para) +msgid "In the private cloud, Alice has a better understanding of the tenants requirements and accordingly can add appropriate oversight and compliance on monitoring and logging. Alice should identify critical services and data and ensure that logging is turned at least on those services and is being aggregated to a central log server. She should start with simple and known use cases and implement correlation and alerting to limit the number of false positives. To implement correlation and alerting, she sends the log data to her organization's existing SIEM tool. Security monitoring should be an ongoing process and she should continue to define use cases and alerts as she has better understanding of the network traffic activity and usage over time." +msgstr "" + +#: ./doc/security-guide/ch059_case-studies-monitoring-logging.xml:10(title) ./doc/security-guide/ch039_case-studies-messaging.xml:10(title) ./doc/security-guide/ch066_case-studies-compliance.xml:13(title) ./doc/security-guide/ch028_case-studies-identity-management.xml:12(title) ./doc/security-guide/ch044_case-studies-database.xml:10(title) ./doc/security-guide/ch009_case-studies.xml:11(title) ./doc/security-guide/ch056_case-studies-instance-management.xml:12(title) ./doc/security-guide/ch022_case-studies-api-endpoints.xml:10(title) ./doc/security-guide/ch015_case-studies-management.xml:34(title) ./doc/security-guide/ch018_case-studies-pkissl.xml:10(title) ./doc/security-guide/ch035_case-studies-networking.xml:24(title) ./doc/security-guide/ch049_case-studies-tenant-data.xml:23(title) ./doc/security-guide/ch053_case-studies-instance-isolation.xml:12(title) +msgid "Bob's Public Cloud" +msgstr "" + +#: ./doc/security-guide/ch059_case-studies-monitoring-logging.xml:11(para) +msgid "When it comes to logging, as a public cloud provider, Bob is interested in logging both for situational awareness as well as compliance. That is, compliance that Bob as a provider is subject to as well as his ability to provide timely and relevant logs or reports on the behalf of his customers for their compliance audits. With that in mind, Bob configures all of his instances, nodes, and infrastructure devices to perform time synchronization with an external, known good time device. Additionally, Bob's team has built a Django based web applications for his customers to perform self-service log retrieval from Bob's SIEM tool. Bob also uses this SIEM tool along with a robust set of alerts and integration with his CMDB to provide operational awareness to both customers and cloud administrators." +msgstr "" + +#: ./doc/security-guide/bk_openstack-sec-guide.xml:6(title) +msgid "OpenStack Security Guide" +msgstr "" + +#: ./doc/security-guide/bk_openstack-sec-guide.xml:14(orgname) ./doc/security-guide/bk_openstack-sec-guide.xml:19(holder) +msgid "OpenStack Foundation" +msgstr "" + +#: ./doc/security-guide/bk_openstack-sec-guide.xml:18(year) +msgid "2013" +msgstr "" + +#: ./doc/security-guide/bk_openstack-sec-guide.xml:21(releaseinfo) +msgid "havana" +msgstr "" + +#: ./doc/security-guide/bk_openstack-sec-guide.xml:22(productname) +msgid "OpenStack" +msgstr "" + +#: ./doc/security-guide/bk_openstack-sec-guide.xml:26(remark) +msgid "Copyright details are filled in by the template." +msgstr "" + +#: ./doc/security-guide/bk_openstack-sec-guide.xml:31(para) +msgid "This book provides best practices and conceptual information about securing an OpenStack cloud." +msgstr "" + +#: ./doc/security-guide/bk_openstack-sec-guide.xml:38(date) +msgid "2013-12-02" +msgstr "" + +#: ./doc/security-guide/bk_openstack-sec-guide.xml:42(para) +msgid "Chapter on Object Storage added." +msgstr "" + +#: ./doc/security-guide/bk_openstack-sec-guide.xml:48(date) +msgid "2013-10-17" +msgstr "" + +#: ./doc/security-guide/bk_openstack-sec-guide.xml:52(para) +msgid "Havana release." +msgstr "" + +#: ./doc/security-guide/bk_openstack-sec-guide.xml:58(date) +msgid "2013-07-02" +msgstr "" + +#: ./doc/security-guide/bk_openstack-sec-guide.xml:62(para) +msgid "Initial creation..." +msgstr "" + +#: ./doc/security-guide/ch065_privacy.xml:3(title) +msgid "Privacy" +msgstr "" + +#: ./doc/security-guide/ch065_privacy.xml:4(para) +msgid "Privacy is an increasingly important element of a compliance program. Businesses are being held to a higher standard by their customers, who have increased interest in understanding how their data is treated from a privacy perspective." +msgstr "" + +#: ./doc/security-guide/ch065_privacy.xml:5(para) +msgid "An OpenStack deployment will likely need to demonstrate compliance with an organization’s Privacy Policy, with the U.S. – E.U. Safe Harbor framework, the ISO/IEC 29100:2011 privacy framework or with other privacy-specific guidelines. In the U.S. the AICPA has defined 10 privacy areas of focus, OpenStack deployments within a commercial environment may desire to attest to some or all of these principles." +msgstr "" + +#: ./doc/security-guide/ch065_privacy.xml:6(para) +msgid "To aid OpenStack architects in the protection of personal data, it is recommended that OpenStack architects review the NIST publication 800-122, titled \"Guide to Protecting the Confidentiality of Personally Identifiable Information (PII).\" This guide steps through the process of protecting:" +msgstr "" + +#: ./doc/security-guide/ch065_privacy.xml:8(para) +msgid "\"any information about an individual maintained by an agency, including (1) any information that can be used to distinguish or trace an individual‘s identity, such as name, social security number, date and place of birth, mother‘s maiden name, or biometric records; and (2) any other information that is linked or linkable to an individual, such as medical, educational, financial, and employment information\"" +msgstr "" + +#: ./doc/security-guide/ch065_privacy.xml:10(para) +msgid "Comprehensive privacy management requires significant preparation, thought and investment. Additional complications are introduced when building global OpenStack clouds, for example navigating the differences between U.S. and more restrictive E.U. privacy laws. In addition, extra care needs to be taken when dealing with sensitive PII that may include information such as credit card numbers or medical records. This sensitive data is not only subject to privacy laws but also regulatory and governmental regulations. By deferring to established best practices, including those published by governments, a holistic privacy management policy may be created and practiced for OpenStack deployments." +msgstr "" + +#: ./doc/security-guide/ch032_networking-best-practices.xml:3(title) +msgid "Networking Services" +msgstr "" + +#: ./doc/security-guide/ch032_networking-best-practices.xml:4(para) +msgid "In the initial architectural phases of designing your OpenStack Network infrastructure it is important to ensure appropriate expertise is available to assist with the design of the physical networking infrastructure, to identify proper security controls and auditing mechanisms." +msgstr "" + +#: ./doc/security-guide/ch032_networking-best-practices.xml:5(para) +msgid "OpenStack Networking adds a layer of virtualized network services - giving tenants the capability to architect their own, virtual networks. These virtualized services are not as currently as mature as their traditional networking counterparts. It is important to be aware of the current state of these virtualized services and what controls may need to be implemented at the virtualized and traditional network boundary." +msgstr "" + +#: ./doc/security-guide/ch032_networking-best-practices.xml:7(title) +msgid "L2 Isolation using VLANs and Tunneling" +msgstr "" + +#: ./doc/security-guide/ch032_networking-best-practices.xml:8(para) +msgid "OpenStack networking can employ two different mechanisms for traffic segregation on a per tenant/network combination: VLANs (IEEE 802.1Q tagging) or L2 tunnels using GRE encapsulation. Which method you choose for traffic segregation and isolation is determined by the scope and scale of your OpenStack deployment." +msgstr "" + +#: ./doc/security-guide/ch032_networking-best-practices.xml:10(title) +msgid "VLANs" +msgstr "" + +#: ./doc/security-guide/ch032_networking-best-practices.xml:11(para) +msgid "VLANs are realized as packets on a specific physical network containing IEEE 802.1Q headers with a specific VLAN ID (VID) field value. VLAN networks sharing the same physical network are isolated from each other at L2, and can even have overlapping IP address spaces. Each distinct physical network supporting VLAN networks is treated as a separate VLAN trunk, with a distinct space of VID values. Valid VID values are 1 through 4094." +msgstr "" + +#: ./doc/security-guide/ch032_networking-best-practices.xml:12(para) +msgid "VLAN configuration complexity depends on your OpenStack design requirements. In order to allow OpenStack Networking to efficiently use VLANs, you must allocate a VLAN range (one for each tenant) and turn each compute node physical switch port into a VLAN trunk port." +msgstr "" + +#: ./doc/security-guide/ch032_networking-best-practices.xml:14(para) +msgid "NOTE: If you intend for your network to support more than 4094 tenants VLAN is probably not the correct option for you as multiple 'hacks' are required to extend the VLAN tags to more than 4094 tenants." +msgstr "" + +#: ./doc/security-guide/ch032_networking-best-practices.xml:18(title) +msgid "L2 Tunneling" +msgstr "" + +#: ./doc/security-guide/ch032_networking-best-practices.xml:19(para) +msgid "Network tunneling encapsulates each tenant/network combination with a unique \"tunnel-id\" that is used to identify the network traffic belonging to that combination. The tenant's L2 network connectivity is independent of physical locality or underlying network design. By encapsulating traffic inside IP packets, that traffic can cross Layer-3 boundaries, removing the need for preconfigured VLANs and VLAN trunking. Tunneling adds a layer of obfuscation to network data traffic, reducing the visibility of individual tenant traffic from a monitoring point of view." +msgstr "" + +#: ./doc/security-guide/ch032_networking-best-practices.xml:20(para) +msgid "OpenStack Networking currently only supports GRE encapsulation with planned future support of VXLAN due in the Havana release." +msgstr "" + +#: ./doc/security-guide/ch032_networking-best-practices.xml:21(para) +msgid "The choice of technology to provide L2 isolation is dependent upon the scope and size of tenant networks that will be created in your deployment. If your environment has limited VLAN ID availability or will have a large number of L2 networks, it is our recommendation that you utilize tunneling." +msgstr "" + +#: ./doc/security-guide/ch032_networking-best-practices.xml:25(title) +msgid "Network Services" +msgstr "" + +#: ./doc/security-guide/ch032_networking-best-practices.xml:26(para) +msgid "The choice of tenant network isolation affects how the network security and control boundary is implemented for tenant services. The following additional network services are either available or currently under development to enhance the security posture of the OpenStack network architecture." +msgstr "" + +#: ./doc/security-guide/ch032_networking-best-practices.xml:28(title) +msgid "Access Control Lists" +msgstr "" + +#: ./doc/security-guide/ch032_networking-best-practices.xml:29(para) +msgid "OpenStack Compute supports tenant network traffic access controls directly when deployed with the legacy nova-network service, or may defer access control to the OpenStack Networking service." +msgstr "" + +#: ./doc/security-guide/ch032_networking-best-practices.xml:30(para) +msgid "Note, legacy nova-network security groups are applied to all virtual interface ports on an instance using IPTables." +msgstr "" + +#: ./doc/security-guide/ch032_networking-best-practices.xml:31(para) +msgid "Security groups allow administrators and tenants the ability to specify the type of traffic, and direction (ingress/egress) that is allowed to pass through a virtual interface port. Security groups rules are stateful L2-L4 traffic filters." +msgstr "" + +#: ./doc/security-guide/ch032_networking-best-practices.xml:32(para) +msgid "It is our recommendation that you enable security groups via OpenStack Networking." +msgstr "" + +#: ./doc/security-guide/ch032_networking-best-practices.xml:35(title) +msgid "L3 Routing and NAT" +msgstr "" + +#: ./doc/security-guide/ch032_networking-best-practices.xml:36(para) +msgid "OpenStack Networking routers can connect multiple L2 networks, and can also provide a gateway that connects one or more private L2 networks to a shared external network, such as a public network for access to the Internet." +msgstr "" + +#: ./doc/security-guide/ch032_networking-best-practices.xml:37(para) +msgid "The L3 router provides basic Network Address Translation (NAT) capabilities on gateway ports that uplink the router to external networks. This router SNATs (Static NAT) all traffic by default, and supports floating IPs, which creates a static one-to-one mapping from a public IP on the external network to a private IP on one of the other subnets attached to the router." +msgstr "" + +#: ./doc/security-guide/ch032_networking-best-practices.xml:38(para) +msgid "It is our recommendation to leverage per tenant L3 routing and Floating IPs for more granular connectivity of tenant VMs." +msgstr "" + +#: ./doc/security-guide/ch032_networking-best-practices.xml:41(title) +msgid "Quality of Service (QoS)" +msgstr "" + +#: ./doc/security-guide/ch032_networking-best-practices.xml:42(para) +msgid "The ability to set QoS on the virtual interface ports of tenant instances is a current deficiency for OpenStack Networking. The application of QoS for traffic shaping and rate-limiting at the physical network edge device is insufficient due to the dynamic nature of workloads in an OpenStack deployment and can not be leveraged in the traditional way.  QoS-as-a-Service (QoSaaS) is currently in development for the OpenStack Networking Havana release as an experimental feature. QoSaaS is planning to provide the following services:" +msgstr "" + +#: ./doc/security-guide/ch032_networking-best-practices.xml:44(para) +msgid "Traffic shaping via DSCP markings" +msgstr "" + +#: ./doc/security-guide/ch032_networking-best-practices.xml:47(para) +msgid "Rate-limiting on a per port/network/tenant basis." +msgstr "" + +#: ./doc/security-guide/ch032_networking-best-practices.xml:50(para) +msgid "Port mirroring (via open source or third-party plugins)" +msgstr "" + +#: ./doc/security-guide/ch032_networking-best-practices.xml:53(para) +msgid "Flow analysis (via open source or third-party plugins)" +msgstr "" + +#: ./doc/security-guide/ch032_networking-best-practices.xml:56(para) +msgid "Tenant traffic port mirroring or Network Flow monitoring is currently not an exposed feature in OpenStack Networking. There are third-party plugin extensions that do provide Port Mirroring on a per port/network/tenant basis. If Open vSwitch is used on the networking hypervisor, it is possible to enable sFlow and port mirroring, however it will require some operational effort to implement." +msgstr "" + +#: ./doc/security-guide/ch032_networking-best-practices.xml:59(title) +msgid "Load Balancing" +msgstr "" + +#: ./doc/security-guide/ch032_networking-best-practices.xml:60(para) +msgid "An experimental feature in the Grizzly release of OpenStack Networking is Load-Balancer-as-a-service (LBaaS). The LBaaS API gives early adopters and vendors a chance to build implementations of the technology. The reference implementation however, is still experimental and should likely not be run in a production environment. The current reference implementation is based on HA-Proxy. There are third-party plugins in development for extensions in OpenStack Networking to provide extensive L4-L7 functionality for virtual interface ports." +msgstr "" + +#: ./doc/security-guide/ch032_networking-best-practices.xml:63(title) +msgid "Firewalls" +msgstr "" + +#: ./doc/security-guide/ch032_networking-best-practices.xml:64(para) +msgid "FW-as-a-Service (FWaaS) is currently in development for the OpenStack Networking Havana release as an experimental feature. FWaaS will address the need to manage and leverage the rich set of security features provided by typical firewall products which are typically far more comprehensive than what is currently provided by security groups. There are third-party plugins in development for extensions in OpenStack Networking to support this." +msgstr "" + +#: ./doc/security-guide/ch032_networking-best-practices.xml:65(para) +msgid "It is critical during the design of an OpenStack Networking infrastructure to understand the current features and limitations of network services that are available. Understanding where the boundaries of your virtual and physical networks will help you add the required security controls in your environment." +msgstr "" + +#: ./doc/security-guide/ch032_networking-best-practices.xml:69(title) +msgid "Network Services Extensions" +msgstr "" + +#: ./doc/security-guide/ch032_networking-best-practices.xml:70(para) +msgid "Here is a list of known plugins provided by the open source community or by SDN companies that work with OpenStack Networking:" +msgstr "" + +#: ./doc/security-guide/ch032_networking-best-practices.xml:71(para) +msgid "Big Switch Controller Plugin, Brocade Neutron Plugin Brocade Neutron Plugin, Cisco UCS/Nexus Plugin, Cloudbase Hyper-V Plugin, Extreme Networks Plugin, Juniper Networks Neutron Plugin, Linux Bridge Plugin, Mellanox Neutron Plugin, MidoNet Plugin, NEC OpenFlow Plugin, Nicira Network Virtualization Platform (NVP) Plugin, Open vSwitch Plugin, PLUMgrid Plugin, Ruijie Networks Plugin, Ryu OpenFlow Controller Plugin" +msgstr "" + +#: ./doc/security-guide/ch032_networking-best-practices.xml:72(para) +msgid "For a more detailed comparison of all features provided by plugins as of the Folsom release, see Sebastien Han's comparison." +msgstr "" + +#: ./doc/security-guide/ch032_networking-best-practices.xml:75(title) +msgid "Networking Services Limitations" +msgstr "" + +#: ./doc/security-guide/ch032_networking-best-practices.xml:76(para) +msgid "OpenStack Networking has the following known limitations:" +msgstr "" + +#: ./doc/security-guide/ch032_networking-best-practices.xml:78(para) +msgid "Overlapping IP addresses — If nodes that run either neutron-l3-agent or neutron-dhcp-agent use overlapping IP addresses, those nodes must use Linux network namespaces. By default, the DHCP and L3 agents use Linux network namespaces. However, if the host does not support these namespaces, run the DHCP and L3 agents on different hosts." +msgstr "" + +#: ./doc/security-guide/ch032_networking-best-practices.xml:79(para) +msgid "If network namespace support is not present, a further limitation of the L3 Agent is that only a single logical router is supported." +msgstr "" + +#: ./doc/security-guide/ch032_networking-best-practices.xml:82(para) +msgid "Multi-Host DHCP-agent — OpenStack Networking supports multiple l3-agent and dhcp-agents with load balancing. However, tight coupling of the location of the virtual machine is not supported." +msgstr "" + +#: ./doc/security-guide/ch032_networking-best-practices.xml:85(para) +msgid "No IPv6 Support for L3 agents — The neutron-l3-agent, used by many plugins to implement L3 forwarding, supports only IPv4 forwarding." +msgstr "" + +#. When image changes, this message will be marked fuzzy or untranslated for you. +#. It doesn't matter what you translate it to: it's not used at all. +#: ./doc/security-guide/ch055_security-services-for-instances.xml:47(None) ./doc/security-guide/ch055_security-services-for-instances.xml:50(None) +msgid "@@image: 'static/filteringWorkflow1.png'; md5=c144af5cbdee1bd17a7bde0bea5b5fe7" +msgstr "" + +#: ./doc/security-guide/ch055_security-services-for-instances.xml:3(title) +msgid "Security Services for Instances" +msgstr "" + +#: ./doc/security-guide/ch055_security-services-for-instances.xml:4(para) +msgid "One of the virtues of running instances in a virtualized environment is that it opens up new opportunities for security controls that are not typically available when deploying onto bare metal. There are several technologies that can be applied to the virtualization stack that bring improved information assurance for cloud tenants." +msgstr "" + +#: ./doc/security-guide/ch055_security-services-for-instances.xml:5(para) +msgid "Deployers or users of OpenStack with strong security requirements may want to consider deploying these technologies. Not all are applicable in every situation, indeed in some cases technologies may be ruled out for use in a cloud because of prescriptive business requirements. Similarly some technologies inspect instance data such as run state which may be undesirable to the users of the system." +msgstr "" + +#: ./doc/security-guide/ch055_security-services-for-instances.xml:6(para) +msgid "In this chapter we explore these technologies and describe the situations where they can be used to enhance security for instances or underlying instances. We also seek to highlight where privacy concerns may exist. These include data pass through, introspection, or providing a source of entropy. In this section we highlight the following additional security services:" +msgstr "" + +#: ./doc/security-guide/ch055_security-services-for-instances.xml:8(para) +msgid "Entropy to Instances" +msgstr "" + +#: ./doc/security-guide/ch055_security-services-for-instances.xml:11(para) ./doc/security-guide/ch055_security-services-for-instances.xml:28(title) +msgid "Scheduling Instances to Nodes" +msgstr "" + +#: ./doc/security-guide/ch055_security-services-for-instances.xml:14(para) ./doc/security-guide/ch055_security-services-for-instances.xml:88(title) +msgid "Trusted Images" +msgstr "" + +#: ./doc/security-guide/ch055_security-services-for-instances.xml:17(para) ./doc/security-guide/ch055_security-services-for-instances.xml:153(title) +msgid "Instance Migrations" +msgstr "" + +#: ./doc/security-guide/ch055_security-services-for-instances.xml:21(title) +msgid "Entropy To Instances" +msgstr "" + +#: ./doc/security-guide/ch055_security-services-for-instances.xml:22(para) +msgid "We consider entropy to refer to the quality and source of random data that is available to an instance. Cryptographic technologies typically rely heavily on randomness, requiring a high quality pool of entropy to draw from. It is typically hard for a virtual machine to get enough entropy to support these operations. Entropy starvation can manifest in instances as something seemingly unrelated for example, slow boot times because the instance is waiting for ssh key generation. Entropy starvation may also motivate users to employ poor quality entropy sources from within the instance, making applications running in the cloud less secure overall." +msgstr "" + +#: ./doc/security-guide/ch055_security-services-for-instances.xml:23(para) +msgid "Fortunately, a cloud architect may address these issues by providing a high quality source of entropy to the cloud instances. This can be done by having enough hardware random number generators (HRNG) in the cloud to support the instances. In this case, \"enough\" is somewhat domain specific. For everyday operations, a modern HRNG is likely to produce enough entropy to support 50-100 compute nodes. High bandwidth HRNGs, such as the RdRand instruction available with Intel Ivy Bridge and newer processors could potentially handle more nodes. For a given cloud, an architect needs to understand the application requirements to ensure that sufficient entropy is available." +msgstr "" + +#: ./doc/security-guide/ch055_security-services-for-instances.xml:24(para) +msgid "Once the entropy is available in the cloud, the next step is getting that entropy into the instances. Tools such as the entropy gathering daemon (EGD) provide a way to fairly and securely distribute entropy through a distributed system. Support exists for using the EGD as an entropy source for LibVirt." +msgstr "" + +#: ./doc/security-guide/ch055_security-services-for-instances.xml:25(para) +msgid "Compute support for these features is not generally available, but it would only require a moderate amount of work for implementors to integrate this functionality." +msgstr "" + +#: ./doc/security-guide/ch055_security-services-for-instances.xml:29(para) +msgid "Before an instance is created, a host for the image instantiation must be selected. This selection is performed by the nova-scheduler which determines how to dispatch compute and volume requests." +msgstr "" + +#: ./doc/security-guide/ch055_security-services-for-instances.xml:30(para) +msgid "The default nova scheduler in Grizzly is the Filter Scheduler, although other schedulers exist (see the section Scheduling in the OpenStack Configuration Reference). The filter scheduler works in collaboration with 'filters' to decide where an instance should be started. This process of host selection allows administrators to fulfill many different security requirements. Depending on the cloud deployment type for example, one could choose to have tenant instances reside on the same hosts whenever possible if data isolation was a primary concern, conversely one could attempt to have instances for a tenant reside on as many different hosts as possible for availability or fault tolerance reasons. The following diagram demonstrates how the filter scheduler works:" +msgstr "" + +#: ./doc/security-guide/ch055_security-services-for-instances.xml:53(para) +msgid "The use of scheduler filters may be used to segregate customers, data, or even discard machines of the cloud that cannot be attested as secure. This generally applies to all OpenStack projects offering a scheduler. When building a cloud, you may choose to implement scheduling filters for a variety of security-related purposes." +msgstr "" + +#: ./doc/security-guide/ch055_security-services-for-instances.xml:54(para) +msgid "Below we highlight a few of the filters that may be useful in a security context, depending on your requirements, the full set of filter documentation is documented in the Filter Scheduler section of the OpenStack Configuration Reference." +msgstr "" + +#: ./doc/security-guide/ch055_security-services-for-instances.xml:55(emphasis) +msgid "Tenant Driven Whole Host Reservation" +msgstr "" + +#: ./doc/security-guide/ch055_security-services-for-instances.xml:56(para) +msgid "There currently exists a blueprint for whole host reservation - This would allow a tenant to exclusively reserve hosts for only it's instances, incurring extra costs." +msgstr "" + +#: ./doc/security-guide/ch055_security-services-for-instances.xml:58(title) +msgid "Host Aggregates" +msgstr "" + +#: ./doc/security-guide/ch055_security-services-for-instances.xml:59(para) +msgid "While not a filter in themselves, host aggregates allow administrators to assign key-value pairs to groups of machines. This allows cloud administrators, not users, to partition up their compute host resources. Each node can have multiple aggregates (see the Host Aggregates section of the OpenStack Configuration Reference for more information on creating and managing aggregates)." +msgstr "" + +#: ./doc/security-guide/ch055_security-services-for-instances.xml:70(title) +msgid "AggregateMultiTenancyIsolation" +msgstr "" + +#: ./doc/security-guide/ch055_security-services-for-instances.xml:71(para) +msgid "Isolates tenants to specific host aggregates. If a host is in an aggregate that has the metadata key filter_tenant_id it will only create instances from that tenant (or list of tenants). A host can be in multiple aggregates. If a host does not belong to an aggregate with the metadata key, it can create instances from all tenants." +msgstr "" + +#: ./doc/security-guide/ch055_security-services-for-instances.xml:74(title) +msgid "DifferentHostFilter" +msgstr "" + +#: ./doc/security-guide/ch055_security-services-for-instances.xml:75(para) +msgid "Schedule the instance on a different host from a set of instances. To take advantage of this filter, the requester must pass a scheduler hint, using different_host as the key and a list of instance uuids as the value. This filter is the opposite of the SameHostFilter." +msgstr "" + +#: ./doc/security-guide/ch055_security-services-for-instances.xml:78(title) +msgid "GroupAntiAffinityFilter" +msgstr "" + +#: ./doc/security-guide/ch055_security-services-for-instances.xml:79(para) +msgid "The GroupAntiAffinityFilter ensures that each instance in a group is on a different host. To take advantage of this filter, the requester must pass a scheduler hint, using group as the key and a list of instance uuids as the value." +msgstr "" + +#: ./doc/security-guide/ch055_security-services-for-instances.xml:82(title) +msgid "Trusted Compute Pools" +msgstr "" + +#: ./doc/security-guide/ch055_security-services-for-instances.xml:83(para) +msgid "There exists a scheduler filter which integrates with the Open Attestation Project (OATS) to define scheduler behavior according to the attestation of PCRs received from a system using Intel TXT." +msgstr "" + +#: ./doc/security-guide/ch055_security-services-for-instances.xml:84(para) +msgid "It is unclear if this feature is compatible with AMD's similar SEM, although the OpenAttestation agent relies on the vendor-agnostic TrouSerS library." +msgstr "" + +#: ./doc/security-guide/ch055_security-services-for-instances.xml:89(para) +msgid "With regards to images, users will be working with pre-installed images or images that they upload themselves. In both cases, users will want to ensure that the image they are ultimately running has not been tampered with. This requires some source of truth such as a checksum for the known good version of an image as well as verification of the running image. This section describes the current best practices around image handling, while also calling out some of the existing gaps in this space." +msgstr "" + +#: ./doc/security-guide/ch055_security-services-for-instances.xml:91(title) +msgid "Image Creation Process" +msgstr "" + +#: ./doc/security-guide/ch055_security-services-for-instances.xml:92(para) +msgid "The OpenStack Documentation provides guidance on how to create and upload an image to Glance. Additionally it is assumed that you have a process by which you install and harden operating systems. Thus, the following items will provide additional guidance on how to ensure your images are built securely prior to upload. There are a variety of options for obtaining images. Each has specific steps that help validate the image's provenance." +msgstr "" + +#: ./doc/security-guide/ch055_security-services-for-instances.xml:93(para) +msgid "The first option is to obtain boot media from a trusted source." +msgstr "" + +#: ./doc/security-guide/ch055_security-services-for-instances.xml:103(para) +msgid "The second option is to use the OpenStack Virtual Machine Image Guide. In this case, you will want to follow your organizations OS hardening guidelines or those provided by a trusted third-party such as the RHEL6 STIG." +msgstr "" + +#: ./doc/security-guide/ch055_security-services-for-instances.xml:104(para) +msgid "The final option is to use an automated image builder. The following example uses the Oz image builder. The OpenStack community has recently created a newer tool worth investigating: disk-image-builder. We have not evaluated this tool from a security perspective." +msgstr "" + +#: ./doc/security-guide/ch055_security-services-for-instances.xml:105(para) +msgid "Example of RHEL 6 CCE-26976-1 which will help implement NIST 800-53 Section AC-19(d) in Oz." +msgstr "" + +#: ./doc/security-guide/ch055_security-services-for-instances.xml:142(para) +msgid "Note, it is the recommendation of this guide to shy away from the manual image building process as it is complex and prone to error. Further, using an automated system like Oz or disk-image-builder for image building, or a configuration management utility like Chef or Puppet for post boot image hardening gives you the ability to produce a consistent image as well as track compliance of your base image to its respective hardening guidelines over time." +msgstr "" + +#: ./doc/security-guide/ch055_security-services-for-instances.xml:143(para) +msgid "If subscribing to a public cloud service, you should check with the cloud provider for an outline of the process used to produce their default images. If the provider allows you to upload your own images, you will want to ensure that you are able to verify that your image was not modified before you spin it up. To do this, refer to the following section on Image Provenance." +msgstr "" + +#: ./doc/security-guide/ch055_security-services-for-instances.xml:146(title) +msgid "Image Provenance and Validation" +msgstr "" + +#: ./doc/security-guide/ch055_security-services-for-instances.xml:147(para) +msgid "Unfortunately, it is not currently possible to force Compute to validate an image hash immediately prior to starting an instance. To understand the situation, we begin with a brief overview of how images are handled around the time of image launch." +msgstr "" + +#: ./doc/security-guide/ch055_security-services-for-instances.xml:148(para) +msgid "Images come from the glance service to the nova service on a node. This transfer should be protected by running over SSL. Once the image is on the node, it is verified with a basic checksum and then it's disk is expanded based on the size of the instance being launched. If, at a later time, the same image is launched with the same instance size on this node, it will be launched from the same expanded image. Since this expanded image is not re-verified before launching, it could be tampered with and the user would not have any way of knowing, beyond a manual inspection of the files in the resulting image." +msgstr "" + +#: ./doc/security-guide/ch055_security-services-for-instances.xml:149(para) +msgid "We hope that future versions of Compute and/or the Image Service will offer support for validating the image hash before each instance launch. An alternative option that would be even more powerful would be allow users to sign an image and then have the signature validated when the instance is launched." +msgstr "" + +#: ./doc/security-guide/ch055_security-services-for-instances.xml:154(para) +msgid "OpenStack and the underlying virtualization layers provide for the Live Migration of images between OpenStack nodes allowing you to seamlessly perform rolling upgrades of your OpenStack Compute nodes without instance downtime. However, Live Migrations also come with their fair share of risk. To understand the risks involved, it is important to first understand how a live migration works. The following are the high level steps preformed during a live migration." +msgstr "" + +#: ./doc/security-guide/ch055_security-services-for-instances.xml:156(para) +msgid "Start instance on destination host" +msgstr "" + +#: ./doc/security-guide/ch055_security-services-for-instances.xml:157(para) +msgid "Transfer memory" +msgstr "" + +#: ./doc/security-guide/ch055_security-services-for-instances.xml:158(para) +msgid "Stop the guest & sync disks" +msgstr "" + +#: ./doc/security-guide/ch055_security-services-for-instances.xml:159(para) +msgid "Transfer state" +msgstr "" + +#: ./doc/security-guide/ch055_security-services-for-instances.xml:160(para) +msgid "Start the guest" +msgstr "" + +#: ./doc/security-guide/ch055_security-services-for-instances.xml:163(title) +msgid "Live Migration Risks" +msgstr "" + +#: ./doc/security-guide/ch055_security-services-for-instances.xml:164(para) +msgid "At various stages of the live migration process the contents of an instances run time memory and disk are transmitted over the network in plain text. Thus there are several risks that need to be addressed when using live migration. The following in-exhaustive list details some of these risks:" +msgstr "" + +#: ./doc/security-guide/ch055_security-services-for-instances.xml:166(para) +msgid "Denial of Service (DoS) : If something fails during the migration process, the instance could be lost." +msgstr "" + +#: ./doc/security-guide/ch055_security-services-for-instances.xml:169(para) +msgid "Data Exposure : Memory or disk transfers must be handled securely." +msgstr "" + +#: ./doc/security-guide/ch055_security-services-for-instances.xml:172(para) +msgid "Data Manipulation : If memory or disk transfers are not handled securely, then an attacker could manipulate user data during the migration." +msgstr "" + +#: ./doc/security-guide/ch055_security-services-for-instances.xml:175(para) +msgid "Code Injection : If memory or disk transfers are not handled securely, then an attacker could manipulate executables, either on disk or in memory, during the migration." +msgstr "" + +#: ./doc/security-guide/ch055_security-services-for-instances.xml:180(title) +msgid "Live Migration Mitigations" +msgstr "" + +#: ./doc/security-guide/ch055_security-services-for-instances.xml:181(para) +msgid "There are several methods to mitigate some of the risk associated with live migrations, the following list details some of these:" +msgstr "" + +#: ./doc/security-guide/ch055_security-services-for-instances.xml:183(para) ./doc/security-guide/ch055_security-services-for-instances.xml:193(title) +msgid "Disable Live Migration" +msgstr "" + +#: ./doc/security-guide/ch055_security-services-for-instances.xml:186(para) +msgid "Isolated Migration Network" +msgstr "" + +#: ./doc/security-guide/ch055_security-services-for-instances.xml:189(para) ./doc/security-guide/ch055_security-services-for-instances.xml:204(title) +msgid "Encrypted Live Migration" +msgstr "" + +#: ./doc/security-guide/ch055_security-services-for-instances.xml:194(para) +msgid "At this time, live migration is enabled in OpenStack by default. Live migrations can be disabled by adding the following lines to the nova policy.json file:" +msgstr "" + +#: ./doc/security-guide/ch055_security-services-for-instances.xml:200(title) +msgid "Migration Network" +msgstr "" + +#: ./doc/security-guide/ch055_security-services-for-instances.xml:201(para) +msgid "As a general practice, live migration traffic should be restricted to the management security domain. Indeed live migration traffic, due to its plain text nature and the fact that you are transferring the contents of disk and memory of a running instance, it is recommended you further separate live migration traffic onto a dedicated network. Isolating the traffic to a dedicated network can reduce the risk of exposure." +msgstr "" + +#: ./doc/security-guide/ch055_security-services-for-instances.xml:205(para) +msgid "If your use case involves keeping live migration enabled, then libvirtd can provide tunneled, encrypted live migrations. That said, this feature is not currently exposed in OpenStack Dashboard, nor the nova-client commands and can only be accessed through manual configuration of libvritd. Encrypted live migration modifies the live migration process by first copying the instance data from the running hypervisor to libvirtd. From there an encrypted tunnel is created between the libvirtd processes on both hosts. Finally, the destination libvirtd process copies the instance back to the underlying hypervisor." +msgstr "" + +#: ./doc/security-guide/ch061_compliance-overview.xml:3(title) +msgid "Compliance Overview" +msgstr "" + +#: ./doc/security-guide/ch061_compliance-overview.xml:4(para) +msgid "An OpenStack deployment may require compliance activities for many purposes, such as regulatory and legal requirements, customer need, privacy considerations, and security best practices. Compliance, when done correctly, unifies and strengthens the other security topics discussed in this guide. This chapter has several objectives:" +msgstr "" + +#: ./doc/security-guide/ch061_compliance-overview.xml:6(para) +msgid "Review common security principles." +msgstr "" + +#: ./doc/security-guide/ch061_compliance-overview.xml:9(para) +msgid "Discuss common control frameworks and certification resources to achieve industry certifications or regulator attestations." +msgstr "" + +#: ./doc/security-guide/ch061_compliance-overview.xml:12(para) +msgid "Act as a reference for auditors when evaluating OpenStack deployments." +msgstr "" + +#: ./doc/security-guide/ch061_compliance-overview.xml:15(para) +msgid "Introduce privacy considerations specific to OpenStack and cloud environments." +msgstr "" + +#: ./doc/security-guide/ch061_compliance-overview.xml:19(title) +msgid "Security Principles" +msgstr "" + +#: ./doc/security-guide/ch061_compliance-overview.xml:20(para) +msgid "Industry standard security principles provide a baseline for compliance certifications and attestations. If these principles are considered and referenced throughout an OpenStack deployment, certification activities may be simplified." +msgstr "" + +#: ./doc/security-guide/ch061_compliance-overview.xml:22(para) +msgid "Layered Defenses: Identify where risks exist in a cloud architecture and apply controls to mitigate the risks. In areas of significant concern, layered defences provide multiple complementary controls to further mitigate risk. For example, to ensure adequate isolation between cloud tenants, we recommend hardening QEMU, using a hypervisor with SELinux support, enforcing mandatory access control policies, and reducing the overall attack surface. The foundational principle is to harden an area of concern with multiple layers of defense such that if any one layer is compromised, other layers will exist to offer protection and minimize exposure." +msgstr "" + +#: ./doc/security-guide/ch061_compliance-overview.xml:25(para) +msgid "Fail Securely: In the case of failure, systems should be configured to fail into a closed secure state. For example, SSL certificate verification should fail closed by severing the network connection if the CNAME doesn't match the server's DNS name. Software often fails open in this situation, allowing the connection to proceed without a CNAME match, which is less secure and not recommended." +msgstr "" + +#: ./doc/security-guide/ch061_compliance-overview.xml:28(para) +msgid "Least Privilege: Only the minimum level of access for users and system services is granted. This access is based upon role, responsibility and job function. This security principal of least privilege is written into several international government security policies, such as NIST 800-53 Section AC-6 within the United States. " +msgstr "" + +#: ./doc/security-guide/ch061_compliance-overview.xml:31(para) +msgid "Compartmentalize: Systems should be segregated in a such way that if one machine, or system-level service, is compromised the security of the other systems will remain intact. Practically, the enablement and proper usage of SELinux helps accomplish this goal." +msgstr "" + +#: ./doc/security-guide/ch061_compliance-overview.xml:34(para) +msgid "Promote Privacy: The amount of information that can be gathered about a system and its users should be minimized." +msgstr "" + +#: ./doc/security-guide/ch061_compliance-overview.xml:37(para) +msgid "Logging Capability: Appropriate logging is implemented to monitor for unauthorized use, incident response and forensics. It is highly recommended that selected audit subsystems be Common Criteria certified, which provides non-attestable event records in most countries." +msgstr "" + +#: ./doc/security-guide/ch064_certifications-compliance-statements.xml:8(title) +msgid "Certification & Compliance Statements" +msgstr "" + +#: ./doc/security-guide/ch064_certifications-compliance-statements.xml:9(para) +msgid "Compliance and security are not exclusive, and must be addressed together. OpenStack deployments are unlikely to satisfy compliance requirements without security hardening. The listing below provides an OpenStack architect foundational knowledge and guidance to achieve compliance against commercial and government certifications and standards." +msgstr "" + +#: ./doc/security-guide/ch064_certifications-compliance-statements.xml:17(title) +msgid "Commercial Standards" +msgstr "" + +#: ./doc/security-guide/ch064_certifications-compliance-statements.xml:18(para) +msgid "For commercial deployments of OpenStack, it is recommended that SOC 1/2 combined with ISO 2700 1/2 be considered as a starting point for OpenStack certification activities. The required security activities mandated by these certifications facilitate a foundation of security best practices and common control criteria that can assist in achieving more stringent compliance activities, including government attestations and certifications." +msgstr "" + +#: ./doc/security-guide/ch064_certifications-compliance-statements.xml:26(para) +msgid "After completing these initial certifications, the remaining certifications are more deployment specific. For example, clouds processing credit card transactions will need PCI-DSS, clouds storing health care information require HIPAA, and clouds within the federal government may require FedRAMP/FISMA, and ITAR, certifications. " +msgstr "" + +#: ./doc/security-guide/ch064_certifications-compliance-statements.xml:34(title) +msgid "SOC 1 (SSAE 16) / ISAE 3402" +msgstr "" + +#: ./doc/security-guide/ch064_certifications-compliance-statements.xml:35(para) +msgid "Service Organization Controls (SOC) criteria are defined by the American Institute of Certified Public Accountants (AICPA). SOC controls assess relevant financial statements and assertions of a service provider, such as compliance with the Sarbanes-Oxley Act. SOC 1 is a replacement for Statement on Auditing Standards No. 70 (SAS 70) Type II report. These controls commonly include physical data centers in scope." +msgstr "" + +#: ./doc/security-guide/ch064_certifications-compliance-statements.xml:44(para) +msgid "There are two types of SOC 1 reports:" +msgstr "" + +#: ./doc/security-guide/ch064_certifications-compliance-statements.xml:47(para) ./doc/security-guide/ch064_certifications-compliance-statements.xml:84(para) +msgid "Type 1 – report on the fairness of the presentation of management's description of the service organization's system and the suitability of the design of the controls to achieve the related control objectives included in the description as of a specified date." +msgstr "" + +#: ./doc/security-guide/ch064_certifications-compliance-statements.xml:54(para) +msgid "Type 2 – report on the fairness of the presentation of management's description of the service organization's system and the suitability of the design and operating effectiveness of the controls to achieve the related control objectives included in the description throughout a specified period" +msgstr "" + +#: ./doc/security-guide/ch064_certifications-compliance-statements.xml:62(para) +msgid "For more details see the AICPA Report on Controls at a Service Organization Relevant to User Entities’ Internal Control over Financial Reporting." +msgstr "" + +#: ./doc/security-guide/ch064_certifications-compliance-statements.xml:70(title) +msgid "SOC 2" +msgstr "" + +#: ./doc/security-guide/ch064_certifications-compliance-statements.xml:71(para) +msgid "Service Organization Controls (SOC) 2 is a self attestation of controls that affect the security, availability, and processing integrity of the systems a service organization uses to process users' data and the confidentiality and privacy of information processed by these system. Examples of users are those responsible for governance of the service organization; customers of the service organization; regulators; business partners; suppliers and others who have an understanding of the service organization and its controls." +msgstr "" + +#: ./doc/security-guide/ch064_certifications-compliance-statements.xml:81(para) +msgid "There are two types of SOC 2 reports:" +msgstr "" + +#: ./doc/security-guide/ch064_certifications-compliance-statements.xml:91(para) +msgid "Type 2 – report on the fairness of the presentation of management's description of the service organization's system and the suitability of the design and operating effectiveness of the controls to achieve the related control objectives included in the description throughout a specified period." +msgstr "" + +#: ./doc/security-guide/ch064_certifications-compliance-statements.xml:99(para) +msgid "For more details see the AICPA Report on Controls at a Service Organization Relevant to Security, Availability, Processing Integrity, Confidentiality or Privacy." +msgstr "" + +#: ./doc/security-guide/ch064_certifications-compliance-statements.xml:108(title) +msgid "SOC 3" +msgstr "" + +#: ./doc/security-guide/ch064_certifications-compliance-statements.xml:109(para) +msgid "Service Organization Controls (SOC) 3 is a trust services report for service organizations. These reports are designed to meet the needs of users who want assurance on the controls at a service organization related to security, availability, processing integrity, confidentiality, or privacy but do not have the need for or the knowledge necessary to make effective use of a SOC 2 Report. These reports are prepared using the AICPA/Canadian Institute of Chartered Accountants (CICA) Trust Services Principles, Criteria, and Illustrations for Security, Availability, Processing Integrity, Confidentiality, and Privacy. Because they are general use reports, SOC 3 Reports can be freely distributed or posted on a website as a seal." +msgstr "" + +#: ./doc/security-guide/ch064_certifications-compliance-statements.xml:121(para) +msgid "For more details see the AICPA Trust Services Report for Service Organizations." +msgstr "" + +#: ./doc/security-guide/ch064_certifications-compliance-statements.xml:128(title) +msgid "ISO 27001/2" +msgstr "" + +#: ./doc/security-guide/ch064_certifications-compliance-statements.xml:129(para) +msgid "The ISO/IEC 27001/2 standards replace BS7799-2, and are specifications for an Information Security Management System (ISMS). An ISMS is a comprehensive set of policies and processes that an organization creates and maintains to manage risk to information assets.  These risks are based upon the confidentiality, integrity, and availability (CIA) of user information. The CIA security triad has been used as a foundation for much of the chapters in this book." +msgstr "" + +#: ./doc/security-guide/ch064_certifications-compliance-statements.xml:137(para) +msgid "For more details see ISO 27001." +msgstr "" + +#: ./doc/security-guide/ch064_certifications-compliance-statements.xml:143(title) +msgid "HIPAA / HITECH" +msgstr "" + +#: ./doc/security-guide/ch064_certifications-compliance-statements.xml:144(para) +msgid "The Health Insurance Portability and Accountability Act (HIPAA) is a United States congressional act that governs the collection, storage, use and destruction of patient health records. The act states that Protected Health Information (PHI) must be rendered \"unusable, unreadable, or indecipherable\" to unauthorized persons and that encryption for data 'at-rest' and 'inflight' should be addressed." +msgstr "" + +#: ./doc/security-guide/ch064_certifications-compliance-statements.xml:151(para) +msgid "HIPAA is not a certification, rather a guide for protecting healthcare data.  Similar to the PCI-DSS, the most important issues with both PCI and HIPPA is that a breach of credit card information, and health data, does not occur. In the instance of a breach the cloud provider will be scrutinized for compliance with PCI and HIPPA controls. If proven compliant, the provider can be expected to immediately implement remedial controls, breach notification responsibilities, and significant expenditure on additional compliance activities.  If not compliant, the cloud provider can expect on-site audit teams, fines, potential loss of merchant ID (PCI), and massive reputation impact." +msgstr "" + +#: ./doc/security-guide/ch064_certifications-compliance-statements.xml:163(para) +msgid "Users or organizations that possess PHI must support HIPAA requirements and are HIPAA covered entities. If an entity intends to use a service, or in this case, an OpenStack cloud that might use, store or have access to that PHI, then a Business Associate Agreement must be signed. The BAA is a contract between the HIPAA covered entity and the OpenStack service provider that requires the provider to handle that PHI in accordance with HIPAA requirements. If the service provider does not handle the PHI, such as with security controls and hardening, then they are subject to HIPAA fines and penalties." +msgstr "" + +#: ./doc/security-guide/ch064_certifications-compliance-statements.xml:174(para) +msgid "OpenStack architects interpret and respond to HIPAA statements, with data encryption remaining a core practice. Currently this would require any protected health information contained within an OpenStack deployment to be encrypted with industry standard encryption algorithms. Potential future OpenStack projects such as object encryption will facilitate HIPAA guidelines for compliance with the act." +msgstr "" + +#: ./doc/security-guide/ch064_certifications-compliance-statements.xml:181(para) +msgid "For more details see the Health Insurance Portability And Accountability Act." +msgstr "" + +#: ./doc/security-guide/ch064_certifications-compliance-statements.xml:187(title) +msgid "PCI-DSS" +msgstr "" + +#: ./doc/security-guide/ch064_certifications-compliance-statements.xml:188(para) +msgid "The Payment Card Industry Data Security Standard (PCI DSS) is defined by the Payment Card Industry Standards Council, and created to increase controls around card holder data to reduce credit card fraud. Annual compliance validation is assessed by an external Qualified Security Assessor (QSA) who creates a Report on Compliance (ROC), or by a Self-Assessment Questionnaire (SAQ) dependent on volume of card-holder transactions.  " +msgstr "" + +#: ./doc/security-guide/ch064_certifications-compliance-statements.xml:196(para) +msgid "OpenStack deployments which stores, processes, or transmits payment card details are in scope for the PCI-DSS. All OpenStack components that are not properly segmented from systems or networks that handle payment data fall under the guidelines of the PCI-DSS. Segmentation in the context of PCI-DSS does not support multi-tenancy, but rather physical separation (host/network). " +msgstr "" + +#: ./doc/security-guide/ch064_certifications-compliance-statements.xml:203(para) +msgid "For more details see PCI security standards." +msgstr "" + +#: ./doc/security-guide/ch064_certifications-compliance-statements.xml:209(title) +msgid "Government Standards" +msgstr "" + +#: ./doc/security-guide/ch064_certifications-compliance-statements.xml:212(title) +msgid "FedRAMP" +msgstr "" + +#: ./doc/security-guide/ch064_certifications-compliance-statements.xml:213(para) +msgid "\"The Federal Risk and Authorization Management Program (FedRAMP) is a government-wide program that provides a standardized approach to security assessment, authorization, and continuous monitoring for cloud products and services\". NIST 800-53 is the basis for both FISMA and FedRAMP which mandates security controls specifically selected to provide protection in cloud environments. FedRAMP can be extremely intensive from specificity around security controls, and the volume of documentation required to meet government standards." +msgstr "" + +#: ./doc/security-guide/ch064_certifications-compliance-statements.xml:223(para) +msgid "For more details see http://www.gsa.gov/portal/category/102371." +msgstr "" + +#: ./doc/security-guide/ch064_certifications-compliance-statements.xml:229(title) +msgid "ITAR" +msgstr "" + +#: ./doc/security-guide/ch064_certifications-compliance-statements.xml:230(para) +msgid "The International Traffic in Arms Regulations (ITAR) is a set of United States government regulations that control the export and import of defense-related articles and services on the United States Munitions List (USML) and related technical data. ITAR is often approached by cloud providers as an \"operational alignment\" rather than a formal certification. This typically involves implementing a segregated cloud environment following practices based on the NIST 800-53 framework, as per FISMA requirements, complemented with additional controls restricting access to \"U.S. Persons\" only and background screening." +msgstr "" + +#: ./doc/security-guide/ch064_certifications-compliance-statements.xml:241(para) +msgid "For more details see http://pmddtc.state.gov/regulations_laws/itar_official.html." +msgstr "" + +#: ./doc/security-guide/ch064_certifications-compliance-statements.xml:247(title) +msgid "FISMA" +msgstr "" + +#: ./doc/security-guide/ch064_certifications-compliance-statements.xml:248(para) +msgid "The Federal Information Security Management Act requires that government agencies create a comprehensive plan to implement numerous government security standards, and was enacted within the E-Government Act of 2002. FISMA outlines a process, which utilizing multiple NIST publications, prepares an information system to store and process government data." +msgstr "" + +#: ./doc/security-guide/ch064_certifications-compliance-statements.xml:255(para) +msgid "This process is broken apart into three primary categories:" +msgstr "" + +#: ./doc/security-guide/ch064_certifications-compliance-statements.xml:259(para) +msgid "System CategorizationThe information system will receive a security category as defined in Federal Information Processing Standards Publication 199 (FIPS 199). These categories reflect the potential impact of system compromise." +msgstr "" + +#: ./doc/security-guide/ch064_certifications-compliance-statements.xml:267(para) +msgid "Control SelectionBased upon system security category as defined in FIPS 199, an organization utilizes FIPS 200 to identify specific security control requirements for the information system. For example, if a system is categorized as “moderate” a requirement may be introduced to mandate “secure passwords.”" +msgstr "" + +#: ./doc/security-guide/ch064_certifications-compliance-statements.xml:276(para) +msgid "Control TailoringOnce system security controls are identified, an OpenStack architect will utilize NIST 800-53 to extract tailored control selection. For example, specification of what constitutes a “secure password.”" +msgstr "" + +#: ./doc/security-guide/ch039_case-studies-messaging.xml:3(title) +msgid "Case Studies: Messaging" +msgstr "" + +#: ./doc/security-guide/ch039_case-studies-messaging.xml:4(para) +msgid "The message queue is a critical piece of infrastructure that supports a number of OpenStack services but is most strongly associated with the Compute service. Due to the nature of the message queue service, Alice and Bob have similar security concerns. One of the larger concerns that remains is that many systems have access to this queue and there is no way for a consumer of the queue messages to verify which host or service placed the messages on the queue. An attacker who is able to successfully place messages on the queue is able to create and delete VM instances, attach the block storage of any tenant and a myriad of other malicious actions. There are a number of solutions on the horizon to fix this, with several proposals for message signing and encryption making their way through the OpenStack development process." +msgstr "" + +#: ./doc/security-guide/ch039_case-studies-messaging.xml:7(para) +msgid "In this case Alice's controls mimic those Bob has deployed for the public cloud." +msgstr "" + +#: ./doc/security-guide/ch039_case-studies-messaging.xml:11(para) +msgid "Bob assumes that at some point infrastructure or networks underpinning the Compute service may become compromised. Due to this, he recognizes the importance of locking down access to the message queue. To do this Bob deploys his RabbitMQ servers with SSL and X.509 client auth for access control. This in turn limits the capabilities of an attacker who has compromised a system that does not have queue access." +msgstr "" + +#: ./doc/security-guide/ch039_case-studies-messaging.xml:12(para) +msgid "Additionally, Bob adds strong network ACL rulesets to enforce which endpoints can communicate with the message servers. This second control provides some additional assurance should the other protections fail." +msgstr "" + +#: ./doc/security-guide/ch066_case-studies-compliance.xml:3(title) +msgid "Case Studies: Compliance" +msgstr "" + +#: ./doc/security-guide/ch066_case-studies-compliance.xml:4(para) +msgid "In this case study we discuss how Alice and Bob would address common compliance requirements. The preceding chapter refers to a wide variety of compliance certifications and standards. Alice will address compliance in a private cloud, while Bob will be focused on compliance for a public cloud." +msgstr "" + +#: ./doc/security-guide/ch066_case-studies-compliance.xml:7(para) +msgid "Alice is building an OpenStack private cloud for the United States government, specifically to provide elastic compute environments for signal processing. Alice has researched government compliance requirements, and has identified that her private cloud will be required to certify against FISMA and follow the FedRAMP accreditation process, which is required for all federal agencies, departments and contractors to become a Certified Cloud Provider (CCP). In this particular scenario for signal processing, the FISMA controls required will most likely be FISMA High, which indicates possible \"severe or catastrophic adverse effects\" should the information system become compromised. In addition to FISMA Moderate controls Alice must ensure her private cloud is FedRAMP certified, as this is a requirement for all agencies that currently utilize, or host federal information within a cloud environment." +msgstr "" + +#: ./doc/security-guide/ch066_case-studies-compliance.xml:8(para) +msgid "To meet these strict government regulations Alice undertakes a number of activities. Scoping of requirements is particularly important due to the volume of controls that must be implemented, which will be defined in NIST Publication 800-53." +msgstr "" + +#: ./doc/security-guide/ch066_case-studies-compliance.xml:9(para) +msgid "All technology within her private cloud must be FIPS certified technology, as mandated within NIST 800-53 and FedRAMP. As the U.S. Department of Defense is involved, Security Technical Implementation Guides (STIGs) will come into play, which are the configuration standards for DOD IA and IA-enabled devices / systems. Alice notices a number of complications here as there is no STIG for OpenStack, so she must address several underlying requirements for each OpenStack service; for example, the networking SRG and Application SRG will both be applicable (list of SRGs). Other critical controls include ensuring that all identities in the cloud use PKI, that SELinux is enabled, that encryption exists for all wire-level communications, and that continuous monitoring is in place and clearly documented. Alice is not concerned with object encryption, as this will be the tenants responsibility rather than the provider." +msgstr "" + +#: ./doc/security-guide/ch066_case-studies-compliance.xml:10(para) +msgid "If Alice has adequately scoped and executed these compliance activities, she may begin the process to become FedRAMP compliant by hiring an approved third-party auditor. Typically this process takes up to 6 months, after which she will receive an Authority to Operate and can offer OpenStack cloud services to the government." +msgstr "" + +#: ./doc/security-guide/ch066_case-studies-compliance.xml:14(para) +msgid "Bob is tasked with compliance for a new OpenStack public cloud deployment, that is focused on providing cloud services to both small developers and startups, as well as large enterprises. Bob recognizes that individual developers are not necessarily concerned with compliance certifications, but to larger enterprises certifications are critical. Specifically Bob desires to achieve SOC 1, SOC 2 Security, as well as ISO 27001/2 as quickly as possible. Bob references the Cloud Security Alliance Cloud Control Matrix (CCM) to assist in identifying common controls across these three certifications (such as periodic access reviews, auditable logging and monitoring services, risk assessment activities, security reviews, etc). Bob then engages an experienced audit team to conduct a gap analysis on the public cloud deployment, reviews the results and fills any gaps identified. Bob works with other team members to ensure that these security controls and activities are regularly conducted for a typical audit period (~6-12 months)." +msgstr "" + +#: ./doc/security-guide/ch066_case-studies-compliance.xml:31(para) +msgid "At the end of the audit period Bob has arranged for an external audit team to review in-scope security controls at randomly sampled points of time over a 6 month period. The audit team provides Bob with an official report for SOC 1 and SOC 2, and separately for ISO 27001/2. As Bob has been diligent in ensuring security controls are in place for his OpenStack public cloud, there are no additional gaps exposed on the report. Bob can now provide these official reports to his customers under NDA, and advertise that he is SOC 1, SOC 2 and ISO 27001/2 compliant on his website." +msgstr "" + +#: ./doc/security-guide/ch021_paste-and-middleware.xml:3(title) +msgid "API Endpoint Configuration Recommendations" +msgstr "" + +#: ./doc/security-guide/ch021_paste-and-middleware.xml:4(para) +msgid "This chapter provides recommendations for improving the security of both public and internal endpoints." +msgstr "" + +#: ./doc/security-guide/ch021_paste-and-middleware.xml:6(title) +msgid "Internal API Communications" +msgstr "" + +#: ./doc/security-guide/ch021_paste-and-middleware.xml:7(para) +msgid "OpenStack provides both public facing and private API endpoints. By default, OpenStack components use the publicly defined endpoints. The recommendation is to configure these components to use the API endpoint within the proper security domain." +msgstr "" + +#: ./doc/security-guide/ch021_paste-and-middleware.xml:8(para) +msgid "Services select their respective API endpoints based on the OpenStack service catalog.  The issue here is these services may not obey the listed public or internal API end point values. This can lead to internal management traffic being routed to external API endpoints." +msgstr "" + +#: ./doc/security-guide/ch021_paste-and-middleware.xml:10(title) +msgid "Configure Internal URLs in Identity Service Catalog" +msgstr "" + +#: ./doc/security-guide/ch021_paste-and-middleware.xml:11(para) +msgid "The Identity Service catalog should be aware of your internal URLs. While this feature is not utilized by default, it may be leveraged through configuration. Additionally, it should be forward-compatible with expectant changes once this behavior becomes the default." +msgstr "" + +#: ./doc/security-guide/ch021_paste-and-middleware.xml:12(para) +msgid "To register an internal URL for an endpoint:" +msgstr "" + +#: ./doc/security-guide/ch021_paste-and-middleware.xml:22(title) +msgid "Configure Applications for Internal URLs" +msgstr "" + +#: ./doc/security-guide/ch021_paste-and-middleware.xml:23(para) +msgid "Some services can be forced to use specific API endpoints.  Therefore, it is recommended that each OpenStack service communicating to the API of another service must be explicitly configured to access the proper internal API endpoint." +msgstr "" + +#: ./doc/security-guide/ch021_paste-and-middleware.xml:24(para) +msgid "Each project may present an inconsistent way of defining target API endpoints. Future releases of OpenStack seek to resolve these inconsistencies through consistent use of the Identity Service catalog." +msgstr "" + +#: ./doc/security-guide/ch021_paste-and-middleware.xml:26(title) +msgid "Configuration Example #1: Nova" +msgstr "" + +#: ./doc/security-guide/ch021_paste-and-middleware.xml:37(title) +msgid "Configuration Example #2: Cinder" +msgstr "" + +#: ./doc/security-guide/ch021_paste-and-middleware.xml:44(title) +msgid "Paste and Middleware" +msgstr "" + +#: ./doc/security-guide/ch021_paste-and-middleware.xml:45(para) +msgid "Most API endpoints and other HTTP services in OpenStack utilize the Python Paste Deploy library. This is important to understand from a security perspective as it allows for manipulation of the request filter pipeline through the application's configuration. Each element in this chain is referred to as middleware. Changing the order of filters in the pipeline or adding additional middleware may have unpredictable security impact." +msgstr "" + +#: ./doc/security-guide/ch021_paste-and-middleware.xml:46(para) +msgid "It is not uncommon that implementors will choose to add additional middleware to extend OpenStack's base functionality. We recommend implementors make careful consideration of the potential exposure introduced by the addition of non-standard software components to their HTTP request pipeline." +msgstr "" + +#: ./doc/security-guide/ch021_paste-and-middleware.xml:47(para) +msgid "Additional information on Paste Deploy may be found at http://pythonpaste.org/deploy/." +msgstr "" + +#: ./doc/security-guide/ch021_paste-and-middleware.xml:51(title) +msgid "API Endpoint Process Isolation & Policy" +msgstr "" + +#: ./doc/security-guide/ch021_paste-and-middleware.xml:52(para) +msgid "API endpoint processes, especially those that reside within the public security domain should be isolated as much as possible. Where deployments allow, API endpoints should be deployed on separate hosts for increased isolation." +msgstr "" + +#: ./doc/security-guide/ch021_paste-and-middleware.xml:54(title) ./doc/security-guide/ch038_transport-security.xml:119(title) +msgid "Namespaces" +msgstr "" + +#: ./doc/security-guide/ch021_paste-and-middleware.xml:55(para) +msgid "Many operating systems now provide compartmentalization support. Linux supports namespaces to assign processes into independent domains. System compartmentalization is covered in more detail in other parts of the guide." +msgstr "" + +#: ./doc/security-guide/ch021_paste-and-middleware.xml:58(title) ./doc/security-guide/ch038_transport-security.xml:124(title) +msgid "Network Policy" +msgstr "" + +#: ./doc/security-guide/ch021_paste-and-middleware.xml:59(para) +msgid "API endpoints typically bridge multiple security domains, as such particular attention should be paid to the compartmentalization of the API processes.  See the Security Domain Bridging section for additional information in this area." +msgstr "" + +#: ./doc/security-guide/ch021_paste-and-middleware.xml:60(para) +msgid "With careful modeling, network ACLs and IDS technologies can be use to enforce explicit point to point communication between network services. As critical cross domain service, this type of explicit enforcement works well for OpenStack's message queue service." +msgstr "" + +#: ./doc/security-guide/ch021_paste-and-middleware.xml:61(para) +msgid "Policy enforcement can be implemented through the configuration of services, host-based firewalls (such as IPTables), local policy (SELinux or AppArmor), and optionally enforced through global network policy." +msgstr "" + +#: ./doc/security-guide/ch021_paste-and-middleware.xml:64(title) ./doc/security-guide/ch038_transport-security.xml:129(title) ./doc/security-guide/ch052_devices.xml:90(title) +msgid "Mandatory Access Controls" +msgstr "" + +#: ./doc/security-guide/ch021_paste-and-middleware.xml:65(para) +msgid "API endpoint processes should be isolated from each other and other processes on a machine. The configuration for those processes should be restricted to those processes not only by Discretionary Access Controls, but through Mandatory Access Controls. The goal of these enhanced access control is to aid in the containment and escalation of API endpoint security breaches.  With mandatory access controls, such breaches will severely limit access to resources and provide earlier alerting on such events." +msgstr "" + +#: ./doc/security-guide/ch041_database-backend-considerations.xml:3(title) +msgid "Database Backend Considerations" +msgstr "" + +#: ./doc/security-guide/ch041_database-backend-considerations.xml:4(para) +msgid "The choice of database server is an important consideration in the security of an OpenStack deployment. While security considerations are not the only basis on which a database server must be chosen, security considerations are the only ones within the scope of this book. In practice, OpenStack only supports two database types: PostgreSQL and MySQL." +msgstr "" + +#: ./doc/security-guide/ch041_database-backend-considerations.xml:5(para) +msgid "PostgreSQL has a number of desirable security features such as Kerberos authentication, object-level security, and encryption support. The PostgreSQL community has done well to provide solid guidance, documentation, and tooling to promote positive security practices." +msgstr "" + +#: ./doc/security-guide/ch041_database-backend-considerations.xml:6(para) +msgid "MySQL has a large community, wide-spread adoption, and provides high availability options. MySQL also has the ability to provide enhanced client authentication by way of plug-in authentication mechanisms. Forked distributions in the MySQL community provide many options for consideration. It is important to choose a specific implementation of MySQL based on a thorough evaluation of the security posture and the level of support provided for the given distribution." +msgstr "" + +#: ./doc/security-guide/ch041_database-backend-considerations.xml:8(title) +msgid "Security References for Database Backends" +msgstr "" + +#: ./doc/security-guide/ch041_database-backend-considerations.xml:9(para) +msgid "Those deploying MySQL or PostgreSQL are advised to refer to existing security guidance. Some references are listed below:" +msgstr "" + +#: ./doc/security-guide/ch041_database-backend-considerations.xml:10(para) +msgid "MySQL:" +msgstr "" + +#: ./doc/security-guide/ch041_database-backend-considerations.xml:12(link) +msgid "OWASP MySQL Hardening" +msgstr "" + +#: ./doc/security-guide/ch041_database-backend-considerations.xml:15(link) +msgid "MySQL Pluggable Authentication" +msgstr "" + +#: ./doc/security-guide/ch041_database-backend-considerations.xml:18(link) +msgid "Security in MySQL" +msgstr "" + +#: ./doc/security-guide/ch041_database-backend-considerations.xml:21(para) +msgid "PostgreSQL:" +msgstr "" + +#: ./doc/security-guide/ch041_database-backend-considerations.xml:23(link) +msgid "OWASP PostgreSQL Hardening" +msgstr "" + +#: ./doc/security-guide/ch041_database-backend-considerations.xml:26(link) +msgid "Total security in a PostgreSQL database" +msgstr "" + +#: ./doc/security-guide/ch014_best-practices-for-operator-mode-access.xml:3(title) +msgid "Management Interfaces" +msgstr "" + +#: ./doc/security-guide/ch014_best-practices-for-operator-mode-access.xml:4(para) +msgid "It is necessary for administrators to perform command and control over the cloud for various operational functions. It is important these command and control facilities are understood and secured." +msgstr "" + +#: ./doc/security-guide/ch014_best-practices-for-operator-mode-access.xml:5(para) +msgid "OpenStack provides several management interfaces for operators and tenants:" +msgstr "" + +#: ./doc/security-guide/ch014_best-practices-for-operator-mode-access.xml:7(para) +msgid "OpenStack Dashboard (Horizon)" +msgstr "" + +#: ./doc/security-guide/ch014_best-practices-for-operator-mode-access.xml:10(para) ./doc/security-guide/ch014_best-practices-for-operator-mode-access.xml:69(title) +msgid "OpenStack API" +msgstr "" + +#: ./doc/security-guide/ch014_best-practices-for-operator-mode-access.xml:13(para) ./doc/security-guide/ch014_best-practices-for-operator-mode-access.xml:93(title) +msgid "Secure Shell (SSH)" +msgstr "" + +#: ./doc/security-guide/ch014_best-practices-for-operator-mode-access.xml:16(para) +msgid "OpenStack Management Utilities (nova-manage, glance-manage, etc.)" +msgstr "" + +#: ./doc/security-guide/ch014_best-practices-for-operator-mode-access.xml:19(para) +msgid "Out-of-Band Management Interfaces (IPMI, etc.)" +msgstr "" + +#: ./doc/security-guide/ch014_best-practices-for-operator-mode-access.xml:24(para) +msgid "The OpenStack Dashboard (Horizon) provides administrators and tenants a web-based graphical interface to provision and access cloud-based resources. The dashboard communicates with the back-end services via calls to the OpenStack API (discussed above)." +msgstr "" + +#: ./doc/security-guide/ch014_best-practices-for-operator-mode-access.xml:26(title) ./doc/security-guide/ch014_best-practices-for-operator-mode-access.xml:72(title) ./doc/security-guide/ch026_compute.xml:13(title) ./doc/security-guide/ch026_compute.xml:40(title) +msgid "Capabilities" +msgstr "" + +#: ./doc/security-guide/ch014_best-practices-for-operator-mode-access.xml:28(para) +msgid "As a cloud administrator, the dashboard provides an overall view of the size and state of your cloud. You can create users and tenants/projects, assign users to tenant/projects and set limits on the resources available for them." +msgstr "" + +#: ./doc/security-guide/ch014_best-practices-for-operator-mode-access.xml:31(para) +msgid "The dashboard provides tenant-users a self-service portal to provision their own resources within the limits set by administrators." +msgstr "" + +#: ./doc/security-guide/ch014_best-practices-for-operator-mode-access.xml:34(para) +msgid "The dashboard provides GUI support for routers and load-balancers. For example, the dashboard now implements all of the main Networking features." +msgstr "" + +#: ./doc/security-guide/ch014_best-practices-for-operator-mode-access.xml:37(para) +msgid "It is an extensible Django web application that allows easy plug-in of third-party products and services, such as billing, monitoring, and additional management tools." +msgstr "" + +#: ./doc/security-guide/ch014_best-practices-for-operator-mode-access.xml:40(para) +msgid "The dashboard can also be branded for service providers and other commercial vendors." +msgstr "" + +#: ./doc/security-guide/ch014_best-practices-for-operator-mode-access.xml:47(para) +msgid "The dashboard requires cookies and JavaScript to be enabled in the web browser." +msgstr "" + +#: ./doc/security-guide/ch014_best-practices-for-operator-mode-access.xml:50(para) +msgid "The web server that hosts dashboard should be configured for SSL to ensure data is encrypted." +msgstr "" + +#: ./doc/security-guide/ch014_best-practices-for-operator-mode-access.xml:53(para) +msgid "Both the Horizon web service and the OpenStack API it uses to communicate with the back-end are susceptible to web attack vectors such as denial of service and must be monitored." +msgstr "" + +#: ./doc/security-guide/ch014_best-practices-for-operator-mode-access.xml:56(para) +msgid "It is now possible (though there are numerous deployment/security implications) to upload an image file directly from a user’s hard disk to Glance through Horizon. For multi-GB images it is still strongly recommended that the upload be done using the Glance CLI" +msgstr "" + +#: ./doc/security-guide/ch014_best-practices-for-operator-mode-access.xml:59(para) +msgid "Create and manage security groups through dashboard. The security groups allows L3-L4 packet filtering for security policies to protect virtual machines" +msgstr "" + +#: ./doc/security-guide/ch014_best-practices-for-operator-mode-access.xml:65(citetitle) +msgid "Grizzly Release Notes" +msgstr "" + +#: ./doc/security-guide/ch014_best-practices-for-operator-mode-access.xml:70(para) +msgid "The OpenStack API is a RESTful web service endpoint to access, provision and automate cloud-based resources.  Operators and users typically access the API through command-line utilities (i.e. Nova, Glance, etc.), language-specific libraries, or third-party tools." +msgstr "" + +#: ./doc/security-guide/ch014_best-practices-for-operator-mode-access.xml:74(para) +msgid "To the cloud administrator the API provides an overall view of the size and state of the cloud deployment and allows the creation of users, tenants/projects, assigning users to tenants/projects and specifying resource quotas on a per tenant/project basis." +msgstr "" + +#: ./doc/security-guide/ch014_best-practices-for-operator-mode-access.xml:77(para) +msgid "The API provides a tenant interface for provisioning, managing, and accessing their resources." +msgstr "" + +#: ./doc/security-guide/ch014_best-practices-for-operator-mode-access.xml:84(para) +msgid "The API service should be configured for SSL to ensure data is encrypted." +msgstr "" + +#: ./doc/security-guide/ch014_best-practices-for-operator-mode-access.xml:87(para) +msgid "As a web service, OpenStack API is susceptible to familiar web site attack vectors such as denial of service attacks." +msgstr "" + +#: ./doc/security-guide/ch014_best-practices-for-operator-mode-access.xml:94(para) +msgid "It has become industry practice to use secure shell (SSH) access for the management of Linux and Unix systems. SSH uses secure cryptographic primitives for communication. With the scope and importance of SSH in typical OpenStack deployments, it is important to understand best practices for deploying SSH." +msgstr "" + +#: ./doc/security-guide/ch014_best-practices-for-operator-mode-access.xml:96(title) +msgid "Host Key Fingerprints" +msgstr "" + +#: ./doc/security-guide/ch014_best-practices-for-operator-mode-access.xml:97(para) +msgid "Often overlooked is the need for key management for SSH hosts. As most or all hosts in an OpenStack deployment will provide an SSH service, it is important to have confidence in connections to these hosts. It cannot be understated that failing to provide a reasonably secure and accessible method to verify SSH host key fingerprints is ripe for abuse and exploitation." +msgstr "" + +#: ./doc/security-guide/ch014_best-practices-for-operator-mode-access.xml:98(para) +msgid "All SSH daemons have private host keys and, upon connection, offer a host key fingerprint. This host key fingerprint is the hash of an unsigned public key. It is important these host key fingerprints are known in advance of making SSH connections to those hosts. Verification of host key fingerprints is instrumental in detecting man-in-the-middle attacks." +msgstr "" + +#: ./doc/security-guide/ch014_best-practices-for-operator-mode-access.xml:99(para) +msgid "Typically, when an SSH daemon is installed, host keys will be generated. It is necessary that the hosts have sufficient entropy during host key generation. Insufficient entropy during host key generation can result in the possibility to eavesdrop on SSH sessions." +msgstr "" + +#: ./doc/security-guide/ch014_best-practices-for-operator-mode-access.xml:100(para) +msgid "Once the SSH host key is generated, the host key fingerprint should be stored in a secure and queriable location. One particularly convenient solution is DNS using SSHFP resource records as defined in RFC-4255. For this to be secure, it is necessary that DNSSEC be deployed." +msgstr "" + +#: ./doc/security-guide/ch014_best-practices-for-operator-mode-access.xml:104(title) +msgid "Management Utilities" +msgstr "" + +#: ./doc/security-guide/ch014_best-practices-for-operator-mode-access.xml:105(para) +msgid "The OpenStack Management Utilities are open-source Python command-line clients that make API calls. There is a client for each OpenStack service (nova, glance, etc.). In addition to the standard CLI client, most of the services have a management command line which makes direct calls to the database. These dedicated management utilities are slowly being deprecated." +msgstr "" + +#: ./doc/security-guide/ch014_best-practices-for-operator-mode-access.xml:115(para) +msgid "The dedicated management utilities (*-manage) in some cases use the direct database connection." +msgstr "" + +#: ./doc/security-guide/ch014_best-practices-for-operator-mode-access.xml:118(para) +msgid "Ensure that the .rc file which has your credential information is secured." +msgstr "" + +#: ./doc/security-guide/ch014_best-practices-for-operator-mode-access.xml:124(para) +msgid "OpenStack End User Guide section command line clients overview" +msgstr "" + +#: ./doc/security-guide/ch014_best-practices-for-operator-mode-access.xml:125(para) +msgid "OpenStack End User Guide section Download and source the OpenStack RC file" +msgstr "" + +#: ./doc/security-guide/ch014_best-practices-for-operator-mode-access.xml:129(title) +msgid "Out-of-Band Management Interface" +msgstr "" + +#: ./doc/security-guide/ch014_best-practices-for-operator-mode-access.xml:130(para) +msgid "OpenStack management relies on out-of-band management interfaces such as the IPMI protocol to access into nodes running OpenStack components. IPMI is a very popular specification to remotely manage, diagnose and reboot servers whether the operating system is running or the system has crashed." +msgstr "" + +#: ./doc/security-guide/ch014_best-practices-for-operator-mode-access.xml:134(para) +msgid "Use strong passwords and safeguard them, or use client-side SSL authentication." +msgstr "" + +#: ./doc/security-guide/ch014_best-practices-for-operator-mode-access.xml:137(para) +msgid "Ensure that the network interfaces are on their own private(management or a separate) network. Segregate management domains with firewalls or other network gear." +msgstr "" + +#: ./doc/security-guide/ch014_best-practices-for-operator-mode-access.xml:140(para) +msgid "If you use a web interface to interact with the BMC/IPMI, always use the SSL interface, such as https or port 443. This SSL interface should NOT use self-signed certificates, as is often default, but should have trusted certificates using the correctly defined fully qualified domain names (FQDNs)." +msgstr "" + +#: ./doc/security-guide/ch014_best-practices-for-operator-mode-access.xml:149(para) +msgid "Monitor the traffic on the management network. The anomalies might be easier to track than on the busier compute nodes." +msgstr "" + +#: ./doc/security-guide/ch014_best-practices-for-operator-mode-access.xml:154(para) +msgid "Out of band management interfaces also often include graphical machine console access. It is often possible, although not necessarily default, that these interfaces are encrypted. Consult with your system software documentation for encrypting these interfaces." +msgstr "" + +#: ./doc/security-guide/ch014_best-practices-for-operator-mode-access.xml:158(link) +msgid "Hacking servers that are turned off" +msgstr "" + +#: ./doc/security-guide/ch028_case-studies-identity-management.xml:3(title) +msgid "Case Studies: Identity Management" +msgstr "" + +#: ./doc/security-guide/ch028_case-studies-identity-management.xml:4(para) +msgid "In this case study we discuss how Alice and Bob would address configuration of OpenStack core services. These include the Keystone Identity service, Dashboard, and Compute services. Alice will be concerned with integration into the existing government directory services, while Bob will need to provide access to the public." +msgstr "" + +#: ./doc/security-guide/ch028_case-studies-identity-management.xml:7(para) +msgid "Alice's enterprise has a well-established directory service with two-factor authentication for all users. She configures Keystone to support an external authentication service supporting authentication with government-issued access cards. She also uses an external LDAP server to provide role information for the users that is integrated with the access control policy. Due to FedRAMP compliance requirements, Alice implements two-factor authentication on the Management network for all administrator access." +msgstr "" + +#: ./doc/security-guide/ch028_case-studies-identity-management.xml:8(para) +msgid "Alice also deploys the Dashboard to manage many aspects of the cloud.  She deploys the Dashboard with HSTS to ensure that only HTTPS is used.  The Dashboard resides within an internal subdomain of the private network domain name system." +msgstr "" + +#: ./doc/security-guide/ch028_case-studies-identity-management.xml:9(para) +msgid "Alice decides to use SPICE instead of VNC for the virtual console.  She wants to take advantage of the emerging capabilities in SPICE." +msgstr "" + +#: ./doc/security-guide/ch028_case-studies-identity-management.xml:13(para) +msgid "Bob must support authentication by the general public, so he elects to use provide for username / password authentication. He has concerns about brute force attacks attempting to crack user passwords, so he also uses an external authentication extension that throttles the number of failed login attempts. Bob's Management network is separate from the other networks within his cloud, but can be reached from his corporate network via ssh. As recommended earlier, Bob requires administrators to use two-factor authentication on the Management network to reduce the risk from compromised administrator passwords." +msgstr "" + +#: ./doc/security-guide/ch028_case-studies-identity-management.xml:14(para) +msgid "Bob also deploys the Dashboard to manage many aspects of the cloud.  He deploys the Dashboard with HSTS to ensure that only HTTPS is used.  He has ensured that the Dashboard is deployed on a second-level domain due to the limitations of the same-origin policy. He also disables HORIZON_IMAGES_ALLOW_UPLOAD to prevent resource exhaustion." +msgstr "" + +#: ./doc/security-guide/ch028_case-studies-identity-management.xml:15(para) +msgid "Bob decides to use VNC for his virtual console for its maturity and security features." +msgstr "" + +#: ./doc/security-guide/ch037_risks.xml:3(title) +msgid "Message Queuing Architecture" +msgstr "" + +#: ./doc/security-guide/ch037_risks.xml:4(para) +msgid "Inter-process communication within OpenStack is facilitated via message queueing services. Today, three messaging service backends are supported:" +msgstr "" + +#: ./doc/security-guide/ch037_risks.xml:6(para) +msgid "RabbitMQ" +msgstr "" + +#: ./doc/security-guide/ch037_risks.xml:9(para) +msgid "Qpid" +msgstr "" + +#: ./doc/security-guide/ch037_risks.xml:12(para) +msgid "ZeroMQ" +msgstr "" + +#: ./doc/security-guide/ch037_risks.xml:15(para) +msgid "Both RabbitMQ and Qpid are Advanced Message Queuing Protocol (AMQP) frameworks which provide message queues for peer-to-peer communication. Queue implementations are typically deployed as centralized or decentralized pool of queue servers. ZeroMQ differs by communicating directly using TCP sockets between peers." +msgstr "" + +#: ./doc/security-guide/ch037_risks.xml:16(para) +msgid "Message queues effectively facilitate command and control functions across OpenStack deployments. Once access to the queue is permitted no further authorization checks are performed. Services accessible via the queue do validate the contexts and tokens within the actual message payload. However, awareness of the token's expiration value should be noted as these tokens are potentially replayable and may provide authorization for other services within the infrastructure." +msgstr "" + +#: ./doc/security-guide/ch037_risks.xml:17(para) +msgid "OpenStack does not support message-level confidence (i.e., message signing). Because of this, the message transport itself must be secured and authentication to the queue server must be performed. For HA configurations, queue to queue authentication and encryption should to be performed as well." +msgstr "" + +#: ./doc/security-guide/ch037_risks.xml:18(para) +msgid "With ZeroMQ messaging, IPC sockets are used on individual machines. These sockets may be vulnerable to attack for local message injection and snooping unless secured by an operator." +msgstr "" + +#: ./doc/security-guide/ch026_compute.xml:3(title) ./doc/security-guide/ch004_book-introduction.xml:122(title) +msgid "Compute" +msgstr "" + +#: ./doc/security-guide/ch026_compute.xml:4(para) +msgid "The Compute Service (Nova) is one of the more complex OpenStack services.  It runs in many locations throughout the cloud and interacts with a variety of internal services.  For this reason, most of our recommendations regarding best practices for Compute Service configuration are distributed throughout this book. We provide specific details in the sections on Management, API Endpoints, Messaging, and Database." +msgstr "" + +#: ./doc/security-guide/ch026_compute.xml:6(title) +msgid "Virtual Console Selection" +msgstr "" + +#: ./doc/security-guide/ch026_compute.xml:7(para) +msgid "One decision a cloud architect will need to make regarding Compute Service configuration is whether to use VNC or SPICE. Below we provide some details on the differences between these options." +msgstr "" + +#: ./doc/security-guide/ch026_compute.xml:9(title) +msgid "Virtual Network Computer (VNC)" +msgstr "" + +#: ./doc/security-guide/ch026_compute.xml:10(para) +msgid "OpenStack can be configured to provide remote desktop console access to instances for tenants and/or administrators using the Virtual Network Computer (VNC) protocol.  " +msgstr "" + +#: ./doc/security-guide/ch026_compute.xml:15(para) +msgid "The OpenStack Dashboard (Horizon) can provide a VNC console for instances directly on the web page using the HTML5 noVNC client.  This requires the nova-novncproxy service to bridge from the public network to the management network." +msgstr "" + +#: ./doc/security-guide/ch026_compute.xml:18(para) +msgid "The nova command line utility can return a URL for the VNC console for access by the nova Java VNC client. This requires the nova-xvpvncproxy service to bridge from the public network to the management network." +msgstr "" + +#: ./doc/security-guide/ch026_compute.xml:25(para) +msgid "The nova-novncproxyand nova-xvpvncproxy services by default open public-facing ports that are token authenticated." +msgstr "" + +#: ./doc/security-guide/ch026_compute.xml:28(para) +msgid "By default, the remote desktop traffic is not encrypted. Havana is expected to have VNC connections secured by Kerberos." +msgstr "" + +#: ./doc/security-guide/ch026_compute.xml:34(link) +msgid "Secure Connections to VNC ports" +msgstr "" + +#: ./doc/security-guide/ch026_compute.xml:37(title) +msgid "Simple Protocol for Independent Computing Environments (SPICE)" +msgstr "" + +#: ./doc/security-guide/ch026_compute.xml:38(para) +msgid "As an alternative to VNC, OpenStack provides remote desktop access to guest virtual machines using the Simple Protocol for Independent Computing Environments (SPICE) protocol." +msgstr "" + +#: ./doc/security-guide/ch026_compute.xml:42(para) +msgid "SPICE is supported by the OpenStack Dashboard (Horizon) directly on the instance web page.  This requires the nova-spicehtml5proxy service." +msgstr "" + +#: ./doc/security-guide/ch026_compute.xml:45(para) +msgid "The nova command line utility can return a URL for SPICE console for access by a SPICE-html client." +msgstr "" + +#: ./doc/security-guide/ch026_compute.xml:50(title) +msgid "Limitations" +msgstr "" + +#: ./doc/security-guide/ch026_compute.xml:52(para) +msgid "Although SPICE has many advantages over VNC, the spice-html5 browser integration currently doesn't really allow admins to take advantage of any of the benefits. To take advantage of SPICE features like multi-monitor, USB pass through, etc. admins are recommended to use a standalone SPICE client within the Management Network." +msgstr "" + +#: ./doc/security-guide/ch026_compute.xml:59(para) +msgid "The nova-spicehtml5proxy service by default opens public-facing ports that are token authenticated." +msgstr "" + +#: ./doc/security-guide/ch026_compute.xml:62(para) +msgid "The functionality and integration are still evolving. We will access the features in the next release and make recommendations." +msgstr "" + +#: ./doc/security-guide/ch026_compute.xml:65(para) +msgid "As is the case for VNC, at this time we recommend using SPICE from the management network in addition to limiting use to few individuals." +msgstr "" + +#: ./doc/security-guide/ch026_compute.xml:71(link) +msgid "SPICE Console" +msgstr "" + +#: ./doc/security-guide/ch026_compute.xml:72(link) +msgid "Red Hat bug 913607" +msgstr "" + +#: ./doc/security-guide/ch026_compute.xml:73(link) +msgid "SPICE support in RDO Grizzly" +msgstr "" + +#. When image changes, this message will be marked fuzzy or untranslated for you. +#. It doesn't matter what you translate it to: it's not used at all. +#: ./doc/security-guide/ch013_node-bootstrapping.xml:60(None) ./doc/security-guide/ch013_node-bootstrapping.xml:65(None) +msgid "@@image: 'static/node-provisioning-pxe.png'; md5=51b76c5aced74f935490b37ba921dc43" +msgstr "" + +#: ./doc/security-guide/ch013_node-bootstrapping.xml:8(title) +msgid "Integrity Life-cycle" +msgstr "" + +#: ./doc/security-guide/ch013_node-bootstrapping.xml:9(para) +msgid "We define integrity life cycle as a deliberate process that provides assurance that we are always running the expected software with the expected configurations throughout the cloud. This process begins with secure bootstrapping and is maintained through configuration management and security monitoring. This chapter provides recommendations on how to approach the integrity life-cycle process." +msgstr "" + +#: ./doc/security-guide/ch013_node-bootstrapping.xml:17(title) +msgid "Secure Bootstrapping" +msgstr "" + +#: ./doc/security-guide/ch013_node-bootstrapping.xml:18(para) +msgid "Nodes in the cloud -- including compute, storage, network, service, and hybrid nodes -- should have an automated provisioning process. This ensures that nodes are provisioned consistently and correctly. This also facilitates security patching, upgrading, bug fixing, and other critical changes. Since this process installs new software that runs at the highest privilege levels in the cloud, it is important to verify that the correct software is installed. This includes the earliest stages of the boot process." +msgstr "" + +#: ./doc/security-guide/ch013_node-bootstrapping.xml:27(para) +msgid "There are a variety of technologies that enable verification of these early boot stages. These typically require hardware support such as the trusted platform module (TPM), Intel Trusted Execution Technology (TXT), dynamic root of trust measurement (DRTM), and Unified Extensible Firmware Interface (UEFI) secure boot. In this book, we will refer to all of these collectively as secure boot technologies. We recommend using secure boot, while acknowledging that many of the pieces necessary to deploy this require advanced technical skills in order to customize the tools for each environment. Utilizing secure boot will require deeper integration and customization than many of the other recommendations in this guide. TPM technology, while common in most business class laptops and desktops for several years, and is now becoming available in servers together with supporting BIOS. Proper planning is essential to a successful secure boot deployment." +msgstr "" + +#: ./doc/security-guide/ch013_node-bootstrapping.xml:43(para) +msgid "A complete tutorial on secure boot deployment is beyond the scope of this book. Instead, here we provide a framework for how to integrate secure boot technologies with the typical node provisioning process. For additional details, cloud architects should refer to the related specifications and software configuration manuals." +msgstr "" + +#: ./doc/security-guide/ch013_node-bootstrapping.xml:50(title) +msgid "Node Provisioning" +msgstr "" + +#: ./doc/security-guide/ch013_node-bootstrapping.xml:51(para) +msgid "Nodes should use Preboot eXecution Environment (PXE) for provisioning. This significantly reduces the effort required for redeploying nodes. The typical process involves the node receiving various boot stages (i.e., progressively more complex software to execute) from a server." +msgstr "" + +#: ./doc/security-guide/ch013_node-bootstrapping.xml:68(para) +msgid "We recommend using a separate, isolated network within the management security domain for provisioning. This network will handle all PXE traffic, along with the subsequent boot stage downloads depicted above. Note that the node boot process begins with two insecure operations: DHCP and TFTP. Then the boot process downloads over SSL the remaining information required to deploy the node. This information might include an initramfs and a kernel. This concludes by downloading the remaining information needed to deploy the node. This may be an operating system installer, a basic install managed by Chef or Puppet, or even a complete file system image that is written directly to disk." +msgstr "" + +#: ./doc/security-guide/ch013_node-bootstrapping.xml:82(para) +msgid "While utilizing SSL during the PXE boot process is somewhat more challenging, common PXE firmware projects, such as iPXE, provide this support. Typically this involves building the PXE firmware with knowledge of the allowed SSL certificate chain(s) so that it can properly validate the server certificate.  This raises the bar for an attacker by limiting the number of insecure, plain text network operations." +msgstr "" + +#: ./doc/security-guide/ch013_node-bootstrapping.xml:92(title) +msgid "Verified Boot" +msgstr "" + +#: ./doc/security-guide/ch013_node-bootstrapping.xml:93(para) +msgid "In general, there are two different strategies for verifying the boot process. Traditional secure boot will validate the code run at each step in the process, and stop the boot if code is incorrect. Boot attestation will record which code is run at each step, and provide this information to another machine as proof that the boot process completed as expected. In both cases, the first step is to measure each piece of code before it is run. In this context, a measurement is effectively a SHA-1 hash of the code, taken before it is executed.  The hash is stored in a platform configuration register (PCR) in the TPM." +msgstr "" + +#: ./doc/security-guide/ch013_node-bootstrapping.xml:105(para) +msgid "Note: SHA-1 is used here because this is what the TPM chips support." +msgstr "" + +#: ./doc/security-guide/ch013_node-bootstrapping.xml:107(para) +msgid "Each TPM has at least 24 PCRs. The TCG Generic Server Specification, v1.0, March 2005, defines the PCR assignments for boot-time integrity measurements. The table below shows a typical PCR configuration. The context indicates if the values are determined based on the node hardware (firmware) or the software provisioned onto the node. Some values are influenced by firmware versions, disk sizes, and other low-level information. Therefore, it is important to have good practices in place around configuration management to ensure that each system deployed is configured exactly as desired." +msgstr "" + +#: ./doc/security-guide/ch013_node-bootstrapping.xml:127(emphasis) +msgid "Register" +msgstr "" + +#: ./doc/security-guide/ch013_node-bootstrapping.xml:128(emphasis) +msgid "What Is Measured" +msgstr "" + +#: ./doc/security-guide/ch013_node-bootstrapping.xml:131(emphasis) +msgid "Context" +msgstr "" + +#: ./doc/security-guide/ch013_node-bootstrapping.xml:134(para) +msgid "PCR-00" +msgstr "" + +#: ./doc/security-guide/ch013_node-bootstrapping.xml:135(para) +msgid "Core Root of Trust Measurement (CRTM), Bios code, Host platform extensions" +msgstr "" + +#: ./doc/security-guide/ch013_node-bootstrapping.xml:137(para) ./doc/security-guide/ch013_node-bootstrapping.xml:142(para) ./doc/security-guide/ch013_node-bootstrapping.xml:147(para) +msgid "Hardware" +msgstr "" + +#: ./doc/security-guide/ch013_node-bootstrapping.xml:140(para) +msgid "PCR-01" +msgstr "" + +#: ./doc/security-guide/ch013_node-bootstrapping.xml:141(para) +msgid "Host Platform Configuration" +msgstr "" + +#: ./doc/security-guide/ch013_node-bootstrapping.xml:145(para) +msgid "PCR-02" +msgstr "" + +#: ./doc/security-guide/ch013_node-bootstrapping.xml:146(para) +msgid "Option ROM Code " +msgstr "" + +#: ./doc/security-guide/ch013_node-bootstrapping.xml:150(para) +msgid "PCR-03" +msgstr "" + +#: ./doc/security-guide/ch013_node-bootstrapping.xml:151(para) +msgid "Option ROM Configuration and Data " +msgstr "" + +#: ./doc/security-guide/ch013_node-bootstrapping.xml:152(para) +msgid "Hardware " +msgstr "" + +#: ./doc/security-guide/ch013_node-bootstrapping.xml:155(para) +msgid "PCR-04" +msgstr "" + +#: ./doc/security-guide/ch013_node-bootstrapping.xml:156(para) +msgid "Initial Program Loader (IPL) Code. For example, master boot record." +msgstr "" + +#: ./doc/security-guide/ch013_node-bootstrapping.xml:158(para) ./doc/security-guide/ch013_node-bootstrapping.xml:163(para) ./doc/security-guide/ch013_node-bootstrapping.xml:168(para) ./doc/security-guide/ch013_node-bootstrapping.xml:173(para) ./doc/security-guide/ch013_node-bootstrapping.xml:179(para) ./doc/security-guide/ch013_node-bootstrapping.xml:184(para) ./doc/security-guide/ch013_node-bootstrapping.xml:189(para) +msgid "Software " +msgstr "" + +#: ./doc/security-guide/ch013_node-bootstrapping.xml:161(para) +msgid "PCR-05" +msgstr "" + +#: ./doc/security-guide/ch013_node-bootstrapping.xml:162(para) +msgid "IPL Code Configuration and Data " +msgstr "" + +#: ./doc/security-guide/ch013_node-bootstrapping.xml:166(para) +msgid "PCR-06" +msgstr "" + +#: ./doc/security-guide/ch013_node-bootstrapping.xml:167(para) +msgid "State Transition and Wake Events " +msgstr "" + +#: ./doc/security-guide/ch013_node-bootstrapping.xml:171(para) +msgid "PCR-07" +msgstr "" + +#: ./doc/security-guide/ch013_node-bootstrapping.xml:172(para) +msgid "Host Platform Manufacturer Control " +msgstr "" + +#: ./doc/security-guide/ch013_node-bootstrapping.xml:176(para) +msgid "PCR-08" +msgstr "" + +#: ./doc/security-guide/ch013_node-bootstrapping.xml:177(para) +msgid "Platform specific, often Kernel, Kernel Extensions, and Drivers" +msgstr "" + +#: ./doc/security-guide/ch013_node-bootstrapping.xml:182(para) +msgid "PCR-09" +msgstr "" + +#: ./doc/security-guide/ch013_node-bootstrapping.xml:183(para) +msgid "Platform specific, often Initramfs" +msgstr "" + +#: ./doc/security-guide/ch013_node-bootstrapping.xml:187(para) +msgid "PCR-10 to PCR-23" +msgstr "" + +#: ./doc/security-guide/ch013_node-bootstrapping.xml:188(para) +msgid "Platform specific " +msgstr "" + +#: ./doc/security-guide/ch013_node-bootstrapping.xml:194(para) +msgid "At the time of this writing, very few clouds are using secure boot technologies in a production environment. As a result, these technologies are still somewhat immature. We recommend planning carefully in terms of hardware selection. For example, ensure that you have a TPM and Intel TXT support. Then verify how the node hardware vendor populates the PCR values. For example, which values will be available for validation. Typically the PCR values listed under the software context in the table above are the ones that a cloud architect has direct control over. But even these may change as the software in the cloud is upgraded.  Configuration management should be linked into the PCR policy engine to ensure that the validation is always up to date." +msgstr "" + +#: ./doc/security-guide/ch013_node-bootstrapping.xml:207(para) +msgid "Each manufacturer must provide the BIOS and firmware code for their servers. Different servers, hypervisors, and operating systems will choose to populate different PCRs.  In most real world deployments, it will be impossible to validate every PCR against a known good quantity (\"golden measurement\"). Experience has shown that, even within a single vendor's product line, the measurement process for a given PCR may not be consistent. We recommend establishing a baseline for each server and monitoring the PCR values for unexpected changes. Third-party software may be available to assist in the TPM provisioning and monitoring process, depending upon your chosen hypervisor solution." +msgstr "" + +#: ./doc/security-guide/ch013_node-bootstrapping.xml:219(para) +msgid "The initial program loader (IPL) code will most likely be the PXE firmware, assuming the node deployment strategy outlined above. Therefore, the secure boot or boot attestation process can measure all of the early stage boot code, such as, bios, firmware, and the like, the PXE firmware, and the node kernel. Ensuring that each node has the correct versions of these pieces installed provides a solid foundation on which to build the rest of the node software stack." +msgstr "" + +#: ./doc/security-guide/ch013_node-bootstrapping.xml:227(para) +msgid "Depending on the strategy selected, in the event of a failure the node will either fail to boot or it can report the failure back to another entity in the cloud. For secure boot, the node will fail to boot and a provisioning service within the management security domain must recognize this and log the event. For boot attestation, the node will already be running when the failure is detected. In this case the node should be immediately quarantined by disabling its network access. Then the event should be analyzed for the root cause. In either case, policy should dictate how to proceed after a failure. A cloud may automatically attempt to re-provision a node a certain number of times. Or it may immediately notify a cloud administrator to investigate the problem. The right policy here will be deployment and failure mode specific." +msgstr "" + +#: ./doc/security-guide/ch013_node-bootstrapping.xml:243(title) +msgid "Node Hardening" +msgstr "" + +#: ./doc/security-guide/ch013_node-bootstrapping.xml:244(para) +msgid "At this point we know that the node has booted with the correct kernel and underlying components. There are many paths for hardening a given operating system deployment. The specifics on these steps are outside of the scope of this book.  We recommend following the guidance from a hardening guide specific to your operating system.  For example, the security technical implementation guides (STIG) and the NSA guides are useful starting places." +msgstr "" + +#: ./doc/security-guide/ch013_node-bootstrapping.xml:254(para) +msgid "The nature of the nodes makes additional hardening possible. We recommend the following additional steps for production nodes:" +msgstr "" + +#: ./doc/security-guide/ch013_node-bootstrapping.xml:259(para) +msgid "Use a read-only file system where possible. Ensure that writeable file systems do not permit execution.  This can be handled through the mount options provided in /etc/fstab." +msgstr "" + +#: ./doc/security-guide/ch013_node-bootstrapping.xml:265(para) +msgid "Use a mandatory access control policy to contain the instances, the node services, and any other critical processes and data on the node.  See the discussions on sVirt / SELinux and AppArmor below." +msgstr "" + +#: ./doc/security-guide/ch013_node-bootstrapping.xml:271(para) +msgid "Remove any unnecessary software packages. This should result in a very stripped down installation because a compute node has a relatively small number of dependencies." +msgstr "" + +#: ./doc/security-guide/ch013_node-bootstrapping.xml:277(para) +msgid "Finally, the node kernel should have a mechanism to validate that the rest of the node starts in a known good state. This provides the necessary link from the boot validation process to validating the entire system. The steps for doing this will be deployment specific. As an example, a kernel module could verify a hash over the blocks comprising the file system before mounting it using dm-verity." +msgstr "" + +#: ./doc/security-guide/ch013_node-bootstrapping.xml:289(title) +msgid "Runtime Verification" +msgstr "" + +#: ./doc/security-guide/ch013_node-bootstrapping.xml:290(para) +msgid "Once the node is running, we need to ensure that it remains in a good state over time. Broadly speaking, this includes both configuration management and security monitoring. The goals for each of these areas are different. By checking both, we achieve higher assurance that the system is operating as desired. We discuss configuration management in the management section, and security monitoring below." +msgstr "" + +#: ./doc/security-guide/ch013_node-bootstrapping.xml:298(title) +msgid "Intrusion Detection System" +msgstr "" + +#: ./doc/security-guide/ch013_node-bootstrapping.xml:299(para) +msgid "Host-based intrusion detection tools are also useful for automated validation of the cloud internals. There are a wide variety of host-based intrusion detection tools available. Some are open source projects that are freely available, while others are commercial. Typically these tools analyze data from a variety of sources and produce security alerts based on rule sets and/or training. Typical capabilities include log analysis, file integrity checking, policy monitoring, and rootkit detection. More advanced -- often custom -- tools can validate that in-memory process images match the on-disk executable and validate the execution state of a running process." +msgstr "" + +#: ./doc/security-guide/ch013_node-bootstrapping.xml:311(para) +msgid "One critical policy decision for a cloud architect is what to do with the output from a security monitoring tool. There are effectively two options. The first is to alert a human to investigate and/or take corrective action. This could be done by including the security alert in a log or events feed for cloud administrators. The second option is to have the cloud take some form of remedial action automatically, in addition to logging the event. Remedial actions could include anything from re-installing a node to performing a minor service configuration. However, automated remedial action can be challenging due to the possibility of false positives." +msgstr "" + +#: ./doc/security-guide/ch013_node-bootstrapping.xml:322(para) +msgid "False positives occur when the security monitoring tool produces a security alert for a benign event. Due to the nature of security monitoring tools, false positives will most certainly occur from time to time. Typically a cloud administrator can tune security monitoring tools to reduce the false positives, but this may also reduce the overall detection rate at the same time. These classic trade-offs must be understood and accounted for when setting up a security monitoring system in the cloud." +msgstr "" + +#: ./doc/security-guide/ch013_node-bootstrapping.xml:331(para) +msgid "The selection and configuration of a host-based intrusion detection tool is highly deployment specific. We recommend starting by exploring the following open source projects which implement a variety of host-based intrusion detection and file monitoring features." +msgstr "" + +#: ./doc/security-guide/ch013_node-bootstrapping.xml:339(link) +msgid "OSSEC" +msgstr "" + +#: ./doc/security-guide/ch013_node-bootstrapping.xml:343(link) +msgid "Samhain" +msgstr "" + +#: ./doc/security-guide/ch013_node-bootstrapping.xml:348(link) +msgid "Tripwire" +msgstr "" + +#: ./doc/security-guide/ch013_node-bootstrapping.xml:352(link) +msgid "AIDE" +msgstr "" + +#: ./doc/security-guide/ch013_node-bootstrapping.xml:355(para) +msgid "Network intrusion detection tools complement the host-based tools. OpenStack doesn't have a specific network IDS built-in, but OpenStack's networking component, Neutron, provides a plugin mechanism to enable different technologies via the Neutron API. This plugin architecture will allow tenants to develop API extensions to insert and configure their own advanced networking services like a firewall, an intrusion detection system, or a VPN between the VMs." +msgstr "" + +#: ./doc/security-guide/ch013_node-bootstrapping.xml:363(para) +msgid "Similar to host-based tools, the selection and configuration of a network-based intrusion detection tool is deployment specific. Snort is the leading open source networking intrusion detection tool, and a good starting place to learn more." +msgstr "" + +#: ./doc/security-guide/ch013_node-bootstrapping.xml:369(para) +msgid "There are a few important security considerations for network and host-based intrusion detection systems." +msgstr "" + +#: ./doc/security-guide/ch013_node-bootstrapping.xml:373(para) +msgid "It is important to consider the placement of the Network IDS on the cloud (for example, adding it to the network boundary and/or around sensitive networks). The placement depends on your network environment but make sure to monitor the impact the IDS may have on your services depending on where you choose to add it. Encrypted traffic, such as SSL, cannot generally be inspected for content by a Network IDS. However, the Network IDS may still provide some benefit in identifying anomalous unencrypted traffic on the network." +msgstr "" + +#: ./doc/security-guide/ch013_node-bootstrapping.xml:385(para) +msgid "In some deployments it may be required to add host-based IDS on sensitive components on security domain bridges.  A host-based IDS may detect anomalous activity by compromised or unauthorized processes on the component. The IDS should transmit alert and log information on the Management network." +msgstr "" + +#: ./doc/security-guide/ch038_transport-security.xml:3(title) +msgid "Messaging Security" +msgstr "" + +#: ./doc/security-guide/ch038_transport-security.xml:4(para) +msgid "This chapter discusses security hardening approaches for the three most common message queuing solutions use in OpenStack: RabbitMQ, Qpid, and ZeroMQ." +msgstr "" + +#: ./doc/security-guide/ch038_transport-security.xml:6(title) +msgid "Messaging Transport Security" +msgstr "" + +#: ./doc/security-guide/ch038_transport-security.xml:7(para) +msgid "AMQP based solutions (Qpid and RabbitMQ) support transport-level security using SSL. ZeroMQ messaging does not natively support SSL, but transport-level security is possible using labelled IPSec or CIPSO network labels." +msgstr "" + +#: ./doc/security-guide/ch038_transport-security.xml:8(para) +msgid "We highly recommend enabling transport-level cryptography for your message queue. Using SSL for the messaging client connections provides protection of the communications from tampering and eavesdropping in-transit to the messaging server. Below is guidance on how SSL is typically configured for the two popular messaging servers Qpid and RabbitMQ. When configuring the trusted certificate authority (CA) bundle that your messaging server uses to verify client connections, it is recommended that this be limited to only the CA used for your nodes, preferably an internally managed CA. The bundle of trusted CAs will determine which client certificates will be authorized and pass the client-server verification step of the setting up the SSL connection. Note, when installing the certificate and key files, ensure that the file permissions are restricted, for example chmod 0600, and the ownership is restricted to the messaging server daemon user to prevent unauthorized access by other processes and users on the messaging server." +msgstr "" + +#: ./doc/security-guide/ch038_transport-security.xml:10(title) +msgid "RabbitMQ Server SSL Configuration" +msgstr "" + +#: ./doc/security-guide/ch038_transport-security.xml:11(para) +msgid "The following lines should be added to the system-wide RabbitMQ configuration file, typically /etc/rabbitmq/rabbitmq.config:" +msgstr "" + +#: ./doc/security-guide/ch038_transport-security.xml:24(para) +msgid "Note, the 'tcp_listeners' option is set to '[]' to prevent it from listening an on non-SSL port. 'ssl_listeners' option should be restricted to only listen on the management network for the services." +msgstr "" + +#: ./doc/security-guide/ch038_transport-security.xml:25(para) +msgid "For more information on RabbitMQ SSL configuration see:" +msgstr "" + +#: ./doc/security-guide/ch038_transport-security.xml:27(link) +msgid "RabbitMQ Configuration" +msgstr "" + +#: ./doc/security-guide/ch038_transport-security.xml:30(link) +msgid "RabbitMQ SSL" +msgstr "" + +#: ./doc/security-guide/ch038_transport-security.xml:35(title) +msgid "Qpid Server SSL Configuration" +msgstr "" + +#: ./doc/security-guide/ch038_transport-security.xml:36(para) +msgid "The Apache Foundation has a messaging security guide for Qpid. See:" +msgstr "" + +#: ./doc/security-guide/ch038_transport-security.xml:38(link) +msgid "Apache Qpid SSL" +msgstr "" + +#: ./doc/security-guide/ch038_transport-security.xml:44(title) +msgid "Queue Authentication and Access Control" +msgstr "" + +#: ./doc/security-guide/ch038_transport-security.xml:45(para) +msgid "RabbitMQ and Qpid offer authentication and access control mechanisms for controlling access to queues. ZeroMQ offers no such mechanisms." +msgstr "" + +#: ./doc/security-guide/ch038_transport-security.xml:46(para) +msgid "Simple Authentication and Security Layer (SASL) is a framework for authentication and data security in Internet protocols. Both RabbitMQ and Qpid offer SASL and other pluggable authentication mechanisms beyond simple usernames and passwords that allow for increased authentication security. While RabbitMQ supports SASL, support in OpenStack does not currently allow for requesting a specific SASL authentication mechanism. RabbitMQ support in OpenStack allows for either username and password authentication over an unencrypted connection or username and password in conjunction with X.509 client certificates to establish the secure SSL connection." +msgstr "" + +#: ./doc/security-guide/ch038_transport-security.xml:47(para) +msgid "We recommend configuring X.509 client certificates on all the OpenStack service nodes for client connections to the messaging queue and where possible (currently only Qpid) perform authentication with X.509 client certificates. When using usernames and passwords, accounts should be created per-service and node for finer grained auditability of access to the queue." +msgstr "" + +#: ./doc/security-guide/ch038_transport-security.xml:48(para) +msgid "The SSL libraries in use by these queuing servers should also be considered prior to deployment. Qpid uses Mozilla's NSS library, whereas RabbitMQ uses Erlang's SSL module which uses OpenSSL." +msgstr "" + +#: ./doc/security-guide/ch038_transport-security.xml:50(title) +msgid "Authentication Configuration Example - RabbitMQ" +msgstr "" + +#: ./doc/security-guide/ch038_transport-security.xml:51(para) +msgid "On the RabbitMQ server, delete the default 'guest' user:" +msgstr "" + +#: ./doc/security-guide/ch038_transport-security.xml:54(para) +msgid "On the RabbitMQ server, for each OpenStack service or node that communicates with the message queue set up user accounts and privileges:" +msgstr "" + +#: ./doc/security-guide/ch038_transport-security.xml:58(para) +msgid "For additional configuration information see:" +msgstr "" + +#: ./doc/security-guide/ch038_transport-security.xml:60(link) +msgid "RabbitMQ Access Control" +msgstr "" + +#: ./doc/security-guide/ch038_transport-security.xml:63(link) +msgid "RabbitMQ Authentication" +msgstr "" + +#: ./doc/security-guide/ch038_transport-security.xml:66(link) +msgid "RabbitMQ Plugins" +msgstr "" + +#: ./doc/security-guide/ch038_transport-security.xml:69(link) +msgid "RabbitMQ SASL External Auth" +msgstr "" + +#: ./doc/security-guide/ch038_transport-security.xml:74(title) +msgid "OpenStack Service Configuration - RabbitMQ" +msgstr "" + +#: ./doc/security-guide/ch038_transport-security.xml:86(para) +msgid "NOTE: A bug exists in the current version of OpenStack Grizzly where if 'kombu_ssl_version' is currently specified in the configuration file for any of the OpenStack services it will cause the following python traceback error: 'TypeError: an integer is required'. The current workaround is to remove 'kombu_ssl_version' from the configuration file. Refer to bug report 1195431 for current status." +msgstr "" + +#: ./doc/security-guide/ch038_transport-security.xml:89(title) +msgid "Authentication Configuration Example - Qpid" +msgstr "" + +#: ./doc/security-guide/ch038_transport-security.xml:90(para) +msgid "For configuration information see:" +msgstr "" + +#: ./doc/security-guide/ch038_transport-security.xml:92(link) +msgid "Apache Qpid Authentication" +msgstr "" + +#: ./doc/security-guide/ch038_transport-security.xml:95(link) +msgid "Apache Qpid Authorization" +msgstr "" + +#: ./doc/security-guide/ch038_transport-security.xml:100(title) +msgid "OpenStack Service Configuration - Qpid" +msgstr "" + +#: ./doc/security-guide/ch038_transport-security.xml:109(para) +msgid "Optionally, if using SASL with Qpid specify the SASL mechanisms in use by adding:" +msgstr "" + +#: ./doc/security-guide/ch038_transport-security.xml:115(title) +msgid "Message Queue Process Isolation & Policy" +msgstr "" + +#: ./doc/security-guide/ch038_transport-security.xml:116(para) +msgid "Each project provides a number of services which send and consume messages. Each binary which sends a message is expected to consume messages, if only replies, from the queue." +msgstr "" + +#: ./doc/security-guide/ch038_transport-security.xml:117(para) +msgid "Message queue service processes should be isolated from each other and other processes on a machine." +msgstr "" + +#: ./doc/security-guide/ch038_transport-security.xml:120(para) +msgid "Network namespaces are highly recommended for all services running on OpenStack Compute Hypervisors. This will help prevent against the bridging of network traffic between VM guests and the management network." +msgstr "" + +#: ./doc/security-guide/ch038_transport-security.xml:121(para) +msgid "When using ZeroMQ messaging, each host must run at least one ZeroMQ message receiver to receive messages from the network and forward messages to local processes via IPC. It is possible and advisable to run an independent message receiver per project within an IPC namespace, along with other services within the same project." +msgstr "" + +#: ./doc/security-guide/ch038_transport-security.xml:125(para) +msgid "Queue servers should only accept connections from the management network. This applies to all implementations. This should be implemented through configuration of services and optionally enforced through global network policy." +msgstr "" + +#: ./doc/security-guide/ch038_transport-security.xml:126(para) +msgid "When using ZeroMQ messaging, each project should run a separate ZeroMQ receiver process on a port dedicated to services belonging to that project. This is equivalent to the AMQP concept of control exchanges." +msgstr "" + +#: ./doc/security-guide/ch038_transport-security.xml:130(para) +msgid "The configuration for these processes should be restricted to those processes, not only by Directory Access Controls, but through Mandatory Access Controls. The goal of such restrictions is to prevent isolation from other processes running on the same machine(s)." +msgstr "" + +#: ./doc/security-guide/ch044_case-studies-database.xml:3(title) +msgid "Case Studies: Database" +msgstr "" + +#: ./doc/security-guide/ch044_case-studies-database.xml:4(para) +msgid "In this case study we discuss how Alice and Bob would address database selection and configuration for their respective private and public clouds." +msgstr "" + +#: ./doc/security-guide/ch044_case-studies-database.xml:7(para) +msgid "Alice's organization has high availability concerns, so she has elected to use MySQL for the database. She further places the database on the Management network and uses SSL with mutual authentication among the services to ensure secure access. Given there will be no external access of the database, she uses certificates signed with the organization's self-signed root certificate on the database and its access endpoints. Alice creates separate user accounts for each database user, and configures the database to use both passwords and X.509 certificates for authentication. She elects not to use the nova-conductor sub-service due to the desire for fine-grained access control policies and audit support." +msgstr "" + +#: ./doc/security-guide/ch044_case-studies-database.xml:11(para) +msgid "Bob is concerned about strong separation of his tenants' data, so he has elected to use the Postgres database , known for its stronger security features.  The database resides on the Management network and uses SSL with mutual authentication with the services. Since the database is on the Management network, the database uses certificates signed with the company's self-signed root certificate. Bob creates separate user accounts for each database user, and configures the database to use both passwords and X.509 certificates for authentication. He elects not to use the nova-conductor sub-service due to a desire for fine-grained access control." +msgstr "" + +#. When image changes, this message will be marked fuzzy or untranslated for you. +#. It doesn't matter what you translate it to: it's not used at all. +#: ./doc/security-guide/ch001_acknowledgements.xml:8(None) ./doc/security-guide/ch001_acknowledgements.xml:11(None) +msgid "@@image: 'static/book-sprint-all-logos.png'; md5=f2d97c3130c32f31412f5af41ad72d39" +msgstr "" + +#: ./doc/security-guide/ch001_acknowledgements.xml:3(title) +msgid "Acknowledgments" +msgstr "" + +#: ./doc/security-guide/ch001_acknowledgements.xml:4(para) +msgid "The OpenStack Security Group would like to acknowledge contributions from the following organizations who were instrumental in making this book possible. These are:" +msgstr "" + +#. When image changes, this message will be marked fuzzy or untranslated for you. +#. It doesn't matter what you translate it to: it's not used at all. +#: ./doc/security-guide/ch033_securing-neutron-services.xml:24(None) ./doc/security-guide/ch033_securing-neutron-services.xml:27(None) +msgid "@@image: 'static/1aa-logical-neutron-flow.png'; md5=63bd2e81863b9b381adb1c6951517498" +msgstr "" + +#: ./doc/security-guide/ch033_securing-neutron-services.xml:3(title) +msgid "Securing OpenStack Networking Services" +msgstr "" + +#: ./doc/security-guide/ch033_securing-neutron-services.xml:4(para) +msgid "In order to secure OpenStack Networking, an understanding of the workflow process for tenant instance creation needs to be mapped to security domains. " +msgstr "" + +#: ./doc/security-guide/ch033_securing-neutron-services.xml:5(para) +msgid "There are four main services that interact with OpenStack Networking. In a typical OpenStack deployment these services map to the following security domains:" +msgstr "" + +#: ./doc/security-guide/ch033_securing-neutron-services.xml:7(para) +msgid "OpenStack Dashboard: Public and Management" +msgstr "" + +#: ./doc/security-guide/ch033_securing-neutron-services.xml:10(para) +msgid "OpenStack Identity: Management" +msgstr "" + +#: ./doc/security-guide/ch033_securing-neutron-services.xml:13(para) +msgid "OpenStack Compute Node: Management and Guest" +msgstr "" + +#: ./doc/security-guide/ch033_securing-neutron-services.xml:16(para) +msgid "OpenStack Network Node: Management, Guest, and possibly Public depending upon neutron-plugin in use." +msgstr "" + +#: ./doc/security-guide/ch033_securing-neutron-services.xml:19(para) +msgid "SDN Services Node: Management, Guest and possibly Public depending upon product used." +msgstr "" + +#: ./doc/security-guide/ch033_securing-neutron-services.xml:30(para) +msgid "In order to isolate sensitive data communication between the OpenStack Networking services and other OpenStack core services, we strongly recommend that these communication channels be configured to only allow communications over an isolated management network." +msgstr "" + +#: ./doc/security-guide/ch033_securing-neutron-services.xml:32(title) +msgid "OpenStack Networking Service Configuration" +msgstr "" + +#: ./doc/security-guide/ch033_securing-neutron-services.xml:34(title) +msgid "Restrict Bind Address of the API server: neutron-server" +msgstr "" + +#: ./doc/security-guide/ch033_securing-neutron-services.xml:35(para) +msgid "To restrict the interface or IP address on which the OpenStack Networking API service binds a network socket for incoming client connections, specify the bind_host and bind_port in the neutron.conf file as shown:" +msgstr "" + +#: ./doc/security-guide/ch033_securing-neutron-services.xml:44(title) +msgid "Restrict DB and RPC communication of the OpenStack Networking services:" +msgstr "" + +#: ./doc/security-guide/ch033_securing-neutron-services.xml:45(para) +msgid "Various components of the OpenStack Networking services use either the messaging queue or database connections to communicate with other components in OpenStack Networking." +msgstr "" + +#: ./doc/security-guide/ch033_securing-neutron-services.xml:46(para) +msgid "It is recommended that you follow the guidelines provided in the Database Authentication and Access Control chapter in the Database section for all components that require direct DB connections." +msgstr "" + +#: ./doc/security-guide/ch033_securing-neutron-services.xml:47(para) +msgid "It is recommended that you follow the guidelines provided in the Queue Authentication and Access Control chapter in the Messaging section for all components that require RPC communication." +msgstr "" + +#. When image changes, this message will be marked fuzzy or untranslated for you. +#. It doesn't matter what you translate it to: it's not used at all. +#: ./doc/security-guide/ch004_book-introduction.xml:113(None) ./doc/security-guide/ch004_book-introduction.xml:118(None) +msgid "@@image: 'static/marketecture-diagram.png'; md5=4ab13a64f80c210be3120abc5c7aee8a" +msgstr "" + +#: ./doc/security-guide/ch004_book-introduction.xml:8(title) +msgid "Introduction to OpenStack" +msgstr "" + +#: ./doc/security-guide/ch004_book-introduction.xml:9(para) +msgid "This guide provides security insight into OpenStack deployments. The intended audience is cloud architects, deployers, and administrators. In addition, cloud users will find the guide both educational and helpful in provider selection, while auditors will find it useful as a reference document to support their compliance certification efforts. This guide is also recommended for anyone interested in cloud security." +msgstr "" + +#: ./doc/security-guide/ch004_book-introduction.xml:16(para) +msgid "Each OpenStack deployment embraces a wide variety of technologies, spanning Linux distributions, database systems, messaging queues, OpenStack components themselves, access control policies, logging services, security monitoring tools, and much more. It should come as no surprise that the security issues involved are equally diverse, and their in-depth analysis would require several guides. We strive to find a balance, providing enough context to understand OpenStack security issues and their handling, and provide external references for further information. The guide could be read from start to finish or sampled as necessary like a reference." +msgstr "" + +#: ./doc/security-guide/ch004_book-introduction.xml:27(para) +msgid "We briefly introduce the kinds of clouds: private, public, and hybrid before presenting an overview of the OpenStack components and their related security concerns in the remainder of the chapter." +msgstr "" + +#: ./doc/security-guide/ch004_book-introduction.xml:32(title) +msgid "Cloud types" +msgstr "" + +#: ./doc/security-guide/ch004_book-introduction.xml:33(para) +msgid "OpenStack is a key enabler in adoption of cloud technology and has several common deployment use cases. These are commonly known as Public, Private, and Hybrid models. The following sections use the National Institute of Standards and Technology (NIST) definition of cloud to introduce these different types of cloud as they apply to OpenStack." +msgstr "" + +#: ./doc/security-guide/ch004_book-introduction.xml:42(title) +msgid "Public cloud" +msgstr "" + +#: ./doc/security-guide/ch004_book-introduction.xml:43(para) +msgid "According to NIST, a public cloud is one in which the infrastructure is open to the general public for consumption. OpenStack public clouds are typically run by a service provider and can be consumed by individuals, corporations, or any paying customer. A public cloud provider may expose a full set of features such as software defined networking, block storage, in addition to multiple instance types. Due to the nature of public clouds, they are exposed to a higher degree of risk. As a consumer of a public cloud you should validate that your selected provider has the necessary certifications, attestations, and other regulatory considerations. As a public cloud provider, depending on your target customers, you may be subject to one or more regulations. Additionally, even if not required to meet regulatory requirements, a provider should ensure tenant isolation as well as protecting management infrastructure from external attacks." +msgstr "" + +#: ./doc/security-guide/ch004_book-introduction.xml:61(title) +msgid "Private cloud" +msgstr "" + +#: ./doc/security-guide/ch004_book-introduction.xml:62(para) +msgid "At the opposite end of the spectrum is the private cloud. As NIST defines it, a private cloud is provisioned for exclusive use by a single organization comprising multiple consumers, such as business units. It may be owned, managed, and operated by the organization, a third-party, or some combination of them, and it may exist on or off premises. Private cloud use cases are diverse, as such, their individual security concerns vary." +msgstr "" + +#: ./doc/security-guide/ch004_book-introduction.xml:72(title) +msgid "Community cloud" +msgstr "" + +#: ./doc/security-guide/ch004_book-introduction.xml:73(para) +msgid "NIST defines a community cloud as one whose  infrastructure is provisioned for the exclusive use by a specific community of consumers from organizations that have shared concerns. For example, mission, security requirements, policy, and compliance considerations. It may be owned, managed, and operated by one or more of the organizations in the community, a third-party, or some combination of them, and it may exist on or off premises." +msgstr "" + +#: ./doc/security-guide/ch004_book-introduction.xml:83(title) +msgid "Hybrid cloud" +msgstr "" + +#: ./doc/security-guide/ch004_book-introduction.xml:84(para) +msgid "A hybrid cloud is defined by NIST as a composition of two or more distinct cloud infrastructures, such as private, community, or public, that remain unique entities, but are bound together by standardized or proprietary technology that enables data and application portability, such as cloud bursting for load balancing between clouds. For example an online retailer may have their advertising and catalogue presented on a public cloud that allows for elastic provisioning. This would enable them to handle seasonal loads in a flexible, cost-effective fashion. Once a customer begins to process their order, they are transferred to the more secure private cloud backend that is PCI compliant." +msgstr "" + +#: ./doc/security-guide/ch004_book-introduction.xml:96(para) +msgid "For the purposes of this document, we treat Community and Hybrid similarly, dealing explicitly only with the extremes of Public and Private clouds from a security perspective. Your security measures depend where your deployment falls upon the private public continuum." +msgstr "" + +#: ./doc/security-guide/ch004_book-introduction.xml:104(title) +msgid "OpenStack service overview" +msgstr "" + +#: ./doc/security-guide/ch004_book-introduction.xml:105(para) +msgid "OpenStack embraces a modular architecture to provide a set of core services that facilitates scalability and elasticity as core design tenets. This chapter briefly reviews OpenStack components, their use cases and security considerations." +msgstr "" + +#: ./doc/security-guide/ch004_book-introduction.xml:123(para) +msgid "OpenStack Compute Service (Nova) provides services to support the management of virtual machine instances at scale, instances that host multi-tiered applications, dev/test environments, \"Big Data\" crunching Hadoop clusters, and/or high performance computing." +msgstr "" + +#: ./doc/security-guide/ch004_book-introduction.xml:128(para) +msgid "The Compute Service facilitates this management through an abstraction layer that interfaces with supported hypervisors, which we address later on in more detail." +msgstr "" + +#: ./doc/security-guide/ch004_book-introduction.xml:131(para) +msgid "Later in the guide, we focus generically on the virtualization stack as it relates to hypervisors." +msgstr "" + +#: ./doc/security-guide/ch004_book-introduction.xml:133(para) +msgid "For information about the current state of feature support, see OpenStack Hypervisor Support Matrix." +msgstr "" + +#: ./doc/security-guide/ch004_book-introduction.xml:137(para) +msgid "The security of Compute is critical for an OpenStack deployment. Hardening techniques should include support for strong instance isolation, secure communication between Compute sub-components, and resiliency of public-facing API endpoints." +msgstr "" + +#: ./doc/security-guide/ch004_book-introduction.xml:144(title) ./doc/security-guide/ch027_storage.xml:8(title) +msgid "Object Storage" +msgstr "" + +#: ./doc/security-guide/ch004_book-introduction.xml:145(para) +msgid "The OpenStack Object Storage Service (Swift) provides support for storing and retrieving arbitrary data in the cloud. The Object Storage Service provides both a native API and an Amazon Web Services S3 compatible API. The service provides a high degree of resiliency through data replication and can handle petabytes of data." +msgstr "" + +#: ./doc/security-guide/ch004_book-introduction.xml:151(para) +msgid "It is important to understand that object storage differs from traditional file system storage. It is best used for static data such as media files (MP3s, images, videos), virtual machine images, and backup files." +msgstr "" + +#: ./doc/security-guide/ch004_book-introduction.xml:155(para) +msgid "Object security should focus on access control and encryption of data in transit and at rest. Other concerns may relate to system abuse, illegal or malicious content storage, and cross authentication attack vectors." +msgstr "" + +#: ./doc/security-guide/ch004_book-introduction.xml:161(title) +msgid "Block Storage" +msgstr "" + +#: ./doc/security-guide/ch004_book-introduction.xml:162(para) +msgid "The OpenStack Block Storage service (Cinder) provides persistent block storage for compute instances. The Block Storage Service is responsible for managing the life-cycle of block devices, from the creation and attachment of volumes to instances, to their release." +msgstr "" + +#: ./doc/security-guide/ch004_book-introduction.xml:167(para) +msgid "Security considerations for block storage are similar to that of object storage." +msgstr "" + +#: ./doc/security-guide/ch004_book-introduction.xml:171(title) +msgid "OpenStack Networking" +msgstr "" + +#: ./doc/security-guide/ch004_book-introduction.xml:172(para) +msgid "The OpenStack Networking Service (Neutron, previously called Quantum) provides various networking services to cloud users (tenants) such as IP address management, DNS, DHCP, load balancing, and security groups (network access rules, like firewall policies). It provides a framework for software defined networking (SDN) that allows for pluggable integration with various networking solutions." +msgstr "" + +#: ./doc/security-guide/ch004_book-introduction.xml:180(para) +msgid "OpenStack Networking allows cloud tenants to manage their guest network configurations. Security concerns with the networking service include network traffic isolation, availability, integrity and confidentiality." +msgstr "" + +#: ./doc/security-guide/ch004_book-introduction.xml:187(para) +msgid "The OpenStack Dashboard Service (Horizon) provides a web-based interface for both cloud administrators and cloud tenants. Through this interface administrators and tenants can provision, manage, and monitor cloud resources. Horizon is commonly deployed in a public facing manner with all the usual security concerns of public web portals." +msgstr "" + +#: ./doc/security-guide/ch004_book-introduction.xml:195(title) +msgid "Identity Service" +msgstr "" + +#: ./doc/security-guide/ch004_book-introduction.xml:196(para) +msgid "The OpenStack Identity Service (Keystone) is a shared service that provides authentication and authorization services throughout the entire cloud infrastructure. The Identity Service has pluggable support for multiple forms of authentication." +msgstr "" + +#: ./doc/security-guide/ch004_book-introduction.xml:201(para) +msgid "Security concerns here pertain to trust in authentication, management of authorization tokens, and secure communication." +msgstr "" + +#: ./doc/security-guide/ch004_book-introduction.xml:206(title) +msgid "Image Service" +msgstr "" + +#: ./doc/security-guide/ch004_book-introduction.xml:207(para) +msgid "The OpenStack Image Service (Glance) provides disk image management services. The Image Service provides image discovery, registration, and delivery services to Compute, the compute service, as needed." +msgstr "" + +#: ./doc/security-guide/ch004_book-introduction.xml:211(para) +msgid "Trusted processes for managing the life cycle of disk images are required, as are all the previously mentioned issues with respect to data security." +msgstr "" + +#: ./doc/security-guide/ch004_book-introduction.xml:216(title) +msgid "Other supporting technology" +msgstr "" + +#: ./doc/security-guide/ch004_book-introduction.xml:217(para) +msgid "OpenStack relies on messaging for internal communication between several of its services. By default, OpenStack uses message queues based on the Advanced Message Queue Protocol (AMQP). Similar to most OpenStack services, it supports pluggable components. Today the implementation backend could be RabbitMQ, Qpid, or ZeroMQ." +msgstr "" + +#: ./doc/security-guide/ch004_book-introduction.xml:226(para) +msgid "As most management commands flow through the message queueing system, it is a primary security concern for any OpenStack deployment. Message queueing security is discussed in detail later in this guide." +msgstr "" + +#: ./doc/security-guide/ch004_book-introduction.xml:230(para) +msgid "Several of the components use databases though it is not explicitly called out. Securing the access to the databases and their contents is yet another security concern, and consequently discussed in more detail later in this guide." +msgstr "" + +#: ./doc/security-guide/ch063_compliance-activities.xml:3(title) +msgid "Compliance Activities" +msgstr "" + +#: ./doc/security-guide/ch063_compliance-activities.xml:4(para) +msgid "There are a number of standard activities that will greatly assist with the compliance process. In this chapter we outline some of the most common compliance activities. These are not specific to OpenStack, however we provide references to relevant sections in this book as useful context." +msgstr "" + +#: ./doc/security-guide/ch063_compliance-activities.xml:6(title) +msgid "Information Security Management System (ISMS)" +msgstr "" + +#: ./doc/security-guide/ch063_compliance-activities.xml:7(para) +msgid "An Information Security Management System (ISMS) is a comprehensive set of policies and processes that an organization creates and maintains to manage risk to information assets. The most common ISMS for cloud deployments is ISO/IEC 27001/2, which creates a solid foundation of security controls and practices for achieving more stringent compliance certifications." +msgstr "" + +#: ./doc/security-guide/ch063_compliance-activities.xml:10(title) +msgid "Risk Assessment" +msgstr "" + +#: ./doc/security-guide/ch063_compliance-activities.xml:11(para) +msgid "A Risk Assessment framework identifies risks within an organization or service, and specifies ownership of these risks, along with implementation and mitigation strategies. Risks apply to all areas of the service, from technical controls to environmental disaster scenarios and human elements, for example a malicious insider (or rogue employee). Risks can be rated using a variety of mechanisms, for example likelihood vs impact. An OpenStack deployment risk assessment can include control gaps that are described in this book." +msgstr "" + +#: ./doc/security-guide/ch063_compliance-activities.xml:14(title) +msgid "Access & Log Reviews" +msgstr "" + +#: ./doc/security-guide/ch063_compliance-activities.xml:15(para) +msgid "Periodic access and log reviews are required to ensure authentication, authorization, and accountability in a service deployment. Specific guidance for OpenStack on these topics are discussed in-depth in the logging section." +msgstr "" + +#: ./doc/security-guide/ch063_compliance-activities.xml:18(title) +msgid "Backup and Disaster Recovery" +msgstr "" + +#: ./doc/security-guide/ch063_compliance-activities.xml:19(para) +msgid "Disaster Recovery (DR) and Business Continuity Planning (BCP) plans are common requirements for ISMS and compliance activities. These plans must be periodically tested as well as documented. In OpenStack key areas are found in the management security domain, and anywhere that single points of failure (SPOFs) can be identified. See the section on secure backup and recovery for additional details." +msgstr "" + +#: ./doc/security-guide/ch063_compliance-activities.xml:22(title) +msgid "Security Training" +msgstr "" + +#: ./doc/security-guide/ch063_compliance-activities.xml:23(para) +msgid "Annual, role-specific, security training is a mandatory requirement for almost all compliance certifications and attestations. To optimise the effectiveness of security training, a common method is to provide role specific training, for example to developers, operational personnel, and non-technical employees. Additional cloud security or OpenStack security training based on this hardening guide would be ideal." +msgstr "" + +#: ./doc/security-guide/ch063_compliance-activities.xml:26(title) +msgid "Security Reviews" +msgstr "" + +#: ./doc/security-guide/ch063_compliance-activities.xml:27(para) +msgid "As OpenStack is a popular open source project, much of the codebase and architecture has been scrutinized by individual contributors, organizations and enterprises. This can be advantageous from a security perspective, however the need for security reviews is still a critical consideration for service providers, as deployments vary, and security is not always the primary concern for contributors. A comprehensive security review process may include architectural review, threat modelling, source code analysis and penetration testing. There are many techniques and recommendations for conducting security reviews that can be found publicly posted. A well-tested example is the Microsoft SDL, created as part of the Microsoft Trustworthy Computing Initiative." +msgstr "" + +#: ./doc/security-guide/ch063_compliance-activities.xml:44(para) +msgid "Security updates are critical to any IaaS deployment, whether private or public. Vulnerable systems expand attack surfaces, and are obvious targets for attackers. Common scanning technologies and vulnerability notification services can help mitigate this threat. It is important that scans are authenticated and that mitigation strategies extend beyond simple perimeter hardening. Multi-tenant architectures such as OpenStack are particularly prone to hypervisor vulnerabilities, making this a critical part of the system for vulnerability management. See the section on instance isolation for additional details." +msgstr "" + +#: ./doc/security-guide/ch063_compliance-activities.xml:47(title) +msgid "Data Classification" +msgstr "" + +#: ./doc/security-guide/ch063_compliance-activities.xml:48(para) +msgid "Data Classification defines a method for classifying and handling information, often to protect customer information from accidental or deliberate theft, loss, or inappropriate disclosure. Most commonly this involves classifying information as sensitive or non-sensitive, or as personally identifiable information (PII). Depending on the context of the deployment various other classifying criteria may be used (government, health-care etc). The underlying principle is that data classifications are clearly defined and in-use. The most common protective mechanisms include industry standard encryption technologies. See the data security section for additional details." +msgstr "" + +#: ./doc/security-guide/ch063_compliance-activities.xml:51(title) +msgid "Exception Process" +msgstr "" + +#: ./doc/security-guide/ch063_compliance-activities.xml:52(para) +msgid "An exception process is an important component of an ISMS. When certain actions are not compliant with security policies that an organization has defined, they must be logged. Appropriate justification, description and mitigation details need to be included, and signed off by appropriate authorities. OpenStack default configurations may vary in meeting various compliance criteria, areas that fail to meet compliance requirements should be logged, with potential fixes considered for contribution to the community." +msgstr "" + +#. When image changes, this message will be marked fuzzy or untranslated for you. +#. It doesn't matter what you translate it to: it's not used at all. +#: ./doc/security-guide/ch027_storage.xml:53(None) +msgid "@@image: 'static/swift_network_diagram-1.png'; md5=83c094bb051cbe5e6161d3f7442f6136" +msgstr "" + +#. When image changes, this message will be marked fuzzy or untranslated for you. +#. It doesn't matter what you translate it to: it's not used at all. +#: ./doc/security-guide/ch027_storage.xml:108(None) ./doc/security-guide/ch027_storage.xml:113(None) +msgid "@@image: 'static/swift_network_diagram-2.png'; md5=69f8effe3f5d0f3cbccfb8c5a5dd299e" +msgstr "" + +#: ./doc/security-guide/ch027_storage.xml:9(para) +msgid "OpenStack Object Storage (Swift) is a service that provides storage and retrieval of data over HTTP. Objects (blobs of data) are stored in an organizational hierarchy that offers anonymous read-only access or ACL defined access based on the authentication mechanism." +msgstr "" + +#: ./doc/security-guide/ch027_storage.xml:14(para) +msgid "A consumer can store objects, modify them, or access them using the HTTP protocol and REST APIs. Backend components of Object Storage use different protocols for keeping the information synchronized in a redundant cluster of services. For more details on the API and the backend components see the OpenStack Storage documentation." +msgstr "" + +#: ./doc/security-guide/ch027_storage.xml:22(para) +msgid "For this document the components will be grouped into the following primary groups:" +msgstr "" + +#: ./doc/security-guide/ch027_storage.xml:26(para) +msgid "Proxy services" +msgstr "" + +#: ./doc/security-guide/ch027_storage.xml:29(para) +msgid "Auth services" +msgstr "" + +#: ./doc/security-guide/ch027_storage.xml:32(para) +msgid "Storage services" +msgstr "" + +#: ./doc/security-guide/ch027_storage.xml:35(para) ./doc/security-guide/ch027_storage.xml:159(td) +msgid "Account service" +msgstr "" + +#: ./doc/security-guide/ch027_storage.xml:38(para) ./doc/security-guide/ch027_storage.xml:164(td) +msgid "Container service" +msgstr "" + +#: ./doc/security-guide/ch027_storage.xml:41(para) ./doc/security-guide/ch027_storage.xml:169(td) +msgid "Object service" +msgstr "" + +#: ./doc/security-guide/ch027_storage.xml:47(title) +msgid "An example diagram from the OpenStack Object Storage Administration Guide (2013)" +msgstr "" + +#: ./doc/security-guide/ch027_storage.xml:58(para) +msgid "An Object Storage environment does not have to necessarily be on the Internet and could also be a private cloud with the \"Public Switch\" being part of the organization's internal network infrastructure." +msgstr "" + +#: ./doc/security-guide/ch027_storage.xml:64(title) +msgid "First thing to secure – the network" +msgstr "" + +#: ./doc/security-guide/ch027_storage.xml:65(para) +msgid "The first aspect of a secure architecture design for Object Storage is in the networking component. The Storage service nodes use rsync between each other for copying data to provide replication and high availability. In addition, the proxy service communicates with the Storage service when relaying data back and forth between the end-point client and the cloud environment." +msgstr "" + +#: ./doc/security-guide/ch027_storage.xml:73(para) +msgid "None of these use any type of encryption or authentication at this layer/tier." +msgstr "" + +#: ./doc/security-guide/ch027_storage.xml:76(para) +msgid "This is why you see a \"Private Switch\" or private network ([V]LAN) in architecture diagrams. This data domain should be separate from other OpenStack data networks as well. For further discussion on security domains please see ." +msgstr "" + +#: ./doc/security-guide/ch027_storage.xml:83(para) +msgid "Rule: Use a private (V)LAN network segment for your Storage services in the data domain." +msgstr "" + +#: ./doc/security-guide/ch027_storage.xml:87(para) +msgid "This necessitates that the Proxy service nodes have dual interfaces (physical or virtual):" +msgstr "" + +#: ./doc/security-guide/ch027_storage.xml:91(para) +msgid "One as a \"public\" interface for consumers to reach" +msgstr "" + +#: ./doc/security-guide/ch027_storage.xml:95(para) +msgid "Another as a \"private\" interface with access to the storage nodes" +msgstr "" + +#: ./doc/security-guide/ch027_storage.xml:99(para) +msgid "The following figure demonstrates one possible network architecture." +msgstr "" + +#: ./doc/security-guide/ch027_storage.xml:102(title) +msgid "Object storage network architecture with a management node (OSAM)" +msgstr "" + +#: ./doc/security-guide/ch027_storage.xml:120(title) +msgid "Securing services – general" +msgstr "" + +#: ./doc/security-guide/ch027_storage.xml:122(title) +msgid "Service runas user" +msgstr "" + +#: ./doc/security-guide/ch027_storage.xml:123(para) +msgid "It is recommended that you configure each service to run under a non-root (UID 0) service account. One recommendation is the username \"swift\" with primary group \"swift.\"" +msgstr "" + +#: ./doc/security-guide/ch027_storage.xml:129(title) +msgid "File permissions" +msgstr "" + +#: ./doc/security-guide/ch027_storage.xml:130(para) +msgid "/etc/swift contains information about the ring topology and environment configuration. The following permissions are recommended:" +msgstr "" + +#: ./doc/security-guide/ch027_storage.xml:138(para) +msgid "This restricts only root to be able to modify configuration files while allowing the services to read them via their group membership in \"swift.\"" +msgstr "" + +#: ./doc/security-guide/ch027_storage.xml:146(title) +msgid "Securing storage services" +msgstr "" + +#: ./doc/security-guide/ch027_storage.xml:147(para) +msgid "The following are the default listening ports for the various storage services:" +msgstr "" + +#: ./doc/security-guide/ch027_storage.xml:152(td) +msgid "Service Name" +msgstr "" + +#: ./doc/security-guide/ch027_storage.xml:153(td) +msgid "Port" +msgstr "" + +#: ./doc/security-guide/ch027_storage.xml:154(td) +msgid "Type" +msgstr "" + +#: ./doc/security-guide/ch027_storage.xml:160(td) +msgid "6002" +msgstr "" + +#: ./doc/security-guide/ch027_storage.xml:161(td) ./doc/security-guide/ch027_storage.xml:166(td) ./doc/security-guide/ch027_storage.xml:171(td) ./doc/security-guide/ch027_storage.xml:176(td) +msgid "TCP" +msgstr "" + +#: ./doc/security-guide/ch027_storage.xml:165(td) +msgid "6001" +msgstr "" + +#: ./doc/security-guide/ch027_storage.xml:170(td) +msgid "6000" +msgstr "" + +#: ./doc/security-guide/ch027_storage.xml:174(td) +msgid "Rsync" +msgstr "" + +#: ./doc/security-guide/ch027_storage.xml:175(td) +msgid "873" +msgstr "" + +#: ./doc/security-guide/ch027_storage.xml:180(para) +msgid "Authentication does not happen at this level in Object Storage. If someone was able to connect to a Storage service node on one of these ports they could access or modify data without authentication. In order to secure against this issue you should follow the recommendations given previously about using a private storage network." +msgstr "" + +#: ./doc/security-guide/ch027_storage.xml:188(title) +msgid "Object storage \"account\" terminology" +msgstr "" + +#: ./doc/security-guide/ch027_storage.xml:189(para) +msgid "An Object Storage \"Account\" is not a user account or credential. The following explains the relations:" +msgstr "" + +#: ./doc/security-guide/ch027_storage.xml:195(td) +msgid "OpenStack Object Storage Account" +msgstr "" + +#: ./doc/security-guide/ch027_storage.xml:196(td) +msgid "Collection of containers; not user accounts or authentication. Which users are associated with the account and how they may access it depends on the authentication system used. See authentication systems later. Referred to in this document as OSSAccount." +msgstr "" + +#: ./doc/security-guide/ch027_storage.xml:205(td) +msgid "OpenStack Object Storage Containers" +msgstr "" + +#: ./doc/security-guide/ch027_storage.xml:206(td) +msgid "Collection of objects. Metadata on the container is available for ACLs. The meaning of ACLs is dependent on the authentication system used." +msgstr "" + +#: ./doc/security-guide/ch027_storage.xml:212(td) +msgid "OpenStack Object Storage Objects" +msgstr "" + +#: ./doc/security-guide/ch027_storage.xml:213(td) +msgid "The actual data objects. ACLs at the object level are also possible with metadata. It is dependent on the authentication system used." +msgstr "" + +#: ./doc/security-guide/ch027_storage.xml:221(para) +msgid " Another way of thinking about the above would be: A single shelf (Account) holds zero or more -> buckets (Containers) which each hold zero or more -> objects. A garage (Object Storage cloud environment) may have multiple shelves (Accounts) with each shelf belonging to zero or more users." +msgstr "" + +#: ./doc/security-guide/ch027_storage.xml:231(para) +msgid "At each level you may have ACLs that dictate who has what type of access. ACLs are interpreted based on what authentication system is in use. The two most common types of authentication providers used are Keystone and SWAuth. Custom authentication providers are also possible. Please see the Object Storage Authentication section for more information." +msgstr "" + +#: ./doc/security-guide/ch027_storage.xml:242(title) +msgid "Securing proxy services" +msgstr "" + +#: ./doc/security-guide/ch027_storage.xml:243(para) +msgid "A Proxy service node should have at least two interfaces (physical or virtual): one public and one private. The public interface may be protected via firewalls or service binding. The public facing service is an HTTP web server that processes end-point client requests, authenticates them, and performs the appropriate action. The private interface does not require any listening services but is instead used to establish outgoing connections to storage service nodes on the private storage network." +msgstr "" + +#: ./doc/security-guide/ch027_storage.xml:253(title) +msgid "Use SSL/TLS" +msgstr "" + +#: ./doc/security-guide/ch027_storage.xml:254(para) +msgid "The built-in or included web server that comes with Swift supports SSL, but it does not support transmission of the entire SSL certificate chain. This causes issues when you use a third party trusted and signed certificate, such as Verisign, for your cloud. The current work around is to not use the built-in web server but an alternative web server instead that supports sending both the public server certificate as well as the CA signing authorities intermediate certificate(s). This allows for end-point clients that have the CA root certificate in their trust store to be able to successfully validate your cloud environment's SSL certificate and chain. An example of how to do this with mod_wsgi and Apache is given below. Also consult the Apache Deployment Guide" +msgstr "" + +#: ./doc/security-guide/ch027_storage.xml:272(para) +msgid "Modify file /etc/apache2/envvars with" +msgstr "" + +#: ./doc/security-guide/ch027_storage.xml:279(para) +msgid "An alternative is to modify your Apache conf file with" +msgstr "" + +#: ./doc/security-guide/ch027_storage.xml:285(para) +msgid "Create a \"swift\" directory in your Apache document root:" +msgstr "" + +#: ./doc/security-guide/ch027_storage.xml:288(para) +msgid "Create the file $YOUR_APACHE_DOC_ROOT/swift/proxy-server.wsgi:" +msgstr "" + +#: ./doc/security-guide/ch027_storage.xml:294(title) +msgid "HTTP listening port" +msgstr "" + +#: ./doc/security-guide/ch027_storage.xml:295(para) +msgid "You should run your Proxy service web server as a non-root (no UID 0) user such as \"swift\" mentioned before. The use of a port greater than 1024 is required to make this easy and avoid running any part of the web container as root. Doing so is not a burden as end-point clients are not typically going to type in the URL manually into a web browser to browse around in the object storage. Additionally, for clients using the HTTP REST API and performing authentication they will normally automatically grab the full REST API URL they are to use as provided by the authentication response. OpenStack’s REST API allows for a client to authenticate to one URL and then be told to use a completely different URL for the actual service. Example: Client authenticates to https://identity.cloud.example.org:55443/v1/auth and gets a response with their authentication key and Storage URL (the URL of the proxy nodes or load balancer) of https://swift.cloud.example.org:44443/v1/AUTH_8980." +msgstr "" + +#: ./doc/security-guide/ch027_storage.xml:315(para) +msgid "The method for configuring your web server to start and run as a non-root user varies by web server and OS." +msgstr "" + +#: ./doc/security-guide/ch027_storage.xml:320(title) +msgid "Load balancer" +msgstr "" + +#: ./doc/security-guide/ch027_storage.xml:321(para) +msgid "If the option of using Apache is not feasible or for performance you wish to offload your SSL work you may employ a dedicated network device load balancer. This is also the common way to provide redundancy and load balancing when using multiple proxy nodes." +msgstr "" + +#: ./doc/security-guide/ch027_storage.xml:326(para) +msgid "If you choose to offload your SSL ensure that the network link between the load balancer and your proxy nodes is on a private (V)LAN segment such that other nodes on the network (possibly compromised) cannot wiretap (sniff) the unencrypted traffic. If such a breach were to occur the attacker could gain access to end-point client or cloud administrator credentials and access the cloud data." +msgstr "" + +#: ./doc/security-guide/ch027_storage.xml:334(para) +msgid "The authentication service you use, such as Keystone or SWAuth, will determine how you configure a different URL in the responses to end-clients so they use your load balancer instead of an individual Proxy service node." +msgstr "" + +#: ./doc/security-guide/ch027_storage.xml:343(title) +msgid "Object storage authentication" +msgstr "" + +#: ./doc/security-guide/ch027_storage.xml:344(para) +msgid "Object Storage uses wsgi to provide a middleware for authentication of end-point clients. The authentication provider defines what roles and user types exist. Some use traditional username and password credentials while others may leverage API key tokens or even client-side x.509 SSL certificates. Custom providers can be integrated in using the wsgi model." +msgstr "" + +#: ./doc/security-guide/ch027_storage.xml:352(title) +msgid "Keystone" +msgstr "" + +#: ./doc/security-guide/ch027_storage.xml:353(para) +msgid "Keystone is the commonly used Identity provider in OpenStack. It may also be used for authentication in Object Storage. Coverage of securing Keystone is already provided in ." +msgstr "" + +#: ./doc/security-guide/ch027_storage.xml:360(title) +msgid "SWAuth" +msgstr "" + +#: ./doc/security-guide/ch027_storage.xml:361(para) +msgid "SWAuth is another alternative to Keystone. In contrast to Keystone it stores the user accounts, credentials, and metadata in object storage itself. More information can be found on the SWAuth website at http://gholt.github.io/swauth/." +msgstr "" + +#: ./doc/security-guide/ch027_storage.xml:371(title) +msgid "Other notable items" +msgstr "" + +#: ./doc/security-guide/ch027_storage.xml:372(para) +msgid "In /etc/swift/swift.conf on every service node there is a \"swift_hash_path_suffix\" setting. This is provided to reduce the chance of hash collisions for objects being stored and avert one user overwriting the data of another user." +msgstr "" + +#: ./doc/security-guide/ch027_storage.xml:377(para) +msgid "This value should be initially set with a cryptographically secure random number generator and consistent across all service nodes. Ensure that it is protected with proper ACLs and that you have a backup copy to avoid data loss." +msgstr "" + +#: ./doc/security-guide/ch006_introduction-to-case-studies.xml:8(title) +msgid "Introduction to Case Studies" +msgstr "" + +#: ./doc/security-guide/ch006_introduction-to-case-studies.xml:9(para) +msgid "This guide refers to two running case studies, which are introduced here and referred to at the end of each chapter." +msgstr "" + +#: ./doc/security-guide/ch006_introduction-to-case-studies.xml:12(title) +msgid "Case Study : Alice the private cloud builder" +msgstr "" + +#: ./doc/security-guide/ch006_introduction-to-case-studies.xml:13(para) +msgid "Alice deploys a private cloud for use by a government department in the US. The cloud must comply with relevant standards, such as FedRAMP. The security paperwork requirements for this cloud are very high. It must have no direct access to the internet: its API endpoints, compute instances, and other resources must be exposed to only systems within the department's network, which is entirely air-gapped from all other networks. The cloud can access other network services on the Organization's Intranet. For example, the authentication and logging services." +msgstr "" + +#: ./doc/security-guide/ch006_introduction-to-case-studies.xml:25(title) +msgid "Case Study : Bob the public cloud provider" +msgstr "" + +#: ./doc/security-guide/ch006_introduction-to-case-studies.xml:26(para) +msgid "Bob is a lead architect for a company that deploys a large greenfield public cloud. This cloud provides IaaS for the masses and enables any consumer with a valid credit card access to utility computing and storage, but the primary focus is enterprise customers. Data privacy concerns are a big priority for Bob as they are seen as a major barrier to large-scale adoption of the cloud by organizations." +msgstr "" + +#: ./doc/security-guide/ch030_state-of-networking.xml:3(title) +msgid "State of Networking" +msgstr "" + +#: ./doc/security-guide/ch030_state-of-networking.xml:4(para) +msgid "OpenStack Networking in the Grizzly release enables the end-user or tenant to define, utilize, and consume networking resources in new ways that had not been possible in previous OpenStack Networking releases. OpenStack Networking provides a tenant-facing API for defining network connectivity and IP addressing for instances in the cloud in addition to orchestrating the network configuration. With the transition to an API-centric networking service, cloud architects and administrators should take into consideration best practices to secure physical and virtual network infrastructure and services." +msgstr "" + +#: ./doc/security-guide/ch030_state-of-networking.xml:5(para) +msgid "OpenStack Networking was designed with a plug-in architecture that provides extensibility of the API via open source community or third-party services. As you evaluate your architectural design requirements, it is important to determine what features are available in OpenStack Networking core services, any additional services that are provided by third-party products, and what supplemental services are required to be implemented in the physical infrastructure." +msgstr "" + +#: ./doc/security-guide/ch030_state-of-networking.xml:6(para) +msgid "This section is a high-level overview of what processes and best practices should be considered when implementing OpenStack Networking. We will talk about the current state of services that are available, what future services will be implemented, and the current limitations in this project." +msgstr "" + +#: ./doc/security-guide/ch043_database-transport-security.xml:3(title) +msgid "Database Transport Security" +msgstr "" + +#: ./doc/security-guide/ch043_database-transport-security.xml:4(para) +msgid "This chapter covers issues related to network communications to and from the database server. This includes IP address bindings and encrypting network traffic with SSL." +msgstr "" + +#: ./doc/security-guide/ch043_database-transport-security.xml:6(title) +msgid "Database Server IP Address Binding" +msgstr "" + +#: ./doc/security-guide/ch043_database-transport-security.xml:7(para) +msgid "To isolate sensitive database communications between the services and the database, we strongly recommend that the database server(s) be configured to only allow communications to and from the database over an isolated management network. This is achieved by restricting the interface or IP address on which the database server binds a network socket for incoming client connections." +msgstr "" + +#: ./doc/security-guide/ch043_database-transport-security.xml:9(title) +msgid "Restricting Bind Address for MySQL" +msgstr "" + +#: ./doc/security-guide/ch043_database-transport-security.xml:10(para) ./doc/security-guide/ch043_database-transport-security.xml:33(para) +msgid "In my.cnf:" +msgstr "" + +#: ./doc/security-guide/ch043_database-transport-security.xml:17(title) +msgid "Restricting Listen Address for PostgreSQL" +msgstr "" + +#: ./doc/security-guide/ch043_database-transport-security.xml:18(para) +msgid "In postgresql.conf:" +msgstr "" + +#: ./doc/security-guide/ch043_database-transport-security.xml:24(title) +msgid "Database Transport" +msgstr "" + +#: ./doc/security-guide/ch043_database-transport-security.xml:25(para) +msgid "In addition to restricting database communications to the management network, we also strongly recommend that the cloud administrator configure their database backend to require SSL. Using SSL for the database client connections  protects the communications from tampering and eavesdropping. As will be discussed in the next section, using SSL also provides the framework for doing database user authentication via X.509 certificates (commonly referred to as PKI). Below is guidance on how SSL is typically configured for the two popular database backends MySQL and PostgreSQL." +msgstr "" + +#: ./doc/security-guide/ch043_database-transport-security.xml:27(para) +msgid "NOTE: When installing the certificate and key files, ensure that the file permissions are restricted, for example chmod 0600, and the ownership is restricted to the database daemon user to prevent unauthorized access by other processes and users on the database server." +msgstr "" + +#: ./doc/security-guide/ch043_database-transport-security.xml:31(title) +msgid "MySQL SSL Configuration" +msgstr "" + +#: ./doc/security-guide/ch043_database-transport-security.xml:32(para) +msgid "The following lines should be added in the system-wide MySQL configuration file:" +msgstr "" + +#: ./doc/security-guide/ch043_database-transport-security.xml:40(para) ./doc/security-guide/ch043_database-transport-security.xml:50(para) +msgid "Optionally, if you wish to restrict the set of SSL ciphers used for the encrypted connection. See http://www.openssl.org/docs/apps/ciphers.html for a list of ciphers and the syntax for specifying the cipher string:" +msgstr "" + +#: ./doc/security-guide/ch043_database-transport-security.xml:46(title) +msgid "PostgreSQL SSL Configuration" +msgstr "" + +#: ./doc/security-guide/ch043_database-transport-security.xml:47(para) +msgid "The following lines should be added in the system-wide PostgreSQL configuration file, postgresql.conf." +msgstr "" + +#: ./doc/security-guide/ch043_database-transport-security.xml:53(para) +msgid "The server certificate, key, and certificate authority (CA) files should be placed in the $PGDATA directory in the following files:" +msgstr "" + +#: ./doc/security-guide/ch043_database-transport-security.xml:55(para) +msgid "$PGDATA/server.crt - Server certificate" +msgstr "" + +#: ./doc/security-guide/ch043_database-transport-security.xml:58(para) +msgid "$PGDATA/server.key - Private key corresponding to server.crt" +msgstr "" + +#: ./doc/security-guide/ch043_database-transport-security.xml:61(para) +msgid "$PGDATA/root.crt - Trusted certificate authorities" +msgstr "" + +#: ./doc/security-guide/ch043_database-transport-security.xml:64(para) +msgid "$PGDATA/root.crl - Certificate revocation list" +msgstr "" + +#: ./doc/security-guide/ch048_key-management.xml:3(title) +msgid "Key Management" +msgstr "" + +#: ./doc/security-guide/ch048_key-management.xml:4(para) +msgid "To address the often mentioned concern of tenant data privacy and limiting cloud provider liability, there is greater interest within the OpenStack community to make data encryption more ubiquitous. It is relatively easy for an end-user to encrypt their data prior to saving it to the cloud, and this is a viable path for tenant objects such as media files, database archives among others. However, when client side encryption is used for virtual machine images, block storage etc, client intervention is necessary in the form of presenting keys to unlock the data for further use. To seamlessly secure the data and yet have it accessible without burdening the client with having to manage their keys and interactively provide them calls for a key management service within OpenStack. Providing encryption and key management services as part of OpenStack eases data-at-rest security adoption, addresses customer concerns about the privacy and misuse of their data with the added advantage of limiting cloud provider liability. Provider liability is of concern in multi-tenant public clouds with respect to handing over tenant data during a misuse investigation." +msgstr "" + +#: ./doc/security-guide/ch048_key-management.xml:5(para) +msgid "A key management service is in the early stages of being developed and has a way to go before becoming an official component of OpenStack. Refer to https://github.com/cloudkeep/barbican/wiki/_pages for details." +msgstr "" + +#: ./doc/security-guide/ch048_key-management.xml:6(para) +msgid "It shall support the creation of keys, and their secure saving (with a service master-key). Some of the design questions still being debated are how much of the Key Management Interchange Protocol (KMIP) to support, key formats, and certificate management.  The key manager will be pluggable to facilitate deployments that need a third-party Hardware Security Module (HSM)." +msgstr "" + +#: ./doc/security-guide/ch048_key-management.xml:7(para) +msgid "OpenStack Block Storage, Cinder, is the first service looking to integrate with the key manager to provide volume encryption." +msgstr "" + +#: ./doc/security-guide/ch048_key-management.xml:9(title) +msgid "References:" +msgstr "" + +#: ./doc/security-guide/ch048_key-management.xml:11(link) +msgid "Barbican" +msgstr "" + +#: ./doc/security-guide/ch048_key-management.xml:14(link) +msgid "KMIP" +msgstr "" + +#: ./doc/security-guide/ch009_case-studies.xml:3(title) +msgid "Case Studies: System Documentation" +msgstr "" + +#: ./doc/security-guide/ch009_case-studies.xml:4(para) +msgid "In this case study we discuss how Alice and Bob would address their system documentation requirements. The documentation suggested above includes hardware and software records, network diagrams, and system configuration details." +msgstr "" + +#: ./doc/security-guide/ch009_case-studies.xml:7(para) +msgid "Alice needs detailed documentation to satisfy FedRamp requirements.  She sets up a configuration management database (CMDB) to store information regarding all of the hardware, firmware, and software versions used throughout the cloud. She also creates a network diagram detailing the cloud architecture, paying careful attention to the security domains and the services that span multiple security domains." +msgstr "" + +#: ./doc/security-guide/ch009_case-studies.xml:8(para) +msgid "Alice also needs to record each network service running in the cloud, what interfaces and ports it binds to, the security domains for each service, and why the service is needed. Alice decides to build automated tools to log into each system in the cloud over secure shell (SSH) using the Python Fabric library. The tools collect and store the information in the CMDB, which simplifies the audit process." +msgstr "" + +#: ./doc/security-guide/ch009_case-studies.xml:12(para) +msgid "In this case, Bob will approach these steps the same as Alice." +msgstr "" + +#: ./doc/security-guide/ch056_case-studies-instance-management.xml:3(title) +msgid "Case Studies: Instance Management" +msgstr "" + +#: ./doc/security-guide/ch056_case-studies-instance-management.xml:4(para) +msgid "In this case study we discuss how Alice and Bob would architect their clouds with respect to instance entropy, scheduling instances, trusted images, and instance migrations." +msgstr "" + +#: ./doc/security-guide/ch056_case-studies-instance-management.xml:7(para) +msgid "Alice has a need for lots of high quality entropy in the instances. For this reason, she decides to purchase hardware with Intel Ivy Bridge chip sets that support the RdRand instruction on each compute node. Using the entropy gathering daemon (EGD) and LibVirt's EGD support, Alice ensures that this entropy pool is distributed to the instances on each compute node." +msgstr "" + +#: ./doc/security-guide/ch056_case-studies-instance-management.xml:8(para) +msgid "For instance scheduling, Alice uses the trusted compute pools to ensure that all cloud workloads are deployed to nodes that presented a proper boot time attestation. Alice decides to disable user permissions for image uploading to help ensure that the images used in the cloud are generated in a known and trusted manner by the cloud administrators." +msgstr "" + +#: ./doc/security-guide/ch056_case-studies-instance-management.xml:9(para) +msgid "Finally, Alice disables instance migrations as this feature is less critical for the high performance application workloads expected to run in this cloud. This helps avoid the various security concerns related to instance migrations." +msgstr "" + +#: ./doc/security-guide/ch056_case-studies-instance-management.xml:13(para) +msgid "Bob is aware that entropy will be a concern for some of his customers, such as those in the financial industry. However, due to the added cost and complexity, Bob has decided to forgo integrating hardware entropy into the first iteration of his cloud. He adds hardware entropy as a fast-follow to do for a later improvement for the second generation of his cloud architecture." +msgstr "" + +#: ./doc/security-guide/ch056_case-studies-instance-management.xml:14(para) +msgid "Bob is interested in ensuring that customers receive a high quality of service. He is concerned that providing too much explicit user control over instance scheduling could negatively impact the quality of service. So he disables this feature. Bob provides images in the cloud from a known trusted source for users to use. Additionally, he also allows users to upload their own images. However, users cannot generally share their images. This helps prevent a user from sharing a malicious image, which could negatively impact the security of other users in the cloud." +msgstr "" + +#: ./doc/security-guide/ch056_case-studies-instance-management.xml:15(para) +msgid "For migrations, Bob wants to enable secure instance migrations in order to support rolling upgrades with minimal user downtime. Bob ensures that all migrations occur on an isolated VLAN. He plans to defer implementing encrypted migrations until this is better supported in Nova client tools. However, he makes a note to track this carefully and switch to encrypted migrations as soon as possible." +msgstr "" + +#: ./doc/security-guide/ch_preface.xml:10(title) +msgid "Preface" +msgstr "" + +#. When image changes, this message will be marked fuzzy or untranslated for you. +#. It doesn't matter what you translate it to: it's not used at all. +#: ./doc/security-guide/ch008_system-roles-types.xml:101(None) ./doc/security-guide/ch008_system-roles-types.xml:106(None) +msgid "@@image: 'static/services-protocols-ports.png'; md5=fb1e9f47d969127b7a5ca683d38cfe20" +msgstr "" + +#: ./doc/security-guide/ch008_system-roles-types.xml:8(title) +msgid "System Documentation Requirements" +msgstr "" + +#: ./doc/security-guide/ch008_system-roles-types.xml:9(para) +msgid "The system documentation for an OpenStack cloud deployment should follow the templates and best practices for the Enterprise Information Technology System in your organization. Organizations often have compliance requirements which may require an overall System Security Plan to inventory and document the architecture of a given system. There are common challenges across the industry related to documenting the dynamic cloud infrastructure and keeping the information up-to-date." +msgstr "" + +#: ./doc/security-guide/ch008_system-roles-types.xml:18(title) +msgid "System Roles & Types" +msgstr "" + +#: ./doc/security-guide/ch008_system-roles-types.xml:19(para) +msgid "The two broadly defined types of nodes that generally make up an OpenStack installation are:" +msgstr "" + +#: ./doc/security-guide/ch008_system-roles-types.xml:23(para) +msgid "Infrastructure nodes. The nodes that run the cloud related services such as the OpenStack Identity Service, the message queuing service, storage, networking, and other services required to support the operation of the cloud." +msgstr "" + +#: ./doc/security-guide/ch008_system-roles-types.xml:30(para) +msgid "Compute, storage, or other resource nodes. Provide storage capacity or virtual machines for your cloud." +msgstr "" + +#: ./doc/security-guide/ch008_system-roles-types.xml:37(title) +msgid "System Inventory" +msgstr "" + +#: ./doc/security-guide/ch008_system-roles-types.xml:38(para) +msgid "Documentation should provide a general description of the OpenStack environment and cover all systems used (production, development, test, etc.). Documenting system components, networks, services, and software often provides the bird's-eye view needed to thoroughly cover and consider security concerns, attack vectors and possible security domain bridging points. A system inventory may need to capture ephemeral resources such as virtual machines or virtual disk volumes that would otherwise be persistent resources in a traditional IT system." +msgstr "" + +#: ./doc/security-guide/ch008_system-roles-types.xml:48(title) +msgid "Hardware Inventory" +msgstr "" + +#: ./doc/security-guide/ch008_system-roles-types.xml:49(para) +msgid "Clouds without stringent compliance requirements for written documentation might benefit from having a Configuration Management Database (CMDB). CMDBs are normally used for hardware asset tracking and overall life-cycle management. By leveraging a CMDB, an organization can quickly identify cloud infrastructure hardware. For example, compute nodes, storage nodes, and network devices that exist on the network but that might not be adequately protected and/or forgotten. OpenStack provisioning system might provide some CMDB-like functions especially if auto-discovery features of hardware attributes are available." +msgstr "" + +#: ./doc/security-guide/ch008_system-roles-types.xml:63(title) +msgid "Software Inventory" +msgstr "" + +#: ./doc/security-guide/ch008_system-roles-types.xml:64(para) +msgid "Just as with hardware, all software components within the OpenStack deployment should be documented. Components here should include system databases; OpenStack software components and supporting sub-components; and, supporting infrastructure software such as load-balancers, reverse proxies, and network address translators. Having an authoritative list like this may be critical toward understanding total system impact due to a compromise or vulnerability of a specific class of software." +msgstr "" + +#: ./doc/security-guide/ch008_system-roles-types.xml:76(title) +msgid "Network Topology" +msgstr "" + +#: ./doc/security-guide/ch008_system-roles-types.xml:77(para) +msgid "A Network Topology should be provided with highlights specifically calling out the data flows and bridging points between the security domains. Network ingress and egress points should be identified along with any OpenStack logical system boundaries. Multiple diagrams may be needed to provide complete visual coverage of the system.  A network topology document should include virtual networks created on behalf of tenants by the system along with virtual machine instances and gateways created by OpenStack." +msgstr "" + +#: ./doc/security-guide/ch008_system-roles-types.xml:88(title) +msgid "Services, Protocols and Ports" +msgstr "" + +#: ./doc/security-guide/ch008_system-roles-types.xml:89(para) +msgid "The Service, Protocols and Ports table provides important additional detail of an OpenStack deployment. A table view of all services running within the cloud infrastructure can immediately inform, guide, and help check security procedures. Firewall configuration, service port conflicts, security remediation areas, and compliance requirements become easier to manage when you have concise information available. Consider the following table:" +msgstr "" + +#: ./doc/security-guide/ch008_system-roles-types.xml:109(para) +msgid "Referencing a table of services, protocols and ports can help in understanding the relationship between OpenStack components. It is highly recommended that OpenStack deployments have information similar to this on record." +msgstr "" + +#: ./doc/security-guide/ch025_web-dashboard.xml:9(para) +msgid "Horizon is the OpenStack dashboard that provides users a self-service portal to provision their own resources within the limits set by administrators. These include provisioning users, defining instance flavors, uploading VM images, managing networks, setting up security groups, starting instances, and accessing the instances via a console." +msgstr "" + +#: ./doc/security-guide/ch025_web-dashboard.xml:14(para) +msgid "The dashboard is based on the Django web framework, therefore secure deployment practices for Django apply directly to Horizon. This guide provides a popular set of Django security recommendations, further information can be found by reading the Django deployment and security documentation." +msgstr "" + +#: ./doc/security-guide/ch025_web-dashboard.xml:21(para) +msgid "The dashboard ships with reasonable default security settings, and has good deployment and configuration documentation." +msgstr "" + +#: ./doc/security-guide/ch025_web-dashboard.xml:26(title) +msgid "Basic Web Server Configuration" +msgstr "" + +#: ./doc/security-guide/ch025_web-dashboard.xml:27(para) +msgid "The dashboard should be deployed as a Web Services Gateway Interface (WSGI) application behind an HTTPS proxy such as Apache or nginx. If Apache is not already in use, we recommend nginx since it is lighter weight and easier to configure correctly." +msgstr "" + +#: ./doc/security-guide/ch025_web-dashboard.xml:32(para) +msgid "When using nginx, we recommend gunicorn as the wsgi host with an appropriate number of synchronous workers. We strongly advise against deployments using fastcgi, scgi, or uWSGI. We strongly advise against the use of synthetic performance benchmarks when choosing a wsgi server." +msgstr "" + +#: ./doc/security-guide/ch025_web-dashboard.xml:39(para) +msgid "When using Apache, we recommend mod_wsgi to host dashboard." +msgstr "" + +#: ./doc/security-guide/ch025_web-dashboard.xml:44(title) +msgid "HTTPS" +msgstr "" + +#: ./doc/security-guide/ch025_web-dashboard.xml:45(para) +msgid "The dashboard should be deployed behind a secure HTTPS server using a valid, trusted certificate from a recognized certificate authority (CA). Private organization-issued certificates are only appropriate when the root of trust is pre-installed in all user browsers." +msgstr "" + +#: ./doc/security-guide/ch025_web-dashboard.xml:50(para) +msgid "HTTP requests to the dashboard domain should be configured to redirect to the fully qualified HTTPS URL." +msgstr "" + +#: ./doc/security-guide/ch025_web-dashboard.xml:54(title) +msgid "HTTP Strict Transport Security (HSTS)" +msgstr "" + +#: ./doc/security-guide/ch025_web-dashboard.xml:55(para) +msgid "It is highly recommended to use HTTP Strict Transport Security (HSTS)." +msgstr "" + +#: ./doc/security-guide/ch025_web-dashboard.xml:57(para) +msgid "NOTE: If you are using an HTTPS proxy in front of your web server, rather than using an HTTP server with HTTPS functionality, follow the Django documentation on modifying the SECURE_PROXY_SSL_HEADER variable." +msgstr "" + +#: ./doc/security-guide/ch025_web-dashboard.xml:63(para) +msgid "See the chapter on PKI/SSL Everywhere for more specific recommendations and server configurations for HTTPS configurations, including the configuration of HSTS." +msgstr "" + +#: ./doc/security-guide/ch025_web-dashboard.xml:68(title) +msgid "Front end Caching" +msgstr "" + +#: ./doc/security-guide/ch025_web-dashboard.xml:69(para) +msgid "Since dashboard is rendering dynamic content passed directly from OpenStack API requests, we do not recommend front end caching layers such as varnish. In Django, static media is directly served from Apache or nginx and already benefits from web host caching." +msgstr "" + +#: ./doc/security-guide/ch025_web-dashboard.xml:76(title) +msgid "Domain Names" +msgstr "" + +#: ./doc/security-guide/ch025_web-dashboard.xml:77(para) +msgid "Many organizations typically deploy web applications at subdomains of an overarching organization domain. It is natural for users to expect a domain of the form openstack.example.org. In this context, there are often many other applications deployed in the same second-level namespace, often serving user-controlled content. This name structure is convenient and simplifies name server maintenance." +msgstr "" + +#: ./doc/security-guide/ch025_web-dashboard.xml:85(para) +msgid "We strongly recommend deploying horizon to a second-level domain, such as https://example.com, and advise against deploying horizon on a shared subdomain of any level, for example https://openstack.example.org or https://horizon.openstack.example.org. We also advise against deploying to bare internal domains like https://horizon/." +msgstr "" + +#: ./doc/security-guide/ch025_web-dashboard.xml:93(para) +msgid "This recommendation is based on the limitations browser same-origin-policy. The recommendations in this guide cannot effectively protect users against known attacks if dashboard is deployed on a domain which also hosts user-generated content, such as scripts, images, or uploads of any kind, even if the user-generated content is on a different subdomain. This approach is used by most major web presences, such as googleusercontent.com, fbcdn.com, github.io, and twimg.com, to ensure that user generated content stays separate from cookies and security tokens." +msgstr "" + +#: ./doc/security-guide/ch025_web-dashboard.xml:103(para) +msgid "Additionally, if you decline to follow this recommendation above about second-level domains, it is vital that you avoid the cookie backed session store and employ HTTP Strict Transport Security (HSTS). When deployed on a subdomain, dashboard's security is only as strong as the weakest application deployed on the same second-level domain." +msgstr "" + +#: ./doc/security-guide/ch025_web-dashboard.xml:111(title) +msgid "Static Media" +msgstr "" + +#: ./doc/security-guide/ch025_web-dashboard.xml:112(para) +msgid "Dashboard's static media should be deployed to a subdomain of the dashboard domain and served by the web server. The use of an external content delivery network (CDN) is also acceptable. This subdomain should not set cookies or serve user-provided content. The media should also be served with HTTPS." +msgstr "" + +#: ./doc/security-guide/ch025_web-dashboard.xml:117(para) +msgid "Django media settings are documented at https://docs.djangoproject.com/en/1.5/ref/settings/#static-root." +msgstr "" + +#: ./doc/security-guide/ch025_web-dashboard.xml:120(para) +msgid "Dashboard's default configuration uses django_compressor to compress and minify css and JavaScript content before serving it. This process should be statically done before deploying dashboard, rather than using the default in-request dynamic compression and copying the resulting files along with deployed code or to the CDN server. Compression should be done in a non-production build environment. If this is not practical, we recommend disabling resource compression entirely. Online compression dependencies (less, nodejs) should not be installed on production machines." +msgstr "" + +#: ./doc/security-guide/ch025_web-dashboard.xml:134(title) +msgid "Secret Key" +msgstr "" + +#: ./doc/security-guide/ch025_web-dashboard.xml:135(para) +msgid "Dashboard depends on a shared SECRET_KEY setting for some security functions. It should be a randomly generated string at least 64 characters long. It must be shared across all active Horizon instances. Compromise of this key may allow a remote attacker to execute arbitrary code. Rotating this key invalidates existing user sessions and caching. Do not commit this key to public repositories." +msgstr "" + +#: ./doc/security-guide/ch025_web-dashboard.xml:144(title) +msgid "Session Backend" +msgstr "" + +#: ./doc/security-guide/ch025_web-dashboard.xml:145(para) +msgid "Horizon's default session backend (django.contrib.sessions.backends.signed_cookies) stores user data in signed but unencrypted cookies stored in the browser. This approach allows the most simple session backend scaling since each Horizon instance is stateless, but it comes at the cost of storing sensitive access tokens in the client browser and transmitting them with every request. This backend ensures that session data has not been tampered with, but the data itself is not encrypted other than the encryption provided by HTTPS." +msgstr "" + +#: ./doc/security-guide/ch025_web-dashboard.xml:156(para) +msgid "If your architecture allows it, we recommend using django.contrib.sessions.backends.cache as your session backend with memcache as the cache. Memcache must not be exposed publicly, and should communicate over a secured private channel. If you choose to use the signed cookies backend, refer to the Django documentation understand the security trade-offs." +msgstr "" + +#: ./doc/security-guide/ch025_web-dashboard.xml:163(para) +msgid "For further details, consult the Django session backend documentation." +msgstr "" + +#: ./doc/security-guide/ch025_web-dashboard.xml:168(title) +msgid "Allowed Hosts" +msgstr "" + +#: ./doc/security-guide/ch025_web-dashboard.xml:169(para) +msgid "Configure the ALLOWED_HOSTS setting with the domain or domains where Horizon is available. Failure to configure this setting (especially if not following the recommendation above regarding second level domains) opens Horizon to a number of serious attacks. Wild card domains should be avoided." +msgstr "" + +#: ./doc/security-guide/ch025_web-dashboard.xml:174(para) +msgid "For further details, see the Django documentation on settings." +msgstr "" + +#: ./doc/security-guide/ch025_web-dashboard.xml:179(title) +msgid "Cookies" +msgstr "" + +#: ./doc/security-guide/ch025_web-dashboard.xml:180(para) +msgid "Session Cookies should be set to HTTPONLY:" +msgstr "" + +#: ./doc/security-guide/ch025_web-dashboard.xml:183(para) +msgid "Never configure CSRF or session cookies to have a wild card domain with a leading dot. Horizon's session and CSRF cookie should be secured when deployed with HTTPS:" +msgstr "" + +#: ./doc/security-guide/ch025_web-dashboard.xml:191(title) +msgid "Password Auto Complete" +msgstr "" + +#: ./doc/security-guide/ch025_web-dashboard.xml:192(para) +msgid "We recommend that implementers do not change the default password auto complete behavior. Users choose stronger passwords in environments that allow them to use the secure browser password manager. Organizations which forbid the browser password manager should enforce this policy at the desktop level." +msgstr "" + +#: ./doc/security-guide/ch025_web-dashboard.xml:200(title) +msgid "Cross Site Request Forgery (CSRF)" +msgstr "" + +#: ./doc/security-guide/ch025_web-dashboard.xml:201(para) +msgid "Django has a dedicated middleware for cross-site request forgery (CSRF)." +msgstr "" + +#: ./doc/security-guide/ch025_web-dashboard.xml:204(para) +msgid "Dashboard is designed to discourage developers from introducing cross-site scripting vulnerabilities with custom dashboards. However, it is important to audit custom dashboards, especially ones that are javascript-heavy for inappropriate use of the @csrf_exempt decorator. Dashboards which do not follow these recommended security settings should be carefully evaluated before restrictions are relaxed." +msgstr "" + +#: ./doc/security-guide/ch025_web-dashboard.xml:213(title) +msgid "Cross Site Scripting (XSS)" +msgstr "" + +#: ./doc/security-guide/ch025_web-dashboard.xml:214(para) +msgid "Unlike many similar systems, OpenStack dashboard allows the entire Unicode character set in most fields. This means developers have less latitude to make escaping mistakes that open attack vectors for cross-site scripting (XSS)." +msgstr "" + +#: ./doc/security-guide/ch025_web-dashboard.xml:218(para) +msgid "Dashboard provides tools for developers to avoid creating XSS vulnerabilities, but they only work if developers use them correctly. Audit any custom dashboards, paying particular attention to use of the mark_safe function, use of is_safe with custom template tags, the safe template tag, anywhere auto escape is turned off, and any JavaScript which might evaluate improperly escaped data." +msgstr "" + +#: ./doc/security-guide/ch025_web-dashboard.xml:227(title) +msgid "Cross Origin Resource Sharing (CORS)" +msgstr "" + +#: ./doc/security-guide/ch025_web-dashboard.xml:228(para) +msgid "Configure your web server to send a restrictive CORS header with each response, allowing only the Horizon domain and protocol:" +msgstr "" + +#: ./doc/security-guide/ch025_web-dashboard.xml:233(para) +msgid "Never allow the wild card origin." +msgstr "" + +#: ./doc/security-guide/ch025_web-dashboard.xml:236(title) +msgid "Horizon Image Upload" +msgstr "" + +#: ./doc/security-guide/ch025_web-dashboard.xml:237(para) +msgid "We recommend that implementers disable HORIZON_IMAGES_ALLOW_UPLOAD unless they have implemented a plan to prevent resource exhaustion and denial of service." +msgstr "" + +#: ./doc/security-guide/ch025_web-dashboard.xml:244(title) +msgid "Upgrading" +msgstr "" + +#: ./doc/security-guide/ch025_web-dashboard.xml:245(para) +msgid "Django security releases are generally well tested and aggressively backwards compatible. In almost all cases, new major releases of Django are also fully backwards compatible with previous releases. Dashboard implementers are strongly encouraged to run the latest stable release of Django with up-to-date security releases." +msgstr "" + +#: ./doc/security-guide/ch025_web-dashboard.xml:253(title) +msgid "Debug" +msgstr "" + +#: ./doc/security-guide/ch025_web-dashboard.xml:254(para) +msgid "Make sure DEBUG is set to False in production. In Django, DEBUG displays stack traces and sensitive web server state information on any exception." +msgstr "" + +#: ./doc/security-guide/ch022_case-studies-api-endpoints.xml:3(title) +msgid "Case Studies: API Endpoints" +msgstr "" + +#: ./doc/security-guide/ch022_case-studies-api-endpoints.xml:4(para) +msgid "In this case study we discuss how Alice and Bob would address endpoint configuration to secure their private and public clouds. Alice's cloud is not publicly accessible, but she is still concerned about securing the endpoints against improper use.  Bob's cloud, being public, must take measures to reduce the risk of attacks by external adversaries." +msgstr "" + +#: ./doc/security-guide/ch022_case-studies-api-endpoints.xml:7(para) +msgid "Alice's organization requires that the security architecture protect the access to the public and private endpoints, so she elects to use the Apache SSL proxy on both public and internal services. Alice's organization has implemented its own certificate authority. Alice contacts the PKI office in her agency that manages her PKI and certificate issuance. Alice obtains certificates issued by this CA and configures the services within both the public and management security domains to use these certificates. Since Alice's OpenStack deployment exists entirely on a disconnected from the Internet network, she makes sure to remove all default CA bundles that contain external public CA providers to ensure the OpenStack services only accept client certificates issued by her agency's CA. Alice has registered all of the services in the Keystone Services Catalog, using the internal URLs for access by internal services. She has installed host-based intrusion detection on all of the API endpoints." +msgstr "" + +#: ./doc/security-guide/ch022_case-studies-api-endpoints.xml:11(para) +msgid "Bob must also protect the access to the public and private endpoints, so he elects to use the Apache SSL proxy on both public and internal services. On the public services, he has configured the certificate key files with certificates signed by a well-known Certificate Authority. He has used his organization's self-signed CA to sign certificates in the internal services on the Management network. Bob has registered his services in the Keystone Services Catalog, using the internal URLs for access by internal services. Bob's public cloud runs services on SELinux, which he has configured with a mandatory access control policy to reduce the impact of any publicly accessible services that may be compromised. He has also configured the endpoints with a host-based IDS." +msgstr "" + +#: ./doc/security-guide/ch046_data-residency.xml:3(title) +msgid "Data Privacy Concerns" +msgstr "" + +#: ./doc/security-guide/ch046_data-residency.xml:4(para) +msgid "OpenStack is designed to support multitenancy and those tenants will most probably have different data requirements. As a cloud builder and operator you need to ensure your OpenStack environment can address various data privacy concerns and regulations. In this chapter we will address the following topics around Data Privacy as it pertains to OpenStack implementations:" +msgstr "" + +#: ./doc/security-guide/ch046_data-residency.xml:6(para) ./doc/security-guide/ch046_data-residency.xml:13(title) +msgid "Data Residency" +msgstr "" + +#: ./doc/security-guide/ch046_data-residency.xml:9(para) ./doc/security-guide/ch046_data-residency.xml:64(title) +msgid "Data Disposal" +msgstr "" + +#: ./doc/security-guide/ch046_data-residency.xml:14(para) +msgid "The privacy and isolation of data has consistently been cited as the primary barrier to cloud adoption over the past few years. Concerns over who owns data in the cloud and whether the cloud operator can be ultimately trusted as a custodian of this data have been significant issues in the past." +msgstr "" + +#: ./doc/security-guide/ch046_data-residency.xml:15(para) +msgid "Numerous OpenStack services maintain data and metadata belonging to tenants or reference tenant information." +msgstr "" + +#: ./doc/security-guide/ch046_data-residency.xml:16(para) +msgid "Tenant data stored in an OpenStack cloud may include the following items:" +msgstr "" + +#: ./doc/security-guide/ch046_data-residency.xml:18(para) +msgid "Swift objects" +msgstr "" + +#: ./doc/security-guide/ch046_data-residency.xml:21(para) +msgid "Compute instance ephemeral filesystem storage" +msgstr "" + +#: ./doc/security-guide/ch046_data-residency.xml:24(para) +msgid "Compute instance memory" +msgstr "" + +#: ./doc/security-guide/ch046_data-residency.xml:27(para) ./doc/security-guide/ch046_data-residency.xml:113(title) +msgid "Cinder volume data" +msgstr "" + +#: ./doc/security-guide/ch046_data-residency.xml:30(para) +msgid "Public keys for Compute Access" +msgstr "" + +#: ./doc/security-guide/ch046_data-residency.xml:33(para) +msgid "Virtual Machine Images in Glance" +msgstr "" + +#: ./doc/security-guide/ch046_data-residency.xml:36(para) +msgid "Machine snapshots" +msgstr "" + +#: ./doc/security-guide/ch046_data-residency.xml:39(para) +msgid "Data passed to OpenStack Compute's configuration-drive extension" +msgstr "" + +#: ./doc/security-guide/ch046_data-residency.xml:42(para) +msgid "Metadata stored by an OpenStack cloud includes the following non-exhaustive items:" +msgstr "" + +#: ./doc/security-guide/ch046_data-residency.xml:44(para) +msgid "Organization name" +msgstr "" + +#: ./doc/security-guide/ch046_data-residency.xml:47(para) +msgid "User's \"Real Name\"" +msgstr "" + +#: ./doc/security-guide/ch046_data-residency.xml:50(para) +msgid "Number or size of running instances, buckets, objects, volumes, and other quota-related items" +msgstr "" + +#: ./doc/security-guide/ch046_data-residency.xml:53(para) +msgid "Number of hours running instances or storing data" +msgstr "" + +#: ./doc/security-guide/ch046_data-residency.xml:56(para) +msgid "IP addresses of users" +msgstr "" + +#: ./doc/security-guide/ch046_data-residency.xml:59(para) +msgid "Internally generated private keys for compute image bundling" +msgstr "" + +#: ./doc/security-guide/ch046_data-residency.xml:65(para) +msgid "OpenStack operators should strive to provide a certain level of tenant data disposal assurance. Best practices suggest that the operator sanitize cloud system media (digital and non-digital) prior to disposal, release out of organization control or release for reuse. Sanitization methods should implement an appropriate level of strength and integrity given the specific security domain and sensitivity of the information." +msgstr "" + +#: ./doc/security-guide/ch046_data-residency.xml:67(para) +msgid "\"Sanitization is the process used to remove information from system media such that there is reasonable assurance that the information cannot be retrieved or reconstructed. Sanitization techniques, including clearing, purging, and destroying media information, prevent the disclosure of organizational information to unauthorized individuals when such media is reused or released for disposal.\" [NIST Special Publication 800-53 Revision 3]" +msgstr "" + +#: ./doc/security-guide/ch046_data-residency.xml:69(para) +msgid "General data disposal and sanitization guidelines as adopted from NIST recommended security controls. Cloud Operators should:" +msgstr "" + +#: ./doc/security-guide/ch046_data-residency.xml:71(para) +msgid "Track, document and verify media sanitization and disposal actions." +msgstr "" + +#: ./doc/security-guide/ch046_data-residency.xml:74(para) +msgid "Test sanitation equipment and procedures to verify proper performance." +msgstr "" + +#: ./doc/security-guide/ch046_data-residency.xml:78(para) +msgid "Sanitize portable, removable storage devices prior to connecting such devices to the cloud infrastructure." +msgstr "" + +#: ./doc/security-guide/ch046_data-residency.xml:81(para) +msgid "Destroy cloud system media that cannot be sanitized." +msgstr "" + +#: ./doc/security-guide/ch046_data-residency.xml:84(para) +msgid "In an OpenStack deployment you will need to address the following:" +msgstr "" + +#: ./doc/security-guide/ch046_data-residency.xml:86(para) +msgid "Secure data erasure" +msgstr "" + +#: ./doc/security-guide/ch046_data-residency.xml:89(para) ./doc/security-guide/ch046_data-residency.xml:106(title) +msgid "Instance memory scrubbing" +msgstr "" + +#: ./doc/security-guide/ch046_data-residency.xml:92(para) +msgid "Block Storage volume data" +msgstr "" + +#: ./doc/security-guide/ch046_data-residency.xml:95(para) ./doc/security-guide/ch046_data-residency.xml:119(title) +msgid "Compute instance ephemeral storage" +msgstr "" + +#: ./doc/security-guide/ch046_data-residency.xml:98(para) ./doc/security-guide/ch046_data-residency.xml:126(title) +msgid "Bare metal server sanitization" +msgstr "" + +#: ./doc/security-guide/ch046_data-residency.xml:102(title) +msgid "Data not securely erased" +msgstr "" + +#: ./doc/security-guide/ch046_data-residency.xml:103(para) +msgid "Within OpenStack some data may be deleted, but not securely erased in the context of the NIST standards outlined above. This is generally applicable to most or all of the above-defined metadata and information stored in the database. This may be remediated with database and/or system configuration for auto vacuuming and periodic free-space wiping." +msgstr "" + +#: ./doc/security-guide/ch046_data-residency.xml:107(para) +msgid "Specific to various hypervisors is the treatment of instance memory. This behavior is not defined in OpenStack Compute, although it is generally expected of hypervisors that they will make a best effort to scrub memory either upon deletion of an instance, upon creation of an instance, or both." +msgstr "" + +#: ./doc/security-guide/ch046_data-residency.xml:108(para) +msgid "Xen explicitly assigns dedicated memory regions to instances and scrubs data upon the destruction of instances (or domains in Xen parlance). KVM depends more greatly on Linux page management; A complex set of rules related to KVM paging is defined in the KVM documentation." +msgstr "" + +#: ./doc/security-guide/ch046_data-residency.xml:109(para) +msgid "It is important to note that use of the Xen memory balloon feature is likely to result in information disclosure. We strongly recommended to avoid use of this feature." +msgstr "" + +#: ./doc/security-guide/ch046_data-residency.xml:110(para) +msgid "For these and other hypervisors, we recommend referring to hypervisor-specific documentation." +msgstr "" + +#: ./doc/security-guide/ch046_data-residency.xml:114(para) +msgid "Plugins to OpenStack Block Storage will store data in a variety of ways. Many plugins are specific to a vendor or technology, whereas others are more DIY solutions around filesystems such as LVM or ZFS. Methods to securely destroy data will vary from one plugin to another, from one vendor's solution to another, and from one filesystem to another." +msgstr "" + +#: ./doc/security-guide/ch046_data-residency.xml:115(para) +msgid "Some backends such as ZFS will support copy-on-write to prevent data exposure. In these cases, reads from unwritten blocks will always return zero. Other backends such as LVM may not natively support this, thus the Cinder plugin takes the responsibility to override previously written blocks before handing them to users. It is important to review what assurances your chosen volume backend provides and to see what mediations may be available for those assurances not provided." +msgstr "" + +#: ./doc/security-guide/ch046_data-residency.xml:116(para) +msgid "Finally, while not a feature of OpenStack, vendors and implementors may choose to add or support encryption of volumes. In this case, destruction of data is as simple as throwing away the key." +msgstr "" + +#: ./doc/security-guide/ch046_data-residency.xml:120(para) +msgid "The creation and destruction of ephemeral storage will be somewhat dependent on the chosen hypervisor and the OpenStack Compute plugin." +msgstr "" + +#: ./doc/security-guide/ch046_data-residency.xml:121(para) +msgid "The libvirt plugin for compute may maintain ephemeral storage directly on a filesystem, or in LVM. Filesystem storage generally will not overwrite data when it is removed, although there is a guarantee that dirty extents are not provisioned to users." +msgstr "" + +#: ./doc/security-guide/ch046_data-residency.xml:122(para) +msgid "When using LVM backed ephemeral storage, which is block-based, it is necessary that the OpenStack Compute software securely erases blocks to prevent information disclosure. There have in the past been information disclosure vulnerabilities related to improperly erased ephemeral block storage devices." +msgstr "" + +#: ./doc/security-guide/ch046_data-residency.xml:123(para) +msgid "Filesystem storage is a more secure solution for ephemeral block storage devices than LVM as dirty extents cannot be provisioned to users. However, it is important to be mindful that user data is not destroyed, so it is suggested to encrypt the backing filesystem." +msgstr "" + +#: ./doc/security-guide/ch046_data-residency.xml:127(para) +msgid "A bare metal server driver for Nova was under development and has since moved into a separate project called Ironic. At the time of this writing, Ironic does not appear to address sanitization of tenant data resident the physical hardware." +msgstr "" + +#: ./doc/security-guide/ch046_data-residency.xml:128(para) +msgid "Additionally, it is possible for tenants of a bare metal system to modify system firmware. TPM technology, described in ##link:Management/Node Bootstrapping##, provides a solution for detecting unauthorized firmware changes." +msgstr "" + +#: ./doc/security-guide/ch062_audit-guidance.xml:3(title) +msgid "Understanding the Audit Process" +msgstr "" + +#: ./doc/security-guide/ch062_audit-guidance.xml:4(para) +msgid "Information system security compliance is reliant on the completion of two foundational processes:" +msgstr "" + +#: ./doc/security-guide/ch062_audit-guidance.xml:6(para) +msgid "Implementation and Operation of Security ControlsAligning the information system with in-scope standards and regulations involves internal tasks which must be conducted before a formal assessment. Auditors may be involved at this state to conduct gap analysis, provide guidance, and increase the likelihood of successful certification." +msgstr "" + +#: ./doc/security-guide/ch062_audit-guidance.xml:9(para) +msgid "Independent Verification and ValidationDemonstration to a neutral third-party that system security controls are implemented and operating effectively, in compliance with in-scope standards and regulations, is required before many information systems achieve certified status. Many certifications require periodic audits to ensure continued certification, considered part of an overarching continuous monitoring practice.  " +msgstr "" + +#: ./doc/security-guide/ch062_audit-guidance.xml:13(title) +msgid "Determining Audit Scope" +msgstr "" + +#: ./doc/security-guide/ch062_audit-guidance.xml:14(para) +msgid "Determining audit scope, specifically what controls are needed and how to design or modify an OpenStack deployment to satisfy them, should be the initial planning step." +msgstr "" + +#: ./doc/security-guide/ch062_audit-guidance.xml:15(para) +msgid "When scoping OpenStack deployments for compliance purposes, consider prioritizing controls around sensitive services, such as command and control functions and the base virtualization technology. Compromises of these facilities may impact an OpenStack environment in its entirety." +msgstr "" + +#: ./doc/security-guide/ch062_audit-guidance.xml:16(para) +msgid "Scope reduction helps ensure OpenStack architects establish high quality security controls which are tailored to a particular deployment, however it is paramount to ensure these practices do not omit areas or features from security hardening. A common example is applicable to PCI-DSS guidelines, where payment related infrastructure may be scrutinized for security issues, but supporting services are left ignored, and vulnerable to attack." +msgstr "" + +#: ./doc/security-guide/ch062_audit-guidance.xml:17(para) +msgid "When addressing compliance, you can increase efficiency and reduce work effort by identifying common areas and criteria that apply across multiple certifications. Much of the audit principles and guidelines discussed in this book will assist in identifying these controls, additionally a number of external entities provide comprehensive lists. The following are some examples:" +msgstr "" + +#: ./doc/security-guide/ch062_audit-guidance.xml:18(para) +msgid "The Cloud Security Alliance Cloud Controls Matrix (CCM) assists both cloud providers and consumers in assessing the overall security of a cloud provider. The CSA CMM provides a controls framework that map to many industry-accepted standards and regulations including the ISO 27001/2, ISACA, COBIT, PCI, NIST, Jericho Forum and NERC CIP." +msgstr "" + +#: ./doc/security-guide/ch062_audit-guidance.xml:19(para) +msgid "The SCAP Security Guide is another useful reference. This is still an emerging source, but we anticipate that this will grow into a tool with controls mappings that are more focused on the US federal government certifications and recommendations. For example, the SCAP Security Guide currently has some mappings for security technical implementation guides (STIGs) and NIST-800-53." +msgstr "" + +#: ./doc/security-guide/ch062_audit-guidance.xml:20(para) +msgid "These control mappings will help identify common control criteria across certifications, and provide visibility to both auditors and auditees on problem areas within control sets for particular compliance certifications and attestations." +msgstr "" + +#: ./doc/security-guide/ch062_audit-guidance.xml:23(title) +msgid "Internal Audit" +msgstr "" + +#: ./doc/security-guide/ch062_audit-guidance.xml:24(para) +msgid "Once a cloud is deployed, it is time for an internal audit. This is the time compare the controls you identified above with the design, features, and deployment strategies utilized in your cloud. The goal is to understand how each control is handled and where gaps exist. Document all of the findings for future reference." +msgstr "" + +#: ./doc/security-guide/ch062_audit-guidance.xml:25(para) +msgid "When auditing an OpenStack cloud it is important to appreciate the multi-tenant environment inherent in the OpenStack architecture. Some critical areas for concern include data disposal, hypervisor security, node hardening, and authentication mechanisms." +msgstr "" + +#: ./doc/security-guide/ch062_audit-guidance.xml:28(title) +msgid "Prepare for External Audit" +msgstr "" + +#: ./doc/security-guide/ch062_audit-guidance.xml:29(para) +msgid "Once the internal audit results look good, it is time to prepare for an external audit. There are several key actions to take at this stage, these are outlined below:" +msgstr "" + +#: ./doc/security-guide/ch062_audit-guidance.xml:31(para) +msgid "Maintain good records from your internal audit. These will prove useful during the external audit so you can be prepared to answer questions about mapping the compliance controls to a particular deployment." +msgstr "" + +#: ./doc/security-guide/ch062_audit-guidance.xml:34(para) +msgid "Deploy automated testing tools to ensure that the cloud remains compliant over time." +msgstr "" + +#: ./doc/security-guide/ch062_audit-guidance.xml:37(para) +msgid "Select an auditor." +msgstr "" + +#: ./doc/security-guide/ch062_audit-guidance.xml:40(para) +msgid "Selecting an auditor can be challenging. Ideally, you are looking for someone with experience in cloud compliance audits. OpenStack experience is another big plus. Often it is best to consult with people who have been through this process for referrals. Cost can vary greatly depending on the scope of the engagement and the audit firm considered." +msgstr "" + +#: ./doc/security-guide/ch062_audit-guidance.xml:43(title) +msgid "External Audit" +msgstr "" + +#: ./doc/security-guide/ch062_audit-guidance.xml:44(para) +msgid "This is the formal audit process. Auditors will test security controls in scope for a specific certification, and demand evidentiary requirements to prove that these controls were also in place for the audit window (for example SOC 2 audits generally evaluate security controls over a 6-12 months period).  Any control failures are logged, and will be documented in the external auditors final report.  Dependent on the type of OpenStack deployment, these reports may be viewed by customers, so it is important to avoid control failures. This is why audit preparation is so important." +msgstr "" + +#: ./doc/security-guide/ch062_audit-guidance.xml:47(title) +msgid "Compliance Maintenance" +msgstr "" + +#: ./doc/security-guide/ch062_audit-guidance.xml:48(para) +msgid "The process doesn't end with a single external audit. Most certifications require continual compliance activities which means repeating the audit process periodically.  We recommend integrating automated compliance verification tools into a cloud to ensure that it is compliant at all times. This should be in done in addition to other security monitoring tools. Remember that the goal is both security and compliance. Failing on either of these fronts will significantly complicate future audits." +msgstr "" + +#. When image changes, this message will be marked fuzzy or untranslated for you. +#. It doesn't matter what you translate it to: it's not used at all. +#: ./doc/security-guide/ch042_database-overview.xml:13(None) ./doc/security-guide/ch042_database-overview.xml:16(None) +msgid "@@image: 'static/databaseusername.png'; md5=a6a5dadedbc1517069ca388c7ac5940a" +msgstr "" + +#. When image changes, this message will be marked fuzzy or untranslated for you. +#. It doesn't matter what you translate it to: it's not used at all. +#: ./doc/security-guide/ch042_database-overview.xml:37(None) ./doc/security-guide/ch042_database-overview.xml:40(None) +msgid "@@image: 'static/databaseusernamessl.png'; md5=9c43242c47eb159b6f61ac41f3d8bced" +msgstr "" + +#. When image changes, this message will be marked fuzzy or untranslated for you. +#. It doesn't matter what you translate it to: it's not used at all. +#: ./doc/security-guide/ch042_database-overview.xml:101(None) ./doc/security-guide/ch042_database-overview.xml:104(None) +msgid "@@image: 'static/novaconductor.png'; md5=dbc1ba139bd1af333f0415bb48704843" +msgstr "" + +#: ./doc/security-guide/ch042_database-overview.xml:3(title) +msgid "Database Access Control" +msgstr "" + +#: ./doc/security-guide/ch042_database-overview.xml:4(para) +msgid "Each of the core OpenStack services (Compute, Identity, Networking, Block Storage) store state and configuration information in databases. In this chapter, we discuss how databases are used currently in OpenStack. We also explore security concerns, and the security ramifications of database backend choices." +msgstr "" + +#: ./doc/security-guide/ch042_database-overview.xml:6(title) +msgid "OpenStack Database Access Model" +msgstr "" + +#: ./doc/security-guide/ch042_database-overview.xml:7(para) +msgid "All of the services within an OpenStack project access a single database. There are presently no reference policies for creating table or row based access restrictions to the database." +msgstr "" + +#: ./doc/security-guide/ch042_database-overview.xml:8(para) +msgid "There are no general provisions for granular control of database operations in OpenStack. Access and privileges are granted simply based on whether a node has access to the database or not.  In this scenario, nodes with access to the database may have full privileges to DROP, INSERT, or UPDATE functions." +msgstr "" + +#: ./doc/security-guide/ch042_database-overview.xml:10(title) +msgid "Granular Access Control" +msgstr "" + +#: ./doc/security-guide/ch042_database-overview.xml:11(para) +msgid "By default, each of the OpenStack services and their processes access the database using a shared set of credentials. This makes auditing database operations and revoking access privileges from a service and its processes to the database particularly difficult." +msgstr "" + +#: ./doc/security-guide/ch042_database-overview.xml:21(title) ./doc/security-guide/ch042_database-overview.xml:96(title) +msgid "Nova Conductor" +msgstr "" + +#: ./doc/security-guide/ch042_database-overview.xml:22(para) +msgid "The compute nodes are the least trusted of the services in OpenStack because they host tenant instances. The nova-conductor service has been introduced to serve as a database proxy, acting as an intermediary between the compute nodes and the database. We discuss its ramifications later in this chapter." +msgstr "" + +#: ./doc/security-guide/ch042_database-overview.xml:23(para) +msgid "We strongly recommend:" +msgstr "" + +#: ./doc/security-guide/ch042_database-overview.xml:25(para) +msgid "All database communications be isolated to a management network" +msgstr "" + +#: ./doc/security-guide/ch042_database-overview.xml:28(para) +msgid "Securing communications using SSL" +msgstr "" + +#: ./doc/security-guide/ch042_database-overview.xml:31(para) +msgid "Creating unique database user accounts per OpenStack service endpoint (illustrated below)" +msgstr "" + +#: ./doc/security-guide/ch042_database-overview.xml:47(title) +msgid "Database Authentication and Access Control" +msgstr "" + +#: ./doc/security-guide/ch042_database-overview.xml:48(para) +msgid "Given the risks around access to the database, we strongly recommend that unique database user accounts be created per node needing access to the database. Doing this facilitates better analysis and auditing for ensuring compliance or in the event of a compromise of a node allows you to isolate the compromised host by removing access for that node to the database upon detection. When creating these per service endpoint database user accounts, care should be taken to ensure that they are configured to require SSL.  Alternatively, for increased security it is recommended that the database accounts be configured using X.509 certificate authentication in addition to usernames and passwords." +msgstr "" + +#: ./doc/security-guide/ch042_database-overview.xml:50(title) +msgid "Privileges" +msgstr "" + +#: ./doc/security-guide/ch042_database-overview.xml:51(para) +msgid "A separate database administrator (DBA) account should be created and protected that has full privileges to create/drop databases, create user accounts, and update user privileges. This simple means of separation of responsibility helps prevent accidental misconfiguration, lowers risk and lowers scope of compromise." +msgstr "" + +#: ./doc/security-guide/ch042_database-overview.xml:52(para) +msgid "The database user accounts created for the OpenStack services and for each node should have privileges limited to just the database relevant to the service where the node is a member." +msgstr "" + +#: ./doc/security-guide/ch042_database-overview.xml:56(title) +msgid "Require User Accounts to Require SSL Transport" +msgstr "" + +#: ./doc/security-guide/ch042_database-overview.xml:58(title) ./doc/security-guide/ch042_database-overview.xml:75(title) +msgid "Configuration Example #1: (MySQL)" +msgstr "" + +#: ./doc/security-guide/ch042_database-overview.xml:63(title) ./doc/security-guide/ch042_database-overview.xml:82(title) +msgid "Configuration Example #2: (PostgreSQL)" +msgstr "" + +#: ./doc/security-guide/ch042_database-overview.xml:64(para) +msgid "In file pg_hba.conf:" +msgstr "" + +#: ./doc/security-guide/ch042_database-overview.xml:67(para) +msgid "Note this command only adds the ability to communicate over SSL and is non-exclusive. Other access methods that may allow unencrypted transport should be disabled so that SSL is the sole access method." +msgstr "" + +#: ./doc/security-guide/ch042_database-overview.xml:68(para) +msgid "The 'md5' parameter defines the authentication method as a hashed password. We provide a secure authentication example in the section below." +msgstr "" + +#: ./doc/security-guide/ch042_database-overview.xml:72(title) +msgid "Authentication with X.509 Certificates" +msgstr "" + +#: ./doc/security-guide/ch042_database-overview.xml:73(para) +msgid "Security may be enhanced by requiring X.509 client certificates for authentication.  Authenticating to the database in this manner provides greater identity assurance of the client making the connection to the database and ensures that the communications are encrypted." +msgstr "" + +#: ./doc/security-guide/ch042_database-overview.xml:88(title) +msgid "OpenStack Service Database Configuration" +msgstr "" + +#: ./doc/security-guide/ch042_database-overview.xml:89(para) +msgid "If your database server is configured to require X.509 certificates for authentication you will need to specify the appropriate SQLAlchemy query parameters for the database backend. These parameters specify the certificate, private key, and certificate authority information for use with the initial connection string." +msgstr "" + +#: ./doc/security-guide/ch042_database-overview.xml:90(para) +msgid "Example of an :sql_connection string for X.509 certificate authentication to MySQL:" +msgstr "" + +#: ./doc/security-guide/ch042_database-overview.xml:97(para) +msgid "OpenStack Compute offers a sub-service called nova-conductor which proxies database connections, with the primary purpose of having the nova compute nodes interfacing with nova-conductor to meet data persistence needs as opposed to directly communicating with the database." +msgstr "" + +#: ./doc/security-guide/ch042_database-overview.xml:98(para) +msgid "Nova-conductor receives requests over RPC and performs actions on behalf of the calling service without granting granular access to the database, its tables, or data within. Nova-conductor essentially abstracts direct database access away from compute nodes." +msgstr "" + +#: ./doc/security-guide/ch042_database-overview.xml:99(para) +msgid "This abstraction offers the advantage of restricting services to executing methods with parameters, similar to stored procedures, preventing a large number of systems from directly accessing or modifying database data. This is accomplished without having these procedures stored or executed within the context or scope of the database itself, a frequent criticism of typical stored procedures." +msgstr "" + +#: ./doc/security-guide/ch042_database-overview.xml:107(para) +msgid "Unfortunately, this solution complicates the task of more fine-grained access control and the ability to audit data access. Because the nova-conductor service receives requests over RPC, it highlights the importance of improving the security of messaging. Any node with access to the message queue may execute these methods provided by the nova-conductor and effectively modifying the database." +msgstr "" + +#: ./doc/security-guide/ch042_database-overview.xml:108(para) +msgid "Finally, it should be noted that as of the Grizzly release, gaps exist where nova-conductor is not used throughout OpenStack Compute. Depending on one's configuration, the use of nova-conductor may not allow deployers to avoid the necessity of providing database GRANTs to individual compute host systems." +msgstr "" + +#: ./doc/security-guide/ch042_database-overview.xml:109(para) +msgid "Note, as nova-conductor only applies to OpenStack Compute, direct database access from compute hosts may still be necessary for the operation of other OpenStack components such as Telemetry (Ceilometer), Networking, and Block Storage." +msgstr "" + +#: ./doc/security-guide/ch042_database-overview.xml:110(para) +msgid "Implementors should weigh the benefits and risks of both configurations before enabling or disabling the nova-conductor service. We are not yet prepared to recommend the use of nova-conductor in the Grizzly release. However, we do believe that this recommendation will change as additional features are added into OpenStack." +msgstr "" + +#: ./doc/security-guide/ch042_database-overview.xml:111(para) +msgid "To disable the nova-conductor, place the following into your nova.conf file (on your compute hosts):" +msgstr "" + +#: ./doc/security-guide/ch024_authentication.xml:3(title) +msgid "Identity" +msgstr "" + +#: ./doc/security-guide/ch024_authentication.xml:4(para) +msgid "The OpenStack Identity Service (Keystone) supports multiple methods of authentication, including username & password, LDAP, and external authentication methods.  Upon successful authentication, The Identity Service provides the user with an authorization token used for subsequent service requests." +msgstr "" + +#: ./doc/security-guide/ch024_authentication.xml:5(para) +msgid "Transport Layer Security TLS/SSL provides authentication between services and persons using X.509 certificates.  Although the default mode for SSL is server-side only authentication, certificates may also be used for client authentication." +msgstr "" + +#: ./doc/security-guide/ch024_authentication.xml:7(title) +msgid "Authentication" +msgstr "" + +#: ./doc/security-guide/ch024_authentication.xml:9(title) +msgid "Invalid Login Attempts" +msgstr "" + +#: ./doc/security-guide/ch024_authentication.xml:10(para) +msgid "The Identity Service does not provide a method to limit access to accounts after repeated unsuccessful login attempts. Repeated failed login attempts are likely brute-force attacks (Refer figure Attack-types). This is a more significant issue in Public clouds." +msgstr "" + +#: ./doc/security-guide/ch024_authentication.xml:11(para) +msgid "Prevention is possible by using an external authentication system that blocks out an account after some configured number of failed login attempts. The account then may only be unlocked with further side-channel intervention." +msgstr "" + +#: ./doc/security-guide/ch024_authentication.xml:12(para) +msgid "If prevention is not an option, detection can be used to mitigate damage.Detection involves frequent review of access control logs to identify unauthorized attempts to access accounts. Possible remediation would include reviewing the strength of the user password, or blocking the network source of the attack via firewall rules. Firewall rules on the keystone server that restrict the number of connections could be used to reduce the attack effectiveness, and thus dissuade the attacker." +msgstr "" + +#: ./doc/security-guide/ch024_authentication.xml:13(para) +msgid "In addition, it is useful to examine account activity for unusual login times and suspicious actions, with possibly disable the account. Often times this approach is taken by credit card providers for fraud detection and alert." +msgstr "" + +#: ./doc/security-guide/ch024_authentication.xml:16(title) +msgid "Multi-factor Authentication" +msgstr "" + +#: ./doc/security-guide/ch024_authentication.xml:17(para) +msgid "Employ multi-factor authentication for network access to privileged user accounts. The Identity Service supports external authentication services through the Apache web server that can provide this functionality. Servers may also enforce client-side authentication using certificates." +msgstr "" + +#: ./doc/security-guide/ch024_authentication.xml:18(para) +msgid "This recommendation provides insulation from brute force, social engineering, and both spear and mass phishing attacks that may compromise administrator passwords." +msgstr "" + +#: ./doc/security-guide/ch024_authentication.xml:22(title) +msgid "Authentication Methods" +msgstr "" + +#: ./doc/security-guide/ch024_authentication.xml:24(title) +msgid "Internally Implemented Authentication Methods" +msgstr "" + +#: ./doc/security-guide/ch024_authentication.xml:25(para) +msgid "The Identity Service can store user credentials in an SQL Database, or may use an LDAP-compliant directory server. The Identity database may be separate from databases used by other OpenStack services to reduce the risk of a compromise of the stored credentials." +msgstr "" + +#: ./doc/security-guide/ch024_authentication.xml:26(para) +msgid "When authentication is provided via username and password, the Identity Service does not enforce policies on password strength, expiration, or failed authentication attempts as recommended by NIST Special Publication 800-118 (draft). Organizations that desire to enforce stronger password policies should consider using Keystone Identity Service Extensions or external authentication services." +msgstr "" + +#: ./doc/security-guide/ch024_authentication.xml:27(para) +msgid "LDAP simplifies integration of Identity authentication into an organization's existing directory service and user account management processes." +msgstr "" + +#: ./doc/security-guide/ch024_authentication.xml:28(para) +msgid "Authentication and authorization policy in OpenStack may be delegated to an external LDAP server. A typical use case is an organization that seeks to deploy a private cloud and already has a database of employees, the users. This may be in an LDAP system. Using LDAP as a source of authority authentication, requests to Identity Service are delegated to the LDAP service, which will authorize or deny requests based on locally set policies. A token is generated on successful authentication." +msgstr "" + +#: ./doc/security-guide/ch024_authentication.xml:29(para) +msgid "Note that if the LDAP system has attributes defined for the user such as admin, finance, HR etc, these must be mapped into roles and groups within Identity for use by the various OpenStack services. The etc/keystone.conf file provides the mapping from the LDAP attributes to Identity attributes." +msgstr "" + +#: ./doc/security-guide/ch024_authentication.xml:30(para) +msgid "The Identity Service MUST NOT be allowed to write to LDAP services used for authentication outside of the OpenStack deployment as this would allow a sufficiently privileged keystone user to make changes to the LDAP directory. This would allow privilege escalation within the wider organization or facilitate unauthorized access to other information and resources. In such a deployment, user provisioning would be out of the realm of the OpenStack deployment." +msgstr "" + +#: ./doc/security-guide/ch024_authentication.xml:32(para) +msgid "There is an OpenStack Security Note (OSSN) regarding keystone.conf permissions." +msgstr "" + +#: ./doc/security-guide/ch024_authentication.xml:33(para) +msgid "There is an OpenStack Security Note (OSSN) regarding potential DoS attacks." +msgstr "" + +#: ./doc/security-guide/ch024_authentication.xml:37(title) +msgid "External Authentication Methods" +msgstr "" + +#: ./doc/security-guide/ch024_authentication.xml:38(para) +msgid "Organizations may desire to implement external authentication for compatibility with existing authentication services or to enforce stronger authentication policy requirements. Although passwords are the most common form of authentication, they can be compromised through numerous methods, including keystroke logging and password compromise. External authentication services can provide alternative forms of authentication that minimize the risk from weak passwords." +msgstr "" + +#: ./doc/security-guide/ch024_authentication.xml:39(para) +msgid "These include:" +msgstr "" + +#: ./doc/security-guide/ch024_authentication.xml:41(para) +msgid "Password Policy Enforcement: Requires user passwords to conform to minimum standards for length, diversity of characters, expiration, or failed login attempts." +msgstr "" + +#: ./doc/security-guide/ch024_authentication.xml:44(para) +msgid "Multi-factor authentication: The authentication service requires the user to provide information based on something they have, such as a one-time password token or X.509 certificate, and something they know, such as a password." +msgstr "" + +#: ./doc/security-guide/ch024_authentication.xml:51(para) +msgid "Kerberos" +msgstr "" + +#: ./doc/security-guide/ch024_authentication.xml:57(title) +msgid "Authorization" +msgstr "" + +#: ./doc/security-guide/ch024_authentication.xml:58(para) +msgid "The Identity Service supports the notion of groups and roles. Users belong to groups. A group has a list of roles. OpenStack services reference the roles of the user attempting to access the service. The OpenStack policy enforcer middleware takes into consideration the policy rule associated with each resource and the user's group/roles and tenant association to determine if he/she has access to the requested resource." +msgstr "" + +#: ./doc/security-guide/ch024_authentication.xml:59(para) +msgid "The Policy enforcement middleware enables fine-grained access control to OpenStack resources. Only admin users can provision new users and have access to various management functionality. The cloud tenant would be able to only spin up instances, attach volumes, etc." +msgstr "" + +#: ./doc/security-guide/ch024_authentication.xml:61(title) +msgid "Establish Formal Access Control Policies" +msgstr "" + +#: ./doc/security-guide/ch024_authentication.xml:62(para) +msgid "Prior to configuring roles, groups, and users, document your required access control policies for the OpenStack installation. The policies should be consistent with any regulatory or legal requirements for the organization. Future modifications to access control configuration should be done consistently with the formal policies. The policies should include the conditions and processes for creating, deleting, disabling, and enabling accounts, and for assigning privileges to the accounts. Periodically review the policies and ensure that configuration is in compliance with approved policies." +msgstr "" + +#: ./doc/security-guide/ch024_authentication.xml:65(title) +msgid "Service Authorization" +msgstr "" + +#: ./doc/security-guide/ch024_authentication.xml:66(para) +msgid "As described in the OpenStack Cloud Administrator Guide, cloud administrators must define a user for each service, with a role of Admin. This service user account provides the service with the authorization to authenticate users." +msgstr "" + +#: ./doc/security-guide/ch024_authentication.xml:67(para) +msgid "The Compute and Object Storage services can be configured to use either the \"tempAuth\" file or Identity Service to store authentication information. The \"tempAuth\" solution MUST NOT be deployed in a production environment since it stores passwords in plain text." +msgstr "" + +#: ./doc/security-guide/ch024_authentication.xml:68(para) +msgid "The Identity Service supports client authentication for SSL which may be enabled. SSL client authentication provides an additional authentication factor, in addition to the username / password, that provides greater reliability on user identification. It reduces the risk of unauthorized access when user names and passwords may be compromised.  However, there is additional administrative overhead and cost to issue certificates to users that may not be feasible in every deployment." +msgstr "" + +#: ./doc/security-guide/ch024_authentication.xml:78(para) +msgid "We recommend that you use client authentication with SSL for the authentication of services to the Identity Service." +msgstr "" + +#: ./doc/security-guide/ch024_authentication.xml:80(para) +msgid "The cloud administrator should protect sensitive configuration files for unauthorized modification. This can be achieved with mandatory access control frameworks such as SELinux, including /etc/keystone.conf and X.509 certificates." +msgstr "" + +#: ./doc/security-guide/ch024_authentication.xml:82(para) +msgid "For client authentication with SSL, you need to issue certificates. These certificates can be signed by an external authority or by the cloud administrator. OpenStack services by default check the signatures of certificates and connections fail if the signature cannot be checked. If the administrator uses self-signed certificates, the check might need to be disabled. To disable these certificates, set insecure=False in the [filter:authtoken] section in the /etc/nova/api.paste.ini file. This setting also disables certificates for other components." +msgstr "" + +#: ./doc/security-guide/ch024_authentication.xml:96(title) +msgid "Administrative Users" +msgstr "" + +#: ./doc/security-guide/ch024_authentication.xml:97(para) +msgid "We recommend that admin users authenticate using Identity Service and an external authentication service that supports 2-factor authentication, such as a certificate.  This reduces the risk from passwords that may be compromised. This recommendation is in compliance with NIST 800-53 IA-2(1) guidance in the use of multi factor authentication for network access to privileged accounts." +msgstr "" + +#: ./doc/security-guide/ch024_authentication.xml:106(title) +msgid "End Users" +msgstr "" + +#: ./doc/security-guide/ch024_authentication.xml:107(para) +msgid "The Identity Service can directly provide end-user authentication, or can be configured to use external authentication methods to conform to an organization's security policies and requirements." +msgstr "" + +#: ./doc/security-guide/ch024_authentication.xml:111(title) +msgid "Policies" +msgstr "" + +#: ./doc/security-guide/ch024_authentication.xml:112(para) +msgid "Each OpenStack service has a policy file in json format, called policy.json. The policy file specifies rules, and the rule that governs each resource. A resource could be API access, the ability to attach to a volume, or to fire up instances." +msgstr "" + +#: ./doc/security-guide/ch024_authentication.xml:113(para) +msgid "The policies can be updated by the cloud administrator to further control access to the various resources. The middleware could also be further customized. Note that your users must be assigned to groups/roles that you refer to in your policies." +msgstr "" + +#: ./doc/security-guide/ch024_authentication.xml:114(para) +msgid "Below is a snippet of the Block Storage service policy.json file." +msgstr "" + +#: ./doc/security-guide/ch024_authentication.xml:133(para) +msgid "Note the default rule specifies that the user must be either an admin or the owner of the volume. It essentially says only the owner of a volume or the admin may create/delete/update volumes. Certain other operations such as managing volume types are accessible only to admin users." +msgstr "" + +#: ./doc/security-guide/ch024_authentication.xml:136(title) +msgid "Tokens" +msgstr "" + +#: ./doc/security-guide/ch024_authentication.xml:137(para) +msgid "Once a user is authenticated, a token is generated and used internally in OpenStack for authorization and access. The default token lifespan is 24 hours. It is recommended that this value be set lower but caution needs to be taken as some internal services will need sufficient time to complete their work. The cloud may not provide services if tokens expire too early. An example of this would be the time needed by the Compute Service to transfer a disk image onto the hypervisor for local caching." +msgstr "" + +#: ./doc/security-guide/ch024_authentication.xml:138(para) +msgid "The following example shows a PKI token. Note that, in practice, the token id value is about 3500 bytes. We shorten it in this example." +msgstr "" + +#: ./doc/security-guide/ch024_authentication.xml:153(para) +msgid "Note that the token is often passed within the structure of a larger context of an Identity Service response. These responses also provide a catalog of the various OpenStack services. Each service is listed with its name, access endpoints for internal, admin, and public access." +msgstr "" + +#: ./doc/security-guide/ch024_authentication.xml:154(para) +msgid "The Identity Service supports token revocation. This manifests as an API to revoke a token, to list revoked tokens and individual OpenStack services that cache tokens to query for the revoked tokens and remove them from their cache and append the same to their list of cached revoked tokens." +msgstr "" + +#: ./doc/security-guide/ch024_authentication.xml:157(title) +msgid "Future" +msgstr "" + +#: ./doc/security-guide/ch024_authentication.xml:158(para) +msgid "Domains are high-level containers for projects, users and groups. As such, they can be used to centrally manage all Keystone-based identity components. With the introduction of account Domains, server, storage and other resources can now be logically grouped into multiple Projects (previously called Tenants) which can themselves be grouped under a master account-like container. In addition, multiple users can be managed within an account Domain and assigned roles that vary for each Project." +msgstr "" + +#: ./doc/security-guide/ch024_authentication.xml:159(para) +msgid "Keystone's V3 API supports multiple domains. Users of different domains may be represented in different authentication backends and even have different attributes that must be mapped to a single set of roles and privileges, that are used in the policy definitions to access the various service resources." +msgstr "" + +#: ./doc/security-guide/ch024_authentication.xml:160(para) +msgid "Where a rule may specify access to only admin users and users belonging to the tenant, the mapping may be trivial. In other scenarios the cloud administrator may need to approve the mapping routines per tenant." +msgstr "" + +#: ./doc/security-guide/ch015_case-studies-management.xml:9(title) +msgid "Case Studies: Management Interfaces" +msgstr "" + +#: ./doc/security-guide/ch015_case-studies-management.xml:10(para) +msgid "Previously we discussed typical OpenStack management interfaces and associated backplane issues. We will now approach these issues by returning to our Alice and Bob case study. Specifically, we will look into how both Alice and Bob will address:" +msgstr "" + +#: ./doc/security-guide/ch015_case-studies-management.xml:16(para) +msgid "Cloud Administration" +msgstr "" + +#: ./doc/security-guide/ch015_case-studies-management.xml:19(para) +msgid "Self Service" +msgstr "" + +#: ./doc/security-guide/ch015_case-studies-management.xml:22(para) +msgid "Data Replication & Recovery" +msgstr "" + +#: ./doc/security-guide/ch015_case-studies-management.xml:25(para) +msgid "SLA & Security Monitoring." +msgstr "" + +#: ./doc/security-guide/ch015_case-studies-management.xml:30(para) +msgid "When building her private cloud, while air-gapped, Alice still needs to consider her service management interfaces. Before deploying her private cloud, Alice has completed her system documentation. Specifically she has identified which OpenStack services will exist in each security domain. From there Alice has further restricted access to management interfaces by deploying a combination of IDS, SSL encryption, and physical network isolation. Additionally, Alice requires high availability and redundant services. Thus, Alice sets up redundant infrastructure for various OpenStack API services." +msgstr "" + +#: ./doc/security-guide/ch015_case-studies-management.xml:31(para) +msgid "Alice also needs to provide assurances that the physical servers and hypervisors have been built from a known secure state into a well-defined configuration. To enable this, Alice uses a combination of a Configuration Management platform to configure each machine according to the standards and regulations she must comply with. It will also enable Alice to report periodically on the state of her cloud and perform remediation to a known state should anything be out of the ordinary. Additionally, Alice provides hardware assurances by using a PXE system to build her nodes from a known set of base images. During the boot process, Alice provides further assurances by enabling Intel TXT and related trusted boot technologies provided by the hardware." +msgstr "" + +#: ./doc/security-guide/ch015_case-studies-management.xml:35(para) +msgid "As a public cloud provider, Bob is concerned with both the continuous availability of management interfaces and the security of transactions to the management interfaces. To that end Bob implements multiple redundant OpenStack API endpoints for the services his cloud will run. Additionally on the public network Bob uses SSL to encrypt all transactions between his customers and his cloud interfaces. To isolate his cloud operations Bob has physically isolated his management, instance migration, and storage networks." +msgstr "" + +#: ./doc/security-guide/ch015_case-studies-management.xml:36(para) +msgid "To ease scaling and reduce management overhead Bob implements a configuration management system. For customer data assurances, Bob offers a backup as a service product as requirements will vary between customers. Finally, Bob does not provide a \"baremetal\" or the ability to schedule an entire node, so to reduce management overhead and increase operational efficiency Bob does not implement any node boot time security." +msgstr "" + +#: ./doc/security-guide/ch018_case-studies-pkissl.xml:3(title) +msgid "Case Studies: PKI and Certificate Management" +msgstr "" + +#: ./doc/security-guide/ch018_case-studies-pkissl.xml:4(para) +msgid "In this case study we discuss how Alice and Bob would address deployment of PKI certification authorities (CA) and certificate management." +msgstr "" + +#: ./doc/security-guide/ch018_case-studies-pkissl.xml:7(para) +msgid "Alice as a cloud architect within a government agency knows that her agency operates its own certification authority. Alice contacts the PKI office in her agency that manages her PKI and certificate issuance. Alice obtains certificates issued by this CA and configures the services within both the public and management security domains to use these certificates. Since Alice's OpenStack deployment exists entirely on a disconnected from the Internet network, she makes sure to remove all default CA bundles that contain external public CA providers to ensure the OpenStack services only accept client certificates issued by her agency's CA." +msgstr "" + +#: ./doc/security-guide/ch018_case-studies-pkissl.xml:11(para) +msgid "Bob is architecting a public cloud and needs to ensure that the publicly facing OpenStack services are using certificates issued by a major public CA. Bob acquires certificates for his public OpenStack services and configures the services to use PKI and SSL and includes the public CAs in his trust bundle for the services. Additionally, Bob also wants to further isolate the internal communications amongst the services within the management security domain. Bob contacts the team within his organization that is responsible for managing his organizations PKI and issuance of certificates using their own internal CA. Bob obtains certificates issued by this internal CA and configures the services that communicate within the management security domain to use these certificates and configures the services to only accept client certificates issued by his internal CA." +msgstr "" + +#. When image changes, this message will be marked fuzzy or untranslated for you. +#. It doesn't matter what you translate it to: it's not used at all. +#: ./doc/security-guide/ch031_neutron-architecture.xml:24(None) ./doc/security-guide/ch031_neutron-architecture.xml:27(None) +msgid "@@image: 'static/sdn-connections.png'; md5=3fb0f3e2bea0784fea8832526d2b2832" +msgstr "" + +#. When image changes, this message will be marked fuzzy or untranslated for you. +#. It doesn't matter what you translate it to: it's not used at all. +#: ./doc/security-guide/ch031_neutron-architecture.xml:36(None) ./doc/security-guide/ch031_neutron-architecture.xml:39(None) +msgid "@@image: 'static/1aa-network-domains-diagram.png'; md5=57ae4448b05a3852180f75f3995711b9" +msgstr "" + +#: ./doc/security-guide/ch031_neutron-architecture.xml:3(title) +msgid "Networking Architecture" +msgstr "" + +#: ./doc/security-guide/ch031_neutron-architecture.xml:4(para) +msgid "OpenStack Networking is a standalone service that often involves deploying several processes across a number of nodes. These processes interact with each other and with other OpenStack services. The main process of the OpenStack Networking service is neutron-server, a Python daemon that exposes the OpenStack Networking API and passes tenant requests to a suite of plugins for additional processing." +msgstr "" + +#: ./doc/security-guide/ch031_neutron-architecture.xml:5(para) +msgid "OpenStack Networking components encompasses the following elements:" +msgstr "" + +#: ./doc/security-guide/ch031_neutron-architecture.xml:7(para) +msgid "neutron server (neutron-server and neutron-*-plugin): This service runs on the network node to service the Networking API and its extensions. It also enforces the network model and IP addressing of each port. The neutron-server and plugin agents require access to a database for persistent storage and access to a message queue for inter-communication." +msgstr "" + +#: ./doc/security-guide/ch031_neutron-architecture.xml:10(para) +msgid "plugin agent (neutron-*-agent): Runs on each compute node to manage local virtual switch (vswitch) configuration. The agents to be run will depend on which plugin you are using. This service requires message queue access. Optional depending on plugin." +msgstr "" + +#: ./doc/security-guide/ch031_neutron-architecture.xml:13(para) +msgid "DHCP agent (neutron-dhcp-agent): Provides DHCP services to tenant networks. This agent is the same across all plugins and is responsible for maintaining DHCP configuration. The neutron-dhcp-agent requires message queue access." +msgstr "" + +#: ./doc/security-guide/ch031_neutron-architecture.xml:16(para) +msgid "l3 agent (neutron-l3-agent): Provides L3/NAT forwarding for external network access of VMs on tenant networks. Requires message queue access. Optional depending on plugin." +msgstr "" + +#: ./doc/security-guide/ch031_neutron-architecture.xml:19(para) +msgid "network provider services (SDN server/services). Provide additional networking services that are provided to tenant networks. These SDN services may interact with the neutron-server, neutron-plugin, and/or plugin-agents via REST APIs or other communication channels." +msgstr "" + +#: ./doc/security-guide/ch031_neutron-architecture.xml:22(para) +msgid "The figure that follows provides an architectural and networking flow diagram of the OpenStack Networking components:" +msgstr "" + +#: ./doc/security-guide/ch031_neutron-architecture.xml:31(title) +msgid "OS Networking Service placement on Physical Servers" +msgstr "" + +#: ./doc/security-guide/ch031_neutron-architecture.xml:32(para) +msgid "In this guide, we focus primarily on a standard architecture that includes a cloud controller host, a network host, and a set of compute hypervisors for running VMs." +msgstr "" + +#: ./doc/security-guide/ch031_neutron-architecture.xml:34(title) +msgid "Network Connectivity of Physical Servers" +msgstr "" + +#: ./doc/security-guide/ch031_neutron-architecture.xml:42(para) +msgid "A standard OpenStack Networking setup has up to four distinct physical data center networks:" +msgstr "" + +#: ./doc/security-guide/ch031_neutron-architecture.xml:44(para) +msgid "Management network Used for internal communication between OpenStack Components. The IP addresses on this network should be reachable only within the data center and is considered the Management Security Domain." +msgstr "" + +#: ./doc/security-guide/ch031_neutron-architecture.xml:47(para) +msgid "Guest network Used for VM data communication within the cloud deployment. The IP addressing requirements of this network depend on the OpenStack Networking plugin in use and the network configuration choices of the virtual networks made by the tenant. This network is considered the Guest Security Domain." +msgstr "" + +#: ./doc/security-guide/ch031_neutron-architecture.xml:50(para) +msgid "External network Used to provide VMs with Internet access in some deployment scenarios. The IP addresses on this network should be reachable by anyone on the Internet and is considered to be in the Public Security Domain." +msgstr "" + +#: ./doc/security-guide/ch031_neutron-architecture.xml:53(para) +msgid "API network Exposes all OpenStack APIs, including the OpenStack Networking API, to tenants. The IP addresses on this network should be reachable by anyone on the Internet. This may be the same network as the external network, as it is possible to create a subnet for the external network that uses IP allocation ranges to use only less than the full range of IP addresses in an IP block. This network is considered the Public Security Domain." +msgstr "" + +#: ./doc/security-guide/ch031_neutron-architecture.xml:56(para) +msgid "For additional information see the Networking chapter in the OpenStack Cloud Administrator Guide." +msgstr "" + +#: ./doc/security-guide/ch047_data-encryption.xml:3(title) +msgid "Data Encryption" +msgstr "" + +#: ./doc/security-guide/ch047_data-encryption.xml:4(para) +msgid "The option exists for implementors to encrypt tenant data wherever it is stored on disk or transported over a network. This is above and beyond the general recommendation that users encrypt their own data before sending it to their provider." +msgstr "" + +#: ./doc/security-guide/ch047_data-encryption.xml:5(para) +msgid "The importance of encrypting data on behalf of tenants is largely related to the risk assumed by a provider that an attacker could access tenant data. There may be requirements here in government, as well as requirements per-policy, in private contract, or even in case law in regard to private contracts for public cloud providers. It is recommended that a risk assessment and legal consul advised before choosing tenant encryption policies." +msgstr "" + +#: ./doc/security-guide/ch047_data-encryption.xml:6(para) +msgid "Per-instance or per-object encryption is preferable over, in descending order, over per-project, per-tenant, per-host, and per-cloud aggregations. This recommendation is inverse to the complexity and difficulty of implementation. Presently, in some projects it is difficult or impossible to implement encryption as loosely granular as even per-tenant. We recommend implementors make a best-effort in encrypting tenant data." +msgstr "" + +#: ./doc/security-guide/ch047_data-encryption.xml:7(para) +msgid "Often, data encryption relates positively to the ability to reliably destroy tenant and per-instance data, simply by throwing away the keys. It should be noted that in doing so, it becomes of great importance to destroy those keys in a reliable and secure manner." +msgstr "" + +#: ./doc/security-guide/ch047_data-encryption.xml:8(para) +msgid "Opportunities to encrypt data for users are present:" +msgstr "" + +#: ./doc/security-guide/ch047_data-encryption.xml:10(para) +msgid "Object Storage objects" +msgstr "" + +#: ./doc/security-guide/ch047_data-encryption.xml:13(para) +msgid "Block Storage volumes & Instance Ephemeral Filesystems" +msgstr "" + +#: ./doc/security-guide/ch047_data-encryption.xml:16(para) +msgid "Network data" +msgstr "" + +#: ./doc/security-guide/ch047_data-encryption.xml:20(title) +msgid "Object Storage Objects" +msgstr "" + +#: ./doc/security-guide/ch047_data-encryption.xml:21(para) +msgid "The ability to encrypt objects in Object Storage is presently limited to disk-level encryption per node. However, there does exist third-party extensions and modules for per-object encryption. These modules have been proposed upstream, but have not per this writing been formally accepted. Below are some pointers: " +msgstr "" + +#: ./doc/security-guide/ch047_data-encryption.xml:22(link) +msgid "https://github.com/Mirantis/swift-encrypt" +msgstr "" + +#: ./doc/security-guide/ch047_data-encryption.xml:23(link) +msgid "http://www.mirantis.com/blog/on-disk-encryption-prototype-for-openstack-swift/" +msgstr "" + +#: ./doc/security-guide/ch047_data-encryption.xml:26(title) +msgid "Block Storage Volumes & Instance Ephemeral Filesystems" +msgstr "" + +#: ./doc/security-guide/ch047_data-encryption.xml:27(para) +msgid "The ability to encrypt volumes depends on the service backends chosen. Some backends may not support this at all." +msgstr "" + +#: ./doc/security-guide/ch047_data-encryption.xml:28(para) +msgid "As both block storage and compute support LVM backed storage, we can easily provide an example applicable to both systems. In deployments using LVM, encryption may be performed against the backing physical volumes. An encrypted block device would be created using the standard Linux tools, with the LVM physical volume (PV) created on top of the decrypted block device using pvcreate. Then, the vgcreate or vgmodify tool may be used to add the encrypted physical volume to an LVM volume group (VG)." +msgstr "" + +#: ./doc/security-guide/ch047_data-encryption.xml:29(para) +msgid "A feature aimed for the Havana release provides encryption of the VM's data before it is written to disk. This allows the privacy of data to be maintained while residing on the storage device. The idea is similar to how self-encrypting drives work. This feature presents a normal block storage device to the VM but encrypts the bytes in the virtualization host before writing them to the disk. The block server operates exactly as it does when reading and writing unencrypted blocks, except special handling will be required for Block Storage features such as snapshots and live migration.  Note that this feature uses an independent key manager." +msgstr "" + +#: ./doc/security-guide/ch047_data-encryption.xml:32(title) +msgid "Network Data" +msgstr "" + +#: ./doc/security-guide/ch047_data-encryption.xml:33(para) +msgid "Tenant data for compute could be encrypted over IPSec or other tunnels. This is not functionality common or standard in OpenStack, but is an option available to motivated and interested implementors." +msgstr "" + +#: ./doc/security-guide/ch047_data-encryption.xml:37(para) +msgid "Block storage supports a variety of mechanisms for supplying mountable volumes. It is outside the scope of this guide to specify recommendations for each Block Storage backend driver. For the purpose of performance, many storage protocols are unencrypted. Some protocols such as iSCSI can provide authentication and encrypted sessions, it is our recommendation to enable these features." +msgstr "" + +#. When image changes, this message will be marked fuzzy or untranslated for you. +#. It doesn't matter what you translate it to: it's not used at all. +#: ./doc/security-guide/ch005_security-domains.xml:24(None) ./doc/security-guide/ch005_security-domains.xml:27(None) +msgid "@@image: 'static/untrusted_trusted.png'; md5=a582dac2ad0b3f439fd4b08386853056" +msgstr "" + +#. When image changes, this message will be marked fuzzy or untranslated for you. +#. It doesn't matter what you translate it to: it's not used at all. +#: ./doc/security-guide/ch005_security-domains.xml:55(None) ./doc/security-guide/ch005_security-domains.xml:58(None) +msgid "@@image: 'static/bridging_security_domains_1.png'; md5=0d5ca26c51882ce3253405e91a597715" +msgstr "" + +#. When image changes, this message will be marked fuzzy or untranslated for you. +#. It doesn't matter what you translate it to: it's not used at all. +#: ./doc/security-guide/ch005_security-domains.xml:63(None) ./doc/security-guide/ch005_security-domains.xml:66(None) +msgid "@@image: 'static/bridging_domains_clouduser.png'; md5=17c8a233ee7de17d2f600c7f6f6afe24" +msgstr "" + +#. When image changes, this message will be marked fuzzy or untranslated for you. +#. It doesn't matter what you translate it to: it's not used at all. +#: ./doc/security-guide/ch005_security-domains.xml:95(None) ./doc/security-guide/ch005_security-domains.xml:98(None) +msgid "@@image: 'static/threat_actors.png'; md5=114c2f9bd9d0319bdd83f9e229d44649" +msgstr "" + +#. When image changes, this message will be marked fuzzy or untranslated for you. +#. It doesn't matter what you translate it to: it's not used at all. +#: ./doc/security-guide/ch005_security-domains.xml:116(None) ./doc/security-guide/ch005_security-domains.xml:119(None) +msgid "@@image: 'static/high-capability.png'; md5=b7ab599c8b40558a52c0ca86aad89741" +msgstr "" + +#: ./doc/security-guide/ch005_security-domains.xml:3(title) +msgid "Security Boundaries and Threats" +msgstr "" + +#: ./doc/security-guide/ch005_security-domains.xml:4(para) +msgid "A cloud can be abstracted as a collection of logical components by virtue of their function, users, and shared security concerns, which we call security domains. Threat actors and vectors are classified based on their motivation and access to resources. Our goal is to provide you a sense of the security concerns with respect to each domain depending on your risk/vulnerability protection objectives." +msgstr "" + +#: ./doc/security-guide/ch005_security-domains.xml:6(title) +msgid "Security Domains" +msgstr "" + +#: ./doc/security-guide/ch005_security-domains.xml:7(para) +msgid "A security domain comprises users, applications, servers or networks that share common trust requirements and expectations within a system. Typically they have the same authentication and authorization (AuthN/Z) requirements and users." +msgstr "" + +#: ./doc/security-guide/ch005_security-domains.xml:8(para) +msgid "Although you may desire to break these domains down further (we later discuss where this may be appropriate), we generally refer to four distinct security domains which form the bare minimum that is required to deploy any OpenStack cloud securely. These security domains are:" +msgstr "" + +#: ./doc/security-guide/ch005_security-domains.xml:10(para) ./doc/security-guide/ch005_security-domains.xml:31(title) +msgid "Public" +msgstr "" + +#: ./doc/security-guide/ch005_security-domains.xml:13(para) ./doc/security-guide/ch005_security-domains.xml:36(title) +msgid "Guest" +msgstr "" + +#: ./doc/security-guide/ch005_security-domains.xml:16(para) ./doc/security-guide/ch005_security-domains.xml:41(title) +msgid "Management" +msgstr "" + +#: ./doc/security-guide/ch005_security-domains.xml:19(para) ./doc/security-guide/ch005_security-domains.xml:46(title) +msgid "Data" +msgstr "" + +#: ./doc/security-guide/ch005_security-domains.xml:22(para) +msgid "We selected these security domains because they can be mapped independently or combined to represent the majority of the possible areas of trust within a given OpenStack deployment. For example, some deployment topologies combine both guest and data domains onto one physical network versus others, which have these networks physically separated. In each case, the cloud operator should be aware of the appropriate security concerns. Security domains should be mapped out against your specific OpenStack deployment topology. The domains and their trust requirements depend upon whether the cloud instance is public, private, or hybrid." +msgstr "" + +#: ./doc/security-guide/ch005_security-domains.xml:32(para) +msgid "The public security domain is an entirely untrusted area of the cloud infrastructure. It can refer to the Internet as a whole or simply to networks over which you have no authority. Any data that transits this domain with confidentiality or integrity requirements should be protected using compensating controls." +msgstr "" + +#: ./doc/security-guide/ch005_security-domains.xml:33(para) +msgid "This domain should always be considered untrusted." +msgstr "" + +#: ./doc/security-guide/ch005_security-domains.xml:37(para) +msgid "Typically used for compute instance-to-instance traffic, the guest security domain handles compute data generated by instances on the cloud but not services that support the operation of the cloud, such as API calls." +msgstr "" + +#: ./doc/security-guide/ch005_security-domains.xml:38(para) +msgid "Public cloud providers and private cloud providers who do not have stringent controls on instance use or who allow unrestricted internet access to VMs should consider this domain to be untrusted. Private cloud providers may want to consider this network as internal and therefore trusted only if they have controls in place to assert that they trust instances and all their tenants." +msgstr "" + +#: ./doc/security-guide/ch005_security-domains.xml:42(para) +msgid "The management security domain is where services interact. Sometimes referred to as the \"control plane\", the networks in this domain transport confidential data such as configuration parameters, usernames, and passwords. Command and Control traffic typically resides in this domain, which necessitates strong integrity requirements. Access to this domain should be highly restricted and monitored. At the same time, this domain should still employ all of the security best practices described in this guide." +msgstr "" + +#: ./doc/security-guide/ch005_security-domains.xml:43(para) +msgid "In most deployments this domain is considered trusted. However, when considering an OpenStack deployment, there are many systems that bridge this domain with others, potentially reducing the level of trust you can place on this domain. See for more information." +msgstr "" + +#: ./doc/security-guide/ch005_security-domains.xml:47(para) +msgid "The data security domain is concerned primarily with information pertaining to the storage services within OpenStack. Much of the data that crosses this network has high integrity and confidentiality requirements and depending on the type of deployment there may also be strong availability requirements." +msgstr "" + +#: ./doc/security-guide/ch005_security-domains.xml:48(para) +msgid "The trust level of this network is heavily dependent on deployment decisions and as such we do not assign this any default level of trust." +msgstr "" + +#: ./doc/security-guide/ch005_security-domains.xml:52(title) +msgid "Bridging Security Domains" +msgstr "" + +#: ./doc/security-guide/ch005_security-domains.xml:53(para) +msgid "A bridge is a component that exists inside more than one security domain. Any component that bridges security domains with different trust levels or authentication requirements must be carefully configured. These bridges are often the weak points in network architecture. A bridge should always be configured to meet the security requirements of the highest trust level of any of the domains it is bridging. In many cases the security controls for bridges should be a primary concern due to the likelihood of attack." +msgstr "" + +#: ./doc/security-guide/ch005_security-domains.xml:61(para) +msgid "The diagram above shows a compute node bridging the data and management domains, as such the compute node should be configured to meet the security requirements of the management domain. Similarly the API Endpoint in this diagram is bridging the untrusted public domain and the management domain, and should be configured to protect against attacks from the public domain propagating through to the management domain." +msgstr "" + +#: ./doc/security-guide/ch005_security-domains.xml:69(para) +msgid "In some cases deployers may want to consider securing a bridge to a higher standard than any of the domains in which it resides. Given the above example of an API endpoint, an adversary could potentially target the API endpoint from the public domain, leveraging it in the hopes of compromising or gaining access to the management domain." +msgstr "" + +#: ./doc/security-guide/ch005_security-domains.xml:70(para) +msgid "The design of OpenStack is such that separation of security domains is difficult - as core services will usually bridge at least two domains, special consideration must be given when applying security controls to them." +msgstr "" + +#: ./doc/security-guide/ch005_security-domains.xml:73(title) +msgid "Threat Classification, Actors and Attack Vectors" +msgstr "" + +#: ./doc/security-guide/ch005_security-domains.xml:74(para) +msgid "Most types of cloud deployment, public or private, are exposed to some form of attack. In this chapter we categorize attackers and summarize potential types of attacks in each security domain." +msgstr "" + +#: ./doc/security-guide/ch005_security-domains.xml:76(title) +msgid "Threat Actors" +msgstr "" + +#: ./doc/security-guide/ch005_security-domains.xml:77(para) +msgid "A threat actor is an abstract way to refer to a class of adversary that you may attempt to defend against. The more capable the actor, the more expensive the security controls that are required for successful attack mitigation and prevention. Security is a tradeoff between cost, usability and defense. In some cases it will not be possible to secure a cloud deployment against all of the threat actors we describe here. Those deploying an OpenStack cloud will have to decide where the balance lies for their deployment / usage." +msgstr "" + +#: ./doc/security-guide/ch005_security-domains.xml:79(para) +msgid "Intelligence Services — Considered by this guide as the most capable adversary. Intelligence Services and other state actors can bring tremendous resources to bear on a target. They have capabilities beyond that of any other actor. It is very difficult to defend against these actors without incredibly stringent controls in place, both human and technical." +msgstr "" + +#: ./doc/security-guide/ch005_security-domains.xml:82(para) +msgid "Serious Organized Crime — Highly capable and financially driven groups of attackers. Able to fund in-house exploit development and target research. In recent years the rise of organizations such as the Russian Business Network, a massive cyber-criminal enterprise has demonstrated how cyber attacks have become a commodity. Industrial espionage falls within the SOC group." +msgstr "" + +#: ./doc/security-guide/ch005_security-domains.xml:85(para) +msgid "Highly Capable Groups — This refers to 'Hacktivist' type organizations who are not typically commercially funded but can pose a serious threat to service providers and cloud operators." +msgstr "" + +#: ./doc/security-guide/ch005_security-domains.xml:88(para) +msgid "Motivated Individuals — Acting alone, these attackers come in many guises, such as rogue or malicious employees, disaffected customers, or small-scale industrial espionage." +msgstr "" + +#: ./doc/security-guide/ch005_security-domains.xml:91(para) +msgid "Script Kiddies — Automated vulnerability scanning/exploitation. Non-targeted attacks. Often only a nuisance, compromise by one of these actors presents a major risk to an organization's reputation." +msgstr "" + +#: ./doc/security-guide/ch005_security-domains.xml:103(title) +msgid "Public / Private Considerations" +msgstr "" + +#: ./doc/security-guide/ch005_security-domains.xml:104(para) +msgid "Private clouds are typically deployed by enterprises or institutions inside their networks and behind their firewalls. Enterprises will have strict policies on what data is allowed to exit their network and may even have different clouds for specific purposes. Users of a private cloud are typically employees of the organization that owns the cloud and are able to be held accountable for their actions. Employees often attend training sessions before accessing the cloud and will likely take part in regular scheduled security awareness training. Public clouds by contrast cannot make any assertions about their users, cloud use-cases or user motivations. This immediately pushes the guest security domain into a completely untrusted state for public cloud providers." +msgstr "" + +#: ./doc/security-guide/ch005_security-domains.xml:105(para) +msgid "A notable difference in the attack surface of public clouds is that they must provide internet access to their services. Instance connectivity, access to files over the internet and the ability to interact with the cloud controlling fabric such as the API endpoints and dashboard are must-haves for the public cloud." +msgstr "" + +#: ./doc/security-guide/ch005_security-domains.xml:106(para) +msgid "Privacy concerns for public and private cloud users are typically diametrically opposed. The data generated and stored in private clouds is normally owned by the operator of the cloud, who is able to deploy technologies such as data loss prevention (DLP) protection, file inspection, deep packet inspection and prescriptive firewalling. In contrast, privacy is one of the primary barriers to adoption for the public cloud, as many of these controls do not exist." +msgstr "" + +#: ./doc/security-guide/ch005_security-domains.xml:109(title) +msgid "Outbound attacks and reputational risk" +msgstr "" + +#: ./doc/security-guide/ch005_security-domains.xml:110(para) +msgid "Careful consideration should be given to potential outbound abuse from a cloud deployment.  Whether public or private, clouds tend to have lots of resource available. An attacker who has established a point of presence within the cloud, either through hacking in or via entitled access (rogue employee), can bring these resources to bear against the internet at large. Clouds with compute services make for ideal DDoS and brute force engines. This is perhaps a more pressing issue for public clouds as their users are largely unaccountable, and can quickly spin up numerous disposable instances for outbound attacks.  Major damage can be inflicted upon a company's reputation if it becomes known for hosting malicious software or launching attacks on other networks. Methods of prevention include egress security groups, outbound traffic inspection, customer education and awareness, and fraud and abuse mitigation strategies." +msgstr "" + +#: ./doc/security-guide/ch005_security-domains.xml:113(title) +msgid "Attack Types" +msgstr "" + +#: ./doc/security-guide/ch005_security-domains.xml:114(para) +msgid "The diagram shows the types of attacks that may be expected from the actors described in the previous section. Note that there will always be exceptions to this diagram but in general, this describes the sorts of attack that could be typical for each actor." +msgstr "" + +#: ./doc/security-guide/ch005_security-domains.xml:122(para) +msgid "The prescriptive defense for each form of attack is beyond the scope of this document. The above diagram can assist you in making an informed decision about which types of threats, and threat actors, should be protected against. For commercial public cloud deployments this might include prevention against serious crime. For those deploying private clouds for government use, more stringent protective mechanisms should be in place, including carefully protected facilities and supply chains. In contrast those standing up basic development or test environments will likely require less restrictive controls (middle of the spectrum)." +msgstr "" + +#: ./doc/security-guide/ch035_case-studies-networking.xml:3(title) +msgid "Case Studies: Networking" +msgstr "" + +#: ./doc/security-guide/ch035_case-studies-networking.xml:4(para) +msgid "In this case study we discuss how Alice and Bob would address providing networking services to the user." +msgstr "" + +#: ./doc/security-guide/ch035_case-studies-networking.xml:7(para) +msgid "A key objective of Alice's cloud is to integrate with the existing auth services and security resources. The key design parameters for this private cloud are a limited scope of tenants, networks and workload type. This environment can be designed to limit what available network resources are available to the tenant and what are the various default quotas and security policies are available. The network policy engine can be modified to restrict creation and changes to network resources. In this environment, Alice might want to leverage nova-network in the application of security group polices on a per instance basis vs. Neutron's application of security group polices on a per port basis. L2 isolation in this environment would leverage VLAN tagging. The use of VLAN tags will allow great visibility of tenant traffic by leveraging existing features and tools of the physical infrastructure." +msgstr "" + +#: ./doc/security-guide/ch035_case-studies-networking.xml:25(para) +msgid "A major business driver for Bob is to provide an advanced networking services to his customers. Bob's customers would like to deploy multi-tiered application stacks. This multi-tiered application are either existing enterprise application or newly deployed applications. Since Bob's public cloud is a multi-tenancy enterprise service, the choice to use for L2 isolation in this environment is to use overlay networking. Another aspect of Bob's cloud is the self-service aspect where the customer can provision available networking services as needed. These networking services encompass L2 networks, L3 Routing, Network ACL and NAT. It is important that per-tenant quota's be implemented in this environment." +msgstr "" + +#: ./doc/security-guide/ch035_case-studies-networking.xml:38(para) +msgid "An added benefit with utilizing OpenStack Networking is when new advanced networking services become available, these new features can be easily provided to the end customers." +msgstr "" + +#: ./doc/security-guide/ch011_management-introduction.xml:3(title) +msgid "Management Introduction" +msgstr "" + +#: ./doc/security-guide/ch011_management-introduction.xml:4(para) +msgid "A cloud deployment is a living system. Machines age and fail, software becomes outdated, vulnerabilities are discovered. When errors or omissions are made in configuration, or when software fixes must be applied, these changes must be made in a secure, but convenient, fashion. These changes are typically solved through configuration management." +msgstr "" + +#: ./doc/security-guide/ch011_management-introduction.xml:5(para) +msgid "Likewise, it is important to protect the cloud deployment from being configured or manipulated by malicious entities. With many systems in a cloud employing compute and networking virtualization, there are distinct challenges applicable to OpenStack which must be addressed through integrity lifecycle management." +msgstr "" + +#: ./doc/security-guide/ch011_management-introduction.xml:6(para) +msgid "Finally, administrators must perform command and control over the cloud for various operational functions. It is important these command and control facilities are understood and secured." +msgstr "" + +#: ./doc/security-guide/ch049_case-studies-tenant-data.xml:3(title) +msgid "Case Studies: Tenant Data" +msgstr "" + +#: ./doc/security-guide/ch049_case-studies-tenant-data.xml:4(para) +msgid "Returning to Alice and Bob, we will use this section to dive into their particular tenant data privacy requirements. Specifically, we will look into how Alice and Bob both handle tenant data, data destruction, and data encryption." +msgstr "" + +#: ./doc/security-guide/ch049_case-studies-tenant-data.xml:7(para) +msgid "As stated during the introduction to Alice's case study, data protection is of an extremely high priority. She needs to ensure that a compromise of one tenant's data does not cause loss of other tenant data. She also has strong regulator requirements that require documentation of data destruction activities. Alice does this using the following:" +msgstr "" + +#: ./doc/security-guide/ch049_case-studies-tenant-data.xml:15(para) +msgid "Establishing procedures to sanitize tenant data when a program or project ends" +msgstr "" + +#: ./doc/security-guide/ch049_case-studies-tenant-data.xml:16(para) +msgid "Track the destruction of both the tenant data and metadata via ticketing in a CMDB" +msgstr "" + +#: ./doc/security-guide/ch049_case-studies-tenant-data.xml:17(para) ./doc/security-guide/ch049_case-studies-tenant-data.xml:28(para) +msgid "For Volume storage:" +msgstr "" + +#: ./doc/security-guide/ch049_case-studies-tenant-data.xml:18(para) ./doc/security-guide/ch049_case-studies-tenant-data.xml:29(para) +msgid "Physical Server Issues" +msgstr "" + +#: ./doc/security-guide/ch049_case-studies-tenant-data.xml:19(para) +msgid "To provide secure ephemeral instance storage, Alice implements qcow2 files on an encrypted filesystem." +msgstr "" + +#: ./doc/security-guide/ch049_case-studies-tenant-data.xml:24(para) +msgid "As stated during the introduction to Bob's case study, tenant privacy is of an extremely high priority. In addition to the requirements and actions Bob will take to isolate tenants from one another at the infrastructure layer, Bob also needs to provide assurances for tenant data privacy. Bob does this using the following:" +msgstr "" + +#: ./doc/security-guide/ch049_case-studies-tenant-data.xml:26(para) +msgid "Establishing procedures to sanitize customer data when a customer churns" +msgstr "" + +#: ./doc/security-guide/ch049_case-studies-tenant-data.xml:27(para) +msgid "Track the destruction of both the customer data and metadata via ticketing in a CMDB" +msgstr "" + +#: ./doc/security-guide/ch049_case-studies-tenant-data.xml:30(para) +msgid "To provide secure ephemeral instance storage, Bob implements qcow2 files on an encrypted filesystems." +msgstr "" + +#: ./doc/security-guide/ch053_case-studies-instance-isolation.xml:3(title) +msgid "Case Studies: Instance Isolation" +msgstr "" + +#: ./doc/security-guide/ch053_case-studies-instance-isolation.xml:4(para) +msgid "In this case study we discuss how Alice and Bob would ensure that  their instances are properly isolated. First we consider hypervisor selection, and then techniques for hardening QEMU and applying mandatory access controls." +msgstr "" + +#: ./doc/security-guide/ch053_case-studies-instance-isolation.xml:7(para) +msgid "Alice chooses Xen for the hypervisor in her cloud due to a strong internal knowledge base and a desire to use the Xen security modules (XSM) for fine-grained policy enforcement." +msgstr "" + +#: ./doc/security-guide/ch053_case-studies-instance-isolation.xml:8(para) +msgid "Alice is willing to apply a relatively large amount of resources to software packaging and maintenance. She will use these resources to build a highly customized version of QEMU that has many components removed, thereby reducing the attack surface. She will also ensure that all compiler hardening options are enabled for QEMU. Alice accepts that these decisions will increase long-term maintenance costs." +msgstr "" + +#: ./doc/security-guide/ch053_case-studies-instance-isolation.xml:9(para) +msgid "Alice writes XSM policies (for Xen) and SELinux policies (for Linux domain 0, and device domains) to provide stronger isolation between the instances. Alice also uses the Intel TXT support in Xen to measure the hypervisor launch in the TPM." +msgstr "" + +#: ./doc/security-guide/ch053_case-studies-instance-isolation.xml:13(para) +msgid "Bob is very concerned about instance isolation since the users in a public cloud represent anyone with a credit card, meaning they are inherently untrusted. Bob has just started hiring the team that will deploy the cloud, so he can tailor his candidate search for specific areas of expertise. With this in mind, Bob chooses a hypervisor based on its technical features, certifications, and community support. KVM has an EAL 4+ common criteria rating, with a layered security protection profile (LSPP) to provide added assurance for instance isolation. This, combined with the strong support for KVM within the OpenStack community drives Bob's decision to use KVM." +msgstr "" + +#: ./doc/security-guide/ch053_case-studies-instance-isolation.xml:14(para) +msgid "Bob weighs the added cost of repackaging QEMU and decides that he cannot commit those resources to the project. Fortunately, his Linux distribution has already enabled the compiler hardening options. So he decides to use this QEMU package. Finally, Bob leverages sVirt to manage the SELinux polices associated with the virtualization stack." +msgstr "" + +#: ./doc/security-guide/ch034_tenant-secure-networking-best-practices.xml:3(title) +msgid "Networking Services Security Best Practices" +msgstr "" + +#: ./doc/security-guide/ch034_tenant-secure-networking-best-practices.xml:4(para) +msgid "This section discusses OpenStack Networking configuration best practices as they apply to tenant network security within your OpenStack deployment." +msgstr "" + +#: ./doc/security-guide/ch034_tenant-secure-networking-best-practices.xml:6(title) +msgid "Tenant Network Services Workflow" +msgstr "" + +#: ./doc/security-guide/ch034_tenant-secure-networking-best-practices.xml:7(para) +msgid "OpenStack Networking provides users real self services of network resources and configurations. It is important that Cloud Architects and Operators evaluate their design use cases in providing users the ability to create, update, and destroy available network resources." +msgstr "" + +#: ./doc/security-guide/ch034_tenant-secure-networking-best-practices.xml:10(title) +msgid "Networking Resource Policy Engine" +msgstr "" + +#: ./doc/security-guide/ch034_tenant-secure-networking-best-practices.xml:11(para) +msgid "A policy engine and its configuration file, policy.json, within OpenStack Networking provides a method to provide finer grained authorization of users on tenant networking methods and objects. It is important that cloud architects and operators evaluate their design and use cases in providing users and tenants the ability to create, update, and destroy available network resources as it has a tangible effect on tenant network availability, network security, and overall OpenStack security. For a more detailed explanation of OpenStack Networking policy definition, please refer to the Authentication and authorization section in the OpenStack Cloud Administrator Guide." +msgstr "" + +#: ./doc/security-guide/ch034_tenant-secure-networking-best-practices.xml:25(address) +msgid "It is important to review the default networking resource policy and modify the policy appropriately for your security posture." +msgstr "" + +#: ./doc/security-guide/ch034_tenant-secure-networking-best-practices.xml:26(para) +msgid "If your deployment of OpenStack provides multiple external access points into different security domains it is important that you limit the tenant's ability to attach multiple vNICs to multiple external access points -- this would bridge these security domains and could lead to unforeseen security compromise. It is possible mitigate this risk by utilizing the host aggregates functionality provided by OpenStack Compute or through splitting the tenant VMs into multiple tenant projects with different virtual network configurations." +msgstr "" + +#: ./doc/security-guide/ch034_tenant-secure-networking-best-practices.xml:29(title) +msgid "Security Groups" +msgstr "" + +#: ./doc/security-guide/ch034_tenant-secure-networking-best-practices.xml:30(para) +msgid "The OpenStack Networking Service provides security group functionality using a mechanism that is more flexible and powerful than the security group capabilities built into OpenStack Compute. Thus, when using OpenStack Networking, nova.conf should always disable built-in security groups and proxy all security group calls to the OpenStack Networking API. Failure to do so will result in conflicting security policies being simultaneously applied by both services. To proxy security groups to OpenStack Networking, use the following configuration values:" +msgstr "" + +#: ./doc/security-guide/ch034_tenant-secure-networking-best-practices.xml:32(para) +msgid "firewall_driver : must be set to 'nova.virt.firewall.NoopFirewallDriver' so that nova-compute does not perform iptables-based filtering itself." +msgstr "" + +#: ./doc/security-guide/ch034_tenant-secure-networking-best-practices.xml:35(para) +msgid "security_group_api : must be set to 'neutron' so that all security group requests are proxied to the OpenStack Network Service." +msgstr "" + +#: ./doc/security-guide/ch034_tenant-secure-networking-best-practices.xml:38(para) +msgid "Security groups and security group rules allow administrators and tenants the ability to specify the type of traffic and direction (ingress/egress) that is allowed to pass through a virtual interface port. A security group is a container for security group rules. When a virtual interface port is created in OpenStack Networking it is associated with a security group. If a security group is not specified, the port will be associated with a 'default' security group. By default this group will drop all ingress traffic and allow all egress. Rules can be added to this group in order to change the behaviour." +msgstr "" + +#: ./doc/security-guide/ch034_tenant-secure-networking-best-practices.xml:39(para) +msgid "When using the security group API through OpenStack Compute, security groups are applied to all virtual interface ports on an instance. The reason for this is that OpenStack Compute security group APIs are instance based and not virtual interface port based as OpenStack Networking." +msgstr "" + +#: ./doc/security-guide/ch034_tenant-secure-networking-best-practices.xml:42(title) +msgid "Quotas" +msgstr "" + +#: ./doc/security-guide/ch034_tenant-secure-networking-best-practices.xml:43(para) +msgid "Quotas provide the ability to limit the number of network resources available to tenants. You can enforce default quotas for all tenants." +msgstr "" + +#: ./doc/security-guide/ch034_tenant-secure-networking-best-practices.xml:70(para) +msgid "OpenStack Networking also supports per-tenant quotas limit via a quota extension API. To enable per-tenant quotas, you need to set quota_driver in neutron.conf." +msgstr "" + +#. When image changes, this message will be marked fuzzy or untranslated for you. +#. It doesn't matter what you translate it to: it's not used at all. +#: ./doc/security-guide/ch052_devices.xml:131(None) ./doc/security-guide/ch052_devices.xml:134(None) +msgid "@@image: 'static/sVirt Diagram 1.png'; md5=ffcdbb45d9054670ad4c270a7c7d3925" +msgstr "" + +#: ./doc/security-guide/ch052_devices.xml:3(title) +msgid "Hardening the Virtualization Layers" +msgstr "" + +#: ./doc/security-guide/ch052_devices.xml:4(para) +msgid "In the beginning of this chapter we discuss the use of both physical and virtual hardware by instances, the associated security risks, and some recommendations for mitigating those risks. We conclude the chapter with a discussion of sVirt, an open source project for integrating SELinux mandatory access controls with the virtualization components." +msgstr "" + +#: ./doc/security-guide/ch052_devices.xml:6(title) +msgid "Physical Hardware (PCI Passthrough)" +msgstr "" + +#: ./doc/security-guide/ch052_devices.xml:7(para) +msgid "Many hypervisors offer a functionality known as PCI passthrough. This allows an instance to have direct access to a piece of hardware on the node. For example, this could be used to allow instances to access video cards offering the compute unified device architecture (CUDA) for high performance computation. This feature carries two types of security risks: direct memory access and hardware infection." +msgstr "" + +#: ./doc/security-guide/ch052_devices.xml:8(para) +msgid "Direct memory access (DMA) is a feature that permits certain hardware devices to access arbitrary physical memory addresses in the host computer. Often video cards have this capability. However, an instance should not be given arbitrary physical memory access because this would give it full view of both the host system and other instances running on the same node. Hardware vendors use an input/output memory management unit (IOMMU) to manage DMA access in these situations. Therefore, cloud architects should ensure that the hypervisor is configured to utilize this hardware feature." +msgstr "" + +#: ./doc/security-guide/ch052_devices.xml:10(para) +msgid "KVM: How to assign devices with VT-d in KVM" +msgstr "" + +#: ./doc/security-guide/ch052_devices.xml:13(para) +msgid "Xen: VTd Howto" +msgstr "" + +#: ./doc/security-guide/ch052_devices.xml:17(para) +msgid "The IOMMU feature is marketed as VT-d by Intel and AMD-Vi by AMD." +msgstr "" + +#: ./doc/security-guide/ch052_devices.xml:19(para) +msgid "A hardware infection occurs when an instance makes a malicious modification to the firmware or some other part of a device. As this device is used by other instances, or even the host OS, the malicious code can spread into these systems. The end result is that one instance can run code outside of its security domain. This is a potential problem in any hardware sharing scenario. The problem is specific to this scenario because it is harder to reset the state of physical hardware than virtual hardware." +msgstr "" + +#: ./doc/security-guide/ch052_devices.xml:20(para) +msgid "Solutions to the hardware infection problem are domain specific. The strategy is to identify how an instance can modify hardware state then determine how to reset any modifications when the instance is done using the hardware. For example, one option could be to re-flash the firmware after use. Clearly there is a need to balance hardware longevity with security as some firmwares will fail after a large number of writes. TPM technology, described in link:Management/Node Bootstrapping, provides a solution for detecting unauthorized firmware changes. Regardless of the strategy selected, it is important to understand the risks associated with this kind of hardware sharing so that they can be properly mitigated for a given deployment scenario." +msgstr "" + +#: ./doc/security-guide/ch052_devices.xml:21(para) +msgid "Additionally, due to the risk and complexities associated with PCI passthrough, it should be disabled by default. If enabled for a specific need, you will need to have appropriate processes in place to ensure the hardware is clean before re-issue." +msgstr "" + +#: ./doc/security-guide/ch052_devices.xml:24(title) +msgid "Virtual Hardware (QEMU)" +msgstr "" + +#: ./doc/security-guide/ch052_devices.xml:25(para) +msgid "When running a virtual machine, virtual hardware is a software layer that provides the hardware interface for the virtual machine. Instances use this functionality to provide network, storage, video, and other devices that may be needed. With this in mind, most instances in your environment will exclusively use virtual hardware, with a minority that will require direct hardware access. The major open source hypervisors use QEMU for this functionality. While QEMU fills an important need for virtualization platforms, it has proven to be a very challenging software project to write and maintain. Much of the functionality in QEMU is implemented with low-level code that is difficult for most developers to comprehend. Furthermore, the hardware virtualized by QEMU includes many legacy devices that have their own set of quirks. Putting all of this together, QEMU has been the source of many security problems, including hypervisor breakout attacks." +msgstr "" + +#: ./doc/security-guide/ch052_devices.xml:41(para) +msgid "For the reasons stated above, it is important to take proactive steps to harden QEMU. We recommend three specific steps: minimizing the code base, using compiler hardening, and using mandatory access controls, such as sVirt, SELinux, or AppArmor." +msgstr "" + +#: ./doc/security-guide/ch052_devices.xml:47(title) +msgid "Minimizing the Qemu Code base" +msgstr "" + +#: ./doc/security-guide/ch052_devices.xml:48(para) +msgid "One classic security principle is to remove any unused components from your system. QEMU provides support for many different virtual hardware devices. However, only a small number of devices are needed for a given instance. Most instances will use the virtio devices. However, some legacy instances will need access to specific hardware, which can be specified using glance metadata:" +msgstr "" + +#: ./doc/security-guide/ch052_devices.xml:54(para) +msgid "A cloud architect should decide what devices to make available to cloud users. Anything that is not needed should be removed from QEMU. This step requires recompiling QEMU after modifying the options passed to the QEMU configure script. For a complete list of up-to-date options simply run ./configure --help from within the QEMU source directory. Decide what is needed for your deployment, and disable the remaining options." +msgstr "" + +#: ./doc/security-guide/ch052_devices.xml:57(title) +msgid "Compiler Hardening" +msgstr "" + +#: ./doc/security-guide/ch052_devices.xml:58(para) +msgid "The next step is to harden QEMU using compiler hardening options. Modern compilers provide a variety of compile time options to improve the security of the resulting binaries. These features, which we will describe in more detail below, include relocation read-only (RELRO), stack canaries, never execute (NX), position independent executable (PIE), and address space layout randomization (ASLR)." +msgstr "" + +#: ./doc/security-guide/ch052_devices.xml:59(para) +msgid "Many modern linux distributions already build QEMU with compiler hardening enabled, so you may want to verify your existing executable before proceeding with the information below. One tool that can assist you with this verification is called checksec.sh." +msgstr "" + +#: ./doc/security-guide/ch052_devices.xml:61(para) +msgid "RELocation Read-Only (RELRO): Hardens the data sections of an executable. Both full and partial RELRO modes are supported by gcc. For QEMU full RELRO is your best choice. This will make the global offset table read-only and place various internal data sections before the program data section in the resulting executable." +msgstr "" + +#: ./doc/security-guide/ch052_devices.xml:64(para) +msgid "Stack Canaries: Places values on the stack and verifies their presence to help prevent buffer overflow attacks." +msgstr "" + +#: ./doc/security-guide/ch052_devices.xml:67(para) +msgid "Never eXecute (NX): Also known as Data Execution Prevention (DEP), ensures that data sections of the executable can not be executed." +msgstr "" + +#: ./doc/security-guide/ch052_devices.xml:70(para) +msgid "Position Independent Executable (PIE): Produces a position independent executable, which is necessary for ASLR.  " +msgstr "" + +#: ./doc/security-guide/ch052_devices.xml:73(para) +msgid "Address Space Layout Randomization (ASLR) : This ensures that both code and data regions will be randomized. Enabled by the kernel (all modern linux kernels support ASLR), when the executable is built with PIE." +msgstr "" + +#: ./doc/security-guide/ch052_devices.xml:76(para) +msgid "Putting this all together, and adding in some additional useful protections, we recommend the following compiler options for gcc when compiling QEMU:" +msgstr "" + +#: ./doc/security-guide/ch052_devices.xml:79(para) +msgid "We recommend testing your QEMU executable file after it is compiled to ensure that the compiler hardening worked properly." +msgstr "" + +#: ./doc/security-guide/ch052_devices.xml:80(para) +msgid "Most cloud deployments will not want to build software such as QEMU by hand. It is better to use packaging to ensure that the process is repeatable and to ensure that the end result can be easily deployed throughout the cloud. The references below provide some additional details on applying compiler hardening options to existing packages." +msgstr "" + +#: ./doc/security-guide/ch052_devices.xml:82(para) +msgid "DEB packages: Hardening Walkthrough" +msgstr "" + +#: ./doc/security-guide/ch052_devices.xml:85(para) +msgid "RPM packages: How to create an RPM package" +msgstr "" + +#: ./doc/security-guide/ch052_devices.xml:91(para) +msgid "Compiler hardening makes it more difficult to attack the QEMU process. However, if an attacker does succeed, we would like to limit the impact of the attack. Mandatory access controls accomplish this by restricting the privileges on QEMU process to only what is needed. This can be accomplished using sVirt / SELinux or AppArmor. When using sVirt, SELinux is configured to run every QEMU process under a different security context. AppArmor can be configured to provide similar functionality. We provide more details on sVirt in the instance isolation section below." +msgstr "" + +#: ./doc/security-guide/ch052_devices.xml:95(title) +msgid "sVirt: SELinux + Virtualization" +msgstr "" + +#: ./doc/security-guide/ch052_devices.xml:96(para) +msgid "With unique kernel-level architecture and National Security Agency (NSA) developed security mechanisms, KVM provides foundational isolation technologies for multi tenancy. With developmental origins dating back to 2002, the Secure Virtualization (sVirt) technology is the application of SELinux against modern day virtualization. SELinux, which was designed to apply separation control based upon labels, has been extended to provide isolation between virtual machine processes, devices, data files and system processes acting upon their behalf." +msgstr "" + +#: ./doc/security-guide/ch052_devices.xml:105(para) +msgid "OpenStack's sVirt implementation aspires to protect hypervisor hosts and virtual machines against two primary threat vectors:" +msgstr "" + +#: ./doc/security-guide/ch052_devices.xml:107(para) +msgid "Hypervisor threats A compromised application running within a virtual machine attacks the hypervisor to access underlying resources. For example, the host OS, applications, or devices within the physical machine. This is a threat vector unique to virtualization and represents considerable risk as the underlying real machine can be compromised due to vulnerability in a single virtual application." +msgstr "" + +#: ./doc/security-guide/ch052_devices.xml:117(para) +msgid "Virtual Machine (multi-tenant) threats A compromised application running within a VM attacks the hypervisor to access/control another virtual machine and its resources. This is a threat vector unique to virtualization and represents considerable risk as a multitude of virtual machine file images could be compromised due to vulnerability in a single application. This virtual network attack is a major concern as the administrative techniques for protecting real networks do not directly apply to the virtual environment." +msgstr "" + +#: ./doc/security-guide/ch052_devices.xml:129(para) +msgid "Each KVM-based virtual machine is a process which is labeled by SELinux, effectively establishing a security boundary around each virtual machine. This security boundary is monitored and enforced by the Linux kernel, restricting the virtual machine's access to resources outside of its boundary such as host machine data files or other VMs." +msgstr "" + +#: ./doc/security-guide/ch052_devices.xml:137(para) +msgid "As shown above, sVirt isolation is provided regardless of the guest Operating System running inside the virtual machine -- Linux or Windows VMs can be used. Additionally, many Linux distributions provide SELinux within the operating system, allowing the virtual machine to protect internal virtual resources from threats. " +msgstr "" + +#: ./doc/security-guide/ch052_devices.xml:139(title) +msgid "Labels and Categories" +msgstr "" + +#: ./doc/security-guide/ch052_devices.xml:140(para) +msgid "KVM-based virtual machine instances are labelled with their own SELinux data type, known as svirt_image_t. Kernel level protections prevent unauthorized system processes, such as malware, from manipulating the virtual machine image files on disk. When virtual machines are powered off, images are stored as svirt_image_t as shown below:" +msgstr "" + +#: ./doc/security-guide/ch052_devices.xml:146(para) +msgid "The svirt_image_t label uniquely identifies image files on disk, allowing for the SELinux policy to restrict access. When a KVM-based Compute image is powered on, sVirt appends a random numerical identifier to the image. sVirt is technically capable of assigning numerical identifiers to 524,288 virtual machines per hypervisor node, however OpenStack deployments are highly unlikely to encounter this limitation." +msgstr "" + +#: ./doc/security-guide/ch052_devices.xml:147(para) +msgid "This example shows the sVirt category identifier:" +msgstr "" + +#: ./doc/security-guide/ch052_devices.xml:152(title) +msgid "Booleans" +msgstr "" + +#: ./doc/security-guide/ch052_devices.xml:153(para) +msgid "To ease the administrative burden of managing SELinux, many enterprise Linux platforms utilize SELinux Booleans to quickly change the security posture of sVirt." +msgstr "" + +#: ./doc/security-guide/ch052_devices.xml:154(para) +msgid "Red Hat Enterprise Linux-based KVM deployments utilize the following sVirt booleans:" +msgstr "" + +#: ./doc/security-guide/ch052_devices.xml:161(emphasis) +msgid "sVirt SELinux Boolean" +msgstr "" + +#: ./doc/security-guide/ch052_devices.xml:162(emphasis) +msgid " Description" +msgstr "" + +#: ./doc/security-guide/ch052_devices.xml:165(para) +msgid "virt_use_common" +msgstr "" + +#: ./doc/security-guide/ch052_devices.xml:166(para) +msgid "Allow virt to use serial/parallel communication ports." +msgstr "" + +#: ./doc/security-guide/ch052_devices.xml:169(para) +msgid "virt_use_fusefs" +msgstr "" + +#: ./doc/security-guide/ch052_devices.xml:170(para) +msgid "Allow virt to read FUSE mounted files." +msgstr "" + +#: ./doc/security-guide/ch052_devices.xml:173(para) +msgid "virt_use_nfs" +msgstr "" + +#: ./doc/security-guide/ch052_devices.xml:174(para) +msgid "Allow virt to manage NFS mounted files." +msgstr "" + +#: ./doc/security-guide/ch052_devices.xml:177(para) +msgid "virt_use_samba" +msgstr "" + +#: ./doc/security-guide/ch052_devices.xml:178(para) +msgid "Allow virt to manage CIFS mounted files." +msgstr "" + +#: ./doc/security-guide/ch052_devices.xml:181(para) +msgid "virt_use_sanlock" +msgstr "" + +#: ./doc/security-guide/ch052_devices.xml:182(para) +msgid "Allow confined virtual guests to interact with the sanlock." +msgstr "" + +#: ./doc/security-guide/ch052_devices.xml:185(para) +msgid "virt_use_sysfs" +msgstr "" + +#: ./doc/security-guide/ch052_devices.xml:186(para) +msgid "Allow virt to manage device configuration (PCI)." +msgstr "" + +#: ./doc/security-guide/ch052_devices.xml:189(para) +msgid "virt_use_usb" +msgstr "" + +#: ./doc/security-guide/ch052_devices.xml:190(para) +msgid "Allow virt to use USB devices." +msgstr "" + +#: ./doc/security-guide/ch052_devices.xml:193(para) +msgid "virt_use_xserver" +msgstr "" + +#: ./doc/security-guide/ch052_devices.xml:194(para) +msgid "Allow virtual machine to interact with the X Window System." +msgstr "" + +#: ./doc/security-guide/ch020_ssl-everywhere.xml:3(title) +msgid "SSL Proxies and HTTP Services" +msgstr "" + +#: ./doc/security-guide/ch020_ssl-everywhere.xml:4(para) +msgid "OpenStack endpoints are HTTP services providing APIs to both end-users on public networks and to other OpenStack services within the same deployment operating over the management network. It is highly recommended these requests, both those internal and external, operate over SSL." +msgstr "" + +#: ./doc/security-guide/ch020_ssl-everywhere.xml:5(para) +msgid "In order for API requests to be encrypted by SSL it's necessary to position the API services behind a proxy that will establish and terminate SSL sessions. The following table offers a non-exhaustive list of software services that can proxy SSL traffic for API requests:" +msgstr "" + +#: ./doc/security-guide/ch020_ssl-everywhere.xml:7(link) +msgid "Pound" +msgstr "" + +#: ./doc/security-guide/ch020_ssl-everywhere.xml:10(link) ./doc/security-guide/ch020_ssl-everywhere.xml:80(title) +msgid "Stud" +msgstr "" + +#: ./doc/security-guide/ch020_ssl-everywhere.xml:13(link) ./doc/security-guide/ch020_ssl-everywhere.xml:119(title) +msgid "nginx" +msgstr "" + +#: ./doc/security-guide/ch020_ssl-everywhere.xml:16(link) +msgid "Apache httpd" +msgstr "" + +#: ./doc/security-guide/ch020_ssl-everywhere.xml:19(para) +msgid "Hardware appliance SSL acceleration proxies" +msgstr "" + +#: ./doc/security-guide/ch020_ssl-everywhere.xml:22(para) +msgid "It is important to be mindful of the size of requests that will be processed by any chosen SSL proxy." +msgstr "" + +#: ./doc/security-guide/ch020_ssl-everywhere.xml:24(title) +msgid "Examples" +msgstr "" + +#: ./doc/security-guide/ch020_ssl-everywhere.xml:25(para) +msgid "Below we provide some sample configuration setting for enabling SSL in some of the most popular web servers/SSL terminators with recommended configurations. Note that we have SSL v3 enabled in some of these examples as this will be required in many deployments for client compatibility." +msgstr "" + +#: ./doc/security-guide/ch020_ssl-everywhere.xml:27(title) +msgid "Pound - with AES-NI acceleration" +msgstr "" + +#: ./doc/security-guide/ch020_ssl-everywhere.xml:81(para) +msgid "This stud example enables SSL v3 for client compatibility.  The ciphers line can be tweaked based on your needs, however this is a reasonable starting place." +msgstr "" + +#: ./doc/security-guide/ch020_ssl-everywhere.xml:120(para) +msgid "This nginx example requires TLS v1.1 or v1.2 for maximum security. The ssl_ciphers line can be tweaked based on your needs, however this is a reasonable starting place." +msgstr "" + +#: ./doc/security-guide/ch020_ssl-everywhere.xml:137(title) +msgid "Apache" +msgstr "" + +#: ./doc/security-guide/ch020_ssl-everywhere.xml:163(para) +msgid "Compute API SSL endpoint in Apache2, which needs to be paired with a short WSGI script." +msgstr "" + +#: ./doc/security-guide/ch020_ssl-everywhere.xml:188(title) +msgid "HTTP Strict Transport Security" +msgstr "" + +#: ./doc/security-guide/ch020_ssl-everywhere.xml:189(para) +msgid "We recommend that all production deployments use HSTS. This header prevents browsers from making insecure connections after they have made a single secure one. If you have deployed your HTTP services on a public or an untrusted domain, HSTS is especially important. To enable HSTS, configure your web server to send a header like this with all requests:" +msgstr "" + +#: ./doc/security-guide/ch020_ssl-everywhere.xml:192(para) +msgid "Start with a short timeout of 1 day during testing, and raise it to one year after testing has shown that you haven't introduced problems for users. Note that once this header is set to a large timeout, it is (by design) very difficult to disable." +msgstr "" + +#: ./doc/security-guide/ch058_forensicsincident-response.xml:3(title) +msgid "Forensics and Incident Response" +msgstr "" + +#: ./doc/security-guide/ch058_forensicsincident-response.xml:4(para) +msgid "A lot of activity goes on within a cloud environment. It is a mix of hardware, operating systems, virtual machine managers, the OpenStack services, cloud-user activity such as creating instances and attaching storage, the network underlying the whole, and finally end-users using the applications running on the various instances." +msgstr "" + +#: ./doc/security-guide/ch058_forensicsincident-response.xml:5(para) +msgid "The generation and collection of logs is an important component of securely monitoring an OpenStack infrastructure. Logs provide visibility into the day-to-day actions of administrators, tenants, and guests, in addition to the activity in the compute, networking, and storage and other components that comprise your OpenStack deployment." +msgstr "" + +#: ./doc/security-guide/ch058_forensicsincident-response.xml:6(para) +msgid "The basics of logging: configuration, setting log level, location of the log files, and how to use and customize logs, as well as how to do centralized collections of logs is well covered in the OpenStack Operations Guide." +msgstr "" + +#: ./doc/security-guide/ch058_forensicsincident-response.xml:7(para) +msgid "Logs are not only valuable for proactive security and continuous compliance activities, but they are also a valuable information  source for investigating and responding to incidents." +msgstr "" + +#: ./doc/security-guide/ch058_forensicsincident-response.xml:8(para) +msgid "For instance, analyzing the access logs of Identity Service or its replacement authentication system would alert us to failed logins, their frequency, origin IP, whether the events are restricted to select accounts etc. Log analysis supports detection." +msgstr "" + +#: ./doc/security-guide/ch058_forensicsincident-response.xml:9(para) +msgid "On detection, further action may be to black list an IP, or recommend strengthening user passwords, or even de-activating a user account if it is deemed dormant." +msgstr "" + +#: ./doc/security-guide/ch058_forensicsincident-response.xml:11(title) +msgid "Monitoring Use Cases" +msgstr "" + +#: ./doc/security-guide/ch058_forensicsincident-response.xml:12(para) +msgid "Monitoring events is more pro-active and provides real-time detection and response.  There are several tools to aid in monitoring." +msgstr "" + +#: ./doc/security-guide/ch058_forensicsincident-response.xml:13(para) +msgid "In the case of an OpenStack cloud instance, we need to monitor the hardware, the OpenStack services, and the cloud resource usage. The last stems from wanting to be elastic, to scale to the dynamic needs of the users." +msgstr "" + +#: ./doc/security-guide/ch058_forensicsincident-response.xml:14(para) +msgid "Here are a few important use cases to consider when implementing log aggregation, analysis and monitoring. These use cases can be implemented and monitored through various commercial and open source tools, homegrown scripts, etc. These tools and scripts can generate events that can then be sent to the administrators through email or integrated dashboard. It is important to consider additional use cases that may apply to your specific network and what you may consider anomalous behavior." +msgstr "" + +#: ./doc/security-guide/ch058_forensicsincident-response.xml:16(para) +msgid "Detecting the absence of log generation is an event of high value. Such an event would indicate a service failure or even an intruder who has temporarily switched off logging or modified the log level to hide their tracks." +msgstr "" + +#: ./doc/security-guide/ch058_forensicsincident-response.xml:20(para) +msgid "Application events such as start and/or stop that were unscheduled would also be events to monitor and examine for possible security implications." +msgstr "" + +#: ./doc/security-guide/ch058_forensicsincident-response.xml:24(para) +msgid "OS events on the OpenStack service machines such as user logins, restarts also provide valuable insight into use/misuse" +msgstr "" + +#: ./doc/security-guide/ch058_forensicsincident-response.xml:28(para) +msgid "Being able to detect the load on the OpenStack servers also enables responding by way of introducing additional servers for load balancing to ensure high availability." +msgstr "" + +#: ./doc/security-guide/ch058_forensicsincident-response.xml:32(para) +msgid "Other events that are actionable are networking bridges going down, ip tables being flushed on compute nodes and consequential loss of access to instances resulting in unhappy customers. " +msgstr "" + +#: ./doc/security-guide/ch058_forensicsincident-response.xml:36(para) +msgid "To reduce security risks from orphan instances on a user/tenant/domain deletion in the Identity service there is discussion to generate notifications in the system and have OpenStack components respond to these events as appropriate such as terminating instances, disconnecting attached volumes, reclaiming CPU and storage resources etc. " +msgstr "" + +#: ./doc/security-guide/ch058_forensicsincident-response.xml:39(para) +msgid "A cloud will host many virtual instances, and monitoring these instances goes beyond hardware monitoring and log files which may just contain CRUD events." +msgstr "" + +#: ./doc/security-guide/ch058_forensicsincident-response.xml:40(para) +msgid "Security monitoring controls such as intrusion detection software, antivirus software, and spyware detection and removal utilities can generate logs that show when and how an attack or intrusion took place. Deploying these tools on the cloud machines provides value and protection. Cloud users, those running instances on the cloud may also want to run such tools on their instances." +msgstr "" + +#: ./doc/security-guide/ch058_forensicsincident-response.xml:44(link) +msgid "http://www.mirantis.com/blog/openstack-monitoring/" +msgstr "" + +#: ./doc/security-guide/ch058_forensicsincident-response.xml:45(link) +msgid "http://blog.sflow.com/2012/01/host-sflow-distributed-agent.html" +msgstr "" + +#: ./doc/security-guide/ch058_forensicsincident-response.xml:46(link) +msgid "http://blog.sflow.com/2009/09/lan-and-wan.html" +msgstr "" + +#: ./doc/security-guide/ch058_forensicsincident-response.xml:47(link) +msgid "http://blog.sflow.com/2013/01/rapidly-detecting-large-flows-sflow-vs.html" +msgstr "" + +#. Put one translator per line, in the form of NAME , YEAR1, YEAR2 +#: ./doc/security-guide/ch058_forensicsincident-response.xml:0(None) +msgid "translator-credits" +msgstr "" + diff --git a/doc/training-guides/locale/he_IL.po b/doc/training-guides/locale/he_IL.po new file mode 100644 index 0000000000..c24530c335 --- /dev/null +++ b/doc/training-guides/locale/he_IL.po @@ -0,0 +1,13912 @@ +# +# Translators: +msgid "" +msgstr "" +"Project-Id-Version: OpenStack Manuals\n" +"POT-Creation-Date: 2014-01-30 06:24+0000\n" +"PO-Revision-Date: 2014-01-27 06:38+0000\n" +"Last-Translator: openstackjenkins \n" +"Language-Team: Hebrew (Israel) (http://www.transifex.com/projects/p/openstack/language/he_IL/)\n" +"MIME-Version: 1.0\n" +"Content-Type: text/plain; charset=UTF-8\n" +"Content-Transfer-Encoding: 8bit\n" +"Language: he_IL\n" +"Plural-Forms: nplurals=2; plural=(n != 1);\n" + +#: ./doc/training-guides/module002-ch005-floating-ips.xml7(title) +msgid "Floating IP Addresses And Security Rules" +msgstr "" + +#: ./doc/training-guides/module002-ch005-floating-ips.xml8(para) +msgid "" +"OpenStack Networking has the concept of Fixed IPs and Floating IPs. Fixed " +"IPs are assigned to an instance on creation and stay the same until the " +"instance is explicitly terminated. Floating ips are ip addresses that can be" +" dynamically associated with an instance. This address can be disassociated " +"and associated with another instance at any time." +msgstr "" + +#: ./doc/training-guides/module002-ch005-floating-ips.xml15(para) +msgid "Various tasks carried out by Floating IP's as of now." +msgstr "" + +#: ./doc/training-guides/module002-ch005-floating-ips.xml19(para) +msgid "create IP ranges under a certain group, only available for admin role." +msgstr "" + +#: ./doc/training-guides/module002-ch005-floating-ips.xml23(para) +msgid "" +"allocate an floating IP to a certain tenant, only available for admin role." +msgstr "" + +#: ./doc/training-guides/module002-ch005-floating-ips.xml27(para) +msgid "deallocate an floating IP from a certain tenant" +msgstr "" + +#: ./doc/training-guides/module002-ch005-floating-ips.xml31(para) +msgid "associate an floating IP to a given instance" +msgstr "" + +#: ./doc/training-guides/module002-ch005-floating-ips.xml35(para) +msgid "disassociate an floating IP from a certain instance" +msgstr "" + +#: ./doc/training-guides/module002-ch005-floating-ips.xml39(para) +msgid "" +"Just as shown by the above figure, we will have nova-network-api to support " +"nova client floating commands. nova-network-api will invoke neutron cli lib " +"to interactive with neutron server via API. The data about floating IPs will" +" be stored in to neutron DB. Neutron Agent, which is running on compute host" +" will enforce the floating IP." +msgstr "" + +#: ./doc/training-guides/module002-ch005-floating-ips.xml46(guilabel) +msgid "Multiple Floating IP Pools" +msgstr "" + +#: ./doc/training-guides/module002-ch005-floating-ips.xml48(para) +msgid "" +"The L3 API in OpenStack Networking supports multiple floating IP pools. In " +"OpenStack Networking, a floating IP pool is represented as an external " +"network and a floating IP is allocated from a subnet associated with the " +"external network. Since each L3 agent can be associated with at most one " +"external network, we need to invoke multiple L3 agent to define multiple " +"floating IP pools. 'gateway_external_network_id'in L3 agent configuration " +"file indicates the external network that the L3 agent handles. You can run " +"multiple L3 agent instances on one host." +msgstr "" + +#: ./doc/training-guides/module002-ch005-floating-ips.xml59(para) +msgid "" +"In addition, when you run multiple L3 agents, make sure that " +"handle_internal_only_routers is set to Trueonly for one L3 agent in an " +"OpenStack Networking deployment and set to Falsefor all other L3 agents. " +"Since the default value of this parameter is True, you need to configure it " +"carefully." +msgstr "" + +#: ./doc/training-guides/module002-ch005-floating-ips.xml65(para) +msgid "" +"Before starting L3 agents, you need to create routers and external networks," +" then update the configuration files with UUID of external networks and " +"start L3 agents." +msgstr "" + +#: ./doc/training-guides/module002-ch005-floating-ips.xml69(para) +msgid "" +"For the first agent, invoke it with the following l3_agent.ini where " +"handle_internal_only_routers is True." +msgstr "" + +#: ./doc/training-guides/bk002-ch009-operator-compute-node-quiz.xml6(title) +#: ./doc/training-guides/bk001-ch006-associate-compute-node-quiz.xml6(title) +msgid "Compute Node Quiz" +msgstr "" + +#: ./doc/training-guides/bk002-ch009-operator-compute-node-quiz.xml8(title) +msgid "Days 5 to 6, 16:40 to 17:00" +msgstr "" + +#: ./doc/training-guides/module003-ch006-more-concepts.xml7(title) +msgid "A Bit More On Swift" +msgstr "" + +#: ./doc/training-guides/module003-ch006-more-concepts.xml8(guilabel) +msgid "Containers and Objects" +msgstr "" + +#: ./doc/training-guides/module003-ch006-more-concepts.xml9(para) +msgid "" +"A container is a storage compartment for your data and provides a way for " +"you to organize your data. You can think of a container as a folder in " +"Windows or a directory in UNIX. The primary difference between a container " +"and these other file system concepts is that containers cannot be nested. " +"You can, however, create an unlimited number of containers within your " +"account. Data must be stored in a container so you must have at least one " +"container defined in your account prior to uploading data." +msgstr "" + +#: ./doc/training-guides/module003-ch006-more-concepts.xml19(para) +msgid "" +"The only restrictions on container names is that they cannot contain a " +"forward slash (/) or an ascii null (%00) and must be less than 257 bytes in " +"length. Please note that the length restriction applies to the name after it" +" has been URL encoded. For example, a container name of Course Docs would be" +" URL encoded as Course%20Docs and therefore be 13 bytes in length rather " +"than the expected 11." +msgstr "" + +#: ./doc/training-guides/module003-ch006-more-concepts.xml27(para) +msgid "" +"An object is the basic storage entity and any optional metadata that " +"represents the files you store in the OpenStack Object Storage system. When " +"you upload data to OpenStack Object Storage, the data is stored as-is (no " +"compression or encryption) and consists of a location (container), the " +"object's name, and any metadata consisting of key/value pairs. For instance," +" you may chose to store a backup of your digital photos and organize them " +"into albums. In this case, each object could be tagged with metadata such as" +" Album : Caribbean Cruise or Album : Aspen Ski Trip." +msgstr "" + +#: ./doc/training-guides/module003-ch006-more-concepts.xml38(para) +msgid "" +"The only restriction on object names is that they must be less than 1024 " +"bytes in length after URL encoding. For example, an object name of " +"C++final(v2).txt should be URL encoded as C%2B%2Bfinal%28v2%29.txt and " +"therefore be 24 bytes in length rather than the expected 16." +msgstr "" + +#: ./doc/training-guides/module003-ch006-more-concepts.xml43(para) +msgid "" +"The maximum allowable size for a storage object upon upload is 5 gigabytes " +"(GB) and the minimum is zero bytes. You can use the built-in large object " +"support and the swift utility to retrieve objects larger than 5 GB." +msgstr "" + +#: ./doc/training-guides/module003-ch006-more-concepts.xml47(para) +msgid "" +"For metadata, you should not exceed 90 individual key/value pairs for any " +"one object and the total byte length of all key/value pairs should not " +"exceed 4KB (4096 bytes)." +msgstr "" + +#: ./doc/training-guides/module003-ch006-more-concepts.xml51(guilabel) +msgid "Language-Specific API Bindings" +msgstr "" + +#: ./doc/training-guides/module003-ch006-more-concepts.xml53(para) +msgid "" +"A set of supported API bindings in several popular languages are available " +"from the Rackspace Cloud Files product, which uses OpenStack Object Storage " +"code for its implementation. These bindings provide a layer of abstraction " +"on top of the base REST API, allowing programmers to work with a container " +"and object model instead of working directly with HTTP requests and " +"responses. These bindings are free (as in beer and as in speech) to " +"download, use, and modify. They are all licensed under the MIT License as " +"described in the COPYING file packaged with each binding. If you do make any" +" improvements to an API, you are encouraged (but not required) to submit " +"those changes back to us." +msgstr "" + +#: ./doc/training-guides/module003-ch006-more-concepts.xml66(para) +msgid "" +"The API bindings for Rackspace Cloud Files are hosted athttp://github.com/rackspace. " +"Feel free to coordinate your changes through github or, if you prefer, send " +"your changes to cloudfiles@rackspacecloud.com. Just make sure to indicate " +"which language and version you modified and send a unified diff." +msgstr "" + +#: ./doc/training-guides/module003-ch006-more-concepts.xml75(para) +msgid "" +"Each binding includes its own documentation (either HTML, PDF, or CHM). They" +" also include code snippets and examples to help you get started. The " +"currently supported API binding for OpenStack Object Storage are:" +msgstr "" + +#: ./doc/training-guides/module003-ch006-more-concepts.xml81(para) +msgid "PHP (requires 5.x and the modules: cURL, FileInfo, mbstring)" +msgstr "" + +#: ./doc/training-guides/module003-ch006-more-concepts.xml85(para) +msgid "Python (requires 2.4 or newer)" +msgstr "" + +#: ./doc/training-guides/module003-ch006-more-concepts.xml88(para) +msgid "Java (requires JRE v1.5 or newer)" +msgstr "" + +#: ./doc/training-guides/module003-ch006-more-concepts.xml91(para) +msgid "C#/.NET (requires .NET Framework v3.5)" +msgstr "" + +#: ./doc/training-guides/module003-ch006-more-concepts.xml94(para) +msgid "Ruby (requires 1.8 or newer and mime-tools module)" +msgstr "" + +#: ./doc/training-guides/module003-ch006-more-concepts.xml98(para) +msgid "" +"There are no other supported language-specific bindings at this time. You " +"are welcome to create your own language API bindings and we can help answer " +"any questions during development, host your code if you like, and give you " +"full credit for your work." +msgstr "" + +#: ./doc/training-guides/module003-ch006-more-concepts.xml103(guilabel) +msgid "Proxy Server" +msgstr "" + +#: ./doc/training-guides/module003-ch006-more-concepts.xml104(para) +msgid "" +"The Proxy Server is responsible for tying together the rest of the OpenStack" +" Object Storage architecture. For each request, it will look up the location" +" of the account, container, or object in the ring (see below) and route the " +"request accordingly. The public API is also exposed through the Proxy " +"Server." +msgstr "" + +#: ./doc/training-guides/module003-ch006-more-concepts.xml110(para) +msgid "" +"A large number of failures are also handled in the Proxy Server. For " +"example, if a server is unavailable for an object PUT, it will ask the ring " +"for a hand-off server and route there instead." +msgstr "" + +#: ./doc/training-guides/module003-ch006-more-concepts.xml114(para) +msgid "" +"When objects are streamed to or from an object server, they are streamed " +"directly through the proxy server to or from the user – the proxy server " +"does not spool them." +msgstr "" + +#: ./doc/training-guides/module003-ch006-more-concepts.xml118(para) +msgid "" +"You can use a proxy server with account management enabled by configuring it" +" in the proxy server configuration file." +msgstr "" + +#: ./doc/training-guides/module003-ch006-more-concepts.xml121(guilabel) +msgid "Object Server" +msgstr "" + +#: ./doc/training-guides/module003-ch006-more-concepts.xml122(para) +msgid "" +"The Object Server is a very simple blob storage server that can store, " +"retrieve and delete objects stored on local devices. Objects are stored as " +"binary files on the filesystem with metadata stored in the file’s extended " +"attributes (xattrs). This requires that the underlying filesystem choice for" +" object servers support xattrs on files. Some filesystems, like ext3, have " +"xattrs turned off by default." +msgstr "" + +#: ./doc/training-guides/module003-ch006-more-concepts.xml130(para) +msgid "" +"Each object is stored using a path derived from the object name’s hash and " +"the operation’s timestamp. Last write always wins, and ensures that the " +"latest object version will be served. A deletion is also treated as a " +"version of the file (a 0 byte file ending with “.ts”, which stands for " +"tombstone). This ensures that deleted files are replicated correctly and " +"older versions don’t magically reappear due to failure scenarios." +msgstr "" + +#: ./doc/training-guides/module003-ch006-more-concepts.xml139(guilabel) +msgid "Container Server" +msgstr "" + +#: ./doc/training-guides/module003-ch006-more-concepts.xml140(para) +msgid "" +"The Container Server’s primary job is to handle listings of objects. It does" +" not’t know where those objects are, just what objects are in a specific " +"container. The listings are stored as sqlite database files, and replicated " +"across the cluster similar to how objects are. Statistics are also tracked " +"that include the total number of objects, and total storage usage for that " +"container." +msgstr "" + +#: ./doc/training-guides/module003-ch006-more-concepts.xml148(guilabel) +msgid "Account Server" +msgstr "" + +#: ./doc/training-guides/module003-ch006-more-concepts.xml149(para) +msgid "" +"The Account Server is very similar to the Container Server, excepting that " +"it is responsible for listings of containers rather than objects." +msgstr "" + +#: ./doc/training-guides/module003-ch006-more-concepts.xml152(guilabel) +#: ./doc/training-guides/module003-ch004-swift-building-blocks.xml225(guilabel) +#: ./doc/training-guides/module003-ch004-swift-building-blocks.xml249(title) +#: ./doc/training-guides/module003-ch009-replication.xml7(title) +msgid "Replication" +msgstr "" + +#: ./doc/training-guides/module003-ch006-more-concepts.xml153(para) +msgid "" +"Replication is designed to keep the system in a consistent state in the face" +" of temporary error conditions like network outages or drive failures." +msgstr "" + +#: ./doc/training-guides/module003-ch006-more-concepts.xml157(para) +msgid "" +"The replication processes compare local data with each remote copy to ensure" +" they all contain the latest version. Object replication uses a hash list to" +" quickly compare subsections of each partition, and container and account " +"replication use a combination of hashes and shared high water marks." +msgstr "" + +#: ./doc/training-guides/module003-ch006-more-concepts.xml163(para) +msgid "" +"Replication updates are push based. For object replication, updating is just" +" a matter of rsyncing files to the peer. Account and container replication " +"push missing records over HTTP or rsync whole database files." +msgstr "" + +#: ./doc/training-guides/module003-ch006-more-concepts.xml168(para) +msgid "" +"The replicator also ensures that data is removed from the system. When an " +"item (object, container, or account) is deleted, a tombstone is set as the " +"latest version of the item. The replicator will see the tombstone and ensure" +" that the item is removed from the entire system." +msgstr "" + +#: ./doc/training-guides/module003-ch006-more-concepts.xml174(para) +msgid "" +"To separate the cluster-internal replication traffic from client traffic, " +"separate replication servers can be used. These replication servers are " +"based on the standard storage servers, but they listen on the replication IP" +" and only respond to REPLICATE requests. Storage servers can serve REPLICATE" +" requests, so an operator can transition to using a separate replication " +"network with no cluster downtime." +msgstr "" + +#: ./doc/training-guides/module003-ch006-more-concepts.xml182(para) +msgid "" +"Replication IP and port information is stored in the ring on a per-node " +"basis. These parameters will be used if they are present, but they are not " +"required. If this information does not exist or is empty for a particular " +"node, the node's standard IP and port will be used for replication." +msgstr "" + +#: ./doc/training-guides/module003-ch006-more-concepts.xml188(guilabel) +msgid "Updaters" +msgstr "" + +#: ./doc/training-guides/module003-ch006-more-concepts.xml189(para) +msgid "" +"There are times when container or account data can not be immediately " +"updated. This usually occurs during failure scenarios or periods of high " +"load. If an update fails, the update is queued locally on the file system, " +"and the updater will process the failed updates. This is where an eventual " +"consistency window will most likely come in to play. For example, suppose a " +"container server is under load and a new object is put in to the system. The" +" object will be immediately available for reads as soon as the proxy server " +"responds to the client with success. However, the container server did not " +"update the object listing, and so the update would be queued for a later " +"update. Container listings, therefore, may not immediately contain the " +"object." +msgstr "" + +#: ./doc/training-guides/module003-ch006-more-concepts.xml204(para) +msgid "" +"In practice, the consistency window is only as large as the frequency at " +"which the updater runs and may not even be noticed as the proxy server will " +"route listing requests to the first container server which responds. The " +"server under load may not be the one that serves subsequent listing requests" +" – one of the other two replicas may handle the listing." +msgstr "" + +#: ./doc/training-guides/module003-ch006-more-concepts.xml211(guilabel) +msgid "Auditors" +msgstr "" + +#: ./doc/training-guides/module003-ch006-more-concepts.xml212(para) +msgid "" +"Auditors crawl the local server checking the integrity of the objects, " +"containers, and accounts. If corruption is found (in the case of bit rot, " +"for example), the file is quarantined, and replication will replace the bad " +"file from another replica. If other errors are found they are logged. For " +"example, an object’s listing cannot be found on any container server it " +"should be." +msgstr "" + +#. When image changes, this message will be marked fuzzy or untranslated for +#. you. +#. It doesn't matter what you translate it to: it's not used at all. +#: ./doc/training-guides/module003-ch007-swift-cluster-architecture.xml13(None) +msgid "@@image: 'figures/image47.png'; md5=90f6c7cf3947d7987eeb55d657cdc927" +msgstr "" + +#. When image changes, this message will be marked fuzzy or untranslated for +#. you. +#. It doesn't matter what you translate it to: it's not used at all. +#: ./doc/training-guides/module003-ch007-swift-cluster-architecture.xml57(None) +msgid "@@image: 'figures/image48.png'; md5=2aa7eb3bddcf6826f33469920dc2a9c3" +msgstr "" + +#: ./doc/training-guides/module003-ch007-swift-cluster-architecture.xml7(title) +msgid "Cluster Arch" +msgstr "" + +#: ./doc/training-guides/module003-ch007-swift-cluster-architecture.xml8(guilabel) +msgid "Access Tier" +msgstr "" + +#: ./doc/training-guides/module003-ch007-swift-cluster-architecture.xml10(title) +#: ./doc/training-guides/bk002-ch013-operator-object-storage-node.xml59(title) +msgid "Swift Cluster Architecture" +msgstr "" + +#: ./doc/training-guides/module003-ch007-swift-cluster-architecture.xml17(para) +msgid "" +"Large-scale deployments segment off an \"Access Tier\". This tier is the " +"“Grand Central” of the Object Storage system. It fields incoming API " +"requests from clients and moves data in and out of the system. This tier is " +"composed of front-end load balancers, ssl- terminators, authentication " +"services, and it runs the (distributed) brain of the object storage system —" +" the proxy server processes." +msgstr "" + +#: ./doc/training-guides/module003-ch007-swift-cluster-architecture.xml25(para) +msgid "" +"Having the access servers in their own tier enables read/write access to be " +"scaled out independently of storage capacity. For example, if the cluster is" +" on the public Internet and requires ssl-termination and has high demand for" +" data access, many access servers can be provisioned. However, if the " +"cluster is on a private network and it is being used primarily for archival " +"purposes, fewer access servers are needed." +msgstr "" + +#: ./doc/training-guides/module003-ch007-swift-cluster-architecture.xml33(para) +msgid "" +"As this is an HTTP addressable storage service, a load balancer can be " +"incorporated into the access tier." +msgstr "" + +#: ./doc/training-guides/module003-ch007-swift-cluster-architecture.xml35(para) +msgid "" +"Typically, this tier comprises a collection of 1U servers. These machines " +"use a moderate amount of RAM and are network I/O intensive. As these systems" +" field each incoming API request, it is wise to provision them with two " +"high-throughput (10GbE) interfaces. One interface is used for 'front-end' " +"incoming requests and the other for 'back-end' access to the object storage " +"nodes to put and fetch data." +msgstr "" + +#: ./doc/training-guides/module003-ch007-swift-cluster-architecture.xml43(guilabel) +#: ./doc/training-guides/module003-ch007-swift-cluster-architecture.xml77(guilabel) +msgid "Factors to Consider" +msgstr "" + +#: ./doc/training-guides/module003-ch007-swift-cluster-architecture.xml44(para) +msgid "" +"For most publicly facing deployments as well as private deployments " +"available across a wide-reaching corporate network, SSL will be used to " +"encrypt traffic to the client. SSL adds significant processing load to " +"establish sessions between clients; more capacity in the access layer will " +"need to be provisioned. SSL may not be required for private deployments on " +"trusted networks." +msgstr "" + +#: ./doc/training-guides/module003-ch007-swift-cluster-architecture.xml52(guilabel) +msgid "Storage Nodes" +msgstr "" + +#: ./doc/training-guides/module003-ch007-swift-cluster-architecture.xml54(title) +msgid "Object Storage (Swift)" +msgstr "" + +#: ./doc/training-guides/module003-ch007-swift-cluster-architecture.xml61(para) +msgid "" +"The next component is the storage servers themselves. Generally, most " +"configurations should have each of the five Zones with an equal amount of " +"storage capacity. Storage nodes use a reasonable amount of memory and CPU. " +"Metadata needs to be readily available to quickly return objects. The object" +" stores run services not only to field incoming requests from the Access " +"Tier, but to also run replicators, auditors, and reapers. Object stores can " +"be provisioned with single gigabit or 10 gigabit network interface depending" +" on expected workload and desired performance." +msgstr "" + +#: ./doc/training-guides/module003-ch007-swift-cluster-architecture.xml72(para) +msgid "" +"Currently 2TB or 3TB SATA disks deliver good price/performance value. " +"Desktop-grade drives can be used where there are responsive remote hands in " +"the datacenter, and enterprise-grade drives can be used where this is not " +"the case." +msgstr "" + +#: ./doc/training-guides/module003-ch007-swift-cluster-architecture.xml78(para) +msgid "" +"Desired I/O performance for single-threaded requests should be kept in mind." +" This system does not use RAID, so each request for an object is handled by " +"a single disk. Disk performance impacts single-threaded response rates." +msgstr "" + +#: ./doc/training-guides/module003-ch007-swift-cluster-architecture.xml83(para) +msgid "" +"To achieve apparent higher throughput, the object storage system is designed" +" with concurrent uploads/downloads in mind. The network I/O capacity (1GbE, " +"bonded 1GbE pair, or 10GbE) should match your desired concurrent throughput " +"needs for reads and writes." +msgstr "" + +#. When image changes, this message will be marked fuzzy or untranslated for +#. you. +#. It doesn't matter what you translate it to: it's not used at all. +#: ./doc/training-guides/module002-ch001-networking-in-openstack.xml230(None) +msgid "@@image: 'figures/image33.png'; md5=e9843f38c9b2555e709357a724fc710d" +msgstr "" + +#: ./doc/training-guides/module002-ch001-networking-in-openstack.xml7(title) +#: ./doc/training-guides/module002-ch001-networking-in-openstack.xml8(guilabel) +#: ./doc/training-guides/module002-ch000-openstack-networking.xml9(title) +#: ./doc/training-guides/bk001-ch007-associate-network-node.xml14(title) +msgid "Networking in OpenStack" +msgstr "" + +#: ./doc/training-guides/module002-ch001-networking-in-openstack.xml9(para) +msgid "" +"OpenStack Networking provides a rich tenant-facing API for defining network " +"connectivity and addressing in the cloud. The OpenStack Networking project " +"gives operators the ability to leverage different networking technologies to" +" power their cloud networking. It is a virtual network service that provides" +" a powerful API to define the network connectivity and addressing used by " +"devices from other services, such as OpenStack Compute. It has a rich API " +"which consists of the following components." +msgstr "" + +#: ./doc/training-guides/module002-ch001-networking-in-openstack.xml20(para) +msgid "" +"Network: An isolated L2 segment, " +"analogous to VLAN in the physical networking world." +msgstr "" + +#: ./doc/training-guides/module002-ch001-networking-in-openstack.xml25(para) +msgid "" +"Subnet: A block of v4 or v6 IP addresses " +"and associated configuration state." +msgstr "" + +#: ./doc/training-guides/module002-ch001-networking-in-openstack.xml30(para) +msgid "" +"Port: A connection point for attaching a " +"single device, such as the NIC of a virtual server, to a virtual network. " +"Also describes the associated network configuration, such as the MAC and IP " +"addresses to be used on that port." +msgstr "" + +#: ./doc/training-guides/module002-ch001-networking-in-openstack.xml38(para) +msgid "" +"You can configure rich network topologies by creating and configuring " +"networks and subnets, and then instructing other OpenStack services like " +"OpenStack Compute to attach virtual devices to ports on these networks. In " +"particular, OpenStack Networking supports each tenant having multiple " +"private networks, and allows tenants to choose their own IP addressing " +"scheme, even if those IP addresses overlap with those used by other tenants." +" This enables very advanced cloud networking use cases, such as building " +"multi-tiered web applications and allowing applications to be migrated to " +"the cloud without changing IP addresses." +msgstr "" + +#: ./doc/training-guides/module002-ch001-networking-in-openstack.xml50(guilabel) +msgid "" +"Plugin Architecture: Flexibility to Choose Different Network Technologies" +msgstr "" + +#: ./doc/training-guides/module002-ch001-networking-in-openstack.xml52(para) +msgid "" +"Enhancing traditional networking solutions to provide rich cloud networking " +"is challenging. Traditional networking is not designed to scale to cloud " +"proportions or to configure automatically." +msgstr "" + +#: ./doc/training-guides/module002-ch001-networking-in-openstack.xml56(para) +msgid "" +"The original OpenStack Compute network implementation assumed a very basic " +"model of performing all isolation through Linux VLANs and IP tables. " +"OpenStack Networking introduces the concept of a plugin, which is a " +"pluggable back-end implementation of the OpenStack Networking API. A plugin " +"can use a variety of technologies to implement the logical API requests. " +"Some OpenStack Networking plugins might use basic Linux VLANs and IP tables," +" while others might use more advanced technologies, such as L2-in-L3 " +"tunneling or OpenFlow, to provide similar benefits." +msgstr "" + +#: ./doc/training-guides/module002-ch001-networking-in-openstack.xml66(para) +msgid "The current set of plugins include:" +msgstr "" + +#: ./doc/training-guides/module002-ch001-networking-in-openstack.xml69(para) +msgid "" +"Open vSwitch: Documentation included in " +"this guide." +msgstr "" + +#: ./doc/training-guides/module002-ch001-networking-in-openstack.xml73(para) +msgid "" +"Cisco: Documented externally at: http://wiki.openstack.org" +"/cisco-quantum" +msgstr "" + +#: ./doc/training-guides/module002-ch001-networking-in-openstack.xml79(para) +msgid "" +"Linux Bridge: Documentation included in " +"this guide and http://wiki.openstack.org/Quantum-Linux-Bridge-Plugin" +msgstr "" + +#: ./doc/training-guides/module002-ch001-networking-in-openstack.xml86(para) +msgid "" +"Nicira NVP: Documentation include in this" +" guide, NVP Product Overview , and NVP Product Support." +msgstr "" + +#: ./doc/training-guides/module002-ch001-networking-in-openstack.xml94(emphasis) +msgid "Ryu:" +msgstr "" + +#: ./doc/training-guides/module002-ch001-networking-in-openstack.xml97(link) +msgid "https://github.com/osrg/ryu/wiki/OpenStack" +msgstr "" + +#: ./doc/training-guides/module002-ch001-networking-in-openstack.xml100(emphasis) +msgid "NEC OpenFlow:" +msgstr "" + +#: ./doc/training-guides/module002-ch001-networking-in-openstack.xml103(link) +msgid "http://wiki.openstack.org/Quantum-NEC-OpenFlow-Plugin" +msgstr "" + +#: ./doc/training-guides/module002-ch001-networking-in-openstack.xml106(emphasis) +msgid "Big Switch, Floodlight REST Proxy:" +msgstr "" + +#: ./doc/training-guides/module002-ch001-networking-in-openstack.xml110(link) +msgid "" +"http://www.openflowhub.org/display/floodlightcontroller/Quantum+REST+Proxy+Plugin" +msgstr "" + +#: ./doc/training-guides/module002-ch001-networking-in-openstack.xml113(emphasis) +msgid "PLUMgrid:" +msgstr "" + +#: ./doc/training-guides/module002-ch001-networking-in-openstack.xml116(link) +msgid "https://wiki.openstack.org/wiki/Plumgrid-quantum" +msgstr "" + +#: ./doc/training-guides/module002-ch001-networking-in-openstack.xml119(emphasis) +msgid "Hyper-V Plugin" +msgstr "" + +#: ./doc/training-guides/module002-ch001-networking-in-openstack.xml123(emphasis) +msgid "Brocade Plugin" +msgstr "" + +#: ./doc/training-guides/module002-ch001-networking-in-openstack.xml127(emphasis) +msgid "Midonet Plugin" +msgstr "" + +#: ./doc/training-guides/module002-ch001-networking-in-openstack.xml131(para) +msgid "" +"Plugins can have different properties in terms of hardware requirements, " +"features, performance, scale, operator tools, etc. Supporting many plugins " +"enables the cloud administrator to weigh different options and decide which " +"networking technology is right for the deployment." +msgstr "" + +#: ./doc/training-guides/module002-ch001-networking-in-openstack.xml136(para) +msgid "Components of OpenStack Networking" +msgstr "" + +#: ./doc/training-guides/module002-ch001-networking-in-openstack.xml137(para) +msgid "" +"To deploy OpenStack Networking, it is useful to understand the different " +"components that make up the solution and how those components interact with " +"each other and with other OpenStack services." +msgstr "" + +#: ./doc/training-guides/module002-ch001-networking-in-openstack.xml141(para) +msgid "" +"OpenStack Networking is a standalone service, just like other OpenStack " +"services such as OpenStack Compute, OpenStack Image service, OpenStack " +"Identity service, and the OpenStack Dashboard. Like those services, a " +"deployment of OpenStack Networking often involves deploying several " +"processes on a variety of hosts." +msgstr "" + +#: ./doc/training-guides/module002-ch001-networking-in-openstack.xml147(para) +msgid "" +"The main process of the OpenStack Networking server is quantum-server, which" +" is a Python daemon that exposes the OpenStack Networking API and passes " +"user requests to the configured OpenStack Networking plugin for additional " +"processing. Typically, the plugin requires access to a database for " +"persistent storage, similar to other OpenStack services." +msgstr "" + +#: ./doc/training-guides/module002-ch001-networking-in-openstack.xml154(para) +msgid "" +"If your deployment uses a controller host to run centralized OpenStack " +"Compute components, you can deploy the OpenStack Networking server on that " +"same host. However, OpenStack Networking is entirely standalone and can be " +"deployed on its own server as well. OpenStack Networking also includes " +"additional agents that might be required depending on your deployment:" +msgstr "" + +#: ./doc/training-guides/module002-ch001-networking-in-openstack.xml163(para) +msgid "" +"plugin agent (quantum-*-agent):Runs on " +"each hypervisor to perform local vswitch configuration. Agent to be run " +"depends on which plugin you are using, as some plugins do not require an " +"agent." +msgstr "" + +#: ./doc/training-guides/module002-ch001-networking-in-openstack.xml170(para) +msgid "" +"dhcp agent (quantum-dhcp-agent):Provides " +"DHCP services to tenant networks. This agent is the same across all plugins." +msgstr "" + +#: ./doc/training-guides/module002-ch001-networking-in-openstack.xml176(para) +msgid "" +"l3 agent (quantum-l3-agent):Provides " +"L3/NAT forwarding to provide external network access for VMs on tenant " +"networks. This agent is the same across all plugins." +msgstr "" + +#: ./doc/training-guides/module002-ch001-networking-in-openstack.xml183(para) +msgid "" +"These agents interact with the main quantum-server process in the following " +"ways:" +msgstr "" + +#: ./doc/training-guides/module002-ch001-networking-in-openstack.xml187(para) +msgid "Through RPC. For example, rabbitmq or qpid." +msgstr "" + +#: ./doc/training-guides/module002-ch001-networking-in-openstack.xml190(para) +msgid "Through the standard OpenStack Networking API." +msgstr "" + +#: ./doc/training-guides/module002-ch001-networking-in-openstack.xml194(para) +msgid "" +"OpenStack Networking relies on the OpenStack Identity Project (Keystone) for" +" authentication and authorization of all API request." +msgstr "" + +#: ./doc/training-guides/module002-ch001-networking-in-openstack.xml197(para) +msgid "" +"OpenStack Compute interacts with OpenStack Networking through calls to its " +"standard API. As part of creating a VM, nova-compute communicates with the " +"OpenStack Networking API to plug each virtual NIC on the VM into a " +"particular network." +msgstr "" + +#: ./doc/training-guides/module002-ch001-networking-in-openstack.xml202(para) +msgid "" +"The OpenStack Dashboard (Horizon) has integration with the OpenStack " +"Networking API, allowing administrators and tenant users, to create and " +"manage network services through the Horizon GUI." +msgstr "" + +#: ./doc/training-guides/module002-ch001-networking-in-openstack.xml206(emphasis) +msgid "Place Services on Physical Hosts" +msgstr "" + +#: ./doc/training-guides/module002-ch001-networking-in-openstack.xml208(para) +msgid "" +"Like other OpenStack services, OpenStack Networking provides cloud " +"administrators with significant flexibility in deciding which individual " +"services should run on which physical devices. On one extreme, all service " +"daemons can be run on a single physical host for evaluation purposes. On the" +" other, each service could have its own physical hosts, and some cases be " +"replicated across multiple hosts for redundancy." +msgstr "" + +#: ./doc/training-guides/module002-ch001-networking-in-openstack.xml215(para) +msgid "" +"In this guide, we focus primarily on a standard architecture that includes a" +" “cloud controller” host, a “network gateway” host, and a set of hypervisors" +" for running VMs. The \"cloud controller\" and \"network gateway\" can be " +"combined in simple deployments, though if you expect VMs to send significant" +" amounts of traffic to or from the Internet, a dedicated network gateway " +"host is suggested to avoid potential CPU contention between packet " +"forwarding performed by the quantum-l3-agent and other OpenStack services." +msgstr "" + +#: ./doc/training-guides/module002-ch001-networking-in-openstack.xml224(emphasis) +msgid "Network Connectivity for Physical Hosts" +msgstr "" + +#: ./doc/training-guides/module002-ch001-networking-in-openstack.xml227(title) +#: ./doc/training-guides/lab002-network-node.xml11(title) +#: ./doc/training-guides/lab003-compute-node.xml14(title) +#: ./doc/training-guides/lab001-control-node.xml10(title) +#: ./doc/training-guides/lab000-virtualbox-basics.xml135(title) +msgid "Network Diagram" +msgstr "" + +#: ./doc/training-guides/module002-ch001-networking-in-openstack.xml234(para) +msgid "" +"A standard OpenStack Networking setup has up to four distinct physical data " +"center networks:" +msgstr "" + +#: ./doc/training-guides/module002-ch001-networking-in-openstack.xml238(para) +msgid "" +"Management network:Used for internal " +"communication between OpenStack Components. The IP addresses on this network" +" should be reachable only within the data center." +msgstr "" + +#: ./doc/training-guides/module002-ch001-networking-in-openstack.xml245(para) +msgid "" +"Data network:Used for VM data " +"communication within the cloud deployment. The IP addressing requirements of" +" this network depend on the OpenStack Networking plugin in use." +msgstr "" + +#: ./doc/training-guides/module002-ch001-networking-in-openstack.xml251(para) +msgid "" +"External network:Used to provide VMs with" +" Internet access in some deployment scenarios. The IP addresses on this " +"network should be reachable by anyone on the Internet." +msgstr "" + +#: ./doc/training-guides/module002-ch001-networking-in-openstack.xml258(para) +msgid "" +"API network:Exposes all OpenStack APIs, " +"including the OpenStack Networking API, to tenants. The IP addresses on this" +" network should be reachable by anyone on the Internet. This may be the same" +" network as the external network, as it is possible to create a subnet for " +"the external network that uses IP allocation ranges to use only less than " +"the full range of IP addresses in an IP block." +msgstr "" + +#. When image changes, this message will be marked fuzzy or untranslated for +#. you. +#. It doesn't matter what you translate it to: it's not used at all. +#: ./doc/training-guides/module003-ch004-swift-building-blocks.xml52(None) +msgid "@@image: 'figures/image40.png'; md5=ed79466c8464513dbeaf1e0954280e5e" +msgstr "" + +#. When image changes, this message will be marked fuzzy or untranslated for +#. you. +#. It doesn't matter what you translate it to: it's not used at all. +#: ./doc/training-guides/module003-ch004-swift-building-blocks.xml116(None) +msgid "@@image: 'figures/image41.png'; md5=a94e26734cec6980c3684d9e824eac2d" +msgstr "" + +#. When image changes, this message will be marked fuzzy or untranslated for +#. you. +#. It doesn't matter what you translate it to: it's not used at all. +#: ./doc/training-guides/module003-ch004-swift-building-blocks.xml169(None) +msgid "@@image: 'figures/image42.png'; md5=1b1dc0abe6ea0c516f22ce399deb75ed" +msgstr "" + +#. When image changes, this message will be marked fuzzy or untranslated for +#. you. +#. It doesn't matter what you translate it to: it's not used at all. +#: ./doc/training-guides/module003-ch004-swift-building-blocks.xml187(None) +msgid "@@image: 'figures/image43.png'; md5=4b15e5a202db5bde53c9b369058aeab8" +msgstr "" + +#. When image changes, this message will be marked fuzzy or untranslated for +#. you. +#. It doesn't matter what you translate it to: it's not used at all. +#: ./doc/training-guides/module003-ch004-swift-building-blocks.xml219(None) +msgid "@@image: 'figures/image44.png'; md5=2c161c2e92d6fefc8140ec86e79e9492" +msgstr "" + +#. When image changes, this message will be marked fuzzy or untranslated for +#. you. +#. It doesn't matter what you translate it to: it's not used at all. +#: ./doc/training-guides/module003-ch004-swift-building-blocks.xml252(None) +msgid "@@image: 'figures/image45.png'; md5=9d55594d7f445764569ab04d8d4373b2" +msgstr "" + +#. When image changes, this message will be marked fuzzy or untranslated for +#. you. +#. It doesn't matter what you translate it to: it's not used at all. +#: ./doc/training-guides/module003-ch004-swift-building-blocks.xml283(None) +msgid "@@image: 'figures/image46.png'; md5=07480e7175b383171173775fb96d70d7" +msgstr "" + +#: ./doc/training-guides/module003-ch004-swift-building-blocks.xml7(title) +msgid "Building Blocks of Swift" +msgstr "" + +#: ./doc/training-guides/module003-ch004-swift-building-blocks.xml8(para) +msgid "" +"The components that enable Swift to deliver high availability, high " +"durability and high concurrency are:" +msgstr "" + +#: ./doc/training-guides/module003-ch004-swift-building-blocks.xml13(para) +msgid "" +"Proxy Servers:Handles all incoming API " +"requests." +msgstr "" + +#: ./doc/training-guides/module003-ch004-swift-building-blocks.xml18(para) +msgid "" +"Rings:Maps logical names of data to " +"locations on particular disks." +msgstr "" + +#: ./doc/training-guides/module003-ch004-swift-building-blocks.xml23(para) +msgid "" +"Zones:Each Zone isolates data from other " +"Zones. A failure in one Zone doesn’t impact the rest of the cluster because " +"data is replicated across the Zones." +msgstr "" + +#: ./doc/training-guides/module003-ch004-swift-building-blocks.xml29(para) +msgid "" +"Accounts & Containers:Each Account " +"and Container are individual databases that are distributed across the " +"cluster. An Account database contains the list of Containers in that " +"Account. A Container database contains the list of Objects in that Container" +msgstr "" + +#: ./doc/training-guides/module003-ch004-swift-building-blocks.xml37(para) +msgid "Objects:The data itself." +msgstr "" + +#: ./doc/training-guides/module003-ch004-swift-building-blocks.xml41(para) +msgid "" +"Partitions:A Partition stores Objects, " +"Account databases and Container databases. It’s an intermediate 'bucket' " +"that helps manage locations where data lives in the cluster." +msgstr "" + +#: ./doc/training-guides/module003-ch004-swift-building-blocks.xml49(title) +msgid "Building Blocks" +msgstr "" + +#: ./doc/training-guides/module003-ch004-swift-building-blocks.xml56(guilabel) +msgid "Proxy Servers" +msgstr "" + +#: ./doc/training-guides/module003-ch004-swift-building-blocks.xml57(para) +msgid "" +"The Proxy Servers are the public face of Swift and handle all incoming API " +"requests. Once a Proxy Server receive a request, it will determine the " +"storage node based on the URL of the object, such as " +"https://swift.example.com/v1/account/container/object . The Proxy " +"Servers also coordinates responses, handles failures and coordinates " +"timestamps." +msgstr "" + +#: ./doc/training-guides/module003-ch004-swift-building-blocks.xml64(para) +msgid "" +"Proxy servers use a shared-nothing architecture and can be scaled as needed " +"based on projected workloads. A minimum of two Proxy Servers should be " +"deployed for redundancy. Should one proxy server fail, the others will take " +"over." +msgstr "" + +#: ./doc/training-guides/module003-ch004-swift-building-blocks.xml69(guilabel) +msgid "The Ring" +msgstr "" + +#: ./doc/training-guides/module003-ch004-swift-building-blocks.xml70(para) +msgid "" +"A ring represents a mapping between the names of entities stored on disk and" +" their physical location. There are separate rings for accounts, containers," +" and objects. When other components need to perform any operation on an " +"object, container, or account, they need to interact with the appropriate " +"ring to determine its location in the cluster." +msgstr "" + +#: ./doc/training-guides/module003-ch004-swift-building-blocks.xml77(para) +msgid "" +"The Ring maintains this mapping using zones, devices, partitions, and " +"replicas. Each partition in the ring is replicated, by default, 3 times " +"across the cluster, and the locations for a partition are stored in the " +"mapping maintained by the ring. The ring is also responsible for determining" +" which devices are used for hand off in failure scenarios." +msgstr "" + +#: ./doc/training-guides/module003-ch004-swift-building-blocks.xml84(para) +msgid "" +"Data can be isolated with the concept of zones in the ring. Each replica of " +"a partition is guaranteed to reside in a different zone. A zone could " +"represent a drive, a server, a cabinet, a switch, or even a data center." +msgstr "" + +#: ./doc/training-guides/module003-ch004-swift-building-blocks.xml88(para) +msgid "" +"The partitions of the ring are equally divided among all the devices in the " +"OpenStack Object Storage installation. When partitions need to be moved " +"around, such as when a device is added to the cluster, the ring ensures that" +" a minimum number of partitions are moved at a time, and only one replica of" +" a partition is moved at a time." +msgstr "" + +#: ./doc/training-guides/module003-ch004-swift-building-blocks.xml94(para) +msgid "" +"Weights can be used to balance the distribution of partitions on drives " +"across the cluster. This can be useful, for example, when different sized " +"drives are used in a cluster." +msgstr "" + +#: ./doc/training-guides/module003-ch004-swift-building-blocks.xml98(para) +msgid "" +"The ring is used by the Proxy server and several background processes (like " +"replication)." +msgstr "" + +#: ./doc/training-guides/module003-ch004-swift-building-blocks.xml100(para) +msgid "" +"The Ring maps Partitions to physical locations on disk. When other " +"components need to perform any operation on an object, container, or " +"account, they need to interact with the Ring to determine its location in " +"the cluster." +msgstr "" + +#: ./doc/training-guides/module003-ch004-swift-building-blocks.xml104(para) +msgid "" +"The Ring maintains this mapping using zones, devices, partitions, and " +"replicas. Each partition in the Ring is replicated three times by default " +"across the cluster, and the locations for a partition are stored in the " +"mapping maintained by the Ring. The Ring is also responsible for determining" +" which devices are used for handoff should a failure occur." +msgstr "" + +#: ./doc/training-guides/module003-ch004-swift-building-blocks.xml112(title) +msgid "The Lord of the Rings" +msgstr "" + +#: ./doc/training-guides/module003-ch004-swift-building-blocks.xml120(para) +msgid "The Ring maps partitions to physical locations on disk." +msgstr "" + +#: ./doc/training-guides/module003-ch004-swift-building-blocks.xml122(para) +msgid "" +"The rings determine where data should reside in the cluster. There is a " +"separate ring for account databases, container databases, and individual " +"objects but each ring works in the same way. These rings are externally " +"managed, in that the server processes themselves do not modify the rings, " +"they are instead given new rings modified by other tools." +msgstr "" + +#: ./doc/training-guides/module003-ch004-swift-building-blocks.xml129(para) +msgid "" +"The ring uses a configurable number of bits from a path’s MD5 hash as a " +"partition index that designates a device. The number of bits kept from the " +"hash is known as the partition power, and 2 to the partition power indicates" +" the partition count. Partitioning the full MD5 hash ring allows other parts" +" of the cluster to work in batches of items at once which ends up either " +"more efficient or at least less complex than working with each item " +"separately or the entire cluster all at once." +msgstr "" + +#: ./doc/training-guides/module003-ch004-swift-building-blocks.xml138(para) +msgid "" +"Another configurable value is the replica count, which indicates how many of" +" the partition->device assignments comprise a single ring. For a given " +"partition number, each replica’s device will not be in the same zone as any " +"other replica's device. Zones can be used to group devices based on physical" +" locations, power separations, network separations, or any other attribute " +"that would lessen multiple replicas being unavailable at the same time." +msgstr "" + +#: ./doc/training-guides/module003-ch004-swift-building-blocks.xml146(guilabel) +msgid "Zones: Failure Boundaries" +msgstr "" + +#: ./doc/training-guides/module003-ch004-swift-building-blocks.xml147(para) +msgid "" +"Swift allows zones to be configured to isolate failure boundaries. Each " +"replica of the data resides in a separate zone, if possible. At the smallest" +" level, a zone could be a single drive or a grouping of a few drives. If " +"there were five object storage servers, then each server would represent its" +" own zone. Larger deployments would have an entire rack (or multiple racks) " +"of object servers, each representing a zone. The goal of zones is to allow " +"the cluster to tolerate significant outages of storage servers without " +"losing all replicas of the data." +msgstr "" + +#: ./doc/training-guides/module003-ch004-swift-building-blocks.xml158(para) +msgid "" +"As we learned earlier, everything in Swift is stored, by default, three " +"times. Swift will place each replica \"as-uniquely-as-possible\" to ensure " +"both high availability and high durability. This means that when choosing a " +"replica location, Swift will choose a server in an unused zone before an " +"unused server in a zone that already has a replica of the data." +msgstr "" + +#: ./doc/training-guides/module003-ch004-swift-building-blocks.xml166(title) +msgid "image33.png" +msgstr "" + +#: ./doc/training-guides/module003-ch004-swift-building-blocks.xml173(para) +msgid "" +"When a disk fails, replica data is automatically distributed to the other " +"zones to ensure there are three copies of the data" +msgstr "" + +#: ./doc/training-guides/module003-ch004-swift-building-blocks.xml176(guilabel) +msgid "Accounts & Containers" +msgstr "" + +#: ./doc/training-guides/module003-ch004-swift-building-blocks.xml178(para) +msgid "" +"Each account and container is an individual SQLite database that is " +"distributed across the cluster. An account database contains the list of " +"containers in that account. A container database contains the list of " +"objects in that container." +msgstr "" + +#: ./doc/training-guides/module003-ch004-swift-building-blocks.xml184(title) +msgid "Accounts and Containers" +msgstr "" + +#: ./doc/training-guides/module003-ch004-swift-building-blocks.xml191(para) +msgid "" +"To keep track of object data location, each account in the system has a " +"database that references all its containers, and each container database " +"references each object" +msgstr "" + +#: ./doc/training-guides/module003-ch004-swift-building-blocks.xml195(guilabel) +#: ./doc/training-guides/module003-ch004-swift-building-blocks.xml216(title) +msgid "Partitions" +msgstr "" + +#: ./doc/training-guides/module003-ch004-swift-building-blocks.xml196(para) +msgid "" +"A Partition is a collection of stored data, including Account databases, " +"Container databases, and objects. Partitions are core to the replication " +"system." +msgstr "" + +#: ./doc/training-guides/module003-ch004-swift-building-blocks.xml200(para) +msgid "" +"Think of a Partition as a bin moving throughout a fulfillment center " +"warehouse. Individual orders get thrown into the bin. The system treats that" +" bin as a cohesive entity as it moves throughout the system. A bin full of " +"things is easier to deal with than lots of little things. It makes for fewer" +" moving parts throughout the system." +msgstr "" + +#: ./doc/training-guides/module003-ch004-swift-building-blocks.xml207(para) +msgid "" +"The system replicators and object uploads/downloads operate on Partitions. " +"As the system scales up, behavior continues to be predictable as the number " +"of Partitions is a fixed number." +msgstr "" + +#: ./doc/training-guides/module003-ch004-swift-building-blocks.xml211(para) +msgid "" +"The implementation of a Partition is conceptually simple -- a partition is " +"just a directory sitting on a disk with a corresponding hash table of what " +"it contains." +msgstr "" + +#: ./doc/training-guides/module003-ch004-swift-building-blocks.xml223(para) +msgid "*Swift partitions contain all data in the system." +msgstr "" + +#: ./doc/training-guides/module003-ch004-swift-building-blocks.xml226(para) +msgid "" +"In order to ensure that there are three copies of the data everywhere, " +"replicators continuously examine each Partition. For each local Partition, " +"the replicator compares it against the replicated copies in the other Zones " +"to see if there are any differences." +msgstr "" + +#: ./doc/training-guides/module003-ch004-swift-building-blocks.xml232(para) +msgid "" +"How does the replicator know if replication needs to take place? It does " +"this by examining hashes. A hash file is created for each Partition, which " +"contains hashes of each directory in the Partition. Each of the three hash " +"files is compared. For a given Partition, the hash files for each of the " +"Partition's copies are compared. If the hashes are different, then it is " +"time to replicate and the directory that needs to be replicated is copied " +"over." +msgstr "" + +#: ./doc/training-guides/module003-ch004-swift-building-blocks.xml241(para) +msgid "" +"This is where the Partitions come in handy. With fewer \"things\" in the " +"system, larger chunks of data are transferred around (rather than lots of " +"little TCP connections, which is inefficient) and there are a consistent " +"number of hashes to compare." +msgstr "" + +#: ./doc/training-guides/module003-ch004-swift-building-blocks.xml246(para) +msgid "" +"The cluster has eventually consistent behavior where the newest data wins." +msgstr "" + +#: ./doc/training-guides/module003-ch004-swift-building-blocks.xml256(para) +msgid "" +"*If a zone goes down, one of the nodes containing a replica notices and " +"proactively copies data to a handoff location." +msgstr "" + +#: ./doc/training-guides/module003-ch004-swift-building-blocks.xml259(para) +msgid "" +"To describe how these pieces all come together, let's walk through a few " +"scenarios and introduce the components." +msgstr "" + +#: ./doc/training-guides/module003-ch004-swift-building-blocks.xml261(guilabel) +msgid "Bird-eye View" +msgstr "" + +#: ./doc/training-guides/module003-ch004-swift-building-blocks.xml262(emphasis) +msgid "Upload" +msgstr "" + +#: ./doc/training-guides/module003-ch004-swift-building-blocks.xml264(para) +msgid "" +"A client uses the REST API to make a HTTP request to PUT an object into an " +"existing Container. The cluster receives the request. First, the system must" +" figure out where the data is going to go. To do this, the Account name, " +"Container name and Object name are all used to determine the Partition where" +" this object should live." +msgstr "" + +#: ./doc/training-guides/module003-ch004-swift-building-blocks.xml270(para) +msgid "" +"Then a lookup in the Ring figures out which storage nodes contain the " +"Partitions in question." +msgstr "" + +#: ./doc/training-guides/module003-ch004-swift-building-blocks.xml272(para) +msgid "" +"The data then is sent to each storage node where it is placed in the " +"appropriate Partition. A quorum is required -- at least two of the three " +"writes must be successful before the client is notified that the upload was " +"successful." +msgstr "" + +#: ./doc/training-guides/module003-ch004-swift-building-blocks.xml277(para) +msgid "" +"Next, the Container database is updated asynchronously to reflect that there" +" is a new object in it." +msgstr "" + +#: ./doc/training-guides/module003-ch004-swift-building-blocks.xml280(title) +msgid "When End-User uses Swift" +msgstr "" + +#: ./doc/training-guides/module003-ch004-swift-building-blocks.xml287(emphasis) +msgid "Download" +msgstr "" + +#: ./doc/training-guides/module003-ch004-swift-building-blocks.xml288(para) +msgid "" +"A request comes in for an Account/Container/object. Using the same " +"consistent hashing, the Partition name is generated. A lookup in the Ring " +"reveals which storage nodes contain that Partition. A request is made to one" +" of the storage nodes to fetch the object and if that fails, requests are " +"made to the other nodes." +msgstr "" + +#. When image changes, this message will be marked fuzzy or untranslated for +#. you. +#. It doesn't matter what you translate it to: it's not used at all. +#: ./doc/training-guides/user-story-includes-template.xml19(None) +msgid "" +"@@image: 'figures/openstack-training-example-image.png'; " +"md5=87bf110d5b53b2168680e1370176ef02" +msgstr "" + +#: ./doc/training-guides/user-story-includes-template.xml7(title) +msgid "Including external content for user stories, version 1.3" +msgstr "" + +#: ./doc/training-guides/user-story-includes-template.xml8(para) +msgid "" +"Save your user story file as associate-my-user-story-name, operator-my-user-" +"story, etc. For example my user story that I assigned myself is operator bug" +" fix so the file name would be operator-fix-documentation-bug.xml. See the " +"operator-fix-documentation-bug.xml file in the repository for more details." +msgstr "" + +#: ./doc/training-guides/user-story-includes-template.xml12(para) +msgid "" +"The include statements below are meant to help you tell and teach the user " +"story. Include as much content as necessary. Use examples." +msgstr "" + +#: ./doc/training-guides/user-story-includes-template.xml14(para) +msgid "" +"Create diagrams through gdraw. Export as png. Reference as local file in the" +" /figures/ director. Share as 'Anyone With the Link' can 'Edit' and add URL " +"to the description so anyone else can update the original." +msgstr "" + +#: ./doc/training-guides/user-story-includes-template.xml17(para) +msgid " big dummy example image" +msgstr "" + +#: ./doc/training-guides/user-story-includes-template.xml22(para) +#: ./doc/training-guides/card074-horizon-snapshots.xml12(para) +#: ./doc/training-guides/card071-create-cinder-horizon.xml11(para) +#: ./doc/training-guides/card071-create-cinder-horizon.xml15(para) +#: ./doc/training-guides/card071-create-cinder-horizon.xml19(para) +#: ./doc/training-guides/bk001-ch003-associate-controller-node.xml17(para) +#: ./doc/training-guides/bk001-ch003-associate-controller-node.xml24(para) +#: ./doc/training-guides/bk001-ch003-associate-controller-node.xml31(para) +#: ./doc/training-guides/bk001-ch003-associate-controller-node.xml40(para) +#: ./doc/training-guides/bk001-ch003-associate-controller-node.xml47(para) +#: ./doc/training-guides/bk001-ch003-associate-controller-node.xml54(para) +#: ./doc/training-guides/bk001-ch003-associate-controller-node.xml61(para) +#: ./doc/training-guides/bk001-ch003-associate-controller-node.xml68(para) +#: ./doc/training-guides/bk001-ch003-associate-controller-node.xml75(para) +#: ./doc/training-guides/bk001-ch003-associate-controller-node.xml82(para) +#: ./doc/training-guides/bk002-ch010-operator-network-node.xml17(para) +#: ./doc/training-guides/bk002-ch010-operator-network-node.xml24(para) +#: ./doc/training-guides/bk001-ch009-associate-object-storage-node.xml17(para) +#: ./doc/training-guides/bk001-ch009-associate-object-storage-node.xml24(para) +#: ./doc/training-guides/bk001-ch009-associate-object-storage-node.xml33(para) +#: ./doc/training-guides/card072-cinder-attach-volume.xml11(para) +#: ./doc/training-guides/bk002-ch004-operator-controller-node.xml17(para) +#: ./doc/training-guides/bk002-ch004-operator-controller-node.xml24(para) +#: ./doc/training-guides/bk002-ch004-operator-controller-node.xml31(para) +#: ./doc/training-guides/bk002-ch002-operator-getting-started-lab.xml15(para) +#: ./doc/training-guides/bk002-ch002-operator-getting-started-lab.xml22(para) +#: ./doc/training-guides/bk002-ch002-operator-getting-started-lab.xml29(para) +#: ./doc/training-guides/bk002-ch002-operator-getting-started-lab.xml36(para) +#: ./doc/training-guides/bk002-ch002-operator-getting-started-lab.xml43(para) +#: ./doc/training-guides/bk002-ch007-operator-compute-node.xml17(para) +#: ./doc/training-guides/bk002-ch007-operator-compute-node.xml24(para) +#: ./doc/training-guides/bk002-ch007-operator-compute-node.xml31(para) +#: ./doc/training-guides/bk002-ch013-operator-object-storage-node.xml17(para) +#: ./doc/training-guides/bk002-ch013-operator-object-storage-node.xml24(para) +#: ./doc/training-guides/bk002-ch013-operator-object-storage-node.xml35(para) +#: ./doc/training-guides/bk002-ch013-operator-object-storage-node.xml42(para) +#: ./doc/training-guides/bk002-ch013-operator-object-storage-node.xml49(para) +#: ./doc/training-guides/bk002-ch013-operator-object-storage-node.xml55(para) +#: ./doc/training-guides/bk002-ch013-operator-object-storage-node.xml62(para) +#: ./doc/training-guides/bk002-ch013-operator-object-storage-node.xml69(para) +#: ./doc/training-guides/bk002-ch013-operator-object-storage-node.xml76(para) +#: ./doc/training-guides/bk002-ch001-operator-getting-started.xml25(para) +#: ./doc/training-guides/bk002-ch001-operator-getting-started.xml32(para) +#: ./doc/training-guides/bk002-ch001-operator-getting-started.xml39(para) +#: ./doc/training-guides/bk002-ch001-operator-getting-started.xml46(para) +#: ./doc/training-guides/bk002-ch001-operator-getting-started.xml53(para) +#: ./doc/training-guides/card008.xml11(para) +#: ./doc/training-guides/bk000-preface.xml133(para) +#: ./doc/training-guides/bk000-preface.xml140(para) +#: ./doc/training-guides/bk000-preface.xml147(para) +#: ./doc/training-guides/bk001-ch001-associate-getting-started.xml27(para) +#: ./doc/training-guides/bk001-ch001-associate-getting-started.xml34(para) +#: ./doc/training-guides/bk001-ch001-associate-getting-started.xml41(para) +#: ./doc/training-guides/bk001-ch001-associate-getting-started.xml48(para) +#: ./doc/training-guides/bk001-ch001-associate-getting-started.xml55(para) +#: ./doc/training-guides/card073-control-state-instance.xml12(para) +#: ./doc/training-guides/bk001-ch005-associate-compute-node.xml17(para) +#: ./doc/training-guides/bk001-ch005-associate-compute-node.xml24(para) +#: ./doc/training-guides/bk001-ch005-associate-compute-node.xml31(para) +#: ./doc/training-guides/bk001-ch005-associate-compute-node.xml40(para) +#: ./doc/training-guides/bk001-ch005-associate-compute-node.xml47(para) +#: ./doc/training-guides/bk001-ch005-associate-compute-node.xml54(para) +#: ./doc/training-guides/bk001-ch005-associate-compute-node.xml61(para) +#: ./doc/training-guides/bk001-ch005-associate-compute-node.xml68(para) +#: ./doc/training-guides/bk001-ch005-associate-compute-node.xml75(para) +#: ./doc/training-guides/card128-swift.xml11(para) +#: ./doc/training-guides/bk003-developer-training-guide.xml13(para) +#: ./doc/training-guides/bk003-developer-training-guide.xml20(para) +#: ./doc/training-guides/bk003-developer-training-guide.xml27(para) +#: ./doc/training-guides/bk003-developer-training-guide.xml34(para) +#: ./doc/training-guides/bk003-developer-training-guide.xml41(para) +#: ./doc/training-guides/bk003-developer-training-guide.xml48(para) +#: ./doc/training-guides/bk003-developer-training-guide.xml55(para) +#: ./doc/training-guides/bk003-developer-training-guide.xml62(para) +#: ./doc/training-guides/bk003-developer-training-guide.xml69(para) +#: ./doc/training-guides/bk001-ch007-associate-network-node.xml17(para) +#: ./doc/training-guides/bk001-ch007-associate-network-node.xml24(para) +#: ./doc/training-guides/bk001-ch007-associate-network-node.xml33(para) +#: ./doc/training-guides/bk001-ch007-associate-network-node.xml40(para) +#: ./doc/training-guides/card070-create-floating-ips.xml11(para) +#: ./doc/training-guides/card070-create-floating-ips.xml16(para) +#: ./doc/training-guides/card070-create-floating-ips.xml21(para) +msgid "image source" +msgstr "" + +#: ./doc/training-guides/user-story-includes-template.xml23(link) +msgid "" +"https://docs.google.com/drawings/d/1Tdn4SZLBdvQybW_nK_lO380YRIe5T6PsI0IyLH5XE3M/edit?usp=sharing" +msgstr "" + +#: ./doc/training-guides/user-story-includes-template.xml25(emphasis) +msgid "" +"Including a whole file. Include as much description about what is being " +"taught here." +msgstr "" + +#: ./doc/training-guides/user-story-includes-template.xml33(link) +#: ./doc/training-guides/user-story-includes-template.xml45(link) +#: ./doc/training-guides/card007-core-overview.xml14(link) +#: ./doc/training-guides/card025.xml13(link) +#: ./doc/training-guides/card074-horizon-snapshots.xml14(link) +#: ./doc/training-guides/card071-create-cinder-horizon.xml21(link) +#: ./doc/training-guides/card009.xml16(link) +#: ./doc/training-guides/card043-ovs-in-network-node.xml15(link) +#: ./doc/training-guides/card072-cinder-attach-volume.xml13(link) +#: ./doc/training-guides/card126-horizon.xml13(link) +#: ./doc/training-guides/card039-nova.xml14(link) +#: ./doc/training-guides/card047-install-nova-compute.xml14(link) +#: ./doc/training-guides/card045-configure-virtual-networking.xml20(link) +#: ./doc/training-guides/card041-neutron.xml22(link) +#: ./doc/training-guides/card008.xml13(link) +#: ./doc/training-guides/card037-rabbitmq.xml14(link) +#: ./doc/training-guides/card040-cinder.xml15(link) +#: ./doc/training-guides/card046-L3_Configuration_in_the_Network_Node.xml14(link) +#: ./doc/training-guides/card127-glance.xml14(link) +#: ./doc/training-guides/card026-network-node-architecture.xml14(link) +#: ./doc/training-guides/card044-install-and-configure-neutron-network-node.xml14(link) +#: ./doc/training-guides/card073-control-state-instance.xml14(link) +#: ./doc/training-guides/card128-swift.xml13(link) +#: ./doc/training-guides/card011.xml14(link) +#: ./doc/training-guides/card070-create-floating-ips.xml23(link) +#: ./doc/training-guides/card038.xml13(link) +msgid "" +"Submit a bug on the section above. Short description for the bug summary. " +"Paragraph for the description and then tag with training-manuals." +msgstr "" + +#: ./doc/training-guides/user-story-includes-template.xml37(emphasis) +msgid "" +"Including a section of a file. Include as much description about what is " +"being taught here." +msgstr "" + +#: ./doc/training-guides/module001-ch011-block-storage.xml6(title) +#: ./doc/training-guides/bk001-ch005-associate-compute-node.xml28(title) +msgid "OpenStack Block Storage" +msgstr "" + +#: ./doc/training-guides/module001-ch011-block-storage.xml7(emphasis) +msgid "Block Storage and OpenStack Compute" +msgstr "" + +#: ./doc/training-guides/module001-ch011-block-storage.xml9(para) +msgid "" +"OpenStack provides two classes of block storage, \"ephemeral\" storage and " +"persistent \"volumes\". Ephemeral storage exists only for the life of an " +"instance, it will persist across reboots of the guest operating system but " +"when the instance is deleted so is the associated storage. All instances " +"have some ephemeral storage. Volumes are persistent virtualized block " +"devices independent of any particular instance. Volumes may be attached to a" +" single instance at a time, but may be detached or reattached to a different" +" instance while retaining all data, much like a USB drive." +msgstr "" + +#: ./doc/training-guides/module001-ch011-block-storage.xml19(guilabel) +msgid "Ephemeral Storage" +msgstr "" + +#: ./doc/training-guides/module001-ch011-block-storage.xml20(para) +msgid "" +"Ephemeral storage is associated with a single unique instance. Its size is " +"defined by the flavor of the instance." +msgstr "" + +#: ./doc/training-guides/module001-ch011-block-storage.xml22(para) +msgid "" +"Data on ephemeral storage ceases to exist when the instance it is associated" +" with is terminated. Rebooting the VM or restarting the host server, " +"however, will not destroy ephemeral data. In the typical use case an " +"instance's root filesystem is stored on ephemeral storage. This is often an " +"unpleasant surprise for people unfamiliar with the cloud model of computing." +msgstr "" + +#: ./doc/training-guides/module001-ch011-block-storage.xml28(para) +msgid "" +"In addition to the ephemeral root volume all flavors except the smallest, " +"m1.tiny, provide an additional ephemeral block device varying from 20G for " +"the m1.small through 160G for the m1.xlarge by default - these sizes are " +"configurable. This is presented as a raw block device with no partition " +"table or filesystem. Cloud aware operating system images may discover, " +"format, and mount this device. For example the cloud-init package included " +"in Ubuntu's stock cloud images will format this space as an ext3 filesystem " +"and mount it on /mnt. It is important to note this a feature of the guest " +"operating system. OpenStack only provisions the raw storage." +msgstr "" + +#: ./doc/training-guides/module001-ch011-block-storage.xml39(guilabel) +msgid "Volume Storage" +msgstr "" + +#: ./doc/training-guides/module001-ch011-block-storage.xml40(para) +msgid "" +"Volume storage is independent of any particular instance and is persistent. " +"Volumes are user created and within quota and availability limits may be of " +"any arbitrary size." +msgstr "" + +#: ./doc/training-guides/module001-ch011-block-storage.xml43(para) +msgid "" +"When first created volumes are raw block devices with no partition table and" +" no filesystem. They must be attached to an instance to be partitioned " +"and/or formatted. Once this is done they may be used much like an external " +"disk drive. Volumes may attached to only one instance at a time, but may be " +"detached and reattached to either the same or different instances." +msgstr "" + +#: ./doc/training-guides/module001-ch011-block-storage.xml49(para) +msgid "" +"It is possible to configure a volume so that it is bootable and provides a " +"persistent virtual instance similar to traditional non-cloud based " +"virtualization systems. In this use case the resulting instance may still " +"have ephemeral storage depending on the flavor selected, but the root " +"filesystem (and possibly others) will be on the persistent volume and thus " +"state will be maintained even if the instance is shutdown. Details of this " +"configuration are discussed in theOpenStack End User Guide." +msgstr "" + +#: ./doc/training-guides/module001-ch011-block-storage.xml59(para) +msgid "" +"Volumes do not provide concurrent access from multiple instances. For that " +"you need either a traditional network filesystem like NFS or CIFS or a " +"cluster filesystem such as GlusterFS. These may be built within an OpenStack" +" cluster or provisioned outside of it, but are not features provided by the " +"OpenStack software." +msgstr "" + +#: ./doc/training-guides/module001-ch011-block-storage.xml65(para) +msgid "" +"The OpenStack Block Storage service works via the interaction of a series of" +" daemon processes named cinder-* that reside persistently on the host " +"machine or machines. The binaries can all be run from a single node, or " +"spread across multiple nodes. They can also be run on the same node as other" +" OpenStack services." +msgstr "" + +#: ./doc/training-guides/module001-ch011-block-storage.xml71(guilabel) +msgid "The current services available in OpenStack Block Storage are:" +msgstr "" + +#: ./doc/training-guides/module001-ch011-block-storage.xml75(para) +msgid "" +"cinder-api - The cinder-api service is a " +"WSGI app that authenticates and routes requests throughout the Block Storage" +" system. It supports the OpenStack API's only, although there is a " +"translation that can be done via Nova's EC2 interface which calls in to the " +"cinderclient." +msgstr "" + +#: ./doc/training-guides/module001-ch011-block-storage.xml85(para) +msgid "" +"cinder-scheduler - The cinder-scheduler " +"is responsible for scheduling/routing requests to the appropriate volume " +"service. As of Grizzly; depending upon your configuration this may be simple" +" round-robin scheduling to the running volume services, or it can be more " +"sophisticated through the use of the Filter Scheduler. The Filter Scheduler " +"is the default in Grizzly and enables filter on things like Capacity, " +"Availability Zone, Volume Types and Capabilities as well as custom filters." +msgstr "" + +#: ./doc/training-guides/module001-ch011-block-storage.xml99(para) +msgid "" +"cinder-volume - The cinder-volume service" +" is responsible for managing Block Storage devices, specifically the back-" +"end devices themselves." +msgstr "" + +#: ./doc/training-guides/module001-ch011-block-storage.xml107(para) +msgid "" +"cinder-backup - The cinder-backup service" +" provides a means to back up a Cinder Volume to OpenStack Object Store " +"(SWIFT)." +msgstr "" + +#: ./doc/training-guides/module001-ch011-block-storage.xml112(guilabel) +msgid "Introduction to OpenStack Block Storage" +msgstr "" + +#: ./doc/training-guides/module001-ch011-block-storage.xml114(para) +msgid "" +"OpenStack Block Storage provides persistent High Performance Block Storage " +"resources that can be consumed by OpenStack Compute instances. This includes" +" secondary attached storage similar to Amazon's Elastic Block Storage (EBS)." +" In addition images can be written to a Block Storage device and specified " +"for OpenStack Compute to use a bootable persistent instance." +msgstr "" + +#: ./doc/training-guides/module001-ch011-block-storage.xml120(para) +msgid "" +"There are some differences from Amazon's EBS that one should be aware of. " +"OpenStack Block Storage is not a shared storage solution like NFS, but " +"currently is designed so that the device is attached and in use by a single " +"instance at a time." +msgstr "" + +#: ./doc/training-guides/module001-ch011-block-storage.xml124(guilabel) +msgid "Backend Storage Devices" +msgstr "" + +#: ./doc/training-guides/module001-ch011-block-storage.xml125(para) +msgid "" +"OpenStack Block Storage requires some form of back-end storage that the " +"service is built on. The default implementation is to use LVM on a local " +"Volume Group named \"cinder-volumes\". In addition to the base driver " +"implementation, OpenStack Block Storage also provides the means to add " +"support for other storage devices to be utilized such as external Raid " +"Arrays or other Storage appliances." +msgstr "" + +#: ./doc/training-guides/module001-ch011-block-storage.xml132(guilabel) +#: ./doc/training-guides/module001-ch005-vm-provisioning-walk-through.xml73(guilabel) +msgid "Users and Tenants (Projects)" +msgstr "" + +#: ./doc/training-guides/module001-ch011-block-storage.xml133(para) +msgid "" +"The OpenStack Block Storage system is designed to be used by many different " +"cloud computing consumers or customers, basically tenants on a shared " +"system, using role-based access assignments. Roles control the actions that " +"a user is allowed to perform. In the default configuration, most actions do " +"not require a particular role, but this is configurable by the system " +"administrator editing the appropriate policy.json file that maintains the " +"rules. A user's access to particular volumes is limited by tenant, but the " +"username and password are assigned per user. Key pairs granting access to a " +"volume are enabled per user, but quotas to control resource consumption " +"across available hardware resources are per tenant." +msgstr "" + +#: ./doc/training-guides/module001-ch011-block-storage.xml145(guilabel) +#: ./doc/training-guides/module001-ch005-vm-provisioning-walk-through.xml97(para) +msgid "For tenants, quota controls are available to limit the:" +msgstr "" + +#: ./doc/training-guides/module001-ch011-block-storage.xml149(para) +#: ./doc/training-guides/module001-ch005-vm-provisioning-walk-through.xml101(para) +msgid "Number of volumes which may be created" +msgstr "" + +#: ./doc/training-guides/module001-ch011-block-storage.xml152(para) +msgid "Number of snapshots which may be created" +msgstr "" + +#: ./doc/training-guides/module001-ch011-block-storage.xml155(para) +msgid "" +"Total number of Giga Bytes allowed per tenant (shared between snapshots and " +"volumes)" +msgstr "" + +#: ./doc/training-guides/module001-ch011-block-storage.xml159(guilabel) +msgid "Volumes Snapshots and Backups" +msgstr "" + +#: ./doc/training-guides/module001-ch011-block-storage.xml160(para) +msgid "" +"This introduction provides a high level overview of the two basic resources " +"offered by the OpenStack Block Storage service. The first is Volumes and the" +" second is Snapshots which are derived from Volumes." +msgstr "" + +#: ./doc/training-guides/module001-ch011-block-storage.xml164(guilabel) +#: ./doc/training-guides/module001-ch006-overview-horizon-cli.xml129(emphasis) +msgid "Volumes" +msgstr "" + +#: ./doc/training-guides/module001-ch011-block-storage.xml165(para) +msgid "" +"Volumes are allocated block storage resources that can be attached to " +"instances as secondary storage or they can be used as the root store to boot" +" instances. Volumes are persistent R/W Block Storage devices most commonly " +"attached to the Compute node via iSCSI." +msgstr "" + +#: ./doc/training-guides/module001-ch011-block-storage.xml170(guilabel) +msgid "Snapshots" +msgstr "" + +#: ./doc/training-guides/module001-ch011-block-storage.xml171(para) +msgid "" +"A Snapshot in OpenStack Block Storage is a read-only point in time copy of a" +" Volume. The Snapshot can be created from a Volume that is currently in use " +"(via the use of '--force True') or in an available state. The Snapshot can " +"then be used to create a new volume via create from snapshot." +msgstr "" + +#: ./doc/training-guides/module001-ch011-block-storage.xml176(guilabel) +msgid "Backups" +msgstr "" + +#: ./doc/training-guides/module001-ch011-block-storage.xml177(para) +msgid "" +"A Backup is an archived copy of a Volume currently stored in Object Storage " +"(Swift)." +msgstr "" + +#: ./doc/training-guides/module001-ch011-block-storage.xml179(guilabel) +msgid "Managing Volumes" +msgstr "" + +#: ./doc/training-guides/module001-ch011-block-storage.xml180(para) +msgid "" +"Cinder is the OpenStack service that allows you to give extra block level " +"storage to your OpenStack Compute instances. You may recognize this as a " +"similar offering from Amazon EC2 known as Elastic Block Storage (EBS). The " +"default Cinder implementation is an iSCSI solution that employs the use of " +"Logical Volume Manager (LVM) for Linux. Note that a volume may only be " +"attached to one instance at a time. This is not a ‘shared storage’ solution " +"like a SAN of NFS on which multiple servers can attach to. It's also " +"important to note that Cinder also includes a number of drivers to allow you" +" to use a number of other vendor's back-end storage devices in addition to " +"or instead of the base LVM implementation." +msgstr "" + +#: ./doc/training-guides/module001-ch011-block-storage.xml192(para) +msgid "" +"Here is brief walk-through of a simple create/attach sequence, keep in mind " +"this requires proper configuration of both OpenStack Compute via cinder.conf" +" and OpenStack Block Storage via cinder.conf." +msgstr "" + +#: ./doc/training-guides/module001-ch011-block-storage.xml198(para) +msgid "" +"The volume is created via cinder create; which creates an LV into the volume" +" group (VG) \"cinder-volumes\"" +msgstr "" + +#: ./doc/training-guides/module001-ch011-block-storage.xml202(para) +msgid "" +"The volume is attached to an instance via nova volume-attach; which creates " +"a unique iSCSI IQN that will be exposed to the compute node" +msgstr "" + +#: ./doc/training-guides/module001-ch011-block-storage.xml207(para) +msgid "" +"The compute node which run the concerned instance has now an active ISCSI " +"session; and a new local storage (usually a /dev/sdX disk)" +msgstr "" + +#: ./doc/training-guides/module001-ch011-block-storage.xml212(para) +msgid "" +"libvirt uses that local storage as a storage for the instance; the instance " +"get a new disk (usually a /dev/vdX disk)" +msgstr "" + +#: ./doc/training-guides/module001-ch011-block-storage.xml217(guilabel) +msgid "Block Storage Capabilities" +msgstr "" + +#: ./doc/training-guides/module001-ch011-block-storage.xml220(para) +#: ./doc/training-guides/module001-ch003-core-projects.xml374(para) +msgid "" +"OpenStack provides persistent block level storage devices for use with " +"OpenStack compute instances." +msgstr "" + +#: ./doc/training-guides/module001-ch011-block-storage.xml224(para) +#: ./doc/training-guides/module001-ch003-core-projects.xml378(para) +msgid "" +"The block storage system manages the creation, attaching and detaching of " +"the block devices to servers. Block storage volumes are fully integrated " +"into OpenStack Compute and the Dashboard allowing for cloud users to manage " +"their own storage needs." +msgstr "" + +#: ./doc/training-guides/module001-ch011-block-storage.xml231(para) +#: ./doc/training-guides/module001-ch003-core-projects.xml385(para) +msgid "" +"In addition to using simple Linux server storage, it has unified storage " +"support for numerous storage platforms including Ceph, NetApp, Nexenta, " +"SolidFire, and Zadara." +msgstr "" + +#: ./doc/training-guides/module001-ch011-block-storage.xml237(para) +#: ./doc/training-guides/module001-ch003-core-projects.xml391(para) +msgid "" +"Block storage is appropriate for performance sensitive scenarios such as " +"database storage, expandable file systems, or providing a server with access" +" to raw block level storage." +msgstr "" + +#: ./doc/training-guides/module001-ch011-block-storage.xml243(para) +#: ./doc/training-guides/module001-ch003-core-projects.xml397(para) +msgid "" +"Snapshot management provides powerful functionality for backing up data " +"stored on block storage volumes. Snapshots can be restored or used to create" +" a new block storage volume." +msgstr "" + +#: ./doc/training-guides/bk001-ch012-associate-review-concept.xml6(title) +msgid "Review of Concepts" +msgstr "" + +#: ./doc/training-guides/bk001-ch012-associate-review-concept.xml8(title) +msgid "Day 2, 16:00 to 17:00" +msgstr "" + +#: ./doc/training-guides/bk002-ch015-operator-object-storage-node-quiz.xml6(title) +#: ./doc/training-guides/bk001-bk010-associate-object-storage-node-quiz.xml5(title) +msgid "Object Storage Node Quiz" +msgstr "" + +#: ./doc/training-guides/bk002-ch015-operator-object-storage-node-quiz.xml8(title) +msgid "Day 9, 16:40 to 17:00" +msgstr "" + +#. When image changes, this message will be marked fuzzy or untranslated for +#. you. +#. It doesn't matter what you translate it to: it's not used at all. +#: ./doc/training-guides/module001-ch001-intro-text.xml102(None) +msgid "@@image: 'figures/image11.png'; md5=e7c8929df3b2e7037fa3a032a7e8370e" +msgstr "" + +#: ./doc/training-guides/module001-ch001-intro-text.xml6(title) +#: ./doc/training-guides/module001-intro-openstack.xml5(title) +msgid "Introduction to OpenStack" +msgstr "" + +#: ./doc/training-guides/module001-ch001-intro-text.xml7(para) +msgid "" +"OpenStack is a cloud operating system that controls large pools of compute, " +"storage, and networking resources throughout a data center, all managed " +"through a dashboard that gives administrators control while empowering users" +" to provision resources through a web interface." +msgstr "" + +#: ./doc/training-guides/module001-ch001-intro-text.xml12(para) +msgid "" +"Cloud computing provides users with access to a shared collection of " +"computing resources: networks for transfer, servers for storage, and " +"applications or services for completing tasks." +msgstr "" + +#: ./doc/training-guides/module001-ch001-intro-text.xml16(para) +msgid "The compelling features of a cloud are:" +msgstr "" + +#: ./doc/training-guides/module001-ch001-intro-text.xml19(para) +msgid "" +"On-demand self-service: Users can automatically provision needed computing " +"capabilities, such as server time and network storage, without requiring " +"human interaction with each service provider." +msgstr "" + +#: ./doc/training-guides/module001-ch001-intro-text.xml25(para) +msgid "" +"Network access: Any computing capabilities are available over the network. " +"Many different devices are allowed access through standardized mechanisms." +msgstr "" + +#: ./doc/training-guides/module001-ch001-intro-text.xml30(para) +msgid "" +"Resource pooling: Multiple users can access clouds that serve other " +"consumers according to demand." +msgstr "" + +#: ./doc/training-guides/module001-ch001-intro-text.xml34(para) +msgid "Elasticity: Provisioning is rapid and scales out or is based on need." +msgstr "" + +#: ./doc/training-guides/module001-ch001-intro-text.xml38(para) +msgid "" +"Metered or measured service: Cloud systems can optimize and control resource" +" use at the level that is appropriate for the service. Services include " +"storage, processing, bandwidth, and active user accounts. Monitoring and " +"reporting of resource usage provides transparency for both the provider and " +"consumer of the utilized service." +msgstr "" + +#: ./doc/training-guides/module001-ch001-intro-text.xml46(para) +msgid "" +"Cloud computing offers different service models depending on the " +"capabilities a consumer may require." +msgstr "" + +#: ./doc/training-guides/module001-ch001-intro-text.xml50(para) +msgid "" +"SaaS: Software as a Service. Provides the consumer the ability to use the " +"software in a cloud environment, such as web-based email for example." +msgstr "" + +#: ./doc/training-guides/module001-ch001-intro-text.xml55(para) +msgid "" +"PaaS: Platform as a Service. Provides the consumer the ability to deploy " +"applications through a programming language or tools supported by the cloud " +"platform provider. An example of platform as a service is an Eclipse/Java " +"programming platform provided with no downloads required." +msgstr "" + +#: ./doc/training-guides/module001-ch001-intro-text.xml62(para) +msgid "" +"IaaS: Infrastructure as a Service. Provides infrastructure such as computer " +"instances, network connections, and storage so that people can run any " +"software or operating system." +msgstr "" + +#: ./doc/training-guides/module001-ch001-intro-text.xml68(para) +msgid "" +"Terms such as public cloud or private cloud refer to the deployment model " +"for the cloud. A private cloud operates for a single organization, but can " +"be managed on-premise or off-premise. A public cloud has an infrastructure " +"that is available to the general public or a large industry group and is " +"likely owned by a cloud services company." +msgstr "" + +#: ./doc/training-guides/module001-ch001-intro-text.xml74(para) +msgid "" +"Clouds can also be described as hybrid. A hybrid cloud can be a deployment " +"model, as a composition of both public and private clouds, or a hybrid model" +" for cloud computing may involve both virtual and physical servers." +msgstr "" + +#: ./doc/training-guides/module001-ch001-intro-text.xml78(para) +msgid "" +"Cloud computing can help with large-scale computing needs or can lead " +"consolidation efforts by virtualizing servers to make more use of existing " +"hardware and potentially release old hardware from service. Cloud computing " +"is also used for collaboration because of its high availability through " +"networked computers. Productivity suites for word processing, number " +"crunching, and email communications, and more are also available through " +"cloud computing. Cloud computing also avails additional storage to the cloud" +" user, avoiding the need for additional hard drives on each user's desktop " +"and enabling access to huge data storage capacity online in the cloud." +msgstr "" + +#: ./doc/training-guides/module001-ch001-intro-text.xml89(para) +msgid "" +"When you explore OpenStack and see what it means technically, you can see " +"its reach and impact on the entire world." +msgstr "" + +#: ./doc/training-guides/module001-ch001-intro-text.xml91(para) +msgid "" +"OpenStack is an open source software for building private and public clouds " +"which delivers a massively scalable cloud operating system." +msgstr "" + +#: ./doc/training-guides/module001-ch001-intro-text.xml97(td) +msgid "" +"OpenStack is backed up by a global community of technologists, developers, " +"researchers, corporations and cloud computing experts." +msgstr "" + +#: ./doc/training-guides/lab000-important-terms.xml6(title) +msgid "Important terms" +msgstr "" + +#: ./doc/training-guides/lab000-important-terms.xml8(title) +msgid "Host Operating System (Host)" +msgstr "" + +#: ./doc/training-guides/lab000-important-terms.xml9(para) +msgid "" +"The operating system that is installed on your laptop or desktop that hosts " +"virtual machines. Commonly referred to as host OS or " +"host. In short, the machine where your Virtual Box is" +" installed." +msgstr "" + +#: ./doc/training-guides/lab000-important-terms.xml16(title) +msgid "Guest Operating System (Guest)" +msgstr "" + +#: ./doc/training-guides/lab000-important-terms.xml17(para) +msgid "" +"The operating system that is installed on your Virtual Box Virtual Machine. " +"This virtual instance is independent of the host OS. Commonly referred to as" +" guest OS or guest." +msgstr "" + +#: ./doc/training-guides/lab000-important-terms.xml23(title) +msgid "Node" +msgstr "" + +#: ./doc/training-guides/lab000-important-terms.xml24(para) +msgid "" +"In this context, refers specifically to servers. Each OpenStack server is a " +"node." +msgstr "" + +#: ./doc/training-guides/lab000-important-terms.xml28(title) +#: ./doc/training-guides/lab001-control-node.xml7(title) +msgid "Control Node" +msgstr "" + +#: ./doc/training-guides/lab000-important-terms.xml29(para) +msgid "" +"Hosts the database, Keystone (Middleware), and the servers for the scope of " +"the current OpenStack deployment. Acts as the brains behind OpenStack and " +"drives services such as authentication, database, and so on." +msgstr "" + +#: ./doc/training-guides/lab000-important-terms.xml35(title) +#: ./doc/training-guides/lab003-compute-node.xml7(title) +#: ./doc/training-guides/lab003-compute-node.xml28(guilabel) +#: ./doc/training-guides/bk002-ch007-operator-compute-node.xml8(title) +#: ./doc/training-guides/bk001-ch005-associate-compute-node.xml8(title) +msgid "Compute Node" +msgstr "" + +#: ./doc/training-guides/lab000-important-terms.xml36(para) +msgid "" +"Has the required Hypervisor (Qemu/KVM) and is your Virtual Machine host." +msgstr "" + +#: ./doc/training-guides/lab000-important-terms.xml40(title) +#: ./doc/training-guides/lab002-network-node.xml4(title) +#: ./doc/training-guides/lab002-network-node.xml23(guilabel) +#: ./doc/training-guides/bk002-ch010-operator-network-node.xml8(title) +#: ./doc/training-guides/bk001-ch007-associate-network-node.xml8(title) +msgid "Network Node" +msgstr "" + +#: ./doc/training-guides/lab000-important-terms.xml41(para) +msgid "Provides Network-as-a-Service and virtual networks for OpenStack." +msgstr "" + +#: ./doc/training-guides/lab000-important-terms.xml45(title) +msgid "Using OpenSSH" +msgstr "" + +#: ./doc/training-guides/lab000-important-terms.xml46(para) +msgid "" +"After you set up the network interfaces file, you can switch to an SSH " +"session by using an OpenSSH client to log in remotely to the required server" +" node (Control, Network, Compute). Open a terminal on your host machine. Run" +" the following command: " +msgstr "" + +#: ./doc/training-guides/card007-core-overview.xml7(title) +msgid "Core Project Overview" +msgstr "" + +#: ./doc/training-guides/bk002-ch014-operator-object-storage-node-lab.xml6(title) +msgid "Object Storage Node Lab" +msgstr "" + +#: ./doc/training-guides/bk002-ch014-operator-object-storage-node-lab.xml8(title) +msgid "Day 9, 13:30 to 14:45, 15:00 to 17:00" +msgstr "" + +#: ./doc/training-guides/st-training-guides.xml9(title) +#: ./doc/training-guides/st-training-guides.xml11(titleabbrev) +#: ./doc/training-guides/st-training-guides.xml17(productname) +msgid "OpenStack Training Guides" +msgstr "" + +#: ./doc/training-guides/st-training-guides.xml14(year) +msgid "2013" +msgstr "" + +#: ./doc/training-guides/st-training-guides.xml15(holder) +msgid "OpenStack Foundation" +msgstr "" + +#: ./doc/training-guides/st-training-guides.xml20(remark) +#: ./doc/training-guides/st-training-guides.xml24(remark) +msgid "Copyright details are filled in by the template." +msgstr "" + +#: ./doc/training-guides/st-training-guides.xml28(para) +msgid "" +"OpenStack™ Training Guides offer the open source community software training" +" for cloud administration and management for any organization." +msgstr "" + +#: ./doc/training-guides/st-training-guides.xml35(date) +msgid "2013-11-04" +msgstr "" + +#: ./doc/training-guides/st-training-guides.xml39(para) +msgid "major restructure of guides" +msgstr "" + +#: ./doc/training-guides/st-training-guides.xml45(date) +msgid "2013-09-11" +msgstr "" + +#: ./doc/training-guides/st-training-guides.xml49(para) +msgid "first training guides sprint held" +msgstr "" + +#: ./doc/training-guides/st-training-guides.xml55(date) +msgid "2013-08-07" +msgstr "" + +#: ./doc/training-guides/st-training-guides.xml59(para) +msgid "rough draft published to the web" +msgstr "" + +#: ./doc/training-guides/st-training-guides.xml65(date) +msgid "2013-07-09" +msgstr "" + +#: ./doc/training-guides/st-training-guides.xml69(para) +msgid "first draft released" +msgstr "" + +#: ./doc/training-guides/st-training-guides.xml75(date) +msgid "2013-06-18" +msgstr "" + +#: ./doc/training-guides/st-training-guides.xml79(para) +msgid "blueprint created" +msgstr "" + +#. When image changes, this message will be marked fuzzy or untranslated for +#. you. +#. It doesn't matter what you translate it to: it's not used at all. +#: ./doc/training-guides/module001-ch005-vm-provisioning-walk-through.xml175(None) +msgid "@@image: 'figures/image21.png'; md5=77049345dd5d86f8f7abe03c0497b1f2" +msgstr "" + +#. When image changes, this message will be marked fuzzy or untranslated for +#. you. +#. It doesn't matter what you translate it to: it's not used at all. +#: ./doc/training-guides/module001-ch005-vm-provisioning-walk-through.xml193(None) +msgid "@@image: 'figures/image09.png'; md5=69ea6c4853c189bd8c387bb4e534f6a2" +msgstr "" + +#. When image changes, this message will be marked fuzzy or untranslated for +#. you. +#. It doesn't matter what you translate it to: it's not used at all. +#: ./doc/training-guides/module001-ch005-vm-provisioning-walk-through.xml229(None) +msgid "@@image: 'figures/image22.png'; md5=d92dca8de8639d5a26cef1c8fcc592ed" +msgstr "" + +#: ./doc/training-guides/module001-ch005-vm-provisioning-walk-through.xml7(title) +msgid "VM Provisioning Walk Through" +msgstr "" + +#: ./doc/training-guides/module001-ch005-vm-provisioning-walk-through.xml8(para) +#: ./doc/training-guides/module001-ch010-vm-provisioning-indepth.xml8(para) +msgid "More Content To be Added ..." +msgstr "" + +#: ./doc/training-guides/module001-ch005-vm-provisioning-walk-through.xml9(para) +msgid "" +"OpenStack Compute gives you a tool to orchestrate a cloud, including running" +" instances, managing networks, and controlling access to the cloud through " +"users and projects. The underlying open source project's name is Nova, and " +"it provides the software that can control an Infrastructure as a Service " +"(IaaS) cloud computing platform. It is similar in scope to Amazon EC2 and " +"Rackspace Cloud Servers. OpenStack Compute does not include any " +"virtualization software; rather it defines drivers that interact with " +"underlying virtualization mechanisms that run on your host operating system," +" and exposes functionality over a web-based API." +msgstr "" + +#: ./doc/training-guides/module001-ch005-vm-provisioning-walk-through.xml20(guilabel) +msgid "Hypervisors" +msgstr "" + +#: ./doc/training-guides/module001-ch005-vm-provisioning-walk-through.xml21(para) +msgid "" +"OpenStack Compute requires a hypervisor and Compute controls the hypervisors" +" through an API server. The process for selecting a hypervisor usually means" +" prioritizing and making decisions based on budget and resource constraints " +"as well as the inevitable list of supported features and required technical " +"specifications. The majority of development is done with the KVM and Xen-" +"based hypervisors. Refer to http://goo.gl/n7AXnC for a detailed " +"list of features and support across the hypervisors." +msgstr "" + +#: ./doc/training-guides/module001-ch005-vm-provisioning-walk-through.xml32(para) +msgid "" +"With OpenStack Compute, you can orchestrate clouds using multiple " +"hypervisors in different zones. The types of virtualization standards that " +"may be used with Compute include:" +msgstr "" + +#: ./doc/training-guides/module001-ch005-vm-provisioning-walk-through.xml38(para) +msgid "" +"KVM- Kernel-based Virtual Machine (visit http://goo.gl/70dvRb)" +msgstr "" + +#: ./doc/training-guides/module001-ch005-vm-provisioning-walk-through.xml43(para) +msgid "" +"LXC- Linux Containers (through libvirt) (visit http://goo.gl/Ous3ly)" +msgstr "" + +#: ./doc/training-guides/module001-ch005-vm-provisioning-walk-through.xml48(para) +msgid "" +"QEMU- Quick EMUlator (visit http://goo.gl/WWV9lL)" +msgstr "" + +#: ./doc/training-guides/module001-ch005-vm-provisioning-walk-through.xml53(para) +msgid "" +"UML- User Mode Linux (visit http://goo.gl/4HAkJj)" +msgstr "" + +#: ./doc/training-guides/module001-ch005-vm-provisioning-walk-through.xml58(para) +msgid "" +"VMWare vSphere4.1 update 1 and newer (visit http://goo.gl/0DBeo5)" +msgstr "" + +#: ./doc/training-guides/module001-ch005-vm-provisioning-walk-through.xml63(para) +msgid "" +"Xen- Xen, Citrix XenServer and Xen Cloud Platform (XCP) (visit http://goo.gl/yXP9t1)" +msgstr "" + +#: ./doc/training-guides/module001-ch005-vm-provisioning-walk-through.xml68(para) +msgid "" +"Bare Metal- Provisions physical hardware via pluggable sub-drivers. (visit " +"http://goo.gl/exfeSg)" +msgstr "" + +#: ./doc/training-guides/module001-ch005-vm-provisioning-walk-through.xml74(para) +msgid "" +"The OpenStack Compute system is designed to be used by many different cloud " +"computing consumers or customers, basically tenants on a shared system, " +"using role-based access assignments. Roles control the actions that a user " +"is allowed to perform. In the default configuration, most actions do not " +"require a particular role, but this is configurable by the system " +"administrator editing the appropriate policy.json file that maintains the " +"rules. For example, a rule can be defined so that a user cannot allocate a " +"public IP without the admin role. A user's access to particular images is " +"limited by tenant, but the username and password are assigned per user. Key " +"pairs granting access to an instance are enabled per user, but quotas to " +"control resource consumption across available hardware resources are per " +"tenant." +msgstr "" + +#: ./doc/training-guides/module001-ch005-vm-provisioning-walk-through.xml88(para) +msgid "" +"While the original EC2 API supports users, OpenStack Compute adds the " +"concept of tenants. Tenants are isolated resource containers forming the " +"principal organizational structure within the Compute service. They consist " +"of a separate VLAN, volumes, instances, images, keys, and users. A user can " +"specify which tenant he or she wishes to be known as by appending " +":project_id to his or her access key. If no tenant is specified in the API " +"request, Compute attempts to use a tenant with the same ID as the user" +msgstr "" + +#: ./doc/training-guides/module001-ch005-vm-provisioning-walk-through.xml104(para) +msgid "Total size of all volumes within a project as measured in GB" +msgstr "" + +#: ./doc/training-guides/module001-ch005-vm-provisioning-walk-through.xml108(para) +msgid "Number of instances which may be launched" +msgstr "" + +#: ./doc/training-guides/module001-ch005-vm-provisioning-walk-through.xml111(para) +msgid "Number of processor cores which may be allocated" +msgstr "" + +#: ./doc/training-guides/module001-ch005-vm-provisioning-walk-through.xml114(para) +msgid "" +"Floating IP addresses (assigned to any instance when it launches so the " +"instance has the same publicly accessible IP addresses)" +msgstr "" + +#: ./doc/training-guides/module001-ch005-vm-provisioning-walk-through.xml119(para) +msgid "" +"Fixed IP addresses (assigned to the same instance each time it boots, " +"publicly or privately accessible, typically private for management purposes)" +msgstr "" + +#: ./doc/training-guides/module001-ch005-vm-provisioning-walk-through.xml124(guilabel) +#: ./doc/training-guides/module001-ch005-vm-provisioning-walk-through.xml162(guilabel) +msgid "Images and Instances" +msgstr "" + +#: ./doc/training-guides/module001-ch005-vm-provisioning-walk-through.xml125(para) +msgid "" +"This introduction provides a high level overview of what images and " +"instances are and description of the life-cycle of a typical virtual system " +"within the cloud. There are many ways to configure the details of an " +"OpenStack cloud and many ways to implement a virtual system within that " +"cloud. These configuration details as well as the specific command line " +"utilities and API calls to perform the actions described are presented in " +"the Image Managementand Volume Managementchapters." +msgstr "" + +#: ./doc/training-guides/module001-ch005-vm-provisioning-walk-through.xml134(para) +msgid "" +"Images are disk images which are templates for virtual machine file systems." +" The image service, Glance, is responsible for the storage and management of" +" images within OpenStack." +msgstr "" + +#: ./doc/training-guides/module001-ch005-vm-provisioning-walk-through.xml138(para) +msgid "" +"Instances are the individual virtual machines running on physical compute " +"nodes. The compute service, Nova, manages instances. Any number of instances" +" maybe started from the same image. Each instance is run from a copy of the " +"base image so runtime changes made by an instance do not change the image it" +" is based on. Snapshots of running instances may be taken which create a new" +" image based on the current disk state of a particular instance." +msgstr "" + +#: ./doc/training-guides/module001-ch005-vm-provisioning-walk-through.xml146(para) +msgid "" +"When starting an instance a set of virtual resources known as a flavor must " +"be selected. Flavors define how many virtual CPUs an instance has and the " +"amount of RAM and size of its ephemeral disks. OpenStack provides a number " +"of predefined flavors which cloud administrators may edit or add to. Users " +"must select from the set of available flavors defined on their cloud." +msgstr "" + +#: ./doc/training-guides/module001-ch005-vm-provisioning-walk-through.xml153(para) +msgid "" +"Additional resources such as persistent volume storage and public IP address" +" may be added to and removed from running instances. The examples below show" +" the cinder-volume service which provide persistent block storage as opposed" +" to the ephemeral storage provided by the instance flavor." +msgstr "" + +#: ./doc/training-guides/module001-ch005-vm-provisioning-walk-through.xml158(para) +msgid "" +"Here is an example of the life cycle of a typical virtual system within an " +"OpenStack cloud to illustrate these concepts." +msgstr "" + +#: ./doc/training-guides/module001-ch005-vm-provisioning-walk-through.xml161(guilabel) +#: ./doc/training-guides/module001-ch005-vm-provisioning-walk-through.xml172(title) +msgid "Initial State" +msgstr "" + +#: ./doc/training-guides/module001-ch005-vm-provisioning-walk-through.xml163(para) +msgid "" +"The following diagram shows the system state prior to launching an instance." +" The image store fronted by the image service, Glance, has some number of " +"predefined images. In the cloud there is an available compute node with " +"available vCPU, memory and local disk resources. Plus there are a number of " +"predefined volumes in the cinder-volume service." +msgstr "" + +#: ./doc/training-guides/module001-ch005-vm-provisioning-walk-through.xml169(para) +msgid "Figure 2.1. Base image state with no running instances" +msgstr "" + +#: ./doc/training-guides/module001-ch005-vm-provisioning-walk-through.xml179(guilabel) +msgid "Launching an instance" +msgstr "" + +#: ./doc/training-guides/module001-ch005-vm-provisioning-walk-through.xml180(para) +msgid "" +"To launch an instance the user selects an image, a flavor and optionally " +"other attributes. In this case the selected flavor provides a root volume " +"(as all flavors do) labeled vda in the diagram and additional ephemeral " +"storage labeled vdb in the diagram. The user has also opted to map a volume " +"from the cinder-volume store to the third virtual disk, vdc, on this " +"instance." +msgstr "" + +#: ./doc/training-guides/module001-ch005-vm-provisioning-walk-through.xml187(para) +msgid "Figure 2.2. Instance creation from image and run time state" +msgstr "" + +#: ./doc/training-guides/module001-ch005-vm-provisioning-walk-through.xml190(title) +msgid "Launch VM Instance" +msgstr "" + +#: ./doc/training-guides/module001-ch005-vm-provisioning-walk-through.xml197(para) +msgid "" +"The OpenStack system copies the base image from the image store to local " +"disk which is used as the first disk of the instance (vda). Having small " +"images will result in faster start up of your instances as less data needs " +"to be copied across the network. The system also creates a new empty disk " +"image to present as the second disk (vdb). Be aware that the second disk is " +"an empty disk with an emphemeral life as it is destroyed when you delete the" +" instance. The compute node attaches to the requested cinder-volume using " +"iSCSI and maps this to the third disk (vdc) as requested. The vCPU and " +"memory resources are provisioned and the instance is booted from the first " +"drive. The instance runs and changes data on the disks indicated in red in " +"the diagram." +msgstr "" + +#: ./doc/training-guides/module001-ch005-vm-provisioning-walk-through.xml210(para) +msgid "" +"There are many possible variations in the details of the scenario, " +"particularly in terms of what the backing storage is and the network " +"protocols used to attach and move storage. One variant worth mentioning here" +" is that the ephemeral storage used for volumes vda and vdb in this example " +"may be backed by network storage rather than local disk. The details are " +"left for later chapters." +msgstr "" + +#: ./doc/training-guides/module001-ch005-vm-provisioning-walk-through.xml217(guilabel) +#: ./doc/training-guides/module001-ch005-vm-provisioning-walk-through.xml226(title) +msgid "End State" +msgstr "" + +#: ./doc/training-guides/module001-ch005-vm-provisioning-walk-through.xml218(para) +msgid "" +"Once the instance has served its purpose and is deleted all state is " +"reclaimed, except the persistent volume. The ephemeral storage is purged. " +"Memory and vCPU resources are released. And of course the image has remained" +" unchanged throughout." +msgstr "" + +#: ./doc/training-guides/module001-ch005-vm-provisioning-walk-through.xml223(para) +msgid "Figure 2.3. End state of image and volume after instance exits" +msgstr "" + +#: ./doc/training-guides/module001-ch005-vm-provisioning-walk-through.xml233(para) +msgid "" +"Once you launch a VM in OpenStack, there's something more going on in the " +"background. To understand what's happening behind the Dashboard, lets take a" +" deeper dive into OpenStack’s VM provisioning. For launching a VM, you can " +"either use Command Line Interface or the OpenStack Horizon Dashboard." +msgstr "" + +#: ./doc/training-guides/operator-editing-code.xml7(title) +msgid "Editing Code" +msgstr "" + +#: ./doc/training-guides/operator-editing-code.xml9(title) +msgid "Get Tools and Accounts" +msgstr "" + +#: ./doc/training-guides/operator-editing-code.xml13(para) +msgid "" +"First create a GitHub account at github.com." +msgstr "" + +#: ./doc/training-guides/operator-editing-code.xml16(para) +msgid "" +"Check out https://wiki.openstack.org/wiki/Documentation/HowTo" +" for more extentsive setup instructions" +msgstr "" + +#: ./doc/training-guides/operator-editing-code.xml18(para) +msgid "" +"Download and install Git from http://git-scm.com/downloads" +msgstr "" + +#: ./doc/training-guides/operator-editing-code.xml22(para) +msgid "Create your local repository directory" +msgstr "" + +#: ./doc/training-guides/operator-editing-code.xml26(title) +msgid "Install SourceTree" +msgstr "" + +#: ./doc/training-guides/operator-editing-code.xml29(link) +msgid "http://www.sourcetreeapp.com/download/" +msgstr "" + +#: ./doc/training-guides/operator-editing-code.xml32(para) +msgid "Ignore the Atlassian Bitbucket and Stack setup" +msgstr "" + +#: ./doc/training-guides/operator-editing-code.xml36(para) +msgid "Add your GitHub username and password" +msgstr "" + +#: ./doc/training-guides/operator-editing-code.xml39(para) +msgid "Set your local repository location" +msgstr "" + +#: ./doc/training-guides/operator-editing-code.xml44(title) +msgid "Install an XML editor" +msgstr "" + +#: ./doc/training-guides/operator-editing-code.xml47(para) +msgid "" +"You can download a 30 day trial of Oxygen. The floating licenses donated by " +"OxygenXML have all been handed out.http://www.oxygenxml.com/download_oxygenxml_editor.html" +msgstr "" + +#: ./doc/training-guides/operator-editing-code.xml51(para) +msgid "" +"AND/OR PyCharm http://download.jetbrains.com/python/pycharm-" +"community-3.0.1.dmg" +msgstr "" + +#: ./doc/training-guides/operator-editing-code.xml54(para) +msgid "AND/OR You can use emacs or vi editors." +msgstr "" + +#: ./doc/training-guides/operator-editing-code.xml55(para) +msgid "Here are some great resources on DocBook and Emacs' NXML mode:" +msgstr "" + +#: ./doc/training-guides/operator-editing-code.xml56(link) +msgid "http://paul.frields.org/2011/02/09/xml-editing-with-emacs/" +msgstr "" + +#: ./doc/training-guides/operator-editing-code.xml57(link) +msgid "https://fedoraproject.org/wiki/How_to_use_Emacs_for_XML_editing" +msgstr "" + +#: ./doc/training-guides/operator-editing-code.xml58(link) +msgid "http://infohost.nmt.edu/tcc/help/pubs/nxml/" +msgstr "" + +#: ./doc/training-guides/operator-editing-code.xml59(para) +msgid "If you prefer vi, there are ways to make DocBook editing easier:" +msgstr "" + +#: ./doc/training-guides/operator-editing-code.xml60(link) +msgid "https://fedoraproject.org/wiki/Editing_DocBook_with_Vi" +msgstr "" + +#: ./doc/training-guides/operator-editing-code.xml65(title) +msgid "Install Maven" +msgstr "" + +#: ./doc/training-guides/operator-editing-code.xml71(para) +msgid "" +"Copy the latest stable binary fromhttp://maven.apache.org/download.cgi" +" into /usr/local/apache-maven" +msgstr "" + +#: ./doc/training-guides/operator-editing-code.xml77(para) +msgid "Install maven with " +msgstr "" + +#: ./doc/training-guides/operator-editing-code.xml81(para) +msgid "Add the maven path" +msgstr "" + +#: ./doc/training-guides/operator-editing-code.xml87(para) +msgid "Set your maven user profile settings" +msgstr "" + +#: ./doc/training-guides/operator-editing-code.xml91(para) +msgid "verify maven is setup with" +msgstr "" + +#: ./doc/training-guides/operator-editing-code.xml98(para) +msgid "" +"Create a Launchpad account: Visit " +"https://login.launchpad.net/+new_accountAfter you create this " +"account, the follow-up page is slightly confusing. It doesn't tell you that " +"you are done. (It gives you the opportunity to change your -password, but " +"you do not have to.)" +msgstr "" + +#: ./doc/training-guides/operator-editing-code.xml107(para) +msgid "" +"Add at least one SSH key to your account profile. To do this, follow the " +"instructions on " +"https://help.launchpad.net/YourAccount/CreatingAnSSHKeyPair\"." +msgstr "" + +#: ./doc/training-guides/operator-editing-code.xml113(para) +msgid "" +"Join The OpenStack Foundation: Visit https://www.openstack.org/join." +" Among other privileges, this also allows you to vote in elections and run " +"for elected positions within The OpenStack Project. When signing up for the " +"Foundation Membership, make sure to give the same E-mail address you'll use " +"for code contributions, since the Primary Email Address in you Foundation " +"Profile will need to match the Preferred Email you set later in your Gerrit " +"contact information." +msgstr "" + +#: ./doc/training-guides/operator-editing-code.xml123(para) +msgid "" +"the CLA: Every developer and contributor needs to sign the Individual " +"Contributor License agreement. Visit https:// review.openstack.org/" +" and click the Sign In link at the top-right corner of the page. Log in with" +" your Launchpad ID. You can preview the text of the Individual CLA." +msgstr "" + +#: ./doc/training-guides/operator-editing-code.xml132(para) +msgid "" +"Add your SSH keys to your GitHub account profile (same one as used in " +"Launchpad, they must match). When you copy and paste the SSH key, include " +"the ssh-rsa algorithm and computer identifier. If this is your first time " +"setting up git and Github, be sure to run these steps in a Terminal window:" +msgstr "" + +#: ./doc/training-guides/operator-editing-code.xml141(para) +msgid "" +"Install git-review. If pip is not already installed, use \"sudo easy_install pip\" to install it on a Mac or " +"Ubuntu" +msgstr "" + +#: ./doc/training-guides/operator-editing-code.xml147(para) +msgid "Change to the directory" +msgstr "" + +#: ./doc/training-guides/operator-editing-code.xml151(para) +msgid "Clone the openstack-manuals repository with" +msgstr "" + +#: ./doc/training-guides/operator-editing-code.xml154(para) +msgid "Change directory to the pulled repository" +msgstr "" + +#: ./doc/training-guides/operator-editing-code.xml158(para) +msgid "" +"Enter your Launchpad account information after testing for ssh key setup " +"with" +msgstr "" + +#: ./doc/training-guides/operator-editing-code.xml166(title) +#: ./doc/training-guides/bk002-ch002-operator-getting-started-lab.xml19(title) +msgid "Fix a Documentation Bug" +msgstr "" + +#: ./doc/training-guides/operator-editing-code.xml170(para) +msgid "" +"Note: For this example, we are going to assume bug 1188522 and change 33713" +msgstr "" + +#: ./doc/training-guides/operator-editing-code.xml174(para) +msgid "" +"Bring uphttps://bugs.launchpad.net/openstack-manuals" +msgstr "" + +#: ./doc/training-guides/operator-editing-code.xml179(para) +msgid "" +"Select a bug that is unassigned and that you can fix. Syntax errors are the " +"best ones to start off with." +msgstr "" + +#: ./doc/training-guides/operator-editing-code.xml183(para) +msgid "" +"Using oXygen, open the /Users/<username>/code/openstack-manuals/doc" +"/admin-guide-cloud/bk-admin-guide-cloud.xml master page for this example. It" +" links together the rest of the material. Find the page with the bug. Open " +"the page that is referenced in the bug description by selecting the content " +"in the author view. Verify you have the correct page by visually inspecting " +"the html page and the xml page." +msgstr "" + +#: ./doc/training-guides/operator-editing-code.xml193(para) +msgid "In the shell," +msgstr "" + +#: ./doc/training-guides/operator-editing-code.xml197(para) +msgid "Verify that you are on master with" +msgstr "" + +#: ./doc/training-guides/operator-editing-code.xml201(para) +msgid "Create your working branch off master with" +msgstr "" + +#: ./doc/training-guides/operator-editing-code.xml205(para) +msgid "Verify that you have the branch open through SourceTree" +msgstr "" + +#: ./doc/training-guides/operator-editing-code.xml209(para) +msgid "" +"Correct the bug through oXygen. Toggle back and forth through the different " +"views at the bottom of the editor." +msgstr "" + +#: ./doc/training-guides/operator-editing-code.xml214(para) +msgid "" +"Once the bug is fixed, verify that the documentation can be built without " +"errors by running" +msgstr "" + +#: ./doc/training-guides/operator-editing-code.xml219(para) +msgid "" +"Verify that the HTML page reflects your changes properly. You can open the " +"file from the command line by using the \"open\" command" +msgstr "" + +#: ./doc/training-guides/operator-editing-code.xml223(para) +msgid "Add the changes" +msgstr "" + +#: ./doc/training-guides/operator-editing-code.xml227(para) +msgid "Commit the changes" +msgstr "" + +#: ./doc/training-guides/operator-editing-code.xml232(para) +msgid "Submit the bug fix to Gerrit" +msgstr "" + +#: ./doc/training-guides/operator-editing-code.xml236(para) +msgid "" +"Track the Gerrit review process athttps://review.openstack.org/#/c/33713." +" Follow and respond inline to the Code Review requests and comments." +msgstr "" + +#: ./doc/training-guides/operator-editing-code.xml243(para) +msgid "" +"Your change will be tested, track the Jenkins testing process at " +"https://jenkins.openstack.org" +msgstr "" + +#: ./doc/training-guides/operator-editing-code.xml247(para) +msgid "If your change is rejected, complete the following steps:" +msgstr "" + +#: ./doc/training-guides/operator-editing-code.xml250(para) +msgid "Respond to the inline comments if any" +msgstr "" + +#: ./doc/training-guides/operator-editing-code.xml253(para) +msgid "Update the status to work in progress" +msgstr "" + +#: ./doc/training-guides/operator-editing-code.xml256(para) +msgid "Checkout the patch from the Gerrit change review" +msgstr "" + +#: ./doc/training-guides/operator-editing-code.xml260(para) +msgid "Follow the recommended tweaks to the files" +msgstr "" + +#: ./doc/training-guides/operator-editing-code.xml263(para) +msgid "Rerun" +msgstr "" + +#: ./doc/training-guides/operator-editing-code.xml267(para) +msgid "add your additional changes to the change log" +msgstr "" + +#: ./doc/training-guides/operator-editing-code.xml271(para) +msgid "Final commit" +msgstr "" + +#: ./doc/training-guides/operator-editing-code.xml275(para) +msgid "Update the Jenkins status to change completed" +msgstr "" + +#: ./doc/training-guides/operator-editing-code.xml280(para) +msgid "" +"Follow the jenkins build progress at https://jenkins.openstack.org/view" +"/Openstack-manuals/. Note if the build process fails, the online " +"documentation will not reflect your bug fix." +msgstr "" + +#: ./doc/training-guides/operator-editing-code.xml289(title) +msgid "Submit a Documentation Bug Fix" +msgstr "" + +#: ./doc/training-guides/operator-editing-code.xml293(para) +msgid "" +"Bring up https://bugs.launchpad.net/openstack-" +"manuals/+filebug" +msgstr "" + +#: ./doc/training-guides/operator-editing-code.xml298(para) +msgid "Give your bug a descriptive name" +msgstr "" + +#: ./doc/training-guides/operator-editing-code.xml301(para) +msgid "verify if asked that it is not a duplicate" +msgstr "" + +#: ./doc/training-guides/operator-editing-code.xml304(para) +msgid "Add some more detail into the description field" +msgstr "" + +#: ./doc/training-guides/operator-editing-code.xml307(para) +msgid "" +"Once submitted, select the assigned to pane and select \"assign to me\" or " +"\"sarob\"" +msgstr "" + +#: ./doc/training-guides/operator-editing-code.xml311(para) +msgid "" +"Follow the instructions for fixing a bug in the Fix a Documentation Bug " +"section." +msgstr "" + +#: ./doc/training-guides/operator-editing-code.xml318(title) +#: ./doc/training-guides/bk002-ch002-operator-getting-started-lab.xml33(title) +msgid "Create a Branch" +msgstr "" + +#: ./doc/training-guides/operator-editing-code.xml320(para) +msgid "" +"This section is using the submission of this training material as the " +"example" +msgstr "" + +#: ./doc/training-guides/operator-editing-code.xml323(para) +msgid "Create a bp/training-manuals branch" +msgstr "" + +#: ./doc/training-guides/operator-editing-code.xml327(para) +msgid "" +"From the openstack-manuals repository, use the template user-story-includes-template.xml as the starting " +"point for your user story. bk001-ch003-associate-" +"general.xml has at least one other included user story that you " +"can use for additional help." +msgstr "" + +#: ./doc/training-guides/operator-editing-code.xml333(para) +msgid "" +"Include the user story xml file into the bk001-ch003" +"-associate-general.xml file. Follow the syntax of the existing " +"xi:include statements." +msgstr "" + +#: ./doc/training-guides/operator-editing-code.xml338(para) +msgid "" +"When your editing is completed. Double check Oxygen doesn't have any errors " +"you are not expecting." +msgstr "" + +#: ./doc/training-guides/operator-editing-code.xml342(para) +msgid "" +"Run maven locally to verify the build will run without errors " +"" +msgstr "" + +#: ./doc/training-guides/operator-editing-code.xml346(para) +msgid "Add your changes into git" +msgstr "" + +#: ./doc/training-guides/operator-editing-code.xml349(para) +msgid "" +"Commit the changes with good syntax. After entering the commit command, VI " +"syntax applies. Use \"i\" to insert and Esc to break out. \":wq\" to write " +"and quit." +msgstr "" + +#: ./doc/training-guides/operator-editing-code.xml358(para) +msgid "Submit your patch for review" +msgstr "" + +#: ./doc/training-guides/operator-editing-code.xml361(para) +msgid "" +"One last step. Go to the review page listed after you submitted your review " +"and add the training core team as reviewers; Sean Roberts and Colin " +"McNamara." +msgstr "" + +#: ./doc/training-guides/operator-editing-code.xml365(para) +msgid "" +"More details on branching can be found here under Gerrit " +"Workflow and the Git " +"docs" +msgstr "" + +#: ./doc/training-guides/operator-editing-code.xml373(title) +msgid "Add Content to the Training Manuals" +msgstr "" + +#: ./doc/training-guides/operator-editing-code.xml376(para) +msgid "" +"Getting Accounts and Tools: We can't do " +"this without operators and developers using and creating the content. Anyone" +" can contribute content. You will need the tools to get started. Go to the " +"Getting Tools and Accounts page." +msgstr "" + +#: ./doc/training-guides/operator-editing-code.xml382(para) +msgid "" +"Pick a Card: Once you have your tools " +"ready to go, you can assign some work to yourself. Go to the Training Trello/KanBan storyboard" +" and assign a card / user story from the Sprint Backlog to yourself. If you " +"don't have a Trello account, no problem, just create one. Email seanrob" +"@yahoo-inc.com and you will have access. Move the card from the Sprint " +"Backlog to Doing." +msgstr "" + +#: ./doc/training-guides/operator-editing-code.xml391(para) +msgid "" +"Create the Content: Each card / user " +"story from the KanBan story board will be a separate chunk of content you " +"will add to the openstack-manuals repository openstack-training sub-project." +msgstr "" + +#: ./doc/training-guides/operator-editing-code.xml396(para) +msgid "" +"Open the file st-training-guides.xml with" +" your XML editor. All the content starts with the set file st-training-guides.xml. The XML structure follows " +"the hierarchy Set -> Book -> Chapter -> Section. The st-training-guides.xml file holds the set level. " +"Notice the set file uses xi:include statements to include the books. We want" +" to open the associate book. Open the associate book and you will see the " +"chapter include statements. These are the chapters that make up the " +"Associate Training Guide book." +msgstr "" + +#: ./doc/training-guides/operator-editing-code.xml407(para) +msgid "" +"Create a branch using the card number as associate-" +"card-XXX where XXX is the card number. Review Creating a Branch again for instructions on how " +"to complete the branch merge." +msgstr "" + +#: ./doc/training-guides/operator-editing-code.xml415(para) +msgid "" +"Copy the user-story-includes-template.xml " +"to associate-card-XXX.xml." +msgstr "" + +#: ./doc/training-guides/operator-editing-code.xml420(para) +msgid "" +"Open the bk001-ch003-asssociate-" +"general.xml file and add <xi:include " +"href=\"associate-card-XXX.xml\">" +msgstr "" + +#: ./doc/training-guides/operator-editing-code.xml426(para) +msgid "" +"Side by side, open associate-card-XXX.xml" +" with your XML editor and open the ubuntu 12.04 " +"install guide with your HTML browser." +msgstr "" + +#: ./doc/training-guides/operator-editing-code.xml431(para) +msgid "" +"Find the HTML content to include. Find the XML file that matches the HTML. " +"Include the whole page using a simple href like <xi:include href=\"associate-card-XXX.xml\"> " +"or include a section using xpath like <xi:include" +" href=\"../basic-install/src/basic-install_controller-common.xml\" " +"xpointer=\"xmlns(db=http://docbook.org/ns/docbook) xpath(//*[@xml:id = " +"'controller-os'])\"> . Review the user-story-includes-template.xml file for the whole syntax." +msgstr "" + +#: ./doc/training-guides/operator-editing-code.xml442(para) +msgid "" +"Copy in other content sources like the Aptira content, your own text " +"describing what needs to be learned with the section, diagrams, and quizzes." +" If you include content from another source like Aptira cocntent make extra " +"paragraph referencing the file and/or HTTP address the content came from." +msgstr "" + +#: ./doc/training-guides/operator-editing-code.xml449(para) +msgid "" +"Verify the code is good by runnning mvn clean generate-sources and by " +"reviewing the local HTML in file:///Users/(localUser)/code/openstack-" +"manuals/doc/training-guide/target/docbkx/webhelp/local/training-" +"guide/content/" +msgstr "" + +#: ./doc/training-guides/operator-editing-code.xml455(para) +msgid "Merge the branch" +msgstr "" + +#: ./doc/training-guides/operator-editing-code.xml458(para) +msgid "Move the card from Doing to Done" +msgstr "" + +#: ./doc/training-guides/card025.xml6(title) +msgid "Role of the Controller Node" +msgstr "" + +#. When image changes, this message will be marked fuzzy or untranslated for +#. you. +#. It doesn't matter what you translate it to: it's not used at all. +#: ./doc/training-guides/module001-ch008-queues-messaging.xml11(None) +msgid "@@image: 'figures/image04.png'; md5=dd0c42b457e2b17fd94e4f62c16b9c37" +msgstr "" + +#. When image changes, this message will be marked fuzzy or untranslated for +#. you. +#. It doesn't matter what you translate it to: it's not used at all. +#: ./doc/training-guides/module001-ch008-queues-messaging.xml47(None) +msgid "@@image: 'figures/image24.png'; md5=aea2956c5e4f01e06171d8d5e1de49b5" +msgstr "" + +#. When image changes, this message will be marked fuzzy or untranslated for +#. you. +#. It doesn't matter what you translate it to: it's not used at all. +#: ./doc/training-guides/module001-ch008-queues-messaging.xml149(None) +#: ./doc/training-guides/module001-ch008-queues-messaging.xml207(None) +msgid "@@image: 'figures/image20.png'; md5=c2cab17b6ee560943403c1d998d7a9d7" +msgstr "" + +#. When image changes, this message will be marked fuzzy or untranslated for +#. you. +#. It doesn't matter what you translate it to: it's not used at all. +#: ./doc/training-guides/module001-ch008-queues-messaging.xml184(None) +msgid "@@image: 'figures/image28.png'; md5=c813069a23d72a7a3f519d896270a62a" +msgstr "" + +#: ./doc/training-guides/module001-ch008-queues-messaging.xml6(title) +#: ./doc/training-guides/bk001-ch003-associate-controller-node.xml28(title) +msgid "OpenStack Messaging and Queues" +msgstr "" + +#: ./doc/training-guides/module001-ch008-queues-messaging.xml8(title) +msgid "Messaging in OpenStack" +msgstr "" + +#: ./doc/training-guides/module001-ch008-queues-messaging.xml15(para) +msgid "" +"AMQP is the messaging technology chosen by the OpenStack cloud. The AMQP " +"broker, either RabbitMQ or Qpid, sits between any two Nova components and " +"allows them to communicate in a loosely coupled fashion. More precisely, " +"Nova components (the compute fabric of OpenStack) use Remote Procedure Calls" +" (RPC hereinafter) to communicate to one another; however such a paradigm is" +" built atop the publish/subscribe paradigm so that the following benefits " +"can be achieved:" +msgstr "" + +#: ./doc/training-guides/module001-ch008-queues-messaging.xml25(para) +msgid "" +"Decoupling between client and servant (such as the client does not need to " +"know where the servant reference is)." +msgstr "" + +#: ./doc/training-guides/module001-ch008-queues-messaging.xml30(para) +msgid "" +"Full a-synchronism between client and servant (such as the client does not " +"need the servant to run at the same time of the remote call)." +msgstr "" + +#: ./doc/training-guides/module001-ch008-queues-messaging.xml35(para) +msgid "" +"Random balancing of remote calls (such as if more servants are up and " +"running, one-way calls are transparently dispatched to the first available " +"servant)." +msgstr "" + +#: ./doc/training-guides/module001-ch008-queues-messaging.xml40(para) +msgid "" +"Nova uses direct, fanout, and topic-based exchanges. The architecture looks " +"like the one depicted in the figure below:" +msgstr "" + +#: ./doc/training-guides/module001-ch008-queues-messaging.xml44(title) +msgid "AMQP" +msgstr "" + +#: ./doc/training-guides/module001-ch008-queues-messaging.xml51(para) +msgid "" +"Nova implements RPC (both request+response, and one-way, respectively " +"nicknamed ‘rpc.call’ and ‘rpc.cast’) over AMQP by providing an adapter class" +" which take cares of marshaling and un-marshalling of messages into function" +" calls. Each Nova service, such as Compute, Scheduler, and so on, creates " +"two queues at the initialization time, one which accepts messages with " +"routing keys ‘NODE-TYPE.NODE-ID’, for example, compute.hostname, and " +"another, which accepts messages with routing keys as generic ‘NODE-TYPE’, " +"for example compute. The former is used specifically when Nova-API needs to " +"redirect commands to a specific node like ‘euca-terminate instance’. In this" +" case, only the compute node whose host’s hypervisor is running the virtual " +"machine can kill the instance. The API acts as a consumer when RPC calls are" +" request/response, otherwise is acts as publisher only." +msgstr "" + +#: ./doc/training-guides/module001-ch008-queues-messaging.xml64(guilabel) +msgid "Nova RPC Mappings" +msgstr "" + +#: ./doc/training-guides/module001-ch008-queues-messaging.xml65(para) +msgid "" +"The figure below shows the internals of a message broker node (referred to " +"as a RabbitMQ node in the diagrams) when a single instance is deployed and " +"shared in an OpenStack cloud. Every Nova component connects to the message " +"broker and, depending on its personality, such as a compute node or a " +"network node, may use the queue either as an Invoker (such as API or " +"Scheduler) or a Worker (such as Compute or Network). Invokers and Workers do" +" not actually exist in the Nova object model, but we are going to use them " +"as an abstraction for sake of clarity. An Invoker is a component that sends " +"messages in the queuing system via two operations: 1) rpc.call and ii) " +"rpc.cast; a Worker is a component that receives messages from the queuing " +"system and reply accordingly to rcp.call operations." +msgstr "" + +#: ./doc/training-guides/module001-ch008-queues-messaging.xml78(para) +msgid "Figure 2 shows the following internal elements:" +msgstr "" + +#: ./doc/training-guides/module001-ch008-queues-messaging.xml81(para) +msgid "" +"Topic Publisher:a Topic Publisher comes " +"to life when an rpc.call or an rpc.cast operation is executed; this object " +"is instantiated and used to push a message to the queuing system. Every " +"publisher connects always to the same topic-based exchange; its life-cycle " +"is limited to the message delivery." +msgstr "" + +#: ./doc/training-guides/module001-ch008-queues-messaging.xml89(para) +msgid "" +"Direct Consumer:a Direct Consumer comes " +"to life if (an only if) a rpc.call operation is executed; this object is " +"instantiated and used to receive a response message from the queuing system;" +" Every consumer connects to a unique direct-based exchange via a unique " +"exclusive queue; its life-cycle is limited to the message delivery; the " +"exchange and queue identifiers are determined by a UUID generator, and are " +"marshaled in the message sent by the Topic Publisher (only rpc.call " +"operations)." +msgstr "" + +#: ./doc/training-guides/module001-ch008-queues-messaging.xml100(para) +msgid "" +"Topic Consumer:a Topic Consumer comes to " +"life as soon as a Worker is instantiated and exists throughout its life-" +"cycle; this object is used to receive messages from the queue and it invokes" +" the appropriate action as defined by the Worker role. A Topic Consumer " +"connects to the same topic-based exchange either via a shared queue or via a" +" unique exclusive queue. Every Worker has two topic consumers, one that is " +"addressed only during rpc.cast operations (and it connects to a shared queue" +" whose exchange key is ‘topic’) and the other that is addressed only during " +"rpc.call operations (and it connects to a unique queue whose exchange key is" +" ‘topic.host’)." +msgstr "" + +#: ./doc/training-guides/module001-ch008-queues-messaging.xml114(para) +msgid "" +"Direct Publisher:a Direct Publisher comes" +" to life only during rpc.call operations and it is instantiated to return " +"the message required by the request/response operation. The object connects " +"to a direct-based exchange whose identity is dictated by the incoming " +"message." +msgstr "" + +#: ./doc/training-guides/module001-ch008-queues-messaging.xml122(para) +msgid "" +"Topic Exchange:The Exchange is a routing " +"table that exists in the context of a virtual host (the multi-tenancy " +"mechanism provided by Qpid or RabbitMQ); its type (such as topic vs. direct)" +" determines the routing policy; a message broker node will have only one " +"topic-based exchange for every topic in Nova." +msgstr "" + +#: ./doc/training-guides/module001-ch008-queues-messaging.xml130(para) +msgid "" +"Direct Exchange:this is a routing table " +"that is created during rpc.call operations; there are many instances of this" +" kind of exchange throughout the life-cycle of a message broker node, one " +"for each rpc.call invoked." +msgstr "" + +#: ./doc/training-guides/module001-ch008-queues-messaging.xml137(para) +msgid "" +"Queue Element:A Queue is a message " +"bucket. Messages are kept in the queue until a Consumer (either Topic or " +"Direct Consumer) connects to the queue and fetch it. Queues can be shared or" +" can be exclusive. Queues whose routing key is ‘topic’ are shared amongst " +"Workers of the same personality." +msgstr "" + +#: ./doc/training-guides/module001-ch008-queues-messaging.xml146(title) +#: ./doc/training-guides/module001-ch008-queues-messaging.xml181(title) +#: ./doc/training-guides/module001-ch008-queues-messaging.xml204(title) +#: ./doc/training-guides/bk001-ch004-associate-controller-node-quiz.xml278(para) +#: ./doc/training-guides/lab001-control-node.xml125(emphasis) +msgid "RabbitMQ" +msgstr "" + +#: ./doc/training-guides/module001-ch008-queues-messaging.xml153(guilabel) +msgid "RPC Calls" +msgstr "" + +#: ./doc/training-guides/module001-ch008-queues-messaging.xml154(para) +msgid "The diagram below shows the message flow during an rp.call operation:" +msgstr "" + +#: ./doc/training-guides/module001-ch008-queues-messaging.xml158(para) +msgid "" +"a Topic Publisher is instantiated to send the message request to the queuing" +" system; immediately before the publishing operation, a Direct Consumer is " +"instantiated to wait for the response message." +msgstr "" + +#: ./doc/training-guides/module001-ch008-queues-messaging.xml164(para) +msgid "" +"once the message is dispatched by the exchange, it is fetched by the Topic " +"Consumer dictated by the routing key (such as ‘topic.host’) and passed to " +"the Worker in charge of the task." +msgstr "" + +#: ./doc/training-guides/module001-ch008-queues-messaging.xml170(para) +msgid "" +"once the task is completed, a Direct Publisher is allocated to send the " +"response message to the queuing system." +msgstr "" + +#: ./doc/training-guides/module001-ch008-queues-messaging.xml175(para) +msgid "" +"once the message is dispatched by the exchange, it is fetched by the Direct " +"Consumer dictated by the routing key (such as ‘msg_id’) and passed to the " +"Invoker." +msgstr "" + +#: ./doc/training-guides/module001-ch008-queues-messaging.xml188(guilabel) +msgid "RPC Casts" +msgstr "" + +#: ./doc/training-guides/module001-ch008-queues-messaging.xml189(para) +msgid "The diagram below the message flow during an rp.cast operation:" +msgstr "" + +#: ./doc/training-guides/module001-ch008-queues-messaging.xml193(para) +msgid "" +"A Topic Publisher is instantiated to send the message request to the queuing" +" system." +msgstr "" + +#: ./doc/training-guides/module001-ch008-queues-messaging.xml197(para) +msgid "" +"Once the message is dispatched by the exchange, it is fetched by the Topic " +"Consumer dictated by the routing key (such as ‘topic’) and passed to the " +"Worker in charge of the task." +msgstr "" + +#: ./doc/training-guides/module001-ch008-queues-messaging.xml211(guilabel) +msgid "AMQP Broker Load" +msgstr "" + +#: ./doc/training-guides/module001-ch008-queues-messaging.xml212(para) +msgid "" +"At any given time the load of a message broker node running either Qpid or " +"RabbitMQ is function of the following parameters:" +msgstr "" + +#: ./doc/training-guides/module001-ch008-queues-messaging.xml217(para) +msgid "" +"Throughput of API calls: the number of API calls (more precisely rpc.call " +"ops) being served by the OpenStack cloud dictates the number of direct-based" +" exchanges, related queues and direct consumers connected to them." +msgstr "" + +#: ./doc/training-guides/module001-ch008-queues-messaging.xml223(para) +msgid "" +"Number of Workers: there is one queue shared amongst workers with the same " +"personality; however there are as many exclusive queues as the number of " +"workers; the number of workers dictates also the number of routing keys " +"within the topic-based exchange, which is shared amongst all workers." +msgstr "" + +#: ./doc/training-guides/module001-ch008-queues-messaging.xml231(para) +msgid "" +"The figure below shows the status of a RabbitMQ node after Nova components’ " +"bootstrap in a test environment. Exchanges and queues being created by Nova " +"components are:" +msgstr "" + +#: ./doc/training-guides/module001-ch008-queues-messaging.xml236(para) +msgid "Exchanges" +msgstr "" + +#: ./doc/training-guides/module001-ch008-queues-messaging.xml241(para) +msgid "nova (topic exchange)" +msgstr "" + +#: ./doc/training-guides/module001-ch008-queues-messaging.xml246(para) +msgid "Queues" +msgstr "" + +#: ./doc/training-guides/module001-ch008-queues-messaging.xml251(para) +msgid "compute.phantom (phantom is hostname)" +msgstr "" + +#: ./doc/training-guides/module001-ch008-queues-messaging.xml254(para) +msgid "compute" +msgstr "" + +#: ./doc/training-guides/module001-ch008-queues-messaging.xml257(para) +msgid "network.phantom (phantom is hostname)" +msgstr "" + +#: ./doc/training-guides/module001-ch008-queues-messaging.xml260(para) +msgid "network" +msgstr "" + +#: ./doc/training-guides/module001-ch008-queues-messaging.xml263(para) +msgid "scheduler.phantom (phantom is hostname)" +msgstr "" + +#: ./doc/training-guides/module001-ch008-queues-messaging.xml266(para) +msgid "scheduler" +msgstr "" + +#: ./doc/training-guides/module001-ch008-queues-messaging.xml269(guilabel) +msgid "RabbitMQ Gotchas" +msgstr "" + +#: ./doc/training-guides/module001-ch008-queues-messaging.xml270(para) +msgid "" +"Nova uses Kombu to connect to the RabbitMQ environment. Kombu is a Python " +"library that in turn uses AMQPLib, a library that implements the standard " +"AMQP 0.8 at the time of writing. When using Kombu, Invokers and Workers need" +" the following parameters in order to instantiate a Connection object that " +"connects to the RabbitMQ server (please note that most of the following " +"material can be also found in the Kombu documentation; it has been " +"summarized and revised here for sake of clarity):" +msgstr "" + +#: ./doc/training-guides/module001-ch008-queues-messaging.xml280(para) +msgid "" +"Hostname: The hostname to the AMQP " +"server." +msgstr "" + +#: ./doc/training-guides/module001-ch008-queues-messaging.xml284(para) +msgid "" +"Userid: A valid username used to " +"authenticate to the server." +msgstr "" + +#: ./doc/training-guides/module001-ch008-queues-messaging.xml288(para) +msgid "" +"Password: The password used to " +"authenticate to the server." +msgstr "" + +#: ./doc/training-guides/module001-ch008-queues-messaging.xml292(para) +msgid "" +"Virtual_host: The name of the virtual " +"host to work with. This virtual host must exist on the server, and the user " +"must have access to it. Default is “/”." +msgstr "" + +#: ./doc/training-guides/module001-ch008-queues-messaging.xml298(para) +msgid "" +"Port: The port of the AMQP server. " +"Default is 5672 (amqp)." +msgstr "" + +#: ./doc/training-guides/module001-ch008-queues-messaging.xml302(para) +msgid "The following parameters are default:" +msgstr "" + +#: ./doc/training-guides/module001-ch008-queues-messaging.xml305(para) +msgid "" +"Insist: insist on connecting to a server." +" In a configuration with multiple load-sharing servers, the Insist option " +"tells the server that the client is insisting on a connection to the " +"specified server. Default is False." +msgstr "" + +#: ./doc/training-guides/module001-ch008-queues-messaging.xml312(para) +msgid "" +"Connect_timeout: the timeout in seconds " +"before the client gives up connecting to the server. The default is no " +"timeout." +msgstr "" + +#: ./doc/training-guides/module001-ch008-queues-messaging.xml317(para) +msgid "" +"SSL: use SSL to connect to the server. " +"The default is False." +msgstr "" + +#: ./doc/training-guides/module001-ch008-queues-messaging.xml321(para) +msgid "More precisely Consumers need the following parameters:" +msgstr "" + +#: ./doc/training-guides/module001-ch008-queues-messaging.xml324(para) +msgid "" +"Connection: the above mentioned " +"Connection object." +msgstr "" + +#: ./doc/training-guides/module001-ch008-queues-messaging.xml328(para) +msgid "Queue:name of the queue." +msgstr "" + +#: ./doc/training-guides/module001-ch008-queues-messaging.xml332(para) +msgid "" +"Exchange:name of the exchange the queue " +"binds to." +msgstr "" + +#: ./doc/training-guides/module001-ch008-queues-messaging.xml336(para) +msgid "" +"Routing_key:the interpretation of the " +"routing key depends on the value of the exchange_type attribute." +msgstr "" + +#: ./doc/training-guides/module001-ch008-queues-messaging.xml343(para) +msgid "" +"Direct exchange:if the routing key " +"property of the message and the routing_key attribute of the queue are " +"identical, then the message is forwarded to the queue." +msgstr "" + +#: ./doc/training-guides/module001-ch008-queues-messaging.xml349(para) +msgid "" +"Fanout exchange:messages are forwarded to" +" the queues bound the exchange, even if the binding does not have a key." +msgstr "" + +#: ./doc/training-guides/module001-ch008-queues-messaging.xml354(para) +msgid "" +"Topic exchange:if the routing key " +"property of the message matches the routing key of the key according to a " +"primitive pattern matching scheme, then the message is forwarded to the " +"queue. The message routing key then consists of words separated by dots " +"(”.”, like domain names), and two special characters are available; star " +"(“”) and hash (“#”). The star matches any word, and the hash matches zero or" +" more words. For example ”.stock.#” matches the routing keys “usd.stock” and" +" “eur.stock.db” but not “stock.nasdaq”." +msgstr "" + +#: ./doc/training-guides/module001-ch008-queues-messaging.xml368(para) +msgid "" +"Durable:this flag determines the " +"durability of both exchanges and queues; durable exchanges and queues remain" +" active when a RabbitMQ server restarts. Non-durable exchanges/queues " +"(transient exchanges/queues) are purged when a server restarts. It is worth " +"noting that AMQP specifies that durable queues cannot bind to transient " +"exchanges. Default is True." +msgstr "" + +#: ./doc/training-guides/module001-ch008-queues-messaging.xml377(para) +msgid "" +"Auto_delete:if set, the exchange is " +"deleted when all queues have finished using it. Default is False." +msgstr "" + +#: ./doc/training-guides/module001-ch008-queues-messaging.xml382(para) +msgid "" +"Exclusive:exclusive queues (such as non-" +"shared) may only be consumed from by the current connection. When exclusive " +"is on, this also implies auto_delete. Default is False." +msgstr "" + +#: ./doc/training-guides/module001-ch008-queues-messaging.xml388(para) +msgid "" +"Exchange_type:AMQP defines several " +"default exchange types (routing algorithms) that covers most of the common " +"messaging use cases." +msgstr "" + +#: ./doc/training-guides/module001-ch008-queues-messaging.xml393(para) +msgid "" +"Auto_ack:acknowledgement is handled " +"automatically once messages are received. By default auto_ack is set to " +"False, and the receiver is required to manually handle acknowledgment." +msgstr "" + +#: ./doc/training-guides/module001-ch008-queues-messaging.xml399(para) +msgid "" +"No_ack:it disable acknowledgement on the " +"server-side. This is different from auto_ack in that acknowledgement is " +"turned off altogether. This functionality increases performance but at the " +"cost of reliability. Messages can get lost if a client dies before it can " +"deliver them to the application." +msgstr "" + +#: ./doc/training-guides/module001-ch008-queues-messaging.xml407(para) +msgid "" +"Auto_declare:if this is True and the " +"exchange name is set, the exchange will be automatically declared at " +"instantiation. Auto declare is on by default. Publishers specify most the " +"parameters of Consumers (such as they do not specify a queue name), but they" +" can also specify the following:" +msgstr "" + +#: ./doc/training-guides/module001-ch008-queues-messaging.xml415(para) +msgid "" +"Delivery_mode:the default delivery mode " +"used for messages. The value is an integer. The following delivery modes are" +" supported by RabbitMQ:" +msgstr "" + +#: ./doc/training-guides/module001-ch008-queues-messaging.xml422(para) +msgid "" +"1 or “transient”:the message is " +"transient. Which means it is stored in memory only, and is lost if the " +"server dies or restarts." +msgstr "" + +#: ./doc/training-guides/module001-ch008-queues-messaging.xml427(para) +msgid "" +"2 or “persistent”:the message is " +"persistent. Which means the message is stored both in-memory, and on disk, " +"and therefore preserved if the server dies or restarts." +msgstr "" + +#: ./doc/training-guides/module001-ch008-queues-messaging.xml433(para) +msgid "" +"The default value is 2 (persistent). During a send operation, Publishers can" +" override the delivery mode of messages so that, for example, transient " +"messages can be sent over a durable queue." +msgstr "" + +#: ./doc/training-guides/bk001-associate-training-guide.xml5(title) +msgid "Associate Training Guide" +msgstr "" + +#: ./doc/training-guides/training-cluster-by-script.xml5(title) +#: ./doc/training-guides/bk000-preface.xml137(title) +msgid "Building the Training Cluster, Scripted" +msgstr "" + +#: ./doc/training-guides/training-cluster-by-script.xml6(para) +msgid "Setting Up Test Environment" +msgstr "" + +#: ./doc/training-guides/training-cluster-by-script.xml7(para) +msgid "" +"For using Virtual Box as test environment, you need to attach three network " +"adapters" +msgstr "" + +#: ./doc/training-guides/training-cluster-by-script.xml11(para) +msgid "" +"Host-Only/ Bridged -- 10.10.10.51 (Guest) -- 10.10.10.xx (Host IP for Host-" +"Only)" +msgstr "" + +#: ./doc/training-guides/training-cluster-by-script.xml15(para) +msgid "" +"Host-Only/ Bridged -- 192.168.100.51 (Guest) -- 192.168.100.xx (Host IP for " +"Host-Only)" +msgstr "" + +#: ./doc/training-guides/training-cluster-by-script.xml19(para) +msgid "" +"Bridged/NAT -- DHCP -- These Scripts should be run without internet " +"connection after Pre-Install.sh. If your networking configuration is not " +"exact a few command will not work. you need to change the Templates/* to the" +" required IP Addresses for custom networks." +msgstr "" + +#: ./doc/training-guides/training-cluster-by-script.xml25(link) +msgid "" +"Extract the scripts locally by downloading and running the scripts tar file." +msgstr "" + +#: ./doc/training-guides/training-cluster-by-script.xml27(emphasis) +msgid "Testing" +msgstr "" + +#: ./doc/training-guides/training-cluster-by-script.xml28(para) +msgid "" +"As of now only */Scripts/ folders content are being tested. Please run the " +"file ~/Scripts/test_scripts.sh for testing all the scripts at once with one " +"click." +msgstr "" + +#: ./doc/training-guides/training-cluster-by-script.xml33(para) +msgid "" +"Test Scripts Individually. Run the " +"Scripts inside the Scripts Folder to check whether the shell scripts are " +"properly functioning. You Don't Need to install Vitual Box although it is " +"advised to do so, as there is a good chance that you may end up breaking " +"your host machine." +msgstr "" + +#: ./doc/training-guides/training-cluster-by-script.xml39(para) +msgid "" +"How to Test them. Testing these scripts " +"is as simple as running them. Although some of the scripts need the required" +" Input parameters. If you do not want to run them manually then you may run " +"the Scripts/test_scripts.sh file. No Need for Virutalbox Guest Addons for " +"testing the scripts as units." +msgstr "" + +#: ./doc/training-guides/training-cluster-by-script.xml46(para) +msgid "" +"Test Entire System you need to install " +"Virtual Box, install Ubuntu Server 12.04 or 13.04. After installation you " +"also need to install Virtual Box Guest Addons. To install Virtual Box guest " +"addons you need do the following : Either use the Virtual Box Guest Addons " +"Installation via. ISO, #apt-get install linux-headers-generic " +"#mount /dev/cdrom0/ /tmp/cdrom #cd /tmp/cdrom/ #./virtualboxOr You" +" May use Ubuntu Repositories for the same #apt-get install linux-" +"headers-generic #apt-get --no-install-recommends install virtualbox-guest-" +"additions" +msgstr "" + +#. When image changes, this message will be marked fuzzy or untranslated for +#. you. +#. It doesn't matter what you translate it to: it's not used at all. +#: ./doc/training-guides/card074-horizon-snapshots.xml12(None) +#: ./doc/training-guides/card071-create-cinder-horizon.xml11(None) +#: ./doc/training-guides/card071-create-cinder-horizon.xml15(None) +#: ./doc/training-guides/card071-create-cinder-horizon.xml19(None) +#: ./doc/training-guides/bk001-ch003-associate-controller-node.xml17(None) +#: ./doc/training-guides/bk001-ch003-associate-controller-node.xml24(None) +#: ./doc/training-guides/bk001-ch003-associate-controller-node.xml31(None) +#: ./doc/training-guides/bk001-ch003-associate-controller-node.xml40(None) +#: ./doc/training-guides/bk001-ch003-associate-controller-node.xml47(None) +#: ./doc/training-guides/bk001-ch003-associate-controller-node.xml54(None) +#: ./doc/training-guides/bk001-ch003-associate-controller-node.xml61(None) +#: ./doc/training-guides/bk001-ch003-associate-controller-node.xml68(None) +#: ./doc/training-guides/bk001-ch003-associate-controller-node.xml75(None) +#: ./doc/training-guides/bk001-ch003-associate-controller-node.xml82(None) +#: ./doc/training-guides/bk002-ch010-operator-network-node.xml17(None) +#: ./doc/training-guides/bk002-ch010-operator-network-node.xml24(None) +#: ./doc/training-guides/bk001-ch009-associate-object-storage-node.xml17(None) +#: ./doc/training-guides/bk001-ch009-associate-object-storage-node.xml24(None) +#: ./doc/training-guides/bk001-ch009-associate-object-storage-node.xml33(None) +#: ./doc/training-guides/card072-cinder-attach-volume.xml11(None) +#: ./doc/training-guides/bk002-ch004-operator-controller-node.xml17(None) +#: ./doc/training-guides/bk002-ch004-operator-controller-node.xml24(None) +#: ./doc/training-guides/bk002-ch004-operator-controller-node.xml31(None) +#: ./doc/training-guides/bk002-ch002-operator-getting-started-lab.xml15(None) +#: ./doc/training-guides/bk002-ch002-operator-getting-started-lab.xml22(None) +#: ./doc/training-guides/bk002-ch002-operator-getting-started-lab.xml29(None) +#: ./doc/training-guides/bk002-ch002-operator-getting-started-lab.xml36(None) +#: ./doc/training-guides/bk002-ch002-operator-getting-started-lab.xml43(None) +#: ./doc/training-guides/bk002-ch007-operator-compute-node.xml17(None) +#: ./doc/training-guides/bk002-ch007-operator-compute-node.xml24(None) +#: ./doc/training-guides/bk002-ch007-operator-compute-node.xml31(None) +#: ./doc/training-guides/bk002-ch013-operator-object-storage-node.xml17(None) +#: ./doc/training-guides/bk002-ch013-operator-object-storage-node.xml24(None) +#: ./doc/training-guides/bk002-ch013-operator-object-storage-node.xml35(None) +#: ./doc/training-guides/bk002-ch013-operator-object-storage-node.xml42(None) +#: ./doc/training-guides/bk002-ch013-operator-object-storage-node.xml49(None) +#: ./doc/training-guides/bk002-ch013-operator-object-storage-node.xml55(None) +#: ./doc/training-guides/bk002-ch013-operator-object-storage-node.xml62(None) +#: ./doc/training-guides/bk002-ch013-operator-object-storage-node.xml69(None) +#: ./doc/training-guides/bk002-ch013-operator-object-storage-node.xml76(None) +#: ./doc/training-guides/bk002-ch001-operator-getting-started.xml25(None) +#: ./doc/training-guides/bk002-ch001-operator-getting-started.xml32(None) +#: ./doc/training-guides/bk002-ch001-operator-getting-started.xml39(None) +#: ./doc/training-guides/bk002-ch001-operator-getting-started.xml46(None) +#: ./doc/training-guides/bk002-ch001-operator-getting-started.xml53(None) +#: ./doc/training-guides/card008.xml11(None) +#: ./doc/training-guides/bk000-preface.xml133(None) +#: ./doc/training-guides/bk000-preface.xml140(None) +#: ./doc/training-guides/bk000-preface.xml147(None) +#: ./doc/training-guides/bk001-ch001-associate-getting-started.xml27(None) +#: ./doc/training-guides/bk001-ch001-associate-getting-started.xml34(None) +#: ./doc/training-guides/bk001-ch001-associate-getting-started.xml41(None) +#: ./doc/training-guides/bk001-ch001-associate-getting-started.xml48(None) +#: ./doc/training-guides/bk001-ch001-associate-getting-started.xml55(None) +#: ./doc/training-guides/card073-control-state-instance.xml12(None) +#: ./doc/training-guides/bk001-ch005-associate-compute-node.xml17(None) +#: ./doc/training-guides/bk001-ch005-associate-compute-node.xml24(None) +#: ./doc/training-guides/bk001-ch005-associate-compute-node.xml31(None) +#: ./doc/training-guides/bk001-ch005-associate-compute-node.xml40(None) +#: ./doc/training-guides/bk001-ch005-associate-compute-node.xml47(None) +#: ./doc/training-guides/bk001-ch005-associate-compute-node.xml54(None) +#: ./doc/training-guides/bk001-ch005-associate-compute-node.xml61(None) +#: ./doc/training-guides/bk001-ch005-associate-compute-node.xml68(None) +#: ./doc/training-guides/bk001-ch005-associate-compute-node.xml75(None) +#: ./doc/training-guides/card128-swift.xml11(None) +#: ./doc/training-guides/bk003-developer-training-guide.xml13(None) +#: ./doc/training-guides/bk003-developer-training-guide.xml20(None) +#: ./doc/training-guides/bk003-developer-training-guide.xml27(None) +#: ./doc/training-guides/bk003-developer-training-guide.xml34(None) +#: ./doc/training-guides/bk003-developer-training-guide.xml41(None) +#: ./doc/training-guides/bk003-developer-training-guide.xml48(None) +#: ./doc/training-guides/bk003-developer-training-guide.xml55(None) +#: ./doc/training-guides/bk003-developer-training-guide.xml62(None) +#: ./doc/training-guides/bk003-developer-training-guide.xml69(None) +#: ./doc/training-guides/bk001-ch007-associate-network-node.xml17(None) +#: ./doc/training-guides/bk001-ch007-associate-network-node.xml24(None) +#: ./doc/training-guides/bk001-ch007-associate-network-node.xml33(None) +#: ./doc/training-guides/bk001-ch007-associate-network-node.xml40(None) +#: ./doc/training-guides/card070-create-floating-ips.xml11(None) +#: ./doc/training-guides/card070-create-floating-ips.xml16(None) +#: ./doc/training-guides/card070-create-floating-ips.xml21(None) +msgid "" +"@@image: 'figures/openstack-training-remote-content-not-available.png'; " +"md5=f2583b37e01220460a55b8c255c987c3" +msgstr "" + +#: ./doc/training-guides/card074-horizon-snapshots.xml7(title) +msgid "Creating Snapshots" +msgstr "" + +#: ./doc/training-guides/card074-horizon-snapshots.xml8(emphasis) +msgid "Creating image snapshots using Horizon" +msgstr "" + +#: ./doc/training-guides/card074-horizon-snapshots.xml12(para) +#: ./doc/training-guides/card071-create-cinder-horizon.xml11(para) +#: ./doc/training-guides/card071-create-cinder-horizon.xml15(para) +#: ./doc/training-guides/card071-create-cinder-horizon.xml19(para) +#: ./doc/training-guides/bk001-ch003-associate-controller-node.xml17(para) +#: ./doc/training-guides/bk001-ch003-associate-controller-node.xml24(para) +#: ./doc/training-guides/bk001-ch003-associate-controller-node.xml31(para) +#: ./doc/training-guides/bk001-ch003-associate-controller-node.xml40(para) +#: ./doc/training-guides/bk001-ch003-associate-controller-node.xml47(para) +#: ./doc/training-guides/bk001-ch003-associate-controller-node.xml54(para) +#: ./doc/training-guides/bk001-ch003-associate-controller-node.xml61(para) +#: ./doc/training-guides/bk001-ch003-associate-controller-node.xml68(para) +#: ./doc/training-guides/bk001-ch003-associate-controller-node.xml75(para) +#: ./doc/training-guides/bk001-ch003-associate-controller-node.xml82(para) +#: ./doc/training-guides/bk002-ch010-operator-network-node.xml17(para) +#: ./doc/training-guides/bk002-ch010-operator-network-node.xml24(para) +#: ./doc/training-guides/bk001-ch009-associate-object-storage-node.xml17(para) +#: ./doc/training-guides/bk001-ch009-associate-object-storage-node.xml24(para) +#: ./doc/training-guides/bk001-ch009-associate-object-storage-node.xml33(para) +#: ./doc/training-guides/card072-cinder-attach-volume.xml11(para) +#: ./doc/training-guides/bk002-ch004-operator-controller-node.xml17(para) +#: ./doc/training-guides/bk002-ch004-operator-controller-node.xml24(para) +#: ./doc/training-guides/bk002-ch004-operator-controller-node.xml31(para) +#: ./doc/training-guides/bk002-ch002-operator-getting-started-lab.xml15(para) +#: ./doc/training-guides/bk002-ch002-operator-getting-started-lab.xml22(para) +#: ./doc/training-guides/bk002-ch002-operator-getting-started-lab.xml29(para) +#: ./doc/training-guides/bk002-ch002-operator-getting-started-lab.xml36(para) +#: ./doc/training-guides/bk002-ch002-operator-getting-started-lab.xml43(para) +#: ./doc/training-guides/bk002-ch007-operator-compute-node.xml17(para) +#: ./doc/training-guides/bk002-ch007-operator-compute-node.xml24(para) +#: ./doc/training-guides/bk002-ch007-operator-compute-node.xml31(para) +#: ./doc/training-guides/bk002-ch013-operator-object-storage-node.xml17(para) +#: ./doc/training-guides/bk002-ch013-operator-object-storage-node.xml24(para) +#: ./doc/training-guides/bk002-ch013-operator-object-storage-node.xml35(para) +#: ./doc/training-guides/bk002-ch013-operator-object-storage-node.xml42(para) +#: ./doc/training-guides/bk002-ch013-operator-object-storage-node.xml49(para) +#: ./doc/training-guides/bk002-ch013-operator-object-storage-node.xml55(para) +#: ./doc/training-guides/bk002-ch013-operator-object-storage-node.xml62(para) +#: ./doc/training-guides/bk002-ch013-operator-object-storage-node.xml69(para) +#: ./doc/training-guides/bk002-ch013-operator-object-storage-node.xml76(para) +#: ./doc/training-guides/bk002-ch001-operator-getting-started.xml25(para) +#: ./doc/training-guides/bk002-ch001-operator-getting-started.xml32(para) +#: ./doc/training-guides/bk002-ch001-operator-getting-started.xml39(para) +#: ./doc/training-guides/bk002-ch001-operator-getting-started.xml46(para) +#: ./doc/training-guides/bk002-ch001-operator-getting-started.xml53(para) +#: ./doc/training-guides/card008.xml11(para) +#: ./doc/training-guides/bk000-preface.xml133(para) +#: ./doc/training-guides/bk000-preface.xml140(para) +#: ./doc/training-guides/bk000-preface.xml147(para) +#: ./doc/training-guides/bk001-ch001-associate-getting-started.xml27(para) +#: ./doc/training-guides/bk001-ch001-associate-getting-started.xml34(para) +#: ./doc/training-guides/bk001-ch001-associate-getting-started.xml41(para) +#: ./doc/training-guides/bk001-ch001-associate-getting-started.xml48(para) +#: ./doc/training-guides/bk001-ch001-associate-getting-started.xml55(para) +#: ./doc/training-guides/card073-control-state-instance.xml12(para) +#: ./doc/training-guides/bk001-ch005-associate-compute-node.xml17(para) +#: ./doc/training-guides/bk001-ch005-associate-compute-node.xml24(para) +#: ./doc/training-guides/bk001-ch005-associate-compute-node.xml31(para) +#: ./doc/training-guides/bk001-ch005-associate-compute-node.xml40(para) +#: ./doc/training-guides/bk001-ch005-associate-compute-node.xml47(para) +#: ./doc/training-guides/bk001-ch005-associate-compute-node.xml54(para) +#: ./doc/training-guides/bk001-ch005-associate-compute-node.xml61(para) +#: ./doc/training-guides/bk001-ch005-associate-compute-node.xml68(para) +#: ./doc/training-guides/bk001-ch005-associate-compute-node.xml75(para) +#: ./doc/training-guides/card128-swift.xml11(para) +#: ./doc/training-guides/bk003-developer-training-guide.xml13(para) +#: ./doc/training-guides/bk003-developer-training-guide.xml20(para) +#: ./doc/training-guides/bk003-developer-training-guide.xml27(para) +#: ./doc/training-guides/bk003-developer-training-guide.xml34(para) +#: ./doc/training-guides/bk003-developer-training-guide.xml41(para) +#: ./doc/training-guides/bk003-developer-training-guide.xml48(para) +#: ./doc/training-guides/bk003-developer-training-guide.xml55(para) +#: ./doc/training-guides/bk003-developer-training-guide.xml62(para) +#: ./doc/training-guides/bk003-developer-training-guide.xml69(para) +#: ./doc/training-guides/bk001-ch007-associate-network-node.xml17(para) +#: ./doc/training-guides/bk001-ch007-associate-network-node.xml24(para) +#: ./doc/training-guides/bk001-ch007-associate-network-node.xml33(para) +#: ./doc/training-guides/bk001-ch007-associate-network-node.xml40(para) +#: ./doc/training-guides/card070-create-floating-ips.xml11(para) +#: ./doc/training-guides/card070-create-floating-ips.xml16(para) +#: ./doc/training-guides/card070-create-floating-ips.xml21(para) +msgid "Remote content not available" +msgstr "" + +#: ./doc/training-guides/card074-horizon-snapshots.xml12(link) +#: ./doc/training-guides/card071-create-cinder-horizon.xml11(link) +#: ./doc/training-guides/card071-create-cinder-horizon.xml15(link) +#: ./doc/training-guides/card071-create-cinder-horizon.xml19(link) +#: ./doc/training-guides/bk001-ch003-associate-controller-node.xml17(link) +#: ./doc/training-guides/bk001-ch003-associate-controller-node.xml24(link) +#: ./doc/training-guides/bk001-ch003-associate-controller-node.xml31(link) +#: ./doc/training-guides/bk001-ch003-associate-controller-node.xml40(link) +#: ./doc/training-guides/bk001-ch003-associate-controller-node.xml47(link) +#: ./doc/training-guides/bk001-ch003-associate-controller-node.xml54(link) +#: ./doc/training-guides/bk001-ch003-associate-controller-node.xml61(link) +#: ./doc/training-guides/bk001-ch003-associate-controller-node.xml68(link) +#: ./doc/training-guides/bk001-ch003-associate-controller-node.xml75(link) +#: ./doc/training-guides/bk001-ch003-associate-controller-node.xml82(link) +#: ./doc/training-guides/bk002-ch010-operator-network-node.xml17(link) +#: ./doc/training-guides/bk002-ch010-operator-network-node.xml24(link) +#: ./doc/training-guides/bk001-ch009-associate-object-storage-node.xml17(link) +#: ./doc/training-guides/bk001-ch009-associate-object-storage-node.xml24(link) +#: ./doc/training-guides/bk001-ch009-associate-object-storage-node.xml33(link) +#: ./doc/training-guides/card072-cinder-attach-volume.xml11(link) +#: ./doc/training-guides/bk002-ch004-operator-controller-node.xml17(link) +#: ./doc/training-guides/bk002-ch004-operator-controller-node.xml24(link) +#: ./doc/training-guides/bk002-ch004-operator-controller-node.xml31(link) +#: ./doc/training-guides/bk002-ch002-operator-getting-started-lab.xml15(link) +#: ./doc/training-guides/bk002-ch002-operator-getting-started-lab.xml22(link) +#: ./doc/training-guides/bk002-ch002-operator-getting-started-lab.xml29(link) +#: ./doc/training-guides/bk002-ch002-operator-getting-started-lab.xml36(link) +#: ./doc/training-guides/bk002-ch002-operator-getting-started-lab.xml43(link) +#: ./doc/training-guides/bk002-ch007-operator-compute-node.xml17(link) +#: ./doc/training-guides/bk002-ch007-operator-compute-node.xml24(link) +#: ./doc/training-guides/bk002-ch007-operator-compute-node.xml31(link) +#: ./doc/training-guides/bk002-ch013-operator-object-storage-node.xml17(link) +#: ./doc/training-guides/bk002-ch013-operator-object-storage-node.xml24(link) +#: ./doc/training-guides/bk002-ch013-operator-object-storage-node.xml35(link) +#: ./doc/training-guides/bk002-ch013-operator-object-storage-node.xml42(link) +#: ./doc/training-guides/bk002-ch013-operator-object-storage-node.xml49(link) +#: ./doc/training-guides/bk002-ch013-operator-object-storage-node.xml55(link) +#: ./doc/training-guides/bk002-ch013-operator-object-storage-node.xml62(link) +#: ./doc/training-guides/bk002-ch013-operator-object-storage-node.xml69(link) +#: ./doc/training-guides/bk002-ch013-operator-object-storage-node.xml76(link) +#: ./doc/training-guides/bk002-ch001-operator-getting-started.xml25(link) +#: ./doc/training-guides/bk002-ch001-operator-getting-started.xml32(link) +#: ./doc/training-guides/bk002-ch001-operator-getting-started.xml39(link) +#: ./doc/training-guides/bk002-ch001-operator-getting-started.xml46(link) +#: ./doc/training-guides/bk002-ch001-operator-getting-started.xml53(link) +#: ./doc/training-guides/card008.xml11(link) +#: ./doc/training-guides/bk000-preface.xml133(link) +#: ./doc/training-guides/bk000-preface.xml140(link) +#: ./doc/training-guides/bk000-preface.xml147(link) +#: ./doc/training-guides/bk001-ch001-associate-getting-started.xml27(link) +#: ./doc/training-guides/bk001-ch001-associate-getting-started.xml34(link) +#: ./doc/training-guides/bk001-ch001-associate-getting-started.xml41(link) +#: ./doc/training-guides/bk001-ch001-associate-getting-started.xml48(link) +#: ./doc/training-guides/bk001-ch001-associate-getting-started.xml55(link) +#: ./doc/training-guides/card073-control-state-instance.xml12(link) +#: ./doc/training-guides/bk001-ch005-associate-compute-node.xml17(link) +#: ./doc/training-guides/bk001-ch005-associate-compute-node.xml24(link) +#: ./doc/training-guides/bk001-ch005-associate-compute-node.xml31(link) +#: ./doc/training-guides/bk001-ch005-associate-compute-node.xml40(link) +#: ./doc/training-guides/bk001-ch005-associate-compute-node.xml47(link) +#: ./doc/training-guides/bk001-ch005-associate-compute-node.xml54(link) +#: ./doc/training-guides/bk001-ch005-associate-compute-node.xml61(link) +#: ./doc/training-guides/bk001-ch005-associate-compute-node.xml68(link) +#: ./doc/training-guides/bk001-ch005-associate-compute-node.xml75(link) +#: ./doc/training-guides/card128-swift.xml11(link) +#: ./doc/training-guides/bk003-developer-training-guide.xml13(link) +#: ./doc/training-guides/bk003-developer-training-guide.xml20(link) +#: ./doc/training-guides/bk003-developer-training-guide.xml27(link) +#: ./doc/training-guides/bk003-developer-training-guide.xml34(link) +#: ./doc/training-guides/bk003-developer-training-guide.xml41(link) +#: ./doc/training-guides/bk003-developer-training-guide.xml48(link) +#: ./doc/training-guides/bk003-developer-training-guide.xml55(link) +#: ./doc/training-guides/bk003-developer-training-guide.xml62(link) +#: ./doc/training-guides/bk003-developer-training-guide.xml69(link) +#: ./doc/training-guides/bk001-ch007-associate-network-node.xml17(link) +#: ./doc/training-guides/bk001-ch007-associate-network-node.xml24(link) +#: ./doc/training-guides/bk001-ch007-associate-network-node.xml33(link) +#: ./doc/training-guides/bk001-ch007-associate-network-node.xml40(link) +#: ./doc/training-guides/card070-create-floating-ips.xml11(link) +#: ./doc/training-guides/card070-create-floating-ips.xml16(link) +#: ./doc/training-guides/card070-create-floating-ips.xml21(link) +msgid "" +"https://docs.google.com/drawings/d/1J2LZSxmc06xKyxMgPjv5fC0blV7qK6956-AeTmFOZD4/edit?usp=sharing" +msgstr "" + +#: ./doc/training-guides/card071-create-cinder-horizon.xml7(title) +msgid "Creating and Deleting Volumes" +msgstr "" + +#: ./doc/training-guides/bk001-ch003-associate-controller-node.xml8(title) +#: ./doc/training-guides/bk002-ch004-operator-controller-node.xml8(title) +#: ./doc/training-guides/lab001-control-node.xml24(guilabel) +msgid "Controller Node" +msgstr "" + +#: ./doc/training-guides/bk001-ch003-associate-controller-node.xml10(title) +msgid "Day 1, 11:15 to 12:30, 13:30 to 14:45" +msgstr "" + +#: ./doc/training-guides/bk001-ch003-associate-controller-node.xml14(title) +#: ./doc/training-guides/module001-ch006-overview-horizon-cli.xml7(title) +msgid "Overview Horizon and OpenStack CLI" +msgstr "" + +#: ./doc/training-guides/bk001-ch003-associate-controller-node.xml21(title) +#: ./doc/training-guides/module001-ch007-keystone-arch.xml6(title) +msgid "Keystone Architecture" +msgstr "" + +#: ./doc/training-guides/bk001-ch003-associate-controller-node.xml35(title) +#: ./doc/training-guides/bk001-ch009-associate-object-storage-node.xml28(title) +#: ./doc/training-guides/bk001-ch005-associate-compute-node.xml35(title) +#: ./doc/training-guides/bk001-ch007-associate-network-node.xml28(title) +msgid "Administration Tasks" +msgstr "" + +#: ./doc/training-guides/bk001-ch003-associate-controller-node.xml37(title) +msgid "Identity CI Commands" +msgstr "" + +#: ./doc/training-guides/bk001-ch003-associate-controller-node.xml44(title) +msgid "Identity User Management" +msgstr "" + +#: ./doc/training-guides/bk001-ch003-associate-controller-node.xml51(title) +msgid "Image CLI Commands" +msgstr "" + +#: ./doc/training-guides/bk001-ch003-associate-controller-node.xml58(title) +msgid "Image List Images" +msgstr "" + +#: ./doc/training-guides/bk001-ch003-associate-controller-node.xml65(title) +msgid "Image Adding Images" +msgstr "" + +#: ./doc/training-guides/bk001-ch003-associate-controller-node.xml72(title) +msgid "Image Manage Images" +msgstr "" + +#: ./doc/training-guides/bk001-ch003-associate-controller-node.xml79(title) +msgid "Message Queue Configuration" +msgstr "" + +#. When image changes, this message will be marked fuzzy or untranslated for +#. you. +#. It doesn't matter what you translate it to: it's not used at all. +#: ./doc/training-guides/lab002-network-node.xml14(None) +#: ./doc/training-guides/lab003-compute-node.xml17(None) +#: ./doc/training-guides/lab001-control-node.xml13(None) +#: ./doc/training-guides/lab000-virtualbox-basics.xml138(None) +msgid "" +"@@image: 'figures/lab000-virtual-box/image03.png'; " +"md5=d25af14759f84d6448d9bedfc67f18b5" +msgstr "" + +#: ./doc/training-guides/lab002-network-node.xml7(emphasis) +#: ./doc/training-guides/lab003-compute-node.xml10(emphasis) +#: ./doc/training-guides/lab001-control-node.xml8(emphasis) +#: ./doc/training-guides/lab000-virtualbox-basics.xml131(emphasis) +msgid "Network Diagram :" +msgstr "" + +#: ./doc/training-guides/lab002-network-node.xml18(para) +#: ./doc/training-guides/lab003-compute-node.xml21(para) +#: ./doc/training-guides/lab001-control-node.xml17(para) +msgid "" +"Vboxnet0, Vboxnet1, Vboxnet2 - are virtual networks setup up by virtual" +" box with your host machine. This is the way your host can communicate with " +"the virtual machines. These networks are in turn used by virtual box VM’s " +"for OpenStack networks, so that OpenStack’s services can communicate with " +"each other." +msgstr "" + +#: ./doc/training-guides/lab002-network-node.xml24(para) +#: ./doc/training-guides/lab003-compute-node.xml29(para) +#: ./doc/training-guides/lab001-control-node.xml25(para) +msgid "Start your Controller Node the one you setup in previous section." +msgstr "" + +#: ./doc/training-guides/lab002-network-node.xml25(emphasis) +#: ./doc/training-guides/lab003-compute-node.xml31(emphasis) +msgid "Preparing Ubuntu 12.04" +msgstr "" + +#: ./doc/training-guides/lab002-network-node.xml28(para) +#: ./doc/training-guides/lab003-compute-node.xml34(para) +#: ./doc/training-guides/lab001-control-node.xml30(para) +msgid "After you install Ubuntu Server, go in sudo mode" +msgstr "" + +#: ./doc/training-guides/lab002-network-node.xml34(para) +#: ./doc/training-guides/lab003-compute-node.xml40(para) +#: ./doc/training-guides/lab001-control-node.xml36(para) +msgid "Add Havana repositories:" +msgstr "" + +#: ./doc/training-guides/lab002-network-node.xml41(para) +#: ./doc/training-guides/lab002-network-node.xml223(para) +#: ./doc/training-guides/lab003-compute-node.xml47(para) +#: ./doc/training-guides/lab001-control-node.xml41(para) +msgid "Update your system:" +msgstr "" + +#: ./doc/training-guides/lab002-network-node.xml49(para) +#: ./doc/training-guides/lab003-compute-node.xml55(para) +msgid "Install NTP and other services:" +msgstr "" + +#: ./doc/training-guides/lab002-network-node.xml55(para) +#: ./doc/training-guides/lab003-compute-node.xml61(para) +msgid "Configure NTP Server to Controller Node:" +msgstr "" + +#: ./doc/training-guides/lab002-network-node.xml64(para) +msgid "" +"Enable IP Forwarding by adding the following to " +"/etc/sysctl.conf:" +msgstr "" + +#: ./doc/training-guides/lab002-network-node.xml72(para) +#: ./doc/training-guides/lab003-compute-node.xml78(para) +msgid "Run the following commands:" +msgstr "" + +#: ./doc/training-guides/lab002-network-node.xml81(emphasis) +msgid "OpenVSwitch" +msgstr "" + +#: ./doc/training-guides/lab002-network-node.xml84(para) +msgid "Install OpenVSwitch Packages:" +msgstr "" + +#: ./doc/training-guides/lab002-network-node.xml90(para) +msgid "Create the bridges:" +msgstr "" + +#: ./doc/training-guides/lab002-network-node.xml97(emphasis) +#: ./doc/training-guides/lab003-compute-node.xml146(para) +#: ./doc/training-guides/lab001-control-node.xml366(emphasis) +msgid "Neutron" +msgstr "" + +#: ./doc/training-guides/lab002-network-node.xml100(para) +msgid "Neutron:" +msgstr "" + +#: ./doc/training-guides/lab002-network-node.xml106(para) +msgid "Edit /etc/neutron/api-paste.ini:" +msgstr "" + +#: ./doc/training-guides/lab002-network-node.xml119(para) +msgid "" +"Edit " +"/etc/neutron/plugins/openvswitch/ovs_neutron_plugin.ini:" +msgstr "" + +#: ./doc/training-guides/lab002-network-node.xml143(para) +msgid "Edit /etc/neutron/metadata_agent.ini:" +msgstr "" + +#: ./doc/training-guides/lab002-network-node.xml159(para) +msgid "Edit /etc/neutron/dhcp_agent.ini:" +msgstr "" + +#: ./doc/training-guides/lab002-network-node.xml165(para) +msgid "Edit /etc/neutron/l3_agent.ini:" +msgstr "" + +#: ./doc/training-guides/lab002-network-node.xml173(para) +msgid "Edit /etc/neutron/neutron.conf:" +msgstr "" + +#: ./doc/training-guides/lab002-network-node.xml190(para) +msgid "Edit /etc/sudoers.d/neutron_sudoers::" +msgstr "" + +#: ./doc/training-guides/lab002-network-node.xml197(para) +msgid "Restart Services:" +msgstr "" + +#: ./doc/training-guides/lab002-network-node.xml205(para) +msgid "" +"Edit Network Interfaces file /etc/network/interfaces:" +msgstr "" + +#. When image changes, this message will be marked fuzzy or untranslated for +#. you. +#. It doesn't matter what you translate it to: it's not used at all. +#: ./doc/training-guides/module001-ch003-core-projects.xml157(None) +msgid "@@image: 'figures/image05.png'; md5=6471ce66920c1bc1b8bd3854cf836b06" +msgstr "" + +#. When image changes, this message will be marked fuzzy or untranslated for +#. you. +#. It doesn't matter what you translate it to: it's not used at all. +#: ./doc/training-guides/module001-ch003-core-projects.xml170(None) +msgid "@@image: 'figures/image16.png'; md5=65b6013bd11cf821161a1ebe91d9968b" +msgstr "" + +#. When image changes, this message will be marked fuzzy or untranslated for +#. you. +#. It doesn't matter what you translate it to: it's not used at all. +#: ./doc/training-guides/module001-ch003-core-projects.xml201(None) +msgid "@@image: 'figures/image06.png'; md5=ad0f7b815daaf1979c604ac862e99a87" +msgstr "" + +#. When image changes, this message will be marked fuzzy or untranslated for +#. you. +#. It doesn't matter what you translate it to: it's not used at all. +#: ./doc/training-guides/module001-ch003-core-projects.xml242(None) +msgid "@@image: 'figures/image03.png'; md5=25ce40bfee4d12f6bf6d781e70b4402d" +msgstr "" + +#. When image changes, this message will be marked fuzzy or untranslated for +#. you. +#. It doesn't matter what you translate it to: it's not used at all. +#: ./doc/training-guides/module001-ch003-core-projects.xml296(None) +msgid "@@image: 'figures/image17.png'; md5=b4720b3ca2aa5b05cebb27c251a81583" +msgstr "" + +#. When image changes, this message will be marked fuzzy or untranslated for +#. you. +#. It doesn't matter what you translate it to: it's not used at all. +#: ./doc/training-guides/module001-ch003-core-projects.xml426(None) +msgid "@@image: 'figures/image26.png'; md5=4dd64736f53fb4d9398067a69e13f32b" +msgstr "" + +#: ./doc/training-guides/module001-ch003-core-projects.xml3(title) +msgid "OpenStack Projects, History, and Releases Overview" +msgstr "" + +#: ./doc/training-guides/module001-ch003-core-projects.xml4(guilabel) +msgid "Project history and releases overview." +msgstr "" + +#: ./doc/training-guides/module001-ch003-core-projects.xml5(para) +msgid "" +"OpenStack is a cloud computing project to provide an infrastructure as a " +"service (IaaS). It is free open source software released under the terms of " +"the Apache License. The project is managed by the OpenStack Foundation, a " +"non-profit corporate entity established in September 2012 to promote " +"OpenStack software and its community." +msgstr "" + +#: ./doc/training-guides/module001-ch003-core-projects.xml11(para) +msgid "" +"More than 200 companies joined the project among which are AMD, Brocade " +"Communications Systems, Canonical, Cisco, Dell, EMC, Ericsson, Groupe Bull, " +"HP, IBM, Inktank, Intel, NEC, Rackspace Hosting, Red Hat, SUSE Linux, " +"VMware, and Yahoo!" +msgstr "" + +#: ./doc/training-guides/module001-ch003-core-projects.xml15(para) +msgid "" +"The technology consists of a series of interrelated projects that control " +"pools of processing, storage, and networking resources throughout a data " +"center, all managed through a dashboard that gives administrators control " +"while empowering its users to provision resources through a web interface." +msgstr "" + +#: ./doc/training-guides/module001-ch003-core-projects.xml20(para) +msgid "" +"The OpenStack community collaborates around a six-month, time-based release " +"cycle with frequent development milestones. During the planning phase of " +"each release, the community gathers for the OpenStack Design Summit to " +"facilitate developer working sessions and assemble plans." +msgstr "" + +#: ./doc/training-guides/module001-ch003-core-projects.xml25(para) +msgid "" +"In July 2010 Rackspace Hosting and NASA jointly launched an open-source " +"cloud-software initiative known as OpenStack. The OpenStack project intended" +" to help organizations which offer cloud-computing services running on " +"standard hardware. The first official release, code-named Austin, appeared " +"four months later, with plans to release regular updates of the software " +"every few months. The early code came from the NASA Nebula platform and from" +" the Rackspace Cloud Files platform. In July 2011, Ubuntu Linux developers " +"adopted OpenStack." +msgstr "" + +#: ./doc/training-guides/module001-ch003-core-projects.xml34(emphasis) +msgid "OpenStack Releases" +msgstr "" + +#: ./doc/training-guides/module001-ch003-core-projects.xml38(td) +msgid "Release Name" +msgstr "" + +#: ./doc/training-guides/module001-ch003-core-projects.xml39(td) +msgid "Release Date" +msgstr "" + +#: ./doc/training-guides/module001-ch003-core-projects.xml40(td) +msgid "Included Components" +msgstr "" + +#: ./doc/training-guides/module001-ch003-core-projects.xml43(td) +msgid "Austin" +msgstr "" + +#: ./doc/training-guides/module001-ch003-core-projects.xml44(td) +msgid "21 October 2010" +msgstr "" + +#: ./doc/training-guides/module001-ch003-core-projects.xml45(td) +msgid "Nova, Swift" +msgstr "" + +#: ./doc/training-guides/module001-ch003-core-projects.xml48(td) +msgid "Bexar" +msgstr "" + +#: ./doc/training-guides/module001-ch003-core-projects.xml49(td) +msgid "3 February 2011" +msgstr "" + +#: ./doc/training-guides/module001-ch003-core-projects.xml50(td) +#: ./doc/training-guides/module001-ch003-core-projects.xml55(td) +#: ./doc/training-guides/module001-ch003-core-projects.xml60(td) +msgid "Nova, Glance, Swift" +msgstr "" + +#: ./doc/training-guides/module001-ch003-core-projects.xml53(td) +msgid "Cactus" +msgstr "" + +#: ./doc/training-guides/module001-ch003-core-projects.xml54(td) +msgid "15 April 2011" +msgstr "" + +#: ./doc/training-guides/module001-ch003-core-projects.xml58(td) +msgid "Diablo" +msgstr "" + +#: ./doc/training-guides/module001-ch003-core-projects.xml59(td) +msgid "22 September 2011" +msgstr "" + +#: ./doc/training-guides/module001-ch003-core-projects.xml63(td) +msgid "Essex" +msgstr "" + +#: ./doc/training-guides/module001-ch003-core-projects.xml64(td) +msgid "5 April 2012" +msgstr "" + +#: ./doc/training-guides/module001-ch003-core-projects.xml65(td) +msgid "Nova, Glance, Swift, Horizon, Keystone" +msgstr "" + +#: ./doc/training-guides/module001-ch003-core-projects.xml69(td) +msgid "Folsom" +msgstr "" + +#: ./doc/training-guides/module001-ch003-core-projects.xml70(td) +msgid "27 September 2012" +msgstr "" + +#: ./doc/training-guides/module001-ch003-core-projects.xml71(td) +#: ./doc/training-guides/module001-ch003-core-projects.xml77(td) +msgid "Nova, Glance, Swift, Horizon, Keystone, Quantum, Cinder" +msgstr "" + +#: ./doc/training-guides/module001-ch003-core-projects.xml75(td) +msgid "Grizzly" +msgstr "" + +#: ./doc/training-guides/module001-ch003-core-projects.xml76(td) +msgid "4 April 2013" +msgstr "" + +#: ./doc/training-guides/module001-ch003-core-projects.xml81(td) +msgid "Havana" +msgstr "" + +#: ./doc/training-guides/module001-ch003-core-projects.xml82(td) +msgid "17 October 2013" +msgstr "" + +#: ./doc/training-guides/module001-ch003-core-projects.xml83(td) +msgid "Nova, Glance, Swift, Horizon, Keystone, Neutron, Cinder" +msgstr "" + +#: ./doc/training-guides/module001-ch003-core-projects.xml87(td) +#: ./doc/training-guides/sources/cinder/drivers.xml56(title) +msgid "Icehouse" +msgstr "" + +#: ./doc/training-guides/module001-ch003-core-projects.xml88(td) +msgid "April 2014" +msgstr "" + +#: ./doc/training-guides/module001-ch003-core-projects.xml89(td) +msgid "" +"Nova, Glance, Swift, Horizon, Keystone, Neutron, Cinder, (More to be added)" +msgstr "" + +#: ./doc/training-guides/module001-ch003-core-projects.xml95(para) +msgid "Some OpenStack users include:" +msgstr "" + +#: ./doc/training-guides/module001-ch003-core-projects.xml98(para) +msgid "PayPal / eBay" +msgstr "" + +#: ./doc/training-guides/module001-ch003-core-projects.xml101(para) +msgid "NASA" +msgstr "" + +#: ./doc/training-guides/module001-ch003-core-projects.xml104(para) +msgid "CERN" +msgstr "" + +#: ./doc/training-guides/module001-ch003-core-projects.xml107(para) +msgid "Yahoo!" +msgstr "" + +#: ./doc/training-guides/module001-ch003-core-projects.xml110(para) +msgid "Rackspace Cloud" +msgstr "" + +#: ./doc/training-guides/module001-ch003-core-projects.xml113(para) +msgid "HP Public Cloud" +msgstr "" + +#: ./doc/training-guides/module001-ch003-core-projects.xml116(para) +msgid "MercadoLibre.com" +msgstr "" + +#: ./doc/training-guides/module001-ch003-core-projects.xml119(para) +msgid "AT&T" +msgstr "" + +#: ./doc/training-guides/module001-ch003-core-projects.xml122(para) +msgid "KT (formerly Korea Telecom)" +msgstr "" + +#: ./doc/training-guides/module001-ch003-core-projects.xml125(para) +msgid "Deutsche Telekom" +msgstr "" + +#: ./doc/training-guides/module001-ch003-core-projects.xml128(para) +msgid "Wikimedia Labs" +msgstr "" + +#: ./doc/training-guides/module001-ch003-core-projects.xml131(para) +msgid "Hostalia of Telef nica Group" +msgstr "" + +#: ./doc/training-guides/module001-ch003-core-projects.xml134(para) +msgid "SUSE Cloud solution" +msgstr "" + +#: ./doc/training-guides/module001-ch003-core-projects.xml137(para) +msgid "Red Hat OpenShift PaaS solution" +msgstr "" + +#: ./doc/training-guides/module001-ch003-core-projects.xml140(para) +msgid "Zadara Storage" +msgstr "" + +#: ./doc/training-guides/module001-ch003-core-projects.xml143(para) +msgid "Mint Services" +msgstr "" + +#: ./doc/training-guides/module001-ch003-core-projects.xml146(para) +msgid "GridCentric" +msgstr "" + +#: ./doc/training-guides/module001-ch003-core-projects.xml149(para) +msgid "" +"OpenStack is a true and innovative open standard. For more user stories, see" +" http://goo.gl/aF4lsL." +msgstr "" + +#: ./doc/training-guides/module001-ch003-core-projects.xml152(guilabel) +msgid "Release Cycle" +msgstr "" + +#: ./doc/training-guides/module001-ch003-core-projects.xml154(title) +msgid "Community Heartbeat" +msgstr "" + +#: ./doc/training-guides/module001-ch003-core-projects.xml161(para) +msgid "" +"OpenStack is based on a coordinated 6-month release cycle with frequent " +"development milestones. You can find a link to the current development " +"release schedule here. The Release Cycle is made of four major stages. " +"Various OpenStack releases are named as follows Various Companies " +"Contributing to OpenStack" +msgstr "" + +#: ./doc/training-guides/module001-ch003-core-projects.xml167(title) +msgid "Various Projects under OpenStack" +msgstr "" + +#: ./doc/training-guides/module001-ch003-core-projects.xml174(para) +msgid "" +"The creation of OpenStack took an estimated 249 years of effort (COCOMO " +"model)." +msgstr "" + +#: ./doc/training-guides/module001-ch003-core-projects.xml176(para) +msgid "In a nutshell, OpenStack has:" +msgstr "" + +#: ./doc/training-guides/module001-ch003-core-projects.xml179(para) +msgid "" +"64,396 commits made by 1,128 contributors, with its first commit made in " +"May, 2010." +msgstr "" + +#: ./doc/training-guides/module001-ch003-core-projects.xml183(para) +msgid "" +"908,491 lines of code. OpenStack is written mostly in Python with an average" +" number of source code comments." +msgstr "" + +#: ./doc/training-guides/module001-ch003-core-projects.xml187(para) +msgid "A code base with a long source history." +msgstr "" + +#: ./doc/training-guides/module001-ch003-core-projects.xml190(para) +msgid "Increasing Y-O-Y commits." +msgstr "" + +#: ./doc/training-guides/module001-ch003-core-projects.xml193(para) +msgid "" +"A very large development team comprised of people from around the world." +msgstr "" + +#: ./doc/training-guides/module001-ch003-core-projects.xml198(title) +msgid "Programming Languages used to design OpenStack" +msgstr "" + +#: ./doc/training-guides/module001-ch003-core-projects.xml205(para) +msgid "" +"For an overview of OpenStack refer to http://www.openstack.org or " +"http://goo.gl/4q7nVI. Common questions and answers are also covered here." +msgstr "" + +#: ./doc/training-guides/module001-ch003-core-projects.xml208(guilabel) +msgid "Core Projects Overview" +msgstr "" + +#: ./doc/training-guides/module001-ch003-core-projects.xml209(para) +msgid "" +"Let's take a dive into some of the technical aspects of OpenStack. Its " +"scalability and flexibility are a few of the awesome features that make it a" +" rock-solid cloud computing platform. The OpenStack core projects serve the " +"community and its demands." +msgstr "" + +#: ./doc/training-guides/module001-ch003-core-projects.xml214(para) +msgid "" +"Being a cloud computing platform, OpenStack consists of many core and " +"incubated projects which makes it really good as an IaaS cloud computing " +"platform/Operating System. But the following points are the main components " +"of OpenStack that are necessary to be present in the cloud to call it an " +"OpenStack Cloud." +msgstr "" + +#: ./doc/training-guides/module001-ch003-core-projects.xml220(guimenu) +msgid "Components of OpenStack" +msgstr "" + +#: ./doc/training-guides/module001-ch003-core-projects.xml221(para) +msgid "" +"OpenStack has a modular architecture with various code names for its " +"components. OpenStack has several shared services that span the three " +"pillars of compute, storage and networking, making it easier to implement " +"and operate your cloud. These services - including identity, image " +"management and a web interface - integrate the OpenStack components with " +"each other as well as external systems to provide a unified experience for " +"users as they interact with different cloud resources." +msgstr "" + +#: ./doc/training-guides/module001-ch003-core-projects.xml229(guisubmenu) +msgid "Compute (Nova)" +msgstr "" + +#: ./doc/training-guides/module001-ch003-core-projects.xml230(para) +msgid "" +"The OpenStack cloud operating system enables enterprises and service " +"providers to offer on-demand computing resources, by provisioning and " +"managing large networks of virtual machines. Compute resources are " +"accessible via APIs for developers building cloud applications and via web " +"interfaces for administrators and users. The compute architecture is " +"designed to scale horizontally on standard hardware." +msgstr "" + +#: ./doc/training-guides/module001-ch003-core-projects.xml238(title) +msgid "" +"OpenStack Compute: Provision and manage large networks of virtual machines" +msgstr "" + +#: ./doc/training-guides/module001-ch003-core-projects.xml246(para) +msgid "" +"OpenStack Compute (Nova) is a cloud computing fabric controller (the main " +"part of an IaaS system). It is written in Python and uses many external " +"libraries such as Eventlet (for concurrent programming), Kombu (for AMQP " +"communication), and SQLAlchemy (for database access). Nova's architecture is" +" designed to scale horizontally on standard hardware with no proprietary " +"hardware or software requirements and provide the ability to integrate with " +"legacy systems and third party technologies. It is designed to manage and " +"automate pools of computer resources and can work with widely available " +"virtualization technologies, as well as bare metal and high-performance " +"computing (HPC) configurations. KVM and XenServer are available choices for " +"hypervisor technology, together with Hyper-V and Linux container technology " +"such as LXC. In addition to different hypervisors, OpenStack runs on ARM." +msgstr "" + +#: ./doc/training-guides/module001-ch003-core-projects.xml262(emphasis) +msgid "Popular Use Cases:" +msgstr "" + +#: ./doc/training-guides/module001-ch003-core-projects.xml265(para) +msgid "" +"Service providers offering an IaaS compute platform or services higher up " +"the stack" +msgstr "" + +#: ./doc/training-guides/module001-ch003-core-projects.xml269(para) +msgid "" +"IT departments acting as cloud service providers for business units and " +"project teams" +msgstr "" + +#: ./doc/training-guides/module001-ch003-core-projects.xml273(para) +msgid "Processing big data with tools like Hadoop" +msgstr "" + +#: ./doc/training-guides/module001-ch003-core-projects.xml276(para) +msgid "" +"Scaling compute up and down to meet demand for web resources and " +"applications" +msgstr "" + +#: ./doc/training-guides/module001-ch003-core-projects.xml280(para) +msgid "" +"High-performance computing (HPC) environments processing diverse and " +"intensive workloads" +msgstr "" + +#: ./doc/training-guides/module001-ch003-core-projects.xml284(guisubmenu) +#: ./doc/training-guides/module003-ch003-obj-store-capabilities.xml86(title) +msgid "Object Storage(Swift)" +msgstr "" + +#: ./doc/training-guides/module001-ch003-core-projects.xml285(para) +msgid "" +"In addition to traditional enterprise-class storage technology, many " +"organizations now have a variety of storage needs with varying performance " +"and price requirements. OpenStack has support for both Object Storage and " +"Block Storage, with many deployment options for each depending on the use " +"case." +msgstr "" + +#: ./doc/training-guides/module001-ch003-core-projects.xml292(title) +msgid "" +"OpenStack Storage: Object and Block storage for use with servers and " +"applications" +msgstr "" + +#: ./doc/training-guides/module001-ch003-core-projects.xml300(para) +msgid "" +"OpenStack Object Storage (Swift) is a scalable redundant storage system. " +"Objects and files are written to multiple disk drives spread throughout " +"servers in the data center, with the OpenStack software responsible for " +"ensuring data replication and integrity across the cluster. Storage clusters" +" scale horizontally simply by adding new servers. Should a server or hard " +"drive fail, OpenStack replicates its content from other active nodes to new " +"locations in the cluster. Because OpenStack uses software logic to ensure " +"data replication and distribution across different devices, inexpensive " +"commodity hard drives and servers can be used." +msgstr "" + +#: ./doc/training-guides/module001-ch003-core-projects.xml311(para) +#: ./doc/training-guides/module003-ch001-intro-objstore.xml24(para) +msgid "" +"Object Storage is ideal for cost effective, scale-out storage. It provides a" +" fully distributed, API-accessible storage platform that can be integrated " +"directly into applications or used for backup, archiving and data retention." +" Block Storage allows block devices to be exposed and connected to compute " +"instances for expanded storage, better performance and integration with " +"enterprise storage platforms, such as NetApp, Nexenta and SolidFire." +msgstr "" + +#: ./doc/training-guides/module001-ch003-core-projects.xml319(para) +msgid "A few details on OpenStack’s Object Storage" +msgstr "" + +#: ./doc/training-guides/module001-ch003-core-projects.xml322(para) +#: ./doc/training-guides/module003-ch003-obj-store-capabilities.xml10(para) +msgid "" +"OpenStack provides redundant, scalable object storage using clusters of " +"standardized servers capable of storing petabytes of data" +msgstr "" + +#: ./doc/training-guides/module001-ch003-core-projects.xml327(para) +#: ./doc/training-guides/module003-ch003-obj-store-capabilities.xml15(para) +msgid "" +"Object Storage is not a traditional file system, but rather a distributed " +"storage system for static data such as virtual machine images, photo " +"storage, email storage, backups and archives. Having no central \"brain\" or" +" master point of control provides greater scalability, redundancy and " +"durability." +msgstr "" + +#: ./doc/training-guides/module001-ch003-core-projects.xml335(para) +#: ./doc/training-guides/module003-ch003-obj-store-capabilities.xml23(para) +msgid "" +"Objects and files are written to multiple disk drives spread throughout " +"servers in the data center, with the OpenStack software responsible for " +"ensuring data replication and integrity across the cluster." +msgstr "" + +#: ./doc/training-guides/module001-ch003-core-projects.xml341(para) +#: ./doc/training-guides/module003-ch003-obj-store-capabilities.xml30(para) +msgid "" +"Storage clusters scale horizontally simply by adding new servers. Should a " +"server or hard drive fail, OpenStack replicates its content from other " +"active nodes to new locations in the cluster. Because OpenStack uses " +"software logic to ensure data replication and distribution across different " +"devices, inexpensive commodity hard drives and servers can be used in lieu " +"of more expensive equipment." +msgstr "" + +#: ./doc/training-guides/module001-ch003-core-projects.xml351(guisubmenu) +msgid "Block Storage(Cinder)" +msgstr "" + +#: ./doc/training-guides/module001-ch003-core-projects.xml352(para) +msgid "" +"OpenStack Block Storage (Cinder) provides persistent block level storage " +"devices for use with OpenStack compute instances. The block storage system " +"manages the creation, attaching and detaching of the block devices to " +"servers. Block storage volumes are fully integrated into OpenStack Compute " +"and the Dashboard allowing for cloud users to manage their own storage " +"needs. In addition to local Linux server storage, it can use storage " +"platforms including Ceph, CloudByte, Coraid, EMC (VMAX and VNX), GlusterFS, " +"IBM Storage (Storwize family, SAN Volume Controller, and XIV Storage " +"System), Linux LIO, NetApp, Nexenta, Scality, SolidFire and HP (Store " +"Virtual and StoreServ 3Par families). Block storage is appropriate for " +"performance sensitive scenarios such as database storage, expandable file " +"systems, or providing a server with access to raw block level storage. " +"Snapshot management provides powerful functionality for backing up data " +"stored on block storage volumes. Snapshots can be restored or used to create" +" a new block storage volume." +msgstr "" + +#: ./doc/training-guides/module001-ch003-core-projects.xml370(emphasis) +msgid "A few points on OpenStack Block Storage:" +msgstr "" + +#: ./doc/training-guides/module001-ch003-core-projects.xml403(guisubmenu) +msgid "Networking(Neutron)" +msgstr "" + +#: ./doc/training-guides/module001-ch003-core-projects.xml404(para) +msgid "" +"Today's data center networks contain more devices than ever before. From " +"servers, network equipment, storage systems and security appliances, many of" +" which are further divided into virtual machines and virtual networks. The " +"number of IP addresses, routing configurations and security rules can " +"quickly grow into the millions. Traditional network management techniques " +"fall short of providing a truly scalable, automated approach to managing " +"these next-generation networks. At the same time, users expect more control " +"and flexibility with quicker provisioning." +msgstr "" + +#: ./doc/training-guides/module001-ch003-core-projects.xml413(para) +msgid "" +"OpenStack Networking is a pluggable, scalable and API-driven system for " +"managing networks and IP addresses. Like other aspects of the cloud " +"operating system, it can be used by administrators and users to increase the" +" value of existing data center assets. OpenStack Networking ensures the " +"network will not be the bottleneck or limiting factor in a cloud deployment " +"and gives users real self-service, even over their network configurations." +msgstr "" + +#: ./doc/training-guides/module001-ch003-core-projects.xml422(title) +msgid "" +"OpenStack Networking: Pluggable, scalable, API-driven network and IP " +"management" +msgstr "" + +#: ./doc/training-guides/module001-ch003-core-projects.xml430(para) +msgid "" +"OpenStack Networking (Neutron, formerly Quantum]) is a system for managing " +"networks and IP addresses. Like other aspects of the cloud operating system," +" it can be used by administrators and users to increase the value of " +"existing data center assets. OpenStack Networking ensures the network will " +"not be the bottleneck or limiting factor in a cloud deployment and gives " +"users real self-service, even over their network configurations." +msgstr "" + +#: ./doc/training-guides/module001-ch003-core-projects.xml438(para) +msgid "" +"OpenStack Neutron provides networking models for different applications or " +"user groups. Standard models include flat networks or VLANs for separation " +"of servers and traffic. OpenStack Networking manages IP addresses, allowing " +"for dedicated static IPs or DHCP. Floating IPs allow traffic to be " +"dynamically re routed to any of your compute resources, which allows you to " +"redirect traffic during maintenance or in the case of failure. Users can " +"create their own networks, control traffic and connect servers and devices " +"to one or more networks. Administrators can take advantage of software-" +"defined networking (SDN) technology like OpenFlow to allow for high levels " +"of multi-tenancy and massive scale. OpenStack Networking has an extension " +"framework allowing additional network services, such as intrusion detection " +"systems (IDS), load balancing, firewalls and virtual private networks (VPN) " +"to be deployed and managed." +msgstr "" + +#: ./doc/training-guides/module001-ch003-core-projects.xml454(para) +msgid "Networking Capabilities" +msgstr "" + +#: ./doc/training-guides/module001-ch003-core-projects.xml457(para) +msgid "" +"OpenStack provides flexible networking models to suit the needs of different" +" applications or user groups. Standard models include flat networks or VLANs" +" for separation of servers and traffic." +msgstr "" + +#: ./doc/training-guides/module001-ch003-core-projects.xml463(para) +msgid "" +"OpenStack Networking manages IP addresses, allowing for dedicated static IPs" +" or DHCP. Floating IPs allow traffic to be dynamically rerouted to any of " +"your compute resources, which allows you to redirect traffic during " +"maintenance or in the case of failure." +msgstr "" + +#: ./doc/training-guides/module001-ch003-core-projects.xml470(para) +msgid "" +"Users can create their own networks, control traffic and connect servers and" +" devices to one or more networks." +msgstr "" + +#: ./doc/training-guides/module001-ch003-core-projects.xml475(para) +msgid "" +"The pluggable backend architecture lets users take advantage of commodity " +"gear or advanced networking services from supported vendors." +msgstr "" + +#: ./doc/training-guides/module001-ch003-core-projects.xml480(para) +msgid "" +"Administrators can take advantage of software-defined networking (SDN) " +"technology like OpenFlow to allow for high levels of multi-tenancy and " +"massive scale." +msgstr "" + +#: ./doc/training-guides/module001-ch003-core-projects.xml486(para) +msgid "" +"OpenStack Networking has an extension framework allowing additional network " +"services, such as intrusion detection systems (IDS), load balancing, " +"firewalls and virtual private networks (VPN) to be deployed and managed." +msgstr "" + +#: ./doc/training-guides/module001-ch003-core-projects.xml493(guisubmenu) +msgid "Dashboard(Horizon)" +msgstr "" + +#: ./doc/training-guides/module001-ch003-core-projects.xml494(para) +msgid "" +"OpenStack Dashboard (Horizon) provides administrators and users a graphical " +"interface to access, provision and automate cloud-based resources. The " +"design allows for third party products and services, such as billing, " +"monitoring and additional management tools. Service providers and other " +"commercial vendors can customize the dashboard with their own brand." +msgstr "" + +#: ./doc/training-guides/module001-ch003-core-projects.xml500(para) +msgid "" +"The dashboard is just one way to interact with OpenStack resources. " +"Developers can automate access or build tools to manage their resources " +"using the native OpenStack API or the EC2 compatibility API." +msgstr "" + +#: ./doc/training-guides/module001-ch003-core-projects.xml504(guisubmenu) +msgid "Identity Service(Keystone)" +msgstr "" + +#: ./doc/training-guides/module001-ch003-core-projects.xml505(para) +msgid "" +"OpenStack Identity (Keystone) provides a central directory of users mapped " +"to the OpenStack services they can access. It acts as a common " +"authentication system across the cloud operating system and can integrate " +"with existing backend directory services like LDAP. It supports multiple " +"forms of authentication including standard username and password " +"credentials, token-based systems and AWS-style (i.e. Amazon Web Services) " +"logins. Additionally, the catalog provides a query-able list of all of the " +"services deployed in an OpenStack cloud in a single registry. Users and " +"third-party tools can programmatically determine which resources they can " +"access." +msgstr "" + +#: ./doc/training-guides/module001-ch003-core-projects.xml516(para) +msgid "" +"Additionally, the catalog provides a query-able list of all of the services " +"deployed in an OpenStack cloud in a single registry. Users and third-party " +"tools can programmatically determine which resources they can access." +msgstr "" + +#: ./doc/training-guides/module001-ch003-core-projects.xml520(para) +msgid "The OpenStack Identity Service enables administrators to:" +msgstr "" + +#: ./doc/training-guides/module001-ch003-core-projects.xml524(para) +msgid "Configure centralized policies across users and systems" +msgstr "" + +#: ./doc/training-guides/module001-ch003-core-projects.xml528(para) +msgid "" +"Create users and tenants and define permissions for compute, storage, and " +"networking resources by using role-based access control (RBAC) features" +msgstr "" + +#: ./doc/training-guides/module001-ch003-core-projects.xml533(para) +msgid "" +"Integrate with an existing directory, like LDAP, to provide a single source " +"of authentication across the enterprise" +msgstr "" + +#: ./doc/training-guides/module001-ch003-core-projects.xml538(para) +msgid "The OpenStack Identity Service enables users to:" +msgstr "" + +#: ./doc/training-guides/module001-ch003-core-projects.xml541(para) +msgid "List the services to which they have access" +msgstr "" + +#: ./doc/training-guides/module001-ch003-core-projects.xml544(para) +msgid "Make API requests" +msgstr "" + +#: ./doc/training-guides/module001-ch003-core-projects.xml547(para) +msgid "Log into the web dashboard to create resources owned by their account" +msgstr "" + +#: ./doc/training-guides/module001-ch003-core-projects.xml551(guisubmenu) +msgid "Image Service(Glance)" +msgstr "" + +#: ./doc/training-guides/module001-ch003-core-projects.xml552(para) +msgid "" +"OpenStack Image Service (Glance) provides discovery, registration and " +"delivery services for disk and server images. Stored images can be used as a" +" template. It can also be used to store and catalog an unlimited number of " +"backups. The Image Service can store disk and server images in a variety of " +"back-ends, including OpenStack Object Storage. The Image Service API " +"provides a standard REST interface for querying information about disk " +"images and lets clients stream the images to new servers." +msgstr "" + +#: ./doc/training-guides/module001-ch003-core-projects.xml561(para) +msgid "" +"The Image Service can store disk and server images in a variety of back-" +"ends, including OpenStack Object Storage. The Image Service API provides a " +"standard REST interface for querying information about disk images and lets " +"clients stream the images to new servers." +msgstr "" + +#: ./doc/training-guides/module001-ch003-core-projects.xml566(para) +msgid "Capabilities of the Image Service include:" +msgstr "" + +#: ./doc/training-guides/module001-ch003-core-projects.xml569(para) +msgid "" +"Administrators can create base templates from which their users can start " +"new compute instances" +msgstr "" + +#: ./doc/training-guides/module001-ch003-core-projects.xml573(para) +msgid "" +"Users can choose from available images, or create their own from existing " +"servers" +msgstr "" + +#: ./doc/training-guides/module001-ch003-core-projects.xml577(para) +msgid "" +"Snapshots can also be stored in the Image Service so that virtual machines " +"can be backed up quickly" +msgstr "" + +#: ./doc/training-guides/module001-ch003-core-projects.xml581(para) +msgid "" +"A multi-format image registry, the image service allows uploads of private " +"and public images in a variety of formats, including:" +msgstr "" + +#: ./doc/training-guides/module001-ch003-core-projects.xml586(para) +msgid "Raw" +msgstr "" + +#: ./doc/training-guides/module001-ch003-core-projects.xml589(para) +msgid "Machine (kernel/ramdisk outside of image, also known as AMI)" +msgstr "" + +#: ./doc/training-guides/module001-ch003-core-projects.xml593(para) +msgid "VHD (Hyper-V)" +msgstr "" + +#: ./doc/training-guides/module001-ch003-core-projects.xml596(para) +msgid "VDI (VirtualBox)" +msgstr "" + +#: ./doc/training-guides/module001-ch003-core-projects.xml599(para) +msgid "qcow2 (Qemu/KVM)" +msgstr "" + +#: ./doc/training-guides/module001-ch003-core-projects.xml602(para) +msgid "VMDK (VMWare)" +msgstr "" + +#: ./doc/training-guides/module001-ch003-core-projects.xml605(para) +msgid "OVF (VMWare, others)" +msgstr "" + +#: ./doc/training-guides/module001-ch003-core-projects.xml608(para) +msgid "" +"To checkout the complete list of Core and Incubated projects under OpenStack" +" check out OpenStack’s Launchpad Project Page here : http://goo.gl/ka4SrV" +msgstr "" + +#: ./doc/training-guides/module001-ch003-core-projects.xml611(guisubmenu) +msgid "Amazon Web Services compatibility" +msgstr "" + +#: ./doc/training-guides/module001-ch003-core-projects.xml612(para) +msgid "" +"OpenStack APIs are compatible with Amazon EC2 and Amazon S3 and thus client " +"applications written for Amazon Web Services can be used with OpenStack with" +" minimal porting effort." +msgstr "" + +#: ./doc/training-guides/module001-ch003-core-projects.xml616(guilabel) +msgid "Governance" +msgstr "" + +#: ./doc/training-guides/module001-ch003-core-projects.xml617(para) +msgid "" +"OpenStack is governed by a non-profit foundation and its board of directors," +" a technical committee and a user committee." +msgstr "" + +#: ./doc/training-guides/module001-ch003-core-projects.xml620(para) +msgid "" +"The foundation's stated mission is by providing shared resources to help " +"achieve the OpenStack Mission by Protecting, Empowering, and Promoting " +"OpenStack software and the community around it, including users, developers " +"and the entire ecosystem. Though, it has little to do with the development " +"of the software, which is managed by the technical committee - an elected " +"group that represents the contributors to the project, and has oversight on " +"all technical matters." +msgstr "" + +#: ./doc/training-guides/card009.xml6(title) +msgid "Install Ubuntu" +msgstr "" + +#: ./doc/training-guides/module003-ch000-openstack-objstore.xml9(title) +msgid "OpenStack Object Storage" +msgstr "" + +#: ./doc/training-guides/card043-ovs-in-network-node.xml7(title) +msgid "OVS Installation and Configuration in Network node" +msgstr "" + +#: ./doc/training-guides/module003-ch008-account-reaper.xml7(title) +msgid "Account Reaper" +msgstr "" + +#: ./doc/training-guides/module003-ch008-account-reaper.xml8(para) +msgid "" +"The Account Reaper removes data from deleted accounts in the background." +msgstr "" + +#: ./doc/training-guides/module003-ch008-account-reaper.xml10(para) +msgid "" +"An account is marked for deletion by a reseller issuing a DELETE request on " +"the account’s storage URL. This simply puts the value DELETED into the " +"status column of the account_stat table in the account database (and " +"replicas), indicating the data for the account should be deleted later." +msgstr "" + +#: ./doc/training-guides/module003-ch008-account-reaper.xml15(para) +msgid "" +"There is normally no set retention time and no undelete; it is assumed the " +"reseller will implement such features and only call DELETE on the account " +"once it is truly desired the account’s data be removed. However, in order to" +" protect the Swift cluster accounts from an improper or mistaken delete " +"request, you can set a delay_reaping value in the [account-reaper] section " +"of the account-server.conf to delay the actual deletion of data. At this " +"time, there is no utility to undelete an account; one would have to update " +"the account database replicas directly, setting the status column to an " +"empty string and updating the put_timestamp to be greater than the " +"delete_timestamp. (On the TODO list is writing a utility to perform this " +"task, preferably through a ReST call.)" +msgstr "" + +#: ./doc/training-guides/module003-ch008-account-reaper.xml28(para) +msgid "" +"The account reaper runs on each account server and scans the server " +"occasionally for account databases marked for deletion. It will only trigger" +" on accounts that server is the primary node for, so that multiple account " +"servers aren’t all trying to do the same work at the same time. Using " +"multiple servers to delete one account might improve deletion speed, but " +"requires coordination so they aren’t duplicating effort. Speed really isn’t " +"as much of a concern with data deletion and large accounts aren’t deleted " +"that often." +msgstr "" + +#: ./doc/training-guides/module003-ch008-account-reaper.xml37(para) +msgid "" +"The deletion process for an account itself is pretty straightforward. For " +"each container in the account, each object is deleted and then the container" +" is deleted. Any deletion requests that fail won’t stop the overall process," +" but will cause the overall process to fail eventually (for example, if an " +"object delete times out, the container won’t be able to be deleted later and" +" therefore the account won’t be deleted either). The overall process " +"continues even on a failure so that it doesn’t get hung up reclaiming " +"cluster space because of one troublesome spot. The account reaper will keep " +"trying to delete an account until it eventually becomes empty, at which " +"point the database reclaim process within the db_replicator will eventually " +"remove the database files." +msgstr "" + +#: ./doc/training-guides/module003-ch008-account-reaper.xml51(para) +msgid "" +"Sometimes a persistent error state can prevent some object or container from" +" being deleted. If this happens, you will see a message such as “Account " +"<name> has not been reaped since <date>” in the log. You can " +"control when this is logged with the reap_warn_after value in the [account-" +"reaper] section of the account-server.conf file. By default this is 30 days." +msgstr "" + +#: ./doc/training-guides/bk002-ch010-operator-network-node.xml10(title) +msgid "Days 7 to 8, 09:00 to 11:00, 11:15 to 12:30" +msgstr "" + +#: ./doc/training-guides/bk002-ch010-operator-network-node.xml14(title) +msgid "Review Associate Networking in OpenStack" +msgstr "" + +#: ./doc/training-guides/bk002-ch010-operator-network-node.xml21(title) +msgid "Review Associate OpenStack Networking Concepts" +msgstr "" + +#: ./doc/training-guides/bk002-ch010-operator-network-node.xml28(title) +#: ./doc/training-guides/bk002-ch004-operator-controller-node.xml35(title) +#: ./doc/training-guides/bk002-ch007-operator-compute-node.xml35(title) +#: ./doc/training-guides/bk002-ch013-operator-object-storage-node.xml28(title) +msgid "Review Associate Administration Tasks" +msgstr "" + +#. When image changes, this message will be marked fuzzy or untranslated for +#. you. +#. It doesn't matter what you translate it to: it's not used at all. +#: ./doc/training-guides/module001-ch006-overview-horizon-cli.xml107(None) +#: ./doc/training-guides/module001-ch006-overview-horizon-cli.xml727(None) +msgid "@@image: 'figures/image14.png'; md5=b3fcef10808f967f7e87f98d096bf2f9" +msgstr "" + +#. When image changes, this message will be marked fuzzy or untranslated for +#. you. +#. It doesn't matter what you translate it to: it's not used at all. +#: ./doc/training-guides/module001-ch006-overview-horizon-cli.xml195(None) +msgid "@@image: 'figures/image25.png'; md5=4c70d08fd2a0aedc8342ab61d3c62a94" +msgstr "" + +#. When image changes, this message will be marked fuzzy or untranslated for +#. you. +#. It doesn't matter what you translate it to: it's not used at all. +#: ./doc/training-guides/module001-ch006-overview-horizon-cli.xml212(None) +msgid "@@image: 'figures/image15.png'; md5=0e003df4e8edbde4ac9c11165d897e84" +msgstr "" + +#. When image changes, this message will be marked fuzzy or untranslated for +#. you. +#. It doesn't matter what you translate it to: it's not used at all. +#: ./doc/training-guides/module001-ch006-overview-horizon-cli.xml638(None) +msgid "@@image: 'figures/image00.png'; md5=6b0f5cb3009d447334ff8b5c5b2cd121" +msgstr "" + +#. When image changes, this message will be marked fuzzy or untranslated for +#. you. +#. It doesn't matter what you translate it to: it's not used at all. +#: ./doc/training-guides/module001-ch006-overview-horizon-cli.xml716(None) +msgid "@@image: 'figures/image30.png'; md5=d9eef0f7a1f99eee18a99e677c7c710b" +msgstr "" + +#: ./doc/training-guides/module001-ch006-overview-horizon-cli.xml8(guilabel) +msgid "How can I use an OpenStack cloud?" +msgstr "" + +#: ./doc/training-guides/module001-ch006-overview-horizon-cli.xml9(para) +msgid "" +"As an OpenStack cloud end user, you can provision your own resources within " +"the limits set by administrators. The examples in this guide show you how to" +" complete these tasks by using the OpenStack dashboard and command-line " +"clients. The dashboard, also known as horizon, is a Web-based graphical " +"interface. The command-line clients let you run simple commands to create " +"and manage resources in a cloud and automate tasks by using scripts. Each of" +" the core OpenStack projects has its own command-line client." +msgstr "" + +#: ./doc/training-guides/module001-ch006-overview-horizon-cli.xml18(para) +msgid "You can modify these examples for your specific use cases." +msgstr "" + +#: ./doc/training-guides/module001-ch006-overview-horizon-cli.xml20(para) +msgid "" +"In addition to these ways of interacting with a cloud, you can access the " +"OpenStack APIs indirectly through cURLcommands or open SDKs, or directly " +"through the APIs. You can automate access or build tools to manage resources" +" and services by using the native OpenStack APIs or the EC2 compatibility " +"API." +msgstr "" + +#: ./doc/training-guides/module001-ch006-overview-horizon-cli.xml25(para) +msgid "" +"To use the OpenStack APIs, it helps to be familiar with HTTP/1.1, RESTful " +"web services, the OpenStack services, and JSON or XML data serialization " +"formats." +msgstr "" + +#: ./doc/training-guides/module001-ch006-overview-horizon-cli.xml28(guilabel) +msgid "OpenStack dashboard" +msgstr "" + +#: ./doc/training-guides/module001-ch006-overview-horizon-cli.xml29(para) +msgid "" +"As a cloud end user, the OpenStack dashboard lets you to provision your own " +"resources within the limits set by administrators. You can modify these " +"examples to create other types and sizes of server instances." +msgstr "" + +#: ./doc/training-guides/module001-ch006-overview-horizon-cli.xml33(guilabel) +#: ./doc/training-guides/module001-ch006-overview-horizon-cli.xml121(emphasis) +#: ./doc/training-guides/module001-ch006-overview-horizon-cli.xml869(guilabel) +#: ./doc/training-guides/bk002-ch001-operator-getting-started.xml12(title) +#: ./doc/training-guides/bk001-ch001-associate-getting-started.xml12(title) +msgid "Overview" +msgstr "" + +#: ./doc/training-guides/module001-ch006-overview-horizon-cli.xml34(para) +msgid "" +"The following requirements must be fulfilled to access the OpenStack " +"dashboard:" +msgstr "" + +#: ./doc/training-guides/module001-ch006-overview-horizon-cli.xml38(para) +msgid "The cloud operator has set up an OpenStack cloud." +msgstr "" + +#: ./doc/training-guides/module001-ch006-overview-horizon-cli.xml42(para) +msgid "" +"You have a recent Web browser that supports HTML5. It must have cookies and " +"JavaScript enabled. To use the VNC client for the dashboard, which is based " +"on noVNC, your browser must support HTML5 Canvas and HTML5 WebSockets. For " +"more details and a list of browsers that support noVNC, seehttps://github.com/kanaka/noVNC/blob/master/README.md," +" andhttps://github.com/kanaka/noVNC/wiki/Browser-support, " +"respectively." +msgstr "" + +#: ./doc/training-guides/module001-ch006-overview-horizon-cli.xml60(para) +msgid "" +"Learn how to log in to the dashboard and get a short overview of the " +"interface." +msgstr "" + +#: ./doc/training-guides/module001-ch006-overview-horizon-cli.xml62(guilabel) +msgid "Log in to the dashboard" +msgstr "" + +#: ./doc/training-guides/module001-ch006-overview-horizon-cli.xml63(para) +msgid "To log in to the dashboard" +msgstr "" + +#: ./doc/training-guides/module001-ch006-overview-horizon-cli.xml66(para) +msgid "Ask your cloud operator for the following information:" +msgstr "" + +#: ./doc/training-guides/module001-ch006-overview-horizon-cli.xml72(para) +msgid "" +"The hostname or public IP address from which you can access the dashboard." +msgstr "" + +#: ./doc/training-guides/module001-ch006-overview-horizon-cli.xml76(para) +msgid "" +"The dashboard is available on the node that has the nova-dashboard server " +"role." +msgstr "" + +#: ./doc/training-guides/module001-ch006-overview-horizon-cli.xml80(para) +msgid "The username and password with which you can log in to the dashboard." +msgstr "" + +#: ./doc/training-guides/module001-ch006-overview-horizon-cli.xml86(para) +msgid "" +"Open a Web browser that supports HTML5. Make sure that JavaScript and " +"cookies are enabled." +msgstr "" + +#: ./doc/training-guides/module001-ch006-overview-horizon-cli.xml90(para) +msgid "" +"As a URL, enter the host name or IP address that you got from the cloud " +"operator." +msgstr "" + +#: ./doc/training-guides/module001-ch006-overview-horizon-cli.xml95(link) +msgid "https://IP_ADDRESS_OR_HOSTNAME/" +msgstr "" + +#: ./doc/training-guides/module001-ch006-overview-horizon-cli.xml98(para) +msgid "" +"On the dashboard log in page, enter your user name and password and click " +"Sign In." +msgstr "" + +#: ./doc/training-guides/module001-ch006-overview-horizon-cli.xml102(para) +msgid "After you log in, the following page appears:" +msgstr "" + +#: ./doc/training-guides/module001-ch006-overview-horizon-cli.xml104(title) +msgid "OpenStack Dashboard - Overview" +msgstr "" + +#: ./doc/training-guides/module001-ch006-overview-horizon-cli.xml111(para) +msgid "" +"The top-level row shows the username that you logged in with. You can also " +"access Settingsor Sign Outof the Web interface." +msgstr "" + +#: ./doc/training-guides/module001-ch006-overview-horizon-cli.xml114(para) +msgid "" +"If you are logged in as an end user rather than an admin user, the main " +"screen shows only the Projecttab." +msgstr "" + +#: ./doc/training-guides/module001-ch006-overview-horizon-cli.xml116(guilabel) +msgid "OpenStack dashboard – Project tab" +msgstr "" + +#: ./doc/training-guides/module001-ch006-overview-horizon-cli.xml117(para) +msgid "" +"This tab shows details for the projects, or projects, of which you are a " +"member." +msgstr "" + +#: ./doc/training-guides/module001-ch006-overview-horizon-cli.xml119(para) +msgid "" +"Select a project from the drop-down list on the left-hand side to access the" +" following categories:" +msgstr "" + +#: ./doc/training-guides/module001-ch006-overview-horizon-cli.xml122(para) +msgid "Shows basic reports on the project." +msgstr "" + +#: ./doc/training-guides/module001-ch006-overview-horizon-cli.xml123(emphasis) +msgid "Instances" +msgstr "" + +#: ./doc/training-guides/module001-ch006-overview-horizon-cli.xml124(para) +msgid "Lists instances and volumes created by users of the project." +msgstr "" + +#: ./doc/training-guides/module001-ch006-overview-horizon-cli.xml126(para) +msgid "" +"From here, you can stop, pause, or reboot any instances or connect to them " +"through virtual network computing (VNC)." +msgstr "" + +#: ./doc/training-guides/module001-ch006-overview-horizon-cli.xml130(para) +msgid "Lists volumes created by users of the project." +msgstr "" + +#: ./doc/training-guides/module001-ch006-overview-horizon-cli.xml131(para) +msgid "From here, you can create or delete volumes." +msgstr "" + +#: ./doc/training-guides/module001-ch006-overview-horizon-cli.xml132(emphasis) +msgid "Images & Snapshots" +msgstr "" + +#: ./doc/training-guides/module001-ch006-overview-horizon-cli.xml134(para) +msgid "" +"Lists images and snapshots created by users of the project, plus any images " +"that are publicly available. Includes volume snapshots. From here, you can " +"create and delete images and snapshots, and launch instances from images and" +" snapshots." +msgstr "" + +#: ./doc/training-guides/module001-ch006-overview-horizon-cli.xml139(emphasis) +msgid "Access & Security" +msgstr "" + +#: ./doc/training-guides/module001-ch006-overview-horizon-cli.xml141(para) +msgid "" +"On the Security Groupstab, you can list, " +"create, and delete security groups and edit rules for security groups." +msgstr "" + +#: ./doc/training-guides/module001-ch006-overview-horizon-cli.xml144(para) +msgid "" +"On the Keypairstab, you can list, create," +" and import keypairs, and delete keypairs." +msgstr "" + +#: ./doc/training-guides/module001-ch006-overview-horizon-cli.xml146(para) +msgid "" +"On the Floating IPstab, you can allocate " +"an IP address to or release it from a project." +msgstr "" + +#: ./doc/training-guides/module001-ch006-overview-horizon-cli.xml149(para) +msgid "" +"On the API Accesstab, you can list the " +"API endpoints." +msgstr "" + +#: ./doc/training-guides/module001-ch006-overview-horizon-cli.xml151(guilabel) +#: ./doc/training-guides/module001-ch006-overview-horizon-cli.xml1073(guilabel) +msgid "Manage images" +msgstr "" + +#: ./doc/training-guides/module001-ch006-overview-horizon-cli.xml152(para) +msgid "" +"During setup of OpenStack cloud, the cloud operator sets user permissions to" +" manage images. Image upload and management might be restricted to only " +"cloud administrators or cloud operators. Though you can complete most tasks " +"with the OpenStack dashboard, you can manage images through only the glance " +"and nova clients or the Image Service and Compute APIs." +msgstr "" + +#: ./doc/training-guides/module001-ch006-overview-horizon-cli.xml158(guilabel) +msgid "Set up access and security" +msgstr "" + +#: ./doc/training-guides/module001-ch006-overview-horizon-cli.xml159(para) +msgid "" +"Before you launch a virtual machine, you can add security group rules to " +"enable users to ping and SSH to the instances. To do so, you either add " +"rules to the default security group or add a security group with rules. For " +"information, seethe section called “Add " +"security group rules”." +msgstr "" + +#: ./doc/training-guides/module001-ch006-overview-horizon-cli.xml165(para) +msgid "" +"Keypairs are SSH credentials that are injected into images when they are " +"launched. For this to work, the image must contain the cloud-init package. " +"For information, seethe section called “Add keypairs”." +msgstr "" + +#: ./doc/training-guides/module001-ch006-overview-horizon-cli.xml170(guilabel) +msgid "Add security group rules" +msgstr "" + +#: ./doc/training-guides/module001-ch006-overview-horizon-cli.xml171(para) +msgid "" +"The following procedure shows you how to add rules to the default security " +"group." +msgstr "" + +#: ./doc/training-guides/module001-ch006-overview-horizon-cli.xml173(para) +msgid "To add rules to the default security group" +msgstr "" + +#: ./doc/training-guides/module001-ch006-overview-horizon-cli.xml176(para) +#: ./doc/training-guides/module001-ch006-overview-horizon-cli.xml295(para) +#: ./doc/training-guides/module001-ch006-overview-horizon-cli.xml388(para) +#: ./doc/training-guides/module001-ch006-overview-horizon-cli.xml645(para) +#: ./doc/training-guides/module001-ch006-overview-horizon-cli.xml684(para) +#: ./doc/training-guides/module001-ch006-overview-horizon-cli.xml761(para) +#: ./doc/training-guides/module001-ch006-overview-horizon-cli.xml1023(para) +msgid "Log in to the OpenStack dashboard." +msgstr "" + +#: ./doc/training-guides/module001-ch006-overview-horizon-cli.xml179(para) +#: ./doc/training-guides/module001-ch006-overview-horizon-cli.xml298(para) +#: ./doc/training-guides/module001-ch006-overview-horizon-cli.xml391(para) +#: ./doc/training-guides/module001-ch006-overview-horizon-cli.xml648(para) +#: ./doc/training-guides/module001-ch006-overview-horizon-cli.xml687(para) +#: ./doc/training-guides/module001-ch006-overview-horizon-cli.xml737(para) +msgid "" +"If you are a member of multiple projects, select a project from the drop-" +"down list at the top of the Projecttab." +msgstr "" + +#: ./doc/training-guides/module001-ch006-overview-horizon-cli.xml184(para) +#: ./doc/training-guides/module001-ch006-overview-horizon-cli.xml303(para) +msgid "Click the Access & Securitycategory." +msgstr "" + +#: ./doc/training-guides/module001-ch006-overview-horizon-cli.xml187(para) +msgid "" +"The dashboard shows the security groups that are available for this project." +msgstr "" + +#: ./doc/training-guides/module001-ch006-overview-horizon-cli.xml192(title) +msgid "OpenStack Dashboard - Security Groups" +msgstr "" + +#: ./doc/training-guides/module001-ch006-overview-horizon-cli.xml201(para) +msgid "Select the default security group and click Edit Rules." +msgstr "" + +#: ./doc/training-guides/module001-ch006-overview-horizon-cli.xml205(para) +msgid "The Security Group Rulespage appears:" +msgstr "" + +#: ./doc/training-guides/module001-ch006-overview-horizon-cli.xml209(title) +msgid "OpenStack Dashboard - Security Group Rules" +msgstr "" + +#: ./doc/training-guides/module001-ch006-overview-horizon-cli.xml218(para) +msgid "Add a TCP rule" +msgstr "" + +#: ./doc/training-guides/module001-ch006-overview-horizon-cli.xml221(para) +#: ./doc/training-guides/module001-ch006-overview-horizon-cli.xml261(para) +msgid "Click Add Rule." +msgstr "" + +#: ./doc/training-guides/module001-ch006-overview-horizon-cli.xml224(para) +#: ./doc/training-guides/module001-ch006-overview-horizon-cli.xml264(para) +msgid "The Add Rulewindow appears." +msgstr "" + +#: ./doc/training-guides/module001-ch006-overview-horizon-cli.xml229(para) +msgid "In the IP Protocollist, select TCP." +msgstr "" + +#: ./doc/training-guides/module001-ch006-overview-horizon-cli.xml232(para) +msgid "In the Openlist, select Port." +msgstr "" + +#: ./doc/training-guides/module001-ch006-overview-horizon-cli.xml235(para) +msgid "In the Portbox, enter 22." +msgstr "" + +#: ./doc/training-guides/module001-ch006-overview-horizon-cli.xml238(para) +#: ./doc/training-guides/module001-ch006-overview-horizon-cli.xml278(para) +msgid "In the Sourcelist, select CIDR." +msgstr "" + +#: ./doc/training-guides/module001-ch006-overview-horizon-cli.xml241(para) +#: ./doc/training-guides/module001-ch006-overview-horizon-cli.xml281(para) +msgid "In the CIDRbox, enter 0.0.0.0/0." +msgstr "" + +#: ./doc/training-guides/module001-ch006-overview-horizon-cli.xml244(para) +#: ./doc/training-guides/module001-ch006-overview-horizon-cli.xml284(para) +msgid "Click Add." +msgstr "" + +#: ./doc/training-guides/module001-ch006-overview-horizon-cli.xml247(para) +msgid "Port 22 is now open for requests from any IP address." +msgstr "" + +#: ./doc/training-guides/module001-ch006-overview-horizon-cli.xml251(para) +msgid "" +"If you want to accept requests from a particular range of IP addresses, " +"specify the IP address block in the CIDRbox." +msgstr "" + +#: ./doc/training-guides/module001-ch006-overview-horizon-cli.xml258(para) +msgid "Add an ICMP rule" +msgstr "" + +#: ./doc/training-guides/module001-ch006-overview-horizon-cli.xml269(para) +msgid "In the IP Protocollist, select ICMP." +msgstr "" + +#: ./doc/training-guides/module001-ch006-overview-horizon-cli.xml272(para) +msgid "In the Typebox, enter -1." +msgstr "" + +#: ./doc/training-guides/module001-ch006-overview-horizon-cli.xml275(para) +msgid "In the Codebox, enter -1." +msgstr "" + +#: ./doc/training-guides/module001-ch006-overview-horizon-cli.xml287(guilabel) +msgid "Add keypairs" +msgstr "" + +#: ./doc/training-guides/module001-ch006-overview-horizon-cli.xml288(para) +msgid "" +"Create at least one keypair for each project. If you have generated a " +"keypair with an external tool, you can import it into OpenStack. The keypair" +" can be used for multiple instances that belong to a project." +msgstr "" + +#: ./doc/training-guides/module001-ch006-overview-horizon-cli.xml292(para) +#: ./doc/training-guides/module001-ch006-overview-horizon-cli.xml310(para) +msgid "To add a keypair" +msgstr "" + +#: ./doc/training-guides/module001-ch006-overview-horizon-cli.xml306(para) +msgid "" +"Click the Keypairstab. The dashboard shows the keypairs that are available " +"for this project." +msgstr "" + +#: ./doc/training-guides/module001-ch006-overview-horizon-cli.xml313(para) +#: ./doc/training-guides/module001-ch006-overview-horizon-cli.xml325(para) +msgid "Click Create Keypair." +msgstr "" + +#: ./doc/training-guides/module001-ch006-overview-horizon-cli.xml316(para) +msgid "The Create Keypairwindow appears." +msgstr "" + +#: ./doc/training-guides/module001-ch006-overview-horizon-cli.xml321(para) +msgid "In the Keypair Namebox, enter a name for your keypair." +msgstr "" + +#: ./doc/training-guides/module001-ch006-overview-horizon-cli.xml328(para) +msgid "Respond to the prompt to download the keypair." +msgstr "" + +#: ./doc/training-guides/module001-ch006-overview-horizon-cli.xml333(para) +msgid "To import a keypair" +msgstr "" + +#: ./doc/training-guides/module001-ch006-overview-horizon-cli.xml336(para) +#: ./doc/training-guides/module001-ch006-overview-horizon-cli.xml351(para) +msgid "Click Import Keypair." +msgstr "" + +#: ./doc/training-guides/module001-ch006-overview-horizon-cli.xml339(para) +msgid "The Import Keypairwindow appears." +msgstr "" + +#: ./doc/training-guides/module001-ch006-overview-horizon-cli.xml344(para) +msgid "In the Keypair Namebox, enter the name of your keypair." +msgstr "" + +#: ./doc/training-guides/module001-ch006-overview-horizon-cli.xml348(para) +msgid "In the Public Keybox, copy the public key." +msgstr "" + +#: ./doc/training-guides/module001-ch006-overview-horizon-cli.xml356(para) +msgid "" +"Save the *.pem file locally and change its permissions so that only you can " +"read and write to the file:" +msgstr "" + +#: ./doc/training-guides/module001-ch006-overview-horizon-cli.xml360(para) +msgid "$ chmod 0600 MY_PRIV_KEY.pem" +msgstr "" + +#: ./doc/training-guides/module001-ch006-overview-horizon-cli.xml363(para) +msgid "Use the ssh-addcommand to make the keypair known to SSH:" +msgstr "" + +#: ./doc/training-guides/module001-ch006-overview-horizon-cli.xml367(para) +msgid "$ ssh-add MY_PRIV_KEY.pem" +msgstr "" + +#: ./doc/training-guides/module001-ch006-overview-horizon-cli.xml370(para) +msgid "The public key of the keypair is registered in the Nova database." +msgstr "" + +#: ./doc/training-guides/module001-ch006-overview-horizon-cli.xml372(para) +msgid "The dashboard lists the keypair in the Access & Securitycategory." +msgstr "" + +#: ./doc/training-guides/module001-ch006-overview-horizon-cli.xml374(guilabel) +#: ./doc/training-guides/module001-ch006-overview-horizon-cli.xml1534(guilabel) +msgid "Launch instances" +msgstr "" + +#: ./doc/training-guides/module001-ch006-overview-horizon-cli.xml375(para) +msgid "" +"Instances are virtual machines that run inside the cloud. You can launch an " +"instance directly from one of the available OpenStack images or from an " +"image that you have copied to a persistent volume. The OpenStack Image " +"Service provides a pool of images that are accessible to members of " +"different projects." +msgstr "" + +#: ./doc/training-guides/module001-ch006-overview-horizon-cli.xml381(guilabel) +#: ./doc/training-guides/module001-ch006-overview-horizon-cli.xml1685(guilabel) +msgid "Launch an instance from an image" +msgstr "" + +#: ./doc/training-guides/module001-ch006-overview-horizon-cli.xml382(para) +msgid "" +"When you launch an instance from an image, OpenStack creates a local copy of" +" the image on the respective compute node where the instance is started." +msgstr "" + +#: ./doc/training-guides/module001-ch006-overview-horizon-cli.xml385(para) +#: ./doc/training-guides/module001-ch006-overview-horizon-cli.xml1688(para) +msgid "To launch an instance from an image" +msgstr "" + +#: ./doc/training-guides/module001-ch006-overview-horizon-cli.xml396(para) +msgid "Click the Images & Snapshotcategory." +msgstr "" + +#: ./doc/training-guides/module001-ch006-overview-horizon-cli.xml399(para) +msgid "" +"The dashboard shows the images that have been uploaded to OpenStack Image " +"Service and are available for this project." +msgstr "" + +#: ./doc/training-guides/module001-ch006-overview-horizon-cli.xml404(para) +msgid "Select an image and click Launch." +msgstr "" + +#: ./doc/training-guides/module001-ch006-overview-horizon-cli.xml407(para) +msgid "In the Launch Imagewindow, specify the following:" +msgstr "" + +#: ./doc/training-guides/module001-ch006-overview-horizon-cli.xml413(para) +msgid "Enter an instance name to assign to the virtual machine." +msgstr "" + +#: ./doc/training-guides/module001-ch006-overview-horizon-cli.xml417(para) +msgid "" +"From the Flavordrop-down list, select the size of the virtual machine to " +"launch." +msgstr "" + +#: ./doc/training-guides/module001-ch006-overview-horizon-cli.xml421(para) +msgid "Select a keypair." +msgstr "" + +#: ./doc/training-guides/module001-ch006-overview-horizon-cli.xml424(para) +msgid "" +"In case an image uses a static root password or a static key set (neither is" +" recommended), you do not need to provide a keypair to launch the instance." +msgstr "" + +#: ./doc/training-guides/module001-ch006-overview-horizon-cli.xml429(para) +msgid "" +"In Instance Count, enter the number of virtual machines to launch from this " +"image." +msgstr "" + +#: ./doc/training-guides/module001-ch006-overview-horizon-cli.xml433(para) +msgid "Activate the security groups that you want to assign to the instance." +msgstr "" + +#: ./doc/training-guides/module001-ch006-overview-horizon-cli.xml437(para) +msgid "" +"Security groups are a kind of cloud firewall that define which incoming " +"network traffic should be forwarded to instances. For details, seethe section called “Add " +"security group rules”." +msgstr "" + +#: ./doc/training-guides/module001-ch006-overview-horizon-cli.xml445(para) +msgid "" +"If you have not created any specific security groups, you can only assign " +"the instance to the default security group." +msgstr "" + +#: ./doc/training-guides/module001-ch006-overview-horizon-cli.xml450(para) +msgid "" +"If you want to boot from volume, click the respective entry to expand its " +"options. Set the options as described inthe" +" section called “Launch an instance from a volume”." +msgstr "" + +#: ./doc/training-guides/module001-ch006-overview-horizon-cli.xml462(para) +msgid "" +"Click Launch Instance. The instance is started on any of the compute nodes " +"in the cloud." +msgstr "" + +#: ./doc/training-guides/module001-ch006-overview-horizon-cli.xml466(para) +msgid "" +"After you have launched an instance, switch to the Instancescategory to view" +" the instance name, its (private or public) IP address, size, status, task, " +"and power state." +msgstr "" + +#: ./doc/training-guides/module001-ch006-overview-horizon-cli.xml470(para) +msgid "Figure 5. OpenStack dashboard – Instances" +msgstr "" + +#: ./doc/training-guides/module001-ch006-overview-horizon-cli.xml471(para) +msgid "" +"If you did not provide a keypair, security groups, or rules so far, by " +"default the instance can only be accessed from inside the cloud through VNC " +"at this point. Even pinging the instance is not possible. To access the " +"instance through a VNC console, seethe section called “Get a console to " +"an instance”." +msgstr "" + +#: ./doc/training-guides/module001-ch006-overview-horizon-cli.xml481(guilabel) +#: ./doc/training-guides/module001-ch006-overview-horizon-cli.xml1763(guilabel) +msgid "Launch an instance from a volume" +msgstr "" + +#: ./doc/training-guides/module001-ch006-overview-horizon-cli.xml482(para) +msgid "" +"You can launch an instance directly from an image that has been copied to a " +"persistent volume." +msgstr "" + +#: ./doc/training-guides/module001-ch006-overview-horizon-cli.xml484(para) +msgid "" +"In that case, the instance is booted from the volume, which is provided by " +"nova-volume, through iSCSI." +msgstr "" + +#: ./doc/training-guides/module001-ch006-overview-horizon-cli.xml486(para) +msgid "" +"For preparation details, seethe " +"section called “Create or delete a volume”." +msgstr "" + +#: ./doc/training-guides/module001-ch006-overview-horizon-cli.xml492(para) +msgid "" +"To boot an instance from the volume, especially note the following steps:" +msgstr "" + +#: ./doc/training-guides/module001-ch006-overview-horizon-cli.xml496(para) +msgid "" +"To be able to select from which volume to boot, launch an instance from an " +"arbitrary image. The image you select does not boot. It is replaced by the " +"image on the volume that you choose in the next steps." +msgstr "" + +#: ./doc/training-guides/module001-ch006-overview-horizon-cli.xml502(para) +msgid "" +"In case you want to boot a Xen image from a volume, note the following " +"requirement: The image you launch in must be the same type, fully " +"virtualized or paravirtualized, as the one on the volume." +msgstr "" + +#: ./doc/training-guides/module001-ch006-overview-horizon-cli.xml508(para) +msgid "Select the volume or volume snapshot to boot from." +msgstr "" + +#: ./doc/training-guides/module001-ch006-overview-horizon-cli.xml512(para) +msgid "Enter a device name. Enter vda for KVM images or xvda for Xen images." +msgstr "" + +#: ./doc/training-guides/module001-ch006-overview-horizon-cli.xml517(para) +#: ./doc/training-guides/module001-ch006-overview-horizon-cli.xml1769(para) +msgid "To launch an instance from a volume" +msgstr "" + +#: ./doc/training-guides/module001-ch006-overview-horizon-cli.xml518(para) +msgid "" +"You can launch an instance directly from one of the images available through" +" the OpenStack Image Service or from an image that you have copied to a " +"persistent volume. When you launch an instance from a volume, the procedure " +"is basically the same as when launching an instance from an image in " +"OpenStack Image Service, except for some additional steps." +msgstr "" + +#: ./doc/training-guides/module001-ch006-overview-horizon-cli.xml526(para) +msgid "" +"Create a volume as described inthe " +"section called “Create or delete a volume”." +msgstr "" + +#: ./doc/training-guides/module001-ch006-overview-horizon-cli.xml534(para) +msgid "It must be large enough to store an unzipped image." +msgstr "" + +#: ./doc/training-guides/module001-ch006-overview-horizon-cli.xml538(para) +msgid "Create an image." +msgstr "" + +#: ./doc/training-guides/module001-ch006-overview-horizon-cli.xml541(para) +msgid "" +"For details, see Creating images " +"manually in the OpenStack Virtual Machine Image " +"Guide." +msgstr "" + +#: ./doc/training-guides/module001-ch006-overview-horizon-cli.xml548(para) +msgid "Launch an instance." +msgstr "" + +#: ./doc/training-guides/module001-ch006-overview-horizon-cli.xml551(para) +msgid "" +"Attach the volume to the instance as described inthe" +" section called “Attach volumes to instances”." +msgstr "" + +#: ./doc/training-guides/module001-ch006-overview-horizon-cli.xml559(para) +msgid "" +"Assuming that the attached volume is mounted as /dev/vdb, use one of the " +"following commands to copy the image to the attached volume:" +msgstr "" + +#: ./doc/training-guides/module001-ch006-overview-horizon-cli.xml566(para) +msgid "For a raw image:" +msgstr "" + +#: ./doc/training-guides/module001-ch006-overview-horizon-cli.xml569(para) +msgid "$ cat IMAGE >/dev/null" +msgstr "" + +#: ./doc/training-guides/module001-ch006-overview-horizon-cli.xml572(para) +msgid "Alternatively, use dd." +msgstr "" + +#: ./doc/training-guides/module001-ch006-overview-horizon-cli.xml575(para) +msgid "For a non-raw image:" +msgstr "" + +#: ./doc/training-guides/module001-ch006-overview-horizon-cli.xml578(para) +msgid "$ qemu-img convert -O raw IMAGE /dev/vdb" +msgstr "" + +#: ./doc/training-guides/module001-ch006-overview-horizon-cli.xml581(para) +msgid "For a *.tar.bz2 image:" +msgstr "" + +#: ./doc/training-guides/module001-ch006-overview-horizon-cli.xml584(para) +msgid "$ tar xfjO IMAGE >/dev/null" +msgstr "" + +#: ./doc/training-guides/module001-ch006-overview-horizon-cli.xml589(para) +msgid "Only detached volumes are available for booting. Detach the volume." +msgstr "" + +#: ./doc/training-guides/module001-ch006-overview-horizon-cli.xml593(para) +msgid "" +"To launch an instance from the volume, continue withthe" +" section called “Launch an instance from an image”." +msgstr "" + +#: ./doc/training-guides/module001-ch006-overview-horizon-cli.xml602(para) +msgid "" +"You can launch an instance directly from one of the images available through" +" the OpenStack Image Service. When you do that, OpenStack creates a local " +"copy of the image on the respective compute node where the instance is " +"started." +msgstr "" + +#: ./doc/training-guides/module001-ch006-overview-horizon-cli.xml609(para) +msgid "SSH in to your instance" +msgstr "" + +#: ./doc/training-guides/module001-ch006-overview-horizon-cli.xml612(para) +msgid "To SSH into your instance, you use the downloaded keypair file." +msgstr "" + +#: ./doc/training-guides/module001-ch006-overview-horizon-cli.xml614(para) +msgid "To SSH into your instance" +msgstr "" + +#: ./doc/training-guides/module001-ch006-overview-horizon-cli.xml617(para) +msgid "Copy the IP address for your instance." +msgstr "" + +#: ./doc/training-guides/module001-ch006-overview-horizon-cli.xml620(para) +msgid "" +"Use the SSH command to make a secure connection to the instance. For " +"example:" +msgstr "" + +#: ./doc/training-guides/module001-ch006-overview-horizon-cli.xml624(para) +msgid "$ ssh -i MyKey.pem ubuntu@10.0.0.2" +msgstr "" + +#: ./doc/training-guides/module001-ch006-overview-horizon-cli.xml627(para) +msgid "" +"A prompt asks, \"Are you sure you want to continue connection (yes/no)?\" " +"Type yes and you have successfully connected." +msgstr "" + +#: ./doc/training-guides/module001-ch006-overview-horizon-cli.xml632(guilabel) +msgid "Manage instances" +msgstr "" + +#: ./doc/training-guides/module001-ch006-overview-horizon-cli.xml633(guilabel) +msgid "Create instance snapshots" +msgstr "" + +#: ./doc/training-guides/module001-ch006-overview-horizon-cli.xml635(title) +msgid "OpenStack Dashboard- Instances" +msgstr "" + +#: ./doc/training-guides/module001-ch006-overview-horizon-cli.xml642(para) +msgid "To create instance snapshots" +msgstr "" + +#: ./doc/training-guides/module001-ch006-overview-horizon-cli.xml653(para) +#: ./doc/training-guides/module001-ch006-overview-horizon-cli.xml692(para) +msgid "Click the Instancescategory." +msgstr "" + +#: ./doc/training-guides/module001-ch006-overview-horizon-cli.xml656(para) +#: ./doc/training-guides/module001-ch006-overview-horizon-cli.xml695(para) +msgid "The dashboard lists the instances that are available for this project." +msgstr "" + +#: ./doc/training-guides/module001-ch006-overview-horizon-cli.xml660(para) +msgid "" +"Select the instance of which to create a snapshot. From the Actionsdrop-down" +" list, select Create Snapshot." +msgstr "" + +#: ./doc/training-guides/module001-ch006-overview-horizon-cli.xml665(para) +msgid "" +"In the Create Snapshotwindow, enter a name for the snapshot. Click Create " +"Snapshot. The dashboard shows the instance snapshot in the Images & " +"Snapshotscategory." +msgstr "" + +#: ./doc/training-guides/module001-ch006-overview-horizon-cli.xml671(para) +msgid "" +"To launch an instance from the snapshot, select the snapshot and click " +"Launch. Proceed withthe" +" section called “Launch an instance from an image”." +msgstr "" + +#: ./doc/training-guides/module001-ch006-overview-horizon-cli.xml680(guilabel) +msgid "Control the state of an instance" +msgstr "" + +#: ./doc/training-guides/module001-ch006-overview-horizon-cli.xml681(para) +msgid "To control the state of an instance" +msgstr "" + +#: ./doc/training-guides/module001-ch006-overview-horizon-cli.xml699(para) +msgid "Select the instance for which you want to change the state." +msgstr "" + +#: ./doc/training-guides/module001-ch006-overview-horizon-cli.xml703(para) +msgid "In the Moredrop-down list in the Actionscolumn, select the state." +msgstr "" + +#: ./doc/training-guides/module001-ch006-overview-horizon-cli.xml707(para) +msgid "" +"Depending on the current state of the instance, you can choose to pause, un-" +"pause, suspend, resume, soft or hard reboot, or terminate an instance." +msgstr "" + +#: ./doc/training-guides/module001-ch006-overview-horizon-cli.xml713(title) +msgid "OpenStack Dashboard : Actions" +msgstr "" + +#: ./doc/training-guides/module001-ch006-overview-horizon-cli.xml720(guilabel) +msgid "Track usage" +msgstr "" + +#: ./doc/training-guides/module001-ch006-overview-horizon-cli.xml721(para) +msgid "" +"Use the dashboard's Overviewcategory to track usage of instances for each " +"project." +msgstr "" + +#: ./doc/training-guides/module001-ch006-overview-horizon-cli.xml724(title) +msgid "OpenStack Dashboard - Track Usage" +msgstr "" + +#: ./doc/training-guides/module001-ch006-overview-horizon-cli.xml731(para) +msgid "" +"You can track costs per month by showing metrics like number of VCPUs, " +"disks, RAM, and uptime of all your instances." +msgstr "" + +#: ./doc/training-guides/module001-ch006-overview-horizon-cli.xml734(para) +msgid "To track usage" +msgstr "" + +#: ./doc/training-guides/module001-ch006-overview-horizon-cli.xml742(para) +msgid "" +"Select a month and click Submitto query the instance usage for that month." +msgstr "" + +#: ./doc/training-guides/module001-ch006-overview-horizon-cli.xml746(para) +msgid "Click Download CSV Summaryto download a CVS summary." +msgstr "" + +#: ./doc/training-guides/module001-ch006-overview-horizon-cli.xml750(guilabel) +msgid "Manage volumes" +msgstr "" + +#: ./doc/training-guides/module001-ch006-overview-horizon-cli.xml751(para) +msgid "" +"Volumes are block storage devices that you can attach to instances. They " +"allow for persistent storage as they can be attached to a running instance, " +"or detached and attached to another instance at any time." +msgstr "" + +#: ./doc/training-guides/module001-ch006-overview-horizon-cli.xml755(para) +msgid "" +"In contrast to the instance's root disk, the data of volumes is not " +"destroyed when the instance is deleted." +msgstr "" + +#: ./doc/training-guides/module001-ch006-overview-horizon-cli.xml757(guilabel) +msgid "Create or delete a volume" +msgstr "" + +#: ./doc/training-guides/module001-ch006-overview-horizon-cli.xml758(para) +msgid "To create or delete a volume" +msgstr "" + +#: ./doc/training-guides/module001-ch006-overview-horizon-cli.xml764(para) +#: ./doc/training-guides/module001-ch006-overview-horizon-cli.xml824(para) +msgid "" +"If you are a member of multiple projects, select a Projectfrom the drop-down" +" list at the top of the tab." +msgstr "" + +#: ./doc/training-guides/module001-ch006-overview-horizon-cli.xml769(para) +#: ./doc/training-guides/module001-ch006-overview-horizon-cli.xml829(para) +msgid "Click the Volumescategory." +msgstr "" + +#: ./doc/training-guides/module001-ch006-overview-horizon-cli.xml772(para) +msgid "To create a volume" +msgstr "" + +#: ./doc/training-guides/module001-ch006-overview-horizon-cli.xml777(para) +msgid "Click Create Volume." +msgstr "" + +#: ./doc/training-guides/module001-ch006-overview-horizon-cli.xml780(para) +msgid "" +"In the window that opens, enter a name to assign to a volume, a description " +"(optional), and define the size in GBs." +msgstr "" + +#: ./doc/training-guides/module001-ch006-overview-horizon-cli.xml785(para) +msgid "Confirm your changes." +msgstr "" + +#: ./doc/training-guides/module001-ch006-overview-horizon-cli.xml788(para) +msgid "The dashboard shows the volume in the Volumescategory." +msgstr "" + +#: ./doc/training-guides/module001-ch006-overview-horizon-cli.xml794(para) +msgid "To delete one or multiple volumes" +msgstr "" + +#: ./doc/training-guides/module001-ch006-overview-horizon-cli.xml799(para) +msgid "" +"Activate the checkboxes in front of the volumes that you want to delete." +msgstr "" + +#: ./doc/training-guides/module001-ch006-overview-horizon-cli.xml803(para) +msgid "" +"Click Delete Volumesand confirm your choice in the pop-up that appears." +msgstr "" + +#: ./doc/training-guides/module001-ch006-overview-horizon-cli.xml807(para) +#: ./doc/training-guides/module001-ch006-overview-horizon-cli.xml864(para) +msgid "A message indicates whether the action was successful." +msgstr "" + +#: ./doc/training-guides/module001-ch006-overview-horizon-cli.xml811(para) +msgid "" +"After you create one or more volumes, you can attach them to instances." +msgstr "" + +#: ./doc/training-guides/module001-ch006-overview-horizon-cli.xml813(para) +msgid "You can attach a volume to one instance at a time." +msgstr "" + +#: ./doc/training-guides/module001-ch006-overview-horizon-cli.xml814(para) +msgid "" +"View the status of a volume in the Instances & Volumescategory of the " +"dashboard: the volume is either available or In-Use." +msgstr "" + +#: ./doc/training-guides/module001-ch006-overview-horizon-cli.xml817(guilabel) +msgid "Attach volumes to instances" +msgstr "" + +#: ./doc/training-guides/module001-ch006-overview-horizon-cli.xml818(para) +msgid "To attach volumes to instances" +msgstr "" + +#: ./doc/training-guides/module001-ch006-overview-horizon-cli.xml821(para) +msgid "Log in to OpenStack dashboard." +msgstr "" + +#: ./doc/training-guides/module001-ch006-overview-horizon-cli.xml832(para) +msgid "Select the volume to add to an instance and click Edit Attachments." +msgstr "" + +#: ./doc/training-guides/module001-ch006-overview-horizon-cli.xml836(para) +msgid "In the Manage Volume Attachmentswindow, select an instance." +msgstr "" + +#: ./doc/training-guides/module001-ch006-overview-horizon-cli.xml840(para) +msgid "" +"Enter a device name under which the volume should be accessible on the " +"virtual machine." +msgstr "" + +#: ./doc/training-guides/module001-ch006-overview-horizon-cli.xml844(para) +msgid "" +"Click Attach Volumeto confirm your changes. The dashboard shows the instance" +" to which the volume has been attached and the volume's device name." +msgstr "" + +#: ./doc/training-guides/module001-ch006-overview-horizon-cli.xml849(para) +msgid "" +"Now you can log in to the instance, mount the disk, format it, and use it." +msgstr "" + +#: ./doc/training-guides/module001-ch006-overview-horizon-cli.xml853(para) +msgid "To detach a volume from an instance" +msgstr "" + +#: ./doc/training-guides/module001-ch006-overview-horizon-cli.xml858(para) +msgid "Select the volume and click Edit Attachments." +msgstr "" + +#: ./doc/training-guides/module001-ch006-overview-horizon-cli.xml861(para) +msgid "Click Detach Volumeand confirm your changes." +msgstr "" + +#: ./doc/training-guides/module001-ch006-overview-horizon-cli.xml868(guilabel) +msgid "OpenStack command-line clients" +msgstr "" + +#: ./doc/training-guides/module001-ch006-overview-horizon-cli.xml870(para) +msgid "" +"You can use the OpenStack command-line clients to run simple commands that " +"make API calls and automate tasks by using scripts. Internally, each client " +"command runs cURL commands that embed API requests. The OpenStack APIs are " +"RESTful APIs that use the HTTP protocol, including methods, URIs, media " +"types, and response codes." +msgstr "" + +#: ./doc/training-guides/module001-ch006-overview-horizon-cli.xml876(para) +msgid "" +"These open-source Python clients run on Linux or Mac OS X systems and are " +"easy to learn and use. Each OpenStack service has its own command-line " +"client. On some client commands, you can specify a debugparameter to show " +"the underlying API request for the command. This is a good way to become " +"familiar with the OpenStack API calls." +msgstr "" + +#: ./doc/training-guides/module001-ch006-overview-horizon-cli.xml882(para) +msgid "" +"The following command-line clients are available for the respective " +"services' APIs:" +msgstr "" + +#: ./doc/training-guides/module001-ch006-overview-horizon-cli.xml884(para) +msgid "cinder(python-cinderclient)" +msgstr "" + +#: ./doc/training-guides/module001-ch006-overview-horizon-cli.xml885(para) +msgid "" +"Client for the Block Storage Service API. Use to create and manage volumes." +msgstr "" + +#: ./doc/training-guides/module001-ch006-overview-horizon-cli.xml887(para) +msgid "glance(python-glanceclient)" +msgstr "" + +#: ./doc/training-guides/module001-ch006-overview-horizon-cli.xml888(para) +msgid "Client for the Image Service API. Use to create and manage images." +msgstr "" + +#: ./doc/training-guides/module001-ch006-overview-horizon-cli.xml890(para) +msgid "keystone(python-keystoneclient)" +msgstr "" + +#: ./doc/training-guides/module001-ch006-overview-horizon-cli.xml891(para) +msgid "" +"Client for the Identity Service API. Use to create and manage users, " +"tenants, roles, endpoints, and credentials." +msgstr "" + +#: ./doc/training-guides/module001-ch006-overview-horizon-cli.xml894(para) +msgid "nova(python-novaclient)" +msgstr "" + +#: ./doc/training-guides/module001-ch006-overview-horizon-cli.xml895(para) +msgid "" +"Client for the Compute API and its extensions. Use to create and manage " +"images, instances, and flavors." +msgstr "" + +#: ./doc/training-guides/module001-ch006-overview-horizon-cli.xml897(para) +msgid "neutron(python-neutronclient)" +msgstr "" + +#: ./doc/training-guides/module001-ch006-overview-horizon-cli.xml898(para) +msgid "" +"Client for the Networking API. Use to configure networks for guest servers. " +"This client was previously known as neutron." +msgstr "" + +#: ./doc/training-guides/module001-ch006-overview-horizon-cli.xml901(para) +msgid "swift(python-swiftclient)" +msgstr "" + +#: ./doc/training-guides/module001-ch006-overview-horizon-cli.xml902(para) +msgid "" +"Client for the Object Storage API. Use to gather statistics, list items, " +"update metadata, upload, download and delete files stored by the object " +"storage service. Provides access to a swift installation for ad hoc " +"processing." +msgstr "" + +#: ./doc/training-guides/module001-ch006-overview-horizon-cli.xml906(para) +msgid "heat(python-heatclient)" +msgstr "" + +#: ./doc/training-guides/module001-ch006-overview-horizon-cli.xml907(para) +msgid "" +"Client for the Orchestration API. Use to launch stacks from templates, view " +"details of running stacks including events and resources, and update and " +"delete stacks." +msgstr "" + +#: ./doc/training-guides/module001-ch006-overview-horizon-cli.xml910(guilabel) +msgid "Install the OpenStack command-line clients" +msgstr "" + +#: ./doc/training-guides/module001-ch006-overview-horizon-cli.xml911(para) +msgid "" +"To install the clients, install the prerequisite software and the Python " +"package for each OpenStack client." +msgstr "" + +#: ./doc/training-guides/module001-ch006-overview-horizon-cli.xml913(guilabel) +msgid "Install the clients" +msgstr "" + +#: ./doc/training-guides/module001-ch006-overview-horizon-cli.xml914(para) +msgid "" +"Use pipto install the OpenStack clients on a Mac OS X or Linux system. It is" +" easy and ensures that you get the latest version of the client from " +"thePython Package Index. Also, " +"piplets you update or remove a package. After you install the clients, you " +"must source an openrc file to set required environment variables before you " +"can request OpenStack services through the clients or the APIs." +msgstr "" + +#: ./doc/training-guides/module001-ch006-overview-horizon-cli.xml924(para) +msgid "To install the clients" +msgstr "" + +#: ./doc/training-guides/module001-ch006-overview-horizon-cli.xml927(para) +msgid "You must install each client separately." +msgstr "" + +#: ./doc/training-guides/module001-ch006-overview-horizon-cli.xml930(para) +msgid "Run the following command to install or update a client package:" +msgstr "" + +#: ./doc/training-guides/module001-ch006-overview-horizon-cli.xml934(para) +msgid "$ sudo pip install [--update] python-<project>client" +msgstr "" + +#: ./doc/training-guides/module001-ch006-overview-horizon-cli.xml938(para) +msgid "" +"Where <project> is the project name and has one of the following " +"values:" +msgstr "" + +#: ./doc/training-guides/module001-ch006-overview-horizon-cli.xml944(para) +msgid "nova. Compute API and extensions." +msgstr "" + +#: ./doc/training-guides/module001-ch006-overview-horizon-cli.xml947(para) +msgid "neutron. Networking API." +msgstr "" + +#: ./doc/training-guides/module001-ch006-overview-horizon-cli.xml950(para) +msgid "keystone. Identity Service API." +msgstr "" + +#: ./doc/training-guides/module001-ch006-overview-horizon-cli.xml953(para) +msgid "glance. Image Service API." +msgstr "" + +#: ./doc/training-guides/module001-ch006-overview-horizon-cli.xml956(para) +msgid "swift. Object Storage API." +msgstr "" + +#: ./doc/training-guides/module001-ch006-overview-horizon-cli.xml959(para) +msgid "cinder. Block Storage Service API." +msgstr "" + +#: ./doc/training-guides/module001-ch006-overview-horizon-cli.xml962(para) +msgid "heat. Orchestration API." +msgstr "" + +#: ./doc/training-guides/module001-ch006-overview-horizon-cli.xml967(para) +msgid "For example, to install the nova client, run the following command:" +msgstr "" + +#: ./doc/training-guides/module001-ch006-overview-horizon-cli.xml971(para) +msgid "$ sudo pip install python-novaclient" +msgstr "" + +#: ./doc/training-guides/module001-ch006-overview-horizon-cli.xml974(para) +msgid "To update the nova client, run the following command:" +msgstr "" + +#: ./doc/training-guides/module001-ch006-overview-horizon-cli.xml978(para) +msgid "$ sudo pip install --upgrade python-novaclient" +msgstr "" + +#: ./doc/training-guides/module001-ch006-overview-horizon-cli.xml982(para) +msgid "To remove the nova client, run the following command:" +msgstr "" + +#: ./doc/training-guides/module001-ch006-overview-horizon-cli.xml986(para) +msgid "$ sudo pip uninstall python-novaclient" +msgstr "" + +#: ./doc/training-guides/module001-ch006-overview-horizon-cli.xml989(para) +msgid "" +"Before you can issue client commands, you must download and source the " +"openrc file to set environment variables. Proceed tothe " +"section called “OpenStack RC file”." +msgstr "" + +#: ./doc/training-guides/module001-ch006-overview-horizon-cli.xml996(guilabel) +msgid "Get the version for a client" +msgstr "" + +#: ./doc/training-guides/module001-ch006-overview-horizon-cli.xml997(para) +msgid "" +"After you install an OpenStack client, you can search for its version " +"number, as follows:" +msgstr "" + +#: ./doc/training-guides/module001-ch006-overview-horizon-cli.xml999(para) +msgid "$ pip freeze | grep python-" +msgstr "" + +#: ./doc/training-guides/module001-ch006-overview-horizon-cli.xml1000(para) +msgid "" +"python-glanceclient==0.4.0python-keystoneclient==0.1.2-e " +"git+https://github.com/openstack/python-" +"novaclient.git@077cc0bf22e378c4c4b970f2331a695e440a939f#egg" +"=python_novaclient-devpython-neutronclient==0.1.1python-swiftclient==1.1.1" +msgstr "" + +#: ./doc/training-guides/module001-ch006-overview-horizon-cli.xml1002(para) +msgid "" +"You can also use the yolk -lcommand to see which version of the client is " +"installed:" +msgstr "" + +#: ./doc/training-guides/module001-ch006-overview-horizon-cli.xml1004(para) +msgid "$ yolk -l | grep python-novaclient" +msgstr "" + +#: ./doc/training-guides/module001-ch006-overview-horizon-cli.xml1005(para) +msgid "" +"python-novaclient - 2.6.10.27 - active development (/Users/your.name/src" +"/cloud-servers/src/src/python-novaclient)python-novaclient - 2012.1 - non-" +"active" +msgstr "" + +#: ./doc/training-guides/module001-ch006-overview-horizon-cli.xml1008(guilabel) +msgid "OpenStack RC file" +msgstr "" + +#: ./doc/training-guides/module001-ch006-overview-horizon-cli.xml1009(para) +msgid "" +"To set the required environment variables for the OpenStack command-line " +"clients, you must download and source an environment file, openrc.sh. It is " +"project-specific and contains the credentials used by OpenStack Compute, " +"Image, and Identity services." +msgstr "" + +#: ./doc/training-guides/module001-ch006-overview-horizon-cli.xml1014(para) +msgid "" +"When you source the file and enter the password, environment variables are " +"set for that shell. They allow the commands to communicate to the OpenStack " +"services that run in the cloud." +msgstr "" + +#: ./doc/training-guides/module001-ch006-overview-horizon-cli.xml1018(para) +msgid "" +"You can download the file from the OpenStack dashboard as an administrative " +"user or any other user." +msgstr "" + +#: ./doc/training-guides/module001-ch006-overview-horizon-cli.xml1020(para) +msgid "To download the OpenStack RC file" +msgstr "" + +#: ./doc/training-guides/module001-ch006-overview-horizon-cli.xml1026(para) +msgid "" +"On the Projecttab, select the project for which you want to download the " +"OpenStack RC file." +msgstr "" + +#: ./doc/training-guides/module001-ch006-overview-horizon-cli.xml1030(para) +msgid "" +"Click Access & Security. Then, click Download OpenStack RC Fileand save " +"the file." +msgstr "" + +#: ./doc/training-guides/module001-ch006-overview-horizon-cli.xml1034(para) +msgid "" +"Copy the openrc.sh file to the machine from where you want to run OpenStack " +"commands." +msgstr "" + +#: ./doc/training-guides/module001-ch006-overview-horizon-cli.xml1038(para) +msgid "" +"For example, copy the file to the machine from where you want to upload an " +"image with a glance client command." +msgstr "" + +#: ./doc/training-guides/module001-ch006-overview-horizon-cli.xml1042(para) +msgid "" +"On any shell from where you want to run OpenStack commands, source the " +"openrc.sh file for the respective project." +msgstr "" + +#: ./doc/training-guides/module001-ch006-overview-horizon-cli.xml1047(para) +msgid "" +"In this example, we source the demo-openrc.sh file for the demo project:" +msgstr "" + +#: ./doc/training-guides/module001-ch006-overview-horizon-cli.xml1051(para) +msgid "$ source demo-openrc.sh" +msgstr "" + +#: ./doc/training-guides/module001-ch006-overview-horizon-cli.xml1054(para) +msgid "" +"When you are prompted for an OpenStack password, enter the OpenStack " +"password for the user who downloaded the openrc.sh file." +msgstr "" + +#: ./doc/training-guides/module001-ch006-overview-horizon-cli.xml1059(para) +msgid "" +"When you run OpenStack client commands, you can override some environment " +"variable settings by using the options that are listed at the end of the " +"nova helpoutput. For example, you can override the OS_PASSWORD setting in " +"the openrc.sh file by specifying a password on a nova command, as follows:" +msgstr "" + +#: ./doc/training-guides/module001-ch006-overview-horizon-cli.xml1067(para) +msgid "$ nova --password <password> image-list" +msgstr "" + +#: ./doc/training-guides/module001-ch006-overview-horizon-cli.xml1070(para) +msgid "Where password is your password." +msgstr "" + +#: ./doc/training-guides/module001-ch006-overview-horizon-cli.xml1074(para) +msgid "" +"During setup of OpenStack cloud, the cloud operator sets user permissions to" +" manage images." +msgstr "" + +#: ./doc/training-guides/module001-ch006-overview-horizon-cli.xml1076(para) +msgid "" +"Image upload and management might be restricted to only cloud administrators" +" or cloud operators." +msgstr "" + +#: ./doc/training-guides/module001-ch006-overview-horizon-cli.xml1078(para) +msgid "" +"After you upload an image, it is considered golden and you cannot change it." +msgstr "" + +#: ./doc/training-guides/module001-ch006-overview-horizon-cli.xml1080(para) +msgid "" +"You can upload images through the glance client or the Image Service API. " +"You can also use the nova client to list images, set and delete image " +"metadata, delete images, and take a snapshot of a running instance to create" +" an image." +msgstr "" + +#: ./doc/training-guides/module001-ch006-overview-horizon-cli.xml1084(guilabel) +msgid "Manage images with the glance client" +msgstr "" + +#: ./doc/training-guides/module001-ch006-overview-horizon-cli.xml1085(para) +msgid "To list or get details for images" +msgstr "" + +#: ./doc/training-guides/module001-ch006-overview-horizon-cli.xml1088(para) +msgid "To list the available images:" +msgstr "" + +#: ./doc/training-guides/module001-ch006-overview-horizon-cli.xml1091(para) +msgid "$ glance image-list" +msgstr "" + +#: ./doc/training-guides/module001-ch006-overview-horizon-cli.xml1094(para) +msgid "You can use grep to filter the list, as follows:" +msgstr "" + +#: ./doc/training-guides/module001-ch006-overview-horizon-cli.xml1098(para) +msgid "$ glance image-list | grep 'cirros'" +msgstr "" + +#: ./doc/training-guides/module001-ch006-overview-horizon-cli.xml1101(para) +msgid "To get image details, by name or ID:" +msgstr "" + +#: ./doc/training-guides/module001-ch006-overview-horizon-cli.xml1104(para) +msgid "$ glance image-show myCirrosImage" +msgstr "" + +#: ./doc/training-guides/module001-ch006-overview-horizon-cli.xml1107(para) +msgid "To add an image" +msgstr "" + +#: ./doc/training-guides/module001-ch006-overview-horizon-cli.xml1110(para) +msgid "" +"The following example uploads a CentOS 6.3 image in qcow2 format and " +"configures it for public access:" +msgstr "" + +#: ./doc/training-guides/module001-ch006-overview-horizon-cli.xml1114(para) +msgid "" +"$glance image-create --name centos63-image --disk-format=qcow2 --container-" +"format=bare --is-public=True ./centos63.qcow2" +msgstr "" + +#: ./doc/training-guides/module001-ch006-overview-horizon-cli.xml1119(para) +msgid "To create an image" +msgstr "" + +#: ./doc/training-guides/module001-ch006-overview-horizon-cli.xml1122(para) +msgid "Write any buffered data to disk." +msgstr "" + +#: ./doc/training-guides/module001-ch006-overview-horizon-cli.xml1125(para) +msgid "" +"For more information, see theTaking Snapshots in the " +"OpenStack Operations Guide." +msgstr "" + +#: ./doc/training-guides/module001-ch006-overview-horizon-cli.xml1131(para) +msgid "To create the image, list instances to get the server ID:" +msgstr "" + +#: ./doc/training-guides/module001-ch006-overview-horizon-cli.xml1135(para) +#: ./doc/training-guides/module001-ch006-overview-horizon-cli.xml1737(para) +#: ./doc/training-guides/module001-ch006-overview-horizon-cli.xml1893(para) +#: ./doc/training-guides/module001-ch006-overview-horizon-cli.xml2056(para) +#: ./doc/training-guides/module001-ch006-overview-horizon-cli.xml2206(para) +#: ./doc/training-guides/module001-ch006-overview-horizon-cli.xml2223(para) +#: ./doc/training-guides/module001-ch006-overview-horizon-cli.xml2379(para) +msgid "$ nova list" +msgstr "" + +#: ./doc/training-guides/module001-ch006-overview-horizon-cli.xml1138(para) +msgid "" +"In this example, the server is named myCirrosServer. Use this server to " +"create a snapshot, as follows:" +msgstr "" + +#: ./doc/training-guides/module001-ch006-overview-horizon-cli.xml1142(para) +msgid "$ nova image-create myCirrosServer myCirrosImage" +msgstr "" + +#: ./doc/training-guides/module001-ch006-overview-horizon-cli.xml1146(para) +msgid "" +"The command creates a qemu snapshot and automatically uploads the image to " +"your repository. Only the tenant that creates the image has access to it." +msgstr "" + +#: ./doc/training-guides/module001-ch006-overview-horizon-cli.xml1151(para) +msgid "Get details for your image to check its status:" +msgstr "" + +#: ./doc/training-guides/module001-ch006-overview-horizon-cli.xml1154(para) +msgid "$ nova image-show IMAGE" +msgstr "" + +#: ./doc/training-guides/module001-ch006-overview-horizon-cli.xml1157(para) +msgid "" +"The image status changes from SAVING to ACTIVE. Only the tenant who creates " +"the image has access to it." +msgstr "" + +#: ./doc/training-guides/module001-ch006-overview-horizon-cli.xml1161(para) +msgid "To launch an instance from your image" +msgstr "" + +#: ./doc/training-guides/module001-ch006-overview-horizon-cli.xml1164(para) +msgid "" +"To launch an instance from your image, include the image ID and flavor ID, " +"as follows:" +msgstr "" + +#: ./doc/training-guides/module001-ch006-overview-horizon-cli.xml1168(para) +msgid "" +"$ nova boot newServer --image 7e5142af-1253-4634-bcc6-89482c5f2e8a --flavor " +"3" +msgstr "" + +#: ./doc/training-guides/module001-ch006-overview-horizon-cli.xml1172(guilabel) +msgid "Troubleshoot image creation" +msgstr "" + +#: ./doc/training-guides/module001-ch006-overview-horizon-cli.xml1175(para) +msgid "" +"You cannot create a snapshot from an instance that has an attached volume. " +"Detach the volume, create the image, and re-mount the volume." +msgstr "" + +#: ./doc/training-guides/module001-ch006-overview-horizon-cli.xml1180(para) +msgid "" +"Make sure the version of qemu you are using is version 0.14 or greater. " +"Older versions of qemu result in an \"unknown option -s\" error message in " +"the nova-compute.log." +msgstr "" + +#: ./doc/training-guides/module001-ch006-overview-horizon-cli.xml1186(para) +msgid "" +"Examine the /var/log/nova-api.log and /var/log/nova-compute.log log files " +"for error messages." +msgstr "" + +#: ./doc/training-guides/module001-ch006-overview-horizon-cli.xml1191(guilabel) +#: ./doc/training-guides/module001-ch006-overview-horizon-cli.xml1245(guilabel) +msgid "Set up access and security for instances" +msgstr "" + +#: ./doc/training-guides/module001-ch006-overview-horizon-cli.xml1192(para) +msgid "" +"When you launch a virtual machine, you can inject a key pair, which provides" +" SSH access to your instance. For this to work, the image must contain the " +"cloud-init package. Create at least one key pair for each project. If you " +"generate a keypair with an external tool, you can import it into OpenStack. " +"You can use the keypair for multiple instances that belong to that project. " +"In case an image uses a static root password or a static key set – neither " +"is recommended – you must not provide a keypair when you launch the " +"instance." +msgstr "" + +#: ./doc/training-guides/module001-ch006-overview-horizon-cli.xml1201(para) +#: ./doc/training-guides/module001-ch006-overview-horizon-cli.xml1255(para) +msgid "" +"A security group is a named collection of network access rules that you use " +"to limit the types of traffic that have access to instances. When you launch" +" an instance, you can assign one or more security groups to it. If you do " +"not create security groups, new instances are automatically assigned to the " +"default security group, unless you explicitly specify a different security " +"group. The associated rules in each security group control the traffic to " +"instances in the group. Any incoming traffic that is not matched by a rule " +"is denied access by default. You can add rules to or remove rules from a " +"security group. You can modify rules for the default and any other security " +"group." +msgstr "" + +#: ./doc/training-guides/module001-ch006-overview-horizon-cli.xml1213(para) +#: ./doc/training-guides/module001-ch006-overview-horizon-cli.xml1267(para) +msgid "" +"You must modify the rules for the default security group because users " +"cannot access instances that use the default group from any IP address " +"outside the cloud." +msgstr "" + +#: ./doc/training-guides/module001-ch006-overview-horizon-cli.xml1216(para) +#: ./doc/training-guides/module001-ch006-overview-horizon-cli.xml1270(para) +msgid "" +"You can modify the rules in a security group to allow access to instances " +"through different ports and protocols. For example, you can modify rules to " +"allow access to instances through SSH, to ping them, or to allow UDP traffic" +" – for example, for a DNS server running on an instance. You specify the " +"following parameters for rules:" +msgstr "" + +#: ./doc/training-guides/module001-ch006-overview-horizon-cli.xml1224(para) +#: ./doc/training-guides/module001-ch006-overview-horizon-cli.xml1278(para) +msgid "" +"Source of traffic. Enable traffic to instances from either IP addresses " +"inside the cloud from other group members or from all IP addresses." +msgstr "" + +#: ./doc/training-guides/module001-ch006-overview-horizon-cli.xml1229(para) +#: ./doc/training-guides/module001-ch006-overview-horizon-cli.xml1283(para) +msgid "Protocol. Choose TCP for SSH, ICMP for pings, or UDP." +msgstr "" + +#: ./doc/training-guides/module001-ch006-overview-horizon-cli.xml1233(para) +#: ./doc/training-guides/module001-ch006-overview-horizon-cli.xml1287(para) +msgid "" +"Destination port on virtual machine. Defines a port range. To open a single " +"port only, enter the same value twice. ICMP does not support ports: Enter " +"values to define the codes and types of ICMP traffic to be allowed." +msgstr "" + +#: ./doc/training-guides/module001-ch006-overview-horizon-cli.xml1239(para) +#: ./doc/training-guides/module001-ch006-overview-horizon-cli.xml1293(para) +msgid "Rules are automatically enforced as soon as you create or modify them." +msgstr "" + +#: ./doc/training-guides/module001-ch006-overview-horizon-cli.xml1241(para) +#: ./doc/training-guides/module001-ch006-overview-horizon-cli.xml1295(para) +msgid "" +"You can also assign a floating IP address to a running instance to make it " +"accessible from outside the cloud. You assign a floating IP address to an " +"instance and attach a block storage device, or volume, for persistent " +"storage." +msgstr "" + +#: ./doc/training-guides/module001-ch006-overview-horizon-cli.xml1246(para) +msgid "" +"When you launch a virtual machine, you can inject a key pair, which provides" +" SSH access to your instance. For this to work, the image must contain the " +"cloud-init package. Create at least one key pair for each project. If you " +"generate a keypair with an external tool, you can import it into OpenStack. " +"You can use the key pair for multiple instances that belong to that project." +" In case an image uses a static root password or a static key set – neither " +"is recommended – you must not provide a key pair when you launch the " +"instance." +msgstr "" + +#: ./doc/training-guides/module001-ch006-overview-horizon-cli.xml1299(guilabel) +msgid "Add or import keypairs" +msgstr "" + +#: ./doc/training-guides/module001-ch006-overview-horizon-cli.xml1300(para) +msgid "To add a key" +msgstr "" + +#: ./doc/training-guides/module001-ch006-overview-horizon-cli.xml1301(para) +msgid "You can generate a keypair or upload an existing public key." +msgstr "" + +#: ./doc/training-guides/module001-ch006-overview-horizon-cli.xml1305(para) +msgid "To generate a keypair, run the following command:" +msgstr "" + +#: ./doc/training-guides/module001-ch006-overview-horizon-cli.xml1309(para) +msgid "$ nova keypair-add KEY_NAME > MY_KEY.pem" +msgstr "" + +#: ./doc/training-guides/module001-ch006-overview-horizon-cli.xml1312(para) +msgid "" +"The command generates a keypair named KEY_NAME, writes the private key to " +"the MY_KEY.pem file, and registers the public key at the Nova database." +msgstr "" + +#: ./doc/training-guides/module001-ch006-overview-horizon-cli.xml1317(para) +msgid "" +"To set the permissions of the MY_KEY.pem file, run the following command:" +msgstr "" + +#: ./doc/training-guides/module001-ch006-overview-horizon-cli.xml1321(para) +msgid "$ chmod 600 MY_KEY.pem" +msgstr "" + +#: ./doc/training-guides/module001-ch006-overview-horizon-cli.xml1324(para) +msgid "" +"The command changes the permissions of the MY_KEY.pem file so that only you " +"can read and write to it." +msgstr "" + +#: ./doc/training-guides/module001-ch006-overview-horizon-cli.xml1328(para) +msgid "To import a key" +msgstr "" + +#: ./doc/training-guides/module001-ch006-overview-horizon-cli.xml1331(para) +msgid "" +"If you have already generated a keypair with the public key located at " +"~/.ssh/id_rsa.pub, run the following command to upload the public key:" +msgstr "" + +#: ./doc/training-guides/module001-ch006-overview-horizon-cli.xml1336(para) +msgid "$ nova keypair-add --pub_key ~/.ssh/id_rsa.pub KEY_NAME" +msgstr "" + +#: ./doc/training-guides/module001-ch006-overview-horizon-cli.xml1340(para) +msgid "" +"The command registers the public key at the Nova database and names the " +"keypair KEY_NAME." +msgstr "" + +#: ./doc/training-guides/module001-ch006-overview-horizon-cli.xml1344(para) +msgid "" +"List keypairs to make sure that the uploaded keypair appears in the list:" +msgstr "" + +#: ./doc/training-guides/module001-ch006-overview-horizon-cli.xml1348(para) +#: ./doc/training-guides/module001-ch006-overview-horizon-cli.xml1678(para) +msgid "$ nova keypair-list" +msgstr "" + +#: ./doc/training-guides/module001-ch006-overview-horizon-cli.xml1351(guilabel) +msgid "Configure security groups and rules" +msgstr "" + +#: ./doc/training-guides/module001-ch006-overview-horizon-cli.xml1352(para) +msgid "To configure security groups" +msgstr "" + +#: ./doc/training-guides/module001-ch006-overview-horizon-cli.xml1355(para) +msgid "To list all security groups" +msgstr "" + +#: ./doc/training-guides/module001-ch006-overview-horizon-cli.xml1358(para) +msgid "" +"To list security groups for the current project, including descriptions, " +"enter the following command:" +msgstr "" + +#: ./doc/training-guides/module001-ch006-overview-horizon-cli.xml1363(para) +msgid "$ nova secgroup-list" +msgstr "" + +#: ./doc/training-guides/module001-ch006-overview-horizon-cli.xml1366(para) +msgid "To create a security group" +msgstr "" + +#: ./doc/training-guides/module001-ch006-overview-horizon-cli.xml1369(para) +msgid "" +"To create a security group with a specified name and description, enter the " +"following command:" +msgstr "" + +#: ./doc/training-guides/module001-ch006-overview-horizon-cli.xml1373(para) +msgid "$ nova secgroup-create SEC_GROUP_NAME GROUP_DESCRIPTION" +msgstr "" + +#: ./doc/training-guides/module001-ch006-overview-horizon-cli.xml1377(para) +msgid "To delete a security group" +msgstr "" + +#: ./doc/training-guides/module001-ch006-overview-horizon-cli.xml1380(para) +msgid "To delete a specified group, enter the following command:" +msgstr "" + +#: ./doc/training-guides/module001-ch006-overview-horizon-cli.xml1384(para) +msgid "$ nova secgroup-delete SEC_GROUP_NAME" +msgstr "" + +#: ./doc/training-guides/module001-ch006-overview-horizon-cli.xml1387(para) +msgid "To configure security group rules" +msgstr "" + +#: ./doc/training-guides/module001-ch006-overview-horizon-cli.xml1388(para) +msgid "Modify security group rules with the nova secgroup-*-rulecommands." +msgstr "" + +#: ./doc/training-guides/module001-ch006-overview-horizon-cli.xml1392(para) +msgid "" +"On a shell, source the OpenStack RC file. For details, seethe " +"section called “OpenStack RC file”." +msgstr "" + +#: ./doc/training-guides/module001-ch006-overview-horizon-cli.xml1400(para) +msgid "To list the rules for a security group" +msgstr "" + +#: ./doc/training-guides/module001-ch006-overview-horizon-cli.xml1403(para) +msgid "$ nova secgroup-list-rules SEC_GROUP_NAME" +msgstr "" + +#: ./doc/training-guides/module001-ch006-overview-horizon-cli.xml1406(para) +msgid "To allow SSH access to the instances" +msgstr "" + +#: ./doc/training-guides/module001-ch006-overview-horizon-cli.xml1409(para) +#: ./doc/training-guides/module001-ch006-overview-horizon-cli.xml1445(para) +msgid "Choose one of the following sub-steps:" +msgstr "" + +#: ./doc/training-guides/module001-ch006-overview-horizon-cli.xml1414(para) +msgid "Add rule for all IPs" +msgstr "" + +#: ./doc/training-guides/module001-ch006-overview-horizon-cli.xml1417(para) +msgid "" +"Either from all IP addresses (specified as IP subnet in CIDR notation as " +"0.0.0.0/0):" +msgstr "" + +#: ./doc/training-guides/module001-ch006-overview-horizon-cli.xml1421(para) +msgid "$ nova secgroup-add-rule SEC_GROUP_NAME tcp 22 22 0.0.0.0/0" +msgstr "" + +#: ./doc/training-guides/module001-ch006-overview-horizon-cli.xml1427(para) +msgid "Add rule for security groups" +msgstr "" + +#: ./doc/training-guides/module001-ch006-overview-horizon-cli.xml1430(para) +msgid "" +"Alternatively, you can allow only IP addresses from other security groups " +"(source groups) to access the specified port:" +msgstr "" + +#: ./doc/training-guides/module001-ch006-overview-horizon-cli.xml1435(para) +msgid "" +"$ nova secgroup-add-group-rule --ip_proto tcp --from_port 22 \\ --to_port 22" +" SEC_GROUP_NAME SOURCE_GROUP_NAME" +msgstr "" + +#: ./doc/training-guides/module001-ch006-overview-horizon-cli.xml1442(para) +msgid "To allow pinging the instances" +msgstr "" + +#: ./doc/training-guides/module001-ch006-overview-horizon-cli.xml1450(para) +msgid "To allow pinging from IPs" +msgstr "" + +#: ./doc/training-guides/module001-ch006-overview-horizon-cli.xml1453(para) +msgid "" +"Specify all IP addresses as IP subnet in CIDR notation: 0.0.0.0/0. This " +"command allows access to all codes and all types of ICMP traffic, " +"respectively:" +msgstr "" + +#: ./doc/training-guides/module001-ch006-overview-horizon-cli.xml1458(para) +msgid "$ nova secgroup-add-rule SEC_GROUP_NAME icmp -1 -1 0.0.0.0/0" +msgstr "" + +#: ./doc/training-guides/module001-ch006-overview-horizon-cli.xml1462(para) +msgid "To allow pinging from other security groups" +msgstr "" + +#: ./doc/training-guides/module001-ch006-overview-horizon-cli.xml1465(para) +msgid "" +"To allow only members of other security groups (source groups) to ping " +"instances:" +msgstr "" + +#: ./doc/training-guides/module001-ch006-overview-horizon-cli.xml1469(para) +msgid "" +"$ nova secgroup-add-group-rule --ip_proto icmp --from_port -1 \\ --to_port " +"-1 SEC_GROUP_NAME SOURCE_GROUP_NAME" +msgstr "" + +#: ./doc/training-guides/module001-ch006-overview-horizon-cli.xml1476(para) +msgid "To allow access through UDP port" +msgstr "" + +#: ./doc/training-guides/module001-ch006-overview-horizon-cli.xml1479(para) +msgid "" +"To allow access through a UDP port, such as allowing access to a DNS server " +"that runs on a VM, complete one of the following sub-steps:" +msgstr "" + +#: ./doc/training-guides/module001-ch006-overview-horizon-cli.xml1486(para) +msgid "To allow UDP access from IPs" +msgstr "" + +#: ./doc/training-guides/module001-ch006-overview-horizon-cli.xml1489(para) +msgid "Specify all IP addresses as IP subnet in CIDR notation: 0.0.0.0/0." +msgstr "" + +#: ./doc/training-guides/module001-ch006-overview-horizon-cli.xml1493(para) +msgid "$ nova secgroup-add-rule SEC_GROUP_NAME udp 53 53 0.0.0.0/0" +msgstr "" + +#: ./doc/training-guides/module001-ch006-overview-horizon-cli.xml1497(para) +msgid "To allow UDP access" +msgstr "" + +#: ./doc/training-guides/module001-ch006-overview-horizon-cli.xml1500(para) +msgid "" +"To allow only IP addresses from other security groups (source groups) to " +"access the specified port:" +msgstr "" + +#: ./doc/training-guides/module001-ch006-overview-horizon-cli.xml1504(para) +msgid "" +"$ nova secgroup-add-group-rule --ip_proto udp --from_port 53 \\ --to_port 53" +" SEC_GROUP_NAME SOURCE_GROUP_NAME" +msgstr "" + +#: ./doc/training-guides/module001-ch006-overview-horizon-cli.xml1511(para) +msgid "" +"To delete a security group rule, specify the same arguments that you used to" +" create the rule." +msgstr "" + +#: ./doc/training-guides/module001-ch006-overview-horizon-cli.xml1515(para) +msgid "" +"To delete the security rule that you created inStep" +" 3.a:" +msgstr "" + +#: ./doc/training-guides/module001-ch006-overview-horizon-cli.xml1520(para) +msgid "$ nova secgroup-delete-rule SEC_GROUP_NAME tcp 22 22 0.0.0.0/0" +msgstr "" + +#: ./doc/training-guides/module001-ch006-overview-horizon-cli.xml1524(para) +msgid "" +"To delete the security rule that you created inStep" +" 3.b:" +msgstr "" + +#: ./doc/training-guides/module001-ch006-overview-horizon-cli.xml1529(para) +msgid "" +"$ nova secgroup-delete-group-rule --ip_proto tcp --from_port 22 \\ --to_port" +" 22 SEC_GROUP_NAME SOURCE_GROUP_NAME" +msgstr "" + +#: ./doc/training-guides/module001-ch006-overview-horizon-cli.xml1535(para) +#: ./doc/training-guides/module001-ch006-overview-horizon-cli.xml1897(para) +msgid "Instances are virtual machines that run inside the cloud." +msgstr "" + +#: ./doc/training-guides/module001-ch006-overview-horizon-cli.xml1537(para) +msgid "" +"Before you can launch an instance, you must gather parameters such as the " +"image and flavor from which you want to launch your instance." +msgstr "" + +#: ./doc/training-guides/module001-ch006-overview-horizon-cli.xml1540(para) +msgid "" +"You can launch an instance directly from one of the available OpenStack " +"images or from an image that you have copied to a persistent volume. The " +"OpenStack Image Service provides a pool of images that are accessible to " +"members of different projects." +msgstr "" + +#: ./doc/training-guides/module001-ch006-overview-horizon-cli.xml1545(guilabel) +msgid "Gather parameters to launch an instance" +msgstr "" + +#: ./doc/training-guides/module001-ch006-overview-horizon-cli.xml1546(para) +msgid "To launch an instance, you must specify the following parameters:" +msgstr "" + +#: ./doc/training-guides/module001-ch006-overview-horizon-cli.xml1550(para) +msgid "" +"The instance source, which is an image or snapshot. Alternatively, you can " +"boot from a volume, which is block storage, to which you've copied an image " +"or snapshot." +msgstr "" + +#: ./doc/training-guides/module001-ch006-overview-horizon-cli.xml1556(para) +msgid "The imageor snapshot, which represents the operating system." +msgstr "" + +#: ./doc/training-guides/module001-ch006-overview-horizon-cli.xml1560(para) +msgid "A namefor your instance." +msgstr "" + +#: ./doc/training-guides/module001-ch006-overview-horizon-cli.xml1563(para) +msgid "" +"The flavorfor your instance, which defines the compute, memory, and storage " +"capacity of nova computing instances. A flavor is an available hardware " +"configuration for a server. It defines the \"size\" of a virtual server that" +" can be launched. For more details and a list of default flavors available, " +"see Section 1.5, \"Managing Flavors,\" (⇽ User Guide for Administrators )." +msgstr "" + +#: ./doc/training-guides/module001-ch006-overview-horizon-cli.xml1572(para) +msgid "" +"User Data is a special key in the metadata service which holds a file that " +"cloud aware applications within the guest instance can access. For example " +"thecloudinitsystem " +"is an open source package from Ubuntu that handles early initialization of a" +" cloud instance that makes use of this user data." +msgstr "" + +#: ./doc/training-guides/module001-ch006-overview-horizon-cli.xml1581(para) +msgid "" +"Access and security credentials, which include one or both of the following " +"credentials:" +msgstr "" + +#: ./doc/training-guides/module001-ch006-overview-horizon-cli.xml1587(para) +msgid "" +"A key-pair for your instance, which are SSH credentials that are injected " +"into images when they are launched. For this to work, the image must contain" +" the cloud-init package. Create at least one keypair for each project. If " +"you already have generated a key-pair with an external tool, you can import " +"it into OpenStack. You can use the keypair for multiple instances that " +"belong to that project. For details, refer to Section 1.5.1, Creating or " +"Importing Keys." +msgstr "" + +#: ./doc/training-guides/module001-ch006-overview-horizon-cli.xml1598(para) +msgid "" +"A security group, which defines which incoming network traffic is forwarded " +"to instances. Security groups hold a set of firewall policies, known as " +"security group rules. For details, see xx." +msgstr "" + +#: ./doc/training-guides/module001-ch006-overview-horizon-cli.xml1606(para) +msgid "" +"If needed, you can assign a floating (public) IP addressto a running " +"instance and attach a block storage device, or volume, for persistent " +"storage. For details, see Section 1.5.3, Managing IP Addresses and Section " +"1.7, Managing Volumes." +msgstr "" + +#: ./doc/training-guides/module001-ch006-overview-horizon-cli.xml1613(para) +msgid "" +"After you gather the parameters you need to launch an instance, you can " +"launch it from animageor avolume." +msgstr "" + +#: ./doc/training-guides/module001-ch006-overview-horizon-cli.xml1619(para) +msgid "To gather the parameters to launch an instance" +msgstr "" + +#: ./doc/training-guides/module001-ch006-overview-horizon-cli.xml1622(para) +msgid "On a shell, source the OpenStack RC file." +msgstr "" + +#: ./doc/training-guides/module001-ch006-overview-horizon-cli.xml1625(para) +#: ./doc/training-guides/module001-ch006-overview-horizon-cli.xml2026(para) +msgid "List the available flavors:" +msgstr "" + +#: ./doc/training-guides/module001-ch006-overview-horizon-cli.xml1628(para) +#: ./doc/training-guides/module001-ch006-overview-horizon-cli.xml2029(para) +msgid "$ nova flavor-list" +msgstr "" + +#: ./doc/training-guides/module001-ch006-overview-horizon-cli.xml1631(para) +msgid "Note the ID of the flavor that you want to use for your instance." +msgstr "" + +#: ./doc/training-guides/module001-ch006-overview-horizon-cli.xml1635(para) +msgid "List the available images:" +msgstr "" + +#: ./doc/training-guides/module001-ch006-overview-horizon-cli.xml1638(para) +msgid "$ nova image-list" +msgstr "" + +#: ./doc/training-guides/module001-ch006-overview-horizon-cli.xml1641(para) +msgid "" +"You can also filter the image list by using grep to find a specific image, " +"like this:" +msgstr "" + +#: ./doc/training-guides/module001-ch006-overview-horizon-cli.xml1645(para) +msgid "$ nova image-list | grep 'kernel'" +msgstr "" + +#: ./doc/training-guides/module001-ch006-overview-horizon-cli.xml1648(para) +msgid "Note the ID of the image that you want to boot your instance from." +msgstr "" + +#: ./doc/training-guides/module001-ch006-overview-horizon-cli.xml1652(para) +msgid "List the available security groups:" +msgstr "" + +#: ./doc/training-guides/module001-ch006-overview-horizon-cli.xml1655(para) +msgid "$ nova secgroup-list --all-tenants" +msgstr "" + +#: ./doc/training-guides/module001-ch006-overview-horizon-cli.xml1658(para) +msgid "" +"If you have not created any security groups, you can assign the instance to " +"only the default security group." +msgstr "" + +#: ./doc/training-guides/module001-ch006-overview-horizon-cli.xml1663(para) +msgid "You can also list rules for a specified security group:" +msgstr "" + +#: ./doc/training-guides/module001-ch006-overview-horizon-cli.xml1667(para) +msgid "$ nova secgroup-list-rules default" +msgstr "" + +#: ./doc/training-guides/module001-ch006-overview-horizon-cli.xml1670(para) +msgid "" +"In this example, the default security group has been modified to allow HTTP " +"traffic on the instance by permitting TCP traffic on Port 80." +msgstr "" + +#: ./doc/training-guides/module001-ch006-overview-horizon-cli.xml1675(para) +msgid "List the available keypairs." +msgstr "" + +#: ./doc/training-guides/module001-ch006-overview-horizon-cli.xml1681(para) +msgid "Note the name of the keypair that you use for SSH access." +msgstr "" + +#: ./doc/training-guides/module001-ch006-overview-horizon-cli.xml1686(para) +msgid "Use this procedure to launch an instance from an image." +msgstr "" + +#: ./doc/training-guides/module001-ch006-overview-horizon-cli.xml1691(para) +msgid "" +"Now you have all parameters required to launch an instance, run the " +"following command and specify the server name, flavor ID, and image ID. " +"Optionally, you can provide a key name for access control and security group" +" for security. You can also include metadata key and value pairs. For " +"example you can add a description for your server by providing the --meta " +"description=\"My Server\"parameter." +msgstr "" + +#: ./doc/training-guides/module001-ch006-overview-horizon-cli.xml1701(para) +msgid "" +"You can pass user data in a file on your local system and pass it at " +"instance launch by using the flag --user-data <user-data-file>." +msgstr "" + +#: ./doc/training-guides/module001-ch006-overview-horizon-cli.xml1706(para) +msgid "" +"$ nova boot --flavor FLAVOR_ID --image IMAGE_ID --key_name KEY_NAME --user-" +"data mydata.file \\ --security_group SEC_GROUP NAME_FOR_INSTANCE --meta " +"KEY=VALUE --meta KEY=VALUE" +msgstr "" + +#: ./doc/training-guides/module001-ch006-overview-horizon-cli.xml1712(para) +msgid "" +"The command returns a list of server properties, depending on which " +"parameters you provide." +msgstr "" + +#: ./doc/training-guides/module001-ch006-overview-horizon-cli.xml1716(para) +msgid "" +"A status of BUILD indicates that the instance has started, but is not yet " +"online." +msgstr "" + +#: ./doc/training-guides/module001-ch006-overview-horizon-cli.xml1720(para) +msgid "A status of ACTIVE indicates that your server is active." +msgstr "" + +#: ./doc/training-guides/module001-ch006-overview-horizon-cli.xml1724(para) +msgid "" +"Copy the server ID value from the id field in the output. You use this ID to" +" get details for or delete your server." +msgstr "" + +#: ./doc/training-guides/module001-ch006-overview-horizon-cli.xml1729(para) +msgid "" +"Copy the administrative password value from the adminPass field. You use " +"this value to log into your server." +msgstr "" + +#: ./doc/training-guides/module001-ch006-overview-horizon-cli.xml1734(para) +msgid "Check if the instance is online:" +msgstr "" + +#: ./doc/training-guides/module001-ch006-overview-horizon-cli.xml1740(para) +msgid "" +"This command lists all instances of the project you belong to, including " +"their ID, their name, their status, and their private (and if assigned, " +"their public) IP addresses." +msgstr "" + +#: ./doc/training-guides/module001-ch006-overview-horizon-cli.xml1746(para) +msgid "If the status for the instance is ACTIVE, the instance is online." +msgstr "" + +#: ./doc/training-guides/module001-ch006-overview-horizon-cli.xml1750(para) +msgid "" +"To view the available options for the nova listcommand, run the following " +"command:" +msgstr "" + +#: ./doc/training-guides/module001-ch006-overview-horizon-cli.xml1754(para) +msgid "$ nova help list" +msgstr "" + +#: ./doc/training-guides/module001-ch006-overview-horizon-cli.xml1757(para) +msgid "" +"If you did not provide a keypair, security groups, or rules, you can only " +"access the instance from inside the cloud through VNC. Even pinging the " +"instance is not possible." +msgstr "" + +#: ./doc/training-guides/module001-ch006-overview-horizon-cli.xml1764(para) +msgid "" +"After youcreate a bootable volume, " +"youlaunch an " +"instance from the volume." +msgstr "" + +#: ./doc/training-guides/module001-ch006-overview-horizon-cli.xml1772(para) +msgid "To create a bootable volume" +msgstr "" + +#: ./doc/training-guides/module001-ch006-overview-horizon-cli.xml1775(para) +msgid "To create a volume from an image, run the following command:" +msgstr "" + +#: ./doc/training-guides/module001-ch006-overview-horizon-cli.xml1779(para) +msgid "" +"# cinder create --image-id 397e713c-b95b-4186-ad46-6126863ea0a9 --display-" +"name my-bootable-vol 8" +msgstr "" + +#: ./doc/training-guides/module001-ch006-overview-horizon-cli.xml1784(para) +msgid "" +"Optionally, to configure your volume, see the Configuring Image Service and " +"Storage for Computechapter in the OpenStack Configuration Reference." +msgstr "" + +#: ./doc/training-guides/module001-ch006-overview-horizon-cli.xml1789(para) +msgid "To list volumes" +msgstr "" + +#: ./doc/training-guides/module001-ch006-overview-horizon-cli.xml1792(para) +msgid "Enter the following command:" +msgstr "" + +#: ./doc/training-guides/module001-ch006-overview-horizon-cli.xml1795(para) +#: ./doc/training-guides/module001-ch006-overview-horizon-cli.xml1886(para) +msgid "$ nova volume-list" +msgstr "" + +#: ./doc/training-guides/module001-ch006-overview-horizon-cli.xml1798(para) +msgid "Copy the value in the ID field for your volume." +msgstr "" + +#: ./doc/training-guides/module001-ch006-overview-horizon-cli.xml1803(para) +msgid "To launch an instance" +msgstr "" + +#: ./doc/training-guides/module001-ch006-overview-horizon-cli.xml1806(para) +msgid "" +"Enter the nova boot command with the --block_device_mapping parameter, as " +"follows:" +msgstr "" + +#: ./doc/training-guides/module001-ch006-overview-horizon-cli.xml1810(para) +msgid "" +"$ nova boot --flavor <flavor> --block_device_mapping " +"<dev_name>=<id>:<type>:<size>:<delete_on_terminate>" +" <name>" +msgstr "" + +#: ./doc/training-guides/module001-ch006-overview-horizon-cli.xml1816(para) +msgid "The command arguments are:" +msgstr "" + +#: ./doc/training-guides/module001-ch006-overview-horizon-cli.xml1819(para) +msgid "--flavor flavor" +msgstr "" + +#: ./doc/training-guides/module001-ch006-overview-horizon-cli.xml1822(para) +msgid "The flavor ID." +msgstr "" + +#: ./doc/training-guides/module001-ch006-overview-horizon-cli.xml1825(para) +msgid "--block_device_mapping dev- name=id:type:size:delete-on-terminate" +msgstr "" + +#: ./doc/training-guides/module001-ch006-overview-horizon-cli.xml1831(para) +msgid "" +"dev-name. A device name where the volume is attached in the system at " +"/dev/dev_name. This value is typically vda." +msgstr "" + +#: ./doc/training-guides/module001-ch006-overview-horizon-cli.xml1836(para) +msgid "" +"id. The ID of the volume to boot from, as shown in the output of nova " +"volume-list." +msgstr "" + +#: ./doc/training-guides/module001-ch006-overview-horizon-cli.xml1840(para) +msgid "" +"type. Either snap or any other value, including a blank string. snap means " +"that the volume was created from a snapshot." +msgstr "" + +#: ./doc/training-guides/module001-ch006-overview-horizon-cli.xml1845(para) +msgid "" +"size. The size of the volume, in GBs. It is safe to leave this blank and " +"have the Compute service infer the size." +msgstr "" + +#: ./doc/training-guides/module001-ch006-overview-horizon-cli.xml1850(para) +msgid "" +"delete-on-terminate. A boolean that indicates whether the volume should be " +"deleted when the instance is terminated. You can specify" +msgstr "" + +#: ./doc/training-guides/module001-ch006-overview-horizon-cli.xml1857(para) +msgid "True or 1" +msgstr "" + +#: ./doc/training-guides/module001-ch006-overview-horizon-cli.xml1860(para) +msgid "False or 0" +msgstr "" + +#: ./doc/training-guides/module001-ch006-overview-horizon-cli.xml1863(para) +msgid "name" +msgstr "" + +#: ./doc/training-guides/module001-ch006-overview-horizon-cli.xml1866(para) +msgid "The name for the server." +msgstr "" + +#: ./doc/training-guides/module001-ch006-overview-horizon-cli.xml1869(para) +msgid "" +"For example, you might enter the following command to boot from a volume " +"with ID bd7cf584-45de-44e3-bf7f-f7b50bf235e. The volume is not deleted when " +"the instance is terminated:" +msgstr "" + +#: ./doc/training-guides/module001-ch006-overview-horizon-cli.xml1875(para) +msgid "" +"$ nova boot --flavor 2 --image 397e713c-b95b-4186-ad46-6126863ea0a9 " +"--block_device_mapping vda=bd7cf584-45de-44e3-bf7f-f7b50bf235e3:::0 " +"myInstanceFromVolume" +msgstr "" + +#: ./doc/training-guides/module001-ch006-overview-horizon-cli.xml1882(para) +msgid "" +"Now when you list volumes, you can see that the volume is attached to a " +"server:" +msgstr "" + +#: ./doc/training-guides/module001-ch006-overview-horizon-cli.xml1889(para) +msgid "" +"Additionally, when you list servers, you see the server that you booted from" +" a volume:" +msgstr "" + +#: ./doc/training-guides/module001-ch006-overview-horizon-cli.xml1896(guilabel) +msgid "Manage instances and hosts" +msgstr "" + +#: ./doc/training-guides/module001-ch006-overview-horizon-cli.xml1899(guilabel) +msgid "Manage IP addresses" +msgstr "" + +#: ./doc/training-guides/module001-ch006-overview-horizon-cli.xml1900(para) +msgid "" +"Each instance can have a private, or fixed, IP address and a public, or " +"floating, one." +msgstr "" + +#: ./doc/training-guides/module001-ch006-overview-horizon-cli.xml1902(para) +msgid "" +"Private IP addresses are used for communication between instances, and " +"public ones are used for communication with the outside world." +msgstr "" + +#: ./doc/training-guides/module001-ch006-overview-horizon-cli.xml1905(para) +msgid "" +"When you launch an instance, it is automatically assigned a private IP " +"address that stays the same until you explicitly terminate the instance. " +"Rebooting an instance has no effect on the private IP address." +msgstr "" + +#: ./doc/training-guides/module001-ch006-overview-horizon-cli.xml1909(para) +msgid "" +"A pool of floating IPs, configured by the cloud operator, is available in " +"OpenStack Compute." +msgstr "" + +#: ./doc/training-guides/module001-ch006-overview-horizon-cli.xml1911(para) +msgid "" +"You can allocate a certain number of these to a project: The maximum number " +"of floating IP addresses per project is defined by the quota." +msgstr "" + +#: ./doc/training-guides/module001-ch006-overview-horizon-cli.xml1914(para) +msgid "" +"You can add a floating IP address from this set to an instance of the " +"project. Floating IP addresses can be dynamically disassociated and " +"associated with other instances of the same project at any time." +msgstr "" + +#: ./doc/training-guides/module001-ch006-overview-horizon-cli.xml1918(para) +msgid "" +"Before you can assign a floating IP address to an instance, you first must " +"allocate floating IPs to a project. After floating IP addresses have been " +"allocated to the current project, you can assign them to running instances." +msgstr "" + +#: ./doc/training-guides/module001-ch006-overview-horizon-cli.xml1922(para) +msgid "" +"One floating IP address can be assigned to only one instance at a time. " +"Floating IP addresses can be managed with the nova *floating-ip-*commands, " +"provided by the python-novaclient package." +msgstr "" + +#: ./doc/training-guides/module001-ch006-overview-horizon-cli.xml1926(para) +msgid "To list pools with floating IP addresses" +msgstr "" + +#: ./doc/training-guides/module001-ch006-overview-horizon-cli.xml1929(para) +msgid "To list all pools that provide floating IP addresses:" +msgstr "" + +#: ./doc/training-guides/module001-ch006-overview-horizon-cli.xml1933(para) +#: ./doc/training-guides/module001-ch006-overview-horizon-cli.xml1944(para) +msgid "$ nova floating-ip-pool-list" +msgstr "" + +#: ./doc/training-guides/module001-ch006-overview-horizon-cli.xml1936(para) +msgid "To allocate a floating IP address to the current project" +msgstr "" + +#: ./doc/training-guides/module001-ch006-overview-horizon-cli.xml1940(para) +msgid "" +"The output of the following command shows the freshly allocated IP address:" +msgstr "" + +#: ./doc/training-guides/module001-ch006-overview-horizon-cli.xml1947(para) +msgid "" +"If more than one pool of IP addresses is available, you can also specify the" +" pool from which to allocate the IP address:" +msgstr "" + +#: ./doc/training-guides/module001-ch006-overview-horizon-cli.xml1952(para) +msgid "$ floating-ip-create POOL_NAME" +msgstr "" + +#: ./doc/training-guides/module001-ch006-overview-horizon-cli.xml1955(para) +msgid "To list floating IP addresses allocated to the current project" +msgstr "" + +#: ./doc/training-guides/module001-ch006-overview-horizon-cli.xml1959(para) +msgid "" +"If an IP is already associated with an instance, the output also shows the " +"IP for the instance, thefixed IP address for the instance, and the name of " +"the pool that provides the floating IP address." +msgstr "" + +#: ./doc/training-guides/module001-ch006-overview-horizon-cli.xml1965(para) +#: ./doc/training-guides/module001-ch006-overview-horizon-cli.xml1989(para) +msgid "$ nova floating-ip-list" +msgstr "" + +#: ./doc/training-guides/module001-ch006-overview-horizon-cli.xml1968(para) +msgid "To release a floating IP address from the current project" +msgstr "" + +#: ./doc/training-guides/module001-ch006-overview-horizon-cli.xml1972(para) +msgid "" +"The IP address is returned to the pool of IP addresses that are available " +"for all projects. If an IP address is currently assigned to a running " +"instance, it is automatically disassociated from the instance." +msgstr "" + +#: ./doc/training-guides/module001-ch006-overview-horizon-cli.xml1978(para) +msgid "$ nova floating-ip-delete FLOATING_IP" +msgstr "" + +#: ./doc/training-guides/module001-ch006-overview-horizon-cli.xml1981(para) +msgid "To assign a floating IP address to an instance" +msgstr "" + +#: ./doc/training-guides/module001-ch006-overview-horizon-cli.xml1984(para) +msgid "" +"To associate an IP address with an instance, one or multiple floating IP " +"addresses must be allocated to the current project. Check this with:" +msgstr "" + +#: ./doc/training-guides/module001-ch006-overview-horizon-cli.xml1992(para) +msgid "" +"In addition, you must know the instance's name (or ID). To look up the " +"instances that belong to the current project, use the nova list command." +msgstr "" + +#: ./doc/training-guides/module001-ch006-overview-horizon-cli.xml1997(para) +msgid "$ nova add-floating-ip INSTANCE_NAME_OR_ID FLOATING_IP" +msgstr "" + +#: ./doc/training-guides/module001-ch006-overview-horizon-cli.xml2001(para) +msgid "" +"After you assign the IP with nova add-floating-ipand configure security " +"group rules for the instance, the instance is publicly available at the " +"floating IP address." +msgstr "" + +#: ./doc/training-guides/module001-ch006-overview-horizon-cli.xml2007(para) +msgid "To remove a floating IP address from an instance" +msgstr "" + +#: ./doc/training-guides/module001-ch006-overview-horizon-cli.xml2010(para) +msgid "" +"To remove a floating IP address from an instance, you must specify the same " +"arguments that you used to assign the IP." +msgstr "" + +#: ./doc/training-guides/module001-ch006-overview-horizon-cli.xml2015(para) +msgid "$ nova remove-floating-ip INSTANCE_NAME_OR_ID FLOATING_IP" +msgstr "" + +#: ./doc/training-guides/module001-ch006-overview-horizon-cli.xml2019(guilabel) +msgid "Change the size of your server" +msgstr "" + +#: ./doc/training-guides/module001-ch006-overview-horizon-cli.xml2021(para) +msgid "You change the size of a server by changing its flavor." +msgstr "" + +#: ./doc/training-guides/module001-ch006-overview-horizon-cli.xml2023(para) +msgid "To change the size of your server" +msgstr "" + +#: ./doc/training-guides/module001-ch006-overview-horizon-cli.xml2032(para) +msgid "Show information about your server, including its size:" +msgstr "" + +#: ./doc/training-guides/module001-ch006-overview-horizon-cli.xml2036(para) +msgid "$ nova show myCirrosServer" +msgstr "" + +#: ./doc/training-guides/module001-ch006-overview-horizon-cli.xml2039(para) +msgid "The size of the server is m1.small (2)." +msgstr "" + +#: ./doc/training-guides/module001-ch006-overview-horizon-cli.xml2042(para) +msgid "" +"To resize the server, pass the server ID and the desired flavor to the nova " +"resizecommand. Include the --poll parameter to report the resize progress." +msgstr "" + +#: ./doc/training-guides/module001-ch006-overview-horizon-cli.xml2047(para) +msgid "$ nova resize myCirrosServer 4 --poll" +msgstr "" + +#: ./doc/training-guides/module001-ch006-overview-horizon-cli.xml2050(para) +msgid "Instance resizing... 100% completeFinished" +msgstr "" + +#: ./doc/training-guides/module001-ch006-overview-horizon-cli.xml2053(para) +msgid "Show the status for your server:" +msgstr "" + +#: ./doc/training-guides/module001-ch006-overview-horizon-cli.xml2059(para) +msgid "" +"When the resize completes, the status becomes VERIFY_RESIZE. To confirm the " +"resize:" +msgstr "" + +#: ./doc/training-guides/module001-ch006-overview-horizon-cli.xml2063(para) +msgid "$ nova resize-confirm 6beefcf7-9de6-48b3-9ba9-e11b343189b3" +msgstr "" + +#: ./doc/training-guides/module001-ch006-overview-horizon-cli.xml2067(para) +#: ./doc/training-guides/module001-ch006-overview-horizon-cli.xml2078(para) +msgid "The server status becomes ACTIVE." +msgstr "" + +#: ./doc/training-guides/module001-ch006-overview-horizon-cli.xml2070(para) +msgid "" +"If the resize fails or does not work as expected, you can revert the resize:" +msgstr "" + +#: ./doc/training-guides/module001-ch006-overview-horizon-cli.xml2074(para) +msgid "$ nova resize-revert 6beefcf7-9de6-48b3-9ba9-e11b343189b3" +msgstr "" + +#: ./doc/training-guides/module001-ch006-overview-horizon-cli.xml2081(guilabel) +msgid "Stop and start an instance" +msgstr "" + +#: ./doc/training-guides/module001-ch006-overview-horizon-cli.xml2082(para) +msgid "Use one of the following methods to stop and start an instance." +msgstr "" + +#: ./doc/training-guides/module001-ch006-overview-horizon-cli.xml2084(guilabel) +msgid "Pause and un-pause an instance" +msgstr "" + +#: ./doc/training-guides/module001-ch006-overview-horizon-cli.xml2085(para) +msgid "To pause and un-pause a server" +msgstr "" + +#: ./doc/training-guides/module001-ch006-overview-horizon-cli.xml2088(para) +msgid "To pause a server, run the following command:" +msgstr "" + +#: ./doc/training-guides/module001-ch006-overview-horizon-cli.xml2091(para) +msgid "$ nova pause SERVER" +msgstr "" + +#: ./doc/training-guides/module001-ch006-overview-horizon-cli.xml2094(para) +msgid "" +"This command stores the state of the VM in RAM. A paused instance continues " +"to run in a frozen state." +msgstr "" + +#: ./doc/training-guides/module001-ch006-overview-horizon-cli.xml2099(para) +msgid "To un-pause the server, run the following command:" +msgstr "" + +#: ./doc/training-guides/module001-ch006-overview-horizon-cli.xml2103(para) +msgid "$ nova unpause SERVER" +msgstr "" + +#: ./doc/training-guides/module001-ch006-overview-horizon-cli.xml2106(guilabel) +msgid "Suspend and resume an instance" +msgstr "" + +#: ./doc/training-guides/module001-ch006-overview-horizon-cli.xml2107(para) +msgid "To suspend and resume a server" +msgstr "" + +#: ./doc/training-guides/module001-ch006-overview-horizon-cli.xml2108(para) +msgid "" +"Administrative users might want to suspend an infrequently used instance or " +"to perform system maintenance." +msgstr "" + +#: ./doc/training-guides/module001-ch006-overview-horizon-cli.xml2113(para) +msgid "" +"When you suspend an instance, its VM state is stored on disk, all memory is " +"written to disk, and the virtual machine is stopped. Suspending an instance " +"is similar to placing a device in hibernation; memory and vCPUs become " +"available." +msgstr "" + +#: ./doc/training-guides/module001-ch006-overview-horizon-cli.xml2120(para) +msgid "" +"To initiate a hypervisor-level suspend operation, run the following command:" +msgstr "" + +#: ./doc/training-guides/module001-ch006-overview-horizon-cli.xml2124(para) +msgid "$ nova suspend SERVER" +msgstr "" + +#: ./doc/training-guides/module001-ch006-overview-horizon-cli.xml2127(para) +msgid "To resume a suspended server:" +msgstr "" + +#: ./doc/training-guides/module001-ch006-overview-horizon-cli.xml2130(para) +msgid "$ nova resume SERVER" +msgstr "" + +#: ./doc/training-guides/module001-ch006-overview-horizon-cli.xml2133(guilabel) +msgid "Reboot an instance" +msgstr "" + +#: ./doc/training-guides/module001-ch006-overview-horizon-cli.xml2134(para) +msgid "" +"You can perform a soft or hard reboot of a running instance. A soft reboot " +"attempts a graceful shutdown and restart of the instance. A hard reboot " +"power cycles the instance." +msgstr "" + +#: ./doc/training-guides/module001-ch006-overview-horizon-cli.xml2138(para) +msgid "To reboot a server" +msgstr "" + +#: ./doc/training-guides/module001-ch006-overview-horizon-cli.xml2141(para) +msgid "By default, when you reboot a server, it is a soft reboot." +msgstr "" + +#: ./doc/training-guides/module001-ch006-overview-horizon-cli.xml2145(para) +msgid "$ nova reboot SERVER" +msgstr "" + +#: ./doc/training-guides/module001-ch006-overview-horizon-cli.xml2148(para) +msgid "To perform a hard reboot, pass the --hard parameter, as follows:" +msgstr "" + +#: ./doc/training-guides/module001-ch006-overview-horizon-cli.xml2150(para) +msgid "$ nova reboot --hard SERVER" +msgstr "" + +#: ./doc/training-guides/module001-ch006-overview-horizon-cli.xml2151(guilabel) +msgid "Evacuate instances" +msgstr "" + +#: ./doc/training-guides/module001-ch006-overview-horizon-cli.xml2152(para) +msgid "" +"If a cloud compute node fails due to a hardware malfunction or another " +"reason, you can evacuate instances to make them available again." +msgstr "" + +#: ./doc/training-guides/module001-ch006-overview-horizon-cli.xml2155(para) +msgid "You can choose evacuation parameters for your use case." +msgstr "" + +#: ./doc/training-guides/module001-ch006-overview-horizon-cli.xml2157(para) +msgid "" +"To preserve user data on server disk, you must configure shared storage on " +"the target host. Also, you must validate that the current VM host is down. " +"Otherwise the evacuation fails with an error." +msgstr "" + +#: ./doc/training-guides/module001-ch006-overview-horizon-cli.xml2161(para) +msgid "To evacuate your server" +msgstr "" + +#: ./doc/training-guides/module001-ch006-overview-horizon-cli.xml2164(para) +msgid "" +"To find a different host for the evacuated instance, run the following " +"command to lists hosts:" +msgstr "" + +#: ./doc/training-guides/module001-ch006-overview-horizon-cli.xml2168(para) +#: ./doc/training-guides/module001-ch006-overview-horizon-cli.xml2345(para) +msgid "$ nova host-list" +msgstr "" + +#: ./doc/training-guides/module001-ch006-overview-horizon-cli.xml2171(para) +msgid "" +"You can pass the instance password to the command by using the --password " +"<pwd> option. If you do not specify a password, one is generated and " +"printed after the command finishes successfully. The following command " +"evacuates a server without shared storage:" +msgstr "" + +#: ./doc/training-guides/module001-ch006-overview-horizon-cli.xml2178(para) +msgid "$ nova evacuate evacuated_server_name host_b" +msgstr "" + +#: ./doc/training-guides/module001-ch006-overview-horizon-cli.xml2181(para) +msgid "" +"The command evacuates an instance from a down host to a specified host. The " +"instance is booted from a new disk, but preserves its configuration " +"including its ID, name, uid, IP address, and so on. The command returns a " +"password:" +msgstr "" + +#: ./doc/training-guides/module001-ch006-overview-horizon-cli.xml2188(para) +msgid "" +"To preserve the user disk data on the evacuated server, deploy OpenStack " +"Compute with shared filesystem." +msgstr "" + +#: ./doc/training-guides/module001-ch006-overview-horizon-cli.xml2193(para) +msgid "$ nova evacuate evacuated_server_name host_b --on-shared-storage" +msgstr "" + +#: ./doc/training-guides/module001-ch006-overview-horizon-cli.xml2197(guilabel) +msgid "Delete an instance" +msgstr "" + +#: ./doc/training-guides/module001-ch006-overview-horizon-cli.xml2198(para) +msgid "When you no longer need an instance, you can delete it." +msgstr "" + +#: ./doc/training-guides/module001-ch006-overview-horizon-cli.xml2200(para) +msgid "To delete an instance" +msgstr "" + +#: ./doc/training-guides/module001-ch006-overview-horizon-cli.xml2203(para) +msgid "List all instances:" +msgstr "" + +#: ./doc/training-guides/module001-ch006-overview-horizon-cli.xml2209(para) +msgid "" +"Use the following command to delete the newServer instance, which is in " +"ERROR state:" +msgstr "" + +#: ./doc/training-guides/module001-ch006-overview-horizon-cli.xml2213(para) +msgid "$ nova delete newServer" +msgstr "" + +#: ./doc/training-guides/module001-ch006-overview-horizon-cli.xml2216(para) +msgid "The command does not notify that your server was deleted." +msgstr "" + +#: ./doc/training-guides/module001-ch006-overview-horizon-cli.xml2220(para) +msgid "Instead, run the nova list command:" +msgstr "" + +#: ./doc/training-guides/module001-ch006-overview-horizon-cli.xml2226(para) +msgid "The deleted instance does not appear in the list." +msgstr "" + +#: ./doc/training-guides/module001-ch006-overview-horizon-cli.xml2230(guilabel) +msgid "Get a console to an instance" +msgstr "" + +#: ./doc/training-guides/module001-ch006-overview-horizon-cli.xml2231(para) +msgid "To get a console to an instance" +msgstr "" + +#: ./doc/training-guides/module001-ch006-overview-horizon-cli.xml2232(para) +msgid "To get a VNC console to an instance, run the following command:" +msgstr "" + +#: ./doc/training-guides/module001-ch006-overview-horizon-cli.xml2234(para) +msgid "$ nova get-vnc-console myCirrosServer xvpvnc" +msgstr "" + +#: ./doc/training-guides/module001-ch006-overview-horizon-cli.xml2235(para) +msgid "The command returns a URL from which you can access your instance:" +msgstr "" + +#: ./doc/training-guides/module001-ch006-overview-horizon-cli.xml2237(guilabel) +msgid "Manage bare metal nodes" +msgstr "" + +#: ./doc/training-guides/module001-ch006-overview-horizon-cli.xml2238(para) +msgid "" +"If you use the bare metal driver, you must create a bare metal node and add " +"a network interface to it. You then launch an instance from a bare metal " +"image. You can list and delete bare metal nodes. When you delete a node, any" +" associated network interfaces are removed. You can list and remove network " +"interfaces that are associated with a bare metal node." +msgstr "" + +#: ./doc/training-guides/module001-ch006-overview-horizon-cli.xml2245(para) +msgid "Commands" +msgstr "" + +#: ./doc/training-guides/module001-ch006-overview-horizon-cli.xml2248(para) +msgid "baremetal-interface-add" +msgstr "" + +#: ./doc/training-guides/module001-ch006-overview-horizon-cli.xml2251(para) +msgid "Adds a network interface to a bare metal node." +msgstr "" + +#: ./doc/training-guides/module001-ch006-overview-horizon-cli.xml2254(para) +msgid "baremetal-interface-list" +msgstr "" + +#: ./doc/training-guides/module001-ch006-overview-horizon-cli.xml2257(para) +msgid "Lists network interfaces associated with a bare metal node." +msgstr "" + +#: ./doc/training-guides/module001-ch006-overview-horizon-cli.xml2261(para) +msgid "baremetal-interface-remove" +msgstr "" + +#: ./doc/training-guides/module001-ch006-overview-horizon-cli.xml2264(para) +msgid "Removes a network interface from a bare metal node." +msgstr "" + +#: ./doc/training-guides/module001-ch006-overview-horizon-cli.xml2268(para) +msgid "baremetal-node-create" +msgstr "" + +#: ./doc/training-guides/module001-ch006-overview-horizon-cli.xml2271(para) +msgid "Creates a bare metal node." +msgstr "" + +#: ./doc/training-guides/module001-ch006-overview-horizon-cli.xml2274(para) +msgid "baremetal-node-delete" +msgstr "" + +#: ./doc/training-guides/module001-ch006-overview-horizon-cli.xml2277(para) +msgid "Removes a bare metal node and any associated interfaces." +msgstr "" + +#: ./doc/training-guides/module001-ch006-overview-horizon-cli.xml2281(para) +msgid "baremetal-node-list" +msgstr "" + +#: ./doc/training-guides/module001-ch006-overview-horizon-cli.xml2284(para) +msgid "Lists available bare metal nodes." +msgstr "" + +#: ./doc/training-guides/module001-ch006-overview-horizon-cli.xml2287(para) +msgid "baremetal-node-show" +msgstr "" + +#: ./doc/training-guides/module001-ch006-overview-horizon-cli.xml2290(para) +msgid "Shows information about a bare metal node." +msgstr "" + +#: ./doc/training-guides/module001-ch006-overview-horizon-cli.xml2293(para) +msgid "To manage bare metal nodes" +msgstr "" + +#: ./doc/training-guides/module001-ch006-overview-horizon-cli.xml2296(para) +msgid "Create a bare metal node." +msgstr "" + +#: ./doc/training-guides/module001-ch006-overview-horizon-cli.xml2299(para) +msgid "" +"$ nova baremetal-node-create --pm_address=1.2.3.4 --pm_user=ipmi " +"--pm_password=ipmi $(hostname -f) 1 512 10 aa:bb:cc:dd:ee:ff" +msgstr "" + +#: ./doc/training-guides/module001-ch006-overview-horizon-cli.xml2304(para) +msgid "Add network interface information to the node:" +msgstr "" + +#: ./doc/training-guides/module001-ch006-overview-horizon-cli.xml2307(para) +msgid "$ nova baremetal-interface-add 1 aa:bb:cc:dd:ee:ff" +msgstr "" + +#: ./doc/training-guides/module001-ch006-overview-horizon-cli.xml2311(para) +msgid "Launch an instance from a bare metal image:" +msgstr "" + +#: ./doc/training-guides/module001-ch006-overview-horizon-cli.xml2314(para) +msgid "" +"$ nova boot --image my-baremetal-image --flavor my-baremetal-flavor test" +msgstr "" + +#: ./doc/training-guides/module001-ch006-overview-horizon-cli.xml2318(para) +msgid "|... wait for instance to become active ..." +msgstr "" + +#: ./doc/training-guides/module001-ch006-overview-horizon-cli.xml2321(para) +msgid "" +"You can list bare metal nodes and interfaces. When a node is in use, its " +"status includes the UUID of the instance that runs on it:" +msgstr "" + +#: ./doc/training-guides/module001-ch006-overview-horizon-cli.xml2326(para) +msgid "$ nova baremetal-node-list" +msgstr "" + +#: ./doc/training-guides/module001-ch006-overview-horizon-cli.xml2329(para) +msgid "Show details about a bare metal node:" +msgstr "" + +#: ./doc/training-guides/module001-ch006-overview-horizon-cli.xml2332(para) +msgid "$ nova baremetal-node-show 1" +msgstr "" + +#: ./doc/training-guides/module001-ch006-overview-horizon-cli.xml2335(guilabel) +msgid "Show usage statistics for hosts and instances" +msgstr "" + +#: ./doc/training-guides/module001-ch006-overview-horizon-cli.xml2336(para) +msgid "" +"You can show basic statistics on resource usage for hosts and instances." +msgstr "" + +#: ./doc/training-guides/module001-ch006-overview-horizon-cli.xml2338(para) +msgid "To show host usage statistics" +msgstr "" + +#: ./doc/training-guides/module001-ch006-overview-horizon-cli.xml2341(para) +msgid "List the hosts and the nova-related services that run on them:" +msgstr "" + +#: ./doc/training-guides/module001-ch006-overview-horizon-cli.xml2348(para) +msgid "" +"Get a summary of resource usage of all of the instances running on the host." +msgstr "" + +#: ./doc/training-guides/module001-ch006-overview-horizon-cli.xml2352(para) +msgid "$ nova host-describe devstack-grizzly" +msgstr "" + +#: ./doc/training-guides/module001-ch006-overview-horizon-cli.xml2355(para) +msgid "" +"The cpu column shows the sum of the virtual CPUs for instances running on " +"the host." +msgstr "" + +#: ./doc/training-guides/module001-ch006-overview-horizon-cli.xml2359(para) +msgid "" +"The memory_mb column shows the sum of the memory (in MB) allocated to the " +"instances that run on the hosts." +msgstr "" + +#: ./doc/training-guides/module001-ch006-overview-horizon-cli.xml2364(para) +msgid "" +"The disk_gb column shows the sum of the root and ephemeral disk sizes (in " +"GB) of the instances that run on the hosts." +msgstr "" + +#: ./doc/training-guides/module001-ch006-overview-horizon-cli.xml2369(para) +msgid "To show instance usage statistics" +msgstr "" + +#: ./doc/training-guides/module001-ch006-overview-horizon-cli.xml2372(para) +msgid "Get CPU, memory, I/O, and network statistics for an instance." +msgstr "" + +#: ./doc/training-guides/module001-ch006-overview-horizon-cli.xml2376(para) +msgid "First, list instances:" +msgstr "" + +#: ./doc/training-guides/module001-ch006-overview-horizon-cli.xml2382(para) +msgid "Then, get diagnostic statistics:" +msgstr "" + +#: ./doc/training-guides/module001-ch006-overview-horizon-cli.xml2385(para) +msgid "$ nova diagnostics myCirrosServer" +msgstr "" + +#: ./doc/training-guides/module001-ch006-overview-horizon-cli.xml2388(para) +msgid "Get summary statistics for each tenant:" +msgstr "" + +#: ./doc/training-guides/module001-ch006-overview-horizon-cli.xml2391(para) +msgid "$ nova usage-list" +msgstr "" + +#: ./doc/training-guides/module001-ch006-overview-horizon-cli.xml2394(para) +msgid "Usage from 2013-06-25 to 2013-07-24:" +msgstr "" + +#: ./doc/training-guides/module001-ch006-overview-horizon-cli.xml2397(guilabel) +msgid "Create and manage networks" +msgstr "" + +#: ./doc/training-guides/module001-ch006-overview-horizon-cli.xml2398(para) +msgid "Before you run commands, set the following environment variables:" +msgstr "" + +#: ./doc/training-guides/module001-ch006-overview-horizon-cli.xml2400(para) +msgid "" +"export OS_USERNAME=adminexport OS_PASSWORD=passwordexport " +"OS_TENANT_NAME=adminexport OS_AUTH_URL=http://localhost:5000/v2.0" +msgstr "" + +#: ./doc/training-guides/module001-ch006-overview-horizon-cli.xml2403(para) +msgid "To create and manage networks" +msgstr "" + +#: ./doc/training-guides/module001-ch006-overview-horizon-cli.xml2406(para) +msgid "List the extensions of the system:" +msgstr "" + +#: ./doc/training-guides/module001-ch006-overview-horizon-cli.xml2409(para) +msgid "$ neutron ext-list -c alias -c name" +msgstr "" + +#: ./doc/training-guides/module001-ch006-overview-horizon-cli.xml2412(para) +msgid "Create a network:" +msgstr "" + +#: ./doc/training-guides/module001-ch006-overview-horizon-cli.xml2415(para) +msgid "$ neutron net-create net1" +msgstr "" + +#: ./doc/training-guides/module001-ch006-overview-horizon-cli.xml2418(para) +#: ./doc/training-guides/module001-ch006-overview-horizon-cli.xml2429(para) +msgid "Created a new network:" +msgstr "" + +#: ./doc/training-guides/module001-ch006-overview-horizon-cli.xml2421(para) +msgid "Create a network with specified provider network type:" +msgstr "" + +#: ./doc/training-guides/module001-ch006-overview-horizon-cli.xml2425(para) +msgid "$ neutron net-create net2 --provider:network-type local" +msgstr "" + +#: ./doc/training-guides/module001-ch006-overview-horizon-cli.xml2432(para) +msgid "" +"Just as shown previous, the unknown option --provider:network-type is used " +"to create a local provider network." +msgstr "" + +#: ./doc/training-guides/module001-ch006-overview-horizon-cli.xml2437(para) +msgid "Create a subnet:" +msgstr "" + +#: ./doc/training-guides/module001-ch006-overview-horizon-cli.xml2440(para) +msgid "$ neutron subnet-create net1 192.168.2.0/24 --name subnet1" +msgstr "" + +#: ./doc/training-guides/module001-ch006-overview-horizon-cli.xml2444(para) +msgid "Created a new subnet:" +msgstr "" + +#: ./doc/training-guides/module001-ch006-overview-horizon-cli.xml2447(para) +msgid "" +"In the previous command, net1 is the network name, 192.168.2.0/24 is the " +"subnet's CIDR. They are positional arguments. --name subnet1 is an unknown " +"option, which specifies the subnet's name." +msgstr "" + +#: ./doc/training-guides/module001-ch006-overview-horizon-cli.xml2453(para) +msgid "Create a port with specified IP address:" +msgstr "" + +#: ./doc/training-guides/module001-ch006-overview-horizon-cli.xml2456(para) +msgid "$ neutron port-create net1 --fixed-ip ip_address=192.168.2.40" +msgstr "" + +#: ./doc/training-guides/module001-ch006-overview-horizon-cli.xml2460(para) +#: ./doc/training-guides/module001-ch006-overview-horizon-cli.xml2475(para) +msgid "Created a new port:" +msgstr "" + +#: ./doc/training-guides/module001-ch006-overview-horizon-cli.xml2463(para) +msgid "" +"In the previous command, net1 is the network name, which is a positional " +"argument. --fixed-ip ip_address=192.168.2.40 is an option, which specifies " +"the port's fixed IP address we wanted." +msgstr "" + +#: ./doc/training-guides/module001-ch006-overview-horizon-cli.xml2469(para) +msgid "Create a port without specified IP address:" +msgstr "" + +#: ./doc/training-guides/module001-ch006-overview-horizon-cli.xml2472(para) +msgid "$ neutron port-create net1" +msgstr "" + +#: ./doc/training-guides/module001-ch006-overview-horizon-cli.xml2478(para) +msgid "" +"We can see that the system will allocate one IP address if we don't specify " +"the IP address in command line." +msgstr "" + +#: ./doc/training-guides/module001-ch006-overview-horizon-cli.xml2482(para) +msgid "Query ports with specified fixed IP addresses:" +msgstr "" + +#: ./doc/training-guides/module001-ch006-overview-horizon-cli.xml2485(para) +msgid "" +"$ neutron port-list --fixed-ips ip_address=192.168.2.2 " +"ip_address=192.168.2.40" +msgstr "" + +#: ./doc/training-guides/module001-ch006-overview-horizon-cli.xml2489(para) +msgid "" +"--fixed-ips ip_address=192.168.2.2 ip_address=192.168.2.40 is one unknown " +"option." +msgstr "" + +#: ./doc/training-guides/module001-ch006-overview-horizon-cli.xml2493(para) +msgid "" +"How to find unknown options?The unknown options can be easily found by " +"watching the output of create_xxx or show_xxx command. For example, in the " +"port creation command, we see the fixed_ips fields, which can be used as an " +"unknown option." +msgstr "" + +#: ./doc/training-guides/module001-ch006-overview-horizon-cli.xml2500(guilabel) +msgid "Create and manage stacks" +msgstr "" + +#: ./doc/training-guides/module001-ch006-overview-horizon-cli.xml2501(para) +msgid "To create a stack from an example template file" +msgstr "" + +#: ./doc/training-guides/module001-ch006-overview-horizon-cli.xml2504(para) +msgid "" +"To create a stack, or template, from anexample template " +"file, run following command:" +msgstr "" + +#: ./doc/training-guides/module001-ch006-overview-horizon-cli.xml2510(para) +msgid "" +"$ heat stack-create mystack --template-" +"file=/path/to/heat/templates/WordPress_Single_Instance.template--" +"parameters=\"InstanceType=m1.large;DBUsername=wp;DBPassword=verybadpassword;KeyName=heat_key;LinuxDistribution=F17\"" +msgstr "" + +#: ./doc/training-guides/module001-ch006-overview-horizon-cli.xml2514(para) +msgid "" +"The --parameters values that you specify depend on which parameters are " +"defined in the template. If the template file is hosted on a website, you " +"can specify the URL with --template-url parameter instead of the --template-" +"file parameter." +msgstr "" + +#: ./doc/training-guides/module001-ch006-overview-horizon-cli.xml2521(para) +msgid "The command returns the following output:" +msgstr "" + +#: ./doc/training-guides/module001-ch006-overview-horizon-cli.xml2524(para) +msgid "" +"You can also use the stack-createcommand to validate a template file without" +" creating a stack from it." +msgstr "" + +#: ./doc/training-guides/module001-ch006-overview-horizon-cli.xml2528(para) +msgid "To do so, run the following command:" +msgstr "" + +#: ./doc/training-guides/module001-ch006-overview-horizon-cli.xml2531(para) +msgid "" +"$ heat stack-create mystack --template-" +"file=/path/to/heat/templates/WordPress_Single_Instance.template" +msgstr "" + +#: ./doc/training-guides/module001-ch006-overview-horizon-cli.xml2535(para) +msgid "If validation fails, the response returns an error message." +msgstr "" + +#: ./doc/training-guides/module001-ch006-overview-horizon-cli.xml2539(para) +msgid "To list stacks" +msgstr "" + +#: ./doc/training-guides/module001-ch006-overview-horizon-cli.xml2542(para) +msgid "" +"To see which stacks are visible to the current user, run the following " +"command:" +msgstr "" + +#: ./doc/training-guides/module001-ch006-overview-horizon-cli.xml2546(para) +msgid "$ heat stack-list" +msgstr "" + +#: ./doc/training-guides/module001-ch006-overview-horizon-cli.xml2549(para) +msgid "To view stack details" +msgstr "" + +#: ./doc/training-guides/module001-ch006-overview-horizon-cli.xml2550(para) +msgid "" +"To explore the state and history of a particular stack, you can run a number" +" of commands." +msgstr "" + +#: ./doc/training-guides/module001-ch006-overview-horizon-cli.xml2554(para) +msgid "To show the details of a stack, run the following command:" +msgstr "" + +#: ./doc/training-guides/module001-ch006-overview-horizon-cli.xml2558(para) +msgid "$ heat stack-show mystack" +msgstr "" + +#: ./doc/training-guides/module001-ch006-overview-horizon-cli.xml2561(para) +msgid "" +"A stack consists of a collection of resources. To list the resources, " +"including their status, in a stack, run the following command:" +msgstr "" + +#: ./doc/training-guides/module001-ch006-overview-horizon-cli.xml2566(para) +msgid "$ heat resource-list mystack" +msgstr "" + +#: ./doc/training-guides/module001-ch006-overview-horizon-cli.xml2569(para) +msgid "" +"To show the details for the specified resource in a stack, run the following" +" command:" +msgstr "" + +#: ./doc/training-guides/module001-ch006-overview-horizon-cli.xml2573(para) +msgid "$ heat resource-show mystack WikiDatabase" +msgstr "" + +#: ./doc/training-guides/module001-ch006-overview-horizon-cli.xml2576(para) +msgid "" +"Some resources have associated metadata which can change throughout the " +"life-cycle of a resource:" +msgstr "" + +#: ./doc/training-guides/module001-ch006-overview-horizon-cli.xml2580(para) +msgid "$ heat resource-metadata mystack WikiDatabase" +msgstr "" + +#: ./doc/training-guides/module001-ch006-overview-horizon-cli.xml2583(para) +msgid "" +"A series of events is generated during the life-cycle of a stack. This " +"command will display those events." +msgstr "" + +#: ./doc/training-guides/module001-ch006-overview-horizon-cli.xml2587(para) +msgid "$ heat event-list mystack" +msgstr "" + +#: ./doc/training-guides/module001-ch006-overview-horizon-cli.xml2590(para) +msgid "To show the details for a particular event, run the following command:" +msgstr "" + +#: ./doc/training-guides/module001-ch006-overview-horizon-cli.xml2594(para) +msgid "$ heat event-show WikiDatabase 1" +msgstr "" + +#: ./doc/training-guides/module001-ch006-overview-horizon-cli.xml2597(para) +msgid "To update a stack" +msgstr "" + +#: ./doc/training-guides/module001-ch006-overview-horizon-cli.xml2600(para) +msgid "" +"To update an existing stack from a modified template file, run a command " +"like the following command:" +msgstr "" + +#: ./doc/training-guides/module001-ch006-overview-horizon-cli.xml2604(para) +msgid "" +"$ heat stack-update mystack --template-" +"file=/path/to/heat/templates/WordPress_Single_Instance_v2.template " +"--parameters=\"InstanceType=m1.large;DBUsername=wp;DBPassword=verybadpassword;KeyName=heat_key;LinuxDistribution=F17\"" +msgstr "" + +#: ./doc/training-guides/module001-ch006-overview-horizon-cli.xml2609(para) +msgid "" +"Some resources are updated in-place, while others are replaced with new " +"resources." +msgstr "" + +#: ./doc/training-guides/bk001-ch009-associate-object-storage-node.xml8(title) +#: ./doc/training-guides/bk002-ch013-operator-object-storage-node.xml8(title) +msgid "Object Storage Node" +msgstr "" + +#: ./doc/training-guides/bk001-ch009-associate-object-storage-node.xml10(title) +msgid "Day 2, 11:30 to 12:30, 13:30 to 14:45" +msgstr "" + +#: ./doc/training-guides/bk001-ch009-associate-object-storage-node.xml14(title) +#: ./doc/training-guides/module003-ch001-intro-objstore.xml7(title) +msgid "Introduction to Object Storage" +msgstr "" + +#: ./doc/training-guides/bk001-ch009-associate-object-storage-node.xml21(title) +msgid "Features and Benefits" +msgstr "" + +#: ./doc/training-guides/bk001-ch009-associate-object-storage-node.xml30(title) +msgid "Object Storage CLI Commands" +msgstr "" + +#: ./doc/training-guides/bk001-ch009-associate-object-storage-node.xml37(title) +msgid "Manage Object Storage" +msgstr "" + +#: ./doc/training-guides/bk001-ch009-associate-object-storage-node.xml38(para) +msgid "Will be included from the swift developer reference" +msgstr "" + +#: ./doc/training-guides/card072-cinder-attach-volume.xml7(title) +msgid "Attaching volumes to an instance" +msgstr "" + +#: ./doc/training-guides/card126-horizon.xml7(title) +msgid "Install Horizon" +msgstr "" + +#. When image changes, this message will be marked fuzzy or untranslated for +#. you. +#. It doesn't matter what you translate it to: it's not used at all. +#: ./doc/training-guides/module001-ch004-openstack-architecture.xml26(None) +msgid "@@image: 'figures/image13.jpg'; md5=94fd9b9a3b33574d85bec7e1ea1675e2" +msgstr "" + +#. When image changes, this message will be marked fuzzy or untranslated for +#. you. +#. It doesn't matter what you translate it to: it's not used at all. +#: ./doc/training-guides/module001-ch004-openstack-architecture.xml70(None) +msgid "@@image: 'figures/image31.jpg'; md5=575b47442c4a8aac250a383f92a1bb46" +msgstr "" + +#. When image changes, this message will be marked fuzzy or untranslated for +#. you. +#. It doesn't matter what you translate it to: it's not used at all. +#: ./doc/training-guides/module001-ch004-openstack-architecture.xml100(None) +msgid "@@image: 'figures/image10.jpg'; md5=9471047adf0d93713be7f54b9db2b53c" +msgstr "" + +#: ./doc/training-guides/module001-ch004-openstack-architecture.xml7(title) +#: ./doc/training-guides/bk001-ch001-associate-getting-started.xml45(title) +msgid "OpenStack Architecture" +msgstr "" + +#: ./doc/training-guides/module001-ch004-openstack-architecture.xml8(guilabel) +msgid "Conceptual Architecture" +msgstr "" + +#: ./doc/training-guides/module001-ch004-openstack-architecture.xml9(para) +msgid "" +"The OpenStack project as a whole is designed to deliver a massively scalable" +" cloud operating system. To achieve this, each of the constituent services " +"are designed to work together to provide a complete Infrastructure as a " +"Service (IaaS). This integration is facilitated through public application " +"programming interfaces (APIs) that each service offers (and in turn can " +"consume). While these APIs allow each of the services to use another " +"service, it also allows an implementer to switch out any service as long as " +"they maintain the API. These are (mostly) the same APIs that are available " +"to end users of the cloud." +msgstr "" + +#: ./doc/training-guides/module001-ch004-openstack-architecture.xml20(para) +msgid "" +"Conceptually, you can picture the relationships between the services as so:" +msgstr "" + +#: ./doc/training-guides/module001-ch004-openstack-architecture.xml23(title) +msgid "Conceptual Diagram" +msgstr "" + +#: ./doc/training-guides/module001-ch004-openstack-architecture.xml32(para) +msgid "" +"Dashboard (\"Horizon\") provides a web front end to the other OpenStack " +"services" +msgstr "" + +#: ./doc/training-guides/module001-ch004-openstack-architecture.xml36(para) +msgid "" +"Compute (\"Nova\") stores and retrieves virtual disks (\"images\") and " +"associated metadata in Image (\"Glance\")" +msgstr "" + +#: ./doc/training-guides/module001-ch004-openstack-architecture.xml41(para) +msgid "Network (\"Quantum\") provides virtual networking for Compute." +msgstr "" + +#: ./doc/training-guides/module001-ch004-openstack-architecture.xml45(para) +msgid "Block Storage (\"Cinder\") provides storage volumes for Compute." +msgstr "" + +#: ./doc/training-guides/module001-ch004-openstack-architecture.xml49(para) +msgid "" +"Image (\"Glance\") can store the actual virtual disk files in the Object " +"Store(\"Swift\")" +msgstr "" + +#: ./doc/training-guides/module001-ch004-openstack-architecture.xml53(para) +msgid "All the services authenticate with Identity (\"Keystone\")" +msgstr "" + +#: ./doc/training-guides/module001-ch004-openstack-architecture.xml57(para) +msgid "" +"This is a stylized and simplified view of the architecture, assuming that " +"the implementer is using all of the services together in the most common " +"configuration. It also only shows the \"operator\" side of the cloud -- it " +"does not picture how consumers of the cloud may actually use it. For " +"example, many users will access object storage heavily (and directly)." +msgstr "" + +#: ./doc/training-guides/module001-ch004-openstack-architecture.xml63(guilabel) +msgid "Logical Architecture" +msgstr "" + +#: ./doc/training-guides/module001-ch004-openstack-architecture.xml64(para) +msgid "This picture is consistent with the conceptual architecture above:" +msgstr "" + +#: ./doc/training-guides/module001-ch004-openstack-architecture.xml67(title) +msgid "Logical Diagram" +msgstr "" + +#: ./doc/training-guides/module001-ch004-openstack-architecture.xml76(para) +msgid "" +"End users can interact through a common web interface (Horizon) or directly " +"to each service through their API" +msgstr "" + +#: ./doc/training-guides/module001-ch004-openstack-architecture.xml81(para) +msgid "" +"All services authenticate through a common source (facilitated through " +"keystone)" +msgstr "" + +#: ./doc/training-guides/module001-ch004-openstack-architecture.xml85(para) +msgid "" +"Individual services interact with each other through their public APIs " +"(except where privileged administrator commands are necessary)" +msgstr "" + +#: ./doc/training-guides/module001-ch004-openstack-architecture.xml90(para) +msgid "" +"In the sections below, we'll delve into the architecture for each of the " +"services." +msgstr "" + +#: ./doc/training-guides/module001-ch004-openstack-architecture.xml92(guilabel) +msgid "Dashboard" +msgstr "" + +#: ./doc/training-guides/module001-ch004-openstack-architecture.xml93(para) +msgid "" +"Horizon is a modular Django web application that provides an end user and " +"administrator interface to OpenStack services." +msgstr "" + +#: ./doc/training-guides/module001-ch004-openstack-architecture.xml97(title) +msgid "Horizon Dashboard" +msgstr "" + +#: ./doc/training-guides/module001-ch004-openstack-architecture.xml104(para) +msgid "As with most web applications, the architecture is fairly simple:" +msgstr "" + +#: ./doc/training-guides/module001-ch004-openstack-architecture.xml108(para) +msgid "" +"Horizon is usually deployed via mod_wsgi in Apache. The code itself is " +"separated into a reusable python module with most of the logic (interactions" +" with various OpenStack APIs) and presentation (to make it easily " +"customizable for different sites)." +msgstr "" + +#: ./doc/training-guides/module001-ch004-openstack-architecture.xml115(para) +msgid "" +"A database (configurable as to which one) which relies mostly on the other " +"services for data. It also stores very little data of its own." +msgstr "" + +#: ./doc/training-guides/module001-ch004-openstack-architecture.xml120(para) +msgid "" +"From a network architecture point of view, this service will need to be " +"customer accessible as well as be able to talk to each service's public " +"APIs. If you wish to use the administrator functionality (i.e. for other " +"services), it will also need connectivity to their Admin API endpoints " +"(which should be non-customer accessible)." +msgstr "" + +#: ./doc/training-guides/module001-ch004-openstack-architecture.xml126(guilabel) +msgid "Compute" +msgstr "" + +#: ./doc/training-guides/module001-ch004-openstack-architecture.xml127(para) +msgid "" +"Nova is the most complicated and distributed component of OpenStack. A large" +" number of processes cooperate to turn end user API requests into running " +"virtual machines. Below is a list of these processes and their functions:" +msgstr "" + +#: ./doc/training-guides/module001-ch004-openstack-architecture.xml133(para) +msgid "" +"nova-api accepts and responds to end user compute API calls. It supports " +"OpenStack Compute API, Amazon's EC2 API and a special Admin API (for " +"privileged users to perform administrative actions). It also initiates most " +"of the orchestration activities (such as running an instance) as well as " +"enforces some policy (mostly quota checks)." +msgstr "" + +#: ./doc/training-guides/module001-ch004-openstack-architecture.xml141(para) +msgid "" +"The nova-compute process is primarily a worker daemon that creates and " +"terminates virtual machine instances via hypervisor's APIs (XenAPI for " +"XenServer/XCP, libvirt for KVM or QEMU, VMwareAPI for VMware, etc.). The " +"process by which it does so is fairly complex but the basics are simple: " +"accept actions from the queue and then perform a series of system commands " +"(like launching a KVM instance) to carry them out while updating state in " +"the database." +msgstr "" + +#: ./doc/training-guides/module001-ch004-openstack-architecture.xml152(para) +msgid "" +"nova-volume manages the creation, attaching and detaching of z volumes to " +"compute instances (similar functionality to Amazon’s Elastic Block Storage)." +" It can use volumes from a variety of providers such as iSCSI or Rados Block" +" Device in Ceph. A new OpenStack project, Cinder, will eventually replace " +"nova-volume functionality. In the Folsom release, nova-volume and the Block " +"Storage service will have similar functionality." +msgstr "" + +#: ./doc/training-guides/module001-ch004-openstack-architecture.xml162(para) +msgid "" +"The nova-network worker daemon is very similar to nova-compute and nova-" +"volume. It accepts networking tasks from the queue and then performs tasks " +"to manipulate the network (such as setting up bridging interfaces or " +"changing iptables rules). This functionality is being migrated to Quantum, a" +" separate OpenStack service. In the Folsom release, much of the " +"functionality will be duplicated between nova-network and Quantum." +msgstr "" + +#: ./doc/training-guides/module001-ch004-openstack-architecture.xml172(para) +msgid "" +"The nova-schedule process is conceptually the simplest piece of code in " +"OpenStack Nova: it takes a virtual machine instance request from the queue " +"and determines where it should run (specifically, which compute server host " +"it should run on)." +msgstr "" + +#: ./doc/training-guides/module001-ch004-openstack-architecture.xml179(para) +msgid "" +"The queue provides a central hub for passing messages between daemons. This " +"is usually implemented with RabbitMQ today, but could be any AMPQ message " +"queue (such as Apache Qpid). New to the Folsom release is support for Zero " +"MQ." +msgstr "" + +#: ./doc/training-guides/module001-ch004-openstack-architecture.xml186(para) +msgid "" +"The SQL database stores most of the build-time and runtime state for a cloud" +" infrastructure. This includes the instance types that are available for " +"use, instances in use, networks available and projects. Theoretically, " +"OpenStack Nova can support any database supported by SQL-Alchemy but the " +"only databases currently being widely used are sqlite3 (only appropriate for" +" test and development work), MySQL and PostgreSQL." +msgstr "" + +#: ./doc/training-guides/module001-ch004-openstack-architecture.xml196(para) +msgid "" +"Nova also provides console services to allow end users to access their " +"virtual instance's console through a proxy. This involves several daemons " +"(nova-console, nova-novncproxy and nova-consoleauth)." +msgstr "" + +#: ./doc/training-guides/module001-ch004-openstack-architecture.xml202(para) +msgid "" +"Nova interacts with many other OpenStack services: Keystone for " +"authentication, Glance for images and Horizon for web interface. The Glance " +"interactions are central. The API process can upload and query Glance while " +"nova-compute will download images for use in launching images." +msgstr "" + +#: ./doc/training-guides/module001-ch004-openstack-architecture.xml207(guilabel) +msgid "Object Store" +msgstr "" + +#: ./doc/training-guides/module001-ch004-openstack-architecture.xml208(para) +msgid "" +"The swift architecture is very distributed to prevent any single point of " +"failure as well as to scale horizontally. It includes the following " +"components:" +msgstr "" + +#: ./doc/training-guides/module001-ch004-openstack-architecture.xml213(para) +msgid "" +"Proxy server (swift-proxy-server) accepts incoming requests via the " +"OpenStack Object API or just raw HTTP. It accepts files to upload, " +"modifications to metadata or container creation. In addition, it will also " +"serve files or container listing to web browsers. The proxy server may " +"utilize an optional cache (usually deployed with memcache) to improve " +"performance." +msgstr "" + +#: ./doc/training-guides/module001-ch004-openstack-architecture.xml222(para) +msgid "" +"Account servers manage accounts defined with the object storage service." +msgstr "" + +#: ./doc/training-guides/module001-ch004-openstack-architecture.xml226(para) +msgid "" +"Container servers manage a mapping of containers (i.e folders) within the " +"object store service." +msgstr "" + +#: ./doc/training-guides/module001-ch004-openstack-architecture.xml230(para) +msgid "" +"Object servers manage actual objects (i.e. files) on the storage nodes." +msgstr "" + +#: ./doc/training-guides/module001-ch004-openstack-architecture.xml234(para) +msgid "" +"There are also a number of periodic processes which run to perform " +"housekeeping tasks on the large data store. The most important of these is " +"the replication services, which ensures consistency and availability through" +" the cluster. Other periodic processes include auditors, updaters and " +"reapers." +msgstr "" + +#: ./doc/training-guides/module001-ch004-openstack-architecture.xml242(para) +msgid "" +"Authentication is handled through configurable WSGI middleware (which will " +"usually be Keystone)." +msgstr "" + +#: ./doc/training-guides/module001-ch004-openstack-architecture.xml244(guilabel) +msgid "Image Store" +msgstr "" + +#: ./doc/training-guides/module001-ch004-openstack-architecture.xml245(para) +msgid "" +"The Glance architecture has stayed relatively stable since the Cactus " +"release. The biggest architectural change has been the addition of " +"authentication, which was added in the Diablo release. Just as a quick " +"reminder, Glance has four main parts to it:" +msgstr "" + +#: ./doc/training-guides/module001-ch004-openstack-architecture.xml252(para) +msgid "" +"glance-api accepts Image API calls for image discovery, image retrieval and " +"image storage." +msgstr "" + +#: ./doc/training-guides/module001-ch004-openstack-architecture.xml256(para) +msgid "" +"glance-registry stores, processes and retrieves metadata about images (size," +" type, etc.)." +msgstr "" + +#: ./doc/training-guides/module001-ch004-openstack-architecture.xml260(para) +msgid "" +"A database to store the image metadata. Like Nova, you can choose your " +"database depending on your preference (but most people use MySQL or SQlite)." +msgstr "" + +#: ./doc/training-guides/module001-ch004-openstack-architecture.xml265(para) +msgid "" +"A storage repository for the actual image files. In the diagram above, Swift" +" is shown as the image repository, but this is configurable. In addition to " +"Swift, Glance supports normal filesystems, RADOS block devices, Amazon S3 " +"and HTTP. Be aware that some of these choices are limited to read-only " +"usage." +msgstr "" + +#: ./doc/training-guides/module001-ch004-openstack-architecture.xml273(para) +msgid "" +"There are also a number of periodic processes which run on Glance to support" +" caching. The most important of these is the replication services, which " +"ensures consistency and availability through the cluster. Other periodic " +"processes include auditors, updaters and reapers." +msgstr "" + +#: ./doc/training-guides/module001-ch004-openstack-architecture.xml278(para) +msgid "" +"As you can see from the diagram in the Conceptual Architecture section, " +"Glance serves a central role to the overall IaaS picture. It accepts API " +"requests for images (or image metadata) from end users or Nova components " +"and can store its disk files in the object storage service, Swift." +msgstr "" + +#: ./doc/training-guides/module001-ch004-openstack-architecture.xml284(guilabel) +msgid "Identity" +msgstr "" + +#: ./doc/training-guides/module001-ch004-openstack-architecture.xml285(para) +msgid "" +"Keystone provides a single point of integration for OpenStack policy, " +"catalog, token and authentication." +msgstr "" + +#: ./doc/training-guides/module001-ch004-openstack-architecture.xml289(para) +msgid "" +"keystone handles API requests as well as providing configurable catalog, " +"policy, token and identity services." +msgstr "" + +#: ./doc/training-guides/module001-ch004-openstack-architecture.xml294(para) +msgid "" +"Each Keystone function has a pluggable backend which allows different ways " +"to use the particular service. Most support standard backends like LDAP or " +"SQL, as well as Key Value Stores (KVS)." +msgstr "" + +#: ./doc/training-guides/module001-ch004-openstack-architecture.xml300(para) +msgid "" +"Most people will use this as a point of customization for their current " +"authentication services." +msgstr "" + +#: ./doc/training-guides/module001-ch004-openstack-architecture.xml302(guilabel) +msgid "Network" +msgstr "" + +#: ./doc/training-guides/module001-ch004-openstack-architecture.xml303(para) +msgid "" +"Quantum provides \"network connectivity as a service\" between interface " +"devices managed by other OpenStack services (most likely Nova). The service " +"works by allowing users to create their own networks and then attach " +"interfaces to them. Like many of the OpenStack services, Quantum is highly " +"configurable due to it's plug-in architecture. These plug-ins accommodate " +"different networking equipment and software. As such, the architecture and " +"deployment can vary dramatically. In the above architecture, a simple Linux " +"networking plug-in is shown." +msgstr "" + +#: ./doc/training-guides/module001-ch004-openstack-architecture.xml315(para) +msgid "" +"quantum-server accepts API requests and then routes them to the appropriate " +"quantum plugin for action." +msgstr "" + +#: ./doc/training-guides/module001-ch004-openstack-architecture.xml319(para) +msgid "" +"Quantum plugins and agents perform the actual actions such as plugging and " +"unplugging ports, creating networks or subnets and IP addressing. These " +"plugins and agents differ depending on the vendor and technologies used in " +"the particular cloud. Quantum ships with plugins and agents for: Cisco " +"virtual and physical switches, Nicira NVP product, NEC OpenFlow products, " +"Openvswitch, Linux bridging and the Ryu Network Operating System." +msgstr "" + +#: ./doc/training-guides/module001-ch004-openstack-architecture.xml329(para) +msgid "" +"The common agents are L3 (layer 3), DHCP (dynamic host IP addressing) and " +"the specific plug-in agent." +msgstr "" + +#: ./doc/training-guides/module001-ch004-openstack-architecture.xml333(para) +msgid "" +"Most Quantum installations will also make use of a messaging queue to route " +"information between the quantum-server and various agents as well as a " +"database to store networking state for particular plugins." +msgstr "" + +#: ./doc/training-guides/module001-ch004-openstack-architecture.xml339(para) +msgid "" +"Quantum will interact mainly with Nova, where it will provide networks and " +"connectivity for its instances." +msgstr "" + +#: ./doc/training-guides/module001-ch004-openstack-architecture.xml341(guilabel) +msgid "Block Storage" +msgstr "" + +#: ./doc/training-guides/module001-ch004-openstack-architecture.xml342(para) +msgid "" +"Cinder separates out the persistent block storage functionality that was " +"previously part of OpenStack Compute (in the form of nova-volume) into it's " +"own service. The OpenStack Block Storage API allows for manipulation of " +"volumes, volume types (similar to compute flavors) and volume snapshots." +msgstr "" + +#: ./doc/training-guides/module001-ch004-openstack-architecture.xml350(para) +msgid "" +"cinder-api accepts API requests and routes them to cinder-volume for action." +msgstr "" + +#: ./doc/training-guides/module001-ch004-openstack-architecture.xml354(para) +msgid "" +"cinder-volume acts upon the requests by reading or writing to the Cinder " +"database to maintain state, interacting with other processes (like cinder-" +"scheduler) through a message queue and directly upon block storage providing" +" hardware or software. It can interact with a variety of storage providers " +"through a driver architecture. Currently, there are drivers for IBM, " +"SolidFire, NetApp, Nexenta, Zadara, linux iSCSI and other storage providers." +msgstr "" + +#: ./doc/training-guides/module001-ch004-openstack-architecture.xml365(para) +msgid "" +"Much like nova-scheduler, the cinder-scheduler daemon picks the optimal " +"block storage provider node to create the volume on." +msgstr "" + +#: ./doc/training-guides/module001-ch004-openstack-architecture.xml370(para) +msgid "" +"Cinder deployments will also make use of a messaging queue to route " +"information between the cinder processes as well as a database to store " +"volume state." +msgstr "" + +#: ./doc/training-guides/module001-ch004-openstack-architecture.xml375(para) +msgid "" +"Like Quantum, Cinder will mainly interact with Nova, providing volumes for " +"its instances." +msgstr "" + +#. When image changes, this message will be marked fuzzy or untranslated for +#. you. +#. It doesn't matter what you translate it to: it's not used at all. +#: ./doc/training-guides/module001-ch009-vm-placement.xml18(None) +msgid "@@image: 'figures/image29.png'; md5=ce788bfd80e615104fa1e3257065824a" +msgstr "" + +#. When image changes, this message will be marked fuzzy or untranslated for +#. you. +#. It doesn't matter what you translate it to: it's not used at all. +#: ./doc/training-guides/module001-ch009-vm-placement.xml58(None) +msgid "@@image: 'figures/image27.png'; md5=c144af5cbdee1bd17a7bde0bea5b5fe7" +msgstr "" + +#. When image changes, this message will be marked fuzzy or untranslated for +#. you. +#. It doesn't matter what you translate it to: it's not used at all. +#: ./doc/training-guides/module001-ch009-vm-placement.xml198(None) +msgid "@@image: 'figures/image07.png'; md5=000eab4cf0deb1da2e692e023065a6ae" +msgstr "" + +#: ./doc/training-guides/module001-ch009-vm-placement.xml7(title) +#: ./doc/training-guides/bk001-ch005-associate-compute-node.xml14(title) +msgid "VM Placement" +msgstr "" + +#: ./doc/training-guides/module001-ch009-vm-placement.xml8(para) +msgid "" +"Compute uses the nova-scheduler service to determine how to dispatch compute" +" and volume requests. For example, the nova-scheduler service determines " +"which host a VM should launch on. The term host in the context of filters " +"means a physical node that has a nova-compute service running on it. You can" +" configure the scheduler through a variety of options." +msgstr "" + +#: ./doc/training-guides/module001-ch009-vm-placement.xml15(title) +#: ./doc/training-guides/lab003-compute-node.xml195(emphasis) +#: ./doc/training-guides/lab001-control-node.xml434(emphasis) +msgid "Nova" +msgstr "" + +#: ./doc/training-guides/module001-ch009-vm-placement.xml22(para) +msgid "" +"Just as shown by above figure, nova-scheduler interacts with other " +"components through queue and central database repo. For scheduling, queue is" +" the essential communications hub." +msgstr "" + +#: ./doc/training-guides/module001-ch009-vm-placement.xml25(para) +msgid "" +"All compute nodes (also known as hosts in terms of OpenStack) periodically " +"publish their status, resources available and hardware capabilities to nova-" +"scheduler through the queue. nova-scheduler then collects this data and uses" +" it to make decisions when a request comes in." +msgstr "" + +#: ./doc/training-guides/module001-ch009-vm-placement.xml30(para) +msgid "" +"By default, the compute scheduler is configured as a filter scheduler, as " +"described in the next section. In the default configuration, this scheduler " +"considers hosts that meet all the following criteria:" +msgstr "" + +#: ./doc/training-guides/module001-ch009-vm-placement.xml36(para) +msgid "Are in the requested availability zone (AvailabilityZoneFilter)." +msgstr "" + +#: ./doc/training-guides/module001-ch009-vm-placement.xml40(para) +msgid "Have sufficient RAM available (RamFilter)." +msgstr "" + +#: ./doc/training-guides/module001-ch009-vm-placement.xml43(para) +msgid "Are capable of servicing the request (ComputeFilter)." +msgstr "" + +#: ./doc/training-guides/module001-ch009-vm-placement.xml48(guilabel) +msgid "Filter Scheduler" +msgstr "" + +#: ./doc/training-guides/module001-ch009-vm-placement.xml49(para) +msgid "" +"The Filter Scheduler supports filtering and weighting to make informed " +"decisions on where a new instance should be created. This Scheduler supports" +" only working with Compute Nodes." +msgstr "" + +#: ./doc/training-guides/module001-ch009-vm-placement.xml53(guilabel) +#: ./doc/training-guides/module001-ch009-vm-placement.xml55(title) +msgid "Filtering" +msgstr "" + +#: ./doc/training-guides/module001-ch009-vm-placement.xml62(para) +msgid "" +"During its work, Filter Scheduler first makes a dictionary of unfiltered " +"hosts, then filters them using filter properties and finally chooses hosts " +"for the requested number of instances (each time it chooses the most weighed" +" host and appends it to the list of selected hosts)." +msgstr "" + +#: ./doc/training-guides/module001-ch009-vm-placement.xml67(para) +msgid "" +"If it turns up, that it can’t find candidates for the next instance, it " +"means that there are no more appropriate hosts where the instance could be " +"scheduled." +msgstr "" + +#: ./doc/training-guides/module001-ch009-vm-placement.xml70(para) +msgid "" +"If we speak about filtering and weighting, their work is quite flexible in " +"the Filter Scheduler. There are a lot of filtering strategies for the " +"Scheduler to support. Also you can even implement your own algorithm of " +"filtering." +msgstr "" + +#: ./doc/training-guides/module001-ch009-vm-placement.xml74(para) +msgid "" +"There are some standard filter classes to use (nova.scheduler.filters):" +msgstr "" + +#: ./doc/training-guides/module001-ch009-vm-placement.xml78(para) +msgid "" +"AllHostsFilter - frankly speaking, this filter does no operation. It passes " +"all the available hosts." +msgstr "" + +#: ./doc/training-guides/module001-ch009-vm-placement.xml82(para) +msgid "" +"ImagePropertiesFilter - filters hosts based on properties defined on the " +"instance’s image. It passes hosts that can support the specified image " +"properties contained in the instance." +msgstr "" + +#: ./doc/training-guides/module001-ch009-vm-placement.xml88(para) +msgid "" +"AvailabilityZoneFilter - filters hosts by availability zone. It passes hosts" +" matching the availability zone specified in the instance properties." +msgstr "" + +#: ./doc/training-guides/module001-ch009-vm-placement.xml93(para) +msgid "" +"ComputeCapabilitiesFilter - checks that the capabilities provided by the " +"host compute service satisfy any extra specifications associated with the " +"instance type. It passes hosts that can create the specified instance type." +msgstr "" + +#: ./doc/training-guides/module001-ch009-vm-placement.xml100(para) +msgid "" +"The extra specifications can have a scope at the beginning of the key string" +" of a key/value pair. The scope format is scope:key and can be nested, i.e. " +"key_string := scope:key_string. Example like capabilities:cpu_info: features" +" is valid scope format. A key string without any : is non-scope format. Each" +" filter defines its valid scope, and not all filters accept non-scope " +"format." +msgstr "" + +#: ./doc/training-guides/module001-ch009-vm-placement.xml109(para) +msgid "" +"The extra specifications can have an operator at the beginning of the value " +"string of a key/value pair. If there is no operator specified, then a " +"default operator of s== is used. Valid operators are:" +msgstr "" + +#: ./doc/training-guides/module001-ch009-vm-placement.xml115(para) +msgid "" +"* = (equal to or greater than as a number; same as vcpus case)* == (equal to" +" as a number)* != (not equal to as a number)* >= (greater than or equal " +"to as a number)* <= (less than or equal to as a number)* s== (equal to as" +" a string)* s!= (not equal to as a string)* s>= (greater than or equal to" +" as a string)* s> (greater than as a string)* s<= (less than or equal " +"to as a string)* s< (less than as a string)* <in> (substring)* " +"<or> (find one of these)Examples are: \">= 5\", \"s== 2.1.0\", " +"\"<in> gcc\", and \"<or> fpu <or> gpu\"" +msgstr "" + +#: ./doc/training-guides/module001-ch009-vm-placement.xml137(para) +msgid "" +"Here ram_allocation_ratio means the virtual RAM to physical RAM allocation " +"ratio (it is 1.5 by default). Really, nice and simple." +msgstr "" + +#: ./doc/training-guides/module001-ch009-vm-placement.xml140(para) +msgid "" +"Next standard filter to describe is AvailabilityZoneFilter and it isn’t " +"difficult too. This filter just looks at the availability zone of compute " +"node and availability zone from the properties of the request. Each compute " +"service has its own availability zone. So deployment engineers have an " +"option to run scheduler with availability zones support and can configure " +"availability zones on each compute host. This classes method host_passes " +"returns True if availability zone mentioned in request is the same on the " +"current compute host." +msgstr "" + +#: ./doc/training-guides/module001-ch009-vm-placement.xml150(para) +msgid "" +"The ImagePropertiesFilter filters hosts based on the architecture, " +"hypervisor type, and virtual machine mode specified in the instance. E.g., " +"an instance might require a host that supports the arm architecture on a " +"qemu compute host. The ImagePropertiesFilter will only pass hosts that can " +"satisfy this request. These instance properties are populated from " +"properties define on the instance’s image. E.g. an image can be decorated " +"with these properties using glance image-update img-uuid --property " +"architecture=arm --property hypervisor_type=qemu Only hosts that satisfy " +"these requirements will pass the ImagePropertiesFilter." +msgstr "" + +#: ./doc/training-guides/module001-ch009-vm-placement.xml161(para) +msgid "" +"ComputeCapabilitiesFilter checks if the host satisfies any extra_specs " +"specified on the instance type. The extra_specs can contain key/value pairs." +" The key for the filter is either non-scope format (i.e. no : contained), or" +" scope format in capabilities scope (i.e. capabilities:xxx:yyy). One example" +" of capabilities scope is capabilities:cpu_info:features, which will match " +"host’s cpu features capabilities. The ComputeCapabilitiesFilter will only " +"pass hosts whose capabilities satisfy the requested specifications. All " +"hosts are passed if no extra_specs are specified." +msgstr "" + +#: ./doc/training-guides/module001-ch009-vm-placement.xml171(para) +msgid "" +"ComputeFilter is quite simple and passes any host whose compute service is " +"enabled and operational." +msgstr "" + +#: ./doc/training-guides/module001-ch009-vm-placement.xml173(para) +msgid "" +"Now we are going to IsolatedHostsFilter. There can be some special hosts " +"reserved for specific images. These hosts are called isolated. So the images" +" to run on the isolated hosts are also called isolated. This Scheduler " +"checks if image_isolated flag named in instance specifications is the same " +"that the host has." +msgstr "" + +#: ./doc/training-guides/module001-ch009-vm-placement.xml180(guilabel) +#: ./doc/training-guides/module001-ch009-vm-placement.xml195(title) +msgid "Weights" +msgstr "" + +#: ./doc/training-guides/module001-ch009-vm-placement.xml181(para) +msgid "Filter Scheduler uses so-called weights during its work." +msgstr "" + +#: ./doc/training-guides/module001-ch009-vm-placement.xml183(para) +msgid "" +"The Filter Scheduler weights hosts based on the config option " +"scheduler_weight_classes, this defaults to " +"nova.scheduler.weights.all_weighers, which selects the only weigher " +"available – the RamWeigher. Hosts are then weighted and sorted with the " +"largest weight winning." +msgstr "" + +#: ./doc/training-guides/module001-ch009-vm-placement.xml188(para) +msgid "" +"Filter Scheduler finds local list of acceptable hosts by repeated filtering " +"and weighing. Each time it chooses a host, it virtually consumes resources " +"on it, so subsequent selections can adjust accordingly. It is useful if the " +"customer asks for the same large amount of instances, because weight is " +"computed for each instance requested." +msgstr "" + +#: ./doc/training-guides/module001-ch009-vm-placement.xml202(para) +msgid "" +"In the end Filter Scheduler sorts selected hosts by their weight and " +"provisions instances on them." +msgstr "" + +#: ./doc/training-guides/card039-nova.xml7(title) +#: ./doc/training-guides/lab003-compute-node.xml198(para) +msgid "Install Nova" +msgstr "" + +#: ./doc/training-guides/bk002-ch003-operator-getting-started-quiz.xml6(title) +#: ./doc/training-guides/bk001-ch002-associate-getting-started-quiz.xml6(title) +msgid "Getting Started Quiz" +msgstr "" + +#: ./doc/training-guides/bk002-ch003-operator-getting-started-quiz.xml8(title) +#: ./doc/training-guides/bk001-ch006-associate-compute-node-quiz.xml8(title) +msgid "Day 1, 16:40 to 17:00" +msgstr "" + +#: ./doc/training-guides/bk004-architect-training-guide.xml5(title) +msgid "Architect Training Guide" +msgstr "" + +#: ./doc/training-guides/bk004-architect-training-guide.xml7(title) +msgid "Architect Training Guide Coming Soon" +msgstr "" + +#: ./doc/training-guides/bk004-architect-training-guide.xml8(para) +msgid "TBD" +msgstr "" + +#: ./doc/training-guides/card047-install-nova-compute.xml7(title) +msgid "Installing Nova" +msgstr "" + +#: ./doc/training-guides/bk002-ch004-operator-controller-node.xml10(title) +msgid "Day 2 to 4, 09:00 to 11:00, 11:15 to 12:30" +msgstr "" + +#: ./doc/training-guides/bk002-ch004-operator-controller-node.xml14(title) +msgid "Review Associate Overview Horizon and OpenStack CLI" +msgstr "" + +#: ./doc/training-guides/bk002-ch004-operator-controller-node.xml21(title) +msgid "Review Associate Keystone Architecture" +msgstr "" + +#: ./doc/training-guides/bk002-ch004-operator-controller-node.xml28(title) +msgid "Review Associate OpenStack Messaging and Queues" +msgstr "" + +#: ./doc/training-guides/lab003-compute-node.xml70(para) +msgid "" +"Enable IP Forwarding by adding the following to " +"/etc/sysctl.conf" +msgstr "" + +#: ./doc/training-guides/lab003-compute-node.xml87(emphasis) +#: ./doc/training-guides/bk001-ch002-associate-getting-started-quiz.xml190(para) +msgid "KVM" +msgstr "" + +#: ./doc/training-guides/lab003-compute-node.xml90(para) +msgid "Install KVM:" +msgstr "" + +#: ./doc/training-guides/lab003-compute-node.xml96(para) +msgid "Edit /etc/libvirt/qemu.conf" +msgstr "" + +#: ./doc/training-guides/lab003-compute-node.xml105(para) +msgid "Delete Default Virtual Bridge" +msgstr "" + +#: ./doc/training-guides/lab003-compute-node.xml112(para) +msgid "" +"To Enable Live Migration Edit " +"/etc/libvirt/libvirtd.conf" +msgstr "" + +#: ./doc/training-guides/lab003-compute-node.xml118(para) +msgid "Edit /etc/init/libvirt-bin.conf" +msgstr "" + +#: ./doc/training-guides/lab003-compute-node.xml122(para) +msgid "Edit /etc/default/libvirt-bin" +msgstr "" + +#: ./doc/training-guides/lab003-compute-node.xml126(para) +msgid "Restart libvirt" +msgstr "" + +#: ./doc/training-guides/lab003-compute-node.xml133(emphasis) +msgid "Neutron and OVS" +msgstr "" + +#: ./doc/training-guides/lab003-compute-node.xml136(para) +#: ./doc/training-guides/card041-neutron.xml9(emphasis) +msgid "Install OpenVSwitch" +msgstr "" + +#: ./doc/training-guides/lab003-compute-node.xml140(para) +msgid "Create bridges:" +msgstr "" + +#: ./doc/training-guides/lab003-compute-node.xml147(para) +msgid "Install the Neutron openvswitch agent:" +msgstr "" + +#: ./doc/training-guides/lab003-compute-node.xml153(para) +msgid "" +"Edit " +"/etc/neutron/plugins/openvswitch/ovs_neutron_plugin.ini" +msgstr "" + +#: ./doc/training-guides/lab003-compute-node.xml174(para) +msgid "Edit /etc/neutron/neutron.conf" +msgstr "" + +#: ./doc/training-guides/lab003-compute-node.xml189(para) +msgid "Restart all the services:" +msgstr "" + +#: ./doc/training-guides/lab003-compute-node.xml205(para) +#: ./doc/training-guides/lab001-control-node.xml467(para) +msgid "Edit /etc/nova/api-paste.ini" +msgstr "" + +#: ./doc/training-guides/lab003-compute-node.xml219(para) +msgid "Edit /etc/nova/nova-compute.conf" +msgstr "" + +#: ./doc/training-guides/lab003-compute-node.xml228(para) +#: ./doc/training-guides/lab001-control-node.xml484(para) +msgid "Edit /etc/nova/nova.conf" +msgstr "" + +#: ./doc/training-guides/lab003-compute-node.xml278(para) +msgid "Restart Nova Services" +msgstr "" + +#: ./doc/training-guides/lab003-compute-node.xml282(para) +msgid "" +"List Nova Services (Check for the Smiley Faces to know if the services are " +"running):" +msgstr "" + +#: ./doc/training-guides/bk002-ch002-operator-getting-started-lab.xml6(title) +msgid "Getting Started Lab" +msgstr "" + +#: ./doc/training-guides/bk002-ch002-operator-getting-started-lab.xml8(title) +msgid "Day 1, 13:30 to 14:45, 15:00 to 17:00" +msgstr "" + +#: ./doc/training-guides/bk002-ch002-operator-getting-started-lab.xml12(title) +msgid "Getting the Tools and Accounts for Committing Code" +msgstr "" + +#: ./doc/training-guides/bk002-ch002-operator-getting-started-lab.xml26(title) +msgid "Submit a Documentation Bug" +msgstr "" + +#: ./doc/training-guides/bk002-ch002-operator-getting-started-lab.xml40(title) +msgid "Optional: Add to the Training Guide Documentation" +msgstr "" + +#. When image changes, this message will be marked fuzzy or untranslated for +#. you. +#. It doesn't matter what you translate it to: it's not used at all. +#: ./doc/training-guides/module003-ch003-obj-store-capabilities.xml89(None) +msgid "@@image: 'figures/image39.png'; md5=e26e374ace84070f5fed24e73adcd562" +msgstr "" + +#: ./doc/training-guides/module003-ch003-obj-store-capabilities.xml7(title) +#: ./doc/training-guides/bk002-ch013-operator-object-storage-node.xml32(title) +msgid "Object Storage Capabilities" +msgstr "" + +#: ./doc/training-guides/module003-ch003-obj-store-capabilities.xml40(guilabel) +msgid "Swift Characteristics" +msgstr "" + +#: ./doc/training-guides/module003-ch003-obj-store-capabilities.xml41(para) +msgid "The key characteristics of Swift include:" +msgstr "" + +#: ./doc/training-guides/module003-ch003-obj-store-capabilities.xml44(para) +msgid "All objects stored in Swift have a URL" +msgstr "" + +#: ./doc/training-guides/module003-ch003-obj-store-capabilities.xml47(para) +msgid "" +"All objects stored are replicated 3x in as-unique-as-possible zones, which " +"can be defined as a group of drives, a node, a rack etc." +msgstr "" + +#: ./doc/training-guides/module003-ch003-obj-store-capabilities.xml52(para) +msgid "All objects have their own metadata" +msgstr "" + +#: ./doc/training-guides/module003-ch003-obj-store-capabilities.xml55(para) +msgid "" +"Developers interact with the object storage system through a RESTful HTTP " +"API" +msgstr "" + +#: ./doc/training-guides/module003-ch003-obj-store-capabilities.xml59(para) +msgid "Object data can be located anywhere in the cluster" +msgstr "" + +#: ./doc/training-guides/module003-ch003-obj-store-capabilities.xml63(para) +msgid "" +"The cluster scales by adding additional nodes -- without sacrificing " +"performance, which allows a more cost-effective linear storage expansion vs." +" fork-lift upgrades" +msgstr "" + +#: ./doc/training-guides/module003-ch003-obj-store-capabilities.xml69(para) +msgid "Data doesn’t have to be migrated to an entirely new storage system" +msgstr "" + +#: ./doc/training-guides/module003-ch003-obj-store-capabilities.xml73(para) +msgid "New nodes can be added to the cluster without downtime" +msgstr "" + +#: ./doc/training-guides/module003-ch003-obj-store-capabilities.xml77(para) +msgid "Failed nodes and disks can be swapped out with no downtime" +msgstr "" + +#: ./doc/training-guides/module003-ch003-obj-store-capabilities.xml81(para) +msgid "Runs on industry-standard hardware, such as Dell, HP, Supermicro etc." +msgstr "" + +#: ./doc/training-guides/module003-ch003-obj-store-capabilities.xml93(para) +msgid "" +"Developers can either write directly to the Swift API or use one of the many" +" client libraries that exist for all popular programming languages, such as " +"Java, Python, Ruby and C#. Amazon S3 and RackSpace Cloud Files users should " +"feel very familiar with Swift. For users who have not used an object storage" +" system before, it will require a different approach and mindset than using " +"a traditional filesystem." +msgstr "" + +#: ./doc/training-guides/card045-configure-virtual-networking.xml7(title) +msgid "Configure Virtual Networking" +msgstr "" + +#: ./doc/training-guides/module003-ch001-intro-objstore.xml8(para) +msgid "" +"OpenStack Object Storage (code-named Swift) is open source software for " +"creating redundant, scalable data storage using clusters of standardized " +"servers to store petabytes of accessible data. It is a long-term storage " +"system for large amounts of static data that can be retrieved, leveraged, " +"and updated. Object Storage uses a distributed architecture with no central " +"point of control, providing greater scalability, redundancy and permanence. " +"Objects are written to multiple hardware devices, with the OpenStack " +"software responsible for ensuring data replication and integrity across the " +"cluster. Storage clusters scale horizontally by adding new nodes. Should a " +"node fail, OpenStack works to replicate its content from other active nodes." +" Because OpenStack uses software logic to ensure data replication and " +"distribution across different devices, inexpensive commodity hard drives and" +" servers can be used in lieu of more expensive equipment." +msgstr "" + +#: ./doc/training-guides/bk001-ch004-associate-controller-node-quiz.xml6(title) +#: ./doc/training-guides/bk002-ch006-operator-controller-node-quiz.xml6(title) +msgid "Controller Node Quiz" +msgstr "" + +#: ./doc/training-guides/bk001-ch004-associate-controller-node-quiz.xml8(title) +msgid "Day 1, 14:25 to 14:45" +msgstr "" + +#: ./doc/training-guides/bk001-ch004-associate-controller-node-quiz.xml10(title) +msgid "Associate Training Guide, Controller Node Quiz Questions" +msgstr "" + +#: ./doc/training-guides/bk001-ch004-associate-controller-node-quiz.xml15(title) +msgid "" +"When managing images for OpenStack you can complete all those tasks with the" +" OpenStack dashboard. (True or False)" +msgstr "" + +#: ./doc/training-guides/bk001-ch004-associate-controller-node-quiz.xml20(para) +#: ./doc/training-guides/bk001-ch004-associate-controller-node-quiz.xml36(para) +#: ./doc/training-guides/bk001-ch004-associate-controller-node-quiz.xml100(para) +#: ./doc/training-guides/bk001-ch004-associate-controller-node-quiz.xml116(para) +#: ./doc/training-guides/bk001-ch004-associate-controller-node-quiz.xml157(para) +#: ./doc/training-guides/bk001-ch004-associate-controller-node-quiz.xml172(para) +#: ./doc/training-guides/bk001-ch004-associate-controller-node-quiz.xml236(para) +#: ./doc/training-guides/bk001-ch004-associate-controller-node-quiz.xml299(para) +#: ./doc/training-guides/bk001-ch002-associate-getting-started-quiz.xml91(para) +#: ./doc/training-guides/bk001-ch002-associate-getting-started-quiz.xml106(para) +#: ./doc/training-guides/bk001-ch002-associate-getting-started-quiz.xml121(para) +#: ./doc/training-guides/bk001-ch002-associate-getting-started-quiz.xml160(para) +#: ./doc/training-guides/bk001-ch002-associate-getting-started-quiz.xml175(para) +msgid "True" +msgstr "" + +#: ./doc/training-guides/bk001-ch004-associate-controller-node-quiz.xml23(para) +#: ./doc/training-guides/bk001-ch004-associate-controller-node-quiz.xml39(para) +#: ./doc/training-guides/bk001-ch004-associate-controller-node-quiz.xml103(para) +#: ./doc/training-guides/bk001-ch004-associate-controller-node-quiz.xml119(para) +#: ./doc/training-guides/bk001-ch004-associate-controller-node-quiz.xml160(para) +#: ./doc/training-guides/bk001-ch004-associate-controller-node-quiz.xml175(para) +#: ./doc/training-guides/bk001-ch004-associate-controller-node-quiz.xml239(para) +#: ./doc/training-guides/bk001-ch004-associate-controller-node-quiz.xml302(para) +#: ./doc/training-guides/bk001-ch002-associate-getting-started-quiz.xml94(para) +#: ./doc/training-guides/bk001-ch002-associate-getting-started-quiz.xml109(para) +#: ./doc/training-guides/bk001-ch002-associate-getting-started-quiz.xml124(para) +#: ./doc/training-guides/bk001-ch002-associate-getting-started-quiz.xml163(para) +#: ./doc/training-guides/bk001-ch002-associate-getting-started-quiz.xml178(para) +msgid "False" +msgstr "" + +#: ./doc/training-guides/bk001-ch004-associate-controller-node-quiz.xml31(title) +msgid "" +"When setting up access and security, SSH credentials (keypairs) must be " +"injected into images after they are launched with a script. (True or False)" +msgstr "" + +#: ./doc/training-guides/bk001-ch004-associate-controller-node-quiz.xml47(title) +msgid "You can track monthly costs with metrics like: (choose all that apply)" +msgstr "" + +#: ./doc/training-guides/bk001-ch004-associate-controller-node-quiz.xml51(para) +msgid "VCPU" +msgstr "" + +#: ./doc/training-guides/bk001-ch004-associate-controller-node-quiz.xml54(para) +msgid "QoS" +msgstr "" + +#: ./doc/training-guides/bk001-ch004-associate-controller-node-quiz.xml57(para) +msgid "Uptime" +msgstr "" + +#: ./doc/training-guides/bk001-ch004-associate-controller-node-quiz.xml60(para) +msgid "Disks" +msgstr "" + +#: ./doc/training-guides/bk001-ch004-associate-controller-node-quiz.xml63(para) +msgid "RAM" +msgstr "" + +#: ./doc/training-guides/bk001-ch004-associate-controller-node-quiz.xml71(title) +msgid "" +"The following OpenStack command-line clients are available. (choose all that" +" apply)" +msgstr "" + +#: ./doc/training-guides/bk001-ch004-associate-controller-node-quiz.xml75(para) +msgid "python-keystoneclient" +msgstr "" + +#: ./doc/training-guides/bk001-ch004-associate-controller-node-quiz.xml78(para) +msgid "python-hypervisorclient" +msgstr "" + +#: ./doc/training-guides/bk001-ch004-associate-controller-node-quiz.xml81(para) +msgid "python-imageclient" +msgstr "" + +#: ./doc/training-guides/bk001-ch004-associate-controller-node-quiz.xml84(para) +msgid "python-cinderclient" +msgstr "" + +#: ./doc/training-guides/bk001-ch004-associate-controller-node-quiz.xml87(para) +msgid "python-novaclient" +msgstr "" + +#: ./doc/training-guides/bk001-ch004-associate-controller-node-quiz.xml95(title) +msgid "" +"To install a client package the following command syntax is used: $ sudo pip" +" install [--update] python-project client (True or False)" +msgstr "" + +#: ./doc/training-guides/bk001-ch004-associate-controller-node-quiz.xml111(title) +msgid "" +"To get a list of images in glance you can use the following command syntax: " +"$ glance image-list" +msgstr "" + +#: ./doc/training-guides/bk001-ch004-associate-controller-node-quiz.xml127(title) +msgid "" +"When troubleshooting image creation you will need to look at which of the " +"following log files for errors? (choose all that apply)" +msgstr "" + +#: ./doc/training-guides/bk001-ch004-associate-controller-node-quiz.xml132(para) +msgid "Examine the /var/log/nova-api.log" +msgstr "" + +#: ./doc/training-guides/bk001-ch004-associate-controller-node-quiz.xml135(para) +msgid "Examine the /var/log/nova-compute.log" +msgstr "" + +#: ./doc/training-guides/bk001-ch004-associate-controller-node-quiz.xml138(para) +msgid "Examine the /var/log/nova-error.log" +msgstr "" + +#: ./doc/training-guides/bk001-ch004-associate-controller-node-quiz.xml141(para) +msgid "Examine the /var/log/nova-status.log" +msgstr "" + +#: ./doc/training-guides/bk001-ch004-associate-controller-node-quiz.xml144(para) +msgid "Examine the /var/log/nova-image.log" +msgstr "" + +#: ./doc/training-guides/bk001-ch004-associate-controller-node-quiz.xml152(title) +msgid "" +"To generate a keypair use the following command syntax: $ nova keypair-add " +"--pub_key ~/.ssh/id_rsa.pub KEY_NAME" +msgstr "" + +#: ./doc/training-guides/bk001-ch004-associate-controller-node-quiz.xml168(title) +msgid "" +"When you want to launch an instance you can only do that from an image. " +"(True or False)" +msgstr "" + +#: ./doc/training-guides/bk001-ch004-associate-controller-node-quiz.xml183(title) +msgid "" +"An instance has a Private IP address which has the following properties? " +"(choose all that apply)" +msgstr "" + +#: ./doc/training-guides/bk001-ch004-associate-controller-node-quiz.xml187(para) +msgid "Used for communication between instances" +msgstr "" + +#: ./doc/training-guides/bk001-ch004-associate-controller-node-quiz.xml190(para) +#: ./doc/training-guides/bk001-ch002-associate-getting-started-quiz.xml193(para) +msgid "VMware vShpere 4.1, update 1 or greater" +msgstr "" + +#: ./doc/training-guides/bk001-ch004-associate-controller-node-quiz.xml193(para) +msgid "Stays the same, even after reboots" +msgstr "" + +#: ./doc/training-guides/bk001-ch004-associate-controller-node-quiz.xml196(para) +msgid "Stays allocated, even if you terminate the instance" +msgstr "" + +#: ./doc/training-guides/bk001-ch004-associate-controller-node-quiz.xml199(para) +msgid "" +"To see the status of the Private IP addresses you use the following command:" +" $ nova floating-ip-pool-list" +msgstr "" + +#: ./doc/training-guides/bk001-ch004-associate-controller-node-quiz.xml208(title) +msgid "" +"To start and stop and instance you can use the following options: (choose " +"all that apply)" +msgstr "" + +#: ./doc/training-guides/bk001-ch004-associate-controller-node-quiz.xml212(para) +msgid "Pause/Un-pause" +msgstr "" + +#: ./doc/training-guides/bk001-ch004-associate-controller-node-quiz.xml215(para) +msgid "Suspend/Resume" +msgstr "" + +#: ./doc/training-guides/bk001-ch004-associate-controller-node-quiz.xml218(para) +msgid "Reboot" +msgstr "" + +#: ./doc/training-guides/bk001-ch004-associate-controller-node-quiz.xml221(para) +msgid "Evacuate" +msgstr "" + +#: ./doc/training-guides/bk001-ch004-associate-controller-node-quiz.xml224(para) +msgid "Shutdown/Restart" +msgstr "" + +#: ./doc/training-guides/bk001-ch004-associate-controller-node-quiz.xml232(title) +msgid "" +"To create a network in OpenStack use the following command: $ neutron net-" +"create net1 (True or False)" +msgstr "" + +#: ./doc/training-guides/bk001-ch004-associate-controller-node-quiz.xml247(title) +msgid "" +"Identity Service provides the following functions: (choose all that apply)" +msgstr "" + +#: ./doc/training-guides/bk001-ch004-associate-controller-node-quiz.xml251(para) +msgid "Group policy objects" +msgstr "" + +#: ./doc/training-guides/bk001-ch004-associate-controller-node-quiz.xml254(para) +msgid "Message queuing" +msgstr "" + +#: ./doc/training-guides/bk001-ch004-associate-controller-node-quiz.xml257(para) +#: ./doc/training-guides/module001-ch007-keystone-arch.xml139(emphasis) +msgid "User management" +msgstr "" + +#: ./doc/training-guides/bk001-ch004-associate-controller-node-quiz.xml260(para) +msgid "Publishing" +msgstr "" + +#: ./doc/training-guides/bk001-ch004-associate-controller-node-quiz.xml263(para) +msgid "Service catalog" +msgstr "" + +#: ./doc/training-guides/bk001-ch004-associate-controller-node-quiz.xml271(title) +msgid "" +"The AMQP supports the following messaging bus options: (choose all that " +"apply)" +msgstr "" + +#: ./doc/training-guides/bk001-ch004-associate-controller-node-quiz.xml275(para) +msgid "ZeroMQ" +msgstr "" + +#: ./doc/training-guides/bk001-ch004-associate-controller-node-quiz.xml281(para) +msgid "Tibco Rendezvous" +msgstr "" + +#: ./doc/training-guides/bk001-ch004-associate-controller-node-quiz.xml284(para) +msgid "IBM WebSphere Message Broker" +msgstr "" + +#: ./doc/training-guides/bk001-ch004-associate-controller-node-quiz.xml287(para) +msgid "Qpid" +msgstr "" + +#: ./doc/training-guides/bk001-ch004-associate-controller-node-quiz.xml295(title) +msgid "" +"OpenStack uses the term tenant but in earlier versions it used the term " +"customer. (True or False)" +msgstr "" + +#: ./doc/training-guides/bk001-ch004-associate-controller-node-quiz.xml312(title) +msgid "Associate Training Guide, Controller Node Quiz Answers" +msgstr "" + +#: ./doc/training-guides/bk001-ch004-associate-controller-node-quiz.xml316(para) +msgid "" +"B (False) - you can manage images through only the glance and nova clients " +"or the Image Service and Compute APIs." +msgstr "" + +#: ./doc/training-guides/bk001-ch004-associate-controller-node-quiz.xml320(para) +msgid "" +"B (False) - Keypairs are SSH credentials that are injected into images when " +"they are launched. For this to work, the image must contain the cloud-init " +"package" +msgstr "" + +#: ./doc/training-guides/bk001-ch004-associate-controller-node-quiz.xml324(para) +msgid "" +"A, C, D, E - You can track costs per month by showing metrics like number of" +" VCPUs, disks, RAM, and uptime of all your instances" +msgstr "" + +#: ./doc/training-guides/bk001-ch004-associate-controller-node-quiz.xml328(para) +msgid "" +"A, D, E - The following command-line clients are available for the " +"respective services' APIs: cinder(python-cinderclient) Client for the Block " +"Storage Service API. Use to create and manage volumes. glance(python-" +"glanceclient) Client for the Image Service API. Use to create and manage " +"images. keystone(python-keystoneclient) Client for the Identity Service API." +" Use to create and manage users, tenants, roles, endpoints, and credentials." +" nova(python-novaclient) Client for the Compute API and its extensions. Use " +"to create and manage images, instances, and flavors. neutron(python-" +"neutronclient) Client for the Networking API. Use to configure networks for " +"guest servers. This client was previously known as neutron. swift(python-" +"swiftclient) Client for the Object Storage API. Use to gather statistics, " +"list items, update metadata, upload, download and delete files stored by the" +" object storage service. Provides access to a swift installation for ad hoc " +"processing. heat(python-heatclient)" +msgstr "" + +#: ./doc/training-guides/bk001-ch004-associate-controller-node-quiz.xml344(para) +#: ./doc/training-guides/bk001-ch004-associate-controller-node-quiz.xml347(para) +#: ./doc/training-guides/bk001-ch004-associate-controller-node-quiz.xml365(para) +msgid "A (True)" +msgstr "" + +#: ./doc/training-guides/bk001-ch004-associate-controller-node-quiz.xml350(para) +msgid "A, B" +msgstr "" + +#: ./doc/training-guides/bk001-ch004-associate-controller-node-quiz.xml353(para) +msgid "B (False) - $ nova keypair-add KEY_NAME > MY_KEY.pem" +msgstr "" + +#: ./doc/training-guides/bk001-ch004-associate-controller-node-quiz.xml356(para) +msgid "B (False) - you can launch and instance from an image or a volume" +msgstr "" + +#: ./doc/training-guides/bk001-ch004-associate-controller-node-quiz.xml359(para) +#: ./doc/training-guides/bk001-ch002-associate-getting-started-quiz.xml222(para) +msgid "A, B, C" +msgstr "" + +#: ./doc/training-guides/bk001-ch004-associate-controller-node-quiz.xml362(para) +msgid "A, B, C, D" +msgstr "" + +#: ./doc/training-guides/bk001-ch004-associate-controller-node-quiz.xml368(para) +msgid "C, E" +msgstr "" + +#: ./doc/training-guides/bk001-ch004-associate-controller-node-quiz.xml371(para) +msgid "A, B, E" +msgstr "" + +#: ./doc/training-guides/bk001-ch004-associate-controller-node-quiz.xml374(para) +msgid "" +"B (False) - Because the term project was used instead of tenant in earlier " +"versions of OpenStack Compute, some command-line tools use --project_id " +"instead of --tenant-id or --os-tenant-id to refer to a tenant ID." +msgstr "" + +#: ./doc/training-guides/bk002-ch007-operator-compute-node.xml10(title) +msgid "Days 5 to 6, 09:00 to 11:00, 11:15 to 12:30" +msgstr "" + +#: ./doc/training-guides/bk002-ch007-operator-compute-node.xml14(title) +msgid "Review Associate VM Placement" +msgstr "" + +#: ./doc/training-guides/bk002-ch007-operator-compute-node.xml21(title) +msgid "Review Associate VM Provisioning Indepth" +msgstr "" + +#: ./doc/training-guides/bk002-ch007-operator-compute-node.xml28(title) +msgid "Review Associate OpenStack Block Storage" +msgstr "" + +#: ./doc/training-guides/bk002-ch013-operator-object-storage-node.xml10(title) +msgid "Day 9, 09:00 to 11:00, 11:15 to 12:30" +msgstr "" + +#: ./doc/training-guides/bk002-ch013-operator-object-storage-node.xml14(title) +msgid "Review Associate Introduction to Object Storage" +msgstr "" + +#: ./doc/training-guides/bk002-ch013-operator-object-storage-node.xml21(title) +msgid "Review Associate Features and Benefits" +msgstr "" + +#: ./doc/training-guides/bk002-ch013-operator-object-storage-node.xml39(title) +msgid "Object Storage Building Blocks" +msgstr "" + +#: ./doc/training-guides/bk002-ch013-operator-object-storage-node.xml46(title) +msgid "Swift Ring Builder" +msgstr "" + +#: ./doc/training-guides/bk002-ch013-operator-object-storage-node.xml52(title) +msgid "More Swift Concepts" +msgstr "" + +#: ./doc/training-guides/bk002-ch013-operator-object-storage-node.xml66(title) +msgid "Swift Account Reaper" +msgstr "" + +#: ./doc/training-guides/bk002-ch013-operator-object-storage-node.xml73(title) +msgid "Swift Replication" +msgstr "" + +#: ./doc/training-guides/bk001-ch002-associate-getting-started-quiz.xml8(title) +msgid "Day 1, 10:40 to 11:00" +msgstr "" + +#: ./doc/training-guides/bk001-ch002-associate-getting-started-quiz.xml10(title) +msgid "Associate Training Guide, Getting Started Quiz Questions" +msgstr "" + +#: ./doc/training-guides/bk001-ch002-associate-getting-started-quiz.xml15(title) +msgid "" +"What are some of the compelling features of a cloud? (choose all that apply)" +msgstr "" + +#: ./doc/training-guides/bk001-ch002-associate-getting-started-quiz.xml19(para) +msgid "On-demand self-service" +msgstr "" + +#: ./doc/training-guides/bk001-ch002-associate-getting-started-quiz.xml22(para) +msgid "Resource pooling" +msgstr "" + +#: ./doc/training-guides/bk001-ch002-associate-getting-started-quiz.xml25(para) +msgid "Metered or measured service" +msgstr "" + +#: ./doc/training-guides/bk001-ch002-associate-getting-started-quiz.xml28(para) +msgid "Elasticity" +msgstr "" + +#: ./doc/training-guides/bk001-ch002-associate-getting-started-quiz.xml31(para) +msgid "Network access" +msgstr "" + +#: ./doc/training-guides/bk001-ch002-associate-getting-started-quiz.xml39(title) +msgid "" +"What three service models does cloud computing provide? (choose all that " +"apply)" +msgstr "" + +#: ./doc/training-guides/bk001-ch002-associate-getting-started-quiz.xml43(para) +msgid "Software as a Service (SaaS)" +msgstr "" + +#: ./doc/training-guides/bk001-ch002-associate-getting-started-quiz.xml46(para) +msgid "Applications as a Service (AaaS)" +msgstr "" + +#: ./doc/training-guides/bk001-ch002-associate-getting-started-quiz.xml49(para) +msgid "Hardware as a Service (HaaS)" +msgstr "" + +#: ./doc/training-guides/bk001-ch002-associate-getting-started-quiz.xml52(para) +msgid "Infrastructure as a Service (IaaS)" +msgstr "" + +#: ./doc/training-guides/bk001-ch002-associate-getting-started-quiz.xml55(para) +msgid "Platform as a Service (PaaS)" +msgstr "" + +#: ./doc/training-guides/bk001-ch002-associate-getting-started-quiz.xml63(title) +msgid "" +"What does the OpenStack project aim to deliver? (choose all that apply)" +msgstr "" + +#: ./doc/training-guides/bk001-ch002-associate-getting-started-quiz.xml67(para) +msgid "Simple to implement cloud solution" +msgstr "" + +#: ./doc/training-guides/bk001-ch002-associate-getting-started-quiz.xml70(para) +msgid "Massively scalable cloud solution" +msgstr "" + +#: ./doc/training-guides/bk001-ch002-associate-getting-started-quiz.xml73(para) +msgid "Feature rich cloud solution" +msgstr "" + +#: ./doc/training-guides/bk001-ch002-associate-getting-started-quiz.xml76(para) +msgid "Multi-vendor interoperability cloud solution" +msgstr "" + +#: ./doc/training-guides/bk001-ch002-associate-getting-started-quiz.xml79(para) +msgid "A new hypervisor cloud solution" +msgstr "" + +#: ./doc/training-guides/bk001-ch002-associate-getting-started-quiz.xml87(title) +msgid "" +"OpenStack code is freely available via the FreeBSD license. (True or False)" +msgstr "" + +#: ./doc/training-guides/bk001-ch002-associate-getting-started-quiz.xml102(title) +msgid "OpenStack Swift is Object Storage. (True or False)" +msgstr "" + +#: ./doc/training-guides/bk001-ch002-associate-getting-started-quiz.xml117(title) +msgid "OpenStack Networking is now called Quantum. (True or False)" +msgstr "" + +#: ./doc/training-guides/bk001-ch002-associate-getting-started-quiz.xml132(title) +msgid "" +"The Image service (Glance) in OpenStack provides: (Choose all that apply)" +msgstr "" + +#: ./doc/training-guides/bk001-ch002-associate-getting-started-quiz.xml136(para) +msgid "Base Templates which users can start new compute instances" +msgstr "" + +#: ./doc/training-guides/bk001-ch002-associate-getting-started-quiz.xml139(para) +msgid "Configuration of centralized policies across users and systems" +msgstr "" + +#: ./doc/training-guides/bk001-ch002-associate-getting-started-quiz.xml142(para) +msgid "" +"Available images for users to choose from or create their own from existing " +"servers" +msgstr "" + +#: ./doc/training-guides/bk001-ch002-associate-getting-started-quiz.xml145(para) +msgid "A central directory of users" +msgstr "" + +#: ./doc/training-guides/bk001-ch002-associate-getting-started-quiz.xml148(para) +msgid "Ability to take store snapshots in the Image Service for backup" +msgstr "" + +#: ./doc/training-guides/bk001-ch002-associate-getting-started-quiz.xml156(title) +msgid "" +"OpenStack APIs are compatible with Amazon EC2 and Amazon S3. (True or False)" +msgstr "" + +#: ./doc/training-guides/bk001-ch002-associate-getting-started-quiz.xml171(title) +msgid "Horizon is the OpenStack name for Compute. (True or False)" +msgstr "" + +#: ./doc/training-guides/bk001-ch002-associate-getting-started-quiz.xml186(title) +msgid "" +"Which Hypervisors can be supported in OpenStack? (Choose all that apply)" +msgstr "" + +#: ./doc/training-guides/bk001-ch002-associate-getting-started-quiz.xml196(para) +msgid "bhyve (BSD)" +msgstr "" + +#: ./doc/training-guides/bk001-ch002-associate-getting-started-quiz.xml199(para) +msgid "Xen" +msgstr "" + +#: ./doc/training-guides/bk001-ch002-associate-getting-started-quiz.xml202(para) +msgid "LXC" +msgstr "" + +#: ./doc/training-guides/bk001-ch002-associate-getting-started-quiz.xml212(title) +msgid "Associate Training Guide, Getting Started Quiz Answers" +msgstr "" + +#: ./doc/training-guides/bk001-ch002-associate-getting-started-quiz.xml216(para) +msgid "A, B, C, D, E" +msgstr "" + +#: ./doc/training-guides/bk001-ch002-associate-getting-started-quiz.xml219(para) +msgid "A, D, E" +msgstr "" + +#: ./doc/training-guides/bk001-ch002-associate-getting-started-quiz.xml225(para) +#: ./doc/training-guides/bk001-ch002-associate-getting-started-quiz.xml231(para) +#: ./doc/training-guides/bk001-ch002-associate-getting-started-quiz.xml240(para) +msgid "B" +msgstr "" + +#: ./doc/training-guides/bk001-ch002-associate-getting-started-quiz.xml228(para) +#: ./doc/training-guides/bk001-ch002-associate-getting-started-quiz.xml237(para) +msgid "A" +msgstr "" + +#: ./doc/training-guides/bk001-ch002-associate-getting-started-quiz.xml234(para) +msgid "A, C, E" +msgstr "" + +#: ./doc/training-guides/bk001-ch002-associate-getting-started-quiz.xml243(para) +msgid "A, B, D, E" +msgstr "" + +#. When image changes, this message will be marked fuzzy or untranslated for +#. you. +#. It doesn't matter what you translate it to: it's not used at all. +#: ./doc/training-guides/module001-ch007-keystone-arch.xml131(None) +msgid "@@image: 'figures/image19.png'; md5=60e446d2b0f887288e414af8dd338778" +msgstr "" + +#. More Content To be Added ... +#.
+#. Identity Service Concepts +#: ./doc/training-guides/module001-ch007-keystone-arch.xml10(para) +msgid "The Identity service performs these functions:" +msgstr "" + +#: ./doc/training-guides/module001-ch007-keystone-arch.xml14(para) +msgid "User management. Tracks users and their permissions." +msgstr "" + +#: ./doc/training-guides/module001-ch007-keystone-arch.xml18(para) +msgid "" +"Service catalog. Provides a catalog of available services with their API " +"endpoints." +msgstr "" + +#: ./doc/training-guides/module001-ch007-keystone-arch.xml22(para) +msgid "" +"To understand the Identity Service, you must understand these concepts:" +msgstr "" + +#: ./doc/training-guides/module001-ch007-keystone-arch.xml25(emphasis) +msgid "User" +msgstr "" + +#: ./doc/training-guides/module001-ch007-keystone-arch.xml27(para) +msgid "" +"Digital representation of a person, system, or service who uses OpenStack " +"cloud services. Identity authentication services will validate that incoming" +" request are being made by the user who claims to be making the call. Users " +"have a login and may be assigned tokens to access resources. Users may be " +"directly assigned to a particular tenant and behave as if they are contained" +" in that tenant." +msgstr "" + +#: ./doc/training-guides/module001-ch007-keystone-arch.xml38(emphasis) +msgid "Credentials" +msgstr "" + +#: ./doc/training-guides/module001-ch007-keystone-arch.xml40(para) +msgid "" +"Data that is known only by a user that proves who they are. In the Identity " +"Service, examples are:" +msgstr "" + +#: ./doc/training-guides/module001-ch007-keystone-arch.xml44(para) +msgid "Username and password" +msgstr "" + +#: ./doc/training-guides/module001-ch007-keystone-arch.xml47(para) +msgid "Username and API key" +msgstr "" + +#: ./doc/training-guides/module001-ch007-keystone-arch.xml50(para) +msgid "An authentication token provided by the Identity Service" +msgstr "" + +#: ./doc/training-guides/module001-ch007-keystone-arch.xml57(emphasis) +msgid "Authentication" +msgstr "" + +#: ./doc/training-guides/module001-ch007-keystone-arch.xml59(para) +msgid "" +"The act of confirming the identity of a user. The Identity Service confirms " +"an incoming request by validating a set of credentials supplied by the user." +" These credentials are initially a username and password or a username and " +"API key. In response to these credentials, the Identity Service issues the " +"user an authentication token, which the user provides in subsequent " +"requests." +msgstr "" + +#: ./doc/training-guides/module001-ch007-keystone-arch.xml71(emphasis) +msgid "Token" +msgstr "" + +#: ./doc/training-guides/module001-ch007-keystone-arch.xml73(para) +msgid "" +"An arbitrary bit of text that is used to access resources. Each token has a " +"scope which describes which resources are accessible with it. A token may be" +" revoked at anytime and is valid for a finite duration." +msgstr "" + +#: ./doc/training-guides/module001-ch007-keystone-arch.xml77(para) +msgid "" +"While the Identity Service supports token-based authentication in this " +"release, the intention is for it to support additional protocols in the " +"future. The intent is for it to be an integration service foremost, and not " +"aspire to be a full-fledged identity store and management solution." +msgstr "" + +#: ./doc/training-guides/module001-ch007-keystone-arch.xml86(emphasis) +msgid "Tenant" +msgstr "" + +#: ./doc/training-guides/module001-ch007-keystone-arch.xml88(para) +msgid "" +"A container used to group or isolate resources and/or identity objects. " +"Depending on the service operator, a tenant may map to a customer, account, " +"organization, or project." +msgstr "" + +#: ./doc/training-guides/module001-ch007-keystone-arch.xml96(emphasis) +msgid "Service" +msgstr "" + +#: ./doc/training-guides/module001-ch007-keystone-arch.xml98(para) +msgid "" +"An OpenStack service, such as Compute (Nova), Object Storage (Swift), or " +"Image Service (Glance). Provides one or more endpoints through which users " +"can access resources and perform operations." +msgstr "" + +#: ./doc/training-guides/module001-ch007-keystone-arch.xml105(emphasis) +msgid "Endpoint" +msgstr "" + +#: ./doc/training-guides/module001-ch007-keystone-arch.xml107(para) +msgid "" +"An network-accessible address, usually described by URL, from where you " +"access a service. If using an extension for templates, you can create an " +"endpoint template, which represents the templates of all the consumable " +"services that are available across the regions." +msgstr "" + +#: ./doc/training-guides/module001-ch007-keystone-arch.xml116(emphasis) +msgid "Role" +msgstr "" + +#: ./doc/training-guides/module001-ch007-keystone-arch.xml118(para) +msgid "" +"A personality that a user assumes that enables them to perform a specific " +"set of operations. A role includes a set of rights and privileges. A user " +"assuming that role inherits those rights and privileges." +msgstr "" + +#: ./doc/training-guides/module001-ch007-keystone-arch.xml122(para) +msgid "" +"In the Identity Service, a token that is issued to a user includes the list " +"of roles that user can assume. Services that are being called by that user " +"determine how they interpret the set of roles a user has and which " +"operations or resources each role grants access to." +msgstr "" + +#: ./doc/training-guides/module001-ch007-keystone-arch.xml128(title) +msgid "Keystone Authentication" +msgstr "" + +#: ./doc/training-guides/module001-ch007-keystone-arch.xml141(para) +msgid "The main components of Identity user management are:" +msgstr "" + +#: ./doc/training-guides/module001-ch007-keystone-arch.xml145(para) +msgid "Users" +msgstr "" + +#: ./doc/training-guides/module001-ch007-keystone-arch.xml148(para) +msgid "Tenants" +msgstr "" + +#: ./doc/training-guides/module001-ch007-keystone-arch.xml151(para) +msgid "Roles" +msgstr "" + +#: ./doc/training-guides/module001-ch007-keystone-arch.xml154(para) +msgid "" +"A user represents a human user, and has associated information such as " +"username, password and email. This example creates a user named \"alice\":" +msgstr "" + +#: ./doc/training-guides/module001-ch007-keystone-arch.xml158(para) +msgid "" +"A tenant can be a project, group, or organization. Whenever you make " +"requests to OpenStack services, you must specify a tenant. For example, if " +"you query the Compute service for a list of running instances, you get a " +"list of all running instances for the specified tenant. This example creates" +" a tenant named \"acme\":" +msgstr "" + +#: ./doc/training-guides/module001-ch007-keystone-arch.xml165(para) +msgid "" +"A role captures what operations a user is permitted to perform in a given " +"tenant. This example creates a role named \"compute-user\":" +msgstr "" + +#: ./doc/training-guides/module001-ch007-keystone-arch.xml169(para) +msgid "" +"The Identity service associates a user with a tenant and a role. To continue" +" with our previous examples, we may wish to assign the \"alice\" user the " +"\"compute-user\" role in the \"acme\" tenant:" +msgstr "" + +#: ./doc/training-guides/module001-ch007-keystone-arch.xml175(para) +msgid "" +"A user can be assigned different roles in different tenants. For example, " +"Alice may also have the \"admin\" role in the \"Cyberdyne\" tenant. A user " +"can also be assigned multiple roles in the same tenant." +msgstr "" + +#: ./doc/training-guides/module001-ch007-keystone-arch.xml179(para) +msgid "" +"The /etc/[SERVICE_CODENAME]/policy.json file controls " +"what users are allowed to do for a given service. For example, " +"/etc/nova/policy.json specifies the access policy for " +"the Compute service, /etc/glance/policy.json specifies " +"the access policy for the Image service, and " +"/etc/keystone/policy.json specifies the access policy " +"for the Identity service." +msgstr "" + +#: ./doc/training-guides/module001-ch007-keystone-arch.xml189(para) +msgid "" +"The default policy.json files in the Compute, Identity, and Image service " +"recognize only the admin role: all operations that do not require the admin " +"role will be accessible by any user that has any role in a tenant." +msgstr "" + +#: ./doc/training-guides/module001-ch007-keystone-arch.xml194(para) +msgid "" +"If you wish to restrict users from performing operations in, say, the " +"Compute service, you need to create a role in the Identity service and then " +"modify /etc/nova/policy.json so that this role is " +"required for Compute operations." +msgstr "" + +#: ./doc/training-guides/module001-ch007-keystone-arch.xml199(para) +msgid "" +"For example, this line in /etc/nova/policy.json " +"specifies that there are no restrictions on which users can create volumes: " +"if the user has any role in a tenant, they will be able to create volumes in" +" that tenant." +msgstr "" + +#: ./doc/training-guides/module001-ch007-keystone-arch.xml207(emphasis) +msgid "Service Management" +msgstr "" + +#: ./doc/training-guides/module001-ch007-keystone-arch.xml210(para) +msgid "" +"The Identity Service provides the following service management functions:" +msgstr "" + +#: ./doc/training-guides/module001-ch007-keystone-arch.xml214(para) +msgid "Services" +msgstr "" + +#: ./doc/training-guides/module001-ch007-keystone-arch.xml217(para) +msgid "Endpoints" +msgstr "" + +#: ./doc/training-guides/module001-ch007-keystone-arch.xml220(para) +msgid "" +"The Identity Service also maintains a user that corresponds to each service," +" such as a user named nova, for the Compute service) and a special service " +"tenant, which is called service." +msgstr "" + +#: ./doc/training-guides/module001-ch007-keystone-arch.xml224(para) +msgid "" +"The commands for creating services and endpoints are described in a later " +"section." +msgstr "" + +#: ./doc/training-guides/card041-neutron.xml7(title) +#: ./doc/training-guides/card041-neutron.xml16(emphasis) +msgid "Install Neutron" +msgstr "" + +#: ./doc/training-guides/card041-neutron.xml10(para) +msgid "" +"OpenVSwitch is one of many options, but for now we will stick with OVS." +msgstr "" + +#: ./doc/training-guides/bk001-ch011-associate-assessment.xml6(title) +msgid "Assessment" +msgstr "" + +#: ./doc/training-guides/bk001-ch011-associate-assessment.xml8(title) +msgid "Day 2, 15:00 to 16:00" +msgstr "" + +#: ./doc/training-guides/bk001-ch011-associate-assessment.xml12(title) +msgid "Questions" +msgstr "" + +#: ./doc/training-guides/bk001-ch011-associate-assessment.xml14(caption) +msgid "Assessment Question 1" +msgstr "" + +#: ./doc/training-guides/bk001-ch011-associate-assessment.xml19(th) +#: ./doc/training-guides/bk001-ch011-associate-assessment.xml40(th) +msgid "Task" +msgstr "" + +#: ./doc/training-guides/bk001-ch011-associate-assessment.xml20(th) +#: ./doc/training-guides/bk001-ch011-associate-assessment.xml41(th) +msgid "Completed?" +msgstr "" + +#: ./doc/training-guides/bk001-ch011-associate-assessment.xml26(para) +#: ./doc/training-guides/bk001-ch011-associate-assessment.xml47(para) +msgid "Configure a ...." +msgstr "" + +#: ./doc/training-guides/bk001-ch011-associate-assessment.xml35(caption) +msgid "Assessment Question 2" +msgstr "" + +#. When image changes, this message will be marked fuzzy or untranslated for +#. you. +#. It doesn't matter what you translate it to: it's not used at all. +#: ./doc/training-guides/module001-ch010-vm-provisioning-indepth.xml118(None) +msgid "@@image: 'figures/image02.png'; md5=58686bf772bae30c415ec79e1dcf50ff" +msgstr "" + +#: ./doc/training-guides/module001-ch010-vm-provisioning-indepth.xml7(title) +#: ./doc/training-guides/bk001-ch005-associate-compute-node.xml21(title) +msgid "VM Provisioning Indepth" +msgstr "" + +#: ./doc/training-guides/module001-ch010-vm-provisioning-indepth.xml9(para) +msgid "The request flow for provisioning an Instance goes like this:" +msgstr "" + +#: ./doc/training-guides/module001-ch010-vm-provisioning-indepth.xml13(para) +msgid "" +"Dashboard or CLI gets the user credentials authenticates with Keystone via " +"REST api." +msgstr "" + +#: ./doc/training-guides/module001-ch010-vm-provisioning-indepth.xml17(para) +msgid "" +"Keystone authenticate the credentials and generate & send back auth-" +"token which will be used for sending request to other Components through " +"REST-call." +msgstr "" + +#: ./doc/training-guides/module001-ch010-vm-provisioning-indepth.xml22(para) +msgid "" +"Dashboard or CLI convert the new instance request specified in ‘launch " +"instance’ or ‘nova-boot’ form to REST API request and send it to nova-api." +msgstr "" + +#: ./doc/training-guides/module001-ch010-vm-provisioning-indepth.xml27(para) +msgid "" +"nova-api receive the request and sends the request for validation auth-token" +" and access permission to keystone." +msgstr "" + +#: ./doc/training-guides/module001-ch010-vm-provisioning-indepth.xml32(para) +msgid "" +"Keystone validates the token and sends updated auth headers with roles and " +"permissions." +msgstr "" + +#: ./doc/training-guides/module001-ch010-vm-provisioning-indepth.xml36(para) +msgid "nova-api interacts with nova-database." +msgstr "" + +#: ./doc/training-guides/module001-ch010-vm-provisioning-indepth.xml39(para) +msgid "Creates initial db entry for new instance." +msgstr "" + +#: ./doc/training-guides/module001-ch010-vm-provisioning-indepth.xml42(para) +msgid "" +"nova-api sends the rpc.call request to nova-scheduler excepting to get " +"updated instance entry with host ID specified." +msgstr "" + +#: ./doc/training-guides/module001-ch010-vm-provisioning-indepth.xml47(para) +msgid "nova-scheduler picks the request from the queue." +msgstr "" + +#: ./doc/training-guides/module001-ch010-vm-provisioning-indepth.xml50(para) +msgid "" +"nova-scheduler interacts with nova-database to find an appropriate host via " +"filtering and weighing." +msgstr "" + +#: ./doc/training-guides/module001-ch010-vm-provisioning-indepth.xml54(para) +msgid "" +"Returns the updated instance entry with appropriate host ID after filtering " +"and weighing." +msgstr "" + +#: ./doc/training-guides/module001-ch010-vm-provisioning-indepth.xml56(para) +msgid "" +"nova-scheduler sends the rpc.cast request to nova-compute for ‘launching " +"instance’ on appropriate host ." +msgstr "" + +#: ./doc/training-guides/module001-ch010-vm-provisioning-indepth.xml60(para) +msgid "nova-compute picks the request from the queue." +msgstr "" + +#: ./doc/training-guides/module001-ch010-vm-provisioning-indepth.xml63(para) +msgid "" +"nova-compute send the rpc.call request to nova-conductor to fetch the " +"instance information such as host ID and flavor( Ram , CPU ,Disk)." +msgstr "" + +#: ./doc/training-guides/module001-ch010-vm-provisioning-indepth.xml68(para) +msgid "nova-conductor picks the request from the queue." +msgstr "" + +#: ./doc/training-guides/module001-ch010-vm-provisioning-indepth.xml71(para) +msgid "nova-conductor interacts with nova-database." +msgstr "" + +#: ./doc/training-guides/module001-ch010-vm-provisioning-indepth.xml74(para) +msgid "Return the instance information." +msgstr "" + +#: ./doc/training-guides/module001-ch010-vm-provisioning-indepth.xml75(para) +msgid "nova-compute picks the instance information from the queue." +msgstr "" + +#: ./doc/training-guides/module001-ch010-vm-provisioning-indepth.xml79(para) +msgid "" +"nova-compute does the REST call by passing auth-token to glance-api to get " +"the Image URI by Image ID from glance and upload image from image storage." +msgstr "" + +#: ./doc/training-guides/module001-ch010-vm-provisioning-indepth.xml84(para) +msgid "glance-api validates the auth-token with keystone." +msgstr "" + +#: ./doc/training-guides/module001-ch010-vm-provisioning-indepth.xml87(para) +msgid "nova-compute get the image metadata." +msgstr "" + +#: ./doc/training-guides/module001-ch010-vm-provisioning-indepth.xml88(para) +msgid "" +"nova-compute does the REST-call by passing auth-token to Network API to " +"allocate and configure the network such that instance gets the IP address." +msgstr "" + +#: ./doc/training-guides/module001-ch010-vm-provisioning-indepth.xml93(para) +msgid "quantum-server validates the auth-token with keystone." +msgstr "" + +#: ./doc/training-guides/module001-ch010-vm-provisioning-indepth.xml97(para) +msgid "nova-compute get the network info." +msgstr "" + +#: ./doc/training-guides/module001-ch010-vm-provisioning-indepth.xml100(para) +msgid "" +"nova-compute does the REST call by passing auth-token to Volume API to " +"attach volumes to instance." +msgstr "" + +#: ./doc/training-guides/module001-ch010-vm-provisioning-indepth.xml104(para) +msgid "cinder-api validates the auth-token with keystone." +msgstr "" + +#: ./doc/training-guides/module001-ch010-vm-provisioning-indepth.xml107(para) +msgid "nova-compute gets the block storage info." +msgstr "" + +#: ./doc/training-guides/module001-ch010-vm-provisioning-indepth.xml110(para) +msgid "" +"nova-compute generates data for hypervisor driver and executes request on " +"Hypervisor( via libvirt or api)." +msgstr "" + +#: ./doc/training-guides/module001-ch010-vm-provisioning-indepth.xml115(title) +msgid "Nova VM Provisioning" +msgstr "" + +#: ./doc/training-guides/bk002-ch011-operator-network-node-lab.xml6(title) +msgid "Network Node Lab" +msgstr "" + +#: ./doc/training-guides/bk002-ch011-operator-network-node-lab.xml8(title) +msgid "Days 7 to 8, 13:30 to 14:45, 15:00 to 17:00" +msgstr "" + +#: ./doc/training-guides/bk002-ch001-operator-getting-started.xml6(title) +#: ./doc/training-guides/bk001-ch001-associate-getting-started.xml6(title) +#: ./doc/training-guides/lab000-virtualbox-basics.xml8(guilabel) +msgid "Getting Started" +msgstr "" + +#: ./doc/training-guides/bk002-ch001-operator-getting-started.xml8(title) +msgid "Day 1, 09:00 to 11:00, 11:15 to 12:30" +msgstr "" + +#: ./doc/training-guides/bk002-ch001-operator-getting-started.xml13(para) +msgid "" +"Training would take 2.5 months self paced, (5) 2 week periods with a user " +"group meeting, or 40 hours instructor led with 40 hours of self paced lab " +"time." +msgstr "" + +#: ./doc/training-guides/bk002-ch001-operator-getting-started.xml15(para) +#: ./doc/training-guides/bk001-ch001-associate-getting-started.xml15(para) +msgid "Prerequisites" +msgstr "" + +#: ./doc/training-guides/bk002-ch001-operator-getting-started.xml17(para) +msgid "Associate guide training" +msgstr "" + +#: ./doc/training-guides/bk002-ch001-operator-getting-started.xml18(para) +msgid "Associate guide virtualbox scripted install completed and running" +msgstr "" + +#: ./doc/training-guides/bk002-ch001-operator-getting-started.xml22(title) +msgid "Review Associate Introduction" +msgstr "" + +#: ./doc/training-guides/bk002-ch001-operator-getting-started.xml29(title) +msgid "Review Associate Brief Overview" +msgstr "" + +#: ./doc/training-guides/bk002-ch001-operator-getting-started.xml36(title) +msgid "Review Associate Core Projects" +msgstr "" + +#: ./doc/training-guides/bk002-ch001-operator-getting-started.xml43(title) +msgid "Review Associate OpenStack Architecture" +msgstr "" + +#: ./doc/training-guides/bk002-ch001-operator-getting-started.xml50(title) +msgid "Review Associate Virtual Machine Provisioning Walk-Through" +msgstr "" + +#: ./doc/training-guides/card008.xml7(title) +msgid "Understanding the RefStack Architecture" +msgstr "" + +#: ./doc/training-guides/module002-ch002-openstack-networking-concepts.xml7(title) +#: ./doc/training-guides/bk001-ch007-associate-network-node.xml21(title) +msgid "OpenStack Networking Concepts" +msgstr "" + +#: ./doc/training-guides/module002-ch002-openstack-networking-concepts.xml8(emphasis) +msgid "Network Types" +msgstr "" + +#: ./doc/training-guides/module002-ch002-openstack-networking-concepts.xml9(para) +msgid "" +"The OpenStack Networking configuration provided by the Rackspace Private " +"Cloud cookbooks allows you to choose between VLAN or GRE isolated networks, " +"both provider- and tenant-specific. From the provider side, an administrator" +" can also create a flat network." +msgstr "" + +#: ./doc/training-guides/module002-ch002-openstack-networking-concepts.xml14(para) +msgid "" +"The type of network that is used for private tenant networks is determined " +"by the network_type attribute, which can be edited in the Chef " +"override_attributes. This attribute sets both the default provider network " +"type and the only type of network that tenants are able to create. " +"Administrators can always create flat and VLAN networks. GRE networks of any" +" type require the network_type to be set to gre." +msgstr "" + +#: ./doc/training-guides/module002-ch002-openstack-networking-concepts.xml21(emphasis) +msgid "Namespaces" +msgstr "" + +#: ./doc/training-guides/module002-ch002-openstack-networking-concepts.xml22(para) +msgid "" +"For each network you create, the Network node (or Controller node, if " +"combined) will have a unique network namespace (netns) created by the DHCP " +"and Metadata agents. The netns hosts an interface and IP addresses for " +"dnsmasq and the quantum-ns-metadata-proxy. You can view the namespaces with " +"the ip netns [list], and can interact with the namespaces with the ip netns " +"exec <namespace> <command> command." +msgstr "" + +#: ./doc/training-guides/module002-ch002-openstack-networking-concepts.xml30(emphasis) +msgid "Metadata" +msgstr "" + +#: ./doc/training-guides/module002-ch002-openstack-networking-concepts.xml31(para) +msgid "" +"Not all networks or VMs need metadata access. Rackspace recommends that you " +"use metadata if you are using a single network. If you need metadata, you " +"may also need a default route. (If you don't need a default route, no-" +"gateway will do.)" +msgstr "" + +#: ./doc/training-guides/module002-ch002-openstack-networking-concepts.xml36(para) +msgid "" +"To communicate with the metadata IP address inside the namespace, instances " +"need a route for the metadata network that points to the dnsmasq IP address " +"on the same namespaced interface. OpenStack Networking only injects a route " +"when you do not specify a gateway-ip in the subnet." +msgstr "" + +#: ./doc/training-guides/module002-ch002-openstack-networking-concepts.xml41(para) +msgid "" +"If you need to use a default route and provide instances with access to the " +"metadata route, create the subnet without specifying a gateway IP and with a" +" static route from 0.0.0.0/0 to your gateway IP address. Adjust the DHCP " +"allocation pool so that it will not assign the gateway IP. With this " +"configuration, dnsmasq will pass both routes to instances. This way, " +"metadata will be routed correctly without any changes on the external " +"gateway." +msgstr "" + +#: ./doc/training-guides/module002-ch002-openstack-networking-concepts.xml49(emphasis) +msgid "OVS Bridges" +msgstr "" + +#: ./doc/training-guides/module002-ch002-openstack-networking-concepts.xml50(para) +msgid "" +"An OVS bridge for provider traffic is created and configured on the nodes " +"where single-network-node and single-compute are applied. Bridges are " +"created, but physical interfaces are not added. An OVS bridge is not created" +" on a Controller-only node." +msgstr "" + +#: ./doc/training-guides/module002-ch002-openstack-networking-concepts.xml55(para) +msgid "" +"When creating networks, you can specify the type and properties, such as " +"Flat vs. VLAN, Shared vs. Tenant, or Provider vs. Overlay. These properties " +"identify and determine the behavior and resources of instances attached to " +"the network. The cookbooks will create bridges for the configuration that " +"you specify, although they do not add physical interfaces to provider " +"bridges. For example, if you specify a network type of GRE, a br-tun tunnel " +"bridge will be created to handle overlay traffic." +msgstr "" + +#: ./doc/training-guides/card037-rabbitmq.xml7(title) +msgid "Installing RabbitMQ" +msgstr "" + +#. When image changes, this message will be marked fuzzy or untranslated for +#. you. +#. It doesn't matter what you translate it to: it's not used at all. +#: ./doc/training-guides/module002-ch003-neutron-use-cases.xml32(None) +msgid "@@image: 'figures/image34.png'; md5=de380963b3137c842e8a1795bc376558" +msgstr "" + +#. When image changes, this message will be marked fuzzy or untranslated for +#. you. +#. It doesn't matter what you translate it to: it's not used at all. +#: ./doc/training-guides/module002-ch003-neutron-use-cases.xml46(None) +msgid "@@image: 'figures/image35.png'; md5=9399b9e427152d07037568bdf38fb184" +msgstr "" + +#. When image changes, this message will be marked fuzzy or untranslated for +#. you. +#. It doesn't matter what you translate it to: it's not used at all. +#: ./doc/training-guides/module002-ch003-neutron-use-cases.xml68(None) +msgid "@@image: 'figures/image36.png'; md5=880830d2a425db41661840218713072d" +msgstr "" + +#. When image changes, this message will be marked fuzzy or untranslated for +#. you. +#. It doesn't matter what you translate it to: it's not used at all. +#: ./doc/training-guides/module002-ch003-neutron-use-cases.xml104(None) +msgid "@@image: 'figures/image37.png'; md5=7371790c2697148cafbdfd50c55cc2f2" +msgstr "" + +#. When image changes, this message will be marked fuzzy or untranslated for +#. you. +#. It doesn't matter what you translate it to: it's not used at all. +#: ./doc/training-guides/module002-ch003-neutron-use-cases.xml126(None) +msgid "@@image: 'figures/image38.png'; md5=2e335e5d101e9b4d710e320a6dfa363e" +msgstr "" + +#: ./doc/training-guides/module002-ch003-neutron-use-cases.xml7(title) +msgid "Neutron Use Cases" +msgstr "" + +#: ./doc/training-guides/module002-ch003-neutron-use-cases.xml8(para) +msgid "" +"As of now you must be wondering, how to use these awesome features that " +"OpenStack Networking has given to us." +msgstr "" + +#: ./doc/training-guides/module002-ch003-neutron-use-cases.xml10(guilabel) +msgid "Use Case: Single Flat Network" +msgstr "" + +#: ./doc/training-guides/module002-ch003-neutron-use-cases.xml11(para) +msgid "" +"In the simplest use case, a single OpenStack Networking network exists. This" +" is a \"shared\" network, meaning it is visible to all tenants via the " +"OpenStack Networking API. Tenant VMs have a single NIC, and receive a fixed " +"IP address from the subnet(s) associated with that network. This essentially" +" maps to the FlatManager and FlatDHCPManager models provided by OpenStack " +"Compute. Floating IPs are not supported." +msgstr "" + +#: ./doc/training-guides/module002-ch003-neutron-use-cases.xml19(para) +msgid "" +"It is common that such an OpenStack Networking network is a \"provider " +"network\", meaning it was created by the OpenStack administrator to map " +"directly to an existing physical network in the data center. This allows the" +" provider to use a physical router on that data center network as the " +"gateway for VMs to reach the outside world. For each subnet on an external " +"network, the gateway configuration on the physical router must be manually " +"configured outside of OpenStack." +msgstr "" + +#: ./doc/training-guides/module002-ch003-neutron-use-cases.xml29(title) +msgid "Single Flat Network" +msgstr "" + +#: ./doc/training-guides/module002-ch003-neutron-use-cases.xml36(guilabel) +msgid "Use Case: Multiple Flat Network" +msgstr "" + +#: ./doc/training-guides/module002-ch003-neutron-use-cases.xml38(para) +msgid "" +"This use case is very similar to the above Single Flat Network use case, " +"except that tenants see multiple shared networks via the OpenStack " +"Networking API and can choose which network (or networks) to plug into." +msgstr "" + +#: ./doc/training-guides/module002-ch003-neutron-use-cases.xml43(title) +msgid "Multiple Flat Network" +msgstr "" + +#: ./doc/training-guides/module002-ch003-neutron-use-cases.xml50(guilabel) +msgid "Use Case: Mixed Flat and Private Network" +msgstr "" + +#: ./doc/training-guides/module002-ch003-neutron-use-cases.xml52(para) +msgid "" +"This use case is an extension of the above flat network use cases, in which " +"tenants also optionally have access to private per-tenant networks. In " +"addition to seeing one or more shared networks via the OpenStack Networking " +"API, tenants can create additional networks that are only visible to users " +"of that tenant. When creating VMs, those VMs can have NICs on any of the " +"shared networks and/or any of the private networks belonging to the tenant. " +"This enables the creation of \"multi-tier\" topologies using VMs with " +"multiple NICs. It also supports a model where a VM acting as a gateway can " +"provide services such as routing, NAT, or load balancing." +msgstr "" + +#: ./doc/training-guides/module002-ch003-neutron-use-cases.xml65(title) +msgid "Mixed Flat and Private Network" +msgstr "" + +#: ./doc/training-guides/module002-ch003-neutron-use-cases.xml72(guilabel) +msgid "Use Case: Provider Router with Private Networks" +msgstr "" + +#: ./doc/training-guides/module002-ch003-neutron-use-cases.xml74(para) +msgid "" +"This use provides each tenant with one or more private networks, which " +"connect to the outside world via an OpenStack Networking router. The case " +"where each tenant gets exactly one network in this form maps to the same " +"logical topology as the VlanManager in OpenStack Compute (of course, " +"OpenStack Networking doesn't require VLANs). Using the OpenStack Networking " +"API, the tenant would only see a network for each private network assigned " +"to that tenant. The router object in the API is created and owned by the " +"cloud admin." +msgstr "" + +#: ./doc/training-guides/module002-ch003-neutron-use-cases.xml84(para) +msgid "" +"This model supports giving VMs public addresses using \"floating IPs\", in " +"which the router maps public addresses from the external network to fixed " +"IPs on private networks. Hosts without floating IPs can still create " +"outbound connections to the external network, as the provider router " +"performs SNAT to the router's external IP. The IP address of the physical " +"router is used as the gateway_ip of the external network subnet, so the " +"provider has a default router for Internet traffic." +msgstr "" + +#: ./doc/training-guides/module002-ch003-neutron-use-cases.xml93(para) +msgid "" +"The router provides L3 connectivity between private networks, meaning that " +"different tenants can reach each others instances unless additional " +"filtering, such as security groups, is used. Because there is only a single " +"router, tenant networks cannot use overlapping IPs. Thus, it is likely that " +"the admin would create the private networks on behalf of tenants." +msgstr "" + +#: ./doc/training-guides/module002-ch003-neutron-use-cases.xml101(title) +msgid "Provider Router with Private Networks" +msgstr "" + +#: ./doc/training-guides/module002-ch003-neutron-use-cases.xml108(guilabel) +msgid "Use Case: Per-tenant Routers with Private Networks" +msgstr "" + +#: ./doc/training-guides/module002-ch003-neutron-use-cases.xml110(para) +msgid "" +"A more advanced router scenario in which each tenant gets at least one " +"router, and potentially has access to the OpenStack Networking API to create" +" additional routers. The tenant can create their own networks, potentially " +"uplinking those networks to a router. This model enables tenant-defined " +"multi-tier applications, with each tier being a separate network behind the " +"router. Since there are multiple routers, tenant subnets can be overlapping " +"without conflicting, since access to external networks all happens via SNAT " +"or Floating IPs. Each router uplink and floating IP is allocated from the " +"external network subnet." +msgstr "" + +#: ./doc/training-guides/module002-ch003-neutron-use-cases.xml123(title) +msgid "Per-tenant Routers with Private Networks" +msgstr "" + +#: ./doc/training-guides/module003-ch002-features-benifits.xml7(title) +msgid "Features and Benifits" +msgstr "" + +#: ./doc/training-guides/module003-ch002-features-benifits.xml12(th) +msgid "Features" +msgstr "" + +#: ./doc/training-guides/module003-ch002-features-benifits.xml13(th) +msgid "Benefits" +msgstr "" + +#: ./doc/training-guides/module003-ch002-features-benifits.xml17(emphasis) +msgid "Leverages commodity hardware" +msgstr "" + +#: ./doc/training-guides/module003-ch002-features-benifits.xml20(td) +msgid "No lock-in, lower price/GB" +msgstr "" + +#: ./doc/training-guides/module003-ch002-features-benifits.xml26(emphasis) +msgid "HDD/node failure agnostic" +msgstr "" + +#: ./doc/training-guides/module003-ch002-features-benifits.xml28(td) +msgid "Self healingReliability, data redundancy protecting from failures" +msgstr "" + +#: ./doc/training-guides/module003-ch002-features-benifits.xml35(emphasis) +msgid "Unlimited storage" +msgstr "" + +#: ./doc/training-guides/module003-ch002-features-benifits.xml37(td) +msgid "" +"Huge & flat namespace, highly scalable read/write accessAbility to serve" +" content directly from storage system" +msgstr "" + +#: ./doc/training-guides/module003-ch002-features-benifits.xml45(emphasis) +msgid "Multi-dimensional scalability" +msgstr "" + +#: ./doc/training-guides/module003-ch002-features-benifits.xml44(td) +msgid "" +" (scale out architecture)Scale vertically and horizontally-" +"distributed storage" +msgstr "" + +#: ./doc/training-guides/module003-ch002-features-benifits.xml49(td) +msgid "Backup and archive large amounts of data with linear performance" +msgstr "" + +#: ./doc/training-guides/module003-ch002-features-benifits.xml55(emphasis) +msgid "Account/Container/Object structure" +msgstr "" + +#: ./doc/training-guides/module003-ch002-features-benifits.xml54(td) +msgid "No nesting, not a traditional file system" +msgstr "" + +#: ./doc/training-guides/module003-ch002-features-benifits.xml59(td) +msgid "Optimized for scaleScales to multiple petabytes, billions of objects" +msgstr "" + +#: ./doc/training-guides/module003-ch002-features-benifits.xml66(emphasis) +msgid "Built-in replication3x+ data redundancy" +msgstr "" + +#: ./doc/training-guides/module003-ch002-features-benifits.xml65(td) +msgid " compared to 2x on RAID" +msgstr "" + +#: ./doc/training-guides/module003-ch002-features-benifits.xml70(td) +msgid "" +"Configurable number of accounts, container and object copies for high " +"availability" +msgstr "" + +#: ./doc/training-guides/module003-ch002-features-benifits.xml77(emphasis) +msgid "Easily add capacity" +msgstr "" + +#: ./doc/training-guides/module003-ch002-features-benifits.xml76(td) +msgid " unlike RAID resize" +msgstr "" + +#: ./doc/training-guides/module003-ch002-features-benifits.xml80(td) +msgid "Elastic data scaling with ease" +msgstr "" + +#: ./doc/training-guides/module003-ch002-features-benifits.xml86(emphasis) +msgid "No central database" +msgstr "" + +#: ./doc/training-guides/module003-ch002-features-benifits.xml88(td) +msgid "Higher performance, no bottlenecks" +msgstr "" + +#: ./doc/training-guides/module003-ch002-features-benifits.xml94(emphasis) +msgid "RAID not required" +msgstr "" + +#: ./doc/training-guides/module003-ch002-features-benifits.xml96(td) +msgid "Handle lots of small, random reads and writes efficiently" +msgstr "" + +#: ./doc/training-guides/module003-ch002-features-benifits.xml102(emphasis) +msgid "Built-in management utilities" +msgstr "" + +#: ./doc/training-guides/module003-ch002-features-benifits.xml105(td) +msgid "" +"Account Management: Create, add, verify, delete usersContainer Management: " +"Upload, download, verifyMonitoring: Capacity, host, network, log trawling, " +"cluster health" +msgstr "" + +#: ./doc/training-guides/module003-ch002-features-benifits.xml114(emphasis) +msgid "Drive auditing" +msgstr "" + +#: ./doc/training-guides/module003-ch002-features-benifits.xml116(td) +msgid "Detect drive failures preempting data corruption" +msgstr "" + +#: ./doc/training-guides/module003-ch002-features-benifits.xml122(emphasis) +msgid "Expiring objects" +msgstr "" + +#: ./doc/training-guides/module003-ch002-features-benifits.xml124(td) +msgid "" +"Users can set an expiration time or a TTL on an object to control access" +msgstr "" + +#: ./doc/training-guides/module003-ch002-features-benifits.xml131(emphasis) +msgid "Direct object access" +msgstr "" + +#: ./doc/training-guides/module003-ch002-features-benifits.xml133(td) +msgid "Enable direct browser access to content, such as for a control panel" +msgstr "" + +#: ./doc/training-guides/module003-ch002-features-benifits.xml140(emphasis) +msgid "Realtime visibility into client requests" +msgstr "" + +#: ./doc/training-guides/module003-ch002-features-benifits.xml143(td) +msgid "Know what users are requesting" +msgstr "" + +#: ./doc/training-guides/module003-ch002-features-benifits.xml149(emphasis) +msgid "Supports S3 API" +msgstr "" + +#: ./doc/training-guides/module003-ch002-features-benifits.xml151(td) +msgid "Utilize tools that were designed for the popular S3 API" +msgstr "" + +#: ./doc/training-guides/module003-ch002-features-benifits.xml157(emphasis) +msgid "Restrict containers per account" +msgstr "" + +#: ./doc/training-guides/module003-ch002-features-benifits.xml160(td) +msgid "Limit access to control usage by user" +msgstr "" + +#: ./doc/training-guides/module003-ch002-features-benifits.xml166(emphasis) +msgid "Support for NetApp, Nexenta, SolidFire" +msgstr "" + +#: ./doc/training-guides/module003-ch002-features-benifits.xml169(td) +msgid "Unified support for block volumes using a variety of storage systems" +msgstr "" + +#: ./doc/training-guides/module003-ch002-features-benifits.xml176(emphasis) +msgid "Snapshot and backup API for block volumes" +msgstr "" + +#: ./doc/training-guides/module003-ch002-features-benifits.xml179(td) +msgid "Data protection and recovery for VM data" +msgstr "" + +#: ./doc/training-guides/module003-ch002-features-benifits.xml185(emphasis) +msgid "Standalone volume API available" +msgstr "" + +#: ./doc/training-guides/module003-ch002-features-benifits.xml188(td) +msgid "Separate endpoint and API for integration with other compute systems" +msgstr "" + +#: ./doc/training-guides/module003-ch002-features-benifits.xml195(emphasis) +msgid "Integration with Compute" +msgstr "" + +#: ./doc/training-guides/module003-ch002-features-benifits.xml197(td) +msgid "" +"Fully integrated to Compute for attaching block volumes and reporting on " +"usage" +msgstr "" + +#: ./doc/training-guides/card040-cinder.xml7(title) +msgid "Install Cinder" +msgstr "" + +#: ./doc/training-guides/lab001-control-node.xml26(emphasis) +msgid "Preparing Ubuntu 13.04/12.04" +msgstr "" + +#: ./doc/training-guides/lab001-control-node.xml47(emphasis) +msgid "Networking :" +msgstr "" + +#: ./doc/training-guides/lab001-control-node.xml48(para) +msgid "" +"Configure your network by editing " +"/etc/network/interfaces file" +msgstr "" + +#: ./doc/training-guides/lab001-control-node.xml50(para) +msgid "" +"Open /etc/network/interfaces and edit file as " +"mentioned:" +msgstr "" + +#: ./doc/training-guides/lab001-control-node.xml84(para) +msgid "After saving the interfaces file, restart the networking service" +msgstr "" + +#: ./doc/training-guides/lab001-control-node.xml90(para) +msgid "" +"You should see the expected network interface cards having the required IP " +"Addresses." +msgstr "" + +#: ./doc/training-guides/lab001-control-node.xml93(emphasis) +msgid "SSH from HOST" +msgstr "" + +#: ./doc/training-guides/lab001-control-node.xml96(para) +msgid "" +"Create a SSH key pair for your Control Node. Follow the same steps as you " +"did in the starting section of the article for your host machine." +msgstr "" + +#: ./doc/training-guides/lab001-control-node.xml99(para) +msgid "To SSH into Control Node from the Host Machine type the below command." +msgstr "" + +#: ./doc/training-guides/lab001-control-node.xml106(para) +msgid "Now you can have access to your host clipboard." +msgstr "" + +#: ./doc/training-guides/lab001-control-node.xml109(emphasis) +msgid "My SQL" +msgstr "" + +#: ./doc/training-guides/lab001-control-node.xml112(para) +msgid "Install MySQL:" +msgstr "" + +#: ./doc/training-guides/lab001-control-node.xml118(para) +msgid "Configure mysql to accept all incoming requests:" +msgstr "" + +#: ./doc/training-guides/lab001-control-node.xml128(para) +msgid "Install RabbitMQ:" +msgstr "" + +#: ./doc/training-guides/lab001-control-node.xml134(para) +msgid "Install NTP service:" +msgstr "" + +#: ./doc/training-guides/lab001-control-node.xml140(para) +msgid "Create these databases:" +msgstr "" + +#: ./doc/training-guides/lab001-control-node.xml157(emphasis) +msgid "Other" +msgstr "" + +#: ./doc/training-guides/lab001-control-node.xml160(para) +msgid "Install other services:" +msgstr "" + +#: ./doc/training-guides/lab001-control-node.xml166(para) +msgid "Enable IP_Forwarding:" +msgstr "" + +#: ./doc/training-guides/lab001-control-node.xml172(para) +msgid "" +"Also add the following two lines into/etc/sysctl.conf:" +msgstr "" + +#: ./doc/training-guides/lab001-control-node.xml179(para) +msgid "To save you from reboot, perform the following" +msgstr "" + +#: ./doc/training-guides/lab001-control-node.xml188(emphasis) +msgid "Keystone" +msgstr "" + +#: ./doc/training-guides/lab001-control-node.xml189(para) +msgid "" +"Keystone is an OpenStack project that provides Identity, Token, Catalog and " +"Policy services for use specifically by projects in the OpenStack family.It " +"implements OpenStack’s Identity API." +msgstr "" + +#: ./doc/training-guides/lab001-control-node.xml192(para) +msgid "Install Keystone packages:" +msgstr "" + +#: ./doc/training-guides/lab001-control-node.xml198(para) +msgid "" +"Adapt the connection attribute in the " +"/etc/keystone/keystone.conf to the new database:" +msgstr "" + +#: ./doc/training-guides/lab001-control-node.xml204(para) +msgid "Restart the identity service then synchronize the database:" +msgstr "" + +#: ./doc/training-guides/lab001-control-node.xml211(para) +msgid "Fill up the keystone database using the below two scripts:" +msgstr "" + +#: ./doc/training-guides/lab001-control-node.xml213(filename) +msgid "keystone_basic.sh" +msgstr "" + +#: ./doc/training-guides/lab001-control-node.xml214(filename) +msgid "keystone_endpoints_basic.sh" +msgstr "" + +#: ./doc/training-guides/lab001-control-node.xml218(para) +msgid "Run Scripts:" +msgstr "" + +#: ./doc/training-guides/lab001-control-node.xml227(para) +msgid "Create a simple credentials file" +msgstr "" + +#: ./doc/training-guides/lab001-control-node.xml233(para) +msgid "Paste the following:" +msgstr "" + +#: ./doc/training-guides/lab001-control-node.xml242(para) +msgid "Load the above credentials:" +msgstr "" + +#: ./doc/training-guides/lab001-control-node.xml248(para) +msgid "To test Keystone, we use a simple CLI command:" +msgstr "" + +#: ./doc/training-guides/lab001-control-node.xml254(emphasis) +msgid "Glance" +msgstr "" + +#: ./doc/training-guides/lab001-control-node.xml255(para) +msgid "" +"OpenStack Glance project provides services for discovering, registering, and" +" retrieving virtual machine images. Glance has a RESTful API that allows " +"querying of VM image metadata as well as retrieval of the actual image." +msgstr "" + +#: ./doc/training-guides/lab001-control-node.xml257(para) +msgid "" +"VM images made available through Glance can be stored in a variety of " +"locations from simple file systems to object-storage systems like the " +"OpenStack Swift project." +msgstr "" + +#: ./doc/training-guides/lab001-control-node.xml258(para) +msgid "" +"Glance, as with all OpenStack projects, is written with the following design" +" guidelines in mind:" +msgstr "" + +#: ./doc/training-guides/lab001-control-node.xml261(para) +#: ./doc/training-guides/lab001-control-node.xml441(para) +#: ./doc/training-guides/lab001-control-node.xml566(para) +msgid "Component based architecture: Quickly add new behaviors" +msgstr "" + +#: ./doc/training-guides/lab001-control-node.xml264(para) +#: ./doc/training-guides/lab001-control-node.xml444(para) +#: ./doc/training-guides/lab001-control-node.xml569(para) +msgid "Highly available: Scale to very serious workloads" +msgstr "" + +#: ./doc/training-guides/lab001-control-node.xml267(para) +msgid "Fault tolerant: Isolated processes avoid cascading failures" +msgstr "" + +#: ./doc/training-guides/lab001-control-node.xml270(para) +#: ./doc/training-guides/lab001-control-node.xml450(para) +#: ./doc/training-guides/lab001-control-node.xml575(para) +msgid "Recoverable: Failures should be easy to diagnose, debug, and rectify" +msgstr "" + +#: ./doc/training-guides/lab001-control-node.xml273(para) +#: ./doc/training-guides/lab001-control-node.xml453(para) +msgid "" +"Open standards: Be a reference implementation for a community-driven api" +msgstr "" + +#: ./doc/training-guides/lab001-control-node.xml277(para) +#: ./doc/training-guides/card127-glance.xml7(title) +msgid "Install Glance" +msgstr "" + +#: ./doc/training-guides/lab001-control-node.xml283(para) +msgid "Update /etc/glance/glance-api-paste.ini" +msgstr "" + +#: ./doc/training-guides/lab001-control-node.xml297(para) +msgid "Update the /etc/glance/glance-registry-paste.ini" +msgstr "" + +#: ./doc/training-guides/lab001-control-node.xml310(para) +msgid "Update the /etc/glance/glance-api.conf" +msgstr "" + +#: ./doc/training-guides/lab001-control-node.xml326(para) +msgid "Update the /etc/glance/glance-registry.conf" +msgstr "" + +#: ./doc/training-guides/lab001-control-node.xml342(para) +msgid "Restart the glance-api and glance-registry services:" +msgstr "" + +#: ./doc/training-guides/lab001-control-node.xml348(para) +msgid "Synchronize the Glance database:" +msgstr "" + +#: ./doc/training-guides/lab001-control-node.xml354(para) +msgid "" +"To test Glance, upload the “cirros cloud image” directly from the internet:" +msgstr "" + +#: ./doc/training-guides/lab001-control-node.xml360(para) +msgid "Check if the image is successfully uploaded:" +msgstr "" + +#: ./doc/training-guides/lab001-control-node.xml367(para) +msgid "" +"Neutron is an OpenStack project to provide “network connectivity as a " +"service\" between interface devices (e.g., vNICs) managed by other Openstack" +" services (e.g., nova)." +msgstr "" + +#: ./doc/training-guides/lab001-control-node.xml370(para) +msgid "Install Neutron Server and the OpenVSwitch package collection:" +msgstr "" + +#: ./doc/training-guides/lab001-control-node.xml376(para) +msgid "" +"Edit the " +"/etc/neutron/plugins/openvswitch/ovs_neutron_plugin.ini:" +msgstr "" + +#: ./doc/training-guides/lab001-control-node.xml396(para) +msgid "Edit the /etc/neutron/api-paste.ini:" +msgstr "" + +#: ./doc/training-guides/lab001-control-node.xml411(para) +msgid "Edit the /etc/neutron/neutron.conf:" +msgstr "" + +#: ./doc/training-guides/lab001-control-node.xml428(para) +msgid "Restart Neutron services:" +msgstr "" + +#: ./doc/training-guides/lab001-control-node.xml435(para) +msgid "" +"Nova is the project name for OpenStack Compute, a cloud computing fabric " +"controller, the main part of an IaaS system. Individuals and organizations " +"can use Nova to host and manage their own cloud computing systems. Nova " +"originated as a project out of NASA Ames Research Laboratory." +msgstr "" + +#: ./doc/training-guides/lab001-control-node.xml438(para) +msgid "Nova is written with the following design guidelines in mind" +msgstr "" + +#: ./doc/training-guides/lab001-control-node.xml447(para) +#: ./doc/training-guides/lab001-control-node.xml572(para) +msgid "Fault-Tolerant: Isolated processes avoid cascading failures" +msgstr "" + +#: ./doc/training-guides/lab001-control-node.xml457(para) +msgid "" +"API Compatibility: Nova strives to provide API-compatible with popular " +"systems like Amazon EC2" +msgstr "" + +#: ./doc/training-guides/lab001-control-node.xml461(para) +msgid "Install nova components:" +msgstr "" + +#: ./doc/training-guides/lab001-control-node.xml544(para) +msgid "Synchronize your database:" +msgstr "" + +#: ./doc/training-guides/lab001-control-node.xml550(para) +msgid "Restart nova-* services (all nova services):" +msgstr "" + +#: ./doc/training-guides/lab001-control-node.xml556(para) +msgid "" +"Check for the smiling faces on nova-* services to confirm your " +"installation::" +msgstr "" + +#: ./doc/training-guides/lab001-control-node.xml562(emphasis) +msgid "Cinder" +msgstr "" + +#: ./doc/training-guides/lab001-control-node.xml563(para) +msgid "" +"Cinder is an OpenStack project to provide “block storage as a service”." +msgstr "" + +#: ./doc/training-guides/lab001-control-node.xml578(para) +msgid "" +"Open Standards: Be a reference implementation for a community-driven api" +msgstr "" + +#: ./doc/training-guides/lab001-control-node.xml582(para) +msgid "" +"API Compatibility: Cinder strives to provide API-compatible with popular " +"systems like Amazon EC2" +msgstr "" + +#: ./doc/training-guides/lab001-control-node.xml586(para) +msgid "Install Cinder components:" +msgstr "" + +#: ./doc/training-guides/lab001-control-node.xml592(para) +msgid "Configure the iscsi services:" +msgstr "" + +#: ./doc/training-guides/lab001-control-node.xml598(para) +msgid "Restart the services:" +msgstr "" + +#: ./doc/training-guides/lab001-control-node.xml605(para) +msgid "Edit /etc/cinder/api-paste.ini:" +msgstr "" + +#: ./doc/training-guides/lab001-control-node.xml622(para) +msgid "Edit /etc/cinder/cinder.conf:" +msgstr "" + +#: ./doc/training-guides/lab001-control-node.xml640(para) +msgid "Then, synchronize Cinder database:" +msgstr "" + +#: ./doc/training-guides/lab001-control-node.xml646(para) +msgid "Finally, create a volumegroup and name it cinder-volumes:" +msgstr "" + +#: ./doc/training-guides/lab001-control-node.xml660(para) +msgid "Proceed to create the physical volume then the volume group:" +msgstr "" + +#: ./doc/training-guides/lab001-control-node.xml667(para) +msgid "" +"Note: Beware that this volume group gets lost after a system reboot. If you " +"dont want to do this step again ... make sure that you save the machine " +"state and not shut it down." +msgstr "" + +#: ./doc/training-guides/lab001-control-node.xml670(para) +msgid "Restart the Cinder services:" +msgstr "" + +#: ./doc/training-guides/lab001-control-node.xml676(para) +msgid "Verify if Cinder services are running:" +msgstr "" + +#: ./doc/training-guides/lab001-control-node.xml682(emphasis) +msgid "Horizon" +msgstr "" + +#: ./doc/training-guides/lab001-control-node.xml683(para) +msgid "" +"Horizon is the canonical implementation of Openstack’s Dashboard, which " +"provides a web based user interface to OpenStack services including Nova, " +"Swift, Keystone, etc." +msgstr "" + +#: ./doc/training-guides/lab001-control-node.xml686(para) +msgid "To install Horizon, proceed like this" +msgstr "" + +#: ./doc/training-guides/lab001-control-node.xml692(para) +msgid "" +"If you don't like the OpenStack Ubuntu Theme, you can remove it with help of" +" the below command:" +msgstr "" + +#: ./doc/training-guides/lab001-control-node.xml698(para) +msgid "Reload Apache and memcached:" +msgstr "" + +#: ./doc/training-guides/card046-L3_Configuration_in_the_Network_Node.xml7(title) +msgid "L3 Configuration in the Network Node" +msgstr "" + +#: ./doc/training-guides/bk000-preface.xml6(title) +msgid "Start Here" +msgstr "" + +#: ./doc/training-guides/bk000-preface.xml8(title) +msgid "Preface" +msgstr "" + +#: ./doc/training-guides/bk000-preface.xml13(title) +msgid "OpenStack Training Guides Are Under Construction" +msgstr "" + +#: ./doc/training-guides/bk000-preface.xml14(para) +msgid "" +"We need your help! This is a community driven project to provide the user " +"group community access to OpenStack training materials. We cannot make this " +"work without your help." +msgstr "" + +#: ./doc/training-guides/bk000-preface.xml16(para) +msgid "" +"There are a few ways to get involved. The easiest way is to use the training" +" guides. Look at the end of each section and you will see the Submit a Bug " +"link. When you find something that can be improved or fixed, submit a bug by" +" clicking on the link." +msgstr "" + +#: ./doc/training-guides/bk000-preface.xml19(para) +msgid "" +"If you want to get involved with the effort around OpenStack community " +"training, read on, here are the options:" +msgstr "" + +#: ./doc/training-guides/bk000-preface.xml24(title) +msgid "Attending a user group using the training materials" +msgstr "" + +#: ./doc/training-guides/bk000-preface.xml25(para) +msgid "" +"The OpenStack community training started at the SFBay OpenStack User Group. " +"More information on this user group and others using the training guides on " +"the OpenStack User " +"Groups page." +msgstr "" + +#: ./doc/training-guides/bk000-preface.xml32(title) +msgid "Teach / Lead a user group using the training materials" +msgstr "" + +#: ./doc/training-guides/bk000-preface.xml33(para) +msgid "" +"Awesome! Your experience will not only give you more experience with " +"OpenStack, but you will help some people find new jobs. We have put all the " +"information about How" +" To Run An OpenStack Hackathon here." +msgstr "" + +#: ./doc/training-guides/bk000-preface.xml40(title) +msgid "Help create the training pages" +msgstr "" + +#: ./doc/training-guides/bk000-preface.xml44(para) +msgid "" +"We are currently working on creating the Associate Training Guide. It is the" +" first of four training guides. We are using the Install Guide, " +"Administration Guides, Developer Documentation, and Aptira supplied content " +"as the sources for most of the Associate Training Guide. The basic idea is " +"that we use XML include statements to actually use the source content to " +"create new pages. We aim to use as much of the material as possible from " +"existing documentation. By doing this we reuse and improve the existing " +"docs. The topics in the Associate Training Guide are in a bunch of KanBan " +"story board cards. Each card in the story board represents something that an" +" Associate trainee needs to learn. But first things first, you need to get " +"some basic tools and accounts installed and configured before you can really" +" start." +msgstr "" + +#: ./doc/training-guides/bk000-preface.xml57(para) +msgid "" +"Getting Accounts and Tools: We can't do " +"this without operators and developers using and creating the content. Anyone" +" can contribute content. You will need the tools to get started. Go to the " +"Getting Tools and Accounts page." +msgstr "" + +#: ./doc/training-guides/bk000-preface.xml64(para) +msgid "" +"Pick a Card: Once you have your tools " +"ready to go, you can assign some work to yourself. Go to the Training Trello/KanBan storyboard" +" and assign a card / user story from the Sprint Backlog to yourself. If you " +"do not have a Trello account, no problem, just create one. Email seanrob" +"@yahoo-inc.com and you will have access." +msgstr "" + +#: ./doc/training-guides/bk000-preface.xml72(para) +msgid "" +"Create the Content: Each card / user " +"story from the KanBan story board will be a separate chunk of content that " +"you will add to the openstack-manuals repository openstack-training sub-" +"project. More details on creating training content here." +msgstr "" + +#: ./doc/training-guides/bk000-preface.xml82(para) +msgid "" +"Here are more details on committing changes to OpenStack fixing a documentation" +" bug , OpenStack Gerrit " +"Workflow, OpenStack " +"Documentation HowTo and , Git " +"Documentation" +msgstr "" + +#: ./doc/training-guides/bk000-preface.xml91(para) +msgid "More details on the OpenStack Training project." +msgstr "" + +#: ./doc/training-guides/bk000-preface.xml95(para) +msgid "" +"OpenStack " +"Training Wiki (describes the project in detail)" +msgstr "" + +#: ./doc/training-guides/bk000-preface.xml99(para) +msgid "" +"OpenStack Training blueprint(this is the key " +"project page)" +msgstr "" + +#: ./doc/training-guides/bk000-preface.xml104(para) +msgid "" +"Bi-Weekly SFBay Hackathon " +"meetup page(we discuss project details with all team members)" +msgstr "" + +#: ./doc/training-guides/bk000-preface.xml108(para) +msgid "" +"Bi-Weekly " +"SFBay Hackathon Etherpad(meetup notes)" +msgstr "" + +#: ./doc/training-guides/bk000-preface.xml112(para) +msgid "" +"Core Training Weekly Meeting Agenda(we review project " +"action items here)" +msgstr "" + +#: ./doc/training-guides/bk000-preface.xml116(para) +msgid "" +"Training Trello/KanBan " +"storyboard(we develop high level project action items here)" +msgstr "" + +#: ./doc/training-guides/bk000-preface.xml123(link) +msgid "" +"Submit a bug. Enter the summary as \"Training, \" with a few words. Be " +"descriptive as possible in the description field. Open the tag pull-down and" +" enter training-manuals." +msgstr "" + +#: ./doc/training-guides/bk000-preface.xml127(title) +msgid "Building the Training Cluster" +msgstr "" + +#: ./doc/training-guides/bk000-preface.xml130(title) +msgid "Important Terms" +msgstr "" + +#: ./doc/training-guides/bk000-preface.xml144(title) +msgid "Building the Training Cluster, Manually" +msgstr "" + +#: ./doc/training-guides/lab000-openstack-training-labs.xml5(title) +msgid "OpenStack Training Labs" +msgstr "" + +#: ./doc/training-guides/card026-network-node-architecture.xml7(title) +msgid "Network Node Overview" +msgstr "" + +#: ./doc/training-guides/bk001-ch001-associate-getting-started.xml8(title) +msgid "Day 1, 09:00 to 11:00" +msgstr "" + +#: ./doc/training-guides/bk001-ch001-associate-getting-started.xml13(para) +msgid "" +"Training will take 1 month self paced, (2) 2 week periods with a user group " +"meeting, or 16 hours instructor led." +msgstr "" + +#: ./doc/training-guides/bk001-ch001-associate-getting-started.xml17(para) +msgid "" +"Working knowledge of Linux CLI, basic Linux SysAdmin skills (directory " +"structure, vi, ssh, installing software)" +msgstr "" + +#: ./doc/training-guides/bk001-ch001-associate-getting-started.xml19(para) +msgid "Basic networking knowledge (Ethernet, VLAN, IP addressing)" +msgstr "" + +#: ./doc/training-guides/bk001-ch001-associate-getting-started.xml20(para) +msgid "Laptop with VirtualBox installed (highly recommended)" +msgstr "" + +#: ./doc/training-guides/bk001-ch001-associate-getting-started.xml24(title) +msgid "Introduction Text" +msgstr "" + +#: ./doc/training-guides/bk001-ch001-associate-getting-started.xml31(title) +#: ./doc/training-guides/module001-ch002-brief-overview.xml7(title) +msgid "Brief Overview" +msgstr "" + +#: ./doc/training-guides/bk001-ch001-associate-getting-started.xml38(title) +msgid "Core Projects" +msgstr "" + +#: ./doc/training-guides/bk001-ch001-associate-getting-started.xml52(title) +msgid "Virtual Machine Provisioning Walk-Through" +msgstr "" + +#: ./doc/training-guides/card044-install-and-configure-neutron-network-node.xml7(title) +msgid "Neutron Installation and Configuration in Network node" +msgstr "" + +#: ./doc/training-guides/card073-control-state-instance.xml7(title) +#: ./doc/training-guides/card073-control-state-instance.xml8(emphasis) +msgid "Controlling instance state" +msgstr "" + +#: ./doc/training-guides/bk001-ch005-associate-compute-node.xml10(title) +msgid "Day 1, 15:00 to 17:00" +msgstr "" + +#: ./doc/training-guides/bk001-ch005-associate-compute-node.xml37(title) +msgid "Block Storage CLI Commands" +msgstr "" + +#: ./doc/training-guides/bk001-ch005-associate-compute-node.xml44(title) +msgid "Block Storage Manage Volumes" +msgstr "" + +#: ./doc/training-guides/bk001-ch005-associate-compute-node.xml51(title) +msgid "Compute CLI Commands" +msgstr "" + +#: ./doc/training-guides/bk001-ch005-associate-compute-node.xml58(title) +msgid "Compute Image creation" +msgstr "" + +#: ./doc/training-guides/bk001-ch005-associate-compute-node.xml65(title) +msgid "Compute Boot Instance" +msgstr "" + +#: ./doc/training-guides/bk001-ch005-associate-compute-node.xml72(title) +msgid "Compute Terminate Instance" +msgstr "" + +#: ./doc/training-guides/bk002-ch005-operator-controller-node-lab.xml6(title) +msgid "Controller Node Lab" +msgstr "" + +#: ./doc/training-guides/bk002-ch005-operator-controller-node-lab.xml8(title) +msgid "Days 2 to 4, 13:30 to 14:45, 15:00 to 17:00" +msgstr "" + +#: ./doc/training-guides/card128-swift.xml7(title) +msgid "Install Swift" +msgstr "" + +#. When image changes, this message will be marked fuzzy or untranslated for +#. you. +#. It doesn't matter what you translate it to: it's not used at all. +#: ./doc/training-guides/module001-ch002-brief-overview.xml54(None) +msgid "@@image: 'figures/image23.jpg'; md5=6b259da45f404aa65ac2388e600f30b3" +msgstr "" + +#: ./doc/training-guides/module001-ch002-brief-overview.xml8(para) +msgid "" +"OpenStack is a cloud operating system that controls large pools of compute, " +"storage, and networking resources throughout a datacenter. It is all managed" +" through a dashboard that gives administrators control while empowering " +"their users to provision resources through a web interface." +msgstr "" + +#: ./doc/training-guides/module001-ch002-brief-overview.xml13(para) +msgid "" +"OpenStack is a global collaboration of developers and cloud computing " +"technologists producing the ubiquitous open source cloud computing platform " +"for public and private clouds. The project aims to deliver solutions for all" +" types of clouds by being" +msgstr "" + +#: ./doc/training-guides/module001-ch002-brief-overview.xml19(para) +msgid "simple to implement" +msgstr "" + +#: ./doc/training-guides/module001-ch002-brief-overview.xml22(para) +msgid "massively scalable" +msgstr "" + +#: ./doc/training-guides/module001-ch002-brief-overview.xml25(para) +msgid "feature rich." +msgstr "" + +#: ./doc/training-guides/module001-ch002-brief-overview.xml28(para) +msgid "" +"To check out more information on OpenStack visit http://goo.gl/Ye9DFT" +msgstr "" + +#: ./doc/training-guides/module001-ch002-brief-overview.xml31(guilabel) +msgid "OpenStack Foundation:" +msgstr "" + +#: ./doc/training-guides/module001-ch002-brief-overview.xml32(para) +msgid "" +"The OpenStack Foundation, established September 2012, is an independent body" +" providing shared resources to help achieve the OpenStack Mission by " +"protecting, empowering, and promoting OpenStack software and the community " +"around it. This includes users, developers and the entire ecosystem. For " +"more information visit http://goo.gl/3uvmNX." +msgstr "" + +#: ./doc/training-guides/module001-ch002-brief-overview.xml38(guilabel) +msgid "Who's behind OpenStack?" +msgstr "" + +#: ./doc/training-guides/module001-ch002-brief-overview.xml39(para) +msgid "" +"Founded by Rackspace Hosting and NASA, OpenStack has grown to be a global " +"software community of developers collaborating on a standard and massively " +"scalable open source cloud operating system. The OpenStack Foundation " +"promotes the development, distribution and adoption of the OpenStack cloud " +"operating system. As the independent home for OpenStack, the Foundation has " +"already attracted more than 7,000 individual members from 100 countries and " +"850 different organizations. It has also secured more than $10 million in " +"funding and is ready to fulfill the OpenStack mission of becoming the " +"ubiquitous cloud computing platform. Checkout http://goo.gl/BZHJKdfor more on the " +"same." +msgstr "" + +#: ./doc/training-guides/module001-ch002-brief-overview.xml51(title) +msgid "Nebula (NASA)" +msgstr "" + +#: ./doc/training-guides/module001-ch002-brief-overview.xml58(para) +msgid "" +"The goal of the OpenStack Foundation is to serve developers, users, and the " +"entire ecosystem by providing a set of shared resources to grow the " +"footprint of public and private OpenStack clouds, enable technology vendors " +"targeting the platform and assist developers in producing the best cloud " +"software in the industry." +msgstr "" + +#: ./doc/training-guides/module001-ch002-brief-overview.xml64(guilabel) +msgid "Who uses OpenStack?" +msgstr "" + +#: ./doc/training-guides/module001-ch002-brief-overview.xml65(para) +msgid "" +"Corporations, service providers, VARS, SMBs, researchers, and global data " +"centers looking to deploy large-scale cloud deployments for private or " +"public clouds leveraging the support and resulting technology of a global " +"open source community. This is just three years into OpenStack, it's new, " +"it's yet to mature and has immense possibilities. How do I say that? All " +"these ‘buzz words’ will fall into a properly solved jigsaw puzzle as you go " +"through this article." +msgstr "" + +#: ./doc/training-guides/module001-ch002-brief-overview.xml73(guilabel) +msgid "It's Open Source:" +msgstr "" + +#: ./doc/training-guides/module001-ch002-brief-overview.xml74(para) +msgid "" +"All of the code for OpenStack is freely available under the Apache 2.0 " +"license. Anyone can run it, build on it, or submit changes back to the " +"project. This open development model is one of the best ways to foster " +"badly-needed cloud standards, remove the fear of proprietary lock-in for " +"cloud customers, and create a large ecosystem that spans cloud providers." +msgstr "" + +#: ./doc/training-guides/module001-ch002-brief-overview.xml80(guilabel) +msgid "Who it's for:" +msgstr "" + +#: ./doc/training-guides/module001-ch002-brief-overview.xml81(para) +msgid "" +"Enterprises, service providers, government and academic institutions with " +"physical hardware that would like to build a public or private cloud." +msgstr "" + +#: ./doc/training-guides/module001-ch002-brief-overview.xml84(guilabel) +msgid "How it's being used today:" +msgstr "" + +#: ./doc/training-guides/module001-ch002-brief-overview.xml85(para) +msgid "" +"Organizations like CERN, Cisco WebEx, DreamHost, eBay, The Gap, HP, " +"MercadoLibre, NASA, PayPal, Rackspace and University of Melbourne have " +"deployed OpenStack clouds to achieve control, business agility and cost " +"savings without the licensing fees and terms of proprietary software. For " +"complete user stories visit http://goo.gl/aF4lsL, this should give " +"you a good idea about the importance of OpenStack." +msgstr "" + +#: ./doc/training-guides/bk002-operator-training-guide.xml5(title) +msgid "Operator Training Guide" +msgstr "" + +#: ./doc/training-guides/bk002-ch008-operator-compute-node-lab.xml6(title) +msgid "Compute Node Lab" +msgstr "" + +#: ./doc/training-guides/bk002-ch008-operator-compute-node-lab.xml8(title) +msgid "Days 5 to 6, 13:30 to 14:45, 15:00 to 17:00" +msgstr "" + +#: ./doc/training-guides/module002-ch004-security-in-neutron.xml7(title) +msgid "Security in Neutron" +msgstr "" + +#: ./doc/training-guides/module002-ch004-security-in-neutron.xml8(guilabel) +msgid "Security Groups" +msgstr "" + +#: ./doc/training-guides/module002-ch004-security-in-neutron.xml9(para) +msgid "" +"Security groups and security group rules allows administrators and tenants " +"the ability to specify the type of traffic and direction (ingress/egress) " +"that is allowed to pass through a port. A security group is a container for " +"security group rules." +msgstr "" + +#: ./doc/training-guides/module002-ch004-security-in-neutron.xml14(para) +msgid "" +"When a port is created in OpenStack Networking it is associated with a " +"security group. If a security group is not specified the port will be " +"associated with a 'default' security group. By default this group will drop " +"all ingress traffic and allow all egress. Rules can be added to this group " +"in order to change the behaviour." +msgstr "" + +#: ./doc/training-guides/module002-ch004-security-in-neutron.xml20(para) +msgid "" +"If one desires to use the OpenStack Compute security group APIs and/or have " +"OpenStack Compute orchestrate the creation of new ports for instances on " +"specific security groups, additional configuration is needed. To enable " +"this, one must configure the following file /etc/nova/nova.conf and set the " +"config option security_group_api=neutron on every node running nova-compute " +"and nova-api. After this change is made restart nova-api and nova-compute in" +" order to pick up this change. After this change is made one will be able to" +" use both the OpenStack Compute and OpenStack Network security group API at " +"the same time." +msgstr "" + +#: ./doc/training-guides/module002-ch004-security-in-neutron.xml32(guilabel) +msgid "Authentication and Authorization" +msgstr "" + +#: ./doc/training-guides/module002-ch004-security-in-neutron.xml33(para) +msgid "" +"OpenStack Networking uses the OpenStack Identity service (project name " +"keystone) as the default authentication service. When OpenStack Identity is " +"enabled Users submitting requests to the OpenStack Networking service must " +"provide an authentication token in X-Auth-Token request header. The " +"aforementioned token should have been obtained by authenticating with the " +"OpenStack Identity endpoint. For more information concerning authentication " +"with OpenStack Identity, please refer to the OpenStack Identity " +"documentation. When OpenStack Identity is enabled, it is not mandatory to " +"specify tenant_id for resources in create requests, as the tenant identifier" +" will be derived from the Authentication token. Please note that the default" +" authorization settings only allow administrative users to create resources " +"on behalf of a different tenant. OpenStack Networking uses information " +"received from OpenStack Identity to authorize user requests. OpenStack " +"Networking handles two kind of authorization policies:" +msgstr "" + +#: ./doc/training-guides/module002-ch004-security-in-neutron.xml54(para) +msgid "" +"Operation-based: policies specify access " +"criteria for specific operations, possibly with fine-grained control over " +"specific attributes;" +msgstr "" + +#: ./doc/training-guides/module002-ch004-security-in-neutron.xml60(para) +msgid "" +"Resource-based:whether access to specific" +" resource might be granted or not according to the permissions configured " +"for the resource (currently available only for the network resource). The " +"actual authorization policies enforced in OpenStack Networking might vary " +"from deployment to deployment." +msgstr "" + +#: ./doc/training-guides/module002-ch004-security-in-neutron.xml70(para) +msgid "" +"The policy engine reads entries from the policy.json file. The actual " +"location of this file might vary from distribution to distribution. Entries " +"can be updated while the system is running, and no service restart is " +"required. That is to say, every time the policy file is updated, the " +"policies will be automatically reloaded. Currently the only way of updating " +"such policies is to edit the policy file. Please note that in this section " +"we will use both the terms \"policy\" and \"rule\" to refer to objects which" +" are specified in the same way in the policy file; in other words, there are" +" no syntax differences between a rule and a policy. We will define a policy " +"something which is matched directly from the OpenStack Networking policy " +"engine, whereas we will define a rule as the elements of such policies which" +" are then evaluated. For instance in create_subnet: " +"[[\"admin_or_network_owner\"]], create_subnet is regarded as a policy, " +"whereas admin_or_network_owner is regarded as a rule." +msgstr "" + +#: ./doc/training-guides/module002-ch004-security-in-neutron.xml88(para) +msgid "" +"Policies are triggered by the OpenStack Networking policy engine whenever " +"one of them matches an OpenStack Networking API operation or a specific " +"attribute being used in a given operation. For instance the create_subnet " +"policy is triggered every time a POST /v2.0/subnets request is sent to the " +"OpenStack Networking server; on the other hand create_network:shared is " +"triggered every time the shared attribute is explicitly specified (and set " +"to a value different from its default) in a POST /v2.0/networks request. It " +"is also worth mentioning that policies can be also related to specific API " +"extensions; for instance extension:provider_network:set will be triggered if" +" the attributes defined by the Provider Network extensions are specified in " +"an API request." +msgstr "" + +#: ./doc/training-guides/module002-ch004-security-in-neutron.xml102(para) +msgid "" +"An authorization policy can be composed by one or more rules. If more rules " +"are specified, evaluation policy will be successful if any of the rules " +"evaluates successfully; if an API operation matches multiple policies, then " +"all the policies must evaluate successfully. Also, authorization rules are " +"recursive. Once a rule is matched, the rule(s) can be resolved to another " +"rule, until a terminal rule is reached." +msgstr "" + +#: ./doc/training-guides/module002-ch004-security-in-neutron.xml110(para) +msgid "" +"The OpenStack Networking policy engine currently defines the following kinds" +" of terminal rules:" +msgstr "" + +#: ./doc/training-guides/module002-ch004-security-in-neutron.xml114(para) +msgid "" +"Role-based rules: evaluate successfully " +"if the user submitting the request has the specified role. For instance " +"\"role:admin\"is successful if the user submitting the request is an " +"administrator." +msgstr "" + +#: ./doc/training-guides/module002-ch004-security-in-neutron.xml121(para) +msgid "" +"Field-based rules: evaluate successfully " +"if a field of the resource specified in the current request matches a " +"specific value. For instance \"field:networks:shared=True\" is successful if" +" the attribute shared of the network resource is set to true." +msgstr "" + +#: ./doc/training-guides/module002-ch004-security-in-neutron.xml130(para) +msgid "" +"Generic rules:compare an attribute in the" +" resource with an attribute extracted from the user's security credentials " +"and evaluates successfully if the comparison is successful. For instance " +"\"tenant_id:%(tenant_id)s\" is successful if the tenant identifier in the " +"resource is equal to the tenant identifier of the user submitting the " +"request." +msgstr "" + +#: ./doc/training-guides/module003-ch009-replication.xml8(para) +msgid "" +"Because each replica in swift functions independently, and clients generally" +" require only a simple majority of nodes responding to consider an operation" +" successful, transient failures like network partitions can quickly cause " +"replicas to diverge. These differences are eventually reconciled by " +"asynchronous, peer-to-peer replicator processes. The replicator processes " +"traverse their local filesystems, concurrently performing operations in a " +"manner that balances load across physical disks." +msgstr "" + +#: ./doc/training-guides/module003-ch009-replication.xml17(para) +msgid "" +"Replication uses a push model, with records and files generally only being " +"copied from local to remote replicas. This is important because data on the " +"node may not belong there (as in the case of handoffs and ring changes), and" +" a replicator can’t know what data exists elsewhere in the cluster that it " +"should pull in. It’s the duty of any node that contains data to ensure that " +"data gets to where it belongs. Replica placement is handled by the ring." +msgstr "" + +#: ./doc/training-guides/module003-ch009-replication.xml25(para) +msgid "" +"Every deleted record or file in the system is marked by a tombstone, so that" +" deletions can be replicated alongside creations. The replication process " +"cleans up tombstones after a time period known as the consistency window. " +"The consistency window encompasses replication duration and how long " +"transient failure can remove a node from the cluster. Tombstone cleanup must" +" be tied to replication to reach replica convergence." +msgstr "" + +#: ./doc/training-guides/module003-ch009-replication.xml33(para) +msgid "" +"If a replicator detects that a remote drive has failed, the replicator uses " +"the get_more_nodes interface for the ring to choose an alternate node with " +"which to synchronize. The replicator can maintain desired levels of " +"replication in the face of disk failures, though some replicas may not be in" +" an immediately usable location. Note that the replicator doesn’t maintain " +"desired levels of replication when other failures, such as entire node " +"failures occur, because most failure are transient." +msgstr "" + +#: ./doc/training-guides/module003-ch009-replication.xml42(para) +msgid "" +"Replication is an area of active development, and likely rife with potential" +" improvements to speed and accuracy." +msgstr "" + +#: ./doc/training-guides/module003-ch009-replication.xml45(para) +msgid "" +"There are two major classes of replicator - the db replicator, which " +"replicates accounts and containers, and the object replicator, which " +"replicates object data." +msgstr "" + +#: ./doc/training-guides/module003-ch009-replication.xml48(guilabel) +msgid "DB Replication" +msgstr "" + +#: ./doc/training-guides/module003-ch009-replication.xml49(para) +msgid "" +"The first step performed by db replication is a low-cost hash comparison to " +"determine whether two replicas already match. Under normal operation, this " +"check is able to verify that most databases in the system are already " +"synchronized very quickly. If the hashes differ, the replicator brings the " +"databases in sync by sharing records added since the last sync point." +msgstr "" + +#: ./doc/training-guides/module003-ch009-replication.xml56(para) +msgid "" +"This sync point is a high water mark noting the last record at which two " +"databases were known to be in sync, and is stored in each database as a " +"tuple of the remote database id and record id. Database ids are unique " +"amongst all replicas of the database, and record ids are monotonically " +"increasing integers. After all new records have been pushed to the remote " +"database, the entire sync table of the local database is pushed, so the " +"remote database can guarantee that it is in sync with everything with which " +"the local database has previously synchronized." +msgstr "" + +#: ./doc/training-guides/module003-ch009-replication.xml67(para) +msgid "" +"If a replica is found to be missing entirely, the whole local database file " +"is transmitted to the peer using rsync(1) and vested with a new unique id." +msgstr "" + +#: ./doc/training-guides/module003-ch009-replication.xml70(para) +msgid "" +"In practice, DB replication can process hundreds of databases per " +"concurrency setting per second (up to the number of available CPUs or disks)" +" and is bound by the number of DB transactions that must be performed." +msgstr "" + +#: ./doc/training-guides/module003-ch009-replication.xml74(guilabel) +msgid "Object Replication" +msgstr "" + +#: ./doc/training-guides/module003-ch009-replication.xml75(para) +msgid "" +"The initial implementation of object replication simply performed an rsync " +"to push data from a local partition to all remote servers it was expected to" +" exist on. While this performed adequately at small scale, replication times" +" skyrocketed once directory structures could no longer be held in RAM. We " +"now use a modification of this scheme in which a hash of the contents for " +"each suffix directory is saved to a per-partition hashes file. The hash for " +"a suffix directory is invalidated when the contents of that suffix directory" +" are modified." +msgstr "" + +#: ./doc/training-guides/module003-ch009-replication.xml85(para) +msgid "" +"The object replication process reads in these hash files, calculating any " +"invalidated hashes. It then transmits the hashes to each remote server that " +"should hold the partition, and only suffix directories with differing hashes" +" on the remote server are rsynced. After pushing files to the remote server," +" the replication process notifies it to recalculate hashes for the rsynced " +"suffix directories." +msgstr "" + +#: ./doc/training-guides/module003-ch009-replication.xml93(para) +msgid "" +"Performance of object replication is generally bound by the number of " +"uncached directories it has to traverse, usually as a result of invalidated " +"suffix directory hashes. Using write volume and partition counts from our " +"running systems, it was designed so that around 2% of the hash space on a " +"normal node will be invalidated per day, which has experimentally given us " +"acceptable replication speeds." +msgstr "" + +#: ./doc/training-guides/bk003-developer-training-guide.xml5(title) +msgid "Developer Training Guide" +msgstr "" + +#: ./doc/training-guides/bk003-developer-training-guide.xml8(title) +msgid "Developer Training Guide Coming Soon" +msgstr "" + +#: ./doc/training-guides/bk003-developer-training-guide.xml10(title) +msgid "Cinder Architecture" +msgstr "" + +#: ./doc/training-guides/bk003-developer-training-guide.xml17(title) +msgid "Cinder Architecture Components" +msgstr "" + +#: ./doc/training-guides/bk003-developer-training-guide.xml24(title) +msgid "Adding an API Method" +msgstr "" + +#: ./doc/training-guides/bk003-developer-training-guide.xml31(title) +msgid "Controllers" +msgstr "" + +#: ./doc/training-guides/bk003-developer-training-guide.xml38(title) +#: ./doc/training-guides/sources/cinder/addmethod.openstackapi.xml53(title) +msgid "Serialization" +msgstr "" + +#: ./doc/training-guides/bk003-developer-training-guide.xml45(title) +msgid "Development Environment" +msgstr "" + +#: ./doc/training-guides/bk003-developer-training-guide.xml52(title) +#: ./doc/training-guides/sources/cinder/drivers.xml7(title) +#: ./doc/training-guides/sources/cinder/drivers.xml26(title) +msgid "Drivers" +msgstr "" + +#: ./doc/training-guides/bk003-developer-training-guide.xml59(title) +#: ./doc/training-guides/sources/cinder/threading.xml7(title) +msgid "Threading" +msgstr "" + +#: ./doc/training-guides/bk003-developer-training-guide.xml66(title) +msgid "Unit Tests" +msgstr "" + +#: ./doc/training-guides/card011.xml7(title) +msgid "Installing MySQL" +msgstr "" + +#: ./doc/training-guides/bk001-bk010-associate-object-storage-node-quiz.xml7(title) +msgid "Day 2, 14:25 to 14:45" +msgstr "" + +#: ./doc/training-guides/lab004-openstack-production.xml7(title) +msgid "OpenStack In Production" +msgstr "" + +#: ./doc/training-guides/lab004-openstack-production.xml8(para) +msgid "More Content To be Added." +msgstr "" + +#: ./doc/training-guides/bk002-ch012-operator-network-node-quiz.xml6(title) +#: ./doc/training-guides/bk001-ch008-associate-network-node-quiz.xml6(title) +msgid "Network Node Quiz" +msgstr "" + +#: ./doc/training-guides/bk002-ch012-operator-network-node-quiz.xml8(title) +msgid "Days 7 to 8, 16:40 to 17:00" +msgstr "" + +#. When image changes, this message will be marked fuzzy or untranslated for +#. you. +#. It doesn't matter what you translate it to: it's not used at all. +#: ./doc/training-guides/lab000-virtualbox-basics.xml207(None) +msgid "" +"@@image: 'figures/lab000-virtual-box/image13.png'; " +"md5=eeaf2e523b991a592182c76fcfc29e07" +msgstr "" + +#. When image changes, this message will be marked fuzzy or untranslated for +#. you. +#. It doesn't matter what you translate it to: it's not used at all. +#: ./doc/training-guides/lab000-virtualbox-basics.xml251(None) +msgid "" +"@@image: 'figures/lab000-virtual-box/image19.png'; " +"md5=9a3c62ffc47b83ab5306820bd3a9a4fc" +msgstr "" + +#. When image changes, this message will be marked fuzzy or untranslated for +#. you. +#. It doesn't matter what you translate it to: it's not used at all. +#: ./doc/training-guides/lab000-virtualbox-basics.xml286(None) +msgid "" +"@@image: 'figures/lab000-virtual-box/image16.png'; " +"md5=bb1f3c80211fafd0ce737725ca39a6b3" +msgstr "" + +#. When image changes, this message will be marked fuzzy or untranslated for +#. you. +#. It doesn't matter what you translate it to: it's not used at all. +#: ./doc/training-guides/lab000-virtualbox-basics.xml320(None) +msgid "" +"@@image: 'figures/lab000-virtual-box/image08.png'; " +"md5=e52887e98a60caa87affd91d78ff6a4f" +msgstr "" + +#. When image changes, this message will be marked fuzzy or untranslated for +#. you. +#. It doesn't matter what you translate it to: it's not used at all. +#: ./doc/training-guides/lab000-virtualbox-basics.xml369(None) +msgid "" +"@@image: 'figures/lab000-virtual-box/image11.png'; " +"md5=f0799ccd13811e991932b79655efe63b" +msgstr "" + +#. When image changes, this message will be marked fuzzy or untranslated for +#. you. +#. It doesn't matter what you translate it to: it's not used at all. +#: ./doc/training-guides/lab000-virtualbox-basics.xml409(None) +msgid "" +"@@image: 'figures/lab000-virtual-box/image07.png'; " +"md5=dc8a7ca4a721116dad4d808efdcd0158" +msgstr "" + +#. When image changes, this message will be marked fuzzy or untranslated for +#. you. +#. It doesn't matter what you translate it to: it's not used at all. +#: ./doc/training-guides/lab000-virtualbox-basics.xml418(None) +msgid "" +"@@image: 'figures/lab000-virtual-box/image18.png'; " +"md5=cc6c10310380102b418c665047c0539c" +msgstr "" + +#. When image changes, this message will be marked fuzzy or untranslated for +#. you. +#. It doesn't matter what you translate it to: it's not used at all. +#: ./doc/training-guides/lab000-virtualbox-basics.xml427(None) +msgid "" +"@@image: 'figures/lab000-virtual-box/image14.png'; " +"md5=469f15068705c1a40cb5504cc2a8e5dd" +msgstr "" + +#. When image changes, this message will be marked fuzzy or untranslated for +#. you. +#. It doesn't matter what you translate it to: it's not used at all. +#: ./doc/training-guides/lab000-virtualbox-basics.xml446(None) +msgid "" +"@@image: 'figures/lab000-virtual-box/image12.png'; " +"md5=266a767b48f2c3eba60b67e01a1c6cc5" +msgstr "" + +#. When image changes, this message will be marked fuzzy or untranslated for +#. you. +#. It doesn't matter what you translate it to: it's not used at all. +#: ./doc/training-guides/lab000-virtualbox-basics.xml488(None) +msgid "" +"@@image: 'figures/lab000-virtual-box/image05.png'; " +"md5=c711ea21fcc2b1e18d9d41375bc9a713" +msgstr "" + +#. When image changes, this message will be marked fuzzy or untranslated for +#. you. +#. It doesn't matter what you translate it to: it's not used at all. +#: ./doc/training-guides/lab000-virtualbox-basics.xml497(None) +msgid "" +"@@image: 'figures/lab000-virtual-box/image17.png'; " +"md5=9077ae7ff15e88187de9941fd8c7db5f" +msgstr "" + +#. When image changes, this message will be marked fuzzy or untranslated for +#. you. +#. It doesn't matter what you translate it to: it's not used at all. +#: ./doc/training-guides/lab000-virtualbox-basics.xml506(None) +msgid "" +"@@image: 'figures/lab000-virtual-box/image02.png'; " +"md5=001129ba8b8030bbf1ca9e23805d9b84" +msgstr "" + +#. When image changes, this message will be marked fuzzy or untranslated for +#. you. +#. It doesn't matter what you translate it to: it's not used at all. +#: ./doc/training-guides/lab000-virtualbox-basics.xml515(None) +msgid "" +"@@image: 'figures/lab000-virtual-box/image00.png'; " +"md5=e90be704c41d381dedab6f8fb3b8c391" +msgstr "" + +#. When image changes, this message will be marked fuzzy or untranslated for +#. you. +#. It doesn't matter what you translate it to: it's not used at all. +#: ./doc/training-guides/lab000-virtualbox-basics.xml533(None) +msgid "" +"@@image: 'figures/lab000-virtual-box/image04.png'; " +"md5=8577d54796c8479a2f089ee09846e130" +msgstr "" + +#. When image changes, this message will be marked fuzzy or untranslated for +#. you. +#. It doesn't matter what you translate it to: it's not used at all. +#: ./doc/training-guides/lab000-virtualbox-basics.xml570(None) +msgid "" +"@@image: 'figures/lab000-virtual-box/image15.png'; " +"md5=2d2b9eb2d913030490694d3df8c26c20" +msgstr "" + +#. When image changes, this message will be marked fuzzy or untranslated for +#. you. +#. It doesn't matter what you translate it to: it's not used at all. +#: ./doc/training-guides/lab000-virtualbox-basics.xml579(None) +msgid "" +"@@image: 'figures/lab000-virtual-box/image10.png'; " +"md5=4f06faaf244be263d90b41855b10d62a" +msgstr "" + +#. When image changes, this message will be marked fuzzy or untranslated for +#. you. +#. It doesn't matter what you translate it to: it's not used at all. +#: ./doc/training-guides/lab000-virtualbox-basics.xml588(None) +msgid "" +"@@image: 'figures/lab000-virtual-box/image01.png'; " +"md5=1eb33f35a0af357f7e96fa03830d49c0" +msgstr "" + +#: ./doc/training-guides/lab000-virtualbox-basics.xml7(title) +msgid "VirtualBox Basics" +msgstr "" + +#: ./doc/training-guides/lab000-virtualbox-basics.xml9(para) +msgid "" +"The following are the conventional methods of deploying OpenStack on Virtual" +" Box for the sake of a test/sandbox or just to try out OpenStack on " +"commodity hardware." +msgstr "" + +#: ./doc/training-guides/lab000-virtualbox-basics.xml12(para) +msgid "1. DevStack" +msgstr "" + +#: ./doc/training-guides/lab000-virtualbox-basics.xml13(para) +msgid "2. Vagrant" +msgstr "" + +#: ./doc/training-guides/lab000-virtualbox-basics.xml14(para) +msgid "" +"But DevStack and Vagrant bring in some level of automated deployment as " +"running the scripts will get your VirtualBox Instance configured as the " +"required OpenStack deployment. We will be manually deploying OpenStack on " +"VirtualBox Instance to get better view of how OpenStack works." +msgstr "" + +#: ./doc/training-guides/lab000-virtualbox-basics.xml19(guilabel) +msgid "Prerequisite:" +msgstr "" + +#: ./doc/training-guides/lab000-virtualbox-basics.xml20(para) +msgid "" +"Well, its a daunting task to just cover all of OpenStack’s concepts let " +"alone Virtualization and Networking. So some basic idea/knowledge on " +"Virtualization, Networking and Linux is required. Even though I will try to " +"keep the level as low as possible for making it easy for Linux Newbies as " +"well as experts." +msgstr "" + +#: ./doc/training-guides/lab000-virtualbox-basics.xml26(para) +msgid "" +"These Virtual Machines and Virtual Networks will be given equal privilege as" +" a physical machine on a physical network." +msgstr "" + +#: ./doc/training-guides/lab000-virtualbox-basics.xml29(para) +msgid "" +"Just for those who would want to do a deeper research or study, for more " +"information you may refer the following links" +msgstr "" + +#: ./doc/training-guides/lab000-virtualbox-basics.xml32(para) +msgid "" +"OpenStack:OpenStack Official " +"Documentation (docs.openstack.org)" +msgstr "" + +#: ./doc/training-guides/lab000-virtualbox-basics.xml34(para) +msgid "" +"Networking:Computer Networks (5th " +"Edition) by Andrew S. Tanenbaum" +msgstr "" + +#: ./doc/training-guides/lab000-virtualbox-basics.xml36(para) +msgid "" +"VirtualBox:Virtual Box Manual " +"(http://www.virtualbox.org/manual/UserManual.html)" +msgstr "" + +#: ./doc/training-guides/lab000-virtualbox-basics.xml38(emphasis) +msgid "Requirements :" +msgstr "" + +#: ./doc/training-guides/lab000-virtualbox-basics.xml39(para) +msgid "" +"Operating Systems - I recommend Ubuntu Server 12.04 LTS, Ubuntu Server 13.10" +" or Debian Wheezy" +msgstr "" + +#: ./doc/training-guides/lab000-virtualbox-basics.xml41(para) +msgid "" +"Note :Ubuntu 12.10 is not supporting " +"OpenStack Grizzly Packages. Ubuntu team has decided not to package Grizzly " +"Packages for Ubuntu 12.10." +msgstr "" + +#: ./doc/training-guides/lab000-virtualbox-basics.xml46(para) +msgid "Recommended Requirements." +msgstr "" + +#: ./doc/training-guides/lab000-virtualbox-basics.xml52(td) +msgid "VT Enabled PC:" +msgstr "" + +#: ./doc/training-guides/lab000-virtualbox-basics.xml53(td) +msgid "Intel ix or Amd QuadCore" +msgstr "" + +#: ./doc/training-guides/lab000-virtualbox-basics.xml56(td) +msgid "4GB Ram:" +msgstr "" + +#: ./doc/training-guides/lab000-virtualbox-basics.xml57(td) +#: ./doc/training-guides/lab000-virtualbox-basics.xml75(td) +msgid "DDR2/DDR3" +msgstr "" + +#: ./doc/training-guides/lab000-virtualbox-basics.xml63(para) +msgid "Minimum Requirements." +msgstr "" + +#: ./doc/training-guides/lab000-virtualbox-basics.xml69(td) +msgid "Non-VT PC's:" +msgstr "" + +#: ./doc/training-guides/lab000-virtualbox-basics.xml70(td) +msgid "Intel Core 2 Duo or Amd Dual Core" +msgstr "" + +#: ./doc/training-guides/lab000-virtualbox-basics.xml74(td) +msgid "2GB Ram:" +msgstr "" + +#: ./doc/training-guides/lab000-virtualbox-basics.xml79(para) +msgid "" +"If you don't know whether your processor is VT enabled, you could check it " +"by installing cpu checker" +msgstr "" + +#: ./doc/training-guides/lab000-virtualbox-basics.xml84(td) +msgid "$sudo apt-get install cpu-checker" +msgstr "" + +#: ./doc/training-guides/lab000-virtualbox-basics.xml88(td) +msgid "$sudo kvm-ok" +msgstr "" + +#: ./doc/training-guides/lab000-virtualbox-basics.xml92(para) +msgid "If your device does not support VT it will show" +msgstr "" + +#: ./doc/training-guides/lab000-virtualbox-basics.xml93(para) +msgid "INFO:Your CPU does not support KVM extensions" +msgstr "" + +#: ./doc/training-guides/lab000-virtualbox-basics.xml94(para) +msgid "KVM acceleration can NOT be used" +msgstr "" + +#: ./doc/training-guides/lab000-virtualbox-basics.xml95(para) +msgid "" +"You will still be able to use Virtual Box but the instances will be very " +"slow." +msgstr "" + +#: ./doc/training-guides/lab000-virtualbox-basics.xml97(para) +msgid "" +"There are many ways to configure your OpenStack Setup, we will be deploying " +"OpenStack Multi Node using OVS as the Network Plugin and QEMU/ KVM as the " +"hypervisor." +msgstr "" + +#: ./doc/training-guides/lab000-virtualbox-basics.xml100(emphasis) +msgid "Host Only Connections:" +msgstr "" + +#: ./doc/training-guides/lab000-virtualbox-basics.xml103(para) +msgid "" +"Host only connections provide an Internal network between your host and the " +"Virtual Machine instances up and running on your host machine.This network " +"is not traceable by other networks." +msgstr "" + +#: ./doc/training-guides/lab000-virtualbox-basics.xml109(para) +msgid "" +"You may even use Bridged connection if you have a router/switch. I am " +"assuming the worst case (one IP without any router), so that it is simple to" +" get the required networks running without the hassle of IP tables." +msgstr "" + +#: ./doc/training-guides/lab000-virtualbox-basics.xml115(para) +msgid "" +"The following are the host only connections that you will be setting up " +"later on :" +msgstr "" + +#: ./doc/training-guides/lab000-virtualbox-basics.xml121(para) +msgid "vboxnet0 - OpenStack Management Network - Host static IP 10.10.10.1" +msgstr "" + +#: ./doc/training-guides/lab000-virtualbox-basics.xml125(para) +msgid "vboxnet1 - VM Conf.Network - Host Static IP 10.20.20.1" +msgstr "" + +#: ./doc/training-guides/lab000-virtualbox-basics.xml129(para) +msgid "vboxnet2 - VM External Network Access (Host Machine) 192.168.100.1" +msgstr "" + +#: ./doc/training-guides/lab000-virtualbox-basics.xml142(para) +msgid "" +"Vboxnet0, Vboxnet1, Vboxnet2 - are virtual networks setup up by virtual box " +"with your host machine. This is the way your host can communicate with the " +"virtual machines. These networks are in turn used by virtual box VM’s for " +"OpenStack networks, so that OpenStack’s services can communicate with each " +"other." +msgstr "" + +#: ./doc/training-guides/lab000-virtualbox-basics.xml147(guilabel) +msgid "Setup Your VM Environment" +msgstr "" + +#: ./doc/training-guides/lab000-virtualbox-basics.xml148(para) +msgid "" +"Before you can start configuring your Environment you need to download some " +"of the following stuff:" +msgstr "" + +#: ./doc/training-guides/lab000-virtualbox-basics.xml153(link) +msgid "Oracle Virtual Box" +msgstr "" + +#: ./doc/training-guides/lab000-virtualbox-basics.xml157(para) +msgid "Note:You cannot set up a amd64 VM on a x86 machine." +msgstr "" + +#: ./doc/training-guides/lab000-virtualbox-basics.xml160(link) +msgid "Ubuntu 12.04 Server or Ubuntu 13.04 Server" +msgstr "" + +#: ./doc/training-guides/lab000-virtualbox-basics.xml164(para) +msgid "" +"Note:You need a x86 image for VM's if kvm-ok fails, even though you are on " +"amd64 machine." +msgstr "" + +#: ./doc/training-guides/lab000-virtualbox-basics.xml166(para) +msgid "" +"Note: Even Though I'm using Ubuntu as Host, the same is applicable to " +"Windows, Mac and other Linux Hosts." +msgstr "" + +#: ./doc/training-guides/lab000-virtualbox-basics.xml170(para) +msgid "" +"If you have i5 or i7 2nd gen processor you can have VT technology inside " +"VM's provided by VmWare. This means that your OpenStack nodes(Which are in " +"turn VM's) will give positive result on KVM-OK. (I call it - Nesting of " +"type-2 Hypervisors). Rest of the configurations remain same except for the " +"UI and few other trivial differences." +msgstr "" + +#: ./doc/training-guides/lab000-virtualbox-basics.xml178(guilabel) +msgid "Configure Virtual Networks" +msgstr "" + +#: ./doc/training-guides/lab000-virtualbox-basics.xml181(para) +msgid "" +"This section of the guide will help you setup your networks for your Virtual" +" Machine." +msgstr "" + +#: ./doc/training-guides/lab000-virtualbox-basics.xml185(para) +msgid "Launch Virtual Box" +msgstr "" + +#: ./doc/training-guides/lab000-virtualbox-basics.xml190(para) +msgid "" +"Click on File>Preferences present on " +"the menu bar of Virtual Box." +msgstr "" + +#: ./doc/training-guides/lab000-virtualbox-basics.xml195(para) +msgid "Select the Network tab." +msgstr "" + +#: ./doc/training-guides/lab000-virtualbox-basics.xml199(para) +msgid "On the right side you will see an option to add Host-Only networks." +msgstr "" + +#: ./doc/training-guides/lab000-virtualbox-basics.xml204(title) +msgid "Create Host Only Networks" +msgstr "" + +#: ./doc/training-guides/lab000-virtualbox-basics.xml213(para) +msgid "Create three Host-Only Network Connections. As shown above." +msgstr "" + +#: ./doc/training-guides/lab000-virtualbox-basics.xml217(para) +msgid "Edit the Host-Only Connections to have the following settings." +msgstr "" + +#: ./doc/training-guides/lab000-virtualbox-basics.xml221(emphasis) +#: ./doc/training-guides/lab000-virtualbox-basics.xml248(title) +#: ./doc/training-guides/lab000-virtualbox-basics.xml389(td) +#: ./doc/training-guides/lab000-virtualbox-basics.xml463(td) +#: ./doc/training-guides/lab000-virtualbox-basics.xml550(td) +msgid "Vboxnet0" +msgstr "" + +#: ./doc/training-guides/lab000-virtualbox-basics.xml226(th) +#: ./doc/training-guides/lab000-virtualbox-basics.xml261(th) +#: ./doc/training-guides/lab000-virtualbox-basics.xml295(th) +msgid "Option" +msgstr "" + +#: ./doc/training-guides/lab000-virtualbox-basics.xml227(th) +#: ./doc/training-guides/lab000-virtualbox-basics.xml262(th) +#: ./doc/training-guides/lab000-virtualbox-basics.xml296(th) +msgid "Value" +msgstr "" + +#: ./doc/training-guides/lab000-virtualbox-basics.xml230(td) +#: ./doc/training-guides/lab000-virtualbox-basics.xml265(td) +#: ./doc/training-guides/lab000-virtualbox-basics.xml299(td) +msgid "IPv4 Address:" +msgstr "" + +#: ./doc/training-guides/lab000-virtualbox-basics.xml231(td) +msgid "10.10.10.1" +msgstr "" + +#: ./doc/training-guides/lab000-virtualbox-basics.xml234(td) +#: ./doc/training-guides/lab000-virtualbox-basics.xml269(td) +#: ./doc/training-guides/lab000-virtualbox-basics.xml303(td) +msgid "IPv4 Network Mask:" +msgstr "" + +#: ./doc/training-guides/lab000-virtualbox-basics.xml235(td) +#: ./doc/training-guides/lab000-virtualbox-basics.xml270(td) +#: ./doc/training-guides/lab000-virtualbox-basics.xml304(td) +msgid "255.255.255.0" +msgstr "" + +#: ./doc/training-guides/lab000-virtualbox-basics.xml238(td) +#: ./doc/training-guides/lab000-virtualbox-basics.xml273(td) +#: ./doc/training-guides/lab000-virtualbox-basics.xml307(td) +msgid "IPv6 Address:" +msgstr "" + +#: ./doc/training-guides/lab000-virtualbox-basics.xml239(td) +#: ./doc/training-guides/lab000-virtualbox-basics.xml243(td) +#: ./doc/training-guides/lab000-virtualbox-basics.xml274(td) +#: ./doc/training-guides/lab000-virtualbox-basics.xml278(td) +#: ./doc/training-guides/lab000-virtualbox-basics.xml308(td) +#: ./doc/training-guides/lab000-virtualbox-basics.xml312(td) +msgid "Can be Left Blank" +msgstr "" + +#: ./doc/training-guides/lab000-virtualbox-basics.xml242(td) +#: ./doc/training-guides/lab000-virtualbox-basics.xml277(td) +#: ./doc/training-guides/lab000-virtualbox-basics.xml311(td) +msgid "IPv6 Network Mask Length :" +msgstr "" + +#: ./doc/training-guides/lab000-virtualbox-basics.xml255(emphasis) +#: ./doc/training-guides/lab000-virtualbox-basics.xml283(title) +#: ./doc/training-guides/lab000-virtualbox-basics.xml468(td) +#: ./doc/training-guides/lab000-virtualbox-basics.xml555(td) +msgid "Vboxnet1" +msgstr "" + +#: ./doc/training-guides/lab000-virtualbox-basics.xml266(td) +msgid "10.20.20.1" +msgstr "" + +#: ./doc/training-guides/lab000-virtualbox-basics.xml290(emphasis) +#: ./doc/training-guides/lab000-virtualbox-basics.xml394(td) +#: ./doc/training-guides/lab000-virtualbox-basics.xml473(td) +msgid "Vboxnet2" +msgstr "" + +#: ./doc/training-guides/lab000-virtualbox-basics.xml300(td) +msgid "192.168.100.1" +msgstr "" + +#: ./doc/training-guides/lab000-virtualbox-basics.xml317(title) +msgid "Image: Vboxnet2" +msgstr "" + +#: ./doc/training-guides/lab000-virtualbox-basics.xml324(guilabel) +msgid "Install SSH and FTP" +msgstr "" + +#: ./doc/training-guides/lab000-virtualbox-basics.xml327(para) +msgid "" +"You may benefit by installing SSH and FTP so that you could use your remote " +"shell to login into the machine and use your terminal which is more " +"convenient that using the Virtual Machines tty through the Virtual Box's UI." +" You get a few added comforts like copy - paste commands into the remote " +"terminal which is not possible directly on VM." +msgstr "" + +#: ./doc/training-guides/lab000-virtualbox-basics.xml335(para) +msgid "" +"FTP is for transferring files to and fro ... you can also use SFTP or " +"install FTPD on both HOST and VM's." +msgstr "" + +#: ./doc/training-guides/lab000-virtualbox-basics.xml339(para) +msgid "" +"Installation of SSH and FTP with its configuration is out of scope of this " +"GUIDE and I may put it up but it depends upon my free time. If someone wants" +" to contribute to this - please do so." +msgstr "" + +#: ./doc/training-guides/lab000-virtualbox-basics.xml345(para) +msgid "" +"Note:Please set up the Networks from " +"inside the VM before trying to SSH and FTP into the machines. I would " +"suggest setting it up at once just after the installation of the Server on " +"VM's is over." +msgstr "" + +#: ./doc/training-guides/lab000-virtualbox-basics.xml349(guilabel) +msgid "Install Your VM's Instances" +msgstr "" + +#: ./doc/training-guides/lab000-virtualbox-basics.xml352(para) +msgid "" +"During Installation of The Operating Systems you will be asked for Custom " +"Software to Install , if you are confused or not sure about this, just skip " +"this step by pressing Enter Key without selecting any of the given Options." +msgstr "" + +#: ./doc/training-guides/lab000-virtualbox-basics.xml358(para) +msgid "" +"Warning - Please do not install any of " +"the other packages except for which are mentioned below unless you know what" +" you are doing. There is a good chance that you may end up getting unwanted " +"errors, package conflicts ... due to the same." +msgstr "" + +#: ./doc/training-guides/lab000-virtualbox-basics.xml363(guilabel) +msgid "Control Node:" +msgstr "" + +#: ./doc/training-guides/lab000-virtualbox-basics.xml364(para) +msgid "Create a new virtual machine. Select Ubuntu Server" +msgstr "" + +#: ./doc/training-guides/lab000-virtualbox-basics.xml366(title) +#: ./doc/training-guides/lab000-virtualbox-basics.xml443(title) +#: ./doc/training-guides/lab000-virtualbox-basics.xml530(title) +msgid "Create New Virtual Machine" +msgstr "" + +#: ./doc/training-guides/lab000-virtualbox-basics.xml373(para) +msgid "" +"Select appropriate RAM, minimum 512 MB of RAM for Control Node. Rest all can" +" be default settings. The hard disk size can be 8GB as default." +msgstr "" + +#: ./doc/training-guides/lab000-virtualbox-basics.xml376(para) +#: ./doc/training-guides/lab000-virtualbox-basics.xml450(para) +#: ./doc/training-guides/lab000-virtualbox-basics.xml537(para) +msgid "Configure the networks" +msgstr "" + +#: ./doc/training-guides/lab000-virtualbox-basics.xml377(para) +#: ./doc/training-guides/lab000-virtualbox-basics.xml451(para) +#: ./doc/training-guides/lab000-virtualbox-basics.xml538(para) +msgid "(Ignore the IP Address for now, you will set it up from inside the VM)" +msgstr "" + +#: ./doc/training-guides/lab000-virtualbox-basics.xml383(th) +#: ./doc/training-guides/lab000-virtualbox-basics.xml457(th) +#: ./doc/training-guides/lab000-virtualbox-basics.xml544(th) +msgid "Network Adapter" +msgstr "" + +#: ./doc/training-guides/lab000-virtualbox-basics.xml384(th) +#: ./doc/training-guides/lab000-virtualbox-basics.xml458(th) +#: ./doc/training-guides/lab000-virtualbox-basics.xml545(th) +msgid "Host-Only Adapter Name" +msgstr "" + +#: ./doc/training-guides/lab000-virtualbox-basics.xml385(th) +#: ./doc/training-guides/lab000-virtualbox-basics.xml459(th) +#: ./doc/training-guides/lab000-virtualbox-basics.xml546(th) +msgid "IP Address" +msgstr "" + +#: ./doc/training-guides/lab000-virtualbox-basics.xml388(td) +#: ./doc/training-guides/lab000-virtualbox-basics.xml462(td) +#: ./doc/training-guides/lab000-virtualbox-basics.xml549(td) +msgid "eth0" +msgstr "" + +#: ./doc/training-guides/lab000-virtualbox-basics.xml390(td) +msgid "10.10.10.51" +msgstr "" + +#: ./doc/training-guides/lab000-virtualbox-basics.xml393(td) +#: ./doc/training-guides/lab000-virtualbox-basics.xml467(td) +#: ./doc/training-guides/lab000-virtualbox-basics.xml554(td) +msgid "eth1" +msgstr "" + +#: ./doc/training-guides/lab000-virtualbox-basics.xml395(td) +#: ./doc/training-guides/lab000-virtualbox-basics.xml474(td) +msgid "192.168.100.51" +msgstr "" + +#: ./doc/training-guides/lab000-virtualbox-basics.xml398(td) +#: ./doc/training-guides/lab000-virtualbox-basics.xml472(td) +#: ./doc/training-guides/lab000-virtualbox-basics.xml559(td) +msgid "eth2" +msgstr "" + +#: ./doc/training-guides/lab000-virtualbox-basics.xml399(td) +#: ./doc/training-guides/lab000-virtualbox-basics.xml478(td) +#: ./doc/training-guides/lab000-virtualbox-basics.xml560(td) +msgid "NAT" +msgstr "" + +#: ./doc/training-guides/lab000-virtualbox-basics.xml400(td) +#: ./doc/training-guides/lab000-virtualbox-basics.xml479(td) +#: ./doc/training-guides/lab000-virtualbox-basics.xml561(td) +msgid "DHCP" +msgstr "" + +#: ./doc/training-guides/lab000-virtualbox-basics.xml404(emphasis) +#: ./doc/training-guides/lab000-virtualbox-basics.xml483(emphasis) +#: ./doc/training-guides/lab000-virtualbox-basics.xml565(emphasis) +msgid "Adapter 1 (Vboxnet0)" +msgstr "" + +#: ./doc/training-guides/lab000-virtualbox-basics.xml406(title) +#: ./doc/training-guides/lab000-virtualbox-basics.xml567(title) +msgid "Adapter1 - Vboxnet0" +msgstr "" + +#: ./doc/training-guides/lab000-virtualbox-basics.xml413(emphasis) +msgid "Adapter 2 (Vboxnet2)" +msgstr "" + +#: ./doc/training-guides/lab000-virtualbox-basics.xml415(title) +msgid "Adapter2 - Vboxnet2" +msgstr "" + +#: ./doc/training-guides/lab000-virtualbox-basics.xml422(emphasis) +#: ./doc/training-guides/lab000-virtualbox-basics.xml583(emphasis) +msgid "Adapter 3 (NAT)" +msgstr "" + +#: ./doc/training-guides/lab000-virtualbox-basics.xml424(title) +#: ./doc/training-guides/lab000-virtualbox-basics.xml585(title) +msgid "Adapter3 - NAT" +msgstr "" + +#: ./doc/training-guides/lab000-virtualbox-basics.xml431(para) +#: ./doc/training-guides/lab000-virtualbox-basics.xml519(para) +#: ./doc/training-guides/lab000-virtualbox-basics.xml592(para) +msgid "Now Install Ubuntu Server 12.04 or 13.04 on this machine." +msgstr "" + +#: ./doc/training-guides/lab000-virtualbox-basics.xml433(para) +#: ./doc/training-guides/lab000-virtualbox-basics.xml521(para) +#: ./doc/training-guides/lab000-virtualbox-basics.xml594(para) +msgid "" +"Note :Install SSH server when asked for " +"Custom Software to Install. Rest of the packages are not required and may " +"come in the way of OpenStack packages - like DNS servers etc. (not " +"necessary). Unless you know what you are doing." +msgstr "" + +#: ./doc/training-guides/lab000-virtualbox-basics.xml438(guilabel) +msgid "Network Node:" +msgstr "" + +#: ./doc/training-guides/lab000-virtualbox-basics.xml439(para) +msgid "Create a new Virtual Machine," +msgstr "" + +#: ./doc/training-guides/lab000-virtualbox-basics.xml440(para) +msgid "" +"Minimum RAM is 512MB. Rest all can be left default. Minimum HDD space 8GB." +msgstr "" + +#: ./doc/training-guides/lab000-virtualbox-basics.xml464(td) +msgid "10.10.10.52" +msgstr "" + +#: ./doc/training-guides/lab000-virtualbox-basics.xml469(td) +msgid "10.20.20.52" +msgstr "" + +#: ./doc/training-guides/lab000-virtualbox-basics.xml477(td) +msgid "eth3" +msgstr "" + +#: ./doc/training-guides/lab000-virtualbox-basics.xml485(title) +msgid "Adapter 1 - Vboxnet0" +msgstr "" + +#: ./doc/training-guides/lab000-virtualbox-basics.xml492(emphasis) +#: ./doc/training-guides/lab000-virtualbox-basics.xml574(emphasis) +msgid "Adapter 2 (Vboxnet1)" +msgstr "" + +#: ./doc/training-guides/lab000-virtualbox-basics.xml494(title) +#: ./doc/training-guides/lab000-virtualbox-basics.xml576(title) +msgid "Adapter2 - Vboxnet1" +msgstr "" + +#: ./doc/training-guides/lab000-virtualbox-basics.xml501(emphasis) +msgid "Adapter 3 (Vboxnet2)" +msgstr "" + +#: ./doc/training-guides/lab000-virtualbox-basics.xml503(title) +msgid "Adapter3 - Vboxnet2" +msgstr "" + +#: ./doc/training-guides/lab000-virtualbox-basics.xml510(emphasis) +msgid "Adapter 4 (NAT)" +msgstr "" + +#: ./doc/training-guides/lab000-virtualbox-basics.xml512(title) +msgid "Adapter4 - NAT" +msgstr "" + +#: ./doc/training-guides/lab000-virtualbox-basics.xml526(guilabel) +msgid "Compute Node:" +msgstr "" + +#: ./doc/training-guides/lab000-virtualbox-basics.xml527(para) +msgid "" +"Create a new virtual machine, give it atleast 1,000 MB RAM. Rest all can be " +"left as defaults. Give atleast 8GB HDD." +msgstr "" + +#: ./doc/training-guides/lab000-virtualbox-basics.xml551(td) +msgid "10.10.10.53" +msgstr "" + +#: ./doc/training-guides/lab000-virtualbox-basics.xml556(td) +msgid "10.20.20.53" +msgstr "" + +#: ./doc/training-guides/lab000-virtualbox-basics.xml599(guilabel) +msgid "Warnings/Advice :" +msgstr "" + +#: ./doc/training-guides/lab000-virtualbox-basics.xml602(para) +msgid "" +"Well there are a few warnings that I must give you out of experience due to " +"common habits that most people may have :" +msgstr "" + +#: ./doc/training-guides/lab000-virtualbox-basics.xml607(para) +msgid "" +"Sometimes shutting down your Virtual Machine may lead to malfunctioning of " +"OpenStack Services. Try not to direct shutdown your 3. In case your VM's " +"don't get internet." +msgstr "" + +#: ./doc/training-guides/lab000-virtualbox-basics.xml612(para) +msgid "From your VM Instance, Use ping command to see whether Internet is on." +msgstr "" + +#: ./doc/training-guides/lab000-virtualbox-basics.xml619(para) +msgid "If its not connected, restart networking service-" +msgstr "" + +#: ./doc/training-guides/lab000-virtualbox-basics.xml627(para) +msgid "" +"If this doesn't work, you need to check your network settings from Virtual " +"Box, you may have left something or misconfigured it." +msgstr "" + +#: ./doc/training-guides/lab000-virtualbox-basics.xml632(para) +msgid "" +"This should reconnect your network about 99% of the times. If you are really" +" unlucky you must be having some other problems or your Internet connection " +"itself is not functioning." +msgstr "" + +#: ./doc/training-guides/lab000-virtualbox-basics.xml638(para) +msgid "" +"Note :There are known bugs with the ping under NAT. Although the latest " +"versions of Virtual Box have better performance, sometimes ping may not work" +" even if your Network is connected to internet." +msgstr "" + +#: ./doc/training-guides/lab000-virtualbox-basics.xml644(para) +msgid "" +"Congrats, you are ready with the infrastructure for deploying OpenStack. " +"Just make sure that you have installed Ubuntu Server on the above setup " +"Virtual Box Instances. In the next section we will go through deploying " +"OpenStack using the above created Virtual Box instances." +msgstr "" + +#: ./doc/training-guides/bk001-ch007-associate-network-node.xml10(title) +msgid "Day 2, 09:00 to 11:00" +msgstr "" + +#: ./doc/training-guides/bk001-ch007-associate-network-node.xml30(title) +msgid "Network CLI Commands" +msgstr "" + +#: ./doc/training-guides/bk001-ch007-associate-network-node.xml37(title) +msgid "Manage Networks" +msgstr "" + +#: ./doc/training-guides/bk001-ch008-associate-network-node-quiz.xml8(title) +msgid "Day 2, 10:40 to 11:00" +msgstr "" + +#: ./doc/training-guides/bk002-ch006-operator-controller-node-quiz.xml8(title) +msgid "Days 2 to 4, 16:40 to 17:00" +msgstr "" + +#: ./doc/training-guides/card070-create-floating-ips.xml7(title) +msgid "Create floating ip" +msgstr "" + +#: ./doc/training-guides/module003-ch005-the-ring.xml7(title) +msgid "Ring Builder" +msgstr "" + +#: ./doc/training-guides/module003-ch005-the-ring.xml8(para) +msgid "" +"The rings are built and managed manually by a utility called the ring-" +"builder. The ring-builder assigns partitions to devices and writes an " +"optimized Python structure to a gzipped, serialized file on disk for " +"shipping out to the servers. The server processes just check the " +"modification time of the file occasionally and reload their in-memory copies" +" of the ring structure as needed. Because of how the ring-builder manages " +"changes to the ring, using a slightly older ring usually just means one of " +"the three replicas for a subset of the partitions will be incorrect, which " +"can be easily worked around." +msgstr "" + +#: ./doc/training-guides/module003-ch005-the-ring.xml18(para) +msgid "" +"The ring-builder also keeps its own builder file with the ring information " +"and additional data required to build future rings. It is very important to " +"keep multiple backup copies of these builder files. One option is to copy " +"the builder files out to every server while copying the ring files " +"themselves. Another is to upload the builder files into the cluster itself. " +"Complete loss of a builder file will mean creating a new ring from scratch, " +"nearly all partitions will end up assigned to different devices, and " +"therefore nearly all data stored will have to be replicated to new " +"locations. So, recovery from a builder file loss is possible, but data will " +"definitely be unreachable for an extended time." +msgstr "" + +#: ./doc/training-guides/module003-ch005-the-ring.xml30(guilabel) +msgid "Ring Data Structure" +msgstr "" + +#: ./doc/training-guides/module003-ch005-the-ring.xml31(para) +msgid "" +"The ring data structure consists of three top level fields: a list of " +"devices in the cluster, a list of lists of device ids indicating partition " +"to device assignments, and an integer indicating the number of bits to shift" +" an MD5 hash to calculate the partition for the hash." +msgstr "" + +#: ./doc/training-guides/module003-ch005-the-ring.xml36(guilabel) +msgid "Partition Assignment List" +msgstr "" + +#: ./doc/training-guides/module003-ch005-the-ring.xml38(para) +msgid "" +"This is a list of array(‘H’) of devices ids. The outermost list contains an " +"array(‘H’) for each replica. Each array(‘H’) has a length equal to the " +"partition count for the ring. Each integer in the array(‘H’) is an index " +"into the above list of devices. The partition list is known internally to " +"the Ring class as _replica2part2dev_id." +msgstr "" + +#: ./doc/training-guides/module003-ch005-the-ring.xml45(para) +msgid "" +"So, to create a list of device dictionaries assigned to a partition, the " +"Python code would look like: devices = [self.devs[part2dev_id[partition]] " +"for part2dev_id in self._replica2part2dev_id]" +msgstr "" + +#: ./doc/training-guides/module003-ch005-the-ring.xml49(para) +msgid "" +"That code is a little simplistic, as it does not account for the removal of " +"duplicate devices. If a ring has more replicas than devices, then a " +"partition will have more than one replica on one device; that’s simply the " +"pigeonhole principle at work." +msgstr "" + +#: ./doc/training-guides/module003-ch005-the-ring.xml54(para) +msgid "" +"array(‘H’) is used for memory conservation as there may be millions of " +"partitions." +msgstr "" + +#: ./doc/training-guides/module003-ch005-the-ring.xml56(guilabel) +msgid "Fractional Replicas" +msgstr "" + +#: ./doc/training-guides/module003-ch005-the-ring.xml57(para) +msgid "" +"A ring is not restricted to having an integer number of replicas. In order " +"to support the gradual changing of replica counts, the ring is able to have " +"a real number of replicas." +msgstr "" + +#: ./doc/training-guides/module003-ch005-the-ring.xml61(para) +msgid "" +"When the number of replicas is not an integer, then the last element of " +"_replica2part2dev_id will have a length that is less than the partition " +"count for the ring. This means that some partitions will have more replicas " +"than others. For example, if a ring has 3.25 replicas, then 25% of its " +"partitions will have four replicas, while the remaining 75% will have just " +"three." +msgstr "" + +#: ./doc/training-guides/module003-ch005-the-ring.xml69(guilabel) +msgid "Partition Shift Value" +msgstr "" + +#: ./doc/training-guides/module003-ch005-the-ring.xml70(para) +msgid "" +"The partition shift value is known internally to the Ring class as " +"_part_shift. This value used to shift an MD5 hash to calculate the partition" +" on which the data for that hash should reside. Only the top four bytes of " +"the hash is used in this process. For example, to compute the partition for " +"the path /account/container/object the Python code might look like: " +"partition = unpack_from('>I', " +"md5('/account/container/object').digest())[0] >> self._part_shift" +msgstr "" + +#: ./doc/training-guides/module003-ch005-the-ring.xml80(para) +msgid "" +"For a ring generated with part_power P, the partition shift value is 32 - P." +msgstr "" + +#: ./doc/training-guides/module003-ch005-the-ring.xml82(guilabel) +msgid "Building the Ring" +msgstr "" + +#: ./doc/training-guides/module003-ch005-the-ring.xml83(para) +msgid "" +"The initial building of the ring first calculates the number of partitions " +"that should ideally be assigned to each device based the device’s weight. " +"For example, given a partition power of 20, the ring will have 1,048,576 " +"partitions. If there are 1,000 devices of equal weight they will each desire" +" 1,048.576 partitions. The devices are then sorted by the number of " +"partitions they desire and kept in order throughout the initialization " +"process." +msgstr "" + +#: ./doc/training-guides/module003-ch005-the-ring.xml92(para) +msgid "" +"Note: each device is also assigned a random tiebreaker value that is used " +"when two devices desire the same number of partitions. This tiebreaker is " +"not stored on disk anywhere, and so two different rings created with the " +"same parameters will have different partition assignments. For repeatable " +"partition assignments, RingBuilder.rebalance() takes an optional seed value " +"that will be used to seed Python’s pseudo-random number generator." +msgstr "" + +#: ./doc/training-guides/module003-ch005-the-ring.xml100(para) +msgid "" +"Then, the ring builder assigns each replica of each partition to the device " +"that desires the most partitions at that point while keeping it as far away " +"as possible from other replicas. The ring builder prefers to assign a " +"replica to a device in a regions that has no replicas already; should there " +"be no such region available, the ring builder will try to find a device in a" +" different zone; if not possible, it will look on a different server; " +"failing that, it will just look for a device that has no replicas; finally, " +"if all other options are exhausted, the ring builder will assign the replica" +" to the device that has the fewest replicas already assigned. Note that " +"assignment of multiple replicas to one device will only happen if the ring " +"has fewer devices than it has replicas." +msgstr "" + +#: ./doc/training-guides/module003-ch005-the-ring.xml115(para) +msgid "" +"When building a new ring based on an old ring, the desired number of " +"partitions each device wants is recalculated. Next the partitions to be " +"reassigned are gathered up. Any removed devices have all their assigned " +"partitions unassigned and added to the gathered list. Any partition replicas" +" that (due to the addition of new devices) can be spread out for better " +"durability are unassigned and added to the gathered list. Any devices that " +"have more partitions than they now desire have random partitions unassigned " +"from them and added to the gathered list. Lastly, the gathered partitions " +"are then reassigned to devices using a similar method as in the initial " +"assignment described above." +msgstr "" + +#: ./doc/training-guides/module003-ch005-the-ring.xml128(para) +msgid "" +"Whenever a partition has a replica reassigned, the time of the reassignment " +"is recorded. This is taken into account when gathering partitions to " +"reassign so that no partition is moved twice in a configurable amount of " +"time. This configurable amount of time is known internally to the " +"RingBuilder class as min_part_hours. This restriction is ignored for " +"replicas of partitions on devices that have been removed, as removing a " +"device only happens on device failure and there’s no choice but to make a " +"reassignment." +msgstr "" + +#: ./doc/training-guides/module003-ch005-the-ring.xml138(para) +msgid "" +"The above processes don’t always perfectly rebalance a ring due to the " +"random nature of gathering partitions for reassignment. To help reach a more" +" balanced ring, the rebalance process is repeated until near perfect (less " +"1% off) or when the balance doesn’t improve by at least 1% (indicating we " +"probably can’t get perfect balance due to wildly imbalanced zones or too " +"many partitions recently moved)." +msgstr "" + +#: ./doc/training-guides/card038.xml7(title) +msgid "" +"Install and configure OpenStack Identity Service in the Controller Node" +msgstr "" + +#: ./doc/training-guides/sources/cinder/development.environment.xml7(title) +msgid "Development.Environment" +msgstr "" + +#: ./doc/training-guides/sources/cinder/development.environment.xml9(title) +#: ./doc/training-guides/sources/cinder/addmethod.openstackapi.xml9(title) +#: ./doc/training-guides/sources/cinder/drivers.xml9(title) +#: ./doc/training-guides/sources/cinder/unit_tests.xml9(title) +#: ./doc/training-guides/sources/cinder/architecture.xml9(title) +#: ./doc/training-guides/sources/cinder/threading.xml9(title) +msgid "Header" +msgstr "" + +#: ./doc/training-guides/sources/cinder/development.environment.xml10(para) +#: ./doc/training-guides/sources/cinder/architecture.xml10(para) +msgid "" +".. Copyright 2010-2011 United States Government as represented by the " +"Administrator of the National Aeronautics and Space Administration. All " +"Rights Reserved. Licensed under the Apache License, Version 2.0 (the " +"\"License\"); you may not use this file except in compliance with the " +"License. You may obtain a copy of the License at " +"http://www.apache.org/licenses/LICENSE-2.0 Unless required by applicable law" +" or agreed to in writing, software distributed under the License is " +"distributed on an \"AS IS\" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY " +"KIND, either express or implied. See the License for the specific language " +"governing permissions and limitations under the License." +msgstr "" + +#: ./doc/training-guides/sources/cinder/development.environment.xml27(title) +msgid "Setting-Up-A-Development-Environment" +msgstr "" + +#: ./doc/training-guides/sources/cinder/development.environment.xml28(para) +msgid "" +"==================================== This page describes how to setup a " +"working Python development environment that can be used in developing cinder" +" on Ubuntu, Fedora or Mac OS X. These instructions assume you're already " +"familiar with git. Refer to GettingTheCode_ for additional information. .. " +"_GettingTheCode: http://wiki.openstack.org/GettingTheCode Following these " +"instructions will allow you to run the cinder unit tests. If you want to be " +"able to run cinder (i.e., launch VM instances), you will also need to " +"install libvirt and at least one of the `supported hypervisors`_. Running " +"cinder is currently only supported on Linux, although you can run the unit " +"tests on Mac OS X. See :doc:`../quickstart` for how to get a working version" +" of OpenStack Compute running as quickly as possible. .. _supported " +"hypervisors: http://wiki.openstack.org/HypervisorSupportMatrix" +msgstr "" + +#: ./doc/training-guides/sources/cinder/development.environment.xml46(title) +msgid "Virtual-Environments" +msgstr "" + +#: ./doc/training-guides/sources/cinder/development.environment.xml47(para) +msgid "" +"-------------------- Cinder development uses `virtualenv " +"[http://pypi.python.org/pypi/virtualenv]`__ to track and manage Python " +"dependencies while in development and testing. This allows you to install " +"all of the Python package dependencies in a virtual environment or " +"\"virtualenv\" (a special subdirectory of your cinder directory), instead of" +" installing the packages at the system level. .. note:: Virtualenv is useful" +" for running the unit tests, but is not typically used for full integration " +"testing or production usage." +msgstr "" + +#: ./doc/training-guides/sources/cinder/development.environment.xml60(title) +msgid "Linux-Systems" +msgstr "" + +#: ./doc/training-guides/sources/cinder/development.environment.xml61(para) +msgid "" +"------------- .. note:: This section is tested for Cinder on Ubuntu " +"(12.04-64) and Fedora-based (RHEL 6.1) distributions. Feel free to add notes" +" and change according to your experiences or operating system. Install the " +"prerequisite packages. On Ubuntu:: sudo apt-get install python-dev libssl-" +"dev python-pip git-core libmysqlclient-dev libpq-dev On Fedora-based " +"distributions like Fedora, RHEL, CentOS and Scientific Linux:: sudo yum " +"install python-devel openssl-devel python-pip git libmysqlclient-dev libqp-" +"dev" +msgstr "" + +#: ./doc/training-guides/sources/cinder/development.environment.xml75(title) +msgid "Mac-Os-X-Systems" +msgstr "" + +#: ./doc/training-guides/sources/cinder/development.environment.xml76(para) +msgid "" +"---------------- Install virtualenv:: sudo easy_install virtualenv Check the" +" version of OpenSSL you have installed:: openssl version If you have " +"installed OpenSSL 1.0.0a, which can happen when installing a MacPorts " +"package for OpenSSL, you will see an error when running " +"``cinder.tests.auth_unittest.AuthTestCase.test_209_can_generate_x509``. The " +"stock version of OpenSSL that ships with Mac OS X 10.6 (OpenSSL 0.9.8l) or " +"Mac OS X 10.7 (OpenSSL 0.9.8r) works fine with cinder." +msgstr "" + +#: ./doc/training-guides/sources/cinder/development.environment.xml90(title) +msgid "Getting-The-Code" +msgstr "" + +#: ./doc/training-guides/sources/cinder/development.environment.xml91(para) +msgid "" +"---------------- Grab the code from GitHub:: git clone " +"https://github.com/openstack/cinder.git cd cinder" +msgstr "" + +#: ./doc/training-guides/sources/cinder/development.environment.xml99(title) +msgid "Running-Unit-Tests" +msgstr "" + +#: ./doc/training-guides/sources/cinder/development.environment.xml100(para) +msgid "" +"------------------ The unit tests will run by default inside a virtualenv in" +" the ``.venv`` directory. Run the unit tests by doing:: ./run_tests.sh The " +"first time you run them, you will be asked if you want to create a virtual " +"environment (hit \"y\"):: No virtual environment found...create one? (Y/n) " +"See :doc:`unit_tests` for more details. .. _virtualenv:" +msgstr "" + +#: ./doc/training-guides/sources/cinder/development.environment.xml113(title) +msgid "Manually-Installing-And-Using-The-Virtualenv" +msgstr "" + +#: ./doc/training-guides/sources/cinder/development.environment.xml114(para) +msgid "" +"-------------------------------------------- You can manually install the " +"virtual environment instead of having ``run_tests.sh`` do it for you:: " +"python tools/install_venv.py This will install all of the Python packages " +"listed in the ``requirements.txt`` file into your virtualenv. There will " +"also be some additional packages (pip, setuptools) that are installed by the" +" ``tools/install_venv.py`` file into the virutalenv. If all goes well, you " +"should get a message something like this:: Cinder development environment " +"setup is complete. To activate the Cinder virtualenv for the extent of your " +"current shell session you can run:: $ source .venv/bin/activate Or, if you " +"prefer, you can run commands in the virtualenv on a case by case basis by " +"running:: $ tools/with_venv.sh [your command]" +msgstr "" + +#: ./doc/training-guides/sources/cinder/development.environment.xml134(title) +msgid "Contributing-Your-Work" +msgstr "" + +#: ./doc/training-guides/sources/cinder/development.environment.xml135(para) +msgid "" +"---------------------- Once your work is complete you may wish to contribute" +" it to the project. Add your name and email address to the ``Authors`` file," +" and also to the ``.mailmap`` file if you use multiple email addresses. Your" +" contributions can not be merged into trunk unless you are listed in the " +"Authors file. Cinder uses the Gerrit code review system. For information on " +"how to submit your branch to Gerrit, see GerritWorkflow_." +msgstr "" + +#: ./doc/training-guides/sources/cinder/addmethod.openstackapi.xml7(title) +msgid "Addmethod.Openstackapi" +msgstr "" + +#: ./doc/training-guides/sources/cinder/addmethod.openstackapi.xml10(para) +msgid "" +".. Copyright 2010-2011 OpenStack Foundation All Rights Reserved. Licensed " +"under the Apache License, Version 2.0 (the \"License\"); you may not use " +"this file except in compliance with the License. You may obtain a copy of " +"the License at http://www.apache.org/licenses/LICENSE-2.0 Unless required by" +" applicable law or agreed to in writing, software distributed under the " +"License is distributed on an \"AS IS\" BASIS, WITHOUT WARRANTIES OR " +"CONDITIONS OF ANY KIND, either express or implied. See the License for the " +"specific language governing permissions and limitations under the License." +msgstr "" + +#: ./doc/training-guides/sources/cinder/addmethod.openstackapi.xml26(title) +msgid "Adding-A-Method-To-The-Openstack-Api" +msgstr "" + +#: ./doc/training-guides/sources/cinder/addmethod.openstackapi.xml27(para) +msgid "" +"==================================== The interface is a mostly RESTful API. " +"REST stands for Representational State Transfer and provides an architecture" +" \"style\" for distributed systems using HTTP for transport. Figure out a " +"way to express your request and response in terms of resources that are " +"being created, modified, read, or destroyed." +msgstr "" + +#: ./doc/training-guides/sources/cinder/addmethod.openstackapi.xml33(title) +msgid "Routing" +msgstr "" + +#: ./doc/training-guides/sources/cinder/addmethod.openstackapi.xml34(para) +msgid "" +"------- To map URLs to controllers+actions, OpenStack uses the Routes " +"package, a clone of Rails routes for Python implementations. See " +"http://routes.groovie.org/ for more information. URLs are mapped to " +"\"action\" methods on \"controller\" classes in " +"``cinder/api/openstack/__init__/ApiRouter.__init__`` . See " +"http://routes.groovie.org/manual.html for all syntax, but you'll probably " +"just need these two: - mapper.connect() lets you map a single URL to a " +"single action on a controller. - mapper.resource() connects many standard " +"URLs to actions on a controller." +msgstr "" + +#: ./doc/training-guides/sources/cinder/addmethod.openstackapi.xml44(title) +msgid "Controllers-And-Actions" +msgstr "" + +#: ./doc/training-guides/sources/cinder/addmethod.openstackapi.xml45(para) +msgid "" +"----------------------- Controllers live in ``cinder/api/openstack``, and " +"inherit from cinder.wsgi.Controller. See ``cinder/api/openstack/servers.py``" +" for an example. Action methods take parameters that are sucked out of the " +"URL by mapper.connect() or .resource(). The first two parameters are self " +"and the WebOb request, from which you can get the req.environ, req.body, " +"req.headers, etc." +msgstr "" + +#: ./doc/training-guides/sources/cinder/addmethod.openstackapi.xml54(para) +msgid "" +"------------- Actions return a dictionary, and wsgi.Controller serializes " +"that to JSON or XML based on the request's content-type. If you define a new" +" controller, you'll need to define a ``_serialization_metadata`` attribute " +"on the class, to tell wsgi.Controller how to convert your dictionary to XML." +" It needs to know the singular form of any list tag such as ``[servers]`` " +"list contains ``[server]`` tags, and which dictionary keys are to be XML " +"attributes as opposed to subtags such as ``[server id=\"4\"/]`` instead of " +"``[server][id]4[/id][/server]``. See `cinder/api/openstack/servers.py` for " +"an example. Faults ------ If you need to return a non-200, you should return" +" faults.Fault(webob.exc.HTTPNotFound())" +msgstr "" + +#: ./doc/training-guides/sources/cinder/drivers.xml10(para) +msgid "" +".. Copyright (c) 2013 OpenStack Foundation All Rights Reserved. Licensed " +"under the Apache License, Version 2.0 (the \"License\"); you may not use " +"this file except in compliance with the License. You may obtain a copy of " +"the License at http://www.apache.org/licenses/LICENSE-2.0 Unless required by" +" applicable law or agreed to in writing, software distributed under the " +"License is distributed on an \"AS IS\" BASIS, WITHOUT WARRANTIES OR " +"CONDITIONS OF ANY KIND, either express or implied. See the License for the " +"specific language governing permissions and limitations under the License." +msgstr "" + +#: ./doc/training-guides/sources/cinder/drivers.xml27(para) +msgid "" +"======= Cinder exposes an API to users to interact with different storage " +"backend solutions. The following are standards across all drivers for Cinder" +" services to properly interact with a driver." +msgstr "" + +#: ./doc/training-guides/sources/cinder/drivers.xml35(title) +msgid "Minimum-Features" +msgstr "" + +#: ./doc/training-guides/sources/cinder/drivers.xml44(para) +msgid "Volume Create/Delete" +msgstr "" + +#: ./doc/training-guides/sources/cinder/drivers.xml45(para) +msgid "Volume Attach/Detach" +msgstr "" + +#: ./doc/training-guides/sources/cinder/drivers.xml46(para) +msgid "Snapshot Create/Delete" +msgstr "" + +#: ./doc/training-guides/sources/cinder/drivers.xml47(para) +msgid "Create Volume from Snapshot" +msgstr "" + +#: ./doc/training-guides/sources/cinder/drivers.xml48(para) +msgid "Get Volume Stats" +msgstr "" + +#: ./doc/training-guides/sources/cinder/drivers.xml49(para) +msgid "Copy Image to Volume" +msgstr "" + +#: ./doc/training-guides/sources/cinder/drivers.xml50(para) +msgid "Copy Volume to Image" +msgstr "" + +#: ./doc/training-guides/sources/cinder/drivers.xml51(para) +msgid "Clone Volume" +msgstr "" + +#: ./doc/training-guides/sources/cinder/drivers.xml36(para) +msgid "" +"---------------- Minimum features are enforced to avoid having a grid of " +"what features are supported by which drivers and which releases. Cinder Core" +" requires that all drivers implement the following minimum features. Havana " +"------ " +msgstr "" + +#: ./doc/training-guides/sources/cinder/drivers.xml60(para) +msgid "All of the above plus" +msgstr "" + +#: ./doc/training-guides/sources/cinder/drivers.xml61(para) +msgid "Extend Volume" +msgstr "" + +#: ./doc/training-guides/sources/cinder/drivers.xml57(para) +msgid "-------- " +msgstr "" + +#: ./doc/training-guides/sources/cinder/drivers.xml66(title) +msgid "Volume-Stats" +msgstr "" + +#: ./doc/training-guides/sources/cinder/drivers.xml73(para) +msgid "driver_version" +msgstr "" + +#: ./doc/training-guides/sources/cinder/drivers.xml74(para) +msgid "free_capacity_gb" +msgstr "" + +#: ./doc/training-guides/sources/cinder/drivers.xml75(para) +msgid "reserved_percentage" +msgstr "" + +#: ./doc/training-guides/sources/cinder/drivers.xml76(para) +msgid "storage_protocol" +msgstr "" + +#: ./doc/training-guides/sources/cinder/drivers.xml77(para) +msgid "total_capacity_gb" +msgstr "" + +#: ./doc/training-guides/sources/cinder/drivers.xml78(para) +msgid "vendor_name" +msgstr "" + +#: ./doc/training-guides/sources/cinder/drivers.xml79(para) +msgid "volume_backend_name" +msgstr "" + +#: ./doc/training-guides/sources/cinder/drivers.xml82(para) +msgid "If the driver is unable to provide a value for free_capacity_gb or" +msgstr "" + +#: ./doc/training-guides/sources/cinder/drivers.xml67(para) +msgid "" +"------------ Volume stats are used by the different schedulers for the " +"drivers to provide a report on their current state of the backend. The " +"following should be provided by a driver. " +"total_capacity_gb, keywords can be provided instead. Please use 'unknown' if" +" the array cannot report the value or 'infinite' if the array has no upper" +msgstr "" + +#: ./doc/training-guides/sources/cinder/unit_tests.xml7(title) +msgid "Unit_Tests" +msgstr "" + +#: ./doc/training-guides/sources/cinder/unit_tests.xml14(title) +msgid "Unit-Tests" +msgstr "" + +#: ./doc/training-guides/sources/cinder/unit_tests.xml15(para) +msgid "" +"========== Cinder contains a suite of unit tests, in the cinder/tests " +"directory. Any proposed code change will be automatically rejected by the " +"OpenStack Jenkins server [#f1]_ if the change causes unit test failures." +msgstr "" + +#: ./doc/training-guides/sources/cinder/unit_tests.xml23(title) +msgid "Running-The-Tests" +msgstr "" + +#: ./doc/training-guides/sources/cinder/unit_tests.xml24(para) +msgid "" +"----------------- Run the unit tests by doing:: ./run_tests.sh This script " +"is a wrapper around the `nose`_ testrunner and the `pep8`_ checker. .. " +"_nose: http://code.google.com/p/python-nose/ .. _pep8: " +"https://github.com/jcrocholl/pep8 Flags ----- The ``run_tests.sh`` script " +"supports several flags. You can view a list of flags by doing:: run_tests.sh" +" -h This will show the following help information:: Usage: ./run_tests.sh " +"[OPTION]... Run Cinder's test suite(s) -V, --virtual-env Always use " +"virtualenv. Install automatically if not present -N, --no-virtual-env Don't " +"use virtualenv. Run tests in local environment -s, --no-site-packages " +"Isolate the virtualenv from the global Python environment -r, --recreate-db " +"Recreate the test database (deprecated, as this is now the default). -n, " +"--no-recreate-db Don't recreate the test database. -x, --stop Stop running " +"tests after the first error or failure. -f, --force Force a clean re-build " +"of the virtual environment. Useful when dependencies have been added. -p, " +"--pep8 Just run pep8 -P, --no-pep8 Don't run pep8 -c, --coverage Generate " +"coverage report -h, --help Print this usage message --hide-elapsed Don't " +"print the elapsed time for each test along with slow test list Because " +"``run_tests.sh`` is a wrapper around nose, it also accepts the same flags as" +" nosetests. See the `nose options documentation`_ for details about these " +"additional flags. .. _nose options documentation: " +"http://readthedocs.org/docs/nose/en/latest/usage.html#options" +msgstr "" + +#: ./doc/training-guides/sources/cinder/unit_tests.xml58(title) +msgid "Running-A-Subset-Of-Tests" +msgstr "" + +#: ./doc/training-guides/sources/cinder/unit_tests.xml59(para) +msgid "" +"------------------------- Instead of running all tests, you can specify an " +"individual directory, file, class, or method that contains test code. To run" +" the tests in the ``cinder/tests/scheduler`` directory:: ./run_tests.sh " +"scheduler To run the tests in the ``cinder/tests/test_libvirt.py`` file:: " +"./run_tests.sh test_libvirt To run the tests in the `HostStateTestCase` " +"class in ``cinder/tests/test_libvirt.py``:: ./run_tests.sh " +"test_libvirt:HostStateTestCase To run the `ToPrimitiveTestCase.test_dict` " +"test method in ``cinder/tests/test_utils.py``:: ./run_tests.sh " +"test_utils:ToPrimitiveTestCase.test_dict" +msgstr "" + +#: ./doc/training-guides/sources/cinder/unit_tests.xml76(title) +msgid "Suppressing-Logging-Output-When-Tests-Fail" +msgstr "" + +#: ./doc/training-guides/sources/cinder/unit_tests.xml77(para) +msgid "" +"------------------------------------------ By default, when one or more unit" +" test fails, all of the data sent to the logger during the failed tests will" +" appear on standard output, which typically consists of many lines of texts." +" The logging output can make it difficult to identify which specific tests " +"have failed, unless your terminal has a large scrollback buffer or you have " +"redirected output to a file. You can suppress the logging output by calling " +"``run_tests.sh`` with the nose flag:: --nologcapture" +msgstr "" + +#: ./doc/training-guides/sources/cinder/unit_tests.xml90(title) +msgid "Virtualenv" +msgstr "" + +#: ./doc/training-guides/sources/cinder/unit_tests.xml91(para) +msgid "" +"---------- By default, the tests use the Python packages installed inside a " +"virtualenv [#f2]_. (This is equivalent to using the ``-V, --virtualenv`` " +"flag). If the virtualenv does not exist, it will be created the first time " +"the tests are run. If you wish to recreate the virtualenv, call " +"``run_tests.sh`` with the flag:: -f, --force Recreating the virtualenv is " +"useful if the package dependencies have changed since the virtualenv was " +"last created. If the ``requirements.txt`` or ``tools/install_venv.py`` files" +" have changed, it's a good idea to recreate the virtualenv. By default, the " +"unit tests will see both the packages in the virtualenv and the packages " +"that have been installed in the Python global environment. In some cases, " +"the packages in the Python global environment may cause a conflict with the " +"packages in the virtualenv. If this occurs, you can isolate the virtualenv " +"from the global environment by using the flag:: -s, --no-site packages If " +"you do not wish to use a virtualenv at all, use the flag:: -N, --no-virtual-" +"env" +msgstr "" + +#: ./doc/training-guides/sources/cinder/unit_tests.xml113(title) +msgid "Database" +msgstr "" + +#: ./doc/training-guides/sources/cinder/unit_tests.xml114(para) +msgid "" +"-------- Some of the unit tests make queries against an sqlite database " +"[#f3]_. By default, the test database (``tests.sqlite``) is deleted and " +"recreated each time ``run_tests.sh`` is invoked (This is equivalent to using" +" the ``-r, --recreate-db`` flag). To reduce testing time if a database " +"already exists it can be reused by using the flag:: -n, --no-recreate-db " +"Reusing an existing database may cause tests to fail if the schema has " +"changed. If any files in the ``cinder/db/sqlalchemy`` have changed, it's a " +"good idea to recreate the test database." +msgstr "" + +#: ./doc/training-guides/sources/cinder/unit_tests.xml128(title) +msgid "Gotchas" +msgstr "" + +#: ./doc/training-guides/sources/cinder/unit_tests.xml129(para) +msgid "" +"------- If you are running the unit tests from a shared " +"folder, you may see tests start to fail or stop completely as a result of " +"Python lockfile issues [#f4]_. You can get around this by manually setting " +"or updating the following line in ``cinder/tests/conf_fixture.py``:: " +"CONF['lock_path'].SetDefault('/tmp') Note that you may use any location (not" +" just ``/tmp``!) as long as it is not a shared folder. .. rubric:: Footnotes" +" .. [#f1] See :doc:`jenkins`. .. [#f2] See :doc:`development.environment` " +"for more details about the use of virtualenv. .. [#f3] There is an effort " +"underway to use a fake DB implementation for the unit tests. See " +"https://lists.launchpad.net/openstack/msg05604.html" +msgstr "" + +#: ./doc/training-guides/sources/cinder/architecture.xml7(title) +msgid "Architecture" +msgstr "" + +#: ./doc/training-guides/sources/cinder/architecture.xml27(title) +msgid "Cinder-System-Architecture" +msgstr "" + +#: ./doc/training-guides/sources/cinder/architecture.xml28(para) +msgid "" +"========================== The Cinder Block Storage Service is intended to " +"be ran on one or more nodes. Cinder uses a sql-based central database that " +"is shared by all Cinder services in the system. The amount and depth of the " +"data fits into a sql database quite well. For small deployments this seems " +"like an optimal solution. For larger deployments, and especially if security" +" is a concern, cinder will be moving towards multiple data stores with some " +"kind of aggregation system." +msgstr "" + +#: ./doc/training-guides/sources/cinder/architecture.xml35(title) +msgid "Components" +msgstr "" + +#: ./doc/training-guides/sources/cinder/architecture.xml55(para) +msgid "" +"DB: sql database for data storage. Used by all components (LINKS NOT SHOWN)" +msgstr "" + +#: ./doc/training-guides/sources/cinder/architecture.xml56(para) +msgid "Web Dashboard: potential external component that talks to the api" +msgstr "" + +#: ./doc/training-guides/sources/cinder/architecture.xml57(para) +msgid "" +"api: component that receives http requests, converts commands and " +"communicates with other components via the queue or http" +msgstr "" + +#: ./doc/training-guides/sources/cinder/architecture.xml58(para) +msgid "" +"Auth Manager: component responsible for users/projects/and roles. Can " +"backend to DB or LDAP. This is not a separate binary, but rather a python " +"class that is used by most components in the system." +msgstr "" + +#: ./doc/training-guides/sources/cinder/architecture.xml59(para) +msgid "scheduler: decides which host gets each volume" +msgstr "" + +#: ./doc/training-guides/sources/cinder/architecture.xml60(para) +msgid "volume: manages dynamically attachable block devices." +msgstr "" + +#: ./doc/training-guides/sources/cinder/architecture.xml36(para) +msgid "" +"---------- Below you will a brief explanation of the different components. " +":: /- ( LDAP ) [ Auth Manager ] --- | \\- ( DB ) | | cinderclient | / \\ | [" +" Web Dashboard ]- -[ api ] -- [ AMQP ] -- [ scheduler ] -- [ volume ] -- ( " +"iSCSI ) \\ / | novaclient | | | | [ REST ] " +msgstr "" + +#: ./doc/training-guides/sources/cinder/threading.xml14(title) +msgid "Threading-Model" +msgstr "" + +#: ./doc/training-guides/sources/cinder/threading.xml18(para) +msgid "model of threading, implemented" +msgstr "" + +#: ./doc/training-guides/sources/cinder/threading.xml15(para) +msgid "" +"=============== through using the Python `eventlet " +"[http://eventlet.net/]`_ and `greenlet " +"[http://packages.python.org/greenlet/]`_ libraries. Green threads use a " +"cooperative model of threading: thread context switches can only occur when " +"specific eventlet or greenlet library calls are made. For example, sleep and" +" certain I/O calls. From the operating system's point of view, each " +"OpenStack service runs in a single thread. The use of green threads reduces " +"the likelihood of race conditions, but does not completely eliminate them. " +"In some cases, you may need to use the ``@utils.synchronized(...)`` " +"decorator to avoid races. In addition, since there is only one operating " +"system thread, a call that blocks that main thread will block the entire " +"process." +msgstr "" + +#: ./doc/training-guides/sources/cinder/threading.xml34(title) +msgid "Yielding-The-Thread-In-Long-Running-Tasks" +msgstr "" + +#: ./doc/training-guides/sources/cinder/threading.xml35(para) +msgid "" +"----------------------------------------- If a code path takes a long time " +"to execute and does not contain any methods that trigger an eventlet context" +" switch, the long-running thread will block any pending threads. This " +"scenario can be avoided by adding calls to the eventlet sleep method in the " +"long-running code path. The sleep call will trigger a context switch if " +"there are pending threads, and using an argument of 0 will avoid introducing" +" delays in the case that there is only a single green thread:: from eventlet" +" import greenthread ... greenthread.sleep(0)" +msgstr "" + +#: ./doc/training-guides/sources/cinder/threading.xml50(title) +msgid "Mysql-Access-And-Eventlet" +msgstr "" + +#: ./doc/training-guides/sources/cinder/threading.xml51(para) +msgid "" +"------------------------- Queries to the MySQL database will block the main " +"thread of a service. This is because OpenStack services use an external C " +"library for accessing the MySQL database. Since eventlet cannot use monkey-" +"patching to intercept blocking calls in a C library, the resulting database " +"query blocks the thread. The Diablo release contained a thread-pooling " +"implementation that did not block, but this implementation resulted in a " +"`bug`_ and was removed. See this `mailing list thread`_ for a discussion of " +"this issue, including a discussion of the `impact on performance`_. .. _bug:" +" https://bugs.launchpad.net/cinder/+bug/838581 .. _mailing list thread: " +"https://lists.launchpad.net/openstack/msg08118.html" +msgstr "" + +#. Put one translator per line, in the form of NAME , YEAR1, YEAR2 +#: ./doc/training-guides/sources/cinder/threading.xml0(None) +msgid "translator-credits" +msgstr "" diff --git a/doc/training-guides/locale/training-guides.pot b/doc/training-guides/locale/training-guides.pot new file mode 100644 index 0000000000..a32baf2b16 --- /dev/null +++ b/doc/training-guides/locale/training-guides.pot @@ -0,0 +1,9563 @@ +msgid "" +msgstr "" +"Project-Id-Version: PACKAGE VERSION\n" +"POT-Creation-Date: 2014-01-30 06:24+0000\n" +"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n" +"Last-Translator: FULL NAME \n" +"Language-Team: LANGUAGE \n" +"MIME-Version: 1.0\n" +"Content-Type: text/plain; charset=UTF-8\n" +"Content-Transfer-Encoding: 8bit\n" + +#: ./doc/training-guides/module002-ch005-floating-ips.xml:7(title) +msgid "Floating IP Addresses And Security Rules" +msgstr "" + +#: ./doc/training-guides/module002-ch005-floating-ips.xml:8(para) +msgid "OpenStack Networking has the concept of Fixed IPs and Floating IPs. Fixed IPs are assigned to an instance on creation and stay the same until the instance is explicitly terminated. Floating ips are ip addresses that can be dynamically associated with an instance. This address can be disassociated and associated with another instance at any time." +msgstr "" + +#: ./doc/training-guides/module002-ch005-floating-ips.xml:15(para) +msgid "Various tasks carried out by Floating IP's as of now." +msgstr "" + +#: ./doc/training-guides/module002-ch005-floating-ips.xml:19(para) +msgid "create IP ranges under a certain group, only available for admin role." +msgstr "" + +#: ./doc/training-guides/module002-ch005-floating-ips.xml:23(para) +msgid "allocate an floating IP to a certain tenant, only available for admin role." +msgstr "" + +#: ./doc/training-guides/module002-ch005-floating-ips.xml:27(para) +msgid "deallocate an floating IP from a certain tenant" +msgstr "" + +#: ./doc/training-guides/module002-ch005-floating-ips.xml:31(para) +msgid "associate an floating IP to a given instance" +msgstr "" + +#: ./doc/training-guides/module002-ch005-floating-ips.xml:35(para) +msgid "disassociate an floating IP from a certain instance" +msgstr "" + +#: ./doc/training-guides/module002-ch005-floating-ips.xml:39(para) +msgid "Just as shown by the above figure, we will have nova-network-api to support nova client floating commands. nova-network-api will invoke neutron cli lib to interactive with neutron server via API. The data about floating IPs will be stored in to neutron DB. Neutron Agent, which is running on compute host will enforce the floating IP." +msgstr "" + +#: ./doc/training-guides/module002-ch005-floating-ips.xml:46(guilabel) +msgid "Multiple Floating IP Pools" +msgstr "" + +#: ./doc/training-guides/module002-ch005-floating-ips.xml:48(para) +msgid "The L3 API in OpenStack Networking supports multiple floating IP pools. In OpenStack Networking, a floating IP pool is represented as an external network and a floating IP is allocated from a subnet associated with the external network. Since each L3 agent can be associated with at most one external network, we need to invoke multiple L3 agent to define multiple floating IP pools. 'gateway_external_network_id'in L3 agent configuration file indicates the external network that the L3 agent handles. You can run multiple L3 agent instances on one host." +msgstr "" + +#: ./doc/training-guides/module002-ch005-floating-ips.xml:59(para) +msgid "In addition, when you run multiple L3 agents, make sure that handle_internal_only_routers is set to Trueonly for one L3 agent in an OpenStack Networking deployment and set to Falsefor all other L3 agents. Since the default value of this parameter is True, you need to configure it carefully." +msgstr "" + +#: ./doc/training-guides/module002-ch005-floating-ips.xml:65(para) +msgid "Before starting L3 agents, you need to create routers and external networks, then update the configuration files with UUID of external networks and start L3 agents." +msgstr "" + +#: ./doc/training-guides/module002-ch005-floating-ips.xml:69(para) +msgid "For the first agent, invoke it with the following l3_agent.ini where handle_internal_only_routers is True." +msgstr "" + +#: ./doc/training-guides/bk002-ch009-operator-compute-node-quiz.xml:6(title) ./doc/training-guides/bk001-ch006-associate-compute-node-quiz.xml:6(title) +msgid "Compute Node Quiz" +msgstr "" + +#: ./doc/training-guides/bk002-ch009-operator-compute-node-quiz.xml:8(title) +msgid "Days 5 to 6, 16:40 to 17:00" +msgstr "" + +#: ./doc/training-guides/module003-ch006-more-concepts.xml:7(title) +msgid "A Bit More On Swift" +msgstr "" + +#: ./doc/training-guides/module003-ch006-more-concepts.xml:8(guilabel) +msgid "Containers and Objects" +msgstr "" + +#: ./doc/training-guides/module003-ch006-more-concepts.xml:9(para) +msgid "A container is a storage compartment for your data and provides a way for you to organize your data. You can think of a container as a folder in Windows or a directory in UNIX. The primary difference between a container and these other file system concepts is that containers cannot be nested. You can, however, create an unlimited number of containers within your account. Data must be stored in a container so you must have at least one container defined in your account prior to uploading data." +msgstr "" + +#: ./doc/training-guides/module003-ch006-more-concepts.xml:19(para) +msgid "The only restrictions on container names is that they cannot contain a forward slash (/) or an ascii null (%00) and must be less than 257 bytes in length. Please note that the length restriction applies to the name after it has been URL encoded. For example, a container name of Course Docs would be URL encoded as Course%20Docs and therefore be 13 bytes in length rather than the expected 11." +msgstr "" + +#: ./doc/training-guides/module003-ch006-more-concepts.xml:27(para) +msgid "An object is the basic storage entity and any optional metadata that represents the files you store in the OpenStack Object Storage system. When you upload data to OpenStack Object Storage, the data is stored as-is (no compression or encryption) and consists of a location (container), the object's name, and any metadata consisting of key/value pairs. For instance, you may chose to store a backup of your digital photos and organize them into albums. In this case, each object could be tagged with metadata such as Album : Caribbean Cruise or Album : Aspen Ski Trip." +msgstr "" + +#: ./doc/training-guides/module003-ch006-more-concepts.xml:38(para) +msgid "The only restriction on object names is that they must be less than 1024 bytes in length after URL encoding. For example, an object name of C++final(v2).txt should be URL encoded as C%2B%2Bfinal%28v2%29.txt and therefore be 24 bytes in length rather than the expected 16." +msgstr "" + +#: ./doc/training-guides/module003-ch006-more-concepts.xml:43(para) +msgid "The maximum allowable size for a storage object upon upload is 5 gigabytes (GB) and the minimum is zero bytes. You can use the built-in large object support and the swift utility to retrieve objects larger than 5 GB." +msgstr "" + +#: ./doc/training-guides/module003-ch006-more-concepts.xml:47(para) +msgid "For metadata, you should not exceed 90 individual key/value pairs for any one object and the total byte length of all key/value pairs should not exceed 4KB (4096 bytes)." +msgstr "" + +#: ./doc/training-guides/module003-ch006-more-concepts.xml:51(guilabel) +msgid "Language-Specific API Bindings" +msgstr "" + +#: ./doc/training-guides/module003-ch006-more-concepts.xml:53(para) +msgid "A set of supported API bindings in several popular languages are available from the Rackspace Cloud Files product, which uses OpenStack Object Storage code for its implementation. These bindings provide a layer of abstraction on top of the base REST API, allowing programmers to work with a container and object model instead of working directly with HTTP requests and responses. These bindings are free (as in beer and as in speech) to download, use, and modify. They are all licensed under the MIT License as described in the COPYING file packaged with each binding. If you do make any improvements to an API, you are encouraged (but not required) to submit those changes back to us." +msgstr "" + +#: ./doc/training-guides/module003-ch006-more-concepts.xml:66(para) +msgid "The API bindings for Rackspace Cloud Files are hosted athttp://github.com/rackspace. Feel free to coordinate your changes through github or, if you prefer, send your changes to cloudfiles@rackspacecloud.com. Just make sure to indicate which language and version you modified and send a unified diff." +msgstr "" + +#: ./doc/training-guides/module003-ch006-more-concepts.xml:75(para) +msgid "Each binding includes its own documentation (either HTML, PDF, or CHM). They also include code snippets and examples to help you get started. The currently supported API binding for OpenStack Object Storage are:" +msgstr "" + +#: ./doc/training-guides/module003-ch006-more-concepts.xml:81(para) +msgid "PHP (requires 5.x and the modules: cURL, FileInfo, mbstring)" +msgstr "" + +#: ./doc/training-guides/module003-ch006-more-concepts.xml:85(para) +msgid "Python (requires 2.4 or newer)" +msgstr "" + +#: ./doc/training-guides/module003-ch006-more-concepts.xml:88(para) +msgid "Java (requires JRE v1.5 or newer)" +msgstr "" + +#: ./doc/training-guides/module003-ch006-more-concepts.xml:91(para) +msgid "C#/.NET (requires .NET Framework v3.5)" +msgstr "" + +#: ./doc/training-guides/module003-ch006-more-concepts.xml:94(para) +msgid "Ruby (requires 1.8 or newer and mime-tools module)" +msgstr "" + +#: ./doc/training-guides/module003-ch006-more-concepts.xml:98(para) +msgid "There are no other supported language-specific bindings at this time. You are welcome to create your own language API bindings and we can help answer any questions during development, host your code if you like, and give you full credit for your work." +msgstr "" + +#: ./doc/training-guides/module003-ch006-more-concepts.xml:103(guilabel) +msgid "Proxy Server" +msgstr "" + +#: ./doc/training-guides/module003-ch006-more-concepts.xml:104(para) +msgid "The Proxy Server is responsible for tying together the rest of the OpenStack Object Storage architecture. For each request, it will look up the location of the account, container, or object in the ring (see below) and route the request accordingly. The public API is also exposed through the Proxy Server." +msgstr "" + +#: ./doc/training-guides/module003-ch006-more-concepts.xml:110(para) +msgid "A large number of failures are also handled in the Proxy Server. For example, if a server is unavailable for an object PUT, it will ask the ring for a hand-off server and route there instead." +msgstr "" + +#: ./doc/training-guides/module003-ch006-more-concepts.xml:114(para) +msgid "When objects are streamed to or from an object server, they are streamed directly through the proxy server to or from the user – the proxy server does not spool them." +msgstr "" + +#: ./doc/training-guides/module003-ch006-more-concepts.xml:118(para) +msgid "You can use a proxy server with account management enabled by configuring it in the proxy server configuration file." +msgstr "" + +#: ./doc/training-guides/module003-ch006-more-concepts.xml:121(guilabel) +msgid "Object Server" +msgstr "" + +#: ./doc/training-guides/module003-ch006-more-concepts.xml:122(para) +msgid "The Object Server is a very simple blob storage server that can store, retrieve and delete objects stored on local devices. Objects are stored as binary files on the filesystem with metadata stored in the file’s extended attributes (xattrs). This requires that the underlying filesystem choice for object servers support xattrs on files. Some filesystems, like ext3, have xattrs turned off by default." +msgstr "" + +#: ./doc/training-guides/module003-ch006-more-concepts.xml:130(para) +msgid "Each object is stored using a path derived from the object name’s hash and the operation’s timestamp. Last write always wins, and ensures that the latest object version will be served. A deletion is also treated as a version of the file (a 0 byte file ending with “.ts”, which stands for tombstone). This ensures that deleted files are replicated correctly and older versions don’t magically reappear due to failure scenarios." +msgstr "" + +#: ./doc/training-guides/module003-ch006-more-concepts.xml:139(guilabel) +msgid "Container Server" +msgstr "" + +#: ./doc/training-guides/module003-ch006-more-concepts.xml:140(para) +msgid "The Container Server’s primary job is to handle listings of objects. It does not’t know where those objects are, just what objects are in a specific container. The listings are stored as sqlite database files, and replicated across the cluster similar to how objects are. Statistics are also tracked that include the total number of objects, and total storage usage for that container." +msgstr "" + +#: ./doc/training-guides/module003-ch006-more-concepts.xml:148(guilabel) +msgid "Account Server" +msgstr "" + +#: ./doc/training-guides/module003-ch006-more-concepts.xml:149(para) +msgid "The Account Server is very similar to the Container Server, excepting that it is responsible for listings of containers rather than objects." +msgstr "" + +#: ./doc/training-guides/module003-ch006-more-concepts.xml:152(guilabel) ./doc/training-guides/module003-ch004-swift-building-blocks.xml:225(guilabel) ./doc/training-guides/module003-ch004-swift-building-blocks.xml:249(title) ./doc/training-guides/module003-ch009-replication.xml:7(title) +msgid "Replication" +msgstr "" + +#: ./doc/training-guides/module003-ch006-more-concepts.xml:153(para) +msgid "Replication is designed to keep the system in a consistent state in the face of temporary error conditions like network outages or drive failures." +msgstr "" + +#: ./doc/training-guides/module003-ch006-more-concepts.xml:157(para) +msgid "The replication processes compare local data with each remote copy to ensure they all contain the latest version. Object replication uses a hash list to quickly compare subsections of each partition, and container and account replication use a combination of hashes and shared high water marks." +msgstr "" + +#: ./doc/training-guides/module003-ch006-more-concepts.xml:163(para) +msgid "Replication updates are push based. For object replication, updating is just a matter of rsyncing files to the peer. Account and container replication push missing records over HTTP or rsync whole database files." +msgstr "" + +#: ./doc/training-guides/module003-ch006-more-concepts.xml:168(para) +msgid "The replicator also ensures that data is removed from the system. When an item (object, container, or account) is deleted, a tombstone is set as the latest version of the item. The replicator will see the tombstone and ensure that the item is removed from the entire system." +msgstr "" + +#: ./doc/training-guides/module003-ch006-more-concepts.xml:174(para) +msgid "To separate the cluster-internal replication traffic from client traffic, separate replication servers can be used. These replication servers are based on the standard storage servers, but they listen on the replication IP and only respond to REPLICATE requests. Storage servers can serve REPLICATE requests, so an operator can transition to using a separate replication network with no cluster downtime." +msgstr "" + +#: ./doc/training-guides/module003-ch006-more-concepts.xml:182(para) +msgid "Replication IP and port information is stored in the ring on a per-node basis. These parameters will be used if they are present, but they are not required. If this information does not exist or is empty for a particular node, the node's standard IP and port will be used for replication." +msgstr "" + +#: ./doc/training-guides/module003-ch006-more-concepts.xml:188(guilabel) +msgid "Updaters" +msgstr "" + +#: ./doc/training-guides/module003-ch006-more-concepts.xml:189(para) +msgid "There are times when container or account data can not be immediately updated. This usually occurs during failure scenarios or periods of high load. If an update fails, the update is queued locally on the file system, and the updater will process the failed updates. This is where an eventual consistency window will most likely come in to play. For example, suppose a container server is under load and a new object is put in to the system. The object will be immediately available for reads as soon as the proxy server responds to the client with success. However, the container server did not update the object listing, and so the update would be queued for a later update. Container listings, therefore, may not immediately contain the object." +msgstr "" + +#: ./doc/training-guides/module003-ch006-more-concepts.xml:204(para) +msgid "In practice, the consistency window is only as large as the frequency at which the updater runs and may not even be noticed as the proxy server will route listing requests to the first container server which responds. The server under load may not be the one that serves subsequent listing requests – one of the other two replicas may handle the listing." +msgstr "" + +#: ./doc/training-guides/module003-ch006-more-concepts.xml:211(guilabel) +msgid "Auditors" +msgstr "" + +#: ./doc/training-guides/module003-ch006-more-concepts.xml:212(para) +msgid "Auditors crawl the local server checking the integrity of the objects, containers, and accounts. If corruption is found (in the case of bit rot, for example), the file is quarantined, and replication will replace the bad file from another replica. If other errors are found they are logged. For example, an object’s listing cannot be found on any container server it should be." +msgstr "" + +#. When image changes, this message will be marked fuzzy or untranslated for you. +#. It doesn't matter what you translate it to: it's not used at all. +#: ./doc/training-guides/module003-ch007-swift-cluster-architecture.xml:13(None) +msgid "@@image: 'figures/image47.png'; md5=90f6c7cf3947d7987eeb55d657cdc927" +msgstr "" + +#. When image changes, this message will be marked fuzzy or untranslated for you. +#. It doesn't matter what you translate it to: it's not used at all. +#: ./doc/training-guides/module003-ch007-swift-cluster-architecture.xml:57(None) +msgid "@@image: 'figures/image48.png'; md5=2aa7eb3bddcf6826f33469920dc2a9c3" +msgstr "" + +#: ./doc/training-guides/module003-ch007-swift-cluster-architecture.xml:7(title) +msgid "Cluster Arch" +msgstr "" + +#: ./doc/training-guides/module003-ch007-swift-cluster-architecture.xml:8(guilabel) +msgid "Access Tier" +msgstr "" + +#: ./doc/training-guides/module003-ch007-swift-cluster-architecture.xml:10(title) ./doc/training-guides/bk002-ch013-operator-object-storage-node.xml:59(title) +msgid "Swift Cluster Architecture" +msgstr "" + +#: ./doc/training-guides/module003-ch007-swift-cluster-architecture.xml:17(para) +msgid "Large-scale deployments segment off an \"Access Tier\". This tier is the “Grand Central” of the Object Storage system. It fields incoming API requests from clients and moves data in and out of the system. This tier is composed of front-end load balancers, ssl- terminators, authentication services, and it runs the (distributed) brain of the object storage system — the proxy server processes." +msgstr "" + +#: ./doc/training-guides/module003-ch007-swift-cluster-architecture.xml:25(para) +msgid "Having the access servers in their own tier enables read/write access to be scaled out independently of storage capacity. For example, if the cluster is on the public Internet and requires ssl-termination and has high demand for data access, many access servers can be provisioned. However, if the cluster is on a private network and it is being used primarily for archival purposes, fewer access servers are needed." +msgstr "" + +#: ./doc/training-guides/module003-ch007-swift-cluster-architecture.xml:33(para) +msgid "As this is an HTTP addressable storage service, a load balancer can be incorporated into the access tier." +msgstr "" + +#: ./doc/training-guides/module003-ch007-swift-cluster-architecture.xml:35(para) +msgid "Typically, this tier comprises a collection of 1U servers. These machines use a moderate amount of RAM and are network I/O intensive. As these systems field each incoming API request, it is wise to provision them with two high-throughput (10GbE) interfaces. One interface is used for 'front-end' incoming requests and the other for 'back-end' access to the object storage nodes to put and fetch data." +msgstr "" + +#: ./doc/training-guides/module003-ch007-swift-cluster-architecture.xml:43(guilabel) ./doc/training-guides/module003-ch007-swift-cluster-architecture.xml:77(guilabel) +msgid "Factors to Consider" +msgstr "" + +#: ./doc/training-guides/module003-ch007-swift-cluster-architecture.xml:44(para) +msgid "For most publicly facing deployments as well as private deployments available across a wide-reaching corporate network, SSL will be used to encrypt traffic to the client. SSL adds significant processing load to establish sessions between clients; more capacity in the access layer will need to be provisioned. SSL may not be required for private deployments on trusted networks." +msgstr "" + +#: ./doc/training-guides/module003-ch007-swift-cluster-architecture.xml:52(guilabel) +msgid "Storage Nodes" +msgstr "" + +#: ./doc/training-guides/module003-ch007-swift-cluster-architecture.xml:54(title) +msgid "Object Storage (Swift)" +msgstr "" + +#: ./doc/training-guides/module003-ch007-swift-cluster-architecture.xml:61(para) +msgid "The next component is the storage servers themselves. Generally, most configurations should have each of the five Zones with an equal amount of storage capacity. Storage nodes use a reasonable amount of memory and CPU. Metadata needs to be readily available to quickly return objects. The object stores run services not only to field incoming requests from the Access Tier, but to also run replicators, auditors, and reapers. Object stores can be provisioned with single gigabit or 10 gigabit network interface depending on expected workload and desired performance." +msgstr "" + +#: ./doc/training-guides/module003-ch007-swift-cluster-architecture.xml:72(para) +msgid "Currently 2TB or 3TB SATA disks deliver good price/performance value. Desktop-grade drives can be used where there are responsive remote hands in the datacenter, and enterprise-grade drives can be used where this is not the case." +msgstr "" + +#: ./doc/training-guides/module003-ch007-swift-cluster-architecture.xml:78(para) +msgid "Desired I/O performance for single-threaded requests should be kept in mind. This system does not use RAID, so each request for an object is handled by a single disk. Disk performance impacts single-threaded response rates." +msgstr "" + +#: ./doc/training-guides/module003-ch007-swift-cluster-architecture.xml:83(para) +msgid "To achieve apparent higher throughput, the object storage system is designed with concurrent uploads/downloads in mind. The network I/O capacity (1GbE, bonded 1GbE pair, or 10GbE) should match your desired concurrent throughput needs for reads and writes." +msgstr "" + +#. When image changes, this message will be marked fuzzy or untranslated for you. +#. It doesn't matter what you translate it to: it's not used at all. +#: ./doc/training-guides/module002-ch001-networking-in-openstack.xml:230(None) +msgid "@@image: 'figures/image33.png'; md5=e9843f38c9b2555e709357a724fc710d" +msgstr "" + +#: ./doc/training-guides/module002-ch001-networking-in-openstack.xml:7(title) ./doc/training-guides/module002-ch001-networking-in-openstack.xml:8(guilabel) ./doc/training-guides/module002-ch000-openstack-networking.xml:9(title) ./doc/training-guides/bk001-ch007-associate-network-node.xml:14(title) +msgid "Networking in OpenStack" +msgstr "" + +#: ./doc/training-guides/module002-ch001-networking-in-openstack.xml:9(para) +msgid "OpenStack Networking provides a rich tenant-facing API for defining network connectivity and addressing in the cloud. The OpenStack Networking project gives operators the ability to leverage different networking technologies to power their cloud networking. It is a virtual network service that provides a powerful API to define the network connectivity and addressing used by devices from other services, such as OpenStack Compute. It has a rich API which consists of the following components." +msgstr "" + +#: ./doc/training-guides/module002-ch001-networking-in-openstack.xml:20(para) +msgid "Network: An isolated L2 segment, analogous to VLAN in the physical networking world." +msgstr "" + +#: ./doc/training-guides/module002-ch001-networking-in-openstack.xml:25(para) +msgid "Subnet: A block of v4 or v6 IP addresses and associated configuration state." +msgstr "" + +#: ./doc/training-guides/module002-ch001-networking-in-openstack.xml:30(para) +msgid "Port: A connection point for attaching a single device, such as the NIC of a virtual server, to a virtual network. Also describes the associated network configuration, such as the MAC and IP addresses to be used on that port." +msgstr "" + +#: ./doc/training-guides/module002-ch001-networking-in-openstack.xml:38(para) +msgid "You can configure rich network topologies by creating and configuring networks and subnets, and then instructing other OpenStack services like OpenStack Compute to attach virtual devices to ports on these networks. In particular, OpenStack Networking supports each tenant having multiple private networks, and allows tenants to choose their own IP addressing scheme, even if those IP addresses overlap with those used by other tenants. This enables very advanced cloud networking use cases, such as building multi-tiered web applications and allowing applications to be migrated to the cloud without changing IP addresses." +msgstr "" + +#: ./doc/training-guides/module002-ch001-networking-in-openstack.xml:50(guilabel) +msgid "Plugin Architecture: Flexibility to Choose Different Network Technologies" +msgstr "" + +#: ./doc/training-guides/module002-ch001-networking-in-openstack.xml:52(para) +msgid "Enhancing traditional networking solutions to provide rich cloud networking is challenging. Traditional networking is not designed to scale to cloud proportions or to configure automatically." +msgstr "" + +#: ./doc/training-guides/module002-ch001-networking-in-openstack.xml:56(para) +msgid "The original OpenStack Compute network implementation assumed a very basic model of performing all isolation through Linux VLANs and IP tables. OpenStack Networking introduces the concept of a plugin, which is a pluggable back-end implementation of the OpenStack Networking API. A plugin can use a variety of technologies to implement the logical API requests. Some OpenStack Networking plugins might use basic Linux VLANs and IP tables, while others might use more advanced technologies, such as L2-in-L3 tunneling or OpenFlow, to provide similar benefits." +msgstr "" + +#: ./doc/training-guides/module002-ch001-networking-in-openstack.xml:66(para) +msgid "The current set of plugins include:" +msgstr "" + +#: ./doc/training-guides/module002-ch001-networking-in-openstack.xml:69(para) +msgid "Open vSwitch: Documentation included in this guide." +msgstr "" + +#: ./doc/training-guides/module002-ch001-networking-in-openstack.xml:73(para) +msgid "Cisco: Documented externally at: http://wiki.openstack.org/cisco-quantum" +msgstr "" + +#: ./doc/training-guides/module002-ch001-networking-in-openstack.xml:79(para) +msgid "Linux Bridge: Documentation included in this guide and http://wiki.openstack.org/Quantum-Linux-Bridge-Plugin" +msgstr "" + +#: ./doc/training-guides/module002-ch001-networking-in-openstack.xml:86(para) +msgid "Nicira NVP: Documentation include in this guide, NVP Product Overview , and NVP Product Support." +msgstr "" + +#: ./doc/training-guides/module002-ch001-networking-in-openstack.xml:94(emphasis) +msgid "Ryu:" +msgstr "" + +#: ./doc/training-guides/module002-ch001-networking-in-openstack.xml:97(link) +msgid "https://github.com/osrg/ryu/wiki/OpenStack" +msgstr "" + +#: ./doc/training-guides/module002-ch001-networking-in-openstack.xml:100(emphasis) +msgid "NEC OpenFlow:" +msgstr "" + +#: ./doc/training-guides/module002-ch001-networking-in-openstack.xml:103(link) +msgid "http://wiki.openstack.org/Quantum-NEC-OpenFlow-Plugin" +msgstr "" + +#: ./doc/training-guides/module002-ch001-networking-in-openstack.xml:106(emphasis) +msgid "Big Switch, Floodlight REST Proxy:" +msgstr "" + +#: ./doc/training-guides/module002-ch001-networking-in-openstack.xml:110(link) +msgid "http://www.openflowhub.org/display/floodlightcontroller/Quantum+REST+Proxy+Plugin" +msgstr "" + +#: ./doc/training-guides/module002-ch001-networking-in-openstack.xml:113(emphasis) +msgid "PLUMgrid:" +msgstr "" + +#: ./doc/training-guides/module002-ch001-networking-in-openstack.xml:116(link) +msgid "https://wiki.openstack.org/wiki/Plumgrid-quantum" +msgstr "" + +#: ./doc/training-guides/module002-ch001-networking-in-openstack.xml:119(emphasis) +msgid "Hyper-V Plugin" +msgstr "" + +#: ./doc/training-guides/module002-ch001-networking-in-openstack.xml:123(emphasis) +msgid "Brocade Plugin" +msgstr "" + +#: ./doc/training-guides/module002-ch001-networking-in-openstack.xml:127(emphasis) +msgid "Midonet Plugin" +msgstr "" + +#: ./doc/training-guides/module002-ch001-networking-in-openstack.xml:131(para) +msgid "Plugins can have different properties in terms of hardware requirements, features, performance, scale, operator tools, etc. Supporting many plugins enables the cloud administrator to weigh different options and decide which networking technology is right for the deployment." +msgstr "" + +#: ./doc/training-guides/module002-ch001-networking-in-openstack.xml:136(para) +msgid "Components of OpenStack Networking" +msgstr "" + +#: ./doc/training-guides/module002-ch001-networking-in-openstack.xml:137(para) +msgid "To deploy OpenStack Networking, it is useful to understand the different components that make up the solution and how those components interact with each other and with other OpenStack services." +msgstr "" + +#: ./doc/training-guides/module002-ch001-networking-in-openstack.xml:141(para) +msgid "OpenStack Networking is a standalone service, just like other OpenStack services such as OpenStack Compute, OpenStack Image service, OpenStack Identity service, and the OpenStack Dashboard. Like those services, a deployment of OpenStack Networking often involves deploying several processes on a variety of hosts." +msgstr "" + +#: ./doc/training-guides/module002-ch001-networking-in-openstack.xml:147(para) +msgid "The main process of the OpenStack Networking server is quantum-server, which is a Python daemon that exposes the OpenStack Networking API and passes user requests to the configured OpenStack Networking plugin for additional processing. Typically, the plugin requires access to a database for persistent storage, similar to other OpenStack services." +msgstr "" + +#: ./doc/training-guides/module002-ch001-networking-in-openstack.xml:154(para) +msgid "If your deployment uses a controller host to run centralized OpenStack Compute components, you can deploy the OpenStack Networking server on that same host. However, OpenStack Networking is entirely standalone and can be deployed on its own server as well. OpenStack Networking also includes additional agents that might be required depending on your deployment:" +msgstr "" + +#: ./doc/training-guides/module002-ch001-networking-in-openstack.xml:163(para) +msgid "plugin agent (quantum-*-agent):Runs on each hypervisor to perform local vswitch configuration. Agent to be run depends on which plugin you are using, as some plugins do not require an agent." +msgstr "" + +#: ./doc/training-guides/module002-ch001-networking-in-openstack.xml:170(para) +msgid "dhcp agent (quantum-dhcp-agent):Provides DHCP services to tenant networks. This agent is the same across all plugins." +msgstr "" + +#: ./doc/training-guides/module002-ch001-networking-in-openstack.xml:176(para) +msgid "l3 agent (quantum-l3-agent):Provides L3/NAT forwarding to provide external network access for VMs on tenant networks. This agent is the same across all plugins." +msgstr "" + +#: ./doc/training-guides/module002-ch001-networking-in-openstack.xml:183(para) +msgid "These agents interact with the main quantum-server process in the following ways:" +msgstr "" + +#: ./doc/training-guides/module002-ch001-networking-in-openstack.xml:187(para) +msgid "Through RPC. For example, rabbitmq or qpid." +msgstr "" + +#: ./doc/training-guides/module002-ch001-networking-in-openstack.xml:190(para) +msgid "Through the standard OpenStack Networking API." +msgstr "" + +#: ./doc/training-guides/module002-ch001-networking-in-openstack.xml:194(para) +msgid "OpenStack Networking relies on the OpenStack Identity Project (Keystone) for authentication and authorization of all API request." +msgstr "" + +#: ./doc/training-guides/module002-ch001-networking-in-openstack.xml:197(para) +msgid "OpenStack Compute interacts with OpenStack Networking through calls to its standard API. As part of creating a VM, nova-compute communicates with the OpenStack Networking API to plug each virtual NIC on the VM into a particular network." +msgstr "" + +#: ./doc/training-guides/module002-ch001-networking-in-openstack.xml:202(para) +msgid "The OpenStack Dashboard (Horizon) has integration with the OpenStack Networking API, allowing administrators and tenant users, to create and manage network services through the Horizon GUI." +msgstr "" + +#: ./doc/training-guides/module002-ch001-networking-in-openstack.xml:206(emphasis) +msgid "Place Services on Physical Hosts" +msgstr "" + +#: ./doc/training-guides/module002-ch001-networking-in-openstack.xml:208(para) +msgid "Like other OpenStack services, OpenStack Networking provides cloud administrators with significant flexibility in deciding which individual services should run on which physical devices. On one extreme, all service daemons can be run on a single physical host for evaluation purposes. On the other, each service could have its own physical hosts, and some cases be replicated across multiple hosts for redundancy." +msgstr "" + +#: ./doc/training-guides/module002-ch001-networking-in-openstack.xml:215(para) +msgid "In this guide, we focus primarily on a standard architecture that includes a “cloud controller” host, a “network gateway” host, and a set of hypervisors for running VMs. The \"cloud controller\" and \"network gateway\" can be combined in simple deployments, though if you expect VMs to send significant amounts of traffic to or from the Internet, a dedicated network gateway host is suggested to avoid potential CPU contention between packet forwarding performed by the quantum-l3-agent and other OpenStack services." +msgstr "" + +#: ./doc/training-guides/module002-ch001-networking-in-openstack.xml:224(emphasis) +msgid "Network Connectivity for Physical Hosts" +msgstr "" + +#: ./doc/training-guides/module002-ch001-networking-in-openstack.xml:227(title) ./doc/training-guides/lab002-network-node.xml:11(title) ./doc/training-guides/lab003-compute-node.xml:14(title) ./doc/training-guides/lab001-control-node.xml:10(title) ./doc/training-guides/lab000-virtualbox-basics.xml:135(title) +msgid "Network Diagram" +msgstr "" + +#: ./doc/training-guides/module002-ch001-networking-in-openstack.xml:234(para) +msgid "A standard OpenStack Networking setup has up to four distinct physical data center networks:" +msgstr "" + +#: ./doc/training-guides/module002-ch001-networking-in-openstack.xml:238(para) +msgid "Management network:Used for internal communication between OpenStack Components. The IP addresses on this network should be reachable only within the data center." +msgstr "" + +#: ./doc/training-guides/module002-ch001-networking-in-openstack.xml:245(para) +msgid "Data network:Used for VM data communication within the cloud deployment. The IP addressing requirements of this network depend on the OpenStack Networking plugin in use." +msgstr "" + +#: ./doc/training-guides/module002-ch001-networking-in-openstack.xml:251(para) +msgid "External network:Used to provide VMs with Internet access in some deployment scenarios. The IP addresses on this network should be reachable by anyone on the Internet." +msgstr "" + +#: ./doc/training-guides/module002-ch001-networking-in-openstack.xml:258(para) +msgid "API network:Exposes all OpenStack APIs, including the OpenStack Networking API, to tenants. The IP addresses on this network should be reachable by anyone on the Internet. This may be the same network as the external network, as it is possible to create a subnet for the external network that uses IP allocation ranges to use only less than the full range of IP addresses in an IP block." +msgstr "" + +#. When image changes, this message will be marked fuzzy or untranslated for you. +#. It doesn't matter what you translate it to: it's not used at all. +#: ./doc/training-guides/module003-ch004-swift-building-blocks.xml:52(None) +msgid "@@image: 'figures/image40.png'; md5=ed79466c8464513dbeaf1e0954280e5e" +msgstr "" + +#. When image changes, this message will be marked fuzzy or untranslated for you. +#. It doesn't matter what you translate it to: it's not used at all. +#: ./doc/training-guides/module003-ch004-swift-building-blocks.xml:116(None) +msgid "@@image: 'figures/image41.png'; md5=a94e26734cec6980c3684d9e824eac2d" +msgstr "" + +#. When image changes, this message will be marked fuzzy or untranslated for you. +#. It doesn't matter what you translate it to: it's not used at all. +#: ./doc/training-guides/module003-ch004-swift-building-blocks.xml:169(None) +msgid "@@image: 'figures/image42.png'; md5=1b1dc0abe6ea0c516f22ce399deb75ed" +msgstr "" + +#. When image changes, this message will be marked fuzzy or untranslated for you. +#. It doesn't matter what you translate it to: it's not used at all. +#: ./doc/training-guides/module003-ch004-swift-building-blocks.xml:187(None) +msgid "@@image: 'figures/image43.png'; md5=4b15e5a202db5bde53c9b369058aeab8" +msgstr "" + +#. When image changes, this message will be marked fuzzy or untranslated for you. +#. It doesn't matter what you translate it to: it's not used at all. +#: ./doc/training-guides/module003-ch004-swift-building-blocks.xml:219(None) +msgid "@@image: 'figures/image44.png'; md5=2c161c2e92d6fefc8140ec86e79e9492" +msgstr "" + +#. When image changes, this message will be marked fuzzy or untranslated for you. +#. It doesn't matter what you translate it to: it's not used at all. +#: ./doc/training-guides/module003-ch004-swift-building-blocks.xml:252(None) +msgid "@@image: 'figures/image45.png'; md5=9d55594d7f445764569ab04d8d4373b2" +msgstr "" + +#. When image changes, this message will be marked fuzzy or untranslated for you. +#. It doesn't matter what you translate it to: it's not used at all. +#: ./doc/training-guides/module003-ch004-swift-building-blocks.xml:283(None) +msgid "@@image: 'figures/image46.png'; md5=07480e7175b383171173775fb96d70d7" +msgstr "" + +#: ./doc/training-guides/module003-ch004-swift-building-blocks.xml:7(title) +msgid "Building Blocks of Swift" +msgstr "" + +#: ./doc/training-guides/module003-ch004-swift-building-blocks.xml:8(para) +msgid "The components that enable Swift to deliver high availability, high durability and high concurrency are:" +msgstr "" + +#: ./doc/training-guides/module003-ch004-swift-building-blocks.xml:13(para) +msgid "Proxy Servers:Handles all incoming API requests." +msgstr "" + +#: ./doc/training-guides/module003-ch004-swift-building-blocks.xml:18(para) +msgid "Rings:Maps logical names of data to locations on particular disks." +msgstr "" + +#: ./doc/training-guides/module003-ch004-swift-building-blocks.xml:23(para) +msgid "Zones:Each Zone isolates data from other Zones. A failure in one Zone doesn’t impact the rest of the cluster because data is replicated across the Zones." +msgstr "" + +#: ./doc/training-guides/module003-ch004-swift-building-blocks.xml:29(para) +msgid "Accounts & Containers:Each Account and Container are individual databases that are distributed across the cluster. An Account database contains the list of Containers in that Account. A Container database contains the list of Objects in that Container" +msgstr "" + +#: ./doc/training-guides/module003-ch004-swift-building-blocks.xml:37(para) +msgid "Objects:The data itself." +msgstr "" + +#: ./doc/training-guides/module003-ch004-swift-building-blocks.xml:41(para) +msgid "Partitions:A Partition stores Objects, Account databases and Container databases. It’s an intermediate 'bucket' that helps manage locations where data lives in the cluster." +msgstr "" + +#: ./doc/training-guides/module003-ch004-swift-building-blocks.xml:49(title) +msgid "Building Blocks" +msgstr "" + +#: ./doc/training-guides/module003-ch004-swift-building-blocks.xml:56(guilabel) +msgid "Proxy Servers" +msgstr "" + +#: ./doc/training-guides/module003-ch004-swift-building-blocks.xml:57(para) +msgid "The Proxy Servers are the public face of Swift and handle all incoming API requests. Once a Proxy Server receive a request, it will determine the storage node based on the URL of the object, such as https://swift.example.com/v1/account/container/object . The Proxy Servers also coordinates responses, handles failures and coordinates timestamps." +msgstr "" + +#: ./doc/training-guides/module003-ch004-swift-building-blocks.xml:64(para) +msgid "Proxy servers use a shared-nothing architecture and can be scaled as needed based on projected workloads. A minimum of two Proxy Servers should be deployed for redundancy. Should one proxy server fail, the others will take over." +msgstr "" + +#: ./doc/training-guides/module003-ch004-swift-building-blocks.xml:69(guilabel) +msgid "The Ring" +msgstr "" + +#: ./doc/training-guides/module003-ch004-swift-building-blocks.xml:70(para) +msgid "A ring represents a mapping between the names of entities stored on disk and their physical location. There are separate rings for accounts, containers, and objects. When other components need to perform any operation on an object, container, or account, they need to interact with the appropriate ring to determine its location in the cluster." +msgstr "" + +#: ./doc/training-guides/module003-ch004-swift-building-blocks.xml:77(para) +msgid "The Ring maintains this mapping using zones, devices, partitions, and replicas. Each partition in the ring is replicated, by default, 3 times across the cluster, and the locations for a partition are stored in the mapping maintained by the ring. The ring is also responsible for determining which devices are used for hand off in failure scenarios." +msgstr "" + +#: ./doc/training-guides/module003-ch004-swift-building-blocks.xml:84(para) +msgid "Data can be isolated with the concept of zones in the ring. Each replica of a partition is guaranteed to reside in a different zone. A zone could represent a drive, a server, a cabinet, a switch, or even a data center." +msgstr "" + +#: ./doc/training-guides/module003-ch004-swift-building-blocks.xml:88(para) +msgid "The partitions of the ring are equally divided among all the devices in the OpenStack Object Storage installation. When partitions need to be moved around, such as when a device is added to the cluster, the ring ensures that a minimum number of partitions are moved at a time, and only one replica of a partition is moved at a time." +msgstr "" + +#: ./doc/training-guides/module003-ch004-swift-building-blocks.xml:94(para) +msgid "Weights can be used to balance the distribution of partitions on drives across the cluster. This can be useful, for example, when different sized drives are used in a cluster." +msgstr "" + +#: ./doc/training-guides/module003-ch004-swift-building-blocks.xml:98(para) +msgid "The ring is used by the Proxy server and several background processes (like replication)." +msgstr "" + +#: ./doc/training-guides/module003-ch004-swift-building-blocks.xml:100(para) +msgid "The Ring maps Partitions to physical locations on disk. When other components need to perform any operation on an object, container, or account, they need to interact with the Ring to determine its location in the cluster." +msgstr "" + +#: ./doc/training-guides/module003-ch004-swift-building-blocks.xml:104(para) +msgid "The Ring maintains this mapping using zones, devices, partitions, and replicas. Each partition in the Ring is replicated three times by default across the cluster, and the locations for a partition are stored in the mapping maintained by the Ring. The Ring is also responsible for determining which devices are used for handoff should a failure occur." +msgstr "" + +#: ./doc/training-guides/module003-ch004-swift-building-blocks.xml:112(title) +msgid "The Lord of the Rings" +msgstr "" + +#: ./doc/training-guides/module003-ch004-swift-building-blocks.xml:120(para) +msgid "The Ring maps partitions to physical locations on disk." +msgstr "" + +#: ./doc/training-guides/module003-ch004-swift-building-blocks.xml:122(para) +msgid "The rings determine where data should reside in the cluster. There is a separate ring for account databases, container databases, and individual objects but each ring works in the same way. These rings are externally managed, in that the server processes themselves do not modify the rings, they are instead given new rings modified by other tools." +msgstr "" + +#: ./doc/training-guides/module003-ch004-swift-building-blocks.xml:129(para) +msgid "The ring uses a configurable number of bits from a path’s MD5 hash as a partition index that designates a device. The number of bits kept from the hash is known as the partition power, and 2 to the partition power indicates the partition count. Partitioning the full MD5 hash ring allows other parts of the cluster to work in batches of items at once which ends up either more efficient or at least less complex than working with each item separately or the entire cluster all at once." +msgstr "" + +#: ./doc/training-guides/module003-ch004-swift-building-blocks.xml:138(para) +msgid "Another configurable value is the replica count, which indicates how many of the partition->device assignments comprise a single ring. For a given partition number, each replica’s device will not be in the same zone as any other replica's device. Zones can be used to group devices based on physical locations, power separations, network separations, or any other attribute that would lessen multiple replicas being unavailable at the same time." +msgstr "" + +#: ./doc/training-guides/module003-ch004-swift-building-blocks.xml:146(guilabel) +msgid "Zones: Failure Boundaries" +msgstr "" + +#: ./doc/training-guides/module003-ch004-swift-building-blocks.xml:147(para) +msgid "Swift allows zones to be configured to isolate failure boundaries. Each replica of the data resides in a separate zone, if possible. At the smallest level, a zone could be a single drive or a grouping of a few drives. If there were five object storage servers, then each server would represent its own zone. Larger deployments would have an entire rack (or multiple racks) of object servers, each representing a zone. The goal of zones is to allow the cluster to tolerate significant outages of storage servers without losing all replicas of the data." +msgstr "" + +#: ./doc/training-guides/module003-ch004-swift-building-blocks.xml:158(para) +msgid "As we learned earlier, everything in Swift is stored, by default, three times. Swift will place each replica \"as-uniquely-as-possible\" to ensure both high availability and high durability. This means that when choosing a replica location, Swift will choose a server in an unused zone before an unused server in a zone that already has a replica of the data." +msgstr "" + +#: ./doc/training-guides/module003-ch004-swift-building-blocks.xml:166(title) +msgid "image33.png" +msgstr "" + +#: ./doc/training-guides/module003-ch004-swift-building-blocks.xml:173(para) +msgid "When a disk fails, replica data is automatically distributed to the other zones to ensure there are three copies of the data" +msgstr "" + +#: ./doc/training-guides/module003-ch004-swift-building-blocks.xml:176(guilabel) +msgid "Accounts & Containers" +msgstr "" + +#: ./doc/training-guides/module003-ch004-swift-building-blocks.xml:178(para) +msgid "Each account and container is an individual SQLite database that is distributed across the cluster. An account database contains the list of containers in that account. A container database contains the list of objects in that container." +msgstr "" + +#: ./doc/training-guides/module003-ch004-swift-building-blocks.xml:184(title) +msgid "Accounts and Containers" +msgstr "" + +#: ./doc/training-guides/module003-ch004-swift-building-blocks.xml:191(para) +msgid "To keep track of object data location, each account in the system has a database that references all its containers, and each container database references each object" +msgstr "" + +#: ./doc/training-guides/module003-ch004-swift-building-blocks.xml:195(guilabel) ./doc/training-guides/module003-ch004-swift-building-blocks.xml:216(title) +msgid "Partitions" +msgstr "" + +#: ./doc/training-guides/module003-ch004-swift-building-blocks.xml:196(para) +msgid "A Partition is a collection of stored data, including Account databases, Container databases, and objects. Partitions are core to the replication system." +msgstr "" + +#: ./doc/training-guides/module003-ch004-swift-building-blocks.xml:200(para) +msgid "Think of a Partition as a bin moving throughout a fulfillment center warehouse. Individual orders get thrown into the bin. The system treats that bin as a cohesive entity as it moves throughout the system. A bin full of things is easier to deal with than lots of little things. It makes for fewer moving parts throughout the system." +msgstr "" + +#: ./doc/training-guides/module003-ch004-swift-building-blocks.xml:207(para) +msgid "The system replicators and object uploads/downloads operate on Partitions. As the system scales up, behavior continues to be predictable as the number of Partitions is a fixed number." +msgstr "" + +#: ./doc/training-guides/module003-ch004-swift-building-blocks.xml:211(para) +msgid "The implementation of a Partition is conceptually simple -- a partition is just a directory sitting on a disk with a corresponding hash table of what it contains." +msgstr "" + +#: ./doc/training-guides/module003-ch004-swift-building-blocks.xml:223(para) +msgid "*Swift partitions contain all data in the system." +msgstr "" + +#: ./doc/training-guides/module003-ch004-swift-building-blocks.xml:226(para) +msgid "In order to ensure that there are three copies of the data everywhere, replicators continuously examine each Partition. For each local Partition, the replicator compares it against the replicated copies in the other Zones to see if there are any differences." +msgstr "" + +#: ./doc/training-guides/module003-ch004-swift-building-blocks.xml:232(para) +msgid "How does the replicator know if replication needs to take place? It does this by examining hashes. A hash file is created for each Partition, which contains hashes of each directory in the Partition. Each of the three hash files is compared. For a given Partition, the hash files for each of the Partition's copies are compared. If the hashes are different, then it is time to replicate and the directory that needs to be replicated is copied over." +msgstr "" + +#: ./doc/training-guides/module003-ch004-swift-building-blocks.xml:241(para) +msgid "This is where the Partitions come in handy. With fewer \"things\" in the system, larger chunks of data are transferred around (rather than lots of little TCP connections, which is inefficient) and there are a consistent number of hashes to compare." +msgstr "" + +#: ./doc/training-guides/module003-ch004-swift-building-blocks.xml:246(para) +msgid "The cluster has eventually consistent behavior where the newest data wins." +msgstr "" + +#: ./doc/training-guides/module003-ch004-swift-building-blocks.xml:256(para) +msgid "*If a zone goes down, one of the nodes containing a replica notices and proactively copies data to a handoff location." +msgstr "" + +#: ./doc/training-guides/module003-ch004-swift-building-blocks.xml:259(para) +msgid "To describe how these pieces all come together, let's walk through a few scenarios and introduce the components." +msgstr "" + +#: ./doc/training-guides/module003-ch004-swift-building-blocks.xml:261(guilabel) +msgid "Bird-eye View" +msgstr "" + +#: ./doc/training-guides/module003-ch004-swift-building-blocks.xml:262(emphasis) +msgid "Upload" +msgstr "" + +#: ./doc/training-guides/module003-ch004-swift-building-blocks.xml:264(para) +msgid "A client uses the REST API to make a HTTP request to PUT an object into an existing Container. The cluster receives the request. First, the system must figure out where the data is going to go. To do this, the Account name, Container name and Object name are all used to determine the Partition where this object should live." +msgstr "" + +#: ./doc/training-guides/module003-ch004-swift-building-blocks.xml:270(para) +msgid "Then a lookup in the Ring figures out which storage nodes contain the Partitions in question." +msgstr "" + +#: ./doc/training-guides/module003-ch004-swift-building-blocks.xml:272(para) +msgid "The data then is sent to each storage node where it is placed in the appropriate Partition. A quorum is required -- at least two of the three writes must be successful before the client is notified that the upload was successful." +msgstr "" + +#: ./doc/training-guides/module003-ch004-swift-building-blocks.xml:277(para) +msgid "Next, the Container database is updated asynchronously to reflect that there is a new object in it." +msgstr "" + +#: ./doc/training-guides/module003-ch004-swift-building-blocks.xml:280(title) +msgid "When End-User uses Swift" +msgstr "" + +#: ./doc/training-guides/module003-ch004-swift-building-blocks.xml:287(emphasis) +msgid "Download" +msgstr "" + +#: ./doc/training-guides/module003-ch004-swift-building-blocks.xml:288(para) +msgid "A request comes in for an Account/Container/object. Using the same consistent hashing, the Partition name is generated. A lookup in the Ring reveals which storage nodes contain that Partition. A request is made to one of the storage nodes to fetch the object and if that fails, requests are made to the other nodes." +msgstr "" + +#. When image changes, this message will be marked fuzzy or untranslated for you. +#. It doesn't matter what you translate it to: it's not used at all. +#: ./doc/training-guides/user-story-includes-template.xml:19(None) +msgid "@@image: 'figures/openstack-training-example-image.png'; md5=87bf110d5b53b2168680e1370176ef02" +msgstr "" + +#: ./doc/training-guides/user-story-includes-template.xml:7(title) +msgid "Including external content for user stories, version 1.3" +msgstr "" + +#: ./doc/training-guides/user-story-includes-template.xml:8(para) +msgid "Save your user story file as associate-my-user-story-name, operator-my-user-story, etc. For example my user story that I assigned myself is operator bug fix so the file name would be operator-fix-documentation-bug.xml. See the operator-fix-documentation-bug.xml file in the repository for more details." +msgstr "" + +#: ./doc/training-guides/user-story-includes-template.xml:12(para) +msgid "The include statements below are meant to help you tell and teach the user story. Include as much content as necessary. Use examples." +msgstr "" + +#: ./doc/training-guides/user-story-includes-template.xml:14(para) +msgid "Create diagrams through gdraw. Export as png. Reference as local file in the /figures/ director. Share as 'Anyone With the Link' can 'Edit' and add URL to the description so anyone else can update the original." +msgstr "" + +#: ./doc/training-guides/user-story-includes-template.xml:17(para) +msgid " big dummy example image" +msgstr "" + +#: ./doc/training-guides/user-story-includes-template.xml:22(para) ./doc/training-guides/card074-horizon-snapshots.xml:12(para) ./doc/training-guides/card071-create-cinder-horizon.xml:11(para) ./doc/training-guides/card071-create-cinder-horizon.xml:15(para) ./doc/training-guides/card071-create-cinder-horizon.xml:19(para) ./doc/training-guides/bk001-ch003-associate-controller-node.xml:17(para) ./doc/training-guides/bk001-ch003-associate-controller-node.xml:24(para) ./doc/training-guides/bk001-ch003-associate-controller-node.xml:31(para) ./doc/training-guides/bk001-ch003-associate-controller-node.xml:40(para) ./doc/training-guides/bk001-ch003-associate-controller-node.xml:47(para) ./doc/training-guides/bk001-ch003-associate-controller-node.xml:54(para) ./doc/training-guides/bk001-ch003-associate-controller-node.xml:61(para) ./doc/training-guides/bk001-ch003-associate-controller-node.xml:68(para) ./doc/training-guides/bk001-ch003-associate-controller-node.xml:75(para) ./doc/training-guides/bk001-ch003-associate-controller-node.xml:82(para) ./doc/training-guides/bk002-ch010-operator-network-node.xml:17(para) ./doc/training-guides/bk002-ch010-operator-network-node.xml:24(para) ./doc/training-guides/bk001-ch009-associate-object-storage-node.xml:17(para) ./doc/training-guides/bk001-ch009-associate-object-storage-node.xml:24(para) ./doc/training-guides/bk001-ch009-associate-object-storage-node.xml:33(para) ./doc/training-guides/card072-cinder-attach-volume.xml:11(para) ./doc/training-guides/bk002-ch004-operator-controller-node.xml:17(para) ./doc/training-guides/bk002-ch004-operator-controller-node.xml:24(para) ./doc/training-guides/bk002-ch004-operator-controller-node.xml:31(para) ./doc/training-guides/bk002-ch002-operator-getting-started-lab.xml:15(para) ./doc/training-guides/bk002-ch002-operator-getting-started-lab.xml:22(para) ./doc/training-guides/bk002-ch002-operator-getting-started-lab.xml:29(para) ./doc/training-guides/bk002-ch002-operator-getting-started-lab.xml:36(para) ./doc/training-guides/bk002-ch002-operator-getting-started-lab.xml:43(para) ./doc/training-guides/bk002-ch007-operator-compute-node.xml:17(para) ./doc/training-guides/bk002-ch007-operator-compute-node.xml:24(para) ./doc/training-guides/bk002-ch007-operator-compute-node.xml:31(para) ./doc/training-guides/bk002-ch013-operator-object-storage-node.xml:17(para) ./doc/training-guides/bk002-ch013-operator-object-storage-node.xml:24(para) ./doc/training-guides/bk002-ch013-operator-object-storage-node.xml:35(para) ./doc/training-guides/bk002-ch013-operator-object-storage-node.xml:42(para) ./doc/training-guides/bk002-ch013-operator-object-storage-node.xml:49(para) ./doc/training-guides/bk002-ch013-operator-object-storage-node.xml:55(para) ./doc/training-guides/bk002-ch013-operator-object-storage-node.xml:62(para) ./doc/training-guides/bk002-ch013-operator-object-storage-node.xml:69(para) ./doc/training-guides/bk002-ch013-operator-object-storage-node.xml:76(para) ./doc/training-guides/bk002-ch001-operator-getting-started.xml:25(para) ./doc/training-guides/bk002-ch001-operator-getting-started.xml:32(para) ./doc/training-guides/bk002-ch001-operator-getting-started.xml:39(para) ./doc/training-guides/bk002-ch001-operator-getting-started.xml:46(para) ./doc/training-guides/bk002-ch001-operator-getting-started.xml:53(para) ./doc/training-guides/card008.xml:11(para) ./doc/training-guides/bk000-preface.xml:133(para) ./doc/training-guides/bk000-preface.xml:140(para) ./doc/training-guides/bk000-preface.xml:147(para) ./doc/training-guides/bk001-ch001-associate-getting-started.xml:27(para) ./doc/training-guides/bk001-ch001-associate-getting-started.xml:34(para) ./doc/training-guides/bk001-ch001-associate-getting-started.xml:41(para) ./doc/training-guides/bk001-ch001-associate-getting-started.xml:48(para) ./doc/training-guides/bk001-ch001-associate-getting-started.xml:55(para) ./doc/training-guides/card073-control-state-instance.xml:12(para) ./doc/training-guides/bk001-ch005-associate-compute-node.xml:17(para) ./doc/training-guides/bk001-ch005-associate-compute-node.xml:24(para) ./doc/training-guides/bk001-ch005-associate-compute-node.xml:31(para) ./doc/training-guides/bk001-ch005-associate-compute-node.xml:40(para) ./doc/training-guides/bk001-ch005-associate-compute-node.xml:47(para) ./doc/training-guides/bk001-ch005-associate-compute-node.xml:54(para) ./doc/training-guides/bk001-ch005-associate-compute-node.xml:61(para) ./doc/training-guides/bk001-ch005-associate-compute-node.xml:68(para) ./doc/training-guides/bk001-ch005-associate-compute-node.xml:75(para) ./doc/training-guides/card128-swift.xml:11(para) ./doc/training-guides/bk003-developer-training-guide.xml:13(para) ./doc/training-guides/bk003-developer-training-guide.xml:20(para) ./doc/training-guides/bk003-developer-training-guide.xml:27(para) ./doc/training-guides/bk003-developer-training-guide.xml:34(para) ./doc/training-guides/bk003-developer-training-guide.xml:41(para) ./doc/training-guides/bk003-developer-training-guide.xml:48(para) ./doc/training-guides/bk003-developer-training-guide.xml:55(para) ./doc/training-guides/bk003-developer-training-guide.xml:62(para) ./doc/training-guides/bk003-developer-training-guide.xml:69(para) ./doc/training-guides/bk001-ch007-associate-network-node.xml:17(para) ./doc/training-guides/bk001-ch007-associate-network-node.xml:24(para) ./doc/training-guides/bk001-ch007-associate-network-node.xml:33(para) ./doc/training-guides/bk001-ch007-associate-network-node.xml:40(para) ./doc/training-guides/card070-create-floating-ips.xml:11(para) ./doc/training-guides/card070-create-floating-ips.xml:16(para) ./doc/training-guides/card070-create-floating-ips.xml:21(para) +msgid "image source" +msgstr "" + +#: ./doc/training-guides/user-story-includes-template.xml:23(link) +msgid "https://docs.google.com/drawings/d/1Tdn4SZLBdvQybW_nK_lO380YRIe5T6PsI0IyLH5XE3M/edit?usp=sharing" +msgstr "" + +#: ./doc/training-guides/user-story-includes-template.xml:25(emphasis) +msgid "Including a whole file. Include as much description about what is being taught here." +msgstr "" + +#: ./doc/training-guides/user-story-includes-template.xml:33(link) ./doc/training-guides/user-story-includes-template.xml:45(link) ./doc/training-guides/card007-core-overview.xml:14(link) ./doc/training-guides/card025.xml:13(link) ./doc/training-guides/card074-horizon-snapshots.xml:14(link) ./doc/training-guides/card071-create-cinder-horizon.xml:21(link) ./doc/training-guides/card009.xml:16(link) ./doc/training-guides/card043-ovs-in-network-node.xml:15(link) ./doc/training-guides/card072-cinder-attach-volume.xml:13(link) ./doc/training-guides/card126-horizon.xml:13(link) ./doc/training-guides/card039-nova.xml:14(link) ./doc/training-guides/card047-install-nova-compute.xml:14(link) ./doc/training-guides/card045-configure-virtual-networking.xml:20(link) ./doc/training-guides/card041-neutron.xml:22(link) ./doc/training-guides/card008.xml:13(link) ./doc/training-guides/card037-rabbitmq.xml:14(link) ./doc/training-guides/card040-cinder.xml:15(link) ./doc/training-guides/card046-L3_Configuration_in_the_Network_Node.xml:14(link) ./doc/training-guides/card127-glance.xml:14(link) ./doc/training-guides/card026-network-node-architecture.xml:14(link) ./doc/training-guides/card044-install-and-configure-neutron-network-node.xml:14(link) ./doc/training-guides/card073-control-state-instance.xml:14(link) ./doc/training-guides/card128-swift.xml:13(link) ./doc/training-guides/card011.xml:14(link) ./doc/training-guides/card070-create-floating-ips.xml:23(link) ./doc/training-guides/card038.xml:13(link) +msgid "Submit a bug on the section above. Short description for the bug summary. Paragraph for the description and then tag with training-manuals." +msgstr "" + +#: ./doc/training-guides/user-story-includes-template.xml:37(emphasis) +msgid "Including a section of a file. Include as much description about what is being taught here." +msgstr "" + +#: ./doc/training-guides/module001-ch011-block-storage.xml:6(title) ./doc/training-guides/bk001-ch005-associate-compute-node.xml:28(title) +msgid "OpenStack Block Storage" +msgstr "" + +#: ./doc/training-guides/module001-ch011-block-storage.xml:7(emphasis) +msgid "Block Storage and OpenStack Compute" +msgstr "" + +#: ./doc/training-guides/module001-ch011-block-storage.xml:9(para) +msgid "OpenStack provides two classes of block storage, \"ephemeral\" storage and persistent \"volumes\". Ephemeral storage exists only for the life of an instance, it will persist across reboots of the guest operating system but when the instance is deleted so is the associated storage. All instances have some ephemeral storage. Volumes are persistent virtualized block devices independent of any particular instance. Volumes may be attached to a single instance at a time, but may be detached or reattached to a different instance while retaining all data, much like a USB drive." +msgstr "" + +#: ./doc/training-guides/module001-ch011-block-storage.xml:19(guilabel) +msgid "Ephemeral Storage" +msgstr "" + +#: ./doc/training-guides/module001-ch011-block-storage.xml:20(para) +msgid "Ephemeral storage is associated with a single unique instance. Its size is defined by the flavor of the instance." +msgstr "" + +#: ./doc/training-guides/module001-ch011-block-storage.xml:22(para) +msgid "Data on ephemeral storage ceases to exist when the instance it is associated with is terminated. Rebooting the VM or restarting the host server, however, will not destroy ephemeral data. In the typical use case an instance's root filesystem is stored on ephemeral storage. This is often an unpleasant surprise for people unfamiliar with the cloud model of computing." +msgstr "" + +#: ./doc/training-guides/module001-ch011-block-storage.xml:28(para) +msgid "In addition to the ephemeral root volume all flavors except the smallest, m1.tiny, provide an additional ephemeral block device varying from 20G for the m1.small through 160G for the m1.xlarge by default - these sizes are configurable. This is presented as a raw block device with no partition table or filesystem. Cloud aware operating system images may discover, format, and mount this device. For example the cloud-init package included in Ubuntu's stock cloud images will format this space as an ext3 filesystem and mount it on /mnt. It is important to note this a feature of the guest operating system. OpenStack only provisions the raw storage." +msgstr "" + +#: ./doc/training-guides/module001-ch011-block-storage.xml:39(guilabel) +msgid "Volume Storage" +msgstr "" + +#: ./doc/training-guides/module001-ch011-block-storage.xml:40(para) +msgid "Volume storage is independent of any particular instance and is persistent. Volumes are user created and within quota and availability limits may be of any arbitrary size." +msgstr "" + +#: ./doc/training-guides/module001-ch011-block-storage.xml:43(para) +msgid "When first created volumes are raw block devices with no partition table and no filesystem. They must be attached to an instance to be partitioned and/or formatted. Once this is done they may be used much like an external disk drive. Volumes may attached to only one instance at a time, but may be detached and reattached to either the same or different instances." +msgstr "" + +#: ./doc/training-guides/module001-ch011-block-storage.xml:49(para) +msgid "It is possible to configure a volume so that it is bootable and provides a persistent virtual instance similar to traditional non-cloud based virtualization systems. In this use case the resulting instance may still have ephemeral storage depending on the flavor selected, but the root filesystem (and possibly others) will be on the persistent volume and thus state will be maintained even if the instance is shutdown. Details of this configuration are discussed in theOpenStack End User Guide." +msgstr "" + +#: ./doc/training-guides/module001-ch011-block-storage.xml:59(para) +msgid "Volumes do not provide concurrent access from multiple instances. For that you need either a traditional network filesystem like NFS or CIFS or a cluster filesystem such as GlusterFS. These may be built within an OpenStack cluster or provisioned outside of it, but are not features provided by the OpenStack software." +msgstr "" + +#: ./doc/training-guides/module001-ch011-block-storage.xml:65(para) +msgid "The OpenStack Block Storage service works via the interaction of a series of daemon processes named cinder-* that reside persistently on the host machine or machines. The binaries can all be run from a single node, or spread across multiple nodes. They can also be run on the same node as other OpenStack services." +msgstr "" + +#: ./doc/training-guides/module001-ch011-block-storage.xml:71(guilabel) +msgid "The current services available in OpenStack Block Storage are:" +msgstr "" + +#: ./doc/training-guides/module001-ch011-block-storage.xml:75(para) +msgid "cinder-api - The cinder-api service is a WSGI app that authenticates and routes requests throughout the Block Storage system. It supports the OpenStack API's only, although there is a translation that can be done via Nova's EC2 interface which calls in to the cinderclient." +msgstr "" + +#: ./doc/training-guides/module001-ch011-block-storage.xml:85(para) +msgid "cinder-scheduler - The cinder-scheduler is responsible for scheduling/routing requests to the appropriate volume service. As of Grizzly; depending upon your configuration this may be simple round-robin scheduling to the running volume services, or it can be more sophisticated through the use of the Filter Scheduler. The Filter Scheduler is the default in Grizzly and enables filter on things like Capacity, Availability Zone, Volume Types and Capabilities as well as custom filters." +msgstr "" + +#: ./doc/training-guides/module001-ch011-block-storage.xml:99(para) +msgid "cinder-volume - The cinder-volume service is responsible for managing Block Storage devices, specifically the back-end devices themselves." +msgstr "" + +#: ./doc/training-guides/module001-ch011-block-storage.xml:107(para) +msgid "cinder-backup - The cinder-backup service provides a means to back up a Cinder Volume to OpenStack Object Store (SWIFT)." +msgstr "" + +#: ./doc/training-guides/module001-ch011-block-storage.xml:112(guilabel) +msgid "Introduction to OpenStack Block Storage" +msgstr "" + +#: ./doc/training-guides/module001-ch011-block-storage.xml:114(para) +msgid "OpenStack Block Storage provides persistent High Performance Block Storage resources that can be consumed by OpenStack Compute instances. This includes secondary attached storage similar to Amazon's Elastic Block Storage (EBS). In addition images can be written to a Block Storage device and specified for OpenStack Compute to use a bootable persistent instance." +msgstr "" + +#: ./doc/training-guides/module001-ch011-block-storage.xml:120(para) +msgid "There are some differences from Amazon's EBS that one should be aware of. OpenStack Block Storage is not a shared storage solution like NFS, but currently is designed so that the device is attached and in use by a single instance at a time." +msgstr "" + +#: ./doc/training-guides/module001-ch011-block-storage.xml:124(guilabel) +msgid "Backend Storage Devices" +msgstr "" + +#: ./doc/training-guides/module001-ch011-block-storage.xml:125(para) +msgid "OpenStack Block Storage requires some form of back-end storage that the service is built on. The default implementation is to use LVM on a local Volume Group named \"cinder-volumes\". In addition to the base driver implementation, OpenStack Block Storage also provides the means to add support for other storage devices to be utilized such as external Raid Arrays or other Storage appliances." +msgstr "" + +#: ./doc/training-guides/module001-ch011-block-storage.xml:132(guilabel) ./doc/training-guides/module001-ch005-vm-provisioning-walk-through.xml:73(guilabel) +msgid "Users and Tenants (Projects)" +msgstr "" + +#: ./doc/training-guides/module001-ch011-block-storage.xml:133(para) +msgid "The OpenStack Block Storage system is designed to be used by many different cloud computing consumers or customers, basically tenants on a shared system, using role-based access assignments. Roles control the actions that a user is allowed to perform. In the default configuration, most actions do not require a particular role, but this is configurable by the system administrator editing the appropriate policy.json file that maintains the rules. A user's access to particular volumes is limited by tenant, but the username and password are assigned per user. Key pairs granting access to a volume are enabled per user, but quotas to control resource consumption across available hardware resources are per tenant." +msgstr "" + +#: ./doc/training-guides/module001-ch011-block-storage.xml:145(guilabel) ./doc/training-guides/module001-ch005-vm-provisioning-walk-through.xml:97(para) +msgid "For tenants, quota controls are available to limit the:" +msgstr "" + +#: ./doc/training-guides/module001-ch011-block-storage.xml:149(para) ./doc/training-guides/module001-ch005-vm-provisioning-walk-through.xml:101(para) +msgid "Number of volumes which may be created" +msgstr "" + +#: ./doc/training-guides/module001-ch011-block-storage.xml:152(para) +msgid "Number of snapshots which may be created" +msgstr "" + +#: ./doc/training-guides/module001-ch011-block-storage.xml:155(para) +msgid "Total number of Giga Bytes allowed per tenant (shared between snapshots and volumes)" +msgstr "" + +#: ./doc/training-guides/module001-ch011-block-storage.xml:159(guilabel) +msgid "Volumes Snapshots and Backups" +msgstr "" + +#: ./doc/training-guides/module001-ch011-block-storage.xml:160(para) +msgid "This introduction provides a high level overview of the two basic resources offered by the OpenStack Block Storage service. The first is Volumes and the second is Snapshots which are derived from Volumes." +msgstr "" + +#: ./doc/training-guides/module001-ch011-block-storage.xml:164(guilabel) ./doc/training-guides/module001-ch006-overview-horizon-cli.xml:129(emphasis) +msgid "Volumes" +msgstr "" + +#: ./doc/training-guides/module001-ch011-block-storage.xml:165(para) +msgid "Volumes are allocated block storage resources that can be attached to instances as secondary storage or they can be used as the root store to boot instances. Volumes are persistent R/W Block Storage devices most commonly attached to the Compute node via iSCSI." +msgstr "" + +#: ./doc/training-guides/module001-ch011-block-storage.xml:170(guilabel) +msgid "Snapshots" +msgstr "" + +#: ./doc/training-guides/module001-ch011-block-storage.xml:171(para) +msgid "A Snapshot in OpenStack Block Storage is a read-only point in time copy of a Volume. The Snapshot can be created from a Volume that is currently in use (via the use of '--force True') or in an available state. The Snapshot can then be used to create a new volume via create from snapshot." +msgstr "" + +#: ./doc/training-guides/module001-ch011-block-storage.xml:176(guilabel) +msgid "Backups" +msgstr "" + +#: ./doc/training-guides/module001-ch011-block-storage.xml:177(para) +msgid "A Backup is an archived copy of a Volume currently stored in Object Storage (Swift)." +msgstr "" + +#: ./doc/training-guides/module001-ch011-block-storage.xml:179(guilabel) +msgid "Managing Volumes" +msgstr "" + +#: ./doc/training-guides/module001-ch011-block-storage.xml:180(para) +msgid "Cinder is the OpenStack service that allows you to give extra block level storage to your OpenStack Compute instances. You may recognize this as a similar offering from Amazon EC2 known as Elastic Block Storage (EBS). The default Cinder implementation is an iSCSI solution that employs the use of Logical Volume Manager (LVM) for Linux. Note that a volume may only be attached to one instance at a time. This is not a ‘shared storage’ solution like a SAN of NFS on which multiple servers can attach to. It's also important to note that Cinder also includes a number of drivers to allow you to use a number of other vendor's back-end storage devices in addition to or instead of the base LVM implementation." +msgstr "" + +#: ./doc/training-guides/module001-ch011-block-storage.xml:192(para) +msgid "Here is brief walk-through of a simple create/attach sequence, keep in mind this requires proper configuration of both OpenStack Compute via cinder.conf and OpenStack Block Storage via cinder.conf." +msgstr "" + +#: ./doc/training-guides/module001-ch011-block-storage.xml:198(para) +msgid "The volume is created via cinder create; which creates an LV into the volume group (VG) \"cinder-volumes\"" +msgstr "" + +#: ./doc/training-guides/module001-ch011-block-storage.xml:202(para) +msgid "The volume is attached to an instance via nova volume-attach; which creates a unique iSCSI IQN that will be exposed to the compute node" +msgstr "" + +#: ./doc/training-guides/module001-ch011-block-storage.xml:207(para) +msgid "The compute node which run the concerned instance has now an active ISCSI session; and a new local storage (usually a /dev/sdX disk)" +msgstr "" + +#: ./doc/training-guides/module001-ch011-block-storage.xml:212(para) +msgid "libvirt uses that local storage as a storage for the instance; the instance get a new disk (usually a /dev/vdX disk)" +msgstr "" + +#: ./doc/training-guides/module001-ch011-block-storage.xml:217(guilabel) +msgid "Block Storage Capabilities" +msgstr "" + +#: ./doc/training-guides/module001-ch011-block-storage.xml:220(para) ./doc/training-guides/module001-ch003-core-projects.xml:374(para) +msgid "OpenStack provides persistent block level storage devices for use with OpenStack compute instances." +msgstr "" + +#: ./doc/training-guides/module001-ch011-block-storage.xml:224(para) ./doc/training-guides/module001-ch003-core-projects.xml:378(para) +msgid "The block storage system manages the creation, attaching and detaching of the block devices to servers. Block storage volumes are fully integrated into OpenStack Compute and the Dashboard allowing for cloud users to manage their own storage needs." +msgstr "" + +#: ./doc/training-guides/module001-ch011-block-storage.xml:231(para) ./doc/training-guides/module001-ch003-core-projects.xml:385(para) +msgid "In addition to using simple Linux server storage, it has unified storage support for numerous storage platforms including Ceph, NetApp, Nexenta, SolidFire, and Zadara." +msgstr "" + +#: ./doc/training-guides/module001-ch011-block-storage.xml:237(para) ./doc/training-guides/module001-ch003-core-projects.xml:391(para) +msgid "Block storage is appropriate for performance sensitive scenarios such as database storage, expandable file systems, or providing a server with access to raw block level storage." +msgstr "" + +#: ./doc/training-guides/module001-ch011-block-storage.xml:243(para) ./doc/training-guides/module001-ch003-core-projects.xml:397(para) +msgid "Snapshot management provides powerful functionality for backing up data stored on block storage volumes. Snapshots can be restored or used to create a new block storage volume." +msgstr "" + +#: ./doc/training-guides/bk001-ch012-associate-review-concept.xml:6(title) +msgid "Review of Concepts" +msgstr "" + +#: ./doc/training-guides/bk001-ch012-associate-review-concept.xml:8(title) +msgid "Day 2, 16:00 to 17:00" +msgstr "" + +#: ./doc/training-guides/bk002-ch015-operator-object-storage-node-quiz.xml:6(title) ./doc/training-guides/bk001-bk010-associate-object-storage-node-quiz.xml:5(title) +msgid "Object Storage Node Quiz" +msgstr "" + +#: ./doc/training-guides/bk002-ch015-operator-object-storage-node-quiz.xml:8(title) +msgid "Day 9, 16:40 to 17:00" +msgstr "" + +#. When image changes, this message will be marked fuzzy or untranslated for you. +#. It doesn't matter what you translate it to: it's not used at all. +#: ./doc/training-guides/module001-ch001-intro-text.xml:102(None) +msgid "@@image: 'figures/image11.png'; md5=e7c8929df3b2e7037fa3a032a7e8370e" +msgstr "" + +#: ./doc/training-guides/module001-ch001-intro-text.xml:6(title) ./doc/training-guides/module001-intro-openstack.xml:5(title) +msgid "Introduction to OpenStack" +msgstr "" + +#: ./doc/training-guides/module001-ch001-intro-text.xml:7(para) +msgid "OpenStack is a cloud operating system that controls large pools of compute, storage, and networking resources throughout a data center, all managed through a dashboard that gives administrators control while empowering users to provision resources through a web interface." +msgstr "" + +#: ./doc/training-guides/module001-ch001-intro-text.xml:12(para) +msgid "Cloud computing provides users with access to a shared collection of computing resources: networks for transfer, servers for storage, and applications or services for completing tasks." +msgstr "" + +#: ./doc/training-guides/module001-ch001-intro-text.xml:16(para) +msgid "The compelling features of a cloud are:" +msgstr "" + +#: ./doc/training-guides/module001-ch001-intro-text.xml:19(para) +msgid "On-demand self-service: Users can automatically provision needed computing capabilities, such as server time and network storage, without requiring human interaction with each service provider." +msgstr "" + +#: ./doc/training-guides/module001-ch001-intro-text.xml:25(para) +msgid "Network access: Any computing capabilities are available over the network. Many different devices are allowed access through standardized mechanisms." +msgstr "" + +#: ./doc/training-guides/module001-ch001-intro-text.xml:30(para) +msgid "Resource pooling: Multiple users can access clouds that serve other consumers according to demand." +msgstr "" + +#: ./doc/training-guides/module001-ch001-intro-text.xml:34(para) +msgid "Elasticity: Provisioning is rapid and scales out or is based on need." +msgstr "" + +#: ./doc/training-guides/module001-ch001-intro-text.xml:38(para) +msgid "Metered or measured service: Cloud systems can optimize and control resource use at the level that is appropriate for the service. Services include storage, processing, bandwidth, and active user accounts. Monitoring and reporting of resource usage provides transparency for both the provider and consumer of the utilized service." +msgstr "" + +#: ./doc/training-guides/module001-ch001-intro-text.xml:46(para) +msgid "Cloud computing offers different service models depending on the capabilities a consumer may require." +msgstr "" + +#: ./doc/training-guides/module001-ch001-intro-text.xml:50(para) +msgid "SaaS: Software as a Service. Provides the consumer the ability to use the software in a cloud environment, such as web-based email for example." +msgstr "" + +#: ./doc/training-guides/module001-ch001-intro-text.xml:55(para) +msgid "PaaS: Platform as a Service. Provides the consumer the ability to deploy applications through a programming language or tools supported by the cloud platform provider. An example of platform as a service is an Eclipse/Java programming platform provided with no downloads required." +msgstr "" + +#: ./doc/training-guides/module001-ch001-intro-text.xml:62(para) +msgid "IaaS: Infrastructure as a Service. Provides infrastructure such as computer instances, network connections, and storage so that people can run any software or operating system." +msgstr "" + +#: ./doc/training-guides/module001-ch001-intro-text.xml:68(para) +msgid "Terms such as public cloud or private cloud refer to the deployment model for the cloud. A private cloud operates for a single organization, but can be managed on-premise or off-premise. A public cloud has an infrastructure that is available to the general public or a large industry group and is likely owned by a cloud services company." +msgstr "" + +#: ./doc/training-guides/module001-ch001-intro-text.xml:74(para) +msgid "Clouds can also be described as hybrid. A hybrid cloud can be a deployment model, as a composition of both public and private clouds, or a hybrid model for cloud computing may involve both virtual and physical servers." +msgstr "" + +#: ./doc/training-guides/module001-ch001-intro-text.xml:78(para) +msgid "Cloud computing can help with large-scale computing needs or can lead consolidation efforts by virtualizing servers to make more use of existing hardware and potentially release old hardware from service. Cloud computing is also used for collaboration because of its high availability through networked computers. Productivity suites for word processing, number crunching, and email communications, and more are also available through cloud computing. Cloud computing also avails additional storage to the cloud user, avoiding the need for additional hard drives on each user's desktop and enabling access to huge data storage capacity online in the cloud." +msgstr "" + +#: ./doc/training-guides/module001-ch001-intro-text.xml:89(para) +msgid "When you explore OpenStack and see what it means technically, you can see its reach and impact on the entire world." +msgstr "" + +#: ./doc/training-guides/module001-ch001-intro-text.xml:91(para) +msgid "OpenStack is an open source software for building private and public clouds which delivers a massively scalable cloud operating system." +msgstr "" + +#: ./doc/training-guides/module001-ch001-intro-text.xml:97(td) +msgid "OpenStack is backed up by a global community of technologists, developers, researchers, corporations and cloud computing experts." +msgstr "" + +#: ./doc/training-guides/lab000-important-terms.xml:6(title) +msgid "Important terms" +msgstr "" + +#: ./doc/training-guides/lab000-important-terms.xml:8(title) +msgid "Host Operating System (Host)" +msgstr "" + +#: ./doc/training-guides/lab000-important-terms.xml:9(para) +msgid "The operating system that is installed on your laptop or desktop that hosts virtual machines. Commonly referred to as host OS or host. In short, the machine where your Virtual Box is installed." +msgstr "" + +#: ./doc/training-guides/lab000-important-terms.xml:16(title) +msgid "Guest Operating System (Guest)" +msgstr "" + +#: ./doc/training-guides/lab000-important-terms.xml:17(para) +msgid "The operating system that is installed on your Virtual Box Virtual Machine. This virtual instance is independent of the host OS. Commonly referred to as guest OS or guest." +msgstr "" + +#: ./doc/training-guides/lab000-important-terms.xml:23(title) +msgid "Node" +msgstr "" + +#: ./doc/training-guides/lab000-important-terms.xml:24(para) +msgid "In this context, refers specifically to servers. Each OpenStack server is a node." +msgstr "" + +#: ./doc/training-guides/lab000-important-terms.xml:28(title) ./doc/training-guides/lab001-control-node.xml:7(title) +msgid "Control Node" +msgstr "" + +#: ./doc/training-guides/lab000-important-terms.xml:29(para) +msgid "Hosts the database, Keystone (Middleware), and the servers for the scope of the current OpenStack deployment. Acts as the brains behind OpenStack and drives services such as authentication, database, and so on." +msgstr "" + +#: ./doc/training-guides/lab000-important-terms.xml:35(title) ./doc/training-guides/lab003-compute-node.xml:7(title) ./doc/training-guides/lab003-compute-node.xml:28(guilabel) ./doc/training-guides/bk002-ch007-operator-compute-node.xml:8(title) ./doc/training-guides/bk001-ch005-associate-compute-node.xml:8(title) +msgid "Compute Node" +msgstr "" + +#: ./doc/training-guides/lab000-important-terms.xml:36(para) +msgid "Has the required Hypervisor (Qemu/KVM) and is your Virtual Machine host." +msgstr "" + +#: ./doc/training-guides/lab000-important-terms.xml:40(title) ./doc/training-guides/lab002-network-node.xml:4(title) ./doc/training-guides/lab002-network-node.xml:23(guilabel) ./doc/training-guides/bk002-ch010-operator-network-node.xml:8(title) ./doc/training-guides/bk001-ch007-associate-network-node.xml:8(title) +msgid "Network Node" +msgstr "" + +#: ./doc/training-guides/lab000-important-terms.xml:41(para) +msgid "Provides Network-as-a-Service and virtual networks for OpenStack." +msgstr "" + +#: ./doc/training-guides/lab000-important-terms.xml:45(title) +msgid "Using OpenSSH" +msgstr "" + +#: ./doc/training-guides/lab000-important-terms.xml:46(para) +msgid "After you set up the network interfaces file, you can switch to an SSH session by using an OpenSSH client to log in remotely to the required server node (Control, Network, Compute). Open a terminal on your host machine. Run the following command: " +msgstr "" + +#: ./doc/training-guides/card007-core-overview.xml:7(title) +msgid "Core Project Overview" +msgstr "" + +#: ./doc/training-guides/bk002-ch014-operator-object-storage-node-lab.xml:6(title) +msgid "Object Storage Node Lab" +msgstr "" + +#: ./doc/training-guides/bk002-ch014-operator-object-storage-node-lab.xml:8(title) +msgid "Day 9, 13:30 to 14:45, 15:00 to 17:00" +msgstr "" + +#: ./doc/training-guides/st-training-guides.xml:9(title) ./doc/training-guides/st-training-guides.xml:11(titleabbrev) ./doc/training-guides/st-training-guides.xml:17(productname) +msgid "OpenStack Training Guides" +msgstr "" + +#: ./doc/training-guides/st-training-guides.xml:14(year) +msgid "2013" +msgstr "" + +#: ./doc/training-guides/st-training-guides.xml:15(holder) +msgid "OpenStack Foundation" +msgstr "" + +#: ./doc/training-guides/st-training-guides.xml:20(remark) ./doc/training-guides/st-training-guides.xml:24(remark) +msgid "Copyright details are filled in by the template." +msgstr "" + +#: ./doc/training-guides/st-training-guides.xml:28(para) +msgid "OpenStack™ Training Guides offer the open source community software training for cloud administration and management for any organization." +msgstr "" + +#: ./doc/training-guides/st-training-guides.xml:35(date) +msgid "2013-11-04" +msgstr "" + +#: ./doc/training-guides/st-training-guides.xml:39(para) +msgid "major restructure of guides" +msgstr "" + +#: ./doc/training-guides/st-training-guides.xml:45(date) +msgid "2013-09-11" +msgstr "" + +#: ./doc/training-guides/st-training-guides.xml:49(para) +msgid "first training guides sprint held" +msgstr "" + +#: ./doc/training-guides/st-training-guides.xml:55(date) +msgid "2013-08-07" +msgstr "" + +#: ./doc/training-guides/st-training-guides.xml:59(para) +msgid "rough draft published to the web" +msgstr "" + +#: ./doc/training-guides/st-training-guides.xml:65(date) +msgid "2013-07-09" +msgstr "" + +#: ./doc/training-guides/st-training-guides.xml:69(para) +msgid "first draft released" +msgstr "" + +#: ./doc/training-guides/st-training-guides.xml:75(date) +msgid "2013-06-18" +msgstr "" + +#: ./doc/training-guides/st-training-guides.xml:79(para) +msgid "blueprint created" +msgstr "" + +#. When image changes, this message will be marked fuzzy or untranslated for you. +#. It doesn't matter what you translate it to: it's not used at all. +#: ./doc/training-guides/module001-ch005-vm-provisioning-walk-through.xml:175(None) +msgid "@@image: 'figures/image21.png'; md5=77049345dd5d86f8f7abe03c0497b1f2" +msgstr "" + +#. When image changes, this message will be marked fuzzy or untranslated for you. +#. It doesn't matter what you translate it to: it's not used at all. +#: ./doc/training-guides/module001-ch005-vm-provisioning-walk-through.xml:193(None) +msgid "@@image: 'figures/image09.png'; md5=69ea6c4853c189bd8c387bb4e534f6a2" +msgstr "" + +#. When image changes, this message will be marked fuzzy or untranslated for you. +#. It doesn't matter what you translate it to: it's not used at all. +#: ./doc/training-guides/module001-ch005-vm-provisioning-walk-through.xml:229(None) +msgid "@@image: 'figures/image22.png'; md5=d92dca8de8639d5a26cef1c8fcc592ed" +msgstr "" + +#: ./doc/training-guides/module001-ch005-vm-provisioning-walk-through.xml:7(title) +msgid "VM Provisioning Walk Through" +msgstr "" + +#: ./doc/training-guides/module001-ch005-vm-provisioning-walk-through.xml:8(para) ./doc/training-guides/module001-ch010-vm-provisioning-indepth.xml:8(para) +msgid "More Content To be Added ..." +msgstr "" + +#: ./doc/training-guides/module001-ch005-vm-provisioning-walk-through.xml:9(para) +msgid "OpenStack Compute gives you a tool to orchestrate a cloud, including running instances, managing networks, and controlling access to the cloud through users and projects. The underlying open source project's name is Nova, and it provides the software that can control an Infrastructure as a Service (IaaS) cloud computing platform. It is similar in scope to Amazon EC2 and Rackspace Cloud Servers. OpenStack Compute does not include any virtualization software; rather it defines drivers that interact with underlying virtualization mechanisms that run on your host operating system, and exposes functionality over a web-based API." +msgstr "" + +#: ./doc/training-guides/module001-ch005-vm-provisioning-walk-through.xml:20(guilabel) +msgid "Hypervisors" +msgstr "" + +#: ./doc/training-guides/module001-ch005-vm-provisioning-walk-through.xml:21(para) +msgid "OpenStack Compute requires a hypervisor and Compute controls the hypervisors through an API server. The process for selecting a hypervisor usually means prioritizing and making decisions based on budget and resource constraints as well as the inevitable list of supported features and required technical specifications. The majority of development is done with the KVM and Xen-based hypervisors. Refer to http://goo.gl/n7AXnC for a detailed list of features and support across the hypervisors." +msgstr "" + +#: ./doc/training-guides/module001-ch005-vm-provisioning-walk-through.xml:32(para) +msgid "With OpenStack Compute, you can orchestrate clouds using multiple hypervisors in different zones. The types of virtualization standards that may be used with Compute include:" +msgstr "" + +#: ./doc/training-guides/module001-ch005-vm-provisioning-walk-through.xml:38(para) +msgid "KVM- Kernel-based Virtual Machine (visit http://goo.gl/70dvRb)" +msgstr "" + +#: ./doc/training-guides/module001-ch005-vm-provisioning-walk-through.xml:43(para) +msgid "LXC- Linux Containers (through libvirt) (visit http://goo.gl/Ous3ly)" +msgstr "" + +#: ./doc/training-guides/module001-ch005-vm-provisioning-walk-through.xml:48(para) +msgid "QEMU- Quick EMUlator (visit http://goo.gl/WWV9lL)" +msgstr "" + +#: ./doc/training-guides/module001-ch005-vm-provisioning-walk-through.xml:53(para) +msgid "UML- User Mode Linux (visit http://goo.gl/4HAkJj)" +msgstr "" + +#: ./doc/training-guides/module001-ch005-vm-provisioning-walk-through.xml:58(para) +msgid "VMWare vSphere4.1 update 1 and newer (visit http://goo.gl/0DBeo5)" +msgstr "" + +#: ./doc/training-guides/module001-ch005-vm-provisioning-walk-through.xml:63(para) +msgid "Xen- Xen, Citrix XenServer and Xen Cloud Platform (XCP) (visit http://goo.gl/yXP9t1)" +msgstr "" + +#: ./doc/training-guides/module001-ch005-vm-provisioning-walk-through.xml:68(para) +msgid "Bare Metal- Provisions physical hardware via pluggable sub-drivers. (visit http://goo.gl/exfeSg)" +msgstr "" + +#: ./doc/training-guides/module001-ch005-vm-provisioning-walk-through.xml:74(para) +msgid "The OpenStack Compute system is designed to be used by many different cloud computing consumers or customers, basically tenants on a shared system, using role-based access assignments. Roles control the actions that a user is allowed to perform. In the default configuration, most actions do not require a particular role, but this is configurable by the system administrator editing the appropriate policy.json file that maintains the rules. For example, a rule can be defined so that a user cannot allocate a public IP without the admin role. A user's access to particular images is limited by tenant, but the username and password are assigned per user. Key pairs granting access to an instance are enabled per user, but quotas to control resource consumption across available hardware resources are per tenant." +msgstr "" + +#: ./doc/training-guides/module001-ch005-vm-provisioning-walk-through.xml:88(para) +msgid "While the original EC2 API supports users, OpenStack Compute adds the concept of tenants. Tenants are isolated resource containers forming the principal organizational structure within the Compute service. They consist of a separate VLAN, volumes, instances, images, keys, and users. A user can specify which tenant he or she wishes to be known as by appending :project_id to his or her access key. If no tenant is specified in the API request, Compute attempts to use a tenant with the same ID as the user" +msgstr "" + +#: ./doc/training-guides/module001-ch005-vm-provisioning-walk-through.xml:104(para) +msgid "Total size of all volumes within a project as measured in GB" +msgstr "" + +#: ./doc/training-guides/module001-ch005-vm-provisioning-walk-through.xml:108(para) +msgid "Number of instances which may be launched" +msgstr "" + +#: ./doc/training-guides/module001-ch005-vm-provisioning-walk-through.xml:111(para) +msgid "Number of processor cores which may be allocated" +msgstr "" + +#: ./doc/training-guides/module001-ch005-vm-provisioning-walk-through.xml:114(para) +msgid "Floating IP addresses (assigned to any instance when it launches so the instance has the same publicly accessible IP addresses)" +msgstr "" + +#: ./doc/training-guides/module001-ch005-vm-provisioning-walk-through.xml:119(para) +msgid "Fixed IP addresses (assigned to the same instance each time it boots, publicly or privately accessible, typically private for management purposes)" +msgstr "" + +#: ./doc/training-guides/module001-ch005-vm-provisioning-walk-through.xml:124(guilabel) ./doc/training-guides/module001-ch005-vm-provisioning-walk-through.xml:162(guilabel) +msgid "Images and Instances" +msgstr "" + +#: ./doc/training-guides/module001-ch005-vm-provisioning-walk-through.xml:125(para) +msgid "This introduction provides a high level overview of what images and instances are and description of the life-cycle of a typical virtual system within the cloud. There are many ways to configure the details of an OpenStack cloud and many ways to implement a virtual system within that cloud. These configuration details as well as the specific command line utilities and API calls to perform the actions described are presented in the Image Managementand Volume Managementchapters." +msgstr "" + +#: ./doc/training-guides/module001-ch005-vm-provisioning-walk-through.xml:134(para) +msgid "Images are disk images which are templates for virtual machine file systems. The image service, Glance, is responsible for the storage and management of images within OpenStack." +msgstr "" + +#: ./doc/training-guides/module001-ch005-vm-provisioning-walk-through.xml:138(para) +msgid "Instances are the individual virtual machines running on physical compute nodes. The compute service, Nova, manages instances. Any number of instances maybe started from the same image. Each instance is run from a copy of the base image so runtime changes made by an instance do not change the image it is based on. Snapshots of running instances may be taken which create a new image based on the current disk state of a particular instance." +msgstr "" + +#: ./doc/training-guides/module001-ch005-vm-provisioning-walk-through.xml:146(para) +msgid "When starting an instance a set of virtual resources known as a flavor must be selected. Flavors define how many virtual CPUs an instance has and the amount of RAM and size of its ephemeral disks. OpenStack provides a number of predefined flavors which cloud administrators may edit or add to. Users must select from the set of available flavors defined on their cloud." +msgstr "" + +#: ./doc/training-guides/module001-ch005-vm-provisioning-walk-through.xml:153(para) +msgid "Additional resources such as persistent volume storage and public IP address may be added to and removed from running instances. The examples below show the cinder-volume service which provide persistent block storage as opposed to the ephemeral storage provided by the instance flavor." +msgstr "" + +#: ./doc/training-guides/module001-ch005-vm-provisioning-walk-through.xml:158(para) +msgid "Here is an example of the life cycle of a typical virtual system within an OpenStack cloud to illustrate these concepts." +msgstr "" + +#: ./doc/training-guides/module001-ch005-vm-provisioning-walk-through.xml:161(guilabel) ./doc/training-guides/module001-ch005-vm-provisioning-walk-through.xml:172(title) +msgid "Initial State" +msgstr "" + +#: ./doc/training-guides/module001-ch005-vm-provisioning-walk-through.xml:163(para) +msgid "The following diagram shows the system state prior to launching an instance. The image store fronted by the image service, Glance, has some number of predefined images. In the cloud there is an available compute node with available vCPU, memory and local disk resources. Plus there are a number of predefined volumes in the cinder-volume service." +msgstr "" + +#: ./doc/training-guides/module001-ch005-vm-provisioning-walk-through.xml:169(para) +msgid "Figure 2.1. Base image state with no running instances" +msgstr "" + +#: ./doc/training-guides/module001-ch005-vm-provisioning-walk-through.xml:179(guilabel) +msgid "Launching an instance" +msgstr "" + +#: ./doc/training-guides/module001-ch005-vm-provisioning-walk-through.xml:180(para) +msgid "To launch an instance the user selects an image, a flavor and optionally other attributes. In this case the selected flavor provides a root volume (as all flavors do) labeled vda in the diagram and additional ephemeral storage labeled vdb in the diagram. The user has also opted to map a volume from the cinder-volume store to the third virtual disk, vdc, on this instance." +msgstr "" + +#: ./doc/training-guides/module001-ch005-vm-provisioning-walk-through.xml:187(para) +msgid "Figure 2.2. Instance creation from image and run time state" +msgstr "" + +#: ./doc/training-guides/module001-ch005-vm-provisioning-walk-through.xml:190(title) +msgid "Launch VM Instance" +msgstr "" + +#: ./doc/training-guides/module001-ch005-vm-provisioning-walk-through.xml:197(para) +msgid "The OpenStack system copies the base image from the image store to local disk which is used as the first disk of the instance (vda). Having small images will result in faster start up of your instances as less data needs to be copied across the network. The system also creates a new empty disk image to present as the second disk (vdb). Be aware that the second disk is an empty disk with an emphemeral life as it is destroyed when you delete the instance. The compute node attaches to the requested cinder-volume using iSCSI and maps this to the third disk (vdc) as requested. The vCPU and memory resources are provisioned and the instance is booted from the first drive. The instance runs and changes data on the disks indicated in red in the diagram." +msgstr "" + +#: ./doc/training-guides/module001-ch005-vm-provisioning-walk-through.xml:210(para) +msgid "There are many possible variations in the details of the scenario, particularly in terms of what the backing storage is and the network protocols used to attach and move storage. One variant worth mentioning here is that the ephemeral storage used for volumes vda and vdb in this example may be backed by network storage rather than local disk. The details are left for later chapters." +msgstr "" + +#: ./doc/training-guides/module001-ch005-vm-provisioning-walk-through.xml:217(guilabel) ./doc/training-guides/module001-ch005-vm-provisioning-walk-through.xml:226(title) +msgid "End State" +msgstr "" + +#: ./doc/training-guides/module001-ch005-vm-provisioning-walk-through.xml:218(para) +msgid "Once the instance has served its purpose and is deleted all state is reclaimed, except the persistent volume. The ephemeral storage is purged. Memory and vCPU resources are released. And of course the image has remained unchanged throughout." +msgstr "" + +#: ./doc/training-guides/module001-ch005-vm-provisioning-walk-through.xml:223(para) +msgid "Figure 2.3. End state of image and volume after instance exits" +msgstr "" + +#: ./doc/training-guides/module001-ch005-vm-provisioning-walk-through.xml:233(para) +msgid "Once you launch a VM in OpenStack, there's something more going on in the background. To understand what's happening behind the Dashboard, lets take a deeper dive into OpenStack’s VM provisioning. For launching a VM, you can either use Command Line Interface or the OpenStack Horizon Dashboard." +msgstr "" + +#: ./doc/training-guides/operator-editing-code.xml:7(title) +msgid "Editing Code" +msgstr "" + +#: ./doc/training-guides/operator-editing-code.xml:9(title) +msgid "Get Tools and Accounts" +msgstr "" + +#: ./doc/training-guides/operator-editing-code.xml:13(para) +msgid "First create a GitHub account at github.com." +msgstr "" + +#: ./doc/training-guides/operator-editing-code.xml:16(para) +msgid "Check out https://wiki.openstack.org/wiki/Documentation/HowTo for more extentsive setup instructions" +msgstr "" + +#: ./doc/training-guides/operator-editing-code.xml:18(para) +msgid "Download and install Git from http://git-scm.com/downloads" +msgstr "" + +#: ./doc/training-guides/operator-editing-code.xml:22(para) +msgid "Create your local repository directory" +msgstr "" + +#: ./doc/training-guides/operator-editing-code.xml:26(title) +msgid "Install SourceTree" +msgstr "" + +#: ./doc/training-guides/operator-editing-code.xml:29(link) +msgid "http://www.sourcetreeapp.com/download/" +msgstr "" + +#: ./doc/training-guides/operator-editing-code.xml:32(para) +msgid "Ignore the Atlassian Bitbucket and Stack setup" +msgstr "" + +#: ./doc/training-guides/operator-editing-code.xml:36(para) +msgid "Add your GitHub username and password" +msgstr "" + +#: ./doc/training-guides/operator-editing-code.xml:39(para) +msgid "Set your local repository location" +msgstr "" + +#: ./doc/training-guides/operator-editing-code.xml:44(title) +msgid "Install an XML editor" +msgstr "" + +#: ./doc/training-guides/operator-editing-code.xml:47(para) +msgid "You can download a 30 day trial of Oxygen. The floating licenses donated by OxygenXML have all been handed out.http://www.oxygenxml.com/download_oxygenxml_editor.html" +msgstr "" + +#: ./doc/training-guides/operator-editing-code.xml:51(para) +msgid "AND/OR PyCharm http://download.jetbrains.com/python/pycharm-community-3.0.1.dmg" +msgstr "" + +#: ./doc/training-guides/operator-editing-code.xml:54(para) +msgid "AND/OR You can use emacs or vi editors." +msgstr "" + +#: ./doc/training-guides/operator-editing-code.xml:55(para) +msgid "Here are some great resources on DocBook and Emacs' NXML mode:" +msgstr "" + +#: ./doc/training-guides/operator-editing-code.xml:56(link) +msgid "http://paul.frields.org/2011/02/09/xml-editing-with-emacs/" +msgstr "" + +#: ./doc/training-guides/operator-editing-code.xml:57(link) +msgid "https://fedoraproject.org/wiki/How_to_use_Emacs_for_XML_editing" +msgstr "" + +#: ./doc/training-guides/operator-editing-code.xml:58(link) +msgid "http://infohost.nmt.edu/tcc/help/pubs/nxml/" +msgstr "" + +#: ./doc/training-guides/operator-editing-code.xml:59(para) +msgid "If you prefer vi, there are ways to make DocBook editing easier:" +msgstr "" + +#: ./doc/training-guides/operator-editing-code.xml:60(link) +msgid "https://fedoraproject.org/wiki/Editing_DocBook_with_Vi" +msgstr "" + +#: ./doc/training-guides/operator-editing-code.xml:65(title) +msgid "Install Maven" +msgstr "" + +#: ./doc/training-guides/operator-editing-code.xml:71(para) +msgid "Copy the latest stable binary fromhttp://maven.apache.org/download.cgi into /usr/local/apache-maven" +msgstr "" + +#: ./doc/training-guides/operator-editing-code.xml:77(para) +msgid "Install maven with " +msgstr "" + +#: ./doc/training-guides/operator-editing-code.xml:81(para) +msgid "Add the maven path" +msgstr "" + +#: ./doc/training-guides/operator-editing-code.xml:87(para) +msgid "Set your maven user profile settings" +msgstr "" + +#: ./doc/training-guides/operator-editing-code.xml:91(para) +msgid "verify maven is setup with" +msgstr "" + +#: ./doc/training-guides/operator-editing-code.xml:98(para) +msgid "Create a Launchpad account: Visit https://login.launchpad.net/+new_accountAfter you create this account, the follow-up page is slightly confusing. It doesn't tell you that you are done. (It gives you the opportunity to change your -password, but you do not have to.)" +msgstr "" + +#: ./doc/training-guides/operator-editing-code.xml:107(para) +msgid "Add at least one SSH key to your account profile. To do this, follow the instructions on https://help.launchpad.net/YourAccount/CreatingAnSSHKeyPair\"." +msgstr "" + +#: ./doc/training-guides/operator-editing-code.xml:113(para) +msgid "Join The OpenStack Foundation: Visit https://www.openstack.org/join. Among other privileges, this also allows you to vote in elections and run for elected positions within The OpenStack Project. When signing up for the Foundation Membership, make sure to give the same E-mail address you'll use for code contributions, since the Primary Email Address in you Foundation Profile will need to match the Preferred Email you set later in your Gerrit contact information." +msgstr "" + +#: ./doc/training-guides/operator-editing-code.xml:123(para) +msgid "the CLA: Every developer and contributor needs to sign the Individual Contributor License agreement. Visit https:// review.openstack.org/ and click the Sign In link at the top-right corner of the page. Log in with your Launchpad ID. You can preview the text of the Individual CLA." +msgstr "" + +#: ./doc/training-guides/operator-editing-code.xml:132(para) +msgid "Add your SSH keys to your GitHub account profile (same one as used in Launchpad, they must match). When you copy and paste the SSH key, include the ssh-rsa algorithm and computer identifier. If this is your first time setting up git and Github, be sure to run these steps in a Terminal window:" +msgstr "" + +#: ./doc/training-guides/operator-editing-code.xml:141(para) +msgid "Install git-review. If pip is not already installed, use \"sudo easy_install pip\" to install it on a Mac or Ubuntu" +msgstr "" + +#: ./doc/training-guides/operator-editing-code.xml:147(para) +msgid "Change to the directory" +msgstr "" + +#: ./doc/training-guides/operator-editing-code.xml:151(para) +msgid "Clone the openstack-manuals repository with" +msgstr "" + +#: ./doc/training-guides/operator-editing-code.xml:154(para) +msgid "Change directory to the pulled repository" +msgstr "" + +#: ./doc/training-guides/operator-editing-code.xml:158(para) +msgid "Enter your Launchpad account information after testing for ssh key setup with" +msgstr "" + +#: ./doc/training-guides/operator-editing-code.xml:166(title) ./doc/training-guides/bk002-ch002-operator-getting-started-lab.xml:19(title) +msgid "Fix a Documentation Bug" +msgstr "" + +#: ./doc/training-guides/operator-editing-code.xml:170(para) +msgid "Note: For this example, we are going to assume bug 1188522 and change 33713" +msgstr "" + +#: ./doc/training-guides/operator-editing-code.xml:174(para) +msgid "Bring uphttps://bugs.launchpad.net/openstack-manuals" +msgstr "" + +#: ./doc/training-guides/operator-editing-code.xml:179(para) +msgid "Select a bug that is unassigned and that you can fix. Syntax errors are the best ones to start off with." +msgstr "" + +#: ./doc/training-guides/operator-editing-code.xml:183(para) +msgid "Using oXygen, open the /Users/<username>/code/openstack-manuals/doc/admin-guide-cloud/bk-admin-guide-cloud.xml master page for this example. It links together the rest of the material. Find the page with the bug. Open the page that is referenced in the bug description by selecting the content in the author view. Verify you have the correct page by visually inspecting the html page and the xml page." +msgstr "" + +#: ./doc/training-guides/operator-editing-code.xml:193(para) +msgid "In the shell," +msgstr "" + +#: ./doc/training-guides/operator-editing-code.xml:197(para) +msgid "Verify that you are on master with" +msgstr "" + +#: ./doc/training-guides/operator-editing-code.xml:201(para) +msgid "Create your working branch off master with" +msgstr "" + +#: ./doc/training-guides/operator-editing-code.xml:205(para) +msgid "Verify that you have the branch open through SourceTree" +msgstr "" + +#: ./doc/training-guides/operator-editing-code.xml:209(para) +msgid "Correct the bug through oXygen. Toggle back and forth through the different views at the bottom of the editor." +msgstr "" + +#: ./doc/training-guides/operator-editing-code.xml:214(para) +msgid "Once the bug is fixed, verify that the documentation can be built without errors by running" +msgstr "" + +#: ./doc/training-guides/operator-editing-code.xml:219(para) +msgid "Verify that the HTML page reflects your changes properly. You can open the file from the command line by using the \"open\" command" +msgstr "" + +#: ./doc/training-guides/operator-editing-code.xml:223(para) +msgid "Add the changes" +msgstr "" + +#: ./doc/training-guides/operator-editing-code.xml:227(para) +msgid "Commit the changes" +msgstr "" + +#: ./doc/training-guides/operator-editing-code.xml:232(para) +msgid "Submit the bug fix to Gerrit" +msgstr "" + +#: ./doc/training-guides/operator-editing-code.xml:236(para) +msgid "Track the Gerrit review process athttps://review.openstack.org/#/c/33713. Follow and respond inline to the Code Review requests and comments." +msgstr "" + +#: ./doc/training-guides/operator-editing-code.xml:243(para) +msgid "Your change will be tested, track the Jenkins testing process at https://jenkins.openstack.org" +msgstr "" + +#: ./doc/training-guides/operator-editing-code.xml:247(para) +msgid "If your change is rejected, complete the following steps:" +msgstr "" + +#: ./doc/training-guides/operator-editing-code.xml:250(para) +msgid "Respond to the inline comments if any" +msgstr "" + +#: ./doc/training-guides/operator-editing-code.xml:253(para) +msgid "Update the status to work in progress" +msgstr "" + +#: ./doc/training-guides/operator-editing-code.xml:256(para) +msgid "Checkout the patch from the Gerrit change review" +msgstr "" + +#: ./doc/training-guides/operator-editing-code.xml:260(para) +msgid "Follow the recommended tweaks to the files" +msgstr "" + +#: ./doc/training-guides/operator-editing-code.xml:263(para) +msgid "Rerun" +msgstr "" + +#: ./doc/training-guides/operator-editing-code.xml:267(para) +msgid "add your additional changes to the change log" +msgstr "" + +#: ./doc/training-guides/operator-editing-code.xml:271(para) +msgid "Final commit" +msgstr "" + +#: ./doc/training-guides/operator-editing-code.xml:275(para) +msgid "Update the Jenkins status to change completed" +msgstr "" + +#: ./doc/training-guides/operator-editing-code.xml:280(para) +msgid "Follow the jenkins build progress at https://jenkins.openstack.org/view/Openstack-manuals/. Note if the build process fails, the online documentation will not reflect your bug fix." +msgstr "" + +#: ./doc/training-guides/operator-editing-code.xml:289(title) +msgid "Submit a Documentation Bug Fix" +msgstr "" + +#: ./doc/training-guides/operator-editing-code.xml:293(para) +msgid "Bring up https://bugs.launchpad.net/openstack-manuals/+filebug" +msgstr "" + +#: ./doc/training-guides/operator-editing-code.xml:298(para) +msgid "Give your bug a descriptive name" +msgstr "" + +#: ./doc/training-guides/operator-editing-code.xml:301(para) +msgid "verify if asked that it is not a duplicate" +msgstr "" + +#: ./doc/training-guides/operator-editing-code.xml:304(para) +msgid "Add some more detail into the description field" +msgstr "" + +#: ./doc/training-guides/operator-editing-code.xml:307(para) +msgid "Once submitted, select the assigned to pane and select \"assign to me\" or \"sarob\"" +msgstr "" + +#: ./doc/training-guides/operator-editing-code.xml:311(para) +msgid "Follow the instructions for fixing a bug in the Fix a Documentation Bug section." +msgstr "" + +#: ./doc/training-guides/operator-editing-code.xml:318(title) ./doc/training-guides/bk002-ch002-operator-getting-started-lab.xml:33(title) +msgid "Create a Branch" +msgstr "" + +#: ./doc/training-guides/operator-editing-code.xml:320(para) +msgid "This section is using the submission of this training material as the example" +msgstr "" + +#: ./doc/training-guides/operator-editing-code.xml:323(para) +msgid "Create a bp/training-manuals branch" +msgstr "" + +#: ./doc/training-guides/operator-editing-code.xml:327(para) +msgid "From the openstack-manuals repository, use the template user-story-includes-template.xml as the starting point for your user story. bk001-ch003-associate-general.xml has at least one other included user story that you can use for additional help." +msgstr "" + +#: ./doc/training-guides/operator-editing-code.xml:333(para) +msgid "Include the user story xml file into the bk001-ch003-associate-general.xml file. Follow the syntax of the existing xi:include statements." +msgstr "" + +#: ./doc/training-guides/operator-editing-code.xml:338(para) +msgid "When your editing is completed. Double check Oxygen doesn't have any errors you are not expecting." +msgstr "" + +#: ./doc/training-guides/operator-editing-code.xml:342(para) +msgid "Run maven locally to verify the build will run without errors " +msgstr "" + +#: ./doc/training-guides/operator-editing-code.xml:346(para) +msgid "Add your changes into git" +msgstr "" + +#: ./doc/training-guides/operator-editing-code.xml:349(para) +msgid "Commit the changes with good syntax. After entering the commit command, VI syntax applies. Use \"i\" to insert and Esc to break out. \":wq\" to write and quit." +msgstr "" + +#: ./doc/training-guides/operator-editing-code.xml:358(para) +msgid "Submit your patch for review" +msgstr "" + +#: ./doc/training-guides/operator-editing-code.xml:361(para) +msgid "One last step. Go to the review page listed after you submitted your review and add the training core team as reviewers; Sean Roberts and Colin McNamara." +msgstr "" + +#: ./doc/training-guides/operator-editing-code.xml:365(para) +msgid "More details on branching can be found here under Gerrit Workflow and the Git docs" +msgstr "" + +#: ./doc/training-guides/operator-editing-code.xml:373(title) +msgid "Add Content to the Training Manuals" +msgstr "" + +#: ./doc/training-guides/operator-editing-code.xml:376(para) +msgid "Getting Accounts and Tools: We can't do this without operators and developers using and creating the content. Anyone can contribute content. You will need the tools to get started. Go to the Getting Tools and Accounts page." +msgstr "" + +#: ./doc/training-guides/operator-editing-code.xml:382(para) +msgid "Pick a Card: Once you have your tools ready to go, you can assign some work to yourself. Go to the Training Trello/KanBan storyboard and assign a card / user story from the Sprint Backlog to yourself. If you don't have a Trello account, no problem, just create one. Email seanrob@yahoo-inc.com and you will have access. Move the card from the Sprint Backlog to Doing." +msgstr "" + +#: ./doc/training-guides/operator-editing-code.xml:391(para) +msgid "Create the Content: Each card / user story from the KanBan story board will be a separate chunk of content you will add to the openstack-manuals repository openstack-training sub-project." +msgstr "" + +#: ./doc/training-guides/operator-editing-code.xml:396(para) +msgid "Open the file st-training-guides.xml with your XML editor. All the content starts with the set file st-training-guides.xml. The XML structure follows the hierarchy Set -> Book -> Chapter -> Section. The st-training-guides.xml file holds the set level. Notice the set file uses xi:include statements to include the books. We want to open the associate book. Open the associate book and you will see the chapter include statements. These are the chapters that make up the Associate Training Guide book." +msgstr "" + +#: ./doc/training-guides/operator-editing-code.xml:407(para) +msgid "Create a branch using the card number as associate-card-XXX where XXX is the card number. Review Creating a Branch again for instructions on how to complete the branch merge." +msgstr "" + +#: ./doc/training-guides/operator-editing-code.xml:415(para) +msgid "Copy the user-story-includes-template.xml to associate-card-XXX.xml." +msgstr "" + +#: ./doc/training-guides/operator-editing-code.xml:420(para) +msgid "Open the bk001-ch003-asssociate-general.xml file and add <xi:include href=\"associate-card-XXX.xml\">" +msgstr "" + +#: ./doc/training-guides/operator-editing-code.xml:426(para) +msgid "Side by side, open associate-card-XXX.xml with your XML editor and open the ubuntu 12.04 install guide with your HTML browser." +msgstr "" + +#: ./doc/training-guides/operator-editing-code.xml:431(para) +msgid "Find the HTML content to include. Find the XML file that matches the HTML. Include the whole page using a simple href like <xi:include href=\"associate-card-XXX.xml\"> or include a section using xpath like <xi:include href=\"../basic-install/src/basic-install_controller-common.xml\" xpointer=\"xmlns(db=http://docbook.org/ns/docbook) xpath(//*[@xml:id = 'controller-os'])\"> . Review the user-story-includes-template.xml file for the whole syntax." +msgstr "" + +#: ./doc/training-guides/operator-editing-code.xml:442(para) +msgid "Copy in other content sources like the Aptira content, your own text describing what needs to be learned with the section, diagrams, and quizzes. If you include content from another source like Aptira cocntent make extra paragraph referencing the file and/or HTTP address the content came from." +msgstr "" + +#: ./doc/training-guides/operator-editing-code.xml:449(para) +msgid "Verify the code is good by runnning mvn clean generate-sources and by reviewing the local HTML in file:///Users/(localUser)/code/openstack-manuals/doc/training-guide/target/docbkx/webhelp/local/training-guide/content/" +msgstr "" + +#: ./doc/training-guides/operator-editing-code.xml:455(para) +msgid "Merge the branch" +msgstr "" + +#: ./doc/training-guides/operator-editing-code.xml:458(para) +msgid "Move the card from Doing to Done" +msgstr "" + +#: ./doc/training-guides/card025.xml:6(title) +msgid "Role of the Controller Node" +msgstr "" + +#. When image changes, this message will be marked fuzzy or untranslated for you. +#. It doesn't matter what you translate it to: it's not used at all. +#: ./doc/training-guides/module001-ch008-queues-messaging.xml:11(None) +msgid "@@image: 'figures/image04.png'; md5=dd0c42b457e2b17fd94e4f62c16b9c37" +msgstr "" + +#. When image changes, this message will be marked fuzzy or untranslated for you. +#. It doesn't matter what you translate it to: it's not used at all. +#: ./doc/training-guides/module001-ch008-queues-messaging.xml:47(None) +msgid "@@image: 'figures/image24.png'; md5=aea2956c5e4f01e06171d8d5e1de49b5" +msgstr "" + +#. When image changes, this message will be marked fuzzy or untranslated for you. +#. It doesn't matter what you translate it to: it's not used at all. +#: ./doc/training-guides/module001-ch008-queues-messaging.xml:149(None) ./doc/training-guides/module001-ch008-queues-messaging.xml:207(None) +msgid "@@image: 'figures/image20.png'; md5=c2cab17b6ee560943403c1d998d7a9d7" +msgstr "" + +#. When image changes, this message will be marked fuzzy or untranslated for you. +#. It doesn't matter what you translate it to: it's not used at all. +#: ./doc/training-guides/module001-ch008-queues-messaging.xml:184(None) +msgid "@@image: 'figures/image28.png'; md5=c813069a23d72a7a3f519d896270a62a" +msgstr "" + +#: ./doc/training-guides/module001-ch008-queues-messaging.xml:6(title) ./doc/training-guides/bk001-ch003-associate-controller-node.xml:28(title) +msgid "OpenStack Messaging and Queues" +msgstr "" + +#: ./doc/training-guides/module001-ch008-queues-messaging.xml:8(title) +msgid "Messaging in OpenStack" +msgstr "" + +#: ./doc/training-guides/module001-ch008-queues-messaging.xml:15(para) +msgid "AMQP is the messaging technology chosen by the OpenStack cloud. The AMQP broker, either RabbitMQ or Qpid, sits between any two Nova components and allows them to communicate in a loosely coupled fashion. More precisely, Nova components (the compute fabric of OpenStack) use Remote Procedure Calls (RPC hereinafter) to communicate to one another; however such a paradigm is built atop the publish/subscribe paradigm so that the following benefits can be achieved:" +msgstr "" + +#: ./doc/training-guides/module001-ch008-queues-messaging.xml:25(para) +msgid "Decoupling between client and servant (such as the client does not need to know where the servant reference is)." +msgstr "" + +#: ./doc/training-guides/module001-ch008-queues-messaging.xml:30(para) +msgid "Full a-synchronism between client and servant (such as the client does not need the servant to run at the same time of the remote call)." +msgstr "" + +#: ./doc/training-guides/module001-ch008-queues-messaging.xml:35(para) +msgid "Random balancing of remote calls (such as if more servants are up and running, one-way calls are transparently dispatched to the first available servant)." +msgstr "" + +#: ./doc/training-guides/module001-ch008-queues-messaging.xml:40(para) +msgid "Nova uses direct, fanout, and topic-based exchanges. The architecture looks like the one depicted in the figure below:" +msgstr "" + +#: ./doc/training-guides/module001-ch008-queues-messaging.xml:44(title) +msgid "AMQP" +msgstr "" + +#: ./doc/training-guides/module001-ch008-queues-messaging.xml:51(para) +msgid "Nova implements RPC (both request+response, and one-way, respectively nicknamed ‘rpc.call’ and ‘rpc.cast’) over AMQP by providing an adapter class which take cares of marshaling and un-marshalling of messages into function calls. Each Nova service, such as Compute, Scheduler, and so on, creates two queues at the initialization time, one which accepts messages with routing keys ‘NODE-TYPE.NODE-ID’, for example, compute.hostname, and another, which accepts messages with routing keys as generic ‘NODE-TYPE’, for example compute. The former is used specifically when Nova-API needs to redirect commands to a specific node like ‘euca-terminate instance’. In this case, only the compute node whose host’s hypervisor is running the virtual machine can kill the instance. The API acts as a consumer when RPC calls are request/response, otherwise is acts as publisher only." +msgstr "" + +#: ./doc/training-guides/module001-ch008-queues-messaging.xml:64(guilabel) +msgid "Nova RPC Mappings" +msgstr "" + +#: ./doc/training-guides/module001-ch008-queues-messaging.xml:65(para) +msgid "The figure below shows the internals of a message broker node (referred to as a RabbitMQ node in the diagrams) when a single instance is deployed and shared in an OpenStack cloud. Every Nova component connects to the message broker and, depending on its personality, such as a compute node or a network node, may use the queue either as an Invoker (such as API or Scheduler) or a Worker (such as Compute or Network). Invokers and Workers do not actually exist in the Nova object model, but we are going to use them as an abstraction for sake of clarity. An Invoker is a component that sends messages in the queuing system via two operations: 1) rpc.call and ii) rpc.cast; a Worker is a component that receives messages from the queuing system and reply accordingly to rcp.call operations." +msgstr "" + +#: ./doc/training-guides/module001-ch008-queues-messaging.xml:78(para) +msgid "Figure 2 shows the following internal elements:" +msgstr "" + +#: ./doc/training-guides/module001-ch008-queues-messaging.xml:81(para) +msgid "Topic Publisher:a Topic Publisher comes to life when an rpc.call or an rpc.cast operation is executed; this object is instantiated and used to push a message to the queuing system. Every publisher connects always to the same topic-based exchange; its life-cycle is limited to the message delivery." +msgstr "" + +#: ./doc/training-guides/module001-ch008-queues-messaging.xml:89(para) +msgid "Direct Consumer:a Direct Consumer comes to life if (an only if) a rpc.call operation is executed; this object is instantiated and used to receive a response message from the queuing system; Every consumer connects to a unique direct-based exchange via a unique exclusive queue; its life-cycle is limited to the message delivery; the exchange and queue identifiers are determined by a UUID generator, and are marshaled in the message sent by the Topic Publisher (only rpc.call operations)." +msgstr "" + +#: ./doc/training-guides/module001-ch008-queues-messaging.xml:100(para) +msgid "Topic Consumer:a Topic Consumer comes to life as soon as a Worker is instantiated and exists throughout its life-cycle; this object is used to receive messages from the queue and it invokes the appropriate action as defined by the Worker role. A Topic Consumer connects to the same topic-based exchange either via a shared queue or via a unique exclusive queue. Every Worker has two topic consumers, one that is addressed only during rpc.cast operations (and it connects to a shared queue whose exchange key is ‘topic’) and the other that is addressed only during rpc.call operations (and it connects to a unique queue whose exchange key is ‘topic.host’)." +msgstr "" + +#: ./doc/training-guides/module001-ch008-queues-messaging.xml:114(para) +msgid "Direct Publisher:a Direct Publisher comes to life only during rpc.call operations and it is instantiated to return the message required by the request/response operation. The object connects to a direct-based exchange whose identity is dictated by the incoming message." +msgstr "" + +#: ./doc/training-guides/module001-ch008-queues-messaging.xml:122(para) +msgid "Topic Exchange:The Exchange is a routing table that exists in the context of a virtual host (the multi-tenancy mechanism provided by Qpid or RabbitMQ); its type (such as topic vs. direct) determines the routing policy; a message broker node will have only one topic-based exchange for every topic in Nova." +msgstr "" + +#: ./doc/training-guides/module001-ch008-queues-messaging.xml:130(para) +msgid "Direct Exchange:this is a routing table that is created during rpc.call operations; there are many instances of this kind of exchange throughout the life-cycle of a message broker node, one for each rpc.call invoked." +msgstr "" + +#: ./doc/training-guides/module001-ch008-queues-messaging.xml:137(para) +msgid "Queue Element:A Queue is a message bucket. Messages are kept in the queue until a Consumer (either Topic or Direct Consumer) connects to the queue and fetch it. Queues can be shared or can be exclusive. Queues whose routing key is ‘topic’ are shared amongst Workers of the same personality." +msgstr "" + +#: ./doc/training-guides/module001-ch008-queues-messaging.xml:146(title) ./doc/training-guides/module001-ch008-queues-messaging.xml:181(title) ./doc/training-guides/module001-ch008-queues-messaging.xml:204(title) ./doc/training-guides/bk001-ch004-associate-controller-node-quiz.xml:278(para) ./doc/training-guides/lab001-control-node.xml:125(emphasis) +msgid "RabbitMQ" +msgstr "" + +#: ./doc/training-guides/module001-ch008-queues-messaging.xml:153(guilabel) +msgid "RPC Calls" +msgstr "" + +#: ./doc/training-guides/module001-ch008-queues-messaging.xml:154(para) +msgid "The diagram below shows the message flow during an rp.call operation:" +msgstr "" + +#: ./doc/training-guides/module001-ch008-queues-messaging.xml:158(para) +msgid "a Topic Publisher is instantiated to send the message request to the queuing system; immediately before the publishing operation, a Direct Consumer is instantiated to wait for the response message." +msgstr "" + +#: ./doc/training-guides/module001-ch008-queues-messaging.xml:164(para) +msgid "once the message is dispatched by the exchange, it is fetched by the Topic Consumer dictated by the routing key (such as ‘topic.host’) and passed to the Worker in charge of the task." +msgstr "" + +#: ./doc/training-guides/module001-ch008-queues-messaging.xml:170(para) +msgid "once the task is completed, a Direct Publisher is allocated to send the response message to the queuing system." +msgstr "" + +#: ./doc/training-guides/module001-ch008-queues-messaging.xml:175(para) +msgid "once the message is dispatched by the exchange, it is fetched by the Direct Consumer dictated by the routing key (such as ‘msg_id’) and passed to the Invoker." +msgstr "" + +#: ./doc/training-guides/module001-ch008-queues-messaging.xml:188(guilabel) +msgid "RPC Casts" +msgstr "" + +#: ./doc/training-guides/module001-ch008-queues-messaging.xml:189(para) +msgid "The diagram below the message flow during an rp.cast operation:" +msgstr "" + +#: ./doc/training-guides/module001-ch008-queues-messaging.xml:193(para) +msgid "A Topic Publisher is instantiated to send the message request to the queuing system." +msgstr "" + +#: ./doc/training-guides/module001-ch008-queues-messaging.xml:197(para) +msgid "Once the message is dispatched by the exchange, it is fetched by the Topic Consumer dictated by the routing key (such as ‘topic’) and passed to the Worker in charge of the task." +msgstr "" + +#: ./doc/training-guides/module001-ch008-queues-messaging.xml:211(guilabel) +msgid "AMQP Broker Load" +msgstr "" + +#: ./doc/training-guides/module001-ch008-queues-messaging.xml:212(para) +msgid "At any given time the load of a message broker node running either Qpid or RabbitMQ is function of the following parameters:" +msgstr "" + +#: ./doc/training-guides/module001-ch008-queues-messaging.xml:217(para) +msgid "Throughput of API calls: the number of API calls (more precisely rpc.call ops) being served by the OpenStack cloud dictates the number of direct-based exchanges, related queues and direct consumers connected to them." +msgstr "" + +#: ./doc/training-guides/module001-ch008-queues-messaging.xml:223(para) +msgid "Number of Workers: there is one queue shared amongst workers with the same personality; however there are as many exclusive queues as the number of workers; the number of workers dictates also the number of routing keys within the topic-based exchange, which is shared amongst all workers." +msgstr "" + +#: ./doc/training-guides/module001-ch008-queues-messaging.xml:231(para) +msgid "The figure below shows the status of a RabbitMQ node after Nova components’ bootstrap in a test environment. Exchanges and queues being created by Nova components are:" +msgstr "" + +#: ./doc/training-guides/module001-ch008-queues-messaging.xml:236(para) +msgid "Exchanges" +msgstr "" + +#: ./doc/training-guides/module001-ch008-queues-messaging.xml:241(para) +msgid "nova (topic exchange)" +msgstr "" + +#: ./doc/training-guides/module001-ch008-queues-messaging.xml:246(para) +msgid "Queues" +msgstr "" + +#: ./doc/training-guides/module001-ch008-queues-messaging.xml:251(para) +msgid "compute.phantom (phantom is hostname)" +msgstr "" + +#: ./doc/training-guides/module001-ch008-queues-messaging.xml:254(para) +msgid "compute" +msgstr "" + +#: ./doc/training-guides/module001-ch008-queues-messaging.xml:257(para) +msgid "network.phantom (phantom is hostname)" +msgstr "" + +#: ./doc/training-guides/module001-ch008-queues-messaging.xml:260(para) +msgid "network" +msgstr "" + +#: ./doc/training-guides/module001-ch008-queues-messaging.xml:263(para) +msgid "scheduler.phantom (phantom is hostname)" +msgstr "" + +#: ./doc/training-guides/module001-ch008-queues-messaging.xml:266(para) +msgid "scheduler" +msgstr "" + +#: ./doc/training-guides/module001-ch008-queues-messaging.xml:269(guilabel) +msgid "RabbitMQ Gotchas" +msgstr "" + +#: ./doc/training-guides/module001-ch008-queues-messaging.xml:270(para) +msgid "Nova uses Kombu to connect to the RabbitMQ environment. Kombu is a Python library that in turn uses AMQPLib, a library that implements the standard AMQP 0.8 at the time of writing. When using Kombu, Invokers and Workers need the following parameters in order to instantiate a Connection object that connects to the RabbitMQ server (please note that most of the following material can be also found in the Kombu documentation; it has been summarized and revised here for sake of clarity):" +msgstr "" + +#: ./doc/training-guides/module001-ch008-queues-messaging.xml:280(para) +msgid "Hostname: The hostname to the AMQP server." +msgstr "" + +#: ./doc/training-guides/module001-ch008-queues-messaging.xml:284(para) +msgid "Userid: A valid username used to authenticate to the server." +msgstr "" + +#: ./doc/training-guides/module001-ch008-queues-messaging.xml:288(para) +msgid "Password: The password used to authenticate to the server." +msgstr "" + +#: ./doc/training-guides/module001-ch008-queues-messaging.xml:292(para) +msgid "Virtual_host: The name of the virtual host to work with. This virtual host must exist on the server, and the user must have access to it. Default is “/”." +msgstr "" + +#: ./doc/training-guides/module001-ch008-queues-messaging.xml:298(para) +msgid "Port: The port of the AMQP server. Default is 5672 (amqp)." +msgstr "" + +#: ./doc/training-guides/module001-ch008-queues-messaging.xml:302(para) +msgid "The following parameters are default:" +msgstr "" + +#: ./doc/training-guides/module001-ch008-queues-messaging.xml:305(para) +msgid "Insist: insist on connecting to a server. In a configuration with multiple load-sharing servers, the Insist option tells the server that the client is insisting on a connection to the specified server. Default is False." +msgstr "" + +#: ./doc/training-guides/module001-ch008-queues-messaging.xml:312(para) +msgid "Connect_timeout: the timeout in seconds before the client gives up connecting to the server. The default is no timeout." +msgstr "" + +#: ./doc/training-guides/module001-ch008-queues-messaging.xml:317(para) +msgid "SSL: use SSL to connect to the server. The default is False." +msgstr "" + +#: ./doc/training-guides/module001-ch008-queues-messaging.xml:321(para) +msgid "More precisely Consumers need the following parameters:" +msgstr "" + +#: ./doc/training-guides/module001-ch008-queues-messaging.xml:324(para) +msgid "Connection: the above mentioned Connection object." +msgstr "" + +#: ./doc/training-guides/module001-ch008-queues-messaging.xml:328(para) +msgid "Queue:name of the queue." +msgstr "" + +#: ./doc/training-guides/module001-ch008-queues-messaging.xml:332(para) +msgid "Exchange:name of the exchange the queue binds to." +msgstr "" + +#: ./doc/training-guides/module001-ch008-queues-messaging.xml:336(para) +msgid "Routing_key:the interpretation of the routing key depends on the value of the exchange_type attribute." +msgstr "" + +#: ./doc/training-guides/module001-ch008-queues-messaging.xml:343(para) +msgid "Direct exchange:if the routing key property of the message and the routing_key attribute of the queue are identical, then the message is forwarded to the queue." +msgstr "" + +#: ./doc/training-guides/module001-ch008-queues-messaging.xml:349(para) +msgid "Fanout exchange:messages are forwarded to the queues bound the exchange, even if the binding does not have a key." +msgstr "" + +#: ./doc/training-guides/module001-ch008-queues-messaging.xml:354(para) +msgid "Topic exchange:if the routing key property of the message matches the routing key of the key according to a primitive pattern matching scheme, then the message is forwarded to the queue. The message routing key then consists of words separated by dots (”.”, like domain names), and two special characters are available; star (“”) and hash (“#”). The star matches any word, and the hash matches zero or more words. For example ”.stock.#” matches the routing keys “usd.stock” and “eur.stock.db” but not “stock.nasdaq”." +msgstr "" + +#: ./doc/training-guides/module001-ch008-queues-messaging.xml:368(para) +msgid "Durable:this flag determines the durability of both exchanges and queues; durable exchanges and queues remain active when a RabbitMQ server restarts. Non-durable exchanges/queues (transient exchanges/queues) are purged when a server restarts. It is worth noting that AMQP specifies that durable queues cannot bind to transient exchanges. Default is True." +msgstr "" + +#: ./doc/training-guides/module001-ch008-queues-messaging.xml:377(para) +msgid "Auto_delete:if set, the exchange is deleted when all queues have finished using it. Default is False." +msgstr "" + +#: ./doc/training-guides/module001-ch008-queues-messaging.xml:382(para) +msgid "Exclusive:exclusive queues (such as non-shared) may only be consumed from by the current connection. When exclusive is on, this also implies auto_delete. Default is False." +msgstr "" + +#: ./doc/training-guides/module001-ch008-queues-messaging.xml:388(para) +msgid "Exchange_type:AMQP defines several default exchange types (routing algorithms) that covers most of the common messaging use cases." +msgstr "" + +#: ./doc/training-guides/module001-ch008-queues-messaging.xml:393(para) +msgid "Auto_ack:acknowledgement is handled automatically once messages are received. By default auto_ack is set to False, and the receiver is required to manually handle acknowledgment." +msgstr "" + +#: ./doc/training-guides/module001-ch008-queues-messaging.xml:399(para) +msgid "No_ack:it disable acknowledgement on the server-side. This is different from auto_ack in that acknowledgement is turned off altogether. This functionality increases performance but at the cost of reliability. Messages can get lost if a client dies before it can deliver them to the application." +msgstr "" + +#: ./doc/training-guides/module001-ch008-queues-messaging.xml:407(para) +msgid "Auto_declare:if this is True and the exchange name is set, the exchange will be automatically declared at instantiation. Auto declare is on by default. Publishers specify most the parameters of Consumers (such as they do not specify a queue name), but they can also specify the following:" +msgstr "" + +#: ./doc/training-guides/module001-ch008-queues-messaging.xml:415(para) +msgid "Delivery_mode:the default delivery mode used for messages. The value is an integer. The following delivery modes are supported by RabbitMQ:" +msgstr "" + +#: ./doc/training-guides/module001-ch008-queues-messaging.xml:422(para) +msgid "1 or “transient”:the message is transient. Which means it is stored in memory only, and is lost if the server dies or restarts." +msgstr "" + +#: ./doc/training-guides/module001-ch008-queues-messaging.xml:427(para) +msgid "2 or “persistent”:the message is persistent. Which means the message is stored both in-memory, and on disk, and therefore preserved if the server dies or restarts." +msgstr "" + +#: ./doc/training-guides/module001-ch008-queues-messaging.xml:433(para) +msgid "The default value is 2 (persistent). During a send operation, Publishers can override the delivery mode of messages so that, for example, transient messages can be sent over a durable queue." +msgstr "" + +#: ./doc/training-guides/bk001-associate-training-guide.xml:5(title) +msgid "Associate Training Guide" +msgstr "" + +#: ./doc/training-guides/training-cluster-by-script.xml:5(title) ./doc/training-guides/bk000-preface.xml:137(title) +msgid "Building the Training Cluster, Scripted" +msgstr "" + +#: ./doc/training-guides/training-cluster-by-script.xml:6(para) +msgid "Setting Up Test Environment" +msgstr "" + +#: ./doc/training-guides/training-cluster-by-script.xml:7(para) +msgid "For using Virtual Box as test environment, you need to attach three network adapters" +msgstr "" + +#: ./doc/training-guides/training-cluster-by-script.xml:11(para) +msgid "Host-Only/ Bridged -- 10.10.10.51 (Guest) -- 10.10.10.xx (Host IP for Host-Only)" +msgstr "" + +#: ./doc/training-guides/training-cluster-by-script.xml:15(para) +msgid "Host-Only/ Bridged -- 192.168.100.51 (Guest) -- 192.168.100.xx (Host IP for Host-Only)" +msgstr "" + +#: ./doc/training-guides/training-cluster-by-script.xml:19(para) +msgid "Bridged/NAT -- DHCP -- These Scripts should be run without internet connection after Pre-Install.sh. If your networking configuration is not exact a few command will not work. you need to change the Templates/* to the required IP Addresses for custom networks." +msgstr "" + +#: ./doc/training-guides/training-cluster-by-script.xml:25(link) +msgid "Extract the scripts locally by downloading and running the scripts tar file." +msgstr "" + +#: ./doc/training-guides/training-cluster-by-script.xml:27(emphasis) +msgid "Testing" +msgstr "" + +#: ./doc/training-guides/training-cluster-by-script.xml:28(para) +msgid "As of now only */Scripts/ folders content are being tested. Please run the file ~/Scripts/test_scripts.sh for testing all the scripts at once with one click." +msgstr "" + +#: ./doc/training-guides/training-cluster-by-script.xml:33(para) +msgid "Test Scripts Individually. Run the Scripts inside the Scripts Folder to check whether the shell scripts are properly functioning. You Don't Need to install Vitual Box although it is advised to do so, as there is a good chance that you may end up breaking your host machine." +msgstr "" + +#: ./doc/training-guides/training-cluster-by-script.xml:39(para) +msgid "How to Test them. Testing these scripts is as simple as running them. Although some of the scripts need the required Input parameters. If you do not want to run them manually then you may run the Scripts/test_scripts.sh file. No Need for Virutalbox Guest Addons for testing the scripts as units." +msgstr "" + +#: ./doc/training-guides/training-cluster-by-script.xml:46(para) +msgid "Test Entire System you need to install Virtual Box, install Ubuntu Server 12.04 or 13.04. After installation you also need to install Virtual Box Guest Addons. To install Virtual Box guest addons you need do the following : Either use the Virtual Box Guest Addons Installation via. ISO, #apt-get install linux-headers-generic #mount /dev/cdrom0/ /tmp/cdrom #cd /tmp/cdrom/ #./virtualboxOr You May use Ubuntu Repositories for the same #apt-get install linux-headers-generic #apt-get --no-install-recommends install virtualbox-guest-additions" +msgstr "" + +#. When image changes, this message will be marked fuzzy or untranslated for you. +#. It doesn't matter what you translate it to: it's not used at all. +#: ./doc/training-guides/card074-horizon-snapshots.xml:12(None) ./doc/training-guides/card071-create-cinder-horizon.xml:11(None) ./doc/training-guides/card071-create-cinder-horizon.xml:15(None) ./doc/training-guides/card071-create-cinder-horizon.xml:19(None) ./doc/training-guides/bk001-ch003-associate-controller-node.xml:17(None) ./doc/training-guides/bk001-ch003-associate-controller-node.xml:24(None) ./doc/training-guides/bk001-ch003-associate-controller-node.xml:31(None) ./doc/training-guides/bk001-ch003-associate-controller-node.xml:40(None) ./doc/training-guides/bk001-ch003-associate-controller-node.xml:47(None) ./doc/training-guides/bk001-ch003-associate-controller-node.xml:54(None) ./doc/training-guides/bk001-ch003-associate-controller-node.xml:61(None) ./doc/training-guides/bk001-ch003-associate-controller-node.xml:68(None) ./doc/training-guides/bk001-ch003-associate-controller-node.xml:75(None) ./doc/training-guides/bk001-ch003-associate-controller-node.xml:82(None) ./doc/training-guides/bk002-ch010-operator-network-node.xml:17(None) ./doc/training-guides/bk002-ch010-operator-network-node.xml:24(None) ./doc/training-guides/bk001-ch009-associate-object-storage-node.xml:17(None) ./doc/training-guides/bk001-ch009-associate-object-storage-node.xml:24(None) ./doc/training-guides/bk001-ch009-associate-object-storage-node.xml:33(None) ./doc/training-guides/card072-cinder-attach-volume.xml:11(None) ./doc/training-guides/bk002-ch004-operator-controller-node.xml:17(None) ./doc/training-guides/bk002-ch004-operator-controller-node.xml:24(None) ./doc/training-guides/bk002-ch004-operator-controller-node.xml:31(None) ./doc/training-guides/bk002-ch002-operator-getting-started-lab.xml:15(None) ./doc/training-guides/bk002-ch002-operator-getting-started-lab.xml:22(None) ./doc/training-guides/bk002-ch002-operator-getting-started-lab.xml:29(None) ./doc/training-guides/bk002-ch002-operator-getting-started-lab.xml:36(None) ./doc/training-guides/bk002-ch002-operator-getting-started-lab.xml:43(None) ./doc/training-guides/bk002-ch007-operator-compute-node.xml:17(None) ./doc/training-guides/bk002-ch007-operator-compute-node.xml:24(None) ./doc/training-guides/bk002-ch007-operator-compute-node.xml:31(None) ./doc/training-guides/bk002-ch013-operator-object-storage-node.xml:17(None) ./doc/training-guides/bk002-ch013-operator-object-storage-node.xml:24(None) ./doc/training-guides/bk002-ch013-operator-object-storage-node.xml:35(None) ./doc/training-guides/bk002-ch013-operator-object-storage-node.xml:42(None) ./doc/training-guides/bk002-ch013-operator-object-storage-node.xml:49(None) ./doc/training-guides/bk002-ch013-operator-object-storage-node.xml:55(None) ./doc/training-guides/bk002-ch013-operator-object-storage-node.xml:62(None) ./doc/training-guides/bk002-ch013-operator-object-storage-node.xml:69(None) ./doc/training-guides/bk002-ch013-operator-object-storage-node.xml:76(None) ./doc/training-guides/bk002-ch001-operator-getting-started.xml:25(None) ./doc/training-guides/bk002-ch001-operator-getting-started.xml:32(None) ./doc/training-guides/bk002-ch001-operator-getting-started.xml:39(None) ./doc/training-guides/bk002-ch001-operator-getting-started.xml:46(None) ./doc/training-guides/bk002-ch001-operator-getting-started.xml:53(None) ./doc/training-guides/card008.xml:11(None) ./doc/training-guides/bk000-preface.xml:133(None) ./doc/training-guides/bk000-preface.xml:140(None) ./doc/training-guides/bk000-preface.xml:147(None) ./doc/training-guides/bk001-ch001-associate-getting-started.xml:27(None) ./doc/training-guides/bk001-ch001-associate-getting-started.xml:34(None) ./doc/training-guides/bk001-ch001-associate-getting-started.xml:41(None) ./doc/training-guides/bk001-ch001-associate-getting-started.xml:48(None) ./doc/training-guides/bk001-ch001-associate-getting-started.xml:55(None) ./doc/training-guides/card073-control-state-instance.xml:12(None) ./doc/training-guides/bk001-ch005-associate-compute-node.xml:17(None) ./doc/training-guides/bk001-ch005-associate-compute-node.xml:24(None) ./doc/training-guides/bk001-ch005-associate-compute-node.xml:31(None) ./doc/training-guides/bk001-ch005-associate-compute-node.xml:40(None) ./doc/training-guides/bk001-ch005-associate-compute-node.xml:47(None) ./doc/training-guides/bk001-ch005-associate-compute-node.xml:54(None) ./doc/training-guides/bk001-ch005-associate-compute-node.xml:61(None) ./doc/training-guides/bk001-ch005-associate-compute-node.xml:68(None) ./doc/training-guides/bk001-ch005-associate-compute-node.xml:75(None) ./doc/training-guides/card128-swift.xml:11(None) ./doc/training-guides/bk003-developer-training-guide.xml:13(None) ./doc/training-guides/bk003-developer-training-guide.xml:20(None) ./doc/training-guides/bk003-developer-training-guide.xml:27(None) ./doc/training-guides/bk003-developer-training-guide.xml:34(None) ./doc/training-guides/bk003-developer-training-guide.xml:41(None) ./doc/training-guides/bk003-developer-training-guide.xml:48(None) ./doc/training-guides/bk003-developer-training-guide.xml:55(None) ./doc/training-guides/bk003-developer-training-guide.xml:62(None) ./doc/training-guides/bk003-developer-training-guide.xml:69(None) ./doc/training-guides/bk001-ch007-associate-network-node.xml:17(None) ./doc/training-guides/bk001-ch007-associate-network-node.xml:24(None) ./doc/training-guides/bk001-ch007-associate-network-node.xml:33(None) ./doc/training-guides/bk001-ch007-associate-network-node.xml:40(None) ./doc/training-guides/card070-create-floating-ips.xml:11(None) ./doc/training-guides/card070-create-floating-ips.xml:16(None) ./doc/training-guides/card070-create-floating-ips.xml:21(None) +msgid "@@image: 'figures/openstack-training-remote-content-not-available.png'; md5=f2583b37e01220460a55b8c255c987c3" +msgstr "" + +#: ./doc/training-guides/card074-horizon-snapshots.xml:7(title) +msgid "Creating Snapshots" +msgstr "" + +#: ./doc/training-guides/card074-horizon-snapshots.xml:8(emphasis) +msgid "Creating image snapshots using Horizon" +msgstr "" + +#: ./doc/training-guides/card074-horizon-snapshots.xml:12(para) ./doc/training-guides/card071-create-cinder-horizon.xml:11(para) ./doc/training-guides/card071-create-cinder-horizon.xml:15(para) ./doc/training-guides/card071-create-cinder-horizon.xml:19(para) ./doc/training-guides/bk001-ch003-associate-controller-node.xml:17(para) ./doc/training-guides/bk001-ch003-associate-controller-node.xml:24(para) ./doc/training-guides/bk001-ch003-associate-controller-node.xml:31(para) ./doc/training-guides/bk001-ch003-associate-controller-node.xml:40(para) ./doc/training-guides/bk001-ch003-associate-controller-node.xml:47(para) ./doc/training-guides/bk001-ch003-associate-controller-node.xml:54(para) ./doc/training-guides/bk001-ch003-associate-controller-node.xml:61(para) ./doc/training-guides/bk001-ch003-associate-controller-node.xml:68(para) ./doc/training-guides/bk001-ch003-associate-controller-node.xml:75(para) ./doc/training-guides/bk001-ch003-associate-controller-node.xml:82(para) ./doc/training-guides/bk002-ch010-operator-network-node.xml:17(para) ./doc/training-guides/bk002-ch010-operator-network-node.xml:24(para) ./doc/training-guides/bk001-ch009-associate-object-storage-node.xml:17(para) ./doc/training-guides/bk001-ch009-associate-object-storage-node.xml:24(para) ./doc/training-guides/bk001-ch009-associate-object-storage-node.xml:33(para) ./doc/training-guides/card072-cinder-attach-volume.xml:11(para) ./doc/training-guides/bk002-ch004-operator-controller-node.xml:17(para) ./doc/training-guides/bk002-ch004-operator-controller-node.xml:24(para) ./doc/training-guides/bk002-ch004-operator-controller-node.xml:31(para) ./doc/training-guides/bk002-ch002-operator-getting-started-lab.xml:15(para) ./doc/training-guides/bk002-ch002-operator-getting-started-lab.xml:22(para) ./doc/training-guides/bk002-ch002-operator-getting-started-lab.xml:29(para) ./doc/training-guides/bk002-ch002-operator-getting-started-lab.xml:36(para) ./doc/training-guides/bk002-ch002-operator-getting-started-lab.xml:43(para) ./doc/training-guides/bk002-ch007-operator-compute-node.xml:17(para) ./doc/training-guides/bk002-ch007-operator-compute-node.xml:24(para) ./doc/training-guides/bk002-ch007-operator-compute-node.xml:31(para) ./doc/training-guides/bk002-ch013-operator-object-storage-node.xml:17(para) ./doc/training-guides/bk002-ch013-operator-object-storage-node.xml:24(para) ./doc/training-guides/bk002-ch013-operator-object-storage-node.xml:35(para) ./doc/training-guides/bk002-ch013-operator-object-storage-node.xml:42(para) ./doc/training-guides/bk002-ch013-operator-object-storage-node.xml:49(para) ./doc/training-guides/bk002-ch013-operator-object-storage-node.xml:55(para) ./doc/training-guides/bk002-ch013-operator-object-storage-node.xml:62(para) ./doc/training-guides/bk002-ch013-operator-object-storage-node.xml:69(para) ./doc/training-guides/bk002-ch013-operator-object-storage-node.xml:76(para) ./doc/training-guides/bk002-ch001-operator-getting-started.xml:25(para) ./doc/training-guides/bk002-ch001-operator-getting-started.xml:32(para) ./doc/training-guides/bk002-ch001-operator-getting-started.xml:39(para) ./doc/training-guides/bk002-ch001-operator-getting-started.xml:46(para) ./doc/training-guides/bk002-ch001-operator-getting-started.xml:53(para) ./doc/training-guides/card008.xml:11(para) ./doc/training-guides/bk000-preface.xml:133(para) ./doc/training-guides/bk000-preface.xml:140(para) ./doc/training-guides/bk000-preface.xml:147(para) ./doc/training-guides/bk001-ch001-associate-getting-started.xml:27(para) ./doc/training-guides/bk001-ch001-associate-getting-started.xml:34(para) ./doc/training-guides/bk001-ch001-associate-getting-started.xml:41(para) ./doc/training-guides/bk001-ch001-associate-getting-started.xml:48(para) ./doc/training-guides/bk001-ch001-associate-getting-started.xml:55(para) ./doc/training-guides/card073-control-state-instance.xml:12(para) ./doc/training-guides/bk001-ch005-associate-compute-node.xml:17(para) ./doc/training-guides/bk001-ch005-associate-compute-node.xml:24(para) ./doc/training-guides/bk001-ch005-associate-compute-node.xml:31(para) ./doc/training-guides/bk001-ch005-associate-compute-node.xml:40(para) ./doc/training-guides/bk001-ch005-associate-compute-node.xml:47(para) ./doc/training-guides/bk001-ch005-associate-compute-node.xml:54(para) ./doc/training-guides/bk001-ch005-associate-compute-node.xml:61(para) ./doc/training-guides/bk001-ch005-associate-compute-node.xml:68(para) ./doc/training-guides/bk001-ch005-associate-compute-node.xml:75(para) ./doc/training-guides/card128-swift.xml:11(para) ./doc/training-guides/bk003-developer-training-guide.xml:13(para) ./doc/training-guides/bk003-developer-training-guide.xml:20(para) ./doc/training-guides/bk003-developer-training-guide.xml:27(para) ./doc/training-guides/bk003-developer-training-guide.xml:34(para) ./doc/training-guides/bk003-developer-training-guide.xml:41(para) ./doc/training-guides/bk003-developer-training-guide.xml:48(para) ./doc/training-guides/bk003-developer-training-guide.xml:55(para) ./doc/training-guides/bk003-developer-training-guide.xml:62(para) ./doc/training-guides/bk003-developer-training-guide.xml:69(para) ./doc/training-guides/bk001-ch007-associate-network-node.xml:17(para) ./doc/training-guides/bk001-ch007-associate-network-node.xml:24(para) ./doc/training-guides/bk001-ch007-associate-network-node.xml:33(para) ./doc/training-guides/bk001-ch007-associate-network-node.xml:40(para) ./doc/training-guides/card070-create-floating-ips.xml:11(para) ./doc/training-guides/card070-create-floating-ips.xml:16(para) ./doc/training-guides/card070-create-floating-ips.xml:21(para) +msgid "Remote content not available" +msgstr "" + +#: ./doc/training-guides/card074-horizon-snapshots.xml:12(link) ./doc/training-guides/card071-create-cinder-horizon.xml:11(link) ./doc/training-guides/card071-create-cinder-horizon.xml:15(link) ./doc/training-guides/card071-create-cinder-horizon.xml:19(link) ./doc/training-guides/bk001-ch003-associate-controller-node.xml:17(link) ./doc/training-guides/bk001-ch003-associate-controller-node.xml:24(link) ./doc/training-guides/bk001-ch003-associate-controller-node.xml:31(link) ./doc/training-guides/bk001-ch003-associate-controller-node.xml:40(link) ./doc/training-guides/bk001-ch003-associate-controller-node.xml:47(link) ./doc/training-guides/bk001-ch003-associate-controller-node.xml:54(link) ./doc/training-guides/bk001-ch003-associate-controller-node.xml:61(link) ./doc/training-guides/bk001-ch003-associate-controller-node.xml:68(link) ./doc/training-guides/bk001-ch003-associate-controller-node.xml:75(link) ./doc/training-guides/bk001-ch003-associate-controller-node.xml:82(link) ./doc/training-guides/bk002-ch010-operator-network-node.xml:17(link) ./doc/training-guides/bk002-ch010-operator-network-node.xml:24(link) ./doc/training-guides/bk001-ch009-associate-object-storage-node.xml:17(link) ./doc/training-guides/bk001-ch009-associate-object-storage-node.xml:24(link) ./doc/training-guides/bk001-ch009-associate-object-storage-node.xml:33(link) ./doc/training-guides/card072-cinder-attach-volume.xml:11(link) ./doc/training-guides/bk002-ch004-operator-controller-node.xml:17(link) ./doc/training-guides/bk002-ch004-operator-controller-node.xml:24(link) ./doc/training-guides/bk002-ch004-operator-controller-node.xml:31(link) ./doc/training-guides/bk002-ch002-operator-getting-started-lab.xml:15(link) ./doc/training-guides/bk002-ch002-operator-getting-started-lab.xml:22(link) ./doc/training-guides/bk002-ch002-operator-getting-started-lab.xml:29(link) ./doc/training-guides/bk002-ch002-operator-getting-started-lab.xml:36(link) ./doc/training-guides/bk002-ch002-operator-getting-started-lab.xml:43(link) ./doc/training-guides/bk002-ch007-operator-compute-node.xml:17(link) ./doc/training-guides/bk002-ch007-operator-compute-node.xml:24(link) ./doc/training-guides/bk002-ch007-operator-compute-node.xml:31(link) ./doc/training-guides/bk002-ch013-operator-object-storage-node.xml:17(link) ./doc/training-guides/bk002-ch013-operator-object-storage-node.xml:24(link) ./doc/training-guides/bk002-ch013-operator-object-storage-node.xml:35(link) ./doc/training-guides/bk002-ch013-operator-object-storage-node.xml:42(link) ./doc/training-guides/bk002-ch013-operator-object-storage-node.xml:49(link) ./doc/training-guides/bk002-ch013-operator-object-storage-node.xml:55(link) ./doc/training-guides/bk002-ch013-operator-object-storage-node.xml:62(link) ./doc/training-guides/bk002-ch013-operator-object-storage-node.xml:69(link) ./doc/training-guides/bk002-ch013-operator-object-storage-node.xml:76(link) ./doc/training-guides/bk002-ch001-operator-getting-started.xml:25(link) ./doc/training-guides/bk002-ch001-operator-getting-started.xml:32(link) ./doc/training-guides/bk002-ch001-operator-getting-started.xml:39(link) ./doc/training-guides/bk002-ch001-operator-getting-started.xml:46(link) ./doc/training-guides/bk002-ch001-operator-getting-started.xml:53(link) ./doc/training-guides/card008.xml:11(link) ./doc/training-guides/bk000-preface.xml:133(link) ./doc/training-guides/bk000-preface.xml:140(link) ./doc/training-guides/bk000-preface.xml:147(link) ./doc/training-guides/bk001-ch001-associate-getting-started.xml:27(link) ./doc/training-guides/bk001-ch001-associate-getting-started.xml:34(link) ./doc/training-guides/bk001-ch001-associate-getting-started.xml:41(link) ./doc/training-guides/bk001-ch001-associate-getting-started.xml:48(link) ./doc/training-guides/bk001-ch001-associate-getting-started.xml:55(link) ./doc/training-guides/card073-control-state-instance.xml:12(link) ./doc/training-guides/bk001-ch005-associate-compute-node.xml:17(link) ./doc/training-guides/bk001-ch005-associate-compute-node.xml:24(link) ./doc/training-guides/bk001-ch005-associate-compute-node.xml:31(link) ./doc/training-guides/bk001-ch005-associate-compute-node.xml:40(link) ./doc/training-guides/bk001-ch005-associate-compute-node.xml:47(link) ./doc/training-guides/bk001-ch005-associate-compute-node.xml:54(link) ./doc/training-guides/bk001-ch005-associate-compute-node.xml:61(link) ./doc/training-guides/bk001-ch005-associate-compute-node.xml:68(link) ./doc/training-guides/bk001-ch005-associate-compute-node.xml:75(link) ./doc/training-guides/card128-swift.xml:11(link) ./doc/training-guides/bk003-developer-training-guide.xml:13(link) ./doc/training-guides/bk003-developer-training-guide.xml:20(link) ./doc/training-guides/bk003-developer-training-guide.xml:27(link) ./doc/training-guides/bk003-developer-training-guide.xml:34(link) ./doc/training-guides/bk003-developer-training-guide.xml:41(link) ./doc/training-guides/bk003-developer-training-guide.xml:48(link) ./doc/training-guides/bk003-developer-training-guide.xml:55(link) ./doc/training-guides/bk003-developer-training-guide.xml:62(link) ./doc/training-guides/bk003-developer-training-guide.xml:69(link) ./doc/training-guides/bk001-ch007-associate-network-node.xml:17(link) ./doc/training-guides/bk001-ch007-associate-network-node.xml:24(link) ./doc/training-guides/bk001-ch007-associate-network-node.xml:33(link) ./doc/training-guides/bk001-ch007-associate-network-node.xml:40(link) ./doc/training-guides/card070-create-floating-ips.xml:11(link) ./doc/training-guides/card070-create-floating-ips.xml:16(link) ./doc/training-guides/card070-create-floating-ips.xml:21(link) +msgid "https://docs.google.com/drawings/d/1J2LZSxmc06xKyxMgPjv5fC0blV7qK6956-AeTmFOZD4/edit?usp=sharing" +msgstr "" + +#: ./doc/training-guides/card071-create-cinder-horizon.xml:7(title) +msgid "Creating and Deleting Volumes" +msgstr "" + +#: ./doc/training-guides/bk001-ch003-associate-controller-node.xml:8(title) ./doc/training-guides/bk002-ch004-operator-controller-node.xml:8(title) ./doc/training-guides/lab001-control-node.xml:24(guilabel) +msgid "Controller Node" +msgstr "" + +#: ./doc/training-guides/bk001-ch003-associate-controller-node.xml:10(title) +msgid "Day 1, 11:15 to 12:30, 13:30 to 14:45" +msgstr "" + +#: ./doc/training-guides/bk001-ch003-associate-controller-node.xml:14(title) ./doc/training-guides/module001-ch006-overview-horizon-cli.xml:7(title) +msgid "Overview Horizon and OpenStack CLI" +msgstr "" + +#: ./doc/training-guides/bk001-ch003-associate-controller-node.xml:21(title) ./doc/training-guides/module001-ch007-keystone-arch.xml:6(title) +msgid "Keystone Architecture" +msgstr "" + +#: ./doc/training-guides/bk001-ch003-associate-controller-node.xml:35(title) ./doc/training-guides/bk001-ch009-associate-object-storage-node.xml:28(title) ./doc/training-guides/bk001-ch005-associate-compute-node.xml:35(title) ./doc/training-guides/bk001-ch007-associate-network-node.xml:28(title) +msgid "Administration Tasks" +msgstr "" + +#: ./doc/training-guides/bk001-ch003-associate-controller-node.xml:37(title) +msgid "Identity CI Commands" +msgstr "" + +#: ./doc/training-guides/bk001-ch003-associate-controller-node.xml:44(title) +msgid "Identity User Management" +msgstr "" + +#: ./doc/training-guides/bk001-ch003-associate-controller-node.xml:51(title) +msgid "Image CLI Commands" +msgstr "" + +#: ./doc/training-guides/bk001-ch003-associate-controller-node.xml:58(title) +msgid "Image List Images" +msgstr "" + +#: ./doc/training-guides/bk001-ch003-associate-controller-node.xml:65(title) +msgid "Image Adding Images" +msgstr "" + +#: ./doc/training-guides/bk001-ch003-associate-controller-node.xml:72(title) +msgid "Image Manage Images" +msgstr "" + +#: ./doc/training-guides/bk001-ch003-associate-controller-node.xml:79(title) +msgid "Message Queue Configuration" +msgstr "" + +#. When image changes, this message will be marked fuzzy or untranslated for you. +#. It doesn't matter what you translate it to: it's not used at all. +#: ./doc/training-guides/lab002-network-node.xml:14(None) ./doc/training-guides/lab003-compute-node.xml:17(None) ./doc/training-guides/lab001-control-node.xml:13(None) ./doc/training-guides/lab000-virtualbox-basics.xml:138(None) +msgid "@@image: 'figures/lab000-virtual-box/image03.png'; md5=d25af14759f84d6448d9bedfc67f18b5" +msgstr "" + +#: ./doc/training-guides/lab002-network-node.xml:7(emphasis) ./doc/training-guides/lab003-compute-node.xml:10(emphasis) ./doc/training-guides/lab001-control-node.xml:8(emphasis) ./doc/training-guides/lab000-virtualbox-basics.xml:131(emphasis) +msgid "Network Diagram :" +msgstr "" + +#: ./doc/training-guides/lab002-network-node.xml:18(para) ./doc/training-guides/lab003-compute-node.xml:21(para) ./doc/training-guides/lab001-control-node.xml:17(para) +msgid "Vboxnet0, Vboxnet1, Vboxnet2 - are virtual networks setup up by virtual box with your host machine. This is the way your host can communicate with the virtual machines. These networks are in turn used by virtual box VM’s for OpenStack networks, so that OpenStack’s services can communicate with each other." +msgstr "" + +#: ./doc/training-guides/lab002-network-node.xml:24(para) ./doc/training-guides/lab003-compute-node.xml:29(para) ./doc/training-guides/lab001-control-node.xml:25(para) +msgid "Start your Controller Node the one you setup in previous section." +msgstr "" + +#: ./doc/training-guides/lab002-network-node.xml:25(emphasis) ./doc/training-guides/lab003-compute-node.xml:31(emphasis) +msgid "Preparing Ubuntu 12.04" +msgstr "" + +#: ./doc/training-guides/lab002-network-node.xml:28(para) ./doc/training-guides/lab003-compute-node.xml:34(para) ./doc/training-guides/lab001-control-node.xml:30(para) +msgid "After you install Ubuntu Server, go in sudo mode" +msgstr "" + +#: ./doc/training-guides/lab002-network-node.xml:34(para) ./doc/training-guides/lab003-compute-node.xml:40(para) ./doc/training-guides/lab001-control-node.xml:36(para) +msgid "Add Havana repositories:" +msgstr "" + +#: ./doc/training-guides/lab002-network-node.xml:41(para) ./doc/training-guides/lab002-network-node.xml:223(para) ./doc/training-guides/lab003-compute-node.xml:47(para) ./doc/training-guides/lab001-control-node.xml:41(para) +msgid "Update your system:" +msgstr "" + +#: ./doc/training-guides/lab002-network-node.xml:49(para) ./doc/training-guides/lab003-compute-node.xml:55(para) +msgid "Install NTP and other services:" +msgstr "" + +#: ./doc/training-guides/lab002-network-node.xml:55(para) ./doc/training-guides/lab003-compute-node.xml:61(para) +msgid "Configure NTP Server to Controller Node:" +msgstr "" + +#: ./doc/training-guides/lab002-network-node.xml:64(para) +msgid "Enable IP Forwarding by adding the following to /etc/sysctl.conf:" +msgstr "" + +#: ./doc/training-guides/lab002-network-node.xml:72(para) ./doc/training-guides/lab003-compute-node.xml:78(para) +msgid "Run the following commands:" +msgstr "" + +#: ./doc/training-guides/lab002-network-node.xml:81(emphasis) +msgid "OpenVSwitch" +msgstr "" + +#: ./doc/training-guides/lab002-network-node.xml:84(para) +msgid "Install OpenVSwitch Packages:" +msgstr "" + +#: ./doc/training-guides/lab002-network-node.xml:90(para) +msgid "Create the bridges:" +msgstr "" + +#: ./doc/training-guides/lab002-network-node.xml:97(emphasis) ./doc/training-guides/lab003-compute-node.xml:146(para) ./doc/training-guides/lab001-control-node.xml:366(emphasis) +msgid "Neutron" +msgstr "" + +#: ./doc/training-guides/lab002-network-node.xml:100(para) +msgid "Neutron:" +msgstr "" + +#: ./doc/training-guides/lab002-network-node.xml:106(para) +msgid "Edit /etc/neutron/api-paste.ini:" +msgstr "" + +#: ./doc/training-guides/lab002-network-node.xml:119(para) +msgid "Edit /etc/neutron/plugins/openvswitch/ovs_neutron_plugin.ini:" +msgstr "" + +#: ./doc/training-guides/lab002-network-node.xml:143(para) +msgid "Edit /etc/neutron/metadata_agent.ini:" +msgstr "" + +#: ./doc/training-guides/lab002-network-node.xml:159(para) +msgid "Edit /etc/neutron/dhcp_agent.ini:" +msgstr "" + +#: ./doc/training-guides/lab002-network-node.xml:165(para) +msgid "Edit /etc/neutron/l3_agent.ini:" +msgstr "" + +#: ./doc/training-guides/lab002-network-node.xml:173(para) +msgid "Edit /etc/neutron/neutron.conf:" +msgstr "" + +#: ./doc/training-guides/lab002-network-node.xml:190(para) +msgid "Edit /etc/sudoers.d/neutron_sudoers::" +msgstr "" + +#: ./doc/training-guides/lab002-network-node.xml:197(para) +msgid "Restart Services:" +msgstr "" + +#: ./doc/training-guides/lab002-network-node.xml:205(para) +msgid "Edit Network Interfaces file /etc/network/interfaces:" +msgstr "" + +#. When image changes, this message will be marked fuzzy or untranslated for you. +#. It doesn't matter what you translate it to: it's not used at all. +#: ./doc/training-guides/module001-ch003-core-projects.xml:157(None) +msgid "@@image: 'figures/image05.png'; md5=6471ce66920c1bc1b8bd3854cf836b06" +msgstr "" + +#. When image changes, this message will be marked fuzzy or untranslated for you. +#. It doesn't matter what you translate it to: it's not used at all. +#: ./doc/training-guides/module001-ch003-core-projects.xml:170(None) +msgid "@@image: 'figures/image16.png'; md5=65b6013bd11cf821161a1ebe91d9968b" +msgstr "" + +#. When image changes, this message will be marked fuzzy or untranslated for you. +#. It doesn't matter what you translate it to: it's not used at all. +#: ./doc/training-guides/module001-ch003-core-projects.xml:201(None) +msgid "@@image: 'figures/image06.png'; md5=ad0f7b815daaf1979c604ac862e99a87" +msgstr "" + +#. When image changes, this message will be marked fuzzy or untranslated for you. +#. It doesn't matter what you translate it to: it's not used at all. +#: ./doc/training-guides/module001-ch003-core-projects.xml:242(None) +msgid "@@image: 'figures/image03.png'; md5=25ce40bfee4d12f6bf6d781e70b4402d" +msgstr "" + +#. When image changes, this message will be marked fuzzy or untranslated for you. +#. It doesn't matter what you translate it to: it's not used at all. +#: ./doc/training-guides/module001-ch003-core-projects.xml:296(None) +msgid "@@image: 'figures/image17.png'; md5=b4720b3ca2aa5b05cebb27c251a81583" +msgstr "" + +#. When image changes, this message will be marked fuzzy or untranslated for you. +#. It doesn't matter what you translate it to: it's not used at all. +#: ./doc/training-guides/module001-ch003-core-projects.xml:426(None) +msgid "@@image: 'figures/image26.png'; md5=4dd64736f53fb4d9398067a69e13f32b" +msgstr "" + +#: ./doc/training-guides/module001-ch003-core-projects.xml:3(title) +msgid "OpenStack Projects, History, and Releases Overview" +msgstr "" + +#: ./doc/training-guides/module001-ch003-core-projects.xml:4(guilabel) +msgid "Project history and releases overview." +msgstr "" + +#: ./doc/training-guides/module001-ch003-core-projects.xml:5(para) +msgid "OpenStack is a cloud computing project to provide an infrastructure as a service (IaaS). It is free open source software released under the terms of the Apache License. The project is managed by the OpenStack Foundation, a non-profit corporate entity established in September 2012 to promote OpenStack software and its community." +msgstr "" + +#: ./doc/training-guides/module001-ch003-core-projects.xml:11(para) +msgid "More than 200 companies joined the project among which are AMD, Brocade Communications Systems, Canonical, Cisco, Dell, EMC, Ericsson, Groupe Bull, HP, IBM, Inktank, Intel, NEC, Rackspace Hosting, Red Hat, SUSE Linux, VMware, and Yahoo!" +msgstr "" + +#: ./doc/training-guides/module001-ch003-core-projects.xml:15(para) +msgid "The technology consists of a series of interrelated projects that control pools of processing, storage, and networking resources throughout a data center, all managed through a dashboard that gives administrators control while empowering its users to provision resources through a web interface." +msgstr "" + +#: ./doc/training-guides/module001-ch003-core-projects.xml:20(para) +msgid "The OpenStack community collaborates around a six-month, time-based release cycle with frequent development milestones. During the planning phase of each release, the community gathers for the OpenStack Design Summit to facilitate developer working sessions and assemble plans." +msgstr "" + +#: ./doc/training-guides/module001-ch003-core-projects.xml:25(para) +msgid "In July 2010 Rackspace Hosting and NASA jointly launched an open-source cloud-software initiative known as OpenStack. The OpenStack project intended to help organizations which offer cloud-computing services running on standard hardware. The first official release, code-named Austin, appeared four months later, with plans to release regular updates of the software every few months. The early code came from the NASA Nebula platform and from the Rackspace Cloud Files platform. In July 2011, Ubuntu Linux developers adopted OpenStack." +msgstr "" + +#: ./doc/training-guides/module001-ch003-core-projects.xml:34(emphasis) +msgid "OpenStack Releases" +msgstr "" + +#: ./doc/training-guides/module001-ch003-core-projects.xml:38(td) +msgid "Release Name" +msgstr "" + +#: ./doc/training-guides/module001-ch003-core-projects.xml:39(td) +msgid "Release Date" +msgstr "" + +#: ./doc/training-guides/module001-ch003-core-projects.xml:40(td) +msgid "Included Components" +msgstr "" + +#: ./doc/training-guides/module001-ch003-core-projects.xml:43(td) +msgid "Austin" +msgstr "" + +#: ./doc/training-guides/module001-ch003-core-projects.xml:44(td) +msgid "21 October 2010" +msgstr "" + +#: ./doc/training-guides/module001-ch003-core-projects.xml:45(td) +msgid "Nova, Swift" +msgstr "" + +#: ./doc/training-guides/module001-ch003-core-projects.xml:48(td) +msgid "Bexar" +msgstr "" + +#: ./doc/training-guides/module001-ch003-core-projects.xml:49(td) +msgid "3 February 2011" +msgstr "" + +#: ./doc/training-guides/module001-ch003-core-projects.xml:50(td) ./doc/training-guides/module001-ch003-core-projects.xml:55(td) ./doc/training-guides/module001-ch003-core-projects.xml:60(td) +msgid "Nova, Glance, Swift" +msgstr "" + +#: ./doc/training-guides/module001-ch003-core-projects.xml:53(td) +msgid "Cactus" +msgstr "" + +#: ./doc/training-guides/module001-ch003-core-projects.xml:54(td) +msgid "15 April 2011" +msgstr "" + +#: ./doc/training-guides/module001-ch003-core-projects.xml:58(td) +msgid "Diablo" +msgstr "" + +#: ./doc/training-guides/module001-ch003-core-projects.xml:59(td) +msgid "22 September 2011" +msgstr "" + +#: ./doc/training-guides/module001-ch003-core-projects.xml:63(td) +msgid "Essex" +msgstr "" + +#: ./doc/training-guides/module001-ch003-core-projects.xml:64(td) +msgid "5 April 2012" +msgstr "" + +#: ./doc/training-guides/module001-ch003-core-projects.xml:65(td) +msgid "Nova, Glance, Swift, Horizon, Keystone" +msgstr "" + +#: ./doc/training-guides/module001-ch003-core-projects.xml:69(td) +msgid "Folsom" +msgstr "" + +#: ./doc/training-guides/module001-ch003-core-projects.xml:70(td) +msgid "27 September 2012" +msgstr "" + +#: ./doc/training-guides/module001-ch003-core-projects.xml:71(td) ./doc/training-guides/module001-ch003-core-projects.xml:77(td) +msgid "Nova, Glance, Swift, Horizon, Keystone, Quantum, Cinder" +msgstr "" + +#: ./doc/training-guides/module001-ch003-core-projects.xml:75(td) +msgid "Grizzly" +msgstr "" + +#: ./doc/training-guides/module001-ch003-core-projects.xml:76(td) +msgid "4 April 2013" +msgstr "" + +#: ./doc/training-guides/module001-ch003-core-projects.xml:81(td) +msgid "Havana" +msgstr "" + +#: ./doc/training-guides/module001-ch003-core-projects.xml:82(td) +msgid "17 October 2013" +msgstr "" + +#: ./doc/training-guides/module001-ch003-core-projects.xml:83(td) +msgid "Nova, Glance, Swift, Horizon, Keystone, Neutron, Cinder" +msgstr "" + +#: ./doc/training-guides/module001-ch003-core-projects.xml:87(td) ./doc/training-guides/sources/cinder/drivers.xml:56(title) +msgid "Icehouse" +msgstr "" + +#: ./doc/training-guides/module001-ch003-core-projects.xml:88(td) +msgid "April 2014" +msgstr "" + +#: ./doc/training-guides/module001-ch003-core-projects.xml:89(td) +msgid "Nova, Glance, Swift, Horizon, Keystone, Neutron, Cinder, (More to be added)" +msgstr "" + +#: ./doc/training-guides/module001-ch003-core-projects.xml:95(para) +msgid "Some OpenStack users include:" +msgstr "" + +#: ./doc/training-guides/module001-ch003-core-projects.xml:98(para) +msgid "PayPal / eBay" +msgstr "" + +#: ./doc/training-guides/module001-ch003-core-projects.xml:101(para) +msgid "NASA" +msgstr "" + +#: ./doc/training-guides/module001-ch003-core-projects.xml:104(para) +msgid "CERN" +msgstr "" + +#: ./doc/training-guides/module001-ch003-core-projects.xml:107(para) +msgid "Yahoo!" +msgstr "" + +#: ./doc/training-guides/module001-ch003-core-projects.xml:110(para) +msgid "Rackspace Cloud" +msgstr "" + +#: ./doc/training-guides/module001-ch003-core-projects.xml:113(para) +msgid "HP Public Cloud" +msgstr "" + +#: ./doc/training-guides/module001-ch003-core-projects.xml:116(para) +msgid "MercadoLibre.com" +msgstr "" + +#: ./doc/training-guides/module001-ch003-core-projects.xml:119(para) +msgid "AT&T" +msgstr "" + +#: ./doc/training-guides/module001-ch003-core-projects.xml:122(para) +msgid "KT (formerly Korea Telecom)" +msgstr "" + +#: ./doc/training-guides/module001-ch003-core-projects.xml:125(para) +msgid "Deutsche Telekom" +msgstr "" + +#: ./doc/training-guides/module001-ch003-core-projects.xml:128(para) +msgid "Wikimedia Labs" +msgstr "" + +#: ./doc/training-guides/module001-ch003-core-projects.xml:131(para) +msgid "Hostalia of Telef nica Group" +msgstr "" + +#: ./doc/training-guides/module001-ch003-core-projects.xml:134(para) +msgid "SUSE Cloud solution" +msgstr "" + +#: ./doc/training-guides/module001-ch003-core-projects.xml:137(para) +msgid "Red Hat OpenShift PaaS solution" +msgstr "" + +#: ./doc/training-guides/module001-ch003-core-projects.xml:140(para) +msgid "Zadara Storage" +msgstr "" + +#: ./doc/training-guides/module001-ch003-core-projects.xml:143(para) +msgid "Mint Services" +msgstr "" + +#: ./doc/training-guides/module001-ch003-core-projects.xml:146(para) +msgid "GridCentric" +msgstr "" + +#: ./doc/training-guides/module001-ch003-core-projects.xml:149(para) +msgid "OpenStack is a true and innovative open standard. For more user stories, see http://goo.gl/aF4lsL." +msgstr "" + +#: ./doc/training-guides/module001-ch003-core-projects.xml:152(guilabel) +msgid "Release Cycle" +msgstr "" + +#: ./doc/training-guides/module001-ch003-core-projects.xml:154(title) +msgid "Community Heartbeat" +msgstr "" + +#: ./doc/training-guides/module001-ch003-core-projects.xml:161(para) +msgid "OpenStack is based on a coordinated 6-month release cycle with frequent development milestones. You can find a link to the current development release schedule here. The Release Cycle is made of four major stages. Various OpenStack releases are named as follows Various Companies Contributing to OpenStack" +msgstr "" + +#: ./doc/training-guides/module001-ch003-core-projects.xml:167(title) +msgid "Various Projects under OpenStack" +msgstr "" + +#: ./doc/training-guides/module001-ch003-core-projects.xml:174(para) +msgid "The creation of OpenStack took an estimated 249 years of effort (COCOMO model)." +msgstr "" + +#: ./doc/training-guides/module001-ch003-core-projects.xml:176(para) +msgid "In a nutshell, OpenStack has:" +msgstr "" + +#: ./doc/training-guides/module001-ch003-core-projects.xml:179(para) +msgid "64,396 commits made by 1,128 contributors, with its first commit made in May, 2010." +msgstr "" + +#: ./doc/training-guides/module001-ch003-core-projects.xml:183(para) +msgid "908,491 lines of code. OpenStack is written mostly in Python with an average number of source code comments." +msgstr "" + +#: ./doc/training-guides/module001-ch003-core-projects.xml:187(para) +msgid "A code base with a long source history." +msgstr "" + +#: ./doc/training-guides/module001-ch003-core-projects.xml:190(para) +msgid "Increasing Y-O-Y commits." +msgstr "" + +#: ./doc/training-guides/module001-ch003-core-projects.xml:193(para) +msgid "A very large development team comprised of people from around the world." +msgstr "" + +#: ./doc/training-guides/module001-ch003-core-projects.xml:198(title) +msgid "Programming Languages used to design OpenStack" +msgstr "" + +#: ./doc/training-guides/module001-ch003-core-projects.xml:205(para) +msgid "For an overview of OpenStack refer to http://www.openstack.org or http://goo.gl/4q7nVI. Common questions and answers are also covered here." +msgstr "" + +#: ./doc/training-guides/module001-ch003-core-projects.xml:208(guilabel) +msgid "Core Projects Overview" +msgstr "" + +#: ./doc/training-guides/module001-ch003-core-projects.xml:209(para) +msgid "Let's take a dive into some of the technical aspects of OpenStack. Its scalability and flexibility are a few of the awesome features that make it a rock-solid cloud computing platform. The OpenStack core projects serve the community and its demands." +msgstr "" + +#: ./doc/training-guides/module001-ch003-core-projects.xml:214(para) +msgid "Being a cloud computing platform, OpenStack consists of many core and incubated projects which makes it really good as an IaaS cloud computing platform/Operating System. But the following points are the main components of OpenStack that are necessary to be present in the cloud to call it an OpenStack Cloud." +msgstr "" + +#: ./doc/training-guides/module001-ch003-core-projects.xml:220(guimenu) +msgid "Components of OpenStack" +msgstr "" + +#: ./doc/training-guides/module001-ch003-core-projects.xml:221(para) +msgid "OpenStack has a modular architecture with various code names for its components. OpenStack has several shared services that span the three pillars of compute, storage and networking, making it easier to implement and operate your cloud. These services - including identity, image management and a web interface - integrate the OpenStack components with each other as well as external systems to provide a unified experience for users as they interact with different cloud resources." +msgstr "" + +#: ./doc/training-guides/module001-ch003-core-projects.xml:229(guisubmenu) +msgid "Compute (Nova)" +msgstr "" + +#: ./doc/training-guides/module001-ch003-core-projects.xml:230(para) +msgid "The OpenStack cloud operating system enables enterprises and service providers to offer on-demand computing resources, by provisioning and managing large networks of virtual machines. Compute resources are accessible via APIs for developers building cloud applications and via web interfaces for administrators and users. The compute architecture is designed to scale horizontally on standard hardware." +msgstr "" + +#: ./doc/training-guides/module001-ch003-core-projects.xml:238(title) +msgid "OpenStack Compute: Provision and manage large networks of virtual machines" +msgstr "" + +#: ./doc/training-guides/module001-ch003-core-projects.xml:246(para) +msgid "OpenStack Compute (Nova) is a cloud computing fabric controller (the main part of an IaaS system). It is written in Python and uses many external libraries such as Eventlet (for concurrent programming), Kombu (for AMQP communication), and SQLAlchemy (for database access). Nova's architecture is designed to scale horizontally on standard hardware with no proprietary hardware or software requirements and provide the ability to integrate with legacy systems and third party technologies. It is designed to manage and automate pools of computer resources and can work with widely available virtualization technologies, as well as bare metal and high-performance computing (HPC) configurations. KVM and XenServer are available choices for hypervisor technology, together with Hyper-V and Linux container technology such as LXC. In addition to different hypervisors, OpenStack runs on ARM." +msgstr "" + +#: ./doc/training-guides/module001-ch003-core-projects.xml:262(emphasis) +msgid "Popular Use Cases:" +msgstr "" + +#: ./doc/training-guides/module001-ch003-core-projects.xml:265(para) +msgid "Service providers offering an IaaS compute platform or services higher up the stack" +msgstr "" + +#: ./doc/training-guides/module001-ch003-core-projects.xml:269(para) +msgid "IT departments acting as cloud service providers for business units and project teams" +msgstr "" + +#: ./doc/training-guides/module001-ch003-core-projects.xml:273(para) +msgid "Processing big data with tools like Hadoop" +msgstr "" + +#: ./doc/training-guides/module001-ch003-core-projects.xml:276(para) +msgid "Scaling compute up and down to meet demand for web resources and applications" +msgstr "" + +#: ./doc/training-guides/module001-ch003-core-projects.xml:280(para) +msgid "High-performance computing (HPC) environments processing diverse and intensive workloads" +msgstr "" + +#: ./doc/training-guides/module001-ch003-core-projects.xml:284(guisubmenu) ./doc/training-guides/module003-ch003-obj-store-capabilities.xml:86(title) +msgid "Object Storage(Swift)" +msgstr "" + +#: ./doc/training-guides/module001-ch003-core-projects.xml:285(para) +msgid "In addition to traditional enterprise-class storage technology, many organizations now have a variety of storage needs with varying performance and price requirements. OpenStack has support for both Object Storage and Block Storage, with many deployment options for each depending on the use case." +msgstr "" + +#: ./doc/training-guides/module001-ch003-core-projects.xml:292(title) +msgid "OpenStack Storage: Object and Block storage for use with servers and applications" +msgstr "" + +#: ./doc/training-guides/module001-ch003-core-projects.xml:300(para) +msgid "OpenStack Object Storage (Swift) is a scalable redundant storage system. Objects and files are written to multiple disk drives spread throughout servers in the data center, with the OpenStack software responsible for ensuring data replication and integrity across the cluster. Storage clusters scale horizontally simply by adding new servers. Should a server or hard drive fail, OpenStack replicates its content from other active nodes to new locations in the cluster. Because OpenStack uses software logic to ensure data replication and distribution across different devices, inexpensive commodity hard drives and servers can be used." +msgstr "" + +#: ./doc/training-guides/module001-ch003-core-projects.xml:311(para) ./doc/training-guides/module003-ch001-intro-objstore.xml:24(para) +msgid "Object Storage is ideal for cost effective, scale-out storage. It provides a fully distributed, API-accessible storage platform that can be integrated directly into applications or used for backup, archiving and data retention. Block Storage allows block devices to be exposed and connected to compute instances for expanded storage, better performance and integration with enterprise storage platforms, such as NetApp, Nexenta and SolidFire." +msgstr "" + +#: ./doc/training-guides/module001-ch003-core-projects.xml:319(para) +msgid "A few details on OpenStack’s Object Storage" +msgstr "" + +#: ./doc/training-guides/module001-ch003-core-projects.xml:322(para) ./doc/training-guides/module003-ch003-obj-store-capabilities.xml:10(para) +msgid "OpenStack provides redundant, scalable object storage using clusters of standardized servers capable of storing petabytes of data" +msgstr "" + +#: ./doc/training-guides/module001-ch003-core-projects.xml:327(para) ./doc/training-guides/module003-ch003-obj-store-capabilities.xml:15(para) +msgid "Object Storage is not a traditional file system, but rather a distributed storage system for static data such as virtual machine images, photo storage, email storage, backups and archives. Having no central \"brain\" or master point of control provides greater scalability, redundancy and durability." +msgstr "" + +#: ./doc/training-guides/module001-ch003-core-projects.xml:335(para) ./doc/training-guides/module003-ch003-obj-store-capabilities.xml:23(para) +msgid "Objects and files are written to multiple disk drives spread throughout servers in the data center, with the OpenStack software responsible for ensuring data replication and integrity across the cluster." +msgstr "" + +#: ./doc/training-guides/module001-ch003-core-projects.xml:341(para) ./doc/training-guides/module003-ch003-obj-store-capabilities.xml:30(para) +msgid "Storage clusters scale horizontally simply by adding new servers. Should a server or hard drive fail, OpenStack replicates its content from other active nodes to new locations in the cluster. Because OpenStack uses software logic to ensure data replication and distribution across different devices, inexpensive commodity hard drives and servers can be used in lieu of more expensive equipment." +msgstr "" + +#: ./doc/training-guides/module001-ch003-core-projects.xml:351(guisubmenu) +msgid "Block Storage(Cinder)" +msgstr "" + +#: ./doc/training-guides/module001-ch003-core-projects.xml:352(para) +msgid "OpenStack Block Storage (Cinder) provides persistent block level storage devices for use with OpenStack compute instances. The block storage system manages the creation, attaching and detaching of the block devices to servers. Block storage volumes are fully integrated into OpenStack Compute and the Dashboard allowing for cloud users to manage their own storage needs. In addition to local Linux server storage, it can use storage platforms including Ceph, CloudByte, Coraid, EMC (VMAX and VNX), GlusterFS, IBM Storage (Storwize family, SAN Volume Controller, and XIV Storage System), Linux LIO, NetApp, Nexenta, Scality, SolidFire and HP (Store Virtual and StoreServ 3Par families). Block storage is appropriate for performance sensitive scenarios such as database storage, expandable file systems, or providing a server with access to raw block level storage. Snapshot management provides powerful functionality for backing up data stored on block storage volumes. Snapshots can be restored or used to create a new block storage volume." +msgstr "" + +#: ./doc/training-guides/module001-ch003-core-projects.xml:370(emphasis) +msgid "A few points on OpenStack Block Storage:" +msgstr "" + +#: ./doc/training-guides/module001-ch003-core-projects.xml:403(guisubmenu) +msgid "Networking(Neutron)" +msgstr "" + +#: ./doc/training-guides/module001-ch003-core-projects.xml:404(para) +msgid "Today's data center networks contain more devices than ever before. From servers, network equipment, storage systems and security appliances, many of which are further divided into virtual machines and virtual networks. The number of IP addresses, routing configurations and security rules can quickly grow into the millions. Traditional network management techniques fall short of providing a truly scalable, automated approach to managing these next-generation networks. At the same time, users expect more control and flexibility with quicker provisioning." +msgstr "" + +#: ./doc/training-guides/module001-ch003-core-projects.xml:413(para) +msgid "OpenStack Networking is a pluggable, scalable and API-driven system for managing networks and IP addresses. Like other aspects of the cloud operating system, it can be used by administrators and users to increase the value of existing data center assets. OpenStack Networking ensures the network will not be the bottleneck or limiting factor in a cloud deployment and gives users real self-service, even over their network configurations." +msgstr "" + +#: ./doc/training-guides/module001-ch003-core-projects.xml:422(title) +msgid "OpenStack Networking: Pluggable, scalable, API-driven network and IP management" +msgstr "" + +#: ./doc/training-guides/module001-ch003-core-projects.xml:430(para) +msgid "OpenStack Networking (Neutron, formerly Quantum]) is a system for managing networks and IP addresses. Like other aspects of the cloud operating system, it can be used by administrators and users to increase the value of existing data center assets. OpenStack Networking ensures the network will not be the bottleneck or limiting factor in a cloud deployment and gives users real self-service, even over their network configurations." +msgstr "" + +#: ./doc/training-guides/module001-ch003-core-projects.xml:438(para) +msgid "OpenStack Neutron provides networking models for different applications or user groups. Standard models include flat networks or VLANs for separation of servers and traffic. OpenStack Networking manages IP addresses, allowing for dedicated static IPs or DHCP. Floating IPs allow traffic to be dynamically re routed to any of your compute resources, which allows you to redirect traffic during maintenance or in the case of failure. Users can create their own networks, control traffic and connect servers and devices to one or more networks. Administrators can take advantage of software-defined networking (SDN) technology like OpenFlow to allow for high levels of multi-tenancy and massive scale. OpenStack Networking has an extension framework allowing additional network services, such as intrusion detection systems (IDS), load balancing, firewalls and virtual private networks (VPN) to be deployed and managed." +msgstr "" + +#: ./doc/training-guides/module001-ch003-core-projects.xml:454(para) +msgid "Networking Capabilities" +msgstr "" + +#: ./doc/training-guides/module001-ch003-core-projects.xml:457(para) +msgid "OpenStack provides flexible networking models to suit the needs of different applications or user groups. Standard models include flat networks or VLANs for separation of servers and traffic." +msgstr "" + +#: ./doc/training-guides/module001-ch003-core-projects.xml:463(para) +msgid "OpenStack Networking manages IP addresses, allowing for dedicated static IPs or DHCP. Floating IPs allow traffic to be dynamically rerouted to any of your compute resources, which allows you to redirect traffic during maintenance or in the case of failure." +msgstr "" + +#: ./doc/training-guides/module001-ch003-core-projects.xml:470(para) +msgid "Users can create their own networks, control traffic and connect servers and devices to one or more networks." +msgstr "" + +#: ./doc/training-guides/module001-ch003-core-projects.xml:475(para) +msgid "The pluggable backend architecture lets users take advantage of commodity gear or advanced networking services from supported vendors." +msgstr "" + +#: ./doc/training-guides/module001-ch003-core-projects.xml:480(para) +msgid "Administrators can take advantage of software-defined networking (SDN) technology like OpenFlow to allow for high levels of multi-tenancy and massive scale." +msgstr "" + +#: ./doc/training-guides/module001-ch003-core-projects.xml:486(para) +msgid "OpenStack Networking has an extension framework allowing additional network services, such as intrusion detection systems (IDS), load balancing, firewalls and virtual private networks (VPN) to be deployed and managed." +msgstr "" + +#: ./doc/training-guides/module001-ch003-core-projects.xml:493(guisubmenu) +msgid "Dashboard(Horizon)" +msgstr "" + +#: ./doc/training-guides/module001-ch003-core-projects.xml:494(para) +msgid "OpenStack Dashboard (Horizon) provides administrators and users a graphical interface to access, provision and automate cloud-based resources. The design allows for third party products and services, such as billing, monitoring and additional management tools. Service providers and other commercial vendors can customize the dashboard with their own brand." +msgstr "" + +#: ./doc/training-guides/module001-ch003-core-projects.xml:500(para) +msgid "The dashboard is just one way to interact with OpenStack resources. Developers can automate access or build tools to manage their resources using the native OpenStack API or the EC2 compatibility API." +msgstr "" + +#: ./doc/training-guides/module001-ch003-core-projects.xml:504(guisubmenu) +msgid "Identity Service(Keystone)" +msgstr "" + +#: ./doc/training-guides/module001-ch003-core-projects.xml:505(para) +msgid "OpenStack Identity (Keystone) provides a central directory of users mapped to the OpenStack services they can access. It acts as a common authentication system across the cloud operating system and can integrate with existing backend directory services like LDAP. It supports multiple forms of authentication including standard username and password credentials, token-based systems and AWS-style (i.e. Amazon Web Services) logins. Additionally, the catalog provides a query-able list of all of the services deployed in an OpenStack cloud in a single registry. Users and third-party tools can programmatically determine which resources they can access." +msgstr "" + +#: ./doc/training-guides/module001-ch003-core-projects.xml:516(para) +msgid "Additionally, the catalog provides a query-able list of all of the services deployed in an OpenStack cloud in a single registry. Users and third-party tools can programmatically determine which resources they can access." +msgstr "" + +#: ./doc/training-guides/module001-ch003-core-projects.xml:520(para) +msgid "The OpenStack Identity Service enables administrators to:" +msgstr "" + +#: ./doc/training-guides/module001-ch003-core-projects.xml:524(para) +msgid "Configure centralized policies across users and systems" +msgstr "" + +#: ./doc/training-guides/module001-ch003-core-projects.xml:528(para) +msgid "Create users and tenants and define permissions for compute, storage, and networking resources by using role-based access control (RBAC) features" +msgstr "" + +#: ./doc/training-guides/module001-ch003-core-projects.xml:533(para) +msgid "Integrate with an existing directory, like LDAP, to provide a single source of authentication across the enterprise" +msgstr "" + +#: ./doc/training-guides/module001-ch003-core-projects.xml:538(para) +msgid "The OpenStack Identity Service enables users to:" +msgstr "" + +#: ./doc/training-guides/module001-ch003-core-projects.xml:541(para) +msgid "List the services to which they have access" +msgstr "" + +#: ./doc/training-guides/module001-ch003-core-projects.xml:544(para) +msgid "Make API requests" +msgstr "" + +#: ./doc/training-guides/module001-ch003-core-projects.xml:547(para) +msgid "Log into the web dashboard to create resources owned by their account" +msgstr "" + +#: ./doc/training-guides/module001-ch003-core-projects.xml:551(guisubmenu) +msgid "Image Service(Glance)" +msgstr "" + +#: ./doc/training-guides/module001-ch003-core-projects.xml:552(para) +msgid "OpenStack Image Service (Glance) provides discovery, registration and delivery services for disk and server images. Stored images can be used as a template. It can also be used to store and catalog an unlimited number of backups. The Image Service can store disk and server images in a variety of back-ends, including OpenStack Object Storage. The Image Service API provides a standard REST interface for querying information about disk images and lets clients stream the images to new servers." +msgstr "" + +#: ./doc/training-guides/module001-ch003-core-projects.xml:561(para) +msgid "The Image Service can store disk and server images in a variety of back-ends, including OpenStack Object Storage. The Image Service API provides a standard REST interface for querying information about disk images and lets clients stream the images to new servers." +msgstr "" + +#: ./doc/training-guides/module001-ch003-core-projects.xml:566(para) +msgid "Capabilities of the Image Service include:" +msgstr "" + +#: ./doc/training-guides/module001-ch003-core-projects.xml:569(para) +msgid "Administrators can create base templates from which their users can start new compute instances" +msgstr "" + +#: ./doc/training-guides/module001-ch003-core-projects.xml:573(para) +msgid "Users can choose from available images, or create their own from existing servers" +msgstr "" + +#: ./doc/training-guides/module001-ch003-core-projects.xml:577(para) +msgid "Snapshots can also be stored in the Image Service so that virtual machines can be backed up quickly" +msgstr "" + +#: ./doc/training-guides/module001-ch003-core-projects.xml:581(para) +msgid "A multi-format image registry, the image service allows uploads of private and public images in a variety of formats, including:" +msgstr "" + +#: ./doc/training-guides/module001-ch003-core-projects.xml:586(para) +msgid "Raw" +msgstr "" + +#: ./doc/training-guides/module001-ch003-core-projects.xml:589(para) +msgid "Machine (kernel/ramdisk outside of image, also known as AMI)" +msgstr "" + +#: ./doc/training-guides/module001-ch003-core-projects.xml:593(para) +msgid "VHD (Hyper-V)" +msgstr "" + +#: ./doc/training-guides/module001-ch003-core-projects.xml:596(para) +msgid "VDI (VirtualBox)" +msgstr "" + +#: ./doc/training-guides/module001-ch003-core-projects.xml:599(para) +msgid "qcow2 (Qemu/KVM)" +msgstr "" + +#: ./doc/training-guides/module001-ch003-core-projects.xml:602(para) +msgid "VMDK (VMWare)" +msgstr "" + +#: ./doc/training-guides/module001-ch003-core-projects.xml:605(para) +msgid "OVF (VMWare, others)" +msgstr "" + +#: ./doc/training-guides/module001-ch003-core-projects.xml:608(para) +msgid "To checkout the complete list of Core and Incubated projects under OpenStack check out OpenStack’s Launchpad Project Page here : http://goo.gl/ka4SrV" +msgstr "" + +#: ./doc/training-guides/module001-ch003-core-projects.xml:611(guisubmenu) +msgid "Amazon Web Services compatibility" +msgstr "" + +#: ./doc/training-guides/module001-ch003-core-projects.xml:612(para) +msgid "OpenStack APIs are compatible with Amazon EC2 and Amazon S3 and thus client applications written for Amazon Web Services can be used with OpenStack with minimal porting effort." +msgstr "" + +#: ./doc/training-guides/module001-ch003-core-projects.xml:616(guilabel) +msgid "Governance" +msgstr "" + +#: ./doc/training-guides/module001-ch003-core-projects.xml:617(para) +msgid "OpenStack is governed by a non-profit foundation and its board of directors, a technical committee and a user committee." +msgstr "" + +#: ./doc/training-guides/module001-ch003-core-projects.xml:620(para) +msgid "The foundation's stated mission is by providing shared resources to help achieve the OpenStack Mission by Protecting, Empowering, and Promoting OpenStack software and the community around it, including users, developers and the entire ecosystem. Though, it has little to do with the development of the software, which is managed by the technical committee - an elected group that represents the contributors to the project, and has oversight on all technical matters." +msgstr "" + +#: ./doc/training-guides/card009.xml:6(title) +msgid "Install Ubuntu" +msgstr "" + +#: ./doc/training-guides/module003-ch000-openstack-objstore.xml:9(title) +msgid "OpenStack Object Storage" +msgstr "" + +#: ./doc/training-guides/card043-ovs-in-network-node.xml:7(title) +msgid "OVS Installation and Configuration in Network node" +msgstr "" + +#: ./doc/training-guides/module003-ch008-account-reaper.xml:7(title) +msgid "Account Reaper" +msgstr "" + +#: ./doc/training-guides/module003-ch008-account-reaper.xml:8(para) +msgid "The Account Reaper removes data from deleted accounts in the background." +msgstr "" + +#: ./doc/training-guides/module003-ch008-account-reaper.xml:10(para) +msgid "An account is marked for deletion by a reseller issuing a DELETE request on the account’s storage URL. This simply puts the value DELETED into the status column of the account_stat table in the account database (and replicas), indicating the data for the account should be deleted later." +msgstr "" + +#: ./doc/training-guides/module003-ch008-account-reaper.xml:15(para) +msgid "There is normally no set retention time and no undelete; it is assumed the reseller will implement such features and only call DELETE on the account once it is truly desired the account’s data be removed. However, in order to protect the Swift cluster accounts from an improper or mistaken delete request, you can set a delay_reaping value in the [account-reaper] section of the account-server.conf to delay the actual deletion of data. At this time, there is no utility to undelete an account; one would have to update the account database replicas directly, setting the status column to an empty string and updating the put_timestamp to be greater than the delete_timestamp. (On the TODO list is writing a utility to perform this task, preferably through a ReST call.)" +msgstr "" + +#: ./doc/training-guides/module003-ch008-account-reaper.xml:28(para) +msgid "The account reaper runs on each account server and scans the server occasionally for account databases marked for deletion. It will only trigger on accounts that server is the primary node for, so that multiple account servers aren’t all trying to do the same work at the same time. Using multiple servers to delete one account might improve deletion speed, but requires coordination so they aren’t duplicating effort. Speed really isn’t as much of a concern with data deletion and large accounts aren’t deleted that often." +msgstr "" + +#: ./doc/training-guides/module003-ch008-account-reaper.xml:37(para) +msgid "The deletion process for an account itself is pretty straightforward. For each container in the account, each object is deleted and then the container is deleted. Any deletion requests that fail won’t stop the overall process, but will cause the overall process to fail eventually (for example, if an object delete times out, the container won’t be able to be deleted later and therefore the account won’t be deleted either). The overall process continues even on a failure so that it doesn’t get hung up reclaiming cluster space because of one troublesome spot. The account reaper will keep trying to delete an account until it eventually becomes empty, at which point the database reclaim process within the db_replicator will eventually remove the database files." +msgstr "" + +#: ./doc/training-guides/module003-ch008-account-reaper.xml:51(para) +msgid "Sometimes a persistent error state can prevent some object or container from being deleted. If this happens, you will see a message such as “Account <name> has not been reaped since <date>” in the log. You can control when this is logged with the reap_warn_after value in the [account-reaper] section of the account-server.conf file. By default this is 30 days." +msgstr "" + +#: ./doc/training-guides/bk002-ch010-operator-network-node.xml:10(title) +msgid "Days 7 to 8, 09:00 to 11:00, 11:15 to 12:30" +msgstr "" + +#: ./doc/training-guides/bk002-ch010-operator-network-node.xml:14(title) +msgid "Review Associate Networking in OpenStack" +msgstr "" + +#: ./doc/training-guides/bk002-ch010-operator-network-node.xml:21(title) +msgid "Review Associate OpenStack Networking Concepts" +msgstr "" + +#: ./doc/training-guides/bk002-ch010-operator-network-node.xml:28(title) ./doc/training-guides/bk002-ch004-operator-controller-node.xml:35(title) ./doc/training-guides/bk002-ch007-operator-compute-node.xml:35(title) ./doc/training-guides/bk002-ch013-operator-object-storage-node.xml:28(title) +msgid "Review Associate Administration Tasks" +msgstr "" + +#. When image changes, this message will be marked fuzzy or untranslated for you. +#. It doesn't matter what you translate it to: it's not used at all. +#: ./doc/training-guides/module001-ch006-overview-horizon-cli.xml:107(None) ./doc/training-guides/module001-ch006-overview-horizon-cli.xml:727(None) +msgid "@@image: 'figures/image14.png'; md5=b3fcef10808f967f7e87f98d096bf2f9" +msgstr "" + +#. When image changes, this message will be marked fuzzy or untranslated for you. +#. It doesn't matter what you translate it to: it's not used at all. +#: ./doc/training-guides/module001-ch006-overview-horizon-cli.xml:195(None) +msgid "@@image: 'figures/image25.png'; md5=4c70d08fd2a0aedc8342ab61d3c62a94" +msgstr "" + +#. When image changes, this message will be marked fuzzy or untranslated for you. +#. It doesn't matter what you translate it to: it's not used at all. +#: ./doc/training-guides/module001-ch006-overview-horizon-cli.xml:212(None) +msgid "@@image: 'figures/image15.png'; md5=0e003df4e8edbde4ac9c11165d897e84" +msgstr "" + +#. When image changes, this message will be marked fuzzy or untranslated for you. +#. It doesn't matter what you translate it to: it's not used at all. +#: ./doc/training-guides/module001-ch006-overview-horizon-cli.xml:638(None) +msgid "@@image: 'figures/image00.png'; md5=6b0f5cb3009d447334ff8b5c5b2cd121" +msgstr "" + +#. When image changes, this message will be marked fuzzy or untranslated for you. +#. It doesn't matter what you translate it to: it's not used at all. +#: ./doc/training-guides/module001-ch006-overview-horizon-cli.xml:716(None) +msgid "@@image: 'figures/image30.png'; md5=d9eef0f7a1f99eee18a99e677c7c710b" +msgstr "" + +#: ./doc/training-guides/module001-ch006-overview-horizon-cli.xml:8(guilabel) +msgid "How can I use an OpenStack cloud?" +msgstr "" + +#: ./doc/training-guides/module001-ch006-overview-horizon-cli.xml:9(para) +msgid "As an OpenStack cloud end user, you can provision your own resources within the limits set by administrators. The examples in this guide show you how to complete these tasks by using the OpenStack dashboard and command-line clients. The dashboard, also known as horizon, is a Web-based graphical interface. The command-line clients let you run simple commands to create and manage resources in a cloud and automate tasks by using scripts. Each of the core OpenStack projects has its own command-line client." +msgstr "" + +#: ./doc/training-guides/module001-ch006-overview-horizon-cli.xml:18(para) +msgid "You can modify these examples for your specific use cases." +msgstr "" + +#: ./doc/training-guides/module001-ch006-overview-horizon-cli.xml:20(para) +msgid "In addition to these ways of interacting with a cloud, you can access the OpenStack APIs indirectly through cURLcommands or open SDKs, or directly through the APIs. You can automate access or build tools to manage resources and services by using the native OpenStack APIs or the EC2 compatibility API." +msgstr "" + +#: ./doc/training-guides/module001-ch006-overview-horizon-cli.xml:25(para) +msgid "To use the OpenStack APIs, it helps to be familiar with HTTP/1.1, RESTful web services, the OpenStack services, and JSON or XML data serialization formats." +msgstr "" + +#: ./doc/training-guides/module001-ch006-overview-horizon-cli.xml:28(guilabel) +msgid "OpenStack dashboard" +msgstr "" + +#: ./doc/training-guides/module001-ch006-overview-horizon-cli.xml:29(para) +msgid "As a cloud end user, the OpenStack dashboard lets you to provision your own resources within the limits set by administrators. You can modify these examples to create other types and sizes of server instances." +msgstr "" + +#: ./doc/training-guides/module001-ch006-overview-horizon-cli.xml:33(guilabel) ./doc/training-guides/module001-ch006-overview-horizon-cli.xml:121(emphasis) ./doc/training-guides/module001-ch006-overview-horizon-cli.xml:869(guilabel) ./doc/training-guides/bk002-ch001-operator-getting-started.xml:12(title) ./doc/training-guides/bk001-ch001-associate-getting-started.xml:12(title) +msgid "Overview" +msgstr "" + +#: ./doc/training-guides/module001-ch006-overview-horizon-cli.xml:34(para) +msgid "The following requirements must be fulfilled to access the OpenStack dashboard:" +msgstr "" + +#: ./doc/training-guides/module001-ch006-overview-horizon-cli.xml:38(para) +msgid "The cloud operator has set up an OpenStack cloud." +msgstr "" + +#: ./doc/training-guides/module001-ch006-overview-horizon-cli.xml:42(para) +msgid "You have a recent Web browser that supports HTML5. It must have cookies and JavaScript enabled. To use the VNC client for the dashboard, which is based on noVNC, your browser must support HTML5 Canvas and HTML5 WebSockets. For more details and a list of browsers that support noVNC, seehttps://github.com/kanaka/noVNC/blob/master/README.md, andhttps://github.com/kanaka/noVNC/wiki/Browser-support, respectively." +msgstr "" + +#: ./doc/training-guides/module001-ch006-overview-horizon-cli.xml:60(para) +msgid "Learn how to log in to the dashboard and get a short overview of the interface." +msgstr "" + +#: ./doc/training-guides/module001-ch006-overview-horizon-cli.xml:62(guilabel) +msgid "Log in to the dashboard" +msgstr "" + +#: ./doc/training-guides/module001-ch006-overview-horizon-cli.xml:63(para) +msgid "To log in to the dashboard" +msgstr "" + +#: ./doc/training-guides/module001-ch006-overview-horizon-cli.xml:66(para) +msgid "Ask your cloud operator for the following information:" +msgstr "" + +#: ./doc/training-guides/module001-ch006-overview-horizon-cli.xml:72(para) +msgid "The hostname or public IP address from which you can access the dashboard." +msgstr "" + +#: ./doc/training-guides/module001-ch006-overview-horizon-cli.xml:76(para) +msgid "The dashboard is available on the node that has the nova-dashboard server role." +msgstr "" + +#: ./doc/training-guides/module001-ch006-overview-horizon-cli.xml:80(para) +msgid "The username and password with which you can log in to the dashboard." +msgstr "" + +#: ./doc/training-guides/module001-ch006-overview-horizon-cli.xml:86(para) +msgid "Open a Web browser that supports HTML5. Make sure that JavaScript and cookies are enabled." +msgstr "" + +#: ./doc/training-guides/module001-ch006-overview-horizon-cli.xml:90(para) +msgid "As a URL, enter the host name or IP address that you got from the cloud operator." +msgstr "" + +#: ./doc/training-guides/module001-ch006-overview-horizon-cli.xml:95(link) +msgid "https://IP_ADDRESS_OR_HOSTNAME/" +msgstr "" + +#: ./doc/training-guides/module001-ch006-overview-horizon-cli.xml:98(para) +msgid "On the dashboard log in page, enter your user name and password and click Sign In." +msgstr "" + +#: ./doc/training-guides/module001-ch006-overview-horizon-cli.xml:102(para) +msgid "After you log in, the following page appears:" +msgstr "" + +#: ./doc/training-guides/module001-ch006-overview-horizon-cli.xml:104(title) +msgid "OpenStack Dashboard - Overview" +msgstr "" + +#: ./doc/training-guides/module001-ch006-overview-horizon-cli.xml:111(para) +msgid "The top-level row shows the username that you logged in with. You can also access Settingsor Sign Outof the Web interface." +msgstr "" + +#: ./doc/training-guides/module001-ch006-overview-horizon-cli.xml:114(para) +msgid "If you are logged in as an end user rather than an admin user, the main screen shows only the Projecttab." +msgstr "" + +#: ./doc/training-guides/module001-ch006-overview-horizon-cli.xml:116(guilabel) +msgid "OpenStack dashboard – Project tab" +msgstr "" + +#: ./doc/training-guides/module001-ch006-overview-horizon-cli.xml:117(para) +msgid "This tab shows details for the projects, or projects, of which you are a member." +msgstr "" + +#: ./doc/training-guides/module001-ch006-overview-horizon-cli.xml:119(para) +msgid "Select a project from the drop-down list on the left-hand side to access the following categories:" +msgstr "" + +#: ./doc/training-guides/module001-ch006-overview-horizon-cli.xml:122(para) +msgid "Shows basic reports on the project." +msgstr "" + +#: ./doc/training-guides/module001-ch006-overview-horizon-cli.xml:123(emphasis) +msgid "Instances" +msgstr "" + +#: ./doc/training-guides/module001-ch006-overview-horizon-cli.xml:124(para) +msgid "Lists instances and volumes created by users of the project." +msgstr "" + +#: ./doc/training-guides/module001-ch006-overview-horizon-cli.xml:126(para) +msgid "From here, you can stop, pause, or reboot any instances or connect to them through virtual network computing (VNC)." +msgstr "" + +#: ./doc/training-guides/module001-ch006-overview-horizon-cli.xml:130(para) +msgid "Lists volumes created by users of the project." +msgstr "" + +#: ./doc/training-guides/module001-ch006-overview-horizon-cli.xml:131(para) +msgid "From here, you can create or delete volumes." +msgstr "" + +#: ./doc/training-guides/module001-ch006-overview-horizon-cli.xml:132(emphasis) +msgid "Images & Snapshots" +msgstr "" + +#: ./doc/training-guides/module001-ch006-overview-horizon-cli.xml:134(para) +msgid "Lists images and snapshots created by users of the project, plus any images that are publicly available. Includes volume snapshots. From here, you can create and delete images and snapshots, and launch instances from images and snapshots." +msgstr "" + +#: ./doc/training-guides/module001-ch006-overview-horizon-cli.xml:139(emphasis) +msgid "Access & Security" +msgstr "" + +#: ./doc/training-guides/module001-ch006-overview-horizon-cli.xml:141(para) +msgid "On the Security Groupstab, you can list, create, and delete security groups and edit rules for security groups." +msgstr "" + +#: ./doc/training-guides/module001-ch006-overview-horizon-cli.xml:144(para) +msgid "On the Keypairstab, you can list, create, and import keypairs, and delete keypairs." +msgstr "" + +#: ./doc/training-guides/module001-ch006-overview-horizon-cli.xml:146(para) +msgid "On the Floating IPstab, you can allocate an IP address to or release it from a project." +msgstr "" + +#: ./doc/training-guides/module001-ch006-overview-horizon-cli.xml:149(para) +msgid "On the API Accesstab, you can list the API endpoints." +msgstr "" + +#: ./doc/training-guides/module001-ch006-overview-horizon-cli.xml:151(guilabel) ./doc/training-guides/module001-ch006-overview-horizon-cli.xml:1073(guilabel) +msgid "Manage images" +msgstr "" + +#: ./doc/training-guides/module001-ch006-overview-horizon-cli.xml:152(para) +msgid "During setup of OpenStack cloud, the cloud operator sets user permissions to manage images. Image upload and management might be restricted to only cloud administrators or cloud operators. Though you can complete most tasks with the OpenStack dashboard, you can manage images through only the glance and nova clients or the Image Service and Compute APIs." +msgstr "" + +#: ./doc/training-guides/module001-ch006-overview-horizon-cli.xml:158(guilabel) +msgid "Set up access and security" +msgstr "" + +#: ./doc/training-guides/module001-ch006-overview-horizon-cli.xml:159(para) +msgid "Before you launch a virtual machine, you can add security group rules to enable users to ping and SSH to the instances. To do so, you either add rules to the default security group or add a security group with rules. For information, seethe section called “Add security group rules”." +msgstr "" + +#: ./doc/training-guides/module001-ch006-overview-horizon-cli.xml:165(para) +msgid "Keypairs are SSH credentials that are injected into images when they are launched. For this to work, the image must contain the cloud-init package. For information, seethe section called “Add keypairs”." +msgstr "" + +#: ./doc/training-guides/module001-ch006-overview-horizon-cli.xml:170(guilabel) +msgid "Add security group rules" +msgstr "" + +#: ./doc/training-guides/module001-ch006-overview-horizon-cli.xml:171(para) +msgid "The following procedure shows you how to add rules to the default security group." +msgstr "" + +#: ./doc/training-guides/module001-ch006-overview-horizon-cli.xml:173(para) +msgid "To add rules to the default security group" +msgstr "" + +#: ./doc/training-guides/module001-ch006-overview-horizon-cli.xml:176(para) ./doc/training-guides/module001-ch006-overview-horizon-cli.xml:295(para) ./doc/training-guides/module001-ch006-overview-horizon-cli.xml:388(para) ./doc/training-guides/module001-ch006-overview-horizon-cli.xml:645(para) ./doc/training-guides/module001-ch006-overview-horizon-cli.xml:684(para) ./doc/training-guides/module001-ch006-overview-horizon-cli.xml:761(para) ./doc/training-guides/module001-ch006-overview-horizon-cli.xml:1023(para) +msgid "Log in to the OpenStack dashboard." +msgstr "" + +#: ./doc/training-guides/module001-ch006-overview-horizon-cli.xml:179(para) ./doc/training-guides/module001-ch006-overview-horizon-cli.xml:298(para) ./doc/training-guides/module001-ch006-overview-horizon-cli.xml:391(para) ./doc/training-guides/module001-ch006-overview-horizon-cli.xml:648(para) ./doc/training-guides/module001-ch006-overview-horizon-cli.xml:687(para) ./doc/training-guides/module001-ch006-overview-horizon-cli.xml:737(para) +msgid "If you are a member of multiple projects, select a project from the drop-down list at the top of the Projecttab." +msgstr "" + +#: ./doc/training-guides/module001-ch006-overview-horizon-cli.xml:184(para) ./doc/training-guides/module001-ch006-overview-horizon-cli.xml:303(para) +msgid "Click the Access & Securitycategory." +msgstr "" + +#: ./doc/training-guides/module001-ch006-overview-horizon-cli.xml:187(para) +msgid "The dashboard shows the security groups that are available for this project." +msgstr "" + +#: ./doc/training-guides/module001-ch006-overview-horizon-cli.xml:192(title) +msgid "OpenStack Dashboard - Security Groups" +msgstr "" + +#: ./doc/training-guides/module001-ch006-overview-horizon-cli.xml:201(para) +msgid "Select the default security group and click Edit Rules." +msgstr "" + +#: ./doc/training-guides/module001-ch006-overview-horizon-cli.xml:205(para) +msgid "The Security Group Rulespage appears:" +msgstr "" + +#: ./doc/training-guides/module001-ch006-overview-horizon-cli.xml:209(title) +msgid "OpenStack Dashboard - Security Group Rules" +msgstr "" + +#: ./doc/training-guides/module001-ch006-overview-horizon-cli.xml:218(para) +msgid "Add a TCP rule" +msgstr "" + +#: ./doc/training-guides/module001-ch006-overview-horizon-cli.xml:221(para) ./doc/training-guides/module001-ch006-overview-horizon-cli.xml:261(para) +msgid "Click Add Rule." +msgstr "" + +#: ./doc/training-guides/module001-ch006-overview-horizon-cli.xml:224(para) ./doc/training-guides/module001-ch006-overview-horizon-cli.xml:264(para) +msgid "The Add Rulewindow appears." +msgstr "" + +#: ./doc/training-guides/module001-ch006-overview-horizon-cli.xml:229(para) +msgid "In the IP Protocollist, select TCP." +msgstr "" + +#: ./doc/training-guides/module001-ch006-overview-horizon-cli.xml:232(para) +msgid "In the Openlist, select Port." +msgstr "" + +#: ./doc/training-guides/module001-ch006-overview-horizon-cli.xml:235(para) +msgid "In the Portbox, enter 22." +msgstr "" + +#: ./doc/training-guides/module001-ch006-overview-horizon-cli.xml:238(para) ./doc/training-guides/module001-ch006-overview-horizon-cli.xml:278(para) +msgid "In the Sourcelist, select CIDR." +msgstr "" + +#: ./doc/training-guides/module001-ch006-overview-horizon-cli.xml:241(para) ./doc/training-guides/module001-ch006-overview-horizon-cli.xml:281(para) +msgid "In the CIDRbox, enter 0.0.0.0/0." +msgstr "" + +#: ./doc/training-guides/module001-ch006-overview-horizon-cli.xml:244(para) ./doc/training-guides/module001-ch006-overview-horizon-cli.xml:284(para) +msgid "Click Add." +msgstr "" + +#: ./doc/training-guides/module001-ch006-overview-horizon-cli.xml:247(para) +msgid "Port 22 is now open for requests from any IP address." +msgstr "" + +#: ./doc/training-guides/module001-ch006-overview-horizon-cli.xml:251(para) +msgid "If you want to accept requests from a particular range of IP addresses, specify the IP address block in the CIDRbox." +msgstr "" + +#: ./doc/training-guides/module001-ch006-overview-horizon-cli.xml:258(para) +msgid "Add an ICMP rule" +msgstr "" + +#: ./doc/training-guides/module001-ch006-overview-horizon-cli.xml:269(para) +msgid "In the IP Protocollist, select ICMP." +msgstr "" + +#: ./doc/training-guides/module001-ch006-overview-horizon-cli.xml:272(para) +msgid "In the Typebox, enter -1." +msgstr "" + +#: ./doc/training-guides/module001-ch006-overview-horizon-cli.xml:275(para) +msgid "In the Codebox, enter -1." +msgstr "" + +#: ./doc/training-guides/module001-ch006-overview-horizon-cli.xml:287(guilabel) +msgid "Add keypairs" +msgstr "" + +#: ./doc/training-guides/module001-ch006-overview-horizon-cli.xml:288(para) +msgid "Create at least one keypair for each project. If you have generated a keypair with an external tool, you can import it into OpenStack. The keypair can be used for multiple instances that belong to a project." +msgstr "" + +#: ./doc/training-guides/module001-ch006-overview-horizon-cli.xml:292(para) ./doc/training-guides/module001-ch006-overview-horizon-cli.xml:310(para) +msgid "To add a keypair" +msgstr "" + +#: ./doc/training-guides/module001-ch006-overview-horizon-cli.xml:306(para) +msgid "Click the Keypairstab. The dashboard shows the keypairs that are available for this project." +msgstr "" + +#: ./doc/training-guides/module001-ch006-overview-horizon-cli.xml:313(para) ./doc/training-guides/module001-ch006-overview-horizon-cli.xml:325(para) +msgid "Click Create Keypair." +msgstr "" + +#: ./doc/training-guides/module001-ch006-overview-horizon-cli.xml:316(para) +msgid "The Create Keypairwindow appears." +msgstr "" + +#: ./doc/training-guides/module001-ch006-overview-horizon-cli.xml:321(para) +msgid "In the Keypair Namebox, enter a name for your keypair." +msgstr "" + +#: ./doc/training-guides/module001-ch006-overview-horizon-cli.xml:328(para) +msgid "Respond to the prompt to download the keypair." +msgstr "" + +#: ./doc/training-guides/module001-ch006-overview-horizon-cli.xml:333(para) +msgid "To import a keypair" +msgstr "" + +#: ./doc/training-guides/module001-ch006-overview-horizon-cli.xml:336(para) ./doc/training-guides/module001-ch006-overview-horizon-cli.xml:351(para) +msgid "Click Import Keypair." +msgstr "" + +#: ./doc/training-guides/module001-ch006-overview-horizon-cli.xml:339(para) +msgid "The Import Keypairwindow appears." +msgstr "" + +#: ./doc/training-guides/module001-ch006-overview-horizon-cli.xml:344(para) +msgid "In the Keypair Namebox, enter the name of your keypair." +msgstr "" + +#: ./doc/training-guides/module001-ch006-overview-horizon-cli.xml:348(para) +msgid "In the Public Keybox, copy the public key." +msgstr "" + +#: ./doc/training-guides/module001-ch006-overview-horizon-cli.xml:356(para) +msgid "Save the *.pem file locally and change its permissions so that only you can read and write to the file:" +msgstr "" + +#: ./doc/training-guides/module001-ch006-overview-horizon-cli.xml:360(para) +msgid "$ chmod 0600 MY_PRIV_KEY.pem" +msgstr "" + +#: ./doc/training-guides/module001-ch006-overview-horizon-cli.xml:363(para) +msgid "Use the ssh-addcommand to make the keypair known to SSH:" +msgstr "" + +#: ./doc/training-guides/module001-ch006-overview-horizon-cli.xml:367(para) +msgid "$ ssh-add MY_PRIV_KEY.pem" +msgstr "" + +#: ./doc/training-guides/module001-ch006-overview-horizon-cli.xml:370(para) +msgid "The public key of the keypair is registered in the Nova database." +msgstr "" + +#: ./doc/training-guides/module001-ch006-overview-horizon-cli.xml:372(para) +msgid "The dashboard lists the keypair in the Access & Securitycategory." +msgstr "" + +#: ./doc/training-guides/module001-ch006-overview-horizon-cli.xml:374(guilabel) ./doc/training-guides/module001-ch006-overview-horizon-cli.xml:1534(guilabel) +msgid "Launch instances" +msgstr "" + +#: ./doc/training-guides/module001-ch006-overview-horizon-cli.xml:375(para) +msgid "Instances are virtual machines that run inside the cloud. You can launch an instance directly from one of the available OpenStack images or from an image that you have copied to a persistent volume. The OpenStack Image Service provides a pool of images that are accessible to members of different projects." +msgstr "" + +#: ./doc/training-guides/module001-ch006-overview-horizon-cli.xml:381(guilabel) ./doc/training-guides/module001-ch006-overview-horizon-cli.xml:1685(guilabel) +msgid "Launch an instance from an image" +msgstr "" + +#: ./doc/training-guides/module001-ch006-overview-horizon-cli.xml:382(para) +msgid "When you launch an instance from an image, OpenStack creates a local copy of the image on the respective compute node where the instance is started." +msgstr "" + +#: ./doc/training-guides/module001-ch006-overview-horizon-cli.xml:385(para) ./doc/training-guides/module001-ch006-overview-horizon-cli.xml:1688(para) +msgid "To launch an instance from an image" +msgstr "" + +#: ./doc/training-guides/module001-ch006-overview-horizon-cli.xml:396(para) +msgid "Click the Images & Snapshotcategory." +msgstr "" + +#: ./doc/training-guides/module001-ch006-overview-horizon-cli.xml:399(para) +msgid "The dashboard shows the images that have been uploaded to OpenStack Image Service and are available for this project." +msgstr "" + +#: ./doc/training-guides/module001-ch006-overview-horizon-cli.xml:404(para) +msgid "Select an image and click Launch." +msgstr "" + +#: ./doc/training-guides/module001-ch006-overview-horizon-cli.xml:407(para) +msgid "In the Launch Imagewindow, specify the following:" +msgstr "" + +#: ./doc/training-guides/module001-ch006-overview-horizon-cli.xml:413(para) +msgid "Enter an instance name to assign to the virtual machine." +msgstr "" + +#: ./doc/training-guides/module001-ch006-overview-horizon-cli.xml:417(para) +msgid "From the Flavordrop-down list, select the size of the virtual machine to launch." +msgstr "" + +#: ./doc/training-guides/module001-ch006-overview-horizon-cli.xml:421(para) +msgid "Select a keypair." +msgstr "" + +#: ./doc/training-guides/module001-ch006-overview-horizon-cli.xml:424(para) +msgid "In case an image uses a static root password or a static key set (neither is recommended), you do not need to provide a keypair to launch the instance." +msgstr "" + +#: ./doc/training-guides/module001-ch006-overview-horizon-cli.xml:429(para) +msgid "In Instance Count, enter the number of virtual machines to launch from this image." +msgstr "" + +#: ./doc/training-guides/module001-ch006-overview-horizon-cli.xml:433(para) +msgid "Activate the security groups that you want to assign to the instance." +msgstr "" + +#: ./doc/training-guides/module001-ch006-overview-horizon-cli.xml:437(para) +msgid "Security groups are a kind of cloud firewall that define which incoming network traffic should be forwarded to instances. For details, seethe section called “Add security group rules”." +msgstr "" + +#: ./doc/training-guides/module001-ch006-overview-horizon-cli.xml:445(para) +msgid "If you have not created any specific security groups, you can only assign the instance to the default security group." +msgstr "" + +#: ./doc/training-guides/module001-ch006-overview-horizon-cli.xml:450(para) +msgid "If you want to boot from volume, click the respective entry to expand its options. Set the options as described inthe section called “Launch an instance from a volume”." +msgstr "" + +#: ./doc/training-guides/module001-ch006-overview-horizon-cli.xml:462(para) +msgid "Click Launch Instance. The instance is started on any of the compute nodes in the cloud." +msgstr "" + +#: ./doc/training-guides/module001-ch006-overview-horizon-cli.xml:466(para) +msgid "After you have launched an instance, switch to the Instancescategory to view the instance name, its (private or public) IP address, size, status, task, and power state." +msgstr "" + +#: ./doc/training-guides/module001-ch006-overview-horizon-cli.xml:470(para) +msgid "Figure 5. OpenStack dashboard – Instances" +msgstr "" + +#: ./doc/training-guides/module001-ch006-overview-horizon-cli.xml:471(para) +msgid "If you did not provide a keypair, security groups, or rules so far, by default the instance can only be accessed from inside the cloud through VNC at this point. Even pinging the instance is not possible. To access the instance through a VNC console, seethe section called “Get a console to an instance”." +msgstr "" + +#: ./doc/training-guides/module001-ch006-overview-horizon-cli.xml:481(guilabel) ./doc/training-guides/module001-ch006-overview-horizon-cli.xml:1763(guilabel) +msgid "Launch an instance from a volume" +msgstr "" + +#: ./doc/training-guides/module001-ch006-overview-horizon-cli.xml:482(para) +msgid "You can launch an instance directly from an image that has been copied to a persistent volume." +msgstr "" + +#: ./doc/training-guides/module001-ch006-overview-horizon-cli.xml:484(para) +msgid "In that case, the instance is booted from the volume, which is provided by nova-volume, through iSCSI." +msgstr "" + +#: ./doc/training-guides/module001-ch006-overview-horizon-cli.xml:486(para) +msgid "For preparation details, seethe section called “Create or delete a volume”." +msgstr "" + +#: ./doc/training-guides/module001-ch006-overview-horizon-cli.xml:492(para) +msgid "To boot an instance from the volume, especially note the following steps:" +msgstr "" + +#: ./doc/training-guides/module001-ch006-overview-horizon-cli.xml:496(para) +msgid "To be able to select from which volume to boot, launch an instance from an arbitrary image. The image you select does not boot. It is replaced by the image on the volume that you choose in the next steps." +msgstr "" + +#: ./doc/training-guides/module001-ch006-overview-horizon-cli.xml:502(para) +msgid "In case you want to boot a Xen image from a volume, note the following requirement: The image you launch in must be the same type, fully virtualized or paravirtualized, as the one on the volume." +msgstr "" + +#: ./doc/training-guides/module001-ch006-overview-horizon-cli.xml:508(para) +msgid "Select the volume or volume snapshot to boot from." +msgstr "" + +#: ./doc/training-guides/module001-ch006-overview-horizon-cli.xml:512(para) +msgid "Enter a device name. Enter vda for KVM images or xvda for Xen images." +msgstr "" + +#: ./doc/training-guides/module001-ch006-overview-horizon-cli.xml:517(para) ./doc/training-guides/module001-ch006-overview-horizon-cli.xml:1769(para) +msgid "To launch an instance from a volume" +msgstr "" + +#: ./doc/training-guides/module001-ch006-overview-horizon-cli.xml:518(para) +msgid "You can launch an instance directly from one of the images available through the OpenStack Image Service or from an image that you have copied to a persistent volume. When you launch an instance from a volume, the procedure is basically the same as when launching an instance from an image in OpenStack Image Service, except for some additional steps." +msgstr "" + +#: ./doc/training-guides/module001-ch006-overview-horizon-cli.xml:526(para) +msgid "Create a volume as described inthe section called “Create or delete a volume”." +msgstr "" + +#: ./doc/training-guides/module001-ch006-overview-horizon-cli.xml:534(para) +msgid "It must be large enough to store an unzipped image." +msgstr "" + +#: ./doc/training-guides/module001-ch006-overview-horizon-cli.xml:538(para) +msgid "Create an image." +msgstr "" + +#: ./doc/training-guides/module001-ch006-overview-horizon-cli.xml:541(para) +msgid "For details, see Creating images manually in the OpenStack Virtual Machine Image Guide." +msgstr "" + +#: ./doc/training-guides/module001-ch006-overview-horizon-cli.xml:548(para) +msgid "Launch an instance." +msgstr "" + +#: ./doc/training-guides/module001-ch006-overview-horizon-cli.xml:551(para) +msgid "Attach the volume to the instance as described inthe section called “Attach volumes to instances”." +msgstr "" + +#: ./doc/training-guides/module001-ch006-overview-horizon-cli.xml:559(para) +msgid "Assuming that the attached volume is mounted as /dev/vdb, use one of the following commands to copy the image to the attached volume:" +msgstr "" + +#: ./doc/training-guides/module001-ch006-overview-horizon-cli.xml:566(para) +msgid "For a raw image:" +msgstr "" + +#: ./doc/training-guides/module001-ch006-overview-horizon-cli.xml:569(para) +msgid "$ cat IMAGE >/dev/null" +msgstr "" + +#: ./doc/training-guides/module001-ch006-overview-horizon-cli.xml:572(para) +msgid "Alternatively, use dd." +msgstr "" + +#: ./doc/training-guides/module001-ch006-overview-horizon-cli.xml:575(para) +msgid "For a non-raw image:" +msgstr "" + +#: ./doc/training-guides/module001-ch006-overview-horizon-cli.xml:578(para) +msgid "$ qemu-img convert -O raw IMAGE /dev/vdb" +msgstr "" + +#: ./doc/training-guides/module001-ch006-overview-horizon-cli.xml:581(para) +msgid "For a *.tar.bz2 image:" +msgstr "" + +#: ./doc/training-guides/module001-ch006-overview-horizon-cli.xml:584(para) +msgid "$ tar xfjO IMAGE >/dev/null" +msgstr "" + +#: ./doc/training-guides/module001-ch006-overview-horizon-cli.xml:589(para) +msgid "Only detached volumes are available for booting. Detach the volume." +msgstr "" + +#: ./doc/training-guides/module001-ch006-overview-horizon-cli.xml:593(para) +msgid "To launch an instance from the volume, continue withthe section called “Launch an instance from an image”." +msgstr "" + +#: ./doc/training-guides/module001-ch006-overview-horizon-cli.xml:602(para) +msgid "You can launch an instance directly from one of the images available through the OpenStack Image Service. When you do that, OpenStack creates a local copy of the image on the respective compute node where the instance is started." +msgstr "" + +#: ./doc/training-guides/module001-ch006-overview-horizon-cli.xml:609(para) +msgid "SSH in to your instance" +msgstr "" + +#: ./doc/training-guides/module001-ch006-overview-horizon-cli.xml:612(para) +msgid "To SSH into your instance, you use the downloaded keypair file." +msgstr "" + +#: ./doc/training-guides/module001-ch006-overview-horizon-cli.xml:614(para) +msgid "To SSH into your instance" +msgstr "" + +#: ./doc/training-guides/module001-ch006-overview-horizon-cli.xml:617(para) +msgid "Copy the IP address for your instance." +msgstr "" + +#: ./doc/training-guides/module001-ch006-overview-horizon-cli.xml:620(para) +msgid "Use the SSH command to make a secure connection to the instance. For example:" +msgstr "" + +#: ./doc/training-guides/module001-ch006-overview-horizon-cli.xml:624(para) +msgid "$ ssh -i MyKey.pem ubuntu@10.0.0.2" +msgstr "" + +#: ./doc/training-guides/module001-ch006-overview-horizon-cli.xml:627(para) +msgid "A prompt asks, \"Are you sure you want to continue connection (yes/no)?\" Type yes and you have successfully connected." +msgstr "" + +#: ./doc/training-guides/module001-ch006-overview-horizon-cli.xml:632(guilabel) +msgid "Manage instances" +msgstr "" + +#: ./doc/training-guides/module001-ch006-overview-horizon-cli.xml:633(guilabel) +msgid "Create instance snapshots" +msgstr "" + +#: ./doc/training-guides/module001-ch006-overview-horizon-cli.xml:635(title) +msgid "OpenStack Dashboard- Instances" +msgstr "" + +#: ./doc/training-guides/module001-ch006-overview-horizon-cli.xml:642(para) +msgid "To create instance snapshots" +msgstr "" + +#: ./doc/training-guides/module001-ch006-overview-horizon-cli.xml:653(para) ./doc/training-guides/module001-ch006-overview-horizon-cli.xml:692(para) +msgid "Click the Instancescategory." +msgstr "" + +#: ./doc/training-guides/module001-ch006-overview-horizon-cli.xml:656(para) ./doc/training-guides/module001-ch006-overview-horizon-cli.xml:695(para) +msgid "The dashboard lists the instances that are available for this project." +msgstr "" + +#: ./doc/training-guides/module001-ch006-overview-horizon-cli.xml:660(para) +msgid "Select the instance of which to create a snapshot. From the Actionsdrop-down list, select Create Snapshot." +msgstr "" + +#: ./doc/training-guides/module001-ch006-overview-horizon-cli.xml:665(para) +msgid "In the Create Snapshotwindow, enter a name for the snapshot. Click Create Snapshot. The dashboard shows the instance snapshot in the Images & Snapshotscategory." +msgstr "" + +#: ./doc/training-guides/module001-ch006-overview-horizon-cli.xml:671(para) +msgid "To launch an instance from the snapshot, select the snapshot and click Launch. Proceed withthe section called “Launch an instance from an image”." +msgstr "" + +#: ./doc/training-guides/module001-ch006-overview-horizon-cli.xml:680(guilabel) +msgid "Control the state of an instance" +msgstr "" + +#: ./doc/training-guides/module001-ch006-overview-horizon-cli.xml:681(para) +msgid "To control the state of an instance" +msgstr "" + +#: ./doc/training-guides/module001-ch006-overview-horizon-cli.xml:699(para) +msgid "Select the instance for which you want to change the state." +msgstr "" + +#: ./doc/training-guides/module001-ch006-overview-horizon-cli.xml:703(para) +msgid "In the Moredrop-down list in the Actionscolumn, select the state." +msgstr "" + +#: ./doc/training-guides/module001-ch006-overview-horizon-cli.xml:707(para) +msgid "Depending on the current state of the instance, you can choose to pause, un-pause, suspend, resume, soft or hard reboot, or terminate an instance." +msgstr "" + +#: ./doc/training-guides/module001-ch006-overview-horizon-cli.xml:713(title) +msgid "OpenStack Dashboard : Actions" +msgstr "" + +#: ./doc/training-guides/module001-ch006-overview-horizon-cli.xml:720(guilabel) +msgid "Track usage" +msgstr "" + +#: ./doc/training-guides/module001-ch006-overview-horizon-cli.xml:721(para) +msgid "Use the dashboard's Overviewcategory to track usage of instances for each project." +msgstr "" + +#: ./doc/training-guides/module001-ch006-overview-horizon-cli.xml:724(title) +msgid "OpenStack Dashboard - Track Usage" +msgstr "" + +#: ./doc/training-guides/module001-ch006-overview-horizon-cli.xml:731(para) +msgid "You can track costs per month by showing metrics like number of VCPUs, disks, RAM, and uptime of all your instances." +msgstr "" + +#: ./doc/training-guides/module001-ch006-overview-horizon-cli.xml:734(para) +msgid "To track usage" +msgstr "" + +#: ./doc/training-guides/module001-ch006-overview-horizon-cli.xml:742(para) +msgid "Select a month and click Submitto query the instance usage for that month." +msgstr "" + +#: ./doc/training-guides/module001-ch006-overview-horizon-cli.xml:746(para) +msgid "Click Download CSV Summaryto download a CVS summary." +msgstr "" + +#: ./doc/training-guides/module001-ch006-overview-horizon-cli.xml:750(guilabel) +msgid "Manage volumes" +msgstr "" + +#: ./doc/training-guides/module001-ch006-overview-horizon-cli.xml:751(para) +msgid "Volumes are block storage devices that you can attach to instances. They allow for persistent storage as they can be attached to a running instance, or detached and attached to another instance at any time." +msgstr "" + +#: ./doc/training-guides/module001-ch006-overview-horizon-cli.xml:755(para) +msgid "In contrast to the instance's root disk, the data of volumes is not destroyed when the instance is deleted." +msgstr "" + +#: ./doc/training-guides/module001-ch006-overview-horizon-cli.xml:757(guilabel) +msgid "Create or delete a volume" +msgstr "" + +#: ./doc/training-guides/module001-ch006-overview-horizon-cli.xml:758(para) +msgid "To create or delete a volume" +msgstr "" + +#: ./doc/training-guides/module001-ch006-overview-horizon-cli.xml:764(para) ./doc/training-guides/module001-ch006-overview-horizon-cli.xml:824(para) +msgid "If you are a member of multiple projects, select a Projectfrom the drop-down list at the top of the tab." +msgstr "" + +#: ./doc/training-guides/module001-ch006-overview-horizon-cli.xml:769(para) ./doc/training-guides/module001-ch006-overview-horizon-cli.xml:829(para) +msgid "Click the Volumescategory." +msgstr "" + +#: ./doc/training-guides/module001-ch006-overview-horizon-cli.xml:772(para) +msgid "To create a volume" +msgstr "" + +#: ./doc/training-guides/module001-ch006-overview-horizon-cli.xml:777(para) +msgid "Click Create Volume." +msgstr "" + +#: ./doc/training-guides/module001-ch006-overview-horizon-cli.xml:780(para) +msgid "In the window that opens, enter a name to assign to a volume, a description (optional), and define the size in GBs." +msgstr "" + +#: ./doc/training-guides/module001-ch006-overview-horizon-cli.xml:785(para) +msgid "Confirm your changes." +msgstr "" + +#: ./doc/training-guides/module001-ch006-overview-horizon-cli.xml:788(para) +msgid "The dashboard shows the volume in the Volumescategory." +msgstr "" + +#: ./doc/training-guides/module001-ch006-overview-horizon-cli.xml:794(para) +msgid "To delete one or multiple volumes" +msgstr "" + +#: ./doc/training-guides/module001-ch006-overview-horizon-cli.xml:799(para) +msgid "Activate the checkboxes in front of the volumes that you want to delete." +msgstr "" + +#: ./doc/training-guides/module001-ch006-overview-horizon-cli.xml:803(para) +msgid "Click Delete Volumesand confirm your choice in the pop-up that appears." +msgstr "" + +#: ./doc/training-guides/module001-ch006-overview-horizon-cli.xml:807(para) ./doc/training-guides/module001-ch006-overview-horizon-cli.xml:864(para) +msgid "A message indicates whether the action was successful." +msgstr "" + +#: ./doc/training-guides/module001-ch006-overview-horizon-cli.xml:811(para) +msgid "After you create one or more volumes, you can attach them to instances." +msgstr "" + +#: ./doc/training-guides/module001-ch006-overview-horizon-cli.xml:813(para) +msgid "You can attach a volume to one instance at a time." +msgstr "" + +#: ./doc/training-guides/module001-ch006-overview-horizon-cli.xml:814(para) +msgid "View the status of a volume in the Instances & Volumescategory of the dashboard: the volume is either available or In-Use." +msgstr "" + +#: ./doc/training-guides/module001-ch006-overview-horizon-cli.xml:817(guilabel) +msgid "Attach volumes to instances" +msgstr "" + +#: ./doc/training-guides/module001-ch006-overview-horizon-cli.xml:818(para) +msgid "To attach volumes to instances" +msgstr "" + +#: ./doc/training-guides/module001-ch006-overview-horizon-cli.xml:821(para) +msgid "Log in to OpenStack dashboard." +msgstr "" + +#: ./doc/training-guides/module001-ch006-overview-horizon-cli.xml:832(para) +msgid "Select the volume to add to an instance and click Edit Attachments." +msgstr "" + +#: ./doc/training-guides/module001-ch006-overview-horizon-cli.xml:836(para) +msgid "In the Manage Volume Attachmentswindow, select an instance." +msgstr "" + +#: ./doc/training-guides/module001-ch006-overview-horizon-cli.xml:840(para) +msgid "Enter a device name under which the volume should be accessible on the virtual machine." +msgstr "" + +#: ./doc/training-guides/module001-ch006-overview-horizon-cli.xml:844(para) +msgid "Click Attach Volumeto confirm your changes. The dashboard shows the instance to which the volume has been attached and the volume's device name." +msgstr "" + +#: ./doc/training-guides/module001-ch006-overview-horizon-cli.xml:849(para) +msgid "Now you can log in to the instance, mount the disk, format it, and use it." +msgstr "" + +#: ./doc/training-guides/module001-ch006-overview-horizon-cli.xml:853(para) +msgid "To detach a volume from an instance" +msgstr "" + +#: ./doc/training-guides/module001-ch006-overview-horizon-cli.xml:858(para) +msgid "Select the volume and click Edit Attachments." +msgstr "" + +#: ./doc/training-guides/module001-ch006-overview-horizon-cli.xml:861(para) +msgid "Click Detach Volumeand confirm your changes." +msgstr "" + +#: ./doc/training-guides/module001-ch006-overview-horizon-cli.xml:868(guilabel) +msgid "OpenStack command-line clients" +msgstr "" + +#: ./doc/training-guides/module001-ch006-overview-horizon-cli.xml:870(para) +msgid "You can use the OpenStack command-line clients to run simple commands that make API calls and automate tasks by using scripts. Internally, each client command runs cURL commands that embed API requests. The OpenStack APIs are RESTful APIs that use the HTTP protocol, including methods, URIs, media types, and response codes." +msgstr "" + +#: ./doc/training-guides/module001-ch006-overview-horizon-cli.xml:876(para) +msgid "These open-source Python clients run on Linux or Mac OS X systems and are easy to learn and use. Each OpenStack service has its own command-line client. On some client commands, you can specify a debugparameter to show the underlying API request for the command. This is a good way to become familiar with the OpenStack API calls." +msgstr "" + +#: ./doc/training-guides/module001-ch006-overview-horizon-cli.xml:882(para) +msgid "The following command-line clients are available for the respective services' APIs:" +msgstr "" + +#: ./doc/training-guides/module001-ch006-overview-horizon-cli.xml:884(para) +msgid "cinder(python-cinderclient)" +msgstr "" + +#: ./doc/training-guides/module001-ch006-overview-horizon-cli.xml:885(para) +msgid "Client for the Block Storage Service API. Use to create and manage volumes." +msgstr "" + +#: ./doc/training-guides/module001-ch006-overview-horizon-cli.xml:887(para) +msgid "glance(python-glanceclient)" +msgstr "" + +#: ./doc/training-guides/module001-ch006-overview-horizon-cli.xml:888(para) +msgid "Client for the Image Service API. Use to create and manage images." +msgstr "" + +#: ./doc/training-guides/module001-ch006-overview-horizon-cli.xml:890(para) +msgid "keystone(python-keystoneclient)" +msgstr "" + +#: ./doc/training-guides/module001-ch006-overview-horizon-cli.xml:891(para) +msgid "Client for the Identity Service API. Use to create and manage users, tenants, roles, endpoints, and credentials." +msgstr "" + +#: ./doc/training-guides/module001-ch006-overview-horizon-cli.xml:894(para) +msgid "nova(python-novaclient)" +msgstr "" + +#: ./doc/training-guides/module001-ch006-overview-horizon-cli.xml:895(para) +msgid "Client for the Compute API and its extensions. Use to create and manage images, instances, and flavors." +msgstr "" + +#: ./doc/training-guides/module001-ch006-overview-horizon-cli.xml:897(para) +msgid "neutron(python-neutronclient)" +msgstr "" + +#: ./doc/training-guides/module001-ch006-overview-horizon-cli.xml:898(para) +msgid "Client for the Networking API. Use to configure networks for guest servers. This client was previously known as neutron." +msgstr "" + +#: ./doc/training-guides/module001-ch006-overview-horizon-cli.xml:901(para) +msgid "swift(python-swiftclient)" +msgstr "" + +#: ./doc/training-guides/module001-ch006-overview-horizon-cli.xml:902(para) +msgid "Client for the Object Storage API. Use to gather statistics, list items, update metadata, upload, download and delete files stored by the object storage service. Provides access to a swift installation for ad hoc processing." +msgstr "" + +#: ./doc/training-guides/module001-ch006-overview-horizon-cli.xml:906(para) +msgid "heat(python-heatclient)" +msgstr "" + +#: ./doc/training-guides/module001-ch006-overview-horizon-cli.xml:907(para) +msgid "Client for the Orchestration API. Use to launch stacks from templates, view details of running stacks including events and resources, and update and delete stacks." +msgstr "" + +#: ./doc/training-guides/module001-ch006-overview-horizon-cli.xml:910(guilabel) +msgid "Install the OpenStack command-line clients" +msgstr "" + +#: ./doc/training-guides/module001-ch006-overview-horizon-cli.xml:911(para) +msgid "To install the clients, install the prerequisite software and the Python package for each OpenStack client." +msgstr "" + +#: ./doc/training-guides/module001-ch006-overview-horizon-cli.xml:913(guilabel) +msgid "Install the clients" +msgstr "" + +#: ./doc/training-guides/module001-ch006-overview-horizon-cli.xml:914(para) +msgid "Use pipto install the OpenStack clients on a Mac OS X or Linux system. It is easy and ensures that you get the latest version of the client from thePython Package Index. Also, piplets you update or remove a package. After you install the clients, you must source an openrc file to set required environment variables before you can request OpenStack services through the clients or the APIs." +msgstr "" + +#: ./doc/training-guides/module001-ch006-overview-horizon-cli.xml:924(para) +msgid "To install the clients" +msgstr "" + +#: ./doc/training-guides/module001-ch006-overview-horizon-cli.xml:927(para) +msgid "You must install each client separately." +msgstr "" + +#: ./doc/training-guides/module001-ch006-overview-horizon-cli.xml:930(para) +msgid "Run the following command to install or update a client package:" +msgstr "" + +#: ./doc/training-guides/module001-ch006-overview-horizon-cli.xml:934(para) +msgid "$ sudo pip install [--update] python-<project>client" +msgstr "" + +#: ./doc/training-guides/module001-ch006-overview-horizon-cli.xml:938(para) +msgid "Where <project> is the project name and has one of the following values:" +msgstr "" + +#: ./doc/training-guides/module001-ch006-overview-horizon-cli.xml:944(para) +msgid "nova. Compute API and extensions." +msgstr "" + +#: ./doc/training-guides/module001-ch006-overview-horizon-cli.xml:947(para) +msgid "neutron. Networking API." +msgstr "" + +#: ./doc/training-guides/module001-ch006-overview-horizon-cli.xml:950(para) +msgid "keystone. Identity Service API." +msgstr "" + +#: ./doc/training-guides/module001-ch006-overview-horizon-cli.xml:953(para) +msgid "glance. Image Service API." +msgstr "" + +#: ./doc/training-guides/module001-ch006-overview-horizon-cli.xml:956(para) +msgid "swift. Object Storage API." +msgstr "" + +#: ./doc/training-guides/module001-ch006-overview-horizon-cli.xml:959(para) +msgid "cinder. Block Storage Service API." +msgstr "" + +#: ./doc/training-guides/module001-ch006-overview-horizon-cli.xml:962(para) +msgid "heat. Orchestration API." +msgstr "" + +#: ./doc/training-guides/module001-ch006-overview-horizon-cli.xml:967(para) +msgid "For example, to install the nova client, run the following command:" +msgstr "" + +#: ./doc/training-guides/module001-ch006-overview-horizon-cli.xml:971(para) +msgid "$ sudo pip install python-novaclient" +msgstr "" + +#: ./doc/training-guides/module001-ch006-overview-horizon-cli.xml:974(para) +msgid "To update the nova client, run the following command:" +msgstr "" + +#: ./doc/training-guides/module001-ch006-overview-horizon-cli.xml:978(para) +msgid "$ sudo pip install --upgrade python-novaclient" +msgstr "" + +#: ./doc/training-guides/module001-ch006-overview-horizon-cli.xml:982(para) +msgid "To remove the nova client, run the following command:" +msgstr "" + +#: ./doc/training-guides/module001-ch006-overview-horizon-cli.xml:986(para) +msgid "$ sudo pip uninstall python-novaclient" +msgstr "" + +#: ./doc/training-guides/module001-ch006-overview-horizon-cli.xml:989(para) +msgid "Before you can issue client commands, you must download and source the openrc file to set environment variables. Proceed tothe section called “OpenStack RC file”." +msgstr "" + +#: ./doc/training-guides/module001-ch006-overview-horizon-cli.xml:996(guilabel) +msgid "Get the version for a client" +msgstr "" + +#: ./doc/training-guides/module001-ch006-overview-horizon-cli.xml:997(para) +msgid "After you install an OpenStack client, you can search for its version number, as follows:" +msgstr "" + +#: ./doc/training-guides/module001-ch006-overview-horizon-cli.xml:999(para) +msgid "$ pip freeze | grep python-" +msgstr "" + +#: ./doc/training-guides/module001-ch006-overview-horizon-cli.xml:1000(para) +msgid "python-glanceclient==0.4.0python-keystoneclient==0.1.2-e git+https://github.com/openstack/python-novaclient.git@077cc0bf22e378c4c4b970f2331a695e440a939f#egg=python_novaclient-devpython-neutronclient==0.1.1python-swiftclient==1.1.1" +msgstr "" + +#: ./doc/training-guides/module001-ch006-overview-horizon-cli.xml:1002(para) +msgid "You can also use the yolk -lcommand to see which version of the client is installed:" +msgstr "" + +#: ./doc/training-guides/module001-ch006-overview-horizon-cli.xml:1004(para) +msgid "$ yolk -l | grep python-novaclient" +msgstr "" + +#: ./doc/training-guides/module001-ch006-overview-horizon-cli.xml:1005(para) +msgid "python-novaclient - 2.6.10.27 - active development (/Users/your.name/src/cloud-servers/src/src/python-novaclient)python-novaclient - 2012.1 - non-active" +msgstr "" + +#: ./doc/training-guides/module001-ch006-overview-horizon-cli.xml:1008(guilabel) +msgid "OpenStack RC file" +msgstr "" + +#: ./doc/training-guides/module001-ch006-overview-horizon-cli.xml:1009(para) +msgid "To set the required environment variables for the OpenStack command-line clients, you must download and source an environment file, openrc.sh. It is project-specific and contains the credentials used by OpenStack Compute, Image, and Identity services." +msgstr "" + +#: ./doc/training-guides/module001-ch006-overview-horizon-cli.xml:1014(para) +msgid "When you source the file and enter the password, environment variables are set for that shell. They allow the commands to communicate to the OpenStack services that run in the cloud." +msgstr "" + +#: ./doc/training-guides/module001-ch006-overview-horizon-cli.xml:1018(para) +msgid "You can download the file from the OpenStack dashboard as an administrative user or any other user." +msgstr "" + +#: ./doc/training-guides/module001-ch006-overview-horizon-cli.xml:1020(para) +msgid "To download the OpenStack RC file" +msgstr "" + +#: ./doc/training-guides/module001-ch006-overview-horizon-cli.xml:1026(para) +msgid "On the Projecttab, select the project for which you want to download the OpenStack RC file." +msgstr "" + +#: ./doc/training-guides/module001-ch006-overview-horizon-cli.xml:1030(para) +msgid "Click Access & Security. Then, click Download OpenStack RC Fileand save the file." +msgstr "" + +#: ./doc/training-guides/module001-ch006-overview-horizon-cli.xml:1034(para) +msgid "Copy the openrc.sh file to the machine from where you want to run OpenStack commands." +msgstr "" + +#: ./doc/training-guides/module001-ch006-overview-horizon-cli.xml:1038(para) +msgid "For example, copy the file to the machine from where you want to upload an image with a glance client command." +msgstr "" + +#: ./doc/training-guides/module001-ch006-overview-horizon-cli.xml:1042(para) +msgid "On any shell from where you want to run OpenStack commands, source the openrc.sh file for the respective project." +msgstr "" + +#: ./doc/training-guides/module001-ch006-overview-horizon-cli.xml:1047(para) +msgid "In this example, we source the demo-openrc.sh file for the demo project:" +msgstr "" + +#: ./doc/training-guides/module001-ch006-overview-horizon-cli.xml:1051(para) +msgid "$ source demo-openrc.sh" +msgstr "" + +#: ./doc/training-guides/module001-ch006-overview-horizon-cli.xml:1054(para) +msgid "When you are prompted for an OpenStack password, enter the OpenStack password for the user who downloaded the openrc.sh file." +msgstr "" + +#: ./doc/training-guides/module001-ch006-overview-horizon-cli.xml:1059(para) +msgid "When you run OpenStack client commands, you can override some environment variable settings by using the options that are listed at the end of the nova helpoutput. For example, you can override the OS_PASSWORD setting in the openrc.sh file by specifying a password on a nova command, as follows:" +msgstr "" + +#: ./doc/training-guides/module001-ch006-overview-horizon-cli.xml:1067(para) +msgid "$ nova --password <password> image-list" +msgstr "" + +#: ./doc/training-guides/module001-ch006-overview-horizon-cli.xml:1070(para) +msgid "Where password is your password." +msgstr "" + +#: ./doc/training-guides/module001-ch006-overview-horizon-cli.xml:1074(para) +msgid "During setup of OpenStack cloud, the cloud operator sets user permissions to manage images." +msgstr "" + +#: ./doc/training-guides/module001-ch006-overview-horizon-cli.xml:1076(para) +msgid "Image upload and management might be restricted to only cloud administrators or cloud operators." +msgstr "" + +#: ./doc/training-guides/module001-ch006-overview-horizon-cli.xml:1078(para) +msgid "After you upload an image, it is considered golden and you cannot change it." +msgstr "" + +#: ./doc/training-guides/module001-ch006-overview-horizon-cli.xml:1080(para) +msgid "You can upload images through the glance client or the Image Service API. You can also use the nova client to list images, set and delete image metadata, delete images, and take a snapshot of a running instance to create an image." +msgstr "" + +#: ./doc/training-guides/module001-ch006-overview-horizon-cli.xml:1084(guilabel) +msgid "Manage images with the glance client" +msgstr "" + +#: ./doc/training-guides/module001-ch006-overview-horizon-cli.xml:1085(para) +msgid "To list or get details for images" +msgstr "" + +#: ./doc/training-guides/module001-ch006-overview-horizon-cli.xml:1088(para) +msgid "To list the available images:" +msgstr "" + +#: ./doc/training-guides/module001-ch006-overview-horizon-cli.xml:1091(para) +msgid "$ glance image-list" +msgstr "" + +#: ./doc/training-guides/module001-ch006-overview-horizon-cli.xml:1094(para) +msgid "You can use grep to filter the list, as follows:" +msgstr "" + +#: ./doc/training-guides/module001-ch006-overview-horizon-cli.xml:1098(para) +msgid "$ glance image-list | grep 'cirros'" +msgstr "" + +#: ./doc/training-guides/module001-ch006-overview-horizon-cli.xml:1101(para) +msgid "To get image details, by name or ID:" +msgstr "" + +#: ./doc/training-guides/module001-ch006-overview-horizon-cli.xml:1104(para) +msgid "$ glance image-show myCirrosImage" +msgstr "" + +#: ./doc/training-guides/module001-ch006-overview-horizon-cli.xml:1107(para) +msgid "To add an image" +msgstr "" + +#: ./doc/training-guides/module001-ch006-overview-horizon-cli.xml:1110(para) +msgid "The following example uploads a CentOS 6.3 image in qcow2 format and configures it for public access:" +msgstr "" + +#: ./doc/training-guides/module001-ch006-overview-horizon-cli.xml:1114(para) +msgid "$glance image-create --name centos63-image --disk-format=qcow2 --container-format=bare --is-public=True ./centos63.qcow2" +msgstr "" + +#: ./doc/training-guides/module001-ch006-overview-horizon-cli.xml:1119(para) +msgid "To create an image" +msgstr "" + +#: ./doc/training-guides/module001-ch006-overview-horizon-cli.xml:1122(para) +msgid "Write any buffered data to disk." +msgstr "" + +#: ./doc/training-guides/module001-ch006-overview-horizon-cli.xml:1125(para) +msgid "For more information, see theTaking Snapshots in the OpenStack Operations Guide." +msgstr "" + +#: ./doc/training-guides/module001-ch006-overview-horizon-cli.xml:1131(para) +msgid "To create the image, list instances to get the server ID:" +msgstr "" + +#: ./doc/training-guides/module001-ch006-overview-horizon-cli.xml:1135(para) ./doc/training-guides/module001-ch006-overview-horizon-cli.xml:1737(para) ./doc/training-guides/module001-ch006-overview-horizon-cli.xml:1893(para) ./doc/training-guides/module001-ch006-overview-horizon-cli.xml:2056(para) ./doc/training-guides/module001-ch006-overview-horizon-cli.xml:2206(para) ./doc/training-guides/module001-ch006-overview-horizon-cli.xml:2223(para) ./doc/training-guides/module001-ch006-overview-horizon-cli.xml:2379(para) +msgid "$ nova list" +msgstr "" + +#: ./doc/training-guides/module001-ch006-overview-horizon-cli.xml:1138(para) +msgid "In this example, the server is named myCirrosServer. Use this server to create a snapshot, as follows:" +msgstr "" + +#: ./doc/training-guides/module001-ch006-overview-horizon-cli.xml:1142(para) +msgid "$ nova image-create myCirrosServer myCirrosImage" +msgstr "" + +#: ./doc/training-guides/module001-ch006-overview-horizon-cli.xml:1146(para) +msgid "The command creates a qemu snapshot and automatically uploads the image to your repository. Only the tenant that creates the image has access to it." +msgstr "" + +#: ./doc/training-guides/module001-ch006-overview-horizon-cli.xml:1151(para) +msgid "Get details for your image to check its status:" +msgstr "" + +#: ./doc/training-guides/module001-ch006-overview-horizon-cli.xml:1154(para) +msgid "$ nova image-show IMAGE" +msgstr "" + +#: ./doc/training-guides/module001-ch006-overview-horizon-cli.xml:1157(para) +msgid "The image status changes from SAVING to ACTIVE. Only the tenant who creates the image has access to it." +msgstr "" + +#: ./doc/training-guides/module001-ch006-overview-horizon-cli.xml:1161(para) +msgid "To launch an instance from your image" +msgstr "" + +#: ./doc/training-guides/module001-ch006-overview-horizon-cli.xml:1164(para) +msgid "To launch an instance from your image, include the image ID and flavor ID, as follows:" +msgstr "" + +#: ./doc/training-guides/module001-ch006-overview-horizon-cli.xml:1168(para) +msgid "$ nova boot newServer --image 7e5142af-1253-4634-bcc6-89482c5f2e8a --flavor 3" +msgstr "" + +#: ./doc/training-guides/module001-ch006-overview-horizon-cli.xml:1172(guilabel) +msgid "Troubleshoot image creation" +msgstr "" + +#: ./doc/training-guides/module001-ch006-overview-horizon-cli.xml:1175(para) +msgid "You cannot create a snapshot from an instance that has an attached volume. Detach the volume, create the image, and re-mount the volume." +msgstr "" + +#: ./doc/training-guides/module001-ch006-overview-horizon-cli.xml:1180(para) +msgid "Make sure the version of qemu you are using is version 0.14 or greater. Older versions of qemu result in an \"unknown option -s\" error message in the nova-compute.log." +msgstr "" + +#: ./doc/training-guides/module001-ch006-overview-horizon-cli.xml:1186(para) +msgid "Examine the /var/log/nova-api.log and /var/log/nova-compute.log log files for error messages." +msgstr "" + +#: ./doc/training-guides/module001-ch006-overview-horizon-cli.xml:1191(guilabel) ./doc/training-guides/module001-ch006-overview-horizon-cli.xml:1245(guilabel) +msgid "Set up access and security for instances" +msgstr "" + +#: ./doc/training-guides/module001-ch006-overview-horizon-cli.xml:1192(para) +msgid "When you launch a virtual machine, you can inject a key pair, which provides SSH access to your instance. For this to work, the image must contain the cloud-init package. Create at least one key pair for each project. If you generate a keypair with an external tool, you can import it into OpenStack. You can use the keypair for multiple instances that belong to that project. In case an image uses a static root password or a static key set – neither is recommended – you must not provide a keypair when you launch the instance." +msgstr "" + +#: ./doc/training-guides/module001-ch006-overview-horizon-cli.xml:1201(para) ./doc/training-guides/module001-ch006-overview-horizon-cli.xml:1255(para) +msgid "A security group is a named collection of network access rules that you use to limit the types of traffic that have access to instances. When you launch an instance, you can assign one or more security groups to it. If you do not create security groups, new instances are automatically assigned to the default security group, unless you explicitly specify a different security group. The associated rules in each security group control the traffic to instances in the group. Any incoming traffic that is not matched by a rule is denied access by default. You can add rules to or remove rules from a security group. You can modify rules for the default and any other security group." +msgstr "" + +#: ./doc/training-guides/module001-ch006-overview-horizon-cli.xml:1213(para) ./doc/training-guides/module001-ch006-overview-horizon-cli.xml:1267(para) +msgid "You must modify the rules for the default security group because users cannot access instances that use the default group from any IP address outside the cloud." +msgstr "" + +#: ./doc/training-guides/module001-ch006-overview-horizon-cli.xml:1216(para) ./doc/training-guides/module001-ch006-overview-horizon-cli.xml:1270(para) +msgid "You can modify the rules in a security group to allow access to instances through different ports and protocols. For example, you can modify rules to allow access to instances through SSH, to ping them, or to allow UDP traffic – for example, for a DNS server running on an instance. You specify the following parameters for rules:" +msgstr "" + +#: ./doc/training-guides/module001-ch006-overview-horizon-cli.xml:1224(para) ./doc/training-guides/module001-ch006-overview-horizon-cli.xml:1278(para) +msgid "Source of traffic. Enable traffic to instances from either IP addresses inside the cloud from other group members or from all IP addresses." +msgstr "" + +#: ./doc/training-guides/module001-ch006-overview-horizon-cli.xml:1229(para) ./doc/training-guides/module001-ch006-overview-horizon-cli.xml:1283(para) +msgid "Protocol. Choose TCP for SSH, ICMP for pings, or UDP." +msgstr "" + +#: ./doc/training-guides/module001-ch006-overview-horizon-cli.xml:1233(para) ./doc/training-guides/module001-ch006-overview-horizon-cli.xml:1287(para) +msgid "Destination port on virtual machine. Defines a port range. To open a single port only, enter the same value twice. ICMP does not support ports: Enter values to define the codes and types of ICMP traffic to be allowed." +msgstr "" + +#: ./doc/training-guides/module001-ch006-overview-horizon-cli.xml:1239(para) ./doc/training-guides/module001-ch006-overview-horizon-cli.xml:1293(para) +msgid "Rules are automatically enforced as soon as you create or modify them." +msgstr "" + +#: ./doc/training-guides/module001-ch006-overview-horizon-cli.xml:1241(para) ./doc/training-guides/module001-ch006-overview-horizon-cli.xml:1295(para) +msgid "You can also assign a floating IP address to a running instance to make it accessible from outside the cloud. You assign a floating IP address to an instance and attach a block storage device, or volume, for persistent storage." +msgstr "" + +#: ./doc/training-guides/module001-ch006-overview-horizon-cli.xml:1246(para) +msgid "When you launch a virtual machine, you can inject a key pair, which provides SSH access to your instance. For this to work, the image must contain the cloud-init package. Create at least one key pair for each project. If you generate a keypair with an external tool, you can import it into OpenStack. You can use the key pair for multiple instances that belong to that project. In case an image uses a static root password or a static key set – neither is recommended – you must not provide a key pair when you launch the instance." +msgstr "" + +#: ./doc/training-guides/module001-ch006-overview-horizon-cli.xml:1299(guilabel) +msgid "Add or import keypairs" +msgstr "" + +#: ./doc/training-guides/module001-ch006-overview-horizon-cli.xml:1300(para) +msgid "To add a key" +msgstr "" + +#: ./doc/training-guides/module001-ch006-overview-horizon-cli.xml:1301(para) +msgid "You can generate a keypair or upload an existing public key." +msgstr "" + +#: ./doc/training-guides/module001-ch006-overview-horizon-cli.xml:1305(para) +msgid "To generate a keypair, run the following command:" +msgstr "" + +#: ./doc/training-guides/module001-ch006-overview-horizon-cli.xml:1309(para) +msgid "$ nova keypair-add KEY_NAME > MY_KEY.pem" +msgstr "" + +#: ./doc/training-guides/module001-ch006-overview-horizon-cli.xml:1312(para) +msgid "The command generates a keypair named KEY_NAME, writes the private key to the MY_KEY.pem file, and registers the public key at the Nova database." +msgstr "" + +#: ./doc/training-guides/module001-ch006-overview-horizon-cli.xml:1317(para) +msgid "To set the permissions of the MY_KEY.pem file, run the following command:" +msgstr "" + +#: ./doc/training-guides/module001-ch006-overview-horizon-cli.xml:1321(para) +msgid "$ chmod 600 MY_KEY.pem" +msgstr "" + +#: ./doc/training-guides/module001-ch006-overview-horizon-cli.xml:1324(para) +msgid "The command changes the permissions of the MY_KEY.pem file so that only you can read and write to it." +msgstr "" + +#: ./doc/training-guides/module001-ch006-overview-horizon-cli.xml:1328(para) +msgid "To import a key" +msgstr "" + +#: ./doc/training-guides/module001-ch006-overview-horizon-cli.xml:1331(para) +msgid "If you have already generated a keypair with the public key located at ~/.ssh/id_rsa.pub, run the following command to upload the public key:" +msgstr "" + +#: ./doc/training-guides/module001-ch006-overview-horizon-cli.xml:1336(para) +msgid "$ nova keypair-add --pub_key ~/.ssh/id_rsa.pub KEY_NAME" +msgstr "" + +#: ./doc/training-guides/module001-ch006-overview-horizon-cli.xml:1340(para) +msgid "The command registers the public key at the Nova database and names the keypair KEY_NAME." +msgstr "" + +#: ./doc/training-guides/module001-ch006-overview-horizon-cli.xml:1344(para) +msgid "List keypairs to make sure that the uploaded keypair appears in the list:" +msgstr "" + +#: ./doc/training-guides/module001-ch006-overview-horizon-cli.xml:1348(para) ./doc/training-guides/module001-ch006-overview-horizon-cli.xml:1678(para) +msgid "$ nova keypair-list" +msgstr "" + +#: ./doc/training-guides/module001-ch006-overview-horizon-cli.xml:1351(guilabel) +msgid "Configure security groups and rules" +msgstr "" + +#: ./doc/training-guides/module001-ch006-overview-horizon-cli.xml:1352(para) +msgid "To configure security groups" +msgstr "" + +#: ./doc/training-guides/module001-ch006-overview-horizon-cli.xml:1355(para) +msgid "To list all security groups" +msgstr "" + +#: ./doc/training-guides/module001-ch006-overview-horizon-cli.xml:1358(para) +msgid "To list security groups for the current project, including descriptions, enter the following command:" +msgstr "" + +#: ./doc/training-guides/module001-ch006-overview-horizon-cli.xml:1363(para) +msgid "$ nova secgroup-list" +msgstr "" + +#: ./doc/training-guides/module001-ch006-overview-horizon-cli.xml:1366(para) +msgid "To create a security group" +msgstr "" + +#: ./doc/training-guides/module001-ch006-overview-horizon-cli.xml:1369(para) +msgid "To create a security group with a specified name and description, enter the following command:" +msgstr "" + +#: ./doc/training-guides/module001-ch006-overview-horizon-cli.xml:1373(para) +msgid "$ nova secgroup-create SEC_GROUP_NAME GROUP_DESCRIPTION" +msgstr "" + +#: ./doc/training-guides/module001-ch006-overview-horizon-cli.xml:1377(para) +msgid "To delete a security group" +msgstr "" + +#: ./doc/training-guides/module001-ch006-overview-horizon-cli.xml:1380(para) +msgid "To delete a specified group, enter the following command:" +msgstr "" + +#: ./doc/training-guides/module001-ch006-overview-horizon-cli.xml:1384(para) +msgid "$ nova secgroup-delete SEC_GROUP_NAME" +msgstr "" + +#: ./doc/training-guides/module001-ch006-overview-horizon-cli.xml:1387(para) +msgid "To configure security group rules" +msgstr "" + +#: ./doc/training-guides/module001-ch006-overview-horizon-cli.xml:1388(para) +msgid "Modify security group rules with the nova secgroup-*-rulecommands." +msgstr "" + +#: ./doc/training-guides/module001-ch006-overview-horizon-cli.xml:1392(para) +msgid "On a shell, source the OpenStack RC file. For details, seethe section called “OpenStack RC file”." +msgstr "" + +#: ./doc/training-guides/module001-ch006-overview-horizon-cli.xml:1400(para) +msgid "To list the rules for a security group" +msgstr "" + +#: ./doc/training-guides/module001-ch006-overview-horizon-cli.xml:1403(para) +msgid "$ nova secgroup-list-rules SEC_GROUP_NAME" +msgstr "" + +#: ./doc/training-guides/module001-ch006-overview-horizon-cli.xml:1406(para) +msgid "To allow SSH access to the instances" +msgstr "" + +#: ./doc/training-guides/module001-ch006-overview-horizon-cli.xml:1409(para) ./doc/training-guides/module001-ch006-overview-horizon-cli.xml:1445(para) +msgid "Choose one of the following sub-steps:" +msgstr "" + +#: ./doc/training-guides/module001-ch006-overview-horizon-cli.xml:1414(para) +msgid "Add rule for all IPs" +msgstr "" + +#: ./doc/training-guides/module001-ch006-overview-horizon-cli.xml:1417(para) +msgid "Either from all IP addresses (specified as IP subnet in CIDR notation as 0.0.0.0/0):" +msgstr "" + +#: ./doc/training-guides/module001-ch006-overview-horizon-cli.xml:1421(para) +msgid "$ nova secgroup-add-rule SEC_GROUP_NAME tcp 22 22 0.0.0.0/0" +msgstr "" + +#: ./doc/training-guides/module001-ch006-overview-horizon-cli.xml:1427(para) +msgid "Add rule for security groups" +msgstr "" + +#: ./doc/training-guides/module001-ch006-overview-horizon-cli.xml:1430(para) +msgid "Alternatively, you can allow only IP addresses from other security groups (source groups) to access the specified port:" +msgstr "" + +#: ./doc/training-guides/module001-ch006-overview-horizon-cli.xml:1435(para) +msgid "$ nova secgroup-add-group-rule --ip_proto tcp --from_port 22 \\ --to_port 22 SEC_GROUP_NAME SOURCE_GROUP_NAME" +msgstr "" + +#: ./doc/training-guides/module001-ch006-overview-horizon-cli.xml:1442(para) +msgid "To allow pinging the instances" +msgstr "" + +#: ./doc/training-guides/module001-ch006-overview-horizon-cli.xml:1450(para) +msgid "To allow pinging from IPs" +msgstr "" + +#: ./doc/training-guides/module001-ch006-overview-horizon-cli.xml:1453(para) +msgid "Specify all IP addresses as IP subnet in CIDR notation: 0.0.0.0/0. This command allows access to all codes and all types of ICMP traffic, respectively:" +msgstr "" + +#: ./doc/training-guides/module001-ch006-overview-horizon-cli.xml:1458(para) +msgid "$ nova secgroup-add-rule SEC_GROUP_NAME icmp -1 -1 0.0.0.0/0" +msgstr "" + +#: ./doc/training-guides/module001-ch006-overview-horizon-cli.xml:1462(para) +msgid "To allow pinging from other security groups" +msgstr "" + +#: ./doc/training-guides/module001-ch006-overview-horizon-cli.xml:1465(para) +msgid "To allow only members of other security groups (source groups) to ping instances:" +msgstr "" + +#: ./doc/training-guides/module001-ch006-overview-horizon-cli.xml:1469(para) +msgid "$ nova secgroup-add-group-rule --ip_proto icmp --from_port -1 \\ --to_port -1 SEC_GROUP_NAME SOURCE_GROUP_NAME" +msgstr "" + +#: ./doc/training-guides/module001-ch006-overview-horizon-cli.xml:1476(para) +msgid "To allow access through UDP port" +msgstr "" + +#: ./doc/training-guides/module001-ch006-overview-horizon-cli.xml:1479(para) +msgid "To allow access through a UDP port, such as allowing access to a DNS server that runs on a VM, complete one of the following sub-steps:" +msgstr "" + +#: ./doc/training-guides/module001-ch006-overview-horizon-cli.xml:1486(para) +msgid "To allow UDP access from IPs" +msgstr "" + +#: ./doc/training-guides/module001-ch006-overview-horizon-cli.xml:1489(para) +msgid "Specify all IP addresses as IP subnet in CIDR notation: 0.0.0.0/0." +msgstr "" + +#: ./doc/training-guides/module001-ch006-overview-horizon-cli.xml:1493(para) +msgid "$ nova secgroup-add-rule SEC_GROUP_NAME udp 53 53 0.0.0.0/0" +msgstr "" + +#: ./doc/training-guides/module001-ch006-overview-horizon-cli.xml:1497(para) +msgid "To allow UDP access" +msgstr "" + +#: ./doc/training-guides/module001-ch006-overview-horizon-cli.xml:1500(para) +msgid "To allow only IP addresses from other security groups (source groups) to access the specified port:" +msgstr "" + +#: ./doc/training-guides/module001-ch006-overview-horizon-cli.xml:1504(para) +msgid "$ nova secgroup-add-group-rule --ip_proto udp --from_port 53 \\ --to_port 53 SEC_GROUP_NAME SOURCE_GROUP_NAME" +msgstr "" + +#: ./doc/training-guides/module001-ch006-overview-horizon-cli.xml:1511(para) +msgid "To delete a security group rule, specify the same arguments that you used to create the rule." +msgstr "" + +#: ./doc/training-guides/module001-ch006-overview-horizon-cli.xml:1515(para) +msgid "To delete the security rule that you created inStep 3.a:" +msgstr "" + +#: ./doc/training-guides/module001-ch006-overview-horizon-cli.xml:1520(para) +msgid "$ nova secgroup-delete-rule SEC_GROUP_NAME tcp 22 22 0.0.0.0/0" +msgstr "" + +#: ./doc/training-guides/module001-ch006-overview-horizon-cli.xml:1524(para) +msgid "To delete the security rule that you created inStep 3.b:" +msgstr "" + +#: ./doc/training-guides/module001-ch006-overview-horizon-cli.xml:1529(para) +msgid "$ nova secgroup-delete-group-rule --ip_proto tcp --from_port 22 \\ --to_port 22 SEC_GROUP_NAME SOURCE_GROUP_NAME" +msgstr "" + +#: ./doc/training-guides/module001-ch006-overview-horizon-cli.xml:1535(para) ./doc/training-guides/module001-ch006-overview-horizon-cli.xml:1897(para) +msgid "Instances are virtual machines that run inside the cloud." +msgstr "" + +#: ./doc/training-guides/module001-ch006-overview-horizon-cli.xml:1537(para) +msgid "Before you can launch an instance, you must gather parameters such as the image and flavor from which you want to launch your instance." +msgstr "" + +#: ./doc/training-guides/module001-ch006-overview-horizon-cli.xml:1540(para) +msgid "You can launch an instance directly from one of the available OpenStack images or from an image that you have copied to a persistent volume. The OpenStack Image Service provides a pool of images that are accessible to members of different projects." +msgstr "" + +#: ./doc/training-guides/module001-ch006-overview-horizon-cli.xml:1545(guilabel) +msgid "Gather parameters to launch an instance" +msgstr "" + +#: ./doc/training-guides/module001-ch006-overview-horizon-cli.xml:1546(para) +msgid "To launch an instance, you must specify the following parameters:" +msgstr "" + +#: ./doc/training-guides/module001-ch006-overview-horizon-cli.xml:1550(para) +msgid "The instance source, which is an image or snapshot. Alternatively, you can boot from a volume, which is block storage, to which you've copied an image or snapshot." +msgstr "" + +#: ./doc/training-guides/module001-ch006-overview-horizon-cli.xml:1556(para) +msgid "The imageor snapshot, which represents the operating system." +msgstr "" + +#: ./doc/training-guides/module001-ch006-overview-horizon-cli.xml:1560(para) +msgid "A namefor your instance." +msgstr "" + +#: ./doc/training-guides/module001-ch006-overview-horizon-cli.xml:1563(para) +msgid "The flavorfor your instance, which defines the compute, memory, and storage capacity of nova computing instances. A flavor is an available hardware configuration for a server. It defines the \"size\" of a virtual server that can be launched. For more details and a list of default flavors available, see Section 1.5, \"Managing Flavors,\" (⇽ User Guide for Administrators )." +msgstr "" + +#: ./doc/training-guides/module001-ch006-overview-horizon-cli.xml:1572(para) +msgid "User Data is a special key in the metadata service which holds a file that cloud aware applications within the guest instance can access. For example thecloudinitsystem is an open source package from Ubuntu that handles early initialization of a cloud instance that makes use of this user data." +msgstr "" + +#: ./doc/training-guides/module001-ch006-overview-horizon-cli.xml:1581(para) +msgid "Access and security credentials, which include one or both of the following credentials:" +msgstr "" + +#: ./doc/training-guides/module001-ch006-overview-horizon-cli.xml:1587(para) +msgid "A key-pair for your instance, which are SSH credentials that are injected into images when they are launched. For this to work, the image must contain the cloud-init package. Create at least one keypair for each project. If you already have generated a key-pair with an external tool, you can import it into OpenStack. You can use the keypair for multiple instances that belong to that project. For details, refer to Section 1.5.1, Creating or Importing Keys." +msgstr "" + +#: ./doc/training-guides/module001-ch006-overview-horizon-cli.xml:1598(para) +msgid "A security group, which defines which incoming network traffic is forwarded to instances. Security groups hold a set of firewall policies, known as security group rules. For details, see xx." +msgstr "" + +#: ./doc/training-guides/module001-ch006-overview-horizon-cli.xml:1606(para) +msgid "If needed, you can assign a floating (public) IP addressto a running instance and attach a block storage device, or volume, for persistent storage. For details, see Section 1.5.3, Managing IP Addresses and Section 1.7, Managing Volumes." +msgstr "" + +#: ./doc/training-guides/module001-ch006-overview-horizon-cli.xml:1613(para) +msgid "After you gather the parameters you need to launch an instance, you can launch it from animageor avolume." +msgstr "" + +#: ./doc/training-guides/module001-ch006-overview-horizon-cli.xml:1619(para) +msgid "To gather the parameters to launch an instance" +msgstr "" + +#: ./doc/training-guides/module001-ch006-overview-horizon-cli.xml:1622(para) +msgid "On a shell, source the OpenStack RC file." +msgstr "" + +#: ./doc/training-guides/module001-ch006-overview-horizon-cli.xml:1625(para) ./doc/training-guides/module001-ch006-overview-horizon-cli.xml:2026(para) +msgid "List the available flavors:" +msgstr "" + +#: ./doc/training-guides/module001-ch006-overview-horizon-cli.xml:1628(para) ./doc/training-guides/module001-ch006-overview-horizon-cli.xml:2029(para) +msgid "$ nova flavor-list" +msgstr "" + +#: ./doc/training-guides/module001-ch006-overview-horizon-cli.xml:1631(para) +msgid "Note the ID of the flavor that you want to use for your instance." +msgstr "" + +#: ./doc/training-guides/module001-ch006-overview-horizon-cli.xml:1635(para) +msgid "List the available images:" +msgstr "" + +#: ./doc/training-guides/module001-ch006-overview-horizon-cli.xml:1638(para) +msgid "$ nova image-list" +msgstr "" + +#: ./doc/training-guides/module001-ch006-overview-horizon-cli.xml:1641(para) +msgid "You can also filter the image list by using grep to find a specific image, like this:" +msgstr "" + +#: ./doc/training-guides/module001-ch006-overview-horizon-cli.xml:1645(para) +msgid "$ nova image-list | grep 'kernel'" +msgstr "" + +#: ./doc/training-guides/module001-ch006-overview-horizon-cli.xml:1648(para) +msgid "Note the ID of the image that you want to boot your instance from." +msgstr "" + +#: ./doc/training-guides/module001-ch006-overview-horizon-cli.xml:1652(para) +msgid "List the available security groups:" +msgstr "" + +#: ./doc/training-guides/module001-ch006-overview-horizon-cli.xml:1655(para) +msgid "$ nova secgroup-list --all-tenants" +msgstr "" + +#: ./doc/training-guides/module001-ch006-overview-horizon-cli.xml:1658(para) +msgid "If you have not created any security groups, you can assign the instance to only the default security group." +msgstr "" + +#: ./doc/training-guides/module001-ch006-overview-horizon-cli.xml:1663(para) +msgid "You can also list rules for a specified security group:" +msgstr "" + +#: ./doc/training-guides/module001-ch006-overview-horizon-cli.xml:1667(para) +msgid "$ nova secgroup-list-rules default" +msgstr "" + +#: ./doc/training-guides/module001-ch006-overview-horizon-cli.xml:1670(para) +msgid "In this example, the default security group has been modified to allow HTTP traffic on the instance by permitting TCP traffic on Port 80." +msgstr "" + +#: ./doc/training-guides/module001-ch006-overview-horizon-cli.xml:1675(para) +msgid "List the available keypairs." +msgstr "" + +#: ./doc/training-guides/module001-ch006-overview-horizon-cli.xml:1681(para) +msgid "Note the name of the keypair that you use for SSH access." +msgstr "" + +#: ./doc/training-guides/module001-ch006-overview-horizon-cli.xml:1686(para) +msgid "Use this procedure to launch an instance from an image." +msgstr "" + +#: ./doc/training-guides/module001-ch006-overview-horizon-cli.xml:1691(para) +msgid "Now you have all parameters required to launch an instance, run the following command and specify the server name, flavor ID, and image ID. Optionally, you can provide a key name for access control and security group for security. You can also include metadata key and value pairs. For example you can add a description for your server by providing the --meta description=\"My Server\"parameter." +msgstr "" + +#: ./doc/training-guides/module001-ch006-overview-horizon-cli.xml:1701(para) +msgid "You can pass user data in a file on your local system and pass it at instance launch by using the flag --user-data <user-data-file>." +msgstr "" + +#: ./doc/training-guides/module001-ch006-overview-horizon-cli.xml:1706(para) +msgid "$ nova boot --flavor FLAVOR_ID --image IMAGE_ID --key_name KEY_NAME --user-data mydata.file \\ --security_group SEC_GROUP NAME_FOR_INSTANCE --meta KEY=VALUE --meta KEY=VALUE" +msgstr "" + +#: ./doc/training-guides/module001-ch006-overview-horizon-cli.xml:1712(para) +msgid "The command returns a list of server properties, depending on which parameters you provide." +msgstr "" + +#: ./doc/training-guides/module001-ch006-overview-horizon-cli.xml:1716(para) +msgid "A status of BUILD indicates that the instance has started, but is not yet online." +msgstr "" + +#: ./doc/training-guides/module001-ch006-overview-horizon-cli.xml:1720(para) +msgid "A status of ACTIVE indicates that your server is active." +msgstr "" + +#: ./doc/training-guides/module001-ch006-overview-horizon-cli.xml:1724(para) +msgid "Copy the server ID value from the id field in the output. You use this ID to get details for or delete your server." +msgstr "" + +#: ./doc/training-guides/module001-ch006-overview-horizon-cli.xml:1729(para) +msgid "Copy the administrative password value from the adminPass field. You use this value to log into your server." +msgstr "" + +#: ./doc/training-guides/module001-ch006-overview-horizon-cli.xml:1734(para) +msgid "Check if the instance is online:" +msgstr "" + +#: ./doc/training-guides/module001-ch006-overview-horizon-cli.xml:1740(para) +msgid "This command lists all instances of the project you belong to, including their ID, their name, their status, and their private (and if assigned, their public) IP addresses." +msgstr "" + +#: ./doc/training-guides/module001-ch006-overview-horizon-cli.xml:1746(para) +msgid "If the status for the instance is ACTIVE, the instance is online." +msgstr "" + +#: ./doc/training-guides/module001-ch006-overview-horizon-cli.xml:1750(para) +msgid "To view the available options for the nova listcommand, run the following command:" +msgstr "" + +#: ./doc/training-guides/module001-ch006-overview-horizon-cli.xml:1754(para) +msgid "$ nova help list" +msgstr "" + +#: ./doc/training-guides/module001-ch006-overview-horizon-cli.xml:1757(para) +msgid "If you did not provide a keypair, security groups, or rules, you can only access the instance from inside the cloud through VNC. Even pinging the instance is not possible." +msgstr "" + +#: ./doc/training-guides/module001-ch006-overview-horizon-cli.xml:1764(para) +msgid "After youcreate a bootable volume, youlaunch an instance from the volume." +msgstr "" + +#: ./doc/training-guides/module001-ch006-overview-horizon-cli.xml:1772(para) +msgid "To create a bootable volume" +msgstr "" + +#: ./doc/training-guides/module001-ch006-overview-horizon-cli.xml:1775(para) +msgid "To create a volume from an image, run the following command:" +msgstr "" + +#: ./doc/training-guides/module001-ch006-overview-horizon-cli.xml:1779(para) +msgid "# cinder create --image-id 397e713c-b95b-4186-ad46-6126863ea0a9 --display-name my-bootable-vol 8" +msgstr "" + +#: ./doc/training-guides/module001-ch006-overview-horizon-cli.xml:1784(para) +msgid "Optionally, to configure your volume, see the Configuring Image Service and Storage for Computechapter in the OpenStack Configuration Reference." +msgstr "" + +#: ./doc/training-guides/module001-ch006-overview-horizon-cli.xml:1789(para) +msgid "To list volumes" +msgstr "" + +#: ./doc/training-guides/module001-ch006-overview-horizon-cli.xml:1792(para) +msgid "Enter the following command:" +msgstr "" + +#: ./doc/training-guides/module001-ch006-overview-horizon-cli.xml:1795(para) ./doc/training-guides/module001-ch006-overview-horizon-cli.xml:1886(para) +msgid "$ nova volume-list" +msgstr "" + +#: ./doc/training-guides/module001-ch006-overview-horizon-cli.xml:1798(para) +msgid "Copy the value in the ID field for your volume." +msgstr "" + +#: ./doc/training-guides/module001-ch006-overview-horizon-cli.xml:1803(para) +msgid "To launch an instance" +msgstr "" + +#: ./doc/training-guides/module001-ch006-overview-horizon-cli.xml:1806(para) +msgid "Enter the nova boot command with the --block_device_mapping parameter, as follows:" +msgstr "" + +#: ./doc/training-guides/module001-ch006-overview-horizon-cli.xml:1810(para) +msgid "$ nova boot --flavor <flavor> --block_device_mapping <dev_name>=<id>:<type>:<size>:<delete_on_terminate> <name>" +msgstr "" + +#: ./doc/training-guides/module001-ch006-overview-horizon-cli.xml:1816(para) +msgid "The command arguments are:" +msgstr "" + +#: ./doc/training-guides/module001-ch006-overview-horizon-cli.xml:1819(para) +msgid "--flavor flavor" +msgstr "" + +#: ./doc/training-guides/module001-ch006-overview-horizon-cli.xml:1822(para) +msgid "The flavor ID." +msgstr "" + +#: ./doc/training-guides/module001-ch006-overview-horizon-cli.xml:1825(para) +msgid "--block_device_mapping dev- name=id:type:size:delete-on-terminate" +msgstr "" + +#: ./doc/training-guides/module001-ch006-overview-horizon-cli.xml:1831(para) +msgid "dev-name. A device name where the volume is attached in the system at /dev/dev_name. This value is typically vda." +msgstr "" + +#: ./doc/training-guides/module001-ch006-overview-horizon-cli.xml:1836(para) +msgid "id. The ID of the volume to boot from, as shown in the output of nova volume-list." +msgstr "" + +#: ./doc/training-guides/module001-ch006-overview-horizon-cli.xml:1840(para) +msgid "type. Either snap or any other value, including a blank string. snap means that the volume was created from a snapshot." +msgstr "" + +#: ./doc/training-guides/module001-ch006-overview-horizon-cli.xml:1845(para) +msgid "size. The size of the volume, in GBs. It is safe to leave this blank and have the Compute service infer the size." +msgstr "" + +#: ./doc/training-guides/module001-ch006-overview-horizon-cli.xml:1850(para) +msgid "delete-on-terminate. A boolean that indicates whether the volume should be deleted when the instance is terminated. You can specify" +msgstr "" + +#: ./doc/training-guides/module001-ch006-overview-horizon-cli.xml:1857(para) +msgid "True or 1" +msgstr "" + +#: ./doc/training-guides/module001-ch006-overview-horizon-cli.xml:1860(para) +msgid "False or 0" +msgstr "" + +#: ./doc/training-guides/module001-ch006-overview-horizon-cli.xml:1863(para) +msgid "name" +msgstr "" + +#: ./doc/training-guides/module001-ch006-overview-horizon-cli.xml:1866(para) +msgid "The name for the server." +msgstr "" + +#: ./doc/training-guides/module001-ch006-overview-horizon-cli.xml:1869(para) +msgid "For example, you might enter the following command to boot from a volume with ID bd7cf584-45de-44e3-bf7f-f7b50bf235e. The volume is not deleted when the instance is terminated:" +msgstr "" + +#: ./doc/training-guides/module001-ch006-overview-horizon-cli.xml:1875(para) +msgid "$ nova boot --flavor 2 --image 397e713c-b95b-4186-ad46-6126863ea0a9 --block_device_mapping vda=bd7cf584-45de-44e3-bf7f-f7b50bf235e3:::0 myInstanceFromVolume" +msgstr "" + +#: ./doc/training-guides/module001-ch006-overview-horizon-cli.xml:1882(para) +msgid "Now when you list volumes, you can see that the volume is attached to a server:" +msgstr "" + +#: ./doc/training-guides/module001-ch006-overview-horizon-cli.xml:1889(para) +msgid "Additionally, when you list servers, you see the server that you booted from a volume:" +msgstr "" + +#: ./doc/training-guides/module001-ch006-overview-horizon-cli.xml:1896(guilabel) +msgid "Manage instances and hosts" +msgstr "" + +#: ./doc/training-guides/module001-ch006-overview-horizon-cli.xml:1899(guilabel) +msgid "Manage IP addresses" +msgstr "" + +#: ./doc/training-guides/module001-ch006-overview-horizon-cli.xml:1900(para) +msgid "Each instance can have a private, or fixed, IP address and a public, or floating, one." +msgstr "" + +#: ./doc/training-guides/module001-ch006-overview-horizon-cli.xml:1902(para) +msgid "Private IP addresses are used for communication between instances, and public ones are used for communication with the outside world." +msgstr "" + +#: ./doc/training-guides/module001-ch006-overview-horizon-cli.xml:1905(para) +msgid "When you launch an instance, it is automatically assigned a private IP address that stays the same until you explicitly terminate the instance. Rebooting an instance has no effect on the private IP address." +msgstr "" + +#: ./doc/training-guides/module001-ch006-overview-horizon-cli.xml:1909(para) +msgid "A pool of floating IPs, configured by the cloud operator, is available in OpenStack Compute." +msgstr "" + +#: ./doc/training-guides/module001-ch006-overview-horizon-cli.xml:1911(para) +msgid "You can allocate a certain number of these to a project: The maximum number of floating IP addresses per project is defined by the quota." +msgstr "" + +#: ./doc/training-guides/module001-ch006-overview-horizon-cli.xml:1914(para) +msgid "You can add a floating IP address from this set to an instance of the project. Floating IP addresses can be dynamically disassociated and associated with other instances of the same project at any time." +msgstr "" + +#: ./doc/training-guides/module001-ch006-overview-horizon-cli.xml:1918(para) +msgid "Before you can assign a floating IP address to an instance, you first must allocate floating IPs to a project. After floating IP addresses have been allocated to the current project, you can assign them to running instances." +msgstr "" + +#: ./doc/training-guides/module001-ch006-overview-horizon-cli.xml:1922(para) +msgid "One floating IP address can be assigned to only one instance at a time. Floating IP addresses can be managed with the nova *floating-ip-*commands, provided by the python-novaclient package." +msgstr "" + +#: ./doc/training-guides/module001-ch006-overview-horizon-cli.xml:1926(para) +msgid "To list pools with floating IP addresses" +msgstr "" + +#: ./doc/training-guides/module001-ch006-overview-horizon-cli.xml:1929(para) +msgid "To list all pools that provide floating IP addresses:" +msgstr "" + +#: ./doc/training-guides/module001-ch006-overview-horizon-cli.xml:1933(para) ./doc/training-guides/module001-ch006-overview-horizon-cli.xml:1944(para) +msgid "$ nova floating-ip-pool-list" +msgstr "" + +#: ./doc/training-guides/module001-ch006-overview-horizon-cli.xml:1936(para) +msgid "To allocate a floating IP address to the current project" +msgstr "" + +#: ./doc/training-guides/module001-ch006-overview-horizon-cli.xml:1940(para) +msgid "The output of the following command shows the freshly allocated IP address:" +msgstr "" + +#: ./doc/training-guides/module001-ch006-overview-horizon-cli.xml:1947(para) +msgid "If more than one pool of IP addresses is available, you can also specify the pool from which to allocate the IP address:" +msgstr "" + +#: ./doc/training-guides/module001-ch006-overview-horizon-cli.xml:1952(para) +msgid "$ floating-ip-create POOL_NAME" +msgstr "" + +#: ./doc/training-guides/module001-ch006-overview-horizon-cli.xml:1955(para) +msgid "To list floating IP addresses allocated to the current project" +msgstr "" + +#: ./doc/training-guides/module001-ch006-overview-horizon-cli.xml:1959(para) +msgid "If an IP is already associated with an instance, the output also shows the IP for the instance, thefixed IP address for the instance, and the name of the pool that provides the floating IP address." +msgstr "" + +#: ./doc/training-guides/module001-ch006-overview-horizon-cli.xml:1965(para) ./doc/training-guides/module001-ch006-overview-horizon-cli.xml:1989(para) +msgid "$ nova floating-ip-list" +msgstr "" + +#: ./doc/training-guides/module001-ch006-overview-horizon-cli.xml:1968(para) +msgid "To release a floating IP address from the current project" +msgstr "" + +#: ./doc/training-guides/module001-ch006-overview-horizon-cli.xml:1972(para) +msgid "The IP address is returned to the pool of IP addresses that are available for all projects. If an IP address is currently assigned to a running instance, it is automatically disassociated from the instance." +msgstr "" + +#: ./doc/training-guides/module001-ch006-overview-horizon-cli.xml:1978(para) +msgid "$ nova floating-ip-delete FLOATING_IP" +msgstr "" + +#: ./doc/training-guides/module001-ch006-overview-horizon-cli.xml:1981(para) +msgid "To assign a floating IP address to an instance" +msgstr "" + +#: ./doc/training-guides/module001-ch006-overview-horizon-cli.xml:1984(para) +msgid "To associate an IP address with an instance, one or multiple floating IP addresses must be allocated to the current project. Check this with:" +msgstr "" + +#: ./doc/training-guides/module001-ch006-overview-horizon-cli.xml:1992(para) +msgid "In addition, you must know the instance's name (or ID). To look up the instances that belong to the current project, use the nova list command." +msgstr "" + +#: ./doc/training-guides/module001-ch006-overview-horizon-cli.xml:1997(para) +msgid "$ nova add-floating-ip INSTANCE_NAME_OR_ID FLOATING_IP" +msgstr "" + +#: ./doc/training-guides/module001-ch006-overview-horizon-cli.xml:2001(para) +msgid "After you assign the IP with nova add-floating-ipand configure security group rules for the instance, the instance is publicly available at the floating IP address." +msgstr "" + +#: ./doc/training-guides/module001-ch006-overview-horizon-cli.xml:2007(para) +msgid "To remove a floating IP address from an instance" +msgstr "" + +#: ./doc/training-guides/module001-ch006-overview-horizon-cli.xml:2010(para) +msgid "To remove a floating IP address from an instance, you must specify the same arguments that you used to assign the IP." +msgstr "" + +#: ./doc/training-guides/module001-ch006-overview-horizon-cli.xml:2015(para) +msgid "$ nova remove-floating-ip INSTANCE_NAME_OR_ID FLOATING_IP" +msgstr "" + +#: ./doc/training-guides/module001-ch006-overview-horizon-cli.xml:2019(guilabel) +msgid "Change the size of your server" +msgstr "" + +#: ./doc/training-guides/module001-ch006-overview-horizon-cli.xml:2021(para) +msgid "You change the size of a server by changing its flavor." +msgstr "" + +#: ./doc/training-guides/module001-ch006-overview-horizon-cli.xml:2023(para) +msgid "To change the size of your server" +msgstr "" + +#: ./doc/training-guides/module001-ch006-overview-horizon-cli.xml:2032(para) +msgid "Show information about your server, including its size:" +msgstr "" + +#: ./doc/training-guides/module001-ch006-overview-horizon-cli.xml:2036(para) +msgid "$ nova show myCirrosServer" +msgstr "" + +#: ./doc/training-guides/module001-ch006-overview-horizon-cli.xml:2039(para) +msgid "The size of the server is m1.small (2)." +msgstr "" + +#: ./doc/training-guides/module001-ch006-overview-horizon-cli.xml:2042(para) +msgid "To resize the server, pass the server ID and the desired flavor to the nova resizecommand. Include the --poll parameter to report the resize progress." +msgstr "" + +#: ./doc/training-guides/module001-ch006-overview-horizon-cli.xml:2047(para) +msgid "$ nova resize myCirrosServer 4 --poll" +msgstr "" + +#: ./doc/training-guides/module001-ch006-overview-horizon-cli.xml:2050(para) +msgid "Instance resizing... 100% completeFinished" +msgstr "" + +#: ./doc/training-guides/module001-ch006-overview-horizon-cli.xml:2053(para) +msgid "Show the status for your server:" +msgstr "" + +#: ./doc/training-guides/module001-ch006-overview-horizon-cli.xml:2059(para) +msgid "When the resize completes, the status becomes VERIFY_RESIZE. To confirm the resize:" +msgstr "" + +#: ./doc/training-guides/module001-ch006-overview-horizon-cli.xml:2063(para) +msgid "$ nova resize-confirm 6beefcf7-9de6-48b3-9ba9-e11b343189b3" +msgstr "" + +#: ./doc/training-guides/module001-ch006-overview-horizon-cli.xml:2067(para) ./doc/training-guides/module001-ch006-overview-horizon-cli.xml:2078(para) +msgid "The server status becomes ACTIVE." +msgstr "" + +#: ./doc/training-guides/module001-ch006-overview-horizon-cli.xml:2070(para) +msgid "If the resize fails or does not work as expected, you can revert the resize:" +msgstr "" + +#: ./doc/training-guides/module001-ch006-overview-horizon-cli.xml:2074(para) +msgid "$ nova resize-revert 6beefcf7-9de6-48b3-9ba9-e11b343189b3" +msgstr "" + +#: ./doc/training-guides/module001-ch006-overview-horizon-cli.xml:2081(guilabel) +msgid "Stop and start an instance" +msgstr "" + +#: ./doc/training-guides/module001-ch006-overview-horizon-cli.xml:2082(para) +msgid "Use one of the following methods to stop and start an instance." +msgstr "" + +#: ./doc/training-guides/module001-ch006-overview-horizon-cli.xml:2084(guilabel) +msgid "Pause and un-pause an instance" +msgstr "" + +#: ./doc/training-guides/module001-ch006-overview-horizon-cli.xml:2085(para) +msgid "To pause and un-pause a server" +msgstr "" + +#: ./doc/training-guides/module001-ch006-overview-horizon-cli.xml:2088(para) +msgid "To pause a server, run the following command:" +msgstr "" + +#: ./doc/training-guides/module001-ch006-overview-horizon-cli.xml:2091(para) +msgid "$ nova pause SERVER" +msgstr "" + +#: ./doc/training-guides/module001-ch006-overview-horizon-cli.xml:2094(para) +msgid "This command stores the state of the VM in RAM. A paused instance continues to run in a frozen state." +msgstr "" + +#: ./doc/training-guides/module001-ch006-overview-horizon-cli.xml:2099(para) +msgid "To un-pause the server, run the following command:" +msgstr "" + +#: ./doc/training-guides/module001-ch006-overview-horizon-cli.xml:2103(para) +msgid "$ nova unpause SERVER" +msgstr "" + +#: ./doc/training-guides/module001-ch006-overview-horizon-cli.xml:2106(guilabel) +msgid "Suspend and resume an instance" +msgstr "" + +#: ./doc/training-guides/module001-ch006-overview-horizon-cli.xml:2107(para) +msgid "To suspend and resume a server" +msgstr "" + +#: ./doc/training-guides/module001-ch006-overview-horizon-cli.xml:2108(para) +msgid "Administrative users might want to suspend an infrequently used instance or to perform system maintenance." +msgstr "" + +#: ./doc/training-guides/module001-ch006-overview-horizon-cli.xml:2113(para) +msgid "When you suspend an instance, its VM state is stored on disk, all memory is written to disk, and the virtual machine is stopped. Suspending an instance is similar to placing a device in hibernation; memory and vCPUs become available." +msgstr "" + +#: ./doc/training-guides/module001-ch006-overview-horizon-cli.xml:2120(para) +msgid "To initiate a hypervisor-level suspend operation, run the following command:" +msgstr "" + +#: ./doc/training-guides/module001-ch006-overview-horizon-cli.xml:2124(para) +msgid "$ nova suspend SERVER" +msgstr "" + +#: ./doc/training-guides/module001-ch006-overview-horizon-cli.xml:2127(para) +msgid "To resume a suspended server:" +msgstr "" + +#: ./doc/training-guides/module001-ch006-overview-horizon-cli.xml:2130(para) +msgid "$ nova resume SERVER" +msgstr "" + +#: ./doc/training-guides/module001-ch006-overview-horizon-cli.xml:2133(guilabel) +msgid "Reboot an instance" +msgstr "" + +#: ./doc/training-guides/module001-ch006-overview-horizon-cli.xml:2134(para) +msgid "You can perform a soft or hard reboot of a running instance. A soft reboot attempts a graceful shutdown and restart of the instance. A hard reboot power cycles the instance." +msgstr "" + +#: ./doc/training-guides/module001-ch006-overview-horizon-cli.xml:2138(para) +msgid "To reboot a server" +msgstr "" + +#: ./doc/training-guides/module001-ch006-overview-horizon-cli.xml:2141(para) +msgid "By default, when you reboot a server, it is a soft reboot." +msgstr "" + +#: ./doc/training-guides/module001-ch006-overview-horizon-cli.xml:2145(para) +msgid "$ nova reboot SERVER" +msgstr "" + +#: ./doc/training-guides/module001-ch006-overview-horizon-cli.xml:2148(para) +msgid "To perform a hard reboot, pass the --hard parameter, as follows:" +msgstr "" + +#: ./doc/training-guides/module001-ch006-overview-horizon-cli.xml:2150(para) +msgid "$ nova reboot --hard SERVER" +msgstr "" + +#: ./doc/training-guides/module001-ch006-overview-horizon-cli.xml:2151(guilabel) +msgid "Evacuate instances" +msgstr "" + +#: ./doc/training-guides/module001-ch006-overview-horizon-cli.xml:2152(para) +msgid "If a cloud compute node fails due to a hardware malfunction or another reason, you can evacuate instances to make them available again." +msgstr "" + +#: ./doc/training-guides/module001-ch006-overview-horizon-cli.xml:2155(para) +msgid "You can choose evacuation parameters for your use case." +msgstr "" + +#: ./doc/training-guides/module001-ch006-overview-horizon-cli.xml:2157(para) +msgid "To preserve user data on server disk, you must configure shared storage on the target host. Also, you must validate that the current VM host is down. Otherwise the evacuation fails with an error." +msgstr "" + +#: ./doc/training-guides/module001-ch006-overview-horizon-cli.xml:2161(para) +msgid "To evacuate your server" +msgstr "" + +#: ./doc/training-guides/module001-ch006-overview-horizon-cli.xml:2164(para) +msgid "To find a different host for the evacuated instance, run the following command to lists hosts:" +msgstr "" + +#: ./doc/training-guides/module001-ch006-overview-horizon-cli.xml:2168(para) ./doc/training-guides/module001-ch006-overview-horizon-cli.xml:2345(para) +msgid "$ nova host-list" +msgstr "" + +#: ./doc/training-guides/module001-ch006-overview-horizon-cli.xml:2171(para) +msgid "You can pass the instance password to the command by using the --password <pwd> option. If you do not specify a password, one is generated and printed after the command finishes successfully. The following command evacuates a server without shared storage:" +msgstr "" + +#: ./doc/training-guides/module001-ch006-overview-horizon-cli.xml:2178(para) +msgid "$ nova evacuate evacuated_server_name host_b" +msgstr "" + +#: ./doc/training-guides/module001-ch006-overview-horizon-cli.xml:2181(para) +msgid "The command evacuates an instance from a down host to a specified host. The instance is booted from a new disk, but preserves its configuration including its ID, name, uid, IP address, and so on. The command returns a password:" +msgstr "" + +#: ./doc/training-guides/module001-ch006-overview-horizon-cli.xml:2188(para) +msgid "To preserve the user disk data on the evacuated server, deploy OpenStack Compute with shared filesystem." +msgstr "" + +#: ./doc/training-guides/module001-ch006-overview-horizon-cli.xml:2193(para) +msgid "$ nova evacuate evacuated_server_name host_b --on-shared-storage" +msgstr "" + +#: ./doc/training-guides/module001-ch006-overview-horizon-cli.xml:2197(guilabel) +msgid "Delete an instance" +msgstr "" + +#: ./doc/training-guides/module001-ch006-overview-horizon-cli.xml:2198(para) +msgid "When you no longer need an instance, you can delete it." +msgstr "" + +#: ./doc/training-guides/module001-ch006-overview-horizon-cli.xml:2200(para) +msgid "To delete an instance" +msgstr "" + +#: ./doc/training-guides/module001-ch006-overview-horizon-cli.xml:2203(para) +msgid "List all instances:" +msgstr "" + +#: ./doc/training-guides/module001-ch006-overview-horizon-cli.xml:2209(para) +msgid "Use the following command to delete the newServer instance, which is in ERROR state:" +msgstr "" + +#: ./doc/training-guides/module001-ch006-overview-horizon-cli.xml:2213(para) +msgid "$ nova delete newServer" +msgstr "" + +#: ./doc/training-guides/module001-ch006-overview-horizon-cli.xml:2216(para) +msgid "The command does not notify that your server was deleted." +msgstr "" + +#: ./doc/training-guides/module001-ch006-overview-horizon-cli.xml:2220(para) +msgid "Instead, run the nova list command:" +msgstr "" + +#: ./doc/training-guides/module001-ch006-overview-horizon-cli.xml:2226(para) +msgid "The deleted instance does not appear in the list." +msgstr "" + +#: ./doc/training-guides/module001-ch006-overview-horizon-cli.xml:2230(guilabel) +msgid "Get a console to an instance" +msgstr "" + +#: ./doc/training-guides/module001-ch006-overview-horizon-cli.xml:2231(para) +msgid "To get a console to an instance" +msgstr "" + +#: ./doc/training-guides/module001-ch006-overview-horizon-cli.xml:2232(para) +msgid "To get a VNC console to an instance, run the following command:" +msgstr "" + +#: ./doc/training-guides/module001-ch006-overview-horizon-cli.xml:2234(para) +msgid "$ nova get-vnc-console myCirrosServer xvpvnc" +msgstr "" + +#: ./doc/training-guides/module001-ch006-overview-horizon-cli.xml:2235(para) +msgid "The command returns a URL from which you can access your instance:" +msgstr "" + +#: ./doc/training-guides/module001-ch006-overview-horizon-cli.xml:2237(guilabel) +msgid "Manage bare metal nodes" +msgstr "" + +#: ./doc/training-guides/module001-ch006-overview-horizon-cli.xml:2238(para) +msgid "If you use the bare metal driver, you must create a bare metal node and add a network interface to it. You then launch an instance from a bare metal image. You can list and delete bare metal nodes. When you delete a node, any associated network interfaces are removed. You can list and remove network interfaces that are associated with a bare metal node." +msgstr "" + +#: ./doc/training-guides/module001-ch006-overview-horizon-cli.xml:2245(para) +msgid "Commands" +msgstr "" + +#: ./doc/training-guides/module001-ch006-overview-horizon-cli.xml:2248(para) +msgid "baremetal-interface-add" +msgstr "" + +#: ./doc/training-guides/module001-ch006-overview-horizon-cli.xml:2251(para) +msgid "Adds a network interface to a bare metal node." +msgstr "" + +#: ./doc/training-guides/module001-ch006-overview-horizon-cli.xml:2254(para) +msgid "baremetal-interface-list" +msgstr "" + +#: ./doc/training-guides/module001-ch006-overview-horizon-cli.xml:2257(para) +msgid "Lists network interfaces associated with a bare metal node." +msgstr "" + +#: ./doc/training-guides/module001-ch006-overview-horizon-cli.xml:2261(para) +msgid "baremetal-interface-remove" +msgstr "" + +#: ./doc/training-guides/module001-ch006-overview-horizon-cli.xml:2264(para) +msgid "Removes a network interface from a bare metal node." +msgstr "" + +#: ./doc/training-guides/module001-ch006-overview-horizon-cli.xml:2268(para) +msgid "baremetal-node-create" +msgstr "" + +#: ./doc/training-guides/module001-ch006-overview-horizon-cli.xml:2271(para) +msgid "Creates a bare metal node." +msgstr "" + +#: ./doc/training-guides/module001-ch006-overview-horizon-cli.xml:2274(para) +msgid "baremetal-node-delete" +msgstr "" + +#: ./doc/training-guides/module001-ch006-overview-horizon-cli.xml:2277(para) +msgid "Removes a bare metal node and any associated interfaces." +msgstr "" + +#: ./doc/training-guides/module001-ch006-overview-horizon-cli.xml:2281(para) +msgid "baremetal-node-list" +msgstr "" + +#: ./doc/training-guides/module001-ch006-overview-horizon-cli.xml:2284(para) +msgid "Lists available bare metal nodes." +msgstr "" + +#: ./doc/training-guides/module001-ch006-overview-horizon-cli.xml:2287(para) +msgid "baremetal-node-show" +msgstr "" + +#: ./doc/training-guides/module001-ch006-overview-horizon-cli.xml:2290(para) +msgid "Shows information about a bare metal node." +msgstr "" + +#: ./doc/training-guides/module001-ch006-overview-horizon-cli.xml:2293(para) +msgid "To manage bare metal nodes" +msgstr "" + +#: ./doc/training-guides/module001-ch006-overview-horizon-cli.xml:2296(para) +msgid "Create a bare metal node." +msgstr "" + +#: ./doc/training-guides/module001-ch006-overview-horizon-cli.xml:2299(para) +msgid "$ nova baremetal-node-create --pm_address=1.2.3.4 --pm_user=ipmi --pm_password=ipmi $(hostname -f) 1 512 10 aa:bb:cc:dd:ee:ff" +msgstr "" + +#: ./doc/training-guides/module001-ch006-overview-horizon-cli.xml:2304(para) +msgid "Add network interface information to the node:" +msgstr "" + +#: ./doc/training-guides/module001-ch006-overview-horizon-cli.xml:2307(para) +msgid "$ nova baremetal-interface-add 1 aa:bb:cc:dd:ee:ff" +msgstr "" + +#: ./doc/training-guides/module001-ch006-overview-horizon-cli.xml:2311(para) +msgid "Launch an instance from a bare metal image:" +msgstr "" + +#: ./doc/training-guides/module001-ch006-overview-horizon-cli.xml:2314(para) +msgid "$ nova boot --image my-baremetal-image --flavor my-baremetal-flavor test" +msgstr "" + +#: ./doc/training-guides/module001-ch006-overview-horizon-cli.xml:2318(para) +msgid "|... wait for instance to become active ..." +msgstr "" + +#: ./doc/training-guides/module001-ch006-overview-horizon-cli.xml:2321(para) +msgid "You can list bare metal nodes and interfaces. When a node is in use, its status includes the UUID of the instance that runs on it:" +msgstr "" + +#: ./doc/training-guides/module001-ch006-overview-horizon-cli.xml:2326(para) +msgid "$ nova baremetal-node-list" +msgstr "" + +#: ./doc/training-guides/module001-ch006-overview-horizon-cli.xml:2329(para) +msgid "Show details about a bare metal node:" +msgstr "" + +#: ./doc/training-guides/module001-ch006-overview-horizon-cli.xml:2332(para) +msgid "$ nova baremetal-node-show 1" +msgstr "" + +#: ./doc/training-guides/module001-ch006-overview-horizon-cli.xml:2335(guilabel) +msgid "Show usage statistics for hosts and instances" +msgstr "" + +#: ./doc/training-guides/module001-ch006-overview-horizon-cli.xml:2336(para) +msgid "You can show basic statistics on resource usage for hosts and instances." +msgstr "" + +#: ./doc/training-guides/module001-ch006-overview-horizon-cli.xml:2338(para) +msgid "To show host usage statistics" +msgstr "" + +#: ./doc/training-guides/module001-ch006-overview-horizon-cli.xml:2341(para) +msgid "List the hosts and the nova-related services that run on them:" +msgstr "" + +#: ./doc/training-guides/module001-ch006-overview-horizon-cli.xml:2348(para) +msgid "Get a summary of resource usage of all of the instances running on the host." +msgstr "" + +#: ./doc/training-guides/module001-ch006-overview-horizon-cli.xml:2352(para) +msgid "$ nova host-describe devstack-grizzly" +msgstr "" + +#: ./doc/training-guides/module001-ch006-overview-horizon-cli.xml:2355(para) +msgid "The cpu column shows the sum of the virtual CPUs for instances running on the host." +msgstr "" + +#: ./doc/training-guides/module001-ch006-overview-horizon-cli.xml:2359(para) +msgid "The memory_mb column shows the sum of the memory (in MB) allocated to the instances that run on the hosts." +msgstr "" + +#: ./doc/training-guides/module001-ch006-overview-horizon-cli.xml:2364(para) +msgid "The disk_gb column shows the sum of the root and ephemeral disk sizes (in GB) of the instances that run on the hosts." +msgstr "" + +#: ./doc/training-guides/module001-ch006-overview-horizon-cli.xml:2369(para) +msgid "To show instance usage statistics" +msgstr "" + +#: ./doc/training-guides/module001-ch006-overview-horizon-cli.xml:2372(para) +msgid "Get CPU, memory, I/O, and network statistics for an instance." +msgstr "" + +#: ./doc/training-guides/module001-ch006-overview-horizon-cli.xml:2376(para) +msgid "First, list instances:" +msgstr "" + +#: ./doc/training-guides/module001-ch006-overview-horizon-cli.xml:2382(para) +msgid "Then, get diagnostic statistics:" +msgstr "" + +#: ./doc/training-guides/module001-ch006-overview-horizon-cli.xml:2385(para) +msgid "$ nova diagnostics myCirrosServer" +msgstr "" + +#: ./doc/training-guides/module001-ch006-overview-horizon-cli.xml:2388(para) +msgid "Get summary statistics for each tenant:" +msgstr "" + +#: ./doc/training-guides/module001-ch006-overview-horizon-cli.xml:2391(para) +msgid "$ nova usage-list" +msgstr "" + +#: ./doc/training-guides/module001-ch006-overview-horizon-cli.xml:2394(para) +msgid "Usage from 2013-06-25 to 2013-07-24:" +msgstr "" + +#: ./doc/training-guides/module001-ch006-overview-horizon-cli.xml:2397(guilabel) +msgid "Create and manage networks" +msgstr "" + +#: ./doc/training-guides/module001-ch006-overview-horizon-cli.xml:2398(para) +msgid "Before you run commands, set the following environment variables:" +msgstr "" + +#: ./doc/training-guides/module001-ch006-overview-horizon-cli.xml:2400(para) +msgid "export OS_USERNAME=adminexport OS_PASSWORD=passwordexport OS_TENANT_NAME=adminexport OS_AUTH_URL=http://localhost:5000/v2.0" +msgstr "" + +#: ./doc/training-guides/module001-ch006-overview-horizon-cli.xml:2403(para) +msgid "To create and manage networks" +msgstr "" + +#: ./doc/training-guides/module001-ch006-overview-horizon-cli.xml:2406(para) +msgid "List the extensions of the system:" +msgstr "" + +#: ./doc/training-guides/module001-ch006-overview-horizon-cli.xml:2409(para) +msgid "$ neutron ext-list -c alias -c name" +msgstr "" + +#: ./doc/training-guides/module001-ch006-overview-horizon-cli.xml:2412(para) +msgid "Create a network:" +msgstr "" + +#: ./doc/training-guides/module001-ch006-overview-horizon-cli.xml:2415(para) +msgid "$ neutron net-create net1" +msgstr "" + +#: ./doc/training-guides/module001-ch006-overview-horizon-cli.xml:2418(para) ./doc/training-guides/module001-ch006-overview-horizon-cli.xml:2429(para) +msgid "Created a new network:" +msgstr "" + +#: ./doc/training-guides/module001-ch006-overview-horizon-cli.xml:2421(para) +msgid "Create a network with specified provider network type:" +msgstr "" + +#: ./doc/training-guides/module001-ch006-overview-horizon-cli.xml:2425(para) +msgid "$ neutron net-create net2 --provider:network-type local" +msgstr "" + +#: ./doc/training-guides/module001-ch006-overview-horizon-cli.xml:2432(para) +msgid "Just as shown previous, the unknown option --provider:network-type is used to create a local provider network." +msgstr "" + +#: ./doc/training-guides/module001-ch006-overview-horizon-cli.xml:2437(para) +msgid "Create a subnet:" +msgstr "" + +#: ./doc/training-guides/module001-ch006-overview-horizon-cli.xml:2440(para) +msgid "$ neutron subnet-create net1 192.168.2.0/24 --name subnet1" +msgstr "" + +#: ./doc/training-guides/module001-ch006-overview-horizon-cli.xml:2444(para) +msgid "Created a new subnet:" +msgstr "" + +#: ./doc/training-guides/module001-ch006-overview-horizon-cli.xml:2447(para) +msgid "In the previous command, net1 is the network name, 192.168.2.0/24 is the subnet's CIDR. They are positional arguments. --name subnet1 is an unknown option, which specifies the subnet's name." +msgstr "" + +#: ./doc/training-guides/module001-ch006-overview-horizon-cli.xml:2453(para) +msgid "Create a port with specified IP address:" +msgstr "" + +#: ./doc/training-guides/module001-ch006-overview-horizon-cli.xml:2456(para) +msgid "$ neutron port-create net1 --fixed-ip ip_address=192.168.2.40" +msgstr "" + +#: ./doc/training-guides/module001-ch006-overview-horizon-cli.xml:2460(para) ./doc/training-guides/module001-ch006-overview-horizon-cli.xml:2475(para) +msgid "Created a new port:" +msgstr "" + +#: ./doc/training-guides/module001-ch006-overview-horizon-cli.xml:2463(para) +msgid "In the previous command, net1 is the network name, which is a positional argument. --fixed-ip ip_address=192.168.2.40 is an option, which specifies the port's fixed IP address we wanted." +msgstr "" + +#: ./doc/training-guides/module001-ch006-overview-horizon-cli.xml:2469(para) +msgid "Create a port without specified IP address:" +msgstr "" + +#: ./doc/training-guides/module001-ch006-overview-horizon-cli.xml:2472(para) +msgid "$ neutron port-create net1" +msgstr "" + +#: ./doc/training-guides/module001-ch006-overview-horizon-cli.xml:2478(para) +msgid "We can see that the system will allocate one IP address if we don't specify the IP address in command line." +msgstr "" + +#: ./doc/training-guides/module001-ch006-overview-horizon-cli.xml:2482(para) +msgid "Query ports with specified fixed IP addresses:" +msgstr "" + +#: ./doc/training-guides/module001-ch006-overview-horizon-cli.xml:2485(para) +msgid "$ neutron port-list --fixed-ips ip_address=192.168.2.2 ip_address=192.168.2.40" +msgstr "" + +#: ./doc/training-guides/module001-ch006-overview-horizon-cli.xml:2489(para) +msgid "--fixed-ips ip_address=192.168.2.2 ip_address=192.168.2.40 is one unknown option." +msgstr "" + +#: ./doc/training-guides/module001-ch006-overview-horizon-cli.xml:2493(para) +msgid "How to find unknown options?The unknown options can be easily found by watching the output of create_xxx or show_xxx command. For example, in the port creation command, we see the fixed_ips fields, which can be used as an unknown option." +msgstr "" + +#: ./doc/training-guides/module001-ch006-overview-horizon-cli.xml:2500(guilabel) +msgid "Create and manage stacks" +msgstr "" + +#: ./doc/training-guides/module001-ch006-overview-horizon-cli.xml:2501(para) +msgid "To create a stack from an example template file" +msgstr "" + +#: ./doc/training-guides/module001-ch006-overview-horizon-cli.xml:2504(para) +msgid "To create a stack, or template, from anexample template file, run following command:" +msgstr "" + +#: ./doc/training-guides/module001-ch006-overview-horizon-cli.xml:2510(para) +msgid "$ heat stack-create mystack --template-file=/path/to/heat/templates/WordPress_Single_Instance.template--parameters=\"InstanceType=m1.large;DBUsername=wp;DBPassword=verybadpassword;KeyName=heat_key;LinuxDistribution=F17\"" +msgstr "" + +#: ./doc/training-guides/module001-ch006-overview-horizon-cli.xml:2514(para) +msgid "The --parameters values that you specify depend on which parameters are defined in the template. If the template file is hosted on a website, you can specify the URL with --template-url parameter instead of the --template-file parameter." +msgstr "" + +#: ./doc/training-guides/module001-ch006-overview-horizon-cli.xml:2521(para) +msgid "The command returns the following output:" +msgstr "" + +#: ./doc/training-guides/module001-ch006-overview-horizon-cli.xml:2524(para) +msgid "You can also use the stack-createcommand to validate a template file without creating a stack from it." +msgstr "" + +#: ./doc/training-guides/module001-ch006-overview-horizon-cli.xml:2528(para) +msgid "To do so, run the following command:" +msgstr "" + +#: ./doc/training-guides/module001-ch006-overview-horizon-cli.xml:2531(para) +msgid "$ heat stack-create mystack --template-file=/path/to/heat/templates/WordPress_Single_Instance.template" +msgstr "" + +#: ./doc/training-guides/module001-ch006-overview-horizon-cli.xml:2535(para) +msgid "If validation fails, the response returns an error message." +msgstr "" + +#: ./doc/training-guides/module001-ch006-overview-horizon-cli.xml:2539(para) +msgid "To list stacks" +msgstr "" + +#: ./doc/training-guides/module001-ch006-overview-horizon-cli.xml:2542(para) +msgid "To see which stacks are visible to the current user, run the following command:" +msgstr "" + +#: ./doc/training-guides/module001-ch006-overview-horizon-cli.xml:2546(para) +msgid "$ heat stack-list" +msgstr "" + +#: ./doc/training-guides/module001-ch006-overview-horizon-cli.xml:2549(para) +msgid "To view stack details" +msgstr "" + +#: ./doc/training-guides/module001-ch006-overview-horizon-cli.xml:2550(para) +msgid "To explore the state and history of a particular stack, you can run a number of commands." +msgstr "" + +#: ./doc/training-guides/module001-ch006-overview-horizon-cli.xml:2554(para) +msgid "To show the details of a stack, run the following command:" +msgstr "" + +#: ./doc/training-guides/module001-ch006-overview-horizon-cli.xml:2558(para) +msgid "$ heat stack-show mystack" +msgstr "" + +#: ./doc/training-guides/module001-ch006-overview-horizon-cli.xml:2561(para) +msgid "A stack consists of a collection of resources. To list the resources, including their status, in a stack, run the following command:" +msgstr "" + +#: ./doc/training-guides/module001-ch006-overview-horizon-cli.xml:2566(para) +msgid "$ heat resource-list mystack" +msgstr "" + +#: ./doc/training-guides/module001-ch006-overview-horizon-cli.xml:2569(para) +msgid "To show the details for the specified resource in a stack, run the following command:" +msgstr "" + +#: ./doc/training-guides/module001-ch006-overview-horizon-cli.xml:2573(para) +msgid "$ heat resource-show mystack WikiDatabase" +msgstr "" + +#: ./doc/training-guides/module001-ch006-overview-horizon-cli.xml:2576(para) +msgid "Some resources have associated metadata which can change throughout the life-cycle of a resource:" +msgstr "" + +#: ./doc/training-guides/module001-ch006-overview-horizon-cli.xml:2580(para) +msgid "$ heat resource-metadata mystack WikiDatabase" +msgstr "" + +#: ./doc/training-guides/module001-ch006-overview-horizon-cli.xml:2583(para) +msgid "A series of events is generated during the life-cycle of a stack. This command will display those events." +msgstr "" + +#: ./doc/training-guides/module001-ch006-overview-horizon-cli.xml:2587(para) +msgid "$ heat event-list mystack" +msgstr "" + +#: ./doc/training-guides/module001-ch006-overview-horizon-cli.xml:2590(para) +msgid "To show the details for a particular event, run the following command:" +msgstr "" + +#: ./doc/training-guides/module001-ch006-overview-horizon-cli.xml:2594(para) +msgid "$ heat event-show WikiDatabase 1" +msgstr "" + +#: ./doc/training-guides/module001-ch006-overview-horizon-cli.xml:2597(para) +msgid "To update a stack" +msgstr "" + +#: ./doc/training-guides/module001-ch006-overview-horizon-cli.xml:2600(para) +msgid "To update an existing stack from a modified template file, run a command like the following command:" +msgstr "" + +#: ./doc/training-guides/module001-ch006-overview-horizon-cli.xml:2604(para) +msgid "$ heat stack-update mystack --template-file=/path/to/heat/templates/WordPress_Single_Instance_v2.template --parameters=\"InstanceType=m1.large;DBUsername=wp;DBPassword=verybadpassword;KeyName=heat_key;LinuxDistribution=F17\"" +msgstr "" + +#: ./doc/training-guides/module001-ch006-overview-horizon-cli.xml:2609(para) +msgid "Some resources are updated in-place, while others are replaced with new resources." +msgstr "" + +#: ./doc/training-guides/bk001-ch009-associate-object-storage-node.xml:8(title) ./doc/training-guides/bk002-ch013-operator-object-storage-node.xml:8(title) +msgid "Object Storage Node" +msgstr "" + +#: ./doc/training-guides/bk001-ch009-associate-object-storage-node.xml:10(title) +msgid "Day 2, 11:30 to 12:30, 13:30 to 14:45" +msgstr "" + +#: ./doc/training-guides/bk001-ch009-associate-object-storage-node.xml:14(title) ./doc/training-guides/module003-ch001-intro-objstore.xml:7(title) +msgid "Introduction to Object Storage" +msgstr "" + +#: ./doc/training-guides/bk001-ch009-associate-object-storage-node.xml:21(title) +msgid "Features and Benefits" +msgstr "" + +#: ./doc/training-guides/bk001-ch009-associate-object-storage-node.xml:30(title) +msgid "Object Storage CLI Commands" +msgstr "" + +#: ./doc/training-guides/bk001-ch009-associate-object-storage-node.xml:37(title) +msgid "Manage Object Storage" +msgstr "" + +#: ./doc/training-guides/bk001-ch009-associate-object-storage-node.xml:38(para) +msgid "Will be included from the swift developer reference" +msgstr "" + +#: ./doc/training-guides/card072-cinder-attach-volume.xml:7(title) +msgid "Attaching volumes to an instance" +msgstr "" + +#: ./doc/training-guides/card126-horizon.xml:7(title) +msgid "Install Horizon" +msgstr "" + +#. When image changes, this message will be marked fuzzy or untranslated for you. +#. It doesn't matter what you translate it to: it's not used at all. +#: ./doc/training-guides/module001-ch004-openstack-architecture.xml:26(None) +msgid "@@image: 'figures/image13.jpg'; md5=94fd9b9a3b33574d85bec7e1ea1675e2" +msgstr "" + +#. When image changes, this message will be marked fuzzy or untranslated for you. +#. It doesn't matter what you translate it to: it's not used at all. +#: ./doc/training-guides/module001-ch004-openstack-architecture.xml:70(None) +msgid "@@image: 'figures/image31.jpg'; md5=575b47442c4a8aac250a383f92a1bb46" +msgstr "" + +#. When image changes, this message will be marked fuzzy or untranslated for you. +#. It doesn't matter what you translate it to: it's not used at all. +#: ./doc/training-guides/module001-ch004-openstack-architecture.xml:100(None) +msgid "@@image: 'figures/image10.jpg'; md5=9471047adf0d93713be7f54b9db2b53c" +msgstr "" + +#: ./doc/training-guides/module001-ch004-openstack-architecture.xml:7(title) ./doc/training-guides/bk001-ch001-associate-getting-started.xml:45(title) +msgid "OpenStack Architecture" +msgstr "" + +#: ./doc/training-guides/module001-ch004-openstack-architecture.xml:8(guilabel) +msgid "Conceptual Architecture" +msgstr "" + +#: ./doc/training-guides/module001-ch004-openstack-architecture.xml:9(para) +msgid "The OpenStack project as a whole is designed to deliver a massively scalable cloud operating system. To achieve this, each of the constituent services are designed to work together to provide a complete Infrastructure as a Service (IaaS). This integration is facilitated through public application programming interfaces (APIs) that each service offers (and in turn can consume). While these APIs allow each of the services to use another service, it also allows an implementer to switch out any service as long as they maintain the API. These are (mostly) the same APIs that are available to end users of the cloud." +msgstr "" + +#: ./doc/training-guides/module001-ch004-openstack-architecture.xml:20(para) +msgid "Conceptually, you can picture the relationships between the services as so:" +msgstr "" + +#: ./doc/training-guides/module001-ch004-openstack-architecture.xml:23(title) +msgid "Conceptual Diagram" +msgstr "" + +#: ./doc/training-guides/module001-ch004-openstack-architecture.xml:32(para) +msgid "Dashboard (\"Horizon\") provides a web front end to the other OpenStack services" +msgstr "" + +#: ./doc/training-guides/module001-ch004-openstack-architecture.xml:36(para) +msgid "Compute (\"Nova\") stores and retrieves virtual disks (\"images\") and associated metadata in Image (\"Glance\")" +msgstr "" + +#: ./doc/training-guides/module001-ch004-openstack-architecture.xml:41(para) +msgid "Network (\"Quantum\") provides virtual networking for Compute." +msgstr "" + +#: ./doc/training-guides/module001-ch004-openstack-architecture.xml:45(para) +msgid "Block Storage (\"Cinder\") provides storage volumes for Compute." +msgstr "" + +#: ./doc/training-guides/module001-ch004-openstack-architecture.xml:49(para) +msgid "Image (\"Glance\") can store the actual virtual disk files in the Object Store(\"Swift\")" +msgstr "" + +#: ./doc/training-guides/module001-ch004-openstack-architecture.xml:53(para) +msgid "All the services authenticate with Identity (\"Keystone\")" +msgstr "" + +#: ./doc/training-guides/module001-ch004-openstack-architecture.xml:57(para) +msgid "This is a stylized and simplified view of the architecture, assuming that the implementer is using all of the services together in the most common configuration. It also only shows the \"operator\" side of the cloud -- it does not picture how consumers of the cloud may actually use it. For example, many users will access object storage heavily (and directly)." +msgstr "" + +#: ./doc/training-guides/module001-ch004-openstack-architecture.xml:63(guilabel) +msgid "Logical Architecture" +msgstr "" + +#: ./doc/training-guides/module001-ch004-openstack-architecture.xml:64(para) +msgid "This picture is consistent with the conceptual architecture above:" +msgstr "" + +#: ./doc/training-guides/module001-ch004-openstack-architecture.xml:67(title) +msgid "Logical Diagram" +msgstr "" + +#: ./doc/training-guides/module001-ch004-openstack-architecture.xml:76(para) +msgid "End users can interact through a common web interface (Horizon) or directly to each service through their API" +msgstr "" + +#: ./doc/training-guides/module001-ch004-openstack-architecture.xml:81(para) +msgid "All services authenticate through a common source (facilitated through keystone)" +msgstr "" + +#: ./doc/training-guides/module001-ch004-openstack-architecture.xml:85(para) +msgid "Individual services interact with each other through their public APIs (except where privileged administrator commands are necessary)" +msgstr "" + +#: ./doc/training-guides/module001-ch004-openstack-architecture.xml:90(para) +msgid "In the sections below, we'll delve into the architecture for each of the services." +msgstr "" + +#: ./doc/training-guides/module001-ch004-openstack-architecture.xml:92(guilabel) +msgid "Dashboard" +msgstr "" + +#: ./doc/training-guides/module001-ch004-openstack-architecture.xml:93(para) +msgid "Horizon is a modular Django web application that provides an end user and administrator interface to OpenStack services." +msgstr "" + +#: ./doc/training-guides/module001-ch004-openstack-architecture.xml:97(title) +msgid "Horizon Dashboard" +msgstr "" + +#: ./doc/training-guides/module001-ch004-openstack-architecture.xml:104(para) +msgid "As with most web applications, the architecture is fairly simple:" +msgstr "" + +#: ./doc/training-guides/module001-ch004-openstack-architecture.xml:108(para) +msgid "Horizon is usually deployed via mod_wsgi in Apache. The code itself is separated into a reusable python module with most of the logic (interactions with various OpenStack APIs) and presentation (to make it easily customizable for different sites)." +msgstr "" + +#: ./doc/training-guides/module001-ch004-openstack-architecture.xml:115(para) +msgid "A database (configurable as to which one) which relies mostly on the other services for data. It also stores very little data of its own." +msgstr "" + +#: ./doc/training-guides/module001-ch004-openstack-architecture.xml:120(para) +msgid "From a network architecture point of view, this service will need to be customer accessible as well as be able to talk to each service's public APIs. If you wish to use the administrator functionality (i.e. for other services), it will also need connectivity to their Admin API endpoints (which should be non-customer accessible)." +msgstr "" + +#: ./doc/training-guides/module001-ch004-openstack-architecture.xml:126(guilabel) +msgid "Compute" +msgstr "" + +#: ./doc/training-guides/module001-ch004-openstack-architecture.xml:127(para) +msgid "Nova is the most complicated and distributed component of OpenStack. A large number of processes cooperate to turn end user API requests into running virtual machines. Below is a list of these processes and their functions:" +msgstr "" + +#: ./doc/training-guides/module001-ch004-openstack-architecture.xml:133(para) +msgid "nova-api accepts and responds to end user compute API calls. It supports OpenStack Compute API, Amazon's EC2 API and a special Admin API (for privileged users to perform administrative actions). It also initiates most of the orchestration activities (such as running an instance) as well as enforces some policy (mostly quota checks)." +msgstr "" + +#: ./doc/training-guides/module001-ch004-openstack-architecture.xml:141(para) +msgid "The nova-compute process is primarily a worker daemon that creates and terminates virtual machine instances via hypervisor's APIs (XenAPI for XenServer/XCP, libvirt for KVM or QEMU, VMwareAPI for VMware, etc.). The process by which it does so is fairly complex but the basics are simple: accept actions from the queue and then perform a series of system commands (like launching a KVM instance) to carry them out while updating state in the database." +msgstr "" + +#: ./doc/training-guides/module001-ch004-openstack-architecture.xml:152(para) +msgid "nova-volume manages the creation, attaching and detaching of z volumes to compute instances (similar functionality to Amazon’s Elastic Block Storage). It can use volumes from a variety of providers such as iSCSI or Rados Block Device in Ceph. A new OpenStack project, Cinder, will eventually replace nova-volume functionality. In the Folsom release, nova-volume and the Block Storage service will have similar functionality." +msgstr "" + +#: ./doc/training-guides/module001-ch004-openstack-architecture.xml:162(para) +msgid "The nova-network worker daemon is very similar to nova-compute and nova-volume. It accepts networking tasks from the queue and then performs tasks to manipulate the network (such as setting up bridging interfaces or changing iptables rules). This functionality is being migrated to Quantum, a separate OpenStack service. In the Folsom release, much of the functionality will be duplicated between nova-network and Quantum." +msgstr "" + +#: ./doc/training-guides/module001-ch004-openstack-architecture.xml:172(para) +msgid "The nova-schedule process is conceptually the simplest piece of code in OpenStack Nova: it takes a virtual machine instance request from the queue and determines where it should run (specifically, which compute server host it should run on)." +msgstr "" + +#: ./doc/training-guides/module001-ch004-openstack-architecture.xml:179(para) +msgid "The queue provides a central hub for passing messages between daemons. This is usually implemented with RabbitMQ today, but could be any AMPQ message queue (such as Apache Qpid). New to the Folsom release is support for Zero MQ." +msgstr "" + +#: ./doc/training-guides/module001-ch004-openstack-architecture.xml:186(para) +msgid "The SQL database stores most of the build-time and runtime state for a cloud infrastructure. This includes the instance types that are available for use, instances in use, networks available and projects. Theoretically, OpenStack Nova can support any database supported by SQL-Alchemy but the only databases currently being widely used are sqlite3 (only appropriate for test and development work), MySQL and PostgreSQL." +msgstr "" + +#: ./doc/training-guides/module001-ch004-openstack-architecture.xml:196(para) +msgid "Nova also provides console services to allow end users to access their virtual instance's console through a proxy. This involves several daemons (nova-console, nova-novncproxy and nova-consoleauth)." +msgstr "" + +#: ./doc/training-guides/module001-ch004-openstack-architecture.xml:202(para) +msgid "Nova interacts with many other OpenStack services: Keystone for authentication, Glance for images and Horizon for web interface. The Glance interactions are central. The API process can upload and query Glance while nova-compute will download images for use in launching images." +msgstr "" + +#: ./doc/training-guides/module001-ch004-openstack-architecture.xml:207(guilabel) +msgid "Object Store" +msgstr "" + +#: ./doc/training-guides/module001-ch004-openstack-architecture.xml:208(para) +msgid "The swift architecture is very distributed to prevent any single point of failure as well as to scale horizontally. It includes the following components:" +msgstr "" + +#: ./doc/training-guides/module001-ch004-openstack-architecture.xml:213(para) +msgid "Proxy server (swift-proxy-server) accepts incoming requests via the OpenStack Object API or just raw HTTP. It accepts files to upload, modifications to metadata or container creation. In addition, it will also serve files or container listing to web browsers. The proxy server may utilize an optional cache (usually deployed with memcache) to improve performance." +msgstr "" + +#: ./doc/training-guides/module001-ch004-openstack-architecture.xml:222(para) +msgid "Account servers manage accounts defined with the object storage service." +msgstr "" + +#: ./doc/training-guides/module001-ch004-openstack-architecture.xml:226(para) +msgid "Container servers manage a mapping of containers (i.e folders) within the object store service." +msgstr "" + +#: ./doc/training-guides/module001-ch004-openstack-architecture.xml:230(para) +msgid "Object servers manage actual objects (i.e. files) on the storage nodes." +msgstr "" + +#: ./doc/training-guides/module001-ch004-openstack-architecture.xml:234(para) +msgid "There are also a number of periodic processes which run to perform housekeeping tasks on the large data store. The most important of these is the replication services, which ensures consistency and availability through the cluster. Other periodic processes include auditors, updaters and reapers." +msgstr "" + +#: ./doc/training-guides/module001-ch004-openstack-architecture.xml:242(para) +msgid "Authentication is handled through configurable WSGI middleware (which will usually be Keystone)." +msgstr "" + +#: ./doc/training-guides/module001-ch004-openstack-architecture.xml:244(guilabel) +msgid "Image Store" +msgstr "" + +#: ./doc/training-guides/module001-ch004-openstack-architecture.xml:245(para) +msgid "The Glance architecture has stayed relatively stable since the Cactus release. The biggest architectural change has been the addition of authentication, which was added in the Diablo release. Just as a quick reminder, Glance has four main parts to it:" +msgstr "" + +#: ./doc/training-guides/module001-ch004-openstack-architecture.xml:252(para) +msgid "glance-api accepts Image API calls for image discovery, image retrieval and image storage." +msgstr "" + +#: ./doc/training-guides/module001-ch004-openstack-architecture.xml:256(para) +msgid "glance-registry stores, processes and retrieves metadata about images (size, type, etc.)." +msgstr "" + +#: ./doc/training-guides/module001-ch004-openstack-architecture.xml:260(para) +msgid "A database to store the image metadata. Like Nova, you can choose your database depending on your preference (but most people use MySQL or SQlite)." +msgstr "" + +#: ./doc/training-guides/module001-ch004-openstack-architecture.xml:265(para) +msgid "A storage repository for the actual image files. In the diagram above, Swift is shown as the image repository, but this is configurable. In addition to Swift, Glance supports normal filesystems, RADOS block devices, Amazon S3 and HTTP. Be aware that some of these choices are limited to read-only usage." +msgstr "" + +#: ./doc/training-guides/module001-ch004-openstack-architecture.xml:273(para) +msgid "There are also a number of periodic processes which run on Glance to support caching. The most important of these is the replication services, which ensures consistency and availability through the cluster. Other periodic processes include auditors, updaters and reapers." +msgstr "" + +#: ./doc/training-guides/module001-ch004-openstack-architecture.xml:278(para) +msgid "As you can see from the diagram in the Conceptual Architecture section, Glance serves a central role to the overall IaaS picture. It accepts API requests for images (or image metadata) from end users or Nova components and can store its disk files in the object storage service, Swift." +msgstr "" + +#: ./doc/training-guides/module001-ch004-openstack-architecture.xml:284(guilabel) +msgid "Identity" +msgstr "" + +#: ./doc/training-guides/module001-ch004-openstack-architecture.xml:285(para) +msgid "Keystone provides a single point of integration for OpenStack policy, catalog, token and authentication." +msgstr "" + +#: ./doc/training-guides/module001-ch004-openstack-architecture.xml:289(para) +msgid "keystone handles API requests as well as providing configurable catalog, policy, token and identity services." +msgstr "" + +#: ./doc/training-guides/module001-ch004-openstack-architecture.xml:294(para) +msgid "Each Keystone function has a pluggable backend which allows different ways to use the particular service. Most support standard backends like LDAP or SQL, as well as Key Value Stores (KVS)." +msgstr "" + +#: ./doc/training-guides/module001-ch004-openstack-architecture.xml:300(para) +msgid "Most people will use this as a point of customization for their current authentication services." +msgstr "" + +#: ./doc/training-guides/module001-ch004-openstack-architecture.xml:302(guilabel) +msgid "Network" +msgstr "" + +#: ./doc/training-guides/module001-ch004-openstack-architecture.xml:303(para) +msgid "Quantum provides \"network connectivity as a service\" between interface devices managed by other OpenStack services (most likely Nova). The service works by allowing users to create their own networks and then attach interfaces to them. Like many of the OpenStack services, Quantum is highly configurable due to it's plug-in architecture. These plug-ins accommodate different networking equipment and software. As such, the architecture and deployment can vary dramatically. In the above architecture, a simple Linux networking plug-in is shown." +msgstr "" + +#: ./doc/training-guides/module001-ch004-openstack-architecture.xml:315(para) +msgid "quantum-server accepts API requests and then routes them to the appropriate quantum plugin for action." +msgstr "" + +#: ./doc/training-guides/module001-ch004-openstack-architecture.xml:319(para) +msgid "Quantum plugins and agents perform the actual actions such as plugging and unplugging ports, creating networks or subnets and IP addressing. These plugins and agents differ depending on the vendor and technologies used in the particular cloud. Quantum ships with plugins and agents for: Cisco virtual and physical switches, Nicira NVP product, NEC OpenFlow products, Openvswitch, Linux bridging and the Ryu Network Operating System." +msgstr "" + +#: ./doc/training-guides/module001-ch004-openstack-architecture.xml:329(para) +msgid "The common agents are L3 (layer 3), DHCP (dynamic host IP addressing) and the specific plug-in agent." +msgstr "" + +#: ./doc/training-guides/module001-ch004-openstack-architecture.xml:333(para) +msgid "Most Quantum installations will also make use of a messaging queue to route information between the quantum-server and various agents as well as a database to store networking state for particular plugins." +msgstr "" + +#: ./doc/training-guides/module001-ch004-openstack-architecture.xml:339(para) +msgid "Quantum will interact mainly with Nova, where it will provide networks and connectivity for its instances." +msgstr "" + +#: ./doc/training-guides/module001-ch004-openstack-architecture.xml:341(guilabel) +msgid "Block Storage" +msgstr "" + +#: ./doc/training-guides/module001-ch004-openstack-architecture.xml:342(para) +msgid "Cinder separates out the persistent block storage functionality that was previously part of OpenStack Compute (in the form of nova-volume) into it's own service. The OpenStack Block Storage API allows for manipulation of volumes, volume types (similar to compute flavors) and volume snapshots." +msgstr "" + +#: ./doc/training-guides/module001-ch004-openstack-architecture.xml:350(para) +msgid "cinder-api accepts API requests and routes them to cinder-volume for action." +msgstr "" + +#: ./doc/training-guides/module001-ch004-openstack-architecture.xml:354(para) +msgid "cinder-volume acts upon the requests by reading or writing to the Cinder database to maintain state, interacting with other processes (like cinder-scheduler) through a message queue and directly upon block storage providing hardware or software. It can interact with a variety of storage providers through a driver architecture. Currently, there are drivers for IBM, SolidFire, NetApp, Nexenta, Zadara, linux iSCSI and other storage providers." +msgstr "" + +#: ./doc/training-guides/module001-ch004-openstack-architecture.xml:365(para) +msgid "Much like nova-scheduler, the cinder-scheduler daemon picks the optimal block storage provider node to create the volume on." +msgstr "" + +#: ./doc/training-guides/module001-ch004-openstack-architecture.xml:370(para) +msgid "Cinder deployments will also make use of a messaging queue to route information between the cinder processes as well as a database to store volume state." +msgstr "" + +#: ./doc/training-guides/module001-ch004-openstack-architecture.xml:375(para) +msgid "Like Quantum, Cinder will mainly interact with Nova, providing volumes for its instances." +msgstr "" + +#. When image changes, this message will be marked fuzzy or untranslated for you. +#. It doesn't matter what you translate it to: it's not used at all. +#: ./doc/training-guides/module001-ch009-vm-placement.xml:18(None) +msgid "@@image: 'figures/image29.png'; md5=ce788bfd80e615104fa1e3257065824a" +msgstr "" + +#. When image changes, this message will be marked fuzzy or untranslated for you. +#. It doesn't matter what you translate it to: it's not used at all. +#: ./doc/training-guides/module001-ch009-vm-placement.xml:58(None) +msgid "@@image: 'figures/image27.png'; md5=c144af5cbdee1bd17a7bde0bea5b5fe7" +msgstr "" + +#. When image changes, this message will be marked fuzzy or untranslated for you. +#. It doesn't matter what you translate it to: it's not used at all. +#: ./doc/training-guides/module001-ch009-vm-placement.xml:198(None) +msgid "@@image: 'figures/image07.png'; md5=000eab4cf0deb1da2e692e023065a6ae" +msgstr "" + +#: ./doc/training-guides/module001-ch009-vm-placement.xml:7(title) ./doc/training-guides/bk001-ch005-associate-compute-node.xml:14(title) +msgid "VM Placement" +msgstr "" + +#: ./doc/training-guides/module001-ch009-vm-placement.xml:8(para) +msgid "Compute uses the nova-scheduler service to determine how to dispatch compute and volume requests. For example, the nova-scheduler service determines which host a VM should launch on. The term host in the context of filters means a physical node that has a nova-compute service running on it. You can configure the scheduler through a variety of options." +msgstr "" + +#: ./doc/training-guides/module001-ch009-vm-placement.xml:15(title) ./doc/training-guides/lab003-compute-node.xml:195(emphasis) ./doc/training-guides/lab001-control-node.xml:434(emphasis) +msgid "Nova" +msgstr "" + +#: ./doc/training-guides/module001-ch009-vm-placement.xml:22(para) +msgid "Just as shown by above figure, nova-scheduler interacts with other components through queue and central database repo. For scheduling, queue is the essential communications hub." +msgstr "" + +#: ./doc/training-guides/module001-ch009-vm-placement.xml:25(para) +msgid "All compute nodes (also known as hosts in terms of OpenStack) periodically publish their status, resources available and hardware capabilities to nova-scheduler through the queue. nova-scheduler then collects this data and uses it to make decisions when a request comes in." +msgstr "" + +#: ./doc/training-guides/module001-ch009-vm-placement.xml:30(para) +msgid "By default, the compute scheduler is configured as a filter scheduler, as described in the next section. In the default configuration, this scheduler considers hosts that meet all the following criteria:" +msgstr "" + +#: ./doc/training-guides/module001-ch009-vm-placement.xml:36(para) +msgid "Are in the requested availability zone (AvailabilityZoneFilter)." +msgstr "" + +#: ./doc/training-guides/module001-ch009-vm-placement.xml:40(para) +msgid "Have sufficient RAM available (RamFilter)." +msgstr "" + +#: ./doc/training-guides/module001-ch009-vm-placement.xml:43(para) +msgid "Are capable of servicing the request (ComputeFilter)." +msgstr "" + +#: ./doc/training-guides/module001-ch009-vm-placement.xml:48(guilabel) +msgid "Filter Scheduler" +msgstr "" + +#: ./doc/training-guides/module001-ch009-vm-placement.xml:49(para) +msgid "The Filter Scheduler supports filtering and weighting to make informed decisions on where a new instance should be created. This Scheduler supports only working with Compute Nodes." +msgstr "" + +#: ./doc/training-guides/module001-ch009-vm-placement.xml:53(guilabel) ./doc/training-guides/module001-ch009-vm-placement.xml:55(title) +msgid "Filtering" +msgstr "" + +#: ./doc/training-guides/module001-ch009-vm-placement.xml:62(para) +msgid "During its work, Filter Scheduler first makes a dictionary of unfiltered hosts, then filters them using filter properties and finally chooses hosts for the requested number of instances (each time it chooses the most weighed host and appends it to the list of selected hosts)." +msgstr "" + +#: ./doc/training-guides/module001-ch009-vm-placement.xml:67(para) +msgid "If it turns up, that it can’t find candidates for the next instance, it means that there are no more appropriate hosts where the instance could be scheduled." +msgstr "" + +#: ./doc/training-guides/module001-ch009-vm-placement.xml:70(para) +msgid "If we speak about filtering and weighting, their work is quite flexible in the Filter Scheduler. There are a lot of filtering strategies for the Scheduler to support. Also you can even implement your own algorithm of filtering." +msgstr "" + +#: ./doc/training-guides/module001-ch009-vm-placement.xml:74(para) +msgid "There are some standard filter classes to use (nova.scheduler.filters):" +msgstr "" + +#: ./doc/training-guides/module001-ch009-vm-placement.xml:78(para) +msgid "AllHostsFilter - frankly speaking, this filter does no operation. It passes all the available hosts." +msgstr "" + +#: ./doc/training-guides/module001-ch009-vm-placement.xml:82(para) +msgid "ImagePropertiesFilter - filters hosts based on properties defined on the instance’s image. It passes hosts that can support the specified image properties contained in the instance." +msgstr "" + +#: ./doc/training-guides/module001-ch009-vm-placement.xml:88(para) +msgid "AvailabilityZoneFilter - filters hosts by availability zone. It passes hosts matching the availability zone specified in the instance properties." +msgstr "" + +#: ./doc/training-guides/module001-ch009-vm-placement.xml:93(para) +msgid "ComputeCapabilitiesFilter - checks that the capabilities provided by the host compute service satisfy any extra specifications associated with the instance type. It passes hosts that can create the specified instance type." +msgstr "" + +#: ./doc/training-guides/module001-ch009-vm-placement.xml:100(para) +msgid "The extra specifications can have a scope at the beginning of the key string of a key/value pair. The scope format is scope:key and can be nested, i.e. key_string := scope:key_string. Example like capabilities:cpu_info: features is valid scope format. A key string without any : is non-scope format. Each filter defines its valid scope, and not all filters accept non-scope format." +msgstr "" + +#: ./doc/training-guides/module001-ch009-vm-placement.xml:109(para) +msgid "The extra specifications can have an operator at the beginning of the value string of a key/value pair. If there is no operator specified, then a default operator of s== is used. Valid operators are:" +msgstr "" + +#: ./doc/training-guides/module001-ch009-vm-placement.xml:115(para) +msgid "* = (equal to or greater than as a number; same as vcpus case)* == (equal to as a number)* != (not equal to as a number)* >= (greater than or equal to as a number)* <= (less than or equal to as a number)* s== (equal to as a string)* s!= (not equal to as a string)* s>= (greater than or equal to as a string)* s> (greater than as a string)* s<= (less than or equal to as a string)* s< (less than as a string)* <in> (substring)* <or> (find one of these)Examples are: \">= 5\", \"s== 2.1.0\", \"<in> gcc\", and \"<or> fpu <or> gpu\"" +msgstr "" + +#: ./doc/training-guides/module001-ch009-vm-placement.xml:137(para) +msgid "Here ram_allocation_ratio means the virtual RAM to physical RAM allocation ratio (it is 1.5 by default). Really, nice and simple." +msgstr "" + +#: ./doc/training-guides/module001-ch009-vm-placement.xml:140(para) +msgid "Next standard filter to describe is AvailabilityZoneFilter and it isn’t difficult too. This filter just looks at the availability zone of compute node and availability zone from the properties of the request. Each compute service has its own availability zone. So deployment engineers have an option to run scheduler with availability zones support and can configure availability zones on each compute host. This classes method host_passes returns True if availability zone mentioned in request is the same on the current compute host." +msgstr "" + +#: ./doc/training-guides/module001-ch009-vm-placement.xml:150(para) +msgid "The ImagePropertiesFilter filters hosts based on the architecture, hypervisor type, and virtual machine mode specified in the instance. E.g., an instance might require a host that supports the arm architecture on a qemu compute host. The ImagePropertiesFilter will only pass hosts that can satisfy this request. These instance properties are populated from properties define on the instance’s image. E.g. an image can be decorated with these properties using glance image-update img-uuid --property architecture=arm --property hypervisor_type=qemu Only hosts that satisfy these requirements will pass the ImagePropertiesFilter." +msgstr "" + +#: ./doc/training-guides/module001-ch009-vm-placement.xml:161(para) +msgid "ComputeCapabilitiesFilter checks if the host satisfies any extra_specs specified on the instance type. The extra_specs can contain key/value pairs. The key for the filter is either non-scope format (i.e. no : contained), or scope format in capabilities scope (i.e. capabilities:xxx:yyy). One example of capabilities scope is capabilities:cpu_info:features, which will match host’s cpu features capabilities. The ComputeCapabilitiesFilter will only pass hosts whose capabilities satisfy the requested specifications. All hosts are passed if no extra_specs are specified." +msgstr "" + +#: ./doc/training-guides/module001-ch009-vm-placement.xml:171(para) +msgid "ComputeFilter is quite simple and passes any host whose compute service is enabled and operational." +msgstr "" + +#: ./doc/training-guides/module001-ch009-vm-placement.xml:173(para) +msgid "Now we are going to IsolatedHostsFilter. There can be some special hosts reserved for specific images. These hosts are called isolated. So the images to run on the isolated hosts are also called isolated. This Scheduler checks if image_isolated flag named in instance specifications is the same that the host has." +msgstr "" + +#: ./doc/training-guides/module001-ch009-vm-placement.xml:180(guilabel) ./doc/training-guides/module001-ch009-vm-placement.xml:195(title) +msgid "Weights" +msgstr "" + +#: ./doc/training-guides/module001-ch009-vm-placement.xml:181(para) +msgid "Filter Scheduler uses so-called weights during its work." +msgstr "" + +#: ./doc/training-guides/module001-ch009-vm-placement.xml:183(para) +msgid "The Filter Scheduler weights hosts based on the config option scheduler_weight_classes, this defaults to nova.scheduler.weights.all_weighers, which selects the only weigher available – the RamWeigher. Hosts are then weighted and sorted with the largest weight winning." +msgstr "" + +#: ./doc/training-guides/module001-ch009-vm-placement.xml:188(para) +msgid "Filter Scheduler finds local list of acceptable hosts by repeated filtering and weighing. Each time it chooses a host, it virtually consumes resources on it, so subsequent selections can adjust accordingly. It is useful if the customer asks for the same large amount of instances, because weight is computed for each instance requested." +msgstr "" + +#: ./doc/training-guides/module001-ch009-vm-placement.xml:202(para) +msgid "In the end Filter Scheduler sorts selected hosts by their weight and provisions instances on them." +msgstr "" + +#: ./doc/training-guides/card039-nova.xml:7(title) ./doc/training-guides/lab003-compute-node.xml:198(para) +msgid "Install Nova" +msgstr "" + +#: ./doc/training-guides/bk002-ch003-operator-getting-started-quiz.xml:6(title) ./doc/training-guides/bk001-ch002-associate-getting-started-quiz.xml:6(title) +msgid "Getting Started Quiz" +msgstr "" + +#: ./doc/training-guides/bk002-ch003-operator-getting-started-quiz.xml:8(title) ./doc/training-guides/bk001-ch006-associate-compute-node-quiz.xml:8(title) +msgid "Day 1, 16:40 to 17:00" +msgstr "" + +#: ./doc/training-guides/bk004-architect-training-guide.xml:5(title) +msgid "Architect Training Guide" +msgstr "" + +#: ./doc/training-guides/bk004-architect-training-guide.xml:7(title) +msgid "Architect Training Guide Coming Soon" +msgstr "" + +#: ./doc/training-guides/bk004-architect-training-guide.xml:8(para) +msgid "TBD" +msgstr "" + +#: ./doc/training-guides/card047-install-nova-compute.xml:7(title) +msgid "Installing Nova" +msgstr "" + +#: ./doc/training-guides/bk002-ch004-operator-controller-node.xml:10(title) +msgid "Day 2 to 4, 09:00 to 11:00, 11:15 to 12:30" +msgstr "" + +#: ./doc/training-guides/bk002-ch004-operator-controller-node.xml:14(title) +msgid "Review Associate Overview Horizon and OpenStack CLI" +msgstr "" + +#: ./doc/training-guides/bk002-ch004-operator-controller-node.xml:21(title) +msgid "Review Associate Keystone Architecture" +msgstr "" + +#: ./doc/training-guides/bk002-ch004-operator-controller-node.xml:28(title) +msgid "Review Associate OpenStack Messaging and Queues" +msgstr "" + +#: ./doc/training-guides/lab003-compute-node.xml:70(para) +msgid "Enable IP Forwarding by adding the following to /etc/sysctl.conf" +msgstr "" + +#: ./doc/training-guides/lab003-compute-node.xml:87(emphasis) ./doc/training-guides/bk001-ch002-associate-getting-started-quiz.xml:190(para) +msgid "KVM" +msgstr "" + +#: ./doc/training-guides/lab003-compute-node.xml:90(para) +msgid "Install KVM:" +msgstr "" + +#: ./doc/training-guides/lab003-compute-node.xml:96(para) +msgid "Edit /etc/libvirt/qemu.conf" +msgstr "" + +#: ./doc/training-guides/lab003-compute-node.xml:105(para) +msgid "Delete Default Virtual Bridge" +msgstr "" + +#: ./doc/training-guides/lab003-compute-node.xml:112(para) +msgid "To Enable Live Migration Edit /etc/libvirt/libvirtd.conf" +msgstr "" + +#: ./doc/training-guides/lab003-compute-node.xml:118(para) +msgid "Edit /etc/init/libvirt-bin.conf" +msgstr "" + +#: ./doc/training-guides/lab003-compute-node.xml:122(para) +msgid "Edit /etc/default/libvirt-bin" +msgstr "" + +#: ./doc/training-guides/lab003-compute-node.xml:126(para) +msgid "Restart libvirt" +msgstr "" + +#: ./doc/training-guides/lab003-compute-node.xml:133(emphasis) +msgid "Neutron and OVS" +msgstr "" + +#: ./doc/training-guides/lab003-compute-node.xml:136(para) ./doc/training-guides/card041-neutron.xml:9(emphasis) +msgid "Install OpenVSwitch" +msgstr "" + +#: ./doc/training-guides/lab003-compute-node.xml:140(para) +msgid "Create bridges:" +msgstr "" + +#: ./doc/training-guides/lab003-compute-node.xml:147(para) +msgid "Install the Neutron openvswitch agent:" +msgstr "" + +#: ./doc/training-guides/lab003-compute-node.xml:153(para) +msgid "Edit /etc/neutron/plugins/openvswitch/ovs_neutron_plugin.ini" +msgstr "" + +#: ./doc/training-guides/lab003-compute-node.xml:174(para) +msgid "Edit /etc/neutron/neutron.conf" +msgstr "" + +#: ./doc/training-guides/lab003-compute-node.xml:189(para) +msgid "Restart all the services:" +msgstr "" + +#: ./doc/training-guides/lab003-compute-node.xml:205(para) ./doc/training-guides/lab001-control-node.xml:467(para) +msgid "Edit /etc/nova/api-paste.ini" +msgstr "" + +#: ./doc/training-guides/lab003-compute-node.xml:219(para) +msgid "Edit /etc/nova/nova-compute.conf" +msgstr "" + +#: ./doc/training-guides/lab003-compute-node.xml:228(para) ./doc/training-guides/lab001-control-node.xml:484(para) +msgid "Edit /etc/nova/nova.conf" +msgstr "" + +#: ./doc/training-guides/lab003-compute-node.xml:278(para) +msgid "Restart Nova Services" +msgstr "" + +#: ./doc/training-guides/lab003-compute-node.xml:282(para) +msgid "List Nova Services (Check for the Smiley Faces to know if the services are running):" +msgstr "" + +#: ./doc/training-guides/bk002-ch002-operator-getting-started-lab.xml:6(title) +msgid "Getting Started Lab" +msgstr "" + +#: ./doc/training-guides/bk002-ch002-operator-getting-started-lab.xml:8(title) +msgid "Day 1, 13:30 to 14:45, 15:00 to 17:00" +msgstr "" + +#: ./doc/training-guides/bk002-ch002-operator-getting-started-lab.xml:12(title) +msgid "Getting the Tools and Accounts for Committing Code" +msgstr "" + +#: ./doc/training-guides/bk002-ch002-operator-getting-started-lab.xml:26(title) +msgid "Submit a Documentation Bug" +msgstr "" + +#: ./doc/training-guides/bk002-ch002-operator-getting-started-lab.xml:40(title) +msgid "Optional: Add to the Training Guide Documentation" +msgstr "" + +#. When image changes, this message will be marked fuzzy or untranslated for you. +#. It doesn't matter what you translate it to: it's not used at all. +#: ./doc/training-guides/module003-ch003-obj-store-capabilities.xml:89(None) +msgid "@@image: 'figures/image39.png'; md5=e26e374ace84070f5fed24e73adcd562" +msgstr "" + +#: ./doc/training-guides/module003-ch003-obj-store-capabilities.xml:7(title) ./doc/training-guides/bk002-ch013-operator-object-storage-node.xml:32(title) +msgid "Object Storage Capabilities" +msgstr "" + +#: ./doc/training-guides/module003-ch003-obj-store-capabilities.xml:40(guilabel) +msgid "Swift Characteristics" +msgstr "" + +#: ./doc/training-guides/module003-ch003-obj-store-capabilities.xml:41(para) +msgid "The key characteristics of Swift include:" +msgstr "" + +#: ./doc/training-guides/module003-ch003-obj-store-capabilities.xml:44(para) +msgid "All objects stored in Swift have a URL" +msgstr "" + +#: ./doc/training-guides/module003-ch003-obj-store-capabilities.xml:47(para) +msgid "All objects stored are replicated 3x in as-unique-as-possible zones, which can be defined as a group of drives, a node, a rack etc." +msgstr "" + +#: ./doc/training-guides/module003-ch003-obj-store-capabilities.xml:52(para) +msgid "All objects have their own metadata" +msgstr "" + +#: ./doc/training-guides/module003-ch003-obj-store-capabilities.xml:55(para) +msgid "Developers interact with the object storage system through a RESTful HTTP API" +msgstr "" + +#: ./doc/training-guides/module003-ch003-obj-store-capabilities.xml:59(para) +msgid "Object data can be located anywhere in the cluster" +msgstr "" + +#: ./doc/training-guides/module003-ch003-obj-store-capabilities.xml:63(para) +msgid "The cluster scales by adding additional nodes -- without sacrificing performance, which allows a more cost-effective linear storage expansion vs. fork-lift upgrades" +msgstr "" + +#: ./doc/training-guides/module003-ch003-obj-store-capabilities.xml:69(para) +msgid "Data doesn’t have to be migrated to an entirely new storage system" +msgstr "" + +#: ./doc/training-guides/module003-ch003-obj-store-capabilities.xml:73(para) +msgid "New nodes can be added to the cluster without downtime" +msgstr "" + +#: ./doc/training-guides/module003-ch003-obj-store-capabilities.xml:77(para) +msgid "Failed nodes and disks can be swapped out with no downtime" +msgstr "" + +#: ./doc/training-guides/module003-ch003-obj-store-capabilities.xml:81(para) +msgid "Runs on industry-standard hardware, such as Dell, HP, Supermicro etc." +msgstr "" + +#: ./doc/training-guides/module003-ch003-obj-store-capabilities.xml:93(para) +msgid "Developers can either write directly to the Swift API or use one of the many client libraries that exist for all popular programming languages, such as Java, Python, Ruby and C#. Amazon S3 and RackSpace Cloud Files users should feel very familiar with Swift. For users who have not used an object storage system before, it will require a different approach and mindset than using a traditional filesystem." +msgstr "" + +#: ./doc/training-guides/card045-configure-virtual-networking.xml:7(title) +msgid "Configure Virtual Networking" +msgstr "" + +#: ./doc/training-guides/module003-ch001-intro-objstore.xml:8(para) +msgid "OpenStack Object Storage (code-named Swift) is open source software for creating redundant, scalable data storage using clusters of standardized servers to store petabytes of accessible data. It is a long-term storage system for large amounts of static data that can be retrieved, leveraged, and updated. Object Storage uses a distributed architecture with no central point of control, providing greater scalability, redundancy and permanence. Objects are written to multiple hardware devices, with the OpenStack software responsible for ensuring data replication and integrity across the cluster. Storage clusters scale horizontally by adding new nodes. Should a node fail, OpenStack works to replicate its content from other active nodes. Because OpenStack uses software logic to ensure data replication and distribution across different devices, inexpensive commodity hard drives and servers can be used in lieu of more expensive equipment." +msgstr "" + +#: ./doc/training-guides/bk001-ch004-associate-controller-node-quiz.xml:6(title) ./doc/training-guides/bk002-ch006-operator-controller-node-quiz.xml:6(title) +msgid "Controller Node Quiz" +msgstr "" + +#: ./doc/training-guides/bk001-ch004-associate-controller-node-quiz.xml:8(title) +msgid "Day 1, 14:25 to 14:45" +msgstr "" + +#: ./doc/training-guides/bk001-ch004-associate-controller-node-quiz.xml:10(title) +msgid "Associate Training Guide, Controller Node Quiz Questions" +msgstr "" + +#: ./doc/training-guides/bk001-ch004-associate-controller-node-quiz.xml:15(title) +msgid "When managing images for OpenStack you can complete all those tasks with the OpenStack dashboard. (True or False)" +msgstr "" + +#: ./doc/training-guides/bk001-ch004-associate-controller-node-quiz.xml:20(para) ./doc/training-guides/bk001-ch004-associate-controller-node-quiz.xml:36(para) ./doc/training-guides/bk001-ch004-associate-controller-node-quiz.xml:100(para) ./doc/training-guides/bk001-ch004-associate-controller-node-quiz.xml:116(para) ./doc/training-guides/bk001-ch004-associate-controller-node-quiz.xml:157(para) ./doc/training-guides/bk001-ch004-associate-controller-node-quiz.xml:172(para) ./doc/training-guides/bk001-ch004-associate-controller-node-quiz.xml:236(para) ./doc/training-guides/bk001-ch004-associate-controller-node-quiz.xml:299(para) ./doc/training-guides/bk001-ch002-associate-getting-started-quiz.xml:91(para) ./doc/training-guides/bk001-ch002-associate-getting-started-quiz.xml:106(para) ./doc/training-guides/bk001-ch002-associate-getting-started-quiz.xml:121(para) ./doc/training-guides/bk001-ch002-associate-getting-started-quiz.xml:160(para) ./doc/training-guides/bk001-ch002-associate-getting-started-quiz.xml:175(para) +msgid "True" +msgstr "" + +#: ./doc/training-guides/bk001-ch004-associate-controller-node-quiz.xml:23(para) ./doc/training-guides/bk001-ch004-associate-controller-node-quiz.xml:39(para) ./doc/training-guides/bk001-ch004-associate-controller-node-quiz.xml:103(para) ./doc/training-guides/bk001-ch004-associate-controller-node-quiz.xml:119(para) ./doc/training-guides/bk001-ch004-associate-controller-node-quiz.xml:160(para) ./doc/training-guides/bk001-ch004-associate-controller-node-quiz.xml:175(para) ./doc/training-guides/bk001-ch004-associate-controller-node-quiz.xml:239(para) ./doc/training-guides/bk001-ch004-associate-controller-node-quiz.xml:302(para) ./doc/training-guides/bk001-ch002-associate-getting-started-quiz.xml:94(para) ./doc/training-guides/bk001-ch002-associate-getting-started-quiz.xml:109(para) ./doc/training-guides/bk001-ch002-associate-getting-started-quiz.xml:124(para) ./doc/training-guides/bk001-ch002-associate-getting-started-quiz.xml:163(para) ./doc/training-guides/bk001-ch002-associate-getting-started-quiz.xml:178(para) +msgid "False" +msgstr "" + +#: ./doc/training-guides/bk001-ch004-associate-controller-node-quiz.xml:31(title) +msgid "When setting up access and security, SSH credentials (keypairs) must be injected into images after they are launched with a script. (True or False)" +msgstr "" + +#: ./doc/training-guides/bk001-ch004-associate-controller-node-quiz.xml:47(title) +msgid "You can track monthly costs with metrics like: (choose all that apply)" +msgstr "" + +#: ./doc/training-guides/bk001-ch004-associate-controller-node-quiz.xml:51(para) +msgid "VCPU" +msgstr "" + +#: ./doc/training-guides/bk001-ch004-associate-controller-node-quiz.xml:54(para) +msgid "QoS" +msgstr "" + +#: ./doc/training-guides/bk001-ch004-associate-controller-node-quiz.xml:57(para) +msgid "Uptime" +msgstr "" + +#: ./doc/training-guides/bk001-ch004-associate-controller-node-quiz.xml:60(para) +msgid "Disks" +msgstr "" + +#: ./doc/training-guides/bk001-ch004-associate-controller-node-quiz.xml:63(para) +msgid "RAM" +msgstr "" + +#: ./doc/training-guides/bk001-ch004-associate-controller-node-quiz.xml:71(title) +msgid "The following OpenStack command-line clients are available. (choose all that apply)" +msgstr "" + +#: ./doc/training-guides/bk001-ch004-associate-controller-node-quiz.xml:75(para) +msgid "python-keystoneclient" +msgstr "" + +#: ./doc/training-guides/bk001-ch004-associate-controller-node-quiz.xml:78(para) +msgid "python-hypervisorclient" +msgstr "" + +#: ./doc/training-guides/bk001-ch004-associate-controller-node-quiz.xml:81(para) +msgid "python-imageclient" +msgstr "" + +#: ./doc/training-guides/bk001-ch004-associate-controller-node-quiz.xml:84(para) +msgid "python-cinderclient" +msgstr "" + +#: ./doc/training-guides/bk001-ch004-associate-controller-node-quiz.xml:87(para) +msgid "python-novaclient" +msgstr "" + +#: ./doc/training-guides/bk001-ch004-associate-controller-node-quiz.xml:95(title) +msgid "To install a client package the following command syntax is used: $ sudo pip install [--update] python-project client (True or False)" +msgstr "" + +#: ./doc/training-guides/bk001-ch004-associate-controller-node-quiz.xml:111(title) +msgid "To get a list of images in glance you can use the following command syntax: $ glance image-list" +msgstr "" + +#: ./doc/training-guides/bk001-ch004-associate-controller-node-quiz.xml:127(title) +msgid "When troubleshooting image creation you will need to look at which of the following log files for errors? (choose all that apply)" +msgstr "" + +#: ./doc/training-guides/bk001-ch004-associate-controller-node-quiz.xml:132(para) +msgid "Examine the /var/log/nova-api.log" +msgstr "" + +#: ./doc/training-guides/bk001-ch004-associate-controller-node-quiz.xml:135(para) +msgid "Examine the /var/log/nova-compute.log" +msgstr "" + +#: ./doc/training-guides/bk001-ch004-associate-controller-node-quiz.xml:138(para) +msgid "Examine the /var/log/nova-error.log" +msgstr "" + +#: ./doc/training-guides/bk001-ch004-associate-controller-node-quiz.xml:141(para) +msgid "Examine the /var/log/nova-status.log" +msgstr "" + +#: ./doc/training-guides/bk001-ch004-associate-controller-node-quiz.xml:144(para) +msgid "Examine the /var/log/nova-image.log" +msgstr "" + +#: ./doc/training-guides/bk001-ch004-associate-controller-node-quiz.xml:152(title) +msgid "To generate a keypair use the following command syntax: $ nova keypair-add --pub_key ~/.ssh/id_rsa.pub KEY_NAME" +msgstr "" + +#: ./doc/training-guides/bk001-ch004-associate-controller-node-quiz.xml:168(title) +msgid "When you want to launch an instance you can only do that from an image. (True or False)" +msgstr "" + +#: ./doc/training-guides/bk001-ch004-associate-controller-node-quiz.xml:183(title) +msgid "An instance has a Private IP address which has the following properties? (choose all that apply)" +msgstr "" + +#: ./doc/training-guides/bk001-ch004-associate-controller-node-quiz.xml:187(para) +msgid "Used for communication between instances" +msgstr "" + +#: ./doc/training-guides/bk001-ch004-associate-controller-node-quiz.xml:190(para) ./doc/training-guides/bk001-ch002-associate-getting-started-quiz.xml:193(para) +msgid "VMware vShpere 4.1, update 1 or greater" +msgstr "" + +#: ./doc/training-guides/bk001-ch004-associate-controller-node-quiz.xml:193(para) +msgid "Stays the same, even after reboots" +msgstr "" + +#: ./doc/training-guides/bk001-ch004-associate-controller-node-quiz.xml:196(para) +msgid "Stays allocated, even if you terminate the instance" +msgstr "" + +#: ./doc/training-guides/bk001-ch004-associate-controller-node-quiz.xml:199(para) +msgid "To see the status of the Private IP addresses you use the following command: $ nova floating-ip-pool-list" +msgstr "" + +#: ./doc/training-guides/bk001-ch004-associate-controller-node-quiz.xml:208(title) +msgid "To start and stop and instance you can use the following options: (choose all that apply)" +msgstr "" + +#: ./doc/training-guides/bk001-ch004-associate-controller-node-quiz.xml:212(para) +msgid "Pause/Un-pause" +msgstr "" + +#: ./doc/training-guides/bk001-ch004-associate-controller-node-quiz.xml:215(para) +msgid "Suspend/Resume" +msgstr "" + +#: ./doc/training-guides/bk001-ch004-associate-controller-node-quiz.xml:218(para) +msgid "Reboot" +msgstr "" + +#: ./doc/training-guides/bk001-ch004-associate-controller-node-quiz.xml:221(para) +msgid "Evacuate" +msgstr "" + +#: ./doc/training-guides/bk001-ch004-associate-controller-node-quiz.xml:224(para) +msgid "Shutdown/Restart" +msgstr "" + +#: ./doc/training-guides/bk001-ch004-associate-controller-node-quiz.xml:232(title) +msgid "To create a network in OpenStack use the following command: $ neutron net-create net1 (True or False)" +msgstr "" + +#: ./doc/training-guides/bk001-ch004-associate-controller-node-quiz.xml:247(title) +msgid "Identity Service provides the following functions: (choose all that apply)" +msgstr "" + +#: ./doc/training-guides/bk001-ch004-associate-controller-node-quiz.xml:251(para) +msgid "Group policy objects" +msgstr "" + +#: ./doc/training-guides/bk001-ch004-associate-controller-node-quiz.xml:254(para) +msgid "Message queuing" +msgstr "" + +#: ./doc/training-guides/bk001-ch004-associate-controller-node-quiz.xml:257(para) ./doc/training-guides/module001-ch007-keystone-arch.xml:139(emphasis) +msgid "User management" +msgstr "" + +#: ./doc/training-guides/bk001-ch004-associate-controller-node-quiz.xml:260(para) +msgid "Publishing" +msgstr "" + +#: ./doc/training-guides/bk001-ch004-associate-controller-node-quiz.xml:263(para) +msgid "Service catalog" +msgstr "" + +#: ./doc/training-guides/bk001-ch004-associate-controller-node-quiz.xml:271(title) +msgid "The AMQP supports the following messaging bus options: (choose all that apply)" +msgstr "" + +#: ./doc/training-guides/bk001-ch004-associate-controller-node-quiz.xml:275(para) +msgid "ZeroMQ" +msgstr "" + +#: ./doc/training-guides/bk001-ch004-associate-controller-node-quiz.xml:281(para) +msgid "Tibco Rendezvous" +msgstr "" + +#: ./doc/training-guides/bk001-ch004-associate-controller-node-quiz.xml:284(para) +msgid "IBM WebSphere Message Broker" +msgstr "" + +#: ./doc/training-guides/bk001-ch004-associate-controller-node-quiz.xml:287(para) +msgid "Qpid" +msgstr "" + +#: ./doc/training-guides/bk001-ch004-associate-controller-node-quiz.xml:295(title) +msgid "OpenStack uses the term tenant but in earlier versions it used the term customer. (True or False)" +msgstr "" + +#: ./doc/training-guides/bk001-ch004-associate-controller-node-quiz.xml:312(title) +msgid "Associate Training Guide, Controller Node Quiz Answers" +msgstr "" + +#: ./doc/training-guides/bk001-ch004-associate-controller-node-quiz.xml:316(para) +msgid "B (False) - you can manage images through only the glance and nova clients or the Image Service and Compute APIs." +msgstr "" + +#: ./doc/training-guides/bk001-ch004-associate-controller-node-quiz.xml:320(para) +msgid "B (False) - Keypairs are SSH credentials that are injected into images when they are launched. For this to work, the image must contain the cloud-init package" +msgstr "" + +#: ./doc/training-guides/bk001-ch004-associate-controller-node-quiz.xml:324(para) +msgid "A, C, D, E - You can track costs per month by showing metrics like number of VCPUs, disks, RAM, and uptime of all your instances" +msgstr "" + +#: ./doc/training-guides/bk001-ch004-associate-controller-node-quiz.xml:328(para) +msgid "A, D, E - The following command-line clients are available for the respective services' APIs: cinder(python-cinderclient) Client for the Block Storage Service API. Use to create and manage volumes. glance(python-glanceclient) Client for the Image Service API. Use to create and manage images. keystone(python-keystoneclient) Client for the Identity Service API. Use to create and manage users, tenants, roles, endpoints, and credentials. nova(python-novaclient) Client for the Compute API and its extensions. Use to create and manage images, instances, and flavors. neutron(python-neutronclient) Client for the Networking API. Use to configure networks for guest servers. This client was previously known as neutron. swift(python-swiftclient) Client for the Object Storage API. Use to gather statistics, list items, update metadata, upload, download and delete files stored by the object storage service. Provides access to a swift installation for ad hoc processing. heat(python-heatclient)" +msgstr "" + +#: ./doc/training-guides/bk001-ch004-associate-controller-node-quiz.xml:344(para) ./doc/training-guides/bk001-ch004-associate-controller-node-quiz.xml:347(para) ./doc/training-guides/bk001-ch004-associate-controller-node-quiz.xml:365(para) +msgid "A (True)" +msgstr "" + +#: ./doc/training-guides/bk001-ch004-associate-controller-node-quiz.xml:350(para) +msgid "A, B" +msgstr "" + +#: ./doc/training-guides/bk001-ch004-associate-controller-node-quiz.xml:353(para) +msgid "B (False) - $ nova keypair-add KEY_NAME > MY_KEY.pem" +msgstr "" + +#: ./doc/training-guides/bk001-ch004-associate-controller-node-quiz.xml:356(para) +msgid "B (False) - you can launch and instance from an image or a volume" +msgstr "" + +#: ./doc/training-guides/bk001-ch004-associate-controller-node-quiz.xml:359(para) ./doc/training-guides/bk001-ch002-associate-getting-started-quiz.xml:222(para) +msgid "A, B, C" +msgstr "" + +#: ./doc/training-guides/bk001-ch004-associate-controller-node-quiz.xml:362(para) +msgid "A, B, C, D" +msgstr "" + +#: ./doc/training-guides/bk001-ch004-associate-controller-node-quiz.xml:368(para) +msgid "C, E" +msgstr "" + +#: ./doc/training-guides/bk001-ch004-associate-controller-node-quiz.xml:371(para) +msgid "A, B, E" +msgstr "" + +#: ./doc/training-guides/bk001-ch004-associate-controller-node-quiz.xml:374(para) +msgid "B (False) - Because the term project was used instead of tenant in earlier versions of OpenStack Compute, some command-line tools use --project_id instead of --tenant-id or --os-tenant-id to refer to a tenant ID." +msgstr "" + +#: ./doc/training-guides/bk002-ch007-operator-compute-node.xml:10(title) +msgid "Days 5 to 6, 09:00 to 11:00, 11:15 to 12:30" +msgstr "" + +#: ./doc/training-guides/bk002-ch007-operator-compute-node.xml:14(title) +msgid "Review Associate VM Placement" +msgstr "" + +#: ./doc/training-guides/bk002-ch007-operator-compute-node.xml:21(title) +msgid "Review Associate VM Provisioning Indepth" +msgstr "" + +#: ./doc/training-guides/bk002-ch007-operator-compute-node.xml:28(title) +msgid "Review Associate OpenStack Block Storage" +msgstr "" + +#: ./doc/training-guides/bk002-ch013-operator-object-storage-node.xml:10(title) +msgid "Day 9, 09:00 to 11:00, 11:15 to 12:30" +msgstr "" + +#: ./doc/training-guides/bk002-ch013-operator-object-storage-node.xml:14(title) +msgid "Review Associate Introduction to Object Storage" +msgstr "" + +#: ./doc/training-guides/bk002-ch013-operator-object-storage-node.xml:21(title) +msgid "Review Associate Features and Benefits" +msgstr "" + +#: ./doc/training-guides/bk002-ch013-operator-object-storage-node.xml:39(title) +msgid "Object Storage Building Blocks" +msgstr "" + +#: ./doc/training-guides/bk002-ch013-operator-object-storage-node.xml:46(title) +msgid "Swift Ring Builder" +msgstr "" + +#: ./doc/training-guides/bk002-ch013-operator-object-storage-node.xml:52(title) +msgid "More Swift Concepts" +msgstr "" + +#: ./doc/training-guides/bk002-ch013-operator-object-storage-node.xml:66(title) +msgid "Swift Account Reaper" +msgstr "" + +#: ./doc/training-guides/bk002-ch013-operator-object-storage-node.xml:73(title) +msgid "Swift Replication" +msgstr "" + +#: ./doc/training-guides/bk001-ch002-associate-getting-started-quiz.xml:8(title) +msgid "Day 1, 10:40 to 11:00" +msgstr "" + +#: ./doc/training-guides/bk001-ch002-associate-getting-started-quiz.xml:10(title) +msgid "Associate Training Guide, Getting Started Quiz Questions" +msgstr "" + +#: ./doc/training-guides/bk001-ch002-associate-getting-started-quiz.xml:15(title) +msgid "What are some of the compelling features of a cloud? (choose all that apply)" +msgstr "" + +#: ./doc/training-guides/bk001-ch002-associate-getting-started-quiz.xml:19(para) +msgid "On-demand self-service" +msgstr "" + +#: ./doc/training-guides/bk001-ch002-associate-getting-started-quiz.xml:22(para) +msgid "Resource pooling" +msgstr "" + +#: ./doc/training-guides/bk001-ch002-associate-getting-started-quiz.xml:25(para) +msgid "Metered or measured service" +msgstr "" + +#: ./doc/training-guides/bk001-ch002-associate-getting-started-quiz.xml:28(para) +msgid "Elasticity" +msgstr "" + +#: ./doc/training-guides/bk001-ch002-associate-getting-started-quiz.xml:31(para) +msgid "Network access" +msgstr "" + +#: ./doc/training-guides/bk001-ch002-associate-getting-started-quiz.xml:39(title) +msgid "What three service models does cloud computing provide? (choose all that apply)" +msgstr "" + +#: ./doc/training-guides/bk001-ch002-associate-getting-started-quiz.xml:43(para) +msgid "Software as a Service (SaaS)" +msgstr "" + +#: ./doc/training-guides/bk001-ch002-associate-getting-started-quiz.xml:46(para) +msgid "Applications as a Service (AaaS)" +msgstr "" + +#: ./doc/training-guides/bk001-ch002-associate-getting-started-quiz.xml:49(para) +msgid "Hardware as a Service (HaaS)" +msgstr "" + +#: ./doc/training-guides/bk001-ch002-associate-getting-started-quiz.xml:52(para) +msgid "Infrastructure as a Service (IaaS)" +msgstr "" + +#: ./doc/training-guides/bk001-ch002-associate-getting-started-quiz.xml:55(para) +msgid "Platform as a Service (PaaS)" +msgstr "" + +#: ./doc/training-guides/bk001-ch002-associate-getting-started-quiz.xml:63(title) +msgid "What does the OpenStack project aim to deliver? (choose all that apply)" +msgstr "" + +#: ./doc/training-guides/bk001-ch002-associate-getting-started-quiz.xml:67(para) +msgid "Simple to implement cloud solution" +msgstr "" + +#: ./doc/training-guides/bk001-ch002-associate-getting-started-quiz.xml:70(para) +msgid "Massively scalable cloud solution" +msgstr "" + +#: ./doc/training-guides/bk001-ch002-associate-getting-started-quiz.xml:73(para) +msgid "Feature rich cloud solution" +msgstr "" + +#: ./doc/training-guides/bk001-ch002-associate-getting-started-quiz.xml:76(para) +msgid "Multi-vendor interoperability cloud solution" +msgstr "" + +#: ./doc/training-guides/bk001-ch002-associate-getting-started-quiz.xml:79(para) +msgid "A new hypervisor cloud solution" +msgstr "" + +#: ./doc/training-guides/bk001-ch002-associate-getting-started-quiz.xml:87(title) +msgid "OpenStack code is freely available via the FreeBSD license. (True or False)" +msgstr "" + +#: ./doc/training-guides/bk001-ch002-associate-getting-started-quiz.xml:102(title) +msgid "OpenStack Swift is Object Storage. (True or False)" +msgstr "" + +#: ./doc/training-guides/bk001-ch002-associate-getting-started-quiz.xml:117(title) +msgid "OpenStack Networking is now called Quantum. (True or False)" +msgstr "" + +#: ./doc/training-guides/bk001-ch002-associate-getting-started-quiz.xml:132(title) +msgid "The Image service (Glance) in OpenStack provides: (Choose all that apply)" +msgstr "" + +#: ./doc/training-guides/bk001-ch002-associate-getting-started-quiz.xml:136(para) +msgid "Base Templates which users can start new compute instances" +msgstr "" + +#: ./doc/training-guides/bk001-ch002-associate-getting-started-quiz.xml:139(para) +msgid "Configuration of centralized policies across users and systems" +msgstr "" + +#: ./doc/training-guides/bk001-ch002-associate-getting-started-quiz.xml:142(para) +msgid "Available images for users to choose from or create their own from existing servers" +msgstr "" + +#: ./doc/training-guides/bk001-ch002-associate-getting-started-quiz.xml:145(para) +msgid "A central directory of users" +msgstr "" + +#: ./doc/training-guides/bk001-ch002-associate-getting-started-quiz.xml:148(para) +msgid "Ability to take store snapshots in the Image Service for backup" +msgstr "" + +#: ./doc/training-guides/bk001-ch002-associate-getting-started-quiz.xml:156(title) +msgid "OpenStack APIs are compatible with Amazon EC2 and Amazon S3. (True or False)" +msgstr "" + +#: ./doc/training-guides/bk001-ch002-associate-getting-started-quiz.xml:171(title) +msgid "Horizon is the OpenStack name for Compute. (True or False)" +msgstr "" + +#: ./doc/training-guides/bk001-ch002-associate-getting-started-quiz.xml:186(title) +msgid "Which Hypervisors can be supported in OpenStack? (Choose all that apply)" +msgstr "" + +#: ./doc/training-guides/bk001-ch002-associate-getting-started-quiz.xml:196(para) +msgid "bhyve (BSD)" +msgstr "" + +#: ./doc/training-guides/bk001-ch002-associate-getting-started-quiz.xml:199(para) +msgid "Xen" +msgstr "" + +#: ./doc/training-guides/bk001-ch002-associate-getting-started-quiz.xml:202(para) +msgid "LXC" +msgstr "" + +#: ./doc/training-guides/bk001-ch002-associate-getting-started-quiz.xml:212(title) +msgid "Associate Training Guide, Getting Started Quiz Answers" +msgstr "" + +#: ./doc/training-guides/bk001-ch002-associate-getting-started-quiz.xml:216(para) +msgid "A, B, C, D, E" +msgstr "" + +#: ./doc/training-guides/bk001-ch002-associate-getting-started-quiz.xml:219(para) +msgid "A, D, E" +msgstr "" + +#: ./doc/training-guides/bk001-ch002-associate-getting-started-quiz.xml:225(para) ./doc/training-guides/bk001-ch002-associate-getting-started-quiz.xml:231(para) ./doc/training-guides/bk001-ch002-associate-getting-started-quiz.xml:240(para) +msgid "B" +msgstr "" + +#: ./doc/training-guides/bk001-ch002-associate-getting-started-quiz.xml:228(para) ./doc/training-guides/bk001-ch002-associate-getting-started-quiz.xml:237(para) +msgid "A" +msgstr "" + +#: ./doc/training-guides/bk001-ch002-associate-getting-started-quiz.xml:234(para) +msgid "A, C, E" +msgstr "" + +#: ./doc/training-guides/bk001-ch002-associate-getting-started-quiz.xml:243(para) +msgid "A, B, D, E" +msgstr "" + +#. When image changes, this message will be marked fuzzy or untranslated for you. +#. It doesn't matter what you translate it to: it's not used at all. +#: ./doc/training-guides/module001-ch007-keystone-arch.xml:131(None) +msgid "@@image: 'figures/image19.png'; md5=60e446d2b0f887288e414af8dd338778" +msgstr "" + +#. More Content To be Added ... +#.
+#. Identity Service Concepts +#: ./doc/training-guides/module001-ch007-keystone-arch.xml:10(para) +msgid "The Identity service performs these functions:" +msgstr "" + +#: ./doc/training-guides/module001-ch007-keystone-arch.xml:14(para) +msgid "User management. Tracks users and their permissions." +msgstr "" + +#: ./doc/training-guides/module001-ch007-keystone-arch.xml:18(para) +msgid "Service catalog. Provides a catalog of available services with their API endpoints." +msgstr "" + +#: ./doc/training-guides/module001-ch007-keystone-arch.xml:22(para) +msgid "To understand the Identity Service, you must understand these concepts:" +msgstr "" + +#: ./doc/training-guides/module001-ch007-keystone-arch.xml:25(emphasis) +msgid "User" +msgstr "" + +#: ./doc/training-guides/module001-ch007-keystone-arch.xml:27(para) +msgid "Digital representation of a person, system, or service who uses OpenStack cloud services. Identity authentication services will validate that incoming request are being made by the user who claims to be making the call. Users have a login and may be assigned tokens to access resources. Users may be directly assigned to a particular tenant and behave as if they are contained in that tenant." +msgstr "" + +#: ./doc/training-guides/module001-ch007-keystone-arch.xml:38(emphasis) +msgid "Credentials" +msgstr "" + +#: ./doc/training-guides/module001-ch007-keystone-arch.xml:40(para) +msgid "Data that is known only by a user that proves who they are. In the Identity Service, examples are:" +msgstr "" + +#: ./doc/training-guides/module001-ch007-keystone-arch.xml:44(para) +msgid "Username and password" +msgstr "" + +#: ./doc/training-guides/module001-ch007-keystone-arch.xml:47(para) +msgid "Username and API key" +msgstr "" + +#: ./doc/training-guides/module001-ch007-keystone-arch.xml:50(para) +msgid "An authentication token provided by the Identity Service" +msgstr "" + +#: ./doc/training-guides/module001-ch007-keystone-arch.xml:57(emphasis) +msgid "Authentication" +msgstr "" + +#: ./doc/training-guides/module001-ch007-keystone-arch.xml:59(para) +msgid "The act of confirming the identity of a user. The Identity Service confirms an incoming request by validating a set of credentials supplied by the user. These credentials are initially a username and password or a username and API key. In response to these credentials, the Identity Service issues the user an authentication token, which the user provides in subsequent requests." +msgstr "" + +#: ./doc/training-guides/module001-ch007-keystone-arch.xml:71(emphasis) +msgid "Token" +msgstr "" + +#: ./doc/training-guides/module001-ch007-keystone-arch.xml:73(para) +msgid "An arbitrary bit of text that is used to access resources. Each token has a scope which describes which resources are accessible with it. A token may be revoked at anytime and is valid for a finite duration." +msgstr "" + +#: ./doc/training-guides/module001-ch007-keystone-arch.xml:77(para) +msgid "While the Identity Service supports token-based authentication in this release, the intention is for it to support additional protocols in the future. The intent is for it to be an integration service foremost, and not aspire to be a full-fledged identity store and management solution." +msgstr "" + +#: ./doc/training-guides/module001-ch007-keystone-arch.xml:86(emphasis) +msgid "Tenant" +msgstr "" + +#: ./doc/training-guides/module001-ch007-keystone-arch.xml:88(para) +msgid "A container used to group or isolate resources and/or identity objects. Depending on the service operator, a tenant may map to a customer, account, organization, or project." +msgstr "" + +#: ./doc/training-guides/module001-ch007-keystone-arch.xml:96(emphasis) +msgid "Service" +msgstr "" + +#: ./doc/training-guides/module001-ch007-keystone-arch.xml:98(para) +msgid "An OpenStack service, such as Compute (Nova), Object Storage (Swift), or Image Service (Glance). Provides one or more endpoints through which users can access resources and perform operations." +msgstr "" + +#: ./doc/training-guides/module001-ch007-keystone-arch.xml:105(emphasis) +msgid "Endpoint" +msgstr "" + +#: ./doc/training-guides/module001-ch007-keystone-arch.xml:107(para) +msgid "An network-accessible address, usually described by URL, from where you access a service. If using an extension for templates, you can create an endpoint template, which represents the templates of all the consumable services that are available across the regions." +msgstr "" + +#: ./doc/training-guides/module001-ch007-keystone-arch.xml:116(emphasis) +msgid "Role" +msgstr "" + +#: ./doc/training-guides/module001-ch007-keystone-arch.xml:118(para) +msgid "A personality that a user assumes that enables them to perform a specific set of operations. A role includes a set of rights and privileges. A user assuming that role inherits those rights and privileges." +msgstr "" + +#: ./doc/training-guides/module001-ch007-keystone-arch.xml:122(para) +msgid "In the Identity Service, a token that is issued to a user includes the list of roles that user can assume. Services that are being called by that user determine how they interpret the set of roles a user has and which operations or resources each role grants access to." +msgstr "" + +#: ./doc/training-guides/module001-ch007-keystone-arch.xml:128(title) +msgid "Keystone Authentication" +msgstr "" + +#: ./doc/training-guides/module001-ch007-keystone-arch.xml:141(para) +msgid "The main components of Identity user management are:" +msgstr "" + +#: ./doc/training-guides/module001-ch007-keystone-arch.xml:145(para) +msgid "Users" +msgstr "" + +#: ./doc/training-guides/module001-ch007-keystone-arch.xml:148(para) +msgid "Tenants" +msgstr "" + +#: ./doc/training-guides/module001-ch007-keystone-arch.xml:151(para) +msgid "Roles" +msgstr "" + +#: ./doc/training-guides/module001-ch007-keystone-arch.xml:154(para) +msgid "A user represents a human user, and has associated information such as username, password and email. This example creates a user named \"alice\":" +msgstr "" + +#: ./doc/training-guides/module001-ch007-keystone-arch.xml:158(para) +msgid "A tenant can be a project, group, or organization. Whenever you make requests to OpenStack services, you must specify a tenant. For example, if you query the Compute service for a list of running instances, you get a list of all running instances for the specified tenant. This example creates a tenant named \"acme\":" +msgstr "" + +#: ./doc/training-guides/module001-ch007-keystone-arch.xml:165(para) +msgid "A role captures what operations a user is permitted to perform in a given tenant. This example creates a role named \"compute-user\":" +msgstr "" + +#: ./doc/training-guides/module001-ch007-keystone-arch.xml:169(para) +msgid "The Identity service associates a user with a tenant and a role. To continue with our previous examples, we may wish to assign the \"alice\" user the \"compute-user\" role in the \"acme\" tenant:" +msgstr "" + +#: ./doc/training-guides/module001-ch007-keystone-arch.xml:175(para) +msgid "A user can be assigned different roles in different tenants. For example, Alice may also have the \"admin\" role in the \"Cyberdyne\" tenant. A user can also be assigned multiple roles in the same tenant." +msgstr "" + +#: ./doc/training-guides/module001-ch007-keystone-arch.xml:179(para) +msgid "The /etc/[SERVICE_CODENAME]/policy.json file controls what users are allowed to do for a given service. For example, /etc/nova/policy.json specifies the access policy for the Compute service, /etc/glance/policy.json specifies the access policy for the Image service, and /etc/keystone/policy.json specifies the access policy for the Identity service." +msgstr "" + +#: ./doc/training-guides/module001-ch007-keystone-arch.xml:189(para) +msgid "The default policy.json files in the Compute, Identity, and Image service recognize only the admin role: all operations that do not require the admin role will be accessible by any user that has any role in a tenant." +msgstr "" + +#: ./doc/training-guides/module001-ch007-keystone-arch.xml:194(para) +msgid "If you wish to restrict users from performing operations in, say, the Compute service, you need to create a role in the Identity service and then modify /etc/nova/policy.json so that this role is required for Compute operations." +msgstr "" + +#: ./doc/training-guides/module001-ch007-keystone-arch.xml:199(para) +msgid "For example, this line in /etc/nova/policy.json specifies that there are no restrictions on which users can create volumes: if the user has any role in a tenant, they will be able to create volumes in that tenant." +msgstr "" + +#: ./doc/training-guides/module001-ch007-keystone-arch.xml:207(emphasis) +msgid "Service Management" +msgstr "" + +#: ./doc/training-guides/module001-ch007-keystone-arch.xml:210(para) +msgid "The Identity Service provides the following service management functions:" +msgstr "" + +#: ./doc/training-guides/module001-ch007-keystone-arch.xml:214(para) +msgid "Services" +msgstr "" + +#: ./doc/training-guides/module001-ch007-keystone-arch.xml:217(para) +msgid "Endpoints" +msgstr "" + +#: ./doc/training-guides/module001-ch007-keystone-arch.xml:220(para) +msgid "The Identity Service also maintains a user that corresponds to each service, such as a user named nova, for the Compute service) and a special service tenant, which is called service." +msgstr "" + +#: ./doc/training-guides/module001-ch007-keystone-arch.xml:224(para) +msgid "The commands for creating services and endpoints are described in a later section." +msgstr "" + +#: ./doc/training-guides/card041-neutron.xml:7(title) ./doc/training-guides/card041-neutron.xml:16(emphasis) +msgid "Install Neutron" +msgstr "" + +#: ./doc/training-guides/card041-neutron.xml:10(para) +msgid "OpenVSwitch is one of many options, but for now we will stick with OVS." +msgstr "" + +#: ./doc/training-guides/bk001-ch011-associate-assessment.xml:6(title) +msgid "Assessment" +msgstr "" + +#: ./doc/training-guides/bk001-ch011-associate-assessment.xml:8(title) +msgid "Day 2, 15:00 to 16:00" +msgstr "" + +#: ./doc/training-guides/bk001-ch011-associate-assessment.xml:12(title) +msgid "Questions" +msgstr "" + +#: ./doc/training-guides/bk001-ch011-associate-assessment.xml:14(caption) +msgid "Assessment Question 1" +msgstr "" + +#: ./doc/training-guides/bk001-ch011-associate-assessment.xml:19(th) ./doc/training-guides/bk001-ch011-associate-assessment.xml:40(th) +msgid "Task" +msgstr "" + +#: ./doc/training-guides/bk001-ch011-associate-assessment.xml:20(th) ./doc/training-guides/bk001-ch011-associate-assessment.xml:41(th) +msgid "Completed?" +msgstr "" + +#: ./doc/training-guides/bk001-ch011-associate-assessment.xml:26(para) ./doc/training-guides/bk001-ch011-associate-assessment.xml:47(para) +msgid "Configure a ...." +msgstr "" + +#: ./doc/training-guides/bk001-ch011-associate-assessment.xml:35(caption) +msgid "Assessment Question 2" +msgstr "" + +#. When image changes, this message will be marked fuzzy or untranslated for you. +#. It doesn't matter what you translate it to: it's not used at all. +#: ./doc/training-guides/module001-ch010-vm-provisioning-indepth.xml:118(None) +msgid "@@image: 'figures/image02.png'; md5=58686bf772bae30c415ec79e1dcf50ff" +msgstr "" + +#: ./doc/training-guides/module001-ch010-vm-provisioning-indepth.xml:7(title) ./doc/training-guides/bk001-ch005-associate-compute-node.xml:21(title) +msgid "VM Provisioning Indepth" +msgstr "" + +#: ./doc/training-guides/module001-ch010-vm-provisioning-indepth.xml:9(para) +msgid "The request flow for provisioning an Instance goes like this:" +msgstr "" + +#: ./doc/training-guides/module001-ch010-vm-provisioning-indepth.xml:13(para) +msgid "Dashboard or CLI gets the user credentials authenticates with Keystone via REST api." +msgstr "" + +#: ./doc/training-guides/module001-ch010-vm-provisioning-indepth.xml:17(para) +msgid "Keystone authenticate the credentials and generate & send back auth-token which will be used for sending request to other Components through REST-call." +msgstr "" + +#: ./doc/training-guides/module001-ch010-vm-provisioning-indepth.xml:22(para) +msgid "Dashboard or CLI convert the new instance request specified in ‘launch instance’ or ‘nova-boot’ form to REST API request and send it to nova-api." +msgstr "" + +#: ./doc/training-guides/module001-ch010-vm-provisioning-indepth.xml:27(para) +msgid "nova-api receive the request and sends the request for validation auth-token and access permission to keystone." +msgstr "" + +#: ./doc/training-guides/module001-ch010-vm-provisioning-indepth.xml:32(para) +msgid "Keystone validates the token and sends updated auth headers with roles and permissions." +msgstr "" + +#: ./doc/training-guides/module001-ch010-vm-provisioning-indepth.xml:36(para) +msgid "nova-api interacts with nova-database." +msgstr "" + +#: ./doc/training-guides/module001-ch010-vm-provisioning-indepth.xml:39(para) +msgid "Creates initial db entry for new instance." +msgstr "" + +#: ./doc/training-guides/module001-ch010-vm-provisioning-indepth.xml:42(para) +msgid "nova-api sends the rpc.call request to nova-scheduler excepting to get updated instance entry with host ID specified." +msgstr "" + +#: ./doc/training-guides/module001-ch010-vm-provisioning-indepth.xml:47(para) +msgid "nova-scheduler picks the request from the queue." +msgstr "" + +#: ./doc/training-guides/module001-ch010-vm-provisioning-indepth.xml:50(para) +msgid "nova-scheduler interacts with nova-database to find an appropriate host via filtering and weighing." +msgstr "" + +#: ./doc/training-guides/module001-ch010-vm-provisioning-indepth.xml:54(para) +msgid "Returns the updated instance entry with appropriate host ID after filtering and weighing." +msgstr "" + +#: ./doc/training-guides/module001-ch010-vm-provisioning-indepth.xml:56(para) +msgid "nova-scheduler sends the rpc.cast request to nova-compute for ‘launching instance’ on appropriate host ." +msgstr "" + +#: ./doc/training-guides/module001-ch010-vm-provisioning-indepth.xml:60(para) +msgid "nova-compute picks the request from the queue." +msgstr "" + +#: ./doc/training-guides/module001-ch010-vm-provisioning-indepth.xml:63(para) +msgid "nova-compute send the rpc.call request to nova-conductor to fetch the instance information such as host ID and flavor( Ram , CPU ,Disk)." +msgstr "" + +#: ./doc/training-guides/module001-ch010-vm-provisioning-indepth.xml:68(para) +msgid "nova-conductor picks the request from the queue." +msgstr "" + +#: ./doc/training-guides/module001-ch010-vm-provisioning-indepth.xml:71(para) +msgid "nova-conductor interacts with nova-database." +msgstr "" + +#: ./doc/training-guides/module001-ch010-vm-provisioning-indepth.xml:74(para) +msgid "Return the instance information." +msgstr "" + +#: ./doc/training-guides/module001-ch010-vm-provisioning-indepth.xml:75(para) +msgid "nova-compute picks the instance information from the queue." +msgstr "" + +#: ./doc/training-guides/module001-ch010-vm-provisioning-indepth.xml:79(para) +msgid "nova-compute does the REST call by passing auth-token to glance-api to get the Image URI by Image ID from glance and upload image from image storage." +msgstr "" + +#: ./doc/training-guides/module001-ch010-vm-provisioning-indepth.xml:84(para) +msgid "glance-api validates the auth-token with keystone." +msgstr "" + +#: ./doc/training-guides/module001-ch010-vm-provisioning-indepth.xml:87(para) +msgid "nova-compute get the image metadata." +msgstr "" + +#: ./doc/training-guides/module001-ch010-vm-provisioning-indepth.xml:88(para) +msgid "nova-compute does the REST-call by passing auth-token to Network API to allocate and configure the network such that instance gets the IP address." +msgstr "" + +#: ./doc/training-guides/module001-ch010-vm-provisioning-indepth.xml:93(para) +msgid "quantum-server validates the auth-token with keystone." +msgstr "" + +#: ./doc/training-guides/module001-ch010-vm-provisioning-indepth.xml:97(para) +msgid "nova-compute get the network info." +msgstr "" + +#: ./doc/training-guides/module001-ch010-vm-provisioning-indepth.xml:100(para) +msgid "nova-compute does the REST call by passing auth-token to Volume API to attach volumes to instance." +msgstr "" + +#: ./doc/training-guides/module001-ch010-vm-provisioning-indepth.xml:104(para) +msgid "cinder-api validates the auth-token with keystone." +msgstr "" + +#: ./doc/training-guides/module001-ch010-vm-provisioning-indepth.xml:107(para) +msgid "nova-compute gets the block storage info." +msgstr "" + +#: ./doc/training-guides/module001-ch010-vm-provisioning-indepth.xml:110(para) +msgid "nova-compute generates data for hypervisor driver and executes request on Hypervisor( via libvirt or api)." +msgstr "" + +#: ./doc/training-guides/module001-ch010-vm-provisioning-indepth.xml:115(title) +msgid "Nova VM Provisioning" +msgstr "" + +#: ./doc/training-guides/bk002-ch011-operator-network-node-lab.xml:6(title) +msgid "Network Node Lab" +msgstr "" + +#: ./doc/training-guides/bk002-ch011-operator-network-node-lab.xml:8(title) +msgid "Days 7 to 8, 13:30 to 14:45, 15:00 to 17:00" +msgstr "" + +#: ./doc/training-guides/bk002-ch001-operator-getting-started.xml:6(title) ./doc/training-guides/bk001-ch001-associate-getting-started.xml:6(title) ./doc/training-guides/lab000-virtualbox-basics.xml:8(guilabel) +msgid "Getting Started" +msgstr "" + +#: ./doc/training-guides/bk002-ch001-operator-getting-started.xml:8(title) +msgid "Day 1, 09:00 to 11:00, 11:15 to 12:30" +msgstr "" + +#: ./doc/training-guides/bk002-ch001-operator-getting-started.xml:13(para) +msgid "Training would take 2.5 months self paced, (5) 2 week periods with a user group meeting, or 40 hours instructor led with 40 hours of self paced lab time." +msgstr "" + +#: ./doc/training-guides/bk002-ch001-operator-getting-started.xml:15(para) ./doc/training-guides/bk001-ch001-associate-getting-started.xml:15(para) +msgid "Prerequisites" +msgstr "" + +#: ./doc/training-guides/bk002-ch001-operator-getting-started.xml:17(para) +msgid "Associate guide training" +msgstr "" + +#: ./doc/training-guides/bk002-ch001-operator-getting-started.xml:18(para) +msgid "Associate guide virtualbox scripted install completed and running" +msgstr "" + +#: ./doc/training-guides/bk002-ch001-operator-getting-started.xml:22(title) +msgid "Review Associate Introduction" +msgstr "" + +#: ./doc/training-guides/bk002-ch001-operator-getting-started.xml:29(title) +msgid "Review Associate Brief Overview" +msgstr "" + +#: ./doc/training-guides/bk002-ch001-operator-getting-started.xml:36(title) +msgid "Review Associate Core Projects" +msgstr "" + +#: ./doc/training-guides/bk002-ch001-operator-getting-started.xml:43(title) +msgid "Review Associate OpenStack Architecture" +msgstr "" + +#: ./doc/training-guides/bk002-ch001-operator-getting-started.xml:50(title) +msgid "Review Associate Virtual Machine Provisioning Walk-Through" +msgstr "" + +#: ./doc/training-guides/card008.xml:7(title) +msgid "Understanding the RefStack Architecture" +msgstr "" + +#: ./doc/training-guides/module002-ch002-openstack-networking-concepts.xml:7(title) ./doc/training-guides/bk001-ch007-associate-network-node.xml:21(title) +msgid "OpenStack Networking Concepts" +msgstr "" + +#: ./doc/training-guides/module002-ch002-openstack-networking-concepts.xml:8(emphasis) +msgid "Network Types" +msgstr "" + +#: ./doc/training-guides/module002-ch002-openstack-networking-concepts.xml:9(para) +msgid "The OpenStack Networking configuration provided by the Rackspace Private Cloud cookbooks allows you to choose between VLAN or GRE isolated networks, both provider- and tenant-specific. From the provider side, an administrator can also create a flat network." +msgstr "" + +#: ./doc/training-guides/module002-ch002-openstack-networking-concepts.xml:14(para) +msgid "The type of network that is used for private tenant networks is determined by the network_type attribute, which can be edited in the Chef override_attributes. This attribute sets both the default provider network type and the only type of network that tenants are able to create. Administrators can always create flat and VLAN networks. GRE networks of any type require the network_type to be set to gre." +msgstr "" + +#: ./doc/training-guides/module002-ch002-openstack-networking-concepts.xml:21(emphasis) +msgid "Namespaces" +msgstr "" + +#: ./doc/training-guides/module002-ch002-openstack-networking-concepts.xml:22(para) +msgid "For each network you create, the Network node (or Controller node, if combined) will have a unique network namespace (netns) created by the DHCP and Metadata agents. The netns hosts an interface and IP addresses for dnsmasq and the quantum-ns-metadata-proxy. You can view the namespaces with the ip netns [list], and can interact with the namespaces with the ip netns exec <namespace> <command> command." +msgstr "" + +#: ./doc/training-guides/module002-ch002-openstack-networking-concepts.xml:30(emphasis) +msgid "Metadata" +msgstr "" + +#: ./doc/training-guides/module002-ch002-openstack-networking-concepts.xml:31(para) +msgid "Not all networks or VMs need metadata access. Rackspace recommends that you use metadata if you are using a single network. If you need metadata, you may also need a default route. (If you don't need a default route, no-gateway will do.)" +msgstr "" + +#: ./doc/training-guides/module002-ch002-openstack-networking-concepts.xml:36(para) +msgid "To communicate with the metadata IP address inside the namespace, instances need a route for the metadata network that points to the dnsmasq IP address on the same namespaced interface. OpenStack Networking only injects a route when you do not specify a gateway-ip in the subnet." +msgstr "" + +#: ./doc/training-guides/module002-ch002-openstack-networking-concepts.xml:41(para) +msgid "If you need to use a default route and provide instances with access to the metadata route, create the subnet without specifying a gateway IP and with a static route from 0.0.0.0/0 to your gateway IP address. Adjust the DHCP allocation pool so that it will not assign the gateway IP. With this configuration, dnsmasq will pass both routes to instances. This way, metadata will be routed correctly without any changes on the external gateway." +msgstr "" + +#: ./doc/training-guides/module002-ch002-openstack-networking-concepts.xml:49(emphasis) +msgid "OVS Bridges" +msgstr "" + +#: ./doc/training-guides/module002-ch002-openstack-networking-concepts.xml:50(para) +msgid "An OVS bridge for provider traffic is created and configured on the nodes where single-network-node and single-compute are applied. Bridges are created, but physical interfaces are not added. An OVS bridge is not created on a Controller-only node." +msgstr "" + +#: ./doc/training-guides/module002-ch002-openstack-networking-concepts.xml:55(para) +msgid "When creating networks, you can specify the type and properties, such as Flat vs. VLAN, Shared vs. Tenant, or Provider vs. Overlay. These properties identify and determine the behavior and resources of instances attached to the network. The cookbooks will create bridges for the configuration that you specify, although they do not add physical interfaces to provider bridges. For example, if you specify a network type of GRE, a br-tun tunnel bridge will be created to handle overlay traffic." +msgstr "" + +#: ./doc/training-guides/card037-rabbitmq.xml:7(title) +msgid "Installing RabbitMQ" +msgstr "" + +#. When image changes, this message will be marked fuzzy or untranslated for you. +#. It doesn't matter what you translate it to: it's not used at all. +#: ./doc/training-guides/module002-ch003-neutron-use-cases.xml:32(None) +msgid "@@image: 'figures/image34.png'; md5=de380963b3137c842e8a1795bc376558" +msgstr "" + +#. When image changes, this message will be marked fuzzy or untranslated for you. +#. It doesn't matter what you translate it to: it's not used at all. +#: ./doc/training-guides/module002-ch003-neutron-use-cases.xml:46(None) +msgid "@@image: 'figures/image35.png'; md5=9399b9e427152d07037568bdf38fb184" +msgstr "" + +#. When image changes, this message will be marked fuzzy or untranslated for you. +#. It doesn't matter what you translate it to: it's not used at all. +#: ./doc/training-guides/module002-ch003-neutron-use-cases.xml:68(None) +msgid "@@image: 'figures/image36.png'; md5=880830d2a425db41661840218713072d" +msgstr "" + +#. When image changes, this message will be marked fuzzy or untranslated for you. +#. It doesn't matter what you translate it to: it's not used at all. +#: ./doc/training-guides/module002-ch003-neutron-use-cases.xml:104(None) +msgid "@@image: 'figures/image37.png'; md5=7371790c2697148cafbdfd50c55cc2f2" +msgstr "" + +#. When image changes, this message will be marked fuzzy or untranslated for you. +#. It doesn't matter what you translate it to: it's not used at all. +#: ./doc/training-guides/module002-ch003-neutron-use-cases.xml:126(None) +msgid "@@image: 'figures/image38.png'; md5=2e335e5d101e9b4d710e320a6dfa363e" +msgstr "" + +#: ./doc/training-guides/module002-ch003-neutron-use-cases.xml:7(title) +msgid "Neutron Use Cases" +msgstr "" + +#: ./doc/training-guides/module002-ch003-neutron-use-cases.xml:8(para) +msgid "As of now you must be wondering, how to use these awesome features that OpenStack Networking has given to us." +msgstr "" + +#: ./doc/training-guides/module002-ch003-neutron-use-cases.xml:10(guilabel) +msgid "Use Case: Single Flat Network" +msgstr "" + +#: ./doc/training-guides/module002-ch003-neutron-use-cases.xml:11(para) +msgid "In the simplest use case, a single OpenStack Networking network exists. This is a \"shared\" network, meaning it is visible to all tenants via the OpenStack Networking API. Tenant VMs have a single NIC, and receive a fixed IP address from the subnet(s) associated with that network. This essentially maps to the FlatManager and FlatDHCPManager models provided by OpenStack Compute. Floating IPs are not supported." +msgstr "" + +#: ./doc/training-guides/module002-ch003-neutron-use-cases.xml:19(para) +msgid "It is common that such an OpenStack Networking network is a \"provider network\", meaning it was created by the OpenStack administrator to map directly to an existing physical network in the data center. This allows the provider to use a physical router on that data center network as the gateway for VMs to reach the outside world. For each subnet on an external network, the gateway configuration on the physical router must be manually configured outside of OpenStack." +msgstr "" + +#: ./doc/training-guides/module002-ch003-neutron-use-cases.xml:29(title) +msgid "Single Flat Network" +msgstr "" + +#: ./doc/training-guides/module002-ch003-neutron-use-cases.xml:36(guilabel) +msgid "Use Case: Multiple Flat Network" +msgstr "" + +#: ./doc/training-guides/module002-ch003-neutron-use-cases.xml:38(para) +msgid "This use case is very similar to the above Single Flat Network use case, except that tenants see multiple shared networks via the OpenStack Networking API and can choose which network (or networks) to plug into." +msgstr "" + +#: ./doc/training-guides/module002-ch003-neutron-use-cases.xml:43(title) +msgid "Multiple Flat Network" +msgstr "" + +#: ./doc/training-guides/module002-ch003-neutron-use-cases.xml:50(guilabel) +msgid "Use Case: Mixed Flat and Private Network" +msgstr "" + +#: ./doc/training-guides/module002-ch003-neutron-use-cases.xml:52(para) +msgid "This use case is an extension of the above flat network use cases, in which tenants also optionally have access to private per-tenant networks. In addition to seeing one or more shared networks via the OpenStack Networking API, tenants can create additional networks that are only visible to users of that tenant. When creating VMs, those VMs can have NICs on any of the shared networks and/or any of the private networks belonging to the tenant. This enables the creation of \"multi-tier\" topologies using VMs with multiple NICs. It also supports a model where a VM acting as a gateway can provide services such as routing, NAT, or load balancing." +msgstr "" + +#: ./doc/training-guides/module002-ch003-neutron-use-cases.xml:65(title) +msgid "Mixed Flat and Private Network" +msgstr "" + +#: ./doc/training-guides/module002-ch003-neutron-use-cases.xml:72(guilabel) +msgid "Use Case: Provider Router with Private Networks" +msgstr "" + +#: ./doc/training-guides/module002-ch003-neutron-use-cases.xml:74(para) +msgid "This use provides each tenant with one or more private networks, which connect to the outside world via an OpenStack Networking router. The case where each tenant gets exactly one network in this form maps to the same logical topology as the VlanManager in OpenStack Compute (of course, OpenStack Networking doesn't require VLANs). Using the OpenStack Networking API, the tenant would only see a network for each private network assigned to that tenant. The router object in the API is created and owned by the cloud admin." +msgstr "" + +#: ./doc/training-guides/module002-ch003-neutron-use-cases.xml:84(para) +msgid "This model supports giving VMs public addresses using \"floating IPs\", in which the router maps public addresses from the external network to fixed IPs on private networks. Hosts without floating IPs can still create outbound connections to the external network, as the provider router performs SNAT to the router's external IP. The IP address of the physical router is used as the gateway_ip of the external network subnet, so the provider has a default router for Internet traffic." +msgstr "" + +#: ./doc/training-guides/module002-ch003-neutron-use-cases.xml:93(para) +msgid "The router provides L3 connectivity between private networks, meaning that different tenants can reach each others instances unless additional filtering, such as security groups, is used. Because there is only a single router, tenant networks cannot use overlapping IPs. Thus, it is likely that the admin would create the private networks on behalf of tenants." +msgstr "" + +#: ./doc/training-guides/module002-ch003-neutron-use-cases.xml:101(title) +msgid "Provider Router with Private Networks" +msgstr "" + +#: ./doc/training-guides/module002-ch003-neutron-use-cases.xml:108(guilabel) +msgid "Use Case: Per-tenant Routers with Private Networks" +msgstr "" + +#: ./doc/training-guides/module002-ch003-neutron-use-cases.xml:110(para) +msgid "A more advanced router scenario in which each tenant gets at least one router, and potentially has access to the OpenStack Networking API to create additional routers. The tenant can create their own networks, potentially uplinking those networks to a router. This model enables tenant-defined multi-tier applications, with each tier being a separate network behind the router. Since there are multiple routers, tenant subnets can be overlapping without conflicting, since access to external networks all happens via SNAT or Floating IPs. Each router uplink and floating IP is allocated from the external network subnet." +msgstr "" + +#: ./doc/training-guides/module002-ch003-neutron-use-cases.xml:123(title) +msgid "Per-tenant Routers with Private Networks" +msgstr "" + +#: ./doc/training-guides/module003-ch002-features-benifits.xml:7(title) +msgid "Features and Benifits" +msgstr "" + +#: ./doc/training-guides/module003-ch002-features-benifits.xml:12(th) +msgid "Features" +msgstr "" + +#: ./doc/training-guides/module003-ch002-features-benifits.xml:13(th) +msgid "Benefits" +msgstr "" + +#: ./doc/training-guides/module003-ch002-features-benifits.xml:17(emphasis) +msgid "Leverages commodity hardware" +msgstr "" + +#: ./doc/training-guides/module003-ch002-features-benifits.xml:20(td) +msgid "No lock-in, lower price/GB" +msgstr "" + +#: ./doc/training-guides/module003-ch002-features-benifits.xml:26(emphasis) +msgid "HDD/node failure agnostic" +msgstr "" + +#: ./doc/training-guides/module003-ch002-features-benifits.xml:28(td) +msgid "Self healingReliability, data redundancy protecting from failures" +msgstr "" + +#: ./doc/training-guides/module003-ch002-features-benifits.xml:35(emphasis) +msgid "Unlimited storage" +msgstr "" + +#: ./doc/training-guides/module003-ch002-features-benifits.xml:37(td) +msgid "Huge & flat namespace, highly scalable read/write accessAbility to serve content directly from storage system" +msgstr "" + +#: ./doc/training-guides/module003-ch002-features-benifits.xml:45(emphasis) +msgid "Multi-dimensional scalability" +msgstr "" + +#: ./doc/training-guides/module003-ch002-features-benifits.xml:44(td) +msgid " (scale out architecture)Scale vertically and horizontally-distributed storage" +msgstr "" + +#: ./doc/training-guides/module003-ch002-features-benifits.xml:49(td) +msgid "Backup and archive large amounts of data with linear performance" +msgstr "" + +#: ./doc/training-guides/module003-ch002-features-benifits.xml:55(emphasis) +msgid "Account/Container/Object structure" +msgstr "" + +#: ./doc/training-guides/module003-ch002-features-benifits.xml:54(td) +msgid "No nesting, not a traditional file system" +msgstr "" + +#: ./doc/training-guides/module003-ch002-features-benifits.xml:59(td) +msgid "Optimized for scaleScales to multiple petabytes, billions of objects" +msgstr "" + +#: ./doc/training-guides/module003-ch002-features-benifits.xml:66(emphasis) +msgid "Built-in replication3x+ data redundancy" +msgstr "" + +#: ./doc/training-guides/module003-ch002-features-benifits.xml:65(td) +msgid " compared to 2x on RAID" +msgstr "" + +#: ./doc/training-guides/module003-ch002-features-benifits.xml:70(td) +msgid "Configurable number of accounts, container and object copies for high availability" +msgstr "" + +#: ./doc/training-guides/module003-ch002-features-benifits.xml:77(emphasis) +msgid "Easily add capacity" +msgstr "" + +#: ./doc/training-guides/module003-ch002-features-benifits.xml:76(td) +msgid " unlike RAID resize" +msgstr "" + +#: ./doc/training-guides/module003-ch002-features-benifits.xml:80(td) +msgid "Elastic data scaling with ease" +msgstr "" + +#: ./doc/training-guides/module003-ch002-features-benifits.xml:86(emphasis) +msgid "No central database" +msgstr "" + +#: ./doc/training-guides/module003-ch002-features-benifits.xml:88(td) +msgid "Higher performance, no bottlenecks" +msgstr "" + +#: ./doc/training-guides/module003-ch002-features-benifits.xml:94(emphasis) +msgid "RAID not required" +msgstr "" + +#: ./doc/training-guides/module003-ch002-features-benifits.xml:96(td) +msgid "Handle lots of small, random reads and writes efficiently" +msgstr "" + +#: ./doc/training-guides/module003-ch002-features-benifits.xml:102(emphasis) +msgid "Built-in management utilities" +msgstr "" + +#: ./doc/training-guides/module003-ch002-features-benifits.xml:105(td) +msgid "Account Management: Create, add, verify, delete usersContainer Management: Upload, download, verifyMonitoring: Capacity, host, network, log trawling, cluster health" +msgstr "" + +#: ./doc/training-guides/module003-ch002-features-benifits.xml:114(emphasis) +msgid "Drive auditing" +msgstr "" + +#: ./doc/training-guides/module003-ch002-features-benifits.xml:116(td) +msgid "Detect drive failures preempting data corruption" +msgstr "" + +#: ./doc/training-guides/module003-ch002-features-benifits.xml:122(emphasis) +msgid "Expiring objects" +msgstr "" + +#: ./doc/training-guides/module003-ch002-features-benifits.xml:124(td) +msgid "Users can set an expiration time or a TTL on an object to control access" +msgstr "" + +#: ./doc/training-guides/module003-ch002-features-benifits.xml:131(emphasis) +msgid "Direct object access" +msgstr "" + +#: ./doc/training-guides/module003-ch002-features-benifits.xml:133(td) +msgid "Enable direct browser access to content, such as for a control panel" +msgstr "" + +#: ./doc/training-guides/module003-ch002-features-benifits.xml:140(emphasis) +msgid "Realtime visibility into client requests" +msgstr "" + +#: ./doc/training-guides/module003-ch002-features-benifits.xml:143(td) +msgid "Know what users are requesting" +msgstr "" + +#: ./doc/training-guides/module003-ch002-features-benifits.xml:149(emphasis) +msgid "Supports S3 API" +msgstr "" + +#: ./doc/training-guides/module003-ch002-features-benifits.xml:151(td) +msgid "Utilize tools that were designed for the popular S3 API" +msgstr "" + +#: ./doc/training-guides/module003-ch002-features-benifits.xml:157(emphasis) +msgid "Restrict containers per account" +msgstr "" + +#: ./doc/training-guides/module003-ch002-features-benifits.xml:160(td) +msgid "Limit access to control usage by user" +msgstr "" + +#: ./doc/training-guides/module003-ch002-features-benifits.xml:166(emphasis) +msgid "Support for NetApp, Nexenta, SolidFire" +msgstr "" + +#: ./doc/training-guides/module003-ch002-features-benifits.xml:169(td) +msgid "Unified support for block volumes using a variety of storage systems" +msgstr "" + +#: ./doc/training-guides/module003-ch002-features-benifits.xml:176(emphasis) +msgid "Snapshot and backup API for block volumes" +msgstr "" + +#: ./doc/training-guides/module003-ch002-features-benifits.xml:179(td) +msgid "Data protection and recovery for VM data" +msgstr "" + +#: ./doc/training-guides/module003-ch002-features-benifits.xml:185(emphasis) +msgid "Standalone volume API available" +msgstr "" + +#: ./doc/training-guides/module003-ch002-features-benifits.xml:188(td) +msgid "Separate endpoint and API for integration with other compute systems" +msgstr "" + +#: ./doc/training-guides/module003-ch002-features-benifits.xml:195(emphasis) +msgid "Integration with Compute" +msgstr "" + +#: ./doc/training-guides/module003-ch002-features-benifits.xml:197(td) +msgid "Fully integrated to Compute for attaching block volumes and reporting on usage" +msgstr "" + +#: ./doc/training-guides/card040-cinder.xml:7(title) +msgid "Install Cinder" +msgstr "" + +#: ./doc/training-guides/lab001-control-node.xml:26(emphasis) +msgid "Preparing Ubuntu 13.04/12.04" +msgstr "" + +#: ./doc/training-guides/lab001-control-node.xml:47(emphasis) +msgid "Networking :" +msgstr "" + +#: ./doc/training-guides/lab001-control-node.xml:48(para) +msgid "Configure your network by editing /etc/network/interfaces file" +msgstr "" + +#: ./doc/training-guides/lab001-control-node.xml:50(para) +msgid "Open /etc/network/interfaces and edit file as mentioned:" +msgstr "" + +#: ./doc/training-guides/lab001-control-node.xml:84(para) +msgid "After saving the interfaces file, restart the networking service" +msgstr "" + +#: ./doc/training-guides/lab001-control-node.xml:90(para) +msgid "You should see the expected network interface cards having the required IP Addresses." +msgstr "" + +#: ./doc/training-guides/lab001-control-node.xml:93(emphasis) +msgid "SSH from HOST" +msgstr "" + +#: ./doc/training-guides/lab001-control-node.xml:96(para) +msgid "Create a SSH key pair for your Control Node. Follow the same steps as you did in the starting section of the article for your host machine." +msgstr "" + +#: ./doc/training-guides/lab001-control-node.xml:99(para) +msgid "To SSH into Control Node from the Host Machine type the below command." +msgstr "" + +#: ./doc/training-guides/lab001-control-node.xml:106(para) +msgid "Now you can have access to your host clipboard." +msgstr "" + +#: ./doc/training-guides/lab001-control-node.xml:109(emphasis) +msgid "My SQL" +msgstr "" + +#: ./doc/training-guides/lab001-control-node.xml:112(para) +msgid "Install MySQL:" +msgstr "" + +#: ./doc/training-guides/lab001-control-node.xml:118(para) +msgid "Configure mysql to accept all incoming requests:" +msgstr "" + +#: ./doc/training-guides/lab001-control-node.xml:128(para) +msgid "Install RabbitMQ:" +msgstr "" + +#: ./doc/training-guides/lab001-control-node.xml:134(para) +msgid "Install NTP service:" +msgstr "" + +#: ./doc/training-guides/lab001-control-node.xml:140(para) +msgid "Create these databases:" +msgstr "" + +#: ./doc/training-guides/lab001-control-node.xml:157(emphasis) +msgid "Other" +msgstr "" + +#: ./doc/training-guides/lab001-control-node.xml:160(para) +msgid "Install other services:" +msgstr "" + +#: ./doc/training-guides/lab001-control-node.xml:166(para) +msgid "Enable IP_Forwarding:" +msgstr "" + +#: ./doc/training-guides/lab001-control-node.xml:172(para) +msgid "Also add the following two lines into/etc/sysctl.conf:" +msgstr "" + +#: ./doc/training-guides/lab001-control-node.xml:179(para) +msgid "To save you from reboot, perform the following" +msgstr "" + +#: ./doc/training-guides/lab001-control-node.xml:188(emphasis) +msgid "Keystone" +msgstr "" + +#: ./doc/training-guides/lab001-control-node.xml:189(para) +msgid "Keystone is an OpenStack project that provides Identity, Token, Catalog and Policy services for use specifically by projects in the OpenStack family.It implements OpenStack’s Identity API." +msgstr "" + +#: ./doc/training-guides/lab001-control-node.xml:192(para) +msgid "Install Keystone packages:" +msgstr "" + +#: ./doc/training-guides/lab001-control-node.xml:198(para) +msgid "Adapt the connection attribute in the /etc/keystone/keystone.conf to the new database:" +msgstr "" + +#: ./doc/training-guides/lab001-control-node.xml:204(para) +msgid "Restart the identity service then synchronize the database:" +msgstr "" + +#: ./doc/training-guides/lab001-control-node.xml:211(para) +msgid "Fill up the keystone database using the below two scripts:" +msgstr "" + +#: ./doc/training-guides/lab001-control-node.xml:213(filename) +msgid "keystone_basic.sh" +msgstr "" + +#: ./doc/training-guides/lab001-control-node.xml:214(filename) +msgid "keystone_endpoints_basic.sh" +msgstr "" + +#: ./doc/training-guides/lab001-control-node.xml:218(para) +msgid "Run Scripts:" +msgstr "" + +#: ./doc/training-guides/lab001-control-node.xml:227(para) +msgid "Create a simple credentials file" +msgstr "" + +#: ./doc/training-guides/lab001-control-node.xml:233(para) +msgid "Paste the following:" +msgstr "" + +#: ./doc/training-guides/lab001-control-node.xml:242(para) +msgid "Load the above credentials:" +msgstr "" + +#: ./doc/training-guides/lab001-control-node.xml:248(para) +msgid "To test Keystone, we use a simple CLI command:" +msgstr "" + +#: ./doc/training-guides/lab001-control-node.xml:254(emphasis) +msgid "Glance" +msgstr "" + +#: ./doc/training-guides/lab001-control-node.xml:255(para) +msgid "OpenStack Glance project provides services for discovering, registering, and retrieving virtual machine images. Glance has a RESTful API that allows querying of VM image metadata as well as retrieval of the actual image." +msgstr "" + +#: ./doc/training-guides/lab001-control-node.xml:257(para) +msgid "VM images made available through Glance can be stored in a variety of locations from simple file systems to object-storage systems like the OpenStack Swift project." +msgstr "" + +#: ./doc/training-guides/lab001-control-node.xml:258(para) +msgid "Glance, as with all OpenStack projects, is written with the following design guidelines in mind:" +msgstr "" + +#: ./doc/training-guides/lab001-control-node.xml:261(para) ./doc/training-guides/lab001-control-node.xml:441(para) ./doc/training-guides/lab001-control-node.xml:566(para) +msgid "Component based architecture: Quickly add new behaviors" +msgstr "" + +#: ./doc/training-guides/lab001-control-node.xml:264(para) ./doc/training-guides/lab001-control-node.xml:444(para) ./doc/training-guides/lab001-control-node.xml:569(para) +msgid "Highly available: Scale to very serious workloads" +msgstr "" + +#: ./doc/training-guides/lab001-control-node.xml:267(para) +msgid "Fault tolerant: Isolated processes avoid cascading failures" +msgstr "" + +#: ./doc/training-guides/lab001-control-node.xml:270(para) ./doc/training-guides/lab001-control-node.xml:450(para) ./doc/training-guides/lab001-control-node.xml:575(para) +msgid "Recoverable: Failures should be easy to diagnose, debug, and rectify" +msgstr "" + +#: ./doc/training-guides/lab001-control-node.xml:273(para) ./doc/training-guides/lab001-control-node.xml:453(para) +msgid "Open standards: Be a reference implementation for a community-driven api" +msgstr "" + +#: ./doc/training-guides/lab001-control-node.xml:277(para) ./doc/training-guides/card127-glance.xml:7(title) +msgid "Install Glance" +msgstr "" + +#: ./doc/training-guides/lab001-control-node.xml:283(para) +msgid "Update /etc/glance/glance-api-paste.ini" +msgstr "" + +#: ./doc/training-guides/lab001-control-node.xml:297(para) +msgid "Update the /etc/glance/glance-registry-paste.ini" +msgstr "" + +#: ./doc/training-guides/lab001-control-node.xml:310(para) +msgid "Update the /etc/glance/glance-api.conf" +msgstr "" + +#: ./doc/training-guides/lab001-control-node.xml:326(para) +msgid "Update the /etc/glance/glance-registry.conf" +msgstr "" + +#: ./doc/training-guides/lab001-control-node.xml:342(para) +msgid "Restart the glance-api and glance-registry services:" +msgstr "" + +#: ./doc/training-guides/lab001-control-node.xml:348(para) +msgid "Synchronize the Glance database:" +msgstr "" + +#: ./doc/training-guides/lab001-control-node.xml:354(para) +msgid "To test Glance, upload the “cirros cloud image” directly from the internet:" +msgstr "" + +#: ./doc/training-guides/lab001-control-node.xml:360(para) +msgid "Check if the image is successfully uploaded:" +msgstr "" + +#: ./doc/training-guides/lab001-control-node.xml:367(para) +msgid "Neutron is an OpenStack project to provide “network connectivity as a service\" between interface devices (e.g., vNICs) managed by other Openstack services (e.g., nova)." +msgstr "" + +#: ./doc/training-guides/lab001-control-node.xml:370(para) +msgid "Install Neutron Server and the OpenVSwitch package collection:" +msgstr "" + +#: ./doc/training-guides/lab001-control-node.xml:376(para) +msgid "Edit the /etc/neutron/plugins/openvswitch/ovs_neutron_plugin.ini:" +msgstr "" + +#: ./doc/training-guides/lab001-control-node.xml:396(para) +msgid "Edit the /etc/neutron/api-paste.ini:" +msgstr "" + +#: ./doc/training-guides/lab001-control-node.xml:411(para) +msgid "Edit the /etc/neutron/neutron.conf:" +msgstr "" + +#: ./doc/training-guides/lab001-control-node.xml:428(para) +msgid "Restart Neutron services:" +msgstr "" + +#: ./doc/training-guides/lab001-control-node.xml:435(para) +msgid "Nova is the project name for OpenStack Compute, a cloud computing fabric controller, the main part of an IaaS system. Individuals and organizations can use Nova to host and manage their own cloud computing systems. Nova originated as a project out of NASA Ames Research Laboratory." +msgstr "" + +#: ./doc/training-guides/lab001-control-node.xml:438(para) +msgid "Nova is written with the following design guidelines in mind" +msgstr "" + +#: ./doc/training-guides/lab001-control-node.xml:447(para) ./doc/training-guides/lab001-control-node.xml:572(para) +msgid "Fault-Tolerant: Isolated processes avoid cascading failures" +msgstr "" + +#: ./doc/training-guides/lab001-control-node.xml:457(para) +msgid "API Compatibility: Nova strives to provide API-compatible with popular systems like Amazon EC2" +msgstr "" + +#: ./doc/training-guides/lab001-control-node.xml:461(para) +msgid "Install nova components:" +msgstr "" + +#: ./doc/training-guides/lab001-control-node.xml:544(para) +msgid "Synchronize your database:" +msgstr "" + +#: ./doc/training-guides/lab001-control-node.xml:550(para) +msgid "Restart nova-* services (all nova services):" +msgstr "" + +#: ./doc/training-guides/lab001-control-node.xml:556(para) +msgid "Check for the smiling faces on nova-* services to confirm your installation::" +msgstr "" + +#: ./doc/training-guides/lab001-control-node.xml:562(emphasis) +msgid "Cinder" +msgstr "" + +#: ./doc/training-guides/lab001-control-node.xml:563(para) +msgid "Cinder is an OpenStack project to provide “block storage as a service”." +msgstr "" + +#: ./doc/training-guides/lab001-control-node.xml:578(para) +msgid "Open Standards: Be a reference implementation for a community-driven api" +msgstr "" + +#: ./doc/training-guides/lab001-control-node.xml:582(para) +msgid "API Compatibility: Cinder strives to provide API-compatible with popular systems like Amazon EC2" +msgstr "" + +#: ./doc/training-guides/lab001-control-node.xml:586(para) +msgid "Install Cinder components:" +msgstr "" + +#: ./doc/training-guides/lab001-control-node.xml:592(para) +msgid "Configure the iscsi services:" +msgstr "" + +#: ./doc/training-guides/lab001-control-node.xml:598(para) +msgid "Restart the services:" +msgstr "" + +#: ./doc/training-guides/lab001-control-node.xml:605(para) +msgid "Edit /etc/cinder/api-paste.ini:" +msgstr "" + +#: ./doc/training-guides/lab001-control-node.xml:622(para) +msgid "Edit /etc/cinder/cinder.conf:" +msgstr "" + +#: ./doc/training-guides/lab001-control-node.xml:640(para) +msgid "Then, synchronize Cinder database:" +msgstr "" + +#: ./doc/training-guides/lab001-control-node.xml:646(para) +msgid "Finally, create a volumegroup and name it cinder-volumes:" +msgstr "" + +#: ./doc/training-guides/lab001-control-node.xml:660(para) +msgid "Proceed to create the physical volume then the volume group:" +msgstr "" + +#: ./doc/training-guides/lab001-control-node.xml:667(para) +msgid "Note: Beware that this volume group gets lost after a system reboot. If you dont want to do this step again ... make sure that you save the machine state and not shut it down." +msgstr "" + +#: ./doc/training-guides/lab001-control-node.xml:670(para) +msgid "Restart the Cinder services:" +msgstr "" + +#: ./doc/training-guides/lab001-control-node.xml:676(para) +msgid "Verify if Cinder services are running:" +msgstr "" + +#: ./doc/training-guides/lab001-control-node.xml:682(emphasis) +msgid "Horizon" +msgstr "" + +#: ./doc/training-guides/lab001-control-node.xml:683(para) +msgid "Horizon is the canonical implementation of Openstack’s Dashboard, which provides a web based user interface to OpenStack services including Nova, Swift, Keystone, etc." +msgstr "" + +#: ./doc/training-guides/lab001-control-node.xml:686(para) +msgid "To install Horizon, proceed like this" +msgstr "" + +#: ./doc/training-guides/lab001-control-node.xml:692(para) +msgid "If you don't like the OpenStack Ubuntu Theme, you can remove it with help of the below command:" +msgstr "" + +#: ./doc/training-guides/lab001-control-node.xml:698(para) +msgid "Reload Apache and memcached:" +msgstr "" + +#: ./doc/training-guides/card046-L3_Configuration_in_the_Network_Node.xml:7(title) +msgid "L3 Configuration in the Network Node" +msgstr "" + +#: ./doc/training-guides/bk000-preface.xml:6(title) +msgid "Start Here" +msgstr "" + +#: ./doc/training-guides/bk000-preface.xml:8(title) +msgid "Preface" +msgstr "" + +#: ./doc/training-guides/bk000-preface.xml:13(title) +msgid "OpenStack Training Guides Are Under Construction" +msgstr "" + +#: ./doc/training-guides/bk000-preface.xml:14(para) +msgid "We need your help! This is a community driven project to provide the user group community access to OpenStack training materials. We cannot make this work without your help." +msgstr "" + +#: ./doc/training-guides/bk000-preface.xml:16(para) +msgid "There are a few ways to get involved. The easiest way is to use the training guides. Look at the end of each section and you will see the Submit a Bug link. When you find something that can be improved or fixed, submit a bug by clicking on the link." +msgstr "" + +#: ./doc/training-guides/bk000-preface.xml:19(para) +msgid "If you want to get involved with the effort around OpenStack community training, read on, here are the options:" +msgstr "" + +#: ./doc/training-guides/bk000-preface.xml:24(title) +msgid "Attending a user group using the training materials" +msgstr "" + +#: ./doc/training-guides/bk000-preface.xml:25(para) +msgid "The OpenStack community training started at the SFBay OpenStack User Group. More information on this user group and others using the training guides on the OpenStack User Groups page." +msgstr "" + +#: ./doc/training-guides/bk000-preface.xml:32(title) +msgid "Teach / Lead a user group using the training materials" +msgstr "" + +#: ./doc/training-guides/bk000-preface.xml:33(para) +msgid "Awesome! Your experience will not only give you more experience with OpenStack, but you will help some people find new jobs. We have put all the information about How To Run An OpenStack Hackathon here." +msgstr "" + +#: ./doc/training-guides/bk000-preface.xml:40(title) +msgid "Help create the training pages" +msgstr "" + +#: ./doc/training-guides/bk000-preface.xml:44(para) +msgid "We are currently working on creating the Associate Training Guide. It is the first of four training guides. We are using the Install Guide, Administration Guides, Developer Documentation, and Aptira supplied content as the sources for most of the Associate Training Guide. The basic idea is that we use XML include statements to actually use the source content to create new pages. We aim to use as much of the material as possible from existing documentation. By doing this we reuse and improve the existing docs. The topics in the Associate Training Guide are in a bunch of KanBan story board cards. Each card in the story board represents something that an Associate trainee needs to learn. But first things first, you need to get some basic tools and accounts installed and configured before you can really start." +msgstr "" + +#: ./doc/training-guides/bk000-preface.xml:57(para) +msgid "Getting Accounts and Tools: We can't do this without operators and developers using and creating the content. Anyone can contribute content. You will need the tools to get started. Go to the Getting Tools and Accounts page." +msgstr "" + +#: ./doc/training-guides/bk000-preface.xml:64(para) +msgid "Pick a Card: Once you have your tools ready to go, you can assign some work to yourself. Go to the Training Trello/KanBan storyboard and assign a card / user story from the Sprint Backlog to yourself. If you do not have a Trello account, no problem, just create one. Email seanrob@yahoo-inc.com and you will have access." +msgstr "" + +#: ./doc/training-guides/bk000-preface.xml:72(para) +msgid "Create the Content: Each card / user story from the KanBan story board will be a separate chunk of content that you will add to the openstack-manuals repository openstack-training sub-project. More details on creating training content here." +msgstr "" + +#: ./doc/training-guides/bk000-preface.xml:82(para) +msgid "Here are more details on committing changes to OpenStack fixing a documentation bug , OpenStack Gerrit Workflow, OpenStack Documentation HowTo and , Git Documentation" +msgstr "" + +#: ./doc/training-guides/bk000-preface.xml:91(para) +msgid "More details on the OpenStack Training project." +msgstr "" + +#: ./doc/training-guides/bk000-preface.xml:95(para) +msgid "OpenStack Training Wiki (describes the project in detail)" +msgstr "" + +#: ./doc/training-guides/bk000-preface.xml:99(para) +msgid "OpenStack Training blueprint(this is the key project page)" +msgstr "" + +#: ./doc/training-guides/bk000-preface.xml:104(para) +msgid "Bi-Weekly SFBay Hackathon meetup page(we discuss project details with all team members)" +msgstr "" + +#: ./doc/training-guides/bk000-preface.xml:108(para) +msgid "Bi-Weekly SFBay Hackathon Etherpad(meetup notes)" +msgstr "" + +#: ./doc/training-guides/bk000-preface.xml:112(para) +msgid "Core Training Weekly Meeting Agenda(we review project action items here)" +msgstr "" + +#: ./doc/training-guides/bk000-preface.xml:116(para) +msgid "Training Trello/KanBan storyboard(we develop high level project action items here)" +msgstr "" + +#: ./doc/training-guides/bk000-preface.xml:123(link) +msgid "Submit a bug. Enter the summary as \"Training, \" with a few words. Be descriptive as possible in the description field. Open the tag pull-down and enter training-manuals." +msgstr "" + +#: ./doc/training-guides/bk000-preface.xml:127(title) +msgid "Building the Training Cluster" +msgstr "" + +#: ./doc/training-guides/bk000-preface.xml:130(title) +msgid "Important Terms" +msgstr "" + +#: ./doc/training-guides/bk000-preface.xml:144(title) +msgid "Building the Training Cluster, Manually" +msgstr "" + +#: ./doc/training-guides/lab000-openstack-training-labs.xml:5(title) +msgid "OpenStack Training Labs" +msgstr "" + +#: ./doc/training-guides/card026-network-node-architecture.xml:7(title) +msgid "Network Node Overview" +msgstr "" + +#: ./doc/training-guides/bk001-ch001-associate-getting-started.xml:8(title) +msgid "Day 1, 09:00 to 11:00" +msgstr "" + +#: ./doc/training-guides/bk001-ch001-associate-getting-started.xml:13(para) +msgid "Training will take 1 month self paced, (2) 2 week periods with a user group meeting, or 16 hours instructor led." +msgstr "" + +#: ./doc/training-guides/bk001-ch001-associate-getting-started.xml:17(para) +msgid "Working knowledge of Linux CLI, basic Linux SysAdmin skills (directory structure, vi, ssh, installing software)" +msgstr "" + +#: ./doc/training-guides/bk001-ch001-associate-getting-started.xml:19(para) +msgid "Basic networking knowledge (Ethernet, VLAN, IP addressing)" +msgstr "" + +#: ./doc/training-guides/bk001-ch001-associate-getting-started.xml:20(para) +msgid "Laptop with VirtualBox installed (highly recommended)" +msgstr "" + +#: ./doc/training-guides/bk001-ch001-associate-getting-started.xml:24(title) +msgid "Introduction Text" +msgstr "" + +#: ./doc/training-guides/bk001-ch001-associate-getting-started.xml:31(title) ./doc/training-guides/module001-ch002-brief-overview.xml:7(title) +msgid "Brief Overview" +msgstr "" + +#: ./doc/training-guides/bk001-ch001-associate-getting-started.xml:38(title) +msgid "Core Projects" +msgstr "" + +#: ./doc/training-guides/bk001-ch001-associate-getting-started.xml:52(title) +msgid "Virtual Machine Provisioning Walk-Through" +msgstr "" + +#: ./doc/training-guides/card044-install-and-configure-neutron-network-node.xml:7(title) +msgid "Neutron Installation and Configuration in Network node" +msgstr "" + +#: ./doc/training-guides/card073-control-state-instance.xml:7(title) ./doc/training-guides/card073-control-state-instance.xml:8(emphasis) +msgid "Controlling instance state" +msgstr "" + +#: ./doc/training-guides/bk001-ch005-associate-compute-node.xml:10(title) +msgid "Day 1, 15:00 to 17:00" +msgstr "" + +#: ./doc/training-guides/bk001-ch005-associate-compute-node.xml:37(title) +msgid "Block Storage CLI Commands" +msgstr "" + +#: ./doc/training-guides/bk001-ch005-associate-compute-node.xml:44(title) +msgid "Block Storage Manage Volumes" +msgstr "" + +#: ./doc/training-guides/bk001-ch005-associate-compute-node.xml:51(title) +msgid "Compute CLI Commands" +msgstr "" + +#: ./doc/training-guides/bk001-ch005-associate-compute-node.xml:58(title) +msgid "Compute Image creation" +msgstr "" + +#: ./doc/training-guides/bk001-ch005-associate-compute-node.xml:65(title) +msgid "Compute Boot Instance" +msgstr "" + +#: ./doc/training-guides/bk001-ch005-associate-compute-node.xml:72(title) +msgid "Compute Terminate Instance" +msgstr "" + +#: ./doc/training-guides/bk002-ch005-operator-controller-node-lab.xml:6(title) +msgid "Controller Node Lab" +msgstr "" + +#: ./doc/training-guides/bk002-ch005-operator-controller-node-lab.xml:8(title) +msgid "Days 2 to 4, 13:30 to 14:45, 15:00 to 17:00" +msgstr "" + +#: ./doc/training-guides/card128-swift.xml:7(title) +msgid "Install Swift" +msgstr "" + +#. When image changes, this message will be marked fuzzy or untranslated for you. +#. It doesn't matter what you translate it to: it's not used at all. +#: ./doc/training-guides/module001-ch002-brief-overview.xml:54(None) +msgid "@@image: 'figures/image23.jpg'; md5=6b259da45f404aa65ac2388e600f30b3" +msgstr "" + +#: ./doc/training-guides/module001-ch002-brief-overview.xml:8(para) +msgid "OpenStack is a cloud operating system that controls large pools of compute, storage, and networking resources throughout a datacenter. It is all managed through a dashboard that gives administrators control while empowering their users to provision resources through a web interface." +msgstr "" + +#: ./doc/training-guides/module001-ch002-brief-overview.xml:13(para) +msgid "OpenStack is a global collaboration of developers and cloud computing technologists producing the ubiquitous open source cloud computing platform for public and private clouds. The project aims to deliver solutions for all types of clouds by being" +msgstr "" + +#: ./doc/training-guides/module001-ch002-brief-overview.xml:19(para) +msgid "simple to implement" +msgstr "" + +#: ./doc/training-guides/module001-ch002-brief-overview.xml:22(para) +msgid "massively scalable" +msgstr "" + +#: ./doc/training-guides/module001-ch002-brief-overview.xml:25(para) +msgid "feature rich." +msgstr "" + +#: ./doc/training-guides/module001-ch002-brief-overview.xml:28(para) +msgid "To check out more information on OpenStack visit http://goo.gl/Ye9DFT" +msgstr "" + +#: ./doc/training-guides/module001-ch002-brief-overview.xml:31(guilabel) +msgid "OpenStack Foundation:" +msgstr "" + +#: ./doc/training-guides/module001-ch002-brief-overview.xml:32(para) +msgid "The OpenStack Foundation, established September 2012, is an independent body providing shared resources to help achieve the OpenStack Mission by protecting, empowering, and promoting OpenStack software and the community around it. This includes users, developers and the entire ecosystem. For more information visit http://goo.gl/3uvmNX." +msgstr "" + +#: ./doc/training-guides/module001-ch002-brief-overview.xml:38(guilabel) +msgid "Who's behind OpenStack?" +msgstr "" + +#: ./doc/training-guides/module001-ch002-brief-overview.xml:39(para) +msgid "Founded by Rackspace Hosting and NASA, OpenStack has grown to be a global software community of developers collaborating on a standard and massively scalable open source cloud operating system. The OpenStack Foundation promotes the development, distribution and adoption of the OpenStack cloud operating system. As the independent home for OpenStack, the Foundation has already attracted more than 7,000 individual members from 100 countries and 850 different organizations. It has also secured more than $10 million in funding and is ready to fulfill the OpenStack mission of becoming the ubiquitous cloud computing platform. Checkout http://goo.gl/BZHJKdfor more on the same." +msgstr "" + +#: ./doc/training-guides/module001-ch002-brief-overview.xml:51(title) +msgid "Nebula (NASA)" +msgstr "" + +#: ./doc/training-guides/module001-ch002-brief-overview.xml:58(para) +msgid "The goal of the OpenStack Foundation is to serve developers, users, and the entire ecosystem by providing a set of shared resources to grow the footprint of public and private OpenStack clouds, enable technology vendors targeting the platform and assist developers in producing the best cloud software in the industry." +msgstr "" + +#: ./doc/training-guides/module001-ch002-brief-overview.xml:64(guilabel) +msgid "Who uses OpenStack?" +msgstr "" + +#: ./doc/training-guides/module001-ch002-brief-overview.xml:65(para) +msgid "Corporations, service providers, VARS, SMBs, researchers, and global data centers looking to deploy large-scale cloud deployments for private or public clouds leveraging the support and resulting technology of a global open source community. This is just three years into OpenStack, it's new, it's yet to mature and has immense possibilities. How do I say that? All these ‘buzz words’ will fall into a properly solved jigsaw puzzle as you go through this article." +msgstr "" + +#: ./doc/training-guides/module001-ch002-brief-overview.xml:73(guilabel) +msgid "It's Open Source:" +msgstr "" + +#: ./doc/training-guides/module001-ch002-brief-overview.xml:74(para) +msgid "All of the code for OpenStack is freely available under the Apache 2.0 license. Anyone can run it, build on it, or submit changes back to the project. This open development model is one of the best ways to foster badly-needed cloud standards, remove the fear of proprietary lock-in for cloud customers, and create a large ecosystem that spans cloud providers." +msgstr "" + +#: ./doc/training-guides/module001-ch002-brief-overview.xml:80(guilabel) +msgid "Who it's for:" +msgstr "" + +#: ./doc/training-guides/module001-ch002-brief-overview.xml:81(para) +msgid "Enterprises, service providers, government and academic institutions with physical hardware that would like to build a public or private cloud." +msgstr "" + +#: ./doc/training-guides/module001-ch002-brief-overview.xml:84(guilabel) +msgid "How it's being used today:" +msgstr "" + +#: ./doc/training-guides/module001-ch002-brief-overview.xml:85(para) +msgid "Organizations like CERN, Cisco WebEx, DreamHost, eBay, The Gap, HP, MercadoLibre, NASA, PayPal, Rackspace and University of Melbourne have deployed OpenStack clouds to achieve control, business agility and cost savings without the licensing fees and terms of proprietary software. For complete user stories visit http://goo.gl/aF4lsL, this should give you a good idea about the importance of OpenStack." +msgstr "" + +#: ./doc/training-guides/bk002-operator-training-guide.xml:5(title) +msgid "Operator Training Guide" +msgstr "" + +#: ./doc/training-guides/bk002-ch008-operator-compute-node-lab.xml:6(title) +msgid "Compute Node Lab" +msgstr "" + +#: ./doc/training-guides/bk002-ch008-operator-compute-node-lab.xml:8(title) +msgid "Days 5 to 6, 13:30 to 14:45, 15:00 to 17:00" +msgstr "" + +#: ./doc/training-guides/module002-ch004-security-in-neutron.xml:7(title) +msgid "Security in Neutron" +msgstr "" + +#: ./doc/training-guides/module002-ch004-security-in-neutron.xml:8(guilabel) +msgid "Security Groups" +msgstr "" + +#: ./doc/training-guides/module002-ch004-security-in-neutron.xml:9(para) +msgid "Security groups and security group rules allows administrators and tenants the ability to specify the type of traffic and direction (ingress/egress) that is allowed to pass through a port. A security group is a container for security group rules." +msgstr "" + +#: ./doc/training-guides/module002-ch004-security-in-neutron.xml:14(para) +msgid "When a port is created in OpenStack Networking it is associated with a security group. If a security group is not specified the port will be associated with a 'default' security group. By default this group will drop all ingress traffic and allow all egress. Rules can be added to this group in order to change the behaviour." +msgstr "" + +#: ./doc/training-guides/module002-ch004-security-in-neutron.xml:20(para) +msgid "If one desires to use the OpenStack Compute security group APIs and/or have OpenStack Compute orchestrate the creation of new ports for instances on specific security groups, additional configuration is needed. To enable this, one must configure the following file /etc/nova/nova.conf and set the config option security_group_api=neutron on every node running nova-compute and nova-api. After this change is made restart nova-api and nova-compute in order to pick up this change. After this change is made one will be able to use both the OpenStack Compute and OpenStack Network security group API at the same time." +msgstr "" + +#: ./doc/training-guides/module002-ch004-security-in-neutron.xml:32(guilabel) +msgid "Authentication and Authorization" +msgstr "" + +#: ./doc/training-guides/module002-ch004-security-in-neutron.xml:33(para) +msgid "OpenStack Networking uses the OpenStack Identity service (project name keystone) as the default authentication service. When OpenStack Identity is enabled Users submitting requests to the OpenStack Networking service must provide an authentication token in X-Auth-Token request header. The aforementioned token should have been obtained by authenticating with the OpenStack Identity endpoint. For more information concerning authentication with OpenStack Identity, please refer to the OpenStack Identity documentation. When OpenStack Identity is enabled, it is not mandatory to specify tenant_id for resources in create requests, as the tenant identifier will be derived from the Authentication token. Please note that the default authorization settings only allow administrative users to create resources on behalf of a different tenant. OpenStack Networking uses information received from OpenStack Identity to authorize user requests. OpenStack Networking handles two kind of authorization policies:" +msgstr "" + +#: ./doc/training-guides/module002-ch004-security-in-neutron.xml:54(para) +msgid "Operation-based: policies specify access criteria for specific operations, possibly with fine-grained control over specific attributes;" +msgstr "" + +#: ./doc/training-guides/module002-ch004-security-in-neutron.xml:60(para) +msgid "Resource-based:whether access to specific resource might be granted or not according to the permissions configured for the resource (currently available only for the network resource). The actual authorization policies enforced in OpenStack Networking might vary from deployment to deployment." +msgstr "" + +#: ./doc/training-guides/module002-ch004-security-in-neutron.xml:70(para) +msgid "The policy engine reads entries from the policy.json file. The actual location of this file might vary from distribution to distribution. Entries can be updated while the system is running, and no service restart is required. That is to say, every time the policy file is updated, the policies will be automatically reloaded. Currently the only way of updating such policies is to edit the policy file. Please note that in this section we will use both the terms \"policy\" and \"rule\" to refer to objects which are specified in the same way in the policy file; in other words, there are no syntax differences between a rule and a policy. We will define a policy something which is matched directly from the OpenStack Networking policy engine, whereas we will define a rule as the elements of such policies which are then evaluated. For instance in create_subnet: [[\"admin_or_network_owner\"]], create_subnet is regarded as a policy, whereas admin_or_network_owner is regarded as a rule." +msgstr "" + +#: ./doc/training-guides/module002-ch004-security-in-neutron.xml:88(para) +msgid "Policies are triggered by the OpenStack Networking policy engine whenever one of them matches an OpenStack Networking API operation or a specific attribute being used in a given operation. For instance the create_subnet policy is triggered every time a POST /v2.0/subnets request is sent to the OpenStack Networking server; on the other hand create_network:shared is triggered every time the shared attribute is explicitly specified (and set to a value different from its default) in a POST /v2.0/networks request. It is also worth mentioning that policies can be also related to specific API extensions; for instance extension:provider_network:set will be triggered if the attributes defined by the Provider Network extensions are specified in an API request." +msgstr "" + +#: ./doc/training-guides/module002-ch004-security-in-neutron.xml:102(para) +msgid "An authorization policy can be composed by one or more rules. If more rules are specified, evaluation policy will be successful if any of the rules evaluates successfully; if an API operation matches multiple policies, then all the policies must evaluate successfully. Also, authorization rules are recursive. Once a rule is matched, the rule(s) can be resolved to another rule, until a terminal rule is reached." +msgstr "" + +#: ./doc/training-guides/module002-ch004-security-in-neutron.xml:110(para) +msgid "The OpenStack Networking policy engine currently defines the following kinds of terminal rules:" +msgstr "" + +#: ./doc/training-guides/module002-ch004-security-in-neutron.xml:114(para) +msgid "Role-based rules: evaluate successfully if the user submitting the request has the specified role. For instance \"role:admin\"is successful if the user submitting the request is an administrator." +msgstr "" + +#: ./doc/training-guides/module002-ch004-security-in-neutron.xml:121(para) +msgid "Field-based rules: evaluate successfully if a field of the resource specified in the current request matches a specific value. For instance \"field:networks:shared=True\" is successful if the attribute shared of the network resource is set to true." +msgstr "" + +#: ./doc/training-guides/module002-ch004-security-in-neutron.xml:130(para) +msgid "Generic rules:compare an attribute in the resource with an attribute extracted from the user's security credentials and evaluates successfully if the comparison is successful. For instance \"tenant_id:%(tenant_id)s\" is successful if the tenant identifier in the resource is equal to the tenant identifier of the user submitting the request." +msgstr "" + +#: ./doc/training-guides/module003-ch009-replication.xml:8(para) +msgid "Because each replica in swift functions independently, and clients generally require only a simple majority of nodes responding to consider an operation successful, transient failures like network partitions can quickly cause replicas to diverge. These differences are eventually reconciled by asynchronous, peer-to-peer replicator processes. The replicator processes traverse their local filesystems, concurrently performing operations in a manner that balances load across physical disks." +msgstr "" + +#: ./doc/training-guides/module003-ch009-replication.xml:17(para) +msgid "Replication uses a push model, with records and files generally only being copied from local to remote replicas. This is important because data on the node may not belong there (as in the case of handoffs and ring changes), and a replicator can’t know what data exists elsewhere in the cluster that it should pull in. It’s the duty of any node that contains data to ensure that data gets to where it belongs. Replica placement is handled by the ring." +msgstr "" + +#: ./doc/training-guides/module003-ch009-replication.xml:25(para) +msgid "Every deleted record or file in the system is marked by a tombstone, so that deletions can be replicated alongside creations. The replication process cleans up tombstones after a time period known as the consistency window. The consistency window encompasses replication duration and how long transient failure can remove a node from the cluster. Tombstone cleanup must be tied to replication to reach replica convergence." +msgstr "" + +#: ./doc/training-guides/module003-ch009-replication.xml:33(para) +msgid "If a replicator detects that a remote drive has failed, the replicator uses the get_more_nodes interface for the ring to choose an alternate node with which to synchronize. The replicator can maintain desired levels of replication in the face of disk failures, though some replicas may not be in an immediately usable location. Note that the replicator doesn’t maintain desired levels of replication when other failures, such as entire node failures occur, because most failure are transient." +msgstr "" + +#: ./doc/training-guides/module003-ch009-replication.xml:42(para) +msgid "Replication is an area of active development, and likely rife with potential improvements to speed and accuracy." +msgstr "" + +#: ./doc/training-guides/module003-ch009-replication.xml:45(para) +msgid "There are two major classes of replicator - the db replicator, which replicates accounts and containers, and the object replicator, which replicates object data." +msgstr "" + +#: ./doc/training-guides/module003-ch009-replication.xml:48(guilabel) +msgid "DB Replication" +msgstr "" + +#: ./doc/training-guides/module003-ch009-replication.xml:49(para) +msgid "The first step performed by db replication is a low-cost hash comparison to determine whether two replicas already match. Under normal operation, this check is able to verify that most databases in the system are already synchronized very quickly. If the hashes differ, the replicator brings the databases in sync by sharing records added since the last sync point." +msgstr "" + +#: ./doc/training-guides/module003-ch009-replication.xml:56(para) +msgid "This sync point is a high water mark noting the last record at which two databases were known to be in sync, and is stored in each database as a tuple of the remote database id and record id. Database ids are unique amongst all replicas of the database, and record ids are monotonically increasing integers. After all new records have been pushed to the remote database, the entire sync table of the local database is pushed, so the remote database can guarantee that it is in sync with everything with which the local database has previously synchronized." +msgstr "" + +#: ./doc/training-guides/module003-ch009-replication.xml:67(para) +msgid "If a replica is found to be missing entirely, the whole local database file is transmitted to the peer using rsync(1) and vested with a new unique id." +msgstr "" + +#: ./doc/training-guides/module003-ch009-replication.xml:70(para) +msgid "In practice, DB replication can process hundreds of databases per concurrency setting per second (up to the number of available CPUs or disks) and is bound by the number of DB transactions that must be performed." +msgstr "" + +#: ./doc/training-guides/module003-ch009-replication.xml:74(guilabel) +msgid "Object Replication" +msgstr "" + +#: ./doc/training-guides/module003-ch009-replication.xml:75(para) +msgid "The initial implementation of object replication simply performed an rsync to push data from a local partition to all remote servers it was expected to exist on. While this performed adequately at small scale, replication times skyrocketed once directory structures could no longer be held in RAM. We now use a modification of this scheme in which a hash of the contents for each suffix directory is saved to a per-partition hashes file. The hash for a suffix directory is invalidated when the contents of that suffix directory are modified." +msgstr "" + +#: ./doc/training-guides/module003-ch009-replication.xml:85(para) +msgid "The object replication process reads in these hash files, calculating any invalidated hashes. It then transmits the hashes to each remote server that should hold the partition, and only suffix directories with differing hashes on the remote server are rsynced. After pushing files to the remote server, the replication process notifies it to recalculate hashes for the rsynced suffix directories." +msgstr "" + +#: ./doc/training-guides/module003-ch009-replication.xml:93(para) +msgid "Performance of object replication is generally bound by the number of uncached directories it has to traverse, usually as a result of invalidated suffix directory hashes. Using write volume and partition counts from our running systems, it was designed so that around 2% of the hash space on a normal node will be invalidated per day, which has experimentally given us acceptable replication speeds." +msgstr "" + +#: ./doc/training-guides/bk003-developer-training-guide.xml:5(title) +msgid "Developer Training Guide" +msgstr "" + +#: ./doc/training-guides/bk003-developer-training-guide.xml:8(title) +msgid "Developer Training Guide Coming Soon" +msgstr "" + +#: ./doc/training-guides/bk003-developer-training-guide.xml:10(title) +msgid "Cinder Architecture" +msgstr "" + +#: ./doc/training-guides/bk003-developer-training-guide.xml:17(title) +msgid "Cinder Architecture Components" +msgstr "" + +#: ./doc/training-guides/bk003-developer-training-guide.xml:24(title) +msgid "Adding an API Method" +msgstr "" + +#: ./doc/training-guides/bk003-developer-training-guide.xml:31(title) +msgid "Controllers" +msgstr "" + +#: ./doc/training-guides/bk003-developer-training-guide.xml:38(title) ./doc/training-guides/sources/cinder/addmethod.openstackapi.xml:53(title) +msgid "Serialization" +msgstr "" + +#: ./doc/training-guides/bk003-developer-training-guide.xml:45(title) +msgid "Development Environment" +msgstr "" + +#: ./doc/training-guides/bk003-developer-training-guide.xml:52(title) ./doc/training-guides/sources/cinder/drivers.xml:7(title) ./doc/training-guides/sources/cinder/drivers.xml:26(title) +msgid "Drivers" +msgstr "" + +#: ./doc/training-guides/bk003-developer-training-guide.xml:59(title) ./doc/training-guides/sources/cinder/threading.xml:7(title) +msgid "Threading" +msgstr "" + +#: ./doc/training-guides/bk003-developer-training-guide.xml:66(title) +msgid "Unit Tests" +msgstr "" + +#: ./doc/training-guides/card011.xml:7(title) +msgid "Installing MySQL" +msgstr "" + +#: ./doc/training-guides/bk001-bk010-associate-object-storage-node-quiz.xml:7(title) +msgid "Day 2, 14:25 to 14:45" +msgstr "" + +#: ./doc/training-guides/lab004-openstack-production.xml:7(title) +msgid "OpenStack In Production" +msgstr "" + +#: ./doc/training-guides/lab004-openstack-production.xml:8(para) +msgid "More Content To be Added." +msgstr "" + +#: ./doc/training-guides/bk002-ch012-operator-network-node-quiz.xml:6(title) ./doc/training-guides/bk001-ch008-associate-network-node-quiz.xml:6(title) +msgid "Network Node Quiz" +msgstr "" + +#: ./doc/training-guides/bk002-ch012-operator-network-node-quiz.xml:8(title) +msgid "Days 7 to 8, 16:40 to 17:00" +msgstr "" + +#. When image changes, this message will be marked fuzzy or untranslated for you. +#. It doesn't matter what you translate it to: it's not used at all. +#: ./doc/training-guides/lab000-virtualbox-basics.xml:207(None) +msgid "@@image: 'figures/lab000-virtual-box/image13.png'; md5=eeaf2e523b991a592182c76fcfc29e07" +msgstr "" + +#. When image changes, this message will be marked fuzzy or untranslated for you. +#. It doesn't matter what you translate it to: it's not used at all. +#: ./doc/training-guides/lab000-virtualbox-basics.xml:251(None) +msgid "@@image: 'figures/lab000-virtual-box/image19.png'; md5=9a3c62ffc47b83ab5306820bd3a9a4fc" +msgstr "" + +#. When image changes, this message will be marked fuzzy or untranslated for you. +#. It doesn't matter what you translate it to: it's not used at all. +#: ./doc/training-guides/lab000-virtualbox-basics.xml:286(None) +msgid "@@image: 'figures/lab000-virtual-box/image16.png'; md5=bb1f3c80211fafd0ce737725ca39a6b3" +msgstr "" + +#. When image changes, this message will be marked fuzzy or untranslated for you. +#. It doesn't matter what you translate it to: it's not used at all. +#: ./doc/training-guides/lab000-virtualbox-basics.xml:320(None) +msgid "@@image: 'figures/lab000-virtual-box/image08.png'; md5=e52887e98a60caa87affd91d78ff6a4f" +msgstr "" + +#. When image changes, this message will be marked fuzzy or untranslated for you. +#. It doesn't matter what you translate it to: it's not used at all. +#: ./doc/training-guides/lab000-virtualbox-basics.xml:369(None) +msgid "@@image: 'figures/lab000-virtual-box/image11.png'; md5=f0799ccd13811e991932b79655efe63b" +msgstr "" + +#. When image changes, this message will be marked fuzzy or untranslated for you. +#. It doesn't matter what you translate it to: it's not used at all. +#: ./doc/training-guides/lab000-virtualbox-basics.xml:409(None) +msgid "@@image: 'figures/lab000-virtual-box/image07.png'; md5=dc8a7ca4a721116dad4d808efdcd0158" +msgstr "" + +#. When image changes, this message will be marked fuzzy or untranslated for you. +#. It doesn't matter what you translate it to: it's not used at all. +#: ./doc/training-guides/lab000-virtualbox-basics.xml:418(None) +msgid "@@image: 'figures/lab000-virtual-box/image18.png'; md5=cc6c10310380102b418c665047c0539c" +msgstr "" + +#. When image changes, this message will be marked fuzzy or untranslated for you. +#. It doesn't matter what you translate it to: it's not used at all. +#: ./doc/training-guides/lab000-virtualbox-basics.xml:427(None) +msgid "@@image: 'figures/lab000-virtual-box/image14.png'; md5=469f15068705c1a40cb5504cc2a8e5dd" +msgstr "" + +#. When image changes, this message will be marked fuzzy or untranslated for you. +#. It doesn't matter what you translate it to: it's not used at all. +#: ./doc/training-guides/lab000-virtualbox-basics.xml:446(None) +msgid "@@image: 'figures/lab000-virtual-box/image12.png'; md5=266a767b48f2c3eba60b67e01a1c6cc5" +msgstr "" + +#. When image changes, this message will be marked fuzzy or untranslated for you. +#. It doesn't matter what you translate it to: it's not used at all. +#: ./doc/training-guides/lab000-virtualbox-basics.xml:488(None) +msgid "@@image: 'figures/lab000-virtual-box/image05.png'; md5=c711ea21fcc2b1e18d9d41375bc9a713" +msgstr "" + +#. When image changes, this message will be marked fuzzy or untranslated for you. +#. It doesn't matter what you translate it to: it's not used at all. +#: ./doc/training-guides/lab000-virtualbox-basics.xml:497(None) +msgid "@@image: 'figures/lab000-virtual-box/image17.png'; md5=9077ae7ff15e88187de9941fd8c7db5f" +msgstr "" + +#. When image changes, this message will be marked fuzzy or untranslated for you. +#. It doesn't matter what you translate it to: it's not used at all. +#: ./doc/training-guides/lab000-virtualbox-basics.xml:506(None) +msgid "@@image: 'figures/lab000-virtual-box/image02.png'; md5=001129ba8b8030bbf1ca9e23805d9b84" +msgstr "" + +#. When image changes, this message will be marked fuzzy or untranslated for you. +#. It doesn't matter what you translate it to: it's not used at all. +#: ./doc/training-guides/lab000-virtualbox-basics.xml:515(None) +msgid "@@image: 'figures/lab000-virtual-box/image00.png'; md5=e90be704c41d381dedab6f8fb3b8c391" +msgstr "" + +#. When image changes, this message will be marked fuzzy or untranslated for you. +#. It doesn't matter what you translate it to: it's not used at all. +#: ./doc/training-guides/lab000-virtualbox-basics.xml:533(None) +msgid "@@image: 'figures/lab000-virtual-box/image04.png'; md5=8577d54796c8479a2f089ee09846e130" +msgstr "" + +#. When image changes, this message will be marked fuzzy or untranslated for you. +#. It doesn't matter what you translate it to: it's not used at all. +#: ./doc/training-guides/lab000-virtualbox-basics.xml:570(None) +msgid "@@image: 'figures/lab000-virtual-box/image15.png'; md5=2d2b9eb2d913030490694d3df8c26c20" +msgstr "" + +#. When image changes, this message will be marked fuzzy or untranslated for you. +#. It doesn't matter what you translate it to: it's not used at all. +#: ./doc/training-guides/lab000-virtualbox-basics.xml:579(None) +msgid "@@image: 'figures/lab000-virtual-box/image10.png'; md5=4f06faaf244be263d90b41855b10d62a" +msgstr "" + +#. When image changes, this message will be marked fuzzy or untranslated for you. +#. It doesn't matter what you translate it to: it's not used at all. +#: ./doc/training-guides/lab000-virtualbox-basics.xml:588(None) +msgid "@@image: 'figures/lab000-virtual-box/image01.png'; md5=1eb33f35a0af357f7e96fa03830d49c0" +msgstr "" + +#: ./doc/training-guides/lab000-virtualbox-basics.xml:7(title) +msgid "VirtualBox Basics" +msgstr "" + +#: ./doc/training-guides/lab000-virtualbox-basics.xml:9(para) +msgid "The following are the conventional methods of deploying OpenStack on Virtual Box for the sake of a test/sandbox or just to try out OpenStack on commodity hardware." +msgstr "" + +#: ./doc/training-guides/lab000-virtualbox-basics.xml:12(para) +msgid "1. DevStack" +msgstr "" + +#: ./doc/training-guides/lab000-virtualbox-basics.xml:13(para) +msgid "2. Vagrant" +msgstr "" + +#: ./doc/training-guides/lab000-virtualbox-basics.xml:14(para) +msgid "But DevStack and Vagrant bring in some level of automated deployment as running the scripts will get your VirtualBox Instance configured as the required OpenStack deployment. We will be manually deploying OpenStack on VirtualBox Instance to get better view of how OpenStack works." +msgstr "" + +#: ./doc/training-guides/lab000-virtualbox-basics.xml:19(guilabel) +msgid "Prerequisite:" +msgstr "" + +#: ./doc/training-guides/lab000-virtualbox-basics.xml:20(para) +msgid "Well, its a daunting task to just cover all of OpenStack’s concepts let alone Virtualization and Networking. So some basic idea/knowledge on Virtualization, Networking and Linux is required. Even though I will try to keep the level as low as possible for making it easy for Linux Newbies as well as experts." +msgstr "" + +#: ./doc/training-guides/lab000-virtualbox-basics.xml:26(para) +msgid "These Virtual Machines and Virtual Networks will be given equal privilege as a physical machine on a physical network." +msgstr "" + +#: ./doc/training-guides/lab000-virtualbox-basics.xml:29(para) +msgid "Just for those who would want to do a deeper research or study, for more information you may refer the following links" +msgstr "" + +#: ./doc/training-guides/lab000-virtualbox-basics.xml:32(para) +msgid "OpenStack:OpenStack Official Documentation (docs.openstack.org)" +msgstr "" + +#: ./doc/training-guides/lab000-virtualbox-basics.xml:34(para) +msgid "Networking:Computer Networks (5th Edition) by Andrew S. Tanenbaum" +msgstr "" + +#: ./doc/training-guides/lab000-virtualbox-basics.xml:36(para) +msgid "VirtualBox:Virtual Box Manual (http://www.virtualbox.org/manual/UserManual.html)" +msgstr "" + +#: ./doc/training-guides/lab000-virtualbox-basics.xml:38(emphasis) +msgid "Requirements :" +msgstr "" + +#: ./doc/training-guides/lab000-virtualbox-basics.xml:39(para) +msgid "Operating Systems - I recommend Ubuntu Server 12.04 LTS, Ubuntu Server 13.10 or Debian Wheezy" +msgstr "" + +#: ./doc/training-guides/lab000-virtualbox-basics.xml:41(para) +msgid "Note :Ubuntu 12.10 is not supporting OpenStack Grizzly Packages. Ubuntu team has decided not to package Grizzly Packages for Ubuntu 12.10." +msgstr "" + +#: ./doc/training-guides/lab000-virtualbox-basics.xml:46(para) +msgid "Recommended Requirements." +msgstr "" + +#: ./doc/training-guides/lab000-virtualbox-basics.xml:52(td) +msgid "VT Enabled PC:" +msgstr "" + +#: ./doc/training-guides/lab000-virtualbox-basics.xml:53(td) +msgid "Intel ix or Amd QuadCore" +msgstr "" + +#: ./doc/training-guides/lab000-virtualbox-basics.xml:56(td) +msgid "4GB Ram:" +msgstr "" + +#: ./doc/training-guides/lab000-virtualbox-basics.xml:57(td) ./doc/training-guides/lab000-virtualbox-basics.xml:75(td) +msgid "DDR2/DDR3" +msgstr "" + +#: ./doc/training-guides/lab000-virtualbox-basics.xml:63(para) +msgid "Minimum Requirements." +msgstr "" + +#: ./doc/training-guides/lab000-virtualbox-basics.xml:69(td) +msgid "Non-VT PC's:" +msgstr "" + +#: ./doc/training-guides/lab000-virtualbox-basics.xml:70(td) +msgid "Intel Core 2 Duo or Amd Dual Core" +msgstr "" + +#: ./doc/training-guides/lab000-virtualbox-basics.xml:74(td) +msgid "2GB Ram:" +msgstr "" + +#: ./doc/training-guides/lab000-virtualbox-basics.xml:79(para) +msgid "If you don't know whether your processor is VT enabled, you could check it by installing cpu checker" +msgstr "" + +#: ./doc/training-guides/lab000-virtualbox-basics.xml:84(td) +msgid "$sudo apt-get install cpu-checker" +msgstr "" + +#: ./doc/training-guides/lab000-virtualbox-basics.xml:88(td) +msgid "$sudo kvm-ok" +msgstr "" + +#: ./doc/training-guides/lab000-virtualbox-basics.xml:92(para) +msgid "If your device does not support VT it will show" +msgstr "" + +#: ./doc/training-guides/lab000-virtualbox-basics.xml:93(para) +msgid "INFO:Your CPU does not support KVM extensions" +msgstr "" + +#: ./doc/training-guides/lab000-virtualbox-basics.xml:94(para) +msgid "KVM acceleration can NOT be used" +msgstr "" + +#: ./doc/training-guides/lab000-virtualbox-basics.xml:95(para) +msgid "You will still be able to use Virtual Box but the instances will be very slow." +msgstr "" + +#: ./doc/training-guides/lab000-virtualbox-basics.xml:97(para) +msgid "There are many ways to configure your OpenStack Setup, we will be deploying OpenStack Multi Node using OVS as the Network Plugin and QEMU/ KVM as the hypervisor." +msgstr "" + +#: ./doc/training-guides/lab000-virtualbox-basics.xml:100(emphasis) +msgid "Host Only Connections:" +msgstr "" + +#: ./doc/training-guides/lab000-virtualbox-basics.xml:103(para) +msgid "Host only connections provide an Internal network between your host and the Virtual Machine instances up and running on your host machine.This network is not traceable by other networks." +msgstr "" + +#: ./doc/training-guides/lab000-virtualbox-basics.xml:109(para) +msgid "You may even use Bridged connection if you have a router/switch. I am assuming the worst case (one IP without any router), so that it is simple to get the required networks running without the hassle of IP tables." +msgstr "" + +#: ./doc/training-guides/lab000-virtualbox-basics.xml:115(para) +msgid "The following are the host only connections that you will be setting up later on :" +msgstr "" + +#: ./doc/training-guides/lab000-virtualbox-basics.xml:121(para) +msgid "vboxnet0 - OpenStack Management Network - Host static IP 10.10.10.1" +msgstr "" + +#: ./doc/training-guides/lab000-virtualbox-basics.xml:125(para) +msgid "vboxnet1 - VM Conf.Network - Host Static IP 10.20.20.1" +msgstr "" + +#: ./doc/training-guides/lab000-virtualbox-basics.xml:129(para) +msgid "vboxnet2 - VM External Network Access (Host Machine) 192.168.100.1" +msgstr "" + +#: ./doc/training-guides/lab000-virtualbox-basics.xml:142(para) +msgid "Vboxnet0, Vboxnet1, Vboxnet2 - are virtual networks setup up by virtual box with your host machine. This is the way your host can communicate with the virtual machines. These networks are in turn used by virtual box VM’s for OpenStack networks, so that OpenStack’s services can communicate with each other." +msgstr "" + +#: ./doc/training-guides/lab000-virtualbox-basics.xml:147(guilabel) +msgid "Setup Your VM Environment" +msgstr "" + +#: ./doc/training-guides/lab000-virtualbox-basics.xml:148(para) +msgid "Before you can start configuring your Environment you need to download some of the following stuff:" +msgstr "" + +#: ./doc/training-guides/lab000-virtualbox-basics.xml:153(link) +msgid "Oracle Virtual Box" +msgstr "" + +#: ./doc/training-guides/lab000-virtualbox-basics.xml:157(para) +msgid "Note:You cannot set up a amd64 VM on a x86 machine." +msgstr "" + +#: ./doc/training-guides/lab000-virtualbox-basics.xml:160(link) +msgid "Ubuntu 12.04 Server or Ubuntu 13.04 Server" +msgstr "" + +#: ./doc/training-guides/lab000-virtualbox-basics.xml:164(para) +msgid "Note:You need a x86 image for VM's if kvm-ok fails, even though you are on amd64 machine." +msgstr "" + +#: ./doc/training-guides/lab000-virtualbox-basics.xml:166(para) +msgid "Note: Even Though I'm using Ubuntu as Host, the same is applicable to Windows, Mac and other Linux Hosts." +msgstr "" + +#: ./doc/training-guides/lab000-virtualbox-basics.xml:170(para) +msgid "If you have i5 or i7 2nd gen processor you can have VT technology inside VM's provided by VmWare. This means that your OpenStack nodes(Which are in turn VM's) will give positive result on KVM-OK. (I call it - Nesting of type-2 Hypervisors). Rest of the configurations remain same except for the UI and few other trivial differences." +msgstr "" + +#: ./doc/training-guides/lab000-virtualbox-basics.xml:178(guilabel) +msgid "Configure Virtual Networks" +msgstr "" + +#: ./doc/training-guides/lab000-virtualbox-basics.xml:181(para) +msgid "This section of the guide will help you setup your networks for your Virtual Machine." +msgstr "" + +#: ./doc/training-guides/lab000-virtualbox-basics.xml:185(para) +msgid "Launch Virtual Box" +msgstr "" + +#: ./doc/training-guides/lab000-virtualbox-basics.xml:190(para) +msgid "Click on File>Preferences present on the menu bar of Virtual Box." +msgstr "" + +#: ./doc/training-guides/lab000-virtualbox-basics.xml:195(para) +msgid "Select the Network tab." +msgstr "" + +#: ./doc/training-guides/lab000-virtualbox-basics.xml:199(para) +msgid "On the right side you will see an option to add Host-Only networks." +msgstr "" + +#: ./doc/training-guides/lab000-virtualbox-basics.xml:204(title) +msgid "Create Host Only Networks" +msgstr "" + +#: ./doc/training-guides/lab000-virtualbox-basics.xml:213(para) +msgid "Create three Host-Only Network Connections. As shown above." +msgstr "" + +#: ./doc/training-guides/lab000-virtualbox-basics.xml:217(para) +msgid "Edit the Host-Only Connections to have the following settings." +msgstr "" + +#: ./doc/training-guides/lab000-virtualbox-basics.xml:221(emphasis) ./doc/training-guides/lab000-virtualbox-basics.xml:248(title) ./doc/training-guides/lab000-virtualbox-basics.xml:389(td) ./doc/training-guides/lab000-virtualbox-basics.xml:463(td) ./doc/training-guides/lab000-virtualbox-basics.xml:550(td) +msgid "Vboxnet0" +msgstr "" + +#: ./doc/training-guides/lab000-virtualbox-basics.xml:226(th) ./doc/training-guides/lab000-virtualbox-basics.xml:261(th) ./doc/training-guides/lab000-virtualbox-basics.xml:295(th) +msgid "Option" +msgstr "" + +#: ./doc/training-guides/lab000-virtualbox-basics.xml:227(th) ./doc/training-guides/lab000-virtualbox-basics.xml:262(th) ./doc/training-guides/lab000-virtualbox-basics.xml:296(th) +msgid "Value" +msgstr "" + +#: ./doc/training-guides/lab000-virtualbox-basics.xml:230(td) ./doc/training-guides/lab000-virtualbox-basics.xml:265(td) ./doc/training-guides/lab000-virtualbox-basics.xml:299(td) +msgid "IPv4 Address:" +msgstr "" + +#: ./doc/training-guides/lab000-virtualbox-basics.xml:231(td) +msgid "10.10.10.1" +msgstr "" + +#: ./doc/training-guides/lab000-virtualbox-basics.xml:234(td) ./doc/training-guides/lab000-virtualbox-basics.xml:269(td) ./doc/training-guides/lab000-virtualbox-basics.xml:303(td) +msgid "IPv4 Network Mask:" +msgstr "" + +#: ./doc/training-guides/lab000-virtualbox-basics.xml:235(td) ./doc/training-guides/lab000-virtualbox-basics.xml:270(td) ./doc/training-guides/lab000-virtualbox-basics.xml:304(td) +msgid "255.255.255.0" +msgstr "" + +#: ./doc/training-guides/lab000-virtualbox-basics.xml:238(td) ./doc/training-guides/lab000-virtualbox-basics.xml:273(td) ./doc/training-guides/lab000-virtualbox-basics.xml:307(td) +msgid "IPv6 Address:" +msgstr "" + +#: ./doc/training-guides/lab000-virtualbox-basics.xml:239(td) ./doc/training-guides/lab000-virtualbox-basics.xml:243(td) ./doc/training-guides/lab000-virtualbox-basics.xml:274(td) ./doc/training-guides/lab000-virtualbox-basics.xml:278(td) ./doc/training-guides/lab000-virtualbox-basics.xml:308(td) ./doc/training-guides/lab000-virtualbox-basics.xml:312(td) +msgid "Can be Left Blank" +msgstr "" + +#: ./doc/training-guides/lab000-virtualbox-basics.xml:242(td) ./doc/training-guides/lab000-virtualbox-basics.xml:277(td) ./doc/training-guides/lab000-virtualbox-basics.xml:311(td) +msgid "IPv6 Network Mask Length :" +msgstr "" + +#: ./doc/training-guides/lab000-virtualbox-basics.xml:255(emphasis) ./doc/training-guides/lab000-virtualbox-basics.xml:283(title) ./doc/training-guides/lab000-virtualbox-basics.xml:468(td) ./doc/training-guides/lab000-virtualbox-basics.xml:555(td) +msgid "Vboxnet1" +msgstr "" + +#: ./doc/training-guides/lab000-virtualbox-basics.xml:266(td) +msgid "10.20.20.1" +msgstr "" + +#: ./doc/training-guides/lab000-virtualbox-basics.xml:290(emphasis) ./doc/training-guides/lab000-virtualbox-basics.xml:394(td) ./doc/training-guides/lab000-virtualbox-basics.xml:473(td) +msgid "Vboxnet2" +msgstr "" + +#: ./doc/training-guides/lab000-virtualbox-basics.xml:300(td) +msgid "192.168.100.1" +msgstr "" + +#: ./doc/training-guides/lab000-virtualbox-basics.xml:317(title) +msgid "Image: Vboxnet2" +msgstr "" + +#: ./doc/training-guides/lab000-virtualbox-basics.xml:324(guilabel) +msgid "Install SSH and FTP" +msgstr "" + +#: ./doc/training-guides/lab000-virtualbox-basics.xml:327(para) +msgid "You may benefit by installing SSH and FTP so that you could use your remote shell to login into the machine and use your terminal which is more convenient that using the Virtual Machines tty through the Virtual Box's UI. You get a few added comforts like copy - paste commands into the remote terminal which is not possible directly on VM." +msgstr "" + +#: ./doc/training-guides/lab000-virtualbox-basics.xml:335(para) +msgid "FTP is for transferring files to and fro ... you can also use SFTP or install FTPD on both HOST and VM's." +msgstr "" + +#: ./doc/training-guides/lab000-virtualbox-basics.xml:339(para) +msgid "Installation of SSH and FTP with its configuration is out of scope of this GUIDE and I may put it up but it depends upon my free time. If someone wants to contribute to this - please do so." +msgstr "" + +#: ./doc/training-guides/lab000-virtualbox-basics.xml:345(para) +msgid "Note:Please set up the Networks from inside the VM before trying to SSH and FTP into the machines. I would suggest setting it up at once just after the installation of the Server on VM's is over." +msgstr "" + +#: ./doc/training-guides/lab000-virtualbox-basics.xml:349(guilabel) +msgid "Install Your VM's Instances" +msgstr "" + +#: ./doc/training-guides/lab000-virtualbox-basics.xml:352(para) +msgid "During Installation of The Operating Systems you will be asked for Custom Software to Install , if you are confused or not sure about this, just skip this step by pressing Enter Key without selecting any of the given Options." +msgstr "" + +#: ./doc/training-guides/lab000-virtualbox-basics.xml:358(para) +msgid "Warning - Please do not install any of the other packages except for which are mentioned below unless you know what you are doing. There is a good chance that you may end up getting unwanted errors, package conflicts ... due to the same." +msgstr "" + +#: ./doc/training-guides/lab000-virtualbox-basics.xml:363(guilabel) +msgid "Control Node:" +msgstr "" + +#: ./doc/training-guides/lab000-virtualbox-basics.xml:364(para) +msgid "Create a new virtual machine. Select Ubuntu Server" +msgstr "" + +#: ./doc/training-guides/lab000-virtualbox-basics.xml:366(title) ./doc/training-guides/lab000-virtualbox-basics.xml:443(title) ./doc/training-guides/lab000-virtualbox-basics.xml:530(title) +msgid "Create New Virtual Machine" +msgstr "" + +#: ./doc/training-guides/lab000-virtualbox-basics.xml:373(para) +msgid "Select appropriate RAM, minimum 512 MB of RAM for Control Node. Rest all can be default settings. The hard disk size can be 8GB as default." +msgstr "" + +#: ./doc/training-guides/lab000-virtualbox-basics.xml:376(para) ./doc/training-guides/lab000-virtualbox-basics.xml:450(para) ./doc/training-guides/lab000-virtualbox-basics.xml:537(para) +msgid "Configure the networks" +msgstr "" + +#: ./doc/training-guides/lab000-virtualbox-basics.xml:377(para) ./doc/training-guides/lab000-virtualbox-basics.xml:451(para) ./doc/training-guides/lab000-virtualbox-basics.xml:538(para) +msgid "(Ignore the IP Address for now, you will set it up from inside the VM)" +msgstr "" + +#: ./doc/training-guides/lab000-virtualbox-basics.xml:383(th) ./doc/training-guides/lab000-virtualbox-basics.xml:457(th) ./doc/training-guides/lab000-virtualbox-basics.xml:544(th) +msgid "Network Adapter" +msgstr "" + +#: ./doc/training-guides/lab000-virtualbox-basics.xml:384(th) ./doc/training-guides/lab000-virtualbox-basics.xml:458(th) ./doc/training-guides/lab000-virtualbox-basics.xml:545(th) +msgid "Host-Only Adapter Name" +msgstr "" + +#: ./doc/training-guides/lab000-virtualbox-basics.xml:385(th) ./doc/training-guides/lab000-virtualbox-basics.xml:459(th) ./doc/training-guides/lab000-virtualbox-basics.xml:546(th) +msgid "IP Address" +msgstr "" + +#: ./doc/training-guides/lab000-virtualbox-basics.xml:388(td) ./doc/training-guides/lab000-virtualbox-basics.xml:462(td) ./doc/training-guides/lab000-virtualbox-basics.xml:549(td) +msgid "eth0" +msgstr "" + +#: ./doc/training-guides/lab000-virtualbox-basics.xml:390(td) +msgid "10.10.10.51" +msgstr "" + +#: ./doc/training-guides/lab000-virtualbox-basics.xml:393(td) ./doc/training-guides/lab000-virtualbox-basics.xml:467(td) ./doc/training-guides/lab000-virtualbox-basics.xml:554(td) +msgid "eth1" +msgstr "" + +#: ./doc/training-guides/lab000-virtualbox-basics.xml:395(td) ./doc/training-guides/lab000-virtualbox-basics.xml:474(td) +msgid "192.168.100.51" +msgstr "" + +#: ./doc/training-guides/lab000-virtualbox-basics.xml:398(td) ./doc/training-guides/lab000-virtualbox-basics.xml:472(td) ./doc/training-guides/lab000-virtualbox-basics.xml:559(td) +msgid "eth2" +msgstr "" + +#: ./doc/training-guides/lab000-virtualbox-basics.xml:399(td) ./doc/training-guides/lab000-virtualbox-basics.xml:478(td) ./doc/training-guides/lab000-virtualbox-basics.xml:560(td) +msgid "NAT" +msgstr "" + +#: ./doc/training-guides/lab000-virtualbox-basics.xml:400(td) ./doc/training-guides/lab000-virtualbox-basics.xml:479(td) ./doc/training-guides/lab000-virtualbox-basics.xml:561(td) +msgid "DHCP" +msgstr "" + +#: ./doc/training-guides/lab000-virtualbox-basics.xml:404(emphasis) ./doc/training-guides/lab000-virtualbox-basics.xml:483(emphasis) ./doc/training-guides/lab000-virtualbox-basics.xml:565(emphasis) +msgid "Adapter 1 (Vboxnet0)" +msgstr "" + +#: ./doc/training-guides/lab000-virtualbox-basics.xml:406(title) ./doc/training-guides/lab000-virtualbox-basics.xml:567(title) +msgid "Adapter1 - Vboxnet0" +msgstr "" + +#: ./doc/training-guides/lab000-virtualbox-basics.xml:413(emphasis) +msgid "Adapter 2 (Vboxnet2)" +msgstr "" + +#: ./doc/training-guides/lab000-virtualbox-basics.xml:415(title) +msgid "Adapter2 - Vboxnet2" +msgstr "" + +#: ./doc/training-guides/lab000-virtualbox-basics.xml:422(emphasis) ./doc/training-guides/lab000-virtualbox-basics.xml:583(emphasis) +msgid "Adapter 3 (NAT)" +msgstr "" + +#: ./doc/training-guides/lab000-virtualbox-basics.xml:424(title) ./doc/training-guides/lab000-virtualbox-basics.xml:585(title) +msgid "Adapter3 - NAT" +msgstr "" + +#: ./doc/training-guides/lab000-virtualbox-basics.xml:431(para) ./doc/training-guides/lab000-virtualbox-basics.xml:519(para) ./doc/training-guides/lab000-virtualbox-basics.xml:592(para) +msgid "Now Install Ubuntu Server 12.04 or 13.04 on this machine." +msgstr "" + +#: ./doc/training-guides/lab000-virtualbox-basics.xml:433(para) ./doc/training-guides/lab000-virtualbox-basics.xml:521(para) ./doc/training-guides/lab000-virtualbox-basics.xml:594(para) +msgid "Note :Install SSH server when asked for Custom Software to Install. Rest of the packages are not required and may come in the way of OpenStack packages - like DNS servers etc. (not necessary). Unless you know what you are doing." +msgstr "" + +#: ./doc/training-guides/lab000-virtualbox-basics.xml:438(guilabel) +msgid "Network Node:" +msgstr "" + +#: ./doc/training-guides/lab000-virtualbox-basics.xml:439(para) +msgid "Create a new Virtual Machine," +msgstr "" + +#: ./doc/training-guides/lab000-virtualbox-basics.xml:440(para) +msgid "Minimum RAM is 512MB. Rest all can be left default. Minimum HDD space 8GB." +msgstr "" + +#: ./doc/training-guides/lab000-virtualbox-basics.xml:464(td) +msgid "10.10.10.52" +msgstr "" + +#: ./doc/training-guides/lab000-virtualbox-basics.xml:469(td) +msgid "10.20.20.52" +msgstr "" + +#: ./doc/training-guides/lab000-virtualbox-basics.xml:477(td) +msgid "eth3" +msgstr "" + +#: ./doc/training-guides/lab000-virtualbox-basics.xml:485(title) +msgid "Adapter 1 - Vboxnet0" +msgstr "" + +#: ./doc/training-guides/lab000-virtualbox-basics.xml:492(emphasis) ./doc/training-guides/lab000-virtualbox-basics.xml:574(emphasis) +msgid "Adapter 2 (Vboxnet1)" +msgstr "" + +#: ./doc/training-guides/lab000-virtualbox-basics.xml:494(title) ./doc/training-guides/lab000-virtualbox-basics.xml:576(title) +msgid "Adapter2 - Vboxnet1" +msgstr "" + +#: ./doc/training-guides/lab000-virtualbox-basics.xml:501(emphasis) +msgid "Adapter 3 (Vboxnet2)" +msgstr "" + +#: ./doc/training-guides/lab000-virtualbox-basics.xml:503(title) +msgid "Adapter3 - Vboxnet2" +msgstr "" + +#: ./doc/training-guides/lab000-virtualbox-basics.xml:510(emphasis) +msgid "Adapter 4 (NAT)" +msgstr "" + +#: ./doc/training-guides/lab000-virtualbox-basics.xml:512(title) +msgid "Adapter4 - NAT" +msgstr "" + +#: ./doc/training-guides/lab000-virtualbox-basics.xml:526(guilabel) +msgid "Compute Node:" +msgstr "" + +#: ./doc/training-guides/lab000-virtualbox-basics.xml:527(para) +msgid "Create a new virtual machine, give it atleast 1,000 MB RAM. Rest all can be left as defaults. Give atleast 8GB HDD." +msgstr "" + +#: ./doc/training-guides/lab000-virtualbox-basics.xml:551(td) +msgid "10.10.10.53" +msgstr "" + +#: ./doc/training-guides/lab000-virtualbox-basics.xml:556(td) +msgid "10.20.20.53" +msgstr "" + +#: ./doc/training-guides/lab000-virtualbox-basics.xml:599(guilabel) +msgid "Warnings/Advice :" +msgstr "" + +#: ./doc/training-guides/lab000-virtualbox-basics.xml:602(para) +msgid "Well there are a few warnings that I must give you out of experience due to common habits that most people may have :" +msgstr "" + +#: ./doc/training-guides/lab000-virtualbox-basics.xml:607(para) +msgid "Sometimes shutting down your Virtual Machine may lead to malfunctioning of OpenStack Services. Try not to direct shutdown your 3. In case your VM's don't get internet." +msgstr "" + +#: ./doc/training-guides/lab000-virtualbox-basics.xml:612(para) +msgid "From your VM Instance, Use ping command to see whether Internet is on." +msgstr "" + +#: ./doc/training-guides/lab000-virtualbox-basics.xml:619(para) +msgid "If its not connected, restart networking service-" +msgstr "" + +#: ./doc/training-guides/lab000-virtualbox-basics.xml:627(para) +msgid "If this doesn't work, you need to check your network settings from Virtual Box, you may have left something or misconfigured it." +msgstr "" + +#: ./doc/training-guides/lab000-virtualbox-basics.xml:632(para) +msgid "This should reconnect your network about 99% of the times. If you are really unlucky you must be having some other problems or your Internet connection itself is not functioning." +msgstr "" + +#: ./doc/training-guides/lab000-virtualbox-basics.xml:638(para) +msgid "Note :There are known bugs with the ping under NAT. Although the latest versions of Virtual Box have better performance, sometimes ping may not work even if your Network is connected to internet." +msgstr "" + +#: ./doc/training-guides/lab000-virtualbox-basics.xml:644(para) +msgid "Congrats, you are ready with the infrastructure for deploying OpenStack. Just make sure that you have installed Ubuntu Server on the above setup Virtual Box Instances. In the next section we will go through deploying OpenStack using the above created Virtual Box instances." +msgstr "" + +#: ./doc/training-guides/bk001-ch007-associate-network-node.xml:10(title) +msgid "Day 2, 09:00 to 11:00" +msgstr "" + +#: ./doc/training-guides/bk001-ch007-associate-network-node.xml:30(title) +msgid "Network CLI Commands" +msgstr "" + +#: ./doc/training-guides/bk001-ch007-associate-network-node.xml:37(title) +msgid "Manage Networks" +msgstr "" + +#: ./doc/training-guides/bk001-ch008-associate-network-node-quiz.xml:8(title) +msgid "Day 2, 10:40 to 11:00" +msgstr "" + +#: ./doc/training-guides/bk002-ch006-operator-controller-node-quiz.xml:8(title) +msgid "Days 2 to 4, 16:40 to 17:00" +msgstr "" + +#: ./doc/training-guides/card070-create-floating-ips.xml:7(title) +msgid "Create floating ip" +msgstr "" + +#: ./doc/training-guides/module003-ch005-the-ring.xml:7(title) +msgid "Ring Builder" +msgstr "" + +#: ./doc/training-guides/module003-ch005-the-ring.xml:8(para) +msgid "The rings are built and managed manually by a utility called the ring-builder. The ring-builder assigns partitions to devices and writes an optimized Python structure to a gzipped, serialized file on disk for shipping out to the servers. The server processes just check the modification time of the file occasionally and reload their in-memory copies of the ring structure as needed. Because of how the ring-builder manages changes to the ring, using a slightly older ring usually just means one of the three replicas for a subset of the partitions will be incorrect, which can be easily worked around." +msgstr "" + +#: ./doc/training-guides/module003-ch005-the-ring.xml:18(para) +msgid "The ring-builder also keeps its own builder file with the ring information and additional data required to build future rings. It is very important to keep multiple backup copies of these builder files. One option is to copy the builder files out to every server while copying the ring files themselves. Another is to upload the builder files into the cluster itself. Complete loss of a builder file will mean creating a new ring from scratch, nearly all partitions will end up assigned to different devices, and therefore nearly all data stored will have to be replicated to new locations. So, recovery from a builder file loss is possible, but data will definitely be unreachable for an extended time." +msgstr "" + +#: ./doc/training-guides/module003-ch005-the-ring.xml:30(guilabel) +msgid "Ring Data Structure" +msgstr "" + +#: ./doc/training-guides/module003-ch005-the-ring.xml:31(para) +msgid "The ring data structure consists of three top level fields: a list of devices in the cluster, a list of lists of device ids indicating partition to device assignments, and an integer indicating the number of bits to shift an MD5 hash to calculate the partition for the hash." +msgstr "" + +#: ./doc/training-guides/module003-ch005-the-ring.xml:36(guilabel) +msgid "Partition Assignment List" +msgstr "" + +#: ./doc/training-guides/module003-ch005-the-ring.xml:38(para) +msgid "This is a list of array(‘H’) of devices ids. The outermost list contains an array(‘H’) for each replica. Each array(‘H’) has a length equal to the partition count for the ring. Each integer in the array(‘H’) is an index into the above list of devices. The partition list is known internally to the Ring class as _replica2part2dev_id." +msgstr "" + +#: ./doc/training-guides/module003-ch005-the-ring.xml:45(para) +msgid "So, to create a list of device dictionaries assigned to a partition, the Python code would look like: devices = [self.devs[part2dev_id[partition]] for part2dev_id in self._replica2part2dev_id]" +msgstr "" + +#: ./doc/training-guides/module003-ch005-the-ring.xml:49(para) +msgid "That code is a little simplistic, as it does not account for the removal of duplicate devices. If a ring has more replicas than devices, then a partition will have more than one replica on one device; that’s simply the pigeonhole principle at work." +msgstr "" + +#: ./doc/training-guides/module003-ch005-the-ring.xml:54(para) +msgid "array(‘H’) is used for memory conservation as there may be millions of partitions." +msgstr "" + +#: ./doc/training-guides/module003-ch005-the-ring.xml:56(guilabel) +msgid "Fractional Replicas" +msgstr "" + +#: ./doc/training-guides/module003-ch005-the-ring.xml:57(para) +msgid "A ring is not restricted to having an integer number of replicas. In order to support the gradual changing of replica counts, the ring is able to have a real number of replicas." +msgstr "" + +#: ./doc/training-guides/module003-ch005-the-ring.xml:61(para) +msgid "When the number of replicas is not an integer, then the last element of _replica2part2dev_id will have a length that is less than the partition count for the ring. This means that some partitions will have more replicas than others. For example, if a ring has 3.25 replicas, then 25% of its partitions will have four replicas, while the remaining 75% will have just three." +msgstr "" + +#: ./doc/training-guides/module003-ch005-the-ring.xml:69(guilabel) +msgid "Partition Shift Value" +msgstr "" + +#: ./doc/training-guides/module003-ch005-the-ring.xml:70(para) +msgid "The partition shift value is known internally to the Ring class as _part_shift. This value used to shift an MD5 hash to calculate the partition on which the data for that hash should reside. Only the top four bytes of the hash is used in this process. For example, to compute the partition for the path /account/container/object the Python code might look like: partition = unpack_from('>I', md5('/account/container/object').digest())[0] >> self._part_shift" +msgstr "" + +#: ./doc/training-guides/module003-ch005-the-ring.xml:80(para) +msgid "For a ring generated with part_power P, the partition shift value is 32 - P." +msgstr "" + +#: ./doc/training-guides/module003-ch005-the-ring.xml:82(guilabel) +msgid "Building the Ring" +msgstr "" + +#: ./doc/training-guides/module003-ch005-the-ring.xml:83(para) +msgid "The initial building of the ring first calculates the number of partitions that should ideally be assigned to each device based the device’s weight. For example, given a partition power of 20, the ring will have 1,048,576 partitions. If there are 1,000 devices of equal weight they will each desire 1,048.576 partitions. The devices are then sorted by the number of partitions they desire and kept in order throughout the initialization process." +msgstr "" + +#: ./doc/training-guides/module003-ch005-the-ring.xml:92(para) +msgid "Note: each device is also assigned a random tiebreaker value that is used when two devices desire the same number of partitions. This tiebreaker is not stored on disk anywhere, and so two different rings created with the same parameters will have different partition assignments. For repeatable partition assignments, RingBuilder.rebalance() takes an optional seed value that will be used to seed Python’s pseudo-random number generator." +msgstr "" + +#: ./doc/training-guides/module003-ch005-the-ring.xml:100(para) +msgid "Then, the ring builder assigns each replica of each partition to the device that desires the most partitions at that point while keeping it as far away as possible from other replicas. The ring builder prefers to assign a replica to a device in a regions that has no replicas already; should there be no such region available, the ring builder will try to find a device in a different zone; if not possible, it will look on a different server; failing that, it will just look for a device that has no replicas; finally, if all other options are exhausted, the ring builder will assign the replica to the device that has the fewest replicas already assigned. Note that assignment of multiple replicas to one device will only happen if the ring has fewer devices than it has replicas." +msgstr "" + +#: ./doc/training-guides/module003-ch005-the-ring.xml:115(para) +msgid "When building a new ring based on an old ring, the desired number of partitions each device wants is recalculated. Next the partitions to be reassigned are gathered up. Any removed devices have all their assigned partitions unassigned and added to the gathered list. Any partition replicas that (due to the addition of new devices) can be spread out for better durability are unassigned and added to the gathered list. Any devices that have more partitions than they now desire have random partitions unassigned from them and added to the gathered list. Lastly, the gathered partitions are then reassigned to devices using a similar method as in the initial assignment described above." +msgstr "" + +#: ./doc/training-guides/module003-ch005-the-ring.xml:128(para) +msgid "Whenever a partition has a replica reassigned, the time of the reassignment is recorded. This is taken into account when gathering partitions to reassign so that no partition is moved twice in a configurable amount of time. This configurable amount of time is known internally to the RingBuilder class as min_part_hours. This restriction is ignored for replicas of partitions on devices that have been removed, as removing a device only happens on device failure and there’s no choice but to make a reassignment." +msgstr "" + +#: ./doc/training-guides/module003-ch005-the-ring.xml:138(para) +msgid "The above processes don’t always perfectly rebalance a ring due to the random nature of gathering partitions for reassignment. To help reach a more balanced ring, the rebalance process is repeated until near perfect (less 1% off) or when the balance doesn’t improve by at least 1% (indicating we probably can’t get perfect balance due to wildly imbalanced zones or too many partitions recently moved)." +msgstr "" + +#: ./doc/training-guides/card038.xml:7(title) +msgid "Install and configure OpenStack Identity Service in the Controller Node" +msgstr "" + +#: ./doc/training-guides/sources/cinder/development.environment.xml:7(title) +msgid "Development.Environment" +msgstr "" + +#: ./doc/training-guides/sources/cinder/development.environment.xml:9(title) ./doc/training-guides/sources/cinder/addmethod.openstackapi.xml:9(title) ./doc/training-guides/sources/cinder/drivers.xml:9(title) ./doc/training-guides/sources/cinder/unit_tests.xml:9(title) ./doc/training-guides/sources/cinder/architecture.xml:9(title) ./doc/training-guides/sources/cinder/threading.xml:9(title) +msgid "Header" +msgstr "" + +#: ./doc/training-guides/sources/cinder/development.environment.xml:10(para) ./doc/training-guides/sources/cinder/architecture.xml:10(para) +msgid ".. Copyright 2010-2011 United States Government as represented by the Administrator of the National Aeronautics and Space Administration. All Rights Reserved. Licensed under the Apache License, Version 2.0 (the \"License\"); you may not use this file except in compliance with the License. You may obtain a copy of the License at http://www.apache.org/licenses/LICENSE-2.0 Unless required by applicable law or agreed to in writing, software distributed under the License is distributed on an \"AS IS\" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. See the License for the specific language governing permissions and limitations under the License." +msgstr "" + +#: ./doc/training-guides/sources/cinder/development.environment.xml:27(title) +msgid "Setting-Up-A-Development-Environment" +msgstr "" + +#: ./doc/training-guides/sources/cinder/development.environment.xml:28(para) +msgid "==================================== This page describes how to setup a working Python development environment that can be used in developing cinder on Ubuntu, Fedora or Mac OS X. These instructions assume you're already familiar with git. Refer to GettingTheCode_ for additional information. .. _GettingTheCode: http://wiki.openstack.org/GettingTheCode Following these instructions will allow you to run the cinder unit tests. If you want to be able to run cinder (i.e., launch VM instances), you will also need to install libvirt and at least one of the `supported hypervisors`_. Running cinder is currently only supported on Linux, although you can run the unit tests on Mac OS X. See :doc:`../quickstart` for how to get a working version of OpenStack Compute running as quickly as possible. .. _supported hypervisors: http://wiki.openstack.org/HypervisorSupportMatrix" +msgstr "" + +#: ./doc/training-guides/sources/cinder/development.environment.xml:46(title) +msgid "Virtual-Environments" +msgstr "" + +#: ./doc/training-guides/sources/cinder/development.environment.xml:47(para) +msgid "-------------------- Cinder development uses `virtualenv [http://pypi.python.org/pypi/virtualenv]`__ to track and manage Python dependencies while in development and testing. This allows you to install all of the Python package dependencies in a virtual environment or \"virtualenv\" (a special subdirectory of your cinder directory), instead of installing the packages at the system level. .. note:: Virtualenv is useful for running the unit tests, but is not typically used for full integration testing or production usage." +msgstr "" + +#: ./doc/training-guides/sources/cinder/development.environment.xml:60(title) +msgid "Linux-Systems" +msgstr "" + +#: ./doc/training-guides/sources/cinder/development.environment.xml:61(para) +msgid "------------- .. note:: This section is tested for Cinder on Ubuntu (12.04-64) and Fedora-based (RHEL 6.1) distributions. Feel free to add notes and change according to your experiences or operating system. Install the prerequisite packages. On Ubuntu:: sudo apt-get install python-dev libssl-dev python-pip git-core libmysqlclient-dev libpq-dev On Fedora-based distributions like Fedora, RHEL, CentOS and Scientific Linux:: sudo yum install python-devel openssl-devel python-pip git libmysqlclient-dev libqp-dev" +msgstr "" + +#: ./doc/training-guides/sources/cinder/development.environment.xml:75(title) +msgid "Mac-Os-X-Systems" +msgstr "" + +#: ./doc/training-guides/sources/cinder/development.environment.xml:76(para) +msgid "---------------- Install virtualenv:: sudo easy_install virtualenv Check the version of OpenSSL you have installed:: openssl version If you have installed OpenSSL 1.0.0a, which can happen when installing a MacPorts package for OpenSSL, you will see an error when running ``cinder.tests.auth_unittest.AuthTestCase.test_209_can_generate_x509``. The stock version of OpenSSL that ships with Mac OS X 10.6 (OpenSSL 0.9.8l) or Mac OS X 10.7 (OpenSSL 0.9.8r) works fine with cinder." +msgstr "" + +#: ./doc/training-guides/sources/cinder/development.environment.xml:90(title) +msgid "Getting-The-Code" +msgstr "" + +#: ./doc/training-guides/sources/cinder/development.environment.xml:91(para) +msgid "---------------- Grab the code from GitHub:: git clone https://github.com/openstack/cinder.git cd cinder" +msgstr "" + +#: ./doc/training-guides/sources/cinder/development.environment.xml:99(title) +msgid "Running-Unit-Tests" +msgstr "" + +#: ./doc/training-guides/sources/cinder/development.environment.xml:100(para) +msgid "------------------ The unit tests will run by default inside a virtualenv in the ``.venv`` directory. Run the unit tests by doing:: ./run_tests.sh The first time you run them, you will be asked if you want to create a virtual environment (hit \"y\"):: No virtual environment found...create one? (Y/n) See :doc:`unit_tests` for more details. .. _virtualenv:" +msgstr "" + +#: ./doc/training-guides/sources/cinder/development.environment.xml:113(title) +msgid "Manually-Installing-And-Using-The-Virtualenv" +msgstr "" + +#: ./doc/training-guides/sources/cinder/development.environment.xml:114(para) +msgid "-------------------------------------------- You can manually install the virtual environment instead of having ``run_tests.sh`` do it for you:: python tools/install_venv.py This will install all of the Python packages listed in the ``requirements.txt`` file into your virtualenv. There will also be some additional packages (pip, setuptools) that are installed by the ``tools/install_venv.py`` file into the virutalenv. If all goes well, you should get a message something like this:: Cinder development environment setup is complete. To activate the Cinder virtualenv for the extent of your current shell session you can run:: $ source .venv/bin/activate Or, if you prefer, you can run commands in the virtualenv on a case by case basis by running:: $ tools/with_venv.sh [your command]" +msgstr "" + +#: ./doc/training-guides/sources/cinder/development.environment.xml:134(title) +msgid "Contributing-Your-Work" +msgstr "" + +#: ./doc/training-guides/sources/cinder/development.environment.xml:135(para) +msgid "---------------------- Once your work is complete you may wish to contribute it to the project. Add your name and email address to the ``Authors`` file, and also to the ``.mailmap`` file if you use multiple email addresses. Your contributions can not be merged into trunk unless you are listed in the Authors file. Cinder uses the Gerrit code review system. For information on how to submit your branch to Gerrit, see GerritWorkflow_." +msgstr "" + +#: ./doc/training-guides/sources/cinder/addmethod.openstackapi.xml:7(title) +msgid "Addmethod.Openstackapi" +msgstr "" + +#: ./doc/training-guides/sources/cinder/addmethod.openstackapi.xml:10(para) +msgid ".. Copyright 2010-2011 OpenStack Foundation All Rights Reserved. Licensed under the Apache License, Version 2.0 (the \"License\"); you may not use this file except in compliance with the License. You may obtain a copy of the License at http://www.apache.org/licenses/LICENSE-2.0 Unless required by applicable law or agreed to in writing, software distributed under the License is distributed on an \"AS IS\" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. See the License for the specific language governing permissions and limitations under the License." +msgstr "" + +#: ./doc/training-guides/sources/cinder/addmethod.openstackapi.xml:26(title) +msgid "Adding-A-Method-To-The-Openstack-Api" +msgstr "" + +#: ./doc/training-guides/sources/cinder/addmethod.openstackapi.xml:27(para) +msgid "==================================== The interface is a mostly RESTful API. REST stands for Representational State Transfer and provides an architecture \"style\" for distributed systems using HTTP for transport. Figure out a way to express your request and response in terms of resources that are being created, modified, read, or destroyed." +msgstr "" + +#: ./doc/training-guides/sources/cinder/addmethod.openstackapi.xml:33(title) +msgid "Routing" +msgstr "" + +#: ./doc/training-guides/sources/cinder/addmethod.openstackapi.xml:34(para) +msgid "------- To map URLs to controllers+actions, OpenStack uses the Routes package, a clone of Rails routes for Python implementations. See http://routes.groovie.org/ for more information. URLs are mapped to \"action\" methods on \"controller\" classes in ``cinder/api/openstack/__init__/ApiRouter.__init__`` . See http://routes.groovie.org/manual.html for all syntax, but you'll probably just need these two: - mapper.connect() lets you map a single URL to a single action on a controller. - mapper.resource() connects many standard URLs to actions on a controller." +msgstr "" + +#: ./doc/training-guides/sources/cinder/addmethod.openstackapi.xml:44(title) +msgid "Controllers-And-Actions" +msgstr "" + +#: ./doc/training-guides/sources/cinder/addmethod.openstackapi.xml:45(para) +msgid "----------------------- Controllers live in ``cinder/api/openstack``, and inherit from cinder.wsgi.Controller. See ``cinder/api/openstack/servers.py`` for an example. Action methods take parameters that are sucked out of the URL by mapper.connect() or .resource(). The first two parameters are self and the WebOb request, from which you can get the req.environ, req.body, req.headers, etc." +msgstr "" + +#: ./doc/training-guides/sources/cinder/addmethod.openstackapi.xml:54(para) +msgid "------------- Actions return a dictionary, and wsgi.Controller serializes that to JSON or XML based on the request's content-type. If you define a new controller, you'll need to define a ``_serialization_metadata`` attribute on the class, to tell wsgi.Controller how to convert your dictionary to XML. It needs to know the singular form of any list tag such as ``[servers]`` list contains ``[server]`` tags, and which dictionary keys are to be XML attributes as opposed to subtags such as ``[server id=\"4\"/]`` instead of ``[server][id]4[/id][/server]``. See `cinder/api/openstack/servers.py` for an example. Faults ------ If you need to return a non-200, you should return faults.Fault(webob.exc.HTTPNotFound())" +msgstr "" + +#: ./doc/training-guides/sources/cinder/drivers.xml:10(para) +msgid ".. Copyright (c) 2013 OpenStack Foundation All Rights Reserved. Licensed under the Apache License, Version 2.0 (the \"License\"); you may not use this file except in compliance with the License. You may obtain a copy of the License at http://www.apache.org/licenses/LICENSE-2.0 Unless required by applicable law or agreed to in writing, software distributed under the License is distributed on an \"AS IS\" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. See the License for the specific language governing permissions and limitations under the License." +msgstr "" + +#: ./doc/training-guides/sources/cinder/drivers.xml:27(para) +msgid "======= Cinder exposes an API to users to interact with different storage backend solutions. The following are standards across all drivers for Cinder services to properly interact with a driver." +msgstr "" + +#: ./doc/training-guides/sources/cinder/drivers.xml:35(title) +msgid "Minimum-Features" +msgstr "" + +#: ./doc/training-guides/sources/cinder/drivers.xml:44(para) +msgid "Volume Create/Delete" +msgstr "" + +#: ./doc/training-guides/sources/cinder/drivers.xml:45(para) +msgid "Volume Attach/Detach" +msgstr "" + +#: ./doc/training-guides/sources/cinder/drivers.xml:46(para) +msgid "Snapshot Create/Delete" +msgstr "" + +#: ./doc/training-guides/sources/cinder/drivers.xml:47(para) +msgid "Create Volume from Snapshot" +msgstr "" + +#: ./doc/training-guides/sources/cinder/drivers.xml:48(para) +msgid "Get Volume Stats" +msgstr "" + +#: ./doc/training-guides/sources/cinder/drivers.xml:49(para) +msgid "Copy Image to Volume" +msgstr "" + +#: ./doc/training-guides/sources/cinder/drivers.xml:50(para) +msgid "Copy Volume to Image" +msgstr "" + +#: ./doc/training-guides/sources/cinder/drivers.xml:51(para) +msgid "Clone Volume" +msgstr "" + +#: ./doc/training-guides/sources/cinder/drivers.xml:36(para) +msgid "---------------- Minimum features are enforced to avoid having a grid of what features are supported by which drivers and which releases. Cinder Core requires that all drivers implement the following minimum features. Havana ------ " +msgstr "" + +#: ./doc/training-guides/sources/cinder/drivers.xml:60(para) +msgid "All of the above plus" +msgstr "" + +#: ./doc/training-guides/sources/cinder/drivers.xml:61(para) +msgid "Extend Volume" +msgstr "" + +#: ./doc/training-guides/sources/cinder/drivers.xml:57(para) +msgid "-------- " +msgstr "" + +#: ./doc/training-guides/sources/cinder/drivers.xml:66(title) +msgid "Volume-Stats" +msgstr "" + +#: ./doc/training-guides/sources/cinder/drivers.xml:73(para) +msgid "driver_version" +msgstr "" + +#: ./doc/training-guides/sources/cinder/drivers.xml:74(para) +msgid "free_capacity_gb" +msgstr "" + +#: ./doc/training-guides/sources/cinder/drivers.xml:75(para) +msgid "reserved_percentage" +msgstr "" + +#: ./doc/training-guides/sources/cinder/drivers.xml:76(para) +msgid "storage_protocol" +msgstr "" + +#: ./doc/training-guides/sources/cinder/drivers.xml:77(para) +msgid "total_capacity_gb" +msgstr "" + +#: ./doc/training-guides/sources/cinder/drivers.xml:78(para) +msgid "vendor_name" +msgstr "" + +#: ./doc/training-guides/sources/cinder/drivers.xml:79(para) +msgid "volume_backend_name" +msgstr "" + +#: ./doc/training-guides/sources/cinder/drivers.xml:82(para) +msgid "If the driver is unable to provide a value for free_capacity_gb or" +msgstr "" + +#: ./doc/training-guides/sources/cinder/drivers.xml:67(para) +msgid "------------ Volume stats are used by the different schedulers for the drivers to provide a report on their current state of the backend. The following should be provided by a driver. total_capacity_gb, keywords can be provided instead. Please use 'unknown' if the array cannot report the value or 'infinite' if the array has no upper" +msgstr "" + +#: ./doc/training-guides/sources/cinder/unit_tests.xml:7(title) +msgid "Unit_Tests" +msgstr "" + +#: ./doc/training-guides/sources/cinder/unit_tests.xml:14(title) +msgid "Unit-Tests" +msgstr "" + +#: ./doc/training-guides/sources/cinder/unit_tests.xml:15(para) +msgid "========== Cinder contains a suite of unit tests, in the cinder/tests directory. Any proposed code change will be automatically rejected by the OpenStack Jenkins server [#f1]_ if the change causes unit test failures." +msgstr "" + +#: ./doc/training-guides/sources/cinder/unit_tests.xml:23(title) +msgid "Running-The-Tests" +msgstr "" + +#: ./doc/training-guides/sources/cinder/unit_tests.xml:24(para) +msgid "----------------- Run the unit tests by doing:: ./run_tests.sh This script is a wrapper around the `nose`_ testrunner and the `pep8`_ checker. .. _nose: http://code.google.com/p/python-nose/ .. _pep8: https://github.com/jcrocholl/pep8 Flags ----- The ``run_tests.sh`` script supports several flags. You can view a list of flags by doing:: run_tests.sh -h This will show the following help information:: Usage: ./run_tests.sh [OPTION]... Run Cinder's test suite(s) -V, --virtual-env Always use virtualenv. Install automatically if not present -N, --no-virtual-env Don't use virtualenv. Run tests in local environment -s, --no-site-packages Isolate the virtualenv from the global Python environment -r, --recreate-db Recreate the test database (deprecated, as this is now the default). -n, --no-recreate-db Don't recreate the test database. -x, --stop Stop running tests after the first error or failure. -f, --force Force a clean re-build of the virtual environment. Useful when dependencies have been added. -p, --pep8 Just run pep8 -P, --no-pep8 Don't run pep8 -c, --coverage Generate coverage report -h, --help Print this usage message --hide-elapsed Don't print the elapsed time for each test along with slow test list Because ``run_tests.sh`` is a wrapper around nose, it also accepts the same flags as nosetests. See the `nose options documentation`_ for details about these additional flags. .. _nose options documentation: http://readthedocs.org/docs/nose/en/latest/usage.html#options" +msgstr "" + +#: ./doc/training-guides/sources/cinder/unit_tests.xml:58(title) +msgid "Running-A-Subset-Of-Tests" +msgstr "" + +#: ./doc/training-guides/sources/cinder/unit_tests.xml:59(para) +msgid "------------------------- Instead of running all tests, you can specify an individual directory, file, class, or method that contains test code. To run the tests in the ``cinder/tests/scheduler`` directory:: ./run_tests.sh scheduler To run the tests in the ``cinder/tests/test_libvirt.py`` file:: ./run_tests.sh test_libvirt To run the tests in the `HostStateTestCase` class in ``cinder/tests/test_libvirt.py``:: ./run_tests.sh test_libvirt:HostStateTestCase To run the `ToPrimitiveTestCase.test_dict` test method in ``cinder/tests/test_utils.py``:: ./run_tests.sh test_utils:ToPrimitiveTestCase.test_dict" +msgstr "" + +#: ./doc/training-guides/sources/cinder/unit_tests.xml:76(title) +msgid "Suppressing-Logging-Output-When-Tests-Fail" +msgstr "" + +#: ./doc/training-guides/sources/cinder/unit_tests.xml:77(para) +msgid "------------------------------------------ By default, when one or more unit test fails, all of the data sent to the logger during the failed tests will appear on standard output, which typically consists of many lines of texts. The logging output can make it difficult to identify which specific tests have failed, unless your terminal has a large scrollback buffer or you have redirected output to a file. You can suppress the logging output by calling ``run_tests.sh`` with the nose flag:: --nologcapture" +msgstr "" + +#: ./doc/training-guides/sources/cinder/unit_tests.xml:90(title) +msgid "Virtualenv" +msgstr "" + +#: ./doc/training-guides/sources/cinder/unit_tests.xml:91(para) +msgid "---------- By default, the tests use the Python packages installed inside a virtualenv [#f2]_. (This is equivalent to using the ``-V, --virtualenv`` flag). If the virtualenv does not exist, it will be created the first time the tests are run. If you wish to recreate the virtualenv, call ``run_tests.sh`` with the flag:: -f, --force Recreating the virtualenv is useful if the package dependencies have changed since the virtualenv was last created. If the ``requirements.txt`` or ``tools/install_venv.py`` files have changed, it's a good idea to recreate the virtualenv. By default, the unit tests will see both the packages in the virtualenv and the packages that have been installed in the Python global environment. In some cases, the packages in the Python global environment may cause a conflict with the packages in the virtualenv. If this occurs, you can isolate the virtualenv from the global environment by using the flag:: -s, --no-site packages If you do not wish to use a virtualenv at all, use the flag:: -N, --no-virtual-env" +msgstr "" + +#: ./doc/training-guides/sources/cinder/unit_tests.xml:113(title) +msgid "Database" +msgstr "" + +#: ./doc/training-guides/sources/cinder/unit_tests.xml:114(para) +msgid "-------- Some of the unit tests make queries against an sqlite database [#f3]_. By default, the test database (``tests.sqlite``) is deleted and recreated each time ``run_tests.sh`` is invoked (This is equivalent to using the ``-r, --recreate-db`` flag). To reduce testing time if a database already exists it can be reused by using the flag:: -n, --no-recreate-db Reusing an existing database may cause tests to fail if the schema has changed. If any files in the ``cinder/db/sqlalchemy`` have changed, it's a good idea to recreate the test database." +msgstr "" + +#: ./doc/training-guides/sources/cinder/unit_tests.xml:128(title) +msgid "Gotchas" +msgstr "" + +#: ./doc/training-guides/sources/cinder/unit_tests.xml:129(para) +msgid "------- If you are running the unit tests from a shared folder, you may see tests start to fail or stop completely as a result of Python lockfile issues [#f4]_. You can get around this by manually setting or updating the following line in ``cinder/tests/conf_fixture.py``:: CONF['lock_path'].SetDefault('/tmp') Note that you may use any location (not just ``/tmp``!) as long as it is not a shared folder. .. rubric:: Footnotes .. [#f1] See :doc:`jenkins`. .. [#f2] See :doc:`development.environment` for more details about the use of virtualenv. .. [#f3] There is an effort underway to use a fake DB implementation for the unit tests. See https://lists.launchpad.net/openstack/msg05604.html" +msgstr "" + +#: ./doc/training-guides/sources/cinder/architecture.xml:7(title) +msgid "Architecture" +msgstr "" + +#: ./doc/training-guides/sources/cinder/architecture.xml:27(title) +msgid "Cinder-System-Architecture" +msgstr "" + +#: ./doc/training-guides/sources/cinder/architecture.xml:28(para) +msgid "========================== The Cinder Block Storage Service is intended to be ran on one or more nodes. Cinder uses a sql-based central database that is shared by all Cinder services in the system. The amount and depth of the data fits into a sql database quite well. For small deployments this seems like an optimal solution. For larger deployments, and especially if security is a concern, cinder will be moving towards multiple data stores with some kind of aggregation system." +msgstr "" + +#: ./doc/training-guides/sources/cinder/architecture.xml:35(title) +msgid "Components" +msgstr "" + +#: ./doc/training-guides/sources/cinder/architecture.xml:55(para) +msgid "DB: sql database for data storage. Used by all components (LINKS NOT SHOWN)" +msgstr "" + +#: ./doc/training-guides/sources/cinder/architecture.xml:56(para) +msgid "Web Dashboard: potential external component that talks to the api" +msgstr "" + +#: ./doc/training-guides/sources/cinder/architecture.xml:57(para) +msgid "api: component that receives http requests, converts commands and communicates with other components via the queue or http" +msgstr "" + +#: ./doc/training-guides/sources/cinder/architecture.xml:58(para) +msgid "Auth Manager: component responsible for users/projects/and roles. Can backend to DB or LDAP. This is not a separate binary, but rather a python class that is used by most components in the system." +msgstr "" + +#: ./doc/training-guides/sources/cinder/architecture.xml:59(para) +msgid "scheduler: decides which host gets each volume" +msgstr "" + +#: ./doc/training-guides/sources/cinder/architecture.xml:60(para) +msgid "volume: manages dynamically attachable block devices." +msgstr "" + +#: ./doc/training-guides/sources/cinder/architecture.xml:36(para) +msgid "---------- Below you will a brief explanation of the different components. :: /- ( LDAP ) [ Auth Manager ] --- | \\- ( DB ) | | cinderclient | / \\ | [ Web Dashboard ]- -[ api ] -- [ AMQP ] -- [ scheduler ] -- [ volume ] -- ( iSCSI ) \\ / | novaclient | | | | [ REST ] " +msgstr "" + +#: ./doc/training-guides/sources/cinder/threading.xml:14(title) +msgid "Threading-Model" +msgstr "" + +#: ./doc/training-guides/sources/cinder/threading.xml:18(para) +msgid "model of threading, implemented" +msgstr "" + +#: ./doc/training-guides/sources/cinder/threading.xml:15(para) +msgid "=============== through using the Python `eventlet [http://eventlet.net/]`_ and `greenlet [http://packages.python.org/greenlet/]`_ libraries. Green threads use a cooperative model of threading: thread context switches can only occur when specific eventlet or greenlet library calls are made. For example, sleep and certain I/O calls. From the operating system's point of view, each OpenStack service runs in a single thread. The use of green threads reduces the likelihood of race conditions, but does not completely eliminate them. In some cases, you may need to use the ``@utils.synchronized(...)`` decorator to avoid races. In addition, since there is only one operating system thread, a call that blocks that main thread will block the entire process." +msgstr "" + +#: ./doc/training-guides/sources/cinder/threading.xml:34(title) +msgid "Yielding-The-Thread-In-Long-Running-Tasks" +msgstr "" + +#: ./doc/training-guides/sources/cinder/threading.xml:35(para) +msgid "----------------------------------------- If a code path takes a long time to execute and does not contain any methods that trigger an eventlet context switch, the long-running thread will block any pending threads. This scenario can be avoided by adding calls to the eventlet sleep method in the long-running code path. The sleep call will trigger a context switch if there are pending threads, and using an argument of 0 will avoid introducing delays in the case that there is only a single green thread:: from eventlet import greenthread ... greenthread.sleep(0)" +msgstr "" + +#: ./doc/training-guides/sources/cinder/threading.xml:50(title) +msgid "Mysql-Access-And-Eventlet" +msgstr "" + +#: ./doc/training-guides/sources/cinder/threading.xml:51(para) +msgid "------------------------- Queries to the MySQL database will block the main thread of a service. This is because OpenStack services use an external C library for accessing the MySQL database. Since eventlet cannot use monkey-patching to intercept blocking calls in a C library, the resulting database query blocks the thread. The Diablo release contained a thread-pooling implementation that did not block, but this implementation resulted in a `bug`_ and was removed. See this `mailing list thread`_ for a discussion of this issue, including a discussion of the `impact on performance`_. .. _bug: https://bugs.launchpad.net/cinder/+bug/838581 .. _mailing list thread: https://lists.launchpad.net/openstack/msg08118.html" +msgstr "" + +#. Put one translator per line, in the form of NAME , YEAR1, YEAR2 +#: ./doc/training-guides/sources/cinder/threading.xml:0(None) +msgid "translator-credits" +msgstr "" + diff --git a/doc/user-guide-admin/locale/he_IL.po b/doc/user-guide-admin/locale/he_IL.po new file mode 100644 index 0000000000..17c6a5d0c8 --- /dev/null +++ b/doc/user-guide-admin/locale/he_IL.po @@ -0,0 +1,2869 @@ +# +# Translators: +msgid "" +msgstr "" +"Project-Id-Version: OpenStack Manuals\n" +"POT-Creation-Date: 2014-01-30 06:24+0000\n" +"PO-Revision-Date: 2014-01-22 22:16+0000\n" +"Last-Translator: openstackjenkins \n" +"Language-Team: Hebrew (Israel) (http://www.transifex.com/projects/p/openstack/language/he_IL/)\n" +"MIME-Version: 1.0\n" +"Content-Type: text/plain; charset=UTF-8\n" +"Content-Transfer-Encoding: 8bit\n" +"Language: he_IL\n" +"Plural-Forms: nplurals=2; plural=(n != 1);\n" + +#: ./doc/user-guide-admin/section_dashboard_admin_manage_stacks.xml4(title) +#: ./doc/user-guide-admin/section_cli_admin_manage_stacks.xml5(title) +msgid "Launch and manage stacks" +msgstr "" + +#: ./doc/user-guide-admin/section_dashboard_admin_manage_stacks.xml5(para) +#: ./doc/user-guide-admin/section_cli_admin_manage_stacks.xml6(para) +msgid "" +"The Orchestration service provides a template-based orchestration engine for" +" the OpenStack cloud, which can be used to create and manage cloud " +"infrastructure resources such as storage, networking, instances, and " +"applications as a repeatable running environment." +msgstr "" + +#: ./doc/user-guide-admin/section_dashboard_admin_manage_stacks.xml10(para) +#: ./doc/user-guide-admin/section_cli_admin_manage_stacks.xml11(para) +msgid "" +"Templates are used to create stacks, which are collections of resources. For" +" example, a stack might include instances, floating IPs, volumes, security " +"groups, or users. The Orchestration service offers access to all OpenStack " +"core services via a single modular template, with additional orchestration " +"capabilities such as auto-scaling and basic high availability." +msgstr "" + +#: ./doc/user-guide-admin/section_dashboard_admin_manage_stacks.xml14(para) +msgid "For information about:" +msgstr "" + +#: ./doc/user-guide-admin/section_dashboard_admin_manage_stacks.xml19(para) +msgid "" +"There are no administration-specific tasks that can be done through the " +"dashboard." +msgstr "" + +#: ./doc/user-guide-admin/section_dashboard_admin_manage_stacks.xml18(para) +msgid "" +"Administrative tasks on the command line, see . " +msgstr "" + +#: ./doc/user-guide-admin/section_dashboard_admin_manage_stacks.xml22(para) +msgid "" +"The basic creation and deletion of Orchestration stacks, refer to the End User Guide." +msgstr "" + +#: ./doc/user-guide-admin/section_dashboard_admin_manage_volumes.xml14(title) +msgid "Manage volumes and volume types" +msgstr "" + +#: ./doc/user-guide-admin/section_dashboard_admin_manage_volumes.xml15(para) +msgid "" +"Volumes are the Block Storage devices that you attach to instances to enable" +" persistent storage. Users can attach a volume to a running instance or " +"detach a volume and attach it to another instance at any time. For " +"information about using the dashboard to create and manage volumes as an end" +" user, see the OpenStack End User Guide." +msgstr "" + +#: ./doc/user-guide-admin/section_dashboard_admin_manage_volumes.xml24(para) +msgid "" +"As an administrative user, you can manage volumes and volume types for users" +" in various projects. You can create and delete volume types, and you can " +"view and delete volumes." +msgstr "" + +#: ./doc/user-guide-admin/section_dashboard_admin_manage_volumes.xml28(title) +msgid "Create a volume type" +msgstr "" + +#: ./doc/user-guide-admin/section_dashboard_admin_manage_volumes.xml31(para) +#: ./doc/user-guide-admin/section_dashboard_admin_manage_volumes.xml58(para) +#: ./doc/user-guide-admin/section_dashboard_admin_manage_volumes.xml93(para) +#: ./doc/user-guide-admin/section_dashboard_admin_manage_instances.xml28(para) +#: ./doc/user-guide-admin/section_dashboard_admin_manage_instances.xml67(para) +#: ./doc/user-guide-admin/section_dashboard_admin_manage_instances.xml111(para) +#: ./doc/user-guide-admin/section_dashboard_admin_manage_projects_users.xml66(para) +#: ./doc/user-guide-admin/section_dashboard_admin_manage_projects_users.xml225(para) +msgid "" +"Log in to the dashboard and choose the admin project " +"from the CURRENT PROJECT drop-down list." +msgstr "" + +#: ./doc/user-guide-admin/section_dashboard_admin_manage_volumes.xml37(para) +#: ./doc/user-guide-admin/section_dashboard_admin_manage_volumes.xml64(para) +#: ./doc/user-guide-admin/section_dashboard_admin_manage_volumes.xml99(para) +msgid "" +"On the Admin tab, click the " +"Volumes category." +msgstr "" + +#: ./doc/user-guide-admin/section_dashboard_admin_manage_volumes.xml41(para) +msgid "Click Create Volume Type." +msgstr "" + +#: ./doc/user-guide-admin/section_dashboard_admin_manage_volumes.xml43(para) +msgid "" +"In the Create Volume Type window, enter a name for the " +"volume type." +msgstr "" + +#: ./doc/user-guide-admin/section_dashboard_admin_manage_volumes.xml47(para) +msgid "" +"Click Create Volume Type to confirm your changes." +msgstr "" + +#: ./doc/user-guide-admin/section_dashboard_admin_manage_volumes.xml53(title) +msgid "Delete volume types" +msgstr "" + +#: ./doc/user-guide-admin/section_dashboard_admin_manage_volumes.xml54(para) +msgid "When you delete a volume type, volumes of that type are not deleted." +msgstr "" + +#: ./doc/user-guide-admin/section_dashboard_admin_manage_volumes.xml68(para) +msgid "Select the volume type or types that you want to delete." +msgstr "" + +#: ./doc/user-guide-admin/section_dashboard_admin_manage_volumes.xml72(para) +msgid "Click Delete Volume Types." +msgstr "" + +#: ./doc/user-guide-admin/section_dashboard_admin_manage_volumes.xml76(para) +msgid "" +"In the Confirm Delete Volume Types window, click " +"Delete Volume Types to confirm the action." +msgstr "" + +#: ./doc/user-guide-admin/section_dashboard_admin_manage_volumes.xml82(para) +#: ./doc/user-guide-admin/section_dashboard_admin_manage_volumes.xml117(para) +msgid "A message indicates whether the action succeeded." +msgstr "" + +#: ./doc/user-guide-admin/section_dashboard_admin_manage_volumes.xml88(title) +msgid "Delete volumes" +msgstr "" + +#: ./doc/user-guide-admin/section_dashboard_admin_manage_volumes.xml89(para) +msgid "" +"When you delete an instance, the data of its attached volumes is not " +"destroyed." +msgstr "" + +#: ./doc/user-guide-admin/section_dashboard_admin_manage_volumes.xml103(para) +msgid "Select the volume or volumes that you want to delete." +msgstr "" + +#: ./doc/user-guide-admin/section_dashboard_admin_manage_volumes.xml107(para) +msgid "Click Delete Volumes." +msgstr "" + +#: ./doc/user-guide-admin/section_dashboard_admin_manage_volumes.xml111(para) +msgid "" +"In the Confirm Delete Volumes window, click " +"Delete Volumes to confirm the action." +msgstr "" + +#: ./doc/user-guide-admin/section_cli_nova_manage_flavors.xml7(title) +#: ./doc/user-guide-admin/section_dashboard_admin_manage_flavors.xml7(title) +msgid "Manage flavors" +msgstr "" + +#: ./doc/user-guide-admin/section_cli_nova_manage_flavors.xml8(para) +msgid "" +"In OpenStack, flavors define the compute, memory, and storage capacity of " +"nova computing instances. To put it simply, a flavor is an available " +"hardware configuration for a server. It defines the size of a" +" virtual server that can be launched." +msgstr "" + +#: ./doc/user-guide-admin/section_cli_nova_manage_flavors.xml13(para) +#: ./doc/user-guide-admin/section_dashboard_admin_manage_flavors.xml14(para) +msgid "A flavor consists of the following parameters:" +msgstr "" + +#: ./doc/user-guide-admin/section_cli_nova_manage_flavors.xml16(term) +msgid "Flavor ID" +msgstr "" + +#: ./doc/user-guide-admin/section_cli_nova_manage_flavors.xml18(para) +msgid "" +"Automatically generated by OpenStack. For private flavors, a value from 1 to" +" 255." +msgstr "" + +#: ./doc/user-guide-admin/section_cli_nova_manage_flavors.xml23(term) +#: ./doc/user-guide-admin/section_cli_keystone_manage_projects_users_roles.xml43(para) +#: ./doc/user-guide-admin/section_dashboard_admin_manage_flavors.xml139(guilabel) +#: ./doc/user-guide-admin/section_dashboard_admin_manage_images.xml48(guilabel) +msgid "Name" +msgstr "" + +#: ./doc/user-guide-admin/section_cli_nova_manage_flavors.xml25(para) +msgid "Name for the new flavor." +msgstr "" + +#: ./doc/user-guide-admin/section_cli_nova_manage_flavors.xml29(term) +#: ./doc/user-guide-admin/section_dashboard_admin_manage_flavors.xml36(para) +#: ./doc/user-guide-admin/section_dashboard_admin_manage_flavors.xml147(guilabel) +#: ./doc/user-guide-admin/section_dashboard_admin_set_quotas.xml129(para) +msgid "VCPUs" +msgstr "" + +#: ./doc/user-guide-admin/section_cli_nova_manage_flavors.xml31(para) +#: ./doc/user-guide-admin/section_dashboard_admin_manage_flavors.xml39(para) +msgid "Number of virtual CPUs to use." +msgstr "" + +#: ./doc/user-guide-admin/section_cli_nova_manage_flavors.xml35(term) +msgid "Memory MB" +msgstr "" + +#: ./doc/user-guide-admin/section_cli_nova_manage_flavors.xml37(para) +msgid "Amount of RAM to use (in megabytes)." +msgstr "" + +#: ./doc/user-guide-admin/section_cli_nova_manage_flavors.xml41(term) +#: ./doc/user-guide-admin/section_dashboard_admin_manage_flavors.xml166(guilabel) +msgid "Root Disk GB" +msgstr "" + +#: ./doc/user-guide-admin/section_cli_nova_manage_flavors.xml43(para) +#: ./doc/user-guide-admin/section_dashboard_admin_manage_flavors.xml55(para) +msgid "Amount of disk space (in gigabytes) to use for the root (/) partition." +msgstr "" + +#: ./doc/user-guide-admin/section_cli_nova_manage_flavors.xml48(term) +#: ./doc/user-guide-admin/section_dashboard_admin_manage_flavors.xml177(guilabel) +msgid "Ephemeral Disk GB" +msgstr "" + +#: ./doc/user-guide-admin/section_cli_nova_manage_flavors.xml50(para) +#: ./doc/user-guide-admin/section_dashboard_admin_manage_flavors.xml64(para) +msgid "" +"Amount of disk space (in gigabytes) to use for the ephemeral partition. If " +"unspecified, the value is 0 by default." +msgstr "" + +#: ./doc/user-guide-admin/section_cli_nova_manage_flavors.xml53(para) +#: ./doc/user-guide-admin/section_dashboard_admin_manage_flavors.xml67(para) +#: ./doc/user-guide-admin/section_dashboard_admin_manage_flavors.xml186(para) +msgid "" +"Ephemeral disks offer machine local disk storage linked to the life cycle of" +" a VM instance. When a VM is terminated, all data on the ephemeral disk is " +"lost. Ephemeral disks are not included in any snapshots." +msgstr "" + +#: ./doc/user-guide-admin/section_cli_nova_manage_flavors.xml61(term) +msgid "Swap" +msgstr "" + +#: ./doc/user-guide-admin/section_cli_nova_manage_flavors.xml63(para) +msgid "" +"Amount of swap space (in megabytes) to use. If unspecified, the value is 0 " +"by default." +msgstr "" + +#: ./doc/user-guide-admin/section_cli_nova_manage_flavors.xml68(para) +#: ./doc/user-guide-admin/section_dashboard_admin_manage_flavors.xml94(para) +msgid "The default flavors are:" +msgstr "" + +#: ./doc/user-guide-admin/section_cli_nova_manage_flavors.xml71(para) +#: ./doc/user-guide-admin/section_dashboard_admin_manage_flavors.xml97(para) +msgid "m1.tiny (1 VCPU/0 GB Disk/512 MB RAM)" +msgstr "" + +#: ./doc/user-guide-admin/section_cli_nova_manage_flavors.xml74(para) +msgid "m1.smaller (1 VCPU/0 GB Disk/1024 MB RAM)" +msgstr "" + +#: ./doc/user-guide-admin/section_cli_nova_manage_flavors.xml77(para) +msgid "m1.small (1 VCPU/10 GB Disk/2048 MB RAM)" +msgstr "" + +#: ./doc/user-guide-admin/section_cli_nova_manage_flavors.xml80(para) +msgid "m1.medium (2 VCPU/10 GB Disk/3072 MB RAM)" +msgstr "" + +#: ./doc/user-guide-admin/section_cli_nova_manage_flavors.xml83(para) +msgid "m1.large (4 VCPU/10 GB Disk/8192 MB RAM)" +msgstr "" + +#: ./doc/user-guide-admin/section_cli_nova_manage_flavors.xml86(para) +msgid "m1.xlarge (8 VCPU/10 GB Disk/8192 MB RAM)" +msgstr "" + +#: ./doc/user-guide-admin/section_cli_nova_manage_flavors.xml89(para) +msgid "" +"You can create and manage flavors with the nova commands " +"provided by the python-novaclient package." +msgstr "" + +#: ./doc/user-guide-admin/section_cli_nova_manage_flavors.xml93(title) +msgid "Create a flavor" +msgstr "" + +#: ./doc/user-guide-admin/section_cli_nova_manage_flavors.xml96(para) +msgid "" +"List flavors to show the ID and name, the amount of memory, the amount of " +"disk space for the root partition and for the ephemeral partition, the swap," +" and the number of virtual CPUs for each flavor." +msgstr "" + +#: ./doc/user-guide-admin/section_cli_nova_manage_flavors.xml105(para) +msgid "" +"To create a flavor, specify a name, ID, RAM size, disk size, and the number " +"of VCPUs for the flavor, as follows:" +msgstr "" + +#: ./doc/user-guide-admin/section_cli_nova_manage_flavors.xml108(replaceable) +msgid "FLAVOR_NAME" +msgstr "" + +#: ./doc/user-guide-admin/section_cli_nova_manage_flavors.xml108(replaceable) +#: ./doc/user-guide-admin/section_cli_nova_manage_flavors.xml131(replaceable) +msgid "FLAVOR_ID" +msgstr "" + +#: ./doc/user-guide-admin/section_cli_nova_manage_flavors.xml108(replaceable) +msgid "RAM_IN_MB ROOT_DISK_IN_GB" +msgstr "" + +#: ./doc/user-guide-admin/section_cli_nova_manage_flavors.xml108(replaceable) +msgid "NUMBER_OF_VCPUS" +msgstr "" + +#: ./doc/user-guide-admin/section_cli_nova_manage_flavors.xml110(para) +msgid "" +"The flavor ID is a number from 1 to 255 and cannot contain special " +"characters or spaces." +msgstr "" + +#: ./doc/user-guide-admin/section_cli_nova_manage_flavors.xml114(para) +msgid "For a list of optional parameters, run this command:" +msgstr "" + +#: ./doc/user-guide-admin/section_cli_nova_manage_flavors.xml119(para) +msgid "" +"After you create a flavor, assign it to a project by specifying the flavor " +"name or ID and the tenant ID:" +msgstr "" + +#: ./doc/user-guide-admin/section_cli_nova_manage_flavors.xml122(replaceable) +msgid "FLAVOR" +msgstr "" + +#: ./doc/user-guide-admin/section_cli_nova_manage_flavors.xml122(replaceable) +#: ./doc/user-guide-admin/section_cli_keystone_manage_projects_users_roles.xml347(replaceable) +#: ./doc/user-guide-admin/section_cli_keystone_manage_projects_users_roles.xml351(replaceable) +#: ./doc/user-guide-admin/section_cli_keystone_manage_projects_users_roles.xml371(replaceable) +#: ./doc/user-guide-admin/section_cli_keystone_manage_projects_users_roles.xml376(replaceable) +msgid "TENANT_ID" +msgstr "" + +#: ./doc/user-guide-admin/section_cli_nova_manage_flavors.xml127(title) +msgid "Delete a flavor" +msgstr "" + +#: ./doc/user-guide-admin/section_cli_nova_manage_flavors.xml130(para) +msgid "Delete a specified flavor, as follows:" +msgstr "" + +#: ./doc/user-guide-admin/bk-admin-user-guide.xml12(title) +msgid "OpenStack Admin User Guide" +msgstr "" + +#: ./doc/user-guide-admin/bk-admin-user-guide.xml13(titleabbrev) +msgid "Admin User Guide" +msgstr "" + +#: ./doc/user-guide-admin/bk-admin-user-guide.xml21(orgname) +#: ./doc/user-guide-admin/bk-admin-user-guide.xml26(holder) +msgid "OpenStack Foundation" +msgstr "" + +#: ./doc/user-guide-admin/bk-admin-user-guide.xml25(year) +msgid "2013" +msgstr "" + +#: ./doc/user-guide-admin/bk-admin-user-guide.xml28(releaseinfo) +msgid "havana" +msgstr "" + +#: ./doc/user-guide-admin/bk-admin-user-guide.xml29(productname) +msgid "OpenStack" +msgstr "" + +#: ./doc/user-guide-admin/bk-admin-user-guide.xml33(remark) +msgid "Copyright details are filled in by the template." +msgstr "" + +#: ./doc/user-guide-admin/bk-admin-user-guide.xml38(para) +msgid "" +"OpenStack is an open source cloud computing platform for public and private " +"clouds. A series of interrelated projects deliver a cloud infrastructure " +"solution. This guide shows OpenStack admin users how to create and manage " +"resources in an OpenStack cloud with the OpenStack dashboard or OpenStack " +"client commands." +msgstr "" + +#: ./doc/user-guide-admin/bk-admin-user-guide.xml48(date) +msgid "2013-10-17" +msgstr "" + +#: ./doc/user-guide-admin/bk-admin-user-guide.xml52(para) +msgid "Havana release." +msgstr "" + +#: ./doc/user-guide-admin/bk-admin-user-guide.xml58(date) +msgid "2013-08-31" +msgstr "" + +#: ./doc/user-guide-admin/bk-admin-user-guide.xml62(para) +msgid "First edition of this document." +msgstr "" + +#: ./doc/user-guide-admin/section_cli_nova_floating_ips.xml6(title) +msgid "Manage IP addresses" +msgstr "" + +#: ./doc/user-guide-admin/section_cli_nova_floating_ips.xml7(para) +msgid "" +"Each instance can have a private, or fixed, IP address and an IP address, often " +"public, that is movable from instance to instance called a floating IP address." +msgstr "" + +#: ./doc/user-guide-admin/section_cli_nova_floating_ips.xml12(para) +msgid "" +"Private IP addresses are used for communication between instances and public" +" ones are used for communication with the outside world." +msgstr "" + +#: ./doc/user-guide-admin/section_cli_nova_floating_ips.xml15(para) +msgid "" +"When you launch an instance, it is automatically assigned a private IP " +"address that stays the same until you explicitly terminate the instance. " +"Rebooting an instance has no effect on its private IP address." +msgstr "" + +#: ./doc/user-guide-admin/section_cli_nova_floating_ips.xml19(para) +msgid "" +"The cloud operator must configure a pool of floating IP addresses. Then, you" +" can allocate a certain number of floating IP addresses from this pool to a " +"project. A project quota defines the maximum number of floating IP addresses" +" for the project." +msgstr "" + +#: ./doc/user-guide-admin/section_cli_nova_floating_ips.xml24(para) +msgid "" +"You can add a floating IP address from this pool to an instance in the " +"project. You can dynamically associate floating IP addresses with or " +"disassociate floating IP addresses from instances in the same project at any" +" time." +msgstr "" + +#: ./doc/user-guide-admin/section_cli_nova_floating_ips.xml29(para) +msgid "" +"Before you can assign a floating IP address to an instance, you must " +"allocate floating IP addresses to a project. After you allocate floating IP " +"addresses to the current project, you can assign them to running instances." +msgstr "" + +#: ./doc/user-guide-admin/section_cli_nova_floating_ips.xml33(para) +msgid "" +"You can assign one floating IP address to only one instance at a time. Use " +"the commands to manage floating IP addresses." +msgstr "" + +#: ./doc/user-guide-admin/section_cli_nova_floating_ips.xml37(title) +msgid "To manage floating IP addresses" +msgstr "" + +#: ./doc/user-guide-admin/section_cli_nova_floating_ips.xml39(para) +msgid "To list the floating IP address pools:" +msgstr "" + +#: ./doc/user-guide-admin/section_cli_nova_floating_ips.xml48(para) +msgid "" +"If this list is empty, the cloud operator must configure a pool of floating " +"IP addresses." +msgstr "" + +#: ./doc/user-guide-admin/section_cli_nova_floating_ips.xml53(para) +msgid "To allocate a floating IP address to the current project:" +msgstr "" + +#: ./doc/user-guide-admin/section_cli_nova_floating_ips.xml61(para) +msgid "" +"By default, the floating IP address is allocated from the " +"public pool. The command shows the allocated IP address." +msgstr "" + +#: ./doc/user-guide-admin/section_cli_nova_floating_ips.xml64(para) +msgid "" +"If more than one IP address pool is available, you can specify the pool from" +" which to allocate the address:" +msgstr "" + +#: ./doc/user-guide-admin/section_cli_nova_floating_ips.xml67(replaceable) +msgid "POOL_NAME" +msgstr "" + +#: ./doc/user-guide-admin/section_cli_nova_floating_ips.xml70(para) +msgid "" +"To list floating IP addresses that are allocated to the current project:" +msgstr "" + +#: ./doc/user-guide-admin/section_cli_nova_floating_ips.xml79(para) +msgid "" +"For each floating IP address that is allocated to the current project, the " +"command shows the floating IP address, the ID for the instance to which the " +"floating IP address is assigned, the associated fixed IP address, and the " +"pool from which the floating IP address was allocated." +msgstr "" + +#: ./doc/user-guide-admin/section_cli_nova_floating_ips.xml87(para) +msgid "" +"To associate a floating IP address with an instance, first allocate that " +"address to the current project:" +msgstr "" + +#: ./doc/user-guide-admin/section_cli_nova_floating_ips.xml96(para) +msgid "List instances to get the instance ID:" +msgstr "" + +#: ./doc/user-guide-admin/section_cli_nova_floating_ips.xml103(para) +msgid "Then, assign the floating IP address to the instance, as follows:" +msgstr "" + +#: ./doc/user-guide-admin/section_cli_nova_floating_ips.xml106(para) +msgid "" +"Notice that the instance is now associated with two floating IP addresses:" +msgstr "" + +#: ./doc/user-guide-admin/section_cli_nova_floating_ips.xml114(para) +msgid "" +"To assign a fixed IP address to a floating IP address that you assign to an " +"instance, add the fixed IP address as an optional parameter:" +msgstr "" + +#: ./doc/user-guide-admin/section_cli_nova_floating_ips.xml117(replaceable) +msgid "FIXED_IP_ADDRESS" +msgstr "" + +#: ./doc/user-guide-admin/section_cli_nova_floating_ips.xml117(replaceable) +msgid "INSTANCE_NAME_OR_ID" +msgstr "" + +#: ./doc/user-guide-admin/section_cli_nova_floating_ips.xml117(replaceable) +#: ./doc/user-guide-admin/section_cli_nova_floating_ips.xml126(replaceable) +msgid "FLOATING_IP_ADDRESS" +msgstr "" + +#: ./doc/user-guide-admin/section_cli_nova_floating_ips.xml118(para) +msgid "" +"After you assign the floating IP address and configure security group rules " +"for the instance, the instance is publicly available at the floating IP " +"address." +msgstr "" + +#: ./doc/user-guide-admin/section_cli_nova_floating_ips.xml124(para) +msgid "To release a floating IP address from the current project:" +msgstr "" + +#: ./doc/user-guide-admin/section_cli_nova_floating_ips.xml127(para) +msgid "" +"The floating IP address is returned to the floating IP address pool that is " +"available to all projects. If a floating IP address is assigned to a running" +" instance, it is automatically disassociated from that instance." +msgstr "" + +#: ./doc/user-guide-admin/section_cli_keystone_manage_projects_users_roles.xml7(title) +msgid "Manage projects, users, and roles" +msgstr "" + +#: ./doc/user-guide-admin/section_cli_keystone_manage_projects_users_roles.xml8(para) +msgid "" +"As a cloud administrator, you manage projects, users, and roles. Projects " +"are organizational units in the cloud to which you can assign users. " +"Projects are also known as tenants or " +"accounts. Users can be members of one " +"or more projects. Roles define which actions users can perform. You assign " +"roles to user-project pairs." +msgstr "" + +#: ./doc/user-guide-admin/section_cli_keystone_manage_projects_users_roles.xml15(para) +msgid "" +"You can define actions for OpenStack service roles in the " +"/etc/PROJECT/policy.json " +"files. For example, define actions for Compute service roles in the " +"/etc/nova/policy.json file." +msgstr "" + +#: ./doc/user-guide-admin/section_cli_keystone_manage_projects_users_roles.xml19(para) +msgid "" +"You can manage projects, users, and roles independently from each other." +msgstr "" + +#: ./doc/user-guide-admin/section_cli_keystone_manage_projects_users_roles.xml21(para) +msgid "" +"During cloud set up, the operator defines at least one project, user, and " +"role." +msgstr "" + +#: ./doc/user-guide-admin/section_cli_keystone_manage_projects_users_roles.xml23(para) +msgid "" +"Learn how to add, update, and delete projects and users, assign users to one" +" or more projects, and change or remove the assignment. To enable or " +"temporarily disable a project or user, you update that project or user. You " +"can also change quotas at the project level." +msgstr "" + +#: ./doc/user-guide-admin/section_cli_keystone_manage_projects_users_roles.xml28(para) +msgid "" +"Before you can delete a user account, you must remove the user account from " +"its primary project." +msgstr "" + +#: ./doc/user-guide-admin/section_cli_keystone_manage_projects_users_roles.xml30(para) +msgid "" +"Before you can run keystone client commands, you must download and source an" +" OpenStack RC file. See Download and source the OpenStack RC " +"file." +msgstr "" + +#: ./doc/user-guide-admin/section_cli_keystone_manage_projects_users_roles.xml35(title) +msgid "Services" +msgstr "" + +#: ./doc/user-guide-admin/section_cli_keystone_manage_projects_users_roles.xml36(para) +msgid "To look at your service catalog, use these keystone client commands." +msgstr "" + +#: ./doc/user-guide-admin/section_cli_keystone_manage_projects_users_roles.xml39(literal) +msgid "service-create" +msgstr "" + +#: ./doc/user-guide-admin/section_cli_keystone_manage_projects_users_roles.xml40(para) +msgid "Keyword arguments:" +msgstr "" + +#: ./doc/user-guide-admin/section_cli_keystone_manage_projects_users_roles.xml46(para) +msgid "Type" +msgstr "" + +#: ./doc/user-guide-admin/section_cli_keystone_manage_projects_users_roles.xml49(para) +#: ./doc/user-guide-admin/section_dashboard_admin_manage_flavors.xml22(th) +#: ./doc/user-guide-admin/section_dashboard_admin_manage_images.xml52(guilabel) +msgid "Description" +msgstr "" + +#: ./doc/user-guide-admin/section_cli_keystone_manage_projects_users_roles.xml52(para) +#: ./doc/user-guide-admin/section_cli_keystone_manage_projects_users_roles.xml67(para) +#: ./doc/user-guide-admin/section_cli_keystone_manage_projects_users_roles.xml78(para) +#: ./doc/user-guide-admin/section_cli_keystone_manage_projects_users_roles.xml89(para) +msgid "Example:" +msgstr "" + +#: ./doc/user-guide-admin/section_cli_keystone_manage_projects_users_roles.xml60(literal) +msgid "service-list" +msgstr "" + +#: ./doc/user-guide-admin/section_cli_keystone_manage_projects_users_roles.xml61(para) +#: ./doc/user-guide-admin/section_cli_keystone_manage_projects_users_roles.xml72(para) +#: ./doc/user-guide-admin/section_cli_keystone_manage_projects_users_roles.xml83(para) +msgid "Arguments" +msgstr "" + +#: ./doc/user-guide-admin/section_cli_keystone_manage_projects_users_roles.xml64(para) +#: ./doc/user-guide-admin/section_cli_keystone_manage_projects_users_roles.xml75(para) +#: ./doc/user-guide-admin/section_cli_keystone_manage_projects_users_roles.xml86(para) +msgid "service_id" +msgstr "" + +#: ./doc/user-guide-admin/section_cli_keystone_manage_projects_users_roles.xml71(literal) +msgid "service-get" +msgstr "" + +#: ./doc/user-guide-admin/section_cli_keystone_manage_projects_users_roles.xml82(literal) +msgid "service-delete" +msgstr "" + +#: ./doc/user-guide-admin/section_cli_keystone_manage_projects_users_roles.xml93(title) +msgid "Create a tenant (project)" +msgstr "" + +#: ./doc/user-guide-admin/section_cli_keystone_manage_projects_users_roles.xml94(para) +msgid "" +"A tenant is a group of zero or more users. In nova, a tenant owns virtual " +"machines. In swift, a tenant owns containers. In the Dashboard, tenants are " +"represented as projects. Users can be associated with more than one tenant. " +"Each tenant and user pairing can have a role associated with it." +msgstr "" + +#: ./doc/user-guide-admin/section_cli_keystone_manage_projects_users_roles.xml102(para) +msgid "" +"To list all projects with their ID, name, and whether they are enabled or " +"disabled:" +msgstr "" + +#: ./doc/user-guide-admin/section_cli_keystone_manage_projects_users_roles.xml118(para) +msgid "Create a project named new-project:" +msgstr "" + +#: ./doc/user-guide-admin/section_cli_keystone_manage_projects_users_roles.xml121(para) +msgid "By default, the project is enabled." +msgstr "" + +#: ./doc/user-guide-admin/section_cli_keystone_manage_projects_users_roles.xml130(para) +msgid "" +"Note the ID for the project so you can update it in the next procedure." +msgstr "" + +#: ./doc/user-guide-admin/section_cli_keystone_manage_projects_users_roles.xml136(title) +#: ./doc/user-guide-admin/section_dashboard_admin_manage_projects_users.xml104(title) +msgid "Update a project" +msgstr "" + +#: ./doc/user-guide-admin/section_cli_keystone_manage_projects_users_roles.xml137(para) +msgid "" +"Specify the project ID to update a project. You can update the name, " +"description, and enabled status of a project." +msgstr "" + +#: ./doc/user-guide-admin/section_cli_keystone_manage_projects_users_roles.xml142(para) +msgid "To temporarily disable a project:" +msgstr "" + +#: ./doc/user-guide-admin/section_cli_keystone_manage_projects_users_roles.xml143(replaceable) +#: ./doc/user-guide-admin/section_cli_keystone_manage_projects_users_roles.xml147(replaceable) +#: ./doc/user-guide-admin/section_cli_keystone_manage_projects_users_roles.xml151(replaceable) +#: ./doc/user-guide-admin/section_cli_keystone_manage_projects_users_roles.xml156(replaceable) +#: ./doc/user-guide-admin/section_cli_keystone_manage_projects_users_roles.xml173(replaceable) +msgid "PROJECT_ID" +msgstr "" + +#: ./doc/user-guide-admin/section_cli_keystone_manage_projects_users_roles.xml146(para) +msgid "To enable a disabled project:" +msgstr "" + +#: ./doc/user-guide-admin/section_cli_keystone_manage_projects_users_roles.xml150(para) +msgid "To update the name of a project:" +msgstr "" + +#: ./doc/user-guide-admin/section_cli_keystone_manage_projects_users_roles.xml154(para) +msgid "To verify your changes, show information for the updated project:" +msgstr "" + +#: ./doc/user-guide-admin/section_cli_keystone_manage_projects_users_roles.xml169(title) +msgid "Delete a project" +msgstr "" + +#: ./doc/user-guide-admin/section_cli_keystone_manage_projects_users_roles.xml172(para) +msgid "To delete a project:" +msgstr "" + +#: ./doc/user-guide-admin/section_cli_keystone_manage_projects_users_roles.xml178(title) +msgid "Create a user" +msgstr "" + +#: ./doc/user-guide-admin/section_cli_keystone_manage_projects_users_roles.xml181(para) +msgid "To list all users:" +msgstr "" + +#: ./doc/user-guide-admin/section_cli_keystone_manage_projects_users_roles.xml183(para) +msgid "" +"The output shows the ID, name, enabled status, and e-mail address for each " +"user:" +msgstr "" + +#: ./doc/user-guide-admin/section_cli_keystone_manage_projects_users_roles.xml196(para) +msgid "" +"To create a user, you must specify a name. Optionally, you can specify a " +"tenant ID, password, and email address. It is recommended that you include " +"the tenant ID and password because the user cannot log in to the dashboard " +"without this information." +msgstr "" + +#: ./doc/user-guide-admin/section_cli_keystone_manage_projects_users_roles.xml202(para) +msgid "To create the new-user user:" +msgstr "" + +#: ./doc/user-guide-admin/section_cli_keystone_manage_projects_users_roles.xml204(replaceable) +msgid "PASSWORD" +msgstr "" + +#: ./doc/user-guide-admin/section_cli_keystone_manage_projects_users_roles.xml218(title) +msgid "Update a user" +msgstr "" + +#: ./doc/user-guide-admin/section_cli_keystone_manage_projects_users_roles.xml219(para) +msgid "You can update the name, email address, and enabled status for a user." +msgstr "" + +#: ./doc/user-guide-admin/section_cli_keystone_manage_projects_users_roles.xml223(para) +msgid "To temporarily disable a user account:" +msgstr "" + +#: ./doc/user-guide-admin/section_cli_keystone_manage_projects_users_roles.xml225(replaceable) +#: ./doc/user-guide-admin/section_cli_keystone_manage_projects_users_roles.xml233(replaceable) +#: ./doc/user-guide-admin/section_cli_keystone_manage_projects_users_roles.xml238(replaceable) +#: ./doc/user-guide-admin/section_cli_keystone_manage_projects_users_roles.xml248(replaceable) +#: ./doc/user-guide-admin/section_cli_keystone_manage_projects_users_roles.xml347(replaceable) +#: ./doc/user-guide-admin/section_cli_keystone_manage_projects_users_roles.xml351(replaceable) +#: ./doc/user-guide-admin/section_cli_keystone_manage_projects_users_roles.xml371(replaceable) +#: ./doc/user-guide-admin/section_cli_keystone_manage_projects_users_roles.xml376(replaceable) +msgid "USER_ID" +msgstr "" + +#: ./doc/user-guide-admin/section_cli_keystone_manage_projects_users_roles.xml226(para) +msgid "" +"If you disable a user account, the user cannot log in to the dashboard. " +"However, data for the user account is maintained, so you can enable the user" +" at any time." +msgstr "" + +#: ./doc/user-guide-admin/section_cli_keystone_manage_projects_users_roles.xml232(para) +msgid "To enable a disabled user account:" +msgstr "" + +#: ./doc/user-guide-admin/section_cli_keystone_manage_projects_users_roles.xml236(para) +msgid "To change the name and description for a user account:" +msgstr "" + +#: ./doc/user-guide-admin/section_cli_keystone_manage_projects_users_roles.xml244(title) +msgid "Delete a user" +msgstr "" + +#: ./doc/user-guide-admin/section_cli_keystone_manage_projects_users_roles.xml247(para) +msgid "To delete a specified user account:" +msgstr "" + +#: ./doc/user-guide-admin/section_cli_keystone_manage_projects_users_roles.xml253(title) +msgid "Create and assign a role" +msgstr "" + +#: ./doc/user-guide-admin/section_cli_keystone_manage_projects_users_roles.xml254(para) +msgid "" +"Users can be members of multiple projects. To assign users to multiple " +"projects, define a role and assign that role to a user-project pair." +msgstr "" + +#: ./doc/user-guide-admin/section_cli_keystone_manage_projects_users_roles.xml259(para) +msgid "To list the available roles:" +msgstr "" + +#: ./doc/user-guide-admin/section_cli_keystone_manage_projects_users_roles.xml272(para) +msgid "To create the new-role role:" +msgstr "" + +#: ./doc/user-guide-admin/section_cli_keystone_manage_projects_users_roles.xml283(para) +msgid "" +"To assign a user to a project, you must assign the role to a user-project " +"pair. To do this, you need the user, role, and project IDs." +msgstr "" + +#: ./doc/user-guide-admin/section_cli_keystone_manage_projects_users_roles.xml289(para) +msgid "To list users:" +msgstr "" + +#: ./doc/user-guide-admin/section_cli_keystone_manage_projects_users_roles.xml301(para) +msgid "Note the ID of the user to which you want to assign the role." +msgstr "" + +#: ./doc/user-guide-admin/section_cli_keystone_manage_projects_users_roles.xml305(para) +msgid "To list role IDs:" +msgstr "" + +#: ./doc/user-guide-admin/section_cli_keystone_manage_projects_users_roles.xml317(para) +msgid "Note the ID of the role that you want to assign." +msgstr "" + +#: ./doc/user-guide-admin/section_cli_keystone_manage_projects_users_roles.xml321(para) +msgid "To list projects:" +msgstr "" + +#: ./doc/user-guide-admin/section_cli_keystone_manage_projects_users_roles.xml335(para) +msgid "Note the ID of the project to which you want to assign the role." +msgstr "" + +#: ./doc/user-guide-admin/section_cli_keystone_manage_projects_users_roles.xml341(para) +msgid "" +"Assign a role to a user-project pair. In this example, you assign the " +"new-role role to the demo and test-project pair:" +msgstr "" + +#: ./doc/user-guide-admin/section_cli_keystone_manage_projects_users_roles.xml347(replaceable) +#: ./doc/user-guide-admin/section_cli_keystone_manage_projects_users_roles.xml360(replaceable) +#: ./doc/user-guide-admin/section_cli_keystone_manage_projects_users_roles.xml371(replaceable) +msgid "ROLE_ID" +msgstr "" + +#: ./doc/user-guide-admin/section_cli_keystone_manage_projects_users_roles.xml350(para) +msgid "To verify the role assignment:" +msgstr "" + +#: ./doc/user-guide-admin/section_cli_keystone_manage_projects_users_roles.xml359(para) +msgid "To get details for a specified role:" +msgstr "" + +#: ./doc/user-guide-admin/section_cli_keystone_manage_projects_users_roles.xml369(para) +msgid "To remove a role from a user-project pair:" +msgstr "" + +#: ./doc/user-guide-admin/section_cli_keystone_manage_projects_users_roles.xml374(para) +msgid "To verify the role removal, run the following command:" +msgstr "" + +#: ./doc/user-guide-admin/section_cli_keystone_manage_projects_users_roles.xml377(para) +msgid "If the role was removed, the command output omits the removed role." +msgstr "" + +#: ./doc/user-guide-admin/section_dashboard_admin_manage_resources.xml13(title) +msgid "View cloud resources" +msgstr "" + +#. When image changes, this message will be marked fuzzy or untranslated for +#. you. +#. It doesn't matter what you translate it to: it's not used at all. +#: ./doc/user-guide-admin/section_dashboard_admin_manage_instances.xml95(None) +msgid "" +"@@image: '../common/figures/change_instance_state.png'; " +"md5=d9eef0f7a1f99eee18a99e677c7c710b" +msgstr "" + +#: ./doc/user-guide-admin/section_dashboard_admin_manage_instances.xml13(title) +msgid "Manage instances" +msgstr "" + +#: ./doc/user-guide-admin/section_dashboard_admin_manage_instances.xml14(para) +msgid "" +"As an administrative user, you can manage instances for users in various " +"projects. You can view, terminate, edit, perform a soft or hard reboot, " +"create a snapshot from, and migrate instances. You can also view the logs " +"for instances or launch a VNC console for an instance." +msgstr "" + +#: ./doc/user-guide-admin/section_dashboard_admin_manage_instances.xml19(para) +msgid "" +"For information about using the dashboard to launch instances as an end " +"user, see the OpenStack End User Guide." +msgstr "" + +#: ./doc/user-guide-admin/section_dashboard_admin_manage_instances.xml25(title) +msgid "Create instance snapshots" +msgstr "" + +#: ./doc/user-guide-admin/section_dashboard_admin_manage_instances.xml34(para) +#: ./doc/user-guide-admin/section_dashboard_admin_manage_instances.xml73(para) +#: ./doc/user-guide-admin/section_dashboard_admin_manage_instances.xml117(para) +msgid "" +"On the Admin tab, click the " +"Instances category." +msgstr "" + +#: ./doc/user-guide-admin/section_dashboard_admin_manage_instances.xml39(para) +msgid "" +"Select an instance to create a snapshot from it. From the " +"Actions drop-down list, select Create " +"Snapshot." +msgstr "" + +#: ./doc/user-guide-admin/section_dashboard_admin_manage_instances.xml45(para) +msgid "" +"In the Create Snapshot window, enter a name for the " +"snapshot. Click Create Snapshot. The dashboard shows " +"the instance snapshot in the Images & Snapshots " +"category." +msgstr "" + +#: ./doc/user-guide-admin/section_dashboard_admin_manage_instances.xml53(para) +msgid "" +"To launch an instance from the snapshot, select the snapshot and click " +"Launch. For information about launching instances, " +"see the OpenStack End User Guide." +msgstr "" + +#: ./doc/user-guide-admin/section_dashboard_admin_manage_instances.xml64(title) +msgid "Control the state of an instance" +msgstr "" + +#: ./doc/user-guide-admin/section_dashboard_admin_manage_instances.xml78(para) +msgid "Select the instance for which you want to change the state." +msgstr "" + +#: ./doc/user-guide-admin/section_dashboard_admin_manage_instances.xml82(para) +msgid "" +"In the More drop-down list in the " +"Actions column, select the state." +msgstr "" + +#: ./doc/user-guide-admin/section_dashboard_admin_manage_instances.xml85(para) +msgid "" +"Depending on the current state of the instance, you can choose to pause, un-" +"pause, suspend, resume, soft or hard reboot, or terminate an instance (items" +" in red are disabled)." +msgstr "" + +#: ./doc/user-guide-admin/section_dashboard_admin_manage_instances.xml90(title) +msgid "Dashboard—Instance Actions" +msgstr "" + +#: ./doc/user-guide-admin/section_dashboard_admin_manage_instances.xml103(title) +msgid "Track usage" +msgstr "" + +#: ./doc/user-guide-admin/section_dashboard_admin_manage_instances.xml104(para) +msgid "" +"Use the Overview category to track usage of instances " +"for each project." +msgstr "" + +#: ./doc/user-guide-admin/section_dashboard_admin_manage_instances.xml106(para) +msgid "" +"You can track costs per month by showing metrics like number of VCPUs, " +"disks, RAM, and uptime of all your instances." +msgstr "" + +#: ./doc/user-guide-admin/section_dashboard_admin_manage_instances.xml122(para) +msgid "" +"Select a month and click Submit to query the instance" +" usage for that month." +msgstr "" + +#: ./doc/user-guide-admin/section_dashboard_admin_manage_instances.xml127(para) +msgid "" +"Click Download CSV Summary to download a CSV summary." +msgstr "" + +#: ./doc/user-guide-admin/section_cli_nova_services.xml6(title) +msgid "Manage Compute services" +msgstr "" + +#: ./doc/user-guide-admin/section_cli_nova_services.xml7(para) +msgid "" +"You can enable and disable Compute services. The following examples disable " +"and enable the nova-compute " +"service." +msgstr "" + +#: ./doc/user-guide-admin/section_cli_nova_services.xml12(para) +msgid "List the Compute services:" +msgstr "" + +#: ./doc/user-guide-admin/section_cli_nova_services.xml26(para) +msgid "Disable a nova service:" +msgstr "" + +#: ./doc/user-guide-admin/section_cli_nova_services.xml34(para) +msgid "" +"The Havana release introduces the optional --reason " +"parameter that enables you to log a reason for disabling a service." +msgstr "" + +#: ./doc/user-guide-admin/section_cli_nova_services.xml41(para) +#: ./doc/user-guide-admin/section_cli_nova_services.xml64(para) +msgid "Check the service list:" +msgstr "" + +#: ./doc/user-guide-admin/section_cli_nova_services.xml55(para) +msgid "Enable the service:" +msgstr "" + +#: ./doc/user-guide-admin/section_dashboard_admin_manage_projects_security.xml7(title) +#: ./doc/user-guide-admin/section_cli_nova_manage_projects_security.xml7(title) +msgid "Manage project security" +msgstr "" + +#: ./doc/user-guide-admin/section_dashboard_admin_manage_projects_security.xml8(para) +#: ./doc/user-guide-admin/section_cli_nova_manage_projects_security.xml8(para) +msgid "" +"Security groups are sets of IP filter rules that are applied to all project " +"instances, and which define networking access to the instance. Group rules " +"are project specific; project members can edit the default rules for their " +"group and add new rule sets." +msgstr "" + +#: ./doc/user-guide-admin/section_dashboard_admin_manage_projects_security.xml13(para) +msgid "" +"All projects have a default security group that is applied to any instance " +"that has no other defined security group. Unless you change the default, " +"this security group denies all incoming traffic and allows only outgoing " +"traffic to your instance." +msgstr "" + +#: ./doc/user-guide-admin/section_dashboard_admin_manage_projects_security.xml19(para) +msgid "" +"For information about updating global controls on the command line, see " +"." +msgstr "" + +#: ./doc/user-guide-admin/section_dashboard_admin_manage_projects_security.xml24(title) +#: ./doc/user-guide-admin/section_cli_nova_manage_projects_security.xml94(title) +msgid "Create a security group" +msgstr "" + +#: ./doc/user-guide-admin/section_dashboard_admin_manage_projects_security.xml27(para) +#: ./doc/user-guide-admin/section_dashboard_admin_manage_projects_security.xml55(para) +#: ./doc/user-guide-admin/section_dashboard_admin_manage_projects_security.xml244(para) +#: ./doc/user-guide-admin/section_dashboard_admin_manage_projects_security.xml269(para) +msgid "Log in to the dashboard as a project member." +msgstr "" + +#: ./doc/user-guide-admin/section_dashboard_admin_manage_projects_security.xml31(para) +#: ./doc/user-guide-admin/section_dashboard_admin_manage_projects_security.xml59(para) +#: ./doc/user-guide-admin/section_dashboard_admin_manage_projects_security.xml248(para) +msgid "" +"On the Project tab, select the appropriate project from" +" the CURRENT PROJECT drop-down list, and click the " +"Access & Security category." +msgstr "" + +#: ./doc/user-guide-admin/section_dashboard_admin_manage_projects_security.xml38(para) +msgid "" +"On the Security Groups tab, click Create " +"Security Group." +msgstr "" + +#: ./doc/user-guide-admin/section_dashboard_admin_manage_projects_security.xml43(para) +msgid "" +"Provide a name and appropriate description for the group, and click " +"Create Security Group. By default, the new rule " +"provides outgoing access rules for the group." +msgstr "" + +#: ./doc/user-guide-admin/section_dashboard_admin_manage_projects_security.xml52(title) +msgid "Add a security group rule" +msgstr "" + +#: ./doc/user-guide-admin/section_dashboard_admin_manage_projects_security.xml66(para) +#: ./doc/user-guide-admin/section_dashboard_admin_manage_projects_security.xml255(para) +msgid "" +"On the Security Groups tab, click Edit " +"rules for the appropriate security group." +msgstr "" + +#: ./doc/user-guide-admin/section_dashboard_admin_manage_projects_security.xml71(para) +msgid "" +"To add a rule, click Add Rule. Set the attributes for" +" the rule, and click Add:" +msgstr "" + +#: ./doc/user-guide-admin/section_dashboard_admin_manage_projects_security.xml114(guilabel) +msgid "IP Protocol" +msgstr "" + +#: ./doc/user-guide-admin/section_dashboard_admin_manage_projects_security.xml116(para) +msgid "The IP protocol to which the rule applies:" +msgstr "" + +#: ./doc/user-guide-admin/section_dashboard_admin_manage_projects_security.xml120(para) +msgid "" +"TCP.Typically used to exchange data between systems, " +"and for end-user communication." +msgstr "" + +#: ./doc/user-guide-admin/section_dashboard_admin_manage_projects_security.xml126(para) +msgid "" +"UDP. Typically used to exchange data between systems, " +"particularly at the application level." +msgstr "" + +#: ./doc/user-guide-admin/section_dashboard_admin_manage_projects_security.xml132(para) +msgid "" +"ICMP. Typically used by network devices, such as " +"routers, to send error or monitoring messages." +msgstr "" + +#: ./doc/user-guide-admin/section_dashboard_admin_manage_projects_security.xml154(guilabel) +msgid "Open" +msgstr "" + +#: ./doc/user-guide-admin/section_dashboard_admin_manage_projects_security.xml156(para) +msgid "" +"For TCP or UDP rules, the Port or Port " +"Range to open for the rule. Choose to open a single port or range" +" of ports." +msgstr "" + +#: ./doc/user-guide-admin/section_dashboard_admin_manage_projects_security.xml161(para) +msgid "" +"For a range of ports, enter port values in the From " +"Port and To Port fields." +msgstr "" + +#: ./doc/user-guide-admin/section_dashboard_admin_manage_projects_security.xml165(para) +msgid "" +"For a single port, enter the port value in the Port " +"field." +msgstr "" + +#: ./doc/user-guide-admin/section_dashboard_admin_manage_projects_security.xml202(guilabel) +msgid "Source" +msgstr "" + +#: ./doc/user-guide-admin/section_dashboard_admin_manage_projects_security.xml204(para) +msgid "The source of the traffic for this rule:" +msgstr "" + +#: ./doc/user-guide-admin/section_dashboard_admin_manage_projects_security.xml208(para) +msgid "" +"CIDR (Classless Inter-Domain Routing). IP address " +"block, which limits access to IPs within the block. Enter the CIDR in the " +"Source field." +msgstr "" + +#: ./doc/user-guide-admin/section_dashboard_admin_manage_projects_security.xml217(para) +msgid "" +"Security Group. Source group that enables any instance " +"in the group to access any other group instance." +msgstr "" + +#: ./doc/user-guide-admin/section_dashboard_admin_manage_projects_security.xml241(title) +msgid "Delete a security group rule" +msgstr "" + +#: ./doc/user-guide-admin/section_dashboard_admin_manage_projects_security.xml260(para) +msgid "" +"To delete a rule, select the rule and click Delete " +"Rule." +msgstr "" + +#: ./doc/user-guide-admin/section_dashboard_admin_manage_projects_security.xml266(title) +#: ./doc/user-guide-admin/section_cli_nova_manage_projects_security.xml165(title) +msgid "Delete a security group" +msgstr "" + +#: ./doc/user-guide-admin/section_dashboard_admin_manage_projects_security.xml273(para) +msgid "" +"On the Project tab, select the appropriate project from" +" the CURRENT PROJECT drop-down list, and click the " +"Access & Security category." +msgstr "" + +#: ./doc/user-guide-admin/section_dashboard_admin_manage_projects_security.xml280(para) +msgid "" +"On the Security Groups tab, select the appropriate " +"group, and click Delete Security Group." +msgstr "" + +#: ./doc/user-guide-admin/section_dashboard_admin_manage_flavors.xml8(para) +msgid "" +"In OpenStack, a flavor defines the compute, memory, and storage capacity of " +"a virtual server that users can launch. As an administrative user, you can " +"create, edit, and delete flavors." +msgstr "" + +#: ./doc/user-guide-admin/section_dashboard_admin_manage_flavors.xml12(para) +msgid "Only administrative users can create and manage flavors." +msgstr "" + +#: ./doc/user-guide-admin/section_dashboard_admin_manage_flavors.xml16(caption) +msgid "Flavor parameters" +msgstr "" + +#: ./doc/user-guide-admin/section_dashboard_admin_manage_flavors.xml21(th) +msgid "Parameter" +msgstr "" + +#: ./doc/user-guide-admin/section_dashboard_admin_manage_flavors.xml28(para) +msgid "Flavor Name" +msgstr "" + +#: ./doc/user-guide-admin/section_dashboard_admin_manage_flavors.xml31(para) +msgid "The flavor name." +msgstr "" + +#: ./doc/user-guide-admin/section_dashboard_admin_manage_flavors.xml44(para) +msgid "RAM" +msgstr "" + +#: ./doc/user-guide-admin/section_dashboard_admin_manage_flavors.xml47(para) +msgid "Amount of RAM to use, in megabytes." +msgstr "" + +#: ./doc/user-guide-admin/section_dashboard_admin_manage_flavors.xml52(para) +msgid "Root Disk" +msgstr "" + +#: ./doc/user-guide-admin/section_dashboard_admin_manage_flavors.xml61(para) +msgid "Ephemeral Disk" +msgstr "" + +#: ./doc/user-guide-admin/section_dashboard_admin_manage_flavors.xml76(para) +msgid "Swap Disk" +msgstr "" + +#: ./doc/user-guide-admin/section_dashboard_admin_manage_flavors.xml79(para) +msgid "" +"Amount of swap space (in megabytes) to use. If unspecified, the default is " +"0." +msgstr "" + +#: ./doc/user-guide-admin/section_dashboard_admin_manage_flavors.xml85(para) +msgid "ID" +msgstr "" + +#: ./doc/user-guide-admin/section_dashboard_admin_manage_flavors.xml88(para) +msgid "The flavor ID, generated by OpenStack." +msgstr "" + +#: ./doc/user-guide-admin/section_dashboard_admin_manage_flavors.xml100(para) +msgid "m1.small (1 VCPU/20 GB Disk/2048 MB RAM)" +msgstr "" + +#: ./doc/user-guide-admin/section_dashboard_admin_manage_flavors.xml103(para) +msgid "m1.medium (2 VCPU/40 GB Disk/4096 MB RAM)" +msgstr "" + +#: ./doc/user-guide-admin/section_dashboard_admin_manage_flavors.xml106(para) +msgid "m1.large (4 VCPU/80 GB Disk/8192 MB RAM)" +msgstr "" + +#: ./doc/user-guide-admin/section_dashboard_admin_manage_flavors.xml109(para) +msgid "m1.xlarge (8 VCPU/160 GB Disk/16384 MB RAM)" +msgstr "" + +#: ./doc/user-guide-admin/section_dashboard_admin_manage_flavors.xml113(title) +msgid "Create flavors" +msgstr "" + +#: ./doc/user-guide-admin/section_dashboard_admin_manage_flavors.xml116(para) +#: ./doc/user-guide-admin/section_dashboard_admin_manage_flavors.xml220(para) +#: ./doc/user-guide-admin/section_dashboard_admin_manage_flavors.xml248(para) +#: ./doc/user-guide-admin/section_dashboard_admin_manage_images.xml27(para) +#: ./doc/user-guide-admin/section_dashboard_admin_manage_images.xml95(para) +#: ./doc/user-guide-admin/section_dashboard_admin_manage_images.xml125(para) +msgid "Log in to the dashboard." +msgstr "" + +#: ./doc/user-guide-admin/section_dashboard_admin_manage_flavors.xml117(para) +#: ./doc/user-guide-admin/section_dashboard_admin_manage_flavors.xml221(para) +#: ./doc/user-guide-admin/section_dashboard_admin_manage_flavors.xml249(para) +#: ./doc/user-guide-admin/section_dashboard_admin_manage_images.xml28(para) +#: ./doc/user-guide-admin/section_dashboard_admin_manage_images.xml96(para) +#: ./doc/user-guide-admin/section_dashboard_admin_manage_images.xml126(para) +msgid "" +"Choose the admin project from the CURRENT " +"PROJECT drop-down list." +msgstr "" + +#: ./doc/user-guide-admin/section_dashboard_admin_manage_flavors.xml122(para) +#: ./doc/user-guide-admin/section_dashboard_admin_manage_flavors.xml226(para) +#: ./doc/user-guide-admin/section_dashboard_admin_manage_flavors.xml254(para) +msgid "" +"On the Admin tab, click the " +"Flavors category." +msgstr "" + +#: ./doc/user-guide-admin/section_dashboard_admin_manage_flavors.xml126(para) +#: ./doc/user-guide-admin/section_dashboard_admin_manage_flavors.xml211(para) +msgid "Click Create Flavor." +msgstr "" + +#: ./doc/user-guide-admin/section_dashboard_admin_manage_flavors.xml130(para) +msgid "" +"In the Create Flavor window, enter or select the " +"following values:" +msgstr "" + +#: ./doc/user-guide-admin/section_dashboard_admin_manage_flavors.xml142(para) +msgid "Enter the flavor name." +msgstr "" + +#: ./doc/user-guide-admin/section_dashboard_admin_manage_flavors.xml150(para) +msgid "Enter the number of virtual CPUs to use." +msgstr "" + +#: ./doc/user-guide-admin/section_dashboard_admin_manage_flavors.xml156(guilabel) +msgid "RAM MB" +msgstr "" + +#: ./doc/user-guide-admin/section_dashboard_admin_manage_flavors.xml160(para) +msgid "Enter the amount of RAM to use, in megabytes." +msgstr "" + +#: ./doc/user-guide-admin/section_dashboard_admin_manage_flavors.xml170(para) +msgid "" +"Enter the mount of disk space in gigabytes to use for the root (/) " +"partition." +msgstr "" + +#: ./doc/user-guide-admin/section_dashboard_admin_manage_flavors.xml181(para) +msgid "" +"Enter the amount of disk space in gigabytes to use for the ephemeral " +"partition. If unspecified, the value is 0 by default." +msgstr "" + +#: ./doc/user-guide-admin/section_dashboard_admin_manage_flavors.xml197(guilabel) +msgid "Swap Disk GB" +msgstr "" + +#: ./doc/user-guide-admin/section_dashboard_admin_manage_flavors.xml201(para) +msgid "" +"Enter the amount of swap space (in megabytes) to use. If unspecified, the " +"default is 0." +msgstr "" + +#: ./doc/user-guide-admin/section_dashboard_admin_manage_flavors.xml217(title) +msgid "Update flavors" +msgstr "" + +#: ./doc/user-guide-admin/section_dashboard_admin_manage_flavors.xml230(para) +msgid "" +"Select the flavor that you want to edit. Click Edit " +"Flavor." +msgstr "" + +#: ./doc/user-guide-admin/section_dashboard_admin_manage_flavors.xml234(para) +msgid "" +"In the Edit Flavor window, you can change the flavor " +"name, VCPUs, RAM, root dish, ephemeral disk, and swap disk values.." +msgstr "" + +#: ./doc/user-guide-admin/section_dashboard_admin_manage_flavors.xml240(para) +#: ./doc/user-guide-admin/section_dashboard_admin_manage_projects_users.xml132(para) +#: ./doc/user-guide-admin/section_dashboard_admin_manage_projects_users.xml197(para) +msgid "Click Save." +msgstr "" + +#: ./doc/user-guide-admin/section_dashboard_admin_manage_flavors.xml245(title) +msgid "Delete flavors" +msgstr "" + +#: ./doc/user-guide-admin/section_dashboard_admin_manage_flavors.xml258(para) +msgid "Select the flavors that you want to delete." +msgstr "" + +#: ./doc/user-guide-admin/section_dashboard_admin_manage_flavors.xml262(para) +msgid "Click Delete Flavors." +msgstr "" + +#: ./doc/user-guide-admin/section_dashboard_admin_manage_flavors.xml266(para) +msgid "" +"In the Confirm Delete Flavors window, click " +"Delete Flavors to confirm the deletion. You cannot " +"undo this action." +msgstr "" + +#: ./doc/user-guide-admin/section_cli_nova_manage_projects_security.xml13(para) +msgid "" +"All projects have a \"default\" security group which is applied to any " +"instance that has no other defined security group. Unless you change the " +"default, this security group denies all incoming traffic and allows only " +"outgoing traffic to your instance." +msgstr "" + +#: ./doc/user-guide-admin/section_cli_nova_manage_projects_security.xml19(para) +msgid "" +"For information about updating rules using the dashboard, see ." +msgstr "" + +#: ./doc/user-guide-admin/section_cli_nova_manage_projects_security.xml23(para) +msgid "" +"You can use the allow_same_net_traffic option in the " +"/etc/nova/nova.conf file to globally control whether " +"the rules applies to hosts which share a network." +msgstr "" + +#: ./doc/user-guide-admin/section_cli_nova_manage_projects_security.xml27(para) +msgid "If set to:" +msgstr "" + +#: ./doc/user-guide-admin/section_cli_nova_manage_projects_security.xml30(para) +msgid "" +"True (default), hosts on the same subnet are not filtered and " +"are allowed to pass all types of traffic between them. On a flat network, " +"this allows all instances from all projects unfiltered communication. With " +"VLAN networking, this allows access between instances within the same " +"project. You can also simulate this setting by configuring the default " +"security group to allow all traffic from the subnet." +msgstr "" + +#: ./doc/user-guide-admin/section_cli_nova_manage_projects_security.xml41(para) +msgid "False, security groups are enforced for all connections." +msgstr "" + +#: ./doc/user-guide-admin/section_cli_nova_manage_projects_security.xml45(para) +msgid "" +"Additionally, the number of maximum rules per security group is controlled " +"by the security_group_rules and the number of allowed security " +"groups per project is controlled by the security_groups quota " +"(see )." +msgstr "" + +#: ./doc/user-guide-admin/section_cli_nova_manage_projects_security.xml51(title) +msgid "List and view current security groups" +msgstr "" + +#: ./doc/user-guide-admin/section_cli_nova_manage_projects_security.xml52(para) +msgid "" +"From the command line you can get a list of security groups for the project " +"you're acting in using the nova command:" +msgstr "" + +#: ./doc/user-guide-admin/section_cli_nova_manage_projects_security.xml56(para) +msgid "" +"Ensure your system variables are set for the user and tenant for which you " +"are checking security group rules. For example:" +msgstr "" + +#: ./doc/user-guide-admin/section_cli_nova_manage_projects_security.xml63(para) +msgid "Output security groups, as follows:" +msgstr "" + +#: ./doc/user-guide-admin/section_cli_nova_manage_projects_security.xml73(para) +msgid "View the details of a group, as follows:" +msgstr "" + +#: ./doc/user-guide-admin/section_cli_nova_manage_projects_security.xml74(replaceable) +msgid "groupName" +msgstr "" + +#: ./doc/user-guide-admin/section_cli_nova_manage_projects_security.xml75(para) +#: ./doc/user-guide-admin/section_cli_nova_manage_projects_security.xml111(para) +#: ./doc/user-guide-admin/section_cli_nova_manage_projects_security.xml174(para) +#: ./doc/user-guide-admin/section_cli_nova_manage_projects_security.xml195(para) +#: ./doc/user-guide-admin/section_cli_cinder_quotas.xml80(para) +#: ./doc/user-guide-admin/section_cli_cinder_quotas.xml100(para) +#: ./doc/user-guide-admin/section_cli_nova_specify_host.xml16(para) +msgid "For example:" +msgstr "" + +#: ./doc/user-guide-admin/section_cli_nova_manage_projects_security.xml84(para) +msgid "" +"These rules are allow type rules as the default is deny. The first column is" +" the IP protocol (one of icmp, tcp, or udp) the second and third columns " +"specify the affected port range. The third column specifies the IP range in " +"CIDR format. This example shows the full port range for all protocols " +"allowed from all IPs." +msgstr "" + +#: ./doc/user-guide-admin/section_cli_nova_manage_projects_security.xml95(para) +msgid "" +"When adding a new security group, you should pick a descriptive but brief " +"name. This name shows up in brief descriptions of the instances that use it " +"where the longer description field often does not. For example, seeing that " +"an instance is using security group \"http\" is much easier to understand " +"than \"bobs_group\" or \"secgrp1\"." +msgstr "" + +#: ./doc/user-guide-admin/section_cli_nova_manage_projects_security.xml102(para) +msgid "" +"Ensure your system variables are set for the user and tenant for which you " +"are checking security group rules." +msgstr "" + +#: ./doc/user-guide-admin/section_cli_nova_manage_projects_security.xml107(para) +msgid "Add the new security group, as follows:" +msgstr "" + +#: ./doc/user-guide-admin/section_cli_nova_manage_projects_security.xml109(replaceable) +msgid "GroupName Description" +msgstr "" + +#: ./doc/user-guide-admin/section_cli_nova_manage_projects_security.xml122(para) +msgid "Add a new group rule, as follows:" +msgstr "" + +#: ./doc/user-guide-admin/section_cli_nova_manage_projects_security.xml124(replaceable) +msgid "secGroupName ip-protocol from-port to-port CIDR" +msgstr "" + +#: ./doc/user-guide-admin/section_cli_nova_manage_projects_security.xml126(para) +msgid "" +"The arguments are positional, and the \"from-port\" and \"to-port\" " +"arguments specify the local port range connections are allowed to access, " +"not the source and destination ports of the connection. For example:" +msgstr "" + +#: ./doc/user-guide-admin/section_cli_nova_manage_projects_security.xml139(para) +msgid "" +"You can create complex rule sets by creating additional rules. For example, " +"if you want to pass both http and https traffic, run:" +msgstr "" + +#: ./doc/user-guide-admin/section_cli_nova_manage_projects_security.xml148(para) +msgid "" +"Despite only outputting the newly added rule, this operation is additive " +"(both rules are created and enforced)." +msgstr "" + +#: ./doc/user-guide-admin/section_cli_nova_manage_projects_security.xml153(para) +msgid "View all rules for the new security group, as follows:" +msgstr "" + +#: ./doc/user-guide-admin/section_cli_nova_manage_projects_security.xml167(para) +msgid "" +"Ensure your system variables are set for the user and tenant for which you " +"are deleting a security group." +msgstr "" + +#: ./doc/user-guide-admin/section_cli_nova_manage_projects_security.xml172(para) +msgid "Delete the new security group, as follows:" +msgstr "" + +#: ./doc/user-guide-admin/section_cli_nova_manage_projects_security.xml173(replaceable) +msgid "GroupName" +msgstr "" + +#: ./doc/user-guide-admin/section_cli_nova_manage_projects_security.xml179(title) +msgid "Create security group rules for a cluster of instances" +msgstr "" + +#: ./doc/user-guide-admin/section_cli_nova_manage_projects_security.xml181(para) +msgid "" +"SourceGroups are a special, dynamic way of defining the CIDR of allowed " +"sources. The user specifies a SourceGroup (Security Group name), and all the" +" users' other Instances using the specified SourceGroup are selected " +"dynamically. This alleviates the need for individual rules to allow each new" +" member of the cluster." +msgstr "" + +#: ./doc/user-guide-admin/section_cli_nova_manage_projects_security.xml188(para) +msgid "" +"Make sure to set the system variables for the user and tenant for which you " +"are deleting a security group." +msgstr "" + +#: ./doc/user-guide-admin/section_cli_nova_manage_projects_security.xml193(para) +msgid "Add a source group, as follows:" +msgstr "" + +#: ./doc/user-guide-admin/section_cli_nova_manage_projects_security.xml194(replaceable) +msgid "secGroupName source-group ip-protocol from-port to-port" +msgstr "" + +#: ./doc/user-guide-admin/section_cli_nova_manage_projects_security.xml197(para) +msgid "" +"The cluster rule allows ssh access from any other instance that" +" uses the global_http group." +msgstr "" + +#. When image changes, this message will be marked fuzzy or untranslated for +#. you. +#. It doesn't matter what you translate it to: it's not used at all. +#: ./doc/user-guide-admin/section_dashboard_admin_manage_projects_users.xml176(None) +msgid "" +"@@image: 'figures/cloud_dash_users_list.png'; " +"md5=1e8329b11c15fe3709ba745363dd4a24" +msgstr "" + +#: ./doc/user-guide-admin/section_dashboard_admin_manage_projects_users.xml7(title) +msgid "Manage projects and users" +msgstr "" + +#: ./doc/user-guide-admin/section_dashboard_admin_manage_projects_users.xml8(para) +msgid "" +"As a cloud administrator, you manage both projects and users. Projects are " +"organizational units in the cloud to which you can assign users. Projects " +"are also known as tenants or accounts.You can manage projects and users " +"independently from each other." +msgstr "" + +#: ./doc/user-guide-admin/section_dashboard_admin_manage_projects_users.xml14(para) +msgid "Users are members of one or more projects." +msgstr "" + +#: ./doc/user-guide-admin/section_dashboard_admin_manage_projects_users.xml15(para) +msgid "" +"During cloud set up, the operator defines at least one project, user, and " +"role. The operator links the role to the user and the user to the project. " +"Roles define the actions that users can perform. As an administrator, you " +"can create additional projects and users as needed." +msgstr "" + +#: ./doc/user-guide-admin/section_dashboard_admin_manage_projects_users.xml20(para) +msgid "" +"Learn how to add, update, and delete projects and users, assign users to one" +" or more projects, and change or remove the assignment. To enable or " +"temporarily disable a project or user, update that project or user. You can " +"also change quotas at the project level. For information, see ." +msgstr "" + +#: ./doc/user-guide-admin/section_dashboard_admin_manage_projects_users.xml26(para) +msgid "" +"When you create a user account, you must assign the account to a primary " +"project. Optionally, you can assign the account to additional projects. " +"Before you can delete a user account, you must remove the user account from " +"its primary project." +msgstr "" + +#: ./doc/user-guide-admin/section_dashboard_admin_manage_projects_users.xml32(title) +msgid "Consequences of disabling projects and users" +msgstr "" + +#: ./doc/user-guide-admin/section_dashboard_admin_manage_projects_users.xml33(para) +msgid "When you disable a project, it has the following consequences:" +msgstr "" + +#: ./doc/user-guide-admin/section_dashboard_admin_manage_projects_users.xml37(para) +msgid "" +"In the dashboard, users can no longer access the project from the " +"CURRENT PROJECT drop-down list on the " +"Project tab." +msgstr "" + +#: ./doc/user-guide-admin/section_dashboard_admin_manage_projects_users.xml43(para) +msgid "" +"Users who are members of only the disabled project can no longer log in." +msgstr "" + +#: ./doc/user-guide-admin/section_dashboard_admin_manage_projects_users.xml47(para) +msgid "" +"You cannot launch instances for a disabled project. Instances that are " +"already running are not automatically terminated though—you must stop them " +"manually." +msgstr "" + +#: ./doc/user-guide-admin/section_dashboard_admin_manage_projects_users.xml53(para) +msgid "" +"The data for a disabled project is maintained so that you can enable the " +"project again at any time." +msgstr "" + +#: ./doc/user-guide-admin/section_dashboard_admin_manage_projects_users.xml58(para) +msgid "" +"When you disable a user account, the user can no longer log in, but the data" +" for the user is maintained so that you can enable the user again at any " +"time." +msgstr "" + +#: ./doc/user-guide-admin/section_dashboard_admin_manage_projects_users.xml63(title) +msgid "Create a project" +msgstr "" + +#: ./doc/user-guide-admin/section_dashboard_admin_manage_projects_users.xml72(para) +#: ./doc/user-guide-admin/section_dashboard_admin_manage_projects_users.xml109(para) +#: ./doc/user-guide-admin/section_dashboard_admin_manage_projects_users.xml205(para) +#: ./doc/user-guide-admin/section_dashboard_admin_set_quotas.xml172(para) +msgid "" +"On the Admin tab, click the " +"Projects category." +msgstr "" + +#: ./doc/user-guide-admin/section_dashboard_admin_manage_projects_users.xml76(para) +#: ./doc/user-guide-admin/section_dashboard_admin_manage_projects_users.xml96(para) +msgid "Click Create Project." +msgstr "" + +#: ./doc/user-guide-admin/section_dashboard_admin_manage_projects_users.xml80(para) +msgid "" +"On the Project Info tab in the Create " +"Project window, enter a name and description for the project. By " +"default, the project is enabled. See ." +msgstr "" + +#: ./doc/user-guide-admin/section_dashboard_admin_manage_projects_users.xml87(para) +msgid "" +"On the Project Members tab, add members to the project." +msgstr "" + +#: ./doc/user-guide-admin/section_dashboard_admin_manage_projects_users.xml91(para) +msgid "" +"On the Quota tab, edit quota values. For information " +"about quotas, see ." +msgstr "" + +#: ./doc/user-guide-admin/section_dashboard_admin_manage_projects_users.xml98(para) +msgid "" +"The Projects category shows the project, including its " +"assigned ID." +msgstr "" + +#: ./doc/user-guide-admin/section_dashboard_admin_manage_projects_users.xml105(para) +msgid "" +"You can update a project to change its name or description, and enable or " +"temporarily disable it." +msgstr "" + +#: ./doc/user-guide-admin/section_dashboard_admin_manage_projects_users.xml113(para) +msgid "Select the project that you want to update." +msgstr "" + +#: ./doc/user-guide-admin/section_dashboard_admin_manage_projects_users.xml117(para) +msgid "" +"In the More drop-down list, click Edit " +"Project." +msgstr "" + +#: ./doc/user-guide-admin/section_dashboard_admin_manage_projects_users.xml121(para) +msgid "" +"In the Edit Project window, you can update a project to" +" change its name or description, and enable or temporarily disable it." +msgstr "" + +#: ./doc/user-guide-admin/section_dashboard_admin_manage_projects_users.xml125(para) +msgid "" +"By default, the project is enabled. To temporarily disable it, clear the " +"Enabled check box. To enable a disabled project, select" +" the Enabled check box." +msgstr "" + +#: ./doc/user-guide-admin/section_dashboard_admin_manage_projects_users.xml137(title) +msgid "Modify user assignments for a project" +msgstr "" + +#: ./doc/user-guide-admin/section_dashboard_admin_manage_projects_users.xml138(para) +msgid "" +"When you create users, you must assign them to a primary project as " +"described in . You can assign users" +" to additional projects or update and remove assignments." +msgstr "" + +#: ./doc/user-guide-admin/section_dashboard_admin_manage_projects_users.xml145(para) +msgid "" +"On the Admin tab, select the " +"Projects category." +msgstr "" + +#: ./doc/user-guide-admin/section_dashboard_admin_manage_projects_users.xml149(para) +msgid "Select a project to modify its user assignments." +msgstr "" + +#: ./doc/user-guide-admin/section_dashboard_admin_manage_projects_users.xml153(para) +msgid "Select Modify Users." +msgstr "" + +#: ./doc/user-guide-admin/section_dashboard_admin_manage_projects_users.xml155(para) +msgid "" +"The Edit Project window shows the following lists of " +"users:" +msgstr "" + +#: ./doc/user-guide-admin/section_dashboard_admin_manage_projects_users.xml159(para) +msgid "" +"All Users. Users that are available to be assigned to " +"the current project." +msgstr "" + +#: ./doc/user-guide-admin/section_dashboard_admin_manage_projects_users.xml164(para) +msgid "" +"Project Members. Users that are assigned to the current" +" project," +msgstr "" + +#: ./doc/user-guide-admin/section_dashboard_admin_manage_projects_users.xml170(title) +msgid "Edit the users list" +msgstr "" + +#: ./doc/user-guide-admin/section_dashboard_admin_manage_projects_users.xml182(para) +msgid "" +"To assign a user to the current project, click + for " +"the user." +msgstr "" + +#: ./doc/user-guide-admin/section_dashboard_admin_manage_projects_users.xml184(para) +msgid "" +"The user moves from the All Users list to the " +"Project Members list." +msgstr "" + +#: ./doc/user-guide-admin/section_dashboard_admin_manage_projects_users.xml189(para) +msgid "" +"To remove a user from the current project, click the " +"- button for the user." +msgstr "" + +#: ./doc/user-guide-admin/section_dashboard_admin_manage_projects_users.xml192(para) +msgid "" +"The user moves from the Project Members list to the " +"All Users list." +msgstr "" + +#: ./doc/user-guide-admin/section_dashboard_admin_manage_projects_users.xml202(title) +msgid "Delete projects" +msgstr "" + +#: ./doc/user-guide-admin/section_dashboard_admin_manage_projects_users.xml209(para) +msgid "Select the projects that you want to delete." +msgstr "" + +#: ./doc/user-guide-admin/section_dashboard_admin_manage_projects_users.xml213(para) +msgid "Click Delete Projects to confirm the deletion." +msgstr "" + +#: ./doc/user-guide-admin/section_dashboard_admin_manage_projects_users.xml216(para) +msgid "You cannot undo the delete action." +msgstr "" + +#: ./doc/user-guide-admin/section_dashboard_admin_manage_projects_users.xml222(title) +msgid "Create a user account" +msgstr "" + +#: ./doc/user-guide-admin/section_dashboard_admin_manage_projects_users.xml231(para) +#: ./doc/user-guide-admin/section_dashboard_admin_manage_projects_users.xml262(para) +#: ./doc/user-guide-admin/section_dashboard_admin_manage_projects_users.xml285(para) +msgid "" +"On the Admin tab, select the Users" +" category." +msgstr "" + +#: ./doc/user-guide-admin/section_dashboard_admin_manage_projects_users.xml235(para) +msgid "Click Create User." +msgstr "" + +#: ./doc/user-guide-admin/section_dashboard_admin_manage_projects_users.xml238(para) +msgid "" +"In the Create User window, enter a user name, email, " +"and preliminary password for the user. Confirm the password." +msgstr "" + +#: ./doc/user-guide-admin/section_dashboard_admin_manage_projects_users.xml241(para) +msgid "" +"Select a project from the Primary Project drop-down " +"list." +msgstr "" + +#: ./doc/user-guide-admin/section_dashboard_admin_manage_projects_users.xml243(para) +msgid "" +"Choose a role for the user from the Role drop-down " +"list. Default is Member." +msgstr "" + +#: ./doc/user-guide-admin/section_dashboard_admin_manage_projects_users.xml248(para) +msgid "Click Create User to confirm your changes." +msgstr "" + +#: ./doc/user-guide-admin/section_dashboard_admin_manage_projects_users.xml250(para) +msgid "Respond to the prompt to remember the password for the user." +msgstr "" + +#: ./doc/user-guide-admin/section_dashboard_admin_manage_projects_users.xml252(para) +msgid "" +"The dashboard assigns an ID to the user, and the user appears in the " +"Users category." +msgstr "" + +#: ./doc/user-guide-admin/section_dashboard_admin_manage_projects_users.xml259(title) +msgid "Disable or enable a user" +msgstr "" + +#: ./doc/user-guide-admin/section_dashboard_admin_manage_projects_users.xml266(para) +msgid "" +"Select the user that you want to disable or enable. You can disable or " +"enable only one user at a time." +msgstr "" + +#: ./doc/user-guide-admin/section_dashboard_admin_manage_projects_users.xml271(para) +msgid "" +"In the Actions drop-down list, select Disable" +" User or Enable User." +msgstr "" + +#: ./doc/user-guide-admin/section_dashboard_admin_manage_projects_users.xml274(para) +msgid "" +"In the Enabled column, the enabled value updates to " +"either True or False." +msgstr "" + +#: ./doc/user-guide-admin/section_dashboard_admin_manage_projects_users.xml282(title) +msgid "Delete users" +msgstr "" + +#: ./doc/user-guide-admin/section_dashboard_admin_manage_projects_users.xml289(para) +msgid "Select the users that you want to delete." +msgstr "" + +#: ./doc/user-guide-admin/section_dashboard_admin_manage_projects_users.xml292(para) +msgid "Click Delete Users." +msgstr "" + +#: ./doc/user-guide-admin/section_dashboard_admin_manage_projects_users.xml295(para) +msgid "" +"In the Confirm Delete Users window, click " +"Delete Users to confirm the deletion." +msgstr "" + +#: ./doc/user-guide-admin/ch_cli.xml10(title) +msgid "OpenStack command-line clients" +msgstr "" + +#: ./doc/user-guide-admin/section_cli_cinder_quotas.xml6(title) +msgid "Manage Block Storage service quotas" +msgstr "" + +#: ./doc/user-guide-admin/section_cli_cinder_quotas.xml7(para) +msgid "" +"As an administrative user, you can update the OpenStack Block Storage " +"Service quotas for a project. You can also update the quota defaults for a " +"new project." +msgstr "" + +#: ./doc/user-guide-admin/section_cli_cinder_quotas.xml12(caption) +msgid "Block Storage quotas" +msgstr "" + +#: ./doc/user-guide-admin/section_cli_cinder_quotas.xml17(th) +msgid "Property name" +msgstr "" + +#: ./doc/user-guide-admin/section_cli_cinder_quotas.xml18(th) +#: ./doc/user-guide-admin/section_dashboard_admin_set_quotas.xml41(th) +msgid "Defines the number of" +msgstr "" + +#: ./doc/user-guide-admin/section_cli_cinder_quotas.xml24(para) +msgid "gigabytes" +msgstr "" + +#: ./doc/user-guide-admin/section_cli_cinder_quotas.xml27(para) +msgid "Volume gigabytes allowed for each tenant." +msgstr "" + +#: ./doc/user-guide-admin/section_cli_cinder_quotas.xml33(para) +msgid "snapshots" +msgstr "" + +#: ./doc/user-guide-admin/section_cli_cinder_quotas.xml36(para) +msgid "Volume snapshots allowed for each tenant." +msgstr "" + +#: ./doc/user-guide-admin/section_cli_cinder_quotas.xml42(para) +msgid "volumes" +msgstr "" + +#: ./doc/user-guide-admin/section_cli_cinder_quotas.xml45(para) +msgid "Volumes allowed for each tenant." +msgstr "" + +#: ./doc/user-guide-admin/section_cli_cinder_quotas.xml52(title) +msgid "View and update Block Storage Service quotas" +msgstr "" + +#: ./doc/user-guide-admin/section_cli_cinder_quotas.xml53(para) +msgid "" +"As an administrative user, you can view and update Block Storage Service " +"quotas." +msgstr "" + +#: ./doc/user-guide-admin/section_cli_cinder_quotas.xml57(para) +msgid "List the default quotas for all projects, as follows:" +msgstr "" + +#: ./doc/user-guide-admin/section_cli_cinder_quotas.xml69(para) +msgid "" +"To update a default value for a new project, update the property in the " +"/etc/cinder/cinder.conf file." +msgstr "" + +#: ./doc/user-guide-admin/section_cli_cinder_quotas.xml77(para) +msgid "View Block Storage Service quotas for a project, as follows:" +msgstr "" + +#: ./doc/user-guide-admin/section_cli_cinder_quotas.xml79(replaceable) +msgid "TENANT_NAME" +msgstr "" + +#: ./doc/user-guide-admin/section_cli_cinder_quotas.xml91(para) +msgid "" +"To update Block Storage Service quotas, place the tenant ID in a usable " +"variable, as follows:" +msgstr "" + +#: ./doc/user-guide-admin/section_cli_cinder_quotas.xml94(replaceable) +msgid "tenantName" +msgstr "" + +#: ./doc/user-guide-admin/section_cli_cinder_quotas.xml97(para) +msgid "Update a particular quota value, as follows:" +msgstr "" + +#: ./doc/user-guide-admin/section_cli_cinder_quotas.xml99(replaceable) +msgid "quotaName" +msgstr "" + +#: ./doc/user-guide-admin/section_cli_cinder_quotas.xml99(replaceable) +msgid "NewValue" +msgstr "" + +#: ./doc/user-guide-admin/section_cli_cinder_quotas.xml99(replaceable) +#: ./doc/user-guide-admin/section_cli_keystone_set_quotas.xml40(replaceable) +msgid "tenantID" +msgstr "" + +#: ./doc/user-guide-admin/section_cli_swift_analyze_log_files.xml7(title) +msgid "Analyze log files" +msgstr "" + +#: ./doc/user-guide-admin/section_cli_swift_analyze_log_files.xml8(para) +msgid "Use the swift command-line client to analyze log files." +msgstr "" + +#: ./doc/user-guide-admin/section_cli_swift_analyze_log_files.xml9(para) +msgid "The swift client is simple to use, scalable, and flexible." +msgstr "" + +#: ./doc/user-guide-admin/section_cli_swift_analyze_log_files.xml9(para) +msgid "" +"Use the swift client or option " +"to get short answers to questions about logs," +msgstr "" + +#: ./doc/user-guide-admin/section_cli_swift_analyze_log_files.xml12(para) +msgid "" +"You can use the option with a single object " +"download to redirect the command output to a specific file or to STDOUT " +"(-). The ability to redirect the output to STDOUT enables" +" you to pipe (|) data without saving it to disk first." +msgstr "" + +#: ./doc/user-guide-admin/section_cli_swift_analyze_log_files.xml18(title) +msgid "Upload and analyze log files" +msgstr "" + +#: ./doc/user-guide-admin/section_cli_swift_analyze_log_files.xml20(para) +msgid "" +"This example assumes that logtest directory contains " +"the following log files:" +msgstr "" + +#: ./doc/user-guide-admin/section_cli_swift_analyze_log_files.xml23(title) +msgid "Example files" +msgstr "" + +#: ./doc/user-guide-admin/section_cli_swift_analyze_log_files.xml27(para) +msgid "Each file uses the following line format:" +msgstr "" + +#: ./doc/user-guide-admin/section_cli_swift_analyze_log_files.xml28(title) +msgid "Log line format" +msgstr "" + +#: ./doc/user-guide-admin/section_cli_swift_analyze_log_files.xml31(para) +msgid "" +"Change into the logtest directory:" +msgstr "" + +#: ./doc/user-guide-admin/section_cli_swift_analyze_log_files.xml35(para) +msgid "Upload the log files into the logtest container:" +msgstr "" + +#: ./doc/user-guide-admin/section_cli_swift_analyze_log_files.xml42(para) +msgid "Get statistics for the account:" +msgstr "" + +#: ./doc/user-guide-admin/section_cli_swift_analyze_log_files.xml48(para) +msgid "Get statistics for the logtest container:" +msgstr "" + +#: ./doc/user-guide-admin/section_cli_swift_analyze_log_files.xml56(para) +msgid "List all objects in the logtest container:" +msgstr "" + +#: ./doc/user-guide-admin/section_cli_swift_analyze_log_files.xml62(title) +msgid "Download and analyze an object" +msgstr "" + +#: ./doc/user-guide-admin/section_cli_swift_analyze_log_files.xml64(para) +msgid "" +"This example uses the option and a hyphen " +"(-) to get information about an object." +msgstr "" + +#: ./doc/user-guide-admin/section_cli_swift_analyze_log_files.xml67(para) +msgid "" +"Use the swift command to download the object. On this " +"command, stream the output to to break down requests by " +"return code and the date 2200 on November 16th, 2010." +msgstr "" + +#: ./doc/user-guide-admin/section_cli_swift_analyze_log_files.xml72(para) +msgid "" +"Using the log line format, find the request type in column 9 and the return " +"code in column 12." +msgstr "" + +#: ./doc/user-guide-admin/section_cli_swift_analyze_log_files.xml74(para) +msgid "" +"After processes the output, it pipes it to " +" and to sum up the number of occurrences for each request " +"type and return code combination." +msgstr "" + +#: ./doc/user-guide-admin/section_cli_swift_analyze_log_files.xml80(para) +msgid "Download an object:" +msgstr "" + +#: ./doc/user-guide-admin/section_cli_swift_analyze_log_files.xml113(para) +msgid "Discover how many PUT requests are in each log file." +msgstr "" + +#: ./doc/user-guide-admin/section_cli_swift_analyze_log_files.xml114(para) +msgid "" +"Use a bash for loop with awk and swift with the " +"option and a hyphen (-) to discover how many PUT requests" +" are in each log file." +msgstr "" + +#: ./doc/user-guide-admin/section_cli_swift_analyze_log_files.xml119(para) +msgid "" +"Run the swift command to list objects in the logtest " +"container. Then, for each item in the list, run the swift " +"command. Pipe the output into grep to filter the PUT requests. Finally, pipe" +" into to count the lines." +msgstr "" + +#: ./doc/user-guide-admin/section_cli_swift_analyze_log_files.xml134(para) +msgid "List the object names that begin with a specified string." +msgstr "" + +#: ./doc/user-guide-admin/section_cli_swift_analyze_log_files.xml136(para) +msgid "" +"Run the swift command to list objects in the logtest " +"container that begin with the 2010-11-15 string." +msgstr "" + +#: ./doc/user-guide-admin/section_cli_swift_analyze_log_files.xml140(para) +msgid "For each item in the list, run the swift command." +msgstr "" + +#: ./doc/user-guide-admin/section_cli_swift_analyze_log_files.xml142(para) +msgid "" +"Pipe the output to and . Use the " +" command to display the object name." +msgstr "" + +#: ./doc/user-guide-admin/section_cli_admin_manage_environment.xml4(title) +msgid "Manage the OpenStack environment" +msgstr "" + +#: ./doc/user-guide-admin/section_cli_admin_manage_environment.xml5(para) +msgid "This section includes tasks specific to the OpenStack environment." +msgstr "" + +#: ./doc/user-guide-admin/section_cli_manage_services.xml7(title) +msgid "Manage services" +msgstr "" + +#: ./doc/user-guide-admin/section_dashboard_admin_manage_images.xml7(title) +msgid "Create and manage images" +msgstr "" + +#: ./doc/user-guide-admin/section_dashboard_admin_manage_images.xml8(para) +msgid "" +"As an administrative user, you can create and manage images for the projects" +" to which you belong. You can also create and manage images for users in all" +" projects to which you have access." +msgstr "" + +#: ./doc/user-guide-admin/section_dashboard_admin_manage_images.xml12(para) +msgid "" +"To create and manage images in specified projects as an end user, see the " +"OpenStack End User Guide." +msgstr "" + +#: ./doc/user-guide-admin/section_dashboard_admin_manage_images.xml17(para) +msgid "" +"To create and manage images as an administrator for other users, use the " +"following procedures." +msgstr "" + +#: ./doc/user-guide-admin/section_dashboard_admin_manage_images.xml20(title) +msgid "Create images" +msgstr "" + +#: ./doc/user-guide-admin/section_dashboard_admin_manage_images.xml21(para) +msgid "" +"For details about image creation, see the Virtual " +"Machine Image Guide." +msgstr "" + +#: ./doc/user-guide-admin/section_dashboard_admin_manage_images.xml33(para) +msgid "" +"On the Admin tab, click the Images" +" category. The images that you can administer for cloud users appear on this" +" page." +msgstr "" + +#: ./doc/user-guide-admin/section_dashboard_admin_manage_images.xml38(para) +#: ./doc/user-guide-admin/section_dashboard_admin_manage_images.xml85(para) +msgid "Click Create Image." +msgstr "" + +#: ./doc/user-guide-admin/section_dashboard_admin_manage_images.xml41(para) +msgid "" +"In the Create An Image window, enter or select the " +"following values:" +msgstr "" + +#: ./doc/user-guide-admin/section_dashboard_admin_manage_images.xml49(para) +msgid "Enter a name for the image." +msgstr "" + +#: ./doc/user-guide-admin/section_dashboard_admin_manage_images.xml53(para) +msgid "Enter a brief description about the image." +msgstr "" + +#: ./doc/user-guide-admin/section_dashboard_admin_manage_images.xml57(guilabel) +msgid "Image Location" +msgstr "" + +#: ./doc/user-guide-admin/section_dashboard_admin_manage_images.xml59(para) +msgid "Include the URL of the image." +msgstr "" + +#: ./doc/user-guide-admin/section_dashboard_admin_manage_images.xml62(guilabel) +msgid "Image File" +msgstr "" + +#: ./doc/user-guide-admin/section_dashboard_admin_manage_images.xml63(para) +msgid "Alternatively, browse to find the image file on your machine." +msgstr "" + +#: ./doc/user-guide-admin/section_dashboard_admin_manage_images.xml67(guilabel) +msgid "Format" +msgstr "" + +#: ./doc/user-guide-admin/section_dashboard_admin_manage_images.xml68(para) +msgid "Select the image format." +msgstr "" + +#: ./doc/user-guide-admin/section_dashboard_admin_manage_images.xml71(para) +msgid "" +"Minimum Disk (GB) and Maximum Disk " +"(GB)" +msgstr "" + +#: ./doc/user-guide-admin/section_dashboard_admin_manage_images.xml73(para) +msgid "Leave these fields empty." +msgstr "" + +#: ./doc/user-guide-admin/section_dashboard_admin_manage_images.xml77(guilabel) +msgid "Public" +msgstr "" + +#: ./doc/user-guide-admin/section_dashboard_admin_manage_images.xml78(para) +msgid "Select this option to make the image public to all users." +msgstr "" + +#: ./doc/user-guide-admin/section_dashboard_admin_manage_images.xml86(para) +msgid "" +"The image is queued to be uploaded. It might take some time before the " +"status changes from queued to active." +msgstr "" + +#: ./doc/user-guide-admin/section_dashboard_admin_manage_images.xml92(title) +msgid "Update images" +msgstr "" + +#: ./doc/user-guide-admin/section_dashboard_admin_manage_images.xml101(para) +#: ./doc/user-guide-admin/section_dashboard_admin_manage_images.xml131(para) +msgid "" +"On the Admin tab, click the Images" +" category." +msgstr "" + +#: ./doc/user-guide-admin/section_dashboard_admin_manage_images.xml105(para) +msgid "" +"Select the image that you want to edit. Click Edit." +msgstr "" + +#: ./doc/user-guide-admin/section_dashboard_admin_manage_images.xml109(para) +msgid "" +"In the Update Image window, you can change the name for" +" the image. Select the Public check box to make the " +"image public. Clear this check box to make the image private. You cannot " +"change the kernel ID, RAM disk ID, or architecture attributes for an image." +msgstr "" + +#: ./doc/user-guide-admin/section_dashboard_admin_manage_images.xml117(para) +msgid "Click Update Image." +msgstr "" + +#: ./doc/user-guide-admin/section_dashboard_admin_manage_images.xml122(title) +msgid "Delete images" +msgstr "" + +#: ./doc/user-guide-admin/section_dashboard_admin_manage_images.xml135(para) +msgid "Select the images that you want to delete." +msgstr "" + +#: ./doc/user-guide-admin/section_dashboard_admin_manage_images.xml138(para) +msgid "Click Delete Images." +msgstr "" + +#: ./doc/user-guide-admin/section_dashboard_admin_manage_images.xml141(para) +msgid "" +"In the Confirm Delete Image window, click " +"Delete Images to confirm the deletion." +msgstr "" + +#: ./doc/user-guide-admin/section_dashboard_admin_manage_images.xml144(para) +msgid "You cannot undo this action." +msgstr "" + +#: ./doc/user-guide-admin/section_dashboard_admin_set_quotas.xml14(title) +msgid "View and manage quotas" +msgstr "" + +#: ./doc/user-guide-admin/section_dashboard_admin_set_quotas.xml15(para) +#: ./doc/user-guide-admin/section_cli_keystone_set_quotas.xml15(para) +msgid "" +"To prevent system capacities from being exhausted without notification, you " +"can set up quotas. Quotas are operational limits. For example, the number of" +" gigabytes allowed for each tenant can be controlled so that cloud resources" +" are optimized. Quotas can be enforced at both the tenant (or project) and " +"the tenant-user level." +msgstr "" + +#: ./doc/user-guide-admin/section_dashboard_admin_set_quotas.xml20(para) +msgid "" +"Typically, you change quotas when a project needs more than 10 volumes or 1 " +"TB on a Compute node." +msgstr "" + +#: ./doc/user-guide-admin/section_dashboard_admin_set_quotas.xml22(para) +msgid "" +"Using the Dashboard, you can view default Compute and Block Storage quotas " +"for new tenants, as well as update quotas for existing tenants." +msgstr "" + +#: ./doc/user-guide-admin/section_dashboard_admin_set_quotas.xml25(para) +msgid "" +"Using the command-line interface, you can manage quotas for the OpenStack " +"Compute Service, the OpenStack Block Storage Service, and the OpenStack " +"Networking Service (see ). Additionally, " +"you can update Compute service quotas for tenant users." +msgstr "" + +#: ./doc/user-guide-admin/section_dashboard_admin_set_quotas.xml31(para) +msgid "" +"The following table describes the Compute and Block Storage service quotas:" +msgstr "" + +#: ./doc/user-guide-admin/section_dashboard_admin_set_quotas.xml34(caption) +msgid "Quota Descriptions" +msgstr "" + +#: ./doc/user-guide-admin/section_dashboard_admin_set_quotas.xml40(th) +msgid "Quota Name" +msgstr "" + +#: ./doc/user-guide-admin/section_dashboard_admin_set_quotas.xml42(th) +msgid "Service" +msgstr "" + +#: ./doc/user-guide-admin/section_dashboard_admin_set_quotas.xml48(para) +msgid "Gigabytes" +msgstr "" + +#: ./doc/user-guide-admin/section_dashboard_admin_set_quotas.xml51(para) +msgid "Volume gigabytes allowed for each project." +msgstr "" + +#: ./doc/user-guide-admin/section_dashboard_admin_set_quotas.xml53(td) +#: ./doc/user-guide-admin/section_dashboard_admin_set_quotas.xml125(td) +#: ./doc/user-guide-admin/section_dashboard_admin_set_quotas.xml143(td) +msgid "Block Storage" +msgstr "" + +#: ./doc/user-guide-admin/section_dashboard_admin_set_quotas.xml57(para) +msgid "Instances" +msgstr "" + +#: ./doc/user-guide-admin/section_dashboard_admin_set_quotas.xml60(para) +msgid "Instances allowed for each project." +msgstr "" + +#: ./doc/user-guide-admin/section_dashboard_admin_set_quotas.xml62(td) +#: ./doc/user-guide-admin/section_dashboard_admin_set_quotas.xml71(td) +#: ./doc/user-guide-admin/section_dashboard_admin_set_quotas.xml80(td) +#: ./doc/user-guide-admin/section_dashboard_admin_set_quotas.xml89(td) +#: ./doc/user-guide-admin/section_dashboard_admin_set_quotas.xml98(td) +#: ./doc/user-guide-admin/section_dashboard_admin_set_quotas.xml107(td) +#: ./doc/user-guide-admin/section_dashboard_admin_set_quotas.xml116(td) +#: ./doc/user-guide-admin/section_dashboard_admin_set_quotas.xml134(td) +msgid "Compute" +msgstr "" + +#: ./doc/user-guide-admin/section_dashboard_admin_set_quotas.xml66(para) +msgid "Injected Files" +msgstr "" + +#: ./doc/user-guide-admin/section_dashboard_admin_set_quotas.xml69(para) +msgid "Injected files allowed for each project." +msgstr "" + +#: ./doc/user-guide-admin/section_dashboard_admin_set_quotas.xml75(para) +msgid "Injected File Content Bytes" +msgstr "" + +#: ./doc/user-guide-admin/section_dashboard_admin_set_quotas.xml78(para) +msgid "Content bytes allowed for each injected file." +msgstr "" + +#: ./doc/user-guide-admin/section_dashboard_admin_set_quotas.xml84(para) +msgid "Metadata Items" +msgstr "" + +#: ./doc/user-guide-admin/section_dashboard_admin_set_quotas.xml87(para) +msgid "Metadata items allowed for each instance." +msgstr "" + +#: ./doc/user-guide-admin/section_dashboard_admin_set_quotas.xml93(para) +msgid "RAM (MB)" +msgstr "" + +#: ./doc/user-guide-admin/section_dashboard_admin_set_quotas.xml96(para) +msgid "RAM megabytes allowed for each instance." +msgstr "" + +#: ./doc/user-guide-admin/section_dashboard_admin_set_quotas.xml102(para) +msgid "Security Groups" +msgstr "" + +#: ./doc/user-guide-admin/section_dashboard_admin_set_quotas.xml105(para) +msgid "Security groups allowed for each project." +msgstr "" + +#: ./doc/user-guide-admin/section_dashboard_admin_set_quotas.xml111(para) +msgid "Security Group Rules" +msgstr "" + +#: ./doc/user-guide-admin/section_dashboard_admin_set_quotas.xml114(para) +msgid "Rules allowed for each security group." +msgstr "" + +#: ./doc/user-guide-admin/section_dashboard_admin_set_quotas.xml120(para) +msgid "Snapshots" +msgstr "" + +#: ./doc/user-guide-admin/section_dashboard_admin_set_quotas.xml123(para) +msgid "Volume snapshots allowed for each project." +msgstr "" + +#: ./doc/user-guide-admin/section_dashboard_admin_set_quotas.xml132(para) +msgid "Instance cores allowed for each project." +msgstr "" + +#: ./doc/user-guide-admin/section_dashboard_admin_set_quotas.xml138(para) +msgid "Volumes" +msgstr "" + +#: ./doc/user-guide-admin/section_dashboard_admin_set_quotas.xml141(para) +msgid "Volumes allowed for each project." +msgstr "" + +#: ./doc/user-guide-admin/section_dashboard_admin_set_quotas.xml149(title) +msgid "View default project quotas" +msgstr "" + +#: ./doc/user-guide-admin/section_dashboard_admin_set_quotas.xml152(para) +#: ./doc/user-guide-admin/section_dashboard_admin_set_quotas.xml169(para) +msgid "Log in to the OpenStack dashboard." +msgstr "" + +#: ./doc/user-guide-admin/section_dashboard_admin_set_quotas.xml154(para) +msgid "" +"On the Admin tab, click the " +"Defaults category." +msgstr "" + +#: ./doc/user-guide-admin/section_dashboard_admin_set_quotas.xml158(para) +msgid "" +"Click the Default Quotas tab to view the default quotas" +" for the Compute and Block Storage services." +msgstr "" + +#: ./doc/user-guide-admin/section_dashboard_admin_set_quotas.xml163(para) +msgid "" +"You can sort the table by clicking on either the Quota " +"Name or Limit column headers." +msgstr "" + +#: ./doc/user-guide-admin/section_dashboard_admin_set_quotas.xml166(title) +msgid "Update project quotas" +msgstr "" + +#: ./doc/user-guide-admin/section_dashboard_admin_set_quotas.xml176(para) +msgid "" +"In the More drop-down list for a project, click " +"Modify Quotas." +msgstr "" + +#: ./doc/user-guide-admin/section_dashboard_admin_set_quotas.xml180(para) +msgid "" +"On the Quota tab in the Edit " +"Project window, edit the quota values. Then, click " +"Save." +msgstr "" + +#: ./doc/user-guide-admin/section_dashboard_admin_set_quotas.xml186(para) +msgid "" +"The dashboard does not show all possible project quotas. To view and update " +"the quotas for a service, use its command-line client. See ." +msgstr "" + +#: ./doc/user-guide-admin/section_cli_keystone_set_quotas.xml14(title) +msgid "Manage quotas" +msgstr "" + +#: ./doc/user-guide-admin/section_cli_keystone_set_quotas.xml21(para) +msgid "" +"Using the command-line interface, you can manage quotas for the OpenStack " +"Compute Service, the OpenStack Block Storage Service, and the OpenStack " +"Networking Service." +msgstr "" + +#: ./doc/user-guide-admin/section_cli_keystone_set_quotas.xml24(para) +msgid "" +"Typically, default values are changed because a tenant requires more than 10" +" volumes, or more than 1TB on a Compute node." +msgstr "" + +#: ./doc/user-guide-admin/section_cli_keystone_set_quotas.xml27(para) +msgid "To view all tenants (projects), run: " +msgstr "" + +#: ./doc/user-guide-admin/section_cli_keystone_set_quotas.xml38(para) +msgid "To display all current users for a tenant, run:" +msgstr "" + +#: ./doc/user-guide-admin/section_dashboard_admin_view_cloud_resources.xml12(title) +msgid "View cloud usage statistics" +msgstr "" + +#: ./doc/user-guide-admin/section_dashboard_admin_view_cloud_resources.xml13(para) +msgid "" +"The Telemetry service provides user-level usage data for OpenStack-based " +"clouds, which can be used for customer billing, system monitoring, or " +"alerts. Data can be collected by notifications sent by existing OpenStack " +"components (for example, usage events emitted from Compute) or by polling " +"the infrastructure (for example, libvirt)." +msgstr "" + +#: ./doc/user-guide-admin/section_dashboard_admin_view_cloud_resources.xml19(para) +msgid "" +"You can only view metering statistics on the dashboard (available only to " +"adminstrators). The Telemetry service must be set up and administered " +"through the command-line interface (CLI)." +msgstr "" + +#: ./doc/user-guide-admin/section_dashboard_admin_view_cloud_resources.xml23(para) +msgid "" +"For basic administration information, refer to the \"Measure Cloud " +"Resources\" chapter in the OpenStack End User Guide." +msgstr "" + +#: ./doc/user-guide-admin/section_dashboard_admin_view_cloud_resources.xml26(title) +msgid "View resource statistics" +msgstr "" + +#: ./doc/user-guide-admin/section_dashboard_admin_view_cloud_resources.xml29(para) +msgid "Log in to the OpenStack dashboard as a user with Admin privileges." +msgstr "" + +#: ./doc/user-guide-admin/section_dashboard_admin_view_cloud_resources.xml31(para) +msgid "" +"On the Admin tab, click the Resource " +"Usage category." +msgstr "" + +#: ./doc/user-guide-admin/section_dashboard_admin_view_cloud_resources.xml37(para) +msgid "" +"Global Disk Usage tab to view disk usage per tenant " +"(project)." +msgstr "" + +#: ./doc/user-guide-admin/section_dashboard_admin_view_cloud_resources.xml38(para) +msgid "" +"Global Network Traffic Usage tab to view ingress or " +"egress usage per tenant (project)." +msgstr "" + +#: ./doc/user-guide-admin/section_dashboard_admin_view_cloud_resources.xml40(para) +msgid "" +"Global Network Usage tab to view duration and creation " +"requests for networks, subnets, routers, ports, and floating IPs, per tenant" +" (project)." +msgstr "" + +#: ./doc/user-guide-admin/section_dashboard_admin_view_cloud_resources.xml43(para) +msgid "" +"Stats tab to view a multi-series line chart with user-" +"defined metrics. You group by project, define the value type (min, max, avg," +" or sum), and specify the time period (or even use a calendar to define a " +"date range)." +msgstr "" + +#: ./doc/user-guide-admin/section_dashboard_admin_view_cloud_resources.xml35(para) +msgid "Click the: " +msgstr "" + +#: ./doc/user-guide-admin/section_dashboard_admin_manage_services.xml13(title) +msgid "View services information" +msgstr "" + +#: ./doc/user-guide-admin/section_dashboard_admin_manage_services.xml14(para) +msgid "" +"As an administrative user, you can view information for OpenStack services." +msgstr "" + +#: ./doc/user-guide-admin/section_dashboard_admin_manage_services.xml18(para) +msgid "" +"Log in to the OpenStack dashboard and choose the admin " +"project from the CURRENT PROJECT drop-down list." +msgstr "" + +#: ./doc/user-guide-admin/section_dashboard_admin_manage_services.xml23(para) +msgid "" +"On the Admin tab, click the System " +"Info category." +msgstr "" + +#: ./doc/user-guide-admin/section_dashboard_admin_manage_services.xml29(para) +msgid "Services tab to view services information." +msgstr "" + +#: ./doc/user-guide-admin/section_dashboard_admin_manage_services.xml30(para) +msgid "" +"The page displays the internal name and the public OpenStack name for the " +"service, the host where the service runs, and whether the service is or is " +"not enabled." +msgstr "" + +#: ./doc/user-guide-admin/section_dashboard_admin_manage_services.xml34(para) +msgid "" +"Compute Services tab to view services specific to the " +"Compute Service. Both host and zone are listed for each service, as well as " +"its activation status." +msgstr "" + +#: ./doc/user-guide-admin/section_dashboard_admin_manage_services.xml27(para) +msgid "Click the:" +msgstr "" + +#: ./doc/user-guide-admin/section_dashboard_admin_manage_services.xml43(guilabel) +msgid "Availability Zones" +msgstr "" + +#: ./doc/user-guide-admin/section_dashboard_admin_manage_services.xml46(guilabel) +msgid "Host Aggregates" +msgstr "" + +#: ./doc/user-guide-admin/section_dashboard_admin_manage_services.xml49(guilabel) +msgid "Network Agents" +msgstr "" + +#: ./doc/user-guide-admin/section_dashboard_admin_manage_services.xml41(para) +msgid "" +"The System Info window also offers status information " +"for the following: " +msgstr "" + +#: ./doc/user-guide-admin/section_cli_nova_specify_host.xml6(title) +msgid "Select hosts where instances are launched" +msgstr "" + +#: ./doc/user-guide-admin/section_cli_nova_specify_host.xml7(para) +msgid "" +"With the appropriate permissions, you can select which host instances are " +"launched on and which roles can boot instances on this host." +msgstr "" + +#: ./doc/user-guide-admin/section_cli_nova_specify_host.xml12(para) +msgid "" +"To select the host where instances are launched, use the " +"--availability_zone " +"zone:host " +"parameter on the command," +msgstr "" + +#: ./doc/user-guide-admin/section_cli_nova_specify_host.xml20(para) +msgid "" +"To specify which roles can launch an instance on a specified host, enable " +"the create:forced_host option in the " +"policy.json file. By default, this option is enabled " +"for only the admin role." +msgstr "" + +#: ./doc/user-guide-admin/section_cli_nova_specify_host.xml27(para) +msgid "" +"To view the list of valid compute hosts, use the command, " +"as follows:" +msgstr "" + +#: ./doc/user-guide-admin/section_cli_nova_specify_host.xml44(para) +msgid "" +"Beginning in the Folsom release, the --availability_zone " +"zone:host " +"parameter replaces the --force_hosts scheduler hint " +"parameter." +msgstr "" + +#: ./doc/user-guide-admin/section_cli_nova_specify_host.xml52(para) +msgid "" +"Beginning in the Grizzly release, you can enable the " +"create:forced_host option in the " +"policy.json file to specify which roles can launch an " +"instance on a specified host." +msgstr "" + +#: ./doc/user-guide-admin/ch_dashboard.xml10(title) +msgid "Dashboard" +msgstr "" + +#: ./doc/user-guide-admin/ch_dashboard.xml12(para) +msgid "" +"As a cloud administrative user, the OpenStack dashboard lets you create and " +"manage projects, users, images, and flavors. You can also set quotas and " +"create and manage services. For information about using the dashboard to " +"perform end user tasks, see the OpenStack End User Guide." +msgstr "" + +#: ./doc/user-guide-admin/section_cli_admin_manage_stacks.xml15(para) +msgid "For information about the:" +msgstr "" + +#: ./doc/user-guide-admin/section_cli_admin_manage_stacks.xml19(para) +msgid "" +"Basic creation and deletion of Orchestration stacks, refer to the End User Guide." +msgstr "" + +#: ./doc/user-guide-admin/section_cli_admin_manage_stacks.xml23(para) +msgid "" +"heat CLI commands, see " +msgstr "" + +#: ./doc/user-guide-admin/section_cli_admin_manage_stacks.xml27(para) +msgid "" +"As an administrator, you can also carry out stack functions on behalf of " +"your users. For example, to resume, suspend, or delete a stack, run:" +msgstr "" + +#: ./doc/user-guide-admin/section_cli_admin_manage_stacks.xml29(replaceable) +#: ./doc/user-guide-admin/section_cli_admin_manage_stacks.xml30(replaceable) +#: ./doc/user-guide-admin/section_cli_admin_manage_stacks.xml31(replaceable) +msgid "stackID" +msgstr "" + +#. Put one translator per line, in the form of NAME , YEAR1, YEAR2 +#: ./doc/user-guide-admin/section_cli_admin_manage_stacks.xml0(None) +msgid "translator-credits" +msgstr "" diff --git a/doc/user-guide-admin/locale/user-guide-admin.pot b/doc/user-guide-admin/locale/user-guide-admin.pot new file mode 100644 index 0000000000..5735260f17 --- /dev/null +++ b/doc/user-guide-admin/locale/user-guide-admin.pot @@ -0,0 +1,2168 @@ +msgid "" +msgstr "" +"Project-Id-Version: PACKAGE VERSION\n" +"POT-Creation-Date: 2014-01-30 06:24+0000\n" +"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n" +"Last-Translator: FULL NAME \n" +"Language-Team: LANGUAGE \n" +"MIME-Version: 1.0\n" +"Content-Type: text/plain; charset=UTF-8\n" +"Content-Transfer-Encoding: 8bit\n" + +#: ./doc/user-guide-admin/section_dashboard_admin_manage_stacks.xml:4(title) ./doc/user-guide-admin/section_cli_admin_manage_stacks.xml:5(title) +msgid "Launch and manage stacks" +msgstr "" + +#: ./doc/user-guide-admin/section_dashboard_admin_manage_stacks.xml:5(para) ./doc/user-guide-admin/section_cli_admin_manage_stacks.xml:6(para) +msgid "The Orchestration service provides a template-based orchestration engine for the OpenStack cloud, which can be used to create and manage cloud infrastructure resources such as storage, networking, instances, and applications as a repeatable running environment." +msgstr "" + +#: ./doc/user-guide-admin/section_dashboard_admin_manage_stacks.xml:10(para) ./doc/user-guide-admin/section_cli_admin_manage_stacks.xml:11(para) +msgid "Templates are used to create stacks, which are collections of resources. For example, a stack might include instances, floating IPs, volumes, security groups, or users. The Orchestration service offers access to all OpenStack core services via a single modular template, with additional orchestration capabilities such as auto-scaling and basic high availability." +msgstr "" + +#: ./doc/user-guide-admin/section_dashboard_admin_manage_stacks.xml:14(para) +msgid "For information about:" +msgstr "" + +#: ./doc/user-guide-admin/section_dashboard_admin_manage_stacks.xml:19(para) +msgid "There are no administration-specific tasks that can be done through the dashboard." +msgstr "" + +#: ./doc/user-guide-admin/section_dashboard_admin_manage_stacks.xml:18(para) +msgid "Administrative tasks on the command line, see . " +msgstr "" + +#: ./doc/user-guide-admin/section_dashboard_admin_manage_stacks.xml:22(para) +msgid "The basic creation and deletion of Orchestration stacks, refer to the End User Guide." +msgstr "" + +#: ./doc/user-guide-admin/section_dashboard_admin_manage_volumes.xml:14(title) +msgid "Manage volumes and volume types" +msgstr "" + +#: ./doc/user-guide-admin/section_dashboard_admin_manage_volumes.xml:15(para) +msgid "Volumes are the Block Storage devices that you attach to instances to enable persistent storage. Users can attach a volume to a running instance or detach a volume and attach it to another instance at any time. For information about using the dashboard to create and manage volumes as an end user, see the OpenStack End User Guide." +msgstr "" + +#: ./doc/user-guide-admin/section_dashboard_admin_manage_volumes.xml:24(para) +msgid "As an administrative user, you can manage volumes and volume types for users in various projects. You can create and delete volume types, and you can view and delete volumes." +msgstr "" + +#: ./doc/user-guide-admin/section_dashboard_admin_manage_volumes.xml:28(title) +msgid "Create a volume type" +msgstr "" + +#: ./doc/user-guide-admin/section_dashboard_admin_manage_volumes.xml:31(para) ./doc/user-guide-admin/section_dashboard_admin_manage_volumes.xml:58(para) ./doc/user-guide-admin/section_dashboard_admin_manage_volumes.xml:93(para) ./doc/user-guide-admin/section_dashboard_admin_manage_instances.xml:28(para) ./doc/user-guide-admin/section_dashboard_admin_manage_instances.xml:67(para) ./doc/user-guide-admin/section_dashboard_admin_manage_instances.xml:111(para) ./doc/user-guide-admin/section_dashboard_admin_manage_projects_users.xml:66(para) ./doc/user-guide-admin/section_dashboard_admin_manage_projects_users.xml:225(para) +msgid "Log in to the dashboard and choose the admin project from the CURRENT PROJECT drop-down list." +msgstr "" + +#: ./doc/user-guide-admin/section_dashboard_admin_manage_volumes.xml:37(para) ./doc/user-guide-admin/section_dashboard_admin_manage_volumes.xml:64(para) ./doc/user-guide-admin/section_dashboard_admin_manage_volumes.xml:99(para) +msgid "On the Admin tab, click the Volumes category." +msgstr "" + +#: ./doc/user-guide-admin/section_dashboard_admin_manage_volumes.xml:41(para) +msgid "Click Create Volume Type." +msgstr "" + +#: ./doc/user-guide-admin/section_dashboard_admin_manage_volumes.xml:43(para) +msgid "In the Create Volume Type window, enter a name for the volume type." +msgstr "" + +#: ./doc/user-guide-admin/section_dashboard_admin_manage_volumes.xml:47(para) +msgid "Click Create Volume Type to confirm your changes." +msgstr "" + +#: ./doc/user-guide-admin/section_dashboard_admin_manage_volumes.xml:53(title) +msgid "Delete volume types" +msgstr "" + +#: ./doc/user-guide-admin/section_dashboard_admin_manage_volumes.xml:54(para) +msgid "When you delete a volume type, volumes of that type are not deleted." +msgstr "" + +#: ./doc/user-guide-admin/section_dashboard_admin_manage_volumes.xml:68(para) +msgid "Select the volume type or types that you want to delete." +msgstr "" + +#: ./doc/user-guide-admin/section_dashboard_admin_manage_volumes.xml:72(para) +msgid "Click Delete Volume Types." +msgstr "" + +#: ./doc/user-guide-admin/section_dashboard_admin_manage_volumes.xml:76(para) +msgid "In the Confirm Delete Volume Types window, click Delete Volume Types to confirm the action." +msgstr "" + +#: ./doc/user-guide-admin/section_dashboard_admin_manage_volumes.xml:82(para) ./doc/user-guide-admin/section_dashboard_admin_manage_volumes.xml:117(para) +msgid "A message indicates whether the action succeeded." +msgstr "" + +#: ./doc/user-guide-admin/section_dashboard_admin_manage_volumes.xml:88(title) +msgid "Delete volumes" +msgstr "" + +#: ./doc/user-guide-admin/section_dashboard_admin_manage_volumes.xml:89(para) +msgid "When you delete an instance, the data of its attached volumes is not destroyed." +msgstr "" + +#: ./doc/user-guide-admin/section_dashboard_admin_manage_volumes.xml:103(para) +msgid "Select the volume or volumes that you want to delete." +msgstr "" + +#: ./doc/user-guide-admin/section_dashboard_admin_manage_volumes.xml:107(para) +msgid "Click Delete Volumes." +msgstr "" + +#: ./doc/user-guide-admin/section_dashboard_admin_manage_volumes.xml:111(para) +msgid "In the Confirm Delete Volumes window, click Delete Volumes to confirm the action." +msgstr "" + +#: ./doc/user-guide-admin/section_cli_nova_manage_flavors.xml:7(title) ./doc/user-guide-admin/section_dashboard_admin_manage_flavors.xml:7(title) +msgid "Manage flavors" +msgstr "" + +#: ./doc/user-guide-admin/section_cli_nova_manage_flavors.xml:8(para) +msgid "In OpenStack, flavors define the compute, memory, and storage capacity of nova computing instances. To put it simply, a flavor is an available hardware configuration for a server. It defines the size of a virtual server that can be launched." +msgstr "" + +#: ./doc/user-guide-admin/section_cli_nova_manage_flavors.xml:13(para) ./doc/user-guide-admin/section_dashboard_admin_manage_flavors.xml:14(para) +msgid "A flavor consists of the following parameters:" +msgstr "" + +#: ./doc/user-guide-admin/section_cli_nova_manage_flavors.xml:16(term) +msgid "Flavor ID" +msgstr "" + +#: ./doc/user-guide-admin/section_cli_nova_manage_flavors.xml:18(para) +msgid "Automatically generated by OpenStack. For private flavors, a value from 1 to 255." +msgstr "" + +#: ./doc/user-guide-admin/section_cli_nova_manage_flavors.xml:23(term) ./doc/user-guide-admin/section_cli_keystone_manage_projects_users_roles.xml:43(para) ./doc/user-guide-admin/section_dashboard_admin_manage_flavors.xml:139(guilabel) ./doc/user-guide-admin/section_dashboard_admin_manage_images.xml:48(guilabel) +msgid "Name" +msgstr "" + +#: ./doc/user-guide-admin/section_cli_nova_manage_flavors.xml:25(para) +msgid "Name for the new flavor." +msgstr "" + +#: ./doc/user-guide-admin/section_cli_nova_manage_flavors.xml:29(term) ./doc/user-guide-admin/section_dashboard_admin_manage_flavors.xml:36(para) ./doc/user-guide-admin/section_dashboard_admin_manage_flavors.xml:147(guilabel) ./doc/user-guide-admin/section_dashboard_admin_set_quotas.xml:129(para) +msgid "VCPUs" +msgstr "" + +#: ./doc/user-guide-admin/section_cli_nova_manage_flavors.xml:31(para) ./doc/user-guide-admin/section_dashboard_admin_manage_flavors.xml:39(para) +msgid "Number of virtual CPUs to use." +msgstr "" + +#: ./doc/user-guide-admin/section_cli_nova_manage_flavors.xml:35(term) +msgid "Memory MB" +msgstr "" + +#: ./doc/user-guide-admin/section_cli_nova_manage_flavors.xml:37(para) +msgid "Amount of RAM to use (in megabytes)." +msgstr "" + +#: ./doc/user-guide-admin/section_cli_nova_manage_flavors.xml:41(term) ./doc/user-guide-admin/section_dashboard_admin_manage_flavors.xml:166(guilabel) +msgid "Root Disk GB" +msgstr "" + +#: ./doc/user-guide-admin/section_cli_nova_manage_flavors.xml:43(para) ./doc/user-guide-admin/section_dashboard_admin_manage_flavors.xml:55(para) +msgid "Amount of disk space (in gigabytes) to use for the root (/) partition." +msgstr "" + +#: ./doc/user-guide-admin/section_cli_nova_manage_flavors.xml:48(term) ./doc/user-guide-admin/section_dashboard_admin_manage_flavors.xml:177(guilabel) +msgid "Ephemeral Disk GB" +msgstr "" + +#: ./doc/user-guide-admin/section_cli_nova_manage_flavors.xml:50(para) ./doc/user-guide-admin/section_dashboard_admin_manage_flavors.xml:64(para) +msgid "Amount of disk space (in gigabytes) to use for the ephemeral partition. If unspecified, the value is 0 by default." +msgstr "" + +#: ./doc/user-guide-admin/section_cli_nova_manage_flavors.xml:53(para) ./doc/user-guide-admin/section_dashboard_admin_manage_flavors.xml:67(para) ./doc/user-guide-admin/section_dashboard_admin_manage_flavors.xml:186(para) +msgid "Ephemeral disks offer machine local disk storage linked to the life cycle of a VM instance. When a VM is terminated, all data on the ephemeral disk is lost. Ephemeral disks are not included in any snapshots." +msgstr "" + +#: ./doc/user-guide-admin/section_cli_nova_manage_flavors.xml:61(term) +msgid "Swap" +msgstr "" + +#: ./doc/user-guide-admin/section_cli_nova_manage_flavors.xml:63(para) +msgid "Amount of swap space (in megabytes) to use. If unspecified, the value is 0 by default." +msgstr "" + +#: ./doc/user-guide-admin/section_cli_nova_manage_flavors.xml:68(para) ./doc/user-guide-admin/section_dashboard_admin_manage_flavors.xml:94(para) +msgid "The default flavors are:" +msgstr "" + +#: ./doc/user-guide-admin/section_cli_nova_manage_flavors.xml:71(para) ./doc/user-guide-admin/section_dashboard_admin_manage_flavors.xml:97(para) +msgid "m1.tiny (1 VCPU/0 GB Disk/512 MB RAM)" +msgstr "" + +#: ./doc/user-guide-admin/section_cli_nova_manage_flavors.xml:74(para) +msgid "m1.smaller (1 VCPU/0 GB Disk/1024 MB RAM)" +msgstr "" + +#: ./doc/user-guide-admin/section_cli_nova_manage_flavors.xml:77(para) +msgid "m1.small (1 VCPU/10 GB Disk/2048 MB RAM)" +msgstr "" + +#: ./doc/user-guide-admin/section_cli_nova_manage_flavors.xml:80(para) +msgid "m1.medium (2 VCPU/10 GB Disk/3072 MB RAM)" +msgstr "" + +#: ./doc/user-guide-admin/section_cli_nova_manage_flavors.xml:83(para) +msgid "m1.large (4 VCPU/10 GB Disk/8192 MB RAM)" +msgstr "" + +#: ./doc/user-guide-admin/section_cli_nova_manage_flavors.xml:86(para) +msgid "m1.xlarge (8 VCPU/10 GB Disk/8192 MB RAM)" +msgstr "" + +#: ./doc/user-guide-admin/section_cli_nova_manage_flavors.xml:89(para) +msgid "You can create and manage flavors with the nova commands provided by the python-novaclient package." +msgstr "" + +#: ./doc/user-guide-admin/section_cli_nova_manage_flavors.xml:93(title) +msgid "Create a flavor" +msgstr "" + +#: ./doc/user-guide-admin/section_cli_nova_manage_flavors.xml:96(para) +msgid "List flavors to show the ID and name, the amount of memory, the amount of disk space for the root partition and for the ephemeral partition, the swap, and the number of virtual CPUs for each flavor." +msgstr "" + +#: ./doc/user-guide-admin/section_cli_nova_manage_flavors.xml:105(para) +msgid "To create a flavor, specify a name, ID, RAM size, disk size, and the number of VCPUs for the flavor, as follows:" +msgstr "" + +#: ./doc/user-guide-admin/section_cli_nova_manage_flavors.xml:108(replaceable) +msgid "FLAVOR_NAME" +msgstr "" + +#: ./doc/user-guide-admin/section_cli_nova_manage_flavors.xml:108(replaceable) ./doc/user-guide-admin/section_cli_nova_manage_flavors.xml:131(replaceable) +msgid "FLAVOR_ID" +msgstr "" + +#: ./doc/user-guide-admin/section_cli_nova_manage_flavors.xml:108(replaceable) +msgid "RAM_IN_MB ROOT_DISK_IN_GB" +msgstr "" + +#: ./doc/user-guide-admin/section_cli_nova_manage_flavors.xml:108(replaceable) +msgid "NUMBER_OF_VCPUS" +msgstr "" + +#: ./doc/user-guide-admin/section_cli_nova_manage_flavors.xml:110(para) +msgid "The flavor ID is a number from 1 to 255 and cannot contain special characters or spaces." +msgstr "" + +#: ./doc/user-guide-admin/section_cli_nova_manage_flavors.xml:114(para) +msgid "For a list of optional parameters, run this command:" +msgstr "" + +#: ./doc/user-guide-admin/section_cli_nova_manage_flavors.xml:119(para) +msgid "After you create a flavor, assign it to a project by specifying the flavor name or ID and the tenant ID:" +msgstr "" + +#: ./doc/user-guide-admin/section_cli_nova_manage_flavors.xml:122(replaceable) +msgid "FLAVOR" +msgstr "" + +#: ./doc/user-guide-admin/section_cli_nova_manage_flavors.xml:122(replaceable) ./doc/user-guide-admin/section_cli_keystone_manage_projects_users_roles.xml:347(replaceable) ./doc/user-guide-admin/section_cli_keystone_manage_projects_users_roles.xml:351(replaceable) ./doc/user-guide-admin/section_cli_keystone_manage_projects_users_roles.xml:371(replaceable) ./doc/user-guide-admin/section_cli_keystone_manage_projects_users_roles.xml:376(replaceable) +msgid "TENANT_ID" +msgstr "" + +#: ./doc/user-guide-admin/section_cli_nova_manage_flavors.xml:127(title) +msgid "Delete a flavor" +msgstr "" + +#: ./doc/user-guide-admin/section_cli_nova_manage_flavors.xml:130(para) +msgid "Delete a specified flavor, as follows:" +msgstr "" + +#: ./doc/user-guide-admin/bk-admin-user-guide.xml:12(title) +msgid "OpenStack Admin User Guide" +msgstr "" + +#: ./doc/user-guide-admin/bk-admin-user-guide.xml:13(titleabbrev) +msgid "Admin User Guide" +msgstr "" + +#: ./doc/user-guide-admin/bk-admin-user-guide.xml:21(orgname) ./doc/user-guide-admin/bk-admin-user-guide.xml:26(holder) +msgid "OpenStack Foundation" +msgstr "" + +#: ./doc/user-guide-admin/bk-admin-user-guide.xml:25(year) +msgid "2013" +msgstr "" + +#: ./doc/user-guide-admin/bk-admin-user-guide.xml:28(releaseinfo) +msgid "havana" +msgstr "" + +#: ./doc/user-guide-admin/bk-admin-user-guide.xml:29(productname) +msgid "OpenStack" +msgstr "" + +#: ./doc/user-guide-admin/bk-admin-user-guide.xml:33(remark) +msgid "Copyright details are filled in by the template." +msgstr "" + +#: ./doc/user-guide-admin/bk-admin-user-guide.xml:38(para) +msgid "OpenStack is an open source cloud computing platform for public and private clouds. A series of interrelated projects deliver a cloud infrastructure solution. This guide shows OpenStack admin users how to create and manage resources in an OpenStack cloud with the OpenStack dashboard or OpenStack client commands." +msgstr "" + +#: ./doc/user-guide-admin/bk-admin-user-guide.xml:48(date) +msgid "2013-10-17" +msgstr "" + +#: ./doc/user-guide-admin/bk-admin-user-guide.xml:52(para) +msgid "Havana release." +msgstr "" + +#: ./doc/user-guide-admin/bk-admin-user-guide.xml:58(date) +msgid "2013-08-31" +msgstr "" + +#: ./doc/user-guide-admin/bk-admin-user-guide.xml:62(para) +msgid "First edition of this document." +msgstr "" + +#: ./doc/user-guide-admin/section_cli_nova_floating_ips.xml:6(title) +msgid "Manage IP addresses" +msgstr "" + +#: ./doc/user-guide-admin/section_cli_nova_floating_ips.xml:7(para) +msgid "Each instance can have a private, or fixed, IP address and an IP address, often public, that is movable from instance to instance called a floating IP address." +msgstr "" + +#: ./doc/user-guide-admin/section_cli_nova_floating_ips.xml:12(para) +msgid "Private IP addresses are used for communication between instances and public ones are used for communication with the outside world." +msgstr "" + +#: ./doc/user-guide-admin/section_cli_nova_floating_ips.xml:15(para) +msgid "When you launch an instance, it is automatically assigned a private IP address that stays the same until you explicitly terminate the instance. Rebooting an instance has no effect on its private IP address." +msgstr "" + +#: ./doc/user-guide-admin/section_cli_nova_floating_ips.xml:19(para) +msgid "The cloud operator must configure a pool of floating IP addresses. Then, you can allocate a certain number of floating IP addresses from this pool to a project. A project quota defines the maximum number of floating IP addresses for the project." +msgstr "" + +#: ./doc/user-guide-admin/section_cli_nova_floating_ips.xml:24(para) +msgid "You can add a floating IP address from this pool to an instance in the project. You can dynamically associate floating IP addresses with or disassociate floating IP addresses from instances in the same project at any time." +msgstr "" + +#: ./doc/user-guide-admin/section_cli_nova_floating_ips.xml:29(para) +msgid "Before you can assign a floating IP address to an instance, you must allocate floating IP addresses to a project. After you allocate floating IP addresses to the current project, you can assign them to running instances." +msgstr "" + +#: ./doc/user-guide-admin/section_cli_nova_floating_ips.xml:33(para) +msgid "You can assign one floating IP address to only one instance at a time. Use the commands to manage floating IP addresses." +msgstr "" + +#: ./doc/user-guide-admin/section_cli_nova_floating_ips.xml:37(title) +msgid "To manage floating IP addresses" +msgstr "" + +#: ./doc/user-guide-admin/section_cli_nova_floating_ips.xml:39(para) +msgid "To list the floating IP address pools:" +msgstr "" + +#: ./doc/user-guide-admin/section_cli_nova_floating_ips.xml:48(para) +msgid "If this list is empty, the cloud operator must configure a pool of floating IP addresses." +msgstr "" + +#: ./doc/user-guide-admin/section_cli_nova_floating_ips.xml:53(para) +msgid "To allocate a floating IP address to the current project:" +msgstr "" + +#: ./doc/user-guide-admin/section_cli_nova_floating_ips.xml:61(para) +msgid "By default, the floating IP address is allocated from the public pool. The command shows the allocated IP address." +msgstr "" + +#: ./doc/user-guide-admin/section_cli_nova_floating_ips.xml:64(para) +msgid "If more than one IP address pool is available, you can specify the pool from which to allocate the address:" +msgstr "" + +#: ./doc/user-guide-admin/section_cli_nova_floating_ips.xml:67(replaceable) +msgid "POOL_NAME" +msgstr "" + +#: ./doc/user-guide-admin/section_cli_nova_floating_ips.xml:70(para) +msgid "To list floating IP addresses that are allocated to the current project:" +msgstr "" + +#: ./doc/user-guide-admin/section_cli_nova_floating_ips.xml:79(para) +msgid "For each floating IP address that is allocated to the current project, the command shows the floating IP address, the ID for the instance to which the floating IP address is assigned, the associated fixed IP address, and the pool from which the floating IP address was allocated." +msgstr "" + +#: ./doc/user-guide-admin/section_cli_nova_floating_ips.xml:87(para) +msgid "To associate a floating IP address with an instance, first allocate that address to the current project:" +msgstr "" + +#: ./doc/user-guide-admin/section_cli_nova_floating_ips.xml:96(para) +msgid "List instances to get the instance ID:" +msgstr "" + +#: ./doc/user-guide-admin/section_cli_nova_floating_ips.xml:103(para) +msgid "Then, assign the floating IP address to the instance, as follows:" +msgstr "" + +#: ./doc/user-guide-admin/section_cli_nova_floating_ips.xml:106(para) +msgid "Notice that the instance is now associated with two floating IP addresses:" +msgstr "" + +#: ./doc/user-guide-admin/section_cli_nova_floating_ips.xml:114(para) +msgid "To assign a fixed IP address to a floating IP address that you assign to an instance, add the fixed IP address as an optional parameter:" +msgstr "" + +#: ./doc/user-guide-admin/section_cli_nova_floating_ips.xml:117(replaceable) +msgid "FIXED_IP_ADDRESS" +msgstr "" + +#: ./doc/user-guide-admin/section_cli_nova_floating_ips.xml:117(replaceable) +msgid "INSTANCE_NAME_OR_ID" +msgstr "" + +#: ./doc/user-guide-admin/section_cli_nova_floating_ips.xml:117(replaceable) ./doc/user-guide-admin/section_cli_nova_floating_ips.xml:126(replaceable) +msgid "FLOATING_IP_ADDRESS" +msgstr "" + +#: ./doc/user-guide-admin/section_cli_nova_floating_ips.xml:118(para) +msgid "After you assign the floating IP address and configure security group rules for the instance, the instance is publicly available at the floating IP address." +msgstr "" + +#: ./doc/user-guide-admin/section_cli_nova_floating_ips.xml:124(para) +msgid "To release a floating IP address from the current project:" +msgstr "" + +#: ./doc/user-guide-admin/section_cli_nova_floating_ips.xml:127(para) +msgid "The floating IP address is returned to the floating IP address pool that is available to all projects. If a floating IP address is assigned to a running instance, it is automatically disassociated from that instance." +msgstr "" + +#: ./doc/user-guide-admin/section_cli_keystone_manage_projects_users_roles.xml:7(title) +msgid "Manage projects, users, and roles" +msgstr "" + +#: ./doc/user-guide-admin/section_cli_keystone_manage_projects_users_roles.xml:8(para) +msgid "As a cloud administrator, you manage projects, users, and roles. Projects are organizational units in the cloud to which you can assign users. Projects are also known as tenants or accounts. Users can be members of one or more projects. Roles define which actions users can perform. You assign roles to user-project pairs." +msgstr "" + +#: ./doc/user-guide-admin/section_cli_keystone_manage_projects_users_roles.xml:15(para) +msgid "You can define actions for OpenStack service roles in the /etc/PROJECT/policy.json files. For example, define actions for Compute service roles in the /etc/nova/policy.json file." +msgstr "" + +#: ./doc/user-guide-admin/section_cli_keystone_manage_projects_users_roles.xml:19(para) +msgid "You can manage projects, users, and roles independently from each other." +msgstr "" + +#: ./doc/user-guide-admin/section_cli_keystone_manage_projects_users_roles.xml:21(para) +msgid "During cloud set up, the operator defines at least one project, user, and role." +msgstr "" + +#: ./doc/user-guide-admin/section_cli_keystone_manage_projects_users_roles.xml:23(para) +msgid "Learn how to add, update, and delete projects and users, assign users to one or more projects, and change or remove the assignment. To enable or temporarily disable a project or user, you update that project or user. You can also change quotas at the project level." +msgstr "" + +#: ./doc/user-guide-admin/section_cli_keystone_manage_projects_users_roles.xml:28(para) +msgid "Before you can delete a user account, you must remove the user account from its primary project." +msgstr "" + +#: ./doc/user-guide-admin/section_cli_keystone_manage_projects_users_roles.xml:30(para) +msgid "Before you can run keystone client commands, you must download and source an OpenStack RC file. See Download and source the OpenStack RC file." +msgstr "" + +#: ./doc/user-guide-admin/section_cli_keystone_manage_projects_users_roles.xml:35(title) +msgid "Services" +msgstr "" + +#: ./doc/user-guide-admin/section_cli_keystone_manage_projects_users_roles.xml:36(para) +msgid "To look at your service catalog, use these keystone client commands." +msgstr "" + +#: ./doc/user-guide-admin/section_cli_keystone_manage_projects_users_roles.xml:39(literal) +msgid "service-create" +msgstr "" + +#: ./doc/user-guide-admin/section_cli_keystone_manage_projects_users_roles.xml:40(para) +msgid "Keyword arguments:" +msgstr "" + +#: ./doc/user-guide-admin/section_cli_keystone_manage_projects_users_roles.xml:46(para) +msgid "Type" +msgstr "" + +#: ./doc/user-guide-admin/section_cli_keystone_manage_projects_users_roles.xml:49(para) ./doc/user-guide-admin/section_dashboard_admin_manage_flavors.xml:22(th) ./doc/user-guide-admin/section_dashboard_admin_manage_images.xml:52(guilabel) +msgid "Description" +msgstr "" + +#: ./doc/user-guide-admin/section_cli_keystone_manage_projects_users_roles.xml:52(para) ./doc/user-guide-admin/section_cli_keystone_manage_projects_users_roles.xml:67(para) ./doc/user-guide-admin/section_cli_keystone_manage_projects_users_roles.xml:78(para) ./doc/user-guide-admin/section_cli_keystone_manage_projects_users_roles.xml:89(para) +msgid "Example:" +msgstr "" + +#: ./doc/user-guide-admin/section_cli_keystone_manage_projects_users_roles.xml:60(literal) +msgid "service-list" +msgstr "" + +#: ./doc/user-guide-admin/section_cli_keystone_manage_projects_users_roles.xml:61(para) ./doc/user-guide-admin/section_cli_keystone_manage_projects_users_roles.xml:72(para) ./doc/user-guide-admin/section_cli_keystone_manage_projects_users_roles.xml:83(para) +msgid "Arguments" +msgstr "" + +#: ./doc/user-guide-admin/section_cli_keystone_manage_projects_users_roles.xml:64(para) ./doc/user-guide-admin/section_cli_keystone_manage_projects_users_roles.xml:75(para) ./doc/user-guide-admin/section_cli_keystone_manage_projects_users_roles.xml:86(para) +msgid "service_id" +msgstr "" + +#: ./doc/user-guide-admin/section_cli_keystone_manage_projects_users_roles.xml:71(literal) +msgid "service-get" +msgstr "" + +#: ./doc/user-guide-admin/section_cli_keystone_manage_projects_users_roles.xml:82(literal) +msgid "service-delete" +msgstr "" + +#: ./doc/user-guide-admin/section_cli_keystone_manage_projects_users_roles.xml:93(title) +msgid "Create a tenant (project)" +msgstr "" + +#: ./doc/user-guide-admin/section_cli_keystone_manage_projects_users_roles.xml:94(para) +msgid "A tenant is a group of zero or more users. In nova, a tenant owns virtual machines. In swift, a tenant owns containers. In the Dashboard, tenants are represented as projects. Users can be associated with more than one tenant. Each tenant and user pairing can have a role associated with it." +msgstr "" + +#: ./doc/user-guide-admin/section_cli_keystone_manage_projects_users_roles.xml:102(para) +msgid "To list all projects with their ID, name, and whether they are enabled or disabled:" +msgstr "" + +#: ./doc/user-guide-admin/section_cli_keystone_manage_projects_users_roles.xml:118(para) +msgid "Create a project named new-project:" +msgstr "" + +#: ./doc/user-guide-admin/section_cli_keystone_manage_projects_users_roles.xml:121(para) +msgid "By default, the project is enabled." +msgstr "" + +#: ./doc/user-guide-admin/section_cli_keystone_manage_projects_users_roles.xml:130(para) +msgid "Note the ID for the project so you can update it in the next procedure." +msgstr "" + +#: ./doc/user-guide-admin/section_cli_keystone_manage_projects_users_roles.xml:136(title) ./doc/user-guide-admin/section_dashboard_admin_manage_projects_users.xml:104(title) +msgid "Update a project" +msgstr "" + +#: ./doc/user-guide-admin/section_cli_keystone_manage_projects_users_roles.xml:137(para) +msgid "Specify the project ID to update a project. You can update the name, description, and enabled status of a project." +msgstr "" + +#: ./doc/user-guide-admin/section_cli_keystone_manage_projects_users_roles.xml:142(para) +msgid "To temporarily disable a project:" +msgstr "" + +#: ./doc/user-guide-admin/section_cli_keystone_manage_projects_users_roles.xml:143(replaceable) ./doc/user-guide-admin/section_cli_keystone_manage_projects_users_roles.xml:147(replaceable) ./doc/user-guide-admin/section_cli_keystone_manage_projects_users_roles.xml:151(replaceable) ./doc/user-guide-admin/section_cli_keystone_manage_projects_users_roles.xml:156(replaceable) ./doc/user-guide-admin/section_cli_keystone_manage_projects_users_roles.xml:173(replaceable) +msgid "PROJECT_ID" +msgstr "" + +#: ./doc/user-guide-admin/section_cli_keystone_manage_projects_users_roles.xml:146(para) +msgid "To enable a disabled project:" +msgstr "" + +#: ./doc/user-guide-admin/section_cli_keystone_manage_projects_users_roles.xml:150(para) +msgid "To update the name of a project:" +msgstr "" + +#: ./doc/user-guide-admin/section_cli_keystone_manage_projects_users_roles.xml:154(para) +msgid "To verify your changes, show information for the updated project:" +msgstr "" + +#: ./doc/user-guide-admin/section_cli_keystone_manage_projects_users_roles.xml:169(title) +msgid "Delete a project" +msgstr "" + +#: ./doc/user-guide-admin/section_cli_keystone_manage_projects_users_roles.xml:172(para) +msgid "To delete a project:" +msgstr "" + +#: ./doc/user-guide-admin/section_cli_keystone_manage_projects_users_roles.xml:178(title) +msgid "Create a user" +msgstr "" + +#: ./doc/user-guide-admin/section_cli_keystone_manage_projects_users_roles.xml:181(para) +msgid "To list all users:" +msgstr "" + +#: ./doc/user-guide-admin/section_cli_keystone_manage_projects_users_roles.xml:183(para) +msgid "The output shows the ID, name, enabled status, and e-mail address for each user:" +msgstr "" + +#: ./doc/user-guide-admin/section_cli_keystone_manage_projects_users_roles.xml:196(para) +msgid "To create a user, you must specify a name. Optionally, you can specify a tenant ID, password, and email address. It is recommended that you include the tenant ID and password because the user cannot log in to the dashboard without this information." +msgstr "" + +#: ./doc/user-guide-admin/section_cli_keystone_manage_projects_users_roles.xml:202(para) +msgid "To create the new-user user:" +msgstr "" + +#: ./doc/user-guide-admin/section_cli_keystone_manage_projects_users_roles.xml:204(replaceable) +msgid "PASSWORD" +msgstr "" + +#: ./doc/user-guide-admin/section_cli_keystone_manage_projects_users_roles.xml:218(title) +msgid "Update a user" +msgstr "" + +#: ./doc/user-guide-admin/section_cli_keystone_manage_projects_users_roles.xml:219(para) +msgid "You can update the name, email address, and enabled status for a user." +msgstr "" + +#: ./doc/user-guide-admin/section_cli_keystone_manage_projects_users_roles.xml:223(para) +msgid "To temporarily disable a user account:" +msgstr "" + +#: ./doc/user-guide-admin/section_cli_keystone_manage_projects_users_roles.xml:225(replaceable) ./doc/user-guide-admin/section_cli_keystone_manage_projects_users_roles.xml:233(replaceable) ./doc/user-guide-admin/section_cli_keystone_manage_projects_users_roles.xml:238(replaceable) ./doc/user-guide-admin/section_cli_keystone_manage_projects_users_roles.xml:248(replaceable) ./doc/user-guide-admin/section_cli_keystone_manage_projects_users_roles.xml:347(replaceable) ./doc/user-guide-admin/section_cli_keystone_manage_projects_users_roles.xml:351(replaceable) ./doc/user-guide-admin/section_cli_keystone_manage_projects_users_roles.xml:371(replaceable) ./doc/user-guide-admin/section_cli_keystone_manage_projects_users_roles.xml:376(replaceable) +msgid "USER_ID" +msgstr "" + +#: ./doc/user-guide-admin/section_cli_keystone_manage_projects_users_roles.xml:226(para) +msgid "If you disable a user account, the user cannot log in to the dashboard. However, data for the user account is maintained, so you can enable the user at any time." +msgstr "" + +#: ./doc/user-guide-admin/section_cli_keystone_manage_projects_users_roles.xml:232(para) +msgid "To enable a disabled user account:" +msgstr "" + +#: ./doc/user-guide-admin/section_cli_keystone_manage_projects_users_roles.xml:236(para) +msgid "To change the name and description for a user account:" +msgstr "" + +#: ./doc/user-guide-admin/section_cli_keystone_manage_projects_users_roles.xml:244(title) +msgid "Delete a user" +msgstr "" + +#: ./doc/user-guide-admin/section_cli_keystone_manage_projects_users_roles.xml:247(para) +msgid "To delete a specified user account:" +msgstr "" + +#: ./doc/user-guide-admin/section_cli_keystone_manage_projects_users_roles.xml:253(title) +msgid "Create and assign a role" +msgstr "" + +#: ./doc/user-guide-admin/section_cli_keystone_manage_projects_users_roles.xml:254(para) +msgid "Users can be members of multiple projects. To assign users to multiple projects, define a role and assign that role to a user-project pair." +msgstr "" + +#: ./doc/user-guide-admin/section_cli_keystone_manage_projects_users_roles.xml:259(para) +msgid "To list the available roles:" +msgstr "" + +#: ./doc/user-guide-admin/section_cli_keystone_manage_projects_users_roles.xml:272(para) +msgid "To create the new-role role:" +msgstr "" + +#: ./doc/user-guide-admin/section_cli_keystone_manage_projects_users_roles.xml:283(para) +msgid "To assign a user to a project, you must assign the role to a user-project pair. To do this, you need the user, role, and project IDs." +msgstr "" + +#: ./doc/user-guide-admin/section_cli_keystone_manage_projects_users_roles.xml:289(para) +msgid "To list users:" +msgstr "" + +#: ./doc/user-guide-admin/section_cli_keystone_manage_projects_users_roles.xml:301(para) +msgid "Note the ID of the user to which you want to assign the role." +msgstr "" + +#: ./doc/user-guide-admin/section_cli_keystone_manage_projects_users_roles.xml:305(para) +msgid "To list role IDs:" +msgstr "" + +#: ./doc/user-guide-admin/section_cli_keystone_manage_projects_users_roles.xml:317(para) +msgid "Note the ID of the role that you want to assign." +msgstr "" + +#: ./doc/user-guide-admin/section_cli_keystone_manage_projects_users_roles.xml:321(para) +msgid "To list projects:" +msgstr "" + +#: ./doc/user-guide-admin/section_cli_keystone_manage_projects_users_roles.xml:335(para) +msgid "Note the ID of the project to which you want to assign the role." +msgstr "" + +#: ./doc/user-guide-admin/section_cli_keystone_manage_projects_users_roles.xml:341(para) +msgid "Assign a role to a user-project pair. In this example, you assign the new-role role to the demo and test-project pair:" +msgstr "" + +#: ./doc/user-guide-admin/section_cli_keystone_manage_projects_users_roles.xml:347(replaceable) ./doc/user-guide-admin/section_cli_keystone_manage_projects_users_roles.xml:360(replaceable) ./doc/user-guide-admin/section_cli_keystone_manage_projects_users_roles.xml:371(replaceable) +msgid "ROLE_ID" +msgstr "" + +#: ./doc/user-guide-admin/section_cli_keystone_manage_projects_users_roles.xml:350(para) +msgid "To verify the role assignment:" +msgstr "" + +#: ./doc/user-guide-admin/section_cli_keystone_manage_projects_users_roles.xml:359(para) +msgid "To get details for a specified role:" +msgstr "" + +#: ./doc/user-guide-admin/section_cli_keystone_manage_projects_users_roles.xml:369(para) +msgid "To remove a role from a user-project pair:" +msgstr "" + +#: ./doc/user-guide-admin/section_cli_keystone_manage_projects_users_roles.xml:374(para) +msgid "To verify the role removal, run the following command:" +msgstr "" + +#: ./doc/user-guide-admin/section_cli_keystone_manage_projects_users_roles.xml:377(para) +msgid "If the role was removed, the command output omits the removed role." +msgstr "" + +#: ./doc/user-guide-admin/section_dashboard_admin_manage_resources.xml:13(title) +msgid "View cloud resources" +msgstr "" + +#. When image changes, this message will be marked fuzzy or untranslated for you. +#. It doesn't matter what you translate it to: it's not used at all. +#: ./doc/user-guide-admin/section_dashboard_admin_manage_instances.xml:95(None) +msgid "@@image: '../common/figures/change_instance_state.png'; md5=d9eef0f7a1f99eee18a99e677c7c710b" +msgstr "" + +#: ./doc/user-guide-admin/section_dashboard_admin_manage_instances.xml:13(title) +msgid "Manage instances" +msgstr "" + +#: ./doc/user-guide-admin/section_dashboard_admin_manage_instances.xml:14(para) +msgid "As an administrative user, you can manage instances for users in various projects. You can view, terminate, edit, perform a soft or hard reboot, create a snapshot from, and migrate instances. You can also view the logs for instances or launch a VNC console for an instance." +msgstr "" + +#: ./doc/user-guide-admin/section_dashboard_admin_manage_instances.xml:19(para) +msgid "For information about using the dashboard to launch instances as an end user, see the OpenStack End User Guide." +msgstr "" + +#: ./doc/user-guide-admin/section_dashboard_admin_manage_instances.xml:25(title) +msgid "Create instance snapshots" +msgstr "" + +#: ./doc/user-guide-admin/section_dashboard_admin_manage_instances.xml:34(para) ./doc/user-guide-admin/section_dashboard_admin_manage_instances.xml:73(para) ./doc/user-guide-admin/section_dashboard_admin_manage_instances.xml:117(para) +msgid "On the Admin tab, click the Instances category." +msgstr "" + +#: ./doc/user-guide-admin/section_dashboard_admin_manage_instances.xml:39(para) +msgid "Select an instance to create a snapshot from it. From the Actions drop-down list, select Create Snapshot." +msgstr "" + +#: ./doc/user-guide-admin/section_dashboard_admin_manage_instances.xml:45(para) +msgid "In the Create Snapshot window, enter a name for the snapshot. Click Create Snapshot. The dashboard shows the instance snapshot in the Images & Snapshots category." +msgstr "" + +#: ./doc/user-guide-admin/section_dashboard_admin_manage_instances.xml:53(para) +msgid "To launch an instance from the snapshot, select the snapshot and click Launch. For information about launching instances, see the OpenStack End User Guide." +msgstr "" + +#: ./doc/user-guide-admin/section_dashboard_admin_manage_instances.xml:64(title) +msgid "Control the state of an instance" +msgstr "" + +#: ./doc/user-guide-admin/section_dashboard_admin_manage_instances.xml:78(para) +msgid "Select the instance for which you want to change the state." +msgstr "" + +#: ./doc/user-guide-admin/section_dashboard_admin_manage_instances.xml:82(para) +msgid "In the More drop-down list in the Actions column, select the state." +msgstr "" + +#: ./doc/user-guide-admin/section_dashboard_admin_manage_instances.xml:85(para) +msgid "Depending on the current state of the instance, you can choose to pause, un-pause, suspend, resume, soft or hard reboot, or terminate an instance (items in red are disabled)." +msgstr "" + +#: ./doc/user-guide-admin/section_dashboard_admin_manage_instances.xml:90(title) +msgid "Dashboard—Instance Actions" +msgstr "" + +#: ./doc/user-guide-admin/section_dashboard_admin_manage_instances.xml:103(title) +msgid "Track usage" +msgstr "" + +#: ./doc/user-guide-admin/section_dashboard_admin_manage_instances.xml:104(para) +msgid "Use the Overview category to track usage of instances for each project." +msgstr "" + +#: ./doc/user-guide-admin/section_dashboard_admin_manage_instances.xml:106(para) +msgid "You can track costs per month by showing metrics like number of VCPUs, disks, RAM, and uptime of all your instances." +msgstr "" + +#: ./doc/user-guide-admin/section_dashboard_admin_manage_instances.xml:122(para) +msgid "Select a month and click Submit to query the instance usage for that month." +msgstr "" + +#: ./doc/user-guide-admin/section_dashboard_admin_manage_instances.xml:127(para) +msgid "Click Download CSV Summary to download a CSV summary." +msgstr "" + +#: ./doc/user-guide-admin/section_cli_nova_services.xml:6(title) +msgid "Manage Compute services" +msgstr "" + +#: ./doc/user-guide-admin/section_cli_nova_services.xml:7(para) +msgid "You can enable and disable Compute services. The following examples disable and enable the nova-compute service." +msgstr "" + +#: ./doc/user-guide-admin/section_cli_nova_services.xml:12(para) +msgid "List the Compute services:" +msgstr "" + +#: ./doc/user-guide-admin/section_cli_nova_services.xml:26(para) +msgid "Disable a nova service:" +msgstr "" + +#: ./doc/user-guide-admin/section_cli_nova_services.xml:34(para) +msgid "The Havana release introduces the optional --reason parameter that enables you to log a reason for disabling a service." +msgstr "" + +#: ./doc/user-guide-admin/section_cli_nova_services.xml:41(para) ./doc/user-guide-admin/section_cli_nova_services.xml:64(para) +msgid "Check the service list:" +msgstr "" + +#: ./doc/user-guide-admin/section_cli_nova_services.xml:55(para) +msgid "Enable the service:" +msgstr "" + +#: ./doc/user-guide-admin/section_dashboard_admin_manage_projects_security.xml:7(title) ./doc/user-guide-admin/section_cli_nova_manage_projects_security.xml:7(title) +msgid "Manage project security" +msgstr "" + +#: ./doc/user-guide-admin/section_dashboard_admin_manage_projects_security.xml:8(para) ./doc/user-guide-admin/section_cli_nova_manage_projects_security.xml:8(para) +msgid "Security groups are sets of IP filter rules that are applied to all project instances, and which define networking access to the instance. Group rules are project specific; project members can edit the default rules for their group and add new rule sets." +msgstr "" + +#: ./doc/user-guide-admin/section_dashboard_admin_manage_projects_security.xml:13(para) +msgid "All projects have a default security group that is applied to any instance that has no other defined security group. Unless you change the default, this security group denies all incoming traffic and allows only outgoing traffic to your instance." +msgstr "" + +#: ./doc/user-guide-admin/section_dashboard_admin_manage_projects_security.xml:19(para) +msgid "For information about updating global controls on the command line, see ." +msgstr "" + +#: ./doc/user-guide-admin/section_dashboard_admin_manage_projects_security.xml:24(title) ./doc/user-guide-admin/section_cli_nova_manage_projects_security.xml:94(title) +msgid "Create a security group" +msgstr "" + +#: ./doc/user-guide-admin/section_dashboard_admin_manage_projects_security.xml:27(para) ./doc/user-guide-admin/section_dashboard_admin_manage_projects_security.xml:55(para) ./doc/user-guide-admin/section_dashboard_admin_manage_projects_security.xml:244(para) ./doc/user-guide-admin/section_dashboard_admin_manage_projects_security.xml:269(para) +msgid "Log in to the dashboard as a project member." +msgstr "" + +#: ./doc/user-guide-admin/section_dashboard_admin_manage_projects_security.xml:31(para) ./doc/user-guide-admin/section_dashboard_admin_manage_projects_security.xml:59(para) ./doc/user-guide-admin/section_dashboard_admin_manage_projects_security.xml:248(para) +msgid "On the Project tab, select the appropriate project from the CURRENT PROJECT drop-down list, and click the Access & Security category." +msgstr "" + +#: ./doc/user-guide-admin/section_dashboard_admin_manage_projects_security.xml:38(para) +msgid "On the Security Groups tab, click Create Security Group." +msgstr "" + +#: ./doc/user-guide-admin/section_dashboard_admin_manage_projects_security.xml:43(para) +msgid "Provide a name and appropriate description for the group, and click Create Security Group. By default, the new rule provides outgoing access rules for the group." +msgstr "" + +#: ./doc/user-guide-admin/section_dashboard_admin_manage_projects_security.xml:52(title) +msgid "Add a security group rule" +msgstr "" + +#: ./doc/user-guide-admin/section_dashboard_admin_manage_projects_security.xml:66(para) ./doc/user-guide-admin/section_dashboard_admin_manage_projects_security.xml:255(para) +msgid "On the Security Groups tab, click Edit rules for the appropriate security group." +msgstr "" + +#: ./doc/user-guide-admin/section_dashboard_admin_manage_projects_security.xml:71(para) +msgid "To add a rule, click Add Rule. Set the attributes for the rule, and click Add:" +msgstr "" + +#: ./doc/user-guide-admin/section_dashboard_admin_manage_projects_security.xml:114(guilabel) +msgid "IP Protocol" +msgstr "" + +#: ./doc/user-guide-admin/section_dashboard_admin_manage_projects_security.xml:116(para) +msgid "The IP protocol to which the rule applies:" +msgstr "" + +#: ./doc/user-guide-admin/section_dashboard_admin_manage_projects_security.xml:120(para) +msgid "TCP.Typically used to exchange data between systems, and for end-user communication." +msgstr "" + +#: ./doc/user-guide-admin/section_dashboard_admin_manage_projects_security.xml:126(para) +msgid "UDP. Typically used to exchange data between systems, particularly at the application level." +msgstr "" + +#: ./doc/user-guide-admin/section_dashboard_admin_manage_projects_security.xml:132(para) +msgid "ICMP. Typically used by network devices, such as routers, to send error or monitoring messages." +msgstr "" + +#: ./doc/user-guide-admin/section_dashboard_admin_manage_projects_security.xml:154(guilabel) +msgid "Open" +msgstr "" + +#: ./doc/user-guide-admin/section_dashboard_admin_manage_projects_security.xml:156(para) +msgid "For TCP or UDP rules, the Port or Port Range to open for the rule. Choose to open a single port or range of ports." +msgstr "" + +#: ./doc/user-guide-admin/section_dashboard_admin_manage_projects_security.xml:161(para) +msgid "For a range of ports, enter port values in the From Port and To Port fields." +msgstr "" + +#: ./doc/user-guide-admin/section_dashboard_admin_manage_projects_security.xml:165(para) +msgid "For a single port, enter the port value in the Port field." +msgstr "" + +#: ./doc/user-guide-admin/section_dashboard_admin_manage_projects_security.xml:202(guilabel) +msgid "Source" +msgstr "" + +#: ./doc/user-guide-admin/section_dashboard_admin_manage_projects_security.xml:204(para) +msgid "The source of the traffic for this rule:" +msgstr "" + +#: ./doc/user-guide-admin/section_dashboard_admin_manage_projects_security.xml:208(para) +msgid "CIDR (Classless Inter-Domain Routing). IP address block, which limits access to IPs within the block. Enter the CIDR in the Source field." +msgstr "" + +#: ./doc/user-guide-admin/section_dashboard_admin_manage_projects_security.xml:217(para) +msgid "Security Group. Source group that enables any instance in the group to access any other group instance." +msgstr "" + +#: ./doc/user-guide-admin/section_dashboard_admin_manage_projects_security.xml:241(title) +msgid "Delete a security group rule" +msgstr "" + +#: ./doc/user-guide-admin/section_dashboard_admin_manage_projects_security.xml:260(para) +msgid "To delete a rule, select the rule and click Delete Rule." +msgstr "" + +#: ./doc/user-guide-admin/section_dashboard_admin_manage_projects_security.xml:266(title) ./doc/user-guide-admin/section_cli_nova_manage_projects_security.xml:165(title) +msgid "Delete a security group" +msgstr "" + +#: ./doc/user-guide-admin/section_dashboard_admin_manage_projects_security.xml:273(para) +msgid "On the Project tab, select the appropriate project from the CURRENT PROJECT drop-down list, and click the Access & Security category." +msgstr "" + +#: ./doc/user-guide-admin/section_dashboard_admin_manage_projects_security.xml:280(para) +msgid "On the Security Groups tab, select the appropriate group, and click Delete Security Group." +msgstr "" + +#: ./doc/user-guide-admin/section_dashboard_admin_manage_flavors.xml:8(para) +msgid "In OpenStack, a flavor defines the compute, memory, and storage capacity of a virtual server that users can launch. As an administrative user, you can create, edit, and delete flavors." +msgstr "" + +#: ./doc/user-guide-admin/section_dashboard_admin_manage_flavors.xml:12(para) +msgid "Only administrative users can create and manage flavors." +msgstr "" + +#: ./doc/user-guide-admin/section_dashboard_admin_manage_flavors.xml:16(caption) +msgid "Flavor parameters" +msgstr "" + +#: ./doc/user-guide-admin/section_dashboard_admin_manage_flavors.xml:21(th) +msgid "Parameter" +msgstr "" + +#: ./doc/user-guide-admin/section_dashboard_admin_manage_flavors.xml:28(para) +msgid "Flavor Name" +msgstr "" + +#: ./doc/user-guide-admin/section_dashboard_admin_manage_flavors.xml:31(para) +msgid "The flavor name." +msgstr "" + +#: ./doc/user-guide-admin/section_dashboard_admin_manage_flavors.xml:44(para) +msgid "RAM" +msgstr "" + +#: ./doc/user-guide-admin/section_dashboard_admin_manage_flavors.xml:47(para) +msgid "Amount of RAM to use, in megabytes." +msgstr "" + +#: ./doc/user-guide-admin/section_dashboard_admin_manage_flavors.xml:52(para) +msgid "Root Disk" +msgstr "" + +#: ./doc/user-guide-admin/section_dashboard_admin_manage_flavors.xml:61(para) +msgid "Ephemeral Disk" +msgstr "" + +#: ./doc/user-guide-admin/section_dashboard_admin_manage_flavors.xml:76(para) +msgid "Swap Disk" +msgstr "" + +#: ./doc/user-guide-admin/section_dashboard_admin_manage_flavors.xml:79(para) +msgid "Amount of swap space (in megabytes) to use. If unspecified, the default is 0." +msgstr "" + +#: ./doc/user-guide-admin/section_dashboard_admin_manage_flavors.xml:85(para) +msgid "ID" +msgstr "" + +#: ./doc/user-guide-admin/section_dashboard_admin_manage_flavors.xml:88(para) +msgid "The flavor ID, generated by OpenStack." +msgstr "" + +#: ./doc/user-guide-admin/section_dashboard_admin_manage_flavors.xml:100(para) +msgid "m1.small (1 VCPU/20 GB Disk/2048 MB RAM)" +msgstr "" + +#: ./doc/user-guide-admin/section_dashboard_admin_manage_flavors.xml:103(para) +msgid "m1.medium (2 VCPU/40 GB Disk/4096 MB RAM)" +msgstr "" + +#: ./doc/user-guide-admin/section_dashboard_admin_manage_flavors.xml:106(para) +msgid "m1.large (4 VCPU/80 GB Disk/8192 MB RAM)" +msgstr "" + +#: ./doc/user-guide-admin/section_dashboard_admin_manage_flavors.xml:109(para) +msgid "m1.xlarge (8 VCPU/160 GB Disk/16384 MB RAM)" +msgstr "" + +#: ./doc/user-guide-admin/section_dashboard_admin_manage_flavors.xml:113(title) +msgid "Create flavors" +msgstr "" + +#: ./doc/user-guide-admin/section_dashboard_admin_manage_flavors.xml:116(para) ./doc/user-guide-admin/section_dashboard_admin_manage_flavors.xml:220(para) ./doc/user-guide-admin/section_dashboard_admin_manage_flavors.xml:248(para) ./doc/user-guide-admin/section_dashboard_admin_manage_images.xml:27(para) ./doc/user-guide-admin/section_dashboard_admin_manage_images.xml:95(para) ./doc/user-guide-admin/section_dashboard_admin_manage_images.xml:125(para) +msgid "Log in to the dashboard." +msgstr "" + +#: ./doc/user-guide-admin/section_dashboard_admin_manage_flavors.xml:117(para) ./doc/user-guide-admin/section_dashboard_admin_manage_flavors.xml:221(para) ./doc/user-guide-admin/section_dashboard_admin_manage_flavors.xml:249(para) ./doc/user-guide-admin/section_dashboard_admin_manage_images.xml:28(para) ./doc/user-guide-admin/section_dashboard_admin_manage_images.xml:96(para) ./doc/user-guide-admin/section_dashboard_admin_manage_images.xml:126(para) +msgid "Choose the admin project from the CURRENT PROJECT drop-down list." +msgstr "" + +#: ./doc/user-guide-admin/section_dashboard_admin_manage_flavors.xml:122(para) ./doc/user-guide-admin/section_dashboard_admin_manage_flavors.xml:226(para) ./doc/user-guide-admin/section_dashboard_admin_manage_flavors.xml:254(para) +msgid "On the Admin tab, click the Flavors category." +msgstr "" + +#: ./doc/user-guide-admin/section_dashboard_admin_manage_flavors.xml:126(para) ./doc/user-guide-admin/section_dashboard_admin_manage_flavors.xml:211(para) +msgid "Click Create Flavor." +msgstr "" + +#: ./doc/user-guide-admin/section_dashboard_admin_manage_flavors.xml:130(para) +msgid "In the Create Flavor window, enter or select the following values:" +msgstr "" + +#: ./doc/user-guide-admin/section_dashboard_admin_manage_flavors.xml:142(para) +msgid "Enter the flavor name." +msgstr "" + +#: ./doc/user-guide-admin/section_dashboard_admin_manage_flavors.xml:150(para) +msgid "Enter the number of virtual CPUs to use." +msgstr "" + +#: ./doc/user-guide-admin/section_dashboard_admin_manage_flavors.xml:156(guilabel) +msgid "RAM MB" +msgstr "" + +#: ./doc/user-guide-admin/section_dashboard_admin_manage_flavors.xml:160(para) +msgid "Enter the amount of RAM to use, in megabytes." +msgstr "" + +#: ./doc/user-guide-admin/section_dashboard_admin_manage_flavors.xml:170(para) +msgid "Enter the mount of disk space in gigabytes to use for the root (/) partition." +msgstr "" + +#: ./doc/user-guide-admin/section_dashboard_admin_manage_flavors.xml:181(para) +msgid "Enter the amount of disk space in gigabytes to use for the ephemeral partition. If unspecified, the value is 0 by default." +msgstr "" + +#: ./doc/user-guide-admin/section_dashboard_admin_manage_flavors.xml:197(guilabel) +msgid "Swap Disk GB" +msgstr "" + +#: ./doc/user-guide-admin/section_dashboard_admin_manage_flavors.xml:201(para) +msgid "Enter the amount of swap space (in megabytes) to use. If unspecified, the default is 0." +msgstr "" + +#: ./doc/user-guide-admin/section_dashboard_admin_manage_flavors.xml:217(title) +msgid "Update flavors" +msgstr "" + +#: ./doc/user-guide-admin/section_dashboard_admin_manage_flavors.xml:230(para) +msgid "Select the flavor that you want to edit. Click Edit Flavor." +msgstr "" + +#: ./doc/user-guide-admin/section_dashboard_admin_manage_flavors.xml:234(para) +msgid "In the Edit Flavor window, you can change the flavor name, VCPUs, RAM, root dish, ephemeral disk, and swap disk values.." +msgstr "" + +#: ./doc/user-guide-admin/section_dashboard_admin_manage_flavors.xml:240(para) ./doc/user-guide-admin/section_dashboard_admin_manage_projects_users.xml:132(para) ./doc/user-guide-admin/section_dashboard_admin_manage_projects_users.xml:197(para) +msgid "Click Save." +msgstr "" + +#: ./doc/user-guide-admin/section_dashboard_admin_manage_flavors.xml:245(title) +msgid "Delete flavors" +msgstr "" + +#: ./doc/user-guide-admin/section_dashboard_admin_manage_flavors.xml:258(para) +msgid "Select the flavors that you want to delete." +msgstr "" + +#: ./doc/user-guide-admin/section_dashboard_admin_manage_flavors.xml:262(para) +msgid "Click Delete Flavors." +msgstr "" + +#: ./doc/user-guide-admin/section_dashboard_admin_manage_flavors.xml:266(para) +msgid "In the Confirm Delete Flavors window, click Delete Flavors to confirm the deletion. You cannot undo this action." +msgstr "" + +#: ./doc/user-guide-admin/section_cli_nova_manage_projects_security.xml:13(para) +msgid "All projects have a \"default\" security group which is applied to any instance that has no other defined security group. Unless you change the default, this security group denies all incoming traffic and allows only outgoing traffic to your instance." +msgstr "" + +#: ./doc/user-guide-admin/section_cli_nova_manage_projects_security.xml:19(para) +msgid "For information about updating rules using the dashboard, see ." +msgstr "" + +#: ./doc/user-guide-admin/section_cli_nova_manage_projects_security.xml:23(para) +msgid "You can use the allow_same_net_traffic option in the /etc/nova/nova.conf file to globally control whether the rules applies to hosts which share a network." +msgstr "" + +#: ./doc/user-guide-admin/section_cli_nova_manage_projects_security.xml:27(para) +msgid "If set to:" +msgstr "" + +#: ./doc/user-guide-admin/section_cli_nova_manage_projects_security.xml:30(para) +msgid "True (default), hosts on the same subnet are not filtered and are allowed to pass all types of traffic between them. On a flat network, this allows all instances from all projects unfiltered communication. With VLAN networking, this allows access between instances within the same project. You can also simulate this setting by configuring the default security group to allow all traffic from the subnet." +msgstr "" + +#: ./doc/user-guide-admin/section_cli_nova_manage_projects_security.xml:41(para) +msgid "False, security groups are enforced for all connections." +msgstr "" + +#: ./doc/user-guide-admin/section_cli_nova_manage_projects_security.xml:45(para) +msgid "Additionally, the number of maximum rules per security group is controlled by the security_group_rules and the number of allowed security groups per project is controlled by the security_groups quota (see )." +msgstr "" + +#: ./doc/user-guide-admin/section_cli_nova_manage_projects_security.xml:51(title) +msgid "List and view current security groups" +msgstr "" + +#: ./doc/user-guide-admin/section_cli_nova_manage_projects_security.xml:52(para) +msgid "From the command line you can get a list of security groups for the project you're acting in using the nova command:" +msgstr "" + +#: ./doc/user-guide-admin/section_cli_nova_manage_projects_security.xml:56(para) +msgid "Ensure your system variables are set for the user and tenant for which you are checking security group rules. For example:" +msgstr "" + +#: ./doc/user-guide-admin/section_cli_nova_manage_projects_security.xml:63(para) +msgid "Output security groups, as follows:" +msgstr "" + +#: ./doc/user-guide-admin/section_cli_nova_manage_projects_security.xml:73(para) +msgid "View the details of a group, as follows:" +msgstr "" + +#: ./doc/user-guide-admin/section_cli_nova_manage_projects_security.xml:74(replaceable) +msgid "groupName" +msgstr "" + +#: ./doc/user-guide-admin/section_cli_nova_manage_projects_security.xml:75(para) ./doc/user-guide-admin/section_cli_nova_manage_projects_security.xml:111(para) ./doc/user-guide-admin/section_cli_nova_manage_projects_security.xml:174(para) ./doc/user-guide-admin/section_cli_nova_manage_projects_security.xml:195(para) ./doc/user-guide-admin/section_cli_cinder_quotas.xml:80(para) ./doc/user-guide-admin/section_cli_cinder_quotas.xml:100(para) ./doc/user-guide-admin/section_cli_nova_specify_host.xml:16(para) +msgid "For example:" +msgstr "" + +#: ./doc/user-guide-admin/section_cli_nova_manage_projects_security.xml:84(para) +msgid "These rules are allow type rules as the default is deny. The first column is the IP protocol (one of icmp, tcp, or udp) the second and third columns specify the affected port range. The third column specifies the IP range in CIDR format. This example shows the full port range for all protocols allowed from all IPs." +msgstr "" + +#: ./doc/user-guide-admin/section_cli_nova_manage_projects_security.xml:95(para) +msgid "When adding a new security group, you should pick a descriptive but brief name. This name shows up in brief descriptions of the instances that use it where the longer description field often does not. For example, seeing that an instance is using security group \"http\" is much easier to understand than \"bobs_group\" or \"secgrp1\"." +msgstr "" + +#: ./doc/user-guide-admin/section_cli_nova_manage_projects_security.xml:102(para) +msgid "Ensure your system variables are set for the user and tenant for which you are checking security group rules." +msgstr "" + +#: ./doc/user-guide-admin/section_cli_nova_manage_projects_security.xml:107(para) +msgid "Add the new security group, as follows:" +msgstr "" + +#: ./doc/user-guide-admin/section_cli_nova_manage_projects_security.xml:109(replaceable) +msgid "GroupName Description" +msgstr "" + +#: ./doc/user-guide-admin/section_cli_nova_manage_projects_security.xml:122(para) +msgid "Add a new group rule, as follows:" +msgstr "" + +#: ./doc/user-guide-admin/section_cli_nova_manage_projects_security.xml:124(replaceable) +msgid "secGroupName ip-protocol from-port to-port CIDR" +msgstr "" + +#: ./doc/user-guide-admin/section_cli_nova_manage_projects_security.xml:126(para) +msgid "The arguments are positional, and the \"from-port\" and \"to-port\" arguments specify the local port range connections are allowed to access, not the source and destination ports of the connection. For example:" +msgstr "" + +#: ./doc/user-guide-admin/section_cli_nova_manage_projects_security.xml:139(para) +msgid "You can create complex rule sets by creating additional rules. For example, if you want to pass both http and https traffic, run:" +msgstr "" + +#: ./doc/user-guide-admin/section_cli_nova_manage_projects_security.xml:148(para) +msgid "Despite only outputting the newly added rule, this operation is additive (both rules are created and enforced)." +msgstr "" + +#: ./doc/user-guide-admin/section_cli_nova_manage_projects_security.xml:153(para) +msgid "View all rules for the new security group, as follows:" +msgstr "" + +#: ./doc/user-guide-admin/section_cli_nova_manage_projects_security.xml:167(para) +msgid "Ensure your system variables are set for the user and tenant for which you are deleting a security group." +msgstr "" + +#: ./doc/user-guide-admin/section_cli_nova_manage_projects_security.xml:172(para) +msgid "Delete the new security group, as follows:" +msgstr "" + +#: ./doc/user-guide-admin/section_cli_nova_manage_projects_security.xml:173(replaceable) +msgid "GroupName" +msgstr "" + +#: ./doc/user-guide-admin/section_cli_nova_manage_projects_security.xml:179(title) +msgid "Create security group rules for a cluster of instances" +msgstr "" + +#: ./doc/user-guide-admin/section_cli_nova_manage_projects_security.xml:181(para) +msgid "SourceGroups are a special, dynamic way of defining the CIDR of allowed sources. The user specifies a SourceGroup (Security Group name), and all the users' other Instances using the specified SourceGroup are selected dynamically. This alleviates the need for individual rules to allow each new member of the cluster." +msgstr "" + +#: ./doc/user-guide-admin/section_cli_nova_manage_projects_security.xml:188(para) +msgid "Make sure to set the system variables for the user and tenant for which you are deleting a security group." +msgstr "" + +#: ./doc/user-guide-admin/section_cli_nova_manage_projects_security.xml:193(para) +msgid "Add a source group, as follows:" +msgstr "" + +#: ./doc/user-guide-admin/section_cli_nova_manage_projects_security.xml:194(replaceable) +msgid "secGroupName source-group ip-protocol from-port to-port" +msgstr "" + +#: ./doc/user-guide-admin/section_cli_nova_manage_projects_security.xml:197(para) +msgid "The cluster rule allows ssh access from any other instance that uses the global_http group." +msgstr "" + +#. When image changes, this message will be marked fuzzy or untranslated for you. +#. It doesn't matter what you translate it to: it's not used at all. +#: ./doc/user-guide-admin/section_dashboard_admin_manage_projects_users.xml:176(None) +msgid "@@image: 'figures/cloud_dash_users_list.png'; md5=1e8329b11c15fe3709ba745363dd4a24" +msgstr "" + +#: ./doc/user-guide-admin/section_dashboard_admin_manage_projects_users.xml:7(title) +msgid "Manage projects and users" +msgstr "" + +#: ./doc/user-guide-admin/section_dashboard_admin_manage_projects_users.xml:8(para) +msgid "As a cloud administrator, you manage both projects and users. Projects are organizational units in the cloud to which you can assign users. Projects are also known as tenants or accounts.You can manage projects and users independently from each other." +msgstr "" + +#: ./doc/user-guide-admin/section_dashboard_admin_manage_projects_users.xml:14(para) +msgid "Users are members of one or more projects." +msgstr "" + +#: ./doc/user-guide-admin/section_dashboard_admin_manage_projects_users.xml:15(para) +msgid "During cloud set up, the operator defines at least one project, user, and role. The operator links the role to the user and the user to the project. Roles define the actions that users can perform. As an administrator, you can create additional projects and users as needed." +msgstr "" + +#: ./doc/user-guide-admin/section_dashboard_admin_manage_projects_users.xml:20(para) +msgid "Learn how to add, update, and delete projects and users, assign users to one or more projects, and change or remove the assignment. To enable or temporarily disable a project or user, update that project or user. You can also change quotas at the project level. For information, see ." +msgstr "" + +#: ./doc/user-guide-admin/section_dashboard_admin_manage_projects_users.xml:26(para) +msgid "When you create a user account, you must assign the account to a primary project. Optionally, you can assign the account to additional projects. Before you can delete a user account, you must remove the user account from its primary project." +msgstr "" + +#: ./doc/user-guide-admin/section_dashboard_admin_manage_projects_users.xml:32(title) +msgid "Consequences of disabling projects and users" +msgstr "" + +#: ./doc/user-guide-admin/section_dashboard_admin_manage_projects_users.xml:33(para) +msgid "When you disable a project, it has the following consequences:" +msgstr "" + +#: ./doc/user-guide-admin/section_dashboard_admin_manage_projects_users.xml:37(para) +msgid "In the dashboard, users can no longer access the project from the CURRENT PROJECT drop-down list on the Project tab." +msgstr "" + +#: ./doc/user-guide-admin/section_dashboard_admin_manage_projects_users.xml:43(para) +msgid "Users who are members of only the disabled project can no longer log in." +msgstr "" + +#: ./doc/user-guide-admin/section_dashboard_admin_manage_projects_users.xml:47(para) +msgid "You cannot launch instances for a disabled project. Instances that are already running are not automatically terminated though—you must stop them manually." +msgstr "" + +#: ./doc/user-guide-admin/section_dashboard_admin_manage_projects_users.xml:53(para) +msgid "The data for a disabled project is maintained so that you can enable the project again at any time." +msgstr "" + +#: ./doc/user-guide-admin/section_dashboard_admin_manage_projects_users.xml:58(para) +msgid "When you disable a user account, the user can no longer log in, but the data for the user is maintained so that you can enable the user again at any time." +msgstr "" + +#: ./doc/user-guide-admin/section_dashboard_admin_manage_projects_users.xml:63(title) +msgid "Create a project" +msgstr "" + +#: ./doc/user-guide-admin/section_dashboard_admin_manage_projects_users.xml:72(para) ./doc/user-guide-admin/section_dashboard_admin_manage_projects_users.xml:109(para) ./doc/user-guide-admin/section_dashboard_admin_manage_projects_users.xml:205(para) ./doc/user-guide-admin/section_dashboard_admin_set_quotas.xml:172(para) +msgid "On the Admin tab, click the Projects category." +msgstr "" + +#: ./doc/user-guide-admin/section_dashboard_admin_manage_projects_users.xml:76(para) ./doc/user-guide-admin/section_dashboard_admin_manage_projects_users.xml:96(para) +msgid "Click Create Project." +msgstr "" + +#: ./doc/user-guide-admin/section_dashboard_admin_manage_projects_users.xml:80(para) +msgid "On the Project Info tab in the Create Project window, enter a name and description for the project. By default, the project is enabled. See ." +msgstr "" + +#: ./doc/user-guide-admin/section_dashboard_admin_manage_projects_users.xml:87(para) +msgid "On the Project Members tab, add members to the project." +msgstr "" + +#: ./doc/user-guide-admin/section_dashboard_admin_manage_projects_users.xml:91(para) +msgid "On the Quota tab, edit quota values. For information about quotas, see ." +msgstr "" + +#: ./doc/user-guide-admin/section_dashboard_admin_manage_projects_users.xml:98(para) +msgid "The Projects category shows the project, including its assigned ID." +msgstr "" + +#: ./doc/user-guide-admin/section_dashboard_admin_manage_projects_users.xml:105(para) +msgid "You can update a project to change its name or description, and enable or temporarily disable it." +msgstr "" + +#: ./doc/user-guide-admin/section_dashboard_admin_manage_projects_users.xml:113(para) +msgid "Select the project that you want to update." +msgstr "" + +#: ./doc/user-guide-admin/section_dashboard_admin_manage_projects_users.xml:117(para) +msgid "In the More drop-down list, click Edit Project." +msgstr "" + +#: ./doc/user-guide-admin/section_dashboard_admin_manage_projects_users.xml:121(para) +msgid "In the Edit Project window, you can update a project to change its name or description, and enable or temporarily disable it." +msgstr "" + +#: ./doc/user-guide-admin/section_dashboard_admin_manage_projects_users.xml:125(para) +msgid "By default, the project is enabled. To temporarily disable it, clear the Enabled check box. To enable a disabled project, select the Enabled check box." +msgstr "" + +#: ./doc/user-guide-admin/section_dashboard_admin_manage_projects_users.xml:137(title) +msgid "Modify user assignments for a project" +msgstr "" + +#: ./doc/user-guide-admin/section_dashboard_admin_manage_projects_users.xml:138(para) +msgid "When you create users, you must assign them to a primary project as described in . You can assign users to additional projects or update and remove assignments." +msgstr "" + +#: ./doc/user-guide-admin/section_dashboard_admin_manage_projects_users.xml:145(para) +msgid "On the Admin tab, select the Projects category." +msgstr "" + +#: ./doc/user-guide-admin/section_dashboard_admin_manage_projects_users.xml:149(para) +msgid "Select a project to modify its user assignments." +msgstr "" + +#: ./doc/user-guide-admin/section_dashboard_admin_manage_projects_users.xml:153(para) +msgid "Select Modify Users." +msgstr "" + +#: ./doc/user-guide-admin/section_dashboard_admin_manage_projects_users.xml:155(para) +msgid "The Edit Project window shows the following lists of users:" +msgstr "" + +#: ./doc/user-guide-admin/section_dashboard_admin_manage_projects_users.xml:159(para) +msgid "All Users. Users that are available to be assigned to the current project." +msgstr "" + +#: ./doc/user-guide-admin/section_dashboard_admin_manage_projects_users.xml:164(para) +msgid "Project Members. Users that are assigned to the current project," +msgstr "" + +#: ./doc/user-guide-admin/section_dashboard_admin_manage_projects_users.xml:170(title) +msgid "Edit the users list" +msgstr "" + +#: ./doc/user-guide-admin/section_dashboard_admin_manage_projects_users.xml:182(para) +msgid "To assign a user to the current project, click + for the user." +msgstr "" + +#: ./doc/user-guide-admin/section_dashboard_admin_manage_projects_users.xml:184(para) +msgid "The user moves from the All Users list to the Project Members list." +msgstr "" + +#: ./doc/user-guide-admin/section_dashboard_admin_manage_projects_users.xml:189(para) +msgid "To remove a user from the current project, click the - button for the user." +msgstr "" + +#: ./doc/user-guide-admin/section_dashboard_admin_manage_projects_users.xml:192(para) +msgid "The user moves from the Project Members list to the All Users list." +msgstr "" + +#: ./doc/user-guide-admin/section_dashboard_admin_manage_projects_users.xml:202(title) +msgid "Delete projects" +msgstr "" + +#: ./doc/user-guide-admin/section_dashboard_admin_manage_projects_users.xml:209(para) +msgid "Select the projects that you want to delete." +msgstr "" + +#: ./doc/user-guide-admin/section_dashboard_admin_manage_projects_users.xml:213(para) +msgid "Click Delete Projects to confirm the deletion." +msgstr "" + +#: ./doc/user-guide-admin/section_dashboard_admin_manage_projects_users.xml:216(para) +msgid "You cannot undo the delete action." +msgstr "" + +#: ./doc/user-guide-admin/section_dashboard_admin_manage_projects_users.xml:222(title) +msgid "Create a user account" +msgstr "" + +#: ./doc/user-guide-admin/section_dashboard_admin_manage_projects_users.xml:231(para) ./doc/user-guide-admin/section_dashboard_admin_manage_projects_users.xml:262(para) ./doc/user-guide-admin/section_dashboard_admin_manage_projects_users.xml:285(para) +msgid "On the Admin tab, select the Users category." +msgstr "" + +#: ./doc/user-guide-admin/section_dashboard_admin_manage_projects_users.xml:235(para) +msgid "Click Create User." +msgstr "" + +#: ./doc/user-guide-admin/section_dashboard_admin_manage_projects_users.xml:238(para) +msgid "In the Create User window, enter a user name, email, and preliminary password for the user. Confirm the password." +msgstr "" + +#: ./doc/user-guide-admin/section_dashboard_admin_manage_projects_users.xml:241(para) +msgid "Select a project from the Primary Project drop-down list." +msgstr "" + +#: ./doc/user-guide-admin/section_dashboard_admin_manage_projects_users.xml:243(para) +msgid "Choose a role for the user from the Role drop-down list. Default is Member." +msgstr "" + +#: ./doc/user-guide-admin/section_dashboard_admin_manage_projects_users.xml:248(para) +msgid "Click Create User to confirm your changes." +msgstr "" + +#: ./doc/user-guide-admin/section_dashboard_admin_manage_projects_users.xml:250(para) +msgid "Respond to the prompt to remember the password for the user." +msgstr "" + +#: ./doc/user-guide-admin/section_dashboard_admin_manage_projects_users.xml:252(para) +msgid "The dashboard assigns an ID to the user, and the user appears in the Users category." +msgstr "" + +#: ./doc/user-guide-admin/section_dashboard_admin_manage_projects_users.xml:259(title) +msgid "Disable or enable a user" +msgstr "" + +#: ./doc/user-guide-admin/section_dashboard_admin_manage_projects_users.xml:266(para) +msgid "Select the user that you want to disable or enable. You can disable or enable only one user at a time." +msgstr "" + +#: ./doc/user-guide-admin/section_dashboard_admin_manage_projects_users.xml:271(para) +msgid "In the Actions drop-down list, select Disable User or Enable User." +msgstr "" + +#: ./doc/user-guide-admin/section_dashboard_admin_manage_projects_users.xml:274(para) +msgid "In the Enabled column, the enabled value updates to either True or False." +msgstr "" + +#: ./doc/user-guide-admin/section_dashboard_admin_manage_projects_users.xml:282(title) +msgid "Delete users" +msgstr "" + +#: ./doc/user-guide-admin/section_dashboard_admin_manage_projects_users.xml:289(para) +msgid "Select the users that you want to delete." +msgstr "" + +#: ./doc/user-guide-admin/section_dashboard_admin_manage_projects_users.xml:292(para) +msgid "Click Delete Users." +msgstr "" + +#: ./doc/user-guide-admin/section_dashboard_admin_manage_projects_users.xml:295(para) +msgid "In the Confirm Delete Users window, click Delete Users to confirm the deletion." +msgstr "" + +#: ./doc/user-guide-admin/ch_cli.xml:10(title) +msgid "OpenStack command-line clients" +msgstr "" + +#: ./doc/user-guide-admin/section_cli_cinder_quotas.xml:6(title) +msgid "Manage Block Storage service quotas" +msgstr "" + +#: ./doc/user-guide-admin/section_cli_cinder_quotas.xml:7(para) +msgid "As an administrative user, you can update the OpenStack Block Storage Service quotas for a project. You can also update the quota defaults for a new project." +msgstr "" + +#: ./doc/user-guide-admin/section_cli_cinder_quotas.xml:12(caption) +msgid "Block Storage quotas" +msgstr "" + +#: ./doc/user-guide-admin/section_cli_cinder_quotas.xml:17(th) +msgid "Property name" +msgstr "" + +#: ./doc/user-guide-admin/section_cli_cinder_quotas.xml:18(th) ./doc/user-guide-admin/section_dashboard_admin_set_quotas.xml:41(th) +msgid "Defines the number of" +msgstr "" + +#: ./doc/user-guide-admin/section_cli_cinder_quotas.xml:24(para) +msgid "gigabytes" +msgstr "" + +#: ./doc/user-guide-admin/section_cli_cinder_quotas.xml:27(para) +msgid "Volume gigabytes allowed for each tenant." +msgstr "" + +#: ./doc/user-guide-admin/section_cli_cinder_quotas.xml:33(para) +msgid "snapshots" +msgstr "" + +#: ./doc/user-guide-admin/section_cli_cinder_quotas.xml:36(para) +msgid "Volume snapshots allowed for each tenant." +msgstr "" + +#: ./doc/user-guide-admin/section_cli_cinder_quotas.xml:42(para) +msgid "volumes" +msgstr "" + +#: ./doc/user-guide-admin/section_cli_cinder_quotas.xml:45(para) +msgid "Volumes allowed for each tenant." +msgstr "" + +#: ./doc/user-guide-admin/section_cli_cinder_quotas.xml:52(title) +msgid "View and update Block Storage Service quotas" +msgstr "" + +#: ./doc/user-guide-admin/section_cli_cinder_quotas.xml:53(para) +msgid "As an administrative user, you can view and update Block Storage Service quotas." +msgstr "" + +#: ./doc/user-guide-admin/section_cli_cinder_quotas.xml:57(para) +msgid "List the default quotas for all projects, as follows:" +msgstr "" + +#: ./doc/user-guide-admin/section_cli_cinder_quotas.xml:69(para) +msgid "To update a default value for a new project, update the property in the /etc/cinder/cinder.conf file." +msgstr "" + +#: ./doc/user-guide-admin/section_cli_cinder_quotas.xml:77(para) +msgid "View Block Storage Service quotas for a project, as follows:" +msgstr "" + +#: ./doc/user-guide-admin/section_cli_cinder_quotas.xml:79(replaceable) +msgid "TENANT_NAME" +msgstr "" + +#: ./doc/user-guide-admin/section_cli_cinder_quotas.xml:91(para) +msgid "To update Block Storage Service quotas, place the tenant ID in a usable variable, as follows:" +msgstr "" + +#: ./doc/user-guide-admin/section_cli_cinder_quotas.xml:94(replaceable) +msgid "tenantName" +msgstr "" + +#: ./doc/user-guide-admin/section_cli_cinder_quotas.xml:97(para) +msgid "Update a particular quota value, as follows:" +msgstr "" + +#: ./doc/user-guide-admin/section_cli_cinder_quotas.xml:99(replaceable) +msgid "quotaName" +msgstr "" + +#: ./doc/user-guide-admin/section_cli_cinder_quotas.xml:99(replaceable) +msgid "NewValue" +msgstr "" + +#: ./doc/user-guide-admin/section_cli_cinder_quotas.xml:99(replaceable) ./doc/user-guide-admin/section_cli_keystone_set_quotas.xml:40(replaceable) +msgid "tenantID" +msgstr "" + +#: ./doc/user-guide-admin/section_cli_swift_analyze_log_files.xml:7(title) +msgid "Analyze log files" +msgstr "" + +#: ./doc/user-guide-admin/section_cli_swift_analyze_log_files.xml:8(para) +msgid "Use the swift command-line client to analyze log files." +msgstr "" + +#: ./doc/user-guide-admin/section_cli_swift_analyze_log_files.xml:9(para) +msgid "The swift client is simple to use, scalable, and flexible." +msgstr "" + +#: ./doc/user-guide-admin/section_cli_swift_analyze_log_files.xml:9(para) +msgid "Use the swift client or option to get short answers to questions about logs," +msgstr "" + +#: ./doc/user-guide-admin/section_cli_swift_analyze_log_files.xml:12(para) +msgid "You can use the option with a single object download to redirect the command output to a specific file or to STDOUT (-). The ability to redirect the output to STDOUT enables you to pipe (|) data without saving it to disk first." +msgstr "" + +#: ./doc/user-guide-admin/section_cli_swift_analyze_log_files.xml:18(title) +msgid "Upload and analyze log files" +msgstr "" + +#: ./doc/user-guide-admin/section_cli_swift_analyze_log_files.xml:20(para) +msgid "This example assumes that logtest directory contains the following log files:" +msgstr "" + +#: ./doc/user-guide-admin/section_cli_swift_analyze_log_files.xml:23(title) +msgid "Example files" +msgstr "" + +#: ./doc/user-guide-admin/section_cli_swift_analyze_log_files.xml:27(para) +msgid "Each file uses the following line format:" +msgstr "" + +#: ./doc/user-guide-admin/section_cli_swift_analyze_log_files.xml:28(title) +msgid "Log line format" +msgstr "" + +#: ./doc/user-guide-admin/section_cli_swift_analyze_log_files.xml:31(para) +msgid "Change into the logtest directory:" +msgstr "" + +#: ./doc/user-guide-admin/section_cli_swift_analyze_log_files.xml:35(para) +msgid "Upload the log files into the logtest container:" +msgstr "" + +#: ./doc/user-guide-admin/section_cli_swift_analyze_log_files.xml:42(para) +msgid "Get statistics for the account:" +msgstr "" + +#: ./doc/user-guide-admin/section_cli_swift_analyze_log_files.xml:48(para) +msgid "Get statistics for the logtest container:" +msgstr "" + +#: ./doc/user-guide-admin/section_cli_swift_analyze_log_files.xml:56(para) +msgid "List all objects in the logtest container:" +msgstr "" + +#: ./doc/user-guide-admin/section_cli_swift_analyze_log_files.xml:62(title) +msgid "Download and analyze an object" +msgstr "" + +#: ./doc/user-guide-admin/section_cli_swift_analyze_log_files.xml:64(para) +msgid "This example uses the option and a hyphen (-) to get information about an object." +msgstr "" + +#: ./doc/user-guide-admin/section_cli_swift_analyze_log_files.xml:67(para) +msgid "Use the swift command to download the object. On this command, stream the output to to break down requests by return code and the date 2200 on November 16th, 2010." +msgstr "" + +#: ./doc/user-guide-admin/section_cli_swift_analyze_log_files.xml:72(para) +msgid "Using the log line format, find the request type in column 9 and the return code in column 12." +msgstr "" + +#: ./doc/user-guide-admin/section_cli_swift_analyze_log_files.xml:74(para) +msgid "After processes the output, it pipes it to and to sum up the number of occurrences for each request type and return code combination." +msgstr "" + +#: ./doc/user-guide-admin/section_cli_swift_analyze_log_files.xml:80(para) +msgid "Download an object:" +msgstr "" + +#: ./doc/user-guide-admin/section_cli_swift_analyze_log_files.xml:113(para) +msgid "Discover how many PUT requests are in each log file." +msgstr "" + +#: ./doc/user-guide-admin/section_cli_swift_analyze_log_files.xml:114(para) +msgid "Use a bash for loop with awk and swift with the option and a hyphen (-) to discover how many PUT requests are in each log file." +msgstr "" + +#: ./doc/user-guide-admin/section_cli_swift_analyze_log_files.xml:119(para) +msgid "Run the swift command to list objects in the logtest container. Then, for each item in the list, run the swift command. Pipe the output into grep to filter the PUT requests. Finally, pipe into to count the lines." +msgstr "" + +#: ./doc/user-guide-admin/section_cli_swift_analyze_log_files.xml:134(para) +msgid "List the object names that begin with a specified string." +msgstr "" + +#: ./doc/user-guide-admin/section_cli_swift_analyze_log_files.xml:136(para) +msgid "Run the swift command to list objects in the logtest container that begin with the 2010-11-15 string." +msgstr "" + +#: ./doc/user-guide-admin/section_cli_swift_analyze_log_files.xml:140(para) +msgid "For each item in the list, run the swift command." +msgstr "" + +#: ./doc/user-guide-admin/section_cli_swift_analyze_log_files.xml:142(para) +msgid "Pipe the output to and . Use the command to display the object name." +msgstr "" + +#: ./doc/user-guide-admin/section_cli_admin_manage_environment.xml:4(title) +msgid "Manage the OpenStack environment" +msgstr "" + +#: ./doc/user-guide-admin/section_cli_admin_manage_environment.xml:5(para) +msgid "This section includes tasks specific to the OpenStack environment." +msgstr "" + +#: ./doc/user-guide-admin/section_cli_manage_services.xml:7(title) +msgid "Manage services" +msgstr "" + +#: ./doc/user-guide-admin/section_dashboard_admin_manage_images.xml:7(title) +msgid "Create and manage images" +msgstr "" + +#: ./doc/user-guide-admin/section_dashboard_admin_manage_images.xml:8(para) +msgid "As an administrative user, you can create and manage images for the projects to which you belong. You can also create and manage images for users in all projects to which you have access." +msgstr "" + +#: ./doc/user-guide-admin/section_dashboard_admin_manage_images.xml:12(para) +msgid "To create and manage images in specified projects as an end user, see the OpenStack End User Guide." +msgstr "" + +#: ./doc/user-guide-admin/section_dashboard_admin_manage_images.xml:17(para) +msgid "To create and manage images as an administrator for other users, use the following procedures." +msgstr "" + +#: ./doc/user-guide-admin/section_dashboard_admin_manage_images.xml:20(title) +msgid "Create images" +msgstr "" + +#: ./doc/user-guide-admin/section_dashboard_admin_manage_images.xml:21(para) +msgid "For details about image creation, see the Virtual Machine Image Guide." +msgstr "" + +#: ./doc/user-guide-admin/section_dashboard_admin_manage_images.xml:33(para) +msgid "On the Admin tab, click the Images category. The images that you can administer for cloud users appear on this page." +msgstr "" + +#: ./doc/user-guide-admin/section_dashboard_admin_manage_images.xml:38(para) ./doc/user-guide-admin/section_dashboard_admin_manage_images.xml:85(para) +msgid "Click Create Image." +msgstr "" + +#: ./doc/user-guide-admin/section_dashboard_admin_manage_images.xml:41(para) +msgid "In the Create An Image window, enter or select the following values:" +msgstr "" + +#: ./doc/user-guide-admin/section_dashboard_admin_manage_images.xml:49(para) +msgid "Enter a name for the image." +msgstr "" + +#: ./doc/user-guide-admin/section_dashboard_admin_manage_images.xml:53(para) +msgid "Enter a brief description about the image." +msgstr "" + +#: ./doc/user-guide-admin/section_dashboard_admin_manage_images.xml:57(guilabel) +msgid "Image Location" +msgstr "" + +#: ./doc/user-guide-admin/section_dashboard_admin_manage_images.xml:59(para) +msgid "Include the URL of the image." +msgstr "" + +#: ./doc/user-guide-admin/section_dashboard_admin_manage_images.xml:62(guilabel) +msgid "Image File" +msgstr "" + +#: ./doc/user-guide-admin/section_dashboard_admin_manage_images.xml:63(para) +msgid "Alternatively, browse to find the image file on your machine." +msgstr "" + +#: ./doc/user-guide-admin/section_dashboard_admin_manage_images.xml:67(guilabel) +msgid "Format" +msgstr "" + +#: ./doc/user-guide-admin/section_dashboard_admin_manage_images.xml:68(para) +msgid "Select the image format." +msgstr "" + +#: ./doc/user-guide-admin/section_dashboard_admin_manage_images.xml:71(para) +msgid "Minimum Disk (GB) and Maximum Disk (GB)" +msgstr "" + +#: ./doc/user-guide-admin/section_dashboard_admin_manage_images.xml:73(para) +msgid "Leave these fields empty." +msgstr "" + +#: ./doc/user-guide-admin/section_dashboard_admin_manage_images.xml:77(guilabel) +msgid "Public" +msgstr "" + +#: ./doc/user-guide-admin/section_dashboard_admin_manage_images.xml:78(para) +msgid "Select this option to make the image public to all users." +msgstr "" + +#: ./doc/user-guide-admin/section_dashboard_admin_manage_images.xml:86(para) +msgid "The image is queued to be uploaded. It might take some time before the status changes from queued to active." +msgstr "" + +#: ./doc/user-guide-admin/section_dashboard_admin_manage_images.xml:92(title) +msgid "Update images" +msgstr "" + +#: ./doc/user-guide-admin/section_dashboard_admin_manage_images.xml:101(para) ./doc/user-guide-admin/section_dashboard_admin_manage_images.xml:131(para) +msgid "On the Admin tab, click the Images category." +msgstr "" + +#: ./doc/user-guide-admin/section_dashboard_admin_manage_images.xml:105(para) +msgid "Select the image that you want to edit. Click Edit." +msgstr "" + +#: ./doc/user-guide-admin/section_dashboard_admin_manage_images.xml:109(para) +msgid "In the Update Image window, you can change the name for the image. Select the Public check box to make the image public. Clear this check box to make the image private. You cannot change the kernel ID, RAM disk ID, or architecture attributes for an image." +msgstr "" + +#: ./doc/user-guide-admin/section_dashboard_admin_manage_images.xml:117(para) +msgid "Click Update Image." +msgstr "" + +#: ./doc/user-guide-admin/section_dashboard_admin_manage_images.xml:122(title) +msgid "Delete images" +msgstr "" + +#: ./doc/user-guide-admin/section_dashboard_admin_manage_images.xml:135(para) +msgid "Select the images that you want to delete." +msgstr "" + +#: ./doc/user-guide-admin/section_dashboard_admin_manage_images.xml:138(para) +msgid "Click Delete Images." +msgstr "" + +#: ./doc/user-guide-admin/section_dashboard_admin_manage_images.xml:141(para) +msgid "In the Confirm Delete Image window, click Delete Images to confirm the deletion." +msgstr "" + +#: ./doc/user-guide-admin/section_dashboard_admin_manage_images.xml:144(para) +msgid "You cannot undo this action." +msgstr "" + +#: ./doc/user-guide-admin/section_dashboard_admin_set_quotas.xml:14(title) +msgid "View and manage quotas" +msgstr "" + +#: ./doc/user-guide-admin/section_dashboard_admin_set_quotas.xml:15(para) ./doc/user-guide-admin/section_cli_keystone_set_quotas.xml:15(para) +msgid "To prevent system capacities from being exhausted without notification, you can set up quotas. Quotas are operational limits. For example, the number of gigabytes allowed for each tenant can be controlled so that cloud resources are optimized. Quotas can be enforced at both the tenant (or project) and the tenant-user level." +msgstr "" + +#: ./doc/user-guide-admin/section_dashboard_admin_set_quotas.xml:20(para) +msgid "Typically, you change quotas when a project needs more than 10 volumes or 1 TB on a Compute node." +msgstr "" + +#: ./doc/user-guide-admin/section_dashboard_admin_set_quotas.xml:22(para) +msgid "Using the Dashboard, you can view default Compute and Block Storage quotas for new tenants, as well as update quotas for existing tenants." +msgstr "" + +#: ./doc/user-guide-admin/section_dashboard_admin_set_quotas.xml:25(para) +msgid "Using the command-line interface, you can manage quotas for the OpenStack Compute Service, the OpenStack Block Storage Service, and the OpenStack Networking Service (see ). Additionally, you can update Compute service quotas for tenant users." +msgstr "" + +#: ./doc/user-guide-admin/section_dashboard_admin_set_quotas.xml:31(para) +msgid "The following table describes the Compute and Block Storage service quotas:" +msgstr "" + +#: ./doc/user-guide-admin/section_dashboard_admin_set_quotas.xml:34(caption) +msgid "Quota Descriptions" +msgstr "" + +#: ./doc/user-guide-admin/section_dashboard_admin_set_quotas.xml:40(th) +msgid "Quota Name" +msgstr "" + +#: ./doc/user-guide-admin/section_dashboard_admin_set_quotas.xml:42(th) +msgid "Service" +msgstr "" + +#: ./doc/user-guide-admin/section_dashboard_admin_set_quotas.xml:48(para) +msgid "Gigabytes" +msgstr "" + +#: ./doc/user-guide-admin/section_dashboard_admin_set_quotas.xml:51(para) +msgid "Volume gigabytes allowed for each project." +msgstr "" + +#: ./doc/user-guide-admin/section_dashboard_admin_set_quotas.xml:53(td) ./doc/user-guide-admin/section_dashboard_admin_set_quotas.xml:125(td) ./doc/user-guide-admin/section_dashboard_admin_set_quotas.xml:143(td) +msgid "Block Storage" +msgstr "" + +#: ./doc/user-guide-admin/section_dashboard_admin_set_quotas.xml:57(para) +msgid "Instances" +msgstr "" + +#: ./doc/user-guide-admin/section_dashboard_admin_set_quotas.xml:60(para) +msgid "Instances allowed for each project." +msgstr "" + +#: ./doc/user-guide-admin/section_dashboard_admin_set_quotas.xml:62(td) ./doc/user-guide-admin/section_dashboard_admin_set_quotas.xml:71(td) ./doc/user-guide-admin/section_dashboard_admin_set_quotas.xml:80(td) ./doc/user-guide-admin/section_dashboard_admin_set_quotas.xml:89(td) ./doc/user-guide-admin/section_dashboard_admin_set_quotas.xml:98(td) ./doc/user-guide-admin/section_dashboard_admin_set_quotas.xml:107(td) ./doc/user-guide-admin/section_dashboard_admin_set_quotas.xml:116(td) ./doc/user-guide-admin/section_dashboard_admin_set_quotas.xml:134(td) +msgid "Compute" +msgstr "" + +#: ./doc/user-guide-admin/section_dashboard_admin_set_quotas.xml:66(para) +msgid "Injected Files" +msgstr "" + +#: ./doc/user-guide-admin/section_dashboard_admin_set_quotas.xml:69(para) +msgid "Injected files allowed for each project." +msgstr "" + +#: ./doc/user-guide-admin/section_dashboard_admin_set_quotas.xml:75(para) +msgid "Injected File Content Bytes" +msgstr "" + +#: ./doc/user-guide-admin/section_dashboard_admin_set_quotas.xml:78(para) +msgid "Content bytes allowed for each injected file." +msgstr "" + +#: ./doc/user-guide-admin/section_dashboard_admin_set_quotas.xml:84(para) +msgid "Metadata Items" +msgstr "" + +#: ./doc/user-guide-admin/section_dashboard_admin_set_quotas.xml:87(para) +msgid "Metadata items allowed for each instance." +msgstr "" + +#: ./doc/user-guide-admin/section_dashboard_admin_set_quotas.xml:93(para) +msgid "RAM (MB)" +msgstr "" + +#: ./doc/user-guide-admin/section_dashboard_admin_set_quotas.xml:96(para) +msgid "RAM megabytes allowed for each instance." +msgstr "" + +#: ./doc/user-guide-admin/section_dashboard_admin_set_quotas.xml:102(para) +msgid "Security Groups" +msgstr "" + +#: ./doc/user-guide-admin/section_dashboard_admin_set_quotas.xml:105(para) +msgid "Security groups allowed for each project." +msgstr "" + +#: ./doc/user-guide-admin/section_dashboard_admin_set_quotas.xml:111(para) +msgid "Security Group Rules" +msgstr "" + +#: ./doc/user-guide-admin/section_dashboard_admin_set_quotas.xml:114(para) +msgid "Rules allowed for each security group." +msgstr "" + +#: ./doc/user-guide-admin/section_dashboard_admin_set_quotas.xml:120(para) +msgid "Snapshots" +msgstr "" + +#: ./doc/user-guide-admin/section_dashboard_admin_set_quotas.xml:123(para) +msgid "Volume snapshots allowed for each project." +msgstr "" + +#: ./doc/user-guide-admin/section_dashboard_admin_set_quotas.xml:132(para) +msgid "Instance cores allowed for each project." +msgstr "" + +#: ./doc/user-guide-admin/section_dashboard_admin_set_quotas.xml:138(para) +msgid "Volumes" +msgstr "" + +#: ./doc/user-guide-admin/section_dashboard_admin_set_quotas.xml:141(para) +msgid "Volumes allowed for each project." +msgstr "" + +#: ./doc/user-guide-admin/section_dashboard_admin_set_quotas.xml:149(title) +msgid "View default project quotas" +msgstr "" + +#: ./doc/user-guide-admin/section_dashboard_admin_set_quotas.xml:152(para) ./doc/user-guide-admin/section_dashboard_admin_set_quotas.xml:169(para) +msgid "Log in to the OpenStack dashboard." +msgstr "" + +#: ./doc/user-guide-admin/section_dashboard_admin_set_quotas.xml:154(para) +msgid "On the Admin tab, click the Defaults category." +msgstr "" + +#: ./doc/user-guide-admin/section_dashboard_admin_set_quotas.xml:158(para) +msgid "Click the Default Quotas tab to view the default quotas for the Compute and Block Storage services." +msgstr "" + +#: ./doc/user-guide-admin/section_dashboard_admin_set_quotas.xml:163(para) +msgid "You can sort the table by clicking on either the Quota Name or Limit column headers." +msgstr "" + +#: ./doc/user-guide-admin/section_dashboard_admin_set_quotas.xml:166(title) +msgid "Update project quotas" +msgstr "" + +#: ./doc/user-guide-admin/section_dashboard_admin_set_quotas.xml:176(para) +msgid "In the More drop-down list for a project, click Modify Quotas." +msgstr "" + +#: ./doc/user-guide-admin/section_dashboard_admin_set_quotas.xml:180(para) +msgid "On the Quota tab in the Edit Project window, edit the quota values. Then, click Save." +msgstr "" + +#: ./doc/user-guide-admin/section_dashboard_admin_set_quotas.xml:186(para) +msgid "The dashboard does not show all possible project quotas. To view and update the quotas for a service, use its command-line client. See ." +msgstr "" + +#: ./doc/user-guide-admin/section_cli_keystone_set_quotas.xml:14(title) +msgid "Manage quotas" +msgstr "" + +#: ./doc/user-guide-admin/section_cli_keystone_set_quotas.xml:21(para) +msgid "Using the command-line interface, you can manage quotas for the OpenStack Compute Service, the OpenStack Block Storage Service, and the OpenStack Networking Service." +msgstr "" + +#: ./doc/user-guide-admin/section_cli_keystone_set_quotas.xml:24(para) +msgid "Typically, default values are changed because a tenant requires more than 10 volumes, or more than 1TB on a Compute node." +msgstr "" + +#: ./doc/user-guide-admin/section_cli_keystone_set_quotas.xml:27(para) +msgid "To view all tenants (projects), run: " +msgstr "" + +#: ./doc/user-guide-admin/section_cli_keystone_set_quotas.xml:38(para) +msgid "To display all current users for a tenant, run:" +msgstr "" + +#: ./doc/user-guide-admin/section_dashboard_admin_view_cloud_resources.xml:12(title) +msgid "View cloud usage statistics" +msgstr "" + +#: ./doc/user-guide-admin/section_dashboard_admin_view_cloud_resources.xml:13(para) +msgid "The Telemetry service provides user-level usage data for OpenStack-based clouds, which can be used for customer billing, system monitoring, or alerts. Data can be collected by notifications sent by existing OpenStack components (for example, usage events emitted from Compute) or by polling the infrastructure (for example, libvirt)." +msgstr "" + +#: ./doc/user-guide-admin/section_dashboard_admin_view_cloud_resources.xml:19(para) +msgid "You can only view metering statistics on the dashboard (available only to adminstrators). The Telemetry service must be set up and administered through the command-line interface (CLI)." +msgstr "" + +#: ./doc/user-guide-admin/section_dashboard_admin_view_cloud_resources.xml:23(para) +msgid "For basic administration information, refer to the \"Measure Cloud Resources\" chapter in the OpenStack End User Guide." +msgstr "" + +#: ./doc/user-guide-admin/section_dashboard_admin_view_cloud_resources.xml:26(title) +msgid "View resource statistics" +msgstr "" + +#: ./doc/user-guide-admin/section_dashboard_admin_view_cloud_resources.xml:29(para) +msgid "Log in to the OpenStack dashboard as a user with Admin privileges." +msgstr "" + +#: ./doc/user-guide-admin/section_dashboard_admin_view_cloud_resources.xml:31(para) +msgid "On the Admin tab, click the Resource Usage category." +msgstr "" + +#: ./doc/user-guide-admin/section_dashboard_admin_view_cloud_resources.xml:37(para) +msgid "Global Disk Usage tab to view disk usage per tenant (project)." +msgstr "" + +#: ./doc/user-guide-admin/section_dashboard_admin_view_cloud_resources.xml:38(para) +msgid "Global Network Traffic Usage tab to view ingress or egress usage per tenant (project)." +msgstr "" + +#: ./doc/user-guide-admin/section_dashboard_admin_view_cloud_resources.xml:40(para) +msgid "Global Network Usage tab to view duration and creation requests for networks, subnets, routers, ports, and floating IPs, per tenant (project)." +msgstr "" + +#: ./doc/user-guide-admin/section_dashboard_admin_view_cloud_resources.xml:43(para) +msgid "Stats tab to view a multi-series line chart with user-defined metrics. You group by project, define the value type (min, max, avg, or sum), and specify the time period (or even use a calendar to define a date range)." +msgstr "" + +#: ./doc/user-guide-admin/section_dashboard_admin_view_cloud_resources.xml:35(para) +msgid "Click the: " +msgstr "" + +#: ./doc/user-guide-admin/section_dashboard_admin_manage_services.xml:13(title) +msgid "View services information" +msgstr "" + +#: ./doc/user-guide-admin/section_dashboard_admin_manage_services.xml:14(para) +msgid "As an administrative user, you can view information for OpenStack services." +msgstr "" + +#: ./doc/user-guide-admin/section_dashboard_admin_manage_services.xml:18(para) +msgid "Log in to the OpenStack dashboard and choose the admin project from the CURRENT PROJECT drop-down list." +msgstr "" + +#: ./doc/user-guide-admin/section_dashboard_admin_manage_services.xml:23(para) +msgid "On the Admin tab, click the System Info category." +msgstr "" + +#: ./doc/user-guide-admin/section_dashboard_admin_manage_services.xml:29(para) +msgid "Services tab to view services information." +msgstr "" + +#: ./doc/user-guide-admin/section_dashboard_admin_manage_services.xml:30(para) +msgid "The page displays the internal name and the public OpenStack name for the service, the host where the service runs, and whether the service is or is not enabled." +msgstr "" + +#: ./doc/user-guide-admin/section_dashboard_admin_manage_services.xml:34(para) +msgid "Compute Services tab to view services specific to the Compute Service. Both host and zone are listed for each service, as well as its activation status." +msgstr "" + +#: ./doc/user-guide-admin/section_dashboard_admin_manage_services.xml:27(para) +msgid "Click the:" +msgstr "" + +#: ./doc/user-guide-admin/section_dashboard_admin_manage_services.xml:43(guilabel) +msgid "Availability Zones" +msgstr "" + +#: ./doc/user-guide-admin/section_dashboard_admin_manage_services.xml:46(guilabel) +msgid "Host Aggregates" +msgstr "" + +#: ./doc/user-guide-admin/section_dashboard_admin_manage_services.xml:49(guilabel) +msgid "Network Agents" +msgstr "" + +#: ./doc/user-guide-admin/section_dashboard_admin_manage_services.xml:41(para) +msgid "The System Info window also offers status information for the following: " +msgstr "" + +#: ./doc/user-guide-admin/section_cli_nova_specify_host.xml:6(title) +msgid "Select hosts where instances are launched" +msgstr "" + +#: ./doc/user-guide-admin/section_cli_nova_specify_host.xml:7(para) +msgid "With the appropriate permissions, you can select which host instances are launched on and which roles can boot instances on this host." +msgstr "" + +#: ./doc/user-guide-admin/section_cli_nova_specify_host.xml:12(para) +msgid "To select the host where instances are launched, use the --availability_zone zone:host parameter on the command," +msgstr "" + +#: ./doc/user-guide-admin/section_cli_nova_specify_host.xml:20(para) +msgid "To specify which roles can launch an instance on a specified host, enable the create:forced_host option in the policy.json file. By default, this option is enabled for only the admin role." +msgstr "" + +#: ./doc/user-guide-admin/section_cli_nova_specify_host.xml:27(para) +msgid "To view the list of valid compute hosts, use the command, as follows:" +msgstr "" + +#: ./doc/user-guide-admin/section_cli_nova_specify_host.xml:44(para) +msgid "Beginning in the Folsom release, the --availability_zone zone:host parameter replaces the --force_hosts scheduler hint parameter." +msgstr "" + +#: ./doc/user-guide-admin/section_cli_nova_specify_host.xml:52(para) +msgid "Beginning in the Grizzly release, you can enable the create:forced_host option in the policy.json file to specify which roles can launch an instance on a specified host." +msgstr "" + +#: ./doc/user-guide-admin/ch_dashboard.xml:10(title) +msgid "Dashboard" +msgstr "" + +#: ./doc/user-guide-admin/ch_dashboard.xml:12(para) +msgid "As a cloud administrative user, the OpenStack dashboard lets you create and manage projects, users, images, and flavors. You can also set quotas and create and manage services. For information about using the dashboard to perform end user tasks, see the OpenStack End User Guide." +msgstr "" + +#: ./doc/user-guide-admin/section_cli_admin_manage_stacks.xml:15(para) +msgid "For information about the:" +msgstr "" + +#: ./doc/user-guide-admin/section_cli_admin_manage_stacks.xml:19(para) +msgid "Basic creation and deletion of Orchestration stacks, refer to the End User Guide." +msgstr "" + +#: ./doc/user-guide-admin/section_cli_admin_manage_stacks.xml:23(para) +msgid "heat CLI commands, see " +msgstr "" + +#: ./doc/user-guide-admin/section_cli_admin_manage_stacks.xml:27(para) +msgid "As an administrator, you can also carry out stack functions on behalf of your users. For example, to resume, suspend, or delete a stack, run:" +msgstr "" + +#: ./doc/user-guide-admin/section_cli_admin_manage_stacks.xml:29(replaceable) ./doc/user-guide-admin/section_cli_admin_manage_stacks.xml:30(replaceable) ./doc/user-guide-admin/section_cli_admin_manage_stacks.xml:31(replaceable) +msgid "stackID" +msgstr "" + +#. Put one translator per line, in the form of NAME , YEAR1, YEAR2 +#: ./doc/user-guide-admin/section_cli_admin_manage_stacks.xml:0(None) +msgid "translator-credits" +msgstr "" + diff --git a/doc/user-guide/locale/he_IL.po b/doc/user-guide/locale/he_IL.po new file mode 100644 index 0000000000..4878d3f607 --- /dev/null +++ b/doc/user-guide/locale/he_IL.po @@ -0,0 +1,2778 @@ +# +# Translators: +msgid "" +msgstr "" +"Project-Id-Version: OpenStack Manuals\n" +"POT-Creation-Date: 2014-01-30 06:24+0000\n" +"PO-Revision-Date: 2014-01-27 15:35+0000\n" +"Last-Translator: openstackjenkins \n" +"Language-Team: Hebrew (Israel) (http://www.transifex.com/projects/p/openstack/language/he_IL/)\n" +"MIME-Version: 1.0\n" +"Content-Type: text/plain; charset=UTF-8\n" +"Content-Transfer-Encoding: 8bit\n" +"Language: he_IL\n" +"Plural-Forms: nplurals=2; plural=(n != 1);\n" + +#: ./doc/user-guide/section_dashboard_create_networks.xml12(title) +msgid "Create a network" +msgstr "" + +#: ./doc/user-guide/section_dashboard_create_networks.xml16(para) +msgid "" +"Log in to the dashboard, choose a project, and click the " +"Networks category." +msgstr "" + +#: ./doc/user-guide/section_dashboard_create_networks.xml21(para) +msgid "Click Create Network." +msgstr "" + +#: ./doc/user-guide/section_dashboard_create_networks.xml24(para) +msgid "In the Create Network window, specify the following values." +msgstr "" + +#: ./doc/user-guide/section_dashboard_create_networks.xml32(guilabel) +msgid "Network" +msgstr "" + +#: ./doc/user-guide/section_dashboard_create_networks.xml32(th) +#: ./doc/user-guide/section_dashboard_create_networks.xml44(th) +#: ./doc/user-guide/section_dashboard_create_networks.xml87(th) +#: ./doc/user-guide/section_dashboard_launch_instances_from_image.xml39(th) +#: ./doc/user-guide/section_dashboard_launch_instances_from_image.xml69(th) +#: ./doc/user-guide/section_dashboard_launch_instances_from_image.xml101(th) +#: ./doc/user-guide/section_dashboard_launch_instances_from_image.xml122(th) +msgid " tab" +msgstr "" + +#: ./doc/user-guide/section_dashboard_create_networks.xml37(guilabel) +msgid "Network Name" +msgstr "" + +#: ./doc/user-guide/section_dashboard_create_networks.xml39(para) +msgid "A name to identify the network." +msgstr "" + +#: ./doc/user-guide/section_dashboard_create_networks.xml44(guilabel) +msgid "Subnet" +msgstr "" + +#: ./doc/user-guide/section_dashboard_create_networks.xml47(guilabel) +msgid "Create Subnet" +msgstr "" + +#: ./doc/user-guide/section_dashboard_create_networks.xml49(para) +msgid "Check this option to create a subnet" +msgstr "" + +#: ./doc/user-guide/section_dashboard_create_networks.xml51(para) +msgid "" +"You do not have to initially specify a subnet (although this will result in " +"the status of 'error' for any attached instance)." +msgstr "" + +#: ./doc/user-guide/section_dashboard_create_networks.xml57(guilabel) +msgid "Subnet Name" +msgstr "" + +#: ./doc/user-guide/section_dashboard_create_networks.xml59(para) +msgid "Name for the subnet." +msgstr "" + +#: ./doc/user-guide/section_dashboard_create_networks.xml62(guilabel) +msgid "Network Address" +msgstr "" + +#: ./doc/user-guide/section_dashboard_create_networks.xml64(para) +msgid "IP address for the subnet." +msgstr "" + +#: ./doc/user-guide/section_dashboard_create_networks.xml68(guilabel) +msgid "IP Version" +msgstr "" + +#: ./doc/user-guide/section_dashboard_create_networks.xml70(para) +msgid "IPv4 or IPv6." +msgstr "" + +#: ./doc/user-guide/section_dashboard_create_networks.xml73(guilabel) +msgid "Gateway IP" +msgstr "" + +#: ./doc/user-guide/section_dashboard_create_networks.xml75(para) +msgid "IP address for a specific gateway. This parameter is optional." +msgstr "" + +#: ./doc/user-guide/section_dashboard_create_networks.xml80(guilabel) +msgid "Disable Gateway" +msgstr "" + +#: ./doc/user-guide/section_dashboard_create_networks.xml82(para) +msgid "Check this option to disable gateway IP address." +msgstr "" + +#: ./doc/user-guide/section_dashboard_create_networks.xml87(guilabel) +msgid "Subnet Detail" +msgstr "" + +#: ./doc/user-guide/section_dashboard_create_networks.xml91(guilabel) +msgid "Enable DHCP" +msgstr "" + +#: ./doc/user-guide/section_dashboard_create_networks.xml93(para) +msgid "Check this option to enable DHCP" +msgstr "" + +#: ./doc/user-guide/section_dashboard_create_networks.xml97(guilabel) +msgid "Allocation Pools" +msgstr "" + +#: ./doc/user-guide/section_dashboard_create_networks.xml99(para) +msgid "You can allocate IP address pools." +msgstr "" + +#: ./doc/user-guide/section_dashboard_create_networks.xml103(guilabel) +msgid "DNS Name Servers" +msgstr "" + +#: ./doc/user-guide/section_dashboard_create_networks.xml105(para) +msgid "You can allocate a name for the DNS server." +msgstr "" + +#: ./doc/user-guide/section_dashboard_create_networks.xml109(guilabel) +msgid "Host Routes" +msgstr "" + +#: ./doc/user-guide/section_dashboard_create_networks.xml111(para) +msgid "Include IP address of host routes." +msgstr "" + +#: ./doc/user-guide/section_dashboard_create_networks.xml118(para) +msgid "Click Create to create a network." +msgstr "" + +#: ./doc/user-guide/section_dashboard_create_networks.xml122(para) +msgid "" +"The dashboard shows the network in the Networks " +"category." +msgstr "" + +#: ./doc/user-guide/section_dashboard_manage_volumes.xml13(title) +msgid "Manage volumes" +msgstr "" + +#: ./doc/user-guide/section_dashboard_manage_volumes.xml15(para) +msgid "" +"Volumes are block storage devices that you attach to instances to enable " +"persistent storage. You can attach a volume to a running instance or detach " +"a volume and attach it to another instance at any time. You can also create " +"a snapshot from or delete a volume. Only administrative users can create " +"volume types." +msgstr "" + +#: ./doc/user-guide/section_dashboard_manage_volumes.xml22(title) +msgid "Create a volume" +msgstr "" + +#: ./doc/user-guide/section_dashboard_manage_volumes.xml26(para) +#: ./doc/user-guide/section_dashboard_manage_volumes.xml54(para) +#: ./doc/user-guide/section_dashboard_manage_volumes.xml99(para) +#: ./doc/user-guide/section_dashboard_manage_volumes.xml150(para) +msgid "" +"Log in to the dashboard, choose a project, and click the " +"Volumes category." +msgstr "" + +#: ./doc/user-guide/section_dashboard_manage_volumes.xml31(para) +msgid "Click Create Volume." +msgstr "" + +#: ./doc/user-guide/section_dashboard_manage_volumes.xml33(para) +msgid "" +"In the window that opens, enter a name, an optional description, and the " +"size in GBs for the volume." +msgstr "" + +#: ./doc/user-guide/section_dashboard_manage_volumes.xml38(para) +msgid "Click Create Volume to confirm your changes." +msgstr "" + +#: ./doc/user-guide/section_dashboard_manage_volumes.xml42(para) +msgid "" +"The dashboard shows the volume in the Volumes category." +msgstr "" + +#: ./doc/user-guide/section_dashboard_manage_volumes.xml48(title) +msgid "Attach volumes to instances" +msgstr "" + +#: ./doc/user-guide/section_dashboard_manage_volumes.xml49(para) +msgid "" +"After you create one or more volumes, you can attach them to instances." +msgstr "" + +#: ./doc/user-guide/section_dashboard_manage_volumes.xml59(para) +msgid "" +"Select the volume to add to an instance and click Edit " +"Attachments." +msgstr "" + +#: ./doc/user-guide/section_dashboard_manage_volumes.xml63(para) +msgid "" +"In the Manage Volume Attachments window, select an " +"instance." +msgstr "" + +#: ./doc/user-guide/section_dashboard_manage_volumes.xml68(para) +msgid "" +"Enter the name of the device from where the volume should be accessible on " +"the virtual machine." +msgstr "" + +#: ./doc/user-guide/section_dashboard_manage_volumes.xml72(para) +msgid "The actual device name might differ due to hypervisor settings." +msgstr "" + +#: ./doc/user-guide/section_dashboard_manage_volumes.xml77(para) +msgid "" +"Click Attach Volume to confirm your changes. The " +"dashboard shows the instance to which the volume is now attached and the " +"device name. You can attach a volume to one instance at a time." +msgstr "" + +#: ./doc/user-guide/section_dashboard_manage_volumes.xml84(para) +msgid "" +"View the status of a volume in the Instances & " +"Volumes category of the dashboard. The volume is either available" +" or In-Use." +msgstr "" + +#: ./doc/user-guide/section_dashboard_manage_volumes.xml90(para) +msgid "" +"Now you can log in to the instance and mount, format, and use the disk." +msgstr "" + +#: ./doc/user-guide/section_dashboard_manage_volumes.xml96(title) +msgid "Detach a volume from an instance" +msgstr "" + +#: ./doc/user-guide/section_dashboard_manage_volumes.xml104(para) +msgid "Select the volume and click Edit Attachments." +msgstr "" + +#: ./doc/user-guide/section_dashboard_manage_volumes.xml108(para) +msgid "Click Detach Volume and confirm your changes." +msgstr "" + +#: ./doc/user-guide/section_dashboard_manage_volumes.xml112(para) +#: ./doc/user-guide/section_dashboard_manage_volumes.xml164(para) +msgid "A message indicates whether the action was successful." +msgstr "" + +#: ./doc/user-guide/section_dashboard_manage_volumes.xml118(title) +msgid "Create volume snapshots" +msgstr "" + +#: ./doc/user-guide/section_dashboard_manage_volumes.xml121(para) +msgid "" +"Log in to the dashboard, choose a project, and click the Instances" +" & Volumes category." +msgstr "" + +#: ./doc/user-guide/section_dashboard_manage_volumes.xml126(para) +msgid "Select a volume from which to create a snapshot." +msgstr "" + +#: ./doc/user-guide/section_dashboard_manage_volumes.xml129(para) +msgid "" +"From the Actions drop-down list, select " +"Create Snapshot." +msgstr "" + +#: ./doc/user-guide/section_dashboard_manage_volumes.xml133(para) +msgid "In the window that opens, enter a snapshot name and a description." +msgstr "" + +#: ./doc/user-guide/section_dashboard_manage_volumes.xml137(para) +msgid "Confirm your changes." +msgstr "" + +#: ./doc/user-guide/section_dashboard_manage_volumes.xml138(para) +msgid "" +"The dashboard shows the new volume snapshot in the Images & " +"Snapshots category." +msgstr "" + +#: ./doc/user-guide/section_dashboard_manage_volumes.xml145(title) +msgid "Delete volumes" +msgstr "" + +#: ./doc/user-guide/section_dashboard_manage_volumes.xml146(para) +msgid "" +"When you delete an instance, the data of its attached volumes is not " +"destroyed." +msgstr "" + +#: ./doc/user-guide/section_dashboard_manage_volumes.xml155(para) +msgid "" +"Activate the check boxes in front of the volumes that you want to delete." +msgstr "" + +#: ./doc/user-guide/section_dashboard_manage_volumes.xml159(para) +msgid "" +"Click Delete Volumes and confirm your choice in the " +"pop-up that appears." +msgstr "" + +#: ./doc/user-guide/section_sdk_manage_images.xml7(title) +msgid "Manage images" +msgstr "" + +#: ./doc/user-guide/section_sdk_manage_images.xml9(title) +msgid "List images" +msgstr "" + +#: ./doc/user-guide/section_sdk_manage_images.xml10(para) +msgid "" +"To list the available images, call the " +"glanceclient.v2.images.Controller.list method:" +msgstr "" + +#: ./doc/user-guide/section_sdk_manage_images.xml16(para) +msgid "" +"The images method returns a Python generator, as " +"shown in the following interaction with the Python interpreter:" +msgstr "" + +#: ./doc/user-guide/section_sdk_manage_images.xml76(title) +msgid "Get image by ID" +msgstr "" + +#: ./doc/user-guide/section_sdk_manage_images.xml77(para) +msgid "" +"To retrieve an image object from its ID, call the " +"glanceclient.v2.images.Controller.get method:" +msgstr "" + +#: ./doc/user-guide/section_sdk_manage_images.xml87(title) +msgid "Get image by name" +msgstr "" + +#: ./doc/user-guide/section_sdk_manage_images.xml88(para) +msgid "" +"The Image Service Python bindings do not support the retrieval of an image " +"object by name. However, the Compute Python bindings enable you to get an " +"image object by name. To get an image object by name, call the " +"novaclient.v1_1.images.ImageManager.find method:" +msgstr "" + +#: ./doc/user-guide/section_sdk_manage_images.xml100(title) +msgid "Upload an image" +msgstr "" + +#: ./doc/user-guide/section_sdk_manage_images.xml101(para) +msgid "" +"To upload an image, call the " +"glanceclient.v2.images.ImageManager.create method:" +msgstr "" + +#: ./doc/user-guide/section_cli_heat.xml9(title) +msgid "Create and manage stacks" +msgstr "" + +#: ./doc/user-guide/section_cli_heat.xml11(title) +msgid "Create a stack from an example template file" +msgstr "" + +#: ./doc/user-guide/section_cli_heat.xml14(para) +msgid "" +"To create a stack, or template, from an example template " +"file, run the following command:" +msgstr "" + +#: ./doc/user-guide/section_cli_heat.xml18(replaceable) +#: ./doc/user-guide/section_cli_heat.xml39(replaceable) +msgid "PATH_TO_HEAT_TEMPLATES" +msgstr "" + +#: ./doc/user-guide/section_cli_heat.xml19(replaceable) +msgid "USERNAME" +msgstr "" + +#: ./doc/user-guide/section_cli_heat.xml19(replaceable) +msgid "PASSWORD" +msgstr "" + +#: ./doc/user-guide/section_cli_heat.xml19(replaceable) +msgid "HEAT_KEY" +msgstr "" + +#: ./doc/user-guide/section_cli_heat.xml20(para) +msgid "" +"The --parameters values that you specify depend on the " +"parameters that are defined in the template. If a website hosts the template" +" file, you can specify the URL with the --template-url " +"parameter instead of the --template-file parameter." +msgstr "" + +#: ./doc/user-guide/section_cli_heat.xml26(para) +msgid "The command returns the following output:" +msgstr "" + +#: ./doc/user-guide/section_cli_heat.xml34(para) +msgid "" +"You can also use the command to validate a template file " +"without creating a stack from it." +msgstr "" + +#: ./doc/user-guide/section_cli_heat.xml38(para) +msgid "To do so, run the following command:" +msgstr "" + +#: ./doc/user-guide/section_cli_heat.xml40(para) +msgid "If validation fails, the response returns an error message." +msgstr "" + +#: ./doc/user-guide/section_cli_heat.xml46(title) +msgid "Get information about stacks" +msgstr "" + +#: ./doc/user-guide/section_cli_heat.xml47(para) +msgid "" +"To explore the state and history of a particular stack, you can run a number" +" of commands." +msgstr "" + +#: ./doc/user-guide/section_cli_heat.xml51(para) +msgid "" +"To see which stacks are visible to the current user, run the following " +"command:" +msgstr "" + +#: ./doc/user-guide/section_cli_heat.xml62(para) +msgid "To show the details of a stack, run the following command:" +msgstr "" + +#: ./doc/user-guide/section_cli_heat.xml67(para) +msgid "A stack consists of a collection of resources." +msgstr "" + +#: ./doc/user-guide/section_cli_heat.xml69(para) +msgid "To list the resources and their status, run the following command:" +msgstr "" + +#: ./doc/user-guide/section_cli_heat.xml79(para) +msgid "" +"To show the details for the specified resource in a stack, run the following" +" command:" +msgstr "" + +#: ./doc/user-guide/section_cli_heat.xml82(para) +msgid "" +"Some resources have associated metadata which can change throughout the " +"life-cycle of a resource:" +msgstr "" + +#: ./doc/user-guide/section_cli_heat.xml88(para) +msgid "A series of events is generated during the life-cycle of a stack." +msgstr "" + +#: ./doc/user-guide/section_cli_heat.xml90(para) +msgid "To display life-cycle events, run::" +msgstr "" + +#: ./doc/user-guide/section_cli_heat.xml100(para) +msgid "To show the details for a particular event, run the following command:" +msgstr "" + +#: ./doc/user-guide/section_cli_heat.xml107(title) +msgid "Update a stack" +msgstr "" + +#: ./doc/user-guide/section_cli_heat.xml110(para) +msgid "" +"To update an existing stack from a modified template file, run a command " +"like the following command:" +msgstr "" + +#: ./doc/user-guide/section_cli_heat.xml121(para) +msgid "" +"Some resources are updated in-place, while others are replaced with new " +"resources." +msgstr "" + +#: ./doc/user-guide/ch_sdk.xml6(title) +msgid "OpenStack Python SDK" +msgstr "" + +#: ./doc/user-guide/ch_sdk.xml8(para) +msgid "" +"Use the OpenStack Python Software Development Kit (SDK) to write Python " +"automation scripts that create and manage resources in your OpenStack cloud." +" The SDK implements Python bindings to the OpenStack API, which enables you " +"to perform automation tasks in Python by making calls on Python objects " +"rather than making REST calls directly. All OpenStack command-line tools are" +" implemented using the Python SDK." +msgstr "" + +#: ./doc/user-guide/section_dashboard_access_and_security.xml12(title) +#: ./doc/user-guide/section_sdk_configure_instances.xml6(title) +#: ./doc/user-guide/section_cli_nova_configure_instances.xml17(title) +msgid "Configure access and security for instances" +msgstr "" + +#: ./doc/user-guide/section_dashboard_access_and_security.xml14(para) +msgid "" +"Before you launch a virtual machine, you can add security group rules to " +"enable users to ping and SSH to the instances. To do so, you either add " +"rules to the default security group or add a security group with rules." +msgstr "" + +#: ./doc/user-guide/section_dashboard_access_and_security.xml18(para) +msgid "" +"Keypairs are SSH credentials that are injected into images when they are " +"launched. For this to work, the image must contain the cloud-" +"init package. Create at least one keypair for each project. For " +"information, see ." +msgstr "" + +#: ./doc/user-guide/section_dashboard_access_and_security.xml23(para) +msgid "" +"If you have generated a keypair with an external tool, you can import it " +"into OpenStack. The keypair can be used for multiple instances that belong " +"to a project. For information, see ." +msgstr "" + +#: ./doc/user-guide/section_dashboard_access_and_security.xml28(title) +msgid "Add rules to the default security group" +msgstr "" + +#: ./doc/user-guide/section_dashboard_access_and_security.xml31(para) +msgid "" +"Log in to the dashboard, choose a project, and click the Access " +"& Security category. The dashboard shows the security groups " +"that are available for this project." +msgstr "" + +#: ./doc/user-guide/section_dashboard_access_and_security.xml37(para) +msgid "" +"Select the default security group and click Edit " +"Rules." +msgstr "" + +#: ./doc/user-guide/section_dashboard_access_and_security.xml41(para) +msgid "To allow ssh access, click Add Rule." +msgstr "" + +#: ./doc/user-guide/section_dashboard_access_and_security.xml45(para) +#: ./doc/user-guide/section_dashboard_access_and_security.xml88(para) +msgid "" +"In the Add Rule window, enter the following values:" +msgstr "" + +#: ./doc/user-guide/section_dashboard_access_and_security.xml52(guilabel) +#: ./doc/user-guide/section_dashboard_access_and_security.xml94(guilabel) +msgid "Rule" +msgstr "" + +#: ./doc/user-guide/section_dashboard_access_and_security.xml54(literal) +msgid "SSH" +msgstr "" + +#: ./doc/user-guide/section_dashboard_access_and_security.xml58(guilabel) +#: ./doc/user-guide/section_dashboard_access_and_security.xml102(guilabel) +msgid "Remote" +msgstr "" + +#: ./doc/user-guide/section_dashboard_access_and_security.xml61(literal) +#: ./doc/user-guide/section_dashboard_access_and_security.xml65(guilabel) +#: ./doc/user-guide/section_dashboard_access_and_security.xml103(literal) +#: ./doc/user-guide/section_dashboard_access_and_security.xml106(guilabel) +msgid "CIDR" +msgstr "" + +#: ./doc/user-guide/section_dashboard_access_and_security.xml67(literal) +#: ./doc/user-guide/section_dashboard_access_and_security.xml107(literal) +msgid "0.0.0.0/0" +msgstr "" + +#: ./doc/user-guide/section_dashboard_access_and_security.xml73(para) +msgid "" +"To accept requests from a particular range of IP addresses, specify the IP " +"address block in the CIDR box." +msgstr "" + +#: ./doc/user-guide/section_dashboard_access_and_security.xml79(para) +#: ./doc/user-guide/section_dashboard_access_and_security.xml112(para) +msgid "Click Add." +msgstr "" + +#: ./doc/user-guide/section_dashboard_access_and_security.xml80(para) +msgid "The ssh port 22 is now open for requests from any IP address." +msgstr "" + +#: ./doc/user-guide/section_dashboard_access_and_security.xml84(para) +msgid "To add an ICMP rule, click Add Rule." +msgstr "" + +#: ./doc/user-guide/section_dashboard_access_and_security.xml95(literal) +msgid "All ICMP" +msgstr "" + +#: ./doc/user-guide/section_dashboard_access_and_security.xml98(guilabel) +msgid "Direction" +msgstr "" + +#: ./doc/user-guide/section_dashboard_access_and_security.xml99(literal) +msgid "Ingress" +msgstr "" + +#: ./doc/user-guide/section_dashboard_access_and_security.xml117(title) +#: ./doc/user-guide/section_sdk_configure_instances.xml9(title) +#: ./doc/user-guide/section_cli_nova_configure_instances.xml79(title) +msgid "Add a keypair" +msgstr "" + +#: ./doc/user-guide/section_dashboard_access_and_security.xml118(para) +msgid "Create at least one keypair for each project." +msgstr "" + +#: ./doc/user-guide/section_dashboard_access_and_security.xml121(para) +#: ./doc/user-guide/section_dashboard_access_and_security.xml149(para) +msgid "" +"Log in to the dashboard, choose a project, and click the Access " +"& Security category." +msgstr "" + +#: ./doc/user-guide/section_dashboard_access_and_security.xml126(para) +#: ./doc/user-guide/section_dashboard_access_and_security.xml154(para) +msgid "" +"The Keypairs tab shows the keypairs that are available " +"for this project." +msgstr "" + +#: ./doc/user-guide/section_dashboard_access_and_security.xml131(para) +msgid "Click Create Keypair." +msgstr "" + +#: ./doc/user-guide/section_dashboard_access_and_security.xml135(para) +msgid "" +"In the Create Keypair window, enter a name for your " +"keypair, and click Create Keypair." +msgstr "" + +#: ./doc/user-guide/section_dashboard_access_and_security.xml140(para) +msgid "Respond to the prompt to download the keypair." +msgstr "" + +#: ./doc/user-guide/section_dashboard_access_and_security.xml146(title) +#: ./doc/user-guide/section_sdk_configure_instances.xml50(title) +#: ./doc/user-guide/section_cli_nova_configure_instances.xml107(title) +msgid "Import a keypair" +msgstr "" + +#: ./doc/user-guide/section_dashboard_access_and_security.xml159(para) +msgid "Click Import Keypair." +msgstr "" + +#: ./doc/user-guide/section_dashboard_access_and_security.xml163(para) +msgid "" +"In the Import Keypair window, enter the name of your " +"keypair. In the Public Key box, copy the public key. " +"Then, click Import Keypair." +msgstr "" + +#: ./doc/user-guide/section_dashboard_access_and_security.xml170(para) +msgid "" +"Save the *.pem file locally. To change its permissions " +"so that only you can read and write to the file, run the following command:" +msgstr "" + +#: ./doc/user-guide/section_dashboard_access_and_security.xml174(replaceable) +#: ./doc/user-guide/section_dashboard_access_and_security.xml189(replaceable) +msgid "MY_PRIV_KEY" +msgstr "" + +#: ./doc/user-guide/section_dashboard_access_and_security.xml176(para) +msgid "" +"If you are using the dashboard from a Windows-based computer, use puttygen " +"to load the *.pem and convert and save as " +"*.ppk. Refer to WinSCP information " +"for more details." +msgstr "" + +#: ./doc/user-guide/section_dashboard_access_and_security.xml187(para) +msgid "To make the keypair known to SSH, run the command:" +msgstr "" + +#: ./doc/user-guide/section_dashboard_access_and_security.xml192(para) +msgid "The Compute database registers the public key of the keypair." +msgstr "" + +#: ./doc/user-guide/section_dashboard_access_and_security.xml194(para) +msgid "" +"The dashboard lists the keypair in the Access & " +"Security category." +msgstr "" + +#: ./doc/user-guide/section_cli_swift_howto.xml6(title) +msgid "Manage objects and containers" +msgstr "" + +#: ./doc/user-guide/section_cli_swift_howto.xml7(para) +msgid "" +"The OpenStack Object Storage Service provides the client, " +"which is a command-line interface (CLI). Use this client to list objects and" +" containers, upload objects to containers, and download or delete objects " +"from containers. You can also gather statistics and update metadata for " +"accounts, containers, and objects." +msgstr "" + +#: ./doc/user-guide/section_cli_swift_howto.xml13(para) +msgid "" +"This client is based on the native swift client library, " +"client.py, which seamlessly re-authenticates if the " +"current token expires during processing, retries operations multiple times, " +"and provides a processing concurrency of 10." +msgstr "" + +#: ./doc/user-guide/section_cli_swift_howto.xml18(para) +msgid "" +"Users have roles on accounts. For example, a user with the admin role has " +"full access to all containers and objects in an account. You can set access " +"control lists (ACLs) at the container level and support lists for read and " +"write access, which you set with the X-Container-Read and" +" X-Container-Write header, respectively." +msgstr "" + +#: ./doc/user-guide/section_cli_swift_howto.xml25(para) +msgid "" +"To give a user read access, use the command with the " +"-r parameter. To give a user write access, use the " +"-w parameter." +msgstr "" + +#: ./doc/user-guide/section_cli_swift_howto.xml29(para) +msgid "" +"The following example enables the testuser user to read " +"objects in the container:" +msgstr "" + +#: ./doc/user-guide/section_cli_swift_howto.xml33(para) +msgid "You can also use this command with a list of users." +msgstr "" + +#: ./doc/user-guide/section_cli_swift_howto.xml34(para) +msgid "" +"If you use StaticWeb middleware to enable Object Storage to serve public web" +" content, use .r:, followed by a list of allowed " +"referrers." +msgstr "" + +#: ./doc/user-guide/section_cli_swift_howto.xml37(para) +msgid "The following command gives object access to all referring domains:" +msgstr "" + +#: ./doc/user-guide/section_cli_nova_config-drive.xml6(title) +msgid "Store metadata on a configuration drive" +msgstr "" + +#: ./doc/user-guide/section_cli_nova_config-drive.xml7(para) +msgid "" +"You can configure OpenStack to write metadata to a special configuration " +"drive that attaches to the instance when it boots. The instance can mount " +"this drive and read files from it to get information that is normally " +"available through the metadata service." +msgstr "" + +#: ./doc/user-guide/section_cli_nova_config-drive.xml14(para) +msgid "" +"One use case for the configuration drive is to pass a networking " +"configuration when you do not use DHCP to assign IP addresses to instances. " +"For example, you might pass the IP configuration for the instance through " +"the configuration drive, which the instance can mount and access before the " +"you configure the network settings for the instance." +msgstr "" + +#: ./doc/user-guide/section_cli_nova_config-drive.xml20(para) +msgid "" +"Any modern guest operating system that is capable of mounting an ISO9660 or " +"VFAT file system can use the configuration drive." +msgstr "" + +#: ./doc/user-guide/section_cli_nova_config-drive.xml24(title) +msgid "Requirements and guidelines" +msgstr "" + +#: ./doc/user-guide/section_cli_nova_config-drive.xml26(title) +msgid "Compute host requirements" +msgstr "" + +#: ./doc/user-guide/section_cli_nova_config-drive.xml28(para) +msgid "" +"The following hypervisors support the configuration drive: libvirt, " +"xenserver, hyper-v, and vmware." +msgstr "" + +#: ./doc/user-guide/section_cli_nova_config-drive.xml33(para) +msgid "" +"To use configuration drive with libvirt, xenserver, or vmware, you must " +"first install the genisoimage package on each Compute " +"host. Otherwise, instances do not boot properly." +msgstr "" + +#: ./doc/user-guide/section_cli_nova_config-drive.xml39(para) +msgid "" +"Use the mkisofs_cmd flag to set the path where you " +"install the genisoimage program. If " +"genisoimage is in same path as the nova-compute service, you do not need to set " +"this flag." +msgstr "" + +#: ./doc/user-guide/section_cli_nova_config-drive.xml47(para) +msgid "" +"By default, Ubuntu packages do not install this package. See bug #1165174." +msgstr "" + +#: ./doc/user-guide/section_cli_nova_config-drive.xml54(para) +msgid "" +"To use configuration drive with hyper-v, you must set the " +"mkisofs_cmd value to the full path to an " +"mkisofs.exe installation. Additionally, you must set the " +"qemu_img_cmd value in the hyperv " +"configuration section to the full path to an qemu-img " +"command installation." +msgstr "" + +#: ./doc/user-guide/section_cli_nova_config-drive.xml67(title) +msgid "Image requirements" +msgstr "" + +#: ./doc/user-guide/section_cli_nova_config-drive.xml69(para) +msgid "" +"An image built with a recent version of the cloud-init " +"package can automatically access metadata passed through the configuration " +"drive. The cloud-init package version 0.7.1 works with " +"Ubuntu and Fedora-based images, such as RHEL." +msgstr "" + +#: ./doc/user-guide/section_cli_nova_config-drive.xml78(para) +msgid "" +"If an image does not have the cloud-init package " +"installed, you must customize the image to run a script that mounts the " +"configuration drive on boot, reads the data from the drive, and takes " +"appropriate action such as adding the public key to an account. See for details on how data is organized on " +"the configuration drive." +msgstr "" + +#: ./doc/user-guide/section_cli_nova_config-drive.xml90(para) +msgid "" +"If you use Xen with a configuration drive, use the " +"xenapi_disable_agent configuration parameter to disable " +"the agent." +msgstr "" + +#: ./doc/user-guide/section_cli_nova_config-drive.xml97(title) +msgid "Guidelines" +msgstr "" + +#: ./doc/user-guide/section_cli_nova_config-drive.xml99(para) +msgid "" +"Do not rely on the presence of the EC2 metadata present in the configuration" +" drive, as this content might be removed in a future release. For example, " +"do not rely on files in the ec2 directory." +msgstr "" + +#: ./doc/user-guide/section_cli_nova_config-drive.xml106(para) +msgid "" +"When you create images that access configuration drive data and multiple " +"directories are under the openstack directory, always " +"select the highest API version by date that your consumer supports. For " +"example, if your guest image supports the 2012-03-05, 2012-08-05, 2013-04-13" +" versions, try 2013-04-13 first and fall back to a previous version if " +"2013-04-13 is not present." +msgstr "" + +#: ./doc/user-guide/section_cli_nova_config-drive.xml119(title) +msgid "Enable and access the configuration drive" +msgstr "" + +#: ./doc/user-guide/section_cli_nova_config-drive.xml122(para) +msgid "" +"To enable the configuration drive, pass the --config-" +"drive=true parameter to the command." +msgstr "" + +#: ./doc/user-guide/section_cli_nova_config-drive.xml126(para) +msgid "" +"This example enables the configuration drive and passes user data, two " +"files, and two key/value metadata pairs, all of which are accessible from " +"the configuration drive:" +msgstr "" + +#: ./doc/user-guide/section_cli_nova_config-drive.xml131(para) +msgid "" +"You can also configure the Compute service to always create a configuration " +"drive." +msgstr "" + +#: ./doc/user-guide/section_cli_nova_config-drive.xml133(para) +msgid "Set this option in the /etc/nova/nova.conf file:" +msgstr "" + +#: ./doc/user-guide/section_cli_nova_config-drive.xml138(para) +msgid "" +"If a user passes the --config-drive=true flag to the " +" command, an administrator cannot disable the configuration " +"drive." +msgstr "" + +#: ./doc/user-guide/section_cli_nova_config-drive.xml146(para) +msgid "" +"The configuration drive has the config-2 volume label. If" +" your guest operating system supports accessing disk by label, you can mount" +" the configuration drive as the /dev/disk/by-" +"label/config-2 device." +msgstr "" + +#: ./doc/user-guide/section_cli_nova_config-drive.xml153(para) +msgid "For example:" +msgstr "" + +#: ./doc/user-guide/section_cli_nova_config-drive.xml157(para) +msgid "" +"Make sure that you use at least version 0.3.1 of CirrOS for configuration " +"drive support." +msgstr "" + +#: ./doc/user-guide/section_cli_nova_config-drive.xml160(para) +msgid "" +"If your guest operating system does not use udev, the " +"/dev/disk/by-label directory is not present." +msgstr "" + +#: ./doc/user-guide/section_cli_nova_config-drive.xml164(para) +msgid "" +"You can use the command to identify the block device that " +"corresponds to the configuration drive. For example, when you boot the " +"CirrOS image with the m1.tiny flavor, the device is " +"/dev/vdb:" +msgstr "" + +#: ./doc/user-guide/section_cli_nova_config-drive.xml172(para) +msgid "Once identified, you can mount the device:" +msgstr "" + +#: ./doc/user-guide/section_cli_nova_config-drive.xml179(title) +msgid "Configuration drive contents" +msgstr "" + +#: ./doc/user-guide/section_cli_nova_config-drive.xml180(para) +msgid "In this example, the contents of the configuration drive are:" +msgstr "" + +#: ./doc/user-guide/section_cli_nova_config-drive.xml193(para) +msgid "" +"The files that appear on the configuration drive depend on the arguments " +"that you pass to the command." +msgstr "" + +#: ./doc/user-guide/section_cli_nova_config-drive.xml198(title) +msgid "OpenStack metadata format" +msgstr "" + +#: ./doc/user-guide/section_cli_nova_config-drive.xml199(para) +msgid "" +"The following example shows the contents of the " +"openstack/2012-08-10/meta_data.json and " +"openstack/latest/meta_data.json files. These files are " +"identical. The file contents are formatted for readability:" +msgstr "" + +#: ./doc/user-guide/section_cli_nova_config-drive.xml206(para) +msgid "" +"Note the effect of the --file /etc/network/interfaces=/home/myuser" +"/instance-interfaces argument that was passed to the " +" command. The contents of this file are contained in the " +"openstack/content/0000 file on the configuration drive," +" and the path is specified as /etc/network/interfaces " +"in the meta_data.json file." +msgstr "" + +#: ./doc/user-guide/section_cli_nova_config-drive.xml217(title) +msgid "EC2 metadata format" +msgstr "" + +#: ./doc/user-guide/section_cli_nova_config-drive.xml218(para) +msgid "" +"The following example shows the contents of the ec2/2009-04-04" +"/meta-data.json, latest/meta-data.json " +"files. These files are identical. The file contents are formatted to improve" +" readability:" +msgstr "" + +#: ./doc/user-guide/section_cli_nova_config-drive.xml226(title) +msgid "User data" +msgstr "" + +#: ./doc/user-guide/section_cli_nova_config-drive.xml227(para) +msgid "" +"The openstack/2012-08-10/user_data, " +"openstack/latest/user_data, ec2/2009-04-04" +"/user-data, and ec2/latest/user-data file " +"are present only if the --user-data flag and the contents" +" of the user data file are passed to the command." +msgstr "" + +#: ./doc/user-guide/section_cli_nova_config-drive.xml237(title) +msgid "Configuration drive format" +msgstr "" + +#: ./doc/user-guide/section_cli_nova_config-drive.xml238(para) +msgid "" +"The default format of the configuration drive as an ISO 9660 file system. To" +" explicitly specify the ISO 9660 format, add the following line to the " +"/etc/nova/nova.conf file:" +msgstr "" + +#: ./doc/user-guide/section_cli_nova_config-drive.xml244(para) +msgid "" +"By default, you cannot attach the configuration drive image as a CD drive " +"instead of as a disk drive. To attach a CD drive, add this line to the " +"/etc/nova/nova.conf file:" +msgstr "" + +#: ./doc/user-guide/section_cli_nova_config-drive.xml250(para) +msgid "" +"For legacy reasons, you can configure the configuration drive to use VFAT " +"format instead of ISO 9660. It is unlikely that you would require VFAT " +"format because ISO 9660 is widely supported across operating systems. " +"However, to use the VFAT format, add the following line to the " +"/etc/nova/nova.conf file:" +msgstr "" + +#: ./doc/user-guide/section_cli_nova_config-drive.xml259(para) +msgid "If you choose VFAT, the configuration drive is 64 MBs." +msgstr "" + +#: ./doc/user-guide/section_cli_nova_config-drive.xml264(title) +msgid "Configuration drive reference" +msgstr "" + +#: ./doc/user-guide/section_cli_nova_config-drive.xml265(para) +msgid "" +"The following table shows the configuration options for the configuration " +"drive:" +msgstr "" + +#: ./doc/user-guide/section_sdk_install.xml6(title) +msgid "Install the OpenStack SDK" +msgstr "" + +#: ./doc/user-guide/section_sdk_install.xml7(para) +msgid "" +"Each OpenStack project has its own Python library. These libraries are " +"bundled with the command-line clients. For example, the Python bindings for " +"the Compute API are bundled with the python-novaclient " +"package." +msgstr "" + +#: ./doc/user-guide/section_sdk_install.xml11(para) +msgid "" +"For details about how to install the clients, see install the OpenStack command-line " +"clients." +msgstr "" + +#: ./doc/user-guide/section_sdk_auth_neutron.xml6(title) +msgid "Authenticate against a Networking endpoint" +msgstr "" + +#: ./doc/user-guide/section_sdk_auth_neutron.xml7(para) +msgid "" +"To authenticate against a Networking endpoint, instantiate a " +"neutronclient.v_2_0.client.Client object:" +msgstr "" + +#: ./doc/user-guide/section_sdk_auth_neutron.xml18(para) +msgid "" +"You can also authenticate by explicitly specifying the endpoint and token:" +msgstr "" + +#: ./doc/user-guide/section_cli_ceilometer.xml8(title) +msgid "Measure cloud resources" +msgstr "" + +#: ./doc/user-guide/section_cli_ceilometer.xml9(para) +msgid "The OpenStack Telemetry service measures cloud resources in OpenStack." +msgstr "" + +#: ./doc/user-guide/section_cli_ceilometer.xml11(para) +msgid "" +"It collects information about how much, who, what, and when with regards to " +"billing. Currently, metering is available through only the " +"command-line client." +msgstr "" + +#: ./doc/user-guide/section_cli_ceilometer.xml15(para) +msgid "To model data, the Telemetry service uses these abstractions:" +msgstr "" + +#: ./doc/user-guide/section_cli_ceilometer.xml19(emphasis) +msgid "Meter" +msgstr "" + +#: ./doc/user-guide/section_cli_ceilometer.xml21(para) +msgid "" +"Measures a specific aspect of resource usage, such as the existence of a " +"running instance, or ongoing performance, such as the CPU utilization for an" +" instance. Meters exist for each type of resource. For example, a separate " +"cpu_util meter exists for each instance. The life cycle " +"of a meter is decoupled from the existence of its related resource. The " +"meter persists after the resource goes away." +msgstr "" + +#: ./doc/user-guide/section_cli_ceilometer.xml31(para) +msgid "A meter has the following attributes:" +msgstr "" + +#: ./doc/user-guide/section_cli_ceilometer.xml34(para) +msgid "String name." +msgstr "" + +#: ./doc/user-guide/section_cli_ceilometer.xml37(para) +msgid "A unit of measurement." +msgstr "" + +#: ./doc/user-guide/section_cli_ceilometer.xml40(para) +msgid "" +"A type. Indicates whether values increase monotonically (cumulative), are " +"interpreted as a change from the previous value (delta), or are standalone " +"and relate only to the current duration (gauge)." +msgstr "" + +#: ./doc/user-guide/section_cli_ceilometer.xml51(emphasis) +msgid "Sample" +msgstr "" + +#: ./doc/user-guide/section_cli_ceilometer.xml53(para) +msgid "" +"An individual data point that is associated with a specific meter. Has the " +"same attributes as the meter, with the addition of timestamp and value " +"attributes. The value attribute is also known as the sample volume." +msgstr "" + +#: ./doc/user-guide/section_cli_ceilometer.xml62(emphasis) +msgid "Statistic" +msgstr "" + +#: ./doc/user-guide/section_cli_ceilometer.xml64(para) +msgid "" +"A set of data point aggregates over a time duration. (In contrast, a sample " +"represents a single data point.) The Telemetry service employs these " +"aggregation functions:" +msgstr "" + +#: ./doc/user-guide/section_cli_ceilometer.xml70(para) +msgid "" +"count. The number of samples in each " +"period." +msgstr "" + +#: ./doc/user-guide/section_cli_ceilometer.xml75(para) +msgid "" +"max. The maximum number of sample volumes" +" in each period." +msgstr "" + +#: ./doc/user-guide/section_cli_ceilometer.xml80(para) +msgid "" +"min. The minimum number of sample volumes" +" in each period." +msgstr "" + +#: ./doc/user-guide/section_cli_ceilometer.xml85(para) +msgid "" +"avg. The average of sample volumes over " +"each period." +msgstr "" + +#: ./doc/user-guide/section_cli_ceilometer.xml90(para) +msgid "" +"sum. The sum of sample volumes over each " +"period." +msgstr "" + +#: ./doc/user-guide/section_cli_ceilometer.xml98(emphasis) +msgid "Alarm" +msgstr "" + +#: ./doc/user-guide/section_cli_ceilometer.xml100(para) +msgid "" +"A set of rules that define a monitor and a current state, with edge-" +"triggered actions associated with target states. Provides user-oriented " +"Monitoring-as-a-Service and a general purpose utility for Openstack. " +"Orchestration auto scaling is a typical use-case. Alarms follow a tristate " +"model of ok, alarm, and " +"insufficient data. For conventional threshold-oriented " +"alarms, a static threshold value and comparison operator govern state " +"transitions. The comparison operator compares a selected meter statistic " +"against an evaluation window of configurable length into the recent past." +msgstr "" + +#: ./doc/user-guide/section_cli_ceilometer.xml119(para) +msgid "" +"This example uses the client to create an auto-scaling " +"stack and the client to measure resources." +msgstr "" + +#: ./doc/user-guide/section_cli_ceilometer.xml125(para) +msgid "Create an auto-scaling stack:" +msgstr "" + +#: ./doc/user-guide/section_cli_ceilometer.xml129(para) +msgid "List the heat resources that were created:" +msgstr "" + +#: ./doc/user-guide/section_cli_ceilometer.xml146(para) +msgid "List the alarms that are set:" +msgstr "" + +#: ./doc/user-guide/section_cli_ceilometer.xml156(para) +msgid "List the meters that are set:" +msgstr "" + +#: ./doc/user-guide/section_cli_ceilometer.xml167(para) +msgid "List samples:" +msgstr "" + +#: ./doc/user-guide/section_cli_ceilometer.xml176(para) +msgid "View statistics:" +msgstr "" + +#: ./doc/user-guide/section_cli_nova_floating_ips.xml6(title) +msgid "Manage IP addresses" +msgstr "" + +#: ./doc/user-guide/section_cli_nova_floating_ips.xml7(para) +msgid "" +"Each instance can have a private, or fixed, IP address and a public, or " +"floating, one." +msgstr "" + +#: ./doc/user-guide/section_cli_nova_floating_ips.xml9(para) +msgid "" +"Private IP addresses are used for communication between instances, and " +"public ones are used for communication with the outside world." +msgstr "" + +#: ./doc/user-guide/section_cli_nova_floating_ips.xml12(para) +msgid "" +"When you launch an instance, it is automatically assigned a private IP " +"address that stays the same until you explicitly terminate the instance. " +"Rebooting an instance has no effect on the private IP address." +msgstr "" + +#: ./doc/user-guide/section_cli_nova_floating_ips.xml16(para) +msgid "" +"A pool of floating IPs, configured by the cloud operator, is available in " +"OpenStack Compute." +msgstr "" + +#: ./doc/user-guide/section_cli_nova_floating_ips.xml18(para) +msgid "" +"You can allocate a certain number of these to a project: The maximum number " +"of floating IP addresses per project is defined by the quota." +msgstr "" + +#: ./doc/user-guide/section_cli_nova_floating_ips.xml21(para) +msgid "" +"You can add a floating IP address from this set to an instance of the " +"project. Floating IP addresses can be dynamically disassociated and " +"associated with other instances of the same project at any time." +msgstr "" + +#: ./doc/user-guide/section_cli_nova_floating_ips.xml25(para) +msgid "" +"Before you can assign a floating IP address to an instance, you first must " +"allocate floating IPs to a project. After floating IP addresses have been " +"allocated to the current project, you can assign them to running instances." +msgstr "" + +#: ./doc/user-guide/section_cli_nova_floating_ips.xml29(para) +msgid "You can assign a floating IP address to one instance at a time." +msgstr "" + +#: ./doc/user-guide/section_cli_nova_floating_ips.xml32(title) +msgid "List floating IP address information" +msgstr "" + +#: ./doc/user-guide/section_cli_nova_floating_ips.xml35(para) +msgid "To list all floating IP addresses:" +msgstr "" + +#: ./doc/user-guide/section_cli_nova_floating_ips.xml63(para) +msgid "To list all pools that provide floating IP addresses:" +msgstr "" + +#: ./doc/user-guide/section_cli_nova_floating_ips.xml76(title) +msgid "Assign floating IP addresses" +msgstr "" + +#: ./doc/user-guide/section_cli_nova_floating_ips.xml77(para) +msgid "You can assign floating IP addresses to a project or an instance." +msgstr "" + +#: ./doc/user-guide/section_cli_nova_floating_ips.xml81(para) +msgid "" +"Allocate a floating IP address to the current project. If more than one IP " +"address pool is available, you can specify the pool from which to allocate " +"the IP address. This example specifies the public pool:" +msgstr "" + +#: ./doc/user-guide/section_cli_nova_floating_ips.xml94(para) +msgid "To release a floating IP address from the current project:" +msgstr "" + +#: ./doc/user-guide/section_cli_nova_floating_ips.xml96(replaceable) +#: ./doc/user-guide/section_cli_nova_floating_ips.xml108(replaceable) +#: ./doc/user-guide/section_cli_nova_floating_ips.xml118(replaceable) +msgid "FLOATING_IP" +msgstr "" + +#: ./doc/user-guide/section_cli_nova_floating_ips.xml97(para) +msgid "" +"The IP address is returned to the pool of IP addresses that are available " +"for all projects. If an IP address is assigned to a running instance, it is " +"disassociated from the instance." +msgstr "" + +#: ./doc/user-guide/section_cli_nova_floating_ips.xml103(para) +msgid "" +"To associate an IP address with an instance, at least one floating IP " +"address must be allocated to the current project." +msgstr "" + +#: ./doc/user-guide/section_cli_nova_floating_ips.xml106(para) +msgid "To assign a floating IP address to an instance:" +msgstr "" + +#: ./doc/user-guide/section_cli_nova_floating_ips.xml108(replaceable) +#: ./doc/user-guide/section_cli_nova_floating_ips.xml118(replaceable) +msgid "INSTANCE_NAME_OR_ID" +msgstr "" + +#: ./doc/user-guide/section_cli_nova_floating_ips.xml109(para) +msgid "" +"After you assign the IP address and configure security group rules for the " +"instance, the instance is publicly available at the floating IP address." +msgstr "" + +#: ./doc/user-guide/section_cli_nova_floating_ips.xml115(para) +msgid "" +"To remove a floating IP address from an instance, specify the same arguments" +" that you used to assign the IP address:" +msgstr "" + +#: ./doc/user-guide/section_sdk_auth_glance.xml6(title) +msgid "Authenticate against an Image Service endpoint" +msgstr "" + +#: ./doc/user-guide/section_sdk_auth_glance.xml7(para) +msgid "" +"To authenticate against an Image Service endpoint, instantiate a " +" glanceclient.v2.client.Client object:" +msgstr "" + +#: ./doc/user-guide/section_dashboard_stacks.xml12(title) +msgid "Launch and manage stacks" +msgstr "" + +#: ./doc/user-guide/section_dashboard_stacks.xml13(para) +msgid "" +"Heat is a service used to orchestrate multiple composite cloud applications " +"using the AWS CloudFormation template format, through both an OpenStack-" +"native ReST API and a CloudFormation-compatible Query API." +msgstr "" + +#: ./doc/user-guide/section_dashboard_stacks.xml17(para) +msgid "" +"The purpose of Heat is to provide a template based orchestration for " +"describing a cloud application by executing appropriate OpenStack API calls " +"to generate running cloud applications, integrate other core components of " +"OpenStack into a one-file template system. The templates allow creation of " +"most OpenStack resource types such as instances, floating ips, volumes, " +"security groups, users, etc." +msgstr "" + +#: ./doc/user-guide/section_dashboard_stacks.xml25(title) +msgid "Launch a stack" +msgstr "" + +#: ./doc/user-guide/section_dashboard_stacks.xml28(para) +msgid "" +"Log in to the dashboard, choose a project, and click " +"Stacks in the Orchestration " +"category." +msgstr "" + +#: ./doc/user-guide/section_dashboard_stacks.xml34(para) +msgid "Click Launch Stack." +msgstr "" + +#: ./doc/user-guide/section_dashboard_stacks.xml39(para) +msgid "" +"In the Select Template window, choose a template source" +" option, URL, File, or " +"Direct Input, from the drop-down list." +msgstr "" + +#: ./doc/user-guide/section_dashboard_stacks.xml47(para) +msgid "" +"Enter the URL, browse to the file location, or directly include the template" +" based on your previous selection." +msgstr "" + +#: ./doc/user-guide/section_dashboard_stacks.xml52(para) +msgid "" +"In the Launch Stack window, specify the following " +"values." +msgstr "" + +#: ./doc/user-guide/section_dashboard_stacks.xml59(guilabel) +msgid "Stack Name" +msgstr "" + +#: ./doc/user-guide/section_dashboard_stacks.xml61(para) +msgid "A name to identify the stack." +msgstr "" + +#: ./doc/user-guide/section_dashboard_stacks.xml65(guilabel) +msgid "Creation Timeout (minutes)" +msgstr "" + +#: ./doc/user-guide/section_dashboard_stacks.xml67(para) +msgid "Creation Timeout in minutes." +msgstr "" + +#: ./doc/user-guide/section_dashboard_stacks.xml71(guilabel) +msgid "Rollback On Failure" +msgstr "" + +#: ./doc/user-guide/section_dashboard_stacks.xml73(para) +msgid "Check this option if you want Heat to rollback on failure." +msgstr "" + +#: ./doc/user-guide/section_dashboard_stacks.xml78(guilabel) +msgid "Password for user \"demo\"" +msgstr "" + +#: ./doc/user-guide/section_dashboard_stacks.xml80(para) +msgid "Password for the user logged in." +msgstr "" + +#: ./doc/user-guide/section_dashboard_stacks.xml84(guilabel) +msgid "DBUsername" +msgstr "" + +#: ./doc/user-guide/section_dashboard_stacks.xml85(para) +msgid "Database user name." +msgstr "" + +#: ./doc/user-guide/section_dashboard_stacks.xml88(guilabel) +msgid "LinuxDistribution" +msgstr "" + +#: ./doc/user-guide/section_dashboard_stacks.xml89(para) +msgid "Linux Distribution used in the stacks." +msgstr "" + +#: ./doc/user-guide/section_dashboard_stacks.xml93(guilabel) +msgid "DBRootPassword" +msgstr "" + +#: ./doc/user-guide/section_dashboard_stacks.xml94(para) +msgid "Database root password." +msgstr "" + +#: ./doc/user-guide/section_dashboard_stacks.xml98(guilabel) +msgid "KeyName" +msgstr "" + +#: ./doc/user-guide/section_dashboard_stacks.xml99(para) +msgid "Name of the keypair." +msgstr "" + +#: ./doc/user-guide/section_dashboard_stacks.xml102(guilabel) +msgid "DBName" +msgstr "" + +#: ./doc/user-guide/section_dashboard_stacks.xml103(para) +msgid "Database name." +msgstr "" + +#: ./doc/user-guide/section_dashboard_stacks.xml106(guilabel) +msgid "DBPassword" +msgstr "" + +#: ./doc/user-guide/section_dashboard_stacks.xml107(para) +msgid "Database password." +msgstr "" + +#: ./doc/user-guide/section_dashboard_stacks.xml110(guilabel) +msgid "InstanceType" +msgstr "" + +#: ./doc/user-guide/section_dashboard_stacks.xml111(para) +msgid "Flavor of the instance." +msgstr "" + +#: ./doc/user-guide/section_dashboard_stacks.xml118(para) +msgid "Click Launch to create a stack." +msgstr "" + +#: ./doc/user-guide/section_dashboard_stacks.xml122(para) +msgid "" +"The dashboard shows the stack in the Stacks category." +msgstr "" + +#: ./doc/user-guide/section_dashboard_stacks.xml126(para) +msgid "" +"After the stack is created, click on the stack name to see these details:" +msgstr "" + +#: ./doc/user-guide/section_dashboard_stacks.xml130(guilabel) +msgid "Topology" +msgstr "" + +#: ./doc/user-guide/section_dashboard_stacks.xml132(para) +msgid "The topology of the stack created." +msgstr "" + +#: ./doc/user-guide/section_dashboard_stacks.xml136(guilabel) +msgid "Overview" +msgstr "" + +#: ./doc/user-guide/section_dashboard_stacks.xml138(para) +msgid "" +"The parameters and details of the stack under the following headings: " +"Info, Status, " +"Outputs, Stack Parameters, and " +"Launch Parameters." +msgstr "" + +#: ./doc/user-guide/section_dashboard_stacks.xml149(guilabel) +msgid "Resources" +msgstr "" + +#: ./doc/user-guide/section_dashboard_stacks.xml151(para) +msgid "The resources used by the stack." +msgstr "" + +#: ./doc/user-guide/section_dashboard_stacks.xml155(guilabel) +msgid "Events" +msgstr "" + +#: ./doc/user-guide/section_dashboard_stacks.xml157(para) +msgid "The events related to the stack." +msgstr "" + +#: ./doc/user-guide/section_dashboard_stacks.xml163(title) +msgid "Delete stacks" +msgstr "" + +#: ./doc/user-guide/section_dashboard_stacks.xml166(para) +#: ./doc/user-guide/section_dashboard_manage_images.xml29(para) +#: ./doc/user-guide/section_dashboard_manage_images.xml113(para) +#: ./doc/user-guide/section_dashboard_manage_images.xml144(para) +msgid "Log in to the dashboard." +msgstr "" + +#: ./doc/user-guide/section_dashboard_stacks.xml169(para) +msgid "" +"On the Project tab, click the " +"Stacks category." +msgstr "" + +#: ./doc/user-guide/section_dashboard_stacks.xml173(para) +msgid "Select the stack that you want to delete." +msgstr "" + +#: ./doc/user-guide/section_dashboard_stacks.xml176(para) +msgid "Click Delete Stack." +msgstr "" + +#: ./doc/user-guide/section_dashboard_stacks.xml180(para) +msgid "" +"In the Confirm Delete Stack window, click " +"Delete Stack to confirm the deletion. You cannot undo" +" this action." +msgstr "" + +#: ./doc/user-guide/section_sdk_authenticate.xml5(title) +msgid "Authentication" +msgstr "" + +#: ./doc/user-guide/section_sdk_authenticate.xml6(para) +msgid "" +"You must authenticate against an OpenStack endpoint before you can use " +"OpenStack services. Each project uses a slightly different syntax for doing " +"authentication." +msgstr "" + +#: ./doc/user-guide/section_sdk_authenticate.xml9(para) +msgid "" +"You must typically authenticate against a specific version of a service. For" +" example, a client might need to authenticate against the Identity Service " +"v2.0." +msgstr "" + +#: ./doc/user-guide/section_sdk_authenticate.xml12(para) +msgid "" +"Python scripts that use the OpenStack SDK must have access to the " +"credentials contained in the OpenStack RC " +"file. Because credentials are sensitive information, do not include " +"them in your scripts. This guide assumes that users source the " +"openrc.sh file and access the credentials by using the " +"environment variables in the Python scripts." +msgstr "" + +#. When image changes, this message will be marked fuzzy or untranslated for +#. you. +#. It doesn't matter what you translate it to: it's not used at all. +#: ./doc/user-guide/section_dashboard_manage_images.xml48(None) +msgid "" +"@@image: '../common/figures/user_image_create.png'; " +"md5=9371228508180bf0cf3f8778ccf50d84" +msgstr "" + +#: ./doc/user-guide/section_dashboard_manage_images.xml6(title) +msgid "Create and manage images" +msgstr "" + +#: ./doc/user-guide/section_dashboard_manage_images.xml7(para) +msgid "" +"The cloud operator assigns roles to users. Roles determine who can upload " +"and manage images. The operator might restrict image upload and management " +"to only cloud administrators or operators." +msgstr "" + +#: ./doc/user-guide/section_dashboard_manage_images.xml11(para) +msgid "" +"If you have admin privileges, you can use the dashboard to create and manage" +" images in the admin project." +msgstr "" + +#: ./doc/user-guide/section_dashboard_manage_images.xml15(title) +msgid "Manage images by using clients and APIs" +msgstr "" + +#: ./doc/user-guide/section_dashboard_manage_images.xml16(para) +msgid "" +"You can also use the and command-line " +"clients or the Image Service and Compute APIs to manage images. See ." +msgstr "" + +#: ./doc/user-guide/section_dashboard_manage_images.xml22(title) +msgid "Create images" +msgstr "" + +#: ./doc/user-guide/section_dashboard_manage_images.xml23(para) +msgid "" +"For details about image creation, see the Virtual " +"Machine Image Guide." +msgstr "" + +#: ./doc/user-guide/section_dashboard_manage_images.xml30(para) +#: ./doc/user-guide/section_dashboard_manage_images.xml114(para) +#: ./doc/user-guide/section_dashboard_manage_images.xml145(para) +msgid "" +"Choose the admin project from the CURRENT " +"PROJECT drop-down list." +msgstr "" + +#: ./doc/user-guide/section_dashboard_manage_images.xml35(para) +#: ./doc/user-guide/section_dashboard_manage_images.xml119(para) +#: ./doc/user-guide/section_dashboard_manage_images.xml150(para) +msgid "" +"On the Project tab, click the Images & " +"Snapshots category." +msgstr "" + +#: ./doc/user-guide/section_dashboard_manage_images.xml40(para) +msgid "" +"Click Create Image. The Create An " +"Image window appears:" +msgstr "" + +#: ./doc/user-guide/section_dashboard_manage_images.xml54(para) +msgid "" +"In the Create An Image window, enter or select the " +"following values:" +msgstr "" + +#: ./doc/user-guide/section_dashboard_manage_images.xml61(guilabel) +msgid "Name" +msgstr "" + +#: ./doc/user-guide/section_dashboard_manage_images.xml62(para) +msgid "Enter a name for the image." +msgstr "" + +#: ./doc/user-guide/section_dashboard_manage_images.xml65(guilabel) +msgid "Description" +msgstr "" + +#: ./doc/user-guide/section_dashboard_manage_images.xml66(para) +msgid "Enter a brief description about the image." +msgstr "" + +#: ./doc/user-guide/section_dashboard_manage_images.xml70(guilabel) +msgid "Image Location" +msgstr "" + +#: ./doc/user-guide/section_dashboard_manage_images.xml72(para) +msgid "Include the URL of the image." +msgstr "" + +#: ./doc/user-guide/section_dashboard_manage_images.xml75(guilabel) +msgid "Image File" +msgstr "" + +#: ./doc/user-guide/section_dashboard_manage_images.xml76(para) +msgid "Alternatively, browse to find the file on your machine." +msgstr "" + +#: ./doc/user-guide/section_dashboard_manage_images.xml80(guilabel) +msgid "Format" +msgstr "" + +#: ./doc/user-guide/section_dashboard_manage_images.xml81(para) +msgid "Select the image format." +msgstr "" + +#: ./doc/user-guide/section_dashboard_manage_images.xml84(para) +msgid "" +"Minimum Disk (GB) and Maximum Disk " +"(GB)" +msgstr "" + +#: ./doc/user-guide/section_dashboard_manage_images.xml86(para) +msgid "Leave these fields empty." +msgstr "" + +#: ./doc/user-guide/section_dashboard_manage_images.xml90(guilabel) +msgid "Public" +msgstr "" + +#: ./doc/user-guide/section_dashboard_manage_images.xml91(para) +msgid "Select this option to make the image public to all users." +msgstr "" + +#: ./doc/user-guide/section_dashboard_manage_images.xml95(guilabel) +msgid "Protected" +msgstr "" + +#: ./doc/user-guide/section_dashboard_manage_images.xml96(para) +msgid "" +"Select this option to ensure that only users with permissions can delete it." +msgstr "" + +#: ./doc/user-guide/section_dashboard_manage_images.xml103(para) +msgid "Click Create Image." +msgstr "" + +#: ./doc/user-guide/section_dashboard_manage_images.xml104(para) +msgid "" +"The image is queued to be uploaded. It might take some time before the " +"status changes from queued to active." +msgstr "" + +#: ./doc/user-guide/section_dashboard_manage_images.xml110(title) +msgid "Update images" +msgstr "" + +#: ./doc/user-guide/section_dashboard_manage_images.xml124(para) +msgid "" +"Select the image that you want to edit. In the More " +"drop-down list, click Edit." +msgstr "" + +#: ./doc/user-guide/section_dashboard_manage_images.xml129(para) +msgid "" +"In the Update Image window, you can change the name for" +" the image. Select the Public check box to make the " +"image public. Clear this check box to make the image private." +msgstr "" + +#: ./doc/user-guide/section_dashboard_manage_images.xml136(para) +msgid "Click Update Image." +msgstr "" + +#: ./doc/user-guide/section_dashboard_manage_images.xml141(title) +msgid "Delete images" +msgstr "" + +#: ./doc/user-guide/section_dashboard_manage_images.xml155(para) +msgid "Select the images that you want to delete." +msgstr "" + +#: ./doc/user-guide/section_dashboard_manage_images.xml158(para) +msgid "Click Delete Images." +msgstr "" + +#: ./doc/user-guide/section_dashboard_manage_images.xml161(para) +msgid "" +"In the Confirm Delete Image window, click " +"Delete Images to confirm the deletion. You cannot " +"undo this action." +msgstr "" + +#: ./doc/user-guide/ch_cli.xml10(title) +msgid "OpenStack command-line clients" +msgstr "" + +#: ./doc/user-guide/section_sdk_auth_nova.xml6(title) +msgid "Authenticate against a Compute endpoint" +msgstr "" + +#: ./doc/user-guide/section_sdk_auth_nova.xml7(para) +msgid "" +"To authenticate against a Compute endpoint, instantiate a " +"novaclient.v_1_1.client.Client object:" +msgstr "" + +#: ./doc/user-guide/section_sdk_auth_nova.xml18(para) +msgid "" +"Alternatively, you can instantiate a " +"novaclient.client.Client object and pass the version " +"number:" +msgstr "" + +#: ./doc/user-guide/section_sdk_auth_nova.xml28(para) +msgid "" +"If you authenticate against an endpoint that uses a custom authentication " +"back-end, you must load the authentication plug-in and pass it to the " +"constructor." +msgstr "" + +#: ./doc/user-guide/section_sdk_auth_nova.xml31(para) +msgid "" +"The Rackspace Public Cloud is an OpenStack deployment that uses a custom " +"authentication back-end. To authenticate against this cloud, you must " +"install the rackspace-novaclient library that contains the " +"Rackspace authentication plug-in, called rackspace. The " +"following Python code shows the additional modifications required to " +"instantiate a Client object that can authenticate " +"against the Rackspace custom authentication back-end." +msgstr "" + +#: ./doc/user-guide/section_sdk_auth_nova.xml53(para) +msgid "" +"If you set the OS_AUTH_SYSTEM environment variable, check" +" for this variable in your Python script to determine whether you need to " +"load a custom authentication back-end:" +msgstr "" + +#: ./doc/user-guide/section_sdk_configure_instances.xml10(para) +msgid "" +"To generate a keypair, call the novaclient.v1_1.keypairs.KeypairManager.create" +" method: " +msgstr "" + +#: ./doc/user-guide/section_sdk_configure_instances.xml21(para) +msgid "The Python script output looks something like this: " +msgstr "" + +#: ./doc/user-guide/section_sdk_configure_instances.xml30(para) +msgid "" +"You will typically write the private key to a file in order to use it later." +" The file must be readable and writeable by only the file owner, otherwise " +"the ssh client will refuse to read the private key file. It is safest to " +"create the file with the appropriate permissions, as shown in the following " +"example: " +msgstr "" + +#: ./doc/user-guide/section_sdk_configure_instances.xml51(para) +msgid "" +"If you have already generated a keypair with the public key located at " +"~/.ssh/id_rsa.pub, pass the contents of the file to the" +" " +" novaclient.v1_1.keypairs.KeypairManager.create method " +"to import the public key to Compute: " +msgstr "" + +#: ./doc/user-guide/section_sdk_configure_instances.xml65(title) +msgid "List keypairs" +msgstr "" + +#: ./doc/user-guide/section_sdk_configure_instances.xml66(para) +msgid "" +"To list keypairs, call the novaclient.v1_1.keypairs.KeypairManager.list" +" method: " +msgstr "" + +#: ./doc/user-guide/section_sdk_configure_instances.xml74(title) +#: ./doc/user-guide/section_cli_nova_configure_instances.xml128(title) +msgid "Create and manage security groups" +msgstr "" + +#: ./doc/user-guide/section_sdk_configure_instances.xml75(para) +msgid "" +"To list security groups for the current project, call the novaclient.v_1.security_groups.SecurityGroupManager.list" +" method: " +msgstr "" + +#: ./doc/user-guide/section_sdk_configure_instances.xml80(para) +msgid "" +"To create a security group with a specified name and description, call the " +"novaclient.v_1.security_groups.SecurityGroupManager.create" +" method: " +msgstr "" + +#: ./doc/user-guide/section_sdk_configure_instances.xml85(para) +msgid "" +"To delete a security group, call the " +" " +"novaclient.v_1.security_groups.SecurityGroupManager.delete" +" method, passing either a novaclient.v1_1.security_groups.SecurityGroup" +" object or group ID as an argument: " +msgstr "" + +#: ./doc/user-guide/section_sdk_configure_instances.xml99(title) +#: ./doc/user-guide/section_cli_nova_configure_instances.xml156(title) +msgid "Create and manage security group rules" +msgstr "" + +#: ./doc/user-guide/section_sdk_configure_instances.xml100(para) +msgid "" +"Access the security group rules from the rules attribute " +"of a novaclient.v1_1.security_groups.SecurityGroup" +" object: " +msgstr "" + +#: ./doc/user-guide/section_sdk_configure_instances.xml106(para) +msgid "" +"To add a rule, to a security group, call the novaclient.v1_1.security_group_rules.SecurityGroupRuleManager.create" +" method: " +msgstr "" + +#: ./doc/user-guide/section_cli_nova_manage_instances.xml6(title) +msgid "Manage instances and hosts" +msgstr "" + +#: ./doc/user-guide/section_cli_nova_manage_instances.xml7(para) +#: ./doc/user-guide/section_dashboard_launch_instances.xml13(para) +msgid "Instances are virtual machines that run inside the cloud." +msgstr "" + +#: ./doc/user-guide/section_sdk_auth_keystone.xml6(title) +msgid "Authenticate against an Identity Service endpoint" +msgstr "" + +#: ./doc/user-guide/section_sdk_auth_keystone.xml7(para) +msgid "" +"To authenticate against the Identity Service v2.0 endpoint, instantiate a " +"" +" keystoneclient.v_20.client.Client object:" +msgstr "" + +#: ./doc/user-guide/section_sdk_auth_keystone.xml18(para) +msgid "" +"After you instantiate a Client object, you can " +"retrieve the token by accessing its auth_token attribute " +"object:" +msgstr "" + +#: ./doc/user-guide/section_sdk_auth_keystone.xml24(para) +msgid "" +"If the Openstack cloud is configured to use public-key infrastructure (PKI) " +"tokens, the Python script output looks something like this:" +msgstr "" + +#: ./doc/user-guide/section_sdk_auth_keystone.xml35(para) +msgid "" +"This example shows a subset of a PKI token. A complete token is over 5000 " +"characters long." +msgstr "" + +#: ./doc/user-guide/section_dashboard_launch_instances.xml12(title) +msgid "Launch and manage instances" +msgstr "" + +#: ./doc/user-guide/section_dashboard_launch_instances.xml14(para) +msgid "" +"You can launch an " +"instance from an OpenStack image. The OpenStack Image Service " +"provides a pool of images that are accessible to members of different " +"projects." +msgstr "" + +#: ./doc/user-guide/section_dashboard_launch_instances.xml18(para) +msgid "" +"You can also launch" +" an instance from an image that you have copied to a persistent " +"volume. The instance boots from the volume, which is provided by " +"nova-volume through iSCSI. When " +"you launch an instance from a volume, especially note the following steps:" +msgstr "" + +#: ./doc/user-guide/section_dashboard_launch_instances.xml28(para) +msgid "" +"To select from which volume to boot, launch an instance from an arbitrary " +"image. The image you select does not boot. It is replaced by the image on " +"the volume that you choose in the next steps." +msgstr "" + +#: ./doc/user-guide/section_dashboard_launch_instances.xml32(para) +msgid "" +"To boot a Xen image from a volume, the image you launch in must be the same " +"type, fully virtualized or paravirtualized, as the one on the volume." +msgstr "" + +#: ./doc/user-guide/section_dashboard_launch_instances.xml37(para) +msgid "" +"Select the volume or volume snapshot from which to boot. Enter a device " +"name. Enter vda for KVM images or xvda" +" for Xen images." +msgstr "" + +#: ./doc/user-guide/section_dashboard_launch_instances.xml51(title) +msgid "SSH in to your instance" +msgstr "" + +#: ./doc/user-guide/section_dashboard_launch_instances.xml52(para) +msgid "To SSH into your instance, you use the downloaded keypair file." +msgstr "" + +#: ./doc/user-guide/section_dashboard_launch_instances.xml55(para) +msgid "The username is ubuntu for the Ubuntu cloud images on TryStack." +msgstr "" + +#: ./doc/user-guide/section_dashboard_launch_instances.xml60(para) +msgid "Copy the IP address for your instance." +msgstr "" + +#: ./doc/user-guide/section_dashboard_launch_instances.xml63(para) +msgid "" +"Use the SSH command to make a secure connection to the instance. For " +"example:" +msgstr "" + +#: ./doc/user-guide/section_dashboard_launch_instances.xml68(para) +msgid "At the prompt, type yes." +msgstr "" + +#: ./doc/user-guide/section_dashboard_launch_instances.xml74(title) +msgid "Track usage for instances" +msgstr "" + +#: ./doc/user-guide/section_dashboard_launch_instances.xml75(para) +msgid "" +"You can track usage for instances for each tenant, also known as a project. " +"You can track costs per month by showing metrics like number of VCPUs, " +"disks, RAM, and uptime for all your instances." +msgstr "" + +#: ./doc/user-guide/section_dashboard_launch_instances.xml81(para) +msgid "" +"Log in to the dashboard, choose a project, and click the " +"Overview category." +msgstr "" + +#: ./doc/user-guide/section_dashboard_launch_instances.xml86(para) +msgid "" +"To query the instance usage for a month, select a month and click " +"Submit." +msgstr "" + +#: ./doc/user-guide/section_dashboard_launch_instances.xml91(para) +msgid "" +"To download a summary, click Download CSV Summary." +msgstr "" + +#: ./doc/user-guide/section_dashboard_launch_instances.xml97(title) +msgid "Create instance snapshots" +msgstr "" + +#: ./doc/user-guide/section_dashboard_launch_instances.xml100(para) +#: ./doc/user-guide/section_dashboard_launch_instances.xml132(para) +msgid "" +"Log in to the dashboard, choose a project, and click the " +"Instances category." +msgstr "" + +#: ./doc/user-guide/section_dashboard_launch_instances.xml106(para) +msgid "" +"Select the instance from which to create a snapshot. From the " +"Actions drop-down list, select Create " +"Snapshot." +msgstr "" + +#: ./doc/user-guide/section_dashboard_launch_instances.xml112(para) +msgid "" +"In the Create Snapshot window, enter a name for the " +"snapshot. Click Create Snapshot. The Images" +" & Snapshots category shows the instance snapshot." +msgstr "" + +#: ./doc/user-guide/section_dashboard_launch_instances.xml119(para) +msgid "" +"To launch an instance from the snapshot, select the snapshot and click " +"Launch. Proceed with ." +msgstr "" + +#: ./doc/user-guide/section_dashboard_launch_instances.xml129(title) +msgid "Manage an instance" +msgstr "" + +#: ./doc/user-guide/section_dashboard_launch_instances.xml138(para) +msgid "Select an instance." +msgstr "" + +#: ./doc/user-guide/section_dashboard_launch_instances.xml141(para) +msgid "" +"In the More drop-down list in the " +"Actions column, select the state." +msgstr "" + +#: ./doc/user-guide/section_dashboard_launch_instances.xml144(para) +msgid "" +"You can resize or rebuild an instance. You can also choose to view the " +"instance console log. Depending on the current state of the instance, you " +"can choose to pause, resume, suspend, soft or hard reboot, or terminate an " +"instance." +msgstr "" + +#: ./doc/user-guide/section_dashboard_launch_instances_from_volume.xml12(title) +msgid "Launch an instance from a volume" +msgstr "" + +#: ./doc/user-guide/section_dashboard_launch_instances_from_volume.xml14(para) +msgid "" +"You can launch an instance directly from an image that has been copied to a " +"persistent volume." +msgstr "" + +#: ./doc/user-guide/section_dashboard_launch_instances_from_volume.xml18(para) +msgid "Create a volume that is large enough to store an unzipped image." +msgstr "" + +#: ./doc/user-guide/section_dashboard_launch_instances_from_volume.xml22(para) +msgid "Create an image." +msgstr "" + +#: ./doc/user-guide/section_dashboard_launch_instances_from_volume.xml23(para) +msgid "" +"For details, see Creating images " +"manually in the OpenStack Virtual Machine Image " +"Guide." +msgstr "" + +#: ./doc/user-guide/section_dashboard_launch_instances_from_volume.xml30(para) +msgid "Launch an instance." +msgstr "" + +#: ./doc/user-guide/section_dashboard_launch_instances_from_volume.xml33(para) +msgid "Attach the volume to the instance." +msgstr "" + +#: ./doc/user-guide/section_dashboard_launch_instances_from_volume.xml36(para) +msgid "" +"Assuming that the attached volume is mounted as /dev/vdb," +" use one of the following commands to copy the image to the attached volume:" +msgstr "" + +#: ./doc/user-guide/section_dashboard_launch_instances_from_volume.xml42(para) +msgid "For a raw image:" +msgstr "" + +#: ./doc/user-guide/section_dashboard_launch_instances_from_volume.xml44(para) +msgid "Alternatively, use ." +msgstr "" + +#: ./doc/user-guide/section_dashboard_launch_instances_from_volume.xml48(para) +msgid "For a non-raw image:" +msgstr "" + +#: ./doc/user-guide/section_dashboard_launch_instances_from_volume.xml52(para) +msgid "For a *.tar.bz2 image:" +msgstr "" + +#: ./doc/user-guide/section_dashboard_launch_instances_from_volume.xml58(para) +msgid "" +"Because only detached volumes are " +"available for booting, detach the volume." +msgstr "" + +#: ./doc/user-guide/section_dashboard_launch_instances_from_volume.xml63(para) +msgid "" +"Now, you can launch an instance from an image that has been copied to the " +"volume. The instance is booted from the volume, which is provided by " +"nova-volume through iSCSI. To " +"launch an instance from the volume, see ." +msgstr "" + +#: ./doc/user-guide/section_dashboard_launch_instances_from_image.xml12(title) +msgid "Launch an instance from an image" +msgstr "" + +#: ./doc/user-guide/section_dashboard_launch_instances_from_image.xml14(para) +msgid "" +"When you launch an instance from an image, OpenStack creates a local copy of" +" the image on the Compute node where the instance starts." +msgstr "" + +#: ./doc/user-guide/section_dashboard_launch_instances_from_image.xml19(para) +msgid "" +"Log in to the dashboard, choose a project, and click the Images " +"& Snapshot category." +msgstr "" + +#: ./doc/user-guide/section_dashboard_launch_instances_from_image.xml22(para) +msgid "" +"The dashboard shows the images that have been uploaded to OpenStack Image " +"Service and are available for this project." +msgstr "" + +#: ./doc/user-guide/section_dashboard_launch_instances_from_image.xml27(para) +msgid "Select an image and click Launch." +msgstr "" + +#: ./doc/user-guide/section_dashboard_launch_instances_from_image.xml31(para) +msgid "" +"In the Launch Image window, specify the following " +"values:" +msgstr "" + +#: ./doc/user-guide/section_dashboard_launch_instances_from_image.xml39(guilabel) +msgid "Details" +msgstr "" + +#: ./doc/user-guide/section_dashboard_launch_instances_from_image.xml44(guilabel) +msgid "Instance Source" +msgstr "" + +#: ./doc/user-guide/section_dashboard_launch_instances_from_image.xml46(para) +msgid "Image or snapshot." +msgstr "" + +#: ./doc/user-guide/section_dashboard_launch_instances_from_image.xml49(guilabel) +msgid "Instance Name" +msgstr "" + +#: ./doc/user-guide/section_dashboard_launch_instances_from_image.xml51(para) +msgid "The name to assign to the virtual machine." +msgstr "" + +#: ./doc/user-guide/section_dashboard_launch_instances_from_image.xml56(guilabel) +msgid "Flavor" +msgstr "" + +#: ./doc/user-guide/section_dashboard_launch_instances_from_image.xml57(para) +msgid "The size of the virtual machine to launch." +msgstr "" + +#: ./doc/user-guide/section_dashboard_launch_instances_from_image.xml61(guilabel) +msgid "Instance Count" +msgstr "" + +#: ./doc/user-guide/section_dashboard_launch_instances_from_image.xml63(para) +msgid "" +"To launch multiple instances, enter a value greater than 1. Default is 1." +msgstr "" + +#: ./doc/user-guide/section_dashboard_launch_instances_from_image.xml69(guilabel) +msgid "Access & Security" +msgstr "" + +#: ./doc/user-guide/section_dashboard_launch_instances_from_image.xml73(guilabel) +msgid "Keypair" +msgstr "" + +#: ./doc/user-guide/section_dashboard_launch_instances_from_image.xml74(para) +msgid "A keypair." +msgstr "" + +#: ./doc/user-guide/section_dashboard_launch_instances_from_image.xml75(para) +msgid "" +"In case an image uses a static root password or a static key set (neither is" +" recommended), you do not need to provide a keypair to launch the instance." +msgstr "" + +#: ./doc/user-guide/section_dashboard_launch_instances_from_image.xml82(guilabel) +msgid "Security Groups" +msgstr "" + +#: ./doc/user-guide/section_dashboard_launch_instances_from_image.xml85(para) +msgid "Activate the security groups that you want to assign to the instance." +msgstr "" + +#: ./doc/user-guide/section_dashboard_launch_instances_from_image.xml88(para) +msgid "" +"Security groups are a kind of cloud firewall that define which incoming " +"network traffic is forwarded to instances. For details, see ." +msgstr "" + +#: ./doc/user-guide/section_dashboard_launch_instances_from_image.xml94(para) +msgid "" +"If you have not created any security groups, you can assign only the default" +" security group to the instance." +msgstr "" + +#: ./doc/user-guide/section_dashboard_launch_instances_from_image.xml101(guilabel) +#: ./doc/user-guide/section_dashboard_launch_instances_from_image.xml105(guilabel) +msgid "Volume Options" +msgstr "" + +#: ./doc/user-guide/section_dashboard_launch_instances_from_image.xml107(para) +msgid "Not applicable when you launch an instance from an image." +msgstr "" + +#: ./doc/user-guide/section_dashboard_launch_instances_from_image.xml108(para) +msgid "" +"To launch from a volume or volume snapshot, select the appropriate option in" +" the Volume Options drop-down list. Then, choose the " +"volume or snapshot." +msgstr "" + +#: ./doc/user-guide/section_dashboard_launch_instances_from_image.xml115(para) +msgid "" +"For information about how to create a bootable volume, see ." +msgstr "" + +#: ./doc/user-guide/section_dashboard_launch_instances_from_image.xml122(guilabel) +msgid "Post-Creation" +msgstr "" + +#: ./doc/user-guide/section_dashboard_launch_instances_from_image.xml126(guilabel) +msgid "Customization Script" +msgstr "" + +#: ./doc/user-guide/section_dashboard_launch_instances_from_image.xml128(para) +msgid "A customization script that runs after your instance launches." +msgstr "" + +#: ./doc/user-guide/section_dashboard_launch_instances_from_image.xml136(para) +msgid "" +"Click Launch. The instance starts on a Compute node " +"in the cloud." +msgstr "" + +#: ./doc/user-guide/section_dashboard_launch_instances_from_image.xml140(para) +msgid "" +"The Instances category shows the instance name, its " +"private and public IP addresses, size, status, task, and power state." +msgstr "" + +#: ./doc/user-guide/section_dashboard_launch_instances_from_image.xml145(para) +msgid "" +"If you did not provide a keypair, security groups, or rules so far, users " +"can only access the instance from inside the cloud through VNC. Even pinging" +" the instance is not possible. To access the instance through a VNC console," +" see ." +msgstr "" + +#: ./doc/user-guide/bk-user-guide.xml12(title) +msgid "OpenStack End User Guide" +msgstr "" + +#: ./doc/user-guide/bk-user-guide.xml13(titleabbrev) +msgid "End User Guide" +msgstr "" + +#: ./doc/user-guide/bk-user-guide.xml21(orgname) +#: ./doc/user-guide/bk-user-guide.xml26(holder) +msgid "OpenStack Foundation" +msgstr "" + +#: ./doc/user-guide/bk-user-guide.xml25(year) +msgid "2013" +msgstr "" + +#: ./doc/user-guide/bk-user-guide.xml28(releaseinfo) +msgid "havana" +msgstr "" + +#: ./doc/user-guide/bk-user-guide.xml29(productname) +msgid "OpenStack" +msgstr "" + +#: ./doc/user-guide/bk-user-guide.xml33(remark) +msgid "Copyright details are filled in by the template." +msgstr "" + +#: ./doc/user-guide/bk-user-guide.xml38(para) +msgid "" +"OpenStack is an open source cloud computing platform for public and private " +"clouds. A series of interrelated projects deliver a cloud infrastructure " +"solution. This guide shows OpenStack end users how to create and manage " +"resources in an OpenStack cloud with the OpenStack dashboard and OpenStack " +"client commands." +msgstr "" + +#: ./doc/user-guide/bk-user-guide.xml48(date) +msgid "2013-12-30" +msgstr "" + +#: ./doc/user-guide/bk-user-guide.xml52(para) +msgid "Added the OpenStack Python SDK chapter." +msgstr "" + +#: ./doc/user-guide/bk-user-guide.xml59(date) +msgid "2013-10-17" +msgstr "" + +#: ./doc/user-guide/bk-user-guide.xml63(para) +msgid "Havana release." +msgstr "" + +#: ./doc/user-guide/bk-user-guide.xml69(date) +msgid "2013-08-19" +msgstr "" + +#: ./doc/user-guide/bk-user-guide.xml73(para) +msgid "Editorial changes." +msgstr "" + +#: ./doc/user-guide/bk-user-guide.xml79(date) +msgid "2013-07-29" +msgstr "" + +#: ./doc/user-guide/bk-user-guide.xml83(para) +msgid "First edition of this document." +msgstr "" + +#: ./doc/user-guide/ch_dashboard.xml10(title) +msgid "OpenStack dashboard" +msgstr "" + +#: ./doc/user-guide/ch_dashboard.xml12(para) +msgid "" +"As a cloud end user, you can use the OpenStack dashboard to provision your " +"own resources within the limits set by administrators. You can modify these " +"examples to create other types and sizes of server instances." +msgstr "" + +#: ./doc/user-guide/section_cli_nova_configure_instances.xml19(para) +msgid "" +"When you launch a virtual machine, you can inject a keypair, which provides SSH access to your " +"instance. For this to work, the image must contain the cloud-" +"init package. Create at least one keypair for each project. If you" +" generate a keypair with an external tool, you can import it into OpenStack." +" You can use the keypair for multiple instances that belong to that project." +" In case an image uses a static root password or a static key set – neither " +"is recommended – you must not provide a keypair when you launch the " +"instance." +msgstr "" + +#: ./doc/user-guide/section_cli_nova_configure_instances.xml29(para) +msgid "" +"A security group is a named collection " +"of network access rules that you use to limit the types of traffic that have" +" access to instances. When you launch an instance, you can assign one or " +"more security groups to it. If you do not create security groups, new " +"instances are automatically assigned to the default security group, unless " +"you explicitly specify a different security group. The associated rules in each security group control the traffic " +"to instances in the group. Any incoming traffic that is not matched by a " +"rule is denied access by default. You can add rules to or remove rules from " +"a security group. You can modify rules for the default and any other " +"security group." +msgstr "" + +#: ./doc/user-guide/section_cli_nova_configure_instances.xml42(para) +msgid "" +"You must modify the rules for the default security group because users " +"cannot access instances that use the default group from any IP address " +"outside the cloud." +msgstr "" + +#: ./doc/user-guide/section_cli_nova_configure_instances.xml45(para) +msgid "" +"You can modify the rules in a security group to allow access to instances " +"through different ports and protocols. For example, you can modify rules to " +"allow access to instances through SSH, to ping them, or to allow UDP traffic" +" – for example, for a DNS server running on an instance. You specify the " +"following parameters for rules:" +msgstr "" + +#: ./doc/user-guide/section_cli_nova_configure_instances.xml53(para) +msgid "" +"Source of traffic. Enable traffic to " +"instances from either IP addresses inside the cloud from other group members" +" or from all IP addresses." +msgstr "" + +#: ./doc/user-guide/section_cli_nova_configure_instances.xml59(para) +msgid "" +"Protocol. Choose TCP for SSH, ICMP for " +"pings, or UDP." +msgstr "" + +#: ./doc/user-guide/section_cli_nova_configure_instances.xml63(para) +msgid "" +"Destination port on virtual machine. " +"Defines a port range. To open a single port only, enter the same value " +"twice. ICMP does not support ports: Enter values to define the codes and " +"types of ICMP traffic to be allowed." +msgstr "" + +#: ./doc/user-guide/section_cli_nova_configure_instances.xml70(para) +msgid "Rules are automatically enforced as soon as you create or modify them." +msgstr "" + +#: ./doc/user-guide/section_cli_nova_configure_instances.xml72(para) +msgid "" +"You can also assign a floating IP address to a running instance to make it " +"accessible from outside the cloud. You assign a floating IP address to an " +"instance and attach a block storage device, or volume, for persistent " +"storage. See ." +msgstr "" + +#: ./doc/user-guide/section_cli_nova_configure_instances.xml81(para) +msgid "You can generate a keypair or upload an existing public key." +msgstr "" + +#: ./doc/user-guide/section_cli_nova_configure_instances.xml84(para) +msgid "To generate a keypair, run the following command:" +msgstr "" + +#: ./doc/user-guide/section_cli_nova_configure_instances.xml86(replaceable) +#: ./doc/user-guide/section_cli_nova_configure_instances.xml115(replaceable) +msgid "KEY_NAME" +msgstr "" + +#: ./doc/user-guide/section_cli_nova_configure_instances.xml86(replaceable) +#: ./doc/user-guide/section_cli_nova_configure_instances.xml98(replaceable) +msgid "MY_KEY" +msgstr "" + +#: ./doc/user-guide/section_cli_nova_configure_instances.xml87(para) +msgid "" +"The command generates a keypair named KEY_NAME, " +"writes the private key to the " +"MY_KEY.pem file, and " +"registers the public key at the Nova database." +msgstr "" + +#: ./doc/user-guide/section_cli_nova_configure_instances.xml95(para) +msgid "" +"To set the permissions of the " +"MY_KEY.pem file, run the " +"following command:" +msgstr "" + +#: ./doc/user-guide/section_cli_nova_configure_instances.xml99(para) +msgid "" +"The command changes the permissions of the " +"MY_KEY.pem file so that only" +" you can read and write to it." +msgstr "" + +#: ./doc/user-guide/section_cli_nova_configure_instances.xml110(para) +msgid "" +"If you have already generated a keypair with the public key located at " +"~/.ssh/id_rsa.pub, run the following command to upload " +"the public key:" +msgstr "" + +#: ./doc/user-guide/section_cli_nova_configure_instances.xml116(para) +msgid "" +"The command registers the public key at the Nova database and names the " +"keypair KEY_NAME." +msgstr "" + +#: ./doc/user-guide/section_cli_nova_configure_instances.xml121(para) +msgid "" +"List keypairs to make sure that the uploaded keypair appears in the list:" +msgstr "" + +#: ./doc/user-guide/section_cli_nova_configure_instances.xml131(para) +msgid "" +"To list security groups for the current project, including descriptions, " +"enter the following command:" +msgstr "" + +#: ./doc/user-guide/section_cli_nova_configure_instances.xml137(para) +msgid "" +"To create a security group with a specified name and description, enter the " +"following command:" +msgstr "" + +#: ./doc/user-guide/section_cli_nova_configure_instances.xml140(replaceable) +#: ./doc/user-guide/section_cli_nova_configure_instances.xml145(replaceable) +#: ./doc/user-guide/section_cli_nova_configure_instances.xml166(replaceable) +#: ./doc/user-guide/section_cli_nova_configure_instances.xml178(replaceable) +#: ./doc/user-guide/section_cli_nova_configure_instances.xml188(replaceable) +#: ./doc/user-guide/section_cli_nova_configure_instances.xml205(replaceable) +#: ./doc/user-guide/section_cli_nova_configure_instances.xml214(replaceable) +#: ./doc/user-guide/section_cli_nova_configure_instances.xml234(replaceable) +#: ./doc/user-guide/section_cli_nova_configure_instances.xml244(replaceable) +#: ./doc/user-guide/section_cli_nova_configure_instances.xml249(replaceable) +msgid "SEC_GROUP_NAME" +msgstr "" + +#: ./doc/user-guide/section_cli_nova_configure_instances.xml140(replaceable) +msgid "GROUP_DESCRIPTION" +msgstr "" + +#: ./doc/user-guide/section_cli_nova_configure_instances.xml143(para) +msgid "To delete a specified group, enter the following command:" +msgstr "" + +#: ./doc/user-guide/section_cli_nova_configure_instances.xml147(para) +msgid "" +"You cannot delete the default security group for a project. Also, you cannot" +" delete a security group that is assigned to a running instance." +msgstr "" + +#: ./doc/user-guide/section_cli_nova_configure_instances.xml158(para) +msgid "Modify security group rules with the commands." +msgstr "" + +#: ./doc/user-guide/section_cli_nova_configure_instances.xml161(para) +msgid "" +"On a shell, source the OpenStack RC file. For details, see ." +msgstr "" + +#: ./doc/user-guide/section_cli_nova_configure_instances.xml165(para) +msgid "To list the rules for a security group" +msgstr "" + +#: ./doc/user-guide/section_cli_nova_configure_instances.xml169(para) +msgid "" +"To allow SSH access to the instances, choose one of the following sub-steps:" +msgstr "" + +#: ./doc/user-guide/section_cli_nova_configure_instances.xml173(title) +msgid "Add rule for all IPs" +msgstr "" + +#: ./doc/user-guide/section_cli_nova_configure_instances.xml175(para) +msgid "" +"Either from all IP addresses (specified as IP subnet in CIDR notation as " +"0.0.0.0/0):" +msgstr "" + +#: ./doc/user-guide/section_cli_nova_configure_instances.xml181(title) +msgid "Add rule for security groups" +msgstr "" + +#: ./doc/user-guide/section_cli_nova_configure_instances.xml183(para) +msgid "" +"Alternatively, you can allow only IP addresses from other security groups " +"(source groups) to access the specified port:" +msgstr "" + +#: ./doc/user-guide/section_cli_nova_configure_instances.xml188(replaceable) +#: ./doc/user-guide/section_cli_nova_configure_instances.xml214(replaceable) +#: ./doc/user-guide/section_cli_nova_configure_instances.xml234(replaceable) +#: ./doc/user-guide/section_cli_nova_configure_instances.xml249(replaceable) +msgid "SOURCE_GROUP_NAME" +msgstr "" + +#: ./doc/user-guide/section_cli_nova_configure_instances.xml193(para) +msgid "To allow pinging the instances, choose one of the following sub-steps:" +msgstr "" + +#: ./doc/user-guide/section_cli_nova_configure_instances.xml197(title) +msgid "To allow pinging from IPs" +msgstr "" + +#: ./doc/user-guide/section_cli_nova_configure_instances.xml199(para) +msgid "" +"Specify all IP addresses as IP subnet in CIDR notation: " +"0.0.0.0/0. This command allows access to all codes and " +"all types of ICMP traffic, respectively:" +msgstr "" + +#: ./doc/user-guide/section_cli_nova_configure_instances.xml208(title) +msgid "To allow pinging from other security groups" +msgstr "" + +#: ./doc/user-guide/section_cli_nova_configure_instances.xml210(para) +msgid "" +"To allow only members of other security groups (source groups) to ping " +"instances:" +msgstr "" + +#: ./doc/user-guide/section_cli_nova_configure_instances.xml219(para) +msgid "" +"To allow access through a UDP port, such as allowing access to a DNS server " +"that runs on a VM, complete one of the following sub-steps:" +msgstr "" + +#: ./doc/user-guide/section_cli_nova_configure_instances.xml224(para) +msgid "" +"To allow UDP access from IPs, specify all IP addresses as IP subnet in CIDR " +"notation: 0.0.0.0/0." +msgstr "" + +#: ./doc/user-guide/section_cli_nova_configure_instances.xml230(para) +msgid "" +"To allow only IP addresses from other security groups (source groups) to " +"access the specified port:" +msgstr "" + +#: ./doc/user-guide/section_cli_nova_configure_instances.xml239(para) +msgid "" +"To delete a security group rule, specify the same arguments that you used to" +" create the rule." +msgstr "" + +#: ./doc/user-guide/section_cli_nova_configure_instances.xml242(para) +msgid "" +"To delete the security rule that you created in :" +msgstr "" + +#: ./doc/user-guide/section_cli_nova_configure_instances.xml245(para) +msgid "" +"To delete the security rule that you created in :" +msgstr "" + +#. Put one translator per line, in the form of NAME , YEAR1, YEAR2 +#: ./doc/user-guide/section_cli_nova_configure_instances.xml0(None) +msgid "translator-credits" +msgstr "" diff --git a/doc/user-guide/locale/user-guide.pot b/doc/user-guide/locale/user-guide.pot new file mode 100644 index 0000000000..a3db3c5ad4 --- /dev/null +++ b/doc/user-guide/locale/user-guide.pot @@ -0,0 +1,2050 @@ +msgid "" +msgstr "" +"Project-Id-Version: PACKAGE VERSION\n" +"POT-Creation-Date: 2014-01-30 06:24+0000\n" +"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n" +"Last-Translator: FULL NAME \n" +"Language-Team: LANGUAGE \n" +"MIME-Version: 1.0\n" +"Content-Type: text/plain; charset=UTF-8\n" +"Content-Transfer-Encoding: 8bit\n" + +#: ./doc/user-guide/section_dashboard_create_networks.xml:12(title) +msgid "Create a network" +msgstr "" + +#: ./doc/user-guide/section_dashboard_create_networks.xml:16(para) +msgid "Log in to the dashboard, choose a project, and click the Networks category." +msgstr "" + +#: ./doc/user-guide/section_dashboard_create_networks.xml:21(para) +msgid "Click Create Network." +msgstr "" + +#: ./doc/user-guide/section_dashboard_create_networks.xml:24(para) +msgid "In the Create Network window, specify the following values." +msgstr "" + +#: ./doc/user-guide/section_dashboard_create_networks.xml:32(guilabel) +msgid "Network" +msgstr "" + +#: ./doc/user-guide/section_dashboard_create_networks.xml:32(th) ./doc/user-guide/section_dashboard_create_networks.xml:44(th) ./doc/user-guide/section_dashboard_create_networks.xml:87(th) ./doc/user-guide/section_dashboard_launch_instances_from_image.xml:39(th) ./doc/user-guide/section_dashboard_launch_instances_from_image.xml:69(th) ./doc/user-guide/section_dashboard_launch_instances_from_image.xml:101(th) ./doc/user-guide/section_dashboard_launch_instances_from_image.xml:122(th) +msgid " tab" +msgstr "" + +#: ./doc/user-guide/section_dashboard_create_networks.xml:37(guilabel) +msgid "Network Name" +msgstr "" + +#: ./doc/user-guide/section_dashboard_create_networks.xml:39(para) +msgid "A name to identify the network." +msgstr "" + +#: ./doc/user-guide/section_dashboard_create_networks.xml:44(guilabel) +msgid "Subnet" +msgstr "" + +#: ./doc/user-guide/section_dashboard_create_networks.xml:47(guilabel) +msgid "Create Subnet" +msgstr "" + +#: ./doc/user-guide/section_dashboard_create_networks.xml:49(para) +msgid "Check this option to create a subnet" +msgstr "" + +#: ./doc/user-guide/section_dashboard_create_networks.xml:51(para) +msgid "You do not have to initially specify a subnet (although this will result in the status of 'error' for any attached instance)." +msgstr "" + +#: ./doc/user-guide/section_dashboard_create_networks.xml:57(guilabel) +msgid "Subnet Name" +msgstr "" + +#: ./doc/user-guide/section_dashboard_create_networks.xml:59(para) +msgid "Name for the subnet." +msgstr "" + +#: ./doc/user-guide/section_dashboard_create_networks.xml:62(guilabel) +msgid "Network Address" +msgstr "" + +#: ./doc/user-guide/section_dashboard_create_networks.xml:64(para) +msgid "IP address for the subnet." +msgstr "" + +#: ./doc/user-guide/section_dashboard_create_networks.xml:68(guilabel) +msgid "IP Version" +msgstr "" + +#: ./doc/user-guide/section_dashboard_create_networks.xml:70(para) +msgid "IPv4 or IPv6." +msgstr "" + +#: ./doc/user-guide/section_dashboard_create_networks.xml:73(guilabel) +msgid "Gateway IP" +msgstr "" + +#: ./doc/user-guide/section_dashboard_create_networks.xml:75(para) +msgid "IP address for a specific gateway. This parameter is optional." +msgstr "" + +#: ./doc/user-guide/section_dashboard_create_networks.xml:80(guilabel) +msgid "Disable Gateway" +msgstr "" + +#: ./doc/user-guide/section_dashboard_create_networks.xml:82(para) +msgid "Check this option to disable gateway IP address." +msgstr "" + +#: ./doc/user-guide/section_dashboard_create_networks.xml:87(guilabel) +msgid "Subnet Detail" +msgstr "" + +#: ./doc/user-guide/section_dashboard_create_networks.xml:91(guilabel) +msgid "Enable DHCP" +msgstr "" + +#: ./doc/user-guide/section_dashboard_create_networks.xml:93(para) +msgid "Check this option to enable DHCP" +msgstr "" + +#: ./doc/user-guide/section_dashboard_create_networks.xml:97(guilabel) +msgid "Allocation Pools" +msgstr "" + +#: ./doc/user-guide/section_dashboard_create_networks.xml:99(para) +msgid "You can allocate IP address pools." +msgstr "" + +#: ./doc/user-guide/section_dashboard_create_networks.xml:103(guilabel) +msgid "DNS Name Servers" +msgstr "" + +#: ./doc/user-guide/section_dashboard_create_networks.xml:105(para) +msgid "You can allocate a name for the DNS server." +msgstr "" + +#: ./doc/user-guide/section_dashboard_create_networks.xml:109(guilabel) +msgid "Host Routes" +msgstr "" + +#: ./doc/user-guide/section_dashboard_create_networks.xml:111(para) +msgid "Include IP address of host routes." +msgstr "" + +#: ./doc/user-guide/section_dashboard_create_networks.xml:118(para) +msgid "Click Create to create a network." +msgstr "" + +#: ./doc/user-guide/section_dashboard_create_networks.xml:122(para) +msgid "The dashboard shows the network in the Networks category." +msgstr "" + +#: ./doc/user-guide/section_dashboard_manage_volumes.xml:13(title) +msgid "Manage volumes" +msgstr "" + +#: ./doc/user-guide/section_dashboard_manage_volumes.xml:15(para) +msgid "Volumes are block storage devices that you attach to instances to enable persistent storage. You can attach a volume to a running instance or detach a volume and attach it to another instance at any time. You can also create a snapshot from or delete a volume. Only administrative users can create volume types." +msgstr "" + +#: ./doc/user-guide/section_dashboard_manage_volumes.xml:22(title) +msgid "Create a volume" +msgstr "" + +#: ./doc/user-guide/section_dashboard_manage_volumes.xml:26(para) ./doc/user-guide/section_dashboard_manage_volumes.xml:54(para) ./doc/user-guide/section_dashboard_manage_volumes.xml:99(para) ./doc/user-guide/section_dashboard_manage_volumes.xml:150(para) +msgid "Log in to the dashboard, choose a project, and click the Volumes category." +msgstr "" + +#: ./doc/user-guide/section_dashboard_manage_volumes.xml:31(para) +msgid "Click Create Volume." +msgstr "" + +#: ./doc/user-guide/section_dashboard_manage_volumes.xml:33(para) +msgid "In the window that opens, enter a name, an optional description, and the size in GBs for the volume." +msgstr "" + +#: ./doc/user-guide/section_dashboard_manage_volumes.xml:38(para) +msgid "Click Create Volume to confirm your changes." +msgstr "" + +#: ./doc/user-guide/section_dashboard_manage_volumes.xml:42(para) +msgid "The dashboard shows the volume in the Volumes category." +msgstr "" + +#: ./doc/user-guide/section_dashboard_manage_volumes.xml:48(title) +msgid "Attach volumes to instances" +msgstr "" + +#: ./doc/user-guide/section_dashboard_manage_volumes.xml:49(para) +msgid "After you create one or more volumes, you can attach them to instances." +msgstr "" + +#: ./doc/user-guide/section_dashboard_manage_volumes.xml:59(para) +msgid "Select the volume to add to an instance and click Edit Attachments." +msgstr "" + +#: ./doc/user-guide/section_dashboard_manage_volumes.xml:63(para) +msgid "In the Manage Volume Attachments window, select an instance." +msgstr "" + +#: ./doc/user-guide/section_dashboard_manage_volumes.xml:68(para) +msgid "Enter the name of the device from where the volume should be accessible on the virtual machine." +msgstr "" + +#: ./doc/user-guide/section_dashboard_manage_volumes.xml:72(para) +msgid "The actual device name might differ due to hypervisor settings." +msgstr "" + +#: ./doc/user-guide/section_dashboard_manage_volumes.xml:77(para) +msgid "Click Attach Volume to confirm your changes. The dashboard shows the instance to which the volume is now attached and the device name. You can attach a volume to one instance at a time." +msgstr "" + +#: ./doc/user-guide/section_dashboard_manage_volumes.xml:84(para) +msgid "View the status of a volume in the Instances & Volumes category of the dashboard. The volume is either available or In-Use." +msgstr "" + +#: ./doc/user-guide/section_dashboard_manage_volumes.xml:90(para) +msgid "Now you can log in to the instance and mount, format, and use the disk." +msgstr "" + +#: ./doc/user-guide/section_dashboard_manage_volumes.xml:96(title) +msgid "Detach a volume from an instance" +msgstr "" + +#: ./doc/user-guide/section_dashboard_manage_volumes.xml:104(para) +msgid "Select the volume and click Edit Attachments." +msgstr "" + +#: ./doc/user-guide/section_dashboard_manage_volumes.xml:108(para) +msgid "Click Detach Volume and confirm your changes." +msgstr "" + +#: ./doc/user-guide/section_dashboard_manage_volumes.xml:112(para) ./doc/user-guide/section_dashboard_manage_volumes.xml:164(para) +msgid "A message indicates whether the action was successful." +msgstr "" + +#: ./doc/user-guide/section_dashboard_manage_volumes.xml:118(title) +msgid "Create volume snapshots" +msgstr "" + +#: ./doc/user-guide/section_dashboard_manage_volumes.xml:121(para) +msgid "Log in to the dashboard, choose a project, and click the Instances & Volumes category." +msgstr "" + +#: ./doc/user-guide/section_dashboard_manage_volumes.xml:126(para) +msgid "Select a volume from which to create a snapshot." +msgstr "" + +#: ./doc/user-guide/section_dashboard_manage_volumes.xml:129(para) +msgid "From the Actions drop-down list, select Create Snapshot." +msgstr "" + +#: ./doc/user-guide/section_dashboard_manage_volumes.xml:133(para) +msgid "In the window that opens, enter a snapshot name and a description." +msgstr "" + +#: ./doc/user-guide/section_dashboard_manage_volumes.xml:137(para) +msgid "Confirm your changes." +msgstr "" + +#: ./doc/user-guide/section_dashboard_manage_volumes.xml:138(para) +msgid "The dashboard shows the new volume snapshot in the Images & Snapshots category." +msgstr "" + +#: ./doc/user-guide/section_dashboard_manage_volumes.xml:145(title) +msgid "Delete volumes" +msgstr "" + +#: ./doc/user-guide/section_dashboard_manage_volumes.xml:146(para) +msgid "When you delete an instance, the data of its attached volumes is not destroyed." +msgstr "" + +#: ./doc/user-guide/section_dashboard_manage_volumes.xml:155(para) +msgid "Activate the check boxes in front of the volumes that you want to delete." +msgstr "" + +#: ./doc/user-guide/section_dashboard_manage_volumes.xml:159(para) +msgid "Click Delete Volumes and confirm your choice in the pop-up that appears." +msgstr "" + +#: ./doc/user-guide/section_sdk_manage_images.xml:7(title) +msgid "Manage images" +msgstr "" + +#: ./doc/user-guide/section_sdk_manage_images.xml:9(title) +msgid "List images" +msgstr "" + +#: ./doc/user-guide/section_sdk_manage_images.xml:10(para) +msgid "To list the available images, call the glanceclient.v2.images.Controller.list method:" +msgstr "" + +#: ./doc/user-guide/section_sdk_manage_images.xml:16(para) +msgid "The images method returns a Python generator, as shown in the following interaction with the Python interpreter:" +msgstr "" + +#: ./doc/user-guide/section_sdk_manage_images.xml:76(title) +msgid "Get image by ID" +msgstr "" + +#: ./doc/user-guide/section_sdk_manage_images.xml:77(para) +msgid "To retrieve an image object from its ID, call the glanceclient.v2.images.Controller.get method:" +msgstr "" + +#: ./doc/user-guide/section_sdk_manage_images.xml:87(title) +msgid "Get image by name" +msgstr "" + +#: ./doc/user-guide/section_sdk_manage_images.xml:88(para) +msgid "The Image Service Python bindings do not support the retrieval of an image object by name. However, the Compute Python bindings enable you to get an image object by name. To get an image object by name, call the novaclient.v1_1.images.ImageManager.find method:" +msgstr "" + +#: ./doc/user-guide/section_sdk_manage_images.xml:100(title) +msgid "Upload an image" +msgstr "" + +#: ./doc/user-guide/section_sdk_manage_images.xml:101(para) +msgid "To upload an image, call the glanceclient.v2.images.ImageManager.create method:" +msgstr "" + +#: ./doc/user-guide/section_cli_heat.xml:9(title) +msgid "Create and manage stacks" +msgstr "" + +#: ./doc/user-guide/section_cli_heat.xml:11(title) +msgid "Create a stack from an example template file" +msgstr "" + +#: ./doc/user-guide/section_cli_heat.xml:14(para) +msgid "To create a stack, or template, from an example template file, run the following command:" +msgstr "" + +#: ./doc/user-guide/section_cli_heat.xml:18(replaceable) ./doc/user-guide/section_cli_heat.xml:39(replaceable) +msgid "PATH_TO_HEAT_TEMPLATES" +msgstr "" + +#: ./doc/user-guide/section_cli_heat.xml:19(replaceable) +msgid "USERNAME" +msgstr "" + +#: ./doc/user-guide/section_cli_heat.xml:19(replaceable) +msgid "PASSWORD" +msgstr "" + +#: ./doc/user-guide/section_cli_heat.xml:19(replaceable) +msgid "HEAT_KEY" +msgstr "" + +#: ./doc/user-guide/section_cli_heat.xml:20(para) +msgid "The --parameters values that you specify depend on the parameters that are defined in the template. If a website hosts the template file, you can specify the URL with the --template-url parameter instead of the --template-file parameter." +msgstr "" + +#: ./doc/user-guide/section_cli_heat.xml:26(para) +msgid "The command returns the following output:" +msgstr "" + +#: ./doc/user-guide/section_cli_heat.xml:34(para) +msgid "You can also use the command to validate a template file without creating a stack from it." +msgstr "" + +#: ./doc/user-guide/section_cli_heat.xml:38(para) +msgid "To do so, run the following command:" +msgstr "" + +#: ./doc/user-guide/section_cli_heat.xml:40(para) +msgid "If validation fails, the response returns an error message." +msgstr "" + +#: ./doc/user-guide/section_cli_heat.xml:46(title) +msgid "Get information about stacks" +msgstr "" + +#: ./doc/user-guide/section_cli_heat.xml:47(para) +msgid "To explore the state and history of a particular stack, you can run a number of commands." +msgstr "" + +#: ./doc/user-guide/section_cli_heat.xml:51(para) +msgid "To see which stacks are visible to the current user, run the following command:" +msgstr "" + +#: ./doc/user-guide/section_cli_heat.xml:62(para) +msgid "To show the details of a stack, run the following command:" +msgstr "" + +#: ./doc/user-guide/section_cli_heat.xml:67(para) +msgid "A stack consists of a collection of resources." +msgstr "" + +#: ./doc/user-guide/section_cli_heat.xml:69(para) +msgid "To list the resources and their status, run the following command:" +msgstr "" + +#: ./doc/user-guide/section_cli_heat.xml:79(para) +msgid "To show the details for the specified resource in a stack, run the following command:" +msgstr "" + +#: ./doc/user-guide/section_cli_heat.xml:82(para) +msgid "Some resources have associated metadata which can change throughout the life-cycle of a resource:" +msgstr "" + +#: ./doc/user-guide/section_cli_heat.xml:88(para) +msgid "A series of events is generated during the life-cycle of a stack." +msgstr "" + +#: ./doc/user-guide/section_cli_heat.xml:90(para) +msgid "To display life-cycle events, run::" +msgstr "" + +#: ./doc/user-guide/section_cli_heat.xml:100(para) +msgid "To show the details for a particular event, run the following command:" +msgstr "" + +#: ./doc/user-guide/section_cli_heat.xml:107(title) +msgid "Update a stack" +msgstr "" + +#: ./doc/user-guide/section_cli_heat.xml:110(para) +msgid "To update an existing stack from a modified template file, run a command like the following command:" +msgstr "" + +#: ./doc/user-guide/section_cli_heat.xml:121(para) +msgid "Some resources are updated in-place, while others are replaced with new resources." +msgstr "" + +#: ./doc/user-guide/ch_sdk.xml:6(title) +msgid "OpenStack Python SDK" +msgstr "" + +#: ./doc/user-guide/ch_sdk.xml:8(para) +msgid "Use the OpenStack Python Software Development Kit (SDK) to write Python automation scripts that create and manage resources in your OpenStack cloud. The SDK implements Python bindings to the OpenStack API, which enables you to perform automation tasks in Python by making calls on Python objects rather than making REST calls directly. All OpenStack command-line tools are implemented using the Python SDK." +msgstr "" + +#: ./doc/user-guide/section_dashboard_access_and_security.xml:12(title) ./doc/user-guide/section_sdk_configure_instances.xml:6(title) ./doc/user-guide/section_cli_nova_configure_instances.xml:17(title) +msgid "Configure access and security for instances" +msgstr "" + +#: ./doc/user-guide/section_dashboard_access_and_security.xml:14(para) +msgid "Before you launch a virtual machine, you can add security group rules to enable users to ping and SSH to the instances. To do so, you either add rules to the default security group or add a security group with rules." +msgstr "" + +#: ./doc/user-guide/section_dashboard_access_and_security.xml:18(para) +msgid "Keypairs are SSH credentials that are injected into images when they are launched. For this to work, the image must contain the cloud-init package. Create at least one keypair for each project. For information, see ." +msgstr "" + +#: ./doc/user-guide/section_dashboard_access_and_security.xml:23(para) +msgid "If you have generated a keypair with an external tool, you can import it into OpenStack. The keypair can be used for multiple instances that belong to a project. For information, see ." +msgstr "" + +#: ./doc/user-guide/section_dashboard_access_and_security.xml:28(title) +msgid "Add rules to the default security group" +msgstr "" + +#: ./doc/user-guide/section_dashboard_access_and_security.xml:31(para) +msgid "Log in to the dashboard, choose a project, and click the Access & Security category. The dashboard shows the security groups that are available for this project." +msgstr "" + +#: ./doc/user-guide/section_dashboard_access_and_security.xml:37(para) +msgid "Select the default security group and click Edit Rules." +msgstr "" + +#: ./doc/user-guide/section_dashboard_access_and_security.xml:41(para) +msgid "To allow ssh access, click Add Rule." +msgstr "" + +#: ./doc/user-guide/section_dashboard_access_and_security.xml:45(para) ./doc/user-guide/section_dashboard_access_and_security.xml:88(para) +msgid "In the Add Rule window, enter the following values:" +msgstr "" + +#: ./doc/user-guide/section_dashboard_access_and_security.xml:52(guilabel) ./doc/user-guide/section_dashboard_access_and_security.xml:94(guilabel) +msgid "Rule" +msgstr "" + +#: ./doc/user-guide/section_dashboard_access_and_security.xml:54(literal) +msgid "SSH" +msgstr "" + +#: ./doc/user-guide/section_dashboard_access_and_security.xml:58(guilabel) ./doc/user-guide/section_dashboard_access_and_security.xml:102(guilabel) +msgid "Remote" +msgstr "" + +#: ./doc/user-guide/section_dashboard_access_and_security.xml:61(literal) ./doc/user-guide/section_dashboard_access_and_security.xml:65(guilabel) ./doc/user-guide/section_dashboard_access_and_security.xml:103(literal) ./doc/user-guide/section_dashboard_access_and_security.xml:106(guilabel) +msgid "CIDR" +msgstr "" + +#: ./doc/user-guide/section_dashboard_access_and_security.xml:67(literal) ./doc/user-guide/section_dashboard_access_and_security.xml:107(literal) +msgid "0.0.0.0/0" +msgstr "" + +#: ./doc/user-guide/section_dashboard_access_and_security.xml:73(para) +msgid "To accept requests from a particular range of IP addresses, specify the IP address block in the CIDR box." +msgstr "" + +#: ./doc/user-guide/section_dashboard_access_and_security.xml:79(para) ./doc/user-guide/section_dashboard_access_and_security.xml:112(para) +msgid "Click Add." +msgstr "" + +#: ./doc/user-guide/section_dashboard_access_and_security.xml:80(para) +msgid "The ssh port 22 is now open for requests from any IP address." +msgstr "" + +#: ./doc/user-guide/section_dashboard_access_and_security.xml:84(para) +msgid "To add an ICMP rule, click Add Rule." +msgstr "" + +#: ./doc/user-guide/section_dashboard_access_and_security.xml:95(literal) +msgid "All ICMP" +msgstr "" + +#: ./doc/user-guide/section_dashboard_access_and_security.xml:98(guilabel) +msgid "Direction" +msgstr "" + +#: ./doc/user-guide/section_dashboard_access_and_security.xml:99(literal) +msgid "Ingress" +msgstr "" + +#: ./doc/user-guide/section_dashboard_access_and_security.xml:117(title) ./doc/user-guide/section_sdk_configure_instances.xml:9(title) ./doc/user-guide/section_cli_nova_configure_instances.xml:79(title) +msgid "Add a keypair" +msgstr "" + +#: ./doc/user-guide/section_dashboard_access_and_security.xml:118(para) +msgid "Create at least one keypair for each project." +msgstr "" + +#: ./doc/user-guide/section_dashboard_access_and_security.xml:121(para) ./doc/user-guide/section_dashboard_access_and_security.xml:149(para) +msgid "Log in to the dashboard, choose a project, and click the Access & Security category." +msgstr "" + +#: ./doc/user-guide/section_dashboard_access_and_security.xml:126(para) ./doc/user-guide/section_dashboard_access_and_security.xml:154(para) +msgid "The Keypairs tab shows the keypairs that are available for this project." +msgstr "" + +#: ./doc/user-guide/section_dashboard_access_and_security.xml:131(para) +msgid "Click Create Keypair." +msgstr "" + +#: ./doc/user-guide/section_dashboard_access_and_security.xml:135(para) +msgid "In the Create Keypair window, enter a name for your keypair, and click Create Keypair." +msgstr "" + +#: ./doc/user-guide/section_dashboard_access_and_security.xml:140(para) +msgid "Respond to the prompt to download the keypair." +msgstr "" + +#: ./doc/user-guide/section_dashboard_access_and_security.xml:146(title) ./doc/user-guide/section_sdk_configure_instances.xml:50(title) ./doc/user-guide/section_cli_nova_configure_instances.xml:107(title) +msgid "Import a keypair" +msgstr "" + +#: ./doc/user-guide/section_dashboard_access_and_security.xml:159(para) +msgid "Click Import Keypair." +msgstr "" + +#: ./doc/user-guide/section_dashboard_access_and_security.xml:163(para) +msgid "In the Import Keypair window, enter the name of your keypair. In the Public Key box, copy the public key. Then, click Import Keypair." +msgstr "" + +#: ./doc/user-guide/section_dashboard_access_and_security.xml:170(para) +msgid "Save the *.pem file locally. To change its permissions so that only you can read and write to the file, run the following command:" +msgstr "" + +#: ./doc/user-guide/section_dashboard_access_and_security.xml:174(replaceable) ./doc/user-guide/section_dashboard_access_and_security.xml:189(replaceable) +msgid "MY_PRIV_KEY" +msgstr "" + +#: ./doc/user-guide/section_dashboard_access_and_security.xml:176(para) +msgid "If you are using the dashboard from a Windows-based computer, use puttygen to load the *.pem and convert and save as *.ppk. Refer to WinSCP information for more details." +msgstr "" + +#: ./doc/user-guide/section_dashboard_access_and_security.xml:187(para) +msgid "To make the keypair known to SSH, run the command:" +msgstr "" + +#: ./doc/user-guide/section_dashboard_access_and_security.xml:192(para) +msgid "The Compute database registers the public key of the keypair." +msgstr "" + +#: ./doc/user-guide/section_dashboard_access_and_security.xml:194(para) +msgid "The dashboard lists the keypair in the Access & Security category." +msgstr "" + +#: ./doc/user-guide/section_cli_swift_howto.xml:6(title) +msgid "Manage objects and containers" +msgstr "" + +#: ./doc/user-guide/section_cli_swift_howto.xml:7(para) +msgid "The OpenStack Object Storage Service provides the client, which is a command-line interface (CLI). Use this client to list objects and containers, upload objects to containers, and download or delete objects from containers. You can also gather statistics and update metadata for accounts, containers, and objects." +msgstr "" + +#: ./doc/user-guide/section_cli_swift_howto.xml:13(para) +msgid "This client is based on the native swift client library, client.py, which seamlessly re-authenticates if the current token expires during processing, retries operations multiple times, and provides a processing concurrency of 10." +msgstr "" + +#: ./doc/user-guide/section_cli_swift_howto.xml:18(para) +msgid "Users have roles on accounts. For example, a user with the admin role has full access to all containers and objects in an account. You can set access control lists (ACLs) at the container level and support lists for read and write access, which you set with the X-Container-Read and X-Container-Write header, respectively." +msgstr "" + +#: ./doc/user-guide/section_cli_swift_howto.xml:25(para) +msgid "To give a user read access, use the command with the -r parameter. To give a user write access, use the -w parameter." +msgstr "" + +#: ./doc/user-guide/section_cli_swift_howto.xml:29(para) +msgid "The following example enables the testuser user to read objects in the container:" +msgstr "" + +#: ./doc/user-guide/section_cli_swift_howto.xml:33(para) +msgid "You can also use this command with a list of users." +msgstr "" + +#: ./doc/user-guide/section_cli_swift_howto.xml:34(para) +msgid "If you use StaticWeb middleware to enable Object Storage to serve public web content, use .r:, followed by a list of allowed referrers." +msgstr "" + +#: ./doc/user-guide/section_cli_swift_howto.xml:37(para) +msgid "The following command gives object access to all referring domains:" +msgstr "" + +#: ./doc/user-guide/section_cli_nova_config-drive.xml:6(title) +msgid "Store metadata on a configuration drive" +msgstr "" + +#: ./doc/user-guide/section_cli_nova_config-drive.xml:7(para) +msgid "You can configure OpenStack to write metadata to a special configuration drive that attaches to the instance when it boots. The instance can mount this drive and read files from it to get information that is normally available through the metadata service." +msgstr "" + +#: ./doc/user-guide/section_cli_nova_config-drive.xml:14(para) +msgid "One use case for the configuration drive is to pass a networking configuration when you do not use DHCP to assign IP addresses to instances. For example, you might pass the IP configuration for the instance through the configuration drive, which the instance can mount and access before the you configure the network settings for the instance." +msgstr "" + +#: ./doc/user-guide/section_cli_nova_config-drive.xml:20(para) +msgid "Any modern guest operating system that is capable of mounting an ISO9660 or VFAT file system can use the configuration drive." +msgstr "" + +#: ./doc/user-guide/section_cli_nova_config-drive.xml:24(title) +msgid "Requirements and guidelines" +msgstr "" + +#: ./doc/user-guide/section_cli_nova_config-drive.xml:26(title) +msgid "Compute host requirements" +msgstr "" + +#: ./doc/user-guide/section_cli_nova_config-drive.xml:28(para) +msgid "The following hypervisors support the configuration drive: libvirt, xenserver, hyper-v, and vmware." +msgstr "" + +#: ./doc/user-guide/section_cli_nova_config-drive.xml:33(para) +msgid "To use configuration drive with libvirt, xenserver, or vmware, you must first install the genisoimage package on each Compute host. Otherwise, instances do not boot properly." +msgstr "" + +#: ./doc/user-guide/section_cli_nova_config-drive.xml:39(para) +msgid "Use the mkisofs_cmd flag to set the path where you install the genisoimage program. If genisoimage is in same path as the nova-compute service, you do not need to set this flag." +msgstr "" + +#: ./doc/user-guide/section_cli_nova_config-drive.xml:47(para) +msgid "By default, Ubuntu packages do not install this package. See bug #1165174." +msgstr "" + +#: ./doc/user-guide/section_cli_nova_config-drive.xml:54(para) +msgid "To use configuration drive with hyper-v, you must set the mkisofs_cmd value to the full path to an mkisofs.exe installation. Additionally, you must set the qemu_img_cmd value in the hyperv configuration section to the full path to an qemu-img command installation." +msgstr "" + +#: ./doc/user-guide/section_cli_nova_config-drive.xml:67(title) +msgid "Image requirements" +msgstr "" + +#: ./doc/user-guide/section_cli_nova_config-drive.xml:69(para) +msgid "An image built with a recent version of the cloud-init package can automatically access metadata passed through the configuration drive. The cloud-init package version 0.7.1 works with Ubuntu and Fedora-based images, such as RHEL." +msgstr "" + +#: ./doc/user-guide/section_cli_nova_config-drive.xml:78(para) +msgid "If an image does not have the cloud-init package installed, you must customize the image to run a script that mounts the configuration drive on boot, reads the data from the drive, and takes appropriate action such as adding the public key to an account. See for details on how data is organized on the configuration drive." +msgstr "" + +#: ./doc/user-guide/section_cli_nova_config-drive.xml:90(para) +msgid "If you use Xen with a configuration drive, use the xenapi_disable_agent configuration parameter to disable the agent." +msgstr "" + +#: ./doc/user-guide/section_cli_nova_config-drive.xml:97(title) +msgid "Guidelines" +msgstr "" + +#: ./doc/user-guide/section_cli_nova_config-drive.xml:99(para) +msgid "Do not rely on the presence of the EC2 metadata present in the configuration drive, as this content might be removed in a future release. For example, do not rely on files in the ec2 directory." +msgstr "" + +#: ./doc/user-guide/section_cli_nova_config-drive.xml:106(para) +msgid "When you create images that access configuration drive data and multiple directories are under the openstack directory, always select the highest API version by date that your consumer supports. For example, if your guest image supports the 2012-03-05, 2012-08-05, 2013-04-13 versions, try 2013-04-13 first and fall back to a previous version if 2013-04-13 is not present." +msgstr "" + +#: ./doc/user-guide/section_cli_nova_config-drive.xml:119(title) +msgid "Enable and access the configuration drive" +msgstr "" + +#: ./doc/user-guide/section_cli_nova_config-drive.xml:122(para) +msgid "To enable the configuration drive, pass the --config-drive=true parameter to the command." +msgstr "" + +#: ./doc/user-guide/section_cli_nova_config-drive.xml:126(para) +msgid "This example enables the configuration drive and passes user data, two files, and two key/value metadata pairs, all of which are accessible from the configuration drive:" +msgstr "" + +#: ./doc/user-guide/section_cli_nova_config-drive.xml:131(para) +msgid "You can also configure the Compute service to always create a configuration drive." +msgstr "" + +#: ./doc/user-guide/section_cli_nova_config-drive.xml:133(para) +msgid "Set this option in the /etc/nova/nova.conf file:" +msgstr "" + +#: ./doc/user-guide/section_cli_nova_config-drive.xml:138(para) +msgid "If a user passes the --config-drive=true flag to the command, an administrator cannot disable the configuration drive." +msgstr "" + +#: ./doc/user-guide/section_cli_nova_config-drive.xml:146(para) +msgid "The configuration drive has the config-2 volume label. If your guest operating system supports accessing disk by label, you can mount the configuration drive as the /dev/disk/by-label/config-2 device." +msgstr "" + +#: ./doc/user-guide/section_cli_nova_config-drive.xml:153(para) +msgid "For example:" +msgstr "" + +#: ./doc/user-guide/section_cli_nova_config-drive.xml:157(para) +msgid "Make sure that you use at least version 0.3.1 of CirrOS for configuration drive support." +msgstr "" + +#: ./doc/user-guide/section_cli_nova_config-drive.xml:160(para) +msgid "If your guest operating system does not use udev, the /dev/disk/by-label directory is not present." +msgstr "" + +#: ./doc/user-guide/section_cli_nova_config-drive.xml:164(para) +msgid "You can use the command to identify the block device that corresponds to the configuration drive. For example, when you boot the CirrOS image with the m1.tiny flavor, the device is /dev/vdb:" +msgstr "" + +#: ./doc/user-guide/section_cli_nova_config-drive.xml:172(para) +msgid "Once identified, you can mount the device:" +msgstr "" + +#: ./doc/user-guide/section_cli_nova_config-drive.xml:179(title) +msgid "Configuration drive contents" +msgstr "" + +#: ./doc/user-guide/section_cli_nova_config-drive.xml:180(para) +msgid "In this example, the contents of the configuration drive are:" +msgstr "" + +#: ./doc/user-guide/section_cli_nova_config-drive.xml:193(para) +msgid "The files that appear on the configuration drive depend on the arguments that you pass to the command." +msgstr "" + +#: ./doc/user-guide/section_cli_nova_config-drive.xml:198(title) +msgid "OpenStack metadata format" +msgstr "" + +#: ./doc/user-guide/section_cli_nova_config-drive.xml:199(para) +msgid "The following example shows the contents of the openstack/2012-08-10/meta_data.json and openstack/latest/meta_data.json files. These files are identical. The file contents are formatted for readability:" +msgstr "" + +#: ./doc/user-guide/section_cli_nova_config-drive.xml:206(para) +msgid "Note the effect of the --file /etc/network/interfaces=/home/myuser/instance-interfaces argument that was passed to the command. The contents of this file are contained in the openstack/content/0000 file on the configuration drive, and the path is specified as /etc/network/interfaces in the meta_data.json file." +msgstr "" + +#: ./doc/user-guide/section_cli_nova_config-drive.xml:217(title) +msgid "EC2 metadata format" +msgstr "" + +#: ./doc/user-guide/section_cli_nova_config-drive.xml:218(para) +msgid "The following example shows the contents of the ec2/2009-04-04/meta-data.json, latest/meta-data.json files. These files are identical. The file contents are formatted to improve readability:" +msgstr "" + +#: ./doc/user-guide/section_cli_nova_config-drive.xml:226(title) +msgid "User data" +msgstr "" + +#: ./doc/user-guide/section_cli_nova_config-drive.xml:227(para) +msgid "The openstack/2012-08-10/user_data, openstack/latest/user_data, ec2/2009-04-04/user-data, and ec2/latest/user-data file are present only if the --user-data flag and the contents of the user data file are passed to the command." +msgstr "" + +#: ./doc/user-guide/section_cli_nova_config-drive.xml:237(title) +msgid "Configuration drive format" +msgstr "" + +#: ./doc/user-guide/section_cli_nova_config-drive.xml:238(para) +msgid "The default format of the configuration drive as an ISO 9660 file system. To explicitly specify the ISO 9660 format, add the following line to the /etc/nova/nova.conf file:" +msgstr "" + +#: ./doc/user-guide/section_cli_nova_config-drive.xml:244(para) +msgid "By default, you cannot attach the configuration drive image as a CD drive instead of as a disk drive. To attach a CD drive, add this line to the /etc/nova/nova.conf file:" +msgstr "" + +#: ./doc/user-guide/section_cli_nova_config-drive.xml:250(para) +msgid "For legacy reasons, you can configure the configuration drive to use VFAT format instead of ISO 9660. It is unlikely that you would require VFAT format because ISO 9660 is widely supported across operating systems. However, to use the VFAT format, add the following line to the /etc/nova/nova.conf file:" +msgstr "" + +#: ./doc/user-guide/section_cli_nova_config-drive.xml:259(para) +msgid "If you choose VFAT, the configuration drive is 64 MBs." +msgstr "" + +#: ./doc/user-guide/section_cli_nova_config-drive.xml:264(title) +msgid "Configuration drive reference" +msgstr "" + +#: ./doc/user-guide/section_cli_nova_config-drive.xml:265(para) +msgid "The following table shows the configuration options for the configuration drive:" +msgstr "" + +#: ./doc/user-guide/section_sdk_install.xml:6(title) +msgid "Install the OpenStack SDK" +msgstr "" + +#: ./doc/user-guide/section_sdk_install.xml:7(para) +msgid "Each OpenStack project has its own Python library. These libraries are bundled with the command-line clients. For example, the Python bindings for the Compute API are bundled with the python-novaclient package." +msgstr "" + +#: ./doc/user-guide/section_sdk_install.xml:11(para) +msgid "For details about how to install the clients, see install the OpenStack command-line clients." +msgstr "" + +#: ./doc/user-guide/section_sdk_auth_neutron.xml:6(title) +msgid "Authenticate against a Networking endpoint" +msgstr "" + +#: ./doc/user-guide/section_sdk_auth_neutron.xml:7(para) +msgid "To authenticate against a Networking endpoint, instantiate a neutronclient.v_2_0.client.Client object:" +msgstr "" + +#: ./doc/user-guide/section_sdk_auth_neutron.xml:18(para) +msgid "You can also authenticate by explicitly specifying the endpoint and token:" +msgstr "" + +#: ./doc/user-guide/section_cli_ceilometer.xml:8(title) +msgid "Measure cloud resources" +msgstr "" + +#: ./doc/user-guide/section_cli_ceilometer.xml:9(para) +msgid "The OpenStack Telemetry service measures cloud resources in OpenStack." +msgstr "" + +#: ./doc/user-guide/section_cli_ceilometer.xml:11(para) +msgid "It collects information about how much, who, what, and when with regards to billing. Currently, metering is available through only the command-line client." +msgstr "" + +#: ./doc/user-guide/section_cli_ceilometer.xml:15(para) +msgid "To model data, the Telemetry service uses these abstractions:" +msgstr "" + +#: ./doc/user-guide/section_cli_ceilometer.xml:19(emphasis) +msgid "Meter" +msgstr "" + +#: ./doc/user-guide/section_cli_ceilometer.xml:21(para) +msgid "Measures a specific aspect of resource usage, such as the existence of a running instance, or ongoing performance, such as the CPU utilization for an instance. Meters exist for each type of resource. For example, a separate cpu_util meter exists for each instance. The life cycle of a meter is decoupled from the existence of its related resource. The meter persists after the resource goes away." +msgstr "" + +#: ./doc/user-guide/section_cli_ceilometer.xml:31(para) +msgid "A meter has the following attributes:" +msgstr "" + +#: ./doc/user-guide/section_cli_ceilometer.xml:34(para) +msgid "String name." +msgstr "" + +#: ./doc/user-guide/section_cli_ceilometer.xml:37(para) +msgid "A unit of measurement." +msgstr "" + +#: ./doc/user-guide/section_cli_ceilometer.xml:40(para) +msgid "A type. Indicates whether values increase monotonically (cumulative), are interpreted as a change from the previous value (delta), or are standalone and relate only to the current duration (gauge)." +msgstr "" + +#: ./doc/user-guide/section_cli_ceilometer.xml:51(emphasis) +msgid "Sample" +msgstr "" + +#: ./doc/user-guide/section_cli_ceilometer.xml:53(para) +msgid "An individual data point that is associated with a specific meter. Has the same attributes as the meter, with the addition of timestamp and value attributes. The value attribute is also known as the sample volume." +msgstr "" + +#: ./doc/user-guide/section_cli_ceilometer.xml:62(emphasis) +msgid "Statistic" +msgstr "" + +#: ./doc/user-guide/section_cli_ceilometer.xml:64(para) +msgid "A set of data point aggregates over a time duration. (In contrast, a sample represents a single data point.) The Telemetry service employs these aggregation functions:" +msgstr "" + +#: ./doc/user-guide/section_cli_ceilometer.xml:70(para) +msgid "count. The number of samples in each period." +msgstr "" + +#: ./doc/user-guide/section_cli_ceilometer.xml:75(para) +msgid "max. The maximum number of sample volumes in each period." +msgstr "" + +#: ./doc/user-guide/section_cli_ceilometer.xml:80(para) +msgid "min. The minimum number of sample volumes in each period." +msgstr "" + +#: ./doc/user-guide/section_cli_ceilometer.xml:85(para) +msgid "avg. The average of sample volumes over each period." +msgstr "" + +#: ./doc/user-guide/section_cli_ceilometer.xml:90(para) +msgid "sum. The sum of sample volumes over each period." +msgstr "" + +#: ./doc/user-guide/section_cli_ceilometer.xml:98(emphasis) +msgid "Alarm" +msgstr "" + +#: ./doc/user-guide/section_cli_ceilometer.xml:100(para) +msgid "A set of rules that define a monitor and a current state, with edge-triggered actions associated with target states. Provides user-oriented Monitoring-as-a-Service and a general purpose utility for Openstack. Orchestration auto scaling is a typical use-case. Alarms follow a tristate model of ok, alarm, and insufficient data. For conventional threshold-oriented alarms, a static threshold value and comparison operator govern state transitions. The comparison operator compares a selected meter statistic against an evaluation window of configurable length into the recent past." +msgstr "" + +#: ./doc/user-guide/section_cli_ceilometer.xml:119(para) +msgid "This example uses the client to create an auto-scaling stack and the client to measure resources." +msgstr "" + +#: ./doc/user-guide/section_cli_ceilometer.xml:125(para) +msgid "Create an auto-scaling stack:" +msgstr "" + +#: ./doc/user-guide/section_cli_ceilometer.xml:129(para) +msgid "List the heat resources that were created:" +msgstr "" + +#: ./doc/user-guide/section_cli_ceilometer.xml:146(para) +msgid "List the alarms that are set:" +msgstr "" + +#: ./doc/user-guide/section_cli_ceilometer.xml:156(para) +msgid "List the meters that are set:" +msgstr "" + +#: ./doc/user-guide/section_cli_ceilometer.xml:167(para) +msgid "List samples:" +msgstr "" + +#: ./doc/user-guide/section_cli_ceilometer.xml:176(para) +msgid "View statistics:" +msgstr "" + +#: ./doc/user-guide/section_cli_nova_floating_ips.xml:6(title) +msgid "Manage IP addresses" +msgstr "" + +#: ./doc/user-guide/section_cli_nova_floating_ips.xml:7(para) +msgid "Each instance can have a private, or fixed, IP address and a public, or floating, one." +msgstr "" + +#: ./doc/user-guide/section_cli_nova_floating_ips.xml:9(para) +msgid "Private IP addresses are used for communication between instances, and public ones are used for communication with the outside world." +msgstr "" + +#: ./doc/user-guide/section_cli_nova_floating_ips.xml:12(para) +msgid "When you launch an instance, it is automatically assigned a private IP address that stays the same until you explicitly terminate the instance. Rebooting an instance has no effect on the private IP address." +msgstr "" + +#: ./doc/user-guide/section_cli_nova_floating_ips.xml:16(para) +msgid "A pool of floating IPs, configured by the cloud operator, is available in OpenStack Compute." +msgstr "" + +#: ./doc/user-guide/section_cli_nova_floating_ips.xml:18(para) +msgid "You can allocate a certain number of these to a project: The maximum number of floating IP addresses per project is defined by the quota." +msgstr "" + +#: ./doc/user-guide/section_cli_nova_floating_ips.xml:21(para) +msgid "You can add a floating IP address from this set to an instance of the project. Floating IP addresses can be dynamically disassociated and associated with other instances of the same project at any time." +msgstr "" + +#: ./doc/user-guide/section_cli_nova_floating_ips.xml:25(para) +msgid "Before you can assign a floating IP address to an instance, you first must allocate floating IPs to a project. After floating IP addresses have been allocated to the current project, you can assign them to running instances." +msgstr "" + +#: ./doc/user-guide/section_cli_nova_floating_ips.xml:29(para) +msgid "You can assign a floating IP address to one instance at a time." +msgstr "" + +#: ./doc/user-guide/section_cli_nova_floating_ips.xml:32(title) +msgid "List floating IP address information" +msgstr "" + +#: ./doc/user-guide/section_cli_nova_floating_ips.xml:35(para) +msgid "To list all floating IP addresses:" +msgstr "" + +#: ./doc/user-guide/section_cli_nova_floating_ips.xml:63(para) +msgid "To list all pools that provide floating IP addresses:" +msgstr "" + +#: ./doc/user-guide/section_cli_nova_floating_ips.xml:76(title) +msgid "Assign floating IP addresses" +msgstr "" + +#: ./doc/user-guide/section_cli_nova_floating_ips.xml:77(para) +msgid "You can assign floating IP addresses to a project or an instance." +msgstr "" + +#: ./doc/user-guide/section_cli_nova_floating_ips.xml:81(para) +msgid "Allocate a floating IP address to the current project. If more than one IP address pool is available, you can specify the pool from which to allocate the IP address. This example specifies the public pool:" +msgstr "" + +#: ./doc/user-guide/section_cli_nova_floating_ips.xml:94(para) +msgid "To release a floating IP address from the current project:" +msgstr "" + +#: ./doc/user-guide/section_cli_nova_floating_ips.xml:96(replaceable) ./doc/user-guide/section_cli_nova_floating_ips.xml:108(replaceable) ./doc/user-guide/section_cli_nova_floating_ips.xml:118(replaceable) +msgid "FLOATING_IP" +msgstr "" + +#: ./doc/user-guide/section_cli_nova_floating_ips.xml:97(para) +msgid "The IP address is returned to the pool of IP addresses that are available for all projects. If an IP address is assigned to a running instance, it is disassociated from the instance." +msgstr "" + +#: ./doc/user-guide/section_cli_nova_floating_ips.xml:103(para) +msgid "To associate an IP address with an instance, at least one floating IP address must be allocated to the current project." +msgstr "" + +#: ./doc/user-guide/section_cli_nova_floating_ips.xml:106(para) +msgid "To assign a floating IP address to an instance:" +msgstr "" + +#: ./doc/user-guide/section_cli_nova_floating_ips.xml:108(replaceable) ./doc/user-guide/section_cli_nova_floating_ips.xml:118(replaceable) +msgid "INSTANCE_NAME_OR_ID" +msgstr "" + +#: ./doc/user-guide/section_cli_nova_floating_ips.xml:109(para) +msgid "After you assign the IP address and configure security group rules for the instance, the instance is publicly available at the floating IP address." +msgstr "" + +#: ./doc/user-guide/section_cli_nova_floating_ips.xml:115(para) +msgid "To remove a floating IP address from an instance, specify the same arguments that you used to assign the IP address:" +msgstr "" + +#: ./doc/user-guide/section_sdk_auth_glance.xml:6(title) +msgid "Authenticate against an Image Service endpoint" +msgstr "" + +#: ./doc/user-guide/section_sdk_auth_glance.xml:7(para) +msgid "To authenticate against an Image Service endpoint, instantiate a glanceclient.v2.client.Client object:" +msgstr "" + +#: ./doc/user-guide/section_dashboard_stacks.xml:12(title) +msgid "Launch and manage stacks" +msgstr "" + +#: ./doc/user-guide/section_dashboard_stacks.xml:13(para) +msgid "Heat is a service used to orchestrate multiple composite cloud applications using the AWS CloudFormation template format, through both an OpenStack-native ReST API and a CloudFormation-compatible Query API." +msgstr "" + +#: ./doc/user-guide/section_dashboard_stacks.xml:17(para) +msgid "The purpose of Heat is to provide a template based orchestration for describing a cloud application by executing appropriate OpenStack API calls to generate running cloud applications, integrate other core components of OpenStack into a one-file template system. The templates allow creation of most OpenStack resource types such as instances, floating ips, volumes, security groups, users, etc." +msgstr "" + +#: ./doc/user-guide/section_dashboard_stacks.xml:25(title) +msgid "Launch a stack" +msgstr "" + +#: ./doc/user-guide/section_dashboard_stacks.xml:28(para) +msgid "Log in to the dashboard, choose a project, and click Stacks in the Orchestration category." +msgstr "" + +#: ./doc/user-guide/section_dashboard_stacks.xml:34(para) +msgid "Click Launch Stack." +msgstr "" + +#: ./doc/user-guide/section_dashboard_stacks.xml:39(para) +msgid "In the Select Template window, choose a template source option, URL, File, or Direct Input, from the drop-down list." +msgstr "" + +#: ./doc/user-guide/section_dashboard_stacks.xml:47(para) +msgid "Enter the URL, browse to the file location, or directly include the template based on your previous selection." +msgstr "" + +#: ./doc/user-guide/section_dashboard_stacks.xml:52(para) +msgid "In the Launch Stack window, specify the following values." +msgstr "" + +#: ./doc/user-guide/section_dashboard_stacks.xml:59(guilabel) +msgid "Stack Name" +msgstr "" + +#: ./doc/user-guide/section_dashboard_stacks.xml:61(para) +msgid "A name to identify the stack." +msgstr "" + +#: ./doc/user-guide/section_dashboard_stacks.xml:65(guilabel) +msgid "Creation Timeout (minutes)" +msgstr "" + +#: ./doc/user-guide/section_dashboard_stacks.xml:67(para) +msgid "Creation Timeout in minutes." +msgstr "" + +#: ./doc/user-guide/section_dashboard_stacks.xml:71(guilabel) +msgid "Rollback On Failure" +msgstr "" + +#: ./doc/user-guide/section_dashboard_stacks.xml:73(para) +msgid "Check this option if you want Heat to rollback on failure." +msgstr "" + +#: ./doc/user-guide/section_dashboard_stacks.xml:78(guilabel) +msgid "Password for user \"demo\"" +msgstr "" + +#: ./doc/user-guide/section_dashboard_stacks.xml:80(para) +msgid "Password for the user logged in." +msgstr "" + +#: ./doc/user-guide/section_dashboard_stacks.xml:84(guilabel) +msgid "DBUsername" +msgstr "" + +#: ./doc/user-guide/section_dashboard_stacks.xml:85(para) +msgid "Database user name." +msgstr "" + +#: ./doc/user-guide/section_dashboard_stacks.xml:88(guilabel) +msgid "LinuxDistribution" +msgstr "" + +#: ./doc/user-guide/section_dashboard_stacks.xml:89(para) +msgid "Linux Distribution used in the stacks." +msgstr "" + +#: ./doc/user-guide/section_dashboard_stacks.xml:93(guilabel) +msgid "DBRootPassword" +msgstr "" + +#: ./doc/user-guide/section_dashboard_stacks.xml:94(para) +msgid "Database root password." +msgstr "" + +#: ./doc/user-guide/section_dashboard_stacks.xml:98(guilabel) +msgid "KeyName" +msgstr "" + +#: ./doc/user-guide/section_dashboard_stacks.xml:99(para) +msgid "Name of the keypair." +msgstr "" + +#: ./doc/user-guide/section_dashboard_stacks.xml:102(guilabel) +msgid "DBName" +msgstr "" + +#: ./doc/user-guide/section_dashboard_stacks.xml:103(para) +msgid "Database name." +msgstr "" + +#: ./doc/user-guide/section_dashboard_stacks.xml:106(guilabel) +msgid "DBPassword" +msgstr "" + +#: ./doc/user-guide/section_dashboard_stacks.xml:107(para) +msgid "Database password." +msgstr "" + +#: ./doc/user-guide/section_dashboard_stacks.xml:110(guilabel) +msgid "InstanceType" +msgstr "" + +#: ./doc/user-guide/section_dashboard_stacks.xml:111(para) +msgid "Flavor of the instance." +msgstr "" + +#: ./doc/user-guide/section_dashboard_stacks.xml:118(para) +msgid "Click Launch to create a stack." +msgstr "" + +#: ./doc/user-guide/section_dashboard_stacks.xml:122(para) +msgid "The dashboard shows the stack in the Stacks category." +msgstr "" + +#: ./doc/user-guide/section_dashboard_stacks.xml:126(para) +msgid "After the stack is created, click on the stack name to see these details:" +msgstr "" + +#: ./doc/user-guide/section_dashboard_stacks.xml:130(guilabel) +msgid "Topology" +msgstr "" + +#: ./doc/user-guide/section_dashboard_stacks.xml:132(para) +msgid "The topology of the stack created." +msgstr "" + +#: ./doc/user-guide/section_dashboard_stacks.xml:136(guilabel) +msgid "Overview" +msgstr "" + +#: ./doc/user-guide/section_dashboard_stacks.xml:138(para) +msgid "The parameters and details of the stack under the following headings: Info, Status, Outputs, Stack Parameters, and Launch Parameters." +msgstr "" + +#: ./doc/user-guide/section_dashboard_stacks.xml:149(guilabel) +msgid "Resources" +msgstr "" + +#: ./doc/user-guide/section_dashboard_stacks.xml:151(para) +msgid "The resources used by the stack." +msgstr "" + +#: ./doc/user-guide/section_dashboard_stacks.xml:155(guilabel) +msgid "Events" +msgstr "" + +#: ./doc/user-guide/section_dashboard_stacks.xml:157(para) +msgid "The events related to the stack." +msgstr "" + +#: ./doc/user-guide/section_dashboard_stacks.xml:163(title) +msgid "Delete stacks" +msgstr "" + +#: ./doc/user-guide/section_dashboard_stacks.xml:166(para) ./doc/user-guide/section_dashboard_manage_images.xml:29(para) ./doc/user-guide/section_dashboard_manage_images.xml:113(para) ./doc/user-guide/section_dashboard_manage_images.xml:144(para) +msgid "Log in to the dashboard." +msgstr "" + +#: ./doc/user-guide/section_dashboard_stacks.xml:169(para) +msgid "On the Project tab, click the Stacks category." +msgstr "" + +#: ./doc/user-guide/section_dashboard_stacks.xml:173(para) +msgid "Select the stack that you want to delete." +msgstr "" + +#: ./doc/user-guide/section_dashboard_stacks.xml:176(para) +msgid "Click Delete Stack." +msgstr "" + +#: ./doc/user-guide/section_dashboard_stacks.xml:180(para) +msgid "In the Confirm Delete Stack window, click Delete Stack to confirm the deletion. You cannot undo this action." +msgstr "" + +#: ./doc/user-guide/section_sdk_authenticate.xml:5(title) +msgid "Authentication" +msgstr "" + +#: ./doc/user-guide/section_sdk_authenticate.xml:6(para) +msgid "You must authenticate against an OpenStack endpoint before you can use OpenStack services. Each project uses a slightly different syntax for doing authentication." +msgstr "" + +#: ./doc/user-guide/section_sdk_authenticate.xml:9(para) +msgid "You must typically authenticate against a specific version of a service. For example, a client might need to authenticate against the Identity Service v2.0." +msgstr "" + +#: ./doc/user-guide/section_sdk_authenticate.xml:12(para) +msgid "Python scripts that use the OpenStack SDK must have access to the credentials contained in the OpenStack RC file. Because credentials are sensitive information, do not include them in your scripts. This guide assumes that users source the openrc.sh file and access the credentials by using the environment variables in the Python scripts." +msgstr "" + +#. When image changes, this message will be marked fuzzy or untranslated for you. +#. It doesn't matter what you translate it to: it's not used at all. +#: ./doc/user-guide/section_dashboard_manage_images.xml:48(None) +msgid "@@image: '../common/figures/user_image_create.png'; md5=9371228508180bf0cf3f8778ccf50d84" +msgstr "" + +#: ./doc/user-guide/section_dashboard_manage_images.xml:6(title) +msgid "Create and manage images" +msgstr "" + +#: ./doc/user-guide/section_dashboard_manage_images.xml:7(para) +msgid "The cloud operator assigns roles to users. Roles determine who can upload and manage images. The operator might restrict image upload and management to only cloud administrators or operators." +msgstr "" + +#: ./doc/user-guide/section_dashboard_manage_images.xml:11(para) +msgid "If you have admin privileges, you can use the dashboard to create and manage images in the admin project." +msgstr "" + +#: ./doc/user-guide/section_dashboard_manage_images.xml:15(title) +msgid "Manage images by using clients and APIs" +msgstr "" + +#: ./doc/user-guide/section_dashboard_manage_images.xml:16(para) +msgid "You can also use the and command-line clients or the Image Service and Compute APIs to manage images. See ." +msgstr "" + +#: ./doc/user-guide/section_dashboard_manage_images.xml:22(title) +msgid "Create images" +msgstr "" + +#: ./doc/user-guide/section_dashboard_manage_images.xml:23(para) +msgid "For details about image creation, see the Virtual Machine Image Guide." +msgstr "" + +#: ./doc/user-guide/section_dashboard_manage_images.xml:30(para) ./doc/user-guide/section_dashboard_manage_images.xml:114(para) ./doc/user-guide/section_dashboard_manage_images.xml:145(para) +msgid "Choose the admin project from the CURRENT PROJECT drop-down list." +msgstr "" + +#: ./doc/user-guide/section_dashboard_manage_images.xml:35(para) ./doc/user-guide/section_dashboard_manage_images.xml:119(para) ./doc/user-guide/section_dashboard_manage_images.xml:150(para) +msgid "On the Project tab, click the Images & Snapshots category." +msgstr "" + +#: ./doc/user-guide/section_dashboard_manage_images.xml:40(para) +msgid "Click Create Image. The Create An Image window appears:" +msgstr "" + +#: ./doc/user-guide/section_dashboard_manage_images.xml:54(para) +msgid "In the Create An Image window, enter or select the following values:" +msgstr "" + +#: ./doc/user-guide/section_dashboard_manage_images.xml:61(guilabel) +msgid "Name" +msgstr "" + +#: ./doc/user-guide/section_dashboard_manage_images.xml:62(para) +msgid "Enter a name for the image." +msgstr "" + +#: ./doc/user-guide/section_dashboard_manage_images.xml:65(guilabel) +msgid "Description" +msgstr "" + +#: ./doc/user-guide/section_dashboard_manage_images.xml:66(para) +msgid "Enter a brief description about the image." +msgstr "" + +#: ./doc/user-guide/section_dashboard_manage_images.xml:70(guilabel) +msgid "Image Location" +msgstr "" + +#: ./doc/user-guide/section_dashboard_manage_images.xml:72(para) +msgid "Include the URL of the image." +msgstr "" + +#: ./doc/user-guide/section_dashboard_manage_images.xml:75(guilabel) +msgid "Image File" +msgstr "" + +#: ./doc/user-guide/section_dashboard_manage_images.xml:76(para) +msgid "Alternatively, browse to find the file on your machine." +msgstr "" + +#: ./doc/user-guide/section_dashboard_manage_images.xml:80(guilabel) +msgid "Format" +msgstr "" + +#: ./doc/user-guide/section_dashboard_manage_images.xml:81(para) +msgid "Select the image format." +msgstr "" + +#: ./doc/user-guide/section_dashboard_manage_images.xml:84(para) +msgid "Minimum Disk (GB) and Maximum Disk (GB)" +msgstr "" + +#: ./doc/user-guide/section_dashboard_manage_images.xml:86(para) +msgid "Leave these fields empty." +msgstr "" + +#: ./doc/user-guide/section_dashboard_manage_images.xml:90(guilabel) +msgid "Public" +msgstr "" + +#: ./doc/user-guide/section_dashboard_manage_images.xml:91(para) +msgid "Select this option to make the image public to all users." +msgstr "" + +#: ./doc/user-guide/section_dashboard_manage_images.xml:95(guilabel) +msgid "Protected" +msgstr "" + +#: ./doc/user-guide/section_dashboard_manage_images.xml:96(para) +msgid "Select this option to ensure that only users with permissions can delete it." +msgstr "" + +#: ./doc/user-guide/section_dashboard_manage_images.xml:103(para) +msgid "Click Create Image." +msgstr "" + +#: ./doc/user-guide/section_dashboard_manage_images.xml:104(para) +msgid "The image is queued to be uploaded. It might take some time before the status changes from queued to active." +msgstr "" + +#: ./doc/user-guide/section_dashboard_manage_images.xml:110(title) +msgid "Update images" +msgstr "" + +#: ./doc/user-guide/section_dashboard_manage_images.xml:124(para) +msgid "Select the image that you want to edit. In the More drop-down list, click Edit." +msgstr "" + +#: ./doc/user-guide/section_dashboard_manage_images.xml:129(para) +msgid "In the Update Image window, you can change the name for the image. Select the Public check box to make the image public. Clear this check box to make the image private." +msgstr "" + +#: ./doc/user-guide/section_dashboard_manage_images.xml:136(para) +msgid "Click Update Image." +msgstr "" + +#: ./doc/user-guide/section_dashboard_manage_images.xml:141(title) +msgid "Delete images" +msgstr "" + +#: ./doc/user-guide/section_dashboard_manage_images.xml:155(para) +msgid "Select the images that you want to delete." +msgstr "" + +#: ./doc/user-guide/section_dashboard_manage_images.xml:158(para) +msgid "Click Delete Images." +msgstr "" + +#: ./doc/user-guide/section_dashboard_manage_images.xml:161(para) +msgid "In the Confirm Delete Image window, click Delete Images to confirm the deletion. You cannot undo this action." +msgstr "" + +#: ./doc/user-guide/ch_cli.xml:10(title) +msgid "OpenStack command-line clients" +msgstr "" + +#: ./doc/user-guide/section_sdk_auth_nova.xml:6(title) +msgid "Authenticate against a Compute endpoint" +msgstr "" + +#: ./doc/user-guide/section_sdk_auth_nova.xml:7(para) +msgid "To authenticate against a Compute endpoint, instantiate a novaclient.v_1_1.client.Client object:" +msgstr "" + +#: ./doc/user-guide/section_sdk_auth_nova.xml:18(para) +msgid "Alternatively, you can instantiate a novaclient.client.Client object and pass the version number:" +msgstr "" + +#: ./doc/user-guide/section_sdk_auth_nova.xml:28(para) +msgid "If you authenticate against an endpoint that uses a custom authentication back-end, you must load the authentication plug-in and pass it to the constructor." +msgstr "" + +#: ./doc/user-guide/section_sdk_auth_nova.xml:31(para) +msgid "The Rackspace Public Cloud is an OpenStack deployment that uses a custom authentication back-end. To authenticate against this cloud, you must install the rackspace-novaclient library that contains the Rackspace authentication plug-in, called rackspace. The following Python code shows the additional modifications required to instantiate a Client object that can authenticate against the Rackspace custom authentication back-end." +msgstr "" + +#: ./doc/user-guide/section_sdk_auth_nova.xml:53(para) +msgid "If you set the OS_AUTH_SYSTEM environment variable, check for this variable in your Python script to determine whether you need to load a custom authentication back-end:" +msgstr "" + +#: ./doc/user-guide/section_sdk_configure_instances.xml:10(para) +msgid "To generate a keypair, call the novaclient.v1_1.keypairs.KeypairManager.create method: " +msgstr "" + +#: ./doc/user-guide/section_sdk_configure_instances.xml:21(para) +msgid "The Python script output looks something like this: " +msgstr "" + +#: ./doc/user-guide/section_sdk_configure_instances.xml:30(para) +msgid "You will typically write the private key to a file in order to use it later. The file must be readable and writeable by only the file owner, otherwise the ssh client will refuse to read the private key file. It is safest to create the file with the appropriate permissions, as shown in the following example: " +msgstr "" + +#: ./doc/user-guide/section_sdk_configure_instances.xml:51(para) +msgid "If you have already generated a keypair with the public key located at ~/.ssh/id_rsa.pub, pass the contents of the file to the novaclient.v1_1.keypairs.KeypairManager.create method to import the public key to Compute: " +msgstr "" + +#: ./doc/user-guide/section_sdk_configure_instances.xml:65(title) +msgid "List keypairs" +msgstr "" + +#: ./doc/user-guide/section_sdk_configure_instances.xml:66(para) +msgid "To list keypairs, call the novaclient.v1_1.keypairs.KeypairManager.list method: " +msgstr "" + +#: ./doc/user-guide/section_sdk_configure_instances.xml:74(title) ./doc/user-guide/section_cli_nova_configure_instances.xml:128(title) +msgid "Create and manage security groups" +msgstr "" + +#: ./doc/user-guide/section_sdk_configure_instances.xml:75(para) +msgid "To list security groups for the current project, call the novaclient.v_1.security_groups.SecurityGroupManager.list method: " +msgstr "" + +#: ./doc/user-guide/section_sdk_configure_instances.xml:80(para) +msgid "To create a security group with a specified name and description, call the novaclient.v_1.security_groups.SecurityGroupManager.create method: " +msgstr "" + +#: ./doc/user-guide/section_sdk_configure_instances.xml:85(para) +msgid "To delete a security group, call the novaclient.v_1.security_groups.SecurityGroupManager.delete method, passing either a novaclient.v1_1.security_groups.SecurityGroup object or group ID as an argument: " +msgstr "" + +#: ./doc/user-guide/section_sdk_configure_instances.xml:99(title) ./doc/user-guide/section_cli_nova_configure_instances.xml:156(title) +msgid "Create and manage security group rules" +msgstr "" + +#: ./doc/user-guide/section_sdk_configure_instances.xml:100(para) +msgid "Access the security group rules from the rules attribute of a novaclient.v1_1.security_groups.SecurityGroup object: " +msgstr "" + +#: ./doc/user-guide/section_sdk_configure_instances.xml:106(para) +msgid "To add a rule, to a security group, call the novaclient.v1_1.security_group_rules.SecurityGroupRuleManager.create method: " +msgstr "" + +#: ./doc/user-guide/section_cli_nova_manage_instances.xml:6(title) +msgid "Manage instances and hosts" +msgstr "" + +#: ./doc/user-guide/section_cli_nova_manage_instances.xml:7(para) ./doc/user-guide/section_dashboard_launch_instances.xml:13(para) +msgid "Instances are virtual machines that run inside the cloud." +msgstr "" + +#: ./doc/user-guide/section_sdk_auth_keystone.xml:6(title) +msgid "Authenticate against an Identity Service endpoint" +msgstr "" + +#: ./doc/user-guide/section_sdk_auth_keystone.xml:7(para) +msgid "To authenticate against the Identity Service v2.0 endpoint, instantiate a keystoneclient.v_20.client.Client object:" +msgstr "" + +#: ./doc/user-guide/section_sdk_auth_keystone.xml:18(para) +msgid "After you instantiate a Client object, you can retrieve the token by accessing its auth_token attribute object:" +msgstr "" + +#: ./doc/user-guide/section_sdk_auth_keystone.xml:24(para) +msgid "If the Openstack cloud is configured to use public-key infrastructure (PKI) tokens, the Python script output looks something like this:" +msgstr "" + +#: ./doc/user-guide/section_sdk_auth_keystone.xml:35(para) +msgid "This example shows a subset of a PKI token. A complete token is over 5000 characters long." +msgstr "" + +#: ./doc/user-guide/section_dashboard_launch_instances.xml:12(title) +msgid "Launch and manage instances" +msgstr "" + +#: ./doc/user-guide/section_dashboard_launch_instances.xml:14(para) +msgid "You can launch an instance from an OpenStack image. The OpenStack Image Service provides a pool of images that are accessible to members of different projects." +msgstr "" + +#: ./doc/user-guide/section_dashboard_launch_instances.xml:18(para) +msgid "You can also launch an instance from an image that you have copied to a persistent volume. The instance boots from the volume, which is provided by nova-volume through iSCSI. When you launch an instance from a volume, especially note the following steps:" +msgstr "" + +#: ./doc/user-guide/section_dashboard_launch_instances.xml:28(para) +msgid "To select from which volume to boot, launch an instance from an arbitrary image. The image you select does not boot. It is replaced by the image on the volume that you choose in the next steps." +msgstr "" + +#: ./doc/user-guide/section_dashboard_launch_instances.xml:32(para) +msgid "To boot a Xen image from a volume, the image you launch in must be the same type, fully virtualized or paravirtualized, as the one on the volume." +msgstr "" + +#: ./doc/user-guide/section_dashboard_launch_instances.xml:37(para) +msgid "Select the volume or volume snapshot from which to boot. Enter a device name. Enter vda for KVM images or xvda for Xen images." +msgstr "" + +#: ./doc/user-guide/section_dashboard_launch_instances.xml:51(title) +msgid "SSH in to your instance" +msgstr "" + +#: ./doc/user-guide/section_dashboard_launch_instances.xml:52(para) +msgid "To SSH into your instance, you use the downloaded keypair file." +msgstr "" + +#: ./doc/user-guide/section_dashboard_launch_instances.xml:55(para) +msgid "The username is ubuntu for the Ubuntu cloud images on TryStack." +msgstr "" + +#: ./doc/user-guide/section_dashboard_launch_instances.xml:60(para) +msgid "Copy the IP address for your instance." +msgstr "" + +#: ./doc/user-guide/section_dashboard_launch_instances.xml:63(para) +msgid "Use the SSH command to make a secure connection to the instance. For example:" +msgstr "" + +#: ./doc/user-guide/section_dashboard_launch_instances.xml:68(para) +msgid "At the prompt, type yes." +msgstr "" + +#: ./doc/user-guide/section_dashboard_launch_instances.xml:74(title) +msgid "Track usage for instances" +msgstr "" + +#: ./doc/user-guide/section_dashboard_launch_instances.xml:75(para) +msgid "You can track usage for instances for each tenant, also known as a project. You can track costs per month by showing metrics like number of VCPUs, disks, RAM, and uptime for all your instances." +msgstr "" + +#: ./doc/user-guide/section_dashboard_launch_instances.xml:81(para) +msgid "Log in to the dashboard, choose a project, and click the Overview category." +msgstr "" + +#: ./doc/user-guide/section_dashboard_launch_instances.xml:86(para) +msgid "To query the instance usage for a month, select a month and click Submit." +msgstr "" + +#: ./doc/user-guide/section_dashboard_launch_instances.xml:91(para) +msgid "To download a summary, click Download CSV Summary." +msgstr "" + +#: ./doc/user-guide/section_dashboard_launch_instances.xml:97(title) +msgid "Create instance snapshots" +msgstr "" + +#: ./doc/user-guide/section_dashboard_launch_instances.xml:100(para) ./doc/user-guide/section_dashboard_launch_instances.xml:132(para) +msgid "Log in to the dashboard, choose a project, and click the Instances category." +msgstr "" + +#: ./doc/user-guide/section_dashboard_launch_instances.xml:106(para) +msgid "Select the instance from which to create a snapshot. From the Actions drop-down list, select Create Snapshot." +msgstr "" + +#: ./doc/user-guide/section_dashboard_launch_instances.xml:112(para) +msgid "In the Create Snapshot window, enter a name for the snapshot. Click Create Snapshot. The Images & Snapshots category shows the instance snapshot." +msgstr "" + +#: ./doc/user-guide/section_dashboard_launch_instances.xml:119(para) +msgid "To launch an instance from the snapshot, select the snapshot and click Launch. Proceed with ." +msgstr "" + +#: ./doc/user-guide/section_dashboard_launch_instances.xml:129(title) +msgid "Manage an instance" +msgstr "" + +#: ./doc/user-guide/section_dashboard_launch_instances.xml:138(para) +msgid "Select an instance." +msgstr "" + +#: ./doc/user-guide/section_dashboard_launch_instances.xml:141(para) +msgid "In the More drop-down list in the Actions column, select the state." +msgstr "" + +#: ./doc/user-guide/section_dashboard_launch_instances.xml:144(para) +msgid "You can resize or rebuild an instance. You can also choose to view the instance console log. Depending on the current state of the instance, you can choose to pause, resume, suspend, soft or hard reboot, or terminate an instance." +msgstr "" + +#: ./doc/user-guide/section_dashboard_launch_instances_from_volume.xml:12(title) +msgid "Launch an instance from a volume" +msgstr "" + +#: ./doc/user-guide/section_dashboard_launch_instances_from_volume.xml:14(para) +msgid "You can launch an instance directly from an image that has been copied to a persistent volume." +msgstr "" + +#: ./doc/user-guide/section_dashboard_launch_instances_from_volume.xml:18(para) +msgid "Create a volume that is large enough to store an unzipped image." +msgstr "" + +#: ./doc/user-guide/section_dashboard_launch_instances_from_volume.xml:22(para) +msgid "Create an image." +msgstr "" + +#: ./doc/user-guide/section_dashboard_launch_instances_from_volume.xml:23(para) +msgid "For details, see Creating images manually in the OpenStack Virtual Machine Image Guide." +msgstr "" + +#: ./doc/user-guide/section_dashboard_launch_instances_from_volume.xml:30(para) +msgid "Launch an instance." +msgstr "" + +#: ./doc/user-guide/section_dashboard_launch_instances_from_volume.xml:33(para) +msgid "Attach the volume to the instance." +msgstr "" + +#: ./doc/user-guide/section_dashboard_launch_instances_from_volume.xml:36(para) +msgid "Assuming that the attached volume is mounted as /dev/vdb, use one of the following commands to copy the image to the attached volume:" +msgstr "" + +#: ./doc/user-guide/section_dashboard_launch_instances_from_volume.xml:42(para) +msgid "For a raw image:" +msgstr "" + +#: ./doc/user-guide/section_dashboard_launch_instances_from_volume.xml:44(para) +msgid "Alternatively, use ." +msgstr "" + +#: ./doc/user-guide/section_dashboard_launch_instances_from_volume.xml:48(para) +msgid "For a non-raw image:" +msgstr "" + +#: ./doc/user-guide/section_dashboard_launch_instances_from_volume.xml:52(para) +msgid "For a *.tar.bz2 image:" +msgstr "" + +#: ./doc/user-guide/section_dashboard_launch_instances_from_volume.xml:58(para) +msgid "Because only detached volumes are available for booting, detach the volume." +msgstr "" + +#: ./doc/user-guide/section_dashboard_launch_instances_from_volume.xml:63(para) +msgid "Now, you can launch an instance from an image that has been copied to the volume. The instance is booted from the volume, which is provided by nova-volume through iSCSI. To launch an instance from the volume, see ." +msgstr "" + +#: ./doc/user-guide/section_dashboard_launch_instances_from_image.xml:12(title) +msgid "Launch an instance from an image" +msgstr "" + +#: ./doc/user-guide/section_dashboard_launch_instances_from_image.xml:14(para) +msgid "When you launch an instance from an image, OpenStack creates a local copy of the image on the Compute node where the instance starts." +msgstr "" + +#: ./doc/user-guide/section_dashboard_launch_instances_from_image.xml:19(para) +msgid "Log in to the dashboard, choose a project, and click the Images & Snapshot category." +msgstr "" + +#: ./doc/user-guide/section_dashboard_launch_instances_from_image.xml:22(para) +msgid "The dashboard shows the images that have been uploaded to OpenStack Image Service and are available for this project." +msgstr "" + +#: ./doc/user-guide/section_dashboard_launch_instances_from_image.xml:27(para) +msgid "Select an image and click Launch." +msgstr "" + +#: ./doc/user-guide/section_dashboard_launch_instances_from_image.xml:31(para) +msgid "In the Launch Image window, specify the following values:" +msgstr "" + +#: ./doc/user-guide/section_dashboard_launch_instances_from_image.xml:39(guilabel) +msgid "Details" +msgstr "" + +#: ./doc/user-guide/section_dashboard_launch_instances_from_image.xml:44(guilabel) +msgid "Instance Source" +msgstr "" + +#: ./doc/user-guide/section_dashboard_launch_instances_from_image.xml:46(para) +msgid "Image or snapshot." +msgstr "" + +#: ./doc/user-guide/section_dashboard_launch_instances_from_image.xml:49(guilabel) +msgid "Instance Name" +msgstr "" + +#: ./doc/user-guide/section_dashboard_launch_instances_from_image.xml:51(para) +msgid "The name to assign to the virtual machine." +msgstr "" + +#: ./doc/user-guide/section_dashboard_launch_instances_from_image.xml:56(guilabel) +msgid "Flavor" +msgstr "" + +#: ./doc/user-guide/section_dashboard_launch_instances_from_image.xml:57(para) +msgid "The size of the virtual machine to launch." +msgstr "" + +#: ./doc/user-guide/section_dashboard_launch_instances_from_image.xml:61(guilabel) +msgid "Instance Count" +msgstr "" + +#: ./doc/user-guide/section_dashboard_launch_instances_from_image.xml:63(para) +msgid "To launch multiple instances, enter a value greater than 1. Default is 1." +msgstr "" + +#: ./doc/user-guide/section_dashboard_launch_instances_from_image.xml:69(guilabel) +msgid "Access & Security" +msgstr "" + +#: ./doc/user-guide/section_dashboard_launch_instances_from_image.xml:73(guilabel) +msgid "Keypair" +msgstr "" + +#: ./doc/user-guide/section_dashboard_launch_instances_from_image.xml:74(para) +msgid "A keypair." +msgstr "" + +#: ./doc/user-guide/section_dashboard_launch_instances_from_image.xml:75(para) +msgid "In case an image uses a static root password or a static key set (neither is recommended), you do not need to provide a keypair to launch the instance." +msgstr "" + +#: ./doc/user-guide/section_dashboard_launch_instances_from_image.xml:82(guilabel) +msgid "Security Groups" +msgstr "" + +#: ./doc/user-guide/section_dashboard_launch_instances_from_image.xml:85(para) +msgid "Activate the security groups that you want to assign to the instance." +msgstr "" + +#: ./doc/user-guide/section_dashboard_launch_instances_from_image.xml:88(para) +msgid "Security groups are a kind of cloud firewall that define which incoming network traffic is forwarded to instances. For details, see ." +msgstr "" + +#: ./doc/user-guide/section_dashboard_launch_instances_from_image.xml:94(para) +msgid "If you have not created any security groups, you can assign only the default security group to the instance." +msgstr "" + +#: ./doc/user-guide/section_dashboard_launch_instances_from_image.xml:101(guilabel) ./doc/user-guide/section_dashboard_launch_instances_from_image.xml:105(guilabel) +msgid "Volume Options" +msgstr "" + +#: ./doc/user-guide/section_dashboard_launch_instances_from_image.xml:107(para) +msgid "Not applicable when you launch an instance from an image." +msgstr "" + +#: ./doc/user-guide/section_dashboard_launch_instances_from_image.xml:108(para) +msgid "To launch from a volume or volume snapshot, select the appropriate option in the Volume Options drop-down list. Then, choose the volume or snapshot." +msgstr "" + +#: ./doc/user-guide/section_dashboard_launch_instances_from_image.xml:115(para) +msgid "For information about how to create a bootable volume, see ." +msgstr "" + +#: ./doc/user-guide/section_dashboard_launch_instances_from_image.xml:122(guilabel) +msgid "Post-Creation" +msgstr "" + +#: ./doc/user-guide/section_dashboard_launch_instances_from_image.xml:126(guilabel) +msgid "Customization Script" +msgstr "" + +#: ./doc/user-guide/section_dashboard_launch_instances_from_image.xml:128(para) +msgid "A customization script that runs after your instance launches." +msgstr "" + +#: ./doc/user-guide/section_dashboard_launch_instances_from_image.xml:136(para) +msgid "Click Launch. The instance starts on a Compute node in the cloud." +msgstr "" + +#: ./doc/user-guide/section_dashboard_launch_instances_from_image.xml:140(para) +msgid "The Instances category shows the instance name, its private and public IP addresses, size, status, task, and power state." +msgstr "" + +#: ./doc/user-guide/section_dashboard_launch_instances_from_image.xml:145(para) +msgid "If you did not provide a keypair, security groups, or rules so far, users can only access the instance from inside the cloud through VNC. Even pinging the instance is not possible. To access the instance through a VNC console, see ." +msgstr "" + +#: ./doc/user-guide/bk-user-guide.xml:12(title) +msgid "OpenStack End User Guide" +msgstr "" + +#: ./doc/user-guide/bk-user-guide.xml:13(titleabbrev) +msgid "End User Guide" +msgstr "" + +#: ./doc/user-guide/bk-user-guide.xml:21(orgname) ./doc/user-guide/bk-user-guide.xml:26(holder) +msgid "OpenStack Foundation" +msgstr "" + +#: ./doc/user-guide/bk-user-guide.xml:25(year) +msgid "2013" +msgstr "" + +#: ./doc/user-guide/bk-user-guide.xml:28(releaseinfo) +msgid "havana" +msgstr "" + +#: ./doc/user-guide/bk-user-guide.xml:29(productname) +msgid "OpenStack" +msgstr "" + +#: ./doc/user-guide/bk-user-guide.xml:33(remark) +msgid "Copyright details are filled in by the template." +msgstr "" + +#: ./doc/user-guide/bk-user-guide.xml:38(para) +msgid "OpenStack is an open source cloud computing platform for public and private clouds. A series of interrelated projects deliver a cloud infrastructure solution. This guide shows OpenStack end users how to create and manage resources in an OpenStack cloud with the OpenStack dashboard and OpenStack client commands." +msgstr "" + +#: ./doc/user-guide/bk-user-guide.xml:48(date) +msgid "2013-12-30" +msgstr "" + +#: ./doc/user-guide/bk-user-guide.xml:52(para) +msgid "Added the OpenStack Python SDK chapter." +msgstr "" + +#: ./doc/user-guide/bk-user-guide.xml:59(date) +msgid "2013-10-17" +msgstr "" + +#: ./doc/user-guide/bk-user-guide.xml:63(para) +msgid "Havana release." +msgstr "" + +#: ./doc/user-guide/bk-user-guide.xml:69(date) +msgid "2013-08-19" +msgstr "" + +#: ./doc/user-guide/bk-user-guide.xml:73(para) +msgid "Editorial changes." +msgstr "" + +#: ./doc/user-guide/bk-user-guide.xml:79(date) +msgid "2013-07-29" +msgstr "" + +#: ./doc/user-guide/bk-user-guide.xml:83(para) +msgid "First edition of this document." +msgstr "" + +#: ./doc/user-guide/ch_dashboard.xml:10(title) +msgid "OpenStack dashboard" +msgstr "" + +#: ./doc/user-guide/ch_dashboard.xml:12(para) +msgid "As a cloud end user, you can use the OpenStack dashboard to provision your own resources within the limits set by administrators. You can modify these examples to create other types and sizes of server instances." +msgstr "" + +#: ./doc/user-guide/section_cli_nova_configure_instances.xml:19(para) +msgid "When you launch a virtual machine, you can inject a keypair, which provides SSH access to your instance. For this to work, the image must contain the cloud-init package. Create at least one keypair for each project. If you generate a keypair with an external tool, you can import it into OpenStack. You can use the keypair for multiple instances that belong to that project. In case an image uses a static root password or a static key set – neither is recommended – you must not provide a keypair when you launch the instance." +msgstr "" + +#: ./doc/user-guide/section_cli_nova_configure_instances.xml:29(para) +msgid "A security group is a named collection of network access rules that you use to limit the types of traffic that have access to instances. When you launch an instance, you can assign one or more security groups to it. If you do not create security groups, new instances are automatically assigned to the default security group, unless you explicitly specify a different security group. The associated rules in each security group control the traffic to instances in the group. Any incoming traffic that is not matched by a rule is denied access by default. You can add rules to or remove rules from a security group. You can modify rules for the default and any other security group." +msgstr "" + +#: ./doc/user-guide/section_cli_nova_configure_instances.xml:42(para) +msgid "You must modify the rules for the default security group because users cannot access instances that use the default group from any IP address outside the cloud." +msgstr "" + +#: ./doc/user-guide/section_cli_nova_configure_instances.xml:45(para) +msgid "You can modify the rules in a security group to allow access to instances through different ports and protocols. For example, you can modify rules to allow access to instances through SSH, to ping them, or to allow UDP traffic – for example, for a DNS server running on an instance. You specify the following parameters for rules:" +msgstr "" + +#: ./doc/user-guide/section_cli_nova_configure_instances.xml:53(para) +msgid "Source of traffic. Enable traffic to instances from either IP addresses inside the cloud from other group members or from all IP addresses." +msgstr "" + +#: ./doc/user-guide/section_cli_nova_configure_instances.xml:59(para) +msgid "Protocol. Choose TCP for SSH, ICMP for pings, or UDP." +msgstr "" + +#: ./doc/user-guide/section_cli_nova_configure_instances.xml:63(para) +msgid "Destination port on virtual machine. Defines a port range. To open a single port only, enter the same value twice. ICMP does not support ports: Enter values to define the codes and types of ICMP traffic to be allowed." +msgstr "" + +#: ./doc/user-guide/section_cli_nova_configure_instances.xml:70(para) +msgid "Rules are automatically enforced as soon as you create or modify them." +msgstr "" + +#: ./doc/user-guide/section_cli_nova_configure_instances.xml:72(para) +msgid "You can also assign a floating IP address to a running instance to make it accessible from outside the cloud. You assign a floating IP address to an instance and attach a block storage device, or volume, for persistent storage. See ." +msgstr "" + +#: ./doc/user-guide/section_cli_nova_configure_instances.xml:81(para) +msgid "You can generate a keypair or upload an existing public key." +msgstr "" + +#: ./doc/user-guide/section_cli_nova_configure_instances.xml:84(para) +msgid "To generate a keypair, run the following command:" +msgstr "" + +#: ./doc/user-guide/section_cli_nova_configure_instances.xml:86(replaceable) ./doc/user-guide/section_cli_nova_configure_instances.xml:115(replaceable) +msgid "KEY_NAME" +msgstr "" + +#: ./doc/user-guide/section_cli_nova_configure_instances.xml:86(replaceable) ./doc/user-guide/section_cli_nova_configure_instances.xml:98(replaceable) +msgid "MY_KEY" +msgstr "" + +#: ./doc/user-guide/section_cli_nova_configure_instances.xml:87(para) +msgid "The command generates a keypair named KEY_NAME, writes the private key to the MY_KEY.pem file, and registers the public key at the Nova database." +msgstr "" + +#: ./doc/user-guide/section_cli_nova_configure_instances.xml:95(para) +msgid "To set the permissions of the MY_KEY.pem file, run the following command:" +msgstr "" + +#: ./doc/user-guide/section_cli_nova_configure_instances.xml:99(para) +msgid "The command changes the permissions of the MY_KEY.pem file so that only you can read and write to it." +msgstr "" + +#: ./doc/user-guide/section_cli_nova_configure_instances.xml:110(para) +msgid "If you have already generated a keypair with the public key located at ~/.ssh/id_rsa.pub, run the following command to upload the public key:" +msgstr "" + +#: ./doc/user-guide/section_cli_nova_configure_instances.xml:116(para) +msgid "The command registers the public key at the Nova database and names the keypair KEY_NAME." +msgstr "" + +#: ./doc/user-guide/section_cli_nova_configure_instances.xml:121(para) +msgid "List keypairs to make sure that the uploaded keypair appears in the list:" +msgstr "" + +#: ./doc/user-guide/section_cli_nova_configure_instances.xml:131(para) +msgid "To list security groups for the current project, including descriptions, enter the following command:" +msgstr "" + +#: ./doc/user-guide/section_cli_nova_configure_instances.xml:137(para) +msgid "To create a security group with a specified name and description, enter the following command:" +msgstr "" + +#: ./doc/user-guide/section_cli_nova_configure_instances.xml:140(replaceable) ./doc/user-guide/section_cli_nova_configure_instances.xml:145(replaceable) ./doc/user-guide/section_cli_nova_configure_instances.xml:166(replaceable) ./doc/user-guide/section_cli_nova_configure_instances.xml:178(replaceable) ./doc/user-guide/section_cli_nova_configure_instances.xml:188(replaceable) ./doc/user-guide/section_cli_nova_configure_instances.xml:205(replaceable) ./doc/user-guide/section_cli_nova_configure_instances.xml:214(replaceable) ./doc/user-guide/section_cli_nova_configure_instances.xml:234(replaceable) ./doc/user-guide/section_cli_nova_configure_instances.xml:244(replaceable) ./doc/user-guide/section_cli_nova_configure_instances.xml:249(replaceable) +msgid "SEC_GROUP_NAME" +msgstr "" + +#: ./doc/user-guide/section_cli_nova_configure_instances.xml:140(replaceable) +msgid "GROUP_DESCRIPTION" +msgstr "" + +#: ./doc/user-guide/section_cli_nova_configure_instances.xml:143(para) +msgid "To delete a specified group, enter the following command:" +msgstr "" + +#: ./doc/user-guide/section_cli_nova_configure_instances.xml:147(para) +msgid "You cannot delete the default security group for a project. Also, you cannot delete a security group that is assigned to a running instance." +msgstr "" + +#: ./doc/user-guide/section_cli_nova_configure_instances.xml:158(para) +msgid "Modify security group rules with the commands." +msgstr "" + +#: ./doc/user-guide/section_cli_nova_configure_instances.xml:161(para) +msgid "On a shell, source the OpenStack RC file. For details, see ." +msgstr "" + +#: ./doc/user-guide/section_cli_nova_configure_instances.xml:165(para) +msgid "To list the rules for a security group" +msgstr "" + +#: ./doc/user-guide/section_cli_nova_configure_instances.xml:169(para) +msgid "To allow SSH access to the instances, choose one of the following sub-steps:" +msgstr "" + +#: ./doc/user-guide/section_cli_nova_configure_instances.xml:173(title) +msgid "Add rule for all IPs" +msgstr "" + +#: ./doc/user-guide/section_cli_nova_configure_instances.xml:175(para) +msgid "Either from all IP addresses (specified as IP subnet in CIDR notation as 0.0.0.0/0):" +msgstr "" + +#: ./doc/user-guide/section_cli_nova_configure_instances.xml:181(title) +msgid "Add rule for security groups" +msgstr "" + +#: ./doc/user-guide/section_cli_nova_configure_instances.xml:183(para) +msgid "Alternatively, you can allow only IP addresses from other security groups (source groups) to access the specified port:" +msgstr "" + +#: ./doc/user-guide/section_cli_nova_configure_instances.xml:188(replaceable) ./doc/user-guide/section_cli_nova_configure_instances.xml:214(replaceable) ./doc/user-guide/section_cli_nova_configure_instances.xml:234(replaceable) ./doc/user-guide/section_cli_nova_configure_instances.xml:249(replaceable) +msgid "SOURCE_GROUP_NAME" +msgstr "" + +#: ./doc/user-guide/section_cli_nova_configure_instances.xml:193(para) +msgid "To allow pinging the instances, choose one of the following sub-steps:" +msgstr "" + +#: ./doc/user-guide/section_cli_nova_configure_instances.xml:197(title) +msgid "To allow pinging from IPs" +msgstr "" + +#: ./doc/user-guide/section_cli_nova_configure_instances.xml:199(para) +msgid "Specify all IP addresses as IP subnet in CIDR notation: 0.0.0.0/0. This command allows access to all codes and all types of ICMP traffic, respectively:" +msgstr "" + +#: ./doc/user-guide/section_cli_nova_configure_instances.xml:208(title) +msgid "To allow pinging from other security groups" +msgstr "" + +#: ./doc/user-guide/section_cli_nova_configure_instances.xml:210(para) +msgid "To allow only members of other security groups (source groups) to ping instances:" +msgstr "" + +#: ./doc/user-guide/section_cli_nova_configure_instances.xml:219(para) +msgid "To allow access through a UDP port, such as allowing access to a DNS server that runs on a VM, complete one of the following sub-steps:" +msgstr "" + +#: ./doc/user-guide/section_cli_nova_configure_instances.xml:224(para) +msgid "To allow UDP access from IPs, specify all IP addresses as IP subnet in CIDR notation: 0.0.0.0/0." +msgstr "" + +#: ./doc/user-guide/section_cli_nova_configure_instances.xml:230(para) +msgid "To allow only IP addresses from other security groups (source groups) to access the specified port:" +msgstr "" + +#: ./doc/user-guide/section_cli_nova_configure_instances.xml:239(para) +msgid "To delete a security group rule, specify the same arguments that you used to create the rule." +msgstr "" + +#: ./doc/user-guide/section_cli_nova_configure_instances.xml:242(para) +msgid "To delete the security rule that you created in :" +msgstr "" + +#: ./doc/user-guide/section_cli_nova_configure_instances.xml:245(para) +msgid "To delete the security rule that you created in :" +msgstr "" + +#. Put one translator per line, in the form of NAME , YEAR1, YEAR2 +#: ./doc/user-guide/section_cli_nova_configure_instances.xml:0(None) +msgid "translator-credits" +msgstr "" +